Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT twoPhaseOperationProcedurePatternActivity {UM, CM, DTP-I, DTP-SR, DTP-FR, dtpRoutineTimeout, dtpUrgentTimeout} 6.4.3 REQUIREMENTS 6.4.3.1 UM Requirements for the DELETE_TRAJECTORY_PREDICTION Operation Table 6-16: UM Requirements for the DTP Operation DTPU-01 UM shall conform to all Invoker Requirements for Two-Phase Operation Procedures as specified in 3.4.1.6.1. DTPU-02 UM shall conform to all DTP-I Data Set Composition and Relationship Requirements when creating and transmitting a DTP-I as specified in table 6-18. DTPU-03 UM should send DTP-I messages that are valid with respect to all service management validation requirements for CM as defined in table 6-17. DTPU-04 UM shall validate that a received DTP-SR or DTP-FR conforms to all DTP-SR or DTP-FR syntactic validation requirements specified in table 6-19 and table 6-21, 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. DTPU-05 UM shall validate that a received DTP-SR or DTP-FR conforms to all DTP-SR or DTP-FR service management validation requirements specified in table 6-19 and table 6-21, 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. 6.4.3.2 CM Requirements for the DELETE_TRAJECTORY_PREDICTION Operation Table 6-17: CM Requirements for the DTP Operation DTPC-01 DTPC-02 DTPC-03 DTPC-04 CM shall conform to all Performer Requirements for Two-Phase Operation Procedures as specified in 3.4.1.6.2. CM shall conform to all DTP-SR and DTP-FR Data Set Composition and Relationship Requirements when creating and transmitting a DTP-SR and DTP-FR, as specified in table 6-19 and table 6-21, respectively. CM shall validate that a received DTP-I conforms to all DTP-I syntactic validation requirements specified in table 6-18, Data Set Composition and Relationship Requirements for the DTP-I. If the DTP-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 Two-Phase Operation Procedures. CM shall validate that the DTP-I conforms to all DTP-I service management validation requirements specified in this table and table 6-18, Data Set Composition and Relationship Requirements for the DTP- I. If the DTP-I fails any of the service management requirements, CM shall cease processing the DTP- I and respond to UM with an DTP-FR message. The content of the DTP-FR depends on the nature of the validation failure, and is specified in table 6-20. CCSDS 910.11-R-2 Page 6-14 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT DTPC-05 CM shall validate that the sleSmCreatorName associated with the DTP-I is the same as the sleSmCreatorName of the Trajectory Prediction associated with the trajectoryId referenced by the trajectoryRef in the DTP-I. [service management validation] DTPC-06 CM shall validate that each DTP-I parameter that is constrained by a Service Agreement parameter is consistent with the applicable Service Agreement parameter. [service management validation] DTPC-07 If the SLE Complex has locally defined DTP-I relationship requirements in addition to those specified in this standard, CM shall validate that the DTP-I conforms to all such local requirements. [service management validation] DTPC-08 If the Trajectory Prediction being deleted is referenced by pending or executing Service Packages, CM shall reject the DTP-I and send a DTP-FR. [service management validation] DTPC-09 If the DTP-I passes syntactic and service management validation, CM shall: a) delete the referenced Trajectory Prediction; b) remove the Trajectory Prediction as applying against the maxSizeTrajectoryFilestore parameter of the Service Agreement; and c) return a DTP-SR message. [perform operation] 6.4.4 DeleteTrajectoryPredictionInvocation (DTP-I) MESSAGE (UM CM) 6.4.4.1 General The DeleteTrajectoryPredictionInvocation (DTP-I) 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 6-5 shows the message structure of the DTP-I as a class diagram. Figure 6-5: DTP-I Message Structure, presented in a Class Diagram 6.4.4.2 Parameters The TrajectoryPredictionReference data set is defined in table 6-11. 6.4.4.3 Data Set Composition and Relationship Requirements Table 6-18 defines the data set composition and relationship requirements for the DTP-I message. CCSDS 910.11-R-2 Page 6-15 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:
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: DRAFT RECOMMENDED STANDARD FOR SPAC
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?