Service management method, device and equipment for multi-platform avionics system

Through service registration and historical operation record management strategies, dynamic switching of layered and centralized management strategies, service management difficulties caused by the heterogeneity of avionics equipment in multi-platform avionics systems are solved, and the system's operating efficiency and adaptability are improved.

CN119003530APending Publication Date: 2024-11-22NORTHWESTERN POLYTECHNICAL UNIV
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411141174.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-20
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The heterogeneity of avionics equipment in multi-platform avionics systems leads to difficulties in service management, limiting the system's construction and operation efficiency.

Method used

The service registration and historical operation record management strategies are adopted, and the optimization strategy is determined based on the service quantity interval through dynamic switching through hierarchical management and centralized management strategies, and task response efficiency is improved.

Benefits of technology

It improves the operation efficiency of multi-platform avionics systems, avoids the inaccurate subjectivity of pre-specified management strategies, adapts to system changes, and enhances the system's adaptability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119003530A_ABST
    Figure CN119003530A_ABST
Patent Text Reader

Abstract

The invention discloses a service management method, device and equipment for a multi-platform avionics system, and relates to the technical field of avionics systems. According to the method, all avionics devices in the multi-platform avionics system are servitized in the form of avionics services, and historical operation records of the multi-platform avionics system are acquired for the avionics services which are registered by the avionics devices and are in a survival state; wherein different historical operation records correspond to different intervals divided according to a preset service number, and an optimal target service management strategy is determined and applied according to different system operation conditions under hierarchical management and centralized management strategies in the historical operation records corresponding to the service number interval in which the total number falls. And after a task request of the avionics equipment is received, the target avionics service corresponding to the task request is determined based on the target service management strategy, the task request is responded, and the historical operation record is updated. And the operation efficiency of the multi-platform avionics system is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of avionics systems, and in particular to a service management method, device and equipment for a multi-platform avionics system. Background Art

[0002] At present, in order to adapt to the new application environment, the mission execution style of future aviation equipment is developing from platform-centered to multi-platform systematic collaboration supported by information systems, and the degree of dependence on information is increasing. The avionics system must break through the limitations of a single platform and integrate manned aircraft, drones, information collection machines, etc. through a service sharing mechanism, that is, a multi-platform avionics system. The scope of mission execution is no longer limited to a formation composed of several multi-purpose aircraft in a target airspace, but has expanded to the coordinated execution of sea, land, air and space systems composed of ground command centers, information collection machines, transport aircraft, drones and airships.

[0003] On the one hand, due to the growth of the performance / quantity / complexity of the sensors in the airborne systems of avionics equipment, the airborne processing platform is required to improve the processing / network / storage / IO capabilities, improve the platform reliability and safety, improve the ability to resist harsh environments, and effectively control the volume / weight / power consumption and the life cycle cost. On the other hand, in practical applications, the airborne processing platform is required not only to enhance the connection between the various systems within the aircraft, but also to be able to process, filter and integrate various information to form a system that supports the execution of business across aircraft platforms.

[0004] Multi-platform avionics systems are composed of a variety of avionics equipment such as manned aircraft, information collection aircraft, transport aircraft and drones, showing obvious heterogeneity. Different equipment may also have different hardware configurations, including various sensors, load capacity and communication equipment. These differences provide multi-platform avionics systems with a wider range of functions and application potential. However, the heterogeneity of avionics equipment in multi-platform avionics systems also makes the management of services between avionics equipment more difficult, limiting the construction and operation efficiency of multi-platform avionics systems. Summary of the invention

[0005] Based on this, it is necessary to provide a service management method, device and equipment for a multi-platform avionics system in response to the above technical problems.

[0006] The present invention adopts the following technical solutions:

[0007] The present invention provides a service management method for a multi-platform avionics system, comprising:

[0008] Receive service registrations in the form of avionics services from various avionics devices in a multi-platform avionics system, and update the service status of each avionics service;

[0009] Acquire historical operation records of multi-platform avionics systems and current service status of each avionics service; wherein different historical operation records correspond to different intervals divided according to preset service quantities, and each historical operation record includes a service quantity interval, a service management strategy, and system operation status, wherein the service management strategy includes hierarchical management of avionics services and centralized management of avionics services;

[0010] According to the current service status of each avionics service, the number of avionics services currently in a live state is determined, and according to the system operation status corresponding to different service management strategies in the service quantity interval in which the avionics service falls, the preferred target service management strategy is determined;

[0011] Switch the current service management strategy to the target service management strategy, receive the task request of the avionics equipment, determine the target avionics service corresponding to the task request based on the target service management strategy, respond to the task request through the target avionics service, and update the historical operation record.

[0012] Optionally, each of the historical operation records includes: a unique identifier of the operation record, a service quantity interval, a service management policy, a minimum delay, a maximum delay, an average delay and the number of records.

[0013] Optionally, the hierarchical management of avionics services specifically includes:

[0014] Divide each avionics service into multiple service layers according to the preset maximum number of avionics services on a single layer;

[0015] The mapping relationship between each avionics service and its corresponding service layer is stored in a hash table;

[0016] When a task request of an avionics device is received, the service layer where the target avionics service corresponding to the task request is located is determined by querying the hash table, and the service layer is traversed to query the target avionics service.

[0017] Optionally, the centralized management of avionics services specifically includes:

[0018] An avionics service list is formed according to the avionics services that are currently in a live state, and when a task request of an avionics device is received, a target avionics service corresponding to the task request is searched from the avionics service list.

[0019] Optionally, determining the preferred target service management strategy according to the system operation conditions corresponding to different service management strategies in the service quantity interval into which the service falls specifically includes:

[0020] Under the hierarchical management strategy corresponding to the service quantity interval it falls into, determining the delay fluctuation under the hierarchical management strategy according to the corresponding maximum delay and minimum delay;

[0021] Under the centralized management strategy corresponding to the service quantity interval it falls into, determining the delay fluctuation under the centralized management strategy according to the corresponding maximum delay and minimum delay;

[0022] The maximum delay, average delay and delay fluctuation under different service management strategies are compared to determine the optimal target service management strategy.

[0023] The present invention provides a service management device for a multi-platform avionics system, comprising:

[0024] A receiving module, used for receiving service registration in the form of avionics services from various avionics devices in the multi-platform avionics system, and updating the service status of each avionics service;

[0025] A receiving module, used for receiving service registration in the form of avionics services from various avionics devices in the multi-platform avionics system, and updating the service status of each avionics service;

[0026] A system monitoring module, used to obtain the historical operation records of the multi-platform avionics system and the service status of each current avionics service; wherein different historical operation records correspond to different intervals divided according to the preset service quantity, and each historical operation record includes the service quantity interval, the service management strategy and the system operation status, and the service management strategy includes hierarchical management of avionics services and centralized management of avionics services;

[0027] The strategy management module is used to determine the number of avionics services currently in a live state according to the current service status of each avionics service, and determine the preferred target service management strategy according to the system operation status corresponding to different service management strategies in the service quantity interval in which the avionics service falls;

[0028] The service management module is used to switch the current service management strategy to the target service management strategy, receive the task request of the avionics equipment, determine the target avionics service corresponding to the task request based on the target service management strategy, respond to the task request through the target avionics service, and update the historical operation record.

[0029] The present invention provides a computer-readable storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the service management method of the multi-platform avionics system is implemented.

[0030] The present invention provides a computer device, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the service management method of the multi-platform avionics system when executing the program.

[0031] At least one of the above technical solutions adopted by the present invention can achieve the following beneficial effects:

[0032] The present invention serves each avionics device in a multi-platform avionics system in the form of an avionics service. For the avionics service that is registered and in a live state, the historical operation record of the multi-platform avionics system is obtained, wherein different historical operation records correspond to different intervals divided according to the preset service quantity. According to the different system operation conditions under the hierarchical management and centralized management strategies in the historical operation records corresponding to the service quantity interval into which the total quantity falls, the preferred target service management strategy is determined and applied, so that after receiving the task request of the avionics device, the target avionics service corresponding to the task request is determined based on the target service management strategy, the task request is responded to through the target avionics service, and the historical operation record is updated. The present invention divides the service quantity interval according to the preset service quantity, and manages the service for multiple registered services according to the strategy with better operation conditions in their historical operation records, thereby avoiding the inaccuracy caused by the subjectivity of the pre-specified management strategy, facilitating the construction of the multi-platform avionics system, and improving the operation efficiency of the multi-platform avionics system. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0034] Figure 1 A schematic flow chart of a service management method for a multi-platform avionics system provided by the present invention;

[0035] Figure 2 A schematic diagram of a request response process corresponding to a centralized management provided by the present invention;

[0036] Figure 3 A schematic diagram of a request response process corresponding to a hierarchical management provided by the present invention;

[0037] Figure 4 A schematic diagram of a multi-level service management structure provided by the present invention;

[0038] Figure 5 A schematic diagram of the operation logic of a multi-level service management provided by the present invention;

[0039] Figure 6A schematic diagram of the interaction process between a system monitoring module and a policy control module provided by the present invention;

[0040] Figure 7 A functional schematic diagram of a strategy control module provided by the present invention;

[0041] Figure 8 A schematic diagram of the interaction process between a policy control module and a system monitoring module provided by the present invention;

[0042] Fig. 9 A schematic diagram of the interaction process between a policy control module, a system monitoring module and a service management module provided by the present invention;

[0043] Fig.10 A functional schematic diagram of a service management module provided by the present invention;

[0044] Fig.11 A schematic diagram of the interaction process between a service management module and a policy control module provided by the present invention;

[0045] Fig.12 A schematic diagram of a service management device for a multi-platform avionics system provided by the present invention;

[0046] Fig.13 A schematic diagram of a computer device for implementing a service management method for a multi-platform avionics system provided by the present invention. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the specific embodiments of the present invention and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0048] At present, multi-platform avionics systems are composed of a variety of equipment such as manned aircraft, unmanned aerial vehicles, and information collection machines, showing obvious heterogeneity. The hardware configurations of different devices may also be different, including various sensors, load capacities, and communication equipment. These differences provide the system with a wider range of functions and application potential.

[0049] Therefore, in one or more embodiments of the present invention, the functions of these device platforms with software and hardware differences are uniformly abstracted into services, and service-level calls are implemented to "decouple" the services and device platforms, thereby achieving service-level interoperability.

[0050] After using service-oriented technology, the multi-platform avionics system stores all services of the current system and needs to manage the services. Especially when the number of services increases, the system load increases, so how to manage the services becomes a problem. For external requests, the response delay will increase, reducing the efficiency of system execution. Since the system stores historical data every time it runs, this historical data can be used for relevant learning, and the system service management strategy can be set based on the current system information and historical data.

[0051] To sum up, the service-oriented management of multi-platform avionics systems has become an important trend in the aviation industry, and the multi-level service management of multi-platform avionics systems enables multi-level service management technology to further improve the operating efficiency of multi-platform avionics systems.

[0052] The technical solutions provided by various embodiments of the present invention are described in detail below in conjunction with the accompanying drawings.

[0053] Figure 1 The following is a flow chart of a service management method for a multi-platform avionics system in the present invention, which specifically includes the following steps:

[0054] S101: receiving service registrations in the form of avionics services from various avionics devices in a multi-platform avionics system, and updating the service status of various avionics services.

[0055] Generally, in order to cope with the differences in avionics equipment in a multi-platform avionics system, each avionics equipment can register the services that can be provided by its own functions with the multi-platform avionics system (hereinafter referred to as the avionics system) in the form of avionics services, thereby isolating the services from the software and hardware resources of the avionics equipment, so that each avionics equipment can communicate and interact under a unified framework.

[0056] After receiving the avionics service registration of each avionics device, the registered avionics device can communicate based on the avionics system, such as mission request, provision of avionics services, etc. In order to avoid the avionics device being unable to provide its registered avionics service due to its own problems, resulting in invalid requests from other avionics devices and reducing the operating efficiency of the avionics system, the avionics system can also update the service status of each avionics service to maintain the validity of the registered avionics service.

[0057] The avionics system mentioned in the present invention may be a server installed in a multi-platform avionics system, or a device such as a desktop computer, a laptop computer, etc. that can execute the solution of the present invention. For the convenience of description, the following description will only be based on the avionics system as the execution subject.

[0058] S102: Obtain historical operation records of the multi-platform avionics system and the current service status of each avionics service; wherein different historical operation records correspond to different intervals divided according to preset service quantities, and each historical operation record includes a service quantity interval, a service management strategy, and a system operation status, and the service management strategy includes hierarchical management of avionics services and centralized management of avionics services.

[0059] For the service management of the avionics system, since avionics services are dynamically added and exited, the number of avionics services may increase over time, and the number of avionics services may accumulate to a considerable amount, at which point the load pressure on the service management capability of the avionics system will become very high. When an external task request arrives, since the number of avionics services is quite large, it will take a lot of time to find the avionics service corresponding to the task request, which greatly increases the response delay of the avionics system to the outside world and reduces the efficiency of the avionics system operation.

[0060] Therefore, avionics services can be managed based on the number of avionics services. Generally, avionics services can be managed through centralized management and hierarchical management. Centralized management means forming an avionics service list based on the currently alive avionics services. When receiving a task request from an avionics device, the target avionics service corresponding to the task request is queried from the avionics service list. Figure 2 The present invention is a schematic diagram of a request response process for centralized management.

[0061] For hierarchical management, each layer can correspond to a certain number of avionics services, so that the load of the avionics system can be shared through multiple layers when the avionics services are registered and called. When determining the target avionics service, the avionics system can first determine the service layer corresponding to the task request, and then search for the target avionics service in the service layer. The overall query time will be reduced due to the reduction in the number of avionics services involved, thereby reducing the response delay of the task request. Unlike the centralized management before the hierarchical system, only a centralized service management center can respond to external task requests, thereby reducing the response delay of the avionics system and improving the operation efficiency and task execution efficiency of the avionics system. Figure 3 The figure is a schematic diagram of a request response process corresponding to hierarchical management in the present invention.

[0062] However, it is not possible to arbitrarily perform hierarchical management of avionics services because, relatively speaking, when the number of available avionics services is small, centralized management of avionics services can respond to the outside world faster to a certain extent. Because under hierarchical management, the service management center needs to first obtain the service layer of the avionics service, that is, the hierarchical position, and then query the target avionics service at the corresponding service layer to complete the external task request.

[0063] Therefore, whether hierarchical management is needed needs to be determined based on actual conditions. The present invention uses historical operation records to determine whether hierarchical management is needed, thereby avoiding errors caused by manually specified strategies. As historical data increases, service management strategies will become more and more accurate.

[0064] When the multi-platform avionics system is first operated, different quantities of avionics services can be managed in advance with different strategies and in response to the task requests of the avionics equipment, thereby generating corresponding operation records under hierarchical management and centralized management, and using them as initial historical operation records for application in subsequent management processes. Among them, different quantities can cover different intervals divided by the preset service quantity. For example, assuming that the pre-divided intervals are 0-100, 101-200 and 201-300. At least three quantities in three intervals are required. This is only an example, and the specific details can be determined according to needs, and the present invention is not limited to this.

[0065] It can be seen that when the avionics system manages avionics services, it is necessary to implement adaptive and dynamic switching of service management strategies. Based on the above content, it is necessary to continuously update historical experience data, and it is necessary to continuously obtain service management strategies, and then complete the switching of service management strategies to improve the efficiency of avionics system execution. Therefore, in one or more embodiments of the present invention, the multi-level service management technology of the present invention is composed of a policy control module, a service management module and a system monitoring module. Its composition architecture is as follows Figure 4 shown.

[0066] Each time the avionics system is running, the system monitoring module will regularly obtain the historical operation records of the multi-platform avionics system and the current service status of each avionics service and send them to the policy control module, and the policy control module will send the recommended service management strategy to the service management module. Then the service management module will automatically switch the management mode to improve the operating efficiency of the avionics system.

[0067] During the operation of the avionics system, the system monitoring module will regularly deliver the current operation records of the avionics system to the strategy control module, and the strategy control module will update the historical database based on the current operation records, that is, the historical operation records. This cycle continuously improves the operation efficiency of the avionics system. The operation logic of multi-level service management is as follows: Figure 5 shown.

[0068] For the system monitoring module, since the policy management module needs to learn from the historical operation records of the system, it must be supported by relevant data. In addition, in order to achieve dynamic and adaptive switching of management modes for service management strategies, it is necessary to obtain service-related information when the system is running, and then obtain service management strategies suitable for the current system situation based on this information. This is what the system monitoring module needs to do.

[0069] From the above, we can see that the system monitoring module can be mainly divided into two major functions: service information monitoring function and system operation information monitoring function.

[0070] The function of service information monitoring is that the system monitoring module regularly obtains all current service information, and then sends this information to the policy management module. After obtaining the information, the policy management module obtains the appropriate service management strategy and then sends it to the service management module. The service management module switches the management mode.

[0071] The function of the system operation information monitoring function is that the system monitoring module regularly obtains information about the system operation, such as the delay in responding to external requests during operation (including minimum delay, maximum delay, and average delay), and then sends the information to the policy monitoring module. The module will update the historical database accordingly based on the message to facilitate subsequent updates of the service management policy.

[0072] The main interfaces required by the functions in the system monitoring module are as follows:

[0073] 1. Service information monitoring function:

[0074] a. Get service information interface: Get the required service information from all current services in the system.

[0075] b. Send service information interface: send the acquired service information to the policy management module.

[0076] 2. System operation information monitoring function:

[0077] a. Get system operation information: Get the relevant information of the system's previous operation cycle.

[0078] b. Send system operation information: Send the acquired system operation information to the policy management module.

[0079] In summary, the system monitoring module needs to regularly obtain information about all current services and the relevant results of the system's previous cycle from the system, and then send this information and results to the policy management module. The policy management module updates the historical database and obtains appropriate service management policies.

[0080] Specifically, the system monitoring module operation process may include the following steps:

[0081] 1) Regularly obtain system operation result information.

[0082] 2) Forward system operation result information to the policy management module.

[0083] 3) Regularly obtain the system’s current service status information.

[0084] 4) Forward the system’s current service status information to the policy management module.

[0085] For example, the system monitoring module can perform the following operations:

[0086] First, use the get_system_info method to periodically obtain the system operation result information within this period from the avionics system center, and then use the send_system_info method to forward the obtained system operation result information to the policy control module. Here, the service quantity is stored in the storage table in the form of intervals, so when sending the operation information, the service quantity can also be rounded up to the interval and then sent. For example, if the service quantity of a certain operation record is 160, and the service quantity interval size in the storage table is 50, then we round it down to 150, that is, the service quantity in the last sent record is 150. Of course, you can also not round up the interval, and directly correspond to the system operation records in different intervals in the form of intervals.

[0087] Secondly, the get_service_info method is used periodically to obtain the status information of the current system internal services from the avionics system center, and then the send_service_info method is used to forward the obtained system service status information to the policy control module. The interaction process between the system monitoring module and the policy control module is as follows: Figure 6 shown.

[0088] The main methods involved in the entire system monitoring module can be:

[0089] (1)struct system_info get_system_info()

[0090] Function: Get the result information of system operation within this cycle.

[0091] parameter:

[0092] Return value: result information of system operation during this period.

[0093] (2)bool send_system_info(const char*ip,constintport)

[0094] Function: Create a connection with the system management and control module.

[0095] Parameters: ip: policy control module ip, port: module port of the policy control module.

[0096] Return value: whether the sending is successful or not.

[0097] (3)struct service_info get_service_info(const char*ip,const intport)

[0098] Function: Get the service status information in the current system.

[0099] Parameters: ip: policy control module ip, port: module port of the policy control module.

[0100] Return value: service status information in the current system

[0101] S103: Determine the number of currently alive avionics services according to the current service status of each avionics service, and determine the preferred target service management strategy according to the system operation status corresponding to different service management strategies in the service quantity interval in which the avionics services fall.

[0102] S104: Switch the current service management strategy to the target service management strategy, receive the task request of the avionics equipment, determine the target avionics service corresponding to the task request based on the target service management strategy, respond to the task request through the target avionics service, and update the historical operation record.

[0103] The multi-platform avionics system will generate historical operation records during operation, which will also include the number of services when the system responds to the outside world during each operation, the maximum delay of the system response, the minimum delay of the system response, the average delay of the system response, etc. After the system monitoring module obtains the historical operation records and current service information, it can send them to the policy control module.

[0104] Afterwards, the required data in the historical operation records can be extracted and stored in the historical database through the policy control module. Each time the avionics system is completed, an operation record can be obtained. According to the service quantity interval of this operation record and the control strategy, the corresponding historical record is found, and then the relevant information of this operation record, such as the minimum delay, average delay, maximum delay, etc., is updated to the corresponding historical record, so as to provide corresponding reference for the subsequent avionics system operation.

[0105] From the functional aspect, the strategy control module can refer to the historical operation records of the avionics system, and then give the corresponding service management strategy according to the current situation in the avionics system. Then the avionics system can realize adaptive service management strategy switching to improve the operation efficiency of the avionics system. Therefore, the strategy control module can have three main functions: historical data update function, historical data acquisition function, and return service management strategy function. Figure 7 This is a functional diagram of a policy control module in the present invention.

[0106] The main interfaces that each function of the policy control module needs to provide are:

[0107] 1. Historical data update function:

[0108] a. Receiving operation data interface: receiving system operation records from the system monitoring module.

[0109] b. Update data interface: integrate the latest operation records and query the previous historical operation records in the historical database to update the existing historical operation records.

[0110] 2. Historical data acquisition function:

[0111] a. Get data interface: Get the data in the current history database according to the primary key information. It is called by the update data interface and the return service management strategy interface as a basic function.

[0112] 3. Return to service management policy function

[0113] a. Send data interface: provides the underlying interface for sending data, which is called by the return service management strategy interface.

[0114] b. Return service management strategy interface: query the historical database according to the service quantity information and call the corresponding send data interface to return the service management strategy to the service management module.

[0115] In summary, the policy control module is mainly responsible for receiving the data of the system operation process from the system monitoring module, storing it, and forming historical experience. In each storage, the historical operation records are updated to form a learning process, and finally returned to the service management module service management strategy.

[0116] Specifically, the policy control module operation process may include the following steps:

[0117] 1) During initialization, a table for storing system historical operation records needs to be created in the historical database.

[0118] 2) Receive the system's previous cycle operation record from the system monitoring module.

[0119] 3) Based on the operation record, query the historical database and then update the historical database

[0120] 4) Receive service-related information in the current system from the system monitoring module.

[0121] 5) Based on the service-related information, query the historical database to obtain the service management strategy suitable for the current situation, and return the strategy to the service management module.

[0122] For example, the policy control module can have the following operations:

[0123] First, it is necessary to create a table in the historical database for storing the historical operation records of the avionics system, and establish the corresponding database table system_run_record. The fields in the table and their meanings are shown in Table 1.

[0124] Table 1 Fields in the table and their meanings

[0125] Field Name Field meaning id Unique ID of the running record service_num Service Area manage_type Service Management Strategy min_delay Minimum delay max_delay Maximum delay avg_delay Average latency count Number of records

[0126] Then, the policy control module will start the monitoring methods recv_system_info and recv_service_info to continuously monitor the information from the system monitoring module, including system operation information and system service information.

[0127] After the policy control module recv_system_info method receives the system operation information (cur_service_num, cur_manage_type, cur_delay) from the system monitoring module, the policy control module uses query_system_info to query the historical database with (service quantity, service management policy) as the primary key. After obtaining the result, it will perform some calculations on the current data and update the table. The calculation method is:

[0128] Take out the original (service_num, manage_type, min_delay, max_delay, avg_delay, count),

[0129] The updated data is (service_num,mange_type,min(min_delay,cur_delay),max(max_delay,cur_delay),(avg_delay*count+cur_delay)) / (count+1),count+1);

[0130] The interaction process between the policy control module and the system monitoring module is shown as follows: Figure 8 shown.

[0131] Then the policy control module recv_service_info method receives the system current service information (service_num, qos, network_bandwidth) from the system monitoring module, which means (current system service quantity, service quality, network bandwidth).

[0132] The policy control module uses the query_manage_type method to query the database with service_num as the primary key, and obtains the manage_type corresponding to the service_num. Finally, send_manage_type is used to send manage_type to the service management module. The interaction process between the policy control module, the system monitoring module, and the service management module is shown in the following figure. Fig. 9 shown.

[0133] In the present invention, a TCP connection can be used between the system monitoring module and the policy control module to transmit data safely and accurately. The main methods involved in the entire policy monitoring module are:

[0134] (1)struct system_info recv_system_info(const char*ip,intport)

[0135] Function: Create a connection with the system management and control module.

[0136] Parameters: ip: policy control module ip, port: module port of the policy control module.

[0137] Return value: Received system operation information record.

[0138] (2)struct service_info recv_service_info(const char*ip,intport)

[0139] Function: Create a connection with the system management and control module.

[0140] Parameters: ip: policy control module ip, port: module port of the policy control module.

[0141] Return value: service information received in the current system.

[0142] (3)struct system_info query_system_info(int service_num,intmanage_type)

[0143] Function: Query the database for historical system operation information.

[0144] Parameters: service_num: service number, manage_type: service management strategy.

[0145] Return value: the queried system historical operation information.

[0146] (4)bool update_system_info(int service_num,intmanage_type,doubledelay)

[0147] Function: Update database information.

[0148] Parameters: service_num: service number, manage_type: service management strategy, delay: system delay

[0149] Return value: whether the update is successful.

[0150] (5)bool send_manage_type(SOCKET conn_manage_type)

[0151] Function: Send service management policies to the service management module

[0152] Parameters: conn_manage_type: TCP connection established between the policy control module and the service management module

[0153] Return value: whether the sending is successful.

[0154] Finally, for the aforementioned service management module, from the functional aspect, the service management module must first support the external device platform to register services to the multi-platform avionics system, then receive policies from the policy management module and perform service management switching, and finally forward the request to the corresponding layer of the service. Therefore, the service management module mainly has service registration function, service management switching function, and request forwarding function. Fig.10 It is a functional schematic diagram of a service management module in the present invention.

[0155] The main interfaces required for each function are as follows:

[0156] 1. Service registration function:

[0157] a. Receive service interface: Receive data from avionics services registered by other avionics equipment.

[0158] b. Storage service interface: stores new data (data that previously had no relevant information in the database).

[0159] 2. Service management switching function:

[0160] a. Get service interface: Get all current avionics services.

[0161] b. Service layering interface: All avionics services are layered and a mapping table between avionics services and layers is set.

[0162] 3. Request forwarding function

[0163] a. Find service interface: Find the layer corresponding to a certain avionics service.

[0164] b. Request forwarding interface: forwards the task request to the corresponding layer of the avionics service.

[0165] To summarize, the service management module needs to receive the service management policy from the policy control module, then switch the service management mode, and finally forward the task request to the corresponding avionics service to complete the response.

[0166] Specifically, the service management module operation process includes the following steps:

[0167] 1) Open the service registration listening program to receive the avionics service registration request from the outside world. After receiving it, add the avionics service to the avionics system to complete the avionics service registration. This program is always open to receive registration requests.

[0168] 2) Open the external request listening program to receive task request information from the outside world. This program is always open to receive external non-service registration requests.

[0169] 3) Start the service policy monitoring program to receive the service management policy from the policy management module.

[0170] 4) Based on the received service management policy, the service management policy switching program is called to perform adaptive switching of the service management policy.

[0171] 5) After receiving the request from the outside, according to the current service management strategy, the request is forwarded to the location of the corresponding avionics service, and the avionics service responds accordingly.

[0172] For example, the service management module can have the following operations:

[0173] First, the service management module uses the recv_registe and recv_request methods to continuously monitor service registration requests and non-registration requests from the outside world, and defines the service representation as a structure service, whose internal variables are shown in Table 2.

[0174] Table 2 Internal variables

[0175]

[0176] After receiving the avionics service registration request, the service management module uses the add_service method to add the avionics service to the system.

[0177] Then, the service management policy is received from the policy control module, and the switch_manage_type method is used to modify the service management policy to complete the switching of the service management policy from centralized to hierarchical or from hierarchical to centralized.

[0178] When avionics services are managed in layers, the server may divide each avionics service into multiple service layers according to a preset maximum number of single-layer avionics services, and save the mapping relationship between each avionics service and its corresponding service layer through a hash table. When a task request from an avionics device is received, the service layer where the target avionics service corresponding to the task request is located is determined by querying the hash table, and the service layers are traversed to query the target avionics service.

[0179] Since service hierarchical management is used, when an external task request arrives, it is necessary to find the service layer where the avionics service corresponding to the task request is located according to the task request. Therefore, the system can establish an index table to record the mapping relationship between avionics services and service layers, as shown in the following Table 3, where the service number 1001001 corresponds to service layer 1, and the service number 2001003 corresponds to service layer 4:

[0180] Table 3 Mapping relationship

[0181] Service Tag Layer number 1001001 1 2001003 4 ... ...

[0182] For the specific implementation of each layer here, in one or more embodiments of the present invention, multi-threading technology may be used, where the main thread serves as the avionics system service management center, and then n (n is the number of layers) child threads are started to start the layers. When the request reaches the main thread of the management center, the main thread searches the mapping relationship table to find the corresponding service layer, and then the main thread hands the request to the child thread, that is, requests the corresponding service layer, to perform corresponding avionics service search and task request forwarding.

[0183] When the avionics services are centrally managed, the server may form an avionics service list based on the currently alive avionics services, and when receiving a task request from an avionics device, query the avionics service list for the target avionics service corresponding to the task request.

[0184] Finally, after receiving the task request from the outside world, the search_service_location method is used to find the location of the avionics service in the task request, and then the send_request method is used to forward the task request to the corresponding avionics service, and the avionics service completes the corresponding response.

[0185] In one or more embodiments of the present invention, when the server determines the preferred target service management strategy based on the system operation conditions corresponding to different service management strategies in the service quantity interval it falls into, it can determine the delay fluctuation under the hierarchical management strategy corresponding to the service quantity interval it falls into according to the corresponding maximum delay and minimum delay; and determine the delay fluctuation under the centralized management strategy corresponding to the service quantity interval it falls into according to the corresponding maximum delay and minimum delay; compare the maximum delay, average delay and delay fluctuation under different service management strategies, and determine the preferred target service management strategy.

[0186] For example, assuming that the number of avionics services in the current system is x, select the operation records of both centralized management and hierarchical management in the interval of historical operation records in which x falls as reference. For example, if the current number of services is 1510, and the service number intervals in the historical records are 1450-1500, 1501-1550, etc., then select the operation records of both centralized management and hierarchical management in the interval of 1501-1550 as reference. Let centralized management be y1, and let hierarchical management be y2.

[0187] Secondly, the corresponding strategy can be selected based on the delay information corresponding to the records y1 and y2. If only the average running time is considered, the preferred target service management strategy can be determined based on the average delay in y1 and y2. If it is also considered that only a certain upper limit can be accepted for the delay, then it is necessary to first check whether the maximum delay meets the requirements and then make a selection based on the average delay. If the delay fluctuation also needs to be considered, then on the basis of the average delay, the difference between the minimum delay and the maximum delay is considered as a fluctuation reference. In actual situations, the management strategy can be selected according to needs.

[0188] Fig.11 The figure is a schematic diagram of the interaction process between a service management module and a policy control module in the present invention.

[0189] The main methods involved in the entire service management module are:

[0190] (1)struct service recv_registe()

[0191] Function: Receive avionics service registration request

[0192] parameter:

[0193] Return value: Received avionics service structure.

[0194] (2)struct request service recv_request()

[0195] Function: Receive external non-service registration requests

[0196] parameter:

[0197] Return value: the received task request structure.

[0198] (3)intmanage_type recv_manage_type()

[0199] Function: Receive service management policies from the policy control module

[0200] parameter:

[0201] Return value: the received service management policy.

[0202] (4)bool add_service(services)

[0203] Function: Add services to the avionics system

[0204] parameter:

[0205] Return value: whether the addition is successful or not

[0206] (5)bool switch_manage_type(intmanage_type)

[0207] Function: The service management module switches the service management strategy

[0208] parameter:

[0209] Return value: whether the switch is successful or not

[0210] (6)location search_service_location(const char*service_name)

[0211] Function: Find the service layer where the avionics service is located

[0212] Parameters: service_name: service name

[0213] Return value: the service layer where the avionics service is located

[0214] (7)bool send_request(location loc)

[0215] Function: Forward mission request to avionics service

[0216] parameter:

[0217] Return value: whether the forwarding is successful or not

[0218] based on Figure 1 The service management method of the multi-platform avionics system shown in the figure serves each avionics device in the multi-platform avionics system in the form of avionics service, obtains the historical operation record of the multi-platform avionics system for the avionics service that is registered and in the survival state, wherein different historical operation records correspond to different intervals divided according to the preset service quantity, and determines and applies the preferred target service management strategy according to the different system operation conditions under the hierarchical management and centralized management strategies in the historical operation records corresponding to the service quantity interval into which the total quantity falls, so that after receiving the task request of the avionics device, the target avionics service corresponding to the task request is determined based on the target service management strategy, the task request is responded to through the target avionics service, and the historical operation record is updated. The present invention divides the service quantity interval according to the preset service quantity, performs service management for multiple services after registration according to the strategy with better operation conditions in their historical operation records, avoids the inaccuracy caused by the subjectivity of the pre-specified management strategy, facilitates the construction of the multi-platform avionics system, and improves the operation efficiency of the multi-platform avionics system.

[0219] When applying the service management method of the multi-platform avionics system provided by the present invention, it is not necessary to Figure 1 The steps are executed in the order shown. The specific execution order of the steps can be determined according to needs, and the present invention does not limit this.

[0220] The above is a service management method for a multi-platform avionics system provided by one or more embodiments of the present invention. Based on the same idea, the present invention also provides a corresponding service management device for a multi-platform avionics system, such as Fig.12 shown.

[0221] Fig.12 A schematic diagram of a service management device for a multi-platform avionics system provided by the present invention includes:

[0222] The receiving module 201 is used to receive service registrations performed by various avionics devices in the multi-platform avionics system in the form of avionics services, and to update the service status of various avionics services;

[0223] The system monitoring module 202 is used to obtain the historical operation records of the multi-platform avionics system and the service status of each current avionics service; wherein each historical operation record includes the number of services and the service management strategy, and the service management strategy includes hierarchical management of avionics services and centralized management of avionics services;

[0224] The policy management module 203 is used to determine the number of currently alive avionics services according to the current service status of each avionics service, and match it with the number of services in the historical operation record to determine the target service management policy corresponding to the matched historical operation record;

[0225] The service management module 204 is used to switch the current service management strategy to the target service management strategy, receive the task request of the avionics equipment, determine the target avionics service corresponding to the task request based on the target service management strategy, and respond to the task request through the target avionics service.

[0226] The specific definition of the service management device of the multi-platform avionics system can be found in the definition of the service management method of the multi-platform avionics system mentioned above, which will not be repeated here. Each module in the service management device of the multi-platform avionics system can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0227] The present invention also provides a computer-readable storage medium, which stores a computer program, which can be used to execute the above Figure 1 A service management method for multi-platform avionics systems is provided.

[0228] The present invention also provides Fig.13 The structural diagram of the computer device shown in FIG. Fig.13 As shown in the figure, at the hardware level, the computer device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include other hardware required for the business. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it to achieve the above Figure 1 A service management method for multi-platform avionics systems is provided.

[0229] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided by the present invention can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0230] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present invention.

Claims

1. A service management method for a multi-platform avionics system, characterized in that: include: Receive service registrations in the form of avionics services from various avionics devices in a multi-platform avionics system, and update the service status of each avionics service; Acquire historical operation records of multi-platform avionics systems and current service status of each avionics service; wherein different historical operation records correspond to different intervals divided according to preset service quantities, and each historical operation record includes a service quantity interval, a service management strategy, and system operation status, wherein the service management strategy includes hierarchical management of avionics services and centralized management of avionics services; According to the current service status of each avionics service, the number of avionics services currently in a live state is determined, and according to the system operation status corresponding to different service management strategies in the service quantity interval in which the avionics service falls, the preferred target service management strategy is determined; Switch the current service management strategy to the target service management strategy, receive the task request of the avionics equipment, determine the target avionics service corresponding to the task request based on the target service management strategy, respond to the task request through the target avionics service, and update the historical operation record.

2. The service management method for a multi-platform avionics system according to claim 1, characterized in that: Each of the historical operation records includes: a unique identifier of the operation record, a service quantity interval, a service management strategy, a minimum delay, a maximum delay, an average delay and the number of records.

3. The service management method for a multi-platform avionics system according to claim 1, characterized in that: The hierarchical management of avionics services specifically includes: Divide each avionics service into multiple service layers according to the preset maximum number of avionics services on a single layer; The mapping relationship between each avionics service and its corresponding service layer is stored in a hash table; When a task request of an avionics device is received, the service layer where the target avionics service corresponding to the task request is located is determined by querying the hash table, and the service layer is traversed to query the target avionics service.

4. The service management method for a multi-platform avionics system according to claim 1, characterized in that: The centralized management of avionics services specifically includes: An avionics service list is formed according to the avionics services that are currently in a live state, and when a task request of an avionics device is received, a target avionics service corresponding to the task request is searched from the avionics service list.

5. The service management method for a multi-platform avionics system according to claim 2, characterized in that: The determining of the preferred target service management strategy according to the system operation conditions corresponding to different service management strategies in the service quantity interval specifically includes: Under the hierarchical management strategy corresponding to the service quantity interval it falls into, determining the delay fluctuation under the hierarchical management strategy according to the corresponding maximum delay and minimum delay; Under the centralized management strategy corresponding to the service quantity interval it falls into, determining the delay fluctuation under the centralized management strategy according to the corresponding maximum delay and minimum delay; The maximum delay, average delay and delay fluctuation under different service management strategies are compared to determine the optimal target service management strategy.

6. A service management device for a multi-platform avionics system, characterized in that: include: A receiving module, used for receiving service registration in the form of avionics services from various avionics devices in the multi-platform avionics system, and updating the service status of each avionics service; A system monitoring module, used to obtain the historical operation records of the multi-platform avionics system and the service status of each current avionics service; wherein different historical operation records correspond to different intervals divided according to the preset service quantity, and each historical operation record includes the service quantity interval, the service management strategy and the system operation status, and the service management strategy includes hierarchical management of avionics services and centralized management of avionics services; The strategy management module is used to determine the number of avionics services currently in a live state according to the current service status of each avionics service, and determine the preferred target service management strategy according to the system operation status corresponding to different service management strategies in the service quantity interval in which the avionics service falls; The service management module is used to switch the current service management strategy to the target service management strategy, receive the task request of the avionics equipment, determine the target avionics service corresponding to the task request based on the target service management strategy, respond to the task request through the target avionics service, and update the historical operation record.

7. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

8. A computer device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method described in any one of claims 1 to 5 is implemented.