A data transmission method and apparatus, a communication device, and a storage medium

Abstract

Embodiments of the present application disclose a data transmission method and device, communication equipment and a storage medium. The method comprises: transmitting a first data packet between a terminal device and a network device, the first data packet comprising first information, the first information being used for indicating or associating with a service of an application layer; and the first information being processed by a first processing layer.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a data transmission method and device, a communication device and a storage medium. BACKGROUND

[0002] At present, whether the service is deployed at the edge network (or local park) side or not, it is a network architecture of separating network and application layer. In the end-to-end data transmission process, the double-end cross-layer conversion of the Transmission Control Protocol (TCP) / Internet Protocol (IP) / Media Access Control (MAC) multi-layer protocol stack between the network and the application layer needs to be performed, which will cause a certain processing delay. In addition, in the data transmission process between the base station and the user plane function, the General Packet Radio Service (GPRS) Tunneling Protocol for the User plane (GTP-U) protocol needs to be used for tunnel encapsulation and routing transmission based on the user plane, which will also cause a certain processing delay. Considering the implementation of subsequent industry service scenarios such as vehicle networking, such as lane positioning or other information opening and network industry collaborative interaction process, the cumulative processing delay of the above-mentioned can reach the millisecond (ms) level, which has an unnegligible impact on high-order auxiliary driving, automatic driving and other delay-sensitive services. Therefore, only by physically sinking can the cross-layer processing delay of the multi-layer protocol stack not be solved, and the demand for network industry collaborative cross-layer optimization cannot be met, and the protocol stack still has a space for further simplification. SUMMARY

[0003] To solve the existing technical problems, the embodiments of the present application provide a data transmission method, device, communication device and storage medium.

[0004] To achieve the above-mentioned purposes, the technical solutions of the embodiments of the present application are as follows:

[0005] In a first aspect, the embodiments of the present application provide a data transmission method, which comprises the following steps:

[0006] The first data packet is transmitted between the terminal device and the network device, the first data packet comprises first information, the first information is used to indicate or associate the service of the application layer, and the first information is processed by the first processing layer.

[0007] In the scheme, the first information includes a first identifier, a second identifier and a third identifier, the first identifier is used to indicate or identify a service type, the second identifier is used to indicate or identify a message type, and the third identifier is used to indicate or identify a generation time of a data packet.

[0008] In the scheme, the first information further includes a fourth identifier and a fifth identifier, the fourth identifier is used to indicate or identify a type of a network element deployed in a service to which data in a data packet is associated, and the fifth identifier is used to indicate or identify an address of a network element in which the service to which the data in the data packet is associated is located.

[0009] In the scheme, when the terminal device is a sending terminal device, before the terminal device and the network device transmit the first data packet, the method further includes:

[0010] The application layer of the terminal device sends a data packet to be transmitted, second information and first service requirement information to the first processing layer, wherein the second information at least includes a service identifier, a message type and a generation time stamp of the data packet.

[0011] The first processing layer of the terminal device encapsulates packet header information for the data packet based on the second information, matches a first quality of service flow identifier (QFI) according to the first service requirement information, and sends the data packet encapsulated with the packet header information and the first quality of service flow identifier (QFI) to the second processing layer, wherein the packet header information includes the first information.

[0012] In the scheme, the second information further includes the following information: a type of a network element deployed in a service to which data in a data packet is associated, and an address of a network element in which the service to which the data in the data packet is associated is located.

[0013] In the scheme, the terminal device and the network device transmit the first data packet, including:

[0014] The plurality of second processing layers of the terminal device sequentially process the data packet from the first processing layer to obtain the first data packet, and send the first data packet to the network device, wherein the plurality of second processing layers at least include a service data adaptation protocol (SDAP) layer, and the SDAP layer is located below the first processing layer.

[0015] In the scheme, the method further includes: the terminal device sends a first request to an access network device, the first request includes a service identifier, and the first request is used to request network element information of a service corresponding to the service identifier.

[0016] The terminal device receives a first response sent by the access network device, wherein the first response includes network element information deployed by a service corresponding to the service identifier, and the network element information includes a network element type and a network element address.

[0017] In the above solution, before the first processing layer of the terminal device encapsulates the packet header information of the first processing layer based on the second information for the data packet, the method further includes:

[0018] The terminal device obtains a first mapping relationship and a second mapping relationship, wherein the first mapping relationship includes a plurality of groups of mapping relationships between first identifiers and service identifiers, and the second mapping relationship includes a plurality of groups of mapping relationships between second identifiers and message types.

[0019] In the above solution, the first processing layer of the terminal device encapsulates the packet header information of the first processing layer based on the second information for the data packet, including:

[0020] The first processing layer of the terminal device looks up the first mapping relationship based on the service identifier, determines the first identifier corresponding to the service identifier, looks up the second mapping relationship based on the message type, determines the second identifier corresponding to the message type, and encapsulates the packet header information based on at least the first identifier, the second identifier, and the data packet generation timestamp.

[0021] In the above solution, when the terminal device is a receiving terminal device, the transmission of the first data packet between the terminal device and the network device includes:

[0022] The first processing layer of the terminal device receives the first data packet from the network device.

[0023] In the above solution, the method further includes: the first processing layer of the terminal device parses the packet header information of the first data packet to obtain first information, wherein the first information at least includes the first identifier, the second identifier, and the third identifier;

[0024] The first processing layer of the terminal device determines the service identifier, the message type, and the data packet generation timestamp based on the first information, and sends third information to the application layer, wherein the third information includes the service identifier, the message type, and the data packet generation timestamp.

[0025] In the above solution, the first information further includes a fourth identifier and a fifth identifier.

[0026] The sending of the third information to the application layer includes: the first processing layer of the terminal device sends the third information to an application layer corresponding to an application indicated or associated by the fourth identifier and the fifth identifier.

[0027] The network element type includes an access network device, a user plane function (UPF), or a multi-access edge computing (MEC).

[0028] In a second aspect, an embodiment of the present application also provides a data transmission method, which includes:

[0029] A first data packet is transmitted between a network device and a terminal device, the first data packet includes first information, the first information is used to indicate or associate a service of an application layer, and the first information is processed by a first processing layer.

[0030] In the above solution, the first information includes a first identifier, a second identifier, and a third identifier, the first identifier is used to indicate or identify a service type, the second identifier is used to indicate or identify a message type, and the third identifier is used to indicate or identify a generation time of the data packet.

[0031] In the above solution, the first information further includes a fourth identifier and a fifth identifier, the fourth identifier is used to indicate or identify a network element type of in-situ deployment of a service associated with data in the data packet, and the fifth identifier is used to indicate or identify a network element address of the service associated with the data in the data packet.

[0032] The network element type includes an access network device, a user plane function (UPF), or a multi-access edge computing (MEC).

[0033] In the above solution, when the network device is a receiving end device, the first data packet is transmitted between the network device and the terminal device, including:

[0034] The first processing layer of the network device receives the first data packet from the terminal device processed by a plurality of second processing layers, and at least the plurality of second processing layers include an SDAP layer, and the SDAP layer is located below the first processing layer.

[0035] In the above solution, the method further includes that the first processing layer of the network device analyzes packet header information of the first data packet to obtain first information, and the first information includes the first identifier, the second identifier, and the third identifier.

[0036] The first processing layer of the network device determines a service identifier, a message type, and a generation time stamp of the data packet based on the first information, and sends fourth information including the service identifier, the message type, and the generation time stamp of the data packet to the application layer.

[0037] In the scheme, the method further comprises: the first processing layer of the network device parses a fourth identifier in the packet header information of the first data packet, and in a case where the network element type indicated or identified by the fourth identifier is the same as the type of the network device, continues to parse other identifiers in the packet header information to obtain first information, the first information comprising: the first identifier, the second identifier, the third identifier, the fourth identifier, and a fifth identifier used to indicate or identify a network element address where a service associated with data in the data packet is located;

[0038] The first processing layer of the network device determines a service identifier, a message type, a data packet generation timestamp, and a network element address based on the first information, and sends fifth information comprising the service identifier, the message type, and the data packet generation timestamp to an application layer of an application corresponding to the network element type and the network element address.

[0039] In the scheme, in a case where the network element type indicated or identified by the fourth identifier is different from the type of the network device, the method further comprises:

[0040] In a case where the network element type indicated or identified by the fourth identifier is a user plane function and the network device is an access network device, the first processing layer of the access network device stops parsing the packet header information of the first data packet, and sends the first data packet to the user plane function; or,

[0041] In a case where the network element type indicated or identified by the fourth identifier is MEC and the network device is a user plane function, the first processing layer of the user plane function stops parsing the packet header information of the first data packet, and sends the first data packet to the MEC.

[0042] In the scheme, in a case where the network device is a sending end device, before the network device and a terminal device transmit the first data packet, the method further comprises:

[0043] The application layer of the network device sends a data packet to be transmitted, sixth information, and second service requirement information to the first processing layer; wherein the sixth information at least comprises a service identifier, a message type, and a data packet generation timestamp;

[0044] The first processing layer of the network device encapsulates packet header information for the data packet based on the sixth information, matches a second quality of service flow identifier (QFI) according to the second service requirement information, and sends the data packet encapsulated with the packet header information and the second quality of service flow identifier (QFI) to the second processing layer, the packet header information comprising the first information.

[0045] In the scheme, the sixth information further comprises the following information: a type of a network element in which the data in the data packet is deployed, and an address of the network element in which the service associated with the data in the data packet is located.

[0046] In the scheme, the transmission of the first data packet between the network device and the terminal device comprises:

[0047] The multiple second processing layers of the network device sequentially process the data packet from the first processing layer to obtain the first data packet, and send the first data packet to the network device; wherein the multiple second processing layers at least comprise an SDAP layer, and the SDAP layer is located below the first processing layer.

[0048] In the scheme, before the first processing layer of the network device encapsulates the packet header information for the data packet based on the sixth information, the method further comprises:

[0049] The network device obtains a third mapping relationship and a fourth mapping relationship, the third mapping relationship comprises a mapping relationship between multiple groups of first identifiers and service identifiers, and the fourth mapping relationship comprises a mapping relationship between multiple groups of second identifiers and message types.

[0050] In the scheme, the first processing layer of the network device encapsulates the packet header information for the data packet based on the sixth information, comprising:

[0051] The first processing layer of the network device looks up the third mapping relationship based on the service identifier to determine the first identifier corresponding to the service identifier, looks up the fourth mapping relationship based on the message type to determine the second identifier corresponding to the message type, and encapsulates the packet header information for the data packet based on at least the first identifier, the second identifier and a generation timestamp of the data packet.

[0052] In the scheme, the network device obtains a third mapping relationship and a fourth mapping relationship, comprising:

[0053] The network device obtains the third mapping relationship and the fourth mapping relationship through configuration; or,

[0054] The network device obtains the third mapping relationship and the fourth mapping relationship from other network devices through signaling.

[0055] In the scheme, in the case that the network device is an access network device, the method further comprises:

[0056] The access network device receives a first request sent by the terminal device, the first request comprising a service identifier, and the first request being used to request network element information of a service corresponding to the service identifier;

[0057] The access network device looks up pre-deployed network element configuration information, obtains network element information corresponding to the service identifier, and sends a first response to the terminal device, wherein the first response includes the network element information, and the network element information includes a network element type and a network element address.

[0058] In a third aspect, an embodiment of the present application further provides a data transmission device, which is applied to a terminal device, and includes: a first communication unit, configured to transmit a first data packet to a network device, wherein the first data packet includes first information, and the first information is used to indicate or associate a service of an application layer; and the first information is processed by a first processing layer.

[0059] In a fourth aspect, an embodiment of the present application further provides a data transmission device, which is applied to a network device, and includes: a second communication unit, configured to transmit a first data packet to a terminal device, wherein the first data packet includes first information, and the first information is used to indicate or associate a service of an application layer; and the first information is processed by a first processing layer.

[0060] In a fifth aspect, an embodiment of the present application further provides a computer readable storage medium, which stores a computer program, and the program is executed by a processor to implement the steps of the data transmission method in the first aspect or the second aspect.

[0061] In a sixth aspect, an embodiment of the present application further provides a communication device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the data transmission method in the first aspect or the second aspect when executing the program.

[0062] The data transmission method, device, communication device and storage medium provided by the embodiment of the present application transmit a first data packet between a terminal device and a network device, the first data packet includes first information, the first information is used to indicate or associate a service of an application layer, and the first information is processed by a first processing layer. By using the technical solution of the embodiment of the present application, a first processing layer is added in the original protocol stack, the first information used to indicate or associate a service of an application layer is encapsulated in a data packet by the first processing layer, that is, the first information is processed or encapsulated by the first processing layer, so that the service awareness identification and efficient adaptation to the upper layer application layer protocol are realized in the communication technology (CT, Communication Technology) domain without relying on the outer TCP / IP protocol stack, the data packet is directly transmitted from the application layer to the communication layer, the end-to-end protocol stack process is greatly simplified, and the data transmission efficiency is maximized. BRIEF DESCRIPTION OF DRAWINGS

[0063] Figure 1a and Figure 1b Network architecture diagram for service deployment;

[0064] Figure 2 Mapping relationship between OSI model and TCP / IP protocol stack;

[0065] Figure 3 End-to-end communication data plane overall protocol stack diagram;

[0066] Figure 4 Flowchart of data transmission method of the embodiment of the application;

[0067] Figure 5 Protocol stack in the data transmission method of the embodiment of the application;

[0068] Figure 6 Service deployment architecture and protocol stack communication flowchart in the data transmission method of the embodiment of the application;

[0069] Figure 7 Data transmission format in the data transmission method of the embodiment of the application;

[0070] Figure 8 Interaction interface between the first processing layer and the upper and lower layers in the data transmission method of the embodiment of the application;

[0071] Figure 9 Addressing implementation flowchart in the data transmission method of the embodiment of the application;

[0072] Figure 10 Flowchart of the data transmission method of the embodiment of the application Figure 2 ;

[0073] Figure 11 Interaction flowchart of the data transmission method of the embodiment of the application;

[0074] Figure 12 Interaction flowchart of the data transmission method of the embodiment of the application Figure 2 ;

[0075] Figure 13 Interaction flowchart of the data transmission method of the embodiment of the application Figure 3 ;

[0076] Figure 14 Application scenario diagram of the data transmission method of the embodiment of the application;

[0077] Figure 15 Endogenous protocol stack flowchart of an application scenario of the data transmission method of the embodiment of the application;

[0078] Figure 16 A network element connection relationship schematic diagram of an application scenario of the data transmission method of the embodiment of the application;

[0079] Figure 17 A field schematic diagram of the first identifier of the data transmission method of the embodiment of the application;

[0080] Figure 18 A message interaction schematic diagram in an application scenario of the data transmission method of the embodiment of the application;

[0081] Figure 19 An interaction flow schematic diagram of the data transmission method of the embodiment of the application Figure 4 ;

[0082] Figure 20 A packet header encapsulation process schematic diagram in the data transmission method of the embodiment of the application;

[0083] Figure 21 An interaction flow schematic diagram of the data transmission method of the embodiment of the application Figure 5 ;

[0084] Figure 22 A component structure schematic diagram one of the data transmission device of the embodiment of the application;

[0085] Figure 23 A component structure schematic diagram of the data transmission device of the embodiment of the application Figure 2 ;

[0086] Figure 24 A hardware component structure schematic diagram of the communication equipment of the embodiment of the application. DETAILED DESCRIPTION

[0087] The application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0088] The technical solution of the embodiment of the application can be applied to various communication systems, for example: a global mobile communication (GSM, Global System of Mobile communication) system, a long term evolution (LTE, Long Term Evolution) system or a 5G system, etc. Optionally, the 5G system or 5G network can also be referred to as a new radio (NR, New Radio) system or NR network.

[0089] Exemplarily, the communication system to which embodiments of the present application apply can comprise network devices and terminal devices (also referred to as terminals, communication terminals, etc.); the network devices can be devices that communicate with the terminal devices. Among them, the network devices can provide communication coverage in a certain area range, and can communicate with terminals located in the area. Optionally, the network devices can be base stations in various communication systems, for example, evolved Node Bs (eNBs) in LTE systems, or base stations (gNBs) in 5G or NR systems.

[0090] It should be understood that the devices with communication functions in the network / system in the embodiments of the present application can be referred to as communication devices. The communication devices can include network devices and terminal devices with communication functions, and the network devices and terminal devices can be the specific devices described above, which will not be described here again; the communication devices can also include other devices in the communication system, such as network controllers, mobile management entities, and other network entities, which are not limited in the embodiments of the present application.

[0091] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document is only used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the three cases of A alone, A and B together, and B alone. In addition, the character " / " in this document generally represents an "or" relationship between the front and rear associated objects.

[0092] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily limit to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0093] Before the technical solutions of the embodiments of the present application are described in detail, the background knowledge related to the embodiments of the present application is first described.

[0094] Many vertical industry applications require low-latency edge computing from 5G networks. Simultaneously, tight coupling and efficient collaboration between the network and services have become crucial means and development trends for ensuring service quality. Taking vehicle-to-everything (V2X) services, which are compatible with both wide-area and local-area scenarios, as an example, assisted driving and autonomous driving are two typical V2X scenarios with high safety requirements. They require high-real-time analysis and processing of massive amounts of perception data from roadside vehicles and equipment. Typical assisted driving services require latency of 50-100ms, while autonomous driving services require latency of less than 20ms or even less than 10ms. This is especially true for key smart intersections, where services need to be deployed locally. However, due to the wide-area mobility inherent in V2X services, achieving wide-area computing power deployment faces high construction costs.

[0095] Currently, there are two deployment methods for 5G private networks. The first method follows the traditional 5G network architecture. User data first needs to pass through the wireless base station, then be routed through the transmission network to the User Plane Function (UPF) network element, and finally reach the Internet (CT external network) after exiting the N6 interface. Service layer peer communication is achieved based on TCP / IP layer application layer protocols. This method is suitable for latency-insensitive upper-layer managed services, such as traffic flow statistics, traffic situation analysis, and safety monitoring. Figure 1a As shown. The second deployment method involves adding physical computing power on the UPF side to offload latency-sensitive services to the edge UPF / Multi-Access Edge Computing (MEC) side, such as high real-time services like collision warnings for pedestrians darting into intersections, red-light jaywalking warnings, and emergency lane changes. This achieves the offloading of hardware and software from the IP private network and local data broadcasting, such as... Figure 1b As shown.

[0096] Figure 1a The problems with the architecture shown are that it involves high business layers, many cross-network elements, long path processes, complex processing, and high latency.

[0097] Figure 1b The problem with the architecture shown is that the cost of sinking core network elements, edge computing power, and service software and hardware to the edge is high.

[0098] The common problem with both architectures is that they are traditional network architectures that separate network and application layer services, with services (OT, IT) and network (CT) physically isolated. In the Open Systems Interconnection (OSI) seven-layer model, CT belongs to the physical layer, while upper-layer services belong to the application layer. Furthermore, multiple layers of protocol adaptation and conversion are required between the network and applications, such as TCP / IP / MAC layers. Figure 2As shown in the figure. The OSI model strictly adheres to the Internet design idea of "high cohesion and low coupling", and each layer in the OSI seven-layer model only focuses on the implementation of the layer, and only provides a standard interface upwards, which does not require the implementation of other layers, and each performs its own function.

[0099] Figure 3 The figure shows the whole protocol stack of the end-to-end communication data plane. As shown in the figure, the data packet from the application layer of the user equipment (UE, User Equipment) to the application layer of the opposite end, in addition to the protocol processing process inside the communication network element such as the base station and the UPF, the mutual process with the application layer and the interface transmission process from the base station to the UPF also involve two additional stack conversion outside: Figure 3

[0100] Conversion 1: From the generation of the data packet of the application layer (Application-layer) of the UE to the reception of the data packet of the application layer (Application-layer) of the opposite end, the network element and the application layer need to be converted through the double-end cross-layer conversion of the TCP / IP / MAC multi-layer protocol stack, and the port (port), IP address and MAC address description of the source end and the destination end are added and removed respectively. Specifically, in the TCP layer, the TCP header is added, which mainly describes the source port and the destination port. The port corresponds to the process or application program, so the computer needs to be parsed. The receiving host can be used to guide the corresponding application program after receiving. In the IP layer, the IP header is added to form a data packet, and the source IP and the destination IP are marked. In the MAC layer, the MAC header is added to form a data frame, and the source MAC address and the target MAC address are described. Among them, the main function of the IP address and the MAC address is to route and address the data packet, and the TCP / IP has a 3-way handshake and a slow start mechanism, which introduces a certain processing delay (denoted as t1);

[0101] Conversion 2: In the transmission process of the data packet from the base station to the UPF network element through the N3 interface, tunnel encapsulation and routing transmission based on the GTP-U protocol are needed, so the double-end protocol processing and conversion of the user datagram protocol (UDP, User Datagram Protocol) / IP and GTP-U are needed, and a certain processing delay (denoted as t2) is introduced.

[0102] Considering the implementation of subsequent vehicle networking and other industry business scenarios such as lane positioning or other information opening and network industry collaborative interaction process, the cumulative delay of t1+t2 can reach ms level, which brings an unavoidable impact on delay-sensitive businesses such as high-order auxiliary driving and automatic driving. Therefore, only by physically sinking can the cross-layer processing delay of the multi-layer protocol stack and the demand for network industry collaborative cross-layer optimization cannot be solved, and the protocol stack has further simplification space.

[0103] Based on this, the following embodiments of the present application are proposed.​

[0104] The embodiment of the present application provides a data transmission method. Figure 4 As shown in Figure 1, the method comprises the following steps. Figure 4

[0105] Step 101: transmitting a first data packet between a terminal device and a network device, wherein the first data packet comprises first information, the first information is used for indicating or associating a service of an application layer, and the first information is processed by a first processing layer.

[0106] In the embodiment, the first data packet transmitted between the terminal device and the network device carries the first information, the first information is used for indicating or associating the service of the application layer, so as to realize service sensing identification through the first information. In the embodiment, a first processing layer is added under the condition of an original 5G RAN protocol stack, to replace a traditional TCP / IP / MAC layer, as shown in Figure 2. Figure 5 The first processing layer is located below an application layer (Application) and above an SDAP. The first information used for indicating or associating the service of the application layer is encapsulated in the data packet through the first processing layer, that is, the first information is processed or encapsulated through the first processing layer, so that service sensing identification and efficient adaptation to an upper application layer protocol are realized in a CT domain without relying on an outer TCP / IP protocol stack, data packets are directly transmitted from the application layer to a communication layer, an end-to-end protocol stack process is greatly simplified, and data transmission efficiency is maximized.

[0107] In some optional embodiments, the first processing layer can also be referred to as a service layer, a service sensing layer (ASP, Application Sensation Protocol) and the like, and the main functions of the first processing layer can include the following.

[0108] 1. Adding the first information in the data packet, realizing indication and association of a specific service of the application layer, and efficiently connecting a communication protocol stack and a protocol link of an upper application layer.

[0109] 2. Realizing intelligent sensing identification of service requirements, establishing mapping of the service to a QoS flow (QoS flow) according to content in the first information, and dynamically matching network capability.

[0110] ​Considering the difference of delay requirement of different industry applications and the deployment flexibility, the function of the first processing layer can be extended to synchronous upgrade of the UPF protocol stack and the local MEC protocol stack to support flexible independent deployment and even distributed deployment of services in the base station network element (option 1), the UPF network element (option 2), and the MEC (option 3). As shown in Figure 6 The endogenous application can be deployed in the access network device, the user plane function (UPF) network element, the MEC, and the like. The communication + endogenous sensing + local computing fusion architecture is realized for the industry scene such as the Internet of Vehicles, the software and hardware are integrated, the performance and the cost are considered, and the cost performance is maximized.

[0111] In the option 1 scenario, the protocol stack path is the shortest, which can replace the TCP / IP / MAC double-end protocol conversion and the protocol encapsulation of UDP / IP and GTP-U across the UPF network element as shown in Figure 3 The delay is maximally reduced.

[0112] In the embodiment, the processing of the first information by the first processing layer at least includes encapsulation (or addition) and / or decapsulation (or parsing) processing, and the like. The first data packet is transmitted between the network device and the terminal device. On the one hand, the terminal device can be used as a sending terminal device, and the network device is used as a receiving terminal device. The first processing layer of the terminal device adds the first information in the data packet or encapsulates the first information in the packet header of the data packet. Correspondingly, after receiving the data packet, the network device parses the data packet through the first processing layer to obtain the first information, or performs decapsulation on the packet header of the data packet to obtain the first information. On the other hand, the network device can be used as a sending terminal device, and the terminal device is used as a receiving terminal device. The first processing layer of the network device adds the first information in the data packet or encapsulates the first information in the packet header of the data packet. Correspondingly, after receiving the data packet, the terminal device parses the data packet through the first processing layer to obtain the first information, or performs decapsulation on the packet header of the data packet to obtain the first information. Optionally, the packet header containing the first information can be referred to as the packet header of the first processing layer or the ASP packet header.

[0113] In some optional embodiments of the application, the first information includes a first identifier, a second identifier, and a third identifier. The first identifier is used to indicate or identify a service type, the second identifier is used to indicate or identify a message type, and the third identifier is used to indicate or identify the generation time of the data packet.

[0114] In the embodiment, the first identifier is used to indicate or identify the service type; for example, the first identifier can be a service identifier (AID, Application ID), which can indicate different service types, such as industrial programmable logic controller (PLC, Programmable Logic Controller) control, machine vision detection, vehicle networking blind area warning, emergency lane change, pedestrian collision detection, etc. In actual application, the first identifier can be carried by a first field, and the bit length of the first field is variable and extensible, such as 1-2 bytes, which can be customized as needed according to the deployment of the service.

[0115] The second identifier is used to indicate or identify the message type; for example, the second identifier can be a message type identifier, such as Message Type (MT), which can indicate different message types, such as industrial control signaling messages, heartbeat packet messages, video stream messages, vehicle networking road condition perception messages, vehicle state messages, etc. In actual application, the second identifier can be carried by a second field, and the bit length of the second field is variable and extensible.

[0116] The third identifier is used to indicate or identify the generation time of the data packet; for example, the third identifier can be a timestamp identifier, such as Time Mark (TM), which can indicate the time of generating the service message. For example, in a vehicle networking scenario, it can support time synchronization between heterogeneous sensing devices such as cameras, radars, vehicle OBUs, and RSUs in the message fusion process at the application layer, and can also support solving the end-to-end delay statistics problem in existing 5G vehicle networking communication. In actual application, the third identifier can be carried by a third field, and the bit length of the third field is variable and extensible.

[0117] In the embodiment, by adding the first information including the first identifier (indicating or identifying the service type), the second identifier (indicating or identifying the message type), and the third identifier in the data packet, the application layer service is indicated and associated, and the mapping between the service and the QoS flow (QoS flow) is established, so that the efficient flow of the data packet from the application layer to the communication network domain can be quickly established, replacing the original TCP / IP / MAC layer protocol process and the original IP and port identification method for the service, and realizing the "one-hop direct" from the application layer to the communication layer.

[0118] In some optional embodiments, the first information further includes a fourth identifier and a fifth identifier, the fourth identifier is used to indicate or identify the type of network element deployed in the service of the data in the data packet; and the fifth identifier is used to indicate or identify the address of the network element where the service of the data in the data packet is located.

[0119] In some optional embodiments, the network element type includes: an access network device, a UPF, or a MEC. Optionally, the access network device can be a base station or a gNB.

[0120] In this embodiment, the first information can further include a fourth identifier and a fifth identifier. The fourth identifier is used to indicate or identify the network element type of the in-service deployment of the data associated with the data in the data packet. For example, the fourth identifier can be a network element type indication identifier, such as a node type indicator (NTI), which can define the in-service deployment of the service on which network element type of gNB / UPF / MEC. In actual application, the fourth identifier can be carried by a fourth field. For example, for the network element type of the in-service deployment of the service at present, the bit length of the fourth field is 2 bits, and the 2-bit flag of the fourth identifier can be:

[0121] 1. flag = 00, indicating that the associated network element type is a base station, corresponding to an option 1 deployment architecture;

[0122] 2. flag = 01, indicating that the associated network element type is a UPF, corresponding to an option 2 deployment architecture;

[0123] 3. flag = 10, indicating that the associated network element type is a local MEC, corresponding to an option 3 deployment architecture.

[0124] It should be noted that the bit length of the fourth field in the embodiment of the application is not limited to 2 bits. In future communication systems, the network element type of the in-service deployment of the service can be increased, and the bit length of the fourth field can also be increased. This embodiment does not limit this.

[0125] The fifth identifier is used to indicate or identify the network element address of the service associated with the data in the data packet. For example, the fifth identifier can be a network element address identifier, such as a node address (NA), which can define the specific address of the network element where the service is located, i.e., the specific address of a certain gNB / UPF / MEC where the service is located. In actual application, the fifth identifier can be carried by a fifth field. Since the MEC-UPF-gNB is a one-to-many connection relationship, the specific byte and bit size can be configured according to the number of network elements.

[0126] Based on this, referring to Figure 7As shown, the first processing layer in the embodiment of the present application includes a first field (corresponding to field 3), a second field (corresponding to field 4), a third field (corresponding to field 5), a fourth field (corresponding to field 1), a fifth field (corresponding to field 2) and a sixth field (corresponding to field 6) in the packet header (or ASP packet header), wherein the first field (corresponding to field 3), the second field (corresponding to field 4) and the third field (corresponding to field 5) are respectively used to encapsulate the first identifier (such as AID), the second identifier (such as MT) and the third identifier (such as TM) in the first information, and the fourth field (corresponding to field 1), the fifth field (corresponding to field 2) and the sixth field (corresponding to field 6) are all optional fields; wherein the optional field means that the first processing layer includes the above-mentioned optional field in the packet header (or ASP packet header), but the corresponding identifier or information can be added or not added in the optional field, for example, in some scenarios, the fourth identifier and the fifth identifier are not included in the first information, then the fourth field (corresponding to field 1) and the fifth field (corresponding to field 2) are empty as shown. The sixth field (corresponding to field 6) is an extension field or a reserved field. Figure 7

[0127] In some optional embodiments of the present application, when the terminal device is a sending terminal device, before the terminal device and the network device transmit the first data packet, the method further includes: the application layer of the terminal device sends the data packet to be transmitted, the second information and the first service requirement information to the first processing layer; wherein the second information at least includes the service identifier, the message type and the timestamp of the data packet; the first processing layer of the terminal device encapsulates the packet header information for the data packet based on the second information, matches the first quality of service flow identifier (QFI, Quality of Service Flow ID) according to the first service requirement information, and sends the data packet encapsulated with the packet header information and the first QFI to the second processing layer, wherein the packet header information includes the first information.

[0128] In some optional embodiments, the terminal device and the network device transmit the first data packet, including: a plurality of second processing layers of the terminal device sequentially process the data packet from the first processing layer to obtain the first data packet, and send the first data packet to the network device; wherein the plurality of second processing layers at least includes a service data adaptation protocol (SDAP, Service Data Adaptation Protocol) layer, and the SDAP layer is located below the first processing layer.

[0129] Figure 8 The figure is a schematic diagram of the interaction interface between the first processing layer and the upper and lower layers in the data transmission method of the embodiment of the present application; as​Figure 8 As shown, for the sending end device, the first processing layer (or ASP layer) and the application layer (Application) exchange information through the (1)-a interface, and the first processing layer (or ASP layer) and the SDAP layer exchange information through the (2)-a interface. For the receiving end device, the first processing layer (or ASP layer) and the application layer (Application) exchange information through the (1)-b interface, and the first processing layer (or ASP layer) and the SDAP layer exchange information through the (2)-b interface.

[0130] Specifically, the content transmitted between the application layer and the first processing layer (or ASP layer) of the sending end device through the (1)-a interface can include service identification, message type, timestamp, network element type (optional information), network element address (optional information), service requirement information (optional information), and data (data). The service requirement information includes but is not limited to: delay, rate bandwidth, packet loss rate, and other index requirements. The content transmitted between the first processing layer (or ASP layer) and the SDAP layer of the sending end device through the (2)-a interface can include a complete data packet containing the packet header information of the first processing layer (such as the ASP layer) and the QFI (such as the first QFI) of service mapping.

[0131] In this embodiment, the first processing layer is located below the application layer and above the SDAP layer. When the terminal device is a sending end device, the application layer of the terminal device sends the data packet to be transmitted, the second information, and the first service requirement information to the first processing layer. The first service requirement information includes but is not limited to: delay, rate bandwidth, packet loss rate, and other index requirements. The second information at least includes the service identification, message type, and timestamp provided by the application layer; in some optional embodiments, the second information further includes the following information: the network element type of the in-situ deployment of the service associated with the data in the data packet, and the network element address of the service associated with the data in the data packet. Further, the first processing layer of the terminal device encapsulates the packet header information of the first processing layer for the data packet according to the second information received from the application layer, including marking the first identification, the second identification, and the third identification; if the network element type and the network element address are also included in the second information, the fourth identification and the fifth identification are marked. On the other hand, the QoS flow has been configured with the corresponding QFI file according to different delay, reliability, scheduling priority, and other indexes by the core network, so that the first processing layer of the terminal device can map the data packet to the first QFI matched therewith according to the obtained first service requirement information, and then send the data packet encapsulated with the packet header information of the first processing layer and the first QFI to the SDAP. Then, after being sequentially processed layer by layer through the existing protocol stack, the first data packet is sent to the network device.

[0132] In the embodiment, the obtaining manner of the service deployment address can include static and dynamic manners. Therefore, the fourth identifier and the fifth identifier are optional information in the first information.

[0133] As an implementation, the method further includes: the terminal device sends a first request to the access network device, the first request including a service identifier, the first request being used to request network element information of a service corresponding to the service identifier; and the terminal device receives a first response sent by the access network device, the first response including the network element information of the service corresponding to the service identifier, the network element information including a network element type and a network element address.

[0134] Figure 9 An addressing implementation flowchart in the data transmission method of the embodiment is shown in FIG. 1. Figure 9 As shown in FIG. 1, the addressing process can include:

[0135] Step 201: The UE sends a first request to the gNB, the first request including a service identifier.

[0136] Step 202: The gNB finds an address corresponding to the service identifier through a related configuration file, and sends a first response to the UE, the first response including a network element type and a network element address of a network element where the service is located.

[0137] In the embodiment, the location of service deployment includes three cases of an access network device, a UPF, and a MEC, and the access network device is the lowest network element. Therefore, in the static addressing manner, an addressing agent (Agent) is deployed or set by default at the access network device (gNB) side, and related configuration files of network element information (which can include a network element type and a network element address) of the service are synchronized to the access network device agent (Agent) in advance. Then, the UE can initiate a session of a first processing layer, and send a first request, i.e., an addressing request (Adress Request), to the access network device, the request carrying a service identifier (service ID). The access network device finds network element information corresponding to the service ID through a related configuration file of the agent (Agent), for example, including a network element type and a network element address, and informs the UE of the network element type and the network element address of the network element where the service is located through a first response, wherein the first response is an addressing response (Adress Response).

[0138] In the above static address obtaining manner, the terminal device has obtained the network element type and the network element address from the access network device, and therefore, fourth fields and fifth fields for filling the fourth identifier and the fifth identifier in the header information of the packet encapsulated by the terminal device as the sending terminal device are empty. Correspondingly, the network element type and the network element address are not included in the second information sent by the application layer of the terminal device to the first processing layer.

[0139] As another implementation, the terminal device can also provide dynamic addressing through dynamic addressing, through the manner of carrying in the packet header information of the first processing layer. Specifically, the application layer of the terminal device as the sending terminal device sends second information to the first processing layer, the second information including the type of the network element in which the data in the data packet is associated with the service and the address of the network element in which the data in the data packet is associated with the service; the first processing layer of the terminal device identifies the type of the network element and the address of the network element in the packet header information, that is, adds the fourth identifier and the fifth identifier; the receiving terminal device (such as a network device) receives the data packet and parses the packet header information to obtain the type of the network element and the address of the network element. In the above manner of obtaining dynamic address, the fourth field and the fifth field of the packet header information of the first processing layer are filled in actual.

[0140] In some optional embodiments of the present application, before the first processing layer of the terminal device encapsulates the packet header information of the first processing layer for the data packet based on the second information, the method further includes: the terminal device obtains a first mapping relationship and a second mapping relationship; wherein the first mapping relationship includes a plurality of groups of mapping relationship between the first identifier and the service identifier, and the second mapping relationship includes a plurality of groups of mapping relationship between the second identifier and the message type.

[0141] In the present embodiment, the terminal device as the sending terminal device maintains the first mapping relationship and the second mapping relationship in advance before sending the data packet. The first mapping relationship can also be referred to as a first mapping table, which defines a plurality of groups of mapping relationship between the first identifier and the service identifier; the second mapping relationship can also be referred to as a second mapping table, which defines a plurality of groups of mapping relationship between the second identifier and the message type.

[0142] In some optional embodiments, the first processing layer of the terminal device encapsulates the packet header information of the first processing layer for the data packet based on the second information, including: the first processing layer of the terminal device determines the first identifier corresponding to the service identifier based on the service identifier by searching the first mapping relationship, and determines the second identifier corresponding to the message type based on the message type by searching the second mapping relationship, and encapsulates the packet header information for the data packet based on at least the first identifier, the second identifier and the generation timestamp of the data packet.

[0143] In this embodiment, after receiving the second information sent by the application layer, the first processing layer of the terminal device, acting as the sending end device, obtains the first identifier corresponding to the service identifier of the data packet by querying a pre-maintained first mapping relationship, and obtains the second identifier corresponding to the message type of the data packet by querying a pre-maintained second mapping relationship. The first processing layer then encapsulates the header information of the data packet based on the first identifier, the second identifier, and the timestamp (marked with a third identifier). If the second information also includes a network element type and a network element address, the first processing layer marks a fourth identifier based on the network element type, marks a fifth identifier based on the network element address, and encapsulates the header information of the data packet based on the first identifier, the second identifier, the timestamp (marked with a third identifier), the fourth identifier, and the fifth identifier.

[0144] In some optional embodiments of the present invention, when the terminal device is a receiving device, the transmission of a first data packet between the terminal device and the network device includes: the first processing layer of the terminal device receiving the first data packet from the network device.

[0145] In this embodiment, refer to Figure 8 As shown, the content transmitted between the first processing layer (or ASP layer) of the receiving device and the SDAP layer through the (2)-b interface is SDAP data packets. The receiving device parses the received SDAP data packets to obtain the first information in the packet header information, such as the first identifier, the second identifier, and the third identifier. The content transmitted between the first processing layer (or ASP layer) of the receiving device and the application layer through the (1)-b interface may include: service identifier, message type, timestamp, and data. In this embodiment, the first processing layer of the terminal device, which is the receiving device, receives the first data packet from the network device, which has been processed by multiple second processing layers. Specifically, the data packet from the network device is processed by the original protocol stack and arrives at the SDAP layer, which then sends it to the first processing layer (or ASP layer) through the interface. Here, the data packet sent by the SDAP layer to the first processing layer (or ASP layer) is called the first data packet.

[0146] In some optional embodiments, the method further includes: the first processing layer of the terminal device parses the header information of the first data packet to obtain first information, the first information including at least the first identifier, the second identifier, and the third identifier; the first processing layer of the terminal device determines the service identifier, message type, and data packet generation timestamp based on the first information, and sends third information to the application layer, the third information including the service identifier, message type, and data packet generation timestamp.

[0147] In this embodiment, the first processing layer of the terminal device as the receiving end device analyzes (or unpacks) the packet header information of the first data packet to obtain first information in the packet header of the first processing layer (or the ASP layer); wherein the first information at least includes the first identifier, the second identifier and the third identifier. Further, the first processing layer can determine the corresponding service identifier according to the first identifier, specifically can find the service identifier corresponding to the first identifier according to the pre-maintained first mapping relationship; and determine the message type corresponding to the second identifier, specifically can find the message type corresponding to the second identifier according to the pre-maintained second mapping relationship; determine the corresponding timestamp according to the third identifier, and then the first processing layer sends the third information to the application layer, wherein the third information includes the service identifier, the message type and the timestamp of the data packet.

[0148] In some optional embodiments, the first information further includes a fourth identifier and a fifth identifier; and the sending of the third information to the application layer includes: the first processing layer of the terminal device sending the third information to the application layer corresponding to the application indicated or associated by the fourth identifier and the fifth identifier.

[0149] In this embodiment, if the network side adopts a dynamic addressing mode, the first information obtained by the first processing layer of the terminal device can further include a fourth identifier and a fifth identifier; then the first processing layer of the terminal device can determine the network element type according to the fourth identifier, determine the network element address according to the fifth identifier, determine the service APP based on the network element type and the network element address, and then the first processing layer of the terminal device sends the third information to the application layer of the APP.

[0150] Based on the above embodiments, the embodiment of the present application further provides a data transmission method. Figure 10 The flow of the data transmission method of the embodiment of the present application is shown in Figure 2 ; as Figure 10 shown, the method comprises:

[0151] Step 301: transmitting a first data packet between a network device and a terminal device, wherein the first data packet includes first information, and the first information is used for indicating or associating a service of an application layer; and the first information is processed by a first processing layer.

[0152] In this embodiment, the first data packet transmitted between the network device and the terminal device carries the first information, and the first information is used for indicating or associating the service of the application layer, so as to realize service sensing identification through the first information. In this embodiment, a first processing layer is added in the case of the original protocol stack, as Figure 5As shown, the first processing layer is located below the application layer (Application) and above the SDAP; the first processing layer encapsulates the first information in the data packet for indicating or associating the service of the application layer, i.e., the first information is processed or encapsulated by the first processing layer, so that the service awareness and efficient adaptation to the upper application layer protocol are realized in the CT domain without relying on the outer TCP / IP protocol stack, the data packet is directly transmitted from the application layer to the communication layer, the end-to-end protocol stack process is greatly simplified, and the data transmission efficiency is maximized.

[0153] In some optional embodiments, the first processing layer can also be referred to as a service layer, a service awareness layer (ASP, Application Sensation Protocol), etc., and its main functions can include:

[0154] 1. Adding the first information in the data packet to indicate and associate the specific service of the application layer, and efficiently connecting the communication protocol stack and the protocol link of the upper application layer.

[0155] 2. Realizing intelligent service awareness, establishing the mapping of the service to the QoS flow according to the content in the first information, and dynamically matching the network capability.

[0156] Considering the difference in the delay requirement of different industry applications and the deployment flexibility, the function of the first processing layer can be extended to the synchronous upgrade of the UPF protocol stack and the local MEC protocol stack to support the service in the base station network element (option 1), the UPF network element (option 2), and the MEC (option 3) to realize flexible independent deployment or even distributed deployment. Figure 6 As shown, the endogenous application can be deployed in the access network device, the user plane function (UPF) network element, the MEC, etc. The communication + endogenous awareness + local computing fusion architecture is realized for the industry scene such as the Internet of Vehicles, the software and hardware are integrated, the performance and cost are considered, and the cost performance is maximized.

[0157] In the embodiment, the processing of the first information by the first processing layer at least includes encapsulation (or addition) and / or decapsulation (or parsing) processing, etc. The first data packet is transmitted between the network device and the terminal device. On one hand, the terminal device can be a sending terminal device, and the network device can be a receiving terminal device. The first processing layer of the terminal device adds the first information in the data packet or encapsulates the first information in the packet header of the data packet. Correspondingly, the network device receives the data packet, parses the data packet by the first processing layer, obtains the first information, or decapsulates the packet header of the data packet to obtain the first information. On the other hand, the network device can be a sending terminal device, and the terminal device can be a receiving terminal device. The first processing layer of the network device adds the first information in the data packet or encapsulates the first information in the packet header of the data packet. Correspondingly, the terminal device receives the data packet, parses the data packet by the first processing layer, obtains the first information, or decapsulates the packet header of the data packet to obtain the first information. Optionally, the packet header containing the first information can be referred to as the packet header of the first processing layer or the ASP packet header.

[0158] In some optional embodiments of the present application, the first information includes a first identifier, a second identifier and a third identifier. The first identifier is used to indicate or identify a service type. The second identifier is used to indicate or identify a message type. The third identifier is used to indicate or identify a generation time of the data packet.

[0159] In some optional embodiments, the first information further includes a fourth identifier and a fifth identifier. The fourth identifier is used to indicate or identify a network element type of in-service deployment associated with data in the data packet. The fifth identifier is used to indicate or identify a network element address where the service associated with the data in the data packet is located.

[0160] In the embodiment, the specific description of each identifier carried by the first information can be referred to the description in the foregoing embodiments, which will not be described here.

[0161] In some optional embodiments, the network element type includes an access network device, a UPF or a MEC. Optionally, the access network device can be a base station or a gNB.

[0162] In some optional embodiments of the present application, when the network device is a receiving terminal device, the first data packet is transmitted between the network device and the terminal device, including: the first processing layer of the network device receives the first data packet from the terminal device processed by a plurality of second processing layers; wherein the plurality of second processing layers at least include an SDAP layer, and the SDAP layer is located below the first processing layer.

[0163] In the embodiment, the specific description of each identifier carried by the first information can be referred to the description in the foregoing embodiments, which will not be described here. Figure 8As shown, the content transmitted between the first processing layer (or ASP layer) of the receiving end device and the SDAP layer through the (2)-b interface is an SDAP data packet. The receiving end device parses the received SDAP data packet to obtain the first information in the packet header information, for example, including the first identifier, the second identifier and the third identifier. The content transmitted between the first processing layer (or ASP layer) of the receiving end device and the application layer through the (1)-b interface can include the service identifier, the message type, the timestamp and the data (data). In this embodiment, the first processing layer of the network device as the receiving end device receives the first data packet from the terminal device and processed by the plurality of second processing layers. Specifically, the data packet from the terminal device reaches the SDAP layer through the processing of the original protocol stack, and is sent to the first processing layer (or ASP layer) by the SDAP layer through the interface. Here, the data packet sent by the SDAP layer to the first processing layer (or ASP layer) is referred to as the first data packet.

[0164] In some optional embodiments, the method further includes: the first processing layer of the network device parses the packet header information of the first data packet to obtain the first information, the first information including the first identifier, the second identifier and the third identifier; the first processing layer of the network device determines the service identifier, the message type and the timestamp of the data packet based on the first information, and sends the fourth information including the service identifier, the message type and the timestamp of the data packet to the application layer.

[0165] This embodiment mainly aims at the first static addressing mode in the above-mentioned embodiments. Since the network element address is obtained by a static mode, the fourth field and the fifth field in the packet header information are empty, i.e., the fourth identifier and the fifth identifier are not included in the first information. Therefore, the first processing layer of the network device directly parses each field in the packet header information to obtain the first identifier, the second identifier and the third identifier.

[0166] In this embodiment, the first processing layer of the network device as the receiving end device parses (or unpacks) the packet header information of the first data packet to obtain the first information in the packet header of the first processing layer (or ASP layer). The first information at least includes the first identifier, the second identifier and the third identifier. Further, the first processing layer can determine the corresponding service identifier according to the first identifier, specifically, can find the service identifier corresponding to the first identifier according to the pre-maintained third mapping relationship; and determine the message type corresponding to the second identifier, specifically, can find the message type corresponding to the second identifier according to the pre-maintained fourth mapping relationship; and determine the corresponding timestamp according to the third identifier. Then, the first processing layer sends the fourth information including the service identifier, the message type and the timestamp of the data packet to the application layer.

[0167] In some optional embodiments of the present application, the method further comprises: the first processing layer of the network device parsing a fourth identifier in the packet header information of the first data packet, in the case that the network element type indicated or identified by the fourth identifier is the same as the type of the network device, continuing to parse other identifiers in the packet header information to obtain first information, the first information comprising: the first identifier, the second identifier, the third identifier, the fourth identifier and a fifth identifier used to indicate or identify a network element address where the data associated with the service in the data packet is located; the first processing layer of the network device determining the service identifier, the message type, the generation timestamp of the data packet and the network element address based on the first information, and sending fifth information comprising the service identifier, the message type and the generation timestamp of the data packet to the application layer of the application corresponding to the network element type and the network element address.

[0168] The present embodiment is mainly directed to the second dynamic addressing mode in the above-mentioned embodiments. Since the network element address is obtained in a dynamic manner, the fourth field and the fifth field in the packet header information are both added with the fourth identifier and the fifth identifier in actuality, i.e. the fourth identifier and the fifth identifier are included in the first information.

[0169] The first processing layer of the network device receives the first data packet, and parses the fourth identifier (or the fourth field) in the header information in the first data packet to obtain the fourth identifier, that is, to obtain the network element type indicated or identified by the fourth identifier. In the embodiment of the application, the network element type includes an access network device, a UPF or a MEC, that is, the service can be endogenously deployed in the access network device (such as a gNB), the UPF or the MEC, and then the network device as the receiving end device can be the access network device (such as a gNB), the UPF or the MEC, and the service can be deployed in other network devices. For example, the access network device receives the first data packet, and determines, by parsing the fourth identifier, that the network element type indicated or identified by the fourth identifier is also the access network device, which indicates that the type of the network device is the same. If the fourth identifier is parsed to determine that the network element type indicated or identified by the fourth identifier is the UPF or the MEC, it indicates that the type of the network device is different. In the embodiment, in the case where the network element type indicated or identified by the fourth identifier is the same as the type of the network device, the first processing layer (such as the ASP layer) of the network device continues to parse other identifiers in the header information to obtain first information, and the first information includes the first identifier, the second identifier, the third identifier, the fourth identifier and a fifth identifier used to indicate or identify the network element address of the service in which the data in the data packet is associated. Further, the first processing layer (such as the ASP layer) of the network device can determine the corresponding service identifier according to the first identifier, specifically can determine the corresponding service identifier according to the third mapping relationship maintained in advance; and determine the message type corresponding to the second identifier, specifically can determine the message type corresponding to the second identifier according to the fourth mapping relationship maintained in advance; determine the corresponding timestamp according to the third identifier; determine the corresponding network element address according to the fourth identifier; and then the first processing layer sends fifth information to the application layer of the application (APP) corresponding to the network element type and the network element address, and the fifth information includes the service identifier, the message type and the timestamp of the generation of the data packet.

[0170] In some optional embodiments, in the case where the network element type indicated or identified by the fourth identifier is different from the type of the network device, the method further includes: when the network element type indicated or identified by the fourth identifier is the user plane function and the network device is the access network device, the first processing layer of the access network device stops parsing the header information of the first data packet, and sends the first data packet to the user plane function; or when the network element type indicated or identified by the fourth identifier is the MEC and the network device is the user plane function, the first processing layer of the user plane function stops parsing the header information of the first data packet, and sends the first data packet to the MEC.

[0171] In the embodiment, in the case that the fourth identifier indicates or identifies a network element type different from the type of the network device, it indicates that the service corresponding to the first data packet is not deployed in the network device currently serving as the receiving end device, and the network device needs to stop parsing the packet header information of the first data packet and further forward the first data packet, for example, in the case that the fourth identifier indicates or identifies a network element type of a user plane function and the network device is an access network device, the first processing layer of the access network device stops parsing the packet header information of the first data packet and sends the first data packet to the user plane function; and the user plane function, after receiving the first data packet, can parse the fourth identifier (or the fourth field) in the packet header information of the first data packet in the manner described in the above embodiment, obtain the fourth identifier, determine whether the indicated or identified network element type is a user plane device by parsing the fourth identifier, and further parse other identifiers if it is; and if it is not, in the case that the fourth identifier indicates or identifies a network element type of a MEC and the network device is a user plane function, the first processing layer of the user plane function stops parsing the packet header information of the first data packet and sends the first data packet to the MEC, which performs similar processing according to the above process.

[0172] In some optional embodiments of the application, in the case that the network device is a sending end device, before the network device and the terminal device transmit the first data packet, the method further includes: the application layer of the network device sends a data packet to be transmitted, sixth information and second service requirement information to the first processing layer; wherein the sixth information at least includes a service identifier, a message type and a data packet generation timestamp; the first processing layer of the network device encapsulates packet header information for the data packet based on the sixth information, matches a second QFI according to the second service requirement information, and sends the data packet encapsulated with the packet header information and the second QFI to the second processing layer, wherein the packet header information includes the first information.

[0173] In some optional embodiments, the transmission of the first data packet between the network device and the terminal device includes: a plurality of second processing layers of the network device sequentially process the data packet from the first processing layer to obtain the first data packet and send the first data packet to the network device; wherein the plurality of second processing layers at least include an SDAP layer, and the SDAP layer is located below the first processing layer.

[0174] In the embodiment, reference is made to Figure 8As shown, the content transmitted between the application layer of the sending device and the first processing layer (or ASP layer) through the (1)-a interface can include: service identification, message type, timestamp, network element type (optional information), network element address (optional information), service requirement information (optional information), and data (data). The service requirement information includes but is not limited to: delay, rate bandwidth, packet loss rate, and the like. The content transmitted between the first processing layer (or ASP layer) of the sending device and the SDAP layer through the (2)-a interface can include: a complete data packet containing the packet header information of the first processing layer (such as the ASP layer) and the service-mapped QFI (such as the second QFI).

[0175] In the embodiment, the first processing layer is located below the application layer and above the SDAP layer. When the network device is a sending device, the application layer of the network device sends a data packet to be transmitted, sixth information, and second service requirement information to the first processing layer. The second service requirement information includes but is not limited to: delay, rate bandwidth, packet loss rate, and the like. The sixth information at least includes service identification, message type, and timestamp provided by the application layer; in some optional embodiments, the sixth information further includes the following information: network element type of service endogenous deployment associated with data in the data packet, network element address where the service associated with the data in the data packet is located. Further, the first processing layer of the network device encapsulates the packet header information of the first processing layer for the data packet according to the sixth information received from the application layer, including marking the first identification, the second identification, and the third identification; if the network element type and the network element address are further included in the sixth information, the fourth identification and the fifth identification are marked. On the other hand, the QoS flow has been configured with a corresponding QFI file according to different indicators such as delay, reliability, and scheduling priority by the core network, so that the first processing layer of the network device can map the data packet to the second QFI matched therewith according to the obtained second service requirement information, and then send the data packet encapsulated with the packet header information of the first processing layer and the second QFI to the SDAP. Then, after being processed layer by layer through the existing protocol stack, the first data packet is sent to the network device.

[0176] In some optional embodiments of the application, before the first processing layer of the network device encapsulates the packet header information for the data packet based on the sixth information, the method further includes: the network device obtains a third mapping relationship and a fourth mapping relationship, the third mapping relationship includes a plurality of mapping relationships between the first identification and the application type, and the fourth mapping relationship includes a plurality of mapping relationships between the second identification and the message type.

[0177] In the embodiment, the network device as the sending end device maintains the third mapping relationship and the fourth mapping relationship in advance before sending the data packet. The third mapping relationship can also be referred to as a third mapping table, in which a plurality of groups of mapping relationships between the first identifiers and the service identifiers are defined; the fourth mapping relationship can also be referred to as a fourth mapping table, in which a plurality of groups of mapping relationships between the second identifiers and the message types are defined.

[0178] In some optional embodiments, the first processing layer of the network device encapsulates the header information of the data packet based on the sixth information, including: the first processing layer of the network device looks up the third mapping relationship based on the service identifier, determines the first identifier corresponding to the service identifier, looks up the fourth mapping relationship based on the message type of the data packet, determines the second identifier corresponding to the message type, and encapsulates the header information of the data packet based on at least the first identifier, the second identifier and the generation timestamp of the data packet.

[0179] In the embodiment, after the first processing layer of the network device as the sending end device receives the sixth information sent by the application layer, the sixth information at least includes the service identifier, the message type and the timestamp, the first processing layer of the network device obtains the first identifier corresponding to the service identifier of the data packet by querying the third mapping relationship maintained in advance, obtains the second identifier corresponding to the message type of the data packet by querying the fourth mapping relationship maintained in advance, and encapsulates the header information of the data packet according to the first identifier, the second identifier and the timestamp (marking the third identifier).

[0180] In some optional embodiments, the network device obtains the third mapping relationship and the fourth mapping relationship, including: the network device obtains the third mapping relationship and the fourth mapping relationship through a configured manner; or the network device obtains the third mapping relationship and the fourth mapping relationship from other network devices through signaling.

[0181] In the embodiment, the network device can obtain the third mapping relationship and the fourth mapping relationship through a configured (or locally configured) manner, or the network device can also obtain the third mapping relationship and the fourth mapping relationship from other network devices (such as a network management device) through signaling or a message.

[0182] In some optional embodiments of the present application, in the case where the network device is an access network device, the method further comprises: the access network device receiving a first request sent by the terminal device, the first request including a service identifier, the first request being used to request network element information of a service corresponding to the service identifier; the access network device searching for pre-deployed network element configuration information, obtaining the network element information corresponding to the service identifier, and sending a first response to the terminal device, the first response including the network element information, the network element information including a network element type and a network element address.

[0183] In the present embodiment, in the case where the network device is an access network device (such as a gNB), based on the description in the above embodiment, the terminal device can obtain the network element type and the network element address in a static addressing manner. Specifically, an addressing agent (Agent) is deployed or set by default on the side of the access network device (gNB), and the related configuration files of the network element information (which can include the network element type and the network element address) of the service are synchronized to the access network device agent (Agent) in advance. Then, the UE can initiate a session of the first processing layer, and send a first request, i.e., an addressing request (Adress Request), to the access network device, the request carrying a service identifier (service ID). The access network device searches for the network element information corresponding to the service ID, such as the network element type and the network element address, through the related configuration files of the agent (Agent), and informs the UE of the network element type and the network element address of the service through a first response, i.e., an addressing response (Adress Response).

[0184] The data transmission method of the present embodiment will be described in detail below in combination with several specific examples. In each of the following examples, the first processing layer is taken as an example of the ASP layer.

[0185] Example One

[0186] The present example is an uplink data transmission scheme, and a static addressing manner is adopted. Figure 11 The interaction flowchart of the data transmission method of the present embodiment is shown in Figure 1, which comprises the following steps. Figure 11

[0187] Step 401: The application layer (APP layer) of the UE sends a data packet to the ASP layer, carrying a service identifier of an application, a message type, a timestamp, and service requirement information.

[0188] Here, the service requirement information can include information such as latency, rate bandwidth, and packet loss rate. The above data packet and the carried information are sent to the ASP layer through an interface (1)-a.

[0189] ​Step 402: The ASP layer obtains the ASP packet header information for the data packet, and dynamically matches the QFI corresponding to the service ID.

[0190] Here, the ASP layer can obtain the first identifier (i.e., AID) corresponding to the service identifier by looking up the first mapping table (e.g., mapping table 1) maintained in advance, and obtain the second identifier (i.e., MT) corresponding to the message type by looking up the second mapping table (e.g., mapping table 2) maintained in advance. The first identifier is filled in the first field, the second identifier is filled in the second field, and the third identifier is marked in the third field according to the timestamp.

[0191] In this example, before step 401 is performed, the application layer of the UE can pre-configure or maintain the related configuration files of the first mapping table (e.g., mapping table 1) and the second mapping table (e.g., mapping table 2).

[0192] In addition, each QoS flow has been configured with a corresponding QFI file by the core network according to different indicators such as delay, reliability, scheduling priority, etc. Therefore, the ASP can map the service demand indicators (i.e., service demand information) received in real time through the interface (1)-a to the matching QFI, realize dynamic network capability matching, and realize more flexible and intelligent service guarantee.

[0193] Step 403: The ASP layer sends the complete data packet and the mapped QFI to the SDAP layer. After receiving the data packet, the SDAP layer processes it according to the existing protocol stack processing procedure, and sends the data packet through the air interface.

[0194] Here, the ASP sends the complete data packet after adding the ASP packet header information and the mapped QFI to the SDAP layer through the interface (2)-a.

[0195] Step 404: After receiving the data packet, the ASP layer of the receiving end device (e.g., gNB, UPF, or MEC) receives the data packet. Since this example uses a static addressing scheme, the network element address is known, so the ASP packet header information of the data packet does not include the fourth identifier for indicating or identifying the network element type and the fifth identifier for indicating or identifying the network element address. Therefore, the ASP layer of the receiving end device parses the ASP packet header to obtain the first identifier, the second identifier, and the third identifier; determines the corresponding service identifier according to the first identifier, determines the corresponding message type according to the second identifier, and determines the timestamp and other information according to the third identifier.

[0196] Here, the ASP layer of the receiving end device receives the data packet sent by the SDAP layer through the interface (2)-b.

[0197] Step 405: The ASP layer of the receiving end device sends the data packet to the APP layer, carrying relevant information, including the service identifier, the message type, and the timestamp and other information.

[0198] Here, the ASP layer of the receiving end device can send information to the APP layer according to the interface (1)-b.

[0199] Step 406: The APP layer of the receiving end device processes according to the association of the service type and the message type indication to the corresponding application process.

[0200] Example II

[0201] This example is an uplink data transmission scheme, and a dynamic addressing mode is adopted. Figure 12 The interactive flow of the data transmission method of the embodiment of the application is shown in Figure 2 As shown in Figure 12 The method comprises the following steps:

[0202] Step 501: The application layer (APP layer) of the UE sends a data packet to the ASP layer, carrying the service identification of the application deployment, the message type, the timestamp, the network element type, the network element address, and the service requirement information.

[0203] Here, the service requirement information can include information such as delay, rate bandwidth, and packet loss rate. The above data packet and the carried information are sent to the ASP layer through the interface (1)-a.

[0204] Step 502: The ASP layer obtains the ASP packet header information encapsulated for the data packet, and dynamically matches the QFI corresponding to the service ID.

[0205] Here, the ASP layer can obtain the first identification (i.e., AID) corresponding to the service identification by looking up the first mapping table (such as mapping table 1) maintained in advance, and obtain the second identification (i.e., MT) corresponding to the message type by looking up the second mapping table (such as mapping table 2) maintained in advance. The first identification is filled in the first field, the second identification is filled in the second field, the third identification is marked in the third field according to the timestamp, the fourth identification (i.e., NTI) is marked in the fourth field according to the network element type, and the fifth identification (i.e., NA) is marked in the fifth field according to the network element address.

[0206] In this example, before step 501 is performed, the application layer of the UE can pre-configure or maintain the related configuration files of the first mapping table (such as mapping table 1) and the second mapping table (such as mapping table 2).

[0207] In addition, each QoS flow has been configured with a corresponding QFI file by the core network according to different indicators such as delay, reliability, and scheduling priority, so that the ASP can map the service requirement indicators (i.e., service requirement information) received in real time through the interface (1)-a to the matching QFI, realize dynamic network capability matching, and realize more flexible and intelligent service guarantee.

[0208] Step 503: The ASP layer sends the complete data packet and the mapped QFI to the SDAP layer. After receiving the data packet, the SDAP layer processes it according to the existing protocol stack processing procedure until the data packet is sent through the air interface.

[0209] Here, the ASP layer sends the complete data packet with the added ASP packet header information and the mapped QFI to the SDAP layer through interface (2)-a.

[0210] Step 504: After the ASP layer of the receiving end device (such as gNB, UPF, or MEC) receives the data packet, since this example uses a dynamic addressing scheme, the ASP packet header information of the data packet includes a fourth identifier for indicating or identifying the network element type and a fifth identifier for indicating or identifying the network element address. Therefore, after the receiving end device (i.e., the access network device such as gNB) at the lowest layer receives the data packet sent by the UE, it parses the fourth field in the ASP packet header to obtain the fourth identifier, determines the network element type according to the fourth identifier, judges the network element position where the service is deployed, and further performs the following steps:

[0211] Step 505: Determine whether the network element type indicated or identified by the fourth identifier is an access network device (such as a base station). If the fourth identifier indicates or identifies the network element type as an access network device (such as a base station, gNB), the ASP layer of the access network device (such as gNB) continues to parse the subsequent packet header fields to obtain the first identifier, the second identifier, the third identifier, and the fifth identifier, and further determines the corresponding service identifier according to the first identifier, the corresponding message type according to the second identifier, the timestamp according to the third identifier, and the corresponding network element address according to the fifth identifier. Then, the ASP layer of the access network device (such as gNB) determines the APP according to the network element type and the network element address, and submits the parsed information such as the service type, the message type, and the timestamp to the APP layer corresponding to the determined APP.

[0212] Step 506: If the fourth identifier indicates or identifies the network element type as a UPF, the access network device (such as gNB) stops parsing other information in the packet header and sends the data packet to the UPF according to the traditional routing architecture.

[0213] Step 507: The ASP layer of the UPF parses the fourth field in the ASP packet header to obtain the fourth identifier and determines the network element type according to the fourth identifier.

[0214] Step 508: If the fourth identifier indicates or identifies the network element type as UPF, the ASP layer of the UPF continues to parse the subsequent packet header field to obtain the first identifier, the second identifier, the third identifier and the fifth identifier, further determines the corresponding service identifier according to the first identifier, determines the corresponding message type according to the second identifier, determines the timestamp according to the third identifier, and determines the corresponding network element address according to the fifth identifier; and the ASP layer of the UPF determines the APP according to the network element type and the network element address, and submits the information such as the service type, the message type and the timestamp obtained by parsing to the APP layer corresponding to the determined APP.

[0215] Step 509: If the fourth identifier indicates or identifies the network element type as local MEC, the UPF stops parsing other information of the ASP packet header, and sends the data packet to the MEC according to the traditional routing architecture, and the ASP layer of the MEC parses the subsequent field and submits the related information obtained by parsing to the APP layer.

[0216] In the above steps 505, 508 and 509, the ASP layer of the network device can send information to the APP layer according to the interface (1)-b.

[0217] Step 510: The APP layer of the network device (such as gNB, UPF or MEC) processes according to the corresponding application process associated to the service type and the message type.

[0218] Example Three

[0219] This example is a downlink data transmission scheme, and this example is described by taking dynamic addressing as an example. Figure 13 Interaction flow diagram of the data transmission method of the embodiment of the application Figure 3 As shown in the figure, the method comprises: Figure 13

[0220] Step 601: The application layer (APP layer) of the network device (such as gNB, UPF or MEC) sends a data packet to the ASP layer, carrying the service identifier of the application deployment, the message type, the timestamp, the network element type, the network element address and the service requirement information.

[0221] Here, the service requirement information can include information such as delay, rate bandwidth and packet loss rate. The above data packet and the carried information are sent to the ASP layer through the interface (1)-a.

[0222] Step 602: The ASP layer of the network device obtains the ASP packet header information encapsulated for the data packet, and the QFI matched by dynamic mapping of the service ID.

[0223] ​Here, the ASP layer can obtain the first identifier (i.e., AID) corresponding to the service identifier by searching the third mapping table (e.g., mapping table 3) maintained in advance, and can obtain the second identifier (i.e., MT) corresponding to the message type by searching the fourth mapping table (e.g., mapping table 4) maintained in advance, fill the first identifier in the first field, fill the second identifier in the second field, mark the third identifier in the third field according to the timestamp, mark the fourth identifier (i.e., NTI) in the fourth field according to the network element type, and mark the fifth identifier (i.e., NA) in the fifth field according to the network element address.

[0224] In the present example, before step 601 is performed, the application layer of the UE can pre-configure or maintain the relevant configuration files of the third mapping table (e.g., mapping table 3) and the fourth mapping table (e.g., mapping table 4).

[0225] In addition, each QoS flow has been configured with a corresponding QFI file by the core network according to different indicators such as delay, reliability, scheduling priority, etc., and then the ASP layer can map the service requirement indicators (i.e., service requirement information) received in real time by the interface (1)-a to the matching QFI, realize dynamic network capability matching, and realize more flexible and intelligent service guarantee.

[0226] Step 603: The ASP layer sends the complete data packet and the mapped QFI to the SDAP layer. After receiving the data packet, the SDAP layer processes according to the existing protocol stack processing process, and sends the data packet through the air interface.

[0227] Here, the ASP layer sends the complete data packet and the mapped QFI after adding the ASP packet header information to the SDAP layer through the interface (2)-a.

[0228] Step 604: After the ASP layer of the UE as the receiving end receives the data packet, the ASP layer analyzes all the ASP packet header information to obtain the first identifier, the second identifier, the third identifier, the fourth identifier, and the fifth identifier. According to the first identifier, the corresponding service identifier is determined, according to the second identifier, the corresponding message type is determined, according to the third identifier, the timestamp and other information are determined, according to the fourth identifier, the corresponding network element type is determined, and according to the fifth identifier, the corresponding network element address and other information are determined.

[0229] Here, the ASP layer of the UE receives the data packet sent by the SDAP layer through the interface (2)-b.

[0230] Step 605: The ASP layer of the UE determines the APP according to the network element type and the network element address, sends the data packet to the APP layer corresponding to the APP, carries relevant information, and the sent information includes the service identifier, the message type, and the timestamp and other information.

[0231] Here, the ASP layer of the receiving end device can send information to the APP layer through the interface (1)-b.

[0232] Step 606: The APP layer of the receiving device associates the corresponding application process with the service type and message type indication for processing.

[0233] The data transmission method of this invention will be described in detail below with reference to a specific application scenario.

[0234] Taking the connected vehicle industry as an example, connected vehicle services possess the characteristic of fusion perception of diverse data elements such as vehicles and roads. This presents both localized smart intersection needs for edge computing and high real-time response, such as blind spot warnings for "ghost pedestrians," emergency braking warnings, and collision warnings; and wide-area needs for traffic management, trajectory tracking, and lane navigation. Therefore, it is a typical scenario of multi-level cloud-edge-device collaborative deployment of business platforms. (Refer to...) Figure 14 As shown, the application's system architecture can be divided into an application layer, a network layer, and a perception layer. The perception layer may include onboard units (OBUs) located on the vehicle, and roadside units (RSUs) deployed on the road, such as cameras, traffic lights, and radar. The network layer includes core network elements / MEC, baseband processing units (BBUs), and active antenna units (AAUs). AAUs communicate with devices in the perception layer via Uu ports. The application layer may include a V2X cloud control platform (i.e., a V2X application).

[0235] Taking latency-sensitive blind zone early warning services as an example, the system requires end-to-end latency of 30-50ms and a reliability of 99.9%. To meet the high real-time and deterministic requirements across a wide area, the service needs to be deployed at the base station network element level, forming an intrinsic base station architecture. The protocol stack process based on ASP is as follows: Figure 15 As shown.

[0236] Assume the network element connection structure at a certain intersection is as follows: Figure 16 As shown, the packet header fields (network element type and network element address) are defined as follows: Figure 16 As shown in the image.

[0237] Reference Figure 16 As shown, the fourth identifier NTI corresponding to the network element type is 00, the fifth identifier NA corresponding to the network element address is 00, and the bit length of the first identifier AID corresponding to the service type is 2 bytes (16 bits), which can be defined as AID = 000100010011; Figure 17 As shown, the first 4 bits represent the industry type, represented by 4 bits, such as Industry = 0, Transportation = 1 (binary 0001), Power Grid = 2, and so on.

[0238] The first classification represents assisted driving or automatic driving. According to the definition in the existing line standard of Internet of Vehicles (such as “Cooperative Intelligent Transport System Vehicle Communication System Application Layer and Application Data Interaction Standard”), the typical V2X service includes DAY1 (stage one assisted driving type service) and DAY2 (stage two automatic driving type service) first classification and event type, safety type, efficiency type, information service and different second sub-class. As shown in Table 1, some DAY1 service classifications are shown, and Table 2 shows some DAY2 service classifications.

[0239] Table 1

[0240]

[0241]

[0242] Table 2

[0243] Serial Number Category Application Name 1 Safety Cooperative Lane Changing 2 Safety Cooperative Ramp Merging 3 Safety Cooperative Intersection Passage 4 Safety Perception Data Sharing / V2X Perception 5 Safety Road Obstacle Warning 6 Safety Slow Traffic Trajectory Identification and Behavior Analysis 7 Efficiency Vehicle Platoon 8 Efficiency Cooperative Fleet Management 9 Efficiency Special Vehicle Signal Priority 10 Efficiency Dynamic Lane Management 11 Efficiency Vehicle Path Guidance 12 Efficiency Station Access Service 13 Efficiency Dynamic Optimization of Traffic Signal Timing Based on Real-Time Connected Data 14 Efficiency Freeway Exclusive Lane Flexible Management 15 Efficiency Intelligent Parking Guidance 16 Information Service Floating Car Data Collection 17 Information Service Differential Data Service 18 Information Service Active and Passive Electronic Toll Collection Based on V2X 19 Information Service Remote Software Upgrade Based on V2X

[0244] Table 2

[0245] Therefore, in the present scenario, the first classification can be defined by 1 bit, such as: assisted driving DAY1 = 0 (binary 0), automatic driving DAY2 = 1 (binary 1).

[0246] The second sub-class can be defined to represent the service category, which is represented by 3 bits, such as event type = 0 (binary 000), safety type = 1 (binary 001), efficiency type = 2 (binary 010), information service type = 3 (binary 011), and so on.

[0247] The specific service name can be defined by 4 bits, such as forward collision = 0, intersection collision = 1, left turn assistance = 2, blind area warning = 3 (binary 0011), and so on.

[0248] The last 4 bits of the first identifier are temporarily defaulted.

[0249] In the present scenario, the mapping table 1 of the first identifier AID and the service identifier (or service type) can be predefined according to the above rules.

[0250] For message type: V2X service includes 5 application layer corresponding V2X national standard message body, message type and second identifier MT one-to-one mapping can be established, for example:

[0251] MT = 000 - BSM: vehicle status information reported by the vehicle OBU module;

[0252] MT = 001 - RSM: AI structured processing and key event identification and extraction of collision, obstacle, vehicle and pedestrian information reported by roadside cameras, radars, etc., and packaging into RSM messages;

[0253] MT = 010 - RSI: Traffic warning messages such as traffic signs and information boards uploaded by roadside communication gateway / roadside unit, such as speed limit ahead, sharp turn, load warning, etc.

[0254] MT = 011 - SPAT: Traffic light timing phase information.

[0255] MT = 100 - MAP: Map data.

[0256] According to the above examples, the mapping table 2 of the second identifier MT and the message type of each industry can be predefined.

[0257] The implementation of the blind area warning and other services is based on the fusion perception and calculation of different V2X message types. The ASP can identify the services and messages based on the above mapping table 1 and mapping table 2.

[0258] For the timestamp, a third identifier TM field can be added to the data packet based on the time when the data packet is received from the application layer or the timestamp carried in the data packet, for example, in the format of date / hour / minute / second / second / second, such as 12 / 31 / 11:59:59.99PM.

[0259] According to the implementation process of the blind area warning service, the implementation process of the blind area warning service can be referred to as shown in Figure 18 , which specifically includes:

[0260] Step 701: The roadside perception device sends perception information to the gNB; wherein the perception information can include roadside traffic event and traffic sign message (RSI), map information (MAP), signal light information (SPAT), and video / radar information.

[0261] Step 702: The vehicle-mounted device sends uplink data to the gNB, wherein the uplink data can include vehicle basic safety message (BSM).

[0262] Step 703: The gNB performs time synchronization and fusion calculation.

[0263] Step 704: The gNB sends downlink data to the vehicle-mounted device, wherein the downlink data can include roadside safety message (RSM), RSI, SPAT, and other messages.

[0264] Here, step 702 can use the ASP-based uplink data transmission scheme of the embodiment of the application. Step 704 can use the ASP-based downlink data transmission scheme of the embodiment of the application.

[0265] The ASP-based uplink data transmission process can be referred to as shown in Figure 19As shown, taking the process of reporting BSM by vehicle OBU to gNB sever as an example, due to the mobility of the vehicle, a dynamic addressing mode is adopted, and specifically can include:

[0266] The application layer (APP layer) of the UE sends a data packet to the ASP layer, carrying the network element type (gNB) to which the service platform belongs, the network element address (the address of the station), the service identification (or the service type, blind area early warning), the message type (BSM), and the service requirement information (such as a time delay of 50 ms and a packet loss rate of 99.9%).

[0267] The ASP layer of the UE encapsulates an ASP packet header, specifically including: looking up a mapping table 1 to obtain a first identification AID corresponding to the service identification 000100010011; looking up a mapping table 2 to obtain a second identification MT corresponding to the message type 001; according to the network element type being gNB, marking a fourth identification NTI as 00; according to the network element address, marking a fifth identification NA as 00; according to the time stamp, marking the third identification as 12 / 31 / 11:59:59.99 PM. In addition, the ASP layer matches QFI=A based on the service requirement (such as a time delay of 50 ms and a packet loss rate of 99.9%).

[0268] The ASP layer of the UE sends the complete data packet and the mapped QFI=A to the SDAP layer.

[0269] The ASP layer of the gNB receives the data packet from the SDAP layer, parses the fourth identification NTI in the ASP packet header, determines that the network element type is a base station, and then continues to parse the remaining packet header information to obtain the first identification AID 000100010011, the second identification MT 001, the third identification 12 / 31 / 11:59:59.99 PM, and the fifth identification NA 00. Then, the ASP layer of the gNB looks up the mapping table 1 according to the first identification AID 000100010011 to determine the corresponding service identification (or service type, such as blind area early warning), and looks up the mapping table 2 according to the second identification MT 001 to determine that the corresponding message type is BSM. Then, the ASP layer of the gNB determines the corresponding “blind area early warning” APP according to the network element type and the network element address, and submits the BSM information to the APP layer corresponding to the “blind area early warning” APP through an interface. The submitted information includes, for example, the service identification (or service type, such as blind area early warning), the message type, and the time stamp.

[0270] Figure 20 It is a schematic diagram of the packet header encapsulation process in the data transmission method of the embodiment of the application; as Figure 20As shown, the ASP layer encapsulates an ASP header for data, the ASP header including a first identifier (AID), a second identifier (MT), and a third identifier (TM), and optionally a fourth identifier (NTI) and a fifth identifier (NA); in addition, QoS flow mapping is performed based on service requirements, and QFI=A is matched.

[0271] The ASP-based downlink data transmission process can refer to Figure 21 As shown, taking the end-to-end communication process of the RSM message issued in the service process as an example, the same dynamic addressing mode can be used, and the process can specifically include:

[0272] The application layer (APP layer) of the gNB sends a data packet to the ASP layer, carrying the network element type (gNB) where the APP is located, the network element address (local address), the service identifier (or service type, blind area early warning), the message type (BSM), and the service requirement information (such as a delay of 50 ms and a packet loss rate of 99.9%).

[0273] The ASP layer of the gNB encapsulates an ASP header, specifically including: looking up a mapping table 1 to obtain a first identifier AID=000100010011 corresponding to the service identifier; looking up a mapping table 2 to obtain a second identifier MT=001 corresponding to the message type, marking a fourth identifier NTI=00 according to the network element type gNB, marking a fifth identifier NA=00 according to the network element address, and marking a third identifier as 12 / 31 / 11:59:59.99 PM according to the timestamp. In addition, the ASP layer matches QFI=A based on the service requirements (such as a delay of 50 ms and a packet loss rate of 99.9%).

[0274] The ASP layer of the gNB sends a complete data packet and the mapped QFI=A to the SDAP layer.

[0275] The ASP layer of the UE receives a data packet from the SDAP layer, parses all the contents in the ASP header, obtains a first identifier AID=000100010011, a second identifier MT=001, a third identifier 12 / 31 / 11:59:59.99 PM, and a fourth identifier NTI=00, determines that the network element type is a base station, and a fifth identifier NA=00, so that the ASP layer of the gNB determines the corresponding service identifier (or service type, such as blind area early warning) according to the first identifier AID=000100010011, and determines the corresponding message type RSM according to the second identifier MT=001 by looking up a mapping table 2. Then, the ASP layer of the UE determines the corresponding “blind area early warning” APP according to the network element type and the network element address, submits RSM information to the APP layer corresponding to the “blind area early warning” APP through an interface, and the submitted information includes, for example, the service identifier (or service type, such as blind area early warning), the message type, and the timestamp.

[0276] Based on the above-mentioned embodiments, the embodiments of the present application further provide a data transmission device, which is applied to a terminal device. Figure 22 As shown in Figure 1, the device comprises a first communication unit 11, which is used for transmitting a first data packet with a network device, wherein the first data packet comprises first information, and the first information is used for indicating or associating a service of an application layer; and the first information is processed by a first processing layer. Figure 22

[0277] In some optional embodiments of the present application, the first information comprises a first identifier, a second identifier and a third identifier, the first identifier is used for indicating or identifying a service type, the second identifier is used for indicating or identifying a message type, and the third identifier is used for indicating or identifying a generation time of the data packet.

[0278] In some optional embodiments of the present application, the first information further comprises a fourth identifier and a fifth identifier, the fourth identifier is used for indicating or identifying a network element type of an in-service deployment of data associated with the service in the data packet, and the fifth identifier is used for indicating or identifying a network element address of the service in which the data associated with the service in the data packet is located.

[0279] In some optional embodiments of the present application, when the terminal device is a sending terminal device, the device further comprises a first processing unit 12, which is used for executing the application layer of the terminal device to send a data packet to be transmitted, second information and first service requirement information to the first processing layer; wherein the second information at least comprises a service identifier, a message type and a generation time stamp of the data packet; and the first processing unit 12 is further used for executing the first processing layer of the terminal device to encapsulate a packet header information based on the second information for the data packet, to match a first quality of service flow identifier (QFI) according to the first service requirement information, and to send the data packet encapsulated with the packet header information and the first quality of service flow identifier (QFI) to a second processing layer, wherein the packet header information comprises the first information.

[0280] In some optional embodiments of the present application, the second information further comprises the following information: a network element type of an in-service deployment of data associated with the service in the data packet, and a network element address of the service in which the data associated with the service in the data packet is located.

[0281] In some optional embodiments of the present application, the first processing unit 12 is further used for executing a plurality of second processing layers of the terminal device to sequentially process the data packet from the first processing layer, so as to obtain the first data packet; wherein the plurality of second processing layers at least comprises an SDAP layer, and the SDAP layer is located at a lower layer of the first processing layer.

[0282] ​The first communication unit 11 is configured to send the first data packet obtained by the first processing unit 12 to the network device.

[0283] In some optional embodiments of the present application, the first communication unit 11 is further configured to send a first request to the access network device, the first request including a service identifier, the first request being used to request information about a network element on which a service corresponding to the service identifier is deployed; and receive a first response sent by the access network device, the first response including information about a network element on which the service corresponding to the service identifier is deployed, the information about the network element including a network element type and a network element address.

[0284] In some optional embodiments of the present application, the first processing unit 12 is configured to, before the first processing layer of the terminal device encapsulates the packet header information of the data packet based on the second information, obtain a first mapping relationship and a second mapping relationship; the first mapping relationship includes a plurality of groups of mapping relationships between first identifiers and service identifiers, and the second mapping relationship includes a plurality of groups of mapping relationships between second identifiers and message types.

[0285] In some optional embodiments of the present application, the first processing unit 12 is configured to, based on the service identifier, search the first mapping relationship to determine a first identifier corresponding to the service identifier, and based on the message type, search the second mapping relationship to determine a second identifier corresponding to the message type, and encapsulate the packet header information of the data packet based on at least the first identifier, the second identifier and a generation timestamp of the data packet.

[0286] In some optional embodiments of the present application, when the terminal device is a receiving terminal device, the apparatus further includes a first processing unit 12 configured to receive, by the first processing layer of the terminal device, the first data packet from the network device.

[0287] In some optional embodiments of the present application, the first processing unit 12 is configured to, perform, by the first processing layer of the terminal device, analysis on the packet header information of the first data packet to obtain first information, the first information including at least the first identifier, the second identifier and the third identifier; and perform, by the first processing layer of the terminal device, determination of a service identifier, a message type and a generation timestamp of a data packet based on the first information, and send third information including the service identifier, the message type and the generation timestamp of the data packet to an application layer.

[0288] In some optional embodiments of the present application, the network element type includes an access network device, a UPF or a MEC.

[0289] In the embodiment of the present application, the first processing unit 12 in the device can be implemented by a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU) or a field-programmable gate array (FPGA) in actual application; and the first communication unit 11 in the device can be implemented by a communication module (including a basic communication suite, an operating system, a communication module, a standardized interface and a protocol, etc.) and a transceiving antenna in actual application.

[0290] The embodiment of the present application further provides a data transmission device, which is applied to a network equipment. Figure 23 The composition structure of the data transmission device of the embodiment of the present application is shown in Fig. 1. Figure 2 As shown in Fig. 1, the device comprises a second communication unit 21, which is used for transmitting a first data packet between the network equipment and a terminal equipment, wherein the first data packet comprises first information, and the first information is used for indicating or associating a service of an application layer; and the first information is processed by a first processing layer. Figure 23

[0291] In some optional embodiments of the present application, the first information comprises a first identifier, a second identifier and a third identifier, the first identifier is used for indicating or identifying a service type, the second identifier is used for indicating or identifying a message type, and the third identifier is used for indicating or identifying a generation time of the data packet.

[0292] In some optional embodiments of the present application, the first information further comprises a fourth identifier and a fifth identifier, the fourth identifier is used for indicating or identifying a network element type of in-situ deployment of a service associated with data in the data packet, and the fifth identifier is used for indicating or identifying a network element address where the service associated with the data in the data packet is located.

[0293] In some optional embodiments of the present application, the network element type comprises an access network equipment, a UPF or a MEC.

[0294] In some optional embodiments of the present application, when the network equipment is a receiving end equipment, the device further comprises a second processing unit 22, which is used for executing the first processing layer of the network equipment to receive the first data packet from the terminal equipment which is processed by a plurality of second processing layers; wherein the plurality of second processing layers at least comprise an SDAP layer, and the SDAP layer is located at a lower layer of the first processing layer.

[0295] ​In some optional embodiments of the present application, the second processing unit 22 is further configured to perform the first processing layer of the network device to parse the packet header information of the first data packet to obtain first information, the first information including the first identifier, the second identifier, and the third identifier; and perform the first processing layer of the network device to determine, based on the first information, a service identifier, a message type, and a data packet generation timestamp, and send fourth information including the service identifier, the message type, and the data packet generation timestamp to the application layer.

[0296] In some optional embodiments of the present application, the second processing unit 22 is further configured to perform the first processing layer of the network device to parse a fourth identifier in the packet header information of the first data packet, and in a case where the fourth identifier indicates or identifies a same type of network element as the network device, continue to parse other identifiers in the packet header information to obtain first information, the first information including the first identifier, the second identifier, the third identifier, the fourth identifier, and a fifth identifier indicating or identifying a network element address of a service associated with data in the data packet; and perform the first processing layer of the network device to determine, based on the first information, a service identifier, a message type, a data packet generation timestamp, and a network element address, and send fifth information including the service identifier, the message type, the data packet generation timestamp, the network element type, and the network element address to the application layer.

[0297] In some optional embodiments of the present application, the second processing unit 22 is further configured to, in a case where the fourth identifier indicates or identifies a different type of network element than the network device, perform the first processing layer of the access network device to stop parsing the packet header information of the first data packet and send the first data packet to the user plane function when the fourth identifier indicates or identifies a user plane function, or perform the first processing layer of the user plane function to stop parsing the packet header information of the first data packet and send the first data packet to the MEC when the fourth identifier indicates or identifies a MEC.

[0298] In some optional embodiments of the present application, when the network device is a sending device, the apparatus further comprises a second processing unit 22 configured to perform, before the first data packet is transmitted between the second communication unit 21 and a terminal device, sending, by an application layer of the network device, a data packet to be transmitted, sixth information and second service requirement information to a first processing layer; wherein the sixth information at least includes service identification, message type and data packet generation timestamp; and further configured to perform, by the first processing layer of the network device, encapsulating, based on the sixth information, packet header information for the data packet, matching a second quality of service flow identifier (QFI) according to the second service requirement information, and sending the data packet encapsulated with the packet header information and the second quality of service flow identifier (QFI) to a second processing layer, wherein the packet header information includes the first information.

[0299] In some optional embodiments of the present application, the sixth information further includes the following information: a network element type of a service to which data in the data packet is associated, and a network element address of the service to which the data in the data packet is associated.

[0300] In some optional embodiments of the present application, the second processing unit 22 is further configured to perform, by the multiple second processing layers of the network device, processing of the data packet from the first processing layer in sequence to obtain the first data packet; wherein the multiple second processing layers at least include an SDAP layer, and the SDAP layer is located below the first processing layer.

[0301] The second communication unit 21 is configured to send the first data packet to the network device.

[0302] In some optional embodiments of the present application, the second processing unit 22 is further configured to perform, by the first processing layer of the network device, obtaining a third mapping relationship and a fourth mapping relationship before encapsulating packet header information for the data packet based on the second information, wherein the third mapping relationship includes a plurality of groups of mapping relationships between first identifiers and service identifications, and the fourth mapping relationship includes a plurality of groups of mapping relationships between second identifiers and message types.

[0303] In some optional embodiments of the present application, the second processing unit 22 is configured to perform, by the first processing layer of the network device, looking up the third mapping relationship based on the service identification, determining a first identifier corresponding to the service identification, looking up the fourth mapping relationship based on the message type, determining a second identifier corresponding to the message type, and encapsulating packet header information for the data packet based on at least the first identifier, the second identifier and the data packet generation timestamp.

[0304] In some optional embodiments of the present application, the second processing unit 22 is configured to obtain the third mapping relationship and the fourth mapping relationship by configuration, or obtain the third mapping relationship and the fourth mapping relationship through signaling from other network devices.

[0305] In some optional embodiments of the present application, in the case that the network device is an access network device, the apparatus further comprises a second processing unit 22.

[0306] The second communication unit 21 is further configured to receive a first request sent by the terminal device, the first request comprising a service identifier, and the first request being used to request network element information of a service corresponding to the service identifier.

[0307] The second processing unit 22 is configured to search for pre-deployed network element configuration information, and obtain the network element information corresponding to the service identifier.

[0308] The second communication unit 21 is further configured to send a first response to the terminal device, the first response comprising the network element information, and the network element information comprising a network element type and a network element address.

[0309] In the embodiments of the present application, the second processing unit 22 in the apparatus can be implemented by a CPU, a DSP, a MCU or an FPGA in actual application; and the second communication unit 21 in the apparatus can be implemented by a communication module (including a basic communication suite, an operating system, a communication module, a standardized interface and a protocol, etc.) and a transceiving antenna in actual application.

[0310] It should be noted that the data transmission apparatus provided by the above embodiments is only used for example to illustrate the division of the above program modules, and in actual application, the above processing can be completed by different program modules according to needs, that is, the internal structure of the apparatus is divided into different program modules to complete all or part of the above processing. In addition, the data transmission apparatus and the data transmission method provided by the above embodiments belong to the same concept, and the specific implementation process is shown in the method embodiments, which will not be repeated here.

[0311] The embodiments of the present application further provide a communication device, which can be a network device or a terminal device. Figure 24 As shown in the hardware component structure diagram of the communication device of the embodiments of the present application, Figure 24 the communication device comprises a memory 32, a processor 31, and a computer program stored in the memory 32 and executable on the processor 31, and the processor 31 implements the steps of the data transmission method applied to the network device or the terminal device when executing the program.

[0312] Optionally, the communication device also includes at least one network interface 33. In this regard, various components of the communication device are coupled together by a bus system 34, which is used to facilitate communication among the components. It should be understood that the bus system 34 is used to facilitate communication among the components and does not necessarily have to be implemented with a single bus. Rather, the bus system 34 can be implemented with a system of buses, such as a data bus, power bus, control bus, and / or a state signal bus. However, for clarity, only a single bus is shown in FIG. 3 and is referred to as the bus system 34. Figure 24

[0313] ​It can be appreciated that the memory 32 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Ferromagnetic Random Access Memory (FRAM), a Flash Memory, a magnetic surface memory, an optical disc, or a Compact Disc Read-Only Memory (CD-ROM). The magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a Random Access Memory (RAM) used as an external cache. By way of example but not limitation, many forms of RAM can be used, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 32 described in the embodiments of the present application is intended to include, but not limited to, these and any other suitable type of memory.

[0314] The method disclosed in the embodiments of the present application can be applied to the processor 31 or implemented by the processor 31. The processor 31 can be an integrated circuit chip having a processing capability of signals. In the implementation process, each step of the above method can be completed by the integrated logic circuit of hardware in the processor 31 or the instruction in the form of software. The processor 31 described above can be a general processor, a DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The processor 31 can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application. The general processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiments of the present application, the hardware decoding processor can be directly embodied to complete the execution, or the combination of hardware and software modules in the decoding processor can be used to complete the execution. The software module can be located in the storage medium, which is located in the memory 32. The processor 31 reads the information in the memory 32 and combines the hardware to complete the steps of the above method.

[0315] In the exemplary embodiments, the communication device can be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs, PLDs (Programmable Logic Devices), CPLDs (Complex Programmable Logic Devices), FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic elements, for executing the above-mentioned methods.

[0316] In the exemplary embodiments, the embodiments of the present application also provide a computer-readable storage medium, such as the memory 32 including a computer program, which can be executed by the processor 31 of the communication device to complete the steps of the above-mentioned methods. The computer-readable storage medium can be FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM, etc. storage; or can be various devices including one or any combination of the above storage.

[0317] The computer-readable storage medium provided by the embodiments of the present application has a computer program stored thereon, which is executed by the processor to implement the steps of the data transmission method applied to the network device or the terminal device by the embodiments of the present application.

[0318] The methods disclosed in the several method embodiments provided in the present application can be combined arbitrarily without conflict to obtain new method embodiments.

[0319] The features disclosed in the several product embodiments provided in the present application can be combined arbitrarily without conflict to obtain new product embodiments.

[0320] The features disclosed in the several method or device embodiments provided in the present application can be combined arbitrarily without conflict to obtain new method embodiments or device embodiments.

[0321] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic, for example, the division of the units is merely a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the various components shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0322] The units described above as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place or distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the present embodiment.

[0323] In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be realized in the form of hardware or in the form of hardware plus software functional unit.

[0324] Those of ordinary skill in the art can understand that all or part of the steps of the above method embodiments can be completed by program instruction related hardware, and the foregoing program can be stored in a computer readable storage medium, and the program executes the steps including the above method embodiments when executed; and the foregoing storage medium includes mobile storage equipment, ROM, RAM, magnetic disc or optical disc and various program code storage media.

[0325] Alternatively, the above-mentioned integrated unit of the present application, if realized in the form of a software function module and sold or used as an independent product, can also be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of the embodiments of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the methods described in the embodiments of the present application. The aforementioned storage medium includes: mobile storage devices, ROM, RAM, magnetic disks or optical disks, and various media that can store program codes.

[0326] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto, any person skilled in the art can easily think of changes or replacements within the technical range disclosed by the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A data transmission method, characterized by, The method is applied to a terminal device, and the method comprises: transmitting a first data packet between the terminal device and a network device, wherein the first data packet comprises first information, and the first information is used for indicating or associating with a service at an application layer; and the first information is processed by a first processing layer; when the terminal device is a sending terminal device, before transmitting the first data packet between the terminal device and the network device, the method further comprises: sending, by an application layer of the terminal device, a data packet to be transmitted, second information and first service requirement information to the first processing layer; wherein the second information comprises at least a service identifier, a message type and a timestamp of the data packet; encapsulating, by the first processing layer of the terminal device, packet header information for the data packet based on the second information, matching a first quality of service flow identifier (QFI) according to the first service requirement information, and sending the data packet encapsulated with the packet header information and the first quality of service flow identifier (QFI) to a service data adaptation protocol (SDAP) layer in a plurality of second processing layers, wherein the SDAP layer is located at a lower layer of the first processing layer, and the packet header information comprises the first information.

2. The method of claim 1, wherein, The first information comprises a first identifier, a second identifier and a third identifier, the first identifier is used for indicating or identifying a service type, the second identifier is used for indicating or identifying a message type, and the third identifier is used for indicating or identifying a generation time of the data packet.

3. The method of claim 2, wherein, The first information further comprises a fourth identifier and a fifth identifier, the fourth identifier is used for indicating or identifying a network element type of in-situ deployment of a service associated with data in the data packet, and the fifth identifier is used for indicating or identifying a network element address of the service associated with the data in the data packet.

4. The method of claim 1, wherein, The second information further comprises the following information: a network element type of in-situ deployment of a service associated with data in the data packet, and a network element address of the service associated with the data in the data packet.

5. The method of claim 1, wherein, The method further comprises: processing, by a plurality of second processing layers of the terminal device, the data packet from the first processing layer in sequence to obtain the first data packet, and sending the first data packet to the network device; wherein the plurality of second processing layers comprise at least a service data adaptation protocol (SDAP) layer, and the SDAP layer is located at a lower layer of the first processing layer.

6. The method of claim 1, wherein, The method further comprises: sending, by the terminal device, a first request to an access network device, wherein the first request comprises a service identifier, and the first request is used for requesting network element information of a service corresponding to the service identifier; receiving, by the terminal device, a first response sent by the access network device, wherein the first response comprises network element information of the service corresponding to the service identifier, and the network element information comprises a network element type and a network element address.

7. The method of claim 1, wherein, Before the first processing layer of the terminal device encapsulates the packet header information of the first processing layer for the data packet based on the second information, the method further comprises: obtaining, by the terminal device, a first mapping relationship and a second mapping relationship; wherein the first mapping relationship comprises a plurality of mapping relationships between first identifiers and service identifiers, and the second mapping relationship comprises a plurality of mapping relationships between second identifiers and message types.

8. The method of claim 7, wherein, The first processing layer of the terminal device encapsulates the first processing layer packet header information for the data packet based on the second information, including: The first processing layer of the terminal device looks up the first mapping relationship based on the service identifier, determines the first identifier corresponding to the service identifier, and looks up the second mapping relationship based on the message type, determines the second identifier corresponding to the message type, and encapsulates the packet header information for the data packet based on at least the first identifier, the second identifier and the data packet generation timestamp.

9. The method of claim 2 or 3, wherein, When the terminal device is a receiving end device, the terminal device and the network device transmit the first data packet, including: The first processing layer of the terminal device receives the first data packet from the network device.

10. The method of claim 9, wherein, The method further includes: The first processing layer of the terminal device parses the packet header information of the first data packet to obtain first information, and the first information at least includes the first identifier, the second identifier and the third identifier; The first processing layer of the terminal device determines the service identifier, the message type and the data packet generation timestamp based on the first information, and sends third information to the application layer, and the third information includes the service identifier, the message type and the data packet generation timestamp.

11. The method of claim 10, wherein, The first information further includes a fourth identifier and a fifth identifier; The third information is sent to the application layer, including: the first processing layer of the terminal device sends the third information to the application layer corresponding to the application indicated or associated by the fourth identifier and the fifth identifier.

12. The method of claim 3, wherein, The network element type includes: access network device, user plane function UPF or multi-access edge computing MEC.

13. A data transmission method, characterized by, The method is applied to a network device, and the method includes: The network device and the terminal device transmit the first data packet, and the first data packet includes first information, and the first information is used to indicate or associate the service of the application layer; the first information is processed by the first processing layer; When the network device is a receiving end device, the network device and the terminal device transmit the first data packet, including: The first processing layer of the network device receives the first data packet from the terminal device processed by multiple second processing layers; wherein the multiple second processing layers at least include the SDAP layer, and the SDAP layer is located below the first processing layer; The method further includes: the first processing layer of the network device parses the packet header information of the first data packet to obtain first information, and the first information includes a first identifier, a second identifier and a third identifier; The first processing layer of the network device determines the service identifier, the message type and the data packet generation timestamp based on the first information, and sends fourth information to the application layer, and the fourth information includes the service identifier, the message type and the data packet generation timestamp.

14. The method of claim 13, wherein, The first information includes a first identifier, a second identifier and a third identifier, the first identifier is used to indicate or identify the service type, the second identifier is used to indicate or identify the message type, and the third identifier is used to indicate or identify the data packet generation time.

15. The method of claim 14, wherein, The first information further includes a fourth identifier and a fifth identifier, the fourth identifier is used to indicate or identify a type of a network element of an in-situ deployment of a data-associated service in a data packet, and the fifth identifier is used to indicate or identify an address of a network element where the data-associated service in the data packet is located.

16. The method of claim 15, wherein, The network element type includes an access network device, a UPF, or a MEC.

17. The method of claim 13, wherein, The method further includes: The first processing layer of the network device parses the fourth identifier in the header information of the first data packet, and in a case where the type of the network element indicated or identified by the fourth identifier is the same as the type of the network device, the first processing layer continues to parse other identifiers in the header information to obtain first information, the first information including the first identifier, the second identifier, the third identifier, the fourth identifier, and a fifth identifier used to indicate or identify an address of a network element where the data-associated service in the data packet is located. The first processing layer of the network device determines, based on the first information, a service identifier, a message type, a timestamp of generation of the data packet, and the address of the network element, and sends fifth information including the service identifier, the message type, and the timestamp of generation of the data packet to an application layer of an application corresponding to the type of the network element and the address of the network element.

18. The method of claim 17, wherein, In a case where the type of the network element indicated or identified by the fourth identifier is different from the type of the network device, the method further includes: In a case where the type of the network element indicated or identified by the fourth identifier is a user plane function and the network device is an access network device, the first processing layer of the access network device stops parsing the header information of the first data packet and sends the first data packet to the user plane function; or In a case where the type of the network element indicated or identified by the fourth identifier is a MEC and the network device is a user plane function, the first processing layer of the user plane function stops parsing the header information of the first data packet and sends the first data packet to the MEC.

19. The method of claim 14 or 15, wherein, In a case where the network device is a sending-end device, before the network device and a terminal device transmit the first data packet, the method further includes: The application layer of the network device sends, to the first processing layer, a data packet to be transmitted, sixth information, and second service requirement information, wherein the sixth information at least includes a service identifier, a message type, and a timestamp of generation of the data packet; The first processing layer of the network device encapsulates header information for the data packet based on the sixth information, matches a second quality of service flow identifier (QFI) according to the second service requirement information, and sends the data packet encapsulated with the header information and the second quality of service flow identifier (QFI) to the second processing layer, the header information including the first information.

20. The method of claim 19, wherein, The sixth information further includes the following information: a type of a network element of an in-situ deployment of a data-associated service in a data packet, and an address of a network element where the data-associated service in the data packet is located.

21. The method of claim 19, wherein, The transmission of the first data packet between the network device and the terminal device includes: The network device comprises a plurality of second processing layers, which sequentially process the data packet from the first processing layer to obtain the first data packet and send the first data packet to the network device; wherein the plurality of second processing layers at least comprises an SDAP layer, and the SDAP layer is located below the first processing layer.

22. The method of claim 19, wherein, Before the first processing layer of the network device encapsulates the packet header information based on the sixth information, the method further comprises: The network device obtains a third mapping relationship and a fourth mapping relationship, the third mapping relationship comprises a plurality of groups of mapping relationships between first identifiers and service identifiers, and the fourth mapping relationship comprises a plurality of groups of mapping relationships between second identifiers and message types.

23. The method of claim 22, wherein, The first processing layer of the network device encapsulates the packet header information based on the sixth information, comprising: The first processing layer of the network device searches the third mapping relationship based on the service identifier to determine the first identifier corresponding to the service identifier, searches the fourth mapping relationship based on the message type to determine the second identifier corresponding to the message type, and encapsulates the packet header information based on at least the first identifier, the second identifier and the generation timestamp of the data packet.

24. The method of claim 22, wherein, The network device obtains a third mapping relationship and a fourth mapping relationship, comprising: The network device obtains the third mapping relationship and the fourth mapping relationship through configuration; or, The network device obtains the third mapping relationship and the fourth mapping relationship through signaling from other network devices.

25. The method according to any one of claims 13 to 15, characterized in that, In the case that the network device is an access network device, the method further comprises: The access network device receives a first request sent by the terminal device, the first request comprising a service identifier, and the first request being used to request network element information of a service corresponding to the service identifier; The access network device searches pre-deployed network element configuration information to obtain network element information corresponding to the service identifier, and sends a first response to the terminal device, the first response comprising the network element information, and the network element information comprising a network element type and a network element address.

26. A data transmission device, characterized by The device is applied to a terminal device, and the device comprises a first communication unit configured to transmit a first data packet to a network device, the first data packet comprising first information, the first information being used to indicate or associate a service at an application layer; and the first information being processed by a first processing layer. When the terminal device is a sending terminal device, the apparatus further comprises a first processing unit configured to, before transmitting the first data packet with the network device, perform sending, by an application layer of the terminal device, a data packet to be transmitted, second information, and first service requirement information to a first processing layer; wherein the second information at least comprises a service identifier, a message type, and a data packet generation timestamp; and perform, by the first processing layer of the terminal device, encapsulating packet header information for the data packet based on the second information, matching a first quality of service flow identifier (QFI) according to the first service requirement information, and sending the data packet encapsulated with the packet header information and the first quality of service flow identifier (QFI) to a service data adaptation protocol (SDAP) layer in a plurality of second processing layers, the SDAP layer being located at a lower layer of the first processing layer, and the packet header information comprising the first information.

27. A data transmission device, characterized by The apparatus is applied to a network device, and the apparatus comprises a second communication unit configured to transmit a first data packet with a terminal device, the first data packet comprising first information, the first information being used for indicating or associating a service of an application layer; and the first information being processed by a first processing layer. When the network device is a receiving terminal device, the apparatus further comprises a second processing unit configured to perform receiving, by a first processing layer of the network device, a first data packet from the terminal device, the first data packet being processed by a plurality of second processing layers; wherein the plurality of second processing layers at least comprise an SDAP layer, the SDAP layer being located at a lower layer of the first processing layer; perform analyzing, by the first processing layer of the network device, packet header information of the first data packet to obtain first information, the first information comprising a first identifier, a second identifier, and a third identifier; and perform determining, by the first processing layer of the network device, a service identifier, a message type, and a data packet generation timestamp based on the first information, and sending fourth information to an application layer, the fourth information comprising the service identifier, the message type, and the data packet generation timestamp.

28. A computer readable storage medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the steps of the method of any one of claims 1 to 12; or The program is executed by the processor to implement the steps of the method of any one of claims 13 to 25.

29. A communication device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, The processor executes the program to implement the steps of the method of any one of claims 1 to 12; or The processor executes the program to implement the steps of the method of any one of claims 13 to 25.

Images