Attachment A - SOW Rev A.pdf

RFP# 80GSFC22R0029

Attachment A

NEAR SPACE NETWORK

SERVICES

STATEMENT OF WORK

DATE: March 2023

Rev. A

Approved By:

Vir Thanvi

Near Space Network

Change History Log Revision Effective Date Description of Changes Released 2/21/23

Rev A 3/20/23 Removed NASA IT Security Policy from Table of Contents Removed IONET 290-004 and

IONET Checklist references Table 7 updated to state BPv6 and BPv7

Table of Contents

1. Introduction

1.1. Introduction

1.2. Background

1.3. Near Space Network Services (NSNS) Contract Objectives

1.4. NSNS Contract Scope and Structure

1.5. Spectrum Management

1.6. Definitions & Terminology

1.6.1. Near Space Region

1.6.2. Ground Segment

1.6.3. Secure

1.6.4. Coverage

1.6.5. Service Provider Latency

1.6.6. Nominal Services

1.6.7. Critical Services

1.6.8. Service Availability

1.6.9. Proficiency

1.6.10. Mean Time to Restore

1.6.11. Near Space Network (NSN) Demarcation

2. NSNS Contract Task Order Structure

2.2. Operational Services Task Orders

2.3. Mission Integration and Special Studies (MI&SS) Task Orders

3. General Requirements

3.1. Management

3.2. Capability Validation

3.3. Operational Services

3.4. Mission Integration and Special Studies (MI&SS)

4. Technical Requirements

4.1. Overarching Requirements for All Services (DTE and Near Space Relay)

4.1.1. Service Capabilities

4.1.2. Service Management

4.1.3. Monitor and Control

4.1.4. Service Execution

4.1.5. Interfaces

4.1.6. Mission Assurance

4.2. Category 1 Direct to Earth (DTE) Services

4.2.1. Performance Requirements for all Category 1 DTE Services

4.2.2. Category 1.1. Earth Proximity (EP) DTE Services

4.2.3. Category 1.2: GEO-to-Cislunar DTE Services

4.2.4. Category 1.3: xCislunar DTE Services

4.3. Category 2 Near Space Relay Services

4.3.1. Category 2.1: Earth Proximity (EP) Relay Services

4.3.2. Category 2.2: GEO-to-Cislunar Relay Services

4.3.3. Category 2.3: xCislunar Space Relay Services

Appendix A – Related Documentation

Applicable Documents

Reference Documents

Appendix C – Acronyms

Figures Figure 1 NSNS Service Categories Figure 2 NSNS Service Regions Figure 3 NSN Interfaces

Tables Table 1 Category 1 NSNS Near Space Direct-to-Earth and Space Relay Services Table 2 Service Regions and Orbits Table 3. Summary of Service Capabilities Table 4. Service Management Capabilities Table 5. Monitor and Control Capabilities for Asset Service Configuration and Asset and Service Status20 Table 6. Monitor and Control Capabilities for Operational Status Notification and Coordination Table 7. Data Service Standards Table 8. Availability, Proficiency, and Reliability Requirements for Category 1 and 2 Services Table 9. Forward Data Service Performance – DTE Table 10. Return Data Service Performance – DTE Table 11. Tracking Performance – DTE Table 12. Forward Data Functional Requirements for Earth Proximity DTE Table 13. Return Data Functional Requirements for Earth Proximity DTE Table 14. Tracking Functional Requirements for Earth Proximity DTE Table 15. Forward RF Signal Performance Requirements for Earth Proximity DTE Table 16. Return RF Signal Performance Requirements for Earth Proximity DTE Table 17. PNT Performance for Earth Proximity DTE Table 18. Maximum Line-of-sight dynamics Table 19. Forward Data Functional Requirements for GEO-to-Cislunar DTE Table 20. Return Data Functional Requirements for GEO-to-Cislunar DTE Table 21. Tracking Functional Requirements for GEO-to-Cislunar DTE Table 22. Forward RF Signal Performance for GEO-to-Cislunar DTE Table 23. Return RF Signal Performance for GEO-to-Cislunar DTE Table 24. PNT Performance for GEO-to-Cislunar DTE Table 25. Maximum Line-of-sight dynamics Table 26. Forward Data Functional Requirements for xCislunar DTE Table 27. Return Data Functional Requirements for xCislunar DTE Table 28. Tracking Functional Requirements for xCislunar DTE Table 29. Forward RF Signal Performance for xCislunar DTE Table 30. Return RF Signal Performance for xCislunar DTE Table 31. PNT Performance for xCislunar DTE Table 32. Maximum Line-of-sight dynamics Table 33. GEO-to-Cislunar Space Relay Capabilities Summary Table 34. Applicable Documents Table 35. Reference Documents

1. Introduction

1.1. Introduction

This Statement of Work (SOW) describes the scope of work to be performed by the Contractor for Contractor-provided communication and navigation services in support of the National Aeronautics and Space Administration (NASA) under the Near Space Network Services (NSNS) Contract. These communication and navigation services are required for NASA to support mission users in the Near Space region. This NSNS SOW requires the Contractor to conduct service capability validation activities and provide operational communications and navigation services as part of the Near Space Network (NSN) to support a diverse set of launch vehicle, robotics, and human spaceflight missions.

1.2. Background

The NSN fulfills the essential needs of user missions, empowering them with mission-critical communications and navigation services and enabling the transmission of science and exploration data to and from space. As a single end-to-end network service for missions in the Near Space region — out to two million kilometers (km) from the Earth’s surface — the NSN orchestrates communications and navigation services, space links, and data transport ensuring its users have secure, robust, and reliable communications and navigation services that fully support user missions’ needs and objectives.

Additionally, NSN serves missions throughout their entire lifecycle, providing requirements analysis, spectrum management, communications analysis, service agreements, mission design, mission planning, and support for launch, operations, and post-mission activities. NSN services are critical to operating NASA’s many robotic spacecraft and human exploration missions, as well as returning ground-breaking scientific data to Earth where it can be used for the benefit of humanity.

NSN is positioned within the NASA’s Goddard Space Flight Center (GSFC) Exploration and Space Communications (ESC) Projects division. NSN operates under the Space Communications and Navigation (SCaN) program office at NASA Headquarters to effectively implement their vision. SCaN is part of the Space Operations Mission Directorate (SOMD) and provides programmatic oversight of NASA’s networks, advanced communication technologies, and other space communications requirements.

1.3. Near Space Network Services (NSNS) Contract Objectives

The goal of the NSNS contract is to provide NASA with a single avenue to procure communication and navigation services that are secure, reliable, and affordable, so that all NSN user missions will receive communication and navigation services in accordance with the functional and performance needs.

The objectives of the NSNS contract are to:

• Provide affordable, proficient, secure, and timely delivery of communication and navigation services from multiple providers for existing and future scientific, technology and human spaceflight mission customers from the Earth’s surface up to 2 million km, including those on the lunar surface or in lunar orbit.

• Deliver communication and navigation services that ensure astronaut safety and meet functional, performance, and mission assurance objectives for both human and robotic missions.

• Solicit commercial providers to validate their capabilities to deliver communication and navigation services such that all user missions receive the services in accordance with the functional and performance needs.

• Offer opportunities for commercial providers, after capability validation, to be considered for follow-on operational communication and navigation services.

• Provide a mechanism to regularly incorporate new communication and navigation services providers, technology upgrades, and improved processes and products through an on-ramp feature that allows for additional awards and further competition as industry develops additional capabilities.

• Encourage infusion and implementation of commercial capabilities that provide communication and navigation services to a diverse range of mission customers, of which NASA will be only one of many.

• Foster competition and create opportunities for new, emerging communication and navigation service providers.

• Provide Lunar Direct-to-Earth (DTE) and Lunar Relay services to NASA Artemis Missions.

1.4. NSNS Contract Scope and Structure

Paramount to the success of NASA and its partner missions, procured communication and navigation services must provide quality secure and reliable end-to-end connectivity among user platforms, relay satellites, and ground stations capable of meeting mission requirements. The NSNS SOW separates the procurement of the desired Near Space communication and navigation capabilities into two categories as shown in Figure 1:

• Category 1: Near Space Direct to Earth (DTE) Services: Direct-to-Earth communication and position, navigation, and timing (PNT) services for user missions from the Earth’s surface up to 2 million km.

• Category 2: Near Space Relay Services: End-to-end Space Relay communication and PNT services for user missions from the Earth’s surface up to 2 million km.

Figure 1 NSNS Service Categories

The NSNS SOW further divides the two Near Space communication and navigation services categories into three service regions as shown in figure 2 below. The three service regions are:

• Region 1: Earth Proximity: Altitudes from the Earth’s surface to Geosynchronous Equatorial Orbit (GEO) at ~36,000 km.

• Region 2: GEO-to-Cislunar: Altitudes from GEO to ~500,000 km from Earth’s surface. This region includes the moon and the Earth-Moon Lagrange points (EML labels in Figure 2).

• Region 3: xCislunar: Altitudes from ~500,000 km to 2 million km from Earth’s surface. This region includes the Sun-Earth Lagrange points 1 and 2 (SEL labels in Figure 2).

Figure 2 NSNS Service Regions coordinate US spectrum allocation issues. US allocations relevant to NSN are consistent with international allocations but may also include additional limitations and constraints.

The Contractor shall acquire all spectrum authorizations needed for their services.

1.6. Definitions & Terminology

1.6.1. Near Space Region

The Near Space Region is defined as the volume of space bounded by the Earth’s surface up to a radius of 2 million km (ref: ITU definition of “Near Space”). This region includes cislunar space and all areas of interest within this volume (e.g., Sun-Earth and Earth-moon Lagrange points) utilized to conduct spaceflight missions and/or provide the services (Communication, Position, Navigation, and Timing) needed by the users.

1.6.2. Ground Segment

The Ground Segment includes any ground-based elements such as the Ground Station, personnel to operate, maintain, and sustain the Ground Station and any systems required to interface with the NSN.

For this NSNS contract, Ground Stations are defined as the infrastructure that provides the interface between the space segment and the ground antenna.

1.6.3. Secure

Secure is defined as the need for confidentiality, integrity, and availability of the systems, data, and communication pathways that support requirements of this NSNS contract. These protections shall be ensured to prevent unauthorized access as well as corruption, interception, and loss of data.

• Confidentiality - Defined as preserving authorized restrictions on information access and disclosure, including ensuring the means for protecting personal privacy and proprietary information from access and disclosure.

• Integrity - Defined as guarding against improper information modification or destruction and includes ensuring information non-repudiation and authenticity.

• Availability - Defined as ensuring timely and reliable operation of the system that provides access to, and use of, information.

1.6.4. Coverage

Coverage is defined as the volume of space covered by services, within which the system can close the link with a specified number of users in that volume. That assumes knowledge of user platform characteristics, number of users serviced simultaneously and expected service duration. Coverage may be measured over one Earth month depending on orbital location of the users.

1.6.5. Service Provider Latency

Latency is defined as the amount of time elapsed during data transfer between a user mission and the NSN interface demarcation.

1.6.6. Nominal Services

Nominal Services are communication and navigation services that support routine user missions’ operations. Examples of nominal services includes support to user mission activities such as but not limited to command uplink, telemetry downlink, and science/payload data handling.

1.6.7. Critical Services

Critical Services are communication and navigation services that pose a risk to mission success if not delivered reliably and securely at all times during mission critical phases.

Routine Critical, Contingency Critical, and Emergency Critical activities are subcategories of critical services.

Routine Critical activities are planned events normally scheduled in advance. Examples of Routine Critical Services include launch, ascent, early orbit operations, descent, and all phases of crewed missions including Extra-Vehicular Activities (EVAs).

Contingency activities are planned events that are executed if the user mission platform experiences a failure or degradation in function or performance that affects normal data collection, or otherwise compromises the health and safety of the system. Anomalies could be sudden, discrete events, such as the failure of a critical component, or could be a gradual degradation in performance detected by engineering trending that permits action prior to the occurrence of a mission-threatening situation.

Emergency activities are unplanned events in response to an unexpected anomaly that if not responded to in a timely manner would result in loss of mission, or in the case of crewed missions, loss of life. Emergency service requests will be coordinated by the NSN directly with the Contractor to receive immediate communications and navigation services to prevent loss of a user mission platform, enable safing, restore nominal operations, and preserve life.

1.6.8. Service Availability

Service Availability is defined as the percentage of time service is scheduled by the provider divided by total time for which services are requested to be scheduled by NSN. Lost scheduled services due to provider discrepancies or actions such as, but not limited to, automated or manual failover to restore service or unscheduled maintenance will be factored into the service availability percentage.

1.6.9. Proficiency

Proficiency is defined as the percentage of the time of usable data received over time of usable data expected.

Proficiency = TUsable Data Received / (TUsable Data Expected).

Expected time of data flow may be shorter than the scheduled service event. Unusable or no data attributed to user missions are not counted towards provider service proficiency.

1.6.10. Mean Time to Restore

Mean Time To Restore (MTTR) is defined as the average elapsed time required to restore a nominal or critical service back to an operational state. MTTR should be computed based upon the recovery of a service vice and individual component and should include both terrestrial and space based assets in the computations.

1.6.11. Near Space Network (NSN) Demarcation

The NSN demarcation defines the interface boundary between the Government and the Contractor zones of responsibility. The Government intends to implement interoperable cloud-driven interfaces as the NSN demarcation, however the Government recognizes that based on mission needs as well as provider capabilities, alternate solutions may be necessary. For example, the NSN demarcation may be a cloud point-of-presence, an edge device residing at a provider’s ground station, or dedicated terrestrial connection at a user mission facility.

2. NSNS Contract Task Order Structure The NSNS contract will acquire Near Space DTE and Near Space Relay communication and navigation services through a series of task orders listed below.

• Capability Validation Task Orders

• Operational Services Task Orders

• Mission Integration and Special Studies (MI&SS) Task Orders

The NSN Services task orders may be tailored, as needed, to meet the unique needs of user missions.

2.1. Capability Validation Task Orders

The Capability Validation Task Orders are the first task orders to be awarded under the NSNS contract.

The Contractor shall perform all work necessary to validate its capability of providing communication and navigation services in the awarded subcategory, consistent with the SOW and the issued task orders. The Capability Validation work will be completed in a methodical series of steps (milestones).

For Category 2.2 only, the Capability Validation work is broken into multiple task orders which will be sequentially issued; only after the Contractor’s successful completion of the then-current task order work, and Government acceptance of the task order’s deliverable(s), will the contractor be eligible for issuance of subsequent capability validation task order(s). Operational readiness shall be achieved at the completion of all milestones and the Government’s acceptance of all required deliverables. Once Capability Validation is successfully completed, the Contractor will then be eligible to compete for, and to be awarded Operational Services Task Orders for the corresponding subcategory of service, as well as to be issued Mission Integration and Special Studies (MI&SS) Task Orders.

2.2. Operational Services Task Orders

Operational Services Task Orders will be released periodically to acquire nominal and critical operational services as well as operational support services, in accordance with the Government’s needs. The Contractor shall perform all work necessary to provide secure and reliable operational end-to-end communication and navigation services meeting all functional, performance, and mission assurance requirements. The operational services shall meet the needs of diverse launch vehicle, robotic and human space flight missions within the awarded subcategory.

2.3. Mission Integration and Special Studies (MI&SS) Task Orders Mission Integration and Special Studies (MI&SS) Task Orders will be issued to address specific or unique NSN needs that require contractor support. The Contractor shall perform work related to special studies, analyses, and testing in support of NSN activities. The Contractor shall collaborate and coordinate with NSNS throughout the MI&SS Task Order.

3. General Requirements

3.1. Management

The Management Requirements apply to all task orders issued under this NSNS contract.

The Contractor shall perform all management functions required to deliver the full scope of each awarded task order.

The Contactor shall submit reports, conduct reviews, and participate in meetings to keep the Government informed of status, risks, and issues. This would include activities such as but not limited to service discrepancies reporting, Operations Services metrics, and other business and technical metrics.

The Contractor shall implement, operate, maintain and sustain capable systems and employ a qualified workforce (demonstrated by training and skills certification, engineering and operations workforce experience, educational attainments and security clearance) to provide services under the NSNS contract.

The Contractor shall execute a continuous risk management process that enables proactive identification of any risks and associated mitigations to providing communication and navigation services.

The Contractor shall identify opportunities for efficiencies, included but not limited to, innovative approaches, cost savings, and process improvements.

The Contractor shall perform all Export Control functions required to deliver NSNS contract services. The Contractor shall comply with all U.S. export control laws and regulations and NASA export policies including:

• Title 22 CFR 120-130: International Traffic in Arms Regulations (ITAR)

• Title 15 CFR Parts 730-799: Export Administration Regulations (EAR)

• NPD 2190.1: NASA Export Control Program

The Contractor shall execute a robust configuration management process to ensure the integrity of the offered services to NSN.

The Contractor shall ensure confidentiality, integrity, and availability of the systems, data, and communication pathways that will support the requirements of this NSNS contract. These protections shall be ensured to prevent unauthorized access as well as corruption, interception, and loss of data.

The Contractor shall control Controlled Unclassified Information (CUI) in accordance with NIST SP 800- 171 and NPR 2810.7.

The Contractor shall handle classified information in accordance with NPR 1600.2 and within the defined parameters of its DD 254 for the applicable subcategories.

The Contractor shall provide the Government online access to data and documentation relevant to the NSNS contract.

The Contractor shall perform an annual assessment in accordance with NIST SP 800-171 or ISO 27002 and provide the results to the Government for review and concurrence. Evidence of compliance shall be presented by the Contractor on an annual basis or as requested by the Government.

The Contractor shall complete an Interconnection Security Agreement (ISA) with any information system that is authorized by a different organization or Authorizing Official (AO).

The Contractor shall notify the Government of cybersecurity incidents within 30 minutes of discovery and provide remediation timelines and on-going daily reporting on all required incident response activities involving NASA data or information systems.

The Contractor shall use FedRAMP approved Cloud services, as applicable, that are processing and or transporting data associated with NSN services. Any FedRAMP approved system can be used to support the NSNS contract. FISMA Moderate and High systems will be required for the execution of the NSNS contract. Moderate systems may be used for certain space science missions and High systems may be used for supporting human spaceflight missions. The categorization supporting each mission shall be based on the Interconnection Security Agreement (ISA) and the data types being transported on a case-by-case basis.

Personnel security requirements for all staff involved with processing and transporting data associated with NSNS contract shall adhere to ITS-HBK-2810.13-01 Personnel Security.

The Contractor shall participate in NSN end-to-end threat assessments.

The Contractor shall conduct network administration, system administration, IT (Information Technology) support services, system maintenance, IT security functions, and other ancillary IT tasks to support contractual requirements and ensure the security of systems.

The Contractor shall have systems capable of connecting to NASA’s mission network.

The Contractor shall ensure compliance with International Telecommunications Union (ITU), Federal Communications Commission (FCC), and National Telecommunications and Information Administration (NTIA) spectrum regulations, as applicable.

The Contractor shall obtain the required frequency authorizations and licenses for the services provided under the NSNS contract.

The Contractor shall be responsible for maintaining compliance with appropriate national and local authorization and licensing requirements and regulations for operations outside of the US.

The Contractor shall maintain OSHA certification for facilities and activities within the United States. For operations outside of the U.S, the Contractor shall be responsible for maintaining compliance with appropriate national and local occupational safety requirements and regulations.

3.2. Capability Validation

The Contractor shall perform all work necessary (including accomplishing all associated milestones) to validate its capability to provide Near Space DTE or Near Space Relay communication and navigation services in the awarded subcategory.

The Contractor shall plan, schedule, and conduct Capability Validation Milestone (CVM) reviews in support of the NSNS contract.

The Contractor shall host periodic Technical Exchange Meetings (TEMs) with the Government to discuss status, progress, and risks as well as any other technical exchanges.

3.3. Operational Services

The Contractor shall provide secure and reliable operational Near Space DTE or Near Space Relay communication and navigation services in the awarded subcategory(ies).

The Contractor shall provide nominal and critical Operational Services as well as operational support services.

The Contractor shall comply with Near Space Network configuration management guidelines (e.g., network freeze) at the time of supporting nominal and critical operational services.

The Contractor shall perform all functions associated with Service Management, Monitor and Control, and Service Execution.

The Contractor shall exchange all required Service Management, Monitor and Control, and Service Execution real-time and non-real-time data with NSN.

The Contractor shall schedule services in accordance with the priority of the NSNS contract.

The Contractor shall ensure systems, personnel are available and trained to support Operational Services per scheduled events.

The Contractor shall allocate network resources to ensure secure and proficient service execution that meets functional and performance requirements as applicable to the service.

During Contingency or Emergency Critical Services, the Contractor shall respond within 30 minutes to service request and coordinate directly with the NSN operations personnel to ensure mission assurance.

The Contractor shall prioritize Critical Service requests over any Nominal Service request. The Contractor shall give absolute priority to Critical Service requests regardless of any other contractual requirement they may have.

The Contractor shall provide on-console support for all critical services.

The Contractor shall provide engineering support when the NSN user mission declares an emergency or contingency.

The Contractor shall provide operational support services. The Contractor shall support the Government during onboarding of new missions by NSN. This includes activities such as, but not limited to:

Table 3. Summary of Service Capabilities

Service Management – Resource Availability Service Management – Resource Request and Confirmation Service Management – Spacecraft Acquisition Data Monitor and Control – Asset and Service Configuration Monitor and Control – Asset and Service Status Monitor and Control – Operational Status Notification Monitor and Control – Operational Coordination Service Execution – Forward Data Services Service Execution – Return Data Services Service Execution – Tracking Services (Category 1, DTE services only) Service Execution – PNT Services (Category 2, Space Relay services only)

4.1.2. Service Management

The Contractor shall provide the following Service Management capabilities as identified in the Table below:

4.1.4. Service Execution

The Contractor shall provide Forward Data Services.

The Contractor shall provide Return Data Services

The Contractor shall provide Position, Navigation, and Timing Service.

4.1.5. Interfaces

The interfaces between NSN and the Contractor systems are as shown in the figure below.

Figure 3 NSN Interfaces

The Contractor shall provide end-to-end services between NSN demarcation and the user platform.

The Contractor shall collaborate with the Government to define Interface Control Document (ICD) amongst Contractor systems, NSN systems, and user missions.

The Contractor shall configure and operate its interfaces to NSN in compliance with the Interconnection Security Agreement (ISA).

The government expects connections to the NSN to be cloud-based, utilizing industry standard interfaces to the maximum extent practicable. The government does recognize that there may be unique circumstances that will require mission unique interfaces that may not be cloud-based.

The Contractor shall provide and receive real-time and non-real-time Service Management, Monitor and Control, and Service Execution data necessary to support communication and navigation services in the Earth Proximity, GEO-to-Cislunar, and xCislunar service regions.

The Contractor shall provide resource availability to NSN.

4.2. Category 1 Direct to Earth (DTE) Services

Category 1 services include secure DTE communication and navigation services between ground stations and user missions in all three Near Space service regions. Category 1 DTE Services provide line of sight communication and tracking services for user missions from the Earth’s surface up to 2 million km.

4.2.1. Performance Requirements for all Category 1 DTE Services This section describes the performance requirements for Category 1 DTE services for all service regions.

The Contractor shall provide secure communications and navigation services that meet or exceed the performance requirements.

The Contractor shall meet or exceed the following Forward and Return Data Service Performance requirements.

Table 9. Forward Data Service Performance – DTE

Forward Data Delivery Latency

Real-time

Forward Data Delivery Jitter

≤ 0.1% of nominal symbol rate

Table 10. Return Data Service Performance – DTE

Return Data Quality Bit-error rate (BER) no more than 1.0E-5, or equivalent frame error rate

(FER)

Return Data Delivery Latency

Real-time services: SLA threshold varies by mission; performance target is < 6 seconds (best effort) and < 15 seconds (maximum)

Non-real-time services: SLA threshold varies by mission Return Data Delivery Jitter

≤ 0.1% of nominal symbol rate

Return Data ERT Accuracy

No more than 50 microseconds at data rates above 1 ksps

The Contractor shall meet or exceed the following Tracking Performance requirements.

Table 11. Tracking Performance – DTE

Antenna Travel Range >360 deg azimuth continuous 0-90 deg elevation

Antenna Tracking Rate 0.5 deg/sec

Autotrack Accuracy ±0.2 dB of beam peak

Timing Reference

For Earth Proximity DTE:

Short term stability better than 6*10^-12 ADEV at Tau = 1 second (desired stability is better than 10^-13) For GEO-to-Cislunar and xCislunar DTE:

Short term stability better than 10^-13 ADEV at Tau = 1 second Long term stability better than 3*10^-15 ADEV @ 1000s

4.2.2. Category 1.1. Earth Proximity (EP) DTE Services

The Contractor shall provide secure communications and navigation services that meet or exceed the functional and performance requirements for the awarded subcategory. It is anticipated that a global network of ground stations is required to provide DTE services for the Earth Proximity service region.

4.2.2.1. EP DTE Functional Requirements

The Contractor shall meet the following functional requirements.

Table 12. Forward Data Functional Requirements for Earth Proximity DTE

Frequency Bands S-band X-band Ka-band Optical (1530 – 1565 nm)

Service Coverage Forward service line of sight coverage for user mission platforms above 5 degrees elevation, subject to antenna horizon masks

Space Service Interface CLTU

ECLTU

File Frame

IP

Bitstream

Space Interface Protocols

CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 231.0 "TC Synchronization and Channel Coding" CCSDS 131.0 "TM Synchronization and Channel Coding" CCSDS 232.0 "TC Space Data Link Protocol" CCSDS 132.0 "TM Space Data Link Protocol" CCSDS 732.0 "AOS Space Data Link Protocol" CCSDS 133.0 "Space Packet Protocol" CCSDS 133.1 "Encapsulation Packet Protocol" CCSDS 727.0 "CCSDS File Delivery Protocol (CFDP)" CCSDS 232.1 "Communications Operation Procedure-1"

Ground Service Interface

CLTU over TCP/IP

CLTU

Transfer Frame CADU over TCP/IP File with delivery meta-data (time, destination, forwarding) CCSDS frame over TCP/IP IP packets Bitstream data encapsulated over UDP/IP

Ground Interface Protocol Stack

CCSDS 912.1 "Space Link Extension--Forward CLTU Service Specification"

CCSDS 912.11 "Space Link Extension--Enhanced Forward CLTU Service"

CCSDS 913.1 "Space Link Extension--Internet Protocol for Transfer Services"

CCSDS 922.3 "Cross Support Transfer Service—Forward Frame Service"

IP

SFTP, HTTP, or CFDP over IP

Table 13. Return Data Functional Requirements for Earth Proximity DTE

Frequency Bands S-band X-band X-band (Space Research Service) Ka-band Optical (1530 – 1565 nm)

Service Coverage Return service line of sight coverage for user mission platforms above 5 degrees elevation subject to antenna horizon masks.

Space Service Interface All Frames Channel Frames Beacon Tone File Packet

IP

Bitstream

Space Interface Protocol Stack

CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 131.0 "TM Synchronization and Channel Coding" CCSDS 132.0 "TM Space Data Link Protocol” CCSDS 732.0 "AOS Space Data Link Protocol" CCSDS 133.0 "Space Packet Protocol" CCSDS 133.1 "Encapsulation Packet Protocol"

Table 19. Forward Data Functional Requirements for GEO-to-Cislunar DTE

X-band Ka-band Optical (1530 – 1565 nm)

Service Coverage S-Band: at least 83% of the sky within 45 degrees of the ecliptic X-Band: at least 83% of the sky within 45 degrees of the ecliptic Ka-Band: at least 70% of the sky within 45 degrees of the ecliptic

Lunar Service Coverage

Service-capable line of sight to user mission platforms for at least:

1) 95% communication coverage at the lunar south pole every day in NRHO

2) 95% of every day for lunar surface (subject to local terrain mask)

Space Service Interface

CLTU

ECLTU

File Frame

IP

Bitstream

Space Interface Protocol

CCSDS 142.0 "Optical Communications Coding and Synchronization" CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 231.0 "TC Synchronization and Channel Coding" CCSDS 131.0 "TM Synchronization and Channel Coding" CCSDS 232.0 "TC Space Data Link Protocol" CCSDS 132.0 "TM Space Data Link Protocol" CCSDS 732.0 "AOS Space Data Link Protocol" CCSDS 133.0 "Space Packet Protocol" CCSDS 133.1 "Encapsulation Packet Protocol" CCSDS 727.0 "CCSDS File Delivery Protocol (CFDP)" CCSDS 232.1 "Communications Operation Procedure-1"

Space Service Internetworking

End-to-end networking services to route data bundles using the DTN protocol suite

Bundle Protocol (BP) Licklider Transmission Protocol (LTP) Bundle Protocol Security (BPSEC) Encapsulation packet standard

Ground Service Interface

CLTU over TCP/IP

CLTU

Transfer Frame CADU over TCP/IP File with delivery meta-data (time, destination, forwarding) CCSDS frame over TCP/IP IP packets Bitstream data encapsulated over UDP/IP

Ground Interface Protocol Stack

CCSDS 913.1 "Space Link Extension--Internet Protocol for Transfer Services"

CCSDS 912.1 "Space Link Extension--Forward CLTU Service Specification"

CCSDS 912.11 "Space Link Extension--Enhanced Forward CLTU Service, Internet Protocol"

CCSDS 922.3 "Cross Support Transfer Service—Forward Frame Service"

Table 20. Return Data Functional Requirements for GEO-to-Cislunar DTE

X-band X-band (Space Research Service) Ka-band Optical (1530 – 1565 nm)

Service Coverage Receive a signal from a user mission platform in at least:

S-Band: 88% of the sky within 45 degrees of the ecliptic X-Band: 83% of the sky within 45 degrees of the ecliptic Ka-Band: 70% of the sky within 45 degrees of the ecliptic

Service Coverage Service-capable line of sight to user mission platforms for at least:

1) 95% of every day in NRHO

2) 95% of every day for lunar surface (subject to local terrain mask)

Multiple Spacecraft per Antenna (MSPA) Capability

Four or more simultaneous ground links configurable among the three bands (S, X, and Ka)

Acquire signals from up to four user mission platforms using a single antenna.

Space Service Interface All Frames Channel Frames Beacon Tone File Packet

IP

Bitstream

Space Interface Protocol Stack

CCSDS 142.0 "Optical Communications Coding and Synchronization" CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 131.0 "TM Synchronization and Channel Coding" CCSDS 132.0 "TM Space Data Link Protocol" CCSDS 732.0 "AOS Space Data Link Protocol" CCSDS 133.0 "Space Packet Protocol" CCSDS 133.1 "Encapsulation Packet Protocol" CCSDS 727.0 "CCSDS File Delivery Protocol (CFDP)"

Space Service Internetworking

End-to-end networking services to route data bundles using the DTN protocol suite

Bundle Protocol (BP) Licklider Transmission Protocol (LTP) Bundle Protocol Security (BPSEC) Encapsulation packet standard

Ground Service Interface

Stream of frames (including fill frames) over TCP/IP Stream of frames per each virtual channel over TCP/IP Tracking support File with delivery meta-data IP packets Bitstream data encapsulated over UDP/IP

Ground Interface Protocol Stack

CCSDS 911.1 "Space Link Extension--Return All Frames Service Specification"

CCSDS 911.2 "Space Link Extension--Return Channel Frames Service Specification"

CCSDS 911.5 “Space Link Extension—Return Operational Control Fields Service Specification”

CCSDS 913.1 " Space Link Extension--Internet Protocol for Transfer Services", Table 21. Tracking Functional Requirements for GEO-to-Cislunar DTE

Tracking Services Tone Ranging PN Ranging 1-way and 2-way Doppler Antenna Angle Data

Forward Spread Spectrum

Pseudo-Noise (PN) Spread Spectrum modulation on the forward links for radiometric tracking/ranging on X-Band

Space Service Interface Raw

Space Interface Protocol

CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 414.1 "Pseudo-Noise (PN) Ranging Systems"

Ground Service Interface

Range Doppler Angles (validated)

Ground Interface Protocol Stack

CCSDS 503.0 "Tracking Data Message" (TDM) standard or Universal Traffic Data Format (UTDF) for observables data contents as compliant with user needs and ICDs

4.2.3.2. GEO-to-Cislunar DTE Performance Requirements

The Contractor shall meet or exceed the following RF Signal Performance requirements. The Contractor shall provide secure services to meet the highest signal performance possible.

Space Interface Protocol

CCSDS 142.0 "Optical Communications Coding and Synchronization" CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 231.0 "TC Synchronization and Channel Coding" CCSDS 131.0 "TM Synchronization and Channel Coding" CCSDS 232.0 "TC Space Data Link Protocol" CCSDS 132.0 "TM Space Data Link Protocol" CCSDS 732.0 "AOS Space Data Link Protocol" CCSDS 133.0 "Space Packet Protocol" CCSDS 133.1 "Encapsulation Packet Protocol" CCSDS 727.0 "CCSDS File Delivery Protocol (CFDP)" CCSDS 232.1 "Communications Operation Procedure-1"

Space Service Internetworking

End-to-end networking services to route data bundles using the DTN protocol suite

Bundle Protocol (BP) Licklider Transmission Protocol (LTP) Bundle Protocol Security (BPSEC) Encapsulation packet standard

Ground Service Interface

CLTU over TCP/IP, CLTU, Transfer Frame, CADU over TCP/IP, File with delivery meta-data (time, destination, forwarding), CCSDS frame over TCP/IP, IP packets, Bitstream data encapsulated over UDP/IP

Ground Interface Protocol Stack

CCSDS 913.1 "Space Link Extension--Internet Protocol for Transfer Services"

CCSDS 912.1 "Space Link Extension—Forward CLTU Service Specification"

CCSDS 912.11 "Space Link Extension—Enhanced Forward CLTU Service, Internet Protocol"

CCSDS 922.3 "Cross Support Transfer Service—Forward Frame Service"

Table 27. Return Data Functional Requirements for xCislunar DTE

Frequency Bands

S-band X-band X-band (Space Research Service) Ka-band Optical (1530 – 1565 nm)

Service Coverage

Receive a signal from a user mission platform in at least:

S-Band: 88% of the sky within 45 degrees of the ecliptic X-Band: 83% of the sky within 45 degrees of the ecliptic Ka-Band: 70% of the sky within 45 degrees of the ecliptic

Sun-Earth Lagrange Service Coverage

Non-Continuous line of sight service coverage for user mission platforms at all azimuth angles and at elevation angles from 6 deg to 89.5 deg subject to antenna horizon masks

Multiple Spacecraft per Antenna (MSPA) Capability

Four or more simultaneous ground links configurable among the three bands (S, X, and Ka)

Acquire signals from up to four user mission platforms using a single antenna.

Space Service Interface All Frames Channel Frames Beacon Tone File Packet

IP

Bitstream

Space Interface Protocol Stack

CCSDS 142.0 "Optical Communications Coding and Synchronization" CCSDS 401.0 "Radio Frequency and Modulation Systems" CCSDS 131.0 "TM Synchronization and Channel Coding" CCSDS 132.0 "TM Space Data Link Protocol" CCSDS 732.0 "AOS Space Data Link Protocol" CCSDS 133.0 "Space Packet Protocol" CCSDS 133.1 "Encapsulation Packet Protocol"

Space Service Internetworking

End-to-end networking services to route data bundles using the DTN protocol suite

Bundle Protocol (BP) Licklider Transmission Protocol (LTP) Bundle Protocol Security (BPSEC) Encapsulation packet standard

Ground Service Interface

Stream of frames (including fill frames) over TCP/IP Stream of frames per each virtual channel over TCP/IP Tracking support File with delivery meta-data IP packets Bitstream data encapsulated over UDP/IP

Ground Interface Protocol Stack

CCSDS 911.1 "Space Link Extension--Return All Frames Service Specification"

CCSDS 911.2 "Space Link Extension--Return Channel Frames Service Specification"

CCSDS 911.5 “Space Link Extension—Return Operational Control Fields Service Specification”

CCSDS 913.1 " Space Link Extension--Internet Protocol for Transfer Services"

EP Earth Proximity ERT Earth Receive Time EAR Export Administration Regulations FCC Federal Communications Commission GEO Geosynchronous Equatorial Orbit HEO Highly Elliptical Orbit HTTPS Hypertext Transfer Protocol Secure IP Internet Protocol ISA Interconnection Security Agreement ITAR International Traffic in Arms Regulations IT Information Technology ITS Information Technology Security ITU International Telecommunications Union LCRNS Lunar Communication and Navigation System LEO Low Earth Orbit LN-IS LunaNet Interoperability Specification MAR Multiple Access Return MEO Medium Earth Orbit MISS Mission Integration and Special Studies NIST National Institute of Standards and Technology NPD NASA Policy Directive NPR NASA Procedural Requirements NSN Near Space Network NSNS Near Space Network Services NTIA National Telecommunications and Information Administration ODM Orbit Data Message PNT Position, Navigation, and Timing RF Radio Frequency SAR Search and Rescue SCaN Space Communications and Navigation SEL1/L2 Sun-Earth Lagrange Point #1 and #2 SLE Space Link Extension SLP Space Link Providers SM Service Management SOC Security Operations Center SOMD Space Operations Mission Directorate SOW Statement of Work SRD Systems Requirement Document SSF Simple Schedule Format TEM Technical Exchange Meeting TCP Transmission Control protocol TLE Two Line Element TO Task Order