Publication: Magyar Közlöny
Issue: MK-2007-70 (Year: 2007, Number: 70)
Era: 2004-2010
Section: Melléklet a 2007. évi XLVI. törvényhez
Paragraph Index: 4460

b) there is a TIS “keep-alive” time-out on the PI. In either case, the AI (if one is present) shall be promoted to PI and its TIS messages shall now be displayed. A new AI shall now be identified. If there was no available AI, no PI is now available and the airborne TIS processor shall be in the “no TIS supported” state. This state shall continue until a TIS message (either traffic or keep-alive) is received from a Mode S ground interrogator. When such an uplink message is received, the II code contained in the message shall become the PI and the airborne processing shall resume the display of TIS. The PI definition shall be initialized to the “none” state when TIS is enabled (TSCR) or disabled (TSDR) by the pilot. 3.2.3 UPLINK MSP CHANNEL 3 (Reserved for ground-to-air alert) The description of this channel has not yet been developed. 3.2.4 UPLINK MSP CHANNEL 4 (Reserved for ground-derived position) The description of this channel has not yet been developed. 3.2.5 UPLINK MSP CHANNEL 5 (ACAS sensitivity level control) The description of this channel has not yet been developed. 3.2.6 UPLINK MSP CHANNEL 6 (Ground-to-air request) 3.2.6.1 PURPOSE This service shall provide a means of requesting access to services supported by the aircraft. When implemented, bit 6 of the register accessed by BDS code 1,D shall be set to a 1. 3.2.6.2 FORMAT The request shall be transferred in an uplink MSP packet with the channel number set to 6 and, in the case of a long form MSP packet, with SP set to “ZERO”. The first byte of the user data field shall contain a service request (SR) header. The contents and format of the service request are specified by the application. 3.2.6.3 SR HEADER ASSIGNMENTS Decimal value of SR Unassigned Dataflash Local system management 3 to 255 Unassigned 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-139 28/11/02 No. 77 3.2.6.3.1 Dataflash 3.2.6.3.1.1 Dataflash request format The format of the user data field shall be as specified in Table 3-1. The user data field of the requesting MSP packet shall contain the decimal value of “ONE” in the first byte (SR header), followed by one or more requests for dataflash services. Each request shall contain a 2-byte dataflash request header (DH), followed by a 1-byte field to define the minimum time interval permitted between reports (MT field), a 4-bit field to determine the event criterion (EC field), a 4-bit field to determine stable time (ST field), and if indicated in EC, a change quanta field (CQ) and a change threshold (CT) field. The 4-bit ST field shall indicate the decimal value in seconds and how long the changed data has been stable before a message shall be initiated. All zeros in the dataflash header (DH) shall indicate that there are no more dataflash requests in the packet. When an MSP packet is completely filled with dataflash requests, or when there is not sufficient room in the packet for another dataflash request header, it shall be assumed that the dataflash request sequence is complete. 3.2.6.3.1.1.1 All aircraft dataflash equipment and installations shall support 16 dataflash contracts. Aircraft equipment and installations originally certified after 1 January 2001 shall support 64 dataflash contracts. Note 1.— A single dataflash contract relates to a single contract number (see 3.2.6.3.1.2.1) for a single register for a particular II code. Therefore, dataflash services, with different DH values for each II code, can be established simultaneously with the same aircraft. These may be modified or discontinued independently of each other. 3.2.6.3.1.1.2 Recommendation.— When a request has been accepted by the aircraft system, a dataflash response should be triggered immediately regardless of thresholds or event criteria. If no response is received in 30 seconds then a check should be made that the aircraft is still available on roll call, and if so a new request should be generated. In order to avoid repeated dataflash requests that produce no response, the number of such requests (N) should be limited (N = 3). 3.2.6.3.1.1.3 When a new contract request is received for a contract already in existence, the old contract shall be discontinued and replaced immediately by the latest one. 3.2.6.3.1.2 Dataflash header (DH) 16 bits The 16-bit DH field is divided into four subfields separated by 3 reserved bits (14 through 16) see Table 3-1. 3.2.6.3.1.2.1 Contract number subfield (CNS) 4 bits (Bits 9 to 12 of the uplink MSP 6 user data field when SR = 1) This subfield shall be interpreted as a contract number permitting 16 different contracts to be associated with the register specified by the BDS1 and BDS2 codes of this contract request. Contract numbers available are 0 to 15 and shall be associated with the II code of the contract request. 3.2.6.3.1.2.2 Request data subfield (RDS) 1 bit (Bit 13 of the uplink MSP 6 user data field when SR = 1 This subfield shall indicate whether or not the contents of the register being monitored by the requested contract must be sent in the MSP packets on downlink channel 3 that are sent each time the criterion for the contract is met. The subfield shall be interpreted as follows: RDS = 0 Send only bits 1 to 40 of the user data field on downlink MSP 3 when the contract criterion is met. RDS = 1 Send bits 1 to 96 of the user data field on downlink MSP 3 when the contract criterion is met. Note.— RDS only indicates the length of the user data field in downlink MSP3 when responding with a value zero in the CI field (see 3.3.3.4.3.1). 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-140 28/11/02 No. 77 3.2.6.3.1.2.3 BDS1 and BDS2 codes 8 bits (Bits 17 to 24 of the uplink MSP6 user data field) BDS1 and BDS2 codes of the register for which the contract is required shall be as specified in Annex 10, Volume IV. 3.2.6.3.1.3 Minimum time (MT) 8 bits The decimal value of the 8-bit MT field shall represent the minimum time in seconds that shall elapse after a report has been eventtriggered and sent to the transponder, before a new report can be initiated. The report sent to the transponder shall always be the most current data available. 3.2.6.3.1.4 Event initiation Event initiation shall be controlled by the two following fields. 3.2.6.3.1.4.1 Event criterion subfield (EC) 4 bits The EC field shall be the four most significant bits following the MT field. If multiple events occur within a single register being monitored by a dataflash contract, (e.g. if more than one parameter shows a significant change) only one message shall be triggered. The decimal value of the EC field shall be interpreted as follows: No report required, discontinue service for the contract specified in the DH field. Report any change. 56-bit change field (CQ) follows ST. Only report changes to bits indicated by a “ONE” in CQ. 56-bit field CQ follows ST. For each parameter report all status changes and all changes of the parameter greater than the quantum value indicated in the same units and resolution of the field in CQ corresponding to that parameter. A zero in the field in CQ corresponding to the parameter indicates that no reports are required. 112 bits of CQ plus CT follow ST. The first 56 bits are as for the EC value 3 above. The second 56 bits are the CT field indicating a threshold value in the field corresponding to the parameter. Report all changes above the threshold where the value in CQ gives the change quantum. 112 bits of CQ plus CT follow ST. Same as for the EC value 4 above except: report all changes below the threshold. 112 bits of CQ plus CT follows ST. Same as for EC values 4 and 5 above except: report only when the threshold is crossed (in either direction). 7 to 14 Not assigned Cancel all contracts for the II code in this request. 3.2.6.3.1.4.2 Stable time field (ST) 4 bits The ST field shall be the 4 bits following the EC field. The decimal value of ST shall indicate in seconds how long the changed data have been stable, to within the change quanta specified in the CQ field, before a message shall be initiated. A value of “ZERO” in this subfield shall indicate that there is no minimum stable time and any change immediately initiates a message. The significance of the ST shall be dependent on which EC mode is being used. For EC modes 4 and 5, regarding stability whilst above/below a threshold, if a parameter value remains above/below the defined threshold for greater than the ST time then a dataflash message shall be generated even if the value does not remain stable to within one quantum. Subsequent quantum changes which are stable for greater than the ST time shall generate further dataflash messages until the value falls below/rises above the threshold. 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-141 28/11/02 No. 77 3.2.6.3.1.5 Change fields — change quanta (CQ) and change threshold (CT) These fields shall be present when indicated in EC. For a transponder register service (i.e. for BDS1 and BDS2 from 1 to 255 inclusive), CQ shall be contained in bits 41 to 96 of the MSP 6 user data field. CT, when required, shall be contained in bits 97 to 152 of the MSP 6 user data field. The quantum value in the CQ field shall be indicated in the same units and resolution as those specified for the register being monitored. It shall specify the amount by which the parameter must change, from its value at the initialization of the contract, and thereafter from the value last reported by a dataflash response, in order to trigger a new dataflash response on downlink MSP channel 3 (see Table 3-1). 3.2.6.3.2 Local system management The purpose of the local system management is to provide a particular ground-air service request that can be defined locally to meet particular requirements (such as for ground station “remote setting” of parameters at the far-field monitor). 3.2.7 UPLINK MSP CHANNEL 7 (Reserved for response to air-to-ground service request) The description of this channel has not yet been developed. 3.2.8 UPLINK MSP CHANNEL 8 (Reserved for trajectory negotiation) The description of this channel has not yet been developed. 3.2.9 UPLINK MSP CHANNELS 9 TO 63 These channels have not been assigned. 3.3 DOWNLINK MSP CHANNELS The following sections are numbered 3.3.X, where “X” is the decimal number equivalent to the downlink MSP channel number. This is done to allow definitions of the hitherto undefined formats to be inserted without affecting paragraph numbers. 3.3.1 DOWNLINK MSP CHANNEL 1 (Reserved for specific services management) The description of this channel has not yet been developed. 3.3.2 DOWNLINK MSP CHANNEL 2 This channel has not been assigned. 3.3.3 DOWNLINK MSP CHANNEL 3 3.3.3.1 PURPOSE Dataflash is a service which announces the availability of information from air-to-ground on an event-triggered basis. When implemented, bit 31 of the register accessed by BDS code 1,D shall be set to a 1. 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-142 28/11/02 No. 77 Note.— This is an efficient means of downlinking information which changes occasionally and unpredictably. 3.3.3.2 SERVICE INITIATION AND TERMINATION 3.3.3.2.1 The dataflash service shall be initiated or discontinued by a service request and is received on uplink MSP channel 6 with a decimal value of ONE in the service request (SR) header, which is contained in the first byte of the user data field. This indicates that the rest of the user data field shall contain a dataflash request. On the receipt of such a request, a dataflash message from the register concerned with the request shall immediately be made available and announced to the ground regardless of the setting of the RDS field in the contract request and of any event criteria. The response shall be as follows. 3.3.3.2.2 When the requested register is being serviced, the contract shall be established and an MSP packet as specified in Table 3-2 shall be announced to the ground on MSP channel 3. The CI field must be set to a value of 1. The message shall be used by the ground system to confirm that the service has been initiated. 3.3.3.2.3 If the requested register is not being serviced, the contract shall not be established. This shall be indicated by announcing the MSP packet on downlink MSP channel 3 to the ground containing only bits 1 to 40 as specified in Table 3-2, and with a value of 2 in the CI field. 3.3.3.2.4 If the maximum number of contracts that can be supported are already established, then the new contract shall be refused. This shall be indicated by announcing to the ground an MSP packet on downlink channel 3, as specified in Table 3-2, and with a value of 3 in the CI field. 3.3.3.2.5 In the case of a request from the ground to terminate the service for a particular register, the termination of the service shall be confirmed by announcing to the ground an MSP packet on downlink channel 3, as shown in Table 3-2, and with a value of 4 in the CI field. 3.3.3.2.6 In the case of a request from the ground to terminate the service for all contracts to a particular II code, the termination of the service shall be confirmed by announcing to the ground an MSP packet on downlink channel 3, as shown in Table 3-2, and with a value of 5 in the CI field. 3.3.3.2.7 When the transponder register service fails for an established contract, the contract shall be terminated by the airborne application. This will be indicated by announcing to the ground an MSP packet on the downlink channel 3, as shown in Table 3-2, and with a value of 7 in the CI field. Transponder register service shall be deemed to have failed when any of the parameters specified to be monitored in the negotiation of the contract are not being updated at the specified minimum rate. 3.3.3.2.8 When a contract is refused due to an invalid value of the EC field in the contract request, this shall be indicated by announcing to the ground an MSP packet on downlink channel 3, as shown in Table 3-2, and with a value of 15 in the CI field. 3.3.3.2.9 If any message is not extracted from the transponder by a ground interrogator within 30 seconds, the aircraft subnetwork shall cancel the message and generate a delivery failure notice (i.e. the TZ timer expires), which shall be delivered to the aircraft MSP service provider. When a delivery failure notice is received the service shall be automatically terminated by the dataflash function with no indication to the ground system. Note.— This is to prevent the transponder message queues being blocked when the ground interrogator stops supplying the message extraction service, either due to a fault or loss of cover. It is the responsibility of the ground application to monitor the dataflash service taking this into account. 3.3.3.2.10 When the transponder has not been selectively interrogated by a Mode S interrogator with a particular II code for 60 seconds (determined by monitoring the IIS subfield in all accepted Mode S interrogations), all dataflash contracts related to that II code shall be cancelled with no indication to the ground system. 3.3.3.3 SERVICE PROVISION On the receipt of a dataflash request, the requested parameters shall be monitored and transferred to the ground using the Mode S air-initiated protocols directed to the II code that was contained in the requesting interrogation. In order to prevent the flooding of the transponder with dataflash messages, an upper limit of ten messages in a six-second period shall be imposed. When the limit of ten messages within a six-second period is reached, further messages shall be queued until they can be sent. Messages queued 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-143 28/11/02 No. 77 in this way shall respond with a CI field value of 6. If after initiating a dataflash message to the ground, the change criterion is met again prior to the message being entered into the transponder for announcement, the message is considered stale and shall be replaced by the most up-to-date information. 3.3.3.4 DOWNLINK MESSAGE STRUCTURE The information shall be transferred in a downlink MSP packet with the channel number M/CH = 3. The format is shown in Table 3-2. The first two bytes of the user data (UD) field shall contain a dataflash header (DH) which shall be identical to the DH field that was contained in the request for service. 3.3.3.4.1 Bits 17 to 31 of UD form the II code contract report (CR) field in which each bit shall indicate that at least one contract is active with the II code, which the bit represents when it is set to a ONE; otherwise, there are no active contracts with that II code. 3.3.3.4.2 Bits 32 to 36 of UD are not assigned. 3.3.3.4.3 Bits 37 to 40 of UD form the contract information (CI) field which shall be interpreted as follows: 3.3.3.4.3.1 When the CI field is equal to zero, the response shall be as requested by the RDS field in the dataflash header of the contract (see 3.2.6.3.1.2.2). When the CI field is not equal to zero, the response shall only contain bits 1 to 40 of the user data field on downlink MSP 3 (see Table 3-2). 3.3.3.5 DATA EXTRACTION BY MODE S GROUND STATIONS The dataflash transaction shall be announced as a downlink frame in response to interrogations UF 4, 5, 20, or 21. The transaction announced shall be either a single segment Comm-B frame or a two segment Comm-B frame, as requested by the contract negotiations. The air-directed Comm-B first segment shall contain the MSP header, dataflash header, and control information for that particular contract. In the case of a contract for a single segment response, if the data is required, it is acquired directly by the ground station extracting the register in question. 3.3.4 DOWNLINK MSP CHANNEL 4 (Reserved for position request) The description of this channel has not yet been developed. CI field value Meaning Response to existing contract New contract established New contract not accepted, or existing contract terminated, due to no transponder register data service New contract not accepted due to maximum number of contracts already being serviced Contract terminated for the DH in this response due to a request from the ground All contracts terminated for the II code that delivered the MSP packet having an EC value of 15 that requested this response Response has been queued due to the limit of six dataflash messages in a ten-second period Contract terminated due to failure of the register data service 8 to 14 Unassigned New contract not accepted due to invalid number in EC field of requested uplink MSP packet 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-144 28/11/02 No. 77 3.3.5 DOWNLINK MSP CHANNEL 5 This channel has not been assigned. 3.3.6 DOWNLINK MSP CHANNEL 6 (Reserved for response to ground-to-air service request.) (See Table 3-3.) The first byte of the user data (UD) field in the downlink MSP channel 6 shall be used to define a response type (RT) field as follows: RT = 0 Unassigned RT = 1 (Reserved) RT = 2 Local system management RT = 3 to 255 Unassigned When implemented, bit 34 of register 1D16 is set to a 1. Note.— The response to a ground-air service request can be used to transfer information resulting from such a service. 3.3.7 DOWNLINK MSP CHANNEL 7 (Reserved for air-to-ground request) The description of this channel has not yet been developed. 3.3.8 DOWNLINK MSP CHANNEL 8 (Reserved for trajectory negotiation) The description of this channel has not yet been developed. 3.3.9 DOWNLINK MSP CHANNELS 9 TO 63 These channels have not been assigned. 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-145 28/11/02 No. 77 TABLES FOR SECTION 3 Table 3-1. Request for dataflash monitoring service Mode S SLM frame containing uplink MSP packet on channel 6 when SR = 1 MSP 6 USER DATA FIELD Bits 1 to 40 Bits 41 to 96 (if required) Bits 97 to 152 (if required) DP = 0 (1 BIT) UPLINK MSP HEADER (1 BYTE) MP = 0 (1 BIT) M/CH = 6 (6 BITS) SERVICE REQUEST (SR) = 1 CONTRACT DATAFLASH HEADER (DH) NUMBER SUBFIELD (CNS) CHANGE QUANTA FIELD (CQ) CHANGE REQUEST DATA (RDS) THRESHOLD FIELD (CT) RESERVED BDS1 CODE BDS2 CODE MINIMUM TIME (MT) INTERVAL LSB = 1 second EVENT CRITERION (EC) STABLE TIME (ST) LSB = 1 second The last byte of the final MA field shall always be unassigned. 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-146 28/11/02 No. 77 Table 3-2. Dataflash for register monitoring service Mode S frame containing downlink MSP packet on Channel 3 MSP 3 USER DATA FIELD Bits 1 to 40 Bits 41 to 96 LINKED COMM B SUBFIELD (LBS) (2 BITS) DP = 0 (1 BIT) MP = 0 (1 BIT) See 5.2.7.3 for specification of M/CH = 3 (6 BITS) MSP packets MSP HEADER FILL 1 = 0 (6 BITS) CONTRACT NUMBER SUBFIELD (CNS) REQUEST DATA (RDS) RESERVED DATAFLASH REGISTER HEADER (DH) MESSAGE BDS1 CONTENT CODE BDS2 CODE II = 1 II = 2 II = 3 II = 4 II = 5 II = 6 II = 7 II CODE II = 8 CONTRACT II = 9 REPORT (CR) II = 10 II = 11 II = 12 II = 13 II = 14 II = 15 NOT ASSIGNED CONTRACT INFORMATION (CI) 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-147 28/11/02 No. 77 Table 3-3. Response to ground-to-air service request Mode S frame containing downlink MSP packet on channel 6 MSP 6 USER DATA FIELD Bits 1 to 40 Bits 41 to 96 LINKED COMM B SUBFIELD (LBS) (2 BITS) This packet shall always be sent as a linked Comm-B. The second segment being a direct copy of the relevant register. DP = 0 (1 BIT) MP = 0 (1 BIT) M/CH = 6 (6 BITS) MSP HEADER FILL 1 = 0 (6 BITS) REGISTER MESSAGE CONTENT RESPONSE TYPE USER DEFINED 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-148 28/11/02 No. 77 4. MODE S BROADCAST PROTOCOLS 4.1 BROADCAST CHANNEL NUMBER ALLOCATIONS The broadcast identifiers shall be represented as a two-digit hexadecimal number, e.g. “XX16” Note.— There are 255 broadcast identifiers available on both the uplink and downlink. Broadcast identifier numbers have been assigned for some applications (see Chapter 5, Table 5-23). The data formats for the data link capability report and for aircraft identification together with the assignment of the broadcast identifiers shall be as defined in Annex 10, Volumes III and IV, respectively. 4.2 UPLINK BROADCAST IDENTIFIERS The following sections are numbered 4.2.X, where “X” is the decimal equivalent of the uplink broadcast identifier number. This is done to allow definitions of the hitherto undefined formats to be inserted without affecting the paragraph numbering. 4.2.1 UPLINK BROADCAST IDENTIFIER 0116 (Reserved for differential GNSS correction) The description of this identifier has not yet been developed. 4.2.2 TO 4.2.47 UPLINK BROADCAST IDENTIFIERS 0216 to 2F16 These identifiers have not been assigned. 4.2.48 UPLINK BROADCAST IDENTIFIER 3016 (Not valid) 4.2.49 UPLINK BROADCAST IDENTIFIERS 3116 (Reserved for RA broadcast (see Annex 10, Volume IV, 4.3.8.4.2.3.4)). 4.2.50 UPLINK BROADCAST IDENTIFIERS 3216 (Reserved for ACAS (see Annex 10, Volume IV, 4.3.8.4.2.3.3)). 4.2.51 TO 4.2.255 UPLINK BROADCAST IDENTIFIERS 3316 to FF16 These identifiers have not been assigned. 4.3 DOWNLINK BROADCAST IDENTIFIER The following sections are numbered 4.3.X, where “X” is the decimal equivalent of the downlink broadcast identifier number. This is done to allow definitions of the hitherto undefined formats to be inserted without affecting the paragraph numbering. 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-149 28/11/02 No. 77 4.3.1 DOWNLINK BROADCAST IDENTIFIER 0116 This identifier has not been assigned. 4.3.2 DOWNLINK BROADCAST IDENTIFIER 0216 (Traffic information service) 4.3.2.1 INTRODUCTION The traffic information service shall be provided by uplinking information on proximate aircraft that may be of interest to own-aircraft by a Mode S interrogator on uplink MSP channel 2. Note.— The service and uplink messages are specified in 3.2.2 under “Uplink MSP Channel 2”. It shall be possible for the aircraft to request to be either connected to or disconnected from the TIS service. These requests shall be made using the Mode S broadcast protocol using broadcast identifier 0216. These requests shall be the only downlink messages used by the TIS. 4.3.2.2 TIS DOWNLINK MESSAGES The TIS airborne data link service shall be able to generate two types of Mode S downlink messages:

Source: https://magyarkozlony.hu/hivatalos-lapok/7e70cec03f34e3c2efd8610b865b65591eafd701/dokumentumok/a55dc160549d57fa4db0035e37c6a6a98dd1a0b9/letoltes