Vehicle dormancy control method, electronic device, network equipment, vehicle and medium

Abstract

The embodiment of the invention provides a vehicle dormancy control method, an electronic device, network equipment, a vehicle and a medium, and the method comprises the steps: monitoring an abnormal wake-up message sent by a network element in a vehicle network when the vehicle is in a network dormancy state; and when the abnormal wake-up message is monitored, positioning a first network element which abnormally wakes up the vehicle network based on the abnormal wake-up message. In other words, after the vehicle enters the network dormant state, the gateway keeps starting the function of monitoring the abnormal wake-up message and continuously monitors the abnormal wake-up message in the network, so that the abnormal wake-up network element can be positioned based on the monitored abnormal wake-up message, and positioning of the abnormal wake-up network element is realized.

Description

Technical Field

[0001] The present application belongs to the field of automobile technology, and specifically relates to a vehicle sleep control method, an electronic device, a network device, a vehicle and a medium. Background Art

[0002] In the field of automotive technology, energy conservation and reducing energy consumption are important considerations. To achieve this goal, the vehicle network is controlled to enter a dormant state when not in use, during which the vehicle's Electronic Control Unit (ECU) and other network devices reduce activity to reduce energy consumption.

[0003] However, in some scenarios, the vehicle network may be abnormally awakened in a dormant state. In the prior art, once the vehicle network enters the dormant state, the vehicle cannot accurately find the wake-up source that causes the abnormal awakening of the vehicle network. Summary of the invention

[0004] Embodiments of the present application provide a vehicle dormancy control method, an electronic device, a network device, a vehicle, and a medium to solve the problem of low reliability of abnormal wake-up monitoring of vehicle networks in the prior art.

[0005] A first aspect of an embodiment of the present application provides a vehicle dormancy control method, the method comprising:

[0006] When the vehicle is in a network dormant state, monitoring abnormal wake-up messages sent by network elements in the vehicle network;

[0007] When the abnormal wake-up message is detected, the first network element of the vehicle network that abnormally wakes up is located based on the abnormal wake-up message.

[0008] Optionally, the abnormal awakening message includes: a first network element identifier, where the first network element identifier is an identifier of a network element that sends the abnormal awakening message;

[0009] The locating, based on the abnormal wake-up message, the first network element that abnormally wakes up the vehicle network includes:

[0010] Based on the first network element identifier in the abnormal awakening message, it is determined that the network element corresponding to the first network element identifier is the first network element that abnormally awakens the vehicle network.

[0011] Optionally, the abnormal wake-up message also includes: an abnormal wake-up identifier and / or an abnormal wake-up reason, wherein the abnormal wake-up identifier is used to indicate that the message it contains is an abnormal wake-up message, and the abnormal wake-up reason is used to indicate the reason why the first network element abnormally wakes up the vehicle network.

[0012] Optionally, when the abnormal wake-up message is detected, the vehicle switches from a network sleep state to a network normal state.

[0013] Optionally, also include:

[0014] When the vehicle is in a network monitoring state, monitoring abnormal non-sleep messages sent by network elements in the vehicle network;

[0015] Based on the abnormal non-sleep message, a second network element causing the vehicle network to be abnormally non-sleep is located.

[0016] Optionally, the abnormal non-sleep message includes a second network element identifier, where the second network element identifier is an identifier of a network element that sends the abnormal non-sleep message;

[0017] The locating the second network element causing the abnormal non-sleep of the vehicle network based on the abnormal non-sleep message includes:

[0018] Based on the second network element identifier in the abnormal non-sleep message, it is determined that the network element corresponding to the second network element identifier is the second network element that causes the vehicle network to be abnormally non-sleep.

[0019] Optionally, the abnormal non-sleep message also includes: an abnormal non-sleep identifier and / or an abnormal non-sleep reason, the abnormal non-sleep identifier is used to indicate that the message it contains is an abnormal non-sleep message, and the abnormal non-sleep reason is used to indicate the reason why the second network element is abnormally non-sleep.

[0020] Optionally, also include:

[0021] Based on the abnormal non-sleep message, generating a forced sleep message;

[0022] The forced sleep message is sent to the second network element, where the forced sleep message is used to instruct the second network element to stop sending the abnormal non-sleep message.

[0023] Optionally, the forced sleep message is also used to instruct the second network element to invalidate a target wake-up condition of the second network element, where the target wake-up condition at least includes a wake-up condition that causes the vehicle network to abnormally not sleep.

[0024] Optionally, when the vehicle meets the network sleep condition, the vehicle switches from the normal network state to the network sleep state; or, when the vehicle meets the network sleep condition, the vehicle switches from the network monitoring state to the network sleep state.

[0025] Optionally, when the vehicle meets the conditions for entering the network monitoring state, the vehicle switches from the normal network state to the network monitoring state.

[0026] Optionally, when the vehicle is in the normal network state or the network monitoring state, when a preset first timer times out, the vehicle meets the bus sleep condition; wherein, the first timer is configured to start after the vehicle is powered off, and reset when any message of the vehicle network is monitored.

[0027] Optionally, when the vehicle is in the normal network state, when a preset second timer times out, the vehicle meets the conditions for entering the network monitoring state; wherein, the second timer is configured to start after the vehicle is powered off, and reset when a normal non-sleeping message of the vehicle network is monitored.

[0028] Optionally, the second timer is also configured to terminate when the first timer times out, wherein the timing duration of the first timer is shorter than the timing duration of the second timer.

[0029] Optionally, the second timer is further configured to start after the abnormal wake-up message is detected.

[0030] Optionally, the second timer is also configured to terminate after timeout.

[0031] Optionally, when the vehicle meets a preset normal non-sleep condition, the vehicle enters a network normal state from a network monitoring state.

[0032] Optionally, when the vehicle is in the network monitoring state, when a preset third timer times out, the vehicle meets the normal non-sleep condition; wherein the third timer is configured to start after the second timer times out.

[0033] Optionally, the third timer is further configured to terminate when the first timer times out, and the timing duration of the first timer is shorter than the timing duration of the third timer.

[0034] Optionally, when the vehicle is in the network monitoring state, when a normal non-sleep message is monitored, the vehicle meets the normal non-sleep condition.

[0035] Optionally, the third timer is also configured to terminate after detecting the normal non-sleeping message when the vehicle is in the network monitoring state.

[0036] Optionally, the second timer is also configured to start after detecting the normal non-sleeping message when the vehicle is in the network monitoring state.

[0037] Optionally, the second timer is configured to start after the third timer times out.

[0038] Optionally, the third timer is also configured to terminate after timing out.

[0039] Optionally, also include:

[0040] Based on the abnormal wake-up message, generate a first monitoring message;

[0041] The first monitoring message is sent to a cloud server, or the first monitoring message is sent to a communication device of the vehicle, so that the communication device sends the first monitoring message to the cloud server.

[0042] Optionally, the generating a first monitoring message based on the abnormal wake-up message includes:

[0043] The first abnormality related information in the abnormal awakening message is encapsulated into a first monitoring message, wherein the first abnormality related information includes a first network element identifier, and the first network element identifier is an identifier of a network element that sends the abnormal awakening message.

[0044] Optionally, the first exception-related information also includes: an abnormal wake-up flag and / or an abnormal wake-up reason, the abnormal wake-up flag is used to indicate that the message it contains is an abnormal wake-up message, and the abnormal wake-up reason is used to indicate the reason why the first network element abnormally wakes up the vehicle network.

[0045] Optionally, if at least two abnormal wake-up messages are monitored, encapsulating the first abnormality related information in the abnormal wake-up message into the first monitoring message includes:

[0046] The first exception related information in the at least two exception wake-up messages is sequentially encapsulated into the first monitoring message.

[0047] Optionally, also include:

[0048] Based on the abnormal non-sleep message, generating a second monitoring message;

[0049] The second monitoring message is sent to the cloud server, or the second monitoring message is sent to the communication device of the vehicle, so that the communication device sends the second monitoring message to the cloud server.

[0050] Optionally, the generating a second monitoring message based on the abnormal non-sleep message includes:

[0051] The second abnormality related information in the abnormal non-sleep message is encapsulated into the second monitoring message, wherein the second abnormality related information includes a second network element identifier, and the second network element identifier is an identifier of a network element that sends the abnormal non-sleep message.

[0052] Optionally, the second abnormality related information also includes: an abnormal non-sleep flag and / or an abnormal non-sleep reason, the abnormal non-sleep flag is used to indicate that the message it contains is an abnormal non-sleep message, and the abnormal non-sleep reason is used to indicate the reason why the second network element is abnormally non-sleep.

[0053] Optionally, if at least two abnormal non-sleep messages are monitored, encapsulating the second abnormality related information in the abnormal non-sleep message into the second monitoring message includes:

[0054] The second abnormality related information in the at least two abnormal non-sleep messages is sequentially encapsulated into the second monitoring message.

[0055] A second aspect of an embodiment of the present application provides a vehicle dormancy control device, the device comprising:

[0056] A monitoring module, used for monitoring abnormal wake-up messages sent by network elements in the vehicle network when the vehicle is in a network dormant state;

[0057] The processing module is used to locate the first network element that abnormally wakes up the vehicle network based on the abnormal wake-up message when the abnormal wake-up message is monitored.

[0058] Optionally, the abnormal awakening message includes: a first network element identifier, where the first network element identifier is an identifier of a network element that sends the abnormal awakening message;

[0059] The processing module is specifically configured to determine, based on the first network element identifier in the abnormal awakening message, that the network element corresponding to the first network element identifier is the first network element that abnormally awakens the vehicle network.

[0060] Optionally, the abnormal wake-up message also includes: an abnormal wake-up identifier and / or an abnormal wake-up reason, wherein the abnormal wake-up identifier is used to indicate that the message it contains is an abnormal wake-up message, and the abnormal wake-up reason is used to indicate the reason why the first network element abnormally wakes up the vehicle network.

[0061] Optionally, when the abnormal wake-up message is detected, the vehicle switches from a network sleep state to a network normal state.

[0062] Optionally, the monitoring module is further used to monitor abnormal non-sleep messages sent by network elements in the vehicle network when the vehicle is in a network monitoring state;

[0063] The processing module is further used to locate the second network element that causes the vehicle network to be abnormally non-sleeping based on the abnormal non-sleeping message.

[0064] Optionally, the abnormal non-sleep message includes a second network element identifier, where the second network element identifier is an identifier of a network element that sends the abnormal non-sleep message;

[0065] The processing module is specifically configured to determine, based on the second network element identifier in the abnormal non-sleep message, that the network element corresponding to the second network element identifier is the second network element that causes the vehicle network to be abnormally non-sleep.

[0066] Optionally, the abnormal non-sleep message also includes: an abnormal non-sleep identifier and / or an abnormal non-sleep reason, the abnormal non-sleep identifier is used to indicate that the message it contains is an abnormal non-sleep message, and the abnormal non-sleep reason is used to indicate the reason why the second network element is abnormally non-sleep.

[0067] Optionally, the processing module is further used to generate a forced sleep message based on the abnormal non-sleep message;

[0068] The sending module is used to send the forced sleep message to the second network element, and the forced sleep message is used to instruct the second network element to stop sending the abnormal non-sleep message.

[0069] Optionally, the forced sleep message is also used to instruct the second network element to invalidate a target wake-up condition of the second network element, where the target wake-up condition at least includes a wake-up condition that causes the vehicle network to abnormally not sleep.

[0070] Optionally, when the vehicle meets the network sleep condition, the vehicle switches from the normal network state to the network sleep state; or, when the vehicle meets the network sleep condition, the vehicle switches from the network monitoring state to the network sleep state.

[0071] Optionally, when the vehicle meets the conditions for entering the network monitoring state, the vehicle switches from the normal network state to the network monitoring state.

[0072] Optionally, when the vehicle is in the normal network state or the network monitoring state, when a preset first timer times out, the vehicle meets the bus sleep condition; wherein, the first timer is configured to start after the vehicle is powered off, and reset when any message of the vehicle network is monitored.

[0073] Optionally, when the vehicle is in the normal network state, when a preset second timer times out, the vehicle meets the conditions for entering the network monitoring state; wherein, the second timer is configured to start after the vehicle is powered off, and reset when a normal non-sleeping message of the vehicle network is monitored.

[0074] Optionally, the second timer is also configured to terminate when the first timer times out, wherein the timing duration of the first timer is shorter than the timing duration of the second timer.

[0075] Optionally, the second timer is further configured to start after the abnormal wake-up message is detected.

[0076] Optionally, the second timer is also configured to terminate after timeout.

[0077] Optionally, when the vehicle meets a preset normal non-sleep condition, the vehicle enters a network normal state from a network monitoring state.

[0078] Optionally, when the vehicle is in the network monitoring state, when a preset third timer times out, the vehicle meets the normal non-sleep condition; wherein the third timer is configured to start after the second timer times out.

[0079] Optionally, the third timer is further configured to terminate when the first timer times out, and the timing duration of the first timer is shorter than the timing duration of the third timer.

[0080] Optionally, when the vehicle is in the network monitoring state, when a normal non-sleep message is monitored, the vehicle meets the normal non-sleep condition.

[0081] Optionally, the third timer is also configured to terminate after detecting the normal non-sleeping message when the vehicle is in the network monitoring state.

[0082] Optionally, the second timer is also configured to start after detecting the normal non-sleeping message when the vehicle is in the network monitoring state.

[0083] Optionally, the second timer is configured to start after the third timer times out.

[0084] Optionally, the third timer is also configured to terminate after timing out.

[0085] Optionally, the processing module is further used to generate a first monitoring message based on the abnormal wake-up message;

[0086] The sending module is further used to send the first monitoring message to the cloud server, or to send the first monitoring message to the communication device of the vehicle, so that the communication device sends the first monitoring message to the cloud server.

[0087] Optionally, the processing module is specifically used to encapsulate the first exception related information in the abnormal wake-up message into a first monitoring message, wherein the first exception related information includes a first network element identifier, and the first network element identifier is an identifier of the network element that sends the abnormal wake-up message.

[0088] Optionally, the first exception-related information also includes: an abnormal wake-up flag and / or an abnormal wake-up reason, the abnormal wake-up flag is used to indicate that the message it contains is an abnormal wake-up message, and the abnormal wake-up reason is used to indicate the reason why the first network element abnormally wakes up the vehicle network.

[0089] Optionally, the processing module is specifically used to encapsulate the first exception related information in the at least two exception wake-up messages into the first monitoring message in sequence.

[0090] Optionally, the processing module is further used to generate a second monitoring message based on the abnormal non-sleep message;

[0091] The sending module is further used to send the second monitoring message to the cloud server, or to send the second monitoring message to the communication device of the vehicle, so that the communication device sends the second monitoring message to the cloud server.

[0092] Optionally, the processing module is specifically used to encapsulate the second exception related information in the abnormal non-sleep message into the second monitoring message, wherein the second exception related information includes a second network element identifier, and the second network element identifier is the identifier of the network element that sends the abnormal non-sleep message.

[0093] Optionally, the second abnormality related information also includes: an abnormal non-sleep flag and / or an abnormal non-sleep reason, the abnormal non-sleep flag is used to indicate that the message it contains is an abnormal non-sleep message, and the abnormal non-sleep reason is used to indicate the reason why the second network element is abnormally non-sleep.

[0094] Optionally, the processing module is specifically used to encapsulate the second abnormality related information in the at least two abnormal non-sleep messages into the second monitoring message in sequence.

[0095] A third aspect of an embodiment of the present application provides an electronic device, comprising: a processor, the processor is used to connect to a memory, the memory stores a computer program / instructions that can be run on the processor, and when the computer program / instructions are executed by the processor, the steps of the vehicle dormancy control method as described in any one of the first aspects are implemented.

[0096] A fourth aspect of an embodiment of the present application provides a network device, wherein the network device includes the electronic device as described in the third aspect.

[0097] A fifth aspect of an embodiment of the present application provides an electronic and electrical architecture, which includes the electronic device as described in the third aspect, or the network device as described in the fourth aspect.

[0098] A sixth aspect of an embodiment of the present application provides a vehicle, comprising the electronic device as described in the third aspect, or the network device as described in the fourth aspect, or the electronic and electrical architecture as described in the fifth aspect.

[0099] A seventh aspect of an embodiment of the present application provides a computer-readable storage medium, on which a computer program / instruction is stored. When the computer program / instruction is executed by a processor, the steps of the vehicle dormancy control method as described in any one of the first aspects are implemented.

[0100] An eighth aspect of an embodiment of the present application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps of the vehicle dormancy control method as described in any one of the first aspects.

[0101] The vehicle dormancy control method, electronic device, network equipment, vehicle and medium provided in the embodiments of the present application monitor the abnormal wake-up message sent by the network element in the vehicle network when the vehicle is in the network dormancy state; when the abnormal wake-up message is detected, the first network element of the vehicle network that abnormally wakes up is located based on the abnormal wake-up message. That is, after the vehicle enters the network dormancy state, the gateway keeps the function of monitoring the abnormal wake-up message turned on, and continuously monitors the abnormal wake-up message in the network, so that the abnormal wake-up network element can be located based on the abnormal wake-up message obtained by monitoring, thereby realizing the location of the abnormal wake-up network element. BRIEF DESCRIPTION OF THE DRAWINGS

[0102] Figure 1 A schematic diagram of a process flow of a vehicle dormancy control method provided in an embodiment of the present application;

[0103] Figure 2 A schematic flow chart of another vehicle dormancy control method provided in an embodiment of the present application;

[0104] Figure 3 A schematic flow chart of another method for controlling vehicle dormancy provided in an embodiment of the present application;

[0105] Figure 4 A schematic diagram of the structure of a vehicle state machine provided in an embodiment of the present application;

[0106] Figure 5 A flowchart of another method for controlling vehicle dormancy provided in an embodiment of the present application;

[0107] Figure 6A flowchart of another method for controlling vehicle dormancy provided in an embodiment of the present application;

[0108] Figure 7 A flowchart of another method for controlling vehicle dormancy provided in an embodiment of the present application;

[0109] Figure 8 A flowchart of another method for controlling vehicle dormancy provided in an embodiment of the present application;

[0110] Fig. 9 A flowchart of another method for controlling vehicle dormancy provided in an embodiment of the present application;

[0111] Fig.10 A schematic diagram of the structure of a vehicle hibernation control device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0112] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0113] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0114] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

[0115] In the related art, the data of each ECU on the vehicle is obtained through the cloud of the gateway (GW), the telematics head unit (THU) and the telematics service provider (TSP). The power-loss system designed based on the vehicle controller identifies and analyzes whether the ECU is in network non-sleep and the reason for non-sleep. The power-loss system automatically sends a reset instruction to the non-sleep ECU remotely and resets it. However, when the gateway in the above technology monitors the abnormal awakening of the vehicle network, the gateway may miss the network management message sent by the controller during the initialization time because the vehicle is in a dormant state and the gateway enters a low-power state. As a result, when the vehicle is abnormally awakened in a dormant state, it is impossible to locate the awakening network element that causes the abnormal awakening of the vehicle. In response to the above problem, a bus dormant state is set. After the vehicle enters the bus dormant state, the network management message is continuously monitored so that the abnormal awakening network element that causes the abnormal awakening of the vehicle can be accurately located based on the network management message. Further, the gateway determines the cause of the awakening of the abnormal awakening network element according to the awakening cause in the network management message. Furthermore, after the gateway detects the abnormal non-sleep message, the gateway directly locates the abnormal non-sleep network element, and also generates a forced sleep instruction based on the abnormal non-sleep message to control the abnormal non-sleep network element to enter the bus sleep state. There is no need to transmit instructions through an external network and is not limited by network stability. Therefore, the control efficiency and reliability of the abnormal non-sleep network element are improved.

[0116] In the vehicle sleep control method provided in the embodiment of the present application, when the ECU in the vehicle is in sleep mode, the network is in a low power consumption state, and when the ECU in the vehicle is in wake-up mode, the network is in a normal working state. After the vehicle is powered off, the modes experienced by each ECU in the vehicle specifically include but are not limited to the following possible modes:

[0117] One possible mode is normal sleep. When the vehicle is powered off, all ECUs in the vehicle usually enter sleep mode. For example, the multimedia system, air conditioning system and lighting system will be automatically turned off. At this time, these systems are in normal sleep mode.

[0118] Another possible mode is abnormal non-sleep state. When the vehicle is powered off, some control systems may not be able to enter sleep mode normally due to factors such as network signals. For example, the microprocessor in the seat memory system continues to run due to a software error and keeps trying to read or store seat position data. Another example is that the Bluetooth processor of the multimedia system fails to receive the sleep command due to unstable network signals and remains active. At this time, these systems are in an abnormal non-sleep state.

[0119] Another possible mode is normal wake-up. After the vehicle is normally asleep, some control systems may be awakened due to user needs. For example, the user remotely starts the vehicle through a mobile phone application, and the vehicle's telematics system is awakened and executes the user's instructions. For example, the user connects a charging gun to the vehicle, and the on-board charging system is awakened. The on-board charging system then wakes up other control systems such as the battery management system through the bus network, thereby realizing the AC charging function. At this time, these systems are awakened normally.

[0120] Another possible mode is abnormal awakening. After the vehicle is normally asleep, some control systems may be awakened due to factors such as hardware failure. For example, due to a failure in the voltage regulator, the engine control unit may repeatedly try to start the engine for self-repair when it detects an abnormal voltage value in a sensor. For example, due to aging or burning of the transistor, the anti-theft system mistakenly determines that the vehicle is at risk of illegal intrusion, thereby activating the anti-theft mode, causing the anti-theft indicator light to suddenly light up. At this time, these systems are awakened abnormally.

[0121] In the embodiment of the present application, based on the network management message of each network element in the vehicle, the abnormal awakening network element is located. For the convenience of description, the present application defines three timers in the following embodiments, namely, the first timer, the second timer and the third timer, wherein the first timer can also be described as T sleep The first timer is mainly used to monitor the dormant state of the vehicle network. When the vehicle meets the dormant condition, T sleep Start timing. If any wake-up signal is detected within the set time, T sleep If no wake-up signal is detected within the set time, T sleep After the timeout, the gateway will determine that the vehicle network can enter the bus sleep state to reduce energy consumption. The second timer can also be described as T monitor-in The second timer is mainly used to manage the transition from the normal state to the monitoring state. When the vehicle meets the normal non-sleeping conditions, T monitor-in Will reset if an active signal other than sleep is detected, T monitor-in When the timing starts and times out, the gateway is triggered to enter the monitoring state and prepare to further check the non-sleep status in the network. The third timer can be described as T monitor-out The third timer is mainly responsible for the duration of the monitoring state. In the monitoring state, T monitor-out Start timing at T monitor-out When the timeout occurs, switch to the normal state, or, at T sleep When the timeout occurs, the bus enters the sleep state to maintain network stability and save energy.

[0122] In an embodiment of the present application, an abnormal wake-up message and an abnormal non-sleep message are described. Both of these messages are determined based on the analysis of the network management message. The embodiment of the present application also describes a monitoring message that encapsulates the abnormal related information in the abnormal wake-up message as a first monitoring message, and describes a monitoring message that encapsulates the abnormal related information in the abnormal non-sleep message as a second monitoring message.

[0123] The following describes the technical solution of the vehicle dormancy control method applied for by taking several specific embodiments as examples:

[0124] Figure 1 A flowchart of a vehicle dormancy control method provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the process of the method of this embodiment is as follows:

[0125] S11: When the vehicle is in a network dormant state, monitoring abnormal wake-up messages sent by network elements in the vehicle network.

[0126] Among them, the possible implementation methods of the vehicle entering the bus dormant state include the following two:

[0127] A possible implementation is: after the vehicle is powered off, the vehicle is in a normal state. If each network element in the vehicle enters sleep mode normally and stops sending network management messages, the gateway controls the vehicle to switch from the normal state to the bus sleep state.

[0128] Another possible implementation method is: if there is a network element in the vehicle that has not entered sleep mode normally and is still sending network management messages, the vehicle switches from the normal state to the monitoring state. When the non-sleeping network element in the vehicle enters sleep mode, the gateway controls the vehicle to switch from the monitoring state to the bus sleep state.

[0129] Among them, the network elements are all electronic control units in the vehicle. Each network element in the vehicle that is connected to normal power will send its own network management message to the gateway to inform the gateway of its current status or request specific operations. For example, the body control module sends its own network management message to inform the gateway whether it is in a normal sleep state, an abnormal non-sleep state, a normal working state, or awakened by an abnormal request. If the network element is awakened abnormally, the abnormal wake-up message is sent to the gateway. The gateway determines the situation of the network element that sent the abnormal wake-up message by receiving and parsing the abnormal wake-up message.

[0130] S12: When the abnormal wake-up message is detected, based on the abnormal wake-up message, locate the first network element that abnormally wakes up the vehicle network.

[0131] Optionally, the abnormal wake-up message includes: a first network element identifier; based on the first network element identifier in the abnormal wake-up message, determining that the network element corresponding to the first network element identifier is the first network element that abnormally wakes up the vehicle network.

[0132] Optionally, the abnormal wake-up message also includes: an abnormal wake-up identifier and / or an abnormal wake-up reason, wherein the abnormal wake-up identifier is used to indicate that the message it contains is an abnormal wake-up message, and the abnormal wake-up reason is used to indicate the reason why the first network element abnormally wakes up the vehicle network.

[0133] Among them, the first network element identifier is the identification information of the network element that sends the abnormal wake-up message. The gateway determines the abnormal wake-up message by parsing the abnormal wake-up identifier, locates the network element that abnormally wakes up the vehicle network by parsing the identification information of the sending network element in the abnormal wake-up message, and determines it to be the first network element. The reason why the first network element abnormally wakes up the vehicle is obtained by parsing the abnormal wake-up reason.

[0134] In this embodiment, when the vehicle is in a network dormant state, the abnormal wake-up message sent by the network element in the vehicle network is monitored; when the abnormal wake-up message is detected, the first network element that abnormally wakes up the vehicle network is located based on the abnormal wake-up message. That is, after the vehicle enters the network dormant state, the gateway keeps the function of monitoring the abnormal wake-up message turned on, and continuously monitors the abnormal wake-up message in the network, so that the abnormal wake-up network element can be located based on the abnormal wake-up message obtained by monitoring, thereby realizing the location of the abnormal wake-up network element.

[0135] In the above embodiment, the in-vehicle network element, whether in a normal state or an abnormal state, must send its own network management message when requesting the network. Table 1 shows the payload format of the network management message.

[0136] Table 1 Network management message payload format

[0137]

[0138] As shown in Table 1, the network management message payload format includes: sending node, identifier (ID), sending type, data length and data field. The sending node, that is, the node that sends the network management message, is all controllers connected to the power supply, such as the telematics system, the body control module and the vehicle positioning system. The ID is used to identify the type and purpose of the network management message. The network management message generally has a unified base address. The ID of the network management message is generally defined as the base address + the node source address (Source Node The base address is used to identify the type of message, and the source address is used to identify the node sending the message. For example, if the base address is 0x18FF0000 and the source address is 0x01, the ID of the network management message is 0x18FF0001. The sending type refers to the transmission mode of the message and the expected response type, including periodic sending and event-driven sending. Here, it is periodic sending, which means that the sleep state information of the node is periodically sent at a fixed time interval. The data length refers to the number of bytes in the data field of the message, and n means that the data field has n bytes (Byte). The data field is the payload / actual data of the network management message, that is, Byte 0 to Byte n as shown in Table 1. Byte is a set of bits (Bits), usually containing 8 bits, used to store and represent information such as characters, numbers, and instructions. In the data field, each node is assigned a unique node source address stored in Byte 0. Byte 1 is the control bit vector (Control Bit Vector, CBV), and the specific content is shown in Table 2. Byte 2 is the wakeup reason (Wakeup Reason) defines all the wake-up conditions of the controller. All active and passive wake-ups of the nodes are represented by different enumeration values. Byte 3 to Byte n are used to carry additional information such as node status and network load.

[0139] Table 2 Control Bit Vector signal definition

[0140]

[0141] As shown in Table 2, the CBV size is 8 bits, where Bit 0 is a Repeat Message Request bit. When set to 1, it indicates that the current node requests all nodes to enter the Repeat Message state to ensure the synchronization of the network state. When set to 0, it indicates that the current node does not require other nodes to enter the Repeat Message state, which means that the node is already in the normal operation state of network communication, or is preparing to enter the sleep state, and believes that the current network state has been synchronized, or no longer requires synchronization operation; Bit 3 is the Master Coordinator Sleep Ready bit. When set to 1, it indicates that the master coordinator node requests synchronous sleep. When set to 0, it indicates that the master coordinator node does not request to start synchronous sleep; Bit 4 is an Active Wakeup Bit, which is used to indicate whether the node actively wakes up the network or passively wakes up the network. When set to 1, it indicates that the node actively wakes up the network, and when set to 0, it indicates passive wakeup; Bit 6 is a Partial Network Information Bit (PNII). PNI Bit is used to indicate that some networks are requested to wake up or remain active while other networks remain dormant. This can reduce unnecessary communication, reduce bus load, and thus reduce energy consumption. PNI Bit is set to 1 to indicate that the network management message contains request information for a partial network (Partial Network Cluster, PNC). It is set to 0 to indicate that the current network management message does not contain specific requests or instructions for any partial network. Bit 1, Bit 2, Bit 5, and Bit 7 are reserved bits (Reserved, Res) for future expansion and are all set to 0.

[0142] Among them, as shown in Table 1 and Table 2, the abnormal wake-up identifier is the 4th bit Active Wakeup Bit in the CBV of the network management message shown in Table 2 is set to 1, indicating that the node actively wakes up the network, the first network element identifier is the node source address of the sending network element of the abnormal wake-up message, that is, the Source NodeIdentifier in Byte 0 of the network management message shown in Table 1, and the abnormal wake-up reason is the Wakeup Reason in Byte 2 of the network management message shown in Table 1. The Wakeup Reason uses different enumeration values ​​to identify the specific reason that causes the sending network element to wake up from the sleep or low power mode. The sending network element may be awakened for one reason or for multiple reasons. The wake-up reason may include but is not limited to the following situations:

[0143] One possible situation is that the GPS signal is abnormal. Assume that the corresponding enumeration value is 0x01. For example, electromagnetic interference near the vehicle affects the GPS signal. When the vehicle does not move, the GPS module is awakened and reports the change in the vehicle's position.

[0144] Another possible situation is the timer interrupt. Assuming that its corresponding enumeration value is 0x02, for example, the engine control unit sets a timer with a preset time. When the timer reaches the preset time and performs tasks such as data collection, the engine control unit is awakened and starts to collect and process information such as engine temperature and pressure.

[0145] Another possible situation is the door opening and remote control key signal. Assume that the corresponding enumeration value is 0x30, including the door opening 0x10 and the remote control key signal 0x20. For example, the user presses the unlock door button on the remote control key while opening the door. The door control module is awakened to detect the status of the door and send a command to unlock the door.

[0146] Figure 2 A flow chart of another method for controlling vehicle dormancy provided in an embodiment of the present application, Figure 2 is Figure 1 On the basis of

[0147] S21: When the vehicle is in a network monitoring state, monitoring abnormal non-sleep messages sent by network elements in the vehicle network.

[0148] Optionally, when the vehicle meets the conditions for entering the network monitoring state, the vehicle switches from the normal network state to the network monitoring state.

[0149] Among them, a possible implementation method for the vehicle to enter the network monitoring state is: after the vehicle is powered off, the vehicle is in a normal state. If there is a network element in the vehicle that has not entered sleep mode normally, the gateway controls the vehicle to switch from the normal network state to the network monitoring state.

[0150] If the network element does not enter sleep mode normally, that is, does not enter sleep mode abnormally, the abnormal non-sleep message is sent to the gateway, and the gateway determines the situation of the network element sending the abnormal non-sleep message by receiving and parsing the abnormal non-sleep message.

[0151] S22: Based on the abnormal non-sleep message, locate the second network element that causes the vehicle network to be abnormally non-sleep.

[0152] Optionally, the abnormal non-sleep message includes a second network element identifier, which is the identifier of the network element that sends the abnormal non-sleep message; based on the second network element identifier in the abnormal non-sleep message, it is determined that the network element corresponding to the second network element identifier is the second network element that causes the vehicle network to be abnormally non-sleep.

[0153] Optionally, the abnormal non-sleep message also includes: an abnormal non-sleep identifier and / or an abnormal non-sleep reason, the abnormal non-sleep identifier is used to indicate that the message it contains is an abnormal non-sleep message, and the abnormal non-sleep reason is used to indicate the reason why the second network element is abnormally non-sleep.

[0154] Among them, the gateway specifically determines the abnormal non-sleep message by parsing the abnormal non-sleep identifier, locates the network element that causes the abnormal non-sleep of the vehicle network by parsing the identification information of the network element sending in the abnormal non-sleep message, and determines it to be the second network element, and obtains the reason for the abnormal non-sleep of the second network element by parsing the non-sleep reason.

[0155] In this embodiment, when the vehicle is in the network monitoring state, the abnormal non-sleep message sent by the network element in the vehicle network is monitored, and based on the abnormal non-sleep message, the second network element causing the abnormal non-sleep of the vehicle network is located. Thus, the location of the abnormal non-sleep network element is achieved, and the cause of the abnormal non-sleep is determined.

[0156] Figure 3 A flow chart of another method for controlling vehicle dormancy provided in an embodiment of the present application, Figure 3 is Figure 2 On the basis of S23 and S24:

[0157] S23: Generate a forced sleep message based on the abnormal non-sleep message.

[0158] Among them, the message payload format of the forced sleep instruction is shown in Table 3.

[0159] Table 3 Forced sleep command message payload format

[0160]

[0161] As shown in Table 3, the payload format of the forced sleep instruction message includes: sending node, ID, sending type, data length and data field, wherein the sending node, that is, the node sending the forced sleep instruction message, is the gateway; ID is an identifier used to identify the type and purpose of the forced sleep instruction message; the sending type here is periodic sending, indicating that the forced sleep instruction is sent periodically at a fixed time interval; the data length refers to the number of bytes in the data field of the forced sleep instruction message, n means that the data field has n bytes; the data field is the payload / actual data of the forced sleep instruction message, that is, Byte 0 to Byte n, in the data field, Byte 0 indicates the network sleep state, which refers to the network sleep state of each abnormal non-sleeping network element; Byte 1 indicates the specified forced sleep instruction; Byte 2 to Byte n-1 are used to carry additional node status and network load information; Byte n is a checksum, which is used to verify the integrity of the data. If all abnormal non-sleep nodes receive a forced sleep command in OFF mode and the checksum is valid, they will set their own WakeupReason to invalid, stop sending abnormal non-sleep messages, and enter sleep until the wake-up condition is met again.

[0162] S24: Send the forced sleep message to the second network element, where the forced sleep message is used to instruct the second network element to stop sending the abnormal non-sleep message.

[0163] Optionally, the forced sleep message is also used to instruct the second network element to invalidate a target wake-up condition of the second network element, where the target wake-up condition at least includes a wake-up condition that causes the vehicle network to abnormally not sleep.

[0164] Among them, the gateway sends a forced sleep command message to the non-sleeping network element, and does not send a forced sleep command message to other already sleeping network elements, so as to avoid waking up the already sleeping network elements again. After the non-sleeping network element receives the strong sleep command message, it sets the Wakeup Reason in its own abnormal non-sleeping message to invalid, stops sending network management messages to the gateway, and the abnormal non-sleeping network element enters the bus sleep state.

[0165] In this embodiment, a forced sleep message is generated based on the abnormal non-sleep message, and the forced sleep message is sent to the second network element, and the forced sleep message is used to instruct the second network element to stop sending the abnormal non-sleep message. Thus, the problem of abnormal non-sleep of the vehicle is solved, thereby saving vehicle electricity.

[0166] Figure 4 A schematic diagram of a vehicle state machine provided in an embodiment of the present application is shown in FIG. Figure 4As shown, the state of the vehicle is controlled by the gateway, including three states: normal state, monitoring state and bus sleep state. After the vehicle is powered off, the jump mechanism of the vehicle state machine is as follows:

[0167] After the vehicle is powered off, the first timer T sleep and the second timer T monitor-in Start timing, at this time the gateway determines that the vehicle is in a normal state. In the normal state, when the vehicle meets the normal non-sleep condition, the second timer T monitor-in Reset, when the vehicle is abnormally not in sleep mode, the second timer T monitor-in Start timing, the second timer T monitor-in After the timeout, the second timer T is terminated monitor-in And start the third timer T monitor-out , at this time, the gateway controls the vehicle to switch from the normal state to the monitoring state; when the gateway receives any message, that is, when the vehicle is not in sleep mode or abnormally not in sleep mode, the first timer T sleep Reset, when the vehicle is in normal sleep mode, the first timer T sleep Start timing, since the first timer T sleep The preset time is less than the second timer T monitor-in The preset time of the first timer T sleep After the first timeout, terminate the second timer T monitor-in , at this time, the gateway controls the vehicle to switch from the normal state to the bus dormant state. In the monitoring state, the third timer T monitor-out The timing continues. When the vehicle meets the normal non-sleeping working condition, the third timer T is terminated. monitor-out And start the second timer T monitor-in , at this time, the gateway controls the vehicle to switch from the monitoring state to the normal state; when the third timer T monitor-out After timeout, terminate the timer T monitor-out And start the timer T monitor-in , the gateway sends a second monitoring message and a forced sleep command. At this time, the gateway controls the vehicle to switch from the monitoring state to the normal state. When the gateway receives the abnormal non-sleep message and sends the forced sleep command, it may be in the third timer T monitor-out Before the timeout, the third timer T monitor-out After the timeout; when the vehicle is in normal sleep mode, the first timer T sleep Start timing, since the first timer T sleep The preset time of the third timer T monitor-in The preset time of the first timer T sleep After the first timeout, terminate the third timer T monitor-out, at this time, the gateway controls the vehicle to switch from the monitoring state to the bus sleep state. In the bus sleep state, when the gateway receives or sends any message, that is, when the vehicle is not sleeping normally or wakes up abnormally, the second timer T is started. monitor-in At this time, the gateway controls the vehicle to switch from the bus sleep state to the normal state, wherein when the vehicle wakes up abnormally, the gateway sends a first monitoring message.

[0168] Figure 5 A flowchart of another method for controlling vehicle dormancy provided in an embodiment of the present application is shown below. Figure 5 is Figure 1 Based on the description of a possible implementation method of vehicle state switching before S11, combined with Figure 4 ,like Figure 5 As shown, the process of the method of this embodiment is as follows:

[0169] S5 1: When the vehicle meets the network sleep condition, the vehicle switches from the network normal state to the network sleep state; or, when the vehicle meets the network sleep condition, the vehicle switches from the network monitoring state to the network sleep state.

[0170] Optionally, when the vehicle is in the normal network state or the network monitoring state, when a preset first timer times out, the vehicle meets the bus sleep condition; wherein, the first timer is configured to start after the vehicle is powered off, and reset when any message of the vehicle network is monitored.

[0171] Among them, Figure 4 As shown, the first timer is T sleep After the vehicle is powered off, the first timer T sleep When the gateway receives any message, the first timer T sleep Reset, that is, when the vehicle is not in sleep mode normally or abnormally, the first timer T sleep When the vehicle is not dormant, the gateway receives the network management message sent by the network element that is working normally. When the vehicle is not dormant, the gateway receives the network management message sent by the network element that is not dormant abnormally. When the gateway does not receive any message, the first timer T sleep Continuous timing and timeout means that the vehicle meets the bus sleep conditions. The gateway controls the vehicle to enter the bus sleep state to monitor abnormal vehicle wake-up.

[0172] In this embodiment, when the vehicle meets the network sleep condition, the vehicle switches from the network normal state to the network sleep state; or when the vehicle meets the network sleep condition, the vehicle switches from the network monitoring state to the network sleep state. Thus, the conditions for the vehicle to switch to the bus sleep state are known, and the accuracy of abnormal vehicle wake-up monitoring is improved.

[0173] Figure 6 A flowchart of another method for controlling vehicle dormancy provided in an embodiment of the present application is shown below. Figure 6 is Figure 2 Based on the description of a possible implementation method of vehicle state switching before S21, combined with Figure 4 ,like Figure 6 As shown, the process of the method of this embodiment is as follows:

[0174] S61: When the vehicle meets the conditions for entering the network monitoring state, the vehicle switches from the normal network state to the network monitoring state.

[0175] Optionally, when the vehicle is in the normal network state, when a preset second timer times out, the vehicle meets the conditions for entering the network monitoring state; wherein, the second timer is configured to start after the vehicle is powered off, and reset when a normal non-sleeping message of the vehicle network is monitored.

[0176] Among them, Figure 4 As shown, the second timer is T monitor-in After the vehicle is powered off, all network elements in the vehicle should enter sleep mode normally. At this time, the vehicle is in a normal state. If there are network elements in the vehicle that have not entered sleep mode normally, they will send an abnormal non-sleep message to the gateway. The first timer T sleep Constantly reset, the second timer T monitor-in Continuous timing, the second timer T monitor-in After the timeout, the vehicle meets the conditions for entering the network monitoring state, and the second timer T is terminated. monitor-in , start the third timer T monitor-out At this time, the gateway controls the vehicle to switch from the normal network state to the network monitoring state.

[0177] In this embodiment, when the vehicle meets the conditions for entering the network monitoring state, the vehicle switches from the normal network state to the network monitoring state. Thus, the conditions for the vehicle to switch to the network monitoring state are known, and the accuracy of the abnormal non-sleep monitoring of the vehicle is improved.

[0178] In the above embodiment, optionally, the second timer is further configured to terminate when the first timer times out, wherein the timing duration of the first timer is shorter than the timing duration of the second timer.

[0179] Among them, Figure 4 As shown in the figure, when all network elements in the vehicle stop sending network management messages and enter normal sleep mode, the first timer T sleep and the second timer T monitor-in The first timer T sleep The timing duration is shorter than the second timer T monitor-in Therefore, the first timer T sleep Than the second timer T monitor-in Timeout first, the first timer T sleep When the timeout occurs, the second timer T is terminated. monitor-in At this time, the gateway controls the vehicle to switch from the normal network state to the bus sleep state.

[0180] Optionally, the second timer is further configured to start after the abnormal wake-up message is detected.

[0181] Among them, Figure 4 As shown, after the vehicle is in the bus sleep state and detects abnormal awakening, the gateway detects the abnormal awakening message sent by the first network element, and the second timer T monitor-in The timing starts, and the gateway controls the vehicle to switch from bus sleep state to network normal state.

[0182] Optionally, the second timer is also configured to terminate after timeout.

[0183] Figure 7 A flowchart of another method for controlling vehicle dormancy provided in an embodiment of the present application is shown below. Figure 7 is Figure 2 Based on the description of a possible implementation method of the vehicle state switching after S22, such as Figure 7 As shown, the process of the method of this embodiment is as follows:

[0184] S71: When the vehicle meets a preset normal non-sleeping condition, the vehicle enters a network normal state from a network monitoring state.

[0185] Optionally, when the vehicle is in the network monitoring state, when a preset third timer times out, the vehicle meets the normal non-sleep condition; wherein the third timer is configured to start after the second timer times out.

[0186] Optionally, when the vehicle is in the network monitoring state, when a normal non-sleep message is monitored, the vehicle meets the normal non-sleep condition.

[0187] Optionally, the third timer is also configured to terminate after detecting the normal non-sleeping message when the vehicle is in the network monitoring state.

[0188] Optionally, the second timer is also configured to start after detecting the normal non-sleeping message when the vehicle is in the network monitoring state.

[0189] Optionally, the second timer is configured to start after the third timer times out.

[0190] Among them, specifically, Figure 4 As shown, when the vehicle is in the monitoring state and the monitoring vehicle is abnormal and not dormant, the third timer T monitor-out During the continuous timing, if the gateway receives the entire non-sleep message sent by the normal non-sleep network element, the normal non-sleep condition is met, and the third timer T is terminated. monitor-out , the second timer T monitor-in The timing starts, and the gateway controls the vehicle from the monitoring state to the normal state.

[0191] In this embodiment, when the vehicle meets the preset normal non-sleeping condition, the vehicle enters the network normal state from the network monitoring state, thereby further improving the integrity of the vehicle abnormal non-sleeping monitoring process.

[0192] In the above embodiment, optionally, the third timer is further configured to terminate when the first timer times out, and the timing duration of the first timer is shorter than the timing duration of the third timer.

[0193] Among them, Figure 4 As shown, when the vehicle is in the monitoring state, when the abnormal non-sleeping network element stops sending network management messages to the gateway, that is, the vehicle is normally asleep again, the first timer T sleep Start timing, since the first timer T sleep The timing duration is less than the third timer T monitor-out Therefore, the first timer T sleep Than the third timer T monitor-out Timeout first, the first timer T sleep After the timeout, the third timer T is terminated. monitor-out At this time, the gateway controls the vehicle to switch from the network monitoring state to the bus sleep state.

[0194] Figure 8 A flowchart of another method for controlling vehicle dormancy provided in an embodiment of the present application is shown below. Figure 8 is Figure 1 In addition, S13 and S14 are included:

[0195] S124: Generate a first monitoring message based on the abnormal wake-up message.

[0196] Optionally, the exception related information in the exception wake-up message is encapsulated into the first monitoring message, wherein the exception related information includes a first network element identifier, and the first network element identifier is an identifier of a network element that sends the exception wake-up message.

[0197] Optionally, the exception-related information also includes: an abnormal wake-up flag and / or an abnormal wake-up reason, the abnormal wake-up flag is used to indicate that the message it contains is an abnormal wake-up message, and the abnormal wake-up reason is used to indicate the reason why the first network element abnormally wakes up the vehicle network.

[0198] Optionally, if at least two abnormal wake-up messages are monitored, the first abnormality related information in the at least two abnormal wake-up messages are sequentially encapsulated into the first monitoring message.

[0199] Among them, as shown in Table 1, the abnormal related information in the abnormal wake-up message is the information in Byte 0, Byte 1 and Byte 2 in the network management message sent by the abnormal wake-up network element, the first network element identifier is the Source Node Identifier of the abnormal wake-up network element in Byte 0, the abnormal wake-up identification information is the Active Wakeup Bit set to 1 in the Control Bit Vector of the abnormal wake-up network element in Byte 1, and the abnormal wake-up reason is the Wakeup Reason of the abnormal wake-up network element in Byte 2. The gateway puts Byte 0, Byte 1, and Byte 2 of the abnormal wake-up message into Byte 0, Byte 1, and Byte 2 of the first monitoring message. If there are two abnormal wake-up messages, Byte 0, Byte 1, and Byte 2 of the two abnormal wake-up messages are put into the first monitoring message in sequence, that is, Byte 0, Byte 1, and Byte 2 of the first abnormal wake-up message are put into Byte 0, Byte 1, and Byte 2 of the first monitoring message, and Byte 0, Byte 1, and Byte 2 of the second abnormal wake-up message are put into Byte 3, Byte 4, and Byte 5 of the first monitoring message, and so on. Table 4 is the payload format of the first monitoring message.

[0200] Table 4 First monitoring message payload format

[0201]

[0202]

[0203] As shown in Table 4, the first monitoring message payload format includes: sending node, ID, sending type, data length and data field, wherein the sending node, that is, the node sending the first monitoring message, is a gateway; ID is an identifier used to identify the type and purpose of the first monitoring message; the sending type here is event-driven sending, indicating that it may contain a network abnormal wake-up event flag. When a network abnormal wake-up is detected, the first monitoring message contains the location and cause of the abnormal wake-up event; the data length refers to the number of bytes of the data field of the first monitoring message, and n means that the data field has n bytes; the data field is the payload / actual data of the first monitoring message, that is, Byte 0 to Byte n, which is used to store the node source address, control bit vector and wake-up cause of the detected abnormal wake-up message, and the remaining bytes are used to carry additional node status and network load information.

[0204] S14: Sending the first monitoring message to a cloud server, or sending the first monitoring message to a communication device of the vehicle, so that the communication device sends the first monitoring message to the cloud server.

[0205] The communication device of the vehicle is a T-box terminal, and the cloud server receives the first monitoring message in the following two ways:

[0206] One possible way is: after the gateway generates the first monitoring message, it sends the first monitoring message to the cloud server.

[0207] Another possible manner is: after the gateway generates the first monitoring message, it sends the first monitoring message to the T-box terminal, and the T-box terminal then uploads the first monitoring message to the cloud server.

[0208] Among them, the cloud server performs signal analysis on the first monitoring message and sends the monitoring result of abnormal vehicle awakening to the host manufacturer or the user, and the host manufacturer and the user take countermeasures to the abnormal vehicle awakening.

[0209] Specifically, the first monitoring message sent by the gateway is binary digital information. The cloud server parses the binary digital information into understandable text information to inform the host manufacturer and the user of the location and reason of the abnormal awakening network element, and the network element with Bit 4 in the Control Bit Vector of the abnormal awakening network element recorded in the first monitoring message set to 1 is determined as the source of the abnormal awakening, the corresponding Source Node Identifier is determined as the node source address of the abnormal awakening network element, and the corresponding Wakeup Reason is determined as the reason for the abnormal awakening.

[0210] In this embodiment, the gateway generates a first monitoring message based on the abnormal awakening message, and the gateway sends the first monitoring message to the cloud server through the terminal, thereby locating the abnormal awakening network element and obtaining the abnormal awakening cause.

[0211] Fig. 9 A flowchart of another method for controlling vehicle dormancy provided in an embodiment of the present application is shown below. Fig. 9 is Figure 2 On the basis of S25 and S26:

[0212] S25: The gateway generates a second monitoring message based on the abnormal non-sleep message.

[0213] Optionally, the exception related information in the abnormal non-sleep message is encapsulated into the second monitoring message, wherein the exception related information includes a second network element identifier, and the second network element identifier is an identifier of a network element that sends the abnormal non-sleep message.

[0214] Optionally, the abnormality-related information also includes: an abnormal non-sleep flag and / or an abnormal non-sleep reason, wherein the abnormal non-sleep flag is used to indicate that the message it contains is an abnormal non-sleep message, and the abnormal non-sleep reason is used to indicate the reason why the second network element is abnormally non-sleep.

[0215] Optionally, if at least two abnormal non-sleep messages are monitored, the second abnormality related information in the at least two abnormal non-sleep messages is sequentially encapsulated into the second monitoring message.

[0216] Among them, as shown in Table 1, the abnormal related information in the abnormal non-sleep message is the information in Byte 0, Byte 1 and Byte 2 in the abnormal non-sleep network management message, the identification information of the sending network element is the Source Node Identifier of the abnormal non-sleep network element in Byte 0, the abnormal wake-up identification information is the Active Wakeup Bit set to 1 in the Control Bit Vector of the abnormal non-sleep network element in Byte 1, and the wake-up reason is the Wakeup Reason of the abnormal non-sleep network element in Byte 2. The gateway puts Byte 0, Byte 1, and Byte 2 of the abnormal non-sleep message into Byte 0, Byte 1, and Byte 2 of the second monitoring message. If there are two abnormal non-sleep messages, Byte 0, Byte 1, and Byte 2 of the two abnormal non-sleep messages are put into the second monitoring message in sequence, that is, Byte 0, Byte 1, and Byte 2 of the first abnormal non-sleep message are put into Byte 0, Byte 1, and Byte 2 of the second monitoring message, and Byte 0, Byte 1, and Byte 2 of the second abnormal non-sleep wake-up message are put into Byte 3, Byte 4, and Byte 5 of the second monitoring message, and so on. Table 5 is the payload format of the second monitoring message.

[0217] Table 5 Second monitoring message payload format

[0218]

[0219]

[0220] As shown in Table 5, the payload format of the second monitoring message includes: sending node, ID, sending type, data length and data field, wherein the sending node, that is, the node sending the first monitoring message, is the gateway; ID is an identifier used to identify the type and purpose of the second monitoring message; the sending type here is event-driven sending, indicating that it may contain a network abnormal non-sleep event flag. When the network abnormal non-sleep is detected, the second monitoring message contains the location and cause of the abnormal non-sleep event; the data length refers to the number of bytes of the data field of the second monitoring message, and n means that the data field has n bytes; the data field is the payload / actual data of the second monitoring message, that is, Byte 0 to Byte n, which is used to store the node source address, control bit vector and wake-up reason of the detected abnormal non-sleep message, and the remaining bytes are used to carry additional node status and network load information.

[0221] Optionally, in the above embodiment, the execution order of S25 and S22 is not limited, and they can be executed successively or simultaneously.

[0222] S26: The gateway sends the second monitoring message to the cloud server.

[0223] The second monitoring message is sent to the cloud server, or the second monitoring message is sent to the communication device of the vehicle, so that the communication device sends the second monitoring message to the cloud server.

[0224] The communication device of the vehicle is a T-box terminal, and the cloud server receives the second monitoring message in the following two ways:

[0225] One possible way is: after the gateway generates the first monitoring message, it sends the first monitoring message to the cloud server.

[0226] Another possible manner is: after the gateway generates the first monitoring message, it sends the first monitoring message to the T-box terminal, and the T-box terminal then uploads the first monitoring message to the cloud server.

[0227] Among them, after the cloud server performs signal analysis on the second monitoring message, it sends the monitoring result of the abnormal non-sleeping of the vehicle to the host manufacturer or the user, and the host manufacturer and the user take countermeasures to the abnormal non-sleeping of the vehicle.

[0228] Specifically, the second monitoring message sent by the gateway is binary digital information. The cloud server parses the binary digital information into understandable text information to inform the host manufacturer and the user of the location and reason of the abnormal non-sleeping network element. The network element with Bit 4 in the Control Bit Vector of the abnormal non-sleeping network element recorded in the second monitoring message set to 1 is determined as the source of the abnormal non-sleeping, the corresponding Source Node Identifier is determined as the node source address of the abnormal non-sleeping network element, and the corresponding Wakeup Reason is determined as the reason for the abnormal non-sleeping.

[0229] In this embodiment, the gateway generates a second monitoring message based on the abnormal non-sleeping message, and the gateway sends the second monitoring message to the cloud server through the terminal, thereby locating the abnormal non-sleeping network element and obtaining the abnormal non-sleeping reason.

[0230] Fig.10 A schematic diagram of the structure of a sleep control device for a vehicle provided in an embodiment of the present application is shown in FIG. Fig.10 As shown, the second aspect of the embodiment of the present application provides a vehicle dormancy control device, the device comprising: a monitoring module 1001 and a processing module 1002, wherein:

[0231] A monitoring module 1001, configured to monitor abnormal wake-up messages sent by network elements in the vehicle network when the vehicle is in a network dormant state;

[0232] The processing module 1002 is used to locate the first network element that abnormally wakes up the vehicle network based on the abnormal wake-up message when the abnormal wake-up message is monitored.

[0233] Optionally, the abnormal awakening message includes: a first network element identifier, where the first network element identifier is an identifier of a network element that sends the abnormal awakening message;

[0234] The processing module 1002 is specifically configured to determine, based on the first network element identifier in the abnormal awakening message, that the network element corresponding to the first network element identifier is the first network element that abnormally awakens the vehicle network.

[0235] Optionally, the abnormal wake-up message also includes: an abnormal wake-up identifier and / or an abnormal wake-up reason, wherein the abnormal wake-up identifier is used to indicate that the message it contains is an abnormal wake-up message, and the abnormal wake-up reason is used to indicate the reason why the first network element abnormally wakes up the vehicle network.

[0236] Optionally, when the abnormal wake-up message is detected, the vehicle switches from a network sleep state to a network normal state.

[0237] Optionally, the monitoring module 1001 is further used to monitor abnormal non-sleep messages sent by network elements in the vehicle network when the vehicle is in a network monitoring state;

[0238] The processing module 1002 is further configured to locate a second network element that causes the vehicle network to abnormally not sleep based on the abnormal non-sleep message.

[0239] Optionally, the abnormal non-sleep message includes a second network element identifier, where the second network element identifier is an identifier of a network element that sends the abnormal non-sleep message;

[0240] The processing module 1002 is specifically configured to determine, based on the second network element identifier in the abnormal non-sleep message, that the network element corresponding to the second network element identifier is the second network element that causes the vehicle network to be abnormally non-sleep.

[0241] Optionally, the abnormal non-sleep message also includes: an abnormal non-sleep identifier and / or an abnormal non-sleep reason, the abnormal non-sleep identifier is used to indicate that the message it contains is an abnormal non-sleep message, and the abnormal non-sleep reason is used to indicate the reason why the second network element is abnormally non-sleep.

[0242] Optionally, the processing module 1002 is further configured to generate a forced sleep message based on the abnormal non-sleep message;

[0243] The sending module 1003 is used to send the forced sleep message to the second network element, and the forced sleep message is used to instruct the second network element to stop sending the abnormal non-sleep message.

[0244] Optionally, the forced sleep message is also used to instruct the second network element to invalidate a target wake-up condition of the second network element, where the target wake-up condition at least includes a wake-up condition that causes the vehicle network to abnormally not sleep.

[0245] Optionally, when the vehicle meets the network sleep condition, the vehicle switches from the normal network state to the network sleep state; or, when the vehicle meets the network sleep condition, the vehicle switches from the network monitoring state to the network sleep state.

[0246] Optionally, when the vehicle meets the conditions for entering the network monitoring state, the vehicle switches from the normal network state to the network monitoring state.

[0247] Optionally, when the vehicle is in the normal network state or the network monitoring state, when a preset first timer times out, the vehicle meets the bus sleep condition; wherein, the first timer is configured to start after the vehicle is powered off, and reset when any message of the vehicle network is monitored.

[0248] Optionally, when the vehicle is in the normal network state, when a preset second timer times out, the vehicle meets the conditions for entering the network monitoring state; wherein, the second timer is configured to start after the vehicle is powered off, and reset when a normal non-sleeping message of the vehicle network is monitored.

[0249] Optionally, the second timer is also configured to terminate when the first timer times out, wherein the timing duration of the first timer is shorter than the timing duration of the second timer.

[0250] Optionally, the second timer is further configured to start after the abnormal wake-up message is detected.

[0251] Optionally, the second timer is also configured to terminate after timeout.

[0252] Optionally, when the vehicle meets a preset normal non-sleep condition, the vehicle enters a network normal state from a network monitoring state.

[0253] Optionally, when the vehicle is in the network monitoring state, when a preset third timer times out, the vehicle meets the normal non-sleep condition; wherein the third timer is configured to start after the second timer times out.

[0254] Optionally, the third timer is further configured to terminate when the first timer times out, and the timing duration of the first timer is shorter than the timing duration of the third timer.

[0255] Optionally, when the vehicle is in the network monitoring state, when a normal non-sleep message is monitored, the vehicle meets the normal non-sleep condition.

[0256] Optionally, the third timer is also configured to terminate after detecting the normal non-sleeping message when the vehicle is in the network monitoring state.

[0257] Optionally, the second timer is also configured to start after detecting the normal non-sleeping message when the vehicle is in the network monitoring state.

[0258] Optionally, the second timer is configured to start after the third timer times out.

[0259] Optionally, the third timer is also configured to terminate after timing out.

[0260] Optionally, the processing module 1002 is further configured to generate a first monitoring message based on the abnormal wake-up message;

[0261] The sending module 1003 is further used to send the first monitoring message to the cloud server, or to send the first monitoring message to the communication device of the vehicle, so that the communication device sends the first monitoring message to the cloud server.

[0262] Optionally, the processing module 1002 is specifically used to encapsulate the first exception related information in the abnormal wake-up message into a first monitoring message, wherein the first exception related information includes a first network element identifier, and the first network element identifier is an identifier of the network element that sends the abnormal wake-up message.

[0263] Optionally, the first exception-related information also includes: an abnormal wake-up flag and / or an abnormal wake-up reason, the abnormal wake-up flag is used to indicate that the message it contains is an abnormal wake-up message, and the abnormal wake-up reason is used to indicate the reason why the first network element abnormally wakes up the vehicle network.

[0264] Optionally, the processing module 1002 is specifically configured to sequentially encapsulate the first exception related information in the at least two exception wake-up messages into the first monitoring message.

[0265] Optionally, the processing module 1002 is further configured to generate a second monitoring message based on the abnormal non-sleep message;

[0266] The sending module 1003 is further used to send the second monitoring message to the cloud server, or to send the second monitoring message to the communication device of the vehicle, so that the communication device sends the second monitoring message to the cloud server.

[0267] Optionally, the processing module 1002 is specifically used to encapsulate the second exception related information in the abnormal non-sleep message into the second monitoring message, wherein the second exception related information includes a second network element identifier, and the second network element identifier is the identifier of the network element that sends the abnormal non-sleep message.

[0268] Optionally, the second abnormality related information also includes: an abnormal non-sleep flag and / or an abnormal non-sleep reason, the abnormal non-sleep flag is used to indicate that the message it contains is an abnormal non-sleep message, and the abnormal non-sleep reason is used to indicate the reason why the second network element is abnormally non-sleep.

[0269] Optionally, the processing module 1002 is specifically configured to sequentially encapsulate the second abnormality related information in the at least two abnormal non-sleep messages into the second monitoring message.

[0270] The device of this embodiment can be used to execute the solutions of the above-mentioned method embodiments. Its implementation principles and technical effects are similar and will not be repeated here.

[0271] An embodiment of the present application also provides an electronic device, including: a processor, the processor is used to connect to a memory, the memory stores a computer program / instructions that can be run on the processor, and when the computer program / instructions are executed by the processor, the steps of the vehicle sleep control method as described above are implemented.

[0272] An embodiment of the present application further provides a network device, which includes the electronic device as described above, wherein the network device may be a gateway, a switch, a router, or the like.

[0273] An embodiment of the present application further provides an electronic and electrical architecture, which includes the electronic device as described above, or the network device as described above.

[0274] An embodiment of the present application also provides a vehicle, comprising the electronic device as described above, or the network device as described above, or the electronic and electrical architecture as described above.

[0275] An embodiment of the present application provides a computer-readable storage medium, on which a computer program / instruction is stored. When the computer program / instruction is executed by a processor, the steps of the vehicle dormancy control method as described in any one of the above items are implemented.

[0276] The embodiment of the present application provides a computer program product, including a computer program / instruction, characterized in that when the computer program / instruction is executed by a processor, the steps of the vehicle dormancy control method as described in any one of the above items are implemented.

[0277] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0278] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0279] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims

1. A vehicle dormancy control method, characterized in that: The method comprises: When the vehicle is in a network dormant state, monitoring abnormal wake-up messages sent by network elements in the vehicle network; When the abnormal wake-up message is detected, the first network element of the vehicle network that abnormally wakes up is located based on the abnormal wake-up message.

2. The method according to claim 1, characterized in that The abnormal awakening message includes: a first network element identifier, where the first network element identifier is an identifier of a network element that sends the abnormal awakening message; The locating, based on the abnormal wake-up message, the first network element that abnormally wakes up the vehicle network includes: Based on the first network element identifier in the abnormal awakening message, it is determined that the network element corresponding to the first network element identifier is the first network element that abnormally awakens the vehicle network.

3. The method according to claim 2, characterized in that The abnormal wake-up message also includes: an abnormal wake-up identifier and / or an abnormal wake-up reason, wherein the abnormal wake-up identifier is used to indicate that the message it contains is an abnormal wake-up message, and the abnormal wake-up reason is used to indicate the reason why the first network element abnormally wakes up the vehicle network.

4. The method according to claim 1, characterized in that: When the abnormal wake-up message is detected, the vehicle switches from the network dormant state to the network normal state.

5. The method according to claim 1, characterized in that Also includes: When the vehicle is in a network monitoring state, monitoring abnormal non-sleep messages sent by network elements in the vehicle network; Based on the abnormal non-sleep message, a second network element causing the vehicle network to be abnormally non-sleep is located.

6. The method according to claim 5, characterized in that The abnormal non-sleep message includes a second network element identifier, where the second network element identifier is an identifier of a network element that sends the abnormal non-sleep message; The locating the second network element causing the abnormal non-sleep of the vehicle network based on the abnormal non-sleep message includes: Based on the second network element identifier in the abnormal non-sleep message, it is determined that the network element corresponding to the second network element identifier is the second network element that causes the vehicle network to be abnormally non-sleep.

7. The method according to claim 6, characterized in that The abnormal non-sleep message also includes: an abnormal non-sleep identifier and / or an abnormal non-sleep reason, the abnormal non-sleep identifier is used to indicate that the message it contains is an abnormal non-sleep message, and the abnormal non-sleep reason is used to indicate the reason why the second network element is abnormally non-sleep.

8. The method according to any one of claims 5 to 7, characterized in that: Also includes: Based on the abnormal non-sleep message, generating a forced sleep message; The forced sleep message is sent to the second network element, where the forced sleep message is used to instruct the second network element to stop sending the abnormal non-sleep message.

9. The method according to claim 8, characterized in that The forced sleep message is also used to instruct the second network element to invalidate a target wake-up condition of the second network element, where the target wake-up condition at least includes a wake-up condition that causes the vehicle network to abnormally not sleep.

10. The method according to any one of claims 1 to 9, characterized in that When the vehicle meets the network sleep condition, the vehicle switches from the normal network state to the network sleep state; or, when the vehicle meets the network sleep condition, the vehicle switches from the network monitoring state to the network sleep state.

11. The method according to claim 10, characterized in that When the vehicle meets the conditions for entering the network monitoring state, the vehicle switches from the normal network state to the network monitoring state.

12. The method according to claim 11, characterized in that When the vehicle is in the normal network state or the network monitoring state, when a preset first timer times out, the vehicle meets the bus sleep condition; wherein, the first timer is configured to start after the vehicle is powered off, and reset when any message of the vehicle network is monitored.

13. The method according to claim 12, characterized in that When the vehicle is in the normal network state, when a preset second timer times out, the vehicle meets the conditions for entering the network monitoring state; wherein, the second timer is configured to start after the vehicle is powered off, and reset when a normal non-sleeping message of the vehicle network is monitored.

14. The method according to claim 13, characterized in that The second timer is further configured to terminate when the first timer times out, wherein the timing duration of the first timer is shorter than the timing duration of the second timer.

15. The method according to claim 14, characterized in that The second timer is further configured to start after detecting the abnormal wake-up message.

16. The method according to claim 13, characterized in that The second timer is also configured to expire after a timeout.

17. The method according to claim 13, characterized in that When the vehicle meets a preset normal non-sleeping condition, the vehicle enters a network normal state from a network monitoring state.

18. The method according to claim 17, characterized in that When the vehicle is in the network monitoring state, when a preset third timer times out, the vehicle meets the normal non-sleep condition; wherein the third timer is configured to start after the second timer times out.

19. The method according to claim 18, characterized in that The third timer is further configured to terminate when the first timer times out, and the timing duration of the first timer is shorter than the timing duration of the third timer.

20. The method according to any one of claims 17 to 19, characterized in that: When the vehicle is in the network monitoring state, when a normal non-sleep message is monitored, the vehicle meets the normal non-sleep condition.

21. The method according to claim 18 or 19, characterized in that The third timer is also configured to terminate after detecting the normal non-sleeping message when the vehicle is in the network monitoring state.

22. The method according to claim 18 or 19, characterized in that The second timer is also configured to start after detecting the normal non-sleeping message when the vehicle is in the network monitoring state.

23. The method according to claim 22, characterized in that The second timer is configured to start after the third timer expires.

24. The method according to claim 23, characterized in that The third timer is further configured to expire after a timeout.

25. The method according to any one of claims 1 to 4, characterized in that Also includes: Based on the abnormal wake-up message, generate a first monitoring message; The first monitoring message is sent to a cloud server, or the first monitoring message is sent to a communication device of the vehicle, so that the communication device sends the first monitoring message to the cloud server.

26. The method according to claim 25, characterized in that The generating a first monitoring message based on the abnormal wake-up message includes: The first abnormality related information in the abnormal awakening message is encapsulated into a first monitoring message, wherein the first abnormality related information includes a first network element identifier, and the first network element identifier is an identifier of a network element that sends the abnormal awakening message.

27. The method according to claim 26, characterized in that The first abnormality-related information also includes: an abnormal wake-up flag and / or an abnormal wake-up reason, wherein the abnormal wake-up flag is used to indicate that the message in which it is located is an abnormal wake-up message, and the abnormal wake-up reason is used to indicate the reason why the first network element abnormally wakes up the vehicle network.

28. The method according to claim 27, characterized in that If at least two abnormal wake-up messages are monitored, encapsulating the first abnormality related information in the abnormal wake-up message into the first monitoring message includes: The first exception related information in the at least two exception wake-up messages is sequentially encapsulated into the first monitoring message.

29. The method according to any one of claims 5 to 9, characterized in that Also includes: Based on the abnormal non-sleep message, generating a second monitoring message; The second monitoring message is sent to the cloud server, or the second monitoring message is sent to the communication device of the vehicle, so that the communication device sends the second monitoring message to the cloud server.

30. The method according to claim 29, characterized in that The generating a second monitoring message based on the abnormal non-sleep message includes: The second abnormality related information in the abnormal non-sleep message is encapsulated into the second monitoring message, wherein the second abnormality related information includes a second network element identifier, and the second network element identifier is an identifier of a network element that sends the abnormal non-sleep message.

31. The method according to claim 30, characterized in that The second abnormality related information also includes: an abnormal non-sleep flag and / or an abnormal non-sleep reason, the abnormal non-sleep flag is used to indicate that the message it contains is an abnormal non-sleep message, and the abnormal non-sleep reason is used to indicate the reason why the second network element is abnormally non-sleep.

32. The method according to claim 31, characterized in that If at least two abnormal non-sleep messages are monitored, encapsulating the second abnormality related information in the abnormal non-sleep message into the second monitoring message includes: The second abnormality related information in the at least two abnormal non-sleep messages is sequentially encapsulated into the second monitoring message.

33. An electronic device, characterized in that: include: A processor, the processor is used to connect to a memory, the memory stores a computer program / instruction that can be run on the processor, and when the computer program / instruction is executed by the processor, the steps of the vehicle dormancy control method as described in any one of claims 1 to 32 are implemented.

34. A network device, characterized in that: The network device comprises the electronic apparatus as claimed in claim 33.

35. An electronic and electrical architecture, characterized in that: The electronic and electrical architecture includes the electronic device as claimed in claim 33, or the network equipment as claimed in claim 34.

36. A vehicle, characterized in that: Comprising the electronic device as described in claim 33, or the network equipment as described in claim 34, or the electronic and electrical architecture as described in claim 35.

37. A computer-readable storage medium, characterized in that: The readable storage medium stores a computer program / instruction, and when the computer program / instruction is executed by a processor, the steps of the vehicle dormancy control method as described in any one of claims 1 to 32 are implemented.

38. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the vehicle dormancy control method as claimed in any one of claims 1 to 32 are implemented.

Images