Vehicle control method and device, gateway node, vehicle, and storage medium

Abstract

The application discloses a vehicle control method and device, a gateway node, a vehicle and a storage medium. The method comprises the following steps: obtaining a first message, wherein the first message comprises a target local network cluster (PNC) identifier; determining a target network segment according to the target PNC identifier and a mask configured for each network segment of the vehicle network in the pre-acquired network configuration information, wherein each network segment is connected with at least one controller, and the mask of the network segment is configured according to the currently connected controllers of the network segment; and forwarding the first message to the target network segment, wherein the first message is used for waking up or sleeping the controllers connected with the target network segment. In the above steps, the mask is adaptively configured according to the currently connected controllers of the network segment, so that the precise wake-up and sleep control of the effective controllers in the network segment are realized, and the vehicle power consumption waste problem caused by the mismatch between the mask configuration and the actual connection state of the controllers, the device function failure or the invalid wake-up is effectively avoided.

Description

Technical Field

[0001] This application belongs to the field of vehicle technology, and in particular relates to a vehicle control method, device, gateway node, vehicle, and storage medium. Background Technology

[0002] With the surge in the number of Electronic Control Units (ECUs) and the increasing complexity of network topologies in vehicles, static power consumption control has become a key requirement for improving vehicle energy efficiency and extending driving range. Consequently, Partial Network Cluster (PNC) technology has been widely applied to in-vehicle network management. The core of PNC technology lies in the precise control of the wake-up and sleep states of different network segments and subnets through gateway nodes. The sleep / wake-up mask (PncInterestMask) is the core basis for the gateway node's decision-making.

[0003] In related technologies, the mainstream implementation of sleep / wake-up masks in PNC systems based on the Automotive Open System Architecture (AUTOSAR) is a predefined, fixed mode. Specifically, during the system design phase, engineers preset the parameter values ​​of the sleep / wake-up mask using an ARXML configuration file, and then compile this mask as a fixed constant into the ECU software program. During vehicle operation, the gateway node directly calls this fixed mask to complete the reception and forwarding judgment of PNC messages. This method can meet basic network management requirements.

[0004] When a vehicle adds a controller due to configuration upgrades or removes some controllers due to fault repairs, the fixed sleep / wake-up mask cannot be adjusted synchronously to adjust the wake-up control logic of the corresponding controller, which can easily cause network management anomalies. For example, a newly added controller may not be able to be woken up normally because the corresponding network segment is not configured with a mask, resulting in functional failure; the network segment corresponding to a removed controller may still be woken up by the mask command, causing unnecessary power consumption waste. Summary of the Invention

[0005] This application provides a vehicle control method, device, gateway node, vehicle, and storage medium. The mask is adapted and configured according to the controllers currently actually connected to the network segment. When the controllers connected to the network segment are added, removed, or replaced, the mask of the network segment is adjusted accordingly to ensure that the network segment mask always matches the currently actually connected controllers. This enables precise wake-up and sleep control of the effective controllers within the network segment, effectively avoiding the problem of wasted vehicle power consumption caused by device malfunction or invalid wake-up due to the mismatch between the mask configuration and the actual connection status of the controller.

[0006] In a first aspect, embodiments of this application provide a vehicle control method, the method comprising: Obtain the first message, which includes the target local network cluster (PNC) identifier; Based on the target PNC identifier and the mask configured for each segment of the vehicle network in the pre-acquired network configuration information, the target network segment is determined. Each network segment is connected to at least one controller, and the mask of the network segment is configured according to the controller currently connected to the network segment. The first message is forwarded to the target network segment, and the first message is used to wake up or put the controller connected to the target network segment into sleep mode.

[0007] In one embodiment of this application, before determining the target network segment based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information, the method further includes: Obtain the current configuration information of each network segment after the vehicle is powered on this time, the current configuration information including the identifier of the controller currently configured in the network segment; For each network segment, reference configuration information for that network segment is obtained. This reference configuration information is the configuration information of the network segment obtained after the vehicle was last powered on. If the current configuration information of the network segment is different from the reference configuration information, the current mask of the network segment is updated.

[0008] In one embodiment of this application, updating the current mask of the network segment includes: Based on the current configuration information of the network segment and the reference configuration information of the network segment, a first controller is determined, wherein the first controller is a controller added or deleted from the network segment; The first mask of the network segment is determined based on the PNC identifier pre-configured for the first controller; The current mask of the network segment is updated using the first mask.

[0009] In one embodiment of this application, determining the first mask of the network segment based on the PNC identifier pre-configured for the first controller includes: If the first controller is a newly added controller in the network segment, then the current mask of the network segment is converted into binary to obtain the value corresponding to multiple bits. Each bit corresponds to one of the multiple PNC identifiers. The multiple PNC identifiers include the PNC identifier pre-configured for each controller of the vehicle. Change the value of the bit corresponding to the PNC identifier of the first controller among the values ​​of the plurality of bits to a first preset value to obtain updated values ​​of the plurality of bits; The values ​​corresponding to the updated bits are converted to decimal to obtain the first mask of the network segment.

[0010] In one embodiment of this application, determining the first mask of the network segment based on the PNC identifier pre-configured for the first controller includes: If the first controller is the controller that the network segment is deleted from, then the current mask of the network segment is converted into binary to obtain the value corresponding to multiple bits. Each bit corresponds to one of the multiple PNC identifiers. The multiple PNC identifiers include the PNC identifier pre-configured for each controller of the vehicle. The value of the bit corresponding to the PNC identifier of the first controller among the values ​​of the plurality of bits is changed to a second preset value to obtain updated values ​​of the plurality of bits. The values ​​corresponding to the updated bits are converted to decimal to obtain the first mask of the network segment.

[0011] In one embodiment of this application, determining the target network segment based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information includes: For each network segment, each byte in the mask of the network segment is converted into binary to obtain the value of multiple bits corresponding to the network segment. Each bit corresponds to one of multiple PNC identifiers, and the multiple PNC identifiers include PNC identifiers pre-configured for each controller of the vehicle. The target network segment is determined based on the target PNC identifier and the values ​​corresponding to multiple bits for each network segment.

[0012] Secondly, embodiments of this application provide a vehicle control device, the device comprising: The acquisition module is used to acquire a first message, the first message including the target local network cluster (PNC) identifier; The determination module is used to determine the target network segment based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information. Each network segment is connected to at least one controller, and the mask of the network segment is configured according to the controller currently connected to the network segment. The transceiver module is used to forward the first message to the target network segment, and the first message is used to wake up or put the controller connected to the target network segment into sleep mode.

[0013] Thirdly, embodiments of this application provide a gateway node, including: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the vehicle control method as described in the first aspect.

[0014] Fourthly, embodiments of this application provide a vehicle including the electronic equipment described in the third aspect.

[0015] Fifthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the vehicle control method as described in the first aspect.

[0016] In a sixth aspect, embodiments of this application provide a computer program product in which instructions, when executed by a processor of a gateway node, cause the gateway node to perform the vehicle control method as described in the first aspect.

[0017] This embodiment provides a vehicle control method, device, gateway node, vehicle, and storage medium. The method involves acquiring a first message, which includes a target local network cluster (PNC) identifier; determining a target network segment based on the target PNC identifier and a mask configured for each network segment of the vehicle network in pre-acquired network configuration information, wherein each network segment connects to at least one controller, and the mask of the network segment is configured according to the controller currently connected to the network segment; and forwarding the first message to the target network segment. The first message is used to wake up or put the controller connected to the target network segment into sleep mode. In the above steps, the mask is adapted to the controller currently actually connected to the network segment. When the controllers connected within the network segment are added, removed, or replaced, the mask of the network segment is adjusted accordingly to ensure that the network segment mask always matches the currently actually connected controller. This achieves precise wake-up and sleep control of the effective controllers within the network segment, effectively avoiding the problem of wasted vehicle power consumption caused by device malfunction or invalid wake-up due to a mismatch between the mask configuration and the actual connection status of the controller. Attached Figure Description

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

[0019] Figure 1 This is a schematic flowchart of a vehicle control method provided in an embodiment of this application; Figure 2 This is a schematic diagram of the gateway node and controller provided in the embodiments of this application. Figure 1 ; Figure 3 This is a schematic diagram of the gateway node and controller provided in the embodiments of this application. Figure 2 ; Figure 4 This is another schematic flowchart of the vehicle control method provided in the embodiments of this application; Figure 5 This is a schematic diagram of the vehicle control device provided in the embodiments of this application; Figure 6 This is a schematic diagram of the gateway node provided in the embodiments of this application. Detailed Implementation

[0020] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0021] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0022] The vehicles can be private cars, such as sedans, SUVs, MPVs, or pickup trucks. They can also be commercial vehicles, such as vans, buses, small trucks, or large semi-trailers. Vehicles can be either gasoline-powered or new energy vehicles. When a vehicle is a new energy vehicle, it can be a hybrid or a pure electric vehicle.

[0023] To address the problems of the prior art, embodiments of this application provide a vehicle control method, apparatus, gateway node, vehicle, and storage medium. The vehicle control method provided in this application embodiment will be described first below.

[0024] Figure 1 A schematic flowchart of a vehicle control method according to an embodiment of this application is shown. Figure 1As shown, the vehicle control method provided in this application embodiment is applied to the vehicle's gateway node and includes the following steps 101-103, wherein: Step 101: Obtain the first message, which includes the target local network cluster (PNC) identifier.

[0025] Gateway nodes used in vehicles, such as in-vehicle gateway nodes, are also known as gateway ECUs.

[0026] In this embodiment, a first message is obtained. The first message may be sent by a controller in the vehicle to the gateway node through a network segment such as the CAN network segment. The gateway node needs to forward it to the corresponding network segment, i.e. the target network segment. The gateway node parses the first message to obtain the target PNC identifier.

[0027] Among them, the Partial Network Cluster (PNC) is the core logical group of AUTOSAR vehicle network management. The PNC identifier is the Partial Network Cluster ID (PNC ID), which is a unique digital identifier assigned to the ECU functional group that can be started and stopped independently in the AUTOSAR Partial Network (PN) architecture. It is mainly used to accurately control the subnet wake-up / sleep, realize energy consumption optimization and network management coordination, and is the basic identification unit of the vehicle network PN mechanism.

[0028] Step 102: Determine the target network segment based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information. Each network segment is connected to at least one controller, and the mask of the network segment is configured according to the controller currently connected to the network segment.

[0029] In this embodiment, each segment of the vehicle network is connected to at least one controller, and the mask of each segment is configured according to the controller currently connected to the segment.

[0030] The mask and network configuration information can be stored in the vehicle's preset storage area, which can be non-volatile memory (NVM). Because data is permanently stored in the medium itself, NVM can be read and written directly once the vehicle's power-on voltage is sufficient, without the need for additional recovery or loading operations. Since it does not have the inherent property of data loss due to power failure, it does not require backup power or data transfer when the vehicle is powered off normally or in an emergency, and can stably preserve data. Moreover, it can prevent data from being accidentally modified or damaged during power-on and power-off processes.

[0031] Specifically, the target network segment is determined based on the target PNC identifier and the pre-acquired network configuration information. The configuration information includes a mask configured for each network segment of the vehicle network. The network segments may include CAN network segments, LIN network segments, Ethernet network segments, etc. The CAN network segment may include power CAN network segments, body CAN network segments, etc.

[0032] Each network segment must connect to at least one controller. Some controllers are optional when the vehicle leaves the factory. For example, depending on the vehicle model configuration, in the basic model, one network segment 'a' may connect to controllers such as the EMS engine management controller, TCU transmission controller, and ABS anti-lock braking controller, while another network segment 'b' may connect to controllers such as the BCM body control controller and instrument cluster controller. In higher-spec models, in addition to the basic model, comfort / entertainment related controllers will be added, such as seat heating controllers, climate control zone controllers, and driver assistance controllers. These controllers can connect to network segment 'a' and / or network segment 'b'. When adding or removing controllers, the mask needs to be adjusted.

[0033] It should be noted that the network segment is not limited to the above, and may include other network segments, and the controllers connected to the network segment are not limited to the controllers mentioned above.

[0034] Step 103: Forward the first message to the target network segment. The first message is used to wake up or put the controller connected to the target network segment into sleep mode.

[0035] In this embodiment, the first message is forwarded to the target network segment, and the first message is used to wake up or put the controller connected to the target network segment into sleep mode.

[0036] The first message includes the bit corresponding to the target PNC identifier. If the bit is set to 1 (1 = wake-up / keep-alive command), the corresponding controller will wake up. If the bit is set to 0 (0 = sleep request), the corresponding controller will not wake up. After receiving the first message, the target network segment broadcasts it. Controllers connected to the target network segment receive the first message and then wake up or put the controller into sleep mode based on the message. See [link to relevant documentation]. Figure 2The target network segment is determined to be CAN2 using the above method. CAN2 connects controller A (ECU A) and controller B (ECU B). If the PNC identifier configured for controller A is PNCX and the PNC identifier configured for controller B is PNCY, the gateway node sends the first message to CAN2. If the target PNC identifier in the first message is PNCX and the corresponding bit of PNCX is set to 1, CAN2 broadcasts the first message. Both controller A and controller B can receive the first message. When controller A receives the first message, it parses it to obtain PNCX and the corresponding bit of PNCX is set to 1. Controller A determines that PNCX is the pre-configured PNC identifier and performs a wake-up operation. Controller B determines that PNCX is not the pre-configured wake-up identifier and does not perform a wake-up operation, remaining in sleep mode.

[0037] In this embodiment, a first message is obtained, which includes the target local network cluster (PNC) identifier. Based on the target PNC identifier and the mask configured for each segment of the vehicle network in the pre-acquired network configuration information, a target network segment is determined. Each network segment connects to at least one controller, and the network segment mask is configured according to the controller currently connected to the network segment. The first message is forwarded to the target network segment. The first message is used to wake up or put the controller connected to the target network segment into sleep mode. In the above steps, the mask is adapted to the controller currently actually connected to the network segment. When the controllers connected within the network segment are added, removed, or replaced, the mask of the network segment is adjusted accordingly to ensure that the network segment mask always matches the currently actually connected controller. This achieves precise wake-up and sleep control of the effective controllers within the network segment, effectively avoiding the problem of wasted vehicle power consumption caused by device malfunction or invalid wake-up due to mismatch between the mask configuration and the actual connection status of the controller.

[0038] In one embodiment of this application, before determining the target network segment based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information, the method further includes: Obtain the current configuration information of each network segment after the vehicle is powered on this time, the current configuration information including the identifier of the controller currently configured in the network segment; For each network segment, reference configuration information for that network segment is obtained. This reference configuration information is the configuration information of the network segment obtained after the vehicle was last powered on. If the current configuration information of the network segment is different from the reference configuration information, the current mask of the network segment is updated.

[0039] In this embodiment, the current configuration information of each network segment after the vehicle is powered on is obtained. The current configuration information includes the identifier of the controller currently configured in the network segment.

[0040] For example, current configuration information can be obtained from the node configuration list (ListOfNodes). The node configuration list records the configuration information of the controllers currently configured in each network segment. The configuration information of the controllers currently configured in a network segment can be determined through communication control parameters (CCP). For example, if the communication control parameter of controller a is the first identifier, the first identifier indicates that controller a is configured in network segment a, meaning that controller a is currently configured in the network segment. If the communication control parameter of controller a is the second identifier, the second identifier indicates that controller a is not configured in network segment a, meaning that controller a is not currently configured in the network segment. Reading the controller with the first identifier in the communication control parameter from the node configuration list yields the identifier of the controller currently configured in the network segment.

[0041] For each network segment, obtain the reference configuration information of the network segment. The reference configuration information is the configuration information of the network segment obtained after the vehicle was last powered on. The reference configuration information includes the identifier of the controller configured in the network segment. The reference configuration information can be obtained from the node configuration list obtained after the vehicle was last powered on. Read the controller with the first identifier whose communication control parameters are obtained from the node configuration list obtained after the vehicle was last powered on, that is, obtain the identifier of the controller configured in the network segment.

[0042] Furthermore, if the current configuration information of the network segment is different from the reference configuration information, it means that the identifiers of the controllers contained in the current configuration information and the reference configuration information are different. For example, controller a exists in the current configuration information but does not exist in the reference configuration information, or controller a does not exist in the current configuration information but exists in the reference configuration information. These are all cases where the current configuration information of the network segment is different from the reference configuration information.

[0043] If the current configuration information of a network segment differs from the reference configuration information, the subnet mask needs to be redefined to update the subnet mask.

[0044] Depending on the configured controller, the network segment mask is dynamically updated, which solves the fundamental problem in related technologies that static masks cannot adapt to changes in vehicle configuration. This ensures the accuracy of PNC routing decisions and effectively avoids the problem of wasted vehicle power consumption caused by device malfunctions or invalid wake-ups due to mismatch between mask configuration and actual controller connection status.

[0045] In one embodiment of this application, updating the current mask of the network segment includes: Based on the current configuration information of the network segment and the reference configuration information of the network segment, a first controller is determined, wherein the first controller is a controller added or deleted from the network segment; The first mask of the network segment is determined based on the PNC identifier pre-configured for the first controller; The current mask of the network segment is updated using the first mask.

[0046] In this embodiment, a first controller is determined based on the difference between the current configuration information of the network segment and the controller identifier contained in the reference configuration information. The first controller is either a controller deleted from the network segment or a controller added to the network segment. For example, if controller 'a' exists in the current configuration information but not in the reference configuration information, controller 'a' is determined to be a controller added to the network segment, i.e., the first controller; conversely, if controller 'a' does not exist in the current configuration information but exists in the reference configuration information, controller 'a' is determined to be a controller deleted from the network segment, i.e., the first controller. The aforementioned controller added to the network segment means that the vehicle has configured a new controller in the corresponding network segment, and controller deleted from the network segment means that the vehicle has removed the corresponding controller from the corresponding network segment.

[0047] Furthermore, based on the PNC identifier pre-configured for the first controller, the first mask of the network segment is determined, and the current mask of the network segment is updated using the first mask, that is, the current mask of the network segment is replaced with the first mask. The PNC identifier configured for the first controller can be obtained from the network configuration information or from the aforementioned node configuration list.

[0048] For each functional network segment of the vehicle network, the mask is configured according to the controller currently connected to it. When the actual connection relationship of the controllers in the network segment changes dynamically (such as the addition / removal of the controller, failure offline, deletion of optional components, etc.), the mask corresponding to the network segment is updated synchronously so that the control logic of the mask always matches the actual access situation of the effective controllers in the network segment, thereby realizing precise wake-up and sleep control of the effective controllers in the network segment.

[0049] In one embodiment of this application, determining the first mask of the network segment based on the PNC identifier pre-configured for the first controller includes: If the first controller is a newly added controller in the network segment, then the current mask of the network segment is converted into binary to obtain the value corresponding to multiple bits. Each bit corresponds to one of the multiple PNC identifiers. The multiple PNC identifiers include the PNC identifier pre-configured for each controller of the vehicle. Change the value of the bit corresponding to the PNC identifier of the first controller among the values ​​of the plurality of bits to a first preset value to obtain updated values ​​of the plurality of bits; The values ​​corresponding to the updated bits are converted to decimal to obtain the first mask of the network segment.

[0050] In this embodiment, if the first controller is a newly added controller in the network segment, the current mask of the network segment is converted into binary. For example, the mask of the network segment where the first controller is located consists of at least one byte, such as a mask consisting of 4 bytes: (0, 16, 32, 0). The mask is converted into binary to obtain the values ​​corresponding to multiple bits: 0000 0000, 00010000, 0010 0000, 0000 0000. Each of the multiple bits corresponds to one of the multiple PNC identifiers. The multiple PNC identifiers include the PNC identifiers pre-configured for each controller of the vehicle. The same PNC identifier in different network segments can correspond to different controllers. A PNC identifier can be used to wake up at least one controller. For example, the PNC identifiers of controllers with the same function can be the same. For example, the PNC identifiers of controllers under the charging function can be the same, or the PNC identifiers of controllers under the door control function can be the same.

[0051] Refer to Tables 1-1 to 1-4 to see the mask for a network segment. The mask is (0, 16, 32, 0). Refer to Table 1-1. The first byte of the mask is 0. Convert it to binary. The corresponding bit value is 0000 0000. Each bit corresponds to a PNC identifier. The PNC identifiers corresponding to 0000 0000 are PNC8-PNC1, respectively.

[0052] Referring to Table 1-2, the second byte of the mask is 16. Converting it to binary, the corresponding bit value is 0001 0000. Each bit corresponds to a PNC identifier. The PNC identifiers corresponding to 0001 0000 are PNC16-PNC9 respectively. For example, the PNC identifier corresponding to 1 in 0001 0000 is PNC13.

[0053] Referring to Table 1-3, the third byte of the mask is 32. Converting it to binary, the corresponding bit value is 0010 0000. Each bit corresponds to a PNC identifier. The PNC identifiers corresponding to 0010 0000 are PNC24-PNC17, respectively. For example, the PNC identifier corresponding to 1 in 0010 0000 is PNC22.

[0054] Referring to Table 1-4, the fourth byte of the mask is 0. Converting it to binary, the corresponding bit value is 0000 0000. Each bit corresponds to a PNC identifier. The PNC identifiers corresponding to 0000 0000 are PNC32-PNC25 respectively.

[0055] Table 1-1

[0056] Table 1-2

[0057] Table 1-3

[0058] Table 1-4

[0059] Furthermore, the values ​​of the bits corresponding to the PNC identifier of the first controller among the multiple bits obtained from the mask conversion are changed to the first preset value. For example, if the PNC identifier corresponding to the first controller is PNC32, the value corresponding to PNC32 is changed from 0 to 1 to obtain the updated values ​​of the multiple bits, such as: 0000 0000, 00010000, 0010 0000, 1000 0000. The updated values ​​of the multiple bits are then converted to decimal to obtain the first mask of the network segment, such as 0000 0000, 0001 0000, 0010 0000, 1000 0000, which are converted to 0, 16, 32, 128, that is, the first mask is (0, 16, 32, 128).

[0060] When a new controller is added to the network segment and the actual connection status changes, the subnet mask of the network segment is updated in real time to ensure that the control range of the network segment mask always fully matches the controllers that are actually effectively connected in the current network segment, thereby achieving precise wake-up and hibernation control of the effective controllers in the network segment.

[0061] In one embodiment of this application, determining the first mask of the network segment based on the PNC identifier pre-configured for the first controller includes: If the first controller is the controller that the network segment is deleted from, then the current mask of the network segment is converted into binary to obtain the value corresponding to multiple bits. Each bit corresponds to one of the multiple PNC identifiers. The multiple PNC identifiers include the PNC identifier pre-configured for each controller of the vehicle. The value of the bit corresponding to the PNC identifier of the first controller among the values ​​of the plurality of bits is changed to a second preset value to obtain updated values ​​of the plurality of bits. The values ​​corresponding to the updated bits are converted to decimal to obtain the first mask of the network segment.

[0062] In this embodiment, if the first controller is the controller for network segment deletion, then the current mask of the network segment is converted into binary. For example, the mask of the network segment where the first controller is located consists of at least one byte, such as a mask consisting of 4 bytes: (0, 16, 32, 128). The mask is converted into binary to obtain the values ​​corresponding to multiple bits: 0000 0000, 00010000, 0010 0000, 1000 0000.

[0063] Each of the multiple bits corresponds to one of the multiple PNC identifiers. The multiple PNC identifiers include the PNC identifier pre-configured for each controller of the vehicle. The same PNC identifier in different network segments can correspond to different controllers. One PNC identifier can be used to wake up at least one controller.

[0064] Refer to Tables 2-1 to 2-4 to see the mask for another network segment. The mask is (0, 16, 32, 128). Refer to Table 2-1. The first byte of the mask is 0. Convert it to binary. The corresponding bit value is 0000 0000. Each bit corresponds to a PNC identifier. The PNC identifiers corresponding to 0000 0000 are PNC8-PNC1, respectively.

[0065] Referring to Table 2-2, the second byte of the mask is 16. Converting it to binary, the corresponding bit value is 0001 0000. Each bit corresponds to a PNC identifier. The PNC identifiers corresponding to 0001 0000 are PNC16-PNC9 respectively. For example, the PNC identifier corresponding to 1 in 0001 0000 is PNC13.

[0066] Referring to Table 2-3, the third byte of the mask is 32. Converting it to binary, the corresponding bit value is 0010 0000. Each bit corresponds to a PNC identifier. The PNC identifiers corresponding to 0010 0000 are PNC24-PNC17. For example, the PNC identifier corresponding to 1 in 0010 0000 is PNC22.

[0067] Referring to Table 2-4, the fourth byte of the mask is 128. Converting it to binary, the corresponding bit value is 1000 0000. Each bit corresponds to a PNC identifier. The PNC identifiers corresponding to 1000 0000 are PNC32-PNC25. For example, the PNC identifier corresponding to 1 in 1000 0000 is PNC32.

[0068] Table 2-1

[0069] Table 2-2

[0070] Table 2-3

[0071] Table 2-4

[0072] Furthermore, the values ​​of the bits corresponding to the PNC identifier of the first controller among the multiple bits obtained from the mask conversion are changed to the second preset value. For example, if the PNC identifier corresponding to the first controller is PNC32, the value corresponding to PNC32 is changed from 1 to 0 to obtain the updated values ​​of the multiple bits, such as: 0000 0000, 00010000, 0010 0000, 0000 0000. The updated values ​​of the multiple bits are then converted to decimal to obtain the first mask of the network segment, such as: 0000 0000, 0001 0000, 0010 0000, 000 0000. These values ​​are converted to 0,16,32,0, that is, the first mask is (0,16,32,0).

[0073] It should be noted that the mask is not limited to four bytes; the number of bytes can be configured according to actual needs.

[0074] When a controller is deleted within a network segment and the actual connection status changes, the subnet mask of that network segment is updated synchronously in real time to ensure that the control range of the network segment mask always fully matches the controllers that are actually effectively connected within the current network segment, thereby achieving precise wake-up and hibernation control of the effective controllers within the network segment.

[0075] In one embodiment of this application, determining the target network segment based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information includes: For each network segment, each byte in the mask of the network segment is converted into binary to obtain the value of multiple bits corresponding to the network segment. Each bit corresponds to one of multiple PNC identifiers, and the multiple PNC identifiers include PNC identifiers pre-configured for each controller of the vehicle. The target network segment is determined based on the target PNC identifier and the values ​​corresponding to multiple bits for each network segment.

[0076] In this embodiment, for each network segment, each byte in the network segment mask is converted into binary to obtain the value corresponding to multiple bits of the network segment. Each bit corresponds to one of multiple PNC identifiers, and the multiple PNC identifiers include PNC identifiers pre-configured for each controller of the vehicle.

[0077] For each network segment, the target PNC identifier is matched with the PNC identifier corresponding to each bit of the network segment to determine the PNC identifier that matches the target PNC identifier.

[0078] For each network segment, if the value corresponding to the matched PNC identifier is the first preset value, then the network segment corresponding to the matched PNC identifier is the target network segment; if the value corresponding to the matched PNC identifier is the second preset value, then the network segment corresponding to the matched PNC identifier is not the target network segment.

[0079] like Figure 3 As shown, ECU A sends a first message via CAN1. The PNC identifier in the first message is PNC22, and the corresponding bit of PNC22 is set to 1. The gateway node receives the first message and obtains the target PNC identifier: PNC22. The gateway node is connected to at least one network segment, such as CAN2 and CAN3. CAN2 connects ECU B and ECU A, and CAN3 connects ECU D and ECU E. The mask of CAN2 is 0,16,32,128, and the mask of CAN3 is 0,16,0,128. The gateway node performs binary conversion on 0,16,32,128 to obtain 0000 0000, 0001 0000, 0010 0000, 1000 0000; and performs binary conversion on 0,16,0,128 to obtain 0000 0000, 0001 0000, 0000 0000, 1000 0000, the gateway node determines that the value of PNC22 in CAN2 is 1, and the gateway node determines that the value of PNC22 in CAN3 is 0, indicating that CAN2 is the target network segment. The wake-up message is sent to CAN2, and CAN2 broadcasts the wake-up message. The PNC identifier pre-configured by ECU B is PNC22, and the corresponding bit of PNC22 is set to 1. The PNC identifier pre-configured by ECU C is PNC1. When ECU B receives the wake-up message, it parses out PNC22, and the corresponding bit of PNC22 is set to 1, which is the same as its own wake-up identifier. Then ECU B performs the wake-up operation. When ECU C receives the wake-up message, it parses out PNC22, and the corresponding bit of PNC22 is not the same as its own wake-up identifier. Then ECU B goes into sleep mode.

[0080] It should be noted that the mask is not limited to four bytes; the number of bytes can be configured according to actual needs.

[0081] The mask is specifically adapted and configured based on the current actual access controller status of each network segment in the vehicle network. A one-to-one correspondence between the network segment mask and the controller under its jurisdiction is pre-established. When there is a dynamic change of adding or deleting controllers in the network segment, the mask of the network segment is immediately adapted and adjusted synchronously to ensure that the control scope of the network segment mask always fully matches the actual effective access controllers in the current network segment, thereby realizing accurate wake-up and hibernation control of effective controllers in the network segment.

[0082] In one embodiment of this application, after updating the current mask of the network segment using the first mask, the method further includes: The updated mask is stored in the vehicle's preset storage area.

[0083] In this embodiment, the updated mask is stored in a preset storage area of ​​the vehicle. The mask configured for each network segment of the vehicle network in the aforementioned pre-acquired network configuration information is also stored in the preset storage area. Optionally, the preset storage area can be a non-volatile memory (NVM). After the vehicle is powered off, the data previously stored in the NVM will not be lost, and when power is restored, all data before the power outage can be directly read from the NVM.

[0084] Figure 4 A schematic flowchart of a vehicle control method according to an embodiment of this application is shown. Figure 4 As shown, the vehicle control method provided in this application embodiment is applied to the vehicle's gateway node and includes the following steps 401-406, wherein: Step 401: Determine whether the communication control parameters in the current node configuration list have been updated.

[0085] In this embodiment, it is determined whether the vehicle is powered on for the first time. If the vehicle is not powered on for the first time, the current node configuration list of the vehicle is obtained. The current node configuration list includes the configuration information of the controllers currently configured in each network segment. The configuration information of the controllers currently configured in the network segment can be obtained through Communication Control Parameters (CCP). The reference node configuration list obtained after the vehicle was last powered on is also obtained. The reference node configuration list includes the configuration information of the controllers configured in each network segment. Based on the current node configuration list and the reference node configuration list, it is determined whether the Communication Control Parameters (CCP) in the current node configuration list has been updated. Whether it has been updated is mainly determined by the value of the Communication Control Parameters. If the value of the CCP of a certain controller is 1 in the current node configuration list and 0 in the reference node configuration list, it means that a new controller has been added, and it is determined that the CCP in the current node configuration list has been updated. If the value of the CCP of each controller in the current node configuration list and the value in the reference node configuration list are the same, it means that no new controller has been added, and the mask stored in the NVM does not need to be updated. The mask stored in the Non-Volatile Memory (NVM) continues to be used to perform routing.

[0086] It should be noted that non-volatile memory is a physical storage medium that can retain data even after power is lost, so it can be stored in NNM.

[0087] Optionally, if the vehicle is powered on for the first time, the memory value is read first from the NVM and used directly for routing. Alternatively, routing is performed according to the mask predefined value stored in the NVM, which can be the default value.

[0088] Step 402: If yes, calculate the mask.

[0089] In this embodiment, if the CCP is updated, the mask is recalculated (that is, if the current configuration information of the network segment is different from the reference configuration information, the current mask of the network segment is updated).

[0090] Step 403: Determine if the mask has been updated. If yes, proceed to step 404a; otherwise, proceed to step 404b.

[0091] In this embodiment, after determining whether the mask needs updating and calculating the new mask, a flag bit needs to be updated. The dynamic mask update is not periodic or unconditional; instead, it is triggered by a key condition, such as a change in the CCP value of any controller, or a change in the CCP value of a specific controller. The specific controller is pre-set and may be a controller under close monitoring. This triggering condition is typically managed with a flag bit. This precisely solves the reliability problem of blindly updating the NVM, which could shorten its lifespan. Mask calculation and writing to the NVM are only performed when the CCP changes. This significantly reduces the number of writes to the NVM, substantially improving the reliability and lifespan of the ECU and the entire system, while avoiding unnecessary resource consumption.

[0092] Step 404a: Set the flag to True.

[0093] In this embodiment, if the mask is updated, the flag is set to True, which triggers the update. The newly calculated mask and the current node configuration list are written to NVM for persistent storage, and the flag is cleared or updated.

[0094] Step 404b: Set the flag to False.

[0095] In this embodiment, if the mask is not updated, the flag is set to False, meaning that no update is needed. The subsequent routing is performed using the mask stored in NVM, which is the mask used during the last power-on.

[0096] Step 405: Store the mask in NVM.

[0097] In this embodiment, if the flag is set to True, the new mask is stored in the NVM, and routing is performed based on the mask stored in the NVM.

[0098] Step 406: Perform routing based on the mask stored in NVM.

[0099] In this embodiment, routing is performed based on the mask stored in the NVM. Specifically, a first message is obtained, wherein the first message includes a target PNC identifier. Based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information, the target network segment is determined, and the first message is sent to the target network segment. The first message is used to wake up or put into sleep mode the controller connected to the target network segment.

[0100] The PNC gateway's sleep / wake-up mask is transformed from a static constant determined during the AUTOSAR design phase into a dynamic variable calculated in real-time by a preset algorithm based on the actual vehicle configuration (ListOfNodes) during ECU operation. This solves the fundamental problem that static masks cannot adapt to changes in vehicle configuration. Regardless of whether the vehicle is high-end, low-end, or has added equipment later, as long as the configuration node list reflects the actual situation, the calculated mask can accurately match the current network topology, thus ensuring the accuracy of PNC routing decisions and avoiding functional failures or energy waste. Furthermore, upon subsequent power-up, the memory value is preferentially read from the NVM and directly used for routing. This forms a complete vehicle network PNC processing system with modules such as configuration awareness, intelligent computing, conditional storage, and efficient execution working collaboratively.

[0101] Figure 5 A structural diagram of the vehicle control device provided in an embodiment of this application is shown. Figure 5 As shown, the vehicle control device 500 includes: The acquisition module 501 is used to acquire a first message, the first message including the target local network cluster (PNC) identifier; The determining module 502 is used to determine the target network segment based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information, wherein each network segment is connected to at least one controller, and the mask of the network segment is configured according to the controller currently connected to the network segment; The transceiver module 503 is used to forward the first message to the target network segment, and the first message is used to wake up or put the controller connected to the target network segment into sleep mode.

[0102] In one embodiment of this application, the device further includes an update module; The acquisition module is further configured to acquire the current configuration information of each network segment after the vehicle's current power-on, the current configuration information including the identifier of the controller currently configured for the network segment; for each network segment, acquire reference configuration information of the network segment, the reference configuration information being the configuration information of the network segment acquired after the vehicle's last power-on, and... The update module is used to update the current mask of the network segment if the current configuration information of the network segment is different from the reference configuration information.

[0103] In one embodiment of this application, the update module is further configured to determine a first controller based on the current configuration information of the network segment and the reference configuration information of the network segment, wherein the first controller is a newly added controller or a deleted controller in the network segment; determine a first mask of the network segment based on a PNC identifier pre-configured for the first controller; and update the current mask of the network segment using the first mask.

[0104] In one embodiment of this application, the update module is specifically configured to, if the first controller is a newly added controller in the network segment, perform binary conversion on the current mask of the network segment to obtain values ​​corresponding to multiple bits, each bit corresponding to one of multiple PNC identifiers, the multiple PNC identifiers including PNC identifiers pre-configured for each controller of the vehicle; change the value of the bit corresponding to the PNC identifier of the first controller among the multiple values ​​corresponding to the multiple bits to a first preset value to obtain updated values ​​corresponding to the multiple bits; and perform decimal conversion on the updated values ​​corresponding to the multiple bits to obtain the first mask of the network segment.

[0105] In one embodiment of this application, the update module is specifically configured to, if the first controller is the controller to be deleted from the network segment, perform binary conversion on the current mask of the network segment to obtain values ​​corresponding to multiple bits, each bit corresponding to one of multiple PNC identifiers, the multiple PNC identifiers including PNC identifiers pre-configured for each controller of the vehicle; change the value of the bit corresponding to the PNC identifier of the first controller among the multiple values ​​corresponding to the multiple bits to a second preset value to obtain updated values ​​corresponding to the multiple bits; and perform decimal conversion on the updated values ​​corresponding to the multiple bits to obtain the first mask of the network segment.

[0106] In one embodiment of this application, the determining module is specifically used to perform binary conversion on each byte in the mask of each network segment to obtain the value corresponding to multiple bits of the network segment, each bit corresponding to one of multiple PNC identifiers, the multiple PNC identifiers including PNC identifiers pre-configured for each controller of the vehicle; and to determine the target network segment based on the target PNC identifier and the value corresponding to the multiple bits of each network segment.

[0107] In one embodiment of this application, the device further includes a processing module; The processing module is used to store the updated mask in a preset storage area of ​​the vehicle.

[0108] The vehicle control device provided in this application embodiment can realize the various processes implemented in the aforementioned vehicle control method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0109] Figure 6 A schematic diagram of the hardware structure of the gateway node provided in an embodiment of this application is shown.

[0110] The gateway node may include a processor 601 and a memory 602 storing computer program instructions.

[0111] Specifically, the processor 601 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0112] Memory 602 may include mass storage for data or instructions. For example, and not limitingly, memory 602 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 602 may include removable or non-removable (or fixed) media. Where appropriate, memory 602 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 602 is non-volatile solid-state memory.

[0113] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to the first aspect of this disclosure.

[0114] The processor 601 implements any of the methods described above in the above embodiments by reading and executing computer program instructions stored in the memory 602.

[0115] In one example, the gateway node may also include a communication interface 603 and a bus 610. For example, Figure 6 As shown, the processor 601, memory 602, and communication interface 603 are connected through bus 610 and complete communication with each other.

[0116] The communication interface 603 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0117] Bus 610 includes hardware, software, or both, that couples components of the method or gateway node described above together. For example, and not as a limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 610 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0118] Additionally, embodiments of this application may provide a vehicle including the gateway node described above.

[0119] Alternatively, embodiments of this application can be implemented using a computer storage medium. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the vehicle control methods described in the above embodiments.

[0120] Alternatively, this application embodiment can provide a computer program product for implementation, wherein when the instructions in the computer program product are executed by the processor of the gateway node, the gateway node implements any of the vehicle control methods in the above embodiments.

[0121] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described as examples. However, the method process of this application is not limited to the specific steps described. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0122] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0123] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0124] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0125] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A vehicle control method, characterized in that, The method, applied to a gateway node of a vehicle, includes: Obtain the first message, which includes the target local network cluster (PNC) identifier; Based on the target PNC identifier and the mask configured for each segment of the vehicle network in the pre-acquired network configuration information, the target network segment is determined. Each network segment is connected to at least one controller, and the mask of the network segment is configured according to the controller currently connected to the network segment. The first message is forwarded to the target network segment, and the first message is used to wake up or put the controller connected to the target network segment into sleep mode.

2. The vehicle control method according to claim 1, characterized in that, Before determining the target network segment based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information, the method further includes: Obtain the current configuration information of each network segment after the vehicle is powered on this time, the current configuration information including the identifier of the controller currently configured in the network segment; For each network segment, reference configuration information for that network segment is obtained. This reference configuration information is the configuration information of the network segment obtained after the vehicle was last powered on. If the current configuration information of the network segment is different from the reference configuration information, the current mask of the network segment is updated.

3. The vehicle control method according to claim 2, characterized in that, Updating the current mask of the network segment includes: Based on the current configuration information of the network segment and the reference configuration information of the network segment, a first controller is determined, wherein the first controller is a controller added or deleted from the network segment; The first mask of the network segment is determined based on the PNC identifier pre-configured for the first controller; The current mask of the network segment is updated using the first mask.

4. The vehicle control method according to claim 3, characterized in that, The step of determining the first mask of the network segment based on the PNC identifier pre-configured for the first controller includes: If the first controller is a newly added controller in the network segment, then the current mask of the network segment is converted into binary to obtain the value corresponding to multiple bits. Each bit corresponds to one of the multiple PNC identifiers. The multiple PNC identifiers include the PNC identifier pre-configured for each controller of the vehicle. Change the value of the bit corresponding to the PNC identifier of the first controller among the values ​​of the plurality of bits to a first preset value to obtain updated values ​​of the plurality of bits; The values ​​corresponding to the updated bits are converted to decimal to obtain the first mask of the network segment.

5. The vehicle control method according to claim 3, characterized in that, The step of determining the first mask of the network segment based on the PNC identifier pre-configured for the first controller includes: If the first controller is the controller that the network segment is deleted from, then the current mask of the network segment is converted into binary to obtain the value corresponding to multiple bits. Each bit corresponds to one of the multiple PNC identifiers. The multiple PNC identifiers include the PNC identifier pre-configured for each controller of the vehicle. The value of the bit corresponding to the PNC identifier of the first controller among the values ​​of the plurality of bits is changed to a second preset value to obtain updated values ​​of the plurality of bits. The values ​​corresponding to the updated bits are converted to decimal to obtain the first mask of the network segment.

6. The vehicle control method according to claim 1, characterized in that, The step of determining the target network segment based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information includes: For each network segment, each byte in the mask of the network segment is converted into binary to obtain the value of multiple bits corresponding to the network segment. Each bit corresponds to one of multiple PNC identifiers, and the multiple PNC identifiers include PNC identifiers pre-configured for each controller of the vehicle. The target network segment is determined based on the target PNC identifier and the values ​​corresponding to multiple bits for each network segment.

7. A vehicle control device, characterized in that, The device includes: The acquisition module is used to acquire a first message, the first message including the target local network cluster (PNC) identifier; The determination module is used to determine the target network segment based on the target PNC identifier and the mask configured for each network segment of the vehicle network in the pre-acquired network configuration information. Each network segment is connected to at least one controller, and the mask of the network segment is configured according to the controller currently connected to the network segment. The transceiver module is used to forward the first message to the target network segment, and the first message is used to wake up or put the controller connected to the target network segment into sleep mode.

8. A gateway node, characterized in that, include: Processor and memory storing computer program instructions; When the processor executes the computer program instructions, it implements the vehicle control method as described in any one of claims 1-6.

9. A vehicle, characterized in that, This includes the gateway node as described in claim 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the vehicle control method as described in any one of claims 1-6.

Images