CN111326026B - Flight information reporting address cooperative generation and dynamic maintenance method - Google Patents
Flight information reporting address cooperative generation and dynamic maintenance method Download PDFInfo
- Publication number
- CN111326026B CN111326026B CN202010119601.XA CN202010119601A CN111326026B CN 111326026 B CN111326026 B CN 111326026B CN 202010119601 A CN202010119601 A CN 202010119601A CN 111326026 B CN111326026 B CN 111326026B
- Authority
- CN
- China
- Prior art keywords
- flight
- address list
- information
- address
- notification
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 35
- 238000012423 maintenance Methods 0.000 title claims abstract description 22
- 230000010365 information processing Effects 0.000 claims description 21
- 239000000284 extract Substances 0.000 claims description 3
- 230000005540 biological transmission Effects 0.000 abstract description 5
- 238000005192 partition Methods 0.000 description 18
- 238000010586 diagram Methods 0.000 description 5
- 238000013316 zoning Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/003—Flight plan management
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/003—Flight plan management
- G08G5/0034—Assembly of a flight plan
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/003—Flight plan management
- G08G5/0039—Modification of a flight plan
Landscapes
- Engineering & Computer Science (AREA)
- Aviation & Aerospace Engineering (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Traffic Control Systems (AREA)
Abstract
The invention belongs to the technical field of air traffic control automation, and particularly relates to a flight information notification address collaborative generation and dynamic maintenance method, which carries out address operation according to edited flight information in a flight information generation stage to generate a flight plan address list for storage; then, transmitting flight information according to the list; receiving flight information at a flight plan notification stage, performing address operation to generate a current plan address list, generating a current address list after adding a reporting unit, comparing the current address list with an original address list, and storing a corresponding result into the address list; then, the flight information is sent to each address of the address list one by one; and judging the message type of the flight information in the flight dynamic reporting stage, and then sending the flight information according to the address list. Compared with the prior art, the invention provides a reasonable message transmission flow, improves the reporting efficiency of flight information, and reduces the rate of missing report and error report.
Description
Technical Field
The invention belongs to the technical field of air traffic control automation, and particularly relates to a flight information notification address collaborative generation and dynamic maintenance method.
Background
The national aviation control system of China is divided into four levels, and according to different jurisdictions, the national aviation control system is divided into nationwide, regional aviation control system, subareas and airports from top to bottom. According to the regulations, the flight plan must be requested in advance and can be implemented after approval. Generally, a flight plan is planned by a control center of a take-off airport, and according to a control airspace and a combat airspace related to a flight route (airspace), the work of declaration, notification, forwarding and the like of the plan is completed according to the duty authority and the notification relation of each level of control center.
The flight intelligence system is an automated system that compiles and processes flight plans and their associated dynamics. The network transmission flow of the flight information designed in the past is as follows: before taking off, the taking-off airport edits and inputs the pre-flying plan into the system, and the flight information is sent to the bottom, namely: the airport system automatically generates the sending address of the flight information according to the flight route (airspace) and then sends the address to all receiving and reporting units. All message sending addresses are always carried during the message transmission, and in the subsequent plan execution process, such as plan change, change during execution, take-off, landing and other processes, the message is sent by the corresponding responsible unit according to all the forwarding addresses carried by the message.
Although the method simplifies the sending process, the method has three problems: firstly, a transmitting address is generated at a take-off airport, and an airport controller has no capability of determining the accuracy of all receiving and reporting addresses of the air route, so that the problems of missed report and wrong report exist; secondly, if other control centers at all levels need, the message can not be forwarded; thirdly, if the report fails, the manual report transmitting responsibility is totally positioned at the airport level, and the work efficiency of the source transmitting node is low. The message reporting method is not in accordance with the working mode of 'responsible by level' of the current control center.
In view of the above reasons, a reasonable message transmission flow is needed in the flight information system, so that the rebroadcasting relationship not only conforms to the practical work, but also can efficiently complete the message retransmission work.
Disclosure of Invention
Technical problem to be solved
The technical problem to be solved by the invention is as follows: how to provide a flight information notification address cooperative generation and dynamic maintenance method.
(II) technical scheme
In order to solve the above technical problems, the present invention provides a flight information notification address collaborative generation and dynamic maintenance method, which is implemented based on a flight information notification address collaborative generation and dynamic maintenance system, and the flight information notification address collaborative generation and dynamic maintenance system includes: the system comprises an information editing module, an information processing module, an address processing module, an information sending module and an information receiving module;
the flight information notification address collaborative generation and dynamic maintenance method comprises the following steps:
step S1: a flight information generation stage;
after the flight information is edited, firstly, performing address operation according to the flight information, and then generating a flight plan address list AL for storage; then, the flight information is sent according to the flight plan address list AL, and then the step S2 is carried out;
step S2: a flight plan reporting stage;
receiving the flight information generated in the step S1, firstly, performing address operation according to the flight information, generating a current plan address list, generating a current plan corresponding notification address list CAL together after adding a reporting unit, comparing the current plan corresponding notification address list CAL with an originally stored flight plan address list AL, and storing a corresponding result into the flight plan address list AL; then the flight information is sent to each address in the flight plan address list AL one by one, and then the step S3 is carried out;
step S3: a flight dynamic reporting stage;
after the flight information is edited or received, judging the message type of the flight information, and then sending the flight information according to a flight plan address list AL.
Wherein the step S1 includes:
step S101: the information editing module generates flight information and outputs the flight information to the information processing module;
step S102: after receiving flight information, the information processing module acquires three data items of a coming unit, a flight task and a flight route from the content of the flight information and outputs the two data items of the flight task and the flight route to the address processing module;
step S103: the address processing module calculates a notification address list YAL of the flight information according to the received two data items of the flight mission and the flight route, extracts a local notification relation list LAL from a local database, and stores the result of intersection of the notification address list YAL and the local notification relation list LAL as a flight plan address list AL;
step S104: the information sending module sends the flight information to each address in the flight plan address list AL one by one to complete the notification process.
In step S103, the result obtained by intersecting the address list YAL to be notified and the local notification relationship list LAL is stored as a flight plan address list AL;
namely: AL ═ YAL | LAL.
Wherein the step S2 includes:
step S201: the information receiving module receives the flight information from the step S1 and outputs the flight information to the information processing module;
step S202: after receiving flight information, the information processing module acquires three data items of a coming unit, a flight task and a flight route from the flight information content, and outputs the three data items of the flight task, the flight route and an coming unit address IA to the address processing module;
step S203: the address processing module calculates a notification address list YAL of the flight information according to the received two data items of the flight mission and the flight route, and generates a planned current notification address list CAL after a unit address IA is added in the notification address list YAL and is intersected with the extracted local notification relation list LAL;
at the moment, if the flight plan address list AL is empty, the address list CAL to be reported currently by the plan is directly used as the flight plan address list AL for storage;
if the flight plan address list AL is not empty, comparing the address list CAL to be reported currently in the plan with the flight plan address list AL, wherein the comparison result is divided into three conditions:
(1) if the planned current notification address list CAL contains a flight plan address list AL, directly storing the planned current notification address list CAL as the flight plan address list AL;
(2) if the address of the planned current reporting address list CAL is less than that of the flight plan address list AL, the addresses which are not in the planned current reporting address list CAL and are in the flight plan address list AL are deleted from the flight plan address list AL, and then the addresses are stored into a to-be-sent reporting cancellation address list NAL;
(3) if the planned current notification address list CAL has more addresses than the flight plan address list AL and less addresses than the flight plan address list AL, filling the planned current notification address list CAL with more addresses than the flight plan address list AL, deleting the planned current notification address list CAL with less addresses than the flight plan address list AL from the flight plan address list AL, and storing the planned current notification address list CAL with less addresses than the flight plan address list AL into a to-be-sent notification address list NAL;
step S204: the information sending module sends the flight information to each address in the planned address list AL one by one, then generates a planned cancellation report and sends the planned cancellation report to all addresses in the address list NAL to be sent, and the processing process is completed.
In step 203, the planned current notification address list CAL is directly stored as a flight plan address list AL, that is to say: AL — CAL.
Wherein the step S3 includes:
step S301: after the information editing module finishes editing or the information receiving module receives new flight information, the flight information is output to the information processing module;
step S302: the information processing module judges the type of flight information; if the flight information is not the CPL information, the information sending module is informed to send the flight information to each address in the flight plan address list AL one by one; if the CPL report is received, judging whether the air route information is modified:
if the flight information is not modified, the information sending module is informed to send the flight information to each address in the flight plan address list AL one by one;
and if the route information is changed, returning to execute the step S202-the step S204.
The CPL report is a current flight change report and is used for reporting a message that a flight line and a secondary code of the aircraft change in flight.
(III) advantageous effects
Compared with the prior art, the technical scheme of the invention provides a reasonable message transmission flow, so that the report forwarding relation not only accords with the actual work, but also can efficiently finish the message forwarding work, thereby improving the report efficiency of flight information and reducing the report missing rate and the report error rate.
Drawings
Fig. 1 is a schematic diagram of a planned full address list according to the technical solution of the present invention.
Fig. 2 is a schematic view of a flight plan generation processing flow according to the technical solution of the present invention.
Fig. 3 is a schematic view of a flight plan notification processing flow according to the technical solution of the present invention.
Fig. 4 is a schematic view of a flight dynamic notification processing flow according to the technical solution of the present invention.
Fig. 5 is a schematic diagram of the technical solution of the present invention.
Detailed Description
In order to make the objects, contents, and advantages of the present invention clearer, the following detailed description of the embodiments of the present invention will be made in conjunction with the accompanying drawings and examples.
In order to solve the technical problems, the invention provides a flight information notification address collaborative generation and dynamic maintenance method, which is used for improving the notification efficiency of flight information and reducing the rate of missed notification and wrong notification, and the method is actually consistent with the linear control work; the method is applied to flight information systems, is applied to control centers at all levels, and has consistent processing processes of all nodes in a distributed system; the flight information notification address cooperative generation and dynamic maintenance method is implemented based on a flight information notification address cooperative generation and dynamic maintenance system, and the flight information notification address cooperative generation and dynamic maintenance system comprises: the system comprises an information editing module, an information processing module, an address processing module, an information sending module and an information receiving module;
as shown in fig. 5, the method for generating and dynamically maintaining flight information notification address cooperatively includes the following steps:
step S1: a flight information generation stage;
after the flight information is edited, firstly, performing address operation according to the flight information, and then generating a flight plan address list AL for storage; then, the flight information is sent according to the flight plan address list AL, and then the step S2 is carried out;
step S2: a flight plan reporting stage;
receiving the flight information generated in the step S1, firstly, performing address operation according to the flight information, generating a current plan address list, generating a current plan corresponding notification address list CAL together after adding a reporting unit, comparing the current plan corresponding notification address list CAL with an originally stored flight plan address list AL, and storing a corresponding result into the flight plan address list AL; then the flight information is sent to each address in the flight plan address list AL one by one, and then the step S3 is carried out;
step S3: a flight dynamic reporting stage;
after the flight information is edited or received, judging the message type of the flight information, and then sending the flight information according to a flight plan address list AL.
Wherein the step S1 includes:
step S101: the information editing module generates flight information and outputs the flight information to the information processing module;
step S102: after receiving flight information, the information processing module acquires three data items of a coming unit, a flight task and a flight route from the content of the flight information and outputs the two data items of the flight task and the flight route to the address processing module;
step S103: the address processing module calculates a notification address list YAL of the flight information according to the received two data items of the flight mission and the flight route, extracts a local notification relation list LAL from a local database, and stores the result of intersection of the notification address list YAL and the local notification relation list LAL as a flight plan address list AL;
step S104: the information sending module sends the flight information to each address in the flight plan address list AL one by one to complete the notification process.
In step S103, the result obtained by intersecting the address list YAL to be notified and the local notification relationship list LAL is stored as a flight plan address list AL;
namely: AL ═ YAL | LAL.
Wherein the step S2 includes:
step S201: the information receiving module receives the flight information from the step S1 and outputs the flight information to the information processing module;
step S202: after receiving flight information, the information processing module acquires three data items of a coming unit, a flight task and a flight route from the flight information content, and outputs the three data items of the flight task, the flight route and an coming unit address IA to the address processing module;
step S203: the address processing module calculates a notification address list YAL of the flight information according to the received two data items of the flight mission and the flight route, and generates a planned current notification address list CAL after a unit address IA is added in the notification address list YAL and is intersected with the extracted local notification relation list LAL;
at the moment, if the flight plan address list AL is empty, the address list CAL to be reported currently by the plan is directly used as the flight plan address list AL for storage;
if the flight plan address list AL is not empty, comparing the address list CAL to be reported currently in the plan with the flight plan address list AL, wherein the comparison result is divided into three conditions:
(1) if the planned current notification address list CAL contains a flight plan address list AL, directly storing the planned current notification address list CAL as the flight plan address list AL;
(2) if the address of the planned current reporting address list CAL is less than that of the flight plan address list AL, the addresses which are not in the planned current reporting address list CAL and are in the flight plan address list AL are deleted from the flight plan address list AL, and then the addresses are stored into a to-be-sent reporting cancellation address list NAL;
(3) if the planned current notification address list CAL has more addresses than the flight plan address list AL and less addresses than the flight plan address list AL, filling the planned current notification address list CAL with more addresses than the flight plan address list AL, deleting the planned current notification address list CAL with less addresses than the flight plan address list AL from the flight plan address list AL, and storing the planned current notification address list CAL with less addresses than the flight plan address list AL into a to-be-sent notification address list NAL;
step S204: the information sending module sends the flight information to each address in the planned address list AL one by one, then generates a planned cancellation report and sends the planned cancellation report to all addresses in the address list NAL to be sent, and the processing process is completed.
In step 203, the planned current notification address list CAL is directly stored as a flight plan address list AL, that is to say: AL — CAL.
Wherein the step S3 includes:
step S301: after the information editing module finishes editing or the information receiving module receives new flight information, the flight information is output to the information processing module;
step S302: the information processing module judges the type of flight information; if the flight information is not the CPL information, the information sending module is informed to send the flight information to each address in the flight plan address list AL one by one; if the CPL report is received, judging whether the air route information is modified:
if the flight information is not modified, the information sending module is informed to send the flight information to each address in the flight plan address list AL one by one;
and if the route information is changed, returning to execute the step S202-the step S204.
The CPL is a current flight change message (current flight plan message) used for reporting a flight route of the aircraft in flight and a message of which the secondary code changes.
Example 1
In this embodiment, as shown in fig. 1, the diagram is a schematic diagram of a planned full address list, in the diagram, each solid line rectangle represents a distributed system node, a connecting line represents a notification relationship of the node, and an arrow points to a notification direction representing flight information.
In fig. 1, the airport node J1 generates a flight information and reports it to the partition node F1, and the flight plan address list of the airport node J1 includes the partition node F1; after receiving flight information sent by an airport node J1, a partition node F1 notifies an area node Z1 and an airport node J2, and a flight plan address list of the partition node F1 comprises an area node Z1, an airport node J1 and an airport node J2; after receiving flight information sent by the partition node F1, the regional node Z1 reports the flight information to the national node K and the partition node F2, and the flight plan address list of the regional node Z1 comprises the national node K, the partition node F1 and the partition node F2; after receiving flight information sent by the regional node Z1, the partition node F2 reports the flight information to an airport node J3, and a flight plan address list of the partition node F2 comprises a regional node Z1 and an airport node J3; after the airport node J3 receives the flight information sent by the partition node F2, the flight plan address list of the airport node J3 comprises the partition node F2; after receiving flight information sent by the regional node Z1, the national node K reports the flight information to the regional node Z2, and a flight plan address list of the national node K comprises the regional node Z1 and the regional node Z2; after receiving the flight information sent nationwide, the regional node Z2 reports the flight information to the partition node F3, and the plan related address list of the regional node Z2 comprises a national node K and a partition node F3; after receiving flight information sent by the regional node Z2, the partition node F3 reports the flight information to an airport node J4, and a flight plan address list of the partition node F3 comprises a regional node Z2 and an airport node J4; after the airport node J4 receives the flight information from the partition node F3, the flight plan address list of the airport node J4 includes the partition node F3.
In fig. 1, through the foregoing process, a planned full address list is maintained in common among the network systems: national node K, regional node Z1, regional node Z2, zoning node F1, zoning node F2, zoning node F3, airport node J1, airport node J2, airport node J3, airport node J4, which is a collection of lists of flight plan addresses for all of the plan related units. When any node in the plan full address list operates the flight plan, the system of each node can be synchronized through the plan full address list, and the full automation can be realized.
FIG. 2 shows a process flow for flight intelligence generation. The flight plan source node generates a new flight information through the information editing module, firstly calculates the address list YAL to be notified of the flight information, then obtains the local notification relation list LAL of the node, and generates and stores the address list AL as the flight plan address list AL after intersecting the address list YAL to be notified and the local notification relation list LAL of the node. And finally, sequentially sending the flight information messages to all the addresses in the flight plan address list AL. Thus, the flight information generation processing flow is completed.
Fig. 3 shows a flight plan notification processing flow. The node receives the flight plan message, firstly calculates the address list YAL to be notified of the flight information according to the flight route and the flight mission, acquires the local notification relation list LAL of the node after adding the unit address IA in the YAL, generates and stores the address list CAL to be notified at present after carrying out intersection operation on the address list YAL to be notified of the flight information and the local notification relation list LAL of the node.
Then, whether the flight plan address list AL is empty is judged:
1. if the flight plan address list AL is empty, directly storing a plan current notification address list CAL as a flight plan address list AL, sequentially sending flight information to each address in the flight plan address list AL, and finishing the flight plan notification processing flow;
2. if the flight plan address list AL is not empty, the plan current advisory address list CAL is compared with the flight plan address list AL:
(1) if the address list is the same as the address list AL, directly storing the address list CAL to be notified currently in the plan as a flight plan address list AL, sequentially sending flight information to each address in the flight plan address list AL, and ending the flight plan notification processing flow;
(2) if not, firstly storing the planned current reporting address list CAL as a flight plan address list AL, then storing the addresses of the planned current reporting address list CAL, which are reduced from the flight plan address list AL, into a to-be-sent reporting cancellation address list NAL, then generating a planned cancellation report and sending the planned cancellation report to all the addresses in the to-be-sent reporting cancellation address list NAL, and emptying the to-be-sent reporting cancellation address list NAL. And finally, sequentially sending the flight information to all the addresses in the flight plan address list AL, and finishing the flight plan notification processing flow.
Fig. 4 shows a flight dynamics notification processing flow. After the node finishes editing or receives the message, judging whether the message is a CPL message:
1. if the message is not a CPL message, directly sending the flight information to each address in a flight plan address list AL one by one, and finishing the flight dynamic notification processing flow;
2. if the message is a CPL message, judging whether the flight route is modified:
(1) if the flight route is not modified, directly sending the flight information to each address in the flight plan address list AL one by one, and finishing the flight dynamic notification processing flow;
(2) if the flight route is modified, firstly, a notification address list YAL of the flight information is calculated according to the flight route and the flight mission, and after a reporting unit IA is added in the notification address list YAL and is intersected with the extracted local notification relation table LAL, a planned current notification address list CAL is generated.
Then, whether the flight plan address list AL is empty is judged:
1) if the address list is empty, storing the address list CAL to be reported currently by the plan as a flight plan address list AL, and sending the flight information to each address in the flight plan address list AL one by one, wherein the flight dynamic report processing flow is finished;
2) if not, the list of addresses CAL to be notified currently by the plan is compared with the list of addresses AL of the flight plan:
2.1) if the address lists CAL are the same, directly storing the planned current to-be-reported address list CAL as a flight plan address list AL, sequentially sending flight information to each address in the flight plan address list AL, and finishing the flight dynamic reporting processing flow;
2.2) if the addresses are different, firstly, storing the planned current reporting address list CAL as a flight plan address list AL, storing the addresses, which are reduced from the flight plan address list AL, of the planned current reporting address list CAL into a to-be-sent reporting cancellation address list NAL, generating planned cancellation reports and sending all the addresses in the to-be-sent reporting cancellation address list NAL, and emptying the to-be-sent reporting cancellation address list NAL.
And finally, sequentially sending the flight information to all the addresses in the flight plan address list AL, and finishing the flight dynamic notification processing flow.
The above description is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, several modifications and variations can be made without departing from the technical principle of the present invention, and these modifications and variations should also be regarded as the protection scope of the present invention.
Claims (5)
1. A flight information notification address cooperative generation and dynamic maintenance method is characterized in that the flight information notification address cooperative generation and dynamic maintenance method is implemented based on a flight information notification address cooperative generation and dynamic maintenance system, and the flight information notification address cooperative generation and dynamic maintenance system comprises: the system comprises an information editing module, an information processing module, an address processing module, an information sending module and an information receiving module;
the flight information notification address collaborative generation and dynamic maintenance method comprises the following steps:
step S1: a flight information generation stage;
after the flight information is edited, firstly, performing address operation according to the flight information, and then generating a flight plan address list AL for storage; then, the flight information is sent according to the flight plan address list AL, and then the step S2 is carried out;
step S2: a flight plan reporting stage;
receiving the flight information generated in the step S1, firstly, performing address operation according to the flight information, generating a current plan address list, generating a current plan corresponding notification address list CAL together after adding a reporting unit, comparing the current plan corresponding notification address list CAL with an originally stored flight plan address list AL, and storing a corresponding result into the flight plan address list AL; then the flight information is sent to each address in the flight plan address list AL one by one, and then the step S3 is carried out;
step S3: a flight dynamic reporting stage;
after editing is completed or flight information is received, judging the message type of the flight information, and then sending the flight information according to a flight plan address list AL;
the step S1 includes:
step S101: the information editing module generates flight information and outputs the flight information to the information processing module;
step S102: after receiving flight information, the information processing module acquires three data items of a coming unit, a flight task and a flight route from the content of the flight information and outputs the two data items of the flight task and the flight route to the address processing module;
step S103: the address processing module calculates a notification address list YAL of the flight information according to the received two data items of the flight mission and the flight route, extracts a local notification relation list LAL from a local database, and stores the result of intersection of the notification address list YAL and the local notification relation list LAL as a flight plan address list AL;
step S104: the information sending module sends the flight information to each address in the flight plan address list AL one by one to complete the reporting process;
in the step S103, the result of intersecting the notification address list YAL and the local notification relationship list LAL is stored as a flight plan address list AL;
namely: AL ═ YAL | LAL.
2. The method for collaborative generation and dynamic maintenance of flight intelligence advisory addresses of claim 1, wherein the step S2 comprises:
step S201: the information receiving module receives the flight information from the step S1 and outputs the flight information to the information processing module;
step S202: after receiving flight information, the information processing module acquires three data items of a coming unit, a flight task and a flight route from the flight information content, and outputs the three data items of the flight task, the flight route and an coming unit address IA to the address processing module;
step S203: the address processing module calculates a notification address list YAL of the flight information according to the received two data items of the flight mission and the flight route, and generates a planned current notification address list CAL after a unit address IA is added in the notification address list YAL and is intersected with the extracted local notification relation list LAL;
at the moment, if the flight plan address list AL is empty, the address list CAL to be reported currently by the plan is directly used as the flight plan address list AL for storage;
if the flight plan address list AL is not empty, comparing the address list CAL to be reported currently in the plan with the flight plan address list AL, wherein the comparison result is divided into three conditions:
(1) if the planned current notification address list CAL contains a flight plan address list AL, directly storing the planned current notification address list CAL as the flight plan address list AL;
(2) if the address of the planned current reporting address list CAL is less than that of the flight plan address list AL, the addresses which are not in the planned current reporting address list CAL and are in the flight plan address list AL are deleted from the flight plan address list AL, and then the addresses are stored into a to-be-sent reporting cancellation address list NAL;
(3) if the planned current notification address list CAL has more addresses than the flight plan address list AL and less addresses than the flight plan address list AL, filling the planned current notification address list CAL with more addresses than the flight plan address list AL, deleting the planned current notification address list CAL with less addresses than the flight plan address list AL from the flight plan address list AL, and storing the planned current notification address list CAL with less addresses than the flight plan address list AL into a to-be-sent notification address list NAL;
step S204: the information sending module sends the flight information to each address in the planned address list AL one by one, then generates a planned cancellation report and sends the planned cancellation report to all addresses in the address list NAL to be sent, and the processing process is completed.
3. The method for collaborative generation and dynamic maintenance of flight intelligence notification addresses according to claim 2, wherein in step S203, the planned current notification address list CAL is directly stored as a flight plan address list AL, that is: AL — CAL.
4. The method for collaborative generation and dynamic maintenance of flight intelligence advisory addresses of claim 2, wherein the step S3 comprises:
step S301: after the information editing module finishes editing or the information receiving module receives new flight information, the flight information is output to the information processing module;
step S302: the information processing module judges the type of flight information; if the flight information is not the CPL information, the information sending module is informed to send the flight information to each address in the flight plan address list AL one by one; if the CPL report is received, judging whether the air route information is modified:
if the flight information is not modified, the information sending module is informed to send the flight information to each address in the flight plan address list AL one by one;
and if the route information is changed, returning to execute the step S202-the step S204.
5. The method for collaborative generation and dynamic maintenance of a flight intelligence advisory address as claimed in claim 4, wherein the CPL advisory is a current flight change advisory for advisory messages of a flight line of an in-flight aircraft, which change in secondary codes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010119601.XA CN111326026B (en) | 2020-02-26 | 2020-02-26 | Flight information reporting address cooperative generation and dynamic maintenance method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010119601.XA CN111326026B (en) | 2020-02-26 | 2020-02-26 | Flight information reporting address cooperative generation and dynamic maintenance method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111326026A CN111326026A (en) | 2020-06-23 |
| CN111326026B true CN111326026B (en) | 2021-02-09 |
Family
ID=71167209
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010119601.XA Expired - Fee Related CN111326026B (en) | 2020-02-26 | 2020-02-26 | Flight information reporting address cooperative generation and dynamic maintenance method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111326026B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111915931A (en) * | 2020-07-26 | 2020-11-10 | 中国人民解放军93209部队 | Batch flight plan error correction method, device and system based on Mercker tree |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1622538A (en) * | 2003-11-24 | 2005-06-01 | 北京航空航天大学 | Down message multi-point delivery method of aviation gateway cluster system |
| CN102223301A (en) * | 2011-06-09 | 2011-10-19 | 民航数据通信有限责任公司 | Data processing system for judging operating states of flights of control tower |
| CN202549080U (en) * | 2012-03-16 | 2012-11-21 | 中国民用航空总局第二研究所 | Fusion system of radar data, flight plan data and ADS-B data |
| CN103001888A (en) * | 2012-11-23 | 2013-03-27 | 北京东土科技股份有限公司 | Real-time data transmission method and node device |
| CN103763188A (en) * | 2014-01-22 | 2014-04-30 | 四川九洲空管科技有限责任公司 | Multi-type message real-time processing method and device |
| CN104332072A (en) * | 2014-10-22 | 2015-02-04 | 北京航空航天大学 | General aviation flight plan management system |
| CN107566049A (en) * | 2017-07-12 | 2018-01-09 | 上海民航华东空管工程技术有限公司 | A kind of method for realizing that civil aviaton's telegram intelligently sends using computer |
| CN110379210A (en) * | 2019-07-30 | 2019-10-25 | 四川九洲空管科技有限责任公司 | A kind of civil aircraft exception flight monitoring method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9930707B2 (en) * | 2015-07-10 | 2018-03-27 | Thales Avionics, Inc. | In-flight entertainment system that identifies wireless access point locations within cabin |
-
2020
- 2020-02-26 CN CN202010119601.XA patent/CN111326026B/en not_active Expired - Fee Related
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1622538A (en) * | 2003-11-24 | 2005-06-01 | 北京航空航天大学 | Down message multi-point delivery method of aviation gateway cluster system |
| CN102223301A (en) * | 2011-06-09 | 2011-10-19 | 民航数据通信有限责任公司 | Data processing system for judging operating states of flights of control tower |
| CN202549080U (en) * | 2012-03-16 | 2012-11-21 | 中国民用航空总局第二研究所 | Fusion system of radar data, flight plan data and ADS-B data |
| CN103001888A (en) * | 2012-11-23 | 2013-03-27 | 北京东土科技股份有限公司 | Real-time data transmission method and node device |
| CN103763188A (en) * | 2014-01-22 | 2014-04-30 | 四川九洲空管科技有限责任公司 | Multi-type message real-time processing method and device |
| CN104332072A (en) * | 2014-10-22 | 2015-02-04 | 北京航空航天大学 | General aviation flight plan management system |
| CN107566049A (en) * | 2017-07-12 | 2018-01-09 | 上海民航华东空管工程技术有限公司 | A kind of method for realizing that civil aviaton's telegram intelligently sends using computer |
| CN110379210A (en) * | 2019-07-30 | 2019-10-25 | 四川九洲空管科技有限责任公司 | A kind of civil aircraft exception flight monitoring method and device |
Non-Patent Citations (1)
| Title |
|---|
| 计划航线通报地址自动生成方法研究;李卫国等;《中国民航飞行学院学报》;20030630;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111326026A (en) | 2020-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108305010B (en) | Workflow engine system and cross-platform and cross-application flow propelling method thereof | |
| US8380373B2 (en) | System and method for dispatching by exception | |
| CN106097780B (en) | A kind of distributed air data processing method based on data center | |
| CN109150572B (en) | Method, device and computer readable storage medium for realizing alarm association | |
| US20040064356A1 (en) | Workflow method and system therefor | |
| CN111326026B (en) | Flight information reporting address cooperative generation and dynamic maintenance method | |
| CN109857074A (en) | Intelligent logistics system and workshop management system | |
| CN101663687A (en) | Scheduling resources for airline flights | |
| CN101147146A (en) | Computer network system for constructing, synchronizing and/or managing a second database from/with a first database, and methods therefore | |
| CN102508737A (en) | Method for synchronizing data between main system and backup system of air traffic control | |
| CN111326027B (en) | Flight information reporting address cooperative generation and dynamic maintenance system | |
| CN116366643A (en) | Cloud edge cooperative platform architecture for intelligent operation and maintenance of industrial mobile robot | |
| CN109144629B (en) | Establishing and working method of flexible production line AGV system semantic web | |
| CN113205705A (en) | Flight telegram centralized processing system and method based on telegram label | |
| CN116129681B (en) | Civil aviation telegraph shunting processing system and method based on regional gridding management | |
| CN100364269C (en) | CNS/ATM control workstation and control method thereof | |
| CN116896767A (en) | Unmanned aerial vehicle cluster information transmission and synchronization method under unreliable network | |
| CN100502256C (en) | Method, device and system for spreading general-purpose accessing transceiver service area | |
| CN101035095B (en) | Information update method for member addition and exit in the temporary group of the instant message | |
| CN117077906A (en) | Construction method of distributed Internet of things system of LNG energy management platform | |
| CN112668935A (en) | Flight management method and device, electronic equipment and computer storage medium | |
| CN113946623B (en) | Main and standby system data real-time synchronization system and method | |
| Zhuang et al. | Application of control transfer technology between automated air traffic control systems based on flight data interaction | |
| Deng et al. | Design of logistics transportation monitoring system based on GPS/DR combined positioning technology | |
| JP2013163560A (en) | Article allotting system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20210209 |