CN115987755A

CN115987755A - Domain controller fault reporting method, system, electronic equipment and readable storage medium

Info

Publication number: CN115987755A
Application number: CN202211551691.5A
Authority: CN
Inventors: 郎世兵; 康轶非; 彭祥军; 姚志伟; 余隆山
Original assignee: Chongqing Changan Automobile Co Ltd
Current assignee: Chongqing Changan Automobile Co Ltd
Priority date: 2022-12-05
Filing date: 2022-12-05
Publication date: 2023-04-18

Abstract

The invention relates to the technical field of vehicle communication, and discloses a domain controller fault reporting method, a system, electronic equipment and a readable storage medium.

Description

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

Technical Field

The invention relates to the technical field of vehicle communication, in particular to a domain controller fault reporting method, a domain controller fault reporting system, electronic equipment and a readable storage medium.

Background

With the development of automobile intellectualization and informatization, the usage amount of vehicle ECU (Electronic Control Unit) chips is increasing, from an engine Control system, an air bag, an anti-lock system, electric power steering, a vehicle body Electronic stabilizing system to an intelligent instrument, an entertainment audio-visual system and an auxiliary driving system; there are also electric drive control, battery management systems, onboard charging systems on electric vehicles, as well as the booming development of onboard gateways, T-boxes (Telematics boxes) and autopilot systems, and such ECU-based distributed EEAs (Electronic/Electronic Architecture) make the vehicle systems more and more complex. In order to solve the above problems, a plurality of ECU functions with similar and separated functions are gradually integrated into a processor hardware platform with performance higher than that of the ECU through a domain controller, and the domain controller becomes more and more powerful and important along with the evolution of the electronic and electrical architecture of the whole vehicle. Due to the high safety and timeliness requirements of vehicles, the importance of fault management and fault warning for individual vehicle-mounted domain controllers is relatively increasing.

However, the existing fault management methods for vehicle-mounted domain controllers are independent, and each domain controller needs to be managed separately, so that the fault management process is disordered, the fault notification management is not uniform, and the fault notification management efficiency is low.

Disclosure of Invention

The following presents a simplified summary in order to provide a basic understanding of some aspects of the disclosed embodiments. This summary is not an extensive overview nor is intended to identify key/critical elements or to delineate the scope of such embodiments but rather as a prelude to the more detailed description that is presented later.

In view of the above drawbacks of the prior art, the present invention discloses a method, a system, an electronic device and a readable storage medium for reporting a domain controller failure, so as to improve the management efficiency of failure notification.

The invention discloses a domain controller fault reporting method, which comprises the following steps: the method comprises the steps of 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 transmission layer and a content layer; establishing a protocol server end corresponding to the domain controller and a protocol client end corresponding to the management equipment, and establishing a fault communication link between the protocol server end and the protocol client end according to the transmission layer; responding to the domain controller to generate a fault event, the protocol server side encodes the fault event according to the content layer to obtain a fault event packet corresponding to the fault event, and sends the fault event packet to the protocol client side through the fault communication link; and the protocol client analyzes the received fault event packet according to the content layer to obtain a fault notification.

Optionally, establishing a failure communication link between the protocol server and the protocol client according to the transport layer includes: the transmission layer comprises a data transmission protocol and a transmission safety protocol; the protocol server side sends a protocol connection request to the protocol client side; the protocol client establishes a data transmission link between the protocol server and the protocol client according to the transmission layer, wherein the data transmission link is used for carrying out data transmission according to the data transmission protocol and the transmission security protocol; and 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.

Optionally, the sending, by the protocol client, the failure subscription request to the protocol server includes: the fault management protocol further comprises a message layer comprising at least one of a remote invocation rule and a message notification rule; the protocol client acquires a fault subscription request and performs message encapsulation on the fault subscription request through the remote calling rule; and the protocol client sends the fault subscription request after message encapsulation to the protocol server so that the protocol server establishes a message uploading service according to the message notification rule, wherein the message uploading service is used for sending the fault event packet to the protocol client through the fault communication link.

Optionally, after the failure event packet is sent to the protocol client through the failure communication link, the method further includes: the domain controller acquires a fault warning list and adds the fault event into the fault warning list; responding to the domain controller to generate fault removing information corresponding to the fault event, the protocol server side encodes the fault removing information according to the content layer to obtain a removing information packet corresponding to the fault removing information, and sends the removing information packet to the protocol client side through the fault communication link; the domain controller deletes the failure event from the failure warning list.

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

Optionally, the encoding, by the protocol server, the fault event according to the content layer to obtain a fault event packet corresponding to the fault event includes: the content layer comprises a data modeling language and a data content template; establishing a data transmission interface at the protocol server terminal according to the data modeling language; and filling the fault event into the data content template by using the data transmission interface and coding to obtain a fault event packet corresponding to the fault event.

Optionally, the fault event packet includes a fault type field and other information fields, where the fault type field carries at least one of a fault identifier, a fault bearer, 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 affecting module, a fault release status, and a fault detail content.

Optionally, the management device comprises at least one of: the communication equipment is used for establishing an external network link between the communication equipment and a preset server side and sending the fault notification to the server side; and the debugging equipment is used for displaying the fault notification, acquiring a user debugging instruction corresponding to the fault notification, and issuing the user debugging instruction to the domain controller, so that the domain controller executes the user debugging instruction.

Optionally, after the failed communication link between the protocol server and the protocol client is established according to the transport layer, the method further includes: the fault management protocol further comprises an operational layer comprising at least one data manipulation instruction; and responding to any data operation instruction acquired by the management equipment and input by a user, and sending the data operation instruction to the protocol server side by the protocol client side through the fault communication link, so that the protocol server side executes the data operation instruction.

The invention discloses a domain controller fault reporting system, which comprises: the system comprises an acquisition module, a fault management module and a fault management module, wherein the acquisition module is used for acquiring a vehicle terminal and a fault management protocol, the vehicle terminal comprises a management device and at least one domain controller, and the fault management protocol comprises a transmission layer and a content layer; the establishing module is used for establishing a protocol server end corresponding to the domain controller and a protocol client end corresponding to the management equipment, and establishing a fault communication link between the protocol server end and the protocol client end according to the transmission layer; the sending module is used for responding to a fault event generated by the domain controller, the protocol server side encodes the fault event according to the content layer to obtain a fault event packet corresponding to the fault event, and the fault event packet is sent to the protocol client side through the fault communication link; and the analysis module is used for analyzing the received fault event packet by the protocol client according to the content layer to obtain a fault notification.

The invention discloses an electronic device, comprising: a processor and a memory; the memory is used for storing computer programs, and the processor is used for executing the computer programs stored by the memory so as to make the electronic equipment execute the method.

The invention discloses a computer-readable storage medium, on which a computer program is stored: which when executed by a processor implements the method described above.

The invention has the beneficial effects that:

the method comprises the steps of obtaining a fault management protocol comprising a transmission layer and a content layer, respectively establishing a protocol server side and a protocol client side on a domain controller and a management device, establishing a fault communication link according to the transmission layer, enabling the protocol server side to code a fault event of the domain controller according to the content layer to obtain a fault event packet, sending the fault event packet to the protocol client side through the fault communication link, and enabling the protocol client side to analyze the fault event packet according to the content layer to obtain a fault notification. Therefore, the fault communication link is established through the client/server structure to connect the domain controller and the management equipment, and the fault event is coded and analyzed through the content layer in the fault management protocol to unify the format of the fault event, so that the unified management of the domain controller fault is realized, and the fault management efficiency is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:

FIG. 1 is a schematic diagram of a five-domain centralized architecture in an embodiment of the present invention;

fig. 2 is a schematic flow chart of a domain controller fault reporting method in an embodiment of the present invention;

fig. 3 is a schematic structural diagram of a fault reporting system implementing a domain controller fault reporting method in an embodiment of the present invention;

fig. 4 is a schematic structural diagram of a protocol stack of a NETCONF protocol in an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a protocol layer of a NETCONF protocol in an embodiment of the present invention;

fig. 6 is a schematic structural diagram of another fault reporting system in an embodiment of the present invention;

fig. 7 is a schematic flowchart of another domain controller fault reporting method in an embodiment of the present invention;

fig. 8 is a schematic flow chart of a domain controller failure release reporting method in an embodiment of the present invention;

FIG. 9 is a flowchart illustrating a method for obtaining a fault warning list according to an embodiment of the present invention

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

fig. 11 is a schematic structural diagram of an electronic device in an embodiment of the invention.

Detailed Description

The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention. It should be noted that, in the following embodiments and examples, subsamples may be combined with each other without conflict.

It should be noted that the drawings provided in the following embodiments are only for illustrating the basic idea of the present invention, and the components related to the present invention are only shown in the drawings rather than drawn according to the number, shape and size of the components in actual implementation, and the type, quantity and proportion of the components in actual implementation may be changed freely, and the layout of the components may be more complicated.

In the following description, numerous details are set forth to provide a more thorough explanation of embodiments of the present invention, however, it will be apparent to one skilled in the art that embodiments of the present invention may be practiced without these specific details, and in other embodiments, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring embodiments of the present invention.

The terms "first," "second," and the like in the description and in the claims, and the above-described drawings of embodiments of the present disclosure, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the present disclosure described herein may be made. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions.

The term "plurality" means two or more, unless otherwise specified.

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 represents: a or B.

The term "and/or" is an associative relationship that describes objects, meaning that three relationships may exist. For example, a and/or B, represents: a or B, or A and B.

With reference to fig. 1, the embodiment of the present disclosure provides a five-domain centralized architecture, wherein functional domains are specifically divided, and a domain controller is divided into a Power domain (Power Train), a Chassis domain (Chassis), a Body domain (Body/Comfort), a Cockpit domain (Cockpit/information), and an automatic driving domain (ADAS), where the domain controller is a core of each functional domain of an automobile and mainly includes three parts, i.e., a domain master processor, an operating system, application software, and an algorithm, and the domain controller is a main core design concept of the domain controller, and depending on the domain master processor with high performance, abundant hardware interface resources, and strong software functional characteristics, the domain controller can integrate core functions that originally need many ECUs, greatly improve system functional integration, and add a standardized interface for data interaction, thereby greatly reducing development and manufacturing costs of the part.

Referring to fig. 2, an embodiment of the present disclosure provides a method for reporting a domain controller fault, including:

step S201, obtaining a vehicle terminal and a fault management protocol;

the vehicle terminal comprises management equipment and at least one domain controller, and the fault management protocol comprises a transmission layer and a content layer;

step S202, a protocol server end corresponding to the domain controller and a protocol client end corresponding to the management device are established, and a fault communication link between the protocol server end and the protocol client end is established according to a transmission layer;

step S203, responding to the domain controller to generate the fault event, the protocol server side encodes the fault event according to the content layer to obtain a fault event packet corresponding to the fault event, and sends the fault event packet to the protocol client side through the fault communication link;

and step S204, the protocol client analyzes the received fault event packet according to the content layer to obtain a fault notification.

By adopting the method for reporting the fault of the domain controller provided by the embodiment of the disclosure, the fault management protocol comprising the transmission layer and the content layer is obtained, the protocol server side and the protocol client side are respectively established on the domain controller and the management equipment, and the fault communication link is established according to the transmission layer, so that the protocol server side codes the fault event of the domain controller according to the content layer to obtain the fault event packet, and sends the fault event packet to the protocol client side through the fault communication link, and the protocol client side analyzes the fault event packet according to the content layer to obtain the fault notification. Therefore, the fault communication link is established through the client/server structure to connect the domain controller and the management equipment, and the fault event is coded and analyzed through the content layer in the fault management protocol to unify the format of the fault event, so that the unified management of the domain controller fault is realized, and the fault management efficiency is improved.

Optionally, the management device comprises at least one of: the communication equipment is used for establishing an external network link between the communication equipment and a preset server side and sending a fault notification to the server side; and the debugging equipment is used for displaying the fault notification, acquiring a user debugging instruction corresponding to the fault notification, and issuing the user debugging instruction to the domain controller, so that the domain controller executes the user debugging instruction.

Therefore, the management device comprises the communication device and/or the debugging device, the fault notification is uploaded to the server side through the communication device, the domain controller is debugged through the debugging device, the faults of the domain controller are managed from the aspects of data collection and instruction debugging, and the management range of the faults of the domain controller is expanded.

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, fifth Generation Mobile Communication Technology) module, and the like; the debugging equipment comprises at least one of a domain controller, a computer, a notebook computer, a smart phone and the like.

With reference to fig. 3, the present disclosure provides a fault reporting system for implementing the above-mentioned method for reporting a domain Controller fault, including a domain Controller module 301, a communication device 302, a debugging device 303, and a server 304, where the domain Controller module 301 includes an electronic unit 3011, a domain control application 3012, a domain control peripheral 3013, and a domain Controller 3014, the electronic unit 3011 is connected to the domain Controller 3014 through a CAN (Controller area network) bus, the domain control application 3012 and the domain control peripheral 3013 are connected to the domain Controller 3014 through application interfaces, the domain Controller 3014 is connected to at least one of the communication device 302 and the debugging device 303 through an ethernet, and the communication device 302 is connected to the server 304; establishing a protocol server end in a domain controller, establishing a protocol client end in communication equipment and debugging equipment, and establishing a fault communication link between the protocol server end and the protocol client end according to a transmission layer; responding to a domain controller to generate a fault event, the protocol server side encodes the fault event according to the content layer to obtain a fault event packet corresponding to the fault event, and sends the fault event packet to the protocol client side through a fault communication link; and the protocol client analyzes the received fault event packet according to the content layer to obtain a fault notification.

By adopting the fault reporting system provided by the embodiment of the disclosure, a fault management protocol comprising a transmission layer and a content layer is obtained, a protocol server side and a protocol client side are respectively established on a domain controller and a management device, and a fault communication link is established according to the transmission layer, so that the protocol server side encodes a fault event of the domain controller according to the content layer to obtain a fault event packet, and sends the fault event packet to the protocol client side through the fault communication link, and the protocol client side analyzes the fault event packet according to the content layer to obtain a fault notification. Therefore, the fault communication link is established through the client/server structure to connect the domain controller and the management equipment, and the fault event is coded and analyzed through the content layer in the fault management protocol to unify the format of the fault event, so that the unified management of the domain controller fault is realized, and the fault management efficiency is improved.

Optionally, establishing a failure communication link between the protocol server and the protocol client according to the transport layer includes: the transmission layer comprises a data transmission protocol and a transmission safety protocol; the protocol server side sends a protocol connection request to the protocol client side; the protocol client establishes a data transmission link between the protocol server and the protocol client according to the transmission layer, wherein the data transmission link is used for carrying out data transmission according to a data transmission protocol and a transmission security protocol; and 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.

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 the protocol connection request to the protocol client in a call-home manner.

In some embodiments, the management device and the domain controller are connected through an ethernet network, and the protocol server side sends a protocol connection request to the protocol client side through the ethernet network.

In some embodiments, the data Transmission Protocol includes a TCP/IP (Transmission Control Protocol/Internet Protocol ) Transmission Protocol, etc.; the Transport Security protocol includes one or more of SSH (Secure Shell protocol) protocol, TLS (Transport Layer Security) protocol, and the like.

Optionally, the sending, by the protocol client, the failure subscription request to the protocol server includes: the fault management protocol further comprises a message layer, wherein the message layer comprises at least one of a remote calling rule and a message notification rule; the protocol client side obtains a fault subscription request and performs message encapsulation on the fault subscription request through a remote calling rule; and the protocol client sends the fault subscription request after the message is encapsulated to the protocol server, so that the protocol server establishes a message uploading service according to the message notification rule, wherein the message uploading service is used for sending the fault event packet to the protocol client through the fault communication link.

In some embodiments, the Remote Call rule includes an RPC (Remote Procedure Call) protocol or the like, and the message NOTIFICATION rule includes a NOTIFICATION protocol or the like.

Optionally, the protocol server encodes the fault event according to the content layer to obtain a fault event packet corresponding to the fault event, including: the content layer comprises a data modeling language and a data content template; establishing a data transmission interface at a protocol server end according to a data modeling language; and filling the fault event into the data content template by using the data transmission interface and coding to obtain a fault event packet corresponding to the fault event.

In some embodiments, the data modeling language includes a YANG (Yet other Next Generation) language or the like, and the data content template is established based on the YANG language for reflecting data formats such as data structure, data syntax, data semantics and the like.

Therefore, the protocol server end encodes the fault event, so that the format of the fault event is unified, more fault information is provided, the fault management of the domain controller is more comprehensive, and a user can check and debug the fault conveniently.

In some embodiments, the failure event package is XML (Extensible Markup Language) formatted data.

In some embodiments, the fault levels include one or more of CRITICAL (criticacal), important (MAJOR), mild (MINOR), WARNING (WARNING), and the like.

In some embodiments, the failure event includes one or more of a hardware device failure, an interface failure, a software failure, a functional failure, and the like.

As shown in table 1, the fault event package includes fault information such as a fault identifier, a fault carrier, a fault level, fault occurrence time, a fault influence module, a fault release status, and fault details.

TABLE 1

Fault information	Type (B)	Field(s)
			Fault identification	uint16	fault-id
Fault carrier	string	fault-source
			Fault influencing module	list<string>	affected-objects
Failure class	enum	fault-severity
			Failure relieved state	bool	is-cleared
Details of faults	string	fault-text
			Time of occurrence of failure	yang:data-and-time	event-time

Optionally, after the failed communication link between the protocol server and the protocol client is established according to the transport layer, the method further includes: the fault management protocol further comprises an operation layer, wherein the operation layer comprises at least one data operation instruction; and responding to any data operation instruction input by the user and collected by the management equipment, and sending the data operation instruction to the protocol server side by the protocol client side through the fault communication link so that the protocol server side executes the data operation instruction.

In some embodiments, the operation instruction includes a configuration query < get-config >, a configuration modification < exit-config >, a configuration delete < delete-config >, a data fetch < get >, and the like.

Therefore, the data operation instruction is set through the operation layer, so that the configuration data of the fault management protocol is modified, the data method is called, and the flexibility of the fault management protocol is improved.

In some embodiments, the fault Management Protocol includes at least one of a NETCONF (Network Configuration Protocol) Protocol, a CLI (Command-line Interface) Protocol, an SNMP (Simple Network Management Protocol) Protocol, and the like, where on one hand, before the occurrence of the NETCONF Protocol, the CLI Protocol is a main method for automatically configuring and changing a Network, but since CLIs defined by vendors are different, a user needs to learn and develop an adaptation script for each vendor, and at the same time, command structures and syntax frequently changed make the CLI script difficult to maintain and costly, and traditional Command line output contents are unstructured, unpredictable and easy to change, which makes the resolution complicated, and the CLI script difficult to implement automatic resolution.

With reference to fig. 4, an embodiment of the present disclosure provides a protocol stack of a NETCONF protocol, which sequentially includes, from bottom to top, an Ethernet (Ethernet) layer, a TCP/IP layer, an SSH protocol layer, and a NETCONF protocol layer, that is, a data transmission link of the NETCONF is based on connection-oriented secure transmission.

With reference to fig. 5, an embodiment of the present disclosure provides a protocol layer of a NETCONF protocol, which sequentially includes, from bottom to top, a transport layer, a message layer, an operation layer, and a content layer; the transmission layer is used for establishing a fault communication link between a protocol Server end (Netconf-Server) and a protocol Client end (Netconf-Client) for data transmission, the bottom layer of the transmission layer depends on the Ethernet, adopts a TCP/IP transmission protocol based on connection-oriented, and ensures data encryption by an SSH protocol, a TLS protocol and the like; the message layer provides a communication model independent of a transmission protocol, which comprises an RPC protocol and a NOTIFICATION protocol, a protocol client side adopts < RPC > elements to package a fault subscription request and sends the request to a protocol server side through a safe connection-oriented session, the protocol server side packages a response message of the operation request through the < RPC-reply > elements and feeds the response message back to the protocol client side, and the protocol server side actively sends a NOTIFICATION event to the client side at any time through the NOTIFICATION protocol; the operation layer defines configuration data of NETCONF through a data operation instruction and obtains state operation data through < get > operation; the content layer is modeled through a YANG language to describe configuration data of a NETCONF protocol; the YANG language is a data modeling language for a NETCONF protocol, is used for defining a data structure, data grammar and data semantics, configuring a data content template and establishing a communication interface, so that data transmitted based on the NETCONF protocol all conform to the definition of the YANG language, wherein the YANG language has the characteristics of good readability, easy learning, hierarchical tree structure, expandability, reusability, capability of being directly mapped to XML and the like.

Thus, a protocol server side and a protocol client side are respectively established on a domain controller and a management device through a NETCONF protocol, a fault communication link is established according to a transmission layer, so that the protocol server side encodes a fault event of the domain controller according to a content layer to obtain a fault event packet, the fault event packet is sent to the protocol client side through the fault communication link, and the protocol client side analyzes the fault event packet according to the content layer to obtain a fault notification. Therefore, the fault communication link is established through the client/server structure to connect the domain controller and the management equipment, and the fault event is coded and analyzed through the content layer in the fault management protocol to unify the format of the fault event, so that the unified management of the domain controller fault is realized, and the fault management efficiency is improved.

Optionally, after the sending the failure event packet to the protocol client through the failure communication link, the method further includes: the domain controller acquires a fault warning list and adds a fault event into the fault warning list; responding to the domain controller to generate fault removing information corresponding to the fault event, the protocol server side encodes the fault removing information according to the content layer to obtain a removing information packet corresponding to the fault removing information, and sends the removing information packet to the protocol client side through the fault communication link; the domain controller deletes the failure event from the failure warning list.

With reference to fig. 6, the present disclosure provides a fault reporting system, including a domain controller 601 and a management device 602, where the domain controller 601 and the management device 602 are connected through a fault Communication link established based on a fault management protocol, where the domain controller 601 includes a protocol server 6011, an equipment database 6012, and a fault management application 6013, the server and the database are connected through an Inter-Process Communication (IPC), the database and the fault management application are connected through an IPC, and the fault management application is used to generate a fault event; the protocol server is used for coding the fault event according to the content layer to obtain a fault event packet corresponding to the fault event and sending the fault event packet to the protocol client through the fault communication link; the database is used for storing a fault warning list.

In some embodiments, the device database comprises a Sysrepo database.

Optionally, after the protocol client analyzes the received fault event packet 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; a domain controller corresponding to a protocol server side counts the event number of fault events in a fault warning list; and if the number of the events is larger than a preset number threshold value, sending the fault warning list to the protocol client.

In some embodiments, the protocol client sends a list query request to the protocol server via a < get > instruction.

In some embodiments, the predetermined number threshold comprises 0-3, for example, the predetermined number threshold is 0.

Referring to fig. 7, an embodiment of the present disclosure provides a method for reporting a domain controller fault, including:

step S701, a protocol server side sends a protocol connection request to a protocol client side;

step S702, the protocol client side carries out SSH authentication;

step S703, the protocol client establishes a data transmission link between the protocol server and the protocol client;

step S704, the protocol client sends a fault subscription request to the protocol server;

step S705, the protocol server side sends the successful subscription information to the protocol client side;

step S706, the fault management application generates a fault event;

step S707, the fault management application sends a fault event to the protocol server;

step S708, the protocol server side encodes the fault event according to the content layer to obtain a fault event packet corresponding to the fault event;

step S709, the protocol server side sends a fault event packet to the protocol client side;

step S710, adding the fault event into a fault warning list by the fault management application;

and step S711, continuing to execute the domain controller failure release reporting method.

As shown in fig. 8, an embodiment of the present disclosure provides a domain controller failure release reporting method, including:

step S801, generating fault release information corresponding to a fault event by a fault management application;

step S802, the fault management application sends fault removing information to a protocol server;

step S803, the protocol server side encodes the failure relief information according to the content layer to obtain a relief information packet corresponding to the failure relief information;

step S804, the protocol server side sends a release information packet to the protocol client side;

step S805, the fault management application deletes the fault event from the fault alert list;

and step S806, continuing to execute the domain controller failure release reporting method.

As shown in fig. 9, an embodiment of the present disclosure provides a method for acquiring a fault warning list, including:

step S901, a protocol client sends a list query request to a protocol server;

step S902, the protocol server side sends a list query request to the fault management application;

step S903, the fault management application counts the event number of the fault events in the fault warning list;

step S904, if the fault event exists in the fault warning list, the fault management application sends the fault warning list to the protocol server side;

step S905, the protocol server side sends a fault warning list to the protocol client side;

and step S906, continuing to execute the domain controller failure release reporting method.

By adopting the method for reporting the fault of the domain controller provided by the embodiment of the disclosure, the fault management protocol comprising the transmission layer and the content layer is obtained, the protocol server side and the protocol client side are respectively established on the domain controller and the management equipment, and the fault communication link is established according to the transmission layer, so that the protocol server side encodes the fault event of the domain controller according to the content layer to obtain the fault event packet, and sends the fault event packet to the protocol client side through the fault communication link, and the protocol client side analyzes the fault event packet according to the content layer to obtain the fault notification, and the method has the following advantages:

firstly, a fault communication link is established through a client/server structure to connect a domain controller and management equipment, and a fault event is coded and analyzed through a content layer in a fault management protocol to unify the format of the fault event, so that the unified management of the domain controller fault is realized, and the fault management efficiency is improved;

secondly, the management equipment comprises communication equipment and/or debugging equipment, wherein the fault notification is uploaded to the server side through the communication equipment, the domain controller is debugged through the debugging equipment, the faults of the domain controller are managed in the aspects of data collection and instruction debugging, and the management range of the faults of the domain controller is expanded;

thirdly, the fault event is coded through the protocol server side, so that the format of the fault event is unified, and more fault information is provided, so that the fault management of the domain controller is more comprehensive, and a user can conveniently check and debug the fault;

and fourthly, setting a data operation instruction through an operation layer, not only modifying the configuration data of the fault management protocol, but also calling a data method, and improving the flexibility of the fault management protocol.

With reference to fig. 10, an embodiment of the present disclosure provides a system for reporting a domain controller fault, including:

the obtaining module 1001 is configured to obtain a vehicle terminal and a fault management protocol, where 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;

the establishing module 1002 is configured to establish a protocol server corresponding to the domain controller and a protocol client corresponding to the management device, and establish a fault communication link between the protocol server and the protocol client according to the transport layer;

the sending module 1003 is configured to respond to a domain controller to generate a fault event, and the protocol server encodes the fault event according to the content layer to obtain a fault event packet corresponding to the fault event, and sends the fault event packet to the protocol client through the fault communication link;

the parsing module 1004 is configured to parse the received fault event packet according to the content layer by the protocol client, so as to obtain a fault notification.

By adopting the domain controller fault reporting system provided by the embodiment of the disclosure, a fault management protocol comprising a transmission layer and a content layer is obtained, a protocol server side and a protocol client side are respectively established on the domain controller and the management equipment, and a fault communication link is established according to the transmission layer, so that the protocol server side encodes a fault event of the domain controller according to the content layer to obtain a fault event packet, and sends the fault event packet to the protocol client side through the fault communication link, and the protocol client side analyzes the fault event packet according to the content layer to obtain a fault notification. Therefore, the fault communication link is established through the client/server structure to connect the domain controller and the management equipment, and the fault event is coded and analyzed through the content layer in the fault management protocol to unify the format of the fault event, so that the unified management of the domain controller fault is realized, and the fault management efficiency is improved.

FIG. 11 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application. It should be noted that the computer system 1100 of the electronic device shown in fig. 11 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 11, the computer system 1100 includes a Central Processing Unit (CPU) 1101, which can perform various appropriate actions and processes, such as executing the methods in the above-described embodiments, according to a program stored in a Read-Only Memory (ROM) 1102 or a program loaded from a storage section 1108 into a Random Access Memory (RAM) 1103. In the RAM 1103, various programs and data necessary for system operation are also stored. The CPU 1101, ROM 1102, and RAM 1103 are connected to each other by a bus 1104. An Input/Output (I/O) interface 1105 is also connected to bus 1104.

The following components are connected to the I/O interface 1105: an input portion 1106 including a keyboard, mouse, and the like; an output section 1107 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 1108 including a hard disk and the like; and a communication section 1109 including a network interface card such as a LAN (Local area network) card, a modem, or the like. The communication section 1109 performs communication processing via a network such as the internet. Drivers 1110 are 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, or the like, is mounted on the drive 1110 as necessary, so that a computer program read out therefrom is mounted into the storage section 1108 as necessary.

In particular, according to embodiments of the application, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising a computer program for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 1109 and/or installed from the 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.

It should be noted that the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having 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), a 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. In the present application, a computer-readable signal medium may include a propagated data signal with a computer program embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

The disclosed embodiments also provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor implements any of the methods in the embodiments.

The computer-readable storage medium in the embodiments of the present disclosure may be understood by those skilled in the art as follows: all or part of the steps for implementing the above method embodiments may be performed by hardware associated with a computer program. The aforementioned computer program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.

The electronic device disclosed in this embodiment includes a processor, a memory, a transceiver, and a communication interface, where the memory and the communication interface are connected to the processor and the transceiver and perform mutual communication, the memory is used for storing a computer program, the communication interface is used for performing communication, and the processor and the transceiver are used for operating the computer program, so that the electronic device performs the steps of the above method.

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.

The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components.

The above description and drawings sufficiently illustrate embodiments of the disclosure to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. The examples merely typify possible variations. Individual components and functions are in one embodiment of the application and the sequence of operations may vary unless explicitly required. Portions and subsamples of some embodiments may be included in or substituted for portions and subsamples of other embodiments. Furthermore, the words used in the specification are words of description for example only and are not limiting upon the claims. As used in the description of the embodiments and the claims, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Similarly, the term "and/or" as used in this application is meant to encompass any and all possible combinations of one or more of the associated listed. Furthermore, the terms "comprises," "comprising," and variations thereof, when used in this application, specify the presence of stated sub-samples, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other sub-samples, integers, steps, operations, elements, components, and/or groups thereof. Without further limitation, an element defined by the phrase "comprising one of 8230," does not exclude the presence of another identical element in a process, method or device comprising the element. In this document, each embodiment may be described with emphasis on differences from other embodiments, and the same and similar parts between the respective embodiments may be referred to each other. For methods, products, etc. of the embodiment disclosure, reference may be made to the description of the method section for relevance if it corresponds to the method section of the embodiment disclosure.

Those of skill in the art would appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software may depend upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments. It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the apparatus and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments disclosed herein, the disclosed methods, products (including but not limited to devices, apparatuses, etc.) may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit may be merely a division of a logical function, and an actual implementation may have another division, for example, a plurality of units or components may be combined or may be integrated into another system, or some subsamples may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form. Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to implement the present embodiment. In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. In the description corresponding to the flowcharts and block diagrams in the figures, operations or steps corresponding to different blocks may also occur in different orders than disclosed in the description, and sometimes there is no specific order between the different operations or steps. For example, two sequential operations or steps may in fact be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. Each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Claims

1. A domain controller fault reporting method is characterized by comprising the following steps:

the method comprises the steps of 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 transmission layer and a content layer;

establishing a protocol server end corresponding to the domain controller and a protocol client end corresponding to the management equipment, and establishing a fault communication link between the protocol server end and the protocol client end according to the transmission layer;

responding to the domain controller to generate a fault event, the protocol server side encodes the fault event according to the content layer to obtain a fault event packet corresponding to the fault event, and sends the fault event packet to the protocol client side through the fault communication link;

and the protocol client analyzes the received fault event packet according to the content layer to obtain a fault notification.

2. The domain controller failure reporting method of claim 1, wherein establishing the failure communication link between the protocol server and the protocol client according to the transport layer comprises:

the transmission layer comprises a data transmission protocol and a transmission safety protocol;

the protocol server side sends a protocol connection request to the protocol client side;

the protocol client establishes a data transmission link between the protocol server and the protocol client according to the transmission layer, wherein the data transmission link is used for carrying out data transmission according to the data transmission protocol and the transmission security protocol;

and 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.

3. A domain controller failure reporting method according to claim 2, wherein the sending, by the protocol client, a failure subscription request to the protocol server includes:

the fault management protocol further includes a message layer including at least one of a remote invocation rule and a message notification rule;

the protocol client acquires a fault subscription request and performs message encapsulation on the fault subscription request through the remote calling rule;

and the protocol client sends the fault subscription request after message encapsulation to the protocol server so that the protocol server establishes a message uploading service according to the message notification rule, wherein the message uploading service is used for sending the fault event packet to the protocol client through the fault communication link.

4. A domain controller failure reporting method as claimed in claim 1, wherein after sending the failure event packet to the protocol client via the failure communication link, the method further comprises:

the domain controller acquires a fault warning list and adds the fault event into the fault warning list;

responding to the domain controller to generate fault removing information corresponding to the fault event, the protocol server side encodes the fault removing information according to the content layer to obtain a removing information packet corresponding to the fault removing information, and sends the removing information packet to the protocol client side through the fault communication link;

the domain controller deletes the failure event from the failure warning list.

5. A domain controller failure reporting method as claimed in claim 4, wherein the protocol client parses the received failure event packet according to the content layer, and after obtaining the failure notification, the method further comprises:

the protocol client sends a list query request to the protocol server;

a domain controller corresponding to the protocol server side counts the event number of the fault events in the fault warning list;

and if the event number is greater than the preset number threshold, sending the fault warning list to the protocol client.

6. A domain controller fault reporting method as claimed in any one of claims 1 to 5, wherein the protocol server side encodes the fault event according to the content layer to obtain a fault event packet corresponding to the fault event, including:

the content layer comprises a data modeling language and a data content template;

establishing a data transmission interface at the protocol server terminal according to the data modeling language;

and filling the fault event into the data content template by using the data transmission interface and coding to obtain a fault event packet corresponding to the fault event.

7. A method for reporting a fault on a domain controller according to any one of claims 1 to 5, wherein the fault event packet includes a fault type field and other information fields, wherein the fault type field carries at least one of a fault identifier, a fault bearer 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 affecting module, a fault release status and fault details.

8. A domain controller fault reporting method according to any of claims 1 to 5, wherein the management device comprises at least one of:

the communication equipment is used for establishing an external network link between the communication equipment and a preset server side and sending the fault notification to the server side;

and the debugging equipment is used for displaying the fault notification, acquiring a user debugging instruction corresponding to the fault notification and issuing the user debugging instruction to the domain controller so that the domain controller executes the user debugging instruction.

9. A domain controller failure reporting method as claimed in any one of claims 1 to 5, wherein after establishing the failure communication link between the protocol server and the protocol client according to the transport layer, the method further comprises:

the fault management protocol further comprises an operational layer comprising at least one data manipulation instruction;

and responding to any data operation instruction acquired by the management equipment and input by a user, and sending the data operation instruction to the protocol server side by the protocol client side through the fault communication link, so that the protocol server side executes the data operation instruction.

10. A domain controller fault reporting system is characterized by comprising:

the system comprises an acquisition module, a fault management module and a fault management module, wherein the acquisition module is used for acquiring a vehicle terminal and a fault management protocol, the vehicle terminal comprises a management device and at least one domain controller, and the fault management protocol comprises a transmission layer and a content layer;

the establishing module is used for establishing a protocol server end corresponding to the domain controller and a protocol client end corresponding to the management equipment, and establishing a fault communication link between the protocol server end and the protocol client end according to the transmission layer;

the sending module is used for responding to a fault event generated by the domain controller, the protocol server side encodes the fault event according to the content layer to obtain a fault event packet corresponding to the fault event, and the fault event packet is sent to the protocol client side through the fault communication link;

and the analysis module is used for analyzing the received fault event packet by the protocol client according to the content layer to obtain a fault notification.

11. An electronic device, comprising: a processor and a memory;

the memory is configured to store a computer program, and the processor is configured to execute the computer program stored in the memory, so as to enable the electronic device to perform the domain controller fault reporting method according to any one of claims 1 to 9.

12. A computer-readable storage medium having stored thereon a computer program, characterized in that:

the computer program, when executed by a processor, implements the domain controller failure reporting method of any of claims 1 to 9.