A data transmission method and apparatus

Abstract

The application discloses a data transmission method and device, wherein the method comprises: a first communication device acquires a data packet and first and second QoS parameters corresponding to the data packet, maps the data packet to a DRB or RLC layer entity according to the first and second QoS parameters, and sends the data packet to a second communication device. In the above scheme, the first communication device maps the first data packet to the DRB or RLC layer entity based on the two QoS parameters, compared with the prior art scheme of determining the QFI corresponding to the first data packet according to the five-tuple of the first data packet, and then mapping the first data packet to the DRB according to the QFI, the quality of service requirement of the first data packet is more comprehensively considered, so that the data can be more effectively distinguished and processed to meet different needs of users.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of wireless communication, and particularly relates to a data transmission method and device. BACKGROUND

[0002] In a mobile communication network, an operator can provide users with more colorful services such as voice, data, video and the like. Because different services have different requirements for time delay, bandwidth and the like, by introducing a quality of service (QoS) scheme, the differentiation of various services is realized, the high-speed data service is guaranteed, and the network experience of users is enhanced. The purpose of the QoS scheme is to provide network services with different service qualities according to different service requirements. Especially when the network is congested, the service quality of users or services with high priority is preferentially guaranteed.

[0003] When the uplink service flow occurs, the terminal device analyzes the uplink data packet of the uplink service flow, obtains the five-tuple of the data packet, determines the QFI corresponding to the five-tuple according to the mapping relationship between the five-tuple and the QoS flow indicator (QFI), and carries the QFI corresponding to the five-tuple in the encapsulation header of the data packet, so as to realize the mapping of the uplink service flow to the QoS flow. When the downlink service flow occurs, the user plane network element can use the same way as the terminal device side to map the downlink service flow to the QoS flow.

[0004] In a protocol data unit (PDU) session, user plane data with the same QFI will be treated in the same way, such as scheduling, forwarding control and the like. However, in some new service scenarios, such as a social live video streaming (SLVS) scenario, there may be real-time viewers (requiring time delay sensitivity) and delayed viewers for the same video, but because the QFI corresponding to the video data is the same, the video data will be mapped to the same QoS flow, so that the video data cannot be processed differently, and the experience of users with different requirements is affected. SUMMARY

[0005] Therefore, the present application provides a data transmission method and device to realize the differentiated processing of data, so as to meet the different requirements of users.

[0006] In a first aspect, an embodiment of the present application provides a data transmission method, which can be applied to a first communication device, which can be a terminal device (or a chip arranged inside the terminal device) or a network device (or a chip arranged inside the network device). In the method, the first communication device obtains a data packet and a first QoS parameter and a second QoS parameter corresponding to the data packet, maps the data packet to a DRB or an RLC layer entity according to the first QoS parameter and the second QoS parameter, and sends the data packet to a second communication device.

[0007] With the above scheme, since the first communication device maps the first data packet to the DRB or the RLC layer entity based on the two QoS parameters, compared with the prior art scheme of determining the QFI corresponding to the first data packet according to the five-tuple of the first data packet, and then mapping the first data packet to the DRB according to the QFI, the service quality requirement of the first data packet is more comprehensively considered, so that the data can be more effectively processed to meet different needs of users.

[0008] In a possible design, the first QoS parameter or information used for indicating the first QoS parameter is carried in the data packet.

[0009] In a possible design, the first communication device is a terminal device, and the first QoS parameter is assigned to the data packet by an application layer of the first communication device.

[0010] In a possible design, the first communication device is a network device, and the first communication device obtains the data packet and the first QoS parameter corresponding to the data packet by receiving a GTP-U data packet from a core network device, wherein the GTP-U data packet includes the data packet and indication information, and the indication information is used to indicate the first QoS parameter.

[0011] In a possible design, the first communication device maps the data packet to the DRB according to the first QoS parameter and the second QoS parameter, including: the first communication device obtains a correspondence relationship between the first QoS parameter, the second QoS parameter and the DRB; and the first communication device maps the data packet to the DRB corresponding to the first QoS parameter and the second QoS parameter according to the correspondence relationship.

[0012] In a possible design, the first communication device is a terminal device, and the first communication device obtains the correspondence relationship by obtaining the correspondence relationship from a network device, wherein the correspondence relationship is carried in RRC signaling.

[0013] In a possible design, the first communication device is a terminal device, and the method further includes: if the first communication device determines that there is no correspondence relationship, the first communication device maps the data packet to a default DRB.

[0014] In a possible design, the default DRB is configured by the network device, or is a DRB with the minimum or maximum DRB ID among the DRBs associated with the second QoS parameter.

[0015] In a possible design, the first communication apparatus is a terminal device, and the method further includes: if the first communication apparatus determines that there is no correspondence relationship, the first communication apparatus sends a first request message to the network device, where the first request message includes the first QoS parameter and the second QoS parameter.

[0016] In a possible design, the method further includes: the first communication apparatus receives a first response message from the network device, where the first response message is used to indicate a DRB corresponding to the first QoS parameter and the second QoS parameter; and the first communication apparatus maps a data packet to the DRB according to the first QoS parameter and the second QoS parameter, including: the first communication apparatus maps the data packet to the DRB corresponding to the first QoS parameter and the second QoS parameter according to the first response message.

[0017] By using the above scheme, the network device can configure a DRB for the terminal device according to a request message of the terminal device, thereby avoiding signaling overhead and maintenance complexity of the terminal device caused by initially configuring a large number of DRBs for the terminal device.

[0018] In a possible design, the first QoS parameter or information used to indicate the first QoS parameter is carried in an SDAP header or a PDCP header of the data packet.

[0019] In a possible design, the first communication apparatus maps the data packet to the DRB according to the first QoS parameter and the second QoS parameter, including: the first communication apparatus determines the second QoS parameter corresponding to the data packet according to the first QoS parameter; and the first communication apparatus maps the data packet to the DRB corresponding to the second QoS parameter according to the second QoS parameter and the correspondence relationship between the DRB.

[0020] In a possible design, the method further includes: the first communication apparatus obtains the correspondence relationship between the first QoS parameter and the second QoS parameter from the core network device.

[0021] In a possible design, the first communication apparatus maps the data packet to the RLC layer entity according to the first QoS parameter and the second QoS parameter, including: the first communication apparatus maps the data packet to a DRB corresponding to the second QoS parameter, where the DRB corresponds to a packet data convergence protocol (PDCP) layer entity associated with at least one RLC layer entity; and the first communication apparatus obtains a correspondence between the first QoS parameter and the RLC layer entity, and maps the data packet to an RLC layer entity corresponding to the first QoS parameter in the at least one RLC layer entity according to the correspondence.

[0022] In a possible design, the first communication apparatus is a terminal device, and the first communication apparatus obtains the correspondence between the first QoS parameter and the RLC layer entity, including: the first communication apparatus obtains the correspondence from a network device, where the correspondence is carried in RRC signaling.

[0023] In a possible design, the first communication apparatus is a terminal device, and the method further includes: the first communication apparatus maps the data packet to a default RLC layer entity if it is determined that the correspondence does not exist.

[0024] In a possible design, the default RLC layer entity is configured by the network device, or is an RLC layer entity corresponding to a minimum or maximum logical channel (LCH) ID in the at least one RLC layer entity.

[0025] In a possible design, the first communication apparatus is a terminal device, and the method further includes: the first communication apparatus sends a second request message to the network device if it is determined that the correspondence does not exist, where the second request message includes the first QoS parameter.

[0026] In a possible design, the method further includes: the first communication apparatus receives a second response message from the network device, where the second response message is used to indicate the RLC layer entity corresponding to the first QoS parameter; and the first communication apparatus maps the data packet to the RLC layer entity corresponding to the first QoS parameter according to the second response message.

[0027] With the above scheme, the network device can configure the RLC layer entity for the terminal device according to the request message of the terminal device, thereby avoiding signaling overhead and maintenance complexity of the terminal device caused by initially configuring a large number of RLC layer entities for the terminal device.

[0028] In a possible design, the PDCP layer entity is configured with a plurality of groups of parameters, and the first QoS parameter corresponds to a group of parameters in the plurality of groups of parameters; and the method further includes: the first communication apparatus processes the data packet according to the parameters corresponding to the first QoS parameter.

[0029] By configuring the PDCP layer entity with multiple sets of parameters, the data packets can be processed according to the corresponding first QoS parameter, and differentiated processing of the data packets is achieved.

[0030] In a possible design, the PDCP layer entity is associated with multiple RLC layer entities, and the first QoS parameter corresponds to at least two RLC layer entities of the multiple RLC layer entities; the at least two RLC layer entities are configured to implement a duplication transmission function; and the PDCP layer entity of the first communication device maps the data packet to the corresponding RLC layer entity according to the first QoS parameter, including: the first communication device receives indication information from the second communication device, where the indication information is used to indicate an RLC layer entity of the at least two RLC layer entities corresponding to the first QoS parameter and used to implement the duplication transmission function; and the first communication device maps the data packet to the RLC layer entity used to implement the duplication transmission function.

[0031] According to the foregoing scheme, the RLC layer entity used to implement the duplication transmission function can be indicated by the network device, and the flexibility of network device regulation and control is improved.

[0032] In a possible design, the first QoS parameter or information used to indicate the first QoS parameter is carried in an SDAP header or a PDCP header or an RLC header of the data packet.

[0033] In a second aspect, an embodiment of the present application provides a data transmission method, which can be applied to a network device (or a chip arranged inside the network device). In the method, the network device obtains a data packet, a first QoS parameter and a second QoS parameter corresponding to the data packet; and sends a GTP-U data packet to a core network device, where the GTP-U data packet includes the data packet and indication information, and the indication information is used to indicate the first QoS parameter and the second QoS parameter.

[0034] According to the foregoing scheme, since the second data packet and the indication information are included in the GTP-U data packet, the second data packet can be subsequently scheduled according to the first QoS parameter and the second QoS parameter, so as to achieve more fine-grained differentiated processing of the data packet on an end-to-end basis.

[0035] In a possible design, the first QoS parameter corresponding to the data packet is obtained in the following manner: receiving the data packet from the terminal device, the data packet being carried on a first DRB or a first RLC layer entity, and obtaining the first QoS parameter according to the first DRB or the first RLC layer entity; or receiving the data packet from the terminal device, the data packet carrying the first QoS parameter or information used to indicate the first QoS parameter.

[0036] In a possible design, the data packet carries the first QoS parameter or the information used to indicate the first QoS parameter in a SDAP header or a PDCP header or an RLC header of the data packet.

[0037] In a possible design, the indication information is carried in a GTP-U header of the GTP-U data packet.

[0038] In a third aspect, an embodiment of the present application provides a communication system, which includes a network device and a core network device; the network device is configured to obtain a data packet, a first QoS parameter and a second QoS parameter corresponding to the data packet, and send a GTP-U data packet to the core network device, the GTP-U data packet including the data packet and indication information, the indication information being used to indicate the first QoS parameter and the second QoS parameter; and the core network device is configured to receive the GTP-U data packet.

[0039] In a possible design, the communication system further includes a terminal device configured to send the data packet to the network device; the data packet is carried on a first DRB or a first RLC layer entity, the first DRB or the first RLC layer entity corresponding to the first QoS parameter; or the data packet carries the first QoS parameter or information used to indicate the first QoS parameter.

[0040] In a possible design, the core network device is further configured to send an IP data packet, the IP data packet including the data packet and the indication information.

[0041] In a fourth aspect, the present application provides a communication apparatus, which can be a terminal device (or a chip arranged inside a terminal device) or a network device (or a chip arranged inside a network device). The communication apparatus has the functions of the first aspect or the second aspect, for example, the communication apparatus includes modules or units or means corresponding to the steps of the first aspect or the second aspect. The functions of the modules or units or means can be implemented by software or hardware, and the hardware can execute corresponding software.

[0042] In a possible design of the communication apparatus, the communication apparatus includes a processing unit and a communication unit. The communication unit can be configured to transceive signals to implement communication between the communication apparatus and another apparatus. The processing unit can be configured to perform some internal operations of the communication apparatus. The functions of the processing unit and the communication unit can correspond to the steps of the first aspect or the second aspect.

[0043] In a possible design of the communication apparatus, the communication apparatus includes a processor and can further include a transceiver. The transceiver can be configured to transceive signals. The processor can execute program instructions to complete the method in any possible design or implementation manner of the first aspect or the second aspect. The communication apparatus can further include one or more memories coupled to the processor. The one or more memories can be integrated with the processor or arranged separately from the processor, which is not limited in the present application. The memory can store necessary computer programs or instructions for implementing the functions of the first aspect or the second aspect. The processor can execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the communication apparatus can implement the method in any possible design or implementation manner of the first aspect or the second aspect.

[0044] In a possible design of the communication apparatus, the communication apparatus includes a processor and a memory. The memory can store necessary computer programs or instructions for implementing the functions of the first aspect or the second aspect. The processor can execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the communication apparatus can implement the method in any possible design or implementation manner of the first aspect or the second aspect.

[0045] In a possible design of the communication apparatus, the communication apparatus includes at least one processor and an interface circuit. The at least one processor can be configured to communicate with another apparatus through the interface circuit, and perform the method executed by the terminal device in any possible design or implementation manner of the first aspect or the second aspect.

[0046] In a fifth aspect, the present application provides a computer readable storage medium, wherein the computer readable storage medium stores computer readable instructions, and when a computer reads and executes the computer readable instructions, the computer executes the method in any possible design of the first aspect or the second aspect.

[0047] In a sixth aspect, the present application provides a computer program product, and when a computer reads and executes the computer program product, the computer executes the method in any possible design of the first aspect or the second aspect.

[0048] In a seventh aspect, the present application provides a chip, wherein the chip comprises a processor coupled with a memory, and the processor is configured to read and execute a software program stored in the memory, so as to realize the method in any possible design of the first aspect or the second aspect.

[0049] These aspects or other aspects of the present application will be more apparent in the following description of the embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0050] Figure 1a A network architecture diagram suitable for the embodiments of the present application;

[0051] Figure 1b Another network architecture diagram suitable for the embodiments of the present application;

[0052] Figure 1c Another network architecture diagram suitable for the embodiments of the present application;

[0053] Figure 1d Another network architecture diagram suitable for the embodiments of the present application;

[0054] Figure 2a A downlink data transmission diagram between layers provided by the embodiments of the present application;

[0055] Figure 2b A QoS model diagram provided by the embodiments of the present application;

[0056] Figure 2c A possible SLVS platform architecture diagram provided by the embodiments of the present application;

[0057] Figure 2d A data repetition transmission diagram provided by the embodiments of the present application;

[0058] Figure 3 A flow diagram corresponding to the data transmission method provided by the first embodiment of the present application;

[0059] Figure 4a A flow diagram corresponding to the implementation mode 1 provided by the first embodiment of the present application;

[0060] Figure 4b A flowchart corresponding to the implementation manner 2 provided for the embodiment one of the present application;

[0061] Figure 4c A flowchart corresponding to the implementation manner 3 provided for the embodiment one of the present application;

[0062] Figure 5a A flowchart corresponding to the data transmission method provided for the embodiment two of the present application;

[0063] Figure 5b A data transmission process diagram provided for the embodiment two of the present application;

[0064] Figure 6a A flowchart corresponding to the data transmission method provided for the embodiment three of the present application;

[0065] Figure 6b A data transmission process diagram provided for the embodiment three of the present application;

[0066] Figure 7 A possible exemplary block diagram of the apparatus involved in the embodiment of the present application;

[0067] Figure 8 A structure diagram of a terminal device provided for the embodiment of the present application;

[0068] Figure 9 A structure diagram of a network device provided for the embodiment of the present application. DETAILED DESCRIPTION

[0069] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments of the present application.

[0070] First, some terms in the embodiments of the present application are explained and described, so as to facilitate the understanding of the skilled in the art.

[0071] (1) Terminal device: can be a wireless terminal device capable of receiving network device scheduling and indication information, the wireless terminal device can be a device that provides voice and / or data connectivity to a user, or a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. The terminal device can communicate with one or more core networks or the Internet through a radio access network (such as a radio access network, RAN), and the terminal device can be a mobile terminal device, such as a mobile phone (or called "cellular" phone, mobile phone), computer and data card, for example, it can be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), tablets (Pads), computers with wireless transceiver functions, etc. The wireless terminal device can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station (MS), remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, subscriber station (SS), customer premises equipment (CPE), terminal, user equipment (UE), mobile terminal (MT), etc. The terminal device can also be a wearable device and a next-generation communication system, such as a terminal device in a 5G communication system or a terminal device in a future evolved public land mobile network (PLMN), etc.

[0072] (2) Network device: a device in a wireless network, for example, the network device can be a radio access network (RAN) node (or device) that accesses a terminal to a wireless network, which can also be referred to as a base station. At present, some examples of RAN devices are: a new generation base station (gNodeB) in a 5G communication system, a transmission reception point (TRP), an evolved Node B (eNB), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (for example, a home evolved NodeB or a home Node B, HNB), a baseband unit (BBU), a wireless fidelity (Wi-Fi) access point (AP), a road side unit (RSU), an access point in an integrated access and backhaul (IAB) system, a control node and a terminal node in a TSN network, and the like. In addition, in a network structure, the network device can include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node. Furthermore, in other possible cases, the network device can be other apparatuses that provide wireless communication functions for terminal devices. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device. For the convenience of description, the apparatuses that provide wireless communication functions for terminal devices are referred to as network devices in the embodiments of the present application.

[0073] (3) The terms "system" and "network" in the embodiments of the present application can be used interchangeably. "At least one" means one or more, and "multiple" means two or more. The "and / or" describes the association relationship of the associated objects, which means that there can be three kinds of relationships, for example, A and / or B, which can represent the cases of A alone, A and B together, and B alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects. "At least one of the following" or similar expressions means any combination of these items, including any combination of single or multiple items. For example, "at least one of A, B and C" includes A, B, C, AB, AC, BC or ABC.

[0074] In addition, unless otherwise specified, the ordinal numbers "first", "second" and the like mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, time sequence, priority or importance of the multiple objects. For example, the first terminal device and the second terminal device are only used to distinguish different terminal devices, and do not mean that the priority or importance of the two terminal devices is different.

[0075] Figure 1a A network architecture suitable for the embodiments of the present application is shown. As shown in Figure 1a The terminal device 130 can access the wireless network to obtain the service of the external network (such as the Internet) through the wireless network, or communicate with other devices through the wireless network, such as communicating with other terminal devices. The wireless network includes a radio access network (RAN) device 110 and a core network (CN) device 120, wherein the RAN device 110 is used to access the terminal device 130 to the wireless network, and the CN device 120 is used to manage the terminal device and provide a gateway for communication with the external network. It should be understood that Figure 1a The number of devices in the communication system shown is only illustrative, and the embodiments of the present application are not limited thereto. In actual application, more terminal devices 130, more RAN devices 110, and other devices can also be included in the communication system.

[0076] The CN can include multiple CN devices 120, and when Figure 1aWhen the network architecture shown is applicable to a 5G communication system, the CN device 120 may be an access and mobility management function (AMF) entity, a session management function (SMF) entity, or a user plane function (UPF) entity. In the embodiment of the present application, the CN device 120 is taken as a UPF entity. For example, the interface between the terminal device 130 and the RAN device 110 may be referred to as a Uu interface or an air interface, and the interface between the RAN device 110 and the UPF entity may be referred to as an N3 interface.

[0077] Figure 1b This is another network architecture diagram applicable to the embodiment of this application. Figure 1b As shown, the network architecture includes CN equipment, RAN equipment and terminal equipment. Among them, the RAN equipment includes a baseband device and a radio frequency device, wherein the baseband device can be implemented by one node or by multiple nodes, and the radio frequency device can be implemented independently from the baseband device, or integrated in the baseband device, or partially remotely and partially integrated in the baseband device. For example, in an LTE communication system, the RAN equipment (eNB) includes a baseband device and a radio frequency device, wherein the radio frequency device can be remotely arranged relative to the baseband device, such as the radio frequency remote unit (RRU) is remotely arranged relative to the BBU. For another example, in an evolutionary structure, the RAN equipment may include a CU and a DU, multiple DUs may be centrally controlled by one CU, and the interface between the CU and the DU may be called an F1-U interface.

[0078] Figure 1c This is another network architecture diagram applicable to the embodiment of this application. Figure 1b The network architecture shown, Figure 1c The control plane (CP) and user plane (UP) of the CU can also be separated and implemented into different entities, namely the control plane (CP) CU entity (i.e., CU-CP entity) and the user plane (UP) CU entity (i.e., CU-UP entity).

[0079] In the above network architecture, the signaling generated by the CU can be sent to the terminal device through the DU, or the signaling generated by the terminal device can be sent to the CU through the DU. The DU can directly encapsulate the signaling through the protocol layer and transparently transmit it to the terminal device or CU without parsing it. In the following embodiments, if the transmission of such signaling between the DU and the terminal device is involved, then the sending or receiving of the signaling by the DU includes this scenario. For example, the signaling of the RRC or PDCP layer will eventually be processed as the signaling of the PHY layer and sent to the terminal device, or converted from the received signaling of the PHY layer. Under this architecture, the signaling of the RRC or PDCP layer can also be considered to be sent by the DU, or sent by the DU and the RF loader.

[0080] Figure 1d This is another network architecture diagram applicable to the embodiment of the present application, such as Figure 1d As shown, the network architecture may include a RAN device 110 , a CN device 120 , a terminal device 1301 and a terminal device 1302 . Figure 1d The network architecture shown is Figure 1a The difference in the network architecture shown is that Figure 1d Terminal device 1301 and terminal device 1302 can communicate through sidelink resources. For example, terminal device 1301 can send a data packet to terminal device 1302.

[0081] above Figure 1a 、 Figure 1b 、 Figure 1c or Figure 1d The network architecture shown can be applicable to communication systems of various radio access technologies (RAT), for example, 5G (or new radio (NR)) communication systems, and of course, future communication systems. The network architecture and service scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. It is known to those skilled in the art that with the evolution of the communication network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0082] The apparatus in the following embodiments of the present application may be located in a terminal device or a network device, depending on the functions implemented. When the above CU-DU structure is adopted, the network device may be a CU node, a DU node, or a RAN device including a CU node and a DU node.

[0083] In the above Figure 1a 、 Figure 1b 、 Figure 1c orFigure 1d In the illustrated network architecture, the communication between the network device and the UPF entity can follow a certain protocol, such as the GTP-U protocol, which is one of the general packet radio service (GPRS) tunneling protocols (GTP).

[0084] The communication between the network device and the terminal device can follow a certain protocol layer structure. For example, the control plane protocol layer structure can include the functions of the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the media access control (MAC) layer, and the physical layer (PHY) and the like. The user plane protocol layer structure can include the functions of the PDCP layer, the RLC layer, the MAC layer, and the physical layer and the like. In a possible implementation, the PDCP layer can further include the service data adaptation protocol (SDAP) layer. For example, the network device can be implemented by one node to implement the functions of the RRC layer, the PDCP layer, the RLC layer, and the MAC layer and the like, or can be implemented by multiple nodes to implement the functions of these protocol layers. For example, if the network device includes a CU and a DU, the CU and the DU can be divided according to the protocol layers of the wireless network, for example, the functions of the PDCP layer and the protocol layers above the PDCP layer are arranged in the CU, and the functions of the protocol layers below the PDCP layer, for example, the RLC layer and the MAC layer and the like are arranged in the DU. This protocol layer division is only an example, and other protocol layer divisions are also possible, for example, the RLC layer is divided, and the functions of the RLC layer and the protocol layers above the RLC layer are arranged in the CU, and the functions of the protocol layers below the RLC layer are arranged in the DU. In addition, other ways of division are also possible, for example, according to the delay, the functions that need to meet the delay requirement are arranged in the DU, and the functions that do not need to meet the delay requirement are arranged in the CU.

[0085] Taking data transmission between network devices and terminal devices as an example, data transmission needs to pass through the user plane protocol layer, such as the SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer. Among them, the SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer can also be collectively referred to as the access layer. According to the direction of data transmission, it is divided into sending or receiving. Each of the above layers is further divided into sending part and receiving part. Taking the following data transmission as an example, see Figure 2a The figure shows the transmission of downlink data between layers. Figure 2a The downward arrow in the figure indicates data transmission, and the upward arrow indicates data reception. After receiving data from the upper layer, the PDCP layer transmits the data to the RLC layer and the MAC layer. The MAC layer then generates a transport block, which is then wirelessly transmitted through the physical layer. Data is encapsulated in each layer. Data received by a layer from the upper layer is considered a service data unit (SDU) of that layer. After layer encapsulation, it becomes a PDU and is then passed to the next layer. For example, data received by the PDCP layer from the upper layer is called a PDCP SDU, and data sent by the PDCP layer to the lower layer is called a PDCP PDU. Data received by the RLC layer from the upper layer is called an RLC SDU, and data sent by the RLC layer to the lower layer is called an RLC PDU. In the protocol, connections between layers are mostly represented by channels. The RLC layer and MAC layer communicate via a logical channel (LCH), while the MAC layer and the physical layer communicate via a transport channel. Below the physical layer is a physical channel, which is used to connect to the physical layer at the other end.

[0086] For example, according to Figure 2a It can also be seen that the terminal device also has an application layer and a non-access layer. The application layer can be used to provide services to applications installed in the terminal device. For example, downlink data received by the terminal device can be transmitted from the physical layer to the application layer in sequence, and then provided to the application by the application layer. For another example, the application layer can obtain data generated by the application (such as videos recorded by users using the application), and transmit the data to the physical layer in sequence, and then send it to other communication devices. The non-access layer can be used to forward user data, such as forwarding uplink data received from the application layer to the SDAP layer or forwarding downlink data received from the SDAP layer to the application layer. In addition, it can identify the QFI in uplink and downlink data packets (see the description below), such as determining the QFI of uplink and downlink data packets based on the mapping relationship between the quintuple and the QFI.

[0087] Based on the communication protocol and protocol layer structure described above, the following Figure 1a 、Figure 1b or Figure 1c Some possible data transmission processes involved in the illustrated network architecture are described.

[0088] by Figure 1b Taking the network architecture shown as an example, the UPF entity can send a downlink data packet to the terminal device 130. For example, the UPF entity obtains data packet X and encapsulates it through the GTP-U protocol (the GTP-U protocol is one of the protocols of the general packet radio service (GPRS) tunneling protocol (GTP)) to obtain a GTP-U protocol data unit (PDU). The GTP-U PDU is then sent to the CU through the N3 interface. The GTP-U PDU includes data packet X. The CU receives the GTP-U PDU, obtains data packet X, and encapsulates data packet X into a PDCP PDU and delivers it to the DU through the F1-U interface. The DU receives the PDCP PDU, obtains data packet X, and encapsulates data packet X into a MAC PDU, which is then sent to the terminal device through the Uu interface.

[0089] Accordingly, the terminal device 130 can send uplink data packets to the UPF entity. For example, the terminal device obtains data packet Y, encapsulates data packet Y into a MAC PDU, and sends it to the DU via the Uu interface. The DU receives data packet Y, encapsulates data packet Y into a PDCP PDU, and delivers it to the CU via the F1-U interface. The CU receives the PDCP PDU, obtains data packet Y, and encapsulates data packet Y into a GTP-U PDU and sends it to the UPF entity.

[0090] exist Figure 1d In the network architecture shown, data transmission can be carried out between a first terminal device (such as terminal device 1301) and a second terminal device (such as terminal device 1302). For example, the first terminal device obtains data packet Z and sends data packet Z to the second terminal device via a side link.

[0091] When the above Figure 1a 、 Figure 1b 、 Figure 1c or Figure 1d When the network architecture shown is applicable to a 5G communication system (abbreviated as 5GS), the data transmission between different communication devices described above can be implemented based on the QoS model in the 5GS. Figure 2b , which is a schematic diagram of a QoS model.

[0092] like Figure 2bAs shown, in the downlink direction, the data packets entering the 5GS are distinguished at the UPF entity, for example, the UPF entity distinguishes the downlink data packets into different QoS flows according to the packet filter sets of the packet detection rule (PDR), and all the data packets in the same QoS flow are marked with the same QFI. The UPF entity delivers the data packets to the network device on the access network (AN) side through the N3 interface. The network device maps the QoS flow to the DRB, and then transmits the downlink data on the Uu interface. In the uplink direction, after the application layer of the terminal device generates the data packet, the uplink data packet is distinguished into different QoS flows according to the packet filter sets in the QoS rules configured by the SMF entity. The SDAP layer entity of the terminal device maps the data packet of the QoS flow to the corresponding DRB according to the mapping relationship of the QFI to the DRB configured by the base station, and then transmits the uplink data on the air interface. Exemplarily, one QoS flow can be mapped to only one DRB, and different QoS flows can be mapped to the same DRB; the mapping relationship of the QoS flow to the DRB can be determined by the network device on the AN side.

[0093] In the QoS rules and the PDR, the packet filter sets are used to identify one or more data packet flows (such as an internet protocol (IP) flow), and the packet filter sets can include one or more packet filter templates. Currently, the 5GS defines two types of packet filter sets based on the PDU session type, namely, an IP packet filter set and an Ethernet packet filter set. When the PDU session type is IP, the packet filter set supports the following packet filter templates in any combination: source / desination IP address or IPv6 prefix; source / desination port number; protocol identification of the protocol above the IP layer; type of service (TOS) field of IPv4 / traffic class and mask of IPv6; IPv6 flow label; security parameter index; and packet filter direction. The commonly used packet filter template adopts the combination of the first three, that is, the data packet is filtered through the five-tuple (source / desination address, source / desination port number, and transport layer protocol) of the IP data packet. In the embodiments of the present application, the five-tuple of the IP data packet is taken as an example of the packet filter template, and any combination described above can also be taken as the packet filter template in the specific embodiments.

[0094] According to the above description, when the five-tuple of the IP data packet is taken as the packet filter template, the packet filter sets in the PDR include the following packet filter templates in any combination: Figure 2bIn the QoS model shown, if the quintuples of different data packets are the same, they will be marked with the same QFI and mapped to the same QoS flow. Furthermore, on the core network side, data packets marked with the same QFI will receive the same forwarding and scheduling treatment. On the air interface side, DRB is a logical pipeline for data packet transmission. Network equipment can perform specific configurations on the DRB to ensure that the data packets processed and transmitted through the DRB can meet the QoS requirements on the air interface side. Therefore, the data packets transmitted through the DRB receive the same treatment on the air interface. In other words, the treatment received by data packets in a QoS flow within 5GS, such as scheduling and forwarding priority, is always the same.

[0095] However, in some possible scenarios, such as SLVS and TCP data streaming, data within the same QoS flow may have different requirements (such as latency). Specifically, for SLVS scenarios, SLVS applications can provide both real-time and delayed viewing data streams, a feature known as "time-shifted viewing." SLVS viewers have a wide range of latency tolerance. Figure 2c A possible SLVS platform architecture diagram is shown in Figure 1. Figure 2c As shown, the live broadcaster first uploads the live video stream to the server, and the server provides the video stream to different types of viewers. For SLVS video streams, when the available bandwidth is limited, priority is given to ensuring the experience of real-time viewers (for example, only basic layer data frames that are sensitive to delay can be transmitted); when the bandwidth is sufficient, enhanced layer data frames that are outdated for real-time viewers can be further transmitted. In this case, the same video stream contains both delay-sensitive data frames and data frames that are not very delay-sensitive but have higher reliability requirements during transmission. For TCP data stream transmission scenarios, in TCP data streams, the timely transmission of TCP ACK frames is beneficial to congestion control (that is, the delay requirement of TCP ACK frames is high), so there are data frames of different importance in the same TCP data stream.

[0096] Taking the SLVS scenario as an example, when the live broadcaster uploads the live video stream to the server, the quintuples of these live video streams are the same, and the QoS guarantee for the data packets of the same quintuple within 5GS is the same. Therefore, when the live video stream has both real-time viewers (delay-sensitive) and viewers who watch with delay, the QoS flow mapped to the live video stream can only set QoS parameters according to the needs of delay-sensitive users (such as ensuring the delay of data transmission, but the transmission reliability is not high enough), and cannot differentiate and process different data frames, thereby affecting the experience of viewers who watch with delay.

[0097] Based on this, the embodiment of the present application provides a data transmission method for realizing differentiated processing of data to meet different needs of users.

[0098] Exemplarily, the data transmission method provided by the embodiment of the present application can include two possible schemes, which are scheme one and scheme two. In scheme one, the first communication device obtains a first data packet and first and second QoS parameters corresponding to the first data packet, and maps the first data packet to a DRB or an RLC layer entity according to the first and second QoS parameters, and sends it to the second communication device; here, the second QoS parameter can be QFI or QFI', and the description of the second QoS parameter can be referred to below. By using this scheme, since the first communication device maps the first data packet to the DRB or the RLC layer entity based on the two QoS parameters, compared with the existing scheme of determining the QFI corresponding to the first data packet according to the five-tuple of the first data packet, and then mapping the first data packet to the DRB according to the QFI, the quality of service requirements of the first data packet are more comprehensively considered, so that the data can be more effectively differentiated and processed to meet different needs of users. Exemplarily, scheme one can be applicable to Figure 1a The network architecture shown, the first communication device can be a terminal device; the second communication device can be a network device. Or, the second communication device can be a terminal device; the first communication device can be a network device. Or, scheme one can be applicable to Figure 1d The network architecture shown, the first communication device can be a terminal device (such as a first terminal device), and the second communication device can be another terminal device (such as a second terminal device). That is, in scheme one, the first communication device can realize more fine-grained differentiated processing of data packets on the air interface or the sidelink interface according to the first and second QoS parameters.

[0099] In scheme two, the first communication device obtains a second data packet and first and second QoS parameters corresponding to the second data packet, and sends a GTP-U data packet to the second communication device, the GTP-U data packet including the second data packet and indication information, the indication information being used to indicate the first and second QoS parameters; here, the second QoS parameter can be QFI (different from QFI'). Exemplarily, scheme two can be applicable to Figure 1a The network architecture shown, the first communication device can be a network device; the second communication device can be a core network device (such as a UPF entity). By using scheme two, since the GTP-U data packet includes the second data packet and the indication information, it is convenient for subsequent scheduling of the second data packet according to the first and second QoS parameters to realize more fine-grained differentiated processing of data packets on an end-to-end basis.

[0100] The following first explains the related technical features involved in the embodiments of the present application. It should be noted that these explanations are to make the embodiments of the present application easier to understand, and should not be regarded as limiting the scope of protection claimed by the present application.

[0101] (1) first QoS parameter

[0102] The first QoS parameter can be referred to as an enhanced QoS indicator (eQI) or other names, which are not limited in particular.

[0103] As an example, the QoS flow is a granularity of QoS differentiation in a PDU session, and the first QoS parameter can be understood as another granularity of QoS differentiation in the PDU session. Compared with the QoS flow, the first QoS parameter has a finer granularity of differentiation.

[0104] As an example, the first QoS parameter can be used to indicate a quality of service level, for example, to indicate a quality of service level within a QoS flow, so that the data packets within a QoS flow can be mapped to different DRBs or RLC layer entities; or used as a reference element for data packet shunting (filtering), such as a consideration factor for a packet filtering template, for example, for allocating data packets in a data stream of the same five-tuple to different QoS flows or different QFIs.

[0105] In the embodiments of the present application, the first QoS parameter can include one or more bits, and different values of the one or more bits are used to indicate different quality of service levels. The indicators for determining the quality of service level can include one or more of the following QoS indicators: priority level, packet delay budget, packet error rate, default maximum burst data volume, average window, etc. For example, the quality of service level can be determined according to the packet delay budget reflecting the real-time requirement of the data packet and the packet error rate reflecting the transmission reliability requirement, and for example, the quality of service level can be determined according to whether the data packet is a new transmission or a retransmission.

[0106] For example, the first QoS parameter includes 2 bits, and different values of the 2 bits can be used to indicate 4 different levels. For example, in a data stream generated by the same application, the first part of the data packets has a relatively high real-time requirement and a relatively high transmission reliability requirement, and the first QoS parameter corresponding to this part of the data packets can be marked as 00; the second part of the data packets has a relatively high real-time requirement and a relatively low transmission reliability requirement, and the first QoS parameter corresponding to this part of the data packets can be marked as 01; the third part of the data packets has a relatively low real-time requirement and a relatively high transmission reliability requirement, and the first QoS parameter corresponding to this part of the data packets can be marked as 10; and the fourth part of the data packets has a relatively low real-time requirement and a relatively low transmission reliability requirement, and the first QoS parameter corresponding to this part of the data packets can be marked as 11.

[0107] For another example, the first QoS parameter includes 1 bit, and different values of the bit can be used to indicate 2 different levels; for example, the first QoS parameter corresponding to a data packet to be newly transmitted at the application layer is marked as 0, and the first QoS parameter corresponding to a data packet to be retransmitted at the application layer is marked as 1.

[0108] For another example, the first QoS parameter includes 4 bits, and different values of the 4 bits can be used to indicate 16 different levels of service quality. The greater the value corresponding to the 4 bits, the higher the QoS requirement. For example, when the first QoS parameter corresponding to a data packet is 1111, it indicates that the QoS requirement of the data packet is the highest; when the first QoS parameter corresponding to a data packet is 0000, it indicates that the QoS requirement of the data packet is the lowest.

[0109] (2) Second QoS parameter

[0110] In an embodiment of the present application, the second QoS parameter can be used to identify a QoS flow, so that the SDAP layer can map the data packet to the corresponding DRB according to the second QoS parameter of the data packet.

[0111] In one example (referred to as Example 1), the second QoS parameter can be QFI, and the value range of QFI can be 【0, 256】.

[0112] In one possible case of this example, the second QoS parameter can be the QFI mentioned above which has a corresponding relationship with the packet filtering template (such as the five-tuple). In this way, when the packet filtering template of the data packet is obtained, the second QoS parameter corresponding to the data packet can be obtained according to the corresponding relationship between the packet filtering template and the second QoS parameter. For example, referring to Table 1, when the five-tuple is used as the packet filtering template, the corresponding relationship between the five-tuple and the second QoS parameter is shown.

[0113] Table 1: Corresponding relationship example between packet filtering template and second QoS parameter

[0114] Packet filter template Second QoS parameter Five tuple 1 1 Five tuple 2 4 Five tuple 3 9 Five tuple 4 20 …… ……

[0115] In another possible case of this example, the second QoS parameter can be a QFI which has a corresponding relationship with the first QoS parameter, and optionally, other possible parameters such as the five-tuple can also be introduced in the corresponding relationship. Taking the example of the corresponding relationship between the five-tuple, the first QoS parameter and the second QoS parameter, referring to Table 2, the corresponding relationship example of the five-tuple, the first QoS parameter and the second QoS parameter is shown.

[0116] Table 2: Corresponding relationship example of five-tuple, first QoS parameter and second QoS parameter

[0117] Five tuple First QoS parameter Second QoS parameter Five tuple 1 0000 1 Five tuple 1 0001 2 Five tuple 1 0002 3 Five tuple 2 0000 4 Five tuple 2 0100 5 …… …… ……

[0118] According to the above table 1 and table 2, in the above table 1, the QFI corresponding to the quintuple is only part of the QFI, and some reserved QFI has not set the corresponding quintuple; in table 2, by introducing the first QoS parameter, it is possible that the data packets of the same quintuple correspond to different second QoS parameters because of the difference of the first QoS parameter; compared with table 1, in table 2, the reserved QFI can be used to further distinguish the data packets.

[0119] In the embodiments of the present application, for the convenience of distinction, the second QoS parameter involved in table 1 is referred to as QFI, and the second QoS parameter involved in table 2 is referred to as QFI'. In addition, the "corresponding relationship" involved in the embodiments of the present application can also be replaced by "mapping relationship" or other words representing similar meanings, and "association" can also be replaced by "correspondence" or other words representing similar meanings.

[0120] In another example (referred to as example 2), the second QoS parameter can also be a newly defined parameter for identifying a QoS flow, and the newly defined second QoS parameter can have a corresponding relationship with the quintuple and the first QoS parameter. For specific implementation, reference can be made to QFI'.

[0121] (3) Repeat transmission function

[0122] At least one radio bearer (RB) can be established between the sending end and the receiving end to transmit data. The radio bearer can be divided into a signalling radio bearer (SRB) for transmitting signalling data and a data radio bearer (DRB) for transmitting service data, and a set of function entities of the same radio bearer includes a PDCP layer entity, at least two RLC layer entities corresponding to the PDCP layer entity, at least one MAC entity corresponding to the at least two RLC layer entities, and at least one PHY entity corresponding to the at least one MAC entity.

[0123] Duplication transmission or duplication transmission of PDCP layer generally refers to copying a data packet of a radio bearer into multiple identical packets (i.e., duplicated packets) at the PDCP layer, and then delivering the two data packets to multiple different RLC layer entities respectively for transmission, and then transmitting to the MAC layer through different logical channels. Among them, the logical channel is the channel between the RLC layer and the MAC layer. It should be noted that the commonly used retransmission refers to retransmission, and the duplication transmission in the embodiments of the present application is not retransmission. Re-transmission refers to re-sending after a data packet fails to be sent, or continuously sending the same data packet multiple times, while duplication transmission is copying one data packet into two data packets and transmitting them on two logical channels. Here, "duplication" can also be understood as "copying".

[0124] In Figure 2d The data duplication transmission diagram shown in the figure, for a radio bearer between the sending end and the receiving end, on the sending end, at least two RLC layer entities correspond to the same PDCP layer entity, and each RLC layer entity corresponds to a logical channel to send data. Correspondingly, on the receiving end, at least two RLC layer entities correspond to the same PDCP layer entity, and each RLC layer entity corresponds to a logical channel to receive data. Therefore, at least two logical channels are included on the radio bearer between the sending end and the receiving end. Among them, in Figure 1a 、 Figure 1b 、 Figure 1c The network architecture shown in the figure, the sending end can be a terminal device, and the receiving end can be a network device; or, the receiving end can be a terminal device, and the sending end can be a network device. In Figure 1d The network architecture shown in the figure, the sending end can be a first terminal device (such as terminal device 1301), and the receiving end can be a second terminal device (such as terminal device 1302); or, the receiving end can be a second terminal device, and the sending end can be a first terminal device; in this case, the DRB between the first terminal device and the second terminal device can also be called a sidelink DRB.

[0125] Figure 2dThe sending end and the receiving end respectively include the same PDCP layer entity and the first RLC layer entity and the second RLC layer entity associated with the same PDCP layer entity, wherein the first RLC layer entity corresponds to the first logical channel, and the second RLC layer entity corresponds to the second logical channel. The sending end sends data on the first logical channel to the receiving end in the cell 1b or the cell group 1 corresponding to the first logical channel, and the receiving end receives the data of the first logical channel sent by the sending end in the cell 1b or the cell group 1 corresponding to the first logical channel. The sending end sends data of the second logical channel to the receiving end in the cell 2b or the cell group 2 corresponding to the second logical channel, and the receiving end receives data on the second logical channel in the cell 2b or the cell group 2 corresponding to the second logical channel. In the repetition mode, the data from the same PDCP layer entity is repeatedly transmitted on the second RLC layer entity of the sending end and the first RLC layer entity of the sending end, so as to improve the reliability of the sending end in sending data. It should be noted that, Figure 2d In the case of taking the sending end and the receiving end corresponding to two cell groups as an example, in other possible cases, the sending end and the receiving end can also correspond to one cell group, which is not limited in detail.

[0126] It should be noted that the above is described by taking the repetition of the PDCP layer of two logical channels as an example, and in other possible embodiments, the repetition of the PDCP layer of more logical channels is also possible, that is, one radio bearer transmits the data packets copied in the PDCP layer through more logical channels, for example, the data packets copied in the PDCP layer can be transmitted through three or four logical channels.

[0127] Further, taking the sending end as a terminal device and the receiving end as a network device as an example, when the network device configures the repetition transmission function for a DRB of the terminal device, the repetition transmission function of the DRB can be activated or deactivated. For example, referring to the above Figure 2dAs shown, the network device configures the first RLC layer entity and the second RLC layer entity for the PDCP layer entity of the DRB, and if the network device activates the repetition transmission function of the DRB, the data of the PDCP layer entity can be repeatedly transmitted through the first RLC layer entity and the second RLC layer entity; if the network device deactivates the repetition transmission function of the DRB, the data of the PDCP layer entity is no longer repeatedly transmitted, and can be transmitted through the first RLC layer entity or the second RLC layer entity. Alternatively, the network device can also indicate the terminal device to transmit the data packet of the DRB through one or more RLC layer entities through control signaling; for example, the control signaling can be a MAC control element (control element, CE), and the MAC CE can include the indication information of the DRB ID and the LCH ID. Correspondingly, after the terminal device receives the MAC CE, the terminal device transmits the data packet of the indicated DRB through the indicated LCH or RLC layer entity.

[0128] (4) Transmission mode of RLC layer entity

[0129] The transmission mode of the RLC layer entity can include transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). Among them, if the transmission mode of the RLC layer entity is TM, the RLC layer entity does not process the SDU delivered to the RLC layer entity and directly transmits it. If the transmission mode of the RLC layer entity is UM, the RLC layer entity can process the SDU delivered to the RLC layer entity (such as adding additional information), and then send the RLC PDU, and does not need to be acknowledged by the peer entity and does not need to be retransmitted. If the transmission mode of the RLC layer entity is AM, the RLC layer entity can process the SDU delivered to the RLC layer entity (such as adding additional information), and then send the RLC PDU, and need to be acknowledged by the peer entity, if the peer entity confirms that the RLC PDU has been successfully received, there is no need to retransmit the RLC PDU, otherwise the RLC PDU needs to be retransmitted.

[0130] (5) Buffer status report (BSR)

[0131] In the 5G communication system, LCHs can be used to carry data, and data of different service types can be carried through different LCHs. Each LCH can be associated with a scheduling priority, which can be configured by a network device. For example, an LCH carrying URLLC service data can be configured with a higher priority, and an LCH carrying eMBB service data can be configured with a lower priority, that is, the priority of URLLC service data is higher, and the priority of eMBB service data is lower, so that when the terminal device has available uplink resources, resource allocation can be given priority to high-priority data. When new data arrives and all LCHs have no data to be sent or higher-priority LCHs have data to be sent, the MAC layer of the terminal device can trigger a BSR to reflect the total amount of data to be transmitted of at least one LCH for network device scheduling.

[0132] Based on the above description of the related features, the scheme of the embodiments of the present application will be described in detail in combination with Embodiments 1 to 3.

[0133] Embodiment 1

[0134] Figure 3 The flowchart corresponding to the data transmission method provided by Embodiment 1 of the present application is shown in FIG. 1, which includes the following steps. Figure 3

[0135] Step 301: The first terminal device obtains a data packet and first and second QoS parameters corresponding to the data packet.

[0136] There can be various implementation manners for the first terminal device to obtain the first QoS parameter corresponding to the data packet. In an example, the application layer of the first terminal device can obtain the data packet generated by the application program, and assign the first QoS parameter to the data packet, that is, the first QoS parameter can be assigned by the application layer of the first terminal device to the data packet. The application layer can assign the first QoS parameter to the data packet according to various criteria, such as the QoS requirement of the data packet, and the specific implementation of the application layer assigning the first QoS parameter to the data packet is not limited in the present embodiment.

[0137] ​In yet another example, the first terminal device can be connected with other devices, which can be industrial devices such as sensors, operating arms, etc. In turn, the first terminal device can receive a data packet and a first QoS parameter corresponding to the data packet from the other devices, i.e., the first QoS parameter can be assigned to the data packet by the industrial devices. The industrial devices can assign the first QoS parameter to the data packet based on various criteria, which are not limited specifically. After receiving the data packet and the first QoS parameter corresponding to the data packet from the industrial devices, the first terminal device can submit the data packet and the first QoS parameter corresponding to the data packet to the non-access layer or the access layer for processing.

[0138] In yet another example, the first QoS parameter can be assigned to the data packet by the non-access layer of the first terminal device, e.g., if the data packet includes a TCP ACK, the non-access layer can identify and assign the first QoS parameter. After obtaining the data packet and the first QoS parameter corresponding to the data packet, the non-access layer can submit the data packet and the first QoS parameter corresponding to the data packet to the access layer, or determine a second QoS parameter (which is QFI' at this time) corresponding to the data packet based on the first QoS parameter, and then submit the data packet and the second QoS parameter corresponding to the data packet to the access layer. The non-access layer can assign the first QoS parameter to the data packet based on various criteria, which are not limited specifically.

[0139] Hereinafter, when described, the first QoS parameter assigned to the data packet by the application layer of the first terminal device will be taken as an example for description, other cases can be referred to the processing, and hereinafter the first QoS parameter will be referred to as eQI.

[0140] At step 302, the first terminal device maps the data packet to a DRB or an RLC layer entity according to the eQI and the second QoS parameter corresponding to the data packet, and sends the data packet to a network device or a second terminal device.

[0141] Hereinafter, several possible implementation manners of the above steps 301 and 302 will be described by taking the data packet as a first data packet as an example.

[0142] Implementation 1

[0143] In implementation manner 1, the second QoS parameter can be QFI (different from QFI').

[0144] Referring to Figure 4aAs shown, the specific implementation of step 301 and step 301 can be that the application layer of the first terminal device can obtain the first data packet and the eQI corresponding to the first data packet, and then submit the first data packet and the eQI corresponding to the first data packet to the non-access layer; after the non-access layer receives the first data packet and the eQI corresponding to the first data packet, the non-access layer can determine the QFI corresponding to the first data packet according to the packet filtering template in the QoS rule, and identify the corresponding QFI for the first data packet. The non-access layer submits the first data packet, the QFI corresponding to the first data packet and the eQI to the SDAP layer entity. The SDAP layer entity maps the first data packet to the DRB according to the QFI corresponding to the first data packet and the eQI, and sends it to the network device or the second terminal device.

[0145] The first terminal device can obtain the correspondence between the QFI, the eQI and the DRB (which can also be described as the correspondence between the QFI+eQI and the DRB), and then the SDAP layer entity of the first terminal device maps the first data packet to the DRB corresponding to the QFI and the eQI according to the correspondence and the QFI and the eQI corresponding to the first data packet. For example, the correspondence between the QFI, the eQI and the DRB can be configured by the network device for the first terminal device through RRC signaling, and the specific configuration method can be various, for example, the network device can configure the correspondence between the QFI, the eQI and the DRB through the SDAP configuration (SDAP-Config) information element in the DRB addition (DRB-ToAddMod) information element carried in the RRC reconfiguration (RRC Reconfiguration) message.

[0146] Referring to Table 3, an example of the correspondence between the QFI, the eQI and the DRB is shown.

[0147] Table 3: Example of correspondence between QFI, eQI and DRB

[0148]

[0149] As can be seen from Table 3, data packets corresponding to different eQIs in the same QoS flow of the same QFI can be mapped into the same or different DRBs. For example, for the QoS flow with QFI 1, data packets corresponding to eQI 1 need to be mapped into DRB 1 for processing and transmission, and data packets corresponding to eQI 2 need to be mapped into DRB 2 for processing and transmission.

[0150] For example, assuming that the eQI corresponding to the first data packet is eQI 2, and the QFI corresponding to the first data packet is QFI 1, according to Table 3, QFI 1+eQI 2 corresponds to DRB 2; in this case, the SDAP layer entity of the first terminal device can map the first data packet into DRB 2.

[0151] It is assumed that the eQI corresponding to the first data packet is eQI 3, and the QFI corresponding to the first data packet is QFI 1. There is no DRB corresponding to QFI 1+eQI 3 in the correspondence shown in Table 3. In this case, in an example, when there is no DRB matching the QFI and eQI corresponding to the first data packet, the first terminal device can send a request message 1 to the network device, and the request message 1 can include QFI 1 (or information indicating QFI 1) and eQI 3 (or information indicating eQI 3, such as the index of eQI 3). Correspondingly, after receiving the request message 1, the network device can return a response message 1 to the first terminal device, and the response message 1 includes the DRB ID corresponding to QFI 1+eQI 3 (or information indicating the DRB corresponding to QFI 1+eQI 3). Further, the first terminal device can update Table 3 according to the DRB corresponding to QFI 1+eQI 3. In this way, the network device can configure the DRB for the first terminal device according to the request message of the first terminal device, avoiding the signaling overhead and the maintenance complexity of the first terminal device caused by initially configuring a large number of DRBs for the first terminal device.

[0152] In yet another example, when there is no DRB matching the QFI and eQI corresponding to the first data packet, the first terminal device can map the first data packet into a default DRB. One implementation of the default DRB is that each QFI can have a corresponding default DRB, and the default DRB corresponding to a QFI can be configured by the network device, such as the network device configuring DRB 1 as the default DRB for QFI 1; or alternatively, the default DRB corresponding to a QFI can be determined by the first terminal device based on preset rule 1, such as preset rule 1 being that the DRB ID or the corresponding LCH ID of all DRBs corresponding to or associated with a QFI is the smallest / largest to be the default DRB, or the logical channel priority of all DRBs corresponding to or associated with a QFI is the highest / lowest to be the default DRB, taking Table 3 as an example, if the DRB with the smallest DRB ID is determined to be the default DRB, then DRB 1 is the default DRB corresponding to QFI 1. Another implementation of the default DRB is that all QFIs share one default DRB, which can be configured by the network device, or determined by the first terminal device based on preset rule 2, such as preset rule 2 being that the DRB ID or the corresponding LCH ID of all DRBs or all DRBs associated with the SDAP layer entity is the smallest / largest to be the default DRB, or the logical channel priority is the highest / lowest to be the default DRB. The preset rule 1 or the preset rule 2 can be predefined by the protocol, or determined by the network device and indicated to the terminal device.

[0153] For this example, in an optional scheme, after the first terminal device maps the first data packet into the default DRB, the first terminal device can also perform the operation in the previous example, i.e., sending a request message 1 to the network device to request the DRB corresponding to QFI 1+eQI 3, and updating Table 3, so as to map the next data packet corresponding to QFI 1+eQI 3 into the DRB corresponding to QFI 1+eQI 3.

[0154] In implementation 1, the first terminal device can encapsulate the eQI corresponding to the first data packet into the first data packet, and then send it to the network device or the second terminal device; or alternatively, the eQI corresponding to the first data packet can not be encapsulated into the data packet, but sent to the network device or the second terminal device layer together with the first data packet.

[0155] For example, the first terminal device can encapsulate the eQI corresponding to the first data packet into the first data packet. For example, the eQI corresponding to the first data packet (or information for indicating the eQI corresponding to the first data packet) can be included in the SDAP header of the first data packet. For example, after the SDAP layer entity of the first terminal device receives the first data packet, the QFI1 and the eQI corresponding to the first data packet, the SDAP layer entity can encapsulate the eQI corresponding to the first data packet into the SDAP header of the first data packet, and then map the encapsulated first data packet to the DRB or deliver the first data packet to the PDCP layer entity. Alternatively, the eQI corresponding to the first data packet (or information for indicating the eQI corresponding to the first data packet) can be included in the PDCP header of the first data packet. For example, when the SDAP layer entity delivers the first data packet to the PDCP layer entity, the SDAP layer entity can further indicate the eQI corresponding to the first data packet. Accordingly, after the PDCP layer entity receives the first data packet delivered by the SDAP layer entity, the PDCP layer entity can encapsulate the eQI corresponding to the first data packet into the PDCP header of the first data packet.

[0156] It should be noted that if one PDCP layer entity corresponds to one eQI, when the SDAP layer entity delivers the first data packet to the PDCP layer entity, the SDAP layer entity can no longer indicate the eQI corresponding to the first data packet. Accordingly, after the PDCP layer entity receives the first data packet delivered by the SDAP layer entity, the PDCP layer entity can encapsulate the eQI corresponding to the PDCP layer entity into the PDCP header of the first data packet. Since the eQI corresponding to the first data packet is included in the SDAP header or the PDCP header of the first data packet, after the second communication device receives the first data packet, the second communication device can obtain the eQI corresponding to the first data packet.

[0157] In implementation 1, the network device can configure multiple DRBs corresponding to the same QFI independently, that is, the PDCP layer entity, the RLC layer entity and the logical channel can be configured independently. For example, DRB 1 and DRB 2 corresponding to QFI 1 can be configured independently, and the configuration of PDCP layer entity 1 corresponding to DRB 1 and PDCP layer entity 2 corresponding to DRB 2 can be different, and / or the configuration of the RLC layer entity (or logical channel) associated with PDCP layer entity 1 and the RLC layer entity (logical channel) associated with PDCP layer entity 2 can be different. Wherein, the configuration of PDCP layer entity 1 and PDCP layer entity 2 can be different, which means that the parameters of PDCP layer entity 1 and the parameters of PDCP layer entity 2 are different, such as the parameters of the PDCP layer entity can include the discard time (a timer is started after the PDCP layer entity receives a PDCP SDU, and a PDCP SDU discard operation is performed after the timer expires, and the time length of the timer can be referred to as the discard time), the discard time of PDCP layer entity 1 is 10ms, and the discard time of PDCP layer entity 2 is 20ms. The configuration of the RLC layer entity associated with PDCP layer entity 1 (such as including RLC layer entity 1) and the RLC layer entity associated with PDCP layer entity 2 (such as including RLC layer entity 1a) can be different, which means that the transmission mode of RLC layer entity 1 and the transmission mode of RLC layer entity 1a are different, such as the transmission mode of RLC layer entity 1 is UM and the transmission mode of RLC layer entity 1a is AM.

[0158] Therefore, since multiple DRBs corresponding to the same QFI can be configured independently, by mapping data packets corresponding to the same QFI but corresponding to different eQIs to different DRBs, the data packets in the same QoS flow can be processed differently, that is, data packets with different delay or reliability requirements can be processed differently in the air interface.

[0159] Implementation 2

[0160] In implementation 2, the second QoS parameter can be QFI'.

[0161] Referring to Figure 4bAs shown, the specific implementation of step 301 and step 302 can be that the application layer of the first terminal device can obtain the first data packet and the eQI corresponding to the first data packet, and then submit the first data packet and the eQI corresponding to the first data packet to the non-access layer; after receiving the first data packet and the eQI corresponding to the first data packet, the non-access layer can determine the QFI' corresponding to the first data packet, and identify the corresponding QFI' for the first data packet. The non-access layer submits the first data packet and the QFI' corresponding to the first data packet to the SDAP layer. The SDAP layer entity maps the first data packet to a DRB according to the QFI' corresponding to the first data packet, and sends it to the network device or the second terminal device.

[0162] Exemplarily, the first terminal device can obtain the corresponding relationship shown in Table 2, and then the non-access layer of the first terminal device can determine the QFI' corresponding to the first data packet according to the corresponding relationship shown in Table 2 and the eQI and the five-tuple corresponding to the first data packet. The first terminal device can obtain the corresponding relationship shown in Table 2 in many ways, such as the corresponding relationship shown in Table 2 can be configured by the core network device through the non-access layer message for the first terminal device, such as configured by the SMF entity through the PDU session establishment / modification process for the first terminal device. According to Table 2, data packets with different eQIs in the same five-tuple data stream can be mapped to different QFI's, and then can be processed and transmitted through different DRBs.

[0163] Exemplarily, the first terminal device can obtain the corresponding relationship between QFI' and DRB ID, and then the SDAP layer entity of the first terminal device can map the first data packet to the DRB corresponding to the QFI' according to the corresponding relationship between QFI' and DRB ID. For example, the first terminal device can obtain the corresponding relationship between QFI' and DRB ID from the network device. The way in which the first terminal device obtains the corresponding relationship between QFI' and DRB ID can also refer to the way in which the terminal device obtains the corresponding relationship between QFI and DRB ID in the existing scheme, and details are not repeated.

[0164] In implementation manner 2, by introducing eQI and mapping the five-tuple and eQI to QFI' by the non-access layer, different data packets with different eQIs can be distinguished and processed, that is, data packets with different delay or reliability requirements are distinguished and processed in the air interface. Moreover, this method does not need to change the operation of the access layer, and has strong applicability.

[0165] Implementation 3

[0166] In implementation manner 3, the second QoS parameter can be QFI (different from QFI').

[0167] Referring to Figure 4c As shown in FIG. 3, the specific implementation of step 301 and step 302 can be: the application layer of the first terminal device can obtain the first data packet and the eQI corresponding to the first data packet, and then submit the first data packet and the eQI corresponding to the first data packet to the non-access layer; after receiving the first data packet and the eQI corresponding to the first data packet, the non-access layer can determine the QFI corresponding to the first data packet according to the packet filtering template in the QoS rule, and identify the corresponding QFI for the first data packet. The non-access layer submits the first data packet, the QFI corresponding to the first data packet, and the eQI to the SDAP layer. The SDAP layer entity maps the first data packet and the eQI corresponding to the first data packet to the DRB (i.e., submits to the PDCP layer entity corresponding to the DRB) according to the QFI corresponding to the first data packet. The PDCP layer entity maps the first data packet to the RLC layer entity or the LCH according to the eQI corresponding to the first data packet, and sends it to the network device or the second terminal device.

[0168] The PDCP layer entity corresponding to the DRB can be associated with multiple RLC layer entities, and the multiple RLC layer entities have a corresponding relationship with the eQI. For example, the network device can configure multiple RLC layer entities associated with the PDCP layer entity for the terminal device, and the corresponding relationship between the eQI and the RLC layer entity; there can be multiple specific configuration methods, and one possible configuration method is that when the network device configures an RLC layer entity or a logical channel corresponding to an RLC layer entity, the DRB ID and the eQI set are indicated in the configuration information element, indicating that the RLC layer entity is associated with the PDCP layer entity corresponding to the DRB ID, and the eQI corresponding to the RLC layer entity is the eQI included in the eQI set (or the RLC layer entity is used to process the data packet mapped to the DRB and the corresponding eQI is included in the eQI set). The eQI set can include one eQI or multiple eQIs. For example, the network device indicates the DRB ID as DRB1 and the eQI set including eQI 1 and eQI 2 in the configuration information element (RLC-BearerConfig or RLC-Config) of RLC layer entity 1, so that the first terminal device can know that the RLC layer entity 1 is associated with the PDCP layer entity 1 corresponding to the DRB 1, and the eQI corresponding to the RLC layer entity 1 includes eQI 1 and eQI 2 (or the RLC layer entity 1 is used to process the data packet mapped to the DRB 1 and the corresponding eQI is eQI 1 or eQI 2).

[0169] It should be understood that, since the RLC layer entity is in one-to-one correspondence with the LCH, the content of the corresponding LCH can also be adaptively extended to the content related to the RLC entity in the embodiments of the present application. For example, the plurality of RLC layer entities correspond to the eQI, and the plurality of LCHs corresponding to the plurality of RLC layer entities also correspond to the eQI, which is also within the protection scope of the present application.

[0170] Referring to Table 4, the PDCP layer entity 1 corresponding to the DRB 1 is associated with the RLC layer entity 1 and the RLC layer entity 2, each of which corresponds to an eQI set, and the eQI set can include one or more eQIs. Among them, the eQI set corresponding to the RLC layer entity 1 includes eQI 1 and eQI 2, and the eQI set corresponding to the RLC layer entity 2 includes eQI 3 and eQI 4.

[0171] Table 4: Correspondence relationship between RLC layer entity and eQI set associated with PDCP layer entity 1

[0172] DRB ID RLC layer entity Set of eQIs DRB 1 RLC layer entity 1 eQI 1, eQI 2 DRB 1 RLC layer entity 2 eQI 3, eQI 4

[0173] As can be seen from Table 4, the data packets corresponding to different eQIs in the same DRB can be mapped to the same or different RLC layer entities. For example, the data packets corresponding to eQI 1 or eQI 2 in DRB 1 need to be mapped to RLC layer entity 1 for processing and transmission, and the data packets corresponding to eQI 3 or eQI 4 need to be mapped to RLC layer entity 2 for processing and transmission.

[0174] In this way, the first terminal device can obtain the correspondence relationship between the RLC layer entity associated with the PDCP layer entity and the eQI, and then the PDCP layer entity of the first terminal device can map the first data packet to the RLC layer entity corresponding to the eQI according to the correspondence relationship and the eQI corresponding to the first data packet.

[0175] Suppose the eQI corresponding to the first data packet mapped to DRB 1 is eQI 2, then according to Table 4, eQI 2 corresponds to RLC layer entity 1; in this case, the PDCP layer entity 1 corresponding to DRB 1 can map the first data packet to RLC layer entity 1.

[0176] It is assumed that the eQI corresponding to the first data packet mapped into the DRB 1 is eQI 5, and there is no RLC layer entity corresponding to eQI 5 in the correspondence shown in Table 4. In this case, in an example, when there is no RLC layer entity matching the eQI corresponding to the first data packet, the first terminal device can send a request message 2 to the network device, and the request message 2 can include eQI 5 (or information for indicating eQI 5, such as the index of eQI 5). Correspondingly, after receiving the request message 2, the network device can return a response message 2 to the first terminal device, and the response message 2 includes the identifier of the RLC layer entity corresponding to eQI 5 in the plurality of RLC layer entities associated with the PDCP layer entity 1 (or information for indicating the RLC layer entity corresponding to eQI 5). Then, the first terminal device can map the first data packet into the RLC layer entity corresponding to eQI 5. Further, the first terminal device can update Table 4 according to the RLC layer entity corresponding to eQI 5. In this way, the network device can configure the RLC layer entity for the first terminal device according to the request message of the first terminal device, avoiding the signaling overhead and the maintenance complexity of the first terminal device caused by initially configuring a large number of RLC layer entities for the first terminal device.

[0177] In another example, when there is no RLC layer entity matching the eQI corresponding to the first data packet, the first terminal device can map the first data packet into a default RLC layer entity, where the default RLC layer entity can be the default RLC layer entity corresponding to the DRB 1. The default RLC layer entity corresponding to the DRB 1 can be configured by the network device, such as the network device configuring the RLC layer entity 1 as the default RLC layer entity for the DRB 1. The specific configuration method can be various, such as the network device indicating the RLC layer entity 1 as the default RLC layer entity in the configuration information element of the RLC layer entity 1. Alternatively, the default RLC layer entity corresponding to the DRB 1 can be determined by the first terminal device based on a preset rule 3, such as the preset rule 3 being that the RLC layer entity corresponding to the minimum / maximum LCH ID is the default RLC layer entity. For example, if the RLC layer entity with the minimum LCH ID is determined as the default RLC layer entity, the RLC layer entity 1 is the default RLC layer entity corresponding to the DRB 1. The preset rule 3 can be predefined by the protocol or determined by the network device and indicated to the terminal device.

[0178] In the implementation 3, when the PDCP layer entity of the DRB is associated with multiple RLC layer entities, the RLC layer entities can be independently configured, such as the multiple RLC layer entities can be configured as different transmission modes. For example, the PDCP layer entity corresponding to the DRB 1 is associated with 2 RLC layer entities (RLC layer entity 1 and RLC layer entity 2), wherein the RLC layer entity 1 can be configured as UM, and the RLC layer entity 2 can be configured as AM. In this way, since the multiple RLC layer entities associated with the PDCP layer entity are independently configured, the data packets in the same QoS flow can be processed differently by mapping the data packets with different eQIs to different RLC layer entities.

[0179] In the implementation 3, the network device can configure one set of parameters or multiple sets of parameters for the PDCP layer entity corresponding to the DRB. For example, the parameters of the PDCP layer entity can include one or more possible parameters, which are described below by taking the discard duration as an example.

[0180] When the network device configures multiple sets of parameters for the PDCP layer entity, the correspondence between the eQI and the multiple sets of parameters can be further configured, as shown in Table 5, which is an example of the correspondence between the eQI and the multiple sets of parameters.

[0181] Table 5: Example of correspondence between eQI and multiple sets of parameters

[0182] eQI Drop duration eQI1, eQI2, eQI3, eQI4 Drop duration 1 (e.g. 10 ms) eQI4, eQI5, eQI6 Drop duration 2 (e.g. 15 ms) eQI7, eQI8 Drop duration 3 (e.g. 20 ms)

[0183] When the network device configures one set of parameters (such as discard duration 1) for the PDCP layer entity, the PDCP layer entity can process the data packets submitted to the PDCP layer entity according to the discard duration. If the network device configures multiple sets of parameters (such as discard duration 1, discard duration 2, and discard duration 3) for the PDCP layer entity, and the correspondence between the first QoS parameter and the multiple sets of parameters, the PDCP layer entity can process the data packets according to the parameters of the PDCP layer entity corresponding to the first QoS parameter of the data packets according to the correspondence shown in Table 5, such as the first QoS parameter corresponding to the data packet 1 is eQI 1, and the discard duration 1 can be used to process the data packet 1, and the first QoS parameter corresponding to the data packet 2 is eQI 4, and the discard duration 2 can be used to process the data packet 2. In this way, since multiple sets of parameters are configured for the PDCP layer entity, the data packets in the same QoS flow can be processed differently by processing the data packets with different eQIs using the same or different parameters.

[0184] In the implementation 3, since the PDCP layer entity maps the data packet to the RLC layer entity corresponding to the eQI according to the eQI corresponding to the data packet, in the embodiment of the application, when the repetition transmission function is configured, the repetition transmission function can be configured for the eQI in one DRB, that is, the data packet corresponding to the eQI can be copied and submitted to multiple RLC layer entities. Wherein, the PDCP layer entity corresponding to the DRB can be associated with multiple RLC layer entities, the eQI configured for repetition transmission corresponds to at least two RLC layer entities of the multiple RLC layer entities, and the at least two RLC layer entities are used to implement repetition transmission. For example, referring to Table 6 shown in the above, eQI 3 corresponds to RLC layer entity 1, RLC layer entity 2 and RLC layer entity 3, and then the repetition transmission function can be configured for eQI 3.

[0185] Table 6: Correspondence between RLC layer entity and eQI set

[0186] DRB ID RLC layer entity Set of eQIs DRB 1 RLC layer entity 1 eQI 1, eQI 2, eQI 3

[0187] DRB 1 RLC layer entity 2 eQI 3, eQI 4 DRB 1 RLC layer entity 3 eQI 3

[0188] Further, in one example, the network device can activate or deactivate the repetition transmission function configured for eQI 3 through control signaling. For example, if the network device activates the repetition transmission function configured for eQI 3 through control signaling, and the eQI corresponding to the first data packet is eQI 3, the PDCP layer entity of the first terminal device can map the first data packet to RLC layer entity 1, RLC layer entity 2 and RLC layer entity 3 for repetition transmission; if the network device deactivates the repetition transmission function configured for eQI 3 through control signaling, the PDCP layer entity of the first terminal device can map the first data packet to RLC layer entity 1 for transmission, or to RLC layer entity 2 for transmission, or to RLC layer entity 3 for transmission.

[0189] In another example, the network device can indicate through control signaling which RLC layer entities corresponding to eQI 3 perform layer repetition transmission. For example, if the network device indicates RLC layer entity 1 and RLC layer entity 2 through control signaling, the PDCP layer entity of the first terminal device can map the first data packet to RLC layer entity 1 and RLC layer entity 2 for repetition transmission. For example, the control signaling can include DRB 1 (or information for indicating DRB 1), eQI 3 (or information for indicating eQI 3) and the identification of RLC layer entity 1 and RLC layer entity 2 (or information for indicating RLC layer entity 1 and RLC layer entity 2, or LCH 1 corresponding to RLC layer entity 1 and LCH 2 corresponding to RLC layer entity 2, or information for indicating LCH 1 and LCH 2).

[0190] It should be noted that the control signaling can be RRC signaling or MAC CE, and the specific implementation is not limited.

[0191] In the implementation manner 3, the eQI corresponding to the first data packet (or information used for indicating the eQI corresponding to the first data packet) can be included in the SDAP header or the PDCP header or the RLC header of the first data packet.

[0192] In the implementation manner 3, when the terminal device performs BSR reporting, the MAC layer of the terminal device needs to calculate the to-be-transmitted data amount of different LCHs. One possible way of calculating the to-be-transmitted data amount of different LCHs is that, for one of the LCHs (for example, LCH 1), the to-be-transmitted data amount of the RLC layer entity 1 and the PDCP layer entity 1 corresponding to the LCH 1 is determined as the buffer status (BS) amount of the LCH 1; similarly, for the LCH 2, the to-be-transmitted data amount of the RLC layer entity 2 and the PDCP layer entity 1 corresponding to the LCH 2 is determined as the BS amount of the LCH 2. As can be seen, in this way, the to-be-transmitted data amount of the PDCP layer entity 1 is calculated in the calculation of the BS amount of the LCH 1 and the LCH 2. For example, the to-be-transmitted data of the PDCP layer entity 1 includes a data packet 1 and a data packet 2, the eQI corresponding to the data packet 1 is eQI 1, and the eQI corresponding to the data packet 2 is eQI 4, as shown in Table 4, the data packet 1 is mapped to the RLC layer entity 1 (or the LCH 1) for transmission, and the data packet 2 is mapped to the RLC layer entity 2 (or the LCH 2) for transmission. However, the data packet 1 and the data packet 2 are calculated in the calculation of the BS amount of the LCH 1 and the LCH 2, which causes the total BS amount reported to the network device to exceed the actual to-be-transmitted data amount of the terminal device, resulting in waste of subsequent scheduling resources.

[0193] Based on this, in the embodiments of the present application, the data amount on the PDCP layer entity can be proportionally allocated to different LCHs, and the specific proportion can be configured by the network, indicated by the application layer, or determined by the terminal device. For example, the data amount on PDCP layer entity 1 is 100, and since PDCP layer entity 1 is associated with RLC layer entity 1, RLC layer entity 2 and RLC layer entity 3, the data amount on PDCP layer entity 1 can be proportionally allocated to LCH 1, LCH 2 and LCH 3 when calculating LCH 1, LCH 2 and LCH 3. For example, the to-be-transmitted data amount of RLC layer entity 1 corresponding to LCH 1 and 40% of the to-be-transmitted data amount of PDCP layer entity 1 can be determined as the BS amount of LCH 1, the to-be-transmitted data amount of RLC layer entity 2 corresponding to LCH 2 and 30% of the to-be-transmitted data amount of PDCP layer entity 1 can be determined as the BS amount of LCH 2, and the to-be-transmitted data amount of RLC layer entity 3 corresponding to LCH 3 and 30% of the to-be-transmitted data amount of PDCP layer entity 1 can be determined as the BS amount of LCH 3. In this way, resource waste caused by the total BS amount reported to the network device exceeding the actual to-be-transmitted data amount of the terminal device can be effectively reduced.

[0194] For the above-mentioned implementation mode 1, implementation mode 2 and implementation mode 3, it should be noted that after the application layer of the first terminal device obtains the first data packet and the eQI corresponding to the first data packet, the eQI or information for indicating the eQI can be encapsulated into the first data packet, such as encapsulating the eQI or information for indicating the eQI into the header generated by the application layer for the first data packet, and then submitting it to the non-access layer. Further, after receiving the first data packet, the non-access layer (or the access layer) can strip off the header generated by the application layer to obtain the eQI corresponding to the first data packet, and then perform subsequent processing. It should be understood that the stripped-off header can not be transmitted on the air interface. Alternatively, the first terminal device can also not encapsulate the eQI into the first data packet, but submit it together with the first data packet to the non-access layer or the access layer.

[0195] From the above, it can be seen that by introducing the eQI, the embodiments of the present application realize more fine-grained differentiated processing of data packets on the air interface or the sidelink interface, so as to effectively meet the different needs of users, such as meeting the needs of real-time watching users and delay watching users.

[0196] Embodiment Two

[0197] Figure 5a The data transmission method provided in Embodiment Two of the present application corresponds to a flowchart, Figure 5b The data transmission process diagram provided in Embodiment Two of the present application.

[0198] AsFigure 5a and Figure 5b as shown, comprising:

[0199] Step 501, the terminal device 1 acquires the second data packet and the eQI and QFI corresponding to the second data packet.

[0200] Step 502, the terminal device 1 maps the second data packet to the DRB or the RLC layer entity according to the eQI and the QFI, and sends to the network device 1.

[0201] Exemplarily, the terminal device 1 can send the second data packet to the network device 1 by using the implementation manner 1 or the implementation manner 3 described in embodiment one.

[0202] Step 503, the network device 1 acquires the second data packet and the eQI and QFI corresponding to the second data packet, and sends the GTP U data packet 1 to the UPF entity 1.

[0203] Here, the GTP U data packet 1 can include the second data packet and the indication information 1, and the indication information 1 is used to indicate the eQI corresponding to the second data packet. Exemplarily, the indication information 1 can include the eQI corresponding to the second data packet, or the index of the eQI corresponding to the second data packet, or other information used to indicate the eQI corresponding to the second data packet, which is not limited in specific. Further, the indication information 1 can also be used to indicate the QFI corresponding to the second data packet. Exemplarily, the indication information 1 can be carried in the GTP U header (GTP-U header).

[0204] There are multiple ways for the network device 1 to obtain the eQI corresponding to the second data packet. In one possible way, the terminal device 1 transmits the eQI corresponding to the second data packet to the network device 1. For example, when the terminal device 1 adopts the implementation manner 1, the eQI corresponding to the second data packet (or information used to indicate the eQI corresponding to the first data packet) can be carried in the SDAP header or the PDCP header; when the terminal device adopts the implementation manner 3, the eQI corresponding to the second data packet (or information used to indicate the eQI corresponding to the first data packet) can be carried in the SDAP header or the PDCP header or the RLC header. For another example, or when the terminal device 1 adopts the implementation manner 1 or the implementation manner 3, the eQI corresponding to the second data packet (or information used to indicate the eQI corresponding to the first data packet) is not encapsulated in the second data packet, but is transmitted to the network device 1 together with the second data packet. In another possible way, the terminal device 1 does not transmit the eQI corresponding to the second data packet to the network device 1, and the network device 1 can determine the eQI corresponding to the second data packet according to the DRB or the RLC layer entity that carries the second data packet. For example, when the terminal device adopts the implementation manner 1, if the DRB corresponds to one eQI, the network device can determine the eQI corresponding to the second data packet according to the DRB that carries the second data packet; when the terminal device adopts the implementation manner 3, if the RLC layer entity corresponds to one eQI, the network device can determine the eQI corresponding to the second data packet according to the RLC layer entity that carries the second data packet.

[0205] In step 504, the UPF entity 1 obtains the second data packet, the eQI corresponding to the second data packet and the QFI, and transmits the second data packet, the eQI corresponding to the second data packet and the QFI to the UPF entity 2 through an IMS network or a server.

[0206] Here, the UPF entity 1 can send an IP packet 1 to an IP multimedia subsystem (IMS) network or a vedio server, the IP packet 1 including the second data packet and indication information 1, which can be carried in a certain layer protocol header of the IP packet 1. Correspondingly, the IMS network or the vedio server sends an IP packet 2 to the UPF entity 2, the IP packet 2 including the second data packet and the indication information 1, which can be carried in a certain layer protocol header of the IP packet 2.

[0207] In step 505, the UPF entity 2 obtains the second data packet, the eQI corresponding to the second data packet and the QFI, and sends a GTP U packet 2 to the network device 2.

[0208] Here, the GTP U packet 2 can include the second data packet and the indication information 1.

[0209] Step 506, the network device 2 acquires the second data packet, the eQI and the QFI corresponding to the second data packet, and transmits the second data packet to the terminal device 2 according to the eQI and the QFI corresponding to the second data packet.

[0210] Here, the network device 2 can transmit the second data packet to the terminal device 2 by using the implementation manner 1 or the implementation manner 3 described in embodiment one. It should be understood that, since the network device 2 does not have an application layer and a non-access layer, when using the implementation manner 1 or the implementation manner 3, after the network device 2 acquires the second data packet, the eQI and the QFI corresponding to the second data packet from the GTP-U data packet, the network device 2 can submit the second data packet, the eQI and the QFI corresponding to the second data packet to the SDAP layer entity to perform corresponding operations. For example, when using the implementation manner 1, the SDAP layer entity can map the second data packet into the DRB corresponding to the eQI and the QFI according to the eQI and the QFI corresponding to the second data packet; when using the implementation manner 3, the SDAP layer entity can map the second data packet into the DRB corresponding to the QFI according to the QFI corresponding to the second data packet, and then the PDCP layer entity corresponding to the DRB can map the second data packet into the RLC layer entity corresponding to the eQI according to the eQI corresponding to the second data packet.

[0211] By using the above method, the QoS of the data packet is further refined on the basis of the existing QFI, and the data packet is processed in an end-to-end manner through the QFI and the eQI.

[0212] Embodiment three

[0213] Figure 6a A flowchart of a data transmission method provided by the embodiment three of the present application is shown in Figure 6b A data transmission process diagram provided by the embodiment three of the present application is shown in

[0214] As shown in Figure 6a and Figure 6b , comprising:

[0215] Step 601, the terminal device 1 acquires the second data packet and the eQI corresponding to the second data packet, and determines the QFI' corresponding to the second data packet according to the eQI corresponding to the second data packet.

[0216] Step 602, the terminal device 1 maps the second data packet to the DRB according to the QFI' corresponding to the second data packet, and transmits the second data packet to the network device 1.

[0217] Exemplarily, the terminal device 1 can transmit the second data packet to the network device 1 by using the implementation manner 2 described in embodiment one.

[0218] At step 603, the network device 1 obtains the second data packet and the QFI' corresponding to the second data packet, and sends the GTP U data packet 1 to the UPF entity 1.

[0219] Here, the GTP U data packet 1 can include the second data packet and the indication information 2, and the indication information 2 is used to indicate the QFI' corresponding to the second data packet. For example, the indication information 2 can include the QFI' corresponding to the second data packet, or an index of the QFI' corresponding to the second data packet, or other information used to indicate the QFI' corresponding to the second data packet, which is not limited in particular. For example, the indication information 2 can be carried in the GTP U header.

[0220] The network device 1 can obtain the QFI' corresponding to the second data packet in various ways, for example, the network device can obtain the QFI corresponding to the data packet in the prior art, which is not described herein.

[0221] At step 604, the UPF entity 1 obtains the second data packet and the QFI' corresponding to the second data packet, and transmits the second data packet and the QFI' corresponding to the second data packet to the UPF entity 2 through the IMS network or the video server.

[0222] At step 605, the UPF entity 2 obtains the second data packet and the QFI' corresponding to the second data packet, and sends the GTP U data packet 2 to the network device 2.

[0223] Here, the GTP U data packet 2 can include the second data packet and the indication information 2.

[0224] At step 606, the network device 2 obtains the second data packet and the QFI' corresponding to the second data packet, and sends the second data packet to the terminal device 2 according to the QFI' corresponding to the second data packet.

[0225] Here, the network device 2 can transmit the second data packet to the terminal device 2 by using the implementation manner 2 described in embodiment one. It should be understood that, since the network device does not have an application layer and a non-access layer, when the implementation manner 2 is used, after the network device 2 obtains the second data packet and the QFI' corresponding to the second data packet from the GTP-U data packet, the network device 2 can submit the second data packet and the QFI' corresponding to the second data packet to the SDAP layer entity to perform corresponding operations. For example, the SDAP layer entity can map the second data packet to the DRB corresponding to the QFI' according to the QFI' corresponding to the second data packet.

[0226] By using the above method, the QFI is improved to the QFI' to realize the refinement of the QoS of the data packet, and the data packet is processed in an end-to-end manner through the QFI'.

[0227] The above describes the scheme provided by the embodiments of the present application mainly from the perspective of device interaction. It can be understood that, in order to implement the above functions, the network device or the terminal device can include hardware structure and / or software module corresponding to each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed in the present text, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is implemented in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0228] The embodiments of the present application can divide the functional units of the terminal device and the network device according to the above method examples, for example, each functional unit can be divided according to each function, or two or more functions can be integrated in one unit. The integrated unit can be implemented in the form of hardware or software functional unit.

[0229] In the case of using the integrated unit, Figure 7 A possible exemplary block diagram of the apparatus involved in the embodiments of the present application is shown. As shown in the figure, Figure 7 The apparatus 700 can include a processing unit 702 and a communication unit 703. The processing unit 702 is used to control and manage the actions of the apparatus 700. The communication unit 703 is used to support the communication of the apparatus 700 with other devices. Optionally, the communication unit 703, also called a transceiver unit, can include a receiving unit and / or a sending unit, used to perform receiving and sending operations respectively. The apparatus 700 can also include a storage unit 701, used to store the program code and / or data of the apparatus 700.

[0230] In an embodiment, the apparatus 700 can be a terminal device (or a chip configured in the terminal device) in any of the above embodiments, such as the first terminal device in Embodiment One, the terminal device 1 in Embodiment Two, or the terminal device 1 in Embodiment Three; wherein the processing unit 702 can enable the apparatus 700 to perform the actions of the terminal device in the above method examples; or the processing unit 702 mainly performs the internal actions of the terminal device in the method examples, and the communication unit 703 can enable the apparatus 700 to communicate with other devices (such as network devices). Alternatively, the apparatus 700 can be a network device (or a chip configured in the network device) in any of the above embodiments, such as the network device 2 in Embodiment Two or the network device 2 in Embodiment Three; wherein the processing unit 702 can enable the apparatus 700 to perform the actions of the network device in the above method examples; or the processing unit 702 mainly performs the internal actions of the network device in the method examples, and the communication unit 703 can enable the apparatus 700 to communicate with other devices (such as terminal devices).

[0231] For example, in this embodiment, the communication unit 703 is configured to obtain the data packet and the first QoS parameter and the second QoS parameter corresponding to the data packet; and the processing unit 702 is configured to map the data packet to the DRB or the RLC layer entity according to the first QoS parameter and the second QoS parameter, and send the data packet to the second communication apparatus through the communication unit 703.

[0232] In a possible design, the first QoS parameter or information used to indicate the first QoS parameter is carried in the data packet.

[0233] In a possible design, the apparatus 700 is a terminal device, and the first QoS parameter is assigned to the data packet by an application layer of the apparatus 700.

[0234] In a possible design, the apparatus 700 is a network device; and the communication unit 703 is specifically configured to receive a GTP-U data packet from a core network device, wherein the GTP-U data packet includes the data packet and indication information used to indicate the first QoS parameter.

[0235] In a possible design, the communication unit 703 is further configured to obtain the correspondence between the first QoS parameter, the second QoS parameter, and the DRB; and the processing unit 702 is specifically configured to map the data packet to the DRB corresponding to the first QoS parameter and the second QoS parameter according to the correspondence.

[0236] In a possible design, the apparatus 700 is a terminal device, and the communication unit 703 is specifically configured to obtain the correspondence from a network device, wherein the correspondence is carried in RRC signaling.

[0237] In a possible design, the apparatus 700 is a terminal device, and the processing unit 702 is further configured to map the data packet to a default DRB if it is determined that there is no correspondence relationship.

[0238] In a possible design, the default DRB is configured by the network device, or is a DRB with the minimum or maximum DRB ID among the DRBs associated with the second QoS parameter.

[0239] In a possible design, the apparatus 700 is a terminal device, and the processing unit 702 is further configured to send, through the communication unit 703, a first request message to the network device if it is determined that there is no correspondence relationship, where the first request message includes the first QoS parameter and the second QoS parameter.

[0240] In a possible design, the communication unit 703 is further configured to receive a first response message from the network device, where the first response message is used to indicate the DRB corresponding to the first QoS parameter and the second QoS parameter, and the processing unit 702 is further configured to map the data packet to the DRB corresponding to the first QoS parameter and the second QoS parameter according to the first response message.

[0241] In a possible design, the first QoS parameter or information used to indicate the first QoS parameter is carried in an SDAP header or a PDCP header of the data packet.

[0242] In a possible design, the processing unit 702 is specifically configured to determine the second QoS parameter corresponding to the data packet according to the first QoS parameter, and map the data packet to the DRB corresponding to the second QoS parameter according to the correspondence relationship between the second QoS parameter and the DRB.

[0243] In a possible design, the communication unit 703 is further configured to obtain the correspondence relationship between the first QoS parameter and the second QoS parameter from a core network device.

[0244] In a possible design, the processing unit 702 is specifically configured to map the data packet to the DRB corresponding to the second QoS parameter, where the DRB corresponds to at least one RLC layer entity of a packet data convergence protocol (PDCP) layer entity, and obtain, through the communication unit 703, a correspondence relationship between the first QoS parameter and the RLC layer entity, and then map the data packet to an RLC layer entity corresponding to the first QoS parameter in the at least one RLC layer entity according to the correspondence relationship.

[0245] In a possible design, the apparatus 700 is a terminal device, and the communication unit 703 is further configured to: acquire the correspondence from a network device, where the correspondence is carried in RRC signaling.

[0246] In a possible design, the apparatus 700 is a terminal device, and the processing unit 702 is further configured to: if it is determined that there is no correspondence, map the data packet to a default RLC layer entity.

[0247] In a possible design, the default RLC layer entity is configured by a network device, or is an RLC layer entity with a minimum or maximum logical channel (LCH) ID corresponding to the at least one RLC layer entity.

[0248] In a possible design, the apparatus 700 is a terminal device, and the processing unit 702 is further configured to: if it is determined that there is no correspondence, send, by the communication unit 703, a second request message to a network device, where the second request message includes the first QoS parameter.

[0249] In a possible design, the communication unit 703 is further configured to: receive a second response message from a network device, where the second response message is used to indicate an RLC layer entity corresponding to the first QoS parameter; and the processing unit 702 is further configured to: map the data packet to the RLC layer entity corresponding to the first QoS parameter according to the second response message.

[0250] In a possible design, the PDCP layer entity is configured with multiple sets of parameters, and the first QoS parameter corresponds to a set of parameters in the multiple sets of parameters; and the processing unit 702 is further configured to: process the data packet according to the parameters corresponding to the first QoS parameter.

[0251] In a possible design, the PDCP layer entity is associated with multiple RLC layer entities, and the first QoS parameter corresponds to at least two RLC layer entities in the multiple RLC layer entities; the at least two RLC layer entities are configured to implement a duplicate transmission function; the communication unit 703 is further configured to: receive indication information from the second communication apparatus, where the indication information is used to indicate an RLC layer entity in the at least two RLC layer entities corresponding to the first QoS parameter and used to implement the duplicate transmission function; and the processing unit 702 is further configured to: map the data packet to the RLC layer entity used to implement the duplicate transmission function.

[0252] In a possible design, the first QoS parameter or information used to indicate the first QoS parameter is carried in an SDAP header or a PDCP header or an RLC header of a data packet.

[0253] In yet another embodiment, the apparatus 700 can be a network device (or a chip configured in a network device) in any of the above embodiments, such as the network device 1 in Embodiment Two or the network device 1 in Embodiment Three; wherein the processing unit 702 can support the apparatus 700 to perform the actions of the network device in the above method examples; or the processing unit 702 mainly performs the internal actions of the network device in the method examples, and the communication unit 703 can support the apparatus 700 to communicate with other devices (such as core network devices).

[0254] For example, in this embodiment, the communication unit 703 is configured to: obtain a data packet, a first QoS parameter and a second QoS parameter corresponding to the data packet; and send a GTP-U data packet to a core network device, wherein the GTP-U data packet comprises the data packet and indication information, and the indication information is used to indicate the first QoS parameter and the second QoS parameter.

[0255] In a possible design, the communication unit 703 is specifically configured to: receive the data packet from a terminal device, wherein the data packet is carried on a first DRB or a first RLC layer entity; and the processing unit 702 is configured to: obtain the first QoS parameter according to the first DRB or the first RLC layer entity; or the communication unit 703 receives the data packet from the terminal device, wherein the data packet carries the first QoS parameter or information used to indicate the first QoS parameter.

[0256] In a possible design, the data packet carries the first QoS parameter or the information used to indicate the first QoS parameter, including that the first QoS parameter or the information used to indicate the first QoS parameter is carried in an SDAP header or a PDCP header or an RLC header of the data packet.

[0257] In a possible design, the indication information is carried in a GTP-U header of the GTP-U data packet.

[0258] It should be understood that the division of units in the above apparatus is only a logical functional division, and in actual implementation, all or part of the units can be integrated into one physical entity, or can be physically separated. The units in the apparatus can all be implemented in the form of software invoked by a processing element; or all be implemented in the form of hardware; or part of the units are implemented in the form of software invoked by a processing element, and part of the units are implemented in the form of hardware. For example, each unit can be a separately established processing element, or can be integrated in a chip of the apparatus, in addition, the unit can also be stored in the form of a program in a memory, and the function of the unit is invoked and executed by a processing element of the apparatus. In addition, all or part of the units can be integrated together, or can be independently implemented. The processing element described herein can be a processor, which can be an integrated circuit with a signal processing capability. In the implementation process, each step of the above method or each unit can be implemented by an integrated logic circuit of hardware in the processing element, or in the form of software invoked by the processing element.

[0259] In one example, the units in any of the above apparatuses can be one or more integrated circuits configured to implement the above method, for example, one or more application specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the units in the apparatus can be implemented in the form of a program invoked by a processing element, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor capable of invoking programs. For another example, the units can be integrated together to implement in the form of a system-on-a-chip (SOC).

[0260] The above receiving unit is an interface circuit of the apparatus for receiving signals from other apparatuses. For example, when the apparatus is implemented in the form of a chip, the receiving unit is an interface circuit of the chip for receiving signals from other chips or apparatuses. The above transmitting unit is an interface circuit of the apparatus for transmitting signals to other apparatuses. For example, when the apparatus is implemented in the form of a chip, the transmitting unit is an interface circuit of the chip for transmitting signals to other chips or apparatuses.

[0261] Please refer to Figure 8, which is a structural diagram of a terminal device provided in an embodiment of the present application. It can be the terminal device in the above embodiment, used to implement the operations of the terminal device in the above embodiment. Figure 8 As shown, the terminal device includes an antenna 810, a radio frequency section 820, and a signal processing section 830. Antenna 810 is connected to radio frequency section 820. In the downlink direction, radio frequency section 820 receives information sent by network devices via antenna 810 and sends the information to signal processing section 830 for processing. In the uplink direction, signal processing section 830 processes the information from the terminal device and sends it to radio frequency section 820. Radio frequency section 820 then processes the information from the terminal device and sends it to the network device via antenna 810.

[0262] The signal processing unit 830 may include a modem subsystem for processing data at various communication protocol layers; a central processing unit for processing the terminal device's operating system and application layers; and other subsystems, such as a multimedia subsystem for controlling the terminal device's camera and screen display, and a peripheral subsystem for connecting to other devices. The modem subsystem may be a separate chip.

[0263] The modem subsystem may include one or more processing elements 831, such as a main control CPU and other integrated circuits. Furthermore, the modem subsystem may include a storage element 832 and an interface circuit 833. Storage element 832 is used to store data and programs. However, the program used to execute the method performed by the terminal device in the above method may not be stored in storage element 832, but rather in a memory external to the modem subsystem, and loaded by the modem subsystem when in use. Interface circuit 833 is used to communicate with other subsystems.

[0264] The modem subsystem can be implemented using a chip comprising at least one processing element and an interface circuit, wherein the processing element is configured to execute each step of any of the methods performed by the terminal device described above, and the interface circuit is configured to communicate with other devices. In one implementation, the unit for implementing each step of the method described above can be implemented as a processing element scheduler. For example, the terminal device may include a processing element and a storage element, with the processing element invoking a program stored in the storage element to execute the method performed by the terminal device in the above method embodiments. The storage element can be a storage element located on the same chip as the processing element, i.e., an on-chip storage element.

[0265] In another implementation, the program for performing the method performed by the terminal device in the above method can be stored in a storage element which is different from the processing element, i.e., an off-chip storage element. At this time, the processing element calls or loads the program from the off-chip storage element to the on-chip storage element to call and perform the method performed by the terminal device in the above method embodiment.

[0266] In yet another implementation, the unit for implementing each step in the above method of the terminal device can be one or more processing elements which are configured on a modem subsystem. Here, the processing element can be an integrated circuit, such as one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these integrated circuit forms. These integrated circuits can be integrated together to form a chip.

[0267] The unit for implementing each step in the above method of the terminal device can be integrated together to form a SOC chip for implementing the above method. The chip can integrate at least one processing element and a storage element, and the method performed by the terminal device can be implemented in the form that the processing element calls the stored program of the storage element; or the chip can integrate at least one integrated circuit for implementing the method performed by the terminal device; or the functions of some units can be implemented in the form of calling programs by processing elements, and the functions of some units can be implemented in the form of integrated circuits.

[0268] It can be seen that the above apparatus for the terminal device can include at least one processing element and an interface circuit, wherein the at least one processing element is used to perform any of the methods performed by the terminal device provided in the above method embodiments. The processing element can perform part or all of the steps performed by the terminal device in the first way, i.e., by calling the program stored in the storage element; or in the second way, i.e., by the integrated logic circuit of the hardware in the processing element in combination with instructions; or in a combination of the first way and the second way.

[0269] Here, the processing element can be implemented by a processor, and the functions of the processing element can be the same as the functions of the processing unit described in Figure 7 For example, the processing element can be a general-purpose processor, such as a CPU, and can also be one or more integrated circuits configured to implement the above method, such as one or more ASICs, or one or more microprocessors DSPs, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. The storage element can be implemented by a memory, and the functions of the storage element can be the same as the functions of the storage unit described in Figure 7The storage units described in the above embodiments have the same functions. The storage element can be one memory or a collective name of multiple memories.

[0270] Figure 8 The terminal device shown can implement the method embodiments shown in Figure 3 、 Figure 5a or Figure 6a The various processes of the terminal device involved in the method embodiments are described below. Figure 8 The operations and / or functions of the various modules in the terminal device are described below to implement the corresponding processes in the above method embodiments. For details, refer to the descriptions in the above method embodiments, and the detailed descriptions are appropriately omitted here.

[0271] Please refer to Figure 9 , which is a structural schematic diagram of a network device provided by the embodiments of the present application. The network device is used to implement the operations of the network device in the above embodiments. As shown in Figure 9 , the network device includes an antenna 901, a radio frequency device 902, and a baseband device 903. The antenna 901 is connected to the radio frequency device 902. In the uplink direction, the radio frequency device 902 receives the information sent by the terminal device through the antenna 901, and sends the information sent by the terminal device to the baseband device 903 for processing. In the downlink direction, the baseband device 903 processes the information of the terminal device and sends it to the radio frequency device 902. The radio frequency device 902 processes the information of the terminal device and sends it to the terminal device through the antenna 901.

[0272] The baseband device 903 can include one or more processing elements 9031, such as a master CPU and other integrated circuits. In addition, the baseband device 903 can also include a storage element 9032 and an interface 9033. The storage element 9032 is used to store programs and data; the interface 9033 is used to interact with the radio frequency device 902, for example, a common public radio interface (CPRI). The above devices for the network device can be located in the baseband device 903, for example, the above devices for the network device can be a chip on the baseband device 903, which includes at least one processing element and an interface circuit. The processing element is used to execute each step of any method executed by the above network device, and the interface circuit is used to communicate with other devices. In one implementation, the unit of the network device that implements each step of the above method can be implemented in the form of a program scheduled by a processing element, for example, the device for the network device includes a processing element and a storage element. The processing element calls the program stored in the storage element to execute the method executed by the network device in the above method embodiments. The storage element can be a storage element on the same chip as the processing element, i.e., an on-chip storage element, or a storage element on a different chip from the processing element, i.e., an off-chip storage element.

[0273] In an implementation, the unit of the network device that implements each step of the above method can be one or more processing elements configured on a baseband device. The processing element can be an integrated circuit, such as one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of such integrated circuits. The integrated circuits can be integrated together to form a chip.

[0274] The unit of the network device that implements each step of the above method can be integrated together to form a system-on-a-chip (SOC) device, such as a baseband chip that includes the SOC device to implement the above method. The chip can include at least one processing element and a memory element. The processing element can invoke a stored program in the memory element to implement the method performed by the network device. Alternatively, the chip can include at least one integrated circuit to implement the method performed by the network device. Alternatively, a combination of the above implementations can be used, in which some units are implemented by the processing element invoking a program and some units are implemented by the integrated circuit.

[0275] It can be seen that the above apparatus for the network device can include at least one processing element and an interface circuit. The at least one processing element is configured to perform any of the methods performed by the network device as provided in the above method embodiments. The processing element can perform some or all of the steps of the network device in a first manner, i.e., by invoking a stored program in a memory element. The processing element can also perform some or all of the steps of the network device in a second manner, i.e., by the integrated logic circuit of the hardware in the processing element in combination with instructions. Of course, a combination of the first manner and the second manner can also be used to perform some or all of the steps of the network device.

[0276] The processing element can be implemented by a processor as described above. The function of the processing element can be the same as the function of the processing unit as described in Figure 7 The processing element can be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above method, such as one or more ASICs, or one or more microprocessors, DSPs, FPGAs, or a combination of at least two of these integrated circuit forms. The memory element can be implemented by a memory. The function of the memory element can be the same as the function of the storage unit as described in Figure 7 The memory element can be one memory or a plurality of memories.

[0277] Figure 9 The network device shown can implement the method as described in Figure 5a orFigure 6a The various processes involved in the illustrated method embodiments involve network devices. Figure 9 The operations and / or functions of the various modules in the illustrated network devices are respectively configured to implement the corresponding flows in the above-described method embodiments. For brevity, detailed descriptions are omitted here, which can be found in the descriptions of the above-described method embodiments.

[0278] Those skilled in the art will appreciate that embodiments of the present application can be readily used as a method, a system or a computer program product. Accordingly, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, etc.) embodying computer-readable program code.

[0279] The present application is described in reference to the flowcharts and / or block diagrams of the method, apparatus (system) and computer program product according to the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, a special purpose computer, an embedded processor or other programmable data processing device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, create means for implementing the functions specified in the flowchart flow or flows and / or block diagram block or blocks.

[0280] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the functions specified in the flowchart flow or flows and / or block diagram block or blocks.

[0281] These computer program instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in the flowchart flow or flows and / or block diagram block or blocks.

[0282] Obviously, those skilled in the art can make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, it is intended to include these modifications and variations as well.

Claims

1. A data transmission method, characterized by, The method comprises: The first communication device acquires a data packet and a first QoS parameter and a second QoS parameter corresponding to the data packet; The first communication device maps the data packet to a data radio bearer (DRB) or a radio link control (RLC) layer entity according to the first QoS parameter and the second QoS parameter, and sends the data packet to a second communication device; The first QoS parameter is a first QoS granularity in a PDU session, the second QoS parameter is a second QoS granularity in the PDU session, the first QoS granularity is smaller than the second QoS granularity, and the second QoS parameter is used to identify a QoS flow.

2. The method of claim 1, wherein, The first QoS parameter or information used to indicate the first QoS parameter is carried in the data packet.

3. The method of claim 1, wherein, The first communication device is a terminal device, and the first QoS parameter is allocated by an application layer of the first communication device for the data packet.

4. The method of claim 1, wherein, The first communication device is a network device. The first communication device acquires a data packet and a first QoS parameter corresponding to the data packet, which comprises: The first communication device receives a GTP-U data packet from a core network device, the GTP-U data packet comprising the data packet and indication information, the indication information being used to indicate the first QoS parameter.

5. The method according to any one of claims 1 to 4, characterized in that, The first communication device maps the data packet to a DRB according to the first QoS parameter and the second QoS parameter, which comprises: The first communication device acquires a correspondence relationship between the first QoS parameter, the second QoS parameter, and a DRB; The first communication device maps the data packet to a DRB corresponding to the first QoS parameter and the second QoS parameter according to the correspondence relationship.

6. The method of claim 5, wherein, The first communication device is a terminal device, and the first communication device acquires the correspondence relationship, which comprises: The first communication device acquires the correspondence relationship from a network device, the correspondence relationship being carried in RRC signaling.

7. The method of claim 5, wherein, The first communication device is a terminal device, and the method further comprises: If the first communication device determines that there is no correspondence relationship, the first communication device maps the data packet to a default DRB.

8. The method of claim 7, wherein, The default DRB is configured by a network device, or is a DRB with the smallest or largest DRB ID among DRBs associated with the second QoS parameter.

9. The method of claim 5, wherein, The first communication device is a terminal device, and the method further comprises: If the first communication device determines that there is no correspondence relationship, the first communication device sends a first request message to a network device, the first request message comprising the first QoS parameter and the second QoS parameter.

10. The method of claim 9, wherein, The method further comprises that the first communication device receives a first response message from a network device, the first response message being used to indicate a DRB corresponding to the first QoS parameter and the second QoS parameter; The first communication device maps the data packet to a DRB according to the first QoS parameter and the second QoS parameter, which comprises that the first communication device maps the data packet to a DRB corresponding to the first QoS parameter and the second QoS parameter according to the first response message.

11. The method of claim 5, wherein, The first QoS parameter or information used for indicating the first QoS parameter is carried in an SDAP header or a PDCP header of the data packet.

12. The method according to any one of claims 1 to 4, characterized in that, The first communication device maps the data packet to a DRB according to the first QoS parameter and the second QoS parameter, including: The first communication device determines the second QoS parameter corresponding to the data packet according to the first QoS parameter. The first communication device maps the data packet to a DRB corresponding to the second QoS parameter according to the second QoS parameter and the correspondence relationship between the DRB.

13. The method of claim 12, wherein, The method further includes: The first communication device obtains the correspondence relationship between the first QoS parameter and the second QoS parameter from a core network device.

14. The method of any one of claims 1 to 4, wherein, The first communication device maps the data packet to an RLC layer entity according to the first QoS parameter and the second QoS parameter, including: The first communication device maps the data packet to a DRB corresponding to the second QoS parameter according to the second QoS parameter, and a packet data convergence protocol (PDCP) layer entity corresponding to the DRB is associated with at least one RLC layer entity. The first communication device obtains a correspondence relationship between the first QoS parameter and the RLC layer entity, and maps the data packet to an RLC layer entity corresponding to the first QoS parameter in the at least one RLC layer entity according to the correspondence relationship.

15. The method of claim 14, wherein, The first communication device is a terminal device, and the first communication device obtains the correspondence relationship between the first QoS parameter and the RLC layer entity, including: The first communication device obtains the correspondence relationship from a network device, and the correspondence relationship is carried in RRC signaling.

16. The method of claim 15, wherein, The first communication device is a terminal device, and the method further includes: If the first communication device determines that there is no correspondence relationship, the first communication device maps the data packet to a default RLC layer entity.

17. The method of claim 16, wherein, The default RLC layer entity is configured by a network device, or is an RLC layer entity with a minimum or maximum logical channel (LCH) ID corresponding to the at least one RLC layer entity.

18. The method of claim 14, wherein, The first communication device is a terminal device, and the method further includes: If the first communication device determines that there is no correspondence relationship, the first communication device sends a second request message to a network device, and the second request message includes the first QoS parameter.

19. The method of claim 18, wherein, The method further includes that the first communication device receives a second response message from a network device, and the second response message is used for indicating an RLC layer entity corresponding to the first QoS parameter. The first communication device maps the data packet to the RLC layer entity corresponding to the first QoS parameter according to the second response message.

20. The method of claim 14, wherein, The PDCP layer entity is configured with multiple sets of parameters, and the first QoS parameter corresponds to a set of parameters in the multiple sets of parameters. The method further includes that the first communication device processes the data packet according to parameters corresponding to the first QoS parameter.

21. The method of claim 14, wherein, The PDCP layer entity is associated with a plurality of RLC layer entities, and the first QoS parameter corresponds to at least two RLC layer entities of the plurality of RLC layer entities; the at least two RLC layer entities are configured to implement a duplication transmission function; The PDCP layer entity of the first communication device maps the data packet to a corresponding RLC layer entity according to the first QoS parameter, including: The first communication device receives indication information from the second communication device, and the indication information is used to indicate an RLC layer entity of the at least two RLC layer entities corresponding to the first QoS parameter and used to implement a duplication transmission function; The first communication device maps the data packet to the RLC layer entity used to implement the duplication transmission function.

22. The method of claim 14, wherein, The first QoS parameter or information used to indicate the first QoS parameter is carried in an SDAP header or a PDCP header or an RLC header of the data packet.

23. A data transmission method, characterized by, The method includes: Obtaining a data packet, a first QoS parameter corresponding to the data packet, and a second QoS parameter; Sending a GTP-U data packet to a core network device, the GTP-U data packet including the data packet and indication information, the indication information being used to indicate the first QoS parameter and the second QoS parameter; The first QoS parameter is a first QoS granularity in a PDU session, the second QoS parameter is a second QoS granularity in the PDU session, the first QoS granularity is smaller than the second QoS granularity, and the second QoS parameter is used to identify a QoS flow.

24. The method of claim 23, wherein, Obtaining the first QoS parameter corresponding to the data packet includes: Receiving the data packet from a terminal device, the data packet being carried on a first DRB or a first RLC layer entity, and the first QoS parameter being obtained according to the first DRB or the first RLC layer entity; or Receiving the data packet from the terminal device, the data packet carrying the first QoS parameter or information used to indicate the first QoS parameter.

25. The method of claim 24, wherein, The data packet carries the first QoS parameter or information used to indicate the first QoS parameter, including that the first QoS parameter or information used to indicate the first QoS parameter is carried in an SDAP header or a PDCP header or an RLC header of the data packet.

26. The method of any one of claims 23-25, wherein, The indication information is carried in a GTP-U header of the GTP-U data packet.

27. A communication system, characterized by The communication system includes a network device and a core network device; The network device is configured to obtain a data packet, a first QoS parameter corresponding to the data packet, and a second QoS parameter, and send a GTP-U data packet to a core network device, the GTP-U data packet including the data packet and indication information, the indication information being used to indicate the first QoS parameter and the second QoS parameter; The core network device is configured to receive the GTP-U data packet; The first QoS parameter is a first QoS granularity in a PDU session, the second QoS parameter is a second QoS granularity in the PDU session, the first QoS granularity is smaller than the second QoS granularity, and the second QoS parameter is used to identify a QoS flow.

28. The communication system of claim 27, wherein, The communication system further includes a terminal device; The terminal device is configured to send the data packet to the network device, wherein the data packet is carried on a first DRB or a first RLC layer entity, the first DRB or the first RLC layer entity corresponds to the first QoS parameter, or the data packet carries the first QoS parameter or information used to indicate the first QoS parameter.

29. The communication system of claim 27 or 28, characterized by The core network device is further configured to send an Internet Protocol (IP) data packet, wherein the IP data packet includes the data packet and the indication information.

30. An apparatus comprising: A unit for performing each step of the method of any of claims 1-26.

31. An apparatus, comprising: An apparatus comprising at least one processor and interface circuitry, wherein the at least one processor is configured to communicate with other apparatuses via the interface circuitry and perform the method of any of claims 1-26.

32. An apparatus comprising: An apparatus comprising a processor configured to invoke a program stored in a memory to perform the method of any of claims 1-26.

33. A computer-readable storage medium, comprising: A program that, when run by a processor, causes the method of any of claims 1-26 to be performed.

34. A computer program product, characterised in that, A computer program product that, when read and executed by a computer, causes the method of any of claims 1-26 to be performed.

Images