Domain controller fault reporting method, system, electronic device and readable storage medium

By establishing a fault management protocol between the vehicle terminal and the management equipment, and using the transmission layer and the content layer to encode and resolve the fault event package, the inefficiency problem caused by the independence of the fault management of the on-board domain controller is solved, and unified management and fault information are realized. Comprehensive.

CN115987755BActive Publication Date: 2024-11-12CHONGQING CHANGAN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202211551691.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-12-05
Publication Date
2024-11-12
Estimated Expiration
2042-12-05

AI Technical Summary

Technical Problem

The fault management methods of existing vehicle domain controllers are independent and have low management efficiency, resulting in inconsistent fault notification management and low efficiency.

Method used

By establishing a fault management protocol between the vehicle terminal and the management equipment, using the transmission layer and the content layer to establish a fault communication link, encode and resolve fault event packets, the unified management of domain controller failures is achieved.

Benefits of technology

It improves the efficiency of fault management, realizes unified management of domain controller faults, expands the scope of fault management, and provides more comprehensive fault information, which is easy for users to view and debug.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115987755B_ABST
    Figure CN115987755B_ABST
Patent Text Reader

Abstract

The present invention relates to the field of vehicle communication technology, and discloses a domain controller fault reporting method, system, electronic device and readable storage medium. The method acquires a fault management protocol including a transport layer and a content layer, and respectively establishes a protocol server and a protocol client in a domain controller and a management device, and establishes a fault communication link according to the transport layer, so that the protocol server encodes the fault event of the domain controller according to the content layer to obtain a fault event package, and sends the fault event package to the protocol client through the fault communication link. The protocol client parses the fault event package according to the content layer to obtain a fault notification. Not only does the fault communication link establish a connection between the domain controller and the management device through a client / server structure, but also the fault event is encoded and parsed through the content layer in the fault management protocol to unify the format of the fault event, thereby realizing unified management of domain controller faults and improving fault management efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of vehicle communication technology, and in particular to a domain controller fault reporting method, system, electronic device and readable storage medium. Background Art

[0002] With the development of automobile intelligence and information technology, the use of vehicle ECU (Electronic Control Unit) chips is increasing, from engine control systems, airbags, anti-lock braking systems, electric power steering, electronic stability systems to smart instruments, entertainment audio and video systems, and assisted driving systems; there are also electric drive control, battery management systems, on-board charging systems on electric vehicles, as well as the booming on-board gateways, T-BOX (Telematics BOX) and autonomous driving systems. This ECU-based distributed EEA (Electrical / Electronic Architecture) makes the vehicle system more and more complex. In order to solve the above problems, many ECU functions with similar and separate functions are gradually integrated into a processor hardware platform with stronger performance than ECU through domain controllers. With the evolution of the electronic and electrical architecture of the whole vehicle, domain controllers are becoming more and more powerful and important. Due to the high requirements of vehicles for safety and timeliness, the importance of fault management and fault warning of each on-board domain controller has increased relatively.

[0003] However, existing fault management methods for vehicle-mounted domain controllers are independent, and each domain controller needs to be managed separately, which makes the fault management process chaotic and the fault notification management inconsistent, resulting in low management efficiency of fault notifications. Summary of the invention

[0004] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical components or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

[0005] In view of the above-mentioned shortcomings of the prior art, the present invention discloses a domain controller fault reporting method, system, electronic device and readable storage medium to improve the management efficiency of fault notification.

[0006] The present invention discloses a method for reporting a fault of a domain controller, comprising: obtaining a vehicle terminal and a fault management protocol, wherein the vehicle terminal comprises a management device and at least one domain controller, and the fault management protocol comprises a transport layer and a content layer; establishing a protocol server corresponding to the domain controller and a protocol client corresponding to the management device, and establishing a fault communication link between the protocol server and the protocol client according to the transport layer; in response to the domain controller generating a fault event, the protocol server encodes the fault event according to the content layer, obtains a fault event package corresponding to the fault event, and sends the fault event package to the protocol client through the fault communication link; the protocol client parses the received fault event package according to the content layer to obtain a fault notification.

[0007] Optionally, a fault communication link is established between the protocol server and the protocol client according to the transport layer, including: the transport layer includes a data transmission protocol and a transmission security protocol; the protocol server sends a protocol connection request to the protocol client; the protocol client establishes a data transmission link between the protocol server and the protocol client according to the transport layer, wherein the data transmission link is used for data transmission according to the data transmission protocol and the transmission security protocol; the protocol client sends a fault subscription request to the protocol server, so that the protocol server determines the data transmission link as a fault communication link.

[0008] Optionally, the protocol client sends a fault subscription request to the protocol server, including: the fault management protocol also includes a message layer, the message layer includes at least one of a remote call rule and a message notification rule; the protocol client obtains the fault subscription request, and encapsulates the fault subscription request through the remote call rule; the protocol client sends the fault subscription request after message encapsulation to the protocol server, so that the protocol server establishes a message upload service according to the message notification rule, wherein the message upload service is used to send the fault event package to the protocol client through the fault communication link.

[0009] Optionally, after sending the fault event package to the protocol client via the fault communication link, the method further includes: the domain controller obtains a fault warning list and adds the fault event to the fault warning list; in response to the domain controller generating fault resolution information corresponding to the fault event, the protocol server encodes the fault resolution information according to the content layer, obtains a resolution information packet corresponding to the fault resolution information, and sends the resolution information packet to the protocol client via the fault communication link; the domain controller deletes the fault event from the fault warning list.

[0010] Optionally, after the protocol client parses the received fault event package according to the content layer and obtains the fault notification, the method further includes: the protocol client sends a list query request to the protocol server; the domain controller corresponding to the protocol server counts the number of fault events in the fault warning list; if the number of events is greater than the preset number threshold, the fault warning list is sent to the protocol client.

[0011] Optionally, the protocol server encodes the fault event according to the content layer to obtain a fault event package corresponding to the fault event, including: the content layer includes a data modeling language and a data content template; a data transmission interface is established on the protocol server according to the data modeling language; the fault event is filled into the data content template and encoded using the data transmission interface to obtain a fault event package corresponding to the fault event.

[0012] Optionally, the fault event package includes a fault type field and other information fields, wherein the fault type field carries at least one of a fault identifier, a fault carrier, and a fault level corresponding to the fault event, and the other information fields carry at least one of a fault occurrence time, a fault impact module, a fault relief status, and fault details.

[0013] Optionally, the management device includes at least one of the following: a communication device, used to establish an external network link between the communication device and a preset server side, and send the fault notification to the server side; a debugging device, used to display the fault notification, collect user debugging instructions corresponding to the fault notification, and send the user debugging instructions to the domain controller, so that the domain controller executes the user debugging instructions.

[0014] Optionally, after establishing a fault communication link between the protocol server and the protocol client according to the transport layer, the method further includes: the fault management protocol also includes an operation layer, and the operation layer includes at least one data operation instruction; in response to the management device collecting any data operation instruction input by the user, the protocol client sends the data operation instruction to the protocol server through the fault communication link, so that the protocol server executes the data operation instruction.

[0015] The present invention discloses a domain controller fault reporting system, comprising: an acquisition module, used for acquiring a vehicle terminal and a fault management protocol, wherein the vehicle terminal comprises a management device and at least one domain controller, and the fault management protocol comprises a transport layer and a content layer; an establishment module, used for establishing a protocol server corresponding to the domain controller and a protocol client corresponding to the management device, and establishing a fault communication link between the protocol server and the protocol client according to the transport layer; a sending module, used for generating a fault event in response to the domain controller, the protocol server encoding the fault event according to the content layer, obtaining a fault event package corresponding to the fault event, and sending the fault event package to the protocol client through the fault communication link; and a parsing module, used for the protocol client to parse the received fault event package according to the content layer to obtain a fault notification.

[0016] The present invention discloses an electronic device, comprising: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes the above method.

[0017] The present invention discloses a computer-readable storage medium, on which a computer program is stored: when the computer program is executed by a processor, the above method is implemented.

[0018] Beneficial effects of the present invention:

[0019] By acquiring a fault management protocol including a transport layer and a content layer, and establishing a protocol server and a protocol client in a domain controller and a management device respectively, a fault communication link is established according to the transport layer, so that the protocol server encodes the fault event of the domain controller according to the content layer to obtain a fault event package, and sends the fault event package to the protocol client through the fault communication link. The protocol client parses the fault event package according to the content layer to obtain a fault notification. In this way, not only a fault communication link is established through the client / server structure to connect the domain controller and the management device, but also the fault event is encoded and parsed through the content layer in the fault management protocol to unify the format of the fault event, thereby realizing unified management of domain controller faults and improving fault management efficiency.

[0020] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0022] Figure 1 It is a structural diagram of a five-domain centralized architecture in an embodiment of the present invention;

[0023] Figure 2 It is a flowchart of a method for reporting a domain controller fault in an embodiment of the present invention;

[0024] Figure 3 It is a structural schematic diagram of a fault reporting system implementing a domain controller fault reporting method in an embodiment of the present invention;

[0025] Figure 4 It is a schematic diagram of the structure of a protocol stack of the NETCONF protocol in an embodiment of the present invention;

[0026] Figure 5 It is a schematic diagram of the structure of the protocol layer of a NETCONF protocol in an embodiment of the present invention;

[0027] Figure 6 is a structural diagram of another fault reporting system in an embodiment of the present invention;

[0028] Figure 7 is a flowchart of another method for reporting a domain controller fault in an embodiment of the present invention;

[0029] Figure 8 It is a flowchart of a method for reporting a domain controller fault resolution in an embodiment of the present invention;

[0030] Fig. 9 This is a flow chart of a method for obtaining a fault warning list in an embodiment of the present invention.

[0031] Fig.10 It is a structural diagram of a domain controller fault reporting system in an embodiment of the present invention;

[0032] Fig.11 It is a schematic diagram of the structure of an electronic device in an embodiment of the present invention. DETAILED DESCRIPTION

[0033] The following describes the embodiments of the present invention through specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and sub-samples in the embodiments can be combined with each other without conflict.

[0034] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0035] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.

[0036] The terms "first", "second", etc. in the specification and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so that the embodiments of the embodiments of the present disclosure described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0037] Unless otherwise stated, the term "plurality" means two or more.

[0038] In the embodiment of the present disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B indicates: A or B.

[0039] The term "and / or" is a description of the association relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or, A and B.

[0040] Combination Figure 1As shown, the disclosed embodiment provides a five-domain centralized architecture, in which the domain controller is divided into a power domain (Power Train), a chassis domain (Chassis), a body domain (Body / Comfort), a cockpit domain (Cockpit / Infotainment), and an autonomous driving domain (ADAS) based on the functional domain. The domain controller is the core of each functional domain of the car. It is mainly composed of three parts: a domain master processor, an operating system, and application software and algorithms. Platformization, high integration, high performance, and good compatibility are the main core design ideas of the domain controller. Relying on a high-performance domain master processor, rich hardware interface resources, and powerful software functional characteristics, the domain controller can integrate the core functions that originally required many ECUs to implement, greatly improving the system function integration. Coupled with the standardized interface for data interaction, the development and manufacturing costs of this part can be greatly reduced.

[0041] Combination Figure 2 As shown, the embodiment of the present disclosure provides a method for reporting a domain controller fault, including:

[0042] Step S201, obtaining a vehicle terminal and a fault management protocol;

[0043] Wherein, the vehicle terminal includes a management device and at least one domain controller, and the fault management protocol includes a transport layer and a content layer;

[0044] Step S202, establishing a protocol server corresponding to the domain controller and a protocol client corresponding to the management device, and establishing a fault communication link between the protocol server and the protocol client according to the transport layer;

[0045] Step S203, in response to the domain controller generating a fault event, the protocol server encodes the fault event according to the content layer, obtains a fault event package corresponding to the fault event, and sends the fault event package to the protocol client through the fault communication link;

[0046] Step S204: the protocol client parses the received fault event package according to the content layer to obtain a fault notification.

[0047] The domain controller fault reporting method provided by the embodiment of the present disclosure is adopted, by obtaining a fault management protocol including a transport layer and a content layer, and establishing a protocol server and a protocol client in the domain controller and the management device respectively, and establishing a fault communication link according to the transport layer, so that the protocol server encodes the fault event of the domain controller according to the content layer to obtain a fault event package, and sends the fault event package to the protocol client through the fault communication link, and the protocol client parses the fault event package according to the content layer to obtain a fault notification. In this way, not only a fault communication link is established through the client / server structure to connect the domain controller and the management device, but also the fault event is encoded and parsed through the content layer in the fault management protocol to unify the format of the fault event, thereby realizing unified management of domain controller faults and improving fault management efficiency.

[0048] Optionally, the management device includes at least one of the following: a communication device, used to establish an external network link between the communication device and a preset server side, and send a fault notification to the server side; a debugging device, used to display the fault notification, collect user debugging instructions corresponding to the fault notification, and send the user debugging instructions to the domain controller, so that the domain controller executes the user debugging instructions.

[0049] In this way, the management device includes a communication device and / or a debugging device, wherein the fault notification is uploaded to the server side through the communication device, the domain controller is debugged through the debugging device, and the fault of the domain controller is managed from the aspects of data collection and instruction debugging, thereby improving the management scope of the domain controller fault.

[0050] In some embodiments, the communication device includes at least one of a T-Box module, a 4G (Fourth Generation Mobile Communication Technology) module, a 5G (Fifth Generation Mobile Communication Technology) module, etc.; the debugging device includes at least one of a domain controller, a computer, a laptop computer, a smart phone, etc.

[0051] Combination Figure 3As shown, the embodiment of the present disclosure provides a fault reporting system for implementing the above-mentioned domain controller fault reporting method, including a domain controller module 301, a communication device 302, a debugging device 303, and a server 304, wherein the domain controller module 301 is composed of an electronic unit 3011, a domain control application 3012, a domain control peripheral 3013, and a domain controller 3014. The electronic unit 3011 communicates with the domain controller 3014 through a CAN (Controller A controller area network (CANET) bus is connected to a domain controller 3014, a domain control application 3012 and a domain control peripheral 3013 are respectively connected to the domain controller 3014 through an application interface, the domain controller 3014 is connected to at least one of a communication device 302 and a debugging device 303 through Ethernet, and the communication device 302 is connected to a server 304; a protocol server is established in the domain controller, a protocol client is established in the communication device and the debugging device, and a fault communication link is established between the protocol server and the protocol client according to the transport layer; in response to the domain controller generating a fault event, the protocol server encodes the fault event according to the content layer, obtains a fault event package corresponding to the fault event, and sends the fault event package to the protocol client through the fault communication link; the protocol client parses the received fault event package according to the content layer to obtain a fault notification.

[0052] The fault reporting system provided by the embodiment of the present disclosure is adopted, by obtaining the fault management protocol including the transport layer and the content layer, and establishing the protocol server and the protocol client in the domain controller and the management device respectively, and establishing a fault communication link according to the transport layer, so that the protocol server encodes the fault event of the domain controller according to the content layer to obtain a fault event package, and sends the fault event package to the protocol client through the fault communication link, and the protocol client parses the fault event package according to the content layer to obtain a fault notification. In this way, not only a fault communication link is established through the client / server structure to connect the domain controller and the management device, but also the fault event is encoded and parsed through the content layer in the fault management protocol to unify the format of the fault event, thereby realizing unified management of domain controller faults and improving fault management efficiency.

[0053] Optionally, a fault communication link is established between the protocol server and the protocol client according to the transport layer, including: the transport layer includes a data transmission protocol and a transmission security protocol; the protocol server sends a protocol connection request to the protocol client; the protocol client establishes a data transmission link between the protocol server and the protocol client according to the transport layer, wherein the data transmission link is used for data transmission according to the data transmission protocol and the transmission security protocol; the protocol client sends a fault subscription request to the protocol server, so that the protocol server determines the data transmission link as a fault communication link.

[0054] In some embodiments, the default port of the protocol client is 4334, the default port of the protocol server is 830, and the protocol server sends a protocol connection request to the protocol client via a call-home method.

[0055] In some embodiments, the management device and the domain controller are connected via Ethernet, and the protocol server sends a protocol connection request to the protocol client via Ethernet.

[0056] In some embodiments, the data transmission protocol includes the TCP / IP (Transmission Control Protocol / Internet Protocol) transmission protocol, etc.; the transmission security protocol includes one or more of the SSH (Secure Shell) protocol, the TLS (Transport Layer Security) protocol, etc.

[0057] Optionally, the protocol client sends a fault subscription request to the protocol server, including: the fault management protocol also includes a message layer, the message layer includes at least one of a remote call rule and a message notification rule; the protocol client obtains the fault subscription request, and encapsulates the fault subscription request through the remote call rule; the protocol client sends the fault subscription request after message encapsulation to the protocol server, so that the protocol server establishes a message upload service according to the message notification rule, wherein the message upload service is used to send the fault event package to the protocol client through the fault communication link.

[0058] In some embodiments, the remote call rule includes an RPC (Remote Procedure Call) protocol, etc., and the message notification rule includes a NOTIFICATION protocol, etc.

[0059] Optionally, the protocol server encodes the fault event according to the content layer to obtain a fault event package corresponding to the fault event, including: the content layer includes a data modeling language and a data content template; a data transmission interface is established on the protocol server according to the data modeling language; the fault event is filled into the data content template and encoded using the data transmission interface to obtain a fault event package corresponding to the fault event.

[0060] In some embodiments, the data modeling language includes YANG (Yet Another Next Generation) language, etc. The data content template is established based on the YANG language to reflect data formats such as data structure, data syntax, and data semantics.

[0061] Optionally, the fault event package includes a fault type field and other information fields, wherein the fault type field carries at least one of a fault identifier, a fault carrier, and a fault level corresponding to the fault event, and other information fields carry at least one of a fault occurrence time, a fault affected module, a fault relief status, and fault details.

[0062] In this way, fault events are encoded through the protocol server, which not only unifies the format of fault events but also provides more fault information, thereby making the fault management of the domain controller more comprehensive and facilitating users to view and debug faults.

[0063] In some embodiments, the fault event package is data in XML (Extensible Markup Language) format.

[0064] In some embodiments, the fault level includes one or more of CRITICAL, MAJOR, MINOR, WARNING, etc.

[0065] In some embodiments, the failure event includes one or more of hardware device failure, interface failure, software failure, functional failure, etc.

[0066] As shown in Table 1, the fault event package includes fault information such as fault identification, fault carrier, fault level, fault occurrence time, fault affected module, fault removal status, and fault details.

[0067] Table 1

[0068] Fault Information type Fields Fault identification uint16 fault-id Fault carrier string fault-source Fault Impact Module list <string> < / string> affected-objects Failure level enum fault-severity Fault clearing status bool is-cleared Fault details string fault-text Failure time yang:data-and-time event-time

[0069] Optionally, after establishing a fault communication link between the protocol server and the protocol client according to the transport layer, the method also includes: the fault management protocol also includes an operation layer, and the operation layer includes at least one data operation instruction; in response to the management device collecting any data operation instruction input by the user, the protocol client sends the data operation instruction to the protocol server through the fault communication link, so that the protocol server executes the data operation instruction.

[0070] In some embodiments, the operating instructions include configuring a query <get-config>, Configuration modification <edit-config>, configuration deletion <delete-config>, Data Acquisition <get>wait.

[0071] In this way, by setting the data operation instructions at the operation layer, not only the configuration data of the fault management protocol can be modified, but also the calling of the data method can be realized, thereby improving the flexibility of the fault management protocol.

[0072] In some embodiments, the fault management protocol includes at least one of the NETCONF (Network Configuration Protocol) protocol, the CLI (Command-line Interface) protocol, the SNMP (Simple Network Management Protocol) protocol, etc., wherein, on the one hand, before the emergence of the NETCONF protocol, the CLI protocol was the main method for automatically changing the configuration of the network, but because the CLIs defined by different manufacturers are different, users need to learn and develop adaptation scripts for each manufacturer respectively. At the same time, the frequently changed command structure and syntax make the CLI script difficult to maintain and costly. The output content of the traditional command line is unstructured, unpredictable, and easy to change, resulting in complex parsing, and it is difficult to achieve automatic parsing of the CLI script. On the other hand, the SNMP protocol uses the UDP transmission protocol, which cannot provide reliable and orderly data transmission, lacks effective security, and lacks a configuration transaction submission mechanism. It can only configure each object separately, rather than for a business. When multiple objects are configured at the same time, if some succeed and some fail, it will cause unknown impact on the network. At the same time, SNMP only manages a single device and does not support network-level configuration and multi-device configuration collaboration.

[0073] Combination Figure 4 As shown, the embodiment of the present disclosure provides a protocol stack of the NETCONF protocol, which includes, from bottom to top, an Ethernet layer, a TCP / IP layer, an SSH protocol layer, and a NETCONF protocol layer, that is, the data transmission link of NETCONF is based on connection-oriented secure transmission.

[0074] Combination Figure 5 As shown, the embodiment of the present disclosure provides a protocol layer of the NETCONF protocol, which includes a transport layer, a message layer, an operation layer, and a content layer from bottom to top; the transport layer is used to establish a fault communication link between the protocol server (Netconf-Server) and the protocol client (Netconf-Client) for data transmission, and its bottom layer relies on Ethernet, adopts a connection-oriented TCP / IP transmission protocol, and uses SSH protocol, TLS protocol and other security protocols to ensure data encryption; the message layer provides a communication model that does not depend on the transmission protocol, including the RPC protocol and the NOTIFICATION protocol, and the protocol client adopts <rpc>The element encapsulates the fault subscription request and sends the request to the protocol server through a secure, connection-oriented session. The protocol server passes <rpc-reply>The element encapsulates the response message of the operation request and feeds it back to the protocol client. In addition, the protocol server actively sends notification events to the client at any time through the NOTIFICATION protocol. The operation layer defines the configuration data of NETCONF through data operation instructions and <get>Operation obtains status operation data; the content layer is modeled using the YANG language to describe the configuration data of the NETCONF protocol; the YANG language is a data modeling language for the NETCONF protocol, which is used to define data structure, data syntax, data semantics, and configure data content templates. It is also used to establish communication interfaces so that data transmitted based on the NETCONF protocol must comply with the definition of the YANG language. The YANG language has the characteristics of good readability, easy learning, hierarchical tree structure, extensibility, reusability, and can be directly mapped to XML.

[0075] In this way, the protocol server and the protocol client are established in the domain controller and the management device respectively through the NETCONF protocol, and a fault communication link is established according to the transport layer, so that the protocol server encodes the fault event of the domain controller according to the content layer to obtain a fault event package, and sends the fault event package to the protocol client through the fault communication link. The protocol client parses the fault event package according to the content layer to obtain a fault notification. In this way, not only a fault communication link is established through the client / server structure to connect the domain controller and the management device, but also the fault event is encoded and parsed through the content layer in the fault management protocol to unify the format of the fault event, thereby realizing unified management of domain controller faults and improving fault management efficiency.

[0076] Optionally, after sending the fault event package to the protocol client via the fault communication link, the method also includes: the domain controller obtains a fault warning list and adds the fault event to the fault warning list; in response to the domain controller generating fault resolution information corresponding to the fault event, the protocol server encodes the fault resolution information according to the content layer, obtains a resolution information package corresponding to the fault resolution information, and sends the resolution information package to the protocol client via the fault communication link; the domain controller deletes the fault event from the fault warning list.

[0077] Combination Figure 6 As shown, the present disclosure implements a fault reporting system, including a domain controller 601 and a management device 602, and a fault communication link is established between the domain controller 601 and the management device 602 based on a fault management protocol, wherein the domain controller 601 includes a protocol server 6011, a device database 6012, and a fault management application 6013, the server and the database are connected via IPC (Inter-Process Communication), the database and the fault management application are connected via IPC, and the fault management application is used to generate fault events; the protocol server is used to encode the fault event according to the content layer, obtain the fault event package corresponding to the fault event, and send the fault event package to the protocol client via the fault communication link; the database is used to store the fault warning list.

[0078] In some embodiments, the device database comprises a Sysrepo database.

[0079] Optionally, after the protocol client parses the received fault event package according to the content layer and obtains the fault notification, the method also includes: the protocol client sends a list query request to the protocol server; the domain controller corresponding to the protocol server counts the number of fault events in the fault warning list; if the number of events is greater than a preset number threshold, the fault warning list is sent to the protocol client.

[0080] In some embodiments, the protocol client <get>Instructs the server to send a list query request.

[0081] In some embodiments, the preset quantity threshold includes 0-3, for example, the preset quantity threshold is 0.

[0082] Combination Figure 7 As shown, the embodiment of the present disclosure provides a method for reporting a domain controller fault, including:

[0083] Step S701, the protocol server sends a protocol connection request to the protocol client;

[0084] Step S702, the protocol client performs SSH authentication;

[0085] Step S703, the protocol client establishes a data transmission link between the protocol server and the protocol client;

[0086] Step S704, the protocol client sends a fault subscription request to the protocol server;

[0087] Step S705, the protocol server sends a subscription success message to the protocol client;

[0088] Step S706, the fault management application generates a fault event;

[0089] Step S707, the fault management application sends a fault event to the protocol server;

[0090] Step S708, the protocol server encodes the fault event according to the content layer to obtain a fault event package corresponding to the fault event;

[0091] Step S709, the protocol server sends a fault event package to the protocol client;

[0092] Step S710, the fault management application adds the fault event to the fault warning list;

[0093] Step S711, continue to execute the above-mentioned domain controller fault resolution reporting method.

[0094] Combination Figure 8 As shown, the embodiment of the present disclosure provides a method for reporting domain controller fault resolution, including:

[0095] Step S801, the fault management application generates fault resolution information corresponding to the fault event;

[0096] Step S802, the fault management application sends fault resolution information to the protocol server;

[0097] Step S803, the protocol server encodes the fault relief information according to the content layer to obtain a relief information packet corresponding to the fault relief information;

[0098] Step S804, the protocol server sends a release information packet to the protocol client;

[0099] Step S805, the fault management application deletes the fault event from the fault warning list;

[0100] Step S806, continue to execute the above-mentioned domain controller fault resolution reporting method.

[0101] Combination Fig. 9 As shown, the embodiment of the present disclosure provides a method for obtaining a fault warning list, including:

[0102] Step S901, the protocol client sends a list query request to the protocol server;

[0103] Step S902, the protocol server sends a list query request to the fault management application;

[0104] Step S903, the fault management application counts the number of fault events in the fault warning list;

[0105] Step S904: If there is a fault event in the fault warning list, the fault management application sends the fault warning list to the protocol server;

[0106] Step S905, the protocol server sends a fault warning list to the protocol client;

[0107] Step S906, continue to execute the above-mentioned domain controller fault resolution reporting method.

[0108] The domain controller fault reporting method provided by the embodiment of the present disclosure obtains a fault management protocol including a transport layer and a content layer, and respectively establishes a protocol server and a protocol client on the domain controller and a management device, and establishes a fault communication link according to the transport layer, so that the protocol server encodes the fault event of the domain controller according to the content layer to obtain a fault event package, and sends the fault event package to the protocol client through the fault communication link, and the protocol client parses the fault event package according to the content layer to obtain a fault notification, which has the following advantages:

[0109] First, not only does it establish a fault communication link through the client / server structure to connect the domain controller and the management device, but it also encodes and parses fault events through the content layer in the fault management protocol to unify the format of fault events, thereby achieving unified management of domain controller faults and improving fault management efficiency;

[0110] Second, the management device includes a communication device and / or a debugging device, wherein the fault notification is uploaded to the server through the communication device, and the domain controller is debugged through the debugging device, and the fault of the domain controller is managed from the aspects of data collection and instruction debugging, thereby improving the management scope of the domain controller fault;

[0111] Third, fault events are encoded through the protocol server, which not only unifies the format of fault events but also provides more fault information, thus making fault management of domain controllers more comprehensive and facilitating users to view and debug faults.

[0112] Fourth, by setting data operation instructions at the operation layer, not only the configuration data of the fault management protocol can be modified, but also the data method can be called, thereby improving the flexibility of the fault management protocol.

[0113] Combination Fig.10 As shown, the embodiment of the present disclosure provides a domain controller fault reporting system, including:

[0114] The acquisition module 1001 is used to acquire a vehicle terminal and a fault management protocol, wherein the vehicle terminal includes a management device and at least one domain controller, and the fault management protocol includes a transport layer and a content layer;

[0115] The establishment module 1002 is used to establish a protocol server corresponding to the domain controller and a protocol client corresponding to the management device, and to establish a fault communication link between the protocol server and the protocol client according to the transport layer;

[0116] The sending module 1003 is used for responding to the domain controller generating a fault event, the protocol server encoding the fault event according to the content layer, obtaining a fault event package corresponding to the fault event, and sending the fault event package to the protocol client through the fault communication link;

[0117] The parsing module 1004 is used by the protocol client to parse the received fault event package according to the content layer to obtain a fault notification.

[0118] The domain controller fault reporting system provided by the embodiment of the present disclosure is adopted, by obtaining the fault management protocol including the transport layer and the content layer, and establishing the protocol server and the protocol client in the domain controller and the management device respectively, and establishing a fault communication link according to the transport layer, so that the protocol server encodes the fault event of the domain controller according to the content layer to obtain a fault event package, and sends the fault event package to the protocol client through the fault communication link, and the protocol client parses the fault event package according to the content layer to obtain a fault notification. In this way, not only a fault communication link is established through the client / server structure to connect the domain controller and the management device, but also the fault event is encoded and parsed through the content layer in the fault management protocol to unify the format of the fault event, thereby realizing unified management of domain controller faults and improving fault management efficiency.

[0119] Fig.11 The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Fig.11 The computer system 1100 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0120] like Fig.11 As shown, the computer system 1100 includes a central processing unit (CPU) 1101, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1102 or the program loaded from the storage part 1108 to the random access memory (RAM) 1103, such as executing the method in the above embodiment. In the RAM 1103, various programs and data required for system operation are also stored. The CPU 1101, the ROM 1102 and the RAM 1103 are connected to each other through the bus 1104. The input / output (I / O) interface 1105 is also connected to the bus 1104.

[0121] The following components are connected to the I / O interface 1105: an input section 1106 including a keyboard, a mouse, etc.; an output section 1107 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 1108 including a hard disk, etc.; and a communication section 1109 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to the I / O interface 1105 as needed. A removable medium 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1110 as needed so that a computer program read therefrom is installed into the storage section 1108 as needed.

[0122] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 1109, and / or installed from a removable medium 1111. When the computer program is executed by a central processing unit (CPU) 1101, various functions defined in the system of the present application are executed.

[0123] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0124] The embodiments of the present disclosure further provide a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, any one of the methods in the embodiments is implemented.

[0125] The computer-readable storage medium in the embodiments of the present disclosure can be understood by ordinary technicians in the field: all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to the computer program. The aforementioned computer program can be stored in a computer-readable storage medium. When the program is executed, the execution includes the steps of the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0126] The electronic device disclosed in this embodiment includes a processor, a memory, a transceiver and a communication interface. The memory and the communication interface are connected to the processor and the transceiver and complete communication with each other. The memory is used to store computer programs, the communication interface is used to communicate, and the processor and the transceiver are used to run the computer program so that the electronic device executes each step of the above method.

[0127] In this embodiment, the memory may include a random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0128] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a graphics processing unit (GPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0129] The above description and the accompanying drawings fully illustrate the embodiments of the present disclosure so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent possible changes only. Unless explicitly required, separate components and functions are in an embodiment of the present application, and the order of operation may vary. Parts and subsamples of some embodiments may be included in or replace parts and subsamples of other embodiments. Moreover, the words used in the present application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and the claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include plural forms as well. Similarly, the term "and / or" as used in the present application refers to any and all possible combinations of listings containing one or more associated ones. In addition, when used in the present application, the term "comprise" and its variants "comprises" and / or comprising refer to the presence of stated sub-samples, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other sub-samples, wholes, steps, operations, elements, components and / or groups thereof. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method or device comprising the element. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can refer to the description of the method part.

[0130] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. Technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present disclosure. Technicians can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0131] In the embodiments disclosed herein, the disclosed methods and products (including but not limited to devices, equipment, etc.) can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units can be only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some sub-samples can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to implement this embodiment. In addition, each functional unit in the embodiment of the present disclosure may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit.

[0132] The flowchart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to the embodiment of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. In the description corresponding to the flowchart and the block diagram in the accompanying drawings, the operations or steps corresponding to different boxes can also occur in a different order from the order disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs the specified functions or actions, or may be implemented by a combination of dedicated hardware and computer instructions.< / get> < / get> < / rpc> < / get>

Claims

1. A method for reporting a domain controller fault, characterized in that: include: Acquire a vehicle terminal and a fault management protocol, wherein the vehicle terminal includes a management device and at least one domain controller, and the fault management protocol includes a transport layer and a content layer; Establishing a protocol server corresponding to the domain controller and a protocol client corresponding to the management device, and establishing a fault communication link between the protocol server and the protocol client according to the transport layer; In response to the domain controller generating a fault event, the protocol server encodes the fault event according to the content layer, obtains a fault event package corresponding to the fault event, and sends the fault event package to the protocol client through the fault communication link; The protocol client parses the received fault event package according to the content layer to obtain a fault notification.

2. The method for reporting a domain controller failure according to claim 1, characterized in that: Establishing a fault communication link between the protocol server and the protocol client according to the transport layer includes: The transport layer includes a data transmission protocol and a transport security protocol; The protocol server sends a protocol connection request to the protocol client; The protocol client establishes a data transmission link between the protocol server and the protocol client according to the transport layer, wherein the data transmission link is used to perform data transmission according to the data transmission protocol and the transmission security protocol; The protocol client sends a fault subscription request to the protocol server, so that the protocol server determines the data transmission link as a faulty communication link.

3. The method for reporting a domain controller failure according to claim 2, characterized in that: The protocol client sends a fault subscription request to the protocol server, including: The fault management protocol further comprises a message layer, wherein the message layer comprises at least one of a remote call rule and a message notification rule; The protocol client obtains a fault subscription request and performs message encapsulation on the fault subscription request according to the remote call rule; The protocol client sends the message-encapsulated fault subscription request to the protocol server, so that the protocol server establishes a message upload service according to the message notification rule, wherein the message upload service is used to send the fault event package to the protocol client through the fault communication link.

4. The method for reporting a domain controller failure according to claim 1, characterized in that: After sending the fault event package to the protocol client via the fault communication link, the method further includes: The domain controller obtains a fault warning list, and adds the fault event to the fault warning list; In response to the domain controller generating fault relief information corresponding to the fault event, the protocol server encodes the fault relief information according to the content layer to obtain a relief information packet corresponding to the fault relief information, and sends the relief information packet to the protocol client through the fault communication link; The domain controller deletes the fault event from the fault warning list.

5. The method for reporting a domain controller failure according to claim 4, characterized in that: The protocol client parses the received fault event packet according to the content layer, and after obtaining the fault notification, the method further includes: The protocol client sends a list query request to the protocol server; The domain controller corresponding to the protocol server counts the number of fault events in the fault warning list; If the event quantity is greater than a preset quantity threshold, the fault warning list is sent to the protocol client.

6. The method for reporting a domain controller failure according to any one of claims 1 to 5, characterized in that: The protocol server encodes the fault event according to the content layer to obtain a fault event package corresponding to the fault event, including: The content layer includes data modeling language and data content templates; Establishing a data transmission interface on the protocol server side according to the data modeling language; The fault event is filled into the data content template and encoded using the data transmission interface to obtain a fault event package corresponding to the fault event.

7. The method for reporting a domain controller failure according to any one of claims 1 to 5, characterized in that: The fault event package includes a fault type field and other information fields, wherein the fault type field carries at least one of a fault identifier, a fault carrier, and a fault level corresponding to the fault event, and the other information fields carry at least one of a fault occurrence time, a fault impact module, a fault relief status, and fault details.

8. The method for reporting a domain controller failure according to any one of claims 1 to 5, characterized in that: The management device includes at least one of the following: A communication device, used to establish an external network link between the communication device and a preset server end, and send the fault notification to the server end; The debugging device is used to display the fault notification, collect the user debugging instruction corresponding to the fault notification, and send the user debugging instruction to the domain controller so that the domain controller executes the user debugging instruction.

9. The method for reporting a domain controller failure according to any one of claims 1 to 5, characterized in that: After establishing the fault communication link between the protocol server and the protocol client according to the transport layer, the method further includes: The fault management protocol also includes an operation layer, the operation layer including at least one data operation instruction; In response to the management device collecting any data operation instruction input by the user, the protocol client sends the data operation instruction to the protocol server through the fault communication link, so that the protocol server executes the data operation instruction.

10. A domain controller fault reporting system, characterized in that: include: An acquisition module, used to acquire a vehicle terminal and a fault management protocol, wherein the vehicle terminal includes a management device and at least one domain controller, and the fault management protocol includes a transport layer and a content layer; An establishment module is used to establish a protocol server corresponding to the domain controller and a protocol client corresponding to the management device, and to establish a fault communication link between the protocol server and the protocol client according to the transport layer; a sending module, configured to, in response to the domain controller generating a fault event, encode the fault event according to the content layer, obtain a fault event package corresponding to the fault event, and send the fault event package to the protocol client through the fault communication link; The parsing module is used for the protocol client to parse the received fault event package according to the content layer to obtain a fault notification.

11. An electronic device, characterized in that: include: Processor and memory; The memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes the domain controller fault reporting method according to any one of claims 1 to 9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the domain controller fault reporting method according to any one of claims 1 to 9 is implemented.