A system integration-oriented aerial platform resource management method and device

Abstract

The application provides a kind of aviation platform resource management method and device for system integration, comprising: step 1, defining the standardized interface of aviation platform resource for system integration;Step 2, cross-platform resource registration and state maintenance;Step 3, design cross-platform resource service call process;In the resource management of multiple aviation platforms, the method of standardized interface design, cross-platform resource registration, multi-platform state maintenance and cross-platform service call is proposed, which can effectively support systematized aviation platform resource management and call, thereby contributing to the resource use of aviation platform fleet.

Description

Technical Field

[0001] This invention belongs to the field of resource management technology and relates to a method and apparatus for managing aviation platform resources for system integration. Background Technology

[0002] Information systems are evolving towards networking, digitalization, service orientation, and intelligence. As a core element of these systems, aviation platforms, supported by networking, are developing towards distributed collaboration. This distributed collaboration among heterogeneous aviation platforms presents entirely new requirements for resource and information service orientation, and for the intelligence of business operations and applications.

[0003] To achieve the goal of resource and information service-oriented aviation platforms within the information system, research on aviation platform resource management is urgently needed. Summary of the Invention

[0004] To address resource management issues in the application of aviation platform resources as services, this paper proposes a system-integrated aviation platform resource management method and apparatus based on the systematic network of the aviation platform. This enables the airborne platform to possess capabilities such as standardized interfaces for heterogeneous aviation platform resources, cross-platform resource registration and status maintenance, and resource service-oriented invocation, supporting resource utilization in distributed scheduling within the aviation platform fleet. The technical solution is as follows: Firstly, a system-integrated approach to aviation platform resource management is provided, including: Step 1: Define standardized interfaces for aviation platform resources oriented towards system integration; Step 2: Register and maintain the status of cross-platform resources; Step 3: Design a cross-platform resource service invocation process.

[0005] Optionally, step 1 specifically includes: (1) Determine the requirements for system integration business scenarios and complete the determination of resource requirements for support resources, flight resources, perception resources and mission resources; (2) Define the functions of perception-type resources and task-type resources that are frequently used across platforms. Describe the functions from the first level, second level and third level. Summarize and abstract the functions of different resources to complete the definition of resource functions, resource structures, resource interaction functions and resource interaction rules.

[0006] By defining the general functions and standardized interfaces of the system integration resources, the design of resource decoupling from a single platform to the system is completed.

[0007] Optionally, step 2 specifically includes: (1) In order to complete the resource aggregation and status unification of multiple platforms, the main platform summarizes the information of each slave platform in the network, and service management software resides on the main platform; (2) Based on the general function design and standardized interface definition, perform message conversion between the internal bus and data link, and complete the registration message and status reporting of resources and their corresponding service capabilities through the data link channel; (3) After receiving the service registration information from the slave platform, the master platform replies with the service registration status and maintains it according to the status reported by the slave platform to form a status table of multiple platforms and perform status summary operation of multiple platforms in the network.

[0008] Optionally, step 3 specifically includes: (1) Obtain cross-platform resource service requests. If the requested resource service is within this platform, the relevant service call is completed through the internal bus. (2) After receiving a service request from the platform, the system converts the data link message into the internal bus, calls the relevant service, and reports the call result to the main platform through the link to complete the service call process.

[0009] Furthermore, if the requested resource service is outside this platform, the internal bus-data link message is converted, and the service request is sent through the data link.

[0010] In a second aspect, an apparatus is provided for implementing the system integration-oriented aviation platform resource management method described in any one of the first aspects, comprising: Define the module, which is used to define standardized interfaces for aviation platform resources oriented towards system integration; The registration module is used for cross-platform resource registration and status maintenance; The design module is used to design cross-platform resource service invocation processes.

[0011] Optionally, the definition module includes: The determination unit is used to determine the requirements for system integration business scenarios and to determine the resource requirements for support resources, flight resources, perception resources, and mission resources. The definition unit is used to define the functions of perception-type resources and task-type resources that are frequently used across platforms. It describes the functions from the first level, second level, and third level, summarizes and abstracts the functions of different resources, and completes the definition of resource functions, resource structures, resource interaction functions, and resource interaction rules.

[0012] Optionally, the registration module includes: The aggregation unit is used by the main platform to aggregate information from each slave platform within the network. Service management software resides on the main platform. The first reporting unit is used to perform message conversion between the internal bus and data link according to the general function design and standardized interface definition, and to report the registration message and status of resources and their corresponding service capabilities through the data link channel. The maintenance unit is used by the main platform to receive service registration information from the slave platform, reply with the service registration status, maintain the status based on the status reported by the slave platform, form a status table for multiple platforms, and perform status summary operations for multiple platforms within the network.

[0013] Optionally, the design module includes: The acquisition unit is used to acquire cross-platform resource service requests. If the requested resource service is within the local platform, the relevant service call is completed through the internal bus; if the requested resource service is outside the local platform, the internal bus-data link message is converted and the service request is sent through the data link. The second reporting unit is used to receive a service request from the platform, convert the data link message into an internal bus, call the relevant service, and report the call result to the main platform through the link to complete the service call process.

[0014] Thirdly, an aviation platform resource management device for system integration is provided, including a processor and a memory, wherein the processor is configured to execute instructions stored in the memory, and the processor implements the aviation platform resource management method for system integration as described in any of the first aspects by executing the instructions.

[0015] Fourthly, a computer-readable storage medium is provided, wherein instructions are stored therein, which, when executed on a processing component of a computer, cause the processing component to perform the aviation platform resource management method for system integration as described in any of the first aspects.

[0016] This invention addresses the issues of resource management and service invocation for aviation platforms during system integration. It proposes a method for resource management and service invocation across multiple aviation platforms, supporting resource utilization in distributed scheduling within an aviation platform fleet and filling the gaps in existing research.

[0017] This invention proposes a standardized interface design, cross-platform resource registration, multi-platform status maintenance, and cross-platform service invocation method for resource management of multiple aviation platforms. It has reference value and can effectively support the systematic management and invocation of aviation platform resources, thereby facilitating the resource utilization of aviation platform fleets. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. The drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a diagram illustrating the resource aggregation and reporting process. Figure 2 Flowchart for initiating cross-platform service registration; Figure 3 Flowchart for cross-platform service registration confirmation; Figure 4 A flowchart for cross-platform service invocation; Figure 5 Workflow diagram for cross-platform service invocation; Figure 6 Diagram of the network simulation board composition; Figure 7 This is a flowchart of the resource management method of the present invention. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0021] The features and illustrative embodiments of various aspects of the present invention will now be described in detail. Numerous specific details are set forth in the following detailed description to provide a thorough understanding of the invention. However, it will be apparent to those skilled in the art that the invention may be practiced without requiring some of these specific details. The following description of embodiments is merely intended to provide a better understanding of the invention by illustrating examples of the invention. The invention is by no means limited to any specific setups and methods set forth below, but covers any improvements, substitutions, and modifications to structures, methods, and devices without departing from the spirit of the invention. Well-known structures and techniques are not shown in the drawings and the following description to avoid unnecessarily obscuring the invention.

[0022] It should be noted that, unless otherwise specified, the embodiments of the present invention and the features thereof can be combined with each other, and the various embodiments can be referenced and cited in each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0023] The present invention will be further described in detail below with reference to the embodiments and accompanying drawings, but the embodiments of the present invention are not limited thereto.

[0024] This invention focuses on the resource management problem in the application of aviation platform resources as services, and proposes an aviation platform resource management method oriented towards system integration. It solves problems such as the standardized design of distributed aviation platform resource interfaces, cross-platform resource registration and status maintenance, and resource service invocation, and supports the use of resources in distributed scheduling in aviation platform fleets.

[0025] This invention proposes a system integration-oriented aviation platform resource management method. This method takes system integration business scenarios as input, combines the resource management requirements of heterogeneous aviation platforms for mission-oriented purposes, and conducts research on system integration-oriented aviation platform resource management methods to support the use of distributed scheduling resources in aviation platform fleets.

[0026] See Figure 7 The implementation process of this method mainly includes defining standardized resource interfaces, registering and maintaining cross-platform resources and their status, and designing cross-platform resource service-oriented invocation processes, as detailed below: 1. Standardized interface definition for aviation platform resources oriented towards system integration: (1) Determine the requirements for system integration business scenarios. This step involves sorting out the resource requirements for support resources, flight resources, perception resources, and mission resources. (2) Detailed functional definitions are made for the perception-type resources and task-type resources that are frequently used across platforms. The functions are described in detail from the first level, second level and third level. The functions of different resources are summarized and abstracted, and the definitions of resource functions, resource structures, resource interaction functions and resource interaction rules are completed.

[0027] By defining the general functions and standardized interfaces of the system integration resources, the design of resource decoupling from a single platform to the system is completed.

[0028] 2. Perform cross-platform resource registration and status maintenance. (1) In order to complete the resource aggregation and status unification of multiple platforms, it is necessary to summarize the information of each slave node platform (also known as slave platform) in the network through the master node platform (also known as the master platform), where the service management software resides on the master node platform; (2) Based on the general function design and standardized interface definition, perform message conversion between the internal bus and data link, and report the registration message and status of resources and their corresponding service capabilities through the data link channel; (3) After receiving the service registration information from the slave platform device, the master platform replies with the service registration status and maintains it according to the status reported by the slave platform to form a status table of multiple platforms and summarize the status of multiple platforms in the network.

[0029] 3. Cross-platform resource service invocation process design Once the main platform completes the status maintenance of cross-platform resources and capabilities, resources and services within the network can be shared.

[0030] (1) Users of the main platform can trigger cross-platform resource service requests through the human-computer interaction interface. If the requested resource service is within the platform, the relevant service call is completed through the internal bus. If the requested resource service is outside the platform, the internal bus-data link message is converted and the service request is sent to the slave platform through the data link. (2) After receiving the service request from the platform, the data link message is converted into the internal bus, and the relevant service is called. The call result is reported to the main platform through the above link to complete the service call process.

[0031] This invention addresses the issues of resource management and service invocation for aviation platforms during system integration. It proposes a method for resource management and service invocation across multiple aviation platforms, supporting resource utilization in distributed scheduling within an aviation platform fleet and filling the gaps in existing research.

[0032] This invention proposes a standardized interface design, cross-platform resource registration, multi-platform status maintenance, and cross-platform service invocation method for resource management of multiple aviation platforms. It has reference value and can effectively support the systematic management and invocation of aviation platform resources, thereby facilitating the resource utilization of aviation platform fleets.

[0033] In one embodiment, the specific process for defining the standardized interface for aviation platform resources for system integration in this invention is as follows: (1) Organize and define the platform resources.

[0034] (2) Define the functions of the resources.

[0035] (3) Design the resource interaction function and its structure.

[0036] As shown in Table 1, (1) the platform resources can be sorted out and defined into support, flight, perception and mission categories, and then detailed sorting and definition of resources can be carried out according to specific equipment categories.

[0037] Table 1 Resource Sorting Definition Table

[0038] As shown in Table 2, (2) complete the functional definition of resources, mainly complete the functional classification definition of resources such as sensors and equipment, such as the first level is the detection function, the second level is the pointing control, signal transmission, echo reception and other functions, and the third level is the beam control, up-conversion, filtering and amplification, radiation, power amplifier and other functions. Table 2 Example of Resource Function Definition

[0039] As shown in Table 3, (3) complete the design of resource interaction functions, mainly complete the interaction definition of resources such as sensors and devices, such as executing tasks, providing feedback on task results, sending data, sending usage plans, etc.; as shown in Table 4, complete the design of resource interaction structure, and define the type, length, range, etc. of data in the interaction function.

[0040] Table 3. Example of Resource Interaction Function Design

[0041] Table 4. Example of Resource Interaction Structure Design

[0042] The process of cross-platform device discovery is as follows Figure 1 As shown, inter-machine communication devices follow an IP-based system or possess unique device IDs, enabling mutual addressing via IP or ID. Internal devices utilize a TSN network, each with its own independent IP address, which can be different from each other. Internal communication is conducted through a task processor (including a switch), while external communication is facilitated by communication, navigation, and identification equipment. Each internal device, according to standardized interface design requirements, reports its device ID, device status, and controllable parameters to the task processor for aggregation. The task processor then distributes these aggregated messages internally via the communication, navigation, and identification equipment. Upon receiving device status information from each platform in the cluster, the main platform aggregates the data and updates the corresponding resource status table in real time.

[0043] like Figure 2 As shown, after completing cross-platform resource discovery and aggregation, devices within the network can send service registration messages to the service management software of the main platform to complete service registration. The detailed process is as follows: the service reports its service registration message (service name, service unique identifier UUID, service function description, and service QoS description) to the data link management service via RPC communication components and the TSN communication protocol. The data link management service encapsulates the service registration message using an external message protocol and sends it to the main platform via the data link. Upon receiving the service registration message, the service management software residing on the main platform... Figure 3 As shown, once the service registration is confirmed, the service of the corresponding platform will be added to the service set within the network, and the service registration confirmation message will be sent back to the corresponding platform.

[0044] like Figure 4As shown, cross-platform service calls are initiated by users on the main platform through human-computer interaction software. After being encapsulated by RPC and TSN protocols, the data link management service performs intra-machine to inter-machine service call instruction conversion and sends the data link to the corresponding platform. The corresponding platform parses the service call request and then sends back the corresponding service message. The service call design for intra-machine interaction is shown in Table 5, and the service call design for inter-machine interaction is shown in Table 6.

[0045] Table 5. Cross-Platform Service Call - Internal Interface Design Examples

[0046] Table 6. Cross-Platform Service Call - External Interface Design Examples

[0047] In one embodiment, such as Figure 5 As shown, the human-computer interaction software resides on a regular PC, while the distributed resource management service resides on the D2000 hardware development machine via a service-oriented runtime framework. The inter-machine network simulation card is a terminal device that supports data link protocol simulation and wireless communication. The components of the inter-machine network simulation board are detailed below. Figure 6 As shown, the wireless communication simulation is implemented using a combiner and a power divider, and the board is an embedded semi-physical board. The above hardware and software constitute the complete operating environment.

[0048] The overall implementation example of service invocation is as follows: 1- The human-computer interaction control command that initiates the service call is called via the RPC protocol; 2- The distributed resource management service (master device) responds to human-machine interaction control commands and sends them to the inter-machine network simulation board 1 via the DDS+UDP protocol; After receiving the DDS+UDP protocol, the 3-inter-machine network simulation board 1 encapsulates the protocol into a custom TTNT message and sends it to the inter-machine network simulation board 2; 4-Inter-machine network simulation board 2 receives the TTNT protocol from inter-machine network simulation board 1 wirelessly; After completing protocol parsing, the 5-inter-machine network simulation board 2 sends the data to the distributed resource management service (slave device) via the DDS+UDP protocol. 6. After completing the protocol parsing, the distributed resource management service (slave device) provides feedback on the corresponding service content.

[0049] The service feedback response process repeats the process described in 6-1 above.

[0050] The above detailed embodiments are a description of the present invention. It should not be considered that the specific embodiments of the present invention are limited to these descriptions. For those skilled in the art, several simple deductions and substitutions can be made without departing from the concept of the present invention, and all of these should be considered to fall within the protection scope of the present invention.

Claims

1. A method for managing aviation platform resources oriented towards system integration, characterized in that, include: Step 1: Define standardized interfaces for aviation platform resources oriented towards system integration; Step 2: Register and maintain the status of cross-platform resources; Step 3: Design a cross-platform resource service invocation process.

2. The method according to claim 1, characterized in that, Step 1 is as follows: (1) Determine the requirements for system integration business scenarios and complete the determination of resource requirements for support resources, flight resources, perception resources and mission resources; (2) Define the functions of perception-type resources and task-type resources that are frequently used across platforms. Describe the functions from the first level, second level and third level. Summarize and abstract the functions of different resources to complete the definition of resource functions, resource structures, resource interaction functions and resource interaction rules.

3. The method according to claim 1, characterized in that, Step 2 is as follows: (1) The main platform summarizes the information of each slave platform in the network, and the service management software resides on the main platform; (2) Based on the general function design and standardized interface definition, perform message conversion between the internal bus and data link, and complete the registration message and status reporting of resources and their corresponding service capabilities through the data link channel; (3) After receiving the service registration information from the slave platform, the master platform replies with the service registration status and maintains it according to the status reported by the slave platform to form a status table of multiple platforms and perform status summary operation of multiple platforms in the network.

4. The method according to claim 1, characterized in that, Step 3 specifically involves: (1) Obtain cross-platform resource service requests. If the requested resource service is within this platform, the relevant service call is completed through the internal bus. (2) After receiving a service request from the platform, the system converts the data link message into the internal bus, calls the relevant service, and reports the call result to the main platform through the link to complete the service call process.

5. The method according to claim 4, characterized in that, If the requested resource service is outside this platform, the internal bus-data link message is converted, and the service request is sent through the data link.

6. An apparatus for implementing the aviation platform resource management method for system integration as described in any one of claims 1 to 5, characterized in that, include: Define the module, which is used to define standardized interfaces for aviation platform resources oriented towards system integration; The registration module is used for cross-platform resource registration and status maintenance; The design module is used to design cross-platform resource service invocation processes.

7. A resource management device for aviation platforms oriented towards system integration, characterized in that, It includes a processor and a memory, the processor being configured to execute instructions stored in the memory, the processor implementing the system integration-oriented aerospace platform resource management method according to any one of claims 1 to 5 by executing the instructions.

8. A computer-readable storage medium storing instructions that, when executed on a processing component of a computer, cause the processing component to perform the system integration-oriented aerospace platform resource management method according to any one of claims 1 to 5.

Images