Data transmission method, apparatus, and system

Abstract

A data transmission method, apparatus, and system. In the method, at least one tunnel is present between an access network device and a terminal device, the tunnel comprises at least one flow, and the at least one flow is used for transmitting data. The access network device can send mapping information to the terminal device, then data transmission can be performed between the access network device and the terminal device on the basis of the mapping information, thereby achieving mapping between the data transmitted by the tunnel or the flow in the tunnel and a QoS flow, thus realizing differentiated transmission.

Description

Data transmission method, device and system

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on December 26, 2023, with application number 202311825742.3 and application name "A Data Transmission Method, Device and System", all contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a data transmission method, device and system. Background Art

[0004] In a wireless communication system, for example, in a new radio (NR) system, a user equipment (UE) can establish a protocol data unit (PDU) session with a data network (DN) network element through a user plane function (UPF) network element. The PDU session provides data transmission services between the UE and the DN network element. In order to support the UE to transmit data simultaneously between 3GPP and Non-3GPP access, a quick UDP internet connections (QUIC) protocol equivalent to TCP is used to establish a QUIC connection between the UE and the UPF network element. Each connection can have different paths carried on the 3GPP and Non-3GPP access paths respectively. The QUIC protocol also has a multi-stream multiplexing feature and can transmit data of multiple streams at the same time.

[0005] In some current designs, the QUIC protocol is being considered for integration between the UE and the RAN to leverage its multi-stream multiplexing and multipath capabilities. However, the existing QoS mapping mechanism cannot meet the differentiated transmission requirements of QUIC-carried data. Therefore, designing a new QoS mapping mechanism is a challenge.

[0006] Summary of the Invention

[0007] The present application provides a data transmission method, apparatus, and system for designing a QoS mapping mechanism for the QUIC protocol between a UE and an access network device to better transmit QUIC-like traffic.

[0008] In a first aspect, the present application provides a data transmission method, which can be applied to an access network device, wherein at least one tunnel exists between the access network device and a terminal device, the tunnel includes at least one flow, and the at least one flow is used to transmit data. The method may include: obtaining mapping information, wherein the mapping information is used to indicate a mapping relationship between the tunnel, a data radio bearer (DRB), and a quality of service (QoS) flow; sending the mapping information to the terminal device; and performing data transmission with the terminal device based on the mapping information. For example, the access network device receives an uplink data packet from the terminal device based on the mapping information, and / or the access network device sends a downlink data packet to the terminal device based on the mapping information.

[0009] Through the above scheme, at least one tunnel can be introduced between the terminal device and the access network device for data transmission. Different streams in the tunnel can be used to carry different contents in the upper-layer data, such as frames or code pieces of different clarity of videos, different types of upper-layer data such as voice, video, data, or data with different transmission requirements of upper-layer data. The upper-layer data can be "diverted" or identified according to different requirements, and QoS management of the data transmitted in the tunnel can be implemented based on the mapping information, so as to perform differentiated transmission in the corresponding DRB and QoS streams to ensure the service experience of the application.

[0010] In one possible implementation, the at least one tunnel uses a target transport layer network protocol, and the data transmission with the terminal device based on the mapping information includes: transmitting data packets using the target transport layer network protocol between the terminal device and the at least one tunnel based on the mapping information. Exemplarily, the target transport layer network protocol may include a Quick UDP Internet Connection (QUIC) protocol.

[0011] Through the above scheme, the target transport layer network protocol is adopted to realize the carrying of different contents in the upper layer data, such as frames or code pieces of different clarity of videos, different types of upper layer data such as voice, video, data, or data with different transmission requirements of upper layer data. The upper layer data can be "diverted" or identified according to different requirements. The access network equipment can implement QoS management of tunnel protocol data packets based on the mapping information, so as to perform differentiated transmission in the corresponding DRB and QoS flow, and provide guarantee for the service experience of the application.

[0012] In one possible implementation, the data transmission with the terminal device according to the mapping information includes: for each tunnel of the at least one tunnel, transmitting the data packets of the tunnel on the target DRB according to the mapping information, wherein the data packets of the tunnel include data packets of at least one flow of the tunnel, and the data packets of the at least one flow carry data of at least one QoS flow.

[0013] Through the above solution, the access network device can map the tunnel data packets to the corresponding DRB based on the mapping information, so as to perform differentiated transmission in the corresponding DRB and QoS flow, thereby ensuring the service experience of the application. It should be understood that in the embodiment of the present application, the data packets of at least one flow can be data frames of at least one flow, and the embodiment of the present application does not limit the data format of the flow.

[0014] The mapping information in the embodiment of the present application can be implemented in a variety of flexible ways. In different implementations, the implementation details of data transmission between the access network device and the terminal device vary. The following examples are provided to illustrate:

[0015] In Example 1, at least one flow of the tunnel includes a first flow, the mapping information includes a mapping relationship between a first QoS flow and the first flow, and a mapping relationship between the first flow and a first DRB, and the first flow is carried on the first DRB. If the tunnel adopts a target transport layer network protocol, the target DRB of the tunnel may include the first DRB.

[0016] This solution allows QoS flow data to be encapsulated in an appropriate primary flow. This allows the primary flow to be transmitted over the appropriate DRB, ultimately achieving differentiated transmission of application data and ensuring a guaranteed service experience. The 1:1 mapping between QoS flows and primary flows eliminates the need to carry the QFI in the corresponding transmitted data packets, simplifying the complexity of tunneling protocols and flow packets.

[0017] Among them, for downlink data transmission, the data transmission with the terminal device according to the mapping information includes: receiving the downlink data packet of the first QoS flow from the core network device; according to the mapping information, encapsulating the payload data of the downlink data packet of the first QoS flow in the downlink data packet of the first flow. And sending the downlink data packet of the first flow through the first DRB. This solution can map and encapsulate the data of the downlink QoS flow sent to the terminal device into the data of the first flow, and transmit the first flow data encapsulated with the QoS flow data on the DRB, thereby realizing differentiated identification and transmission of downlink data, and providing transmission guarantee for application experience.

[0018] For uplink data transmission, according to the mapping information, data transmission with the terminal device may include: receiving the uplink data packet of the first flow through the first DRB according to the mapping information; encapsulating the payload data of the uplink data packet of the first flow in the uplink data packet of the first QoS flow; and sending the uplink data packet of the first QoS flow to the core network device. This solution can map and encapsulate the data of the uplink QoS flow sent by the terminal device to the data of the first flow, and transmit it on the corresponding DRB, thereby achieving differentiated identification and transmission of uplink data, providing transmission guarantee for application experience.

[0019] In Example 2, at least one flow of the tunnel includes a first flow, the mapping information includes a mapping relationship between multiple QoS flows and the first flow, and a mapping relationship between the first flow and a first DRB, and the first flow is carried on the first DRB. If the tunnel adopts a target transport layer network protocol, the target DRB of the tunnel may include the first DRB.

[0020] Through the above solution, multiple QoS flows can be mapped to the first flow. When the first flow is transmitted over a DRB, it can be transmitted over the appropriate DRB, ultimately achieving differentiated transmission of application data and ensuring a guaranteed service experience. In this solution, the n:1 mapping relationship between QoS flows and first flows can improve the transmission efficiency based on the target transport layer protocol between terminal devices and access network devices, reducing the number of first flows and context resources maintained by the protocol.

[0021] The multiple QoS flows include a first QoS flow and a second QoS flow. For downlink data transmission, according to the mapping information, data transmission with the terminal device may include: receiving a downlink data packet of the first QoS flow, the downlink data packet of the first QoS flow including the identifier of the first QoS flow; encapsulating the payload data of the downlink data packet of the first QoS flow in the downlink data packet of the first flow according to the mapping information, and sending the downlink data packet of the first flow through the first DRB; or receiving a downlink data packet of the second QoS flow, the downlink data packet of the second QoS flow including the identifier of the second QoS flow; encapsulating the payload data of the downlink data packet of the second QoS flow in the downlink data packet of the first flow according to the mapping information, and sending the downlink data packet of the first flow through the first DRB. This solution can map and encapsulate the data of multiple downlink QoS flows sent to the terminal device into the data of the first flow, and transmit the first flow data encapsulated with the data of multiple QoS flows on the DRB, thereby achieving differentiated identification and transmission of downlink data, providing transmission guarantee for application experience, and reducing the number of first flows and context resources maintained by the protocol.

[0022] For uplink data transmission, based on the mapping information, data transmission with the terminal device may include: receiving an uplink data packet of the first flow through the first DRB according to the mapping information; wherein, if the uplink data packet of the first flow includes an identifier of a first QoS flow, the method further includes: encapsulating the payload data of the uplink data packet of the first flow into an uplink data packet of the first QoS flow according to the mapping information, and sending the uplink data packet of the first QoS flow to the core network device; or, if the uplink data packet of the first flow includes an identifier of a second QoS flow, the method further includes: encapsulating the payload data of the uplink data packet of the first flow into an uplink data packet of the second QoS flow according to the mapping information, and sending the uplink data packet of the second QoS flow to the core network device. This solution can map and encapsulate data of multiple uplink QoS flows sent by the terminal device into data of the first flow and transmit it on the corresponding DRB, thereby achieving differentiated identification and transmission of uplink data and providing transmission guarantee for application experience. Example 3, the mapping information includes a mapping relationship between the tunnel and the first QoS flow, and a mapping relationship between the tunnel and the first DRB, and the data of the tunnel is carried on the first DRB. Among them, if the tunnel adopts the target transport layer network protocol, the target DRB of the tunnel may include the first DRB.

[0023] Through the above solution, individual QoS flows can be mapped to tunnels, and tunnel protocol packets can be transmitted over the DRB. This allows for the transmission of QoS flows over appropriate DRBs, ultimately achieving differentiated transmission of application data and ensuring a guaranteed service experience. In this solution, the 1:1 mapping relationship between QoS flows and tunnels can improve the transmission efficiency of the target transport layer protocol between terminal devices and access network devices, reduce the number of first flows and context resources maintained by the protocol, and simplify the complexity of the protocol between terminal devices and access network devices.

[0024] Among them, for downlink data transmission, according to the mapping information, data transmission with the terminal device may include: receiving the downlink data packet of the first QoS flow from the core network device; encapsulating the payload data of the downlink data packet of the first QoS flow in the downlink data packet of the tunnel according to the mapping information; and sending the downlink data packet of the tunnel through the first DRB. This solution can map and encapsulate the data of the downlink QoS flow sent to the terminal device into the data of the tunnel, and transmit it on the corresponding DRB, thereby realizing differentiated identification and transmission of downlink data, providing transmission guarantee for application experience.

[0025] For uplink data transmission, based on the mapping information, data transmission with the terminal device may include: receiving the uplink data packet of the tunnel through the first DRB according to the mapping information; encapsulating the payload data of the uplink data packet of the tunnel into the uplink data packet of the first QoS flow; and sending the uplink data packet of the first QoS flow to the core network device. This solution can map and encapsulate the data of the uplink QoS flow sent by the terminal device into the data packet of the tunnel and transmit it on the corresponding DRB, thereby achieving differentiated identification and transmission of uplink data and providing transmission guarantee for application experience.

[0026] In Example 4, the mapping information includes a mapping relationship between the tunnel and a first DRB, and a mapping relationship between a first flow in the tunnel and a first QoS flow, and data of the tunnel is carried on the first DRB. If the tunnel adopts a target transport layer network protocol, the target DRB of the tunnel may include the first DRB.

[0027] This solution provides refined data transmission management based on tunnels and tunnel flows. The DRB transmits service data for flows and QoS flows carried in tunnel protocol packets, ultimately achieving differentiated transmission of application data and ensuring a guaranteed service experience. In this solution, the 1:1 mapping relationship between DRBs and tunnels enables mapping between QoS flows and tunnel flows, improving transmission efficiency based on the target transport layer protocol between terminal devices and access network equipment.

[0028] Among them, for downlink data transmission, according to the mapping information, data transmission with the terminal device may include: receiving the downlink data packet of the first QoS flow from the core network device; according to the mapping information, encapsulating the payload data of the downlink data packet of the first QoS flow in the downlink data packet of the first flow in the tunnel; and sending the downlink data packet of the first flow in the tunnel through the first DRB. This solution can map and encapsulate the data of the downlink QoS flow sent by the terminal device into the data packet of the flow in the tunnel, and transmit it on the corresponding DRB, thereby realizing differentiated identification and transmission of uplink data, and providing transmission guarantee for application experience.

[0029] For uplink data transmission, according to the mapping information, data transmission with the terminal device may include: receiving the uplink data packet of the first flow in the tunnel through the first DRB according to the mapping information; encapsulating the payload data of the uplink data packet of the first flow in the tunnel into the uplink data packet of the first QoS flow; and sending the uplink data packet of the first QoS flow to the core network device. This solution can map and encapsulate the data of the uplink QoS flow sent by the terminal device into the data packet of the flow in the tunnel, and transmit it on the corresponding DRB, thereby realizing differentiated identification and transmission of uplink data, providing transmission guarantee for application experience.

[0030] In a second aspect, the present application provides a data transmission method, which can be applied to a terminal device, wherein at least one tunnel exists between the terminal device and an access network device, the tunnel includes at least one flow, and the at least one flow is used to transmit data. The method includes: receiving mapping information, wherein the mapping information is used to indicate a mapping relationship between the tunnel, a data radio bearer (DRB), and a quality of service (QoS) flow; and performing data transmission with the access network device based on the mapping information. For example, the terminal device sends an uplink data packet to the access network device based on the mapping information, and / or receives a downlink data packet from the access network device based on the mapping information.

[0031] In one possible implementation, the at least one tunnel uses a target transport layer network protocol, and the data transmission with the access network device based on the mapping information includes: transmitting data packets using the target transport layer network protocol between the access network device and the access network device based on the mapping information. Exemplarily, the target transport layer network protocol may include a Quick UDP Internet Connection (QUIC) protocol.

[0032] In one possible implementation, the data transmission with the access network device based on the mapping information includes: for each tunnel of the at least one tunnel, transmitting the data packets of the tunnel on the target DRB according to the mapping information, wherein the data packets of the tunnel include data packets of at least one flow of the tunnel, and the data packets of the at least one flow carry data of at least one QoS flow.

[0033] The mapping information in the embodiment of the present application can be implemented in a variety of flexible ways. In different implementations, the implementation details of data transmission between the access network device and the terminal device vary. The following examples are provided to illustrate:

[0034] In Example 1, at least one flow of the tunnel includes a first flow, the mapping information includes a mapping relationship between a first QoS flow and the first flow, and a mapping relationship between the first flow and a first DRB, and the first flow is carried on the first DRB. If the tunnel adopts a target transport layer network protocol, the target DRB of the tunnel may include the first DRB.

[0035] Among them, for downlink data transmission, data transmission with the access network device according to the mapping information may include: receiving the downlink data packet of the first stream through the first DRB according to the mapping information; decapsulating the downlink data packet, and delivering the payload of the downlink data packet to the upper layer protocol.

[0036] For uplink data transmission, data transmission with the access network device according to the mapping information may include: the party sending an uplink data packet according to the mapping information, including: obtaining data submitted by the upper layer protocol, and encapsulating the data in the payload of the uplink data packet of the first flow according to the mapping information; and sending the uplink data packet through the first DRB.

[0037] Example 2: At least one flow of the tunnel includes a first flow, and the mapping information includes a mapping relationship between multiple QoS flows and the first flow, and a mapping relationship between the first flow and a first DRB, and the first flow is carried on the first DRB.

[0038] Among them, the multiple QoS flows include a first QoS flow and a second QoS flow. For downlink data transmission, data transmission with the access network device according to the mapping information may include: receiving the downlink data packet of the first flow through the first DRB according to the mapping information, the downlink data packet including the identifier of the first QoS flow or the identifier of the second QoS flow; decapsulating the downlink data packet and delivering the payload of the downlink data packet to the upper layer protocol.

[0039] For uplink data transmission, data transmission with the access network device according to the mapping information may include: obtaining data submitted by the upper layer protocol, and encapsulating the data in the payload of the uplink data packet of the first flow according to the mapping information, the uplink data packet including the identifier of the first QoS flow or the identifier of the second QoS flow; sending the uplink data packet of the first flow through the first DRB.

[0040] Example 3: The mapping information includes a mapping relationship between the tunnel and the first QoS flow, and a mapping relationship between the tunnel and the first DRB, and the data of the tunnel is carried on the first DRB.

[0041] Among them, for downlink data transmission, data transmission with the access network device according to the mapping information may include: receiving the downlink data packet of the tunnel through the first DRB according to the mapping information; decapsulating the downlink data packet of the tunnel, and delivering the payload of the downlink data packet to the upper layer protocol.

[0042] For uplink data transmission, data transmission with the access network device according to the mapping information includes: obtaining data submitted by the upper layer protocol, and encapsulating the data in the payload of the uplink data packet of the tunnel according to the mapping information; and sending the uplink data packet through the first DRB.

[0043] Example 4: The mapping information includes a mapping relationship between the tunnel and the first DRB, and a mapping relationship between the first flow in the tunnel and the first QoS flow, and the data of the tunnel is carried on the first DRB.

[0044] Among them, for downlink data transmission, data transmission with the access network device according to the mapping information includes: receiving the downlink data packet of the first flow in the tunnel through the first DRB according to the mapping information; decapsulating the downlink data packet of the first flow in the tunnel, and delivering the payload of the downlink data packet to the upper layer protocol.

[0045] For uplink data transmission, data transmission with the access network device according to the mapping information includes: obtaining data submitted by the upper layer protocol, and encapsulating the data in the payload of the uplink data packet of the first flow encapsulated in the tunnel according to the mapping information; and sending the uplink data packet through the first DRB.

[0046] In the third aspect, the present application provides a data transmission method, which can be applied to an access network device, wherein there is at least one tunnel between the access network device and the terminal device, the tunnel includes at least one flow, and the at least one flow is used to transmit data. The method may include: obtaining mapping information, wherein the mapping information is used to indicate the mapping relationship between the tunnel, the data radio bearer DRB, and the quality of service QoS flow; sending the mapping information to the terminal device; for each tunnel in the at least one tunnel, transmitting the data packet of the tunnel on the target DRB according to the mapping information, wherein the data packet of the tunnel includes the data packet of at least one flow of the tunnel, and the data packet of the at least one flow carries the data of at least one QoS flow. For specific implementation details, please refer to any possible implementation method for the first aspect above, which will not be repeated here.

[0047] In the fourth aspect, an embodiment of the present application provides a data transmission method, which can be applied to a terminal device, wherein there is at least one tunnel between the access network device and the terminal device, the tunnel includes at least one flow, and the at least one flow is used to transmit data. The method may include: receiving mapping information, wherein the mapping information is used to indicate the mapping relationship between the tunnel, the data radio bearer DRB, and the quality of service QoS flow; for each tunnel in the at least one tunnel, according to the mapping information, transmitting the data packet of the tunnel on the target DRB, wherein the data packet of the tunnel includes the data packet of at least one flow of the tunnel, and the data packet of the at least one flow carries the data of at least one QoS flow. For specific implementation details, please refer to any possible implementation method for the second aspect above, which will not be repeated here.

[0048] In a fifth aspect, the present application provides a communication device comprising at least one processor and an interface circuit, wherein the interface circuit is used to provide data or code instructions to the at least one processor, and the at least one processor is used to implement the method described in the first aspect and any possible design of the first aspect through a logic circuit or executing code instructions, or implement the method described in the second aspect and any possible design of the second aspect, or implement the method described in the third aspect and any possible design of the third aspect, or implement the method described in the fourth aspect and any possible design of the fourth aspect through a logic circuit or executing code instructions.

[0049] In a sixth aspect, an embodiment of the present application provides a communication system, comprising a communication device for implementing the method described in the first aspect and any possible design of the first aspect, or comprising a communication device for implementing the method described in the third aspect and any possible design of the third aspect, a communication device for implementing the method described in the second aspect and any possible design of the second aspect, or a communication device for implementing the method described in the fourth aspect and any possible design of the fourth aspect.

[0050] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a program code. When the program code is run on a computer, the computer executes the method described in the first aspect and any possible design of the first aspect, or, when the program code is run on a computer, the computer executes the method described in the second aspect and any possible design of the second aspect, or, when the program code is run on a computer, the computer executes the method described in the third aspect and any possible design of the third aspect, or, when the program code is run on a computer, the computer executes the method described in the fourth aspect and any possible design of the fourth aspect.

[0051] In an eighth aspect, an embodiment of the present application provides a computer program product. When the computer program product is run on a computer, the computer executes the method described in the first aspect and any possible design of the first aspect, or executes the method described in the second aspect and any possible design of the second aspect, or executes the method described in the third aspect and any possible design of the third aspect, or executes the method described in the fourth aspect and any possible design of the fourth aspect.

[0052] Based on the implementations provided in the above aspects, the embodiments of the present application can be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figures 1(a) and 1(b) show schematic diagrams of the architecture of a communication system to which embodiments of the present application are applicable;

[0054] FIG2 shows a schematic diagram of the architecture of a protocol stack;

[0055] FIG3 is a schematic diagram showing the encapsulation mode of a QUIC data packet;

[0056] FIG4 shows a schematic diagram of a QUIC packet frame;

[0057] FIG5 shows a schematic diagram of the architecture of a protocol stack;

[0058] FIG6 shows a schematic diagram of the principle of QoS mapping;

[0059] FIG7 shows a schematic diagram of a QoS mapping relationship;

[0060] FIG8 is a schematic diagram showing a flow chart of a data transmission method according to an embodiment of the present application;

[0061] FIG9 is a schematic diagram showing a session establishment process according to an embodiment of the present application;

[0062] FIG10 shows a schematic diagram of a QoS mapping model;

[0063] 11 and 12 respectively illustrate a downlink data transmission process and an uplink data transmission process corresponding to a first embodiment of the present application;

[0064] FIG13 shows a schematic diagram of another QoS mapping model;

[0065] 14 and 15 respectively illustrate the downlink data transmission process and the uplink data transmission process corresponding to the second embodiment of the present application;

[0066] FIG16 and FIG17 respectively illustrate the downlink data transmission process and the uplink data transmission process corresponding to the third embodiment of the present application;

[0067] FIG18 and FIG19 respectively show the downlink data transmission process and the uplink data transmission process corresponding to the fourth embodiment of the present application;

[0068] FIG20 shows a schematic structural diagram of a communication device;

[0069] FIG21 shows a schematic structural diagram of another communication device. DETAILED DESCRIPTION

[0070] To meet the challenges of wireless broadband technology and maintain the leading edge of the Third Generation Partnership Project (3GPP) network, the 3GPP standards group has developed the Next Generation System (NGS) architecture, known as the 5G network architecture. This architecture not only supports access to the 5G core network (CN) using 3GPP-defined radio access technologies (such as Long Term Evolution (LTE) and 5G Radio Access Network (RAN)), but also supports access to the 5G core network using non-3GPP access technologies via the non-3GPP interworking function (N3IWF) or the next generation packet data gateway (ngPDG).

[0071] Figure 1(a) is a schematic diagram of a 5G network architecture based on a service-oriented architecture. The 5G network architecture shown in Figure 1(a) may include access network equipment and core network equipment. The terminal device accesses the data network (DN) through the access network equipment and the core network equipment. Among them, the core network equipment includes but is not limited to some or all of the following network elements: authentication server function (AUSF) network element (not shown in the figure), unified data management (UDM) network element, unified data repository (UDR) network element, network storage function (NRF) network element (not shown in the figure), network expos network element (not shown in the figure), application function (AF) network element, policy control function (PCF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, binding support function (BSF) network element (not shown in the figure).

[0072] Terminal devices can be user equipment (UE), mobile stations, mobile terminal devices, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver functions, wearable devices, vehicles, urban air vehicles (such as drones and helicopters), ships, robots, robotic arms, smart home devices, etc.

[0073] Access network equipment can be a radio access network (RAN) device or a wireline access network (FAN) device. Among them, radio access network equipment includes 3GPP access network equipment, untrusted non-3GPP access network equipment and trusted non-3GPP access network equipment. 3GPP access network equipment includes but is not limited to: evolved NodeB (eNodeB) in LTE, next generation NodeB (gNB) in 5G mobile communication system, base station in future mobile communication system or module or unit that completes part of the functions of base station, such as centralized unit (CU), distributed unit (DU), etc. Untrusted non-3GPP access network equipment includes but is not limited to: untrusted non-3GPP access gateway or N3IWF device, untrusted wireless local area network (WLAN) access point (AP), switch, router. Trusted non-3GPP access network equipment includes but is not limited to: trusted non-3GPP access gateway, trusted WLAN AP, switch, router. Wired access network equipment includes but is not limited to: wireline access gateway, fixed telephone network equipment, switches, and routers.

[0074] Access network equipment and terminal devices can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of access network equipment and terminal devices.

[0075] The AMF network element is responsible for UE mobility management, including mobile state management, allocating temporary identities to UEs, and authenticating and authorizing UEs.

[0076] The SMF network element is responsible for the selection and reselection of UPF network elements, IP address allocation, bearer establishment, modification and release, and quality of service (QoS) control.

[0077] The UPF network element supports all or part of the following functions: interconnecting protocol data unit (PDU) sessions with the data network; packet routing and forwarding (for example, supporting uplink classification (Uplink classifier) ​​of traffic before forwarding to the data network); and data packet inspection.

[0078] The UDM network element is responsible for managing contract data and notifying the corresponding network element when the contract data is modified.

[0079] The UDR network element stores and retrieves contract data, policy data, and public architecture data; it provides access to relevant data for UDM, PCF, and NEF network elements. The UDR network element must implement different data access authentication mechanisms for different types of data, such as contract data and policy data, to ensure data access security. The UDR network element must be able to return a failure response with an appropriate cause value for illegal service-based operations or data access requests.

[0080] NEF network element is used to support the opening of capabilities and events.

[0081] The AF network element communicates application-side requirements to the network, such as QoS requirements or user status event subscriptions. The AF can be a third-party functional entity or an application service deployed by a carrier, such as the IP Multimedia Subsystem (IMS) voice call service. AF network elements include those within the core network (i.e., the carrier's AF network element) and third-party AF network elements (such as an enterprise's application server).

[0082] The PCF network element includes policy control functions such as billing for sessions and service flow levels, QoS bandwidth guarantee and mobility management, and terminal device policy decision-making. PCF network elements include access and mobility management policy control function (AM PCF) network element and session management policy control function (SM PCF) network element. Among them, the AM PCF network element is used to formulate AM policies for terminal devices. The AM PCF network element can also be called a policy control network element that provides services for terminal devices (PCF for a UE). The SM PCF network element is used to formulate session management policies (SM policies) for sessions. The SM PCF network element can also be called a policy control network element that provides services for sessions (PCF for a PDU session).

[0083] NRF network elements can be used to provide network element discovery capabilities, providing network element information corresponding to the network element type based on requests from other network elements. NRF also provides network element management services such as network element registration, update, and deregistration, as well as network element status subscription and push notification.

[0084] The BSF network element can provide BSF service registration / deregistration / update, NRF connection detection, session binding information creation, UE information acquisition, and session binding information query for duplicate IP addresses.

[0085] The AUSF network element is responsible for authenticating the UE to determine whether the UE is allowed to access the network.

[0086] A DN is a network located outside of a carrier network. A carrier network can connect to multiple DNs, and a variety of services can be deployed on the DN, providing data and / or voice services to terminal devices. For example, a DN is the private network of a smart factory. Sensors installed in the workshop can be terminal devices. The DN houses a sensor control server, which provides services to the sensors. Sensors can communicate with the control server, receive instructions from the control server, and transmit collected sensor data to the control server based on the instructions. Another example is a DN that is a company's internal office network. An employee's mobile phone or computer can be a terminal device, allowing them to access information and data resources on the company's internal office network.

[0087] In Figure 1(a), Npcf, Nufr, Nudm, Naf, Namf, and Nsmf are the service-oriented interfaces provided by the PCF, UDR, UDM, AF, AMF, and SMF, respectively, for invoking corresponding service-oriented operations. N1, N2, N3, N4, and N6 are interface serial numbers, and their meanings are as follows:

[0088] 1) N1: The interface between AMF and terminal devices, which can be used to deliver non-access stratum (NAS) signaling (such as QoS rules from AMF) to terminal devices.

[0089] 2) N2: The interface between AMF and access network equipment, which can be used to transmit radio bearer control information from the core network side to the access network equipment.

[0090] 3) N3: The interface between the access network equipment and UPF, mainly used to transmit uplink and downlink user plane data between the access network equipment and UPF.

[0091] 4) N4: The interface between SMF and UPF can be used to transmit information between the control plane and the user plane, including controlling the issuance of forwarding rules, QoS rules, traffic statistics rules, etc. for the user plane and reporting information on the user plane.

[0092] 5) N6: Interface between UPF and DN, used to transmit uplink and downlink user data flows between UPF and DN.

[0093] Figure 1(b) is a schematic diagram of a 5G network architecture based on point-to-point interfaces. The functions of the network elements in Figure 1(a) can be referred to for the functions of the corresponding network elements, and will not be repeated here. The main difference between Figure 1(b) and Figure 1(a) is that the interfaces between the control plane network elements in Figure 1(a) are service-oriented interfaces, while the interfaces between the control plane network elements in Figure 1(b) are point-to-point interfaces.

[0094] In the architecture shown in Figure 1(b), the interface names and functions between the various network elements are as follows:

[0095] 1) For the meanings of the N1, N2, N3, N4 and N6 interfaces, please refer to the above description.

[0096] 2) N5: The interface between the AF network element and the PCF network element, which can be used to issue application service requests and report network events.

[0097] 3) N7: The interface between PCF network element and SMF network element, which can be used to issue PDU session granularity and service data flow granularity control strategy.

[0098] 4) N8: The interface between the AMF network element and the UDM network element, which can be used by the AMF network element to obtain access and mobility management related contract data and authentication data from the UDM network element, and the AMF network element to register terminal device mobility management related information with the UDM network element.

[0099] 5) N9: User plane interface between UPF network elements, used to transmit uplink and downlink user data flows between UPF network elements.

[0100] 6) N10: The interface between the SMF network element and the UDM network element, which can be used by the SMF network element to obtain session management related contract data from the UDM network element, and the SMF network element to register terminal device session related information with the UDM network element.

[0101] 7) N11: The interface between the SMF network element and the AMF network element, which can be used to transmit PDU session tunnel information between the access network device and the UPF, transmit control messages sent to the terminal device, transmit wireless resource control information sent to the access network device, etc.

[0102] 8) N15: The interface between the PCF network element and the AMF network element, which can be used to issue terminal device policies and access control related policies.

[0103] 9) N35: The interface between the UDM network element and the UDR network element, which can be used by the UDM network element to obtain user contract data information from the UDR network element.

[0104] 10) N36: Interface between PCF network element and UDR network element, which can be used by PCF network element to obtain policy-related contract data and application data-related information from UDR network element.

[0105] It is understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network element or function can be implemented by a single device, or by multiple devices, or can be a functional module within a single device, and this is not specifically limited in the embodiments of the present application.

[0106] The mobility management network element, session management network element, data management network element, and network storage function network element in this application can be the AMF network element, SMF network element, UDM network element, and NRF network element in the 5G system, respectively, or can be a network element with the functions of the above-mentioned AMF network element, SMF network element, UDM network element, and NRF network element in future communications such as 6G networks. This application is not limited to this. In the embodiments of this application, an example is described in which the AMF network element, SMF network element, UDM network element, and NRF network element are the mobility management network element, session management network element, data management network element, and network storage function network element, respectively. In addition, the AMF network element, SMF network element, UDM network element, and NRF network element are referred to as AMF, SMF, UDM, and NRF, respectively.

[0107] For ease of explanation, the embodiments of the present application are described using a base station and a UE as specific examples of an access network device and a terminal device, respectively. Any base station and UE appearing in any subsequent location can be replaced by an access network device and a terminal device, respectively.

[0108] To facilitate understanding of the content of this application, the relevant background involved in the embodiments of this application is first introduced below.

[0109] 1. Quick UDP internet connections (QUIC) protocol:

[0110] The QUIC protocol is a transport protocol equivalent to the Transmission Control Protocol (TCP). As shown in the protocol stack structure in Figure 2, the QUIC protocol is carried on the UDP protocol and incorporates the advantages of the HTTP / 2 API, TLS, and TCP during its design. Its goal is to optimize overall latency and throughput, and improve performance during network handoffs.

[0111] A data packet using the QUIC protocol can be called a QUIC data packet. The encapsulation mode of the QUIC data packet is shown in Figure 3, including the header and payload (or payload) of the data packet. It follows the principle of encrypting the payload and encrypting the header as much as possible to avoid problems such as parsing and intercepting network traffic by network middleware, thereby enhancing the security of data transmission.

[0112] Among them, the header of the QUIC data packet includes a UDP header and a common header, for example, including at least one public flag, a connection ID (CID), a QUIC version, a sequence number, etc. The CID can be used to associate data with the same link.

[0113] The payload portion of a QUIC packet is an encrypted ciphertext that can encapsulate frame data of multiple streams. The frame may include type, stream identifier, offset value, data length, stream payload (e.g., including stream data), etc. For example, as shown in FIG4 , taking the terminal device and the server as the sender and receiver of the QUIC packet, respectively, for the QUIC connection between the terminal device and the server, QUIC packet 1, QUIC packet 2, and QUIC packet 3 can be associated based on CID1. A certain frame of QUIC packet 1 (e.g., represented as 2QUIC frame) can encapsulate data of streams 1 and 2, a certain frame of QUIC packet 2 (e.g., represented as 3QUIC frame) can encapsulate data of streams 1, 2, and 3, and a certain frame of QUIC packet 3 (e.g., represented as 1QUIC frame) can encapsulate data of stream 2.

[0114] It should be understood that Figures 3 and 4 are merely examples of the QUIC packet format and are not intended to be limiting. The width of the rectangular boxes is merely an example and does not represent the length of the contents within the packet. For example, in a specific implementation, a QUIC packet can be either a long header packet or a short header packet. A long header packet contains source and destination CID fields. The destination CID is specified by the receiver and is used to provide stable routing for the packet. The source CID is set by the peer end as the destination CID. These fields can be used to set the CID for a new connection. A short header packet contains only the destination CID and omits the explicit length. The length of the destination CID field is assumed to be known to the peer end.

[0115] It is worth noting that in an embodiment of the present application, the above-mentioned QUIC protocol can be used as the target transport layer network protocol to establish a QUIC connection (or QUIC tunnel, see details below) between the terminal device and the access network device. The QUIC connection may include at least one stream, and the at least one stream can be used to transmit data. Each stream in the QUIC connection can be carried by a stream or a datagram, and the data frame transmitted by each stream is contained in a QUIC data packet. The QUIC data packet sent from the terminal device to the access network device can be called an uplink data packet, and the uplink data packet can include uplink data frames of one or more streams. The QUIC data packet sent from the access network device to the terminal device can be called a downlink data packet, and the downlink data packet can include downlink data frames of one or more streams.

[0116] When the terminal device or access network device acts as the transmitter, the target data to be transmitted through the stream can be encapsulated in the payload of the data frame of the corresponding stream, and then the data frame of the stream can be encapsulated in a QUIC data packet, and the QUIC data packet can be sent to the other end. Correspondingly, when the access network device or terminal device acts as the receiver, it first decapsulates the QUIC data packet to obtain the data frame of the stream, and then decapsulates the data frame of the stream to obtain the corresponding target data. In the following, the data packet of the stream transmitted between the terminal device and the access network device is specifically a QUIC data packet containing the data frame of the stream. A QUIC data packet can contain one or more data frames, which will not be distinguished or described one by one in the following.

[0117] 2. QUIC Tunnel and CID:

[0118] Taking the terminal device and the server as the two endpoints using the QUIC protocol as an example, each QUIC connection between the terminal device and the server can also be called a QUIC tunnel. "Tunnel" and "connection" can be used interchangeably below. It can usually have a set of CIDs, represented as CIDs, and each CID can identify the QUIC tunnel.

[0119] Among them, CID can be independently selected by the terminal device, and each terminal device selects a CID for use by the other end. The main function of CID is to ensure that when the address of the underlying protocol (such as UDP protocol, IP protocol or lower-level protocol stack) changes, it will not cause a QUIC connection data packet to be transmitted to the wrong QUIC terminal device, and can support application (APP) unaware connection migration. The terminal device can use a special implementation (and possibly special deployment) method to select the CID, which will enable the data packet with the CID to be routed back to the terminal device and correctly identified when received.

[0120] End devices can maintain a set of CIDs received from peers, each of which can be used to send QUIC packets. End devices can restrict the use of CIDs, for example, allowing a CID to only be used to send packets from the same local address to the same destination address. When the address changes, the CID needs to be updated.

[0121] At any time during a QUIC connection with a server, a terminal device can change the CID it uses to interact with the peer to another available CID. When the peer migrates the connection, the CID published by the terminal device is consumed, meaning that the CID is no longer used. When a terminal device wants to stop using a CID, it can send a Revoke CID frame to the peer. Sending a Revoke CID frame means that the CID will not be used again and requests the peer to replace it with a new CID using a New CID frame.

[0122] For example, during the handshake, a QUIC packet with a long header sets the CID used by both peers. The source CID of each peer becomes the destination CID for packets sent to that peer. After processing the initial packet, each peer sets the destination CID field of subsequent packets to the value of the source CID field it received.

[0123] When an end device sends an initial packet without receiving an initial packet or retry packet from the server, it generates an unpredictable value to fill the Destination CID field of the initial packet it sends. The Destination CID must be at least 8 bytes long. The client on the end device must use the same Destination CID on a connection until it receives a packet from the server.

[0124] The client can choose a value to fill the Source CID field and set the Source CID Length field to indicate its length. The first 0-RTT packet sent by the client uses the same Source CID and Destination CID as the first Initial packet it sent.

[0125] After first receiving an Initial or Retry packet from the server, the client uses the Source CID provided by the server as the Destination CID for all subsequent packets it sends, including any 0-RTT packets. This means that the client may need to change the Destination CID field twice during connection establishment: once in response to a Retry packet from the server, and once in response to the Initial packet from the server. Once a client receives a valid Initial packet from the server, it MUST discard any subsequent packets received on that connection with a different Source CID value.

[0126] The client MUST change the Destination CID value in all subsequent packets it sends after receiving the first Initial or Retry packet. The server MUST set the Destination CID for all packets it sends based on the first Initial packet it receives. Any subsequent changes to the Destination CID MUST only be made via the value carried in the New CID frame; if a subsequent Initial packet contains a different Source CID, the packet MUST be discarded. This avoids the unpredictable consequences of stateless processing of multiple Initial packets with different Source CIDs.

[0127] In the embodiments of the present application, only the negotiation and use of the CID of the QUIC connection between the UE and the RAN are focused on, and the data packet format is not focused on.

[0128] 3. Access traffic steering, switching and splitting (ATSSS) rules:

[0129] The ATSSS rules specify the overall technical requirements for the offloading, migration and separation of access services in the core network of the 5G mobile communication network, including the new technical functional requirements of network elements such as PCF, AMF, SMF, UPF and NRF relative to 5G network functions and interfaces.

[0130] Access service offloading is a process of directing a flow. A new data flow selects an access network and transmits its traffic over the specified access network. Access service offloading is applicable between a 3rd Generation Partnership Project (3GPP) access and a non-3GPP access.

[0131] Access service migration is a flow migration process that migrates all traffic of an ongoing service flow from one access network to another, maintaining service flow continuity. Access service migration is applicable between a 3GPP access network and a non-3GPP access network.

[0132] Access service splitting involves splitting and dividing service data flows between multiple access networks. When traffic splitting (splitting) is applied to a data flow, some traffic within that flow is transmitted over one access, while other traffic within the same flow is transmitted over another access. Access service splitting is applicable between a 3GPP access and a non-3GPP access.

[0133] In an embodiment of the present application, the terminal device can control the diversion of services according to ATSSS rules. For example, the terminal device determines according to the ATSSS rules that the data flow of the service is transmitted only through 3GPP access technology, or is transmitted only through non-3GPP access technology, or is transmitted through both 3GPP access technology and non-3GPP access technology, that is, diverting the service through the two access technologies.

[0134] 4. Radio Bearer (RB):

[0135] A radio bearer is a general term for a series of protocol entities and configurations allocated by a base station to a UE. These include the radio resource control (RRC) or service data adaptation protocol (SDAP) protocol entity, the packet data convergence protocol (PDCP) entity, the radio link control (RLC) protocol entity, the medium access control (MAC) protocol entity, and a series of resources allocated by the physical layer (PHY). The protocol stack architecture is shown in Figure 5. Radio bearers are divided into data radio bearers (DRBs) and signaling radio bearers (SRBs). The former carries data, while the latter carries signaling messages.

[0136] In an embodiment of the present application, a DRB can carry at least one QUIC tunnel. Each QUIC tunnel can be associated with at least one CID.

[0137] 5. Protocol Data Unit (PDU) Session:

[0138] One of the key tasks of 5GS session management is to provide data connection to DN for terminal devices. In order to establish a connection between terminal devices and DN, a PDU session needs to be established. A PDU session is a logical connection between a terminal device and a specific DN, which provides the terminal device with a user plane connection to the DN. Among them, "PDU" is the basic user protocol type carried by the PDU session, which can be an IP data packet or an Ethernet frame, depending on the PDU session type. 5GS currently supports three PDU session types, including IP-based PDU session type, Ethernet PDU session type, and unstructured PDU session type. The "PDU" carried by the IP-based PDU session is an IP data packet, and the "PDU" carried by the Ethernet PDU session is an Ethernet frame. For unstructured PDU sessions, 5GS does not interpret the "PDU" it carries.

[0139] During the PDU session establishment process, the corresponding user plane connection between the terminal device and the DN will be activated. The user plane connection provides the transmission of PDUs between the terminal device and the DN, carrying actual data, such as voice and video. A terminal device can request to establish multiple PDU sessions simultaneously. These multiple PDU sessions can be connected to different DNs respectively. For example, if the UE requires both Internet connectivity and IMS services, a PDU session from the terminal device to the Internet and a PDU session from the terminal device to the IMS can be established simultaneously. In addition, a terminal device can also request to establish multiple PDU sessions to a single DN at the same time.

[0140] 6. Quality of service (QoS):

[0141] QoS aims to provide end-to-end service quality assurance tailored to the diverse needs of various services. QoS is a tool for effectively utilizing network resources, allowing different traffic types to compete unequally for network resources. Voice, video, and critical data applications receive priority service within network devices. Factors influencing network quality include bandwidth, latency, jitter, and packet loss rate, all of which can be used as QoS metrics.

[0142] Among them, QoS management is supported in both NSA (Non-Standalone) and SA (Standalone) networking, but in SA networking, the concept of bearer is not used between the base station and the core network. Instead, the evolved packet system (EPS) bearer in the NSA network becomes a QoS flow. Each QoS flow is identified by a QoS flow identifier (QoS flow ID, QFI). Within a PDU session, the QFI of each QoS Flow is unique. The core network will notify the base station of the identifier (5G QoS identifier, 5QI) corresponding to each QoS flow to determine its QoS attributes. The base station needs to map the QoS flow to the DRB. The QoS flow and the air interface wireless bearer can be a many-to-one mapping relationship or a one-to-one mapping relationship, as shown in Figure 6.

[0143] 7. QoS mapping rules:

[0144] Based on the protocol stack architecture shown in Figure 5, when data is transmitted between the base station and the UE, the functions of the SDAP protocol layer include the following two aspects:

[0145] (1) Add the QoS flow ID (QFI) to the data packet, and the receiver reads the QFI from the SDAP header of the data packet.

[0146] (2) Map one or more QoS flows to a DRB.

[0147] As shown in Figure 7, there can be multiple QoS flows with the same 5QI in the system, and the QoS flows with the same 5QI can be mapped to the same DRB. Alternatively, QoS flows with different 5QIs can be mapped to the same DRB.

[0148] The base station side needs to map the QoS Flow to the corresponding DRB so that downlink data can be sent to the UE through the corresponding bearer. For downlink data, when the QoS Flow passes through the SDAP layer, the SDAP layer maps each QoS Flow to the corresponding DRB based on the mapping relationship between the NR 5QI network management configuration value and the QoS class identifier (QCI).

[0149] To send data to the base station, the UE also needs to find the corresponding DRB. The current QoS mapping rule is based on a two-layer mapping: IP flow <-> QoS flow <-> DRB, as shown in Figure 6. For uplink data, when the IP flow from the upper application layer passes through the SDAP layer, the SDAP layer encapsulates the IP flow into the uplink data packet of the corresponding QoS flow based on the QoS mapping relationship and sends the uplink data packet to the base station via the DRB.

[0150] Due to the complexity of the protocol stack between the UE and the access network equipment (such as RAN), especially when transmitting traffic data similar to QUIC packets, the application layer multiplexes multiple streams on a QUIC packet. The existing QoS mapping mechanism cannot meet the differentiated transmission of QUIC-carried data. Therefore, after the introduction of the QUIC protocol, the QoS mapping rules need to be redesigned.

[0151] The embodiments of the present application provide a data transmission method, device and system for designing a QoS mapping mechanism for the QUIC protocol between the UE and the access network device to better transmit QUIC-like traffic. Among them, the method and the device are based on the same technical concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated. Moreover, in the various embodiments of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0152] It should be noted that, in the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.

[0153] Furthermore, unless otherwise specified, ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish between multiple objects, and are not used to limit the priority or importance of multiple objects. For example, the first access network device and the second access network device are only used to distinguish between different access network devices, rather than to indicate the difference in priority or importance of the two devices. For example, in some embodiments, the method steps performed by the first access network device and the second access network device can be interchangeable. For example, in a switching scenario, the first access network device can serve as the source access network device of the UE, and the second access network device can serve as the target access network device of the UE. Conversely, the first access network device can serve as the target access network device of the UE, and the second access network device can serve as the source access network device of the UE.

[0154] FIG8 shows a schematic flow chart of a data transmission method according to an embodiment of the present application.

[0155] As shown in FIG8 , the data transmission method may include the following steps:

[0156] S810: The access network device obtains mapping information.

[0157] In an embodiment of the present application, the mapping information may indicate a mapping relationship between a tunnel, a DRB, and a QoS flow. There may be at least one tunnel between the access network device and the terminal device, and any one of the at least one tunnel may include at least one flow that can be used to transmit data.

[0158] Among them, any tunnel of the at least one tunnel can adopt the target transport layer network protocol, and the target transport layer network protocol includes the QUIC protocol introduced above, or can include other transport layer network protocols similar to the QUIC protocol. For the convenience of description below, the target transport layer network protocol is referred to as the tunnel protocol, and the data packet adopting the target transport layer network protocol is called the tunnel protocol data packet, which can include data frames of one or more streams. When the QUIC protocol is adopted, the flow of the tunnel can be carried by a stream or a datagram.

[0159] For ease of distinction, in an embodiment of the present application, one or more data streams transmitted through a tunnel using a target transport layer network protocol between a terminal device and an access network device are referred to as streams. Tunnels and streams can be carried on the air interface DRB between the terminal device and the access network device. The encapsulation mode of the tunnel data packet or stream can be found in the previous description and will not be repeated here. The multiple data streams transmitted between the terminal device and the core network (such as a core network gateway device) are called QoS Flows. QoS Flows meet the corresponding QoS requirements. QoS flows include the air interface portion between the terminal device and the access network device and the portion between the access network device and the core network gateway device. The implementation of the mapping relationship between QoS Flow and tunnels, or flows in tunnels, or DRBs will be introduced below and will not be repeated here.

[0160] Before implementing S810, in an optional implementation, the terminal device may initiate a session establishment process and, during this session establishment process, negotiate tunnel information with the access network device, such as the tunnel's first address and tunnel attribute information. Alternatively, the network may initiate a session modification process, during which the access network device and the terminal device may negotiate tunnel information, such as the tunnel's first address and tunnel attribute information. Alternatively, the access network device may obtain mapping information during other processes, which is not limited in this embodiment of the present application.

[0161] For example, taking the process of establishing a session initiated by a terminal device as an example, as shown in FIG9 , the process of establishing a tunnel may include the following steps:

[0162] S901: The terminal device sends a session message to the SMF network element via the AMF network element. The session message may be a session establishment message, indicating the establishment of a session for the terminal device, such as a PDU session. Alternatively, the session message may be a session modification message, indicating the modification of a session, such as a PDU session.

[0163] Accordingly, the AMF network element can receive session messages from the terminal device and forward the session messages to the SMF network element. The "forwarding" here can be understood as "transparent transmission", that is, the AMF network element only converts the format of the session message from the terminal device to send the content that the terminal device expects to send to the SMF network element to the SMF network element. The AMF network element does not parse the session message from the terminal device. The description of "forwarding" below can be understood as "transparent transmission" and will not be distinguished or repeated one by one.

[0164] In an embodiment of the present application, the session message can be represented as a first non-access layer message, and the session message can include first indication information, and the first indication information can indicate that the terminal device supports the target transport layer network protocol, or the first indication information indicates that the terminal device supports multi-channel communication based on the target transport layer network protocol. The terminal device can send a session message to the AMF network element through the N1 interface. The AMF network element sends the session message to the SMF network element through the N11 interface. The SMF network element can receive the session message from the AMF network element and obtain the first indication information from the session message. The SMF network element can analyze whether the terminal device and the access network device support establishing a tunnel using the target transport layer network protocol based on the first indication information.

[0165] In an optional embodiment, the session message from the terminal device can be represented as a second non-access layer message, and the session message can include second indication information, and the second indication information indicates that a tunnel is to be established between the terminal device and the access network device. The second indication information can be an explicit indication or an implicit indication. In the case of an explicit indication, the second indication information can be, for example, a request indicator, indicating a request or need to establish a tunnel between the terminal device and the first access network device. In the case of an implicit indication, the second indication information can be, for example, a description of the service requirement. If the description information of the service requirement describes that the service on the terminal device side has a stable delay requirement, it can be regarded as an implicit indication that a tunnel using the target transport layer network protocol needs to be established between the terminal device and the access network device.

[0166] It should be understood that in the embodiment of the present application, the first indication information and the second indication information can be carried in the same message or in different messages, and the embodiment of the present application does not limit this.

[0167] S902: Implement contract processing, policy processing, authentication / authorization processing, user plane function processing, etc. between the terminal device, access network equipment, and multiple network elements of the core network (such as AMF network elements, SMF network elements, PCF network elements, and UDM network elements). Detailed implementation details can be found in the relevant standard documents of 3GPP and will not be repeated here.

[0168] S903: The SMF network element determines that a tunnel needs to be established between the terminal device and the access network device.

[0169] In an embodiment of the present application, the SMF network element may determine that a tunnel needs to be established between the terminal device and the access network device based on the content of the session message received from the terminal device in S901. For example, when the session message carries the second indication information, the SMF network element may determine that a tunnel needs to be established between the terminal device and the access network device based on the second indication information. Or for example, when the session message carries the first indication information, the SMF network element may also obtain the tunnel capability information of the access network device. If both the terminal device and the access network device can support the target transport layer network protocol, or both can support multi-channel communication based on the target transport layer network protocol, the SMF network element may determine that a tunnel needs to be established between the terminal device and the access network device.

[0170] Alternatively, the SMF network element may be the one that determines the need to establish a tunnel between the terminal device and the access network device through interaction with the terminal device, or the access network device, or other core network network elements during the implementation of S902. For example, during the implementation of S902, the SMF network element may also receive other request information from the terminal device, such as DNN or Slice information, etc. The SMF network element may determine the need to establish a tunnel between the terminal device and the access network device based on the DNN or Slice information. Or, for example, during the implementation of S902, the SMF network element may also determine the need to establish a tunnel between the terminal device and the access network device based on the policy information received from the PCF network element or the contract information received from the UDM network element.

[0171] S904: The SMF network element sends an Nx session message to the access network device via the AMF network element. Correspondingly, the access network device receives the Nx session message from the SMF network element.

[0172] In an embodiment of the present application, the SMF network element may send an N11 session message to the AMF network element through the N11 interface, and the N11 session message may carry tunnel address configuration indication information. The AMF network element sends an N2 session message to the access network device through the N2 interface, and the N2 session message may carry tunnel address configuration indication information. The tunnel address configuration indication information is used to request the access network device to configure the first address of the tunnel, or it can be understood that the tunnel address configuration indication information is used to instruct the access network device to configure the first address of the tunnel for the terminal device.

[0173] In an optional implementation, the tunnel address configuration indication information from the SMF network element can be expressed as the second indication information, and the second indication information indicates that the tunnel is established between the terminal device and the access network device. The second indication information can be carried in a fourth non-access layer message from the SMF network element. The fourth non-access layer message can be a newly added control plane message. The SMF network element can send the fourth non-access layer message to the AMF network element through the N11 interface, and the AMF network element can send the fourth non-access layer message to the access network device through the N2 interface.

[0174] In an optional implementation, the Nx session message from the SMF network element may also include QoS rules.

[0175] S905: The access network device configures the first address of the tunnel for the terminal device according to the relevant instruction information from the SMF network element.

[0176] In an optional implementation, the tunnel address configuration indication information from the SMF network element may be represented as fourth indication information, where the fourth indication information is used to indicate the first address of the configured tunnel. The access network device may also determine, based on the fourth indication information and the agreement of the target transport layer network protocol, that the default mode is an attribute of the tunnel, which may include, for example, any one of the following transmission modes: data packet mode, stream mode, or security mode.

[0177] In another optional implementation, the tunnel address configuration indication information from the SMF network element can be represented as third configuration information, and the third configuration information can include tunnel attribute information. When implementing S905, the access network device can also obtain tunnel attributes from the third configuration information. The attribute can include, for example, any of the following transmission modes: data packet mode, stream mode, or security mode.

[0178] S906: The access network device sends the first information to the terminal device. Correspondingly, the terminal device receives the first information and may feed back response information for the first information to the access network device.

[0179] In an embodiment of the present application, the first information may include a first address of the tunnel. In another optional implementation, the first information may also include attribute information of the tunnel, which may include, for example, any one of the following transmission modes: data packet mode, stream mode, or security mode.

[0180] S907: A tunnel using the target transport layer network protocol is established between the terminal device and the first access network device. Afterwards, the terminal device can transmit data with the access network device based on the tunnel, and the tunnel can be used to ensure the communication quality between the terminal device and the access network device.

[0181] In one embodiment, the terminal device may initiate S907 based on the received information. In another embodiment, the access network device may initiate S907 based on the received information. The specific implementation details of S907 can be found in the connection establishment process of the target transport layer network protocol, such as the connection establishment process of the QUIC protocol, and will not be repeated here.

[0182] S908: The first access network device feeds back an Nx session response message to the SMF network element via the AMF network element. Correspondingly, the SMF network element receives the Nx session response message from the first access network device.

[0183] S909: The SMF network element and other core network elements execute the remaining steps of establishing the PDU session. Detailed implementation details can be found in the relevant standard documents of 3GPP and will not be repeated here.

[0184] It should be understood that Figure 9 is only an example of the interaction process that may be involved in establishing a tunnel between a terminal device and an access network device and is not a limitation. In other embodiments, the terminal device may interact with the access network device and / or the core network element in other ways to exchange information related to establishing the tunnel, which will not be described in detail here. In an optional implementation, depending on the device capabilities, a tunnel using the target transport layer network protocol may also be established between the terminal device and different access network devices in a dual connection (DC) scenario or a mobile switching scenario, which will not be described in detail here.

[0185] At any time before the terminal device transmits data with the access network device based on the tunnel, the access network device may execute the above S810 to obtain mapping information.

[0186] For example, the access network device may obtain the mapping information from the Nx session message upon receiving it in S904. Alternatively, the access network device may obtain the mapping information from the exchanged information when interacting with other core network elements, or determine the mapping information based on the exchanged information. For example, the access network device may determine the mapping information based on QoS profile information from the core network. The embodiment of the present application does not limit the manner in which this mapping information is obtained.

[0187] S820: The access network device sends mapping information to the terminal device. Correspondingly, the terminal device receives the mapping information.

[0188] In the embodiment of the present application, the execution timing of S820 may be, for example, after S907 and before S908 as shown in FIG. 9 , or after S908 and before S909 . The embodiment of the present application does not impose any specific limitation.

[0189] The access network device may send the mapping information to the terminal device via access layer signaling (AS). The AS signaling may be newly added AS signaling between the access network device and the terminal device, or may be a reuse of existing AS signaling, such as carrying the mapping information in a reserved field of the existing AS signaling, or carrying the mapping information in a new cell, or replacing other cells in the existing AS signaling with the mapping information.

[0190] S830: The access network device and the terminal device perform data transmission based on the mapping information. For example, the access network device performs data transmission based on the mapping information. Similarly, the terminal device performs data transmission based on the mapping information with the access network device.

[0191] During specific implementation, the access network device may receive uplink data packets based on the mapping information, and / or send downlink data packets based on the mapping information. For example, the access network device may map data of a downlink QoS flow from the core network to one or more tunnel-based flows between the access network device and the terminal device, or map uplink data of one or more tunnel-based flows from the terminal device to a QoS flow.

[0192] Similarly, the terminal device may also send uplink data packets according to the mapping information, and / or receive downlink data packets according to the mapping information. Specifically, for example, the terminal device may receive and decapsulate a tunnel protocol data packet containing a downlink data frame based on a tunnel and containing one or more streams from the access network device according to the mapping information, or may encapsulate data submitted by the upper layer protocol in a tunnel protocol data packet containing an uplink data frame based on a tunnel and containing one or more streams according to the mapping information and send the data to the access network device.

[0193] In specific implementations, the mapping information can be implemented in a variety of ways. Depending on the different implementations of the mapping information, the mapping process during tunnel-based data transmission between the access network device and the terminal device may vary. For ease of understanding, the following describes different implementations in conjunction with the accompanying drawings and embodiments.

[0194] It is worth noting that, in the following text, the uplink data packet of the corresponding flow transmitted between the terminal device and the access network device based on the tunnel can replace the uplink data frame of the corresponding flow, and the downlink data packet of the corresponding flow can be replaced by the downlink data frame of the corresponding flow. The embodiment of the present application does not limit the format of the data transmitted by the tunnel flow. In addition, when implementing the mapping between the flow in the tunnel and the QoS flow, the identifier QFI of the corresponding QoS flow can be added to the header of the data frame of the flow in the tunnel, or added to the control information part of the data packet containing the data frame of the flow. For example, QFI1 can be added to the header of the flow frame in the tunnel carrying QoS flow data, or QFI can be added to the header of the tunnel protocol data packet that encapsulates the data frame of the tunnel flow, or QFI can be encapsulated in an independent tunnel protocol control information (such as the control frame of QUIC), and the control information and the data frame of the tunnel flow are encapsulated in the same tunnel protocol data packet. Since the embodiment of the present application does not limit the carrying position of QFI, the above examples are applicable to the different embodiments below, and the similarities will not be repeated below.

[0195] In the following examples, it is assumed that independent SDAP functionality is not required. For example, the security and reordering features of the original SDAP and PDCP air interface are no longer needed, or it is understood that the security and reordering features of the SDAP and PDCP layers are merged into a new air interface protocol layer (or it is understood that the new air interface protocol layer is directly above PDCP). This new protocol layer can be the QUIC layer, and other layer features of PDCP, such as IP header compression, are still retained. The mapping model in this case can be shown in Figure 10. Alternatively, it can be understood that the QoS flow or QFI terminates at the access network device, and the terminal device only perceives the Stream ID. That is, on the terminal device side, the flow in the tunnel is mapped 1:1 with the QoS flow. Data of different flows in the tunnel can be carried on different DRBs.

[0196] The examples are as follows:

[0197] (1) Method 1: The flows in the tunnel are mapped 1:1 to the QoS flows. The mapping information includes the mapping relationship between the QoS flows and the flows in the tunnel, and the mapping relationship between the flows in the tunnel and the DRB.

[0198] In this method 1, the mapping information includes the mapping relationship between a single QoS flow and a single flow in the tunnel, and the mapping relationship between a single flow in the tunnel and a DRB. A single flow in the tunnel can be identified by a Stream ID or a CID, which is not limited in this embodiment of the present application.

[0199] Taking the QUIC protocol as an example, in one example, the mapping information may include the following content:

[0200] Precedence=1

[0201] QUIC selection descriptor:

[0202] Stream ID#1 or CID#1 (including source CID and destination CID);

[0203] QFI=3;

[0204] DRB=#1.

[0205] This means that Stream#1 (CID#1 used by Stream#1) is mapped to QFI 3, and Stream ID#1 is transmitted on DRB#1.

[0206] In another example, the mapping information may include the following:

[0207] Precedence=1

[0208] QUIC selection descriptor:

[0209] Stream ID#1 or CID#1 (including source CID and destination CID);

[0210] QFI = 3; and

[0211] Precedence=1

[0212] QUIC selection descriptor:

[0213] QFI=3;

[0214] DRB=#1.

[0215] The access network device can separately send the mapping relationship between a single QoS flow and a single flow in the tunnel to the terminal device, or separately send the mapping relationship between a single QoS flow and a DRB to the terminal device. For example, the mapping relationship between a single QoS flow and a single flow in the tunnel is carried in one AS signaling, and the mapping relationship between a single QoS flow and a DRB is carried in another AS signaling. The embodiments of the present application do not limit the content of the mapping information and the method of sending the mapping information.

[0216] Based on the mapping information, when downlink data transmission is performed between the access network device and the terminal device, including when the access network device sends a tunnel protocol data packet to the terminal device, as shown in FIG11 , the following steps may be included:

[0217] S1101: A core network sends a downlink data packet of a first QoS flow to an access network device. Specifically, the core network may be a user plane gateway function of the core network. Exemplarily, the identifier of the first QoS flow may be QFI1. Accordingly, the access network device receives the downlink data packet of the first QoS flow.

[0218] S1102: The access network device encapsulates the payload data of the downlink data packet of the first QoS flow into the downlink data packet of the first flow according to the mapping information.

[0219] Taking the GTU-P protocol adopted on the core network side as an example, when implementing S1102, the access network device needs to first remove the GTU-P header and then, based on the mapping relationship between the QFI and the stream indicated by the mapping information, encapsulate the payload data of the downlink data packet of the first QoS flow into the downlink data packet / frame of the first flow, and include Stream ID#1 information in the frame header of the downlink data packet of the flow. At the same time, the frame is encapsulated in a tunnel protocol data packet, and the tunnel CID (e.g., represented as CID#1, including source CID#1 and destination CID#1) is used in the header of the tunnel protocol data packet.

[0220] S1103: The access network device sends the downlink data packet of the first stream to the terminal device through the first DRB corresponding to the first stream (for example, represented as DRB#1) according to the mapping relationship between the stream and the DRB indicated by the mapping information. Specifically, the access network device may be a tunnel protocol data packet that sends the downlink data packet of the first stream to the terminal device. Accordingly, the terminal device receives the downlink data packet of the first stream through the first DRB according to the mapping information, for example, receives the tunnel protocol data packet that contains the downlink data packet of the first stream.

[0221] S1104: The terminal device delivers the downlink data packet of the first flow received from the first DRB to the tunnel, decapsulates the downlink data packet of the first flow according to the mapping information, and delivers the payload of the downlink data packet to the upper layer protocol.

[0222] Specifically, the terminal device may deliver the tunnel protocol data packet containing the first-stream downlink data packet received from the first DRB to the tunnel, and then decapsulate the tunnel protocol data packet according to the mapping information to obtain the first-stream downlink data packet / frame, and deliver the payload of the first-stream downlink data packet / frame to the upper layer protocol.

[0223] Exemplarily, the upper layer protocol may be an IP protocol. When implementing S1104, the terminal device may demultiplex the payload data in the stream into multiple IP streams based on the mapping relationship between the stream and the IP stream, and deliver the data to the upper application layer. Alternatively, the terminal device may demultiplex the payload data in the stream into multiple IP streams based on the mapping relationship between the IP stream and the QFI, and the mapping relationship between the QFI and the stream, and deliver the data to the upper application layer. In this case, the intermediate mapping of the stream to the QFI, and the QFI to the IP stream, may be retained inside the terminal device. The embodiment of the present application does not require a large number of modifications to the mapping of the QFI to the IP stream, but only requires enhancement of the mapping process inside the terminal device. The mapping relationship between the stream and the IP stream may, for example, be sent by the access network device to the terminal device. Specifically, during the session establishment process, the mapping relationship between the stream and the IP stream may be carried in the PDU session acceptance message sent by the access network device to the terminal device; or during the tunnel establishment process, or after the tunnel is established, the access network device may send the mapping relationship between the above stream and the IP stream to the terminal device; or it may be sent by the core network device (such as the SMF network element) to the terminal device. The embodiment of the present application does not limit the implementation method of the terminal device obtaining the mapping relationship between the stream and the IP stream (direct or indirect mapping relationship), and it will not be repeated in the following embodiments.

[0224] Based on the mapping information, when uplink data transmission is performed between the access network device and the terminal device, including when the terminal device sends a tunnel protocol data packet to the access network device, as shown in FIG12 , the following steps may be included:

[0225] S1201: The terminal device obtains data delivered by the upper layer protocol, and encapsulates the data into the payload of the uplink data packet of the first flow according to the mapping information.

[0226] For example, the upper layer protocol may be an IP protocol. When implementing S1201, the terminal device may encapsulate the data delivered by the upper layer protocol in the frame data of the stream, i.e., encapsulate it in the payload of the first stream's uplink data packet / frame, and use the first stream's stream identifier, such as Stream ID, in the header of the first stream's uplink data packet / frame, based on the mapping relationship between the IP stream and the QFI, and the mapping relationship between the QFI and the stream, or based on the mapping relationship between the IP stream and the stream. The uplink data packet of the first stream is then encapsulated in a tunnel protocol data packet, and the CID of the tunnel (for example, represented as CID#1, including source CID#1 and target CID#1) is used in the header of the tunnel protocol data packet. A single stream in the tunnel may be identified by Stream ID. If a single tunnel contains only one stream, any tunnel identifier CID may identify the stream in the tunnel. If a single tunnel contains multiple streams, different CIDs may be used to identify different streams, and this embodiment of the present application does not limit this.

[0227] S1202: The terminal device sends an uplink data packet of the first flow to the access network device via the first DRB corresponding to the first flow, based on the mapping relationship between the stream and the DRB indicated by the mapping information. This includes sending a tunneling protocol data packet containing the uplink data packet / frame of the first flow. Correspondingly, the access network device receives the uplink data packet of the first flow via the first DRB, based on the mapping information. This includes receiving a tunneling protocol data packet containing the uplink data packet / frame of the first flow.

[0228] S1203: The access network device encapsulates the payload data of the uplink data packet of the first flow into the uplink data packet of the first QoS flow according to the mapping information.

[0229] For example, the identifier of the first QoS flow can be QFI1, and the uplink data packet of the first QoS flow can be, for example, a GTP-U data packet. The encapsulation method of the GTP-U data packet can be found in the relevant standard documents of 3GPP and will not be described here.

[0230] Among them, after the access network device receives the uplink data packet from the first DRB, specifically after receiving the tunnel protocol data packet from the first DRB and the tunnel protocol data packet contains the uplink data packet of the first flow, it can identify the first flow identifier or the tunnel identifier in the tunnel protocol data packet, and then encapsulate the payload data of the uplink data packet of the first flow (such as the payload part in the QUIC stream Frame) in the uplink data packet of the first QoS flow according to the mapping relationship between the stream and the QoS flow indicated by the mapping information, and at the same time add the identifier of the first QoS flow, such as QFI1, to the header of the uplink data packet of the first QoS flow (such as the GTP header).

[0231] S1204: The access network device sends the uplink data packet of the first QoS flow to the core network device. Correspondingly, the core network device receives the uplink data packet of the first QoS flow from the access network device.

[0232] Therefore, through the method shown in Figures 11 and 12 above, when the target transport layer network protocol is used for data transmission between the terminal device and the access network device, the air interface can identify the granularity of the stream flow in the tunnel, and then perform QoS management on the stream flow to perform differentiated transmission in the corresponding DRB and QoS flow.

[0233] (2) Mode 2: The flows in the tunnel are mapped 1:1 to the DRB. The mapping information includes the mapping relationship between multiple QoS flows and a single flow in the tunnel, and the mapping relationship between a single flow in the tunnel and the DRB.

[0234] In this second method, the access network device and the terminal device can exchange mapping information in the process of establishing a session in the manner shown in Figure 9. This process can be found in the relevant description of Figure 9 and will not be repeated here. The difference lies in that the content of the mapping information exchanged in method 2 is different from that in method 1. In this second method, the mapping information includes the mapping relationship between multiple QoS flows and a single flow in the tunnel, and the mapping relationship between a single flow in the tunnel and the DRB. A single flow in the tunnel can be identified by a Stream ID, or by a CID. This is not limited in the embodiments of the present application. Afterwards, data can be transmitted between the terminal device and the access network device in accordance with the content indicated by the mapping information.

[0235] In this second approach, the mapping model is shown in Figure 13. Data from multiple QoS flows can be transmitted within the same tunnel stream, and each DRB can carry data from one stream within the tunnel. In other words, the mapping relationship between QoS flows and streams within the tunnel is many-to-one. It's worth noting that while this approach only indicates that data from multiple QoS flows can be transmitted within the same tunnel stream, at any given time, each stream packet encapsulates the payload data of only one QoS flow.

[0236] Therefore, in this second approach, the mapping information includes the mapping relationship between multiple QoS flows and a single flow in the tunnel, as well as the mapping relationship between a single flow in the tunnel and a DRB. A single flow in the tunnel can be identified by a Stream ID or a CID, which is not limited in this embodiment of the present application.

[0237] Similarly, taking the QUIC protocol as an example, in one example, the mapping information may include the following content:

[0238] Precedence=1

[0239] QUIC selection descriptor:

[0240] Stream ID#1 or CID#1 (including source CID and destination CID);

[0241] QFI=3, QFI=5;

[0242] DRB=#1.

[0243] This means that Stream#1 (CID#1 used by Stream#1) is mapped to QFI 3 or QFI 5, and Stream ID#1 is transmitted on DRB#1.

[0244] In another example, the mapping information may include the following:

[0245] Precedence=1

[0246] QUIC selection descriptor:

[0247] Stream ID#1 or CID#1 (including source CID and destination CID);

[0248] QFI=3, QFI=5; and

[0249] Precedence=1

[0250] QUIC selection descriptor:

[0251] QFI=3, QFI=5;

[0252] DRB=#1.

[0253] The access network device can separately send the mapping relationship between multiple QoS flows and a single flow in the tunnel to the terminal device, or separately send the mapping relationship between multiple QoS flows and DRBs to the terminal device. For example, the mapping relationship between multiple QoS flows and a single flow in the tunnel is carried in one AS signaling, and the mapping relationship between multiple QoS flows and DRBs is carried in another AS signaling. The embodiments of the present application do not limit the content of the mapping information and the method of sending the mapping information.

[0254] Based on the mapping information, when downlink data transmission is performed between the access network device and the terminal device, including when the access network device sends a tunnel protocol data packet to the terminal device, as shown in FIG14 , the following steps may be included:

[0255] S1401: An access network device receives downlink data packets for multiple QoS flows from a core network device. Each downlink data packet for a QoS flow includes an identifier for the QoS flow. This simply means that the access network device can receive downlink data packets for multiple QoS flows from the core network device, either simultaneously or at different times. The timing of the reception is not limited.

[0256] S1402: The access network device encapsulates the payload data of the downlink data packets of the multiple QoS flows into a downlink data packet of at least one flow in the tunnel according to the mapping information.

[0257] For example, the multiple QoS flows include a first QoS flow and a second QoS flow, and the first QoS flow and the second QoS flow are mapped to the same stream in the tunnel.

[0258] When implementing S1401, the access network device receives a downlink data packet of the first QoS flow, and the downlink data packet of the first QoS flow includes an identifier of the first QoS flow. When implementing S1402, the access network device encapsulates the payload data of the downlink data packet of the first QoS flow in the downlink data packet of the first flow according to the mapping information. Specifically, it can be encapsulated in the data frame of the downlink data packet of the first flow. Taking the QUIC protocol as an example, it is encapsulated in the Stream Frame payload in QUIC. The downlink data packet of the first flow can also be encapsulated in a tunnel protocol data packet, and the tunnel protocol data packet can be sent to the terminal device.

[0259] Alternatively, when implementing S1401, the access network device receives a downlink data packet of the second QoS flow, and the downlink data packet of the second QoS flow includes an identifier of the second QoS flow. When implementing S1402, the access network device encapsulates the payload data of the downlink data packet of the second QoS flow in the downlink data packet of the first flow according to the mapping information. Specifically, it can be encapsulated in the data frame of the downlink data packet of the first flow. Taking the QUIC protocol as an example, it is encapsulated in the Stream Frame payload in QUIC. The downlink data packet of the first flow can also be encapsulated in a tunnel protocol data packet, and the tunnel protocol data packet can be sent to the terminal device.

[0260] Here, still taking the GTU-P protocol used on the core network side as an example, QFI1 and QFI2 respectively represent the QFIs corresponding to the downlink data packets of the two QoS flows received at S1401, and the mapping relationship between QFI and stream indicated by the mapping information indicates that QFI1 and QFI2 are mapped to stream ID1. When implementing S1402, the access network device needs to first remove the GTU-P header, and then, based on the mapping relationship between QFI and stream indicated by the mapping information, encapsulate the payload data of the downlink data packet with QFI1 into the payload of a downlink data packet of the first flow, and add the corresponding QIF to the control information portion of the downlink data packet of the first flow. For example, QFI1 may be added to the header of the tunnel flow frame carrying the QoS flow data, or QFI1 information may be added to the header of the tunnel protocol packet encapsulating the data frame of the first flow, or QFI1 may be encapsulated in independent tunnel protocol control information (e.g., a QUIC control frame), and the control information and the data frame of the first flow may be encapsulated together in the same tunnel protocol packet. And / or, when implementing S1402, the access network device needs to first remove the GTU-P header, and then encapsulate the payload data of the downlink data packet of QFI2 in the payload of another downlink data packet of the first flow according to the mapping relationship between QFI and stream indicated by the mapping information, and add QFI2 to the control information part of a downlink data packet of the first flow, such as the header of the flow frame in the tunnel carrying QoS flow data, or add QFI2 information to the header of the tunnel protocol data packet that encapsulates the data frame of the first flow, or encapsulate QFI2 in an independent tunnel protocol control information (such as the control frame of QUIC), and encapsulate the control information and the data packet of the first flow in the same tunnel protocol data packet.

[0261] It should be understood that in the embodiment of the second method, when the access network device encapsulates the data packets transmitted based on the tunnel flow according to the mapping information, the payload data of the same QFI can be placed in the payload of a Frame, so that the header of the corresponding Stream only carries the identifier of one QFI. The data of multiple QoS flows should not be encapsulated in the payload of the same Frame, that is, only the data of the QoS flow corresponding to one QFI is encapsulated in a Frame. The data of QoS flows corresponding to different QFIs mapped to the same DRB can be placed in different Frames in the same Stream, and the data of QFIs mapped on different DRBs should be placed on different Streams. When the access network device implements the following S1403, the mapping relationship (1:1) between the stream and the DRB indicated by the mapping information is used so that the data packets of the corresponding Stream can be sent to the terminal device through the corresponding DRB.

[0262] Taking the QUIC protocol as an example, the encapsulation mode of the data packet transmitted in the tunnel can refer to the relevant introduction in the previous article, and will not be repeated here. Among them, when the access network device encapsulates the QUIC data packet transmitted in the tunnel according to the mapping information, the value of QFI can be extended in the header of the frame, or the value of QFI can be extended in the header of the QUIC data packet. As shown in Figure 3, in an optional implementation, the value of QFI can be extended and encoded in the stream ID field in the header of the frame. Alternatively, an independent option / parameter can be added to the "length" field in the header of the frame to carry the value of the extended QFI, or the frame header can be extended to add a new information element to carry the QFI. In another optional implementation, when the QUIC protocol is adopted, the QFI can be added to the QUIC header, the QFI can be encoded in the CID field of the QUIC header, or the QFI can be encoded in other extensible fields. Alternatively, the QUIC header can be extended to add a new information element to carry the QFI. In another optional implementation, a new control frame can be introduced into the QUIC data packet, and the QFI can be carried in the control frame, and the control frame and the downlink data packet of the stream can be encapsulated in the same QUIC packet. The embodiment of the present application does not limit the carrying position of the QFI value.

[0263] S1403: The access network device sends downlink data packets of the first flow to the terminal device through the first DRB according to the mapping information, including sending at least one downlink data packet of the first flow to the terminal device through the first DRB. Each downlink data packet of the first flow can be included in a tunnel protocol data packet sent by the access network device to the terminal device.

[0264] Accordingly, the terminal device receives the downlink data packets of the first flow through the first DRB according to the mapping information, including receiving at least one downlink data packet of the first flow through the first DRB, for example, accessing at least one tunnel protocol data packet containing the downlink data packets of the first flow.

[0265] S1404: The downlink data packet of the first flow includes the identifier of the first QoS flow or the identifier of the second QoS flow. The terminal device decapsulates the downlink data packet according to the mapping information and delivers the payload of the downlink data packet of the first flow to the upper layer protocol.

[0266] Similarly, the upper-layer protocol may be an IP protocol. When S1404 is implemented, the terminal device may deliver the payload corresponding to the QFI in the downlink data packet of the first flow to the upper-layer protocol based on the mapping relationship between the QFI and the IP flow, or the terminal device may deliver the payload corresponding to the QFI in the downlink data packet of the first flow to the upper-layer protocol based on the mapping relationship between the IP flow and the QFI, and the mapping relationship between the QFI and the stream. The above-mentioned mapping relationship between the QFI and the IP flow, or the mapping relationship between the IP flow and the QFI, and the mapping relationship between the QFI and the stream, may be sent to the terminal device by the access network device or the core network element (e.g., the SMF element). Please refer to the previous introduction for details and will not be repeated here.

[0267] Among them, when the terminal device receives the downlink data packet of the first flow through the first DRB, it can submit the downlink data packet of the first flow to the Stream buffer corresponding to the QUIC tunnel layer. The terminal device can identify the frame header information in the payload of the QUIC data packet, such as the QFI in the frame header. Then, the terminal device can decapsulate the data in the Frame payload based on the mapping of the QFI and the IP flow and submit it to the upper-layer IP protocol.

[0268] Based on the mapping information, when uplink data transmission is performed between the access network device and the terminal device, including when the terminal device sends a tunnel protocol data packet to the access network device, as shown in FIG15 , the following steps may be included:

[0269] S1501: The terminal device obtains data delivered by the upper layer protocol, and encapsulates the data into the payload of the uplink data packet of the first flow according to the mapping information.

[0270] The data delivered by the upper layer protocol may include data mapped to the first QoS stream, and / or data mapped to the second QoS stream. If the mapping information indicates that the data mapped to the first QoS stream and the data mapped to the second QoS stream can be mapped to the same stream in the tunnel, when S1501 is implemented, the terminal device may encapsulate the data delivered by the upper layer protocol in the payload of the uplink data packet of the first stream according to the mapping information, the uplink data packet of the first stream includes the identifier of the first QoS stream or the identifier of the second QoS stream, or the uplink data packet of the tunnel protocol containing the uplink data packet of the first stream includes the identifier of the first QoS stream or the identifier of the second QoS stream.

[0271] Specifically, the terminal device can encapsulate the data that needs to be mapped to the first QoS flow submitted by the upper layer protocol into the payload of an uplink data frame of the first flow according to the mapping information, and then encapsulate the data frame into the uplink tunnel protocol data packet, and the uplink tunnel protocol data packet includes the identifier of the first QoS flow. Specifically, the identifier of the first QoS flow can be located in the control information part of the uplink data packet of the first flow, for example, the identifier of the first QoS flow can be added to the header of the tunnel protocol data packet or the header of the tunnel flow frame carrying the QoS flow data, or the identifier of the first QoS flow can be added to the header of the tunnel protocol data packet that encapsulates the uplink data frame of the first flow, or the identifier of the first QoS flow can be encapsulated in an independent tunnel protocol control information (such as a QUIC control frame), and the control information and the data packet of the first flow are encapsulated together in the same uplink tunnel protocol data packet. The embodiment of the present application does not limit the location of adding the QFI, and the implementation details can also be found in the downlink transmission scheme introduced in Figure 14 above, which will not be repeated here.

[0272] Alternatively, according to the mapping information, the data that needs to be mapped to the second QoS flow submitted by the upper layer protocol is encapsulated in the payload of another uplink data frame of the first flow, and then the data frame is encapsulated in the uplink tunnel protocol data packet, and the uplink tunnel protocol data packet includes the identifier of the second QoS flow. Specifically, the QFI can be located in the control information part of the uplink data packet of the first flow, for example, the identifier of the second QoS flow is added to the header of the tunnel protocol data packet or the header of the tunnel flow frame carrying the QoS flow data, or the identifier of the second QoS flow is added to the header of the uplink tunnel protocol data packet that encapsulates the uplink data frame of the first flow, or the identifier of the second QoS flow is encapsulated in an independent tunnel protocol control information (such as a QUIC control frame), and the control information and the data packet of the first flow are encapsulated together in the same uplink tunnel protocol data packet. It should be understood that in the embodiment of the second method, when the terminal device encapsulates the data packet of the tunnel-based stream transmission according to the mapping information, the payload data of the same QFI can be placed in the payload of a Frame, so that the header of the corresponding Stream only carries the identifier of one QFI. The payload of the same Frame should not encapsulate data for multiple QFIs, that is, a Frame should only encapsulate data corresponding to one QFI. Data corresponding to QFIs mapped to the same DRB can be placed in the same Stream, while data corresponding to QFIs mapped to different DRBs should be placed in different Streams. When the terminal device implements S1502 below, it will use the mapping relationship (1:1) between the stream and DRB indicated by the mapping information to send the data packets of the corresponding Stream to the access network device through the corresponding DRB.

[0273] Taking the QUIC protocol as an example, the encapsulation mode of the data packet transmitted in the tunnel can refer to the relevant introduction in the previous article, which will not be repeated here. Among them, when the terminal device encapsulates the QUIC data packet transmitted in the tunnel according to the mapping information, the header of the corresponding frame in the QUIC data packet can be extended to carry the QFI value. As shown in Figure 3, in an optional implementation, the QFI value can be extended and encoded in the stream ID field in the header of the frame. Or an independent option / parameter can be added to the "length" field in the header of the corresponding frame to carry the extended QFI value, or the frame header can be extended to add a new information element to carry the QFI. In another optional implementation, when the QUIC protocol is adopted, the QFI can be added to the QUIC header, the QFI can be encoded in the CID field of the QUIC header, or the QFI can be encoded in other extensible fields. Or the QUIC header can be extended to add a new information element to carry the QFI. In another optional implementation, a new control frame can be introduced into the QUIC data packet, and the QFI can be carried in the control frame, and the control frame and the downlink data packet of the stream are encapsulated in the same QUIC packet. The embodiment of the present application does not limit the carrying position of the QFI value.

[0274] S1502: The terminal device sends a tunnel protocol data packet containing an uplink data frame of the first flow through the first DRB according to the mapping information. For example, the terminal device sends a tunnel protocol data packet containing at least one uplink data frame of the first flow through the first DRB. Correspondingly, the access network device receives a tunnel protocol data packet containing an uplink data frame of the first flow through the first DRB according to the mapping information. For example, the terminal device receives a tunnel protocol data packet containing at least one uplink data frame of the first flow through the first DRB.

[0275] S1503: If the tunnel protocol data packet includes the identifier of the first QoS flow, the access network device encapsulates the payload data of the data frame of the first flow in the tunnel protocol data packet into the uplink data packet of the first QoS flow according to the mapping information, and adds the identifier of the first QoS flow to the header of the uplink data packet of the first QoS flow, for example, represented as QFI1, or adds the identifier of the first QoS flow to the tunnel protocol uplink data packet that includes the uplink data packet of the flow. The carrying position of the QFI can be found in the relevant introduction above and will not be repeated here.

[0276] Alternatively, if the tunnel protocol data packet includes the identifier of the second QoS flow, the access network device encapsulates the payload data of the first flow in the tunnel protocol data packet in the uplink data packet of the second QoS flow according to the mapping information, and adds the identifier of the second QoS flow to the header of the uplink data packet of the second QoS flow, for example, represented as QFI2, or adds the identifier of the second QoS flow to the tunnel protocol uplink data packet that includes the uplink data packet of the flow. The carrying position of QFI can be found in the relevant introduction above and will not be repeated here.

[0277] Exemplarily, the uplink data packet of the first QoS flow or the uplink data packet of the second QoS flow may be a GTP-U data packet. The encapsulation method of the GTP-U data packet can be found in the relevant standard documents of 3GPP and will not be described in detail here.

[0278] S1504: The access network device sends an uplink data packet of the first QoS flow to the core network device, or the access network device sends an uplink data packet of the second QoS flow to the core network device. Correspondingly, the core network device receives the uplink data packet of the first QoS flow, or the core network device receives the uplink data packet of the second QoS flow.

[0279] Therefore, through the method shown in Figures 14 and 15 above, when the target transport layer network protocol is used for data transmission between the terminal device and the access network device, based on the 1:1 mapping relationship between the stream flow and the DRB, the air interface can identify the data flow with the granularity of the stream flow in the tunnel, and then perform QoS management and mapping of the stream flow to perform differentiated transmission in the corresponding DRB and QoS flow.

[0280] (3) Mode 3: The tunnel and the QoS flow are mapped 1:1. The mapping information includes the mapping relationship between the tunnel and a single QoS flow, and the mapping relationship between the tunnel and the DRB.

[0281] In this third method, the access network device and the terminal device can exchange mapping information in the process of establishing a session in the manner shown in Figure 9. This process can be found in the relevant description of Figure 9 and will not be repeated here. The difference is that the content of the mapping information exchanged in Method 3 is different from that in Method 1 or Method 2. In this third method, the mapping information includes the mapping relationship between the tunnel and a single QoS flow, and the mapping relationship between the tunnel and the DRB. Afterwards, the terminal device and the access network device can transmit data according to the content indicated by the mapping information.

[0282] In this third approach, mapping to QoS flows / QFIs is achieved at the tunnel / connection granularity. A DRB can carry data from at least one tunnel and encapsulate data from at least one flow transmitted in the same tunnel / connection into packets of the same QoS flow / QFI. Alternatively, data from at least one flow transmitted in a tunnel / connection is mapped to the same QoS flow / QFI.

[0283] Therefore, in this third method, the mapping information includes the mapping relationship between the tunnel and a single QoS flow, and the mapping relationship between the tunnel and the DRB. For example, if the data of a tunnel is carried on the first DRB, the mapping information includes the mapping relationship between the tunnel and the first QoS flow, and the mapping relationship between the tunnel and the first DRB.

[0284] Taking the QUIC protocol as an example, in one example, the mapping information may include the following content:

[0285] Precedence=1

[0286] QUIC selection descriptor:

[0287] CID#1 (including source CID and target CID);

[0288] QFI=3;

[0289] DRB=#1.

[0290] This means that the data corresponding to CID#1 is mapped to QFI 3, and the data corresponding to CID#1 is transmitted on DRB#1.

[0291] When multiple tunnels / connections are mapped to the same DRB, the mapping information may also include the following:

[0292] QUIC selection descriptor:

[0293] CID#1, QFI=3; CID#2, QFI=4;

[0294] DRB=#1.

[0295] In another example, the mapping information may include the following:

[0296] Precedence=1

[0297] QUIC selection descriptor:

[0298] CID#1 (including source CID and target CID);

[0299] QFI = 3; and

[0300] Precedence=1

[0301] QUIC selection descriptor:

[0302] QFI=3;

[0303] DRB=#1.

[0304] The access network device can separately send the mapping relationship between the tunnel and a single QoS flow to the terminal device, or separately send the mapping relationship between the QoS flow and the DRB to the terminal device. For example, the mapping relationship between the single QoS flow and the tunnel identifier is carried in one AS signaling, and the mapping relationship between the QoS flow identifier and the DRB is carried in another AS signaling. The embodiments of the present application do not limit the content of the mapping information and the method of sending the mapping information.

[0305] Based on the mapping information, when downlink data transmission is performed between the access network device and the terminal device, including when the access network device sends a tunnel protocol data packet to the terminal device, as shown in FIG16 , the following steps may be included:

[0306] S1601: The core network sends a downlink data packet of a first QoS flow to an access network device. Specifically, the core network may be a user plane gateway function of the core network.

[0307] Correspondingly, the access network device receives the downlink data packet of the first QoS flow from the core network device.

[0308] S1602: The access network device encapsulates the payload data of the downlink data packet of the first QoS flow into the downlink data packet of the tunnel according to the mapping information.

[0309] For example, CID#1 (e.g., including source CID#1 and destination CID#1) represents the tunnel identifier (or connection identifier) ​​corresponding to the first QoS flow. Taking the GTU-P protocol adopted on the core network side as an example, when implementing S1602, the access network device needs to first remove the GTU-P header, and then, based on the mapping relationship between the QFI and the CID indicated by the mapping information, encapsulate the payload data of the downlink data packet of the first QoS flow in the payload of any stream frame or datagram frame corresponding to CID#1, and encapsulate the stream frame or datagram frame in the downlink tunnel protocol data packet, and use the corresponding CID, such as CID#1, in the header of the tunnel protocol data packet.

[0310] S1603: The access network device sends the downlink data packet of the tunnel to the terminal device through the first DRB corresponding to the first QoS flow according to the mapping information. Correspondingly, the terminal device receives the downlink data packet of the tunnel through the first DRB according to the mapping information.

[0311] S1604: The terminal device decapsulates the downlink data packet of the tunnel according to the mapping information, and delivers the payload of the downlink data packet to the upper layer protocol.

[0312] Among them, taking the QUIC protocol as an example, when implementing S1604, the terminal device can submit the downlink data packet received through the first DRB to the QUIC tunnel, and according to the mapping relationship between the CID and the IP flow, demultiplex the payload data of the QUIC data packet to multiple IP flows, and submit it to the upper application layer. Or according to the mapping relationship between the CID and the QFI, and the intermediate mapping relationship between the QFI and the IP flow, demultiplex the payload data of the QUIC data packet to multiple IP flows, and submit it to the upper application layer. In this case, the intermediate mapping of CID to QFI and QFI to IP flow can be retained inside the terminal device. The embodiment of the present application does not require a lot of modifications to the mapping of QFI to IP flow, and only needs to enhance this mapping process inside the terminal device. Among them, similarly, the above-mentioned mapping relationship between CID and IP flow, or the mapping relationship between CID and QFI, and the intermediate mapping relationship between QFI and IP flow, can also be indicated by the access network device. Please refer to the relevant introduction in the previous text and will not be repeated here.

[0313] Other implementation details of S1601-S1604 are similar to the downlink transmission in the above-mentioned method 1 or method 2. The detailed implementation details can be found in the relevant description in the previous text combined with Figure 11 or Figure 14, and will not be repeated here.

[0314] Based on the mapping information, when uplink data transmission is performed between the access network device and the terminal device, for example, when the terminal device sends a tunnel protocol data packet to the access network device, as shown in FIG17 , the following steps may be included:

[0315] S1701: The terminal device obtains the data delivered by the upper layer protocol, and encapsulates the data in the payload of the uplink data packet of the tunnel according to the mapping information.

[0316] For example, the upper layer protocol may be an IP protocol. When implementing S1701, the terminal device may encapsulate the data delivered by the upper layer protocol in any uplink frame according to the mapping relationship between the IP stream and the QFI, and the mapping relationship between the QFI and the CID, and encapsulate the data frame in a tunnel protocol data packet. That is, it is sufficient to encapsulate the uplink data packet corresponding to the CID, without limiting the corresponding stream frame. At the same time, the CID of the tunnel is used in the header of the tunnel protocol data packet (for example, expressed as CID#1, including source CID#1 and target CID#1). In an optional implementation, the terminal device may map different quadruple groups (including source IP address, source port number, destination IP address, and destination port number) to different QUIC streams / Datagrams.

[0317] S1702: The terminal device sends an uplink data packet of the tunnel through the first DRB according to the mapping information. Correspondingly, the access network device receives an uplink data packet of the tunnel through the first DRB according to the mapping information.

[0318] S1703: The access network device encapsulates the payload data of the uplink data packet of the tunnel into the uplink data packet of the first QoS flow according to the mapping information.

[0319] Among them, after receiving the uplink data packet from the first DRB, the access network device can identify the tunnel identifier in the data packet, that is, the CID, and then encapsulate the payload data in the corresponding frame in the uplink data packet in the uplink data packet of the first QoS flow according to the mapping relationship between the CID and the identifier of the QoS flow indicated by the mapping information, and add the corresponding QFI to the header of the uplink data packet of the first QoS flow. Exemplarily, the uplink data packet of the first QoS flow can be, for example, a GTP-U data packet. The encapsulation method of the GTP-U data packet can be referred to the relevant standard documents of 3GPP and will not be repeated here.

[0320] S1704: The access network device sends an uplink data packet of the first QoS flow to the core network device. Correspondingly, the core network device receives the uplink data packet of the first QoS flow.

[0321] Other implementation details of S1701-S1704 are similar to the uplink transmission in the above-mentioned method 1 or method 2. The detailed implementation details can be found in the relevant description in the previous text combined with Figure 12 or Figure 15, and will not be repeated here.

[0322] Therefore, through the method shown in Figures 16 and 17 above, when the target transport layer network protocol is used for data transmission between the terminal device and the access network device, based on the 1:1 mapping relationship between the tunnel / connection and QFI, DRB, the air interface can identify the data flow at the tunnel granularity, and then perform QoS management and mapping on the tunnel data flow to perform differentiated transmission in the corresponding DRB and QoS flow.

[0323] (4) Mode 4: The tunnel and the DRB are mapped 1:1. The mapping information includes the mapping relationship between the tunnel and a single DRB, and the mapping relationship between a single flow in the tunnel and the QoS flow.

[0324] In this fourth mode, the access network device and the terminal device can exchange mapping information in the process of establishing a session in the manner shown in Figure 9. This process can be referred to the relevant description of Figure 9 and will not be repeated here. The difference lies in that the content of the mapping information exchanged in mode 4 is different from that in mode 1, mode 2, or mode 3. In this mode 4, the mapping information includes the mapping relationship between the tunnel and a single DRB, and the mapping relationship between a single flow in the tunnel and the QoS flow. Afterwards, the terminal device and the access network device can transmit data according to the content indicated by the mapping information.

[0325] In this fourth mode, the mapping between the QoS flow / QFI and the mapping between the tunnel and the DRB is achieved at the granularity of the flow in the tunnel. For example, a DRB can carry at least one tunnel, and the data of a single flow transmitted in the same tunnel / connection can be encapsulated in the data packet of the same QoS flow / QFI (or the data packet of the same QoS flow / QFI can be encapsulated in the data packet of a single flow transmitted in the same tunnel / connection), and the data packets of at least one flow in the same tunnel can be transmitted on the same DRB. Alternatively, the data of at least one stream in a tunnel is mapped to the same QoS flow / QFI, and the data of at least one stream in a tunnel is mapped to the same DRB.

[0326] Therefore, in this fourth mode, the mapping information includes the mapping relationship between the tunnel and a single DRB, and the mapping relationship between a single flow in the tunnel and a QoS flow. For example, if the data of a tunnel is carried on the first DRB, the mapping information includes the mapping relationship between the tunnel and the first DRB, and the mapping relationship between the first flow in the tunnel and the first QoS flow.

[0327] Taking the QUIC protocol as an example, in one example, the mapping information may include the following content:

[0328] Precedence=1

[0329] QUIC selection descriptor:

[0330] Stream ID#1, CID#1 (source CID1, destination CID1) <--> QFI = 3;

[0331] Stream ID#2, CID#2 (source CID2, destination CID2) <--> QFI = 4;

[0332] CID#1, CID#2<->DRB=#1;

[0333] It can also contain only a stream, a QFI, and a Connection ID.

[0334] The above content means that Connection1 (which can have multiple CIDs, including CID#1 and CID#2) is placed on DRB#1 for transmission, and Stream#1 (CID#1) in the QUIC connection is mapped to QFI 3, and Stream#2 (CID#2) in the QUIC connection is mapped to QFI 4.

[0335] In another example, the mapping information may include the following:

[0336] Stream ID#1, CID#1 (source CID1, destination CID1) <--> QFI = 3;

[0337] CID#1<->DRB=#1; and

[0338] Stream ID#2, CID#2 (source CID2, destination CID2) <--> QFI = 4;

[0339] CID#2<->DRB=#1.

[0340] The access network device can separately inform the terminal device of the mapping relationship between different tunnels and DRBs and QFIs. The embodiment of the present application does not limit the content of the mapping information and the method of issuing the mapping information.

[0341] Based on the mapping information, when downlink data transmission is performed between the access network device and the terminal device, including when the access network device sends a tunnel protocol data packet to the terminal device, as shown in FIG18 , the following steps may be included:

[0342] S1801: The core network sends a downlink data packet of a first QoS flow to an access network device. Correspondingly, the access network device receives the downlink data packet of the first QoS flow from the core network device.

[0343] S1802: The access network device encapsulates the payload data of the downlink data packet of the first QoS flow into the downlink data packet of the first flow in the tunnel according to the mapping information.

[0344] For example, CID#1 (for example, including source CID#1 and destination CID#1) represents the tunnel identifier (or connection identifier) ​​of the tunnel corresponding to the first QoS flow. Taking the GTU-P protocol adopted on the core network side as an example, when implementing S1802, the access network device needs to first remove the GTU-P header, and then encapsulate the payload data of the downlink data packet of the first QoS flow in the payload of the Stream Frame or datagram Frame corresponding to the CID#1 and StreamID1 according to the mapping relationship between the QFI and CID+StreamID indicated by the mapping information, and then encapsulate the Stream Frame or datagram Frame in the tunnel protocol data packet, and use CID#1 (source CID#1, destination CID#1) in the header of the tunnel protocol data packet. Among them, the corresponding QFI can be added to the header of the Stream Frame or datagram Frame, or the corresponding QFI can be added to the header of the tunnel protocol data packet containing the Stream Frame or datagram Frame, or the QFI can be encapsulated in an independent tunnel protocol control information (such as the control frame of QUIC). The carrying position of the QFI can refer to the relevant introduction in the previous text and will not be repeated here.

[0345] S1803: The access network device sends a tunnel protocol data packet containing the downlink data frame of the first flow in the tunnel through the first DRB according to the mapping information. Correspondingly, the terminal device receives the tunnel protocol data packet containing the downlink data frame of the first flow in the tunnel through the first DRB according to the mapping information.

[0346] For example, according to the mapping between CID#1 and DRB#1 indicated by the mapping information, a tunnel protocol data packet containing the downlink data frame of the first flow in the tunnel is sent through DRB#1. Correspondingly, the terminal device receives the tunnel protocol data packet containing the downlink data frame of the first flow in the tunnel through DRB#1 according to the mapping information.

[0347] S1804: The terminal device decapsulates the tunnel protocol data packet according to the mapping information, and delivers the payload of the tunnel protocol data packet to the upper layer protocol.

[0348] Among them, taking the QUIC protocol as an example, when implementing S1804, the terminal device can submit the tunnel protocol data packet containing the downlink data frame of the first stream in the tunnel received through the first DRB to the QUIC tunnel, and demultiplex the payload data of the QUIC data packet to multiple IP streams according to the mapping relationship between CID, StreamID and StreamID and IP stream, and submit it to the upper application layer. Or, according to the mapping relationship between the tunnel identifier and QFI, and the mapping relationship between QFI and IP stream, demultiplex the payload data of the QUIC data packet to multiple IP streams and submit it to the upper application layer. In this case, the intermediate mapping of the tunnel identifier to QFI and QFI to IP stream can be retained inside the terminal device. The embodiment of the present application does not require a lot of modifications to the mapping of QFI to IP stream, and only needs to enhance the mapping process inside the terminal device. The above mapping relationship can be sent by the access network device to the terminal device. The notification method can refer to the relevant introduction in the previous text, which will not be repeated here.

[0349] Other implementation details of S1801-S1804 are similar to the downlink transmission in the above-mentioned method 1 or method 2. The detailed implementation details can be found in the relevant description in the previous text combined with Figure 11 or Figure 14, and will not be repeated here.

[0350] Based on the mapping information, when uplink data transmission is performed between the access network device and the terminal device, for example, when the terminal device sends a tunnel protocol data packet to the access network device, as shown in FIG19 , the following steps may be included:

[0351] S1901: The terminal device obtains data delivered by the upper layer protocol, and encapsulates the data into the payload of the uplink data packet of the first flow in the tunnel according to the mapping information.

[0352] For example, the upper layer protocol may be an IP protocol. When implementing S1901, the terminal device may encapsulate the data delivered by the upper layer protocol in the frame of the corresponding stream flow according to the mapping relationship between the IP flow and the QFI, and the mapping relationship between the QFI and the stream flow, and then encapsulate the frame in a tunnel protocol data packet, while using the tunnel CID (for example, represented as CID#1, including source CID#1 and target CID#1) in the header of the tunnel protocol data packet. Among them, the corresponding QFI may be added to the header of the stream frame, or the corresponding QFI may be added to the header of the tunnel protocol data packet containing the stream frame, or the QFI may be encapsulated in an independent tunnel protocol control information (such as a QUIC control frame). The carrying position of the QFI can be found in the relevant introduction above and will not be repeated here.

[0353] S1902: The terminal device sends a tunnel protocol data packet containing an uplink data frame of the first flow in the tunnel through the first DRB according to the mapping information. Correspondingly, the access network device receives a tunnel protocol data packet containing an uplink data frame of the first flow in the tunnel through the first DRB according to the mapping information.

[0354] S1903: The access network device encapsulates the payload data of the uplink data frame of the first flow in the tunnel in the tunnel protocol data packet into the uplink data packet of the first QoS flow according to the mapping information.

[0355] Among them, after receiving the uplink tunnel protocol data packet, the access network device can identify the tunnel identifier and flow identifier in the uplink tunnel protocol data packet, and then encapsulate the payload data in the corresponding frame in the data packet into the uplink data packet of the first QoS flow according to the mapping relationship between the streamID, CID and the QoS flow identifier indicated by the mapping information, and add the corresponding QFI to the header of the data packet. Exemplarily, the uplink data packet of the first QoS flow can be, for example, a GTP-U data packet. The encapsulation method of the GTP-U data packet can be referred to the relevant standard documents of 3GPP and will not be repeated here.

[0356] S1904: The access network device sends an uplink data packet of the first QoS flow to the core network device. Correspondingly, the core network device receives the uplink data packet of the first QoS flow.

[0357] Other implementation details of S1901-S1904 are similar to the uplink transmission in the above-mentioned method 1 or method 2. The detailed implementation details can be found in the relevant description in the previous text combined with Figure 12 or Figure 15, and will not be repeated here.

[0358] Therefore, through the method shown in Figures 18 and 19 above, when the target transport layer network protocol is used for data transmission between the terminal device and the access network device, based on the 1:1 mapping relationship between the tunnel / connection and the DRB and the 1:1 mapping relationship between the flow in the tunnel / connection and the QFI, it is possible to perform QoS management and mapping of the data flow in the tunnel so as to perform differentiated transmission in the corresponding DRB and QoS flow.

[0359] An embodiment of the present application also provides a communication device for executing the method executed by the terminal device or access network device in the above method embodiment. Relevant features can be found in the above method embodiment and will not be repeated here.

[0360] As shown in FIG. 20 , the communication device 2000 may include: a processing unit 2001 and a communication unit 2002 .

[0361] When the communication device is used to execute the method executed by the access network device, there may be at least one tunnel between the access network device and the terminal device, and the tunnel may include at least one stream, and the at least one stream is used to transmit data, wherein the communication device may include: a processing unit 2001, used to obtain mapping information, wherein the mapping information is used to indicate the mapping relationship between the tunnel, the data radio bearer DRB, and the quality of service QoS stream; a communication unit 2002, used to send the mapping information to the terminal device. According to the mapping information, data is transmitted with the terminal device. For example, the access network device sends an uplink data packet according to the mapping information, and / or receives a downlink data packet according to the mapping information. For the specific implementation method, please refer to the method steps implemented by the access network device in the above method embodiment, which will not be repeated here.

[0362] When the communication device is used to execute the method executed by the terminal device, there may be at least one tunnel between the terminal device and the access network device, and the tunnel may include at least one stream, and the at least one stream is used to transmit data, wherein the communication device may include: a communication unit 2002, used to receive mapping information, wherein the mapping information is used to indicate the mapping relationship between the tunnel, the data radio bearer DRB, and the quality of service QoS stream; and transmit data with the access network device according to the mapping information. For example, the terminal device sends an uplink data packet according to the mapping information, and / or receives a downlink data packet according to the mapping information. For the specific implementation method, please refer to the method steps implemented by the terminal device in the above method embodiment, which will not be repeated here.

[0363] It should be understood that the division of the various units in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into a physical entity, or they can be physically separated. In addition, the units in the device can be implemented in the form of a processor calling software; for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or realize the functions of the various units of the device, where the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units can be realized by designing the hardware circuits. The hardware circuit can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units by designing the logical relationship of the components in the circuit. For another example, in another implementation, the hardware circuit can be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units. All units of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0364] In an embodiment of the present application, a processor is a circuit with a signal processing capability. In one implementation, the processor may be a circuit with instruction reading and execution capability, such as a CPU, a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0365] It can be seen that each unit in the above device can be one or more processors (or processing circuits) configured to implement the above method, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0366] In addition, the various units in the above devices can be fully or partially integrated together, or can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the various units of the device. The type of the at least one processor can be different, for example, including a CPU and FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.

[0367] In a simple embodiment, those skilled in the art can imagine that the communication devices in the above embodiments may all adopt the form shown in FIG. 21 .

[0368] The apparatus 2100 shown in FIG21 includes at least one processor 2110 and a communication interface 2130. In an optional design, a memory 2120 may also be included.

[0369] The specific connection medium between the processor 2110 and the memory 2120 is not limited in the embodiment of the present application.

[0370] In the apparatus as shown in FIG. 21 , the processor 2110 may transmit data through the communication interface 2130 when communicating with other devices.

[0371] When the communication device adopts the form shown in Figure 21, the processor 2110 in Figure 21 can call the computer execution instructions stored in the memory 2120, so that the device 2100 can execute any of the above method embodiments.

[0372] An embodiment of the present application also relates to a chip system, which includes a processor for calling a computer program or computer instructions stored in a memory so that the processor executes the method of any of the above embodiments.

[0373] In a possible implementation, the processor may be coupled to the memory through an interface.

[0374] In a possible implementation, the chip system may also directly include a memory, in which a computer program or computer instructions are stored.

[0375] For example, the memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may 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), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache memory. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0376] An embodiment of the present application further relates to a processor, which is used to call a computer program or computer instruction stored in a memory so that the processor executes the method described in any of the above embodiments.

[0377] For example, in the embodiments of the present application, the processor is an integrated circuit chip with signal processing capabilities. For example, the processor can be an FPGA, a general-purpose processor, a DSP, an ASIC or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a CPU, a network processor (NP), a microcontroller unit (MCU), a PLD or other integrated chip, and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0378] It should be understood that the embodiments of the present application may be provided as methods, systems, or computer program products.

[0379] In one possible implementation, an embodiment of the present application provides a computer-readable storage medium, which stores program code. When the program code runs on the computer, the computer executes the above method embodiment.

[0380] In a possible implementation, an embodiment of the present application provides a computer program product. When the computer program product is run on a computer, the computer is caused to execute the above method embodiment.

[0381] Therefore, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0382] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0383] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0384] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these changes and variations. In the various embodiments of the present application, unless otherwise specified or logically conflicting, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

Claims

1. A data transmission method, characterized in that, Applied to an access network device, there is at least one tunnel between the access network device and a terminal device, the tunnel includes at least one flow, and the at least one flow is used to transmit data. The method includes: Obtain mapping information, where the mapping information is used to indicate the mapping relationship between the tunnel, data radio bearer (DRB), and quality of service (QoS) flow; Send the mapping information to the terminal device; Perform data transmission with the terminal device according to the mapping information.

2. The method according to claim 1, wherein At least one flow of the tunnel includes a first flow, and the mapping information includes the mapping relationship between a first QoS flow and the first flow, and the mapping relationship between the first flow and a first DRB, and the first flow is carried on the first DRB.

3. The method according to claim 2, wherein The performing data transmission with the terminal device according to the mapping information includes: Receive a downlink data packet of the first QoS flow from a core network device; According to the mapping information, encapsulate the payload data of the downlink data packet of the first QoS flow in a downlink data packet of the first flow, and send the downlink data packet of the first flow through the first DRB.

4. The method according to claim 2 or 3, characterized in that, The performing data transmission with the terminal device according to the mapping information includes: Receive an uplink data packet of the first flow through the first DRB according to the mapping information; Encapsulate the payload data of the uplink data packet of the first flow in an uplink data packet of the first QoS flow; Send the uplink data packet of the first QoS flow to the core network device.

5. The method according to claim 1, characterized in that, At least one flow of the tunnel includes a first flow, and the mapping information includes the mapping relationship between multiple QoS flows and the first flow, and the mapping relationship between the first flow and a first DRB, and the first flow is carried on the first DRB.

6. The method according to claim 5, characterized in that, The multiple QoS flows include a first QoS flow and a second QoS flow. The performing data transmission with the terminal device according to the mapping information includes: Receive a downlink data packet of the first QoS flow, and the downlink data packet of the first QoS flow includes an identifier of the first QoS flow; According to the mapping information, encapsulate the payload data of the downlink data packet of the first QoS flow in a downlink data packet of the first flow, and send the downlink data packet of the first flow through the first DRB; And / or Receive a downlink data packet of the second QoS flow, and the downlink data packet of the second QoS flow includes an identifier of the second QoS flow; According to the mapping information, encapsulate the payload data of the downlink data packet of the second QoS flow in a downlink data packet of the first flow, and send the downlink data packet of the first flow through the first DRB.

7. The method according to claim 5 or 6, characterized in that, The performing data transmission with the terminal device according to the mapping information includes: Receive an uplink data packet of the first flow through the first DRB according to the mapping information; Wherein, if the uplink data packet of the first flow includes an identifier of the first QoS flow, the method further includes: According to the mapping information, encapsulate the payload data of the uplink data packet of the first flow in the uplink data packet of the first QoS flow, and send the uplink data packet of the first QoS flow to the core network device; and / or, If the identifier of the second QoS flow is included in the uplink data packet of the first flow, the method further includes: According to the mapping information, encapsulate the payload data of the uplink data packet of the first flow in the uplink data packet of the second QoS flow, and send the uplink data packet of the second QoS flow to the core network device.

8. The method according to claim 1, wherein The mapping information includes the mapping relationship between the tunnel and the first QoS flow, and the mapping relationship between the tunnel and the first DRB, and the data of the tunnel is carried on the first DRB.

9. The method according to claim 8, wherein The data transmission with the terminal device according to the mapping information includes: Receive the downlink data packet of the first QoS flow from the core network device; According to the mapping information, encapsulate the payload data of the downlink data packet of the first QoS flow in the downlink data packet of the tunnel; Send the downlink data packet of the tunnel through the first DRB.

10. The method according to claim 8 or 9, characterized in that The data transmission with the terminal device according to the mapping information includes: According to the mapping information, receive the uplink data packet of the tunnel through the first DRB; Encapsulate the payload data of the uplink data packet of the tunnel in the uplink data packet of the first QoS flow; Send the uplink data packet of the first QoS flow to the core network device.

11. The method according to claim 1, characterized in that, The mapping information includes the mapping relationship between the tunnel and the first DRB, and the mapping relationship between the first flow in the tunnel and the first QoS flow, and the data of the tunnel is carried on the first DRB.

12. The method according to claim 11, wherein The data transmission with the terminal device according to the mapping information includes: Receive the downlink data packet of the first QoS flow from the core network device; According to the mapping information, encapsulate the payload data of the downlink data packet of the first QoS flow in the downlink data packet of the first flow in the tunnel; Send the downlink data packet of the first flow in the tunnel through the first DRB.

13. The method according to claim 11 or 12, characterized in that, The data transmission with the terminal device according to the mapping information includes: According to the mapping information, receive the uplink data packet of the first flow in the tunnel through the first DRB; Encapsulate the payload data of the uplink data packet of the first flow in the tunnel in the uplink data packet of the first QoS flow; Send the uplink data packet of the first QoS flow to the core network device.

14. A data transmission method, characterized in that, Applied to a terminal device, there is at least one tunnel between the terminal device and the access network device, the tunnel includes at least one flow, and the at least one flow is used for data transmission. The method includes: Receive mapping information, where the mapping information is used to indicate the mapping relationship between the tunnel, the data radio bearer DRB, and the quality of service QoS flow; According to the mapping information, perform data transmission with the access network device.

15. The method according to claim 14, wherein At least one flow of the tunnel includes a first flow, the mapping information includes the mapping relationship between the first QoS flow and the first flow, and the mapping relationship between the first flow and the first DRB, and the first flow is carried on the first DRB.

16. The method according to claim 15, wherein Performing data transmission with the access network device according to the mapping information includes: Receiving a downlink data packet of the first flow through the first DRB according to the mapping information; Decapsulating the downlink data packet and delivering the payload of the downlink data packet to an upper-layer protocol.

17. The method according to claim 15 or 16, characterized in that Performing data transmission with the access network device according to the mapping information includes: Obtaining data delivered by the upper-layer protocol and encapsulating the data in the payload of an uplink data packet of the first flow according to the mapping information; Sending the uplink data packet through the first DRB.

18. The method according to claim 14, characterized in that, At least one flow of the tunnel includes a first flow, the mapping information includes the mapping relationship between multiple QoS flows and the first flow, and the mapping relationship between the first flow and the first DRB, and the first flow is carried on the first DRB.

19. The method according to claim 18, characterized in that, The multiple QoS flows include a first QoS flow and a second QoS flow. Receiving a downlink data packet according to the mapping information includes: Receiving a downlink data packet of the first flow through the first DRB according to the mapping information, where the downlink data packet includes an identifier of the first QoS flow or includes an identifier of the second QoS flow; Decapsulating the downlink data packet and delivering the payload of the downlink data packet to an upper-layer protocol.

20. The method according to claim 18 or 19, characterized in that, Performing data transmission with the access network device according to the mapping information includes: Obtaining data delivered by the upper-layer protocol and encapsulating the data in the payload of an uplink data packet of the first flow according to the mapping information, where the uplink data packet includes an identifier of the first QoS flow or includes an identifier of the second QoS flow; Sending the uplink data packet of the first flow through the first DRB.

21. The method according to claim 14, wherein The mapping information includes the mapping relationship between the tunnel and the first QoS flow, and the mapping relationship between the tunnel and the first DRB, and the data of the tunnel is carried on the first DRB.

22. The method according to claim 21, wherein Performing data transmission with the access network device according to the mapping information includes: Receiving a downlink data packet of the tunnel through the first DRB according to the mapping information; Decapsulating the downlink data packet of the tunnel and delivering the payload of the downlink data packet to an upper-layer protocol.

23. The method according to claim 21 or 22, characterized in that, Performing data transmission with the access network device according to the mapping information includes: Obtaining data delivered by the upper-layer protocol and encapsulating the data in the payload of an uplink data packet of the tunnel according to the mapping information; Sending the uplink data packet through the first DRB.

24. The method according to claim 14, wherein The mapping information includes the mapping relationship between the tunnel and the first DRB, and the mapping relationship between the first flow in the tunnel and the first QoS flow, and the data of the tunnel is carried on the first DRB.

25. The method according to claim 24, wherein Performing data transmission with the access network device according to the mapping information includes: Receive the downlink data packets of the first flow in the tunnel according to the mapping information through the first DRB; Decapsulate the downlink data packets of the first flow in the tunnel, and deliver the payload of the downlink data packets to the upper layer protocol.

26. The method according to claim 24 or 25, characterized in that, The data transmission with the access network device according to the mapping information includes: Obtain the data delivered by the upper layer protocol, and according to the mapping information, encapsulate the data in the payload of the uplink data packets of the first flow in the tunnel; Send the uplink data packets through the first DRB.

27. A communication device, characterized in that, Comprising at least one processor and an interface circuit, the interface circuit is configured to provide data or code instructions for the at least one processor, and the at least one processor is configured to implement the method according to any one of claims 1-13 or implement the method according to any one of claims 14-26 through logic circuits or by executing code instructions.

28. A communication system, characterized in that, Comprising a communication device for implementing the method according to any one of claims 1-13 or a communication device for implementing the method according to any one of claims 14-26.

29. A computer-readable storage medium, characterized in that, The computer-readable medium stores program code, and when the program code runs on a computer, the computer is caused to execute the method according to any one of claims 1-13 or execute the method according to any one of claims 14-26.

30. A computer program product, characterized in that, When the computer program product runs on a computer, the computer is caused to execute the method according to any one of claims 1-13 or execute the method according to any one of claims 14-26.

Images