Data collection and performance enhancement for communication networks

Abstract

Techniques for improving performance of wireless networks and / or devices in wireless networks are described. For example, a method of wireless communication includes receiving, by a communication node, one or more delay values at a first time, where each delay value indicates an amount of time to delay a measurement, and performing the measurement at or after a third time, where the third time is based on a delay value from the one or more delay values, and a second time when the communication node enters an idle state or an inactive state, where the first time precedes the second time in time, and where the second time precedes the third time in time.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to digital wireless communications. BACKGROUND

[0002] Mobile communication technology is pushing the world towards an increasingly interconnected and networked society. Next generation systems and wireless communication technology will need to support a wider range of use case features and provide more complex and precise access requirements and flexibility compared to existing wireless networks.

[0003] Long Term Evolution (LTE) is a wireless communication standard for mobile devices and data terminals developed by the Third Generation Partnership Project (3GPP). LTE-Advanced (LTE-A) is a wireless communication standard that enhances the LTE standard. The fifth generation of wireless systems, 5G, advances the LTE and LTE-A wireless standards and is committed to supporting higher data rates, massive connectivity, ultra-low latency, high reliability, and other emerging business needs. SUMMARY

[0004] Techniques for data collection and / or performance enhancement for wireless networks are disclosed. Wireless network configuration can be optimized by analyzing relevant data reported by user equipment (UE) or base stations (RAN nodes) to enhance performance of the wireless network.

[0005] A first wireless communication method includes receiving, by a communication node, one or more delay values at a first time, where each delay value indicates an amount of time to delay a measurement, and performing the measurement at or after a third time, where the third time is based on a delay value from the one or more delay values and a second time when the communication node enters an idle state or an inactive state, where the first time precedes the second time in time, and where the second time precedes the third time in time.

[0006] In some embodiments, the one or more delay values include a first delay value associated with the idle state and a second delay value associated with the inactive state. In some embodiments, the one or more delay values include a first delay value based on an amount of time the communication node spends in the idle state or in a connected state, and the one or more delay values include a second delay value based on a second amount of time the communication node spends in the inactive state or in the connected state.

[0007] In some embodiments, the first wireless communication method further includes transmitting, to a network node, a delay value and / or a second time value indicating an amount of time to perform the measurement, where the delay value or the second time value is transmitted after the communication node enters the connected state or an active state, and where the delay value and / or the second time value is sent in response to a result of the measurement being invalid.

[0008] A second wireless communication method includes transmitting, to a network node, a report in response to an occurrence of a secondary cell group (SCG) failure, where the report includes an indication of the SCG failure and a status of a primary SCG cell (PSCell) at the time of the failure. In some embodiments, the status of the PSCell indicates whether the PSCell was operating on a dormant bandwidth part (BWP). In some embodiments, the network node comprises a master node (MN).

[0009] A third wireless communication method includes receiving, by a first network node, a report from a communication node, where the report is received in response to an occurrence of a secondary cell group (SCG) failure, and where the report includes an indication of the SCG failure and a status of a primary SCG cell (PSCell) at the time of the failure, and transmitting the report to a second network node.

[0010] In some embodiments, the status of the PSCell indicates whether the PSCell was operating on a dormant bandwidth part (BWP). In some embodiments, the first network node comprises a master node (MN), and where the second network node comprises a secondary node (SN).

[0011] A fourth wireless communication method includes transmitting, to a first network node, mobility enhancement related information in response to an occurrence of a mobility failure when transitioning from a second network node to a third network node, where the mobility enhancement related information includes: dual active protocol stack (DAPS) related information, conditional secondary cell group primary cell addition or change (CPAC) failure information, conditional handover (CHO) failure cause information, or successful handover related information.

[0012] In some embodiments, the DAPS related information includes a packet data convergence protocol (PDCP) type and / or an indication of whether a maximum number of converged carriers was reached. In some embodiments, the CHO failure cause information includes an integrity protection failure or an invalid abstract syntax notation (ASN.1). In some embodiments, the successful handover related information includes a handover type and / or two-step random access channel (RACH) related information. In some embodiments, the CPAC failure indication indicates whether a conditional secondary cell group primary cell (PSCell) change was triggered by a master node or a secondary node.

[0013] A fifth wireless communication method includes transmitting, by a network node to a network, usage related information of user equipment (UE) assistance information received from a UE, where the usage related information indicates whether the UE assistance information and / or a metric associated with the UE assistance information was received or used by the network node, where the UE assistance information includes one or more parameters and one or more corresponding values for each parameter collected by the UE for network performance enhancement, and where the usage related information includes: an indication of whether the UE assistance information has been received by the network node, an indication of whether the UE assistance information has been used by the network node, a result of the network node using the UE assistance information, a number of records of UE assistance information received by the network node, a number of records of UE assistance information used by the network node, a list of types of UE assistance information received by the network node, a list of types of UE assistance information used by the network node, a number of records of UE assistance information received by the network node per type of UE assistance information, a number of records of UE assistance information used by the network node per type of UE assistance information, a result of the network node using UE assistance information per type of UE assistance information, a number of user equipments from which the network node has received UE assistance information, a number of user equipments from which the network node has received and used UE assistance information, a number of user equipments from which the network node has received UE assistance information per type of UE assistance information, or a number of user equipments from which the network node has received and used UE assistance information per type of UE assistance information.

[0014] In some embodiments, the network includes a core network, a trace collection entity (TCE), or an operations, administration, and maintenance (OAM).

[0015] A sixth wireless communication method includes transmitting, by a network node to a network, a demand or a prediction of a quality of service (QoS) flow sent by a communication node, and receiving, from the network after the transmitting, a QoS parameter for the QoS flow, where the QoS parameter includes: an indicator that the QoS demand of the QoS flow has changed over time, or a list of one or more QoS parameters to be used by the communication node for the QoS flow.

[0016] In some embodiments, the sixth wireless communication method further includes mapping the QoS flow to a list of one or more data radio bearers (DRBs) based on the QoS parameter. In some embodiments, the network node switches the mapping of the QoS flow from a first DRB in the list of one or more DRBs to a second DRB in the list of one or more DRBs. In some embodiments, the network includes a core network or an application server.

[0017] A seventh method of wireless communication includes receiving, by a network, a demand or prediction of a quality of service (QoS) flow transmitted by a communication node; and transmitting, after the receiving, a QoS parameter for the QoS flow, wherein the QoS parameter includes an indicator that a QoS demand of the QoS flow has changed over time or a list of one or more QoS parameters to be used by the communication node for the QoS flow.

[0018] In some embodiments, the network receives the demand or prediction of the QoS flow directly from the communication or from a network node. In some embodiments, the network includes a core network or an application server.

[0019] In yet another example aspect, the method described above is embodied in the form of processor-executable code and stored in a non-transitory computer-readable storage medium. When executed by a processor, the code included in the computer-readable storage medium causes the processor to implement the methods described in this patent document.

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

[0021] The above and other aspects and embodiments will be more fully described in the following detailed description, reference being made to the accompanying drawings, illustrations and claims. BRIEF DESCRIPTION OF DRAWINGS

[0022] Figure 1 An example 5G network architecture is shown.

[0023] Figure 2 A dual connectivity (DC) diagram is shown.

[0024] Figure 3 A measurement reporting signaling procedure is shown.

[0025] Figure 4 An example signaling procedure for early measurements is shown.

[0026] Figure 5 An example signaling procedure for data collection for invalid early measurements is shown.

[0027] Figure 6 An example signaling procedure for data collection for secondary cell group (SCG) failure and primary SCG cell (PSCell) in dormant bandwidth part (BWP) is shown.

[0028] Figure 7 An example signaling procedure for data collection for handover failure is shown and configured with dual active protocol stack (DAPS) packet data convergence protocol (PDCP).

[0029] Figure 8 An example signaling procedure for data collection for conditional PSCell addition / change (CPAC) failure is shown.

[0030] Figure 9 An example signaling procedure for data collection for conditional handover (CHO) failure is shown.

[0031] Figure 10 An example signaling procedure for data collection for successful handover is shown.

[0032] Figure 11 An example signaling procedure for data collection using user equipment (UE) assistance information is shown.

[0033] Figure 12 An example signaling procedure for quality of service (QoS) or quality of experience (QoE) enhancements is shown.

[0034] Figure 13A An example flow diagram for performing measurements based on received time delays is shown.

[0035] Figure 13B An example flow diagram for transmitting a report in response to occurrence of an SCG failure is shown.

[0036] Figure 13C An example flow diagram for processing a report in response to occurrence of an SCG failure is shown.

[0037] Figure 13D An example flow diagram for transmitting mobility enhancement related information in response to occurrence of a handover failure is shown.

[0038] Figure 13E An example flow diagram for transmitting usage related information of user equipment (UE) assistance information is shown.

[0039] Figure 13F An example flow diagram for receiving special QoS parameters is shown.

[0040] Figure 13G An example flow diagram for transmitting special QoS parameters is shown.

[0041] Figure 14 An example block diagram of a hardware platform, which can be a network node or a communication node or part of a network, is shown. DETAILED DESCRIPTION

[0042] Figure 1 An example 5G network architecture is shown. As shown in Figure 1 a fifth generation (5G) network architecture can include a 5G core network (5GC) and a next generation radio access network (NG-RAN).

[0043] 5GC can include any of an Access Mobility Function (AMF), a Session Management Function (SMF), and a User Plane Function (UPF). NG-RAN can include base stations with different Radio Access Technologies (RATs), such as evolved 4G base stations (ng-eNBs), 5G base stations (gNBs). NG-RAN base stations can be connected to the 5GC through an NG interface, and NG-RAN base stations can be connected through an Xn interface.

[0044] Figure 2 A dual connectivity (DC) diagram is shown. As shown Figure 2 Various networks (e.g., 4G and 5G systems) can support dual connectivity (DC) functionality. A DC-enabled UE can maintain a connection with two base stations simultaneously, where the first base station can be a master node (MN) and the second base station is a secondary node (SN). Participation in a DC-enabled cell located at the MN can include a master cell group (MCG) containing a primary cell (PCell), and the secondary base station can include a secondary cell group (SCG) including a primary SCG cell (PSCell). The base stations and the terminal UE can be connected through a Uu air interface.

[0045] Figure 3 A signaling procedure for measurement reporting is shown. A UE can provide RAN node (e.g., base station) measurement result reporting information. As shown Figure 3 The UE can send an RRC uplink message to the RAN node. The RRC uplink message can include an available indication. The RAN node can send a UE information request message to the UE. The UE can transmit a UE information response message to the RAN node in response to receiving the UE information request.

[0046] Example titles of the following sections are used to facilitate understanding of the disclosed subject matter and do not limit the scope of the claimed subject matter in any way. Thus, one or more features of one example section can be combined with one or more features of another example section. Furthermore, 5G terminology is used for clarity of explanation, but the technology disclosed in this document is not limited to 5G technology and can be used in wireless systems implementing other protocols as well.

[0047] I. Example techniques for early measurements

[0048] Currently, timer T331 is configured for early measurements, when the UE enters RRC_IDLE or RRC_INACTIVE state, the UE can start performing early measurements and start timer T331, when timer T331 expires, the UE will stop performing early measurements. However, in the case that the UE enters RRC_CONNECTED state relatively late, if timer T331 is short, the early measurement result can be invalid, because timer T331 can have expired, and if timer T331 is long, the UE can perform early measurements for a considerable amount of time, and spend more UE battery consumption. The UE can perform early measurements by measuring, for example, parameters of one or more signals received from one or more base stations (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), etc.).

[0049] In the example techniques described in Section I, a time delay is introduced, if the time delay is received, the UE starts performing early measurements after the time according to the time delay (e.g., the UE does not start performing early measurements immediately when entering RRC_IDLE or RRC_INACTIVE state). This delay measurement technique can achieve reasonable UE battery consumption. In some embodiments, the base station can configure the time delay as a first time value for RRC_IDLE state and a second different time value for RRC_INACTIVE state. In some embodiments, the base station can determine different time delays according to the behavior of the UE. For example, if the base station determines that the UE spends a significant amount of time (e.g., more than a predetermined limit of amount of time) in RRC_IDLE or RRC_INACTIVE state within a predetermined period of time, the base station can configure the time delay for this UE to be longer than the predetermined time value. In another example, if the base station determines that the UE spends a significant amount of time in connected (or active) state within a predetermined period of time, the base station can configure the time delay for this UE to be shorter than the predetermined time value. Thus, the time delay can be configured according to the typical minimum time that the UE is in idle, inactive, or connected state, where the typical minimum time can be determined by the RAN node using statistics related to the amount of time that the UE is in idle, inactive, and / or connected state.

[0050] Further, when the UE enters RRC_CONNECTED state, if the UE considers the early measurement result as invalid, the UE records the value of the time delay and / or the value of timer T331, and reports (or transmits) the value of the time delay and / or the value of timer T331 to the base station, to be able to optimize the configuration of the time delay and / or timer T331. The example embodiments I.1 to I.2 below further describe example techniques for early measurements.

[0051] Example embodiment I.1

[0052] Figure 4 An example signaling procedure for early measurement corresponding to this example embodiment is shown.

[0053] Step 1: The base station sends an RRC DL message (e.g., RRCRelease) including a time delay to the UE, or the base station broadcasts the time delay.

[0054] Step 2: The UE obtains the time delay via receiving the RRC DL message (e.g., RRCRelease) or via receiving the broadcast. The UE starts to perform early measurement after a time according to the time delay when the UE enters the RRC_IDLE or RRC_INACTIVE state. In Step 2, the UE does not start to perform early measurement immediately when entering the RRC_IDLE or RRC_INACTIVE state. The UE starts a timer T331 when starting to perform early measurement, and the UE stops performing early measurement when the UE determines that the timer T331 expires.

[0055] Step 3: The UE enters the RRC_CONNECTED state, and if the UE considers the early measurement result valid (the UE can consider the early measurement result invalid, e.g., when the timer T331 has expired or the measurement is stopped too early before the UE enters the connected state), the UE sends the early measurement result included in an RRC UL message to the base station.

[0056] Step 4: The base station makes a corresponding decision (e.g., performs DC and / or CA immediately) according to the early measurement result.

[0057] Example embodiment I.2

[0058] Figure 5 An example signaling procedure for data collection for invalid early measurement corresponding to this example embodiment is shown.

[0059] Step 1: The base station sends an RRC DL message (e.g., RRCRelease) including a time delay to the UE, or the base station broadcasts the time delay.

[0060] Step 2: The UE obtains the time delay via receiving the RRC DL message (e.g., RRCRelease) or via receiving the broadcast. The UE starts to perform early measurement after a time according to the time delay when the UE enters the RRC_IDLE or RRC_INACTIVE state. In Step 2, the UE does not start to perform early measurement immediately when entering the RRC_IDLE or RRC_INACTIVE state. The UE starts a timer T331 when starting to perform early measurement, and the UE stops performing early measurement when the UE determines that the timer T331 expires.

[0061] Step 3: The UE enters RRC CONNECTED state and considers the early measurement result invalid since the timer T331 has expired. The UE records the value of the time delay and / or the value of the timer T331.

[0062] Step 4: The UE reports information about the invalid early measurement including the recorded value of the time delay and / or the value of the timer T331 to the base station via an RRC UL message (e.g., a UE INFORMATION RESPONSE message). Before this, the UE can send an available indication included in the RRC UL message to the base station to indicate that there is available information about the invalid early measurement to be reported.

[0063] Step 5: The base station can optimize the configuration of the time delay and / or the timer T331 based on the received information about the invalid early measurement.

[0064] II. Example techniques for dormant BWP

[0065] Currently, the concept of dormancy bandwidth part (BWP) is introduced mainly to save UE battery consumption and can quickly switch to normal BWP for data transmission. When SCG failure occurs, the UE sends an SCG failure information message to the base station to indicate SCG failure.

[0066] In the example techniques described in Section II, the PSCell state (e.g., whether the PSCell is in dormancy BWP) is introduced and reported to the base station (e.g., included in the SCG failure information message) so as to be able to optimize the configuration of the dormancy BWP, because the frequency resources configured for the dormancy BWP are different from the frequency resources configured for the normal BWP, and SCG failure can also occur when the PSCell is in the dormancy BWP. The technical advantage of including the PSCell state in the SCG failure information message is that it can enable the base station to determine whether the UE experiences failure when switching between the dormancy BWP mode and the normal state. For example, if the base station determines that the number of failures experienced by the UE when switching between the dormancy BWP mode and the normal state is greater than a predetermined value, the base station can not instruct the UE to enter the dormancy BWP mode. The example techniques of the dormancy BWP are further described in example embodiment II.1.

[0067] Example embodiment II.1

[0068] Figure 6 An example signaling procedure for data collection for SCG failure and PSCell in dormancy BWP corresponding to this example embodiment is shown.

[0069] Step 1: The UE detects SCG failure and determines that the PSCell is in or operating on a dormant BWP.

[0070] Step 2: The UE sends the SCG failure information message including the PSCell status (e.g., whether the PSCell is in the dormant BWP) to the MN to indicate that the SCG failure occurred in the SN and the PSCell is in the dormant BWP.

[0071] Step 3: The MN forwards the received information about the SCG failure and the PSCell status to the SN.

[0072] Step 4: The SN can optimize the configuration of the dormant BWP based on the received information about the SCG failure and the PSCell status.

[0073] III. Example techniques for mobility enhancement related reporting

[0074] Currently, to enhance mobility, dual active protocol stack (DAPS) is introduced. When DAPS is applied to handover, DAPS packet data convergence protocol (PDCP) is configured in the handover target to reduce handover delay, but more resources will be spent in the handover target. Sometimes, due to the application of DAPS PDCP, the UE can more easily reach the maximum number of aggregated carriers that matches its capability. In addition, conditional PSCell addition / change (CPAC) is introduced to improve the reliability of PSCell addition / change. In addition, conditional handover (CHO) is introduced to improve the reliability of handover (HO). In addition, a successful handover report can be introduced to report the case where the signal is poor despite the successful HO.

[0075] In the example techniques described in Section III, PDCP type (e.g., DAPS PDCP, normal PDCP) and / or an indication of whether the maximum number of aggregated carriers is reached are introduced and reported to the base station in order to be able to identify the case when a mobility failure occurs. The mobility failure can include, for example, a handover failure or a PSCell change failure. In addition, CPAC failure information (e.g., conditional PSCell change triggered by the MN or the SN) is introduced to improve the reliability of CPAC (e.g., disable the SN triggered conditional PSCell change according to the number of statistical failures of the SN triggered conditional PSCell change). In addition, CHO failure information (e.g., CHO failure cause) is introduced to improve the reliability of CHO. In addition, successful handover related information is introduced to enhance the successful handover report (e.g., for HO and / or RACH) for network optimization. The example techniques related to mobility enhancement related reporting are further described in Example Embodiments III.1 to III.4 below.

[0076] Example embodiment III.1

[0077] Figure 7 An example signaling procedure for data collection for handover failure is shown, and a DAPS PDCP is configured corresponding to this example embodiment.

[0078] Step 1: UE is handed over from source (e.g., first base station) to target (e.g., second base station), and DAPS PDCP is configured in target.

[0079] Step 2: UE detects handover failure, and DAPS PDCP is configured in target.

[0080] Step 3: UE reports handover failure information including PDCP type (e.g., DAPS PDCP) and / or indication of whether maximum number of aggregated carriers is reached to base station (here the base station can be source, target or other). Received handover failure information can be forwarded to source or target.

[0081] Step 4: BS (here the base station can be source, target or other) finds root cause of handover failure based on received handover failure information.

[0082] Example embodiment III.2

[0083] Figure 8 An example signaling procedure for data collection for CPAC failure is shown, corresponding to this example embodiment.

[0084] Step 1: S-SN initiates conditional PSCell change from S-SN to T-SN for UE.

[0085] Step 2: UE detects conditional PSCell change failure, saves relevant failure information, e.g., S-SN ID, T-SN ID, triggering node (MN or SN).

[0086] Step 3: UE reports CPAC failure information, e.g., S-SN ID, T-SN ID, triggering node (MN or SN) to MN.

[0087] Step 4: MN can send a message to S-SN to directly disable SN triggered conditional PSCell change according to the statistics of SN triggered conditional PSCell change failure received from UE. Or MN sends a message to S-SN to forward the received CPAC failure information to S-SN, and let S-SN disable SN triggered conditional PSCell change by its own decision.

[0088] Example embodiment III.3

[0089] Figure 9An example signaling procedure for data collection for CHO failure corresponding to this example embodiment is shown.

[0090] Step 1: UE switches from source to target and CHO is applied.

[0091] Step 2: UE detects CHO failure and saves CHO failure cause information, e.g., integrity protection failure occurs or invalid ASN.1 is found when decoding encapsulated messages included in CHO command related to one or more CHO candidate cells.

[0092] Step 3: UE reports CHO failure cause information including CHO candidate cell ID, CHO failure cause (e.g., integrity protection failure, invalid ASN.1) to BS (BS here can be source, target or other). Received CHO failure cause information can be forwarded to source or target.

[0093] Step 4: BS (BS here can be source, target or other) finds root cause of CHO failure based on received CHO failure cause information.

[0094] Example embodiment III.4

[0095] Figure 10 An example signaling procedure for data collection for successful handover corresponding to this example embodiment is shown.

[0096] Step 1: UE switches from source to target and succeeds.

[0097] Step 2: UE reports to target HO related information including HO type (e.g., CHO, DAPS, normal HO) and / or 2-step RACH related information. 2-step RACH related information includes at least one of: number of fallbacks between 2-step RACH and 4-step RACH per RACH procedure, number of fallbacks between 2-step RACH and 4-step RACH per beam, an indicator indicating fallback between 2-step RACH and 4-step RACH per RACH procedure (set to true if 2-step RACH is at least fallback to 4-step RACH once during the RACH procedure), an indicator indicating fallback between 2-step RACH and 4-step RACH per beam (set to true if 2-step RACH is at least fallback to 4-step RACH once during the RACH procedure per beam), number of PUSCH transmission occasions (POs) selected per beam, PO indices selected per beam (listed in time order of the attempts), an indicator indicating whether maximum transmission power is used for transmission of PUSCH payload of 2-step RACH per RACH procedure, an indicator indicating whether maximum transmission power is used for transmission of PUSCH payload of 2-step RACH per PO, an indicator indicating whether maximum transmission power is used for transmission of PUSCH payload of 2-step RACH per beam (if maximum transmission power is used to transmit PUSCH payload of 2-step RACH at least on one PO mapped to the beam, the maximum transmission power will be used for the beam), maximum power level used for transmission of PUSCH payload of 2-step RACH per RACH procedure, maximum power level used for transmission of 2-step RACH per PO, maximum power level used for transmission of PUSCH payload of 2-step RACH per beam (if multiple POs are mapped to one beam, it can be a list of maximum power levels per PO or the maximum power level in all POs), power ramping step on each PO used for transmission of PUSCH payload of 2-step RACH, number of power ramping steps per beam, maximum preamble transmission power per beam, number of fallbacks between 2-step CFRA and 2-step CBRA per RACH procedure, number of fallbacks between 2-step CFRA and 2-step CBRA per beam, number of preambles sent on each beam and beam index, indices of attempted beams and number of preambles sent on each attempted beam listed in time order of the attempts, contention detection indication per beam (where the contention detection indication is set to true if at least one failed contention resolution is detected on the beam), fallback related information (e.g., number of fallbacks used during RACH attempts with RACH resources configured for 2-step RACH with a value greater than 0 or a list of fallback values used during RACH attempts with RACH resources configured for 2-step RACH,or the maximum backoff value used during a RACH attempt with RACH resources configured for 2-step RACH), the number of preambles sent by each RACH procedure in each preamble group, the number of preambles sent by each beam in each preamble group, an indication indicating which group of preambles (such as group A, group B, or both) is selected by each RACH procedure, an indication indicating which group of preambles (such as group A, group B, or both) is selected by each beam, an indication indicating which type of beam is selected by each RACH procedure (such as SSB, CSI-RS, or both), a list of beam types selected by each RACH procedure in time order.

[0098] Step 3: The target forwards the successful handover related information to the source.

[0099] Step 4: The source can perform corresponding optimization (e.g. for HO and / or RACH) according to the successful handover related information.

[0100] IV. Example techniques for UE assistance information related reporting

[0101] Currently, although UE assistance information is introduced, the network is not aware of the usage of UE assistance data in the RAN node.

[0102] In the example techniques described in Section IV, information related to the usage of UE assistance information is introduced to enable the network to estimate the usage of UE assistance information in the RAN node. Example techniques for UE assistance information related reporting are further described in example embodiment IV.1 below.

[0103] Example embodiment IV.1

[0104] Figure 11 An example signaling procedure for data collection for the usage of UE assistance information corresponding to this example embodiment is shown.

[0105] Step 1: A RAN node (e.g. a BS) receives UE assistance information from one or more UEs. The UE assistance information can comprise one or more parameters (e.g. signal strength, delay, etc.) and one or more values corresponding to the one or more parameters. The one or more values of the one or more parameters can be measured by the UE, e.g. during early measurements described in this patent document.

[0106] Step 2: The RAN node sends information related to the usage of the UE assistance information to the network (e.g., core network (CN), trace collection entity (TCE), operation management and maintenance (OAM)). The RAN node can send the usage related information indicating whether the RAN node has received and / or used the assistance information from the UE to adjust the performance of the RAN node. The usage related information can also include metrics related to the UE assistance information. The information related to the usage of the UE assistance information includes at least one of the following: (1) an indication of whether the RAN node has received the UE assistance information, (2) an indication of whether the RAN node has used the UE assistance information, (3) a result of the RAN node using the UE assistance information (e.g., success or not), (4) a number of records of the UE assistance information that the RAN node has received, (5) a number of records of the UE assistance information that the RAN node has used, (6) a list of types of the UE assistance information that the RAN node has received, (7) a list of types of the UE assistance information that the RAN node has used, (8) a number of records of the UE assistance information that the RAN node has received per type, (9) a number of records of the UE assistance information that the RAN node has used per type, (10) a result of the RAN node using the UE assistance information per type (e.g., success or not), (11) a number of UEs from which the RAN node has received the UE assistance information, (12) a number of UEs from which the RAN node has used the UE assistance information, (13) a number of UEs from which the RAN node has received the UE assistance information per type, or (14) a number of UEs from which the RAN node has used the UE assistance information per type.

[0107] Step 3: The network can estimate the usage of the UE assistance information in the RAN node.

[0108] V. Example techniques for quality of service (QoS) or quality of experience (QoE) enhancement

[0109] Currently, XR (e.g., AR, VR) is introduced, and some XR related QoS flows can greatly change their QoS requirements (e.g., burst throughput, latency, reliability) over time.

[0110] In the example techniques described in Section V, some enhancements are introduced in the RAN node and / or the UE to improve QoS / QoE, especially for XR services. The example techniques for QoS / QoE enhancements are further described in the following example embodiment V.1.

[0111] Example embodiment V.1

[0112] Figure 12 An example signaling procedure for QoS / QoE enhancements corresponding to this example embodiment is shown.

[0113] Step 1: UE sends requirements and / or predictions for QoS flow to RAN node (e.g., BS).

[0114] Step 2: RAN node forwards requirements and / or predictions for QoS flow to network (e.g., CN, application server).

[0115] Step 3: Network can send special QoS parameters for QoS flow to RAN node, including an indicator indicating that QoS flow and its QoS requirements change significantly over time, a list of QoS parameters that QoS flow uses primarily. QoS parameters can include, for example, maximum latency or latency value.

[0116] Step 4: RAN node can map QoS flow on a group of data radio bearers (DRBs) (e.g., a list of one or more DRBs) according to, for example, the list of QoS parameters that QoS flow uses primarily. For example, RAN node can map QoS flow to a first DRB from the group of DRBs, and then can quickly switch the mapping to a second different DRB from the group of DRBs when needed (e.g., RAN node determines that the measured performance of the first DRB is less than the value indicated by the QoS parameters).

[0117] Figure 13A An example flowchart 1300 for performing a measurement based on a received time delay is shown. At operation 1302, one or more delay values are received by a communication node at a first time, where each delay value indicates an amount of time to be delayed for a measurement. At operation 1304, the communication node performs the measurement at or after a third time, where the third time is based on a delay value from the one or more delay values, and a second time when the communication node enters an idle state or an inactive state, where the first time precedes the second time in time, and where the second precedes the third time in time. For example, when the communication node enters the idle state or the inactive state, the communication node determines the third time by adding the time delay indicated by the delay value to the second time.

[0118] In some embodiments of the method 1300, the one or more delay values include a first delay value associated with the idle state and a second delay value associated with the inactive state. In some embodiments of the method 1300, the one or more delay values include a first delay value based on an amount of time the communication node spends in the idle state or in the connected state, and the one or more delay values include a second delay value based on a second amount of time the communication node spends in the inactive state or in the connected state. In some embodiments, the method 1300 further includes transmitting, to the network node, a delay value and / or a second time value indicating a second amount of time within which to perform the measurement, wherein the delay value or the second time value is transmitted after the communication node enters the connected state or the active state, and wherein the delay value and / or the second time value is sent in response to a result of the measurement being invalid.

[0119] Figure 13B An example flow diagram 1310 is shown for transmitting a report in response to an occurrence of a SCG failure. At operation 1312, a communication node transmits, to a network node, a report in response to an occurrence of a secondary cell group (SCG) failure, wherein the report includes an indication of the SCG failure and a state of a primary SCG cell (PSCell) at the time of the failure. The communication node can determine the occurrence of the SCG failure and trigger the generation and transmission of the report. In some embodiments of the method 1310, the state of the PSCell indicates whether the PSCell is operating on a dormant bandwidth part (BWP). In some embodiments of the method 1310, the network node comprises a master node (MN).

[0120] Figure 13C An example flow diagram 1320 is shown for processing a report in response to an occurrence of a SCG failure. At operation 1322, a first network node receives a report from a communication node, wherein the report is received in response to an occurrence of a secondary cell group (SCG) failure, and wherein the report includes an indication of the SCG failure and a state of a primary SCG cell (PSCell) at the time of the failure. At operation 1324, the first network node transmits the report to a second network node. In some embodiments of the method 1320, the state of the PSCell indicates whether the PSCell is operating on a dormant bandwidth part (BWP). In some embodiments of the method 1320, the first network node comprises a master node (MN), and wherein the second network node comprises a secondary node (SN).

[0121] Figure 13DAn example flowchart 1330 for transmitting mobility enhancement related information in response to occurrence of a handover failure is shown. At operation 1332, the communication node transmits mobility enhancement related information to a first network node in response to a mobility failure occurring when transitioning from a second network node to a third network node, where the mobility enhancement related information includes: dual active protocol stack (DAPS) related information, conditional primary cell group primary cell addition or change (CPAC) failure information, conditional handover (CHO) failure cause information, and / or successful handover related information.

[0122] In some embodiments of the method 1330, the DAPS related information includes a packet data convergence protocol (PDCP) type and / or an indication of whether a maximum number of aggregated carriers is reached. In some embodiments of the method 1330, the CHO failure cause information includes an integrity protection failure or an invalid abstract syntax notation (ASN.1). In some embodiments of the method 1330, the successful handover related information includes a handover type and / or two-step random access channel (RACH) related information. In some embodiments of the method 1330, the CPAC failure indication indicates whether a conditional primary secondary cell group primary cell (PSCell) change was triggered by a primary node or a secondary node.

[0123] Figure 13EAn example flow diagram 1340 for transmitting usage related information for user equipment (UE) assistance information is shown. At operation 1342, a network node transmits, to a network, usage related information for user equipment (UE) assistance information received from a UE, wherein the usage related information indicates whether the UE assistance information and / or metrics associated with the UE assistance information were received or used by the network node, wherein the UE assistance information comprises one or more parameters and one or more corresponding values for each parameter collected by the UE for network performance enhancement, and wherein the usage related information comprises: an indication of whether the UE assistance information was received by the network node, an indication of whether the UE assistance information was used by the network node, a result of the network node using the UE assistance information, a number of records of UE assistance information received by the network node, a number of records of UE assistance information used by the network node, a list of types of UE assistance information that has been received by the network node, a list of types of UE assistance information that has been used by the network node, a number of records of UE assistance information received by the network node per type of UE assistance information, a number of records of UE assistance information used by the network node per type of UE assistance information, a result of the network node using UE assistance information per type of UE assistance information, a number of user equipment from which UE assistance information has been received by the network node, a number of user equipment from which UE assistance information has been received and used by the network node, a number of user equipment from which UE assistance information has been received by the network node per type of UE assistance information, or a number of user equipment from which UE assistance information has been received and used by the network node per type of UE assistance information. In some embodiments of the method 1340, the network comprises a core network, a trace collection entity (TCE), or an operations management and maintenance (OAM).

[0124] Figure 13F An example flow diagram 1350 for receiving special QoS parameters is shown. At operation 1352, a network node transmits, to a network, requirements or predictions for a quality of service (QoS) flow sent by a communication node. At operation 1354, the network node receives, from the network and after the transmitting, QoS parameters for the QoS flow, wherein the QoS parameters comprise: an indicator of how the QoS requirements for the QoS flow change over time, or a list of one or more QoS parameters for the QoS flow used by the communication node.

[0125] In some embodiments of the method 1350, the method further comprises mapping the QoS flow to a list of one or more data radio bearers (DRBs) based on the QoS parameters. In some embodiments of the method 1350, the network node switches a mapping of the QoS flow from a first DRB in the list of one or more DRBs to a second DRB in the list of one or more DRBs. In some embodiments of the method 1350, the network comprises a core network or an application server.

[0126] Figure 13G An example flowchart 1360 for transmitting special QoS parameters is shown. At operation 1362, the network receives a requirement or prediction of a quality of service (QoS) flow sent by a communication node. At operation 1364, the network transmits, upon receipt, a QoS parameter of the QoS flow, where the QoS parameter comprises: an indicator of a change in QoS requirement of the QoS flow over time, or a list of one or more QoS parameters to be used by the communication node for the QoS flow. In some embodiments of method 1360, the network receives the requirement or prediction of the QoS flow directly from the communication or network node. In some embodiments of method 1360, the network comprises a core network or an application server.

[0127] Figure 14 An example block diagram of a hardware platform 1400, which can be part of a network node (e.g., RAN node or base station) or a communication node (e.g., UE) or a network (e.g., core network, TCE, OAM, or application server), is shown. The hardware platform 1400 includes at least one processor 1410 and a memory 1405 having instructions stored thereon. The instructions, when executed by the processor 1410, configure the hardware platform 1400 to perform the operations of method 1300 in FIG. 13 and the operations in the various embodiments described in this patent document. A transmitter 1415 transmits or sends information or data to another node. For example, a network node transmitter can send a message including a time delay to a user equipment. A receiver 1420 receives information or data transmitted or sent by another node. For example, a user equipment can receive a message including a time delay from a network node. Figure 4-1 3 and the operations in the various embodiments described in this patent document. A transmitter 1415 transmits or sends information or data to another node. For example, a network node transmitter can send a message including a time delay to a user equipment. A receiver 1420 receives information or data transmitted or sent by another node. For example, a user equipment can receive a message including a time delay from a network node.

[0128] The following sections describe example methods for data collection and / or performance enhancement for wireless networks.

[0129] In a first example embodiment, the UE receives a time delay, and if received, the UE starts performing early measurements after a time according to the time delay. Thus, for example, the UE does not start performing early measurements immediately when entering RRC_IDLE or RRC_INACTIVE state. In some implementations of the first example embodiment, the UE in RRC_IDLE or RRC_INACTIVE state is configured with a different value, or even a different value for each UE in RRC_IDLE or RRC_INACTIVE state depending on the UE behavior (e.g., for which the duration has a high probability to remain in RRC_IDLE or RRC_INACTIVE state). In some implementations of the first example embodiment, when the UE enters RRC_CONNECTED state and considers the early measurement results invalid, the UE records the value of the time delay and / or the value of the timer T331 and reports to the base station.

[0130] In a second example embodiment, when SCG failure occurs, the UE reports PSCell status (e.g., whether PSCell is in dormant BWP) to the RAN node (e.g., included in the SCG failure information message reported to the MN).

[0131] In a third example embodiment, the UE reports to the RAN node (e.g., BS) information related to mobility enhancements, including at least one of: DAPS related information, CPAC failure information (e.g., whether a conditional PSCell change was triggered by the MN or SN), CHO failure cause information, or successful handover related information.

[0132] In some implementations of the third example embodiment, the DAPS related information can include PDCP type (e.g., DAPS PDCP, normal PDCP) and / or an indication of whether a maximum number of aggregated carriers was reached; the CHO failure cause information can include integrity protection failure or invalid ASN.1; or the successful handover related information can include HO type (e.g., CHO, DAPS HO, normal HO) and / or 2-step RACH related information.

[0133] In a fourth example embodiment, the RAN node (e.g., BS) sends to the network (e.g., CN, TCE, OAM) information related to usage of UE assistance information. In some implementations of the fourth example embodiment, the information related to usage of UE assistance information includes at least one of: an indication of whether the RAN node has received UE assistance information, an indication of whether the RAN node has used UE assistance information, a result (e.g., whether satisfied or not) of the RAN node using UE assistance information, a number of records of UE assistance information that the RAN node has received, a number of records of UE assistance information that the RAN node has used, a list of types of UE assistance information that the RAN node has received, a list of types of UE assistance information that the RAN node has used, a number of records of UE assistance information that the RAN node has received per type, a number of records of UE assistance information that the RAN node has used per type, a result (e.g., whether satisfied or not) of the RAN node using UE assistance information per type, a number of UEs from which the RAN node has received UE assistance information, a number of UEs from which the RAN node has used UE assistance information, a number of UEs from which the RAN node has received UE assistance information per type, or a number of UEs from which the RAN node has used UE assistance information per type.

[0134] In a fourth example embodiment, a RAN node (e.g., BS) receives special QoS parameters for a QoS flow from a network (e.g., CN, application server). In some implementations of the fifth example embodiment, the special QoS parameters for a QoS flow include at least one of: an indicator indicating that the QoS flow has a large variation in its QoS requirements over time, a list of QoS parameters that are mostly used by the QoS flow. In some implementations of the fifth example embodiment, the RAN node can map the QoS flow onto a DRB group (a list of DRBs) according to the received special QoS parameters for the QoS flow. In some implementations of the fifth example embodiment, the RAN node can quickly switch the mapped DRB for the QoS flow (among the mapped DRB group) when needed. In some implementations of the fifth example embodiment, the network receives the requirements and / or predictions for the QoS flow from the UE and then sends the special QoS parameters for the QoS flow to the RAN node. In some implementations of the fifth example embodiment, the requirements and / or predictions for the QoS flow are sent directly from the UE to the network (e.g., via NAS) or from the UE to the RAN node and forwarded to the network.

[0135] In this document, the term "exemplary" is used to mean "example of" and, unless otherwise noted, does not imply ideal or preferred embodiment.

[0136] Some 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, embodied in a computer-readable medium, including computer-executable instructions, such as program code. Computer-readable media can include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), compact disc (CD), digital versatile disc (DVD), etc. Thus, computer-readable media can include non-transitory storage media. Generally, program modules can include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

[0137] Some embodiments disclosed can be implemented using hardware circuitry, software, or a combination thereof. For example, hardware circuitry implementations can include discrete analog and / or digital components, e.g., integrated as part of a printed circuit board. Alternatively or additionally, disclosed components or modules can be implemented as application specific integrated circuit (ASIC) and / or field programmable gate array (FPGA) devices. Some implementations additionally or alternatively include a digital signal processor (DSP), which is a specialized microprocessor optimized for the operation of digital signals processing related to the functionality disclosed herein. Likewise, various components or subcomponents within each module can be implemented in software, hardware, or firmware. Connections between modules and / or components within a module 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.

[0138] Although this document contains many details, these should not be construed as limiting the scope of the required invention or of what can be required, but as merely describing a specific feature of specific embodiments. Some of the features described in this document in the context of separate embodiments can also be implemented within a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features can be described above as acting in particular combinations, one or more features from a particular combination can in some cases be excised from that combination and acting in the context of a sub-combination or in a different sub-combination. Likewise, operations described as being performed in a particular order can be performed in a different order, or in a different order than shown, or in parallel, without departing from the scope of the required features. Also, although operational steps of various embodiments have been described in this document, it is to be understood that no individual step is required, nor is it implied, that any or all described operations be performed in the order presented. Further, as will be appreciated, individual steps implemented in one embodiment are not necessarily required to be implemented in a corresponding embodiment.

[0139] Only some implementations and examples are described herein, other implementations, improvements, 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 communication device, mobility enhancement related information, wherein the mobility enhancement related information comprises successful handover related information in response to an occurrence of a successful handover when transitioning from a first base station to a second base station, wherein the successful handover related information comprises 2-step random access channel (RACH) related information including an indicator indicating a fallback from 2-step RACH to 4-step RACH on an associated beam.

2. The method of claim 1, wherein, The successful handover related information further comprises a handover type.

3. The method of claim 1, wherein, The indicator is set to true in response to a 2-step RACH falling back to a 4-step RACH at least once on the associated beam during a RACH procedure.

4. The method of claim 1, wherein, The 2-step RACH related information further comprises at least one of: indices of attempted beams and a number of preambles transmitted on each attempted beam, listed in a chronological order of the attempts, a contention detection indication for each beam, or a list of beam types selected in a chronological order per RACH procedure.

5. The method of claim 4, wherein, The beam types comprise synchronization signal blocks (SSBs) and / or channel state information reference signals (CSI-RSs). 6.A method of wireless communication, comprising: receiving, by a network device, mobility enhancement related information, wherein the mobility enhancement related information comprises successful handover related information in response to an occurrence of a successful handover when transitioning from a first base station to a second base station, wherein the successful handover related information comprises 2-step random access channel (RACH) related information including an indicator indicating a fallback from 2-step RACH to 4-step RACH on an associated beam.

7. The method of claim 6, wherein, The successful handover related information further comprises a handover type.

8. The method of claim 6, wherein, The indicator is set to true in response to a 2-step RACH falling back to a 4-step RACH at least once on the associated beam during a RACH procedure.

9. The method of claim 6, wherein, The 2-step RACH related information further comprises at least one of: indices of attempted beams and a number of preambles transmitted on each attempted beam, listed in a chronological order of the attempts, a contention detection indication for each beam, or a list of beam types selected in a chronological order per RACH procedure.

10. The method of claim 9, wherein, The beam types comprise synchronization signal blocks (SSBs) and / or channel state information reference signals (CSI-RSs). 11.An apparatus for wireless communication, comprising a processor configured to: transmit mobility enhancement related information, wherein in response to an occurrence of a successful handover when transitioning from a first base station to a second base station, the mobility enhancement related information comprises successful handover related information, wherein the successful handover related information comprises 2-step random access channel (RACH) related information including an indicator indicating a fallback from 2-step RACH to 4-step RACH on an associated beam.

12. The apparatus of claim 11, wherein, The successful handover related information further comprises a handover type.

13. The apparatus of claim 11, wherein, The indicator is set to true in response to a 2-step RACH falling back to a 4-step RACH at least once on the associated beam during a RACH procedure.

14. The apparatus of claim 11, wherein, The 2-step RACH related information further comprises at least one of: an index of the attempted beams and a number of preambles transmitted on each of the attempted beams, listed in a time order of the attempts, a contention detection indication for each beam, or a list of beam types selected in a time order per RACH procedure.

15. The apparatus of claim 14, wherein, The beam types include synchronization signal blocks (SSBs) and / or channel state information reference signals (CSI-RSs).

16. An apparatus for wireless communication, comprising a processor configured to: receive mobility enhancement related information, wherein in response to an occurrence of a successful handover when transitioning from a first base station to a second base station, the mobility enhancement related information comprising successful handover related information, wherein the successful handover related information comprises 2-step random access channel (RACH) related information, the 2-step RACH related information comprising an indicator indicating a fallback from 2-step RACH to 4-step RACH on an associated beam.

17. The apparatus of claim 16, wherein, The successful handover related information further comprises a handover type.

18. The apparatus of claim 16, wherein, The indicator is set to true in response to a 2-step RACH falling back to a 4-step RACH at least once on the associated beam during a RACH procedure.

19. The apparatus of claim 16, wherein, The 2-step RACH related information further comprises at least one of: an index of the attempted beams and a number of preambles transmitted on each of the attempted beams, listed in a time order of the attempts, a contention detection indication for each beam, or a list of beam types selected in a time order per RACH procedure.

20. The apparatus of claim 19, wherein, The beam types include synchronization signal blocks (SSBs) and / or channel state information reference signals (CSI-RSs).

Images