Unmanned low-latency network architecture system and data transmission method

Abstract

The application belongs to the technical field of Internet of Vehicles, and discloses an unmanned low-latency network architecture system and a data transmission method. The system comprises an access network, a transmission network and a regional core network, a cloud server connected with the transmission network, a mobile terminal connected with the access network and a vehicle terminal connected with the access network; the access network is provided with an access network device, the access network device is used for receiving current transmission data, when the current transmission data comprises an unmanned request, a first network slice created is selected, data sent by the vehicle terminal is transmitted to the cloud server via the access network, the transmission network and the regional core network according to the first network slice, so that the cloud server stores the vehicle data and / or transmits the vehicle data to the mobile terminal. In the above manner, the access network device provided on the access network selects a network slice for transmission when receiving an unmanned request, reduces the data transmission latency during peak congestion, and improves the information transmission efficiency of unmanned driving.

Description

Technical Field

[0001] This invention relates to the field of vehicle networking technology, and in particular to a low-latency network architecture system and data transmission method for autonomous driving. Background Technology

[0002] In the current vehicle-to-everything (V2X) architecture, it mainly consists of three layers from high to low: the application layer, the network layer, and the data acquisition layer. The primary function of the network layer is to provide information transmission services, namely, to aggregate, analyze, process, and transmit input and output data. It typically consists of a web server and web services. GPS positioning signals and vehicle sensor signals are uploaded to the backend service center, where the server performs statistical management of the data, provides corresponding services to each vehicle, and can perform joint data analysis to establish various relationships between vehicles, between vehicles and people, and between vehicles and the backend, providing efficient, accurate, and timely data services to the user base.

[0003] 5G networks inherit the security features of 4G, offer greater mobility, and provide users with more robust service security, stricter data protection, and stronger user privacy. However, when applied to vehicle-to-everything (V2X) networks to meet the security needs of different industries, the 5G secure network architecture has the following drawbacks: High latency in the access network due to peak-hour congestion leads to low information transmission efficiency for autonomous driving. Furthermore, in traditional V2X communication, communication between the mobile terminal and the vehicle must pass through the platform, increasing latency through multiple routing steps and impacting the transmission efficiency of autonomous driving information.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this invention is to provide a low-latency network architecture system and data transmission method for autonomous driving, aiming to solve the technical problem of high latency caused by peak-hour congestion in the access network, resulting in low information transmission efficiency for autonomous driving.

[0006] To achieve the above objectives, the present invention provides a low-latency network architecture system for autonomous driving, the low-latency network architecture system for autonomous driving comprising: an access network, a transmission network and a regional core network, a cloud server connected to a transmission network, a mobile terminal connected to an access network and an in-vehicle terminal connected to an access network;

[0007] The access network is equipped with an access network device, which is used to receive currently transmitted data. When the currently transmitted data includes an autonomous driving request, the device selects a first network slice that has been created, and sends the data sent by the vehicle terminal to the cloud server via the access network, the transmission network and the regional core network according to the first network slice, so that the cloud server can store the vehicle data and / or send it to the mobile terminal.

[0008] Optionally, the network route corresponding to the first network slice includes: the vehicle terminal, the access network connected to the vehicle terminal, the transmission network corresponding to the vehicle terminal, the regional core network, the transmission network connected to the cloud server, and the cloud server.

[0009] Optionally, the access network device is further configured to, upon receiving vehicle control data from the mobile terminal, select an existing second network slice and transmit the control data to the vehicle terminal via the access network, the transmission network, and the regional core network according to the second network slice.

[0010] Optionally, the network route corresponding to the second network slice includes: the mobile terminal, the access network connected to the mobile terminal, the transmission network corresponding to the mobile terminal, the regional core network, the transmission network corresponding to the vehicle terminal, the access network connected to the vehicle terminal, and the vehicle terminal itself.

[0011] Optionally, the autonomous driving low-latency network architecture system also includes a cloud client connected to a transmission network, wherein the cloud server and the cloud client are connected through a preset cloud link;

[0012] The cloud client is used to select a target transmission path according to the current instruction type, and communicate with the cloud server or the vehicle terminal according to the target transmission path.

[0013] Optionally, the current instruction type includes query type and backup type;

[0014] Accordingly, the network route corresponding to the target transmission path includes: the cloud client, the preset cloud link, and the cloud server.

[0015] Optionally, the current instruction type includes control type and monitoring type;

[0016] Accordingly, the network route corresponding to the target transmission path includes: the cloud client, the transmission network connected to the cloud client, the regional core network, the transmission network corresponding to the vehicle terminal, the access network connected to the vehicle terminal, and the vehicle terminal itself.

[0017] Optionally, the autonomous driving low-latency network architecture system also includes multiple regional core networks set up according to different regional locations.

[0018] In addition, to achieve the above objectives, the present invention also proposes a data transmission method, which is applied to the low-latency network architecture system for autonomous driving as described above. The system includes: an access network, a transmission network and a regional core network, a cloud server connected to a transmission network, a mobile terminal connected to an access network and an in-vehicle terminal connected to an access network, wherein the access network is equipped with access network devices.

[0019] The data transmission method includes:

[0020] The access network device receives the currently transmitted data. When the currently transmitted data includes an autonomous driving request, it selects the first network slice that has been created. Based on the first network slice, it sends the data sent by the vehicle terminal to the cloud server via the access network, the transmission network, and the regional core network, so that the cloud server can store the vehicle data and / or send it to the mobile terminal.

[0021] Optionally, the network route corresponding to the first network slice includes: the vehicle terminal, the access network connected to the vehicle terminal, the transmission network corresponding to the vehicle terminal, the regional core network, the transmission network connected to the cloud server, and the cloud server.

[0022] The system proposed in this invention includes: an access network, a transmission network, and a regional core network; a cloud server connected to the transmission network; a mobile terminal connected to the access network; and an in-vehicle terminal connected to the access network. An access network device is provided on the access network. This access network device receives currently transmitted data. When the currently transmitted data includes an autonomous driving request, it selects a pre-created first network slice. Based on the first network slice, the data sent by the in-vehicle terminal is transmitted to the cloud server via the access network, transmission network, and regional core network, so that the cloud server can store the vehicle data and / or send it to the mobile terminal. Through this method, the access network device on the access network selects a network slice for transmission when receiving an autonomous driving request, reducing data transmission latency during peak congestion and improving the information transmission efficiency of autonomous driving. Attached Figure Description

[0023] Figure 1 This is a structural block diagram of the first embodiment of the low-latency network architecture system for autonomous driving of the present invention;

[0024] Figure 2 This is a structural block diagram of a second embodiment of the low-latency network architecture system for autonomous driving according to the present invention;

[0025] Figure 3This is a schematic diagram of the data flow of the low-latency network architecture system for autonomous driving according to the present invention;

[0026] Figure 4 This is a flowchart illustrating the first embodiment of the data transmission method of the present invention.

[0027] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0028] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.

[0029] This invention provides a low-latency network architecture system for autonomous driving, referring to... Figure 1 , Figure 1 This is a structural block diagram of the first embodiment of the low-latency network architecture system for autonomous driving according to the present invention.

[0030] In this embodiment, the low-latency network architecture system for autonomous driving includes: an access network 10, a transmission network 20, and a regional core network 30, a cloud server 40 connected to a transmission network 20, a mobile terminal 50 connected to an access network 10, and an in-vehicle terminal 60 connected to an access network 10.

[0031] The access network 10 is equipped with an access network device 70, which is used to receive currently transmitted data. When the currently transmitted data includes an autonomous driving request, the access network device 70 selects a first network slice that has been created, and sends the data sent by the vehicle terminal 60 to the cloud server 40 via the access network 10, the transmission network 20 and the regional core network 30 according to the first network slice, so that the cloud server 40 can store the vehicle data and / or send it to the mobile terminal 50.

[0032] Understandably, referring to Figure 1 The regional core network 30 and multiple transmission networks 20 form a star topology, with the regional core network 30 as the central node. Each transmission network 20 is directly connected to the central node to form a star network structure, and the other end of each transmission network 20 is connected to one or more access networks 10. In specific implementation, the cloud server 40 directly accesses the regional core network 30 through the transmission network 20. The base station is the interface device for terminal devices to access the vehicle network, i.e., the access network device 70. The mobile terminal 50 and the vehicle terminal 60 interact with the base station to access the vehicle network. The mobile terminal 50 is a mobile phone, tablet, or other device held by the passenger, and the vehicle terminal 60 is an OBU device installed in the vehicle.

[0033] It should be noted that the access network 10 consists of a series of transmission entities (line equipment and transmission facilities) between the service node interface and the user-network interface, providing an implementation system with transmission carrying capacity for data transmission. Access network equipment 70 refers to line equipment located in the access network 10, such as base stations, routers, multiplexers, etc.

[0034] It should be understood that the currently transmitted data is data received by the access device from mobile terminals or vehicle terminals, and can also be data transmitted to mobile terminals or vehicle terminals via the network. To ensure that the communication of autonomous vehicles is not affected by public network congestion, this embodiment pre-constructs network slices to provide independent virtual private networks. In specific implementations, optionally, a first network slice is reserved exclusively for autonomous driving information; upon receiving an autonomous driving request, the first network slice is allocated to the autonomous driving communication network. Optionally, autonomous driving requests have high priority; upon receiving an autonomous driving request, the dedicated network slice is preferentially allocated to the autonomous driving communication network. If the data received by the access device is not autonomous driving information, the data transmission method in normal mode is used.

[0035] It should be noted that when 5G networks are applied to vehicle-to-everything (V2X) networks, different application scenarios have different requirements for network mobility, security, latency, and reliability. This embodiment uses network slicing to divide a physical network into multiple virtual networks. Each virtual network caters to different application scenario needs, and the virtual networks are logically independent and do not affect each other. Network slicing is used for on-demand networking, separating multiple virtual end-to-end networks on a unified infrastructure. Each network slice is logically isolated from the access network 10, transmission network 20, and regional core network 30 to adapt to different types of applications. In the specific implementation, end-to-end network slices are created in advance according to different service requirements for easy use during subsequent data transmission.

[0036] It should be understood that this embodiment is applicable to the following two scenarios:

[0037] 1. When a passenger queries the vehicle status via mobile terminal 50, before the access network device 70 performs the network slice selection action, the cloud server 40 receives the vehicle query request from the mobile terminal 50 from the vehicle network. In response to the vehicle query request, the cloud server 40 sends a data acquisition request to the vehicle terminal 60. The vehicle terminal 60, in response to the data acquisition request, transmits the vehicle status information to the access network 10. The access network device 70 then selects a network slice and sends the data from the vehicle terminal to the cloud server 40 via the vehicle network. The cloud server 40 then sends feedback to the mobile terminal 50 that issued the vehicle query request. (See reference...) Figure 1Suppose a mobile terminal C sends a vehicle query request for vehicle V. The mobile terminal requests the vehicle status from the backend: C→B1→N_t→N_c→N_t→A; the backend performs the query, and the vehicle terminal returns the vehicle status information: A→N_t→N_c→N_t→B→V→B→N_t→N_c→N_t→A; the backend returns the vehicle status information to the mobile terminal: A→N_t→N_c→N_t→B1→C.

[0038] 2. Background monitoring of vehicle status: The cloud server 40 periodically executes vehicle status monitoring tasks, sending data acquisition requests to the vehicle terminal 60. The vehicle terminal 60 responds to the data acquisition request by transmitting vehicle status information to the access network 10. The access network device 70 selects a network slice and sends the data from the vehicle terminal to the cloud server 40 via the vehicle network. The cloud server 40 stores the received data, referring to... Figure 1 The background system queries the vehicle status information, which is returned by the vehicle terminal: A→N_t→N_c→N_t→B→V→B→N_t→N_c→N_t→A. The background system then stores the vehicle data.

[0039] It should be noted that the access network device 70 queries the first network slice containing the two endpoints based on the node identifier of the access network 10 it is connected to and the peer identifier of the data sent by the vehicle terminal 60, and transmits the data sent by the vehicle terminal 60 to the cloud server 40 through the first network slice.

[0040] Specifically, the network route corresponding to the first network slice includes: the vehicle terminal, the access network connected to the vehicle terminal, the transmission network corresponding to the vehicle terminal, the regional core network, the transmission network connected to the cloud server, and the cloud server.

[0041] It should be understood that, with reference Figure 1 Assuming cloud server A queries the vehicle status of vehicle terminal V1, the network route corresponding to the first network slice is: V1→B3→N_t→N_c→N_t→A; assuming cloud server A queries the vehicle status of vehicle terminal V, the network route corresponding to the first network slice is: V→B→N_t→N_c→N_t→A.

[0042] Furthermore, the access network device 70 is also configured to, upon receiving vehicle control data sent by the mobile terminal 50, select an existing second network slice and send the control data to the vehicle terminal 60 via the access network 10, the transmission network 20, and the regional core network 30 according to the second network slice.

[0043] It should be noted that the first network slice and the second network slice correspond to different service requirements and are used to distinguish them. In this embodiment, the second network slice is applicable to the scenario where the mobile terminal 50 controls the vehicle terminal 60. The mobile terminal 50 is connected to the access network device 70. When the mobile terminal 50 sends vehicle control data, the access network device 70 queries the second network slice containing two endpoints based on the access network 10 identifier it is connected to and the controlled end of the vehicle control data. The vehicle control data sent by the mobile terminal 50 is then transmitted to the corresponding vehicle terminal 60 through the second network slice. In specific implementation, the vehicle terminal 60 interacts with a nearby base station at regular intervals. The base station uploads the interaction information of the vehicle terminal 60 to the vehicle network, where it is stored and organized by the cloud server 40. When any access network device 70 needs to transmit vehicle control data, it interacts with the cloud server 40 to query the access network 10 node identifier corresponding to the controlled end. The access network device 70 determines the second network slice containing two endpoints based on the access network 10 identifier it is connected to and the queried access network 10 node identifier. In traditional communication methods, communication between the mobile terminal and the vehicle terminal must pass through the platform, increasing latency due to multiple routing steps. The network architecture of this embodiment enables direct communication between the mobile terminal 50 and the vehicle terminal 60, while the cloud server 40 provides backup, avoiding multiple redundant routing and not increasing the communication latency between the mobile terminal 50 and the vehicle terminal 60, thus improving the transmission efficiency of autonomous driving information.

[0044] Furthermore, the network route corresponding to the second network slice includes: the mobile terminal, the access network connected to the mobile terminal, the transmission network corresponding to the mobile terminal, the regional core network, the transmission network corresponding to the vehicle terminal, the access network connected to the vehicle terminal, and the vehicle terminal itself.

[0045] It should be understood that, with reference Figure 1 Assuming that the mobile terminal C controls the vehicle terminal V, the network route corresponding to the second network slice is: C→B1→N_t→N_c→N_t→B→V.

[0046] In the specific implementation, before the mobile terminal controls the vehicle terminal, an interaction process for selecting the vehicle needs to be performed, referring to... Figure 1 Assuming mobile terminal C1 selects vehicle V1, the mobile terminal requests vehicle selection from the backend: C1→B2→N_t→N_c→N_t→A. The backend cloud server transmits a signal to the selected vehicle: A→N_t→N_c→N_t→V1. The selected vehicle returns confirmation information to the backend cloud server: V1→B3→N_t→N_c→N_t→A. The backend server returns confirmation information to the mobile terminal: A→N_t→N_c→N_t→B2→C1.

[0047] In practice, before the mobile terminal controls the vehicle terminal, a control ownership confirmation process needs to be performed, referring to... Figure 1 Suppose that mobile terminal C requests control of vehicle V. The mobile terminal submits a control declaration to the backend cloud server: C→B1→N_t→N_c→N_t→A. The backend cloud server confirms the control to the mobile terminal and simultaneously sends the control ownership to the selected vehicle (in parallel): 1) A→N_t→N_c→N_t→B1→C; 2) A→N_t→N_c→N_t→B→V.

[0048] In its specific implementation, this embodiment includes two control methods. The first method involves the vehicle being controlled by a backend client, as described above. Figure 1 Assuming vehicle V is controlled by backend client A', the specific process of backend monitoring the vehicle is as follows: The vehicle sends a controlled status confirmation (controlled by the platform client) to the backend cloud server. The backend client receives the takeover request: V→B→N_t→N_c→N_t→A→N_t→N_c→N_t→A'. The backend client sends a takeover confirmation to the vehicle and replies to the backend server with a takeover confirmation (in parallel): 1) A'→N_t→N_c→N_t→B→V; 2) A'→N_t→N_c→N_t→A. The backend client interacts and communicates with the vehicle, and synchronously sends the interaction information to the backend cloud server for data backup (in parallel): 1) 2)A'→N_t→N_c→N_t→A; 3)V→B→N_t→N_c→N_t→A.

[0049] In practical implementation, the second control method involves a mobile terminal controlling the vehicle-mounted terminal, as described above. Figure 1 Assuming vehicle V is controlled by mobile terminal C, the specific process of the mobile terminal monitoring the vehicle is as follows: The vehicle sends a controlled status confirmation (controlled by the mobile terminal) to the backend cloud server. The passenger mobile terminal receives the takeover request: V→B→N_t→N_c→N_t→A→N_t→N_c→N_t→B1→C. The passenger mobile terminal sends a takeover confirmation to the vehicle and replies to the backend server with a takeover confirmation (in parallel): 1) C→N_t→N_c→N_t→B→V; 2) C→N_t→N_c→N_t→A. The passenger mobile terminal interacts and communicates with the vehicle, and synchronously sends the interaction information to the backend server for data backup (in parallel): 1) 2) 3) V→B→N_t→N_c→N_t→A.

[0050] Furthermore, the autonomous driving low-latency network architecture system also includes multiple regional core networks 30 set up according to different regional locations.

[0051] It should be noted that each core network serves as a central node, directly connected to each transmission network 20 to form a star network structure. Multiple regional core networks 30 are set up according to different regional locations, avoiding high latency caused by long data transmission distances. This regionalized construction of the vehicle-to-everything (V2X) network improves data transmission efficiency.

[0052] The system proposed in this embodiment includes: an access network, a transmission network, and a regional core network; a cloud server connected to a transmission network; a mobile terminal connected to an access network; and an in-vehicle terminal connected to an access network. An access network device is provided on the access network. This access network device receives currently transmitted data. When the currently transmitted data includes an autonomous driving request, it selects a pre-created first network slice. Based on the first network slice, the data sent by the in-vehicle terminal is transmitted to the cloud server via the access network, transmission network, and regional core network, so that the cloud server can store the vehicle data and / or send it to the mobile terminal. Through this method, the access network device on the access network selects a network slice for transmission when receiving an autonomous driving request, reducing data transmission latency during peak congestion and improving the information transmission efficiency of autonomous driving.

[0053] refer to Figure 2 , Figure 2 This is a structural block diagram of the second embodiment of the low-latency network architecture system for autonomous driving according to the present invention.

[0054] Based on the first embodiment described above, the low-latency network architecture system for autonomous driving in this embodiment further includes a cloud client 80 connected to a transmission network 20, and the cloud server 40 and the cloud client 80 are connected through a preset cloud link.

[0055] The cloud client 80 is used to select a target transmission path according to the current instruction type, and communicate with the cloud server 40 or the vehicle terminal 60 according to the target transmission path.

[0056] It should be understood that, with reference Figure 2 Cloud client A' connects to cloud server A in two ways. In the first way, cloud client A' accesses the transmission network, connects to the regional core network via link M, and communicates with cloud server A through the transmission network connected to the cloud server. In the second way, a pre-defined cloud link N is established between the transmission network connected to cloud client A' and the transmission network connected to cloud server A. In the specific implementation, link M is a public cloud link, and link N is a self-built cloud link. The cloud client selects different paths for transmission according to different command types, reducing multiple routing in the regional core network, distributing the link pressure on data transmission, and improving the data transmission efficiency of the cloud client.

[0057] Furthermore, the current instruction type includes query type and backup type;

[0058] Accordingly, the network route corresponding to the target transmission path includes: the cloud client 80, the preset cloud link, and the cloud server 40.

[0059] It should be noted that the interaction between cloud client 80 and the server includes cloud client 80 querying data from cloud server 40 (i.e., the current command type is query) and cloud client 80 sending data to cloud server 40 for backup (i.e., the current command type is backup). (Refer to...) Figure 2 When the current instruction type is query or backup, the cloud client and cloud server interact with each other through link N.

[0060] Furthermore, the current instruction type includes control type and monitoring type;

[0061] Accordingly, the network route corresponding to the target transmission path includes: the cloud client 80, the transmission network 20 connected to the cloud client 80, the regional core network 30, the transmission network 20 corresponding to the vehicle terminal 60, the access network 10 connected to the vehicle terminal 60, and the vehicle terminal 60 itself.

[0062] It is understandable that the interaction between the cloud client 80 and the vehicle terminal 60 includes the cloud client 80 issuing control commands to the vehicle terminal 60 under user operation (i.e., the current command type is control), and the cloud client 80 requesting vehicle status information from the vehicle terminal 60 under user operation (i.e., the current command type is monitoring). (Refer to...) Figure 2 When the current instruction type is control or monitoring, the cloud client interacts with the vehicle terminal through the transmission network, link M, regional core network, transmission network, and access network.

[0063] It should be noted that, referring to Figure 3 , Figure 3This is a schematic diagram of the data flow of the low-latency network architecture system for autonomous driving according to the present invention. This embodiment includes three data flows. The first data flow is the vehicle-side data flow. The vehicle collects vehicle status information based on its own installed sensors, stitches the image data, measures the distance between the vehicle and surrounding targets based on radar data, fuses the image data and radar data to generate video data, and makes decisions based on the fused data. On the one hand, the decision data is executed, and on the other hand, the video data and decision data are transmitted to the vehicle terminal via the vehicle Ethernet. The vehicle terminal OBU then transmits the data to the vehicle network via NR (New Radio, 5G New Radio). The second data flow is the background monitoring data flow. The vehicle manufacturer's cloud server or vehicle manufacturer's cloud client interacts with the vehicle terminal through the vehicle network to obtain the vehicle status data collected by the vehicle terminal or send control commands to the vehicle terminal. The third data flow is the mobile phone monitoring data flow. The mobile phone interacts with the vehicle terminal through the vehicle network to obtain the vehicle status data collected by the vehicle terminal or send control commands to the vehicle terminal. All data transmitted between the mobile phone and the vehicle terminal is transmitted to the vehicle manufacturer's cloud server for backup. The low-latency network architecture system for autonomous driving proposed in this embodiment can meet the remote monitoring and control requirements of autonomous driving.

[0064] In this embodiment, the low-latency network architecture system for autonomous driving also includes a cloud client connected to a transmission network. The cloud server and the cloud client are connected via a preset cloud link. The cloud client selects a target transmission path based on the current command type and communicates with the cloud server or vehicle terminal according to the target transmission path. Through this method, the cloud client selects different paths for transmission based on different command types, reducing multiple routing steps in the regional core network, alleviating the link pressure on data transmission, reducing data transmission latency for the cloud client, and improving the information transmission efficiency of autonomous driving.

[0065] Reference Figure 4 , Figure 4 This is a flowchart illustrating the first embodiment of the data transmission method of the present invention.

[0066] like Figure 4 As shown, the data transmission method proposed in this embodiment of the invention is applied to the low-latency network architecture system for autonomous driving described above. The system includes: an access network, a transmission network, and a regional core network; a cloud server connected to a transmission network; a mobile terminal connected to an access network; and an in-vehicle terminal connected to an access network. The access network is equipped with access network devices.

[0067] The data transmission method includes:

[0068] Step S10: The access network device receives the currently transmitted data. When the currently transmitted data includes an autonomous driving request, it selects the first network slice that has been created. Based on the first network slice, it sends the data sent by the vehicle terminal to the cloud server via the access network, the transmission network, and the regional core network, so that the cloud server can store the vehicle data and / or send it to the mobile terminal.

[0069] It should be understood that the above are merely illustrative examples and do not constitute any limitation on the technical solutions of the present invention. In specific applications, those skilled in the art can make settings as needed, and the present invention does not impose any restrictions on this.

[0070] The system proposed in this embodiment includes: an access network, a transmission network, and a regional core network; a cloud server connected to a transmission network; a mobile terminal connected to an access network; and an in-vehicle terminal connected to an access network. An access network device is provided on the access network. This device receives currently transmitted data. When the currently transmitted data includes an autonomous driving request, it selects a pre-created first network slice. Based on the first network slice, it sends the data sent by the in-vehicle terminal to the cloud server via the access network, transmission network, and regional core network, enabling the cloud server to store vehicle data and / or send it to the mobile terminal. Through this method, the access network device on the access network selects a network slice for transmission when receiving an autonomous driving request, reducing data transmission latency during peak congestion and improving the information transmission efficiency of autonomous driving.

[0071] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of this invention. In practical applications, those skilled in the art can select some or all of the workflow to achieve the purpose of this embodiment according to actual needs, and no restrictions are imposed here.

[0072] In addition, for technical details not described in detail in this embodiment, please refer to the low-latency network architecture system for autonomous driving provided in any embodiment of the present invention, which will not be repeated here.

[0073] Furthermore, it should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0074] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0075] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of 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 read-only memory (ROM) / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0076] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A low-latency network architecture system for autonomous driving, characterized in that, The low-latency network architecture system for autonomous driving includes: an access network, a transmission network, and multiple regional core networks set up according to different regional locations, a cloud server connected to a transmission network, a mobile terminal connected to an access network, and an in-vehicle terminal connected to an access network. The access network is equipped with access network devices, which are used to receive currently transmitted data. When the currently transmitted data includes an autonomous driving request, the access network devices query a first network slice containing two endpoints based on the access network node identifier they are connected to and the peer identifier of the data sent by the vehicle terminal. They then select the first network slice that has already been created and send the data sent by the vehicle terminal to the cloud server via the access network, the transmission network, and the regional core network according to the first network slice. This allows the cloud server to store and / or send the vehicle data to the mobile terminal. The first network slice is a pre-created end-to-end network slice. Autonomous driving requests have high priority, and when an autonomous driving request is received, the first network slice is preferentially allocated to the autonomous driving communication network.

2. The low-latency network architecture system for autonomous driving as described in claim 1, characterized in that, The network route corresponding to the first network slice includes: the vehicle terminal, the access network connected to the vehicle terminal, the transmission network corresponding to the vehicle terminal, the regional core network, the transmission network connected to the cloud server, and the cloud server.

3. The low-latency network architecture system for autonomous driving as described in claim 1, characterized in that, The access network device is further configured to, upon receiving vehicle control data from the mobile terminal, select an existing second network slice and transmit the control data to the vehicle terminal via the access network, the transmission network, and the regional core network according to the second network slice.

4. The low-latency network architecture system for autonomous driving as described in claim 3, characterized in that, The network route corresponding to the second network slice includes: the mobile terminal, the access network connected to the mobile terminal, the transmission network corresponding to the mobile terminal, the regional core network, the transmission network corresponding to the vehicle terminal, the access network connected to the vehicle terminal, and the vehicle terminal itself.

5. The low-latency network architecture system for autonomous driving as described in claim 1, characterized in that, The autonomous driving low-latency network architecture system also includes a cloud client connected to a transmission network, and the cloud server and the cloud client are connected through a preset cloud link; The cloud client is used to select a target transmission path according to the current instruction type, and communicate with the cloud server or the vehicle terminal according to the target transmission path.

6. The low-latency network architecture system for autonomous driving as described in claim 5, characterized in that, The current instruction type includes query type and backup type; Accordingly, the network route corresponding to the target transmission path includes: the cloud client, the preset cloud link, and the cloud server.

7. The low-latency network architecture system for autonomous driving as described in claim 5, characterized in that, The current instruction type includes control type and monitoring type; Accordingly, the network route corresponding to the target transmission path includes: the cloud client, the transmission network connected to the cloud client, the regional core network, the transmission network corresponding to the vehicle terminal, the access network connected to the vehicle terminal, and the vehicle terminal itself.

8. A data transmission method, characterized in that, The data transmission method is applied to the low-latency network architecture system for autonomous driving as described in any one of claims 1-7. The system includes: an access network, a transmission network, and multiple regional core networks set up according to different regional locations, a cloud server connected to a transmission network, a mobile terminal connected to an access network, and an in-vehicle terminal connected to an access network. The access network is equipped with access network devices. The data transmission method includes: The access network device receives the currently transmitted data. When the currently transmitted data includes an autonomous driving request, it queries a first network slice containing two endpoints based on the access network node identifier it is connected to and the peer identifier of the data sent by the vehicle terminal. It then selects the already created first network slice and sends the data sent by the vehicle terminal to the cloud server via the access network, the transmission network, and the regional core network according to the first network slice. This allows the cloud server to store and / or send the vehicle data to the mobile terminal. The first network slice is a pre-created end-to-end network slice. The autonomous driving request has high priority, and when an autonomous driving request is received, the first network slice is preferentially allocated to the autonomous driving communication network.

9. The data transmission method as described in claim 8, characterized in that, The network route corresponding to the first network slice includes: the vehicle terminal, the access network connected to the vehicle terminal, the transmission network corresponding to the vehicle terminal, the regional core network, the transmission network connected to the cloud server, and the cloud server.

Images