Development of JAXAs SLE Gateway

1
Development of JAXAs SLE Gateway

• SpaceOps 2004
• May 17-21, 2004 Montreal, Canada
• Hideharu Nanba
• Ryo Suzuki
• Engineer, Consolidated Space Tracking and Data
  Acquisition Department
• Office of Space Flight and Operations
• Japan Aerospace Exploration Agency (JAXA)
• 2-1-1 Sengen, Tsukuba City, Ibaraki Pref.
  305-8505, Japan
• E-mail Nanba.Hideharu_at_jaxa.jp
• suzuki.ryo_at_jaxa.jp

2
Contents

• Introduction
• Service Outline
• System Aspects
• - Provider GW
• - User GW
• Schedule
• Future Study

3
Introduction (1/3)

• Background
• Under the Consolidation of Japanese Space
  Agencies, it was agreed to connect each others
  tracking ground stations network using the CCSDS
  Space Link Extension (SLE) protocol.
• Institute Space and Astronautical Science
  (ISAS)
• JAXA National Aerospace Laboratory of Japan
  (NAL)
• National Space Development Agency of Japan
  (NASDA)

4
Introduction (2/3)

• Concept of SLE implementation
• JAXAs internal protocols for the ground station
  interface
• - SDTP protocol used by former ISAS
• - H-II protocol used by former NASDA
• Two pairs of SLE Provider / User Gateways
  development
• - SLE Provider / User GW at Sagamihara (SLE?SDTP
  )
• - SLE Provider / User GW at Tsukuba (SLE?H-II)
• (This presentation shows the SLE Provider /
  User Gateways at Tsukuba.)
• After the development, these SLE Gateways will be
  also used for the Cross Support services with
  other agencies.

5
Introduction (3/3)
6
Service Outline (1/4)

• Supported Services (Provider GW / User GW)
• SLE Transfer Service for Telemetry and
  Telecommand over TCP/IP
• Return All Frame (RAF) and Forward CLTU (F-CLTU)
• based on the Blue Book
• RAF Timely Online Delivery Mode
• Offline Delivery Mode
• F-CLTU Online Delivery Mode

7
Service Outline (2/4)

• Interface Data (Provider GW / User GW)
• Implement the Heartbeat mechanism to monitor TCP
  connection
• Encode / Decode PDUs using ASN.1 BER
• Bind / Unbind operation expected from User side
• Peer Abort using TCP Urgent data
• Some PDUs are not implemented (See the tables)

8
Service Outline (3/4)
9
Service Outline (4/4)
10
System Aspects (1/18)

• Capability
• For Redundancy, Provider GW has Two machines.
• Three satellites can be supported simultaneously.
• Data rate capability
• Telemetry 32768 bps 2 Satellites
• 262144 bps 1 Satellite
• Telecommand 4000 bps 3 Satellites

11
System Aspects (2/18)
12
System Aspects (3/18)

• Support Configuration
• Basic support configuration
• 1 Satellite 1 Station 1 Provider GW 1 SLE
  User
• Redundant support configurations
• 1 Satellite 2 Stations 2 Provider GWs 2 SLE
  Users
• 1 Satellite 1 Station 2 Provider GWs 2 SLE
  Users
• 1 Satellite 1 Station 1 Provider GW 2 SLE
  Users

13
System Aspects (4/18)
14
System Aspects (5/18)
15
System Aspects (6/18)
16
System Aspects (7/18)

• Operation Outline
• Provider GW has Two operation modes
• - Manual Operation
• - Automatic Operation
• based on the GN Plan (operation schedule)
  provided by
• Ground Network Planning system (GNP)

17
System Aspects (8/18)

• Operation Interface
• 1) Configuration ID (a set of configuration
  parameters)
• defined in the Interface Control Document
  (ICD), and
• set to the ground stations.
• 2) Orbital information
• provided for the antenna predictions
• 3) Pass assignment request
• including Station, Times, Configuration ID,
  etc.
• 4) Real-time operation via SLE Provider GW

18
System Aspects (9/18)
19
System Aspects (10/18)

• Capability
• For Redundancy, User GW has Two machines.
• Three satellites can be supported simultaneously.
• Data rate capability
• Telemetry 40000 bps 3 Satellites
• Telecommand 2000 bps 3 Satellites

20
System Aspects (11/18)
21
System Aspects (12/18)

• Supported Configuration
• Basic supported configuration
• 1 Satellite 1 Station (SLE Provider) 1 User
  GW 1 Mission Control
• Redundant supported configurations
• 1 Satellite 2 Stations (SLE Providers) 2 User
  GWs 2 Mission Controls
• 1 Satellite 1 Station (SLE Provider) 2 User
  GWs 2 Mission Controls
• 1 Satellite 1 Station (SLE Provider) 1 User
  GW 2 Mission Controls

22
System Aspects (13/18)
23
System Aspects (14/18)
24
System Aspects (15/18)
25
System Aspects (16/18)

• Operation Outline
• User GW has Two operation modes
• - Manual Operation
• - Automatic Operation
• based on the operation schedule which is set
  by operator

26
System Aspects (17/18)

• Operation Interface
• 1) Configuration parameters
• described in the Interface Control Document
  (ICD)
• 2) Orbital information
• provided for the antenna predictions
• 3) Pass assignment request
• including Station, Times, etc.
• 4) Real-time operation via SLE User GW

27
System Aspects (18/18)
28
Schedule (1/2)
29
Schedule (2/2)

• Target Satellite
• Provider GW will be used for
• - SOLAR-B (will be launch in Aug.-Sep., 2006)
• for LEOP Operation and Emergency Situation
• User GW will be used for
• - DRTS (was launched in Sep. 10, 2002)
• for Emergency Situation

30
Future Study

• Future Study (Provider GW / User GW)
• Implementation of the Return Channel Frame (RCF)
  ?
• Service Management in XML file format ?