MCP/gr-mcp-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
gr-mcp-docs/reference/cospas-sarsat/t-series/t020.md
Ryan Malloy 4ed92efd69 refactor: move spec references out of published site 
Cospas-Sarsat specification summaries moved to reference/ for internal
use only. Links updated to point to official cospas-sarsat.int site.

The extracted images remain in public/ for use in other pages.
2026-02-13 05:03:09 -07:00

7682 lines
173 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
title: "T020: (with markup)"
description: "Official Cospas-Sarsat T-series document T020"
sidebar:
badge:
text: "T"
variant: "note"
# Extended Cospas-Sarsat metadata
documentId: "T020"
series: "T"
seriesName: "Technical"
documentType: "specification"
isLatest: true
issue: 2
revision: 10
documentDate: "October 2025"
originalTitle: "C/S T.020 - Issue 2 Rev.10 (with markup)"
---
> **📋 Document Information**
>
> **Series:** T-Series (Technical)
> **Version:** Issue 2 - Revision 10
> **Date:** October 2025
> **Source:** [Cospas-Sarsat Official Documents](https://www.cospas-sarsat.int/en/documents-pro/system-documents)
---
COSPAS-SARSAT MEOLUT
COMMISSIONING STANDARD
C/S T.020
Issue 2 – Revision 10
NOTE
This document includes requirements yet to be determined or to be confirmed for beacons
moving at velocities between 5 and 10 m/s (i.e., “slow-moving medium speed”) and above 10 m/s
(“fast-moving” beacon). The values of these requirements are labelled as to be confirmed (TBC)
or appear in square brackets [ ] and their determination is ongoing.
![Image 1 from page 1](/images/cospas-sarsat/T-series/T020/T020_page_1_img_1.png)
COSPAS-SARSAT MEOLUT
COMMISSIONING STANDARD
HISTORY
Issue
Revision
Date
Comments
Approved by the Cospas-Sarsat Council (CSC-55)
Approved by the Cospas-Sarsat Council (CSC-57)
Approved by the Cospas-Sarsat Council (CSC-59)
Approved by the Cospas-Sarsat Council (CSC-60)
Approved by the Cospas-Sarsat Council (CSC-61)
Approved by the Cospas-Sarsat Council (CSC-62)
Approved by the Cospas-Sarsat Council (CSC-64)
Approved by the Cospas-Sarsat Council (CSC-65)
Approved by the Cospas-Sarsat Council (CSC-66)
Approved by the Cospas-Sarsat Council (CSC-67)
Approved by the Cospas-Sarsat Council (CSC-69)
Approved by the Cospas-Sarsat Council (CSC-71)
Approved by the Cospas-Sarsat Council (CSC-73)
TABLE OF CONTENTS
Page
History ..................................................................................................................................................... i
Table of Contents ................................................................................................................................... ii
List of Figures ....................................................................................................................................... iii
List of Tables ........................................................................................................................................ iii
1.
INTRODUCTION ........................................................................................................ 1-1
1.1
Purpose ..................................................................................................................... 1-1
1.2
Scope
..................................................................................................................... 1-1
1.3
Reference Documents................................................................................................. 1-1
2.
MEOLUT COMMISSIONING ................................................................................... 2-1
2.1
General ..................................................................................................................... 2-1
2.2
Pre-Test Requirements ............................................................................................... 2-1
2.3
Test Data Collection ................................................................................................... 2-2
2.4
Frequency Registration............................................................................................... 2-3
2.5
Data Collection Limitation ......................................................................................... 2-3
2.6
Reference System ....................................................................................................... 2-4
2.7
Submission of Results ................................................................................................ 2-4
2.8
MEOLUT Commissioning and Integration ................................................................ 2-4
2.9
MEOLUT/MCC Interface .......................................................................................... 2-4
2.10 Confirmation of Requirements ................................................................................... 2-4
2.11 Change of Configuration ............................................................................................ 2-5
2.11.1 Location of MEOLUT ................................................................................... 2-5
2.11.2 Modification to MEOLUT Configuration (eg, Addition of Satellite Channels,
Addition of Data Sources or Significant Change in the Processing) .......................... 2-6
3.
EVALUATION OF OPERATIONAL REQUIREMENTS ...................................... 3-1
3.1
MEOLUT Data Availability ....................................................................................... 3-1
3.2
Data Requirements ..................................................................................................... 3-1
3.3
Satellite Tracking and Visibility Capability ............................................................... 3-1
3.4
Status and Alarm ........................................................................................................ 3-1
3.5
RF Radiation and Emissions ...................................................................................... 3-1
3.6
Data Archiving ........................................................................................................... 3-1
4.
EVALUATION OF FUNCTIONAL AND PROCESSING REQUIREMENTS .... 4-1
4.1
Functional Requirements ............................................................................................ 4-1
4.1.1
Antenna and RF Subsystems ......................................................................... 4-1
4.1.2
Time and Frequency Reference Subsystem ................................................... 4-1
4.1.3
Satellite Tracking Subsystem ......................................................................... 4-1
4.1.4
MCC Interface ............................................................................................... 4-1
4.2
Beacon Message Processing ....................................................................................... 4-1
5.
EVALUATION OF PERFORMANCE REQUIREMENTS .................................... 5-1
5.1
Data Collection Test ................................................................................................... 5-1
5.1.1
Test Beacons .................................................................................................. 5-1
5.1.2
Satellite Tracking Schedule ........................................................................... 5-2
5.2
Detection and Location Statistics ............................................................................... 5-2
5.3
Detection and Location Data ...................................................................................... 5-2
LIST OF ANNEXES
ANNEX A MEOLUT COMMISSIONING REPORT
ANNEX B STATISTICS FOR OPERATIONAL REQUIREMENTS
ANNEX C STATISTICS FOR PERFORMANCE REQUIREMENTS
ANNEX D BEACON SIMULATOR TEST SCRIPT
ANNEX E DATA FORMAT
ANNEX F MEOLUT COMMISSIONING - PRINCIPLES AND POLICIES
ANNEX G GUIDELINES FOR INTEGRATION OF NEW MEOLUTS IN THE
COSPAS-SARSAT SYSTEM
ANNEX H GUIDELINES FOR REGISTRATION OF NEW MEOLUTS WITH ITU
LIST OF FIGURES
Figure C.1: (Location Error)/EHE Cumulative Distribution ............................................................. C-7
Figure G.1: Overview of MEOLUT Integration ................................................................................ G-3
LIST OF TABLES
Table A.1: MEOLUT Commissioning Summary Data Table (General Part) .................................... A-2
Table A.2: MEOLUT Commissioning Summary Data Table (C/S T.001 Beacon Part) ................... A-3
Table A.3: MEOLUT Commissioning Summary Data Table (C/S T.018 Beacon Part) ................... A-9
Table A.4: MEOLUT Test Beacon Location Table ......................................................................... A-18
Table A.5: Implementation Status of MEOLUT Critical Changes .................................................. A-19
Table A.6: MEOLUT Antenna Location Table ............................................................................... A-20
Table E.1: Description of the Fields .................................................................................................. E-1
Table E.2:MEOLUT Satellite Tracking ............................................................................................. E-1
Table E.3: Beacon Message Data ...................................................................................................... E-2
Table E.4: MEOLUT Solution Data .................................................................................................. E-4
Table E.6: Beacon Database Description ........................................................................................... E-6
Table E.7: Beacon Test Script Log .................................................................................................... E-6
1-1
1.
INTRODUCTION
1.1
Purpose
The Cospas-Sarsat MEOLUT Commissioning Standard shall be used to verify that a MEOSAR Local
User Terminal (MEOLUT) complies with document C/S T.019, “Cospas-Sarsat MEOLUT
Performance Specification and Design Guidelines”. The national Administrations that wish to connect
a new MEOLUT to the Cospas-Sarsat network shall conduct the tests and provide the data, which is
specified in this document, to the Cospas-Sarsat Secretariat. The MEOLUT to be commissioned shall
be fully described according to the technical file located in Annex A, Appendix 1.
1.2
Scope
This standard specifies MEOLUT commissioning for the 406 MHz data channels that are relayed
through the MEOSAR satellites and received and processed by the MEOLUT. Section 2 defines the
general commissioning process, section 3 describes the evaluation of the operational requirements,
section 4 specifies the commissioning of functional and processing requirements, and section 5
specifies the commissioning of performance requirements. The annexes define the test requirements,
signal characteristics, test beacon messages, the format of the test data which is to be collected, and
the format of the commissioning report which is to be submitted to the Cospas-Sarsat Secretariat.
1.3
Reference Documents
The following documents contain useful information applicable to MEOLUT commissioning:
Reference
Title
C/S A.001
Cospas-Sarsat Data Distribution Plan (DDP)
C/S A.002
Cospas-Sarsat Mission Control Centres Standard Interface Description (SID)
C/S A.003
Cospas-Sarsat System Monitoring and Reporting
C/S A.005
Cospas-Sarsat MCC Performance Specification and Design Guidelines
C/S A.006
Cospas-Sarsat MCC Commissioning Standard
C/S T.001
Specification for Cospas-Sarsat 406 MHz Distress Beacons
C/S T.006
Cospas-Sarsat Orbitography Network Specification
C/S T.011
Description of the 406 MHz Payloads Used in the Cospas-Sarsat GEOSAR System
C/S T.016
Description of the 406 MHz Payload Used in the Cospas-Sarsat MEOSAR System
C/S T.015
Cospas-Sarsat Specification and Type Approval Standard for 406 MHz Ship
Security Alert (SSAS) Beacons
C/S T.017
Cospas-Sarsat MEOSAR Space Segment Commissioning Standard
C/S T.018
Specification for Second Generation Cospas-Sarsat 406 MHz Distress Beacons
C/S T.019
Cospas-Sarsat MEOLUT Performance Specification and Design Guidelines
- END OF SECTION 1 -
2-1
2.
MEOLUT COMMISSIONING
2.1
General
The Cospas-Sarsat MEOLUT commissioning tests defined in this document are intended to be
performed in addition to national acceptance tests, and are required prior to fully integrating a
MEOLUT into the Cospas-Sarsat Ground Segment. Conducting these tests and assessing the results is
the responsibility of the national Administration that desires to commission a MEOLUT.
The tests verify the MEOLUT's ability to receive and process signals transmitted from a distress beacon
that is compliant with document C/S T.001, “Specification for Cospas-Sarsat 406 MHz Distress
Beacons” or document C/S T.018, “Specification for Second Generation Cospas-Sarsat 406 MHz
Distress Beacons”, relayed by the MEOSAR satellites described in document C/S T.016, “Description
of the 406 MHz Payload Used in the Cospas-Sarsat MEOSAR System”, and received and processed
in accordance with document C/S T.019. A cross reference of the requirements in document C/S T.019
and the corresponding commissioning requirements specified in this document is provided in the
“Summary Table” of the commissioning report (Annex A). The tests shall be conducted with the
MEOLUT in its operational configuration and location, and connected to the associated MCC.
However, the data should not be distributed to other Cospas-Sarsat Ground Segment Operators.
The MEOLUT may provide optional capabilities as described in document C/S T.019, such as:
1. the MEOLUT may provide 406 MHz beacon data to other MEOLUTs according to the
specifications contained in document C/S T.019,
2. the MEOLUT may process 406 MHz beacon data retrieved from other commissioned
MEOLUTs according to the MEOLUT data exchange specifications contained in C/S T.019 to
enhance system performance and support redundancy of the Cospas-Sarsat Ground Segment,
3. the ability to receive and process beacon signals received through downlinks from non-
MEOSAR, Cospas-Sarsat commissioned satellites to obtain beacon data.
The MEOLUT must initially be commissioned with all optional capabilities disabled according to the
non-optional tests described in Annex A. The optional capabilities, if to be used, must then be
commissioned to verify that the MEOLUT meets all requirements as described by the optional tests
contained in Annex A.
2.2
Pre-Test Requirements
Prior to commencing the test, the national Administration conducting the test shall coordinate with
appropriate authorities in its SAR region, as well as notifying all affected Cospas-Sarsat MCCs, of the
periods of operation and the location(s) of each of the test beacon(s). It is also invited to provide this
information to the Cospas-Sarsat Secretariat.
2-2
Prior to commencing the tests, the national Administration in consultation with the MEOLUT
manufacturer must identify the Declared Coverage Area (DCA) of the MEOLUT, as described in
document C/S T.019 and in section A.5 of this document. The DCA must be verified using performance
analysis, simulation, or both, and must be equal to or greater than the Minimum Performance Area
defined in document C/S T.019. The DCA must
indicate the declared coverage for each beacon identified in document C/S T.019; that is:
•
the declared coverage for non-ELT(DT) C/S T.001 beacons, where relevant performance
specifications are met,
•
the declared coverage for ELT(DT) C/S T.001 beacons, where relevant performance
specifications are met,
•
the declared coverage for non-ELT(DT) C/S T.018 beacons, where relevant performance
specifications are met,
•
the declared coverage for ELT(DT) C/S T.018 beacons, where relevant performance
specifications are met.
Assumptions with respect to visibility as per Annex D of document C/S T.019 and TOA/FOA data
quality and single-channel throughput used in the analysis or simulation should be validated with data
from Annex E.
The MEOLUT shall be commissioned with all assets that comprise the MEOLUT. However, if the
DCA assumes fewer assets, for example, fewer antenna beams, then commissioning results shall also
be reported for a MEOLUT in that configuration. In particular, if fewer antenna beams are used for the
DCA, only data that results from an antenna tracking schedule generated using the fewer number of
antenna beams shall be used in generating the results. This may result in the need for two sets of results,
one for the MEOLUT with all available assets, and one for the MEOLUT with the configuration needed
for the DCA.
2.3
Test Data Collection
The commissioning process for the MEOLUT comprises the collection of specific beacon messages
and the specified numbers of solutions. The MEOLUT shall utilize beacon data received directly from
downlinks from MEOSAR satellites for the data acquisition and statistical data analysis for the
commissioning tests.
Data collection requirements for commissioning a MEOLUT’s optional capabilities are as follows:
1. The MEOLUT, once commissioned, may provide 406 MHz beacon data to other MEOLUTs
according to the specifications contained in document C/S T.019. Data collected directly from
downlinks from commissioned MEOSAR satellites that comply with document C/S T.016,
“Description of the 406 MHz Payload Used in the Cospas-Sarsat MEOSAR System” and
document C/S T.017 “Cospas-Sarsat MEOSAR Space Segment Commissioning Standard”
shall be used for the data acquisition and statistical data analysis for the commissioning tests.
2. The MEOLUT may process 406 MHz beacon data retrieved from other commissioned
MEOLUTs according to the MEOLUT data exchange specifications contained in document
2-3
C/S T.019. Data from every commissioned MEOLUT that will provide data to the MEOLUT
being commissioned shall be used for the data acquisition and statistical data analysis for the
commissioning tests.
3. The MEOLUT has the ability to receive and process beacon signals received through
downlinks from non-MEOSAR, Cospas-Sarsat commissioned satellites to obtain beacon data.
Data collected from every non-MEOSAR, Cospas-Sarsat commissioned satellite that will be
used shall be included in the data acquisition and statistical data analysis for the commissioning
tests.
2.4
Frequency Registration
Administrations should register their MEOLUT’s use of the 1544 to 1545 MHz frequency band by
“notifying” their MEOLUTs with the International Telecommunication Union (ITU) in accordance
with article 11 of the radio regulations. The information required to notify MEOLUTs is identified at
Annex H. The ITU only accepts notification requests submitted in electronic format and has developed
a software application, available free of charge from their web site, which captures the required
information and produces the necessary electronic file.
2.5
Data Collection Limitation
Only the data collected from those satellite channels that comply with documents C/S T.016 and
C/S T.017 shall be used for the statistical data analysis. Data from satellites in an Initial Operational
Capability (IOC) status should not be used for test data collection.
The data collection limitations for commissioning a MEOLUT’s optional capabilities are as follows:
1. The MEOLUT once commissioned may provide 406 MHz beacon data to other MEOLUTs
according to the specifications contained in document C/S T.019. Only the data collected from
those satellite channels that comply with documents C/S T.016 and C/S T.017 shall be used for
the statistical data analysis. Data from satellites in an Initial Operational Capability (IOC) status
should not be used for test data collection.
2. The MEOLUT may process 406 MHz beacon data retrieved from other commissioned
MEOLUTs according to the MEOLUT data exchange specifications contained in C/S T.019 to
enhance system performance and support redundancy of the Cospas-Sarsat Ground System.
Only data that has been retrieved from another MEOLUT that has also been commissioned to
provide 406 MHz beacon data to other MEOLUTs may be used.
3. The MEOLUT may have the ability to receive and process beacon signals received through
downlinks from non-MEOSAR, Cospas-Sarsat commissioned satellites to obtain beacon data.
Only the data collected from commissioned satellites shall be used. Data from satellites in an
Initial Operational Capability (IOC) status should not be used for test data collection.
2-4
2.6
Reference System
All location data for the MEOLUT commissioning shall be given with respect to the Bureau
International de l’Heure (BIH) geodetic reference system.
2.7
Submission of Results
The results of the MEOLUT commissioning process shall be documented in the commissioning report,
in accordance with the format detailed at Annex A.
The complete commissioning report and the data files detailed at Annex E are to be submitted to the
Cospas-Sarsat Secretariat for further evaluation, and distribution to Participants for subsequent review
at the Joint Committee. Revisions or updates to commissioning reports should be provided to the
Secretariat with a clear indication given on the cover page of the sections that have been revised and a
short description of the nature of the revisions.
In order to provide Participants with sufficient time to adequately review the commissioning report, all
reports (or updates) must be submitted to the Secretariat a minimum of six weeks prior to the start of
the Joint Committee meeting. Submissions received after this date will be considered for review at the
following Joint Committee meeting.
2.8
MEOLUT Commissioning and Integration
The test results, as defined in the annexes, shall be submitted to the Cospas-Sarsat Secretariat. The
results will be reviewed by the Cospas-Sarsat Secretariat and submitted to the Joint Committee. The
MEOLUT will be integrated into the Cospas-Sarsat Ground Segment as described in Annex F and
Annex G.
2.9
MEOLUT/MCC Interface
Validation that the MEOLUT/MCC interface satisfies the minimum requirements of document
C/S T.019 shall be completed by the national Administration as part of the MEOLUT commissioning.
2.10
Confirmation of Requirements
The national Administration shall confirm compliance to all requirements detailed in this document
with either a measurement, a verification, a declaration, analysis or a combination of these methods:
a) A measurement requires the national Administration to conduct a test and include the
supporting data as part of the commissioning report.
b) A verification requires a national Administration to test a requirement; however, supporting
data does not need to be provided as part of the commissioning report.
2-5
c) A declaration of compliance confirms that specific requirements are met although not
necessarily tested as part of the commissioning process.
d) Analysis requires the national Administration to provide analysis as part of the commissioning
report that confirms that specific requirements are met.
Conformance to all requirements shall be documented in the commissioning report.
The exact method of confirming compliance for each respective requirement is identified in the
summary table of the commissioning report (Annex A).
For requirements, whose compliance are confirmed by measurement, Annex A indicates whether the
measurement must be done after installation at the installation site (S) or can alternatively be done at
the vendor’s facility (F). Measurements done at the vendor’s facility must follow the same procedures
as specified for testing done at the installation site, including the provision of test data.
Annex A also indicates which measurements can be confirmed using results from prior commissioning
of the same hardware and software versions (P). Any changes in the hardware or software version that
are claimed to be equivalent must be justified by the commissioning authority.
2.11
Change of Configuration
2.11.1
Location of MEOLUT
If the location of a commissioned MEOLUT has been changed, the responsible national Administration
shall ensure that the MEOLUT continues to satisfy C/S T.019 requirements prior to resuming
operations. Additionally, the national Administration shall:
a) confirm that the level of local interference does not adversely affect the MEOLUT
performance;
b) verify the performance of the communication links;
c) verify the performance of the antenna and RF subsystems; and
d) update the technical file of the MEOLUT commissioning report (Appendix 1 to Annex A
refers) by providing a declaration that the MEOLUT satisfies C/S T.019 requirements and the
following information, to the Cospas-Sarsat Secretariat:
•
Antenna Characteristics (Annex A, Appendix 1, section A.2.1),
•
General LUT Indoor Equipment Description (Annex A, Appendix 1, section A.2.2) -
identify any changes to the equipment configuration, or indicate “no change” if the
configuration has not been changed,
•
General Capabilities (Annex A, Appendix 1, section A.2.3), - identify any changes to the
general capabilities of the MEOLUT, or indicate “no change” if appropriate,
•
Communications Capability (Annex A, Appendix 1, section A.4),
•
Declared Coverage Area (Annex A, Appendix 1, section A.5),
2-6
•
Location (Annex A, Appendix 1, section A.6).
2.11.2
Modification to MEOLUT Configuration (e.g., Addition of Satellite Channels, Addition
of Data Sources or Significant Change in the Processing)
If the configuration of a commissioned MEOLUT has been changed, the responsible national
Administration shall ensure that the MEOLUT continues to satisfy C/S T.019 requirements prior to
resuming operations. After the configuration change, Administrations shall confirm the MEOLUT
satisfies C/S T.019 before distributing data from the MEOLUT operationally. Additionally, the
national Administration shall:
a.
verify the performance of the antenna and RF subsystems if adding a new antenna or a new
channel;
b.
provide updated Tables A.1, A.2 and A.3, and conduct tests defined in Annex A, at least for
performance testing related to section 5 of document C/S T.019;
c.
update the technical file of the MEOLUT commissioning report (Appendix 1 to Annex A
refers) by providing a declaration that the MEOLUT satisfies C/S T.019 requirements and the
following information, to the Cospas-Sarsat Secretariat:
i.
Antenna Characteristics (Annex A, Appendix 1, section A.2.1) if adding a new antenna,
or indicate “no change” if the configuration has not been changed,
ii.
General LUT Indoor Equipment Description (Annex A, Appendix 1, section A.2.2) -
identify any changes to the equipment configuration, or indicate “no change” if the
configuration has not been changed,
iii.
General Capabilities (Annex A, Appendix 1, section A.2.3), - identify any changes to the
general capabilities of the MEOLUT, or indicate “no change” if appropriate,
iv.
Communications Capability (Annex A, Appendix 1, section A.4),
v.
Declared Coverage Area (Annex A, Appendix 1, section A.5).
In general, any change that is determined to potentially impact MEOLUT performance, especially
beacon alert detection or location performance, requires retesting to verify that the MEOLUT continues
to satisfy C/S T.019 requirements. National Administrations shall make this determination, possibly
with consultation with the MEOLUT vendor and Cospas-Sarsat experts.
Some conditions that may be considered a change in configuration that would warrant conducting these
tests might include:
a.
adding a new antenna or channel to a commissioned MEOLUT;
b.
removing an antenna or channel from a commissioned MEOLUT;
c.
adding data collection from other commissioned MEOLUTs that exchange data according to
the MEOLUT data exchange specifications contained in document C/S T.019;
d.
significant modifications to the MEOLUT processing algorithm(s), other software, or
hardware;
e.
implementing major new functionality/critical change (e.g., processing of a new beacon
standard), if required by Council; and
f.
Addition or removal of a satellite constellation.
The responsible administration shall submit results of its verification of MEOLUT performance in a
supplementary commissioning report to the Joint Committee meeting for subsequent review.
2-7
- END OF SECTION 2 -
3-1
3.
EVALUATION OF OPERATIONAL REQUIREMENTS
3.1
MEOLUT Data Availability
The MEOLUT data availability shall be measured during the commissioning period in accordance with
guidance provided at Annex B. If any basic function or requirement is not performed by the MEOLUT,
the MEOLUT data shall be considered unavailable.
A reliability assessment is performed by measurement during the commissioning period and by an
analysis that predicts the availability for a one-year period to verify that the MEOLUT will meet the
availability requirement in accordance with guidance provided at Annex B.
3.2
Data Requirements
The national Administration shall ensure that the MEOLUT provides the data necessary for the
associated MCC to distribute alert data according to document C/S A.002 (SID). This shall be verified
and noted in the appropriate section of the MEOLUT commissioning report.
3.3
Satellite Tracking and Visibility Capability
The national Administration shall ensure that the MEOLUT shall be capable of meeting the
requirements of section 3.4 in document C/S T.019. This shall be declared in the appropriate section
of the MEOLUT commissioning report.
3.4
Status and Alarm
The national Administration shall describe the status and alarm functions of the MEOLUT and declare
compliance in the appropriate section of the MEOLUT commissioning report.
3.5
RF Radiation and Emissions
The national Administration shall ensure that the MEOLUT does not radiate or emit any radio
frequency signals that will interfere with the functioning of the Cospas-Sarsat System. This shall be
declared in the appropriate section of the MEOLUT commissioning report.
3.6
Data Archiving
The national Administration shall describe the data archiving capability of the MEOLUT and declare
compliance to the relevant section of document C/S T.019 in the appropriate section of the MEOLUT
commissioning report.
- END OF SECTION 3 -
4-1
4.
EVALUATION OF FUNCTIONAL AND PROCESSING REQUIREMENTS
4.1
Functional Requirements
4.1.1
Antenna and RF Subsystems
The national Administration shall verify that the antenna and RF subsystems of the MEOLUT can
acquire, track and receive the downlink signals from any Cospas-Sarsat MEOSAR satellites as
described in document C/S T.016. This verification shall be documented in the MEOLUT
commissioning report.
4.1.2
Time and Frequency Reference Subsystem
The national Administration shall declare in the MEOLUT commissioning report, the MEOLUT’s
capability to maintain time and frequency subsystems according to document C/S T.019.
4.1.3
Satellite Tracking Subsystem
The national Administration shall declare, in the MEOLUT commissioning report, the MEOLUT’s
capability to maintain accurate satellite orbital elements and tracking schedules as described in
document C/S T.019.
4.1.4
MCC Interface
The national Administration shall verify that the MEOLUT provides timely alert data of the level of
quality and detail specified in documents C/S T.019, C/S A.002 and C/S A.005, “Cospas-Sarsat
Mission Control Centre Performance Specification and Design Guidelines”. This verification shall be
documented in the MEOLUT commissioning report.
The national Administration shall declare in the MEOLUT commissioning report the methodology
used by the MEOLUT to determine when an independent-location solution has a better location quality
than solutions previously sent to the MCC, so that the better-quality solution would then be sent to the
associated MCC.
4.2
Beacon Message Processing
The national Administration shall conduct tests, and record the results in the appropriate section of the
commissioning report, which confirm the MEOLUTs compliance to the “channels processing
specifications” detailed in document C/S T.019.
These tests require the MEOLUT to process the data described at Annex D.1 in the manner prescribed.
The processing consists of bit verification, message validation, message processing and transmission.
The specific beacon test messages contained at Annex D.1 can be transmitted by a test beacon or a
beacon simulator.
4-2
National Administrations should ensure that test beacons or simulators are capable of transmitting the
beacon messages at the frequencies described at Annex D.1. Alternatively, national Administrations
may arrange for the simulators in the United States or France to uplink the messages contained at
Annex D.1. If the test messages cannot be transmitted during the commissioning period, the national
Administration may develop alternative methods of confirming compliance with the beacon message
processing requirements and proceed with the commissioning test, and preparation and submission of
the commissioning report. For beacon message processing, the unavailability of the test beacon or
simulators to uplink the test messages contained at Annex D.1 shall not prevent the MEOLUT from
being commissioned, if other adequate methods are used. If alternative methods are used, these
methods shall be completely documented in the commissioning report.
- END OF SECTION 4 -
5-1
5.
EVALUATION OF PERFORMANCE REQUIREMENTS
The national Administration shall conduct the tests defined at Annex C to confirm conformance with
the MEOLUT performance requirements detailed at document C/S T.019. The results of these tests
shall be included in the MEOLUT commissioning report. Additional guidance pertaining to the tests
detailed at Annex C is provided in the remainder of this section.
5.1
Data Collection Test
Tests shall be conducted to confirm that the MEOLUT processing satisfies the performance
requirements detailed in document C/S T.019.
All data collected from test beacons during the entire time period of the commissioning test shall be
used to generate statistics that validate the performance requirements are met.
All data and results shall be provided electronically to the Secretariat as part of the commissioning
report. The required data elements and the format of the files to be included in the commissioning
report are detailed in Annex E.
5.1.1
Test Beacons
Beacon tests shall be conducted with type-approved Cospas-Sarsat 406 MHz beacons coded with the
test protocol and/or beacon simulators (i.e., not an orbitography beacon), as described in document
C/S T.022. The beacons that are used for these tests shall not be used for updating the satellite orbital
elements. However, any reference beacon that is not used by the MEOLUT for the determination of
satellite orbits may be used as a test beacon during the commissioning of the MEOLUT. The
characteristics of all beacons used during commissioning shall be described in the commissioning
report.
Each test beacon must be placed as described below at a 3D position that is known to within 5 metres,
and shall remain fixed at this position throughout the test (except for tests involving moving beacons).
For tests involving moving beacons, a reference trajectory (set of time/latitude/longitude/altitude
points) shall be provided with a sufficient accuracy (e.g., 10 m for SGB, 100 m for FGB; the location
accuracy of the reference trajectory shall be reported for review). The test beacon locations shall be
given with respect to the reference system given in section 2.6.
1)
Use test beacon(s) located at the MEOLUT to perform all commissioning tests to verify the
MEOLUT meets all performance requirements.
2)
Use 1 or more test beacon(s) located as near the edge of the Declared Coverage Area as practical
or at least 1,000 km from the MEOLUT, to demonstrate the MEOLUT Declared Coverage Area.
These tests require the MEOLUT to process the data described at Annex D.3 in the manner prescribed.
The processing consists of beacon detection probability, probability of DOA location, DOA location
5-2
accuracy, TOA/FOA measurement accuracy (if applicable), and expected horizontal error / quality
factor. The specific beacon test messages contained at Annex D.3 can be transmitted by a test beacon
or a beacon simulator.
Beacons, and their set-up, used for the moving test configurations shall be documented in the
commissioning report. Their location and velocity as a function of time shall be reported in the
commissioning report. The beacon velocity profile should include velocities in a nearly static
configuration and in a slow-moving configuration, as well as the transition between these regimes.
National Administrations should ensure that test beacons or simulators are capable of transmitting the
beacon messages at the frequencies described at Annex D.3. Alternatively, national Administrations
may arrange for the simulators in the USA or France to uplink the messages contained at Annex D.3.
If the test messages cannot be transmitted during the commissioning period, the national
Administration may develop alternative methods of confirming compliance with the beacon message
processing requirements and proceed with the commissioning test, and preparation and submission of
the commissioning report. The unavailability of the test beacon or simulators to uplink the test
messages contained at Annex D.3 shall not prevent the MEOLUT from being commissioned, if other
adequate methods are used. If alternative methods are used, these methods shall be completely
documented in the commissioning report.
If test beacons transmit in the operational 406 MHz frequency band or if beacon bursts are transmitted
using the normal frame synchronization pattern, the total number of beacons simultaneously active
shall not exceed 5.
5.1.2
Satellite Tracking Schedule
Beacon tests shall consist of receiving and processing data on all scheduled passes from the
commissioned satellites that are visible during the test period. All available data channels shall be used
for the collection of data from available satellites during this data collection test.
5.2
Detection and Location Statistics
Statistics will be reported for beacons identified in section 5.1.1, item 1, and separately for those
identified in item 3.
Statistics will be also reported for all orbitography/reference beacons defined in document C/S A.001.
The statistics are defined in Annex A and shall be derived as listed in Annex C.
5.3
Detection and Location Data
The detection and location data from all tracked satellite passes shall be provided for each test beacon
used during the test period.
5-3
A minimum of 1,000 beacon burst transmissions shall be used to establish the detection data statistics
for both C/S T.001 and C/S T.018 beacons. A minimum of 1,000 location data solutions shall be used
to establish the location data statistics for both C/S T.001 and C/S T.018 beacons.
A minimum of 100,000 detections shall be used to establish the processing anomaly statistics.
- END OF SECTION 5 -
A-1
ANNEX A
MEOLUT COMMISSIONING REPORT
Country or national Administration:
_______________
Cospas-Sarsat Identifier:
_______________
Location of MEOLUT:
_______________
Start of Commissioning Period:
_______________
End of Commissioning Period:
_______________
Commissioning documents versions
C/S T.019, Issue [XX], Revision [XX]
C/S T.020, Issue [XX], Revision [XX]
Section A.1 contains a summary of the commissioning results as well as the analysis (A), declarations
(D) and verifications (V), by the national Administration, for requirements not specifically measured
(M). The organization of the summary table follows the requirements contained in document
C/S T.019.
For requirements, whose compliance are confirmed by measurement, section A.1 indicates whether
the measurement must be done after installation at the installation site (S) or can alternatively be done
at the vendor’s facility (F). Measurements done at the vendor’s facility must follow the same
procedures as specified for testing done at the installation site, including the provision of test data.
Section A.1 also indicates which measurements can be confirmed using results from prior
commissioning of the same hardware and software versions (P). Any changes in the hardware or
software version that are claimed to be equivalent must be justified by the commissioning authority.
For every requirement, if there is no indication in Tables A.1, A.2 and A.3 of whether a requirement
can be confirmed on site (S), at vendor’s facility (F) or from previous commissioning (P), the
requirement must be verified on site.
Section A.2 contains the measurements (M) to support the results presented in section A.1, a copy of
the associated data is provided in electronic format as required by this document. A technical
description of the MEOLUT is presented in Appendix 1.
Section A.3 contains a summary table providing the implementation status of the MEOLUT critical
changes decided by the Council.
A-2
A.1
Summary Table
Tables A.1, A.2 and A.3 shall be provided in full in the commissioning report (for initial or subsequent
commissioning), with rows not applicable showing as greyed out.
Table A.1: MEOLUT Commissioning Summary Data Table (General Part)
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F) or
Installation
Site (S)
Prior
Results (P)
or not
3.1
MEOLUT Data Availability
A≥95
2.1.1
M, A
S
No
3.2
Data Requirements
n/a
n/a
D, V
Verify capability to use
standard formats in Table 3.1
of C/S T.019. If non-standard
formats will be used, declare
and verify this capability.
3.3.1
Satellite Data Channels
Minimum
MEOSAR
n/a
V
3.3.2
MEOLUT Data Exchange
n/a
n/a
D
Only applicable to MEOLUTs
which exchange data with
other MEOLUTs
3.4
Satellite Tracking and
Visibility
n/a
n/a
V
3.5
Status and Alarm
n/a
n/a
D
Include description in
technical file
3.6
RF Radiation and Emissions
n/a
n/a
D
3.7
Data Archiving
n/a
n/a
D
3.8
QMS
n/a
D
4.1.1
Antenna and RF Subsystem
n/a
n/a
V
4.1.2
Time and Frequency
Reference Subsystem
n/a
n/a
V
4.1.3
Satellite Tracking
Subsystem
All MEOSAR
satellites
n/a
D
4.1.4
MCC Interface
n/a
n/a
V
4.2.8
MEOLUT Data Exchange
See C/S T.019
Annex C
n/a
D
Only applicable to MEOLUTs
which exchange data with
other MEOLUTs
4.2.9
Time and Frequency
Requirements
n/a
n/a
D
4.2.10
Independent Location
Processing
n/a
n/a
V
Check generation of location
and validity
4.2.11
Transmitting Data
to the MCC
n/a
n/a
V
Using MCC message log table
as defined in Annex E.
See additional tests for-
ELT(DT) beacons in Tables
A.2 and A.3
Declared Coverage Area
(for each beacon identified
in document C/S T.019)
n/a
Appendix 1,
A.5
A and/or V
See section Appendix 1,
section A.5
A-3
Table A.2: MEOLUT Commissioning Summary Data Table (C/S T.001 Beacon Part)
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results
(P) or
not
4.2.2
Beacon Message Recovery
Exact match on 9
Bit Frame Synch
n/a
D
Achieve identical match on 9 bit frame
synchronization
4.2.1
(see para
2.2.4.B to
C/S T.001)
Bit Rate Tolerance Check
Test - BR1
M/N>0.75
2.2.1
M
For 396 bps
F
P
M
For 404 bps
F
P
4.2.3.1
Bit Verification Test - BV1
See Annex D.1
2.2.2
M
F
P
Bit Verification Test - BV2
See Annex D.1
2.2.2
M
F
P
Bit Verification Test – BV3
See Annex D.1
2.2.2
M
F
P
4.2.4.1
Beacon Message Validation
Test - MV1
See Annex D.1
2.2.3
M
F
P
Beacon Message Validation
Test - MV2
See Annex D.1
2.2.3
M
F
P
Beacon Message Validation
Test – MV5
See Annex D.1
2.2.3
M
F
P
Beacon Message Validation
Test – MV6
See Annex D.1
2.2.3
M
F
P
4.2.5.1
Invalid Message Processing
Test – IMP1
See Annex D.1
2.2.4
M
F
P
4.2.6.1
Beacon Message Processing
Test - LP1
See Annex D.1
2.2.5
M
F
P
Beacon Message Processing
Test - LP2
See Annex D.1
2.2.5
M
F
P
Beacon Message Processing
Test - LP3
See Annex D.1
2.2.5
M
F
P
Beacon Message Processing
Test - LP4
See Annex D.1
2.2.5
M
F
P
4.2.6.1 and
4.2.11
Return Link
Test – RL1
See Annex D.1
2.2.6
M
F
P
4.2.7
Multiple valid message
processing
n/a
2.2.7
D
4.2.11
Transmitting Data
to the MCC
n/a
n/a
V
Using MCC message log table as
defined in Annex E
2.2.8
M
For C/S T.001 ELT(DT) beacons using
script in section D.3.2.2
F
P
5.1
RF Signal Margin
n/a
n/a
D
5.2.1
Signal Sensitivity
Signal sensitivity
better than
34.8 dB-Hz
D
5.3.1
Beacon Message Detection
Probability
(nearly-static beacon)
T≥0.99
2.3.1.1
M
After 10 minutes - Configuration 1
S
No
M
After 10 minutes - Configuration 2
F
P
Beacon Message Detection
Probability
((low speed) slow-moving
beacon)
T≥0.99
2.3.1.1
M
After 10 minutes - Configuration 3.1
F
P
2.3.1.1
M
After 10 minutes - Configuration 3.2
F
P
Beacon Message Detection
Probability(\#)
((medium speed) slow-
moving beacon)
T≥0.99
2.3.1.1
M
After 10 minutes - Configuration 4
F
P
Beacon Message Detection
Probability(\*)
T≥0.99
2.3.1.1
M
After 10 minutes - Configuration 5
TBD
TBD
A-4
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results
(P) or
not
(fast-moving beacon)
Beacon Message Detection
Probability (ELT(DT))
T>0.99
2.3.1.2
M
Within any 1 minute period
S
No
5.4.1.1,
5.4.2.1
Probability of FDOA/TDOA
Location
(nearly-static beacon)
PDL≥0.90
2.3.1.3
M
Single burst – Configuration 1
S
No
M
Single burst – Configuration 2
F
P
PDL≥0.98
2.3.1.3
M
After 10 minutes - Configuration 1
S
No
M
After 10 minutes - Configuration 2
F
P
Probability of FDOA/TDOA
Location
((low speed) slow-moving
beacon)
PDL≥0.90
2.3.1.3
M
Single burst – Configuration 3.1
F
P
2.3.1.3
M
Single burst – Configuration 3.2
F
P
PDL≥0.98
2.3.1.3
M
After 10 minutes - Configuration 3.1
F
P
2.3.1.3
M
After 10 minutes - Configuration 3.2
F
P
Probability of FDOA/TDOA
Location(\#)
((medium speed) slow-
moving beacon)
PDL≥0.90
2.3.1.3
M
Single burst - Configuration 4
F
P
PDL≥0.98
2.3.1.3
M
After 10 minutes - Configuration 4
F
P
Probability of FDOA/TDOA
Location(\*)
(fast-moving beacon)
PDL≥0.90
2.3.1.3
M
Single burst – Configuration 5
TBD
TBD
PDL≥0.98
2.3.1.3
M
After 10 minutes - Configuration 5
TBD
TBD
5.5
Capacity
100 beacons
n/a
D
5.6.1
Location Accuracy
(nearly-static beacon)
M/N≥0.90 (5 km)
2.3.1.4
M
Single burst – Configuration 1
S
No
M
Single burst – Configuration 2
F
P
Location Accuracy
(nearly-static beacon)
M/N≥0.95 (5 km)
2.3.1.4
M
Within 10 minutes – Configuration 1
S
No
M
Within 10 minutes – Configuration 2
F
P
M/N≥0.98 (10 km)
2.3.1.4
M
Within 10 minutes – Configuration 1
S
No
M
Within 10 minutes – Configuration 2
F
P
5.6.3
Location Accuracy
((low speed) slow-moving
beacon)
M/N≥0.70
(10 km)
2.3.1.4
M
Single burst – Configuration 3.1
F
P
2.3.1.4
M
Single burst – Configuration 3.2
F
P
M/N≥0.95
(20 km)
2.3.1.4
M
Single burst– Configuration 3.1
F
P
2.3.1.4
M
Single burst– Configuration 3.2
F
P
Location Accuracy
((low speed) slow-moving
beacon)
M/N≥0.75
(5 km)
2.3.1.4
M
Within 10 minutes – Configuration 3.1
F
P
2.3.1.4
M
Within 10 minutes – Configuration 3.2
F
P
M/N≥0.95
(7 km)
2.3.1.4
M
Within 10 minutes – Configuration 3.1
F
P
2.3.1.4
M
Within 10 minutes – Configuration 3.2
F
P
5.6.5
Location Accuracy(\#)
((medium speed) slow-
moving beacon)
M/N≥0.70
(10 km)
2.3.1.4
M
Single burst – Configuration 4
F
P
M/N≥0.95
(20 km)
2.3.1.4
M
Single burst – Configuration 4
F
P
Location Accuracy(\#)
((medium speed) slow-
moving beacon)
M/N≥0.75
(5 km)
2.3.1.4
M
Within 10 minutes – Configuration 4
F
P
M/N≥0.95
(7 km)
2.3.1.4
M
Within 10 minutes – Configuration 4
F
P
5.6.7
Location Accuracy(\*)
(fast-moving beacon)
M/N>0.90
(TBD km)
2.3.1.4
M
Single burst – Configuration 5
TBD
TBD
Location Accuracy(\*)
(fast-moving beacon)
M/N≥0.95
(TBD km)
2.3.1.4
M
Within 10 minutes– Configuration 5
TBD
TBD
M/N≥0.98
(TBD km)
2.3.1.4
M
Within 10 minutes – Configuration 5
TBD
TBD
A-5
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results
(P) or
not
5.7.1
Processing Bandwidth
406.006 to
406.094 MHz
n/a
D
5.7.2
Acquisition Frequency
Range
Beacon with a
deviation from the
center frequency of
± 5.45 kHz
n/a
D
5.8.1.1
TOA/FOA Measurement
Accuracy
TOAσ < 25 µsec
TOAbias < 2.5 µsec
FOAσ< 0.2 Hz
FOAbias < 0.02 Hz
2.3.2.6
M
Only applicable to MEOLUTs which
will provide data to other MEOLUTs
34.8 dBHz < C/N0 < 37.8 dBHz
F
P
5.8.2
External Data Processing
C/S T.019
sections 4.2.10
and 5
D
Only applicable to MEOLUTs which
process data from other MEOLUTs
Transmitting Data
to the MCC
n/a
n/a
V
Using MCC message log table as
defined in Annex E.
2.2.8
M
For C/S T.001 ELT(DT) beacons using
script in section D.3.2.2
F
P
RF Signal Margin
n/a
n/a
D
Signal Sensitivity
Signal sensitivity
better than
34.8 dB-Hz
D
Beacon Message Detection
Probability
(nearly-static beacon)
T≥0.99
2.3.2.1
M
After 10 minutes - Configuration 1
S
No
2.3.2.1
M
After 10 minutes - Configuration 2
F
P
Beacon Message Detection
Probability
((low speed) slow-moving
beacon)
T≥0.99
2.3.2.1
M
After 10 minutes - Configuration 3.1
F
P
2.3.2.1
M
After 10 minutes- Configuration 3.2
F
P
Beacon Message Detection
Probability(\#)
((medium speed)slow-
moving beacon)
T≥0.99
2.3.2.1
M
After 10 minutes - Configuration 4
F
P
Beacon Message Detection
Probability(\*)
(fast-moving beacon)
T≥0.99
2.3.2.1
M
After 10 minutes - Configuration 5
TBD
TBD
Beacon Message Detection
Probability (ELT(DT))
T>0.99
2.3.2.2
M
Within any 1 minute period
S
No
Probability of FDOA/TDOA
Location
(nearly-static beacon)
PDL≥0.90
2.3.2.3
M
Single burst – Configuration 1
S
No
M
Single burst – Configuration 2
F
P
PDL≥0.98
2.3.2.3
M
After 10 minutes - Configuration 1
S
No
M
After 10 minutes - Configuration 2
F
P
Probability of FDOA/TDOA
Location
((low speed) slow-moving
beacon)
PDL≥0.90
2.3.2.3
M
Single burst – Configuration 3.1
F
P
2.3.2.3
M
Single burst – Configuration 3.2
F
P
PDL≥0.98
2.3.2.3
M
After 10 minutes - Configuration 3.1
F
P
2.3.2.3
M
After 10 minutes - Configuration 3.2
F
P
Probability of FDOA/TDOA
Location(\#)
((medium speed) slow-
moving beacon)
PDL≥0.90
2.3.2.3
M
Single burst – Configuration 4
F
P
PDL≥0.98
2.3.2.3
M
After 10 minutes - Configuration 4
F
P
Probability of FDOA/TDOA
Location(\*)
(fast-moving beacon)
PDL≥0.90
2.3.2.3
M
Single burst – Configuration 5
TBD
TBD
PDL≥0.98
2.3.2.3
M
After 10 minutes - Configuration 5
TBD
TBD
Capacity
100 beacons
n/a
D
A-6
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results
(P) or
not
Location Accuracy
(nearly-static beacon)
M/N≥0.90 (5 km)
2.3.2.4
M
Single Burst – Configuration 1
S
No
M
Single burst – Configuration 2
F
P
Location Accuracy
(nearly-static beacon)
M/N≥0.95 (5 km)
2.3.2.4
M
Within 10 minutes – Configuration 1
S
No
M
Within 10 minutes – Configuration 2
F
P
M/N≥0.98 (10 km)
2.3.2.4
M
Within 10 minutes – Configuration 1
S
No
M
Within 10 minutes – Configuration 2
F
P
Location Accuracy
((low speed) slow-moving
beacon)
M/N≥0.70
(10 km)
2.3.2.4
M
Single burst – Configuration 3.1
F
P
2.3.2.4
M
Single burst – Configuration 3.2
F
P
M/N≥0.95
(20 km)
2.3.2.4
M
Single burst – Configuration 3.1
F
P
2.3.2.4
M
Single burst – Configuration 3.2
F
P
Location Accuracy
((low speed) slow-moving
beacon)
M/N≥0.75
(5 km)
2.3.2.4
M
Within 10 minutes – Configuration 3.1
F
P
2.3.2.4
M
Within 10 minutes – Configuration 3.2
F
P
M/N≥0.95
(7 km)
2.3.2.4
M
Within 10 minutes – Configuration 3.1
F
P
2.3.2.4
M
Within 10 minutes – Configuration 3.2
F
P
Location Accuracy(\#)
((medium speed) slow-
moving beacon)
M/N≥0.70
(10 km)
2.3.2.4
M
Single burst – Configuration 4
F
P
M/N≥0.95
(20 km)
2.3.2.4
M
Single burst – Configuration 4
F
P
Location Accuracy(\#)
((medium speed) slow-
moving beacon)
M/N≥0.75
(5 km)
2.3.2.4
M
Within 10 minutes – Configuration 4
F
P
M/N≥0.95
(7 km)
2.3.2.4
M
Within 10 minutes – Configuration 4
F
P
Location Accuracy(\*)
(fast-moving beacon)
M/N>0.90
(TBD km)
2.3.2.4
M
Single burst – Configuration 5
TBD
TBD
Location Accuracy(\*)
(fast-moving beacon)
M/N≥0.95
(TBD km)
2.3.2.4
M
Within 10 minutes – Configuration 5
TBD
TBD
M/N≥0.98
(TBD km)
2.3.2.4
M
Within 10 minutes – Configuration 5
TBD
TBD
Processing Bandwidth
406.006 to
406.094 MHz
n/a
D
Acquisition Frequency
Range
Beacon with a
deviation from the
center frequency of
± 5.45 kHz
n/a
D
Expected Horizontal Error /
Quality Factor
Prediction Accuracy
NC1/10 /NL < 0.15
0.93 ≤ NC1/NL ≤ 0.97
NC2/NL < 0.01
2.3.2.5
M
EHE results must be
provided for factory and
on-site tests, as
appropriate
Processing Anomalies
< 1x10-4
2.3.2.7
M
Processing anomalies that consist of a
single burst from a single satellite shall
be identified separately
S
No
5.9
Combined Processing
C/S T.019
sections 4.2.10
and 5
D
Only applicable to MEOLUTs which
use non-MEOSAR C/S satellites
Transmitting Data
to the MCC
n/a
n/a
V
Using MCC message log table as
defined in Annex E
2.2.8
M
For C/S T.001 ELT(DT) beacons using
script in section D.3.2.2
F
P
RF Signal Margin
n/a
n/a
D
A-7
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results
(P) or
not
Signal Sensitivity
Signal sensitivity
better than
34.8 dB-Hz
D
Beacon Message Detection
Probability
(nearly-static beacon)
T≥0.99
2.3.3.1
M
After 10 minutes - Configuration 1
S
No
M
After 10 minutes - Configuration 2
F
P
Beacon Message Detection
Probability
((low speed) slow-moving
beacon)
T≥0.99
2.3.1.1
M
After 10 minutes- Configuration 3.1
F
P
2.3.1.1
M
After 10 minutes - Configuration 3.2
F
P
Beacon Message Detection
Probability(\#)
((medium speed) slow-
moving beacon)
T≥0.99
2.3.1.1
M
After 10 minutes - Configuration 4
F
P
Beacon Message Detection
Probability(\*)
(fast-moving beacon)
T≥0.99
2.3.1.1
M
After 10 minute - Configuration 5
TBD
TBD
Beacon Message Detection
Probability (ELT(DT))
T>0.99
2.3.3.2
M
Within any 1 minute period
S
No
Probability of FDOA/TDOA
Location
PDL≥0.90
2.3.3.3
M
Single burst – Configuration 1
S
No
M
Single burst – Configuration 2
F
P
PDL≥0.98
2.3.3.3
M
After 10 minutes – Configuration 1
S
No
M
After 10 minutes - Configuration 2
F
P
Probability of FDOA/TDOA
Location
((low speed) slow-moving
beacon)
PDL≥0.90
2.3.1.3
M
Single burst – Configuration 3.1
F
P
2.3.1.3
M
Single burst – Configuration 3.2
F
P
PDL≥0.98
2.3.1.3
M
After 10 minutes - Configuration 3.1
F
P
2.3.1.3
M
After 10 minutes - Configuration 3.2
F
P
Probability of FDOA/TDOA
Location(\#)
((medium speed) slow-
moving beacon)
PDL≥0.90
2.3.1.3
M
Single burst – Configuration 4
F
P
PDL≥0.98
2.3.1.3
M
After 10 minutes - Configuration 4
F
P
Probability of FDOA/TDOA
Location(\*)
(fast-moving beacon)
PDL≥0.90
2.3.1.3
M
Single burst – Configuration 5
TBD
TBD
PDL≥0.98
2.3.1.3
M
After 10 minutes -Configuration 5
TBD
TBD
Capacity
100 beacons
n/a
D
Location Accuracy
(nearly-static beacon)
M/N≥0.90 (5 km)
2.3.3.4
M
Single burst – Configuration 1
S
No
M
Single burst – Configuration 2
F
P
Location Accuracy
(nearly-static beacon)
M/N≥0.95 (5 km)
2.3.3.4
M
Within 10 minutes – Configuration 1
S
No
M
Within 10 minutes – Configuration 2
F
P
M/N≥0.98 (10 km)
2.3.3.4
M
Within 10 minutes – Configuration 1
S
No
M
Within 10 minutes – Configuration 2
F
P
Location Accuracy
((low speed) slow-moving
beacon)
M/N≥0.70
(10 km)
2.3.3.4
M
Single burst – Configuration 3.1
F
P
2.3.3.4
M
Single burst – Configuration 3.2
F
P
M/N≥0.95
(20 km)
2.3.3.4
M
Single burst – Configuration 3.1
F
P
2.3.3.4
M
Single burst – Configuration 3.2
F
P
Location Accuracy
((low speed) slow-moving
beacon)
M/N≥0.75
(5 km)
2.3.3.4
M
Within 10 minutes – Configuration 3.1
F
P
2.3.3.4
M
Within 10 minutes – Configuration 3.2
F
P
2.3.3.4
M
Within 10 minutes – Configuration 3.1
F
P
A-8
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results
(P) or
not
M/N≥0.95
(7 km)
2.3.3.4
M
Within 10 minutes – Configuration 3.2
F
P
Location Accuracy(\#)
((medium speed) slow-
moving beacon)
M/N≥0.70
(10 km)
2.3.1.4
M
Single burst – Configuration 4
F
P
M/N≥0.95
(20 km)
2.3.1.4
M
Single burst – Configuration 4
F
P
Location Accuracy(\#)
((medium speed) slow-
moving beacon)
M/N≥0.75
(5 km)
2.3.3.4
M
Within 10 minutes – Configuration 4
F
P
M/N≥0.95
(7 km)
2.3.3.4
M
Within 10 minutes – Configuration 4
F
P
Location Accuracy(\*)
(fast-moving beacon)
M/N>0.90
(TBD km)
2.3.3.4
M
Single burst – Configuration 5
TBD
TBD
Location Accuracy(\*)
(fast-moving beacon)
M/N≥0.95
(TBD km)
2.3.3.4
M
Within 10 minutes – Configuration 5
TBD
TBD
M/N≥0.98
(TBD km)
2.3.3.4
M
Within 10 minutes – Configuration 5
TBD
TBD
Processing Bandwidth
406.006 to
406.094 MHz
n/a
D
Acquisition Frequency
Range
Beacon with a
deviation from the
center frequency of
± 5.45 kHz
n/a
D
Expected Horizontal Error /
Quality Factor
Prediction Accuracy
NC1/10 /NL < 0.15
0.93 ≤ NC1/NL ≤ 0.97
NC2/NL < 0.01
2.3.3.5
M
EHE results must be
provided for factory and
on-site tests, as
appropriate
Processing Anomalies
< 1x10-4
2.3.3.6
M
Processing anomalies that consist of a
single burst from a single satellite shall
be identified separately.
S
No
5.10
Expected Horizontal Error /
Quality Factor
Prediction Accuracy
NC1/10 /NL < 0.15
0.93 ≤ NC1/NL ≤ 0.97
NC2/NL < 0.01
2.3.1.5
M
EHE results must be
provided for factory and
on-site tests, as
appropriate
5.11
Processing Anomalies
< 1x10-4
2.3.1.6
M
Processing anomalies that consist of a
single burst from a single satellite shall
be identified separately.
S
No
Notes:
(\#) Testing of Configuration 4 is not required for MEOLUT commissioning until the location accuracy performance
and the test velocity (in brackets in Annex C) is confirmed for Configuration 4, but could be provided if available.
(\*) Testing of Configuration 5 is not required for MEOLUT commissioning until the location accuracy performance
requirement (noted TBD) is finalized.
A-9
Table A.3: MEOLUT Commissioning Summary Data Table (C/S T.018 Beacon Part)
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results (P)
or not
4.2.2
Beacon Message Recovery
- MR1
See Annex D.1
3.2.1
M
F
P
Beacon Message Recovery
- MR2
See Annex D.1
3.2.1
M
F
P
4.2.3.2
Bit Verification - BV1
See Annex D.1
3.2.2
M
F
P
4.2.5.2
Invalid Message
Processing – IMP1
See Annex D.1
3.2.3
M
F
P
4.2.6.2
Message Association -
MA1
See Annex D.1
3.2.4
M
F
P
4.2.6.1 and
4.2.11
Return Link Test – RL1
See Annex D.1
3.2.5
M
F
P
4.2.11
Transmitting Data
to the MCC
n/a
n/a
V
Using MCC message log table as
defined in Annex E.
3.2.6
M
For C/S T.018 ELT(DT) beacons using
script in section D.3.4.2.
F
P
5.1
RF Signal Margin
n/a
n/a
D
5.2.2
Signal Sensitivity
Signal sensitivity
better than
30.55 dB-Hz
D
5.3.2
Beacon Message Detection
Probability
Partially Overlapping
Bursts
T>0.95
3.3.1.1
M
Also provide the single-burst location
probability for information only –
Configuration 1
F
P
Beacon Message Detection
Probability
(nearly-static beacon)
T≥0.999
3.3.1.2
M
After 30 seconds - Configuration 1
S
No
M
After 30 seconds - Configuration 2
F
P
Beacon Message Detection
Probability
((low speed) slow-moving
beacon)
T≥0.999
3.3.1.2
M
After 30 seconds - Configuration 3.1(##)
F
P
M
After 30 seconds - Configuration 3.2
F
P
Beacon Message Detection
Probability(\#)
((medium speed) slow-
moving beacon)
T≥0.999
3.3.1.2
M
After 30 seconds - Configuration 4
F
P
Beacon Message Detection
Probability(\*)
(fast-moving beacon)
T≥0.999
3.3.1.2
M
After 30 seconds - Configuration 5
TBD
TBD
Beacon Message Detection
Probability (ELT(DT))
T>0.99
3.3.1.3
M
Within any 1 minute period
S
No
5.4.1.2,
5.4.2.2
Probability of
FDOA/TDOA Location
(nearly-static beacon)
PDL≥0.95
3.3.1.4
M
Single burst - Configuration 1
S
No
M
Single burst - Configuration 2
F
P
PDL≥0.98
3.3.1.4
M
Within 30 seconds - Configuration 1
S
No
M
Within 30 seconds - Configuration 2
F
P
PDL≥0.98
3.3.1.4
M
Within 5 minutes - Configuration 1
S
No
M
Within 5 minutes - - Configuration 2
F
P
PDL≥0.98
3.3.1.4
M
Within 30 minutes - Configuration 1
S
No
M
Within 30 minutes - Configuration 2
F
P
5.4.1.2,
5.4.2.2
Probability of
FDOA/TDOA Location
PDL≥0.95
3.3.1.4
M
Single burst - Configuration 3.1(##)
F
P
M
Single burst - Configuration 3.2
F
P
A-10
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results (P)
or not
((low speed) slow-moving
beacon)
PDL≥0.98
3.3.1.4
M
Within 30 seconds - Configuration
3.1(\#\#)
F
P
M
Within 30 seconds - Configuration 3.2
F
P
PDL≥0.98
3.3.1.4
M
Within 5 minutes - Configuration 3.1(##)
F
P
M
Within 5 minutes - Configuration 3.2
F
P
5.4.1.2,
5.4.2.2
Probability of
FDOA/TDOA Location(\#)
((medium speed) slow-
moving beacon)
PDL≥0.95
3.3.1.4
M
Single burst - Configuration 4
F
P
PDL≥0.98
3.3.1.4
M
Within 30 seconds - Configuration 4
F
P
PDL≥0.98
3.3.1.4
M
Within 5 minutes - Configuration 4
F
P
5.4.1.2,
5.4.2.2
Probability of
FDOA/TDOA Location(\*)
(fast-moving beacon)
PDL≥0.95
3.3.1.4
M
Single burst - Configuration 5
TBD
TBD
PDL≥0.98
3.3.1.4
M
Within 30 seconds - Configuration 5
TBD
TBD
PDL≥0.98
3.3.1.4
M
Within 5 minutes - Configuration 5
TBD
TBD
5.5
Capacity
100 beacons
n/a
D
5.6.2
Location Accuracy
(nearly-static beacon)
M/N≥0.95 (5 km)
3.3.1.5
M
Single Burst - Configuration 1
S
No
M
Single Burst - Configuration 2
F
P
M/N≥0.97 (5 km)
3.3.1.5
M
Within 30 seconds - Configuration 1
S
No
M
Within 30 seconds - Configuration 2
F
P
M/N≥0.97 (1 km)
3.3.1.5
M
Within 5 minutes - Configuration 1
S
No
M
Within 5 minutes - Configuration 2
F
P
M/N≥0.97 (0.1
km)
3.3.1.5
M
After 30 minutes - Configuration 1(†)
S
No
M
After 30 minutes - Configuration 2(†)
F
P
5.6.4
Location Accuracy
((low speed) slow-moving
beacon)
M/N≥0.95 (5 km)
3.3.1.5
M
Single Burst - Configuration 3.1(##)
F
P
3.3.1.5
M
Single Burst - Configuration 3.2
F
P
M/N≥0.97 (5 km)
3.3.1.5
M
Within 30 seconds - Configuration
3.1(\#\#)
F
P
3.3.1.5
M
Within 30 seconds - Configuration 3.2
F
P
M/N≥0.97 (1 km)
3.3.1.5
M
Within 5 minutes - Configuration 3.1(##)
F
P
3.3.1.5
M
Within 5 minutes - Configuration 3.2
F
P
5.6.6
Location Accuracy(\#)
((medium speed) slow-
moving beacon)
M/N≥0.95 (5 km)
3.3.1.5
M
Single Burst - Configuration 4
F
P
M/N≥0.97 (5 km)
3.3.1.5
M
Within 30 seconds - Configuration 4
F
P
M/N≥0.97 (1 km)
3.3.1.5
M
Within 5 minutes - Configuration 4
F
P
5.6.8
Location Accuracy(\*)
(fast-moving beacon)
M/N≥0.95
(TBD km)
3.3.1.5
M
Single Burst - Configuration 5
TBD
TBD
M/N≥0.97
(TBD km)
3.3.1.5
M
Within 30 seconds - Configuration 5
TBD
TBD
M/N≥0.97
(TBD km)
3.3.1.5
M
Within 5 minutes - Configuration 5
TBD
TBD
5.7.1
Processing Bandwidth
406.006 to
406.094 MHz
n/a
D
5.7.2
Acquisition Frequency
Range
Beacon center
frequency in the
range 406.05 MHz
± 1.65 kHz
n/a
D
5.8.1.2
TOA/FOA Measurement
Accuracy
TOAσ < [1] µsec
TOAbias < [0.2] µsec
FOAσ < [0.2] Hz
FOAbias < [0.02] Hz
3.3.2.7
M
Only applicable to MEOLUTs which
will provide data to other MEOLUTs
[30.55] dBHz < C/N0 < [33.55] dBHz
F
P
5.8.2
External Data Processing
C/S T.019
sections 4.2.10
and 5
D
Only applicable to MEOLUTs which
process data from other MEOLUTs
A-11
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results (P)
or not
Transmitting Data
to the MCC
n/a
n/a
V
Using MCC message log table as
defined in Annex E
3.2.6
M
For C/S T.018 ELT(DT) beacons using
script in section D.3.4.2.
F
P
RF Signal Margin
n/a
n/a
D
Signal Sensitivity
Signal sensitivity
better than
30.55 dB-Hz
D
Beacon Message Detection
Probability
Partially Overlapping
Bursts
T>0.95
3.3.1.1
M
Also provide the single-burst location
probability for information only
F
P
Beacon Message Detection
Probability
T≥0.999
3.3.2.2
M
After 30 seconds - Configuration 1
S
No
M
After 30 seconds - Configuration 2
F
P
Beacon Message Detection
Probability
((low speed) slow-moving
beacon)
T≥0.999
3.3.1.2
M
After 30 seconds - Configuration 3.1(##)
F
P
M
After 30 seconds - Configuration 3.2
F
P
Beacon Message Detection
Probability(\#)
((medium speed) slow-
moving beacon)
T≥0.999
3.3.1.2
M
After 30 seconds - Configuration 4
F
P
Beacon Message Detection
Probability(\*)
(fast-moving beacon)
T≥0.999
3.3.1.2
M
After 30 seconds - Configuration 5
TBD
TBD
Beacon Message Detection
Probability (ELT(DT))
T>0.99
3.3.2.3
M
Within any 1 minute period
S
No
Probability of
FDOA/TDOA Location
(nearly-static beacon)
PDL≥0.95
3.3.2.4
M
Single burst - Configuration 1
S
No
M
Single burst - Configuration 2
F
P
PDL≥0.98
3.3.2.4
M
Within 30 seconds - Configuration 1
S
No
M
Within 30 seconds - Configuration 2
F
P
PDL≥0.98
3.3.2.4
M
Within 5 minutes - Configuration 1
S
No
M
Within 5 minutes - Configuration 2
F
P
PDL≥0.98
3.3.2.4
M
Within 30 minutes - Configuration 1
S
No
M
Within 30 minutes - Configuration 2
F
P
Probability of
FDOA/TDOA Location
((low speed) slow-moving
beacon)
PDL≥0.95
3.3.1.4
M
Single burst - Configuration 3.1(##)
F
P
M
Single burst - Configuration 3.2
F
P
PDL≥0.98
3.3.1.4
M
Within 30 seconds - Configuration
3.1(\#\#)
F
P
M
Within 30 seconds - Configuration 3.2
F
P
PDL≥0.98
3.3.1.4
M
Within 5 minutes - Configuration 3.1(##)
F
P
M
Within 5 minutes - Configuration 3.2
F
P
Probability of
FDOA/TDOA Location(\#)
((medium speed) slow-
moving beacon)
PDL≥0.95
3.3.1.4
M
Single burst - Configuration 4
F
P
PDL≥0.98
3.3.1.4
M
Within 30 seconds - Configuration 4
F
P
PDL≥0.98
3.3.1.4
M
Within 5 minutes - Configuration 4
F
P
Probability of
FDOA/TDOA Location(\*)
(fast-moving beacon)
PDL≥0.95
3.3.1.4
M
Single burst - Configuration 5
TBD
TBD
PDL≥0.98
3.3.1.4
M
Within 30 seconds - Configuration 5
TBD
TBD
PDL≥0.98
3.3.1.4
M
Within 5 minutes - Configuration 5
TBD
TBD
Capacity
100 beacons
n/a
D
3.3.2.5
M
Single Burst - Configuration 1
S
No
A-12
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results (P)
or not
Location Accuracy
(nearly-static beacon)
M/N≥0.95 (5 km)
M
Single Burst - Configuration 2
F
P
M/N≥0.97 (5 km)
3.3.2.5
M
Within 30 seconds - Configuration 1
S
No
M
Within 30 seconds - Configuration 2
F
P
M/N≥0.97 (1 km)
3.3.2.5
M
Within 5 minutes - Configuration 1
S
No
M
Within 5 minutes - Configuration 2
F
P
M/N≥0.97 (0.1
km)
3.3.2.5
M
After 30 minutes - Configuration 1(†)
S
No
M
After 30 minutes - Configuration 2(†)
F
P
Location Accuracy
((low speed) slow-moving
beacon)
M/N≥0.95 (5 km)
3.3.2.5
M
Single Burst - Configuration 3.1(##)
F
P
3.3.2.5
M
Single Burst - Configuration 3.2
F
P
M/N≥0.97 (5 km)
3.3.2.5
M
Within 30 seconds - Configuration
3.1(\#\#)
F
P
3.3.2.5
M
Within 30 seconds - Configuration 3.2
F
P
M/N≥0.97 (1 km)
3.3.2.5
M
Within 5 minutes - Configuration 3.1(##)
F
P
3.3.2.5
M
Within 5 minutes - Configuration 3.2
F
P
Location Accuracy(\#)
((medium speed) slow-
moving beacon)
M/N≥0.95 (5 km)
3.3.2.5
M
Single Burst - Configuration 4
F
P
M/N≥0.97 (5 km)
3.3.2.5
M
Within 30 seconds - Configuration 4
F
P
M/N≥0.97 (1 km)
3.3.2.5
M
Within 5 minutes - Configuration 4
F
P
Location Accuracy(\*)
(fast-moving beacon)
M/N≥0.95
(TBD km)
3.3.2.5
M
Single Burst - Configuration 5
TBD
TBD
M/N≥0.97
(TBD km)
3.3.2.5
M
Within 30 seconds - Configuration 5
TBD
TBD
M/N≥0.97
(TBD km)
3.3.2.5
M
Within 5 minutes - Configuration 5
TBD
TBD
Processing Bandwidth
406.006 to
406.094 MHz
n/a
D
Acquisition Frequency
Range
Beacon center
frequency in the
range 406.05 MHz
± 1.65 kHz
n/a
D
Expected Horizontal Error
/ Quality Factor(‡)
Prediction Accuracy
NC1/10 /NL < 0.15
0.93≤ NC1/NL≤0.97
NC2/NL < 0.01
3.3.2.6
M
EHE results must be
provided for factory and
on-site tests, as appropriate
Processing Anomalies(⸸)
< 1x10-4
3.3.2.8
M
Processing anomalies that consist of a
single burst from a single satellite shall
be identified separately.
S
No
5.9
Combined Processing
C/S T.019
sections 4.2.10
and 5
D
Only applicable to MEOLUTs which
use non-MEOSAR C/S satellites.
Transmitting Data
to the MCC
n/a
n/a
V
Using MCC message log table as
defined in Annex E
3.2.6
M
For C/S T.018 ELT(DT) beacons using
script in section D.3.4.2.
F
P
RF Signal Margin
n/a
n/a
D
Signal Sensitivity
Signal sensitivity
better than
30.55 dB-Hz
D
Beacon Message Detection
Probability
Partially Overlapping
Bursts
T>0.95
3.3.1.1
M
Also provide the single-burst location
probability for information only
F
P
A-13
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results (P)
or not
Beacon Message Detection
Probability
(nearly-static beacon)
T≥0.999
3.3.3.2
M
After 30 seconds - Configuration 1
S
No
M
After 30 seconds - Configuration 2
F
P
Beacon Message Detection
Probability
((low speed) slow-moving
beacon)
T≥0.999
3.3.1.3
M
After 30 seconds - Configuration 3.1(##)
F
P
M
After 30 seconds - Configuration 3.2
F
P
Beacon Message Detection
Probability(\#)
((medium speed) slow-
moving beacon)
T≥0.999
3.3.1.2
M
After 30 seconds - Configuration 4
F
P
Beacon Message Detection
Probability(\*)
(fast-moving beacon)
T≥0.999
3.3.1.2
M
After 30 seconds - Configuration 5
TBD
TBD
Beacon Message Detection
Probability (ELT(DT))
T>0.99
3.3.3.3
M
Within any 1 minute period
S
No
Probability of
FDOA/TDOA Location
(nearly-static beacon)
PDL≥0.95
3.3.3.4
M
Single burst - Configuration 1
S
No
M
Single burst - Configuration 2
F
P
PDL≥0.98
3.3.3.4
M
Within 30 seconds - Configuration 1
S
No
M
Within 30 seconds - Configuration 2
F
P
PDL≥0.98
3.3.3.4
M
Within 5 minutes - Configuration 1
S
No
M
Within 5 minutes - Configuration 2
F
P
PDL≥0.98
3.3.3.4
M
Within 30 minutes - Configuration 1
S
No
M
Within 30 minutes - Configuration 2
F
P
Probability of
FDOA/TDOA Location
((low speed) slow-moving
beacon)
PDL≥0.95
3.3.1.4
M
Single burst - Configuration 3.1(##)
F
P
M
Single burst - Configuration 3.2
F
P
PDL≥0.98
3.3.1.4
M
Within 30 seconds - Configuration
3.1(\#\#)
F
P
M
Within 30 seconds - Configuration 3.2
F
P
PDL≥0.98
3.3.1.4
M
Within 5 minutes - Configuration 3.1(##)
F
P
M
Within 5 minutes - Configuration 3.2
F
P
Probability of
FDOA/TDOA Location(\#)
((medium speed) slow-
moving beacon)
PDL≥0.95
3.3.1.4
M
Single burst - Configuration 4
F
P
PDL≥0.98
3.3.1.4
M
Within 30 seconds - Configuration 4
F
P
PDL≥0.98
3.3.1.4
M
Within 5 minutes - Configuration 4
F
P
Probability of
FDOA/TDOA Location(\*)
(fast-moving beacon)
PDL≥0.95
3.3.1.4
M
Single burst - Configuration 5
TBD
TBD
PDL≥0.98
3.3.1.4
M
Within 30 seconds - Configuration 5
TBD
TBD
PDL≥0.98
3.3.1.4
M
Within 5 minutes - Configuration 5
TBD
TBD
Capacity
100 beacons
n/a
D
Location Accuracy
(nearly-static beacon)
M/N≥0.95 (5 km)
3.3.3.5
M
Single Burst - Configuration 1
S
No
M
Single Burst - Configuration 2
F
P
M/N≥0.97 (5 km)
3.3.3.5
M
Within 30 seconds - Configuration 1
S
No
M
Within 30 seconds - Configuration 2
F
P
M/N≥0.97 (1 km)
3.3.3.5
M
Within 5 minutes - Configuration 1
S
No
M
Within 5 minutes - Configuration 2
F
P
M/N≥0.97 (0.1
km)
3.3.3.5
M
After 30 minutes - Configuration 1(†)
S
No
M
After 30 minutes - Configuration 2(†)
F
P
Location Accuracy
((low speed) slow-moving
beacon)
M/N≥0.95 (5 km)
3.3.3.5
M
Single Burst - Configuration 3.1(##)
F
P
3.3.3.5
M
Within 30 seconds - Configuration 3.2
F
P
M/N≥0.97 (5 km)
3.3.3.5
M
Within 30 seconds - Configuration
3.1(\#\#)
F
P
A-14
Section in
C/S T.019
Requirement or Test
Pass Criteria
Result or
Report Ref
Pass/
Fail
Method of
Compliance
Declaration / Verification or
Comments
Facility (F)
or
Installation
Site (S)
Prior
Results (P)
or not
3.3.3.5
M
Within 30 seconds - Configuration 3.2
F
P
M/N≥0.97 (1 km)
3.3.3.5
M
Within 5 minutes - Configuration 3.1(##)
F
P
3.3.3.5
M
Within 5 minutes - Configuration 3.2
F
P
Location Accuracy(\#)
((medium speed) slow-
moving beacon)
M/N≥0.95 (5 km)
3.3.3.5
M
Single Burst - Configuration 4
F
P
M/N≥0.97 (5 km)
3.3.3.5
M
Within 30 seconds - Configuration 4
F
P
M/N≥0.97 (1 km)
3.3.3.5
M
Within 5 minutes - Configuration 4
F
P
Location Accuracy(\*)
(fast-moving beacon)
M/N≥0.95
(TBD km)
3.3.3.5
M
Single Burst - Configuration 5
TBD
TBD
M/N≥0.97
(TBD km)
3.3.3.5
M
Within 30 seconds - Configuration 5
TBD
TBD
M/N≥0.97
(TBD km)
3.3.3.5
M
Within 5 minutes - Configuration 5
TBD
TBD
Processing Bandwidth
406.006 to
406.094 MHz
n/a
D
Acquisition Frequency
Range
Center frequency
in the range
406.05 MHz
± 1.65 kHz
n/a
D
Expected Horizontal Error
/ Quality Factor(‡)
Prediction Accuracy
NC1/10 /NL < 0.15
0.93≤NC1/NL≤0.97
NC2/NL < 0.01
3.3.3.6
M
EHE results must be
provided for factory and
on-site tests, as appropriate
Processing Anomalies(⸸)
< 1x10-4
3.3.3.7
M
Processing anomalies that consist of a
single burst from a single satellite shall
be identified separately.
S
No
5.10
Expected Horizontal Error
/ Quality Factor(‡)
Prediction Accuracy
NC1/10 /NL < 0.15
0.93≤NC1/NL≤0.97
NC2/NL < 0.01
3.3.1.6
M
EHE results must be
provided for factory and
on-site tests, as appropriate
5.11
Processing Anomalies(⸸)
< 1x10-4
3.3.1.7
M
Processing anomalies that consist of a
single burst from a single satellite shall
be identified separately.
S
No
Notes:
(\#) Testing of Configuration 4 is not required for MEOLUT commissioning until the test velocity (in brackets) is
finalized for Configuration 4, but could be provided if available.
(\*) Testing of Configuration 5 is not required for MEOLUT commissioning until the location accuracy performance
requirement (noted TBD) is finalized.
(†) Testing of Configurations 1 and 2 shall be performed and results reported in the MEOLUT commissioning report.
For MEOLUTs that commence commissioning (see document C/S P.011 at footnote 1, page 5-8) prior to 15 October
2026 (scheduled end of CSC-75) this will not be a pass/fail criteria. JC-40 is expected to review and make
recommendations to the Council concerning this specification, a possible extension of this waiver of the “pass”
requirement and/or whether and when the MEOLUT may be required to undergo a partial recommissioning to
demonstrate “pass” compliance. The Council at its scheduled October 2026 session is anticipated to consider the
recommendations of JC-40 and make decisions on these matters accordingly.
(‡) The EHE test shall be performed and results reported in the MEOLUT commissioning report. For MEOLUTs
that commence commissioning (see document C/S P.011 at footnote 1, page 5-8) prior to 15 October 2026 (scheduled
end of CSC-75) this will not be a pass/fail criteria. JC-40 is expected to review and make recommendations to the
Council concerning this specification, a possible extension of this waiver of the “pass” requirement and/or whether
and when the MEOLUT may be required to undergo a partial recommissioning to demonstrate “pass” compliance.
The Council at its scheduled October 2026 session is anticipated to consider the recommendations of JC-40 and make
decisions on these matters accordingly.
A-15
(⸸) The processing anomaly test shall be performed and results reported in the MEOLUT commissioning report. For
MEOLUTs that commence commissioning (see document C/S P.011 at footnote 1, page 5-8) prior to 15 October 2026
(scheduled end of CSC-75) this will not be a pass/fail criteria. JC-40 is expected to review and make recommendations
to the Council concerning this specification, a possible extension of this waiver of the “pass” requirement and/or
whether and when the MEOLUT may be required to undergo a partial recommissioning to demonstrate “pass”
compliance. The Council at its scheduled October 2026 session is anticipated to consider the recommendations of
JC-40 and make decisions on these matters accordingly.
(\#\#) Testing of configuration 3.1 is not required for commissioning of the MEOLUT SGB capability.
A-16
A.2
Results of Measurements
This section contains the detailed results of measurements summarized in section A.1. Each of the
requirements is referred to in the report by the report reference number. The test procedure column
identifies the reference in this document, where the detailed test procedure and pass/fail criteria are
provided.
General part
Report Ref \#
Title
Test
Procedure
2.1
Operational Requirements
2.1.1
MEOLUT Data Availability (A)
B.1
C/S T.001 Beacons
Report Ref \#
Title
Test
Procedure
2.2
Functional and Processing Requirements
2.2.1
Bit Rate Tolerance Check
D.1.2
2.2.2
Bit Verification (test code sequence BV1 - BV2 - BV3)
D.2.1
2.2.3
Beacon Message Validation
(test code sequence MV1 - MV2 - MV5 - MV6)
D.2.1
2.2.4
Invalid Message Processing (test code sequence IMP1)
D.2.1
2.2.5
Beacon Message Processing
(test code sequence LP1 - LP2 - LP3 - LP4)
D.2.1
2.2.6
Return Link Test (test code sequence RL1)
D.2.1
2.2.7
Multiple valid message processing
2.2.8
C/S T.001 ELT(DT) functional validation script
D.3.2.2
2.3
Performance Requirements
2.3.1
Stand Alone Statistics
2.3.1.1
Beacon Detection Probability (T) Non ELT(DT) Beacons
C.2.1
2.3.1.2
Beacon Detection Probability (T) ELT(DT) Beacons
C.2.2
2.3.1.3
Probability of DOA Location (PDL)
C.2.3
2.3.1.4
Location Accuracy
C.2.4
2.3.1.5
Expected Horizontal Error / Quality Factor
C.2.6
2.3.1.6
Processing Anomalies
C.2.7
2.3.2
MEOLUT Data Exchange
2.3.2.1
Beacon Detection Probability (T) Non ELT(DT) Beacons
C.2.1
2.3.2.2
Beacon Detection Probability (T) ELT(DT) Beacons
C.2.2
2.3.2.3
Probability of DOA Location (PDL)
C.2.3
2.3.2.4
Location Accuracy
C.2.4
2.3.2.5
Expected Horizontal Error / Quality Factor
C.2.5
2.3.2.6
TOA/FOA Measurement Accuracy
C.2.6
2.3.2.7
Processing Anomalies
C.2.7
2.3.3
Combined Non-MEOSAR Satellite Statistics
2.3.3.1
Beacon Detection Probability (T) Non ELT(DT) Beacons
C.2.1
2.3.3.2
Beacon Detection Probability (T) ELT(DT) Beacons
C.2.2
2.3.3.3
Probability of DOA Location (PDL)
C.2.3
2.3.3.4
Location Accuracy
C.2.4
2.3.3.5
Expected Horizontal Error / Quality Factor
C.2.6
2.3.3.6
Processing Anomalies
C.2.7
A-17
C/S T.018 Beacons
Report Ref \#
Title
Test
Procedure
3.1
Operational Requirements (same as 2.1)
3.2
Functional and Processing Requirements
3.2.1
Message Recovery (test code sequence MR1 - MR2)
D.2.2
3.2.2
Bit Verification (test code sequence BV1)
D.2.2
3.2.3
Invalid Message Processing (test code sequence IMP1)
D.2.2
3.2.4
Message Association (test code sequence MA1)
D.2.2
3.2.5
Return Link Test (test code sequence RL1)
D.2.2
3.2.6
C/S T.018 ELT(DT) functional validation script
D.3.4.2
3.3
Performance Requirements
3.3.1
Stand Alone Statistics
3.3.1.1
Beacon Detection Probability (T(OB)) Partially Overlapping Bursts
C.3.1
3.3.1.2
Beacon Detection Probability (T) Non ELT(DT) Beacons
C.3.2
3.3.1.3
Beacon Detection Probability (T) ELT(DT) Beacons
C.3.3
3.3.1.4
Probability of DOA Location (PDL)
C.3.4
3.3.1.5
Location Accuracy
C.3.5
3.3.1.6
Expected Horizontal Error / Quality Factor
C.3.6
3.3.1.7
Processing Anomalies
C.3.7
3.3.2
MEOLUT Data Exchange
3.3.2.1
Beacon Detection Probability (T(OB)) Partially Overlapping Bursts
C.3.1
3.3.2.2
Beacon Detection Probability (T) Non ELT(DT) Beacons
C.3.2
3.3.2.3
Beacon Detection Probability (T) ELT(DT) Beacons
C.3.3
3.3.2.4
Probability of DOA Location (PDL)
C.3.4
3.3.2.5
Location Accuracy
C.3.5
3.3.2.6
Expected Horizontal Error / Quality Factor
C.3.6
3.3.2.7
TOA/FOA Measurement Accuracy
C.3.7
3.3.2.8
Processing Anomalies
C.3.8
3.3.3
Combined Non-MEOSAR Satellite Statistics
3.3.3.1
Beacon Detection Probability (T(OB)) Partially Overlapping Bursts
C.3.1
3.3.3.2
Beacon Detection Probability (T) Non ELT(DT) Beacons
C.3.2
3.3.3.3
Beacon Detection Probability (T) ELT(DT) Beacons
C.3.3
3.3.3.4
Probability of DOA Location (PDL)
C.3.4
3.3.3.5
Location Accuracy
C.3.5
3.3.3.6
Expected Horizontal Error / Quality Factor
C.3.6
3.3.3.7
Processing Anomalies
C.3.8
A-18
Table A.4: MEOLUT Test Beacon Location Table
Beacon
Number
Beacon Identifier
Longitude
(Degrees East)
Latitude
(Degrees North)
Altitude
(metres)
…
n
A-19
A.3
MEOLUT Critical Changes Implementation
The implementation status of the MEOLUT critical changes decided by the Council shall be reported
in Table A.5 provided in the MEOLUT commissioning report.
Table A.5: Implementation Status of MEOLUT Critical Changes
Reference
Brief Description
Status
(Implemented/Not implemented/Date of
future implementation)
MEOLUT-1
MEOLUT-2
…
MEOLUT-N
A-20
Appendix 1 - Technical File
A.1
General
This appendix defines LUT information to be provided by national Administrations for LUT
commissioning. The following information is required as a minimum:
A.2
LUT Hardware Description
A.2.1 Antenna Characteristics
a) number and type(s) of antennas
b) gain/temperature ratio (G/T) at 5˚ elevation angle above the local horizon, and actual elevation
angle at which the G/T was measured
c) operational limitations
d) dedicated or shared
e) site-horizon profile
f) operational-tracking (elevation) limits
g) downlink frequency (S/L band)
Table A.6: MEOLUT Antenna Location Table
Antenna
Number
Antenna
Diameter
(if applicable)
(m)
Longitude
(Degrees East)
Latitude
(Degrees North)
Altitude
(m)
…
n
A-21
A.2.2 General LUT Indoor Equipment Description
a) equipment complement
b) stand alone, shared, or collocated with MCC
c) LUT manufacturer and model number
d) status and alarm functions
e) location – latitude, longitude, altitude
A.2.3 General Capabilities
a) specific processing capability
b) spectrum monitoring capability
c) optional capabilities
A.3
Processing
a) specific-performance capability
b) manufacturer specifications
c) processing bandwidth, signal sensitivity and beacon processing capacity of each data channel
A.4
Communications Capability – internal and external
a) primary-mode configuration
b) backup-mode configuration
A.5
Coverage Area
Describe the Declared Coverage Area of the MEOLUT system.
The description of the Declared Coverage Area shall be accompanied, if applicable, with the following:
1) Satellite tracking schedule used;
2) Description of DCA as:
a) the latitude and longitude values of the DCA contour, and/or
b) the coverage radius around the MEOLUT;
3) Graphical plots of performance analysis or simulation should:
a) Indicate the DCA,
b) Provide a legend of all colors and/or scales used;
4) Beacon characteristics including transmission pattern;
5) Simulation time period and step size;
A-22
6) Simulation grid size;
7) List the C/S T.019 performance requirements used as criteria to determine the DCA;
8) Performance and modelling assumptions and their dependencies, such as:
a) Detection performance as a function of elevation angle or received signal strength,
b) Standard deviation (1 sigma) TOA and FOA accuracy, as a function of beacon elevation angle
or received signal strength,
c) A description of methodology used for location accuracy assessment at a given grid node (e.g.,
statistical EHE calculation or modelling of the complete detection and location process used
by the MEOLUT);
9) A description of any empirical basis for performance assumptions such as type of test sources
(beacon simulator or operational beacons).
A.6
MEOLUT Network
For a networked MEOLUT, this section shall include a list of all the other MEOLUTs that exchange
data with this MEOLUT and their status (commissioned or not).
A.7
MEOLUT Designated Reference Beacons List
This section shall include the list of all designated QMS reference beacons, as described in document
C/S A.003, that are planned for use for the QMS of the MEOLUT1.
- END OF ANNEX A -
1 A list of available designated QMS reference beacons is available on the Cospas-Sarsat website.
B-1
ANNEX B
STATISTICS FOR OPERATIONAL REQUIREMENTS
B.1
MEOLUT Data Availability (A)
Measurement during the commissioning period
MEOLUT data availability measures the probability of receiving complete and accurate MEOLUT
data at the MCC. Availability (A) is expressed as a percentage and is calculated by dividing the amount
of operational time (OT) by the time required to be in operation (OTR). The time required to be in
operation (OTR), expressed in hours, is 24 times the number of days in the commissioning period
inclusive of all maintenance downtime. Downtime (DT) is that period of time when the performance
of the MEOLUT is below the minimum requirements specified in document C/S T.019 over the
Declared Coverage Area in the configuration for which the MEOLUT was commissioned. Therefore:
A = (OT / OTR) * 100 = (1 - (DT / OTR)) * 100 and shall be greater than 95.
Prediction
A reliability analysis shall be performed and the results reported to verify that the MEOLUT will meet
the availability requirement. The analysis shall be based on industry standard methodology using Mean
Time Between Failure (MTBF) and Mean Time To Repair (MTTR) values for all the components and
interfaces comprising the MEOLUT.
- END OF ANNEX B -
C-1
ANNEX C
STATISTICS FOR PERFORMANCE REQUIREMENTS
C.1
Commissioning Status
C.1.1 General
This annex describes the statistics to be provided to the Cospas-Sarsat Secretariat when commissioning
a MEOLUT.
For the 406 MHz solution statistics, the report must include a list of all 406 MHz beacons used for the
statistical data analysis.
C.2
C/S T.001 Beacon Statistics
C.2.1 Beacon Detection Probability (T)
Statistics will be generated using the test script identified in Annex D.3.1 to meet the following
requirements:
Calculate:
T = N / B
where:
N = number of 10-minute windows for which the MEOLUT produced a valid message within
10 minutes from the first beacon message transmission for each beacon ID
B = total number of 10-minute windows (not overlapping) within the duration of the beacon
activation period2 for each beacon ID
The test script will be executed a minimum of four times producing a minimum of 1,200 bursts in
4x25=100 windows.
The value of T using data from all test beacon IDs shall be 0.99 or greater.
Detection Probability statistics shall be provided for each motion configuration defined in
section C.2.4.
2 A MEOLUT shall not use information from past 10-minute windows to improve beacon message detection in
subsequent 10-minute windows (this might require a specific MEOLUT test set up to force a reset of the detection
mechanism)
C-2
C.2.2 ELT(DT) Beacon Detection Probability (T(DT))
Statistics will be generated using the test script identified in Annex D.3.2.1 to meet the following
requirements:
Calculate:
T(DT) = N / B
where:
N = number of 1-minute windows for which the MEOLUT produced at least one complete
message for each beacon ID
B = total number of 1-minute windows (not overlapping) within the duration of the beacon
activation period for each beacon ID
The value of T(DT) using data from all test beacon IDs shall be 0.99 or greater.
C.2.3 Probability of DOA Location (PDL)
Single Burst
Statistics will be generated using the test script identified in Annex D.3.1 to meet the
following requirements:
PDL = M/N
where:
M = number of DOA single-burst locations produced by the MEOLUT for a test beacon,
within three minutes of the single burst transmission
N = total number of beacon bursts transmitted by the test beacons
PDL shall be 0.90 or greater
Within 10 minutes
Statistics will be generated using the test script identified in Annex D.3.1 to meet the
following requirements:
PDL = M/N
where:
M = number of beacons that produced a DOA location within 10 minutes from the first beacon
message transmission
N = total number of test beacons (i.e., the maximum value of YY within the script)
PDL shall be 0.98 or greater.
A set of single-burst and 10-minute PDL statistics shall be provided for each motion configuration
defined in section C.2.4.
C-3
C.2.4 Location Accuracy
For each DOA location solution used in generating the location performance statistics defined in the
sections below, the associated location error shall be determined using the known beacon position at
the time of the last burst used in the DOA location solution.
Single burst solutions
Statistics will be generated using the test script identified in Annex D.3.1 (the test script will be
executed a minimum of four times producing a minimum of 1,200 bursts), or a test beacon for moving
configurations to meet the following requirements:
Configuration 1: static beacon
M/N shall be greater than or equal to the following:
0.90 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 2: nearly-static beacon (velocity = 0.4 m/s)
M/N shall be greater than or equal to the following:
0.90 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 3.1: (low speed) slow-moving beacon (velocity = 2 m/s)
M/N shall be greater than or equal to the following:
0.70 where:
M = number of solutions within 10 km
N = number of solutions
0.95 where:
M = number of solutions within 20 km
N = number of solutions
Configuration 3.2: (low speed) slow-moving beacon (velocity = 5 m/s)
M/N shall be greater than or equal to the following:
0.70 where:
M = number of solutions within 10 km
N = number of solutions
0.95 where:
M = number of solutions within 20 km
N = number of solutions
Configuration 43: (medium speed) slow-moving beacon (velocity = [5 to 10] m/s)
M/N shall be greater than or equal to the following:
0.70 where:
M = number of solutions within 10 km
3 Testing of Configuration 4 is not required for MEOLUT commissioning until the test velocity (in brackets) is
finalized for Configuration 4, but could be provided if available.
C-4
N = number of solutions
0.95 where:
M = number of solutions within 20 km
N = number of solutions
Configuration 54: fast-moving beacon (velocity > 10 m/s)
M/N shall be greater than or equal to the following:
0.90 where:
M = number of solutions within TBD km
N = number of solutions
For each configuration, a histogram for the location accuracy of the correct solutions shall be provided.
The histogram shall be in 1 km increments from 0 to 20 km. All solutions with an error greater than
20 km shall be individually listed and an explanation for the error provided. The cumulative
distribution function based on the histogram shall also be provided.
Solutions within 10 minutes
Statistics will be generated using the test script identified in Annex D.3.1, or a test beacon for
moving configurations, to meet the following requirements:
Configuration 1: static beacon
M/N shall be greater than or equal to the following (M and N are solutions produced within
10 minutes from the first beacon message transmission):
0.95 where:
M = number of solutions within 5 km
N = number of solutions
0.98 where:
M = number of solutions within 10 km
N = number of solutions
Configuration 2: nearly-static beacon (velocity = 0.4 m/s)
M/N shall be greater than or equal to the following (M and N are solutions produced within
10 minutes from the first beacon message transmission):
0.95 where:
M = number of solutions within 5 km
N = number of solutions
0.98 where:
M = number of solutions within 10 km
N = number of solutions
4 Testing of Configuration 5 is not required for MEOLUT commissioning until the location accuracy performance
requirement (noted TBD) is finalized.
C-5
Configuration 3.1: (low speed) slow-moving beacon (velocity = 2 m/s)
M/N shall be greater than or equal to the following) (M and N are solutions produced within
10 minutes from the first beacon message transmission):
0.75 where:
M = number of solutions within 5 km
N = number of solutions
0.95 where:
M = number of solutions within 7 km
N = number of solutions
Configuration 3.2: (low speed) slow-moving beacon (velocity = 5 m/s)
M/N shall be greater than or equal to the following) (M and N are solutions produced within
10 minutes from the first beacon message transmission):
0.75 where:
M = number of solutions within 5 km
N = number of solutions
0.95 where:
M = number of solutions within 7 km
N = number of solutions
Configuration 45: (medium speed) slow-moving beacon (velocity = [5 to 10] m/s)
M/N shall be greater than or equal to the following:
0.70 where:
M = number of solutions within 10 km
N = number of solutions
0.95 where:
M = number of solutions within 20 km
N = number of solutions
Configuration 56: fast-moving beacon (velocity > 10 m/s)
M/N shall be greater than or equal to the following) (M and N are solutions produced within
10 minutes from the first beacon message transmission):
0.95 where:
M = number of solutions within TBD km
N = number of solutions
0.98 where:
M = number of solutions within TBD km
N = number of solutions
For each configuration, a histogram for the location accuracy of the correct solutions shall be provided.
The histogram shall be in 1 km increments from 0 to 20 km. All solutions with an error greater than
5 Testing of Configuration 4 is not required for MEOLUT commissioning until the test velocity (in brackets) is
finalized for Configuration 4, but could be provided if available.
6 Testing of Configuration 5 is not required for MEOLUT commissioning until the location accuracy performance
requirement (noted TBD) is finalized.
C-6
20 km shall be individually listed and an explanation for the error provided. The cumulative
distribution function based on the histogram shall also be provided.
The location selection methodology, if any, used to generate the 10-minute location accuracy statistics
shall be documented in the MEOLUT commissioning report7.
C.2.5 Expected Horizontal Error / Quality Factor
For each test configuration in section C.2.4, compare each beacon DOA location produced by the
MEOLUT with the known location of the test beacon (at the time of the last burst used in the DOA
location) to derive the actual location error.
Check that the Expected Horizontal Error is as follows:
NC1/10/NL < 0.15
0.93 ≤ NC1/NL ≤ 0.97
NC2/NL < 0.01
With:
NC1/10 = number of locations with a location error < EHE/10
NC1 = number of locations with a location error < EHE
NC2 = number of locations with a location error > 2 x EHE
NL = total number of locations
In addition to each test configuration, EHE results should be reported for different location categories
(containing at least 1,000 locations each), in order to avoid any averaging effect of the results. These
categories8 are:
•
Single-burst locations for at least one static primary test beacons within the DCA,
•
Single-burst locations for at least one primary test slow-moving beacon within the DCA,
•
Multi-burst locations for at least one static primary test beacons within the DCA,
•
Multi-burst locations for at least one primary test slow-moving beacon within the DCA,
•
Locations for other available test beacons and for all active reference beacons located inside
the DCA,
•
Locations for at least one other test beacon if available and for all active reference beacons
located outside the DCA, which were detected by the MEOLUT under test.
Plot the cumulative distribution of location error normalized by the EHE for each category tested from
the above list. Include with each plot the EHE limit mask as illustrated in Figure C.1 below. In this
figure, points 1, 2, 3 and 4 bound the EHE mask, and the dotted curve is an example of a hypothetical
cumulative distribution plot that would meet the performance requirement. The reported cumulative
distribution for each plot must pass below point 1, between points 2 and 3, and above point 4 in order
to meet the required performance.
7 E.g., all locations produced by the MEOLUT are used, or locations with lowest EHE values over 10 minutes, or with
higher number of bursts or satellites, or last solution received in the 10 minute window, other.
8 Testing for fast-moving beacon to be determined.
C-7
Figure C.1: (Location Error)/EHE Cumulative Distribution
C.2.6 TOA/FOA Measurement Accuracy
For each received beacon transmission received on each satellite channel:
1. Filter out beacon transmissions received with received C/N0 less than 34.8 dBHz or greater
than 37.8 dBHz.
2. Determine the TOA and FOA measurement error using the known beacon position.
From the beacon log data as defined in Annex E (in particular the transmission time and frequency of
the transmitted bursts), calculate:
1. The standard deviation of the error of the TOA and FOA measurements for all filtered beacon
messages.
2. The bias of the mean of the error of the TOA and FOA measurements.
The standard deviation of the error shall be:
Better than 25 microseconds for TOA
Better than 0.20 Hz for FOA
The bias of the mean of the error shall be:
Less than 2.5 microseconds for TOA
Less than 0.02 Hz for FOA
C.2.7 Processing Anomalies
From the beacon message data table (see section E.3), collect detected C/S T.001 beacon messages
received on the transmitted test beacon frequency  2 kHz.
Count all messages (NM).
![Image 1 from page 49](/images/cospas-sarsat/T-series/T020/T020_page_49_img_1.png)
C-8
Count all anomalies (NA) which are defined as any beacon 15 hex ID that does not match exactly the
15 hex ID of the beacons known to transmit within the test beacon frequency  2 kHz (e.g., test
beacons, reference beacons, etc.).
Determine the probability (PA) to detect an anomaly:
PA = NA / NM
Check that PA is less than 10-4.
C.3
C/S T.018 Beacon Statistics
C.3.1 Partially Overlapping Beacon Detection Probability (T(OB))
Statistics will be generated using the test script identified in Annex D.4.1.1 to meet the following
requirements.
Configuration 1: static beacon
Calculate:
T(OB) = N / B
where:
N = number of beacon messages for which the MEOLUT produced a valid message for each
transmitted beacon ID
B = total number of beacon messages transmitted for each beacon ID
The value of T(OB) using data from all test beacon IDs shall be 0.95 or greater.
C.3.2 Beacon Detection Probability (T)
Statistics will be generated using the test script identified in Annex D.4.1.2 to meet the following
requirements:
Calculate:
T = N / B
where:
N = number of 30-second windows for which the MEOLUT produced a valid message within
30-seconds from the first beacon message transmission for each beacon ID
B = total number of 30-second windows (not overlapping) within the duration of the beacon
activation period or each beacon ID
The value of T using data from all test beacon IDs shall be 0.999 or greater.
Detection Probability statistics shall be provided for each motion configuration defined in
section C.2.4.
C-9
C.3.3 ELT(DT) Beacon Detection Probability (T(DT))
Statistics will be generated using the test script identified in Annex D.4.2 to meet the following
requirements:
Calculate:
T(DT) = N / B
where:
N = number of 1-minute windows for which the MEOLUT produced at least one valid message
for each beacon ID
B = total number of 1-minute windows (not overlapping) within the duration of the beacon
activation period for each beacon ID
The value of T(DT) using data from all test beacon IDs shall be 0.99 or greater.
C.3.4 Probability of DOA Location (PDL)
Single Burst
Statistics will be generated using data resulting from the execution of all the test scripts
identified in Annexes D.4.1.2, D.4.1.3, D.4.1.4 and D.4.1.5 to meet the following
requirements:
PDL = M/N
where:
M = number of DOA single-burst locations produced by the MEOLUT for a test beacon,
within three minutes of the single burst transmission.
N = total number of beacon messages transmitted by the test beacons
PDL shall be 0.95 or greater
Within 30 seconds
Statistics will be generated using the test script identified in Annex D.4.1.2 to meet the
following requirements:
PDL = M/N
where:
M = number of beacons that produced a DOA location
N = total number of test beacons
PDL shall be 0.98 or greater.
Within 5 minutes
Statistics will be generated using the test script identified in Annex D.4.1.3 to meet the
following requirements:
C-10
PDL = M/N
where:
M = number of beacons that produced a DOA location
N = total number of test beacons
PDL shall be 0.98 or greater.
Within 30 minutes
Statistics will be generated using the test script identified in Annex D.4.1.4 to meet the
following requirements:
PDL = M/N
where:
M = number of beacons that produced a DOA location
N = total number of test beacons
PDL shall be 0.98 or greater.
A set of single-burst and 10-minute PDL statistics shall be provided for each motion configuration
defined in section C.2.4.
C.3.5 Location Accuracy
For each DOA location solution used in generating the location performance statistics defined in the
sections below, the associated location error shall be determined using the known beacon position at
the time of the last burst used in the DOA location solution.
Single burst solutions
Statistics will be generated using data resulting from the execution of all the test scripts
identified in Annexes D.4.1.2, D.4.1.3, D.4.1.4 and D.4.1.5 to meet the following
requirements:
Configuration 1: static beacon
M/N shall be greater than or equal to the following:
0.95 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 2: nearly-static beacon (velocity = 0.4 m/s)
M/N shall be greater than or equal to the following:
0.95 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 3.1: (low speed) slow-moving beacon (velocity = 2 m/s)
C-11
M/N shall be greater than or equal to the following:
0.95 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 3.2: (low speed) slow-moving beacon (velocity = 5 m/s)
M/N shall be greater than or equal to the following:
0.95 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 49: (medium speed) slow-moving beacon (velocity = [5 to 10] m/s)
M/N shall be greater than or equal to the following:
0.95 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 510: fast-moving beacon (velocity > 10 m/s)
M/N shall be greater than or equal to the following:
0.95 where:
M = number of solutions within TBD km
N = number of solutions
For each configuration, a histogram for the location accuracy of the correct solutions shall be provided.
The histogram shall be in 1 km increments from 0 to 20 km. All solutions with an error greater than
20 km shall be individually listed and an explanation for the error provided. The cumulative
distribution function based on the histogram shall also be provided.
Solutions within 30 seconds after beacon activation
Statistics will be generated using the test script identified in Annex D.4.1.2 to meet the
following requirements:
Configuration 1: static beacon
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 2: nearly-static beacon (velocity = 0.4 m/s)
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within 5 km
9 Testing of Configuration 4 is not required for MEOLUT commissioning until the test velocity (in brackets) is
finalized for Configuration 4, but could be provided if available.
10 Testing of Configuration 5 is not required for MEOLUT commissioning until the location accuracy performance
requirement (noted TBD) is finalized.
C-12
N = number of solutions
Configuration 3.1: (low speed) slow-moving beacon (velocity = 2 m/s)
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 3.2: (low speed) slow-moving beacon (velocity = 5 m/s)
M/N shall be greater than or equal to the following) (M and N are solutions produced within
10 minutes from the first beacon message transmission):
0.97 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 411: (medium speed) slow-moving beacon (velocity = [5 to 10] m/s)
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within 5 km
N = number of solutions
Configuration 512: fast-moving beacon (velocity > 10 m/s)
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within TBD km
N = number of solutions
For each configuration, a histogram for the location accuracy of the correct solutions shall be provided.
The histogram shall be in 1 km increments from 0 to 20 km. All solutions with an error greater than
20 km shall be individually listed and an explanation for the error provided. The cumulative
distribution function based on the histogram shall also be provided.
Solutions within 5 minutes after beacon activation
Statistics will be generated using the test script identified in Annex D.4.1.3 to meet the
following requirements:
Configuration 1: static beacon
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within 1 km
N = number of solutions
11 Testing of Configuration 4 is not required for MEOLUT commissioning until the test velocity (in brackets) is
finalized for Configuration 4, but could be provided if available.
12 Testing of Configuration 5 is not required for MEOLUT commissioning until the location accuracy performance
requirement (noted TBD) is finalized.
C-13
Configuration 2: nearly-static beacon (velocity = 0.4 m/s)
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within 1 km
N = number of solutions
Configuration 3.1: (low speed) slow-moving beacon (velocity = 2 m/s)
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within 1 km
N = number of solutions
Configuration 3.2: (low speed) slow-moving beacon (velocity = 5 m/s)
M/N shall be greater than or equal to the following) (M and N are solutions produced within
10 minutes from the first beacon message transmission):
0.97 where:
M = number of solutions within 1 km
N = number of solutions
Configuration 413: (medium speed) slow-moving beacon (velocity = [5 to 10] m/s)
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within 1 km
N = number of solutions
Configuration 514: fast-moving beacon (velocity > 10 m/s)
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within TBD km
N = number of solutions
For each configuration, a histogram for the location accuracy of the correct solutions shall be provided.
The histogram shall be in 0.2 km increments from 0 to 10 km. All solutions with an error greater than
10 km shall be individually listed and an explanation for the error provided. The cumulative
distribution function based on the histogram shall also be provided.
Solutions within 30 minutes after beacon activation
Statistics will be generated using the test script identified in Annex D.4.1.4 to meet the
following requirements:
Configuration 1: static beacon
M/N shall be greater than or equal to the following:
13 Testing of Configuration 4 is not required for MEOLUT commissioning until the test velocity (in brackets) is
finalized for Configuration 4, but could be provided if available.
14 Testing of Configuration 5 is not required for MEOLUT commissioning until the location accuracy performance
requirement (noted TBD) is finalized.
C-14
0.97 where:
M = number of solutions within 0.1 km
N = number of solutions
Configuration 2: nearly-static beacon (velocity = 0.4 m/s)
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within 0.1 km
N = number of solutions
For each configuration, a histogram for the location accuracy of the correct solutions shall be provided.
The histogram shall be in 20 m increments from 0 to 1 km. All solutions with an error greater than
1 km shall be individually listed and an explanation for the error provided. The cumulative distribution
function based on the histogram shall also be provided.
Solutions after 30 minutes after beacon activation
Statistics will be generated using the test script identified in Annex D.4.1.5 to meet the
following requirements:
M/N shall be greater than or equal to the following:
0.97 where:
M = number of solutions within 0.1 km
N = number of solutions
A histogram for the location accuracy of the correct solutions shall be provided. The histogram shall
be in 20 m increments from 0 to 1 km. All solutions with an error greater than 1 km shall be individually
listed and an explanation for the error provided. The cumulative distribution function based on the
histogram shall also be provided.
The location selection methodology, if any, used to generate the 30-second, 5-minute and 30-minute
location accuracy statistics shall be documented in the MEOLUT commissioning report15.
C.3.6 Expected Horizontal Error / Quality Factor
For each test configuration in section C.3.4, compare each beacon DOA location produced by the
MEOLUT with the known location of the test beacon (at the time of the last burst used in the DOA
location) to derive the actual location error.
Check that the Expected Horizontal Error is as follows:
NC1/10/NL < 0.15
0.93 ≤ NC1/NL ≤ 0.97
NC2/NL < 0.01
With:
NC1/10 = number of locations with a location error < EHE/10
15 E.g., all locations produced by the MEOLUT are used, or locations with lowest EHE values over 30 seconds,
5 minutes and 30 minutes, or with higher number of bursts or satellites, or last solution received in the 30-second,
5-minute and 30-minute window, other.
C-15
NC1 = number of locations with a location error < EHE
NC2 = number of locations with a location error > 2 x EHE
NL = total number of locations
In addition to each test configuration, EHE results should be reported for different location categories
(containing at least 1,000 locations each), in order to avoid any averaging effect of the results. These
categories16 are:
•
Single-burst locations for at least one static primary test beacon within the DCA,
•
Single-burst locations for at least one primary test slow-moving beacon within the DCA,
•
Multi-burst locations for at least one static primary test beacon within the DCA,
•
Multi-burst locations for at least one primary test slow-moving beacon within the DCA,
•
Locations for other available test beacons and for all active reference beacons located inside
the DCA,
•
Locations for at least one other test beacon if available and for all active reference beacons
located outside the DCA, which were detected by the MEOLUT under test.
Plot the cumulative distribution of location error normalized by the EHE for each category tested from
the above list. Include with each plot the EHE limit mask as illustrated in Figure C.1 from section
C.2.5. In this figure, points 1, 2, 3 and 4 bound the EHE mask, and the dotted curve is an example of a
hypothetical cumulative distribution plot that would meet the performance requirement. The reported
cumulative distribution for each plot must pass below point 1, between points 2 and 3, and above
point 4 in order to meet the required performance.
C.3.7 TOA/FOA Measurement Accuracy
For each received beacon message:
1. Filter out messages with received C/N0 less than [30.55] dBHz or greater than [33.55] dBHz.
2. Determine the TOA and FOA measurement error using the known beacon position.
From the beacon log data as defined in Annex E (in particular the transmission time and frequency of
the transmitted bursts), calculate:
1. The standard deviation of the error of the TOA and FOA measurements for all filtered beacon
messages.
2. The bias of the mean of the error of the TOA and FOA measurements.
The standard deviation of the error shall be:
Better than [1] microseconds for TOA
Better than [0.2] Hz for FOA
The bias of the mean of the error shall be:
Less than [0.2] microseconds for TOA
Less than [0.02] Hz for FOA
16 Testing for fast moving beacon to be determined.
C-16
C.3.8 Processing Anomalies
From the beacon message data table (see section E.3), collect detected C/S T.018 beacon messages
received within ± 10 Hz from the expected received test-beacon frequency17.
Count all messages (NM).
Count all anomalies (NA) which are defined as any beacon 23 Hex ID that does not match exactly the
23 Hex ID of the beacons known to transmit within the test beacon frequency 10 Hz (e.g., test beacons,
reference beacons, etc.).
Determine the probability (PA) to detect an anomaly:
PA = NA / NM
Check that PA is less than 10-4.
- END OF ANNEX C -
17 The expected received test beacon frequency depends on the beacon-to-satellite geometry, and thus is a function of
the satellite channel; the expected received frequency of the test beacons or beacon simulator shall be then determined
for each satellite channel, to allow the collection of received messages within ± 10 Hz of the expected received test
beacon frequency.
D-1
ANNEX D
BEACON SIMULATOR TEST SCRIPT
D.1
C/S T.001 Message Processing Testing
D.1.1 C/S T.001 Test Messages to be Transmitted
Test
Code
Sequence
Simulator
Transmit
Frequency
(MHz)
Date/Time
(UTC)
Transmitted
30 Hex Transmitted Message
(15 Hex Identifier, bits 26-85)
Number of Bit Errors
Comments
PDF-1 BCH-
PDF-2 BCH-
Bit Rate Tolerance Check (BR)
BR1
[TBD]
406.064
[TBD]
96EEF9DA0A2BA9EB5F96F400000F19
(2DDDF3B414FFBFF)
Transmit 20 bursts at the lower end of the permissible Bit
Rate Range (396 bps)
[TBD]
406.064
[TBD]
96EEF9DA0A2BA9EB5F96F400000F19
Transmit 20 bursts at the higher end of the permissible Bit
Rate Range (404 bps)
Bit Verification (BV)
BV1
USA
406.064
[TBD]
56EE1100000000037E540000000000
(ADDC22000000000)
n/a
n/a
USA, User Test coded beacon with two (2) bit errors
introduced at bits 44 and 48 in PDF-1.
BV2
USA
406.064
[TBD]
D6E10E1A4324920458B9D555555555
(ADC21C348649240)
USA, Orbitography beacon with a pattern of Α01" in the long
message. No bit errors
406.064
[TBD]
D6E10E1A4324920458B9D555555555
Same as above
BV3
USA
406.064
[TBD]
D6EEAAAAAAAAAAA2EA1A24E14CD2F4
(ADDD55555555554)
USA, User Test coded beacon with encoded position
(39, -76.86667) in PDF-2. One bit error at bit 138.
Message Validation (MV)
MV1
USA
406.064
[TBD]
D6EE1100000000265F1424DB4CEFBF
(ADDC22000000004)
USA, User Test coded beacon with encoded position
(38.8667, -76.933) in PDF-1 and PDF-2. Two (2) bit errors at
bits 44 and 48 in PDF-1. Two (2) bit errors at bits 133 and 134
in BCH-2
D-2
Test
Code
Sequence
Simulator
Transmit
Frequency
(MHz)
Date/Time
(UTC)
Transmitted
30 Hex Transmitted Message
(15 Hex Identifier, bits 26-85)
Number of Bit Errors
Comments
PDF-1 BCH-
PDF-2 BCH-
406.064
D6EE0011100000265F1424DB4CE3BF
Three (3) bit errors at bits 52, 56 and 60 in PDF-1.
MV2
USA
406.064
[TBD]
96EE0000002729A5E22BB61B842E0A
(2DDC000000FFBFF)
USA, Standard Location Protocol Test coded beacon with
encoded position (38.884, -76.931) in PDF-1 and PDF-2.
406.064
96EE0000002729A5E22BB61B842E0A
Same as above
406.064
96EE0000002729A5E22BB61B842E0A
Same as above
406.064
[TBD]
96EE00000029299B91383601261D93
Position updated to (40.996, -76.851).
406.064
96EE00000029299B91383601261D9F
Two (2) bit errors at bits 141 and 142 in BCH-2.
MV5
France
406.064
[TBD]
8E3E0000002B80372E8B968E01107B
(1C7C000000FFBFF)
France, Standard Location Test Encoded position (43.559,
1.482) in PDF-1 and PDF-2.
Fixed Bit 107 in error
Bits 107-110=0101 instead of 1101
MV6
France
406.064
[TBD]
8E3F00000AE2017508A9BE0F380330
(1C7E00003F81FE0)
France, National Location Test Protocol Encoded position
(43.559, 1.482) in PDF-1 and PDF-2
Bit 109 in error.
Bit 107-109= 111 instead of 110
Invalid Message Processing (IMP)
IMP1
France
406.064
[TBD]
8E3E0780002B80372E8BB68E011E5C
(PDF1: 1C7C0F000057006)
Transmission power 40 dBm
France, Test User
Four (4) bit errors at bits 46, 47,48 and 49 in PDF-1.
Location Protocol Processing (LP)
LP1
France
406.064
[TBD]
8E3E0000007FDFFC77A376000003DD
(1C7C000000FFBFF)
France, Standard Location Protocol Test coded beacon with
default encoded position in PDF-1 and 0s in PDF-2.
406.064
8E3E0000007FDFFC77A376000003DD
Same as above
406.064
8E3E0000007FDFFC77A376000003DD
Same as above
406.064
8E3E0000002B80372E8BB68E011E5C
Encoded position (43.559, 1.482) in PDF-1 and PDF-2
406.064
8E3E0000002B80372E8BB68E011E5C
Same as above
406.064
8E3E0000002B80372E8BB68E011E5C
Same as above
D-3
Test
Code
Sequence
Simulator
Transmit
Frequency
(MHz)
Date/Time
(UTC)
Transmitted
30 Hex Transmitted Message
(15 Hex Identifier, bits 26-85)
Number of Bit Errors
Comments
PDF-1 BCH-
PDF-2 BCH-
LP2
France
406.064
[TBD]
8E3F00000AA20175813BB60F380F6B
(1C7E00003F81FE0)
Encoded position (42.559, 1.482) in PDF-1 and PDF-2
406.064
8E3F00000AA20175813BB60F380F6B
Same as above
406.064
8E3F00000AA20175813BB60F380F6B
Same as above
406.064
8E3F00000AE2017508A9B60F380F6B
France, National Location Protocol Test coded beacon with
encoded position (43.559, 1.482) in PDF-1 and PDF-2
406.064
8E3F00000AE2017508A9B60F380F6B
Same as above
406.064
8E3F00000AE2017508A9B60F380F6B
Same as above
LP3
USA
406.064
[TBD]
D6EE1F1E1E1E1E06A383EFE0FF0146
(ADDC3C3C3C3C3C0)
USA, User Test coded beacon with user default information
in PDF-2. One (1) bit error at bit 48 in PDF-1
406.064
D6EE1F1E1E1E1E06A383E4E14CD2BE
Updated user information in PDF-2. One (1) bit error in bit 48
in PDF-1 and two (2) bit errors at bits 141 and 143 in BCH-2.
406.064
D6EE1F1E1E1E1E06A383E4E14CD2BE
One (1) bit error in bit 48 in PDF-1 and two (2) bit errors at
bits 141 and 143 in BCH-2.
406.064
D6EE1F1E1E1E1E06A383E4E14CD2B4
One (1) bit error in bit 48 in PDF-1.
LP4
USA
406.064
[TBD]
96EF000049C14CD260D5F608380389
(2DDE0000BF81FE0)
USA, National Location Protocol Test Coded beacon with
encoded position (38.996, -76.851).
406.064
96EF000049C14CD260D5F608380389
Same as above.
406.064
96EF000049814CD2E947F608380389
Encoded position (37.996, -76.851) updated.
406.064
96EF000049814CD2E947F60838038F
Two (2) bit errors in bits 142 and 143.
406.064
96EF000049814CD2E947F6083803E9
Two (2) bit errors in bits 138 and 139.
Return Link (RL)
RL1
France
406.064
[TBD]
8E3DC990004AE01ABB608866E0E91B
(1C7B932000BFDFF)
RLS Location protocol encoded position (43.558, 1.484) in
PDF-1 and PDF-2. The message shall be transmitted 12
times with a repetition period of 50 seconds.
406.064
[TBD]
8E3DC990004AE01ABB608A66E0E5DF
(1C7B932000BFDFF)
RLS Acknowledgment Message. The message shall be
transmitted 12 times with a repetition period of 50 seconds.
D-4
C/S T.001 ELT(DT) Functional Validation Script
This script aims at validating specific management of ELT(DT) alerts at MEOLUT level.
The script is composed of one beacon transmitting the following sequence:
•
24 nominal bursts with 5 second repetition rate,
•
18 nominal bursts with 10 second repetition rate,
•
6 nominal bursts with 28.5 second repetition rate,
•
10 cancellation bursts with 10 second repetition rate,
•
no transmission during 2 minutes,
•
24 nominal bursts with 5 second repetition rate,
•
18 nominal bursts with 10 second repetition rate,
•
6 nominal bursts with 28.5 second repetition rate.
The transmissions shall not use an operational channel of the 406 MHz bandwidth and shall be transmitted
with a nominal power of 37 dBm. Beacon message should be encoded using normal mode and ELT(DT)
Location Test protocol in bits 43-66.
The possible combinations of 15 Hex IDs are described in the table below, considering the possible
combinations of bits 41-66, and the French country code and location bits 67-85 defaulted to the values
specified in section A3.2 of document C/S T.001. Note that the location bits in PDF-1 and PDF-2 in the
actual transmitted messages will change from burst to burst to simulate motion.
Bits 43-66
All “0”
All “1”
Bits 41-42
1C520 00000 3FDFF
1C527 FFFFF BFDFF
1C528 00000 3FDFF
1C52F FFFFF BFDFF
1C530 00000 3FDFF
1C537 FFFFF BFDFF
Additional beacon message definition:
•
since the encoded location is encoded over PDF1 and PDF2 fields, both fields shall be constructed
to provide a location that changes from burst to burst, consistent with horizontal motion at a speed
of 1,200 km/h,
•
the last three nominal bursts of the first activation sequence shall contain the same encoded location,
•
the last three nominal bursts of the second activation sequence shall contain the default encoded
location,
•
the “means of activation” bits in PDF-2 should be set to ‘01’,
•
the “encoded altitude” bits should be set to a constant value of ‘0010’,
D-5
•
the “encoded location freshness” bits should be set to ‘11’.
The possible combinations of 15 Hex IDs of transmitted messages (using hexadecimal representation) of
the simulated beacon for cancellation transmission is coded as follow, considering the possible
combinations of bits 41-66, the French country code and the fixed bits for cancellation messages:
Bits 43-66
All “0”
All “1”
Bits 41-42
1C520 00000 7EBFA
1C527 FFFFF FEBFA
1C528 00000 7EBFA
1C52F FFFFF FEBFA
1C530 00000 7EBFA
1C537 FFFFF FEBFA
Note: the fixed bits of PDF-2 for cancellation message shall be set according to the beacon cancellation
message definition in document C/S T.001.
D-6
D.1.2 C/S T.001 Expected Processing
Test
Code
Sequence
Message to be Transmitted by
MEOLUT
Encoded
Location
Comments
BR1
96EEF9DA0A2BA9EB5F96F400000F19
n/a
MEOLUT sends a valid message to the MCC.
BV1
56EE0000000000037E540000000000
n/a
MEOLUT should correct two bit errors and transmit corrected message to the MCC.
BV2
D6E10E1A4324920458B9D555555555
n/a
MEOLUT should transmit orbitography beacon message without error correcting the long message.
BV3
D6EEAAAAAAAAAAA2EA1A24E14CD2B4
39, -76.86667
MEOLUT should correct error at bit 138 and transmit alert to the MCC.
MV1
D6EE0000000000265F1424FFFFFFFF
D6EE0000000000265F1424DB4CE3BF
n/a
38.8667, -76.933
For the first burst, MEOLUT corrects the beacon message (message is valid but not complete) and transmits the
corrected message to the MCC with bits 113 to 144 all set to “1".
For the second burst, MEOLUT corrects the beacon message (message is confirmed and complete) and transmits
the corrected message to the MCC.
MV2
96EE0000002729A5E22BB61B842E0A
96EE00000029299B91383601261D93
96EE00000029299B913836FFFFFFFF
38.884, -76.931
40.996, 76.851
n/a
For the first burst, the MEOLUT sends a complete, confirmed message to the MCC and calculates DOA position.
For the fourth burst the MEOLUT sends a complete, confirmed message to the MCC and calculates DOA position.
For the fifth burst the MEOLUT sends a confirmed but incomplete message to the MCC and calculates DOA position.
MV5
8E3E0000002B80372E8BBFFFFFFFFF
n/a
MEOLUT sends a confirmed invalid message with an independent location to the MCC without bit correction
in PDF1+BCH1 and with bits 107 to 144 set to “1”.
MV6
8E3F00000AE2017508A9BFFFFFFFFF
n/a
MEOLUT sends a confirmed invalid message with an independent location to the MCC without bit correction
in PDF1+BCH1 and with bits 107 to 144 set to “1”.
IMP1
Case 1: no message transmitted
Case 2:
8E3E0780002B80372E8BBFFFFFFFFF
n/a
Two outcomes are possible for this test:
Case 1: If 2 or less matching invalid messages, MEOLUT shall filter out messages.
Case 2: If 3 or more matching invalid messages, MEOLUT sends a confirmed invalid message with an independent
location to the MCC without bit correction in PDF1+BCH1 and with bits 107 to 144 set to “1”.
LP1
8E3E0000007FDFFC77A376000003DD
8E3E0000002B80372E8BB68E011E5C
Default location
43.559, 1.482
MEOLUT sends two confirmed messages with the update of the encoded position confirmed message for
Standard Location Protocol beacon to MCC and calculates DOA position associated with both messages.
D-7
Test
Code
Sequence
Message to be Transmitted by
MEOLUT
Encoded
Location
Comments
LP2
8E3F00000AA20175813BB60F380F6B
8E3F00000AE2017508A9B60F380F6B
42.559, 1.482
43.559, 1.482
MEOLUT sends updated, confirmed message for National Location Protocol beacon to MCC and calculates DOA
position.
LP3
1. D6EE1E1E1E1E1E06A383EFE0FF0146
2. and/or 3.
D6EE1E1E1E1E1E06A383E4FFFFFFFF
4.D6EE1E1E1E1E1E06A383E4E14CD2B4
n/a
MEOLUT sends:
From transmitted burst \#1: a confirmed or unconfirmed complete message (depending on the number matching
received messages).
From transmitted bursts \#2 or \#3: a confirmed incomplete message with PDF-2 defaulted with bits 113 to 144
set to “1”. Which burst is sent depends on which message is confirmed. If no confirmation is achieved, then no
message is sent.
From transmitted bursts \#4: a confirmed or unconfirmed complete message (depending on the number matching
received messages) with updated user information in new PDF-2.
LP4
96EF000049C14CD260D5F608380389
96EF000049814CD2E947F608380389
96EF000049814CD2E947F6FFFFFFFF
38.996, -76.851
37.996, -76.851
n/a
MEOLUT sends complete, confirmed message with an independent location to the MCC and calculates DOA
position.
For the third burst MEOLUT sends complete, confirmed message to the MCC and calculates DOA position.
For the fourth and fifth burst, the MEOLUT sends a confirmed but incomplete message to MCC depending on which
message is confirmed and calculates DOA position.
RL1
8E3DC990004AE01ABB608866E0E91B
8E3DC990004AE01ABB608A66E0E5DF
43.558, 1.484
Forward Link message: MEOLUT sends at least one complete message to the MCC.
Acknowledgment message: MEOLUT sends at least one complete acknowledgment message to the MCC.
C/S T.001 ELT(DT) Functional Validation Script
For the FGB ELT(DT) functional validation test, it should be verified that each received burst (as collected per Table E.3) results in an alert
message sent to the associated MCC (as collected per Table E.5).
D-8
D.2
C/S T.018 Message Processing Testing
D.2.1 C/S T.018 Test Messages to be Transmitted
Test Code
Sequence
Simulator
Transmit
Frequency
(MHz)
Date/Time
(UTC)
Transmitted
63 Hex Transmitted Message
(23 Hex Identifier)
Number of
Bit Errors
Comments
PDF
BCH
Message Recovery (MR)
MR1
[TBD]
406.05
[TBD]
3FFF1B0038C95C7BE00BD8CE0003A000400BFFF0000004C00587A6ECF9F8EA1
(9C77FFF1B00F0001D000200)
Transmit bursts with normal mode PRN
406.05
[TBD]
BFFF1B0038C95C7BE00BD8CE0003A000402BFFF0000004C00583EE3B7F96E32
(9C77FFF1B00F0001D000201)
Transmit bursts with self-test mode PRN
MR2
[TBD]
406.047
[TBD]
3FFF1B0038C95C7BE00BD8CE0003A000404BFFF0000004C0058F3743F524F87
(9C77FFF1B00F0001D000202)
Transmit 20 bursts at the lower limit of
the processing bandwidth
406.053
[TBD]
3FFF1B0038C95C7BE00BD8CE0003A000406BFFF0000004C0058B7F94734AF14
(9C77FFF1B00F0001D000203)
Transmit 20 bursts at the upper limit of
the processing bandwidth
Bit Verification (BV)
BV1
[TBD]
406.05
[TBD]
3FFF1B0038C95C7BE00BD8CE0F03A000440BFFF0000004C00580CD87F19B6B1
(9C77FFF1B00F0781D000220)
Transmit bursts with 6 bit errors on
PDF+BCH
Invalid Message Processing (IMP)
IMP1
[TBD]
406.05
[TBD]
3FFF1B0038C95C7BE00BD8CE0F13A000440BFFF0000004C00580CD87F19B6B1
(9C77FFF1B00F0789D000220)
Transmit bursts with 7 bit errors
on PDF+BCH
Message Association (MA)
MA1
[TBD]
406.05
[TBD]
3FFF1B0038D95C7BE00BD8CE0003A0004607FFF0000004C0059040FD1F52693
(9C77FFF1B00F0001D000230)
1 burst with rotating fields \#0
406.05
[TBD]
0FFF1B0038D95C7BE00BD8CE0003A0004607FFF1546004E340088F57A696090
(9C77FFF1B00F0001D000230)
1 burst with rotating fields \#1
406.05
[TBD]
3FFF1B0038D9527BE00BD8CE0003A0004607FFF220200000000ACEC7AB6DDAA
(9C77FFF1B00F0001D000230)
1 burst with rotating fields \#2
406.05
[TBD]
3FFF1B0038D9537BE00BD8CE0003A0004607FFF3000000000008C4D946E59D2
(9C77FFF1B00F0001D000230)
1 burst with rotating fields \#3
D-9
Test Code
Sequence
Simulator
Transmit
Frequency
(MHz)
Date/Time
(UTC)
Transmitted
63 Hex Transmitted Message
(23 Hex Identifier)
Number of
Bit Errors
Comments
PDF
BCH
406.05
[TBD]
3FFF1B0038D953FBE00BD8CE0003A0004604000FFFFFFFFFFFEF636F21C9D0F
(9C77FFF1B00F0001D000230)
1 burst with rotating fields \#15
Return Link (RL)
RL1
France
406.05
[TBD]
3FFF1B0038D95C7BE00BD8CE0003A0004807FFF0000004C0058477A9AD3ECE4
(9C77FFF1B00F0001D000240)
3FFF1B0038D95C7BE00BD8CE0003A0004807FFF220200000000EF99319017DD
(9C77FFF1B00F0001D000240)
Each message shall be transmitted 6 times
alternating (at 30 second intervals)
between the two beacon messages
resulting in 12 bursts in total.
406.05
[TBD]
3FFF1B0038D95C7BE00BD8CE0003A0004807FFF0000004C0058477A9AD3ECE4
(9C77FFF1B00F0001D000240)
3FFF1B0038D95C7BE00BD8CE0003A0004807FFF220300000000D92177A63257
(9C77FFF1B00F0001D000240)
RLS Acknowledgment Message.
Each message shall be transmitted 6 times
alternating (at 30 second intervals)
between the two beacon messages
resulting in 12 bursts in total.
D-10
C/S T.018 ELT(DT) Functional Validation Script
This script aims at validating specific management of ELT(DT) alerts at MEOLUT level.
The script is composed of one beacon transmitting the following sequence:
•
24 nominal bursts with 5 second repetition rate,
•
18 nominal bursts with 10 second repetition rate,
•
6 nominal bursts with 28.5 second repetition rate,
•
10 cancellation bursts with 10 second repetition rate,
•
no transmission during 2 minutes,
•
24 nominal bursts with 5 second repetition rate,
•
18 nominal bursts with 10 second repetition rate,
•
6 nominal bursts with 28.5 second repetition rate.
The transmissions shall be done at 406.05 MHz.
The Hex ID of the simulated beacon for transmissions is coded as follow:
9C57 FFF0 D00F 000D B000 001
•
9C57: fixed value for all beacon events18 (this is an example using a French country code 226)
Additional beacon message definition:
-
the encoded latitude/longitude in the main field of the message shall be constructed in the beacon
message, consistent with horizontal beacon motion at 1,200 km/h,
-
the last three nominal bursts of the first activation sequence shall contain the same encoded location,
-
the first three nominal bursts of the cancellation sequence shall contain the same encoded location,
-
the last three bursts of the cancellation sequence shall contain the default encoded location,
-
the last three bursts of the second activation sequence shall contain the default encoded location,
-
the rotating field shall be \#1 with:
o ‘Time of last encoded location’ should be all ones,
o altitude of encoded location should be 0 m,
o triggering event should be ‘1000’,
o GNSS status should be 2D,
o remaining battery capacity should be ‘11’.
18 In this document, the term “beacon event” is used to describe a beacon activation with its individual Hex ID and/or other
characteristics (e.g., frequency, bitrate, etc.), being active for a period of time (i.e., from the activation until the completion
of transmission of the last burst).
D-11
The script of this test shall implement beacon messages using the normal spreading sequence with the Test
Protocol bit 43 set to 1. For cancellation transmissions, the rotating field shall be #15 and the “method of
deactivation” field shall be set to ‘01’.
D-12
D.2.2 C/S T.018 Expected Processing
Test
Code
Sequence
Message to be Transmitted by MEOLUT
Encoded
Location
Comments
MR1
3FFF1B0038C95C7BE00BD8CE0003A000400BFFF0000004C00587A6ECF9F8EA1
43.56049,
1.48083
MEOLUT sends message with normal mode PRN to the MCC and filters out self-test
mode PRN.
MR2
3FFF1B0038C95C7BE00BD8CE0003A000404BFFF0000004C0058F3743F524F87
and
3FFF1B0038C95C7BE00BD8CE0003A000406BFFF0000004C0058B7F94734AF14
43.56049,
1.48083
MEOLUT records message and sends it to the MCC.
BV1
3FFF1B0038C95C7BE00BD8CE0003A000440BFFF0000004C00580CD87F19B6B2
43.56049,
1.48083
MEOLUT should correct 6 bit errors and transmit corrected message.
IMP1
Case 1:
no message transmitted
Case 2:
3FFF1B0038C95C7BE00BD8CE0F13A000440BFFF0000004C00580CD87F19B6B1
n/a
Two outcomes are possible for this test:
Case 1: If 2 or less matching invalid messages, MEOLUT shall filter out messages.
Case2: If 3 or more matching invalid messages, MEOLUT calculates and sends a
location solution with a confirmed invalid message to the MCC without bit
correction in PDF+BCH.
The 23 Hex ID of the alert message is “9C77FFF1B00F0789D000220”.
MA1
3FFF1B0038D95C7BE00BD8CE0003A0004607FFF0000004C0058040FD1F52693
3FFF1B0038D95C7BE00BD8CE0003A0004607FFF1546004E340088F57A696090
3FFF1B0038D95C7BE00BD8CE0003A0004607FFF220200000000ACEC7AB6DDAA
3FFF1B0038D95C7BE00BD8CE0003A0004607FFF3000000000008C4D946E59D2
3FFF1B0038D95C7BE00BD8CE0003A0004604000FFFFFFFFFFFEF636F21C9D0F
43.56049,
1.48083
MEOLUT corrects beacon messages and transmits corrected message to MCC
even if the EHE does not decrease.
The 23 Hex ID of all alert messages is “9C77FFF1B00F0001D000230”.
RL1
3FFF1B0038D95C7BE00BD8CE0003A0004807FFF0000004C0058477A9AD3ECE4
3FFF1B0038D95C7BE00BD8CE0003A0004807FFF220200000000EF99319017DD
3FFF1B0038D95C7BE00BD8CE0003A0004807FFF0000004C0058477A9AD3ECE4
3FFF1B0038D95C7BE00BD8CE0003A0004807FFF220300000000D92177A63257
43.56049,
1.48083
43.56049,
1.48083
Forward Link message: MEOLUT sends at least one valid message for each
rotating field (\#0 and \#2) to the MCC.
Acknowledgment message: MEOLUT sends at least one valid acknowledgment
message for each rotating field (\#0 and \#2) to the MCC.
The 23 hex ID of all alert messages is “9C77FFF1B00F0001D000240”.
C/S T.018 ELT(DT) Functional Validation Script
For the SGB ELT(DT) functional validation test, it should be verified that each received burst (as collected per Table E.3) results in an alert message
sent to the associated MCC (as collected per Table E.5).
D-13
D.3
C/S T.001 Performance Testing
D.3.1
General Performance Script for C/S T.001 Beacons
This annex provides a description of the beacon signals that have to be transmitted in order to generate the
statistics for performance requirements described in Annex C. The script is comprised of 25 beacon IDs
simultaneously active and each transmitting 12 bursts. The transmissions shall only use an unallocated
channel of the 406 MHz frequency bandwidth. No beacon bursts shall overlap in time, and each beacon ID
shall transmit at a fixed repetition period of 50 seconds without randomization.
The 15 Hex IDs of beacon events are coded as follows: 9C9D0000YYD0037.
•
9C9D0: fixed value for all beacon events (this is an example using a French country code),
•
YY: beacon event serial 01 to 25,
•
D00: fixed value for all beacon events,
•
37: signifies nominal transmission power of 37 dBm,
•
the transmitted frequency of each beacon event shall be ft = f0 - 5450 + (YY -1) * (2*5450)/(25-1)
Hz (rounded to Hz), with f0 being the center frequency of the beacon frequency channel used.
The first beacon (YY=01) shall transmit its first burst at time T0. The second beacon (YY=02) shall transmit
its first burst at T0+2 seconds, the third beacon (YY=03) shall transmit its first burst at To+4 seconds, and
so on, with the 25th beacon (YY=25) transmitting its first burst at T0+48 seconds. The first beacon (YY=01)
shall transmit its second burst at T0+50 seconds, and the script shall continue as such until the 25th beacon
(YY=25) transmits its 12th burst at T0+598 seconds. Hence, one execution of this script shall produce a total
of 300 bursts.
The appropriate country code is to be coded within the 15 Hex ID to indicate which beacon simulator is
transmitting the burst.
The script of this test shall implement beacon messages using the inverted frame synchroniser pattern.
D.3.2
Performance Evaluation Script for C/S T.001 ELT(DT)s
The script is comprised of 25 beacon IDs, each transmitting 63 bursts, with a fixed repetition rate of
28.5 seconds and beacon event separated by 1 s. The transmissions shall not use an operational channel of
the 406 MHz bandwidth, but the transmission frequency shall be spread so that it covers a range of 10.9
kHz with a resolution of 412.5 Hz.
The script shall be repeated for a duration of at least 4 hours to allow various geometric configurations and
tracking plan.
The 15 Hex IDs of beacon events are coded as follows: 1C538 0ZZYY 3FDFF,
•
1C538: fixed value for all beacon events (this is an example using a French country code 226),
D-14
•
YY: beacon event serial 01 to 25,
•
D: fixed value for all beacon events,
•
ZZ: frequency shift factor between 0 and 27 (the transmitted frequency shall be ft = f0 +ZZ x 412.5
Hz, with f0 = 406.058600 MHz the nominal frequency). A correspondence between ZZ and YY is
given in the table below,
•
FF: 37, signifies nominal transmission power of 37 dBm.
The appropriate country code is to be coded within the 15 Hex ID to indicate which beacon simulator is
transmitting the burst.
The script of this test shall implement beacon messages using the inverted frame synchronization pattern
(self-test mode).
The following table gives additional guidance about the test script to be used:
15 Hex ID of Beacon
Time of Transmission
T0 + XX s
Transmission Power
(dBm)
Frequency ZZ
1C538 00001 3FDFF
1C538 01402 3FDFF
1C538 00703 3FDFF
1C538 02204 3FDFF
1C538 00105 3FDFF
1C538 01506 3FDFF
1C538 00807 3FDFF
1C538 02308 3FDFF
1C538 00209 3FDFF
1C538 01610 3FDFF
1C538 00911 3FDFF
1C538 02412 3FDFF
1C538 00313 3FDFF
1C538 01714 3FDFF
1C538 01015 3FDFF
1C538 02516 3FDFF
1C538 00417 3FDFF
1C538 01818 3FDFF
1C538 01119 3FDFF
1C538 02620 3FDFF
1C538 00521 3FDFF
1C538 01922 3FDFF
1C538 01223 3FDFF
1C538 02724 3FDFF
1C538 00625 3FDFF
1C538 00001 3FDFF
28.5
1C538 01402 3FDFF
29.5
…
…
…
…
D-15
D.4
C/S T.018 Performance Testing
D.4.1 General Performance Script for C/S T.018 Beacons
Performance scripts described in this section shall be transmitted in self-test mode to avoid any disruption
of the operational System (except the Partially Overlapping Bursts Script, for which transmission using the
normal mode is required).
D.4.1.1
Partially Overlapping Bursts Script
This is a script for four overlapping bursts to evaluate the associated detection performance.
This annex provides a description of the beacon signals that have to be transmitted in order to generate the
statistics for performance requirements described in Annex C. The script is comprised of 4 beacon IDs,
each transmitting 25 bursts with a repetition period of 30 seconds.
The 23 Hex IDs of beacon events are coded as follows: ADF7 FFF0 XXXF DNNF PP00 000
•
ADF7: fixed value for all beacon events (this is an example using a USA country code)
•
XXX: beacon event ID 1 to 4
•
NN = total number of bursts (fixed value) to be transmitted for each beacon ID during each
execution of the script (25),
•
PP = the same transmit power to be used for each beacon ID, and using the same power level as for
the other performance test scripts,
The appropriate country code is to be coded within the 23 Hex ID to indicate which beacon simulator is
transmitting the burst.
The script of this test shall implement beacon messages using the Test Protocol bit set to “1”.
23 Hex ID of Beacon
Time of Transmission
T0 + XX s
Frequency
FF (Hz)
ADF7 FFF0 001F D25F PP00 000
0.0
ADF7 FFF0 002F D25F PP00 000
0.25
ADF7 FFF0 003F D25F PP00 000
0.50
ADF7 FFF0 004F D25F PP00 000
0.75
…
ADF7 FFF0 001F D25F PP00 000
30.0
ADF7 FFF0 002F D25F PP00 000
30.25
ADF7 FFF0 003F D25F PP00 000
30.50
ADF7 FFF0 004F D25F PP00 000
30.75
…
ADF7 FFF0 001F D25F PP00 000
60.0
ADF7 FFF0 002F D25F PP00 000
60.25
ADF7 FFF0 003F D25F PP00 000
60.50
ADF7 FFF0 004F D25F PP00 000
60.75
…
ADF7 FFF0 001F D25F PP00 000
90.0
ADF7 FFF0 002F D25F PP00 000
90.25
D-16
ADF7 FFF0 003F D25F PP00 000
90.50
ADF7 FFF0 004F D25F PP00 000
90.75
…
D.4.1.2
30-Second Script
This is a script for the first 30 seconds of beacon activation, to evaluate the detection and location
performance for single burst and at 30 seconds from beacon activation.
This annex provides a description of the beacon signals that have to be transmitted in order to generate the
statistics for performance requirements described in Annex C. The script is comprised of 4 beacon IDs,
each transmitting 6 bursts with a repetition period of 5 seconds. The beacon IDs will increment from 1 to
100 in sets of 4 and then restart.
The 23 Hex IDs of beacon events are coded as follows: ADF7 FFF0 XXXF DNNF PP00 000
•
ADF7: fixed value for all beacon events (this is an example using a USA country code),
•
FFF0: TAC 65532 for beacon simulator, followed by the first 2 bits of the serial number set to 00,
•
XXX: beacon event ID 1 to 4, 5 to 8, …, 81 to 84, …, 97 to 100, 1 to 4, ….,
•
NN = total number of bursts (fixed value) to be transmitted for each beacon ID during each
execution of the script (6),
•
PP = transmitted power.
Additional beacon burst parameters (see table below):
•
FF: transmitted frequency that shall be ft = f0 - 1650 + (XXX -1) * (2*1650)/(100-1) Hz, with f0 =
406.05 MHz (rounded to Hz),
•
CRA: Chip Rate Accuracy, shall be so that CRA = 0.6\*sin(pi/2\*(XXX-1)) chips/s,
•
CRV: Chip Rate Variation, shall be so that CRV = 0.6\*sin(pi/2\*INT((XXX-1)/4)) chips/s².
The appropriate country code is to be coded within the 23 Hex ID to indicate which beacon simulator is
transmitting the burst.
The script of this test shall implement beacon messages using the Test Protocol bit set to “1”.
23 Hex ID of Beacon
Time of
Transmission
T0 + XX s
Transmission
Power (dBm)
Frequency
FF (Hz)
Chip rate
accuracy
CRA
(chips/s)
Chip rate
variation
CRV
(chips/s²)
ADF7 FFF0 001F D06F PP00 000
0.0
PP
ADF7 FFF0 002F D06F PP00 000
1.1
PP
0.6
ADF7 FFF0 003F D06F PP00 000
2.2
PP
ADF7 FFF0 004F D06F PP00 000
3.3
PP
-0.6
ADF7 FFF0 001F D06F PP00 000
5.0
PP
ADF7 FFF0 002F D06F PP00 000
6.1
PP
0.6
ADF7 FFF0 003F D06F PP00 000
7.2
PP
ADF7 FFF0 004F D06F PP00 000
8.3
PP
-0.6
D-17
23 Hex ID of Beacon
Time of
Transmission
T0 + XX s
Transmission
Power (dBm)
Frequency
FF (Hz)
Chip rate
accuracy
CRA
(chips/s)
Chip rate
variation
CRV
(chips/s²)
…
…
…
…
…
…
ADF7 FFF0 001F D06F PP00 000
25.0
PP
ADF7 FFF0 002F D06F PP00 000
26.1
PP
0.6
ADF7 FFF0 003F D06F PP00 000
27.2
PP
ADF7 FFF0 004F D06F PP00 000
28.3
PP
-0.6
ADF7 FFF0 005F D06F PP00 000
30.0
PP
0.6
ADF7 FFF0 006F D06F PP00 000
31.1
PP
0.6
0.6
ADF7 FFF0 007F D06F PP00 000
32.2
PP
0.6
ADF7 FFF0 008F D06F PP00 000
33.3
PP
-0.6
0.6
…
…
…
…
…
…
ADF7 FFF0 097F D06F PP00 000
745.0
PP
0.6
ADF7 FFF0 098F D06F PP00 000
746.1
PP
0.6
0.6
ADF7 FFF0 099F D06F PP00 000
747.2
PP
0.6
ADF7 FFF0 100F D06F PP00 000
748.3
PP
-0.6
0.6
ADF7 FFF0 001F D06F PP00 000
750.0
PP
ADF7 FFF0 002F D06F PP00 000
751.1
PP
0.6
ADF7 FFF0 003F D06F PP00 000
752.2
PP
ADF7 FFF0 004F D06F PP00 000
753.3
PP
-0.6
…
…
…
…
…
…
D.4.1.3
5-Minute Script
This is a script for the first 5 minutes of beacon activation, to evaluate the location performance for single
burst and at 5 minutes.
This annex provides a description of the beacon signals that have to be transmitted in order to generate the
statistics for performance requirements described in Annex C. The script is comprised of 4 beacon IDs each
transmitting 6 bursts with a repetition period of 5 seconds followed by 9 bursts with a repetition period of
30 seconds. The beacon IDs will increment from 1 to 16 in sets of 4 and then restart.
The 23 Hex IDs of beacon events are coded as follows: ADF7 FFF0 XXXF DNNF PP00 000
•
ADF7: fixed value for all beacon events (this is an example using a USA country code),
•
FFF0: TAC 65532 for beacon simulator, followed by the first 2 bits of the serial number set to 00,
•
XXX : beacon event ID, 1 to 4, 5 to 8, 9 to 12, 13 to 16, 1 to 4, …,
•
NN = total number of bursts (fixed value) to be transmitted for each beacon ID during each
execution of the script (15),
•
PP = transmitted power,
Additional beacon burst parameters (see table below):
•
FF: transmitted frequency that shall be ft = f0 - 1650 + (XXXX -1) * (2*1650)/(16-1) Hz, with f0 =
406.05 MHz (rounded to Hz),
•
CRA: Chip Rate Accuracy, shall be so that CRA = 0.6\*sin(pi/2\*(XXXX-1)) chips/s,
D-18
•
CRV: Chip Rate Variation, shall be so that CRV = 0.6\*sin(pi/2\*INT((XXXX-1)/4)) chips/s².
The appropriate country code is to be coded within the 23 Hex ID to indicate which beacon simulator is
transmitting the burst.
The script of this test shall implement beacon messages using the Test Protocol bit set to “1”.
23 Hex ID of Beacon
Time of
Transmission
T0 + XX s
Transmission
Power (dBm)
Frequency
FF (Hz)
Chip rate
accuracy
CRA
(chips/s)
Chip rate
variation
CRV
(chips/s²)
ADF7 FFF0 001F D15F PP00 000
0.0
PP
ADF7 FFF0 002F D15F PP00 000
1.1
PP
0.6
ADF7 FFF0 003F D15F PP00 000
2.2
PP
ADF7 FFF0 004F D15F PP00 000
3.3
PP
-0.6
ADF7 FFF0 001F D15F PP00 000
5.0
PP
ADF7 FFF0 002F D15F PP00 000
6.1
PP
0.6
ADF7 FFF0 003F D15F PP00 000
7.2
PP
ADF7 FFF0 004F D15F PP00 000
8.3
PP
-0.6
…
…
…
…
…
…
ADF7 FFF0 001F D15F PP00 000
25.0
PP
ADF7 FFF0 002F D15F PP00 000
26.1
PP
0.6
ADF7 FFF0 003F D15F PP00 000
27.2
PP
ADF7 FFF0 004F D15F PP00 000
28.3
PP
-0.6
ADF7 FFF0 001F D15F PP00 000
55.0
PP
ADF7 FFF0 002F D15F PP00 000
56.1
PP
0.6
ADF7 FFF0 003F D15F PP00 000
57.2
PP
ADF7 FFF0 004F D15F PP00 000
58.3
PP
-0.6
ADF7 FFF0 001F D15F PP00 000
85.0
PP
ADF7 FFF0 002F D15F PP00 000
86.1
PP
0.6
ADF7 FFF0 003F D15F PP00 000
87.2
PP
ADF7 FFF0 004F D15F PP00 000
88.3
PP
-0.6
…
…
…
…
…
…
ADF7 FFF0 001F D15F PP00 000
295.0
PP
ADF7 FFF0 002F D15F PP00 000
296.1
PP
0.6
ADF7 FFF0 003F D15F PP00 000
297.2
PP
ADF7 FFF0 004F D15F PP00 000
298.3
PP
-0.6
ADF7 FFF0 005F D15F PP00 000
300.0
PP
0.6
ADF7 FFF0 006F D15F PP00 000
301.1
PP
0.6
0.6
ADF7 FFF0 007F D15F PP00 000
302.2
PP
0.6
ADF7 FFF0 008F D15F PP00 000
303.3
PP
-0.6
0.6
…
…
…
…
…
…
ADF7 FFF0 013F D15F PP00 000
1195.0
PP
-0.6
ADF7 FFF0 014F D15F PP00 000
1196.1
PP
0.6
-0.6
ADF7 FFF0 015F D15F PP00 000
1197.2
PP
-0.6
ADF7 FFF0 016F D15F PP00 000
1198.3
PP
-0.6
-0.6
ADF7 FFF0 001F D15F PP00 000
1200.0
PP
ADF7 FFF0 002F D15F PP00 000
1201.1
PP
0.6
ADF7 FFF0 003F D15F PP00 000
1202.2
PP
ADF7 FFF0 004F D15F PP00 000
1203.3
PP
-0.6
…
…
…
…
…
…
D-19
D.4.1.4
30-Minute Script
This is a script for the first 30 minutes of beacon activation, to evaluate the location performance for single
burst and at 30 minutes.
This annex provides a description of the beacon signals that have to be transmitted in order to generate the
statistics for performance requirements described in Annex C. The script is comprised of 4 beacon IDs,
each transmitting 6 bursts with a repetition period of 5 seconds followed by 59 bursts with a repetition
period of 30 seconds. The beacon IDs will increment from 1 to 8 in sets of 4 and then restart to insure proper
processing.
The 23 Hex IDs of beacon events are coded as follows: ADF7 FFF0 XXXF DNNF PP00 000
•
ADF7: fixed value for all beacon events (this is an example using a USA country code),
•
FFF0: TAC 65532 for beacon simulator, followed by the first 2 bits of the serial number set to 00,
•
XXX: beacon event serial 1 to 4, 5 to 8, 1 to 4, …,
•
NN = total number of bursts (fixed value) to be transmitted for each beacon ID during each
execution of the script (65),
•
PP = transmitted power,
Additional beacon burst parameters (see table below):
•
FF: transmitted frequency that shall be ft = f0 - 1650 + (XXXX -1) * (2*1650)/(8-1) Hz, with f0 =
406.05 MHz (rounded to Hz),
•
CRA: Chip Rate Accuracy, shall be so that CRA = 0.6\*sin(pi/2\*(XXXX-1)) chips/s,
•
CRV: Chip Rate Variation, shall be so that CRV = 0.6\*sin(pi/2\*INT((XXXX-1)/4)) chips/s².
The appropriate country code is to be coded within the 23 Hex ID to indicate which beacon simulator is
transmitting the burst.
The script of this test shall implement beacon messages using the Test Protocol bit set to “1”.
23 Hex ID of Beacon
Time of
Transmission
T0 + XX s
Transmission
Power (dBm)
Frequency
FF (Hz)
Chip rate
accuracy
CRA
(chips/s)
Chip rate
variation
CRV
(chips/s²)
ADF7 FFF0 001F D65F PP00 000
0.0
PP
ADF7 FFF0 002F D65F PP00 000
1.1
PP
0.6
ADF7 FFF0 003F D65F PP00 000
2.2
PP
ADF7 FFF0 004F D65F PP00 000
3.3
PP
-0.6
ADF7 FFF0 001F D65F PP00 000
5.0
PP
ADF7 FFF0 002F D65F PP00 000
6.1
PP
0.6
ADF7 FFF0 003F D65F PP00 000
7.2
PP
ADF7 FFF0 004F D65F PP00 000
8.3
PP
-0.6
…
…
…
…
…
…
ADF7 FFF0 001F D65F PP00 000
25.0
PP
ADF7 FFF0 002F D65F PP00 000
26.1
PP
0.6
ADF7 FFF0 003F D65F PP00 000
27.2
PP
D-20
23 Hex ID of Beacon
Time of
Transmission
T0 + XX s
Transmission
Power (dBm)
Frequency
FF (Hz)
Chip rate
accuracy
CRA
(chips/s)
Chip rate
variation
CRV
(chips/s²)
ADF7 FFF0 004F D65F PP00 000
28.3
PP
-0.6
ADF7 FFF0 001F D65F PP00 000
55.0
PP
ADF7 FFF0 002F D65F PP00 000
56.1
PP
0.6
ADF7 FFF0 003F D65F PP00 000
57.2
PP
ADF7 FFF0 004F D65F PP00 000
58.3
PP
-0.6
ADF7 FFF0 001F D65F PP00 000
85.0
PP
ADF7 FFF0 002F D65F PP00 000
86.1
PP
0.6
ADF7 FFF0 003F D65F PP00 000
87.2
PP
ADF7 FFF0 004F D65F PP00 000
88.3
PP
-0.6
…
…
…
…
…
…
ADF7 FFF0 001F D65F PP00 000
1795.0
PP
ADF7 FFF0 002F D65F PP00 000
1796.1
PP
0.6
ADF7 FFF0 003F D65F PP00 000
1797.2
PP
ADF7 FFF0 004F D65F PP00 000
1798.3
PP
-0.6
ADF7 FFF0 005F D65F PP00 000
1800.0
PP
0.6
ADF7 FFF0 006F D65F PP00 000
1801.1
PP
0.6
0.6
ADF7 FFF0 007F D65F PP00 000
1802.2
PP
0.6
ADF7 FFF0 008F D65F PP00 000
1803.3
PP
-0.6
0.6
…
…
…
…
…
…
ADF7 FFF0 005F D65F PP00 000
3595.0
PP
0.6
ADF7 FFF0 006F D65F PP00 000
3596.1
PP
0.6
0.6
ADF7 FFF0 007F D65F PP00 000
3597.2
PP
0.6
ADF7 FFF0 008F D65F PP00 000
3598.3
PP
-0.6
0.6
ADF7 FFF0 001F D65F PP00 000
3600.0
PP
ADF7 FFF0 002F D65F PP00 000
3601.1
PP
0.6
ADF7 FFF0 003F D65F PP00 000
3602.2
PP
ADF7 FFF0 004F D65F PP00 000
3603.3
PP
-0.6
…
…
…
…
…
…
D.4.1.5
After 30-Minute Script
This is a script for transmission as after the 30 first minutes of beacon activation, to evaluate the location
performance for single burst and after 30 minutes.
This annex provides a description of the beacon signals that have to be transmitted in order to generate the
statistics for performance requirements described in Annex C. The script is comprised of 15 beacon IDs,
each transmitting 15 bursts with a repetition period of 120 seconds. The beacon IDs will increment from 1
to 30 in sets of 15 and then restart.
The 23 Hex IDs of beacon events are coded as follows: ADF7 FFF0 XXXF DNNF PP00 000
•
ADF7: fixed value for all beacon events (this is an example using a USA country code),
•
FFF0: TAC 65532 for beacon simulator, followed by the first 2 bits of the serial number set to 00,
•
XXX: beacon event serial 1 to 15, 16 to 30, 1 to 15, …,
D-21
•
NN = total number of bursts (fixed value) to be transmitted for each beacon ID during each
execution of the script (15),
•
PP = transmitted power,
Additional beacon burst parameters (see table below):
•
FF: transmitted frequency that shall be ft = f0 - 1650 + (XXXX -1) * (2*1650)/(30-1) Hz, with f0 =
406.05 MHz (rounded to Hz),
•
CRA: Chip Rate Accuracy, shall be so that CRA = 0.6\*sin(pi/2\*(XXXX-1)) chips/s,
•
CRV: Chip Rate Variation, shall be so that CRV = 0.6\*sin(pi/2\*INT((XXXX-1)/4)) chips/s².
The appropriate country code is to be coded within the 23 Hex ID to indicate which beacon simulator is
transmitting the burst.
The script of this test shall implement beacon messages using the Test Protocol bit set to “1”.
23 Hex ID of Beacon
Time of
Transmission
T0 + XX s
Transmission
Power (dBm)
Frequency
FF (Hz)
Chip rate
accuracy
CRA
(chips/s)
Chip rate
variation
CRV
(chips/s²)
ADF7 FFF0 001F D15F PP00 000
PP
ADF7 FFF0 002F D15F PP00 000
PP
0.6
ADF7 FFF0 003F D15F PP00 000
PP
…
…
…
…
…
…
ADF7 FFF0 015F D15F PP00 000
PP
-0.6
ADF7 FFF0 001F D15F PP00 000
PP
…
…
…
…
…
…
ADF7 FFF0 015F D15F PP00 000
PP
…
…
…
…
…
…
ADF7 FFF0 015F D15F PP00 000
PP
-0.6
ADF7 FFF0 016F D15F PP00 000
PP
-0.6
-0.6
…
…
…
…
…
…
ADF7 FFF0 030F D15F PP00 000
PP
-0.6
…
…
…
…
…
…
ADF7 FFF0 030F D15F PP00 000
PP
-0.6
ADF7 FFF0 001F D15F PP00 000
PP
…
…
…
…
…
…
D-22
D.4.2 Performance Evaluation Script for C/S T.018 ELT(DT)s
Performance script described in this section shall be transmitted in self-test mode to avoid any disruption
of the operational system.
The script is comprised of 25 beacon IDs, each transmitting 63 bursts, with a fixed repetition rate of
28.5 seconds and beacon events are separated by 1 second. The transmission frequency shall be spread
around 406.05 MHz so that it covers a range of 3.3 kHz with a resolution of 412.5 Hz.
The script shall be repeated for a duration of at least 4 hours to allow various geometric configurations and
tracking plan.
The 23 Hex IDs of beacons events are coded as follows: 9C54 FFF0 0YYF DNNF PP00 0ZZ
•
9C54: fixed value for all beacon events (this is an example using a French country code 226),
•
FFF0: TAC 65532 for beacon simulator, followed by the first 2 bits of the serial number set to 00,
•
YY : beacon event serial 01 to 25,
•
D: fixed value for all beacon events,
•
NN: total number of transmitted burst (fixed value) to be transmitted for each beacon ID during
each execution of the script (63),
•
PP: transmitted power,
•
ZZ: frequency shift factor, between 0 and 8 (the transmitted frequency shall be ft = f0 - 1650 + ZZ
x 412.5 Hz, with f0 = 406.05 MHz). A correspondence between ZZ and YY is given in the table
below.
The appropriate country code is to be coded within the 23 Hex ID to indicate which beacon simulator is
transmitting the burst.
The script of this test shall implement beacon messages encoded with the Test Protocol bit 43 set to 1.
The following table give additional guidance about the test script to be used:
23 Hex ID
Time of Transmission
T0 + XX s
Transmission Power
(dBm)
Frequency ZZ
9C54 FFF0 001F D63F PP00 001
PP
9C54 FFF0 002F D63F PP00 008
9C54 FFF0 003F D63F PP00 001
9C54 FFF0 004F D63F PP00 007
9C54 FFF0 005F D63F PP00 002
9C54 FFF0 006F D63F PP00 006
9C54 FFF0 007F D63F PP00 003
9C54 FFF0 008F D63F PP00 005
9C54 FFF0 009F D63F PP00 000
9C54 FFF0 010F D63F PP00 008
9C54 FFF0 011F D63F PP00 001
9C54 FFF0 012F D63F PP00 007
D-23
9C54 FFF0 013F D63F PP00 002
9C54 FFF0 014F D63F PP00 006
9C54 FFF0 015F D63F PP00 003
9C54 FFF0 016F D63F PP00 005
9C54 FFF0 017F D63F PP00 000
9C54 FFF0 018F D63F PP00 008
9C54 FFF0 019F D63F PP00 001
9C54 FFF0 020F D63F PP00 007
9C54 FFF0 021F D63F PP00 002
9C54 FFF0 022F D63F PP00 006
9C54 FFF0 023F D63F PP00 003
9C54 FFF0 024F D63F PP00 005
9C54 FFF0 025F D63F PP00 004
9C54 FFF0 001F D63F PP00 000
28.5
9C54 FFF0 002F D63F PP00 008
29.5
…
…
…
…
- END OF ANNEX D -
E-1
ANNEX E
DATA FORMAT
E.1
General
This annex describes the data format to be provided in electronic files using ASCII format to the
Cospas-Sarsat Secretariat when commissioning a MEOLUT. The data is to be provided in a comma
separated value (csv) format, and each field shall include an entry. If there is no data for any given
field, then the field can be empty. All solution data used in the commissioning testing shall be provided.
Data file shall use the suffix “\_Ex.csv” (e.g., 2019-01-01\_E2.csv for a MEOLUT satellite tracking
file).
A description of the fields is provided below:
Field
Relative position of the data
Description
Description of the information provided
Detailed Format
Guidance on how the data should be provided
Type
C - Character, N - Numeric and L - Logical
Width
The total number of characters for the field
Dec
The total number of digits after the decimal point
MF\#
Message Field as described in document C/S A.002 (SID)
Comments
Table E.1: Description of the Fields
E.2
MEOLUT Satellite Tracking
The satellites tracked by the MEOLUT during the commissioning test period shall be documented
using the following format.
Field
Description
Detailed Format
Type
Width
Dec
MF\#
Comments
LUT ID
N
Antenna ID
N
Note 1
Satellite ID
N
AOS\_Time
(Acquisition of Signal)
(UTC)
yyyy-mm-dd hh:mm:ss.xxx
C
LOS\_Time
(Loss of Signal)
(UTC)
yyyy-mm-dd hh:mm:ss.xxx
C
Table E.2:MEOLUT Satellite Tracking
E-2
Note:
1 The antenna may be either:
a. a traditional parabolic antenna that tracks a single satellite, or
b. an antenna that may track multiple satellites simultaneously (e.g., a phased array).
In either case, an antenna ID shall be provided.
E.3
Beacon Message Data
All beacon valid messages produced by the LUT for C/S T.001 and C/S T.018 beacons during the
commissioning test period will be documented using the following format.
Field
Description
Detailed Format
Type Width
Dec
MF\#
Comments
Packet/record number
(as collected)
N
Raw/Full message (36 Hex)
for C/S T.001 beacon, or
raw/full message (63 Hex)
for C/S T.018 beacon
h...h
C
36, or
77 for C/S T.001
beacons
Note 1
Beacon ID
15 Hex for C/S T.001 beacon, or
23 Hex for C/S T.018 beacon
h..h
C
15, or
22 for C/S T.001
beacons, or
92 for C/S T.018
beacons
Time of packet received (UTC)
yyyy-mm-dd hh:mm:ss.xxx
C
Note 2
FOA (Hz)
nnnnnnnnn.nnn
N
Note 3
Frequency Offset (Hz)
snnnnn.nnn
N
Note 3
TOA (UTC)
yyyy-mm-dd hh:mm:ss.xxxxxxxxx
C
Note 3
Time Offset (s)
n.nnnnnnnnn
N
Note 3
C/N0 (dB.Hz)
nn.n
N
Bit rate (bps)
nnn.nnn
N
LUT ID - Antenna ID
nnnnnn
N
2-71
Note 4
Spacecraft ID
nnn
N
Satellite
position
(km)
X
snnnnn.nnnn
N
Note 5
Y
snnnnn.nnnn
N
Z
snnnnn.nnnn
N
Satellite
velocity
(km/s)
X
snnn.nnnnnn
N
Note 6
Y
snnn.nnnnnn
N
Z
snnn.nnnnnn
N
BCH-1/BCH errors
n
Note 7
BCH-2 errors
n
Note 8
Table E.3: Beacon Message Data
E-3
Notes:
1 For C/S T.018 beacons, field 2 is composed of the 250-bit C/S T.018 raw/full message, which
shall be left padded (to form a 63 Hex character) with the following two bits:
•
bit 1: self-test indicator based on PRN sequence detected by the MEOLUT (0 = normal
mode, 1 = self-test mode), followed by
•
bit 2: 0.
2 The time of packet received (UTC) is the logged time at which the packet is received at
MEOLUT.
3 The values of TOA, FOA, TOA offset and FOA offset shall be provided after MEOLUT-
internal calibration, if any.
4 The LUT ID followed by the antenna ID to form a 6-digit field. The antenna may be a
traditional parabolic antenna that tracks a single satellite or an antenna that may track multiple
satellites simultaneously (e.g., a phased array). In either case, an antenna ID shall be included.
5 Associated satellite position data and associated reference frame (preferably Earth-Centered
Earth-Fixed frame) may be provided or optionally disclosed.
6 Associated satellite velocity data and associated reference frame (preferably Earth-Centered
Earth-Fixed frame) may be provided or optionally disclosed.
7 For C/S T.001 beacons, this field gives the number of corrected errors by BCH-1. The number
of errors is comprised between 0 and 3. For C/S T.018 beacons, this field gives the number of
corrected errors by the BCH error correcting code. The number of errors is comprised between
0 and 6.
8 For C/S T.001 beacons, this field gives the number of corrected errors by BCH-2. The number
of errors is comprised between 0 and 2. If not applicable (because of a short message or a
protocol that do not use BCH-2), this field shall be left empty. For C/S T.018 beacons, this
field shall be left empty.
E.4
LUT Database for Solution Data
All the location solutions produced by the LUT for the beacon IDs reported in the commissioning
report during the commissioning test period shall be documented according to the format defined.
Field
Description
Detailed Format
Type Width
Dec
MF\#
Comments
Solution ID
N
Note 1
LUTID
nnnn
N
Time stamp of 1st burst used for
location (UTC)
yyyy-mm-dd
hh:mm:ss.xxx
C
14a
Time stamp of last burst used for
location (UTC)
yyyy-mm-dd
hh:mm:ss.xxx
C
14b
Time of location computation or time
solution sent (UTC)
yyyy-mm-dd
hh:mm:ss.xxx
C
Beacon ID
15 Hex for C/S T.001 beacon, or
23 Hex for C/S T.018 beacon
h..h
C
15, or
22, or 92
E-4
Field
Description
Detailed Format
Type Width
Dec
MF\#
Comments
Estimated Transmission Frequency
406.nnnnnnnn
N
Note 2
Full message
36 Hex for C/S T.001 beacon, or
63 Hex for C/S T.018 beacon
h...h
C
36, or
77, or [90]
[note for MF\#90]
Number of bursts used
nn
N
Note 3
Data used T/F/D
a
C
Note 4
LUT ID - Antenna IDs
nnnnnn ... nnnnnn
N
2-71
Note 5
Number of packets used to derive the
solution
nnn
N
Note 6
Number of satellites used to derive the
solution
nnn
N
Derived
from MF\#83
Satellite IDs
nnn ... nnn
N
Note 7
JDOP
nn.nn
N
Expected horizontal error
nnn.nn
N
Location methodology
a - a
C
Note 8
Latitude(degree)
snn.nnnnn
M
Note 9
Longitude (degree)
snnn.nnnnn
N
Note 10
Altitude (km)
nn.nnnnnn
N
Location error (km)
nnnn.nnn
N
Note 11
Course (degrees)
nnn
N
Note 12
Horizontal speed magnitude (m/s)
nnn.n
N
Vertical speed magnitude (m/s)
snnn.n
N
TOA residual standard deviation (s)
n.nnnnnnnnn
N
Note 13
FOA residual standard deviation (Hz)
nn.nnn
N
Comment
C
Table E.4: MEOLUT Solution Data
Notes:
1 This number has not to be generated by the LUT.
2 This value is an estimation of the beacon transmission frequency calculated as part of the
location process.
3 Number of bursts used in location computation.
4 T – TDOA only, F – FDOA only, D – TDOA/FDOA.
5 A list of LUT ID - Antenna ID (field 11 of Table E.3) separated by spaces.
6 A packet is a burst received from a specific satellite/antenna combination (channel) with an
associated TOA/FOA. A single transmitted burst can result in many packets received at a
MEOLUT dependent on the number of available satellite data channels.
7 A list of satellite IDs separated by spaces. The satellites shall be listed in the same sequence as
the LUT ID - Antenna ID specified in field 11.
8 Location methodology in the format “overall method – multi-burst method” where:
E-5
•
“overall method” describes the type of location algorithm used.
For example:
o P2Dd: position only in 2D with default altitude value,
o P2Dm: position only in 2D with altitude data obtained from a Digital Elevation Model,
o P3D: position only with altitude estimation,
o P2D/V3D: position in 2D and velocity in 3D,
o P3D/V3D: position in 3D and velocity in 3D,
•
“multi-burst method” describes the type of multi-burst accumulation used.
For example:
o Global: use all TOA/FOA data available from multiple bursts to calculate a single
location,
o Average: an average of successive single-burst locations.
9 Latitude to be provided in decimal and ± format (i.e., without North or South indication).
10 Longitude to be provided in decimal and ± format (i.e., without East or West indication).
11 Can be empty.
12 Velocity estimation, when available, shall be with respect to the estimate location and may be
provided or optionally disclosed. If not provided, leave it empty.
13 Can be set to 0 or to a default value if the number of measurements is equal to the number of
unknowns, and may be provided or optionally disclosed. If not provided, leave it empty.
E.5
MCC Message Log Table
All the location and detection solutions produced by the LUT and intended to be sent to the MCC
during the commissioning test period shall be documented according to the same format provided in
section E.4. If no location is available, the location fields (e.g., latitude, longitude, DOP etc.) would be
empty.
SIT messages listed in Table 3.1 of document C/S T.019 shall be collected and provided as part of the
data package.
Table E.5
E.6
Beacon Database Description
Field
Description
Detailed Format
Type
Width
Dec
Comments
Beacon Number
nn
N
Location
C
Beacon ID
15 Hex for C/S T.001 beacon,
or
23 Hex for C/S T.018 beacon
h..h
C
15, or
Beacon latitude
snn.nnnnn
N
Beacon longitude
snnn.nnnnn
N
Beacon altitude (km)
snn.nnn
N
Type of Beacon
C
E-6
Field
Description
Detailed Format
Type
Width
Dec
Comments
Country Code
C
Activation Time
yyyy-mm-dd
hh:mm:ss.xxx
N
Deactivation Time
yyyy-mm-dd
hh:mm:ss.xxx
N
Actual Time “On”
yyyy-mm-dd
hh:mm:ss.xxx
N
Actual Time “Off”
yyyy-mm-dd
hh:mm:ss.xxx
N
Comments
C
Table E.6: Beacon Database Description
E.7
Beacon Test Script Log
All the beacon test scripts used during the LUT commissioning test period shall be documented using
the format in Table E.7. For tests involving moving beacons, the reference trajectory shall be provided
as per requirements of section 5.1.1.
Field
Description
Detailed Format
Type
Width
Dec
Comments
Transmission Time
(UTC)
yyyy-mm-dd
hh:mm:ss.xxxxxxxxx
N
Beacon ID
15 Hex for C/S T.001 beacon, or
23 Hex for C/S T.018 beacon
h.h
C
15, or
Full message
36 Hex for C/S T.001 beacon, or
63 Hex for C/S T.018 beacon
h…h
C
36, or
Note 1
Transmitted power (dBm)
nn
N
Transmitted frequency (MHz)
nnn.nnnnnn
N
Beacon latitude (deg)
snn.nnnnn
N
Beacon longitude (deg)
snnn.nnnnn
N
Beacon altitude (m)
nnnn
N
Course (degrees)
nnn
N
Note 2
Horizontal speed magnitude (m/s)
nnn.n
N
Vertical speed magnitude (m/s)
snnn.n
N
Chip rate accuracy (chips/s)
sn.n
N
Note 3
Chip rate variation (chips/s²)
sn.n
N
Comments
C
Table E.7: Beacon Test Script Log
E-7
Notes:
1 For C/S T.018 beacons, field 3 is composed of the 250-bit C/S T.018 raw/full message, which
shall be left padded (to form a 63 Hex character) with the following two bits:
•
bit 1: self-test indicator based on PRN sequence transmitted in the beacon script (0 =
normal mode, 1 = self-test mode), followed by
•
bit 2: 0.
2 These fields can be left empty if the beacon velocity is not known.
3 Only for SGB bursts. If the information is not available in the beacon simulator log, the beacon
simulator script can be provided instead.
- END OF ANNEX E -
F-1
ANNEX F
MEOLUT COMMISSIONING - PRINCIPLES AND POLICIES
F.1
References
The Cospas-Sarsat Council approved the general principles of its commissioning policy for
MEOLUTs, provided hereunder in sections F.2, F.3 and F.4.
F.2
General
The following principles govern the commissioning of Cospas-Sarsat Ground Segment equipment:
F.2.1
A State which has notified its association with the Cospas-Sarsat Programme as a Ground
Segment Provider assumes the responsibility "to adhere to the technical specifications and
operating procedures set by the Council for the purpose of ensuring adequate System
performance" and "to provide, as agreed with the Council, appropriate performance data in
order to confirm compatibility of its Ground Segment equipment with the System"
(section 3.1 of the Letter of Notification).
F.2.2
Cospas-Sarsat performance specification and design guidelines for MEOLUTs and MCCs are
defined in documents C/S T.019 and C/S A.005, respectively.
F.2.3
Cospas-Sarsat criteria and test methods for verifying that MEOLUTs and MCCs meet these
standards are defined in documents C/S T.020 and C/S A.006, respectively.
F.2.4
The responsible Agency or Administration installing and planning to operate a new
MEOLUT or MCC shall plan and conduct appropriate tests, in accordance with the applicable
Cospas-Sarsat standards, which may form part of its own acceptance testing.
F.2.5
A commissioning report, including the results of the commissioning tests defined by Cospas-
Sarsat, shall be submitted to the Cospas-Sarsat Secretariat, for review by the Joint Committee.
The commissioning report must be submitted six weeks prior to the Joint Committee meeting.
Reports submitted less than six weeks in advance will be considered at the subsequent Joint
Committee meeting.
F.2.6
After review of the commissioning report, the Joint Committee makes appropriate
recommendations to the Cospas-Sarsat Council. Formal commissioning is recorded at the
subsequent Council meeting, after approval of the Joint Committee recommendation by the
Council.
F.2.7
This commissioning and reporting procedure shall be implemented by all Cospas-Sarsat
Ground Segment Providers, including Parties to the International Cospas-Sarsat Programme
F-2
Agreement, for commissioning new MEOLUTs and MCCs or new equipment or functions
which have a significant impact on the Cospas-Sarsat Ground Segment operation.
F.2.8
The cost of implementing the commissioning procedure and reporting to the Cospas-Sarsat
Joint Committee is borne by the operating Agency or Administration installing the equipment
to be commissioned.
F.2.9
Ground Segment equipment will be commissioned into the Cospas-Sarsat System only if the
formal association of the MEOLUT and MCC operator with the Cospas-Sarsat Programme
has been notified in accordance with the standard procedure, unless otherwise agreed by the
Council.
F.3
LUT Commissioning
The following principles govern the implementation of the Cospas-Sarsat MEOLUT Commissioning
Standard (C/S T.020):
F.3.1
The implementation of the commissioning procedure defined in document C/S T.020 is the
responsibility of the operating Agency or Administration.
F.3.2
The operating Agency or Administration will be responsible for equipment which may be
required for performing the commissioning tests.
F.3.3
A MEOLUT may be commissioned as a stand-alone system, independent of an MCC.
However, MEOLUT commissioning may take place at the same time that the associated MCC
is being commissioned.
F.3.4
The MEOLUT/MCC interface is part of the MEOLUT commissioning. Therefore, it shall be
tested as part of the MEOLUT commissioning procedure.
F.3.5
If the test results in the commissioning report submitted by the operating Agency or
Administration do not demonstrate full compliance document C/S T.019, corrective action
shall be taken by the operating Agency or Administration.
F.3.6
If the test results in the commissioning report submitted by the operating Agency or
Administration do demonstrate full compliance with document C/S T.019, the alert data
derived from the new MEOLUT can be immediately used by the associated MCC for
distribution in accordance with document C/S A.001.
F.3.7
Once the alert data derived from the new MEOLUT begins to be used by the associated MCC,
a change of System status shall be notified to all MCCs by the associated MCC, in accordance
with the procedure of document C/S A.001.
F.3.8
The Joint Committee shall, at its following meeting, review the commissioning report and
recommend to the Cospas-Sarsat Council, as appropriate, formal commissioning of the
MEOLUT.
F-3
F.4
Status of the Cospas-Sarsat Ground Segment
F.4.8
After their commissioning, MEOLUTs are listed and described as appropriate in the
applicable System documents and the “Cospas-Sarsat System Data” document.
F.4.8
The Cospas-Sarsat MEOLUTs commissioned in the Cospas-Sarsat System shall be listed on
the Cospas-Sarsat website www.cospas-sarsat.int.
- END OF ANNEX F -
G-1
ANNEX G
GUIDELINES FOR INTEGRATION OF NEW MEOLUTS
IN THE COSPAS-SARSAT SYSTEM
The introduction of new MEOLUTs in the Cospas-Sarsat System is supervised by the Technical
Working Group (TWG) of the Cospas-Sarsat Joint Committee whose objectives include:
a) the improvement of the overall performance of the Cospas-Sarsat Ground Segment; and
c) the technical control of the development of the Cospas-Sarsat LUTs.
The guidelines hereunder, and Figure G.1, provide procedures for integrating a new MEOLUT into the
Cospas-Sarsat Ground Segment.
1. Installation of New Equipment - The new MEOLUT(s) equipment should be sited to allow the
widest possible horizon and to maximize coverage of national SRRs as well as the entire Cospas-
Sarsat System. The location of the MEOLUT(s) should also allow for reliable communications
with the associated MCC.
2. Ground Segment Description and MEOLUT Coverage - The national Administration should ensure
that a description of the new MEOLUT(s) along with (1) coordinates, (2) address, (3) frequencies
and (4) MEOLUT antenna masks are provided to the Cospas-Sarsat Secretariat.
The national Administration should also ensure that their MEOLUT(s) are properly registered
with the International Telecommunications Union (ITU). The forms provided in Annex H to
this document should be completed and forwarded to ITU through the appropriate national
authorities.
3. Commissioning Test - For new Ground Segment Providers, the MEOLUT Commissioning tests
may be scheduled to coincide with the MCC commissioning tests. In any case, the MEOLUT
should be connected to the MCC and tested in its operational configuration , including optional
capabilities, if used. However, statistics for optional capabilities shall be collected separately.
The MEOLUT Operator should ensure that test beacon(s) capable of transmitting the test code
sequences contained in Annex D is (are) available for the commissioning test, or the MEOLUT
Operator should coordinate with beacon simulator providers in the USA or France for the
transmission of such code sequences. If test beacons/simulators cannot be used during the
commissioning test, the MEOLUT Operator should ensure that an alternative method of
confirming compliance is identified.
The relevant sections of this document describe the operational, functional and processing, and
performance requirements to be tested. During the test, the data from the MEOLUT(s) should
be transmitted to the associated MCC, however, the data should be suppressed by the MCC
and not transmitted within the Cospas-Sarsat System.
4. Preparation of Commissioning Report - The results of the tests, along with the proper declarations
and verifications for items not specifically tested, should be documented in a commissioning report.
Annex A to this document contains the format of the commissioning report.
G-2
The commissioning report should include as a minimum the information requested in this
document and in the format contained in Annex A. In addition, information to explain or clarify
results should also be included in the commissioning report.
Any anomaly, or failure to meet a requirement, observed during the commissioning test should
be corrected and the requirement re-tested. After the MEOLUT satisfies the requirements of
document C/S T.019, the completed commissioning report should be submitted by the national
Administration to the Cospas-Sarsat Secretariat.
5. Initial Operational Capability (IOC) - If the commissioning test has been completed successfully,
and the commissioning report has been forwarded to the Cospas-Sarsat Secretariat, the MEOLUT
may begin operations in an IOC status. However, the MEOLUT cannot reach IOC status prior to
the MCC IOC date if the associated MCC is also in the commissioning process. The national
Administration, through its associated MCC, should notify all Ground Segment Operators of
a MEOLUT’s IOC status via a System Status message.
The IOC phase allows a thorough review of the MEOLUT performance. However a MEOLUT
shall not remain in an IOC phase for more than one year. MEOLUTs that have not reached
FOC within one year will be considered not operational, and documented as “Under
Development”. To regain IOC status the MEOLUT will require a retest of the elements which
prevented it from reaching FOC. The MEOLUT then must operate again in an IOC phase prior
to reaching FOC. All Cospas-Sarsat Ground Segment Operators should monitor the data from
new MEOLUTs for any significant anomalies that could impact Cospas-Sarsat operations.
6. Full Operational Capability (FOC) - If after 90 days of operation in an IOC state no anomalies are
detected in the performance of the MEOLUT, the MEOLUT should be declared at FOC by the
appropriate nodal MCC. The transition of a MEOLUT from an IOC status to a FOC status ensures
that the MEOLUT performs to Cospas-Sarsat standards and does not negatively impact System
operations.
7. Formal Commissioning - The Joint Committee reviews the commissioning report and, pending
additional details or explanations, submits the report to the Cospas-Sarsat Council. The Council
accepts the commissioning report and the MEOLUT is formally commissioned in the Cospas-
Sarsat Ground Segment.
G-3
Figure G.1: Overview of MEOLUT Integration
- END OF ANNEX G -
MO* Installs
MEOLUT
Equipment
MO Analyzes
Test Results/
Prepare Report
Ground Segment
Description to
C/S Secretariat
Begin Process to
Register MEOLUT
with ITU
MEOLUT Begins
Operations at IOC
C/S System
Monitors for
Anomalies
NM** Declares
MEOLUT at FOC
MEOLUT
Operator Takes
Corrective Action
Council Formally
Commissions
MEOLUT
C/S Secretariat
Submits Report to
Next JC
Conform to
C/S T.019?
* MO: MEOLUT operator
** NO: Nodal MCC
MO Prepares
Required
Documentation
MO Performs
Commissioning
Tests
Any
Significant
Anomalies?
JC Evaluates
Report and
Recommends
Commisionning
MO Submit
Report to C/S
Secretariat
MO Coordinates with
Beacons Simulator
Providers as Necessary
No
Yes
Yes
No
H-1
ANNEX H
GUIDELINES FOR REGISTRATION OF NEW MEOLUTS WITH ITU
[This Annex shall be taken from the corresponding Annex of document C/S T.005 (LEOLUT
Commissioning Standard) or document C/S T.010 (GEOLUT Commissioning Standard), with the
appropriate changes made to ensure that all references to LEOLUTs or GEOLUTs are changed to
MEOLUTs.]
- END OF ANNEX H -
- END OF DOCUMENT -
Cospas-Sarsat Secretariat
1250 Boul. René-Lévesque West, Suite 4215, Montreal (Quebec) H3B 4W8 Canada
Telephone: +1 514 500 7999 / Fax: +1 514 500 7996
Email: mail@cospas-sarsat.int
Website: www.cospas-sarsat.int
Reference in New Issue View Git Blame Copy Permalink