Ryan Malloy
4ed92efd69
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.
90 KiB
| title | description | sidebar | documentId | series | seriesName | documentType | isLatest | issue | revision | documentDate | originalTitle | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| T005: C/S T.005 - Issue 3 Rev.3 | Official Cospas-Sarsat T-series document T005 |
|
T005 | T | Technical | specification | true | 3 | 3 | October 2023 | C/S T.005 - Issue 3 Rev.3 |
📋 Document Information
Series: T-Series (Technical) Version: Issue 3 - Revision 3 Date: October 2023 Source: Cospas-Sarsat Official Documents
COSPAS-SARSAT LEOLUT COMMISSIONING STANDARD C/S T.005 Issue 3 - Revision 3
COSPAS-SARSAT LEOLUT COMMISSIONING STANDARD History Issue Revision Date Comments
Approved (CSC-5)
Approved (CSC-21)
Approved (CSC-23)
Approved (CSC-29)
Approved (CSC-31)
Approved (CSC-37)
Approved (CSC-39)
Approved (CSC-43)
Approved (CSC-51)
Approved (CSC-64)
Approved (CSC-69)
TABLE OF CONTENTS Page 1. INTRODUCTION ....................................................................................................... 1-1 1.1 Purpose ................................................................................................................. 1-1 1.2 Scope .................................................................................................................... 1-1 1.3 Reference Documents ........................................................................................... 1-1 2. LEOLUT 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-2 2.5 Data Collection Limitation ................................................................................... 2-2 2.6 Submission of Results .......................................................................................... 2-2 2.7 LEOLUT Commissioning and Integration ........................................................... 2-3 2.8 LEOLUT/MCC Interface ..................................................................................... 2-3 2.9 Confirmation of Requirements ............................................................................. 2-3 2.10 Change of Location .............................................................................................. 2-3 3. EVALUATION OF OPERATIONAL REQUIREMENTS ..................................... 3-1 3.1 LEOLUT Data Availability .................................................................................. 3-1 3.2 Data Requirements ............................................................................................... 3-1 3.3 Data Channels ....................................................................................................... 3-1 3.4 Satellite Tracking Capability ................................................................................ 3-1 3.5 Satellite Visibility/Signal Lock ............................................................................ 3-1 3.6 Status and Alarm .................................................................................................. 3-2 3.7 RF Radiation and Emissions ................................................................................ 3-2 3.8 Data Archiving ..................................................................................................... 3-2 4. EVALUATION OF FUNCTIONAL AND PROCESSING REQUIREMENTS ... 4-1 4.1 Functional Requirements ...................................................................................... 4-1 4.1.1 Antenna and RF Subsystem ................................................................... 4-1 4.1.2 Time and Frequency Reference Subsystem ........................................... 4-1 4.1.3 Orbit Maintenance Subsystem ............................................................... 4-1 4.1.4 MCC Interface ........................................................................................ 4-1 4.2 Beacon Message Processing ................................................................................. 4-1
EVALUATION OF PERFORMANCE REQUIREMENTS ................................... 5-1 5.1 SARP Test ............................................................................................................ 5-1 5.1.1 Satellite Passes ....................................................................................... 5-1 5.1.2 Orbitography or Reference Beacons ...................................................... 5-1 5.2 SARR Test ............................................................................................................ 5-1 5.2.1 Test Beacons .......................................................................................... 5-1 5.2.2 Satellite Passes ....................................................................................... 5-2 5.3 Combined SARP/SARR Test ............................................................................... 5-2 5.4 Combined LEO / GEO Processing ....................................................................... 5-2 5.5 Solution Statistics ................................................................................................. 5-2 5.6 Minimum Point Solution Statistics ....................................................................... 5-3 5.7 Solution Data ........................................................................................................ 5-3 LIST OF FIGURES Figure G.1: Overview of LEOLUT Integration LIST OF ANNEXES Annex A: LEOLUT 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: LEOLUT Commissioning - Principles and Policies Annex G: Guidelines for Integration of New LEOLUTs in the Cospas-Sarsat System Annex H: Guidelines for Registration of New LEOLUTs with ITU
1-1
INTRODUCTION 1.1 Purpose The Cospas-Sarsat LEOLUT Commissioning Standard shall be used to verify that a LEOSAR Local User Terminal (LEOLUT) complies with the Cospas-Sarsat LEOLUT Performance Specification (C/S T.002). The national Administrations that wish to connect a new LEOLUT to the Cospas-Sarsat network shall conduct the tests and provide the data, which is specified in this document, to the Cospas-Sarsat Secretariat. For multi-LEOLUT environments, each LEOLUT shall be commissioned individually as if it were a stand-alone LEOLUT. 1.2 Scope This standard specifies LEOLUT commissioning for the 406 MHz SARP channel (Processed Data Stream, PDS), the 406 MHz SARR channel (Ground Search and Rescue Processor, G-SARP), and for combined processing on the 406 MHz channels (i.e. SARP/SARR, SARP/GEOSAR, SARR/GEOSAR, and SARP/SARR/GEOSAR). 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 LEOLUT commissioning: a. C/S A.001, Cospas-Sarsat Data Distribution Plan (DDP); b. C/S A.002, Cospas-Sarsat Mission Control Centres Standard Interface Description (SID); c. C/S A.005, Cospas-Sarsat MCC Performance Specification and Design Guidelines; d. C/S A.006, Cospas-Sarsat MCC Commissioning Standard; e. C/S T.001, Specification for Cospas-Sarsat 406 MHz Distress Beacons; f. C/S T.002, Cospas-Sarsat LEOLUT Performance Specification and Design Guidelines; g. C/S T.003, Description of the Cospas-Sarsat LEOSAR Space Segment; h. C/S T.006, Cospas-Sarsat Orbitography Network Specification; i. C/S T.009, Cospas-Sarsat GEOLUT Performance Specification and Design Guidelines; and j. C/S T.010, Cospas-Sarsat GEOLUT Commissioning Standard.
- END OF SECTION 1-
2-1
LEOLUT COMMISSIONING 2.1 General The Cospas-Sarsat LEOLUT 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 LEOLUT into the Cospas-Sarsat Ground Segment. Conducting these tests and assessing the results is the responsibility of the national Administration desiring to commission a LEOLUT. The tests verify the LEOLUT's ability to receive and process signals transmitting in the SARP channel and optionally the SARR channel in accordance with document C/S T.002 (LEOLUT specification). A cross reference of the requirements in C/S T.002 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 LEOLUT 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 LEOLUT may be commissioned in various modes depending on the configuration of the LEOLUT, and the data channels processed. The SARP channel is specifically tested with the use of global-mode PDS data and local-mode PDS data. The SARR channel is specifically tested with the use of data obtained only from the G-SARP. If the LEOLUT is expected to operate with combined data from the SARP and SARR channels or with data from GEOLUTs, the combined modes of operation should be analyzed and reported separately in the commissioning report (Annex A), as specified in section 5.1.4. For LEOLUTs which use data from GEOLUTs for combined LEO/GEO processing, it is a prerequisite that the GEOLUTs meet the specification requirements of document C/S T.009 and be commissioned in accordance with document C/S T.010, in addition to the specific LEO/GEO commissioning requirements detailed herein. 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 test periods of operation and the test beacon location(s), and is also invited to provide this information to the Cospas-Sarsat Secretariat.
2-2
2.3 Test Data Collection The commissioning process for the SARP and SARR channels comprises the collection of specific beacon messages and the specified numbers of solutions. If a LEOLUT has the capability to process data from multiple channels or multiple sources, the data acquisition for the commissioning tests may be conducted individually or in parallel. Data should be collected from all available channels from all commissioned satellites. 2.4 Frequency Registration Administrations should register their LEOLUT’s use of the 1544.5 MHz frequency band by “notifying” their LEOLUTs with the International Telecommunication Union (ITU) in accordance with article 11 of the radio regulations. The information required to notify LEOLUTs 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.003 (LEOSAR space segment description) and C/S T.011 (GEOSAR payload description) 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.6 Submission of Results The results of the LEOLUT commissioning process, shall be documented in the commissioning report, in accordance with the format detailed at Annex A for a review by the Joint Committee or an Expert Working Group (EWG) tasked by the Cospas-Sarsat Council to review LUT commissioning reports (e.g., an EWG on LUT commissioning or the Joint Committee). In addition, the data detailed at Annex E shall be submitted to the Cospas-Sarsat Secretariat for evaluation, retention, and distribution to Participants. 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.
2-3
2.7 LEOLUT Commissioning and Integration The test results, as defined in the annexes shall be submitted for review by the experts of the Joint Committee or an EWG tasked by the Cospas-Sarsat Council to review LUT commissioning reports. The LEOLUT will be integrated into the Cospas-Sarsat Ground Segment as described in Annex F and Annex G. 2.8 LEOLUT/MCC Interface Validation of the LEOLUT/MCC interface shall be completed by the national Administration as part of the LEOLUT commissioning. 2.9 Confirmation of Requirements The national Administration shall confirm compliance to all requirements detailed in this document with either a measurement, verification, declaration, or combination of these methods. The exact method of confirming compliance for each respective requirement is identified in the summary table of the commissioning report (Annex A). A measurement requires the national Administration to conduct a test and include the supporting data as part of the commissioning report. 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. A declaration of compliance confirms that specific requirements are met although not necessarily tested as part of the commissioning process. Conformance to all requirements shall be documented in the commissioning report. 2.10 Change of Location If the location of a commissioned LEOLUT has been changed, the responsible national Administration shall ensure that the LEOLUT continues to satisfy C/S T.002 requirements prior to resuming operations. Additionally, the national Administration shall: a. confirm that the level of local interference does not adversely affect LEOLUT performance; b. verify the performance of the communication links in the new location; c. verify the performance of the antenna and RF subsystems; and d. update the technical file of the LEOLUT commissioning report (Appendix 1 to Annex A refers) by providing a declaration that the LEOLUT satisfies C/S T.002 requirements and the following information, to the Cospas-Sarsat Secretariat:
2-4
(i) Antenna Characteristics (Annex A, Appendix 1, section A.2.1), (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 LEOLUT, or indicate “no change” if appropriate, (iv) Communications Capability (Annex A, Appendix 1, section A.4), (v) Coverage (Annex A, Appendix 1, section A.5), (vi) Location (Annex A, Appendix 1, section A.6).
- END OF SECTION 2 -
3-1
EVALUATION OF OPERATIONAL REQUIREMENTS 3.1 LEOLUT Data Availability The LEOLUT 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 LEOLUT, the LEOLUT data shall be considered unavailable. 3.2 Data Requirements The national Administration shall ensure that the LEOLUT provides the data necessary for the associated MCC to distribute alert data according to the document C/S A.002 (SID). This shall be verified and noted in the appropriate section of the LEOLUT commissioning report. 3.3 Data Channels The data channels processed by the LEOLUT shall be listed in the commissioning report. The national Administration shall verify that the appropriate data channel requirements, as detailed at document C/S T.002 (LEOLUT specification), are satisfied, and note this in the appropriate section of the LEOLUT commissioning report. Furthermore, if the LEOLUT implements combined LEO/GEO processing, the identification of the sources of the GEOSAR data used shall be declared in the appropriate section of the commissioning report. 3.4 Satellite Tracking Capability The LEOLUT’s ability to track and recover data shall be measured for all scheduled passes during the commissioning period, according to the guidance provide at Annex B. The test results and associated analysis shall be included in the appropriate sections of the commissioning report. 3.5 Satellite Visibility/Signal Lock The national Administration shall conduct the tests and record the measurements detailed at Annex B, to demonstrate conformance with the satellite visibility specification contained at document C/S T.002 (LEOLUT specification). The test results and associated analysis shall be included in the appropriate sections of the commissioning report.
3-2
3.6 Status and Alarm The national Administration shall describe the status and alarm functions of the LEOLUT and declare compliance in the appropriate section of the LEOLUT commissioning report. 3.7 RF Radiation and Emissions The national Administration shall ensure that the LEOLUT 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 LEOLUT commissioning report. 3.8 Data Archiving The national Administration shall describe the data archiving capability of the LEOLUT and declare compliance in the appropriate section of the LEOLUT commissioning report.
- END OF SECTION 3 -
4-1
EVALUATION OF FUNCTIONAL AND PROCESSING REQUIREMENTS 4.1 Functional Requirements 4.1.1 Antenna and RF Subsystem The national Administration shall verify that the antenna and RF subsystem of the LEOLUT can acquire, track and receive the downlink signals from Cospas-Sarsat satellites. This verification shall be documented in the LEOLUT commissioning report. 4.1.2 Time and Frequency Reference Subsystem The national Administration shall declare in the LEOLUT commissioning report, the LEOLUT’s capability to maintain time and frequency subsystems according to document C/S T.002 (LEOLUT specification). 4.1.3 Orbit Maintenance Subsystem The national Administration shall declare, in the LEOLUT commissioning report, the LEOLUT’s capability to maintain accurate satellite orbital elements and tracking schedules as described in document C/S T.002 (LEOLUT specification). 4.1.4 MCC Interface The national Administration shall verify that the LEOLUT provides timely alert data of the level of quality and detail specified in documents C/S A.002 (SID) and C/S A.005 (MCC specification). This verification shall be documented in the LEOLUT commissioning report. 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 LEOLUTs compliance to the “channels processing specifications” detailed in document C/S T.002 (LEOLUT specification). These tests require the LEOLUT to process the data described at Annex D 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 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. Alternatively, national Administrations may arrange for the simulators in the United States or France to uplink the messages contained at Annex D. 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 shall not prevent the LEOLUT 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
EVALUATION OF PERFORMANCE REQUIREMENTS The national Administration shall conduct the tests defined at Annex C to confirm conformance with the LEOLUT performance requirements detailed at document C/S T.002 (LEOLUT specification). The results of these tests shall be included in the LEOLUT commissioning report. Additional guidance pertaining to the tests detailed at Annex C is provided in the remainder of this section. 5.1 SARP Test SARP data shall be collected from the available Cospas-Sarsat orbitography/test beacons (see Cospas-Sarsat website www.cospas-sarsat.org. At least one test/orbitography beacon shall be outside the local-mode coverage area. 5.1.1 Satellite Passes The performance measurement test shall consist of receiving and processing all scheduled passes during the test period. Global-mode data shall be obtained at least once from each available Cospas and Sarsat satellite. A pass schedule for all satellite passes during the test period, as defined in Annex E, shall be submitted to the Cospas-Sarsat Secretariat. 5.1.2 Orbitography or Reference Beacons A list of those orbitography or reference beacons that are used by the LEOLUT during the SARP test for updating the orbital elements shall be provided in the commissioning report. Solution data from these beacons shall not be used in the calculation of the LEOLUT performance statistics for those passes in which they are used for updating the orbits. 5.2 SARR Test A test shall be conducted to confirm that the LEOLUT local-mode SARR processing satisfies the performance requirements detailed in document C/S T.002. This test will be conducted using only data received via the SARR channel. 5.2.1 Test Beacons Local-mode tests shall be conducted with type-approved Cospas-Sarsat 406 MHz beacons coded with the test protocol and/or approved beacon simulators (i.e. not an
5-2
orbitography beacon). The beacons must be placed within the LEOLUT local-mode coverage area at a position known to within 100 metres and shall remain fixed at this position throughout the test. The beacon locations shall be given with respect to the reference system given in section 5.2.1. The test beacons shall not be used for updating the orbital elements. 5.2.2 Satellite Passes Local-mode tests shall consist of receiving and processing all scheduled passes from all commissioned satellites during the test period. 5.3 Combined SARP/SARR Test If the LEOLUT is expected to operate with combined data from the SARP and SARR channels, then a test shall be conducted to confirm that the LEOLUT satisfies the performance requirements detailed in document C/S T.002. This test will be conducted using data received from the SARP (local and global) and the G-SARP, and shall include data received from both within and external to the LEOLUT’s local-mode coverage area. 5.4 Combined LEO/GEO Processing If the LEOLUT is expected to perform combined LEO/GEO processing, then tests shall be conducted to confirm that the LEOLUT satisfies the LEO/GEO performance requirements detailed in document C/S T.002. The following channel combinations shall be tested if they are used operationally: a. combined SARP/GEOSAR or SARP/SARR/GEOSAR; and b. combined SARR/GEOSAR. 5.5 Solution Statistics All solutions from test/orbitography beacons used for commissioning shall be collected. Statistics shall be calculated on two types of solutions. a. solutions meeting the following criteria: (i) having four (4) or more data points, (ii) data points bracketing the TCA of the satellite to the beacon, and (iii) having an absolute value of cross-track angle (|CTA|) between 1 degree and 20 degrees, shall be classified as nominal solutions. b. solutions not meeting the criteria above shall be classified as marginal solutions. The statistics which shall be derived are listed in Annex C.
5-3
5.6 Minimum Point Solution Statistics LEOLUTs which implement combined LEO/GEO processing shall provide minimum point location accuracy solution statistics for all LEO/GEO channel combinations listed in 5.1.4 in addition to the requirements detailed in section 5.1.5. Minimum point solutions are defined as those solutions which are calculated from only two LEOSAR data points plus data from the GEOSAR system. Since minimum point solutions are a subset of marginal solutions, they are incorporated into the marginal solutions statistics1. Additionally, the minimum point solution location accuracy statistics shall be reported separately. 5.7 Solution Data The solution data from all tracked satellite passes shall be provided for each orbitography, beacon simulator, and/or test beacon used during the test period. A minimum of: a. 1000 nominal solutions shall be used for the SARP test (SARP data only); b. 100 nominal solutions for the combined SARP/SARR test (all solutions shall include SARP and SARR data); c. 50 nominal solutions shall be used for the local-mode SARR test (SARR data only); d. 100 nominal solutions and 100 minimum point solutions for the combined SARP/GEOSAR or SARP/SARR/GEOSAR tests; and e. 100 nominal solutions and 100 minimum point solutions for the combined SARR/GEOSAR test. All solutions shall be recorded in ASCII format onto a diskette and provided to the Secretariat as part of the commissioning report. The required data elements to be included in the commissioning report ASCII files, are listed in Annex E.
- END OF SECTION 5 - 1 When only two data points are available, the processing does not have sufficient data to compute an ambiguity resolution probability; the ambiguity resolution probability is always set to 50%. For this reason, there is no specified requirement for ambiguity resolution of minimum point solutions, and the requirement for marginal solutions is specified only for those marginal solutions that are not minimum point solutions.
ANNEXES TO COSPAS-SARSAT LEOLUT COMMISSIONING STANDARD
A-1
ANNEX A LEOLUT COMMISSIONING REPORT Country or national Administration: _______________ Location of LEOLUT:
Cospas-Sarsat Identifier:
Operational Configuration
(see Note) Start of Commissioning Period:
End of Commissioning Period:
Section 1.0 contains a summary of the commissioning results as well as the declarations (D) and verifications (V), by the national Administration, for requirements not specifically measured. The organization of the summary table follows the requirements contained in document C/S T.002. Section 2.0 contains the measurements (M) to support the results presented in section 1.0, a copy of the associated data is provided in ASCII format as required by document C/S T.005. A technical description of the LEOLUT is presented in Appendix 1. Note: When combined LEO/GEO processing is implemented, the sources (i.e., satellite and GEOLUT) of any GEOSAR data used by LEOLUT shall be identified. 1.0 Summary Table Paragraph in C/S T.002 Requirement or Test Pass Criteria Result Pass/ Fail Method of Compliance Declaration/Verification or Comments 3.1 LEOLUT Data Availability A 95 M 3.2 Data Requirements n/a n/a V 3.3 Data Channels Minimum 406 MHz Channel n/a V 3.4 Satellite Tracking Capability ST > 99 M 3.5 Satellite Visibility/Signal Lock L = 0 M 3.6 Status and Alarm n/a n/a D Include description in technical file 3.7 RF Radiation/Emissions n/a n/a D 3.8 Data Archiving n/a 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
A-2
Paragraph in C/S T.002 Requirement or Test Pass Criteria Result Pass/ Fail Method of Compliance Declaration/Verification or Comments 4.1.3 Orbit Maintenance Subsystem Maintenance for up to 8 Satellites. Update using 2 Methods. n/a D 4.1.4 MCC Interface n/a n/a V 4.2.2.1 SARP Channel Data Recovery n/a n/a V Ability to recover global and local- mode PDS data 4.2.2.2 SARR Channel Data Recovery Exact Match on 9 Bit Frame Synch n/a D Achieve identical match on 9 bit frame synchronization See para 2.2.4.B to C/S T.001 Bit Rate Tolerance Check Test - BR1 M/N > 0.75 n/a M 4.2.3 Bit Verification Test - BV1 See Annex D to C/S T.005 n/a M Bit Verification Test - BV2 See Annex D to C/S T.005 n/a M 4.2.4 Beacon Message Validation Test - MV1 See Annex D to C/S T.005 n/a M Beacon Message Validation Test - MV2 See Annex D to C/S T.005 n/a Beacon Message Validation Test - MV3 See Annex D to C/S T.005 n/a M Beacon Message Validation Test - MV4 See Annex D to C/S T.005 n/a M 4.2.5 Beacon Message Processing Test - LP1 See Annex D to C/S T.005 n/a M Beacon Message Processing Test - LP2 See Annex D to C/S T.005 n/a M Beacon Message Processing Test - LP3 See Annex D to C/S T.005 n/a M Beacon Message Processing Test - LP4 See Annex D to C/S T.005 n/a M Beacon Message Processing Test - IV1 See Annex D to C/S T.005 n/a M 4.2.6 Time and Frequency Requirements n/a n/a D 4.2.7 Doppler Processing and Validation Test - DP1 See Annex D to C/S T.005 n/a M 4.2.7.1 Selection of Data Points
--
-- Requirement the same as requirement 4.2.4 in C/S T.002 4.2.7.2 Rejection of Data Points Test - DP2 See Annex D to C/S T.005 n/a M 4.2.7.3 Combining Global/Local-mode SARP Data n/a n/a D 4.2.7.4 Combining SARR/SARP Data n/a n/a D
A-3
Paragraph in C/S T.002 Requirement or Test Pass Criteria Result Pass/ Fail Method of Compliance Declaration/Verification or Comments 4.2.7.5 Combining LEO/GEO Data n/a n/a V Alert msg to MCC shall include sources of GEO data & indicate beacon freq. Stability/instability. 4.2.7.6 Validation of Doppler Locations n/a n/a D 4.2.7.7 Beacon Message Assignment
--
-- Requirement the same as requirement 4.2.5 in C/S T.002 4.2.8 Transmission of Alert Data
--
-- Requirement the same as requirement 3.2 in C/S T.002 5.1.1 RF Signal Margin n/a n/a D 5.1.2 Processing Time PT < 15 min for 99% of passes M Requirement applicable to all processing combinations 5.1.3 Orbit Determination Error 2 km n/a D 5.1.4 Ambiguity Resolution A + B = 100 V 5.1.5 SARP Error Ellipse Nominal Solutions N/A M SARP Error Ellipse Marginal Solutions N/A M SARR Error Ellipse Nominal Solutions N/A M SARR Error Ellipse Marginal Solutions N/A M 5.2.1 SARP Data Recovery DR M 5.2.2 SARP Time and Frequency Calculation 1 millihertz and 1 millisecond resolution D 5.2.3 SARP Beacon Capacity 90 beacons in local-mode 200 beacons in global-mode D 5.2.4 SARP Location Accuracy M/N 0.95 (5 km) M Nominal Solutions M/N 0.98 (10 km) M SARP Location Accuracy M/N 0.60 (5 km) M Marginal Solutions M/N 0.80 (20 km) M 5.2.5 SARP Ambiguity Resolution Nominal Solutions M/N 0.90 M SARP Ambiguity Resolution Marginal Solutions M/N 0.60 M 5.3.1 SARR Signal Sensitivity Signal Sensitivity better than 36dB-Hz D
A-4
Paragraph in C/S T.002 Requirement or Test Pass Criteria Result Pass/ Fail Method of Compliance Declaration/Verification or Comments 5.3.2 SARR Beacon Message Throughput T 0.75 M 5.3.3 SARR Probability of Doppler Location PDL 0.95 M 5.3.4 SARR Time and Frequency Calculation 350 millihertz and 10 ms D 5.3.5 SARR Beacon Capacity 10 beacons D 5.3.6 SARR Location Accuracy M/N 0.95 (5 km) M Nominal Solutions M/N 0.98 (10 km) M SARR Location Accuracy M/N 0.60 (5 km) M Marginal Solutions M/N 0.80 (20 km) M 5.3.7 SARR Ambiguity Resolution Nominal Solutions M/N 0.90 M SARR Ambiguity Resolution Marginal Solutions M/N 0.60 M 5.3.8 False Alert Prevention False Alerts Caused by Processing Anomalies < 1 x 10-4 D,V 5.3.9 Processing Bandwidth 406.010 to 406.090 MHz D 5.4 Combined SARP and SARR Processing as per document C/S T.002 D Only applicable to LEOLUTs which combine SARP and SARR data 5.4.a Combined SARP and SARR Location Accuracy Nominal Solutions M/N 0.95 (5 km) M Only applicable to LEOLUTs which combine SARP and SARR data M/N 0.98 (10 km) M Combined SARP and SARR Location Accuracy M/N 0.60 (5 km) M Marginal Solutions M/N 0.80 (20 km) M 5.4.b Combined SARP and SARR Ambiguity Resolution Nominal Solutions M/N 0.90 M Only applicable to LEOLUTs which combine SARP and SARR data Combined SARP and SARR Ambiguity Resolution Marginal Solutions M/N 0.60 M
A-5
Paragraph in C/S T.002 Requirement or Test Pass Criteria Result Pass/ Fail Method of Compliance Declaration/Verification or Comments 5.4.c Combined SARP and SARR Error Ellipse Nominal Solutions N/A M Only applicable to LEOLUTs which combine SARP and SARR data Combined SARP and SARR Error Ellipse Marginal Solutions N/A M 5.5 Combined SARP/GEOSAR or SARP/SARR/GEOSAR Processing as per document C/S T.002 D Only applicable to LEOLUTs which combine LEOSAR and GEOSAR data 5.5.1.a Combined SARP/GEOSAR or SARP/SARR/GEOSAR Processing M/N 0.95 (5 km) M Only applicable to LEOLUTs which combine LEOSAR and GEOSAR data Location Accuracy Nominal Solutions M/N 0.98 (10 km) M Combined SARP/GEOSAR or SARP/SARR/GEOSAR Processing M/N 0.60 (5 km) M Location Accuracy Marginal Solutions M/N 0.80 (20 km) M 5.5.2 Combined SARP/GEOSAR or SARP/SARR/GEOSAR Processing M/N 0.60 (5 km) M Only applicable to LEOLUTs which combine LEOSAR and GEOSAR data Location Accuracy Minimum Point Solutions M/N 0.80 (20 km) M 5.5.1.b Combined SARP/GEOSAR or SARP/SARR/GEOSAR Processing Ambiguity Resolution Nominal Solutions M/N 0.90 M Only applicable to LEOLUTs which combine LEOSAR and GEOSAR data Combined SARP/GEOSAR or SARP/SARR/GEOSAR Processing Ambiguity Resolution Marginal Solutions M/N 0.60 M Excluding minimum point solutions 5.5.1.c Combined SARP/GEOSAR or SARP/SARR/GEOSAR Processing Error Ellipse Nominal Solutions N/A M Only applicable to LEOLUTs which combine LEOSAR and GEOSAR data Combined SARP/GEOSAR or SARP/SARR/GEOSAR Processing Error Ellipse Marginal Solutions N/A M 5.5 Combined SARR/GEOSAR Processing as per document C/S T.002 D Only applicable to LEOLUTs which combine SARP and GEOSAR data
A-6
Paragraph in C/S T.002 Requirement or Test Pass Criteria Result Pass/ Fail Method of Compliance Declaration/Verification or Comments 5.5.1.a Combined SARR/GEOSAR Location Accuracy Nominal Solutions M/N 0.95 (5 km) M Only applicable to LEOLUTs which combine SARR and GEOSAR data M/N 0.98 (10 km) M Combined SARR/GEOSAR Location Accuracy Marginal Solutions M/N 0.60 (5 km) M Only applicable to LEOLUTs which combine LEOSAR and GEOSAR data M/N 0.80 (20 km) M 5.5.2 Combined SARR/GEOSAR Location Accuracy Minimum Point Solutions M/N 0.60 (5 km) M Only applicable to LEOLUTs which combine LEOSAR and GEOSAR data M/N 0.80 (20 km) M 5.5.1.b Combined SARR/GEOSAR Ambiguity Resolution Nominal Solutions M/N 0.90 M Only applicable to LEOLUTs which combine SARR and GEOSAR data Combined SARR/GEOSAR Ambiguity Resolution Marginal Solutions M/N 0.60 M Excluding minimum point solutions 5.5.1.c Combined SARR/GEOSAR Error Ellipse Nominal Solutions N/A M Only applicable to LEOLUTs which combine SARR and GEOSAR data Combined SARR/GEOSAR Error Ellipse Marginal Solutions N/A M
A-7
2.0 Results of Measurements This section contains the detailed results of measurements summarized in section 1.0. Each of the requirements is referred to in the report by the report reference number. The test procedure column identifies the reference in document C/S T.005, where the detailed test procedure and pass / fail criteria is provided. Report Ref # Title Test Procedure 2.1 Operational Requirements 2.1.1 LEOLUT Data Availability (A) B.1 2.1.2 Satellite Tracking (ST) B.2 2.1.3 Satellite Visibility/Signal Lock (L) B.3 2.2 Functional and Processing Requirements 2.2.1 Bit Verification (test code sequence BV1 - BV2) D1 2.2.2 Beacon Message Validation (test code sequence MV1 - MV4) D1 2.2.3 Beacon Message Processing (test code sequence LP1 - LP4 and IV1) D1 2.2.4 Doppler Processing and Validation (test code sequence DP1) D1 2.2.5 Rejection of Data Points (test code sequence DP2) D1 2.3 Performance Requirements 2.3.1 Processing Time (PT) C.1.2 2.3.2 SARP Statistics 2.3.2.1 SARP Data Recovery (DR) C.2.1 2.3.2.2 SARP Location Accuracy C.2.2 2.3.2.3 SARP Ambiguity Resolution C.2.3 2.3.2.4 SARP Error Ellipse C.2.4 2.3.3 SARR Statistics 2.3.3.1 SARR Beacon Message Throughput (T) C.2.5 2.3.3.2 SARR Probability of Doppler Location (PDL) C.2.6 2.3.3.3 SARR Location Accuracy C.2.2 2.3.3.4 SARR Ambiguity Resolution C.2.3 2.3.3.5 SARR Error Ellipse C.2.4
A-8
2.3.4 Combined SARP / SARR Statistics 2.3.4.1 Location Accuracy C.2.2 2.3.4.2 Ambiguity Resolution C.2.3 2.3.4.3 Error Ellipse C.2.4 2.3.5 Combined SARP/GEOSAR or SARP/SARR/GEOSAR Statistics 2.3.5.1 Location Accuracy C.2.2 2.3.5.2 Ambiguity Resolution C.2.3 2.3.5.3 Error Ellipse C.2.4 2.3.6 Combined SARR/GEOSAR Statistics 2.3.6.1 Location Accuracy C.2.2 2.3.6.2 Ambiguity Resolution C.2.3 2.3.6.3 Error Ellipse C.2.4 3.0 Other Information 3.1 The list of orbitography beacons used for orbit updates.
A-9
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. type and number of antennas b. gain/temperature ratio (G/T) at 5o elevation angle above the local horizon, and actual elevation angle at which the G/T was measured c. operational limitations d. dedicated or shared 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 A.2.3 General Capabilities a. processing capability ( SARP and SARR) b. interference-monitoring capability c. combined LEO/GEO processing capabilities A.3 Processing a. specific-performance capability b. manufacturer specifications c. bit error rate on PDS channel at Eb/No of 13 dB d. list of orbitography beacons used for orbit updating during the global-mode test e. G-SARP parameters (processing bandwidth, signal sensitivity and beacon processing capacity) A.4 Communications Capability a. primary-mode configuration b. backup-mode configuration
A-10
A.5 Coverage a. site-horizon profile b. operational-tracking (elevation) limits A.6 Location 2 a. latitude and longitude (of antenna) b. altitude
- END OF ANNEX A -
The location shall be given with respect to the Bureau International de L’Heure (BIH) geodetic reference system.
B-1
ANNEX B STATISTICS FOR OPERATIONAL REQUIREMENTS B.1 LEOLUT Data Availability (A) LEOLUT data availability measures the probability of receiving complete and accurate LEOLUT data at the MCC. Whenever a LEOLUT does not perform any of its functions, downtime (DT) is measured from LOS of the last successful satellite pass to AOS of the next successful satellite pass. 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 is that period of time when the LEOLUT fails to perform any of its basic functions. Therefore: A = (OT / OTR) * 100 = (1 - (DT / OTR)) * 100 and shall be greater than 95. B.2 Satellite Tracking (ST) ST = N/M * 100 and shall be greater than 99, where M = number of non-conflicting passes visible to the LEOLUT with a maximum elevation angle of 5o above the horizon during the commissioning period, and N = number of successfully tracked passes. B.3 Satellite Visibility/Signal Lock (L) L = number of passes that the LEOLUT lost carrier lock on the satellite downlink carrier signal while the satellite was above a 5o elevation angle (except where local obstructions prevent this). L shall be equal to 0.
- 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 LEOLUT. Data sets pertaining to number of points, TCA and CTA for nominal solutions and marginal solutions are defined in sections 5.1.4. For 406 MHz statistics, the report must include a list of: a) all 406 MHz beacons which were used for orbit updating during the test period; and b) all 406 MHz beacons used for the statistical data analysis. C.1.2 Processing Time (PT) Processing time is defined as the elapsed time between the Loss Of Signal (LOS) and the time at which all processed solutions are transmitted to the MCC. Processing time is evaluated for the LEOLUT in its operational configuration (i.e. when it is configured to process all channels as described in section 3.3). PT = N - LOS, where N is the time when all solutions are transmitted to the MCC and LOS is the loss of signal. PT shall be less than 15 minutes for 99% of all passes. The minimum, average and maximum processing times for the commissioning period shall be provided. C.2 406 MHz Statistics C.2.1 Data Recovery (DR) DR= Number of received 2.4 kbps frames Number of expected 2.4 kbps frames while satellite is above 5 elevation angle o DR shall be 1.0 or greater for each pass. This test is required for SARP only commissioning. It is not required for any combined channel processing commissioning.
C-2
C.2.2 Location Accuracy Nominal Solutions 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 0.98 where: M = number of solutions within 10 km N = number of solutions A histogram for the location accuracy of the correct solutions shall be provided. The histogram shall be in 2 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. Marginal Solutions M/N shall be greater than or equal to the following: 0.60 where: M = number of solutions within 5 km N = number of solutions 0.80 where: M = number of solutions within 20 km N = number of solutions Minimum Point Solutions M/N shall be greater than or equal to the following: 0.60 where: M = number of solutions within 5 km N = number of solutions 0.80 where: M = number of solutions within 20 km N = number of solutions
C-3
Testing the minimum point solution accuracy is only applicable to combined LEO - GEO Processing channel combinations. A histogram for the location accuracy of the correct solutions shall be provided. The histogram shall be in 5 km increments from 0 to 50 km. All solutions with an error greater than 50 km shall be individually listed and an explanation for the error provided. C.2.3 Ambiguity Resolution Nominal Solutions For the global-mode, the M/N shall be greater than or equal to 0.90, where: M = number of solutions with correct “A” solution N = number of solutions Marginal Solutions (Excluding minimum point solutions) For the global-mode, the M/N shall be greater than or equal to 0.60, where: M = number of solutions with correct “A” solution N = number of solutions C.2.4 Error Ellipse Nominal Solutions For the global-mode, the M/N shall be reported where: M = number of solutions for which the actual location falls inside the error ellipse N = number of solutions Marginal Solutions For the global-mode, the M/N shall be reported where: M = number of solutions for which the actual location falls inside the error ellipse N = number of solutions C.2.5 Beacon Message Throughput (T) For each test beacon event calculate: T = N / (D/R + 1), where: N = Number of valid messages recovered by the G-SARP D = Duration of the curve (first valid point to last valid point) R = Repetition rate of the test beacon The average value of T for all beacon events shall be 0.75 or greater.
C-4
This test is required for G-SARP only commissioning. It is not required for any combined channel processing commissioning. C.2.6 Probability of Doppler Location (PDL) PDL = M/N, where: M = Number of satellite passes with 4 minutes of mutual visibility between the LEOLUT, satellite and test beacon at 5o elevation angle where a Doppler solution for the test beacon was calculated N = Total number of satellite passes with 4 minutes of mutual visibility between the LEOLUT, satellite and test beacon at 5o elevation angle PDL shall be 0.95 or greater This test is required for G-SARP only commissioning. It is not required for any combined channel processing commissioning.
- END OF ANNEX C -
ANNEX D BEACON SIMULATOR TEST SCRIPT D.1 Test Messages to be Transmitted Test Code Sequence Simulator Transmit Frequency (MHz) Date/Time (UTC) Transmitted 30 Hex Transmitted Code (15 Hex Identifier, bits 26-85) Number of Bit Errors Comments PDF-1 BCH-1 PDF-2 BCH-2 Bit Rate Tolerance Check (BR) BR1 [TBD] 406.025 [TBD] 96EEF9DA0A2BA9EB5F96F400000F19
Transmit 20 bursts at the higher end of the permissible Bit Rate Range (396 bps) [TBD] 406.025 [TBD] 96EEF9DA0A2BA9EB5F96F400000F19
Transmit 20 bursts at the lower end of the permissible Bit Rate Range (404 bps) Bit Verification (BV) BV1 USA 406.025 [TBD] 56EE1100000000037E540000000000
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.027 [TBD] D6E10E1A4324920458B9D555555555
USA, Orbitography beacon with a pattern of 01" in the long message. No bit errors 406.027 D6E10E1A4324920458B9D555555555
Same as above Message Validation (MV) MV1 USA 406.023 [TBD] D6EE1100000000265F1424DB4CEFBF
USA, User Test coded beacon with encoded position (38.855, -76.931) in PDF-1. Two (2) bit errors at bits 44 and 48 in PDF-1. Two (2) bit errors at bits 133 and 134 in BCH-2 406.023 D6EE0011100000265F1424DB4CE3BF
Three (3) bit errors at bits 52, 56 and 60 in PDF-1. MV2 USA 406.025 [TBD] 96EE0000002729A5E22BB61B842E0A
USA, Standard Location Protocol Test coded beacon with encoded position (38.855, - 76.931) in PDF-1 and PDF-2. 406.025 96EE0000002729A5E22BB61B842E0A
Same as above 406.025 96EE0000002729A5E22BB61B842EOA
Same as above D-1
Test Code Sequence Simulator Transmit Frequency (MHz) Date/Time (UTC) Transmitted 30 Hex Transmitted Code (15 Hex Identifier, bits 26-85) Number of Bit Errors Comments PDF-1 BCH-1 PDF-2 BCH-2 MV2 (Cont) USA 406.025 [TBD] 96EE00000029299B91383601261D93
Position updated to 40.995 degrees. 406.025 96EE00000029299B91383601261D9F
Two (2) bit errors at bits 141 and 142 in BCH-2. MV3 USA 406.027 [TBD] 96EF000009B74CE5C3CFF61C080BF5
USA, National Location Protocol Test coded beacon with encoded position (38.855, -76.931) in PDF-1 and PDF-2. Three (3) bit errors at bits 88, 96 and 104 in BCH-1. 406.027 96EF111109B74CE4C2CEF61C080BF5
USA, National Location Protocol Test coded beacon with encoded position (38.855, -76.931) in PDF-1 and PDF-2. Four (4) bit errors at bits 44, 48, 52 and 56 in PDF-1. 406.027 96EF111019B74CE4C2CEF61C080BF5
USA, National Location Protocol Test coded beacon with encoded position (38.855, -76.931) in PDF-1 and PDF-2. Four (4) bit errors at bits 44, 48, 52 and 60 in PDF-1. MV4 USA 406.025 [TBD] D6EEFEAAAAAAAAA2EA1A24E14CD2B4
USA, User Test coded beacon with encoded position (38.855, -76.931) in PDF-2. Three (3) bit errors at bits 42, 44 and 46 in PDF-1. D-2
Test Code Sequence Simulator Transmit Frequency (MHz) Date/Time (UTC) Transmitted 30 Hex Code Number of Bit Errors Comments PDF-1 BCH-1 PDF-2 BCH-2 Location Protocol Processing (LP) LP1 France 406.025 [TBD] 8E3E0000007FDFFC77A376000003DD
France, Standard Location Protocol Test coded beacon with default encoded position in PDF-1 and 0s in PDF-2. 406.025 8E3E0000007FDFFC77A376000003DD
Same as above 406.025 8E3E0000007FDFFC 77A376000003DD
Same as above 406.025 8E3E0000002B80372E8BB68E011E5C
Encoded position (43.559, 1.482) in PDF-1 and PDF-2 406.025 8E3E0000002B80372E8BB68E011E5C
Same as above 406.025 8E3E0000002B80372E8BB68E011E5C
Same as above LP2 France 406.025 [TBD] 8E3F00000AA20175813BB60F380F6B
France, National Location Protocol Test coded beacon with encoded position (42.559, 1.482) in PDF-1 and PDF-2 406.025 8E3F00000AA20175813BB60F380F6B
Same as above 406.025 8E3F00000AA20175813BB60F380F6B
Same as above 406.025 8E3FF0004AE2017491D4360F380F6B
Encoded position updated (43.559, 1.482) in PDF-1 406.025 8E3FF0004AE2017491D4360F380F6B
Same as above 406.025 8E3FF0004AE2017491D4360F380F6B
Same as above D-3
Test Code Sequence Simulator Transmit Frequency (MHz) Date/Time (UTC) Transmitted 30 Hex Transmitted Code (15 Hex Identifier, bits 26-85) Number of Bit Errors Comments PDF-1 BCH-1 PDF-2 BCH-2 LP3 USA 406.025 [TBD] D6EE1F1E1E1E1E06A383EFE0FF0146
USA, User Test coded beacon with default encoded position in PDF-2. One (1) bit error at bit 48 in PDF-1 406.025 D6EE1F1E1E1E1E06A383E4E14CD2BE
Encoded position updated (38.995, - 76.851) 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.025 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.025 D6EE1F1E1E1E1E06A383E4E14CD2B4
One (1) bit error in bit 48 in PDF-1. LP4 USA 406.025 [TBD] 96EF000049C14CD260D5F608380389
USA, National Location Protocol Test Coded beacon with encoded position (38.995, -76.851). 406.025 96EF000049C14CD260D5F608380389
Same as above. 406.025 96EFF00049C14CD260D5F608380389
Four (4) bit errors at bits 41, 42, 43 and 44 in PDF-1. 406.025 96EF000049814CD2E947F608380389
Encoded position (37.995, -76.851) updated. 406.025 96EF000049814CD2E947F60838038F
Two (2) bit errors in bits 142 and 143. 406.025 96EF000049814CD2E947F6083803E9
Two (2) bit errors in bits 138 and 139. D-4
Test Code Sequence Simulator Transmit Frequency (MHz) Date/Time (UTC) Transmitted 30 Hex Transmitted Code (15 Hex Identifier, bits 26-85) Number of Bit Errors Comments PDF-1 BCH-1 PDF-2 BCH-2 Invalid Beacon Message Processing (IV) IV1 France 406.025 [TBD] 8E3FF0004AE2017491D4360F380F6B
France, National Location Protocol Test coded beacon. Four (4) bit errors at bits 41, 42, 43 and 44. 406.025 8E3FF0004AE2017493D4360F380F6B
France, National Location Protocol Test coded beacon. Four (4) bit errors at bits 41, 42, 43 and 44 and one (1) bit error at bit 95. 406.025 8E3FF0004AE2017493D4360F380F6B
Same as above. 406.025 8E3FF0004AE2017493D4360F380F6B
Same as above. Doppler Processing (DP) DP1 France 406.025 [TBD] 4E3EAAAAAAAAAAA057FD8000000000
France User Test coded beacon. 406.025 4E3EAAAAAAAAAAA057FD8000322000
Same as above 406.025 4E3EAAAAAAAAAAA057FD8000000000
Multiple errors in PDF-2 DP2 USA 406.025 [TBD] 56EE0000000000477BEAC000000000
USA, User Test coded beacon. 406.025 56EE0000000000477BEAC000000000
Same as above 406.029 56EE0000000000477BEAC000000000
Same as above 406.025 56EE0000000000477BEAC000000000
Same as above 406.025 56EE0000000000477BEAC000000000
Same as above D-5
Test Code Sequence Simulator Transmit Frequency (MHz) Date/Time (UTC) Transmitted 30 Hex Transmitted Code (15 Hex Identifier, bits 26-85) Number of Bit Errors Comments PDF-1 BCH-1 PDF-2 BCH-2 DP2 (Cont) USA 406.025 [TBD] 56EE0000000000477BEAC000000000
Same as above 406.025 56EE0000000000477BEAC000000000
Same as above 406.029 56EE0000000000477BEAC000000000
Same as above 406.025 56EE0000000000477BEAC000000000
Same as above 406.025 56EE0000000000477BEAC000000000
Same as above D-6
D.2 Expected Processing Test Code Sequence Message to be Transmitted by LEOLUT Encoded Location Comments BR1 96EEF9DA0A2BA9EB5F96F400000F19 n/a LEOLUT sends a valid message to the MCC. BV1 56EE0000000000037E540000000000 n/a LEOLUT should correct two bit errors and transmit corrected message to MCC. BV2 D6E10E1A4324920458B9D555555555 n/a LEOLUT should transmit orbitography beacon message without error correcting the long message. MV1 D6EE0000000000265F1424FFFFFFFF n/a LEOLUT corrects both beacon messages (message is confirmed) and transmits corrected message to MCC with bits 113 to 144 set to all 1. MV2 96EE0000002729A5E22BB61B842E0A 38.855, -76.951 LEOLUT sends the first complete, confirmed message to MCC and calculates Doppler position. MV3 n/a n/a LEOLUT suppresses beacon alert because no valid message exists and no match available for invalid messages. MV4 n/a n/a LEOLUT suppresses beacon alert because no message has 3 bit errors and is not confirmed. LP1 8E3E0000002B80372E8BB68E011E5C 43.559, 1.482 LEOLUT sends updated, confirmed message for Standard Location Protocol beacon to MCC. LP2 8E3F00000AA20175813BB60F380F6B 43.559, 1.482 LEOLUT sends updated, confirmed message for National Location Protocol beacon to MCC. LP3 D6EE1E1E1E1E1E06A383E4FFFFFFFF n/a LEOLUT sends valid short message to MCC, however bits 113 to 144 are set to all 1 because PDF-2 is not confirmed. LP4 96EF000049C14CD260D5F608380389 38.855, -76.951 LEOLUT sends complete, confirmed message to MCC. IV1 8E3FF0004AE2017491D436FFFFFFFF or 8E3FF0004AE2017493D436FFFFFFFF n/a LEOLUT calculates Doppler location and sends invalid message to MCC with bits 113 to 144 all set to 1. DP1 4E3EAAAAAAAAAAA057FD8000000000 n/a LEOLUT should generate Doppler location, set bits 113 to 144 to 0 and transmit to MCC. DP2 56EE0000000000477BEAC000000000 n/a LEOLUT should eliminate suspect data points and calculate Doppler location.
- END OF ANNEX D - D-7
E-1
ANNEX E DATA FORMAT E.1 General This annex describes the data format to be provided to the Cospas-Sarsat Secretariat separately from a commissioning report. The data is to be provided in three separate electronic text files, one for the tracking database (section D.2), the solution data (section D.3), and the beacon database (section D.4). The data is to be provided in a comma (,) delimited format, and each field shall include an entry. If there is no data for any given field, then a blank space is to be inserted into the appropriate portion of the file. All solution data used in the commissioning testing are to be provided. 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 bytes for the field Dec The total number of bytes after the decimal MF# Message Field as described in C/S A.002 (SID) Comments E.2 Tracking Database Field Description Detailed Format Type Width Dec MF# Comments
LUT ID AAAA C
Satellite ID nnn N
Orbit Number nnnnn N
LUT AOS Time YYDDDhhmm N
LUT LOS Time YYDDDhhmm N
Pass Scheduled Y or N L
Pass Tracked Y or N L
Solution from Pass Y or N L
Manually Scheduled Y or N L
E-2
E.3 LUT Database for Solution Data Field Description Detailed Format Type Width Dec MF# Comments
LUT ID C
Location Name C
Beacon ID C
Beacon Message C
Satellite ID nnn N
A Calculated TCA YYDDDhhmm N
Note 1
B Calculated TCA YYDDDhhmm N
LUT AOS Time YYDDDhhmm N
LUT LOS Time YYDDDhhmm N
Window Factor n N
LUT TPC YYDDDhhmm N
Message Number nnnnn N
Transmit Time YYDDDhhmm N
Time of First Data Point Received snnnn N
Note 2
Time of Last Data Point Received snnnn N
Note 2
“A” Latitude snn.nnn N
“A” Longitude snnn.nnn N
“A” CTA snn.n N
“A” Heading nnn N
“A” Semi-Major nnn.n N
“A” Semi-Minor nnn.n N
“A” Bias (Hz) snnnnn.n N
“B” Latitude snn.nnn N
“B” Longitude snnn.nnn N
“B” CTA snn.n N
“B” Heading nnn N
“B” Semi-Major nnn.n N
“B” Semi-Minor nnn.n N
“A” Probability nn N
Number of Points nnnn N
Confidence Factor n N
Note 3
Processing Sources C
Note 4
GEOLUT Source C
GEOSAR Satellite C
Note 5
Comments C
Notes 1. For 406 MHz unlocated alerts, use time of last data point. 2. Time in seconds relative to calculated TCA of solution A. 3. Confidence factor of "A" solution. Use 9 if not calculated at LEOLUT. 4. For 406 MHz alerts, indicate each channel source which provided data in the alert as “S” for SARP, “G” for SARR, and/or “C” for Combined with GEOSAR data (e.g. a SARP only solution would be indicated with an “S”, a SARP/SARR solution would be indicated by “SG”, and a SARP/SARR/GEOSAR solution would be indicated by “SGC”). 5. Indicate the first letter for the series of the GEOSAR satellite (e.g. G for GOES) followed by its designator (e.g. G08 would represent GOES-8 and I2A would represent INSAT-2A).
E-3
E.4 Beacon Database Description Field Description Detailed Format Type Width Dec MF# Comments
Beacon Number nn N
Location C
Beacon ID C
Latitude of Beacon snn.nnn N
Longitude of Beacon snnn.nnn N
Type C
Country C
Activation Time YYDDDhhmm N
Deactivation Time YYDDDhhmm N
Actual “On” Time YYDDDhhmm N
Actual “Off” Time YYDDDhhmm N
Comments C
- END OF ANNEX E -
F-1
ANNEX F LEOLUT COMMISSIONING - PRINCIPLES AND POLICIES F.1 References The Cospas-Sarsat Council approved the general principles of its commissioning policy for LEOLUTs, 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 standards and design guidelines for LEOLUTs and MCCs are defined in documents C/S T.002 and C/S A.005, respectively. F.2.3 Cospas-Sarsat criteria and test methods for verifying that LEOLUTs and MCCs meet these standards are defined in documents C/S T.005 and C/S A.006, respectively. F.2.4 The responsible Agency or Administration installing and planning to operate a new LEOLUT 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 or an EWG established by the Cospas-Sarsat Council to review LUT commissioning reports and be subsequently submitted by the Ground Segment Provider as per the meeting submission deadline. F.2.6 After review of the commissioning report, appropriate recommendations are made to the Cospas-Sarsat Council. Formal commissioning is recorded at the subsequent Council meeting, after approval of recommendation by the Council.
F-2
F.2.7 This commissioning and reporting procedure shall be implemented by all Cospas-Sarsat Ground Segment operators, including Parties to the International Cospas-Sarsat Programme Agreement, for commissioning new LEOLUTs 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 Cospas- Sarsat 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 LEOLUT 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 LEOLUT Commissioning Standard (C/S T.005): F.3.1 The implementation of the commissioning procedure defined in document C/S T.005 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 LEOLUT may be commissioned as a stand-alone system, independent of an MCC. However, LEOLUT commissioning may take place at the same time that the associated MCC is being commissioned. F.3.4 The LEOLUT/MCC interface is part of the LEOLUT commissioning. Therefore, it shall be tested as part of the LEOLUT 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 with the LEOLUT Performance Specification (C/S T.002), corrective action shall be taken. F.3.6 If the test results in the commissioning report submitted by the operating Agency or Administration do demonstrate full compliance with the LEOLUT Performance Specification (C/S T.002), the alert data derived from the new LEOLUT can be immediately used by the associated MCC for distribution in accordance with the Cospas-Sarsat Data Distribution Plan (C/S A.001). F.3.7 Once the alert data derived from the new LEOLUT 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
F.3.8 The Joint Committee or an EWG established by the Council for the purpose reviews the LUT commissioning report and recommends to the Cospas-Sarsat Council, as appropriate, formal commissioning of the LEOLUT. F.4 STATUS OF THE COSPAS-SARSAT GROUND SEGMENT F.4.1 After their commissioning, LEOLUTs are listed and described as appropriate in the applicable System documents and the “Cospas-Sarsat System Data” document. F.4.2 The Cospas-Sarsat LEOLUTs commissioned in the Cospas-Sarsat System shall be listed on the Cospas-Sarsat website www.cospas-sarsat.org.
- END OF ANNEX F -
G-1
ANNEX G GUIDELINES FOR INTEGRATION OF NEW LEOLUTs IN THE COSPAS-SARSAT SYSTEM The introduction of new LEOLUTs in the Cospas-Sarsat System is supervised by the Joint Committee or an EWG body tasked by the Cospas-Sarsat Council to review LUT commissioning reports whose objectives support: a) the improvement of the overall performance of the Cospas-Sarsat Ground Segment; and b) the technical control of the development of the Cospas-Sarsat LUTs. The guidelines hereunder, and Figure G.1, provide procedures for integrating a new LEOLUT into the Cospas-Sarsat Ground Segment. 1. Installation of New Equipment - The new LEOLUT(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 LEOLUT(s) should also allow for reliable communications with the associated MCC. 2. Ground Segment Description and LEOLUT Coverage - The national Administration should ensure that a description of the new LEOLUT(s) along with (1) coordinates, (2) address, (3) frequencies and (4) LEOLUT antenna masks are provided to the Cospas- Sarsat Secretariat. The national Administration should also ensure that their LEOLUT(s) are properly registered with the International Telecommunications Union (ITU). The forms provided in Annex I to this document should be completed and forwarded to ITU through the appropriate national authorities. 3. Commissioning Test - For new Ground Segment Providers, the LEOLUT Commissioning tests may be scheduled to coincide with the MCC commissioning tests. In any case, the LEOLUT should be connected to the MCC and tested in its operational configuration processing all channels identified in section 3.3 of this document. However, statistics for the different channels may be collected separately. The LEOLUT 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 LEOLUT 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 LEOLUT 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
G-2
LEOLUT(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. 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 LEOLUT satisfies the requirements of document C/S T.002 “Cospas-Sarsat LEOLUT Performance Specification and Design Guidelines,” 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 LEOLUT may begin operations in an IOC status. However, the LEOLUT 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 LEOLUT’s IOC status via a System Status message. The IOC phase allows a thorough review of the LEOLUT performance. However a LEOLUT shall not remain in an IOC phase for more than one year. LEOLUTs that have not reached FOC within one year will be considered not operational, and documented as “Under Development”. To regain IOC status the LEOLUT will require a retest of the elements which prevented it from reaching FOC. The LEOLUT then must operate again in an IOC phase prior to reaching FOC. All Cospas-Sarsat Ground Segment Operators should monitor the data from new LEOLUTs 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 LEOLUT, the LEOLUT should be declared at FOC by the appropriate nodal MCC. The transition of a LEOLUT from an IOC status to a FOC status ensures that the LEOLUT performs to Cospas-Sarsat standards and does not negatively impact System operations. 7. Formal Commissioning - The Joint Committee or an EWG established by the Cospas- Sarsat Council for the purpose reviews the commissioning report and, pending additional details or explanations, provides recommendations on approval of the report and the commissioning of the LEOLUT into the Cospas-Sarsat Ground Segment to the Council. The Council approves the recommendation and decides that the LEOLUT is formally commissioned in the Cospas-Sarsat Ground Segment.
G-3
Figure G.1: Overview of LEOLUT Integration -END OF ANNEX G- Any Significant Anomalies? LO Coordinates with Beacon Simulator Providers as Necessary Conform to C/S T.002? LO* Installs LEOLUT Equipment Begin Process to Register LUTs with ITU LO Submit Report to C/S Secretariat Ground Segment Description to C/S Secretariat LO Prepares Required Documentation LO Performs Commissioning Test LO Analyzes Test Results/ Prepare Report LEOLUT Begins Operations at IOC LEOLUT Operator Takes Corrective Action Council Formally Commissions LEOLUT JC or EWG on LUT commissioning Evaluates Report and Recommends NM** Declares LEOLUT at FOC C/S System Monitors for Anomalies Report is submitted for review Yes No Yes No *LO: LEOLUT Operator **NM: Nodal MCC
H-4
ANNEX H GUIDELINES FOR REGISTRATION OF NEW LEOLUTs WITH ITU INSTRUCTIONS FOR FILLING THE FORM OF NOTICE ApS4/III FOR REGISTRATION OF COSPAS-SARSAT LEOLUTs WITH ITU
NOTES:
The form ApS4/III provided at appendix 1 to this Annex is to be completed by each national administration or agency operating Cospas-Sarsat LEOLUTs, for each LUT and each satellite network (i.e. KOSPAS and SAR)3.
Plain characters in the description below reproduce the text of ITU BR Circular Letter CR/65. Comments by the Secretariat are in Italics.
Different information is required for registering GEOLUTs. In particular, GEOLUTs cannot be associated with the KOSPAS and SAR networks as notified to ITU. HEADER4: DATE Date of submission by notifying administration for its own use. Administration serial number Serial/reference number given by the notifying administration for its own use. A1f. NOTIFYING ADMINISTRATION The country symbol designating the notifying administration and the symbol designating the international satellite system, if appropriate. Note that the three letter symbol designating the country is different from the Cospas-Sarsat three letter abbreviation given on the Cospas- Sarsat website www.cospas-sarsat.org. The ITU three letter country symbol is given in Table B1 of the Preface to the International Frequency List (IFL). Cospas-Sarsat has not been declared as an international system and no abbreviation has been assigned, so the second part of this field should not be completed. RR1488 Indicate with a X that this is a Notification. RR1107 and RR1610 To be left blank. RS46 Not applicable to Cospas-Sarsat LEOLUTs. NOTIFICATION INTENDED FOR ADDITION To be indicated with the letter A for a “new” earth station (not previously notified). Letters M or S are to be used for modification or suppression of earth stations previously notified. BR IDENTIFICATION NO. OF STATION TO BE MODIFIED / SUPPRESSED To be used only in case of modification or suppression of earth stations previously notified. SECTION 1: CHARACTERISTICS OF EARTH STATION 3 Note that since Mars 2008, the ITU has made available a PC based data capture software application named Spacecap for the electronic capture of data elements to be furnished in notices relating to space systems and Earth stations. The latest version of the software, dated 28 July 2009, is freely available at the website www.itu.int/ITU- R/software/space/spacecap/index.html. The electronic version of the notice form APS4/III is no longer available but all requirements for submission of an Earth station are spelt out in Annex 2 to Appendix 4 of the Radio Regulations (www.itu.int/publ/R-REG-RR/en). 4 Note that these fields refer to the form ApS4/III, minor adjustments might be required when using the new ITU electronic data capture system (Spacecap).
H-5
A1e1. TYPE Indicate Specific with letter S. A1e2. NAME OF EARTH STATION Enter name of LEOLUT. A1e3a. COUNTRY Indicate the country in which the station is located using the appropriate symbol given in Table No. B1 of the Preface to the IFL or the SRS. In most cases this is the same symbol as in field A1f). A1e3b. GEOGRAPHICAL COORDINATES Specific to the LEOLUT. A4c1. ASSOCIATED SPACE STATION KOSPAS or SAR. A4c2. NOMINAL ORBITAL LONGITUDE Not applicable, leave blank. A7a. HORIZON ELEVATION DIAGRAM Enter the number of the attachment containing the diagram indicating the horizon elevation angle for each azimuth around the station (instructions for presentation of graphical data are given in IFRB circular letter No. 769 of 23 December 1988); or alternatively, fill in the table provided for the values of horizon elevation angle (A7a TABLE OF VALUES FOR THE HORIZON ELEVATION). In this case it is not necessary to fill in values for each 5 or 10 degrees of azimuth; only changes in the horizon elevation angle need be indicated. Thus, for example, if the horizon elevation angle has a constant value of 1.5 degrees between azimuths of 50 and 180 degrees only two entries are required in the table; one for an azimuth of 50 degrees and one for an azimuth of 180 degrees. In addition, if for two consecutive values of azimuth in the table, the horizon elevation angles are different, intermediate values will be calculated by linear interpolation. A7b. ELEVATION ANGLE Enter the planned minimum operating angle of elevation of the antenna on the direction of maximum radiation towards the associated space station, expressed in decimal degrees from the horizontal plane. In the case of Cospas-Sarsat LEOLUTs this elevation angle should be 0.0 degrees or the minimum value (over 0) specified in Table A7a. A7c. OPERATING AZIMUTHAL ANGLES Enter the planned range of operating azimuthal angles for the direction of maximum radiation, each value expressed in decimal degrees clockwise from True North. In the case of Cospas-Sarsat LEOLUTs these values should be 0.0 to 360.0 degrees. A7d. ALTITUDE Enter the height of the centre of the antenna above mean sea level, expressed in metres. This information is specific to each Cospas-Sarsat LEOLUT. A10. COORDINATING AREA DIAGRAMS Not necessary for Cospas-Sarsat LEOLUTs. End of page ApS4/III - 1
H-6
SECTION 2: TRANSMITTING EARTH STATION CHARACTERISTICS Not applicable to Cospas-Sarsat LEOLUTs, pages ApS4/III - 2a and 2b are not to be completed nor forwarded to the ITU. SECTION 3: RECEIVING EARTH STATION CHARACTERISTICS CHARACTERISTICS OF THE ANTENNA B1. ASSOCIATED SATELLITE TRANSMITTING BEAM DESIGNATION Enter the receiving beam designation by a symbol consisting of up to four characters. For Cospas-Sarsat LEOLUTs, enter T1. ADD/MOD/SUP/REP of the antenna Leave blank. OLD BEAM DESIGNATION Leave blank. B5. EARTH STATION ANTENNA CHARACTERISTICS a. MAXIMUM ISOTROPIC GAIN Enter the appropriate sign (+ or -) followed by the isotropic gain (Gi see RR154) of the antenna in the direction of maximum radiation, expressed in dBi. Enter value specific to the LEOLUT antenna, as specified by the manufacturer. For example, Bundaberg LUT was notified as +25.9 dBi, other Cospas-Sarsat LEOLUTs could have figures of about +30.0 dBi. b. BEAMWIDTH Enter the total beamwidth at the mean half-power points of the main lobe, expressed in decimal degrees. Enter value specific to the LEOLUT antenna, as specified by the manufacturer. For example, Bundaberg LUT was notified with 8.00 degrees beamwidth, other Cospas-Sarsat LEOLUTs could have beamwidth of about 5.00 degrees. C1. ANTENNA RADIATION PATTERN DIAGRAM. SEE ATTACHMENT No. If available, enter the attachment number where the measured radiation diagram of the LUT antenna is provided. This is NOT required for Cospas-Sarsat LEOLUTs and, alternatively, the radiation pattern symbol can be entered in c2. C2. RADIATION PATTERN Indicate the reference radiation pattern (from table in BR Circular CR/65 and the Preface to IFL or SRS). Note that if the radiation pattern had been provided as an attachment, then this should be left blank. The symbol AP29 can be used for Cospas-Sarsat LEOLUTs. It refers to Annex 3 to Appendix 29 of the RR (Radiation Patterns for Earth Station Antennae to Be Used When They Are Not Published). FOR NON STANDARD ANTENNA PROVIDE … Leave blank.
H-7
INFORMATION COMMON TO THE FOLLOWING GROUPS (LISTS) OF ASSIGNED FREQUENCIES OF THIS ANTENNA A2a. DATE OF BRINGING INTO USE Enter date of commissioning or expected date of operation (dd/mm/yy). A3a. OPERATING AGENCY OR COMPANY Using symbols from Table No. 12A/12B of the Preface to the IFL or SRS, indicate the operating agency or company and the postal and telegraphic addresses of the administration to which communications should be sent on urgent matters regarding interference, quality of emissions, and questions referring to the technical operation of stations (see Article 22 of the RR). If there is no symbol in Table No. 12A/12B of the Preface corresponding to the administration or agency concerned, spell out the name in box REMARKS with reference to box A3a or A3b as applicable, and the Bureau will provide the symbol. The Preface to the SRS is available in CD form at the Secretariat, information on existing symbols, as recorded for each country in the Preface, can be provided on request. For example, the symbols given in the Preface to the Space Radiocommunications Stations are:
- 005 for INTA, Spain
- 018 for CNES, France
- 003 for National Defence, Algeria
- 027 for Ministry of Transport, London, UK A3b. ADMINISTRATION RESPONSIBLE FOR THE STATION Enter A if the operating agency is an administration, refer to Tables 12A/12B of the Preface otherwise. SPECIAL SECTION AR11/A (RR1042) Enter the number of the Special Section of the Weekly Circular in which the advance information was published under Section I of Article
This box should be left blank and references to advance publications of the satellite networks provided in OTHER SPECIAL SECTIONS (see below). SPECIAL SECTION AR11/C (RR1060) Leave blank. SPECIAL SECTION ART.14 (RR1610) Leave blank. OTHER SPECIAL SECTIONS
- Forms in respect of the KOSPAS network, enter: in column reference, in column number (1) SPA-AA
(2) SPA-AA
- Forms in respect of the SAR network, enter: in column reference, in column number (1) SPA-AA
(2) SPA-AA
A6/A7. COORDINATED WITH OR AGREEMENT REACHED WITH Leave blank.
H-8
A6/A7. COORDINATION REQUESTED WITH OR AGREEMENT SOUGHT WITH Leave blank. REMARKS Leave blank. End of page ApS4/III - 3a SATELLITE TRANSMITTING BEAM DESIGNATION Enter the symbol T1 BR IDENTIFICATION NUMBER OF GROUP (LIST) OF FREQUENCIES TO BE MODIFIED / SUPPRESSED / REPLACED To be used only in case of modification or suppression of group of assigned frequencies previously notified. Leave blank for notification of LEOLUTs not previously registered. ADD / MOD / SUP / REP Enter the symbol A CHARACTERISTICS COMMON TO THE FOLLOWING GROUP (LIST) OF ASSIGNED FREQUENCIES C4a. CLASS OF STATION Indicate the appropriate class of station and the nature of service, using the symbols given in Tables Nos. 6A1 and 6B1 respectively of the Preface to the IFL and the SRS. Up to four pairs of values can be provided For Cospas-Sarsat LEOLUTs, enter the symbols:
- TB which designates aeronautical earth stations,
- TI which designates coast earth stations, C4b. NATURE OF SERVICE For Cospas-Sarsat LEOLUTs, enter the symbols:
- FS i.e. a land station established solely for the safety of life, and
- OT i.e. a station open exclusively to the operational traffic of the service concerned. C6. POLARIZATION Enter the symbol for the type of polarization in the first box (see Table No. 9D1 of the Preface to the IFL and the SRS). For Cospas-Sarsat LEOLUTs, enter the symbol CL which indicates a left-hand circular polarization. Leave the second box (if linear, …) blank. C3a. ASSIGNED FREQUENCY BAND Enter the bandwidth of the assigned frequency band as defined in RR141, expressed in KHz. The assigned frequency band should in no case exceed the bandwidth of a single satellite transponder. Enter the figure 800 (kHz) for Sarsat satellites and 1000 (kHz) for Cospas satellites, or the value specific to the LEOLUT if different.
H-9
C5b. RECEIVING SYSTEM NOISE TEMPERATURE Enter the value of the lowest total receiving noise temperature expressed in kelvins, referred to the output of the earth station antenna under clear sky conditions. This data is specific to the LUT and should be obtained from the LUT manufacturer. EMISSIONS RECEIVED BY THE ASSIGNED FREQUENCIES LISTED BELOW C7a. DESIGNATION OF EMISSION Indicate the necessary bandwidth (RR146) and class of emission (RR133) in accordance with Article 4 and Appendix 6. For the KOSPAS network the registered data for the T1 frequency beam shows 1M00FXX. For the SAR network the registered data for the T1 frequency beam shows 800KFXX. However, the best description of the class of emission received by the LUT is G9D. Therefore, for Cospas-Sarsat LEOLUTs, the designation of emission to be entered is 1M00G9D for Kospas network and 800KG9D for SAR network. C8e. C/N Objective (total - clear sky) Enter the required carrier to noise ratio, in decibels, for the overall link for each carrier when clear sky propagation conditions apply. This data is specific to the LUT and should be obtained from the LUT manufacturer. GROUP (LIST) OF ASSIGNED FREQUENCIES HAVING THE ABOVE COMMON CHARACTERISTICS C2a. ASSIGNED FREQUENCY The value 1544.5 should be entered as shown at Annex 3 with the letter M (for MHz) in the last box. End of page ApS4/III - 3b End of form
H-10
FORM OF NOTICE NOTIFICATION INTENDED FOR A1f. NOTIFYING ADMINISTRATION RR1488 Notification Request for Coordination Agreement under Art.14 Request for Assistance of the BR for and /or FIRST NOTIFICATION RESUBMISSION ADDITION MODIFICATION SUPPRESSION EARTH STATION (APPENDIX S4 - ANNEX 2A) RR1107 RR1107 ApS4/III A1e2. NAME OF THE EARTH STATION A1e3a. COUNTRY A1e3b. GEOGRAPHICAL COORDINATES A4c1. ASSOCIATED SPACE STATION (if geostationary) A4c2. NOMINAL ORBITAL LONGITUDE A7d. ALTITUDE A7c. OPERATING AZIMUTHAL ANGLES RR1610 BR IDENTIFICATION NO. OF STATION TO BE MODIFIED / SUPPRESSED A1e1. TYPE (Specific/Typical) RR1610 DATE (Day/Month/Year) Administration Serial Number
Metres Degrees E/W L o n g i t u d e L a t i t u d e Degrees Min. Sec. Deg. E/W N/S Min. Sec. Form ApS4/III - 1 GENERAL NOTES : different emissions (with associated power and power density values) in this box. If there are more emissions, use another page on the preceding page. In all cases where there is more information than can fit in a box, follow this procedure.
- CHARACTERISTICS OF THE EARTH STATION ii. Data items that are related are grouped together in a box. For example, the page labelled "Form ApS4/III - 2b" (at the bottom) contains a box titled "Emissions common to the assigned frequencies listed below". It is possible to specify 12 of the same type to provide additional data, after checking ( ) the field labelled 'More emissions on next page" iii. This form can be used to add, modify or suppress an existing station, by entering A, M or S in the box at the top right- hand corner of this page in the area titled "Notification intended for". In the case of a modification of an existing station, where certain data fields are to be added, modified or suppressed, provide ALL the data in the particular box as they would look after the change. In addition, indicate that the corresponding antenna or group of frequencies is being modified by entering M or R in the field that has been provided for this purpose at these levels. iv. Certain fields in this notice form have a superscript "1"as part of their labels. This has the following meaning : 1 - This information is not required for the notification of a typical earth station.
Request for Coordination RS 46 PAGE OF A7a. TABLE OF VALUES FOR THE HORIZON ELEVATION AZIMUTH ELEVATION ANGLE Degrees AZIMUTH ELEVATION ANGLE Degrees AZIMUTH ELEVATION ANGLE Degrees AZIMUTH ELEVATION ANGLE Degrees AZIMUTH ELEVATION ANGLE Degrees AZIMUTH ELEVATION ANGLE Degrees
FROM (Degrees) TO (Degrees) A7b. ELEVATION ANGLE
Degrees i. This form of notice consists of three parts - 1, 2, and 3 - as indicated below : 1 - Characteristics of the earth station 2 - Transmitting earth station characteristics and 3 - Receiving earth station characteristics. In each part, each information item/data field includes a number in its label. This number is the same as that used for the same item in Appendix S4 (WRC-95) within the same part. For example, on the page labelled "Form ApS4/III - 2a" (at the bottom), the field "A2a. Date of bringing into use" is the item numbered 2a in Part A of Annex 2A to Appendix S4. A7a. HORIZON ELEVATION DIAGRAM SEE ATTACHMENT NO. A10. COORDINATION AREA DIAGRAMS SEE ATTACHMENT NO. d d m m y y A B C
A S C C B A C N a m e C o f L U T m m m
K O S P A S o R A S r d d d X m m s s s m m X d d s ( To be completed - See Annex I ) Or the code for the location of LEOLUT as identified in the preface to the IFL if different from A1f
H-11
OLD BEAM DESIGNATION (if changed) NOTES ON FILLING IN THE NEXT PAGES: 2. TRANSMITTING EARTH STATION CHARACTERISTICS B1. ASSOCIATED SATELLITE RECEIVING BEAM DESIGNATION b. BEAMWIDTH CHARACTERISTICS OF THE ANTENNA +/- dBi Degrees B5. EARTH STATION ANTENNA CHARACTERISTICS a. MAXIMUM ISOTROPIC GAIN (4) (5) A2a. DATE OF BRINGING INTO USE R R RR Provision R R R R R R OTHER SPECIAL SECTIONS (1) (2) (3) Reference Number A R
1 / A / Number A R
1 / C / Number A R
4 / C / Number SPECIAL SECTION AR11/A (RR1042) SPECIAL SECTION AR11/C (RR1060) SPECIAL SECTION ART.14 (RR1610) Symbols of the Administrations concerned R R R R RR Provision R R R R R R Symbols of the Administrations concerned R R A3b. ADMINISTRATION RESPONSIBLE FOR THE STATION (Refer to Table 12A/12B of the Preface to the IFL & SRS) Day Month Year INFORMATION COMMON TO THE FOLLOWING GROUPS (LISTS) OF ASSIGNED FREQUENCIES OF THIS ANTENNA REMARKS Form ApS4/III - 2a A3a. OPERATING AGENCY OR COMPANY (Refer to Table 12A/12B of the Preface to the IFL & SRS) A6/A7. COORDINATED WITH OR AGREEMENT REACHED WITH A6/A7. COORDINATION REQUESTED WITH OR AGREEMENT SOUGHT WITH of the antenna ADD / MOD / SUP / REP c2. RADIATION PATTERN (give reference pattern or provide diagram) c1. ANTENNA RADIATION PATTERN DIAGRAM. SEE ATTACHMENT NO. NOTE: For a steerable beam, the last character of the beam designation shall be "R" FOR NON-STANDARD ANTENNA PROVIDE: PAGE OF FOR EACH ANTENNA YOU MAY PROVIDE ONE OR MORE GROUPS (LISTS) OF ASSIGNED FREQUENCIES, EACH GROUP (LIST) HAVING ONE SET OF COMMON CHARACTERISTICS. THE BOTTOM HALF OF THIS PAGE CONTAINS COMMON DATA THAT IS APPLICABLE TO ONE OR MORE GROUPS (LISTS) OF FREQUENCIES OF THIS ANTENNA. FOR EACH GROUP (LIST) OF FREQUENCIES OF THIS ANTENNA, FIRST FILL IN THE SET OF COMMON CHARACTERISTICS, FOLLOWED BY THE GROUP (LIST) OF FREQUENCIES TO WHICH THE SET APPLIES. USE AS MANY PAGES AS NECESSARY. Degrees PHI1 dBi Coefficient A dBi Coefficient B dBi Coefficient C dBi Coefficient D Do not send this page to the ITU
H-12
+/- dBW dBW/Hz +/- MORE ON NEXT PAGE C4a. CLASS OF STATION C4b. NATURE OF SERVICE C8a1/C8b1. * MAXIMUM PEAK POWER C8a2/C8b2. * MAXIMUM POWER DENSITY EMISSIONS COMMON TO THE ASSIGNED FREQUENCIES LISTED BELOW GROUP (LIST) OF ASSIGNED FREQUENCIES HAVING THE ABOVE COMMON CHARACTERISTICS C7a. DESIGNATION OF EMISSION Form ApS4/III - 2b CHARACTERISTICS COMMON TO THE FOLLOWING GROUP (LIST) OF ASSIGNED FREQUENCIES k/M/G Hz C2a. ASSIGNED FREQUENCY k/M/G Hz C2a. ASSIGNED FREQUENCY BR IDENTIFICATION NUMBER OF GROUP (LIST) OF FREQUENCIES TO BE MODIFIED / SUPPRESSED / REPLACED PAGE OF of the group ADD / MOD / SUP / REP C6. POLARIZATION TYPE in degrees if linear, provide angle C3a. ASSIGNED FREQUENCY BAND (kHz) C8g. MAXIMUM AGGREGATE POWER dBW +/- +/- dBW C8c1. MINIMUM PEAK POWER dBW/Hz +/- C8c2. MINIMUM POWER DENSITY SATELLITE RECEIVING BEAM DESIGNATION
- If maximum peak power and maximum power density values are of type C8b, check this box Reason for minimum peak power and minimum power density (C8c) values being absent; see attachment No. MORE EMISSIONS ON NEXT PAGE Do not send this page to the ITU
H-13
OLD BEAM DESIGNATION (if changed) NOTES ON FILLING IN THE NEXT PAGES: 3. RECEIVING EARTH STATION CHARACTERISTICS B1. ASSOCIATED SATELLITE TRANSMITTING BEAM DESIGNATION b. BEAMWIDTH CHARACTERISTICS OF THE ANTENNA +/- dBi Degrees B5. EARTH STATION ANTENNA CHARACTERISTICS a. MAXIMUM ISOTROPIC GAIN (4) (5) A2a. DATE OF BRINGING INTO USE R R RR Provision R R R R R R OTHER SPECIAL SECTIONS (1) (2) (3) Reference Number A R
1 / A / Number A R
1 / C / Number A R
4 / C / Number SPECIAL SECTION AR11/A (RR1042) SPECIAL SECTION AR11/C (RR1060) SPECIAL SECTION ART.14 (RR1610) Symbols of the Administrations concerned R R R R RR Provision R R R R R R Symbols of the Administrations concerned R R A3b. ADMINISTRATION RESPONSIBLE FOR THE STATION (Refer to Table 12A/12B of the Preface to the IFL & SRS) Day Month Year INFORMATION COMMON TO THE FOLLOWING GROUPS (LISTS) OF ASSIGNED FREQUENCIES OF THIS ANTENNA REMARKS Form ApS4/III - 3a A3a. OPERATING AGENCY OR COMPANY (Refer to Table 12A/12B of the Preface to the IFL & SRS) A6/A7. COORDINATED WITH OR AGREEMENT REACHED WITH A6/A7. COORDINATION REQUESTED WITH OR AGREEMENT SOUGHT WITH of the antenna ADD / MOD / SUP / REP c2. RADIATION PATTERN (give reference pattern or provide diagram) c1. ANTENNA RADIATION PATTERN DIAGRAM. SEE ATTACHMENT NO. NOTE: For a steerable beam, the last character of the beam designation shall be "R" FOR NON-STANDARD ANTENNA PROVIDE: PAGE OF FOR EACH ANTENNA YOU MAY PROVIDE ONE OR MORE GROUPS (LISTS) OF ASSIGNED FREQUENCIES, EACH GROUP (LIST) HAVING ONE SET OF COMMON CHARACTERISTICS. THE BOTTOM HALF OF THIS PAGE CONTAINS COMMON DATA THAT IS APPLICABLE TO ONE OR MORE GROUPS (LISTS) OF FREQUENCIES OF THIS ANTENNA. FOR EACH GROUP (LIST) OF FREQUENCIES OF THIS ANTENNA, FIRST FILL IN THE SET OF COMMON CHARACTERISTICS, FOLLOWED BY THE GROUP (LIST) OF FREQUENCIES TO WHICH THE SET APPLIES. USE AS MANY PAGES AS NECESSARY. dBi Coefficient A dBi Coefficient B dBi Coefficient C dBi Coefficient D Degrees PHI1
2 9 5
S P A - A A A A A - P S A y y m m d d
P A
T Or 223 and 281 for SAR Not to be completed if antenna radiation pattern diagram has been included with submission
H-14
EMISSIONS RECEIVED BY THE ASSIGNED FREQUENCIES LISTED BELOW MORE ON NEXT PAGE C4a. CLASS OF STATION C4b. NATURE OF SERVICE C5b. RECEIVING SYSTEM NOISE TEMPERATURE C3a. ASSIGNED FREQUENCY BAND CHARACTERISTICS COMMON TO THE FOLLOWING GROUP (LIST) OF ASSIGNED FREQUENCIES C7a. DESIGNATION OF EMISSION GROUP (LIST) OF ASSIGNED FREQUENCIES HAVING THE ABOVE COMMON CHARACTERISTICS Form ApS4/III - 3b C6. POLARIZATION BR IDENTIFICATION NUMBER OF GROUP (LIST) OF FREQUENCIES TO BE MODIFIED / SUPPRESSED / REPLACED PAGE OF of the group ADD / MOD / SUP / REP kelvins (kHz) TYPE SATELLITE TRANSMITTING BEAM DESIGNATION dB C8e. C/N Objective (total - clear sky) if linear, provide angle in degrees k/M/G Hz C2a. ASSIGNED FREQUENCY k/M/G Hz C2a. ASSIGNED FREQUENCY MORE EMISSIONS ON NEXT PAGE -END OF ANNEX H- -END OF DOCUMENT-
T C I T S T O T I T B T B L F
M D
G
M 1000 for Kospas and 800 for SAR Or 800KG9D for SAR F S O T
H-15
page left blank
Cospas-Sarsat Secretariat 1250 René-Lévesque Blvd. West, Suite 4215, Montreal (Quebec) H3B 4W8 Canada Telephone: +1 514 500 7999 Fax: +1 514 500 7996 Email: mail@cospas-sarsat.int Website: http://www.cospas-sarsat.int