曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

intended to prevent the output of misleading information under unintentional interference scenarios that could arise. It is not
intended to specifically address intentional interference. While it is impossible to completely verify this requirement through
testing, an acceptable means of compliance can be found in the appropriate receiver Minimum Operational Performance
Standards published by RTCA and EUROCAE.
11. Recording of GNSS parameters
11.1 In order to be able to conduct post-incident/accident investigations (Chapter 2, 2.4.3), it is necessary to record
GNSS information both for the augmentation system and for the appropriate GNSS core system constellation used for the
operation. The parameters to be recorded are dependent on the type of operation, augmentation system and core elements
used. All parameters available to users within a given service area should be recorded at representative locations in the
service area.
11.2 The objective is not to provide independent assurance that the GNSS is functioning correctly, nor is it to provide
another level of system monitoring for anomalous performance or input data for a NOTAM process. The recording system
need not be independent of the GNSS service and may be delegated to other States or entities. In order to enable future
reconstruction of position, velocity and time indications provided by specific GNSS configurations, it is recommended to log
data continuously, generally at a 1 Hz rate.
11.3 For GNSS core systems the following monitored items should be recorded for all satellites in view:
a) observed satellite carrier-to-noise density (C/N0);
b) observed satellite raw pseudo-range code and carrier phase measurements;
c) broadcast satellite navigation messages, for all satellites in view; and
d) relevant recording receiver status information.
11.4 For SBAS the following monitored items should be recorded for all geostationary satellites in view in addition to
the GNSS core system monitored items listed above:
a) observed geostationary satellite carrier-to-noise density (C/N0);
b) observed geostationary satellite raw pseudo-range code and carrier phase measurements;
23/11/06 ATT D-50
Attachment D Annex 10 — Aeronautical Communications
c) broadcast SBAS data messages; and
d) relevant receiver status information.
11.5 For GBAS the following monitored items should be recorded in addition to the GNSS core system and SBAS
monitored items listed above (where appropriate):
a) VDB power level;
b) VDB status information; and
c) broadcast GBAS data messages.
12. GNSS performance assessment
The data described in Section 11 may also support periodic confirmation of GNSS performance in the service area.
13. GNSS and database
Note.— Provisions relating to aeronautical data are contained in Annex 11, Chapter 2, and Annex 15, Chapter 3.
13.1 The database is to be current with respect to the effective AIRAC cycle, which generally means that a current
database be loaded into the system approximately every 28 days. Operating with out-of-date navigation databases has to be
avoided.
13.2 In certain situations, operations using an expired database can be conducted safely by implementing a process
and/or using procedures to ensure that the required data is correct. These processes and/or procedures need prior approval by
the State.
13.2.1 These procedures should be based on one of the following methods:
a) require the crew to check, prior to the operation, critical database information against current published information.
(This method increases workload and would not be practical for all applications.); or
b) waive the requirement for a current database and frequent checks by the crew of the database information. This
waiver can only be applied to very specific cases where aircraft are operated in a strictly limited geographical area
and where that area is controlled by a single regulatory agency or multiple agencies that coordinate this process; or
c) use another approved method that ensures an equivalent level of safety.
14. Modelling of residual errors
14.1 Application of the integrity requirements for SBAS and GBAS requires that a model distribution be used to
characterize the error characteristics in the pseudo-range. The HPL/LPL and VPL models (see 7.5.3) are constructed based on
models of the individual error components (in the pseudo-range domain) that are independent, zero-mean, normal
distributions. The relationship between this model and the true error distribution must be defined.
ATT D-51 23/11/06
Annex 10 — Aeronautical Communications Volume I
14.2 One method of ensuring that the protection level risk requirements are met is to define the model variance (σ2),
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：附件10--航空電信an10_v1_6ed下(109)