Dormancy wake-up method, apparatus, device, vehicle, and medium

Abstract

The application provides a hibernation wake-up method, device, equipment, vehicle and medium, wherein the method comprises: in response to a detected wake-up event, identifying the type of wake-up source; in response to the type of wake-up source being a message wake-up, determining the type of message wake-up; in response to the type of message wake-up being an application message, entering a preset state; and in response to detecting a jump edge change of a pin of a wake-up source corresponding to an application message within a preset time during the preset state, performing a hibernation wake-up operation. In this way, the area controller can be prevented from being repeatedly and mistakenly woken up by an application message sent by another controller, thereby reducing current consumption, reducing high-voltage power supply cycles, and significantly reducing the static power consumption of the whole vehicle.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and more particularly to a sleep / wake-up method, apparatus, device, vehicle, and medium. Background Technology

[0002] As automotive electronic and electrical architectures move towards centralized domain controllers, more and more automakers are setting up Zone Control Units (ZCUs) in different locations on the vehicle body. This allows sensors, actuators, and other components that are physically close to each other to be connected to the same ZCU, which then handles the inputs and outputs of the relevant areas in a unified manner.

[0003] Because the area controller integrates a large number of input / output (I / O) interfaces and component control functions, when the vehicle's high voltage is de-energized and it enters a sleep state, other controllers (such as the battery management system (BMS) and remote communication module (TBOX) still need to continuously send application messages for a specific period of time (e.g., 1 hour) due to functional requirements. During this time, the area controller will continuously receive application messages from other controllers, repeatedly waking up from sleep and immediately resuming the detection and control of all inputs and outputs, resulting in prolonged current consumption. This, in turn, triggers a high-voltage charging cycle, significantly increasing the vehicle's static power consumption. Summary of the Invention

[0004] This application provides a sleep-wake method, apparatus, device, vehicle, and medium that can prevent the area controller from being repeatedly and falsely woken up by application messages sent by other controllers, thereby reducing current consumption, reducing high-voltage power replenishment cycles, and significantly reducing the static power consumption of the entire vehicle.

[0005] In a first aspect, embodiments of this application provide a sleep / wake-up method applied to a region controller, the method comprising: In response to a detected wake-up event, identify the type of wake-up source; In response to the wake-up source being a message wake-up, the type of the message wake-up is determined; In response to the message wake-up type being an application message, the system enters a preset state; In response to the detection of a transition edge change on the wake-up source pin corresponding to the application message within a preset time period during the preset state, a sleep wake-up operation is performed.

[0006] Secondly, embodiments of this application provide a sleep / wake-up device configured in a region controller, comprising: The identification module is used to identify the type of wake-up source in response to a detected wake-up event; The determination module is configured to determine the type of wake-up message in response to the wake-up source being a message wake-up message. The first processing module is configured to enter a preset state in response to the wake-up message being an application message. The wake-up module is used to perform a sleep-wake-up operation in response to a change in the edge of the wake-up source pin corresponding to the application message within a preset time during the preset state.

[0007] Thirdly, embodiments of this application provide an electronic device, including: A processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to perform a sleep-wake method as described in any one of the embodiments of this application.

[0008] Fourthly, embodiments of this application provide a vehicle including electronic equipment as described in embodiments of this application.

[0009] Fifthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that causes a computer to perform the sleep-wake method described in any one of the embodiments of this application.

[0010] The technical solution disclosed in this application identifies the type of wake-up source in response to a detected wake-up event. If the wake-up source type is message wake-up, the type of message wake-up is determined. If the message wake-up type is application message, a preset state is entered. Furthermore, if a transition edge is detected on the wake-up source pin corresponding to the application message within a preset time while in the preset state, a sleep wake-up operation is performed. This avoids repeated false wake-ups of the area controller by application messages sent by other controllers, thereby reducing current consumption, minimizing high-voltage power replenishment cycles, and significantly reducing the overall vehicle static power consumption. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 A flowchart of a sleep-wake method provided in an embodiment of this application; Figure 2 A flowchart illustrating another sleep-wake method provided in this application embodiment; Figure 3 A flowchart illustrating another hibernation / wake-up method provided in this application embodiment; Figure 4 A schematic block diagram of a sleep / wake-up device provided in an embodiment of this application; Figure 5 A schematic block diagram of an electronic device provided in an embodiment of this application; Figure 6 This is a schematic block diagram of a vehicle provided in an embodiment of this application. Detailed Implementation

[0013] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0014] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0015] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or solution described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0016] As mentioned earlier, since the area controller integrates a large number of input / output interfaces and component control functions, when the vehicle's high voltage is de-energized and it enters a sleep state, other controllers (such as the Battery Management System (BMS) and the Telecommunication Module (TBOX) still need to continuously send application messages for a specific period of time (e.g., 1 hour) due to functional requirements. During this time, the area controller will continuously receive application messages from other controllers, repeatedly waking up from sleep mode and immediately resuming the detection and control of all inputs and outputs, resulting in prolonged current consumption. This, in turn, triggers a high-voltage charging cycle, significantly increasing the vehicle's static power consumption.

[0017] In response, this application provides a hibernation wake-up method, apparatus, device, vehicle, and medium to solve the problem that after a vehicle is powered down and enters a hibernation state, other controllers continuously send application messages within a specific time period, causing the area controller to repeatedly wake up from hibernation, resulting in long-term current consumption, which in turn triggers a high-voltage power replenishment cycle and significantly increases the static power consumption of the entire vehicle.

[0018] The technical solutions provided in this application will be described in detail below through some embodiments. It should be noted that the various embodiments of this application can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0019] Figure 1 This is a flowchart illustrating a sleep / wake-up method provided in an embodiment of this application. The sleep / wake-up method provided in this embodiment can be applied to a region controller, i.e., it is executed by the region controller.

[0020] like Figure 1 As shown in the embodiments of this application, the sleep-wake method may include the following steps: S101, in response to the detected wake-up event, identifies the type of wake-up source.

[0021] The aforementioned wake-up event refers to a trigger signal that wakes the area controller from a low-power sleep state to a full-function operating state, such as remotely unlocking the vehicle with a vehicle key, remotely turning on the air conditioner with a vehicle key, opening the door, or pressing the brake pedal.

[0022] The wake-up source mentioned above refers to the origin of the wake-up event. For example, when the wake-up event is the vehicle key remotely unlocking the vehicle or the vehicle key remotely turning on the air conditioning, then the wake-up source can be determined to be the vehicle key; when the wake-up event is the car door being opened, then the wake-up source can be determined to be the car door, and so on.

[0023] It should be understood that the aforementioned wake-up source can also be the primary wake-up source, which refers to the main wake-up source or the first wake-up source of a wake-up operation.

[0024] In some embodiments, when the vehicle's high voltage is de-energized and it enters a sleep state, the area controller on the vehicle also enters a sleep state. Although the area controller enters a sleep state, some logic circuits within it (such as network transceivers, I / O edge detection logic, etc.) remain operational. When these logic circuits detect a wake-up event that would wake the area controller from a sleep state to full-function operation, the area controller can identify the wake-up source type corresponding to the wake-up event and determine whether to perform a sleep-wake operation based on the wake-up source type to avoid accidental wake-up. Specifically, the wake-up source type refers to the type of wake-up source.

[0025] In one optional implementation, the area controller of this application identifies the wake-up source type corresponding to the wake-up event, which may include: in response to detecting a wake-up event, obtaining the network management message corresponding to the wake-up event; and identifying the type of wake-up source based on preset bytes in the network management message.

[0026] In some embodiments, the structure of the network management message corresponding to the wake-up event can be as shown in Table 1 below: Table 1

[0027] The term "Bit" specifically refers to a bit, and "Byte" specifically refers to a byte.

[0028] The wake-up sources corresponding to the above wake-up events can include the following: The first type, 0x0F: Initialization reason unknown (temporarily allowed, set to a specific wake-up event in the second Protocol Data Unit (PDU)); The second type, 0x1F: Wake-up from the bus (received a Network Management or Diagnostic message). The third type, 0x2F: Power is supplied by the auxiliary power position (Accessory, ACC) or the ignition switch ON position signal (Klemme 15, LK15); The fourth type, 0x3F to 0x7F: Peripheral Input / Output (I / O) wake-up.

[0029] The peripheral input / output (I / O) wake-up can include, but is not limited to, wake-up when the car door is opened or the car window is raised or lowered.

[0030] The aforementioned hold event AC refers to the condition for the area controller to remain awake. Furthermore, multiple hold-and-wake events can be set in parallel within the same network management message, as shown in Table 2 below: Table 2

[0031] It should be understood that each hold event corresponding to each bit is an independent event; Furthermore, the holding events shown in Table 2 above are merely illustrative examples of this application and are not intended as specific limitations on this application. They can be flexibly adjusted according to actual application needs.

[0032] Based on the structure of the network management message shown in Table 1 above, the area controller of this application can obtain preset bytes from the network management message corresponding to the wake-up event. Then, based on the wake-up source defined by the preset bytes corresponding to the wake-up event, the type of wake-up source is identified. The preset bytes can be selected as Bytes 3-4 in the network management message shown in Table 1.

[0033] In this application, the wake-up source type may include: local event wake-up and message wake-up.

[0034] Among them, the wake-up source type corresponding to 0x2F to 0x7F in the preset bytes is local event wake-up, and the wake-up source type corresponding to 0x0F to 0x1F in the preset bytes is message wake-up.

[0035] For example, assuming the wake-up event defined in the preset bytes of the network management message is the peripheral input / output I / O wake-up of the door being opened, then according to the wake-up source type corresponding to 0x2F to 0x7F in the preset bytes being local event wake-up, the wake-up source type corresponding to the door being opened wake-up event is determined to be local event wake-up.

[0036] For example, assuming the wake-up event defined in the preset bytes of the network management message is bus wake-up, then based on the wake-up source type corresponding to 0x0F to 0x1F in the preset bytes being message wake-up, the type of the wake-up source corresponding to the bus wake-up event is determined to be message wake-up.

[0037] S102, in response to the wake-up source being message wake-up, determine the type of message wake-up.

[0038] In some embodiments, considering that the types of message wake-up may include multiple types, such as network management messages and application messages, the regional controller of this application can further determine the type of message wake-up after determining that the wake-up source type corresponding to the wake-up event is message wake-up, and then take different response operations according to the type of message wake-up, thereby reducing the problem of the regional controller being repeatedly and mistakenly woken up by application messages sent by other controllers.

[0039] As an optional implementation, when determining the type of message wake-up, this application may optionally include: in response to the wake-up source being a message wake-up, obtaining the identifier information of the message wake-up; and then, determining the type of message wake-up based on the identifier information of the message wake-up.

[0040] Among them, the identification information of message wake-up refers to the unique information of message wake-up, such as the ID information of message wake-up.

[0041] Furthermore, the types of message wake-up in this application may include network management messages and application messages.

[0042] Considering that each wake-up message carries identification information, this application can obtain the identification information from the wake-up message when the wake-up source type is determined to be a wake-up message. Then, the type of the wake-up message can be found based on its identification information from a pre-established mapping relationship between identification information and types.

[0043] In other words, when determining the type of message wake-up, the type of message wake-up can be determined from the mapping relationship between the identifier and the type based on the identifier of the message wake-up.

[0044] It should be understood that the aforementioned pre-established mapping relationship between identification information and type specifically refers to the pre-established mapping relationship between the identification information of message wake-up and the type of message wake-up.

[0045] In some embodiments, the mapping relationship between the pre-established identification information and type can be shown in Table 3 below.

[0046] Table 3

[0047] In other embodiments, the mapping relationship between the pre-established identification information and type can also be shown in Table 4 below.

[0048]

[0049] Each identifier in Table 3 above corresponds to a type of information; Figure 4 Each range of identifier information corresponds to a type of information.

[0050] It should be noted that Tables 3 and 4 above are merely illustrative examples of this application and are not intended to limit this application. They can be added, deleted, modified, or updated as needed.

[0051] S103, in response to the message wake-up type being an application message, enter the preset state.

[0052] S104, in response to being in a preset state, if a transition edge change is detected on the wake-up source pin corresponding to the application message within a preset time, a sleep wake-up operation is performed.

[0053] The aforementioned preset state refers to an intermediate state between sleep mode and full-function operation mode. Optionally, this preset state can be a restricted wake-up state.

[0054] In related technologies, when a region controller receives an application message from another controller (such as a battery management system, BMS), it immediately resumes the detection and control of all inputs and outputs. If a local wake-up source (such as a position light switch) happens to be physically closed (lit) at this time, but this state has been maintained for a long period before wake-up, the region controller will treat the received application message as a valid wake-up signal, directly triggering its own wake-up. This increases the load current of the position light, causing the low-voltage battery to deplete, which in turn triggers the high-voltage relay to close, replenishing the low-voltage battery through the high-voltage power battery. Furthermore, the high-voltage replenishment logic resets the timers of other controllers, causing them to continue sending application messages, thus waking up the region controller again. This process repeats, entering an infinite loop of "wake-up-replenishment-upload-re-wake-up," ultimately leading to excessive static current in the vehicle and severely depleting the high-voltage battery.

[0055] Therefore, when the area controller of this application determines that the wake-up message type is an application message, it does not directly use the application message as a valid wake-up signal to perform a sleep-wake operation. Instead, it enters a preset state to temporarily disable its own regular input / output processing functions and activates a monitoring circuit. This monitoring circuit monitors whether the wake-up source pin supporting the sleep-wake logic has a changing edge. The monitoring circuit detects whether the wake-up source pin has a changing edge, such as a rising edge or a falling edge. Based on the detection result, it determines whether to perform a sleep-wake operation.

[0056] In some embodiments, determining whether to perform a sleep-wake operation based on the detection result may include: if the monitoring circuit detects a rising edge or falling edge transition on the wake-up source pin corresponding to the application message within a preset time period, it is determined that this is a new operation intention generated by the user. In this case, the wake-up source flag can be updated from message wake-up to local event wake-up, and the preset state can be exited. A sleep-wake operation is then performed, allowing the area controller to restore the detection and control of all its inputs and outputs according to the local event wake-up logic, thus entering a full-function operating state to drive the load. In this way, when the message wake-up type is an application message, the area controller is controlled to enter a preset state, preventing the area controller from driving the load in this state. Through simple edge transition detection, not only can the current consumption during a single false wake-up be greatly reduced, but the accuracy of the area controller's sleep-wake operation can also be improved, preventing the area controller from being repeatedly and falsely woken up by application messages sent by other controllers.

[0057] The technical solution disclosed in this application identifies the type of wake-up source in response to a detected wake-up event. If the wake-up source type is message wake-up, the type of message wake-up is determined. If the message wake-up type is application message, a preset state is entered. Furthermore, if a transition edge is detected on the wake-up source pin corresponding to the application message within a preset time while in the preset state, a sleep wake-up operation is performed. This avoids repeated false wake-ups of the area controller by application messages sent by other controllers, thereby reducing current consumption, minimizing high-voltage power replenishment cycles, and significantly reducing the overall vehicle static power consumption.

[0058] Based on the foregoing embodiments, this application may optionally further include: in response to the fact that no edge change of the wake-up source pin corresponding to the application message is detected within a preset time period while in a preset state, the application re-enters the sleep state.

[0059] In some embodiments, the aforementioned determination of whether to perform a sleep / wake-up operation based on the detection result may further include: if the monitoring circuit does not detect a rising edge or falling edge transition on the wake-up source pin corresponding to the application message within a preset time period, then the local signal is determined to be a static hold signal. This static hold signal specifically refers to application messages repeatedly sent by other controllers within a specific time period, i.e., new operation intentions not generated by the user. In this case, it is determined that the received application message is not a valid wake-up signal, and the sleep / wake-up operation is not performed; instead, the system re-enters the sleep state from the preset state. This solves the problem of repeated false wake-ups of the regional controller due to application messages continuously sent by other controllers within a specific time period, preventing it from entering the sleep state and thus causing an infinite cycle of continuous charging of the high-voltage battery, thereby reducing the vehicle's static current consumption and static power consumption.

[0060] In some alternative implementations, considering that the types of message wake-up can include application messages and network management messages, then combining... Figure 2 The hibernation / wake-up method described in the foregoing embodiments is further optimized. For example... Figure 2 As shown, the method may include the following steps: S201, in response to the detected wake-up event, identifies the type of wake-up source.

[0061] S202, in response to the wake-up source type being message wake-up, determine the type of message wake-up. If the type of message wake-up is application message, proceed to step S203; otherwise, proceed to step S206.

[0062] S203, in response to the message wake-up type being an application message, enter the preset state.

[0063] S204, in response to being in a preset state, if a transition edge change is detected on the wake-up source pin corresponding to the application message within a preset time, a sleep wake-up operation is performed.

[0064] S205, in response to the fact that no edge change of the wake-up source pin corresponding to the application message is detected within a preset time during the preset state, it re-enters the sleep state.

[0065] S206, in response to a network management message as the wake-up message type, performs a sleep wake-up operation.

[0066] In some embodiments, when the type of wake-up message is determined to be a network management message, it indicates that the wake-up is valid. At this point, a sleep-wake operation can be performed to allow the area controller to resume the detection and control of all its inputs and outputs according to the local event wake-up logic, thus entering a full-function operating state to drive the load. Furthermore, while the area controller is in a full-function operating state, it can also synchronously monitor whether other wake-up events are active. If other wake-up events are active, the wake-up event is merged with other wake-up events, and the normal wake-up and maintenance logic is entered. In this way, when the wake-up event corresponds to a network management message, the network management message is treated as a valid wake-up signal, directly triggering the area controller's sleep-wake operation. This preserves the normal responsiveness to user operations and ensures a good user experience.

[0067] In some alternative implementations, considering that the wake-up source type can include message wake-up and local event wake-up, then combining Figure 3 The hibernation / wake-up method described in the foregoing embodiments will be further optimized and explained. For example... Figure 3 As shown, the method may include the following steps: S301, In response to the detected wake-up event, identify the type of wake-up source. If the type is message wake-up, proceed to step S302; otherwise, proceed to step S307.

[0068] S302, in response to the wake-up source type being message wake-up, determine the type of message wake-up. If the type of message wake-up is application message, proceed to step S303; otherwise, proceed to step S306.

[0069] S303, in response to a message wake-up type of application message, enters a preset state.

[0070] S304, in response to being in a preset state, if a transition edge change is detected on the wake-up source pin corresponding to the application message within a preset time, a sleep wake-up operation is performed.

[0071] S305, in response to the fact that no edge change of the wake-up source pin corresponding to the application message is detected within a preset time during the preset state, re-enters the sleep state.

[0072] S306, in response to a network management message as the wake-up message type, performs a sleep wake-up operation.

[0073] S307, in response to the wake-up source being a local event wake-up, performs a sleep wake-up operation.

[0074] In some embodiments, when the wake-up source is determined to be a local event wake-up, it indicates that the area controller is in a fully hibernating state. In this case, there is no need to detect the transition edge of the local event wake-up; that is, the local event wake-up is assumed to be a valid wake-up. The area controller can then perform a hibernation wake-up operation according to the network management wake-up and maintenance logic. This allows the area controller to restore the detection and control of all its inputs and outputs according to the local event wake-up logic, thus entering a full-function operating state to drive the load. In this way, when the wake-up source is a local event wake-up, the local event wake-up is treated as a valid wake-up signal, directly triggering the area controller's hibernation wake-up operation. This avoids the drawback of being unable to wake up the area controller after a local event wake-up is triggered, thereby preserving user operation responsiveness and ensuring a good user experience.

[0075] To implement the above embodiments, this application also proposes a sleep / wake-up device. Referring below to the appendix... Figure 4 This application describes a sleep / wake-up device proposed in its embodiments. Figure 4 As shown, the sleep-wake device 400 includes: an identification module 410, a determination module 420, a first processing module 430, and a wake-up module 440.

[0076] The identification module 410 is used to identify the type of wake-up source in response to a detected wake-up event; The determination module 420 is used to determine the type of message wake-up in response to the wake-up source being a message wake-up. The first processing module 430 is configured to enter a preset state in response to the wake-up message being an application message. The wake-up module 440 is used to perform a sleep-wake-up operation in response to a change in the edge of the wake-up source pin corresponding to the application message during a preset time period while in the preset state.

[0077] In one optional implementation of this application embodiment, the sleep / wake-up device 400 further includes: The second processing module is used to re-enter the sleep state if, during the preset state, no edge change is detected on the wake-up source pin corresponding to the application message within a preset time.

[0078] In one optional implementation of this application embodiment, the identification module 410 is specifically used for: In response to a detected wake-up event, the network management message corresponding to the wake-up event is obtained; The type of the wake-up source is identified based on preset bytes in the network management message.

[0079] In one optional implementation of this application embodiment, the determining module 420 is specifically used for: In response to the wake-up source being a message wake-up, the identifier information of the message wake-up is obtained; The type of message wake-up is determined based on the identifier information of the message wake-up.

[0080] In one optional implementation of this application embodiment, the determining module 420 is further configured to: Based on the identification information of the message wake-up, the type of the message wake-up is determined from the mapping relationship between the identification information and the type.

[0081] In one optional implementation of this application embodiment, the wake-up module 440 is specifically used for: In response to the wake-up source being a local event wake-up, a sleep wake-up operation is performed.

[0082] In one optional implementation of this application embodiment, the wake-up module 440 is specifically used for: In response to a network management message being the type of the wake-up message, a sleep wake-up operation is performed.

[0083] It should be understood that the sleep / wake-up device embodiments and the aforementioned sleep / wake-up method embodiments can correspond to each other, and similar descriptions can be found in the first aspect of the method embodiments. To avoid repetition, further details are omitted here. Specifically, Figure 4 The device 400 shown can perform Figure 1 The corresponding method embodiments, and the foregoing and other operations and / or functions of each module in device 400 are respectively implemented to achieve Figure 1 For the sake of brevity, the corresponding processes in each method are not described in detail here.

[0084] The apparatus 400 of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the first aspect method embodiment in this application can be completed by integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the first aspect method disclosed in this application embodiment can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the first aspect method embodiment described above.

[0085] Figure 5 This is a schematic block diagram of an electronic device provided as an embodiment of this application. Figure 5 As shown, the electronic device 500 may include a memory 510 and a processor 520. The memory 510 stores computer programs and transmits the program code to the processor 520. In other words, the processor 520 can call and run the computer program from the memory 510 to implement the sleep-wake method described in any one of the embodiments of this application.

[0086] For example, the processor 520 can be used to execute the sleep-wake method described in any one of the embodiments of this application according to the instructions in the computer program.

[0087] In some alternative embodiments, the above-described sleep-wake method includes: In response to a detected wake-up event, identify the type of wake-up source; In response to the wake-up source being a message wake-up, the type of the message wake-up is determined; In response to the message wake-up type being an application message, the system enters a preset state; In response to the detection of a transition edge change on the wake-up source pin corresponding to the application message within a preset time period during the preset state, a sleep wake-up operation is performed.

[0088] In some alternative embodiments, the method further includes: In response to the fact that no edge transition is detected on the wake-up source pin corresponding to the application message during the preset state, the device re-enters the sleep state.

[0089] In some alternative embodiments, identifying the type of wake-up source in response to a detected wake-up event includes: In response to a detected wake-up event, the network management message corresponding to the wake-up event is obtained; The type of the wake-up source is identified based on preset bytes in the network management message.

[0090] In some optional embodiments, the response to the wake-up source being of type message wake-up, determining the type of message wake-up includes: In response to the wake-up source being a message wake-up, the identifier information of the message wake-up is obtained; The type of message wake-up is determined based on the identifier information of the message wake-up.

[0091] In some optional embodiments, determining the type of message wake-up based on the message wake-up identification information includes: Based on the identification information of the message wake-up, the type of the message wake-up is determined from the mapping relationship between the identification information and the type.

[0092] In some alternative embodiments, the method further includes: In response to the wake-up source being a local event wake-up, a sleep wake-up operation is performed.

[0093] In some alternative embodiments, the method further includes: In response to a network management message being the type of the wake-up message, a sleep wake-up operation is performed.

[0094] In some embodiments of this application, the processor 520 may include, but is not limited to: General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0095] In some embodiments of this application, the memory 510 includes, but is not limited to: Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0096] In some embodiments of this application, the computer program may be divided into one or more modules, which are stored in the memory 510 and executed by the processor 520 to complete the sleep-wake method described in any one embodiment of this application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the area controller.

[0097] like Figure 5 As shown, the electronic device 500 may further include: Transceiver 530, which can be connected to processor 520 or memory 510.

[0098] The processor 520 can control the transceiver 530 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include antennas, and the number of antennas may be one or more.

[0099] It should be understood that the various components in the area controller are connected through a bus system, which includes not only a data bus, but also a power bus, a control bus, and a status signal bus.

[0100] Figure 6 This is a schematic block diagram of a vehicle provided as an embodiment of this application. Figure 6 As shown, the vehicle 600 may include: electronic device 500 as described in the embodiments of this application. This application detachably mounts the electronic device on the vehicle for ease of installation and maintenance. The vehicle including the aforementioned electronic device can identify the type of wake-up source in response to a detected wake-up event. If the wake-up source type is message wake-up, the type of message wake-up is determined. If the message wake-up type is application message, a preset state is entered. Furthermore, if a transition edge is detected on the wake-up source pin corresponding to the application message within a preset time while in the preset state, a sleep wake-up operation is performed. This avoids repeated false wake-ups of the area controller by application messages sent by other controllers, thereby reducing current consumption, reducing high-voltage power replenishment cycles, and significantly reducing the overall vehicle static power consumption.

[0101] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a computer, enables the computer to perform the sleep-wake method described in any one of the embodiments of this application.

[0102] This application also provides a computer program product containing program instructions that, when run on an electronic device, cause the electronic device to execute the sleep-wake method described in any one of the embodiments of this application.

[0103] When implemented using software, it can be implemented entirely or partially as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0104] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0105] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0106] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into a first processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0107] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0108] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for waking up from hibernation, characterized in that, Applied to a region controller, the method includes: In response to a detected wake-up event, identify the type of wake-up source; In response to the wake-up source being a message wake-up, the type of the message wake-up is determined; In response to the message wake-up type being an application message, the system enters a preset state; In response to the detection of a transition edge change on the wake-up source pin corresponding to the application message within a preset time period during the preset state, a sleep wake-up operation is performed.

2. The method according to claim 1, characterized in that, The method further includes: In response to the fact that no edge transition is detected on the wake-up source pin corresponding to the application message during the preset state, the device re-enters the sleep state.

3. The method according to claim 1, characterized in that, The process of identifying the type of wake-up source in response to a detected wake-up event includes: In response to a detected wake-up event, the network management message corresponding to the wake-up event is obtained; The type of the wake-up source is identified based on preset bytes in the network management message.

4. The method according to claim 1, characterized in that, The response to the wake-up source being of type message wake-up, determining the type of message wake-up includes: In response to the wake-up source being a message wake-up, the identifier information of the message wake-up is obtained; The type of message wake-up is determined based on the identifier information of the message wake-up.

5. The method according to claim 4, characterized in that, Determining the type of message wake-up based on the message wake-up identifier information includes: Based on the identification information of the message wake-up, the type of the message wake-up is determined from the mapping relationship between the identification information and the type.

6. The method according to claim 1, characterized in that, The method further includes: In response to a network management message being the type of the wake-up message, a sleep wake-up operation is performed.

7. A sleep / wake-up device, characterized in that, Configured on the area controller, including: The identification module is used to identify the type of wake-up source in response to a detected wake-up event; The determination module is configured to determine the type of wake-up message in response to the wake-up source being a message wake-up message. The first processing module is configured to enter a preset state in response to the wake-up message being an application message. The wake-up module is used to perform a sleep-wake-up operation in response to a change in the edge of the wake-up source pin corresponding to the application message within a preset time during the preset state.

8. An electronic device, characterized in that, include: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to perform the method as described in any one of claims 1 to 6.

9. A vehicle, characterized in that, include: The electronic device as described in claim 8.

10. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as described in any one of claims 1 to 6.

Images