Publication: Magyar Közlöny
Issue: MK-2009-104 (Year: 2009, Number: 104)
Era: 2004-2010
Section: 
Paragraph Index: 1878

c) the Tq timer associated with any released packets shall be stopped. 5.2.7 Mode S specific services processing Mode S specific services shall be processed by an entity in the XDLP termed the Mode S specific services entity (SSE). Transponder registers shall be used to convey the information specified in Table 5-24. The data structuring of the registers in Table 5-24 shall be implemented in such a way that interoperability is ensured. Note 1.— The data formats and protocols for messages transferred via Mode S specific services are specified in the Technical Provisions for Mode S Services and Extended Squitter (Doc 9871) (in preparation). Note 2.— Uniform implementation of the data formats and protocols for messages transferred via Mode S specific services will ensure interoperability. Note 3.— This section describes the processing of control and message data received from the Mode S specific services interface. Note 4.— Control data consists of information permitting the determination of, for example, message length, BDS code used to access the data format for a particular register, and aircraft address. 5.2.7.1 ADLP PROCESSING 5.2.7.1.1 DOWNLINK PROCESSING 5.2.7.1.1.1 Specific services capability. The ADLP shall be capable of receiving control and message data from the Mode S specific services interface(s) and sending delivery notices to this interface. The control data shall be processed to determine the protocol type and the length of the message data. When the message or control data provided at this interface are erroneous (i.e. incomplete, invalid or inconsistent), the ADLP shall discard the message and deliver an error report at the interface. Note.— The diagnostic content and error reporting mechanism are a local issue. 5.2.7.1.1.2 Broadcast processing. The control and message data shall be used to format the Comm-B broadcast message as specified in 5.2.7.5 and transferred to the transponder. 5.2.7.1.1.3 GICB processing. The 8-bit BDS code shall be determined from the control data. The 7-byte register content shall be extracted from the received message data. The register content shall be transferred to the transponder, along with an indication of the specified register number. A request to address one of the air-initiated Comm-B registers or the airborne collision avoidance system (ACAS) active resolution advisories register shall be discarded. The assignment of registers shall be as specified in Table 5-24. Note.— Provision of the data available in transponder registers 40, 50 and 60 {HEX} has been mandated in some ICAO Regions in support of ATM applications. 5.2.7.1.1.4 MSP processing 5.2.7.1.1.4.1 The MSP message length, channel number (M/CH) (5.2.7.3.1.3) and optionally the interrogator identifier (II) code shall be determined from the control data. The MSP message content shall be extracted from the received Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-38 message data. If the message length is 26 bytes or less, the SSE shall format an air-initiated Comm-B message (5.2.7.1.1.4.2) for transfer to the transponder using the short form MSP packet (5.2.7.3.1). If the message length is 27 to 159 bytes and the transponder has adequate downlink ELM capability, the SSE shall format an ELM message for transfer using the short form MSP packet. If the message length is 27 to 159 bytes and the transponder has a limited downlink ELM capability, the SSE shall format multiple long form MSP packets (5.2.7.3.2) using ELM messages, as required utilizing the L-bit and M/SN fields for association of the packets. If the message length is 27 to 159 bytes and the transponder does not have downlink ELM capability, the SSE shall format multiple long form MSP packets (5.2.7.3.2) using air initiated Comm-B messages, as required utilizing the L-bit and M/SN fields for association of the packets. Different frame types shall never be used in the delivery of an MSP message. Messages longer than 159 bytes shall be discarded. The assignment of downlink MSP channel numbers shall be as specified in Table 5-25. 5.2.7.1.1.4.2 For an MSP, a request to send a packet shall cause the packet to be multisite-directed to the interrogator which II code is specified in control data. If no II code is specified, the packet shall be downlinked using the air-initiated protocol. A message delivery notice for this packet shall be provided to the Mode S specific interface when the corresponding close-out(s) have been received from the transponder. If a close-out has not been received from the transponder in Tz seconds, as specified in Table 5-1, the MSP packet shall be discarded. This shall include the cancellation in the transponder of any frames associated with this packet. A delivery failure notice for this message shall be provided to the Mode S specific services interface. 5.2.7.1.2 UPLINK PROCESSING Note.— This section describes the processing of Mode S specific services messages received from the transponder. 5.2.7.1.2.1 Specific services capability. The ADLP shall be capable of receiving Mode S specific services messages from the transponder via frame processing. The ADLP shall be capable of delivering the messages and the associated control data at the specific services interface. When the resources allocated at this interface are insufficient to accommodate the output data, the ADLP shall discard the message and deliver an error report at this interface. Note.— The diagnostic content and the error reporting mechanism are a local issue. 5.2.7.1.2.2 Broadcast processing. If the received message is a broadcast Comm-A, as indicated by control data received over the transponder/ADLP interface, the broadcast ID and user data (5.2.7.5) shall be forwarded to the Mode S specific services interface (5.2.3.2.1) along with the control data that identifies this as a broadcast message. The assignment of uplink broadcast identifier numbers shall be as specified in Table 5-23. 5.2.7.1.2.3 MSP processing. If the received message is an MSP, as indicated by the packet format header (5.2.7.3), the user data field of the received MSP packet shall be forwarded to the Mode S specific services interface (5.2.3.2.1) together with the MSP channel number (M/CH), the IIS subfield (5.2.2.1.1.1) together with control data that identifies this as an MSP message. L-bit processing shall be performed as specified in 5.2.7.4. The assignment of uplink MSP channel numbers shall be as specified in Table 5-25. 5.2.7.2 GDLP PROCESSING 5.2.7.2.1 UPLINK PROCESSING 5.2.7.2.1.1 Specific services capability. The GDLP shall be capable of receiving control and message data from the Mode S specific services interface(s) (5.2.3.2.2) and sending delivery notices to the interface(s). The control data shall be processed to determine the protocol type and the length of the message data. 5.2.7.2.1.2 Broadcast processing. The GDLP shall determine the interrogator(s), broadcast azimuths and scan times from the control data and format the broadcast message for transfer to the interrogator(s) as specified in 5.2.7.5. Part I Annex 10 — Aeronautical Communications I-5-39 22/11/07 5.2.7.2.1.3 GICB processing. The GDLP shall determine the register number and the aircraft address from the control data. The aircraft address and BDS code shall be passed to the interrogator as a request for a ground-initiated Comm-B. 5.2.7.2.1.4 MSP processing. The GDLP shall extract from the control data the message length, the MSP channel number (M/CH) and the aircraft address, and obtain the message content from the message data. If the message length is 27 bytes or less, the SSE shall format a Comm-A message for transfer to the interrogator using the short form MSP packet (5.2.7.3.1). If the message length is 28 to 151 bytes and the transponder has uplink ELM capability, the SSE shall format an ELM message for transfer to the interrogator using the short form MSP packet. If the message length is 28 to 151 bytes and the transponder does not have uplink ELM capability, the SSE shall format multiple long form MSP packets (5.2.7.3.2) utilizing the L-bit and the M/SN fields for association of the packets. Messages longer than 151 bytes shall be discarded. The interrogator shall provide a delivery notice to the Mode S specific services interface(s) indicating successful or unsuccessful delivery, for each uplinked packet. 5.2.7.2.2 DOWNLINK PROCESSING 5.2.7.2.2.1 Specific services capability. The GDLP shall be capable of receiving Mode S specific services messages from the interrogator via frame processing. 5.2.7.2.2.2 Broadcast processing. If the received message is a broadcast Comm-B, as indicated by the interrogator/GDLP interface, the GDLP shall:

Source: https://magyarkozlony.hu/hivatalos-lapok/bfd0d67db9f223889f627fd618725b03526630e2/dokumentumok/d5234fd7275da04023366ab8a434989962a31bdf/letoltes