Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT Table 3-22: InvalidMessageResponse Message Data Set Parameter Name Parameter Definition/Description Data Type Units diagnostic The reason for the invalidity of the Enum n/a message: – ‘invalid messageSequenceNumber’; – ‘repeated messageSequenceNumber’; – ‘invoked operation not supported by this Service Agreement’; – ‘notification not supported by this Service Agreement’. invocationMessageSequenceNumber The sequence number of the invalid Positive n/a invocation or notification message. Integer messageSequenceNumber See table 3-5. serviceAgreementRef The identification of the Service String256 n/a Agreement under which the invalid message being reported upon was received. sleSmCreatorName The logical or functional name of the creator of the InvalidMessageResponse. String256 n/a NOTE – Despite its name, the parameter invocationMessageSequenceNumber may refer to notifications as well as invocations. Table 3-23: UnrecognizedMessageSetResponse diagnostic Parameter Definition diagnostic value Definition/Description Rqmt ‘document source The communication-service-provided Source MPR-0005 not authorized for identification associated with the Message Set is sleSmCreatorName’ not authorized to send Message Sets using the sleSmCreatorName in the context of the referenced Service Agreement ‘does not conform to syntax of SLE- SM message set’ The content of the message set does not conform to the syntax of an SLE-SM message set. MSD-0001, MSD-0003 – MSD-0008 erroredItem value sleSm- CreatorName n/a ‘sleSmCreatorName not authorized for Service Agreement’ ‘unknown serviceAgreement- Ref’ The sleSmCreatorName is not authorized in the context of the referenced Service Agreement. The serviceAgreementRef does not reference an authorized SLE-SM Service Agreement. MPR-0004 MPR-0003 sleSm- CreatorName service- AgreementRef CCSDS 910.11-R-2 Page 3-35 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT diagnostic value Definition/Description Rqmt ‘unknown The sleSmCreatorName is not recognized by MPR-0002 sleSmCreatorName’ the Receiver as an authorized creator of SLE-SM message sets. ‘version not supported’ The version named in sleSmVersionRef is not supported MSD-0002 erroredItem value sleSm- CreatorName sleSmVersion Ref Table 3-24: InvalidMessageResponse diagnostic Parameter Definition diagnostic value Definition/Description Rqmt ‘invalid The messageSequenceNumber of at least one MPR-0006 messageSequence- invocation message in a message set is not greater Number’ than the messageSequenceNumber of all valid invocation messages received in previous message sets with that same sleSmCreatorName and serviceAgreementRef. ‘invoked operation not supported by this Service Agreement’ ‘notification not supported by this Service Agreement’ ‘repeated Message- SequenceNumber’ The invocation message is for an operation that is not supported under the referenced Service Agreement. The notification is not supported under the referenced Service Agreement. The messageSequenceNumber of an invocation message repeats within the message set. MPR-0008 MPR-0009 MPR-0007 Parameter or Data Set Identified by erroredItem message- Sequence- Number Identification of the unsupported operation. Identification of the unsupported operation. message- Sequence- Number 3.3.4.4.3 Data Set Composition and Relationship Requirements Table 3-25 defines the data set composition and relationship requirements common to all SleSmExceptionResponse messages. Table 3-25: Data Set Composition and Relationship Requirements for All SleSmExceptionResponses ERD-0001 An SleSmExceptionResponse shall contain the SleSmExceptionResponse parameters specified in table 3-20. [syntactic validation] ERD-0002 The sleSmVersionRef parameter shall have the value of ‘1’. [syntactic validation] ERD-0003 An SleSmExceptionResponse shall contain one InvalidMessageResponse data set or one UnrecognizedMessageSetResponse data set. [syntactic validation] CCSDS 910.11-R-2 Page 3-36 March 2008
Page 2 and 3:
Draft Recommendation for Space Data
Page 4 and 5:
DRAFT RECOMMENDED STANDARD FOR SPAC
Page 6 and 7:
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45: DRAFT RECOMMENDED STANDARD FOR SPAC
Page 48 and 49: CCSDS 910.11-R-2 Page 2-5 March 200
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
Page 410 and 411:
Page 412 and 413:
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 432 and 433:
Page 434 and 435:
Page 436:
show all

Space Link Extension - Service Management - CCSDS

Create successful ePaper yourself

Delete template?

Save as template?