Space Link Extension - Service Management - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT NOTE – Submission of trajectory data occurs on the order of months, days or minutes in advance of the support period to which the trajectory data applies. b) DELETE_TRAJECTORY_PREDICTION (DTP)—to delete a Trajectory Prediction that currently resides at CM; c) QUERY_TRAJECTORY_PREDICTION (QTP)—to query the content of a Trajectory Prediction that resides at CM. No Trajectory Prediction operations can be performed by UM. 2.2.5.1 Storage Area at CM UM is responsible for managing the Trajectory Predictions resident at CM. UM must keep track of the expiration dates for the Trajectory Predictions and add and delete as necessary. CM will not notify UM when Trajectory Predictions resident at CM expire. There is a limited amount of storage space available at CM for Trajectory Predictions. The maximum allowed storage area is defined in the applicable Service Agreement. CM will reject new Trajectory Predictions once this storage space is exceeded. 2.2.5.2 Trajectory Prediction Validation When UM requests the addition of a new Trajectory Prediction, the validation performed by CM is limited, i.e., checking of storage space available at CM, sanity checking of time window, conformance to indicated format, uniqueness of Trajectory Prediction identifier. Further locally-defined checks may be performed by CM as part of the validation of a Service Package that references the Trajectory Prediction. Requests for deletion of Trajectory Predictions that are referenced by pending or executing Service Packages will be rejected. To allow UM to keep track of referenced Trajectory Predictions, the QUERY_TRAJECTORY_PREDICTION operation returns the list of pending or executing Service Packages that reference the queried Trajectory Prediction. 2.2.6 SERVICE AGREEMENT SERVICE The negotiation and generation of the Service Agreement are beyond the scope of this Recommended Standard. For this reason, there is only one Service Agreement operation that CM can perform when invoked by UM: QUERY_SERVICE_AGREEMENT (QSA)—to query the content of a Service Agreement that resides at CM. The QSA operation has been defined to support the return of Service Agreement data either in the format defined in this Recommended Standard or in a bilaterally agreed format. No Service Agreement operations can be performed by UM. CCSDS 910.11-R-2 Page 2-13 March 2008
DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT 2.3 MAPPING TO W3C XML SCHEMA The SLE-SM Recommended Standard is intended to be technology independent. However, it has been mapped to World Wide Web Consortium (W3C) Extensible Markup Language (XML) schema in order to support prototype implementations that have fed back useful information into the process of generating the Recommended Standard. The mapping of this Recommended Standard to XML schema is provided as a virtual annex at the following URL: [URL TBD] 2.4 SECURITY ASPECTS OF SLE MANAGEMENT SERVICES 2.4.1 SECURITY BACKGROUND/INTRODUCTION The SLE-SM services defined in this Recommended Standard are abstract and in themselves address some of the security concerns. Security of real implementations of the SLE-SM services also must depend on the security features associated the concrete transfer syntax used to represent the abstract data sets defined herein, and/or the security capabilities of the underlying communication service. At present, an SLE-SM mapping to World Wide Web Consortium (W3C) XML schema (reference [17]) has been adopted as one transfer syntax for SLE-SM interactions. For implementations that use this XML mapping, most of the security for the SLE-SM services will be provided by implementation of XML security standards (references [18]–[20]), which have been developed under the auspices of the W3C and the Organization for the Advancement of Structured Information Standards (OASIS). NOTE – For the purposes of this description, these XML security standards are assumed to be implemented in middleware that is part of the underlying communication service. 2.4.2 STATEMENTS OF SECURITY CONCERNS 2.4.2.1 Introduction This subsection identifies SLE-SM service support for capabilities that respond to security concerns in the areas of data privacy, data integrity, authentication, access control, availability of resources, and auditing. The support described herein is predicated on the use of the W3C XML schema mapping for SLE-SM and the referenced W3C XML security standards. SLE-SM operation messages are recommended to be fully encrypted in accordance with the XML Encryption Syntax and Processing recommendation (reference [18]). CCSDS 910.11-R-2 Page 2-14 March 2008
Page 2 and 3:
Draft Recommendation for Space Data
Page 4 and 5:
DRAFT RECOMMENDED STANDARD FOR SPAC
Page 6 and 7: DRAFT RECOMMENDED STANDARD FOR SPAC
Page 48 and 49: CCSDS 910.11-R-2 Page 2-5 March 200
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:
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?