A hibernation wakeup method, system and apparatus

By converting and mapping the sleep/wake signals of different vehicle models, flexible sleep/wake control in the communication computing architecture is realized using a wake-up source parser, policy controller, and actuator. This solves the problems of high power consumption and difficulty in anomaly localization in the vehicle, and improves the efficiency of sleep/wake in the vehicle.

CN116634531BActive Publication Date: 2025-12-09YINWANG INTELLIGENT TECHNOLOGIES CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210125226.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-02-10
Publication Date
2025-12-09
Estimated Expiration
2042-02-10

AI Technical Summary

Technical Problem

Existing sleep/wake-up solutions are not applicable to communication and computing architectures, resulting in high vehicle power consumption and difficulty in locating network node anomalies. They also fail to meet the sleep/wake-up scenarios of multiple central gateways and the mutual influence between CGWs.

Method used

By converting the sleep/wake signals of different vehicle models into a unified sleep/wake signal and determining the static control target based on the mapping relationship, the sleep/wake control of the vehicle integrated unit is realized by using a wake-up source parser, a wake-up strategy controller, and a wake-up actuator.

Benefits of technology

It enables flexible sleep/wake-up control in the communication computing architecture, reducing overall vehicle power consumption and improving the efficiency of anomaly localization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116634531B_ABST
    Figure CN116634531B_ABST
Patent Text Reader

Abstract

The application relates to a hibernation wake-up method, system and device, the method comprising converting a first hibernation wake-up signal generated in a vehicle network of a first vehicle model into a second unified hibernation wake-up signal converted from a hibernation wake-up signal with the same function generated in a vehicle network of a different vehicle model; determining a static control target for representing the function of the first hibernation wake-up signal based on the second hibernation wake-up signal; determining a hibernation wake-up action for waking up or controlling at least one vehicle-mounted object in at least one vehicle integrated unit to hibernate based on the static control target; and executing at least one hibernation wake-up action. The hibernation wake-up method, system and device provided in the application embodiment can realize hibernation wake-up control based on a communication computing architecture.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the field of intelligent vehicles, and in particular to a hibernation wake-up method, system and device. BACKGROUND

[0002] With the rapid development of intelligent and networked vehicles, the substantial increase in vehicle information and the demand for vehicle intelligence have jointly driven the upgrade and evolution of vehicle electronic and electrical architecture. From the perspective of electronic control units (ECUs), the vehicle electrical and electronic (E / E) architecture has undergone three generations of evolution.

[0003] The first generation is a distributed electronic and electrical architecture, in which one function corresponds to one ECU. The second generation is a centralized electronic and electrical architecture, in which the original single-function ECUs are integrated in a controller according to functional categories, for example, ECUs are integrated in the power domain, chassis domain, body domain, driving domain, and cockpit domain. The third generation is a central centralized electronic and electrical architecture, which further centralizes the functional domains to form one or more central computing units, and further centralizes the functional domains in the second generation to form regional controllers. The central centralized electronic and electrical architecture can also be referred to as a communication and computation architecture (CCA).

[0004] In related technologies, the hibernation wake-up scheme adopted in the distributed electronic and electrical architecture is that when a certain function is activated in the vehicle hibernation state, the vehicle network needs to be awakened; only when all network nodes meet the hibernation conditions, the vehicle network can hibernate. This hibernation wake-up scheme affects the power consumption of the vehicle, and reduces the vehicle stationary storage period. At the same time, in this hibernation wake-up scheme, each network node affects each other, and once an abnormal factor such as software bug or hardware failure causes the network node to fail to hibernate normally, it is difficult to locate.

[0005] In related technologies, the hibernation wake-up scheme adopted in the centralized electronic and electrical architecture is that the hibernation wake-up requirements of different ECUs in the central gateway (CGW) are the judgment conditions, and different network segments are independently hibernated or awakened. Figure 1 An exemplary network topology diagram of the centralized electronic and electrical architecture is shown. As Figure 1As shown, the CGW of the centralized electronic and electrical architecture is connected with three CANs, CAN1, CAN2 and CAN3. The CAN1 is connected with three ECUs, ECU1, ECU2 and ECU3. The CAN2 is connected with three ECUs, ECU4, ECU5 and ECU6. The CAN3 is connected with three ECUs, ECU7, ECU8 and ECU9. When the CGW detects that the ECU1 on the CAN1 is woken up in the sleep state of the vehicle, it is determined whether there is an associated ECU on the CAN2 that has functional interaction with the ECU1. If there is an associated ECU, the CGW wakes up the CAN2 and the associated ECU on the CAN2. When the CGW determines that all ECUs in the CAN1 send sleep requests and all associated ECUs of the ECUs in the CAN1 also send sleep requests, the CAN1 is controlled to sleep. This sleep and wake-up scheme does not consider the sleep and wake-up scenarios of multiple CGWs and the mutual influence between CGWs in the sleep and wake-up process. Meanwhile, this sleep and wake-up scheme does not consider the sleep and wake-up of Ethernet, LIN and hardwire.

[0006] Since the ECUs in the communication computing architecture interact through multiple VIUs, the above sleep and wake-up schemes are not applicable to the communication computing architecture. Considering that a large number of in-vehicle electronic and electrical architectures have been changed from the distributed electronic and electrical architecture and the centralized electronic and electrical architecture to the communication computing architecture, how to realize sleep and wake-up control in the communication computing architecture has become a problem to be solved. SUMMARY

[0007] Therefore, a sleep and wake-up method, system and device are provided, which can realize sleep and wake-up control based on the communication computing architecture.

[0008] In a first aspect, an embodiment of the present application provides a sleep and wake-up method, which comprises:

[0009] converting at least one first sleep and wake-up signal into at least one second sleep and wake-up signal, the first sleep and wake-up signal being used to represent a sleep and wake-up signal generated in a vehicle network of a first vehicle model, and the second sleep and wake-up signal being used to represent a unified sleep and wake-up signal converted from a sleep and wake-up signal with the same function generated in a vehicle network of a different vehicle model;

[0010] determine at least one static control target based on the at least one second sleep wake-up signal, the static control target being used to represent a function of the first sleep wake-up signal;

[0011] determine at least one sleep wake-up action based on the at least one static control target, the sleep wake-up action being used to wake up or control to sleep at least one vehicle-mounted object in at least one integrated vehicle unit;

[0012] execute the at least one sleep wake-up action.

[0013] In a possible implementation, the converting of the at least one first sleep wake-up signal into the at least one second sleep wake-up signal comprises:

[0014] For any one of the at least one first sleep wake-up signal, determine a second sleep wake-up signal corresponding to the first sleep wake-up signal based on a first mapping relationship, the first mapping relationship being used to represent a mapping relationship between a sleep wake-up signal generated in a vehicle-mounted network of a first vehicle model and a unified sleep wake-up signal.

[0015] In a possible implementation, the determining of the at least one static control target based on the at least one second sleep wake-up signal comprises:

[0016] For any one of the at least one second sleep wake-up signal, determine a static control target corresponding to the second sleep wake-up signal based on a second mapping relationship, the second mapping relationship being used to represent a mapping relationship between the unified sleep wake-up signal and a vehicle-mounted object;

[0017] merge the static control targets corresponding to the second sleep wake-up signals to obtain the at least one static control target.

[0018] In a possible implementation, the determining of the at least one sleep wake-up action based on the at least one static control target comprises:

[0019] For any one of the at least one static control target, determine at least one integrated vehicle unit corresponding to the static control target and a vehicle-mounted object in each determined integrated vehicle unit that needs to be controlled to sleep wake up based on a third mapping relationship, the third mapping relationship being used to represent a mapping relationship between a static control target and an integrated vehicle unit and a vehicle-mounted object that needs to be controlled to sleep wake up;

[0020] determine the at least one sleep wake-up action according to whether the vehicle-mounted object that needs to be controlled to sleep wake up is currently in a wake-up state or a sleep state.

[0021] In a possible implementation, the first hibernation wake-up signal comprises a first signal for waking up the vehicle-mounted object, and / or a second signal for controlling the vehicle-mounted object to hibernate, and the method further comprises:

[0022] In a case where the network management packet is received, or the service packet is received, or the first level change is detected, it is determined that the first signal is obtained;

[0023] In a case where the network management packet is not received within the preset time, or the service packet is not received, or the second level change is detected, it is determined that the second signal is obtained.

[0024] In a second aspect, embodiments of the present application provide a hibernation wake-up system, comprising: a wake-up source analyzer, a wake-up strategy controller, and a wake-up executor;

[0025] The wake-up source analyzer is configured to convert at least one first hibernation wake-up signal into at least one second hibernation wake-up signal, and send the at least one second hibernation wake-up signal to the wake-up strategy controller, wherein the first hibernation wake-up signal is used to represent a hibernation wake-up signal generated in a vehicle-mounted network of a first vehicle model, and the second hibernation wake-up signal is used to represent a unified hibernation wake-up signal converted from a hibernation wake-up signal with the same function generated in a vehicle-mounted network of a different vehicle model;

[0026] The wake-up strategy controller is configured to determine at least one static control target based on the at least one second hibernation wake-up signal, and send the at least one static control target to the wake-up executor, wherein the static control target is used to represent a function of the first hibernation wake-up signal;

[0027] The wake-up executor is configured to determine at least one hibernation wake-up action based on the at least one static control target, and execute the at least one hibernation wake-up action, wherein the hibernation wake-up action is used to wake up or control at least one vehicle-mounted object in at least one vehicle integrated unit to hibernate.

[0028] In a possible implementation, the wake-up source analyzer and the wake-up executor are deployed in the vehicle integrated unit, and the wake-up strategy controller is deployed in a domain controller.

[0029] In a possible implementation, the wake-up source analyzer, the wake-up strategy controller, and the wake-up executor are deployed in the vehicle integrated unit.

[0030] In a possible implementation, the wake-up strategy controller comprises a distributed wake-up strategy controller and a centralized wake-up strategy controller, the wake-up source resolver, the wake-up executor and the distributed wake-up strategy controller are deployed in a vehicle integrated unit, and the centralized wake-up strategy controller is deployed in a domain controller.

[0031] In a possible implementation, the wake-up source resolver is further configured to:

[0032] For any one of the at least one first sleep wake-up signal, a second sleep wake-up signal corresponding to the first sleep wake-up signal is determined based on a first mapping relationship, and the first mapping relationship is used to represent a mapping relationship between a sleep wake-up signal generated in a vehicle network of a first vehicle model and a unified sleep wake-up signal.

[0033] In a possible implementation, the wake-up strategy controller is further configured to:

[0034] For any one of the at least one second sleep wake-up signal, a static control target corresponding to the second sleep wake-up signal is determined based on a second mapping relationship, and the second mapping relationship is used to represent a mapping relationship between a unified sleep wake-up signal and a vehicle object;

[0035] The static control targets corresponding to the second sleep wake-up signals are merged to obtain the at least one static control target.

[0036] In a possible implementation, the wake-up executor is further configured to:

[0037] For any one of the at least one static control target, at least one vehicle integrated unit corresponding to the static control target and a vehicle object needing sleep wake-up control in each determined vehicle integrated unit are determined based on a third mapping relationship, and the third mapping relationship is used to represent a mapping relationship between a static control target and a vehicle integrated unit and a vehicle object needing sleep wake-up control;

[0038] The at least one sleep wake-up action is determined according to whether the vehicle object needing sleep wake-up control is currently in a wake-up state or a sleep state.

[0039] In a possible implementation, the first sleep wake-up signal comprises a first signal for waking up a vehicle object and / or a second signal for controlling a vehicle object to sleep, and the sleep wake-up system further comprises a wake-up source.

[0040] The wake-up source is configured to determine that the first signal is obtained in a case that a network management packet is received, or a service packet is received, or a first level change is detected; and determine that the second signal is obtained in a case that no network management packet is received, or no service packet is received, or a second level change is detected within a preset time.

[0041] In a third aspect, embodiments of the present application provide a hibernation wake-up device, the device comprising:

[0042] A conversion module is configured to convert at least one first hibernation wake-up signal into at least one second hibernation wake-up signal, the first hibernation wake-up signal being used to represent a hibernation wake-up signal generated in a vehicle network of a first vehicle model, and the second hibernation wake-up signal being used to represent a unified hibernation wake-up signal converted from a hibernation wake-up signal of the same function generated in a vehicle network of a different vehicle model;

[0043] A first determination module is configured to determine at least one static control target based on the at least one second hibernation wake-up signal, the static control target being used to represent a function of the first hibernation wake-up signal;

[0044] A second determination module is configured to determine at least one hibernation wake-up action based on the at least one static control target, the hibernation wake-up action being used to wake up or control at least one vehicle-mounted object in at least one vehicle integrated unit to hibernate;

[0045] An execution module is configured to execute the at least one hibernation wake-up action.

[0046] In a possible implementation, the conversion module is further configured to:

[0047] For any one of the at least one first hibernation wake-up signal, a second hibernation wake-up signal corresponding to the first hibernation wake-up signal is determined based on a first mapping relationship, the first mapping relationship being used to represent a mapping relationship between a hibernation wake-up signal generated in a vehicle network of a first vehicle model and a unified hibernation wake-up signal.

[0048] In a possible implementation, the first determination module is further configured to:

[0049] For any one of the at least one second hibernation wake-up signal, a static control target corresponding to the second hibernation wake-up signal is determined based on a second mapping relationship, the second mapping relationship being used to represent a mapping relationship between a unified hibernation wake-up signal and a vehicle-mounted object;

[0050] The static control targets corresponding to the second sleep-wakeup signals are merged to obtain the at least one static control target.

[0051] In a possible implementation, the second determining module is further configured to:

[0052] For any one of the at least one static control target, at least one vehicle integrated unit corresponding to the static control target is determined based on a third mapping relationship, and a vehicle-mounted object that needs to be controlled to sleep and wake up in each determined vehicle integrated unit is determined, the third mapping relationship being used to represent a mapping relationship between a static control target and a vehicle integrated unit and a vehicle-mounted object that needs to be controlled to sleep and wake up.

[0053] The at least one sleep-wakeup action is determined according to whether the vehicle-mounted object that needs to be controlled to sleep and wake up is currently in a wake-up state or a sleep state.

[0054] In a possible implementation, the first sleep-wakeup signal includes a first signal used to wake up a vehicle-mounted object, and / or a second signal used to control a vehicle-mounted object to sleep, and the apparatus further includes:

[0055] The third determining module is configured to determine that the first signal is obtained in a case where a network management packet is received, or a service packet is received, or a first level change is detected.

[0056] The fourth determining module is configured to determine that the second signal is obtained in a case where a network management packet is not received, or a service packet is not received, or a second level change is detected within a preset time.

[0057] In a fourth aspect, an embodiment of the present application provides a sleep-wakeup apparatus, which can execute the sleep-wakeup method in the first aspect or one or more of the possible implementation manners of the first aspect.

[0058] In a fifth aspect, an embodiment of the present application provides a computer program product, including computer readable code or a nonvolatile computer readable storage medium carrying computer readable code, when the computer readable code is run in an electronic device, a processor in the electronic device executes the sleep-wakeup method in the first aspect or one or more of the possible implementation manners of the first aspect.

[0059] In the embodiments of the present application, sleep-wakeup signals generated by vehicle-mounted networks of different vehicle models can be converted into unified sleep-wakeup signals, and unified static control targets are obtained, and then vehicle-mounted objects in vehicle integrated units are woken up or put to sleep, and sleep-wakeup control in a communication computing architecture is realized by means of software.

[0060] These and other aspects of this application will become more apparent in the description of the following embodiments(s). Attached Figure Description

[0061] The accompanying drawings, which are included in and form part of this specification, illustrate exemplary embodiments, features, and aspects of this application together with the specification and serve to explain the principles of this application.

[0062] Figure 1 An exemplary network topology diagram of a centralized electronic and electrical architecture is shown;

[0063] Figures 2 to 4 The diagrams show exemplary network topologies of ring networks in a communication computing architecture.

[0064] Figure 5 and Figure 6 Exemplary network topologies for star-shaped communication computing architectures are shown below;

[0065] Figure 7 This diagram illustrates the architecture of the sleep / wake-up system provided in an embodiment of this application.

[0066] Figure 8 This document illustrates a flowchart of the sleep / wake-up method provided in an embodiment of this application.

[0067] Figure 9 An exemplary schematic diagram of the network topology of the communication computing architecture is shown;

[0068] Figure 10 The interactive flowchart of the sleep-wake method provided in the embodiments of this application is shown;

[0069] Figure 11 A schematic diagram of the deployment of the wake-up and hibernation system provided in an embodiment of this application is shown;

[0070] Figure 12 The interactive flowchart of the sleep-wake method provided in the embodiments of this application is shown;

[0071] Figure 13 A schematic diagram of the deployment of the wake-up and hibernation system provided in an embodiment of this application is shown;

[0072] Figure 14 The interactive flowchart of the sleep-wake method provided in the embodiments of this application is shown;

[0073] Figure 15 A schematic diagram of the deployment of the wake-up and hibernation system provided in an embodiment of this application is shown;

[0074] Figure 16 The interactive flowchart of the sleep-wake method provided in the embodiments of this application is shown;

[0075] Figure 17 Fig. 1 shows a structure schematic diagram of a hibernation wakeup device provided by an embodiment of the present application;

[0076] Figure 18 Fig. 1 shows a structure schematic diagram of a hibernation wakeup device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0077] Various exemplary embodiments, features, and aspects of the present application will be described in detail hereinafter with reference to the drawings. The same reference numbers in the drawings represent the same or similar elements. Although various aspects of the embodiments are illustrated in the drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

[0078] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations.

[0079] In addition, for the purpose of convenience and brevity, detailed descriptions of well-known functions and structures incorporated in the present application can not be described in detail herein. It should be appreciated that those skilled in the art can appreciate the embodiments of the present application without undue efforts and experimentation once given the overall conceptual framework.

[0080] In the communication computing architecture, ECUs of the vehicle are distributed into multiple areas, and one VIU is deployed in each area to manage the ECUs in the area. The VIUs are interconnected through high-speed Ethernet to complete high-speed communication of the whole vehicle. In the embodiments of the present application, the VIU can have one or more of the following multiple functions: electronic control function, i.e., the VIU is used to implement part or all of the electronic control functions provided by the ECUs inside the vehicle parts; the same function as the gateway, i.e., the VIU can also have part or all of the same functions as the gateway, such as protocol conversion function, protocol encapsulation and forwarding function, and data format conversion function; processing function of data across vehicle parts, i.e., processing, calculation, etc. of data obtained from actuators of multiple vehicle parts. It should be noted that the above are only exemplary examples of the VIU function, and are not intended to limit the VIU, and the VIU can have more or less functions than the above.

[0081] In the communication computing architecture, there is an independent domain controller (DC) in each functional domain of the vehicle. For example, the DC in the vehicle can include an automatic driving domain controller (ADAS\AD Domain Controller, ADC), a cockpit domain controller (Cockpit Domain Controller, CDC), a vehicle domain controller (Vehicle Domain Controller, VDC), etc.

[0082] Among them, the ADC can be used to provide services for vehicle parts that implement automatic driving functions, including monocular camera, binocular camera, millimeter wave radar, laser radar, ultrasonic radar, etc. It should be noted that the function of the ADC can be implemented by a mobile data center (Mobile Data Center, MDC). The CDC can be used to provide services for vehicle parts in the cockpit domain. The vehicle parts in the cockpit domain include head-up display (Head-Up Display, HUD), instrument display, radio, navigation, camera, etc. The VDC can be used to provide services for vehicle parts in the body domain and vehicle parts in the chassis domain. Among them, the vehicle parts in the body domain include door and window lifting controller, power rearview mirror, air conditioner, central door lock, etc. The vehicle parts in the chassis domain include vehicle parts in the braking system, vehicle parts in the steering system, vehicle parts in the acceleration system, such as throttle, etc.

[0083] In the embodiment of the present application, the VDC, MDC and CDC can be logically fused as needed. In one example, the VDC and MDC are fused, that is, the vehicle control business and the automatic driving business are fused, while the CDC is retained. In another example, the MDC and CDC are fused, that is, the automatic driving and entertainment control modules are fused, while the VDC is retained. In another example, the VDC and CDC are fused, that is, the vehicle control business and the entertainment control module are fused, while the MDC is retained. In another example, the VDC, MDC and CDC are fused, that is, the vehicle control business and the automatic driving business are fused. At this time, the architecture integrates the VDC, MDC and CDC into a central computer. The correspondence between functions and elements no longer exists, and the central computer commands the VIU as needed. In the embodiment of the present application, in order to simplify the description and facilitate understanding, in the embodiment of the present application, the VDC, MDC, CDC, or the components obtained by the fusion of two or three of them can be replaced by the xDC.

[0084] Considering the needs of different vehicle models, the communication computing architecture can support different forms of networking of VIU and xDC, such as ring networking and star networking, etc. Figures 2 to 4FIG. 1 shows an exemplary network topology diagram of a ring networking of a communication computing architecture. Figure 5 and Figure 6 FIG. 2 shows an exemplary network topology diagram of a star networking of a communication computing architecture. Figures 2 to 6 The VIU1, VIU2, VIU3 and VIU4 involved in FIG. 1 are VIUs, and the functions of the VIU, VDC, MDC and CDC are as described above, which will not be repeated here. It can be understood that, Figures 2 to 6 The communication computing architecture shown in FIG. 1 is only an example of the communication computing architecture and is not intended to limit the communication computing architecture. The communication computing architecture can further include more or less VIUs, and can have other networking forms, which will not be repeated here.

[0085] The signal-oriented communication mode is the traditional interaction mode of vehicles. The ECUs perform point-to-point data transmission through CAN and LIN buses. The communication mode is determined when the vehicle is manufactured. When the vehicle architecture evolves into a communication computing architecture, most of the computing power is concentrated in the VDC. The interaction between software and hardware in the vehicle is no longer point-to-point, and there is a lot of collaboration between hardware. Any adjustment will involve the entire network, which brings inconvenience to updating. The signal-oriented communication mode is already unable to meet the communication computing architecture.

[0086] The Service-Oriented Architecture (SOA) effectively solves the coupling problem between software and hardware, and is a software architecture that adapts to the centralization evolution of electronic and electrical architecture. Under the concept of SOA, when the vehicle needs to implement a certain function, the relevant service A "subscribes" the service B. After receiving the subscription information, service A "pushes" the service to service B, and then the relevant service executes the function. SOA services the software, and the upgrade and adjustment of the service will not affect the entire network, thereby improving the functionality of the vehicle. Different services can call different software combinations, and different service combinations can also execute different functions, greatly enhancing the reusability of the software.

[0087] In the communication computing architecture, the VIU and xDC constitute the core network of the vehicle network, while the CAN, Ethernet, LIN, and General-Purpose Input / Output (GPIO) connections under the VIU constitute the access network of the vehicle network. In this embodiment, to maintain compatibility with existing ECUs, the CAN and LIN sleep / wake-up methods from related technologies are still used for the access network; however, to ensure the flexibility of the sleep / wake-up scheme, the wake-up sleep method provided in this embodiment is used for the core network. The sleep / wake-up scheme provided in this embodiment can simplify the development for vehicle manufacturers and maximize the platformization of the sleep / wake-up scheme. The sleep / wake-up scheme provided in this embodiment can be loaded into the vehicle equipment in software form (early or later) and sold.

[0088] Figure 7 This diagram illustrates the architecture of a sleep / wake-up system provided in an embodiment of this application. Figure 7 As shown, the sleep-wake system includes a wake-up source resolver 11, a wake-up policy controller 12, and a wake-up executor 13.

[0089] The wake-up source resolver 11 can be used to convert at least one first sleep wake-up signal into at least one second sleep wake-up signal. The first sleep wake-up signal can represent a sleep wake-up signal generated in the vehicle network of a first vehicle model, where "first vehicle model" can represent any vehicle model. It is understood that functionally identical sleep wake-up signals generated in the vehicle networks of different vehicle models are different. For example, the vehicle network of vehicle model A (i.e., the first vehicle model) achieves full wake-up of the vehicle's low-voltage power supply through a high-level PIN input (i.e., a sleep wake-up signal generated in the vehicle network of vehicle model A); the vehicle network of vehicle model B (i.e., the first vehicle model) achieves full wake-up of the vehicle's low-voltage power supply through a CAN message with KeyON=1 (i.e., a sleep wake-up signal generated in the vehicle network of vehicle model B). The second sleep wake-up signal can be used to represent a unified sleep wake-up signal converted from functionally identical sleep wake-up signals generated in the vehicle networks of different vehicle models. For example, the wake-up source resolver 11 can convert the aforementioned high-level PIN input into "KL15=1", and can also convert the aforementioned CAN message with KeyON=1 into "KL15=1". Therefore, the first sleep / wake-up signals generated by the in-vehicle networks of different vehicle models have the same function and can be converted into a unified sleep / wake-up signal after being parsed by the wake-up source parser 11.

[0090] In one example, the first sleep wake-up signal includes, but is not limited to, a CAN message, an Ethernet interface message, a LIN interface message, a General-Purpose Input / Output (GPIO) message, and the like. The message includes, but is not limited to, a network management message, a service message, and the like. The type of the message is not limited in the embodiments of the present application.

[0091] In one possible implementation, the first sleep wake-up signal includes a first signal for waking up the in-vehicle object and / or a second signal for controlling the in-vehicle object to sleep. The wake-up source analyzer 11 can determine that the first signal is obtained when a network management message is received, or a service message is received, or a first level change is detected. The wake-up source analyzer 11 can determine that the second signal is obtained when a network management message is not received within a preset time, or a service message is not received within the preset time, or a second level change is detected. The preset time can be set as needed, for example, 30 seconds or 1 minute, and the like. The present application is not limited in this regard.

[0092] The first level change can represent a level change for waking up the in-vehicle object, and the second level change can represent a level change for controlling the in-vehicle object to sleep. The first level change can be from low to high, or from high to low. The second level change can be from low to high, or from high to low. In the embodiments of the present application, it can be pre-set which interfaces or lines on which a change from low to high is detected as the first level change, which interfaces or lines on which a change from low to high is detected as the second level change, which interfaces or lines on which a change from high to low is detected as the first level change, and which interfaces or lines on which a change from high to low is detected as the second level change. In this way, when the wake-up source analyzer 11 detects a level change (from low to high, or from high to low) on an interface or a line, it can determine whether the level change is the first level change or the second level change according to the pre-set content, and further determine whether the first signal or the second signal is obtained.

[0093] As shown in FIG. 6, when the external wake-up source (for example, CAN, LIN, Ethernet interface, GPIO, and the like) starts to send a network management message, a service message, or stops sending a network management message, a service message, the wake-up source analyzer 11 receives the N first sleep wake-up signals collected. The wake-up source analyzer 11 converts the N first sleep wake-up signals to obtain N second sleep wake-up signals. N is an integer greater than or equal to 1, and N represents the number of the first sleep wake-up signals. Figure 7 As shown in FIG. 6, when the external wake-up source (for example, CAN, LIN, Ethernet interface, GPIO, and the like) starts to send a network management message, a service message, or stops sending a network management message, a service message, the wake-up source analyzer 11 receives the N first sleep wake-up signals collected. The wake-up source analyzer 11 converts the N first sleep wake-up signals to obtain N second sleep wake-up signals. N is an integer greater than or equal to 1, and N represents the number of the first sleep wake-up signals.

[0094] The wake-up source resolver 11 can send at least one second sleep wake-up signal to the wake-up policy controller 12. The sending method can be CANNM message, CAN application message, UDPNM message, or a custom message based on the IP protocol stack and a combination thereof. In this embodiment, there is no restriction on the way the wake-up source resolver 11 sends the second sleep wake-up signal to the wake-up policy controller 12.

[0095] The wake-up strategy controller 12 can be used to determine at least one static control target (or sleep-wake mode, wake-up mode, sleep mode, etc.) based on at least one second sleep-wake signal. The static control target can represent the function of the first sleep-wake signal. Here, the static control target includes a static wake-up target to be woken up, and / or a static sleep target to be put into sleep mode. For example, the static control target can be a CAN network segment, LIN network segment, Ethernet segment, or ECU combination required for DC charging, Bluetooth key unlocking wake-up, or vehicle wake-up, or a sleep mode for a specific CAN network segment, LIN network segment, Ethernet segment, or ECU combination.

[0096] like Figure 7 As shown, after receiving N second sleep wake-up signals, the wake-up decision controller 12 outputs M static control targets. Here, M is an integer greater than or equal to 1, representing the number of static control targets. It is understandable that although each second sleep wake-up signal corresponds to one static control target, considering that some static control targets can be merged, the number of static control targets output by the wake-up decision controller 12 may differ from the number of received second sleep wake-up signals. For example, if second sleep wake-up signal A corresponds to static control target A, second sleep wake-up signal B corresponds to static control target B, and second sleep wake-up signal C corresponds to static control target C, then the final static control target output by the wake-up decision controller 12 is the union of static control targets A, B, and C. If static control targets A, B, and C can be merged, the final output of the wake-up decision controller 12 needs to be merged to avoid unnecessary processing by the wake-up actuator 13. For example, if static control target A is CAN1 wake-up, static control target B is CAN2 wake-up, and static control target C is vehicle wake-up, then the wake-up decision controller 12 only needs to output vehicle wake-up, and does not need to output CAN1 wake-up, CAN2 wake-up and vehicle wake-up.

[0097] The wake-up decision controller 12 can send the at least one static control target to the wake-up executor 13. The sending manner can be a CANNM message, a CAN application message, a UDPNM message, or a self-defined IP protocol stack-based message, or a combination thereof, and the wake-up decision controller 12 is not limited to the manner of sending the static control target to the wake-up executor 13 in the embodiments of the present application. In a possible implementation manner, the wake-up decision controller 12 can send the static control target to the wake-up executor 13 in a unicast or broadcast manner.

[0098] The wake-up executor 13 can be configured to determine at least one sleep wake-up action based on the at least one static control target. The sleep wake-up action can be used to wake up at least one vehicle-mounted object (for example, CAN, LIN, ECU, etc.) in at least one vehicle integrated unit (VIU), or control at least one vehicle-mounted object in at least one vehicle integrated unit to sleep. In a case where the first sleep wake-up signal is a first signal, the sleep wake-up action obtained based on the first sleep wake-up signal can be used to wake up at least one vehicle-mounted object in at least one vehicle integrated unit; in a case where the first sleep wake-up signal is a second signal, the sleep wake-up action obtained based on the first sleep wake-up signal can be used to control at least one vehicle-mounted object in at least one vehicle integrated unit to sleep.

[0099] The wake-up executor 13 can execute the determined at least one sleep wake-up action. In an example, the execution of the sleep wake-up action includes but is not limited to sending a CAN NM to an ECU, and waking up the ECU through a specific interface.

[0100] The sleep wake-up system provided by the embodiments of the present application can be applied to intelligent vehicles, new energy vehicles, or traditional vehicles, etc. The new energy vehicles include pure electric vehicles, extended-range electric vehicles, hybrid vehicles, fuel cell vehicles, and other new energy vehicles. The traditional vehicles include gasoline vehicles and diesel vehicles.

[0101] The sleep wake-up system provided by the embodiments of the present application can convert the sleep wake-up signals generated by the vehicle-mounted networks of different vehicle models into unified sleep wake-up signals, and obtain unified static control targets, and then wake up or sleep the vehicle-mounted objects in the vehicle integrated unit, thereby realizing sleep wake-up control in the communication computing architecture through software.

[0102] Figure 8 A flowchart of a sleep wake-up method provided by the embodiments of the present application is shown. The method can be applied to a sleep wake-up system, for example Figure 7 The sleep wake-up system shown. As Figure 8 The method can include:

[0103] Step S201, converting the at least one first sleep wake-up signal into at least one second sleep wake-up signal.

[0104] The first sleep wake-up signal is used to represent a sleep wake-up signal generated in a vehicle network of a first vehicle model, and the second sleep wake-up signal is used to represent a unified sleep wake-up signal converted from a sleep wake-up signal with the same function generated in a vehicle network of a different vehicle model.

[0105] In one example, the first sleep wake-up signal can include a first signal used to wake up a vehicle-mounted object. In a case where a network management packet is received, or a service packet is received, or a first level change is detected, the sleep wake-up system can determine that the first signal is obtained. In a case where the sleep wake-up system determines that the first signal is obtained, it indicates that one or more vehicle-mounted objects in one or more vehicle integrated units need to be woken up.

[0106] In another example, the first sleep wake-up signal can include a second signal used to control a vehicle-mounted object to sleep. In a case where a network management packet is not received within a preset time, or a service packet is not received, or a second level change is detected, the sleep wake-up system determines that the second signal is obtained. In a case where the sleep wake-up system determines that the second signal is obtained, it indicates that one or more vehicle-mounted objects in one or more vehicle integrated units need to be controlled to sleep.

[0107] For ease of description, the network topology shown in Figure 9 is taken as an example for illustration in the embodiments of the present application. Figure 9 An exemplary schematic diagram of a network topology of a communication computing architecture is shown. As Figure 9 shown, the communication computing architecture includes four VIUs (i.e., VIU1, VIU2, VIU3, and VIU4) and a VDC, a MDC, and a CDC. As Figure 9As shown, VIU1 includes CAN11 and CAN12; wherein CAN11 is hung with ECU11, ECU12 and ECU13; CAN12 is hung with ECU14, ECU15 and ECU16. VIU2 includes CAN21 and LIN21; wherein, CAN21 is hung with ECU21, ECU22 and ECU23; LIN21 is hung with ECU24, ECU25 and ECU26. VIU3 includes CAN31, CAN32 and CAN33; wherein, CAN31 is hung with ECU31, ECU32 and ECU33; CAN33 is hung with ECU34 and ECU35; CAN32 is hung with ECU36. VIU4 includes CAN41 and LIN41; wherein, LIN41 is hung with ECU41, ECU42 and ECU43; CAN41 is hung with ECU44, CU45 and ECU46. The above VIU1, VIU2, VIU3 and VIU4 are vehicle integrated units, the above CAN11, CAN12 and LIN21 are vehicle objects, and the above ECU11, ECU12 and ECU13 are also vehicle objects. The first signal can be used to wake up one or more vehicle objects in one or more vehicle integrated units, for example, the first signal can be used to wake up CAN11 of VIU1, or used to wake up ECU14 and ECU15 hung under CAN12 of VIU1. The second signal can be used to control one or more vehicle objects in one or more vehicle integrated units to sleep, for example, the second signal can be used to control CAN41 and LIN41 of VIU4 to sleep, or used to control ECU44 hung under CAN41 to sleep, etc.

[0108] In a possible implementation, step S201 can include: determining, for any first sleep wake-up signal in the at least one first sleep wake-up signal, a second sleep wake-up signal corresponding to the first sleep wake-up signal based on a first mapping relationship, the first mapping relationship being used to represent a mapping relationship between sleep wake-up signals generated in a vehicle network of a first vehicle model and unified sleep wake-up signals.

[0109] Table 1 shows an example of the first mapping relationship. As shown in Table 1, based on Figure 9In a case where VIU3 J4-35 detects a high level, the hibernation wake-up system can determine that the first hibernation wake-up signal is acquired. At this time, the hibernation wake-up system can convert the first hibernation wake-up signal into the second hibernation wake-up signal "A+ direct current charging" according to the first mapping relationship. In a case where there is no network management message of CAN21, the hibernation wake-up system can determine that the first hibernation wake-up signal is acquired. At this time, the hibernation wake-up system can convert the first hibernation wake-up signal into the second hibernation wake-up signal "CAN21 application hibernation" according to the first mapping relationship. In a possible implementation manner, the name of the second hibernation wake-up signal can be used to represent the function of the second hibernation wake-up signal. Considering that the first hibernation wake-up signal before conversion and the second hibernation wake-up signal after conversion are corresponding and the functions implemented are the same, the name of the second hibernation wake-up signal also represents the function of the first hibernation wake-up signal.

[0110] Table 1

[0111]

[0112] As shown in Table 1, in the embodiment of the present application, a unique identifier can be set for each second hibernation wake-up signal. In this way, the efficiency can be improved by transmitting the identifier of the second hibernation wake-up signal instead of the name of the second hibernation wake-up signal.

[0113] As shown in Table 1, in the embodiment of the present application, a unique identifier can be set for each second hibernation wake-up signal. In this way, the efficiency can be improved by transmitting the identifier of the second hibernation wake-up signal instead of the name of the second hibernation wake-up signal. Figure 7 For example, the hibernation wake-up system shown in FIG. 1 can be used. The first hibernation wake-up signal is converted into the second hibernation wake-up signal by the wake-up source parser 11, and the second hibernation wake-up signal is sent to the wake-up strategy controller 12 for subsequent processing. In the embodiment of the present application, interface 1 (Interface 1) is used to represent the interface between the wake-up source parser 11 and the wake-up strategy controller 12. The wake-up source parser 11 can send the second hibernation wake-up signal to the wake-up strategy controller 12 through the interface 1.

[0114] Table 2 shows an example of interface 1. As shown in Table 2, the second hibernation wake-up signal with an identifier of 2 corresponds to a name of "Bluetooth key unlocking" in the interface 1. Therefore, when the wake-up source parser 11 transmits the identifier 2 through the interface 1, the wake-up strategy controller 12 can obtain the name "Bluetooth key unlocking" of the second hibernation wake-up signal.

[0115] Table 2

[0116] Serial number Identity of the second sleep wake-up signal Name of the second sleep wake-up signal 1 2 Bluetooth key unlock 2 4 KL15

[0117] In the embodiment of the present application, the first mapping relationship and the interface 1 can be set according to needs and historical experience.

[0118] In step S202, at least one static control target is determined based on the at least one second hibernation wake-up signal.

[0119] The static control target is used to represent the function of the first sleep wake-up signal.

[0120] In a possible implementation, the step S202 can include: determining, for any one of the at least one second sleep wake-up signal, a static control target corresponding to the second sleep wake-up signal based on a second mapping relationship, the second mapping relationship being used to represent a mapping relationship between a unified sleep wake-up signal and a vehicle-mounted object; and merging the static control targets corresponding to the second sleep wake-up signals to obtain the at least one static control target.

[0121] Table 3 shows an example of the second mapping relationship. As shown in Table 3, based on the second mapping relationship, when the sleep wake-up system obtains the second sleep wake-up signal with an identifier of 1, a static control target with an identifier of 1, a name of “DC charging”, and a content of “CAN41” can be obtained, which represents the function of “A+ DC charging”. When the sleep wake-up system obtains the second sleep wake-up signal with an identifier of 2, a static control target with an identifier of 2, a name of “Bluetooth key unlocking wake-up”, and a content of “CAN11, CAN12, and CAN31” can be obtained, which represents the function of “Bluetooth key unlocking”. Figure 9 Table 3

[0122]

[0123] As shown in Table 3, in the embodiments of the present application, a unique identifier can be set for each static control target according to the function represented by the static control target, or a unique identifier can be set for each static control target according to needs. In this way, by delivering the identifier of the static control target instead of the name and content of the static control target, the efficiency can be improved.

[0124] As shown in the sleep wake-up system of

[0125] Figure 7 In the sleep wake-up system shown in FIG. 12, the wake-up strategy controller 12 determines the static control target based on the second sleep wake-up signal, and sends the static control target to the wake-up executor 13 for subsequent processing. In the embodiments of the present application, interface 2 (Interface 2) is used to represent the interface between the wake-up strategy controller 12 and the wake-up executor 13, and the wake-up source strategy controller 12 can send the static control target to the wake-up executor 13 through the interface 2.

[0126] ​Table 4 shows an example of interface 2. As shown in Table 4, interface 2 defines the content corresponding to the static control target with identifier 1 as "CAN41". Therefore, when the wake-up strategy controller 12 transmits identifier 1 through interface 2, the wake-up actuator 13 can obtain the name of the static control target as "DC charging" and the content as "CAN41".

[0127] Table 4

[0128] Identity Name Content 1 Direct current charging CAN41 2 Bluetooth key unlock wake-up CAN11, CAN12 and CAN31 3 Left front door wake-up CAN11 and CAN41 4 Vehicle wake-up Vehicle network wake-up 5 CAN21 sleep CAN21

[0129] In this embodiment of the application, the second mapping relationship and interface 2 can be set as needed and based on historical experience.

[0130] Step S203: Based on the at least one static control target, determine at least one sleep / wake-up action.

[0131] The sleep / wake-up action is used to wake up at least one in-vehicle object in at least one vehicle integration unit or to control at least one in-vehicle object in at least one vehicle integration unit to enter sleep mode. It can be understood that when the first sleep / wake-up signal is a first signal, the corresponding sleep / wake-up action is used to wake up at least one in-vehicle object in at least one vehicle integration unit. When the first sleep / wake-up signal is a second signal, the corresponding sleep / wake-up action is used to control at least one in-vehicle object in at least one vehicle integration unit to enter sleep mode.

[0132] In one possible implementation, step S203 may include: for any one of the at least one static control targets, based on a third mapping relationship, determining at least one vehicle integration unit corresponding to the static control target, and the vehicle-mounted object in each determined vehicle integration unit that needs to be subject to sleep / wake-up control, wherein the third mapping relationship is used to characterize the mapping relationship between the static control target, the vehicle integration unit, and the vehicle-mounted object that needs to be subject to sleep / wake-up control; and determining the at least one sleep / wake-up action based on whether the vehicle-mounted object subject to sleep / wake-up control is currently in a wake-up state or a sleep state.

[0133] Table 5 shows an example of the third mapping relationship. As shown in Table 5, based on Figure 9 When the hibernation wake-up system obtains a static control target identified as 1, according to the third mapping relationship, the hibernation wake-up actions of ECU44 and ECU45, which are identified as 1, have the vehicle integration unit as "VIU4", and have the vehicle object as "CAN41", can be obtained. This hibernation wake-up action is used to wake up ECU44 and ECU45, which are connected to "CAN41" of the vehicle integration unit "VIU4".

[0134] Table 5

[0135]

[0136] In the embodiments of the present application, the third mapping relationship can be set according to needs and historical experience.

[0137] In step S204, the at least one hibernation wake-up action is executed.

[0138] The hibernation wake-up system can execute various hibernation wake-up actions to wake up or control at least one vehicle-mounted object in the at least one vehicle integrated unit to hibernate.

[0139] The hibernation wake-up system provided by the embodiments of the present application can convert hibernation wake-up signals generated by vehicle-mounted networks of different vehicle models into unified hibernation wake-up signals and obtain unified static control targets, and then wake up or hibernate vehicle-mounted objects in vehicle integrated units, thereby realizing hibernation wake-up control in a communication computing architecture in a software manner.

[0140] Figure 10 An interaction flowchart of the hibernation wake-up method provided by the embodiments of the present application is shown. Figure 10 The method shown can be applied to Figure 7 The system shown. As Figure 10 The method shown can include:

[0141] In step S401, the external wake-up source sends at least one first hibernation wake-up signal to a wake-up source parser.

[0142] In step S402, the wake-up source parser converts the at least one first hibernation wake-up signal into at least one second hibernation wake-up signal.

[0143] In step S403, the wake-up source parser sends the at least one second hibernation wake-up signal to a wake-up strategy controller.

[0144] In step S404, the wake-up strategy controller determines at least one static control target based on the at least one second hibernation wake-up signal.

[0145] In step S405, the wake-up strategy controller sends the at least one static control target to a wake-up executor.

[0146] In step S406, the wake-up executor determines at least one hibernation wake-up action based on the at least one static control target.

[0147] In step S407, the wake-up executor executes the at least one hibernation wake-up action to wake up or hibernate at least one vehicle-mounted object in the at least one vehicle integrated unit.

[0148] Steps S401 to S407 can refer to steps S201 to S204, which will not be described here again.

[0149] The sleep wake-up method provided by the embodiments of the present application can convert sleep wake-up signals generated by vehicle-mounted networks of different vehicle models into unified sleep wake-up signals, and obtain unified static control targets, and then wake up or sleep the vehicle-mounted objects in the whole vehicle integrated unit, thereby realizing sleep wake-up control in the communication computing architecture by means of software.

[0150] In a possible implementation, the wake-up source analyzer and the wake-up executor in the sleep wake-up system can be deployed in the whole vehicle integrated unit, and the wake-up strategy controller is deployed in the domain controller.

[0151] Figure 11 A deployment schematic diagram of the sleep wake-up system provided by the embodiments of the present application is shown. As shown in Figure 11 On the basis of the communication computing architecture shown in Figure 9 Each VIU (including VIU1, VIU2, VIU3 and VIU4) is deployed with a wake-up source analyzer and a wake-up executor, and the xDC is deployed with a wake-up strategy controller.

[0152] Figure 12 An interaction flowchart of the sleep wake-up method provided by the embodiments of the present application is shown. The method can be applied to Figure 11 As shown in Figure 12 The method comprises the following steps.

[0153] In step S501, an external wake-up source sends a first sleep wake-up signal to the wake-up source analyzer in the VIU.

[0154] The external signal source can send the first sleep wake-up signal to the wake-up analyzer in each VIU. As shown in Figure 11 The external wake-up source sends the first sleep wake-up signal 11 and the first sleep wake-up signal 12 to the wake-up source analyzer in VIU1; the external wake-up source sends the first sleep wake-up signal 21 and the first sleep wake-up signal 22 to the wake-up source analyzer in VIU2; the external wake-up source sends the first sleep wake-up signal 31 and the first sleep wake-up signal 32 (not shown) to the wake-up source analyzer in VIU3; and the external wake-up source sends the first sleep wake-up signal 41 and the first sleep wake-up signal 42 to the wake-up source analyzer in VIU4. It can be understood that the external wake-up source can send more or less first sleep wake-up signals to the wake-up source analyzer in the VIU than Figure 11 As shown in

[0155] In one example, the external wake-up source "Passive Entry & Passive Start (PEPS)" can send the first sleep wake-up signal "CAN NM message" to VIU1.

[0156] In step S502, the wake-up source resolver in the VIU converts the first sleep wake-up signal into a second sleep wake-up signal.

[0157] The wake-up source resolver in each VIU can convert the received first sleep wake-up signal into a second sleep wake-up signal. For example... Figure 11 As shown, the wake-up source resolver in VIU1 can convert the first sleep wake-up signal 11 into the second sleep wake-up signal 11, and the first sleep wake-up signal 12 into the second sleep wake-up signal 12; the wake-up source resolver in VIU2 can convert the first sleep wake-up signal 21 into the second sleep wake-up signal 21, and the first sleep wake-up signal 22 into the second sleep wake-up signal 22; the wake-up source resolver in VIU3 can convert the first sleep wake-up signal 31 into the second sleep wake-up signal 31, and the first sleep wake-up signal 32 into the second sleep wake-up signal 32 (not shown); the wake-up source resolver in VIU4 can convert the first sleep wake-up signal 41 into the second sleep wake-up signal 41, and the first sleep wake-up signal 42 into the second sleep wake-up signal 42. It should be noted that the above are only examples of the first and second sleep wake-up signals; in actual execution, there may be more or fewer first and second sleep wake-up signals.

[0158] In one example, the first sleep wake-up signal, “CAN NM message”, can be converted into a second sleep wake-up signal, “identified as 2 and named Bluetooth Key Unlock”.

[0159] In step S503, the wake-up source resolver in the VIU sends the second sleep wake-up signal to the wake-up policy controller in the xDC.

[0160] The wake-up source resolver in each VIU can send the obtained second sleep wake-up signal to the wake-up policy controller in the xDC for processing. For example... Figure 11 As shown, the wake-up source resolver in VIU1 can send the second sleep wake-up signal 11 and the second sleep wake-up signal 12 to the wake-up policy controller in xDC. The wake-up source resolver in VIU2 can send the second sleep wake-up signal 21 and the second sleep wake-up signal 22 to the wake-up policy controller in xDC. The wake-up source resolver in VIU4 can send the second sleep wake-up signal 41 and the second sleep wake-up signal 42 to the wake-up policy controller in xDC.

[0161] In one example, the wake source resolver in VIU1 sends the second dormant wake signal with "ID 2, name Bluetooth key unlock" to the wake policy controller in dC.

[0162] Step S504, the wake policy controller in dC determines the static control target according to the second dormant wake signal from the wake source resolver in each VIU.

[0163] The wake policy controller in dC can determine one static control target based on each received second dormant wake signal, and take the union of each static control target to obtain the final static control target. As shown in Table 3, the wake policy controller in dC finally obtains the static control target 1. Figure 11

[0164] In one example, the wake policy controller in dC obtains the static control target with "ID 2, name Bluetooth key unlock wake" based on the second dormant wake signal with "ID 2, name Bluetooth key unlock" (as shown in Table 3).

[0165] Step S505, the wake decision controller in dC sends the static control target to the wake enforcer in each VIU.

[0166] As shown in Table 3, the wake decision controller in dC sends the static wake target 1 to the wake enforcer in VIU2, the wake enforcer in VIU2, the wake enforcer in VIU3 (not shown), and the wake enforcer in VIU4, respectively. Figure 11

[0167] In one example, the wake policy controller in dC sends the static control target with "ID 2, name Bluetooth key unlock wake" to the wake enforcer in all VIUs.

[0168] Step S506, the wake enforcer in the VIU determines the vehicle-mounted object in the current VIU that needs to be woken up and / or the vehicle-mounted object in the current VIU that needs to be put into hibernation according to the received static control target and the state of each vehicle-mounted object in the current VIU.

[0169] As shown in Table 3, the wake enforcer in VIU2 determines that the vehicle-mounted object with ID 1 needs to be woken up and the vehicle-mounted object with ID 2 needs to be put into hibernation. Figure 11 ​​As shown, the wake-up executor in VIU1 determines that the sleep wake-up action 11 (e.g., wake up vehicle object 1) and the sleep wake-up action 12 (e.g., control vehicle object 2 to sleep) need to be performed according to the static control target 1 and the states of the vehicle objects in VIU1; the wake-up executor in VIU2 determines that the sleep wake-up action 21 and the sleep wake-up action 22 need to be performed according to the static control target 1 and the states of the vehicle objects in VIU2; the wake-up executor in VIU3 determines that the sleep wake-up action 31 and the sleep wake-up action 32 (not shown) need to be performed according to the static control target 1 and the states of the vehicle objects in VIU3; the wake-up executor in VIU4 determines that the sleep wake-up action 41 and the sleep wake-up action 42 need to be performed according to the static control target 1 and the states of the vehicle objects in VIU4. It should be noted that the above is only an example of the sleep wake-up action, and more or fewer actions can be determined in actual execution.

[0170] In one example, the wake-up executor in VIU1 wakes up ECU11 and ECU12 hanging under CAN11, and wakes up ECU14, ECU15 and ECU16 hanging under CAN12. The wake-up executor in VIU2 wakes up ECU21 hanging under CAN21. The wake-up executor in VIU3 has no corresponding sleep wake-up action, and the wake-up executor in VIU4 has no sleep wake-up action.

[0171] In step S507, the wake-up executor in the VIU wakes up the vehicle object in the current VIU that needs to be woken up, and / or controls the vehicle object in the current VIU that needs to sleep to sleep.

[0172] In one example, VIU1 and VIU2 perform the sleep wake-up action described above, and VIU3 and VIU3 do not need to perform the sleep wake-up action.

[0173] The sleep wake-up method provided by the embodiments of the present application can convert the sleep wake-up signals generated by the vehicle networks of different vehicle models into unified sleep wake-up signals, obtain unified static control targets, and then wake up or sleep the vehicle objects in the vehicle integrated unit, thereby realizing sleep wake-up control in the communication computing architecture through software.

[0174] It is considered that the vehicle has a demand for a specific wake-up duration. For example, when the vehicle owner is within a certain distance (such as 5 meters) from the vehicle, the vehicle will detect the car key. At this time, the vehicle will wake up the VIU and the uDC. If the user further approaches the vehicle, the vehicle can be automatically unlocked, thereby providing a good user experience for the vehicle owner. If the wake-up time of the vehicle is relatively long (such as > 1 second), the vehicle door has not been unlocked when the vehicle owner needs to open the door, which will affect the customer experience. Figure 11The wake-up strategy controller is deployed in the dxC, and all the hibernation wake-up actions need to go through the process of "VIU" to "dxC" and then back to "VIU", thereby prolonging the hibernation wake-up time of the vehicle, which may affect the user experience.

[0175] In a possible implementation, the wake-up source resolver, the wake-up strategy controller and the wake-up executor in the hibernation wake-up system can all be deployed in the whole vehicle integration unit.

[0176] Figure 13 A deployment schematic diagram of the hibernation wake-up system provided by the embodiments of the present application is shown. As shown in Figure 13 On the basis of the communication computing architecture shown in Figure 9 A wake-up source resolver, a wake-up executor and a wake-up strategy controller are deployed in each VIU (including VIU1, VIU2, VIU3 and VIU4).

[0177] Considering that the external wake-up source on one VIU will affect the hanged objects of other VIUs, the static control target output by the wake-up strategy controller on one VIU needs to be sent to the wake-up executors on various VIUs for processing. In order to simplify the design, it is assumed that the wake-up strategy (i.e., the second mapping relationship) carried by each wake-up strategy controller is the same, and then the wake-up source resolver on one VIU only needs to send the static control target to the wake-up executors on various VIUs, without sending the second hibernation wake-up signal to the wake-up strategy controllers on other VIUs for processing. In addition, it is assumed that the vehicle network is reasonably planned, and in the case that the wake-up strategy controller on one VIU only supports the external wake-up source on the VIU (i.e., can only transform the first hibernation wake-up signal generated on the VIU), the goal of waking up the whole vehicle and the goal of controlling the whole vehicle to hibernate can still be achieved. In principle, each VIU will deploy a wake-up strategy controller. If it is found in the vehicle network design process that a VIU does not directly receive an external wake-up source, the VIU does not need to deploy a wake-up strategy controller.

[0178] Figure 14 An interaction flowchart of a hibernation wake-up method provided by the embodiments of the present application is shown. The method can be applied to Figure 13 The system shown. As shown in Figure 14 The method comprises the following steps.

[0179] In step S601, the external wake-up source sends a first hibernation wake-up signal to the wake-up source resolver in the VIU.

[0180] In step S602, the wake-up source resolver in the VIU converts the first hibernation wake-up signal into a second hibernation wake-up signal.

[0181] Steps S601 and S602 can refer to steps S501 and S502, which are not repeated here.

[0182] In step S603, the wake-up source parser in the VIU sends the second sleep wake-up signal to the wake-up policy controller in the current VIU.

[0183] In one example, the wake-up source parser in VIU1 sends the second sleep wake-up signal "identified as 2, named as Bluetooth key unlock" to the wake-up policy controller in VIU1.

[0184] In step S604, the wake-up policy controller in the VIU determines the static control target according to the second sleep wake-up signal from the wake-up source parser in the current VIU.

[0185] In one example, the wake-up policy controller in VIU1 gets the static control target "identified as 2, named as Bluetooth key unlock wake-up" based on the second sleep wake-up signal "identified as 2, named as Bluetooth key unlock" (as shown in Table 3).

[0186] In step S605, the wake-up decision controller in the VIU sends the static control target to the wake-up enforcer in the VIU.

[0187] In one possible implementation, the wake-up decision controller in the VIU can send the static control target to the wake-up enforcers in all VIUs. Then, the wake-up enforcers in each VIU can perform steps S606 and S607 to realize the control of the vehicle-mounted object. For example, as mentioned above, the wake-up policy controller in VIU1 sends the static control target "identified as 2, named as Bluetooth key unlock wake-up" to the wake-up enforcers in VIU1, VIU2, VIU3 and VIU4 respectively. Figure 9

[0188] In one possible implementation, the wake-up decision controller in the VIU can send the static control target to the wake-up enforcers in the VIU related to the static control target. For example, as shown in Table 3, since the content of the static control target "identified as 2, named as Bluetooth key unlock wake-up" involves CAN11, CAN12 and CAN31, as shown in Table 4, CAN11 and CAN12 are hung under VIU1, and CAN31 is hung under VIU3, that is, the VIUs related to the static control target "identified as 2, named as Bluetooth key unlock wake-up" are VIU1 and VIU3, therefore, the wake-up decision controller in VIU1 can send the static control target to the wake-up enforcers in VIU1 and VIU3 respectively. Figure 9

[0189] ​​Step S606, the wake-up executor in the VIU determines the vehicle-mounted object in the current VIU that needs to be woken up and / or the vehicle-mounted object in the current VIU that needs to be put to sleep according to the received static control target and the state of each vehicle-mounted object in the current VIU.

[0190] Step S607, the wake-up executor in the VIU wakes up the vehicle-mounted object in the current VIU that needs to be woken up, and / or controls the vehicle-mounted object in the current VIU that needs to be put to sleep to be put to sleep.

[0191] Steps S606 and S607 can refer to steps S506 and S507, which will not be described here again.

[0192] In the embodiments of the present application, the wake-up strategy controller deployed in the dxC is moved down to each VIU, and when the vehicle-mounted object in the wake-up VIU needs to be put to sleep, the speed of putting to sleep and waking up is accelerated.

[0193] For the wake-up strategy controller mentioned above, if the static control targets corresponding to the wake-up sources received by different VIUs conflict, for example, VIU1 will trigger CAN21 to wake up, and VIU2 will trigger CAN21 to sleep, a conflict will occur. Figure 13

[0194] In a possible implementation, the wake-up strategy controller is divided into a distributed wake-up strategy controller and a centralized wake-up strategy controller, the wake-up source resolver, the wake-up executor, and the distributed wake-up strategy controller in the sleep-wake-up system are deployed in the vehicle integrated unit, and the centralized wake-up strategy controller is deployed in the domain controller.

[0195] Figure 15 A deployment schematic diagram of the sleep-wake-up system provided by the embodiments of the present application is shown. As shown in the figure, Figure 15 As shown in the communication computing architecture shown in the figure, a wake-up source resolver, a wake-up executor, and a distributed wake-up strategy controller are deployed in each VIU (including VIU1, VIU2, VIU3, and VIU4), and a centralized wake-up strategy controller is deployed in the dxC. Figure 9 In order to ensure that the local wake-up source can quickly wake up the vehicle-mounted object, while avoiding the conflict of the wake-up and sleep behaviors of different vehicle-mounted objects caused by different wake-up sources, based on the principle of "fast wake-up and slow sleep", in the embodiments of the present application, the distributed wake-up strategy controller and the centralized wake-up strategy controller need to be divided for the wake-up action. Among them, the distributed wake-up strategy controller can only decide the wake-up of the vehicle-mounted object in the current VIU; the centralized wake-up strategy controller can only decide the wake-up of the vehicle-mounted object across the VIUs.

[0196]

[0197] ​​In order to ensure that the centralized policy controller decision comes from different VIUs, the wake-up source interface 1 needs to be modified to add the definition of the source VIU. The modified interface 1 (which can be referred to as interface 3) is shown in Table 6.

[0198] Table 6

[0199]

[0200] For hibernation, in the embodiments of the present application, the policy involved in hibernation needs to be moved up to the centralized wake-up policy controller on the basis of Figure 14 Figure 16 The interaction flowchart of the hibernation wake-up method provided by the embodiments of the present application is shown. The method can be applied to the system shown in Figure 15 As shown in Figure 16 The method comprises the following steps:

[0201] Step S701: An external wake-up source sends a first hibernation wake-up signal to a wake-up source parser in a first VIU.

[0202] The first VIU represents any one of the VIUs in the communication computing architecture.

[0203] Step S702: The wake-up source parser in the first VIU converts the first hibernation wake-up signal into a second hibernation wake-up signal.

[0204] Steps S701 and S702 can refer to steps S501 and S502, which will not be described here.

[0205] Step S7031: The wake-up parser in the first VIU sends the second hibernation wake-up signal to a distributed wake-up policy controller in the first VIU.

[0206] In one example, the wake-up source parser in VIU1 sends the second hibernation wake-up signal with the identification of 2 and the name of Bluetooth key unlocking to the distributed wake-up policy controller in VIU1.

[0207] Step S7032: The wake-up parser in the first VIU sends the second hibernation wake-up signal to a centralized wake-up policy controller in the xDC.

[0208] In one example, the wake-up source parser in VIU1 sends the second hibernation wake-up signal with the identification of 2 and the name of Bluetooth key unlocking to the centralized wake-up policy controller in the xDC.

[0209] Step S7041: The distributed wake-up policy controller in the first VIU determines a static control target based on the second hibernation wake-up signal from the wake-up source parser in the first VIU.

[0210] ​In one example, the distributed wake-up strategy controller in the VIU1 determines the static control target of "identified as 2, named as Bluetooth key unlock wake-up" based on the second sleep wake-up signal of "identified as 2, named as Bluetooth key unlock" from the VIU1.

[0211] Step S7042, the centralized wake-up strategy controller in the xDC determines the static control target based on the second sleep wake-up signal from the wake-up source resolver in the first VIU.

[0212] In one example, the centralized wake-up strategy controller in the xDC determines the static control target of "identified as 2, named as Bluetooth key unlock wake-up" based on the second sleep wake-up signal of "identified as 2, named as Bluetooth key unlock" from the VIU1.

[0213] Step S7051, the distributed wake-up strategy controller in the first VIU sends the determined static wake-up target to the wake-up executor in the first VIU.

[0214] In one example, the wake-up strategy controller in the VIU1 sends the static control target of "identified as 2, named as Bluetooth key unlock wake-up" to the wake-up executor in the VIU1.

[0215] Step S7052, the centralized wake-up strategy controller in the xDC sends the determined static wake-up target to the wake-up executor in the second VIU.

[0216] Wherein, the second VIU represents a VIU in the communication computing architecture other than the first VIU.

[0217] In one example, the wake-up strategy controller in the xDC sends the static control target of "identified as 2, named as Bluetooth key unlock wake-up" to the wake-up executor in the VIU other than the VIU1.

[0218] Step S7061, the wake-up executor in the first VIU determines the vehicle-mounted object in the first VIU that needs to be woken up and / or the vehicle-mounted object that needs to be put to sleep according to the received static control target and the state of each vehicle-mounted object in the current VIU.

[0219] In one example, the wake-up executor in the VIU1 wakes up the ECU11 and the ECU12 under the CAN11, and wakes up the ECU14, the ECU15 and the ECU16 under the CAN12.

[0220] Step S7062, the wake-up executor in the second VIU determines the vehicle-mounted object in the second VIU that needs to be woken up and / or the vehicle-mounted object that needs to be put to sleep according to the received static control target and the state of each vehicle-mounted object in the current VIU.

[0221] In one example, the wake-up executor in the VIU 2 wakes up the ECU 21 hanging under the CAN 21. The wake-up executor in the VIU 3 has no corresponding sleep wake-up action, and the wake-up executor in the VIU 4 has no sleep wake-up action.

[0222] In step S7071, the wake-up executor in the first VIU wakes up the vehicle-mounted object in the first VIU that needs to be woken up, and / or controls the vehicle-mounted object in the first VIU that needs to be put into sleep.

[0223] In step S7072, the wake-up executor in the second VIU wakes up the vehicle-mounted object in the second VIU that needs to be woken up, and / or controls the vehicle-mounted object in the second VIU that needs to be put into sleep.

[0224] In the embodiments of the present application, since the distributed wake-up strategy controller is deployed in the VIU, the wake-up speed can be accelerated when the wake-up source of the VIU needs to wake up the local vehicle-mounted object. At the same time, since the centralized wake-up strategy controller is still reserved in the dxC, the conflict problem of sleep wake-up is solved, and the reliability is improved.

[0225] It should be noted that in the embodiments of the present application, the wake-up strategy controller deployed in the VIU can be referred to as a distributed wake-up strategy controller, and the wake-up strategy controller deployed in the dxC can be referred to as a centralized wake-up strategy controller or a global wake-up strategy controller.

[0226] Figure 17 A structure schematic diagram of the sleep wake-up device provided by the embodiments of the present application is shown. As shown in Figure 17 The device 1700 can include:

[0227] The conversion module 1701 is configured to convert at least one first sleep wake-up signal into at least one second sleep wake-up signal, the first sleep wake-up signal being used to represent the sleep wake-up signal generated in the vehicle-mounted network of the first vehicle model, and the second sleep wake-up signal being used to represent the unified sleep wake-up signal converted from the sleep wake-up signal with the same function generated in the vehicle-mounted network of different vehicle models;

[0228] The first determination module 1702 is configured to determine at least one static control target based on the at least one second sleep wake-up signal, the static control target being used to represent the function of the first sleep wake-up signal.

[0229] The second determination module 1703 is configured to determine at least one sleep wake-up action based on the at least one static control target, the sleep wake-up action being used to wake up or control to sleep at least one vehicle-mounted object in at least one vehicle integrated unit.

[0230] The execution module 1704 is configured to execute the at least one hibernation wake-up action.

[0231] In a possible implementation, the conversion module is further configured to:

[0232] For any one of the at least one first hibernation wake-up signal, determine a second hibernation wake-up signal corresponding to the first hibernation wake-up signal based on a first mapping relationship, the first mapping relationship being used to represent a mapping relationship between a hibernation wake-up signal generated in a vehicle network of a first vehicle model and a unified hibernation wake-up signal.

[0233] In a possible implementation, the first determination module is further configured to:

[0234] For any one of the at least one second hibernation wake-up signal, determine a static control target corresponding to the second hibernation wake-up signal based on a second mapping relationship, the second mapping relationship being used to represent a mapping relationship between the unified hibernation wake-up signal and a vehicle-mounted object;

[0235] merge the static control targets corresponding to the second hibernation wake-up signals to obtain the at least one static control target.

[0236] In a possible implementation, the second determination module is further configured to:

[0237] For any one of the at least one static control target, determine at least one vehicle integrated unit corresponding to the static control target and a vehicle-mounted object that needs to be controlled for hibernation wake-up in each determined vehicle integrated unit based on a third mapping relationship, the third mapping relationship being used to represent a mapping relationship between the static control target and the vehicle integrated unit and the vehicle-mounted object that needs to be controlled for hibernation wake-up;

[0238] determine the at least one hibernation wake-up action according to whether the vehicle-mounted object that needs to be controlled for hibernation wake-up is currently in an awake state or a hibernation state.

[0239] In a possible implementation, the first hibernation wake-up signal includes a first signal used to wake up a vehicle-mounted object and / or a second signal used to control a vehicle-mounted object to hibernate. Figure 18 A structure schematic diagram of a hibernation wake-up apparatus provided by an embodiment of the present application is shown. As shown in Figure 18 on the basis of Figure 17 the apparatus 1700 can further include:

[0240] The third determining module 1705 is configured to determine that the first signal is obtained when the network management packet is received, or the service packet is received, or the first level change is detected.

[0241] The fourth determining module 1706 is configured to determine that the second signal is obtained when the network management packet is not received, or the service packet is not received, or the second level change is detected within a preset time.

[0242] An embodiment of the present application provides a hibernation wakeup device, including a processor and a memory for storing processor-executable instructions; wherein the processor is configured to implement the above method when executing the instructions.

[0243] An embodiment of the present application provides a non-volatile computer-readable storage medium, which stores computer program instructions, and the computer program instructions are executed by a processor to implement the above method.

[0244] An embodiment of the present application provides a computer program product, including computer-readable code or a non-volatile computer-readable storage medium carrying computer-readable code, when the computer-readable code is run in a processor of an electronic device, the processor in the electronic device executes the above method.

[0245] The computer-readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium, for example, can be (but is not limited to) an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium include a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital video disc (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch cards or punched tape, and any suitable combination of the foregoing. A computer-readable storage medium, as used herein, is not to be construed as being transitory signals per se.

[0246] Computer readable program instructions or code for carry out the operations described herein can be downloaded to respective computing / processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network can comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and / or edge servers. A network adaptation card or network interface in each computing / processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium in the respective computing / processing device.

[0247] Computer readable program instructions for carrying out operations of the present application can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state setting data, or any combination of source code or object code in any combination of one or more programming languages including an object oriented programming language such as Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions can execute entirely on a user's computing device, partly on the user's computing device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server. In the latter scenario, the remote computing device can be connected to the user's computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computing device, such as through the Internet using an Internet Service Provider. In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate array (FPGA), or programmable logic array (PLA) can execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present application.

[0248] Various aspects of the present application are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer readable program instructions.

[0249] These computer readable program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer readable program instructions can also be stored in a computer readable storage medium that can include a non-transitory computer readable storage medium that can be a computer readable storage medium having no data, programs, program modules, and / or computer readable program instructions presently, and / or not yet, stored thereon. The instructions can be stored in a computer readable storage medium that can be implemented in any method or technology for storage of information, including magnetic storage media, optical storage media, solid-state storage media, and others.

[0250] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable data processing apparatus, or other device implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0251] The flow diagrams and block diagrams in the accompanying drawings show archi tectures, functional and operational architectures of possible implementations of apparatuses, systems, methods and computer program products according to the present application. In this regard, each block in the flow diagrams and block diagrams can represent a module, a segment, or a portion of instructions, which comprises one or more executable instructions for implementing the specified logical functions (acts). In some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in some cases, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. These and other alternatives are possible.

[0252] It also is noted that each of the blocks of the flowchart, and / or combinations of blocks, can be implemented by hardware, by software including one or more computer program instructions, by firmware, or by a combination of hardware, software, and / or firmware. Also, each of the blocks of the flowchart, and / or combinations of blocks, can be implemented by special purpose hardware-based computer systems which are specifically programmed, configured, or constructed to perform one or more computer program instructions.

[0253] Although the application has been described in connection with various embodiments, it will be understood that the application is capable of further modifications. These and other changes, along with the apparent alternatives and equivalents, fall within the scope of the claimed application. The description herein is intended to be illustrative only and is presented to enable any person skilled in the art to make and use the application. Numerous modifications and adaptations will be apparent to those skilled in the art without departing from the scope of the described application. The scope of the described application is not to be limited by the specific illustrative embodiments contained herein but only by the scope of the appended claims, which follow this disclosure.

[0254] Various embodiments of the application have been described in connection with the embodiments described above. The description is intended to be illustrative only and not exhaustive of all possible embodiments. Numerous modifications and adaptations will be apparent to those skilled in the art without departing from the scope of the described embodiments. The scope of the described embodiments is not to be limited by the specific illustrative embodiments contained herein but only by the scope of the appended claims, which follow this disclosure.

Claims

1. A hibernate wake-up method, characterized by, The method comprises: converting at least one first sleep wake-up signal into at least one second sleep wake-up signal, the first sleep wake-up signal being used to represent a sleep wake-up signal generated in a vehicle network of a first vehicle model, and the second sleep wake-up signal being used to represent a unified sleep wake-up signal converted from a sleep wake-up signal of the same function generated in a vehicle network of a different vehicle model; determining at least one static control target based on the at least one second sleep wake-up signal, the static control target being used to represent a function of the first sleep wake-up signal; determining at least one sleep wake-up action based on the at least one static control target, the sleep wake-up action being used to wake up or control to sleep at least one vehicle-mounted object in at least one vehicle integrated unit; performing the at least one sleep wake-up action.

2. The method of claim 1, wherein, The conversion of the at least one first sleep wake-up signal into the at least one second sleep wake-up signal comprises: for any one of the at least one first sleep wake-up signal, determining a second sleep wake-up signal corresponding to the first sleep wake-up signal based on a first mapping relationship, the first mapping relationship being used to represent a mapping relationship between a sleep wake-up signal generated in a vehicle network of a first vehicle model and a unified sleep wake-up signal.

3. The method according to claim 1 or 2, characterized in that, The determination of the at least one static control target based on the at least one second sleep wake-up signal comprises: for any one of the at least one second sleep wake-up signal, determining a static control target corresponding to the second sleep wake-up signal based on a second mapping relationship, the second mapping relationship being used to represent a mapping relationship between a unified sleep wake-up signal and a vehicle-mounted object; merging the static control targets corresponding to the second sleep wake-up signals to obtain the at least one static control target.

4. The method according to claim 1 or 2, characterized in that, The determination of the at least one sleep wake-up action based on the at least one static control target comprises: for any one of the at least one static control target, determining at least one vehicle integrated unit corresponding to the static control target and a vehicle-mounted object in each determined vehicle integrated unit that needs to be controlled to sleep and wake up based on a third mapping relationship, the third mapping relationship being used to represent a mapping relationship between a static control target and a vehicle integrated unit and a vehicle-mounted object that needs to be controlled to sleep and wake up; determining the at least one sleep wake-up action according to whether the vehicle-mounted object that needs to be controlled to sleep and wake up is currently in a wake-up state or a sleep state.

5. The method according to claim 1 or 2, characterized in that, The first sleep wake-up signal comprises a first signal used to wake up a vehicle-mounted object and / or a second signal used to control a vehicle-mounted object to sleep, and the method further comprises: determining that the first signal is obtained in a case where a network management packet is received or a service packet is received or a first level change is detected; determining that the second signal is obtained in a case where a network management packet is not received or a service packet is not received or a second level change is detected within a preset time.

6. A dormancy wake-up system, comprising: The hibernation wake-up system comprises a wake-up source resolver, a wake-up strategy controller and a wake-up executor. The wake-up source resolver is configured to convert at least one first hibernation wake-up signal into at least one second hibernation wake-up signal and send the at least one second hibernation wake-up signal to the wake-up strategy controller, wherein the first hibernation wake-up signal is used to represent a hibernation wake-up signal generated in a vehicle network of a first vehicle model, and the second hibernation wake-up signal is used to represent a unified hibernation wake-up signal converted from a hibernation wake-up signal with the same function generated in a vehicle network of a different vehicle model. The wake-up strategy controller is configured to determine at least one static control target based on the at least one second hibernation wake-up signal and send the at least one static control target to the wake-up executor, wherein the static control target is used to represent the function of the first hibernation wake-up signal. The wake-up executor is configured to determine at least one hibernation wake-up action based on the at least one static control target and execute the at least one hibernation wake-up action, wherein the hibernation wake-up action is used to wake up or control at least one vehicle-mounted object in at least one vehicle integrated unit to hibernate.

7. The system of claim 6, wherein, The wake-up source resolver and the wake-up executor are deployed in the vehicle integrated unit, and the wake-up strategy controller is deployed in the domain controller.

8. The system of claim 6, wherein, The wake-up source resolver, the wake-up strategy controller and the wake-up executor are deployed in the vehicle integrated unit.

9. The system of claim 6, wherein, The wake-up strategy controller comprises a distributed wake-up strategy controller and a centralized wake-up strategy controller, the wake-up source resolver, the wake-up executor and the distributed wake-up strategy controller are deployed in the vehicle integrated unit, and the centralized wake-up strategy controller is deployed in the domain controller.

10. The system of any one of claims 6 to 9, wherein, The wake-up source resolver is further configured to: For any one of the at least one first hibernation wake-up signal, determine a second hibernation wake-up signal corresponding to the first hibernation wake-up signal based on a first mapping relationship, wherein the first mapping relationship is used to represent a mapping relationship between a hibernation wake-up signal generated in a vehicle network of a first vehicle model and a unified hibernation wake-up signal.

11. The system of any one of claims 6 to 9, wherein, The wake-up strategy controller is further configured to: For any one of the at least one second hibernation wake-up signal, determine a static control target corresponding to the second hibernation wake-up signal based on a second mapping relationship, wherein the second mapping relationship is used to represent a mapping relationship between a unified hibernation wake-up signal and a vehicle-mounted object; merge the static control targets corresponding to the second hibernation wake-up signals to obtain the at least one static control target.

12. The system of any one of claims 6 to 9, wherein, The wake-up executor is further configured to: For any one of the at least one static control target, at least one vehicle integrated unit corresponding to the static control target and a vehicle object in each determined vehicle integrated unit that needs to be controlled to sleep and wake up are determined based on a third mapping relationship, and the third mapping relationship is used to represent a mapping relationship between a static control target and a vehicle integrated unit and a vehicle object that needs to be controlled to sleep and wake up. The at least one sleep and wake-up action is determined according to whether the vehicle object that needs to be controlled to sleep and wake up is currently in a wake-up state or a sleep state.

13. The system of any one of claims 6 to 9, wherein, The first sleep and wake-up signal includes a first signal used to wake up a vehicle object and / or a second signal used to control a vehicle object to sleep, and the sleep and wake-up system further includes a wake-up source. The wake-up source is used to determine that the first signal is obtained in a case where a network management packet is received, or a service packet is received, or a first level change is detected. The second signal is determined to be obtained in a case where a network management packet is not received within a preset time, or a service packet is not received, or a second level change is detected.

14. A hibernate wake-up apparatus, comprising: The device includes: A conversion module is configured to convert at least one first sleep and wake-up signal into at least one second sleep and wake-up signal, the first sleep and wake-up signal is used to represent a sleep and wake-up signal generated in a vehicle network of a first vehicle model, and the second sleep and wake-up signal is used to represent a unified sleep and wake-up signal converted from a sleep and wake-up signal with the same function generated in a vehicle network of a different vehicle model; A first determination module is configured to determine at least one static control target based on the at least one second sleep and wake-up signal, and the static control target is used to represent a function of the first sleep and wake-up signal; A second determination module is configured to determine at least one sleep and wake-up action based on the at least one static control target, and the sleep and wake-up action is used to wake up or control at least one vehicle object in at least one vehicle integrated unit to sleep; An execution module is configured to execute the at least one sleep and wake-up action.

15. The apparatus of claim 14, wherein, The conversion module is further configured to: For any one of the at least one first sleep and wake-up signal, a second sleep and wake-up signal corresponding to the first sleep and wake-up signal is determined based on a first mapping relationship, and the first mapping relationship is used to represent a mapping relationship between a sleep and wake-up signal generated in a vehicle network of a first vehicle model and a unified sleep and wake-up signal.

16. The apparatus of claim 14 or 15, wherein, The first determination module is further configured to: For any one of the at least one second sleep and wake-up signal, a static control target corresponding to the second sleep and wake-up signal is determined based on a second mapping relationship, and the second mapping relationship is used to represent a mapping relationship between a unified sleep and wake-up signal and a vehicle object; The static control targets corresponding to the second sleep and wake-up signals are merged to obtain the at least one static control target.

17. The apparatus of claim 14 or 15, wherein, The second determination module is further configured to: For any one of the at least one static control target, at least one vehicle integrated unit corresponding to the static control target is determined based on a third mapping relationship, and a vehicle object in each determined vehicle integrated unit that needs to be controlled to sleep and wake up, the third mapping relationship is used to represent the mapping relationship between the static control target and the vehicle integrated unit and the vehicle object that needs to be controlled to sleep and wake up; According to whether the vehicle object that needs to be controlled to sleep and wake up is currently in a wake-up state or a sleep state, the at least one sleep and wake-up action is determined.

18. The apparatus of claim 14 or 15, wherein, The first sleep and wake-up signal includes a first signal for waking up the vehicle object, and / or a second signal for controlling the vehicle object to sleep, and the apparatus further comprises: The third determination module is configured to determine that the first signal is obtained in a case where the network management message is received, or the service message is received, or the first level change is detected; The fourth determination module is configured to determine that the second signal is obtained in a case where the network management message is not received within a preset time, or the service message is not received, or the second level change is detected.

19. A hibernate wake-up apparatus, comprising: Comprise: A processor; A memory for storing processor-executable instructions; Wherein the processor is configured to implement the method of any one of claims 1 to 5 when executing the instructions.

20. A non-transitory computer readable storage medium having stored thereon computer program instructions, wherein, The computer program instructions are executed by the processor to implement the method of any one of claims 1 to 5.

21. A computer program product comprising computer readable code which, when run in an electronic device, causes a processor in the electronic device to perform the method of any one of claims 1 to 5.

Citation Information

Patent Citations

  • Sleep and wake-up method for in-vehicle hybrid network including vehicle-mounted Ethernet

    CN110758289A

  • Low-voltage power transmission system, DCDC converter, control method, equipment and medium

    CN113859047A