Vehicle sub-network segment network management method and system based on direct flag bit mapping

Abstract

The invention relates to a vehicle sub-network segment network management method based on direct flag bit mapping, and the method comprises the following steps: responding to a local function demand event, generating a network management message through a corresponding function controller, the data field of the network management message comprising a group of standardized flag bits, the standardized flag bit comprises a basic network segment flag bit used for identifying that a target physical network segment needs to be awakened, a priority flag bit used for representing a function priority, a resource demand flag bit used for quantifying a function resource demand and a collaborative management flag bit used for identifying whether collaborative execution of multiple network segments is needed or not. By defining a four-layer standardized flag bit structure comprising basic network segments, priorities, resource requirements and collaborative management, the hardware cost and upgrading threshold of the system are remarkably reduced, excellent backward compatibility is realized, a complex service-network segment mapping table maintained by the gateway is avoided, and the service performance of the system is improved. And the gateway complexity and the single-point fault risk are fundamentally reduced.

Description

Technical Field

[0001] This invention relates to the field of vehicle electronic and electrical architecture, and specifically to a vehicle segment network management method and system with direct flag bit mapping. Background Technology

[0002] With the continuous improvement of vehicle intelligence and connectivity, the vehicle's electronic and electrical architecture is becoming increasingly complex, with a significant increase in the number of on-board electronic control units (ECUs) and richer functions. To meet complex communication needs and reduce power consumption, modern vehicles typically adopt an architecture that divides controllers of different functional domains into different physical network segments (such as powertrain CAN, body CAN, entertainment CAN, etc.) and introduces network management mechanisms to allow some networks to hibernate during non-working periods to reduce the vehicle's static current.

[0003] Among related technologies, there are two main network management schemes. One is a partial network management mechanism based on the AUTOSAR standard, which achieves precise network segment wake-up control by defining PNC identifiers and setting PNC bitmaps in the data field of network management (NM) messages. The other is a segmented network management scheme based on a central gateway lookup table, where the function controller sends a function request to the gateway, and the gateway determines and wakes up the target network segment by querying a pre-set function-network segment mapping table. However, all of the aforementioned existing technologies have significant drawbacks. The AUTOSAR PN solution relies on dedicated transceiver hardware that supports PNC functionality, leading to increased hardware costs and making it impossible to deploy on a large number of existing traditional ECU platforms, resulting in poor compatibility and complex system configuration. The gateway lookup table solution, on the other hand, deeply couples complex business logic with network management, requiring the gateway to maintain and frequently update a massive mapping table, becoming a bottleneck and single point of failure in system development. Any functional change or addition requires modification of the gateway configuration, resulting in poor system scalability and hindering rapid feature iteration and deployment. Furthermore, with the rapid iteration of intelligent connected functions, traditional architectures struggle to support the flexible and rapid deployment of new features, severely restricting the speed of innovation. Simultaneously, the complex mapping relationships and state machines make network behavior unpredictable, posing potential risks in safety-critical scenarios.

[0004] Therefore, there is an urgent need in this field for a vehicle segment network management solution that can overcome the above-mentioned defects, decouple functions from network management, have high compatibility and scalability, and enable fine-grained power consumption management to solve the above problems. Summary of the Invention

[0005] This application provides a vehicle segment network management method and system with direct flag bit mapping to solve the above-mentioned problems.

[0006] In a first aspect, embodiments of this application provide a vehicle segment network management method based on direct flag bit mapping, comprising the following steps: In response to a local functional requirement event, a network management message is generated through the corresponding functional controller. The data field of the network management message contains a set of standardized flag bits, including a basic network segment flag bit for identifying the target physical network segment to be woken up, a priority flag bit for characterizing the functional priority, a resource requirement flag bit for quantifying the functional resource requirements, and a collaborative management flag bit for identifying whether multi-network segment collaborative execution is required. The generated network management message is broadcast on the physical network segment where the function controller is located. The central gateway receives the network management messages from each function controller and extracts the corresponding standardized flag bits. Based on the standardized flag bits extracted from each target physical network segment, the global network segment requirement status is generated through aggregation processing. The system status parameters of the vehicle at the current moment are obtained. Based on the obtained system status parameters and the generated global network segment demand status, it is determined whether there is a preset risk conflict. Based on the judgment result, the corresponding differentiated arbitration strategy is executed to adjust the wake-up method of the target physical network segment, and the final network segment wake-up message is generated and sent to the target physical network segment to perform the wake-up operation.

[0007] In conjunction with the first aspect, in one implementation, the resource requirement flag includes at least a power consumption level information subfield, a duration requirement information subfield, and a bandwidth requirement subfield.

[0008] In conjunction with the first aspect, in one implementation, the aggregation processing based on the standardized flag bits of each extracted target physical network segment includes: performing a bitwise logical OR operation on all standardized flag bits.

[0009] In conjunction with the first aspect, in one implementation, the system status parameters include: remaining battery power data, ambient temperature data, and gateway processor load data.

[0010] In conjunction with the first aspect, in one implementation, the determination of whether there is a preset risk conflict based on the acquired system state parameters and the generated global network segment demand state specifically includes: Based on the power consumption level information subfield in the resource demand flag and the remaining battery power data, determine whether there is a risk of power consumption conflict. Based on the duration demand information subfield in the resource demand flag and the ambient temperature data, determine whether there is an overheating risk; Based on the gateway processor load data and the bandwidth demand information subfield in the resource demand flag, it is determined whether there is a risk of resource shortage.

[0011] In conjunction with the first aspect, in one implementation method, the execution of the corresponding differentiated arbitration strategy based on the judgment result specifically includes: When a power consumption conflict risk is detected, the central gateway sets a power consumption risk flag in the network segment wake-up message it sends, triggers the high power consumption function controller to perform autonomous power consumption limitation, and sends corresponding information to the user at the same time. When an overheating risk is detected, the central gateway sets an overheating risk flag in the network segment wake-up message it sends, and simultaneously executes an overheating prevention strategy. When a risk of resource shortage is identified, the wake-up sequence of the target physical network segment is adjusted. If none of the above risks are identified, the corresponding target physical network segment will be directly activated based on the global network segment demand status.

[0012] In conjunction with the first aspect, in one implementation, triggering the high-power function controller to perform autonomous power consumption limitation includes: when the function controller detects that the power consumption risk flag is set, if the value of the power consumption level subfield in the resource requirement flag corresponding to its own function is greater than a first preset threshold and the value of the duration requirement subfield is greater than a second preset threshold, then the function controller automatically limits the execution duration of the function based on a preset time.

[0013] In conjunction with the first aspect, in one implementation, the triggering of the high-power function controller to perform autonomous power consumption limitation further includes: after automatically limiting the execution duration of the function, the function controller sends a function limitation notification to the human-machine interaction module through the vehicle network to remind the user that the current function is limited and the reason for it.

[0014] In conjunction with the first aspect, in one implementation, the adjustment of the network segment wake-up timing includes: If the collaborative management flag bit in the network management message received from each functional controller is not set, the network segment wake-up message sending period of the target physical network segment will be extended based on the preset duration. If the collaborative management flag bit in the network management message received from at least one functional controller is set, then the network segment wake-up message transmission period of the target physical network segment is extended based on a preset duration, and each target physical network segment to be woken up is woken up sequentially based on the priority flag bit.

[0015] In conjunction with the first aspect, in one embodiment, the overheat protection strategy includes: If it is determined that there is no risk of power consumption conflict, the preset thermal management related physical network segment is actively woken up and its priority is set to the highest. At the same time, the arbitration results of the resource shortage risk are integrated and the final target physical network segment wake-up operation is executed. If a power consumption conflict risk is detected, the arbitration result of the resource shortage risk is integrated to perform the target physical network segment wake-up operation, and the overheat risk flag is set in the sent network segment wake-up message to trigger the woken-up functional controller to start the preset temperature self-test program.

[0016] In conjunction with the first aspect, in one implementation, the preset temperature self-test program includes: The function controller reads temperature sensor data from its own chip and temperature data from the load components it is responsible for according to a preset cycle. If any temperature data detected exceeds its preset safety threshold, at least one protective action is executed, including reducing output power, entering intermittent operation mode, or suspending function operation, until the temperature data is less than the preset safety threshold.

[0017] Secondly, embodiments of this application provide a vehicle segmentation network management system based on direct flag bit mapping, comprising: Multiple functional controllers are communicatively connected to multiple physical network segments of the vehicle, and each of the functional controllers is configured to perform the steps involved in the vehicle segment network management method of direct flag bit mapping. The central gateway, which is communicatively connected to all the physical network segments, is configured to perform the steps involved in the vehicle segment network management method of direct flag bit mapping.

[0018] Thirdly, embodiments of this application provide a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the vehicle segment network management method with direct flag bit mapping as described above.

[0019] The beneficial effects of the technical solutions provided in this application include: 1. By defining a four-layer standardized flag structure that includes basic network segments, priorities, resource requirements, and collaborative management, a common communication language is established between the functional controller and the central gateway. This design enables the controller to accurately express network requirements in a standardized and data-driven manner, while the gateway only needs to perform efficient aggregation and arbitration based on the flags. This achieves complete decoupling of business functions from underlying network management. This purely software-defined solution can be directly deployed on existing standard AUTOSARECUs without the need for dedicated hardware or hardware modifications. This not only significantly reduces system hardware costs and upgrade barriers, achieving excellent backward compatibility, but also avoids the need for the gateway to maintain a complex service-network segment mapping table, fundamentally reducing gateway complexity and single point of failure risk, and laying a solid foundation for flexible system expansion.

[0020] 2. Based on the standardized flag communication protocol described above, network management logic is separated from the complex service mapping of the gateway. The role of the central gateway is simplified to aggregating flags and arbitrating based on preset rules. There is no need to maintain dynamic service-network segment mapping relationships. Therefore, when functions change or new features are needed, only the flag generation logic within the corresponding controller needs to be adjusted, without modifying the gateway's core configuration and processing flow. This architecture achieves deep decoupling between services and the network, greatly improving the flexibility of system development, the speed of function iteration, and the robustness of the overall architecture.

[0021] 3. By combining resource requirement flags (such as power consumption, duration, and bandwidth) with real-time system status parameters (such as battery level, ambient temperature, and gateway processor load) to determine conflict risks, and executing differentiated arbitration strategies accordingly (such as triggering autonomous time limits when power consumption conflicts occur, and adjusting wake-up timing when resources are scarce), refined intelligent decision-making on network wake-up behavior is achieved. This arbitration mechanism based on state awareness and explicit rules replaces the traditional complex table lookup and state machine, effectively reducing the static current consumption of the entire vehicle and making network behavior more deterministic and predictable, thereby improving the reliability of the system in safety-critical scenarios. Attached Figure Description

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

[0023] Figure 1 This is a schematic diagram illustrating the main steps of the present invention; Figure 2 This is an example diagram illustrating the priority flag bit encoding definition in Embodiment 1 of the present invention; Figure 3 This is an example diagram illustrating the encoding definition of the resource requirement flag bit in Embodiment 1 of the present invention; Figure 4 This is an example diagram showing the initial values ​​of the flag bits of each functional controller in Embodiment 1 of the present invention; Figure 5 This is an example diagram showing the aggregation result of the flag bits of each functional controller in Embodiment 1 of the present invention. Detailed Implementation

[0024] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0025] Example 1: This application provides a vehicle segment network management method based on direct flag bit mapping, including the following steps: S1. In response to a local functional requirement event, a network management message is generated through the corresponding functional controller. The data field of the network management message contains a set of standardized flag bits. The standardized flag bits include a basic network segment flag bit for identifying the target physical network segment to be woken up, a priority flag bit for characterizing the functional priority, a resource requirement flag bit for quantifying the functional resource requirements, and a collaborative management flag bit for identifying whether multi-network segment collaborative execution is required. This step is initiated when a function controller in the vehicle (such as the air conditioning controller, battery management controller, in-vehicle infotainment controller, etc.) detects that a local function requirement event has been triggered. Local functional requirement events include, but are not limited to: remote control commands initiated by the user through the remote key or mobile terminal APP (such as remotely starting the air conditioner), functions automatically triggered by the vehicle system according to preset conditions (such as battery preheating timed start in low temperature environment), or abnormal states detected by sensors (such as airbag collision signals). S101: Logic for generating normalized flags ① Each function controller has a pre-configured function requirement-flag mapping rule base. This rule base defines the mapping relationship between all function requirement events that the function controller can process and their corresponding standardized flag values. When generating a network management message, the function controller executes the following sub-steps: The function controller determines one or more target physical network segments that need to be woken up based on the data interaction objects involved in the current functional requirements; Physical network segments include, but are not limited to: The Power CAN segment (PCAN) is used for the control of motors, batteries, gearboxes, etc. The infotainment CAN network segment (ICAN) is used for the central control screen, audio system, navigation, etc. The vehicle body CAN bus (BCAN) is used for controlling doors, windows, air conditioning, lights, etc. The chassis CAN network segment (CCAN) is used for braking, steering, suspension, etc. Reserved extended network segment (ECAN).

[0026] In the basic network segment flag, the function controller sets the bit corresponding to the target physical network segment to "1" and the remaining bits to "0", as shown in the table below:

[0027] ② The controller queries the mapping rule base based on the urgency and importance of the functional requirement event, and assigns a priority value to this requirement. The priority level can be predefined. The example provided in this embodiment is as follows: Figure 2 As shown, that is: Emergency Priority (6~7): Used for handling safety-critical or system failures (such as brake failure alarm, battery thermal runaway), requiring immediate response; High priority (4~5): Used for functions with high time sensitivity (such as vehicle anti-theft alarm, remote vehicle positioning); Medium priority (2~3): Used for routine comfort functions (such as remote air conditioning start, seat heating); Low priority (0~1): Used for background tasks that can be delayed (such as software OTA upgrades, log uploads); The function controller then encodes the corresponding priority value and fills it into the priority flag field.

[0028] ③ The function controller performs a quantitative analysis of the resources required to execute this function requirement and fills in the corresponding subfields of the resource requirement flag: Power consumption level information subfield: Select one of the preset levels (preferably low, medium, high, and very high) based on the peak power consumption range during function operation; Duration Requirement Information Subfield: Select one of the preset levels (preferably short, medium, long, and very long) based on the expected execution time of the function; Bandwidth Requirement Information Subfield: Select one of the preset levels (preferably low, medium, high, and extremely high) based on the amount of network communication bandwidth required during function execution; The examples provided in this embodiment are as follows: Figure 3 As shown.

[0029] ④ The function controller determines whether the current function requirement requires the collaborative work of different ECUs on multiple physical network segments to complete. If so, it sets the collaborative management flag to "1" (indicating collaborative function); otherwise, it sets it to "0" (indicating independent function).

[0030] S102: Encapsulation of network management messages The function controller encapsulates the four standardized flag bits generated above into the user data field of a network management message (NM PDU) conforming to the AUTOSAR NM protocol, according to a predefined format and order. After generating a complete NM message, the function controller prepares to broadcast it on the physical network segment it is connected to, thereby sending standardized information containing precise network requirements to the central gateway.

[0031] When a vehicle needs to add new functions or adjust existing functional requirements, it is only necessary to update its functional requirement-flag mapping rule base in the corresponding functional controller to define the mapping relationship between the new or adjusted functions and the four-layer standardized flags (basic network segment, priority, resource requirements, and collaborative management), without modifying the processing logic of the central gateway or the network topology. This greatly reduces the complexity of system upgrades and development and maintenance costs.

[0032] S2. Broadcast the generated network management message in the physical network segment where the function controller is located, and receive the network management message from each function controller through the central gateway and extract the corresponding standardized flag bits. Specifically, after the function controller broadcasts NM messages on the physical network segments it is connected to, the central gateway listens to each physical network segment. When it captures a message that matches the NM message identifier, it parses it and extracts the basic network segment flag, priority flag, resource requirement flag, and collaborative management flag from the fields of the NM message.

[0033] S3. Aggregate the extracted standardized flag bits of each target physical network segment to generate the global network segment requirement status; Specifically, the central gateway performs aggregation calculations on the standardized flag bits extracted from each NM message. Specifically, it performs a bitwise logical OR operation on the basic network segment flag bits. This operation ensures that for each physical network segment, as long as any functional controller's demand flag bit indicates that the network segment needs to be woken up, the network segment is marked as needing to be woken up in the aggregation result. The operation generates a global physical network segment demand bitmap, which constitutes the core part of the global network segment demand status. At the same time, the gateway records the highest request priority corresponding to each target physical network segment marked as needing to be woken up, and classifies and statistically analyzes the resource requirements of all requests (such as power consumption level information, duration requirement information, and bandwidth requirement information), as well as identifies whether there are collaborative management requirements. This information together constitutes a complete global network segment requirement status for subsequent risk assessment and decision-making.

[0034] In a specific example of this embodiment, the normalized flag bits extracted from each NM message are as follows: Figure 4 As shown, the polymerization process is as follows Figure 5 As shown.

[0035] S4. Obtain the system status parameters of the vehicle at the current moment. Based on the obtained system status parameters and the generated global network segment demand status, determine whether there is a preset risk conflict. Based on the judgment result, execute the corresponding differentiated arbitration strategy to adjust the wake-up method of the target physical network segment, generate the final network segment wake-up message, and send the network segment wake-up message to the target physical network segment to perform the wake-up operation.

[0036] S401: System Status Parameter Acquisition The central gateway acquires system status parameters reflecting the vehicle's current operating environment in real time via the vehicle bus or dedicated sensor interfaces, mainly including: Remaining battery charge (SOC): Obtained through the battery management system (BMS); Ambient temperature: obtained via the vehicle domain controller or an independent temperature sensing module; Gateway's own resource status: Real-time load rate of the gateway processor (CPU).

[0037] S402: Risk Conflict Assessment The central gateway compares and analyzes the real-time system status parameters it acquires with the global network segment requirement status generated in step S3, and determines whether the following preset risks exist: ① Power consumption conflict risk assessment: The central gateway performs the following steps: Based on the currently acquired remaining battery power data, query the preset power-budget point mapping table to determine the total available power budget points for the current system; This example demonstrates the mapping: SOC 80% → 80 points; SO50%C → 50 points; Based on the power consumption level information subfields corresponding to each function in the global network segment demand status, the preset power consumption level-demand point mapping table is queried, the power consumption level of each function is converted into demand points, and then summed to obtain the estimated total power consumption demand points.

[0038] Example mapping in this embodiment: Extremely high power consumption → 8 points, high power consumption → 5 points, medium power consumption → 3 points, low power consumption → 1 point; By comparing the total power consumption demand points with the available power consumption budget points, if the total power consumption demand points are greater than the available power consumption budget points, it is determined that there is a risk of power consumption conflict.

[0039] ② Overheating risk assessment: The central gateway performs the following steps: Based on the currently acquired ambient temperature data, if the ambient temperature data is greater than the preset ambient temperature threshold (preferably set to 55°C in this embodiment), then based on the global network segment demand status, long-term high-power function requests are identified. For each such request, according to its power consumption level information subfield and duration demand information subfield, the preset power consumption level-demand point mapping table and duration demand-demand point mapping table are queried to calculate its heat generation risk points and sum them up to obtain the total number of function heat generation risk points. If the total number of overheating risk points exceeds the preset overheating risk point threshold, then an overheating risk is identified.

[0040] ③ Assessment of resource scarcity risk: The central gateway performs the following steps: Based on the monitored current load rate of the gateway processor (CPU), query the preset load rate-load point mapping table to determine the current system load points; Based on the global network segment demand status, identify all pending requests, and according to their bandwidth demand information subfield, query the preset bandwidth demand-load point mapping table to calculate the total load points of pending tasks. If the total number of pending tasks exceeds the current system load, then there is a risk of resource shortage.

[0041] It should be noted that the purpose of setting up the above-mentioned power consumption-budget point mapping table, power consumption level-demand point mapping table, duration demand-demand point mapping table, load rate-load point mapping table, and bandwidth demand-load point mapping table is to uniformly quantify system state parameters and functional requirement parameters with different physical meanings and dimensions into unitless, comparable points. This allows the central gateway to perform standardized processing and fusion analysis of multi-dimensional and heterogeneous input information through simple mathematical operations, thereby efficiently and consistently executing complex risk judgment and arbitration logic. This avoids writing a large number of independent and complex condition judgment rules for each risk combination. The mapping relationship can be predefined and adjusted according to the specific vehicle configuration, hardware performance, and design goals.

[0042] Furthermore, the risk assessment logic of this application is not limited to the above-mentioned implementation method based on point mapping and comparison. Those skilled in the art will understand that the core of risk assessment lies in comparing and associating system state parameters with functional requirement characteristics, and making a judgment on whether there is a risk of conflict based on preset rules. The above-mentioned method of converting mapping tables into points for quantitative comparison is only a preferred embodiment for implementing this core logic. Its advantages are clear logic, high computational efficiency and easy configuration. Without departing from the core concept of this application, those skilled in the art can also adopt other equivalent or modified implementation methods.

[0043] S403: Implementation of Differentiated Arbitration Strategies Based on the risk assessment results of step S402, the central gateway executes the corresponding differentiated arbitration strategy and generates the final network segment wake-up message.

[0044] ① Arbitration strategy to address power consumption conflict risks: If a power consumption conflict risk is identified, the central gateway will perform the following arbitration: Set the risk flag: In the upcoming network segment wake-up message, set the power consumption risk flag; ② Arbitration strategies for addressing resource scarcity risks: If a risk of resource shortage is identified, the central gateway will perform the following arbitration to alleviate its processing load and network congestion: Extend the wake-up period: Extend the sending period of the network segment wake-up message from the standard period (e.g., 50ms) to a longer preset period (preferably 100ms in this embodiment). Simultaneously, a judgment is made based on the collaborative management flag bit in each NM message: If the coordination management flag bit in the NM message received from each functional controller is not set, it is determined that there is no coordination requirement at present, and only the wake-up period is extended. If the coordination management flag bit in the NM message received from at least one functional controller is set, it is determined that there is a coordination requirement. While extending the wake-up period, the target physical network segments to be woken up are woken up sequentially based on the priority flag bit in the NM message. That is, a network segment wake-up message is first sent to the target physical network segments with urgent priority. After confirming that their network activity is stable, a network segment wake-up message is then sent to the target physical network segments with higher priority, and so on.

[0045] ③ Arbitration strategy for overheating risk: If an overheating risk is identified, the central gateway will perform the following arbitration: Set the risk flag: In the upcoming network segment wake-up message, set the overheat risk flag; Simultaneously, a further decision is made based on whether the power consumption risk flag is set in the network segment wake-up message: If the power consumption risk flag is not set: the central gateway will proactively add the preset thermal management-related physical network segments to the highest priority wake-up list to ensure that the heat dissipation system starts up synchronously; at the same time, it will integrate the arbitration strategy for resource shortage risk and execute the final target physical network segment wake-up operation; In this embodiment, the preset thermal management-related physical network segment includes the cooling fan control network segment, which can also be adjusted according to actual needs; If the power consumption risk flag is set: For energy saving reasons, the central gateway will not actively wake up the high-power heat dissipation system network segment, but will only set the overheating risk flag.

[0046] ④ Default strategy in risk-free situations: If none of the above risks are identified, the central gateway will directly determine the list of target physical network segments to be woken up based on the global network segment demand status generated by S3, and wake up simultaneously at a standard cycle.

[0047] S404: Wake-up message sending and execution The central gateway encapsulates the execution result of the S403 arbitration policy into a final network segment wake-up message. The core content of this message includes: Target network segment list: includes one or more target physical network segments that need to be woken up; Risk flags: including power consumption risk flag and / or overheat risk flag; Subsequently, the central gateway sends corresponding network segment wake-up messages to each target physical network segment according to the timing determined by arbitration. According to the AUTOSAR network management protocol, when a node (ECU) on the target network segment hears the message, it will exit the hibernation mode and enter the network activity state, thereby completing the wake-up operation of the target physical network segment. At the same time, the function controller on the target physical network segment can trigger corresponding autonomous management behaviors by parsing the risk flag bits in the message, thus forming a complete risk control closed loop. When the function controller detects a power consumption risk flag and / or an overheat risk flag: ① When the function controller detects that the power consumption risk flag is set, if the value of the power consumption level subfield in the resource requirement flag corresponding to its own function is greater than the first preset threshold and the value of the duration requirement subfield is greater than the second preset threshold, then it will perform autonomous power consumption limitation: automatically limit the execution duration of the function based on the preset time. Specifically: When the function controller detects that the power consumption risk flag in the network segment wake-up message is set (=1), it will check the resource requirement flag corresponding to the local function requirement it serves. If the power consumption level information subfield value corresponding to the function is greater than the first preset threshold (in this embodiment, it is preset to represent a high power consumption function), and its duration requirement information subfield value is greater than the second preset threshold (in this embodiment, it is preset to represent a long-time task), then the function controller will automatically start an execution timer for the function based on the preset safe execution duration (preferably 10 minutes in this embodiment). When the timer expires, the controller automatically pauses or terminates the execution of the high-power, long-duration function and sends a function limitation notification to the human-machine interface module via the vehicle network to remind the user, such as: the air conditioning has been paused to save power.

[0048] ② When the function controller detects that the overheat risk flag is set, it will execute the overheat protection strategy: trigger the awakened function controller to start the preset temperature self-test program; Specifically: when the function controller detects that the overheat risk flag in the network segment wake-up message is set (=1), it immediately starts the preset temperature self-test program; The control function controller reads the temperature sensor data of its own chip according to a preset cycle, and reads the temperature data of the load components it is responsible for through a dedicated interface (for example, the motor controller reads the motor winding temperature, and the battery manager reads the cell temperature). If any temperature data detected exceeds its preset safety threshold, the function controller will immediately and autonomously execute protection actions, such as: reducing output power (frequency reduction), entering intermittent operation mode, or suspending function operation in extreme cases until the temperature data falls back to the safe range. The specific temperature self-test procedure provided in this embodiment is as follows: Taking the motor controller as an example, the functional controller reads its own chip temperature through the internal temperature sensor according to a preset cycle (preferably 100ms in this embodiment), and at the same time reads the motor winding temperature through a dedicated temperature acquisition interface; if the chip temperature exceeds the preset first threshold (preferably 105°C in this embodiment) or the motor winding temperature exceeds the preset second threshold (preferably 150°C in this embodiment), it is determined that there is an overheating risk, and the frequency reduction protection action is immediately executed to reduce the motor output power to 70% of the rated power; if the temperature data continues to rise and exceeds the preset third threshold (preferably 115°C for the chip or 170°C for the winding in this embodiment), it enters the intermittent operation mode (run for 2 seconds / pause for 3 seconds); in extreme cases, if the temperature exceeds the preset fourth threshold (preferably 125°C for the chip or 180°C for the winding in this embodiment), the function operation is immediately suspended until the temperature data is less than the preset first threshold; It is understood that the above-mentioned preset temperature threshold, frequency reduction ratio, intermittent operation mode parameters, and protection action triggering conditions and specific types are merely illustrative examples. Those skilled in the art can make corresponding configurations and adjustments based on the functional characteristics, hardware tolerance, and system safety objectives of different functional controllers. For example, the battery manager can be set with different temperature thresholds and protection strategies, and the protection scope of this application is not limited to the above-mentioned specific values ​​and examples.

[0049] Compared to the centralized thermal management strategy where the central gateway actively wakes up the preset thermal management-related physical network segments when there is no risk of power consumption conflict, the above-mentioned distributed protection mechanism based on functional controller self-testing is a degradation safety strategy under resource-constrained conditions. When the system faces both overheating and power consumption conflict risks at the same time, each functional node can autonomously implement rapid and accurate local temperature monitoring and protection without increasing the system's additional power consumption. Thus, while ensuring that critical hardware is not damaged by overheating, limited electrical energy resources are prioritized for maintaining the vehicle's core functions and basic safety, achieving an optimal balance between safety and energy efficiency under multiple resource constraints.

[0050] Example 2: This second embodiment provides a system corresponding to the method in the first embodiment. The system includes: multiple function controllers and a central gateway.

[0051] Function controllers: Function controllers are the various electronic control units (ECUs) in the vehicle, such as the air conditioning controller, battery management controller (BMS), in-vehicle infotainment controller (IVI), body control module (BCM), etc. Each function controller is communicatively connected to one or more physical network segments (such as the power CAN network segment PCAN, body CAN network segment BCAN, infotainment CAN network segment ICAN, etc.).

[0052] Each function controller is configured as follows: Demand Awareness and Flag Generation Module: Used to respond to local functional demand events (such as receiving user instructions, timed triggers, sensor alarms, etc.) and generate network management messages containing a set of standardized flags based on the internally preset functional demand-flag mapping rule library; the standardized flags include: basic network segment flag, priority flag, resource demand flag, and collaborative management flag.

[0053] Message broadcast module: Used to broadcast generated network management messages on the physical network segment to which it is connected; Risk Response Module: After wake-up, it parses the network segment wake-up message sent by the central gateway; if the power consumption risk flag in the message is set and its own function meets the characteristics of high power consumption and long time, it automatically limits the execution time of the function; if the overheat risk flag is set, it starts the temperature self-test program and executes autonomous thermal protection.

[0054] Central Gateway: As the communication hub and intelligent decision-making center of the vehicle network, the central gateway's hardware includes multiple independent network interfaces, which communicate with all the physical network segments that need to be managed (such as PCAN, ICAN, BCAN, CCAN, ECAN). The central gateway is configured as follows: Message receiving and parsing module: used to simultaneously monitor all physical network segments, receive network management messages broadcast by various functional controllers, and extract standardized flag bits from their data fields; Flag aggregation module: used to perform bitwise logical OR operation on the extracted flag bits of each basic network segment to generate global network segment demand status (including global wake-up bitmap, highest priority of each network segment, resource demand statistics and collaborative demand identification). System status monitoring module: used to acquire vehicle system status parameters in real time, including remaining battery charge (SOC), ambient temperature, and the load rate of the gateway's own processor (CPU).

[0055] Risk assessment and arbitration decision-making module (intelligent core): This is the core module of the system, used for: Risk assessment: Based on the global network segment demand status and real-time system status parameters, and through preset mapping rules and comparison logic, determine whether there are risks of power consumption conflict, overheating, and resource shortage.

[0056] Arbitration decision: Based on the risk assessment results, a differentiated arbitration strategy is implemented to generate the final network segment wake-up message, which includes: a list of target physical network segments and risk flags that need to be set.

[0057] Wake-up message generation and sending module: It is used to encapsulate the arbitration decision result into a network segment wake-up message conforming to the AUTOSAR NM protocol, and send the message to each target physical network segment according to the timing of the decision to perform a precise network segment wake-up operation.

[0058] When the vehicle is in sleep mode, a local demand event of any functional controller will trigger the above system workflow. The functional controller expresses the demand through standardized flag bits, and the central gateway understands and coordinates the global demand through aggregation, judgment and arbitration, and finally executes the decision through network segment wake-up message. This process achieves complete decoupling of business functions and network management: function changes only require adjusting the local mapping rule base of the corresponding functional controller, without changing the complex logic of the central gateway. At the same time, the system can intelligently resolve resource conflicts based on real-time power, temperature, load and other statuses, and achieve fine-grained management of vehicle network power consumption and deterministic control of wake-up behavior while ensuring safety and critical functions.

[0059] This system embodiment achieves all the beneficial effects of the method in Embodiment 1 through software and hardware collaboration, providing a highly compatible, scalable, and intelligent segmented network management solution for intelligent connected vehicles.

[0060] Example 3: Computer-readable storage medium This third embodiment provides a computer-readable storage medium on which a computer program is stored, which, when executed by a processor, implements the steps of the method as described in the first embodiment. Specifically, a computer-readable storage medium can be any tangible medium that contains or stores program code, including but not limited to: read-only memory (ROM), random access memory (RAM), flash memory, hard disk, optical disc (CD-ROM, DVD), Blu-ray disc, USB storage device, server storage space, etc. When the processor in the vehicle (such as the processor of the function controller or the processor of the central gateway) executes the computer program stored on the storage medium, it can implement the various method steps in the aforementioned embodiment one, thereby completing functions such as generating and parsing standardized flag bits, aggregating global network segment demand states, judging risk conflicts, executing differentiated arbitration strategies, and generating and sending wake-up messages.

[0061] By storing the technical solution of this application in the form of a computer program on a readable storage medium, it is convenient to upgrade the software and expand the functions on the existing vehicle electronic and electrical architecture. The network management method of this application can be implemented without modifying the hardware, which further reduces the system upgrade cost and deployment difficulty.

[0062] In the description of this application, it should be noted that the terms "upper," "lower," etc., indicating the orientation or positional relationship are based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this application. Unless otherwise expressly specified and limited, the terms "installed," "connected," and "linked" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication between two elements. For those skilled in the art, the specific meaning of the above terms in this application can be understood according to the specific circumstances.

[0063] It should be noted that in this application, 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 one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0064] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for vehicle segment network management using direct flag bit mapping, characterized in that, Includes the following steps: In response to a local functional requirement event, a network management message is generated through the corresponding functional controller. The data field of the network management message contains a set of standardized flag bits, including a basic network segment flag bit for identifying the target physical network segment to be woken up, a priority flag bit for characterizing the functional priority, a resource requirement flag bit for quantifying the functional resource requirements, and a collaborative management flag bit for identifying whether multi-network segment collaborative execution is required. The generated network management message is broadcast on the physical network segment where the function controller is located. The central gateway receives the network management messages from each function controller and extracts the corresponding standardized flag bits. Based on the standardized flag bits extracted from each target physical network segment, the global network segment requirement status is generated through aggregation processing. The system status parameters of the vehicle at the current moment are obtained. Based on the obtained system status parameters and the generated global network segment demand status, it is determined whether there is a preset risk conflict. Based on the judgment result, the corresponding differentiated arbitration strategy is executed to adjust the wake-up method of the target physical network segment, and the final network segment wake-up message is generated and sent to the target physical network segment to perform the wake-up operation.

2. The vehicle segment network management method based on direct flag bit mapping according to claim 1, characterized in that, The resource requirement flag includes at least a power consumption level information subfield, a duration requirement information subfield, and a bandwidth requirement subfield.

3. The vehicle segment network management method based on direct flag bit mapping according to claim 1, characterized in that, The aggregation process based on the standardized flag bits of each extracted target physical network segment includes: performing a bitwise logical OR operation on all standardized flag bits.

4. The vehicle segment network management method based on direct flag bit mapping according to claim 2, characterized in that, The system status parameters include: remaining battery power data, ambient temperature data, and gateway processor load data.

5. The vehicle segment network management method based on direct flag bit mapping according to claim 4, characterized in that, The determination of whether there is a preset risk conflict based on the acquired system status parameters and the generated global network segment demand status specifically includes: Based on the power consumption level information subfield in the resource demand flag and the remaining battery power data, determine whether there is a risk of power consumption conflict. Based on the duration demand information subfield in the resource demand flag and the ambient temperature data, determine whether there is an overheating risk; Based on the gateway processor load data and the bandwidth demand information subfield in the resource demand flag, it is determined whether there is a risk of resource shortage.

6. The vehicle segment network management method based on direct flag bit mapping according to claim 1, characterized in that, The execution of the corresponding differentiated arbitration strategy based on the judgment result specifically includes: When a power consumption conflict risk is detected, the central gateway sets a power consumption risk flag in the network segment wake-up message it sends, triggers the high power consumption function controller to perform autonomous power consumption limitation, and sends corresponding information to the user at the same time. When an overheating risk is detected, the central gateway sets an overheating risk flag in the network segment wake-up message it sends, and simultaneously executes an overheating prevention strategy. When a risk of resource shortage is identified, the wake-up sequence of the target physical network segment is adjusted. If none of the above risks are identified, the corresponding target physical network segment will be directly activated based on the global network segment demand status.

7. The vehicle segment network management method based on direct flag bit mapping according to claim 6, characterized in that, The triggering of the high-power function controller to perform autonomous power consumption limitation includes: when the function controller detects that the power risk flag is set, if the value of the power level subfield in the resource requirement flag corresponding to its own function is greater than the first preset threshold and the value of the duration requirement subfield is greater than the second preset threshold, then the function controller automatically limits the execution duration of the function based on a preset time.

8. The vehicle segment network management method based on direct flag bit mapping according to claim 7, characterized in that, The triggering of the high-power function controller to perform autonomous power consumption limitation also includes: after automatically limiting the execution duration of the function, the function controller sends a function limitation notification to the human-machine interaction module through the vehicle network to remind the user that the current function is limited and the reason for it.

9. The vehicle segment network management method based on direct flag bit mapping according to claim 6, characterized in that, The adjustment of the network segment wake-up timing includes: If the collaborative management flag bit in the network management message received from each functional controller is not set, the network segment wake-up message sending period of the target physical network segment will be extended based on the preset duration. If the collaborative management flag bit in the network management message received from at least one functional controller is set, then the network segment wake-up message transmission period of the target physical network segment is extended based on a preset duration, and each target physical network segment to be woken up is woken up sequentially based on the priority flag bit.

10. The vehicle segment network management method based on direct flag bit mapping according to claim 6, characterized in that, The overheat prevention strategy includes: If it is determined that there is no risk of power consumption conflict, the preset thermal management related physical network segment is actively woken up and its priority is set to the highest. At the same time, the arbitration results of the resource shortage risk are integrated and the final target physical network segment wake-up operation is executed. If a power consumption conflict risk is detected, the arbitration result of the resource shortage risk is integrated to perform the target physical network segment wake-up operation, and the overheat risk flag is set in the sent network segment wake-up message to trigger the woken-up functional controller to start the preset temperature self-test program.

11. The vehicle segment network management method based on direct flag bit mapping according to claim 10, characterized in that, The preset temperature self-test program includes: The function controller reads temperature sensor data from its own chip and temperature data from the load components it is responsible for according to a preset cycle. If any temperature data detected exceeds its preset safety threshold, at least one protective action is executed, including reducing output power, entering intermittent operation mode, or suspending function operation, until the temperature data is less than the preset safety threshold.

12. A vehicle segment network management system based on direct flag bit mapping, characterized in that, include: Multiple function controllers are communicatively connected to multiple physical network segments of the vehicle, and each of the function controllers is configured to perform the steps involving the function controller in the method of claim 1; A central gateway, communicatively connected to all said physical network segments, is configured to perform the steps involving the central gateway in the method of claim 1.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the vehicle segment network management method with direct flag bit mapping as described in claim 1.

Images