Automatic identification and management method and device for equipment in airborne server cluster

Abstract

The invention discloses a method and a device for automatically identifying and managing equipment in an airborne server cluster, and relates to the field of airborne server clusters, and the method comprises the following steps of: defining an identifier: according to the scale of the airborne server cluster, defining a unified identifier bit; equipment identification: identifying a unified identification bit corresponding to the slot according to the level of the equipment inserted into the slot; and equipment management: reporting the management information corresponding to the airborne server to a background maintenance system along with the unified identification bit through a data transmission bus, and carrying out airborne server equipment management according to an airborne server interaction protocol. And the maintenance difficulty of maintenance personnel is greatly reduced.

Description

Technical Field

[0001] This application relates to the field of airborne server clusters, and particularly to a method and device for automatically identifying and managing devices within an airborne server cluster. Background Art

[0002] Currently, most airborne servers are deployed independently, and various servers rely solely on traditional physical tags to identify and manage their locations / regions / slots. However, the following problems are faced:

[0003] Firstly, with the continuous increase in the cabinet-style, centralized deployment and quantity of airborne servers, relying solely on traditional methods for location / region / slot identification will greatly increase the workload of device searching during the maintenance and management process and reduce work efficiency;

[0004] Secondly, general interface servers have interchangeability requirements. When a server needs to be replaced / added due to business requirements or equipment failures, a series of tasks such as remaking physical tags and updating the models, numbers, etc. stored in the background need to be carried out, increasing the maintenance workload;

[0005] Finally, in the traditional method, maintenance personnel need to find the corresponding device and manage and maintain it through the debugging port, and one-key maintenance cannot be performed in the background. Summary of the Invention

[0006] Aiming at the above deficiencies in the prior art, the present invention provides a method and device for automatically identifying and managing devices within an airborne server cluster, which solves the problem of difficultly and quickly identifying the location of an airborne server and performing centralized management and maintenance of multiple servers in the environment of an airborne server cluster.

[0007] To achieve the above invention purpose, the technical solution adopted by the present invention is: A method for automatically identifying and managing devices within an airborne server cluster, including:

[0008] S1. Define an identifier: Define a unified identifier bit according to the scale of the airborne server cluster;

[0009] S2. Device identification: Identify the unified identifier bit corresponding to the slot according to the level of the device inserted into the slot;

[0010] S3. Device management: Report the management information corresponding to the airborne server to the background maintenance system along with the unified identifier bit through the data transmission bus, and manage the airborne server devices according to the airborne server interaction protocol.

[0011] Furthermore: S2 includes:

[0012] S201. In response to the insertion of an airborne server into a slot, inject high and low levels into the corresponding electrical interface of the slot;

[0013] S202. Identify the high and low levels of the corresponding telecommunications interface through the on-board server, and identify the unified identification bit corresponding to the slot.

[0014] Furthermore, in S3, the types of device management include heartbeat detection, status query, fault reporting, and instruction request operations.

[0015] Furthermore, in S3, the heartbeat detection process supports periodic detection and node disconnection confirmation mechanisms. The interaction protocol timing sequence of the heartbeat detection process is: the background maintenance system sends a heartbeat request to the on-board server, and the on-board server sends a heartbeat response to the background maintenance system.

[0016] Furthermore, in S3, the interaction protocol timing sequence of the status query process is: the background maintenance system sends a status query request to the on-board server, and the on-board server sends a status query response to the background maintenance system.

[0017] Furthermore, in S3, fault reporting supports real-time reporting. The interaction protocol timing sequence of the fault reporting process is: the on-board server reports a fault to the background maintenance system, and the background maintenance system responds to the fault of the on-board server.

[0018] Furthermore, instruction requests include remote power-on, power-off, reset, and restart. The interaction protocol timing sequence of the instruction request process is: the background maintenance system sends a control instruction request to the on-board server, and the on-board server sends a control instruction response to the background maintenance system.

[0019] Furthermore, the message interface of the interaction protocol includes:

[0020] Destination address, used to record the address information of the request initiator, aligned in 8 bits;

[0021] Source address, used to record the address information of the request responder, aligned in 8 bits;

[0022] Message sequence number, the length varies according to the type of on-board control bus adopted;

[0023] Message type, the minimum set includes heartbeat request / response, fault reporting / response, status query request / response, control instruction request / response, 1 byte;

[0024] Data length, used to specify the length of the data field, 2 bytes;

[0025] Data field, the actual requirements are defined by the upper-layer service itself, 0 to K bytes, where K represents the maximum length of the data field;

[0026] Checksum field, used to check the check value of all bytes before the field, 2 bytes.

[0027] To achieve the above-mentioned invention object, the present invention also adopts the following technical solution: An automatic identification and management device for equipment in an airborne server cluster, which is used to execute the above method, includes:

[0028] A background maintenance system, which is used to identify the unified identification bit information corresponding to the airborne server and conduct centralized management and maintenance on the airborne server;

[0029] A control bus, which is used for data transmission between the background maintenance system and the airborne server;

[0030] An airborne server deployment area, which is used to store the airborne server.

[0031] Furthermore: The backplane of the airborne server slot is provided with a telecommunication interface for identifying the unified identification bit.

[0032] The beneficial effects of the present invention are:

[0033] 1. Based on the combination of the unified identification bit and the telecommunication interface, the automatic identification of the location information of the airborne servers in a large-scale airborne server cluster is realized, greatly reducing the maintenance difficulty of the maintenance personnel;

[0034] 2. Based on the centralized management and interaction protocol of multiple types of airborne control buses, the management and control functions of a large-scale airborne server cluster are realized. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 It is a flowchart of the method for automatic identification and management of equipment in an airborne server cluster;

[0036] Figure 2 It is a schematic diagram of the deployment of an airborne server cluster;

[0037] Figure 3 It is a schematic diagram of the interaction protocol timing;

[0038] Figure 4 It is a framework diagram of the automatic identification and management device for equipment in an airborne server cluster. DETAILED DESCRIPTION OF THE INVENTION

[0039] The following describes the specific implementation manners of the present invention to facilitate those skilled in the art of the present technology to understand the present invention. However, it should be clear that the present invention is not limited to the scope of the specific implementation manners. For those ordinary skilled in the art of the present technology, as long as various changes are within the spirit and scope of the present invention defined and determined by the appended claims, these changes are obvious, and all inventions and creations using the inventive concept of the present invention are within the scope of protection.

[0040] As Figure 1 shown, in an embodiment of the present invention, there is provided a method for automatic identification and management of equipment in an airborne server cluster, including:

[0041] S1. Define identification: Define a unified identification bit according to the scale of the airborne server cluster;

[0042] S2. Device identification: Identify the unified identification bit corresponding to the slot according to the level of the slot where the device is inserted;

[0043] S3. Device management: Report the management information corresponding to the airborne server to the background maintenance system along with the unified identification bit through the data transmission bus, and manage the airborne server devices according to the airborne server interaction protocol.

[0044] Among them, as Figure 2 shown, a scenario of the latter airborne server cluster in practical applications is provided: The airborne server cluster is deployed by region, cabinet, and slot:

[0045] By region: Deployed in different regions (such as Figure 2 Middle Region #1 to Region #N), and it is distributed in the front cabin, middle cabin, rear cabin and other electronic equipment cabins of the aircraft;

[0046] By cabinet: In the same region (such as Figure 2 Middle Region #1), multiple cabinets are deployed;

[0047] By slot: In the same cabinet (such as Figure 2 Cabinet #1 in Middle Region #1), multiple slots are deployed, and the corresponding airborne servers (such as Figure 1 Server #1 to Server #X1) are inserted into different slots;

[0048] Among them, the number of regions, the number of cabinets in each region, and the number of slots in each cabinet are all freely set according to actual needs.

[0049] Based on the above method for dividing the airborne server cluster, in this embodiment, the unified identification bit includes a region identification bit (AreaID, X bits), a cabinet identification bit (RackID, Y bits), and a slot identification bit (SlotID, Z bits), where the number of bits of X, Y, and Z can vary according to the scale of the airborne server cluster;

[0050] As an optimization of this solution, S2 includes:

[0051] S201. In response to the insertion of the airborne server into the slot, inject high and low levels into the corresponding electrical interface of the slot;

[0052] S202. Identify the unified identification bit corresponding to the slot by the airborne server identifying the high and low levels of the corresponding electrical interface.

[0053] In the deployment scheme of dividing areas, cabinets, and slots provided in this embodiment, each slot should include a telecommunications interface corresponding to AreaID, RackID, and SlotID. Each telecommunications interface injects high and low levels through the slot backplane. After the recorded server is inserted into the slot, it can automatically identify the high and low levels of the corresponding telecommunications interface, and then obtain the values of AreaID, RackID, and SlotID corresponding to this slot;

[0054] After the airborne server identifies AreaID, RackID, and SlotID, it reports the above ID values, as well as information such as equipment, software, and faults, to the background maintenance system through the control bus during power-on, periodically, or for maintenance.

[0055] It should be noted that this embodiment only provides a deployment scheme in an actual application scenario as an illustration of the scheme, and is not limited to the deployment scheme of dividing areas, cabinets, and slots. According to the actual situation, it can also be set as a deployment scheme of dividing aircraft, areas, cabinets, and slots, or dividing fleets, aircraft, areas, cabinets, and slots, etc., so as to realize the identification and management of airborne server clusters on a multi-aircraft and multi-fleet scale.

[0056] Specifically, in S3, the types of device management should at least include heartbeat detection, status query, fault reporting, and instruction request operations implemented based on multiple airborne buses.

[0057] In particular, the supported airborne buses should include but are not limited to Ethernet, ARINC 429, I2C, RS232 / 485, etc.; the protocol interaction process supports message retransmission and confirmation mechanisms.

[0058] In this embodiment, the heartbeat detection process supports periodic detection and node disconnection confirmation mechanisms. As shown in Figure 3 (a), the interaction protocol timing of the heartbeat detection process is: the background maintenance system sends a heartbeat request to the airborne server, and the airborne server sends a heartbeat response to the background maintenance system; fault reporting supports real-time reporting. As shown in Figure 3 (b), the interaction protocol timing of the fault reporting process is: the airborne server reports a fault to the background maintenance system, and the background maintenance system responds to the fault of the airborne server; as shown in Figure 3 (c), the interaction protocol timing of the status query process is: the background maintenance system sends a status query request to the airborne server, and the airborne server sends a status query response to the background maintenance system; instruction requests include but are not limited to remote power-on, power-off, reset, and restart. As shown in Figure 3 (d), the interaction protocol timing of the instruction request process is: the background maintenance system sends a control instruction request to the airborne server, and the airborne server sends a control instruction response to the background maintenance system.

[0059] The definition of the message interface of the interaction protocol is shown in Table 1:

[0060] Table 1 Message Interface of the Interaction Protocol

[0061]

[0062] Among them, the destination address is used to record the address information of the request originator, aligned in 8 bits;

[0063] The source address is used to record the address information of the request responder, aligned in 8 bits;

[0064] The message sequence number varies in length according to the type of airborne control bus adopted;

[0065] The message type, the minimum set includes heartbeat request / response, fault reporting / response, status query request / response, control instruction request / response, 1 byte;

[0066] The data length is used to specify the length of the data field, 2 bytes;

[0067] The data field, the actual requirements are defined by the upper-layer service itself, 0 to K bytes, where K represents the maximum length of the data field;

[0068] The check field is used to check the check value of all bytes before the field, 2 bytes.

[0069] In particular, the storage method of the destination address and the source address is as follows:

[0070] ((~AreaID)<<(Y+Z))|((~RackID)<<Z)|(~SlotID)

[0071] Among them, << represents left shift, that is, put SlotID into the rightmost side of the destination address / source address storage space, put RackID after shifting left by Z bits, and then put AreaID after shifting left by Y bits.

[0072] Among them, the data field is an extensible field, supporting extension according to the actual usage scenario, which improves the compatibility of this solution.

[0073] As Figure 4 shown, this application also discloses a device for automatic identification and management of devices in an airborne server cluster for executing the above solution, including:

[0074] The background maintenance system is used to identify the unified identification bit information corresponding to the airborne server and perform centralized management and maintenance on the airborne server;

[0075] The control bus is used for data transmission between the background maintenance system and the airborne server;

[0076] Airborne server deployment area, including airborne server slots for storing airborne servers.

[0077] Preferably, the device may further include a data transmission bus. Each type of device respectively leads out a control bus to cross-link with the backbone network control bus. At the same time, the device leads out another data transmission bus to cross-link with the backbone network data transmission bus. The background maintenance system is respectively cross-linked with the backbone network data transmission bus and the control bus. The data transmission bus is used to assist the control bus in performing device management and reduce the data transmission pressure on the control bus.

[0078] Preferably, to ensure the reliability of airborne server identification and reporting, the control bus can be designed in a primary and standby redundant mode. Only when the primary control bus fails, the standby control bus takes over the interaction with the background maintenance system instead of the primary bus.

[0079] Preferably, the backplane of the airborne server slot is provided with a telecommunication interface for identifying the unified identification bit. This interface is used to inject the high and low levels of the relevant unified identification bit when the airborne server is inserted into the slot, where the high level represents 1 and the low level represents 0.

[0080] The above embodiments are only used to illustrate the technical solutions of the present application, rather than limiting them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions carried by the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present application.

Claims

1. An automatic identification and management method for devices within an airborne server cluster, characterized in that, It includes: S1. Define an identifier: Define a unified identification bit according to the scale of the airborne server cluster. S2. Device identification: Identify the unified identification bit corresponding to the slot according to the level of the slot where the device is inserted. S3. Device management: Report the management information corresponding to the airborne server to the background maintenance system along with the unified identification bit through the control bus, and manage the airborne server devices according to the airborne server interaction protocol.

2. The method for automatically identifying and managing devices within an airborne server cluster according to claim 1, wherein S2 It includes: S201. In response to the insertion of the airborne server into the slot, inject high and low levels into the corresponding electrical interface of the slot. S202. Identify the unified identification bit corresponding to the slot by the airborne server recognizing the high and low levels of the corresponding electrical interface.

3. The method for automatically identifying and managing devices within an airborne server cluster according to claim 1, wherein In S3, the types of device management include heartbeat detection, status query, fault reporting, and instruction request operations.

4. The method for automatically identifying and managing devices in an airborne server cluster according to claim 3, wherein In S3, the heartbeat detection process supports periodic detection and node disconnection confirmation mechanisms. The interaction protocol timing of the heartbeat detection process is: The background maintenance system sends a heartbeat request to the airborne server, and the airborne server sends a heartbeat response to the background maintenance system.

5. The method for automatically identifying and managing devices within an airborne server cluster according to claim 3, characterized in that, In S3, the interaction protocol timing of the status query process is: The background maintenance system sends a status query request to the airborne server, and the airborne server sends a status query response to the background maintenance system.

6. The method for automatically identifying and managing devices in an airborne server cluster according to claim 3, wherein In S3, fault reporting supports real-time reporting. The interaction protocol timing of the fault reporting process is: The airborne server reports a fault to the background maintenance system, and the background maintenance system makes a fault response to the airborne server.

7. The method for automatically identifying and managing devices in an airborne server cluster according to claim 3, characterized in that, The instruction request includes remote power-on, power-off, reset, and restart. The interaction protocol timing of the instruction request process is: The background maintenance system sends a control instruction request to the airborne server, and the airborne server sends a control instruction response to the background maintenance system.

8. The method for automatically identifying and managing devices within an airborne server cluster according to claim 1, wherein, The message interface of the interaction protocol includes: Destination address, used to record the address information of the request initiator, aligned in 8 bits. Source address, used to record the address information of the request responder, aligned in 8 bits. Message sequence number, whose length varies according to the type of the adopted airborne control bus. Message type, the minimum set includes heartbeat request / response, fault reporting / response, status query request / response, control instruction request / response, 1 byte. Data length, used to specify the length of the data field, 2 bytes. Data field, the actual requirements are defined by the upper-layer service itself, 0 to K bytes, where K represents the maximum length of the data field. Check field, used to check the values of all bytes before the field, 2 bytes.

9. An automatic device for identifying and managing devices within an airborne server cluster, characterized in that For implementing the method according to any one of claims 1-8, it includes: Background maintenance system, used to identify the unified identification bit information corresponding to the airborne server, and perform centralized management and maintenance on the airborne server. Control bus, used for data transmission between the background maintenance system and the airborne server. Airborne server deployment area, including airborne server slots, used to store airborne servers.

10. The device for automatically identifying and managing devices within an airborne server cluster according to claim 9, wherein The backplane of the airborne server slot is provided with an electrical interface for identifying the unified identification bit.

Images