WO2020063108A1 - 数据传输的方法和装置 - Google Patents

数据传输的方法和装置 Download PDF

Info

Publication number
WO2020063108A1
WO2020063108A1 PCT/CN2019/099054 CN2019099054W WO2020063108A1 WO 2020063108 A1 WO2020063108 A1 WO 2020063108A1 CN 2019099054 W CN2019099054 W CN 2019099054W WO 2020063108 A1 WO2020063108 A1 WO 2020063108A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos flow
drb
information
data
mapping relationship
Prior art date
Application number
PCT/CN2019/099054
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 EP19865768.6A priority Critical patent/EP3836612A4/en
Priority to CA3111098A priority patent/CA3111098A1/en
Priority to JP2021517258A priority patent/JP7177259B2/ja
Publication of WO2020063108A1 publication Critical patent/WO2020063108A1/zh
Priority to US17/211,101 priority patent/US11968558B2/en
Priority to JP2022180054A priority patent/JP2023025025A/ja

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/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]
    • 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
    • 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/0257—Traffic management, e.g. flow control or congestion control per individual bearer or channel the individual bearer or channel having a maximum bit rate or a bit rate guarantee
    • 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/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present application relates to the field of communications, and more specifically, to a method and apparatus for data transmission in the field of communications.
  • 5G will support various types of network deployment and application types, including: higher-speed experience and greater bandwidth access capabilities, lower latency and highly reliable information interaction, larger-scale, low-cost MTC devices. Access and management.
  • an access network device may adopt a structure in which a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU) are separated.
  • CU-DU distributed unit-user Plane
  • CU-UP distributed unit-user Plane
  • the CU-CP part includes the radio resource control (RRC) function and the control plane part of the packet data convergence protocol (PDCP).
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the CU-UP part includes the data plane part of the CU, which mainly includes services.
  • Data adaptation protocol service data adaptation protocol, SDAP
  • SDAP data plane part of PDCP protocol stack.
  • This application provides a method and device for data transmission, which can implement data transmission based on quality of service QoS flows under separate CU-CP and CU-UP architectures.
  • a data transmission method includes:
  • the centralized unit-user plane CU-UP of the radio access network RAN receives quality of service QoS flow data
  • the CU-UP Sending, by the CU-UP, first information to the radio access network RAN centralized unit-control plane CU-CP, where the first information includes a QoS flow identification ID and a PDU session ID of the QoS flow data,
  • the PDU session corresponding to the PDU session ID includes the QoS flow data.
  • the CU-UP when the CU-UP receives the quality of service QoS flow data, it can send the QoS flow identification ID and PDU of the QoS flow data to the CU-CP. Session ID, where the PDU session corresponding to the PDU session ID includes the QoS flow data, so that the CU-CP can determine the mapping mode of the QoS flow data to the radio bearer, thereby satisfying the transmission performance parameters of the QoS flow and improving the user experience.
  • the QoS flow data corresponds to a first data radio bearer DRB, wherein the radio access network centralized unit-user plane CU-UP receives quality of service QoS Streaming data, including:
  • the method further includes: the CU-UP receives second information from the CU-CP, and the second information is used to indicate that the QoS flow data is from Corresponding to the first DRB becomes corresponding to the second DRB.
  • the subsequent CU-UP receives the QoS flow data from the terminal device from the second DRB, or when the CU-UP receives the QoS flow data from the core network, it maps the QoS flow data to the second DRB for transmission.
  • the second information may include a DRB ID of the second DRB and the QoS flow ID, and optionally may further include a QoS parameter of the QoS flow.
  • the first DRB is a default DRB
  • the second DRB is a proprietary DRB
  • the CU-UP When the first DRB is the default DRB, when the CU-UP receives a certain QoS flow data from the default DRB, the CU-UP notifies the CU-CP that the QoS flow data arrives, so that the CU-CP establishes a new proprietary for the QoS flow.
  • the DRB or mapping the QoS flow data to another existing proprietary DRB, implements the remapping process of the QoS flow from the default DRB to the proprietary DRB.
  • the first information further includes a DRB ID of the first DRB.
  • the first information may not include the DRB ID of the first DRB, that is, the CU-UP may not need to inform the CU-CP of the DRB ID of the first DRB, and only need to inform the above.
  • the list of QoS flow IDs in the PDU session is sufficient. At this time, extra signaling overhead can be saved.
  • the first information when the CU-UP receives the QoS flow data from a terminal device, the first information further includes an uplink indication; or when the CU-UP When receiving the QoS flow data from the core network, the first information further includes a downlink indication.
  • the uplink indication may be used to indicate that the transmission direction is uplink, or used to indicate that the QoS flow data is uplink QoS flow data.
  • the downlink indication may be used to indicate that the transmission direction is downlink, or to indicate that the QoS flow data is downlink QoS flow data.
  • the CU-UP can explicitly inform the CU-CP respectively that the QoS flow data is uplink data or downlink data.
  • the CU-UP only informs the CU-CP that QoS flow data has arrived, and does not tell the CU-CP that the QoS flow data is uplink QoS flow data or downlink QoS flow data, that is, at this time, the CU-CP and CU-UP does not need to distinguish whether the QoS flow data is uplink data or downlink data.
  • a data transmission method including:
  • the control plane CU-CP of the RAN centralized unit of the radio access network receives first information from the user plane CU-UP of the centralized unit of the radio access network, wherein the first information includes a QoS flow identifier ID and PDU of the QoS flow data.
  • the first information includes a QoS flow identifier ID and PDU of the QoS flow data.
  • a session ID where the PDU session corresponding to the PDU session ID includes the QoS flow data;
  • the CU-CP uses the first information.
  • the CU-UP when the CU-UP receives the quality of service QoS flow data, it can send the QoS flow identification ID and PDU of the QoS flow data to the CU-CP. Session ID, where the PDU session corresponding to the PDU session ID includes the QoS flow data, so that the CU-CP can determine the mapping mode of the QoS flow data to the radio bearer, thereby satisfying the transmission performance parameters of the QoS flow and improving the user experience.
  • the CU-CP obtains information included in the first information, and determines the arrival of QoS flow data according to the information included in the first information. Further, the CU-CP may determine to continue to maintain the mapping relationship between the QoS flow included in the first information and the first DRB, or change the first DRB corresponding to the QoS flow to the second DRB.
  • the CU-CP determines that the mapping relationship between the QoS flow included in the first information and the first DRB is maintained unchanged, other operations may not be performed.
  • the method when the CU-CP determines that the first DRB corresponding to the QoS flow becomes the second DRB, the method further includes: the CU-CP sends the CU-CP to the CU. -The UP sends second information, which is used to instruct the QoS flow data to change from corresponding to the first DRB to corresponding to the second DRB.
  • the DU can obtain the mapping relationship between the QoS flow and the second DRB, and is used for the DU to perform uplink and downlink scheduling of the second DRB on the user equipment.
  • the second information may include a DRB ID of the second DRB and the QoS flow ID, and optionally may further include a QoS parameter of the QoS flow.
  • the CU-CP may send an F1-C message to the DU.
  • the F1-C message encapsulates an RRC message sent to the terminal device, and the RRC message may include the second information.
  • the first DRB is a default DRB
  • the second DRB is a proprietary DRB
  • the CU-UP When the first DRB is the default DRB, when the CU-UP receives a certain QoS flow data from the default DRB, the CU-UP notifies the CU-CP that the QoS flow data arrives, so that the CU-CP establishes a new proprietary for the QoS flow.
  • the DRB or mapping the QoS flow data to another existing proprietary DRB, implements the remapping process of the QoS flow from the default DRB to the proprietary DRB.
  • the first information further includes a DRB ID of the first DRB.
  • the first information further includes an uplink indication, and the uplink indication is used for the QoS flow data to be uplink data;
  • the first information further includes a downlink indication, and the downlink indication is used for the QoS flow data to be downlink data.
  • a data transmission method which includes:
  • the centralized unit CU determines the mapping relationship between the quality of service QoS flow and the DRB.
  • the mapping relationship includes at least one of the following: the mapping relationship between the uplink QoS flow and the DRB, the mapping relationship between the downlink QoS flow and the DRB, or the mapping relationship between the bidirectional QoS flow and the DRB. ;
  • the CU sends third information to the distributed unit DU, where the third information includes a mapping relationship between the QoS flow and a DRB.
  • the CU decides the asymmetric QoS flow-to-DRB mapping relationship and notifies the DU of the asymmetric mapping relationship, which can implement flexible uplink QoS flow mapping and downlink QoS flow mapping and achieve uplink QoS. Decoupling the mapping relationship between flow and downlink QoS flow.
  • the requirements for the uplink transmission and the downlink transmission of the QoS flow can be separately guaranteed (the guaranteed bit rates and maximum bit rates of the uplink and downlink transmissions are different); on the other hand, the network can be based on the uplink / downlink network load and interference conditions. , QoS flow parameter characteristics, etc., flexible configuration of uplink and downlink mapping of QoS flow, further improving the user experience.
  • the CU includes separate centralized unit-user plane CU-UP and centralized unit-control plane CU-CP,
  • the determining, by the centralized unit CU, the mapping relationship between the quality of service QoS flow and the DRB includes: the CU-CP determining the mapping relationship between the QoS flow and the DRB;
  • the sending, by the CU, third information to the distributed unit DU includes: the CU-CP sending the third information to the DU.
  • the DU After receiving the third information, the DU records the mapping relationship indicated by the third information. For the QoS flow corresponding to the uplink QoS flow and / or the downlink QoS flow indicated by the third information, the media access control (MAC) layer and the radio link control (RLC) layer are determined respectively. Configuration parameters. In a possible implementation manner, the DU performs uplink and downlink scheduling respectively at the MAC layer according to the QoS flow in the DRB.
  • MAC media access control
  • RLC radio link control
  • the method further includes: the CU-CP sending the third information to the CU-UP.
  • the CU-UP After receiving the third information, the CU-UP records the mapping relationship indicated by the third information.
  • the CU-UP receives the downlink QoS flow data sent by the core network, it can map the downlink QoS flow data to the corresponding DRB and pass it to the DU according to the mapping relationship between the downlink QoS flow ID and the DRB indicated by the third information.
  • the CU-UP receives the uplink QoS flow data sent by the terminal device, it can verify whether the uplink QoS flow data is transmitted on the corresponding DRB according to the mapping relationship between the uplink QoS flow ID and the DRB indicated by the third information.
  • the sending, by the CU-CP, the third information to the CU-UP includes:
  • the sending, by the CU-CP, the third information to the DU includes:
  • the third information may further include a mapping indication, which is used to indicate that the data in the QoS flow mapped to the DRB is uplink data or downlink data ( indication, UL data, DL data, QoS, flow map, or DRB), or indicate that the data in the QoS flow mapped to the DRB is uplink data and downlink data.
  • a mapping indication which is used to indicate that the data in the QoS flow mapped to the DRB is uplink data or downlink data ( indication, UL data, DL data, QoS, flow map, or DRB), or indicate that the data in the QoS flow mapped to the DRB is uplink data and downlink data.
  • the third information may further include an asymmetric mapping indication, which is used to indicate that the data in the QoS flow mapped to the DRB is uplink data or downlink data (indication why the UL data, DL, data, QoS, flow, map, DRB).
  • an asymmetric mapping indication which is used to indicate that the data in the QoS flow mapped to the DRB is uplink data or downlink data (indication why the UL data, DL, data, QoS, flow, map, DRB).
  • the CU-CP can explicitly indicate that the QoS flow in the CU-UP mapping relationship is an uplink QoS flow, or a downlink QoS flow, or a bidirectional QoS flow.
  • the CU-CP may also implicitly indicate that the QoS flow in the CU-UP mapping relationship is an uplink QoS flow, or a downlink QoS flow, or a bidirectional QoS flow.
  • the CU-CP determines the asymmetric QoS flow-to-DRB mapping relationship, and the CU-UP notifies the CU-UP and the DU of the asymmetric mapping relationship, which can implement flexible uplink QoS flow mapping and downlink QoS flow mapping realizes the decoupling of the mapping relationship between uplink QoS flow and downlink QoS flow.
  • the requirements for the uplink transmission and the downlink transmission of the QoS flow can be separately guaranteed (the guaranteed bit rates and maximum bit rates of the uplink and downlink transmissions are different); on the other hand, the network can be based on the uplink / downlink network load and interference conditions , QoS flow parameter characteristics, etc., flexible configuration of uplink and downlink mapping of QoS flow, further improving the user experience.
  • a method for data transmission including:
  • a distributed unit DU in a radio access network receives third information from a centralized unit CU, where the third information includes a mapping relationship between a QoS flow and a DRB, wherein the mapping relationship includes at least one of the following: an uplink QoS flow and a DRB Mapping relationship between the downlink QoS flow and the DRB, or the mapping relationship between the bidirectional QoS flow and the DRB;
  • the DU uses the third information.
  • the CU decides the asymmetric QoS flow-to-DRB mapping relationship and notifies the DU of the asymmetric mapping relationship, which can implement flexible uplink QoS flow mapping and downlink QoS flow mapping and achieve uplink QoS. Decoupling the mapping relationship between flow and downlink QoS flow.
  • the requirements for the uplink transmission and the downlink transmission of the QoS flow can be separately guaranteed (the guaranteed bit rates and maximum bit rates of the uplink and downlink transmissions are different); on the other hand, the network can be based on the uplink / downlink network load and interference conditions. , QoS flow parameter characteristics, etc., flexible configuration of uplink and downlink mapping of QoS flow, further improving the user experience.
  • the CU includes separate centralized unit-user plane CU-UP and centralized unit-control plane CU-CP, wherein the radio access network
  • the distributed unit DU in the receiving the third information from the CU includes:
  • the DU After receiving the third information, the DU records the mapping relationship indicated by the third information. For the QoS flow corresponding to the uplink QoS flow and / or the downlink QoS flow indicated by the third information, the media access control (MAC) layer and the radio link control (RLC) layer are determined respectively. Configuration parameters. In a possible implementation manner, the DU performs uplink and downlink scheduling respectively at the MAC layer according to the QoS flow in the DRB.
  • MAC media access control
  • RLC radio link control
  • the receiving, by the DU, the third information from the CU-CP includes:
  • the third information when the mapping relationship includes a mapping relationship between an uplink QoS flow and a DRB, the third information further includes an uplink indication;
  • the third information further includes a downlink indication
  • the third information further includes a bidirectional indication.
  • a data transmission method including:
  • the core network CN determines the direction of the QoS flow.
  • the direction of the QoS flow includes only uplink QoS flows, only downlink QoS flows, or bidirectional QoS flows.
  • the core network sends fourth information to the RAN, where the fourth information is used to indicate a direction of the QoS flow.
  • the RAN may specifically be a CU-CP or a CU.
  • the fourth information includes: a PDU session ID, a QoS flow ID, and a directional characteristic of a QoS flow corresponding to the QoS flow ID.
  • the directional characteristic is, for example, uplink, downlink, or bidirectional.
  • the fourth information may further include an uplink QoS parameter of the QoS flow, where the uplink QoS parameter is a QoS parameter configured when the QoS flow is transmitted in uplink.
  • the fourth information may further include downlink QoS parameters of the QoS flow, wherein the downlink QoS parameters are QoS parameters configured when the QoS flow is transmitted in the downlink.
  • the fourth information may further include UL QoS parameters and DL QoS parameters of the QoS flow.
  • the access network device may determine the direction of the QoS flow, and may independently configure the uplink transmission and the downlink transmission of the QoS flow. Specifically, if the QoS flow is only an uplink QoS flow, the access network device determines an uplink data packet scheduling policy of the QoS flow without considering downlink transmission; if the QoS flow is only a downlink QoS flow, access The network device decides the scheduling strategy for the downlink data packets of the QoS flow without considering the uplink transmission. Therefore, the embodiments of the present application can meet specific requirements of QoS flows.
  • a data transmission method including:
  • the core network CN determines the direction of the QoS flow
  • the RAN receives fourth information from the core network, where the fourth information is used to indicate a direction of the QoS flow, and the direction of the QoS flow includes only an uplink QoS flow, only a downlink QoS flow, or a two-way QoS flow;
  • the RAN uses the fourth information. Specifically, the RAN acquires the information included in the fourth information, and determines the directional characteristic of the QoS flow according to the information included in the RAN. .
  • the RAN may specifically be a CU-CP or a CU.
  • the access network device may determine the direction of the QoS flow, and may independently configure the uplink transmission and the downlink transmission of the QoS flow. Specifically, if the QoS flow is only an uplink QoS flow, the access network device determines an uplink data packet scheduling policy of the QoS flow without considering downlink transmission; if the QoS flow is only a downlink QoS flow, access The network device decides the scheduling strategy for the downlink data packets of the QoS flow without considering the uplink transmission. Therefore, the embodiments of the present application can meet specific requirements of QoS flows.
  • an apparatus may be a radio access network device, a network element or module in a radio access network device, or a chip in a radio access network device. Chip inside a network or module.
  • the device has a function of implementing the foregoing first aspect to the sixth aspect and various possible implementation manners of any aspect. This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the device includes a transceiver module.
  • the device further includes a processing module.
  • the transceiver module may be at least one of a transceiver, a receiver, and a transmitter.
  • the transceiver module It may include a radio frequency circuit or an antenna.
  • the processing module may be a processor.
  • the apparatus further includes a storage module, which may be, for example, a memory. When a memory module is included, the memory module is used to store instructions.
  • the processing module is connected to the storage module, and the processing module may execute instructions stored in the storage module or derived from other instructions, so that the device executes the foregoing first aspect to the sixth aspect and various possible implementations of any aspect. Way of communication.
  • the device may be a radio access network device, or a module, network element, or function in a radio access network device.
  • the chip when the device is a chip, the chip includes a transceiver module.
  • the device further includes a processing module.
  • the transceiver module may be, for example, an input / output interface, a pin on the chip. Or circuit, etc.
  • the processing module may be, for example, a processor.
  • the processing module can execute instructions to cause a chip in the terminal to execute the foregoing first aspect to the sixth aspect and any possible implemented communication method.
  • the processing module may execute instructions in a storage module, and the storage module may be a storage module in a chip, such as a register, a cache, and the like.
  • the storage module can also be located inside the communication device, but outside the chip, such as read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM).
  • ROM read-only memory
  • RAM random access memory
  • the processor mentioned above may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the above.
  • a computer storage medium stores program code, where the program code is used to instruct execution of a method in any one of the foregoing first to sixth aspects or any possible implementation manner thereof. Instructions.
  • a computer program product containing instructions which when run on a computer, causes the computer to execute the method in any one of the first to sixth aspects described above or any possible implementation thereof.
  • a communication system includes a device and a combination thereof having methods and various possible designed functions for implementing any one of the first to sixth aspects.
  • a processor is provided, which is coupled to a memory, and is configured to execute the method in any one of the foregoing first to sixth aspects or any possible implementation manner thereof.
  • a chip is provided.
  • the chip includes a processor and a communication interface.
  • the communication interface is used to communicate with an external device or an internal device.
  • the processor is used to implement any one of the first to sixth aspects described above or Any of its possible implementations.
  • the chip may further include a memory, and the memory stores instructions, and the processor is configured to execute the instructions stored in the memory or originate from other instructions.
  • the processor is configured to implement the method in any possible implementation manner of any one of the first to sixth aspects.
  • the chip may be integrated on a network device.
  • FIG. 1 shows a schematic diagram of a radio access network to which an embodiment of the present application is applied.
  • FIG. 2 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 3 shows a schematic flowchart of a specific QoS flow data transmission method according to an embodiment of the present application.
  • FIG. 4 shows a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 5 shows a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 6 shows a schematic flowchart of a specific QoS stream data transmission method according to an embodiment of the present application.
  • FIG. 7 shows a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 8 shows a schematic block diagram of a communication device according to an embodiment of the present application.
  • FIG. 9 shows a schematic block diagram of another communication device according to an embodiment of the present application.
  • the technical solutions in the embodiments of the present application may be applied to a 5th generation (5G) mobile communication system or a future evolved mobile communication system.
  • 5G 5th generation
  • 5G future evolved mobile communication system
  • FIG. 1 shows a schematic diagram of a radio access network (RAN) 100 to which an embodiment of the present application is applied.
  • the radio access network may include various forms of base stations, macro base stations, micro base stations (also called small stations), relay stations, access points, and new wireless controllers (new controllers, NR controllers).
  • Centralized network unit centralized unit
  • radio remote module distributed network unit (distributed unit), transmission and reception point (TRP) or transmission point (transmission point, TP), or any other wireless access Equipment
  • TRP transmission and reception point
  • TP transmission point
  • the embodiment of the present application is not limited to this.
  • the names of devices with wireless access functions may be different.
  • the radio access network device may be a next generation base station (gNB) in a 5G mobile communication system or a base station in a future mobile communication system.
  • gNB next generation base station
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the wireless access network.
  • the wireless access network in the embodiment of the present application is used to provide a wireless communication function for a terminal device.
  • the terminal device may also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), or the like.
  • the terminal device may be a sensor mounted on a vehicle in a V2X communication system, a vehicle-mounted terminal, a wireless terminal in self-driving, a wireless terminal in transportation safety, and the like.
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.
  • the centralized unit CU can be further divided into a centralized unit-control plane CU-CP and one or more distributed units-user plane CU-UP .
  • the radio access network 100 includes one CU-CP, multiple CU-UPs, and multiple distributed unit DUs.
  • the CU-UP, CU-CP, and DU can be set on different physical devices, which is not limited in the embodiment of the present application.
  • CU-CP can be connected to one DU
  • one CU-CP can be connected to one CU-UP
  • one DU can be connected to multiple CU-UPs
  • one CU-UP is under the control of the same CU-CP.
  • Multiple DUs can be connected under the control of the same CU-CP.
  • CU-CP and CU-UP can communicate through this E1 interface.
  • CU-CP and CU-UP and DU will have their own interfaces.
  • the interface between CU-CP and DU is F1-C interface
  • the interface between CU-UP and DU is F1-U interface.
  • the CU-CP includes a control plane part of the CU, including an RRC function and a control plane part of the PDCP, for example, for processing data of a signaling radio bearer (SRB).
  • CU-UP includes the user plane part of the CU, including the SDAP protocol stack and the data plane part of the PDCP protocol stack, for example, the user processes data of a data radio bearer (DRB).
  • DRB data radio bearer
  • the DU includes an RLC layer, a MAC layer, and a PHY layer.
  • FIG. 2 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • the CU-UP in the CU-CP / CU-UP separation scenario, when the CU-UP receives the quality of service QoS flow data, it can send related information of the QoS flow data to the CU-CP to notify the QoS flow data that , So that the CU-CP can determine the mapping mode of the QoS flow data to the radio bearer.
  • the CU-CP and CU-UP in FIG. 2 reference may be made to the description in FIG. 1. To avoid repetition, details are not described herein again.
  • the method in FIG. 2 includes 210 and 220.
  • the CU-UP receives quality of service QoS flow data.
  • the CU-UP may receive the QoS flow data from the terminal device, and may also receive the QoS data from the core network.
  • the data transmission direction is the uplink direction.
  • the QoS flow data may be referred to as uplink QoS flow data.
  • the CU-UP receives the QoS flow data from the core network, the data transmission direction is the downlink direction.
  • the QoS flow data may be referred to as downlink QoS flow data.
  • the QoS flow data corresponds to the first DRB, that is, the QoS flow data is transmitted by the first DRB.
  • the CU-UP receives the quality of service QoS flow data.
  • the CU-UP receives the QoS flow data from the terminal device through the first DRB, or the CU-UP receives the QoS flow data from the terminal device.
  • the DRB transmits the QoS flow data from the terminal device.
  • the QoS flow data is data that has been sent to the CU-UP through the first DRB.
  • the CU-UP receives the quality of service QoS flow data, which may be replaced by the CU-CP receiving the QoS flow data from the core network that needs to be transmitted through the first DRB, or the CU-CP Receive the QoS flow data from the core network and pass the first DRB to the terminal device.
  • the QoS data is sent by the core network to the CU-UP, and the CU-UP will map the QoS flow data to the first DRB for transmission according to the mapping relationship between the QoS flow data and the first DRB.
  • the QoS flow data received here may include one QoS flow data or multiple QoS flow data, which is not limited in the embodiment of the present application.
  • the first DRB is a default DRB.
  • the network device will configure a default DRB. If the QoS flow packet is not explicitly configured by RRC to transmit the mapping relationship of the QoS flow to the DRB, the reflected QoS is not used to indicate the QoS flow to the DRB. Mapping relationship, the default DRB is used to transmit the data packet.
  • the CU-UP sends first information to the CU-CP, where the first information includes a QoS flow identifier ID and a PDU session ID of the QoS flow data, and a PDU session corresponding to the PDU session ID includes the QoS flow. data.
  • the number of QoS flow identification IDs may be one or more.
  • the CU-UP when the first DRB is the default DRB, the CU-UP receives the quality of service QoS flow data and sends the QoS flow ID and PDU session ID of the QoS flow data to the CU-CP, which can be understood as: when the CU -UP determines that the QoS flow data of the QoS flow data delivered via the default data radio bearer DRB arrives, and sends the QoS flow ID and PDU session ID of the QoS flow data to the CU-CP to inform the CU-CP of the quality of service QoS flow data The default DRB arrives.
  • the CU-UP when the first DRB is a proprietary DRB, the CU-UP receives the quality of service QoS flow data and sends the QoS flow ID and the PDU session ID of the QoS flow data to the CU-CP, which can be understood as:
  • the CU-UP determines that the quality of service QoS flow data delivered via the dedicated data radio bearer DRB arrives, it sends the QoS flow ID and PDU session ID of the QoS flow data to the CU-CP to notify the CU-CP of the quality of service QoS flow Data arrives via a proprietary DRB.
  • the first information may further include a DRB identification ID of the first DRB, that is, the CU-UP may notify the CU-CP of the DRB ID of the first DRB.
  • the first information may not include the DRB ID of the first DRB, that is, the CU-UP may not need to inform the CU-CP of the DRB ID of the first DRB, and only needs to inform the above-mentioned PDU session.
  • the QoS flow ID list is sufficient. At this time, extra signaling overhead can be saved.
  • the CU-CP when the CU-CP sends a bearer context setup request (bearer context setup request), it clearly indicates the QoS flow ID corresponding to the first DRB. Therefore, when the CU-CP notifies the CU-CP only of the PDU ID and the When the QoS flow ID is in the PDU session, the CU-CP can determine the DRB corresponding to the QoS flow, that is, the first DRB. In an optional embodiment, when the CU-CP determines that the QoS flow data is transmitted by the default DRB, it may determine that the first DRB is the default DRB.
  • the first information may include auxiliary information
  • the auxiliary information includes packet delivery performance statistics on the QoS flow or the first DRB.
  • the packet delivery performance statistics include, for example, a packet loss rate, a reordering waiting time, and a packet. At least one of the arrival rate and the like.
  • the first information when the CU-UP receives the QoS flow data from a terminal device, the first information further includes an uplink indication; or when the CU-UP receives the QoS flow data from a core network, all The first information further includes a downlink indication.
  • the uplink indication may be used to indicate that the transmission direction is uplink, or used to indicate that the QoS flow data is uplink QoS flow data.
  • the downlink indication may be used to indicate that the transmission direction is downlink, or to indicate that the QoS flow data is downlink QoS flow data.
  • the CU-UP can explicitly inform the CU-CP respectively that the QoS flow data is uplink data or downlink data.
  • the CU-UP only informs the CU-CP that QoS flow data has arrived, and does not tell the CU-CP that the QoS flow data is uplink QoS flow data or downlink QoS flow data, that is, at this time, the CU-CP and CU-UP does not need to distinguish whether the QoS flow data is uplink data or downlink data.
  • the CU-CP receives the first information.
  • the CU-CP uses the first information.
  • the CU-CP obtains information included in the first information, and determines the arrival of QoS flow data according to the information included in the first information. Further, the CU-CP may determine to keep the mapping relationship between the QoS flow included in the first information and the first DRB unchanged, or change the first DRB corresponding to the QoS flow to the second DRB.
  • the CU-CP may determine whether to change the DRB corresponding to the QoS flow according to the load situation of the current data transmission and the performance parameters of the QoS flow data. As an example, when the first DRB is the default DRB, the default DRB has the lowest priority. If the QoS flow data contains user data, it should have a higher priority. The CU-CP considers that the default DRB cannot meet the Requirements for performance parameters of QoS flows. At this time, the CU-CP may determine to change the default DRB corresponding to the QoS flow data to the second DRB.
  • the second DRB is a dedicated DRB, and its priority is higher than the default DRB.
  • the performance parameters of the QoS flow include: 5QI, priority level, packet delay budget, packet error rate, packet error rate, and whether the QoS flow is delay critical. Wait.
  • the CU-CP determines that the mapping relationship between the QoS flow included in the first information and the first DRB is maintained unchanged, other operations may not be performed.
  • the CU-CP may send second information to the CU-UP.
  • the second information is used for Instructs the QoS flow to change from corresponding to the first DRB to corresponding to the second DRB.
  • the CU-UP receives the second information, and determines that the QoS flow corresponds to the second DRB according to the second information. Specifically, when the subsequent CU-UP receives the QoS flow data from the terminal device from the second DRB, or when the CU-UP receives the QoS flow data from the core network, it maps the QoS flow data to the second DRB. transmission.
  • the second information may be sent to the DU so that the DU can obtain the QoS flow and the first DRB.
  • the mapping relationship between the two DRBs is used by the DU to perform second DRB uplink and downlink scheduling on the user equipment.
  • the second information may be sent to the terminal device, so that the terminal device can obtain the QoS flow.
  • the mapping relationship with the second DRB may further send the QoS flow data to the second DRB for transmission, or receive the QoS flow data from the second DRB.
  • the CU-CP may send an F1-C message to the DU.
  • the F1-C message encapsulates an RRC message sent to the terminal device, and the RRC message may include the second information.
  • the terminal device when the terminal device receives the downlink QoS data stream from the second DRB, the terminal device may send the uplink QoS stream data to the second DRB for transmission according to the reflected QoS mode.
  • the second information may include a DRB ID of the second DRB and the QoS flow ID, and optionally, may further include QoS parameters of the QoS flow.
  • the QoS parameters are, for example, 5QI, priority level, packet delay budget, packet error rate, whether the QoS flow is delay critical, etc.
  • the first DRB is a default DRB
  • the second DRB is a dedicated DRB.
  • the second DRB is an existing dedicated DRB or a newly-built dedicated DRB.
  • the CU-CP may establish a dedicated DRB through a signaling process of sending a UE context modification message to the CU-UP, the DU, and the UE.
  • a process of establishing the proprietary DRB refer to the prior art, which will not be described here.
  • the first DRB is a dedicated DRB
  • the second DRB is another dedicated DRB.
  • the second DRB is an existing dedicated DRB or a newly-built dedicated DRB.
  • the second information may include an uplink indication or a downlink indication.
  • uplink indication and the downlink indication reference may be made to the foregoing description. To avoid repetition, details are not described herein again.
  • the CU-UP when the CU-UP receives the quality of service QoS flow data, it can send the QoS flow identification ID and PDU of the QoS flow data to the CU-CP. Session ID, where the PDU session corresponding to the PDU session ID includes the QoS flow data, so that the CU-CP can determine the mapping mode of the QoS flow data to the radio bearer, thereby satisfying the transmission performance parameters of the QoS flow and improving the user experience.
  • the CU-UP when the first DRB is the default DRB, when the CU-UP receives a certain QoS flow data from the default DRB, the CU-UP notifies the CU-CP that the QoS flow data arrives, so that the CU-CP establishes a new QoS flow for the QoS flow. Or to map the QoS flow data to another existing private DRB, to implement the remapping process of the QoS flow from the default DRB to the private DRB.
  • the CU-UP when the first DRB is a dedicated DRB, when the CU-UP receives certain QoS flow data from the dedicated DRB, the CU-UP notifies the CU-CP that the QoS flow data arrives, so that the CU-CP is the QoS flow.
  • FIG. 3 shows a schematic flowchart of a specific QoS flow data transmission method according to an embodiment of the present application. It should be understood that FIG. 3 shows the steps or operations of the method for transmitting QoS streaming data, but these steps or operations are merely examples, and the embodiment of the present application may also perform other operations or a modification of each operation in FIG. 3. In addition, each step in FIG. 3 may be performed in a different order than that presented in FIG. 3, and it may not be necessary to perform all operations in FIG. 3.
  • the CU-UP triggers the process of establishing a bearer context (Bearer context setup).
  • the CU-UP receives uplink user data of the UE from the first DRB, or receives downlink user data that needs to be mapped to the first DRB from the 5G core network (5GC).
  • the first DRB is a default DRB.
  • the CU-UP sends first information to the CU-CP, where the first information includes a QoS flow identifier ID and a PDU session ID of the QoS flow data received in step 300, and the PDU session corresponding to the PDU session ID includes The QoS flow data.
  • the first information may further include a DRB ID of the first DRB.
  • the CU-UP may not distinguish an uplink UL or a downlink DL direction, that is, the CU-UP informs the CU-CP of the PDU session ID described in the received QoS flow data and the QoS flow ID of the received QoS flow data.
  • the CU-UP can distinguish the uplink UL and downlink DL directions, that is, the CU-UP informs the CU-CP of the PDU session ID described in the received QoS flow data, and the QoS flow ID of the received QoS flow data. It can also be notified that the QoS flow data is an uplink QoS flow or a downlink QoS flow.
  • the first information may be carried in a data notification message, a bearer context inactivity modification notification message, or a bearer context modification request message, or other E1AP messages. This is not limited in the embodiments of the present application.
  • the CU-CP sends second information to the CU-UP, where the second information is used to instruct the QoS flow data to change from corresponding to the first DRB to corresponding to the second DRB.
  • the second information may refer to the description above. To avoid repetition, details are not described herein again.
  • the CU-CP uses the first information to control transmission of QoS flow data. Specifically, the CU-CP may decide to maintain the mapping relationship between the QoS flow and DRB included in the first message unchanged, or decide to change the QoS flow from corresponding to the first DRB to corresponding to the second DRB.
  • the second DRB may be a newly-built proprietary DRB, or an existing dedicated DRB that has been established.
  • the CU-CP may send a bearer context modification request to the CU-UP, which includes the second information.
  • the second information may include a mapping relationship between a QoS flow and a second DRB.
  • the second information may include: a DRB ID of the second DRB, a QoS flow ID, and a QoS parameter of the QoS flow.
  • the CU-UP and the CU-CP interactively send a bearer context modification request (bearer context modification request) / bearer context modification response (bearer context modification response).
  • the CU-UP may send the data notification message to the CU-CP.
  • the data notification message includes first information.
  • the CU-CP may decide whether to send a bearer context modification request (bearer context modification request) to the CU-UP.
  • the bearer context modification request may include second information.
  • the CU-UP sends a bearer context modification request (bearer context modification request) to the CU-CP.
  • the bearer context modification request may include first information.
  • the CU-CP sends a bearer context modification confirmation (bearer context modification confirmation) to the CU-UP.
  • the CU-CP may send a bearer context modification request to the CU-UP, and the bearer context modification request may include second information. Then, the CU-UP can reply to the CU-CP with a bearer context modification response.
  • the CU-CP sends a UE context modification request (UE context modification request) to the DU, which may include second information.
  • the second information may include: a DRB ID of the second DRB, a QoS flow ID, or a QoS parameter of the QoS flow.
  • the DU sends a UE context modification response (UE context modification response) to the CU-CP.
  • the UE context modification response may further include a transport network layer (TNL) address of the DU, and / or a packet data convergence protocol (PDCP) status.
  • TNL transport network layer
  • PDCP packet data convergence protocol
  • the CU-CP sends a bearer context modification request to the CU-UP.
  • the CU-UP sends a bearer context modification response to the CU-CP.
  • the bearer context modification request may include a TNL transport layer address of the DU and / or a PDCP status.
  • the CU-CP sends an RRC connection reconfiguration message to the UE.
  • the connection reconfiguration message may include second information for the UE to update the QoS flow to DRB mapping relationship.
  • the CU-UP notifies the CU-CP only when a data packet belonging to the QoS flow for the first time arrives. For the QoS flow that has sent the first information, the CU-UP will not remind the CU-CP that the QoS flow data arrives later.
  • the CU-UP maps the QoS flow to the second DRB according to the mapping relationship between the QoS flow ID of the QoS flow and the second DRB sent by the CU-CP.
  • the CU-UP when the CU-UP receives the quality of service QoS flow data, it can send the QoS flow identification ID and PDU of the QoS flow data to the CU-CP. Session ID, where the PDU session corresponding to the PDU session ID includes the QoS flow data, so that the CU-CP can control the transmission of the QoS flow data, thereby meeting the performance parameters of QoS flow and improving the user experience.
  • the CU-UP when the first DRB is the default DRB, when the CU-UP receives a certain QoS flow data from the default DRB, the CU-UP notifies the CU-CP that the QoS flow data arrives, so that the CU-CP establishes a new one for the QoS flow. Or to map the QoS flow data to another existing private DRB, to implement the remapping process of the QoS flow from the default DRB to the private DRB.
  • the CU-UP when the first DRB is a dedicated DRB, when the CU-UP receives certain QoS flow data from the dedicated DRB, the CU-UP notifies the CU-CP that the QoS flow data arrives, so that the CU-CP is the QoS flow.
  • FIG. 4 and FIG. 5 respectively show schematic flowcharts of a data transmission method provided by an embodiment of the present application.
  • the CU-CP can determine the asymmetric QoS flow-to-DRB mapping relationship, and then notify the CU-UP and DU of the asymmetric mapping relationship.
  • the CU decides the asymmetric mapping relationship between QoS and DRB, and then notifies the DU of the asymmetric mapping relationship.
  • the CU-CP, CU-UP, DU in FIG. 4 and the CU-DU in FIG. 5 reference may be made to the description in FIG. 1. To avoid repetition, details are not described herein again.
  • the method for transmitting data in FIG. 4 includes 410 to 440.
  • FIG. 4 shows the steps or operations of the data transmission method, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or a modification of each operation in FIG. 4.
  • each step in FIG. 4 may be performed in a different order than that presented in FIG. 4, and it is possible that not all operations in FIG. 4 are to be performed.
  • the CU-CP determines a mapping relationship between the quality of service QoS flow and the DRB.
  • the mapping relationship includes at least one of the following: the mapping relationship between the uplink QoS flow and the DRB, the mapping relationship between the downlink QoS flow and the DRB, or the mapping between the bidirectional QoS flow and the DRB. relationship.
  • mapping relationship between the uplink QoS flow and the DRB refers to: the mapping relationship between the uplink QoS flow data and the DRB transmitting the uplink QoS flow data;
  • mapping relationship between the downlink QoS flow and the DRB refers to: the downlink transmission QoS
  • the mapping relationship between the bidirectional QoS flow and the DRB refers to: the mapping relationship between the QoS flow data and the DRB transmitting the QoS flow data, where the QoS flow data includes the uplink , Including the uplink.
  • the mapping relationship includes the mapping relationship between the uplink QoS flow and the DRB and / or the mapping relationship between the downlink QoS flow and the DRB
  • the mapping relationship between the QoS flow and the DRB is asymmetric. That is, in the embodiment of the present application, the mapping relationship between the uplink QoS flow and DRB and the mapping relationship between the downlink QoS flow and DRB are decoupled, and the mapping relationship between the uplink QoS flow and DRB and the mapping relationship between the downlink QoS flow and DRB may be the same. Or different, this embodiment of the present application does not limit this.
  • the uplink QoS flow ID # 1 may be mapped to DRB # 1
  • the downlink QoS flow ID # 1 may be mapped to DRB # 2.
  • the mapping relationship between the QoS flow and the DRB is symmetrical, that is, the mapping relationship between the uplink QoS flow and the DRB and the downlink QoS flow are at this time.
  • the mapping relationship of DRB is the same.
  • QoS flow ID # 1 may be mapped to DRB # 1, which means that both the upstream QoS flow ID # 1 and the downstream QoS flow ID # 1 are mapped to DRB # 1.
  • the CU-CP sends third information to the CU-UP, where the third information includes a mapping relationship between the QoS flow and the DRB in 410.
  • the third information may further include a mapping indication, which is used to indicate that the data in the QoS flow mapped to the DRB is uplink data or downlink data.
  • DL data, QoS, flow, map, DRB
  • the third information may further include a mapping indication, which is used to indicate that the data in the QoS flow mapped to the DRB is uplink data or downlink data.
  • DL data, QoS, flow, map, DRB
  • DRB downlink data
  • the third information may further include an asymmetric mapping indication, which is used to indicate that the data in the QoS flow mapped to the DRB is uplink data or downlink data (indication why the UL data, DL, data, QoS, flow, map, DRB).
  • an asymmetric mapping indication which is used to indicate that the data in the QoS flow mapped to the DRB is uplink data or downlink data (indication why the UL data, DL, data, QoS, flow, map, DRB).
  • the asymmetric mapping indication is used to indicate that the mapping relationship is a mapping relationship between uplink QoS flows and DRBs.
  • the asymmetric mapping indication also It can be called uplink indication.
  • the mapping relationship includes a mapping relationship between a downlink QoS flow and a DRB
  • the asymmetric mapping indication is used to indicate that the mapping relationship is a mapping relationship between a downlink QoS flow and a DRB.
  • the asymmetric mapping instruction may also be referred to as a downlink Instructions.
  • the asymmetric mapping indication is used to indicate that the mapping relationship is a mapping relationship between a bidirectional QoS flow and a DRB.
  • the asymmetric mapping instruction may also be referred to as a bidirectional Instructions.
  • the CU-CP can explicitly indicate that the QoS flow in the CU-UP mapping relationship is an uplink QoS flow, or a downlink QoS flow, or a bidirectional QoS flow.
  • the third information may be in the format of Table 1 below:
  • QFI stands for QoS flow ID.
  • the DRB ID, QFI, QFI direction, and QoS parameters can be filled in Table 1 according to specific scenarios.
  • the QFI direction may specifically be the above-mentioned asymmetric mapping indication.
  • the CU-CP may also implicitly indicate that the QoS flow in the CU-UP mapping relationship is an uplink QoS flow, or a downlink QoS flow, or a bidirectional QoS flow.
  • the third information may include a guaranteed flow bit rate GFBR or a maximum flow bit rate MFBR of QoS flow # 1.
  • QoS flow # 1 is an uplink QoS flow; if the QoS flow # If the downstream GFBR or MFBR of 1 is greater than zero and the upstream GFBR or MFBR is equal to zero, then QoS flow # 1 is the downstream QoS flow; if the downstream GFBR or MFBR of QoS flow # 1 is greater than zero and the upstream GFBR or MFBR is greater than zero, The QoS flow # 1 is a bidirectional QoS flow.
  • the CU-CP may send a bearer context establishment request or a bearer context modification request to the CU-UP, and the bearer context establishment request or the bearer context modification request may include third information.
  • the CU-UP may receive the third information from the CU-CP and use the third information.
  • the CU-UP After receiving the third information, the CU-UP records the mapping relationship indicated by the third information.
  • the CU-UP receives the downlink QoS flow data sent by the core network, it can map the downlink QoS flow data to the corresponding DRB and pass it to the DU according to the mapping relationship between the downlink QoS flow ID and the DRB indicated by the third information.
  • the CU-UP When the CU-UP receives the uplink QoS flow data sent by the terminal device, it can verify whether the uplink QoS flow data is transmitted on the corresponding DRB according to the mapping relationship between the uplink QoS flow ID and the DRB indicated by the third information.
  • the CU-UP will wait for the Receive the end marker packet of the uplink QoS flow data on DRB # 1, and determine that the last data packet of the uplink QoS flow data is received from DRB # 1. In addition, the CU-UP will receive the uplink QoS flow data from DRB # 3. After that, the CU-UP sends the entire uplink QoS flow data to the core network.
  • the CU-CP sends third information to the DU, where the third information includes a mapping relationship between the QoS flow in the 410 and the DRB.
  • the CU-CP may send a user equipment UE context establishment request or a UE context modification request to the DU, and the UE context establishment request or the UE context modification request includes third information.
  • the DU receives the third information.
  • the DU uses the third information.
  • the DU After receiving the third information, the DU records the mapping relationship indicated by the third information. For the QoS flow corresponding to the uplink QoS flow and / or the downlink QoS flow indicated by the third information, the media access control (MAC) layer and the radio link control (RLC) layer are determined respectively. Configuration parameters. In a possible implementation manner, the DU performs uplink and downlink scheduling respectively at the MAC layer according to the QoS flow in the DRB.
  • MAC media access control
  • RLC radio link control
  • the CU-CP determines the asymmetric QoS flow-to-DRB mapping relationship, and the CU-UP notifies the CU-UP and the DU of the asymmetric mapping relationship, which can implement flexible uplink QoS flow mapping and downlink QoS flow mapping realizes the decoupling of the mapping relationship between uplink QoS flow and downlink QoS flow.
  • the requirements for the uplink transmission and the downlink transmission of the QoS flow can be separately guaranteed (the guaranteed bit rates and maximum bit rates of the uplink and downlink transmissions are different); on the other hand, the network can be based on the uplink / downlink network load and interference conditions. , QoS flow parameter characteristics, etc., flexible configuration of uplink and downlink mapping of QoS flow, further improving the user experience.
  • the method for transmitting data in FIG. 5 includes 510 to 530. It should be understood that FIG. 5 shows the steps or operations of the data transmission method, but these steps or operations are merely examples, and the embodiment of the present application may also perform other operations or a modification of each operation in FIG. 5. In addition, each step in FIG. 5 may be performed in a different order than that presented in FIG. 5, and it is possible that not all operations in FIG. 5 are to be performed.
  • the CU determines a mapping relationship between a quality of service QoS flow and a DRB, where the mapping relationship includes at least one of the following: a mapping relationship between an uplink QoS flow and a DRB, a mapping relationship between a downlink QoS flow and a DRB, or a mapping relationship between a two-way QoS flow and a DRB.
  • mapping relationship between a QoS flow and a DRB refer to the description in 410 in FIG. 4. To avoid repetition, details are not described herein again.
  • the CU sends third information to the DU, where the third information includes a mapping relationship between the QoS flow in the 410 and the DRB.
  • the DU receives the third information from the CU.
  • the third information reference may be made to the description in 420 and 430 in FIG. 4. To avoid repetition, details are not described herein again.
  • the DU uses the third information.
  • 530 may refer to the description in 440 in FIG. 4. To avoid repetition, details are not described herein again.
  • the CU decides the asymmetric QoS flow-to-DRB mapping relationship and notifies the DU of the asymmetric mapping relationship, which can implement flexible uplink QoS flow mapping and downlink QoS flow mapping and achieve uplink QoS. Decoupling the mapping relationship between flow and downlink QoS flow.
  • the requirements for the uplink transmission and the downlink transmission of the QoS flow can be separately guaranteed (the guaranteed bit rates and maximum bit rates of the uplink and downlink transmissions are different); on the other hand, the network can be based on the uplink / downlink network load and interference conditions. , QoS flow parameter characteristics, etc., flexible configuration of uplink and downlink mapping of QoS flow, further improving the user experience.
  • FIG. 6 shows a schematic flowchart of a specific QoS stream data transmission method according to an embodiment of the present application. It should be understood that FIG. 6 shows the steps or operations of the method for transmitting QoS streaming data, but these steps or operations are merely examples, and the embodiment of the present application may also perform other operations or a modification of each operation in FIG. 6. In addition, each step in FIG. 6 may be performed in a different order than that presented in FIG. 6, and it is possible that not all operations in FIG. 6 are to be performed.
  • CU-CP, CU-UP, and DU can refer to the description in FIG. 1. To avoid repetition, details are not repeated here.
  • the CU-CP decides to trigger the bearer context process (bearer context setup).
  • the CU-CP sends a bearer context setup request (bearer context setup request) to the CU-UP, which includes third information.
  • the CU-UP In response to the bearer context establishment request, the CU-UP sends a bearer context establishment response (bearer context setup request request response) to the CU-CP.
  • a bearer context establishment response (bearer context setup request request response)
  • the CU-CP and the DU perform a UE context setup (UE context setup) process. Specifically, the CU-CP sends a UE context establishment request to the DU, and the UE context establishment request includes third information. In response to the UE context establishment request, the DU may send a context establishment response to the CU-UP. Specifically, the CU-CP and the DU communicate through an F1-C interface.
  • UE context setup UE context setup
  • the CU-CP sends a bearer context modification request (bearer context modification request) to the CU-UP.
  • the CU-UP In response to the bearer context modification request sent by the CU-CP, the CU-UP sends a bearer context modification response (bearer context modification response) to the CU-CP.
  • a bearer context modification response (bearer context modification response)
  • the CU-CP determines the asymmetric QoS flow-to-DRB mapping relationship, and then notifies the CU-UP and DU of the asymmetric mapping relationship, which can implement flexible uplink QoS flow mapping and downlink QoS flow.
  • the mapping realizes the decoupling of the mapping relationship between the uplink QoS flow and the downlink QoS flow.
  • the requirements for the uplink transmission and the downlink transmission of the QoS flow can be separately guaranteed (the guaranteed bit rates and maximum bit rates of the uplink and downlink transmissions are different); on the other hand, the network can be based on the uplink / downlink network load and interference conditions. , QoS flow parameter characteristics, etc., flexible configuration of uplink and downlink mapping of QoS flow, further improving the user experience.
  • FIG. 7 shows a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • the access network device may determine the direction of the QoS flow, and may independently configure the uplink transmission and the downlink transmission of the QoS flow.
  • the CU and CU-CP in FIG. 7 reference may be made to the description in FIG. 1. To avoid repetition, details are not described herein again.
  • the core network CN determines the direction of the QoS flow.
  • some QoS flows may have only one-way characteristics, that is, only uplink QoS flows, or only downlink QoS flows, or some QoS flows may have two-way characteristics, that is, the QoS flows may be
  • the uplink QoS flow may also be an uplink QoS flow.
  • a core network CN for example, an access and mobility management function (AMF) network element in the core network may determine the directional characteristics of the QoS flow.
  • AMF access and mobility management function
  • the core network sends fourth information to the RAN.
  • the core network may notify the radio access network RAN (for example, CU-CP, or CU) of the direction characteristics of a certain QoS flow through the fourth information, for example, the QoS flow is an uplink QoS flow, a downlink QoS flow, or a bidirectional QoS flow.
  • RAN for example, CU-CP, or CU
  • the fourth information includes: a PDU session ID, a QoS flow ID, and a directional characteristic of a QoS flow corresponding to the QoS flow ID.
  • the directional characteristic is, for example, uplink, downlink, or bidirectional.
  • the fourth information may further include an uplink QoS parameter of the QoS flow, where the uplink QoS parameter is a QoS parameter configured when the QoS flow is transmitted in uplink.
  • the fourth information may further include downlink QoS parameters of the QoS flow, wherein the downlink QoS parameters are QoS parameters configured when the QoS flow is transmitted in the downlink.
  • the fourth information may further include UL QoS parameters and DL QoS parameters of the QoS flow.
  • the fourth information may be in the format of Table 2 below.
  • QFI represents a QoS flow ID
  • session ID represents a PDU session ID
  • QFI represents a QoS flow ID
  • session ID represents a PDU session ID
  • QoS parameters can be filled in Table 2 according to specific scenarios.
  • the AMF may send a PDU session resource establishment request (PDU session resource setup request) to the RAN, and the PDU session resource establishment request may include fourth information.
  • the RAN may send a PDU session resource establishment response (PDU session resource setup response) to the AFM.
  • the RAN receives the fourth information.
  • the RAN uses the fourth information.
  • the RAN acquires the information included in the fourth information, and determines the directional characteristic of the QoS flow according to the information included in the RAN.
  • the CU-CP may separately notify the CU-UP and the DU of the directional characteristic of the QoS flow.
  • the access network device may determine the direction of the QoS flow, and may independently configure the uplink transmission and the downlink transmission of the QoS flow. Specifically, if the QoS flow is only an uplink QoS flow, the access network device determines an uplink data packet scheduling policy of the QoS flow without considering downlink transmission; if the QoS flow is only a downlink QoS flow, access The network device decides the scheduling strategy for the downlink data packets of the QoS flow without considering the uplink transmission. Therefore, the embodiments of the present application can meet specific requirements of QoS flows.
  • CU, CU-CP, CU-UP, DU, and CN include hardware structures and / or software modules corresponding to performing each function.
  • the embodiments of this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.
  • functional units may be divided into CU, CU-CP, CU-UP, DU, and CN according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more of them may be divided.
  • the functions are integrated in one processing unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit. It should be noted that the division of the units in the embodiments of the present application is schematic, and is only a logical function division. There may be another division manner in actual implementation.
  • FIG. 8 shows a possible exemplary block diagram of a communication device involved in the embodiment of the present application.
  • the device 800 may exist in the form of software, hardware, or a combination of software and hardware. .
  • FIG. 8 shows a possible schematic block diagram of a device involved in an embodiment of the present application.
  • the apparatus 800 includes a processing unit 802 and a communication unit 803.
  • the processing unit 802 is configured to control and manage the operation of the device.
  • the communication unit 803 is configured to support communication between the device and other devices.
  • the device may further include a storage unit 801 for storing program code and data of the device.
  • the apparatus 800 shown in FIG. 8 may be a CU, a CU-CP, a CU-UP, a DU, and a CN involved in the embodiment of the present application.
  • the processing unit 802 can support the device 800 to perform the actions performed by the CU in the foregoing method examples.
  • the processing unit 802 supports the device 800 to perform, for example, 510 in FIG. 5 and 730 in FIG. 7. , And / or other processes for the techniques described herein.
  • the communication unit 803 can support communication between the device 800 and the DU, CN, etc.
  • the communication unit 803 supports the device 800 to perform step 520 in FIG. 5, 720 in FIG. 7, and / or other related communication processes.
  • the processing unit 802 can support the device 800 to perform the actions performed by the CU-CP in the foregoing method examples.
  • the processing unit 802 supports the device 800 to perform, for example, 230 in FIG. 2. 300 in FIG. 3, 410 in FIG. 4, 500 in FIG. 6, 730 in FIG. 7, and / or other processes for the techniques described herein.
  • the communication unit 803 can support communication between the device 800 and CU-UP, DU, CN, etc.
  • the communication unit 803 supports the device 800 to perform steps 220, 240 in FIG. 2, 301 to 306 in FIG. 3, and FIG. 4 420,430, 601 to 605 in FIG. 6, 720 in FIG. 7, and / or other related communication processes.
  • the processing unit 802 can support the device 800 to perform the actions performed by the CU-UP in the foregoing method examples.
  • the processing unit 802 supports the device 800 to perform, for example, 210 in FIG. 2.
  • the communication unit 803 can support communication between the device 800 and CU-UP, DU, CN, etc.
  • the communication unit 803 supports the device 800 to perform steps 220, 240 in FIG. 2, 301 to 303, and 305 in FIG. 3, 420 in FIG. 4, 601, 602, 604, 605 in FIG. 6, and / or other related communication processes.
  • the processing unit 802 can support the device 800 to perform the actions performed by the CU-UP in the foregoing method examples.
  • the processing unit 802 supports the device 800 to perform, for example, 210 in FIG. 2.
  • the communication unit 803 can support communication between the device 800 and CU-UP, DU, CN, etc.
  • the communication unit 803 supports the device 800 to perform steps 220, 240 in FIG. 2, 301 to 303, and 305 in FIG. 3, 420 in FIG. 4, 601, 602, 604, 605 in FIG. 6, and / or other related communication processes.
  • the processing unit 802 can support the device 800 to perform the actions performed by the DU in the foregoing method examples.
  • the processing unit 802 supports the device 800 to perform, for example, 440 in FIG. 4 and 530 in FIG. 5. , And / or other processes for the techniques described herein.
  • the communication unit 803 can support communication between the device 800 and CU-CP, CU-UP, CN terminal equipment, etc.
  • the communication unit 803 supports the device 800 to perform 304 in FIG. 3, 430 in FIG. 4, and FIG. 5 520, 603 in FIG. 6, and / or other related communication processes.
  • the processing unit 802 can support the device 800 to perform the actions performed by the CN in the foregoing method examples.
  • the processing unit 802 supports the device 800 to perform, for example, 710 in FIG. 7 and / or use Other processes for the techniques described herein.
  • the communication unit 803 can support communication between the device 800 and CU-CP, CU, and the like.
  • the communication unit 803 supports the device 800 to perform 720 in FIG. 7 and / or other related communication processes.
  • the processing unit 802 may be a processor or a controller, for example, it may be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (application) -specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, units, and circuits described in connection with the present disclosure.
  • the processor may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication unit 803 may be a communication interface. The communication interfaces are collectively referred to. In a specific implementation, the communication interface may include one or more interfaces.
  • the storage unit 801 may be a memory.
  • the processing unit 802 is a processor
  • the communication unit 803 is a communication interface
  • the storage unit 801 is a memory
  • the device 800 involved in the embodiment of the present application may be the communication device 900 shown in FIG. 9.
  • the apparatus 900 includes: a processor 902 and a communication interface 903. Further, the apparatus 900 may further include a memory 901. Optionally, the device 900 may further include a bus 904.
  • the communication interface 903, the processor 902, and the memory 901 may be connected to each other through a bus 904.
  • the bus 904 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA). Bus, etc.
  • the bus 904 may be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • the processor 902 may execute various functions of the device 900 by running or executing a program stored in the memory 901.
  • the communication device 900 shown in FIG. 9 may be a CU, a CU-CP, a CU-UP, a DU, and a CN involved in the embodiment of the present application.
  • the processor 902 can execute the actions performed by the CU in the foregoing method examples by running or executing a program stored in the memory 901.
  • the processor 902 can execute the actions performed by the CU-CP in the foregoing method examples by running or executing a program stored in the memory 901.
  • the processor 902 can execute the actions performed by the CU-UP in the foregoing method examples by running or executing a program stored in the memory 901.
  • the processor 902 can execute the actions performed by the DU in the foregoing method examples by running or executing a program stored in the memory 901.
  • the processor 902 can execute or execute a program stored in the memory 901 to perform actions performed by the CN in each of the foregoing method examples.
  • a computer-readable storage medium in which instructions are stored, and the instructions in the foregoing method embodiments are executed when the instructions are executed.
  • a computer program product including an instruction is provided, and the method in the foregoing method embodiment is executed when the instruction is executed.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (DVD)), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD)) and so on.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • semiconductor medium for example, a solid state disk (solid state disk, SSD)
  • At least one means one or more, and “multiple” means two or more.
  • “And / or” describes the association relationship between related objects, and indicates that there can be three kinds of relationships. For example, A and / or B can indicate: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character “/” generally indicates that the related objects are an "or” relationship. "At least one or more of the following” or similar expressions refers to any combination of these items, including any combination of single or plural items.
  • At least one (a) of a, b, or c can be expressed as: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • an embodiment or “an embodiment” mentioned throughout the specification means that a particular feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present invention.
  • the appearances of "in one embodiment” or “in an embodiment” appearing throughout the specification are not necessarily referring to the same embodiment.
  • the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not deal with the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and / or a computer.
  • an application running on a computing device and a computing device can be components.
  • One or more components can reside within a process and / or thread of execution, and a component can be localized on one computer and / or distributed between 2 or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • a component may, for example, be based on a signal having one or more data packets (e.g., data from two components that interact with another component between a local system, a distributed system, and / or a network, such as the Internet that interacts with other systems through signals) Communicate via local and / or remote processes.
  • data packets e.g., data from two components that interact with another component between a local system, a distributed system, and / or a network, such as the Internet that interacts with other systems through signals
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of this application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • the aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .

Landscapes

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

Abstract

本申请提供数据传输的方法和装置，能够在分离的CU-CP和CU-UP架构下实现基于服务质量QoS流的数据传输。本申请实施例中，在CU-CP/CU-UP分离场景下，当CU-UP接收到服务质量QoS流数据时，可以向CU-CP发送该QoS流数据的QoS流标识ID和PDU会话ID，其中PDU会话ID所对应的PDU会话包括该QoS流数据，使得CU-CP可以决定该QoS流数据到无线承载的映射方式，从而满足了QoS流的传输性能参数，提升用户体验。

Description

数据传输的方法和装置 技术领域
本申请涉及通信领域，并且更具体的，涉及通信领域中的数据传输的方法和装置。
背景技术
随着下一代通信系统研究的全面展开并逐渐深入，业界对5G研究的具体内容达成了基本共识。5G将支持各种类型的网络部署和应用类型，其中包括：更高速率体验和更大带宽的接入能力、更低时延和高可靠的信息交互、更大规模，低成本的MTC设备的接入和管理。
现在标准中定义接入网设备可以采用集中式单元(central unit，CU)与分布式单元(distributed unit，DU)分离的架构。并且，在CU-DU架构中，又增加了一种新的架构：在CU部分，可以将CU分为集中式单元-控制面(central unit-control plane，CU-CP)和分布式单元-用户面(Central Unit-User Plane，CU-UP)。其中，CU-CP部分包括无线资源控制(Radio Resource Control，RRC)功能以及分组数据汇聚协议(packet data convergence protocol，PDCP)的控制面部分，CU-UP部分包括CU的数据面部分，主要包括服务数据适配协议(service data adaptation protocol，SDAP)协议栈以及PDCP协议栈的数据面部分。
基于此，如何在该分离的CU-CP和CU-UP架构下实现基于服务质量流(quality of service flow，QoS flow)的数据传输是亟需解决的问题。
发明内容
本申请提供数据传输的方法和装置，能够在分离的CU-CP和CU-UP架构下实现基于服务质量QoS流的数据传输。
第一方面，提供了一种数据传输的方法，所述方法包括：
无线接入网RAN的集中式单元-用户面CU-UP接收服务质量QoS流数据；
所述CU-UP向所述无线接入网RAN集中式单元-控制面CU-CP发送第一信息，其中，所述第一信息包括所述QoS流数据的QoS流标识ID和PDU会话ID，所述PDU会话ID所对应的PDU会话包括所述QoS流数据。
因此，本申请实施例中，在CU-CP/CU-UP分离场景下，当CU-UP接收到服务质量QoS流数据时，可以向CU-CP发送该QoS流数据的QoS流标识ID和PDU会话ID，其中PDU会话ID所对应的PDU会话包括该QoS流数据，使得CU-CP可以决定该QoS流数据到无线承载的映射方式，从而满足了QoS流的传输性能参数，提升用户体验。
结合第一方面，在第一方面的某些实现方式中，所述QoS流数据对应第一数据无线承载DRB，其中，所述无线接入网集中式单元-用户面CU-UP接收服务质量QoS流数据，包括：
所述CU-UP通过所述第一DRB接收来自终端设备所述QoS流数据；或者
所述CU-UP接收来自核心网的需要通过所述第一DRB传递的所述QoS流数据。
结合第一方面，在第一方面的某些实现方式中，还包括：所述CU-UP接收来自所述CU-CP的第二信息，所述第二信息用于指示所述QoS流数据从对应所述第一DRB变为对应第二DRB。这样，后续CU-UP将从该第二DRB接收来自终端设备的该QoS流数据，或者CU-UP从核心网接收到该QoS流数据时，将该QoS流数据映射到第二DRB上进行传输。
可选的，第二信息可以包括所述第二DRB的DRB ID、所述QoS流ID，可选的还可以包括所述QoS流的QoS参数。
结合第一方面，在第一方面的某些实现方式中，所述第一DRB为默认DRB，所述第二DRB为专有DRB。
当第一DRB为默认DRB时，CU-UP从默认DRB收到某一QoS flow数据时，CU-UP通知CU-CP该QoS flow数据到达，使得CU-CP为该QoS flow建立新的专有DRB，或者将该QoS flow数据映射到另一已有的专有DRB上，实现了QoS flow从默认DRB到专有DRB的重映射流程。
结合第一方面，在第一方面的某些实现方式中，所述第一信息中还包括所述第一DRB的DRB ID。
可选的，本申请的另一种实现方式中，第一信息中可以不包括第一DRB的DRB ID，即CU-UP可以不需要告知CU-CP第一DRB的DRB ID，只需要告知上述PDU会话下的QoS流ID列表即可，此时可以节省额外信令开销。
结合第一方面，在第一方面的某些实现方式中，当所述CU-UP从终端设备接收所述QoS流数据时，所述第一信息还包括上行指示；或者当所述CU-UP从核心网接收所述QoS流数据时，所述第一信息还包括下行指示。
具体的，上行指示可以用于指示传输方向为上行，或者用于指示该QoS流数据为上行QoS流数据。下行指示可以用于指示传输方向为下行，或者用于指示该QoS流数据为下行QoS流数据。这时，CU-UP可以分别明确告知CU-CP，该QoS流数据为上行数据或者下行数据。
或者，可选的，CU-UP仅告知CU-CP QoS流数据到达，并不告诉CU-CP该QoS流数据为上行QoS流数据或下行QoS流数据，也就是说，此时CU-CP以及CU-UP并不需要区分该QoS流数据为上行数据还是下行数据。
第二方面，提供了一种数据传输的方法，包括：
无线接入网RAN集中式单元的控制面CU-CP从无线接入网集中式单元用户面CU-UP接收第一信息，其中，所述第一信息包括QoS流数据的QoS流标识ID和PDU会话ID，所述PDU会话ID所对应的PDU会话包括所述QoS流数据；
所述CU-CP使用所述第一信息。
因此，本申请实施例中，在CU-CP/CU-UP分离场景下，当CU-UP接收到服务质量QoS流数据时，可以向CU-CP发送该QoS流数据的QoS流标识ID和PDU会话ID，其中PDU会话ID所对应的PDU会话包括该QoS流数据，使得CU-CP可以决定该QoS流数据到无线承载的映射方式，从而满足了QoS流的传输性能参数，提升用户体验。
具体的，CU-CP获取该第一信息中包括的信息，并根据其中包括的信息，确定QoS流数据到达。进一步的，CU-CP可以确定继续保持第一信息中包括的QoS流与第一DRB的映射关系，或者将该QoS流对应的该第一DRB变为第二DRB。
可选的，当CU-CP确定继续保持第一信息中包括的QoS流与第一DRB的映射关系不变，可以不执行其他操作。
结合第二方面，在第二方面的某些实现方式中，当CU-CP确定将该QoS流对应的该第一DRB变为第二DRB时，还包括：所述CU-CP向所述CU-UP发送第二信息，所述第二信息用于指示所述QoS流数据从对应第一DRB变为对应第二DRB。这样，使得DU可以获取该QoS流与第二DRB的映射关系，用于DU对用户设备进行第二DRB上下行调度。
可选的，第二信息可以包括所述第二DRB的DRB ID、所述QoS流ID，可选的还可以包括所述QoS流的QoS参数。
一种实现方式中，CU-CP可以向DU发送F1-C消息，该F1-C消息中封装由发送给终端设备的RRC消息，该RRC消息中可以包括该第二信息。
结合第二方面，在第二方面的某些实现方式中，所述第一DRB为默认DRB，所述第二DRB为专有DRB。
当第一DRB为默认DRB时，CU-UP从默认DRB收到某一QoS flow数据时，CU-UP通知CU-CP该QoS flow数据到达，使得CU-CP为该QoS flow建立新的专有DRB，或者将该QoS flow数据映射到另一已有的专有DRB上，实现了QoS flow从默认DRB到专有DRB的重映 射流程。
结合第二方面，在第二方面的某些实现方式中，所述第一信息中还包括所述第一DRB的DRB ID。
结合第二方面，在第二方面的某些实现方式中，，所述第一信息还包括上行指示，所述上行指示用于所述QoS流数据为上行数据；或者
所述第一信息还包括下行指示，所述下行指示用于所述QoS流数据为下行数据。
第三方面，提供了一种数据传输的方法，其特征在于，包括：
集中式单元CU确定服务质量QoS流与DRB的映射关系，所述映射关系包括以下至少一个：上行QoS流与DRB的映射关系、下行QoS流与DRB的映射关系或双向QoS流与DRB的映射关系；
所述CU向分布式单元DU发送第三信息，所述第三信息包括所述QoS流与DRB的映射关系。
因此，本申请实施例中，CU决定非对称向QoS flow到DRB映射关系，并将该非对称映射关系通知给DU，能够实现了灵活的上行QoS flow映射和下行QoS flow映射，实现了上行QoS流和下行QoS流映射关系的解耦。这样，一方面能够分别保障QoS流的上行传输和下行传输的需求(其上行传输、下行传输的保障比特速率、最大比特速率不同)，另一方面网络可以根据上行/下行的网络负载、干扰情况、QoS流参数特征等，灵活配置QoS流的上行和下行映射，进一步提升了用户体验。
结合第三方面，在第三方面的某些实现方式中，所述CU包括分离的集中式单元-用户面CU-UP和集中式单元-控制面CU-CP，
其中，所述集中式单元CU确定服务质量QoS流与DRB的映射关系，包括：所述CU-CP确定所述QoS流与DRB的映射关系；
所述CU向分布式单元DU发送第三信息，包括：所述CU-CP向所述DU发送所述第三信息。
DU收到第三信息后，记录该第三信息所指示的映射关系。对于第三信息所指示的上行QoS流和/或下行QoS流所对应的QoS流，分别决定其媒体介入控制(media access control，MAC)层、无线链路控制(radio link control，RLC)层的配置参数。一种可能的实现方式中，DU根据DRB内的的QoS流，在MAC层分别进行上行、下行调度。
所述方法还包括：所述CU-CP向所述CU-UP所述发送第三信息。
CU-UP收到第三信息后，记录该第三信息所指示的映射关系。当CU-UP收到核心网发送的下行QoS流数据时，可以根据第三信息所指示的下行QoS流ID与DRB的映射关系，将该下行QoS流数据映射到对应的DRB上传递给DU。当CU-UP收到终端设备发送的上行QoS流数据时，可以根据第三信息所指示的上行QoS流ID与DRB的映射关系，验证该上行QoS流数据是否在对应的DRB上进行传输。
结合第三方面，在第三方面的某些实现方式中，所述CU-CP向所述CU-UP所述发送第三信息，包括：
所述CU-CP向所述CU-UP发送承载上下文建立请求或承载上下文修改请求，所述承载上下文建立请求或所述承载上下文修改请求中包括所述第三信息；
所述CU-CP向所述DU发送所述第三信息，包括：
所述CU-CP向所述DU发送用户设备UE上下文建立请求或UE上下文修改请求，所述UE上下文建立请求或所述UE上下文修改请求中包括所述第三信息。
结合第三方面，在第三方面的某些实现方式中，第三信息中还可以包括映射指示(mapping indication)，用于指示映射到DRB中的QoS流中的数据为上行数据或下行数据(indication whether the UL data or DL data of one QoS flow map to this DRB)，或者指示映射到DRB中的QoS流中的数据为上行数据和下行数据。
可选的，本申请实施例中，第三信息中还可以包括非对称映射指示(mapping  indication)，用于指示映射到DRB中的QoS流中的数据为上行数据或下行数据(indication whether the UL data or DL data of one QoS flow map to this DRB)。
这样，CU-CP可以显式指示CU-UP映射关系中QoS流为上行QoS流，或者下行QoS流，或者双向QoS流。
可选的，本申请实施中，CU-CP也可以隐式指示CU-UP映射关系中QoS流为上行QoS流，或者下行QoS流，或者双向QoS流。
因此，本申请实施例中，CU-CP决定非对称向QoS flow到DRB映射关系，CU-UP将该非对称映射关系通知给CU-UP和DU，能够实现了灵活的上行QoS flow映射和下行QoS flow映射，实现了上行QoS流和下行QoS流映射关系的解耦。这样，一方面能够分别保障QoS流的上行传输和下行传输的需求(其上行传输、下行传输的保障比特速率、最大比特速率不同)，另一方面网络可以根据上行/下行的网络负载、干扰情况、QoS流参数特征等，灵活配置QoS流的上行和下行映射，进一步提升了用户体验。
第四方面，提供了一种数据传输的方法，包括：
无线接入网中的分布式单元DU从集中式单元CU接收第三信息，所述第三信息包括QoS流与DRB的映射关系，其中，所述映射关系包括以下至少一个：上行QoS流与DRB的映射关系、下行QoS流与DRB的映射关系或双向QoS流与DRB的映射关系；
所述DU使用所述第三信息。
因此，本申请实施例中，CU决定非对称向QoS flow到DRB映射关系，并将该非对称映射关系通知给DU，能够实现了灵活的上行QoS flow映射和下行QoS flow映射，实现了上行QoS流和下行QoS流映射关系的解耦。这样，一方面能够分别保障QoS流的上行传输和下行传输的需求(其上行传输、下行传输的保障比特速率、最大比特速率不同)，另一方面网络可以根据上行/下行的网络负载、干扰情况、QoS流参数特征等，灵活配置QoS流的上行和下行映射，进一步提升了用户体验。
结合第四方面，在第四方面的某些实现方式中，所述CU包括分离的集中式单元-用户面CU-UP和集中式单元-控制面CU-CP，其中，所述无线接入网中的分布式单元DU从CU接收第三信息，包括：
所述DU从所述CU-CP接收所述第三信息。
DU收到第三信息后，记录该第三信息所指示的映射关系。对于第三信息所指示的上行QoS流和/或下行QoS流所对应的QoS流，分别决定其媒体介入控制(media access control，MAC)层、无线链路控制(radio link control，RLC)层的配置参数。一种可能的实现方式中，DU根据DRB内的的QoS流，在MAC层分别进行上行、下行调度。
结合第四方面，在第四方面的某些实现方式中，所述DU从所述CU-CP接收所述第三信息，包括：
所述DU从所述CU-CP接收用户设备UE上下文建立请求或UE上下文修改请求，所述UE上下文建立请求或所述UE上下文修改请求中包括所述第三信息。
结合第四方面，在第四方面的某些实现方式中，当所述映射关系包括上行QoS流与DRB的映射关系时，所述第三信息中还包括上行指示；
当所述映射关系包括下行QoS流与DRB的映射关系时，所述第三信息中还包括下行指示；
当所述映射关系包括双向QoS流与DRB的映射关系时，所述第三信息中还包括双向指示。
第五方面，提供了一种数据传输的方法，包括：
核心网CN确定QoS流的方向，该QoS流的方向包括仅为上行QoS流、仅为下行QoS流或为双向QoS流；
核心网向RAN发送第四信息，其中，该第四信息用于指示该QoS流的方向。
这里，RAN具体可以为CU-CP，或者CU。
一种可能的实现方式，该第四信息包括：PDU会话(session)ID、QoS流ID、QoS流ID对应的QoS流的方向特性，这里方向特性例如为上行、下行或者双向。
另外，当QoS流为上行时，第四信息中还可以包括该QoS流的上行QoS参数，其中上行QoS参数为该QoS流在上行传输时所配置的QoS参数。当QoS流为下行时，第四信息中还可以包括该QoS流的下行QoS参数，其中下行QoS参数为该QoS流在下行传输时所配置的QoS参数。当QoS流为双向时，第四信息中还可以包括该QoS flow的UL QoS参数和DL QoS参数。
因此，本申请实施例中，接入网设备可根据确定QoS流的方向，并可以对该QoS流的上行传输和下行传输进行独立配置。具体而言，若该QoS流仅为上行QoS流，则接入网设备决定该QoS流的上行数据包的调度策略，而不用考虑下行传输；若该QoS流仅为下行QoS流，则接入网设备决定该QoS流的下行数据包的调度策略，而不用考虑上行传输。因此本申请实施例能够满足QoS流的特定需求。
第六方面，提供了一种数据传输的方法，包括：
核心网CN确定QoS流的方向，
RAN从核心网接收第四信息，其中，该第四信息用于指示该QoS流的方向，该QoS流的方向包括仅为上行QoS流、仅为下行QoS流或为双向QoS流；
该RAN使用该第四信息。具体的，RAN获取该第四信息中包括的信息，并根据其中包括的信息，确定QoS流的方向特性。。
这里，RAN具体可以为CU-CP，或者CU。
因此，本申请实施例中，接入网设备可根据确定QoS流的方向，并可以对该QoS流的上行传输和下行传输进行独立配置。具体而言，若该QoS流仅为上行QoS流，则接入网设备决定该QoS流的上行数据包的调度策略，而不用考虑下行传输；若该QoS流仅为下行QoS流，则接入网设备决定该QoS流的下行数据包的调度策略，而不用考虑上行传输。因此本申请实施例能够满足QoS流的特定需求。
第七方面，提供了一种装置，该装置可以是无线接入网设备，无线接入网设备中的网元或模块，也可以是无线接入网设备内的芯片，无线接入网设备中的网络或模块内的芯片。该装置具有实现上述第一方面至第六方面及任一方面的各种可能的实现方式的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，该装置包括：收发模块，可选地，该装置还包括处理模块，所述收发模块例如可以是收发器、接收器、发射器中的至少一种，该收发模块可以包括射频电路或天线。该处理模块可以是处理器。可选地，所述装置还包括存储模块，该存储模块例如可以是存储器。当包括存储模块时，该存储模块用于存储指令。该处理模块与该存储模块连接，该处理模块可以执行该存储模块存储的指令或源自其他的指令，以使该装置执行上述第一方面至第六方面及任一方面的各种可能的实现方式的通信方法。在本设计中，该装置可以为无线接入网设备，或无线接入网设备中的模块、网元或者功能。
在另一种可能的设计中，当该装置为芯片时，该芯片包括：收发模块，可选地，该装置还包括处理模块，收发模块例如可以是该芯片上的输入/输出接口、管脚或电路等。处理模块例如可以是处理器。该处理模块可执行指令，以使该终端内的芯片执行上述第一方面至第六方面以及任意可能的实现的通信方法。可选地，该处理模块可以执行存储模块中的指令，该存储模块可以为芯片内的存储模块，如寄存器、缓存等。该存储模块还可以是位于通信设备内，但位于芯片外部，如只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)等。
其中，上述任一处提到的处理器，可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用 于控制上述第一方面至第六方面各方面通信方法的程序执行的集成电路。
第八方面，提供了一种计算机存储介质，该计算机存储介质中存储有程序代码，该程序代码用于指示执行上述第一方面至第六方面任一方面或其任意可能的实现方式中的方法的指令。
第九方面，提供了一种包含指令的计算机程序产品，其在计算机上运行时，使得计算机执行上述第一方面至第六方面任一方面或其任意可能的实现方式中的方法。
第十方面，提供了一种通信系统，该通信系统包括具有实现上述第一方面至第六方面任一方面的各方法及各种可能设计的功能的装置及其组合。
第十一方面，提供了一种处理器，用于与存储器耦合，用于执行上述第一方面至第六方面任一方面或其任意可能的实现方式中的方法。
第十二方面，提供了一种芯片，芯片包括处理器和通信接口，该通信接口用于与外部器件或内部器件进行通信，该处理器用于实现上述第一方面至第六方面任一方面或其任意可能的实现方式中的方法。
可选地，该芯片还可以包括存储器，该存储器中存储有指令，处理器用于执行存储器中存储的指令或源于其他的指令。当该指令被执行时，处理器用于实现上述第一方面至第六方面任一方面其任意可能的实现方式中的方法。
可选地，该芯片可以集成在网络设备上。
附图说明
图1示出了应用本申请实施例的无线接入网的示意图。
图2示出了本申请实施例提供的数据传输的方法的示意性流程图。
图3示出了本申请实施例提供的一个具体的QoS流数据传输的方法的示意性流程图。
图4示出了本申请实施例提供的数据传输的方法的示意性流程图。
图5示出了本申请实施例提供的数据传输的方法的示意性流程图。
图6示出了本申请实施例提供的一个具体的QoS流数据传输的方法的示意性流程图。
图7示出了本申请实施例提供的一种数据传输的方法的示意性流程图。
图8示出了本申请实施例提供的一种通信装置的示意性框图。
图9示出了本申请实施例提供的另一种通信装置的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例中的技术方案可以应用于第五代(5th generation，5G)移动通信系统或未来演进的移动通信系统中。
图1示出了应用本申请实施例的无线接入网(radio access network，RAN)100的示意图。本申请实施例中，无线接入网中可以包括各种形式的基站，宏基站，微基站(也称为小站)，中继站，接入点，新无线控制器(new radio controller，NR controller)，集中式网元(centralized unit)，射频拉远模块，分布式网元(distributed unit)，发送接收点(transmission reception point，TRP)或传输点(transmission point，TP)，或者任何其它无线接入设备，但本申请实施例不限于此。其中，在采用不同的无线接入技术的系统中，具备无线接入功能的设备的名称可能会有所不同。例如，无线接入网设备可以是5G移动通信系统中的下一代基站(next generation NodeB，gNB)或未来移动通信系统中的基站。本申请的实施例对无线接入网所采用的具体技术和具体设备形态不做限定。
本申请实施例中的无线接入网用以为终端设备提供无线通信功能。这里，终端设备也可以称为终端(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。终端设备可以是V2X通信系统中装载在车上 的传感器、车载终端、无人驾驶(self driving)中的无线终端、运输安全(transportation safety)中的无线终端等等。本申请的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
在集中式单元CU与分布式单元分离的无线接入网架构中，集中式单元CU可以进一步分为一个集中式单元-控制面CU-CP和一个或多个分布式单元-用户面CU-UP。如图1所示，该无线接入网100包括一个CU-CP、多个CU-UP、多个分布式单元DU。其中，CU-UP、CU-CP、DU可以设置于不同的物理设备上，本申请实施例对此不作限定。
具体而言，一个DU只可以连接一个CU-CP，一个CU-UP只可以连接一个CU-CP，一个DU在同一个CU-CP的控制下可以连接到多个CU-UP，一个CU-UP在同一个CU-CP的控制下可以连接多个DU。其中，CU-CP和CU-UP之间会存在一个开放的接口：E1接口。CU-CP和CU-UP可以通过该E1接口进行通信。与此同时，CU-CP和CU-UP与DU都会有各自的接口，例如CU-CP与DU之间的接口为F1-C接口，CU-UP与DU之间的接口为F1-U接口。
本申请实施例中，CU-CP包括CU的控制面部分，包括RRC功能以及PDCP的控制面部分，例如用于处理信令无线承载(signal radio bearer，SRB)的数据。CU-UP包括CU的用户面部分，包括SDAP协议栈以及PDCP协议栈的数据面部分，例如用户处理数据无线承载(data radio bearer，DRB)的数据。DU包括RLC层、MAC层、PHY层。
图2示出了本申请实施例提供的数据传输的方法的示意性流程图。本申请实施例在CU-CP/CU-UP分离场景下，当CU-UP接收到服务质量QoS流数据时，可以向CU-CP发送该QoS流数据的相关信息，以通知该QoS流数据到达，使得CU-CP可以决定该QoS流数据到无线承载的映射方式。具体的，图2中的CU-CP和CU-UP可以参见图1中的描述，为避免重复，这里不再赘述。图2中的方法包括210和220。
210，CU-UP接收服务质量QoS流数据。
具体的，CU-UP可以从终端设备接收该QoS流数据，也可以从核心网接收该QoS数据。需要说明的是，本申请实施例中，当CU-UP从终端设备接收该QoS流数据时，数据传输的方向为上行方向，此时该QoS流数据可以称为上行QoS流数据。当CU-UP从核心网接收该QoS流数据时，数据传输的方向为下行方向，此时该QoS流数据可以称为下行QoS流数据。
本申请实施例中，该QoS流数据对应第一DRB，也就是说，该QoS流数据由第一DRB传递。例如，当数据传输方向为上行方向时，CU-UP接收服务质量QoS流数据，可以具体为，CU-UP通过第一DRB接收来自终端设备的所述QoS流数据，或者CU-UP接收由第一DRB传递的来自终端设备的所述QoS流数据。此时该QoS流数据是已经通过该第一DRB发送到CU-UP的数据。
当数据传输方向为下行方向时，CU-UP接收服务质量QoS流数据，可以替换为，CU-CP接收来自核心网的需要通过所述第一DRB传递的所述QoS流数据，或者CU-CP接收来自核心网，并将由第一DRB传递至终端设备的所述QoS流数据。此时，该QoS数据由核心网发送至CU-UP，并且CU-UP将要根据该QoS流数据与第一DRB的映射关系，将该QoS流数据映射到第一DRB上进行传递。
需要说明的是，这里接收到的QoS流数据可以包括一个QoS流数据，或包括多个QoS流数据，本申请实施例对此不作限定。
可选的，本申请实施例中，第一DRB为默认(default)DRB。具体的，对于每个PDU会话，网络设备会配置一个默认DRB，如果QoS flow数据包没有明确被RRC配置用于传输该QoS流到DRB的映射关系，也没有用反射QoS指示该QoS流到DRB的映射关系，则使用默认DRB传输该数据包。
220，CU-UP向CU-CP发送第一信息，所述第一信息包括所述QoS流数据的QoS流标识ID和PDU会话ID，所述PDU会话ID所对应的PDU会话包括所述QoS流数据。这里，QoS流标识ID的数量可以为一个或者多个。
本申请实施例中，当第一DRB为默认DRB时，CU-UP接收服务质量QoS流数据，并向 CU-CP发送该QoS流数据的QoS流ID和PDU会话ID，可以理解为：当CU-UP确定经由默认数据无线承载DRB传递的服务质量QoS流数据到达时，向CU-CP发送该QoS流数据的QoS流ID和PDU会话ID，以向CU-CP通知该服务质量QoS流数据经由默认DRB到达。
本申请实施例中，当第一DRB为专有DRB时，CU-UP接收服务质量QoS流数据，并向CU-CP发送该QoS流数据的QoS流ID和PDU会话ID，可以理解为：当CU-UP确定经由专有数据无线承载DRB传递的服务质量QoS流数据到达时，向CU-CP发送该QoS流数据的QoS流ID和PDU会话ID，以向CU-CP通知该服务质量QoS流数据经由专有DRB到达。
可选的，本申请实施例的一种实现方式中，第一信息中还可以包括第一DRB的DRB标识ID，即CU-UP可以告知CU-CP第一DRB的DRB ID。本申请的另一种实现方式中，第一信息中可以不包括第一DRB的DRB ID，即CU-UP可以不需要告知CU-CP第一DRB的DRB ID，只需要告知上述PDU会话下的QoS流ID列表即可，此时可以节省额外信令开销。
具体的，由于CU-CP在发送承载上下文建立请求(bearer context setup request)时，会明确指示与第一DRB对应的QoS流ID，因此，当CU-UP只向CU-CP通知PDU ID和该PDU会话下的QoS流ID时，CU-CP能够确定该QoS流对应的DRB，即第一DRB。一种可选的实施例，当CU-CP确定该QoS流数据由默认DRB传递，则可以确定第一DRB为默认DRB。
可选的，第一信息中可以包括辅助信息，该辅助信息包括所述QoS流或者第一DRB上的包传递性能统计，其中，包传递性能统计例如包括丢包率、重排序等待时间、包到达速率等中的至少一种。
可选的，当所述CU-UP从终端设备接收所述QoS流数据时，所述第一信息还包括上行指示；或者当所述CU-UP从核心网接收所述QoS流数据时，所述第一信息还包括下行指示。具体的，上行指示可以用于指示传输方向为上行，或者用于指示该QoS流数据为上行QoS流数据。下行指示可以用于指示传输方向为下行，或者用于指示该QoS流数据为下行QoS流数据。这时，CU-UP可以分别明确告知CU-CP，该QoS流数据为上行数据或者下行数据。
或者，可选的，CU-UP仅告知CU-CP QoS流数据到达，并不告诉CU-CP该QoS流数据为上行QoS流数据或下行QoS流数据，也就是说，此时CU-CP以及CU-UP并不需要区分该QoS流数据为上行数据还是下行数据。
对应的，CU-CP接收第一信息。
230，CU-CP使用所述第一信息。
具体的，CU-CP获取该第一信息中包括的信息，并根据其中包括的信息，确定QoS流数据到达。进一步的，CU-CP可以确定继续保持第一信息中包括的QoS流与第一DRB的映射关系不变，或者将该QoS流对应的该第一DRB变为第二DRB。
具体的，CU-CP可以根据当前数据传输的负载情况和QoS流数据的性能参数，确定是否改变该QoS流对应的DRB。作为举例，当第一DRB为默认DRB时，默认DRB的优先级程度最低，如果该QoS流数据包含用户数据，则应当具有更高的优先级，CU–CP认为则该默认DRB并不能满足该QoS流的性能参数的需求。此时CU-CP可以确定将该QoS流数据对应的默认DRB变为第二DRB。其中，第二DRB为专用DRB，其优先级程度高于默认DRB。
需要说明的是，QoS流的性能参数包括：5QI，优先级程度(priority level)，包延迟预算(packet delay budget)，丢包率(packet error rate),QoS流是否为延迟紧急(delay critical)等。
可选的，当CU-CP确定继续保持第一信息中包括的QoS流与第一DRB的映射关系不变，可以不执行其他操作。
可选的，240，本申请实施例中，当CU-CP确定将该QoS流对应的该第一DRB变为第二DRB之后，可以向CU-UP发送第二信息，该第二信息用于指示该QoS流从对应所述第一DRB变为对应第二DRB。
对应的，CU-UP接收第二信息，并根据第二信息，确定该QoS流对应于第二DRB。具 体的，后续CU-UP将从该第二DRB接收来自终端设备的该QoS流数据，或者CU-UP从核心网接收到该QoS流数据时，将该QoS流数据映射到第二DRB上进行传输。
可选的，本申请实施例中，当CU-CP确定将该QoS流对应的该第一DRB变为第二DRB之后，可以向DU发送该第二信息，使得DU可以获取该QoS流与第二DRB的映射关系，用于DU对用户设备进行第二DRB上下行调度。
可选的，本申请实施例中，当CU-CP确定将该QoS流对应的该第一DRB变为第二DRB之后，可以向终端设备发送该第二信息，使得终端设备可以获取该QoS流与第二DRB的映射关系，进一步的可以将该QoS流数据发送到第二DRB上进行传递，或者从该第二DRB上接收该QoS流数据。一种实现方式中，CU-CP可以向DU发送F1-C消息，该F1-C消息中封装由发送给终端设备的RRC消息，该RRC消息中可以包括该第二信息。
一种可能的实现方式中，终端设备在从第二DRB上接收到下行的该QoS数据流时，可以根据反射QoS方式，将上行的该QoS流数据发送在第二DRB上进行传输。
可选的，本申请实施例中，所述第二信息中可以包括所述第二DRB的DRB ID、所述QoS流ID，可选的，还可以包括所述QoS流的QoS参数。这里，QoS参数例如为5QI，优先级程度(priority level)，包延迟预算(packet delay budget)，丢包率(packet error rate),QoS流是否为延迟紧急(delay critical)等
可选的，本申请实施例中，第一DRB为默认DRB，第二DRB为专有(dedicated)DRB。具体的，所述第二DRB为现有的专有DRB或新建的专有DRB。
具体的，CU-CP可以通过向CU-UP、DU以及UE发送UE上下文修改消息的信令流程来建立专有DRB。具体的，建立该专有DRB的过程可以参见现有技术，这里不再描述。
可选的，本申请实施例中，第一DRB为专有DRB，第二DRB为另一专有(dedicated)DRB。具体的，所述第二DRB为现有的专有DRB或新建的专有DRB。
可选的，第二信息中可以包括上行指示或下行指示。具体的，上行指示以及下行指示可以参见上文中的描述，为避免重复，这里不再赘述。
因此，本申请实施例中，在CU-CP/CU-UP分离场景下，当CU-UP接收到服务质量QoS流数据时，可以向CU-CP发送该QoS流数据的QoS流标识ID和PDU会话ID，其中PDU会话ID所对应的PDU会话包括该QoS流数据，使得CU-CP可以决定该QoS流数据到无线承载的映射方式，从而满足了QoS流的传输性能参数，提升用户体验。
进一步地，当第一DRB为默认DRB时，CU-UP从默认DRB收到某一QoS flow数据时，CU-UP通知CU-CP该QoS flow数据到达，使得CU-CP为该QoS flow建立新的专有DRB，或者将该QoS flow数据映射到另一已有的专有DRB上，实现了QoS flow从默认DRB到专有DRB的重映射流程。
进一步地，当第一DRB为专有DRB时，CU-UP从专有DRB收到某一QoS flow数据时，CU-UP通知CU-CP该QoS flow数据到达，使得CU-CP为该QoS flow建立新的专有DRB，或者将该QoS flow数据映射到另一已有的专有DRB上，实现了QoS flow从专有DRB到另一专有DRB的重映射流程。
图3示出了本申请实施例提供的一个具体的QoS流数据传输的方法的示意性流程图。应理解，图3示出了QoS流数据传输的方法的步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其他操作或者图3中的各个操作的变形。此外，图3中的各个步骤可以按照与图3呈现的不同的顺序来执行，并且有可能并非要执行图3中的全部操作。
300，CU-UP触发建立承载上下文过程(Bearer context setup is triggered)。
在建立承载上下文之后，CU-UP从第一DRB收到UE的上行用户数据，或者从5G核心网(5GC)收到需映射到第一DRB的下行用户数据。可选的，第一DRB为默认DRB。
301，CU-UP向CU-CP发送第一信息，其中，第一信息包括步骤300中接收到的QoS流数据的QoS流标识ID和PDU会话ID，所述PDU会话ID所对应的PDU会话包括该QoS流数据。
可选的，第一信息中还可以包括第一DRB的DRB ID。
一种实现方式，CU-UP可以不区分上行UL或者下行DL方向，即CU-UP告知CU-CP接收到的QoS流数据所述的PDU会话ID、接收到的QoS流数据的QoS流ID。
另一种实现方式，CU-UP可以区分上行UL、下行DL方向，即CU-UP告知CU-CP接收到的QoS流数据所述的PDU会话ID、接收到的QoS流数据的QoS流ID，还可以告知该QoS流数据为上行QoS流或下行QoS流。
作为示例，第一信息可以承载于数据通知(data notification)消息，或者承载上下文去激活修改(bearer context inactivity notification)消息，或者承载于承载上下文修改要求(bearer context modification required)消息，或者其他E1AP消息，本申请实施例对此不作限定。
具体的，第一信息可以参见图2中的描述，为避免重复，这里不再赘述。
可选的，302，CU-CP向CU-UP发送第二信息，所述第二信息用于指示所述QoS流数据从对应第一DRB变为对应第二DRB。具体的，第二信息可以参见上文中的描述，为避免重复，这里不再赘述。
具体的，CU-CP收到第一信息后，使用该第一信息控制QoS流数据的传输。具体的，CU-CP可以决定维持第一消息中包括的QoS流与DRB的映射关系不变，或者决定将所述QoS流从对应第一DRB变为对应第二DRB。这里，第二DRB可以为新建的专有DRB，或者已经建立好的现有的专有DRB。当CU-CP决定将所述QoS流从对应第一DRB变为对应第二DRB时，向CU-UP发送该第二信息。
作为示例，CU-CP可以向CU-UP发送承载上下文修改请求，其中包括第二信息。
一种实现方式中，第二信息可以包括QoS流与第二DRB的映射关系。具体的，第二信息可以包括：第二DRB的DRB ID、QoS流ID以及QoS流的QoS参数。
可选的，303，CU-UP与CU-CP之间交互发送承载上下文修改请求(bearer context modification request)/承载上下文修改响应(bearer context modification response)。
一种可能的实施例，CU-UP可以向CU-CP发送上述数据通知消息。可选的，该数据通知消息包括第一信息。CU-CP可以决定是否向CU-UP发送承载上下文修改请求(bearer context modification request)。可选的，该承载上下文修改请求中可以包括第二信息。
一种可能的实施例，CU-UP向CU-CP发送承载上下文修改要求(bearer context modification required)。可选的，该承载上下文修改要求中可以包括第一信息。对应的，CU-CP向CU-UP发送承载上下文修改确认(bearer context modification confirm)。可选的，CU-CP可以向CU-UP发送承载上下文修改请求，该承载上下文修改请求中可以包括第二信息。然后，CU-UP可以向CU-CP回复承载上下文修改响应。
304，CU-CP向DU发送UE上下文修改请求(UE context modification request)，其中可以包括第二信息。具体的，第二信息可以包括：第二DRB的DRB ID、QoS流ID或者QoS流的QoS参数。对应的，DU向CU-CP发送UE上下文修改响应(UE context modification response)。其中，UE上下文修改响应中还可以包括DU的传输网络层(transport network layer,TNL)地址，和/或分组数据汇聚协议(packet data convergence protocol，PDCP)状态。
305，CU-CP向CU-UP发送承载上下文修改请求。响应于该承载上下文修改请求，CU-UP向CU-CP发送承载上下文修改响应。其中，该承载上下文修改请求中可以包括DU的TNL传输层地址，和/或PDCP状态。
306，CU-CP向UE发送RRC连接重配置消息，该连接重配置消息中可以包括第二信息，用于UE更新QoS flow到DRB映射关系。
需要说明的是，对于映射到默认DRB内的QoS flow，仅仅当首次属于QoS flow的数据包到达时，CU-UP通知CU-CP。对于已经发送过第一信息的QoS flow，CU-UP将不会提醒CU-CP后续该QoS flow数据到达。当后续该QoS flow到达时，CU-UP根据CU-CP发送 的该QoS flow的QoS flow ID与第二DRB的映射关系，将该QoS flow映射到第二DRB上。
因此，本申请实施例中，在CU-CP/CU-UP分离场景下，当CU-UP接收到服务质量QoS流数据时，可以向CU-CP发送该QoS流数据的QoS流标识ID和PDU会话ID，其中PDU会话ID所对应的PDU会话包括该QoS流数据，使得CU-CP可以控制该QoS流数据的传输，从而满足了QoS flow的性能参数，提升用户体验。
进一步地，当第一DRB为默认DRB时，CU-UP从默认DRB收到某一QoS flow数据时，CU-UP通知CU-CP该QoS flow数据到达，使得CU-CP为该QoS flow建立新的专有DRB，或者将该QoS flow数据映射到另一已有的专有DRB上，实现了QoS flow从默认DRB到专有DRB的重映射流程。
进一步地，当第一DRB为专有DRB时，CU-UP从专有DRB收到某一QoS flow数据时，CU-UP通知CU-CP该QoS flow数据到达，使得CU-CP为该QoS flow建立新的专有DRB，或者将该QoS flow数据映射到另一已有的专有DRB上，实现了QoS flow从专有DRB到另一专有DRB的重映射流程。
图4和图5分别示出了本申请实施例提供的数据传输的方法的示意性流程图。图4中在CU-CP/CU-UP分离的场景下，CU-CP可以决定非对称QoS flow到DRB映射关系，然后将该非对称映射关系通知给CU-UP和DU，图5在CU-DU分离的场景下，CU决定非对称向QoS flow到DRB映射关系，然后将该非对称映射关系通知给DU。具体的，图4中的CU、CU-CP、CU-UP、DU和图5中的CU-DU可以参见图1中的描述，为避免重复，这里不再赘述。
具体的，图4中的传输数据的方法包括410至440。应理解，图4示出了数据传输的方法的步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其他操作或者图4中的各个操作的变形。此外，图4中的各个步骤可以按照与图4呈现的不同的顺序来执行，并且有可能并非要执行图4中的全部操作。
410，CU-CP确定服务质量QoS流与DRB的映射关系，所述映射关系包括以下至少一个：上行QoS流与DRB的映射关系、下行QoS流与DRB的映射关系或双向QoS流与DRB的映射关系。
具体的，上行QoS流与DRB的映射关系指的是：上行传输的QoS流数据与传输该上行QoS流数据的DRB的映射关系；下行QoS流与DRB的映射关系指的是：下行传输的QoS流数据与传输该下行QoS流数据的DRB的映射关系；双向QoS流与DRB的映射关系指的是：QoS流数据和传输该QoS流数据的DRB的映射关系，其中该QoS流数据即包括上行，也包括上行。
由此可知，当映射关系包括上行QoS流与DRB的映射关系和/或下行QoS流与DRB的映射关系时，QoS流到DRB的映射关系是不对称的。也就是说，本申请实施例中，上行QoS流与DRB的映射关系与下行QoS流与DRB的映射关系解耦，上行QoS流与DRB的映射关系与下行QoS流与DRB的映射关系可以相同，或者不同，本申请实施例对此不作限定。例如，上行QoS流ID#1可以映射到DRB#1，下行QoS流ID#1可以映射到DRB#2。
本申请实施例中，当映射关系包括双向QoS流与DRB的映射关系时，QoS流到DRB的映射关系是对称的，也就是说，此时上行QoS流与DRB的映射关系与下行QoS流与DRB的映射关系相同。例如，QoS流ID#1可以映射到DRB#1，此时表示上行QoS流ID#1和下行QoS流ID#1均映射到DRB#1。
420，CU-CP向CU-UP发送第三信息，该第三信息中包括410中的QoS流与DRB的映射关系。
可选的，本申请实施例中，第三信息中还可以包括映射指示(mapping indication)，用于指示映射到DRB中的QoS流中的数据为上行数据或下行数据(indication whether the UL data or DL data of one QoS flow map to this DRB)，或者指示映射到DRB中的QoS流中的数据为上行数据和下行数据。
可选的，本申请实施例中，第三信息中还可以包括非对称映射指示(mapping indication)，用于指示映射到DRB中的QoS流中的数据为上行数据或下行数据(indication whether the UL data or DL data of one QoS flow map to this DRB)。
具体而言，当所述映射关系包括上行QoS流与DRB的映射关系时，该非对称映射指示用于指示该映射关系为上行QoS流与DRB的映射关系，此时，该非对称映射指示也可以称为上行指示。当所述映射关系包括下行QoS流与DRB的映射关系时，该非对称映射指示用于指示该映射关系为下行QoS流与DRB的映射关系，此时，该非对称映射指示也可以称为下行指示。当所述映射关系包括双向QoS流与DRB的映射关系时，该非对称映射指示用于指示该映射关系为双向QoS流与DRB的映射关系，此时，该非对称映射指示也可以称为双向指示。这样，CU-CP可以显式指示CU-UP映射关系中QoS流为上行QoS流，或者下行QoS流，或者双向QoS流。
作为示例，第三信息可以为如下表1的格式：
表1
Figure PCTCN2019099054-appb-000001
其中，QFI表示QoS流ID。具体的，DRB ID、QFI、QFI方向以及QoS参数可以根据具体的场景进行填入表1中。这里QFI方向具体可以为上述非对称映射指示。
可选的，本申请实施中，CU-CP也可以隐式指示CU-UP映射关系中QoS流为上行QoS流，或者下行QoS流，或者双向QoS流。作为示例，第三信息中可以包含QoS flow#1的保障流比特速率GFBR或最大流比特速率MFBR。具体而言，若QoS flow#1的上行保障流比特速率GFBR或最大流比特速率MFBR大于零，且下行GFBR或MFBR等于零，则所述QoS flow#1为上行QoS流；若所述QoS flow#1的下行GFBR或MFBR大于零，且上行GFBR或MFBR等于零，则所述QoS flow#1为下行QoS流；若QoS flow#1的下行GFBR或MFBR大于零，且上行GFBR或MFBR大于零，则所述QoS flow#1为双向QoS流。
一种具体的实现方式中，CU-CP可以向所述CU-UP发送承载上下文建立请求或承载上下文修改请求，该承载上下文建立请求或承载上下文修改请求中可以包括第三信息。
对应的，CU-UP可以从CU-CP接收第三信息，并使用该第三信息。
具体的，CU-UP收到第三信息后，记录该第三信息所指示的映射关系。当CU-UP收到核心网发送的下行QoS流数据时，可以根据第三信息所指示的下行QoS流ID与DRB的映射关系，将该下行QoS流数据映射到对应的DRB上传递给DU。
当CU-UP收到终端设备发送的上行QoS流数据时，可以根据第三信息所指示的上行QoS流ID与DRB的映射关系，验证该上行QoS流数据是否在对应的DRB上进行传输。
另外，如果后续CU-CP对该第三信息所指示的上行QoS流数据进行了重映射操作，例如将该上行QoS流从DRB#1重映射到DRB#3时，CU-UP将会等待从DRB#1上收到该上行QoS流数据的end marker数据包，确定从DRB#1上收到了该上行QoS流数据的最后一个数据包。并且，CU-UP将会从DRB#3上接收该上行QoS流数据。之后，CU-UP将该全部的上行QoS流数据发送给核心网。
430，CU-CP向DU发送第三信息，该第三信息中包括410中的QoS流与DRB的映射关系。
一种可能的实现方式中，CU-CP可以向所述DU发送用户设备UE上下文建立请求或UE 上下文修改请求，该UE上下文建立请求或UE上下文修改请求中包括第三信息。
具体的，第三信息可以参见420中的描述，为避免重复，这里不再赘述。
对应的，DU接收第三信息。
440，DU使用该第三信息。
具体的，DU收到第三信息后，记录该第三信息所指示的映射关系。对于第三信息所指示的上行QoS流和/或下行QoS流所对应的QoS流，分别决定其媒体介入控制(media access control，MAC)层、无线链路控制(radio link control，RLC)层的配置参数。一种可能的实现方式中，DU根据DRB内的的QoS流，在MAC层分别进行上行、下行调度。
因此，本申请实施例中，CU-CP决定非对称向QoS flow到DRB映射关系，CU-UP将该非对称映射关系通知给CU-UP和DU，能够实现了灵活的上行QoS flow映射和下行QoS flow映射，实现了上行QoS流和下行QoS流映射关系的解耦。这样，一方面能够分别保障QoS流的上行传输和下行传输的需求(其上行传输、下行传输的保障比特速率、最大比特速率不同)，另一方面网络可以根据上行/下行的网络负载、干扰情况、QoS流参数特征等，灵活配置QoS流的上行和下行映射，进一步提升了用户体验。
具体的，图5中的传输数据的方法包括510至530。应理解，图5示出了数据传输的方法的步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其他操作或者图5中的各个操作的变形。此外，图5中的各个步骤可以按照与图5呈现的不同的顺序来执行，并且有可能并非要执行图5中的全部操作。
510，CU确定服务质量QoS流与DRB的映射关系，所述映射关系包括以下至少一个：上行QoS流与DRB的映射关系、下行QoS流与DRB的映射关系或双向QoS流与DRB的映射关系。
具体的，QoS流与DRB的映射关系可以参见图4中410中的描述，为避免重复，这里不再赘述。
520，CU向DU发送第三信息，该第三信息中包括410中的QoS流与DRB的映射关系。对应的，DU从CU接收该第三信息。具体的，第三信息可以参见图4中420、430中的描述，为避免重复，这里不再赘述。
530，DU使用第三信息。
具体的，530可以参见图4中440中的描述，为避免重复，这里不再赘述。
因此，本申请实施例中，CU决定非对称向QoS flow到DRB映射关系，并将该非对称映射关系通知给DU，能够实现了灵活的上行QoS flow映射和下行QoS flow映射，实现了上行QoS流和下行QoS流映射关系的解耦。这样，一方面能够分别保障QoS流的上行传输和下行传输的需求(其上行传输、下行传输的保障比特速率、最大比特速率不同)，另一方面网络可以根据上行/下行的网络负载、干扰情况、QoS流参数特征等，灵活配置QoS流的上行和下行映射，进一步提升了用户体验。
图6示出了本申请实施例提供的一个具体的QoS流数据传输的方法的示意性流程图。应理解，图6示出了QoS流数据传输的方法的步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其他操作或者图6中的各个操作的变形。此外，图6中的各个步骤可以按照与图6呈现的不同的顺序来执行，并且有可能并非要执行图6中的全部操作。这里，CU-CP、CU-UP、DU可以参见图1中的描述，为避免重复，这里不再赘述。
600，CU-CP决定触发承载上下文过程(bearer context setup is triggered)。
601，CU-CP向CU-UP发送承载上下文建立请求(bearer context setup request)，其中包括第三信息。
602，响应承载上下文建立请求，CU-UP向CU-CP发送承载上下文建立响应(bearer context setup request response)。
603：CU-CP与DU进行UE上下文建立(UE context setup)过程，具体的，CU-CP向DU发送UE上下文建立请求，该UE上下文建立请求中包括第三信息。响应于该UE上下文 建立请求，DU可以向CU-UP发送上下文建立响应。具体的，CU-CP与DU之间通过F1-C接口进行通信。
604，CU-CP向CU-UP发送承载上下文修改请求(bearer context modification request)。
605，响应于CU-CP发送的承载上下文修改请求，CU-UP向CU-CP发送承载上下文修改响应(bearer context modification response)。
因此，本申请实施例中，CU-CP决定非对称向QoS flow到DRB映射关系，然后将该非对称映射关系通知给CU-UP和DU，能够实现了灵活的上行QoS流映射和下行QoS流映射，实现了上行QoS流和下行QoS流映射关系的解耦。这样，一方面能够分别保障QoS流的上行传输和下行传输的需求(其上行传输、下行传输的保障比特速率、最大比特速率不同)，另一方面网络可以根据上行/下行的网络负载、干扰情况、QoS流参数特征等，灵活配置QoS流的上行和下行映射，进一步提升了用户体验。
图7示出了本申请实施例提供的一种数据传输的方法的示意性流程图。图7中接入网设备可根据确定QoS流的方向，并可以对该QoS流的上行传输和下行传输进行独立配置。具体的，图7中的CU、CU-CP可以参见图1中的描述，为避免重复，这里不再赘述。
710，核心网CN确定QoS流的方向。
具体而言，本申请实施例中可以存在一些QoS流仅具有单向特性，即仅为上行QoS流，或仅为下行QoS流，也可以存在一些QoS流具有双向特性，即该QoS流可以为上行QoS流，也可以为上行QoS流。本申请实施例中，核心网CN，例如核心网中的接入和移动性管理功能(access and mobility management function，AMF)网元可以确定QoS流的方向特性。
720，核心网向RAN发送第四信息。
具体的，核心网可以通过第四信息通知无线接入网RAN(例如CU-CP，或CU)某个QoS流的方向特性，例如该QoS流为上行QoS流，下行QoS流或者双向QoS流。
一种可能的实现方式，该第四信息包括：PDU会话(session)ID、QoS流ID、QoS流ID对应的QoS流的方向特性，这里方向特性例如为上行、下行或者双向。
另外，当QoS流为上行时，第四信息中还可以包括该QoS流的上行QoS参数，其中上行QoS参数为该QoS流在上行传输时所配置的QoS参数。当QoS流为下行时，第四信息中还可以包括该QoS流的下行QoS参数，其中下行QoS参数为该QoS流在下行传输时所配置的QoS参数。当QoS流为双向时，第四信息中还可以包括该QoS flow的UL QoS参数和DL QoS参数。
作为示例，第四信息可以为如下表2的格式：。
表2
Figure PCTCN2019099054-appb-000002
其中，QFI表示QoS流ID，会话ID表示PDU会话ID。具体的，会话ID、QFI、QFI方向以及QoS参数可以根据具体的场景进行填入表2中。
一种可能的实现方式中，AMF可以向RAN发送PDU会话资源建立请求(PDU session resource setup request)，该PDU会话资源建立请求中可以包括第四信息。响应于该PDU 会话资源建立请求，RAN可以向AFM发送PDU会话资源建立响应(PDU session resource setup response)。
对应的，RAN接收该第四信息。
730，RAN使用第四信息。
具体的，RAN获取该第四信息中包括的信息，并根据其中包括的信息，确定QoS流的方向特性。并且，在CU-CP分离的场景下，当CU-CP确定QoS流的方向特性后，CU-CP可以分别告知CU-UP和DU该QoS流的方向特性。
因此，本申请实施例中，接入网设备可根据确定QoS流的方向，并可以对该QoS流的上行传输和下行传输进行独立配置。具体而言，若该QoS流仅为上行QoS流，则接入网设备决定该QoS流的上行数据包的调度策略，而不用考虑下行传输；若该QoS流仅为下行QoS流，则接入网设备决定该QoS流的下行数据包的调度策略，而不用考虑上行传输。因此本申请实施例能够满足QoS流的特定需求。
上述结合图2至图7主要从不同设备之间交互的角度对本申请实施例提供的方案进行了介绍。下面将结合图8和图9描述执行本申请实施例提供的方案的设备。可以理解的是，CU、CU-CP、CU-UP、DU、CN为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本申请中所公开的实施例描述的各示例的单元及算法步骤，本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的技术方案的范围。
本申请实施例可以根据上述方法示例对CU、CU-CP、CU-UP、DU、CN等进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，图8示出了本申请实施例中所涉及的一种通信装置的一种可能的示例性框图，该装置800可以以软件、硬件或软硬结合的形式存在。图8示出了本申请实施例中所涉及的装置的一种可能的示意性框图。装置800包括：处理单元802和通信单元803。处理单元802用于对装置的动作进行控制管理。通信单元803用于支持装置与其他设备的通信。装置还可以包括存储单元801，用于存储装置的程序代码和数据。
图8所示的装置800可以是本申请实施例所涉及的CU、CU-CP、CU-UP、DU、CN。
当图8所示的装置800为CU时，处理单元802能够支持装置800执行上述各方法示例中由CU完成的动作，例如，处理单元802支持装置800执行例如图5中510，图7中730，和/或用于本文所描述的技术的其它过程。通信单元803能够支持装置800与DU、CN等之间的通信，例如，通信单元803支持装置800执行图5中的步520，图7中的720，和/或其他相关的通信过程。
当图8所示的装置800为CU-CP时，处理单元802能够支持装置800执行上述各方法示例中由CU-CP完成的动作，例如，处理单元802支持装置800执行例如图2中230，图3中的300，图4中410，图6中500，图7中730，和/或用于本文所描述的技术的其它过程。通信单元803能够支持装置800与CU-UP、DU、CN等之间的通信，例如，通信单元803支持装置800执行图2中的步220，240，图3中的301至306，图4中的420,430，图6中的601至605，图7中的720，和/或其他相关的通信过程。
当图8所示的装置800为CU-UP时，处理单元802能够支持装置800执行上述各方法示例中由CU-UP完成的动作，例如，处理单元802支持装置800执行例如图2中210，和/或用于本文所描述的技术的其它过程。通信单元803能够支持装置800与CU-UP、DU、CN等之间的通信，例如，通信单元803支持装置800执行图2中的步220，240，图3中 的301至303，以及305，图4中的420，图6中的601，602，604，605，和/或其他相关的通信过程。
当图8所示的装置800为CU-UP时，处理单元802能够支持装置800执行上述各方法示例中由CU-UP完成的动作，例如，处理单元802支持装置800执行例如图2中210，和/或用于本文所描述的技术的其它过程。通信单元803能够支持装置800与CU-UP、DU、CN等之间的通信，例如，通信单元803支持装置800执行图2中的步220，240，图3中的301至303，以及305，图4中的420，图6中的601，602，604，605，和/或其他相关的通信过程。
当图8所示的装置800为DU时，处理单元802能够支持装置800执行上述各方法示例中由DU完成的动作，例如，处理单元802支持装置800执行例如图4中440，图5中530，和/或用于本文所描述的技术的其它过程。通信单元803能够支持装置800与CU-CP、CU-UP、CN终端设备等之间的通信，例如，通信单元803支持装置800执行图3中的304，图4中的430，图5中的520，图6中的603，和/或其他相关的通信过程。
当图8所示的装置800为CN时，处理单元802能够支持装置800执行上述各方法示例中由CN完成的动作，例如，处理单元802支持装置800执行例如图7中710，和/或用于本文所描述的技术的其它过程。通信单元803能够支持装置800与CU-CP、CU等之间的通信，例如，通信单元803支持装置800执行图7中的720，和/或其他相关的通信过程。
示例性地，处理单元802可以是处理器或控制器，例如可以是中央处理器(central processing unit，CPU)，通用处理器，数字信号处理器(digital signal processor，DSP)，专用集成电路(application-specific integrated circuit，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，单元和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元803可以是通信接口，该通信接口是统称，在具体实现中，该通信接口可以包括一个或多个接口。存储单元801可以是存储器。
当处理单元802为处理器，通信单元803为通信接口，存储单元801为存储器时，本申请实施例所涉及的装置800可以为图9所示的通信装置900。
参阅图9所示，该装置900包括：处理器902和通信接口903。进一步地，该装置900还可以包括存储器901。可选的，装置900还可以包括总线904。其中，通信接口903、处理器902以及存储器901可以通过总线904相互连接；总线904可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。所述总线904可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
其中，处理器902可以通过运行或执行存储在存储器901内的程序，执行所述装置900的各种功能。
示例性地，图9所示的通信装置900可以是本申请实施例所涉及的CU、CU-CP、CU-UP、DU、CN。
当装置900为CU时，处理器902可以通过运行或执行存储在存储器901内的程序，执行上述各方法示例中由CU完成的动作。当装置900为CU-CP时，处理器902可以通过运行或执行存储在存储器901内的程序，执行上述各方法示例中由CU-CP完成的动作。当装置900为CU-UP时，处理器902可以通过运行或执行存储在存储器901内的程序，执行上述各方法示例中由CU-UP完成的动作。当装置900为DU时，处理器902可以通过运行或执行存储在存储器901内的程序，执行上述各方法示例中由DU完成的动作。当装置900为CN时，处理器902可以通过运行或执行存储在存储器901内的程序，执行上述各方法 示例中由CN完成的动作。
作为本实施例的另一种形式，提供一种计算机可读存储介质，其上存储有指令，该指令被执行时执行上述方法实施例中的方法。
作为本实施例的另一种形式，提供一种包含指令的计算机程序产品，该指令被执行时执行上述方法实施例中的方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本发明的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。应理解，在本发明的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
还应理解，本文中涉及的第一、第二以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本 申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (58)

  1. 一种数据传输的方法，其特征在于，包括：
    无线接入网的分布式单元DU从集中式单元CU接收信息，所述信息包括服务质量QoS流与数据无线承载DRB的映射关系，其中，所述映射关系包括以下至少一个：上行QoS流与DRB的映射关系或下行QoS流与DRB的映射关系；
    所述DU使用所述信息。
  2. 如权利要求1所述的数据传输的方法，其特征在于，所述信息用于指示映射到DRB中的QoS流中的数据为上行数据或下行数据。
  3. 如权利要求1所述的数据传输的方法，其特征在于，当所述映射关系包括上行QoS流与DRB的映射关系时，所述信息中还包括上行指示。
  4. 如权利要求1所述的数据传输的方法，其特征在于，当所述映射关系包括下行QoS流与DRB的映射关系时，所述信息中还包括下行指示。
  5. 如权利要求1-4任一所述的数据传输的方法，其特征在于，
    所述CU包括分离的集中式单元-用户面CU-UP和集中式单元-控制面CU-CP，其中，所述无线接入网中的分布式单元DU从CU接收信息，包括：
    所述DU从所述CU-CP接收所述信息。
  6. 如权利要求5所述的数据传输的方法，其特征在于，所述DU从所述CU-CP接收所述信息，包括：
    所述DU从所述CU-CP接收用户设备UE上下文建立请求，所述UE上下文建立请求中包括所述信息。
  7. 如权利要求5所述的数据传输的方法，其特征在于，所述DU从所述CU-CP接收所述信息，包括：
    所述DU从所述CU-CP接收用户设备UE上下文修改请求，所述UE上下文修改请求中包括所述信息。
  8. 如权利要求1-5任一所述的数据传输的方法，其特征在于，所述DU从所述CU接收所述信息，包括：
    所述DU从所述CU接收用户设备UE上下文建立请求，所述UE上下文建立请求中包括所述信息。
  9. 如权利要求1-5任一所述的数据传输的方法，其特征在于，所述DU从所述CU接收所述信息，包括：
    所述DU从所述CU接收用户设备UE上下文修改请求，所述UE上下文修改请求中包括所述信息。
  10. 一种数据传输的方法，其特征在于，包括：
    无线接入网的集中式单元CU向DU发送UE上下文建立请求，所述UE上下文建立请求中包括信息，所述信息包括QoS流与DRB的映射关系，其中，所述映射关系包括以下至少一个：上行QoS流与DRB的映射关系或下行QoS流与DRB的映射关系；
    所述CU接收来自DU的上下文建立响应。
  11. 如权利要求10所述的数据传输的方法，其特征在于，所述信息用于指示映射到DRB中的QoS流中的数据为上行数据或下行数据。
  12. 如权利要求10所述的数据传输的方法，其特征在于，当所述映射关系包括上行QoS流与DRB的映射关系时，所述信息中还包括上行指示。
  13. 如权利要求10所述的数据传输的方法，其特征在于，当所述映射关系包括下行QoS流与DRB的映射关系时，所述信息中还包括下行指示。
  14. 如权利要求10-13任一所述的数据传输的方法，其特征在于，
    所述CU包括分离的集中式单元-用户面CU-UP和集中式单元-控制面CU-CP，其中，所述CU向所述DU发送UE上下文建立请求，包括：
    所述CU-CP向所述DU发送所述UE上下文建立请求。
  15. 如权利要求14所述的数据传输的方法，其特征在于，所述方法还包括，
    所述CU-CP向所述CU-UP发送承载上下文建立请求，所述承载上下文建立请求包括所述信息；所述CU-CP接收来自所述CU-UP的承载上下文建立响应。
  16. 如权利要求14或15所述的数据传输的方法，其特征在于，所述方法还包括，
    所述CU-CP向所述CU-UP发送承载上下文修改请求，所述承载上下文修改请求包括所述信息；所述CU-CP接收来自所述CU-UP的承载上下文修改响应。
  17. 一种通信装置，其特征在于，包括：
    接收单元，用于从集中式单元CU接收信息，所述信息包括服务质量QoS流与数据无线承载DRB的映射关系，其中，所述映射关系包括以下至少一个：上行QoS流与DRB的映射关系或下行QoS流与DRB的映射关系；
    处理单元，用于使用所述信息。
  18. 如权利要求17所述的通信装置，其特征在于，所述信息用于指示映射到DRB中的QoS流中的数据为上行数据或下行数据。
  19. 如权利要求17所述的通信装置，其特征在于，当所述映射关系包括上行QoS流与DRB的映射关系时，所述信息中还包括上行指示。
  20. 如权利要求17所述的通信装置，其特征在于，当所述映射关系包括下行QoS流与DRB的映射关系时，所述信息中还包括下行指示。
  21. 如权利要求17-20任一所述的通信装置，其特征在于，
    所述CU包括分离的集中式单元-用户面CU-UP和集中式单元-控制面CU-CP，其中，所述接收单元，用于从所述CU-CP接收所述信息。
  22. 如权利要求21所述的通信装置，其特征在于，所述接收单元，用于从所述CU-CP接收用户设备UE上下文建立请求，所述UE上下文建立请求中包括所述信息。
  23. 如权利要求21所述的通信装置，其特征在于，所述接收单元，用于从所述CU-CP接收用户设备UE上下文修改请求，所述UE上下文修改请求中包括所述信息。
  24. 如权利要求17-20任一所述的通信装置，其特征在于，所述接收单元，用于从所述CU接收用户设备UE上下文建立请求，所述UE上下文建立请求中包括所述信息。
  25. 如权利要求17-20任一所述的通信装置，其特征在于，所述接收单元，用于从所述CU接收用户设备UE上下文修改请求，所述UE上下文修改请求中包括所述信息。
  26. 一种通信装置，其特征在于，包括：
    发送单元，用于向DU发送UE上下文建立请求，所述UE上下文建立请求中包括信息，所述信息包括QoS流与DRB的映射关系，其中，所述映射关系包括以下至少一个：上 行QoS流与DRB的映射关系或下行QoS流与DRB的映射关系；
    接收单元，用于接收来自DU的上下文建立响应。
  27. 如权利要求26所述的通信装置，其特征在于，所述信息用于指示映射到DRB中的QoS流中的数据为上行数据或下行数据。
  28. 如权利要求26所述的通信装置，其特征在于，当所述映射关系包括上行QoS流与DRB的映射关系时，所述信息中还包括上行指示。
  29. 如权利要求26所述的通信装置，其特征在于，当所述映射关系包括下行QoS流与DRB的映射关系时，所述信息中还包括下行指示。
  30. 如权利要求26-29任一所述的通信装置，其特征在于，所述通信装置是集中式单元-控制面CU-CP实体。
  31. 如权利要求30所述的通信装置，其特征在于，
    所述发送单元还用于向所述CU-UP发送承载上下文建立请求，所述承载上下文建立请求包括所述信息；
    所述接收单元还用于接收来自所述CU-UP的承载上下文建立响应。
  32. 如权利要求30或31所述的通信装置，其特征在于，
    所述发送单元还用于向所述CU-UP发送承载上下文修改请求，所述承载上下文修改请求包括所述信息；
    所述接收单元还用于接收来自所述CU-UP的承载上下文修改响应。
  33. 一种数据传输的方法，其特征在于，所述方法包括：
    无线接入网RAN的集中式单元-用户面CU-UP接收服务质量QoS流数据；
    所述CU-UP向所述无线接入网RAN集中式单元-控制面CU-CP发送第一信息，其中，所述第一信息包括所述QoS流数据的QoS流标识ID和PDU会话ID，所述PDU会话ID所对应的PDU会话包括所述QoS流数据。
  34. 根据权利要求33所述的方法，其特征在于，所述QoS流数据对应第一数据无线承载DRB，其中，所述无线接入网集中式单元-用户面CU-UP接收服务质量QoS流数据，包括：
    所述CU-UP通过所述第一DRB接收来自终端设备所述QoS流数据。
  35. 根据权利要求34所述的方法，其特征在于，还包括：
    所述CU-UP接收来自所述CU-CP的第二信息，所述第二信息用于指示所述QoS流数据从对应所述第一DRB变为对应第二DRB。
  36. 根据权利要求35所述的方法，其特征在于，所述第一DRB为默认DRB，所述第二DRB为专有DRB。
  37. 根据权利要求34所述的方法，其特征在于，所述第一DRB为默认DRB，所述QoS流数据没有被无线资源控制RRC配置用于传输该所述QoS流到DRB的映射关系，也没有用反射QoS指示所述QoS流到DRB的映射关系。
  38. 根据权利要求33-37任一所述的方法，其特征在于，所述CU-UP接收所述QoS流数据，包括所述CU-UP首次接收属于所述QoS流的数据包。
  39. 根据权利要求33-38中任一所述的方法，其特征在于，所述CU-UP向所述CU-CP发送所述第一信息，包括：所述CU-UP通过数据通知消息向所述CU-CP发送所述第一 信息。
  40. 一种数据传输的方法，其特征在于，所述方法包括：
    无线接入网RAN集中式单元的控制面CU-CP从无线接入网集中式单元用户面CU-UP接收第一信息，其中，所述第一信息包括QoS流数据的QoS流标识ID和PDU会话ID，所述PDU会话ID所对应的PDU会话包括所述QoS流数据；
    所述CU-CP使用所述第一信息。
  41. 根据权利要求40所述的方法，其特征在于，还包括：
    所述CU-CP向所述CU-UP发送第二信息，所述第二信息用于指示所述QoS流数据从对应第一DRB变为对应第二DRB。
  42. 根据权利要求40所述的方法，其特征在于，所述第一DRB为默认DRB，所述第二DRB为专有DRB。
  43. 根据权利要求42所述的方法，其特征在于，所述第一DRB为默认DRB，所述QoS流数据没有被无线资源控制RRC配置用于传输该所述QoS流到DRB的映射关系，也没有用反射QoS指示所述QoS流到DRB的映射关系。
  44. 一种通信装置，其特征在于，包括：
    接收单元，用于接收服务质量QoS流数据；
    发送单元，用于向所述无线接入网RAN集中式单元-控制面CU-CP发送第一信息，其中，所述第一信息包括所述QoS流数据的QoS流标识ID和PDU会话ID，所述PDU会话ID所对应的PDU会话包括所述QoS流数据。
  45. 根据权利要求44所述的装置，其特征在于，所述QoS流数据对应第一数据无线承载DRB，其中，所述接收单元具体用于：
    通过所述第一DRB接收来自终端设备所述QoS流数据。
  46. 根据权利要求45所述的装置，其特征在于，所述接收单元还用于：
    接收来自所述CU-CP的第二信息，所述第二信息用于指示所述QoS流数据从对应所述第一DRB变为对应第二DRB。
  47. 根据权利要求46所述的装置，其特征在于，所述第一DRB为默认DRB，所述第二DRB为专有DRB。
  48. 根据权利要求45所述的装置，其特征在于，所述第一DRB为默认DRB，所述QoS流数据没有被无线资源控制RRC配置用于传输该所述QoS流到DRB的映射关系，也没有用反射QoS指示所述QoS流到DRB的映射关系。
  49. 根据权利要求44-48任一所述的装置，其特征在于，
    所述CU-UP接收所述QoS流数据，包括所述CU-UP首次接收属于所述QoS流的数据包。
  50. 根据权利要求44-49中任一所述的装置，其特征在于，所述CU-UP向所述CU-CP发送所述第一信息，包括：所述CU-UP通过数据通知消息向所述CU-CP发送所述第一信息。
  51. 一种通信装置，其特征在于，包括：
    接收单元，用于从无线接入网集中式单元用户面CU-UP接收第一信息，其中，所述第一信息包括QoS流数据的QoS流标识ID和PDU会话ID，所述PDU会话ID所对应的PDU会话包括所述QoS流数据；
    处理单元，用于使用所述第一信息。
  52. 根据权利要求51所述的装置，其特征在于，还包括：
    发送单元，用于向所述CU-UP发送第二信息，所述第二信息用于指示所述QoS流数据从对应第一DRB变为对应第二DRB。
  53. 根据权利要求52所述的装置，其特征在于，所述第一DRB为默认DRB，所述第二DRB为专有DRB。
  54. 根据权利要求51所述的装置，其特征在于，所述第一DRB为默认DRB，所述QoS流数据没有被无线资源控制RRC配置用于传输该所述QoS流到DRB的映射关系，也没有用反射QoS指示所述QoS流到DRB的映射关系。
  55. 一种通信系统，其特征在于，包括权利要求17-25中任一项所述的装置和权利要求26-32中任一项所述的装置。
  56. 一种通信系统，其特征在于，包括权利要求44-50中任一项所述的装置和权利要求51-54中任一项所述的装置。
  57. 一种通信设备，其特征在于，用于执行权利要求1-16和33-43中任意一项所述的方法。
  58. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行权利要求1-16和33-43中任意一项所述的方法。
PCT/CN2019/099054 2018-09-28 2019-08-02 数据传输的方法和装置 WO2020063108A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP19865768.6A EP3836612A4 (en) 2018-09-28 2019-08-02 DATA TRANSMISSION PROCESS AND APPARATUS
CA3111098A CA3111098A1 (en) 2018-09-28 2019-08-02 Data transmission method and apparatus
JP2021517258A JP7177259B2 (ja) 2018-09-28 2019-08-02 データ伝送方法及び装置
US17/211,101 US11968558B2 (en) 2018-09-28 2021-03-24 Data transmission method and apparatus
JP2022180054A JP2023025025A (ja) 2018-09-28 2022-11-10 データ伝送方法及び装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811143393.6A CN110972194B (zh) 2018-09-28 2018-09-28 数据传输的方法和装置
CN201811143393.6 2018-09-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/211,101 Continuation US11968558B2 (en) 2018-09-28 2021-03-24 Data transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2020063108A1 true WO2020063108A1 (zh) 2020-04-02

Family

ID=68084066

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/099054 WO2020063108A1 (zh) 2018-09-28 2019-08-02 数据传输的方法和装置

Country Status (6)

Country Link
US (1) US11968558B2 (zh)
EP (1) EP3836612A4 (zh)
JP (2) JP7177259B2 (zh)
CN (3) CN110430599B (zh)
CA (1) CA3111098A1 (zh)
WO (1) WO2020063108A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3912387A4 (en) * 2019-01-17 2022-07-27 ZTE Corporation METHODS, DEVICE AND SYSTEMS FOR DATA MAPPING IN A WIRELESS COMMUNICATION
WO2020166817A1 (en) * 2019-02-12 2020-08-20 Lg Electronics Inc. Early data transmission in cu-du split
CN111132228B (zh) * 2019-12-25 2022-07-15 展讯半导体(成都)有限公司 Rrc重配置消息的处理方法及装置、存储介质、终端
JP7449397B2 (ja) * 2020-02-03 2024-03-13 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおいてｃｐとｕｐとが分離されたマルチキャストの送信のための方法及びその装置
CN115443723A (zh) * 2020-05-14 2022-12-06 Oppo广东移动通信有限公司 一种多路径传输方法及装置、网络设备、终端
EP4079042A4 (en) * 2020-05-29 2023-06-14 Samsung Electronics Co., Ltd. METHOD AND DEVICE FOR SUPPORTING INTERCELLULAR TRANSFER
CN113747524A (zh) * 2020-05-29 2021-12-03 北京三星通信技术研究有限公司 支持切换的方法和设备
WO2022141548A1 (zh) * 2020-12-31 2022-07-07 华为技术有限公司 一种数据传输方法及装置
CN115190655B (zh) * 2021-04-07 2024-07-30 大唐移动通信设备有限公司 数据处理方法、装置、网络设备、存储介质及程序产品

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103875275A (zh) * 2013-12-31 2014-06-18 华为技术有限公司 一种数据传输方法和用户设备以及基站
CN105228263A (zh) * 2014-06-30 2016-01-06 中兴通讯股份有限公司 Drb转换方法及装置
CN107690159A (zh) * 2016-08-05 2018-02-13 电信科学技术研究院 用户面数据的处理方法及装置
CN108811153A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 通信方法、集中式单元、分布式单元、基站及终端设备

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3482602B1 (en) 2016-07-05 2023-10-18 Apple Inc. Systems, methods and devices for control-user plane separation for 5g radio access networks
CN107889155A (zh) * 2016-09-30 2018-04-06 中兴通讯股份有限公司 一种网络切片的管理方法及装置
CN108282868B (zh) 2017-01-05 2023-07-18 中兴通讯股份有限公司 控制信令配置方法及装置
CN112637870A (zh) 2017-01-16 2021-04-09 中兴通讯股份有限公司 实体配置方法、装置及系统、cu-u
CN108616933A (zh) * 2017-01-24 2018-10-02 电信科学技术研究院 一种中央单元-分布式单元架构下的通信处理方法及装置
CN112653543B (zh) 2017-02-03 2022-04-12 华为技术有限公司 无线通信方法、用户设备、接入网设备和网络系统
CN108390830B (zh) * 2017-02-03 2024-03-05 华为技术有限公司 一种QoS流处理方法、设备和通信系统
CN116528399A (zh) 2017-02-10 2023-08-01 中兴通讯股份有限公司 Gtp传输通道的配置方法及装置
WO2018145879A1 (en) * 2017-02-10 2018-08-16 Sony Corporation Communications system, infrastructure equipment, communications device and methods
CN108430077B (zh) * 2017-02-14 2021-09-14 中国移动通信有限公司研究院 一种业务质量标识的方法及无线接入网元设备
CN108513325B (zh) 2017-02-28 2022-04-12 中兴通讯股份有限公司 一种无线接入网络系统及集中单元
CN108632910B (zh) * 2017-03-24 2019-07-02 电信科学技术研究院 一种QoS处理方法和设备
WO2019019032A1 (zh) * 2017-07-25 2019-01-31 北京小米移动软件有限公司 下行数据包配置方法及装置
CN109548182B (zh) * 2017-08-11 2022-08-12 北京三星通信技术研究有限公司 建立双连接的方法及装置
CN108541032B (zh) * 2017-09-22 2022-04-29 中兴通讯股份有限公司 无线基站分离架构下的通信方法、功能实体及无线基站
US10716096B2 (en) * 2017-11-07 2020-07-14 Apple Inc. Enabling network slicing in a 5G network with CP/UP separation
EP3625987B1 (en) * 2018-02-14 2021-07-07 LG Electronics Inc. Method and apparatus for modifying mapping rule
CN110381535B (zh) * 2018-04-12 2022-04-29 中兴通讯股份有限公司 传输控制方法及装置
US11716558B2 (en) * 2018-04-16 2023-08-01 Charter Communications Operating, Llc Apparatus and methods for integrated high-capacity data and wireless network services
US11258549B2 (en) * 2018-05-10 2022-02-22 Comcast Cable Communications, Llc Packet duplication control
US11375557B2 (en) * 2018-06-13 2022-06-28 Telefonaktiebolaget Lm Ericsson (Publ) Internet protocol (IP) address assignment in integrated access backhaul (IAB) networks
CN111901766A (zh) * 2020-04-27 2020-11-06 中兴通讯股份有限公司 承载配置、上下文信息管理、释放方法、装置和设备
US20220078808A1 (en) * 2020-09-08 2022-03-10 Qualcomm Incorporated Packet delay budget (pdb) and time sensitive communication (tsc) traffic in integrated access and backhaul (iab) networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103875275A (zh) * 2013-12-31 2014-06-18 华为技术有限公司 一种数据传输方法和用户设备以及基站
CN105228263A (zh) * 2014-06-30 2016-01-06 中兴通讯股份有限公司 Drb转换方法及装置
CN107690159A (zh) * 2016-08-05 2018-02-13 电信科学技术研究院 用户面数据的处理方法及装置
CN108811153A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 通信方法、集中式单元、分布式单元、基站及终端设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Establishment of DRB QoS in CU -DU architecture", 3GPP TSG-RAN WG3 MEETING #99BIS R3-182208, 20 April 2018 (2018-04-20), XP051430362 *
3GPP: "El Application Protocol (E1 AP )(Release 15", 3GPP TS 38. 463, no. V15.0.0, 30 June 2018 (2018-06-30), pages 1 - 132, XP051474306 *

Also Published As

Publication number Publication date
EP3836612A4 (en) 2021-10-20
CN110430599A (zh) 2019-11-08
JP2023025025A (ja) 2023-02-21
CN110972194B (zh) 2024-09-17
CN110972194A (zh) 2020-04-07
CN110312282B (zh) 2021-06-29
CN110312282A (zh) 2019-10-08
EP3836612A1 (en) 2021-06-16
JP2022501929A (ja) 2022-01-06
US20210211926A1 (en) 2021-07-08
US11968558B2 (en) 2024-04-23
JP7177259B2 (ja) 2022-11-22
CA3111098A1 (en) 2020-04-02
CN110430599B (zh) 2020-10-16

Similar Documents

Publication Publication Date Title
WO2020063108A1 (zh) 数据传输的方法和装置
US11540349B2 (en) Data transmission method, access network device, terminal, and communications system
CN110249597B (zh) 一种通信处理方法及装置
WO2019029643A1 (zh) 通信方法、基站、终端设备和系统
WO2020088472A1 (zh) 通信方法及装置
US20190230682A1 (en) Data transmission method, apparatus, and system
US20230098258A1 (en) Relay bearer establishing method and communication apparatus
WO2020119013A1 (zh) 侧链通信方法和装置
US20200205023A1 (en) Transmission control protocol (tcp) based control of a wireless user device
TWI804984B (zh) 用於第2層ue到網絡中繼的連接建立方法與設備
WO2021238318A1 (zh) 一种通信方法及装置
WO2019029642A1 (zh) 通信方法、基站、终端设备和系统
WO2021197269A1 (zh) 一种临近服务的数据传输方法、设备及系统
WO2020164557A1 (zh) 一种通信方法及相关装置
WO2020030176A1 (zh) 数据传输的方法和设备
WO2022082798A1 (zh) 通信方法及装置
WO2018228545A1 (zh) 信息处理方法以及相关装置
WO2023246746A1 (zh) 一种通信方法及相关设备
WO2023185608A1 (zh) 一种数据传输的方法及通信装置
WO2023207555A1 (zh) 一种通信方法及装置
WO2024017036A1 (zh) 一种数据发送方法及装置
CN115915286A (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: 19865768

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3111098

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2019865768

Country of ref document: EP

Effective date: 20210311

ENP Entry into the national phase

Ref document number: 2021517258

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE