Global Science & Technology

ITC 2003Las Vegas, NV USA

22 October 2003

CCSDS Space Link Extension Service Management Standards

and Prototyping Activities

John PietrasGlobal Science and Technology, Inc.

222 October 2003

Outline

• Background and motivation for Space Link Extension (SLE) Service Management (SM)

• SLE-SM context• CCSDS SLE-SM specification overview• International prototyping efforts: status and plans

322 October 2003

Background and Motivation

• Creation of SLE data transfer services Need to manage the configuration of those services

• Standard management of standard SLE services as alternative to ad hoc management methods

• “While we’re at it”, address long-standing lack of standards for TT&C service management (e.g., scheduling)

422 October 2003

SLE-SM Context

Complex Management Utilization Management

Mission Data Operations SystemTT&C/SLE Complex

Mission Spacecraft

Instruments

RF and Data Subsystem

RF SLETransferServiceProvision

SLE Transfer Service Users

Spacecraft command and telemetry data over SLE transfer servicesSpacecraft command and telemetry data over other (non-SLE) communication pathsService management transactionsComplex-internal equipment control and monitoringMDOS-internal coordination

522 October 2003

Utilization Management and Complex Management Roles

• Utilization Management (UM)– The function(s) within spaceflight mission management that are

responsible for acquiring and operating TT&C and SLE service on behalf of the mission

• Complex Management (CM)– The function(s) of the Complex that are responsible for:

» Establishing the TT&C/SLE service relationship with the mission

» Negotiating length and levels of service (service agreement)» Responding to service requests for individual contacts» Responding to requests to change service configuration» Responding to requests for service status information» Issuing service status reports» Translating and actuating the service requests on the

Complex’s resources, and collecting status from those resources to synthesize service status

622 October 2003

CCSDS SLE-SM Resource Model

Forward Space Link Carrier

0.. n

Return Space Link Carrier

0.. m

antenna

ForwardSymbol Stream

Forward Link Protocol Processing

Forward CLTUTransfer Service

ReturnSymbol Stream

Return Link Protocol Processing

Return RAFTransfer Service

1.. 2Return RCF

Transfer Service

0.. y

0.. z

RF and modulation baseband bitstream space link data units

722 October 2003

SLE-SM Specification Overview

• Focus on the interface by which UM requests services for individual contacts (service request subset of SLE-SM)*

– SLE-SM information model– SLE-SM transactions

• Representation of the associated management information in eXtensible Markup Language (XML) schema

*Other UM-CM interactions are potential topics of future standardization

822 October 2003

SLE-SM Information Model:Service Agreement

• Long-lived (conceptual) repository of rules and constraints against which configuration profiles and service requests can be validated

– Frequency ranges– Possible modulations– Possible coding options– Maximum number of type

XXX data transfer service instances

– Possible transfer service delivery modes

– Etc.• Provides an “namespace” for

interactions between UM and CM

Service Agreement

922 October 2003

SLE-SM Information Model:Carrier Configuration Profile

• Parameter values for a single RF carrier configuration

– Forward or return– Modulation

» Number of symbol streams– Frequency– Coding– Etc.

• Contains one or more transfer service profiles per symbol stream

• Must be valid with respect to the Service Agreement

• Multiple configuration profiles may exist for a Service Agreement

Service Agreement

CarrierConfiguration

Profile

1..n

1022 October 2003

SLE-SM Information Model:Trajectory Data

• Predictive information used to derive pointing angles and Doppler compensation

• Time-dependent• Multiple predictive data sets

may exist for the same time– E.g., launch/maneuver

contingencies• Stable state vectors

– CCSDS Orbit Parameter Message (OPM)

• Ephemeris– CCSDS Ephemeris Parameter

Message (EPM)

Service Agreement

CarrierConfiguration

Profile

1..n

TrajectoryData

1..n

1122 October 2003

SLE-SM Information Model:Service Request

• Request for TT&C and SLE services for a specific period of time (contact, pass)

• Composed of references to (multiple) existing carrier and transfer service configuration profiles

– Specifies preferred start and stop times for each RF carrier, plus acceptable lag and lead times

• May include multiple scenarios

– Alternate sets of carrier configurations that may be invoked on short notice

• References an existing trajectory data file

• Must be valid with respect to the Service Agreement

Service Agreement

CarrierConfiguration

Profile

1..n

TrajectoryData

1..n

Service Request

1..n

1..n

1..n 1..n

1222 October 2003

SLE-SM Information Model:Referencing Framework

serviceAgreementRef

spaceLinkCarrierCharDataSetRef

xxxProdCharDataSetRef

Carrier Config Profile

carrierProfileRef

Transfer Service InstancetransferServiceConfigProfileRef

Transfer Service Instance

transferServiceConfigProfileRef

Carrier Instance

.

.

Service Request

Scenario

Scenario

Carrier Instance

Carrier Config Profile

.

.

Service AgreementserviceAgreementRef.

Space Link Carrierand Symbol Stream

Characteristics

Protocol Processing and Transfer Service

Characteristics

Transfer Service Config Profile

Carrier Config Profile

Transfer Service Config Profile

Transfer Service Config Profile

Transfer Service Config Profile

1322 October 2003

Service Request Transactions(1 of 2)

• Service Request– New service request

» Result: acknowledged, accepted, or rejected– Replace service request

» Only replaces in-place request if success is guaranteed» Makes possible incremental scheduling of resources» Result: acknowledged, accepted, or rejected

– Delete service request» Result: acknowledged, deleted, or deletion failed

– Invoke alternate scenario» Result: successful or failed

– Query service request» Result: successful or failed

1422 October 2003

Service Request Transactions (2 of 2)

• Configuration Profile– New configuration profile– Delete configuration profile– Query configuration profile

• Trajectory– New trajectory– Replace trajectory– Delete trajectory

• Service Agreement– Query service agreement

1522 October 2003

Extending SLE-SM Service Request Framework

• SLE-SM standard is currently “CCSDS centric”• Extension points for management of non-CCSDS standard

services– Plug in additional or replacement types for components of the

resource model• Adaptation of the referencing framework to allow hybrid

standard/legacy implementations– Use of legacy aspects subject to bilateral agreeements

1622 October 2003

SLE SM Prototyping Activities

• Round 1 – Stand-alone prototype implementations– 2000 – Spring 2003– Developed against previous SLE-SM specifications and early

draft schema– Local extensions/modifications/interpretations of standards

needed to bring prototypes to fruition– The prototypes have provided valuable feedback to the

evolution of the SLE-SM concepts, requirements, and schema• Round 2 – Interoperability among the prototypes

– Late fall 2003 – CY2004– Different development teams creating prototype UM and CM

implementations against a common subset of “stable” draft version (V0.1.2) of SLE-SM XML schema

1722 October 2003

Provider UserSLE Interface

BNSC/Vega SLE-SM Prototype

UtilisationManager

(web browser)

(HTTP - download applet)

ComplexManager

(TCP/IP)

web server

XML files handler(servlet)

HTML pages(web browser)

(HTTP)

(RMI -TCP/IP)

antennapointing

file(HTTP upload)

antennapointing

file

User Transportconfiguration file

User Transportconfiguration file

configuration filesfor Ground Stationresources (HTTP download)

(TCP/IP)Ground

Station

Equipment

Control

Centre

EquipmentCLTUsCLTUs

Frames Frames

SLE-APIRAF Provider

F-CLTU ProviderSLE-API

RAF User

F-CLTU User

(TCP/IP)

XMLfilesXML

filesXMLfilesXML

files

Database (JDBC)

Graphic courtesy of Paula Quintela of Vega Group plcFor more information contact Paula (Paula.Quintela@vega.co.uk)

1822 October 2003

Sequencing

Trajectory

SLE Config

DSMSGroundSystems

DSMSServiceManagementSystem

Oracle 9i

ServiceRequestTracking,Mgmt

XSLTTrans-formationsCCSDS

StandardSLE SM ServiceRequests

Scheduling

DSMSServiceManagementSystem

DSMSGroundSystems

P R O T O T Y P E S Y S T E MCSSXP Prototype System Scheduling

Sequencing

Trajectory

SLE Config

Scheduling

Sequencing

Trajectory

SLE Config

1st Order Test: Equivalent Inputs. 2nd Order Test: Shadow track Mission.

NASA/Jet Propulsion Laboratory (JPL) CCSDS SLE SM XML Prototype (CSSXP)

Graphic courtesy of Erik Barkley of JPLFor more information, contact Erik.J.Barkley@jpl.nasa.gov

L E G A C Y S Y S T E M

1922 October 2003

TCP/IP

ServiceRequest

Data

UserInput

User Interface / DataCapture Web Pages

Oracle 9i- Stored Configuration Profiles- XML Document Processing- User data- Error Checking

Web Server / SOAP

Send XML Config

Profiles and Svc

RequestsHTML

FormattedResponses

Receive XMLService

Responses XML Processing - JAVA / DOM / StoredProcedures

Service Request Processing – Stored Procedures

ConfigProfileTables

ServiceRequest

Tables

AvailableServiceTables

ServiceRequest

ResponseXML

TCP/IP

Web Services - SOAP

SLE XML Documents

Oracle 9i Database

User Interface - HTML

TCP/IP

Utilization Management Complex Management

User Workstation

- COTS Communications and Web Services

- SLE SM Prototype Developed Software

- COTS client and server platforms

- CCSDS P3 Defined XML Data Formats

- Oracle 9i Relational Database

TCP/IP Network

NASA Consolidated Space Operations Contract (CSOC)/Lockheed Martin SLE Management Prototype

Graphic courtesy of Andy Schreckenghost of Lockheed –Martin

For more information contact Lindolfo Martinez of Lockheed-Martin (Lindolfo.Martinez@csoconline.com)

2022 October 2003

UmConsole(Java/JAXB)

Email client

CERES SOCColorado Springs, CO

Email client & CmConsole(Java/JAXB)

Wallops Flight FacilityWallops Island, VA

Internet Service Request and Response

XML files

WFF Sched/Mgmt system(s)

Email client & CmConsole

DataLynx Ops CenterColumbia, MD

JHU APL

DataLynx Sched/Mgmt system

Service Request and Response XML file email attachments

Air Force Satellite Control Network (AFSCN)/GST Interoperability Project Phase 3 SM Prototype

Global Science & Technology

For more information contact John Pietras (pietras@gst.com)

2122 October 2003

GST

QinetiQ, RALGS

RosettaSOC

HayabusaSOC

Round 2: SLE-SM Prototype Interoperability Tests

Complex Manager (CM) [Ground Station (Network)] Interoperability tests currently being plannedUtilization Management (UM) [SOC] Tentative and/or candidate interoperability tests

JPL DSN

2222 October 2003

AFSCN/GST UM – JPL DSN CM

• Purpose– Demonstrate interoperability of independently-developed

implementations of SLE-SM standards– Expose unforeseen implementation dependencies

• GUI UM application generates New Service Request, Replace Service Request, Delete Service Request, Invoke Alternate Scenario, and Query Service Request invocations

• JPL CM application receives and validates service requests, generate DSN support products, and generates XML responses to invocations

• Configuration profile instance documents generated by hand to enable validation of service requests

• Messages exchanged as text attachments to email messages

• Interoperability tests to begin in November 2003• Possible future enhancements

– On-line email access– SOAP over SMTP– UM generation of configuration profiles

2322 October 2003

JAXA Hayabusa UM – JPL DSN CM

• Purpose – Validate JPL DSN SLE-SM prototype processes in the context of an

operational spacecraft» Japan Aerospace Exploration Agency (JAXA) Hayabusa (formerly Muses-C),

launched in May 2003– Expose SLE-SM to ISAS/Hayabusa mission operators for insight and

feedback• Hayabusa mission operators generate SLE-SM-compliant XML

representations of real operational requests for DSN support– These may be generated by hand, or perhaps by a prototype UM

application– Transferred using SMTP

• JPL DSN CM prototype validates service requests, generates DSN support products, and generates XML responses to invocations

• JPL and Hayabusa personnel compare operational and prototype support products to validate correctness of support products generated by prototype

• Testing with Hayabusa-generated messages to begin November 2003

2422 October 2003

European Space Agency (ESA)/Vega UM – JPL DSN CM (Tentative)

• ESA funding of Vega development of UM currently in negotiation

• Purpose– Prototype UM application for possible use in support of future

ESA missions» ESA Rosetta is the prime candidate

– Expose SLE-SM to ESA mission managers and operations community for insight and feedback

• ESA/Vega UM generates service requests for JPL DSN support

– Exact catalog of SLE-SM interactions to be supported still under consideration

• JPL DSN CM prototype validates service requests, generates DSN support products, and generates XML responses to invocations

• SLE-SM products and process evaluated by ESA mission managers and operators

• Interoperability testing could begin sometime after April 2004

• Shadow-mode testing using Rosetta would likely follow

2522 October 2003

GST UM – BNSC/Vega CM (Candidate)

• Could be executed in CY2004• Purpose

– Provide additional assurance through use of second CM implementation

• Replicate capabilities exercised in tests with JPL CM– Ensure global support of a common core set of capabilities

• Additional capabilities and applications TBD• Could involve QinetiQ, RAL, or both

2622 October 2003

Acknowledgements

• NASA (HQ) Data Systems Standards Office• Goddard Space Flight Center Data Systems Standards

Office• Jet Propulsion Laboratory Data Systems Standards Office• U.S. Air Force Space and Missile Systems Center

(SMC)/Range Network (RN)

• Erik Barkley, JPL• Andy Schreckenghost, Lockheed-Martin• Paula Quintela, Vega Group plc• Hugh Kelliher, Space ConneXions Limited

2722 October 2003

Backup Slides

2822 October 2003

British National Space Centre (BNSC)/Vega SLE-SM Prototype

• CM (provider-side) system is currently installed at QinetiQground station in West Freugh, UK– Based on earlier (pre-XML) SLE-SM managed object model– Web browser-based UM interface

• Vega is currently re-implementing CM system in compliance with latest-version SLE-SM XML schema V0.1.2– First release will receive and respond to service requests

» Service agreement and configuration profile information loaded locally

– To be installed at both the QinetiQ ground station and the Rutherford-Appleton Laboratory (RAL) ground station in Oxfordshire, UK

• For more information, contact Paula Quintela of Vega Group plc

– Paula.Quintela@vega.co.uk

2922 October 2003

NASA/Jet Propulsion Laboratory (JPL) CSSXP

• XML/SOAP/HTTP/SQL/JDBC/Oracle-based CM prototype provides SLE-SM front-end to existing Deep Space Network (DSN) TT&C scheduling and configuration system

• Combined prototype/legacy system ingests SLE-SM service requests, generates support products used by DSN, and generates SLE-SM responses

• No UM (user) prototype: service request and configuration profile XML instance documents generated by hand using XMLSpy

• For more information, contact Erik Barkley of JPL– Erik.J.Barkley@jpl.nasa.gov

3022 October 2003

SOAP/HTTP

Applet

Legend:CSSXP Java code

COTS/Public Domain Code

E-Mail Client

Requests

Responses

J2EE Server

JDBC/SQL

Oracle 9iW3C DOM

DB Utilities XML Utilities

Model Objects/Validation

Business Layer (Service Request Processor,Configuration Processor,Response Generation, etc.)

Servlets

EnterpriseBeans

JDBCConnectionPool

Requests

Responses

SMTP

NASA/Jet Propulsion Laboratory (JPL) SLE-SM Prototype

Graphic courtesy of Erik Barkley of JPL

3122 October 2003

NASA CSOC/LM SLE Management Prototype

• Complete CM and UM prototype applications based on web services (XML/SOAP/HTTP) communications combined with SQL/ODBC/Oracle database relational processing

• Web-based end user screens supported via Apache webserver and JSP on the UM server

• Testing completed for most SLE Management features using latest available XML schemas

• Standalone effort completed September 30, 2003– Products transitioned to GSFC engineering

• For more information please contact Lindolfo Martinez of Lockheed-Martin– Lindolfo.Martinez@csoconline.com

3222 October 2003

Air Force Satellite Control Network (AFSCN)/GST Interoperability Project Phase 3 SM Prototype

• Java-based SLE-SM applications developed to schedule contacts from Johns Hopkins University Applied Physics Lab (APL) and NASA GSFC WFF ground stations in support of AFSCN Interoperability Project Phase 3

– UM software installed at USAF Center for Research Support (CERES) SOC

– CM generation software installed at Honeywell DataLynxOperations Center (control point for APL ground station) and WFF

• Draft SLE-SM schema extended to support Phase 3-unique aspects

• No integration with operational systems– Short implementation time (~1.5 months)– Limited duration of Phase 3– Security isolation requirements

• For more information please contact John Pietras of GST– pietras@gst.com