Configurable granularity for measurement and reporting of transmission delays in wireless networks

By introducing configurable timing and data granularity in wireless communication systems, collaborative monitoring and reporting of delay information, the shortcomings of delay measurement and reporting in URLLC applications in the prior art are solved, and the effective delay of 5G networks is achieved Monitor and optimize.

CN119054268APending Publication Date: 2024-11-29ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094449.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-07-27
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

The prior art is difficult to effectively monitor and report data transmission delays in uplink and downlink in wireless communication systems, especially in ultra-reliable low-latency communication (URLLC) applications, which lack direct measurement of end-to-end delay and Packet-level delay statistics support affects network performance optimization.

Method used

By introducing configurable timing and data granularity in wireless network systems, a dedicated protocol data unit (PDU) is designed to collaborate between network nodes and devices to monitor, measure and report data transmission delays, providing flexible delay segmentation solutions. and report configuration, supporting delay measurement and reporting at QoS stream level.

Benefits of technology

It realizes delay information monitoring and reporting for specific applications and data communication sessions, improves network performance diagnosis and optimization capabilities, supports low-end to end delay 5G networks, and meets the strict delay requirements of URLLC.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119054268A_ABST
    Figure CN119054268A_ABST
Patent Text Reader

Abstract

The present disclosure relates generally to wireless communication systems and methods, and in particular to monitoring and reporting uplink and downlink data transmission delays according to configurable timing and data granularity. Various example implementations disclosed herein provide a mechanism for a network side of a wireless network system to, among various network nodes, devices, and entities, and between a control plane and a user plane of a wireless network, monitoring, measurement, calculation and reporting of information related to downlink and uplink data transmission delays are flexibly configured in a cooperative manner. The disclosed implementations provide a configurable network delay segmentation scheme in addition to configurable timing, data granularity or data flow granularity, content and format for monitoring / measuring / computing / reporting related delay information. Thus, various network devices or nodes coordinate under the adaptive configuration of the network to effectively monitor, measure, calculate and report delay information that adapts to the requirements of particular applications and particular data communication sessions. For reporting delay information in the user plane, a dedicated protocol data unit (PDU) is also designed and constructed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication systems and methods, and more particularly to monitoring and reporting uplink and downlink data transmission delays according to configurable timing and data granularity. Background Art

[0002] Data transmission between a wireless terminal and a core network in a wireless communication system may rely on both an air communication interface between the wireless terminal and a radio access network node and one or more communication interfaces between the radio access network node and the core network. The end-to-end time delay (delay) or latency (latency) of such data transmission (these two terms are used interchangeably in this disclosure) constitutes a key performance indicator of wireless communication systems, especially ultra-reliable low-latency communication (URLLC) applications. Effective monitoring and reporting of such end-to-end communication delays will help diagnose and improve wireless network transmission functions. Summary of the invention

[0003] The present disclosure generally relates to wireless communication systems and methods, and more particularly to monitoring and reporting uplink and downlink data transmission delays according to configurable timing and data granularity. Various example implementations disclosed herein provide mechanisms for the network side of a wireless network system to flexibly configure monitoring, measurement, calculation and reporting of information related to downlink and uplink data transmission delays in a collaborative manner between various network nodes, devices and entities and between the control plane and the user plane of the wireless network. In addition to configurable timing, data granularity or data stream granularity, content and format for monitoring / measuring / calculating / reporting related delay information, the disclosed implementation also provides a configurable network delay segmentation scheme. Therefore, various network devices or nodes coordinate under the adaptive configuration of the network to effectively monitor, measure, calculate and report delay information adapted to the needs of specific applications and specific data communication sessions. For reporting delay information in the user plane, a dedicated protocol data unit (PDU) is also designed and constructed.

[0004] In some example implementations, a method for providing a data transmission delay between a wireless terminal device and a core network by a wireless network access network node is disclosed. The method may include: receiving a transmission delay configuration from the core network, the transmission delay configuration specifying at least one of the following: a transmission delay providing a segmentation scheme in a plurality of segmentation schemes; or a monitoring / reporting configuration for the data transmission delay in a plurality of monitoring / reporting configurations. The method may also include: sending at least a portion of the transmission delay configuration to the wireless terminal device; receiving a transmission delay information item from the wireless terminal device during a data transmission session between the core network and the wireless terminal device; and generating a report based on the transmission delay information item and according to the transmission delay configuration and sending the report to the core network.

[0005] In the above implementation, the transmission delay provides a segmentation scheme including one of the following: an end-to-end delay scheme or a Radio Access Network (RAN) partial delay scheme.

[0006] In any of the above implementations, the monitoring / reporting configuration includes at least one of the following: a reporting timing configuration; a reporting granularity configuration; or a data packet transmission timestamp scheme.

[0007] In any of the above implementations, the reporting timing configuration indicates a reporting frequency or a reporting time period.

[0008] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as at least one of the following: average packet delay; per-packet delay; packet delay distribution; or packet delay distribution information.

[0009] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as the packet delay distribution; the packet delay distribution is included in an uplink protocol data unit (PDU) session frame; and the uplink PDU session frame includes: a first field for indicating the number of multiple delay ranges; and multiple field blocks, each field block including the number of data packets whose delay values ​​fall within a delay range among the multiple delay ranges.

[0010] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as the packet delay distribution information; the packet delay distribution information is included in an uplink protocol data unit (PDU) session frame; and the uplink PDU session frame includes: a first field for identifying the packet delay distribution; a second field for indicating the number of parameters associated with the packet delay distribution; and a field block including the values ​​of the number of parameters.

[0011] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as the per-packet delay; the per-packet delay is included in an uplink protocol data unit (PDU) session frame; and the PDU session frame includes: a first field for indicating the number of per-packet delay samples; and multiple second fields, each second field including per-packet delay samples.

[0012] In any of the above implementations, the data packet transmission timestamp scheme indicates one of: including a transmission timestamp in a data packet header; or including a transmission timestamp in a packet data convergence protocol header.

[0013] In any of the above implementations, the data transmission delay is associated with a user plane of the wireless network.

[0014] In any of the above implementations, the data transmission delay includes a downlink user plane data transmission delay.

[0015] In any of the above implementations, the method also includes: relaying at least one downlink data packet from the core network to the wireless terminal device; and the transmission delay information item associated with the at least one downlink data packet is received from the wireless terminal device on the control plane of the wireless access network node, and includes end-to-end downlink transmission delay information or RAN part downlink transmission delay information associated with the at least one downlink data packet calculated by the wireless terminal device.

[0016] In any of the above implementations, the transmission delay information item is received in the control plane of the radio access network node as part of a Radio Resource Control (RRC) measurement report.

[0017] In any of the above implementations, generating the report and sending the report to the core network includes: inserting the report into an NG Application Protocol (NGAP) message, and sending the NGAP message to the core network in the control plane.

[0018] In any of the above implementations, generating the report and sending the report to the core network includes: inserting the report into an E1 Application Protocol (E1AP) message in the control plane, and sending the E1AP message to the user plane of the wireless access network node; extracting the report from the E1AP message, and inserting the report into a PDU session information PDU in the user plane of the wireless access network node; and sending the PDU session information PDU to the core network in the user plane.

[0019] In any of the above implementations, the data transmission delay includes uplink user plane data transmission delay.

[0020] In any of the above implementations, the transmission delay information item received from the wireless terminal device includes timestamp information of at least one uplink data packet sent from the wireless terminal device.

[0021] In any of the above implementations, the timestamp information of the at least one uplink data packet transmitted from the wireless terminal device is included in a header of the at least one uplink data packet.

[0022] In any of the above implementations, the transmission delay provides a segmentation scheme including the end-to-end delay scheme; and generating the report according to the transmission delay configuration and sending the report to the core network includes: relaying the timestamp information to the core network so that the core network can calculate the data transmission delay.

[0023] In any of the above implementations, the transmission delay provides a segmentation scheme including the RAN partial delay scheme; and generating the report according to the transmission delay configuration and sending the report to the core network includes: calculating the RAN partial delay information associated with the at least one uplink data packet in the user plane of the wireless access network node; sending the RAN partial delay information to the control plane of the wireless access network node; and sending the RAN partial delay information to the core network via an NGAP message in the control plane.

[0024] In any of the above implementations, the transmission delay provides a segmentation scheme including the RAN partial delay scheme; and generating the report according to the transmission delay configuration and sending the report to the core network includes: calculating the RAN partial delay information associated with the at least one uplink data packet in the user plane of the wireless access network node; and sending the RAN partial delay information to the core network via an uplink PDU session information PDU to the core network in the user plane.

[0025] In some other implementations, a method for monitoring / reporting a data transmission delay between the wireless terminal device and a core network in a wireless network by a wireless terminal device is disclosed. The method may include: receiving a transmission delay configuration from a control plane of a wireless access network node, the transmission delay configuration specifying at least one of the following: a transmission delay providing a segmentation scheme in a plurality of segmentation schemes; or a monitoring / reporting configuration for the data transmission delay in a plurality of monitoring / reporting configurations. The method may also include: sending a transmission delay information item to the wireless access network node during a data transmission session between the core network and the wireless terminal device according to the transmission delay configuration.

[0026] In the above implementation, the transmission delay provides a segmentation solution including one of the following: an end-to-end delay solution or a radio access network (RAN) partial delay solution.

[0027] In any of the above implementations, the monitoring / reporting configuration includes at least one of the following: a reporting timing configuration; a reporting granularity configuration; or a data packet transmission timestamp scheme.

[0028] In any of the above implementations, the reporting timing configuration indicates a reporting frequency or a reporting time period.

[0029] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as at least one of the following: average packet delay; per-packet delay; packet delay distribution; or packet delay distribution information.

[0030] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as the packet delay distribution; the packet delay distribution is included in an uplink protocol data unit (PDU) session frame; and the uplink PDU session frame includes: a first field for indicating the number of multiple delay ranges; and multiple field blocks, each field block including the number of data packets whose delay values ​​fall within a delay range among the multiple delay ranges.

[0031] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as the packet delay distribution information; the packet delay distribution information is included in an uplink protocol data unit (PDU) session frame; and the uplink PDU session frame includes: a first field for identifying the packet delay distribution; a second field for indicating the number of parameters associated with the packet delay distribution; and a field block including the values ​​of the number of parameters.

[0032] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as the per-packet delay; the per-packet delay is included in an uplink protocol data unit (PDU) session frame; and the uplink PDU session frame includes: a first field for indicating the number of per-packet delay samples; and multiple second fields, each second field including per-packet delay samples.

[0033] In any of the above implementations, the data packet transmission timestamp scheme indicates one of: including a transmission timestamp in a data packet header; or including a transmission timestamp in a packet data convergence protocol header.

[0034] In any of the above implementations, the data transmission delay is associated with a user plane of the wireless network.

[0035] In any of the above implementations, the data transmission delay includes a downlink user plane data transmission delay.

[0036] In any of the above implementations, it also includes: obtaining reception timestamp information of at least one downlink data packet, and generating the transmission delay information item by calculating the end-to-end downlink transmission delay information or the RAN part downlink transmission delay information associated with the at least one downlink data packet based on the reception timestamp information and the transmission delay configuration; and the transmission delay information item is sent to the control plane of the wireless access network node.

[0037] In any of the above implementations, the transmission delay information item is sent as part of a radio resource control (RRC) measurement report.

[0038] In any of the above implementations, the data transmission delay includes uplink user plane data transmission delay.

[0039] In any of the above implementations, the transmission delay information item includes timestamp information of at least one uplink data packet sent from the wireless terminal device.

[0040] In any of the above implementations, the timestamp information of the at least one uplink data packet transmitted from the wireless terminal device is included in a header of the at least one uplink data packet.

[0041] In some other implementations, a method for providing a data transmission delay between a wireless terminal device and a core network by a core network node of a wireless network is disclosed. The method may include: sending a transmission delay configuration to a wireless access network node, the transmission delay configuration specifying at least one of the following: a segmentation scheme for providing a transmission delay in multiple segmentation schemes; or a monitoring / reporting setting for the data transmission delay in multiple monitoring / reporting configurations. The method may also include: receiving a transmission delay information item from the wireless access network node during a data transmission session between the core network node and the wireless terminal device, the transmission delay information item being generated by the wireless access network node or the wireless terminal device according to the transmission delay configuration.

[0042] In the above implementation, the transmission delay provides a segmentation solution including one of the following: an end-to-end delay solution or a radio access network (RAN) partial delay solution.

[0043] In any of the above implementations, the monitoring / reporting configuration includes at least one of the following: a reporting timing configuration; a reporting granularity configuration; or a data packet transmission timestamp scheme.

[0044] In any of the above implementations, the reporting timing configuration indicates a reporting frequency or a reporting time period.

[0045] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as at least one of the following: average packet delay; per-packet delay; packet delay distribution; or packet delay distribution information.

[0046] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as the packet delay distribution; the packet delay distribution is included in an uplink protocol data unit (PDU) session frame; and the uplink PDU session frame includes: a first field for indicating the number of multiple delay ranges; and multiple field blocks, each field block including the number of data packets whose delay values ​​fall within a delay range among the multiple delay ranges.

[0047] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as the packet delay distribution information; the packet delay distribution information is included in an uplink protocol data unit (PDU) session frame; and the uplink PDU session frame includes: a first field for identifying the packet delay distribution; a second field for indicating the number of parameters associated with the packet delay distribution; and a field block including the values ​​of the number of parameters.

[0048] In any of the above implementations, the reporting granularity configuration indicates that the data transmission delay is reported as the per-packet delay; the per-packet delay is included in an uplink protocol data unit (PDU) session frame; and the uplink PDU session frame includes: a first field for indicating the number of per-packet delay samples; and multiple second fields, each second field including per-packet delay samples.

[0049] In any of the above implementations, the data packet transmission timestamp scheme indicates one of: including a transmission timestamp in a data packet header; or including a transmission timestamp in a packet data convergence protocol header.

[0050] In any of the above implementations, the data transmission delay is associated with a user plane of the wireless network.

[0051] In any of the above implementations, the data transmission delay includes a downlink user plane data transmission delay.

[0052] In any of the above implementations, the transmission delay information item is: received from the wireless access network node; and includes end-to-end downlink transmission delay information or RAN part downlink transmission delay information associated with at least one downlink data packet calculated by the wireless terminal device and relayed by the wireless access network node.

[0053] In any of the above implementations, the transmission delay information item is received from a control plane of the radio access network node in a NG Application Protocol (NGAP) message.

[0054] In any of the above implementations, the transmission delay information item is received from the user plane of the radio access network node as a header in a PDU session information PDU.

[0055] In any of the above implementations, the transmission delay information item includes the RAN part downlink transmission delay information, and the method further includes: calculating the end-to-end downlink transmission delay information based on the transmission delay information item and the core-to-access transmission delay information associated with the at least one downlink data packet.

[0056] In any of the above implementations, the transmission delay providing segmentation scheme includes the end-to-end delay scheme; and the transmission delay information item includes timestamp information of at least one uplink data packet sent from the wireless terminal device.

[0057] In any of the above implementations, the transmission delay provides a segmentation scheme including the RAN part delay scheme; and the transmission delay information item includes the RAN part delay information calculated by the radio access network node.

[0058] In any of the above implementations, the transmission delay information item is received from a control plane of the radio access network node in a NGAP message.

[0059] In any of the above implementations, the transmission delay information item is received from the user plane of the radio access network node in a PDU session information PDU.

[0060] In some other implementations, a wireless device including a processor and a memory is disclosed. The processor may be configured to read computer code from the memory to implement any of the above methods.

[0061] In some other implementations, a computer program product is disclosed, the computer program product comprising a non-transitory computer-readable program medium having computer code stored thereon. The computer code, when executed by a processor, may cause the processor to implement any of the above methods.

[0062] Other aspects and alternatives of the above embodiments and their implementations are described in more detail in the following figures, description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1 An example wireless communication network including a radio access network, a core network, and a data network is shown.

[0064] Figure 2 An example radio access network is shown including a plurality of mobile stations or UEs (user equipment) and radio access network nodes communicating with each other via an over-the-air wireless communication interface.

[0065] Figure 3 A separation architecture for dividing a radio access network node into a centralized unit (CU) and one or more distributed units (DU) is shown.

[0066] Figure 4 Various network functions of an example core network are shown.

[0067] Figure 5 Various network functions of an example 5G core network are shown.

[0068] Figure 6 An example process for configuring QoS flows using QoS (Quality of Service) delay monitoring and reporting between a core network, an access network, and a wireless terminal is shown.

[0069] Figure 7 An example flow of monitoring, measuring, calculating, and reporting of configurable downlink end-to-end delay is shown.

[0070] Figure 8 An example flow of monitoring, measuring, calculating, and reporting of configurable uplink end-to-end delay is shown.

[0071] Fig. 9 An example flow of monitoring, measuring, calculating and reporting of configurable downlink RAN ​​portion delay is shown.

[0072] Fig.10 An example flow of monitoring, measuring, calculating and reporting of configurable uplink RAN ​​portion delay is shown.

[0073] Specific implementation method

[0074] The examples of the techniques and implementations and / or embodiments described in the present disclosure may be used to facilitate configuration, monitoring, and reporting of data transmission delays in wireless communication network systems. The term "exemplary" is used to represent "an example of...", and unless otherwise specified, does not imply an ideal or preferred example, implementation, or embodiment. Section titles are used in the present disclosure to facilitate understanding of the disclosed implementations, and are not intended to limit the techniques disclosed in the various sections to the corresponding sections. The disclosed implementations may be further implemented in a variety of different forms, and therefore, the scope of the present disclosure or the claimed subject matter is intended to be interpreted as not being limited to any of the embodiments presented below. Various implementations may be implemented as methods, devices, components, systems, or non-transient computer-readable media. Therefore, the embodiments of the present disclosure may, for example, take the form of hardware, software, firmware, or any combination thereof.

[0075] The present disclosure is particularly related to monitoring and reporting of uplink and downlink data transmission delays according to configurable timing and data granularity. Various example implementations disclosed herein provide mechanisms for the network side of a wireless network system to flexibly configure monitoring, measurement, calculation and reporting of information related to downlink and uplink data transmission delays in a collaborative manner between various network nodes, devices and entities and between the control plane and the user plane of the wireless network. In addition to configurable timing, data granularity or data flow granularity, content and format for monitoring / measuring / calculating / reporting related delay information, the disclosed implementation also provides a configurable network delay segmentation scheme. Therefore, various network devices or nodes coordinate under the adaptive configuration of the network to effectively monitor, measure, calculate and report delay information adapted to the needs of specific applications and specific data communication sessions. For reporting delay information in the user plane, a dedicated protocol data unit (PDU) is also designed and constructed.

[0076] Wireless Network Overview

[0077] Example wireless communication network (such as Figure 1 100) shown may include wireless terminal devices or user equipment (UE) 110, 111 and 112, a carrier network 102, various service applications 140, and other data networks 150. For example, the carrier network 102 may include access networks 120 and 121, and a core network 130. The carrier network 110 may be configured to transmit voice, data, and other information (collectively referred to as data services) between the UEs 110, 111, 112, between the UEs and the service applications 140, or between the UEs and other data networks 150. The access networks 120 and 121 may be configured as various wireless access network nodes (wireless access network nodes, WANN, alternatively referred to as base stations) to interact with the UEs on one side of the communication session and the core network 130 on the other side. The core network 130 may include various network nodes configured to control the communication session and perform network access management and service routing. The service application 140 may be hosted by various application servers deployed outside the core network 130 but connected to the core network 130. Similarly, other data networks 150 may also be connected to the core network 130 .

[0078] exist Figure 1In the wireless communication network 100 of FIG. 1 , UEs may communicate with each other via a radio access network. For example, UEs 110 and 112 may be connected to the same access network 120 and communicate via the same access network 120. UEs may communicate with each other via an access network and a core network. For example, UE 110 may be connected to access network 120, and UE 111 may be connected to access network 121, and thus, UE 110 and UE 111 may communicate with each other via access networks 120 and 121 and core network 130. UEs may also communicate with service applications 140 and data network 150 via core network 130. In addition, as shown in 113, UEs may communicate directly with each other via sidelink communications.

[0079] Figure 2 Also shown is an example system diagram of a wireless access network 120 including a WANN 202 serving UEs 110 and 112 via an air interface 204. The wireless transmission resources used for the air interface 204 include a combination of frequency resources, time resources and / or space resources. Each of the UEs 110 and 112 may be a mobile terminal device or a fixed terminal device equipped with a mobile access unit (such as a SIM (Subscriber Identity Module) / USIM (Universal Subscriber Identity Module) module) for accessing the wireless communication network 100. Both UEs 110 and 112 may be implemented as terminal devices including but not limited to the following: mobile phones, smart phones, tablet computers, laptop computers, in-vehicle communication devices, roadside communication devices, sensor devices, smart appliances (such as televisions, refrigerators and ovens) or other devices capable of wireless communication over a network. As Figure 2 As shown in , each of the UEs (such as UE 112) may include a transceiver circuit 206 coupled to one or more antennas 208 to enable wireless communication with WANN 120 or with another UE (such as UE 110). The transceiver circuit 206 may also be coupled to a processor 210, which may also be coupled to a memory 212 or other storage device. The memory 212 may be transient or non-transitory and may store computer instructions or codes therein, which, when read and executed by the processor 210, cause the processor 210 to implement the various methods described herein.

[0080] Similarly, WANN 120 may include a base station or other wireless network access point that can communicate wirelessly with one or more UEs and with the core network 130 via an air interface 204. For example, WANN 120 may be implemented in, but not limited to, the following forms: a 2G base station, a 3G nodeB, an LTE eNB, a 4G LTE base station, a 5G NR base station, a 5G centralized unit base station, or a 5G distributed unit base station. Each type of these WANNs may be configured to perform a corresponding set of wireless network functions. WANN 202 may include a transceiver circuit 214 coupled to one or more antennas 216 (antennas 216 may include various forms of antenna towers 218) to enable wireless communications with UEs 110 and 112. Transceiver circuit 214 may be coupled to one or more processors 220, which may also be coupled to a memory 222 or other storage device. The memory 222 may be transient or non-transitory and may store therein instructions or codes that, when read and executed by the one or more processors 220 , cause the one or more processors 220 to implement various functions of the WANN 120 described herein.

[0081] Such as Figure 2 Data packets in the example wireless access network described in the figure can be transmitted as protocol data units (PDUs). The data therein can be packaged into PDUs wrapped with nested and / or layered protocol headers at various network layers. Once a connection (e.g., a radio link control (RRC) connection) is established between the sender and the receiver, the PDUs can be transmitted between the sending device or sender (the two terms are used interchangeably) and the receiving device or receiver (the two terms are also used interchangeably). Either the sending device or the receiving device can be a wireless terminal device, such as Figure 2 devices 110 and 120; or wireless access network nodes, such as Figure 2 Node 202. Each device can be a sending device and a receiving device for two-way communication.

[0082] like Figure 3As shown, for example, one or more base stations 202 of the WANN 120 may include multiple separate access network nodes in the form of a centralized unit (CU) 302 and at least one distributed unit (DU) 304 and 306. In a 5G network, for example, the base station may be implemented as a gNB. Correspondingly, the gNB 202 may functionally and / or physically include a gNB-CU 302 and one or more gNB-DUs 304 and gNB-DUs 306. For example, the CU may be configured to provide support for high-level communication protocols such as Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC), while the DU may be configured to provide support for low-level protocol stacks such as Radio Link Control (RLC), Medium Access Control (MAC), and physical layers.

[0083] In some other implementations, the CU 302 may be further divided into two separate functional or physical entities, referred to as the CU-CP (control plane unit of the gNB-CU) hosting the RRC entity and the CU-UP (user plane unit of the CU) hosting the SDAP and PDCP entities. Such separation of the user plane and the control plane in the high protocol layer (CU layer) in the base station may increase the flexibility of the deployment of the access network.

[0084] In some implementations, such as Figure 3 As shown, CU 302 can be connected to DU1 304 and DU2 306 via various F1 interfaces. For example, the F1 interface can also include an F1-C interface and an F1-U interface, and the F1-C interface and the F1-U interface can be used to carry control plane information and user plane information, respectively. For example, the F1-C interface can be used between the DU and the CU-CP part of the CU 302, and the F1-U interface can be used between the DU and the CU-UP part of the CU 302. For example, gNB 202 can be connected to the core network 130 via an NG interface. Figure 3 As shown, when the gNB is divided into CU and DU, the NG connection to the core network can be implemented between CU 302 and the core network. Figure 3 As further shown, the UE may be connected to the core network 130 via the WANN 120 through a wireless interface.

[0085] like Figure 3As further shown in 320 and 330 of , each of the DUs can serve UEs via one or more cells. Each cell is associated with a coverage area. These cells may alternatively be referred to as serving cells. The coverage areas between the cells may partially overlap. Each UE can actively communicate with at least one cell when it may be connected to or may be connected to more than one cell. Figure 3 In the example of , UE1, UE2, and UE3 can be served by cell 1 320 of DU1, while UE4 and UE5 are served by cell 2 330 of DU1. In some implementations, the UE can be served by two or more cells simultaneously. Each UE can be mobile, and the signal strength and quality from various cells at the UE can depend on the UE location. In some embodiments, the CU can be a gNB Central Unit (gNB-CU) and the DU can be a gNB Distributed Unit (gNB-DU). Although the various implementations described below are provided in the context of a 5G cellular wireless network, the basic principles described herein are applicable to other types of wireless access networks, including but not limited to other generations of cellular networks, as well as Wi-Fi (wireless fidelity), Bluetooth, ZigBee, and WiMax (World Interoperability for Microwave Access) networks.

[0086] In some example implementations, Figure 3 The cells shown in may alternatively be referred to as service cells. Service cells may be grouped into service cell groups (cell groups, CGs). A service cell group may be a master CG (Master CG, MCG) or a secondary CG (Secondary CG, SCG). In each type of cell group, there may be one master cell and one or more secondary cells. For example, the master cell in an MSG may be referred to as a PCell, and the master cell in an SCG may be referred to as a PScell. A secondary cell in either an MCG or an SCG may be referred to as an SCell. The master cell including the PCell and the PScell ​​may be collectively referred to as a SpCell. All of these cells may be referred to as service cells or cells. Unless otherwise specifically distinguished, the terms "cell" and "service cell" may generally be used interchangeably. The term "service cell" may refer to a cell that is serving, will serve, or may serve a UE. In other words, a "service cell" may not currently serve a UE. Although the various embodiments described below may sometimes refer to one of the above types of service cells, the basic principles apply to all types of service cells in two types of service cell groups.

[0087] Figure 4 An example division of network functions in the core network 130 is shown. Figure 4 Only a single instance of a network node for some functions is shown in the figure, but those skilled in the art will appreciate that each of these network functions may be instantiated as multiple instances or network nodes distributed throughout the core network 130. Further, each network node in the core network 130 may support one or more of the core network functions shown. Figure 4 As shown, the core network 130 may include but is not limited to an access management network node (AMNN) 430, a session management network node (SMNN) 440, a data routing network node (DRNN) 450, a policy control network node (PCNN) 420 and an application data management network node (ADMNN) 410.

[0088] The access management network node 430 communicates with the access network 120, the session management network node 442, and the policy control network node 420 via the communication interface 122, the communication interface 432, and the communication interface 424, respectively, and may be responsible for providing UE registration, authentication, and access to the core network 130, as well as the allocation of the session management network node 440 to support specific UE communication requirements. The session management network node 440 allocated by the access management network node 430 may in turn be responsible for allocating data routing network nodes 450 to support specific UE communication requirements and controlling these allocated data routing network nodes 450 via the communication interface 446. Alternatively or additionally, in some implementations, the data routing network node 450 may be directly allocated by the access management network node 430 via the interface 434 and controlled by the session management network 442 via the communication interface 446. The access policy and session routing policy applicable to the UE may be managed by the policy control network node 420, which transmits the policy to the access management network node 430 and the session management network node 440 via the communication interface 424 and the communication interface 422, respectively. Figure 4 The signaling exchange and data exchange performed between various types of network nodes by various communication interfaces indicated by various connection lines in the figure can be carried by signaling or data messages that follow a predetermined type of format or protocol.

[0089] In order to support a specific end-to-end communication task requested by the UE, a communication session may be established to support a data service pipe for transmitting specific end-to-end communication data services. Figure 4 As shown in 470, the carrier network portion of the data traffic pipe may involve one or more network nodes in the access network 120 and a group of data routing network nodes 452, 454, and 456 in the core network 130, for example, the group of data routing network nodes 452, 454, and 456 are selected and controlled by a group of session management network nodes 442 and 444, and the group of session management nodes 442 and 444 may be selected and controlled by the access management network node 430 responsible for establishing and managing communication sessions. Data traffic is routed between the UE at one end of the data traffic pipe, the carrier network portion of the data traffic pipe (including a group of network nodes in the access network 120 and selected data routing network nodes 452, 454, and 456 in the core network 130), and the other end of the data traffic pipe (including, for example, another UE, an application server 140, or another data network 150) via communication interfaces (such as 124, 458, and 459).

[0090] The application server 140 may also transmit other configuration and control information to the core network 130. The information transmitted to the core network 130 may be referred to as application data. Such application data may be transmitted by Figure 4 The application data may be transmitted from the application server 140 to the application data management network node 410 via the communication interface 414, for example, in a message. Alternatively, the application server 140 may access the application data management network node 410 using an open API (Application Programming Interface) provided by the core network 130. Figure 4 Only a single application server is shown, but those skilled in the art will appreciate that in actual implementation, the core network 130 may support multiple service applications of different types.

[0091] In some specific implementations, Figure 5 The wireless communication network 500 may include a UE 110, an application server 140, a data network 150, and a carrier network including a RAN 520 and a core network 502. Figure 4Corresponding to the more general description of , a specific implementation of the core network 502 may include an application function (AF) 514, a network exposure function (NEF) 512, and a unified data repository (UDR) function 510. These three types of network nodes can be used together as Figure 4 The core network 502 may also include an access and mobility management function (AMF) 530 and a session management function (SMF (session management function), or I-SMF (intermediate SMF), indicating intermediate SMF) 544 and 542. AMF and SMF are used as Figure 4 The AMF 530 and SMFs 544 and 542 can obtain communication policy information from the separate access / mobility management policy control function (AM PCF) 520 and session management policy control function (SM PCF) 522, respectively. AM PCF 520 and SMPCF 522 are used as Figure 4 Policy Control Network Node (PCNN) 420.

[0092] like Figure 5 As further shown, each of the SMF and I-SMF 522 and 544 controls one or more user-plane functions (UPF) 552. The RAN 520 and one or more UPFs 552 may be allocated by the core network and form the carrier network portion of the data traffic pipe (or alternatively, data traffic path) for a particular communication session. The UPF 552 may be used as Figure 4 Data routing network node (DRNN) 450.

[0093] Figure 5 The various network nodes or network functions in the network use signaling or data messages that follow a predetermined type of format or protocol, through Figure 5The various communication interfaces indicated by the various connection lines in the communication network are used to transmit signaling information and data. For example, some example communication interfaces defined in the fifth generation new air interface wireless communication specification can be used in the communication network 500 as shown in FIG. Figure 5 The example communication interfaces are used between various network nodes indicated by the labels along the connection lines, and include the N1 interface between UE 110 and AMF 530 via RAN 520, the N2 interface between RAN 520 and AMF 530, the N3 interface between RAN 520 and UPF 550, the N4 interface between SMF 542 / 544 and UPF 552, the N11 interface between AMF 530 and I-SMF 542, and the N16a interface between I-SMF 542 and SMF 544.

[0094] End-to-end delay in data transmission

[0095] The end-to-end delay / latency of data transmission in the wireless communication system described above represents the amount of time required for the source device to transmit and reach its destination. For uplink communication, the source device may be a wireless terminal or UE, and the destination may be a UPF network node in the core network described above. Similarly, for downlink communication, the source device may be a UPF network node, and the destination may be a wireless terminal device or UE.

[0096] In a communication network, end-to-end communication can be established as a data communication session (alternatively referred to as a data session or communication session). Each data session can include the transmission of data of different types, characteristics, and transmission requirements. Therefore, a data session can be configured to include multiple data streams, wherein each data stream includes data having similar transmission characteristics and / or associated with similar transmission quality requirements. The transmission of each of these data streams can be controlled and configured based on its transmission characteristics / requirements. For example, the communication network can allocate communication resources to the data streams based on the transmission characteristics / requirements of the data streams.

[0097] Such transmission characteristics / requirements of a data stream can be used to determine a set of transmission parameters (collectively referred to as a transmission profile of the data stream). The configuration of the transmission of the data stream (such as communication resource allocation) can then be based on such transmission profile. The data stream can be referred to as a Quality of Service (QoS) stream and can be characterized by a network-configurable set of QoS parameters. The data in each QoS stream in each QoS stream can be transmitted as a data packet. The term data packet can be used to refer to the smallest granularity of a data unit being transmitted in an uplink or downlink. The transmission of data either succeeds or fails at the packet level. The term data referred to in this disclosure is used in the general sense and includes both user data and control information transmitted as data packets. Data packets in a QoS stream or more generally in a data communication session can be associated with an order so that received data packets can be assembled to restore the original data in the correct order.

[0098] The transmission of data packets is typically associated with a transmission delay or latency associated with the air-to-air interface and other wired or wireless interfaces between the various network nodes described above. Some implementations of data transmission, such as 5G ultra-reliable low-latency communications (URLLC) applications, are intended to provide services with strict requirements on data transmission delay and service availability. Therefore, 5G mobile networks supporting URLLC must provide low latency, as well as minimal packet loss or out-of-order packet arrival. For example, some URLLC services may require end-to-end communication delays to be below the range of 0.5ms to 50ms at the application layer. For another specific example, the maximum delay (or wireless delay) in the air interface may be additionally specified. For some 5G URLLC services, such wireless interface delays may be required to be no more than 1ms.

[0099] Therefore, it is important to monitor, measure, and report network latency for both uplink and downlink data transmission. For example, such latency information can be used to perform network diagnostics and design modifications to improve the performance of the wireless network. For another example, such latency information can be used to adjust resource allocation and QoS parameters within and between data flows, between data communication sessions, and between different users to balance and optimize the overall performance of the network.

[0100] In some implementations, the monitoring, measurement, and reporting of network delays may themselves be configurable. For example, such configurations may be included in network control messages that carry QoS parameters. Such data transmission delay monitoring, measurement, and reporting configurations may be provided to various network nodes before or during the establishment of a data communication session or the establishment of a data flow. The various network nodes may then act accordingly during the communication session to collaboratively support the monitoring and reporting of network data transmission delays.

[0101] Such monitoring / reporting configurations may be designed by the network to provide flexibility in specifying the levels, segmentation, data granularity or data flow granularity, timing, format and other aspects of the various network nodes involved in a communication session to monitor, calculate and / or report information related to network communication delays in either the uplink (UL) or downlink (DL) directions.

[0102] In particular, to ensure low end-to-end latency for URLLC, 5G networks need to support performance measurement definitions related to UL / DL packet latency of 5G networks. Unlike traditional delay monitoring and measurement, end-to-end UL / DL packet latency (UE to UPF latency) needs to be measured for QoS flows per 5G Quality-of-flow Indicator (5QI) between UPF and UE. Such end-to-end UL / DL packet latency between UE and UPF can be measured separately or by measuring two segment delays and adding them together, namely the UL / DL packet latency between UPF and RAN (UPF to RAN latency) and the UL / DL packet latency between UE and RAN (UE to RAN latency, or radio interface latency).

[0103] Compared with the prior art, the following various example implementations provide improved network delay monitoring, measurement and reporting capabilities. In particular, the current technology lacks support for the following requirements.

[0104] ● No support for direct UE to UPF delay measurement. For UE to UPF delay, current technology only supports measuring UPF to RAN delay and UE to RAN delay separately, and then adding these two delays. Such methods increase the processing time and burden of network nodes and UEs (especially for applications that are only interested in end-to-end delay).

[0105] ●Current technologies do not support latency measurement per QoS flow and only provide average latency / delay at the Data Radio Bearer (DRB) level, which may not be granular enough for some applications.

[0106] Current technologies do not support packet-level network latency monitoring, measurement, and reporting.

[0107] • Current technology does not provide various packet-level latency statistics, such as packet-level latency distribution above the DRB-level average latency.

[0108] • Current technology does not utilize any CUs that are partitioned into control plane units and user plane units.

[0109] Various example implementations disclosed herein provide mechanisms for the network side of a wireless network system to flexibly configure monitoring, measurement, calculation, and reporting of information related to downlink and uplink data transmission delays in a collaborative manner between various network nodes, devices, and entities and between the control plane and the user plane of the wireless network. In addition to configurable timing, data granularity or data flow granularity, content, and format for monitoring / measurement / calculation / reporting of relevant delay information, the disclosed implementation also provides a configurable network delay segmentation scheme. Therefore, various network devices or nodes coordinate under the adaptive configuration of the network to effectively monitor, measure, calculate, and report delay information adapted to the needs of specific applications and specific data communication sessions. A dedicated protocol data unit (PDU) is also designed and constructed for reporting delay information in the user plane.

[0110] Network latency monitoring, measurement, calculation and reporting configuration

[0111] In some example implementations, an adaptive and flexible configuration for monitoring, measuring, calculating, and reporting information related to network delay may be determined by the network side of the wireless communication network. For example, the configuration may be determined by a core network entity / function or node. The configuration information may be delivered to various network nodes via various control / data messages and various network interfaces.

[0112] For a specific non-limiting example, such configuration information may be included as part of a QoS parameter set. In such a manner, the configuration may be provided at a QoS flow level. In other words, for a specific user communication session, each QoS flow in different QoS flows may be configured separately with respect to monitoring, measuring, calculating and reporting of network delay. Therefore, such configuration may be part of a QoS profile. The QoS profile may be predefined as each QoS profile being associated with a set of network delay configuration parameters in other QoS parameters. The QoS profile may be indexed and signaled using a QoS index. Alternatively, the network delay configuration parameters may be explicitly included in a QoS configuration message.

[0113] In some example implementations, network delay configuration parameters may include, but are not limited to:

[0114]

[0115]

[0116] As shown in the above example, the network can configure two types of delay measurements for QoS flows, including RAN partial delay measurement (delay between NG-RAN (gNB) and UE) and end-to-end (E2E) delay (delay between UPF of CN (core network) and UE) measurement.

[0117] As further shown in the above example, for each QoS flow, a QoS delay configuration may be defined within the QoS parameters, wherein the QoS delay configuration includes at least one of the following parameters:

[0118] A selection indication or flag to indicate whether RAN partial latency (e.g., latency between NG-RAN (gNB) and UE) is configured to be measured, or whether E2E latency (e.g., latency between UPF of CN (core network) and UE) is configured to be measured. This flag provides the system with the flexibility to determine, based on a specific application or QoS, whether it is only interested in E2E latency, or is also interested in finer granularity in segment latency (e.g., radio interface latency) as an alternative to or in addition to E2E latency.

[0119] Reporting frequency or time period, used to indicate the reporting frequency or time period of the UL / DL RAN part or E2E delay measurement (note that in the case where the E2E delay scheme is selected, the UL E2E delay can be calculated at the CN, and the RAN may only need to report the DL E2E delay measurement). The reporting period can be specified as an absolute time length in seconds, for example. Alternatively, an index in a predefined index set can be used to indicate the reporting time period. Each index in the indexes can correspond to a predefined specific reporting time period.

[0120] Alternatively, a reporting frequency may be specified. The reporting frequency may be the inverse of the reporting period.

[0121] · Timestamp type, used to indicate which type of timestamp will be used when needed. For example, the type of timestamp can include: including a timestamp in an IP header (i.e., in the header of each data packet), or including a timestamp in a PDCP header or information field. The IP header timestamp scheme refers to inserting a timestamp into the Internet Protocol (IP) header of an IP data packet associated with a QoS flow, while the PDCP timestamp scheme refers to inserting a timestamp into the PDCP header or information field of a PDCP protocol data unit (PDU) associated with a QoS flow. The timestamp so included indicates the time when the data packet is sent from the PDCP entity or the time when it arrives at the PDCP entity, and can be used by the receiving network device or node of the timestamp to derive or calculate uplink or downlink delays and other timing information.

[0122] · Reporting granularity, which is used to indicate the reporting type of the results / information of the monitored or measured delay information. As an example, the granularity type may indicate whether the report should be made at a per-packet level, per-QoS flow level, and packet statistics level, etc. For example, the granularity type may include one of the following: packet average, per-packet, distribution range / histogram, and distributed, etc. The reporting granularity parameter may indicate which of these predefined granularity schemes should be used for a specific configured QoS flow. Such parameters may be included in the QoS parameter set as an index or enumeration value corresponding to the predefined granularity configuration. For example, if the "average" type is indicated, the NG-RAN (gNB) may report the average delay result of all packet samples for a specific period (e.g., the above-mentioned reporting time period). If the "per-packet" type is indicated, the NG-RAN

[0123] (gNB) may report all latency / delay results for all packet samples during the reporting time period as a list. If the "distributed range" type is indicated, the NG-RAN (gNB) may report the detailed latency distribution for all packet samples during the reporting time period as, for example, a histogram indicating the number of packets for each of a plurality of latency ranges. If the "distributed" type is indicated, the NG-RAN (gNB) may report the detailed latency distribution for all packet samples during the reporting time period as, for example, a histogram indicating the number of packets for each of a plurality of latency ranges.

[0124] If the type is set, the NG-RAN (gNB) may report a parameterized mathematical distribution of all packet samples during the reporting time period. Alternatively, instead of a numerical histogram, the report may indicate the equations from a distribution set used to describe the delay distribution at packet level (by using a set of predefined equations and indices of these equations)

[0125] and the values ​​of the measured / derived parameters associated with the indicated formulas.

[0126] Configuration process for delay monitoring, measurement, calculation and reporting parameters

[0127] Various parameters for monitoring, measuring, calculating and reporting configuration of data transmission delay can be provided for each QoS flow from the core network side. Figure 6 An example procedure is provided in and is described in more detail below.

[0128] Specifically, Figure 6 A flow chart is shown for configuring QoS flows using QoS network delay monitoring, measurement, calculation and reporting parameters between the core network, access network and UE. Figure 6 Specific references to 5G network terminology may be used in the description below, but no such limitation is intended in the description below, and the basic principles disclosed below are broadly applicable to other wireless communication systems.

[0129] like Figure 6 As shown, in step 1, the CN may send a message (e.g., an initial context establishment request message or a PDU session establishment / modification request message) to the access network (e.g., a gNB (as described above, in the case of CP / UP separation of the gNB, gNB-CU-CP)) to request allocation / modification of resources for one or several PDU sessions and for each QoS flow in the PDU session. The QoS monitoring configuration as described above and determined by the network for QoS may optionally be included in the QoS parameter set in the message. For example, such a message may be sent as an NG Application Protocol (NGAP) in the control plane. Therefore, such a message may be received by the control plane of the access network. As described above, the QoS monitoring configuration as determined by the network for QoS may optionally be included in the QoS parameter set in the message. For example, such a message may be sent as an NG Application Protocol (NGAP) in the control plane. Therefore, such a message may be received by the control plane of the access network. Figure 6 As shown, in the case where the CP and UP functions in the access network are functionally and / or physically separated, such messages will be received by the gNB-CU-CP.

[0130] In step 2, the access network (e.g., gNB-CU-CP) sends a message (e.g., Bearer Context Setup / Modification Request message) to the user plane of the access network (e.g., gNB-CU-UP in case of CP-UP detachment) to request allocation / modification of resources for one or several PDU sessions for each QoS flow in the PDU session. The QoS monitoring configuration may optionally be included in the QoS parameters in the message. As an example, such a message may be implemented as an E1 message.

[0131] In step 3, the access network node (e.g., gNB-CU-UP) stores the received QoS delay configuration for the QoS flow, for example in the user plane of the access network node, as a basis for subsequent actions related to delay monitoring, measurement, calculation and reporting.

[0132] In step 4, the UE context at the gNB-DU is established under the provision of the gNB-CU-CP.

[0133] In step 5, the gNB-CU-CP sends an RRC message, such as an RRC Setup Complete message or an RRC Reconfiguration Request message, to the UE for each QoS flow in the PDU session. The QoS delay configuration may optionally be included in the QoS parameters in the message so that the UE is aware of these delay configuration parameters.

[0134] In step 6, the UE stores the received QoS delay configuration for the QoS flow so that the UE can determine its actions in monitoring, measuring, calculating and reporting QoS data packet network delay information based on such QoS delay configuration.

[0135] In step 7, a PDU session may be established / modified between the CN, the access network (e.g., gNB), and the UE when at least one QoS flow among the multiple QoS flows is configured with QoS delay monitoring, measurement, calculation, and reporting configuration.

[0136] Example DL direct E2E latency monitoring, measurement, calculation and reporting scenario

[0137] Under the configured direct E2E delay monitoring scheme, the network can collaboratively monitor, measure, exchange, calculate and report information related to the configured E2E delay results (e.g., average, per packet, distribution range or distribution) for DL ​​packets of QoS flows.

[0138] Figure 7 An example flow chart for monitoring, measuring, exchanging, calculating and reporting delay information related to DL E2E latency from UPF to UE is shown.

[0139] like Figure 7 As shown, in step 1, at least one QoS flow may be configured with a QoS delay configuration (as described above with respect to Figure 6 In the case described above, a PDU session is established between CN, gNB and UE. It is assumed that the QoS delay configuration indicates an E2E solution.

[0140] In step 2, after the UPF determines to use the E2E delay scheme according to the QoS delay configuration for the QoS flow, the UPF of the CN may send at least one downlink user plane data packet with a corresponding UPF timestamp to the user plane of the access network (e.g., gNB-CU-UP). For example, such a timestamp may be included in an Internet Protocol (IP) header of one or more IP data packets corresponding to the QoS flow. The IP data packet may be encapsulated in the downlink user plane data packet. The UPF timestamp may indicate a time instance when at least one encapsulated IP data packet is sent from the UPF or arrives at the UPF.

[0141] In step 3, the gNB-CU-UP may send downlink user plane data packets to the gNB-DU (if CU-DU separation is implemented in the access network).

[0142] In step 4, the gNB-DU may send downlink user plane data packets to the UE.

[0143] In step 5, after the UE determines to use the E2E delay scheme according to the QoS delay configuration for the QoS flow, the PDCP layer of the UE may calculate the E2E DL delay of the received at least one downlink IP data packet between the UPF and the UE by subtracting the UPF timestamp included in the IP header of the at least one IP data packet from the time when the at least one IP data packet arrives at the PDCP entity of the UE. The UE may also record the calculated delay or delay result of the at least one DL data packet.

[0144] In step 6, the UE may measure / monitor / calculate the DL E2E delay for the reporting time period indicated in the QoS delay configuration. The UE may then send an RRC message with a DL E2E delay report information item to the control plane (e.g., gNB-CU-CP) of the access network via the gNB DU. The E2E delay report information item may be generated according to the above-mentioned QoS delay configuration. Thus, such report information items may include, for example, an average delay, a per-packet delay, a delay distribution histogram, or a delay distribution during the reporting time period as configured in the QoS delay configuration.

[0145] In the above example implementation, the delay distribution information of the QoS flow may include but is not limited to at least one of the following.

[0146] · List of latency distribution ranges or latency histogram Specifically, each item in the list may indicate the number of delay samples within a specific delay value range, where each value range may be defined as a low delay value and a high delay value of the value range. Each item in the list may include at least one of the following: a "range ID" for indicating a predefined delay value range; a "range start / end" pair for indicating the range by the lowest / highest value of the range;

[0147] And "Number of samples" is used to indicate the number of packets in the delay value range corresponding to the "range ID" or "range start / end" pair for the measured network delay result. For example, range ID = 1 can represent delay values ​​between [0, 0.2ms), range ID = 2 can represent delay values ​​between [0.2, 0.4ms), range ID = 3 can represent delay values ​​between [0.4, 0.6ms), etc. Similarly, the "range start / end" pair can indicate the lowest / highest value of the range. For example, for the delay range (0.2ms, 0.4ms), the "range start" of the pair can be set to 0.2, and the "range end" of the pair can be set to 0.4.

[0148] · List of raw delay samples for distribution calculationsEach entry in the list indicates the delay result for a data packet and may optionally include the PDCP sequence number associated with the measured data packet. Such information may be used by other network nodes to perform desired derivations or calculations.

[0149] · Information Items Corresponding to Parameterized Mathematical Delay Distributions Such information items may include at least one of the following:

[0150] "Delay distribution ID" is used to indicate a predefined delay distribution or a probability density formula for a delay distribution;

[0151] "Number of formula parameters", indicating the number of parameters of the selected parameterized mathematical distribution; "List of formula parameters", where each item in the list indicates the value of the parameter of the distribution used in the corresponding order. For example, in the case where the normal probability density formula is selected, it is as follows:

[0152] Table 2

[0153]

[0154] The above information items corresponding to the selected normal probability formula can represent the following.

[0155] Delay distribution ID: ID=1 indicates that the normal probability density formula is used.

[0156] Number of formula parameters: equal to = 2 (only two parameters, μ and σ)

[0157] The first item in the formula parameter list: the value of the first parameter μ.

[0158] The second item in the formula’s parameter list: the value of the second parameter σ.

[0159] return Figure 7 In step 7, the access network may report the QoS delay information during the reporting time period to the core network. Such reporting may be implemented in two exemplary optional ways.

[0160] In an optional implementation shown in step 7A, the report may be implemented in the control plane. Specifically, after receiving an RRC message with (multiple) DL delay information items sent from the UE, the gNB-CU-CP may send, for example, an NGAP message with (multiple) DL delay information items to the CN.

[0161] In the optional implementation shown in step 7B, the report may be implemented in the user plane instead. Figure 7As shown in step 7B-1 of the present invention, after receiving the RRC message with (multiple) DL delay information items sent by the UE, the gNB-CU-CP sends a message (e.g., an E1 application protocol (E1AP) message) including (multiple) DL delay information items to the user plane of the access network node (e.g., gNB-CU-UP). Further, in step 7B-2, after receiving the message with (multiple) DL delay information items sent from the gNB-CU-CP, the gNB-CU-UP sends user plane data, such as a NG-U (next generation user plane) data packet including the DL delay information items, to the UPF of the CN. For example, the NG-U data packet may be implemented as a UL PDU SESSION INFORMATION PDU, etc. In other words, the NG-U data packet may be encapsulated in a special PDU for reporting UL PDU session information, and in this case, the UL PDU session message includes (multiple) QoS delay information items.

[0162] Example UL direct E2E latency monitoring, measurement, calculation and reporting scenario

[0163] Under the configured direct E2E delay monitoring scheme, the network may cooperatively monitor, measure, exchange, calculate, and report information related to the configured E2E delay results (eg, average, per packet, distribution range, or distribution) for UL packets of a QoS flow.

[0164] Figure 8 An example flow chart for monitoring, measuring, exchanging, calculating and reporting delay information related to UL E2E latency from UE to UPF is shown.

[0165] like Figure 8 As shown, in step 1, at least one QoS flow may be configured with a QoS delay configuration (as described above with respect to Figure 6 In the case described above, a PDU session is established between CN, gNB and UE. It is assumed that the QoS delay configuration indicates an E2E solution.

[0166] In step 2, the UE may send an uplink user plane packet with a UE timestamp in an Internet Protocol (IP) header of an IP packet associated with the QoS flow to the gNB-DU. The IP packet may be encapsulated in the uplink user plane packet. The UE timestamp may indicate the time when the encapsulated IP packet is sent from, for example, the PDCP layer of the UE.

[0167] In step 3, the gNB-DU may send uplink user plane data packets to the gNB-CU-UP (if CU-DU separation is implemented in the access network).

[0168] In step 4, the gNB-CU-UP may send uplink user plane data packets to the UPF of the CN.

[0169] In step 5, the UPF of the CN may calculate the UL delay / latency of the received uplink IP data packet between the UPF and the UE by subtracting the UE timestamp in the IP header of the IP data packet from the time when the IP data packet arrives at the UPF. The UPF may also record the delay / latency results for each UL data packet. The UPF may measure the UL delay for a specific period (e.g., the reporting time period configured above) and use the collected UL delay results to determine the UL E2E delay distribution (histogram or distribution) as described above.

[0170] Example DL RAN partial delay monitoring, measurement, calculation and reporting scheme

[0171] Under the configured RAN portion delay monitoring scheme, the network can collaboratively monitor, measure, exchange, calculate and report information related to the configured RAN portion delay results (e.g., average, per packet, distribution range or distribution) for DL ​​packets of the QoS flow.

[0172] Fig. 9 An example flow chart for monitoring, measuring, exchanging, calculating and reporting delay information related to DL RAN partial latency is shown.

[0173] like Fig. 9 As shown, in step 1, a PDU session may be established between the CN, the gNB, and the UE when at least one QoS flow is configured with a QoS monitoring configuration. It is assumed that the QoS delay configuration indicates a RAN partial delay scheme.

[0174] In step 2, the CN's UPF may send a downlink user plane data packet to the gNB-CU-UP.

[0175] In step 3, the gNB-CU-UP may send the PDCP PDU associated with the QoS flow to the gNB-DU with a gNB timestamp in the PDCP PDU header or in the IP header of the IP packet encapsulated in the PDCP PDU. The gNB timestamp may indicate the time when the PDCP PDU is sent from the PDCP layer / entity of the gNB or the time when the corresponding PDCP SDU (Service Data Unit) arrives at the PDCP layer of the gNB.

[0176] In step 4, the gNB-DU may send downlink user plane data packets to the UE.

[0177] In step 5, the PDCP layer of the UE may calculate the DL delay / latency of the received downlink PDCP PDU between the gNB and the UE by subtracting the gNB timestamp included in the PDCP PDU header or the IP packet header therein from the time when the PDCP PDU arrives at the PDCP layer / entity of the UE. The UE may also record the delay / latency result of the DL packet as the RAN partial delay / latency.

[0178] In step 6, the UE may measure the RAN part DL latency for a specific period (e.g., the configured reporting time period as described above). Then, the UE may send an RRC message with at least one latency information item related to the RAN part DL latency to the gNB-CU-CP via the gNB-DU according to the UE's stored QoS latency configuration for the corresponding QoS flow (e.g., the average latency, per-packet latency, distribution range and / or distribution information as described above).

[0179] In step 7, the control plane of the access network (e.g., gNB-CU-CP) reports the delay / latency information item to the CN. Such reporting can be implemented in two example optional ways.

[0180] In the optional implementation shown in step 7A, the report can be implemented in the control plane. Specifically, as shown in step 7A, after receiving the RRC message with the delay information item sent by the UE, the gNB-CU-CP sends, for example, an NGAP message with the delay information item from the control plane of the access network to the CN.

[0181] In an optional implementation shown in step 7B, the report may be implemented in the user plane instead. In particular, as shown in step 7B-1, the gNB-CU-CP sends a message (e.g., an E1AP message) with a delay information item to the user plane (e.g., gNB-CU-UP) of the access network after receiving the RRC message with the delay information item sent by the UE. Further, in step 7B-2, the gNB-CU-UP sends a user plane data packet, such as an NG-U data packet with a delay information item, to the UPF of the CN after receiving the message with the delay information item sent by the gNB-CU-CP. For example, the NG-U data packet may be implemented as a UL PDU session information PDU, etc. In other words, the NG-U data packet may be encapsulated in a special PDU for reporting UL PDU session information, and in this case, the UL PDU session information includes (multiple) QoS delay information items.

[0182] Example UL RAN Partial Delay Monitoring, Measurement, Calculation and Reporting Scheme

[0183] Under the configured RAN portion delay monitoring scheme, the network can collaboratively monitor, measure, exchange, calculate and report information related to the configured RAN portion delay results (e.g., average, per packet, distribution range or distribution) for UL data packets of the QoS flow.

[0184] Fig.10 An example flow chart for monitoring, measuring, exchanging, calculating and reporting delay information related to UL RAN portion latency is shown.

[0185] like Fig.10 As shown, in step 1, a PDU session may be established between the CN, the gNB, and the UE when at least one QoS flow is configured with a QoS delay configuration. It is assumed that the QoS delay configuration indicates a RAN partial delay scheme.

[0186] In step 2, the UE may send the PDCP PDU associated with the QoS flow to the gNB-DU with a UE timestamp in the PDCP PDU header or in the IP header of the IP data packet encapsulated in the PDCP PDU. The UE timestamp indicates the time when the PDCP PDU is sent from the PDCP layer / entity of the UE, or the time when the corresponding PDCP SDU arrives at the PDCP layer / entity of the UE.

[0187] In step 3, the gNB DU may send uplink user plane data packets to the gNB-CU-UP.

[0188] In step 4, after receiving the PDCP PDU sent by the UE, the gNB-CU-UP (or the PDCP layer / entity of the gNB) may calculate the UL transmission delay / latency of the received uplink PDCP PDU between the gNB and the UE by subtracting the UE timestamp from the time when the PDCP PDU arrives at the gNB-CU-UP (the PDCP layer / entity of the gNB). The UE timestamp may be extracted from the IP header or the PDCP PDU header of the IP packet encapsulated in the PDCP PDU. The gNB-CU-UP may then record the delay / latency result of the UL packet as the RAN partial delay.

[0189] In step 5, the gNB-CU-UP may also send uplink user plane data packets to the UPF of the CN.

[0190] In step 6, the access network may report the RAN partial QoS delay information to the CN. Such reporting may be implemented in two exemplary optional ways.

[0191] In an optional implementation shown in step 6A, the reporting may be implemented in the control plane. Specifically, in step 6A-1, the gNB-CU-UP may measure the RAN part UL delay for a specific time period (e.g., a configured reporting time period). Then, the gNB-CU-UP may send a message to the control plane (e.g., gNB-CU-CP) of the access network based on the QoS delay configuration of the QoS flow stored by the gNB-CU-UP, such as an E1AP message having at least one of multiple delay information items for the RAN part UL delay of the QoS flow. Further, in step 6A-2, the gNB-CU-CP, after receiving the message with the delay information item sent by the gNB-CU-UP, then sends a control plane message to the CN, such as an NGAP message with the DL delay information item.

[0192] In the optional implementation shown in step 6B, the report can be implemented in the user plane. Specifically, Figure 6 As shown in step 6B of the , the gNB-CU-UP measures the RAN part UL latency for a specific configured time period, and then sends a user plane data packet, for example, a NG-U data packet with at least one latency information item of the multiple latency information items for the RAN part UL latency of the QoS flow to the UPF of the CN according to the stored QoS latency configuration of the QoS flow of the gNB-CU-UP. The NG-U data packet may be implemented as a UL PDU session information PDU, etc. In other words, the NG-U data packet may be encapsulated in a special PDU for reporting UL PDU session information, and in this case, the UL PDU session information includes (multiple) QoS latency information items.

[0193] UL PDU Session PDU used to report the delay information item containing the delay distribution range ID

[0194] As mentioned above about Figure 7 , Fig. 9 and Fig.10 As described in the implementation method of the present invention, a UL PDU session PDU can be constructed to report QoS delay information from the user plane of the access network (e.g., gNB-CU-UP) to the core network. The UL PDU session PDU can be regarded as a dedicated user plane PDU in parallel with other normal data PDUs.

[0195] In some implementations, such a dedicated PDU may be constructed to report delay information items including delay distribution information associated with a delay range ID as described above. An example construction of such a PDU is shown below, which shows a UL PDU Session Information PDU (referred to as PDU Type 1) format with various UL / DL delay distribution information field definitions. Similarly, such a UL PDU Session Information PDU may be used to carry UL / DL delay information associated with the measured distribution of a delay range with a range ID to the UPF of the CN. It should be further understood that other types of PDUs may also be constructed that include similar fields to carry UL / DL delay distribution information to a target network node.

[0196] Table 3

[0197]

[0198]

[0199] In addition to the usual PDU fields, various delay / latency information fields are described in more detail below. A UL Dist Ind (distribution indication) field (1 bit, value = 0 or 1) may be included. For example, if this bit is set to "1", it indicates that DL delay distribution information is included / present in the PDU. Otherwise, such information is not included in the PDU.

[0200] The DL delay Dist (distribution) of the E2E Ind (indication) field (1 bit, value = 0 or 1) may be included. This parameter indicates whether the DL delay distribution result is the RAN part delay (delay between NG-RAN and UE) or the E2E delay (delay between UPF and UE) (e.g., a value of 0 corresponds to the RAN part delay, and a value of 1 corresponds to the E2E delay).

[0201] A UL Delay Dist Ind (Distribution Indication) field (1 bit, value = 0 or 1) may also be included. If this bit is set to "1", the UL RAN part delay distribution information (between NG-RAN and UE) is included / present in the PDU. Otherwise, such information is not included in the PDU.

[0202] A DL delay distribution range number field may be included. When this parameter is included, the parameter indicates how the delay range (block) may be configured for the current DL delay distribution information. In one example, as shown in Table 3 above, when this field is included, the field may occupy one octet, providing an indication of up to 255 DL delay ranges.

[0203] For each DL delay range in a plurality of DL delay ranges, a corresponding set of fields may be included to carry the distribution information of each DL delay range, and the corresponding set of fields may include a "DL range ID" field and a "number of DL samples in the range" field, for example, each field occupies one octet. The "DL range ID" field may indicate a predefined DL delay range. For example, range ID = 1 may represent a DL delay range of [0, 0.2ms), range ID = 2 may represent a DL delay value range of [0.2, 0.4ms), range ID = 3 may represent a DL delay value range of [0.4, 0.6ms), and so on. For another example, the "number of DL samples in the range" may be an integer, indicating the number of measured data packets having DL delay results within the corresponding delay value range indicated by the range ID. As shown in Table 3, the number of times these two fields are repeated in the PDU is the "number of DL delay distribution ranges".

[0204] Further, a "number of UL delay distribution ranges" field may be included. When this parameter is included, the parameter indicates how the delay range (block) may be configured for the current UL delay distribution information. In an example, as shown in Table 3 above, when this field is included, the field may occupy one octet, providing an indication of up to 255 UL delay ranges.

[0205] For each UL delay range in multiple UL delay ranges, a corresponding field set may be included to carry the distribution information of each UL delay range, and the corresponding field set includes a "UL range ID" field and a "number of UL samples in the range" field, for example, each field occupies one octet. The "UL range ID" field may indicate a predefined UL delay range. For example, range ID = 1 may represent a UL delay range of [0, 0.2ms), range ID = 2 may represent a UL delay value range of [0.2, 0.4ms), range ID = 3 may represent a UL delay value range of [0.4, 0.6ms), etc. For another example, the "number of UL samples in the range" may be an integer, indicating the number of measured data packets having UL delay results within the corresponding delay value range indicated by the range ID. As shown in Table 3, the number of times these two fields are repeated in the PDU is the "number of UL delay distribution ranges".

[0206] UL PDU Session PDU used to report a delay information item containing a delay distribution range start / end pair

[0207] In some implementations, such a dedicated PDU may be constructed to report delay information items including delay distribution range start / end pair information. An example construction of such a PDU is shown below, which shows the format of a UL PDU Session Information PDU (referred to as PDU Type 1) with UL / DL delay distribution information field definition. Similarly, such a UL PDU Session Information PDU may be used to carry UL / DL delay distribution information related to a delay range associated with a start / end value pair to the UPF of the CN. It should be further understood that other types of (multiple) PDUs may also be constructed to include similar fields to carry UL / DL delay distribution information related to a delay range with a start / end value pair to a target network node.

[0208] Table 4

[0209]

[0210]

[0211]

[0212] In addition to the usual PDU fields, the various delay / latency information fields in Table 4 are described in more detail below. Most of the field definitions of the UL / DL delay distribution information are similar to the example implementation with respect to Table 3, except for the following fields.

[0213] Specifically, for each DL delay range in a plurality of DL delay ranges, a corresponding set of fields may be included to carry the distribution information of each DL delay range, the corresponding set of fields including (1) a "range start" field, which, if indicated as present, may occupy, for example, 1 octet, for indicating the start delay value of the corresponding DL delay range; (2) a "range end" field, which, if indicated as present, may occupy, for example, 1 octet, for indicating the end delay value of the corresponding DL delay range; and (3) a "number of DL samples in range" field, which, for example, may occupy 1 octet, for indicating the number of packets whose measured DL delay results are within the value range indicated by "range start" and "range end". As shown in Table 4, the number of times these three fields are repeated in the PDU is "number of DL delay distribution ranges".

[0214] Similarly, for each UL delay range in the plurality of UL delay ranges, a corresponding set of fields may be included to carry the distribution information of each UL delay range, the corresponding set of fields including (1) a "range start" field, which, if indicated as present, may, for example, occupy 1 octet, and is used to indicate the start delay value of the corresponding UL delay range; (2) a "range end" field, which, if indicated as present, may, for example, occupy 1 octet, and is used to indicate the end delay value of the corresponding UL delay range; and (3) a "number of UL samples in range" field, which, for example, may occupy 1 octet, and is used to indicate the number of packets whose measured UL delay results are within the value range indicated by "range start" and "range end". As shown in Table 4, the number of times these three fields are repeated in the PDU is "number of UL delay distribution ranges".

[0215] As an example, when the "Range Start" field is indicated as 0.2, and the "Range End" field is indicated as 0.4, the corresponding delay range may be (0.2 ms, 0.4 ms).

[0216] UL PDU Session PDU used to report the Delay Information Item containing the packet delay samples

[0217] In some implementations, such a dedicated PDU may be constructed to report delay information items including delay distribution information associated with delayed packet level samples as described above. An example construction of such a PDU is shown below, which illustrates the format of a UL PDU SESSIONINFORMATION PDU (referred to as PDU Type 1) with UL / DL delay distribution information field definition. Similarly, such a UL PDU SESSIONINFORMATION PDU may be used to carry UL / DL delay distribution information associated with packet level delay samples to the UPF of the CN. It should be further understood that other types of PDUs may also be constructed to include similar fields to carry UL / DL delay distribution information associated with packet level delay samples to the target network node.

[0218] Table 5

[0219]

[0220]

[0221] In addition to the usual PDU fields, the various delay / latency information fields in Table 5 are described in more detail below. In addition to the following fields, some of the field definitions of the UL / DL delay distribution information in Table 5 are similar to the implementation of Tables 3 and 4 above.

[0222] Specifically, a "number of DL delay samples" may be included. For example, if this parameter is included, the parameter may, for example, occupy 1 octet to indicate up to 255 DL packet level delay samples. This field may be followed by a corresponding number of blocks. Each block, if present, may occupy a certain number of octets (e.g., 4 octets) to carry the delay information for each DL packet, and may also occupy a certain number of octets (e.g., 4 octets) to carry the PDCP sequence number associated with the corresponding DL packet. Each of these blocks corresponds to one of the "DL packet delay" fields and one of the "DL PDCP sequence number" fields in Table 5.

[0223] Similarly, a "number of UL delay samples" may be included. For example, if included, the parameter may, for example, occupy 1 octet to indicate up to 255 UL packet level delay samples. This field may be followed by a corresponding number of blocks. Each block, if present, may occupy a certain number of octets (e.g., 4 octets) to carry delay information for each UL packet and also occupy a certain number of octets (e.g., 4 octets) to carry the PDCP sequence number associated with the corresponding UL packet. Each of these blocks corresponds to one of the "UL Packet Delay" fields and one of the "UL PDCP Sequence Number" fields of Table 5.

[0224] The above per-packet delay information may be used by various network nodes in the wireless network to calculate delay distribution information.

[0225] UL PDU Session PDU used to report the Delay Information Item containing the Delay Distribution Information

[0226] In some implementations, such a dedicated PDU may be constructed to report delay information items, including the delay distribution information related to delay distribution described above. An example construction of such a PDU is shown below, which shows the UL PDU SESSION INFORMATION PDU (referred to as PDU Type 1) format with UL / DL delay distribution information field definition. Similarly, such UL PDU SESSION INFORMATION PDU may be used to carry UL / DL delay distribution information to the UPF of the CN. It should be further understood that other types of PDUs may also be constructed to include similar fields to carry UL / DL delay distribution information to the target network node.

[0227] Table 6

[0228]

[0229]

[0230] In addition to the usual PDU fields, the various delay / latency information fields in Table 6 are described in more detail below. In addition to the following fields, some of the field definitions of the UL / DL delay distribution information in Table 6 are similar to the implementation of Table 3, Table 4 and Table 5 above.

[0231] A "DL delay distribution ID" field may be included. If present, this field may occupy, for example, 1 octet, and may be used to indicate up to 255 DL delay distribution IDs corresponding to a predefined DL delay distribution set. For example, formula ID=1 may correspond to a predefined binomial distribution, while formula ID=2 may correspond to a predefined normal distribution, etc.

[0232] A "Number of DL Formula Parameters" field may be included. For example, this parameter, if present, may occupy 1 octet to indicate up to 255 parameters used in the parameterized mathematical distribution.

[0233] A block of multiple "DL formula parameters" fields may be included, each field being used to carry one of the DL formula parameters. For example, each of these fields, if present, may, for example, occupy 4 octets specifying one DL formula parameter.

[0234] Similarly, a "UL delay distribution ID" field may be included. If present, this field may occupy, for example, 1 octet to indicate up to 255 UL delay distribution IDs corresponding to a predefined UL delay distribution set. For example, formula ID = 1 may correspond to a predefined binomial distribution, while formula ID = 2 may correspond to a predefined normal distribution, and so on. A "number of UL formula parameters" field may be included. If present, this parameter may, for example, occupy 1 octet to indicate up to 255 parameters used in the parameterized mathematical distribution. A block of multiple "UL formula parameters" fields may be included, each field being used to carry one UL formula parameter among multiple UL formula parameters. Each of these fields, if present, may, for example, occupy 4 octets to specify one UL formula parameter.

[0235] As described above, the delay distribution can be a function of all possible values ​​of a specified delay variable, and also quantifies the relative frequency (probability) of each specific delay variable value occurring. In other words, the delay distribution provides a parameterized mathematical function that can be used to calculate the probability of any single delay observed from the sample space.

[0236] Example delay distributions may include, but are not limited to, binomial distribution, Poisson distribution, geometric distribution, normal distribution, and lognormal distribution, etc. Delay distributions may be classified based on the type of data. For example, for the RAN portion of the collected data packets, or the E2E delay of the data packets between the UPF and the UE, the normal distribution may be suitable for describing the collected data, as shown below.

[0237] Table 7

[0238]

[0239]

[0240] In the case of selecting the above normal probability density formula, the blocks (sets) of the UL delay distribution information in the above UL PDU session PDU frame can be allocated as follows:

[0241] Delay distribution ID: ID=1 indicates that the normal probability density formula is used.

[0242] Number of formula parameters: equal to = 2 (only two parameters, μ and σ)

[0243] The first item in the formula parameter list: the value of the first parameter μ.

[0244] The second item in the formula’s parameter list: the value of the second parameter σ.

[0245] The above description and accompanying drawings provide specific example embodiments and implementations. However, the described subject matter can be implemented in various different forms, and therefore, the subject matter covered or claimed is intended to be interpreted as not being limited to any example embodiment set forth herein. It is intended to provide a reasonably wide scope for the subject matter claimed or covered. In particular, for example, the subject matter can be implemented as a method, device, component, system, or non-transient computer-readable medium for storing computer code. Therefore, the embodiment can, for example, take the form of hardware, software, firmware, storage medium, or any combination thereof. For example, the above method embodiment can be implemented by a component, device, or system including a memory and a processor by executing a computer code stored in the memory.

[0246] Throughout the specification and claims, terms may have nuanced meanings that are suggested or implied by the context, beyond those explicitly stated. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, the claimed subject matter is intended to include, in whole or in part, a combination of the example embodiments.

[0247] In general, terms can be understood at least in part according to the usage in the context. For example, terms such as "and", "or", or "and / or" used in this article can include various meanings, which can depend at least in part on the context in which these terms are used. Typically, if "or" is used to associate a list such as A, B, or C, it is intended to represent A, B, and C (here for inclusive meanings), and A, B, or C (here for exclusive meanings). In addition, at least in part depending on the context, the term "one or more" as used in this article can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, or characteristics in a plural sense. Similarly, at least in part depending on the context, terms such as "one", "an", or "the" can be understood to convey singular usage or to convey plural usage. In addition, also at least in part depending on the context, the term "based on" can be understood as not necessarily intended to convey a set of factors that are exclusive, but allows the presence of additional factors that are not necessarily explicitly described.

[0248] References to features, advantages, or similar language throughout the specification do not imply that all features and advantages that may be achieved using the present solution should be or are included in any single implementation thereof. Rather, language referencing such features and advantages is understood to mean that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussion of features and advantages and similar language throughout the specification may, but need not, refer to the same embodiment.

[0249] In addition, the features, advantages, and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. Based on the description herein, one of ordinary skill in the relevant art will recognize that the present solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.

Claims

1. A method for providing a data transmission delay between a wireless terminal device and a core network by a wireless access network node of a wireless network, comprising: Receive a transmission delay configuration from the core network, the transmission delay configuration specifying at least one of the following: Transmission delay in multiple segmentation schemes provides segmentation schemes; or a monitoring / reporting configuration for the data transmission delay among a plurality of monitoring / reporting configurations; Sending at least a portion of the transmission delay configuration to the wireless terminal device; During a data transmission session between the core network and the wireless terminal device, receiving a transmission delay information item from the wireless terminal device; as well as A report is generated based on the transmission delay information item and according to the transmission delay configuration and the report is sent to the core network.

2. The method according to claim 1, wherein: The transmission delay provides a segmentation solution including one of the following: an end-to-end delay solution or a radio access network (RAN) partial delay solution.

3. The method according to claim 2, wherein: The monitoring / reporting configuration includes at least one of the following: Report timing configuration; Report granularity configuration; or Packet transmission timestamping scheme.

4. The method according to claim 3, wherein: The reporting timing configuration indicates a reporting frequency or a reporting time period.

5. The method according to claim 3, wherein: The reporting granularity configuration indicates that the data transmission delay is reported as at least one of the following: Average packet delay; Delay per packet; Packet delay distribution; or Packet delay distribution information.

6. The method according to claim 5, wherein: The report granularity configuration indicates that the data transmission delay is reported as the data packet delay distribution; The packet delay profile is included in an uplink protocol data unit (PDU) session frame; and The uplink PDU session frame includes: The first field is used to indicate the number of multiple delay ranges; as well as A plurality of field blocks, each field block including the number of data packets having delay values ​​falling within a delay range of the plurality of delay ranges.

7. The method according to claim 5, wherein: The report granularity configuration indicates that the data transmission delay is reported as the data packet delay distribution information; The packet delay distribution information is included in an uplink protocol data unit (PDU) session frame; and The uplink PDU session frame includes: The first field is used to identify the data packet delay distribution; A second field is used to indicate the number of parameters associated with the packet delay distribution; and A field block containing the values ​​of the stated number of parameters.

8. The method according to claim 5, wherein: The reporting granularity configuration indicates that the data transmission delay is reported as the per-packet delay; The per-packet delay is included in an uplink protocol data unit (PDU) session frame; and The PDU session frame includes: The first field is used to indicate the number of delay samples per data packet; as well as A plurality of second fields, each second field comprising per-packet delay samples.

9. The method according to claim 3, wherein: The packet transmission timestamp scheme indicates one of the following: Include a transmission timestamp in the packet header; or A transmission timestamp is included in the Packet Data Convergence Protocol header.

10. The method according to claim 3, wherein: The data transmission delay is associated with a user plane of the wireless network.

11. The method according to claim 10, wherein: The data transmission delay includes a downlink user plane data transmission delay.

12. The method according to claim 11, wherein: The method further comprises: relaying at least one downlink data packet from the core network to the wireless terminal device; and The transmission delay information item associated with the at least one downlink data packet is received from the wireless terminal device on the control plane of the wireless access network node, and includes end-to-end downlink transmission delay information or RAN part downlink transmission delay information associated with the at least one downlink data packet calculated by the wireless terminal device.

13. The method according to claim 12, wherein: The transmission delay information item is received in a control plane of the radio access network node as part of a radio resource control (RRC) measurement report.

14. The method according to claim 12, wherein: Generating the report and sending the report to the core network includes inserting the report into an NG Application Protocol (NGAP) message and sending the NGAP message to the core network in the control plane.

15. The method according to claim 12, wherein: Generating the report and sending the report to the core network includes: inserting the report into an E1 Application Protocol (E1AP) message in the control plane, and sending the E1AP message to a user plane of the radio access network node; extracting the report from the E1AP message and inserting the report into a PDU Session Information PDU in the user plane of the radio access network node; and The PDU session information PDU is sent to the core network in the user plane.

16. The method according to claim 10, wherein: The data transmission delay includes uplink user plane data transmission delay.

17. The method according to claim 16, wherein: The transmission delay information item received from the wireless terminal device includes time stamp information of at least one uplink data packet sent from the wireless terminal device.

18. The method according to claim 17, wherein: The time stamp information of the at least one uplink data packet transmitted from the wireless terminal device is included in a header of the at least one uplink data packet.

19. The method of claim 17, wherein: The transmission delay provides a segmentation scheme including the end-to-end delay scheme; and Generating the report according to the transmission delay configuration and sending the report to the core network includes: relaying the timestamp information to the core network for the core network to calculate the data transmission delay.

20. The method of claim 17, wherein: The transmission delay provides a segmented solution including the RAN part delay solution; and Generating the report according to the transmission delay configuration and sending the report to the core network includes: calculating, in the user plane of the radio access network node, RAN portion delay information associated with the at least one uplink data packet; Sending the RAN part delay information to a control plane of the radio access network node; and The RAN partial delay information is sent to the core network via an NGAP message in the control plane.

21. The method of claim 17, wherein: The transmission delay provides a segmented solution including the RAN part delay solution; and Generating the report according to the transmission delay configuration and sending the report to the core network includes: calculating, in the user plane of the radio access network node, RAN portion delay information associated with the at least one uplink data packet; as well as The RAN portion delay information is sent to the core network via an uplink PDU session information PDU to the core network in the user plane.

22. A method for monitoring / reporting a data transmission delay between the wireless terminal device and a core network in a wireless network by a wireless terminal device, comprising: Receiving a transmission delay configuration of a control plane from a wireless access network node, the transmission delay configuration specifying at least one of the following: Transmission delays in multiple segmentation schemes provide segmentation schemes; or a monitoring / reporting configuration for the data transmission delay among a plurality of monitoring / reporting configurations; as well as According to the transmission delay configuration, a transmission delay information item is sent to the radio access network node during a data transmission session between the core network and the wireless terminal device.

23. The method according to claim 22, wherein: The transmission delay provides a segmentation solution including one of the following: an end-to-end delay solution or a radio access network (RAN) partial delay solution.

24. The method according to claim 23, wherein: The monitoring / reporting configuration includes at least one of the following: Report timing configuration; Report granularity configuration; or Packet transmission timestamping scheme.

25. The method according to claim 24, wherein: The reporting timing configuration indicates a reporting frequency or a reporting time period.

26. The method according to claim 24, wherein: The reporting granularity configuration indicates that the data transmission delay is reported as at least one of the following: Average packet delay; Delay per packet; Packet delay distribution; or Packet delay distribution information.

27. The method of claim 26, wherein: The report granularity configuration indicates that the data transmission delay is reported as the data packet delay distribution; The packet delay profile is included in an uplink protocol data unit (PDU) session frame; and The uplink PDU session frame includes: The first field is used to indicate the number of multiple delay ranges; as well as A plurality of field blocks, each field block including the number of data packets having delay values ​​falling within a delay range of the plurality of delay ranges.

28. The method of claim 26, wherein: The report granularity configuration indicates that the data transmission delay is reported as the data packet delay distribution information; The packet delay distribution information is included in an uplink protocol data unit (PDU) session frame; and The uplink PDU session frame includes: The first field is used to identify the data packet delay distribution; A second field is used to indicate the number of parameters associated with the packet delay distribution; and A field block containing the values ​​of the stated number of parameters.

29. The method of claim 26, wherein: The reporting granularity configuration indicates that the data transmission delay is reported as the per-packet delay; The per-packet delay is included in an uplink protocol data unit (PDU) session frame; and The uplink PDU session frame includes: The first field is used to indicate the number of delay samples per data packet; as well as A plurality of second fields, each second field comprising per-packet delay samples.

30. The method of claim 24, wherein: The packet transmission timestamp scheme indicates one of the following: Include a transmission timestamp in the packet header; or A transmission timestamp is included in the Packet Data Convergence Protocol header.

31. The method of claim 22, wherein: The data transmission delay is associated with a user plane of the wireless network.

32. The method according to claim 31, wherein: The data transmission delay includes a downlink user plane data transmission delay.

33. The method of claim 32, wherein: The method comprises: obtaining reception timestamp information of at least one downlink data packet, and generating the transmission delay information item by calculating end-to-end downlink transmission delay information or RAN part downlink transmission delay information associated with the at least one downlink data packet according to the reception timestamp information and the transmission delay configuration; and The transmission delay information item is sent to a control plane of the radio access network node.

34. The method of claim 33, wherein: The transmission delay information item is sent as a part of a Radio Resource Control (RRC) measurement report.

35. The method of claim 31, wherein: The data transmission delay includes uplink user plane data transmission delay.

36. The method of claim 35, wherein: The transmission delay information item includes time stamp information of at least one uplink data packet transmitted from the wireless terminal device.

37. The method of claim 36, wherein: The time stamp information of the at least one uplink data packet transmitted from the wireless terminal device is included in a header of the at least one uplink data packet.

38. A method for providing a data transmission delay between a wireless terminal device and a core network by a core network node of a wireless network, comprising: Sending a transmission delay configuration to a wireless access network node, the transmission delay configuration specifying at least one of the following: Transmission delay in multiple segmentation schemes provides segmentation schemes; or a monitoring / reporting setting for the data transmission delay in a plurality of monitoring / reporting configurations; as well as During a data transmission session between the core network node and the wireless terminal device, a transmission delay information item is received from the wireless access network node, where the transmission delay information item is generated by the wireless access network node or the wireless terminal device according to the transmission delay configuration.

39. The method of claim 38, wherein: The transmission delay provides a segmentation solution including one of the following: an end-to-end delay solution or a radio access network (RAN) partial delay solution.

40. The method of claim 39, wherein: The monitoring / reporting configuration includes at least one of the following: Report timing configuration; Report granularity configuration; or Packet transmission timestamping scheme.

41. The method of claim 40, wherein: The reporting timing configuration indicates a reporting frequency or a reporting time period.

42. The method of claim 40, wherein: The reporting granularity configuration indicates that the data transmission delay is reported as at least one of the following: Average packet delay; Delay per packet; Packet delay distribution; or Packet delay distribution information.

43. The method of claim 42, wherein: The report granularity configuration indicates that the data transmission delay is reported as the data packet delay distribution; The packet delay profile is included in an uplink protocol data unit (PDU) session frame; and The uplink PDU session frame includes: The first field is used to indicate the number of multiple delay ranges; as well as A plurality of field blocks, each field block including the number of data packets having delay values ​​falling within a delay range of the plurality of delay ranges.

44. The method of claim 42, wherein: The report granularity configuration indicates that the data transmission delay is reported as the data packet delay distribution information; The packet delay distribution information is included in an uplink protocol data unit (PDU) session frame; and The uplink PDU session frame includes: The first field is used to identify the data packet delay distribution; A second field is used to indicate the number of parameters associated with the packet delay distribution; and A field block containing the values ​​of the stated number of parameters.

45. The method of claim 42, wherein: The reporting granularity configuration indicates that the data transmission delay is reported as the per-packet delay; The per-packet delay is included in an uplink protocol data unit (PDU) session frame; and The uplink PDU session frame includes: The first field is used to indicate the number of delay samples per data packet; as well as A plurality of second fields, each second field comprising per-packet delay samples.

46. ​​The method of claim 40, wherein: The packet transmission timestamp scheme indicates one of the following: Include a transmission timestamp in the packet header; or A transmission timestamp is included in the Packet Data Convergence Protocol header.

47. The method of claim 40, wherein: The data transmission delay is associated with a user plane of the wireless network.

48. The method of claim 47, wherein: The data transmission delay includes a downlink user plane data transmission delay.

49. The method of claim 48, wherein: The transmission delay information item is: received from the radio access network node; and The information includes end-to-end downlink transmission delay information or RAN part downlink transmission delay information associated with at least one downlink data packet, which is calculated by the wireless terminal device and relayed by the wireless access network node.

50. The method of claim 49, wherein: The transmission delay information item is received from a control plane of the radio access network node in a NG Application Protocol (NGAP) message.

51. The method of claim 49, wherein: The transmission delay information item is received from the user plane of the radio access network node as a header in a PDU session information PDU.

52. The method of claim 49, wherein: The transmission delay information item includes the RAN part downlink transmission delay information, and the method further includes: End-to-end downlink transmission delay information is calculated based on the transmission delay information item and core-to-access transmission delay information associated with the at least one downlink data packet.

53. The method of claim 47, wherein: The transmission delay provides a segmentation scheme including the end-to-end delay scheme; and The transmission delay information item includes timestamp information of at least one uplink data packet sent from the wireless terminal device.

54. The method of claim 47, wherein: The transmission delay provides a segmented solution including the RAN partial delay solution; and The transmission delay information item includes RAN part delay information calculated by the radio access network node.

55. The method of claim 54, wherein: The transmission delay information item is received from the control plane of the radio access network node in a NGAP message.

56. The method of claim 54, wherein: The transmission delay information item is received from the user plane of the radio access network node in a PDU session information PDU.

57. A wireless network node in a wireless network device, comprising a memory for storing instructions and a processor for executing the instructions to implement the method according to any one of claims 1 to 56.

58. A computer-readable non-transitory medium for storing computer instructions, which, when executed by a processor of a wireless network device, cause the wireless network device to implement the method according to any one of claims 1 to 56.