Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 5.7.3 REQUIREMENTS 5.7.3.1 UM Requirements for the DELETE_SPACE_LINK_EVENTS_PROFILE Operation Table 5-63: UM Requirements for the DSLEP Operation DSLEPU-01 UM shall conform to all Invoker Requirements for Two-Phase Operation Procedures as specified in 3.4.1.6.1. DSLEPU-02 UM shall conform to all DSLEP-I Data Set Composition and Relationship Requirements when creating and transmitting an DSLEP-I as specified in table 5-65. DSLEPU-03 UM should send DSLEP-I messages that are valid with respect to all service management validation requirements for CM as defined in table. DSLEPU-04 UM shall validate that a received DSLEP-SR or DSLEP-FR conforms to all DSLEP-SR or DSLEP-FR syntactic validation requirements specified in table 5-60 or table 5-62, 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 Two- Phase Operation Procedures. DSLEPU-05 UM shall validate that a received DSLEP-SR or DSLEP-FR conforms to all DSLEP-SR or DSLEP-FR service management validation requirements specified in table 5-60 or table 5-62, 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 Two-Phase Operation Procedures. 5.7.3.2 CM Requirements for the DELETE_SPACE_LINK_EVENTS_PROFILE Operation Table 5-64: CM Requirements for the DSLEP Operation DSLEPC-01 CM shall conform to all Performer Requirements for Two-Phase Operation Procedures as specified in 3.4.1.6.2. DSLEPC-02 CM shall validate that a received DSLEP-I conforms to all DSLEP-I syntactic validation requirements specified in table 5-65, Data Set Composition and Relationship Requirements for the DSLEP-I. If the DSLEP-I fails any of the syntactic requirements, CM shall process the message set containing the syntactically invalid return in accordance with the Performer Requirements for Two-Phase Operation Procedures. DSLEPC-03 CM shall validate that the spaceLinkEventsProfileRef matches the spaceLinkEventsProfileId for a Space Link Events Profile within the context of the referenced Service Agreement. [service management validation] DSLEPC-04 CM shall validate that the spaceLinkEventsProfileRef identifies an Events Profile that has no pending or executing Service Packages referencing it. [service management validation] DSLEPC-05 CM shall validate that the sleSmCreatorName associated with the DSLEP-I is the same as the sleSmCreatorName of the events associated with the spaceLinkEventsProfileId referenced by the spaceLinkEventsProfileRef in the DSLEP-I. [service management validation] CCSDS 910.11-R-2 Page 5-65 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT DSLEPC-06 If the SLE Complex has locally defined DSLEP-I relationship requirements in addition to those specified in this Recommended Standard, CM shall validate that the DSLEP-I conforms to all such local requirements. [service management validation] DSLEPC-07 If the DSLEP-I is valid, CM shall a) delete the referenced SpaceLinkEventsProfile; b) remove the Events Profile as counting against the maxSpaceLinkEventsProfiles parameter of the Service Agreement; and c) and return a DSLEP-SR. [perform operation] DSLEPC-08 CM shall conform to all DSLEP-SR Data Set Composition and Relationship Requirements when creating and transmitting an DSLEP-SR as specified in table 5-60. DSLEPC-09 CM shall conform to all DSLEP-FR Data Set Composition and Relationship Requirements when creating and transmitting an DSLEP-FR as specified in table 5-62. 5.7.4 DeleteSpaceLinkEventsProfileInvocation MESSAGE (DSLEP-I) (UM CM) 5.7.4.1 General The DeleteSpaceLinkEventsProfileInvocation 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.2. Figure 5-18 is the message structure class diagram for the DSLEP-I message. AddSpaceLinkEventProfile- Invocation 1 1 SpaceLinkEventsProfileReference spaceLinkEventsProfileRef Figure 5-18: DSLEP-I Message Structure Class Diagram 5.7.4.2 Parameters The contents of the SpaceLinkEventsProfileReference data set are defined in table 5-58. CCSDS 910.11-R-2 Page 5-66 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:
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: DRAFT RECOMMENDED STANDARD FOR SPAC
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?