A data flow diagram for vehicle-mounted systems

Abstract

The present invention relates to a data flow graph applied to an in-vehicle system, and belongs to the field of in-vehicle network technology. The data flow graph is a collection of nodes, data flow directions, network structures, and instance definitions in the Ethernet of the in-vehicle system; the data flow graph is stored in a storage medium in the form of data and is read or modified by the in-vehicle system; there are three types of nodes, namely, active nodes, intermediate nodes, and terminal nodes, and the data of the in-vehicle system is transmitted through the nodes; the data flow direction is the direction of data transmission, which is composed of the data to be transmitted and the sender and receiver of the data; the instance is defined as a minimum computing unit, and only one instance can be run on each hardware entity, and each instance has a globally unique identifier; the network structure includes all instance definitions, as well as the network connection relationship between each instance. The present invention effectively decouples the hardware from the upper-layer application, and designs the whole vehicle software topology based on the in-vehicle network, and divides the sub-network to support the algorithm deployment in the cloud.

Description

Technical Field

[0001] The invention relates to a data flow graph applied to a vehicle-mounted system, belonging to the technical field of vehicle-mounted networks. Background Art

[0002] With the development and changes of the new generation of automotive electronic and electrical architecture and the trend of software-defined cars, the current traditional automotive software development and communication methods are difficult to adapt to the requirements of rapid iteration and development. The rapid iteration of software faces a strong binding with the hardware computing platform and the body network structure. The update and replacement of software and the increase of functions are often accompanied by changes in the body electronic and electrical architecture and the redevelopment of ECU, etc., which leads to a long development and verification cycle and high development costs. Summary of the invention

[0003] The technical problem to be solved by the present invention is: to provide a data flow diagram applied to the vehicle-mounted system to solve the application of SOA (service-oriented architecture) and software-defined cars under the new generation of vehicle-mounted electronic and electrical architecture, the support of heterogeneous computing platforms, and the support of V2X functions.

[0004] In order to solve the above technical problems, the technical solution proposed by the present invention is: a data flow graph applied to an in-vehicle system, wherein the data flow graph is a collection of nodes, data flows, network structures and instance definitions in an Ethernet network of the in-vehicle system; the data flow graph is stored in a storage medium in the form of data and is read or modified by the in-vehicle system;

[0005] The nodes are of three types: source nodes, intermediate nodes and terminal nodes. The data of the vehicle-mounted system is transmitted through the nodes, and each node can calculate and circulate the data; the source node is used to generate data, each source node only generates and outputs one piece of data, cannot input data, and the data flows into the intermediate node; the intermediate node is used to operate data, can input and output data, the number of input and output data is unlimited, and the input data can come from the source node and / or other intermediate nodes; the terminal node is used to consume data results, each terminal node has only one piece of data input, cannot output data, and the input data comes from each intermediate node; the data flow is the direction of data transmission, which is composed of the data to be transmitted and the sender and receiver of the data; the instance is defined as a minimum computing unit, the computing unit runs on a single hardware entity, only one instance can run on each hardware entity, and each instance needs to have a globally unique identifier; the network structure includes all instance definitions and the network connection relationship between each instance.

[0006] The improvement of the above technical solution is: the data flow graph is stored in a file in XML or YAML format, and the file stores nodes, data flows and instance definitions respectively; wherein the ID of the instance definition needs to be globally unique.

[0007] The improvement of the above technical solution is: the network structure includes a body network and a cloud network, and both the body network and the cloud network are connected to the Internet; the cloud network also includes a cloud server with instances deployed, and the instances on the cloud server can be used as part of a data flow graph to transmit data with nodes in the vehicle network.

[0008] The improvement of the above technical solution is that the data transmitted through Ethernet is transmitted through an upper layer protocol carried by TCP or UDP.

[0009] The beneficial effects of the present invention are: the present invention effectively decouples the hardware from the upper-level applications, and based on the vehicle network, efficiently designs the whole vehicle software topology, divides the sub-network, and supports the deployment of cloud-based algorithms; compared with the current software design ideas, it is more convenient and efficient, and the data flow can be seen intuitively; each node can automatically choose to communicate locally or through the network according to the definition of the data flow graph. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 It is a schematic diagram of a vehicle-cloud integrated architecture of a data flow diagram applied to a vehicle-mounted system based on an embodiment of the present invention.

[0011] Figure 2 It is a schematic diagram of a data flow graph node definition applied to a vehicle-mounted system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0012] Embodiment 1

[0013] A data flow graph applied to an in-vehicle system. The data flow graph is a collection of nodes, data flows, network structures, and instance definitions in the Ethernet of the in-vehicle system. The vehicle-cloud integrated architecture constructed by the data flow graph is as follows: Figure 1 The data flow graph is stored in the storage medium in the form of data and is read or modified by the vehicle system;

[0014] There are three types of nodes: source nodes, intermediate nodes, and terminal nodes. Figure 2As shown, the data of the vehicle system is transmitted through nodes, and each node can calculate and circulate the data; the source node is used to generate data, each source node only generates and outputs one piece of data, cannot input data, and the data flows into the intermediate node; the intermediate node is used to operate data, can input and output data, the number of input and output data is unlimited, and the input data can come from the source node and / or other intermediate nodes; the terminal node is used to consume data results, each terminal node has only one piece of data input, cannot output data, and the input data comes from each intermediate node; the data flow is the direction of data transmission, which is composed of the data to be transmitted and the sender and receiver of the data; the instance is defined as a minimum computing unit, the computing unit runs on a single hardware entity, only one instance can run on each hardware entity, and each instance needs to have a globally unique identifier; the network structure includes all instance definitions and the network connection relationship between instances.

[0015] The data flow graph is stored in a file in XML or YAML format, which stores nodes, data flows, and instance definitions respectively; the ID of the instance definition must be globally unique.

[0016] The network structure includes a body network and a cloud network, both of which are connected to the Internet; the cloud network also includes a cloud server with instances deployed on it, and the instances on the cloud server can be used as part of a data flow graph to transmit data with nodes in the vehicle network.

[0017] Data transmitted via Ethernet is transmitted via an upper layer protocol carried on TCP or UDP.

[0018] After the vehicle system is started, the data flow diagram is loaded from the storage medium, and the transmission mode of each data flow is determined according to the network structure and instance definition. When the sender and receiver of the data in the data flow belong to the same instance, the data transmission is carried out through the local pipeline; when the sender and receiver of the data in the data flow belong to different instances, a sending end and a receiving end are created between the two instances, and the data is transmitted through the pre-defined network structure between the instances.

[0019] Through data flow graphs, the implementation of software-defined cars can be completed from a new perspective. Each application layer node can run in the vehicle system without relying on specific hardware and network structure. The nodes automatically determine the communication method and communicate through pre-defined data flow graphs. It can adapt to the new generation of vehicle electronic and electrical architecture and is flexibly compatible with different hardware platforms and hardware architectures. When the computing hardware platform or network structure changes, the application layer nodes do not need to be changed, which greatly increases the flexibility of hardware selection and reduces development difficulty and cost.

[0020] In addition, the system can also easily integrate V2X applications, and application nodes can be flexibly deployed on the cloud server. These application nodes can communicate and work together with the application layer nodes on the vehicle side without distinction. The entire body software runs in a car-cloud integrated manner, which facilitates function expansion and OTA upgrades.

Claims

1. A data flow graph applied to a vehicle-mounted system, characterized in that: The data flow graph is a collection of nodes, data flows, network structures, and instance definitions in the Ethernet of the vehicle-mounted system; the data flow graph is stored in a storage medium in the form of data and is read or modified by the vehicle-mounted system; The nodes include three types: source nodes, intermediate nodes and terminal nodes. The data of the vehicle-mounted system is transmitted through the nodes, and each node can calculate and circulate the data; the source node is used to generate data, and each source node only generates and outputs one piece of data, and cannot input data, and the data flows into the intermediate node; the intermediate node is used to operate data, and can input and output data. The number of input and output data is not limited, and the input data can come from the source node and / or other intermediate nodes; the terminal node is used to consume data results, and each terminal node has only one piece of data input and cannot output data, and the input data comes from each intermediate node; the data flow direction is the direction of data transmission, which is composed of the data to be transmitted and the sender and receiver of the data; the instance is defined as a minimum computing unit, and the computing unit runs on a single hardware entity. Only one instance can run on each hardware entity, and each instance has a globally unique identifier; the network structure includes all instance definitions and the network connection relationship between each instance; After the vehicle system is started, the data flow diagram is loaded from the storage medium, and the transmission mode of each data flow is determined according to the network structure and instance definition. When the sender and receiver of the data in the data flow belong to the same instance, the data transmission is carried out through the local pipeline; when the sender and receiver of the data in the data flow belong to different instances, a sending end and a receiving end are created between the two instances, and the data is transmitted through the pre-defined network structure between the instances.

2. The data flow graph applied to the vehicle-mounted system according to claim 1, characterized in that: The data flow graph is stored in a file in XML or YAML format, in which nodes, data flows and instance definitions are stored respectively; the ID of the instance definition must be globally unique.

3. The data flow graph applied to the vehicle-mounted system according to claim 1, characterized in that: The network structure includes a vehicle body network and a cloud network, both of which are connected to the Internet; the cloud network also includes a cloud server with instances deployed on it, and the instances on the cloud server can be used as part of a data flow graph to transmit data with nodes in the vehicle network.

4. The data flow graph applied to the vehicle-mounted system according to claim 1, characterized in that: Data transmitted via Ethernet is transmitted via an upper layer protocol carried on TCP or UDP.

Images