Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 6.3.3 REQUIREMENTS 6.3.3.1 UM Requirements for the ADD_TRAJECTORY_PREDICTION Operation Table 6-2: UM Requirements for the ATP Operation ATPU-01 UM shall conform to all Invoker Requirements for Two-Phase Operation Procedures as specified in 3.4.1.6.1. ATPU-02 UM shall conform to all ATP-I Data Set Composition and Relationship Requirements when creating and transmitting an ATP-I as specified in table 6-10. ATPU-03 UM should submit ATP-I messages that are valid with respect to all service management validation requirements for CM as defined in table 6-3. ATPU-04 UM shall validate that a received ATP-SR or ATP-FR conforms to all ATP-SR or ATP-FR syntactic validation requirements specified in tables 6-13 and 6-15, 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. ATPU-05 UM shall validate that a received ATP-SR or ATP-FR conforms to all ATP-SR or ATP-FR service management validation requirements specified in tables 6-13 and 6-15, 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. ATPU-06 UM should provide Trajectory Prediction start and stop times consistent with the Service Packages that will be referencing this Trajectory Prediction. Consistent times mean the following relationship is true: Trajectory Prediction start time < earliest Service Scenario start time < latest Service Scenario stop time < Trajectory Prediction stop time. 6.3.3.2 CM Requirements for the ADD_TRAJECTORY_PREDICTION Operation Table 6-3: CM Requirements for the ATP Operation ATPC-01 ATPC-02 ATPC-03 ATPC-04 ATPC-05 CM shall conform to Performer Requirements for Two-Phase Operation Procedures as specified in 3.4.1.6.2. CM shall conform to all ATP-SR and ATP-FR Data Set Composition and Relationship Requirements when creating and transmitting a ATP-SR and ATP-FR, as specified in tables 6-13 and 6-15, respectively. CM shall validate that a received ATP-I conforms to all ATP-I syntactic validation requirements specified in this table and table 6-10, Data Set Composition and Relationship Requirements for the ATP- I. If the ATP-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 ATP-I conforms to all ATP-I service management validation requirements specified in table 6-10, Data Set Composition and Relationship Requirements for the ATP-I. If the ATP-I fails any of the service management requirements, CM shall cease processing the ATP-I and respond to UM with an ATP-FR message. The content of the ATP-FR depends on the nature of the validation failure, and is specified in table 6-14. CM shall validate that the ATP-I would not cause the storage area at CM reserved for Trajectory Predictions to exceed maxSizeTrajectoryFilestore for the referenced Service Agreement. [service management validation] CCSDS 910.11-R-2 Page 6-4 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT ATPC-06 ATPC-07 ATPC-08 ATPC-09 ATPC-10 ATPC-11 ATPC-12 ATPC-13 ATPC-14 CM shall validate that each ATP-I parameter that is constrained by a Service Agreement parameter is consistent with the applicable Service Agreement parameter. [service management validation] CM shall validate that all ATP-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] If the SLE Complex has locally defined ATP-I relationship requirements in addition to those specified in this standard, CM shall validate that the ATP-I conforms to all such local requirements. [service management validation] If the OrbitParameterMessageText data set is used in the ATP-I, then CM shall validate that the contents of parameter opmTextData meet any data composition and relationship requirements defined for the Orbit Parameter Message (OPM) in the CCSDS Recommended Standard for Orbit Data Messages (ODM) (reference [14]). [service management validation] If the OrbitParameterMessageXml data set is used in the ATP-I, then CM shall validate that the contents of parameter opmXmlData meet any data composition and relationship requirements defined for the Orbit Parameter Message (OPM) in the CCSDS Recommended Standard for Orbit Data Messages (ODM) (references [14] and [16]). [service management validation] If the OrbitEphemerisMessageText data set is used in the ATP-I, then CM shall validate that the contents of parameter oemTextData meet any data composition and relationship requirements defined for the Orbit Ephemeris Message (OEM) in the CCSDS Recommended Standard for Orbit Data Messages (ODM) (reference [14]). [service management validation] If the OrbitEphemerisMessageXml data set is used in the ATP-I, then CM shall validate that the contents of parameter oemXmlData meet any data composition and relationship requirements defined for the Orbit Ephemeris Message (OEM) in the CCSDS Recommended Standard for Orbit Data Messages (ODM) (references [14] and [16]). [service management validation] If the OrbitBilateralMessage data set is used in the ATP-I, then CM shall validate that the OrbitBilateralMessage data set composition and relationship requirements for the format indicated by parameter bilateralTrajectoryFormatId are met. [service management validation] If the ATP-I passes syntactic and service management validation, CM shall: a) add the Trajectory Prediction to the set of Trajectory Predictions resident at CM; b) count the Trajectory Prediction as applying against the maxSizeTrajectoryFilestore parameter of the Service Agreement; and c) return an ATP-SR message. [perform operation] 6.3.4 AddTrajectoryPredictionInvocation (ATP-I) MESSAGE (UM CM) 6.3.4.1 General The AddTrajectoryPredictionInvocation (ATP-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-2 shows the ATP-I message structure as a class diagram. CCSDS 910.11-R-2 Page 6-5 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: DRAFT RECOMMENDED STANDARD FOR SPAC
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?