Data handover method and system for itwr system and atc system

Abstract

The embodiment of the application discloses a data handover method and system of an iTWR system and an ATC system.The method comprises the following steps: the iTWR system initiates a handover step, the iTWR system sends a handover message containing a take-off runway number to the ATC system, the ATC system receives the handover step, the ATC system receives the handover message, identifies an approach sector code in the ATC system according to the handover message, and completes data handover of the iTWR system to the ATC system according to the approach sector code.The above technical scheme of the application provides a new bidirectional data handover receiving mode between the iTWR system and the ATC system, that is, the handover is performed according to the take-off / landing runway number, so that the accuracy of handover and receiving between the two systems can be ensured; and the iTWR system and the ATC system do not need to additionally agree to configure the same approach / tower sector code, so that the configuration flexibility and functional expansibility of the respective systems are improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of air traffic management system data processing, and particularly relates to a data handover method and system for iTWR system and ATC system. BACKGROUND

[0002] An air traffic control automation system (ATC system for short) is a core system for implementing air command by an air traffic control department, and provides air traffic controllers with display of air flight situation and various flight conflicts and various abnormal alarms, and provides air traffic controllers with flight plan dynamic related information and an integrated system of control means by processing flight plans and dynamic telegrams.

[0003] A tower control automation system (iTWR system for short) is a control command system suitable for the tower department of an air traffic control department, and integrates functions of multiple systems required by tower control, such as air traffic control automation, advanced field activity guidance, tower electronic progress sheet, digital air traffic control, collaborative release, weather and light control, and can provide tower controllers with highly informationized and intelligent new-generation tower control command systems for air, field situation display and various flight and field conflict alarms.

[0004] The ATC system and the iTWR system are both control command systems of the air traffic control department, the ATC system mainly faces the district adjustment and approach department of the air traffic control department, and provides control services for high-altitude, medium-altitude and low-altitude aircraft, and the iTWR system mainly faces the tower department of the air traffic control department, and provides control services for low-altitude aircraft, field aircraft and vehicles.

[0005] Arriving aircraft: the approach controller first uses the ATC system for command, and then hands over to the tower controller of the iTWR system for continued command until the aircraft lands and taxies to the designated parking position.

[0006] Departing aircraft: the tower controller first uses the iTWR system for command, and then hands over to the approach controller of the ATC system for continued command until the aircraft flies out of the control airspace and is finally commanded by an external control unit.

[0007] In the iTWR system or the ATC system, the handover is usually sector-based, so the sector-based handover rule is also used when the iTWR system hands over to the ATC system or the ATC system hands over to the iTWR system.

[0008] When iTWR system hands over to ATC system from different runways, the specified handover approach sector is usually different, especially for multi-runway airports, which may involve up to 5 or 6 handover approach sectors.

[0009] When ATC system hands over to iTWR system from different runways, the specified handover tower sector is usually different, especially for multi-runway airports, which requires a corresponding handover tower sector for each runway.

[0010] Now the handover between iTWR system and ATC system is almost based on the C-type handover message in the MHT4029.3-2020 Civil Aviation Air Traffic Control Automation System Part 3: Flight Data Exchange issued by the Civil Aviation Administration of China, which has ORGAD (message sending unit address) and SECDEST (handover destination sector) to clearly indicate the use of sector code for handover.

[0011] Therefore, in the iTWR system, the handover approach sector code to ATC system when each runway takes off needs to be configured, and it needs to be ensured that the approach sector code is consistent with the approach sector code in the ATC system.

[0012] In the ATC system, the handover tower sector code to iTWR system when each runway lands needs to be configured, and it needs to be ensured that the tower sector code is consistent with the tower sector code in the iTWR system.

[0013] The disadvantages and causes of the above traditional technology are:

[0014] (1) The system configuration is not flexible enough: iTWR system and ATC system are two separate systems, each system has a main system and a backup system, which may involve four system manufacturers. Due to the differences in system design by different manufacturers, it may not be possible to keep the tower sector code in the ATC system consistent with the tower sector code in the iTWR system, and the approach sector code in the iTWR system may not be consistent with the approach sector code in the ATC system, such as character length restrictions, not allowed to contain numbers and underscores, etc.

[0015] (2) Not conducive to system function expansion: The handover tower sector code in the ATC system cannot be modified at will. If the tower sector code in the iTWR system is adjusted or a new runway is opened, the ATC system must also be modified simultaneously. The handover approach sector code in the iTWR system cannot be modified at will, but the ATC system may modify or add sector codes due to route / airspace adjustments or airspace traffic reasons. Once the handover approach sector code is changed, the iTWR system must also be modified simultaneously.

[0016] (3) Parameter modification will affect the maintainability of the system: system parameter modification usually requires software restart to take effect, iTWR system and ATC system are very important production and operation systems of air traffic control department, and any parameter modification and software restart need to be verified and applied for shutdown maintenance and a series of approval processes. SUMMARY

[0017] The embodiment of the present application aims to provide an iTWR system and ATC system data handover method and system to overcome the aforementioned technical defects.

[0018] To achieve the above-mentioned purpose, in a first aspect, the embodiment of the present application provides an iTWR system and ATC system data handover method, comprising:

[0019] The iTWR system initiates the handover step: the iTWR system sends a handover message containing the take-off runway number to the ATC system;

[0020] The ATC system receives the handover step: the ATC system receives the handover message, identifies the approach sector code in the ATC system according to the handover message, and completes the data handover of the iTWR system to the ATC system according to the approach sector code.

[0021] As a specific embodiment of the present application, the iTWR system initiates the handover step specifically:

[0022] Identify the take-off runway number in the iTWR system;

[0023] Determine whether the take-off runway number is empty, if it is empty, initiate handover failure;

[0024] If the take-off runway number is not empty, determine whether the take-off runway number is the runway number configured in the iTWR system; if not, initiate handover failure;

[0025] If the take-off runway number is the runway number configured in the iTWR system, the iTWR system sends a handover message containing the take-off runway number to the ATC system.

[0026] As a specific embodiment of the present application, the ATC system receives the handover step specifically:

[0027] The ATC system receives the handover message sent by the iTWR system;

[0028] Determine whether the take-off runway number is empty, if it is empty, receive handover failure;

[0029] If the take-off runway number is not empty, determine whether the take-off runway number in the handover message is the runway number configured in the ATC system; if not, receive handover failure;

[0030] If the takeoff runway number is a runway number configured in the ATC system, identifying an approach sector code inside the ATC system according to the message sending unit address and the takeoff runway number;

[0031] If it cannot be identified, receiving handover failure; if it can be identified, receiving handover success.

[0032] In a second aspect, embodiments of the present application provide a data handover method of an ATC system and an iTWR system, comprising:

[0033] The ATC system initiates a handover step: the ATC system sends a handover message containing a landing runway number to the iTWR system;

[0034] The iTWR system receives a handover step: the iTWR system receives the handover message, identifies a tower sector code in the iTWR system according to the handover message, and completes data handover of the ATC system to the iTWR system according to the tower sector code.

[0035] In some embodiments of the present application, the ATC system initiates a handover step specifically:

[0036] Identifying a landing runway number in the ATC system;

[0037] Determining whether the landing runway number is empty, if it is empty, initiating handover failure;

[0038] If the landing runway number is not empty, determining whether the landing runway number is a runway number configured in the ATC system; if not, initiating handover failure;

[0039] If the landing runway number is a runway number configured in the ATC system, the ATC system sends a handover message containing the landing runway number to the iTWR system.

[0040] In some embodiments of the present application, the iTWR system receives a handover step specifically:

[0041] The iTWR system receives the handover message sent by the ATC system;

[0042] Determining whether the landing runway number is empty, if it is empty, receiving handover failure;

[0043] If the landing runway number is not empty, determining whether the landing runway number in the handover message is a runway number configured in the iTWR system; if not, receiving handover failure;

[0044] If the landing runway number is a runway number configured in the iTWR system, identifying a tower sector code inside the iTWR system according to the landing runway number;

[0045] If not identifiable, a handover failure is received; if identifiable, a handover success is received.

[0046] In a third aspect, the embodiments of the present application provide a data handover system of an iTWR system and an ATC system, comprising:

[0047] The iTWR system is configured to send a handover message containing a takeoff runway number.

[0048] The ATC system is configured to receive the handover message sent by the iTWR system, identify an approach sector code in the ATC system according to the handover message, and complete data handover from the iTWR system to the ATC system according to the approach sector code.

[0049] Further, the ATC system is further configured to send a handover message containing a landing runway number to the iTWR system.

[0050] The iTWR system is further configured to receive the handover message, identify a tower sector code in the iTWR system according to the handover message, and complete data handover from the ATC system to the iTWR system according to the tower sector code.

[0051] The embodiments of the present application have the following beneficial effects:

[0052] (1) Flexible configuration and good compatibility: the takeoff / landing runway number is used to replace the approach / tower sector code as the handover identifier, which can ensure consistency between the iTWR system and the ATC system, and even if the systems are from different manufacturers, there will be no difficulty in configuring uniformity.

[0053] (2) Facilitate system function expansion: the adjustment of the approach sector code of the ATC system does not affect the iTWR system, and the adjustment of the tower sector code of the iTWR system does not affect the ATC system, thereby reducing the coupling degree between the parameter configurations of the two systems.

[0054] (3) Improve the maintainability of the system: the frequency of system parameter modification is reduced, and the iTWR system and the ATC system can run more continuously and stably, thereby improving the reliability of the system and enhancing the operation safety.

[0055] That is, the above technical solution of the present application provides a new bidirectional data handover receiving method between the iTWR system and the ATC system, that is, the handover is performed according to the takeoff / landing runway number, which can ensure the accuracy of the handover and receiving between the two systems; and the iTWR system and the ATC system do not need to additionally agree to configure the same approach / tower sector code, thereby improving the configuration flexibility and function expansion of the respective systems. BRIEF DESCRIPTION OF DRAWINGS

[0056] In order to more clearly illustrate the technical solutions in the specific embodiments or the prior art, the following will briefly introduce the drawings needed to be used in the specific embodiments or prior art description.

[0057] Figure 1 is a processing logic flow chart of initiating handover in the iTWR system of the present application;

[0058] Figure 2 is a processing logic flow chart of receiving handover in the ATC system of the present application;

[0059] Figure 3 is a processing logic flow chart of initiating handover in the ATC system of the present application;

[0060] Figure 4 is a processing logic flow chart of receiving handover in the iTWR system of the present application. DETAILED DESCRIPTION

[0061] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts belong to the scope of protection of the present application.

[0062] It should be understood that, when used in the specification and the appended claims, the terms "comprise" and "include" indicate the presence of the described features, integers, steps, operations, elements, and / or components, but do not exclude one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0063] The iTWR system is a control command system based on a single airport, and the configuration parameters of the system include the runway number of the airport, such as 02L / 20R.

[0064] The ATC system is a control command system based on one or more airports, and the configuration parameters of the system include the runway numbers of all the airports, such as 02L / 20R, 01 / 19, and 02 / 20.

[0065] Once the runway number of an airport is determined and published, it is usually fixed and unchanged. For the aircraft taking off, the tower controller can ensure that the take-off runway number used by each aircraft taking off is accurate, whether the control command is issued or the manual operation in the iTWR system, so that the take-off runway number is completely feasible as the handover receiving mode from the iTWR system to the ATC system.

[0066] Accordingly, for arriving aircraft, whether the approach controller issues control instructions or operates manually in the ATC system, the landing runway number used by each arriving aircraft can be ensured to be accurate. Therefore, using the landing runway number as the handover and reception method from the ATC system to the iTWR system is entirely feasible.

[0067] Based on this, this application provides a data transfer method from an iTWR system to an ATC system, including:

[0068] The iTWR system initiates the handover process by sending a handover message containing the takeoff runway number to the ATC system.

[0069] The ATC system receives the handover message, identifies the approach sector code in the ATC system based on the handover message, and completes the data handover from the iTWR system to the ATC system based on the approach sector code.

[0070] Among them, such as Figure 1 As shown, the handover process logic in the iTWR system is as follows:

[0071] The iTWR system identifies the takeoff runway number;

[0072] Determine if the takeoff runway number is empty; if it is, the handover will fail.

[0073] If the takeoff runway number is not empty, determine whether the takeoff runway number is the runway number configured in the iTWR system; if not, the handover will fail.

[0074] If the takeoff runway number is the runway number configured in the iTWR system, the iTWR system sends a handover message containing the takeoff runway number to the ATC system.

[0075] Correspondingly, such as Figure 2 As shown, the processing logic flow for receiving and transferring data in the ATC system is as follows:

[0076] The ATC system receives a handover message from the iTWR system;

[0077] Determine if the takeoff runway number is empty; if so, the handover fails.

[0078] If the takeoff runway number is not empty, determine whether the takeoff runway number in the handover message is the runway number configured in the ATC system; if not, the handover will fail.

[0079] If the takeoff runway number is the runway number configured in the ATC system, the approach sector code inside the ATC system is identified based on the message sending unit address and the takeoff runway number.

[0080] If the corresponding approach sector code cannot be identified, the handover will fail; if the corresponding approach sector code can be identified, the handover will succeed.

[0081] It should be noted that since the ATC system can include multiple airports, and different airports may have the same runway number, the ATC system must combine the message sending unit address and the takeoff runway number to identify and convert them into the ATC system's internal approach sector code.

[0082] As can be seen from the above description, the data transfer method from the iTWR system to the ATC system provided in this application has the following advantages:

[0083] (1) Flexible configuration and good compatibility: The takeoff runway number is used to replace the approach sector code as the handover identifier, which can ensure that it is consistent in both the iTWR system and the ATC system. Even if the systems are from different manufacturers, there will be no difficulty in unifying the configuration.

[0084] (2) It is conducive to the expansion of system functions: the adjustment of the ATC system approach sector code does not affect the iTWR system, reducing the coupling between the parameter configurations of the two systems.

[0085] (3) Improve system maintainability: Reduce the frequency of system parameter modification, which enables the iTWR system and ATC system to operate more continuously and stably, thereby improving system reliability and enhancing operational safety.

[0086] Based on the same inventive concept, embodiments of the present invention provide a data transfer method from an ATC system to an iTWR system, including:

[0087] The ATC system initiates the handover process by sending a handover message containing the landing runway number to the iTWR system.

[0088] The iTWR system receives the handover message, identifies the tower sector code in the iTWR system based on the handover message, and completes the data handover from the ATC system to the iTWR system based on the tower sector code.

[0089] Among them, such as Figure 3 As shown, the handover process logic in the ATC system is as follows:

[0090] The ATC system identifies the landing runway number;

[0091] Determine if the landing runway number is empty; if it is empty, the handover will fail.

[0092] If the landing runway number is not empty, then determine whether the landing runway number is the runway number configured in the ATC system; if not, then the handover will fail.

[0093] If the landing runway number is a runway number configured in the ATC system, the ATC system sends a handover message containing the landing runway number to the iTWR system.

[0094] Correspondingly, as shown in Figure 4 the processing logic flow of receiving handover in the iTWR system is as follows:

[0095] The iTWR system receives the handover message sent by the ATC system;

[0096] Determine whether the landing runway number is empty. If yes, the receiving handover fails;

[0097] If the landing runway number is not empty, determine whether the landing runway number in the handover message is a runway number configured in the iTWR system. If not, the receiving handover fails;

[0098] If the landing runway number is a runway number configured in the iTWR system, identify the tower sector code inside the iTWR system according to the landing runway number;

[0099] If the corresponding tower sector code cannot be identified, the receiving handover fails. If the corresponding tower sector code can be identified, the receiving handover succeeds.

[0100] From the above description, it can be known that the data handover method of the ATC system to the iTWR system provided by the present application has the following advantages:

[0101] (1) Flexible configuration and good compatibility: using the landing runway number to replace the tower sector code as the handover identifier can ensure that the ATC system and the iTWR system are consistent, and even if they are systems of different manufacturers, there will be no difficulty in configuring uniformity.

[0102] (2) Beneficial to system function expansion: the iTWR system approach sector code adjustment does not affect the ATC system, reducing the coupling degree between the parameter configurations of the two systems.

[0103] (3) Improve the maintainability of the system: reduce the frequency of system parameter modification, and enable the ATC system and the iTWR system to run more continuously and stably, thereby improving the reliability of the system and enhancing the operation safety.

[0104] Corresponding to the description of the method embodiment part, the present application also provides a data handover system of an iTWR system and an ATC system, which comprises the iTWR system and the ATC system, and uses a runway number as a handover identifier, thereby realizing bidirectional data handover between the two systems.

[0105] The iTWR system performs data handover to the ATC system, which comprises:

[0106] (i) The handover is initiated in the iTWR system, and the specific processing logic is described in detail in Figure 1 and the corresponding text description.

[0107] (ii) The handover is initiated in the ATC system, and the specific processing logic is described in detail in Figure 2 and the corresponding text description.

[0108] The data handover from the ATC system to the iTWR system includes:

[0109] (i) The handover is initiated in the ATC system, and the specific processing logic is described in detail in Figure 3 and the corresponding text description.

[0110] (ii) The handover is initiated in the iTWR system, and the specific processing logic is described in detail in Figure 4 and the corresponding text description.

[0111] It should be noted that more specific descriptions of the data handover system of the present application are described in the foregoing method embodiment section, and will not be repeated here.

[0112] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of various equivalent modifications or replacements within the technical range disclosed by the present application, and these modifications or replacements should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A data handover method of an iTWR system and an ATC system, the method comprising: The method comprises the following steps: iTWR system initiates handover step: the iTWR system sends a handover message containing a take-off runway number to the ATC system; ATC system receives handover step: the ATC system receives the handover message, identifies an approach sector code in the ATC system according to the handover message, and completes data handover from the iTWR system to the ATC system according to the approach sector code; The ATC system receives the handover step specifically comprises: The ATC system receives the handover message sent by the iTWR system; Determine whether the take-off runway number is empty, if yes, the handover fails; If the take-off runway number is not empty, determine whether the take-off runway number in the handover message is a runway number configured in the ATC system; if not, the handover fails; If the take-off runway number is a runway number configured in the ATC system, identify an approach sector code inside the ATC system according to the take-off runway number and the address of the message sender; If it cannot be identified, the handover fails; If it can be identified, the handover succeeds.

2. The data handover method of claim 1, wherein, The iTWR system initiates the handover step specifically comprises: Identify the take-off runway number in the iTWR system; Determine whether the take-off runway number is empty, if yes, the handover fails; If the take-off runway number is not empty, determine whether the take-off runway number is a runway number configured in the iTWR system; If not, the handover fails; 3. A data handover method of an ATC system and an iTWR system, characterized by, If the take-off runway number is a runway number configured in the iTWR system, the iTWR system sends a handover message containing the take-off runway number to the ATC system. The method comprises the following steps: ATC system initiates handover step: the ATC system sends a handover message containing a landing runway number to the iTWR system; iTWR system receives handover step: the iTWR system receives the handover message, identifies a tower sector code in the iTWR system according to the handover message, and completes data handover from the ATC system to the iTWR system according to the tower sector code; The iTWR system receives the handover step specifically comprises: The iTWR system receives the handover message sent by the ATC system; Determine whether the landing runway number is empty, if yes, the handover fails; If the landing runway number is not empty, determine whether the landing runway number in the handover message is a runway number configured in the iTWR system; if not, the handover fails; If the landing runway number is a runway number configured in the iTWR system, identify a tower sector code inside the iTWR system according to the landing runway number; If it cannot be identified, the handover fails; 4. The data handover method of claim 3, wherein, If it can be identified, the handover succeeds. The ATC system initiates the handover step specifically comprises: Identify the landing runway number in the ATC system; Determine whether the landing runway number is empty, if yes, the handover fails; If the landing runway number is not empty, determine whether the landing runway number is a runway number configured in the ATC system; if not, the handover fails; 5. A data handover system of an iTWR system and an ATC system, characterized by, If the landing runway number is a runway number configured in the ATC system, the ATC system sends a handover message containing the landing runway number to the iTWR system. The method comprises the following steps: iTWR system, configured to send a handover message containing a take-off runway number; The ATC system is configured to receive the handover message sent by the iTWR system, identify the approach sector code in the ATC system according to the handover message, and complete the data handover from the iTWR system to the ATC system according to the approach sector code. The ATC system receives the handover message sent by the iTWR system. If the takeoff runway number is empty, the handover is failed. If the takeoff runway number is not empty, it is determined whether the takeoff runway number in the handover message is the runway number configured in the ATC system. If the takeoff runway number is not the runway number configured in the ATC system, the handover is failed. If the takeoff runway number is the runway number configured in the ATC system, the approach sector code in the ATC system is identified according to the address of the message sending unit and the takeoff runway number. If the approach sector code cannot be identified, the handover is failed. If the approach sector code can be identified, the handover is successful.

6. The data handover system according to claim 5, wherein The ATC system is further configured to send a handover message containing a landing runway number to the iTWR system. The iTWR system is further configured to receive the handover message, identify the tower sector code in the iTWR system according to the handover message, and complete the data handover from the ATC system to the iTWR system according to the tower sector code.

Images