Method for measuring delay

Abstract

Methods, systems, and apparatus are provided for packet-level downlink delay monitoring. Multiple downlink user packets are received at a base station via a downlink NG User Plane Interface (NG-U) frame from a core network (CN) quality of service (QoS) stream. One or more of the multiple downlink user packets are sent to a user equipment (UE). Subsequently, a Next Generation Application Protocol (NGAP) message or an uplink NG-U frame is sent to the CN, the NGAP message or uplink NG-U frame including a radio access network (RAN) portion of the downlink delay of at least one downlink user packet and an associated Packet Data Convergence Protocol (PDCP) sequence number (SN), or a downlink NG-U frame SN encapsulating at least one downlink user packet.

Description

Technical Field

[0001] This topic generally relates to wireless communication. In particular, it relates to methods, devices, and systems for monitoring data packet latency. Background Technology

[0002] Based on the current 3GPP (Third Generation Partnership Project) specifications, it is not possible to directly measure the latency of each packet in a specific Quality of Service (QoS) flow between User Equipment (UE) and User Plane Function (UPF). To address this limitation, the 5G Radio Access Network (RAN) can measure the packet-level uplink / downlink latency between the UE and the RAN and report it to the Core Network (CN).

[0003] Measuring the latency of each data packet between the UE and the RAN presents significant challenges. For example, using a timestamp scheme to calculate the latency between the UE and the RAN could greatly increase the burden on the UE. Alternatively, if the UE reports the Packet Data Convergence Protocol (PDCP) queuing latency of each data packet (which is part of the uplink end-to-end latency) via Radio Resource Control (RRC) messages, it could consume substantial air interface resources. Furthermore, monitoring the latency of all data packets from all UEs may be impractical, as the RAN currently cannot determine which data packets to sample.

[0004] The end-to-end latency / delay used in this article refers to the time taken for communication from the source device to the destination. 5G Ultra Reliable Low Latency Communication (URLLC) is designed for services with stringent requirements for latency and availability. 5G mobile networks supporting URLLC must provide low latency, minimal packet loss, and minimal out-of-order packet arrival. For example, end-to-end low-latency communication for URLLC services requires 0.5 to 50 milliseconds at the application layer and less than 1 millisecond at the 5G radio interface.

[0005] To ensure low-end-to-end latency for URLLC, 5G networks need to support performance measurement definitions related to UL / DL (Uplink / Downlink) packet latency. Based on current 3GPP specifications, 5G networks currently only support average latency measurement at the Data Radio Bearer (DRB) / QoS stream level between the RAN and UE, but do not support measurement and reporting of per-packet latency between the RAN and UE.

[0006] Furthermore, a 5G base station (gNB) can be divided into two physical entities, called gNB-CU (Centralized Unit) and gNB-DU (Distributed Unit). gNB-CU provides support for higher layers of the protocol stack (e.g., Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and RRC), while gNB-DU provides support for lower layers of the protocol stack (e.g., RadioLink Control (RLC), Medium Access Control (MAC), and the physical layer). QoS monitoring requirements that are not currently supported should also be supported in the CU / DU gNB. Summary of the Invention

[0007] This topic relates to a method, apparatus, and system for providing packet delay monitoring in wireless communication systems.

[0008] In some embodiments, a method for packet-level downlink delay monitoring includes: receiving, at a base station, a plurality of downlink user packets from a Quality of Service (QoS) stream from a core network (CN) via a downlink NG User plane interface (NG-U) frame; and transmitting one or more of the plurality of downlink user packets to a user equipment (UE). The method further includes subsequently transmitting an NGAP message or an uplink NG-U frame to the CN, the NGAP message or uplink NG-U frame including: a radio access network (RAN) portion of the downlink delay of at least one downlink user packet, and an associated Packet Data Convergence Protocol (PDCP) sequence number (SN), or a downlink NG-U frame SN encapsulating at least one downlink user packet.

[0009] In some embodiments, a method for packet-level uplink delay monitoring includes: receiving a Packet Data Convergence Protocol (PDCP) Packet Data Unit (PDU) from a User Equipment (UE) at a base station. The method further includes a Radio Access Network (RAN) portion of the received PDCP PDU's uplink delay calculated by: adding the uplink delay of the PDCP PDU at the base station to the average delay reported by a UE at the UE associated with a Quality of Service (QoS) flow of the PDCP PDU; or adding the uplink delay of the PDCP PDU at the base station to the delay reported by the corresponding UE at the UE; and reporting the RAN portion of the packet-level uplink delay to the core network (CN).

[0010] In some other embodiments, an apparatus for wireless communication may include a memory storing instructions and processing circuitry communicating with the memory. The processing circuitry is configured to perform the methods described above when the processing circuitry executes the instructions.

[0011] In some other embodiments, a device for wireless communication may include a memory storing instructions and processing circuitry communicating with the memory. The processing circuitry is configured to perform the methods described above when the processing circuitry executes the instructions.

[0012] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the methods described above.

[0013] The above and other aspects and their embodiments are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0014] Figure 1 An example of a wireless communication system including a wireless base station and one or more user devices is shown.

[0015] Figure 2 An example of a base station (gNB) is shown.

[0016] Figure 3 An example of a user equipment (UE) is shown.

[0017] Figure 4 A swimlane diagram illustrating an example of communication between the gNB, UE, and core network (CN) according to this topic is shown.

[0018] Figure 5 A swimlane diagram illustrating an example of communication between the gNB, UE, and CN according to this topic is shown.

[0019] Figure 6A swimlane diagram illustrating an example of communication between the gNB, UE, and CN according to this topic is shown. Detailed Implementation

[0020] The subject matter will now be described in detail with reference to the accompanying drawings, which form part of this subject matter and illustrate specific examples of embodiments by way of illustration. However, it should be noted that the subject matter can be embodied in a variety of different forms, and therefore the covered or claimed subject matter is intended to be construed as not being limited to any of the embodiments set forth below.

[0021] Throughout the specification and claims, terms may have nuanced meanings suggested or implied in the context beyond their explicitly stated meanings. Similarly, the phrases “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and the phrases “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. For example, the claimed subject matter is intended to encompass all or part of the exemplary embodiments or combinations of embodiments.

[0022] Generally, terms can be understood at least in part from their usage in the context. For example, terms such as “and,” “or,” or “and / or” as used herein can include a variety of meanings that can depend at least in part on the context in which they are used. Typically, “or,” when used in a list of associations (such as A, B, or C), is intended to mean A, B, and C (used here in an inclusive sense) and A, B, or C (used here in an exclusive sense). Furthermore, the terms “one or more” or “at least one” as used herein, depending at least in part on the context, 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, depending at least in part on the context, terms such as “a,” “an,” or “the” can be understood to convey either a singular or a plural usage. Furthermore, the terms “based on” or “determined by” can be understood as not necessarily intended to convey an exclusive set of factors, but rather, at least in part, depending on the context, may allow for additional factors that are not necessarily explicitly described.

[0023] Figure 1A diagram of an example wireless communication system 100 (also referred to as wireless system 100, system 100) is shown, which includes a plurality of communication nodes (or simply nodes) configured to communicate wirelessly with each other. Typically, the plurality of communication nodes includes at least one user equipment 102 and at least one wireless access node 104. Figure 1 The example wireless communication system 100 is shown as including two user equipments 102 (including a first user equipment 102 (1) and a second user equipment 102 (2)) and a wireless access node 104. However, various other examples of wireless communication systems 100 including any combination of one or more user equipments 102 and / or one or more wireless access nodes 104 are also possible.

[0024] Typically, user equipment described herein (such as user equipment 102) may include a single electronic device or device capable of wireless communication over a network, or multiple electronic devices or devices (e.g., a network of multiple electronic devices or devices). User equipment may include, or be otherwise referred to as, a user terminal, user terminal equipment, or user equipment (UE). Furthermore, user equipment may be, or includes, mobile devices (such as mobile phones, smartphones, smartwatches, tablets, laptops, vehicles, or other vessels (as a non-limiting example, those driven by a person, motor, or engine, such as automobiles, airplanes, trains, ships, or bicycles)) or fixed or stationary devices (as a non-limiting example, such as desktop computers, or other computing devices that are typically stationary for extended periods (such as electrical appliances, other relatively heavy devices including those for the Internet of Things (IoT), or computing devices used in commercial or industrial environments)). In various embodiments, user equipment 102 may include transceiver circuitry 106 (also referred to as transceiver 106) coupled to antenna 108 to enable wireless communication with wireless access node 104. The transceiver circuit 106 may also be coupled to the processor 110, which may also be coupled to the memory 112 or other storage devices. The memory 112 may store instructions or code therein that, when read and executed by the processor 110, cause the processor 110 to implement the various methods described herein.

[0025] Furthermore, generally speaking, a wireless access node as described herein (such as wireless access node 104) may include a single electronic device or apparatus, or multiple electronic devices or apparatuses (e.g., a network of multiple electronic devices or apparatuses), and may include one or more base stations or other wireless network access points capable of wirelessly communicating with one or more user equipments and / or with one or more other wireless access nodes 104 via a network. For example, in various embodiments, wireless access node 104 may include a 4G LTE base station, a 5G NR base station, a 5G centralized unit base station, a 5G distributed unit base station, a Next Generation Node B (gNB), an Enhanced Node B (eNB), or other similar or next-generation (e.g., 6G) base station. Wireless access node 104 may include transceiver circuitry 114 (also referred to as transceiver 114) coupled to an antenna 116 (antenna 116 may include an antenna tower 118 in various ways) to enable wireless communication with user equipment 102 or another wireless access node 104. The transceiver circuit 114 may also be coupled to one or more processors 120, which may also be coupled to memory 122 or other storage devices. Memory 122 may store instructions or code therein that, when read and executed by processor 120, cause processor 120 to implement one or more of the methods described herein.

[0026] In various embodiments, two communication nodes in the wireless communication system 100—such as user equipment 102 and wireless access node 104, two user equipment 102 without wireless access node 104, or two wireless access nodes 104 without user equipment 102—can be configured to wirelessly communicate with each other in or through a mobile network and / or wireless access network according to one or more standards and / or specifications. Typically, standards and / or specifications can define rules or procedures under which communication nodes can wirelessly communicate, and these rules or procedures in various embodiments may include those for communication in the millimeter (mm) band, and / or those with multiple antenna schemes and beamforming capabilities. Furthermore or alternatively, the standards and / or specifications are those that define wireless access technologies and / or cellular technologies (such as, as a non-limiting example, Fourth Generation (4G) Long Term Evolution (LTE), Fifth Generation (5G) New Radio (NR)).

[0027] Furthermore, in the wireless communication system 100, communication nodes are configured to wirelessly transmit signals to each other. Typically, communication between two communication nodes in the wireless communication system 100 can be or includes both sending and receiving, and is usually simultaneous, depending on the perspective of the specific node in the communication. For example, for a given communication between a first node and a second node, where the first node sends a signal to the second node and the second node receives a signal from the first node, the first node can be referred to as a source or transmitting node or device, and the second node can be referred to as a destination or receiving node or device, and the communication can be considered as the first node sending and the second node receiving. Of course, since each communication node in the wireless communication system 100 can both send and receive signals, a single communication node can be both a transmitting / source node and a receiving / destination node simultaneously, or switch between being a source / transmitting node and a destination / receiving node.

[0028] Furthermore, specific signals can be characterized or defined as uplink (UL) signals, downlink (DL) signals, or sidelink (SL) signals. An uplink signal is a signal transmitted from user equipment 102 to radio access node 104. A downlink signal is a signal transmitted from radio access node 104 to user equipment 102. A sidelink signal is a signal transmitted from one user equipment 102 to another user equipment 102, or from one radio access node 104 to another radio access node 104. Moreover, for sidelink transmission, the first / source user equipment 102 transmits the sidelink signal directly to the second / destination user equipment 102 without forwarding it to radio access node 104.

[0029] Furthermore, the signals transmitted between communication nodes in the wireless communication system 100 can be characterized or defined as data signals or control signals. Typically, data signals are signals that include or carry data (such as multimedia data, e.g., voice data and / or image data), while control signals are signals that carry control information that configures the communication nodes in a specific way to facilitate communication between them, or otherwise controls how the communication nodes transmit data signals to each other. Additionally, specific signals can be defined or characterized as combinations of data / control and uplink / downlink / sidelink signals, including uplink control signals, uplink data signals, downlink control signals, downlink data signals, sidelink control signals, and sidelink data signals.

[0030] For at least some specifications (such as 5G NR), data signals and control signals are transmitted and / or carried on physical channels. Typically, a physical channel corresponds to a set of time-frequency resources used for signal transmission. Different types of physical channels can be used to transmit different types of signals. For example, physical data channels (or simply data channels) are used to transmit data signals, and physical control channels (or simply control channels) are used to transmit control signals. Example types of physical data channels include, but are not limited to, Physical Downlink Shared Channel (PDSCH) for transmitting downlink data signals, Physical Uplink Shared Channel (PUSCH) for transmitting uplink data signals, and Physical Sidelink Shared Channel (PSSCH) for transmitting sidelink data signals. Furthermore, example types of physical control channels include, but are not limited to, the Physical Downlink Control Channel (PDCCH) for transmitting downlink control signals, the Physical Uplink Control Channel (PUCCH) for transmitting uplink control signals, and the Physical Sidelink Control Channel (PSCCH) for transmitting sidelink control signals. As used herein, for simplicity, unless otherwise stated, a particular type of physical channel is also used to refer to the signals transmitted on that particular type of physical channel, and / or the transmission on that particular type of transmission. For example, PDSCH refers to the Physical Downlink Shared Channel itself, downlink data signals transmitted on the PDSCH, or downlink data transmission. Therefore, when a communication node is sending or receiving a PDSCH, it means that the communication node is sending or receiving signals on the PDSCH.

[0031] Additionally, for at least some specifications such as 5G NR and / or for at least some types of control signals, the control signals transmitted by the communication nodes may include control information, which includes information required to enable the transmission of one or more data signals between the communication nodes, and / or information required to schedule one or more data channels (or one or more transmissions on data channels). For example, such control information may include: information required to correctly receive, decode, and demodulate data signals received on physical data channels during data transmission; and / or information required for uplink scheduling authorization, which informs the user equipment of the resources and transmission formats used for uplink data transmission. In some embodiments, the control information includes downlink control information (DCI) transmitted from the radio access node 104 to the user equipment 102 in the downlink direction. In other embodiments, the control information includes uplink control information (UCI) or sidelink control information (SCI), the uplink control information being sent from user equipment 102 to radio access node 104 in the uplink direction, and the sidelink control information being sent from one user equipment 102 (1) to another user equipment 102 (2) in the sidelink direction.

[0032] Furthermore, in the wireless communication system 100, the time slot format for multiple time slots or frames can be configured by the wireless access node 104 or specified by a protocol. In some examples, time slots can be indicated or specified as downlink time slots, flexible time slots, or uplink time slots. Additionally, in various embodiments, Orthogonal Frequency Division Multiplexing (OFDM) symbols can be indicated or specified as downlink symbols, flexible symbols, or uplink symbols.

[0033] Figure 2 An example of base station 200 is shown. Example base station 200 may include wireless transmit / receive (Tx / Rx) circuitry 208 to transmit / receive communications with a UE and / or other base stations. Base station 200 may also include network interface circuitry 209 (e.g., optical or wired interconnect, Ethernet, and / or other data transmission media / protocols) to enable the base station to communicate with other base stations and / or the core network. Base station 200 may optionally include input / output (I / O) interface 206 for communication with operators, etc.

[0034] Base station 200 may also include system circuitry 204. System circuitry 204 may include one or more processors 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more processors 124 to perform base station functions. Parameters 228 may include parameters that support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0035] The term “network” (as indicated by reference numeral 200) used herein is interchangeable with gNB in ​​NR, eNB in ​​LTE, base station, core network, or radio access node of a wireless network.

[0036] Figure 3An example of an electronic device for implementing a terminal device 300 (e.g., a user equipment (UE)) is shown. The UE 300 may be a mobile device, such as a smartphone or a mobile communication module located in a vehicle. The UE 300 may include a communication interface 302, system circuitry 304, input / output interfaces (I / O) 306, display circuitry 308, and storage device 309. The display circuitry may include a user interface 310. The system circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuit. The system circuitry 304 may be implemented, for example, using one or more systems on a chip (SoC), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. The system circuitry 304 may be part of an implementation of any desired functionality in the UE 300. In this regard, system circuitry 304 may include logic that facilitates, for example, decoding and playing music and video (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections (as an example, for internet connections); establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR (infrared) sensors), and other types of inputs.

[0037] Reference Figure 3The communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 that processes signals transmitted and received via one or more antennas 314. The communication interface 302 may include one or more transceivers. These transceivers may be wireless transceivers, which include modulation / demodulation circuitry, digital-to-analog converters (DACs), shapers, analog-to-digital converters (ADCs), filters, waveform shapers, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals may conform to any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), channels, bit rates, and encodings. As a specific example, communication interface 302 may include transceivers supporting transmission and reception under the following standards: 2G, 3G, Bluetooth, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), and 5G standards. However, the technologies described below, whether originating from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies, are applicable to other wireless communication technologies.

[0038] Reference Figure 3 System logic 304 may include one or more processors 321 and memory 322. Memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. Processor 321 is configured to execute instructions 326 to implement the desired functions of UE 300. Parameters 328 can provide and specify configuration and operational options for instructions 326. Memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that UE 300 will send or has received through communication interface 302. In various embodiments, system power for UE 300 may be provided by power storage devices such as batteries or transformers.

[0039] Downlink packet delay monitoring Figure 4 A swimlane diagram 400 shows an example of communication 400 between gNB 200, UE 300 and CN 250 according to this topic.

[0040] When it is necessary to set or modify one or more QoS flows, CN 250 can send a Next Generation Application Protocol (NGAP) message to gNB 200 in step S401 via the NextGen (NG) control plane interface (the interface between the Next Generation Radio Access Network (NR-RAN) node and the AMF). The NGAP message can request the establishment or modification of QoS flows and can include packet delay sampling configuration for at least one QoS flow. The packet delay sampling configuration can instruct the RAN how to select packets for this QoS flow as sampled packets for per-packet delay monitoring and / or reporting.

[0041] The packet delay sampling configuration can be configured for uplink and / or downlink and includes at least one of the following: (1) a delay threshold, and one or more other sampling rules, for instructing the RAN to report only the packet delay results of selected packets whose measured RAN partial delay exceeds the specified threshold; (2) a sample packet interval, for instructing the RAN to select one packet for monitoring and reporting every few packets; (3) a sample packet interval, for instructing the RAN to select one packet for monitoring and reporting every few packets; (4) a sample time period, for instructing the RAN to select one packet for monitoring and reporting at certain time intervals; (5) a sample percentage, for instructing the RAN to select the percentage of all packets for monitoring and reporting; and (6) a start time and an end time, for instructing the RAN to select all packets within the time interval specified by the start time and end time for monitoring and reporting.

[0042] Packet delay sampling configuration can be set up for downlink, or for both downlink and uplink, which can be applied to downlink packet selection. NGAP messages can include PDU session resource setup request, PDU session resource modification request, and initial context setup request, among others.

[0043] After a QoS flow is successfully established or modified, in S402, CN 250 sends the QoS flow user data packet to gNB 200 via an NG User Plane Interface (NG-U) frame (NG-U interface, the user plane interface between the Next Generation Radio Access Network (NR-RAN) node and the UPF at CN). If CN 250 decides to select this user data packet as a sample data packet for downlink delay monitoring, CN 250 may include a packet monitoring indication (flag) in the NG-U frame carrying this user data packet.

[0044] In S403, gNB 200 can receive user data packets for a QoS stream via an NG-U frame sent by CN 250. gNB can decide whether to measure and / or report the downlink delay for this user data packet based on at least one of the following: (1) if CN 250 includes a packet monitoring indication in the NG-U frame, gNB 200 can select this user data packet as a sample for downlink delay monitoring; that is, measure and report the downlink delay for this user data packet; (2) if gNB 200 receives a packet delay sampling configuration for downlink for this QoS stream, gNB 200 can decide whether to select this user data packet for downlink delay monitoring based on the received packet delay sampling configuration.

[0045] In S404, gNB 200 can send user data packets to UE300 via PDCP Packet Data Unit (PDU); that is, the user data packets are encapsulated in this PDCP PDU.

[0046] In S405, if the selected user data packet is used as a sample data packet for downlink delay monitoring, the gNB 200 can calculate the RAN portion (including the delay on the air interface) of the downlink delay of this data packet. For example, for RLC UM mode, based on the received HARQ feedback information, the delay between receiving the user data packet (e.g., an IP packet in gNB 200) and the UE 300 receiving the last part of the RLC SDU (PDCP PDU) data packet is calculated; or for AM mode, based on the received RLC ACK, the delay between receiving the user data packet (e.g., an IP packet in gNB 200) and the UE 300 receiving the last part of the RLC SDU (PDCP PDU) data packet is calculated.

[0047] In the case of a gNB 200 with CU / DU separation, in step S404, the gNB-CU can send a PDCP PDU to the UE via the gNB-DU, wherein the gNB-CU sends a downlink New Radio unlicensed (NR-U) data packet (e.g., a downlink user data PDU to the gNB-DU), and the PDCP PDU is encapsulated in the NR-U data packet.

[0048] To calculate the RAN portion of the downlink delay for this data packet, when the gNB-CU sends a user data packet (which can be encapsulated in an NR-U packet) encapsulated in a PDCP PDU to the gNB-DU via an NR-U packet, the gNB-CU can include a delay polling indication for each data packet in this NR-U packet.

[0049] In S404, after the gNB-DU sends the PDCP PDU to the UE 300, if a packet delay polling indication for the PDCP PDU has been received previously, the gNB-DU can calculate the downlink delay DU portion of the PDCP PDU (including the delay on the air interface) and can send the downlink delay DU portion of the PDCP PDU along with the associated PDCP PDU SN (e.g., downlink data transmission status PDU) in the uplink NR-U packet. For example, for RLC UM mode, the delay between receiving the PDCP PDU from the gNB-DU and the UE 300 receiving the last part of the RLC SDU (PDCP PDU) packet can be calculated based on the received HARQ feedback information; or, for AM mode, the delay between receiving the PDCP PDU from the gNB-DU and the UE 300 receiving the last part of the RLC SDU (PDCP PDU) packet can be calculated based on the received RLC ACK.

[0050] After the gNB-CU receives the DU portion of the downlink delay of the PDCP PDU and the associated PDCP PDU SN via the uplink NR-U data packet sent by the gNB-DU, the gNB-CU calculates the RAN portion of the downlink delay of the PDCP PDU by summing the DU portion of the downlink delay of the PDCP PDU, the downlink F1-U interface of the PDCP PDU, and the PDCP queuing delay of the PDCP PDU at the gNB-CU.

[0051] In S406, if the delay of one or more selected packets needs to be reported based on the received Packet Delay Sampling Configuration, the gNB 200 can report the calculated RAN portion of the downlink delay of one or more user packets through the control plane or user plane; that is, the gNB 200 can send an NGAP message or an uplink NG-U frame to the CN 250, which includes one or more calculated RAN portions of the downlink delay of one or more user packets, and the associated packet sequence number (PDCP PDU SN or DL ​​NG-U frame SN) of the corresponding user packet can be encapsulated in the message or uplink NG-U frame.

[0052] In this way, CN 250 can obtain the RAN portion of the downlink delay of associated user data packets and monitor the performance of QoS flows. Furthermore, CN 250 can calculate the end-to-end downlink delay between UPF 350 and UE300 by adding the reported RAN portion of the downlink delay of associated user data packets to the downlink delay of associated user data packets between UPF 350 and the RAN.

[0053] Estimate the latency of each UL packet using the average D1 latency reported by the UE. Figure 5 Swimlane diagram 500 shows another example of communication 400 between gNB 200, UE 300 and CN 250 according to this topic.

[0054] In S501, when one or more QoS flows need to be established or modified, CN 250 can send a message to gNB200 via the NG interface. This message can request the setting or modification of these QoS flows and can include a Packet Delay Sampling Configuration for at least one QoS flow. This Packet Delay Sampling Configuration instructs the RAN how to select packets for this QoS flow as sampled packets for per-packet delay monitoring and reporting. This Packet Delay Sampling Configuration can be configured for uplink and / or downlink, and this configuration can be applied to downlink packet selection.

[0055] In S503, gNB 200 can receive the average D1 delay (for DRB or QoS flow) at UE 300 via the RRC measurement report or MAC CE frame sent by UE 300 in S502.

[0056] The average D1 latency can be the average UL PDCP queuing latency at the DRB level. The UE 300 can measure the UL PDCP queuing latency at the DRB level. Assuming all QoS flows mapped to the same DRB receive the same QoS treatment, the gNB 200 is responsible for converting DRB-level latency to QoS-level latency. Furthermore, if multiple DRBs map to the same QoS, the gNB 200 can calculate the QoS-level latency.

[0057] In S504, gNB 200 can send an authorized resource signaling message to UE 300 to indicate to UE 300 that radio resources are available for uplink data transmission.

[0058] In S505, UE 300 can send user data packets to gNB200 via PDCP PDU (i.e., user data packets are encapsulated in this PDCP PDU).

[0059] In S506, gNB 200 can receive user data packets sent by UE 300. Based on the received packet delay sampling configuration for uplink, gNB 200 can decide whether to select the user data packet as a sample data packet for uplink delay measurement.

[0060] Furthermore, in S506, if a QoS flow user data packet sent by the UE is selected as the sample data packet for uplink delay monitoring, the gNB 200 can calculate the uplink delay of this data packet at the gNB (including the delay on the air interface, but excluding the D1 delay at the UE). For example, based on the provided scheduling authorization, the delay between the time when the PDCP PDU is scheduled (the user data packet is encapsulated in this PDCP PDU) and the time when the corresponding PDCP SDU (the user data packet encapsulated in the PDCP PDU) is sent to the CN is calculated.

[0061] The gNB 200 can calculate the RAN portion of the uplink delay of the selected user's data packet delay by adding the uplink delay of this data packet at the gNB 200 to the average D1 delay associated with the QoS flow of this data packet reported by the corresponding UE.

[0062] In the case of a gNB with separate CU / DU, in S505, the gNB-CU can receive user data packets sent by the UE 300 through the gNB-DU. The gNB-DU sends uplink NR-U data packets (e.g., UL user data PDU) to the gNB-CU, and the PDCP PDU sent by the UE 300 is encapsulated in this NR-U data packet.

[0063] To calculate the RAN portion of the uplink delay of a data packet, when the gNB-DU sends a PDCP PDU to the gNB-CU via an uplink NR-U data packet, the gNB-DU may include the DU portion of the uplink delay of this PDCP PDU (including the delay on the air interface) and the associated PDCP PDU SN in this uplink NR-U data packet. For example, based on the provided scheduling authorization, the gNB-DU may calculate the DU portion of the uplink delay of this PDCP PDU from the time the PDCP PDU is scheduled (when the user data packet is encapsulated in this PDCP PDU) until the time the gNB-DU receives the corresponding PDCP SDU (the user data packet encapsulated in the PDCP PDU). If the UE 300 sends the average D1 delay associated with the Quality of Service (QoS) flow of this PDCP PDU via a MAC CE frame, the gNB-DU will receive this MAC CE frame and add this average D1 delay to the finally calculated DU portion of the uplink delay of this PDCP PDU.

[0064] After the gNB-CU receives the DU portion of the uplink delay of the PDCP PDU, along with the associated PDCP PDU SN and PDCP PDU, via the uplink NR-U data packet sent by the gNB-DU, if the gNB-CU receives the delay via an RRC message sent by the UE 300, the gNB-CU can calculate the RAN portion of the downlink delay of the PDCP PDU by summing the DU portion of the uplink delay of the PDCP PDU, the uplink F1-U interface of this PDCP PDU, and the average D1 delay reported by the corresponding UE associated with the QoS flow of this data packet.

[0065] In S507, if the delay of the selected packet needs to be reported based on the received packet delay sampling configuration, the gNB 200 can report the RAN portion of the calculated uplink delay of the packet to the CN 250; that is, the gNB 200 can send an uplink NG-U frame to the CN 250, which includes the RAN portion of the calculated uplink delay of the packet and the associated PDCP PDUSN.

[0066] In this way, CN 250 can obtain the RAN portion of the uplink delay of associated user data packets and monitor the performance of QoS flows; in addition, UPF 350 can calculate the end-to-end uplink delay between UPF 350 and UE300 by adding the reported RAN portion of the uplink delay of associated user data packets to the uplink delay of associated user data packets between UPF 350 and RAN.

[0067] Calculate UL single packet delay using D1 single packet delay reported by UE Figure 6 Swimlane diagram 600 shows yet another example of communication between a base station (gNB), user equipment (UE), and core network (CN) according to this topic.

[0068] As mentioned above Figure 4 and Figure 6 The description states that when it is necessary to set or modify one or more QoS flows, the CN sends the message in S601 to the gNB 200 via the NG interface. This message requests the setting or modification of these QoS flows and includes a Packet Delay Sampling Configuration for at least one QoS flow. This Packet Delay Sampling Configuration can be configured for uplink and / or downlink, and this configuration can be applied to downlink packet selection.

[0069] In S602, before gNB 200 sends authorization resource signaling for uplink user data packet transmission to UE 300, gNB 200 can decide whether to select the user data packet as a sample data packet for uplink delay measurement based on the received uplink data packet delay sampling configuration.

[0070] In S603, gNB 200 can send an authorization resource signaling to UE 300 to indicate to UE 300 that radio resources are available for uplink data transmission. If gNB 200 decides to select uplink user data packets associated with the authorization resource signaling as sample data packets for uplink delay measurement, gNB 200 can include a D1 requirement indication in the authorization signaling to instruct UE 300 to report the D1 delay of the transmitted data packets(s) associated with the authorized resources.

[0071] In S604, UE 300 can send user data packets to gNB 200 via PDCP PDU (i.e., the user data packets are encapsulated in this PDCP PDU).

[0072] In S605, UE 300 can send an L1 or L2 frame to gNB 200, including the D1 delay of at least one PDCP PDU and the corresponding PDCP PDU SN. For example, UE 300 can send this information via an L2 MAC CE frame. The D1 delay can be the UL PDCP queuing delay of the corresponding data packet.

[0073] In S606, gNB 200 can calculate the uplink delay (including the delay on the air interface, but excluding the D1 delay on the UE side) of the selected data packet at gNB 200. For example, based on the provided scheduling authorization, gNB 200 can calculate the delay from the time the PDCP PDU is scheduled (the user data packet is encapsulated in this PDCP PDU) to the time the corresponding PDCP SDU (the user data packet encapsulated in the PDCPPDU) is sent to CN 250.

[0074] The gNB 200 can calculate the RAN portion of the uplink delay of the selected user data packet delay by adding the uplink delay of this data packet at the gNB to the D1 delay of the corresponding data packet reported by the corresponding UE.

[0075] In the case of a gNB with separate CU / DU, in S604, the gNB-CU can receive user data packets sent by the UE 300 through the gNB-DU. The gNB-DU sends uplink NR-U data packets (e.g., UL user data PDU) to the gNB-CU, and the PDCP PDU sent by the UE 300 is encapsulated in this NR-U data packet.

[0076] To calculate the RAN portion of the uplink delay for this data packet, when the gNB-DU sends a PDCP PDU to the gNB-CU via an uplink NR-U data packet, the gNB-DU may include the DU portion of the uplink delay for this PDCP PDU (including the delay on the air interface) and the associated PDCP PDU SN in this uplink NR-U data packet. For example, based on the provided scheduling authorization, the gNB-DU may calculate the DU portion of the uplink delay for this PDCP PDU, starting from the time the PDCP PDU is scheduled (when the user data packet is encapsulated in this PDCP PDU) and ending at the time the gNB-DU receives the corresponding PDCP SDU (the user data packet encapsulated in the PDCP PDU). If the UE 300 sends the D1 delay of this PDCP PDU via a MAC CE frame, the gNB-DU will receive this MAC CE frame and add the D1 delay of this PDCP PDU to the finally calculated DU portion of the uplink delay for this PDCP PDU.

[0077] After the gNB-CU receives the DU portion of the uplink delay of the PDCP PDU, along with the associated PDCP PDU SN and PDCP PDU, via the uplink NR-U data packet sent by the gNB-DU, if the gNB-CU receives the delay via an RRC message sent by the UE 300, the gNB-CU can calculate the RAN portion of the downlink delay of the PDCP PDU by summing the DU portion of the uplink delay of the PDCP PDU, the uplink F1-U interface of this PDCP PDU, and the D1 delay reported by the corresponding UE associated with this data packet.

[0078] In S607, if it is necessary to report the delay of the selected packet based on the received packet delay sampling configuration, the gNB 200 can report the calculated RAN portion of the uplink delay of the packet through the user plane; that is, the gNB can send an uplink NG-U frame to the UPF 350, which includes the calculated RAN portion of the uplink delay of the packet and the associated PDCP sequence number (SN).

[0079] In this way, CN 250 can obtain the RAN portion of the uplink delay of associated user data packets and monitor the performance of QoS flows. Furthermore, CN 250 can calculate the end-to-end uplink delay between CN 250 (i.e., the UPF on the CN side) and UE 300 by adding the RAN portion of the reported uplink delay of associated user data packets to the uplink delay of associated user data packets between the UPF and the RAN.

[0080] The above description and accompanying drawings provide specific example embodiments and implementations. However, the described subject matter can be implemented in a variety of different forms, and therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the example embodiments set forth herein. A reasonably broad scope is intended for the claimed or covered subject matter. Among other things, the subject matter can be implemented as a method, apparatus, component, system, or non-transitory computer-readable medium for storing computer code. Accordingly, embodiments can take the form of, for example, hardware, software, firmware, storage medium, or any combination thereof. For example, the above-described method embodiments can be implemented by a component, apparatus, or system including a memory and a processor by executing computer code stored in the memory.

[0081] Throughout the specification and claims, terms may have nuanced meanings suggested or implied in the context beyond their expressly stated meanings. 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 different embodiments. For example, the claimed subject matter is intended to encompass all or a combination of some of the exemplary embodiments.

[0082] Generally, terms can be understood at least in part from their usage in context. For example, terms such as “and,” “or,” or “and / or” as used herein can include a variety of meanings that can depend at least in part on the context in which they are used. Typically, “or,” when used in a list of associations (such as A, B, or C), is intended to mean A, B, and C (used here in an inclusive sense) and A, B, or C (used here in an exclusive sense). Furthermore, depending at least in part on the context, the term “one or more,” as used herein, can be used to describe any feature, structure, or characteristic in a singular sense, or it can be used to describe a combination of features, structures, or characteristics in a plural sense. Similarly, depending at least in part on the context, terms such as “a,” “an,” or “the” can be understood to convey either a singular or a plural usage. Moreover, the term “based on” can be understood not necessarily to convey an exclusive set of factors, but rather, depending at least in part on the context, allows for additional factors that may not be explicitly described.

[0083] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable using this solution should be included or included in any single implementation thereof. Rather, references to features and advantages are to be understood as meaning that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, discussions of features and advantages and similar language throughout this specification may (but not necessarily) refer to the same embodiments.

[0084] Furthermore, in one or more embodiments, the described features, advantages, and characteristics of this solution can be combined in any suitable manner. Based on the description herein, those skilled in the art will recognize that this solution can be practiced without one or more specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments, which may not be present in all embodiments of this solution.

[0085] The subject matter of this disclosure may also include the following: The first aspect includes a method for packet-level downlink delay monitoring, the method comprising: receiving at a base station a plurality of downlink user packets from a quality of service (QoS) stream from a core network (CN) via a downlink NG user plane interface (NG-U) frame; and sending one or more of the plurality of downlink user packets to a user equipment (UE), subsequently: sending an NGAP message or an uplink NG-U frame to the CN, the NGAP message or uplink NG-U frame including: a radio access network (RAN) portion of the downlink delay of at least one downlink user packet, and an associated packet data convergence protocol (PDCP) sequence number (SN), or a downlink NG-U frame SN encapsulating at least one downlink user packet.

[0086] The second aspect includes the method of the first aspect, wherein the base station includes a Centralized Unit (CU) and a Distributed Unit (DU), and the method further includes: sending a delay polling indication for each data packet in a downlink New Radio User Plane (NR-U) data packet for a PDCP PDU encapsulated in an NR-U data packet from the CU to the DU; sending the received PDCP PDU to the UE from the DU; and subsequently: in response to receiving the data packet delay polling indication for the PDCP PDU; calculating the DU portion of the downlink delay of the PDCP PDU from the DU; and sending the DU portion of the downlink delay of the PDCP PDU and the associated PDCP PDU SN to the CU in an uplink NR-U data packet.

[0087] The third aspect includes the method of any of the foregoing aspects, the method further comprising: determining whether to measure and / or report downlink latency for at least one downlink user data packet encapsulated in a downlink NG-U frame according to at least one of the following: whether the downlink NG-U frame includes a packet monitoring indication, and if so, selecting at least one downlink user data packet as a sample for downlink latency monitoring; or whether a packet latency sampling configuration for a downlink QoS flow is received, and if so, determining whether to select at least one downlink user data packet for downlink latency monitoring.

[0088] The fourth aspect includes the method of any of the foregoing aspects, further comprising: receiving a message from the CN including a packet delay sampling configuration for at least one QoS flow, wherein the packet delay sampling configuration instructs the RAN how to select packets of the QoS flow as sample packets for each packet-level delay monitoring and / or reporting; and the packet delay sampling configuration is configured for uplink and / or downlink, and includes at least one of the following: a delay threshold and sampling rules for instructing the RAN to report only the packet delay results of selected packets whose measured RAN partial delay exceeds the indicated threshold; a sample packet interval for instructing the RAN to select one packet for monitoring and reporting every several packets; a sample time period for instructing the RAN to select one packet for monitoring and reporting at regular time intervals; a sample percentage for instructing the RAN to select a percentage of all packets for monitoring and reporting; and a start time and an end time for instructing the RAN to select all packets within a specified time period between the start time and the end time for monitoring and reporting.

[0089] The fifth aspect includes a method for packet-level uplink delay monitoring, comprising: receiving a Packet Data Convergence Protocol (PDCP) Packet Data Unit (PDU) from a User Equipment (UE) at a base station; calculating the radio access network (RAN) portion of the uplink delay of the received PDCP PDU by: adding the uplink delay of the PDCP PDU at the base station to the average delay reported by a UE at the UE associated with a Quality of Service (QoS) flow of the PDCP PDU; or adding the uplink delay of the PDCP PDU at the base station to the delay reported by the corresponding UE at the UE; and reporting the RAN portion of the packet-level uplink delay to the core network (CN).

[0090] The sixth aspect includes the method of the fifth aspect, which further includes receiving the average delay at the UE from the UE via a Media Access Control (MAC) Control Element (CE) frame.

[0091] The seventh aspect includes the method of the fifth or sixth aspect, which further includes: sending a necessary instruction to the UE in the authorization signaling to instruct the UE to report the delay of one or more data packets (associated with the corresponding authorized resources) in accordance with the authorization signaling.

[0092] The eighth aspect includes the methods of the fifth to seventh aspects, the method further comprising: receiving at least one PDCP PDU delay and a corresponding PDCP PDU sequence number (SN) from the UE via a MAC CE frame.

[0093] The ninth aspect includes the method of any one of the fifth to eighth aspects, the method further comprising: sending an uplink NG user plane interface (NG-U) frame to the CN, including the RAN portion of the calculated packet uplink delay and the associated PDCP PDU SN.

[0094] The tenth aspect includes the methods of the fifth to ninth aspects, wherein the base station includes a centralized unit (CU) and a distributed unit (DU), and the method further includes: transmitting a received PDCP PDU from the UE via an uplink NR-U data packet from the DU to the CU, wherein the uplink NR-U data packet includes the DU portion of the PDCP PDU with uplink delay and the associated PDCP PDU SN.

[0095] The eleventh aspect includes the methods of aspects five through nine, the method further comprising: receiving, via a MAC CE frame, the average delay associated with the QoS flow of the PDCP PDU at the UE, or the delay of the PDCP PDU at the UE, from the UE, and then adding the delay at the UE to the DU portion of the uplink delay of the PDCP PDU.

[0096] The twelfth aspect includes the methods of aspects five through eleven, wherein the PDCP PDU includes user data packets, and the method further includes: determining, based on the received data packet delay sampling configuration for uplink, whether to select the user data packet as a sample data packet for uplink delay measurement.

[0097] The thirteenth aspect includes the methods of aspects five through twelve, further comprising: receiving a message from the CN including a packet delay sampling configuration for at least one QoS flow, wherein the packet delay sampling configuration instructs the RAN how to select packets in the QoS flow as sample packets for each packet-level delay monitoring and / or reporting; and the packet delay sampling configuration is configured for uplink and / or downlink, and includes at least one of the following: a delay threshold and sampling rules for instructing the RAN to report only the packet delay results of selected packets whose measured RAN partial delay exceeds the indicated threshold; a sample packet interval for instructing the RAN to select one packet for monitoring and reporting every few packets; a sampling time period for instructing the RAN to select one packet for monitoring and reporting at regular time intervals; a sampling percentage for instructing the RAN to select a percentage of all packets for monitoring and reporting; and a start time and an end time for instructing the RAN to select all packets within a specified time period between the start time and the end time for monitoring and reporting.

[0098] The fourteenth aspect includes a wireless communication device comprising: a processor; and a memory in communication with the processor, the memory storing a plurality of instructions executable by the processor to enable the device to implement the methods of the first to thirteenth aspects.

[0099] The fifteenth aspect includes a non-transitory computer-readable medium comprising a plurality of operable instructions, which, when executed by one or more processors, implement the methods of the first through thirteenth aspects.

Claims

1. A method for packet-level downlink latency monitoring, comprising: At the base station, multiple downlink user data packets are received from the Quality of Service (QoS) stream of the core network (CN) via downlink NG user plane interface (NG-U) frames; as well as Send one or more of the plurality of downlink user data packets to the user equipment (UE), and then: Sending an NGAP message or an uplink NG-U frame to the CN, the NGAP message or uplink NG-U frame including: The radio access network (RAN) portion of the downlink delay of at least one downlink user data packet, and The associated Packet Data Convergence Protocol (PDCP) sequence number SN, or the downlink NG-U frame SN that encapsulates the at least one downlink user data packet.

2. The method according to claim 1, wherein: The base station includes centralized units (CU) and distributed units (DU), and The method further includes: The CU sends a delay polling indication for each packet in the downlink New Radio User Plane (NR-U) data packet for PDCP PDU encapsulated in the NR-U data packet to the DU. The DU sends the received PDCP PDU to the UE; and subsequently: In response to receiving a packet delay polling indication for the PDCP PDU: The DU portion of the downlink delay of the PDCP PDU is calculated from the DU; and the DU portion of the downlink delay of the PDCP PDU and the associated PDCP PDU SN are sent to the CU in the uplink NR-U data packet.

3. The method according to claim 1 further includes: Determine whether to measure and / or report downlink latency for the at least one downlink user data packet encapsulated in the downlink NG-U frame based on at least one of the following: If the downlink NG-U frame includes a packet monitoring indication, then at least one downlink user data packet is selected as a sample for downlink latency monitoring; or If a packet delay sampling configuration for downlink QoS flow has been received, then determine whether to select the at least one downlink user packet for downlink delay monitoring.

4. The method according to claim 1 further includes: Receive a message from the CN including a packet delay sampling configuration for at least one QoS flow, wherein The packet delay sampling configuration instructs the RAN on how to select packets from the QoS flow as sample packets for each packet-level delay monitoring and / or reporting; and The packet delay sampling configuration is configured for uplink and / or downlink, and includes at least one of the following: Delay thresholds and sampling rules are used to instruct the RAN to report only the packet delay results of selected packets whose measured RAN portion delay exceeds the indicated threshold; The sampling data packet interval is used to instruct the RAN to select a data packet for monitoring and reporting every few data packets; The sampling time period is used to instruct the RAN to select a data packet for monitoring and reporting at regular time intervals; The sampling percentage is used to indicate to the RAN the percentage of all data packets selected for monitoring and reporting; and The start time and end time are used to instruct the RAN to select all data packets within a specified time period between the start time and the end time for monitoring and reporting.

5. A method for packet-level uplink latency monitoring, comprising: At the base station, receive Packet Data Convergence Protocol (PDCP) Packet Data Units (PDUs) from User Equipment (UE). The uplink delay of the received PDCP PDU is calculated in the Radio Access Network (RAN) portion as follows: Add the uplink delay of the PDCP PDU at the base station to the average delay reported by the UE at the UE that is associated with the QoS flow of the PDCP PDU; or Add the uplink delay of the PDCP PDU at the base station to the delay reported by the corresponding UE at the UE; as well as Report the RAN portion of the uplink delay at the packet level to the core network CN.

6. The method according to claim 5 further includes: The average latency at the UE is received from the UE via a Media Access Control (MAC) Control Element (CE) frame.

7. The method according to claim 5 further includes: The authorization signaling sends the necessary indication to the UE, instructing the UE to report the delay of one or more data packets that have been sent and are associated with the corresponding authorized resources, in accordance with the authorization signaling.

8. The method according to claim 5 further includes: At least one PDCP PDU delay and the corresponding PDCPPDU sequence number (SN) at the UE are received from the UE via a MAC CE frame.

9. The method according to claim 5 further includes: Send an uplink NG user plane interface (NG-U) frame to the CN, including the calculated uplink delay of the data packet (RAN portion) and the associated PDCP PDU SN.

10. The method according to claim 5, wherein: The base station includes centralized units (CU) and distributed units (DU), and The method further includes: The DU sends a PDCP PDU received from the UE via an uplink NR-U data packet to the CU, wherein... The uplink NR-U data packet includes the DU portion of the uplink delay of the PDCP PDU and the associated PDCP PDU SN.

11. The method according to claim 10, further comprising: The DU receives the average latency associated with the Quality of Service (QoS) flow of the PDCP PDU at the UE via a MAC CE frame, or the latency of the PDCP PDU at the UE, and then... The delay at the UE is added by the DU to the DU portion of the uplink delay of the PDCP PDU.

12. The method according to claim 5, wherein: The PDCP PDU includes user data packets, and the method further includes: Based on the received packet delay sampling configuration for uplink, determine whether to select the user packet as the sample packet for uplink delay measurement.

13. The method according to claim 5 further includes: Receive a message from the CN including a packet delay sampling configuration for at least one QoS flow, wherein The packet delay sampling configuration instructs the RAN on how to select packets from the QoS flow as sample packets for each packet-level delay monitoring and / or reporting; and The packet delay sampling configuration is configured for uplink and / or downlink, and includes at least one of the following: Delay thresholds and sampling rules are used to instruct the RAN to report only the packet delay results of selected packets whose measured RAN portion delay exceeds the indicated threshold; The sampling data packet interval is used to instruct the RAN to select a data packet for monitoring and reporting every few data packets; The sampling time period is used to instruct the RAN to select a data packet for monitoring and reporting at regular time intervals; The sampling percentage is used to indicate to the RAN the percentage of all data packets selected for monitoring and reporting; and The start time and end time are used to instruct the RAN to select all data packets within a specified time period between the start time and the end time for monitoring and reporting.

14. A device for wireless communication, comprising: processor; as well as A memory that communicates with the processor, the memory storing a plurality of instructions that can be executed by the processor to cause the device to implement the method according to claim 1 or 5.

15. A non-transitory computer-readable medium comprising a plurality of operable instructions, which, when executed by one or more processors, implement the method according to claim 1 or 5.

Images