Vehicle and network topology thereof

Abstract

The invention provides a vehicle and a network topology structure thereof, and relates to the technical field of vehicles. The network topology structure comprises a first network topology, a second network topology and a vehicle control unit. Wherein the first network topology is connected with the vehicle control unit to form a vehicle area network for realizing basic functions of a vehicle; the second network topology is used for deploying a gateway and a scene module, the gateway is used for connecting the vehicle control unit and the scene module to form an expansion area network, and the scene module is used for achieving the scene function of the vehicle. The basic function of the vehicle can be realized through the whole vehicle area network; according to a scenarized function demand, a scenarized module in the expansion area network of the application is subjected to modular decline, so that a scenarized function of a vehicle is realized; through the method, the development work of wiring harness and software levels related to the conversion between architectures of the network topology structure is reduced, so that the problem of poor flexibility of the existing network topology structure is relieved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a vehicle and a network topology thereof. Background Art

[0002] The network topology of a vehicle is a system composed of various components and transmitting information through a certain communication medium. The components mainly include the control module, actuators and sensors in the vehicle, and the communication medium can be a bus connecting the components, such as the Controller Area Network (CAN) bus or the Local Interconnect Network (LIN) bus.

[0003] At present, there are two common network topologies for vehicles: the first network topology uses the vehicle controller as the gateway, and the vehicle has two networks, one for power-related and one for other components; the second network topology has a separate gateway and is differentiated according to functional domains. The vehicle contains multiple networks, such as power CAN, body CAN, chassis CAN, intelligent driving CAN, etc. However, the conversion between the architectures of these two network topologies involves development work at the wiring harness and software levels, and has poor flexibility. Summary of the invention

[0004] The present application provides a vehicle and a network topology structure thereof, so as to alleviate the problem of poor flexibility of existing network topology structures.

[0005] In a first aspect, the present application provides a network topology structure of a vehicle, the network topology structure comprising a first network topology, a second network topology and a vehicle controller; wherein:

[0006] The first network topology is connected to the vehicle controller to form a vehicle area network for realizing the basic functions of the vehicle;

[0007] The second network topology is used to deploy gateways and scenario modules. The gateway is used to connect the vehicle controller and the scenario module to form an expansion area network. The scenario module is used to realize the scenario-based functions of the vehicle.

[0008] In a possible implementation, the gateway is specifically used to respond to received signals, determine a routing object according to a signal type of the signal, and route the signal to the routing object, wherein the routing object includes a vehicle controller and a scene module included in the second network topology.

[0009] In a possible implementation manner, a terminal resistor is provided between the gateway and the scene module.

[0010] In a possible implementation, the scenario module includes at least: components involved in one or more combinations of the cockpit domain, the intelligent driving domain, and the external transmission domain.

[0011] In a possible implementation, the network topology completes the compilation of the communication protocol according to maximum functionality.

[0012] In a possible implementation, the network topology passes the functional verification of maximum functionality, each network physical layer, link layer test, controller static current test, wake-up and sleep test.

[0013] In a possible implementation manner, the network topology structure corresponds to a vehicle signal list, and the vehicle signal list includes a bodywork signal list, a modification control signal list, and a low-voltage plug-in list.

[0014] In a second aspect, the present application provides a vehicle, comprising: a vehicle body and a network topology structure of the vehicle as described in any one of the first aspects.

[0015] In a possible implementation, the first network topology and the second network topology are arranged at positions on the vehicle body independently of each other.

[0016] In a possible implementation manner, the physical arrangement of the second network topology and the wiring harness plug-in reservation have been completed in the vehicle body.

[0017] The vehicle and its network topology provided by the present application include a first network topology, a second network topology and a vehicle controller; wherein: the first network topology is connected to the vehicle controller to form a vehicle area network for realizing the basic functions of the vehicle; the second network topology is used to deploy a gateway and a scene module, the gateway is used to connect the vehicle controller and the scene module to form an expansion area network, and the scene module is used to realize the scenario functions of the vehicle. The basic functions of the vehicle can be realized through the vehicle area network of the present application; the scenario modules in the expansion area network of the present application are modularized and reduced according to the scenario function requirements, so as to realize the scenario functions of the vehicle; the above method is used to reduce the development work at the wiring harness and software levels involved in the conversion between the architectures of the network topology structure, so as to alleviate the problem of poor flexibility of the existing network topology structure. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0019] Figure 1 A schematic diagram of a vehicle network topology structure provided in an embodiment of the present application Figure 1 ;

[0020] Figure 2A schematic diagram of a flow chart of a bidirectional routing signal of a gateway provided in an embodiment of the present application;

[0021] Figure 3 A schematic diagram of a vehicle network topology provided in an embodiment of the present application Figure 2 .

[0022] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical scheme and advantages of the present application clearer, the technical scheme in the embodiment of the present application will be described in more detail below in conjunction with the drawings in the preferred embodiments of the present application. In the drawings, the same or similar reference numerals throughout represent the same or similar parts or parts with the same or similar functions. The described embodiments are part of the embodiments of the present application, not all of the embodiments. The embodiments described below with reference to the drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limitations on the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application. The embodiments of the present application are described in detail below in conjunction with the drawings.

[0024] Those skilled in the art should understand that these implementations are only used to explain the technical principles of the present application and are not intended to limit the protection scope of the present application. Those skilled in the art can make adjustments to them as needed to adapt to specific application scenarios.

[0025] For different usage scenarios, the common network topology structures on the current market cannot cover all scenarios. The conversion between network topology architectures involves development work at the wiring harness and software levels, and has poor flexibility.

[0026] In one example, if the vehicle is only used as a tool vehicle for individual customers and the required vehicle functions are relatively simple, if a separate gateway is used in the vehicle to form a 4- to 5-way network topology, this will lead to an increase in the cost of the vehicle without realizing the value, that is, there will be a waste of cost.

[0027] In another example, for modification customers and large leasing customers, if the network topology is too simple during the vehicle development stage, this will lead to higher costs for customers' subsequent installations and a longer time spent in meeting customer needs. There is a possibility that the vehicle network load after loading may exceed 50%.

[0028] Therefore, in response to the problems existing in common network topology structures, the network topology structure of the vehicle provided by this application is more flexible, and scenario-based modules can be flexibly selected according to different usage requirements, so as to achieve the goal of reducing the cost of the whole vehicle and quickly meeting customer needs. Furthermore, in response to the subsequent installation needs of the vehicle, the network topology structure of the vehicle provided by this application has completed the network forwarding verification and wiring harness system design in the research and development stage, and customers can install the corresponding parts non-destructively and quickly according to their own installation needs.

[0029] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0030] Figure 1 A schematic diagram of a vehicle network topology structure provided in an embodiment of the present application Figure 1 ,like Figure 1 As shown, the network topology structure includes a first network topology structure 101, a second network topology structure 102 and a vehicle controller 103; wherein:

[0031] The first network topology 101 is connected to the vehicle control unit (VCU) 103 to form a vehicle area network for realizing basic functions of the vehicle;

[0032] The second network topology 102 is used to deploy a gateway (GW for short) and a scene module. The gateway is used to connect the vehicle controller and the scene module to form an expansion area network. The scene module is used to realize the scene-based functions of the vehicle.

[0033] In this embodiment, it can be understood that the vehicle controller is a key electronic control unit in the vehicle, responsible for managing and coordinating various subsystems of the vehicle.

[0034] The first network topology 101 is connected to the vehicle controller 103 to form a vehicle area network, which can be used to implement basic functions of the vehicle. The basic functions of the vehicle include but are not limited to the following: driving the vehicle, instrument display in the cockpit, cooling control, low speed reminder, and chassis function.

[0035] The second network topology 102 is used to deploy the gateway and the scenario module. When forming the extended area network of the vehicle, the gateway is needed to connect the vehicle controller and the scenario module. Among them, the scenario module is used to realize the scenario function of the vehicle, and the scenario function of the vehicle refers to the function that the vehicle has when meeting the requirements of different scenarios.

[0036] To sum up, it can be understood that when only basic functional requirements are met, the vehicle area network can be realized; if there are scenario-based functional requirements, the expansion area network is required to achieve it.

[0037] An embodiment of the present application provides a network topology structure of a vehicle, wherein the network topology structure includes a vehicle area network and an expansion area network. The basic functions of the vehicle can be realized through the vehicle area network; the scenario modules in the expansion area network are modularized and reduced according to the scenario function requirements, so as to realize the scenario functions of the vehicle; the conversion between architectures of the network topology structure is reduced by the above method, which involves the development work at the wiring harness and software levels, so as to alleviate the problem of poor flexibility of the existing network topology structure.

[0038] Based on the above embodiment, the gateway is specifically used to respond to the received signal, determine the routing object according to the signal type of the signal, and route the signal to the routing object, where the routing object includes the vehicle controller and the scene module included in the second network topology. Among them, the gateway is a network device that acts as a bridge in the network topology of the vehicle, connects different network topologies, and coordinates the communication between different network topologies.

[0039] In this embodiment, it can be understood that after the gateway responds to the received signal, the gateway determines the routing object according to the signal type of the signal. After determining the routing object, the signal is routed to the routing object through the gateway, wherein the routing object includes the vehicle controller and the scene module included in the second network topology.

[0040] For example, if the determined routing object is a vehicle controller, the signal is routed to the vehicle controller through the gateway; if the determined routing object is a scene module included in the second network topology, the signal is routed to the scene module included in the second network topology through the gateway.

[0041] by Figure 2 As an example, it explains how to use the gateway to bidirectionally route signals. Figure 2 A schematic diagram of a flow chart of a bidirectional routing signal of a gateway provided in an embodiment of the present application. Figure 2 It can be seen that when the signal type of the signal is one of the following signal types: electronic parking signal, tire pressure status signal, airbag status signal, keyless entry related signal, upper equipment status signals at all levels, financial lock input signal, the gateway will route the signal to the vehicle controller; when the signal type of the signal is one of the following signal types: according to GB / T32960 involving compliance test-related vehicle signals, financial lock feedback signals, upper equipment control signals, handbrake status signals, airbag fault status signals, remote lock interaction signals, the gateway will route the signal to the scenario module included in the second network topology.

[0042] The embodiments of the present application can improve the efficiency of signal transmission by determining a routing object according to the signal type of the signal and routing the signal to the routing object.

[0043] Based on the above embodiment, a terminal resistor is provided between the gateway and the scene module. Providing a terminal resistor between the gateway and the scene module can effectively avoid sudden voltage changes, thereby improving the stability of the network topology.

[0044] Based on the above embodiment, the scenario module includes at least: components involved in one or more combinations of the cockpit domain, the intelligent driving domain and the external transmission domain.

[0045] In this embodiment, it can be understood that the scene module at least includes: components involved in the cockpit domain, or components involved in the cockpit domain and the intelligent driving domain, or components involved in the cockpit domain, the intelligent driving domain and the external domain, or components involved in the cockpit domain and the external domain, or components involved in the external domain, and so on.

[0046] In one example, when the scenario-based functional requirements include electronic handbrakes and airbags, the scenario module at least includes the components involved in the cockpit domain.

[0047] In another example, when the scenario-based functional requirements include tire pressure monitoring, electronic handbrake, airbags, keyless entry, and assisted driving systems, the scenario module at least includes components involved in the cockpit domain and the intelligent driving domain.

[0048] In another example, when scenario-based functional requirements include body modification, financial locking of vehicles for major customers, and installation of telematics boxes (TBOX) for major customers, the scenario module at least includes components involved in the outbound domain.

[0049] The embodiment of the present application flexibly selects scenario modules according to scenario-based functional requirements, which can improve the flexibility of the network topology.

[0050] Furthermore, taking the scene module including the components involved in the cockpit domain, intelligent driving domain and outbound domain as an example, Figure 3 A schematic diagram of a vehicle network topology provided in an embodiment of the present application Figure 2 ,in, Figure 3 (a) represents the vehicle area network, and (b) represents the expansion area network. Figure 3 It can be seen that the network topology of the vehicle includes the vehicle area network and the expansion area network. Figure 31 and 2 together constitute the vehicle area network, and the rectangle with slashes represents the terminal resistance. It should be noted that when the vehicle needs to be connected to an off-board charger, the battery management system (BMS) of the vehicle area network needs to be connected to the off-board charger; the topological structure of the vehicle area network is self-consistent and has been widely used in mass-produced models.

[0051] from Figure 3 It can be seen that the vehicle area network includes the main and auxiliary drive controllers, BMS, anti-lock braking system (ABS), electronic water pump controller (WPC), electric power steering system (EPS), multimedia interactive system (MMI), acoustic vehicle alert system (AVAS), Instrument Cluster (IC), TBOX, and on-board diagnostic system (OBD).

[0052] Among them, ABS is used to periodically release and reapply braking force to ensure that the wheels remain rolling during braking; EPS is used to provide steering assistance through an electric motor; WPC is used to cool the engine; AVAS is used to generate sound to alert road users; IC is used to provide vehicle operating information to vehicle users; the main and auxiliary drive controller is used to coordinate and manage multiple motor drive systems; BMS is used to manage and protect the battery pack; OBD is used to monitor and diagnose the vehicle's operating status and fault conditions; TBOX is used to realize the vehicle's remote information processing and communication functions.

[0053] Furthermore, taking the scene module including components involved in the cockpit domain, intelligent driving domain and outbound domain as an example, when the gateway routes signals to the routing object, it first needs to determine whether the routing object is the vehicle area controller or the scene module. If the routing object is determined to be the vehicle area controller, the signal is routed to the vehicle area controller through the gateway; if the routing object is determined to be the scene module, it is necessary to further determine the routing object corresponding to the scene module.

[0054] In one example, if the signal type of the signal is an upper installation control signal, the routing object is the components involved in the outgoing domain corresponding to the scene module.

[0055] On the basis of the above-mentioned embodiment, the network topology structure completes the compilation of the communication protocol according to the maximum function. Among them, the communication protocol refers to a series of rules and standards followed by the sender and the receiver when transmitting data in the network. Furthermore, the compilation of the communication protocol according to the maximum function is to ensure that the data in the network topology structure can be accurately transmitted from the sender to the receiver. The specific implementation method of completing the compilation of the communication protocol according to the maximum function of different network topologies can be set according to actual needs.

[0056] In one example, in a star network topology, all nodes need to communicate through a central node. When the communication protocol is compiled according to maximum functionality, the load balancing and fault recovery mechanism of the central node must be considered.

[0057] The embodiment of the present application completes the compilation of the communication protocol according to the maximum functionality of the network topology structure, thereby realizing the maximum functionality of the network topology structure and ensuring the high efficiency of data transmission in the network topology structure.

[0058] On the basis of the above-mentioned embodiments, the network topology structure passes the functional verification of the maximum function, the test of each network physical layer, the link layer, the controller static current test, the wake-up and sleep test. Specifically, during the design and deployment of the network topology structure, a series of tests are performed to ensure that the network topology structure can pass the functional verification of the maximum function, the test of each network physical layer, the link layer, the controller static current test, the wake-up and sleep test. Among them, the functional verification of the maximum function of the network topology structure is the key to ensure that the vehicle can operate according to the expected function; the test of each network physical layer and link layer of the network topology structure is to ensure the reliability of the network physical layer and the link layer; the controller static current test of the network topology structure is to ensure the performance of the devices deployed in the network topology structure in the low power consumption mode; the wake-up and sleep test of the network topology structure is to determine the performance and function of the devices deployed in the network topology structure when waking up from the sleep state and entering the sleep state.

[0059] Furthermore, the order of functional verification of the maximum functionality of the network topology, testing of each network physical layer, link layer, controller static current testing, wake-up and sleep testing can be set according to actual needs.

[0060] In one implementation, the network topology structure is sequentially subjected to functional verification of maximum functionality, testing of each network physical layer, link layer, controller static current testing, and wake-up and sleep testing.

[0061] In another implementation, the network topology structure is sequentially subjected to network physical layer testing, link layer testing, controller static current testing, wake-up and sleep testing, and maximum functional verification.

[0062] The embodiments of the present application can ensure the high efficiency of data transmission in the network topology structure by performing functional verification of the maximum functionality of the network topology structure, testing of each network physical layer, link layer, controller static current testing, wake-up and sleep testing.

[0063] On the basis of the above embodiment, the network topology structure corresponds to a vehicle signal list, and the vehicle signal list includes a body signal list, a modification control signal list and a low-voltage plug-in list.

[0064] In this embodiment, it can be understood that the network topology structure described in the above embodiment corresponds to a vehicle signal list, wherein the vehicle signal list includes an upper installation information list, a modification control signal list, and a low-voltage plug-in list. This means that if there is a scenario-based function requirement for the vehicle, the component information required to realize the corresponding scenario-based requirement can be found from the vehicle signal list corresponding to the network topology structure of the vehicle. The scenario-based function of the vehicle is realized based on the queried component information.

[0065] The embodiment of the present application can quickly install components by searching for component information required to implement corresponding scenario requirements from a vehicle signal list corresponding to the vehicle's network topology structure, thereby reducing the difficulty of modifying the entire vehicle.

[0066] On the basis of the above embodiments, the embodiments of the present application further provide a vehicle, the vehicle including the network topology structure of the vehicle as described in any of the above embodiments. Furthermore, the layout positions of the above-mentioned first network topology and second network topology on the vehicle body are independent of each other. This means that the layout positions of the first network topology and the second network topology on the vehicle body do not affect each other, and changes in the second network topology structure will not affect the first network topology structure.

[0067] Furthermore, the physical layout of the second network topology and the wiring harness plug-in reservation have been completed in the vehicle body, such as various bracket fixations, CAN twisted pair cables in the wiring harness, controller power supply, CAN cables and opponent plug-ins. This means that if there is a scenario-based functional requirement, the components corresponding to the scenario-based functional requirements can be installed in the reserved physical layout and wiring harness plug-in of the second network topology without changing the network topology structure, so as to achieve lossless installation of components; if there is no scenario-based functional requirement, the reserved physical layout and wiring harness plug-in of the second network topology will not be processed in any way.

[0068] The embodiment of the present application can improve the flexibility of the network topology structure by reserving the physical layout and wiring harness plug-in of the second network topology.

[0069] Furthermore, during the vehicle development stage, the underlying design of the vehicle area network and the expansion area network of the network topology structure described in the above embodiment is completed; the physical layout of the controller in the expansion area network and the wiring harness plug-in are reserved, such as reserving various types of bracket fixes, CAN twisted pair cables in the wiring harness, controller power supply, CAN cables and opponent plug-ins; the correlation determination of the controllers required for the network topology is completed, and a controller function correlation determination list is generated.

[0070] Furthermore, if the user has scenario-based function requirements in the future, he only needs to determine the components corresponding to the scenario-based function requirements from the controller function relevance determination list, and install the components in the corresponding physical layout and wiring harness plug-in of the reserved second network topology to enable the vehicle to realize the scenario-based function.

[0071] In summary, the network topology structure provided by the embodiment of the present application is more flexible and can flexibly select scenario-based modules according to different scenario-based functional requirements, thereby achieving the goal of reducing the cost of the entire vehicle and quickly meeting different scenario-based functional requirements; at the same time, for subsequent installation needs of the vehicle, customers can quickly and non-destructively install corresponding components according to scenario-based functional requirements, thereby reducing the difficulty of vehicle modification.

[0072] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0073] In the description of the embodiments of the present application, it should be understood that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense. For example, it can be a fixed connection, or it can be indirectly connected through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to the specific circumstances. The orientation or position relationship indicated by the terms "upper", "lower", "front", "back", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc. is based on the orientation or position relationship shown in the accompanying drawings, which is only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present application. In the description of the present application, the meaning of "multiple" is two or more, unless otherwise precisely and specifically specified.

[0074] The terms "first", "second", "third", "fourth", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0075] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A vehicle network topology structure, characterized in that: The network topology structure includes a first network topology, a second network topology and a vehicle controller; wherein: The first network topology is connected to the vehicle controller to form a vehicle area network for realizing basic functions of the vehicle; The second network topology is used to deploy a gateway and a scene module. The gateway is used to connect the vehicle controller and the scene module to form an expansion area network. The scene module is used to realize the scene-based function of the vehicle.

2. The network topology structure according to claim 1, characterized in that: The gateway is specifically used to respond to received signals, determine a routing object according to a signal type of the signal, and route the signal to the routing object, wherein the routing object includes the vehicle controller and the scene module included in the second network topology.

3. The network topology structure according to claim 1 or 2, characterized in that: A terminal resistor is arranged between the gateway and the scene module.

4. The network topology structure according to claim 1 or 2, characterized in that: The scenario module includes at least: components involved in one or more combinations of the cockpit domain, the intelligent driving domain and the external transmission domain.

5. The network topology structure according to claim 1 or 2, characterized in that: The network topology structure completes the compilation of the communication protocol according to maximum functionality.

6. The network topology structure according to claim 1 or 2, characterized in that: The network topology structure passes the functional verification of maximum functionality, each network physical layer, link layer test, controller static current test, wake-up and sleep test.

7. The network topology structure according to claim 1 or 2, characterized in that: The network topology structure corresponds to a vehicle signal list, and the vehicle signal list includes a bodywork signal list, a modification control signal list and a low-voltage plug-in list.

8. A vehicle, characterized in that: A network topology structure comprising a vehicle body and the vehicle as claimed in any one of claims 1 to 7.

9. The vehicle according to claim 8, characterized in that The arrangement positions of the first network topology and the second network topology on the vehicle body are independent of each other.

10. The vehicle according to claim 8 or 9, characterized in that The physical layout and wiring harness plug-in reservation of the second network topology have been completed in the vehicle body.

Images