An airborne software addressing method based on application layer address

Abstract

The present invention provides an airborne software addressing method based on application layer addresses. An airborne ANS server node establishes a coupling relationship with a ground ANS server node, and airborne / ground application software establishes a binding relationship with an airborne / ground proxy node. When the airborne / ground application software initiates a data transmission request, the airborne / ground proxy node initiates an application layer address resolution request, which is then resolved by the airborne / ground ANS server node, feeding back the destination application software routing information to the airborne / ground application software, which then performs data transmission. The present invention uses an application layer address naming mechanism to hide the physical location information of both parties, thereby improving the security of interaction. Furthermore, the application layer address-based addressing mechanism, dynamic registration, and system synchronization mechanism address the issue of airborne network planning updates caused by changing scenarios, enabling anytime, anywhere access and plug-and-play requirements, thereby improving the continuity of interaction.

Description

Technical Field

[0001] The present invention relates to the field of airborne communications, and in particular to an airborne software addressing method based on application layer addresses. Background Art

[0002] At present, due to the instability of airborne wireless links, the variability of application software running status and residence location, and the variability of mobile device access locations, it is difficult to meet the plug-and-play requirements of application software interaction on the airborne side, between air and ground, and between the ground. There is an urgent need for a solution that can solve the problem of airborne network planning and updating caused by scenarios such as changes in mobile device access points and changes in application software residence locations. Summary of the Invention

[0003] In response to the problems existing in the existing technology, an airborne software addressing method based on application layer address is provided. The application software is now decoupled from the underlying transmission network. During the interaction process, the source end does not need to know the physical location and transmission medium of the destination end. This solves the problem of network planning updates caused by scenarios such as changes in the access point of mobile devices and changes in the resident location of application software. At the same time, the security of the interaction process is improved.

[0004] The technical solution adopted by the present invention is as follows: an airborne software addressing method based on application layer address is applied between the airborne terminal and the ground terminal;

[0005] The airborne end includes an airborne proxy node and an airborne ANS server node that establish a coupling relationship. The ground end includes a ground proxy node and a ground ANS server node that establish a coupling relationship. The airborne ANS server node establishes a coupling relationship with the ground ANS server node. The airborne / ground application software establishes a binding relationship with the airborne / ground proxy node.

[0006] When the airborne / ground application software initiates a data transmission request, the message only carries the application layer address of the destination application software. The airborne / ground proxy node initiates an application layer address resolution request, which is then completed by the airborne / ground ANS server node. The routing information of the destination application software is fed back to the airborne / ground application software, and the airborne / ground application software performs data transmission.

[0007] Furthermore, the addressing process between onboard application software is as follows:

[0008] The onboard application software initiates a data request via the bound onboard proxy node;

[0009] The airborne proxy node initiates an application layer address resolution request to the airborne ANS server node. The airborne ANS server node determines that the destination is the airborne application software based on the destination application layer address carried in the request. It then combines the cached state and policy of the destination airborne application software to determine whether the source and destination parties can interact. After successful resolution, it returns an application layer address resolution response carrying the routing information of the destination airborne application software.

[0010] The onboard application software and the destination application software transmit data.

[0011] Furthermore, the addressing process between ground-side application software is as follows:

[0012] The ground-side application software initiates a data request through the bound ground agent node;

[0013] The ground proxy node initiates an application layer address resolution request to the ground ANS server node. The ground ANS server node determines that the destination is the ground application software based on the destination application layer address carried in the request. It then combines the cached state and policy of the destination ground application software to determine whether the source and destination parties can interact. After successful resolution, it returns an application layer address resolution response carrying the destination ground application software routing information.

[0014] The ground-side application software and the destination-side application software transmit data.

[0015] Furthermore, the addressing process between the onboard application software and the ground application software is as follows:

[0016] The onboard application software initiates a data transmission request to the destination application software via the bound onboard proxy node;

[0017] The airborne proxy node initiates an application layer address resolution request to the airborne ANS server node. The airborne ANS server node determines that the destination application layer address carried in the request is not the local airborne application software, and the airborne ANS server node fails to resolve the address.

[0018] The airborne ANS server node sends an address resolution request to the ground ANS server node with the destination application layer address. The ground ANS server node determines that it is a ground-side application software based on the destination application layer address in the request. It then determines whether the source and destination can interact with each other based on the cached destination application software status and policy. If the resolution is successful, it returns an application layer address resolution response with the ground-side destination application software routing information.

[0019] The airborne application software exchanges data with the ground application software.

[0020] Furthermore, the application layer address name structure is:

[0021] <Proxy Node>&<ANS Server Node>&<Network>

[0022] Among them, each field in <…> is an identifier, and the identifiers are distinguished by the delimiter "&". The parsing matches the application layer name from right to left; the identifier is described by a string, and the delimiter "." is used to represent multiple application software on the same proxy node; <Proxy Node> represents the name of the proxy node bound to the application software; <ANS Server Node> represents the name of the ANS server node that establishes a coupling relationship with the proxy node; <Network> represents the network name to which the application software belongs.

[0023] Furthermore, it also includes that the airborne / ground application software completes binding and synchronization with the airborne / ground proxy node according to the dynamic registration mechanism; the airborne / ground proxy node establishes a coupling relationship with the airborne / ground ANS server node according to the dynamic registration mechanism.

[0024] Furthermore, the dynamic registration mechanism includes:

[0025] The airborne / ground application software is bound to at most one airborne / ground proxy node; the airborne / ground proxy node supports at least two airborne / ground application software to be bound to it; the binding of the airborne / ground application software to the airborne / ground proxy node is initiated by the application software;

[0026] The airborne / ground proxy node is coupled to at most one airborne / ground ANS server node; the coupling relationship between the airborne / ground proxy node and the airborne / ground ANS server node should be actively initiated by the proxy node;

[0027] After the airborne / ground application software, the airborne / ground proxy node, and the airborne / ground ANS server node complete the dynamic registration process, periodic heartbeat detection is started.

[0028] Furthermore, it also includes a system synchronization mechanism. When the binding relationship between the airborne / ground application software and the airborne / ground proxy node or the coupling relationship between the airborne / ground proxy node and the airborne / ground ANS server node changes, the attributes and running states of the involved application software are updated.

[0029] Furthermore, the system synchronization mechanism specifically includes:

[0030] After the dynamic registration of the airborne application software is successful, the airborne proxy node synchronizes the attributes and running states to the airborne ANS server node. After completing the local update, it synchronizes the attributes and running states to the ground ANS server node, and starts periodic heartbeat detection to update the attributes and running states of the application software in real time;

[0031] After the ground application software is dynamically registered successfully, the ground agent node synchronizes the attributes and running status to the ground ANS server node, and starts periodic heartbeat detection to update the application software attributes and running status in real time;

[0032] After the onboard proxy node is successfully dynamically registered, it will synchronize the attributes and running status of multiple onboard application software with which it has established a binding relationship with the onboard ANS server node. After completing the local update, it will synchronize the attributes and running status with the ground ANS server node and start periodic heartbeat detection to update the application software attributes and running status in real time.

[0033] After the ground agent node is successfully dynamically registered, the ground ANS server node updates the properties and running status of multiple ground application software that have established binding relationships with the ground agent node, and starts periodic heartbeat detection to update the application software properties and running status in real time.

[0034] Furthermore, when the mobile device is connected to the airborne terminal or the ground terminal, the system synchronization mechanism in which the binding relationship between the airborne / ground application software and the airborne / ground agent node changes is used to update the attributes and operating status.

[0035] Compared with the existing technology, the beneficial effects of adopting the above technical solution are as follows: the present invention adopts a new airborne software application layer address naming mechanism, which hides the actual physical location information of the software of both communicating parties and improves the security of interaction; at the same time, based on the addressing mechanism, dynamic registration and system synchronization mechanism of the application layer address, it solves the problem of airborne network planning and updating caused by scenarios such as changes in the access point of mobile equipment and changes in the resident location of application software, realizes access anytime and anywhere, plug-and-play requirements, and improves the continuity of interaction. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 FIG. 1 is a schematic diagram of a system architecture in an embodiment of the present invention.

[0037] Figure 2 Schematic diagram of the interactive addressing process between onboard application software in one embodiment of the present invention.

[0038] Figure 3 Schematic diagram of the interactive addressing process between ground-side application software in one embodiment of the present invention.

[0039] Figure 4 The figure is a schematic diagram of the interactive addressing process between air-ground application software in one embodiment of the present invention.

[0040] Figure 5 Schematic diagram of the dynamic registration process of airborne / ground application software in one embodiment of the present invention.

[0041] Figure 6Schematic diagram of the dynamic registration process of airborne / ground agent nodes in one embodiment of the present invention.

[0042] Figure 7 Schematic diagram of system synchronization when the binding relationship between onboard application software and onboard proxy node changes in one embodiment of the present invention.

[0043] Figure 8 This is a schematic diagram of system synchronization when the binding relationship between ground application software and ground agent nodes changes in one embodiment of the present invention.

[0044] Figure 9 Schematic diagram of system synchronization when the coupling relationship between the onboard proxy node and the onboard ANS server node changes in one embodiment of the present invention.

[0045] Figure 10 Schematic diagram of system synchronization when the coupling relationship between the ground agent node and the ground ANS server node changes in one embodiment of the present invention. DETAILED DESCRIPTION

[0046] The embodiments of the present application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar modules or modules with the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application and are not to be construed as limiting the present application. On the contrary, the embodiments of the present application include all changes, modifications, and equivalents that fall within the spirit and scope of the appended claims.

[0047] In order to meet the plug-and-play requirements for onboard, air-to-ground, and ground-to-air application software interaction in civil aircraft projects, the embodiment of the present invention proposes an onboard software addressing method based on application layer addresses, which decouples application software from the underlying transmission network. During the interaction process, the source end does not need to know the physical location and transmission medium of the destination end, solving the problem of network planning updates caused by changes in the access point of mobile devices and the location of application software, while improving the security of the interaction process. Specifically:

[0048] The airborne software addressing method based on the application layer address is applied between the airborne terminal and the ground terminal;

[0049] The airborne end includes an airborne proxy node and an airborne ANS server node (ANS: Address Name Service) that establish a coupling relationship. The ground end includes a ground proxy node and a ground ANS server node that establish a coupling relationship. The airborne ANS server node establishes a coupling relationship with the ground ANS server node, and the airborne / ground application software establishes a binding relationship with the airborne / ground proxy node.

[0050] When the airborne / ground application software initiates a data transmission request, only the application layer address of the destination application software is carried in the message. The airborne / ground proxy node initiates an application layer address resolution request, and then the airborne / ground ANS server node completes the resolution and feeds back the routing information of the destination application software to the airborne / ground application software, and the airborne / ground application software performs data transmission.

[0051] As Figure 1 shown in the schematic diagram of the system architecture in this embodiment, the following rules must be satisfied among each node:

[0052] (1) The airborne / ground application software needs to establish a binding relationship with the corresponding proxy node, and is only allowed to be bound to one proxy node. Multiple proxy nodes are allowed to exist in the airborne / ground side.

[0053] (2) The airborne / ground proxy node must establish a coupling relationship with the ANS server node, and is only allowed to be coupled to one ANS server node. When there are multiple ANS server nodes, one of the ground ANS server nodes serves as the main node of the whole system.

[0054] (3) The airborne ANS server node must establish a coupling relationship with the ground ANS server node, and is only allowed to be coupled to one ground ANS server node.

[0055] In this embodiment, addressing depends on the application layer address, and a unique name is assigned to each application software and node respectively. Specifically, the application layer address name structure is:

[0056] <Proxy node>&<ANS server node>&<Network>

[0057] Among them:

[0058] (1) Each field in <…> is called an identifier, and the identifiers are distinguished by the delimiter "&". When addressing, the application layer name is matched from right to left;

[0059] (2) The identifier is described by a string, and the delimiter "." is used to identify multiple application software bound on the same proxy node.

[0060] (3) The identifier is allowed to be empty, indicating matching any one or all. Among them, the <proxy node> identifier is required, and other identifiers can be empty;

[0061] (4) The identifier is allowed to use wildcards, where "*" means matching all, and "+" means matching the local server node or the local network.

[0062] In the application layer address structure, <proxy node> represents the node name that establishes a binding relationship with the application software, including the airborne proxy node and the ground proxy node; <ANS server node> represents the ANS server node name that establishes a coupling relationship with the proxy node, including the airborne ANS server node and the ground ANS server node. Usually, there is only one airborne ANS server node on the airborne side of a single aircraft, and using the tail number as this identifier can ensure its uniqueness; <network> represents the network name to which the application software belongs, which can be used to distinguish different countries, different regions or different airlines.

[0063] As Figure 1 shown, if the application layer address is: AOC.ACD&N1234&Air China, it means that in the Air China network, the airborne ANS server node is N1234, and it is an AOC application that establishes a binding relationship with the ACD domain airborne proxy node.

[0064] The addressing method proposed in this embodiment will be further described below.

[0065] In this embodiment, the addressing method based on the application layer address mainly depends on the established ANS server node. Through this node, the application layer address is resolved, and the application layer address of the destination application software is resolved into a routable transmission path.

[0066] As Figure 2 shown, the following is the interactive addressing process between airborne application software:

[0067] (1) The airborne application software initiates a data request through the bound airborne proxy node;

[0068] (2) The airborne proxy node sends an application layer address resolution request to the airborne ANS server node. The airborne ANS server node determines that the destination is the airborne application software based on the destination application layer address carried in the request, and judges whether the source and destination can interact by combining the cached status and policies of the destination airborne application software; after successful resolution, it returns an application layer address resolution response and carries the routing information of the destination airborne application software;

[0069] (3) The airborne application software and the destination application software perform data transmission.

[0070] As Figure 3 shown, the interactive addressing process between ground application software is similar to the airborne addressing process. Different from the airborne side, the ground proxy node and the ground ANS server node are responsible for address resolution on the ground side. The specific process is as follows:

[0071] (1) The ground application software initiates a data request through the bound ground proxy node;

[0072] (2) The ground proxy node initiates an application layer address resolution request to the ground ANS server node. The ground ANS server node determines that the destination is the ground application software based on the destination application layer address carried in the request, and combines the cached state and policy of the destination ground application software to determine whether the source and destination can interact. After successful resolution, the ground ANS server node returns an application layer address resolution response carrying the destination ground application software routing information.

[0073] (3) The ground-side application software and the destination-side application software transmit data.

[0074] like Figure 4 As shown, this embodiment also proposes that the addressing process between the airborne application software and the ground application software is:

[0075] (1) The onboard application software initiates a data transmission request to the destination application software through the bound onboard proxy node;

[0076] (2) The airborne proxy node initiates an application layer address resolution request to the airborne ANS server node. The airborne ANS server node determines that the destination application layer address carried in the request is not the local airborne application software, and the airborne ANS server node fails to resolve the address.

[0077] (3) The airborne ANS server node sends an address resolution request to the ground ANS server node with the destination application layer address. The ground ANS server node determines that it is a ground-side application software based on the destination application layer address in the request. It then determines whether the source and destination can interact with each other based on the cached destination application software status and policy. After successful resolution, it returns an application layer address resolution response and carries the ground destination application software routing information.

[0078] (4) The airborne application software and the ground application software exchange data.

[0079] In order to enable random access and plug-and-play of application software and system nodes anywhere, this embodiment also proposes a dynamic registration and system synchronization mechanism to ensure the continuity of interaction.

[0080] Specifically, in this embodiment, dynamic registration mainly includes two parts: dynamic establishment of the binding relationship between the application software and the agent node (including airborne and ground); dynamic establishment of the coupling relationship between the agent node and the ANS server node (including airborne and ground).

[0081] like Figure 5 As shown, the dynamic registration process of airborne / ground application software is as follows:

[0082] The airborne / ground application software starts the software and initiates a binding request. The airborne / ground agent node receives the request and determines that it is a legitimate application software. The binding is successful. The airborne / ground application software synchronizes its status with the airborne / ground agent node and starts periodic heartbeat detection.

[0083] like Figure 6 As shown below, the dynamic registration flow chart of airborne / ground agent nodes is as follows:

[0084] The airborne / ground agent node is started and initiates a connection establishment request. The airborne / ground ANS server node receives the request and determines it to be a legitimate agent node. The connection is successfully established. The airborne / ground agent node synchronizes its status with the airborne / ground ANS server node and starts periodic heartbeat detection.

[0085] It should be noted that dynamic registration in this embodiment needs to meet the following rules:

[0086] 1) Airborne / ground application software can only be bound to one airborne / ground agent node at most, and the agent node supports at least two application software to be bound to it;

[0087] 2) The binding relationship between the application software and the proxy node should be initiated by the application software. The proxy node is not allowed to initiate a binding request. Both the application software and the proxy node can actively initiate an unbinding request;

[0088] 3) An airborne / ground proxy node can be coupled with at most one airborne / ground ANS server node, and an ANS server node can support at least one proxy node to be coupled with it;

[0089] 4) The connection between the proxy node and the ANS server node should be initiated by the proxy node. The ANS server node is not allowed to initiate a connection request. Both the proxy node and the ANS server node can initiate a disconnection request.

[0090] 5) After the airborne / ground application software, proxy node, and ANS server node complete the dynamic registration process, periodic heartbeat detection will be started.

[0091] Furthermore, system synchronization also includes two parts: synchronization of properties and operating status between the application software and the proxy node; and synchronization of properties and operating status between the proxy node and the ANS server node. System synchronization is triggered when the binding relationship between the application software and the proxy node changes, when the access point of a mobile device changes (including the location of the application software), or when the coupling relationship between the proxy node and the ANS server node changes.

[0092] The following further explains the system synchronization mechanism for different scenarios.

[0093] like Figure 7As shown in the figure, when the binding relationship between the onboard application software and the onboard proxy node changes:

[0094] After the onboard application software is successfully dynamically registered, the onboard proxy node synchronizes the attributes and running status with the onboard ANS server node. After completing the local update, it synchronizes the attributes and running status with the ground ANS server node and starts periodic heartbeat detection at the same time. When the heartbeat detection fails, it is determined that the running status of the airborne application software has failed, and the attributes and running status are synchronized with the onboard ANS server node and the ground ANS server node again to ensure the consistency of the airborne and ground status.

[0095] like Figure 8 As shown in the figure, when the binding relationship between the ground application software and the ground agent node changes:

[0096] After the ground application software is successfully dynamically registered, the ground agent node synchronizes the attributes and running status to the ground ANS server node, and starts periodic heartbeat detection at the same time. When the heartbeat detection fails, it is determined that the running status of the ground application software is faulty, and the attributes and running status are synchronized to the ground ANS server node again.

[0097] The changes in the access points of mobile devices (including changes in the location where application software resides) include changes in access at the airborne end and changes in access at the ground end. The synchronization process is similar to the process of changing the binding relationship between airborne application software and proxy nodes and the process of changing the binding relationship between ground application software and proxy nodes, and will not be repeated here.

[0098] like Figure 9 As shown, when the coupling relationship between the airborne proxy node and the airborne ANS server node changes:

[0099] After the airborne proxy node is dynamically registered successfully, it will synchronize the attributes and running status of multiple airborne application software that have established binding relationships with the airborne ANS server node. After completing the local update, it will synchronize the attributes and running status with the ground ANS server node and start periodic heartbeat detection at the same time. When the heartbeat detection fails, it is determined that the running status of the airborne proxy node has failed, and the attributes and running status of multiple airborne application software that have established binding relationships with the airborne proxy node will be synchronized with the airborne ANS server node and the ground ANS server node again to ensure the consistency of the airborne and ground status.

[0100] like Figure 10 As shown in the figure, when the coupling relationship between the ground agent node and the ground ANS server node changes:

[0101] After the ground agent node is successfully dynamically registered, the ground ANS server node updates the attributes and running status of multiple ground application software that have established a binding relationship with the ground agent node, and starts periodic heartbeat detection at the same time. When the heartbeat detection fails, it is determined that the running status of the ground agent node has failed, and the attributes and running status of multiple airborne application software that have established a binding relationship with the ground agent node are synchronized to the airborne ANS server node again.

[0102] This invention uses an application-layer address naming mechanism to hide the actual physical location of the software on both sides of the communication, improving the security of the interaction. Through an application-layer address-based addressing mechanism, dynamic registration, and system synchronization, it addresses the issue of onboard network planning updates caused by changes in the access point of mobile devices and the resident location of application software, enabling anytime, anywhere access and plug-and-play, improving the continuity of interaction.

[0103] It should be noted that in the description of the embodiments of the present invention, it should also be noted that, unless otherwise clearly specified and limited, the terms "setting" and "connection" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a direct connection, or an indirect connection through an intermediate medium. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances; the drawings in the embodiments are used to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings herein can be arranged and designed in various different configurations.

[0104] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. An onboard software addressing method based on application layer address, characterized in that: It is applied between the airborne side and the ground side; The airborne side includes an airborne agent node and an airborne ANS server node that establish a coupling relationship. The ground side includes a ground agent node and a ground ANS server node that establish a coupling relationship. The airborne ANS server node and the ground ANS server node establish a coupling relationship. The airborne / ground application software correspondingly establishes a binding relationship with the airborne / ground agent node; When the airborne / ground application software initiates a data transmission request, the message only carries the application layer address of the destination application software. The airborne / ground agent node initiates an application layer address resolution request, and then the airborne / ground ANS server node completes the resolution and feeds back the routing information of the destination application software to the airborne / ground application software, and the airborne / ground application software conducts data transmission.

2. The method for addressing onboard software based on application layer address according to claim 1, characterized in that: The addressing process between airborne application software is as follows: The airborne application software initiates a data request through the bound airborne agent node; The airborne agent node initiates an application layer address resolution request to the airborne ANS server node. The airborne ANS server node determines that the destination is an airborne application software according to the destination application layer address carried in the request, and judges whether the source and destination can interact by combining the cached status and policies of the destination airborne application software; after successful resolution, it returns an application layer address resolution response and carries the routing information of the destination airborne application software; The airborne application software conducts data transmission with the destination airborne application software.

3. The method for addressing onboard software based on application layer address according to claim 1 or 2, characterized in that: The addressing process between ground application software is as follows: The ground application software initiates a data request through the bound ground agent node; The ground agent node initiates an application layer address resolution request to the ground ANS server node. The ground ANS server node determines that the destination is a ground application software according to the destination application layer address carried in the request, and judges whether the source and destination can interact by combining the cached status and policies of the destination ground application software; after successful resolution, it returns an application layer address resolution response and carries the routing information of the destination ground application software; The ground application software conducts data transmission with the destination ground application software.

4. The method for addressing onboard software based on application layer address according to claim 1, characterized in that: The addressing process between the airborne application software and the ground application software is as follows: The airborne application software initiates a data transmission request to the destination ground application software through the bound airborne agent node; The airborne agent node initiates an application layer address resolution request to the airborne ANS server node. The airborne ANS server node determines that it is not its own airborne application software according to the destination application layer address carried in the request, and the resolution of the airborne ANS server node fails; The airborne ANS server node initiates an address resolution request to the ground ANS server node carrying the destination application layer address. The ground ANS server node determines that it is a ground application software according to the destination application layer address in the request; judges whether the source and destination can interact by combining the cached status and policies of the destination ground application software; after successful resolution, it returns an application layer address resolution response and carries the routing information of the destination ground application software; The airborne application software conducts data interaction with the destination ground application software.

5. The method for addressing onboard software based on application layer address according to claim 1, characterized in that: The application layer address name structure is: <Agent node>&<ANS server node>&<Network> Among them, each field in <…> is an identifier, and the identifiers are distinguished by the separator symbol "&". The parsing is to match the application layer name from right to left; the identifier is described by a string, and the separator symbol "." is used to represent multiple application software on the same proxy node; <proxy node> represents the name of the proxy node with the binding relationship to the application software; <ANS server node> represents the name of the ANS server node that establishes a coupling relationship with the proxy node; <network> represents the network name to which the application software belongs.

6. The method for addressing onboard software based on application layer address according to claim 1, characterized in that: It also includes that the airborne / ground application software completes binding and synchronization with the airborne / ground proxy node according to the dynamic registration mechanism; the airborne / ground proxy node establishes a coupling relationship with the airborne / ground ANS server node according to the dynamic registration mechanism.

7. The method for addressing onboard software based on application layer address according to claim 6, characterized in that: The dynamic registration mechanism includes: The airborne / ground application software is bound to at most one airborne / ground proxy node; the airborne / ground proxy node supports at least two airborne / ground application software to be bound to it; the binding of the airborne / ground application software to the airborne / ground proxy node is initiated by the application software; The airborne / ground proxy node is coupled to at most one airborne / ground ANS server node; the coupling relationship between the airborne / ground proxy node and the airborne / ground ANS server node should be actively initiated by the proxy node; After the airborne / ground application software, airborne / ground proxy node, and airborne / ground ANS server node complete the dynamic registration process, periodic heartbeat detection is started.

8. The method for addressing onboard software based on application layer address according to claim 1, characterized in that: It also includes a system synchronization mechanism that updates the attributes and operating states of the relevant application software when the binding relationship between the airborne / ground application software and the airborne / ground proxy node or the coupling relationship between the airborne / ground proxy node and the airborne / ground ANS server node changes.

9. The method for addressing onboard software based on application layer address according to claim 8, characterized in that: The system synchronization mechanism specifically includes: After the dynamic registration of the airborne application software is successful, the airborne proxy node synchronizes the attributes and operating states to the airborne ANS server node. After the airborne ANS server node completes the local update, it synchronizes the attributes and operating states to the ground ANS server node, and starts periodic heartbeat detection to update the attributes and operating states of the application software in real time; After the dynamic registration of the ground application software is successful, the ground proxy node synchronizes the attributes and operating states to the ground ANS server node, and starts periodic heartbeat detection to update the attributes and operating states of the application software in real time; After the dynamic registration of the airborne proxy node is successful, it synchronizes the attributes and operating states of multiple airborne application software with which the binding relationship is established to the airborne ANS server node. After the airborne ANS server node completes the local update, it synchronizes the attributes and operating states to the ground ANS server node, and starts periodic heartbeat detection to update the attributes and operating states of the application software in real time; After the dynamic registration of the ground proxy node is successful, the ground ANS server node updates the attributes and operating states of multiple ground application software with which the binding relationship is established to this ground proxy node, and starts periodic heartbeat detection to update the attributes and operating states of the application software in real time.

10. The method for addressing onboard software based on application layer address according to claim 9, characterized in that: When a mobile device is connected to an airborne terminal or a ground terminal, the system synchronization mechanism that changes the binding relationship between the airborne / ground application software and the airborne / ground agent node is used to update the attributes and operation status.

Images