WO2021114107A1 - 一种数据传输方法及装置 - Google Patents

一种数据传输方法及装置 Download PDF

Info

Publication number
WO2021114107A1
WO2021114107A1 PCT/CN2019/124396 CN2019124396W WO2021114107A1 WO 2021114107 A1 WO2021114107 A1 WO 2021114107A1 CN 2019124396 W CN2019124396 W CN 2019124396W WO 2021114107 A1 WO2021114107 A1 WO 2021114107A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
qos parameter
layer entity
drb
rlc layer
Prior art date
Application number
PCT/CN2019/124396
Other languages
English (en)
French (fr)
Inventor
范强
黄曲芳
娄崇
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19955950.1A priority Critical patent/EP4061051A4/en
Priority to CN201980102812.8A priority patent/CN114762386A/zh
Priority to PCT/CN2019/124396 priority patent/WO2021114107A1/zh
Publication of WO2021114107A1 publication Critical patent/WO2021114107A1/zh
Priority to US17/836,001 priority patent/US20220303825A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]

Definitions

  • This application relates to the field of wireless communication technology, and in particular to a data transmission method and device.
  • QoS quality of service
  • the terminal device analyzes the upstream data packet of the upstream service flow to obtain the five-tuple of the data packet, and determines the five-tuple according to the mapping relationship between the five-tuple and the QoS flow indicator (QFI).
  • QFI QoS flow indicator
  • the QFI corresponding to the tuple, and the QFI corresponding to the quintuple is carried in the encapsulation header of the data packet, so as to realize the mapping of the upstream service flow to the QoS flow.
  • the user plane network element can use the same method as the terminal device side to map the downstream service flow to the QoS flow.
  • PDU protocol data unit
  • SLVS social live video streaming
  • video data correspond to the same QFI, which will be mapped to the same QoS stream, which makes it impossible to distinguish the video data and affects the experience of users with different needs.
  • the present application provides a data transmission method and device to implement differentiated processing of data to meet different needs of users.
  • the embodiments of the present application provide a data transmission method, which can be applied to a first communication device, and the first communication device can be a terminal device (or a chip set in the terminal device) or a network device (or a network device). Chip inside the device).
  • the first communication device obtains the data packet and the first QoS parameter and the second QoS parameter corresponding to the data packet, and maps the data packet to DRB or RLC according to the first QoS parameter and the second QoS parameter Layer entity and sent to the second communication device.
  • the first communication device maps the first data packet to the DRB or RLC layer entity based on two QoS parameters, compared to the existing solution, the first data packet is determined according to the quintuple of the first data packet.
  • the corresponding QFI, and then mapping the first data packet to the DRB according to the QFI more comprehensively considers the service quality requirements of the first data packet, so that the data can be distinguished and processed more effectively to meet different needs of users.
  • the first QoS parameter or information used to indicate the first QoS parameter is carried in a data packet.
  • the first communication device is a terminal device, and the first QoS parameter is allocated to the data packet by the application layer of the first communication device.
  • the first communication device is a network device; the first communication device obtains the data packet and the first QoS parameter corresponding to the data packet, including: the first communication device receives the GTP-U data packet from the core network device , The GTP-U data packet includes the data packet and indication information, and the indication information is used to indicate the first QoS parameter.
  • 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 the first QoS parameter, the The corresponding relationship between the second QoS parameter and the DRB; 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 corresponding relationship.
  • the first communication device is a terminal device, and acquiring the corresponding relationship by the first communication device includes: the first communication device acquires the corresponding relationship from a network device, and the corresponding relationship is carried in RRC signaling in.
  • the first communication device is a terminal device, and the method further includes: if the first communication device determines that there is no corresponding relationship, mapping the data packet to the default DRB.
  • the default DRB is configured by the network device, or is the DRB with the smallest or largest DRB ID among the DRBs associated with the second QoS parameter.
  • the first communication device is a terminal device, and the method further includes: if the first communication device determines that there is no corresponding relationship, sending a first request message to the network device, the first request message Including the first QoS parameter and the second QoS parameter.
  • the method further includes: the first communication device receives a first response message from the network device, where the first response message is used to indicate the first QoS parameter and the second QoS parameter Corresponding DRB; 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 maps the data packet to the DRB according to the first response message DRB corresponding to the first QoS parameter and the second QoS parameter.
  • the network device can configure the DRB for the terminal device according to the request message of the terminal device, avoiding the signaling overhead and the maintenance complexity of the terminal device caused by configuring a large number of DRBs for the terminal device at the beginning.
  • the first QoS parameter or the information used to indicate the first QoS parameter is carried in the SDAP header or the PDCP header of the data packet.
  • 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 determines the data according to the first QoS parameter The second QoS parameter corresponding to the packet; the first communication device maps the data packet to the DRB corresponding to the second QoS parameter according to the correspondence between the second QoS parameter and the DRB.
  • the method further includes: the first communication device obtains the correspondence between the first QoS parameter and the second QoS parameter from a core network device.
  • the first communication device maps the data packet to the RLC layer entity according to the first QoS parameter and the second QoS parameter, including: the first communication device according to the second QoS parameter, The data packet is mapped to the DRB corresponding to the second QoS parameter, and the PDCP layer entity corresponding to the DRB is associated with at least one RLC layer entity; the first communication device obtains the first QoS parameter and the RLC layer entity Corresponding relationship, and according to the corresponding relationship, map the data packet to the RLC layer entity corresponding to the first QoS parameter in the at least one RLC layer entity.
  • the first communication device is a terminal device, and the first communication device obtains the corresponding relationship between the first QoS parameter and the RLC layer entity, including: the first communication device obtains the corresponding relationship from the network device, The corresponding relationship is carried in RRC signaling.
  • the first communication device is a terminal device, and the method further includes: if the first communication device determines that there is no corresponding relationship, mapping the data packet to the default RLC layer entity.
  • the default RLC layer entity is configured by the network device, or is the RLC layer entity with the smallest or largest corresponding logical channel LCH ID in the at least one RLC layer entity.
  • the first communication device is a terminal device, and the method further includes: if the first communication device determines that there is no corresponding relationship, sending a second request message to the network device, the second request message Including the first QoS parameter.
  • the method further includes: the first communication device receives a second response message from the network device, the second response message is used to indicate the RLC layer entity corresponding to the first QoS parameter; A communication device maps the data packet to the RLC layer entity corresponding to the first QoS parameter according to the second response message.
  • the network device can configure the RLC layer entity for the terminal device according to the request message of the terminal device, avoiding the signaling overhead and the maintenance complexity of the terminal device caused by configuring a large number of RLC layer entities for the terminal device at the beginning.
  • the PDCP layer entity is configured with multiple sets of parameters, and the first QoS parameter corresponds to one set of the multiple sets of parameters; the method further includes: The parameter corresponding to the first QoS parameter is used to process the data packet.
  • the data packets can be processed by using the corresponding parameters according to the first QoS parameters corresponding to the data packets, thereby realizing the differentiated processing of the data packets.
  • 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 The entity is configured to implement the replication transmission function; 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 from the second communication device The instruction information is used to indicate the RLC layer entity used to perform the replication transmission function among the at least two RLC layer entities corresponding to the first QoS parameter; the first communication device maps the data packet to the The RLC layer entity used to perform the replication transmission function.
  • the network device can indicate the RLC layer entity used to perform the replication transmission function, which improves the flexibility of network device regulation.
  • the first QoS parameter or the information used to indicate the first QoS parameter is carried in the SDAP header, PDCP header, or RLC header of the data packet.
  • the embodiments of the present application provide a data transmission method, which can be applied to a network device (or a chip set inside the network device).
  • the network device obtains the data packet, the first QoS parameter and the second QoS parameter corresponding to the data packet; sends a GTP-U data packet to the core network device, and the GTP-U data packet includes the data Packet and indication information, where the indication information is used to indicate the first QoS parameter and the second QoS parameter.
  • the GTP-U data packet includes the second data packet and the indication information, it is convenient to subsequently schedule the second data packet according to the first QoS parameter and the second QoS parameter, so as to realize the end-to-end update of the data packet. Fine-grained differentiation processing.
  • 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 Obtain the first QoS parameter according to the first DRB or the first RLC layer entity; or, receive the data packet from the terminal device, the data packet carrying the first QoS parameter, or Information used to indicate the first QoS parameter.
  • the data packet carries the first QoS parameter or the information used to indicate the first QoS parameter, including: the SDAP header, the PDCP header, or the RLC header of the data packet carries The first QoS parameter or information used to indicate the first QoS parameter.
  • the indication information is carried in the GTP-U header of the GTP-U data packet.
  • embodiments of the present application provide a communication system, which includes a network device and a core network device; wherein the network device is used to obtain a data packet, and the first QoS parameter and the second QoS parameter corresponding to the data packet And, sending a GTP-U data packet to a core network device, the GTP-U data packet including the data packet and indication information, and the indication information is used to indicate the first QoS parameter and the second QoS Parameter; the core network device is used to receive the GTP-U data packet.
  • the communication system further includes a terminal device for sending the data packet to the network device; wherein the data packet is carried on the first DRB or the first RLC layer entity, so 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.
  • the core network device is also used to send a network protocol IP data packet, and the IP data packet includes the data packet and the indication information.
  • the present application provides a communication device.
  • the communication device may be a terminal device (or a chip set inside the terminal device) or a network device (or a chip set inside the network device).
  • the communication device has the function of implementing the first aspect or the second aspect.
  • the communication device includes a module or unit or means corresponding to the steps involved in the first aspect or the second aspect.
  • the function Or the unit or means can be realized by software, or by hardware, and can also be realized by hardware executing corresponding software.
  • the communication device includes a processing unit and a communication unit, where the communication unit can be used to send and receive signals to achieve communication between the communication device and other devices; the processing unit can be used to perform the communication Some internal operations of the device.
  • the functions performed by the processing unit and the communication unit may correspond to the steps involved in the first aspect or the second aspect described above.
  • the communication device includes a processor, and may also include a transceiver.
  • the transceiver is used to send and receive signals, and the processor executes program instructions to complete any of the above-mentioned first or second aspects.
  • the communication device may further include one or more memories, and the memories are used for coupling with the processor.
  • the one or more memories may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory may store necessary computer programs or instructions for realizing the functions related to the first aspect or the second aspect.
  • the processor can execute the computer program or instruction stored in the memory, and when the computer program or instruction is executed, the communication device realizes any of the possible designs or implementations of the first aspect or the second aspect. method.
  • the communication device includes a processor and a memory, and the memory can store necessary computer programs or instructions for realizing the functions related to the first aspect or the second aspect.
  • the processor can execute the computer program or instruction stored in the memory, and when the computer program or instruction is executed, the communication device realizes any of the possible designs or implementations of the first aspect or the second aspect. method.
  • the communication device includes at least one processor and an interface circuit, where at least one processor is used to communicate with other devices through the interface circuit, and execute any possibility of the first aspect or the second aspect.
  • this application provides a computer-readable storage medium that stores computer-readable instructions.
  • the computer reads and executes the computer-readable instructions, the computer executes the first aspect or Any possible design method of the second aspect.
  • this application provides a computer program product, which when a computer reads and executes the computer program product, causes the computer to execute any one of the possible design methods of the first aspect or the second aspect.
  • the present application provides a chip that includes a processor, and the processor is coupled with a memory, and is configured to read and execute a software program stored in the memory to implement the above-mentioned first aspect or second aspect. Any one of the possible design methods.
  • FIG. 1a is a schematic diagram of a network architecture applicable to an embodiment of this application.
  • FIG. 1b is a schematic diagram of another network architecture to which the embodiments of this application are applicable;
  • FIG. 1c is a schematic diagram of another network architecture to which an embodiment of this application is applicable.
  • FIG. 1d is a schematic diagram of another network architecture to which an embodiment of this application is applicable.
  • 2a is a schematic diagram of downlink data transmission between various layers provided by an embodiment of this application.
  • Figure 2b is a schematic diagram of a QoS model provided by an embodiment of the application.
  • Figure 2c is a schematic diagram of a possible SLVS platform architecture provided by an embodiment of the application.
  • FIG. 2d is a schematic diagram of repeated data transmission according to an embodiment of the application.
  • FIG. 3 is a schematic diagram of a flow corresponding to the data transmission method provided in the first embodiment of the application.
  • FIG. 4a is a schematic diagram of the process corresponding to Implementation Mode 1 provided by Embodiment 1 of this application;
  • FIG. 4b is a schematic flowchart of the corresponding implementation manner 2 provided in the first embodiment of this application;
  • FIG. 4c is a schematic flow diagram corresponding to Implementation Mode 3 provided by Embodiment 1 of this application;
  • FIG. 5a is a schematic diagram of the process corresponding to the data transmission method provided in the second embodiment of the application.
  • FIG. 5b is a schematic diagram of a data transmission process provided in Embodiment 2 of this application.
  • FIG. 6a is a schematic diagram of the process corresponding to the data transmission method provided in the third embodiment of the application.
  • FIG. 6b is a schematic diagram of a data transmission process provided in Embodiment 3 of this application.
  • FIG. 7 is a possible exemplary block diagram of a device involved in an embodiment of this application.
  • FIG. 8 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • FIG. 9 is a schematic structural diagram of a network device provided by an embodiment of this application.
  • Terminal device It can be a wireless terminal device that can receive network device scheduling and instruction information.
  • a wireless terminal device can be a device that provides voice and/or data connectivity to users, or a handheld device with wireless connection function, or Other processing equipment connected to the wireless modem.
  • the terminal device can communicate with one or more core networks or the Internet via a radio access network (e.g., radio access network, RAN).
  • the terminal device can be a mobile terminal device, such as a mobile phone (or called a "cellular" phone, mobile phone). (mobile phone)), computers and data cards, for example, may be portable, pocket-sized, handheld, built-in computer or vehicle-mounted mobile devices, which exchange language and/or data with the wireless access network.
  • Wireless terminal equipment can also be called system, subscriber unit, subscriber station, mobile station, mobile station (MS), remote station (remote station), access point ( access point (AP), remote terminal equipment (remote terminal), access terminal equipment (access terminal), user terminal equipment (user terminal), user agent (user agent), subscriber station (SS), user terminal equipment (customer premises equipment, CPE), terminal (terminal), user equipment (user equipment, UE), mobile terminal (mobile terminal, MT), etc.
  • the terminal device may also be a wearable device and a next-generation communication system, for example, a terminal device in a 5G communication system or a terminal device in a public land mobile network (PLMN) that will evolve in the future.
  • PLMN public land mobile network
  • a network device may be a radio access network (radio access network, RAN) node (or device) that connects a terminal to the wireless network, and may also be called a base station.
  • RAN equipment are: new generation Node B (gNodeB), transmission reception point (TRP), evolved Node B (evolved Node B, eNB), wireless network in 5G communication system Controller (radio network controller, RNC), node B (Node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB), Or home Node B, HNB, baseband unit (BBU), wireless fidelity (Wi-Fi) access point (AP), roadside unit (RSU), The access point in the integrated access and backhaul (IAB) system, the control node and the terminal node in the TSN network, etc.
  • IAB integrated access and backhaul
  • the network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node.
  • the network device may be another device that provides wireless communication functions for the terminal device.
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the network device.
  • a device that provides a wireless communication function for a terminal device is referred to as a network device.
  • the ordinal numbers such as "first" and "second” mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the order, timing, priority, or importance of multiple objects. degree.
  • the first terminal device and the second terminal device are only used to distinguish different terminal devices, but do not indicate the difference in priority or importance of the two terminal devices.
  • FIG. 1a is a schematic diagram of a network architecture to which an embodiment of this application is applicable.
  • the terminal device 130 can access a wireless network to obtain services from an external network (such as the Internet) through the wireless network, or communicate with other devices through the wireless network, for example, it can communicate with other terminal devices.
  • the wireless network includes a radio access network (RAN) device 110 and a core network (core network, CN) device 120.
  • the RAN device 110 is used to connect the terminal device 130 to the wireless network
  • the CN device 120 is used to Manage terminal equipment and provide a gateway for communication with the external network.
  • the number of devices in the communication system shown in FIG. 1a is only for illustration, and the embodiments of the present application are not limited to this. In actual applications, the communication system may also include more terminal devices 130 and more RAN devices. 110, may also include other devices.
  • the CN may include multiple CN devices 120.
  • the CN device 120 may be an access and mobility management function (AMF) entity, session management A function (session management function, SMF) entity or a user plane function (UPF) entity, etc.
  • AMF access and mobility management function
  • SMF session management A function
  • UPF user plane function
  • the CN device 120 is an UPF entity as an example.
  • the interface between the terminal device 130 and the RAN device 110 may be called a Uu interface or an air interface
  • the interface between the RAN device 110 and the UPF entity may be called an N3 interface.
  • FIG. 1b is a schematic diagram of another network architecture to which an embodiment of this application is applicable.
  • the network architecture includes CN equipment, RAN equipment, and terminal equipment.
  • the RAN equipment includes a baseband device and a radio frequency device.
  • the baseband device can be implemented by one node or by multiple nodes.
  • the radio frequency device can be implemented remotely from the baseband device, or integrated in the baseband device, or partially pulled.
  • the remote part is integrated in the baseband device.
  • the RAN equipment (eNB) includes a baseband device and a radio frequency device, where the radio frequency device can be arranged remotely relative to the baseband device, such as a remote radio unit (RRU) arranged remotely relative to the BBU .
  • RRU remote radio unit
  • a RAN device 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.
  • FIG. 1c is a schematic diagram of another network architecture to which an embodiment of this application is applicable.
  • the control plane (CP) and the user plane (UP) of the CU can also be separated and implemented by dividing them into different entities, which are respectively the control plane (CP) CU entity ( That is, the CU-CP entity) and the user plane (UP) CU entity (ie, the CU-UP entity).
  • CP control plane
  • UP user plane
  • 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 may directly pass the protocol layer encapsulation without analyzing the signaling and transparently transmit it to the terminal device or the CU.
  • the sending or receiving of the signaling by the DU includes this scenario.
  • RRC or PDCP layer signaling will eventually be processed as PHY layer signaling and sent to the terminal device, or converted from received PHY layer signaling.
  • the RRC or PDCP layer signaling can also be considered to be sent by the DU, or sent by the DU and radio frequency load.
  • FIG. 1d is a schematic diagram of another network architecture to which the embodiments of this application are applicable.
  • the network architecture may include a RAN device 110, a CN device 120, a terminal device 1301, and a terminal device 1302.
  • the difference between the network architecture shown in FIG. 1d and the network architecture shown in FIG. 1a is that the terminal device 1301 and the terminal device 1302 in FIG. 1d can communicate through sidelink resources, such as terminal devices. 1301 may send a data packet to the terminal device 1302.
  • the network architecture shown in Figure 1a, Figure 1b, Figure 1c, or Figure 1d can be applied to various radio access technology (RAT) communication systems, such as 5G (or called new wireless (new radio)).
  • RAT radio access technology
  • radio, NR radio access technology
  • the network architecture and business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application.
  • Those of ordinary skill in the art will know that with communication With the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.
  • the devices in the following embodiments of the present application may be located in terminal equipment or network equipment according to their realized functions.
  • the network device may be a CU node, or a DU node, or a RAN device including a CU node and a DU node.
  • the communication between the network device and the UPF entity can follow a certain protocol, such as the GTP-U protocol, which is a general packet radio service Technology (general packet radio service, GPRS) tunnel transmission protocol (GPRS tunnel protocol, GTP) is one of the protocols.
  • GTP-U protocol which is a general packet radio service Technology (general packet radio service, GPRS) tunnel transmission protocol (GPRS tunnel protocol, GTP) is one of the protocols.
  • control plane protocol layer structure can include the radio resource control (RRC) layer and the packet data convergence protocol (PDCP) Layer, radio link control (RLC) layer, media access control (MAC) layer, physical layer (PHY) and other protocol layer functions;
  • user plane protocol layer structure can include PDCP
  • the functions of protocol layers such as layer, RLC layer, MAC layer, and physical layer; in a possible implementation, the PDCP layer may also include a service data adaptation protocol (SDAP) layer.
  • SDAP service data adaptation protocol
  • a network device may implement the functions of protocol layers such as RRC, PDCP, RLC, and MAC by one node, or may implement the functions of these protocol layers by multiple nodes.
  • CU and DU can be divided according to the protocol layer of the wireless network.
  • the functions of the PDCP layer and the above protocol layers are set in the CU, and the protocol layers below PDCP, such as the RLC layer and the MAC layer, etc.
  • the function is set in DU.
  • this protocol layer is just an example, and it can also be divided in other protocol layers, for example, in the RLC layer, setting the functions of the RLC layer and above protocol layers in the CU, and setting the functions of the protocol layers below the RLC layer in the DU; Or, divide in a certain protocol layer, for example, set part of the functions of the RLC layer and the functions of the protocol layer above the RLC layer in the CU, and set the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer in the DU. In addition, it can also be divided in other ways, for example, by time delay. The functions that need to meet the time delay requirements for processing time are set in the DU, and the functions that do not need to meet the delay requirements are set in the CU.
  • FIG. 2a shows a schematic diagram of downlink data transmission between layers.
  • the downward arrow indicates data transmission
  • the upward arrow indicates data reception.
  • the PDCP layer After the PDCP layer obtains the data from the upper layer, it transmits the data to the RLC layer and the MAC layer, and then the MAC layer generates a transmission block, and then performs wireless transmission through the physical layer. Data is encapsulated correspondingly in each layer.
  • the data received by a certain layer from the upper layer of the layer is regarded as the service data unit (SDU) of the layer, and after layer encapsulation, it becomes a PDU, and then is passed to the lower layer.
  • SDU service data unit
  • the data received by the PDCP layer from the upper layer is called PDCP SDU
  • the data sent by the PDCP layer to the lower layer is called PDCP PDU
  • the data received by the RLC layer from the upper layer is called RLC SDU
  • the data sent by the RLC layer to the lower layer is called RLC PDU.
  • the connections between layers are mostly corresponded in the way of channels.
  • the RLC layer and the MAC layer correspond to each other through a logical channel (LCH), and the MAC layer and the physical layer correspond to each other through a transport channel. Below the physical layer is a physical channel, which is used to correspond to the other end.
  • the physical layer is used to correspond to the other end.
  • the terminal device also has an application layer and a non-access layer; where the application layer can be used to provide services to applications installed in the terminal device, for example, the terminal device receives Downlink data can be sequentially transmitted from the physical layer to the application layer, and then provided to the application by the application layer; for example, the application layer can obtain data generated by the application (such as the video recorded by the user using the application, etc.), and transmit the data in turn To the physical layer, send to other communication devices.
  • the application layer can be used to provide services to applications installed in the terminal device, for example, the terminal device receives Downlink data can be sequentially transmitted from the physical layer to the application layer, and then provided to the application by the application layer; for example, the application layer can obtain data generated by the application (such as the video recorded by the user using the application, etc.), and transmit the data in turn To the physical layer, send 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; and, data packets in the uplink and downlink directions
  • the QFI is identified in (see the description below), for example, the QFI of the data packet in the uplink and downlink directions is determined according to the mapping relationship between the quintuple and the QFI.
  • the UPF entity can send a downlink data packet to the terminal device 130.
  • the UPF entity obtains the data packet X and uses the GTP-U protocol (GTP-U protocol is a general packet radio service technology (GPRS) tunnel transmission protocol (GPRS tunnel protocol, GTP) is encapsulated to obtain the GTP-U protocol data unit (protocol data unit, PDU), and then the GTP-U is sent to the CU through the N3 interface PDU, GTP-U PDU includes data packet X.
  • GTP-U protocol is a general packet radio service technology
  • the general packet radio service, GPRS tunnel transmission protocol, GTP GPRS tunnel protocol, GTP
  • PDU protocol data unit
  • GTP-U PDU includes data packet X.
  • the CU receives the GTP-U PDU, obtains the data packet X, and encapsulates the 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 the data packet X, encapsulates the data packet X in the MAC PDU, and sends it to the terminal device through the Uu interface.
  • the terminal device 130 may send an uplink data packet to the UPF entity.
  • the terminal device obtains the data packet Y, encapsulates the data packet Y into a MAC PDU, and sends it to the DU through the Uu interface.
  • the DU receives the data packet Y, and encapsulates the data packet Y into a PDCP PDU and delivers it to the CU through the F1-U interface.
  • the CU receives the PDCP PDU, obtains the data packet Y, encapsulates the data packet Y into a GTP-U PDU, and sends it to the UPF entity.
  • data transmission can be performed between the first terminal device (such as the terminal device 1301) and the second terminal device (such as the terminal device 1302).
  • the first terminal device obtains a data packet Z and passes The side link sends the data packet Z to the second terminal device.
  • FIG. 1a is a schematic diagram of a QoS model.
  • data packets entering 5GS are differentiated at the UPF entity.
  • the UPF entity divides the downlink data packets according to the packet filter sets of the downlink packet detection rule (packet detection rule, PDR). Different QoS flows are distinguished, and all data packets in the same QoS flow are marked with the same QFI.
  • the UPF entity transfers the data packet 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.
  • the application layer of the terminal device In the upstream direction, after the application layer of the terminal device generates the data packet, it distinguishes the upstream data packet into different QoS flows according to the packet filtering set in the QoS rules (rules) configured by the SMF entity.
  • the SDAP layer entity of the terminal device maps the data packets of the QoS flow to the corresponding DRB according to the QFI to DRB mapping relationship configured by the base station, and then performs uplink data transmission on the air interface.
  • one QoS flow can only be mapped to one DRB, and different QoS flows can be mapped to the same DRB; the mapping relationship between the QoS flow and the DRB can be determined by the network device on the AN side.
  • the QoS rules and the packet filtering set in the PDR are used to identify one or more data packet flows (such as Internet protocol (IP) flows), and the packet filtering set may include one or more packet filtering templates.
  • IP Internet protocol
  • 5GS defines two types of packet filtering sets based on PDU session types, namely, IP packet filtering sets and Ethernet (Ethernet) packet filtering sets.
  • the packet filtering set supports any combination of the following packet filtering templates: source/destination IP address or IPv6 prefix; source/destination port number; protocol identification of the protocol above the IP layer; IPv4 service type (type of service, TOS) field/IPv6 traffic category and mask; IPv6 flow label; security parameter index; packet filtering direction.
  • packet filtering templates use a combination of the first three, that is, packet filtering is performed through the five-tuple of the IP data packet (source/destination address, source/destination port number, transport layer protocol).
  • the quintuple of the IP data packet is used as the packet filtering template as an example.
  • any combination of the foregoing may also be used as the packet filtering template.
  • DRB is a logical channel for data packet transmission.
  • the network device can configure 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, through the DRB The transmitted data packets receive the same treatment on the air interface. In other words, the treatment of data packets in a QoS flow within 5GS, such as scheduling and forwarding priority, is always the same.
  • FIG. 2c is a schematic diagram of a possible SLVS platform architecture. As shown in Figure 2c, the live broadcaster first uploads the live video stream to the server, and the server provides the video stream to different types of viewers.
  • the experience of real-time viewers is prioritized (for example, only the delay-sensitive basic layer data frames can be transmitted); when the bandwidth is sufficient, further transmission can be outdated for real-time viewers. )
  • the enhancement layer data frame there are both time-sensitive data frames and data frames that are less time-sensitive but require high reliability during the transmission of the same video stream.
  • the timely transmission of TCP ACK frames is good for congestion control (that is, the TCP ACK frame requires a higher delay), so there is also importance in the same TCP data stream Different data frames.
  • the quintuple of these live video streams is the same, and the QoS guarantee of the data packet of the same quintuple in 5GS is the same, so when the broadcaster uploads the live video stream to the server.
  • the QoS stream mapped by the live video stream can only be set according to the needs of delay-sensitive users (such as ensuring the delay of data transmission, However, the transmission reliability is not high enough), and different data frames cannot be distinguished and processed, which affects the experience of delayed viewing audiences.
  • an embodiment of the present application provides a data transmission method, which is used to implement differentiated processing of data to meet different needs of users.
  • the data transmission method provided in the embodiment of the present application may include two possible solutions, namely, solution one and solution two.
  • the first communication device obtains the first data packet and the first QoS parameter and the second QoS parameter corresponding to the first data packet, and maps the first data packet to the first data packet according to the first QoS parameter and the second QoS parameter
  • the DRB or RLC layer entity is sent to the second communication device;
  • the second QoS parameter here may be QFI or QFI', and the description of the second QoS parameter can be referred to below.
  • the first communication device maps the first data packet to the DRB or RLC layer entity based on two QoS parameters, compared to the existing solution, the first data packet is determined based on the quintuple of the first data packet.
  • the corresponding QFI, and then mapping the first data packet to the DRB according to the QFI more comprehensively considers the service quality requirements of the first data packet, so that the data can be distinguished and processed more effectively to meet different needs of users.
  • solution one may be applicable to the network architecture illustrated in FIG. 1a, the first communication device may be a terminal device; the second communication device may be a network device. Alternatively, the second communication device may be a terminal device; the first communication device may be a network device.
  • the first communication device may be a terminal device (such as a first terminal device), and the second communication device may be another terminal device (such as a second terminal device). That is to say, in the first solution, 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 QoS parameter and the second QoS parameter.
  • the first communication device obtains the second data packet and the first QoS parameter and the second QoS parameter corresponding to the second data packet, and sends the GTP-U data packet to the second communication device. It includes a second data packet and indication information, where the indication information is used to indicate the first QoS parameter and the second QoS parameter; the second QoS parameter here may be QFI (different from QFI').
  • the second solution may be applicable to the network architecture shown in FIG. 1a, the first communication device may be a network device; the second communication device may be a core network device (such as a UPF entity).
  • Adopting the second scheme since the GTP-U data packet includes the second data packet and the indication information, it is convenient to schedule the second data packet according to the first QoS parameter and the second QoS parameter, so as to realize the end-to-end update of the data packet. Fine-grained differentiation processing.
  • the first QoS parameter may be called an enhanced QoS indicator (eQI) or other names, which is not specifically limited.
  • eQI enhanced QoS indicator
  • the QoS flow is the QoS differentiation granularity in the PDU session
  • the first QoS parameter can be understood as another QoS differentiation granularity in the PDU session.
  • the granularity of the first QoS parameter is finer.
  • the first QoS parameter can be used to indicate the quality of service level, for example, to indicate the quality of service level in a QoS flow, so that data packets in a QoS flow can be mapped to different DRB or RLC layer entities;
  • the reference cell of data packet offloading (filtering) for example, is used as a consideration factor of the packet filtering template, for example, used to allocate data packets in the same five-tuple data flow to different QoS flows, or to allocate different QFIs.
  • the first QoS parameter may include one or more bits, and different values of the one or more bits are used to indicate different service quality levels.
  • the indicators for determining the service quality 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, it can be based on response data packets
  • the packet delay budget required by the real-time performance and the packet error rate that reflect the transmission reliability requirements are used to determine the service quality level.
  • the service quality level can be determined based on whether the data packet is new or retransmitted.
  • the first QoS parameter includes 2 bits, and different values of the 2 bits can be used to indicate 4 different levels.
  • the first part of the data packet requires higher real-time performance and higher transmission reliability requirements, then the first QoS parameter corresponding to this part of the data packet can be marked as 00; the second part of the data packet The real-time requirement is relatively high, and the transmission reliability requirement is slightly lower, then the first QoS parameter corresponding to this part of the data packet can be marked as 01; the third part of the data packet has a slightly lower real-time requirement, and the transmission reliability requirement is relatively high, then this part
  • the first QoS parameter corresponding to the data packet can be marked as 10; the fourth part of the data packet has slightly lower real-time requirements and lower transmission reliability requirements, so the first QoS parameter corresponding to this part of the data packet can be marked as 11.
  • the first QoS parameter includes 1 bit, and different values of this bit can be used to indicate two different levels; for example, the first QoS parameter corresponding to a newly transmitted data packet at the application layer is marked as 0 , Mark the first QoS parameter corresponding to the data packet retransmitted by the application layer as 1.
  • the first QoS parameter includes 4 bits, and different values of the 4 bits can be used to indicate 16 different service quality levels.
  • the second QoS parameter can be used to identify the 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.
  • the second QoS parameter may be QFI, and the value range of QFI may be [0, 256].
  • the second QoS parameter may be the aforementioned QFI that has a corresponding relationship with the packet filtering template (such as a quintuple).
  • the packet filtering template such as a quintuple
  • the second QoS parameter corresponding to the data packet can be obtained according to the correspondence between the packet filtering template and the second QoS parameter.
  • Table 1 when a quintuple is used as a packet filtering template, an example of the correspondence between the quintuple and the second QoS parameter.
  • Table 1 Example of the correspondence between the packet filtering template and the second QoS parameter
  • the second QoS parameter may be a QFI that has a corresponding relationship with the first QoS parameter.
  • other possible parameters such as quintuples, may be introduced into the corresponding relationship. .
  • Table 2 which is an example of the corresponding relationship between the quintuple, the first QoS parameter, and the second QoS parameter.
  • the QFI corresponding to the quintuple is only a part of the QFI, and some reserved QFIs have not yet set their corresponding quintuple; in Table 2, the introduction of the first QoS Parameters, so that the data packets of the same five-tuple may correspond to different second QoS parameters due to the difference in the first QoS parameter; compared to Table 1, the reserved QFI can be used in Table 2 to compare The data packet undergoes further differentiation processing.
  • the second QoS parameter involved in Table 1 is referred to as QFI
  • the second QoS parameter involved in Table 2 is referred to as QFI'.
  • the "correspondence” referred to in the embodiments of the present application can also be replaced with “mapping relationship” or other words representing similar meanings, and “association” can also be replaced with “correspondence” or other words representing similar meanings.
  • the second QoS parameter may also be a newly defined parameter used to identify a QoS flow, and the newly defined second QoS parameter may be between the quintuple and the first QoS parameter.
  • the newly defined second QoS parameter may be between the quintuple and the first QoS parameter.
  • At least one radio bearer can be established between the sending end and the receiving end to transmit data.
  • Radio bearers can be divided into signaling radio bearer (SRB) used to transmit signaling data and data radio bearer (DRB) used to transmit service data.
  • SRB signaling radio bearer
  • DRB data radio bearer
  • a set of functional entities of the same radio bearer It includes one PDCP layer entity, at least two RLC layer entities corresponding to the PDCP layer entity, at least one MAC entity corresponding to at least two RLC layer entities, and at least one PHY entity corresponding to at least one MAC entity.
  • Repeated transmission, or repeated transmission at the PDCP layer usually refers to copying the data packets carried by the radio into multiple identical packets (that is, repeated packets) at the PDCP layer, and then these two data packets are delivered to multiple different RLC layers.
  • the entity transmits, and then transmits to the MAC layer through different logical channels.
  • the logical channel is the channel from the RLC layer to the MAC layer.
  • Resending refers to sending the same data packet again after failure, or sending the same data packet multiple times in succession, and repeated transmission is to copy one data packet to two data packets and put them on two logical channels for transmission.
  • "Repetition” here can also be understood as "copy”.
  • each RLC layer entity corresponds to a logic Channel to send data.
  • the same PDCP layer entity on the receiving end corresponds to at least two RLC layer entities, and each RLC layer entity corresponds to a logical channel to receive data. Therefore, the radio bearer between the sending end and the receiving end includes at least two logical channels.
  • the sending end may be a terminal device, and the receiving end may be a network device; alternatively, the receiving end may be a terminal device, and the sending end may be a network device.
  • the sending end may be a first terminal device (such as terminal device 1301), and the receiving end may be a second terminal device (such as terminal device 1302); or, the receiving end may be a second terminal device.
  • the sending end may be the first terminal device; in this case, the DRB between the first terminal device and the second terminal device may also be called a sidelink DRB.
  • the sending end and the receiving end shown in FIG. 2d 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, where the first RLC layer entity corresponds to the first logical channel, The second RLC layer entity corresponds to the second logical channel.
  • the sender sends the data on the first logical channel to the receiver in cell 1b or cell group 1 corresponding to the first logical channel, and the receiver receives the first logic sent by the sender in cell 1b or cell group 1 corresponding to the first logical channel.
  • Channel data The sender sends the data on the first logical channel to the receiver in cell 1b or cell group 1 corresponding to the first logical channel.
  • the transmitting end sends the data of the second logical channel to the receiving end in the cell 2b or cell group 2 corresponding to the second logical channel, and the receiving end receives the data on the second logical channel in the cell 2b or cell group 2 corresponding to the second logical channel.
  • data from the same PDCP layer entity is repeatedly transmitted on the second RLC layer entity at the sending end and the first RLC layer entity at the sending end, so that the reliability of sending data at the sending end can be improved.
  • Fig. 2d takes the sending end and the receiving end respectively corresponding to two cell groups as an example. In other possible situations, the sending end and the receiving end may also correspond to one cell group respectively, which is not specifically limited.
  • the foregoing description is based on the repetition of the PDCP layer of two logical channels as an example. In other possible embodiments, it may also be the repetition of the PDCP layer of more logical channels, that is, one
  • the radio bearer transmits data packets copied at the PDCP layer through more logical channels. For example, it is possible to transmit data packets copied at the PDCP layer through three or four logical channels.
  • the repeat transmission function of the DRB can be activated or deactivated.
  • the network device configures a first RLC layer entity and a second RLC layer entity for the PDCP layer entity of the DRB.
  • the data of the PDCP layer entity can be Repeated transmission is carried out through the first RLC layer entity and the second RLC layer entity; if the network device deactivates the DRB repeated transmission function, the data of the PDCP layer entity will no longer be repeatedly transmitted, for example, it can be transmitted through the first RLC layer entity Or through the second RLC layer entity for transmission.
  • the network device may also use control signaling to instruct the terminal device through which one or several RLC layer entities to transmit the DRB data packet; for example, the control signaling may be a MAC control element (control element CE), MAC CE It may include indication information of DRB ID and LCH ID.
  • the terminal device after receiving the MACCE, the terminal device performs data packet transmission for the indicated DRB through the indicated LCH or RLC layer entity.
  • the transmission mode of the RLC layer entity may 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 perform any processing on the SDU submitted to the RLC layer entity, and directly transmits it transparently. If the transmission mode of the RLC layer entity is UM, the RLC layer entity can process the SDU submitted to the RLC layer entity (for example, additional information can be added), and then send RLC PDU without the need for confirmation from the peer entity, and no more Perform a retransmission.
  • TM transparent mode
  • UM unacknowledged mode
  • AM acknowledged mode
  • the RLC layer entity can process the SDU submitted to the RLC layer entity (for example, additional information can be added), and then send RLC PDU, and the confirmation of the peer entity is required. If the peer entity If it is confirmed 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.
  • Buffer status report (buffer status report, BSR)
  • LCH can be used to carry data, and data of different service types can be carried by different LCHs.
  • Each LCH can be associated with a scheduling priority, which can be configured by network equipment.
  • the LCH carrying URLLC service data can be configured with a higher priority
  • the LCH carrying eMBB service data can be configured with a lower priority, that is It is said that 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, it can give priority to resource allocation for high-priority data.
  • the MAC layer of the terminal device can trigger the BSR to reflect the total amount of data to be transmitted on at least one LCH for network equipment Scheduling.
  • FIG. 3 is a schematic diagram of the process corresponding to the data transmission method provided in Embodiment 1 of the application, as shown in FIG. 3, including:
  • Step 301 The first terminal device obtains a data packet and a first QoS parameter and a second QoS parameter corresponding to the data packet.
  • the application layer of the first terminal device can obtain the data packet generated by the application and assign the first QoS parameter to the data packet, that is, the first QoS parameter can be the data packet allocated by the application layer of the first terminal device .
  • the application layer can allocate the first QoS parameter to the data packet according to multiple basis. For example, the application layer can allocate the first QoS parameter to the data packet according to the QoS requirements of the data packet. In the embodiment of this application, the application layer is allocated the first QoS parameter to the data packet.
  • the specific implementation of QoS parameters is not limited.
  • the first terminal device may be connected to other devices, and the other devices may be industrial equipment, such as sensors, operating arms, and the like. Furthermore, the first terminal device may receive data packets from other devices and the first QoS parameters corresponding to the data packets, that is, the first QoS parameters may be allocated by industrial equipment to the data packets. The industrial equipment may allocate the first QoS parameter to the data packet according to various types, which are not specifically limited. After receiving the data packet and the first QoS parameter corresponding to the data packet from the industrial device, the first terminal device may 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.
  • the first QoS parameter may be allocated to the data packet by the non-access layer of the first terminal device. For example, if the data packet includes TCP ACK, the non-access layer can identify and allocate the first QoS parameter . After the non-access layer obtains the data packet and the first QoS parameter corresponding to the data packet, it can submit the data packet and the first QoS parameter corresponding to the data packet to the access layer, or it can also determine the data packet corresponding to the data packet according to the first QoS parameter. The second QoS parameter (the second QoS parameter is QFI' at this time), and then the data packet and the second QoS parameter corresponding to the data packet are delivered to the access layer. There may be multiple basis for the non-access layer to allocate the first QoS parameter to the data packet, which is not specifically limited.
  • the first QoS parameter will be described as an example where the first QoS parameter is allocated to the data packet by the application layer of the first terminal device. Other situations can be handled by reference, and the first QoS parameter will be referred to as eQI hereinafter.
  • Step 302 The first terminal device maps the data packet to a DRB or RLC layer entity according to the eQI and the second QoS parameter corresponding to the data packet, and sends it to the network device or the second terminal device.
  • step 301 and step 302 are described.
  • the second QoS parameter may be QFI (different from QFI').
  • step 301 and step 301 may be: the application layer of the first terminal device may obtain the first data packet and the eQI corresponding to the first data packet, and then combine the first data packet and the first data packet
  • the corresponding eQI is submitted to the non-access stratum; after the non-access stratum receives the first data packet and the eQI corresponding to the first data packet, it can determine the QFI corresponding to the first data packet according to the packet filtering template in the QoS rules, and is The first data packet identifies the corresponding QFI.
  • the non-access layer delivers the first data packet and the QFI and eQI corresponding to the first data packet to the SDAP layer entity.
  • the SDAP layer entity maps the first data packet to the DRB according to the QFI and eQI corresponding to the first data packet, and sends it to the network device or the second terminal device.
  • the first terminal device may obtain the corresponding relationship between QFI, eQI and DRB (also can be described as the corresponding relationship between QFI+eQI and DRB), and then the SDAP layer entity of the first terminal device can obtain the corresponding relationship and the corresponding relationship between the first terminal device and the corresponding relationship.
  • the QFI and eQI corresponding to a data packet map the first data packet to the DRB corresponding to the QFI and eQI.
  • the corresponding relationship between QFI, eQI, and DRB can be configured by the network device through RRC signaling for the first terminal device shown. There can be multiple specific configuration methods.
  • the network device can be configured through RRC Reconfiguration (RRC Reconfiguration).
  • the SDAP configuration (SDAP-Config) information element in the DRB add (DRB-ToAddMod) information element carried in the message is used to configure the correspondence between QFI, eQI and DRB.
  • the data packets corresponding to different eQIs in the QoS flow of the same QFI can be mapped to the same or different DRBs.
  • the corresponding data packet with eQI of eQI 1 needs to be mapped to DRB 1 for processing and transmission
  • the corresponding data packet with eQI of eQI 2 needs to be mapped to DRB 2 for processing and transmission .
  • the eQI corresponding to the first data packet is eQI2
  • the QFI corresponding to the first data packet is QFI1.
  • QFI1+eQI2 corresponds to DRB2; in this case, the first terminal device
  • the SDAP layer entity can map the first data packet to DRB 2.
  • the first terminal device may send a request message 1 to the network device, and the request message 1 may include QFI 1 (or Information used to indicate QFI 1) and eQI 3 (or information used to indicate eQI 3, such as the index of eQI 3).
  • the network device may return response message 1 to the first terminal device ,
  • the response message 1 includes the DRB ID corresponding to QFI 1+eQI 3 (or the information used to indicate the DRB corresponding to QFI 1+eQI3), and the first terminal device can map the first data packet to the corresponding QFI 1+eQI 3 In the DRB. Further, the first terminal device may update Table 3 according to the DRB corresponding to QFI 1+eQI 3. In this way, the network device can configure DRB for the first terminal device according to the request message of the first terminal device, avoiding the signaling overhead caused by configuring a large number of DRBs for the first terminal device and the maintenance of the first terminal device at the beginning the complexity.
  • the first terminal device may map the first data packet to the default DRB.
  • One way to implement 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.
  • the network device is QFI 1 and configures DRB 1 as the default DRB; or, a QFI The corresponding default DRB may be determined by the first terminal device based on preset rule 1.
  • preset rule 1 may be the default DRB with the smallest/largest DRB ID of all DRBs corresponding to or associated with a QFI or the corresponding LCH ID, or The default DRB with the highest/lowest logical channel priority among all DRBs corresponding to or associated with a QFI is the default DRB. Taking Table 3 as an example, if it is determined that the DRB with the smallest ID is 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 a default DRB.
  • the default DRB can be configured by the network device or determined by the first terminal device based on the preset rule 2.
  • the preset rule 2 can be all DRBs or the same Among all DRBs associated with the SDAP layer entity, the DRB ID or the corresponding LCH ID with the smallest/largest ID is the default DRB, or the default DRB with the highest/lowest logical channel priority is the default DRB.
  • the preset rule 1 or the preset rule 2 may be predefined by the protocol, or determined by the network device and instructed to the terminal device.
  • the first terminal device maps the first data packet to the default DRB, it can also perform the operation in the previous example, that is, send request message 1 to the network device, requesting QFI 1+eQI 3 corresponds to the DRB, and Table 3 is updated, so that the next data packet corresponding to QFI 1+eQI 3 is mapped to the DRB corresponding to QFI 1+eQI 3.
  • 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, it can also send the eQI corresponding to the first data packet to the network device or the second terminal device. It is not encapsulated in a data packet, but is sent to the network device or the second terminal device layer together with the first data packet.
  • the SDAP header of the first data packet may include the eQI corresponding to the first data packet (or used to indicate the first data packet).
  • EQI information corresponding to the data packet for example, after receiving the first data packet and the QFI1 and eQI corresponding to the first data packet, the SDAP layer entity of the first terminal device can encapsulate the eQI corresponding to the first data packet into the first data packet.
  • the SDAP header of the data packet then maps the encapsulated first data packet to the DRB or submits it to the PDCP layer entity.
  • the PDCP header of the first data packet may include the eQI corresponding to the first data packet (or information used to indicate the eQI corresponding to the first data packet); for example, the SDAP layer entity delivers the first data packet to the PDCP layer entity It can also further indicate the eQI corresponding to the first data packet.
  • the PDCP layer entity receives the first data packet submitted by the SDAP layer entity, it can encapsulate the eQI corresponding to the first data packet into the PDCP of the first data packet. Head in.
  • a PDCP layer entity corresponds to only one eQI
  • the SDAP layer entity delivers the first data packet to the PDCP layer entity, it may no longer indicate the eQI corresponding to the first data packet.
  • PDCP After the layer entity receives the first data packet submitted by the SDAP layer entity, it can encapsulate the eQI corresponding to the PDCP layer entity into the PDCP header of the first data packet. Since the SDAP header or PDCP header of the first data packet includes the eQI corresponding to the first data packet, it is convenient for the second communication device to obtain the eQI corresponding to the first data packet after receiving the first data packet.
  • the network device can independently configure multiple DRBs corresponding to the same QFI, that is, the PDCP layer entity, the RLC layer entity, and the logical channel can all be independently configured.
  • 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 PDCP layer entity 1 is associated
  • the configuration of the RLC layer entity (or logical channel) and the RLC layer entity (logical channel) associated with the PDCP layer entity 2 may be different.
  • the configuration of the PDCP layer entity 1 and the PDCP layer entity 2 may refer to that the parameters of the PDCP layer entity 1 and the parameters of the PDCP layer entity 2 are different.
  • the parameters of the PDCP layer entity may include the discarding duration (the PDCP layer entity receives a PDCP A timer is started after the SDU, and the PDCP SDU discard operation is performed after the timeout.
  • the duration of the timer can be called the discard duration.
  • the discard duration of PDCP layer entity 1 is 10ms
  • the discard of PDCP layer entity 2 The duration is 20ms.
  • the configuration difference between the RLC layer entity associated with PDCP layer entity 1 (for example, including RLC layer entity 1) and the RLC layer entity associated with PDCP layer entity 2 (for example, including RLC layer entity 1a) may refer to the transmission mode and RLC of RLC layer entity 1
  • the transmission mode of the layer entity 1a is different.
  • the transmission mode of the RLC layer entity 1 is UM
  • the transmission mode of the RLC layer entity 1a is AM.
  • the second QoS parameter may be QFI'.
  • 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 combine the first data packet and the first data packet The corresponding eQI is submitted to the non-access stratum; after the non-access stratum receives the first data packet and the eQI corresponding to the first data packet, it can determine the QFI' corresponding to the first data packet, and identify the corresponding QFI for the first data packet QFI'. The non-access layer delivers 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 the DRB according to the QFI' corresponding to the first data packet, and sends it to the network device or the second terminal device.
  • the first terminal device may obtain the corresponding relationship shown in Table 2, and the non-access layer of the first terminal device may use the corresponding relationship shown in Table 2 and the eQI and quintuple corresponding to the first data packet. , Determine the QFI' corresponding to the first data packet.
  • the first terminal device can obtain the corresponding relationship shown in Table 2 in many ways.
  • the corresponding relationship shown in Table 2 can be configured by the core network device for the first terminal device through a non-access layer message, such as SMF.
  • the entity configures the first terminal device through a PDU session establishment/modification process.
  • data packets of 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.
  • 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 corresponding relationship between QFI' and DRB ID according to the corresponding relationship between QFI' and DRB ID. DRB.
  • the first terminal device may obtain the corresponding relationship between QFI' and DRB ID from the network device.
  • the manner in which the first terminal device obtains the corresponding relationship between QFI' and DRB ID can also refer to the manner in which the terminal device obtains the corresponding relationship between QFI and DRB ID in the existing solution, and details are not described again.
  • the data packets of different eQIs can be distinguished and processed, that is, the delay or reliability requirements are different.
  • the data packets are differentiated and processed on the air interface.
  • this method does not need to change the operation of the access layer, and has strong applicability.
  • the second QoS parameter may be QFI (different from QFI').
  • step 301 and step 302 may be: the application layer of the first terminal device may obtain the first data packet and the eQI corresponding to the first data packet, and then combine the first data packet and the first data packet The corresponding eQI is submitted to the non-access stratum; after the non-access stratum receives the first data packet and the eQI corresponding to the first data packet, it can determine the QFI corresponding to the first data packet according to the packet filtering template in the QoS rules, and is The first data packet identifies the corresponding QFI.
  • the non-access layer delivers the first data packet and the QFI and eQI corresponding to the first data packet 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 according to the QFI corresponding to the first data packet (that is, to the PDCP layer entity corresponding to the DRB), and the PDCP layer entity according to the eQI corresponding to the first data packet ,
  • the first data packet is mapped to the RLC layer entity or LCH, and sent to the network device or the second terminal device.
  • the PDCP layer entity corresponding to the DRB can be associated with multiple RLC layer entities, and multiple RLC layer entities have a corresponding relationship with the eQI.
  • the network device can configure multiple RLC layer entities associated with the PDCP layer entity for the terminal device, and the corresponding relationship between eQI and RLC layer entity; there can be multiple specific configuration methods.
  • the network device is When an RLC layer entity or a logical channel corresponding to an RLC layer entity is configured, the DRB ID and eQI set are indicated in the configuration cell, indicating that the RLC layer entity is associated with the PDCP layer entity corresponding to the DRB ID, and the RLC layer entity corresponds to
  • the eQI is the eQI included in the eQI set (or the RLC layer entity is used to process data packets mapped to the DRB and the corresponding eQI is the eQI included in the eQI set); the above eQI set may include one eQI, or multiple eQI.
  • the DRB ID indicated by the network device in the configuration cell (RLC-BearerConfig or RLC-Config) of the RLC layer entity 1 is DRB 1
  • the indicated eQI set includes eQI 1 and eQI 2
  • the first terminal device can It is learned 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 RLC layer entity 1 is used to process the mapping to the DRB 1 and the corresponding eQI is eQI 1 or eQI 2 data packet).
  • the content of the corresponding LCH may also be adaptively extended where the RLC entity is involved in the embodiment of the present application.
  • multiple RLC layer entities have a correspondence relationship with eQI, and it can also be adaptively extended to obtain multiple LCH layer entities corresponding to multiple RLC layer entities that have a correspondence relationship with eQI, which is also within the protection scope of the present application.
  • the PDCP layer entity 1 corresponding to DRB1 is associated with the RLC layer entity 1 and the RLC layer entity 2.
  • Each RLC layer entity corresponds to an eQI set, and the eQI set may include one or more eQIs.
  • the eQI set corresponding to RLC layer entity 1 includes eQI1 and eQI2, and the eQI set corresponding to RLC layer entity 2 includes eQI3 and eQI4.
  • Table 4 Example of correspondence between RLC layer entities and eQI sets associated with PDCP layer entity 1
  • DRB ID RLC layer entity eQI collection DRB 1 RLC layer entity 1 eQI 1, eQI 2 DRB 1 RLC layer entity 2 eQI 3, eQI 4
  • the data packets corresponding to different eQIs in the same DRB can be mapped to the same or different RLC layer entities.
  • the data packet corresponding to eQI 1 or eQI 2 in DRB 1 needs to be mapped to RLC layer entity 1 for processing and transmission
  • the data packet corresponding to eQI 3 or eQI 4 needs to be mapped to RLC layer entity 2 Processing and transmission.
  • the first terminal device can obtain the corresponding relationship between the RLC layer entity and eQI associated with the PDCP layer entity, and then the PDCP layer entity of the first terminal device can map the first data packet according to the corresponding relationship and the eQI corresponding to the first data packet To the RLC layer entity corresponding to the eQI.
  • eQI 2 corresponds to RLC layer entity 1.
  • the PDCP layer entity 1 corresponding to DRB 1 can transfer the first data The packet is mapped to the RLC layer entity 1.
  • the first terminal device may send a request message 2 to the network device, and the request message 2 may include eQI 5 (or Information used to indicate eQI 5, such as the index of eQI 5). Accordingly, after receiving the request message 2, the network device may return a response message 2 to the first terminal device.
  • the response message 2 includes the data associated with the PDCP layer entity 1.
  • the identifier of the RLC layer entity corresponding to eQI 5 among the RLC layer entities (or the information used to indicate the RLC layer entity corresponding to eQI 5), and then the first terminal device may map the first data packet to the RLC layer entity corresponding to eQI 5 in. Further, the first terminal device may 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 first level caused by configuring a large number of RLC layer entities for the first terminal device at the beginning. The maintenance complexity of the terminal equipment.
  • the first terminal device may map the first data packet to a default RLC layer entity, where the default RLC layer entity may be a DRB 1 corresponds to the default RLC layer entity.
  • the default RLC layer entity corresponding to DRB 1 can be configured by the network device.
  • the network device is DRB 1 configures the RLC layer entity 1 as the default RLC layer entity.
  • the network device indicates the RLC layer entity 1 as the default RLC layer entity in the configuration information element of the RLC layer entity 1; or, the default RLC layer entity corresponding to DRB1 may be determined by the first terminal device based on preset rule 3, such as preset Rule 3 can be that the RLC layer entity with the smallest/largest corresponding LCH ID among the RLC layer entities associated with the PDCP layer corresponding to DRB1 is the default RLC layer entity.
  • preset Rule 3 may be predefined by the protocol, or determined by the network device and instructed to the terminal device.
  • Implementation Mode 3 when the PDCP layer entity of the DRB is associated with multiple RLC layer entities, these RLC layer entities can be independently configured, for example, multiple RLC layer entities can be configured in different transmission modes.
  • the PDCP layer entity corresponding to DRB 1 is associated with two RLC layer entities (respectively RLC layer entity 1, RLC layer entity 2), where RLC layer entity 1 can be configured as UM, and RLC layer entity 2 can be configured as AM .
  • RLC layer entity 1 can be configured as UM
  • RLC layer entity 2 can be configured as AM .
  • the network device may configure a set of parameters for the PDCP layer entity corresponding to the DRB, or may also configure multiple sets of parameters.
  • the parameters of the PDCP layer entity may include one or more possible parameters, and the following description will be made by taking an example in which the parameters of the PDCP layer entity include the discarding duration.
  • the network device When the network device configures multiple sets of parameters for the PDCP layer entity, it can further configure the correspondence between eQI and multiple sets of parameters. See Table 5, which is an example of the correspondence between eQI and multiple sets of parameters.
  • the PDCP layer entity can process the data packet submitted to the PDCP layer entity according to the discarding duration. If the network device configures multiple sets of parameters for the PDCP layer entity (such as discarding duration 1, discarding duration 2 and discarding duration 3), and the correspondence between the first QoS parameter and the multiple sets of parameters, the PDCP layer entity can be based on Table 5
  • the schematic correspondence relationship uses the parameters of the PDCP layer entity corresponding to the first QoS parameter corresponding to the data packet to process the data packet.
  • the discarding duration 1 can be used for the data Packet 1 is processed.
  • the discarding duration 2 can be used to process data packet 2.
  • 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
  • the repeated transmission function when the repeated transmission function is configured, it can be in a DRB, Configure the repeated transmission function for the eQI, that is, the data packet corresponding to the eQI can be copied and submitted to multiple RLC layer entities.
  • the PDCP layer entity corresponding to the DRB may be associated with multiple RLC layer entities
  • the eQI configured for repeated 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 repeated transmission.
  • eQI3 corresponds to RLC layer entity 1, RLC layer entity 2 and RLC layer entity 3, and the repeat transmission function can be configured for eQI3.
  • the network device can activate or deactivate the repeated transmission function configured for eQI3 through control signaling. For example, if the network device activates the repeated transmission function configured for eQI3 through control signaling, the first data packet corresponds to If the eQI is eQI3, 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 repeated transmission; if the network device is deactivated through control signaling For the repeated transmission function configured for eQI3, the PDCP layer entity of the first terminal device can map the first data packet to RLC layer entity 1 for transmission or map to RLC layer entity 2 for transmission or map to RLC layer entity 3 To transfer.
  • the network device may indicate through control signaling which RLC layer entities corresponding to eQI3 are used to perform layer repetitive transmission. For example, if the network device instructs 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 repeated transmission
  • the control signaling may include DRB 1 (or information used to indicate DRB 1), eQI3 (or information used to indicate eQI3), and the identities of RLC layer entity 1 and RLC layer entity 2 (or used to Information 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 used to indicate LCH 1 and LCH 2).
  • control signaling may be RRC signaling or MAC CE, which is not specifically limited.
  • the SDAP header, PDCP header, or RLC header of the first data packet may include the eQI corresponding to the first data packet (or information used to indicate the eQI corresponding to the first data packet).
  • the MAC layer of the terminal device when it performs BSR reporting, it needs to calculate the amount of data to be transmitted for different LCHs.
  • a possible way to calculate the amount of data to be transmitted for different LCHs is to target one of the LCHs. (Such as LCH 1), the amount of data to be transmitted 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 LCH The amount of data to be transmitted of the corresponding RLC layer entity 2 and PDCP layer entity 1 is determined as the BS amount of LCH 2.
  • BS buffer status
  • the amount of data to be transmitted in PDCP layer entity 1 is calculated when calculating the BS amount of LCH 1 and LCH 2.
  • the data to be transmitted in PDCP layer entity 1 includes data packet 1 and data packet. 2.
  • the eQI corresponding to data packet 1 is eQI 1
  • the eQI corresponding to data packet 2 is eQI 4.
  • data packet 1 is mapped to RLC layer entity 1 (or LCH 1) for transmission
  • Data packet 2 is mapped to RLC layer entity 2 (or LCH 2) for transmission, but when calculating the BS amount of LCH 1, data packet 1 and data packet 2 are calculated, and the data is also calculated when calculating the BS amount of LCH 2 Packet 1 and data packet 2 are calculated, which will cause the total BS amount reported to the network device to exceed the actual amount of data to be transmitted by the terminal device, resulting in a waste of subsequent scheduling resources.
  • the amount of data on the PDCP layer entity can be allocated to different LCHs in proportion, and the specific proportion can be configured by the network, or instructed by the application layer, or determined by the implementation of the terminal device.
  • the amount of data on PDCP layer entity 1 is 100. Since PDCP layer entity 1 is associated with RLC layer entity 1, RLC layer entity 2 and RLC layer entity 3, when calculating LCH 1, LCH 2, and LCH 3, you can The amount of data on PDCP layer entity 1 is allocated to LCH 1, LCH 2 and LCH 3 in proportion.
  • the amount of data to be transmitted in RLC layer entity 1 corresponding to LCH 1 can be 40% of the amount of data to be transmitted in PDCP layer entity 1.
  • % Is determined as the BS volume of LCH 1, and 30% of the data volume to be transmitted of RLC layer entity 2 corresponding to LCH 2 and 30% of the data volume to be transmitted of PDCP layer entity 1 is determined as the BS volume of LCH2, and the RLC layer corresponding to LCH 3 30% of the to-be-transmitted data volume of entity 3 and the PDCP-layer entity 1’s to-be-transmitted data volume are determined as the BS volume of LCH3.
  • the application layer of the first terminal device after the application layer of the first terminal device obtains the first data packet and the eQI corresponding to the first data packet, it can use the eQI or be used to indicate The eQI information is encapsulated into the first data packet, for example, the eQI or the information used to indicate the eQI is encapsulated into a header generated by the application layer for the first data packet, and then submitted to the non-access layer; further After receiving the first data packet, the non-access layer (or access layer) can strip off the header generated by the application layer, obtain the eQI corresponding to the first data packet, and then perform subsequent processing; it should be understood that the header is stripped off The head may not transmit on the air interface. Alternatively, the first terminal device may not encapsulate the eQI into the first data packet, but submit it to the non-access layer or the access layer together with the first data packet.
  • FIG. 5a is a schematic flow diagram corresponding to the data transmission method provided in the second embodiment of the application
  • FIG. 5b is a schematic diagram of the data transmission process provided in the second embodiment of the application.
  • Step 501 The terminal device 1 obtains the second data packet and the eQI and QFI corresponding to the second data packet.
  • Step 502 The terminal device 1 maps the second data packet to the DRB or RLC layer entity according to the eQI and QFI, and sends it to the network device 1.
  • the terminal device 1 may use the implementation manner 1 or the implementation manner 3 described in the first embodiment to send the second data packet to the network device 1.
  • Step 503 The network device 1 obtains 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.
  • the GTP U data packet 1 may include a second data packet and indication information 1, and the indication information 1 is used to indicate the eQI corresponding to the second data packet.
  • the indication information 1 may 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 specifically limited.
  • the indication information 1 may also be used to indicate the QFI corresponding to the second data packet.
  • the indication information 1 may be carried in a GTP-U header (GTP-U header).
  • the network device 1 may obtain the eQI corresponding to the second data packet.
  • One possible way is that the terminal device 1 transmits the eQI corresponding to the second data packet to the network device 1.
  • the eQI corresponding to the second data packet (or the 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 method At 3 o'clock, the eQI corresponding to the second data packet (or the information used to indicate the eQI corresponding to the first data packet) may be carried in the SDAP header or the PDCP header or the RLC header.
  • the eQI corresponding to the second data packet (or the information used to indicate the eQI corresponding to the first data packet) is not encapsulated in the second data packet, Instead, it is transmitted to the network device 1 together with the second data packet.
  • the terminal device 1 does not transmit the eQI corresponding to the second data packet to the network device 1.
  • the network device 1 can determine the eQI corresponding to the second data packet according to the DRB or RLC layer entity that carries the second data packet.
  • the network device can carry the DRB of the second data packet to determine the eQI corresponding to the second data packet; when the terminal device adopts implementation mode 3, if the RLC If the layer entity corresponds to one eQI, the RLC layer entity that can carry the second data packet by the network device determines the eQI corresponding to the second data packet.
  • step 504 the UPF entity 1 obtains the second data packet and the eQI and QFI corresponding to the second data packet, and transmits the second data packet and the eQI and QFI corresponding to the second data packet to the UPF entity 2 through the IMS network or server.
  • the UPF entity 1 may send an IP data packet 1 to an IP multimedia subsystem (IMS) network or a video server (video server), and the IP data packet 1 includes the second data packet and the instruction information 1, and the instruction information 1 can be carried in a certain layer of protocol header of IP data packet 1.
  • IMS IP multimedia subsystem
  • video server video server
  • the IMS network or the video server sends an IP data packet 2 to the UPF entity 2.
  • the IP data packet 2 includes the second data packet and the indication information 1, and the indication information 1 may be carried in a certain layer protocol header of the IP data packet 2.
  • step 505 the UPF entity 2 obtains the second data packet, the eQI and QFI corresponding to the second data packet, and sends the GTP U data packet 2 to the network device 2.
  • the GTP U data packet 2 may include the second data packet and the indication information 1.
  • Step 506 The network device 2 obtains the second data packet and the eQI and QFI corresponding to the second data packet, and sends the second data packet to the terminal device 2 according to the eQI and QFI corresponding to the second data packet.
  • the network device 2 may adopt the implementation manner 1 or the implementation manner 3 described in the first embodiment to transmit the second data packet to the terminal device 2. It should be understood that since the network device 2 does not have an application layer and a non-access layer, when the implementation method 1 or the implementation method 3 is adopted, the network device 2 obtains the second data packet and the second data packet from the GTP-U data packet After the corresponding eQI and QFI, the second data packet and the eQI and QFI corresponding to the second data packet can be submitted to the SDAP layer entity to perform corresponding operations.
  • the SDAP layer entity can map the second data packet to the DRB corresponding to eQI and QFI according to the eQI and QFI corresponding to the second data packet; when implementation mode 3 is adopted, the SDAP layer entity can map the second data packet to the DRB corresponding to eQI and QFI.
  • the QFI corresponding to the second data packet maps the second data packet to the DRB corresponding to the QFI
  • the PDCP layer entity corresponding to the DRB can map the second data packet to the RLC layer entity corresponding to the eQI according to the eQI corresponding to the second data packet .
  • the QoS of the data packet is further refined on the basis of the existing QFI, and the data packet is differentiated end-to-end through QFI and eQI.
  • FIG. 6a is a schematic diagram of the process corresponding to the data transmission method provided in the third embodiment of this application
  • FIG. 6b is a schematic diagram of the data transmission process provided in the third embodiment of this application.
  • Step 601 The terminal device 1 obtains 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.
  • 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 sends it to the network device 1.
  • the terminal device 1 may use the implementation manner 2 described in the first embodiment to send the second data packet to the network device 1.
  • 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.
  • the GTP U data packet 1 may include a second data packet and indication information 2, and the indication information 2 is used to indicate the QFI' corresponding to the second data packet.
  • the indication information 2 may include the QFI' corresponding to the second data packet, or the index of the QFI' corresponding to the second data packet, or other information used to indicate the QFI' corresponding to the second data packet. limited.
  • the indication information 2 may be carried in the GTP U header.
  • the network device 1 may be implemented by referring to the manner in which the network device obtains the QFI' corresponding to the data packet in the prior art, which will not be repeated here.
  • 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.
  • 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.
  • the GTP U data packet 2 may include the second data packet and the indication information 2.
  • 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.
  • the network device 2 may use the implementation manner 2 described in the first embodiment to transmit the second data packet to the terminal device 2. It should be understood that since the network device does not have the application layer and the non-access layer, when the implementation mode 2 is adopted, 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 second data packet and the QFI' corresponding to the second data packet can be submitted to the SDAP layer entity to perform corresponding operations. For example, the SDAP layer entity may map the second data packet to the DRB corresponding to QFI' according to the QFI' corresponding to the second data packet.
  • the QoS of the data packet is refined, and the data packet is differentiated end-to-end through QFI'.
  • the network device or the terminal device may include a hardware structure and/or software module corresponding to each function.
  • 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 executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application may divide the terminal device and the network device into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • FIG. 7 shows a possible exemplary block diagram of a device involved in an embodiment of the present application.
  • the apparatus 700 may include: a processing unit 702 and a communication unit 703.
  • the processing unit 702 is used to control and manage the actions of the device 700.
  • the communication unit 703 is used to support communication between the apparatus 700 and other devices.
  • the communication unit 703 is also called a transceiving unit, and may include a receiving unit and/or a sending unit, which are used to perform receiving and sending operations respectively.
  • the device 700 may further include a storage unit 701 for storing program codes and/or data of the device 700.
  • the apparatus 700 may be the terminal device (or a chip set in the terminal device) in any of the foregoing embodiments, such as the first terminal device in the first embodiment and the terminal device 1 in the second embodiment. Or the terminal device 1 in the third embodiment; wherein, the processing unit 702 can support the apparatus 700 to perform the actions of the terminal device in the above method examples; or the processing unit 702 mainly executes the internal actions of the terminal device in the method examples, and the communication unit 703 can support communication between the apparatus 700 and other devices (such as network devices).
  • the processing unit 702 can support the apparatus 700 to perform the actions of the terminal device in the above method examples; or the processing unit 702 mainly executes the internal actions of the terminal device in the method examples, and the communication unit 703 can support communication between the apparatus 700 and other devices (such as network devices).
  • the apparatus 700 may be the network device (or a chip set in the network device) in any of the foregoing embodiments, such as the network device 2 in the second embodiment or the network device 2 in the third embodiment; wherein, the processing unit 702 may support the apparatus 700 to perform the actions of the network equipment in the above method examples; or, the processing unit 702 may mainly perform the internal actions of the network equipment in the method examples, and the communication unit 703 may support the interaction between the apparatus 700 and other equipment (such as terminal equipment). Inter-communication.
  • 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; the processing unit 702 is configured to: according to the first QoS parameter and the second QoS parameter , Map the data packet to the DRB or RLC layer entity, and send it to the second communication device through the communication unit 703.
  • the first QoS parameter or information used to indicate the first QoS parameter is carried in a data packet.
  • the apparatus 700 is a terminal device, and the first QoS parameter is allocated by the application layer of the apparatus 700 for the data packet.
  • the apparatus 700 is a network device; the communication unit 703 is specifically configured to: receive a GTP-U data packet from a core network device, the GTP-U data packet includes the data packet and instruction information, and the instruction information is used for Indicates the first QoS parameter.
  • the communication unit 703 is further configured to: obtain the corresponding relationship between the first QoS parameter, the second QoS parameter, and the DRB; the processing unit 702 is specifically configured to: compare the data according to the corresponding relationship The packet is mapped to the DRB corresponding to the first QoS parameter and the second QoS parameter.
  • the apparatus 700 is a terminal device, and the communication unit 703 is specifically configured to obtain the corresponding relationship from a network device, and the corresponding relationship is carried in RRC signaling.
  • the apparatus 700 is a terminal device, and the processing unit 702 is further configured to: if it is determined that there is no corresponding relationship, map the data packet to the default DRB.
  • the default DRB is configured by the network device, or is the DRB with the smallest or largest DRB ID among the DRBs associated with the second QoS parameter.
  • the apparatus 700 is a terminal device, and the processing unit 702 is further configured to: if it is determined that there is no corresponding relationship, send a first request message to the network device through the communication unit 703, where the first request message includes The first QoS parameter and the second QoS parameter.
  • 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 first QoS parameter and the DRB corresponding to the second QoS parameter
  • 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 shown.
  • the first QoS parameter or the information used to indicate the first QoS parameter is carried in the SDAP header or the PDCP header of the data packet.
  • 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, according to the correspondence between the second QoS parameter and the DRB, Map the data packet to the DRB corresponding to the second QoS parameter.
  • the communication unit 703 is further configured to obtain the correspondence between the first QoS parameter and the second QoS parameter from a core network device.
  • the processing unit 702 is specifically configured to map the data packet to the DRB corresponding to the second QoS parameter according to the second QoS parameter, and the packet data convergence protocol PDCP layer entity corresponding to the DRB Associate at least one RLC layer entity; and obtain the corresponding relationship between the first QoS parameter and the RLC layer entity through the communication unit 703, and then map the data packet to the first one of the at least one RLC layer entity according to the corresponding relationship.
  • the RLC layer entity corresponding to the QoS parameter is specifically configured to map the data packet to the DRB corresponding to the second QoS parameter according to the second QoS parameter, and the packet data convergence protocol PDCP layer entity corresponding to the DRB Associate at least one RLC layer entity; and obtain the corresponding relationship between the first QoS parameter and the RLC layer entity through the communication unit 703, and then map the data packet to the first one of the at least one RLC layer entity according to the corresponding relationship.
  • the RLC layer entity corresponding to the QoS parameter is specifically configured to map
  • the apparatus 700 is a terminal device, and the communication unit 703 is further configured to obtain the corresponding relationship from a network device, and the corresponding relationship is carried in RRC signaling.
  • the apparatus 700 is a terminal device, and the processing unit 702 is further configured to: if it is determined that there is no corresponding relationship, map the data packet to a default RLC layer entity.
  • the default RLC layer entity is configured by the network device, or is the RLC layer entity with the smallest or largest corresponding logical channel LCH ID in the at least one RLC layer entity.
  • the apparatus 700 is a terminal device, and the processing unit 702 is further configured to: if it is determined that there is no corresponding relationship, send a second request message to the network device through the communication unit 703, where the second request message includes The first QoS parameter.
  • the communication unit 703 is further configured to: receive 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 processing unit 702 is further configured to Used for: mapping the data packet to the RLC layer entity corresponding to the first QoS parameter according to the second response message.
  • the PDCP layer entity is configured with multiple sets of parameters, and the first QoS parameter corresponds to one set of the multiple sets of parameters; the processing unit 702 is further configured to: The parameters corresponding to the QoS parameters are used to process the data packets.
  • 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 The entity is configured to implement the replication transmission function; the communication unit 703 is further configured to: receive indication information from the second communication device, where the indication information is used to indicate the at least two RLC layers corresponding to the first QoS parameter The RLC layer entity used to perform the copy transmission function in the entity; the processing unit 702 is further used to map the data packet to the RLC layer entity used to perform the copy transmission function.
  • the first QoS parameter or the information used to indicate the first QoS parameter is carried in the SDAP header, PDCP header, or RLC header of the data packet.
  • the apparatus 700 may be the network device (or a chip set in the network device) in any of the foregoing embodiments, such as the network device 1 in the second embodiment or the network device 1 in the third embodiment. ;
  • the processing unit 702 can support the apparatus 700 to perform the actions of the network equipment in the above method examples; or, the processing unit 702 mainly executes the internal actions of the network equipment in the method examples, and the communication unit 703 can support the apparatus 700 and other equipment ( For example, the communication between core network equipment).
  • 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 the core network device.
  • the 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.
  • the communication unit 703 is specifically configured to: receive the data packet from the terminal device, the data packet being carried on the first DRB or the first RLC layer entity, and the processing unit 702 is configured to: The first DRB or the first RLC layer entity obtains the first QoS parameter; or, the communication unit 703 receives the data packet from the terminal device, and the data packet carries the first QoS Parameter or information used to indicate the first QoS parameter.
  • the data packet carries the first QoS parameter or the information used to indicate the first QoS parameter, including: the SDAP header, the PDCP header, or the RLC header of the data packet carries The first QoS parameter or information used to indicate the first QoS parameter.
  • the indication information is carried in the GTP-U header of the GTP-U data packet.
  • each unit in the device can be all implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; part of the units can also be implemented in the form of software called by the processing elements, and some of the units can be implemented in the form of hardware.
  • each unit can be a separate processing element, or it can be integrated in a certain chip of the device for implementation.
  • it can also be stored in the memory in the form of a program, which is called and executed by a certain processing element of the device.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in a processor element or implemented in a form of being called by software through a processing element.
  • the unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (ASICs), or, one or Multiple microprocessors (digital singnal processors, DSPs), or, one or more field programmable gate arrays (Field Programmable Gate Arrays, FPGAs), or a combination of at least two of these integrated circuits.
  • ASICs application specific integrated circuits
  • DSPs digital singnal processors
  • FPGAs Field Programmable Gate Arrays
  • the unit in the device can be implemented in the form of a processing element scheduler
  • the processing element can be a processor, such as a general-purpose central processing unit (central processing unit, CPU), or other processors that can call programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the above receiving unit is an interface circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit used by the chip to receive signals from other chips or devices.
  • the above unit for sending is an interface circuit of the device for sending signals to other devices.
  • the sending unit is an interface circuit used by the chip to send signals to other chips or devices.
  • FIG. 8 is a schematic structural diagram of a terminal device according to an embodiment of the application. It may be the terminal device in the above embodiment, and is used to implement the operation of the terminal device in the above embodiment.
  • the terminal device includes: an antenna 810, a radio frequency part 820, and a signal processing part 830.
  • the antenna 810 is connected to the radio frequency part 820.
  • the radio frequency part 820 receives the information sent by the network device through the antenna 810, and sends the information sent by the network device to the signal processing part 830 for processing.
  • the signal processing part 830 processes the information of the terminal equipment and sends it to the radio frequency part 820
  • the radio frequency part 820 processes the information of the terminal equipment and sends it to the network equipment through the antenna 810.
  • the signal processing part 830 may include a modem subsystem, which is used to process data at various communication protocol layers; it may also include a central processing subsystem, which is used to process terminal equipment operating systems and application layers; in addition, it may also Including other subsystems, such as multimedia subsystems, peripheral subsystems, etc., where the multimedia subsystem is used to control the terminal device camera, screen display, etc., and the peripheral subsystem is used to realize the connection with other devices.
  • the modem subsystem can be a separate chip.
  • the modem subsystem may include one or more processing elements 831, for example, including a main control CPU and other integrated circuits.
  • the modem subsystem may also include a storage element 832 and an interface circuit 833.
  • the storage element 832 is used to store data and programs, but the program used to execute the method executed by the terminal device in the above method may not be stored in the storage element 832, but stored in a memory outside the modem subsystem.
  • the modem subsystem is loaded and used.
  • the interface circuit 833 is used to communicate with other subsystems.
  • the modem subsystem can be implemented by a chip, the chip includes at least one processing element and an interface circuit, wherein the processing element is used to execute each step of any method executed by the above terminal device, and the interface circuit is used to communicate with other devices.
  • the unit for the terminal device to implement each step in the above method can be implemented in the form of a processing element scheduler.
  • the device for the terminal device includes a processing element and a storage element, and the processing element calls the program stored by the storage element to Perform the method performed by the terminal device in the above method embodiment.
  • the storage element may be a storage element whose processing element is on the same chip, that is, an on-chip storage element.
  • the program used to execute the method executed by the terminal device in the above method may be a storage element on a different chip from the processing element, that is, an off-chip storage element.
  • the processing element calls or loads a program from the off-chip storage element on the on-chip storage element to call and execute the method executed by the terminal device in the above method embodiment.
  • the unit of the terminal device that implements each step in the above method may be configured as one or more processing elements, and these processing elements are arranged on the modem subsystem, where the processing elements may be integrated circuits, For example: one or more ASICs, or, one or more DSPs, or, one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.
  • the units of the terminal device that implement each step in the above method can be integrated together and implemented in the form of an SOC, and the SOC chip is used to implement the above method.
  • the chip can integrate at least one processing element and a storage element, and the processing element can call the stored program of the storage element to implement the method executed by the above terminal device; or, the chip can integrate at least one integrated circuit to implement the above terminal The method executed by the device; or, it can be combined with the above implementations.
  • the functions of some units are implemented in the form of calling programs by processing elements, and the functions of some units are implemented in the form of integrated circuits.
  • the above apparatus for terminal equipment may include at least one processing element and an interface circuit, wherein at least one processing element is used to execute any of the methods performed by the terminal equipment provided in the above method embodiments.
  • the processing element can execute part or all of the steps executed by the terminal device in the first way: calling the program stored in the storage element; or in the second way: combining instructions through the integrated logic circuit of the hardware in the processor element Part or all of the steps performed by the terminal device are executed in a manner; of course, part or all of the steps executed by the terminal device can also be executed in combination with the first manner and the second manner.
  • the processing element here is the same as that described above, and can be implemented by a processor, and the function of the processing element can be the same as the function of the processing unit described in FIG. 7.
  • the processing element may 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 DSP , Or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • the storage element may be realized by a memory, and the function of the storage element may be the same as the function of the storage unit described in FIG. 7.
  • the storage element can be a single memory or a collective term for multiple memories.
  • the terminal device shown in FIG. 8 can implement various processes involving the terminal device in the method embodiment illustrated in FIG. 3, FIG. 5a, or FIG. 6a.
  • the operations and/or functions of the various modules in the terminal device shown in FIG. 8 are used to implement the corresponding processes in the foregoing method embodiments.
  • FIG. 9 is a schematic structural diagram of a network device provided by an embodiment of the application. It is used to implement the operation of the network device in the above embodiment.
  • the network equipment 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.
  • 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.
  • the baseband device 903 processes the information of the terminal device and sends it to the radio frequency device 902, and the radio frequency device 902 processes the information of the terminal device and sends it to the terminal device via the antenna 901.
  • the baseband device 903 may include one or more processing elements 9031, for example, a main control CPU and other integrated circuits.
  • the baseband device 903 may 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 exchange information with the radio frequency device 902.
  • the interface is, for example, a common public radio interface. , CPRI).
  • the above apparatus for network equipment may be located in the baseband apparatus 903.
  • the above apparatus for network equipment may be a chip on the baseband apparatus 903.
  • the chip includes at least one processing element and an interface circuit, wherein the processing element is used to execute the above network. For each step of any method executed by the device, the interface circuit is used to communicate with other devices.
  • the unit for the network device to implement each step in the above method can be implemented in the form of a processing element scheduler.
  • the device for the network device includes a processing element and a storage element, and the processing element calls the program stored by the storage element to Perform the method performed by the network device in the above method embodiment.
  • the storage element may be a storage element with the processing element on the same chip, that is, an on-chip storage element, or a storage element on a different chip from the processing element, that is, an off-chip storage element.
  • the unit of the network device that implements each step in the above method may be configured as one or more processing elements, and these processing elements are arranged on the baseband device.
  • the processing elements here may be integrated circuits, such as one Or multiple ASICs, or, one or more DSPs, or, one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.
  • the units for the network equipment to implement each step in the above method can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the baseband device includes the SOC chip for implementing the above method.
  • At least one processing element and storage element can be integrated in the chip, and the processing element can call the stored program of the storage element to implement the method executed by the above network device; or, at least one integrated circuit can be integrated in the chip to implement the above network The method executed by the device; or, it can be combined with the above implementations.
  • the functions of some units are implemented in the form of calling programs by processing elements, and the functions of some units are implemented in the form of integrated circuits.
  • the above apparatus for a network device may include at least one processing element and an interface circuit, wherein at least one processing element is used to execute any of the methods performed by the network device provided in the above method embodiments.
  • the processing element can execute part or all of the steps executed by the network device in the first way: calling the program stored in the storage element; or in the second way: combining instructions through the integrated logic circuit of the hardware in the processor element Part or all of the steps performed by the network device are executed in the method; of course, part or all of the steps executed by the network device above can also be executed in combination with the first method and the second method.
  • the processing element here is the same as that described above, and can be implemented by a processor, and the function of the processing element can be the same as the function of the processing unit described in FIG. 7.
  • the processing element may 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 DSP , Or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • the storage element may be realized by a memory, and the function of the storage element may be the same as the function of the storage unit described in FIG. 7.
  • the storage element can be a single memory or a collective term for multiple memories.
  • the network device shown in FIG. 9 can implement various processes involving the network device in the method embodiment shown in FIG. 5a or FIG. 6a.
  • the operations and/or functions of the various modules in the network device shown in FIG. 9 are used to implement the corresponding processes in the foregoing method embodiments.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开一种数据传输方法及装置，其中方法包括：第一通信装置获取数据包和数据包对应的第一QoS参数和第二QoS参数，根据所述第一QoS参数和所述第二QoS参数，将数据包映射到DRB或RLC层实体，并发送给第二通信装置。采用上述方案，由于第一通信装置是基于两种QoS参数将第一数据包映射到DRB或RLC层实体，相比于现有方案中根据第一数据包的五元组来确定第一数据包对应的QFI，进而根据QFI将第一数据包映射到DRB来说，更加全面地考虑了第一数据包的服务质量要求，从而能够更有效地对数据进行区分处理，以满足用户的不同需求。

Description

一种数据传输方法及装置 技术领域
本申请涉及无线通信技术领域，特别涉及一种数据传输方法及装置。
背景技术
移动通信网络中，运营商能够为用户提供语音、数据、视频等更多丰富多彩的业务。由于不同的业务对时延、带宽等要求各不相同，通过引入服务质量(quality of service，QoS)方案，实现各种业务的差异化，为高速数据业务提供了保障，增强了用户的网络体验。QoS方案的目的是针对各种不同的业务需求，提供不同服务质量的网络服务。尤其是在网络拥塞时，优先保障优先级高的用户或业务的服务质量。
上行业务流发生时，终端设备通过对上行业务流的上行数据包进行分析，获取数据包的五元组，根据五元组与服务质量流标识(QoS flow indicator，QFI)的映射关系确定该五元组对应的QFI，并在数据包的封装头中携带该五元组对应的QFI，从而实现将上行业务流映射至QoS流。下行业务流发生时，用户面网元可以采用与终端设备侧相同的方式，将下行业务流映射至QoS流。
在一个协议数据单元(protocol data unit，PDU)会话内，具有相同QFI的用户面数据将受到相同的对待等级，如调度，转发控制等。然而，在一些新的业务场景中，比如社交直播视频流(social live video streaming，SLVS)场景中，同一视频可能同时存在实时观看的观众(要求时延敏感)和延时观看的观众，但由于这些视频数据对应的QFI相同，从而会映射到同一QoS流，导致无法对视频数据进行区分处理，影响不同需求的用户的体验。
发明内容
有鉴于此，本申请提供了一种数据传输方法及装置，用以实现对数据进行区分处理，以满足用户的不同需求。
第一方面，本申请实施例提供一种数据传输方法，该方法可以应用于第一通信装置，第一通信装置可以终端设备(或者设置在终端设备内部的芯片)或者网络设备(或者设置在网络设备内部的芯片)。在该方法中，第一通信装置获取数据包和数据包对应的第一QoS参数和第二QoS参数，根据所述第一QoS参数和所述第二QoS参数，将数据包映射到DRB或RLC层实体，并发送给第二通信装置。
采用上述方案，由于第一通信装置是基于两种QoS参数将第一数据包映射到DRB或RLC层实体，相比于现有方案中根据第一数据包的五元组来确定第一数据包对应的QFI，进而根据QFI将第一数据包映射到DRB来说，更加全面地考虑了第一数据包的服务质量要求，从而能够更有效地对数据进行区分处理，以满足用户的不同需求。
在一种可能的设计中，第一QoS参数或者用于指示第一QoS参数的信息携带在数据包中。
在一种可能的设计中，第一通信装置为终端设备，第一QoS参数是由第一通信装置的应用层为数据包分配的。
在一种可能的设计中，第一通信装置为网络设备；第一通信装置获取数据包和数据包 对应的第一QoS参数，包括：第一通信装置接收来自核心网设备的GTP-U数据包，GTP-U数据包中包括数据包和指示信息，指示信息用于指示第一QoS参数。
在一种可能的设计中，第一通信装置根据所述第一QoS参数和所述第二QoS参数，将数据包映射到DRB，包括：第一通信装置获取所述第一QoS参数、所述第二QoS参数和DRB的对应关系；第一通信装置根据所述对应关系，将数据包映射到所述第一QoS参数、所述第二QoS参数对应的DRB。
在一种可能的设计中，第一通信装置为终端设备，第一通信装置获取所述对应关系，包括：第一通信装置从网络设备获取所述对应关系，所述对应关系携带在RRC信令中。
在一种可能的设计中，第一通信装置为终端设备，所述方法还包括：第一通信装置若确定没有所述对应关系，则将数据包映射到默认DRB。
在一种可能的设计中，所述默认DRB为网络设备配置的，或者为第二QoS参数关联的DRB中DRB ID最小或最大的DRB。
在一种可能的设计中，第一通信装置为终端设备，所述方法还包括：第一通信装置若确定没有所述对应关系，则向网络设备发送第一请求消息，所述第一请求消息包括所述第一QoS参数和所述第二QoS参数。
在一种可能的设计中，所述方法还包括：第一通信装置接收来自网络设备的第一响应消息，所述第一响应消息用于指示所述第一QoS参数、所述第二QoS参数对应的DRB；第一通信装置根据所述第一QoS参数和所述第二QoS参数，将数据包映射到DRB，包括：第一通信装置根据所示第一响应消息，将数据包映射到所述第一QoS参数、所述第二QoS参数对应的DRB。
采用上述方案，网络设备可以根据终端设备的请求消息为终端设备配置DRB，避免一开始为终端设备配置大量的DRB所带来的信令开销和终端设备的维护复杂度。
在一种可能的设计中，所述第一QoS参数或者用于指示所述第一QoS参数的信息携带在数据包的SDAP头或PDCP头中。
在一种可能的设计中，第一通信装置根据所述第一QoS参数和所述第二QoS参数，将数据包映射到DRB，包括：第一通信装置根据所述第一QoS参数，确定数据包对应的所述第二QoS参数；第一通信装置根据所述第二QoS参数和DRB的对应关系，将数据包映射到所述第二QoS参数对应的DRB。
在一种可能的设计中，所述方法还包括：第一通信装置从核心网设备获取所述第一QoS参数和所述第二QoS参数的对应关系。
在一种可能的设计中，第一通信装置根据所述第一QoS参数和所述第二QoS参数，将数据包映射到RLC层实体，包括：第一通信装置根据所述第二QoS参数，将数据包映射到所述第二QoS参数对应的DRB，所述DRB对应的分组数据汇聚协议PDCP层实体关联至少一个RLC层实体；第一通信装置获取所述第一QoS参数和RLC层实体的对应关系，并根据所述对应关系，将数据包映射到所述至少一个RLC层实体中的第一QoS参数对应的RLC层实体。
在一种可能的设计中，第一通信装置为终端设备，第一通信装置获取所述第一QoS参数和RLC层实体的对应关系，包括：第一通信装置从网络设备获取所述对应关系，所述对应关系携带在RRC信令中。
在一种可能的设计中，第一通信装置为终端设备，所述方法还包括：第一通信装置若 确定没有所述对应关系，则将数据包映射到默认RLC层实体。
在一种可能的设计中，所述默认RLC层实体为网络设备配置的，或者为所述至少一个RLC层实体中对应的逻辑信道LCH ID最小或最大的RLC层实体。
在一种可能的设计中，第一通信装置为终端设备，所述方法还包括：第一通信装置若确定没有所述对应关系，则向网络设备发送第二请求消息，所述第二请求消息包括所述第一QoS参数。
在一种可能的设计中，所述方法还包括：第一通信装置接收来自网络设备的第二响应消息，所述第二响应消息用于指示所述第一QoS参数对应的RLC层实体；第一通信装置根据所示第二响应消息，将数据包映射到所述第一QoS参数对应的RLC层实体。
采用上述方案，网络设备可以根据终端设备的请求消息为终端设备配置RLC层实体，避免一开始为终端设备配置大量的RLC层实体所带来的信令开销和终端设备的维护复杂度。
在一种可能的设计中，所述PDCP层实体被配置有多组参数，所述第一QoS参数对应所述多组参数中的一组参数；所述方法还包括：第一通信装置根据所述第一QoS参数对应的参数，对数据包进行处理。
采用上述方案，通过为PDCP层实体配置多组参数，从而可以根据数据包对应的第一QoS参数，采用相应的参数对数据包进行处理，实现了对数据包的区分处理。
在一种可能的设计中，所述PDCP层实体关联多个RLC层实体，所述第一QoS参数对应所述多个RLC层实体中的至少两个RLC层实体；所述至少两个RLC层实体被配置为实现复制传输功能；第一通信装置的PDCP层实体根据所述第一QoS参数，将数据包映射到对应的RLC层实体，包括：第一通信装置接收来自所述第二通信装置的指示信息，所述指示信息用于指示所述第一QoS参数对应的所述至少两个RLC层实体中用于执行复制传输功能的RLC层实体；第一通信装置将数据包映射到所述用于执行复制传输功能的RLC层实体。
采用上述方案，可以由网络设备来指示用于执行复制传输功能的RLC层实体，提高了网络设备调控的灵活性。
在一种可能的设计中，所述第一QoS参数或者用于指示所述第一QoS参数的信息携带在数据包的SDAP头或PDCP头或RLC头。
第二方面，本申请实施例提供一种数据传输方法，该方法可以应用于网络设备(或者设置在网络设备内部的芯片)。在该方法中，网络设备获取数据包、所述数据包对应的第一QoS参数和第二QoS参数；向核心网设备发送GTP-U数据包，所述GTP-U数据包中包括所述数据包和指示信息，所述指示信息用于指示所述第一QoS参数和所述第二QoS参数。
采用上述方案，由于GTP-U数据包中包括第二数据包和指示信息，从而便于后续根据第一QoS参数和第二QoS参数来调度第二数据包，以实现数据包在端到端上更细粒度的区分处理。
在一种可能的设计中，获取所述数据包对应的第一QoS参数，包括：接收来自终端设备的所述数据包，所述数据包承载于第一DRB或者第一RLC层实体上，以及根据所述第一DRB或者所述第一RLC层实体，得到所述第一QoS参数；或者，接收来自所述终端设备的所述数据包，所述数据包中携带所述第一QoS参数或者用于指示所述第一QoS参数 的信息。
在一种可能的设计中，所述数据包中携带所述第一QoS参数或者用于指示所述第一QoS参数的信息，包括：所述数据包的SDAP头或PDCP头或RLC头中携带所述第一QoS参数或者用于指示所述第一QoS参数的信息。
在一种可能的设计中，所述指示信息携带在所述GTP-U数据包的GTP-U头中。
第三方面，本申请实施例提供一种通信系统，该通信系统包括网络设备和核心网设备；其中，网络设备用于获取数据包、所述数据包对应的第一QoS参数和第二QoS参数；以及，向核心网设备发送GTP-U数据包，所述GTP-U数据包中包括所述数据包和指示信息，所述指示信息用于指示所述第一QoS参数和所述第二QoS参数；核心网设备用于接收所述GTP-U数据包。
在一种可能的设计中，所述通信系统还包括终端设备，用于向所述网络设备发送所述数据包；其中，所述数据包承载于第一DRB或者第一RLC层实体上，所述第一DRB或者所述第一RLC层实体对应所述第一QoS参数；或者，所述数据包中携带所述第一QoS参数或者用于指示所述第一QoS参数的信息。
在一种可能的设计中，核心网设备还用于发送网络协议IP数据包，所述IP数据包包括所述数据包和所述指示信息。
第四方面，本申请提供一种通信装置，所述通信装置可以为终端设备(或者设置在终端设备内部的芯片)或者网络设备(或者设置在网络设备内部的芯片)。所述通信装置具备实现上述第一方面或第二方面的功能，比如，所述通信装置包括执行上述第一方面或第二方面涉及步骤所对应的模块或单元或手段(means)，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元、通信单元，其中，通信单元可以用于收发信号，以实现该通信装置和其它装置之间的通信；处理单元可以用于执行该通信装置的一些内部操作。处理单元、通信单元执行的功能可以和上述第一方面或第二方面涉及的步骤相对应。
在一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器执行程序指令，以完成上述第一方面或第二方面中任意可能的设计或实现方式中的方法。其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合。所述一个或多个存储器可以和处理器集成在一起，也可以与处理器分离设置，本申请并不限定。存储器可以保存实现上述第一方面或第二方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面或第二方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和存储器，存储器可以保存实现上述第一方面或第二方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面或第二方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括至少一个处理器和接口电路，其中，至少一个处理器用于通过所述接口电路与其它装置通信，并执行上述第一方面或第二方面任意可能的设计或实现方式中由终端设备执行的方法。
第五方面，本申请提供一种计算机可读存储介质，所述计算机存储介质中存储有计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行上述第一方面或第二方面的任一种可能的设计中的方法。
第六方面，本申请提供一种计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得计算机执行上述第一方面或第二方面的任一种可能的设计中的方法。
第七方面，本申请提供一种芯片，所述芯片包括处理器，所述处理器与存储器耦合，用于读取并执行所述存储器中存储的软件程序，以实现上述第一方面或第二方面的任一种可能的设计中的方法。
本申请的这些方面或其它方面在以下实施例的描述中会更加简明易懂。
附图说明
图1a为本申请实施例适用的一种网络架构示意图；
图1b为本申请实施例适用的又一种网络架构示意图；
图1c为本申请实施例适用的又一种网络架构示意图；
图1d为本申请实施例适用的又一种网络架构示意图；
图2a为本申请实施例提供的下行数据在各层间传输示意图；
图2b为本申请实施例提供的一种QoS模型示意图；
图2c为本申请实施例提供的一种可能的SLVS平台架构示意图；
图2d为本申请实施例提供的数据重复传输示意图；
图3为本申请实施例一提供的数据传输方法所对应的流程示意图；
图4a为本申请实施例一提供的实现方式1所对应的流程示意图；
图4b为本申请实施例一提供的实现方式2所对应的流程示意图；
图4c为本申请实施例一提供的实现方式3所对应的流程示意图；
图5a为本申请实施例二提供的数据传输方法所对应的流程示意图；
图5b为本申请实施例二提供的数据传输过程示意图；
图6a为本申请实施例三提供的数据传输方法所对应的流程示意图；
图6b为本申请实施例三提供的数据传输过程示意图；
图7为本申请实施例中所涉及的装置的可能的示例性框图；
图8为本申请实施例提供的一种终端设备的结构示意图；
图9为本申请实施例提供的一种网络设备的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。
首先，对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
(1)终端设备：可以是能够接收网络设备调度和指示信息的无线终端设备，无线终端设备可以是指向用户提供语音和/或数据连通性的设备，或具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。终端设备可以经无线接入网(如，radio access network，RAN)与一个或多个核心网或者互联网进行通信，终端设备可以是移动终端设备， 如移动电话(或称为“蜂窝”电话，手机(mobile phone))、计算机和数据卡，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(SIP)话机、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、平板电脑(Pad)、带无线收发功能的电脑等设备。无线终端设备也可以称为系统、订户单元(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)等。终端设备也可以是可穿戴设备以及下一代通信系统，例如，5G通信系统中的终端设备或者未来演进的公共陆地移动网络(public land mobile network，PLMN)中的终端设备等。
(2)网络设备：是无线网络中的设备，例如网络设备可以为将终端接入到无线网络的无线接入网(radio access network，RAN)节点(或设备)，又可以称为基站。目前，一些RAN设备的举例为：5G通信系统中的新一代基站(generation Node B，gNodeB)、传输接收点(transmission reception point，TRP)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)、无线保真(wireless fidelity，Wi-Fi)接入点(access point，AP)、路边单元(road side unit，RSU)、融合接入回传(integrated access and backhaul，IAB)系统中的接入点、TSN网络中的控制节点和终端节点等。另外，在一种网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备。此外，在其它可能的情况下，网络设备可以是其它为终端设备提供无线通信功能的装置。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。为方便描述，本申请实施例中，为终端设备提供无线通信功能的装置称为网络设备。
(3)本申请实施例中的术语“系统”和“网络”可被互换使用。“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A、同时存在A和B、单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如“A，B和C中的至少一个”包括A，B，C，AB，AC，BC或ABC。
以及，除非有特别说明，本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度。例如，第一终端设备和第二终端设备，只是为了区分不同的终端设备，而并不是表示这两种终端设备的优先级或者重要程度等的不同。
图1a为本申请实施例适用的一种网络架构示意图。如图1a所示，终端设备130可接 入到无线网络，以通过无线网络获取外网(例如因特网)的服务，或者通过无线网络与其它设备通信，如可以与其它终端设备通信。该无线网络包括无线接入网(radio access network，RAN)设备110和核心网(core network，CN)设备120，其中RAN设备110用于将终端设备130接入到无线网络，CN设备120用于对终端设备进行管理并提供与外网通信的网关。应理解，图1a所示的通信系统中各个设备的数量仅作为示意，本申请实施例并不限于此，实际应用中在通信系统中还可以包括更多的终端设备130、更多的RAN设备110，还可以包括其它设备。
CN中可以包括多个CN设备120，当图1a所示的网络架构适用于5G通信系统时，CN设备120可以为接入和移动性管理功能(access and mobility management function，AMF)实体、会话管理功能(session management function，SMF)实体或用户面功能(user plane function，UPF)实体等，本申请实施例中以CN设备120为UPF实体为例。示例性地，终端设备130和RAN设备110之间的接口可以称为Uu接口或空口，RAN设备110和UPF实体之间的接口可以称为N3接口。
图1b为本申请实施例适用的又一种网络架构示意图。如图1b所示，该网络架构包括CN设备、RAN设备和终端设备。其中，RAN设备包括基带装置和射频装置，其中基带装置可以由一个节点实现，也可以由多个节点实现，射频装置可以从基带装置拉远独立实现，也可以集成在基带装置中，或者部分拉远部分集成在基带装置中。例如，在LTE通信系统中，RAN设备(eNB)包括基带装置和射频装置，其中射频装置可以相对于基带装置拉远布置，例如射频拉远单元(remote radio unit，RRU)相对于BBU拉远布置。又例如，在一种演进结构中，RAN设备可以包括CU和DU，多个DU可以由一个CU集中控制，CU和DU之间的接口可以称为F1-U接口。
图1c为本申请实施例适用的又一种网络架构示意图。相对于图1b所示的网络架构，图1c中还可以将CU的控制面(CP)和用户面(UP)分离，分成不同实体来实现，分别为控制面(control plane，CP)CU实体(即CU-CP实体)和用户面(user plane，UP)CU实体(即CU-UP实体)。
在以上网络架构中，CU产生的信令可以通过DU发送给终端设备，或者终端设备产生的信令可以通过DU发送给CU。DU可以不对该信令进行解析而直接通过协议层封装而透传给终端设备或CU。以下实施例中如果涉及这种信令在DU和终端设备之间的传输，此时，DU对信令的发送或接收包括这种场景。例如，RRC或PDCP层的信令最终会处理为PHY层的信令发送给终端设备，或者，由接收到的PHY层的信令转变而来。在这种架构下，该RRC或PDCP层的信令，即也可以认为是由DU发送的，或者，由DU和射频装载发送的。
图1d为本申请实施例适用的又一种网络架构示意图，如图1d所示，该网络架构可以包括RAN设备110、CN设备120、终端设备1301和终端设备1302。图1d所示意的网络架构与图1a所示意的网络架构的区别之处在于，图1d中终端设备1301和终端设备1302之间可以通过侧行链路(sidelink)资源进行通信，比如，终端设备1301可以向终端设备1302发送数据包。
上述图1a、图1b、图1c或图1d所示意的网络架构可以适用于各种无线接入技术(radio access technology，RAT)的通信系统中，例如可以是5G(或者称为新无线(new radio，NR))通信系统，当然也可以是未来的通信系统。本申请实施例描述的网络架构 以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着通信网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请以下实施例中的装置，根据其实现的功能，可以位于终端设备或网络设备。当采用以上CU-DU的结构时，网络设备可以为CU节点、或DU节点、或包括CU节点和DU节点的RAN设备。
在上述图1a、图1b、图1c或图1d所示意的网络架构中，网络设备和UPF实体之间的通信可以遵循一定的协议，比如GTP-U协议，GTP-U协议为通用分组无线服务技术(general packet radio service，GPRS)隧道传输协议(GPRS tunnel protocol，GTP)的其中一种协议。
网络设备和终端设备之间的通信可以遵循一定的协议层结构，例如控制面协议层结构可以包括无线资源控制(radio resource control，RRC)层、分组数据汇聚层协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层(physical layer，PHY)等协议层的功能；用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层等协议层的功能；在一种可能的实现中，PDCP层之上还可以包括业务数据适配(service data adaptation protocol，SDAP)层。示例性地，网络设备可以由一个节点实现RRC、PDCP、RLC和MAC等协议层的功能，或者可以由多个节点实现这些协议层的功能。例如，若网络设备包括CU和DU，则CU和DU可以根据无线网络的协议层划分，例如PDCP层及以上协议层的功能设置在CU，PDCP以下的协议层，例如RLC层和MAC层等的功能设置在DU。这种协议层的划分仅仅是一种举例，还可以在其它协议层划分，例如在RLC层划分，将RLC层及以上协议层的功能设置在CU，RLC层以下协议层的功能设置在DU；或者，在某个协议层中划分，例如将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。此外，也可以按其它方式划分，例如按时延划分，将处理时间需要满足时延要求的功能设置在DU，不需要满足该时延要求的功能设置在CU。
以网络设备和终端设备之间的数据传输为例，数据传输需要经过用户面协议层，比如经过SDAP层、PDCP层、RLC层、MAC层、物理层，其中，SDAP层、PDCP层、RLC层、MAC层、物理层也可以统称为接入层。根据数据的传输方向分为发送或接收，上述每层又分为发送部分和接收部分。以下数据传输为例，参见图2a所示为下行数据在各层间传输示意图，图2a中向下的箭头表示数据发送，向上的箭头表示数据接收。PDCP层自上层取得数据后，会将数据传送到RLC层与MAC层，再由MAC层生成传输块，然后通过物理层进行无线传输。数据在各个层中进行相对应的封装，某一层从该层的上层收到的数据视为该层的服务数据单元(service data unit，SDU)，经过层封装后成为PDU，再传递给下一个层。例如PDCP层从上层接收到的数据称为PDCP SDU，PDCP层发送到下层的数据称为PDCP PDU；RLC层从上层接收到的数据称为RLC SDU，RLC层发送到下层的数据称为RLC PDU。在协议中，层间的联系大都以通道的方式进行对应。RLC层与MAC层间通过逻辑信道(logical channel，LCH)对应，MAC层与物理层则是通过传输通道(transport channel)对应，物理层以下为物理信道(physical channel)，用来对应到另一端的物理层。
示例性地，根据图2a还可以看出，终端设备还具有应用层和非接入层；其中，应用层可以用于向终端设备中所安装的应用程序提供服务，比如，终端设备接收到的下行数据可以由物理层依次传输到应用层，进而由应用层提供给应用程序；又比如，应用层可以获取应用程序产生的数据(比如用户使用应用程序录制的视频等)，并将数据依次传输到物理层，发送给其它通信装置。非接入层可以用于转发用户数据，比如将从应用层接收到的上行数据转发给SDAP层或者将从SDAP层接收到的下行数据转发给应用层；以及，在上行和下行方向的数据包中标识QFI(可以参见下文的描述)，比如根据五元组与QFI的映射关系确定上行和下行方向的数据包的QFI。
基于上述所描述的通信协议和协议层结构，下面针对上述图1a、图1b或图1c所示意的网络架构中所涉及的一些可能的数据传输过程进行描述。
以图1b所示意的网络架构为例，UPF实体可以向终端设备130发送下行数据包，比如，UPF实体获取数据包X，并通过GTP-U协议(GTP-U协议为通用分组无线服务技术(general packet radio service，GPRS)隧道传输协议(GPRS tunnel protocol，GTP)的其中一种协议)进行封装得到GTP-U协议数据单元(protocol data unit，PDU)，进而通过N3接口向CU发送GTP-U PDU，GTP-U PDU中包括数据包X。CU接收GTP-U PDU，获取数据包X，并将数据包X封装成PDCP PDU通过F1-U接口递交给DU。DU接收PDCP PDU，获取数据包X，并将数据包X封装到MAC PDU中，通过Uu接口发送给终端设备。
相应地，终端设备130可以向UPF实体发送上行数据包，比如终端设备获取数据包Y，将数据包Y封装到MAC PDU中，通过Uu接口发送给DU。DU接收数据包Y，并将数据包Y封装成PDCP PDU通过F1-U接口递交给CU。CU接收PDCP PDU，获取数据包Y，并将数据包Y封装成GTP-U PDU发送给UPF实体。
在图1d所示意的网络架构中，第一终端设备(比如终端设备1301)和第二终端设备(比如终端设备1302)之间可以进行数据传输，比如第一终端设备获取数据包Z，并通过侧行链路将数据包Z发送给第二终端设备。
当上述图1a、图1b、图1c或图1d所示意的网络架构适用于5G通信系统(可简称为5GS(5G system))时，上述所描述的不同通信装置之间的数据传输可以基于5GS中的QoS模型来实现。参见图2b，为一种QoS模型示意图。
如图2b所示，在下行方向上，进入5GS的数据包在UPF实体处进行区分，比如UPF实体根据下行包检测规则(packet detection rule，PDR)的包过滤集合(packet filter sets)将下行数据包区分到不同的QoS流，同一QoS流内的所有数据包标记有相同的QFI。UPF实体将数据包通过N3接口传递到接入网(access network，AN)侧的网络设备。网络设备将QoS流映射到DRB，进而在Uu接口上进行下行数据的传输。在上行方向上，终端设备的应用层生成数据包后，根据SMF实体配置的QoS规则(rules)中的包过滤集合将上行数据包区分成不同的QoS流。终端设备的SDAP层实体根据基站配置的QFI到DRB的映射关系，将QoS流的数据包映射到对应的DRB上，然后在空口上进行上行数据的传输。示例性地，一个QoS流只能映射到一个DRB，不同QoS流可以映射到相同DRB；QoS流到DRB的映射关系可以由AN侧的网络设备来决定。
其中，QoS规则和PDR中的包过滤集合用于识别一个或多个数据包流(如网络协议 (internet protocol，IP)流)，包过滤集合中可以包括一个或多个包过滤模板。目前，5GS基于PDU会话类型定义了两类包过滤集合，即IP包过滤集合和以太网(Ethernet)包过滤集合。当PDU会话类型是IP时，包过滤集合支持以下任意组合的包过滤模板：源/目的IP地址或IPv6前缀；源/目的端口号；IP层之上协议的协议标识；IPv4的服务类型(type of service，TOS)字段/IPv6的流量类别和掩码；IPv6流标签；安全参数索引；包过滤方向。常用的包过滤模板采用前三者的组合，即通过IP数据包的五元组(源/目的地址，源/目的端口号，传输层协议)来进行数据包过滤。在本发明实施例中，将以IP数据包的五元组作为包过滤模板为例，具体实施例中也可以以上述任意组合作为包过滤模板。
根据上述描述可知，当采用图2b所示意的QoS模型时，若不同数据包的五元组相同，则会被标记相同的QFI，进而映射到同一QoS流中。进一步地，在核心网侧，标记有相同QFI的数据包将会受到相同的转发、调度待遇。在空口侧，DRB是数据包传输的一个逻辑管道，网络设备可以对DRB进行特定的配置，以保证通过该DRB进行处理和传输的数据包在空口侧能够达到的QoS要求，因此，通过该DRB传输的数据包在空口受到的待遇是相同的。也就是说，一个QoS流内的数据包在5GS内受到的待遇，如调度、转发优先级，总是相同的。
然而，在一些可能的场景中，比如SLVS场景、TCP数据流传输场景，同一QoS流中的数据可能具有不同的要求(比如时延要求)。具体来说，针对于SLVS场景，SLVS应用可以同时提供实时观看和延时观看的数据流，称之为“time-shifted viewing”特性，SLVS应用的观众具有广泛的延迟容忍度。图2c为一种可能的SLVS平台架构示意图，如图2c所示，直播者首先将直播视频流上传到服务器端，由服务器向不同类型的观众提供该视频流。对于SLVS视频流，在可用带宽受限时，优先保证实时观众的体验(比如可以只传输时延敏感的基本层数据帧)；在带宽充足时，可以进一步传输对实时观众而言已经过时(outdated)的增强层数据帧。此种情形下，同一个视频流在传输过程中既存在时延敏感的数据帧，也存在时延不太敏感但可靠性要求较高的数据帧。针对于TCP数据流传输场景，在TCP数据流中，TCP ACK帧的及时传输对拥塞控制有好处(即TCP ACK帧的时延要求较高)，因此同一个TCP数据流中，也存在重要性不同的数据帧。
以SLVS场景为例，由于直播者将直播视频流上传到服务器端时，这些直播视频流的五元组相同，而相同五元组的数据包在5GS内的QoS保障是相同的，因此当该直播视频流同时存在实时观众(时延敏感)和延时观看的观众时，该直播视频流所映射的QoS流只能按照时延敏感用户的需求设置QoS参数(如保证数据传输的时延，但传输可靠性不够高)，无法对不同数据帧进行区分处理，从而影响延时观看观众的体验。
基于此，本申请实施例提供一种数据传输方法，用于实现对数据进行区分处理，以满足用户的不同需求。
示例性地，本申请实施例提供的数据传输方法可以包括两种可能的方案，分别为方案一和方案二。在方案一中，第一通信装置获取第一数据包和第一数据包对应的第一QoS参数和第二QoS参数，并根据第一QoS参数和第二QoS参数，将第一数据包映射到DRB或RLC层实体，并发送给第二通信装置；此处的第二QoS参数可以为QFI或QFI’，有关第二QoS参数的描述可参见下文。采用该方案，由于第一通信装置是基于两种QoS参数将第一数据包映射到DRB或RLC层实体，相比于现有方案中根据第一数据包的五元组来确定第一数据包对应的QFI，进而根据QFI将第一数据包映射到DRB来说，更加全面地考 虑了第一数据包的服务质量要求，从而能够更有效地对数据进行区分处理，以满足用户的不同需求。示例性地，方案一可以适用于图1a所示意的网络架构，第一通信装置可以为终端设备；第二通信装置可以为网络设备。或者，第二通信装置可以为终端设备；第一通信装置可以为网络设备。或者，方案一可以适用于图1d所示意的网络架构，第一通信装置可以为终端设备(比如第一终端设备)，第二通信装置可以为另一终端设备(比如第二终端设备)。也就是说，方案一中，第一通信装置可以根据第一QoS参数和第二QoS参数，实现数据包在空口或sidelink接口上更细粒度的区分处理。
在方案二中，第一通信装置获取第二数据包和第二数据包对应的第一QoS参数和第二QoS参数，并向第二通信装置发送GTP-U数据包，GTP-U数据包中包括第二数据包、指示信息，指示信息用于指示第一QoS参数和第二QoS参数；此处的第二QoS参数可以为QFI(区别于QFI’)。示例性地，方案二可以适用于图1a所示意的网络架构，第一通信装置可以为网络设备；第二通信装置可以为核心网设备(比如UPF实体)。采用方案二，由于GTP-U数据包中包括第二数据包和指示信息，从而便于后续根据第一QoS参数和第二QoS参数来调度第二数据包，以实现数据包在端到端上更细粒度的区分处理。
下面先对本申请实施例涉及的相关技术特征进行解释说明。需要说明的是，这些解释是为了让本申请实施例更容易被理解，而不应该视为对本申请所要求的保护范围的限定。
(1)第一QoS参数
第一QoS参数可以称为增强QoS指示(enhanced QoS indicator，eQI)或者其它名称，具体不做限定。
作为示例，QoS流为PDU会话中的QoS区分粒度，第一QoS参数可以理解为PDU会话中的又一种QoS区分粒度。相比于QoS流来说，第一QoS参数的区分粒度更细。
作为示例，第一QoS参数可以用于指示服务质量等级，例如指示一个QoS流内的服务质量等级，使得一个QoS流内的数据包可以映射到不同的DRB或RLC层实体；或者，用作将数据包分流(过滤)的参考信元，比如作为包过滤模板的考虑因素，例如，用于将同一个五元组的数据流中的数据包分配到不同的QoS流，或分配不同的QFI。
本申请实施例中，第一QoS参数可以包括一个或多个比特，一个或多个比特的不同取值用于指示不同的服务质量等级。其中，确定服务质量等级的指标可以包括如下QoS指标中的一种或多种：优先级等级、包延迟预算、误包率、默认最大突发数据量、平均窗口等，比如可以根据反应数据包的实时性要求的包延迟预算和反应传输可靠性要求的误包率来确定服务质量等级，又比如可以根据数据包为新传或重传来确定服务质量等级。
举个例子，第一QoS参数包括2个比特，2个比特的不同取值可以用于指示4个不同的等级。比如，同一个应用产生的数据流中，第一部分数据包实时性要求比较高，传输可靠性要求也比较高，则该部分数据包对应的第一QoS参数可以标记为00；第二部分数据包实时性要求比较高，传输可靠性要求稍低，则该部分数据包对应的第一QoS参数可以标记为01；第三部分数据包实时性要求稍低，传输可靠性要求比较高，则该部分数据包对应的第一QoS参数可以标记为10；第四部分数据包实时性要求稍低，传输可靠性要求也比较低，则该部分数据包对应的第一QoS参数可以标记为11。
再举个例子，第一QoS参数包括1个比特，该比特的不同取值可以用于指示2个不同的等级；比如，将应用层进行新传的数据包对应的第一QoS参数标记为0，将应用层进行 重传的数据包对应的第一QoS参数标记为1。
再举个例子，第一QoS参数包括4个比特，4个比特的不同取值可以用于指示16个不同的服务质量等级。4个比特的取值所对应的数值越大，表示QoS要求越高。比如某一个数据包对应的第一QoS参数为1111时，表示该数据包的QoS要求最高；某一个数据包对应的第一QoS参数为0000时，表示该数据包的QoS要求最低。
(2)第二QoS参数
本申请实施例中，第二QoS参数可以用于标识QoS流，以使得SDAP层可以根据数据包的第二QoS参数将数据包映射到相应的DRB。
在一个示例(称为示例1)中，第二QoS参数可以为QFI，QFI的取值范围可以为【0，256】。
在该示例的一种可能的情形中，第二QoS参数可以为前文所提及的与包过滤模板(如五元组)存在对应关系的QFI。如此，当获取到数据包的包过滤模板后，可以根据包过滤模板和第二QoS参数之间的对应关系，得到数据包对应的第二QoS参数。比如，参见表1所示，当以五元组作为包过滤模板时，五元组和第二QoS参数之间的对应关系示例。
表1：包过滤模板和第二QoS参数之间的对应关系示例
包过滤模板 第二QoS参数
五元组1 1
五元组2 4
五元组3 9
五元组4 20
…… ……
在该示例的又一种可能的情形中，第二QoS参数可以为与第一QoS参数存在对应关系的QFI，可选地，还可以在该对应关系中引入其它可能的参数，比如五元组。以五元组、第一QoS参数和第二QoS参数之间存在对应关系为例，参见表2所示，为五元组、第一QoS参数和第二QoS参数的对应关系示例。
表2：五元组、第一QoS参数和第二QoS参数的对应关系示例
五元组 第一QoS参数 第二QoS参数
五元组1 0000 1
五元组1 0001 2
五元组1 0002 3
五元组2 0000 4
五元组2 0100 5
…… …… ……
根据上述表1和表2可知：上述表1中，五元组所对应的QFI仅为部分QFI，有些预留的QFI尚未设置其对应的五元组；在表2中，通过引入第一QoS参数，从而使得同一五元组的数据包有可能因为第一QoS参数的不同而对应不同的第二QoS参数；相比于表1来说，表2中可以通过利用预留的QFI来对数据包进行进一步的区分处理。
本申请实施例中，为便于区分，将表1中涉及的第二QoS参数称为QFI，将表2中所 涉及的第二QoS参数称为QFI’。此外，本申请实施例中所涉及的“对应关系”也可以替换为“映射关系”或者其它表示类似含义的词语，“关联”也可以替换为“对应”或者其它表示类似含义的词语。
在又一个示例(称为示例2)中，第二QoS参数也可以为新定义的一个用于标识QoS流的参数，新定义的第二QoS参数可以与五元组、第一QoS参数之间存在对应关系，具体实现可以参照QFI’。
(3)重复传输功能
发送端和接收端之间可以建立至少一个无线承载(radio bearer，RB)来传输数据。无线承载可以分为用于传输信令数据的信令无线承载(signalling radio bearer，SRB)和用于传输业务数据的数据无线承载(data radio bearer，DRB)，同一无线承载的一组功能实体集合包括一个PDCP层实体，该PDCP层实体对应的至少两个RLC层实体，至少两个RLC层实体对应的至少一个MAC实体，至少一个MAC实体对应的至少一个PHY实体。
重复传输或者说PDCP层的重复传输，通常指将无线承载的数据包在PDCP层复制成多个相同的包(也就是重复包)，然后这两个数据包分别递交给多个不同的RLC层实体进行传输，进而通过不同的逻辑信道传输到MAC层。其中，逻辑信道是RLC层到MAC层之间的信道。需要注意的是，通常所说的重传是指重新传输(retransmission)，而本申请实施例中的重复传输(duplication transmission)并不是重新传输。重新发送是指同一个数据包发送失败后的再次发送，或者是同一个数据包的连续多次发送，而重复传输是将一个数据包复制两个数据包，分别放到两个逻辑信道上传输，这里的“重复”，也可以理解为“复制”。
在图2d所示的数据重复传输示意图中，对于发送端和接收端之间的一个无线承载，发送端上由于同一PDCP层实体对应至少两个RLC层实体，每个RLC层实体分别对应一条逻辑信道来发送数据。相应地，接收端上同一PDCP层实体对应至少两个RLC层实体，每个RLC层实体对应一条逻辑信道来接收数据。因此，发送端和接收端之间这个无线承载上包含至少两个逻辑信道。其中，在图1a、图1b、图1c所示意的网络架构中，发送端可以为终端设备，接收端可以为网络设备；或者，接收端可以为终端设备，发送端可以为网络设备。在图1d所示意的网络架构中，发送端可以为第一终端设备(比如终端设备1301)，接收端可以为第二终端设备(比如终端设备1302)；或者，接收端可以为第二终端设备，发送端可以为第一终端设备；此种情形下，第一终端设备和第二终端设备之间的DRB也可以称为sidelink DRB。
图2d所示的发送端和接收端分别包含同一PDCP层实体以及所述同一PDCP层实体关联的第一RLC层实体和第二RLC层实体，其中，第一RLC层实体对应第一逻辑信道，第二RLC层实体对应第二逻辑信道。发送端在第一逻辑信道对应的小区1b或小区组1向接收端发送第一逻辑信道上的数据，接收端在第一逻辑信道对应的小区1b或小区组1接收发送端发送的第一逻辑信道的数据。发送端在第二逻辑信道对应的小区2b或小区组2向接收端发送第二逻辑信道的数据，接收端在第二逻辑信道对应的小区2b或小区组2接收第二逻辑信道上的数据。在重复模式下，在发送端的第二RLC层实体和发送端的第一RLC层实体上对来自同一PDCP层实体的数据进行重复传输，从而可以提高发送端发送数据的可靠性。需要说明的是，图2d在是以发送端和接收端分别对应两个小区组为例，在其它可能的情形中，发送端和接收端也可以分别对应一个小区组，具体不做限定。
需要说明的是，上述是以两个逻辑信道的PDCP层的重复为例进行描述的，在其它可 能的实施例中，还可能是更多个逻辑信道的PDCP层的重复，也就是说，一个无线承载通过更多个逻辑信道来传输在PDCP层被复制的数据包，例如可能通过三个或四个逻辑信道来传输在PDCP层被复制的数据包。
进一步地，以发送端为终端设备，接收端为网络设备为例，当网络设备为终端设备的一个DRB配置了重复传输功能后，可以激活或去激活该DRB的重复传输功能。比如，参见上述图2d所示，网络设备为该DRB的PDCP层实体配置了第一RLC层实体和第二RLC层实体，若网络设备激活该DRB的重复传输功能，则PDCP层实体的数据可以通过第一RLC层实体和第二RLC层实体进行重复传输；若网络设备去激活该DRB的重复传输功能，则PDCP层实体的数据不再进行重复传输，比如可以通过第一RLC层实体进行传输或通过第二RLC层实体进行传输。或者，网络设备也可以通过控制信令指示终端设备通过哪一条或哪几条RLC层实体对该DRB的数据包进行传输；比如，控制信令可以是MAC控制元素(control element CE)，MAC CE可以包括DRB ID、LCH ID的指示信息。相应地，终端设备接收到MACCE后，对所指示的DRB，通过所指示的LCH或RLC层实体进行数据包传输。
(4)RLC层实体的传输模式
RLC层实体的传输模式可以包括透明模式(transparent mode，TM)、非确认模式(unacknowledged mode，UM)和确认模式(acknowledged mode，AM)。其中，若RLC层实体的传输模式为TM，则RLC层实体不对递交到RLC层实体的SDU做任何处理，直接透传。若RLC层实体的传输模式为UM，则RLC层实体可以对递交到RLC层实体的SDU进行处理(比如可以添加额外信息)，进而发送RLC PDU，且不需要对等实体的确认，也不再进行重传。若RLC层实体的传输模式为AM，则RLC层实体可以对递交到RLC层实体的SDU进行处理(比如可以添加额外信息)，进而发送RLC PDU，且需要对等实体的确认，若对等实体确认该RLC PDU已成功接收，则无需在对该RLC PDU进行重传，否则需要对该RLC PDU进行重传。
(5)缓存状态报告(buffer status report，BSR)
5G通信系统中，LCH可以用来承载数据，不同业务类型的数据可以通过不同的LCH承载。每个LCH可以关联一个调度优先级，该优先级可以通过网络设备配置，例如承载URLLC业务数据的LCH可以配置较高的优先级，承载eMBB业务数据的LCH可以配置较低的优先级，也就是说URLLC业务数据的优先级较高，而eMBB业务数据的优先级较低，从而当终端设备有可用的上行资源时，可以优先考虑为高优先级的数据进行资源分配。当有新数据到达而所有LCH都没有待发送数据或者更高优先级的LCH有待发送数据时，终端设备的MAC层可以触发BSR，用于反映至少一个LCH的待传输数据总量，供网络设备调度。
基于上述对相关特征的描述，下面结合实施例一至实施例三对本申请实施例的方案进行详细说明。
实施例一
图3为本申请实施例一提供的数据传输方法所对应的流程示意图，如图3所示，包括：
步骤301，第一终端设备获取数据包和数据包对应的第一QoS参数和第二QoS参数。
其中，第一终端设备获取数据包和数据包对应的第一QoS参数的实现方式可以有多种。 在一个示例中，第一终端设备的应用层可以获取应用程序产生的数据包，并为数据包分配第一QoS参数，即第一QoS参数可以为第一终端设备的应用层为数据包分配的。应用层为数据包分配第一QoS参数的依据可以有多种，比如应用层可以根据数据包的QoS要求为数据包分配第一QoS参数，本申请实施例中对应用层为数据包分配第一QoS参数的具体实现不做限定。
在又一个示例中，第一终端设备可以与其它装置连接，其它装置可以为工业设备，比如传感器、操作臂等。进而第一终端设备可以接收来自其它装置的数据包和数据包对应的第一QoS参数，即第一QoS参数可以为工业设备为数据包分配的。工业设备为数据包分配第一QoS参数的依据可以有多种，具体不做限定。第一终端设备从工业设备接收到数据包和数据包对应的第一QoS参数后，可以将数据包和数据包对应的第一QoS参数递交给非接入层或者接入层处理。
在又一个示例中，第一QoS参数可以为第一终端设备的非接入层为数据包分配的，比如若数据包中包括TCP ACK，则可以由非接入层识别并分配第一QoS参数。非接入层获取到数据包和数据包对应的第一QoS参数后，可以向接入层递交数据包和数据包对应的第一QoS参数，或者，也可以根据第一QoS参数确定数据包对应的第二QoS参数(此时第二QoS参数为QFI’)，进而向接入层递交数据包和数据包对应的第二QoS参数。非接入层为数据包分配第一QoS参数的依据可以有多种，具体不做限定。
下文在描述时，将以第一QoS参数为第一终端设备的应用层为数据包分配的为例进行描述，其它情形可以参照处理，以及下文中将第一QoS参数称为eQI。
步骤302，第一终端设备根据数据包对应的eQI和第二QoS参数，将数据包映射到DRB或RLC层实体，并发送给网络设备或第二终端设备。
下面以数据包为第一数据包为例，描述上述步骤301和步骤302的几种可能的实现方式。
实现方式1
在实现方式1中，第二QoS参数可以为QFI(区别于QFI’)。
参见图4a所示，步骤301和步骤301的具体实现可以为：第一终端设备的应用层可以获取第一数据包和第一数据包对应的eQI，进而将第一数据包和第一数据包对应的eQI递交给非接入层；非接入层接收到第一数据包和第一数据包对应的eQI后，根据QoS规则中的包过滤模板可以确定第一数据包对应的QFI，并为第一数据包标识对应的QFI。非接入层将第一数据包、第一数据包对应的QFI和eQI递交到SDAP层实体。SDAP层实体根据第一数据包对应的QFI和eQI将第一数据包映射到DRB，并发送给网络设备或第二终端设备。
其中，第一终端设备可以获取QFI、eQI和DRB之间的对应关系(也可以描述为QFI+eQI和DRB之间的对应关系)，进而第一终端设备的SDAP层实体根据该对应关系以及第一数据包对应的QFI、eQI，将第一数据包映射到QFI、eQI对应的DRB。比如，QFI、eQI和DRB之间的对应关系可以为网络设备通过RRC信令为所示第一终端设备配置的，具体的配置方式可以有多种，比如，网络设备通过RRC重配置(RRC Reconfiguration)消息中携带的DRB添加(DRB-ToAddMod)信元中的SDAP配置(SDAP-Config)信元来配置QFI、eQI和DRB之间的对应关系。
参见表3所示，为QFI、eQI和DRB之间的对应关系示例。
表3：QFI、eQI和DRB之间的对应关系示例
Figure PCTCN2019124396-appb-000001
从表3可以看出，同一个QFI的QoS流中对应不同eQI的数据包可以映射到相同或者不同的DRB中。比如，对于QFI为1的QoS流中，对应的eQI为eQI 1的数据包需映射到DRB 1中进行处理和传输，对应的eQI为eQI 2的数据包需映射到DRB 2中进行处理和传输。
示例性地，假设第一数据包对应的eQI为eQI 2，第一数据包对应的QFI为QFI 1，根据表3可知，QFI 1+eQI 2对应DRB 2；此种情形下，第一终端设备的SDAP层实体可以将第一数据包映射到DRB 2中。
再假设第一数据包对应的eQI为eQI 3，第一数据包对应的QFI为QFI 1，表3所示意的对应关系中不存在QFI 1+eQI 3对应的DRB。此种情形下，在一个示例中，当没有与第一数据包对应的QFI和eQI匹配的DRB时，第一终端设备可以向网络设备发送请求消息1，请求消息1中可以包括QFI 1(或者用于指示QFI 1的信息)和eQI 3(或者用于指示eQI 3的信息，比如eQI 3的索引)，相应地，网络设备接收到请求消息1后，可以向第一终端设备返回响应消息1，响应消息1中包括QFI 1+eQI 3对应的DRB ID(或者用于指示QFI 1+eQI3对应的DRB的信息)，进而第一终端设备可以将第一数据包映射到QFI 1+eQI 3对应的DRB中。进一步地，第一终端设备可以根据QFI 1+eQI 3对应的DRB对表3进行更新。采用该种方式，网络设备可以根据第一终端设备的请求消息为第一终端设备配置DRB，避免一开始为第一终端设备配置大量的DRB所带来的信令开销和第一终端设备的维护复杂度。
在又一个示例中，当没有与第一数据包对应的QFI和eQI匹配的DRB时，第一终端设备可以将第一数据包映射到默认DRB中。默认DRB的一种实现方式是每个QFI可以有一个对应的默认DRB，一个QFI对应的默认DRB可以是网络设备配置的，比如网络设备为QFI 1配置DRB 1为默认DRB；又或者，一个QFI对应的默认DRB可以为第一终端设备基于预设规则1确定的，比如预设规则1可以为一个QFI对应或关联的所有DRB中DRB ID或对应的LCH ID最小/最大的为默认DRB，或者一个QFI对应或关联的所有DRB中逻辑信道优先级最高/最低的为默认DRB，以表3为例，若确定DRB ID最小的为默认DRB，则DRB 1为QFI 1对应的默认DRB。默认DRB的另一种实现方式是所有QFI共用一个默认DRB，默认DRB可以是网络设备配置的，或者第一终端设备基于预设规则2确定的，比如预设规则2可以是所有DRB或与该SDAP层实体关联的所有DRB中DRB ID或对应的LCH ID最小/最大的为默认DRB，或者逻辑信道优先级最高/最低的为默认DRB。其中，预设规则1或预设规则2可以是协议预定义的，或者是由网络设备确定并指示给终端设备的。
针对于该示例，在一种可选的方案中，第一终端设备将第一数据包映射到默认DRB中后，还可以执行上一示例中的操作，即向网络设备发送请求消息1，请求QFI 1+eQI 3 对应的DRB，并对表3进行更新，以便于将下一个对应QFI 1+eQI 3的数据包映射到QFI1+eQI 3对应的DRB中。
在实现方式1中，第一终端设备可以将第一数据包对应的eQI封装到第一数据包中，进而发送给网络设备或第二终端设备；或者，也可以将第一数据包对应的eQI不封装到数据包中，而是和第一数据包一起发送给网络设备或第二终端设备层。
以第一终端设备可以将第一数据包对应的eQI封装到第一数据包中为例，比如，第一数据包的SDAP头中可以包括第一数据包对应的eQI(或者用于指示第一数据包对应的eQI的信息)；比如，第一终端设备的SDAP层实体接收到第一数据包、第一数据包对应的QFI1和eQI后，可以将第一数据包对应的eQI封装到第一数据包的SDAP头，进而将封装后的第一数据包映射到DRB或者说递交给PDCP层实体。或者，第一数据包的PDCP头中可以包括第一数据包对应的eQI(或者用于指示第一数据包对应的eQI的信息)；比如，SDAP层实体将第一数据包递交给PDCP层实体时，还可以进一步指示第一数据包对应的eQI，相应地，PDCP层实体接收到SDAP层实体递交的第一数据包后，可以将第一数据包对应的eQI封装到第一数据包的PDCP头中。
需要说明的是，若一个PDCP层实体只对应一个eQI时，则SDAP层实体将第一数据包递交给该PDCP层实体时，也可以不再指示第一数据包对应的eQI，相应地，PDCP层实体接收到SDAP层实体递交的第一数据包后，可以将该PDCP层实体对应的eQI封装到第一数据包的PDCP头中。由于第一数据包的SDAP头或PDCP头中包括第一数据包对应的eQI，从而便于第二通信装置接收到第一数据包后，可以获取到第一数据包对应的eQI。
在实现方式1中，网络设备可以对同一个QFI对应的多个DRB进行独立配置，即PDCP层实体、RLC层实体和逻辑信道均可以独立进行配置。举个例子，QFI 1对应的DRB 1和DRB 2可以进行独立配置，则DRB 1对应的PDCP层实体1和DRB 2对应的PDCP层实体2的配置可以不同，和/或，PDCP层实体1关联的RLC层实体(或逻辑信道)和PDCP层实体2关联的RLC层实体(逻辑信道)的配置可以不同。其中，PDCP层实体1和PDCP层实体2的配置不同可以是指PDCP层实体1的参数和PDCP层实体2的参数不同，比如PDCP层实体的参数可以包括丢弃时长(PDCP层实体收到一个PDCP SDU后会启动一个定时器(timer)，超时后执行PDCP SDU丢弃(discard)操作，该定时器的时长可以称为丢弃时长)，PDCP层实体1的丢弃时长为10ms，PDCP层实体2的丢弃时长为20ms。PDCP层实体1关联的RLC层实体(比如包括RLC层实体1)和PDCP层实体2关联的RLC层实体(比如包括RLC层实体1a)的配置不同可以是指RLC层实体1的传输模式和RLC层实体1a的传输模式不同，比如RLC层实体1的传输模式为UM，RLC层实体1a的传输模式为AM。
如此，由于同一个QFI对应的多个DRB可以独立配置，从而通过将对应同一个QFI但对应不同eQI的数据包映射到不同的DRB，可以实现对同一QoS流中的数据包进行区分处理，即使得对时延或可靠性要求不同的数据包在空口可以得到区分处理。
实现方式2
在实现方式2中，第二QoS参数可以为QFI’。
参见图4b所示，步骤301和步骤302的具体实现可以为：第一终端设备的应用层可以获取第一数据包和第一数据包对应的eQI，进而将第一数据包和第一数据包对应的eQI递交给非接入层；非接入层接收到第一数据包和第一数据包对应的eQI后，可以确定第一 数据包对应的QFI’，并为第一数据包标识对应的QFI’。非接入层将第一数据包、第一数据包对应的QFI’递交到SDAP层。SDAP层实体根据第一数据包对应的QFI’将第一数据包映射到DRB，并发送给网络设备或第二终端设备。
示例性地，第一终端设备可以获取表2所示意的对应的关系，进而第一终端设备的非接入层可以根据表2所示意的对应关系以及第一数据包对应的eQI和五元组，确定第一数据包对应的QFI’。第一终端设备可以获取表2所示意的对应的关系的方式可以有多种，比如表2所示意的对应关系可以为核心网设备通过非接入层消息为第一终端设备配置的，如SMF实体通过PDU会话建立或修改(PDU session establishment/modification)流程为第一终端设备配置。根据表2可知，相同五元组的数据流中不同eQI的数据包可以映射为不同的QFI’，进而可以通过不同的DRB进行处理和传输。
示例性地，第一终端设备可以获取QFI’和DRB ID的对应关系，进而第一终端设备的SDAP层实体可以根据QFI’和DRB ID的对应关系，将第一数据包映射到QFI’对应的DRB。比如，第一终端设备可以从网络设备获取QFI’和DRB ID的对应关系。第一终端设备获取QFI’和DRB ID的对应关系的方式也可以参见现有方案中终端设备获取QFI和DRB ID的对应关系的方式，具体不再赘述。
采用实现方式2，通过引入eQI，并由非接入层进行五元组、eQI到QFI’的映射，从而可以实现对不同eQI的数据包进行区分处理，即使得对时延或可靠性要求不同的数据包在空口得到区分处理。而且该种方式无需改变接入层的操作，具有较强的适用性。
实现方式3
在实现方式3中，第二QoS参数可以为QFI(区别于QFI’)。
参见图4c所示，步骤301和步骤302的具体实现可以为：第一终端设备的应用层可以获取第一数据包和第一数据包对应的eQI，进而将第一数据包和第一数据包对应的eQI递交给非接入层；非接入层接收到第一数据包和第一数据包对应的eQI后，根据QoS规则中的包过滤模板可以确定第一数据包对应的QFI，并为第一数据包标识对应的QFI。非接入层将第一数据包、第一数据包对应的QFI和eQI递交到SDAP层。SDAP层实体根据第一数据包对应的QFI将第一数据包和第一数据包对应的eQI映射到DRB(即递交给DRB对应的PDCP层实体)，PDCP层实体根据第一数据包对应的eQI，将第一数据包映射到RLC层实体或LCH，并发送给网络设备或第二终端设备。
其中，DRB对应的PDCP层实体可以关联多个RLC层实体，且多个RLC层实体与eQI存在对应关系。比如，网络设备可以为终端设备配置PDCP层实体关联的多个RLC层实体，以及eQI到RLC层实体的对应关系；具体的配置方式可以有多种，一种可能的配置方式为，网络设备为一个RLC层实体或与一个RLC层实体对应的逻辑信道进行配置时，在配置信元中指示DRB ID以及eQI集合，表示该RLC层实体关联到DRB ID对应的PDCP层实体，并且RLC层实体对应的eQI为eQI集合中包括的eQI(或者说RLC层实体用于处理映射到该DRB中且对应的eQI为eQI集合所包含的eQI的数据包)；上述eQI集合可以包括一个eQI，或多个eQI。举个例子，网络设备在RLC层实体1的配置信元(RLC-BearerConfig或RLC-Config)中指示的DRB ID为DRB 1，指示的eQI集合包括eQI 1和eQI 2，如此第一终端设备可获知RLC层实体1关联到DRB 1对应的PDCP层实体1，RLC层实体1对应的eQI包括eQI 1和eQI 2(或者说RLC层实体1用于处理映射到DRB 1中且对应的eQI为eQI 1或eQI 2的数据包)。
应理解，由于RLC层实体与LCH一一对应，因此，本申请实施例中涉及RLC实体之处也可以适应性延伸得到其对应的LCH的内容。比如，多个RLC层实体与eQI存在对应关系，也可以适应性延伸得到多个RLC层实体对应的多个LCH与eQI存在对应关系，其也在本申请的保护范围之内。
参见表4所示，DRB1对应的PDCP层实体1关联RLC层实体1、RLC层实体2，每个RLC层实体对应一个eQI集合，eQI集合可以包括一个或多个eQI。其中，RLC层实体1对应的eQI集合包括eQI1、eQI2，RLC层实体2对应的eQI集合包括eQI3、eQI4。
表4：PDCP层实体1关联的RLC层实体和eQI集合的对应关系示例
DRB ID RLC层实体 eQI集合
DRB 1 RLC层实体1 eQI 1、eQI 2
DRB 1 RLC层实体2 eQI 3、eQI 4
从表4可以看出，同一DRB中对应不同eQI的数据包可以映射到相同或者不同的RLC层实体中。比如，DRB 1中对应的eQI为eQI 1或eQI 2的数据包需映射到RLC层实体1中进行处理和传输，对应的eQI为eQI 3或eQI 4的数据包需映射到RLC层实体2中进行处理和传输。
如此，第一终端设备可以获取PDCP层实体关联的RLC层实体和eQI对应关系，进而第一终端设备的PDCP层实体可以根据该对应关系以及第一数据包对应的eQI，将第一数据包映射到eQI对应的RLC层实体。
假设映射到DRB 1中的第一数据包对应的eQI为eQI 2，则根据表4可知，eQI 2对应RLC层实体1；此种情形下，DRB 1对应的PDCP层实体1可以将第一数据包映射到RLC层实体1中。
再假设映射到DRB 1中的第一数据包对应的eQI为eQI 5，表4所示意的对应关系中不存在eQI 5对应的RLC层实体。此种情形下，在一个示例中，当没有与第一数据包对应的eQI匹配的RLC层实体时，第一终端设备可以向网络设备发送请求消息2，请求消息2中可以包括eQI 5(或者用于指示eQI 5的信息，比如eQI 5的索引)，相应地，网络设备接收到请求消息2后，可以向第一终端设备返回响应消息2，响应消息2中包括PDCP层实体1关联的多个RLC层实体中eQI 5对应的RLC层实体的标识(或者用于指示eQI 5对应的RLC层实体的信息)，进而第一终端设备可以将第一数据包映射到eQI 5对应的RLC层实体中。进一步地，第一终端设备可以根据eQI 5对应的RLC层实体对表4进行更新。采用该种方式，网络设备可以根据第一终端设备的请求消息为第一终端设备配置RLC层实体，避免一开始为第一终端设备配置大量的RLC层实体所带来的信令开销和第一终端设备的维护复杂度。
在又一个示例中，当没有与第一数据包对应的eQI匹配的RLC层实体时，第一终端设备可以将第一数据包映射到默认RLC层实体中，其中该默认RLC层实体可以为DRB 1对应的默认RLC层实体，DRB 1对应的默认RLC层实体可以是网络设备配置的，比如网络设备为DRB 1配置RLC层实体1为默认RLC层实体，具体的配置方式可以有多种，如网络设备在RLC层实体1的配置信元中指示RLC层实体1为默认RLC层实体；又或者，DRB1对应的默认RLC层实体可以为第一终端设备基于预设规则3确定的，比如预设规则3可以为DRB1对应的PDCP层关联的RLC层实体中对应的LCH ID最小/最大的为默认 RLC层实体，以表4为例，若确定对应的LCH ID最小的RLC层实体为默认RLC层实体，则RLC层实体1为DRB 1对应的默认RLC层实体。其中，预设规则3可以是协议预定义的，或者是由网络设备确定并指示给终端设备的。
在实现方式3中，当DRB的PDCP层实体关联多个RLC层实体时，这些RLC层实体可以独立配置，比如多个RLC层实体可以配置为不同的传输模式。举个例子，DRB 1对应的PDCP层实体关联2个RLC层实体(分别为RLC层实体1、RLC层实体2)，其中，RLC层实体1可以配置为UM，RLC层实体2可以配置为AM。如此，由于PDCP层实体关联的多个RLC层实体独立配置，从而通过将不同eQI的数据包映射到不同的RLC层实体上能够实现对同一QoS流中的数据包进行区分处理。
在实现方式3中，网络设备可以为DRB对应的PDCP层实体配置一组参数，或者也可以配置多组参数。示例性地，PDCP层实体的参数可以包括一种或多种可能的参数，下面以PDCP层实体的参数包括丢弃时长为例进行描述。
当网络设备为PDCP层实体配置多组参数时，还可以进一步配置eQI和多组参数之间的对应关系，参见表5所示，为eQI和多组参数之间的对应关系示例。
表5：eQI和多组参数之间的对应关系示例
eQI 丢弃时长
eQI1、eQI2、eQI3、eQI4 丢弃时长1(比如10ms)
eQI4、eQI5、eQI6 丢弃时长2(比如15ms)
eQI7、eQI8 丢弃时长3(比如20ms)
当网络设备为PDCP层实体配置一组参数(比如配置了丢弃时长1)，则PDCP层实体可以根据该丢弃时长对递交到PDCP层实体的数据包进行处理。若网络设备为PDCP层实体配置多组参数(比如丢弃时长1、丢弃时长2和丢弃时长3)，以及第一QoS参数和多组参数之间的对应关系，则PDCP层实体可以根据表5所示意的对应关系，采用数据包对应的第一QoS参数所对应的PDCP层实体的参数对数据包进行处理，比如数据包1对应的第一QoS参数为eQI 1，则可以采用丢弃时长1对数据包1进行处理，又比如数据包2对应的第一QoS参数为eQI 4，则可以采用丢弃时长2对数据包2进行处理。如此，由于为PDCP层实体配置了多组参数，从而通过对不同eQI的数据包采用相同或不同的参数进行处理，能够实现对同一QoS流中的数据包进行区分处理。
在实现方式3中，由于PDCP层实体是根据数据包对应的eQI将数据包映射到eQI对应的RLC层实体上，因此，本申请实施例中在配置重复传输功能时，可以在一个DRB中，针对eQI配置重复传输功能，即对应该eQI的数据包可以复制递交到多个RLC层实体。其中，该DRB对应的PDCP层实体可以关联多个RLC层实体，配置重复传输的eQI对应多个RLC层实体中的至少两个RLC层实体，至少两个RLC层实体用于实现重复传输。比如，参见上述表6所示，eQI 3对应RLC层实体1、RLC层实体2和RLC层实体3，进而可以针对eQI 3配置重复传输功能。
表6：RLC层实体和eQI集合的对应关系示例
DRB ID RLC层实体 eQI集合
DRB 1 RLC层实体1 eQI 1、eQI 2、eQI 3
DRB 1 RLC层实体2 eQI 3、eQI 4
DRB 1 RLC层实体3 eQI 3
进一步地，在一个示例中，网络设备可以通过控制信令激活或去激活针对eQI3配置的重复传输功能，比如，若网络设备通过控制信令激活针对eQI3配置的重复传输功能，第一数据包对应的eQI为eQI3，则第一终端设备的PDCP层实体可以将第一数据包映射到RLC层实体1、RLC层实体2和RLC层实体3中进行重复传输；若网络设备通过控制信令去激活针对eQI3配置的重复传输功能，则第一终端设备的PDCP层实体可以将第一数据包映射到RLC层实体1中进行传输或映射到RLC层实体2中进行传输或映射到RLC层实体3中进行传输。
在又一个示例中，网络设备可以通过控制信令指示通过eQI3对应的哪些RLC层实体进行层重复传输。比如，若网络设备通过控制信令指示RLC层实体1和RLC层实体2，则第一终端设备的PDCP层实体可以将第一数据包映射到RLC层实体1和RLC层实体2中进行重复传输；示例性地，控制信令中可以包括DRB 1(或者用于指示DRB 1的信息)、eQI3(或者用于指示eQI3的信息)以及RLC层实体1和RLC层实体2的标识(或者用于指示RLC层实体1和RLC层实体2的信息，或者RLC层实体1对应的LCH 1和RLC层实体2对应的LCH 2，或者用于指示LCH 1和LCH 2的信息)。
需要说明的是，上述控制信令可以为RRC信令或者MAC CE，具体不做限定。
在实现方式3中，第一数据包的SDAP头或PDCP头或RLC头中可以包括第一数据包对应的eQI(或者用于指示第一数据包对应的eQI的信息)。
在实现方式3中，终端设备的MAC层在进行BSR上报时，需要计算不同LCH的待传输数据量，其中，计算不同LCH的待传输数据量的一种可能的方式为，针对于其中一个LCH(比如LCH 1)，将LCH 1对应的RLC层实体1和PDCP层实体1的待传输数据量确定为LCH 1的缓存状态(buffer status，BS)量；类似地，针对于LCH 2，将LCH 2对应的RLC层实体2和PDCP层实体1的待传输数据量确定为LCH 2的BS量。由此可知，采用这种方式，在计算LCH 1和LCH 2的BS量时都将PDCP层实体1的待传输数据量计算进来，比如PDCP层实体1的待传输数据包括数据包1和数据包2，数据包1对应的eQI为eQI 1，数据包2对应的eQI为eQI 4，参见上述表4所示，后续传输时，数据包1是映射到RLC层实体1(或LCH 1)进行传输，数据包2是映射到RLC层实体2(或LCH 2)进行传输，但在计算LCH 1的BS量时将数据包1和数据包2计算进来，在计算LCH 2的BS量时也将数据包1和数据包2计算进来，从而会导致上报给网络设备的总BS量会超过终端设备的实际待传输数据量，造成后续调度资源的浪费。
基于此，本申请实施例中，可以将PDCP层实体上的数据量按照比例分配到不同LCH，具体比例可以由网络进行配置，或由应用层指示，或终端设备实现决定。举个例子，PDCP层实体1上的数据量为100，由于PDCP层实体1关联RLC层实体1、RLC层实体2和RLC层实体3，进而在计算LCH 1、LCH 2和LCH 3时，可以将PDCP层实体1上的数据量按照比例分配给LCH 1、LCH 2和LCH 3，比如可以将LCH 1对应的RLC层实体1的待传输数据量和PDCP层实体1的待传输数据量的40％确定为LCH 1的BS量，将LCH 2对应的RLC层实体2的待传输数据量和PDCP层实体1的待传输数据量的30％确定为LCH2的BS量，将LCH 3对应的RLC层实体3的待传输数据量和PDCP层实体1的待传输数 据量的30％确定为LCH 3的BS量。如此，能够有效降低因上报给网络设备的总BS量超过终端设备的实际待传输数据量而造成的资源浪费。
针对于上述实现方式1、实现方式2和实现方式3，需要说明的是，第一终端设备的应用层获取到第一数据包和第一数据包对应的eQI后，可以将eQI或者用于指示该eQI的信息封装到第一数据包中，比如将eQI或者用于指示该eQI的信息封装到应用层为第一数据包生成的头(header)中，进而递交给非接入层；进一步地，非接入层(或接入层)在接收到第一数据包后，可以将应用层生成的头剥离掉，从中获取第一数据包对应的eQI，进而执行后续处理；应理解，剥离掉的头可不在空口上进行传输。或者，第一终端设备也可以不将eQI封装到第一数据包中，而是和第一数据包一起递交给非接入层或接入层。
综合上述内容可知，本申请实施例中通过引入eQI，实现了数据包在空口或sidelink接口上更细粒度的区分处理，从而能够有效满足用户的不同需求，比如可以满足实时观看的用户和延时观看的用户的需求。
实施例二
图5a为本申请实施例二提供的数据传输方法所对应的流程示意图，图5b为本申请实施例二提供的数据传输过程示意图。
如图5a和图5b所示，包括：
步骤501，终端设备1获取第二数据包和第二数据包对应的eQI和QFI。
步骤502，终端设备1根据eQI和QFI，将第二数据包映射到DRB或RLC层实体，并发送给网络设备1。
示例性地，终端设备1可以采用实施例一中所描述的实现方式1或实现方式3将第二数据包发送给网络设备1。
步骤503，网络设备1获取第二数据包和第二数据包对应的eQI和QFI，并向UPF实体1发送GTP U数据包1。
此处，GTP U数据包1可以包括第二数据包和指示信息1，指示信息1用于指示第二数据包对应的eQI。示例性地，指示信息1可以包括第二数据包对应的eQI，或者第二数据包对应的eQI的索引，又或者其它用于指示第二数据包对应的eQI的信息，具体不做限定。进一步地，指示信息1还可以用于指示第二数据包对应的QFI。示例性地，指示信息1可以携带在GTP U头(GTP-U header)中。
网络设备1获取第二数据包对应的eQI的方式可以有多种。一种可能的方式为，终端设备1将第二数据包对应的eQI传输给网络设备1。比如，当终端设备1采用实现方式1时，第二数据包对应的eQI(或者用于指示第一数据包对应的eQI的信息)可以携带在SDAP头或PDCP头中；当终端设备采用实现方式3时，第二数据包对应的eQI(或者用于指示第一数据包对应的eQI的信息)可以携带在SDAP头或PDCP头或RLC头中。又比如，或者，当终端设备1采用实现方式1或实现方式3时，第二数据包对应的eQI(或者用于指示第一数据包对应的eQI的信息)未封装在第二数据包中，而是和第二数据包一起传输给网络设备1。又一种可能的方式为，终端设备1未将第二数据包对应的eQI传输给网络设备1，网络设备1可以根据承载第二数据包的DRB或RLC层实体来确定第二数据包对应的eQI；比如，当终端设备采用实现方式1时，若DRB对应一个eQI，则网络设备可以承载第二数据包的DRB确定第二数据包对应的eQI；当终端设备采用实现方式3时，若 RLC层实体对应一个eQI，则网络设备可以承载第二数据包的RLC层实体确定第二数据包对应的eQI。
步骤504，UPF实体1获取第二数据包、第二数据包对应的eQI和QFI，并通过IMS网络或者服务器将第二数据包、第二数据包对应的eQI和QFI传输给UPF实体2。
此处，UPF实体1可以向IP多媒体子系统(IP multimedia subsystem，IMS)网络或视频服务器(vedio server)发送IP数据包1，IP数据包1中包括第二数据包和指示信息1，指示信息1可以携带在IP数据包1的某层协议头中。相应地，IMS网络或视频服务器向UPF实体2发送IP数据包2，IP数据包2中包括第二数据包和指示信息1，指示信息1可以携带在IP数据包2的某层协议头中。
步骤505，UPF实体2获取第二数据包、第二数据包对应的eQI和QFI，并向网络设备2发送GTP U数据包2。
此处，GTP U数据包2可以包括第二数据包和指示信息1。
步骤506，网络设备2获取第二数据包、第二数据包对应的eQI和QFI，并根据第二数据包对应的eQI和QFI将第二数据包发送给终端设备2。
此处，网络设备2可以采用实施例一中所描述的实现方式1或实现方式3将第二数据包传输给终端设备2。应理解，由于网络设备2不具有应用层和非接入层，因此当采用实现方式1或实现方式3时，网络设备2从GTP-U数据包中获取到第二数据包、第二数据包对应的eQI和QFI后，可将第二数据包、第二数据包对应的eQI和QFI递交给SDAP层实体来执行相应操作。比如当采用实现方式1时，SDAP层实体可以根据第二数据包对应的eQI和QFI将第二数据包映射到eQI、QFI对应的DRB中；当采用实现方式3时，SDAP层实体可以根据第二数据包对应的QFI将第二数据包映射到QFI对应的DRB中，进而DRB对应的PDCP层实体可以根据第二数据包对应的eQI，将第二数据包映射到eQI对应的RLC层实体中。
采用上述方法，在现有QFI基础上进一步对数据包的QoS进行细化，并通过QFI和eQI对数据包进行端到端的区分处理。
实施例三
图6a为本申请实施例三提供的数据传输方法所对应的流程示意图，图6b为本申请实施例三提供的数据传输过程示意图。
如图6a和图6b所示，包括：
步骤601，终端设备1获取第二数据包和第二数据包对应的eQI，并根据第二数据包对应的eQI确定第二数据包对应的QFI’。
步骤602，终端设备1根据第二数据包对应的QFI’，将第二数据包映射到DRB，并发送给网络设备1。
示例性地，终端设备1可以采用实施例一中所描述的实现方式2将第二数据包发送给网络设备1。
步骤603，网络设备1获取第二数据包和第二数据包对应的QFI’，并向UPF实体1发送GTP U数据包1。
此处，GTP U数据包1可以包括第二数据包和指示信息2，指示信息2用于指示第二数据包对应的QFI’。示例性地，指示信息2可以包括第二数据包对应的QFI’，或者第二数 据包对应的QFI’的索引，又或者其它用于指示第二数据包对应的QFI’的信息，具体不做限定。示例性地，指示信息2可以携带在GTP U头中。
网络设备1获取第二数据包对应的QFI’的方式可以有多种，比如可以参照现有技术中网络设备获取数据包对应的QFI的方式来实现，此处不再赘述。
步骤604，UPF实体1获取第二数据包和第二数据包对应的QFI’，并通过IMS网络或者视频服务器将第二数据包和第二数据包对应的QFI’传输给UPF实体2。
步骤605，UPF实体2获取第二数据包和第二数据包对应的QFI’，并向网络设备2发送GTP U数据包2。
此处，GTP U数据包2可以包括第二数据包和指示信息2。
步骤606，网络设备2获取第二数据包和第二数据包对应的QFI’，并根据第二数据包对应的QFI’将第二数据包发送给终端设备2。
此处，网络设备2可以采用实施例一中所描述的实现方式2将第二数据包传输给终端设备2。应理解，由于网络设备不具有应用层和非接入层，因此当采用实现方式2时，网络设备2从GTP-U数据包中获取到第二数据包和第二数据包对应的QFI’后，可将第二数据包和第二数据包对应的QFI’递交给SDAP层实体来执行相应操作。比如SDAP层实体可以根据第二数据包对应的QFI’将第二数据包映射到QFI’对应的DRB中。
采用上述方法，通过对现有QFI改进为QFI’，从而实现了对数据包的QoS进行细化，并通过QFI’对数据包进行端到端的区分处理。
上述主要从设备交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，为了实现上述功能，网络设备或终端设备可以包括执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请的实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对终端设备和网络设备进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
在采用集成的单元的情况下，图7示出了本申请实施例中所涉及的装置的可能的示例性框图。如图7所示，装置700可以包括：处理单元702和通信单元703。处理单元702用于对装置700的动作进行控制管理。通信单元703用于支持装置700与其他设备的通信。可选地，通信单元703也称为收发单元，可以包括接收单元和/或发送单元，分别用于执行接收和发送操作。装置700还可以包括存储单元701，用于存储装置700的程序代码和/或数据。
在一个实施例中，该装置700可以为上述任一实施例中的终端设备(或设置在终端设备中的芯片)，比如实施例一中的第一终端设备、实施例二中的终端设备1或者实施例三中的终端设备1；其中，处理单元702可以支持装置700执行上文中各方法示例中终端设备的动作；或者，处理单元702主要执行方法示例中的终端设备的内部动作，通信单元703可以支持装置700与其它设备(比如网络设备)之间的通信。或者，该装置700可以为上 述任一实施例中的网络设备(或设置在网络设备中的芯片)，比如实施例二中的网络设备2或者实施例三中的网络设备2；其中，处理单元702可以支持装置700执行上文中各方法示例中网络设备的动作；或者，处理单元702主要执行方法示例中的网络设备的内部动作，通信单元703可以支持装置700与其它设备(比如终端设备)之间的通信。
示例性地，在该实施例中，通信单元703用于：获取数据包和数据包对应的第一QoS参数和第二QoS参数；处理单元702用于：根据第一QoS参数和第二QoS参数，将数据包映射到DRB或RLC层实体，并通过通信单元703发送给第二通信装置。
在一种可能的设计中，第一QoS参数或者用于指示第一QoS参数的信息携带在数据包中。
在一种可能的设计中，装置700为终端设备，第一QoS参数是由装置700的应用层为数据包分配的。
在一种可能的设计中，装置700为网络设备；通信单元703具体用于：接收来自核心网设备的GTP-U数据包，GTP-U数据包中包括数据包和指示信息，指示信息用于指示第一QoS参数。
在一种可能的设计中，通信单元703还用于：获取所述第一QoS参数、所述第二QoS参数和DRB的对应关系；处理单元702具体用于：根据所述对应关系，将数据包映射到所述第一QoS参数、所述第二QoS参数对应的DRB。
在一种可能的设计中，装置700为终端设备，通信单元703具体用于：从网络设备获取所述对应关系，所述对应关系携带在RRC信令中。
在一种可能的设计中，装置700为终端设备，处理单元702还用于：若确定没有所述对应关系，则将数据包映射到默认DRB。
在一种可能的设计中，所述默认DRB为网络设备配置的，或者为第二QoS参数关联的DRB中DRB ID最小或最大的DRB。
在一种可能的设计中，装置700为终端设备，处理单元702还用于：若确定没有所述对应关系，则通过通信单元703向网络设备发送第一请求消息，所述第一请求消息包括所述第一QoS参数和所述第二QoS参数。
在一种可能的设计中，通信单元703还用于：接收来自网络设备的第一响应消息，所述第一响应消息用于指示所述第一QoS参数、所述第二QoS参数对应的DRB；处理单元702还用于：根据所示第一响应消息，将数据包映射到所述第一QoS参数、所述第二QoS参数对应的DRB。
在一种可能的设计中，所述第一QoS参数或者用于指示所述第一QoS参数的信息携带在数据包的SDAP头或PDCP头中。
在一种可能的设计中，处理单元702具体用于：根据所述第一QoS参数，确定数据包对应的所述第二QoS参数；以及，根据所述第二QoS参数和DRB的对应关系，将数据包映射到所述第二QoS参数对应的DRB。
在一种可能的设计中，通信单元703还用于：从核心网设备获取所述第一QoS参数和所述第二QoS参数的对应关系。
在一种可能的设计中，处理单元702具体用于：根据所述第二QoS参数，将数据包映射到所述第二QoS参数对应的DRB，所述DRB对应的分组数据汇聚协议PDCP层实体关联至少一个RLC层实体；以及通过通信单元703获取所述第一QoS参数和RLC层实体的 对应关系，进而根据所述对应关系，将数据包映射到所述至少一个RLC层实体中的第一QoS参数对应的RLC层实体。
在一种可能的设计中，装置700为终端设备，通信单元703还用于：从网络设备获取所述对应关系，所述对应关系携带在RRC信令中。
在一种可能的设计中，装置700为终端设备，处理单元702还用于：若确定没有所述对应关系，则将数据包映射到默认RLC层实体。
在一种可能的设计中，所述默认RLC层实体为网络设备配置的，或者为所述至少一个RLC层实体中对应的逻辑信道LCH ID最小或最大的RLC层实体。
在一种可能的设计中，装置700为终端设备，处理单元702还用于：若确定没有所述对应关系，则通过通信单元703向网络设备发送第二请求消息，所述第二请求消息包括所述第一QoS参数。
在一种可能的设计中，通信单元703还用于：接收来自网络设备的第二响应消息，所述第二响应消息用于指示所述第一QoS参数对应的RLC层实体；处理单元702还用于：根据所示第二响应消息，将数据包映射到所述第一QoS参数对应的RLC层实体。
在一种可能的设计中，所述PDCP层实体被配置有多组参数，所述第一QoS参数对应所述多组参数中的一组参数；处理单元702还用于：根据所述第一QoS参数对应的参数，对数据包进行处理。
在一种可能的设计中，所述PDCP层实体关联多个RLC层实体，所述第一QoS参数对应所述多个RLC层实体中的至少两个RLC层实体；所述至少两个RLC层实体被配置为实现复制传输功能；通信单元703还用于：接收来自所述第二通信装置的指示信息，所述指示信息用于指示所述第一QoS参数对应的所述至少两个RLC层实体中用于执行复制传输功能的RLC层实体；处理单元702还用于：将数据包映射到所述用于执行复制传输功能的RLC层实体。
在一种可能的设计中，所述第一QoS参数或者用于指示所述第一QoS参数的信息携带在数据包的SDAP头或PDCP头或RLC头。
在又一个实施例中，该装置700可以为上述任一实施例中的网络设备(或设置在网络设备中的芯片)，比如实施例二中的网络设备1或者实施例三中的网络设备1；其中，处理单元702可以支持装置700执行上文中各方法示例中网络设备的动作；或者，处理单元702主要执行方法示例中的网络设备的内部动作，通信单元703可以支持装置700与其它设备(比如核心网设备)之间的通信。
示例性地，在该实施例中，通信单元703用于：获取数据包、数据包对应的第一QoS参数和第二QoS参数；以及，向核心网设备发送GTP-U数据包，所述GTP-U数据包中包括所述数据包和指示信息，所述指示信息用于指示所述第一QoS参数和所述第二QoS参数。
在一种可能的设计中，通信单元703具体用于：接收来自终端设备的所述数据包，所述数据包承载于第一DRB或者第一RLC层实体上，以及处理单元702用于：根据所述第一DRB或者所述第一RLC层实体，得到所述第一QoS参数；或者，通信单元703接收来自所述终端设备的所述数据包，所述数据包中携带所述第一QoS参数或者用于指示所述第一QoS参数的信息。
在一种可能的设计中，所述数据包中携带所述第一QoS参数或者用于指示所述第一 QoS参数的信息，包括：所述数据包的SDAP头或PDCP头或RLC头中携带所述第一QoS参数或者用于指示所述第一QoS参数的信息。
在一种可能的设计中，所述指示信息携带在所述GTP-U数据包的GTP-U头中。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是处理器，比如通用中央处理器(central processing unit，CPU)，或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上用于接收的单元是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路。以上用于发送的单元是一种该装置的接口电路，用于向其它装置发送信号。例如，当该装置以芯片的方式实现时，该发送单元是该芯片用于向其它芯片或装置发送信号的接口电路。
请参考图8，其为本申请实施例提供的一种终端设备的结构示意图。其可以为以上实施例中的终端设备，用于实现以上实施例中终端设备的操作。如图8所示，该终端设备包括：天线810、射频部分820、信号处理部分830。天线810与射频部分820连接。在下行方向上，射频部分820通过天线810接收网络设备发送的信息，将网络设备发送的信息发送给信号处理部分830进行处理。在上行方向上，信号处理部分830对终端设备的信息进行处理，并发送给射频部分820，射频部分820对终端设备的信息进行处理后经过天线810发送给网络设备。
信号处理部分830可以包括调制解调子系统，用于实现对数据各通信协议层的处理；还可以包括中央处理子系统，用于实现对终端设备操作系统以及应用层的处理；此外，还可以包括其它子系统，例如多媒体子系统，周边子系统等，其中多媒体子系统用于实现对终端设备相机，屏幕显示等的控制，周边子系统用于实现与其它设备的连接。调制解调子系统可以为单独设置的芯片。
调制解调子系统可以包括一个或多个处理元件831，例如，包括一个主控CPU和其它集成电路。此外，该调制解调子系统还可以包括存储元件832和接口电路833。存储元件832用于存储数据和程序，但用于执行以上方法中终端设备所执行的方法的程序可能不存 储于该存储元件832中，而是存储于调制解调子系统之外的存储器中，使用时调制解调子系统加载使用。接口电路833用于与其它子系统通信。
该调制解调子系统可以通过芯片实现，该芯片包括至少一个处理元件和接口电路，其中处理元件用于执行以上终端设备执行的任一种方法的各个步骤，接口电路用于与其它装置通信。在一种实现中，终端设备实现以上方法中各个步骤的单元可以通过处理元件调度程序的形式实现，例如用于终端设备的装置包括处理元件和存储元件，处理元件调用存储元件存储的程序，以执行以上方法实施例中终端设备执行的方法。存储元件可以为处理元件处于同一芯片上的存储元件，即片内存储元件。
在另一种实现中，用于执行以上方法中终端设备所执行的方法的程序可以在与处理元件处于不同芯片上的存储元件，即片外存储元件。此时，处理元件从片外存储元件调用或加载程序于片内存储元件上，以调用并执行以上方法实施例中终端设备执行的方法。
在又一种实现中，终端设备实现以上方法中各个步骤的单元可以是被配置成一个或多个处理元件，这些处理元件设置于调制解调子系统上，这里的处理元件可以为集成电路，例如：一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA，或者这些类集成电路的组合。这些集成电路可以集成在一起，构成芯片。
终端设备实现以上方法中各个步骤的单元可以集成在一起，以SOC的形式实现，该SOC芯片，用于实现以上方法。该芯片内可以集成至少一个处理元件和存储元件，由处理元件调用存储元件的存储的程序的形式实现以上终端设备执行的方法；或者，该芯片内可以集成至少一个集成电路，用于实现以上终端设备执行的方法；或者，可以结合以上实现方式，部分单元的功能通过处理元件调用程序的形式实现，部分单元的功能通过集成电路的形式实现。
可见，以上用于终端设备的装置可以包括至少一个处理元件和接口电路，其中至少一个处理元件用于执行以上方法实施例所提供的任一种终端设备执行的方法。处理元件可以以第一种方式：即调用存储元件存储的程序的方式执行终端设备执行的部分或全部步骤；也可以以第二种方式：即通过处理器元件中的硬件的集成逻辑电路结合指令的方式执行终端设备执行的部分或全部步骤；当然，也可以结合第一种方式和第二种方式执行终端设备执行的部分或全部步骤。
这里的处理元件同以上描述，可以通过处理器实现，处理元件的功能可以和图7中所描述的处理单元的功能相同。示例性地，处理元件可以是通用处理器，例如CPU，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。存储元件可以通过存储器实现，存储元件的功能可以和图7中所描述的存储单元的功能相同。存储元件可以是一个存储器，也可以是多个存储器的统称。
图8所示的终端设备能够实现图3、图5a或图6a所示意的方法实施例中涉及终端设备的各个过程。图8所示的终端设备中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述描述。
请参考图9，其为本申请实施例提供的一种网络设备的结构示意图。用于实现以上实施例中网络设备的操作。如图9所示，该网络设备包括：天线901、射频装置902、基带 装置903。天线901与射频装置902连接。在上行方向上，射频装置902通过天线901接收终端设备发送的信息，将终端设备发送的信息发送给基带装置903进行处理。在下行方向上，基带装置903对终端设备的信息进行处理，并发送给射频装置902，射频装置902对终端设备的信息进行处理后经过天线901发送给终端设备。
基带装置903可以包括一个或多个处理元件9031，例如，包括一个主控CPU和其它集成电路。此外，该基带装置903还可以包括存储元件9032和接口9033，存储元件9032用于存储程序和数据；接口9033用于与射频装置902交互信息，该接口例如为通用公共无线接口(common public radio interface，CPRI)。以上用于网络设备的装置可以位于基带装置903，例如，以上用于网络设备的装置可以为基带装置903上的芯片，该芯片包括至少一个处理元件和接口电路，其中处理元件用于执行以上网络设备执行的任一种方法的各个步骤，接口电路用于与其它装置通信。在一种实现中，网络设备实现以上方法中各个步骤的单元可以通过处理元件调度程序的形式实现，例如用于网络设备的装置包括处理元件和存储元件，处理元件调用存储元件存储的程序，以执行以上方法实施例中网络设备执行的方法。存储元件可以为处理元件处于同一芯片上的存储元件，即片内存储元件，也可以为与处理元件处于不同芯片上的存储元件，即片外存储元件。
在另一种实现中，网络设备实现以上方法中各个步骤的单元可以是被配置成一个或多个处理元件，这些处理元件设置于基带装置上，这里的处理元件可以为集成电路，例如：一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA，或者这些类集成电路的组合。这些集成电路可以集成在一起，构成芯片。
网络设备实现以上方法中各个步骤的单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现，例如，基带装置包括该SOC芯片，用于实现以上方法。该芯片内可以集成至少一个处理元件和存储元件，由处理元件调用存储元件的存储的程序的形式实现以上网络设备执行的方法；或者，该芯片内可以集成至少一个集成电路，用于实现以上网络设备执行的方法；或者，可以结合以上实现方式，部分单元的功能通过处理元件调用程序的形式实现，部分单元的功能通过集成电路的形式实现。
可见，以上用于网络设备的装置可以包括至少一个处理元件和接口电路，其中至少一个处理元件用于执行以上方法实施例所提供的任一种网络设备执行的方法。处理元件可以以第一种方式：即调用存储元件存储的程序的方式执行网络设备执行的部分或全部步骤；也可以以第二种方式：即通过处理器元件中的硬件的集成逻辑电路结合指令的方式执行网络设备执行的部分或全部步骤；当然，也可以结合第一种方式和第二种方式执行以上网络设备执行的部分或全部步骤。
这里的处理元件同以上描述，可以通过处理器实现，处理元件的功能可以和图7中所描述的处理单元的功能相同。示例性地，处理元件可以是通用处理器，例如CPU，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。存储元件可以通过存储器实现，存储元件的功能可以和图7中所描述的存储单元的功能相同。存储元件可以是一个存储器，也可以是多个存储器的统称。
图9所示的网络设备能够实现图5a或图6a所示意的方法实施例中涉及网络设备的各个过程。图9所示的网络设备中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述 描述。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (33)

  1. 一种数据传输方法，其特征在于，所示方法包括：
    第一通信装置获取数据包和所述数据包对应的第一服务质量QoS参数和第二QoS参数；
    所述第一通信装置根据所述第一QoS参数和所述第二QoS参数，将所述数据包映射到数据无线承载DRB或无线链路控制RLC层实体，并发送给第二通信装置。
  2. 根据权利要求1所述的方法，其特征在于，所述第一QoS参数或者用于指示所述第一QoS参数的信息携带在所述数据包中。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一通信装置为终端设备，所述第一QoS参数是由所述第一通信装置的应用层为所述数据包分配的。
  4. 根据权利要求1或2所述的方法，其特征在于，所述第一通信装置为网络设备；
    第一通信装置获取数据包和所述数据包对应的第一QoS参数，包括：
    所述第一通信装置接收来自核心网设备的GTP-U数据包，所述GTP-U数据包中包括所述数据包和指示信息，所示指示信息用于指示所述第一QoS参数。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一通信装置根据所述第一QoS参数和所述第二QoS参数，将所述数据包映射到DRB，包括：
    所述第一通信装置获取所述第一QoS参数、所述第二QoS参数和DRB的对应关系；
    所述第一通信装置根据所述对应关系，将所述数据包映射到所述第一QoS参数、所述第二QoS参数对应的DRB。
  6. 根据权利要求5所述的方法，其特征在于，所述第一通信装置为终端设备，所述第一通信装置获取所述对应关系，包括：
    所述第一通信装置从网络设备获取所述对应关系，所述对应关系携带在RRC信令中。
  7. 根据权利要求5所述的方法，其特征在于，所述第一通信装置为终端设备，所述方法还包括：
    所述第一通信装置若确定没有所述对应关系，则将所述数据包映射到默认DRB。
  8. 根据权利要求7所述的方法，其特征在于，所述默认DRB为网络设备配置的，或者为第二QoS参数关联的DRB中DRB ID最小或最大的DRB。
  9. 根据权利要求5至8中任一项所述的方法，其特征在于，所述第一通信装置为终端设备，所述方法还包括：
    所述第一通信装置若确定没有所述对应关系，则向网络设备发送第一请求消息，所述第一请求消息包括所述第一QoS参数和所述第二QoS参数。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：所述第一通信装置接收来自网络设备的第一响应消息，所述第一响应消息用于指示所述第一QoS参数、所述第二QoS参数对应的DRB；
    所述第一通信装置根据所述第一QoS参数和所述第二QoS参数，将所述数据包映射到DRB，包括：所述第一通信装置根据所示第一响应消息，将所述数据包映射到所述第一QoS参数、所述第二QoS参数对应的DRB。
  11. 根据权利要求5至10中任一项所述的方法，其特征在于，所述第一QoS参数或者用于指示所述第一QoS参数的信息携带在所述数据包的SDAP头或PDCP头中。
  12. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一通信装置根据所述第一QoS参数和所述第二QoS参数，将所述数据包映射到DRB，包括：
    所述第一通信装置根据所述第一QoS参数，确定所述数据包对应的所述第二QoS参数；
    所述第一通信装置根据所述第二QoS参数和DRB的对应关系，将所述数据包映射到所述第二QoS参数对应的DRB。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述第一通信装置从核心网设备获取所述第一QoS参数和所述第二QoS参数的对应关系。
  14. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一通信装置根据所述第一QoS参数和所述第二QoS参数，将所述数据包映射到RLC层实体，包括：
    所述第一通信装置根据所述第二QoS参数，将所述数据包映射到所述第二QoS参数对应的DRB，所述DRB对应的分组数据汇聚协议PDCP层实体关联至少一个RLC层实体；
    所述第一通信装置获取所述第一QoS参数和RLC层实体的对应关系，并根据所述对应关系，将所述数据包映射到所述至少一个RLC层实体中的第一QoS参数对应的RLC层实体。
  15. 根据权利要求14所述的方法，其特征在于，所述第一通信装置为终端设备，所述第一通信装置获取所述第一QoS参数和RLC层实体的对应关系，包括：
    所述第一通信装置从网络设备获取所述对应关系，所述对应关系携带在RRC信令中。
  16. 根据权利要求15所述的方法，其特征在于，所述第一通信装置为终端设备，所述方法还包括：
    所述第一通信装置若确定没有所述对应关系，则将所述数据包映射到默认RLC层实体。
  17. 根据权利要求16所述的方法，其特征在于，所述默认RLC层实体为网络设备配置的，或者为所述至少一个RLC层实体中对应的逻辑信道LCH ID最小或最大的RLC层实体。
  18. 根据权利要求14至17中任一项所述的方法，其特征在于，所述第一通信装置为终端设备，所述方法还包括：
    所述第一通信装置若确定没有所述对应关系，则向网络设备发送第二请求消息，所述第二请求消息包括所述第一QoS参数。
  19. 根据权利要求18所述的方法，其特征在于，所述方法还包括：所述第一通信装置接收来自网络设备的第二响应消息，所述第二响应消息用于指示所述第一QoS参数对应的RLC层实体；
    所述第一通信装置根据所示第二响应消息，将所述数据包映射到所述第一QoS参数对应的RLC层实体。
  20. 根据权利要求14至19中任一项所述的方法，其特征在于，所述PDCP层实体被配置有多组参数，所述第一QoS参数对应所述多组参数中的一组参数；
    所述方法还包括：所述第一通信装置根据所述第一QoS参数对应的参数，对所述数据包进行处理。
  21. 根据权利要求14至20中任一项所述的方法，其特征在于，所述PDCP层实体关联多个RLC层实体，所述第一QoS参数对应所述多个RLC层实体中的至少两个RLC层 实体；所述至少两个RLC层实体被配置为实现复制传输功能；
    所述第一通信装置的PDCP层实体根据所述第一QoS参数，将所述数据包映射到对应的RLC层实体，包括：
    所述第一通信装置接收来自所述第二通信装置的指示信息，所述指示信息用于指示所述第一QoS参数对应的所述至少两个RLC层实体中用于执行复制传输功能的RLC层实体；
    所述第一通信装置将所述数据包映射到所述用于执行复制传输功能的RLC层实体。
  22. 根据权利要求14至21中任一项所述的方法，其特征在于，所述第一QoS参数或者用于指示所述第一QoS参数的信息携带在所述数据包的SDAP头或PDCP头或RLC头。
  23. 一种数据传输方法，其特征在于，所述方法包括：
    获取数据包、所述数据包对应的第一QoS参数和第二QoS参数；
    向核心网设备发送GTP-U数据包，所述GTP-U数据包中包括所述数据包和指示信息，所述指示信息用于指示所述第一QoS参数和所述第二QoS参数。
  24. 根据权利要求23所述的方法，其特征在于，获取所述数据包对应的第一QoS参数，包括：
    接收来自终端设备的所述数据包，所述数据包承载于第一DRB或者第一RLC层实体上，以及所述根据所述第一DRB或者所述第一RLC层实体，得到所述第一QoS参数；或者，
    接收来自所述终端设备的所述数据包，所述数据包中携带所述第一QoS参数或者用于指示所述第一QoS参数的信息。
  25. 根据权利要求24所述的方法，其特征在于，所述数据包中携带所述第一QoS参数或者用于指示所述第一QoS参数的信息，包括：所述数据包的SDAP头或PDCP头或RLC头中携带所述第一QoS参数或者用于指示所述第一QoS参数的信息。
  26. 根据权利要求23至25中任一项所述的方法，其特征在于，所述指示信息携带在所述GTP-U数据包的GTP-U头中。
  27. 一种通信系统，其特征在于，所述通信系统包括：网络设备和核心网设备；
    所述网络设备，用于获取数据包、所述数据包对应的第一QoS参数和第二QoS参数；以及，向核心网设备发送GTP-U数据包，所述GTP-U数据包中包括所述数据包和指示信息，所述指示信息用于指示所述第一QoS参数和所述第二QoS参数；
    所述核心网设备，用于接收所述GTP-U数据包。
  28. 根据权利要求27所述的通信系统，其特征在于，所述通信系统还包括终端设备；
    所述终端设备，用于向所述网络设备发送所述数据包；其中，所述数据包承载于第一DRB或者第一RLC层实体上，所述第一DRB或者所述第一RLC层实体对应所述第一QoS参数；或者，所述数据包中携带所述第一QoS参数或者用于指示所述第一QoS参数的信息。
  29. 根据权利要求27或28所述的通信系统，其特征在于，所述核心网设备，还用于发送网络协议IP数据包，所述IP数据包包括所述数据包和所述指示信息。
  30. 一种装置，其特征在于，包括用于执行如权利要求1至26中任一项所述的方法的各步骤的单元。
  31. 一种装置，其特征在于，包括至少一个处理器和接口电路，其中，所述至少一个处理器用于通过所述接口电路与其它装置通信，并执行如权利要求1至26中任一项所述 的方法。
  32. 一种装置，其特征在于，包括处理器，用于调用存储器中存储的程序，以执行如权利要求1至26中任一项所述的方法。
  33. 一种计算机可读存储介质，其特征在于，包括程序，当所述程序被处理器运行时，如权利要求1至26中任一项所述的方法被执行。
PCT/CN2019/124396 2019-12-10 2019-12-10 一种数据传输方法及装置 WO2021114107A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP19955950.1A EP4061051A4 (en) 2019-12-10 2019-12-10 DATA TRANSMISSION METHOD AND DEVICE
CN201980102812.8A CN114762386A (zh) 2019-12-10 2019-12-10 一种数据传输方法及装置
PCT/CN2019/124396 WO2021114107A1 (zh) 2019-12-10 2019-12-10 一种数据传输方法及装置
US17/836,001 US20220303825A1 (en) 2019-12-10 2022-06-09 Data transmission method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/124396 WO2021114107A1 (zh) 2019-12-10 2019-12-10 一种数据传输方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/836,001 Continuation US20220303825A1 (en) 2019-12-10 2022-06-09 Data transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2021114107A1 true WO2021114107A1 (zh) 2021-06-17

Family

ID=76329149

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/124396 WO2021114107A1 (zh) 2019-12-10 2019-12-10 一种数据传输方法及装置

Country Status (4)

Country Link
US (1) US20220303825A1 (zh)
EP (1) EP4061051A4 (zh)
CN (1) CN114762386A (zh)
WO (1) WO2021114107A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023024684A1 (zh) * 2021-08-26 2023-03-02 华为技术有限公司 数据传输的方法和装置
WO2024007875A1 (zh) * 2022-07-06 2024-01-11 华为技术有限公司 数据量指示方法、数据递交方法及装置
WO2024011423A1 (zh) * 2022-07-12 2024-01-18 Oppo广东移动通信有限公司 数据处理方法、装置、设备、存储介质及程序产品

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117835316A (zh) * 2022-09-29 2024-04-05 维沃移动通信有限公司 信息处理方法及通信设备
WO2024124020A1 (en) * 2022-12-07 2024-06-13 Interdigital Patent Holdings, Inc. Uplink transmissions using pdu set-based priority within a qos flow

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080107119A1 (en) * 2006-11-08 2008-05-08 Industrial Technology Research Institute Method and system for guaranteeing QoS between different radio networks
CN107637123A (zh) * 2017-04-27 2018-01-26 北京小米移动软件有限公司 信息传递方法、装置及计算机可读存储介质
CN109302751A (zh) * 2017-07-24 2019-02-01 华硕电脑股份有限公司 无线通信系统中服务服务质量流的方法和设备
CN109392004A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 通信方法、基站、终端设备和系统
CN109600664A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 业务传输方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102499481B1 (ko) * 2016-08-01 2023-02-14 삼성전자 주식회사 무선 통신 네트워크에서 데이터 통신을 관리하는 방법 및 장치
US20180324631A1 (en) * 2017-05-05 2018-11-08 Mediatek Inc. Using sdap headers for handling of as/nas reflective qos and to ensure in-sequence packet delivery during remapping in 5g communication systems
CN118301679A (zh) * 2017-06-16 2024-07-05 华为技术有限公司 一种通信方法及接入网设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080107119A1 (en) * 2006-11-08 2008-05-08 Industrial Technology Research Institute Method and system for guaranteeing QoS between different radio networks
CN107637123A (zh) * 2017-04-27 2018-01-26 北京小米移动软件有限公司 信息传递方法、装置及计算机可读存储介质
CN109302751A (zh) * 2017-07-24 2019-02-01 华硕电脑股份有限公司 无线通信系统中服务服务质量流的方法和设备
CN109392004A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 通信方法、基站、终端设备和系统
CN109600664A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 业务传输方法和装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "SDAP header format", 3GPP DRAFT; R2-1800176, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Vancouver, Canada; 20180122 - 20180126, 12 January 2018 (2018-01-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051386060 *
SHARP: "Alignment with QoS section in TS 23.501", 3GPP DRAFT; R2-1801505_REVISED-R2-1713863_ALIGN_WITH_23501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Vancouver, Canada; 20180122 - 20180126, 12 January 2018 (2018-01-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051386901 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023024684A1 (zh) * 2021-08-26 2023-03-02 华为技术有限公司 数据传输的方法和装置
WO2024007875A1 (zh) * 2022-07-06 2024-01-11 华为技术有限公司 数据量指示方法、数据递交方法及装置
WO2024011423A1 (zh) * 2022-07-12 2024-01-18 Oppo广东移动通信有限公司 数据处理方法、装置、设备、存储介质及程序产品

Also Published As

Publication number Publication date
EP4061051A1 (en) 2022-09-21
EP4061051A4 (en) 2022-12-07
US20220303825A1 (en) 2022-09-22
CN114762386A (zh) 2022-07-15

Similar Documents

Publication Publication Date Title
US10721754B2 (en) Data transmission method and apparatus
US11510223B2 (en) Wireless data priority services
WO2021114107A1 (zh) 一种数据传输方法及装置
JP2022095657A (ja) ロングタームエボリューション通信システムのためのマルチテクノロジアグリゲーションアーキテクチャ
US9432873B2 (en) Differentiation of traffic flows for uplink transmission
CN112335304B (zh) 一种数据发送方法、装置和通信系统
WO2018059518A1 (zh) 一种数据传输方法、装置和系统
JP2013515420A (ja) リレーにおけるサービス品質の制御
US20230116578A1 (en) Data transmission method and apparatus
WO2021219098A1 (zh) 一种通信方法及装置
WO2018000220A1 (zh) 数据传输方法、数据传输装置及系统
WO2022148371A1 (zh) 传输报文的方法和装置
WO2022012361A1 (zh) 一种通信方法及装置
WO2022202835A1 (ja) 通信制御方法
WO2022147727A1 (zh) 一种通信方法及装置
WO2023050415A1 (zh) 一种多路径传输方法及装置、通信设备
JP7478749B2 (ja) 無線ベアラ確立方法及び装置
WO2022082798A1 (zh) 通信方法及装置
WO2022151107A1 (zh) 信号的发送和接收方法、装置和通信系统
WO2023185608A1 (zh) 一种数据传输的方法及通信装置
WO2022061757A1 (zh) 资源分配方法、装置和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19955950

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019955950

Country of ref document: EP

Effective date: 20220617

NENP Non-entry into the national phase

Ref country code: DE