Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 3.4.2.6 Requirements 3.4.2.6.1 Invoker Requirements for Three-Phase Operation Procedures Table 3-32: Invoker Requirements for the Three-Phase Operation Procedures 3PI-0001 3PI-0002 3PI-0003 3PI-0004 3PI-0005 3PI-0006 3PI-0006 3PI-0007 3PI-0008 3PI-0009 The Invoker shall format the operation Invocation and transmit it to the Performer’s message set port in conformance with the Sender Requirements for the SLE-SM Document Exchange Protocol as defined in 3.3.3.1. The Invoker shall set the value of the disposition timer using the value of the appropriate three-phase timer parameter for that operation in the referenced Service Agreement: a) If the invocation is urgent, the urgent parameter shall be set to ‘true’ and the disposition timer shall be set to the messageTimestamp of the Invocation plus the value of the urgent timeout parameter for that operation. b) If the invocation is routine, the urgent parameter shall be set to ‘false’ and the disposition timer shall be set to the messageTimestamp of the Invocation plus the value of the routine timeout parameter for that operation. The Invoker shall validate returns received from the Performer on the message set port in accordance with the Receiver Requirements for the SLE-SM Document Exchange Protocol as defined in 3.3.3.2. The Invoker shall validate exception responses received from the Performer on the exception response port in accordance with the Sender Requirements for the SLE-SM Document Exchange Protocol as defined in 3.3.3.1. For each syntactically valid UnrecognizedMessageSetResponse received on the exception response port, the Invoker shall attempt to correlate the content of the UnrecognizedMessageSet- Response with one or more Invocations awaiting disposition. If correlation is successful, the Invoker shall terminate any operation for which an Invocation is contained in a message set for which a validated UnrecognizedMessageSetResponse is received. The Invoker is not required to further interpret or act upon any UnrecognizedMessageSetResponse 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 an Invocation awaiting disposition. If correlation is successful, the Invoker shall terminate the operation for which the Invocation is rejected in the InvalidMessageResponse. The Invoker is not required to further interpret or act upon any InvalidMessageResponse that cannot be correlated. If the expectedDispositionTime parameter of the AcknowledgedReturn message is less than the disposition time that the Invoker set based on the value of the appropriate (routine or urgent) three-phase timeout value, the Invoker shall reset the value of the return disposition timer to the value of the expectedDispositionTime parameter of the AcknowledgedReturn message. The Invoker shall terminate any operation for which a FailedReturn* is received. The Invoker shall ignore any AcknowledgedReturn that is received either (a) after receipt of a SuccessfulReturn or FailedReturn* for the same operation, or (b) after the associated disposition timer expires. The Invoker shall confirm that the invocationMessageSequenceNumber and ServiceAgreementRef parameters of a return match the messageSequenceNumber and ServiceAgreementRef, respectively, of an Invocation for which the Invoker is awaiting a return, in order to associate a return with an Invocation. NOTE – This is a necessary but not sufficient condition for acceptance of a return for an Invocation. There are additional operation-level matching criteria that must also be met, as specified in the requirements for the specific operations. CCSDS 910.11-R-2 Page 3-55 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 3PI-0010 3PI-0011 If an AcknowledgedReturn, a SuccessfulReturn or a FailedReturn* fails any service management validation requirement specified for its return type, the return shall be deemed to be service management-invalid. The Invoker is not required to further interpret or act upon the service managementinvalid return. If a SuccessfulReturn or FailedReturn* is not received for the operation by the time the associated disposition timer expires, the Invoker shall contact the Performer to determine the disposition of the operation. 3.4.2.6.2 Performer Requirements for Three-Phase Operation Procedures Table 3-33: Performer Requirements for the Three-Phase Operation Procedures 3PP-0101 3PP-0102 3PP-0103 3PP-0104 3PP-0105 The Performer shall receive and validate the operation Invocation in conformance with the Receiver Requirements for the SLE-SM Document Exchange Protocol as defined in 3.3.3.2. If the Invocation passes message set validation as specified in 3PP-0101, the Performer shall generate and send an AcknowledgedReturn message to the Invoker’s message port in accordance with the Sender Requirements for the SLE-SM Document Exchange Protocol as defined in 3.3.3.2. a) If the urgent parameter of the invocation is ‘true’, the Performer shall set the expectedDispositionTime parameter of the AcknowledgedReturn message to no later than the messageTimestamp of the Invocation plus the value of the urgent timeout parameter of the referenced Service Agreement. Otherwise, the Performer shall set the expectedDispositionTime parameter to no later than the messageTimestamp of the Invocation plus the value of the routine timeout parameter of the referenced Service Agreement. b) The Performer shall transmit the AcknowledgedReturn to the Invoker such that the return is received by the Invoker at or before the messageTimestamp of the operation Invocation plus the value of the routine timeout or urgent timeout parameter of the referenced Service Agreement, as appropriate (see 3PI-0002). c) The Performer shall transmit the AcknowledgedReturn prior to transmitting the SuccessfulReturn or FailedReturn* message (see 3PP-0103). d) The Performer shall start a local disposition timer for the operation and set it to timeout with sufficient lead time before the expectedDispositionTime to allow the final return for the operation to be received by the Invoker prior to the expectedDispositionTime. NOTE – See 3.4.2.2, Note 1, for considerations in setting the disposition timer. The Performer shall perform operation-specific service management validation on the Invocation. a) If the Invocation passes service management validation, the Performer shall perform the operation and generate and transmit a SuccessfulReturn to the Invoker’s message set port in accordance with the Sender Requirements for the SLE-SM Document Exchange Protocol as defined in 3.3.3.1. The parameters of the SuccessfulReturn are operation-specific. b) If the invocation fails service management validation, the Performer shall cease interpreting and acting upon the Invocation, generate a FailedReturn*, and transmit the FailedReturn* to the Invoker’s message set port in accordance with the Sender Requirements for the SLE-SM Document Exchange Protocol. The Performer shall transmit the SuccessfulReturn or FailedReturn to the Invoker before the expiration of the associated disposition timer. If the invoked operation cannot be successfully completed or failed for other reasons by the expiration of that timer, the Performer shall terminate the operation and return a FailedReturn* with diagnostic value ‘operation timeout’. The Performer shall validate exception responses received from the Invoker on the exception response port in accordance with the Sender Requirements for the SLE-SM Document Exchange Protocol as defined in 3.3.3.1. CCSDS 910.11-R-2 Page 3-56 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: DRAFT RECOMMENDED STANDARD FOR SPAC
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 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?