Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 5.3.3 REQUIREMENTS 5.3.3.1 UM Requirements for the ADD_SPACE_LINK_SESSION_PROFILE Operation Table 5-2: UM Requirements for the ASLSP Operation ASLSPU-01 UM shall conform to all ASLSP-I Data Set Composition and Relationship Requirements when creating and transmitting an ASLSP-I as specified in table 5-25 and table 5-27. ASLSPU-02 UM shall conform to all Invoker Requirements for Three-Phase Operation Procedures as specified in 3.4.2.6.1. ASLSPU-03 UM should send ASLSP-I messages that are valid with respect to all service management validation requirements for CM as defined in table 5-25 and table 5-27. ASLSPU-04 UM shall validate that a received ASLSP-AR, ASLSP-SR, or ASLSP-FR conforms to all ASLSP-AR, ASLSP-SR, or ASLSP-FR syntactic validation requirements specified in table 5-29, table 5-30, or, table 5-32, respectively. If the return fails any of the syntactic validation requirements, UM shall process the message set containing the syntactically invalid return in accordance with the Invoker Requirements for Three-Phase Operation Procedures. ASLSPU-05 UM shall validate that a received ASLSP-AR, ASLSP-SR, or ASLSP-FR conforms to all ASLSP-AR, ASLSP-SR, or ASLSP-FR service management validation requirements specified in table 5-29, table 5-30, or, table 5-32, respectively. If the return fails any of the service management validation requirements, UM shall process the service management-invalid return in accordance with the Invoker Requirements for Three-Phase Operation Procedures. 5.3.3.2 CM Requirements for the ADD_SPACE_LINK_SESSION_PROFILE Operation Table 5-3: CM Requirements for the ASLSP Operation ASLSPC-01 CM shall conform to all Performer Requirements for Three-Phase Operation Procedures as specified in 3.4.2.6.2. ASLSPC-02 CM shall validate that a received ASLSP-I conforms to all ASLSP-I syntactic validation requirements specified in table 5-25 and table 5-27, Data Set Composition and Relationship Requirements for the ASLSP-I. If the ASLSP-I fails any of the syntactic requirements, CM shall process the message set containing the syntactically invalid invocation in accordance with the Performer Requirements for Three-Phase Operation Procedures. ASLSPC-03 CM shall validate that the ASLSP-I conforms to all ASLSP-I service management validation requirements specified in this table and in table 5-25 and table 5-27, Data Set Composition and Relationship Requirements. If the ASLSP-I fails any of the service management requirements, CM shall cease processing the ASLSP-I and respond to UM with an ASLSP-FR message. The content of the ASLSP-FR depends on the nature of the validation failure, and is specified table 5-31. ASLSPC-04 CM shall validate that the ASLSP-I would not cause the number of Carrier Profiles to exceed maxCarrierProfiles for the referenced Service Agreement parameter. [service management validation] ASLSPC-05 CM shall validate that each ASLSP-I parameter that is constrained by a Service Agreement parameter is consistent with the applicable Service Agreement parameter. [service management validation] CCSDS 910.11-R-2 Page 5-5 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT ASLSPC-06 CM shall validate that all ASLSP-I parameter values that are related to each other (as defined in the Data Set Composition and Relationship Requirements) contain mutually compatible values. [service management validation] ASLSPC-07 If the SLE Complex has locally defined ASLSP-I relationship requirements in addition to those specified in this Recommended Standard, CM shall validate that the ASLSP-I conforms to all such local requirements. [service management validation] ASLSPC-08 If the ASLSP-I passes all syntactic and service management validation, CM shall: a) add the Carrier Profile to the set of Carrier Profiles resident at CM: b) count the Carrier Profile as applying against the maxCarrierProfiles parameter of the Service Agreement; and c) send an ASLSP-SR message to CM. [perform operation] ASLSPC-09 CM shall conform to all ASLSP-SR Data Set Composition and Relationship Requirements when creating and transmitting an ASLSP-SR as specified in table 5-30. ASLSPC-10 CM shall conform to all ASLSP-FR Data Set Composition and Relationship Requirements when creating and transmitting an ASLSP-FR as specified in table 5-32. ASLSPC-11 CM shall conform to all ASLSP-AR Data Set Composition and Relationship Requirements when creating and transmitting an ASLSP-AR as specified in table 5-29. 5.3.4 DATA SET STEREOTYPE 5.3.4.1 General The data set stereotype captures the parameters and data set relationships that are common among messages that create Space Link Session Profiles or report their contents. Figure 5-2 shows the message structure of the data set stereotype as a class diagram. CCSDS 910.11-R-2 Page 5-6 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:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
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: DRAFT RECOMMENDED STANDARD FOR SPAC
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?