Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 3.3.3.2 Receiver Requirements for the SLE-SM Document Exchange Protocol Table 3-2: Receiver Requirements for the SLE-SM Document Exchange Protocol MPR-0001 The Receiver shall validate that any document received on the message set port conforms to all SleSmMessageSet syntactic validation requirements specified in table 3-4, Data Set Composition and Relationship Requirements for SleSmMessageSet Documents). If the document fails any of the syntactic requirements, the Receiver shall deem the document to be invalid, discard the document, and send an UnrecognizedMessageSetResponse to the exception response port of the Sender. The Receiver is not required to further interpret or act upon the invalid document. [syntactic validation] MPR-0002 If the sleSmCreatorName (table 3-3) is not known to the Receiver as a legitimate creator of SLE-SM message sets, the Receiver shall deem the message set to be invalid, discard the message set, and send an UnrecognizedMessageSetResponse to the exception response port of the Sender. The Receiver is not required to further interpret or act upon the invalid message set. [Authorization validation] MPR-0003 If the serviceAgreementRef (table 3-3) references a Service Agreement that is not supported by the Receiver, the Receiver shall deem the message set to be invalid, discard the message set, and send an UnrecognizedMessageSetResponse to the exception response port of the Sender. The Receiver is not required to further interpret or act upon the invalid message set. [Authorization validation] MPR-0004 If the sleSmCreatorName is not authorized in the context of the referenced Service Agreement, the Receiver shall deem the message set to be invalid, discard the message set, and send an UnrecognizedMessageSetResponse to the exception response port of the Sender. The Receiver is not required to further interpret or act upon the invalid message set. [Authorization validation] MPR-0005 If the communication-service-provided Source identification associated with the Message Set is not authorized to send Message Sets using the sleSmCreatorName in the context of the referenced Service Agreement, the Receiver shall deem the message set to be invalid, discard the message set, and send an UnrecognizedMessageSetResponse to the exception response port of the Sender. The Receiver is not required to further interpret or act upon the invalid message set. [Authorization validation] MPR-0006 If the messageSequenceNumber (table 3-5) of any invocation message in a message set is not greater than the messageSequenceNumber of all valid invocation messages received in previous message sets with that sleSmCreatorName and serviceAgreementRef, the Receiver shall deem each such message invalid and shall send an InvalidMessageResponse to the exception response port of the Sender. The Receiver is not required to further interpret or act upon the invalid invocation message, and the messageSequenceNumber of the invalid invocation message shall not be used to determine sequence integrity of subsequent invocation messages. [Sequence validation] MPR-0007 If the messageSequenceNumbers of two or more invocation messages in a message set are the same, the Receiver shall deem the same-numbered messages that appear after the first such instance to be invalid, and for each such invalid message shall send an InvalidMessageResponse (3.3.4.4) to the exception response port of the Sender. The Receiver is not required to further interpret or act upon the invalid invocation message. [Sequence validation] CCSDS 910.11-R-2 Page 3-15 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT MPR-0008 If an invocation message is received for an operation that is not supported under the referenced Service Agreement, the Receiver shall send an InvalidMessageResponse to the exception response port of the Sender. The Receiver is not required to further interpret or act upon the invalid message. [Supported operation validation] MPR-0009 If a notification message is received that is not supported under the referenced Service Agreement, the Receiver shall send an InvalidMessageResponse to the exception response port of the Sender. The Receiver is not required to further interpret or act upon the invalid message. [Supported operation validation] MPR-0010 If a return or confirmation message is received for an operation/notification that is not supported under the referenced Service Agreement, the Receiver shall deem the message invalid. The Receiver is not required to further interpret or act upon the invalid message. [Supported operation validation] MPR-0011 The Receiver shall process multiple invocation messages in a message set in messageSequenceNumber order. MPR-0012 The Receiver should increment the messageSequenceNumber values of InvalidMessageResponses in the order that the messages are generated, with respect to the same sleSmCreatorName and serviceAgreementRef. 3.3.4 SLE-SM DOCUMENTS 3.3.4.1 General The abstract SleSmDocument data set is the basis for all documents that are exchanged between UM and CM via the SLE-SM document exchange protocol. There are two concrete data sets that inherit the parameters of the SleSmDocument data set, the SleSmMessageSet data set and the SleSmExceptionResponse data set. The SleSmMessageSet data set is specified in 3.3.4.2. The SleSmExceptionResponse data set is specified in 3.3.4.4. 3.3.4.2 SleSmMessageSet 3.3.4.2.1 General The class diagram for the SleSmMessageSet message structure is shown in figure 3-8. CCSDS 910.11-R-2 Page 3-16 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: DRAFT RECOMMENDED STANDARD FOR SPAC
Page 48 and 49: CCSDS 910.11-R-2 Page 2-5 March 200
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:
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

Create successful ePaper yourself

Delete template?

Save as template?