CN117097741A

CN117097741A - Fault information synchronization method

Info

Publication number: CN117097741A
Application number: CN202311147502.2A
Authority: CN
Inventors: 金川; 周昌申; 隗盛; 秦晨
Original assignee: Shanghai Yingheng Electronic Co ltd
Current assignee: Shanghai Yingheng Electronic Co ltd
Priority date: 2023-09-06
Filing date: 2023-09-06
Publication date: 2023-11-21

Abstract

The invention discloses a fault information synchronization method. The method comprises the following steps: and storing the detected fault information, generating storage time and verification information corresponding to the fault information, transmitting the storage time and the verification information to a second device based on a preset communication connection, and synchronizing the fault information to the second device in response to a fault synchronization request of the second device. According to the embodiment of the invention, based on the preset communication connection and the fault synchronization request, the fault information of the first equipment is synchronously updated to the second equipment, so that the synchronous update and mutual backup of the fault information among a plurality of electronic equipment can be realized, and all fault information of the damaged electronic equipment before the damage can be accurately acquired through other electronic equipment under the condition that one electronic equipment is damaged.

Description

Fault information synchronization method

Technical Field

The invention relates to the technical field of data storage, in particular to a fault information synchronization method.

Background

In the automotive field, diagnostic trouble codes (Diagnostic Trouble Code, DTCs) are commonly used to record various trouble information occurring in vehicle systems. As vehicle systems and components become more complex, an electronic control unit (Electronic Control Unit, ECU) may store hundreds or thousands of DTCs, and the electronics within the ECU that store the DTCs, once slightly damaged, may cause the DTCs to be unreadable, and thus it becomes increasingly important for failure information of the vehicle to be stored synchronously.

In the existing fault information storage and reading process, the following two problems exist: firstly, the existing fault reading architecture cannot accurately acquire fault codes stored in damaged or abnormal vehicle parts; and secondly, the failure information of the vehicle cannot be obtained due to the damage of equipment storing the failure code. In summary, a method for synchronizing fault information is needed to solve the above-mentioned problems.

Disclosure of Invention

The invention provides a fault information synchronization method, which aims to solve the technical problem that vehicle fault information cannot be accurately acquired due to damage of automobile parts and equipment storing fault codes.

According to an aspect of the present invention, there is provided a fault information synchronization method, wherein the method is applied to a first device, and includes:

storing the detected fault information and generating storage time and verification information corresponding to the fault information;

transmitting the storage time and the verification information to the second device based on a preset communication connection;

the failure information is synchronized to the second device in response to a failure synchronization request of the second device.

According to another aspect of the present invention, there is provided a fault information synchronization apparatus, which is applied to a first device, including:

the information generation module is used for storing the detected fault information and generating storage time and verification information corresponding to the fault information;

the information transmission module is used for transmitting the storage time and the verification information to the second equipment based on the preset communication connection;

and the fault synchronization module is used for responding to the fault synchronization request of the second equipment and synchronizing the fault information to the second equipment.

According to another aspect of the present invention, there is provided an electronic apparatus including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the fault information synchronization method of any one of the embodiments of the present invention.

According to another aspect of the present invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to implement the fault information synchronization method according to any one of the embodiments of the present invention when executed.

According to the technical scheme, the detected fault information is stored, the storage time and the verification information corresponding to the fault information are generated, the storage time and the verification information are transmitted to the second device based on the preset communication connection, and the fault information is synchronized to the second device in response to a fault synchronization request of the second device. According to the embodiment of the invention, the fault information of the first equipment can be synchronously updated to the second equipment by presetting the communication connection and the fault synchronous request, so that the synchronous update and mutual backup of the fault information among a plurality of electronic equipment are realized, and the method can support that under the condition that a certain electronic equipment is damaged, all the fault information of the damaged equipment before the damage occurs can be accurately obtained through other electronic equipment.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flowchart of a fault information synchronization method according to a first embodiment of the present invention;

fig. 2 is a flowchart of a fault information synchronization method according to a second embodiment of the present invention;

fig. 3 is a flowchart of a fault information synchronization method according to a third embodiment of the present invention;

fig. 4 is a diagram illustrating an exemplary architecture of an EE architecture of an automobile according to a third embodiment of the present invention;

FIG. 5 is a flowchart illustrating a fault code storage process according to a third embodiment of the present invention;

FIG. 6 is a flowchart illustrating a fault code update service according to a third embodiment of the present invention;

fig. 7 is a schematic structural diagram of a fault information synchronization device according to a fourth embodiment of the present invention;

fig. 8 is a schematic structural diagram of an electronic device implementing a fault information synchronization method according to an embodiment of the present invention.

Detailed Description

In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example 1

Fig. 1 is a flowchart of a fault information synchronization method according to a first embodiment of the present invention, where the method may be applicable to a situation of fault information synchronization between different electronic devices in a vehicle system, and the method may be performed by a fault information synchronization device, where the fault information synchronization device may be implemented in a form of hardware and/or software, and the fault information synchronization device may be configured in the electronic device, for example, may include a vehicle device and the like. As shown in fig. 1, the fault information synchronization method provided in the first embodiment is applied to a first device, and specifically includes the following steps:

s110, storing the detected fault information and generating storage time and verification information corresponding to the fault information.

In the embodiment of the present invention, the first device and the second device may be understood as different electronic devices in the vehicle system, and the first device and the second device may be, for example, different Electronic Control Units (ECU) or storage devices in the vehicle system, or the like. The failure information may be understood as failure information related to the vehicle system corresponding to the first device, and the failure information may include a failure code (DTC), snapshot Data (snap shot Data), extension Data (Extended Data), storage time, verification information, and the like. The storage time may be understood as a writing time of the fault information corresponding to the first device, i.e. a time when the fault information is finally written into the storage space of the first device. The verification information may be understood as a verification value generated by the first device from the stored fault information, and may include a cyclic redundancy check (Cyclic Redundancy Check, CRC) value, a parity value, a Checksum (Checksum), a longitudinal redundancy check (Longitudinal Redundancy Check, LRC) value, and the like.

Specifically, the fault information of the first device may be monitored, where the monitoring manner may include, but is not limited to, the following: the fault information generated by the first equipment can be monitored by utilizing a pre-configured fault monitoring module, the fault information generated by the first equipment can be monitored by utilizing an On-board diagnostic system (On-Board Diagnostics, OBD) and the like; the detected fault information may be stored in a fault storage space local to the first device, and further, the storage space may be a Non-volatile Memory (NVM) in the first device, for example, and may include, but is not limited to: flash Memory, erasable programmable read-Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), etc.; corresponding storage time and verification information may be generated based on the detected fault information, wherein the verification information may include, but is not limited to, the following: CRC value, parity value, checksum (Checksum), LRC value, etc.

S120, transmitting the storage time and the verification information to the second device based on the preset communication connection.

In the embodiment of the present invention, the preset communication connection may be understood as a pre-configured connection manner for implementing data communication between the first device and the second device, where the preset communication connection may include an IP-based extensible service-Oriented Middleware over IP (SOME/IP), a communication connection based on a data distribution service (Data Distribution Service, DDS), and so on.

Specifically, a data communication connection between the first device and the second device may be established based on the configured preset communication connection, and the storage time and the verification information corresponding to the first device may be transmitted to the second device, where the transmission manner of the storage time and the verification information may include, but is not limited to, the following several types: the storage time and the verification information corresponding to the first device can be published to the second device subscribing to the fault topic message based on the publish/subscribe (Pub/Sub) function of the SOME/IP communication protocol; the storage time and the authentication information corresponding to the first device may be published to the second device subscribing to the fault topic message based on a publish/subscribe (Pub/Sub) function of the DDS communication protocol.

S130, synchronizing the fault information to the second device in response to the fault synchronization request of the second device.

In the embodiment of the present invention, the response may be understood as a response operation performed by the first device after receiving the request for failure synchronization of the second device. The request for fault synchronization may be understood as a request for applying for fault information synchronization triggered by the second device according to the storage time and the verification information. Synchronization may be understood as an operation for making the failure information stored by the first device and the second device identical.

Specifically, the first device may receive a second device triggered failure synchronization request, where the manner in which the second device triggers the failure synchronization request may include, but is not limited to, the following: when the verification information of the second equipment is inconsistent with the received verification information corresponding to the first equipment, the second equipment triggers a fault synchronization request; when the storage time of the second equipment is longer than the storage time corresponding to the received first equipment, the second equipment triggers a fault synchronization request; when the verification information of the second device is inconsistent with the received verification information corresponding to the first device, and the storage time of the second device is longer than the storage time corresponding to the received first device, the second device triggers a fault synchronization request; after receiving the fault synchronization request triggered by the second device, the first device can respond to the request through a preset communication connection such as an SOME/IP communication protocol, and transmit corresponding fault information to the second device, so that the fault information of the second device can be synchronized.

According to the technical scheme, the detected fault information is stored, the storage time and the verification information corresponding to the fault information are generated, the storage time and the verification information are transmitted to the second device based on the preset communication connection, and the fault information is synchronized to the second device in response to a fault synchronization request of the second device. The embodiment of the invention can synchronously update the fault information stored by the first equipment to the second equipment based on the fault synchronous request of the second equipment, realizes mutual backup and mutual synchronization of the fault information among a plurality of electronic equipment, and can support all the fault information before being recovered by other electronic equipment under the condition that one electronic equipment is damaged.

Example two

Fig. 2 is a flowchart of a fault information synchronization method according to a second embodiment of the present invention, which is further optimized and expanded based on the foregoing embodiments, and may be combined with each of the optional technical solutions in the foregoing embodiments. It should be understood that this embodiment is only described with respect to two electronic devices (a first device and a second device) in the same failure synchronization group, and this should not limit the scope of implementation of the embodiment of the present invention. As shown in fig. 2, the fault information synchronization method provided in the second embodiment is applied to a first device, and specifically includes the following steps:

s210, monitoring fault information of the first equipment based on a preset fault monitoring module.

In the embodiment of the invention, the preset fault monitoring module can be understood as a preconfigured software module for monitoring the fault information of the ECU, and the preset fault monitoring module can be preconfigured in each ECU.

Specifically, the fault information of the first device may be monitored by using a preset fault monitoring module, where the preset fault monitoring module may be preconfigured in the first device, and the fault information may include, but is not limited to: diagnostic Trouble Codes (DTCs), snapshot data, extension data, failure storage time, failure verification information, and the like. In some embodiments, the preset fault monitoring module may be used to monitor the working states of various sensors, electronic control units and various actuators on the vehicle during the running of the vehicle, and if a fault event occurs, the working states are stored in the form of a fault code (DTC).

S220, storing the fault information in a lasting mode and storing the storage time of the fault information.

In the embodiment of the invention, the persistent storage can be understood as converting transient fault information into persistent fault information, and storing the persistent fault information in the electronic device.

Specifically, after the fault information is detected, the fault information may be stored in a persistent manner, and the fault information may be stored in a storage space of the first device, where the storage space of the fault information may include, but is not limited to: flash memory, EPROM memory, EEPROM memory, etc.; the storage time corresponding to the fault information, that is, the writing time of the fault information, may be stored in the storage space of the first device. Illustratively, after the fault information is detected, the current fault information may be published using a Data Distribution Service (DDS) and the fault code is stored in a DDS corresponding fault callback according to a diagnostic specification, where the diagnostic specification may include, but is not limited to, ISO 15765, ISO 15031, SAE J1939, etc., and the storage time for the fault information is updated.

S230, determining verification information of the stored fault information according to a preset cyclic redundancy check code generation rule.

In the embodiment of the invention, the preset cyclic redundancy check code generation rule can be understood as a rule which is preconfigured and used for generating a CRC check value, and CRC is a widely applied data transmission error detection technology and can be used for ensuring the correctness and the integrity of data transmission.

Specifically, the stored fault information may be generated to a corresponding CRC value as verification information based on a preset cyclic redundancy check code generation rule, which may include, but is not limited to: CRC-8, CRC-16, CRC-32, etc., and further, CRC values may be generated by bit-wise calculations, byte-wise calculations, nibble calculations, etc.

S240, the first device and the second device are controlled to establish preset communication connection, wherein the preset communication connection comprises an IP-based expandable service-oriented middleware connection.

In the embodiment of the present invention, an IP-based extensible service oriented middleware connection (SOME/IP) may be understood as a preconfigured connection manner for implementing data communication between a first device and a second device, where SOME/IP is used as a middleware to mainly provide the following functions: serialization (Serialization), remote procedure call (Remote Procedure Call, RPC), service discovery (Service Discovery, SD), publish/subscribe (Pub/Sub), and message Segmentation (segment).

In particular, a data communication connection may be established between the first device and the second device using a preset communication connection, wherein the preset communication connection may include an IP-based extensible service oriented middleware connection (SOME/IP), and further, the SOME/IP-based service may be composed of a Method, an Event, and a Field (Field).

S250, the storage time and the verification information are sent to the second device through a preset communication connection.

Specifically, a preset communication connection such as a Pub/Sub function of a SOME/IP middleware protocol may be utilized, a second device may subscribe to a message published by a first device with a storage time and authentication information as a Topic (Topic) through an IP-based extensible service oriented middleware-service discovery (SOME/IP Service Discovery, SOME/IP-SD), and after the first device publishes the Topic message, the second device may acquire the storage time and authentication information published by the first device through a subscription service, and may implement transmitting the storage time and authentication information of the first device to the second device through the preset communication connection.

And S260, receiving a fault synchronization request triggered by the second equipment based on the storage time and the verification information.

Specifically, the second device may compare the failure storage time and verification information issued by the first device with the failure storage time and verification information of the failure storage space of the second device, if the two information are not matched, the second device may trigger a failure synchronization request, and the first device may receive the failure synchronization request triggered by the second device through a preset communication connection, for example, a SOME/IP middleware protocol.

And S270, transmitting the fault information to the second equipment according to the fault synchronization request.

Specifically, the first device (server side) may respond to the fault synchronization request issued by the second device (client side) based on a preset communication connection, for example, a SOME/IP middleware protocol, and may transmit the fault information to the second device in the form of a response message, so as to realize synchronization of the fault information of the second device.

Further, on the basis of the above embodiment of the present invention, the second device and the first device belong to the same failure synchronization group.

In the embodiment of the invention, all electronic devices in a vehicle system can be divided into a plurality of fault synchronization groups based on actual needs, and synchronous update of fault information can be realized among the electronic devices in each fault synchronization group, for example, if a first device and a second device belong to the same fault synchronization group, then the fault information synchronization between the first device and the second device can be realized through preset communication connection such as SOME/IP middleware protocol; further, the electronic devices among the different fault synchronization groups do not synchronize the fault information. In some embodiments, all the ECUs in the vehicle system may be divided into a plurality of failure synchronization groups, and the synchronization update of the failure information may be implemented between the ECUs in each failure synchronization group, so as to implement distributed storage and reading of the failure information.

Further, on the basis of the above embodiment of the present invention, the fault information synchronization method further includes:

checking verification information in response to the device start-up instruction;

and synchronizing the fault information of the second equipment to the local under the condition that verification information fails to verify.

In the embodiment of the invention, the device starting command can be understood as a command for waking up the vehicle ECU, and according to different ECU positions configured by the vehicle, the device starting command can comprise a door opening command triggered when the vehicle opens a door, an opening command triggered when the vehicle-mounted terminal is opened, a control command triggered when the vehicle is remotely controlled to be opened/unlocked through a remote control terminal (such as mobile phone software, a remote controller and the like), and the like.

Specifically, after receiving the device start instruction, the first device may check the verification information (CRC value) of its own storage space, and in case that verification of the verification information fails, issue a failure synchronization request to the second device in the same failure synchronization group, and synchronously update the failure information stored in the second device to the failure storage space of the local (i.e., the first device) according to the responded failure information.

receiving second verification information of a second device and second storage time;

and synchronizing the second fault information of the second device to the local in case that the second verification information is different from the verification information or the second storage time is longer than the storage time.

In the embodiment of the present invention, the second verification information may be understood as a verification value generated by the second device according to the self-fault information, and the second verification information may include a CRC value, a parity value, a Checksum (Checksum), an LRC value, and the like. The second storage time may be understood as a writing time of the fault information corresponding to the second device, i.e., a time when the fault information is finally written into the storage space of the second device. The second failure information may be understood as failure information related to the vehicle corresponding to the second device, and may include a failure code (DTC), snapshot Data (snap shot Data), extension Data (Extended Data), storage time, authentication information, and the like.

Specifically, the first device may subscribe to receive the second verification information and the second storage time issued by the second device through a preset communication connection, for example, a SOME/IP middleware protocol, and may compare the second verification information and the second storage time with the verification information and the storage time corresponding to the first device, and may issue a failure synchronization request to the second device in the same failure synchronization group when the second verification information is different from the verification information or the second storage time is greater than the storage time, and synchronously update the failure information stored by the second device to the failure storage space of the local (i.e., the first device) according to the responded failure information.

According to the technical scheme, the fault information of the first equipment is monitored based on the preset fault monitoring module, the fault information is stored, the storage time of the fault information is stored, verification information of the stored fault information is determined according to a preset cyclic redundancy check code generation rule, the first equipment and the second equipment are controlled to establish preset communication connection, the preset communication connection comprises an IP-based expandable service oriented middleware connection, the storage time and the verification information are sent to the second equipment through the preset communication connection, a fault synchronization request triggered by the second equipment based on the storage time and the verification information is received, and the fault information is transmitted to the second equipment according to the fault synchronization request. According to the embodiment of the invention, the storage time and verification information issued by the first equipment can be received by the second equipment, the fault information of the first equipment is synchronously updated to the second equipment based on the triggered fault synchronous request, so that the synchronous update and mutual backup of the fault information among all the electronic equipment in the same fault synchronous group are realized, and when damage or abnormality occurs to one electronic equipment, all the fault information before the damage or abnormality can be accurately obtained through other electronic equipment in the fault synchronous group.

Example III

Fig. 3 is a flowchart of a fault information synchronization method according to a third embodiment of the present invention. Based on the above embodiment, the present embodiment provides an implementation manner of a fault information synchronization method, taking the first device and the second device as different ECUs in a vehicle system respectively as an example, and can implement real-time sharing of fault codes (DTCs) between ECUs in the same fault synchronization group and mutual backup updating based on DDS and SOME/IP communication protocols under an electronic and electrical (Electronic Engineering, EE) architecture of a next-generation vehicle. Fig. 4 is a structural example diagram of an EE architecture of an automobile according to a third embodiment of the present invention. As shown in fig. 3, the fault information synchronization method provided in the third embodiment of the present invention specifically includes the following steps:

s310, subscription and release of all ECUs with DTCs (fault codes) as topics are established based on the DDS communication protocol.

And S320, monitoring ECU fault information based on a fault monitoring module, if a corresponding fault event is generated, issuing the fault information through the DDS, and storing a fault code, updating a CRC value of a storage space and writing time according to diagnosis specifications in a corresponding fault callback of the DDS.

Fig. 5 is a flowchart illustrating a fault code storage process according to a third embodiment of the present invention. As shown in fig. 5, when the fault monitoring module monitors that a fault event is generated by a certain ECU, for example, the ECU1 may store the corresponding fault event in the form of DTC in its own storage space according to the diagnostic specification, and update the CRC value and writing time of its own storage space at the same time; further, the ECU1 may issue a DTC (fault code) as a topic to other ECUs subscribing to the topic message based on the DDS communication protocol, and after receiving the fault information issued by the ECU1, the other ECUs may store the fault information in the storage space of the ECU1 and update the CRC value and the writing time of the storage space of the ECU.

S330, each ECU issues CRC value and writing time of the current fault information storage space based on SOME/IP communication protocol.

In an embodiment of the present invention, SOME/IP based services include two types: firstly, fault code synchronous service, namely, an ECU issues CRC value and last writing time of the current fault storage space; and secondly, a fault code updating service, namely updating fault storage data from a specified ECU.

S340, subscribing the fault code synchronization service, and judging whether to apply for updating the DTC storage space to other ECUs according to the received CRC value and the writing time.

S350, checking CRC values of the storage space after the ECU wakes up (starts), and if the checking fails, updating fault storage data stored by other ECUs to the storage space of the ECU through a fault code updating service.

Fig. 6 is a flowchart illustrating a fault code updating service according to a third embodiment of the present invention. As shown in fig. 6, taking ECU1 as a service end and ECU2 as a client end, when ECU2 receives the CRC value and write time of the storage space issued by ECU1, it compares the above information with the CRC value and write time of the local storage space, and if the CRC values of the two are inconsistent and the received write time is greater than the local write time, it can issue a failure synchronization request to ECU1 in the same failure synchronization group through the SOME/IP communication protocol, and synchronously update the failure information stored by ECU1 to the failure storage space of the local (i.e., ECU 2) according to the responsive failure information, where the failure storage space may be Flash memory in ECU 2. Similarly, the failure storage data in the ECU2 may be updated to the failure storage space of the ECU 1. It should be noted that, in the embodiment of the present invention, the synchronization update process of the fault information between the ECU1 and the ECU2 is only used as an example, and in the actual operation process, the synchronization update storage of the fault information between all the ECUs in the same fault synchronization group may be implemented based on the same fault information synchronization principle, which is not described in detail in the embodiment of the present invention.

S360, checking CRC value of the storage space after the ECU wakes up (starts), and if the checking is successful, completing the synchronization of the storage space information through S330 and S340.

According to the technical scheme, subscription and release of DTCs are established on the basis of a DDS communication protocol, ECU fault information is monitored on the basis of a fault monitoring module, if a corresponding fault event is generated, the fault information is released through the DDS, a fault code is stored in the corresponding fault callback of the DDS according to diagnosis specifications, CRC value and writing time of a storage space are updated, each ECU releases the CRC value and the writing time of the current fault information storage space on the basis of an SOME/IP communication protocol, the fault code synchronization service is subscribed, whether the DTC storage space needs to be updated is judged according to the received CRC value and writing time, the CRC value of the storage space is checked after the ECU wakes up (starts up), if the fault information stored by other ECUs is updated to the storage space of the ECU through the fault code updating service, if the fault information is checked successfully, the storage space information synchronization is completed through S330 and S340. The embodiment of the invention can realize real-time sharing, mutual synchronization and mutual backup of fault codes (DTCs) among the ECUs in the same fault synchronization group based on DDS and SOME/IP communication protocols; the distributed storage of fault information can be realized; it can support that in the case that a certain ECU is damaged, all fault information of the damaged ECU before the damage occurs can be accurately obtained through other ECUs in the fault synchronization group.

Example IV

Fig. 7 is a schematic structural diagram of a fault information synchronization device according to a fourth embodiment of the present invention. As shown in fig. 7, the apparatus is applied to a first device, including:

the information generating module 41 is configured to store the detected fault information and generate a storage time and verification information corresponding to the fault information.

An information transmission module 42 for transmitting the storage time and the authentication information to the second device based on the preset communication connection.

The fault synchronization module 43 is configured to synchronize the fault information to the second device in response to a fault synchronization request of the second device.

According to the technical scheme, the information generating module is used for storing the detected fault information and generating the storage time and the verification information corresponding to the fault information, the information transmitting module is used for transmitting the storage time and the verification information to the second equipment based on the preset communication connection, and the fault synchronizing module is used for synchronizing the fault information to the second equipment in response to a fault synchronizing request of the second equipment. According to the embodiment of the invention, the fault information of the first equipment can be synchronously updated to the second equipment based on the preset communication connection and the fault synchronization request, so that the synchronous update and mutual backup of the fault information among a plurality of electronic equipment are realized, and the accurate acquisition of all the fault information of the damaged electronic equipment before the damage occurs can be supported through other electronic equipment under the condition that one electronic equipment is damaged.

Further, on the basis of the above embodiment of the invention, the information generating module 41 includes:

the fault information monitoring unit is used for monitoring the fault information of the first equipment based on a preset fault monitoring module.

And the first information storage unit is used for storing the fault information in a lasting mode and saving the storage time of the fault information.

And the second information storage unit is used for determining verification information of the stored fault information according to a preset cyclic redundancy check code generation rule.

Further, on the basis of the above embodiment of the invention, the information transmission module 42 includes:

the device connection unit is used for controlling the first device and the second device to establish preset communication connection, wherein the preset communication connection comprises an IP-based expandable service-oriented middleware connection.

And the information sending unit is used for sending the storage time and the verification information to the second equipment through a preset communication connection.

Further, on the basis of the above embodiment of the invention, the fault synchronization module 43 includes:

and the request receiving unit is used for receiving a fault synchronization request triggered by the second equipment based on the storage time and the verification information.

And the fault information transmission unit is used for transmitting the fault information to the second equipment according to the fault synchronization request.

Further, on the basis of the embodiment of the invention, the method further comprises the following steps:

and the verification information checking module is used for responding to the equipment starting instruction and checking the verification information.

And the first information synchronization module is used for synchronizing the fault information of the second equipment to the local under the condition that verification information fails to verify.

and the information receiving module is used for receiving the second verification information and the second storage time of the second equipment.

And the second information synchronization module is used for synchronizing second fault information of the second equipment to the local under the condition that the second verification information is different from the verification information and the second storage time is longer than the storage time.

The fault information synchronization device provided by the embodiment of the invention can execute the fault information synchronization method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

Example five

Fig. 8 shows a schematic diagram of an electronic device 50 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 8, the electronic device 50 includes at least one processor 51, and a memory, such as a Read Only Memory (ROM) 52, a Random Access Memory (RAM) 53, etc., communicatively connected to the at least one processor 51, in which the memory stores a computer program executable by the at least one processor, and the processor 51 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 52 or the computer program loaded from the storage unit 58 into the Random Access Memory (RAM) 53. In the RAM 53, various programs and data required for the operation of the electronic device 50 can also be stored. The processor 51, the ROM 52 and the RAM 53 are connected to each other via a bus 54. An input/output (I/O) interface 55 is also connected to bus 54.

Various components in the electronic device 50 are connected to the I/O interface 55, including: an input unit 56 such as a keyboard, a mouse, etc.; an output unit 57 such as various types of displays, speakers, and the like; a storage unit 58 such as a magnetic disk, an optical disk, or the like; and a communication unit 59 such as a network card, modem, wireless communication transceiver, etc. The communication unit 59 allows the electronic device 50 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks.

The processor 51 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 51 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 51 performs the various methods and processes described above, such as the fault information synchronization method.

In some embodiments, the fault information synchronization method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 58. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 50 via the ROM 52 and/or the communication unit 59. When the computer program is loaded into RAM 53 and executed by processor 51, one or more steps of the fault information synchronization method described above may be performed. Alternatively, in other embodiments, processor 51 may be configured to perform the fault information synchronization method in any other suitable manner (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. A method of synchronizing fault information, applied to a first device, the method comprising:

transmitting the storage time and the verification information to a second device based on a preset communication connection;

and synchronizing the fault information to the second device in response to a fault synchronization request of the second device.

2. The method according to claim 1, wherein the storing the detected fault information and generating the storage time and the verification information corresponding to the fault information includes:

monitoring the fault information of the first equipment based on a preset fault monitoring module;

persisting the fault information and saving the storage time of the fault information;

and determining the verification information of the stored fault information according to a preset cyclic redundancy check code generation rule.

3. The method of claim 1, wherein the transmitting the storage time and the authentication information to the second device based on the preset communication connection comprises:

controlling the first equipment and the second equipment to establish the preset communication connection, wherein the preset communication connection comprises an IP-based expandable service-oriented middleware connection;

and sending the storage time and the verification information to the second equipment through the preset communication connection.

4. A method according to claim 1 or 3, characterized in that the second device belongs to the same fault synchronization group as the first device.

5. The method of claim 1, wherein synchronizing the failure information to the second device in response to a failure synchronization request of the second device comprises:

receiving the fault synchronization request triggered by the second device based on the storage time and the verification information;

and transmitting the fault information to the second equipment according to the fault synchronization request.

6. The method as recited in claim 1, further comprising:

checking the verification information in response to a device start-up instruction;

and synchronizing fault information of the second equipment to the local under the condition that verification of the verification information fails.

7. The method as recited in claim 1, further comprising:

receiving second verification information of the second device and second storage time;

and synchronizing second fault information of the second device to the local under the condition that the second verification information is different from the verification information or the second storage time is longer than the storage time.

8. A fault information synchronizing apparatus for use with a first device, the apparatus comprising:

the information transmission module is used for transmitting the storage time and the verification information to the second equipment based on a preset communication connection;

9. An electronic device, the electronic device comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the fault information synchronization method of any one of claims 1-7.

10. A computer readable storage medium storing computer instructions for causing a processor to implement the fault information synchronization method of any one of claims 1-7 when executed.