WO2020221201A1 - 通信方法、装置及系统 - Google Patents

通信方法、装置及系统 Download PDF

Info

Publication number
WO2020221201A1
WO2020221201A1 PCT/CN2020/087223 CN2020087223W WO2020221201A1 WO 2020221201 A1 WO2020221201 A1 WO 2020221201A1 CN 2020087223 W CN2020087223 W CN 2020087223W WO 2020221201 A1 WO2020221201 A1 WO 2020221201A1
Authority
WO
WIPO (PCT)
Prior art keywords
delay
path
network device
network
data packet
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2020/087223
Other languages
English (en)
French (fr)
Inventor
胡星星
张宏平
曾清海
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP20799000.3A priority Critical patent/EP3952402B1/en
Publication of WO2020221201A1 publication Critical patent/WO2020221201A1/zh
Priority to US17/514,332 priority patent/US12126539B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • H04L47/283—Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B17/00—Monitoring; Testing
    • H04B17/30—Monitoring; Testing of propagation channels
    • H04B17/309—Measuring or estimating channel quality parameters
    • H04B17/364—Delay profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method, related equipment and system.
  • ultra-reliable low-latency (URLLC) services require latency within 0.5ms.
  • URLLC ultra-reliable low-latency
  • the base station needs to count the transmission delay.
  • the base station performs delay statistics according to the data radio bearer (DRB), and the prior art only mentions that the user equipment (UE) communicates with a base station through one path (that is, a DRB only Corresponds to a method of delay statistics when a radio link control (RLC) entity bears.
  • RLC radio link control
  • One DRB only corresponds to one RLC entity bearer, which means that a DRB data packet is only transmitted on one RLC entity.
  • MR-DC multi-radio dual connectivity
  • the embodiments of the present application provide a communication method, related equipment, and system.
  • one DRB corresponds to the bearer of two or more RLC entities
  • statistics on DRB delay can be realized.
  • the embodiments of the present application provide a communication method applied to the network side.
  • the method includes: receiving first information from a terminal device, where the first information includes information about a first delay and a second delay , Or, the first information includes the information of the third delay, the first delay is the delay of the terminal device on the first path, the second delay is the delay of the terminal device on the second path, and the third delay is It is obtained by the terminal device according to the delay of the terminal device on the first path and the delay of the terminal device on the second path, the first path is used to transmit the first data packet, and the second path is used to transmit the second data packet, Both the first data packet and the second data packet belong to the first DRB. Then determine the uplink delay of the first DRB according to the first information, the fourth delay, and the fifth delay.
  • the fourth delay is the network-side delay on the first path
  • the fifth delay is the second delay.
  • the UE can perform UE-side timing on each path separately.
  • Delay statistics network equipment can perform network-side delay statistics for each path separately, and finally determine the uplink delay of the DRB, and realize the statistics of DRB delay.
  • the network-side statistics of DRB delay can facilitate the network side Based on the delay, the resource allocation is adjusted to meet the business's demand for delay.
  • the embodiment of the present application may be applied to a multi-radio dual connectivity (MR-DC) scenario.
  • MR-DC multi-radio dual connectivity
  • the network-side delay on the first path is the delay of the first network device on the first path
  • the network-side delay on the second path is the delay of the second network device on the second path. Time delay.
  • the method before determining the uplink delay of the first DRB according to the first information, the fourth delay, and the fifth delay, the method further includes: from the second communication device Receive the fifth time delay.
  • the embodiments of the present application may also be applied to carrier aggregation (CA) scenarios.
  • CA carrier aggregation
  • the network-side delay on the first path is the network-side delay on the path corresponding to the first RLC entity of the first network device
  • the network-side delay on the second path is the first network device The network-side delay on the path corresponding to the second RLC entity.
  • the first information includes information about the first delay and the second delay
  • the uplink delay of the first DRB is determined according to the first information, the fourth delay, and the fifth delay, including: The first uplink delay is determined according to the first delay and the fourth delay, and the second uplink delay is determined according to the second delay and the fifth delay.
  • the uplink delay of the first DRB is determined according to the first uplink delay and the second uplink delay.
  • the first information includes information about the third delay
  • the foregoing determining the uplink delay of the first DRB according to the first information, the fourth delay, and the fifth delay includes: determining according to the fourth delay and the fifth delay The sixth delay, and the uplink delay of the first DRB according to the third delay and the sixth delay.
  • the first information includes information about the first delay and the second delay
  • the first information also includes an identifier corresponding to the first delay and an identifier corresponding to the second delay, and the identifier is used to distinguish Different time delays.
  • the above identifier can distinguish different paths.
  • the identifier in a DC scenario, can be a logical channel (LCH) identifier, a cell group (cell group) identifier, a base station identifier, etc.
  • LCH logical channel
  • the identifier may be a logical channel identifier, a cell group identifier, an RLC identifier, etc.
  • the first delay includes the packet data convergence protocol (PDCP) of the terminal device when the entity receives the first data packet from the upper layer to the terminal device to obtain it from the first network
  • the second delay includes the delay between the PDCP entity of the terminal device receiving the second data packet from the upper layer and the terminal device obtaining the uplink authorization to send the second data packet to the second network device.
  • PDCP packet data convergence protocol
  • the first delay includes the time between when the PDCP entity of the terminal device receives the first data packet from the upper layer and the terminal device obtains the uplink authorization to send the first data packet to the first RLC entity. Time delay.
  • the second delay includes the delay between when the PDCP entity of the terminal device receives the second data packet from the upper layer and when the terminal device obtains the uplink authorization to send the second data packet to the second RLC entity.
  • the fourth delay includes the HARQ transmission delay of the first network device's hybrid automatic repeat request, the delay of the RLC entity of the first network device, and the PDCP of the first network device. At least one of the delay of the entity and the delay of the first interface, the first interface being a communication interface between the central unit CU of the first network device and the distribution unit DU of the first network device.
  • the fifth delay includes at least one of the HARQ transmission delay of the second network device, the delay of the RLC entity of the second network device, and the delay of the second interface, where the second interface is the first network device and The communication interface between the second network devices.
  • the fourth delay includes the HARQ transmission delay of the first network device, the delay of the first RLC entity of the first network device, and the delay of the PDCP entity of the first network device. At least one of the delay and the delay of the first interface, where the first interface is a communication interface between the CU of the network device and the DU of the network device.
  • the fifth delay includes the HARQ transmission delay of the first network device, the delay of the second RLC entity of the first network device, the delay of the PDCP entity of the first network device, and the delay of the first interface. at least one.
  • the method before receiving the first information from the terminal device, the method further includes: sending first instruction information to the terminal device, where the first instruction information is used to instruct the terminal device to obtain the first information.
  • the first indication information may also carry the identifier of the first DRB.
  • the method before determining the uplink delay of the first DRB according to the first information, the fourth delay, and the fifth delay, the method further includes: sending second indication information to the second network device, and the second indication The information is used to instruct the second network device to acquire the fifth time delay.
  • the second indication information may also carry the identifier of the first DRB.
  • the above method further includes: sending third indication information to the terminal device, where the third indication information is used to instruct the terminal device to stop acquiring the first information.
  • the third indication information may also carry the identifier of the first DRB.
  • the above method further includes: sending fourth indication information to the second network device, where the fourth indication information is used to instruct the second network device to stop acquiring the fifth delay.
  • the fourth indication information may also carry the identifier of the first DRB.
  • the embodiments of the present application provide another communication method applied to the terminal device side.
  • the method includes: acquiring first information, where the first information includes information about a first delay and a second delay, Or, the first information includes information about the third delay, the first delay is the delay of the terminal device on the first path, the second delay is the delay of the terminal device on the second path, and the third delay is
  • the terminal device is obtained according to the delay of the terminal device on the first path and the delay of the terminal device on the second path.
  • the first path is used to transmit the first data packet
  • the second path is used to transmit the second data packet. Both the first data packet and the second data packet belong to the first DRB. Then send the first information to the first network device.
  • the UE can perform UE-side timing on each path separately.
  • Delay statistics network equipment can perform network-side delay statistics for each path separately, and finally determine the uplink delay of the DRB, and realize the statistics of DRB delay.
  • the network-side statistics of DRB delay can facilitate the network side Based on the delay, the resource allocation is adjusted to meet the business's demand for delay.
  • the embodiment of the present application may be applied to a DC scenario.
  • the network-side delay on the first path is the delay of the first network device on the first path
  • the network-side delay on the second path is the delay of the second network device on the second path. Time delay.
  • the embodiment of this application may also be applied to a CA scenario.
  • the network-side delay on the first path is the network-side delay on the path corresponding to the first RLC entity of the first network device
  • the network-side delay on the second path is the first network device The network-side delay on the path corresponding to the second RLC entity.
  • the first information includes information about the first delay and the second delay
  • the first information also includes an identifier corresponding to the first delay and an identifier corresponding to the second delay, and the identifier is used to distinguish Different time delays.
  • the above identifier can distinguish different paths.
  • the identifier in a DC scenario, can be a logical channel (LCH) identifier, a cell group (cell group) identifier, a base station identifier, etc.
  • LCH logical channel
  • the identifier may be a logical channel identifier, a cell group identifier, an RLC identifier, etc.
  • the first delay includes the time between when the PDCP entity of the terminal device receives the first data packet from the upper layer and the terminal device obtains the uplink authorization to send the first data packet to the first network device.
  • the second delay includes the delay between the PDCP entity of the terminal device receiving the second data packet from the upper layer and the terminal device obtaining the uplink authorization to send the second data packet to the second network device.
  • the first delay includes the time between when the PDCP entity of the terminal device receives the first data packet from the upper layer and the terminal device obtains the uplink authorization to send the first data packet to the first RLC entity.
  • the second delay includes the delay between the PDCP entity of the terminal device receiving the second data packet from the upper layer and the terminal device obtaining the uplink authorization to send the second data packet to the second RLC entity.
  • the method before obtaining the first information, further includes: receiving first indication information from the first network device, where the first indication information is used to instruct the terminal device to obtain the first information.
  • the first indication information may also carry the identifier of the first DRB.
  • the method further includes: receiving third indication information from the first network device, where the third indication information is used to instruct the terminal device to stop acquiring the first information.
  • the third indication information may also carry the identifier of the first DRB.
  • an embodiment of the present application provides a communication method applied to a network device side.
  • the method includes: receiving second information from a terminal device.
  • the second information includes information about a first delay or a second delay.
  • the first delay is the delay of the terminal device on the first path
  • the second delay is the delay of the terminal device on the second path.
  • the first path is used to transmit the first data packet
  • the second path is used to transmit the second path.
  • the data packet, the first data packet and the second data packet all belong to the first DRB.
  • the uplink delay of the first DRB is determined according to the second information and the sixth delay. If the second information includes the information of the first delay, the sixth delay is the network-side delay on the first path, if The second information includes information about the second delay, and the sixth delay is the network side delay on the second path.
  • a DRB corresponds to a scenario where two or more RLC entities are carried (that is, a DRB data packet is transmitted on two or more paths), and the UE can perform UE-side delay statistics on a certain path
  • the network device can perform network-side delay statistics on the path, and finally determine the uplink delay of the DRB, and realize the DRB delay statistics.
  • the network-side statistics of the DRB delay can facilitate the network side based on the time delay. Adjust the resource allocation to meet the delay requirements of the business.
  • the embodiment of the present application may be applied to a DC scenario.
  • the network-side delay on the first path is the delay of the first network device on the first path
  • the network-side delay on the second path is the delay of the second network device on the second path. Time delay.
  • the method before determining the uplink delay of the first DRB according to the second information and the sixth delay, the method further includes: receiving the fifth delay from the second communication device.
  • the embodiment of this application may also be applied to a CA scenario.
  • the network-side delay on the first path is the network-side delay on the path corresponding to the first RLC entity of the first network device
  • the network-side delay on the second path is the first network device The network-side delay on the path corresponding to the second RLC entity.
  • the first information further includes an identifier corresponding to the first delay or the second delay, and the identifier is used to distinguish different delays.
  • the above identifier can distinguish different paths.
  • the identifier in a DC scenario, can be a logical channel (LCH) identifier, a cell group (cell group) identifier, a base station identifier, etc.
  • LCH logical channel
  • the identifier may be a logical channel identifier, a cell group identifier, an RLC identifier, etc.
  • the first delay includes the time between when the PDCP entity of the terminal device receives the first data packet from the upper layer and the terminal device obtains the uplink authorization to send the first data packet to the first network device. Time delay.
  • the second delay includes the delay between the PDCP entity of the terminal device receiving the second data packet from the upper layer and the terminal device obtaining the uplink authorization to send the second data packet to the second network device.
  • the first delay includes the time between when the PDCP entity of the terminal device receives the first data packet from the upper layer and the terminal device obtains the uplink authorization to send the first data packet to the first RLC entity. Time delay.
  • the second delay includes the delay between the PDCP entity of the terminal device receiving the second data packet from the upper layer and the terminal device obtaining the uplink authorization for sending the second data packet to the second RLC entity.
  • the sixth delay includes the HARQ transmission delay of the first network device and the delay of the RLC entity of the first network device. At least one of the delay of the PDCP entity of the first network device and the delay of the first interface, where the first interface is a communication interface between the CU of the first network device and the DU of the first network device.
  • the sixth delay includes at least one of the HARQ transmission delay of the second network device, the delay of the RLC entity of the second network device, and the delay of the second interface ,
  • the second interface is a communication interface between the first network device and the second network device.
  • the sixth delay includes the HARQ transmission delay of the first network device, and the first RLC entity of the first network device. At least one of the delay, the delay of the PDCP entity of the first network device, and the delay of the first interface, where the first interface is a communication interface between the CU of the first network device and the DU of the first network device.
  • the sixth delay includes the HARQ transmission delay of the first network device, the delay of the second RLC entity of the first network device, and the delay of the PDCP entity of the first network device. At least one of the delay and the delay of the first interface.
  • the method before receiving the second information from the terminal device, the method further includes: sending fifth indication information to the terminal device, where the fifth indication information is used to instruct the terminal device to count the second information.
  • the fifth indication information may also carry the identifier of the first DRB.
  • the method further includes: sending sixth indication information to the second network device, where the sixth indication information is used to instruct the second network device to count the network side delay on the second path.
  • the sixth indication information may also carry the identifier of the first DRB.
  • the method further includes: sending seventh indication information to the terminal device, where the seventh indication information is used to instruct the terminal device to stop counting the second information.
  • the seventh indication information may also carry the identifier of the first DRB.
  • the method further includes: sending eighth indication information to the second network device, where the eighth indication information is used to instruct the second network device to stop counting the network-side delay on the second path.
  • the eighth indication information may also carry the identifier of the first DRB.
  • an embodiment of the present application provides a communication method applied to a terminal device side.
  • the method includes: acquiring second information.
  • the second information includes information about the first delay or the second delay. Is the delay of the terminal device on the first path, and the second delay is the delay of the terminal device on the second path.
  • the first path is used to transmit the first data packet, and the second path is used to transmit the second data packet. Both the first data packet and the second data packet belong to the first DRB. After that, the second information is sent to the first network device.
  • the UE can perform UE-side delay on a certain path
  • the network device can perform network-side delay statistics for the path, and finally determine the uplink delay of the DRB, and realize the statistics of the DRB delay.
  • the network-side statistics of the DRB delay can facilitate the network side based on this Delay adjusts the resource allocation to meet the business's demand for delay.
  • the embodiment of the present application may be applied to a DC scenario.
  • the network-side delay on the first path is the delay of the first network device on the first path
  • the network-side delay on the second path is the delay of the second network device on the second path. Time delay.
  • the embodiment of this application may also be applied to a CA scenario.
  • the network-side delay on the first path is the network-side delay on the path corresponding to the first RLC entity of the first network device
  • the network-side delay on the second path is the first network device The network-side delay on the path corresponding to the second RLC entity.
  • the first information further includes an identifier corresponding to the first delay or the second delay, and the identifier is used to distinguish different delays.
  • the above identifier can distinguish different paths.
  • the identifier in a DC scenario, can be a logical channel (LCH) identifier, a cell group (cell group) identifier, a base station identifier, etc.
  • LCH logical channel
  • the identifier may be a logical channel identifier, a cell group identifier, an RLC identifier, etc.
  • the first delay includes the time between when the PDCP entity of the terminal device receives the first data packet from the upper layer and the terminal device obtains the uplink authorization to send the first data packet to the first network device. Time delay.
  • the second delay includes the delay between the PDCP entity of the terminal device receiving the second data packet from the upper layer and the terminal device obtaining the uplink authorization to send the second data packet to the second network device.
  • the first delay includes the time between when the PDCP entity of the terminal device receives the first data packet from the upper layer and the terminal device obtains the uplink authorization to send the first data packet to the first RLC entity. Time delay.
  • the second delay includes the delay between the PDCP entity of the terminal device receiving the second data packet from the upper layer and the terminal device obtaining the uplink authorization for sending the second data packet to the second RLC entity.
  • the method before acquiring the second information, further includes: receiving fifth instruction information from the first network device, where the fifth instruction information is used to instruct the terminal device to acquire the second information.
  • the fifth indication information may also carry the identifier of the first DRB.
  • the method further includes: receiving seventh indication information from the first network device, where the seventh indication information is used to instruct the terminal device to stop acquiring the second information.
  • the seventh indication information may also carry the identifier of the first DRB.
  • the embodiments of the present application provide another communication method, which is applied to the network side, and the method includes: obtaining a fifth delay, and sending the fifth delay to the first network device, wherein the fifth delay For the network side delay on the second path, the second path is used to transmit the second data packet, the second data packet belongs to the first DRB, and the path used to transmit the data packet of the first DRB includes two or more .
  • the UE can perform UE-side timing on each path separately.
  • Delay statistics network equipment can perform network-side delay statistics for each path separately, and finally determine the uplink delay of the DRB, and realize the statistics of DRB delay.
  • the network-side statistics of DRB delay can facilitate the network side Based on the delay, the resource allocation is adjusted to meet the business's demand for delay.
  • the embodiment of the present application may be applied to a DC scenario.
  • the network-side delay on the first path is the delay of the first network device on the first path
  • the network-side delay on the second path is the delay of the second network device on the second path. Time delay.
  • the fifth delay includes at least one of the HARQ transmission delay of the second network device, the delay of the RLC entity of the second network device, and the delay of the second interface, and the second interface is The communication interface between the first network device and the second network device.
  • the method before obtaining the fifth delay, further includes: receiving second indication information from the first network device, where the second indication information is used to instruct the second network device to obtain the fifth delay.
  • the second indication information may also carry the identifier of the first DRB.
  • the above method further includes: receiving fourth indication information from the first network device, where the fourth indication information is used to instruct the second network device to stop acquiring the fifth delay.
  • the fourth indication information may also carry the identifier of the first DRB.
  • an embodiment of the present application provides a communication device.
  • the communication device may include at least one functional module or unit for correspondingly executing the communication method provided in the first aspect, or among possible implementations of the first aspect Any of the provided communication methods.
  • the communication device may be a network device or a component (such as a chip or a circuit) that can be used in a network device.
  • the communication device may include a transceiver unit and a processing unit.
  • the transceiver unit is configured to receive first information from the terminal device, where the first information includes information about a first delay and a second delay, or the first information includes information about a third delay, and the first delay is The delay of the terminal device on the first path, the second delay is the delay of the terminal device on the second path, and the third delay is the terminal device according to the delay of the terminal device on the first path and the terminal device on the first path.
  • the delay on the second path is obtained.
  • the first path is used to transmit the first data packet
  • the second path is used to transmit the second data packet. Both the first data packet and the second data packet belong to the first DRB.
  • the processing unit is configured to determine the uplink delay of the first DRB according to the first information, the fourth delay, and the fifth delay, where the fourth delay is the network-side delay on the first path, and the fifth delay Is the network side delay on the second path.
  • the foregoing transceiver unit may be implemented by a transceiver, and the transceiver may be a transceiver circuit or an interface circuit.
  • the processing unit can be implemented by a processor.
  • the communication device may further include a memory for storing code (program) or data.
  • an embodiment of the present application provides a communication device.
  • the communication device may include at least one functional module or unit for correspondingly executing the communication method provided in the second aspect, or among possible implementations of the second aspect Any of the provided communication methods.
  • the communication device may be a terminal device or a component (for example, a chip or a circuit) that may be used in a terminal device.
  • the communication device may include a processing unit and a transceiver unit.
  • the processing unit is configured to obtain first information, where the first information includes information about the first delay and the second delay, or the first information includes information about the third delay, and the first delay is the The delay on the first path, the second delay is the delay of the terminal device on the second path, and the third delay is the terminal device according to the delay of the terminal device on the first path and the terminal device on the second path
  • the first path is used to transmit the first data packet
  • the second path is used to transmit the second data packet
  • both the first data packet and the second data packet belong to the first DRB.
  • the transceiver unit is configured to send the first information to the first network device.
  • the foregoing transceiver unit may be implemented by a transceiver, and the transceiver may be a transceiver circuit or an interface circuit.
  • the processing unit can be implemented by a processor.
  • the communication device may further include a memory for storing code (program) or data.
  • an embodiment of the present application provides a communication device.
  • the communication device may include at least one functional module or unit for correspondingly executing the communication method provided in the third aspect, or among possible implementations of the third aspect Any of the provided communication methods.
  • the communication device may be a network device or a component (such as a chip or a circuit) that can be used in a network device.
  • the communication device may include a transceiver unit and a processing unit.
  • the transceiver unit is configured to receive second information from the terminal device, the second information includes information about the first delay or the second delay, the first delay is the delay of the terminal device on the first path, and the second delay is The delay of the terminal device on the second path.
  • the first path is used to transmit the first data packet
  • the second path is used to transmit the second data packet. Both the first data packet and the second data packet belong to the first DRB.
  • the processing unit is configured to determine the uplink delay of the first DRB according to the second information and the sixth delay. If the second information includes the information of the first delay, the sixth delay is the network side time on the first path. Delay. If the second information includes information about the second delay, the sixth delay is the network-side delay on the second path.
  • the foregoing transceiver unit may be implemented by a transceiver, and the transceiver may be a transceiver circuit or an interface circuit.
  • the processing unit can be implemented by a processor.
  • the communication device may further include a memory for storing code (program) or data.
  • an embodiment of the present application provides another communication device.
  • the communication device may include at least one functional module or unit for correspondingly executing the communication method provided in the fourth aspect, or possible implementations of the fourth aspect Any one of the provided communication methods.
  • the communication device may be a terminal device or a component (for example, a chip or a circuit) that may be used in a terminal device.
  • the communication device may include a processing unit and a transceiver unit.
  • the processing unit is configured to obtain second information.
  • the second information includes information about the first delay or the second delay.
  • the first delay is the delay of the terminal device on the first path
  • the second delay is the terminal device's delay on the first path.
  • the first path is used to transmit the first data packet
  • the second path is used to transmit the second data packet. Both the first data packet and the second data packet belong to the first DRB.
  • the transceiver unit is used to send second information to the first network device.
  • the foregoing transceiver unit may be implemented by a transceiver, and the transceiver may be a transceiver circuit or an interface circuit.
  • the processing unit can be implemented by a processor.
  • the communication device may further include a memory for storing code (program) or data.
  • an embodiment of the present application provides a communication device.
  • the communication device may include at least one functional module or unit for correspondingly executing the communication method provided in the fifth aspect, or among possible implementations of the fifth aspect Any of the provided communication methods.
  • the communication device may be a network device or a component (such as a chip or a circuit) that can be used in a network device.
  • the communication device may include a transceiver unit and a sending unit.
  • the processing unit is configured to obtain a fifth delay, where the fifth delay is a network-side delay on a second path, the second path is used to transmit a second data packet, and the second data packet belongs to the first DRB and is used for There are two or more paths for transmitting the data packet of the first DRB.
  • the transceiver unit is configured to send the fifth time delay to the first network device.
  • the foregoing transceiver unit may be implemented by a transceiver, and the transceiver may be a transceiver circuit or an interface circuit.
  • the processing unit can be implemented by a processor.
  • the communication device may further include a memory for storing code (program) or data.
  • an embodiment of the present application provides a network device, which is configured to execute the communication method described in the first aspect, the third aspect, or the fifth aspect.
  • the network device may include a memory and a processor, a transmitter, and a receiver coupled with the memory.
  • the transmitter is used to support the network device to perform the step of sending information by the network device in the communication method provided in the first aspect, the third aspect, or the fifth aspect.
  • the receiver is used to support the network device to perform the step of receiving information by the network device in the communication method provided in the first aspect, the third aspect, or the fifth aspect.
  • the processor is configured to support the network device to perform other processing steps in the communication method provided by the first aspect, the third aspect or the fifth aspect, except for sending information and receiving information.
  • the transmitter and receiver in the embodiments of the present application may be integrated together, or may be coupled through a coupler.
  • the memory is used to store the implementation code of the communication method described in the first aspect, or the third or fifth aspect
  • the processor is used to execute the program code stored in the memory, so that the network device executes the first aspect, Or the communication method provided by the third or fifth aspect.
  • the memory and the processor can be integrated together or coupled through a coupler.
  • an embodiment of the present application provides a terminal device, which is used to execute the communication method described in the second or fourth aspect.
  • the terminal device may include a memory and a processor, a transmitter, and a receiver coupled with the memory.
  • the transmitter is used to support the terminal device to perform the step of sending information by the terminal device in the communication method provided in the second aspect or the fourth aspect.
  • the receiver is used to support the terminal device to perform the step of receiving information by the terminal device in the communication method provided in the second aspect or the fourth aspect.
  • the processor is used to support the terminal device to execute other processing steps of the terminal device in the communication method provided in the second aspect or the fourth aspect except for sending information and receiving information.
  • the transmitter and receiver in the embodiments of the present application may be integrated together, or may be coupled through a coupler.
  • the memory is used to store the implementation code of the communication method described in the second aspect or the fourth aspect
  • the processor is used to execute the program code stored in the memory, that is, to execute the communication method provided in the second or fourth aspect .
  • the memory and the processor can be integrated together or coupled through a coupler.
  • an embodiment of the present application provides a communication system, including a terminal device and a first network device.
  • the first network device may be the communication device described in the foregoing sixth aspect or the network device described in the eleventh aspect
  • the terminal device may be the communication device described in the foregoing seventh aspect or The terminal equipment described in the twelfth aspect.
  • the first network device may be the communication device described in the foregoing eighth aspect or the network device described in the eleventh aspect
  • the terminal device may be the communication device described in the foregoing ninth aspect or the tenth aspect.
  • the communication system further includes a second network device, and the second network device may be the communication device described in the tenth aspect or the network device described in the eleventh aspect.
  • embodiments of the present application provide a computer-readable storage medium with instructions stored on the readable storage medium, which when run on a computer, cause the computer to execute the communication method described in any of the above aspects.
  • the embodiments of the present application provide a computer program product containing instructions, which when run on a computer, cause the computer to execute the communication method described in any of the foregoing aspects.
  • inventions of the present application provide a communication chip.
  • the communication chip may include a processor and one or more interfaces coupled to the processor.
  • the processor may be used to call the implementation program of the communication method provided in any one of the foregoing aspects from the memory, and execute the instructions contained in the program.
  • the interface can be used to output the processing result of the processor.
  • Fig. 1 is a schematic diagram of a wireless communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of the architecture of a user plant (UP) protocol layer involved in an embodiment of the present application;
  • UP user plant
  • FIG. 3 is a schematic diagram of a protocol stack of a network device provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a QoS flow-based QoS architecture provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of the mapping process from QoS flow to DRB provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of multiple different DRB types provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of multiple different DRB types provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of an uplink data transmission process provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a downlink data transmission process provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another uplink data transmission process provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another downlink data transmission process provided by an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of a communication method provided in the first implementation of this application.
  • FIG. 13 is a schematic flowchart of a communication method provided in the second implementation of this application.
  • FIG. 14 is a schematic flowchart of a communication method provided in the third implementation of this application.
  • 15 is a schematic flowchart of a communication method provided in the fourth implementation of the application.
  • 16 is a schematic flowchart of a communication method provided in the fifth implementation of this application.
  • FIG. 17 is a schematic flowchart of a communication method provided by implementation six of this application.
  • FIG. 18 is a schematic diagram of the hardware structure of a communication device provided by an embodiment of the present application.
  • FIG. 19 is a schematic diagram of the hardware structure of another communication device provided by an embodiment of the present application.
  • FIG. 20 is a schematic diagram of a logical structure of a network device provided by an embodiment of the present application.
  • 21 is a schematic diagram of the hardware structure of a communication device provided by an embodiment of the present application.
  • FIG. 22 is a schematic diagram of a logical structure of a terminal device provided by an embodiment of the present application.
  • FIG. 23 is a schematic structural diagram of a communication chip provided by an embodiment of the present application.
  • FIG. 1 shows a wireless communication system related to an embodiment of the present application.
  • the wireless communication system 100 may work in an authorized frequency band or an unlicensed frequency band.
  • the wireless communication system 100 is not limited to a long term evolution (LTE) system, and may also be a 5G system or a new radio technology (NR) system, or may be other evolution systems. It can be understood that the use of unlicensed frequency bands can increase the system capacity of the wireless communication system 100.
  • the wireless communication system 100 includes: one or more access network devices 101, one or more terminal devices 102, and a core network 103. among them:
  • the access network device 101 may perform wireless communication with the terminal device 102 through one or more antennas. Each access network device 101 can provide communication coverage for its corresponding coverage area 104.
  • the coverage area 104 corresponding to the access network device 101 may be divided into multiple sectors (sector), where one sector corresponds to a part of the coverage area (not shown).
  • the access network device 101 may include: an evolved NodeB (evolved NodeB, eNB or eNodeB), or a next-generation node (next-generation Node B, gNB), and so on.
  • the wireless communication system 100 may include several different types of access network devices 101, such as a macro base station (macro base station), a micro base station (micro base station), and so on.
  • the access network device 101 may apply different wireless technologies, for example, a cell wireless access technology, or a wireless local area network (wireless local area networks, WLAN) wireless access technology.
  • the access network device 101 may also be called a base station, an access point (access point, AP), a transmission receive point (TRP), a central unit (CU) or other network entities, and may include the above Some or all of the functions of the network entity.
  • the terminal device 102 is a device with a wireless transceiver function. It can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on the water (such as a ship, etc.); it can also be deployed in the air (such as a plane, a balloon, etc.).
  • the terminal device may be a mobile phone (mobile phone), a tablet computer (Pad), a portable computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, Wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation safety (transportation safety) ), wireless terminals in smart cities, smart cars, wireless terminals in smart homes, etc.
  • the embodiment of this application does not limit the application scenario.
  • Terminal equipment can also be called UE, terminal (terminal), access terminal, UE unit, UE station, mobile equipment, mobile station, mobile station, mobile terminal, mobile client, mobile unit, Remote station, remote terminal equipment, remote unit, wireless unit, wireless communication equipment, user agent or user device, etc.
  • the access network device 101 communicates with the terminal device 102 through the wireless interface 105.
  • the access network device 101 may be used for the interface 106 (such as the S1 interface or the NG interface) to transmit control information or user data to the core network 103.
  • the access network device 101 and the access network device 101 may also communicate with each other directly or indirectly through an interface 107 (such as an X2/Xn interface).
  • the core network 103 equipment (such as 5G core network) includes but is not limited to: access and mobility management function (AMF) entities, session management function (session management function, SMF) entities, user plane function (user plane function) , UPF) entities, etc.
  • AMF access and mobility management function
  • SMF session management function
  • user plane function user plane function
  • UPF user plane function
  • AMF access and mobility management function
  • RAN radio access network
  • SMF radio access network
  • the SMF is used to manage the creation and deletion of a user's protocol data unit (PDU) session (session), and maintain the PDU session context and user plane forwarding management channel information.
  • PDU protocol data unit
  • UPF is used to receive data packets from the terminal device 102 and forward the data packets.
  • UPF is also used for quality of service (QoS) control, accounting information statistics, and so on.
  • QoS quality of service
  • the core network 103 equipment includes but is not limited to: MME, serving gateway (serving gateway, S-GW) entity, packet data network gateway (packet data network gateway, PDN-GW) entity, etc.
  • MME serving gateway
  • S-GW packet data network gateway
  • PDN-GW packet data network gateway
  • MME is used for access control, legal interception, user roaming control, including security and permission control, and mobility management, interaction with radio access network equipment, S-GW and other network elements, and signaling forwarding functions.
  • S-GW When S-GW is used to switch between radio access network devices, it can be used as a local anchor point and assist in the reordering function of radio access network devices; when switching between different access systems, it can be used as a mobility anchor point.
  • Reorder function perform legal interception function; perform data packet routing and forwarding; perform packet marking at the uplink and downlink transmission layers; in idle state, downlink packet buffer and initiate network-triggered service request functions; used for operators Billing and other functions.
  • PDN-GW is used for user's packet filtering function, lawful interception function, UE's IP address allocation function, data packet transmission layer marking in the uplink/downlink, uplink/downlink service level charging and service level gating , Perform business-based uplink/downlink rate control and other functions.
  • the interface between the 4G base station and the 4G core network is called the S1 port
  • the interface between the 5G base station and the 5G core network is called the NG port
  • the interface between the two 4G base stations is called the X2 port.
  • the interface between is called Xn port.
  • the interface between the 4G base station and the 5G base station serving the UE at the same time is called the X2 port.
  • the interface between the 4G base station and the 5G base station serving the UE at the same time is called the Xn port.
  • the wireless communication system 100 shown in FIG. 1 is only to illustrate the technical solution of the application more clearly, and does not constitute a limitation to the application.
  • Those of ordinary skill in the art will know that with the evolution of the network architecture and new services In the emergence of scenarios, the technical solutions provided in this application are equally applicable to similar technical problems.
  • the network devices involved in the following embodiments can be understood as access network devices.
  • the number of access network devices that provide data transmission services for terminal devices may be one or more.
  • there are two base stations that provide data transmission services for the UE one of which is a primary station and the other is a secondary station. Both the primary station and the secondary station can send downlink data to the UE, and both can receive uplink data sent by the UE.
  • FIG. 2 is a schematic diagram of the architecture of the user plant (UP) protocol layer involved in the embodiment of the present application.
  • the protocol layers of UE and base station such as gNB
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC media access control
  • PHY physical
  • the SDAP layer is a protocol layer newly introduced in 5G.
  • the SDAP layer responsible for mapping each quality of service flow (Qos flow) from the 5th generation core network (5generationcore, 5GC) to the DRB of the radio access layer, that is, according to the business attributes corresponding to the Qos flow, the data packets corresponding to the Qos flow are placed in the corresponding On the DRB.
  • Qos flow quality of service flow
  • the PDCP layer can perform services such as security, header compression, encryption, and switching. There may be multiple PDCP entities in the PDCP layer, and each entity carries data of one radio bearer (RB).
  • RB radio bearer
  • the PDCP layer can be configured to ensure that the data submitted upwards is in order (that is, submitted in order).
  • the RLC layer can perform services such as segmentation, reassembly, and retransmission. There may be multiple RLC entities in the RLC layer, and each RLC entity provides services for each PDCP entity.
  • the MAC layer can provide data transmission services for services on logical channels, and perform confirmation and denial services such as scheduling, hybrid automatic repeat request (HARQ).
  • HARQ hybrid automatic repeat request
  • the PHY layer can encode and transmit data transmitted from the MAC layer.
  • the protocol layers of the UE and the base station from top to bottom are: RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the RRC layer is used to perform broadcast, paging, RRC link establishment, radio bearer control, mobility, UE measurement report control, etc.
  • the data after each layer has processed the data is called PDU in this layer.
  • the data input from the upper layer is called the service data unit (SDU) of the layer.
  • SDU service data unit
  • the data input by the PDCP layer to the RLC layer is called PDCP PDU for the PDCP layer, and RLC SDU for the RLC layer.
  • the access network device 101 may be a base station (such as a gNB) with a separate architecture of a centralized unit (CU) and a distributed unit (DU).
  • the base station can be connected to a core network device (for example, it can be a 4G core network or a 5G core network, etc.).
  • CU and DU can be understood as the division of the base station from the perspective of logical functions.
  • CU and DU can be physically separated or deployed together. Multiple DUs can share one CU.
  • One DU can also connect to multiple CUs.
  • the CU and DU can be connected through an interface, for example, an F1 interface.
  • the function of the CU and the function of the DU may be divided according to the protocol layer of the wireless network.
  • the functions of the RRC layer, the SDAP layer, and the PDCP layer are set in the CU, and the functions of the RLC layer, the MAC layer, and the PHY layer are set in the DU.
  • the foregoing division of the functions of the CU and the DU according to the protocol layer is only an example, and the division can also be performed in other ways.
  • the CU or DU may have more protocol layer functions, or the CU or DU may also have part of the protocol layer processing functions.
  • part of the functions of the RLC layer and the functions of the protocol layer above the RLC layer may be set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer may be set in the DU.
  • the function of the CU and the function of the DU can also be divided according to the type of service or other system requirements. For example, it is divided by time delay, and functions whose processing time needs to meet the delay requirement are set in the DU, and functions that do not need to meet the delay requirement are set in the CU.
  • the CU may have one or more functions of the core network.
  • One or more CUs can be set centrally or separately.
  • the CU can be set on the network side to facilitate centralized management.
  • the DU can have multiple radio frequency functions, or the radio frequency functions can be set remotely.
  • FIG. 3 is a schematic diagram of a protocol stack of a network device provided by an embodiment of this application.
  • the control plane control The plant, CP
  • UP user plant
  • CU-CP CU control plane
  • CU-UP CU user plane
  • the CU-CP and CU-UP can be implemented by different functional entities, and the CU-CP and CU-UP can be coupled with the DU to jointly complete the function of the base station.
  • the CU-CP is responsible for the control plane function, which mainly includes the function of the RRC layer and the function of PDCP-C.
  • PDCP-C is mainly responsible for encryption and decryption of control plane data, integrity protection, data transmission, etc.
  • CU-UP is responsible for user plane functions, mainly including SDAP layer functions and PDCP-U.
  • PDCP-U is mainly responsible for data plane encryption and decryption, integrity protection, header compression, serial number maintenance, data transmission, etc.
  • the CU-CP and the CU-UP can be connected through an interface, for example, an E1 interface connection.
  • CU-CP represents that the base station can be connected to the core network equipment through the interface, and connected to the DU through the control plane interface (for example, F1-C (control plane)), and CU-UP is connected through the user plane interface (for example, F1-U (user plane) ) Connect with DU.
  • control plane interface for example, F1-C (control plane)
  • user plane interface for example, F1-U (user plane)
  • Connect with DU for example, F1-U (user plane)
  • the function of PDCP-C is also on the CU-UP side (not shown in the figure).
  • the core network establishes one or more PDU sessions for it.
  • the RAN (such as a base station) establishes one or more DRBs for each PDU session.
  • DRB can be understood as a data bearer between the base station and the UE, and the data packets in the data bearer have the same forwarding processing.
  • PDU session can be understood as a connection between the UE and a data network (data network, DN) to provide PDU connection services.
  • the data flow with the same QoS requirement is the QoS flow.
  • the QoS architecture based on QoSflow is shown in Figure 4.
  • This architecture is suitable for RAN equipment in the NR system, such as gNB connected to 5GC, and also suitable for evolved universal terrestrial radio access , E-UTRA)
  • the RAN equipment in the system such as the eNB, is connected to the 5GC.
  • 5GC establishes one or more PDUsessions for it.
  • the RAN establishes one or more DRBs for each PDU session.
  • QoS flow refers to a data flow with the same QoS requirements in a PDU session.
  • the transmission between the base station and the UE is called the access stratum (AS), and the transmission between the UE and the core network is called the non-access stratum (NAS).
  • the QoS flow-based QoS architecture mainly includes the QoS flow mapping between the access layer AS and the non-access layer NAS.
  • the NAS layer is mainly responsible for the mapping relationship between IP flows or other types of data packets and QoS flows.
  • the core network user plane function entity UPF generates downlink QoS flows, for example, through packet detection rules (PDR).
  • the terminal generates uplink QoS flow, for example, through QoS rules.
  • the AS layer is mainly responsible for the mapping relationship between QoS flow and DRB (that is, through the mapping rule of the AS).
  • the network side (such as the base station) configures the mapping relationship between QoS flow and DRB, and provides QoS services for QoS flow in the DRB of the air interface.
  • Qos flow is the smallest granularity of Qos differentiation in each PDU session.
  • a Qos Flow ID (QFI) is carried in the NG-U data packet header to identify which Qos Flow the data packet belongs to.
  • QFI Qos Flow ID
  • Both PDR and Qos rule use a packet filter to identify the corresponding data packet type, so as to know which Qos flow the packet belongs to.
  • Packet filter judges the data packet by identifying the characteristics of the data packet. For example, for an IP data packet, the source or destination IP address of the data packet, the source port number or destination port number, and the transport layer protocol number are used to identify the packet. Types of.
  • the Qos rule can be notified to the UE through 5GC, pre-configured inside the UE, or obtained by reflecting the Qos (Reflective QoS) feature.
  • the Reflective QoS feature means that the UE can generate the corresponding relationship between the data packet of the uplink service and the Qos flow through the corresponding relationship between the data packet of the downlink service and the Qos flow.
  • the core network can activate the Reflective QoS feature through the control plane or the user plane. Specifically, the core network can notify the terminal QoS flow to activate the Reflective QoS feature through a non-access layer message.
  • the QoS flow rule will carry an indication of this QoS flow activates the indication information of the Reflective QoS feature (reflective service flow feature), or the core network carries a reflective service flow indicator (reflective QoS indicator, RQI) in the header of the data packet sent to the radio access network side to indicate this Data packets have Reflective QoS characteristics.
  • the mapping process of QoS flow to DRB can be seen in Figure 5.
  • the SDAP protocol layer is above the user plane PDCP layer
  • the SDAP protocol layer is responsible for mapping the QoS flow from the non-access layer to the DRB of the access layer, for example, mapping QoS flow 1 in PDU session 1 to DRB1, and mapping QoS flow 2 in PDU session 1 to DRB2.
  • the SDAP entity that implements the SDAP protocol is established by session, and is also responsible for adding uplink QoS flow id and/or downlink QoS flow id to the air interface protocol stack.
  • QoS profile refers to the QoS parameter corresponding to the QoS flow id, including one or more of delay, packet loss rate, priority, guaranteed rate, maximum rate, and notification indication of unsatisfied rate.
  • the QoS flows of different sessions cannot be mapped to the same DRB.
  • Each session of each terminal can correspond to a default DRB (default DRB), and the terminal maps the QoS flow that is not configured with the uplink QoS flow and the DRB mapping relationship to the default DRB.
  • the gNB on the RAN side can configure the mapping relationship between the uplink QoS flow and the DRB for the terminal through RRC signaling or reflective mapping (Reflective Mapping). Reflective mapping means that the downlink data packet carries the QoS flow id, the terminal detects the QoS flow id, and maps the QoS flow with the same QoS flow id in the uplink to the same DRB.
  • the base station can also notify the UE whether the SDAP header should be carried in the uplink or/and downlink of the corresponding DRB through the RRC message.
  • the SDAP layer of the base station needs to carry QFI for each data packet in the downlink direction, that is, carry the QFI in the SDAP PDU.
  • the SDAP layer of the UE needs to carry QFI for each data packet in the downlink direction, that is, carry the QFI in the SDAP PDU.
  • EPC 4G evolved packet core
  • EPS evolved packet system
  • E-RAB evolved radio access bearer
  • MR-DC multi-radio dual connectivity
  • the network side can provide communication services for the UE through two or more base stations.
  • the two or more base stations may belong to the same radio access technology (radio access technology, RAT), or may belong to different radio access technologies.
  • RAT radio access technology
  • one base station belongs to LTE, and one belongs to NR.
  • the core network in MR-DC may be a 4G core network or a 5G core network.
  • a DRB can have various forms, which are distinguished by the base station to which the PDCP layer and the RLC/MAC/PHY layer belong.
  • DRB is divided into the bearer terminated by the master node (master node terminated bearer, MNterminated bearer) (that is, the bearer is terminated on the master station, which can also be called the user plane connection with the core network and terminates at the master station )
  • MNterminated bearer master node terminated bearer
  • the secondary station secondary nodeterminated bearer, SN terminated bearer
  • DRB can be divided into primary cell group bearer (MCGbearer), secondary cell group bearer (SCG bearer), and split bearer.
  • MCG bearer means that the RLC bearer corresponding to a DRB is only at the primary station.
  • the DRB may have one or more RLC entities at the primary station.
  • the primary station may have two RLC bearers.
  • SCG bearer means that the RLC bearer corresponding to a DRB is only in the secondary station.
  • the DRB may have one or more RLC entities at the secondary station.
  • the primary station may have two RLC bearers.
  • Split bearer refers to the RLC bearer corresponding to a DRB in both the primary station and the secondary station. For example, data in one DRB can be split to two base stations.
  • MCG refers to a group of serving cells on the primary station in MR-DC. These serving cells include the primary cell and optionally one or more secondary cells.
  • SCG refers to a group of serving cells on the secondary station in the MR-DC, these serving cells include a primary secondary cell and optionally one or more secondary cells.
  • MN terminated bearer/SN terminated bearer can be combined with MCG bearer/SCG bearer/split bearer to form different DRB types.
  • Fig. 7 is an example where the primary station is the base station in the NR system, the secondary station is the base station in the E-UTRA system, and the UE is connected to the 5G core network.
  • the split bearer is explained by taking the bearer terminated by the master station as an example.
  • the user plane connection with the core network ends at the master station, and the PDCP entity of the master station (i.e. NR PDCP in Figure 7) sends data packets belonging to a certain DRB (assumed to be DRB1) to the RLC entity of the master station (i.e., Figure 7 NR RLC).
  • NR RLC receives the DRB1 data packet sent by the NR PDCP layer, it sends the data packet to the NR MAC layer.
  • the NR MAC layer After the NR MAC layer receives the DRB1 data packet sent by the NR RLC layer, it sends the data packet
  • the NR PHY layer After receiving the DRB1 data packet, the NR PHY layer sends it to the UE, and the PDCP entity of the primary station (ie NR PDCP in Figure 7) will also send the DRB1 data packet to the secondary The RLC entity of the station (ie E-UTRA RLC in Figure 7).
  • the E-UTRA RLC After receiving the DRB1 data packet from the NR PDCP layer, the E-UTRA RLC sends the data packet to the E-UTRA MAC layer, and the E-UTRA MAC layer receives the data packet.
  • the E-UTRA PHY layer After arriving at the data packet of DRB1, it sends the data packet to the E-UTRA PHY layer. After receiving the data packet of DRB1, the E-UTRA PHY layer sends it to the UE.
  • the protocol layer entities on path 1 include NR PDCP, NR RLC, NR MAC, NR PHY, the first PHY of the UE, and the first MAC of the UE. , UE's first RLC and UE's first PDCP.
  • the protocol layer entities on Path 2 include NR PDCP, E-UTRA RLC, E-UTRA MAC, E-UTRA PHY, the second PHY of the UE, the second MAC of the UE, the second RLC of the UE, and the second PDCP of the UE.
  • the sender can send the same data packet to the UE through two or more base stations.
  • the master station will copy the data packet sent to the terminal device (such as the URLLC service data packet) into two (or more) copies at the PDCP layer, and send them to the terminal through two (or more) different base stations Equipment, thereby improving the reliability of the service.
  • the master station will copy the data packet (such as PDCP PDU) into two copies at the PDCP layer, and send the two copies of the data to the respective RLC entities of the two base stations, and the respective RLC entities of the two base stations will transfer the data
  • the packet is sent to the UE, that is, it is sent to the UE through a split bearer.
  • the PDCP layer of the uplink DRB on the UE side can also copy the data packet into two (or more) copies, and send the two (or more) data to the two (or more) RLC entities of the UE, where One RLC entity sends the data packet to the primary station, and the other RLC entity sends the data packet to the secondary station, that is, it sends the data packet to the two base stations through the split bearer.
  • the data packet replication mode in this DC scenario is referred to as a DC duplication mode.
  • the data packets (such as PDCP PDU) sent by the primary station and the secondary station to the UE are the same, and correspondingly, the data packets (such as PDCP PDU) sent by the UE to the primary station and the secondary station are also the same.
  • the sending end can also send data packets to the receiving end through multiple carriers or cells of a base station.
  • the master station will copy the data packets (such as URLLC service data packets, such as PDCP PDU) sent to the terminal device into two (or more) copies at the PDCP layer, and pass the two or more RLCs of the master station The entity is sent to the terminal device, thereby improving the reliability of the service.
  • data packets such as URLLC service data packets, such as PDCP PDU
  • the master station will copy data packets (such as PDCP Data PDU) into two copies at the PDCP layer, and send the two copies of data to two RLC entities in the master station, and the two RLC entities will send the data packets to the UE.
  • the UE side can also copy the data packet into two (or more) copies at the PDCP layer of the uplink DRB, and send the two (or more) data to the two (or more) RLC entities of the UE.
  • One RLC entity sends the data packet to one RLC entity of the master station, and the other RLC entity sends the data packet to another RLC entity of the master station.
  • the data packet duplication mode in this CA scenario is referred to as CA duplication mode.
  • the data packets (such as PDCP PDU) sent by the two RLC entities of the master station to the UE are the same, and correspondingly, the data packets (such as PDCP PDU) sent by the UE to the two RLC entities of the master station are also the same of.
  • these two or more RLC entities correspond to the same MAC entity, but the data packets of these RLC entities are restricted from being sent on different carriers or cells (for example, restricted by logical channel mapping). It can also be seen here that two or more paths are used to transmit data packets.
  • the protocol layer entity on path 1 includes the first PDCP of the base station, the first RLC of the base station, the MAC of the base station, the PHY of the base station, the PHY of the UE, the MAC of the UE, the third RLC of the UE, and the second PDCP of the UE.
  • the protocol layer entities on path 2 include the first PDCP of the base station, the second RLC of the base station, the MAC of the base station, the PHY of the base station, the PHY of the UE, the MAC of the UE, the fourth RLC of the UE, and the second PDCP of the UE.
  • the DC scenario hereinafter in this application refers to a DC including DC duplication and non-duplication.
  • the CA scenario refers to the CA duplication scenario.
  • the sender may not use the copying method, but instead use the offloading method to use two or more base stations to transmit the data packet to the UE.
  • the PDCP layer of the master station divides the data packet sent to the terminal device (for example, the data packet of the URLLC service) into two parts.
  • One part of the data packet is sent to the UE through the RLC of the master station, and the other part is sent to the UE through the secondary station.
  • the RLC is sent to the UE, that is, it is sent to the UE through a split bearer.
  • the UE can also divide the data packet into two parts at the PDCP layer of the uplink DRB, send a part of the data packet to an RLC entity of the UE and send it to the master station, and send the remaining part of the data packet to the UE
  • the other RLC entity is sent to the secondary station, that is, it is sent to the two base stations through split bearer.
  • this data packet distribution mode is referred to as a non-duplication mode.
  • the data packets sent by the primary station and the secondary station to the UE are different, and correspondingly, the data packets sent by the UE to the primary station and the secondary station are also different.
  • This can be regarded as two or more paths used to transmit DRB data packets, and the specific explanation is the same as the explanation in the above DC scenario.
  • URLLC services require delays within 0.5 ms.
  • operators need to know the current network delay performance.
  • the current protocol only provides the delay statistics method when the UE communicates with one base station on one path (that is, one DRB corresponds to only one RLC bearer), and does not provide multiple paths for the UE and two or more base stations.
  • This application proposes a delay statistics method for the situation that one DRB corresponds to two or more RLC bearers.
  • a path may also be referred to as a branch, a path, a link, etc.
  • the path may refer to the path between the UE and different base stations, and may also refer to the path between the UE and different RLC entities of the same base station.
  • the protocol layer entities on the UE side involved in path 1 include from top to bottom: PDCP layer, RLC layer, MAC layer, and PHY layer.
  • the protocol layer entities on the UE side involved in path 2 sequentially include the PDCP layer, the RLC layer, the MAC layer, and the PHY layer from top to bottom.
  • the protocol layer entities on the network side involved in path 1 include from bottom to top: the PHY layer, MAC layer, RLC layer, and PDCP layer of the master station.
  • the protocol layer entities on the network side involved in path 2 include from bottom to top: The PHY layer, MAC layer and RLC layer of the station.
  • the network-side protocol layer entities involved in path 3 include from top to bottom: the PDCP layer of the master station, the RLC layer of the master station, the MAC layer of the master station, and the PHY layer of the master station.
  • the protocol layer entities involved on the network side include from top to bottom: the RLC layer of the secondary station, the MAC layer of the secondary station, and the PHY layer of the secondary station.
  • the protocol layer entities on the UE side involved in path 3 include from bottom to top: The PHY layer of the UE, the MAC layer of the UE, the RLC layer of the UE, and the PDCP layer of the UE.
  • the protocol layer entities on the UE side involved in path 4 include from bottom to top: the PHY layer of the UE, the MAC layer of the UE, the RLC layer of the UE, and the PDCP layer of the UE.
  • the RLC layer, MAC layer, RLC layer, and PDCP layer on the UE side involved in path 3 and path 4 are two different protocol entities.
  • the schematic diagram in the embodiments of this application is based on the protocol entity of the UE connected to the 5G core network as an example. This application can also be used in scenarios where the UE is connected to the 4G core network (for example, there is no SDAP protocol layer).
  • Figure 8 or Figure 9 describes multiple paths corresponding to different PHY entities, in actual applications, different paths can also correspond to the same PHY entity, but different RLCs
  • the entity's data packets are sent on different carriers or cells.
  • the primary station gNB1 provides two paths to transmit DRB1 data packets for the UE.
  • Figure 10 which is a schematic diagram of the uplink data transmission process
  • Figure 11 which is a schematic diagram of the downlink data transmission process.
  • the protocol layer entities on the UE side involved in path 5 include from top to bottom: the PDCP layer of the UE, the third RLC layer of the UE, the MAC layer of the UE, and the PHY layer of the UE.
  • the protocol layer entities on the UE side involved in path 6 include from top to bottom: the PDCP layer of the UE, the fourth RLC layer of the UE, the MAC layer of the UE, and the PHY layer of the UE. Moreover, the RLC layer on the UE side involved in path 5 and path 6 are two different protocol entities, and the MAC layer and PHY layer on the UE side involved are two sets of the same protocol entity.
  • the network-side protocol layer entities involved in path 5 include from bottom to top: the PHY layer of gNB1, the MAC layer of gNB1, the first RLC layer of gNB1 and the PDCP layer of gNB1, and the network-side protocol layer entities involved in path 6 From bottom to top, it includes the PHY layer of gNB1, the MAC layer of gNB1, the second RLC layer of gNB1, and the PDCP layer of gNB1. And the RLC layer on the network side involved in path 5 and path 6 are two different protocol entities, and the MAC layer and PHY layer on the network side involved are two sets of the same protocol entity.
  • gNB1 provides two paths for UE to transmit DRB1 data packets through two RLC entities.
  • the network-side protocol layer entities involved in path 7 include from top to bottom: the PDCP layer of gNB1, the first RLC layer of gNB1, the MAC layer of gNB1 and the PHY layer of gNB1, and the PHY layer of gNB1
  • the protocol layer entities on the network side involved in the other path include from top to bottom: the PDCP layer of gNB1, the second RLC layer of gNB1, the MAC layer of gNB1, and the PHY layer of gNB1.
  • the RLC layer on the network side involved in these two paths are two different protocol entities, and the MAC layer and PHY layer on the network side involved are two sets of the same protocol entity.
  • the protocol layer entities on the UE side involved in path 7 include, from bottom to top, the PHY layer of the UE, the MAC layer of the UE, the third RLC layer of the UE, and the PDCP layer of the UE.
  • the protocol layer entities on the UE side involved in the other path include from bottom to top: the PHY layer of the UE, the MAC layer of the UE, the fourth RLC layer of the UE, and the PDCP layer of the UE.
  • the RLC layer on the UE side involved in these two paths are two different protocol entities, and the MAC layer and PHY layer on the UE side involved are two sets of the same protocol entity. For the same device (terminal device or network device), although different RLCs in FIG. 10 or FIG.
  • FIG. 11 correspond to the same PHY entity, data packets of different RLC entities are sent on different carriers or cells.
  • device terminal device or network device
  • FIG. 10 or FIG. 11 multiple paths correspond to the same PHY entity, in practical applications, different paths may also correspond to different PHY entities.
  • the uplink and downlink delays are counted in sections, and the uplink delay is divided into two sections, D1 and D2.
  • D1 can be understood as the delay on the UE side.
  • D1 includes the time between when the PDCP of the UE receives the data packet from the upper layer and when it obtains the uplink authorization to send the data packet.
  • the time delay also includes the time delay from the UE sending the scheduling request or random access to obtaining the uplink authorization.
  • D1 is counted by the UE and reported to the network side.
  • D2 can be understood as the delay on the network side, including HARQ transmission or retransmission delay, RLC side delay (such as processing delay), F1 port delay, PDCP delay (such as PDCP reordering delay), Xn port time One or more of Yanzhong.
  • D2 on path 1 includes: the HARQ transmission or retransmission delay of the first network device gNB1, the RLC side delay (such as processing delay) of gNB1, the F1 port delay of gNB1, and gNB1 PDCP delay (for example, PDCP reorder delay).
  • D2 on path 2 includes: the HARQ transmission or retransmission delay of the second network device gNB2, the RLC side delay of gNB2 (such as processing delay), the Xn port delay of gNB1 and gNB2, and the PDCP delay of gNB1 (such as PDCP reordering delay).
  • the HARQ transmission or retransmission delay of gNB2, the RLC side delay (such as processing delay) of gNB2, and the Xn interface delay of gNB1 and gNB2 are acquired by gNB2 and sent to gNB1.
  • gNB1 is responsible for counting the PDCP delay of gNB1, combining the HARQ transmission or retransmission delay of gNB2 sent by gNB2, the RLC-side delay (such as processing delay) of gNB2, and the Xn port delay of gNB1 and gNB2 to determine D2 of path 2. Or the HARQ transmission or retransmission delay of gNB2 and the RLC side delay (for example, processing delay) of gNB2 are acquired by gNB2 and sent to gNB1.
  • gNB1 is responsible for counting the Xn port delay of gNB1 and gNB2, the PDCP delay of gNB1, and the HARQ transmission or retransmission delay of gNB2 sent by gNB2, and the RLC side delay (such as processing delay) of gNB2 to determine D2 of path 2.
  • the Xn port delay can be counted by the first network device or the second network device.
  • the downlink delay includes PDCP layer delay (such as CU-UP delay), F1-U delay, HARQ transmission or retransmission delay, and RLC side delay (such as processing delay).
  • PDCP layer delay such as CU-UP delay
  • F1-U delay F1-U delay
  • HARQ transmission or retransmission delay RLC side delay
  • the downlink delay is the time from receiving a data packet from the upper layer of PDCP to the MAC layer from determining that the packet is correctly received by the UE (for example, according to the HARQ feedback received by the base station from the UE, it is determined that the packet is correctly received by the UE. ) Time period.
  • the time delay of the CU-UP can be: the time period from when the CU-UP receives the data packet through the NG-U to when the data packet is sent to the CU-DU.
  • the base station determines the uplink or downlink delay. And it can perform delay statistics according to the DRB granularity. After the base station obtains the DRB delay result, it can be converted into QoS flow-level delay (all QoS flows mapped to the same DRB have the same QoS processing) and then sent to the core network .
  • the core network can monitor the delay of the transmission path (air interface delay + delay between the access network and the core network) to determine whether the network can meet the delay requirements of different services, or to facilitate the core network to adjust the network resource allocation To meet the delay requirements of different services.
  • the following describes in detail how the base station determines the uplink delay when one DRB corresponds to two or more RLC bearers.
  • FIG. 12 is a schematic flowchart of a communication method provided in Embodiment 1 of the present application.
  • the method includes steps S201-S204. among them,
  • the terminal device generates first information.
  • the first information includes information about the first time delay and the second time delay.
  • the first time delay is the time delay of the terminal device on the first path
  • the second time delay is the terminal device on the first path. Delay on the second path, the first path is used to transmit the first data packet, the second path is used to transmit the second data packet, and both the first data packet and the second data packet belong to the first DRB.
  • the terminal device sends the first information to the first network device, and correspondingly, the first network device receives the first information from the terminal device.
  • the second network device sends a fifth delay to the first network device, the first network device receives the fifth delay from the second network device, and the fifth delay is the network-side delay on the second path.
  • the first network device determines the uplink delay of the first DRB according to the first delay, the second delay, the fourth delay, and the fifth delay, where the fourth delay is the network-side delay on the first path .
  • step S202 and step S203 are not limited.
  • the network-side delay on the first path is the delay of the first network device on the first path
  • the network-side delay on the second path is the second The delay of the network device on the second path.
  • the first network device and the second network device may be base stations.
  • the first network device and the second network device may be of the same standard or different standards.
  • the first network device is a base station in NR
  • the second network device is a base station in LTE.
  • the first DRB is a certain DRB, and the DRB is on the first network device or the DRB is terminated on the first network device.
  • the DRB is an MN terminated bearer.
  • the first network device is an SN
  • the DRB is an SN terminated bearer. If the DC duplication method is adopted, the UE copies the DRB data packet into two copies, and sends one data packet to the first network device through the first path, and another data packet to the second network device through the second path. Network equipment.
  • the UE divides the DRB data packet into two parts, and sends a part of the data packet to the first network device through the first path, and sends the remaining part of the data packet to the first network device through the second path.
  • Network equipment It should be noted that this application does not limit how a specific UE divides data packets. An example is that the UE is suspended in the RLC layer according to the data volume of the PDCP layer (suspended means that the data packet is waiting for the initial transmission, and the data packet arrives at the RLC layer. The sum of the data volume for initial transmission is compared with a threshold configured on the network side. The terminal equipment counts the UE side delay of the DRB on the two paths respectively.
  • the first network device counts the network-side delay of the DRB on the first path
  • the second network device counts the network-side delay of the DRB on the second path.
  • the first network device is gNB1
  • the second network device is gNB2
  • the first path is path 1
  • the second path is path 2.
  • gNB1 counts the network side delay D2 on path 1
  • gNB2 counts the network side delay on path 2
  • the UE counts the terminal side delay D1 on path 1 and the terminal side delay D1 on path 2 respectively.
  • the UE sends D1 of path 1 and D1 of path 2 to gNB1
  • gNB2 sends the network-side delay of path 2 to gNB1
  • gNB1 finally determines the uplink delay of DRB1.
  • the first data packet and the second data packet are only for distinguishing data transmitted on different paths.
  • the first data packet and the second data packet can be the same.
  • the UE counts the first delay and the second delay.
  • the first data packet and the second The second data packet may be several different data packets or the same several data packets. If the non-DC duplication method is adopted, the first data packet and the second data packet may be several different data packets.
  • the average delay on the path within a period of time may be counted, and the average delay may be regarded as the delay on the path.
  • the first network device uses the network-side average delay in the first time window on the first path as the network-side delay on the first path, and the UE will be the UE in the second time window of the first path.
  • the average delay on the side is taken as the delay on the UE side on the first path.
  • the duration of the first time window and the second time window may be equal or different.
  • the data packets transmitted on the first path in the first time window and the second time window all belong to the first DRB.
  • the data packets transmitted on the first path in the first time window and the second time window may be completely the same or different.
  • the number of the first data packet and the second data packet are both one or more, and the number of the first data packet and the second data packet may be the same or different.
  • the UE side counts the delay of the DRB on each path.
  • the first delay counted by the UE includes the delay between the PDCP entity of the UE receiving the first data packet from the upper layer and the UE obtaining the uplink authorization to send the first data packet to the first network device.
  • the second delay counted by the UE includes the delay between the PDCP entity of the UE receiving the second data packet from the upper layer and the UE obtaining the uplink authorization to send the second data packet to the second network device.
  • the way for the UE to determine the uplink delay on the UE side can be as follows: within a certain period, statistics are received from the PDCP upper layer service access point (SAP) or the SDAP upper layer SAP corresponding to each data packet on the first path The time delay between the data packet and the uplink authorization for transmitting the data packet, and then the average of the time delays of these data packets is taken as the first time delay. Similarly, in a certain period, calculate the delay between receiving the data packet from the PDCP upper layer SAP or SDAP upper layer SAP corresponding to each data packet on the second path to having the uplink authorization to transmit the data packet, and then The delay of these data packets is averaged as the second delay.
  • the statistical period on the first path and the statistical period on the second path may be the same or different, and the statistical period may be predetermined or configured by the network device.
  • the UE when the UE reports the information of the first delay or the second delay, it may carry an identifier corresponding to the path, such as a logical channel (LCH) identification (ID) or cell group (cell group) ID or RLC
  • ID logical channel
  • cell group cell group
  • RLC logical channel
  • the identifier (such as the primary RLC identifier or the secondary RLC identifier) or the identifier of the base station (such as the primary station identifier or the secondary station identifier) identifies the first delay and the second delay.
  • the first time delay and the second time delay are implicitly identified by different names or different positions of the two time delays.
  • the UE may carry the DRB identifier when reporting the information of the first delay or the second delay, which is used to indicate the delay information of which DRB to report.
  • the fourth delay counted by the first network device includes the HARQ transmission delay of the first network device, the delay of the RLC entity of the first network device, and the delay of the PDCP entity of the first network device. At least one of the delay and the delay of the first interface, where the first interface is a communication interface (that is, an F1 interface) between the CU of the first network device and the DU of the first network device.
  • the fifth delay counted by the second network device includes at least one of the HARQ transmission delay of the second network device, the delay of the RLC entity of the second network device, and the delay of the second interface, where the second interface is the first The communication interface between the network device and the second network device (such as Xn port, Xn port is the interface between the master station and the auxiliary station).
  • the delay of the protocol entity includes the processing delay of the protocol layer or the delay from receiving a data packet from the lower layer to sending the data packet to the upper layer.
  • the HARQ transmission delay of the first network device refers to the HARQ transmission delay of the first network device when the first network device obtains the data packet of the first DRB
  • the delay of the RLC entity of the first network device refers to the first network
  • the delay of the PDCP entity of the first network device refers to the RLC of the first network device when the first network device acquires the data packet of the first DRB.
  • the delay of the first interface refers to the delay of the first interface of the first network device when the first network device obtains the data packet of the first DRB.
  • the HARQ transmission delay of the second network device is Refers to the HARQ transmission delay of the second network device when the second network device acquires the data packet of the first DRB, and the delay of the RLC entity of the second network device refers to the second network when the second network device acquires the data packet of the first DRB.
  • the delay of the RLC entity of the device, the delay of the second interface refers to the delay of the second interface of the second network device when the second network device acquires the data packet of the first DRB.
  • the fourth delay includes the HARQ transmission delay of the first network device, the delay of the RLC entity of the first network device, and the delay of the PDCP entity of the first network device.
  • the fifth delay includes the HARQ transmission delay of the second network device and the delay of the RLC entity of the second network device.
  • the delay of the second interface is counted by the first network device, and the first network device determines the second path in combination with the fifth delay, the delay of the second interface, and the delay of the PDCP layer of the first network device. D2.
  • the delay of the second interface may also be calculated by the second network device.
  • the fifth delay includes the HARQ transmission delay of the second network device and the delay of the RLC entity of the second network device.
  • the delay of the second interface, the first network device determines the D2 of the second path in combination with the fifth delay and the delay of the PDCP layer of the first network device.
  • the fourth delay includes the HARQ transmission delay of the first network device and the time of the RLC entity of the first network device. Delay, the delay of the PDCP entity of the first network device, and the delay of the first interface.
  • the fifth delay includes the HARQ transmission delay of the second network device and the delay of the RLC entity of the second network device.
  • the delay of the second interface is counted by the CU unit, and the CU unit combines the fifth delay, the delay of the second interface, and the delay of the PDCP layer of the first network device to determine D2 of the second path.
  • the delay of the second interface may also be calculated by the second network device.
  • the fifth delay includes the HARQ transmission delay of the second network device and the delay of the RLC entity of the second network device.
  • the CU unit With the delay of the second interface, the CU unit combines the fifth delay and the delay of the PDCP layer of the first network device to determine D2 of the second path.
  • the fourth delay includes the HARQ transmission delay of the first network device and the time of the RLC entity of the first network device.
  • the fifth delay includes the HARQ transmission delay of the second network device and the delay of the RLC entity of the second network device.
  • the DU unit determines the D2 of the second path in combination with the fifth delay.
  • the method for the first network device to determine the uplink delay on the network side may be: in a certain period, counting the delay between each data packet on the first path from when the data packet is scheduled by the base station to when the data packet is received by the base station. Then the delay of these data packets is averaged as the fourth delay. Or the first network device separately counts the average delay (within a certain period) of each data packet on the first path from the DU scheduling the data packet to the DU sending the data packet to the CU-UP, and the F1 port delay, and The average delay of the CU-UP (the average delay from receiving each data packet through the F1 port to sending the data packet to the core network by the CU-UP), and then adding these delays to obtain the fourth delay.
  • the internal statistical uplink delay of the second network device is: within a certain period, each data packet on the second path is calculated from the base station scheduling the data packet to the base station receiving the data packet processing (such as sending to the core network or PDCP) The delay between the time when the layer is submitted to the upper layer), and then the average delay of these data packets is taken as the fifth delay.
  • the second network device separately counts the average delay of each data packet on the second path from the base station scheduling the data packet to the base station receiving the data packet processing (such as the time when the DU is sent to the CU) (at a certain time) Within the period), and X2/Xn port delay, and then add these delays to obtain the fifth delay.
  • the first network device may determine the uplink delay of the first DRB according to the first delay, the second delay, the fourth delay, and the fifth delay as follows: The four delays determine the first uplink delay, and the second uplink delay is determined according to the second delay and the fifth delay. Then, the uplink delay of the first DRB is determined according to the first uplink delay and the second uplink delay. That is to say, in this embodiment, the total delay of each path is first determined (for example, the uplink delay of each path is: UE-side average uplink delay reported by the UE + base station side statistics of the path on the base station side Average delay), and then determine the final delay of the DRB according to the total delay on each path (where the final delay is the uplink delay of the first DRB).
  • gNB1 first determines the total delay of path 1 according to D1 of path 1 and D2 of path 1, and determines the total delay of path 2 according to D1 of path 2 and D2 of path 2.
  • the final delay of the DRB is determined according to the total delay of path 1 and the total delay of path 2.
  • the final delay of the DRB is min (the delay of path 1 and the delay of path 2), or the DRB The final delay of is max (the delay of path 1 and the delay of path 2), or the final delay of the DRB is the average of the delay of path 1 and the delay of path 2.
  • the first network device may determine the first time delay according to the current time. The first upstream delay is confirmed with the fourth delay determined at the current moment, and the second upstream delay is obtained according to the second delay determined at the current moment and the fifth delay determined at the current moment.
  • the fifth delay sent by the second network device does not include the PDCP delay.
  • the first network device determines the D2 of the second path, it can be based on the fifth delay sent by the second network device and the first The PDCP delay of the network device is summed to obtain D2 of the second path. It is understandable that the embodiment of the present application does not limit the manner in which the network device determines the final delay of the DRB.
  • the UE may carry the foregoing first information in an RRC message (such as a measurement report message).
  • RRC message such as a measurement report message
  • the method further includes: the first network device sends first indication information to the terminal device, and the terminal device receives the first indication information from the first network device, the first indication The information is used to instruct the terminal device to count the above-mentioned first information, and after receiving the first indication information, the terminal device starts to count the first information, or the first indication information is used to instruct the terminal device to count the above-mentioned first delay and second delay After receiving the first indication information, the terminal device starts to count the first information.
  • the first DRB is located or terminated on, which network device sends the first indication information to the terminal device.
  • the master station sends the first indication information to the terminal device.
  • the secondary station sends the first indication information to the terminal device.
  • the first indication information may also include the identifier of the DRB to indicate which DRB the UE performs the UE-side delay statistics on. Different DRBs can also be configured with different statistical periods.
  • the first indication information may also indicate to perform delay statistics on uplink, or perform delay statistics on downlink, or perform delay statistics on uplink and downlink. In implementing this process, delay statistics can be configured according to the granularity of DRB. Implementing this process can reduce the load of the UE and reduce the processing overhead of the UE.
  • the first network device may send the first indication information through a measurement configuration message.
  • the network side mentioned in this embodiment notifies the UE of which DRB delay information to perform statistics on, that is, the first indication information includes the DRB identifier to indicate which DRB the UE performs UE side delay statistics on.
  • different statistical periods or the same statistical period can be configured for different DRBs in the first indication information.
  • the first indication information may also indicate to perform delay statistics on uplink, or perform delay statistics on downlink, or perform delay statistics on uplink and downlink.
  • the first indication information may be sent in the measurement configuration. These can be used as an independent implementation, and may not depend on the specific statistics on the network side and the reporting method of the UE in this application.
  • the method further includes: the first network device sends second indication information to the second network device, and the second network device receives the second time delay from the first network device.
  • Indication information instructs the second network device to count the fifth delay.
  • the primary station needs to notify the secondary station through the Xn/X2 interface to perform statistics on the network-side delay on the second path of the DRB.
  • it may also be instructed to perform uplink delay statistics, or downlink delay statistics, or uplink and downlink delay statistics.
  • the second indication information may also include a DRB identifier to indicate which DRBs the secondary station performs network-side delay statistics for.
  • DRB offloading refers to the change of a DRB between the MN terminated bearer and the SN terminated bearer
  • the master station transfers the DRB from the master station to the secondary station
  • the UE sends it when it receives the network device
  • the DRB offloading command can automatically stop the delay statistics for this DRB.
  • the DRB offloading command issued by the master station also carries the instruction information of the source base station (the base station before the migration) to delete the delay measurement configuration task of the DRB.
  • the UE can stop the delay statistics of the DRB according to the indication information.
  • the measurement task cannot be inherited, and the measurement identifier (measID) is independent on both the primary station and the secondary station.
  • the master station does not notify the UE to delete the delay measurement task of the DRB, the UE reports the result of not counting the DRB or the UE does not report the statistics result.
  • the UE restarts to perform delay statistics on the DRB.
  • the master station migrates the DRB on the master station to the secondary station, the master station can also notify the secondary station to stop performing delay statistics on the DRB.
  • the target base station base station after the relocation
  • can trigger the measurement task of the DRB again. Implementing this process can reduce the load of the UE and reduce the processing overhead of the UE.
  • the embodiment of the present application is described by taking two network devices as an example. In practical applications, more network devices may be a path through which the terminal device transmits the data packet of the first DRB.
  • the implementation process in the case of multiple paths can refer to the implementation process in the foregoing two paths, which will not be repeated here.
  • the UE can perform UE-side delay statistics for each path separately, and the network device can separately calculate each path.
  • the path performs network-side delay statistics, and finally determines the uplink delay of the DRB, and realizes the statistics of DRB delay.
  • the network-side statistics of the DRB delay can facilitate the network side to adjust the resource allocation based on the delay to satisfy the service The need for delay.
  • FIG. 13 is a schematic flowchart of a communication method provided in the second embodiment of the present application. The method includes steps S301-S303. among them,
  • the terminal device generates first information.
  • the first information includes information about the first delay and the second delay.
  • the first delay is the delay of the terminal device on the first path
  • the second delay is the terminal device's delay on the first path. Delay on the second path, the first path is used to transmit the first data packet, the second path is used to transmit the second data packet, and both the first data packet and the second data packet belong to the first DRB.
  • the terminal device sends the first information to the first network device, and the first network device receives the first information from the terminal device.
  • the first network device determines the uplink delay of the first DRB according to the first delay, the second delay, the fourth delay, and the fifth delay, where the fourth delay is the network-side delay on the first path , The fifth delay is the network-side delay on the second path.
  • the first network device has at least two RLC entities to perform data transmission with the UE.
  • the network-side delay on the first path is the delay on the path corresponding to the first RLC entity of the first network device
  • the second path The network side delay above is the delay on the path corresponding to the second RLC entity of the first network device.
  • the first network device is gNB1
  • the first path is path 5
  • the second path is path 6.
  • the gNB1 counts the network side delay D2 on path 5 and the network side delay D2 on path 6, and the UE counts the terminal side delay D1 on path 5 and the terminal side delay D1 on path 6 respectively.
  • the UE sends D1 of path 5 and D1 of path 6 to gNB1, and gNB1 finally determines the uplink delay of DRB1.
  • the first DRB is a certain DRB. If CAduplication is adopted, the UE copies the DRB data packet into two copies, and sends one data packet to the first RLC entity of the first network device through the first path, and another data packet through the second path Sent to the second RLC entity of the first network device.
  • the terminal equipment counts the UE side delay of the DRB on the two paths respectively.
  • the first network device counts the network-side delay of the DRB on the first path and the network-side delay of the DRB on the second path. For example, in FIG. 10, the first network device is gNB1, the first path is path 5, and the second path is path 6.
  • the gNB1 counts the network side delay D2 on path 5 and the network side delay D2 on path 6, and the UE counts the terminal side delay D1 on path 5 and the terminal side delay D1 on path 6 respectively. Then, the UE sends D1 of path 5 and D1 of path 6 to gNB1, and gNB1 finally determines the uplink delay of DRB1.
  • the first delay counted by the UE includes the time between the PDCP entity of the terminal device receiving the first data packet from the upper layer and the terminal device obtaining the uplink authorization to send the first data packet to the first RLC entity.
  • the second delay counted by the UE includes the delay between the PDCP entity of the terminal device receiving the second data packet from the upper layer and the terminal device obtaining the uplink authorization for sending the second data packet to the second RLC entity.
  • the way for the UE to determine the uplink delay on the UE side may be: in a certain period, the statistics of each data packet on the first path corresponding to the PDCP upper layer SAP or the SDAP upper layer SAP receiving the data packet until it has passed the first RLC
  • the entity transmits the delay between the uplink authorization of the data packet, and then takes the average of the delays of these data packets as the first delay.
  • the statistics are calculated for each data packet on the second path from the PDCP upper layer SAP or the SDAP upper layer SAP receiving the data packet to having the uplink authorization to transmit the data packet through the second RLC entity. Delay, and then average the delays of these data packets as the second delay.
  • the statistical period on the first path and the statistical period on the second path may be the same or different, and the statistical period may be predetermined or configured by the network device. It should be noted that because the scheduling time of the data packets in the two paths may be different, the UE counts the first delay and the second delay. In the same statistical period, the first data packet and the second data packet can be It is a number of different data packets, or it can be a number of the same data packets.
  • the UE when the UE reports the information of the first delay or the second delay, it carries the identifier corresponding to the path, such as LCHID or cell groupID or RLC identifier (such as the primary RLC identifier or the secondary RLC identifier) to identify the first delay and the second delay.
  • the identifier corresponding to the path
  • the UE may carry the DRB identifier when reporting the information of the first delay or the second delay, which is used to indicate the delay information of which DRB to report.
  • the fourth delay counted by the first network device includes the HARQ transmission delay of the first network device, the delay of the first RLC entity of the first network device, and the PDCP entity of the first network device. At least one of the delay of and the delay of the first interface, where the first interface is a communication interface between the CU of the network device and the DU of the network device.
  • the fifth delay counted by the first network device includes the HARQ transmission delay of the first network device, the delay of the second RLC entity of the first network device, the delay of the PDCP entity of the first network device, and the delay of the first interface. At least one of Yanzhong.
  • the method for the first network device to determine the uplink delay on the network side may be: in a certain period, counting the delay between each data packet on the first path from when the data packet is scheduled by the base station to when the data packet is received by the base station. Then the delay of these data packets is averaged as the fourth delay. Or the first network device separately counts the average delay for each data packet on the first path from the DU scheduling the data packet to the DU sending the data packet to the CU-UP, the F1 port delay, and the average CU-UP delay Delay (the average delay between CU-UP receiving each data packet through the F1 port and sending the data packet to the core network), and then adding these delays to get the fourth delay.
  • the time delay between each data packet on the second path from when the base station schedules the data packet to when the base station receives the data packet is calculated, and then the average delay of these data packets is taken as The fifth time delay.
  • the first network device separately counts the average delay of each data packet on the second path from the DU scheduling the data packet to the DU sending the data packet to the CU-UP, the F1 port delay, and the average CU-UP delay Delay (the average delay between CU-UP receiving each data packet through the F1 port and sending the data packet to the core network), and then adding these delays to obtain the fifth delay.
  • the first network device may determine the uplink delay of the first DRB according to the first delay, the second delay, the fourth delay, and the fifth delay as follows: The four delays determine the first uplink delay, and the second uplink delay is determined according to the second delay and the fifth delay. Then, the uplink delay of the first DRB is determined according to the first uplink delay and the second uplink delay. That is to say, in this embodiment, the total delay of each path is first determined (for example, the uplink delay of each path is: UE-side average uplink delay reported by the UE + base station side statistics of the path on the base station side Average delay), and then determine the final delay of the DRB according to the total delay on each path (where the final delay is the uplink delay of the first DRB).
  • gNB1 first determines the total delay of path 5 based on D1 of path 5 and D2 of path 5, and determines the total delay of path 6 based on D1 of path 6 and D2 of path 6.
  • the final delay of the DRB is determined according to the total delay of path 5 and the total delay of path 6, for example, the final delay of the DRB is min (the delay of path 5, the delay of path 6), or the DRB The final delay of is max (the delay of path 5, the delay of path 6), or the final delay of the DRB is the average of the delay of path 5 and the delay of path 6.
  • the first network device may determine the first time delay according to the current time.
  • the first upstream delay is confirmed with the fourth delay determined at the current moment, and the second upstream delay is obtained according to the second delay determined at the current moment and the fifth delay determined at the current moment. It is understandable that the embodiment of the present application does not limit the manner in which the network device determines the final delay of the DRB.
  • the UE may carry the foregoing first information in an RRC message (such as a measurement report message).
  • RRC message such as a measurement report message
  • the method further includes: the first network device sends first indication information to the terminal device, and the terminal device receives the first indication information from the first network device, the first indication The information is used to instruct the terminal device to count the foregoing first information, and after receiving the first instruction information, the terminal device starts to count the first information.
  • the first indication information may also include the identifier of the DRB to indicate which DRB the UE performs the UE-side delay statistics on. Different DRBs can also be configured with different statistical periods.
  • the first indication information may also indicate to perform delay statistics on uplink, or perform delay statistics on downlink, or perform delay statistics on uplink and downlink.
  • delay statistics can be configured according to the granularity of DRB. Implementing this process can reduce the load of the UE and reduce the processing overhead of the UE.
  • the first network device may send the first indication information through a measurement configuration message.
  • the UE can perform UE-side delay statistics for each path separately, and the network device can separately calculate each path.
  • the path performs network-side delay statistics, and finally determines the uplink delay of the DRB, and realizes the statistics of DRB delay.
  • the network-side statistics of the DRB delay can facilitate the network side to adjust the resource allocation based on the delay to satisfy the service The need for delay.
  • the UE reports the UE-side delay on two paths, and the first network device counts the total delay on the two paths, and calculates the total delay according to the two paths. The total delay determines the final delay of the first DRB.
  • the UE can report the UE-side delay after the two paths are combined.
  • the base station first obtains the combined network-side delay according to the statistics of each segment of the delay of each path, and then according to the combined UE-side time
  • the delay and the combined network-side delay determine the final delay of the first DRB.
  • FIG. 14 is a schematic flowchart of a communication method provided in Embodiment 3 of the present application. The method includes steps S401-S404. among them,
  • the terminal device generates first information, where the first information includes information about a third delay, and the third delay is the terminal device according to the delay of the terminal device on the first path and the time of the terminal device on the second path.
  • the first path is used to transmit the first data packet
  • the second path is used to transmit the second data packet. Both the first data packet and the second data packet belong to the first DRB.
  • the terminal device sends the first information to the first network device, and the first network device receives the first information from the terminal device.
  • the second network device sends a fifth delay to the first network device, the first network device receives the fifth delay from the second network device, and the fifth delay is the network-side delay on the second path.
  • the first network device determines the uplink delay of the first DRB according to the third delay, the fourth delay, and the fifth delay, where the fourth delay is the network-side delay on the first path.
  • step S402 and step S403 is not limited. This embodiment can be applied to DC scenarios.
  • the network-side delay on the first path is the delay of the first network device on the first path
  • the network-side delay on the second path is the delay of the second network device on the second path.
  • the third time delay calculated by the terminal device comprehensively considers the UE side delay of the first data packet transmitted on the first path and the UE side delay of the second data packet transmitted on the second path.
  • the third delay is obtained by comprehensively determining the UE side delay of the first data packet transmitted on the first path and the UE side delay of the second data packet transmitted on the second path. Both the first data packet and the second data packet have one or more data.
  • the way for the UE to determine the uplink delay on the UE side can be as follows: in a certain period, count the data packets corresponding to each data packet on the first path and the second path from the PDCP upper layer SAP or the SDAP upper layer SAP receiving the data packet until it has transmission The delay between the uplink grants of the data packet, and then the average of the delays of these data packets is taken as the third delay.
  • the data packets transmitted on each path are the same.
  • the UE can count the same data packets sent to the two paths as two data packets independently, that is to say, statistics are received from the PDCP upper layer SAP or SDAP upper layer SAP to each path with the uplink authorization to transmit the data packet
  • the data packet can have two delay values.
  • each data packet corresponds to the data packet received from the PDCP upper layer SAP or the SDAP upper layer SAP to obtain the uplink authorization to transmit the data packet from any path Time delay between
  • maximum value for example, each data packet corresponds to the time between receiving the data packet from the PDCP upper layer SAP or the SDAP upper layer SAP to obtaining the latest uplink authorization to transmit the data packet from these paths Delay
  • the average value as the final delay of the data packet on the UE side.
  • non-duplication DC packets that is, the data packets transmitted on each path are different.
  • the UE counts the delay between receiving a data packet from the upper SAP of PDCP or the upper SAP of SDAP to having the uplink authorization to transmit the data packet (which may come from either of the two paths). In this case, the UE counts the delays of the two paths (that is, it does not distinguish which path it is, and it is determined uniformly, that is, it is similar to the method of determining only one path). It should be noted that because the scheduling time of the data packets in the two paths may be different, the UE is delaying the third time when counting. In the same statistical period, the data packets in the first path and the second path may be Several different data packets may also be the same several data packets.
  • the UE side reported one delay in the embodiment of the present application.
  • the UE obtains the combined D1 according to the D1 of each path, and reports it to the network device, where the combination may be an average value, or a maximum value, or a minimum value, which is not limited in the embodiment of the application.
  • the way for the network device to determine the uplink delay on the network side may be as follows: the network side separately counts on two paths and determines the processing delay on the network side.
  • This application also does not limit the minimum or maximum value of the two paths as the processing delay on the network side.
  • the network equipment obtains the combined D2 according to the D2 of each path, and then obtains the final delay statistics result according to the combined D1 reported by the UE, that is, determines the final delay of the DRB (where the final delay is that of the first DRB). Uplink delay). It is understandable that the embodiment of the present application does not limit the manner in which the network device determines the final delay of the DRB.
  • the first network device and the second network device respectively count the network-side delays on their respective paths.
  • the first network device is gNB1
  • the second network device is gNB2
  • the first path is path 1
  • the second path is path 2.
  • gNB1 counts the network-side delay D2 on path 1
  • gNB2 counts the network-side delay on path 2
  • the UE comprehensively counts the terminal-side average delay D1 on path 1 and path 2 (or the UE side when the UE counts DRB1 packets The average delay D1).
  • the UE sends the statistical result D1 to gNB1, and gNB2 sends the fifth delay to gNB1, and gNB1 finally determines the uplink delay of DRB1.
  • the first network device determines the uplink delay of the first DRB according to the third delay, the fourth delay, and the fifth delay, specifically: the first network device determines the uplink delay according to the fourth delay and the fifth delay The sixth delay, and the uplink delay of the first DRB is determined according to the third delay and the sixth delay.
  • the fifth delay sent by the second network device does not include the PDCP delay.
  • the first network device determines the D2 of the second path, it can be based on the fifth delay sent by the second network device and the first The PDCP delays of the network equipment are summed to obtain D2 of the second path, and then D2 of the first path and D2 of the second path are combined to determine the sixth delay.
  • the final uplink delay of DRB1 the D1 uplink delay reported by the UE (for example, the average value of D1 on path 1 and D1 on path 2) + the D2 uplink delay determined by gNB1 (for example, path The average value of D2 on 1 and D2 on path 2).
  • the first network device may confirm the sixth uplink delay according to the latest fourth delay and the latest fifth delay.
  • the HARQ transmission delay of the first network device the delay of the RLC entity of the first network device, the delay of the PDCP entity of the first network device, the delay of the first interface, and the HARQ transmission delay of the second network device
  • the delay of the RLC entity of the second network device and the delay of the second interface reference may be made to the related description in the first embodiment shown in FIG. 12, which will not be repeated here.
  • the fourth delay and the fifth delay reference may be made to the related description in the first embodiment shown in FIG. 12, which will not be repeated here.
  • the UE may carry the foregoing first information in an RRC message (such as a measurement report message).
  • the UE may carry the DRB identifier when reporting the information of the first delay or the second delay, which is used to indicate the delay information of which DRB to report.
  • the method further includes: the first network device sends the first indication information to the terminal device, and the terminal device receives the first indication information from the first network device.
  • the first indication information is used to instruct the terminal device to count the first information.
  • the first DRB which network device sends the first indication information to the terminal device.
  • the master station sends the first indication information to the terminal device.
  • the secondary station sends the first indication information to the terminal device.
  • the first indication information may also include the identifier of the DRB to indicate which DRB the UE performs the UE-side delay statistics on.
  • the first indication information may also indicate to perform delay statistics on uplink, or perform delay statistics on downlink, or perform delay statistics on uplink and downlink.
  • delay statistics can be configured according to the granularity of DRB. Implementing this process can reduce the load of the UE and reduce the processing overhead of the UE.
  • the first network device sends the first instruction information to the terminal device, and the terminal device receives the first instruction information from the first network device. The steps of the terminal device to count the first information according to the first indication information can be taken as an embodiment alone, without relying on the above-mentioned UE reporting method and network side determination method.
  • the method further includes: the first network device sends second indication information to the second network device, and the second network device receives the second time delay from the first network device.
  • Indication information instructs the second network device to count the fifth delay.
  • the primary station needs to notify the secondary station through the Xn/X2 interface to perform statistics on the network-side delay on the second path of the DRB.
  • it may also be instructed to perform uplink delay statistics, or downlink delay statistics, or uplink and downlink delay statistics.
  • the second indication information may also include a DRB identifier to indicate which DRBs the secondary station performs network-side delay statistics for.
  • the UE when the UE receives the DRB offloading command issued by the network device, it can automatically stop the delay statistics of the DRB. Or the DRB offloading command issued by the network device also carries the instruction information of the source base station (the base station before the migration) to delete the delay measurement configuration task of the DRB. When the UE receives the DRB offloading command, it can stop the delay statistics of the DRB according to the indication information. This is because the measurement task cannot be inherited, and the measurement identifier (measID) is independent on both the primary station and the secondary station.
  • the measurement identifier (measID) is independent on both the primary station and the secondary station.
  • the UE reports the result of not counting the DRB or the UE does not report the statistics result.
  • the UE restarts to perform delay statistics on the DRB.
  • the master station migrates the DRB on the master station to the secondary station, the master station can also notify the secondary station to stop performing delay statistics on the DRB.
  • the target base station base station after the relocation
  • the embodiment of the present application is described by taking two network devices as an example. In practical applications, more network devices may be a path through which the terminal device transmits the data packet of the first DRB.
  • the implementation process in the case of multiple paths can refer to the implementation process in the foregoing two paths, which will not be repeated here.
  • the UE can perform UE-side delay statistics on multiple paths, and the network device can perform delay statistics on multiple paths. Perform delay statistics on the network side, and finally determine the uplink delay of the DRB, and realize the statistics of the DRB delay.
  • the statistics of the DRB delay on the network side can facilitate the network side to adjust the resource allocation based on the delay to meet the service requirements. The need for latency.
  • FIG. 14 is described in a DC scenario.
  • This application can also be applied to a CA scenario.
  • FIG. 15 is a schematic flowchart of a communication method provided in the fourth embodiment of the present application. The method includes steps S501-S503. among them,
  • the terminal device generates first information, where the first information includes information about a third delay, and the third delay is the terminal device according to the delay of the terminal device on the first path and the time of the terminal device on the second path.
  • the first path is used to transmit the first data packet
  • the second path is used to transmit the second data packet. Both the first data packet and the second data packet belong to the first DRB.
  • the terminal device sends the first information to the first network device, and the first network device receives the first information from the terminal device.
  • the first network device determines the uplink delay of the first DRB according to the third delay, the fourth delay, and the fifth delay, where the fourth delay is the network-side delay on the first path, and the fifth The delay is the network-side delay on the second path.
  • the first network device has at least two RLC entities to perform data transmission with the UE.
  • the network-side delay on the first path is the delay on the path corresponding to the first RLC entity of the first network device
  • the second path The network side delay above is the delay on the path corresponding to the second RLC entity of the first network device.
  • the third time delay calculated by the terminal device comprehensively considers the UE side delay of the first data packet transmitted on the first path and the UE side delay of the second data packet transmitted on the second path.
  • the third delay is obtained by comprehensively determining the UE side delay of the first data packet transmitted on the first path and the UE side delay of the second data packet transmitted on the second path. Both the first data packet and the second data packet have one or more data.
  • the way for the UE to determine the uplink delay on the UE side can be as follows: in a certain period, count the data packets corresponding to each data packet on the first path and the second path from the PDCP upper layer SAP or the SDAP upper layer SAP receiving the data packet until it has transmission The delay between the uplink grants of the data packet, and then the average of the delays of these data packets is taken as the third delay.
  • the data packets transmitted on each path are the same.
  • the UE can count the same data packets sent to the two paths as two data packets independently, that is to say, statistics are received from the PDCP upper layer SAP or SDAP upper layer SAP to each path with the uplink authorization to transmit the data packet
  • the data packet can have two delay values.
  • each data packet corresponds to the data packet received from the PDCP upper layer SAP or the SDAP upper layer SAP to obtain the uplink authorization to transmit the data packet from any path Time delay between
  • maximum value for example, each data packet corresponds to the time between receiving the data packet from the PDCP upper layer SAP or the SDAP upper layer SAP to obtaining the latest uplink authorization to transmit the data packet from these paths Delay
  • the average value as the final delay of the data packet on the UE side.
  • the UE side reported one delay in the embodiment of the present application.
  • the UE obtains the combined D1 according to the D1 of each path, and reports it to the network device, where the combination can be the average value, the maximum value, or the minimum value.
  • the first network device separately counts and determines a processing delay on the network side on the two paths (for example, taking the average value, or the maximum value, or the minimum value, etc.).
  • This application also does not limit the minimum or maximum value of the two paths as the processing delay on the network side.
  • the network equipment obtains the combined D2 according to the D2 of each path, and then obtains the final delay statistics result according to the combined D1 reported by the UE, that is, determines the final delay of the DRB (where the final delay is that of the first DRB). Uplink delay). It is understandable that the embodiment of the present application does not limit the manner in which the network device determines the final delay of the DRB.
  • the first network device determines the uplink delay of the first DRB according to the third delay, the fourth delay, and the fifth delay, specifically: the first network device determines the uplink delay according to the fourth delay and the fifth delay
  • the sixth delay, and the uplink delay of the first DRB is determined according to the third delay and the sixth delay.
  • the first network device is gNB1
  • the first path is path 5
  • the second path is path 6.
  • gNB1 comprehensively counts the network-side average delay D2 on path 5 and path 6 (or gNB1 counts the network-side average delay D2 of DRB1 data packets), and the UE comprehensively counts the terminal-side average delay D1 on path 5 and path 6 ( Or the UE counts the UE side average delay D1 of the data packet of DRB1). Then, the UE sends the statistical result D1 to gNB1, and gNB1 finally determines the uplink delay of DRB1.
  • the UE may carry the foregoing first information in an RRC message (such as a measurement report message).
  • the UE may carry the DRB identifier when reporting the information of the first delay or the second delay, which is used to indicate the delay information of which DRB to report.
  • the method further includes: the first network device sends the first indication information to the terminal device, and the terminal device receives the first indication information from the first network device.
  • the first indication information is used to instruct the terminal device to count the first information.
  • the first indication information may also include the identifier of the DRB to indicate which DRB the UE performs the UE-side delay statistics on. Different DRBs can also be configured with different statistical periods.
  • the first indication information may also indicate to perform delay statistics on uplink, or perform delay statistics on downlink, or perform delay statistics on uplink and downlink. In implementing this process, delay statistics can be configured according to the granularity of DRB. Implementing this process can reduce the load of the UE and reduce the processing overhead of the UE.
  • the UE can perform UE-side delay statistics on multiple paths, and the network device can perform delay statistics on multiple paths. Perform delay statistics on the network side, and finally determine the uplink delay of the DRB, and realize the statistics of the DRB delay.
  • the statistics of the DRB delay on the network side can facilitate the network side to adjust the resource allocation based on the delay to meet the service requirements. The need for latency.
  • the foregoing embodiments 1 to 4 are all based on the statistics of the delays of multiple paths (the multiple delays of these multiple paths can be reported separately, or the combined delay can be reported) as an example. In practical applications, it is also possible to only count the delay of a certain path (for example, only count the delay of data packets sent through the primary station, or only count the delay of data packets sent through the secondary station).
  • FIG. 16 which is a schematic flowchart of a communication method according to Embodiment 5 of the present application. The method includes but is not limited to the following steps S601-S603. among them,
  • the terminal device generates second information, where the second information includes the first delay or the second delay.
  • the second information includes information about the first time delay or the second time delay.
  • the first delay is the delay of the terminal device on the first path
  • the second delay is the delay of the terminal device on the second path.
  • the first path is used to transmit the first data packet
  • the second path is used to transmit the second path.
  • the second data packet, the first data packet and the second data packet belong to the first DRB.
  • the terminal device sends second information to the first network device, and the first network device receives the second information from the terminal device.
  • the first network device determines the uplink delay of the first DRB according to the second information and the sixth delay. If the second information includes the information of the first delay, the sixth delay is the network-side delay on the first path. Delay: If the second information includes information about the second delay, the sixth delay is the network-side delay on the second path.
  • the protocol can define which path delay is to be counted.
  • the first network device is the master station.
  • the protocol defines the statistics on the path delay between the master station and the terminal device. , The UE is responsible for counting the UE side delay on the path, and the master station is responsible for counting the network side delay on the path.
  • the protocol defined in the protocol is to count the delay on the path between the secondary station and the terminal equipment, then the UE is responsible for counting the UE side delay on the path, and the secondary station is responsible for counting the network side delay on the path and sending it to The master station is finalized. Or, according to the type of DRB defined in the protocol, choose which path delay to count.
  • the UE is responsible for counting the UE side delay on the path between the master station and the terminal device, and the master station is responsible for Count the network-side delay on the path. If it is SN terminated bearer, the UE is responsible for counting the UE-side delay on the path between the auxiliary station and the terminal device, and the auxiliary station is responsible for counting the network-side delay on the path. Or, for the CA scenario, the protocol defines the statistics of the delay on the path between the primary RLC entity of the first network device and the terminal device, then the UE is responsible for counting the UE side delay on the path, and the first network device Responsible for counting the network-side delay on the path.
  • the network device may indicate which path the delay is to be counted.
  • the network device may also send indication information to the terminal device to indicate which path the delay is to be counted, and the indication information may carry the path ID (such as LCH ID, base station ID, cell group ID, or RLC identifier (such as primary RLC identifier or secondary RLC identifier), etc.).
  • the first network device is the master station, and the master station can send indication information to the UE.
  • the indication information carries the identity of the master station and indicates to count the delay on the path between the master station and the terminal device.
  • the UE is responsible for counting the UE side delay on the path
  • the master station is responsible for counting the network side delay on the path.
  • the indication information may also carry the identifier of the DRB to indicate which DRB delays are to be counted.
  • the embodiments of this application can be applied to DC scenarios.
  • the network-side delay on the first path is the delay of the first network device on the first path
  • the network-side delay on the second path is the delay of the second network device on the second path. If the statistics are the delay on the first path, the first network device determines the total delay on the first path according to the D1 of the first path reported by the UE and the D2 of the first path calculated by the first network device. If the statistics are the delay on the second path, the second network device determines the total delay on the second path according to the D1 of the second path reported by the UE and the D2 of the second path sent by the second network device.
  • the delay on the UE side that is, the first delay includes the PDCP entity of the terminal device receiving the first data packet from the upper layer to the terminal device to obtain the first network
  • the delay on the network side that is, the sixth delay includes the HARQ transmission delay of the first network device, the delay of the RLC entity of the first network device, the delay of the PDCP entity of the first network device, and the delay of the first interface.
  • At least one of the first interface is a communication interface between the CU of the first network device and the DU of the first network device, such as an F1 interface.
  • the delay on the UE side that is, the second delay includes the PDCP entity of the terminal device receiving the second data packet from the upper layer to the terminal device and sending the second data packet to the second network device.
  • the delay on the network side that is, the sixth delay includes at least one of the HARQ transmission delay of the second network device, the delay of the RLC entity of the second network device, and the delay of the second interface.
  • the second interface is the first The communication interface between the network device and the second network device, such as an Xn interface.
  • the embodiments of the present application can also be applied to CA scenarios.
  • the network-side delay on the first path is the network-side delay on the path corresponding to the first RLC entity of the first network device
  • the network-side delay on the second path is the second RLC entity of the first network device
  • the network-side delay on the corresponding path If the statistics are the delay on the first path, the first network device determines the total delay on the first path according to the D1 of the first path reported by the UE and the D2 of the first path calculated by the first network device. If the statistics are the delay on the second path, the first network device determines the total delay on the second path according to the D1 of the second path reported by the UE and the D2 of the second path calculated by the first network device.
  • the delay on the UE side that is, the first delay includes the PDCP entity of the terminal device receiving the first data packet from the upper layer to the terminal device to obtain the first network
  • the delay on the network side that is, the sixth delay includes the HARQ transmission delay of the first network device, the delay of the first RLC entity of the first network device, the delay of the PDCP entity of the first network device, and the delay of the first interface.
  • the first interface is a communication interface between the CU of the first network device and the DU of the first network device.
  • the delay on the UE side that is, the first delay includes the PDCP entity of the terminal device receiving the second data packet from the upper layer to the terminal device obtaining the second data packet to the first network device
  • the delay on the network side that is, the sixth delay includes the HARQ transmission delay of the first network device, the delay of the second RLC entity of the first network device, the delay of the PDCP entity of the first network device, and the delay of the first interface.
  • the first interface is a communication interface between the CU of the first network device and the DU of the first network device.
  • the first information reported by the UE may also include an identifier corresponding to the first delay or the second delay, and the identifier is used to distinguish different delays.
  • the identifier may be a path identifier, or an LCH identifier, or a base station identifier, or a cell group identifier.
  • the UE when the UE receives the DRB offloading command issued by the network device, it can automatically stop the delay statistics of the DRB. Or the DRB offloading command issued by the network device also carries the instruction information of the source base station (the base station before the migration) to delete the delay measurement configuration task of the DRB.
  • the UE may stop the delay statistics of the DRB according to the indication information.
  • the master station does not notify the UE to delete the delay measurement task of the DRB, the UE reports the result of not counting the DRB or the UE does not report the statistics result.
  • the UE restarts to perform delay statistics on the DRB.
  • the master station when the master station migrates the DRB on the master station to the secondary station, the master station can also notify the secondary station to stop performing delay statistics on the DRB. After the DRB is relocated, the target base station (base station after the relocation) can trigger the measurement task of the DRB again. Implementing this process can reduce the load of the UE and reduce the processing overhead of the UE
  • the UE can perform UE-side delay statistics on a certain path, and the network device can The network side delay statistics are performed on this path, and the uplink delay of the DRB is finally determined, which realizes the DRB delay statistics.
  • the network side statistics of the DRB delay can facilitate the network side to adjust the resource allocation based on the delay. Meet the business's demand for delay.
  • FIGS. 12 to 16 are all described by taking the uplink delay as an example.
  • the downlink delay it can be counted separately by the network side.
  • FIG. 17 is a schematic flowchart of a communication method according to Embodiment 6 of the present application. The method includes the following steps.
  • the second network device sends a seventh delay to the first network device, and the first network device receives the seventh delay sent by the second network device.
  • the seventh delay is the network-side downlink delay on the third path.
  • the three paths are used to transmit the third data packet, and the third data packet belongs to the first DRB.
  • the first network device determines the downlink delay of the first DRB according to the seventh delay and the eighth delay.
  • the eighth delay is the network-side downlink delay on the fourth path, and the fourth path is used to transmit the fourth path.
  • Data packet, the fourth data packet belongs to the first DRB.
  • the seventh delay includes that the second network device receives an RLC SDU from the PDCP of the first network device until the last part of the RLC SDU is correctly received by the UE (according to the received HARQ feedback information to confirm that it is correctly received by the UE) The time delay between.
  • the seventh delay may also include at least one of X2 or Xn delay.
  • the eighth delay is the delay between when the PDCP of the first network device receives a data packet from the upper layer to when the MAC layer receives the data packet from the PHY and is correctly received by the UE.
  • the eighth delay may include: PDCP layer delay (for example, CU-UP delay), F1-U delay, HARQ transmission or retransmission delay, and RLC side delay (for example, processing delay).
  • PDCP layer delay for example, CU-UP delay
  • F1-U delay for example, F1-U delay
  • HARQ transmission or retransmission delay for example, RLC side delay
  • RLC side delay for example, processing delay.
  • gNB1 counts the downlink processing delay of path 3 (for example, within a period of time, each data packet is received from the upper layer of PDCP until the MAC layer receives the data packet from the PHY.
  • the UE is correct Time period received)
  • gNB2 counts the downlink processing delay of path 4
  • gNB2 can also count the Xn/X2 delay between gNB2 and gNB1.
  • gNB2 can calculate the final value of the downlink delay result on the gNB2 side (for example, it can count the average processing delay of data packets in a period of time at the secondary station.
  • the processing delay is: from gNB1 receiving an RLC SDU to the end of the RLC SDU The time when a part is correctly received by the UE) is notified to gNB1, and the final determination is made by gNB1.
  • the first network device determines the downlink delay of the first DRB according to the seventh delay and the eighth delay. Specifically, it may be: determining the average value (or weighted average value, or maximum value, or minimum value) of the seventh delay and the eighth delay as the downlink delay of the first DRB. In this case, there is no need for the UE to report the downlink delay.
  • the UE can also count the downlink delay.
  • the UE internal processing downlink delay is: the delay between the time when the last segment of the SDAP or PDCPSDU is correctly received by the terminal device and the time when the SDAP or PDCP layer of the terminal device submits the SDU to the upper layer.
  • the UE can separately count and report the UE-side downlink delay on each branch.
  • Fig. 17 is an illustration using a DC scenario as an example.
  • a network device separately counts the downlink delay on each path and finally determines the downlink delay of the first DRB.
  • the seventh delay may include one or more of the CU-UP delay of the first network device, the F1-U delay, and the DU-side delay.
  • the eighth delay may include: one or more of CU-UP delay, F1-U delay, and DU-side delay of the first network device.
  • gNB1 counts the delay on the downstream network side on path 7.
  • the same method is used to count the delay on the downstream network side on another path, and finally the downstream delay of the first DRB is determined.
  • Embodiment 6 shown in FIG. 17, which will not be repeated here.
  • the network side may also only count the downlink delay corresponding to the data packet of the first DRB on one path. For example, only the downlink delay corresponding to the data packet of the first DRB sent from the master station to the UE is counted. Or only the downlink delay corresponding to the data packet of the first DRB sent from the secondary station to the UE is counted.
  • this path can also be the same as the path for uplink delay statistics, that is, the uplink delay statistics are the delay of that path, and the downlink delay also counts the delay of the corresponding path.
  • the foregoing embodiment takes the terminal device to send the UE-side delay of the multiple paths to the first network device as an example.
  • the terminal device may also send D1 of the first path to the first network device, such as the master station, and send D1 of the second path to the second network device, such as the secondary station,
  • the station determines the uplink delay of the second path according to the D1 of the second path sent by the terminal device and the network-side delay of the second path calculated by itself, and then directly sends the total uplink delay of the second path to the master station (instead of The partial delay of the second path is sent to the master station, and the master station determines the uplink delay of the first DRB according to the total uplink delay of the first path and the total uplink delay of the second path.
  • the first network device mentioned in the foregoing embodiments sends the first instruction information to the terminal device, and the terminal device receives the first instruction information from the first network device.
  • the terminal equipment can count the UE side delay involved in the first DRB according to the first indication information as an embodiment alone, without relying on the specific UE reporting and network side determination procedures involved in the foregoing method embodiments.
  • the first DRB is or terminates on which network device, which network device sends the first indication information to the terminal device.
  • the master station sends the first indication information to the terminal device.
  • the secondary station sends the first indication information to the terminal device.
  • the first indication information may also include the identifier of the DRB to indicate which DRB the UE performs the UE-side delay statistics on. Different DRBs can also be configured with different statistical periods.
  • the first indication information may also indicate to perform delay statistics on uplink, or perform delay statistics on downlink, or perform delay statistics on uplink and downlink. In implementing this process, delay statistics can be configured according to the granularity of DRB. Implementing this process can reduce the load of the UE and reduce the processing overhead of the UE.
  • the first network device may send the first indication information through a measurement configuration message.
  • the implementation process for the DRB offloading (unloading) scenario can also be implemented as an independent embodiment alone, without relying on the specific UE reporting and network side determination processes involved in the foregoing method embodiments. That is, the UE can automatically stop the delay measurement of the DRB when it receives the DRB offloading command issued by the network device. Or the DRB offloading command issued by the master station also carries the instruction information of the source base station (the base station before the migration) to delete the delay measurement configuration task of the DRB. When receiving the DRB offloading command, the UE can stop the delay statistics of the DRB according to the indication information. This is because the measurement task cannot be inherited, and the measurement identifier (measID) is independent on both the primary station and the secondary station.
  • the measurement identifier (measID) is independent on both the primary station and the secondary station.
  • the UE reports the result of not counting the DRB or the UE does not report the statistics result.
  • the UE restarts to perform delay statistics on the DRB.
  • the UE can also report the proportion information, which is the proportion of the data packet delay exceeding the threshold.
  • the threshold can be determined by the network side. Set up. For example, the UE counts the UE-side delay of 10 data packets in a period, and determines whether the delay of each data packet exceeds a threshold, and then compares this with the number of data packets exceeding the threshold (for example, 8). The ratio of the number of 10 data packets (10) is used as the reported ratio information, and the network side determines the UE side delay (or delay range) according to the ratio.
  • each network element such as a terminal device, a network device, etc.
  • each network element includes a hardware structure and/or software module corresponding to each function.
  • this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the method implemented by the terminal device can also be implemented by a component (such as a chip or circuit) that can be configured in the terminal device, or implemented by a network device (first network device or second network device).
  • the method can also be implemented by a component (such as a chip or a circuit) that can be configured in a network device.
  • the embodiments of the present application can divide the terminal equipment, network equipment, etc. into functional modules according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 18 shows a schematic diagram of a possible logical structure of the communication device involved in the foregoing embodiment.
  • the communication device 800 includes a transceiver unit 801 and a processing unit 802.
  • the communication device may be a first network device or a component configurable in the first network device.
  • the transceiver unit 801 is configured to support the communication device 800 to perform the steps of receiving or sending information corresponding to the first network device in the method embodiments shown in FIG. 12 to FIG. 17.
  • the processing unit 802 is configured to support the communication device to execute the processing steps corresponding to the first network device in the method embodiments shown in FIG. 12 to FIG. 17, for example, to implement other functions except the function of the transceiver unit.
  • the communication device 800 may further include a storage unit for storing code (program) or data.
  • the processing unit 802 may call the code or data of the storage unit, so that the communication device 800 can determine the uplink delay of the first DRB according to the first information, the fourth delay, and the fifth delay, where the The first information includes information about the first delay and the second delay, or the first information includes information about the third delay, the first delay is the delay of the terminal device on the first path, and the second delay is The delay of the terminal device on the second path.
  • the third delay is obtained by the terminal device based on the delay of the terminal device on the first path and the delay of the terminal device on the second path.
  • the first path is used to transmit the second path.
  • One data packet, the second path is used to transmit the second data packet, the first data packet and the second data packet belong to the first DRB
  • the fourth delay is the network side delay on the first path
  • the fifth delay Is the network side delay on the second path.
  • the aforementioned processing unit 802 may be a processor or a processing circuit.
  • the transceiver unit 801 may be a transceiver or a transceiver circuit or an interface circuit.
  • the storage unit may be a memory. The above-mentioned processing unit, transceiver unit and storage unit may be integrated or separated.
  • FIG. 19 shows a schematic diagram of a possible logical structure of the communication device involved in the foregoing embodiment.
  • the communication device 900 includes a processing unit 901 and a transceiver unit 902.
  • the communication device may be a second network device or a component configurable in the second network device.
  • the transceiver unit 902 is configured to support the communication device 900 to perform the steps of receiving or sending information corresponding to the second network device in the method embodiments shown in FIG. 12 to FIG. 17.
  • the processing unit 901 is configured to support the second network device to perform the processing steps related to the second network device in the method embodiments shown in FIG. 12 to FIG. 17, for example, to implement other functions except the function of the transceiver unit.
  • the communication device 900 may further include a storage unit for storing code (program) or data.
  • the processing unit 802 may call the code or data of the storage unit, so that the communication device 900 obtains the fifth delay.
  • the fifth delay is the network-side delay on the second path.
  • the second data packet belongs to the first DRB, and there are two or more paths for transmitting the data packet of the first DRB.
  • the aforementioned processing unit 901 may be a processor or a processing circuit.
  • the transceiver unit 902 may be a transceiver or a transceiver circuit or an interface circuit.
  • the storage unit may be a memory. The above-mentioned processing unit, transceiver unit and storage unit may be integrated or separated.
  • FIG. 20 shows a schematic diagram of a possible hardware structure of the network device involved in the foregoing embodiment provided by the embodiment of this application.
  • the network device may be the aforementioned first network device or the second network device.
  • the network device 1000 may include: one or more processors 1001, a memory 1002, a network interface 1003, a transceiver 1005, and an antenna 1008. These components can be connected through the bus 1004 or in other ways.
  • FIG. 20 uses the bus connection as an example. among them:
  • the network interface 1003 can be used for the network device 1000 to communicate with other communication devices, such as other network devices.
  • the network interface 1003 may be a wired interface.
  • the transceiver 1005 may be used to transmit and process the signal output by the processor 1001, such as signal modulation.
  • the transceiver 1005 can also be used for receiving and processing the mobile communication signal received by the antenna 1008. For example, signal demodulation.
  • the transceiver 1005 can be regarded as a wireless modem. In the network device 1000, the number of the transceiver 1005 may be one or more.
  • the antenna 1008 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in a free space, or convert electromagnetic waves in a free space into electromagnetic energy in a transmission line.
  • the memory 1002 may be coupled with the processor 1001 through a bus 1004 or an input/output port, and the memory 1002 may also be integrated with the processor 1001.
  • the memory 1002 is used to store various software programs and/or multiple sets of instructions or data.
  • the memory 1002 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.
  • the memory 1002 may store an operating system (hereinafter referred to as system), such as embedded operating systems such as uCOS, VxWorks, RTLinux, and so on.
  • system operating system
  • the memory 1002 may also store a network communication program, which may be used to communicate with one or more additional devices, one or more user equipment, and one or more network devices.
  • the processor 1001 may be a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination that realizes certain functions, for example, a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the processor 1001 may be used to read and execute computer-readable instructions. Specifically, the processor 1001 may be used to call a program stored in the memory 1002, such as a program for implementing the communication method provided by one or more embodiments of the present application on the network device 1000 side, and execute instructions contained in the program.
  • a program stored in the memory 1002 such as a program for implementing the communication method provided by one or more embodiments of the present application on the network device 1000 side, and execute instructions contained in the program.
  • the network device 1000 may be the network device 101 in the wireless communication system 100 shown in FIG. 1, and may be implemented as a base transceiver station, a wireless transceiver, a basic service set (BSS), and an extended service set (ESS). , NodeB, eNodeB, gNB, etc.
  • the network device 1000 shown in FIG. 20 is only an implementation manner of the embodiment of the present application. In actual applications, the network device 1000 may also include more or fewer components, which is not limited here. For the specific implementation of the network device 1000, reference may be made to related descriptions in the foregoing method embodiments, and details are not described herein again.
  • FIG. 21 shows a possible logical structure diagram of the communication device corresponding to the corresponding operation of the terminal device involved in the foregoing embodiment, and the communication device 110 includes: processing The unit 1101 and the transceiver unit 1102.
  • the communication device may be a terminal device or a component that can be used in a terminal device.
  • the transceiver unit 1102 is configured to support the communication device 110 to perform the steps of receiving or sending information by the corresponding terminal device in the method embodiments shown in FIG. 12 to FIG. 17.
  • the processing unit 1101 is configured to support the terminal device to perform the processing steps related to the terminal device in the method embodiments shown in FIG. 12 to FIG.
  • the communication device may further include a storage unit for storing code (program) or data.
  • the processing unit 1101 may call the code or data of the storage unit, so that the communication device 110 obtains the first information, where the first information includes the information of the first delay and the second delay, or the first One piece of information includes information about the third delay, the first delay is the delay of the terminal device on the first path, the second delay is the delay of the terminal device on the second path, and the third delay is the terminal device according to The delay of the terminal device on the first path and the delay of the terminal device on the second path are obtained.
  • the first path is used to transmit the first data packet
  • the second path is used to transmit the second data packet. Both and the second data packet belong to the first DRB.
  • the aforementioned processing unit 1101 may be a processor or a processing circuit.
  • the transceiver unit 1102 may be a transceiver or a transceiver circuit or an interface circuit.
  • the storage unit may be a memory. The above-mentioned processing unit, transceiver unit and storage unit may be integrated or separated.
  • the terminal device 120 may include: an input and output module (for example, an audio input and output module 125, a key input module 126, a display 127, etc.), a user interface 128, one or more processors 121, a transceiver 122, an antenna 123 and memory 124. These components can be connected via a bus or in other ways.
  • Figure 22 uses a bus connection as an example. among them:
  • the antenna 123 can be used to convert electromagnetic energy into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in transmission lines.
  • the transceiver 122 can be used to transmit and process the signal output by the processor 121, and can also be used to receive and process the mobile communication signal received by the antenna 123.
  • the transceiver 122 can be regarded as a wireless modem.
  • the number of the transceiver 122 may be one or more.
  • the terminal device 120 may also include other communication components, such as a GPS module, a Bluetooth (Bluetooth) module, and a wireless fidelity (Wi-Fi) module. Not limited to the above-mentioned wireless communication signals, the terminal device 1200 may also support other wireless communication signals, such as satellite signals, shortwave signals, and so on. Not limited to wireless communication, the terminal device 120 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.
  • a wired network interface such as a LAN interface
  • the input and output module can be used to realize the interaction between the terminal device 120 and the user/external environment, and can mainly include an audio input and output module 125, a key input module 126, a display 127, and so on.
  • the input and output modules may also include: cameras, touch screens, sensors, and so on. Among them, the input and output modules all communicate with the processor 121 through the user interface 128.
  • the memory 124 may be coupled with the processor 121 through a bus or an input/output port, and the memory 124 may also be integrated with the processor 121.
  • the memory 124 is used to store various software programs and/or multiple sets of instructions.
  • the memory 124 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.
  • the memory 124 may store an operating system (hereinafter referred to as system), such as an embedded operating system such as ANDROID, IOS, WINDOWS, or LINUX.
  • the memory 12212 may also store a network communication program, which may be used to communicate with one or more additional devices, one or more user devices, and one or more network devices.
  • the memory 124 can also store a user interface program, which can vividly display the content of the application program through a graphical operation interface, and receive user control operations on the application program through input controls such as menus, dialog boxes, and keys. .
  • the memory 124 may be used to store the implementation program of the communication method provided by one or more embodiments of the present application on the terminal device 120 side.
  • the implementation of the communication method provided by one or more embodiments of the present application please refer to the foregoing embodiments.
  • the processor 121 may be used to read and execute computer-readable instructions. Specifically, the processor 121 may be used to call a program stored in the memory 124, such as an implementation program on the terminal device 120 side of the communication method provided by one or more embodiments of the present application, and execute the instructions contained in the program to implement the previous The method involved in the embodiment is continued.
  • the processor 121 can support: global system for mobile communication (GSM) (2G) communication, wideband code division multiple access (WCDMA) (3G) communication, and long term evolution (long term evolution) , LTE) (4G) communication, and one or more of 5G communication, etc.
  • GSM global system for mobile communication
  • WCDMA wideband code division multiple access
  • LTE long term evolution
  • the processor 121 when the processor 121 receives any message or data, it specifically receives it by driving or controlling the transceiver 122. Therefore, the processor 121 can be regarded as a control center that performs transmission or reception, and the transceiver 122 is a specific performer of transmission and reception operations.
  • the terminal device 120 may be the terminal device 102 in the wireless communication system 100 shown in FIG. 1, and may be implemented as an eMTC device, a mobile device, a mobile station, a mobile unit, and a wireless unit. Remote units, user agents, mobile clients, etc.
  • the terminal device 120 shown in FIG. 22 is only an implementation manner of the embodiment of the present application. In actual applications, the terminal device 120 may also include more or fewer components, which is not limited here. For the specific implementation of the terminal device 120, reference may be made to the relevant descriptions in the foregoing method embodiments, which will not be repeated here.
  • the communication chip 1300 may include a processor 1301, and one or more interfaces 1302 coupled to the processor 1301.
  • the processor 1301 may be used to read and execute computer-readable instructions.
  • the processor 1301 may mainly include a controller, an arithmetic unit, and a register.
  • the controller is mainly responsible for instruction decoding and sending control signals for the operations corresponding to the instructions.
  • the arithmetic unit is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations and logical operations, etc., and can also perform address operations and conversions.
  • the register is mainly responsible for storing the register operands and intermediate operation results temporarily stored during the execution of the instruction.
  • the hardware architecture of the processor 1301 can be an application specific integrated circuit (ASIC) architecture, a microprocessor without interlocked pipeline stage architecture (microprocessor without interlocked stages architecture, MIPS) architecture, and advanced streamlining. Instruction set machine (advanced RISC machines, ARM) architecture or NP architecture, etc.
  • the processor 1301 may be single-core or multi-core.
  • the interface 1302 can be used to input data to be processed to the processor 1301, and can output the processing result of the processor 1301 to the outside.
  • the interface 1302 can be a general purpose input output (GPIO) interface, which can be connected to multiple peripheral devices (such as a display (LCD), a camera (camara), a radio frequency (RF) module, etc.) connection.
  • GPIO general purpose input output
  • the interface 1302 is connected to the processor 1301 through the bus 1303.
  • the processor 1301 may be used to call the implementation program or data on the communication device side of the communication method provided by one or more embodiments of the present application from the memory, so that the chip can implement the aforementioned FIG. 12 to FIG. 17 shows the communication method.
  • the memory may be integrated with the processor 1301, or may be coupled to the communication chip 130 through the interface 1302, that is to say, the memory may be a part of the communication chip 130 or may be independent of the communication chip 130.
  • the interface 1302 can be used to output the execution result of the processor 1301. In this application, the interface 1302 may be specifically used to output the decoding result of the processor 1301.
  • processor 1301 and the interface 1302 may be implemented through hardware design, or through software design, or through a combination of software and hardware, which is not limited here.
  • a computer storage medium is also provided, and computer execution instructions are stored in the computer storage medium.
  • a device may be a single-chip microcomputer, a chip, etc.
  • the storage medium can be stored in a readable storage medium.
  • the computer executes the instructions, so that the device or processor executes the steps of the terminal device or network device in the communication method provided in FIG. 12 to FIG. 17.
  • the foregoing computer storage media may include: U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.
  • a computer program product in another embodiment, includes computer-executable instructions stored in a computer-readable storage medium; at least one processor of the device can be accessed from a computer
  • the read storage medium reads the computer-executable instruction, and at least one processor executes the computer-executable instruction to make the device implement the steps of the terminal device or the network device in the communication method provided in FIGS. 12 to 17.
  • a communication system in another embodiment of the present application, includes multiple devices, and the multiple devices include a terminal device and a first network device.
  • the communication system includes multiple devices, and the multiple devices include a terminal device, a first network device, and a second network device.
  • the first network device may be the communication device shown in FIG. 18 or the network device provided in FIG. 20, and is used to execute the steps corresponding to the first network device in the delay statistics method provided in FIGS. 12 to 17 .
  • the terminal device may be the communication device shown in FIG. 21 or the terminal device provided in FIG. 22, and is used to execute the steps corresponding to the terminal device in the delay statistics method provided in FIGS. 12-17.
  • the second network device may be the communication device shown in FIG. 19 or the network device provided in FIG. 20, and is used to perform the steps corresponding to the second network device in the delay statistics method provided in FIGS. 12 to 17 .
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.
  • the computer can be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • computer instructions can be transmitted from a website, computer, server, or data center through a cable (such as Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means to transmit to another website, computer, server or data center.
  • a 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 or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

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

Abstract

本申请公开了一种通信方法, 相关设备及系统, 其中该方法包括: 第一网络设备从终端设备接收第一信息, 该第一信息包括第一时延和第二时延或者第一信息包括第三时延, 第一时延为终端设备在第一路径上的时延, 第二时延为终端设备在第二路径上的时延, 第三时延为终端设备根据终端设备在第一路径上的时延和终端设备在第二路径上的时延得到的, 第一路径和第二路径上传输的数据包均属于第一DRB。第一网络设备根据第一信息、第四时延和第五时延确定第一DRB的上行时延, 第四时延为在第一路径上的网络侧时延, 第五时延为在第二路径上的网络侧时延。实施本申请, 针对一个DRB的数据包在多条路径上传输的场景, 可实现对DRB时延的统计。

Description

通信方法、装置及系统 技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法、相关设备及系统。
背景技术
随着通信需求的发展，越来越多的业务需要保证低时延的性能，比如超可靠低时延(ultra-reliable low latency，URLLC)业务需要时延在0.5ms之内。为了保证业务的性能，基站需要统计传输时延。现有技术中，基站是按照数据无线承载(data radio bearer，DRB)进行时延统计，并且现有技术只提到了用户设备(user equipment，UE)与一个基站进行一条路径通信(即一个DRB只对应一个无线链路控制(radio link control，RLC)实体承载)时的时延统计方法。一个DRB只对应一个RLC实体承载也即是说一个DRB的数据包只在一个RLC实体上传输。
而第五代(thefifth generation，5G)通信技术中引入多无线电双连接(multi-radio dual connectivity，MR-DC)技术，网络侧可以通过两个或多个基站为UE提供多条路径通信服务。而现有技术中只提供了UE与一个基站进行一条路径通信，并没有考虑一个DRB对应两个或多个RLC实体承载的场景，因此，针对一个DRB对应两个或多个的RLC实体承载的场景，如何统计该DRB的传输时延是目前需要解决的技术问题。
发明内容
本申请实施例提供了一种通信方法、相关设备及系统，针对一个DRB对应两个或多个RLC实体承载的场景，可实现对DRB时延的统计。
第一方面，本申请实施例提供了一种通信方法，应用于网络侧，该方法包括：从终端设备接收第一信息，其中，该第一信息包括第一时延和第二时延的信息，或者，第一信息包括第三时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第三时延为终端设备根据终端设备在第一路径上的时延和终端设备在第二路径上的时延得到的，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。然后根据第一信息、第四时延和第五时延确定第一DRB的上行时延，其中，第四时延为在第一路径上的网络侧时延，第五时延为在第二路径上的网络侧时延。
实施本申请实施例，针对一个DRB对应两个或多个RLC实体承载(即一个DRB的数据包在两条或多条路径上传输)的场景，UE可以分别对每条路径进行UE侧的时延统计，网络设备可以分别对每条路径进行网络侧的时延统计，最终确定出该DRB的上行时延，实现了对DRB时延的统计，网络侧统计出DRB的时延可以便于网络侧基于该时延调整资源分配以满足业务对时延的需求。
在一种可能的设计中，本申请实施例可以应用于多无线电双连接(multi-radio dual connectivity，MR-DC)场景。这种情况下，在第一路径上的网络侧时延为第一网络设备在第一路径上的时延，在第二路径上的网络侧时延为第二网络设备在第二路径上的时延。
在一种可能的设计中，在DC场景中，上述根据所述第一信息、第四时延和第五时延确定所述第一DRB的上行时延之前，还包括：从第二通信设备接收第五时延。
在一种可能的设计中，本申请实施例也可以应用于载波聚合(carrier aggregation，CA)场景。这种情况下，在第一路径上的网络侧时延为第一网络设备的第一RLC实体对应的路径上的网络侧时延，在第二路径上的网络侧时延为第一网络设备的第二RLC实体对应的路径上的网络侧时延。
在一种可能的设计中，第一信息包括第一时延和第二时延的信息，根据第一信息、第四时延和第五时延确定第一DRB的上行时延，包括：上述根据第一时延和第四时延确定第一上行时延，并根据第二时延和第五时延确定第二上行时延。根据第一上行时延和第二上行时延确定第一DRB的上行时延。
或者，第一信息包括第三时延的信息，上述根据第一信息、第四时延和第五时延确定第一DRB的上行时延，包括：根据第四时延和第五时延确定第六时延，并根据第三时延和第六时延第一DRB的上行时延。
在一种可能的设计中，若第一信息包括第一时延和第二时延的信息，第一信息还包括第一时延对应的标识和第二时延对应的标识，标识用于区别不同的时延。
可选的，上述标识可以区别出不同的路径，例如在DC场景中，该标识可以是逻辑信道(logical channel，LCH)标识、小区组(cell group)标识、基站标识等，在CA场景中，该标识可以是逻辑信道标识、小区组标识、RLC标识等。
在一种可能的设计中，在DC场景中，第一时延包括终端设备的包数据汇聚协议(packet data convergence protocol，PDCP)实体从上层收到第一数据包到终端设备获得向第一网络设备发送第一数据包的上行授权之间的时延。同理，第二时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第二网络设备发送第二数据包的上行授权之间的时延。
在一种可能的设计中，在CA场景中，第一时延包括终端设备的PDCP实体从上层收到第一数据包到终端设备获得向第一RLC实体发送第一数据包的上行授权之间的时延。同理，第二时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第二RLC实体发送第二数据包的上行授权之间的时延。
在一种可能的设计中，在DC场景中，第四时延包括第一网络设备的混合自动重传请求HARQ传输时延、第一网络设备的RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，该第一接口为第一网络设备的集中单元CU与第一网络设备的分布单元DU之间的通信接口。同理，第五时延包括第二网络设备的HARQ传输时延、第二网络设备的RLC实体的时延和第二接口的时延中的至少一个，该第二接口为第一网络设备和第二网络设备之间的通信接口。
在一种可能的设计中，在CA场景中，第四时延包括第一网络设备的HARQ传输时延、第一网络设备的第一RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，第一接口为网络设备的CU与网络设备的DU之间的通信接口。同理，第五时延包括第一网络设备的HARQ传输时延、第一网络设备的第二RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个。
在一种可能的设计中，上述从终端设备接收第一信息之前，还包括：向终端设备发送第一指示信息，第一指示信息用于指示终端设备获取第一信息。可选的，第一指示信息中还可以携带第一DRB的标识。实施该过程，可以按照DRB粒度进行时延统计的配置，从而实现了灵活配置DRB时延统计。
在一种可能的设计中，上述根据第一信息、第四时延和第五时延确定第一DRB的上行时延之前，还包括：向第二网络设备发送第二指示信息，第二指示信息用于指示第二网络设备获取第五时延。可选的，第二指示信息中还可以携带第一DRB的标识。实施该过程，可以按照DRB粒度进行时延统计的配置，从而实现了灵活配置DRB时延统计。
在一种可能的设计中，上述方法还包括：向终端设备发送第三指示信息，该第三指示信息用于指示终端设备停止获取第一信息。可选的，第三指示信息中还可以携带第一DRB的标识。实施该过程，可以灵活配置DRB时延统计，可以减少UE的负荷，降低UE的处理开销。
在一种可能的设计中，上述方法还包括：向第二网络设备发送第四指示信息，该第四指示信息用于指示第二网络设备停止获取第五时延。可选的，第四指示信息中还可以携带第一DRB的标识。实施该过程，可以灵活配置DRB时延统计，可以减少第二网络设备的负荷，降低第二网络设备的处理开销。
第二方面，本申请实施例提供了另一种通信方法，应用于终端设备侧，该方法包括：获取第一信息，其中，该第一信息包括第一时延和第二时延的信息，或者，第一信息包括第三时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第三时延为终端设备根据终端设备在第一路径上的时延和终端设备在第二路径上的时延得到的，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。之后向第一网络设备发送第一信息。
实施本申请实施例，针对一个DRB对应两个或多个RLC实体承载(即一个DRB的数据包在两条或多条路径上传输)的场景，UE可以分别对每条路径进行UE侧的时延统计，网络设备可以分别对每条路径进行网络侧的时延统计，最终确定出该DRB的上行时延，实现了对DRB时延的统计，网络侧统计出DRB的时延可以便于网络侧基于该时延调整资源分配以满足业务对时延的需求。
在一种可能的设计中，本申请实施例可以应用于DC场景。这种情况下，在第一路径上的网络侧时延为第一网络设备在第一路径上的时延，在第二路径上的网络侧时延为第二网络设备在第二路径上的时延。
在一种可能的设计中，本申请实施例也可以应用于CA场景。这种情况下，在第一路径上的网络侧时延为第一网络设备的第一RLC实体对应的路径上的网络侧时延，在第二路径上的网络侧时延为第一网络设备的第二RLC实体对应的路径上的网络侧时延。
在一种可能的设计中，若第一信息包括第一时延和第二时延的信息，第一信息还包括第一时延对应的标识和第二时延对应的标识，标识用于区别不同的时延。
可选的，上述标识可以区别出不同的路径，例如在DC场景中，该标识可以是逻辑信道(logical channel，LCH)标识、小区组(cell group)标识、基站标识等，在CA场景中，该标识可以是逻辑信道标识、小区组标识、RLC标识等。
在一种可能的设计中，在DC场景中，第一时延包括终端设备的PDCP实体从上层收到第一数据包到终端设备获得向第一网络设备发送第一数据包的上行授权之间的时延；第二时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第二网络设备发送第二数据包的上行授权之间的时延。
在一种可能的设计中，在CA场景中，第一时延包括终端设备的PDCP实体从上层收到第一数据包到终端设备获得向第一RLC实体发送第一数据包的上行授权之间的时延；第二时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第二RLC实体发送第二数据包的上行授权之间的时延。
在一种可能的设计中，在获取第一信息之前，还包括：从第一网络设备接收第一指示信息，该第一指示信息用于指示终端设备获取第一信息。可选的，第一指示信息中还可以携带第一DRB的标识。实施该过程，可以按照DRB粒度进行时延统计的配置，从而实现了灵活配置DRB时延统计。
在一种可能的设计中，该方法还包括：从第一网络设备接收第三指示信息，该第三指示信息用于指示终端设备停止获取第一信息。可选的，第三指示信息中还可以携带第一DRB的标识。实施该过程，可以灵活配置DRB时延统计，可以减少UE的负荷，降低UE的处理开销。
第三方面，本申请实施例提供了一种通信方法，应用于网络设备侧，该方法包括：从终端设备接收第二信息，第二信息包括第一时延或第二时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。之后，根据第二信息和第六时延确定第一DRB的上行时延，如果第二信息包括第一时延的信息，第六时延为在第一路径上的网络侧的时延，如果第二信息包括第二时延的信息，第六时延为在第二路径上的网络侧的时延。
实施本申请实施例，一个DRB对应两个或多个RLC实体承载(即一个DRB的数据包在两条或多条路径上传输)的场景，UE可以对某一条路径进行UE侧的时延统计，网络设备可以对该条路径进行网络侧的时延统计，最终确定出该DRB的上行时延，实现了对DRB时延的统计，网络侧统计出DRB的时延可以便于网络侧基于该时延调整资源分配以满足业务对时延的需求。
在一种可能的设计中，本申请实施例可以应用于DC场景。这种情况下，在第一路径上的网络侧时延为第一网络设备在第一路径上的时延，在第二路径上的网络侧时延为第二网络设备在第二路径上的时延。
在一种可能的设计中，在DC场景中，上述根据第二信息和第六时延确定第一DRB的上行时延之前，还包括：从第二通信设备接收第五时延。
在一种可能的设计中，本申请实施例也可以应用于CA场景。这种情况下，在第一路径上的网络侧时延为第一网络设备的第一RLC实体对应的路径上的网络侧时延，在第二路径上的网络侧时延为第一网络设备的第二RLC实体对应的路径上的网络侧时延。
在一种可能的设计中，第一信息还包括第一时延或第二时延对应的标识，标识用于区别不同的时延。
可选的，上述标识可以区别出不同的路径，例如在DC场景中，该标识可以是逻辑信道(logical channel，LCH)标识、小区组(cell group)标识、基站标识等，在CA场景中，该标识可以是逻辑信道标识、小区组标识、RLC标识等。
在一种可能的设计中，在DC场景中，第一时延包括终端设备的PDCP实体从上层收到第一数据包到终端设备获得向第一网络设备发送第一数据包的上行授权之间的时延。
或者，第二时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第二网络设备发送第二数据包的上行授权之间的时延。
在一种可能的设计中，在CA场景中，第一时延包括终端设备的PDCP实体从上层收到第一数据包到终端设备获得向第一RLC实体发送第一数据包的上行授权之间的时延。
或者，第二时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第二RLC实体发送第二数据包的上行授权之间的时延。
在一种可能的设计中，在DC场景中，如果第二信息包括第一时延的信息，第六时延包括第一网络设备的HARQ传输时延、第一网络设备的RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，第一接口为第一网络设备的CU与第一网络设备的DU之间的通信接口。
或者，如果第二信息包括第二时延的信息，第六时延包括第二网络设备的HARQ传输时延、第二网络设备的RLC实体的时延和第二接口的时延中的至少一个，第二接口为第一网络设备和第二网络设备之间的通信接口。
在一种可能的设计中，在CA场景中，如果第二信息包括第一时延的信息，第六时延包括第一网络设备的HARQ传输时延、第一网络设备的第一RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，第一接口为第一网络设备的CU与第一网络设备的DU之间的通信接口。
或者，如果第二信息包括第二时延的信息，第六时延包括第一网络设备的HARQ传输时延、第一网络设备的第二RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个。
在一种可能的设计中，在从终端设备接收第二信息之前，还包括：向终端设备发送第五指示信息，第五指示信息用于指示终端设备统计第二信息。可选的，第五指示信息中还可以携带第一DRB的标识。实施该过程，可以按照DRB粒度进行时延统计的配置，从而实现了灵活配置DRB时延统计。
在一种可能的设计中，该方法还包括：向第二网络设备发送第六指示信息，第六指示信息用于指示第二网络设备统计第二路径上的网络侧的时延。可选的，第六指示信息中还可以携带第一DRB的标识。实施该过程，可以按照DRB粒度进行时延统计的配置，从而实现了灵活配置DRB时延统计。
在一种可能的设计中，该方法还包括：向终端设备发送第七指示信息，第七指示信息用于指示终端设备停止统计第二信息。可选的，第七指示信息中还可以携带第一DRB的标识。实施该过程，可以灵活配置DRB时延统计，可以减少UE的负荷，降低UE的处理开销。
在一种可能的设计中，该方法还包括：向第二网络设备发送第八指示信息，第八指示 信息用于指示第二网络设备停止统计第二路径上的网络侧的时延。可选的，第八指示信息中还可以携带第一DRB的标识。实施该过程，可以灵活配置DRB时延统计，可以减少第二网络设备的负荷，降低第二网络设备的处理开销。
第四方面，本申请实施例提供了一种通信方法，应用于终端设备侧，该方法包括：获取第二信息，第二信息包括第一时延或第二时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。之后，向第一网络设备发送第二信息。
实施本申请实施例，针对一个DRB对应两个或多个RLC实体承载(即一个DRB的数据包在两条或多条路径上传输)的场景，UE可以对某一条路径进行UE侧的时延统计，网络设备可以对该条路径进行网络侧的时延统计，最终确定出该DRB的上行时延，实现了对DRB时延的统计，网络侧统计出DRB的时延可以便于网络侧基于该时延调整资源分配以满足业务对时延的需求。
在一种可能的设计中，本申请实施例可以应用于DC场景。这种情况下，在第一路径上的网络侧时延为第一网络设备在第一路径上的时延，在第二路径上的网络侧时延为第二网络设备在第二路径上的时延。
在一种可能的设计中，本申请实施例也可以应用于CA场景。这种情况下，在第一路径上的网络侧时延为第一网络设备的第一RLC实体对应的路径上的网络侧时延，在第二路径上的网络侧时延为第一网络设备的第二RLC实体对应的路径上的网络侧时延。
在一种可能的设计中，第一信息还包括第一时延或第二时延对应的标识，标识用于区别不同的时延。
可选的，上述标识可以区别出不同的路径，例如在DC场景中，该标识可以是逻辑信道(logical channel，LCH)标识、小区组(cell group)标识、基站标识等，在CA场景中，该标识可以是逻辑信道标识、小区组标识、RLC标识等。
在一种可能的设计中，在DC场景中，第一时延包括终端设备的PDCP实体从上层收到第一数据包到终端设备获得向第一网络设备发送第一数据包的上行授权之间的时延。
或者，第二时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第二网络设备发送第二数据包的上行授权之间的时延。
在一种可能的设计中，在CA场景中，第一时延包括终端设备的PDCP实体从上层收到第一数据包到终端设备获得向第一RLC实体发送第一数据包的上行授权之间的时延。
或者，第二时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第二RLC实体发送第二数据包的上行授权之间的时延。
在一种可能的设计中，在获取第二信息之前，还包括：从第一网络设备接收第五指示信息，第五指示信息用于指示终端设备获取第二信息。可选的，第五指示信息中还可以携带第一DRB的标识。实施该过程，可以按照DRB粒度进行时延统计的配置，从而实现了灵活配置DRB时延统计。
在一种可能的设计中，该方法还包括：从第一网络设备接收第七指示信息，第七指示信息用于指示终端设备停止获取第二信息。可选的，第七指示信息中还可以携带第一DRB 的标识。实施该过程，可以灵活配置DRB时延统计，可以减少UE的负荷，降低UE的处理开销。
第五方面，本申请实施例提供了另一种通信方法，应用于网络侧，该方法包括：获取第五时延，以及向第一网络设备发送第五时延，其中，该第五时延为在第二路径上的网络侧时延，该第二路径用于传输第二数据包，第二数据包属于第一DRB，用于传输第一DRB的数据包的路径包括两条或多条。
实施本申请实施例，针对一个DRB对应两个或多个RLC实体承载(即一个DRB的数据包在两条或多条路径上传输)的场景，UE可以分别对每条路径进行UE侧的时延统计，网络设备可以分别对每条路径进行网络侧的时延统计，最终确定出该DRB的上行时延，实现了对DRB时延的统计，网络侧统计出DRB的时延可以便于网络侧基于该时延调整资源分配以满足业务对时延的需求。
在一种可能的设计中，本申请实施例可以应用于DC场景。这种情况下，在第一路径上的网络侧时延为第一网络设备在第一路径上的时延，在第二路径上的网络侧时延为第二网络设备在第二路径上的时延。
在一种可能的设计中，第五时延包括第二网络设备的HARQ传输时延、第二网络设备的RLC实体的时延和第二接口的时延中的至少一个，该第二接口为第一网络设备和第二网络设备之间的通信接口。
在一种可能的设计中，在获取第五时延之前，还包括：从第一网络设备接收第二指示信息，第二指示信息用于指示第二网络设备获取第五时延。可选的，第二指示信息中还可以携带第一DRB的标识。实施该过程，可以按照DRB粒度进行时延统计的配置，从而实现了灵活配置DRB时延统计。
在一种可能的设计中，上述方法还包括：从第一网络设备接收第四指示信息，该第四指示信息用于指示第二网络设备停止获取第五时延。可选的，第四指示信息中还可以携带第一DRB的标识。实施该过程，可以灵活配置DRB时延统计，可以减少第二网络设备的负荷，降低第二网络设备的处理开销。
第六方面，本申请实施例提供了一种通信装置，该通信装置可包括至少一个功能模块或单元，用于相应的执行第一方面所提供的通信方法，或者第一方面可能的实施方式中的任意一种所提供的通信方法。该通信装置可以为网络设备或者可以用于网络设备的部件(例如芯片或者电路)。一种可能的方式中，该通信装置可以包括收发单元和处理单元。
收发单元，用于从终端设备接收第一信息，其中，该第一信息包括第一时延和第二时延的信息，或者，第一信息包括第三时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第三时延为终端设备根据终端设备在第一路径上的时延和终端设备在第二路径上的时延得到的，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。
处理单元，用于根据第一信息、第四时延和第五时延确定第一DRB的上行时延，其中，第四时延为在第一路径上的网络侧时延，第五时延为在第二路径上的网络侧时延。
可选的，上述收发单元可以通过收发器实现，收发器可以为收发电路或者接口电路等。处理单元可以通过处理器实现。可选的，该通信装置还可以包括存储器，用于存储代码(程 序)或者数据。
第七方面，本申请实施例提供了一种通信装置，该通信装置可包括至少一个功能模块或单元，用于相应的执行第二方面所提供的通信方法，或者第二方面可能的实施方式中的任意一种所提供的通信方法。该通信装置可以为终端设备或者可以用于终端设备的部件(例如芯片或者电路)。一种可能的方式中，该通信装置可以包括处理单元和收发单元。
处理单元，用于获取第一信息，其中，该第一信息包括第一时延和第二时延的信息，或者，第一信息包括第三时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第三时延为终端设备根据终端设备在第一路径上的时延和终端设备在第二路径上的时延得到的，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。
收发单元，用于向第一网络设备发送第一信息。
可选的，上述收发单元可以通过收发器实现，收发器可以为收发电路或者接口电路等。处理单元可以通过处理器实现。可选的，该通信装置还可以包括存储器，用于存储代码(程序)或者数据。
第八方面，本申请实施例提供了一种通信装置，该通信装置可包括至少一个功能模块或单元，用于相应的执行第三方面所提供的通信方法，或者第三方面可能的实施方式中的任意一种所提供的通信方法。该通信装置可以为网络设备或者可以用于网络设备的部件(例如芯片或者电路)。一种可能的方式中，该通信装置可以包括收发单元和处理单元。
收发单元，用于从终端设备接收第二信息，第二信息包括第一时延或第二时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。
处理单元，用于根据第二信息和第六时延确定第一DRB的上行时延，如果第二信息包括第一时延的信息，第六时延为在第一路径上的网络侧的时延，如果第二信息包括第二时延的信息，第六时延为在第二路径上的网络侧的时延。
可选的，上述收发单元可以通过收发器实现，收发器可以为收发电路或者接口电路等。处理单元可以通过处理器实现。可选的，该通信装置还可以包括存储器，用于存储代码(程序)或者数据。
第九方面，本申请实施例提供了另一种通信装置，该通信装置可包括至少一个功能模块或单元，用于相应的执行第四方面所提供的通信方法，或者第四方面可能的实施方式中的任意一种所提供的通信方法。该通信装置可以为终端设备或者可以用于终端设备的部件(例如芯片或者电路)。一种可能的方式中，该通信装置可以包括处理单元和收发单元。
处理单元，用于获取第二信息，第二信息包括第一时延或第二时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。
收发单元，用于向第一网络设备发送第二信息。
可选的，上述收发单元可以通过收发器实现，收发器可以为收发电路或者接口电路等。 处理单元可以通过处理器实现。可选的，该通信装置还可以包括存储器，用于存储代码(程序)或者数据。
第十方面，本申请实施例提供了一种通信装置，该通信装置可包括至少一个功能模块或单元，用于相应的执行第五方面所提供的通信方法，或者第五方面可能的实施方式中的任意一种所提供的通信方法。该通信装置可以为网络设备或者可以用于网络设备的部件(例如芯片或者电路)。一种可能的方式中，该通信装置可以包括收发单元和发送单元。
处理单元，用于获取第五时延，第五时延为在第二路径上的网络侧时延，该第二路径用于传输第二数据包，第二数据包属于第一DRB，用于传输第一DRB的数据包的路径包括两条或多条。
收发单元，用于向第一网络设备发送第五时延。
可选的，上述收发单元可以通过收发器实现，收发器可以为收发电路或者接口电路等。处理单元可以通过处理器实现。可选的，该通信装置还可以包括存储器，用于存储代码(程序)或者数据。
第十一方面，本申请实施例提供了一种网络设备，该用于执行第一方面、或第三方面或第五方面描述的通信方法。该网络设备可包括：存储器以及与所述存储器耦合的处理器、发射器、接收器。示例性的，所述发射器用于支持网络设备执行第一方面、或第三方面或第五方面所提供的通信方法中网络设备发送信息的步骤。所述接收器用于支持网络设备执行第一方面、或第三方面或第五方面所提供的通信方法中网络设备接收信息的步骤。处理器用于支持网络设备执行第一方面、或第三方面或第五方面所提供的通信方法中网络设备除发送信息以及接收信息以外的其他处理步骤。需要说明的是，本申请实施例中的发射器和接收器可以集成在一起，也可以通过耦合器耦合。所述存储器用于存储第一方面、或第三方面或第五方面描述的通信方法的实现代码，所述处理器用于执行所述存储器中存储的程序代码，使得该网络设备执行第一方面、或第三方面或第五方面所提供的通信方法。存储器和处理器可以集成在一起，也可以通过耦合器耦合。
第十二方面，本申请实施例提供了一种终端设备，该用于执行第二方面或第四方面描述的通信方法。该终端设备可包括：存储器以及与所述存储器耦合的处理器、发射器、接收器。示例性的，所述发射器用于支持终端设备执行第二方面或第四方面所提供的通信方法中终端设备发送信息的步骤。所述接收器用于支持终端设备执行第二方面或第四方面所提供的通信方法中终端设备接收信息的步骤。处理器用于支持终端设备执行第二方面或第四方面所提供的通信方法中终端设备除发送信息以及接收信息以外的其他处理步骤。需要说明的是，本申请实施例中的发射器和接收器可以集成在一起，也可以通过耦合器耦合。所述存储器用于存储第二方面或第四方面描述的通信方法的实现代码，所述处理器用于执行所述存储器中存储的程序代码，即执行第二方面或第四方面所提供的通信方法。存储器和处理器可以集成在一起，也可以通过耦合器耦合。
第十三方面，本申请实施例提供了一种通信系统，包括终端设备和第一网络设备。示例性的，所述第一网络设备可以是如前述第六方面所描述的通信装置或第十一方面所描述的网络设备，所述终端设备可以是如前述第七方面所描述的通信装置或第十二方面所描述的终端设备。或者，所述第一网络设备可以是如前述第八方面所描述的通信装置或第十一 方面所描述的网络设备，所述终端设备可以是如前述第九方面所描述的通信装置或第十二方面所描述的终端设备。
在一种可能的设计中，该通信系统还包括第二网络设备，所述第二网络设备可以是如前述第十方面所描述的通信装置或第十一方面所描述的网络设备。
第十四方面，本申请实施例提供了一种计算机可读存储介质，所述可读存储介质上存储有指令，当其在计算机上运行时，使得计算机执行上述任一方面描述的通信方法。
第十五方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一方面描述的通信方法。
第十六方面，本申请实施例提供了一种通信芯片，该通信芯片可包括：处理器，以及耦合于所述处理器的一个或多个接口。示例性的，所述处理器可用于从存储器中调用上述任一方面所提供的通信方法的实现程序，并执行该程序包含的指令。所述接口可用于输出所述处理器的处理结果。
附图说明
下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请实施例提供的一种无线通信系统示意图；
图2是本申请实施例涉及的用户面(user plant，UP)的协议层的架构示意图；
图3是本申请实施例提供的一种网络设备的协议栈示意图；
图4是本申请实施例提供的基于QoSflow的QoS架构示意图；
图5是本申请实施例提供的QoS flow到DRB的映射过程示意图；
图6是本申请实施例提供的多种不同DRB类型的示意图；
图7是本申请实施例提供的多种不同DRB类型的示意图；
图8是本申请实施例提供的一种上行数据传输过程的示意图；
图9是本申请实施例提供的一种下行数据传输过程的示意图；
图10是本申请实施例提供的另一种上行数据传输过程的示意图；
图11是本申请实施例提供的另一种下行数据传输过程的示意图；
图12是本申请实施一提供的一种通信方法的流程示意图；
图13是本申请实施二提供的一种通信方法的流程示意图；
图14是本申请实施三提供的一种通信方法的流程示意图；
图15是本申请实施四提供的一种通信方法的流程示意图；
图16是本申请实施五提供的一种通信方法的流程示意图；
图17是本申请实施六提供的一种通信方法的流程示意图；
图18是本申请实施例提供的一种通信装置的硬件结构示意图；
图19是本申请实施例提供的另一种通信装置的硬件结构示意图；
图20是本申请实施例提供的一种网络设备的逻辑结构示意图；
图21是本申请实施例提供的一种通信装置的硬件结构示意图；
图22是本申请实施例提供的一种终端设备的逻辑结构示意图；
图23是本申请实施例提供的一种通信芯片的结构示意图。
具体实施方式
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。
首先对本申请涉及的通信系统进行介绍。参考图1，图1示出了本申请实施例涉及的无线通信系统。无线通信系统100可以工作在授权频段，也可以工作在非授权频段。无线通信系统100不限于长期演进(long term evolution，LTE)系统，还可以是5G系统或者新无线技术(new radio，NR)系统，或者可以是其他演进系统等。可以理解的，非授权频段的使用可以提高无线通信系统100的系统容量。如图1所示，无线通信系统100包括：一个或多个接入网设备101，一个或多个终端设备102，以及核心网103。其中：
接入网设备101可以通过一个或多个天线来和终端设备102进行无线通信。各个接入网设备101均可以为各自对应的覆盖范围104提供通信覆盖。接入网设备101对应的覆盖范围104可以被划分为多个扇区(sector)，其中，一个扇区对应一部分覆盖范围(未示出)。
在本申请实施例中，接入网设备101可以包括：演进的节点B(evolved NodeB，eNB或者eNodeB)，或下一代节点(next-generation Node B，gNB)等等。无线通信系统100可以包括几种不同类型的接入网设备101，例如宏基站(macro base station)、微基站(micro base station)等。接入网设备101可以应用不同的无线技术，例如小区无线接入技术，或者无线局域网(wireless local area networks，WLAN)无线接入技术。另外，接入网设备101还可称为基站、接入点(access point，AP)、收发点(transmission receive point，TRP)、中心单元(central unit，CU)或其他网络实体，并且可以包括以上网络实体的功能中的一些或所有功能。
在本申请实施例中，终端设备102是一种具有无线收发功能的设备。可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球上等)。所述终端设备可以是手机(mobile phone)、平板电脑(Pad)、便携电脑、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智能汽车、智慧家庭(smart home)中的无线终端等等。本申请的实施例对应用场景不做限定。终端设备又可以称为UE、终端(terminal)、接入终端、UE单元、UE站、移动设备、移动站、移动台(mobile station)、移动终端、移动客户端、移动单元(mobile unit)、远方站、远程终端设备、远程单元、无线单元、无线通信设备、用户代理或用户装置等。
具体的，接入网设备101通过无线接口105与终端设备102通信。具体的，接入网设备101可用于接口106(如S1接口或NG接口)向核心网103传输控制信息或者用户数据。具体的，接入网设备101与接入网设备101之间也可以通过接口107(如X2/Xn接口)，直接地或者间接地，相互通信。
核心网103设备(比如5G核心网)包括但不限于：接入移动管理功能(access and mobility management function，AMF)实体、会话管理功能(session management function，SMF)实体、用户面功能(user plane function，UPF)实体等。其中，AMF用于进行接入和移动性管理，与 无线接入网(radio access network，RAN)设备、SMF等网元进行交互以及信令转发等功能。SMF用于管理用户的协议数据单元(protocol data unit，PDU)会话(session)的创建、删除等，维护PDU会话上下文及用户面转发管理通道信息。UPF用于接收来自终端设备102的数据包，并进行数据包的转发。UPF还用于服务质量(quality of service，QoS)控制、计费信息统计等。
核心网103设备(比如4G核心网)包括但不限于：MME、服务网关(serving gateway，S-GW)实体、分组数据网络网关(packet data network gateway，PDN-GW)实体等。其中，MME用于进行接入控制，合法监听，用户漫游控制，包括安全和许可控制,以及移动性管理，与无线接入网设备、S-GW等网元进行交互以及信令转发等功能。S-GW用于进行无线接入网设备间切换时，可以作为本地锚定点，并协助完成无线接入网设备的重排序功能；在不同接入系统间切换时，作为移动性锚点，同样具有重排序功能；执行合法侦听功能；进行数据包的路由和前转；在上行和下行传输层进行分组标记；空闲状态下，下行分组缓冲和发起网络触发的服务请求功能；用于运营商间的计费等功能。PDN-GW用于用户的包过滤功能、合法侦听功能、UE的IP地址分配功能、在上/下行链路中进行数据包传输层标记、进行上/下行业务等级计费以及业务级门控、进行基于业务的上/下行速率的控制等功能。
其中，4G基站与4G核心网之间的接口称为S1口，5G基站与5G核心网之间的接口称为NG口，两个4G基站之间的接口称为X2口，两个5G基站之间的接口称为Xn口。当UE连接到4G核心网时，同时服务该UE的4G基站和5G基站之间的接口称为X2口。当UE连接到5G核心网时，同时服务该UE的4G基站和5G基站之间的接口称为Xn口。
需要说明的，图1示出的无线通信系统100仅仅是为了更加清楚的说明本申请的技术方案，并不构成对本申请的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
除非特殊说明，下述各实施例中涉及的网络设备可以理解为接入网设备。
本申请实施例中，为终端设备提供数据传输服务的接入网设备的数量可以是一个，也可以是多个。例如，为UE提供数据传输服务的基站包括两个，其中一个为主站，另一个为辅站。主站和辅站均可以向UE发送下行数据，也均可以接收UE发送的上行数据。
需要说明的是，本申请实施例中的术语“系统”和“网络”可被互换使用。“多个”是指两个或两个以上，鉴于此，本申请实施例中也可以将“多个”理解为“至少两个”。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。
下面介绍一下本申请实施例中涉及的无线网络的协议层。参见图2，是本申请实施例中涉及的用户面(user plant，UP)的协议层的架构示意图。对于用户面而言：UE、基站(如gNB)的协议层由上至下分别为：服务数据适配协议(service data adaptation protocol，SDAP)层、分组数据汇聚协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、介质访问控制(media access control，MAC)层和物理(physical，PHY)层。
其中，SDAP层为5G中新引入的一个协议层。负责把第5代核心网(5generationcore， 5GC)下来的各个服务质量流(Qos flow)映射到无线接入层的DRB，即根据Qos flow对应的业务属性，把Qos flow对应的数据包放在对应的DRB上传输。
PDCP层可执行诸如安全性、头压缩、加密和切换之类的服务。PDCP层可以存在多个PDCP实体，每个实体承载一个无线承载(RB)的数据。PDCP层可以配置保证向上提交的数据是有序的(即按序提交)。
RLC层可执行诸如分段、重新装配、重传等服务。RLC层可以存在多个RLC实体，每个RLC实体为每个PDCP实体提供服务。
MAC层可对逻辑信道上的业务提供数据传输服务，执行诸如调度、混合自动重传请求(hybrid automatic repeat request，HARQ)的确认和否定服务。
PHY层可对MAC层传下的数据进行编码和传输。
相应的，对于控制面而言：UE、基站的协议层由上至下分别为：RRC层、PDCP层、RLC层、MAC层和PHY层。
其中，RRC层用于执行广播、寻呼、RRC链接建立、无线承载控制、移动、UE测量上报控制等。
对于发送端而言，每一层处理完数据之后的数据，在本层称为PDU。对于每一层而言，从上一层输入的数据称为本层的服务数据单元(service data unit，SDU)。比如PDCP层输入给RLC层的数据，对于PDCP层而言，称为PDCP PDU，对于RLC层而言，称为RLC SDU。
在本申请实施例中，接入网设备101可以是集中单元(centralized unit，CU)和分布单元(distribute unit，DU)分离架构的基站(如gNB)。该基站可以与核心网设备相连(例如可以是4G的核心网，也可以是5G的核心网等)。CU和DU可以理解为是对该基站从逻辑功能角度的划分。CU和DU在物理上可以是分离的也可以部署在一起。多个DU可以共用一个CU。一个DU也可以连接多个CU。CU和DU之间可以通过接口相连，例如可以是F1接口。
可选的，CU的功能和DU的功能可以根据无线网络的协议层进行划分。例如RRC层、SDAP层以及PDCP层的功能设置在CU，而RLC层、MAC层、PHY层等的功能设置在DU。可以理解，上述对CU的功能和DU的功能按照协议层进行划分仅仅是一种举例，也可以按照其他的方式进行划分。例如，CU或者DU可以具有更多协议层的功能，或者，CU或DU还可以具有协议层的部分处理功能。示例性的，可以将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。
或者，CU的功能和DU的功能还可以按照业务类型或者其他系统需求进行划分。例如按时延划分，将处理时间需要满足时延要求的功能设置在DU中，不需要满足该时延要求的功能设置在CU中。
或者，CU可以具有核心网的一个或多个功能。一个或者多个CU可以集中设置，也分离设置。例如CU可以设置在网络侧方便集中管理。DU可以具有多个射频功能，也可以将射频功能拉远设置。
应理解，CU的功能可以由一个实体来实现，也可以由不同的实体实现。可选的，可以对CU的功能进行进一步切分，示例性的，图3为本申请实施例提供的一种网络设备的协 议栈示意图，如图3所示，可以将CU的控制面(control plant，CP)和用户面(user plant，UP)分离，即CU的控制面(CU-CP)和CU用户面(CU-UP)。其中，CU-CP和CU-UP可以由不同的功能实体来实现，所述CU-CP和CU-UP可以与DU相耦合，共同完成基站的功能。一种可能的方式中，CU-CP负责控制面功能，主要包含RRC层的功能和PDCP-C的功能。PDCP-C主要负责控制面数据的加解密、完整性保护、数据传输等。CU-UP负责用户面功能，主要包含SDAP层的功能和PDCP-U。其中，PDCP-U主要负责数据面的加解密、完整性保护、头压缩、序列号维护、数据传输等。CU-CP和CU-UP可以通过通过接口相连，例如可以是E1接口连接。CU-CP代表基站可以通过接口和核心网设备连接，通过控制面接口(例如，F1-C(控制面))和DU连接，CU-UP通过用户面接口(例如，F1-U(用户面))和DU连接。可选的，还有一种可能的实现是PDCP-C的功能也在CU-UP侧(图中未示出)。
基于上述无线网络的协议层，下面对DRB涉及的数据传输内容进行介绍。
对于每个UE而言，核心网为其建立一个或多个PDUsession。RAN(例如基站)为每个PDU session建立一个或多个DRB。DRB可以理解为是基站和UE之间的数据承载，该数据承载中的数据包具备相同的转发处理。PDU session可以理解为是UE和数据网络(data network，DN)之间提供PDU连接服务的连接。一个PDU session内，具备相同QoS需求的数据流即为QoS flow。
在5G场景下，基于QoSflow的QoS架构如图4所示，该架构适用于NR系统中的RAN设备，如gNB连接到5GC，也适用于演进的通用陆基无线接入(evolved universal terrestrial radio access，E-UTRA)系统中的RAN设备，如eNB连接到5GC。对于每个UE而言，5GC为其建立一个或多个PDUsession。对于每个UE而言，RAN为每个PDU session建立一个或多个DRB。其中，QoS flow是指一个PDU session内，具备相同QoS需求的数据流。其中，可以是多个具有相同QoS需求的IP flow。
把基站和UE之间的传输称为接入层(access stratum，AS)，把UE和核心网之间的传输称为非接入层(non-access stratum，NAS)。基于QoS flow的QoS架构中，主要包括接入层AS和非接入层NAS的QoS flow映射。NAS层主要负责IP flow或其它类型数据包和QoS flow的映射关系，由核心网用户面功能实体UPF产生下行的QoS flow，例如通过包检测规则(packet detection rule，PDR)来实现。终端产生上行的QoS flow，例如通过Qos rules来实现。AS层主要负责QoS flow与DRB的映射关系(即通过AS的mapping rule来实现)，网络侧(例如基站)配置QoS flow和DRB的映射关系，并在空口的DRB中为QoS flow提供QoS服务。
在NAS层，Qos flow是每个PDU session中Qos差异化的最小粒度。在每个PDU session中，在NG-U的数据包装头中携带了一个Qos Flow ID(QFI)来标识该数据包属于哪个Qos Flow。PDR和Qos rule都是通过包过滤器(Packet filter)来识别对应数据包类型，从而知道该包属于哪个Qos flow。Packet filter通过识别数据包的特性来判断该数据包，比如对于IP数据包，通过该数据包的源IP地址或者目标IP地址，源端口号或目标端口号，传输层协议号等来识别包的类型。对于UE而言，Qos rule可以通过5GC通知UE，也可以通过UE内部预先配置，还可以通过反射Qos(Reflective QoS)特性来获得。Reflective QoS特性是指UE可以通过下行业务的数据包与Qos flow对应关系来生成上行业务的数据包与Qos flow 的对应关系。
核心网可通过控制面或用户面的方式来激活Reflective QoS特性，具体的，核心网可通过非接入层消息通知终端QoS flow激活Reflective QoS特性，例如将在QoS flow的规则中携带一个指示该QoS flow激活Reflective QoS特性(反射服务流特性)的指示信息，或者，核心网在发送到无线接入网侧的数据包包头中携带反射服务流特性指示(reflective QoS indicator，RQI)，以指示该数据包具备Reflective QoS特性。
QoS flow到DRB的映射过程可参见图5所示，在连接到下一代核心网(next generation core，NGC)的无线接入网侧的协议栈中，在用户面PDCP层之上是SDAP协议层，SDAP协议层负责将来自非接入层的QoS flow映射到接入层的DRB上，比如把PDU session 1中的Qos flow 1映射到DRB1，把PDU session 1中的Qos flow 2映射到DRB2。执行SDAP协议的SDAP实体是按会话(session)建立的，还负责在空口协议栈中添加上行QoS flow id和/或下行QoS flow id。其中，在进行QoS flow到DRB的映射过程中，可将同一sesison内的多个QoS flow映射到同一DRB中，基于基站和核心网之间用户面数据包包头中QoS flow id对应的QoS profile，可使同一DRB中的数据包包得到相同的转发处理。其中，QoS profile是指QoS flow id对应的QoS参数，包含时延、丢包率、优先级、保证速率、最大速率、速率不满足的通知指示等其中一项或多项。不同session的QoS flow不能映射到同一DRB中。每一终端的每一session可对应一个默认DRB(default DRB)，终端将没有配置上行QoS flow和DRB映射关系的QoS flow映射到default DRB中。RAN侧的gNB可通过RRC信令或反射映射(Reflective mapping)的方式给终端配置上行QoS flow和DRB的映射关系。Reflective mapping是指下行数据包中携带QoS flow id，终端检测到QoS flow id，并将上行相同QoS flow id的QoS flow映射到同一DRB中。另外基站还可以通过RRC消息通知UE对应的DRB中上或/和下行是否要携带SDAP报头。当配置下行需要携带SDAP报头时，基站的SDAP层需要在下行方向为每个数据包携带QFI，即在SDAP PDU中携带QFI。当配置上行需要携带SDAP报头时，UE的SDAP层需要在下行方向为每个数据包携带QFI，即在SDAP PDU中携带QFI。
当UE连接到4G演进分组核心网(evolved packet core，EPC)时，一个演进数据包传输系统(evolved packet system，EPS)承载与一个演进的无线接入承载(evolved radio access bearer，E-RAB)一一对应。EPS承载或E-RAB是连接到EPC网络时进行QoS控制的最少粒度。
而5G中引入多无线电双连接(multi-radio dual connectivity，MR-DC)，网络侧可以通过两个或多个基站为UE提供通信服务。这两个或多个基站可以属于同一个无线接入制式(radio access technology，RAT)，也可以属于不同的无线接入制式。比如一个基站属于LTE，一个属于NR。而且MR-DC中的核心网可能是4G核心网，也可能是5G核心网。
在MR-DC中，一个DRB可以有各种形式，各种形式是以PDCP层和RLC/MAC/PHY层所属的基站来区分的。按照PDCP层所属基站来区分，DRB分为主站终止的承载(master node terminated bearer，MNterminated bearer)(即承载是终止在主站上，也可以称为和核心网的用户面连接终止于主站)和辅站终止的承载(secondary nodeterminated bearer，SN terminated bearer)(即承载是终止在辅站上，也可以称为和核心网的用户面连接终止于辅站)。 按照RLC/MAC/PHY层所属的基站来区分，DRB可以分为主小区组承载(master cell groupbearer，MCGbearer)，辅小区组承载(secondarycell group，SCG bearer)，分流承载(split bearer)。
其中，MCG bearer是指一个DRB对应的RLC承载只在主站。该DRB在主站可能具有一个或多个RLC实体，比如对于载波聚合(carrier aggregation，CA)数据包复制场景，可以在主站上具有两个RLC承载。
SCG bearer是指一个DRB对应的RLC承载只在辅站。该DRB在辅站可能具有一个或多个RLC实体，比如对于CA数据包复制场景，可以在主站上具有两个RLC承载。
split bearer是指一个DRB对应的RLC承载在主站和辅站都有。比如一个DRB中的数据可以分流到两个基站中。
MCG指MR-DC中主站上的一组服务小区，这些服务小区包括主小区和可选的一个或多个辅小区。SCG指MR-DC中辅站上的一组服务小区，这些服务小区包括主辅小区和可选的一个或多个辅小区。
MN terminated bearer/SN terminated bearer可以和MCG bearer/SCG bearer/split bearer进行各种组合组成不同的DRB类型。如图6和图7所示。其中，图7是以主站为NR系统中的基站，辅站为E-UTRA系统中的基站，且UE连接到5G核心网为例。
如图7所示，以主站终止的承载为例说明下split bearer。和核心网的用户面连接终止于主站，主站的PDCP实体(即图7中的NR PDCP)将属于某一DRB(假设为DRB1)的数据包发送给主站的RLC实体(即图7中的NR RLC)，NR RLC收到NR PDCP层发送的DRB1的数据包后，将数据包发送给NR MAC层，NR MAC层收到NR RLC层发送的DRB1的数据包后，将数据包发送给NR PHY层，NR PHY层收到该DRB1的数据包后，将其发给发送给UE，并且主站的PDCP实体(即图7中的NR PDCP)还会将DRB1的数据包发给辅站的RLC实体(即图7中的E-UTRA RLC)，E-UTRA RLC收到NR PDCP层发送的DRB1的数据包后，将数据包发送给E-UTRA MAC层，E-UTRA MAC层收到DRB1的数据包后，将数据包发送给E-UTRA PHY层，E-UTRA PHY层收到该DRB1的数据包后，将其发给发送给UE。这里可以看作两条路径(path)用来传输DRB1的数据包，其中路径1上的协议层实体包括NR PDCP、NR RLC、NR MAC、NR PHY、UE的第一PHY、UE的第一MAC、UE的第一RLC和UE的第一PDCP。路径2上的协议层实体包括NR PDCP、E-UTRA RLC、E-UTRA MAC、E-UTRA PHY、UE的第二PHY、UE的第二MAC、UE的第二RLC和UE的第二PDCP。
在MR-DC场景下，为了保证业务的可靠性，发送端可以通过两个或多个基站将相同的数据包发送给UE。例如，主站会在PDCP层把发往终端设备的数据包(例如是URLLC业务的数据包)复制为两份(或多份)，并通过两个(或多个)不同的基站发送给终端设备，从而提高该业务的可靠性。比如对于MR-DC场景，主站会在PDCP层把数据包(比如PDCP PDU)复制为两份，把两份数据发送给两个基站各自的RLC实体，由两个基站各自的RLC实体将数据包发送给UE，也即是说通过split bearer发送给UE。同样，UE侧在上行DRB的PDCP层也可以把数据包复制为两份(或多份)，把两份(或多份)数据发送给该UE的两个(或多个)RLC实体，其中一个RLC实体将数据包发送给主站，另外一个RLC实体将 数据包发送给辅站，也即是说通过split bearer发送给两个基站。为便于描述，下述实施例中将这种DC场景下的数据包复制方式称为DC复制(duplication)方式。DC duplication方式中，主站和辅站发送给UE的数据包(比如PDCP PDU)是一样的，相应的，UE发送给主站和辅站的数据包(比如PDCP PDU)也是一样的。
除了采用DCduplication方式来保证业务的可靠性以外，在载波聚合(carrier aggregation，CA)场景下，发送端还可以通过一个基站的多个载波或小区将数据包发送给接收端。例如，主站会在PDCP层把发往终端设备的数据包(例如是URLLC业务的数据包，比如PDCP PDU)复制为两份(或多份)，并通过主站的两个或多个RLC实体发送给终端设备，从而提高该业务的可靠性。比如主站会在PDCP层把数据包(比如PDCP Data PDU)复制为两份，把两份数据发送给主站中的两个RLC实体，由两个RLC实体将数据包发送给UE。同样的，UE侧也可以在上行DRB的PDCP层把数据包复制为两份(或多份)，把两份(或多份)数据发送给该UE的两个(或多个)RLC实体，其中一个RLC实体将数据包发送给主站的一个RLC实体，另外一个RLC实体将数据包发送给主站的另一个RLC实体。为便于描述，下述实施例中将这种CA场景下的数据包复制方式称为CA duplication方式。CA duplication方式中，主站的两个RLC实体发送给UE的数据包(比如PDCP PDU)是一样的，相应的，UE发送给主站的两个RLC实体的数据包(比如PDCP PDU)也是一样的。对于CA duplication而言，这两个或多个RLC实体对应相同的MAC实体，但限制这些RLC实体的数据包在不同的载波或小区上发送(比如通过逻辑信道映射限制)。这里也可以看作两条或多条路径(path)用来传输数据包。比如路径1上的协议层实体包括基站的第一PDCP、基站的第一RLC、基站的MAC、基站的PHY、UE的PHY、UE的MAC、UE的第三RLC和UE的第二PDCP。路径2上的协议层实体包括基站的第一PDCP、基站的第二RLC、基站的MAC、基站的PHY、UE的PHY、UE的MAC、UE的第四RLC和UE的第二PDCP。
上述DC duplication和CA duplication方式均为复制(duplication)方式。需要说明的是，除非特别说明，本申请中下文中的DC场景是指包括DC duplication和非duplication的DC。除非特别说明，CA场景是指CA duplication场景。此外，除了将数据包复制为两份(或多份)以外，发送端还可以不采用复制的方式，而是采用分流方式利用两个或多个基站向UE传输数据包。例如，主站在PDCP层把发往终端设备的数据包(例如是URLLC业务的数据包)划分为两部分，其中一部分数据包通过主站的RLC发送给UE，另一部分数据包通过辅站的RLC发送给UE,也即是说通过split bearer发送给UE。相应的，UE在上行DRB的PDCP层也可以把数据包划分为两部分，把其中一部分数据包发送给该UE的一个RLC实体并发送给主站，把剩余的另外一部分数据包发送给该UE的另一个RLC实体并发送给辅站,也即是说通过split bearer发送给两个基站。为便于描述，下述实施例中将这种数据包分流方式称为非duplication方式。非duplication方式中，主站和辅站发送给UE的数据包是不一样的，相应的，UE发送给主站和辅站的数据包也是不一样的。这里可以看作两条或多条路径(path)用来传输DRB的数据包，具体解释同以上DC场景下的解释。
随着通信需求的发展，越来越多的业务需要保证低时延的性能，比如URLLC业务需要时延在0.5ms之内。为了保证业务的性能，运营商需要知道当前网络的时延性能。
目前协议中仅提供了UE与一个基站进行一条路径(path)通信(即一个DRB只对应一 个RLC承载)时的时延统计方法，并未提供针对UE与两个或多个基站进行多条路径通信或者UE与一个基站的多个RLC实体进行多条路径通信时的时延统计方法，也即是说目前协议中并未提供一个DRB对应两个或多个RLC承载时的时延统计方法。本申请针对一个DRB对应两个或多个RLC承载这种情况提出了一种时延统计方法。
本申请中，路径也可以称为支路、通路、链路等。路径可以是指UE与不同的基站之间的路径，也可以是指UE与同一基站的不同RLC实体之间的路径。
比如，DC场景下，主站gNB1和辅站gNB2这两个基站提供两条路径来为UE传输DRB1的数据包。参见图8，是上行数据传输过程的示意图。参见图9，是下行数据传输过程的示意图。这里，针对上行传输过程，路径1中涉及的UE侧的协议层实体由上至下依次包括：PDCP层、RLC层、MAC层和PHY层。路径2中涉及的UE侧的协议层实体由上至下依次包括：PDCP层、RLC层、MAC层和PHY层。并且路径1和路径2中涉及的UE侧的RLC层、MAC层和PHY层是两组不同的协议实体。路径1中涉及的网络侧的协议层实体由下至上依次包括：主站的PHY层、MAC层、RLC层和PDCP层，路径2中涉及的网络侧的协议层实体由下至上依次包括：辅站的PHY层、MAC层和RLC层。针对下行传输过程，路径3中涉及的网络侧的协议层实体由上至下依次包括：主站的PDCP层、主站的RLC层、主站的MAC层和主站的PHY层，路径4中涉及的网络侧的协议层实体由上至下依次包括：辅站的RLC层、辅站的MAC层和辅站的PHY层，路径3中涉及的UE侧的协议层实体由下至上依次包括：UE的PHY层、UE的MAC层、UE的RLC层、UE的PDCP层。路径4中涉及的UE侧的协议层实体由下至上依次包括：UE的PHY层、UE的MAC层、UE的RLC层、UE的PDCP层。并且路径3和路径4中涉及的UE侧的RLC层、MAC层、RLC层、PDCP层是两组不同的协议实体。需要说明的是，本申请实施例中示意图是以UE连接到5G核心网的协议实体为示例，本申请还可以用于UE连接到4G核心网的场景中(比如没有SDAP协议层)，本申请并不做具体的限定。对于同一个设备而言(终端设备或网络设备)，虽然图8或图9中是以多条路径对应不同的PHY实体描述的，实际应用中，不同路径还可以对应同一PHY实体，但是不同RLC实体的数据包在不同的载波或小区上发送。
又比如，CA场景下，主站gNB1这一个基站提供两条路径来为UE传输DRB1的数据包。参见图10，是上行数据传输过程的示意图，参见图11，是下行数据传输过程的示意图。这里，针对上行传输过程，路径5中涉及的UE侧的协议层实体由上至下依次包括：UE的PDCP层、UE的第三RLC层、UE的MAC层和UE的PHY层。路径6中涉及的UE侧的协议层实体由上至下依次包括：UE的PDCP层、UE的第四RLC层、UE的MAC层和UE的PHY层。并且路径5和路径6中涉及的UE侧的RLC层是两个不同的协议实体，涉及的UE侧的MAC层和PHY层是两组相同的协议实体。路径5中涉及的网络侧的协议层实体由下至上依次包括：gNB1的PHY层、gNB1的MAC层、gNB1的第一RLC层和gNB1的PDCP层，路径6中涉及的网络侧的协议层实体由下至上依次包括：gNB1的PHY层、gNB1的MAC层、gNB1的第二RLC层和gNB1的PDCP层。并且路径5和路径6中涉及的网络侧的RLC层是两个不同的协议实体，涉及的网络侧的MAC层和PHY层是两组相同的协议实体。gNB1通过两个RLC实体来为UE提供两条路径传输DRB1的数据包。同 理，针对下行传输过程，路径7中涉及的网络侧的协议层实体由上至下依次包括：gNB1的PDCP层、gNB1的第一RLC层、gNB1的MAC层和gNB1的PHY层，gNB1的另一条路径中涉及的网络侧的协议层实体由上至下也是依次包括：gNB1的PDCP层、gNB1的第二RLC层、gNB1的MAC层和gNB1的PHY层。并且这2条路径中涉及的网络侧的RLC层是两个不同的协议实体，涉及的网络侧的MAC层和PHY层是两组相同的协议实体。路径7中涉及的UE侧的协议层实体由下至上依次包括：UE的PHY层、UE的MAC层、UE的第三RLC层和UE的PDCP层。另一条路径中涉及的UE侧的协议层实体由下至上也是依次包括：UE的PHY层、UE的MAC层、UE的第四RLC层和UE的PDCP层。并且这2条路径中涉及的UE侧的RLC层是两个不同的协议实体，涉及的UE侧的MAC层和PHY层是两组相同的协议实体。对于同一个设备而言(终端设备或网络设备)，虽然图10或图11中不同的RLC对应同一PHY实体，但是不同RLC实体的数据包在不同的载波或小区上发送。此外，对于同一个设备而言(终端设备或网络设备)，虽然图10或图11中是以多条路径对应同一PHY实体描述的，实际应用中，不同路径还可以对应不同的PHY实体。
本申请中的上下行的时延是分段统计的，上行时延分为D1和D2两段统计。D1可以理解为UE侧的时延。D1包括UE的PDCP从上层收到数据包到得到了发送该数据包的上行授权之间的时间。该时延中也包括了从UE发送调度请求或随机接入到得到上行授权的时延。D1由UE进行统计并上报给网络侧。D2可以理解为网络侧的时延，包括HARQ传输或重传时延、RLC侧时延(例如处理时延)、F1口时延、PDCP时延(比如PDCP重排序时延)、Xn口时延中的一种或多种。例如，如图8所示，路径1上的D2包括：第一网络设备gNB1的HARQ传输或重传时延、gNB1的RLC侧时延(例如处理时延)、gNB1的F1口时延和gNB1的PDCP时延(比如PDCP重排序时延)。路径2上的D2包括：第二网络设备gNB2的HARQ传输或重传时延、gNB2的RLC侧时延(例如处理时延)、gNB1与gNB2的Xn口时延和gNB1的PDCP时延(比如PDCP重排序时延)。其中，gNB2的HARQ传输或重传时延、gNB2的RLC侧时延(例如处理时延)、gNB1与gNB2的Xn口时延由gNB2获取并发送给gNB1。gNB1负责统计gNB1的PDCP时延，结合gNB2发送的gNB2的HARQ传输或重传时延、gNB2的RLC侧时延(例如处理时延)、gNB1与gNB2的Xn口时延确定路径2的D2。或者gNB2的HARQ传输或重传时延、gNB2的RLC侧时延(例如处理时延)由gNB2获取并发送给gNB1。gNB1负责统计gNB1与gNB2的Xn口时延、gNB1的PDCP时延，结合gNB2发送的gNB2的HARQ传输或重传时延、gNB2的RLC侧时延(例如处理时延)确定路径2的D2。Xn口时延可以由第一网络设备统计，也可以由第二网络设备统计。
对于下行时延而言，下行时延包括PDCP层时延(比如CU-UP的时延)、F1-U时延、HARQ传输或重传时延、RLC侧时延(例如处理时延)中的一种或多种。如下图9所示，下行时延为从PDCP的上一层收到数据包到MAC层从确定该包被UE正确接收到(比如按照基站从UE收到的HARQ反馈确定该包被UE正确接收)的时间段。其中CU-UP的时延可以为：CU-UP通过NG-U收到数据包到把该数据包发送给CU-DU的时间段。
本申请中，由基站来确定上行或下行时延。并且可以按照DRB粒度进行时延统计，基站在得到DRB时延结果后可以再转化为QoS flow级别的时延(映射到同一个DRB中的所 有QoS flow具有相同的QoS处理)进而发送给核心网。核心网可以监控传输路径的时延(空口时延+接入网到核心网之间的时延)，以确定网络能否满足不同业务的时延需求，或者，便于核心网调整网络的资源分配，以满足不同业务的时延需求。
下面针对一个DRB对应两个或多个RLC承载时基站如何确定上行时延进行详细介绍。
实施例一
可参见图12，是本申请实施例一提供的一种通信方法的流程示意图。该方法包括步骤S201-S204。其中，
S201：终端设备生成第一信息，第一信息包括第一时延和第二时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。
S202：终端设备向第一网络设备发送第一信息，相应的，第一网络设备从终端设备接收第一信息。
S203：第二网络设备向第一网络设备发送第五时延，第一网络设备从第二网络设备接收第五时延，第五时延为在第二路径上的网络侧时延。
S204：第一网络设备根据第一时延、第二时延、第四时延和第五时延确定第一DRB的上行时延，第四时延为在第一路径上的网络侧时延。
其中，步骤S202和步骤S203的执行先后顺序不作限定。
本实施例可以应用于DC场景。即存在至少两个网络设备与UE进行数据传输。以2个网络设备与UE进行数据传输为例，在第一路径上的网络侧时延为第一网络设备在第一路径上的时延，在第二路径上的网络侧时延为第二网络设备在第二路径上的时延。第一网络设备和第二网络设备可以是基站。第一网络设备和第二网络设备可以为同一制式，也可以为不同制式，例如，第一网络设备为NR中的基站，第二网络设备为LTE中的基站。
第一DRB为某一DRB，该DRB是在第一网络设备上或者该DRB终止在该第一网络设备上。比如当第一网络设备是MN时，该DRB为MN terminated bearer。第一网络设备是SN时，该DRB为SN terminated bearer。若采用DC duplication方式，UE将该DRB的数据包复制为两份，并通过第一路径将一份数据包发送给第一网络设备，以及通过第二路径将另一份数据包发送给第二网络设备。或者，若采用非DCduplication方式，UE将该DRB的数据包划分为两部分，并通过第一路径将其中一部分数据包发送给第一网络设备，以及通过第二路径将剩余部分数据包发送给第二网络设备。需要说明的是，本申请并不限定具体UE如何划分数据包，一种例子是UE根据PDCP层的数据量和RLC层中悬置(悬置是指数据包在等待初始传输，数据包到达RLC层且还没有被调度过)进行初始传输的数据量之和与一个网络侧配置的门限进行比较。终端设备统计的是该DRB分别在两条路径上的UE侧的时延。第一网络设备统计的是该DRB在第一路径上的网络侧时延，第二网络设备统计的是该DRB在第二路径上的网络侧的时延。例如图8中，第一网络设备为gNB1，第二网络设备为gNB2，第一路径为路径1，第二路径为路径2。gNB1统计路径1上的网络侧时延D2，gNB2统计路径2上的网络侧时延，UE分别统计路径1上的终端侧时延D1以 及路径2上的终端侧时延D1。然后，UE将路径1的D1和路径2的D1发送给gNB1，gNB2将路径2的网络侧时延发送给gNB1，由gNB1最终确定DRB1的上行时延。
需要说明的是，第一数据包和第二数据包仅仅为了区分不同的路径上传输的数据，具体应用中，若采用DC duplication方式，则第一数据包和第二数据包可以是相同的若干个数据包，需要说明的是，由于两条路径中的数据包的调度时刻可能不同，UE在统计第一时延和第二时延时，在同一个统计周期内，第一数据包和第二数据包可以是不同的若干个数据包，也可以是相同的若干个数据包。若采用非DC duplication方式，则第一数据包和第二数据包可以是不同的若干个数据包。
可选的，在统计某一条路径上的时延时，可以统计一段时间内该条路径上的平均时延，将该平均时延作为该条路径上的时延。例如，第一网络设备将第一路径上的第一时间窗内的网络侧的平均时延作为在第一路径上的网络侧时延，UE将在第一路径的第二时间窗内的UE侧的平均时延作为在第一路径上的UE侧的时延。第一时间窗和第二时间窗的时长可以相等，也可以不同。第一时间窗和第二时间窗内在第一路径上传输的数据包均属于第一DRB。在第一时间窗和第二时间窗内第一路径上传输的数据包可以完全相同，也可以不同。第一数据包和第二数据包的数量均为一个或多个，第一数据包和第二数据包的数量可以相同也可以不同。
可选的，在DC场景中，UE侧统计的是该DRB在各条路径上的时延。UE统计的第一时延包括UE的PDCP实体从上层收到第一数据包到UE获得向第一网络设备发送第一数据包的上行授权之间的时延。UE统计的第二时延包括UE的PDCP实体从上层收到第二数据包到UE获得向第二网络设备发送第二数据包的上行授权之间的时延。
UE确定UE侧的上行时延的方式可以为：在一定周期内，统计第一路径上每个数据包对应的从PDCP上层服务接入点(service access point，SAP)或从SDAP上层SAP收到该数据包到具有传输该数据包的上行授权之间的时延，然后对这些数据包的时延进行取平均值作为第一时延。同理，在一定周期内，统计第二路径上每个数据包对应的从PDCP上层SAP或从SDAP上层SAP收到该数据包到具有传输该数据包的上行授权之间的时延，然后对这些数据包的时延进行取平均值作为第二时延。可选地，第一路径上的统计周期和第二路径上的统计周期可以相同或者不同，该统计周期可以预先规定或者可以由网络设备配置。
可选的，UE上报第一时延或第二时延的信息时可以携带路径对应的标识，比如逻辑信道(logical channel，LCH)标识(identification，ID)或小区组(cell group)ID或者RLC标识(比如主RLC标识或辅RLC标识)或者基站的标识(比如主站标识或辅站标识)来标识第一时延和第二时延。或者，UE上报时通过两个时延的名称不同或出现的位置不同来隐式标识第一时延和第二时延。
可选的，UE上报第一时延或第二时延的信息时可以携带DRB标识，用于指示上报哪一个DRB的时延信息。
可选的，在DC场景中，第一网络设备统计的第四时延包括第一网络设备的HARQ传输时延、第一网络设备的RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，其中第一接口为第一网络设备的CU与第一网络设备的DU之间的通信接口(即F1接口)。第二网络设备统计的第五时延包括第二网络设备的HARQ传输时 延、第二网络设备的RLC实体的时延、第二接口的时延中的至少一个，其中第二接口为第一网络设备和第二网络设备之间的通信接口(如Xn口，Xn口是主站和辅站之间的接口)。其中，协议实体的时延包括协议层的处理时延或该层从低层接收到数据包至将该数据包发送到上层的时延。
其中，第一网络设备的HARQ传输时延是指第一网络设备获取第一DRB的数据包时第一网络设备的HARQ传输时延，第一网络设备的RLC实体的时延是指第一网络设备获取第一DRB的数据包时第一网络设备的RLC实体的时延，第一网络设备的PDCP实体的时延是指第一网络设备获取第一DRB的数据包时第一网络设备的RLC实体的时延，第一接口的时延是指第一网络设备获取第一DRB的数据包时第一网络设备的第一接口的时延，相应的，第二网络设备的HARQ传输时延是指第二网络设备获取第一DRB的数据包时第二网络设备的HARQ传输时延，第二网络设备的RLC实体的时延是指第二网络设备获取第一DRB的数据包时第二网络设备的RLC实体的时延，第二接口的时延是指第二网络设备获取第一DRB的数据包时第二网络设备的第二接口的时延。
当第一网络设备未采用CU-DU分离架构时，第四时延包括第一网络设备的HARQ传输时延、第一网络设备的RLC实体的时延以及第一网络设备的PDCP实体的时延。第五时延包括第二网络设备的HARQ传输时延和第二网络设备的RLC实体的时延。可选的，第二接口的时延由第一网络设备统计，并且第一网络设备结合第五时延、第二接口的时延、第一网络设备的PDCP层的时延确定第二路径的D2。可选的，第二接口的时延还可以是第二网络设备统计的，这种情况下，第五时延包括第二网络设备的HARQ传输时延、第二网络设备的RLC实体的时延和第二接口的时延，第一网络设备结合第五时延和第一网络设备的PDCP层的时延确定第二路径的D2。
可选的，当第一网络设备采用CU-DU分离架构时，若第一网络设备为CU单元，第四时延包括第一网络设备的HARQ传输时延、第一网络设备的RLC实体的时延、第一网络设备的PDCP实体的时延以及第一接口的时延。第五时延包括第二网络设备的HARQ传输时延和第二网络设备的RLC实体的时延。可选的，第二接口的时延由CU单元统计，并且CU单元结合第五时延、第二接口的时延、第一网络设备的PDCP层的时延确定第二路径的D2。可选的，第二接口的时延还可以是第二网络设备统计的，这种情况下，第五时延包括第二网络设备的HARQ传输时延、第二网络设备的RLC实体的时延和第二接口的时延，CU单元结合第五时延和第一网络设备的PDCP层的时延确定第二路径的D2。
可选的，当第一网络设备采用CU-DU分离架构时，若第一网络设备为DU单元，第四时延包括第一网络设备的HARQ传输时延和第一网络设备的RLC实体的时延，第五时延包括第二网络设备的HARQ传输时延和第二网络设备的RLC实体的时延，DU单元结合第五时延确定第二路径的D2。
第一网络设备确定网络侧的上行时延的方式可以为：在一定周期内，统计第一路径上每个数据包从基站调度该数据包到基站收到该数据包处理之间的时延，然后对这些数据包的时延进行取平均值作为第四时延。或者第一网络设备分别统计第一路径上每个数据包从DU调度该数据包到DU把该数据包发送给CU-UP的平均时延(在一定周期内)，和F1口时延，和CU-UP的平均时延(CU-UP通过F1口收到每个数据包到把该数据包发送给核心 网的平均时延)，然后根据这些时延相加得到第四时延。同理，第二网络设备内部统计上行时延为：在一定周期内，统计第二路径上每个数据包从基站调度该数据包到基站收到该数据包处理(比如发送给核心网或PDCP层提交给上层的时刻)之间的时延，然后对这些数据包的时延进行取平均值作为第五时延。或者第二网络设备分别统计第二路径上每个数据包从基站调度该数据包到基站收到该数据包处理(比如DU发送给CU的时刻)之间的时延的平均时延(在一定周期内)，和X2/Xn口时延，然后根据这些时延相加得到第五时延。
可选的，第一网络设备根据第一时延、第二时延、第四时延和第五时延确定第一DRB的上行时延可以为：第一网络设备根据第一时延和第四时延确定第一上行时延，并根据第二时延和第五时延确定第二上行时延。然后根据第一上行时延和第二上行时延确定第一DRB的上行时延。也即是说，本实施例中是先确定每条路径的总时延(比如每条路径的上行时延为:UE上报的UE侧上行平均时延+基站侧统计的该路径在基站侧的平均时延)，再根据每条路径上的总时延确定该DRB的最终时延(其中，该最终时延为第一DRB的上行时延)。以图8为例，gNB1先根据路径1的D1和路径1的D2确定路径1的总时延，根据路径2的D1和路径2的D2确定路径2的总时延。例如确定公式为路径1的时延＝路径1中D1时延+路径1中D2时延；路径2的时延＝路径中D1时延+路径2中D2时延。最终根据路径1的总时延和路径2的总时延确定该DRB的最终时延，例如该DRB的最终时延为min(路径1的时延，路径2的时延)，或者，该DRB的最终时延为max(路径1的时延，路径2的时延)，或者，该DRB的最终时延为路径1的时延与路径2的时延的平均值。可选的，由于第一时延和第四时延获得的时刻可能不同，第二时延和第五时延获得的时刻可能不同，第一网络设备可以根据根据当前时刻确定的第一时延和当前时刻确定的第四时延确认第一上行时延，根据当前时刻确定的第二时延和当前时刻确定的第五时延获得第二上行时延。可选的，第二网络设备发送的第五时延中不包括PDCP的时延，第一网络设备在确定第二路径的D2时，可以根据第二网络设备发送的第五时延以及第一网络设备的PDCP的时延求和得到第二路径的D2。可以理解的是，本申请实施例对于网络设备确定该DRB的最终时延的方式不作限定。
可选的，UE可以在RRC消息(比如测量上报消息)中携带上述第一信息。
可选的，第一网络设备从终端设备接收第一信息之前，还包括：第一网络设备向终端设备发送第一指示信息，终端设备从第一网络设备接收第一指示信息，该第一指示信息用于指示终端设备统计上述第一信息，终端设备收到该第一指示信息后，开始统计第一信息，或者第一指示信息用于指示终端设备统计上述第一时延和第二时延，终端设备收到该第一指示信息后，开始统计第一信息。可选的，第一DRB在哪个网络设备上或终止于哪个网络设备上，则由哪个网络设备向终端设备发送第一指示信息。例如，针对MNterminated split bearer而言，则由主站向终端设备发送第一指示信息。针对SNterminated split bearer而言，则由辅站向终端设备发送第一指示信息。可选的，该第一指示信息中还可以包括DRB的标识，以指示UE对哪些DRB进行UE侧的时延统计。不同的DRB还可以配置不同的统计周期。可选的，第一指示信息还可以指示对上行进行时延统计，或对下行进行时延统计，或对上行和下行进行时延统计。实施该过程，可以按照DRB粒度进行时延统计的配置。实施该过程，可以减少UE的负荷，降低UE的处理开销。可选的，第一网络设备可以通过测 量配置消息发送第一指示信息。需要说明的是，本实施例中提到的网络侧通知UE进行统计哪些DRB的时延信息，即第一指示信息中包括DRB的标识，以指示UE对哪些DRB进行UE侧的时延统计。可选的，第一指示信息中还可以为不同的DRB配置不同的统计周期或相同的统计周期。可选的，第一指示信息还可以指示对上行进行时延统计，或对下行进行时延统计，或对上行和下行进行时延统计。可选地，可以在测量配置中发送第一指示信息。这些可以作为一个独立的实施方式，可以不依赖于本申请中网络侧的具体统计和UE的上报方法。
可选的，第二网络设备向第一网络设备发送第五时延之前，还包括：第一网络设备向第二网络设备发送第二指示信息，第二网络设备从第一网络设备接收第二指示信息，该第二指示信息指示第二网络设备统计第五时延。例如，针对DC场景，比如对于MN terminated split bearer而言，主站需要通过Xn/X2接口通知辅站对DRB的第二路径上的网络侧时延进行统计。可选的，还可以指示进行上行时延的统计，或进行下行时延时延的统计，或进行上行和下行时延的统计。可选的，该第二指示信息中还可以包括DRB的标识，以指示辅站对哪些DRB进行网络侧的时延统计。
针对DRB offloading(卸载)场景(DRB offloading是指一个DRB在MN terminated bearer和SN terminated bearer之间变化，例如主站将主站上的DRB迁移到辅站上)，UE在接收到网络设备下发的DRB offloading命令时可以自动停止对该DRB的时延统计。或者主站下发的DRB offloading命令中同时携带源基站(迁移之前的基站)删除该DRB的时延测量配置任务的指示信息。UE在接收到该DRB offloading命令时可以根据该指示信息停止对该DRB的时延统计，这是因为测量任务无法继承，测量标识(measID)在主站和辅站两边是独立的。或者当主站没有通知UE删除该DRB的时延测量任务时，UE上报没有统计到该DRB的结果或UE不上报统计结果。当UE从辅站收到对该DRB的时延测量任务时，UE重新开始对该DRB进行时延统计。同样的，当主站将主站上的DRB迁移到辅站上时，主站还可以通知辅站停止对该DRB进行时延统计。当该DRB迁移之后，可以由目标基站(迁移之后的基站)重新触发对该DRB的测量任务。实施该过程，可以减少UE的负荷，降低UE的处理开销。
本申请实施例是以两个网络设备为例进行的说明，在实际应用中，还可以是更多的网络设备为终端设备通过传输第一DRB的数据包的路径。多条路径时的实现过程可以参考前述两条路径时的实现过程，此处不再赘述。
实施图12所示方法实施例，针对一个DRB的数据包在多条路径上传输的场景，例如DC场景，UE可以分别对每条路径进行UE侧的时延统计，网络设备可以分别对每条路径进行网络侧的时延统计，最终确定出该DRB的上行时延，实现了对DRB时延的统计，网络侧统计出DRB的时延可以便于网络侧基于该时延调整资源分配以满足业务对时延的需求。
实施例二
前述图12所示实施例一中，是以DC场景描述的，本申请还可以适用于CA场景，具体的可以参见图13，是本申请实施例二提供的一种通信方法的流程示意图。该方法包括步 骤S301-S303。其中，
S301：终端设备生成第一信息，第一信息包括第一时延和第二时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。
S302：终端设备向第一网络设备发送第一信息，第一网络设备从终端设备接收第一信息。
S303：第一网络设备根据第一时延、第二时延、第四时延和第五时延确定第一DRB的上行时延，第四时延为在第一路径上的网络侧时延，第五时延为在第二路径上的网络侧时延。
本实施例可以应用于CA场景。即第一网络设备具备至少2个RLC实体与UE进行数据传输。以第一网络设备具备2个RLC实体与UE进行数据传输为例，在第一路径上的网络侧时延为第一网络设备的第一RLC实体对应的路径上的时延，在第二路径上的网络侧时延为第一网络设备的第二RLC实体对应的路径上的时延。例如图10中，第一网络设备为gNB1，第一路径为路径5，第二路径为路径6。gNB1统计路径5上的网络侧时延D2以及路径6上的网络侧时延D2，UE分别统计路径5上的终端侧时延D1以及路径6上的终端侧时延D1。然后，UE将路径5的D1和路径6的D1发送给gNB1，由gNB1最终确定DRB1的上行时延。
第一DRB为某一DRB。若采用CAduplication方式，UE将该DRB的数据包复制为两份，并通过第一路径将一份数据包发送给第一网络设备的第一RLC实体，以及通过第二路径将另一份数据包发送给的第一网络设备的第二RLC实体。终端设备统计的是该DRB分别在两条路径上的UE侧的时延。第一网络设备统计的是该DRB在第一路径上的网络侧时延以及该DRB在第二路径上的网络侧的时延。例如图10中，第一网络设备为gNB1，第一路径为路径5，第二路径为路径6。gNB1统计路径5上的网络侧时延D2以及路径6上的网络侧时延D2，UE分别统计路径5上的终端侧时延D1以及路径6上的终端侧时延D1。然后，UE将路径5的D1和路径6的D1发送给gNB1，由gNB1最终确定DRB1的上行时延。
可选的，在CA场景中，UE统计的第一时延包括终端设备的PDCP实体从上层收到第一数据包到终端设备获得向第一RLC实体发送第一数据包的上行授权之间的时延。UE统计的第二时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第二RLC实体发送第二数据包的上行授权之间的时延。
比如UE确定UE侧的上行时延的方式可以为：在一定周期内，统计第一路径上每个数据包对应的从PDCP上层SAP或从SDAP上层SAP收到该数据包到具有通过第一RLC实体传输该数据包的上行授权之间的时延，然后对这些数据包的时延进行取平均值作为第一时延。同理，在一定周期内，统计第二路径上每个数据包对应的从PDCP上层SAP或从SDAP上层SAP收到该数据包到具有通过第二RLC实体传输该数据包的上行授权之间的时延，然后对这些数据包的时延进行取平均值作为第二时延。可选地，第一路径上的统计周期和第二路径上的统计周期可以相同或者不同，该统计周期可以预先规定或者可以由网络设备 配置。需要说明的是，由于两条路径中的数据包的调度时刻可能不同，UE在统计第一时延和第二时延时，在同一个统计周期内，第一数据包和第二数据包可以是不同的若干个数据包，也可以是相同的若干个数据包。
可选的，UE上报第一时延或第二时延的信息时携带路径对应的标识，比如LCHID或cell groupID或者RLC标识(比如主RLC标识或辅RLC标识)来标识第一时延和第二时延。或者，UE上报时通过两个时延的名称不同或出现的位置不同来隐式标识第一时延和第二时延。可选的，UE上报第一时延或第二时延的信息时可以携带DRB标识，用于指示上报哪一个DRB的时延信息。
可选的，在CA场景中，第一网络设备统计的第四时延包括第一网络设备的HARQ传输时延、第一网络设备的第一RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，第一接口为网络设备的CU与网络设备的DU之间的通信接口。第一网络设备统计的第五时延包括第一网络设备的HARQ传输时延、第一网络设备的第二RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个。
第一网络设备确定网络侧的上行时延的方式可以为：在一定周期内，统计第一路径上每个数据包从基站调度该数据包到基站收到该数据包处理之间的时延，然后对这些数据包的时延进行取平均值作为第四时延。或者第一网络设备分别统计第一路径上每个数据包从DU调度该数据包到DU把该数据包发送给CU-UP的平均时延，和F1口时延，和CU-UP的平均时延(CU-UP通过F1口收到每个数据包到把该数据包发送给核心网的平均时延)，然后根据这些时延相加得到第四时延。同理，在一定周期内，统计第二路径上每个数据包从基站调度该数据包到基站收到该数据包处理之间的时延，然后对这些数据包的时延进行取平均值作为第五时延。或者第一网络设备分别统计第二路径上每个数据包从DU调度该数据包到DU把该数据包发送给CU-UP的平均时延，和F1口时延，和CU-UP的平均时延(CU-UP通过F1口收到每个数据包到把该数据包发送给核心网的平均时延)，然后根据这些时延相加得到第五时延。
可选的，第一网络设备根据第一时延、第二时延、第四时延和第五时延确定第一DRB的上行时延可以为：第一网络设备根据第一时延和第四时延确定第一上行时延，并根据第二时延和第五时延确定第二上行时延。然后根据第一上行时延和第二上行时延确定第一DRB的上行时延。也即是说，本实施例中是先确定每条路径的总时延(比如每条路径的上行时延为:UE上报的UE侧上行平均时延+基站侧统计的该路径在基站侧的平均时延)，再根据每条路径上的总时延确定该DRB的最终的时延(其中，该最终时延为第一DRB的上行时延)。以图10为例，gNB1先根据路径5的D1和路径5的D2确定路径5的总时延，根据路径6的D1和路径6的D2确定路径6的总时延。例如确定公式为路径5的时延＝路径5中D1时延+路径5中D2时延；路径6的时延＝路径6中D1时延+路径6中D2时延。最终根据路径5的总时延和路径6的总时延确定该DRB的最终时延，例如该DRB的最终时延为min(路径5的时延，路径6的时延)，或者，该DRB的最终时延为max(路径5的时延，路径6的时延)，或者，该DRB的最终时延为路径5的时延与路径6的时延的平均值。可选的，由于第一时延和第四时延获得的时刻可能不同，第二时延和第五时延获得的时刻可能不同，第一网络设备可以根据根据当前时刻确定的第一时延和当前时刻确定的第四时 延确认第一上行时延，根据当前时刻确定的第二时延和当前时刻确定的第五时延获得第二上行时延。可以理解的是，本申请实施例对于网络设备确定该DRB的最终时延的方式不作限定。
可选的，UE可以在RRC消息(比如测量上报消息)中携带上述第一信息。
可选的，第一网络设备从终端设备接收第一信息之前，还包括：第一网络设备向终端设备发送第一指示信息，终端设备从第一网络设备接收第一指示信息，该第一指示信息用于指示终端设备统计上述第一信息，终端设备收到该第一指示信息后，开始统计第一信息。可选的，该第一指示信息中还可以包括DRB的标识，以指示UE对哪些DRB进行UE侧的时延统计。不同的DRB还可以配置不同的统计周期。可选的，第一指示信息还可以指示对上行进行时延统计，或对下行进行时延统计，或对上行和下行进行时延统计。实施该过程，可以按照DRB粒度进行时延统计的配置。实施该过程，可以减少UE的负荷，降低UE的处理开销。可选的，第一网络设备可以通过测量配置消息发送第一指示信息。
实施图13所示方法实施例，针对一个DRB的数据包在多条路径上传输的场景，例如CA场景，UE可以分别对每条路径进行UE侧的时延统计，网络设备可以分别对每条路径进行网络侧的时延统计，最终确定出该DRB的上行时延，实现了对DRB时延的统计，网络侧统计出DRB的时延可以便于网络侧基于该时延调整资源分配以满足业务对时延的需求。
实施例三
前述图12所示实施例一以及图13所示实施例二中，UE上报两条路径上的UE侧时延，第一网络设备统计两条路径上的总时延，并根据两条路径上的总时延确定出第一DRB的最终时延。除了采用这种方式以外，UE可以上报两条路径合并后的UE侧时延，基站先根据每条路径统计的每段时延统计得到合并的网络侧时延，再根据合并后的UE侧时延以及合并后的网络侧时延确定出第一DRB的最终时延。具体的，可参见图14，是本申请实施例三提供的一种通信方法的流程示意图。该方法包括步骤S401-S404。其中，
S401：终端设备生成第一信息，其中，第一信息包括第三时延的信息，第三时延为终端设备根据终端设备在第一路径上的时延和终端设备在第二路径上的时延得到的，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。
S402：终端设备向第一网络设备发送第一信息，第一网络设备从终端设备接收第一信息；
S403：第二网络设备向第一网络设备发送第五时延，第一网络设备从第二网络设备接收第五时延，第五时延为在第二路径上的网络侧时延。
S404：第一网络设备根据第三时延、第四时延和第五时延确定第一DRB的上行时延，其中，第四时延为在第一路径上的网络侧时延。
其中，步骤S402和步骤S403的执行先后顺序不作限定。本实施例可以应用于DC场景。在第一路径上的网络侧时延为第一网络设备在第一路径上的时延，在第二路径上的网络侧时延为第二网络设备在第二路径上的时延。
其中，终端设备统计第三时延时综合考虑了第一路径上传输的第一数据包的UE侧时延以及第二路径上传输的第二数据包的UE侧时延。第三时延是基于第一路径上传输的第一数据包的UE侧时延和第二路径上传输的第二数据包的UE侧时延进行综合确定得到的。第一数据包和第二数据包的数据均为一个或多个。
UE确定UE侧的上行时延的方式可以为：在一定周期内，统计第一路径和第二路径上每个数据包对应的从PDCP上层SAP或从SDAP上层SAP收到该数据包到具有传输该数据包的上行授权之间的时延，然后对这些数据包的时延进行取平均值作为第三时延。对于DC duplication场景而言，即，每条路径上传输的数据包相同。UE可以把发往两条路径上的相同数据包作为两个数据包独立统计，也就是说统计从PDCP上层SAP或SDAP上层SAP收到数据包到各条路径上具有传输该数据包的上行授权之间的时延，该数据包可以具有两个时延取值。或者把该数据包在两条路径上的最小值(比如每个数据包对应的从PDCP上层SAP或从SDAP上层SAP收到该数据包到从任何一条路径上获得具有传输该数据包的上行授权之间的时延)或最大值(比如每个数据包对应的从PDCP上层SAP或从SDAP上层SAP收到该数据包到从这些路径上获得具有传输该数据包的最晚的上行授权之间的时延)，或平均值做为该数据包在UE侧的最终时延。对于非duplication的DC包而言，即，每条路径上传输的数据包不同。UE统计的是从PDCP上层SAP或SDAP上层SAP收到数据包到具有传输该数据包的上行授权(可能来自两条路径中的任何一个)之间的时延。这种情况，UE统计的是两条路径的时延(即不区分是哪条路径，统一确定，即类似只有一个路径的确定方法)。需要说明的是，由于两条路径中的数据包的调度时刻可能不同，UE在统计第三时延时，在同一个统计周期内，第一路径和第二路径中统计到的数据包可能是不同的若干个数据包，也可能是相同的若干个数据包。
相较于实施例一或实施例二中UE上报2个时延，本申请实施例中UE侧上报的是一个时延。UE根据每条路径的D1得到合并的D1，并上报给网络设备，其中，合并可以是取均值，或取最大值，或取最小值等，本申请实施例对此不做限定。
网络设备确定网络侧的上行时延的方式可以为：网络侧在两条路径上分别统计并确定出一个网络侧的处理时延。比如可以按照两条路径的平均值作为网络侧的时延，比如平均值＝average(路径1上的D2，路径2上的D2)。本申请也不限制按照两条路径的最小值或最大值作为网络侧的处理时延。网络设备根据每条路径的D2得到合并的D2，再根据UE上报的合并的D1得到最终的时延统计结果，即确定出该DRB的最终时延(其中，该最终时延为第一DRB的上行时延)。可以理解的是，本申请实施例对于网络设备确定该DRB的最终时延的方式不作限定。
第一网络设备和第二网络设备分别统计各自路径上的网络侧时延。例如图8中，第一网络设备为gNB1，第二网络设备为gNB2，第一路径为路径1，第二路径为路径2。gNB1统计路径1上的网络侧时延D2，gNB2统计路径2上的网络侧时延，UE综合统计路径1和路径2上的终端侧平均时延D1(或者UE统计DRB1的数据包的UE侧平均时延D1)。然后，UE将统计结果D1发送给gNB1，gNB2将第五时延发送给gNB1，由gNB1最终确定DRB1的上行时延。
可选的，第一网络设备根据第三时延、第四时延和第五时延确定第一DRB的上行时延， 具体为：第一网络设备根据第四时延和第五时延确定第六时延，并根据第三时延和第六时延确定第一DRB的上行时延。可选的，第二网络设备发送的第五时延中不包括PDCP的时延，第一网络设备在确定第二路径的D2时，可以根据第二网络设备发送的第五时延以及第一网络设备的PDCP的时延求和得到第二路径的D2，再结合第一路径的D2和第二路径的D2确定得到第六时延。以图8为例，DRB1的最终上行时延＝UE上报的D1上行时延(例如是路径1上的D1和路径2上的D1的平均值)+gNB1确定的D2上行时延(例如是路径1上的D2和路径2上的D2的平均值)。可选的，由于第四时延和第五时延获得的时刻可能不同，第一网络设备可以根据最新的第四时延和最新的第五时延确认第六上行时延。
其中，第一网络设备的HARQ传输时延、第一网络设备的RLC实体的时延、第一网络设备的PDCP实体的时延、第一接口的时延、第二网络设备的HARQ传输时延、第二网络设备的RLC实体的时延、第二接口的时延的相关描述可以参考前述图12所示实施例一中的相关描述，此处不再赘述。第四时延和第五时延的相关描述可以参考前述图12所示实施例一中的相关描述，此处不再赘述。
可选的，UE可以在RRC消息(比如测量上报消息)中携带上述第一信息。可选的，UE上报第一时延或第二时延的信息时可以携带DRB标识，用于指示上报哪一个DRB的时延信息。
可选的，第一网络设备从终端设备接收第一信息之前，还包括：第一网络设备向终端设备发送第一指示信息，终端设备从第一网络设备接收第一指示信息。第一指示信息用于指示终端设备统计第一信息。可选的，第一DRB在哪个网络设备上，则由哪个网络设备向终端设备发送第一指示信息。例如，针对MNterminated split bearer而言，则由主站向终端设备发送第一指示信息。针对SNterminated split bearer而言，则由辅站向终端设备发送第一指示信息。可选的，该第一指示信息中还可以包括DRB的标识，以指示UE对哪些DRB进行UE侧的时延统计。不同的DRB还可以配置不同的统计周期。可选的，第一指示信息还可以指示对上行进行时延统计，或对下行进行时延统计，或对上行和下行进行时延统计。实施该过程，可以按照DRB粒度进行时延统计的配置。实施该过程，可以减少UE的负荷，降低UE的处理开销。需要说明的是，第一网络设备向终端设备发送第一指示信息，终端设备从第一网络设备接收第一指示信息。终端设备根据该第一指示信息统计第一信息这几个步骤可以单独作为一个实施例，而无需依赖上述UE的上报方法和网络侧的确定方法。
可选的，第二网络设备向第一网络设备发送第五时延之前，还包括：第一网络设备向第二网络设备发送第二指示信息，第二网络设备从第一网络设备接收第二指示信息，该第二指示信息指示第二网络设备统计第五时延。例如，针对DC场景，比如对于MN terminated split bearer而言，主站需要通过Xn/X2接口通知辅站对DRB的第二路径上的网络侧时延进行统计。可选的，还可以指示进行上行时延的统计，或进行下行时延时延的统计，或进行上行和下行时延的统计。可选的，该第二指示信息中还可以包括DRB的标识，以指示辅站对哪些DRB进行网络侧的时延统计。
针对DRB offloading场景，UE在接收到网络设备下发的DRB offloading命令时可以自动停止对该DRB的时延统计。或者网络设备下发的DRB offloading命令中同时携带源基站(迁移之前的基站)删除该DRB的时延测量配置任务的指示信息。UE在接收到该DRB  offloading命令时可以根据该指示信息停止对该DRB的时延统计，这是因为测量任务无法继承，测量标识(measID)在主站和辅站两边是独立的。或者当主站没有通知UE删除该DRB的时延测量任务时，UE上报没有统计到该DRB的结果或UE不上报统计结果。当UE从辅站收到对该DRB的时延测量任务时，UE重新开始对该DRB进行时延统计。同样的，当主站将主站上的DRB迁移到辅站上时，主站还可以通知辅站停止对该DRB进行时延统计。当该DRB迁移之后，可以由目标基站(迁移之后的基站)重新触发对该DRB的测量任务。实施该过程，可以减少UE的负荷，降低UE的处理开销。
本申请实施例是以两个网络设备为例进行的说明，在实际应用中，还可以是更多的网络设备为终端设备通过传输第一DRB的数据包的路径。多条路径时的实现过程可以参考前述两条路径时的实现过程，此处不再赘述。
实施图14所示方法实施例三，针对一个DRB的数据包在多条路径上传输的场景，例如DC场景，UE可以对多条路径进行UE侧的时延统计，网络设备可以对多条路径进行网络侧的时延统计，最终确定出该DRB的上行时延，实现了对DRB时延的统计，网络侧统计出DRB的时延可以便于网络侧基于该时延调整资源分配以满足业务对时延的需求。
实施例四
前述图14所示实施例三中，是以DC场景描述的，本申请还可以适用于CA场景，具体的可以参见图15，是本申请实施例四提供的一种通信方法的流程示意图。该方法包括步骤S501-S503。其中，
S501：终端设备生成第一信息，其中，第一信息包括第三时延的信息，第三时延为终端设备根据终端设备在第一路径上的时延和终端设备在第二路径上的时延得到的，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。
S502：终端设备向第一网络设备发送第一信息，第一网络设备从终端设备接收第一信息。
S503：第一网络设备根据第三时延、第四时延和第五时延确定第一DRB的上行时延，其中，第四时延为在第一路径上的网络侧时延，第五时延为在第二路径上的网络侧时延。
本实施例可以应用于CA场景。即第一网络设备具备至少2个RLC实体与UE进行数据传输。以第一网络设备具备2个RLC实体与UE进行数据传输为例，在第一路径上的网络侧时延为第一网络设备的第一RLC实体对应的路径上的时延，在第二路径上的网络侧时延为第一网络设备的第二RLC实体对应的路径上的时延。
其中，终端设备统计第三时延时综合考虑了第一路径上传输的第一数据包的UE侧时延以及第二路径上传输的第二数据包的UE侧时延。第三时延是基于第一路径上传输的第一数据包的UE侧时延和第二路径上传输的第二数据包的UE侧时延进行综合确定得到的。第一数据包和第二数据包的数据均为一个或多个。
UE确定UE侧的上行时延的方式可以为：在一定周期内，统计第一路径和第二路径上每个数据包对应的从PDCP上层SAP或从SDAP上层SAP收到该数据包到具有传输该数据包的上行授权之间的时延，然后对这些数据包的时延进行取平均值作为第三时延。对于 CAduplication场景而言，即，每条路径上传输的数据包相同。UE可以把发往两条路径上的相同数据包作为两个数据包独立统计，也就是说统计从PDCP上层SAP或SDAP上层SAP收到数据包到各条路径上具有传输该数据包的上行授权之间的时延，该数据包可以具有两个时延取值。或者把该数据包在两条路径上的最小值(比如每个数据包对应的从PDCP上层SAP或从SDAP上层SAP收到该数据包到从任何一条路径上获得具有传输该数据包的上行授权之间的时延)或最大值(比如每个数据包对应的从PDCP上层SAP或从SDAP上层SAP收到该数据包到从这些路径上获得具有传输该数据包的最晚的上行授权之间的时延)，或平均值做为该数据包在UE侧的最终时延。
相较于实施例一或实施例二中UE上报2个时延，本申请实施例中UE侧上报的是一个时延。UE根据每条路径的D1得到合并的D1，并上报给网络设备，其中，合并可以是取均值，或取最大值，或取最小值等。
第一网络设备在两条路径上分别统计并确定出一个网络侧的处理时延(例如取均值，或取最大值，或取最小值等)。比如可以按照两条路径的平均值作为网络侧的时延，比如平均值＝average(路径5上的D2，路径6上的D2)。本申请也不限制按照两条路径的最小值或最大值作为网络侧的处理时延。网络设备根据每条路径的D2得到合并的D2，再根据UE上报的合并的D1得到最终的时延统计结果，即确定出该DRB的最终时延(其中，该最终时延为第一DRB的上行时延)。可以理解的是，本申请实施例对于网络设备确定该DRB的最终时延的方式不作限定。
可选的，第一网络设备根据第三时延、第四时延和第五时延确定第一DRB的上行时延，具体为：第一网络设备根据第四时延和第五时延确定第六时延，并根据第三时延和第六时延确定第一DRB的上行时延。例如图10中，第一网络设备为gNB1，第一路径为路径5，第二路径为路径6。gNB1综合统计路径5和路径6上的网络侧平均时延D2(或者gNB1统计DRB1的数据包的网络侧平均时延D2)，UE综合统计路径5和路径6上的终端侧平均时延D1(或者UE统计DRB1的数据包的UE侧平均时延D1)。然后，UE将统计结果D1发送给gNB1，由gNB1最终确定DRB1的上行时延。
可选的，UE可以在RRC消息(比如测量上报消息)中携带上述第一信息。可选的，UE上报第一时延或第二时延的信息时可以携带DRB标识，用于指示上报哪一个DRB的时延信息。
可选的，第一网络设备从终端设备接收第一信息之前，还包括：第一网络设备向终端设备发送第一指示信息，终端设备从第一网络设备接收第一指示信息。第一指示信息用于指示终端设备统计第一信息。可选的，该第一指示信息中还可以包括DRB的标识，以指示UE对哪些DRB进行UE侧的时延统计。不同的DRB还可以配置不同的统计周期。可选的，第一指示信息还可以指示对上行进行时延统计，或对下行进行时延统计，或对上行和下行进行时延统计。实施该过程，可以按照DRB粒度进行时延统计的配置。实施该过程，可以减少UE的负荷，降低UE的处理开销。
实施图15所示方法实施例四，针对一个DRB的数据包在多条路径上传输的场景，例如CA场景，UE可以对多条路径进行UE侧的时延统计，网络设备可以对多条路径进行网络侧的时延统计，最终确定出该DRB的上行时延，实现了对DRB时延的统计，网络侧统 计出DRB的时延可以便于网络侧基于该时延调整资源分配以满足业务对时延的需求。
实施例五
前述实施例一至实施例四均是以统计多条路径的时延(可以对这多条路径的多个时延分别上报，也可以是上报合并后的一个时延)为例进行的说明，在实际应用中，还可以只统计某一条路径的时延(比如只统计通过主站中发送的数据包的时延，或只统计通过辅站中发送的数据包的时延)。参见图16，是本申请实施例五提供的一种通信方法的流程示意图。该方法包括但不限于如下步骤S601-S603。其中，
S601：终端设备生成第二信息，第二信息包括第一时延或第二时延。第二信息包括第一时延或第二时延的信息。第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。
S602：终端设备向第一网络设备发送第二信息，第一网络设备从终端设备接收第二信息。
S603：第一网络设备根据第二信息和第六时延确定第一DRB的上行时延，如果第二信息包括第一时延的信息，第六时延为在第一路径上的网络侧的时延；如果第二信息包括第二时延的信息，第六时延为在第二路径上的网络侧的时延。
可选的，可以协议中定义统计哪一条路径上的时延，例如，针对DC场景，第一网络设备为主站，协议中定义的是统计主站与终端设备之间的路径上的时延，则UE负责统计该路径上的UE侧时延，主站负责统计该路径上的网络侧时延。或者，协议中定义的是统计辅站与终端设备之间的路径上的时延，则UE负责统计该路径上的UE侧时延，辅站负责统计该路径上的网络侧时延并发送给主站进行最终确定。或者，协议中定义的按照该DRB的类型选择统计哪一条路径上的时延，如果是MN terminated bearer，则UE负责统计主站与终端设备之间的路径上的UE侧时延，主站负责统计该路径上的网络侧时延，如果是SN terminated bearer，则UE负责统计辅站与终端设备之间的路径上的UE侧时延，辅站负责统计该路径上的网络侧时延。又或者，针对CA场景，协议中定义的是统计第一网络设备的主RLC实体与终端设备之间的路径上的时延，则UE负责统计该路径上的UE侧时延，第一网络设备负责统计该路径上的网络侧时延。
可选的，还可以是网络设备指示统计哪一条路径上的时延，例如，网络设备还可以向终端设备发送指示信息，以指示统计哪一条路径上的时延，该指示信息中可以携带路径的ID(例如LCH ID、基站ID、cell group ID或者RLC标识(比如主RLC标识或辅RLC标识)等)。例如，针对DC场景，第一网络设备为主站，主站可以向UE发送指示信息，该指示信息中携带主站的标识，指示统计主站与终端设备之间的路径上的时延，则UE负责统计该路径上的UE侧时延，主站负责统计该路径上的网络侧时延。可选的，该指示信息中还可以携带DRB的标识，以指示对哪些DRB的时延进行统计。
本申请实施例可以应用于DC场景。在第一路径上的网络侧时延为第一网络设备在第一路径上的时延，在第二路径上的网络侧时延为第二网络设备在第二路径上的时延。如果统计的是第一路径上的时延，则第一网络设备根据UE上报的第一路径的D1和第一网络设 备统计的第一路径的D2确定第一路径上的总时延。如果统计的是第二路径上的时延，则第二网络设备根据UE上报的第二路径的D1和第二网络设备发送的第二路径的D2确定第二路径上的总时延。
DC场景下，如果统计的是第一路径上的时延，则UE侧的时延，即第一时延包括终端设备的PDCP实体从上层收到第一数据包到终端设备获得向第一网络设备发送第一数据包的上行授权之间的时延。网络侧的时延，即第六时延包括第一网络设备的HARQ传输时延、第一网络设备的RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，第一接口为第一网络设备的CU与第一网络设备的DU之间的通信接口，例如F1接口。如果统计的是第二路径上的时延，则UE侧的时延，即第二时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第二网络设备发送第二数据包的上行授权之间的时延。网络侧的时延，即第六时延包括第二网络设备的HARQ传输时延、第二网络设备的RLC实体的时延和第二接口的时延中的至少一个，第二接口为第一网络设备和第二网络设备之间的通信接口，例如Xn接口。
本申请实施例还可以应用于CA场景。在第一路径上的网络侧时延为第一网络设备的第一RLC实体对应的路径上的网络侧时延，在第二路径上的网络侧时延为第一网络设备的第二RLC实体对应的路径上的网络侧时延。如果统计的是第一路径上的时延，则第一网络设备根据UE上报的第一路径的D1和第一网络设备统计的第一路径的D2确定第一路径上的总时延。如果统计的是第二路径上的时延，则第一网络设备根据UE上报的第二路径的D1和第一网络设备统计的第二路径的D2确定第二路径上的总时延。
CA场景下，如果统计的是第一路径上的时延，则UE侧的时延，即第一时延包括终端设备的PDCP实体从上层收到第一数据包到终端设备获得向第一网络设备的第一RLC实体发送第一数据包的上行授权之间的时延。网络侧的时延，即第六时延包括第一网络设备的HARQ传输时延、第一网络设备的第一RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，第一接口为第一网络设备的CU与第一网络设备的DU之间的通信接口。如果统计的是第二路径上的时延，则UE侧的时延，即第一时延包括终端设备的PDCP实体从上层收到第二数据包到终端设备获得向第一网络设备的第二RLC实体发送第二数据包的上行授权之间的时延。网络侧的时延，即第六时延包括第一网络设备的HARQ传输时延、第一网络设备的第二RLC实体的时延、第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，第一接口为第一网络设备的CU与第一网络设备的DU之间的通信接口。
可选的，UE上报的第一信息中还可以包括第一时延或第二时延对应的标识，该标识用于区别不同的时延。例如，该标识可以是路径标识，或者LCH标识，或者基站标识，或者小区组标识。
针对DRB offloading场景，UE在接收到网络设备下发的DRB offloading命令时可以自动停止对该DRB的时延统计。或者网络设备下发的DRB offloading命令中同时携带源基站(迁移之前的基站)删除该DRB的时延测量配置任务的指示信息。UE在接收到该DRB offloading命令时可以根据该指示信息停止对该DRB的时延统计。或者当主站没有通知UE删除该DRB的时延测量任务时，UE上报没有统计到该DRB的结果或UE不上报统计结果。 当UE从辅站收到对该DRB的时延测量任务时，UE重新开始对该DRB进行时延统计。同样的，当主站将主站上的DRB迁移到辅站上时，主站还可以通知辅站停止对该DRB进行时延统计。当该DRB迁移之后，可以由目标基站(迁移之后的基站)重新触发对该DRB的测量任务。实施该过程，可以减少UE的负荷，降低UE的处理开销
实施图16所示方法实施例五，针对一个DRB的数据包在多条路径上传输的场景，例如DC场景或者CA场景，UE可以对某一条路径进行UE侧的时延统计，网络设备可以对该条路径进行网络侧的时延统计，最终确定出该DRB的上行时延，实现了对DRB时延的统计，网络侧统计出DRB的时延可以便于网络侧基于该时延调整资源分配以满足业务对时延的需求。
实施例六
上述图12至图16均是以上行时延为例进行说明的。对于下行时延而言，则可以由网络侧单独统计即可。参见图17，是本申请实施例六提供的一种通信方法的流程示意图。该方法包括如下步骤。
S701：第二网络设备向第一网络设备发送第七时延，第一网络设备接收第二网络设备发送的第七时延，第七时延为第三路径上的网络侧下行时延，第三路径用于传输第三数据包，第三数据包属于第一DRB。
S702：第一网络设备根据第七时延和第八时延确定第一DRB的下行时延，该第八时延为第四路径上的网络侧下行时延，第四路径用于传输第四数据包，第四数据包属于第一DRB。
可选的，第七时延包括第二网络设备从第一网络设备的PDCP收到一个RLC SDU到该RLC SDU的最后一部分被UE正确接收(按照接收到的HARQ反馈信息确认被UE正确接收)之间的时延。可选的，第七时延还可能包括X2或Xn口时延中的至少一个。第八时延为第一网络设备的PDCP从上一层收到数据包到MAC层从PHY收到该数据包被UE正确之间的时延。第八时延可包括：PDCP层时延(比如CU-UP的时延)、F1-U时延，HARQ传输或重传时延、RLC侧时延(例如处理时延)。如图9所示，DC场景下，gNB1统计在路径3的下行处理时延(比如一段时间内从PDCP的上一层收到每个数据包到MAC层从PHY收到该数据包被UE正确收到时间段)，gNB2统计路径4的下行处理时延，gNB2也可以统计gNB2与gNB1之间Xn/X2的时延。gNB2可以把gNB2侧的下行时延结果最终值(比如可以统计一段时间内的数据包在辅站的平均处理时延，该处理时延为：从gNB1收到一个RLC SDU到该RLC SDU的最后一部分被UE正确接收的时刻)通知gNB1，由gNB1进行最终确定。
可选的，第一网络设备根据第七时延和第八时延确定第一DRB的下行时延。具体可以为：将第七时延和第八时延的平均值(或加权平均值，或最大值，或最小值)确定为是第一DRB的下行时延。这种情况中，无需让UE上报下行时延。
可选的，UE也可以统计下行时延。比如UE内部处理下行时延为：SDAP或PDCPSDU最后一个分段被终端设备正确接收的时刻到终端设备的SDAP或PDCP层把该SDU提交给上层的时刻之间的时延。同上行一样，UE可以分别统计每条支路上的UE侧下行时延并上报。
图17是以DC场景为例进行的说明，在CA场景中，由一个网络设备分别统计各条路径上的下行时延并最终确定第一DRB的下行时延。例如，CA场景中，第七时延可包括：第一网络设备的CU-UP的时延、F1-U时延和DU侧时延中的一种或多种。第八时延可包括：第一网络设备的CU-UP的时延、F1-U时延和DU侧时延中的一种或多种。参见图11，gNB1统计路径7上的下行网络侧的时延，同理，采用同样方法统计另一条路径上的下行网络侧的时延，并最终确定第一DRB的下行时延。确定第一DRB的下行时延的方式可以参见图17所示实施例六的相关描述，此处不再赘述。
此外，网络侧还可以只统计一条路径上的第一DRB的数据包对应的下行时延。比如只统计从主站发送给UE的第一DRB的数据包对应的下行时延。或者只统计从辅站发送给UE的第一DRB的数据包对应的下行时延。进一步的，这条路径还可以是和上行时延统计的路径相同，即上行时延统计的是那条路径的时延，下行时延也统计对应路径的时延。
需要说明的是，前面的实施例都说的是DRB，可选的是，也可以针对信令无线承载(signal radio bearer，SRB)进行以上所有实施例的相同的处理。
需要说明的是，针对终端设备分别统计多条路径上的UE侧时延的场景，前述实施例是以终端设备将这多条路径的UE侧时延都发送给第一网络设备为例进行的说明，在其他可选的实现方式中，终端设备还可以将第一路径的D1发送给第一网络设备，例如主站，将第二路径的D1发送给第二网络设备，例如辅站，辅站根据终端设备发送的第二路径的D1以及自身统计的第二路径的网络侧时延确定得到第二路径的上行时延后，直接向主站发送第二路径的上行总时延(而非向主站发送第二路径的部分时延)，再由主站根据第一路径的上行总时延和第二路径的上行总时延确定第一DRB的上行时延。
需要说明的是，前述各实施例中提及的第一网络设备向终端设备发送第一指示信息，终端设备从第一网络设备接收第一指示信息。终端设备根据该第一指示信息统计第一DRB涉及的UE侧时延这几个步骤可以单独作为一个实施例，而无需依赖前述各方法实施例涉及的具体的UE的上报和网络侧的确定过程。可选的，第一DRB在哪个网络设备上或终止于那个网络设备上，则由哪个网络设备向终端设备发送第一指示信息。例如，针对MN terminated split bearer而言，则由主站向终端设备发送第一指示信息。针对SN terminated split bearer而言，则由辅站向终端设备发送第一指示信息。可选的，该第一指示信息中还可以包括DRB的标识，以指示UE对哪些DRB进行UE侧的时延统计。不同的DRB还可以配置不同的统计周期。可选的，第一指示信息还可以指示对上行进行时延统计，或对下行进行时延统计，或对上行和下行进行时延统计。实施该过程，可以按照DRB粒度进行时延统计的配置。实施该过程，可以减少UE的负荷，降低UE的处理开销。可选的，第一网络设备可以通过测量配置消息发送第一指示信息。
针对DRB offloading(卸载)场景的实现过程也可以单独作为一个独立实施例来实施，而无需依赖前述各方法实施例涉及的具体的UE的上报和网络侧的确定过程。即，UE在接收到网络设备下发的DRB offloading命令时可以自动停止对该DRB的时延测量。或者主站下发的DRB offloading命令中同时携带源基站(迁移之前的基站)删除该DRB的时延测量配置任务的指示信息。UE在接收到该DRB offloading命令时可以根据该指示信息停止对该DRB的时延统计，这是因为测量任务无法继承，测量标识(measID)在主站和辅站两边是 独立的。或者当主站没有通知UE删除该DRB的时延测量任务时，UE上报没有统计到该DRB的结果或UE不上报统计结果。当UE从辅站收到对该DRB的时延测量任务时，UE重新开始对该DRB进行时延统计。
前述各方法实施例均是以UE上报时延信息为例进行的说明，除此之外，UE还可以上报比例信息，该比例为数据包的时延超过门限的比例，该门限可以由网络侧设置。例如，UE在一个周期内统计了10个数据包的UE侧时延，其中确定每个数据包的时延是否超过门限值，再根据超过门限的数据包的数量(例如8个)与这10个数据包的数量(10个)的比值作为上报的比例信息，网络侧根据该比例确定UE侧的时延(或时延范围)。
上述主要从各个网络设备之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如终端设备、网络设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的网元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
可以理解的是，上述方法中，由终端设备实现的方法，也可以由可配置于终端设备的部件(例如芯片或者电路)实现，由网络设备(第一网络设备或者第二网络设备)实现的方法，也可以由可配置于网络设备的部件(例如芯片或者电路)实现。
本申请实施例可以根据上述方法示例对终端设备、网络设备等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图18示出了上述实施例中所涉及的通信装置的一种可能的逻辑结构示意图，通信装置800包括：收发单元801和处理单元802。该通信装置可以为第一网络设备或者可配置于第一网络设备的部件。示例性的，收发单元801用于支持通信装置800执行前述图12至图17所示方法实施例中对应第一网络设备接收或者发送信息的步骤。处理单元802，用于支持通信装置执行前述图12至图17所示方法实施例中对应第一网络设备相关的处理步骤，例如实现除收发单元功能以外的其他功能等。可选的，该通信装置800还可以包括存储单元，用于存储代码(程序)或者数据。一种可能的方式中，处理单元802可以调用存储单元的代码或者数据，使得通信装置800实现根据第一信息、第四时延和第五时延确定第一DRB的上行时延，其中，该第一信息包括第一时延和第二时延的信息，或者，第一信息包括第三时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第三时延为终端设备根据终端设备在第一路径上的时延和终端设备在第二路径上的时延得到的，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB，第四时延为在第一路径上的网络侧时延，第五时延为在第二路径上的网络侧时延。
在硬件实现上，上述处理单元802可以为处理器或者处理电路等。收发单元801可以为收发器或者收发电路或者接口电路等。存储单元可以为存储器。上述处理单元、收发单元和存储单元可以集成在一起，也可以分离。
图19示出了上述实施例中所涉及的通信装置的一种可能的逻辑结构示意图，通信装置900包括：处理单元901和收发单元902。该通信装置可以为第二网络设备或者可配置于第二网络设备的部件。示例性的，收发单元902用于支持通信装置900执行前述图12至图17所示方法实施例中对应第二网络设备接收或者发送信息的步骤。处理单元901，用于支持第二网络设备执行前述图12至图17所示方法实施例中第二网络设备相关的处理步骤，例如实现除收发单元功能以外的其他功能等。可选的，该通信装置900还可以包括存储单元，用于存储代码(程序)或者数据。一种可能的方式中，处理单元802可以调用存储单元的代码或者数据，使得通信装置900获取第五时延，第五时延为在第二路径上的网络侧时延，该第二路径用于传输第二数据包，第二数据包属于第一DRB，用于传输第一DRB的数据包的路径包括两条或多条。
在硬件实现上，上述处理单元901可以为处理器或者处理电路等。收发单元902可以为收发器或者收发电路或者接口电路等。存储单元可以为存储器。上述处理单元、收发单元和存储单元可以集成在一起，也可以分离。
图20所示，为本申请的实施例提供的上述实施例中所涉及的网络设备的一种可能的硬件结构示意图。该网络设备可以是上述第一网络设备或第二网络设备。如图20所示，网络设备1000可包括：一个或多个处理器1001、存储器1002、网络接口1003、收发器1005和天线1008。这些部件可通过总线1004或者其他方式连接，图20以通过总线连接为例。其中：
网络接口1003可用于网络设备1000与其他通信设备，例如其他网络设备，进行通信。具体的，网络接口1003可以是有线接口。
收发器1005可用于对处理器1001输出的信号进行发射处理，例如信号调制。收发器1005还可用于对天线1008接收的移动通信信号进行接收处理。例如信号解调。在本申请的一些实施例中，收发器1005可看作一个无线调制解调器。在网络设备1000中，收发器1005的数量可以是一个或者多个。天线1008可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。
存储器1002可以和处理器1001通过总线1004或者输入输出端口耦合，存储器1002也可以与处理器1001集成在一起。存储器1002用于存储各种软件程序和/或多组指令或者数据。具体的，存储器1002可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器1002可以存储操作系统(下述简称系统)，例如uCOS、VxWorks、RTLinux等嵌入式操作系统。存储器1002还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个用户设备，一个或多个网络设备进行通信。
处理器1001可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所 述处理器也可以是实现确定功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。
本申请实施例中，处理器1001可用于读取和执行计算机可读指令。具体的，处理器1001可用于调用存储于存储器1002中的程序，例如本申请的一个或多个实施例提供的通信方法在网络设备1000侧的实现程序，并执行该程序包含的指令。
可以理解的，网络设备1000可以是图1示出的无线通信系统100中的网络设备101，可实施为基站收发台，无线收发器，一个基本服务集(BSS)，一个扩展服务集(ESS)，NodeB，eNodeB，gNB等等。
需要说明的是，图20所示的网络设备1000仅仅是本申请实施例的一种实现方式，实际应用中，网络设备1000还可以包括更多或更少的部件，这里不作限制。关于网络设备1000的具体实现可以参考前述方法实施例中的相关描述，此处不再赘述。
在采用对应各个功能划分各个功能模块的情况下，图21示出了上述实施例中所涉及的对应实现终端设备的相应操作的通信装置的一种可能的逻辑结构示意图，通信装置110包括：处理单元1101和收发单元1102。该通信装置可以为终端设备或者可用于终端设备的部件。示例性的，收发单元1102用于支持通信装置110执行前述图12至图17所示方法实施例中对应终端设备接收或者发送信息的步骤。处理单元1101，用于支持终端设备执行前述图12至图17所示方法实施例中终端设备相关的处理步骤，例如实现除收发单元功能以外的其他功能等。可选的，该通信装置还可以包括存储单元，用于存储代码(程序)或者数据。一种可能的方式中，处理单元1101可以调用存储单元的代码或者数据，使得通信装置110获取第一信息，其中，该第一信息包括第一时延和第二时延的信息，或者，第一信息包括第三时延的信息，第一时延为终端设备在第一路径上的时延，第二时延为终端设备在第二路径上的时延，第三时延为终端设备根据终端设备在第一路径上的时延和终端设备在第二路径上的时延得到的，第一路径用于传输第一数据包，第二路径用于传输第二数据包，第一数据包和第二数据包均属于第一DRB。
在硬件实现上，上述处理单元1101可以为处理器或者处理电路等。收发单元1102可以为收发器或者收发电路或者接口电路等。存储单元可以为存储器。上述处理单元、收发单元和存储单元可以集成在一起，也可以分离。
如图22所示，为本申请的实施例提供的上述实施例中所涉及的终端设备的一种可能的硬件结构示意图。如图22所示，终端设备120可包括：输入输出模块(例如音频输入输出模块125、按键输入模块126以及显示器127等)、用户接口128、一个或多个处理器121、收发器122、天线123以及存储器124。这些部件可通过总线或者其它方式连接，图22以通过总线连接为例。其中：
天线123可用于将电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。收发器122可用于对处理器121输出的信号进行发射处理，也可用于对天线123接收的移动通信信号进行接收处理。在本申请实施例中，收发器122可看作一个无线调制解调器。在终端设备120中，收发器122的数量可以是一个或者多个。
除了图22所示的收发器122，终端设备120还可包括其他通信部件，例如GPS模块、蓝牙(Bluetooth)模块、无线高保真(wireless fidelity，Wi-Fi)模块等。不限于上述表述的无线 通信信号，终端设备1200还可以支持其他无线通信信号，例如卫星信号、短波信号等等。不限于无线通信，终端设备120还可以配置有有线网络接口(如LAN接口)来支持有线通信。
输入输出模块可用于实现终端设备120和用户/外部环境之间的交互，可主要包括音频输入输出模块125、按键输入模块126以及显示器127等。具体的，输入输出模块还可包括：摄像头、触摸屏以及传感器等等。其中，输入输出模块均通过用户接口128与处理器121进行通信。
存储器124可以和处理器121通过总线或者输入输出端口耦合，存储器124也可以与处理器121集成在一起。存储器124用于存储各种软件程序和/或多组指令。具体的，存储器124可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器124可以存储操作系统(下述简称系统)，例如ANDROID，IOS，WINDOWS，或者LINUX等嵌入式操作系统。存储器12212还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个用户设备，一个或多个网络设备进行通信。存储器124还可以存储用户接口程序，该用户接口程序可以通过图形化的操作界面将应用程序的内容形象逼真的显示出来，并通过菜单、对话框以及按键等输入控件接收用户对应用程序的控制操作。
在本申请实施例中，存储器124可用于存储本申请的一个或多个实施例提供的通信方法在终端设备120侧的实现程序。关于本申请的一个或多个实施例提供的通信方法的实现，请参考前述实施例。
处理器121可用于读取和执行计算机可读指令。具体的，处理器121可用于调用存储于存储器124中的程序，例如本申请的一个或多个实施例提供的通信方法在终端设备120侧的实现程序，并执行该程序包含的指令以实现前续实施例涉及的方法。处理器121可支持：全球移动通信系统(global system for mobile communication，GSM)(2G)通信、宽带码分多址(wideband code division multiple access，WCDMA)(3G)通信，以及长期演进(long term evolution，LTE)(4G)通信、以及5G通信等等中的一个或多个。可选地，当处理器121发送任何消息或数据时，其具体通过驱动或控制收发器122做发送。可选地，当处理器121接收任何消息或数据时，其具体通过驱动或控制收发器122做接收。因此，处理器121可以被视为是执行发送或接收的控制中心，收发器122是发送和接收操作的具体执行者。
可以理解的，终端设备120可以是图1示出的无线通信系统100中的终端设备102，可实施为eMTC设备、移动设备，移动台(mobile station)，移动单元(mobile unit)，无线单元，远程单元，用户代理，移动客户端等等。
需要说明的，图22所示的终端设备120仅仅是本申请实施例的一种实现方式，实际应用中，终端设备120还可以包括更多或更少的部件，这里不作限制。关于终端设备120的具体实现可以参考前述方法实施例中的相关描述，此处不再赘述。
参见图23，图23示出了本申请提供的一种通信芯片的结构示意图。如图23所示，通信芯片1300可包括：处理器1301，以及耦合于处理器1301的一个或多个接口1302。示例性的：
处理器1301可用于读取和执行计算机可读指令。具体实现中，处理器1301可主要包括控制器、运算器和寄存器。示例性的，控制器主要负责指令译码，并为指令对应的操作 发出控制信号。运算器主要负责执行定点或浮点算数运算操作、移位操作以及逻辑操作等，也可以执行地址运算和转换。寄存器主要负责保存指令执行过程中临时存放的寄存器操作数和中间操作结果等。具体实现中，处理器1301的硬件架构可以是专用集成电路(application specific integrated circuits，ASIC)架构、无互锁管道阶段架构的微处理器(microprocessor without interlocked piped stages architecture，MIPS)架构、进阶精简指令集机器(advanced RISC machines，ARM)架构或者NP架构等等。处理器1301可以是单核的，也可以是多核的。
示例性的，接口1302可用于输入待处理的数据至处理器1301，并且可以向外输出处理器1301的处理结果。具体实现中，接口1302可以是通用输入输出(general purpose input output，GPIO)接口，可以和多个外围设备(如显示器(LCD)、摄像头(camara)、射频(radio frequency，RF)模块等等)连接。接口1302通过总线1303与处理器1301相连。
一种可能的实现方式中，处理器1301可用于从存储器中调用本申请的一个或多个实施例提供的通信方法在通信设备侧的实现程序或者数据，使得该芯片可以实现前述图12至图17所示的通信方法。存储器可以和处理器1301集成在一起，也可以通过接口1302与通信芯片130相耦合，也就是说存储器可以是通信芯片130的一部分，也可以独立于该通信芯片130。接口1302可用于输出处理器1301的执行结果。本申请中，接口1302可具体用于输出处理器1301的译码结果。关于本申请的一个或多个实施例提供的通信方法可参考前述各个实施例，这里不再赘述。
需要说明的，处理器1301、接口1302各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
在本申请的另一实施例中，还提供一种计算机存储介质，计算机存储介质中存储有计算机执行指令，当一个设备(可以是单片机，芯片等)或者处理器可以调用可读存储介质中存储的计算机执行指令，从而使得该设备或者处理器来执行图12至图17所提供的通信方法中终端设备或网络设备的步骤。前述的计算机存储介质可以包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
在本申请的另一实施例中，还提供一种计算机程序产品，该计算机程序产品包括计算机执行指令，该计算机执行指令存储在计算机可读存储介质中；设备的至少一个处理器可以从计算机可读存储介质读取该计算机执行指令，至少一个处理器执行该计算机执行指令使得设备实施图12至图17所提供的通信方法中终端设备或网络设备的步骤。
在本申请的另一实施例中，还提供一种通信系统，该通信系统包括多个设备，该多个设备包括终端设备和第一网络设备。或者，该通信系统包括多个设备，该多个设备包括终端设备、第一网络设备和第二网络设备。示例性的，第一网络设备可以为图18所示的通信装置或图20所提供的网络设备，且用于执行图12至图17所提供的时延统计方法中对应第一网络设备的步骤。和/或，终端设备可以为图21所示的通信装置或图22所提供的终端设备，且用于执行图12至图17所提供的时延统计方法中对应终端设备的步骤。和/或，第二网络设备可以为图19所示的通信装置或图20所提供的网络设备，且用于执行图12至图17所提供的时延统计方法中对应第二网络设备的步骤。
最后应说明的是：以上，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘solid state disk(SSD))等。
综上，以上仅为本申请的较佳实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (23)

  1. 一种通信方法，其特征在于，包括：
    从终端设备接收第一信息，其中，所述第一信息包括第一时延和第二时延的信息，或者，所述第一信息包括第三时延的信息，所述第一时延为所述终端设备在第一路径上的时延，所述第二时延为所述终端设备在第二路径上的时延，所述第三时延为所述终端设备根据所述终端设备在所述第一路径上的时延和所述终端设备在第二路径上的时延得到的，所述第一路径用于传输第一数据包，所述第二路径用于传输第二数据包，所述第一数据包和所述第二数据包均属于第一数据无线承载DRB；
    根据所述第一信息、第四时延和第五时延确定所述第一DRB的上行时延，其中，所述第四时延为在所述第一路径上的网络侧时延，所述第五时延为在所述第二路径上的网络侧时延。
  2. 根据权利要求1所述的方法，其特征在于，所述在所述第一路径上的网络侧时延为第一网络设备在所述第一路径上的时延，所述在所述第二路径上的网络侧时延为第二网络设备在所述第二路径上的时延。
  3. 根据权利要求2所述的方法，其特征在于，所述根据所述第一信息、第四时延和第五时延确定所述第一DRB的上行时延之前，还包括：
    从所述第二通信设备接收所述第五时延。
  4. 根据权利要求1所述的方法，其特征在于，所述在所述第一路径上的网络侧时延为所述第一网络设备的第一无线链路控制RLC实体对应的路径上的网络侧时延，所述在所述第二路径上的网络侧时延为所述第一网络设备的第二RLC实体对应的路径上的网络侧时延。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述第一信息包括所述第一时延和所述第二时延的信息，所述根据所述第一信息、第四时延和第五时延确定所述第一DRB的上行时延，包括：
    根据所述第一时延和所述第四时延确定第一上行时延，并根据所述第二时延和所述第五时延确定第二上行时延；
    根据所述第一上行时延和所述第二上行时延确定所述第一DRB的上行时延；
    或者，所述第一信息包括所述第三时延的信息；所述根据所述第一信息、第四时延和第五时延确定所述第一DRB的上行时延，包括：
    根据所述第四时延和所述第五时延确定第六时延，并根据所述第三时延和所述第六时延所述第一DRB的上行时延。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，若所述第一信息包括所述第一时延和所述第二时延的信息，所述第一信息还包括所述第一时延对应的标识和所述第二时延对应的标识。
  7. 根据权利要求2、3、5或6所述的方法，其特征在于，所述第一时延包括所述终端设备的包数据汇聚协议PDCP实体从上层收到所述第一数据包到所述终端设备获得向所述第一网络设备发送所述第一数据包的上行授权之间的时延；所述第二时延包括所述终端设备的PDCP实体从上层收到所述第二数据包到所述终端设备获得向所述第二网络设备发送所述第二数据包的上行授权之间的时延。
  8. 根据权利要求4、5或6所述的方法，其特征在于，所述第一时延包括所述终端设备的PDCP实体从上层收到所述第一数据包到所述终端设备获得向所述第一RLC实体发送所述第一数据包的上行授权之间的时延；所述第二时延包括所述终端设备的PDCP实体从上层收到所述第二数据包到所述终端设备获得向所述第二RLC实体发送所述第二数据包的上行授权之间的时延。
  9. 根据权利要求2、3、5、6或7所述的方法，其特征在于，所述第四时延包括所述第一网络设备的混合自动重传请求HARQ传输时延、所述第一网络设备的RLC实体的时延、所述第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，所述第一接口为所述第一网络设备的集中单元CU与所述第一网络设备的分布单元DU之间的通信接口；所述第五时延包括所述第二网络设备的HARQ传输时延、所述第二网络设备的RLC实体的时延和第二接口的时延中的至少一个，所述第二接口为所述第一网络设备和所述第二网络设备之间的通信接口。
  10. 根据权利要求4、5、6或8所述的方法，其特征在于，所述第四时延包括所述第一网络设备的HARQ传输时延、所述第一网络设备的所述第一RLC实体的时延、所述第一网络设备的PDCP实体的时延和第一接口的时延中的至少一个，所述第一接口为所述网络设备的CU与所述网络设备的DU之间的通信接口；所述第五时延包括所述第一网络设备的HARQ传输时延、所述第一网络设备的所述第二RLC实体的时延、所述第一网络设备的PDCP实体的时延和所述第一接口的时延中的至少一个。
  11. 根据权利要求1至10任一项所述的方法，其特征在于，所述从终端设备接收第一信息之前，还包括：
    向所述终端设备发送第一指示信息，所述第一指示信息用于指示所述终端设备获取所述第一信息。
  12. 一种通信方法，其特征在于，包括：
    获取第一信息，其中，所述第一信息包括第一时延和第二时延的信息，或者，所述第一信息包括第三时延的信息，所述第一时延为终端设备在第一路径上的时延，所述第二时延为所述终端设备在第二路径上的时延，所述第三时延为所述终端设备根据所述终端设备在所述第一路径上的时延和所述终端设备在所述第二路径上的时延得到的，所述第一路径用于传输第一数据包，所述第二路径用于传输第二数据包，所述第一数据包和所述第二数 据包均属于第一DRB；
    向第一网络设备发送所述第一信息。
  13. 根据权利要求12所述的方法，其特征在于，在所述第一路径上的网络侧时延为所述第一网络设备在所述第一路径上的时延，在所述第二路径上的网络侧时延为第二网络设备在所述第二路径上的时延。
  14. 根据权利要求12所述的方法，其特征在于，在所述第一路径上的网络侧时延为所述第一网络设备的第一无线链路控制RLC实体对应的路径上的网络侧时延，在所述第二路径上的网络侧时延为所述第一网络设备的第二RLC实体对应的路径上的网络侧时延。
  15. 根据权利要求12至14任一项所述的方法，其特征在于，若所述第一信息包括所述第一时延和所述第二时延的信息，所述第一信息还包括所述第一时延对应的标识和所述第二时延对应的标识，所述标识用于区别不同的时延。
  16. 根据权利要求13或15所述的方法，其特征在于，所述第一时延包括所述终端设备的PDCP实体从上层收到所述第一数据包到所述终端设备获得向所述第一网络设备发送所述第一数据包的上行授权之间的时延；所述第二时延包括所述终端设备的PDCP实体从上层收到所述第二数据包到所述终端设备获得向所述第二网络设备发送所述第二数据包的上行授权之间的时延。
  17. 根据权利要求14或15所述的方法，其特征在于，所述第一时延包括所述终端设备的PDCP实体从上层收到所述第一数据包到所述终端设备获得向所述第一RLC实体发送所述第一数据包的上行授权之间的时延；所述第二时延包括所述终端设备的PDCP实体从上层收到所述第二数据包到所述终端设备获得向所述第二RLC实体发送所述第二数据包的上行授权之间的时延。
  18. 根据权利要求12至17任一项所述的方法，其特征在于，所述获取第一信息之前，还包括：
    从所述第一网络设备接收第一指示信息，所述第一指示信息用于指示所述终端设备统计所述第一信息。
  19. 一种通信装置，其特征在于，所述通信装置包括用于执行权利要求1至11任一项所述的通信方法的模块或单元。
  20. 一种通信装置，其特征在于，所述通信装置包括用于执行权利要求12至18任一项所述的通信方法的模块或单元。
  21. 一种通信系统，其特征在于，包括终端设备和第一网络设备，其中，所述第一网络设备为权利要求19所述的通信装置，所述终端设备为权利要求20所述的通信装置。
  22. 根据权利要求21所述的通信系统，其特征在于，所述通信系统还包括第二网络设备。
  23. 一种计算机存储介质，其特征在于，所述计算机存储介质上存储有指令，当所述指令在处理器上运行时，使得所述处理器执行权利要求1至11或者权利要求12至18任一项所述的的通信方法。
PCT/CN2020/087223 2019-04-30 2020-04-27 通信方法、装置及系统 Ceased WO2020221201A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20799000.3A EP3952402B1 (en) 2019-04-30 2020-04-27 Communication method and apparatus with determination of uplink delay
US17/514,332 US12126539B2 (en) 2019-04-30 2021-10-29 Communication method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910366086.2 2019-04-30
CN201910366086.2A CN111866929B (zh) 2019-04-30 2019-04-30 通信方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/514,332 Continuation US12126539B2 (en) 2019-04-30 2021-10-29 Communication method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2020221201A1 true WO2020221201A1 (zh) 2020-11-05

Family

ID=72965880

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/087223 Ceased WO2020221201A1 (zh) 2019-04-30 2020-04-27 通信方法、装置及系统

Country Status (4)

Country Link
US (1) US12126539B2 (zh)
EP (1) EP3952402B1 (zh)
CN (2) CN114630360A (zh)
WO (1) WO2020221201A1 (zh)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11838777B2 (en) * 2020-02-14 2023-12-05 Intel Corporation Support for quality-of-service (QOS) monitoring in a dual connectivity or split ng-ran with control plane (CP)—user plane (UP) separation
CN113938904B (zh) * 2020-06-29 2024-09-24 华为技术有限公司 数据传输的方法和装置
WO2022077493A1 (zh) * 2020-10-16 2022-04-21 Oppo广东移动通信有限公司 一种传输时延的测量方法及装置、终端设备、网络设备
US12432616B2 (en) * 2020-10-22 2025-09-30 Telefonaktiebolaget Lm Ericsson (Publ) Radio network node, network node, and methods performed in a wireless communication network
EP4233357A4 (en) * 2020-10-26 2024-05-22 Telefonaktiebolaget LM Ericsson (publ) USER DEVICE, RADIO NETWORK NODE AND METHODS FOR HANDLING DELAYS IN DUAL CONNECTED MODE
CN114698033A (zh) * 2020-12-31 2022-07-01 维沃移动通信有限公司 服务质量保障方法、装置及通信设备
CN112804707B (zh) * 2021-01-04 2024-07-23 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备
WO2022151327A1 (en) * 2021-01-15 2022-07-21 Zte Corporation A method for measuring wireless quality of experience
US20240314052A1 (en) * 2021-02-01 2024-09-19 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for determining path transmission delay, communication device, and storage medium
WO2022193225A1 (zh) * 2021-03-18 2022-09-22 华为技术有限公司 一种突发监测的方法和装置
CN114189298B (zh) * 2021-10-22 2024-02-09 新华三大数据技术有限公司 一种无线网络系统及其统计平均时延的方法
KR20230145875A (ko) * 2022-04-11 2023-10-18 삼성전자주식회사 수행하는 서비스에 기반하여 지연 시간을 포함하는 측정 보고를 전송하는 전자 장치 및 전자 장치의 동작 방법
CN114885360B (zh) * 2022-06-09 2024-07-26 中国联合网络通信集团有限公司 时延可靠性确定方法、接入网设备及存储介质
US20260059593A1 (en) * 2022-09-07 2026-02-26 Lg Electronics Inc. Method and apparatus for transmitting/receiving wireless signal in wireless communication system
CN116865914A (zh) * 2023-07-31 2023-10-10 联想(北京)有限公司 无线链路控制层数据重传方法、装置、系统及存储介质
WO2025025076A1 (zh) * 2023-07-31 2025-02-06 上海移远通信技术股份有限公司 用于无线通信的方法、终端设备和网络设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106937305A (zh) * 2015-12-30 2017-07-07 华为技术有限公司 时延管理方法、传输网设备及通信系统
CN108632879A (zh) * 2017-03-15 2018-10-09 中国移动通信有限公司研究院 一种数据的发送方法、基站及终端
CN108924876A (zh) * 2017-03-24 2018-11-30 华为技术有限公司 数据传输方法、接入网设备、终端及通信系统
EP3456006A1 (en) * 2016-05-13 2019-03-20 Telefonaktiebolaget LM Ericsson (PUBL) Improved resource usage in a multipath network

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6496075B2 (ja) * 2015-07-08 2019-04-03 ノキア ソリューションズ アンド ネットワークス オサケユキチュア 第１の基地局又は第２の基地局を選択してユーザ装置（ｕｅ）にパケットデータユニット（ｐｄｕ）を送信する方法及び装置
CN108377567B (zh) * 2016-11-01 2021-02-23 北京三星通信技术研究有限公司 一种在5g架构下建立双连接传输数据的方法、装置和系统
CN108809548B (zh) * 2017-05-05 2021-08-20 华为技术有限公司 副本传输方法及相关设备
US10798754B2 (en) * 2017-07-24 2020-10-06 Asustek Computer Inc. Method and apparatus for serving quality of service (QOS) flow in a wireless communication system
CN109548085A (zh) * 2017-08-11 2019-03-29 华为技术有限公司 传输数据的方法、接入网设备和终端设备
CN109526029B (zh) * 2017-09-20 2022-05-10 中国移动通信有限公司研究院 一种业务优化方法、介质、相关装置和设备
CN109672510B (zh) * 2017-10-13 2021-01-29 华为技术有限公司 通信方法和通信装置
CN109729583B (zh) * 2017-10-27 2021-06-25 维沃移动通信有限公司 一种无线资源配置方法、基站和用户终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106937305A (zh) * 2015-12-30 2017-07-07 华为技术有限公司 时延管理方法、传输网设备及通信系统
EP3456006A1 (en) * 2016-05-13 2019-03-20 Telefonaktiebolaget LM Ericsson (PUBL) Improved resource usage in a multipath network
CN108632879A (zh) * 2017-03-15 2018-10-09 中国移动通信有限公司研究院 一种数据的发送方法、基站及终端
CN108924876A (zh) * 2017-03-24 2018-11-30 华为技术有限公司 数据传输方法、接入网设备、终端及通信系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI; LG ELECTRONICS INC: "Relay delay consideration", 3GPP DRAFT; R3-092552, 16 October 2009 (2009-10-16), Miyazaki Japan, pages 1 - 12, XP050392047 *
See also references of EP3952402A4 *

Also Published As

Publication number Publication date
US20220052956A1 (en) 2022-02-17
EP3952402A1 (en) 2022-02-09
EP3952402B1 (en) 2025-10-22
US12126539B2 (en) 2024-10-22
CN114630360A (zh) 2022-06-14
CN111866929A (zh) 2020-10-30
CN111866929B (zh) 2022-03-08
EP3952402A4 (en) 2022-06-15

Similar Documents

Publication Publication Date Title
CN111866929B (zh) 通信方法、装置及系统
CN110505160B (zh) 一种通信方法及装置
US12273150B2 (en) Delay measurement method, network device, and terminal device
CN105848222B (zh) 用于切换的方法和基站设备
CN112312429B (zh) 一种提升终端设备测量能力的方法、芯片以及终端设备
CN104519583B (zh) 一种通过双连接进行数据传输和处理的方法、装置和系统
US11240700B2 (en) Communication method and access network device
CN106105304A (zh) Lte网络中的双连接性中的协调上行授权分配的缓冲区状态报告的增强
CN110662299B (zh) 通信方法、装置及存储介质
EP4351192A1 (en) Relay communication method, apparatus and system
CN112351460B (zh) 数据传输方法及相关设备
CN109428694B (zh) 一种媒体接入控制层复用的方法及设备
CN112566186B (zh) 通信方法及装置
WO2023078339A1 (zh) 一种数据传输的方法、卫星基站、信关站及存储介质
CN116349259A (zh) 通信方法及装置
WO2019192458A1 (zh) 通信方法和装置
US20240179560A1 (en) Communication method and communication apparatus
WO2020030176A1 (zh) 数据传输的方法和设备
WO2021127943A1 (zh) 无线通信方法和终端设备
WO2021134697A1 (zh) 一种通信方法及装置
US20250175820A1 (en) Multi-path communications for user equipment in centralized unit and distributed unit split architecture
WO2020063401A1 (zh) 一种模式切换方法、数据流分流方法及装置
WO2024011462A1 (zh) 一种通信方法及装置、通信设备、接入网架构
WO2022178778A1 (zh) 一种数据传输方法及通信装置
EP4694341A1 (en) Communication method, apparatus and system, and storage medium

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: 20799000

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020799000

Country of ref document: EP

Effective date: 20211029

WWG Wipo information: grant in national office

Ref document number: 2020799000

Country of ref document: EP