Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT state machine Trajectory Prediction QTP_I / QTP_SR ATP_I Available H* trajectory prediction successfully added? DTP_I [not owned] / DTP_FR reference added DTP_I / DTP_FR [yes] / ATP_SR Unreferenced Referenced [no] / ATP_FR DTP_I [owned] / DTP_SR last reference removed Figure 6-1: State Diagram for Trajectory Prediction Table 6-1: State Table for Trajectory Prediction Information Entity States Available Events Initial Acknowledged Unreferenced Referenced ATP-I [successfully added] SR -> Unreferenced [else] FR -> Final * * * ATP-I * * [owned] SR -> Final FR * * [else] FR QTP-I * * SR reference added * * -> Referenced last ref removed * * * -> Unreferenced The State Machine trajectory prediction lifecycle conforms to the state machine shown, with reference criteria as described in DTPC-08. 6.2 OWNERSHIP OF TRAJECTORY PREDICTIONS Each trajectory prediction is owned by the UM entity associated with the sleSmCreatorName used in the SleSmMessageSet that contained the invocation message that created the trajectory prediction. <strong>CCSDS</strong> 910.11-R-2 Page 6-2 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 6.3 ADD_TRAJECTORY_PREDICTION (ATP) OPERATION 6.3.1 PURPOSE The ADD_TRAJECTORY_PREDICTION (ATP) operation allows UM to add a new Trajectory Prediction at CM. 6.3.2 PROCEDURE The procedure for the ATP operation is that for a two-phase operation procedure, which follows the two-phase operation procedure pattern specified in 3.4.1.2. The ATP operation involves the exchange of the following messages: – AddTrajectoryPredictionInvocation (ATP-I); – AddTrajectoryPredictionSuccessfulReturn (ATP-SR); – AddTrajectoryPredictionFailedReturn (ATP-FR). The message sequence diagram for the ADD_TRAJECTORY_PREDICTION operation conforms to the stereotyped sequence diagram for the two-phase operation messaging pattern defined in 3.4.1.3, with the following argument list: twoPhaseOperationProcedurePatternSequence {UM, CM, ATP-I, ATP-SR, ATP-FR} The activity diagram for the ADD_TRAJECTORY_PREDICTION operation conforms to the stereotyped activity diagram for the two-phase operation procedure pattern defined in 3.4.1.5, with the following argument list: twoPhaseOperationProcedurePatternActivity {UM, CM, ATP-I, ATP-SR, ATP-FR, atpRoutineTimeout, atpUrgentTimeout} <strong>CCSDS</strong> 910.11-R-2 Page 6-3 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: DRAFT RECOMMENDED STANDARD FOR SPAC
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?