Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT activities are to be carried out, and the behavior of the Invoker and Performer if the time constraints are violated. 3.4.2.2 Procedure Pattern The three-phase operation procedure begins with the Invoker generating an operation Invocation message, placing it in an SleSmMessageSet, transmitting the SleSmMessageSet to the Performer’s message set port using the SLE-SM document exchange protocol defined in 3.3, and starting the disposition timer for the operation. If the urgent parameter of the invocation is ‘false’, the disposition timer is set to the urgent three-phase timeout value specified in the Service Agreement (see section 7) for that operation type; otherwise, the disposition timer is set to the routine three-phase timeout value for that operation. Upon receipt of the SleSmMessageSet containing the Invocation, the Performer performs message set validation as specified for the Receive and Validate SLE-SM Message Set activity subgroup of the Document Exchange Protocol activity group in 3.3. If the SleSmMessageSet fails message set validation, the Performer generates and transmits an exception response containing an UnrecognizedMessageSetResponse or InvalidMessageResponse (as appropriate to the exception) to the Invoker exception response port, as specified in 3.3. If the Invocation message passes message set validation, the Performer estimates how long it will take to perform the operation, returns to the Invoker’s message set port an AcknowledgedReturn message containing in the expectedDispositionTime parameter (see table 3-14) the maximum estimated time until a final disposition can be provided, and starts a local disposition timer based on that value. If the urgent parameter of the invocation is ‘false’, the expectedDispositionTime value is constrained to be no longer than that allowed by the urgent three-phase timeout value specified for the operation in the Service Agreement (see section 7); otherwise, the expectedDispositionTime value is constrained to be no longer than that allowed by the routine three-phase timeout value specified for the operation. The AcknowledgedReturn message may also contain locally defined further information explaining the conditions that determined the expectedDispositionTime value in the privateAnnotation parameter (e.g., ‘next weekly schedule run’). NOTES 1 In order for the Performer to ensure that any return to an Invocation arrives at the Invoker before the specified expectedDispositionTime, the Performer must adjust (i.e., shorten) its local disposition timer value by some amount of time to compensate for the transit of the return across the communications network that connects them. The method by which the Performer determines this adjustment factor is outside the scope of this Recommended Standard. CCSDS 910.11-R-2 Page 3-47 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 2 It is assumed that the time standards upon which the Invoker and Performer set their disposition timers are synchronized to within one (1) second of each other. If this assumption cannot be made for a particular pair of Invoker and Performer, then additional methods may be required to compensate for the ambiguity (such as further decreasing the Performer’s disposition timer value to account for the ambiguity). Any such adjustment for time standard ambiguity is outside the scope of this Recommended Standard. The Performer performs service management validation on the Invocation. The details of service management level validation are specific to each operation. If the Invocation is valid at the service management level and the operation can be performed before the disposition timeout is reached, the Performer performs the invoked operation and returns a SuccessfulReturn message to the Invoker’s message set port. The details of the performance of the operation and the information returned as part of the result are operation-specific. The Performer may perform local functions specific to a successful operation as part of completing the operation procedure. If the Invocation is not valid at the service management level, or if the Performer cannot complete service management validation before the disposition timer expires, the Performer completes the operation procedure and returns a FailedReturn* message to the Invoker’s message set port such that the Invoker receives the result before the disposition timer expires. The FailedReturn* message contains operation-specific diagnostic information. The Performer may perform local functions specific to a failed operation as part of completing the operation procedure. Upon receipt of an UnrecognizedMessageSetResponse or InvalidMessage- Response, the Invoker validates the exception response in accordance with the Receive and Validate SLE-SM Exception Response activity subgroup of the Document Exchange Protocol activity group specified in 3.3. The Invoker attempts to correlate the contents of each syntactically correct UnrecognizedMessageSetResponse and InvalidMessageResponse with SLE-SM operation Invocations that have been sent by the Invoker. If the UnrecognizedMessageSetResponse or InvalidMessageResponse can be correlated to one or more Invocations, the Invoker terminates the correlated operation(s), and completes the procedure. The Invoker may perform local functions specific to an unknown or invalid Invocation as part of completing the operation procedure (e.g., update local databases to reflect failure of the operation, contact the Performer to troubleshoot the failure). Upon receipt of the SleSmMessageSet containing the AcknowledgedReturn message, the Invoker performs message set validation as specified for the Receive and Validate SLE-SM Message Set activity subgroup of the Document Exchange Protocol activity group in 3.3. If the SleSmMessageSet passes message set validation, the Invoker performs service management validation on the AcknowledgedReturn. The details of service management validation are specific to each operation, and are specified in the associated Invoker and Performer requirements for each operation. If the CCSDS 910.11-R-2 Page 3-48 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: 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 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?