Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT CSPD-48 A CarrierResult data set shall contain a) an FSpaceLinkEventsResult data set if and only if: 1) the carrierProfileRef parameter of the CarrierResult references a forward Space Link Carrier Profile in the Space Link Session Profile; and 2) the corresponding SpaceLinkServiceRequest of the ServicePackageInvocation contains a SpaceLinkEventsProfileReference data set with the same carrierProfileRef value and a spaceLinkEventsProfileRef for a Forward Space Link Events Profile; b) an RSpaceLinkEventsResult data set if and only if: 1) the carrierProfileRef parameter of the CarrierResult references a return Space Link Carrier Profile in the Space Link Session Profile; and 2) the corresponding SpaceLinkServiceRequest of the ServicePackageInvocation contains a SpaceLinkEventsProfileReference data set with the same carrierProfileRef value and a spaceLinkEventsProfileRef for a Return Space Link Events Profile. c) a BilateralSpaceLinkEventsResult data set if and only if the corresponding SpaceLinkServiceRequest of the ServicePackageInvocation contains a SpaceLinkEventsProfileReference data set with the spaceLinkEventsProfileRef indicating a BilateralSpaceLinkEventsProfile. [service management validation] CSPD-49 CSPD-50 CSPD-51 CSPD-52 NOTE – Use of bilaterally defined event sequences also implies a bilaterally defined mechanism for identifying events with respect to particular space link carriers. For each ServiceScenarioResult data set, the trajectoryRef parameter shall have the same value as that of the ServicePackageInvocation. [service management validation] The [R|F]SpaceLinkEventsResults data set shall contain the same number, ordering, and contents of the [R|F]SpaceLinkAvailableStates as that contained in the referenced Space Link Events Profile. [service management validation] All eventScheduledTime values associated with space link availability states and space link data transport states shall be within the interval of time bound by the corresponding parent space link availability or data transport state. [service management validation] For each RetrievalTsProfileRespecification data set in the corresponding ServicePackageInvocation that references a non-bilateral Space Link Session Transfer Service Profile, the CcsdsRetrievalTsInstanceResult data set shall contain one RetrievalTsProfileRespecResult data set and one RetrievalTsProfileInEffect data set. [service management validation] NOTE – RetrievalTsProfileRespecification data sets that reference bilateral Retrieval Transfer Service Profiles are reflected in the content of the bilateralRtrvlTsInstanceResultData parameter of the corresponding BilateralRetrievalTsInstanceResult data set. How these changes are reflected are determined bilaterally and are outside the scope of this Recommended Standard. CCSDS 910.11-R-2 Page 4-41 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT CSPD-53 CSPD-54 CSPD-55 A RetrievalTsProfileRespecResult data set shall contain one or more RespecifiedParameter data sets. [syntactic validation] A RetrievalTsProfileRespecResult data set shall contain the same number and contents of RespecifiedParameter data sets as its corresponding RetrievalTsProfileRespecification data set of the corresponding ServicePackageInvocation. [service management validation] A RetrievalTsProfileInEffect data set shall contain the contents of the referenced (transferServiceProfileRef) Retrieval Transfer Service Profile, as modified by the RespecifiedParameter data set(s) of the associated RetrievalTsProfileRespecResult data set. [service management validation] 4.3.8 CreateServicePackageSuccessfulReturn (CSP-SR) MESSAGE (CM UM) 4.3.8.1 General The CreateServicePackageSuccessfulReturn message conforms to the data set composition and relationship requirements for, and inherits the parameters of, the stereotype, as specified in 3.3.4.3.3.2, and the stereotype, as specified in 4.3.7. The class diagram for the message structure is shown in figure 4-9. , CreateServicePackage- SuccessfulReturn 1 1 ServicePackageReference servicePackageRef Figure 4-9: CSP-SR Message Structure, Presented in a Class Diagram 4.3.8.2 Parameters The contents of the ServicePackageReference data set are defined in table 4-18. CCSDS 910.11-R-2 Page 4-42 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:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115: DRAFT RECOMMENDED STANDARD FOR SPAC
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?