Vehicle scenario-based management method and apparatus, medium, and device

Through the vehicle scenario-based management method, the target functional scenarios are identified and the power supply ports of the distribution box drive are controlled, which solves the problem of poor energy saving effect in the existing vehicle management technology, and achieves more efficient vehicle power management and adaptability.

WO2025119094A1PCT designated stage expired Publication Date: 2025-06-12VOYAH AUTOMOBILE TECH CO LTD

Patent Information

Application Number
PCT/CN2024/135624
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-12-04
Filing Date
2024-11-29
Publication Date
2025-06-12

AI Technical Summary

Technical Problem

The existing vehicle management technology has the problem of poor energy saving effect, especially in the coordination management of network status of on-board power equipment and controller nodes.

Method used

Through the vehicle scene-based management method, the trigger signal is obtained to identify the target functional scenario, the target abstract device is determined, and the distribution box drive power supply port is controlled to supply the physical equipment based on the preset mapping relationship to achieve the target functional scenario.

Benefits of technology

It reduces vehicle power consumption, improves energy saving effect, and decouples functional scenarios and physical equipment through abstract equipment decoupling, adapts to equipment distribution of different models, improving the applicability and flexibility of the method.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024135624_12062025_PF_FP_ABST
    Figure CN2024135624_12062025_PF_FP_ABST
Patent Text Reader

Abstract

Provided are a vehicle scenario-based management method and apparatus, a medium, and a device. The vehicle scenario-based management method comprises: acquiring a triggering signal, and on the basis of a target functional scenario corresponding to the triggering signal, identifying a corresponding target abstract device; on the basis of the target abstract device and on the basis of a preset mapping relationship, determining a corresponding first target device and a corresponding second target device; and controlling the second target device to manage the first target device, so that the first target device realizes the target functional scenario by means of a target entity device.
Need to check novelty before this filing date? Find Prior Art

Description

Vehicle scenario management method, device, medium and equipment CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application discloses and claims priority to Chinese patent applications No. 2023116582618 and No. 2023116605963 filed on December 4, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present disclosure relates to the field of vehicle management technology, and in particular to a scenario-based vehicle management method, apparatus, medium, and equipment. Background Art

[0003] With the advancement of vehicle technology, the number of onboard devices has increased, leading to increased control complexity. For example, onboard electrical devices are currently powered on and off uniformly through a start switch, leaving devices not required for certain functional scenarios powered on, resulting in unnecessary energy consumption. For example, onboard controllers are currently managed primarily through global network management, directly coordinating the network status of each controller node based on network management messages, resulting in poor energy conservation. Summary of the Invention

[0004] The embodiments of the present disclosure provide a vehicle scenario management method, apparatus, medium and equipment, which can control the corresponding physical equipment according to the functional scenario at least to a certain extent, reduce vehicle power consumption and improve energy-saving effects.

[0005] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by practice of the present disclosure.

[0006] According to the first aspect of the present disclosure, a vehicle scenario management method is provided, including: obtaining a trigger signal, identifying a corresponding target abstract device according to a target functional scenario corresponding to the trigger signal; determining a corresponding first target device and a second target device based on a preset mapping relationship according to the target abstract device; and controlling the second target device to manage the first target device so that the first target device realizes the target functional scenario through the target physical device.

[0007] According to the second aspect of the present disclosure, a vehicle scenario management device is provided, including: an identification unit for obtaining a trigger signal, and identifying a corresponding target abstract device according to a target function scenario corresponding to the function trigger signal; a determination unit for determining a corresponding first target device and a second target device based on a preset mapping relationship according to the target abstract device; and a management unit for controlling the second target device to manage the first target device so that the first target device realizes the target function scenario through the target entity device.

[0008] According to the third aspect of the present disclosure, an electronic device is provided, comprising one or more processors and one or more memories, wherein at least one program code is stored in the one or more memories, and the at least one program code is loaded and executed by the one or more processors to implement the operations performed by any of the methods described in the first aspect.

[0009] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided, comprising at least one computer program instruction stored thereon, wherein the at least one computer program instruction is loaded and executed by a processor to implement the operations performed by any of the methods described in the first aspect.

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

[0011] FIG1 shows a flow chart of a vehicle scenario management method according to some embodiments of the present disclosure;

[0012] FIG2 shows a flow chart of a vehicle scenario management method according to other embodiments of the present disclosure;

[0013] FIG3 shows a software architecture diagram of the vehicle scenario management method in FIG2 ;

[0014] FIG4 shows a flow chart of a vehicle scenario management method according to yet other embodiments of the present disclosure;

[0015] FIG5 shows a software architecture diagram of the vehicle scenario management method in FIG4 ;

[0016] FIG6 shows a structural diagram of a vehicle scenario management device according to some embodiments of the present disclosure;

[0017] FIG7 shows a schematic structural diagram of an electronic device according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0018] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of the present disclosure.

[0019] In addition, the described features, structures or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure can be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, well-known methods, devices, implementations or operations are not shown or described in detail to avoid blurring various aspects of the present disclosure.

[0020] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0021] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0022] It should also be noted that the terms "first," "second," and the like in the specification and claims of the present disclosure and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, such that the embodiments of the present disclosure described herein can be implemented in an order other than that shown or described.

[0023] FIG1 shows a flow chart of a vehicle scenario management method according to some embodiments of the present disclosure. As shown in FIG1 , a vehicle scenario management method is provided, which includes but is not limited to the following steps:

[0024] Step S101: Acquire a trigger signal, and identify a corresponding target abstract device according to a target functional scenario corresponding to the trigger signal;

[0025] Step S102, determining the corresponding first target device and second target device based on the target abstract device and a preset mapping relationship; and

[0026] Step S103: Control the second target device to manage the first target device, so that the first target device implements the target functional scenario through the target entity device.

[0027] It is understood that during vehicle use, various functional scenarios may be involved, such as body control, air conditioning control, high-voltage chassis control, cabin control, autonomous driving control, door unlocking, window opening control, and image acquisition control. Different functional scenarios may involve different physical devices. In some embodiments, the physical devices may include electrical devices, physical controllers, and other devices.

[0028] In some embodiments, the trigger signal includes a function trigger signal and a wake-up trigger signal. Different function scenarios require corresponding function trigger signals to trigger. For example, unlocking a vehicle door requires sending an unlock signal to the vehicle. If the unlock signal is sent via the vehicle key, the unlock signal is the function trigger signal for unlocking the vehicle door. When implementing a certain function scenario, a wake-up trigger signal is also required to notify the central integrated controller, which will subsequently wake up the physical controller implementing the function scenario.

[0029] It should be noted that before the vehicle is put into use, for example, during the vehicle development phase, by sorting out the functional processes corresponding to each functional scenario of the vehicle, it is possible to determine the product capabilities required for the underlying layer to execute to realize the functional scenario, such as the product capabilities required for the lock execution of body control, the product capabilities required for the speaker drive of the cabin, etc. By abstracting and defining each product capability, the abstract device corresponding to the functional scenario is determined.

[0030] It should be noted that the aforementioned product capabilities refer to the abstraction of vehicle hardware resources, such as those required to provide locking, key signals, and instrument display enhancements. Product capabilities can be determined based on historical vehicle development data, and different product capabilities can be combined to create abstract devices corresponding to functional scenarios. In other words, the abstract device in the disclosed embodiments is a conceptual aggregation of individual product capabilities.

[0031] In some embodiments, the first target device may be a target power supply port, and correspondingly, the second target device is a target power distribution box. The target power distribution box may drive the target power supply port to supply power to the target power-consuming device so that the target power-consuming device can realize the target functional scenario.

[0032] In other embodiments, the first target device may be a target subnet, and correspondingly, the second target device is a target area gateway. The target subnet is mounted on the target area gateway, and the target area gateway can wake up the target subnet to wake up the entity controller in the target subnet, so that the entity controller can realize the target function scenario.

[0033] The present disclosure establishes a corresponding relationship between functional scenarios and abstract devices, as well as a mapping relationship between abstract devices and first target devices and second target devices. When a target functional scenario is triggered, the target abstract device is identified based on the corresponding relationship, and the first target device and second target device are determined based on the target abstract device. The second target device is then controlled to manage the first target device, so that the first target device implements the target functional scenario through the target physical device. The present disclosure enables the implementation of the target functional scenario by only controlling the physical device corresponding to the target abstract device, thereby reducing vehicle power consumption and improving energy-saving effects. At the same time, the functional scenario and physical device are decoupled through the abstract device, so that the functional scenario does not need to focus on specific physical devices, thereby being able to adapt to the power distribution of equipment in different vehicle models, thereby improving the applicability and flexibility of the method.

[0034] Referring to Figures 2 and 3, Figure 2 shows a flowchart of a vehicle scenario management method according to other embodiments of the present disclosure; Figure 3 shows a software architecture diagram of the vehicle scenario management method in Figure 2.

[0035] As shown in FIG2 , the trigger signal is a function trigger signal, the first target device is a target power supply port, the second target device is a target distribution box, and the vehicle scenario management method includes but is not limited to the following steps S201 to S203 .

[0036] In step S201 , a function trigger signal is acquired, and a corresponding target abstract device is identified according to a target function scenario corresponding to the function trigger signal.

[0037] It is understandable that during the use of the vehicle, it corresponds to various functional scenarios, such as body control, air conditioning control, high-voltage chassis control, cockpit control, automatic driving control, door unlocking, window opening control, image acquisition control, etc. Different functional scenarios may involve different electrical equipment; and different functional scenarios require corresponding function trigger signals to trigger. For example, unlocking the door requires sending an unlock signal to the vehicle. The unlock signal is sent through the vehicle key, and the unlock signal is the function trigger signal for unlocking the door.

[0038] In some embodiments of step S201, based on the aforementioned solution, identifying the corresponding target abstract device according to the target functional scenario corresponding to the trigger signal may include the following steps:

[0039] Step S2011: obtaining a first mapping relationship table, wherein the first mapping relationship table records the correspondence between each functional scenario and each abstract device; and

[0040] Step S2012: According to the target function scenario corresponding to the function trigger signal, query the first mapping relationship table for a target abstract device that matches the target function scenario.

[0041] Before a vehicle is put into use, the disclosed embodiments construct a first mapping table to record the correspondence between each functional scenario and each abstract device. For example, each abstract device is assigned a device identifier, i.e., a device ID, and the functional scenario is matched with the corresponding device ID to establish a correspondence between the two. It is understood that a functional scenario may correspond to multiple abstract devices, i.e., multiple device IDs.

[0042] After constructing the first mapping relationship table, when the target function scenario is triggered, the corresponding target abstract device can be determined by querying the first mapping relationship table to implement subsequent power distribution control, thereby improving vehicle power distribution efficiency.

[0043] It is worth noting that there is not necessarily a one-to-one correspondence between abstract devices and physical devices. For ease of understanding, the relationship between abstract devices and physical devices is illustrated here. For example: if unlocking a car door involves four abstract door modules, that is, one car door corresponds to one door module, then the four door modules can be the abstract devices referred to in the disclosed embodiment, but in the actual hardware deployment of the vehicle, the functions of the four abstract door modules may be implemented by four actual controllers, three actual controllers, two actual controllers, or one actual controller. Therefore, the relationship between abstract devices and physical devices may be one-to-one, many-to-one, or one-to-many, which is not limited here.

[0044] In step S202, the corresponding target power supply port and target power distribution box are determined according to the target abstract device based on a preset mapping relationship.

[0045] In some embodiments of step S202, based on the aforementioned solution, determining the corresponding target power supply port and target power distribution box according to the target abstract device and based on a preset mapping relationship may include:

[0046] Step S2021: obtaining a second mapping relationship table, wherein the second mapping relationship table records the correspondence between each abstract device, each power supply port, and each distribution box; and

[0047] Step S2022: According to the target abstract device, query the second mapping relationship table for a target power supply port and a target distribution box that match the target abstract device.

[0048] It is understood that in order to implement regional power supply management for various electrical devices in the vehicle, the disclosed embodiment is provided with multiple power distribution boxes for zoned power supply management of electrical devices in different areas. Each power distribution box is provided with multiple power supply ports, and each power supply port is electrically connected to an actual device. Therefore, the power distribution box can supply power to the actual device through the power supply port. In other words, the power supply port and the actual device have a corresponding relationship based on the electrical connection relationship.

[0049] On the basis of the above, the embodiment of the present disclosure is implemented before the vehicle is put into use, for example, in the vehicle development stage. According to the requirements of different functional scenarios, a corresponding relationship between each abstract device, each power supply port and each distribution box is established. For example: in the functional scenario of unlocking the car door, 4 door modules are required to support the implementation of this functional scenario, and the vehicle is configured with 2 actual controllers for the 4 door modules. There is an actual electrical connection relationship between the 2 actual controllers and one or two power supply ports. Therefore, the corresponding power supply port can be determined according to the actual controller. Since the power supply port is provided in the distribution box, the corresponding distribution box can be determined based on the power supply port, so that the corresponding relationship between the 4 door modules and the corresponding power supply ports and the distribution box can be established.

[0050] For ease of understanding, the embodiment of the present disclosure shows one of the mapping relationships between various abstract devices, various power supply ports, and various power distribution modules in Table 1, as shown in the following table:

[0051] Table 1 Second mapping relationship table

[0052] As shown in Table 1, each abstract device, each power port, and each power distribution box is configured with an ID, allowing for quick identification of the corresponding device, port, or power distribution box. In some embodiments, for a door module with a device ID of 0x001, its corresponding power distribution box ID is power distribution box 1, and its corresponding power port ID is 0x111.

[0053] It is understandable that different car models may have different functional scenarios, so the configurations of the corresponding abstract devices, distribution boxes, and power supply ports may also be different. In order to improve the applicability of the method of the embodiment of the present disclosure to different car models, the specific configurations of each car model can be adapted through the car model configuration word. In some embodiments, for a certain car model, there is a door module with a device ID of 0x001, a light module with a device ID of 0x002, but no parking module with a device ID of 0x003. Through the configuration words of each car model, the second mapping relationship table corresponding to the car model can be quickly matched.

[0054] After identifying the target abstract device based on the second mapping table, the target power port and target distribution box that match the target abstract device can be determined by querying the second mapping table. In some embodiments, the target abstract device is a light module with a device ID of 0x002. The target power port is determined to be the power port with an ID of 0x222, and the target distribution box is determined to be the distribution box with an ID of 1.

[0055] In step S203, the target power distribution box is controlled to drive the target power supply port to supply power to the target physical device, where the target physical device is used to implement the target functional scenario.

[0056] In some embodiments of step S203, based on the aforementioned scheme, controlling the target distribution box to drive the target power supply port to supply power to the target physical device may include: sending a power-on request for the target power supply port to the target distribution box, so that the target distribution box drives the target power supply port to supply power to the target physical device according to the power-on request.

[0057] In some embodiments of step S203, based on the aforementioned scheme, the target power supply port is provided with a first identifier, and the target distribution box is provided with a second identifier, and sending a power-on request for the target power supply port to the target distribution box so that the target distribution box drives the target power supply port to power the target entity device according to the power-on request may include: sending a power-on request for the target power supply port to the target distribution box according to the second identifier, and the power-on request includes the first identifier, so that the target distribution box locates the target power supply port according to the first identifier and drives the target power supply port to power the target entity device.

[0058] It is understandable that the first identifier can be the ID of the target power supply port, and the second identifier can be the identifier of the target distribution box. It is understandable that the first identifier is an abstract identifier of the target power supply port, and the second identifier is an abstract identifier of the target distribution box. Depending on the vehicle model, different target power ports can be configured for the first identifier, and different target distribution boxes can be configured for the second identifier. When sending a power-on request to the target distribution box, the corresponding target distribution box can be determined based on the second identifier, and then the first identifier can be carried in the power-on request, so that the target distribution box can be located at the target power supply port provided on the distribution box based on the first identifier, so as to drive the target power supply port to power the target entity device.

[0059] In some embodiments, based on the aforementioned scheme, before controlling the target distribution box to drive the target power supply port to supply power to the target physical device, the method may also include: obtaining the power-on status of the target power supply port, and if the target power supply port is in the power-off state, controlling the target distribution box to drive the target power supply port to supply power to the target physical device.

[0060] It is understandable that since the same physical device may be used to implement different functional scenarios, for example, functional scenario A and functional scenario B both require the use of physical device C to implement. Therefore, it is possible that the vehicle is already implementing functional scenario B before implementing functional scenario A, and physical device C may already be in a powered-on state. In this case, when functional scenario A is triggered and the corresponding target power supply port is determined to be the power supply port connected to physical device C, the target power supply port can be first detected. After determining that the target power supply port is in a powered-off state, the target power distribution box can be controlled to drive the target power supply port to power the target physical device, thereby avoiding invalid issuance of control instructions.

[0061] In some embodiments, based on the aforementioned scheme, after controlling the target distribution box to drive the target power supply port to supply power to the target physical device, the method may also include: obtaining the current information of the target power supply port fed back by the target distribution box; obtaining an optimized power distribution strategy generated based on the current information; and performing power distribution optimization according to the optimized power distribution strategy.

[0062] It should be noted that the current information of the target power supply port is uploaded to the cloud, and the cloud can optimize the power distribution strategy through big data analysis. In some embodiments, if the big data analysis finds that the power distribution time is too long, the power distribution time can be reduced to achieve power distribution optimization.

[0063] Table 2 shows the current information of each power supply port corresponding to Table 1.

[0064] Table 2 Current information of power supply port

[0065] In some embodiments, based on the aforementioned solution, the method is implemented based on a service-oriented architecture.

[0066] As shown in Figure 3, the vehicle scenario management method of the embodiment of the present disclosure is implemented based on a service-oriented architecture. Based on the service-oriented architecture, the embodiment of the present disclosure divides the software system into a functional logic layer, a device control layer, and a device sensor execution layer.

[0067] The functional logic layer is used to process the functional logic (for example, responding to the function trigger signal and identifying the corresponding target abstract device according to the function trigger signal), and after the target entity device corresponding to the target abstract device is powered on, controlling the control service corresponding to the target entity device, such as body control service, air conditioning control service, high-voltage chassis control service, cockpit control service and automatic driving control service, etc.

[0068] The device control layer includes the power supply management service and the port power control service. The power supply management service is used to establish the corresponding relationship between each abstract device, each distribution box, and each power supply port, namely the second mapping relationship table, and is used for power distribution management and monitoring. The port power control service is used to send power requests to the target power supply port corresponding to the target physical device based on the port status (e.g., open, closed, faulty).

[0069] The device sensing execution layer includes the driver management service and the current monitoring service. The driver management service receives the ID of the target power port requested by the device power control service and drives and monitors the target power port. The current monitoring service monitors the drive current and status of the target power port and feeds this information back to the power device management service and the port power control service.

[0070] It can be understood that service-oriented architecture combines different functional units (services) of the system through well-defined interfaces and protocols. These services are independent and reusable and can interact across multiple systems and organizations, thereby improving the flexibility, scalability and maintainability of the software system.

[0071] Based on the above disclosed content, the embodiment of the present disclosure establishes a correspondence between functional scenarios and abstract devices, as well as a mapping relationship between abstract devices and power supply ports and distribution boxes. Then, when the target functional scenario is triggered, the target abstract device is identified according to the correspondence, the target power supply port and target distribution box are determined according to the target abstract device, and then the target distribution box is controlled to drive the target power supply port to power the target physical device to realize the target functional scenario. The present disclosure enables the realization of the target functional scenario to only require the physical device corresponding to the target abstract device to be powered, optimizes the vehicle power distribution strategy, and reduces vehicle battery loss. At the same time, the functional scenario and the physical device are decoupled through the abstract device, so that the functional scenario does not need to focus on the physical device, thereby being able to adapt to the power distribution of equipment of different models, improving the applicability and flexibility of the method.

[0072] 4 and 5 , FIG4 shows a flow chart of a vehicle scenario management method according to some further embodiments of the present disclosure; FIG5 shows a software architecture diagram of the vehicle scenario management method in FIG4 .

[0073] As shown in Figure 4, the trigger signal is a wake-up trigger signal, the first target device is the target subnet, and the second target device is the target regional gateway. The vehicle scenario network management method can be executed on a central integrated controller, and the central integrated controller is communicated with each regional gateway. Each regional gateway is equipped with at least one subnet, and each subnet is equipped with at least one physical controller; the method includes but is not limited to the following steps S401 to S404.

[0074] In step S401, a wake-up trigger signal is acquired, and a corresponding target abstract device is identified according to a target functional scenario corresponding to the wake-up trigger signal.

[0075] With the development of intelligent, electrified and networked vehicles, the number of on-board electrical devices has gradually increased, which has led to an increase in on-board controllers, and in turn, an increase in the number of messages in the bus, and an increase in the network complexity of the vehicle. At present, the network status of each controller node is mainly coordinated and managed based on the network management message directly through global network management to coordinate the communication behavior between the controller nodes. In some embodiments, during the network management process, each on-board controller is grouped and bound according to its function. Due to the bit limit of the network management message PNC (partial network cluster), the grouping of on-board controllers is also limited. In some embodiments, there may be overlap in the controllers corresponding to each function. The overlapping controllers will repeatedly send and receive messages from the central integrated controller, resulting in increased power consumption. In some embodiments, when the vehicle function is adjusted or the network management topology is adjusted, each controller related to the function needs to be adaptively adjusted, which increases the development cost of the vehicle and reduces development efficiency. The embodiment of the present disclosure uses a regional gateway to perform local network management on each subnet. Each subnet does not need to perform wake-up identification, which reduces vehicle power consumption and improves energy saving.

[0076] It's understandable that during vehicle use, a variety of functional scenarios may occur, such as body control, air conditioning control, high-voltage chassis control, cockpit control, autonomous driving control, door unlocking, window opening control, and image acquisition control. Different functional scenarios may involve different physical controllers. Furthermore, when a specific functional scenario is implemented, a wake-up trigger signal is required to notify the central integrated controller, which subsequently wakes up the physical controller implementing that functional scenario. Therefore, the network management software system needs to collect the wake-up trigger signal.

[0077] In the disclosed embodiment, the wake-up trigger signal is collected by each regional gateway. The signal source of the wake-up trigger signal can be an IO (Input Output) wake-up source, a CAN (Controller Area Network) wake-up source, or a LIN (Local Interconnect Network) wake-up source. The content of the wake-up trigger signal can be waking up the vehicle, unlocking the door, waking up the air conditioning controller, etc. The content of the wake-up trigger signal varies depending on the functional scenario and is not limited here.

[0078] Before a vehicle is put into use, the disclosed embodiments construct a mapping table to record the correspondence between each functional scenario and each abstract device. For example, each abstract device is assigned a device identifier, i.e., a device ID, and the functional scenario is matched with the corresponding device ID to establish a correspondence between the two. It is understood that a functional scenario may correspond to multiple abstract devices, i.e., multiple device IDs.

[0079] After constructing the mapping relationship table, when the target function scenario is triggered, the corresponding target abstract device can be determined by querying the mapping relationship table to implement subsequent network management, thereby improving the efficiency of vehicle network management.

[0080] It is worth noting that there is not necessarily a one-to-one correspondence between abstract devices and physical devices (such as physical controllers). For ease of understanding, the relationship between abstract devices and physical devices is illustrated here. For example: if the door unlocking involves 4 abstract door modules, that is, one door corresponds to one door module, then the 4 door modules can be the abstract devices referred to in the embodiment of the present disclosure, but in the actual hardware deployment of the vehicle, the functions of the 4 abstract door modules may be implemented by 4 physical controllers, 3 physical controllers, 2 physical controllers, or 1 physical controller. Therefore, the relationship between the abstract device and the physical device may be a one-to-one correspondence, a many-to-one correspondence, or a one-to-many correspondence, which is not limited here.

[0081] In step S402, a corresponding target regional gateway and a target subnet are determined according to the target abstract device based on a preset third mapping relationship, and the target subnet is mounted on the target regional gateway.

[0082] In some embodiments of step S402, based on the aforementioned solution, determining the corresponding target regional gateway and target subnet according to the target abstract device and based on a preset first mapping relationship may include:

[0083] Step S4021: Obtain a third mapping relationship table, wherein the third mapping relationship table records the correspondence between each abstract device, each regional gateway, and each subnet, and each regional gateway is connected to at least one subnet; and

[0084] Step S4022: According to the target abstract device, query the third mapping relationship table for a target regional gateway and a target subnet that match the target abstract device.

[0085] It can be understood that in order to perform regional network management of various controllers of the vehicle, the embodiment of the present disclosure is provided with multiple regional gateways, each regional gateway is equipped with at least one subnet, and each subnet is provided with at least one physical controller.

[0086] On the basis of the above, the embodiment of the present disclosure is established before the vehicle is put into use, for example, in the vehicle development stage. According to the requirements of different functional scenarios, the corresponding relationship between each abstract device, each regional gateway and each subnet is established. For example: in the functional scenario of unlocking the car door, 4 door modules are required to support the implementation of this functional scenario, and the vehicle is configured with 2 physical controllers for the 4 door modules. The 2 physical controllers may be located in the same subnet or in different subnets. Assuming that the 2 physical controllers are respectively located in subnet 1 and subnet 2, and subnet 1 and subnet 2 are both located in regional gateway 1, then the target regional gateway corresponding to the 4 door modules (target abstract devices) is regional gateway 1, and the target subnets corresponding to the 4 door modules are subnet 1 and subnet 2.

[0087] For ease of understanding, the embodiment of the present disclosure shows one of the mapping relationships between each abstract device, each regional gateway, and each subnet in Table 3, as shown in the following table:

[0088] Table 3 The third mapping relationship table

[0089] As shown in Table 3, each abstract device, each regional gateway, and each subnet is configured with an ID, so that the corresponding abstract device, regional gateway, and subnet can be quickly identified by the ID. In some embodiments, for an abstract device with a device ID of 0x001, its corresponding regional gateway ID is regional gateway 1, and its corresponding subnet ID is 0x111.

[0090] It is understandable that, since different car models may have different functional scenarios, the configurations of the corresponding abstract devices, regional gateways, and subnets may also be different. In order to improve the applicability of the method of the embodiment of the present disclosure to different car models, the specific configurations of each car model can be adapted through the car model configuration word. In some embodiments, for a certain car model, there is an abstract device 1 with a device ID of 0x001, an abstract device 2 with a device ID of 0x002, and an abstract device 3 with a device ID of 0x003, but there is no abstract device 4 with a device ID of 0x004. Through the configuration words of each car model, the second mapping relationship table corresponding to the car model can be quickly matched.

[0091] Based on the third mapping relationship table, after identifying the target abstract device, the target regional gateway and target subnet that match the target abstract device can be determined by querying the third mapping relationship table. In some embodiments, the target abstract device is abstract device 2 with a device ID of 0x002. By querying the table, the target regional gateway ID is determined to be a regional gateway with a device ID of 2, and the target subnet is determined to be a subnet with an ID of 0x222.

[0092] In step S403, a corresponding target network management message is generated according to the target regional gateway and the target subnet based on a preset fourth mapping relationship.

[0093] In some embodiments of step S403, based on the aforementioned solution, generating a corresponding target network management message based on the target regional gateway and the target subnet and based on a preset fourth mapping relationship may include:

[0094] Step S4031: Obtain a fourth mapping relationship table, wherein the fourth mapping relationship table records the correspondence between each regional gateway and each subnet and each network segment of the network management message;

[0095] Step S4032: according to the target regional gateway and the target subnet, query the target network segment corresponding to the target regional gateway and the target subnet in the fourth mapping relationship table; and

[0096] Step S4033: Set the target network segment of the network management message to generate a target network management message.

[0097] It is understood that the central integrated controller of the embodiment of the present disclosure and each regional gateway can communicate based on the CAN bus. Therefore, the central integrated controller and each regional gateway can send CAN messages to each other to exchange information. Since the CAN message is in the form of a matrix of 8 rows of bytes and 8 columns of bits, the matrix composed of each byte and each bit has multiple network segments. Therefore, the embodiment of the present disclosure pre-establishes a corresponding relationship between each regional gateway, each subnet, and the central integrated controller and each network segment in the matrix, so that it can be identified whether each regional gateway, each subnet, and the central integrated controller needs to be awakened or put into sleep based on the setting information of the network segment.

[0098] For ease of understanding, the embodiment of the present disclosure shows in Table 4 the correspondence between each regional gateway, each subnet, and the central integrated controller and each network segment of the matrix network management message, as shown in the following table:

[0099] Table 4 Fourth mapping relationship table

[0100] As can be seen from Table 4, based on the network management message, the embodiment of the present disclosure sets subnet 1 to subnet N on the CAN8 to CAN11 network segments, respectively, sets regional gateways 1 to regional gateways 4 on Bit 1 to Bit 3 of Byte 1, respectively, and sets the central integrated controller on Bit 0 of Byte 1. This establishes a correspondence between each regional gateway, each subnet, and the central integrated controller and each network segment of the matrix network management message.

[0101] In some embodiments, based on the aforementioned solution, each of the regional gateways is provided with a CAN transceiver, and each of the CAN transceivers is used to send and receive network management messages.

[0102] That is to say, the embodiment of the present disclosure only requires the hardware support of the central integrated controller on the backbone network and each regional gateway for a CAN transceiver with a CANID filtering function. The network management messages of the central integrated controller are received through each regional gateway, and the various subnets to which it is attached are awakened through the regional gateway, thereby waking up each entity controller in the subnet. Therefore, there is no need for the hardware support of each entity controller for a CAN transceiver with a CANID filtering function, thereby reducing the hardware cost of the entity controller. Since each entity controller does not need to identify the network management message, each entity controller does not need to be awakened when the central integrated controller broadcasts the network management message. Compared with the traditional entity controller that needs to be awakened first and then identify the network management message, the embodiment of the present disclosure can further reduce the power consumption of the entity controller.

[0103] In step S404, the target network management message is broadcast to each regional gateway, so that the target regional gateway wakes up the target subnet according to the target network management message.

[0104] It is understood that when the central integrated controller broadcasts the target network management message to each regional gateway, each regional gateway can determine whether to wake itself up and whether to wake up each of its associated subnets based on the setting information of each network segment in the target management message. For the target regional gateway, since the setting information in the target network management message corresponds to the target subnet, after identifying the target network management message, the target regional gateway can determine whether to wake itself up and whether to wake up each of its associated target subnets.

[0105] In some embodiments of step S404, based on the aforementioned scheme, the target area gateway wakes up the target subnet according to the target network management message, which may include: the target area gateway identifies the setting information of the target network segment in the target network management message, and wakes up the target subnet according to the identification result.

[0106] It is understood that when the target subnet needs to be awakened, the target subnet's setting information may be 1. Similarly, when the target subnet needs to be put to sleep, the target subnet's setting information may be 0. The principle of the target subnet's sleep control is the same as that of the wake-up control, and will not be further described here.

[0107] In some embodiments, based on the aforementioned scheme, the method may further include: obtaining the working status of the target subnet, and if the target subnet is in a dormant state, generating a corresponding target network management message based on the target area gateway and the target subnet and a preset fourth mapping relationship.

[0108] It is understandable that since the same subnet may be used to implement different functional scenarios, for example, both functional scenario A and functional scenario B need to be implemented using subnet C. Then, it is possible that the vehicle is already implementing functional scenario B before implementing functional scenario A. At this time, subnet C may already be in the awake state. Then, when the corresponding target subnet is determined to be subnet C after functional scenario A is triggered, the working status of subnet C can be detected. In some embodiments, the working status of subnet C can be detected by the target area gateway, and the detection result can be fed back to the central integrated controller. After determining that subnet C is in the dormant state, the corresponding target network management message is generated based on the preset fourth mapping relationship according to the target area gateway and the target subnet, thereby reducing the generation and transmission of messages, reducing the system workload, and playing a role in further energy saving.

[0109] In some embodiments, based on the aforementioned solution, the method is implemented based on a service-oriented architecture.

[0110] As shown in Figure 5, based on the service-oriented architecture, the embodiment of the present disclosure divides the software system into a network wake-up module, a sleep wake-up scenario management module, a device management module, a network management module, a network sleep wake-up control module and a mapping table management module. Among them, the sleep wake-up scenario management module, the device management module, the network management module and the mapping table management are deployed in the central integrated controller, and each regional gateway is deployed with a network wake-up module and a network wake-up control module respectively.

[0111] The network wake-up module is used to process various wake-up sources such as IO / CAN / LIN to identify the wake-up trigger signal, and send the wake-up trigger signal to the sleep wake-up scene trigger signal. At the same time, it sends a network management message to the central integrated controller. The network management message contains the setting information of the central integrated controller, so that the central integrated controller can wake itself up according to the setting information.

[0112] The sleep-wake-up scene management module is used to process the functional logic (for example, in response to the wake-up trigger signal, identify the corresponding target abstract device according to the function trigger signal), and after the physical device corresponding to the target abstract device is awakened, control the control service corresponding to the physical device, such as body control service, air conditioning control service, high-voltage chassis control service, cockpit control service and automatic driving control service, etc.

[0113] The mapping table management module is used to establish the mapping relationship between each abstract device, each regional gateway and each subnet, that is, the third mapping relationship table; and to establish the mapping relationship between each regional gateway and each subnet and each network segment of the network management message, that is, the fourth mapping relationship table.

[0114] The device management module is used to perform network management control on each subnet in the regional gateway based on the third mapping relationship table and the fourth mapping relationship table.

[0115] The network management module is used to identify whether there is a subnet that needs to be awakened or dormant according to the dormant or awake state of the subnet ID, and set the network segment position corresponding to the network management message (NM message) to generate the target network management message.

[0116] The network sleep and wake-up control module is used to control the corresponding network segment to sleep or wake up according to the corresponding network segment setting information in the target network management message sent by the network management module.

[0117] It can be understood that the service-oriented architecture combines different functional modules of the system through well-defined interfaces and protocols. These modules are independent and reusable and can interact across multiple systems and organizations, thereby improving the flexibility, scalability and maintainability of the software system.

[0118] Based on the above-disclosed content, the present disclosure receives the network management messages of the central integrated controller through each regional gateway, and wakes up each subnet to which it is attached through the regional gateway, thereby waking up each physical controller in the subnet, thereby eliminating the need for the hardware of each physical controller to support a CAN transceiver with CANID filtering function, thereby reducing the hardware cost of the physical controller; since each physical controller does not need to identify the network management message, each physical controller does not need to be awakened when the central integrated controller broadcasts the network management message. Compared with the traditional physical controller that needs to be awakened first and then identify the network management message, the embodiment of the present disclosure can further reduce the power consumption of the physical controller.

[0119] The present disclosure divides local network management according to network segments. Compared with the traditional division according to functions, it can decouple vehicle network management from functions and perform multi-layer decoupling through the mapping relationship between abstract devices, regional gateways and subnets. Therefore, when the vehicle function or network topology is adjusted, the mapping relationship table and configuration information can be updated to adapt to different vehicle models, thereby improving the adaptability and flexibility of the method.

[0120] The following describes an embodiment of the device of the present disclosure, which can be used to perform the method in the above embodiment of the present disclosure. For details not disclosed in the embodiment of the device of the present disclosure, please refer to the embodiment of the method in the above embodiment of the present disclosure.

[0121] FIG6 shows a structural diagram of a vehicle scenario management device according to some embodiments of the present disclosure. As shown in FIG6 , a vehicle scenario management device is provided, which may include: an identification unit 601 for acquiring a trigger signal and identifying a corresponding target abstract device based on a target functional scenario corresponding to the trigger signal; a determination unit 602 for determining a corresponding first target device and a corresponding second target device based on a preset mapping relationship based on the target abstract device; and a management unit 603 for controlling the second target device to manage the first target device so that the first target device implements the target functional scenario through the target physical device. In some embodiments, the trigger signal is a functional trigger signal, the first target device is a target power supply port, and the second target device is a target distribution box. The management unit includes a control subunit (not shown). The identification unit 601 is further configured to acquire a functional trigger signal and identify a corresponding target abstract device based on a target functional scenario corresponding to the functional trigger signal; the determination unit 602 is further configured to determine a corresponding target power supply port and a target distribution box based on a preset mapping relationship based on the target abstract device; and the control subunit 603 is configured to control the target distribution box to drive the target power supply port to power the target physical device, and the target physical device is configured to implement the target functional scenario.

[0122] In some embodiments, the trigger signal is a wake-up trigger signal, the first target device is the target subnet, and the second target device is the target regional gateway. The management unit 603 includes a generation subunit (not shown) and a broadcast subunit (not shown). The identification unit 601 can also be used to obtain the wake-up trigger signal and identify the corresponding target abstract device based on the target functional scenario corresponding to the wake-up trigger signal; the determination unit 602 is also used to determine the corresponding target regional gateway and target subnet based on the target abstract device and the preset third mapping relationship, and the target subnet is mounted on the target regional gateway; the generation subunit is used to generate the corresponding target network management message based on the preset fourth mapping relationship according to the target regional gateway and the target subnet; and the broadcast subunit is used to broadcast the target network management message to each regional gateway so that the target regional gateway wakes up the target subnet according to the target network management message.

[0123] Figure 7 shows a schematic diagram of the structure of an electronic device according to some embodiments of the present disclosure. As shown in Figure 7, an electronic device is provided, including one or more processors and one or more memories, wherein the one or more memories store at least one program code, and the at least one program code is loaded and executed by the one or more processors to implement the operations performed by any of the methods described in the first aspect.

[0124] As shown in Figure 7, electronic device 700 is implemented as a general-purpose computing device. Components of electronic device 700 may include, but are not limited to, the aforementioned at least one processing unit 710, the aforementioned at least one storage unit 720, and a bus 730 connecting various system components (including storage unit 720 and processing unit 710).

[0125] The storage unit stores program code, which can be executed by the processing unit 710, so that the processing unit 710 performs the steps described in the above "Example Method" section of this specification according to various exemplary embodiments of the present disclosure.

[0126] The storage unit 720 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 421 and / or a cache memory unit 722 , and may further include a read-only memory unit (ROM) 723 .

[0127] The storage unit 720 may also include a program / utility 724 having a set (at least one) of program modules 725, such program modules 725 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0128] Bus 730 may represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0129] The electronic device 700 can also communicate with one or more external devices 800 (e.g., a keyboard, a pointing device, a Bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 700, and / or any device that enables the electronic device 700 to communicate with one or more other computing devices (e.g., a router, a modem, etc.). Such communication can occur via an input / output (I / O) interface 750. Furthermore, the electronic device 700 can communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network such as the Internet) via a network adapter 760. As shown, the network adapter 760 communicates with other modules of the electronic device 700 via a bus 730. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 700, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0130] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope and spirit of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination of any of these. Furthermore, the functional units may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit.

[0131] In the several embodiments provided in the present disclosure, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0132] The units described as separate components may or may not be physically separate, and the components of the control device may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0133] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0134] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, in which at least one computer program instruction is stored. The at least one computer program instruction is loaded and executed by a processor to implement the operations performed by any method described in the first aspect.

[0135] The computer-readable storage medium may be a portable compact disc read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the computer-readable storage medium of the present disclosure is not limited thereto. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0136] The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0137] The program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, and the like, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a stand-alone software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the user computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0138] The foregoing is merely an embodiment of the present disclosure and is not intended to limit the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included within the scope of the claims of the present disclosure.

Claims

1. A vehicle scenario management method, comprising: Acquire a trigger signal, and identify a corresponding target abstract device according to a target functional scenario corresponding to the trigger signal; According to the target abstract device, determining a corresponding first target device and a corresponding second target device based on a preset mapping relationship; as well as The second target device is controlled to manage the first target device so that the first target device realizes the target function scenario through the target entity device.

2. The method according to claim 1, wherein: The trigger signal is a function trigger signal, the first target device is a target power supply port, the second target device is a target power distribution box, and the determining of the corresponding first target device and second target device based on the target abstract device and a preset mapping relationship includes: According to the target abstract device, determining the corresponding target power supply port and target power distribution box based on a preset mapping relationship; Correspondingly, the controlling the second target device to manage the first target device so that the first target device implements the target function scenario through the target entity device includes: The target power distribution box is controlled to drive the target power supply port to supply power to the target entity device, and the target entity device is used to realize the target functional scenario.

3. The method according to claim 2, wherein: The step of identifying a corresponding target abstract device according to a target functional scenario corresponding to the trigger signal includes: Acquire a first mapping relationship table, wherein the first mapping relationship table records the correspondence between each functional scenario and each abstract device; and According to the target function scenario corresponding to the function trigger signal, a target abstract device matching the target function scenario is searched in the first mapping relationship table.

4. The method according to claim 2, wherein: The step of determining the corresponding target power supply port and the target power distribution box according to the target abstract device based on a preset mapping relationship includes: Acquire a second mapping relationship table, wherein the second mapping relationship table records the correspondence between each abstract device, each power supply port, and each distribution box; and According to the target abstract device, the target power supply port and the target power distribution box matching the target abstract device are searched in the second mapping relationship table.

5. The method according to claim 2, wherein: The controlling the target power distribution box to drive the target power supply port to supply power to the target entity device includes: A power-on request for the target power supply port is sent to the target power distribution box, so that the target power distribution box drives the target power supply port to supply power to the target entity device according to the power-on request.

6. The method according to claim 5, wherein: The target power supply port is provided with a first identifier, the target power distribution box is provided with a second identifier, and sending a power-on request for the target power supply port to the target power distribution box so that the target power distribution box drives the target power supply port to supply power to the target entity device according to the power-on request, including: A power-on request for the target power supply port is sent to the target distribution box according to the second identifier, and the power-on request includes the first identifier, so that the target distribution box can locate the target power supply port according to the first identifier and drive the target power supply port to supply power to the target entity device.

7. The method according to claim 2, before controlling the target power distribution box to drive the target power supply port to supply power to the target entity device, the method further comprises: The power-on state of the target power supply port is obtained, and if the target power supply port is in a power-off state, the target power distribution box is controlled to drive the target power supply port to supply power to the target entity device.

8. The method according to claim 2, after controlling the target power distribution box to drive the target power supply port to supply power to the target entity device, the method further comprises: Obtaining current information of the target power supply port fed back by the target power distribution box; as well as Acquire an optimized power distribution strategy generated according to the current information; Power distribution optimization is performed according to the optimized power distribution strategy.

9. The method according to claim 1, wherein: The trigger signal is a wake-up trigger signal, the first target device is a target subnet, the second target device is a target regional gateway, the target subnet is mounted on the target regional gateway, and the corresponding first target device and second target device are determined based on the target abstract device and a preset mapping relationship, including: According to the target abstract device, determining the corresponding target regional gateway and target subnet based on a preset third mapping relationship; Correspondingly, controlling the second target device to manage the first target device includes: According to the target regional gateway and the target subnet, generating a corresponding target network management message based on a preset fourth mapping relationship; and The target network management message is broadcast to each regional gateway, so that the target regional gateway wakes up the target subnet according to the target network management message.

10. The method according to claim 9, wherein: The determining, according to the target abstract device, a corresponding target regional gateway and a target subnet based on a preset third mapping relationship includes: Obtaining the third mapping relationship table, wherein the third mapping relationship table records the correspondence between each abstract device, each regional gateway, and each subnet, and each regional gateway is equipped with at least one subnet; and According to the target abstract device, the target regional gateway and the target subnet matching the target abstract device are searched in the third mapping relationship table.

11. The method according to claim 9, wherein: The generating a corresponding target network management message based on the target regional gateway and the target subnet and based on a preset fourth mapping relationship includes: Obtain a fourth mapping relationship table, wherein the fourth mapping relationship table records the correspondence between each regional gateway and each subnet and each network segment of the network management message; According to the target regional gateway and the target subnet, querying the target network segment corresponding to the target regional gateway and the target subnet in the fourth mapping relationship table; and The target network segment of the network management message is set to generate a target network management message.

12. The method according to claim 11, wherein: The target area gateway wakes up the target subnet according to the target network management message, including: The target area gateway identifies the setting information of the target network segment of the target network management message, and wakes up the target subnet according to the identification result.

13. The method according to claim 9, further comprising: The working status of the target subnet is obtained. If the target subnet is in a dormant state, a corresponding target network management message is generated according to the target regional gateway and the target subnet based on a preset fourth mapping relationship.

14. The method according to claim 9, wherein: Each of the regional gateways is provided with a CAN transceiver, and each of the CAN transceivers is used for sending and receiving network management messages.

15. The method according to claim 1, wherein: The method is implemented based on a service-oriented architecture.

16. A vehicle scenario management device, comprising: An identification unit, used to obtain a trigger signal, and identify a corresponding target abstract device according to a target functional scenario corresponding to the trigger signal; A determination unit, configured to determine, according to the target abstract device, a corresponding first target device and a corresponding second target device based on a preset mapping relationship; as well as A management unit is used to control the second target device to manage the first target device so that the first target device realizes the target function scenario through the target entity device.

17. The device according to claim 16, wherein: The trigger signal is a function trigger signal, the first target device is a target power supply port, the second target device is a target power distribution box, the management unit includes a control subunit, and the determination unit is further used to determine the corresponding target power supply port and target power distribution box according to the target abstract device based on a preset mapping relationship; The control subunit is used to control the target power distribution box to drive the target power supply port to supply power to the target physical device, and the target physical device is used to realize the target functional scenario.

18. The device according to claim 16, wherein: The trigger signal is a wake-up trigger signal, the first target device is a target subnet, the second target device is a target regional gateway, the target subnet is mounted on the target regional gateway, and the determination unit is further used to determine the corresponding target regional gateway and target subnet according to the target abstract device based on a preset third mapping relationship; The management unit comprises: A generating subunit, configured to generate a corresponding target network management message based on a preset fourth mapping relationship according to the target regional gateway and the target subnet; as well as The broadcast subunit is used to broadcast the target network management message to each regional gateway, so that the target regional gateway wakes up the target subnet according to the target network management message.

19. A computer-readable storage medium, comprising at least one computer program instruction stored thereon, wherein the at least one computer program instruction is loaded and executed by a processor to implement the operations performed by the method according to any one of claims 1 to 15.

20. An electronic device, comprising one or more processors and one or more memories, wherein the one or more memories store at least one program code, and the at least one program code is loaded and executed by the one or more processors to implement the operations performed by any of the methods described in claims 1-15.

Citation Information

Patent Citations

  • SOA-based vehicle local network wake-up method, system and device, and medium

    CN116347573A

  • Vehicle sleep awakening method and device, vehicle and storage medium

    CN116909638A

  • Vehicle scenarized power distribution method and device, medium and equipment

    CN117698603A

  • Vehicle scenarized network management method and device, medium and equipment

    CN117955755A

Cited By

  • Equipment management method and device, business server and storage medium

    CN121691490A