Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 3.4.3.6 Requirements 3.4.3.6.1 Notifier Requirements for Notified Operation Procedures Table 3-36: Notifier Requirements for the Notified Operation Procedures CNN-0001 CNN-0002 CNN-0003 CNN-0004 CNN-0005 CNN-0006 CNN-0007 CNN-0008 CNN-0009 The Notifier shall format the Notification and transmit it to the Recipient’s message set port in conformance with the Sender Requirements for the SLE-SM Document Exchange Protocol (3.3.3.1). The Notifier shall set the confirmation timer to the value of the messageTimestamp of the Notification message plus the confirmationTimeout for the referenced ServiceAgreement. The Notifier shall validate a Confirmation received from the Recipient in accordance with the Receiver Requirements for the SLE-SM Document Exchange Protocol. The Notifier shall validate exception responses received from the Recipient on the exception response port in accordance with the Sender Requirements for the SLE-SM Document Exchange Protocol. If a received Confirmation fails any service management validation requirement specified for its notified operation type, the Confirmation shall be deemed to be service management-invalid. The Notifier is not required to further interpret or act upon the service management-invalid Confirmation. For each syntactically valid UnrecognizedMessageSetResponse received on the exception response port, the Notifier shall attempt to correlate the content of the UnrecognizedMessage- SetResponse with a Notification awaiting confirmation. If correlation is successful, the Notifier shall inform the Recipient, by bilaterally agreed means, of the operation that emitted the Notification. The Notifier is not required to further interpret or act upon any Unrecognized- MessageSetResponse that cannot be correlated. For each syntactically valid InvalidMessageResponse received on the exception response port, the Invoker shall attempt to correlate the content of the InvalidMessageResponse with a Notification awaiting confirmation. If correlation is successful, the Notifier shall inform the Recipient, by bilaterally agreed means, of the operation that emitted the Notification. The Notifier is not required to further interpret or act upon any InvalidMessageResponse that cannot be correlated. The Notifier shall confirm that the invocationMessageSequenceNumber and ServiceAgreementRef parameters of a Confirmation match the messageSequence- Number and ServiceAgreementRef, respectively, of a Notification for which the Notifier is awaiting a Confirmation, in order to associate a Confirmation with a Notification. NOTE – This is a necessary but not sufficient condition for acceptance of a Confirmation for a notification. There are additional operation-level matching criteria that must also be met, as specified under the requirements for the specific operations. If a validated Confirmation is not received for a Notification by the time the associated confirmation timer expires, the Notifier shall inform the Recipient, by bilaterally agreed means, of the operation that emitted the Notification. CCSDS 910.11-R-2 Page 3-63 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 3.4.3.6.2 Recipient Requirements for Notified Operation Procedures Table 3-37: Recipient Requirements for the Notified Operation Procedures CNR-0101 CNR-0102 CNR-0103 CNR-0104 CNR-0105 CNR-0106 The Recipient shall receive and validate the Notification message in conformance with the Receiver Requirements for the SLE-SM Document Exchange Protocol (3.3.3.2). If the Notification message passes message set validation as specified in CNC-0101, the Recipient shall generate and send a Confirmation message to the Recipient’s message set port in accordance with the Sender Requirements for the SLE-SM Document Exchange Protocol. If the Notification fails validation, the Recipient shall cease interpreting and acting upon the Notification and not send a Confirmation. The Recipient should transmit the Confirmation message such that the Recipient receives the Confirmation no later than the messageTimestamp of the Notification plus the value of the confirmationTimeout of the referenced Service Agreement. The Recipient shall validate exception responses received from the Notifier on the exception response port in accordance with the Sender Requirements for the SLE-SM Document Exchange Protocol. If a received Notification fails any service management validation requirement specified for its notified operation type, the Notification shall be deemed to be service management-invalid. The Recipient is not required to further interpret or act upon the service management-invalid Notification. For each syntactically valid UnrecognizedMessageSetResponse received on the exception response port, the Recipient shall attempt to correlate the content of the UnrecognizedMessage- SetResponse with a Confirmation that was sent. If correlation is successful, the Recipient shall notify the Notifier by other means of the contents of any Confirmation that was contained in a message set for which a valid UnrecognizedMessageSetResponse is received. The Recipient is not required to further interpret or act upon any UnrecognizedMessageSetResponse that cannot be correlated. CCSDS 910.11-R-2 Page 3-64 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:
Page 46 and 47:
Page 48 and 49:
CCSDS 910.11-R-2 Page 2-5 March 200
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
CCSDS 910.11-R-2 Page 3-11 March 20
Page 72 and 73: CCSDS 910.11-R-2 Page 3-13 March 20
Page 74 and 75: DRAFT RECOMMENDED STANDARD FOR SPAC
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?