Network wakeup method and apparatus, and electronic device and storage medium

Abstract

Provided in the present application are a network wakeup method and apparatus, and an electronic device and a storage medium. The method comprises: acquiring state signals of zone controllers and determining, from among the state signals, a target interaction signal for waking up a domain controller; if the network state of a network where the domain controller is located is a sleeping state, sending a network wakeup request to the domain controller; and if a handshake signal which is fed back by the domain controller in response to the network wakeup request has been received, sending the target interaction signal to the domain controller. In the present application, handshake verification can be flexibly performed on the basis of the actual wakeup condition of a domain controller, thereby avoiding unnecessary time consumption and improving the vehicle use experience; and a handshake determination logic is added for the sending of a target interaction signal, and the function of performing communication handshake with a receiving node is realized by means of the sending of a network wakeup request, thereby ensuring the timeliness and success rate of a handshake process and improving the efficiency of information interaction between different controllers.

Description

Network wake-up method, device, electronic device and storage medium

[0001] This application claims priority to a Chinese patent application filed with the Patent Office of China on January 23, 2024, with application number 202410098156.1, entitled “Network wake-up method, device, electronic device and storage medium”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present application relates to the field of vehicle-mounted network technology, and more specifically, to a network wake-up method, device, electronic device, and storage medium. Background Art

[0003] With the rapid development of science and technology, the use of vehicles in people's daily lives is becoming more and more common. In order to realize more functions of vehicles, the network architecture of the whole vehicle is becoming more and more complex, the number of network communication nodes is increasing, and the network management of the whole vehicle is becoming more and more complex. Network anomalies are increasing, which brings greater challenges to the function realization and energy management of the whole vehicle. At present, the corresponding controllers in the vehicle structure are usually awakened by synchronizing the status between different controllers, so that the vehicle can realize the corresponding functions. However, since different controllers require different initialization times to switch from sleep state to working state, different controllers cannot wake up and sleep at the same time, which in turn causes the time for the vehicle to realize the corresponding functions to become longer and inefficient. Therefore, how to improve the efficiency of information exchange between different controllers has become an urgent problem to be solved.

[0004] Summary of the Invention

[0005] In view of this, embodiments of the present application provide a network wake-up method, device, electronic device, and storage medium to improve the above-mentioned problem.

[0006] According to a first aspect of an embodiment of the present application, a network wake-up method is provided, the method comprising: obtaining a status signal of a regional controller, and determining a target interaction signal for waking up a domain controller from the status signal; if the network status of the network where the domain controller is located is a sleep state, sending a network wake-up request to the domain controller; if a handshake signal is received from the domain controller in response to the network wake-up request, sending the target interaction signal to the domain controller.

[0007] According to a second aspect of an embodiment of the present application, a network wake-up device is provided, comprising: a target interaction signal determination module, configured to obtain a status signal of a regional controller and determine a target interaction signal for waking up a domain controller from the status signal; a first sending module, configured to send a network wake-up request to the domain controller if the network status of the network where the domain controller is located is a dormant state; and a second sending module, configured to send the target interaction signal to the domain controller if a handshake signal fed back by the domain controller in response to the network wake-up request is received.

[0008] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising: a processor; and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the network wake-up method as described above is implemented.

[0009] According to a fourth aspect of the embodiments of the present application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor, the network wake-up method described above is implemented.

[0010] In the solution of the present application, the status signal of the regional controller is first obtained, and the target interaction signal for waking up the domain controller is filtered out from the status signal, and the network status of the network where the domain controller is located is determined. Then, when the network status is dormant, a network wake-up request is sent to the domain controller, so that the domain controller can shake hands with the regional controller based on the network wake-up request, and after receiving the handshake signal fed back by the domain controller based on the network wake-up request, the target interaction signal is sent to the domain controller, so that the domain controller executes the function corresponding to the target interaction signal. The solution of the present application can flexibly perform handshake verification according to the actual wake-up situation of the domain controller, avoid extra time consumption, and improve the car-using experience. A handshake judgment logic is added for the sending of the target interaction signal, and the function of communicating and shaking hands with the receiving node is realized by sending a network wake-up request, ensuring the timeliness and success rate of the handshake process and improving the efficiency of information interaction between different controllers.

[0011] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can derive other drawings based on these drawings without inventive effort.

[0013] FIG1 is a schematic diagram of an architecture of a method for implementing a network wake-up method according to an embodiment of the present application.

[0014] FIG2 is a schematic diagram illustrating interaction of a controller for implementing a network wake-up method according to an embodiment of the present application.

[0015] FIG3 is a flow chart of a method for waking up a network according to an embodiment of the present application.

[0016] FIG4 is a handshake scheme of controller interaction in a network wake-up method according to an embodiment of the present application.

[0017] FIG5 is a diagram illustrating a fixed delay solution for controller interaction in a network wake-up method according to an embodiment of the present application.

[0018] FIG6 is a flow chart of a method for waking up a network according to another embodiment of the present application.

[0019] FIG7 is a schematic flow chart of a method for waking up a network according to another embodiment of the present application.

[0020] FIG8 is a schematic flow chart of a method for waking up a network according to another embodiment of the present application.

[0021] FIG9 is a flow chart of a method for waking up a network according to yet another embodiment of the present application.

[0022] FIG10 is a schematic diagram showing wake-up corresponding to different target interaction signals according to an embodiment of the present application.

[0023] FIG11 is a flow chart of a method for waking up a network according to an embodiment of the present application.

[0024] FIG12 is a block diagram of a network wake-up device according to an embodiment of the present application.

[0025] FIG13 is a hardware structure diagram of an electronic device according to an embodiment of the present application.

[0026] The above-mentioned drawings have shown clear embodiments of the present invention, which will be described in more detail later. These drawings and textual descriptions are not intended to limit the scope of the present invention in any way, but to illustrate the concept of the present invention to computer technicians in this field through specific embodiments. DETAILED DESCRIPTION

[0027] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be thorough and complete and will fully convey the concepts of the example embodiments to those skilled in the art.

[0028] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0029] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner.In the following description, many specific details are provided so as to provide a full understanding of the embodiments of the present application. However, it will be appreciated by those skilled in the art that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, devices, steps etc. can be adopted. In other cases, known methods, devices, implementations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0030] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices. The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily need to be executed in the order described. For example, some operations / steps may be further decomposed, while others may be combined or partially combined, so the actual execution order may vary depending on the actual situation.

[0031] Currently, the mainstream architecture for network wake-up in the automotive industry typically consists of a composite star topology consisting of a domain controller, regional controllers, sensors, and actuators. As shown in Figure 1, the domain controllers are connected to regional controllers A, B, C, and D, respectively. Regional controller A is also connected to sensors and switches to obtain switch signals or sensor status signals when the switches and / or sensors change. Based on the switch signals or sensor status signals, it can send wake-up information to the domain controller, thereby enabling the actuators in regional controller B to execute corresponding functions based on the execution information sent by the domain controller after awakening. However, due to the different initialization times required for different controllers to switch from sleep to active state, and because the wake-up source does not wake up all controllers in the topology simultaneously, when the onboard controllers are awakened by external operations, if the status of the controllers is not synchronized, there will be no response after the control command is issued, resulting in vehicle function failure. As shown in Figure 2, when a change in the state of a switch or sensor is detected, for example, when a switch is pressed, regional controller A is first awakened, waiting for regional controller A to initialize. After initialization is complete, a request is sent on the bus to awaken the domain controller. As shown in Figure 2, regional controller A sends a switch signal to the domain controller so that the domain controller initializes according to regional A_NM. During the initialization process, regional controller A sends a switch signal to the domain controller so that the domain controller wakes up the actuator of the corresponding function after completing initialization and logical judgment. However, due to the introduction of the concept of local network management to reduce energy consumption, each controller can enter a dormant state in advance according to the function setting. Therefore, each time an external wake-up event is triggered, the initialization time of each controller is not completely fixed. This may cause the domain controller to receive a switch signal before initialization is complete, making the corresponding controller unable to perform the corresponding function.

[0032] Please refer to Figure 3, which shows a network wake-up method provided by an embodiment of the present application. In a specific embodiment, the network wake-up method can be applied to the network wake-up device 600 as shown in Figure 12 and the electronic device 700 configured with the network wake-up device 600 (Figure 13). The specific process of this embodiment will be described below. Of course, it can be understood that the method can be executed by a cloud server with computing and processing capabilities. The process shown in Figure 3 will be described in detail below. The network wake-up method can specifically include the following steps:

[0033] Step 110: Acquire a status signal of the regional controller, and determine a target interaction signal for waking up the domain controller from the status signal.

[0034] As one approach, the status signal of the regional controller may be sensor change information obtained by detecting sensors managed by the regional controller, and the status signal determined based on the sensor change information. Alternatively, the regional controller may be monitored in real time, and the status signal of the regional controller may be obtained after a change in the regional controller is determined.

[0035] As a method, in the regional controller, different status signals correspond to different functions, wherein the status signal indicating the linkage of the domain controller is used to wake up the domain controller, and then the domain controller can be woken up according to the status signal used to wake up the domain controller, so that the domain controller performs the corresponding function according to the corresponding status signal.

[0036] Optionally, the status signal can be parsed to determine whether a wake-up flag is present in the status signal. The status signal can then be filtered based on the wake-up flag. If a wake-up flag is present, the corresponding status signal can be determined as the target interaction signal based on the wake-up flag. Alternatively, the status signal can be filtered based on the function corresponding to the zone controller's status signal, with the status signal used for wake-up being determined as the target interaction signal.

[0037] Step 120: If the network state of the network where the domain controller is located is in a dormant state, a network wake-up request is sent to the domain controller.

[0038] As a method, when the domain controller executes the corresponding function according to the target interaction signal, the network status of the CAN network where the domain controller is located can be determined first. When the network status is in the awake state, it can be determined that the domain controller can directly execute the corresponding function according to the target interaction signal of the regional controller. When the network status is in the dormant state, the network where the domain controller is located can be awakened first, and then the corresponding function can be executed according to the target interaction signal of the regional controller after awakening. This avoids receiving the target interaction signal when the network where the domain controller is located is in the dormant state or during the awakening process, resulting in the domain controller being unable to respond according to the target interaction signal, resulting in failure of the vehicle function. Therefore, before sending the target interaction signal to the domain controller, the network status of the network where the domain controller is located is determined first.

[0039] As one method, the network status of the domain controller can be determined by obtaining network packets from the network where the domain controller is located. Optionally, if the network where the domain controller is located is in a dormant state, network packets from the network where the domain controller is located cannot be received. If network packets from the network where the domain controller is located are received, it is determined that the network where the domain controller is located is in an awake state.

[0040] Optionally, the network message of the network where the domain controller is located can be analyzed to determine whether any of the sleep flags, wake-up flags or maintain wake-up flags are present in the network message, thereby determining the network status of the network where the domain controller is located.

[0041] As a method, when it is determined that the network status of the network where the domain controller is located is in a dormant state, it can be determined that the domain controller can be woken up first, so that when the domain controller is in the awake state, it can execute corresponding functions according to the target interaction signal.

[0042] Optionally, when it is determined that the network state of the network where the domain controller is located is in a dormant state, a network wake-up request is generated according to a wake-up source of the domain controller, so that the network wake-up request can be sent to the domain controller to wake up the domain controller.

[0043] Step 130: If a handshake signal fed back by the domain controller in response to the network wake-up request is received, the target interaction signal is sent to the domain controller.

[0044] As a method, the domain controller wakes up the network where the domain controller is located according to the received network wake-up request, and generates and sends a handshake signal to the regional controller, so that the regional controller can handshake according to the handshake signal fed back by the domain controller in response to the network wake-up request, so that the target interaction signal can be sent to the domain controller after the handshake is completed, so that the domain controller can execute the corresponding function according to the received target interaction signal, thereby avoiding the inability to execute the corresponding function according to the target signal due to the network where the domain controller is located being in a dormant state or receiving the target interaction signal during the initialization process, and the increase in the function execution time, thereby affecting the overall user experience.

[0045] Optionally, handshake verification can be flexibly performed based on the actual wake-up situation of the domain controller, avoiding extra time consumption and improving the user's car experience. As shown in Figure 4, when the switch is detected, regional controller A first performs network initialization, which consumes T1ms. After initialization is complete, it sends region A_NM to the domain controller, so that the domain controller initializes according to region A_NM, which consumes T2ms. After initialization is complete, the handshake signal domain controller_NM is fed back to regional controller A. Regional controller A performs a handshake confirmation based on the handshake signal domain controller_NM. After the handshake is confirmed, regional controller A sends a switch signal to the domain controller, so that the domain controller executes the corresponding function. In the prior art, a fixed initialization time method is usually used, that is, the regional controller is not allowed to issue a function request or status until a certain period of time after the network where the domain controller is located is woken up by the network. As shown in Figure 5, when the switch is detected to be pressed, the regional controller A first performs network initialization, which consumes T1ms. After the initialization is completed, it sends the regional A_NM to the domain controller so that the domain controller initializes according to the regional A_NM, which consumes T2ms. After a delay of T3ms in sending the regional A_NM to the domain controller, the regional controller A sends the switch signal to the domain controller so that the domain controller performs the corresponding function. The bus wake-up time of the vehicle is divided into two cases, Tmin (network wake-up only) and Tmax (low-power wake-up), according to the sleep state. In Figures 4 and 5, when the network state of the network where the domain controller is located is in sleep state, the time from pressing the switch to sending is: Thandshakemin=Tswitch anti-shake time+T1min+T2min; Thandshakemax=Tswitch anti-shake time+T1max+T2max; Tdelaymin=Tswitch anti-shake time+T1min+T3; Tdelaymax=Tswitch anti-shake time+T1max+T3, among which T3>T2max. It can be determined that the handshake scheme of the present application can ensure that the functional signal is sent earlier, reduce the response time, and improve the functional response efficiency of the domain controller.

[0046] In an embodiment of the present application, the status signal of the regional controller is first obtained, and the target interaction signal for waking up the domain controller is determined in the status signal, and the network status of the network where the domain controller is located is determined, and then when the network status is in a dormant state, a network wake-up request is sent to the domain controller, so that the domain controller can shake hands with the regional controller based on the network wake-up request, and after receiving the handshake signal fed back by the domain controller based on the network wake-up request, the target interaction signal is sent to the domain controller, so that the domain controller executes the function corresponding to the target interaction signal. The solution of the present application can flexibly perform handshake verification according to the actual wake-up situation of the domain controller, avoid extra time consumption, and improve the car-using experience. A handshake judgment logic is added for the sending of the target interaction signal, and the function of communicating and shaking hands with the receiving node is realized by sending a network wake-up request, thereby ensuring the timeliness and success rate of the handshake process and improving the efficiency of information interaction between different controllers.

[0047] Please refer to Figure 6, which shows a network wake-up method provided by an embodiment of the present application. The process shown in Figure 6 will be described in detail below. The network wake-up method may specifically include the following steps:

[0048] Step 210: Acquire multiple network messages of the regional controller and determine the message type corresponding to each of the multiple network messages.

[0049] As a method, the regional controller may include multiple sensors, each sensor corresponds to a node, and each node will send its own corresponding network message. The routing management module in the regional controller can be used to obtain the network messages of each node under the regional controller, thereby obtaining multiple network messages of the regional control.

[0050] Optionally, each node under the regional controller will generate a corresponding network message when a change occurs, and the network message includes node information, so that the message type corresponding to each of the multiple network messages can be determined based on the node information in the multiple network messages.

[0051] Step 220: If there is a target network message of an event type among the multiple network messages, the status signal is obtained from the target network message, wherein the target network message of the event type is a network message generated when the state of the zone controller changes.

[0052] As a method, when performing message analysis on multiple network messages, the corresponding node information in the multiple network messages can be determined to determine whether the node information indicates that a state change has occurred in the regional controller. If it is determined that the node information indicates that a state change has occurred in the regional controller, the message type of the network message corresponding to the node information is determined to be an event type.

[0053] Alternatively, the status signal may be a signal indicating a change in the state of a sensor corresponding to a node managed by the regional controller. For example, if a switch managed by a regional controller is pressed, the corresponding status signal may be a signal indicating a change in the value of the switch signal to 0. Alternatively, the status signal may be a signal indicating a change from one state to another.

[0054] Step 230: If there is a status signal for waking up the domain controller in the status signal, determine the status signal for waking up the domain controller as the target interaction signal.

[0055] As a method, since the status signals in the target network message may include status signals of different types and different functions, in order to accurately determine the interaction signal that needs to be sent after the regional controller and the domain controller shake hands (that is, the domain controller needs to be woken up), the status signal used to wake up the domain controller can be determined as the target interaction signal according to the function of the status signal.

[0056] In some embodiments, step 230 includes: if there is a reference state signal in the state signal that changes from a first signal value to a second signal value, determining a change time interval for the reference state signal to change from the first signal value to the second signal value; if the change time interval is less than a second preset time interval and the reference state signal is a state signal for waking up the domain controller, determining the reference state signal as the target interaction signal.

[0057] As a method, since a sensor may change multiple times in a short period of time (such as a momentary switch), the interval between each change from the first signal value to the second signal value or the change from the second signal value to the first signal value is shorter than the initialization time of the zone controller. As a result, after the zone controller is initialized, it is detected that the status signal has not changed, resulting in the zone controller not shaking hands with the domain controller and not sending the status signal, thereby making the corresponding function unable to be implemented. Therefore, when it is determined that there is a change from the first signal value to the second signal value in the status signal and the time interval from the first signal value to the second signal value is shorter than the second preset time interval and the status signal is a signal for waking up the domain controller, the status signal is determined to be a target interaction signal. Optionally, the first preset time interval can be set according to actual needs. For example, the initialization time of the zone controller can be set to the second preset time interval. No specific limitation is made here.

[0058] Step 240: If the network state of the network where the domain controller is located is in a dormant state, a network wake-up request is sent to the domain controller.

[0059] In some embodiments, after step 250, the method further includes: if no handshake signal sent by the domain controller is received within a first preset time interval, sending the target interaction signal to the domain controller.

[0060] As a way, in order to avoid the target interaction signal being unable to be sent to the domain controller due to handshake failure, and then causing the domain controller to be unable to perform the corresponding function according to the target interaction signal, therefore, when it is determined that the handshake signal sent by the domain controller is not received within the first preset time interval, the target interaction signal is directly sent to the domain controller, so that the domain controller performs the corresponding function according to the target interaction signal.

[0061] Step 250: If a handshake signal fed back by the domain controller in response to the network wake-up request is received, the target interaction signal is sent to the domain controller.

[0062] The specific step descriptions of step 240 to step 250 can refer to step 120 to step 130, which will not be repeated here.

[0063] In this embodiment, screening is performed based on the message types of multiple network messages to determine that the message type of the multiple network messages is an event type network message, and a status signal is obtained from the network message of the event type. Furthermore, a status signal for waking up the domain controller is determined in the status signal as a target interaction signal, thereby ensuring that the domain controller can perform corresponding functions according to the target interaction signal, and ensuring information interaction of the target interaction signal between the regional controller and the domain controller.

[0064] Please refer to Figure 7, which shows a network wake-up method provided by an embodiment of the present application. The process shown in Figure 7 will be described in detail below. The network wake-up method may specifically include the following steps:

[0065] Step 310: If it is determined to obtain the status signal of the regional controller, a target interaction signal for waking up the domain controller is determined from the status signal.

[0066] Step 320: Determine the message period corresponding to each of the plurality of network messages and the message type corresponding to each of the plurality of network messages.

[0067] As one approach, multiple network messages can be parsed to determine the message period and message type corresponding to each of the multiple messages. Optionally, when generating a network message, the message sending period corresponding to each network message can be added to the corresponding network message, thereby determining the message period corresponding to each of the multiple network messages by parsing the multiple network messages.

[0068] Optionally, each node under the regional controller will generate a corresponding network message when a change occurs, and the network message includes node information, so that the message type corresponding to each of the multiple network messages can be determined based on the node information in the multiple network messages.

[0069] Step 330 : Filter out at least two target network packets from the plurality of network packets according to the packet periods corresponding to the plurality of network packets and the packet types corresponding to the plurality of network packets.

[0070] As a way to improve the handshake success rate between the domain controller and the regional controller, the domain controller can be awakened by at least two different types of network messages. As long as any one of the at least two different types of network messages can enable the domain controller to feedback the handshake signal value to the regional controller, it can be determined that the handshake between the regional controller and the domain controller is successful.

[0071] Optionally, a message period threshold may be pre-set to determine the first type of network message whose message period is less than the message period threshold among multiple network messages, thereby ensuring that the domain controller can receive the wake-up request corresponding to the first type of network message as early as possible, thereby shortening the handshake time between the regional controller and the domain controller.

[0072] Optionally, in order to ensure the handshake success rate of the domain controller, the second type of network messages with network management type can be filtered according to the message types of multiple network messages, so that the domain controller can successfully wake up according to the wake-up request corresponding to the network message of network management type and shake hands with the regional controller.

[0073] Step 340: Generate a network wake-up request corresponding to each of the at least two target network messages, and send the network wake-up request corresponding to each of the at least two target network messages to the domain controller.

[0074] As one approach, after determining at least two target network messages, corresponding network wake-up requests are generated based on the at least two network messages. Optionally, if the target network message is a short-period message (i.e., the message period is less than a message period threshold), a network wake-up request carrying a message period is generated based on the message period of the target network message, thereby enabling the corresponding network wake-up request to be sent to the domain controller based on the message period.

[0075] Optionally, if the target network message is a network management type network message, a network wake-up request carrying the message type is generated according to the network management type of the target network message, thereby ensuring that the domain controller can wake up the network where the domain controller is located according to the network wake-up request carrying the message type, thereby ensuring the handshake success rate of the domain controller.

[0076] Step 350: If a handshake signal fed back by the domain controller in response to the network wake-up request is received, the target interaction signal is sent to the domain controller.

[0077] The specific step descriptions of steps 310 to 320 and step 350 can refer to steps 110 and 130 and will not be repeated here.

[0078] In this embodiment, when it is determined that the network state of the domain controller is in a dormant state, the message period and message type corresponding to each of the multiple network messages obtained from the regional controller are determined, so that the multiple network messages are filtered according to the message period and the message type, so that at least two target network messages are determined from the multiple network messages, so that corresponding network wake-up requests are generated according to the at least two target network messages, and then the domain controller is woken up based on the network wake-up request, so that the domain controller and the regional controller complete the handshake, thereby improving the handshake success rate.

[0079] Please refer to Figure 8, which shows a network wake-up method provided by an embodiment of the present application. The following will describe the process shown in Figure 8 in detail. The network wake-up method may specifically include the following steps:

[0080] Step 410: Acquire a status signal of the regional controller, and determine a target interaction signal for waking up the domain controller from the status signal.

[0081] Step 420: If the network state of the network where the domain controller is located is in a dormant state, a network wake-up request is sent to the domain controller.

[0082] The specific step descriptions of step 410 to step 420 can refer to step 110 to step 120, which will not be repeated here.

[0083] Step 430: During the process of waiting to receive the handshake signal, if the target interaction signal changes, the changed target interaction signal is determined.

[0084] As a method, while waiting for the domain controller to respond to the network wake-up request and feedback the handshake signal, if the target interaction signal to be sent continues to change, it will be sent according to the initial state of the target interaction signal after the handshake is successful. Therefore, while the regional controller is waiting to receive the handshake signal, if it is detected that the target interaction signal has changed, it is necessary to determine the changed target interaction signal.

[0085] Step 440: After receiving the handshake signal, the changed target interaction signal is sent to the domain controller.

[0086] As a method, when the regional controller receives the handshake signal sent by the domain controller in response to the network wake-up request, it can first determine the timestamp of receiving the handshake signal, and determine the target interaction signal after the last change before the time corresponding to the timestamp based on the timestamp, so that the changed target interaction signal can be sent to the domain controller, ensuring that the domain controller can perform the corresponding function according to the changed target interaction signal.

[0087] In this embodiment, while waiting to receive a handshake signal, after determining that the target signal has changed, the changed target interaction signal is sent to the domain controller after receiving the handshake signal, so that the domain controller executes the corresponding function according to the latest target interaction signal, thereby ensuring the real-time nature of the target interaction signal.

[0088] Please refer to Figure 9, which shows a network wake-up method provided by an embodiment of the present application. The process shown in Figure 9 will be described in detail below. The network wake-up method may specifically include the following steps:

[0089] Step 510: Acquire a status signal of the regional controller, and determine a target interaction signal for waking up the domain controller from the status signal.

[0090] Step 520: If the network state of the network where the domain controller is located is in a dormant state, a network wake-up request is sent to the domain controller.

[0091] The specific step descriptions of step 510 to step 520 can refer to step 110 to step 120, which will not be repeated here.

[0092] Step 530: While waiting for the handshake signal to be received, obtain a default signal and send the default signal to the domain controller, wherein the default signal does not contain a value indicating a signal change.

[0093] As a way to ensure the sending specifications of the target interactive signal or network message, while waiting for the domain controller to respond to the network wake-up request and feedback the handshake signal, you can first obtain the default signal. The default signal can be the value corresponding to the default state of the switch IO port during wake-up, or it can be the standby RAM memory value, and then send the default signal to the domain controller.

[0094] Step 540: If the target interaction signal changes, determine the changed target interaction signal.

[0095] As a method, while waiting for the domain controller to respond to the network wake-up request and feedback the handshake signal, if the target interaction signal to be sent continues to change, it will be sent according to the initial state of the target interaction signal after the handshake is successful. Therefore, while the regional controller is waiting to receive the handshake signal, if it is detected that the target interaction signal has changed, it is necessary to determine the changed target interaction signal.

[0096] Step 550: When the number of frames sent by the default signal is greater than or equal to the preset number of frames, the changed target interaction signal is sent to the domain controller.

[0097] As one approach, when it is determined that the regional controller has received a handshake signal fed back by the domain controller in response to a network wake-up request, or has not received a handshake signal within a first preset time interval, and when it is determined that the target interaction signal has changed, it is first determined whether the number of frames sent by the default signal is greater than or equal to the preset number of frames. If it is determined that the number of frames sent by the default signal is greater than or equal to the preset number of frames, the changed target interaction signal is sent to the domain controller, thereby ensuring that the target interaction signal is effectively received. As shown in Figure 10, for different target interaction signals, while waiting to receive a handshake signal, the default signal is first obtained and sent to the domain controller. If the regional controller receives a handshake signal or determines that it has not received a handshake signal within the first preset time interval, the target interaction signal is sent until all target interaction signals are sent.

[0098] In this embodiment, while waiting to receive a handshake signal, a default signal is first obtained and sent to the domain controller. Thus, after determining that the target interaction signal has changed, the changed target interaction signal is determined, and after the regional controller receives the handshake signal, when the number of frames of the default signal sent is greater than the preset number of frames, the changed target interaction signal is sent, thereby ensuring the sending specifications of the target interaction signal and the real-time nature of the interaction signal.

[0099] Figure 11 is a network wake-up method shown in an embodiment of the present application. As shown in Figure 11, when the state of the switch or sensor managed by the regional controller changes or an event request is issued, the network state of the network where the domain controller is located is determined. If it is determined that the network state of the network where the domain controller is located is in the awake state, the signal corresponding to the switch or sensor is sent to the domain controller according to the normal sending logic of the network message or signal; if it is determined that the network state of the network where the domain controller is located is in the sleep state, a network wake-up request is sent to the domain controller, and it is determined whether the regional controller receives the handshake signal sent by the domain controller. If the handshake signal is received, the request signal corresponding to the switch or sensor is sent to the domain controller based on the handshake signal; if the handshake signal is not received within the first preset time interval, the request signal corresponding to the switch or sensor is still sent to the domain controller, so as to flexibly perform handshake verification according to the actual wake-up situation of the controller, avoid extra time consumption, and improve the car experience.

[0100] FIG12 is a block diagram of a network wake-up device according to an embodiment of the present application. As shown in FIG12 , the network wake-up device 600 includes: a target interaction signal determination module 610 , a first sending module 620 , and a second sending module 630 .

[0101] The target interaction signal determination module 610 is used to obtain the status signal of the regional controller and determine the target interaction signal for waking up the domain controller from the status signal; the first sending module 620 is used to send a network wake-up request to the domain controller if the network status of the network where the domain controller is located is a dormant state; the second sending module 630 is used to send the target interaction signal to the domain controller if a handshake signal fed back by the domain controller in response to the network wake-up request is received.

[0102] In some embodiments, the network wake-up device 600 further includes: a third sending module, configured to send the target interaction signal to the domain controller if the handshake signal sent by the domain controller is not received within a first preset time interval.

[0103] In some embodiments, the target interaction signal determination module 610 includes: a message type determination submodule, used to obtain multiple network messages of the regional controller and determine the message type corresponding to each of the multiple network messages; a status signal acquisition submodule, used to obtain the status signal from the target network message if there is a target network message whose corresponding message type is an event type among the multiple network messages, wherein the target network message of the event type is a network message generated when the status of the regional controller changes; a target interaction signal determination submodule, used to determine the status signal for waking up the domain controller as the target interaction signal if there is a status signal for waking up the domain controller in the status signal.

[0104] In some embodiments, the target interaction signal determination submodule includes: a change time interval determination unit, which is used to determine the change time interval for the reference state signal to change from the first signal value to the second signal value if there is a reference state signal in the state signal that changes from the first signal value to the second signal value; a target interaction signal determination unit, which is used to determine the reference state signal as the target interaction signal if the change time interval is less than the first preset time interval and the reference state signal is a state signal for waking up the domain controller.

[0105] In some embodiments, the first sending module 620 includes: a message acquisition submodule, which is used to obtain multiple network messages of the regional controller if the network state is the sleep state; a message type acquisition submodule, which is used to determine the message period corresponding to each of the multiple network messages and the message type corresponding to each of the multiple network messages; a target network message determination submodule, which is used to filter out at least two target network messages from the multiple network messages according to the message period corresponding to each of the multiple network messages and the message type corresponding to each of the multiple network messages; a sending submodule, which is used to generate a network wake-up request corresponding to each of the at least two target network messages, and send the network wake-up request corresponding to each of the at least two target network messages to the domain controller respectively.

[0106] In some embodiments, the network wake-up device 600 also includes: an update module, which is used to determine the changed target interaction signal if the target interaction signal changes while waiting to receive the handshake signal; and a fourth sending module, which is used to send the changed target interaction signal to the domain controller after receiving the handshake signal.

[0107] In some embodiments, the network wake-up device 600 also includes: a fifth sending module, used to obtain a default signal and send the default signal to the domain controller while waiting for the handshake signal to be received, wherein the default signal does not contain a value indicating that the signal has changed; a determination module, used to determine the changed target interaction signal if the target interaction signal changes; and a sixth sending module, used to send the changed target interaction signal to the domain controller when the number of sending frames of the default signal is greater than or equal to the preset number of frames.

[0108] According to one aspect of an embodiment of the present application, an electronic device is also provided. As shown in Figure 13, the vehicle 700 includes a processor 710 and one or more memories 720. The one or more memories 720 are used to store program instructions executed by the processor 710. When the processor 710 executes the program instructions, the above-mentioned network wake-up method is implemented.

[0109] Furthermore, the processor 710 may include one or more processing cores. The processor 710 runs or executes instructions, programs, code sets, or instruction sets stored in the memory 720, and calls data stored in the memory 720. Optionally, the processor 710 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 710 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to handle wireless communications. It is understandable that the above-mentioned modem may not be integrated into the processor and may be implemented separately through a communication chip.

[0110] According to one aspect of the present application, a computer-readable storage medium is provided. The computer-readable storage medium may be included in the electronic device described in the above embodiments, or may exist independently without being incorporated into the electronic device. The computer-readable storage medium carries computer-readable instructions. When the computer-readable storage instructions are executed by a processor, the method of any of the above embodiments is implemented.

[0111] It should be noted that the computer-readable medium shown in the embodiments of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0112] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. In some cases, the names of these units do not constitute limitations on the units themselves.

[0113] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0114] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of this application and include common knowledge or customary techniques in the art that are not disclosed herein.

[0115] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for waking up a network, characterized in that, The method includes: Obtaining a status signal of a regional controller and determining a target interaction signal for waking up a domain controller from the status signal; If the network status of the network where the domain controller is located is in a sleep state, sending a network wake-up request to the domain controller; If a handshake signal fed back by the domain controller in response to the network wake-up request is received, sending the target interaction signal to the domain controller.

2. The method according to claim 1, wherein After sending the network wake-up request to the domain controller, the method further includes: If the handshake signal sent by the domain controller is not received within a first preset time interval, sending the target interaction signal to the domain controller.

3. The method according to claim 1, wherein The obtaining the status signal of the regional controller and screening out the target interaction signal for waking up the domain controller from the status signal includes: Obtaining a plurality of network packets of the regional controller and determining the packet type corresponding to each of the plurality of network packets; If there is a target network packet with a corresponding packet type being an event type among the plurality of network packets, obtaining the status signal in the target network packet, where the target network packet of the event type is a network packet generated by a status change of the regional controller; If there is a status signal for waking up the domain controller in the status signal, determining the status signal for waking up the domain controller as the target interaction signal.

4. The method according to claim 3, characterized in that The if there is a status signal for waking up the domain controller in the status signal, determining the status signal for waking up the domain controller as the target interaction signal includes: If there is a reference status signal whose first signal value changes to a second signal value in the status signal, determining the change time interval during which the reference status signal changes from the first signal value to the second signal value; If the change time interval is less than a second preset time interval and the reference status signal is a status signal for waking up the domain controller, determining the reference status signal as the target interaction signal.

5. The method according to claim 1, wherein The if the network status is in a sleep state, sending a network wake-up request to the domain controller includes: If the network status is in the sleep state, obtaining a plurality of network packets of the regional controller; Determining the packet period corresponding to each of the plurality of network packets and the packet type corresponding to each of the plurality of network packets; Screening out at least two target network packets from the plurality of network packets according to the packet period corresponding to each of the plurality of network packets and the packet type corresponding to each of the plurality of network packets; Generating network wake-up requests corresponding to each of the at least two target network packets and sending the network wake-up requests corresponding to each of the at least two target network packets to the domain controller respectively.

6. The method according to any one of claims 1-5, characterized in that, If it is determined that the network status is in a sleep state, after sending a network wake-up request to the domain controller, the method further includes: During the process of waiting to receive the handshake signal, if the target interaction signal changes, determining the changed target interaction signal; After receiving the handshake signal, sending the changed target interaction signal to the domain controller.

7. The method according to any one of claims 1-5, characterized in that, If it is determined that the network state is the sleep state, after sending a network wake-up request to the domain controller, the method further includes: During the process of waiting to receive the handshake signal, obtain a default signal and send the default signal to the domain controller, where there is no value indicating a change in the signal in the default signal; If the target interaction signal changes, determine the changed target interaction signal; When the number of transmission frames of the default signal is greater than or equal to a preset number of frames, send the changed target interaction signal to the domain controller.

8. A wake-up device for a network, characterized in that The device includes: A target interaction signal determination module, configured to obtain a status signal of a regional controller and determine a target interaction signal for waking up the domain controller from the status signal; A first sending module, configured to send a network wake-up request to the domain controller if the network state of the network where the domain controller is located is the sleep state; A second sending module, configured to send the target interaction signal to the domain controller if a handshake signal fed back by the domain controller in response to the network wake-up request is received.

9. An electronic device, characterized in that, The electronic device includes: A processor; A memory, on which computer-readable instructions are stored, and when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that, Program code is stored in the computer-readable storage medium, and the program code can be called by the processor to execute the method according to any one of claims 1 to 7.

Images