Attachment Q GRDDP 418 XO RPT 0039 Version 1.00.pdf

Effective Date: January 19, 2022 418-XO-RPT-0039 Expiration Date: Five years from date of last signature Baseline Version 1.0 Responsible Organization: GeoXO Flight Project/Code 418

Geostationary Operational Environmental Satellite

(GOES)

Reliable Data Delivery Protocol (GRDDP) Signature page

Prepared by:

Electronically approved by:

Michael A. Roza Date GeoXO Flight Project, Systems Engineer NASA GSFC, Code 418

Reviewed by:

Electronically approved by: 01/10/2022

Steven W. Bidwell Date GeoXO Flight Project, Mission Systems Engineer NASA GSFC, Code 599

Approved by:

Electronically approved by Monica Todirita for: 01/18/2022

Jason H. Hair Date GeoXO Flight Project, Project Manager NASA GSFC, Code 418

01/20/2022

/GeoXO Flight Project Systems Engineering

GRDDP

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol (GRDDP)

Version: 1.0 Printed by: rkhoover Printed on: Friday, January 21, 2022

No filter applied.

No sort applied.

Generated from DOORS 9.7.2.4

Contents

1 1Introduction

1.1 1Scope

1.2 1Requirements Terminology

2 2Reference Document

3 3Definitions

4 4Overall Functional Description

4.1 4Multiplexed Logical Channels

4.1.1 4Channel Independence

4.1.2 4Transmit Priority

4.1.3 4Data Transmit Queue

4.1.4 4Urgent Message Transmit Queue

4.2 4Reliable Delivery

4.2.1 4Error Detection

4.2.2 4Packet Sequence Numbers

4.2.3 4Sequence Number Use

4.2.4 5Acknowledgement and Retransmit

4.2.5 5Retransmission

5 6Packet Format

5.1 6Header

5.1.1 6Destination Address

5.1.2 6Protocol ID

5.1.3 6Source Address

5.1.4 6Packet Control

5.1.4.1 6User Defined Bits

5.1.4.2 6Packet Type

5.1.5 7Application Payload Length MSB

5.1.6 7Application Payload Length LSB

5.1.7 7Channel Number

5.1.8 7Sequence Number

5.2 7Application Payload

5.2.1 7Data Packets and Urgent Messages

5.2.2 7Acknowledge and Reset Packets

Project: GeoXO Flight Project Systems Engineering Module: GRDDP Baseline Version: 1.0

Contents ii

5.3 7Trailer

5.3.1 8CRC Preset

6 9Transport Channel Definition

6.1 9TEP Parameters

6.2 9TEP States

7 10Channel Operations

7.1 10Logical Connections

7.2 10Reset Command

7.2.1 10Reset Timer Cancellation

7.2.2 10Reset Timer Expiration

7.3 10Transport Channel Connection

7.4 10Receive TEP Operations

7.4.1 10Sliding Window

7.4.2 10Sliding Window Range

7.4.3 10Window Advance

7.4.4 10Packet Acknowledgement

7.4.5 11Packets with Errors

7.4.6 11Out of Window Sequence Number

7.4.7 11Duplicate Sequence Number

7.4.8 11Urgent Message Acknowledgement

7.4.9 11Urgent Message Delivery Order

7.4.10 11Urgent Message Delivery Priority

7.4.11 11Reset Command Sequence Number

7.4.12 11Reset Command Processing

7.4.13 11Packets Pending Delivery

7.4.14 11Reset Command Report

7.5 11Transmit TEP Operations

7.5.1 11Transmit TEP ACKs

7.5.2 12Transmit TEP Sequence Number Allocation

7.5.3 12Reset Command Sequence Number

7.5.4 12Transmit Window

7.5.5 12Unacknowledged Packets

7.5.6 12Transmit Window Start

7.5.7 12Transmit Window Advance

7.5.8 12Packet Retransmit

7.5.9 12Retry Reset

7.5.10 12Timeout Start

Contents iii

7.5.11 12Urgent Message Transmission

8 13Acronyms

Contents iv

Page 1 of 13 Printed Friday, January 21, 2022

ID

GRDDP1

GRDDP2

GRDDP3

GRDDP4

GRDDP5

GRDDP6

GRDDP7

Object Number

1.0-1

1.1

1.1.0-1

1.1.0-2

1.2

1.2.0-1

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

1 Introduction The GeoXO spacecraft uses European Cooperation for Space Standardization (ECSS) SpaceWire for the transfer of sensor, telemetry, and command data between instruments and the spacecraft. The GeoXO Program has directed that all data transferred over SpaceWire implement a reliable data delivery protocol. The SpaceWire Standard does not specify a protocol for reliable data delivery. It is the purpose of this document to specify a reliable data delivery protocol for the GeoXO spacecraft and instruments.

1.1 Scope

The Reliable Data Delivery Protocol uses the lower level SpaceWire data link layer to provide reliable packet delivery services to one or more higher level host application processes.

This document specifies the functional requirements for the Reliable Data Delivery Protocol service. This document does not specify the interfaces to the lower or higher level processes, which may be implementation dependent.

1.2 Requirements Terminology

The following requirements terminology is used throughout this document:

The use of “shall” designates a requirement that must be met.

The use of “will” designates a statement of fact or intention of the government.

The use of “may” designates that permission has been granted by the government.

The term “(TBD)” means, “to be determined” and is used when no value is available with subsequent study needed to obtain it.

The term “(TBR)” means “to be refined/reviewed” for a value that is subject to review for appropriateness and is subject to revision. The vendor is liable for compliance with the information marked “TBR” as if the “TBR” notation did not exist.

Page 2 of 13 Printed Friday, January 21, 2022

ID

GRDDP8

GRDDP9

Object Number

2.0-1

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

2 Reference Document The lower layer protocol definitions for the GeoXO instrument to spacecraft data bus are compliant with EUROPEAN COOPERATION FOR SPACE STANDARDIZATION

⦁ SpaceWire - Links, Nodes, Routers and Networks ECSS-E-ST-50-12C Rev.1, 15 May 2019.

Page 3 of 13 Printed Friday, January 21, 2022

ID

GRDDP10

GRDDP11

GRDDP12

GRDDP13

GRDDP14

GRDDP15

GRDDP16

Object Number

3.0-1

3.0-2

3.0-3

3.0-4

3.0-5

3.0-6

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

3 Definitions Transmitter: An electronic circuit that transmits signals over a physical medium.

Receiver: An electronic circuit that receives signals over a physical medium.

SpaceWire Port: SpaceWire transmitter and receiver circuits and associated logic that implements the SpaceWire Exchange level protocol including link initialization, character flow control, and link error detection and recovery.

SpaceWire Link: A bidirectional point-to-point connection between two SpaceWire ports.

Transport End Point: A Transport End Point (TEP) is defined on a host system for the purpose of either transmitting or receiving application packets over a SpaceWire Link.

Multiple TEPs can be defined for any host system, but each TEP can only transmit or receive not both.

Transport Channel: A protocol defined data path between two TEPs. A Transport Channel can exist only between one transmit TEP and one receive TEP. Each Transport Channel is a one-way data path for application packets. The protocol supports multiple concurrent Transport Channels over a SpaceWire Link.

Page 4 of 13 Printed Friday, January 21, 2022

ID

GRDDP17

GRDDP18

GRDDP19

GRDDP20

GRDDP21

GRDDP22

GRDDP23

GRDDP24

GRDDP25

GRDDP26

GRDDP27

GRDDP28

GRDDP29

GRDDP30

GRDDP31

GRDDP32

GRDDP33

GRDDP34

GRDDP35

Object Number

4.0-1

4.1

4.1.0-1

4.1.1

4.1.1.0-1

4.1.2

4.1.2.0-1

4.1.3

4.1.3.0-1

4.1.4

4.1.4.0-1

4.2

4.2.0-1

4.2.1

4.2.1.0-1

4.2.2

4.2.2.0-1

4.2.3

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

4 Overall Functional Description This protocol describes the mechanism for reliable transfer of data packets over a SpaceWire connection (providing services through the exchange and packet layers).

This protocol adds the following capabilities to a SpaceWire link:

a) Multiplexed Logical Connections

b) Reliable Delivery

c) Missing packet detection

d) Out of sequence packet reordering

4.1 Multiplexed Logical Channels

The protocol shall support multiple simultaneous logical connections over a single SpaceWire link.

4.1.1 Channel Independence

Each Transport channel shall operate independently from other transport channels.

4.1.2 Transmit Priority

When more than one packet is available for transmit, all Acknowledge packets shall be transmitted first, then Reset Command packets, then Urgent Message packets, then Retransmit packets, then Data packets.

4.1.3 Data Transmit Queue

When data packets from more than one channel are available for transmit, packets shall be transmitted in the order in which they are queued.

4.1.4 Urgent Message Transmit Queue

When Urgent Message packets from more than one channel are available for transmit, packets shall be transmitted in the order in which they are queued.

4.2 Reliable Delivery

The Reliable Delivery protocol detects lost packets, duplicate packets, out of sequence packets, and provides damaged data recovery. The protocol provides additional error detection beyond the SpaceWire physical layer utilizing CRCs, packet sequence numbers, positive acknowledgement, and timeouts to detect lost or duplicated Data packets.

4.2.1 Error Detection

Packet errors shall be detected by adding a Cyclic Redundancy Check (CRC) to each packet transmitted, checking it at the receiver, and discarding any erroneous packet.

4.2.2 Packet Sequence Numbers

An 8 bit sequence number shall be assigned to each packet transmitted.

4.2.3 Sequence Number Use

Page 5 of 13 Printed Friday, January 21, 2022

ID

GRDDP36

GRDDP37

GRDDP38

GRDDP39

GRDDP40

Object Number

4.2.3.0-1

4.2.4

4.2.4.0-1

4.2.5

4.2.5.0-1

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

At the receiver the sequence numbers shall be used to detect lost Data, duplicate packets and to correctly order packets.

4.2.4 Acknowledgement and Retransmit

The receiver shall send a positive acknowledgment (ACK) for each data packet received without error.

4.2.5 Retransmission

If the ACK is not received within a defined channel-specific timeout interval the data shall be retransmitted as defined in GRDDP121 [7.5].

Page 6 of 13 Printed Friday, January 21, 2022

ID

GRDDP41

GRDDP42

GRDDP43

GRDDP44

GRDDP45

GRDDP46

GRDDP47

GRDDP48

GRDDP49

GRDDP50

GRDDP51

GRDDP52

GRDDP53

GRDDP54

Object Number

5.0-1

5.1

5.1.1

5.1.1.0-1

5.1.2

5.1.2.0-1

5.1.3

5.1.3.0-1

5.1.4

5.1.4.0-1

5.1.4.1

5.1.4.1.0-1

5.1.4.2

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

5 Packet Format All protocol packets include an 8-byte header, followed by a variable length payload, followed by a 1-byte CRC. The Figure GRDDP42 shows how the protocol packet is encapsulated within the standard SpaceWire packet. Note that while a SpaceWire packet may have zero or more destination addresses before the payload, the Reliable Delivery Protocol requires that exactly one destination address is delivered to the protocol logic.

Figure GRDDP42 GRDDP Packet within a SpaceWire Packet

5.1 Header

5.1.1 Destination Address

The first byte of the header shall contain the Destination Address which is an SLA that identifies the destination TEP to which the packet is being sent.

5.1.2 Protocol ID

The second byte of the header shall be decimal 238 as assigned by the ECSS.

5.1.3 Source Address

The third byte of the header shall be the Source Address SLA that identifies the node from which the packet was sent.

5.1.4 Packet Control

The fourth byte of the header shall contain packet control data.

5.1.4.1 User Defined Bits

The most significant nibble of the Packet Control byte shall be set to all zeros unless a program using this protocol defines them, in a program specific document, for purposes beyond the scope of this document.

Note: For example, a program may define these bits as a sub-PID to identify the payload data to a higher level process.

5.1.4.2 Packet Type

Page 7 of 13 Printed Friday, January 21, 2022

ID

GRDDP55

GRDDP56

GRDDP57

GRDDP58

GRDDP59

GRDDP60

GRDDP61

GRDDP62

GRDDP63

GRDDP64

GRDDP65

GRDDP66

GRDDP67

GRDDP68

GRDDP69

GRDDP70

Object Number

5.1.4.2.0-1

5.1.4.2.0-2

5.1.5

5.1.5.0-1

5.1.6

5.1.6.0-1

5.1.7

5.1.7.0-1

5.1.8

5.1.8.0-1

5.2

5.2.1

5.2.1.0-1

5.2.2

5.2.2.0-1

5.3

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

The least significant nibble of the Packet Control byte shall identify packet type as listed in Table GRDDP55.

Table GRDDP55 Packet Type Values Packet Type Value

Application Data 0

Acknowledge 1

Reset Command 2

Urgent Message Data 3

Reserved 4 to 15

The most significant nibble of the Packet Control byte is reserved and shall be set to 0.

5.1.5 Application Payload Length MSB

The fifth header byte shall contain the most significant byte of the Application Payload byte length field.

5.1.6 Application Payload Length LSB

The sixth header byte shall contain the least significant byte of the Application Payload byte length field.

5.1.7 Channel Number

The seventh header byte shall contain the Destination SLA and have the same value as header byte 1.

5.1.8 Sequence Number

The eighth byte of the header shall be a sequence number in the range 0 through 255.

It is recommended that the sequence number range be twice the window size.

5.2 Application Payload

5.2.1 Data Packets and Urgent Messages

The protocol Data packets and Urgent Message Packets shall contain an Application Payload field containing 1 to 65520 (inclusive) bytes of content for delivery to the Application Level client associated with the channel's Receive TEP.

5.2.2 Acknowledge and Reset Packets

Protocol packets that are an Acknowledge or Reset Command shall contain a zero length Application Payload field.

5.3 Trailer

Page 8 of 13 Printed Friday, January 21, 2022

ID

GRDDP71

GRDDP147

GRDDP72

Object Number

5.3.0-1

5.3.1

5.3.1.0-1

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

The protocol packet trailer shall be an 8 bit Asynchronous Transfer Code (ATM) Cyclic Redundancy Check (CRC) computed from the transport header destination SLA to the last payload byte, defined in the following polynomial:

CRC8, ATM (HEC)

x8 + x2 + x + 1

5.3.1 CRC Preset

Prior to computing each packet's CRC, the initial value for the computation shall be set to all 1s.

Page 9 of 13 Printed Friday, January 21, 2022

ID

GRDDP73

GRDDP74

GRDDP75

GRDDP76

GRDDP77

GRDDP78

Object Number

6.0-1

6.1

6.1.0-1

6.2

6.2.0-1

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

6 Transport Channel Definition The set of available Transport Channels for each host system shall be pre-defined in protocol configuration tables.

6.1 TEP Parameters

Each TEP shall be defined with the parameters found in Table GRDDP76.

Table GRDDP76 TEP Parameters

Local SLA The SLA assigned to the TEP for each channel.

Remote SLA The SLA assigned to the TEP which is connected to the Local TEP.

TEP Type Identifies the TEP as transmit or receive.

Window Size The size of the channel's sequence number window.

The Window size must be a power of 2.

Time Out Transmit TEPs only. The time to wait to receive an acknowledge before retransmitting a data packet.

Maximum Retries Transmit TEPs only. The number of retry attempts allowed before declaring a channel failure.

6.2 TEP States

Each TEP shall be in one of three possible operating states

Closed The TEP does not generate any packets on the link and does not respond to any packets received.

Enabled A TEP transitions to the “Enabled” state when the host has requested it to be opened, and provided appropriate I/O buffer information. In addition, a Transmit TEP sends a reset command on this transition.

Open A Receive TEP transitions from Enabled to Open when a Reset command has been received from the remote Transmit channel. A Transmit TEP transitions from Enabled to Open when it receives an ACK for a Reset command that it has sent to the remote Receive TEP.

Page 10 of 13 Printed Friday, January 21, 2022

ID

GRDDP79

GRDDP80

GRDDP81

GRDDP82

GRDDP83

GRDDP84

GRDDP85

GRDDP86

GRDDP87

GRDDP88

GRDDP89

GRDDP90

GRDDP91

GRDDP92

GRDDP93

GRDDP94

GRDDP95

GRDDP96

GRDDP97

GRDDP98

Object Number

7.1

7.1.0-1

7.2

7.2.0-1

7.2.1

7.2.1.0-1

7.2.2

7.2.2.0-1

7.3

7.3.0-1

7.4

7.4.0-1

7.4.1

7.4.1.0-1

7.4.2

7.4.2.0-1

7.4.3

7.4.3.0-1

7.4.4

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

7 Channel Operations

7.1 Logical Connections

Upon power up initialization all TEPs shall be in the Closed state.

7.2 Reset Command

When a Transmit TEP transitions to the Enabled state, it shall send a Reset command to its remote Receive TEP and initiate an acknowledgement timer.

7.2.1 Reset Timer Cancellation

Upon receipt of a Reset acknowledgement, the transmit TEP shall cancel the acknowledgement timer.

7.2.2 Reset Timer Expiration

Upon expiration of the Reset timer period, the transmit TEP shall retransmit the Reset command.

7.3 Transport Channel Connection

A Transport Channel connection shall be considered established when a Transmit TEP and Receive TEP are both in the Open state.

7.4 Receive TEP Operations

A receive TEP does not send data packets, Urgent Messages, or Reset Commands.

7.4.1 Sliding Window

The receive TEP shall maintain a sliding window which is a range of consecutive sequence numbers to determine whether each received data packet will be accepted or discarded.

7.4.2 Sliding Window Range

The receive window range shall start with the sequence number of the next data packet expected to be delivered and end with sequence number equal to the start plus Window Size minus 1.

7.4.3 Window Advance

The receive window shall be advanced by 1 upon receipt of a packet containing the next expected sequence number.

Note: If packets with successively adjacent sequence numbers have already been received out of order, the start of the receive window will be advanced by more than 1, plus the number of successively adjacent “early” packets.

7.4.4 Packet Acknowledgement

Page 11 of 13 Printed Friday, January 21, 2022

ID

GRDDP99

GRDDP100

GRDDP101

GRDDP102

GRDDP103

GRDDP104

GRDDP105

GRDDP106

GRDDP107

GRDDP108

GRDDP109

GRDDP110

GRDDP111

GRDDP112

GRDDP113

GRDDP114

GRDDP115

GRDDP116

GRDDP117

GRDDP118

GRDDP119

GRDDP120

GRDDP121

GRDDP122

Object Number

7.4.4.0-1

7.4.5

7.4.5.0-1

7.4.6

7.4.6.0-1

7.4.7

7.4.7.0-1

7.4.8

7.4.8.0-1

7.4.9

7.4.9.0-1

7.4.9.0-2

7.4.10

7.4.10.0-1

7.4.11

7.4.11.0-1

7.4.12

7.4.12.0-1

7.4.13

7.4.13.0-1

7.4.14

7.4.14.0-1

7.5

7.5.1

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

All Data and Reset Command packets received without error shall be acknowledged.

7.4.5 Packets with Errors

Any packet received with detectable errors shall be discarded and not acknowledged.

7.4.6 Out of Window Sequence Number

A data packet that is received with a sequence number that is not within the receive window shall be acknowledged, but discarded.

7.4.7 Duplicate Sequence Number

A data packet received with a sequence number within the receive window that is a duplicate of a packet pending delivery to the host shall be acknowledged, but discarded.

7.4.8 Urgent Message Acknowledgement

Urgent Message packets shall not be acknowledged.

7.4.9 Urgent Message Delivery Order

Urgent Message packets shall be delivered to the host in the order received.

The Urgent Message sequence number shall be set to 0.

7.4.10 Urgent Message Delivery Priority

Urgent Message packets shall be delivered to the host before any Data Packets pending delivery.

7.4.11 Reset Command Sequence Number

A Reset command that does not have a sequence number of zero shall be treated as an error packet.

7.4.12 Reset Command Processing

When a Reset command is received, the receive window start shall be set to 1.

7.4.13 Packets Pending Delivery

When a Reset command is received all packets pending delivery to the host shall be discarded.

7.4.14 Reset Command Report

Receipt of a reset command shall be reported to the host.

7.5 Transmit TEP Operations

7.5.1 Transmit TEP ACKs

Page 12 of 13 Printed Friday, January 21, 2022

ID

GRDDP123

GRDDP124

GRDDP125

GRDDP126

GRDDP127

GRDDP128

GRDDP129

GRDDP130

GRDDP131

GRDDP132

GRDDP133

GRDDP134

GRDDP135

GRDDP136

GRDDP137

GRDDP138

GRDDP139

GRDDP140

GRDDP141

GRDDP142

GRDDP143

GRDDP144

Object Number

7.5.1.0-1

7.5.2

7.5.2.0-1

7.5.3

7.5.3.0-1

7.5.4

7.5.4.0-1

7.5.5

7.5.5.0-1

7.5.6

7.5.6.0-1

7.5.7

7.5.7.0-1

7.5.8

7.5.8.0-1

7.5.9

7.5.9.0-1

7.5.10

7.5.10.0-1

7.5.11

7.5.11.0-1

7.5.11.0-2

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

A transmit TEP shall not send an ACK packet.

7.5.2 Transmit TEP Sequence Number Allocation

Each data packet transmitted shall have a sequence number allocated from the TEP's transmit window range of available sequence numbers.

7.5.3 Reset Command Sequence Number

All Reset commands shall be transmitted with a sequence number zero.

7.5.4 Transmit Window

A transmit TEP shall maintain a sliding window range of consecutive sequence numbers that are available for transmitting data packets.

7.5.5 Unacknowledged Packets

The transmit window shall limit the number of unacknowledged data packets that can be transmitted.

7.5.6 Transmit Window Start

The transmit window start shall be set to 1 when an ACK is received for a Reset command.

7.5.7 Transmit Window Advance

The transmit window start shall be advanced by 1 when the ACK is received for the first sequence number in the transmit window.

7.5.8 Packet Retransmit

A transmitted data packet that is not acknowledged within a channel specific timeout interval shall be retransmitted with the original sequence number up to a channel specific number of times.

7.5.9 Retry Reset

When a channel specific number of retry attempts have been exceeded the channel shall be reset.

7.5.10 Timeout Start

The timeout interval shall begin when the last byte of the Data Packet or Reset Command has been transmitted.

7.5.11 Urgent Message Transmission

Urgent Message Packets shall be sent immediately without being allocated a transmit window sequence number or starting an acknowledgement timer.

Note that Urgent Message Packets are sent once without retries or acknowledgements.

Page 13 of 13 Printed Friday, January 21, 2022

ID

GRDDP145

GRDDP146

Object Number

8.0-1

418-XO-RPT-0039, RM Version, Geostationary Operational Environmental Satellite (GOES) Reliable Data Delivery Protocol

(GRDDP)

8 Acronyms ACK Acknowledgment ATM Asynchronous Transfer Mode CRC Cyclic Redundancy Check ECSS European Cooperation for Space Standardization GOES Geostationary Operational Environmental Satelite GeoXO Geostationary Extended Observations Satellite Series GRDDP GOES Reliable Data Delivery Protocol GSFC Goddard Space Flight Center HEC Header Error Code ID Identification NASA National Aeronautics and Space Administration SLA SpaceWire Logical Address TEP Transport End Point

Effective Date: January 19, 2022 418-XO-RPT-0039 Expiration Date: Five years from date of last signature Baseline Version 1.0 Responsible Organization: GeoXO Flight Project/Code 418

Document Change Record (DCR)

CCR GEO-XO#: X000049 Rev: Title: 418-XO-RPT-0039: Baseline GOES Reliable Data Delivery Protocol (GRDDP) Contract # N/A GOES S/C: GEO-XO Effectivity: Instruments CCB Status: Approved Doc #: 418-XO-RPT-0039 CCB Date: 1/19/2021 Doc Version: 1.0 Contract Mod#: N/A DOORs Version: 1.0 Doc Change Date: Jan. 19, 2022 DOORs ID #: 1.0