Vehicle network wire harness configuration method and device, vehicle and storage medium

Abstract

The invention discloses a vehicle network wire harness configuration method and device, a vehicle and a storage medium, and the method comprises the steps: obtaining a network topology demand and a network configuration demand of the vehicle; configuring an initial network wire harness of the vehicle based on the network topology requirement; in response to the network configuration demand being a first configuration demand, configuring a target network harness of the vehicle based on the initial network harness and the short-circuit loop; in response to the network configuration demand being a second configuration demand, configuring a target network harness of the vehicle based on the initial network harness; wherein the number of configuration services supported by the second configuration demand is higher than the number of configuration services supported by the first configuration demand. According to the invention, the technical problem of high complexity in the wire harness design process due to the fact that a vehicle needs to design various network wire harnesses to meet different network configuration requirements in the prior art is solved.

Description

Technical Field

[0001] This invention relates to the field of automation control technology, and more specifically, to a method, apparatus, vehicle, and storage medium for configuring vehicle network harnesses. Background Technology

[0002] In the field of vehicle network communication technology, wiring harnesses, as the physical carrier connecting various electronic control units and sensors, undertake the critical functions of data transmission and power distribution. With the continuous improvement of automotive electronics and intelligence, the in-vehicle network architecture is becoming increasingly complex, placing higher demands on the configuration flexibility, reliability, and maintainability of wiring harness systems. In modern vehicle manufacturing and modification scenarios, it is often necessary to quickly adjust the connection methods and node distribution of wiring harnesses according to different vehicle configurations, optional functional packages, or specific network topologies to adapt to diverse production needs.

[0003] However, existing vehicle network wiring harness technology primarily relies on customized designs and fixed connection solutions. To meet diverse network configuration requirements, it is often necessary to redesign and manufacture multiple specifications and models of wiring harness products. This traditional approach results in a cumbersome wiring harness design process, involving extensive drawing, mold development, and sample verification, significantly increasing the R&D cycle and design complexity. Furthermore, fixed wiring harnesses lack versatility and reconfigurability; once the vehicle network configuration changes, the original wiring harnesses often cannot be reused, leading to resource waste and difficulty in adapting to the trend of small-batch, multi-variety flexible production.

[0004] Therefore, there is a lack of a universal solution in the existing technology that can flexibly adapt to various network topologies and meet the differentiated configuration requirements without repeated design. Summary of the Invention

[0005] This invention provides a method, apparatus, vehicle, and storage medium for configuring vehicle network harnesses, thereby at least solving the technical problem in the prior art where the design of harnesses is highly complex due to the need to design multiple network harnesses to meet different network configuration requirements.

[0006] According to one embodiment of the present invention, a method for configuring a vehicle network harness is provided, comprising: obtaining network topology requirements and network configuration requirements of the vehicle; configuring an initial network harness of the vehicle based on the network topology requirements; configuring a target network harness of the vehicle based on the initial network harness and a short-circuit loop in response to a first configuration requirement of the network configuration requirement; and configuring the target network harness of the vehicle based on the initial network harness in response to a second configuration requirement of the network configuration requirement; wherein the number of configuration services supported by the second configuration requirement is higher than the number of configuration services supported by the first configuration requirement.

[0007] Optionally, the method for configuring the vehicle network harness further includes: determining the number of controllers of the target controller based on network configuration requirements, wherein the target controller is connected to the vehicle; comparing the number of controllers with a preset value to obtain a comparison result; in response to the comparison result indicating that the number of controllers is greater than the preset value, determining the network configuration requirement as a second configuration requirement; and in response to the comparison result indicating that the number of controllers is less than or equal to the preset value, determining the network configuration requirement as a first configuration requirement.

[0008] Optionally, the method for configuring the vehicle network harness further includes: establishing a first electrical connection relationship between a first short-circuit loop and an initial network harness, and establishing a second electrical connection relationship between a second short-circuit loop and the initial network harness; configuring the target network harness based on the first electrical connection relationship and the second electrical connection relationship.

[0009] Optionally, the configuration method for the vehicle network harness further includes: acquiring multiple transmission buses of the initial network harness, wherein the multiple transmission buses include a power transmission bus, a chassis transmission bus, and a display transmission bus; determining multiple high-level signal pins of the multiple transmission buses, wherein each transmission bus corresponds to one high-level signal pin; and establishing a path between the multiple high-level signal pins and a common high-level node based on a first short-circuit loop.

[0010] Optionally, the configuration method for the vehicle network harness further includes: identifying multiple low-level signal pins for multiple transmission buses, wherein each transmission bus corresponds to one low-level signal pin; and establishing a path between the multiple low-level signal pins and a common low-level node based on a second short-circuit loop.

[0011] According to one embodiment of the present invention, a configuration system for a vehicle network harness is also provided, comprising: a gateway connector having an initial network harness configured therein, wherein the initial network harness is configured based on network topology requirements; a short circuit breaker having a short-circuit loop configured therein; a processor configured to configure a target network harness of the vehicle based on the initial network harness and the short-circuit loop in response to a first configuration requirement of a network configuration requirement; and configured the target network harness of the vehicle based on the initial network harness in response to a second configuration requirement of a network configuration requirement; wherein the number of configuration services supported by the second configuration requirement is higher than the number of configuration services supported by the first configuration requirement.

[0012] According to one embodiment of the present invention, a vehicle network harness configuration apparatus is also provided, comprising: an acquisition module for acquiring network topology requirements and network configuration requirements of a vehicle; a first configuration module for configuring an initial network harness of the vehicle based on the network topology requirements; a second configuration module for configuring a target network harness of the vehicle based on the initial network harness and a short-circuit loop in response to the network configuration requirements for the first configuration requirements; and a third configuration module for configuring the target network harness of the vehicle based on the initial network harness in response to the network configuration requirements for the second configuration requirements; wherein the number of configuration services supported by the second configuration requirements is higher than the number of configuration services supported by the first configuration requirements.

[0013] Optionally, the vehicle network harness configuration device further includes: a first determining module, configured to determine the number of controllers of the target controller based on network configuration requirements, wherein the target controller is connected to the vehicle; a comparison module, configured to compare the number of controllers with a preset value to obtain a comparison result; a second determining module, configured to determine the network configuration requirement as a second configuration requirement in response to the comparison result indicating that the number of controllers is greater than the preset value; and a third determining module, configured to determine the network configuration requirement as a first configuration requirement in response to the comparison result indicating that the number of controllers is less than or equal to the preset value.

[0014] Optionally, the second configuration module includes: an establishment unit, configured to establish a first electrical connection relationship between the first short-circuit loop and the initial network harness, and to establish a second electrical connection relationship between the second short-circuit loop and the initial network harness; and a first configuration unit, configured to configure the target network harness based on the first electrical connection relationship and the second electrical connection relationship.

[0015] Optionally, the establishment unit includes: an acquisition subunit for acquiring multiple transmission buses of the initial network harness, wherein the multiple transmission buses include a power transmission bus, a chassis transmission bus, and a display transmission bus; a first determination subunit for determining multiple high-level signal pins of the multiple transmission buses, wherein each transmission bus corresponds to one high-level signal pin; and a first establishment subunit for establishing a path between the multiple high-level signal pins and a common high-level node based on a first short-circuit loop.

[0016] Optionally, the establishment unit further includes: a second determining subunit, used to determine multiple low-level signal pins of multiple transmission buses, wherein each transmission bus corresponds to one low-level signal pin; and a second establishing subunit, used to establish a path between the multiple low-level signal pins and a common low-level node based on a second short-circuit loop.

[0017] According to one embodiment of the present invention, a vehicle is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the vehicle network harness configuration method of any of the above claims.

[0018] According to one embodiment of the present invention, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the vehicle network harness configuration method of any of the above claims.

[0019] According to one embodiment of the present invention, a non-volatile storage medium is also provided, wherein a computer program is stored in the non-volatile storage medium, wherein the computer program is configured to execute the vehicle network harness configuration method of any of the above claims when running.

[0020] According to one embodiment of the present invention, a computer program product is also provided, which stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the vehicle network harness configuration method described in any of the above claims.

[0021] In this embodiment of the invention, by obtaining the network topology requirements and network configuration requirements of the vehicle, the technical objective of configuring the initial network harness of the vehicle based on the network topology requirements is achieved. This achieves the technical effect of configuring the target network harness of the vehicle based on the initial network harness and short-circuit loop in response to the network configuration requirements as the first configuration requirement, and configuring the target network harness of the vehicle based on the initial network harness in response to the network configuration requirements as the second configuration requirement. This can solve the technical problem in the prior art where the design of the harness is highly complex because the vehicle needs to design multiple network harnesses to meet different network configuration requirements. Attached Figure Description

[0022] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0023] Figure 1 This is a flowchart of a method for configuring a vehicle network harness according to one embodiment of the present invention;

[0024] Figure 2 This is a flowchart of a method for determining vehicle network configuration requirements according to one embodiment of the present invention;

[0025] Figure 3 This is a structural block diagram of a vehicle network harness configuration system according to one embodiment of the present invention;

[0026] Figure 4 This is a structural block diagram of a vehicle network harness configuration device according to one embodiment of the present invention;

[0027] Figure 5This is a structural block diagram of an electronic device according to one embodiment of the present invention. Detailed Implementation

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

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

[0030] According to an embodiment of the present invention, an embodiment of a method for configuring a vehicle network harness is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system containing at least a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0031] This method embodiment can also be executed in an electronic device, similar control device, or vehicle-mounted terminal that includes a memory and a processor. Taking a vehicle-mounted terminal as an example, the vehicle-mounted terminal may include one or more processors and a memory for storing data. Optionally, the vehicle-mounted terminal may also include a communication device for communication functions and a display device. Those skilled in the art will understand that the above structural description is merely illustrative and does not limit the structure of the vehicle-mounted terminal. For example, the vehicle-mounted terminal may include more or fewer components than those described above, or have a different configuration than those described above.

[0032] A processor may include one or more processing units. For example, a processor may include a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microprocessor, a field-programmable gate array (FPGA), a neural network processing unit (NPU), a tensor processing unit (TPU), or an artificial intelligence (AI) type processor. Different processing units may be independent components or integrated into one or more processors. In some instances, electronic devices may also include one or more processors.

[0033] The memory can be used to store computer programs, such as the computer program corresponding to the vehicle network harness configuration method in this embodiment of the invention. The processor implements the vehicle network harness configuration method by running the computer program stored in the memory. The memory may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to electronic devices via a grid. Examples of such grids include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0034] The communication device is used to receive or transmit data via a grid. Specific examples of the aforementioned grid may include a wireless grid provided by the mobile terminal's communication provider. In one example, the communication device includes a network interface controller (NIC), which can connect to other grid devices via a base station to communicate with the Internet. In another example, the communication device may be a radio frequency (RF) module used for wireless communication with the Internet. In some embodiments of this solution, the communication device is used to connect to mobile devices such as mobile phones and tablets, enabling the mobile device to send commands to the vehicle-mounted terminal.

[0035] The display device can be a touchscreen liquid crystal display (LCD) or a touch display (also referred to as a "touchscreen" or "touch display screen"). This LCD allows the user to interact with the user interface of the in-vehicle terminal. In some embodiments, the in-vehicle terminal has a graphical user interface (GUI), allowing the user to interact with the GUI through finger contact and / or gestures on a touch-sensitive surface. The human-machine interaction function may include a vehicle gear shifting function, and executable instructions for performing these functions are configured / stored in one or more processor-executable computer program products or readable storage media.

[0036] Figure 1 This is a flowchart of a vehicle network harness configuration method according to one embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0037] Step S101: Obtain the vehicle's network topology requirements and network configuration requirements.

[0038] Optionally, the execution subject in this embodiment is the vehicle network configuration system. It should be noted that other electronic devices and processors can also be used as the execution subject, and no further limitations are made here.

[0039] In the technical solution provided by step S101 of the present invention, it is first necessary to determine whether the vehicle has low or high configuration requirements. This technical action determines whether the vehicle needs to merge multiple CAN buses (such as power bus, display bus, chassis bus) into a single bus structure (low configuration requirements) or needs to keep multiple buses independent and route data through a gateway (high configuration requirements).

[0040] Analyze the communication protocols between the various electronic control units (ECUs) inside the vehicle to identify the specific bus types involved (such as powertrain CAN, display CAN, chassis CAN, etc.) and the distribution of their high and low level signals (CAN_H / CAN_L) in order to determine the specific pin locations that need to be shorted or isolated.

[0041] The aforementioned network topology requirements refer to the structural form of physical connections and logical communication between various nodes within the vehicle (such as the engine controller, ABS module, and instrument cluster). Specifically, in this solution, it refers to whether to merge multiple independent CAN buses into one (single-bus topology) or to maintain multiple independent CAN buses and interact through a gateway (multi-bus topology).

[0042] The aforementioned network configuration requirements refer to the specific requirements for the quantity, type, and connection method of in-vehicle network devices, depending on the different optional packages offered by the vehicle model. This directly determines the specific topology that the wiring harness needs to support and is the basis for deciding whether to install a circuit breaker.

[0043] As an optional implementation, in the vehicle manufacturing execution system, the configuration code of the vehicle is automatically read based on the vehicle's production order number. The system pre-defines the mapping relationship between the configuration code and the network topology. If the order corresponds to a low-configuration model, the system generates an instruction requiring the assembly station to install a "configurable universal shorter circuit breaker" at the gateway connector to short-circuit the powertrain, comfort, and chassis CAN buses. If the order corresponds to a high-configuration model, the system instructs to skip the shorter circuit breaker installation step and maintain the circuit's independence.

[0044] As an alternative implementation, during wire harness pre-assembly or vehicle inspection, technicians use a handheld diagnostic tool to read the vehicle's VIN code and configuration information. The diagnostic tool screen displays the required network topology for the vehicle (such as "single bus mode" or "multi-bus mode"). If the display indicates that a bus needs to be merged, the technician manually selects the corresponding universal shorting plug and inserts it into the gateway terminal connector; if the display indicates that an independent bus is required, the technician confirms that the connector is unused and no further action is needed.

[0045] It is worth noting that by accurately obtaining the vehicle's network topology and configuration requirements, the design of the main wiring harness can be directly unified and standardized. This technical step allows main wiring harnesses of the same physical specification to avoid repeated design modifications for different configurations. Only during the final assembly stage is the decision made regarding whether to add a circuit breaker based on the obtained requirements, thus flexibly adapting to various network architectures. This fundamentally eliminates the problem of a surge in wiring harness varieties caused by numerous configurations, significantly reducing the design complexity of wiring harnesses, material management costs, and the risk of pin definition errors, and realizing the platform-based scalability of the wiring harness system.

[0046] Step S102: Configure the vehicle's initial network harness based on network topology requirements.

[0047] In the technical solution provided by step S102 of the present invention, the obtained network topology requirements (such as "single bus mode" or "multi-bus mode") are matched with the preset wiring harness connection logic. The system needs to identify which CAN bus channels (such as power CAN, display CAN, chassis CAN) need to be electrically connected under the current requirements, and which need to be kept isolated.

[0048] Furthermore, based on the mapping results, the physical state of the vehicle's pre-fabricated initial network harness is adjusted. If the requirement is a merged bus, the originally independent line nodes are electrically shorted by connecting a circuit breaker; if the requirement is an independent bus, the lines are kept disconnected or logically routed through a gateway.

[0049] The aforementioned initial network harness refers to the basic wiring harness components that are pre-installed in the vehicle before specific configuration. They generally have common interface definitions and reserved connection points, but have not yet formed a final electrical connection state. They are in a "semi-finished" state awaiting configuration and can adapt to various potential topologies.

[0050] The aforementioned network topology requirements, specifically in this application, refer to specific instructions regarding the physical connections of the wiring harnesses, that is, clearly indicating which bus nodes should be shorted to form a single communication domain, or which nodes should remain independent to maintain a multi-communication domain architecture.

[0051] As an optional implementation, on an automated assembly line, after receiving a network topology requirement command, the central control unit drives a robotic arm to grasp the corresponding "configurable universal shorting device". The robotic arm precisely inserts the shorting device into the designated reserved hole of the gateway connector in the initial network harness. The conductive plate inside the shorting device instantly physically shorts the power CAN_H / L (high and low level pins of the power CAN bus) and display CAN_H / L (high and low level pins of the display CAN bus), automatically completing the topology configuration from "multi-channel independent" to "single-channel combined" without manual intervention.

[0052] It's worth noting that by configuring the initial network cables based on network topology requirements, the same set of basic wiring harness hardware can be adapted to multiple network architectures. This technique eliminates the need for customized internal wiring designs for different vehicle configurations; the electrical connection state of the wiring harness can be flexibly switched simply by changing the installation or location of the circuit breaker. This eliminates the need to develop dedicated wiring harnesses for each network configuration, significantly reducing the number of wiring harnesses, lowering mold development costs and warehouse management complexity, while ensuring the consistency and reliability of the physical connections of the wiring harnesses across different vehicle configurations.

[0053] Step S103: In response to the network configuration requirement being the first configuration requirement, configure the vehicle's target network harness based on the initial network harness and short-circuit loop.

[0054] In the technical solution provided by step S103 of the present invention, the system first verifies whether the current network configuration requirement belongs to the "first configuration requirement" (usually referring to a simplified topology that needs to merge multiple buses to reduce costs, such as low-configuration vehicle models). Only when the requirement matches is the subsequent circuit breaker installation action triggered.

[0055] After confirming the requirements, the "configurable universal circuit breaker" is connected to the reserved interface of the initial network harness. The conductive elements inside the circuit breaker will physically bridge the originally independent multiple sets of CAN bus signal lines (such as connecting the H / L lines of the power CAN and display CAN respectively), thereby artificially constructing an electrical "short circuit loop" inside the initial harness.

[0056] Furthermore, by establishing the aforementioned short-circuit loop, the electrical characteristics of the initial network harness can be changed, that is, from supporting multiple independent communications to supporting single-channel combined communications, ultimately forming a "target network harness" that meets the first configuration requirements.

[0057] The aforementioned first configuration requirement refers to a specific vehicle network architecture requirement, typically corresponding to lower-spec models or simplified network topologies. Under this requirement, the vehicle does not need a separate gateway to route data from different domains. Instead, it needs to physically short-join multiple CAN buses for powertrain, chassis, display, etc., into a single common bus for communication.

[0058] The aforementioned short-circuit loop refers to the electrical conduction path formed within the initial network harness by inserting a general-purpose short circuit breaker. This loop forcibly connects multiple sets of originally isolated twisted-pair signals, placing multiple ECU nodes within the same broadcast domain and enabling direct signal pass-through rather than routing and forwarding.

[0059] The aforementioned target network harness refers to the finished harness that, after configuration steps, ultimately meets the installation requirements of a specific vehicle model (i.e., the first configuration requirement vehicle model).

[0060] As an optional implementation, the automated assembly robot reads the configuration instructions issued by the system. If the instruction is identified as "first configuration requirement," the robot's end effector automatically grasps a standard shorting circuit breaker assembly and precisely inserts it into the designated port of the initial network harness on the conveyor belt. After the insertion is completed, the robot's built-in vision sensor confirms that the shorting circuit breaker is in place and verifies whether the short-circuit loop has been successfully established using an electrical test probe. If the verification is successful, the robot defines the harness as the "target network harness" and places it in the finished product area; if it is not the first configuration requirement, the robot skips this step and directly transfers the initial harness.

[0061] It is worth noting that by responding to the initial configuration requirements and utilizing short-circuit loops to configure the target network harness, it is possible to rapidly derive low-cost configuration vehicle harnesses using a single hardware platform. This technical step eliminates the need to redesign internal wiring or develop dedicated molds for harnesses used in lower-spec models; simply adding a low-cost shorter circuit breaker to the existing general-purpose harness achieves bus merging. This reduces the material costs and R&D amortization costs of harnesses for lower-spec models, while ensuring zero downtime on the production line when switching between different configuration models, significantly improving the flexibility and economic efficiency of harness manufacturing.

[0062] Step S104: In response to the network configuration requirement being a second configuration requirement, configure the vehicle's target network harness based on the initial network harness, wherein the number of configuration services supported by the second configuration requirement is higher than the number of configuration services supported by the first configuration requirement.

[0063] In the technical solution provided by step S104 of the present invention, the system first determines that the current network configuration requirement belongs to the "second configuration requirement", that is, it identifies that the vehicle needs to support more independent communication domains, higher data bandwidth or more complex gateway routing functions (such as the simultaneous existence of multiple independent CAN buses for power, chassis, display, entertainment and other purposes).

[0064] Unlike the first configuration requirement, step S104 requires either "not installing a circuit breaker" or "keeping the circuit open." The system control assembly process skips the circuit breaker insertion step, ensuring that the lines reserved for different bus systems in the initial network harness (such as power CAN_H / L and display CAN_H / L) are physically electrically isolated and do not conduct to each other.

[0065] Furthermore, while maintaining the independence of the lines, it is confirmed that the initial network harness is capable of connecting to a central gateway or multi-domain controller. At this point, the initial network harness is directly converted into the target network harness, whose internal structure supports logical data exchange between independent buses through the gateway, rather than physical signal merging.

[0066] The second configuration requirement mentioned above refers to a high-level vehicle network architecture requirement, typically corresponding to high-configuration models. Under this requirement, the vehicle needs to support multiple independent communication domains (such as powertrain domain, body domain, intelligent driving domain, etc.), with controlled data routing between each domain through gateways to ensure high real-time performance, high security, and large data volume transmission requirements.

[0067] The aforementioned number of configuration services refers to the number of independent communication channels supported by the network harness, the total number of connected ECU nodes, and the number of complex function combinations that can be implemented. It is worth noting that the second configuration requirement supports a higher number of configuration services than the first configuration requirement, meaning that it can support more types of sensors, controllers, and more complex vehicle functions (such as advanced autonomous driving, multi-screen interaction, etc.).

[0068] The aforementioned target network harness (second configuration) refers to the finished harness that maintains the initial network harness in a multi-path independent state. It has no internal short-circuit bridging and retains complete independent twisted-pair pairs. It is designed specifically for high-end vehicle models that require complex routing communication through a gateway.

[0069] As an optional implementation, on the final assembly line, when the system identifies a vehicle order as a "second configuration requirement" (such as a high-end version), it automatically sends a "skip circuit breaker installation" command to the workstation terminal. When the initial network harness flows through this workstation, neither the robotic arm nor a human performs any insertion operations; the harness maintains its original multi-path independent state from the factory. The system automatically records this harness as a "high-end target harness" and directly transfers it to the gateway installation workstation.

[0070] As an alternative implementation, during the configuration phase, the detection device scans the incoming initial network harness. If it is confirmed as a "second configuration requirement," the device initiates a "vacancy detection" procedure, using probes to test the continuity of the reserved short-circuit holes. Only when all reserved holes are detected to be in an open state (i.e., no short-circuit plug is inserted) does the system determine that the configuration is successful and mark the harness as a "target network harness" that meets the second configuration requirement. If a short-circuit plug is detected as being incorrectly installed, the device immediately alarms and intercepts the connection to prevent network communication conflicts or gateway malfunctions in high-end models due to physical short circuits.

[0071] It's worth noting that by responding to the second configuration requirement and directly configuring the target network harness based on the initial network harness, a seamless adaptation of the same basic harness hardware to highly complex network architectures can be achieved. This technique eliminates the need to develop a completely independent harness mold or redesign internal wiring for high-end models. It simply leverages the inherent multi-path independence of the initial harness (i.e., no short-circuiting) to meet the stringent requirements of high-end models for multi-domain isolation, high bandwidth, and complex gateway routing. This not only eliminates the additional R&D costs for high-end model harnesses but also ensures a high degree of consistency in the physical structure of the harnesses between high- and low-end models, greatly simplifying vehicle supply chain management and production processes.

[0072] Steps S101 to S104 above show that, in this invention, by obtaining the vehicle's network topology requirements and network configuration requirements, the technical objective of configuring the vehicle's initial network harness based on the network topology requirements is achieved. This achieves the technical effect of configuring the vehicle's target network harness based on the initial network harness and short-circuit loop in response to the network configuration requirements as the first configuration requirement, and configuring the vehicle's target network harness based on the initial network harness in response to the network configuration requirements as the second configuration requirement. This solves the technical problem in the prior art where the design of multiple network harnesses is required to meet different network configuration requirements, resulting in high complexity in the harness design process.

[0073] The method described in this embodiment will now be described in further detail.

[0074] Step S201: Determine the number of controllers for the target controller based on network configuration requirements, wherein the target controller is connected to the vehicle;

[0075] Step S202: Compare the number of controllers with a preset value to obtain the comparison result;

[0076] Step S203: In response to the comparison result indicating that the number of controllers is greater than a preset value, determine the network configuration requirement as the second configuration requirement;

[0077] Step S204: In response to the comparison result indicating that the number of controllers is less than or equal to a preset value, the network configuration requirement is determined as the first configuration requirement.

[0078] In this embodiment, such as Figure 2 As shown, the system sends broadcast query commands via the vehicle communication bus (such as the OBD interface or gateway diagnostic port) or reads the pre-stored production configuration list to scan and count the total number of electronic control units (ECUs) that are actually connected and active on the current vehicle in real time.

[0079] The number of controllers obtained from the statistics is then compared arithmetically with a preset "numerical threshold" in the system. Specifically, the threshold is the critical point that distinguishes between simple and complex network architectures, and is used to quantitatively determine the richness of vehicle functions.

[0080] Furthermore, the configuration requirement type is automatically output based on the comparison results. If the number of controllers exceeds the threshold, the logic determines that the vehicle function is complex and the communication load is high, thus marking it as a "second configuration requirement" that requires an independent multi-bus; if the number of controllers does not exceed the threshold, it is determined that the function is relatively simple and marked as a "first configuration requirement" suitable for a single-path combined bus.

[0081] The aforementioned target controller refers to the electronic control unit (ECU) in the vehicle responsible for specific functions (such as engine management, window control, ABS anti-lock braking, etc.). Specifically, in this solution, it refers to those control nodes that are physically connected to the vehicle's network harness and participate in communication; their number directly reflects the complexity of the network topology and the data traffic load.

[0082] The aforementioned preset values ​​refer to empirical thresholds or critical values ​​pre-set in the control system. These values ​​can be calculated based on network bandwidth capacity, signal conflict probability, and vehicle model positioning, and are used as the dividing line between "low-end / simplified network" and "high-end / full network".

[0083] The comparison result mentioned above refers to the logical state (i.e., "greater than" or "less than or equal to") generated after comparing the number of controllers with a preset value. Specifically, this result serves as the basis for triggering subsequent wiring harness configuration actions (installing a circuit breaker or keeping it independent).

[0084] As an optional implementation, during the vehicle off-line inspection, automated testing equipment connects to the vehicle's diagnostic interface and sends node discovery requests to the entire vehicle. The equipment counts the number of ECUs that receive responses (e.g., 25 nodes). The system compares the number of ECUs (25) with a preset value (e.g., 15). Since 25 is greater than 15, the comparison result is "greater than," and the system immediately and automatically generates an instruction to lock the vehicle's network configuration requirement as "second configuration requirement" and instructs the production line to skip the circuit breaker installation process, retaining multiple independent topologies.

[0085] As an alternative implementation, during the production planning phase, the system extracts the bill of materials for the vehicle order and counts the quantity of all controller-type parts included (e.g., down to 8 nodes). This quantity is transmitted to the wiring harness configuration control system and compared with a preset value (e.g., 15). Since 8 is less than 15, the comparison result is "less than or equal to," and the system pre-marks the vehicle's network configuration requirement as "first configuration requirement." When the vehicle enters the final assembly line, the workstation terminal directly prompts technicians to install a universal shorting device to merge the buses and meet the low-configuration requirement.

[0086] It is worth noting that determining network configuration requirements by comparing the number of controllers with preset values ​​enables the objectivity and automation of network architecture determination. This technology eliminates the need for manual experience or cumbersome configuration code lookups, directly utilizing the physical scale of vehicle electronic nodes as a quantitative indicator to accurately and automatically differentiate the network requirements of high-end and low-end models. This not only eliminates wiring harness configuration errors caused by human judgment (such as incorrectly installing a circuit breaker in a high-end vehicle leading to communication failure, or failing to install a circuit breaker in a low-end vehicle resulting in cost waste), but also ensures a strict match between the wiring harness configuration strategy and the actual electronic load capacity of the vehicle, achieving standardization and efficient execution of production decision-making logic.

[0087] Step S301: Establish a first electrical connection between the first short-circuit loop and the initial network harness, and establish a second electrical connection between the second short-circuit loop and the initial network harness;

[0088] Step S302: Configure the target network harness based on the first electrical connection relationship and the second electrical connection relationship.

[0089] In this embodiment, the system identifies the different communication domains that need to be merged (e.g., "power domain + chassis domain + display domain"). Subsequently, the "first short-circuit loop" and the "second short-circuit loop" are activated or installed respectively. The first short-circuit loop is responsible for physically connecting the high-level pins of the three CAN buses (e.g., CAN1_H, CAN2_H, and CAN3_H), and the second short-circuit loop is responsible for connecting the low-level pins of the three CAN buses (e.g., CAN1_L, CAN2_L, and CAN3_L).

[0090] The pins of the first short-circuit loop are precisely connected to the corresponding first set of reserved interfaces in the initial network harness to establish the "first electrical connection relationship"; at the same time, the pins of the second short-circuit loop are connected to the second set of reserved interfaces to establish the "second electrical connection relationship".

[0091] Furthermore, based on the aforementioned electrical connections between the two paths (high and low levels), the initial network harness is reconstructed into a target network harness with a "merged bus" architecture. At this point, the vehicle network is no longer completely separate, but rather merged into an independent broadcast domain, with each domain containing multiple physically shorted buses, achieving a network topology configuration with low configuration requirements.

[0092] The aforementioned first / second electrical connection relationship refers to the specific conduction state formed between the short-circuit loop and the initial network harness. The first electrical connection relationship specifically refers to the physical conduction path (high level) between the first group of bus nodes; the second electrical connection relationship specifically refers to the physical conduction path (low level) between the second group of bus nodes.

[0093] As an optional implementation, an integrated "dual-channel configuration module" is used as the short-circuit component. This module internally encapsulates a first short-circuit loop and a second short-circuit loop. During assembly, a robotic arm or worker inserts this module into the large multi-pin connector of the initial network harness in one go. Contact A inside the module automatically establishes the first electrical connection (connecting the high-level pins of multiple CAN buses), and contact B automatically establishes the second electrical connection (connecting the low-level pins of multiple CAN buses). A single insertion and removal operation completes the reconstruction of two topologies, generating the target network harness supporting dual merged buses.

[0094] It is worth noting that by introducing first and second short-circuit loops and establishing electrical connections respectively, it is possible to achieve fine-grained hierarchical configuration of vehicle network topology, thereby improving the universal wiring harness platform's ability to cover all models (low-end and high-end) and significantly reducing the complexity of material management caused by configuration segmentation.

[0095] Step S401: Obtain multiple transmission buses of the initial network harness, wherein the multiple transmission buses include a power transmission bus, a chassis transmission bus, and a display transmission bus;

[0096] Step S402: Determine multiple high-level signal pins for multiple transmission buses, wherein each transmission bus corresponds to one high-level signal pin;

[0097] Step S403: Establish a path between multiple high-level signal pins and a common high-level node based on the first short-circuit loop.

[0098] In this embodiment, the system first scans the initial network harness, accurately identifying and extracting specific transmission bus groups that need to be merged from numerous lines. These include the "power transmission bus" responsible for engine / motor control, the "chassis transmission bus" responsible for suspension / steering control, and the "display transmission bus" responsible for instrument panel / central control screen communication. This step ensures the accuracy of the operated objects and avoids mistakenly connecting other irrelevant signals.

[0099] Within each identified transmission bus (twisted pair structure), the system further distinguishes and identifies the "high-level signal pin" (i.e., the CAN_H pin) representing a logic "1" or dominant potential. Since each bus has a pair of high and low level lines, this action ensures that only the high-level line is operated on, preventing common-mode interference or communication failure caused by incorrectly shorting the low-level line (CAN_L).

[0100] Furthermore, by utilizing the conductive structure inside the first short-circuit loop, all the high-level signal pins of the identified power, chassis, and display buses are simultaneously and physically connected to a unified "common high-level node." This technical action electrically forces the potential of these pins to be flattened, causing the high-level signals of the originally independent three buses to be physically merged into a single signal transmission channel.

[0101] Specifically, the powertrain / chassis / display transmission bus refers to the independent communication links in a vehicle that carry data from different functional domains. The powertrain transmission bus mainly connects core drive components such as the engine and transmission; the chassis transmission bus connects driving control components such as ABS and EPS; and the display transmission bus connects infotainment components such as the instrument cluster and HUD.

[0102] The aforementioned high-level signal pin refers to the connector pin (usually CAN_H) corresponding to the wire with the higher potential in the differential signal line pair. In CAN communication, the high-level line is responsible for transmitting the main dominant signal and is the key line that determines the bus logic state.

[0103] The aforementioned common high-level node refers to an electrical busbar located within the first short-circuit loop. All selected high-level signal pins are connected to this point, which serves as a physically "zero-impedance" connection point, enabling direct interconnection and potential equalization of multiple high-level signals.

[0104] As an optional implementation, the first short-circuit loop is designed as a plug-in with an internal star-shaped connection structure. When this plug-in is inserted into the reserved interface of the initial network harness, its internal copper busbar structure automatically contacts the high-level pins corresponding to the power, chassis, and display buses. The center point of the copper busbar is the "common high-level node," which directly fuses or presses these three pins together inside the plug-in. Thus, by simply inserting the plug-in, the physical parallel connection of the three bus high-level lines can be completed within milliseconds, forming a single high-level transmission channel.

[0105] As an alternative implementation, the first short-circuit loop can also employ a matrix contact design with multiple elastic probes at its bottom. During assembly, the control system drives the short-circuit loop downwards, causing the probes to precisely pierce or contact the insulation layers of the high-level lines of the power, chassis, and display buses (or directly contact the exposed pins). The printed circuit traces inside the short-circuit loop converge these probes to a common ground or power plane as a "common high-level node." This approach allows software definition of which pins connect to the common node; if an "autopilot bus" needs to be added in the future, only the wiring definition inside the short-circuit loop needs to be updated, without changing the wiring harness structure.

[0106] It is worth noting that by acquiring a specific transmission bus and establishing a path only between its high-level signal pins and the common high-level node, a semi-merged topology reconstruction for differential signal pairs can be achieved. The technical advantage of this step is that it enables the synchronization and merging of high-level signals on multiple buses without compromising the independence of the low-level signal line (CAN_L). This "single-line merging" mechanism provides a physical basis for building special hybrid communication protocols or redundant backup networks, allowing the initial network harness to flexibly adapt to intermediate configurations that only require partial signal fusion or have special requirements for high-level synchronization, thereby reducing the need for custom-designed harnesses for specific signal logic.

[0107] Step S501: Determine multiple low-level signal pins for multiple transmission buses, wherein each transmission bus corresponds to one low-level signal pin;

[0108] Step S502: Establish a path between multiple low-level signal pins and a common low-level node based on the second short-circuit loop.

[0109] In this embodiment, based on the transmission buses (power, chassis, display, etc.) identified in the previous step, the system further precisely locks the "low-level signal pin" (i.e. CAN_L pin) representing logic "0" or recessive potential in each bus. This action ensures that the operation object corresponds one-to-one with the high-level pin in steps S401-S403.

[0110] By utilizing the conductive medium inside the second short-circuit loop, all the aforementioned locked low-level signal pins (Power CAN_L, Chassis CAN_L, Display CAN_L) are simultaneously physically connected to a unified "common low-level node." This technique electrically forces the potential of these pins to be flattened, causing the low-level signals of the originally independent buses to be physically merged into a single return path.

[0111] Furthermore, once the low-level path is established, combined with the high-level path established in the previous steps, the complete twisted-pair pairs of the power bus, chassis bus, and display bus are physically shorted. At this point, multiple independent differential buses are electrically merged into a single shared bus, and all controllers connected to these original buses are now in the same broadcast domain.

[0112] The aforementioned low-level signal pin refers to the connector pin (usually CAN_L) corresponding to the wire with the lower potential in a differential communication line pair (such as the CAN bus). Together with the high-level pin, it forms a differential signal, responsible for transmitting the complementary state of the signal, and is a crucial part in ensuring communication anti-interference capability and logical integrity.

[0113] The aforementioned common low-level node refers to the electrical busbar set inside the second short-circuit loop, where all selected low-level signal pins converge. This node, as a physical "zero-impedance" connection point, enables direct interconnection and potential equalization of multiple low-level signals, and together with the "common high-level node," forms a complete short-circuit loop.

[0114] The aforementioned second short-circuit loop is a dedicated circuit component for handling low-level signal merging. It is physically isolated from the first short-circuit loop that handles high-level signals but functions in tandem, ensuring that high and low-level signals are correctly merged and avoiding common-mode voltage anomalies caused by cross-short circuits.

[0115] As an optional implementation, a "dedicated low-level short-circuit plug-in" symmetrical to the first short-circuit loop structure is used. This plug-in has an independent conductive bus specifically designed to correspond to the CAN_L pin position in the connector. When the assembly robot inserts this plug-in into the initial wiring harness, its internal contacts automatically bridge the low-level pins of the power, chassis, and display buses to the "common low-level node" at the center of the plug-in. Because the high and low levels are handled separately by two independent plug-ins, this implementation allows for flexible selection on the production line: if only the high level needs to be combined (special test mode), only the first plug-in can be installed; if complete merging is required, both plug-ins can be installed simultaneously, achieving extremely high process flexibility.

[0116] As an alternative implementation, the second short-circuit loop can also be integrated into a two-layer modular component. The upper layer of this component handles the high level (first loop), while the lower layer is dedicated to the low level (second loop). During this process, the elastic probe array on the lower layer of the module precisely presses against the low-level pins of all target buses and converges them to a "common low-level node" at the bottom through vertical vias within the module. This method establishes both high and low level paths simultaneously with a single plug-in / plug-out action, significantly improving the assembly line's cycle time and reducing the risk of accidentally omitting a single loop.

[0117] It's worth noting that by identifying the low-level signal pins of multiple transmission buses and establishing pathways between them and a common low-level node, the physical fusion of multiple independent differential buses can be achieved, forming a single shared communication domain. This step, combined with the previous high-level merging action, completely connects the previously isolated powertrain, chassis, and display buses electrically. All electronic control units (ECUs) connected to these buses can directly broadcast and receive data on the same physical network without the need for a gateway. This not only eliminates the physical isolation barriers between multiple buses, achieving the "single-bus architecture" required for lower-spec models, but also ensures the integrity of the differential signals (synchronous shorting of high and low levels), avoiding signal distortion or communication failures caused by shorting only a single wire.

[0118] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or grid device, etc.) to execute the methods of the various embodiments of the present invention.

[0119] Figure 3 This is a structural block diagram of a vehicle network harness configuration system 300 according to one embodiment of the present invention, such as... Figure 3 As shown, the system includes: a gateway connector 31, a circuit breaker 32, and a processor 33.

[0120] Gateway connector 31, which is configured with an initial network harness, wherein the initial network harness is configured based on network topology requirements;

[0121] The circuit breaker 32 has a short-circuit loop inside it.

[0122] Processor 33 is configured to configure a target network harness of a vehicle based on an initial network harness and a short-circuit loop in response to a first configuration requirement of network configuration requirements; and to configure a target network harness of a vehicle based on an initial network harness in response to a second configuration requirement of network configuration requirements.

[0123] The second configuration requirement supports a higher number of configuration services than the first configuration requirement.

[0124] Specifically, a gateway connector is a core physical interface component in a vehicle network architecture. It not only provides mechanical connection functions but also serves as the carrier of the "initial network harness." It is the execution terminal for configuring the system, allowing external components (such as circuit breakers) to be inserted to change the connectivity of internal wiring.

[0125] Specifically, a circuit breaker is a pluggable functional module that internally encapsulates a specific "short-circuit loop". Its function is to physically short-circuit the high / low level signals of multiple originally independent buses (such as CAN1, CAN2, CAN3) in the initial wiring harness together, thereby electrically merging them into a single bus to reduce network complexity and meet the needs of low-configuration vehicle models.

[0126] The aforementioned first and second configuration requirements refer to two different levels of vehicle network specification definitions. The "first configuration requirement" corresponds to lower-spec models with fewer functions and fewer controllers, requiring cost reduction through bus merging; the "second configuration requirement" corresponds to higher-spec models with more functions and more controllers, requiring independent bus channels to ensure high bandwidth and low latency, supporting more configuration services.

[0127] Specifically, an "initial network harness" is pre-installed inside the gateway connector. This harness is not customized for a single vehicle model, but is designed based on the maximum network topology requirements. It includes all possible independent transmission buses (such as independent lines for powertrain, chassis, display, and other domains), serving as a general physical platform to support different configuration requirements.

[0128] The processor reads the vehicle's "network configuration request" signal in real time. It first determines whether the request belongs to the "first configuration request" (low-end / simplified version) or the "second configuration request" (high-end / full version). This determination is usually based on the number of controllers or the list of functional services installed in the vehicle, where the second configuration request supports a significantly larger number of services than the first configuration request.

[0129] Furthermore, in response to the first configuration requirement, the processor triggers the actuator to connect the "circuit breaker" to the gateway connector. The "short-circuit loop" inside the circuit breaker establishes an electrical connection with a specific pin in the initial network harness, physically shorting and merging multiple independent transmission buses to form a "target network harness" (single-bus or low-bus architecture) serving the lower-spec vehicle.

[0130] For the second configuration requirement, the processor determines that there is no need to merge the buses, and maintains the original state of the "initial network harness" (i.e., without installing a short circuit breaker or a pass-through module), directly defining it as the "target network harness". At this time, the CAN buses of each domain remain independently isolated to support the complex multi-domain communication services of high-end models.

[0131] This embodiment also provides a vehicle network harness configuration device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0132] Figure 4 This is a structural block diagram of a vehicle network harness configuration device 400 according to one embodiment of the present invention, such as... Figure 4 As shown, the device includes: an acquisition module 41, a first configuration module 42, a second configuration module 43, and a third configuration module 44.

[0133] Module 41 is used to obtain the vehicle's network topology requirements and network configuration requirements;

[0134] The first configuration module 42 is used to configure the vehicle's initial network harness based on network topology requirements;

[0135] The second configuration module 43 is used to configure the vehicle's target network harness based on the initial network harness and short-circuit loop in response to the network configuration requirement as the first configuration requirement.

[0136] The third configuration module 44 is used to configure the vehicle's target network harness based on the initial network harness in response to the network configuration requirement as the second configuration requirement.

[0137] The second configuration requirement supports a higher number of configuration services than the first configuration requirement.

[0138] Optionally, the vehicle network harness configuration device 400 further includes: a first determining module, configured to determine the number of controllers of the target controller based on network configuration requirements, wherein the target controller is connected to the vehicle; a comparison module, configured to compare the number of controllers with a preset value to obtain a comparison result; a second determining module, configured to determine the network configuration requirement as a second configuration requirement in response to the comparison result indicating that the number of controllers is greater than the preset value; and a third determining module, configured to determine the network configuration requirement as a first configuration requirement in response to the comparison result indicating that the number of controllers is less than or equal to the preset value.

[0139] Optionally, the second configuration module 43 includes: an establishment unit, configured to establish a first electrical connection relationship between the first short-circuit loop and the initial network harness, and to establish a second electrical connection relationship between the second short-circuit loop and the initial network harness; and a first configuration unit, configured to configure the target network harness based on the first electrical connection relationship and the second electrical connection relationship.

[0140] Optionally, the establishment unit includes: an acquisition subunit for acquiring multiple transmission buses of the initial network harness, wherein the multiple transmission buses include a power transmission bus, a chassis transmission bus, and a display transmission bus; a first determination subunit for determining multiple high-level signal pins of the multiple transmission buses, wherein each transmission bus corresponds to one high-level signal pin; and a first establishment subunit for establishing a path between the multiple high-level signal pins and a common high-level node based on a first short-circuit loop.

[0141] Optionally, the establishment unit further includes: a second determining subunit, used to determine multiple low-level signal pins of multiple transmission buses, wherein each transmission bus corresponds to one low-level signal pin; and a second establishing subunit, used to establish a path between the multiple low-level signal pins and a common low-level node based on a second short-circuit loop.

[0142] Embodiments of the present invention also provide a vehicle including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the above-described vehicle network harness configuration method.

[0143] Optionally, in this embodiment, the vehicle may be configured to store a computer program for performing the following steps:

[0144] Step S101: Obtain the vehicle's network topology requirements and network configuration requirements;

[0145] Step S102: Configure the vehicle's initial network harness based on network topology requirements;

[0146] Step S103: In response to the network configuration requirement being the first configuration requirement, configure the vehicle's target network harness based on the initial network harness and short-circuit loop.

[0147] Step S104: In response to the network configuration requirement being a second configuration requirement, configure the vehicle's target network harness based on the initial network harness, wherein the number of configuration services supported by the second configuration requirement is higher than the number of configuration services supported by the first configuration requirement.

[0148] Optionally, when the processor executes the program, it also performs the following steps: determining the number of controllers of the target controller based on network configuration requirements, wherein the target controller is connected to the vehicle; comparing the number of controllers with a preset value to obtain a comparison result; in response to the comparison result indicating that the number of controllers is greater than the preset value, determining the network configuration requirement as a second configuration requirement; in response to the comparison result indicating that the number of controllers is less than or equal to the preset value, determining the network configuration requirement as a first configuration requirement.

[0149] Optionally, when the processor executes the program, it also performs the following steps: establishing a first electrical connection relationship between the first short-circuit loop and the initial network harness, and establishing a second electrical connection relationship between the second short-circuit loop and the initial network harness; configuring the target network harness based on the first electrical connection relationship and the second electrical connection relationship.

[0150] Optionally, the processor may further implement the following steps when executing the program: acquiring multiple transmission buses of the initial network harness, wherein the multiple transmission buses include a power transmission bus, a chassis transmission bus, and a display transmission bus; determining multiple high-level signal pins of the multiple transmission buses, wherein each transmission bus corresponds to one high-level signal pin; and establishing a path between the multiple high-level signal pins and a common high-level node based on a first short-circuit loop.

[0151] Optionally, when the processor executes the program, it also performs the following steps: determining multiple low-level signal pins of multiple transmission buses, wherein each transmission bus corresponds to one low-level signal pin; and establishing a path between the multiple low-level signal pins and a common low-level node based on a second short-circuit loop.

[0152] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0153] Embodiments of the present invention also provide an electronic device, such as... Figure 5 As shown, it includes a memory 51 and a processor 52, wherein the memory stores a computer program and the processor is configured to run the computer program to execute the above-described vehicle network harness configuration method.

[0154] Optionally, in this embodiment, the electronic device may be configured to store a computer program for performing the following steps:

[0155] Step S101: Obtain the vehicle's network topology requirements and network configuration requirements;

[0156] Step S102: Configure the vehicle's initial network harness based on network topology requirements;

[0157] Step S103: In response to the network configuration requirement being the first configuration requirement, configure the vehicle's target network harness based on the initial network harness and short-circuit loop.

[0158] Step S104: In response to the network configuration requirement being a second configuration requirement, configure the vehicle's target network harness based on the initial network harness, wherein the number of configuration services supported by the second configuration requirement is higher than the number of configuration services supported by the first configuration requirement.

[0159] Optionally, when the processor executes the program, it also performs the following steps: determining the number of controllers of the target controller based on network configuration requirements, wherein the target controller is connected to the vehicle; comparing the number of controllers with a preset value to obtain a comparison result; in response to the comparison result indicating that the number of controllers is greater than the preset value, determining the network configuration requirement as a second configuration requirement; in response to the comparison result indicating that the number of controllers is less than or equal to the preset value, determining the network configuration requirement as a first configuration requirement.

[0160] Optionally, when the processor executes the program, it also performs the following steps: establishing a first electrical connection relationship between the first short-circuit loop and the initial network harness, and establishing a second electrical connection relationship between the second short-circuit loop and the initial network harness; configuring the target network harness based on the first electrical connection relationship and the second electrical connection relationship.

[0161] Optionally, the processor may further implement the following steps when executing the program: acquiring multiple transmission buses of the initial network harness, wherein the multiple transmission buses include a power transmission bus, a chassis transmission bus, and a display transmission bus; determining multiple high-level signal pins of the multiple transmission buses, wherein each transmission bus corresponds to one high-level signal pin; and establishing a path between the multiple high-level signal pins and a common high-level node based on a first short-circuit loop.

[0162] Optionally, when the processor executes the program, it also performs the following steps: determining multiple low-level signal pins of multiple transmission buses, wherein each transmission bus corresponds to one low-level signal pin; and establishing a path between the multiple low-level signal pins and a common low-level node based on a second short-circuit loop.

[0163] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0164] Embodiments of the present invention also provide a computer-readable storage medium storing a computer program configured to execute the above-described vehicle network harness configuration method when run on a computer or processor.

[0165] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0166] Step S101: Obtain the vehicle's network topology requirements and network configuration requirements;

[0167] Step S102: Configure the vehicle's initial network harness based on network topology requirements;

[0168] Step S103: In response to the network configuration requirement being the first configuration requirement, configure the vehicle's target network harness based on the initial network harness and short-circuit loop.

[0169] Step S104: In response to the network configuration requirement being a second configuration requirement, configure the vehicle's target network harness based on the initial network harness, wherein the number of configuration services supported by the second configuration requirement is higher than the number of configuration services supported by the first configuration requirement.

[0170] Optionally, the storage medium is configured to store program code for performing the following steps: determining the number of controllers of the target controller based on network configuration requirements, wherein the target controller is connected to the vehicle; comparing the number of controllers with a preset value to obtain a comparison result; in response to the comparison result indicating that the number of controllers is greater than the preset value, determining the network configuration requirement as a second configuration requirement; in response to the comparison result indicating that the number of controllers is less than or equal to the preset value, determining the network configuration requirement as a first configuration requirement.

[0171] Optionally, the storage medium is configured to store program code for performing the following steps: establishing a first electrical connection between a first short-circuit loop and an initial network harness, and establishing a second electrical connection between a second short-circuit loop and the initial network harness; configuring the target network harness based on the first and second electrical connection relationships.

[0172] Optionally, the storage medium is configured to store program code for performing the following steps: acquiring multiple transmission buses of the initial network harness, wherein the multiple transmission buses include a power transmission bus, a chassis transmission bus, and a display transmission bus; determining multiple high-level signal pins of the multiple transmission buses, wherein each transmission bus corresponds to one high-level signal pin; and establishing a path between the multiple high-level signal pins and a common high-level node based on a first short-circuit loop.

[0173] Optionally, the storage medium is configured to store program code for performing the following steps: determining multiple low-level signal pins of multiple transmission buses, wherein each transmission bus corresponds to one low-level signal pin; establishing a path between the multiple low-level signal pins and a common low-level node based on a second short-circuit loop.

[0174] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0175] Embodiments of the present invention also provide a computer program product, including a computer program, wherein the computer program, when executed by a processor, implements the steps of the above-described vehicle network harness configuration method.

[0176] Optionally, in this embodiment, the computer program product described above may be configured to store a computer program for performing the following steps:

[0177] Step S101: Obtain the vehicle's network topology requirements and network configuration requirements;

[0178] Step S102: Configure the vehicle's initial network harness based on network topology requirements;

[0179] Step S103: In response to the network configuration requirement being the first configuration requirement, configure the vehicle's target network harness based on the initial network harness and short-circuit loop.

[0180] Step S104: In response to the network configuration requirement being a second configuration requirement, configure the vehicle's target network harness based on the initial network harness, wherein the number of configuration services supported by the second configuration requirement is higher than the number of configuration services supported by the first configuration requirement.

[0181] Optionally, when the computer program executes the program, it further implements the following steps: determining the number of controllers of the target controller based on network configuration requirements, wherein the target controller is connected to the vehicle; comparing the number of controllers with a preset value to obtain a comparison result; in response to the comparison result indicating that the number of controllers is greater than the preset value, determining the network configuration requirement as a second configuration requirement; in response to the comparison result indicating that the number of controllers is less than or equal to the preset value, determining the network configuration requirement as a first configuration requirement.

[0182] Optionally, when the computer program executes the program, it also performs the following steps: establishing a first electrical connection relationship between the first short-circuit loop and the initial network harness, and establishing a second electrical connection relationship between the second short-circuit loop and the initial network harness; configuring the target network harness based on the first electrical connection relationship and the second electrical connection relationship.

[0183] Optionally, when the computer program executes the program, it also performs the following steps: acquiring multiple transmission buses of the initial network harness, wherein the multiple transmission buses include a power transmission bus, a chassis transmission bus, and a display transmission bus; determining multiple high-level signal pins of the multiple transmission buses, wherein each transmission bus corresponds to one high-level signal pin; and establishing a path between the multiple high-level signal pins and a common high-level node based on a first short-circuit loop.

[0184] Optionally, when the computer program executes the program, it also performs the following steps: determining multiple low-level signal pins of multiple transmission buses, wherein each transmission bus corresponds to one low-level signal pin; and establishing a path between the multiple low-level signal pins and a common low-level node based on a second short-circuit loop.

[0185] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0186] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0187] In the embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0188] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0189] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0190] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or grid device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0191] The above are merely preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for configuring a vehicle network harness, characterized in that, include: Obtain the vehicle's network topology and network configuration requirements; Configure the initial network harness of the vehicle based on the network topology requirements; In response to the network configuration requirement being the first configuration requirement, the target network harness of the vehicle is configured based on the initial network harness and the short-circuit loop; In response to the network configuration requirement being a second configuration requirement, the target network harness of the vehicle is configured based on the initial network harness. The second configuration requirement supports a higher number of configuration services than the first configuration requirement.

2. The method for configuring a vehicle network harness according to claim 1, characterized in that, The method further includes: The number of target controllers is determined based on the network configuration requirements, wherein the target controllers are connected to the vehicle; The number of controllers is compared with a preset value to obtain the comparison result; In response to the comparison result indicating that the number of controllers is greater than the preset value, the network configuration requirement is determined to be the second configuration requirement; In response to the comparison result indicating that the number of controllers is less than or equal to the preset value, the network configuration requirement is determined to be the first configuration requirement.

3. The method for configuring a vehicle network harness according to claim 1, characterized in that, The short-circuit loop includes a first short-circuit loop and a second short-circuit loop. Configuring the target network harness of the vehicle based on the initial network harness, the first short-circuit loop, and the second short-circuit loop includes: Establish a first electrical connection between the first short-circuit loop and the initial network harness, and establish a second electrical connection between the second short-circuit loop and the initial network harness; Configure the target network harness based on the first electrical connection relationship and the second electrical connection relationship.

4. The method for configuring a vehicle network harness according to claim 3, characterized in that, Establishing the first electrical connection between the first short-circuit loop and the initial network harness includes: Obtain multiple transmission buses of the initial network harness, wherein the multiple transmission buses include a power transmission bus, a chassis transmission bus, and a display transmission bus; Determine multiple high-level signal pins for the multiple transmission buses, wherein each transmission bus corresponds to one high-level signal pin; The first short-circuit loop establishes a path between the multiple high-level signal pins and the common high-level node.

5. The method for configuring a vehicle network harness according to claim 4, characterized in that, Establishing the second electrical connection between the second short-circuit loop and the initial network harness includes: Determine multiple low-level signal pins for the multiple transmission buses, wherein each transmission bus corresponds to one low-level signal pin; The second short-circuit loop establishes a path between the plurality of low-level signal pins and the common low-level node.

6. A configuration system for a vehicle network harness, characterized in that, include: A gateway connector, wherein an initial network harness is configured within the gateway connector, and the initial network harness is configured based on network topology requirements; A circuit breaker, wherein a short-circuit circuit is configured within the circuit breaker; A processor is configured to configure a target network harness of a vehicle based on the initial network harness and the short-circuit loop in response to a first configuration requirement of network configuration; and to configure the target network harness of the vehicle based on the initial network harness in response to a second configuration requirement of network configuration. The second configuration requirement supports a higher number of configuration services than the first configuration requirement.

7. A device for configuring a vehicle network harness, characterized in that, include: The acquisition module is used to acquire the vehicle's network topology and network configuration requirements. The first configuration module is used to configure the initial network harness of the vehicle based on the network topology requirements; The second configuration module is used to configure the target network harness of the vehicle based on the initial network harness and the short-circuit loop in response to the network configuration requirement being the first configuration requirement. The third configuration module is used to configure the target network harness of the vehicle based on the initial network harness in response to the network configuration requirement being the second configuration requirement. The second configuration requirement supports a higher number of configuration services than the first configuration requirement.

8. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the vehicle network harness configuration method as described in any one of claims 1 to 5.

9. A vehicle comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the vehicle network harness configuration method as described in any one of claims 1 to 5.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the vehicle network harness configuration method according to any one of claims 1 to 5 when run on a computer or processor.

Images