Att 1 TRD 6 May 21.pdf

GNSS/Interference Wave-Front Simulator requirements 06 May 2021

782TS/RNWG has a requirement for a Global Navigation Satellite System (GNSS)/Interference Wave-Front simulator, henceforth referred to as the simulator for conciseness, that can present multiple simultaneous GNSS constellations and multiple jammers with a minimum of eight (8) RF output ports to support a single eight (8) element controlled radiation pattern antenna (CRPA)/antenna electronics (AE) or eight (8) fixed radiation pattern antenna (FRPA) assets. The simulator shall provide the following requirements and capabilities listed below in this document.

Any numbered item listed with a (C) is regarded as contemplative where it is not a requirement but a desired feature. Any numbered item without this designation shall be considered a requirement and must be provided by the simulator.

GNSS Signals

1. Global Positioning System (GPS) signals

a) Simulator shall provide the following GPS signals:

L1 C/A, L1C, L1P, L2P, L2C, L5, L1Y, and L2Y.

The L1Y and L2Y signals may be integrated into the simulator by means of a removable hardware/software module after initial simulator delivery. This L1Y and L2Y module shall be integrated no later than 16 June 2022.

Due to the controlled nature of the L1Y and L2Y signals and their definitions, in order for a vendor to be a viable candidate they must either be a company that is compliant with the following parameters or solicit the aid of a company that is compliant with the following parameters in order to integrate these signals on behalf of the vendor. The integrating company shall be: a United States (US) owned company, pre-approved by the GPS directorate (SMC), an active participant with the GPS Satellite Simulation Working Group (SSWG), and shall adhere to the latest technical requirements documentation for implementing Y-code on GPS simulators as directed by the GPS directorate.

2. M-Code support (AES, MNSA)

a) Simulator shall provide the following GPS signals:

M-AES, M-MNSA for both L1, L2.

The M-AES and M-MNSA signals may be integrated into the simulator by means of a removable hardware/software module after initial simulator delivery. This M-AES and M-MNSA module shall be integrated no later than 16 June 2022.

Due to the controlled nature of the M-AES and M-MNSA signals and their definitions, in order for a vendor to be a viable candidate they must either be a company that is compliant with the following parameters or solicit the aid of a company that is compliant with the following parameters in order to integrate these signals on behalf of the vendor. The integrating company shall be: a United States (US) owned company, pre-approved by the GPS directorate (SMC), an active participant with the GPS Satellite Simulation Working Group (SSWG), and shall adhere to the latest technical requirements documentation for implementing M-code on GPS simulators as directed by the GPS directorate.

3. GLONASS Signals:

Simulator shall provide the following open standard-precision GLONASS signals:

L1OF and L2OF.

4. BeiDou Signals: (C) Simulator shall provide the following signals:

B1i, B2i, B2a, and B1c.

These signals may be integrated into the simulator by means of a removable hardware/software module after initial simulator delivery.

5. Galileo Signals: (C)

E1, E5a, E5b, and E6.

6. QZSS Signals: (C)

L1-C/A, L1C, L2C, and L5.

7. Satellite-based Augmentation System (SBAS) Signals: (C)

Simulator shall provide following signals:

WAAS, EGNOS, MSAS, SDCM, and GAGAN.

8. Capable of additional Signals: (C)

NAVIC (L5 & S-band), AltNav, LAAS, and GBAS.

Almanac/Ephemeris

9. Simulator shall be capable of testing all GPS week roll overs from 1980 to 2060.

10. Simulator shall be capable of transferring the full GNSS message over ethernet via transmission control protocol/internet protocol (TCP/IP) and/or user datagram protocol (UDP/IP) upon user request.

11. Simulator shall be capable of adjusting future leap seconds forward & backward as desired.

12. Simulator shall support almanac and ephemeris updates as defined below.

a) Simulator shall be capable of multiple updates during a single scenario.

b) Simulator shall provide the ability to load ephemeris cut-overs every two, four, or six hour intervals for the GPS constellation.

c) Simulator shall provide full almanac updates every 12.5 minutes for the GPS constellation.

d) Simulator shall be capable of providing the appropriate almanac and ephemeris update rates and cut-overs for their respective GNSS constellation within the simulator.

Max Dynamics

13. Simulator shall provide signals for vehicle velocities from 0 to ≥ 9,000 m/s.

14. Simulator shall provide signals for vehicle accelerations from 0 to ≥ 1,500 m/s2.

15. Simulator shall provide signals for vehicle jerk from 0 to ≥ 400 m/s3.

Power/Coherent Phase control for GNSS & Jammers

16. Simulator shall create, maintain, and control radio frequency (RF) signals with regards to phase control and power adjustment range for GNSS satellite vehicles as described below.

a) Simulator shall maintain phase coherency between RF output elements for the GNSS carrier signal. (Threshold ≤ ±5°; Objective ≤ ±1°)

b) Simulator shall maintain phase coherency between RF output elements for the GNSS code signal. (Threshold ≤ ± 8ns; Objective ≤ ± 2ns)

c) Simulator shall provide a minimum operating range of 60dB for the following power limits

(dBm) within each RF output element while maintaining phase coherency. (Threshold - 140dBm to -80dBm; Objective -140dBm to -10dBm)

d) Simulator shall maintain a RF power level resolution for each GNSS signal. (Threshold ≤ ±1 dB; Objective ≤ ±0.01 dB)

e) Simulator shall provide the ability to attenuate individual SV power levels via ethernet TCP/IP or UDP/IP.

f) Simulator shall dynamically adjust phase between RF output elements based on the dynamic geometry between CRPA/AE receiver antenna elements and the RF transmitters of the GNSS constellation SV.

17. Simulator shall provide jamming signals as defined by the following parameters below.

a) Simulator shall maintain phase coherency between RF output elements for the jammer carrier signal. (Threshold ≤ ±5°; Objective ≤ ±1°)

b) Relative to a nominal signal power of -130 dBm, the simulator shall be capable of generating the following jammer to signal (J/S) ratio. (Threshold ≥ 120dB J/S; Objective ≥ 138dB J/S)

c) Coherent carrier phase shall be maintained as the power is attenuated between maximum

J/S to minimum J/S.

d) Simulator shall provide the following J/S power level resolution. (Threshold ≤ ±1 dB;

Objective ≤ ±0.01 dB)

e) Simulator shall dynamically adjust phase between RF output elements based on the dynamic geometry between CRPA/AE receiver antenna elements and RF jamming transmitters.

External Motion Control and Synchronization

18. Simulator shall process vehicle motion from an external source with the following parameters.

a) Simulator shall be able to process external motion data for no less than eight (8) motion data sets within the specified objective and threshold criteria. (Objective ≤ 1ms; Threshold ≤ 10ms)

b) Simulator shall have ability to process up to eight (8) simultaneous external motion data sets for FRPA receivers.

c) Simulator shall have ability to process one external motion vehicle for a CRPA/AE asset with

8 elements.

d) Simulator shall be capable of synchronizing with an external 10 MHz oscillator.

e) Simulator shall be capable of synchronizing the start of external motion data with a single pulse per second (PPS) synchronization pulse.

f) Simulator shall receive motion data sets via 10GB ethernet using TCP/IP and/or UDP/IP.

g) Simulator shall be capable of modifying the system internet protocol (IP) addresses for network configuration.

h) Simulator shall interpret external motion data using the following parameters:

• Coordinate frames in acceptable common standards shall be used: Earth-Centered Earth-Fixed (ECEF), Geodetic WGS84, North-East-Down (NED) and East-North-Up (ENU).

• Translational Position, translational velocity, translational acceleration, and translational jerk defined in x, y and z components

• Angular position, angular velocity, angular acceleration, and angular jerk defined in roll, pitch and yaw components

• GNSS time

i) Simulator shall be capable of processing external motion data in binary form.

Total Latency

19. Total latency (millisecond)

a) Simulator shall have a maximum total latency as specified by the threshold and objective criteria. (Threshold ≤ 20ms; Objective ≤ 5ms)

b) Simulator’s latency shall be deterministic. (Threshold ≤ 100µs; Objective ≤ 1µs)

Total latency is defined as the time between the receipt of kinematic vehicle motion data from the remote controller to RF output at the antenna element and shall be measured utilizing: eight (8) external motion vehicles, the jammers within the scenario, and the satellite vehicles that are active and visible to the respective geographic scenario.

CRPA/FRPA Control

20. Simulator shall have ability to use each element as a separate FRPA vehicle receiver via remote motion control.

21. Simulator shall be capable of attenuating each element via TCP/IP and/or UDP/IP commands from remote controller.

22. Simulator shall be capable of using the RF outputs to simulate combinations of CRPA/AE and FRPA antennas. Examples:

a) Two 4-element CRPA/AE

b) One 4-element CRPA/AE plus four (4) FRPA antennas

c) One 8-element CRPA/AE

Terrain Obscuration

23. Simulator shall provide Terrain Obscuration features as defined below. (C)

a) Simulator shall have capability of providing terrain obscuration, i.e. ability to block GNSS or jammer signals to the receiver as a result of blockage from terrain.

b) Simulator shall have ability to load external terrain data such as Digital Terrain Elevation data

(DTED).

c) Simulator shall be capable of multipath reflection for one GNSS constellation with following objectives and thresholds. (Threshold: 1 reflection per SV; Objective: 2 reflections per SV)

Multiple Coherent Jammers

24. Simulator is required to generate at a minimum of the following jamming techniques: Chirp, Continuous Wave (CW), Bi-Phase Shift Keying, Pulse CW, and spoofers.

25. Simulator shall be capable of providing multiple phased coherent jammers per RF output element.

(Objective 32 L1/L2 jammers; Threshold 12 L1/L2jammers)

26. Simulator shall be capable of the following jammer kinematics.

a) Simulator shall have the ability to place ground jammers at user specified GPS coordinates (latitude/longitude/altitude/attitude)

b) Shall have ability to provide flight kinematics for airborne jammers

i. Objective: External vehicle motion control of airborne jammers as specified in item 18 above.

ii. Threshold: User defined jammer with simulator embedded vehicle motion

27. Simulator shall adjust the Doppler frequency shift based on relative flight dynamics between GNSS receiver and jammers.

Calibration Requirements.

28. Simulator shall be capable of user performed carrier/code phase calibration.

29. Vendor shall provide documentation for carrier/code calibration procedure. (Threshold: Manual calibration; Objective: Automated calibration)

Antenna Modeling Requirements

30. Simulator shall have the ability to import an external GNSS receiver antenna file containing antenna gain/phase as function of azimuth and elevation with 1° resolution.

31. Simulator shall have the ability to import an external jammer antenna file containing antenna gain/phase as function of azimuth and elevation with 1° resolution.

32. Simulator shall have ability to specify lever arm for each antenna assembly in relation to center of gravity (CG) of flight motion vehicle in x, y, z, pitch, yaw, and roll components.

33. Simulator shall process the lever arm for each antenna element in relation to the center of the antenna assembly in x, y, z, pitch, yaw, and roll components.

Ancillary

34. Vendor shall provide an instruction manuals and documentation for the simulator.

35. Vendor shall provide on-site operational training.

36. Documentation shall define external motion data with their respective data types, associated precision, boundary alignment constraints as well endianness.

37. Vendor shall supply an acceptance test procedure (ATP) for a Factory Acceptance Test (FAT) of all systems/sub-systems 30 days prior to the test event and upon government concurrence of the procedure and post the test event, the vendor shall supply a report of the test with results. The purpose of the test is to demonstrate the compliance of the simulator to the requirements within this document.