Quality of service and quality of experience monitoring

Abstract

Methods, systems, and devices are described for quality of service (QoS) and quality of experience (QoE) monitoring in mobile communications technology. An example method of wireless communication includes receiving, by a second network element, a measurement request message from a first network element; performing one or more measurements based on the measurement request message to generate a measurement report message; and transmitting the measurement report message to the first network element.

Description

TECHNICAL FIELD

[0001] This document generally relates to wireless communication. BACKGROUND

[0002] Wireless communication technology is pushing the world towards an increasingly interconnected and networked society. The rapid growth and technological advancements in wireless communication have led to greater demands for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency, are also important to meet the needs of various communication scenarios. Next generation systems and wireless communication technologies will provide support for an increasing number of users and devices, as well as support for higher data rates, compared to existing wireless networks. SUMMARY

[0003] This document relates to methods, systems, and devices for quality-of-service (QoS) and quality-of-experience (QoE) monitoring in mobile communication technologies, including 5th Generation (5G) and New Radio (NR) communication systems.

[0004] In one example aspect, a method of wireless communication is disclosed. The method includes transmitting, by a first network element, a measurement request message to a second network element, and receiving a measurement report message after the transmitting.

[0005] In another example aspect, a method of wireless communication is disclosed. The method includes receiving, by a second network element, a measurement request message from a first network element; performing one or more measurements based on the measurement request message to generate a measurement report message; and transmitting the measurement report message to the first network element.

[0006] In yet another example aspect, the methods described above are implemented in the form of processor-executable code and stored in a computer-readable program medium.

[0007] In yet another example embodiment, an apparatus configured or operable to perform the methods described above is disclosed.

[0008] The above and other aspects and embodiments are more fully described in the following detailed description, reference being made to the accompanying drawings, in which: BRIEF DESCRIPTION OF DRAWINGS

[0009] Figure 1 Examples of network nodes (e.g., base stations or gNodeBs) and wireless devices (e.g., user equipment (UEs)) in wireless communication are shown.

[0010] Figure 2 An example of a QoE reporting procedure is shown.

[0011] Figures 3A to 3D Examples of time synchronization accuracy monitoring are shown.

[0012] Figures 4A to 4C Examples of delay monitoring are shown.

[0013] Figures 5A to 5E Examples of clock drift monitoring are shown.

[0014] Figures 6A to 6C Examples of burst spread monitoring are shown.

[0015] Figure 7 Examples of PUR and / or IDT resource suitability reporting are shown.

[0016] Figures 8A to 8C Examples of survival time monitoring are shown.

[0017] Figure 9A And Figure 9B Examples of wireless communication methods are shown.

[0018] Figure 10 is a block diagram representation of an apparatus that can be used in the implementation of the methods and techniques described in this document. DETAILED DESCRIPTION

[0019] Network maintenance and parameter configuration optimization is typically costly and time consuming, and impacts network Quality of Service (QoS) and Quality of Experience (QoE) metrics. In turn, network maintenance and parameter configuration optimization relies on QoS and QoE performance. In an example, network optimization and parameter configuration optimization can be performed upon detection of degradation in QoS and QoE performance.

[0020] Embodiments of the disclosed technology are directed to automatic detection of QoS and QoE and subsequent optimization. Existing implementations of such methods include Self-Organizing Network (SON), Minimization of Drive Testing (MDT), and data collection for QoE. In this document, additional methods are described, including 5GS time synchronization accuracy monitoring, Semi-Persistent Scheduling (SPS) / Configured Grant (CG) burst spread monitoring, Predefined Uplink Resource (PUR) suitability, etc.

[0021] Figure 1An example of a wireless communication system (e.g., LTE, 5G, or New Radio (NR) cellular network) is shown that includes a BS 120 and one or more user equipment (UE) 111, 112, and 113. In some embodiments, the downlink transmissions (141, 142, 143) include a measurement request message. In response, the UE transmits (131, 132, 133) a measurement report to the BS 120. The UE can be, for example, a smartphone, a tablet, a mobile computer, a machine-to-machine (M2M) device, a terminal, a mobile device, an Internet of Things (IoT) device, etc.

[0022] Figure 2 An example of a QoE reporting procedure is shown that includes the following steps between a network element 1 (NE1) and a network element 2 (NE2):

[0023] Step 1: NE1 receives a QoE measurement request from NE2;

[0024] Step 2: NE1 performs measurements according to the QoE measurement request; and

[0025] Step 3: NE1 reports the measurement results to NE2.

[0026] In some embodiments, the network element 1 can be a g-NodeB (gNB), a gNB Centralized Unit (CU), a gNB Distributed Unit (DU), a user equipment (UE), or a smart device, and the network element 2 can be a QoC Collection Entity (QCE), a 5G Core (5GC) network, a gNB, a gNB-CU, or a gNB-DU.

[0027] In some embodiments, the measurement request includes one or more of the following:

[0028] 1. Time synchronization accuracy reporting indication

[0029] 2. 5GS (TSN bridge) delay reporting indication

[0030] 3. Clock drift reporting indication

[0031] 4. Burst spread reporting indication

[0032] 5. PUR and / or IDT resource suitability reporting indication

[0033] 6. Survival time reporting indication

[0034] Herein, the reporting indication can also be one of the following: a monitoring indication, a measurement indication, or a measurement configuration.

[0035] In some embodiments, the measurement request can also include a measurement control number (QMC ID) and / or reporting address information (QCE), and the measurement request can come from one of the following entities: a network management system, various application protocols (e.g., NGAP, S1AP, XNAP, X2AP, F1AP, E1AP), Radio Resource Control (RRC), System Information Block (SIB), Medium Access Control (MAC)-Control Element (CE), or Downlink Control Information (DCI).

[0036] This document uses section headings and subheadings to facilitate ease of understanding, and not for the purpose of limiting the scope of the disclosed technologies and embodiments to certain sections. Thus, embodiments disclosed in different sections can be used together. In addition, this document uses examples from 3GPP New Radio (NR) network architecture and 5G protocols to facilitate understanding, and the disclosed technologies and embodiments can be practiced in other wireless systems using communication protocols different from 3GPP protocols.

[0037] Example embodiments of 5GS time synchronization accuracy monitoring

[0038] Figure 3A An example is shown in which the 5GC obtains 5GS time synchronization accuracy. As shown therein, the 5GC sends a 5GS time synchronization accuracy reporting indication to the UE, which can be sent through a Non-Access-Stratum (NAS) Protocol Data Unit (PDU) or NAS message. In response, the UE sends a 5GS time synchronization accuracy report to the UE, which can be sent through a NAS PDU or NAS message.

[0039] In some embodiments and as shown in Figure 3B The 5GS time synchronization accuracy report includes a transmission timestamp of a downlink (DL) transmission (denoted as t1) and a reception timestamp t2. The DL transmission can be a Time Sensitive Networking (TSN) packet with a transmission timestamp, a DL data transmission with a transmission timestamp, or a DL signaling transmission with a transmission timestamp. In an example, for a TSN packet with a transmission timestamp, the timestamp in a gPTP or 802.1 packet can be used as the timestamp.

[0040] Once the 5GC obtains the 5GS time synchronization accuracy report (which includes t1 and t2), it can infer the DL transmission delay (e.g., DL delay = t2 - t1), combine it with the UL transmission delay (which can be obtained based on the UL TSN packet timestamp), and then can determine whether the UE’s clock is accurate (e.g., based on whether the DL transmission delay is equal to the UL transmission delay).

[0041] In some embodiments, the device-side TSN translator (DS-TT) and the UE are combined. In other embodiments, the DS-TT and the UE are separate. In an example, for UL TSN transmissions, the timestamp will typically be added in the TSN packet by the UE-TT.

[0042] In some embodiments, the network-side TSN translator (NW-TT) and the User Plane Function (UPF) are combined. In other embodiments, the NW-TT and the UPF are separate. In an example, for DL TSN transmissions, the timestamp will typically be added in the TSN packet by the UE-TT.

[0043] Figure 3C Another example of time synchronization accuracy monitoring is shown, which is applicable to the following scenarios:

[0044] - between a gNB-CU and a gNB-DU, where the gNB-CU (node 2) obtains the F1 time synchronization accuracy from the gNB-DU (node 1);

[0045] - between a UE and a gNB-DU, where the gNB-DU (node 2) obtains the time synchronization accuracy from the UE (node 1);

[0046] - between a UE and a gNB, where the gNB (node 2) obtains the time synchronization accuracy from the UE (node 1);

[0047] - between a UE and a gNB, where the 5GC (node 2) obtains the time synchronization accuracy from the gNB (node 1); and

[0048] - between gNBs, where the gNB (node 2) obtains the time synchronization accuracy from another gNB (node 1).

[0049] In the foregoing examples, the time synchronization accuracy report indication can be a packet frame, a NAS PDU, or a NAS signaling including a transmission timestamp t1; and the time synchronization accuracy report can be sent through a packet frame, a NAS PDU, or a NAS signaling including a DL transmission (e.g., carrying the time synchronization accuracy report indication) start timestamp t1, a DL transmission (e.g., carrying the time synchronization accuracy report indication) reception timestamp t2, a UL transmission (e.g., the time synchronization accuracy report) start timestamp t3.

[0050] In some embodiments, once node 2 receives the time synchronization accuracy report including t1, t2, and t3, it records a UL transmission (e.g., the time synchronization accuracy report) reception timestamp t4, and provides (t1, t2, t3, t4) to the data collection component. In examples, the data collection component can infer a DL transmission delay (e.g., DL delay = t2 - t1) and a UL transmission delay (e.g., UL delay = t4 - t3) based on the (t1, t2, t3, t4) information. Based on whether the DL transmission delay is equal to the UL transmission delay, the data collection component can determine whether the clock of node 1 is accurate.

[0051] In some embodiments, the data collection component can be in node 2 or in a node 2 Operation and Maintenance Center (OMC).

[0052] In some embodiments, the 5GC sends a 5GS time synchronization accuracy report indication to the UE, and can be sent through a NAS PDU or a NAS message.

[0053] Figure 3D An example is shown for Timing Advance (TA) update procedure monitoring for time synchronization accuracy. As shown therein, a UE records one or more uplink TA values in a Timing Advance Command (TAC) MAC CE sent from a gNB and / or a downlink Te value computed by the UE. Herein, an uplink TA indicates a timing advance between downlink and uplink or a TA value received in a TA command from a gNB, and a downlink Te indicates a DL timing estimate value in duration or a DL timing estimate bias value in duration. The UE then reports the one or more TA values and / or Te value to the gNB. In examples, the one or more TA values and / or Te value can be a list of values.

[0054] Example embodiments of 5GS delay monitoring

[0055] Figure 4AAn example of 5GS (bridge) delay monitoring is shown. As shown herein, the 5GC transmits a delay report indication to the UE (which can be sent over NAS PDU or NAS message) and subsequently receives the 5GS (TSN bridge) delay (which can be sent over NAS PDU or NAS message). This procedure is similar to the procedure shown in Figure 3A , except that the delay is reported in Figure 4A , and the timestamp is reported in Figure 3A .

[0056] As shown in Figure 4B , the downlink (DL) transmission can be a TSN packet with a transmission timestamp, a TSN time domain clock transfer packet, a DL data transmission with a transmission timestamp, or a DL signaling transmission with a transmission timestamp. In an example, for a TSN packet with a transmission timestamp, the timestamp in a gPTP or 802.1 packet can be used as the timestamp.

[0057] Once the UE obtains the DL transmission start timestamp t1 and the DL transmission receive timestamp t2, it can infer the 5GS (TSN bridge) transmission delay (e.g., delay = t2 - t1) and report it to the 5GC.

[0058] In some embodiments, the TSN sync master is located in the network equipment (e.g., UPF side), so only the one-way trip delay (DL delay) needs to be reported.

[0059] In some embodiments, the device-side TSN translator (DS-TT) and the UE are combined. In other embodiments, the DS-TT and the UE are separate. In an example, for UL TSN transmission, the timestamp will typically be added in the TSN packet by the UE-TT.

[0060] In some embodiments, the network-side TSN translator (NW-TT) and the user plane function (UPF) are combined. In other embodiments, the NW-TT and the UPF are separate. In an example, for DL TSN transmission, the timestamp will typically be added in the TSN packet by the UE-TT.

[0061] Figure 4C Another example of 5GS (bridging) delay monitoring is shown. In this example, the TSN sync master is located in the UE side, so the round-trip delay (UL delay plus DL delay) needs to be reported. As shown in Figure 4C , a TSN time domain clock transfer packet is sent from UE1 at timestamp t1 (which is included in the TSN time domain clock transfer packet).

[0062] Once the UE 2 receives the TSN time domain clock transport packet with timestamp t1, the TSN time domain clock transport packet is augmented with a reception timestamp t2, and the UE 2 can infer the 5GS (TSN bridge) transport delay (e.g., delay = t2 - t1) and report it to the 5GC.

[0063] In some embodiments, the device-side TSN translator (DS-TT) and the UE are combined. In other embodiments, the DS-TT and the UE are separate.

[0064] In some embodiments, the network-side TSN translator (NW-TT) and the user plane function (UPF) are combined. In other embodiments, the NW-TT and the UPF are separate.

[0065] In some embodiments, for TSN time domain clock transport, a timestamp will typically be added by the sender in the TSN packet.

[0066] Example embodiments of UE clock drift monitoring

[0067] Figure 5A An example procedure to trigger UE clock drift monitoring is shown. As shown therein, the gNB sends a UE clock drift reporting indication to the UE, which can be sent through a system information block (SIB), a DL UE-specific RRC message, a MAC CE, or a DCI. Upon receiving the UE clock drift reporting indication, the UE performs UE clock monitoring (as shown in Figure 5B and Figure 5C ). After obtaining the clock drift monitoring results, the UE reports it to the gNB, which can be sent through a UL UE-specific RRC message or a MAC CE.

[0068] Figure 5B Another example procedure to trigger UE clock drift monitoring is shown. As shown therein, the gNB periodically sends a referenceTimeinfo with PDC (Propagation Delay Compensation) to the UE. Upon receiving at least two referenceTimeinfo with PDC, the UE calculates the clock drift of the UE with the time interval between the two referenceTimeinfo. In an example, the UE corrects its time clock based on the first referenceTimeinfo. Then, upon receiving the second referenceTimeinfo, it can calculate the time difference between the UE’s clock and the current time indicated in the second referenceTimeinfo, thereby determining the clock drift of the UE.

[0069] In some embodiments, more than two referenceTimeinfo with PDC can be received, in which case the UE can report clock drift for every two adjacent referenceTimeinfo. In other embodiments, the UE can report only one of average clock drift, maximum clock drift, minimum clock drift, or clock drift value per two referenceTimeinfo.

[0070] In Figure 5C , the gNB sends referenceTimeinfo to the UE with or without PDC (propagation delay compensation). Upon receiving at least two referenceTimeinfo, the UE periodically corrects the time clock based on system frame number (SFN) and timing advance (TA) information. In an example, if the time of SFN boundary in the first occasion for correcting the clock is X, and the clock correction period is Y SFN, then the time of SFN boundary in the second occasion for correcting the clock is X + 10*Y (ms) + N_TA**T_c / 2, where 10*Y (ms) is the time difference between the two occasions for correcting the clock, and N_TA**T_c / 2 is the PDC or DL transmission delay. Herein, the amount of time clock correction is the time clock drift.

[0071] In some embodiments, and similar to the scenario described in Figure 5B , if more than one clock drift value is obtained, the UE can report only one of a list of clock drift, average clock drift, maximum clock drift, minimum clock drift, or clock drift value per two adjacent referenceTimeinfo.

[0072] Figure 5D Another example of UE clock drift level reporting based on gNB request is shown. As shown therein, the gNB sends a UE clock drift reporting indication to the UE, which can be sent through SIB, DL UE-specific RRC message, MAC CE, or DCI. If the UE chooses DL UE-specific RRC message, MAC CE, or DCI to send the UE clock drift reporting indication, the UE must first send at least one of the following indications to the gNB: UE clock drift reporting capability, TSC service support indication, referenceTimeinfo reception capability, referenceTimeInfoPreference, or accurate clock synchronization requirement related indication. Finally, the UE sends a UE clock drift report to the gNB, which includes a clock drift level, which can be sent through UL UE-specific RRC message or MAC CE.

[0073] Figure 5EAn example of UE clock drift level reporting according to UE capability is shown, where the UE includes the UE clock drift level in the UECapabilitylnformation message, which can be used by the eNB if necessary. In the example, Figure 3D The UE clock drift level in FIG. 3E can be one of the pre-defined values shown in Table 1 or Table 2 (which correspond to clock stratum level or clock accuracy enumeration, respectively).

[0074] Table 1: Example of clock stratum level

[0075]

[0076]

[0077] Table 2: Example of clock accuracy defined in IEEE Standard 1588

[0078]

[0079]

[0080] In some embodiments, UE clock drift level defined by 3GPP can also be used, e.g., the maximum amount or degree of UE clock drift per predefined time period (e.g., 1 ms or 1 s).

[0081] Example embodiments of burst expansion monitoring

[0082] In a TSN network, the 5GC can provide TSC Assistance Information (TSCAI) including burst arrival time and periodicity to the gNB. The gNB will configure Configured Grant (CG) and / or Semi-Persistent Scheduling (SPS) resources based on the TSCAI information. However, data packets can not always arrive at the burst arrival time, e.g., they can arrive before or after the burst arrival time. This variation in arrival time is referred to as burst expansion (and also referred to as burst arrival time variation range).

[0083] When packets arrive after the burst arrival time, the packets can not fit for transmission over the CG or SPS resources. Therefore, for parameter optimization, the burst expansion should be identified by the 5GC (e.g., AMF) providing the TSCAI or the gNB providing the SPS and / or CG configuration.

[0084] Figure 6AAn example of burst expansion monitoring is shown. As shown therein, the 5GC sends a burst expansion reporting indication to the UE, which can be sent through a NAS PDU or NAS message. The 5GC sends a TSCAI to the gNB, and the gNB configures CG resources for the UE. The UE records burst expansion information. In examples, the recorded burst expansion information can include one or more of a per-packet burst expansion record list, a burst expansion range, a maximum burst expansion value before the burst arrival value, a minimum burst expansion before the burst arrival value (e.g., a negative value to indicate the maximum burst expansion value before the burst arrival value), or a maximum burst expansion value after the burst arrival value. Finally, the UE reports the burst expansion record to the 5GC, which can be sent through a NAS PDU or NAS message.

[0085] Figure 6B Another example of burst expansion monitoring is shown. As shown therein, the gNB sends a burst expansion reporting indication to the UE, which can be sent through a SIB, a DL UE-specific RRC message, a MAC CE, or a DCI. The gNB then configures CG resources for the UE. The UE records burst expansion information. In examples, the recorded burst expansion information can include one or more of a per-packet burst expansion record list, a burst expansion range, a maximum burst expansion value before the burst arrival value, a minimum burst expansion before the burst arrival value (e.g., a negative value to indicate the maximum burst expansion value before the burst arrival value), or a maximum burst expansion value after the burst arrival value. Finally, the UE reports the burst expansion record to the gNB, which can be sent through a UL UE-specific RRC message or a MAC CE.

[0086] Figure 6C Another example of burst expansion monitoring is shown, in which the 5GC obtains burst expansion from the gNB. As shown therein, the 5GC sends a TSCAI to the gNB, which includes a DL TSCAI (e.g., a TSC Assistance Information Downlink Information Element (IE)). The 5GC then sends a burst expansion reporting indication to the gNB, which can be sent through NGAP signaling or a user data PDU. In some embodiments, the TSCAI and the burst expansion reporting indication can be sent simultaneously. In other embodiments, and as shown therein, the TSCAI and the burst expansion reporting indication can be sent separately. Figure 6CAs shown, they can be sent in two different operations (e.g., no runtime order is required). The gNB records the burst spreading information. In an example, the recorded burst spreading information can include one or more of a per-packet burst spreading record list, a burst spreading range, a maximum burst spreading value before the burst arrival value, a minimum burst spreading before the burst arrival value (e.g., a negative value to indicate the maximum burst spreading value before the burst arrival value), or a maximum burst spreading value after the burst arrival value. Finally, the gNB reports the burst spreading record to the 5GC, which can be sent through NGAP signaling or user data PDU.

[0087] Example embodiments of PUR and / or IDT resource suitability reporting

[0088] Preconfigured Uplink Resource (PUR) is introduced in NB-IoT / eMTC for UE transmission in IDLE state (e.g., eNB configures PUR resource in RRCConnectionRelease message, and the UE in IDLE state can transmit PUSCH through the configured PUR resource). PUR and / or RRC_INACTIVE Data Transmission (IDT) in NR is for UE transmission in RRC_INACTIVE state. In this case, UL resource will be pre-configured, and the UE can perform transmission through the pre-configured UL resource. If the pre-configured resource is not suitable (e.g., time domain does not match the data, data size does not match TBS, etc.), PUR and / or IDT resource cannot be used. In addition, if PUR or IDT transmission fails, the PUR and / or IDT resource will be wasted. To make more efficient use of resources, the eNB / gNB should be informed of this information for PUR and / or IDT resource configuration optimization.

[0089] Figure 7 Examples of PUR and / or IDT resource suitability reporting are shown. As shown therein, the gNB (or eNB) sends PUR and / or IDT resource (re)configuration in RRCConnectionRelease message, and then sends a PUR and / or IDT resource suitability reporting indication, which can be sent through SIB, DL UE-specific RRC message, MAC CE, or DCI. In an example, the DL UE-specific RRC message can be RRCConnectionRelease message or UE Information Request (e.g., UE Information Request) message. In some embodiments, the two operations can be performed simultaneously. In other embodiments, the two operations can be performed separately without requiring runtime order.

[0090] In some embodiments, when the PUR and / or IDT resource suitability reporting indication is sent in a DL UE-specific RRC message, MAC CE, or DCI, the eNB sends a PUR and / or IDT resource suitability reporting record available indication before the request. The available indication can be sent in an UL RRC message, EDT message 3, RRC message 5, or MAC CE during the PUR and / or IDT transmission procedure.

[0091] In some embodiments, the UE records the PUR and / or IDT resource suitability related information and then reports the PUR and / or IDT resource suitability related information in a subsequent UL transmission, which can be sent through an UL UE-specific RRC message or MAC CE. In an example, the UL UE-specific RRC message can be an UL RRC message, EDT message 3, RRC message 5, or UE Information Response (e.g., UEInformationResponse) message during the PUR and / or IDT transmission procedure. In another example, the PUR and / or IDT resource suitability related information includes burst extension information, burst TBS information, TA invalidation indication, no data transmission, fallback for large TBS, fallback for TA invalidation, PUR and / or IDT configuration identification, etc., which are defined as:

[0092] - burst extension indicates the time variation of the burst arrival before or after the configured PUR and / or IDT resource. The burst extension information can include one or more of a per-packet burst extension record list, a burst extension range, a maximum burst extension value before the burst arrival value, a minimum burst extension before the burst arrival value (e.g., a negative value is used to indicate the maximum burst extension value before the burst arrival value), or a maximum burst extension value after the burst arrival value.

[0093] - burst TBS represents the TBS of the real burst. The burst TBS information includes one or more of a per-packet burst TBS record list, a burst TBS range, a maximum burst TBS value, and a minimum burst TBS value.

[0094] - TA invalidation indication indicates that the TA is invalid at the PUR and / or IDT resource time occasion. In an example, the TA invalidation indication can be a single indication, a time stamp of the PUR and / or IDT resource time occasion when the TA is invalid, or a list of time stamps of the PUR and / or IDT resource time occasion when the TA is invalid.

[0095] - No data transmission indication that there is no data to transmit at the PUR and / or IDT resource time occasion. In an example, it can be an indication, a time stamp of the PUR and / or IDT resource time occasion when there is no data to transmit, or a list of time stamps of the PUR and / or IDT resource time occasion when there is no data to transmit.

[0096] - Back-off indication for large TBS that the PUR and / or IDT transmission falls back to non-PUR and / or IDT procedure when the TBS is too large to be transmitted on the configured PUR and / or IDT resource. In an example, this can be configured as an indication.

[0097] - Back-off indication for TA invalid that the PUR and / or IDT transmission falls back to non-PUR and / or IDT procedure when the TA is invalid at the PUR and / or IDT resource time occasion. In an example, this can be configured as an indication.

[0098] - PUR and / or IDT configuration identification to identify the PUR and / or IDT configuration in the eNB / gNB when sending / receiving PUR and / or IDT resource (re)configuration and / or PUR and / or IDT resource applicability related information.

[0099] Example embodiments of survival time monitoring

[0100] Survival time is defined as the time an application consuming a communication service can continue without an expected message. The maximum survival time indicates the time period in which the communication service can not meet the application’s requirements before the communication service is considered in an unavailable state. The survival time can be expressed as a time period or a maximum number of consecutively wrongly received or missing messages, especially in the case of cyclic traffic.

[0101] In some embodiments, the survival time or whether the degree of applicability is fulfilled can be monitored in the gNB or the UE. The survival time monitoring can be triggered by the 5GS to evaluate the 5GS performance or by the gNB to evaluate the gNB scheduling performance.

[0102] Figure 8AAn example is shown in which the 5GS obtains the survival time monitoring information from the UE. As shown therein, the 5GS sends a survival time threshold configuration to the UE, which can be sent through a NAS PDU or a NAS message. The 5GS then sends a survival time reporting indication to the UE, which can be sent through a NAS PDU or a NAS message. In some embodiments, these two operations can be performed simultaneously (e.g., sent in one NAS PDU or one NAS message). In other embodiments, these two operations can be performed separately without requiring a runtime order. The UE performs measurements and records survival time related statistics, and then sends a survival time monitoring report containing the survival time related statistics results to the 5GC, which can be sent through a NAS PDU or a NAS message.

[0103] Figure 8B An example is shown in which the gNB obtains the survival time monitoring information from the UE. As shown therein, three operations are performed:

[0104] - the 5GS sends a survival time threshold configuration to the UE, which can be sent through a NAS PDU or a NAS message.

[0105] - the 5GS sends a survival time threshold configuration to the gNB, which can be sent through NGAP signaling.

[0106] - the gNB sends a survival time reporting indication to the UE, which can be sent through a SIB, a DL UE-specific RRC message, a MAC CE, or a DCI.

[0107] In some embodiments, these three operations can be performed simultaneously. In other embodiments, these three operations can be performed separately with requiring a runtime order. The UE then performs measurements and collects survival time related statistics, and then sends a survival time monitoring report to the gNB, which includes the survival time related statistics results, which can be sent through a UL UE-specific RRC message, a MAC CE, or a DCI.

[0108] Figure 8C An example is shown in which the 5GC obtains the survival time monitoring information from the gNB. As shown therein, two operations are performed:

[0109] - the 5GS sends a survival time threshold configuration to the gNB, which can be sent through NGAP signaling.

[0110] - the 5GS sends a survival time reporting indication to the gNB, which can be sent through NGAP signaling.

[0111] In some embodiments, the two operations can be performed simultaneously (e.g., sent in one NGAP signaling). In other embodiments, the two operations can be performed separately without requiring a runtime order. The gNB then performs the measurements and collects the survival time related statistics, and then sends a survival time monitoring report to the 5GC, which includes the survival time related statistics results, which can be sent through NGAP signaling.

[0112] In some embodiments, and for Figure 8A , Figure 8B and Figure 8C The survival time related statistics and the survival time monitoring report include at least one of: a perception of survival time not being met, a number of packets not meeting the survival time. Herein, the survival time not being met corresponds to a number of consecutively incorrectly received packets reaching a certain threshold, or a duration of consecutively incorrectly received packets reaching a time period threshold.

[0113] Example methods and implementations of the disclosed technology

[0114] Figure 9A An example of a method 900 of wireless communication is shown. The method 900 includes, at operation 902, transmitting, by a first network element to a second network element, a measurement request message.

[0115] The method 900 includes, at operation 904, receiving, after the transmitting, a measurement report message.

[0116] Figure 9B An example of a method 950 of wireless communication is shown. The method 950 includes, at operation 952, receiving, by a second network element from a first network element, a measurement request message.

[0117] The method 950 includes, at operation 954, performing one or more measurements to generate a measurement report message based on the measurement request message.

[0118] The method 950 includes, at operation 956, transmitting, to the first network element, the measurement report message.

[0119] In some embodiments, the first network element is a quality of experience collection entity (QCE), a 5G core (5GC) network, an eNodeB (eNB), a gNodeB (gNB), or a gNB centralized unit (CU), and wherein the second network element is a user equipment (UE), a gNB, a gNB distributed unit (DU), or a smart device.

[0120] In some embodiments, the first network element is a 5GC network, and the second network element is a gNB or a UE, the measurement request message is a non-access stratum (NAS) protocol data unit (PDU) or a NAS message, and the measurement report message is a NAS PDU or a NAS message.

[0121] In some embodiments, the first network element is a gNB-CU and the second network element is a gNB-DU, wherein the measurement request message is an Fl application protocol (FlAP) or FlAP protocol data unit (PDU), and the measurement report message is an FlAP or FlAP PDU.

[0122] In some embodiments, the first network element is an eNB and the second network element is a UE, the measurement request message is a radio resource control (RRC) message, a medium access control (MAC) control element (CE), or a radio frame, and the measurement report message is an RRC message, a MAC CE, or a RF.

[0123] In some embodiments, the measurement request message includes a 5G system synchronization accuracy reporting indication, and the measurement report message includes a 5G system synchronization accuracy report.

[0124] In some embodiments, the measurement report message further includes a first timestamp corresponding to a downlink transmission by the first network element and a second timestamp corresponding to a reception of the downlink transmission by the second network element.

[0125] In some embodiments, the downlink transmission includes the measurement request message or a downlink packet.

[0126] In some embodiments, the measurement report message further includes a first timestamp corresponding to a downlink transmission by the first network element, a second timestamp corresponding to a reception of the downlink transmission by the second network element, and a third timestamp corresponding to a transmission of the measurement report message by the second network element.

[0127] In some embodiments, the measurement request message includes an uplink timing advance (TA) value reporting indication and / or a downlink Te value reporting indication, and the measurement report message includes an uplink TA value and / or a downlink Te value.

[0128] In some embodiments, the measurement request message includes a 5G system downlink delay reporting indication, and the measurement report message includes a 5G system downlink delay report.

[0129] In some embodiments, the measurement request message is a time sensitive networking (TSN) packet, and further includes a first timestamp corresponding to a transmission of the measurement request message, and the measurement report message further includes a delay that is a difference between the first timestamp corresponding to the transmission of the measurement request message by the first network element and a second timestamp corresponding to a reception of the measurement request message by the second network element.

[0130] In some embodiments, the measurement request message includes a clock drift reporting indication, and the measurement report message includes a clock drift report.

[0131] In some embodiments, the first network element is configured to transmit two or more reference time information messages including a propagation delay compensation (PDC) parameter, and the second network element is configured to determine the clock drift based on the local clock and an adjacent one of the two or more reference time information messages.

[0132] In some embodiments, the clock drift report includes the clock drift, a maximum value of the clock drift, a minimum value of the clock drift, or an average value of the clock drift.

[0133] In some embodiments, the first network element is configured to transmit a reference time information message, the second network element is configured to determine the clock drift based on a predefined duration and the reference time information message, and the clock drift report includes the clock drift.

[0134] In some embodiments, the predefined duration is based on a time of a system frame number (SFN) boundary.

[0135] In some embodiments, the measurement report message further includes a clock drift level, and wherein the clock drift level corresponds to one of a plurality of clock stratum levels.

[0136] In some embodiments, the measurement report message further includes an indicator corresponding to a clock accuracy.

[0137] In some embodiments, the measurement request message is a system information block (SIB), a downlink UE-specific radio resource control (RRC) message, a medium access control (MAC) control element (CE), or a downlink control information (DCI), and the measurement report message is an uplink UE-specific RRC message or a MAC CE.

[0138] In some embodiments, the measurement request message includes a burst spread report indication, and the measurement report message includes a burst spread report.

[0139] In some embodiments, the burst spread report includes one or more of a list of burst spread records per packet, a burst spread range, a maximum burst spread value before a burst arrival value, a minimum burst spread value before a burst arrival value, a maximum burst spread value after a burst arrival value, and a minimum burst spread value after a burst arrival value.

[0140] In some embodiments, the measurement request message is a non-access stratum (NAS) protocol data unit (PDU) or a NAS message, and the measurement report message is a NAS PDU or a NAS message.

[0141] In some embodiments, the measurement request message is a system information block (SIB), a downlink UE-specific radio resource control (RRC) message, a medium access control (MAC) control element (CE), or a downlink control information (DCI), and the measurement report message is an uplink UE-specific RRC message or a MAC CE.

[0142] In some embodiments, the measurement request message is a next generation application protocol (NGAP) message or a user data protocol data unit (PDU), and the measurement report message is an NGAP message or a user data PDU.

[0143] In some embodiments, the measurement request message includes a preconfigured uplink resource (PUR) or RRC_INACTIVE data transmission (IDT) resource suitability reporting indication.

[0144] In some embodiments, the measurement report message includes a PUR or IDT resource suitability information report including at least one of a PUR or IDT burst extension, a burst transport block size (TBS), a timing advance (TA) invalidation indication, an indication of no data transmission on a PUR or IDT resource, an indication of fallback for a large TBS, an indication of fallback for TA invalidation, and a PUR or IDT configuration identification.

[0145] In some embodiments, the first network element is an eNodeB (eNB) or a gNodeB (gNB), and wherein the second network element is a user equipment (UE).

[0146] In some embodiments, the method 900 further includes an operation of transmitting, by the first network element, a measurement threshold configuration message to the second network element.

[0147] In some embodiments, the method 950 further includes an operation of receiving, by the second network element, a measurement threshold configuration message from the first network element.

[0148] In some embodiments, the measurement request message includes a time-to-live reporting indication, and the measurement report message includes a time-to-live monitoring report.

[0149] In some embodiments, the time-to-live monitoring report includes one or more of a perception of not meeting a time-to-live, a number of packets not meeting the time-to-live for a duration, a number of events not meeting the time-to-live for a duration, a number of consecutively incorrectly received packets for a duration, and wherein the time-to-live corresponds to a number of consecutively incorrectly received packets exceeding a first threshold or a duration of consecutively incorrectly received packets exceeding a second threshold.

[0150] In some embodiments, the measurement request message includes a time sensitive networking (TSN) quality of experience (QoE) related reporting indication, and wherein the measurement report includes any available TSN QoE related information including at least one of a 5G system synchronization accuracy report, a 5G system downlink delay report, a clock drift report, a burst spread report, a PUR or IDT resource suitability report, and a survival time monitoring report.

[0151] In some embodiments, the measurement request message is a non-access stratum (NAS) protocol data unit (PDU) or NAS message, and wherein the measurement report message is a NAS PDU or NAS message.

[0152] In some embodiments, the measurement request message is a system information block (SIB), a downlink UE-specific radio resource control (RRC) message, a medium access control (MAC) control element (CE), or a downlink control information (DCI), and wherein the measurement report message is an uplink UE-specific RRC message or a MAC CE.

[0153] In some embodiments, the measurement threshold configuration message is a non-access stratum (NAS) protocol data unit (PDU) or NAS message.

[0154] Figure 10 is a block diagram representation of a portion of an apparatus in accordance with some embodiments of the presently disclosed technology. An apparatus 1005, such as a base station or a wireless device (or UE), can include processor electronics 1010, such as a microprocessor that implements one or more of the techniques presented in this document. The apparatus 1005 can include transceiver electronics 1015 to transmit and / or receive wireless signals through one or more communication interfaces, such as antenna(s) 1020. The apparatus 1005 can include other communication interfaces for transmitting and receiving data. The apparatus 1005 can include one or more memories (not explicitly shown) configured to store information, such as data and / or instructions. In some implementations, the processor electronics 1010 can include at least a portion of the transceiver electronics 1015. In some embodiments, the disclosed technology, modules, or functions, at least some of which are implemented using the apparatus 1005.

[0155] Some of the embodiments described herein are described in the general context of methods or processes, which can be implemented in one embodiment by a computer program product, executable program routines, and / or program modules, including computer program instructions stored on a computer-readable medium, such as a memory, physical and / or virtual network devices, and / or storage devices, which are accessed by a computer and / or a processing unit(s) of a computer. The computer-readable medium can include non-transitory storage media that is readable by a computer and / or computing device and / or machine. The computer-readable medium can include a non-transitory memory, mechanism that stores data, including propagated signals and carrier waves, which are not transient and Durably stored. The computer-readable medium can include, but is not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disks (DVD), BLU-RAY discs or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, solid-state drives (SSDs), or any other medium that can be used to store information for access by a computer. In some embodiments, the computer-readable medium can include a combination of one or more of the above. Accordingly, in some embodiments, the computer program product can include a computer program product embodied in a computer-readable medium.

[0156] Some of the disclosed embodiments can be implemented as a device or module that uses hardware circuitry, software, or a combination thereof. For example, a hardware circuit implementation can include discrete analog and / or digital components, for example, integrated as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules can be implemented as an Application Specific Integrated Circuit (ASIC) and / or a Field Programmable Gate Array (FPGA) device. Some embodiments can additionally or alternatively include a digital signal processor (DSP), which is a specialized microprocessor optimized for the operation requirements of digital signal processing associated with the functionality disclosed in this application. Similarly, the various components or subcomponents within each module can be implemented in software, hardware, or firmware. Connections between the modules and / or components within the modules can be provided using any of the connection methods and media known in the art, including but not limited to communication over the Internet, wired or wireless networks using appropriate protocols.

[0157] Although this document contains many specifics, these should not be construed as limiting the scope of the invention or of what can be claimed but as merely providing illustrations of some of the embodiments of the invention. Some features described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in isolation that in multiple embodiments. Also, although the features can be described and illustrated with respect to particular combinations only, many of these features have general applications that can be used in conjunction with other present or future technologies. Thus, the features are not limited to any specific combination or permutation. It should also be noted that the features can be implemented individually or in any combination, and are not limited to the embodiments specifically recited herein. Also, although the features can be described and illustrated with respect to particular sequences or order of operations, this should not be construed as a requirement, but rather examples of an order in which the operations were executed. The operations can be executed in other sequences or orders.

[0158] Only a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in this disclosure.

Claims

1. A method of wireless communication, comprising: transmitting, by a first network element, a measurement request message to a second network element; and receiving, after the transmitting, a measurement report message, wherein the measurement request message includes a time sensitive networking (TSN) quality of experience (QoE) related reporting indication, wherein the measurement report message includes available TSN QoE related information including at least one of a 5G system synchronization accuracy report, a 5G system downlink delay report, a clock drift report, a burst spread report, a preconfigured uplink resource (PUR) or inactivity data transmission (IDT) resource suitability report, and a time to live monitoring report, wherein the first network element is a 5GC network element and the second network element is a gNB or a user equipment (UE), wherein the measurement request message is a non-access stratum (NAS) protocol data unit (PDU) or a NAS message, and the measurement request message includes a 5G system synchronization accuracy report indication, wherein the measurement report message is a NAS PDU or a NAS message, and the measurement report message includes a 5G system synchronization accuracy report, a first timestamp corresponding to a downlink transmission by the first network element, and a second timestamp corresponding to a reception of the downlink transmission by the second network element. 2.The method of claim 1, wherein the downlink transmission includes the measurement request message or a downlink packet. 3.The method of claim 1, wherein the measurement report message further includes a first timestamp corresponding to the downlink transmission by the first network element, a second timestamp corresponding to a reception of the downlink transmission by the second network element, and a third timestamp corresponding to a transmission of the measurement report message by the second network element. 4.The method of claim 1, wherein the measurement request message includes a 5G system downlink delay report indication, and the measurement report message includes a 5G system downlink delay report. 5.The method of claim 4, wherein the measurement request message is a time sensitive networking (TSN) packet, and further includes a first timestamp corresponding to a transmission of the measurement request message, and wherein the measurement report message further includes a delay that is a difference between the first timestamp corresponding to the transmission of the measurement request message by the first network element and a second timestamp corresponding to a reception of the measurement request message by the second network element. 6.The method of claim 1, wherein the measurement request message includes a burst spread report indication, and the measurement report message includes a burst spread report. 7.The method of claim 6, wherein the burst spread report includes one or more of a per-packet burst spread record list, a burst spread range, a maximum burst spread value before a burst arrival value, a minimum burst spread value before a burst arrival value, a maximum burst spread value after a burst arrival value, and a minimum burst spread value after a burst arrival value. ​ 8. The method of claim 1, further comprising: transmitting, by the first network element to the second network element, a measurement threshold configuration message.

9. The method of claim 8, wherein the measurement request message includes a time-to-live reporting indication and the measurement report message includes a time-to-live monitoring report.

10. The method of claim 9, wherein the time-to-live monitoring report includes one or more of a perception of not meeting a time-to-live, a number of packets not meeting the time-to-live for a duration of time, a number of events not meeting the time-to-live for a duration of time, a number of consecutively incorrectly received packets for a duration of time, and wherein the time-to-live corresponds to a number of consecutively incorrectly received packets exceeding a first threshold or a duration of time of consecutively incorrectly received packets exceeding a second threshold.

11. The method of any one of claims 8 to 10, wherein the measurement threshold configuration message is a non-access stratum (NAS) protocol data unit (PDU) or NAS message.

12. A method of wireless communication, comprising: receiving, by a second network element from a first network element, a measurement request message; performing, based on the measurement request message, one or more measurements to generate a measurement report message; and transmitting, to the first network element, the measurement report message, wherein the measurement request message includes a time sensitive networking (TSN) quality of experience (QoE) related reporting indication, wherein the measurement report message includes available TSN QoE related information including at least one of a 5G system synchronization accuracy report, a 5G system downlink delay report, a clock drift report, a burst expansion report, a preconfigured uplink resource (PUR) or inactivity data transfer (IDT) resource suitability report, and a time-to-live monitoring report, wherein the first network element is a 5GC network element and the second network element is a gNB or a user equipment (UE), wherein the measurement request message is a non-access stratum (NAS) protocol data unit (PDU) or NAS message and the measurement request message includes a 5G system synchronization accuracy report indication, wherein the measurement report message is a NAS PDU or NAS message and the measurement report message includes a 5G system synchronization accuracy report, a first timestamp corresponding to a downlink transmission by the first network element, and a second timestamp corresponding to a reception of the downlink transmission by the second network element.

13. The method of claim 12, wherein the downlink transmission includes the measurement request message or a downlink packet.

14. The method of claim 12, wherein the measurement report message further includes the first timestamp corresponding to the downlink transmission by the first network element, the second timestamp corresponding to the reception of the downlink transmission by the second network element, and a third timestamp corresponding to a transmission of the measurement report message by the second network element. ​ 15. The method of claim 12, wherein the measurement request message includes a 5G system downlink delay reporting indication and the measurement report message includes a 5G system downlink delay report.

16. The method of claim 15, wherein the measurement request message is a time sensitive networking (TSN) packet and further includes a first timestamp corresponding to transmission of the measurement request message, and wherein the measurement report message further includes a delay that is a difference between the first timestamp corresponding to transmission of the measurement request message by the first network element and a second timestamp corresponding to reception of the measurement request message by the second network element.

17. The method of claim 12, wherein the measurement request message includes a burst expansion reporting indication and the measurement report message includes a burst expansion report.

18. The method of claim 17, wherein the burst expansion report includes one or more of a list of burst expansion records per packet, a burst expansion range, a maximum burst expansion value before a burst arrival value, a minimum burst expansion value before a burst arrival value, a maximum burst expansion value after a burst arrival value, and a minimum burst expansion value after a burst arrival value.

19. The method of claim 12, further comprising: receiving, by the second network element, a measurement threshold configuration message from the first network element.

20. The method of claim 19, wherein the measurement request message includes a time-to-live reporting indication and the measurement report message includes a time-to-live monitoring report.

21. The method of claim 20, wherein the time-to-live monitoring report includes one or more of a perception of a time-to-live not being met, a number of packets not meeting the time-to-live for a duration of time, a number of events not meeting the time-to-live for a duration of time, a number of consecutively incorrectly received packets for a duration of time, and wherein the time-to-live corresponds to a number of consecutively incorrectly received packets exceeding a first threshold or a duration of consecutively incorrectly received packets exceeding a second threshold.

22. The method of any one of claims 19 to 21, wherein the measurement threshold configuration message is a non-access stratum (NAS) protocol data unit (PDU) or a NAS message.

23. A wireless communication device comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement a method according to any one of claims 1 to 22.

24. A computer program product comprising a computer readable program medium code stored thereon, which code, when executed by a processor, causes the processor to implement a method according to any one of claims 1 to 22.

Images