Network handling of primary-secondary cell group cell (pscell) changes

Abstract

Methods, devices, and mechanisms are provided for detecting and reporting successful secondary node and / or primary secondary cell group cell (PScell) changes. In one example, a method of wireless communication performed by a first network element includes transmitting, to a second network element, an indication of a primary-secondary cell group cell (PScell) change associated with a user equipment (UE); transmitting an SPC configuration based on the indication; and receiving an SPC report, wherein the SPC report is based on the SPC configuration and SPC information associated with the UE.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Patent Application No. 18 / 365,345, filed on August 4, 2023, and U.S. Provisional Application No. 63 / 370,717, filed on August 8, 2022, the disclosures of which are hereby incorporated by reference in their entirety and for all applicable purposes. Background Art

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multiple access communication system may include multiple base stations (BSs), each of which simultaneously supports communication of multiple communication devices, which may be further referred to as user equipment (UE). In order to meet the growing demand for extended mobile broadband connections, wireless communication technology is evolving from long-term evolution (LTE) technology to next-generation new radio (NR) technology, which may be referred to as the fifth generation (5G). For example, NR is designed to provide lower latency, higher bandwidth or higher throughput, and higher reliability compared to LTE. NR is designed to operate on a wide spectrum band array, for example, from low frequency bands below about 1 gigahertz (GHz) and mid-frequency bands of about 1 GHz to about 6 GHz to high frequency bands such as millimeter wave (mmWave) bands. NR is also designed to operate across different spectrum types, from licensed spectrum to unlicensed spectrum and shared spectrum. Spectrum sharing enables operators to have the opportunity to aggregate spectrum to dynamically support high-bandwidth services. Spectrum sharing can extend the benefits of NR technology to operators that may not have access to licensed spectrum.

[0004] When operating in a wireless communication system, a UE may move between the coverage areas of multiple different base stations. The UE may report channel measurements. When the BS detects a degradation of channel quality based on reported channel measurements and / or other channel information, the BS may initiate a handover of the UE to another BS that may provide better channel quality to the UE. In a case where the radio signal of a neighboring base station, which may be referred to as a target base station, will provide an enhanced connection with the UE relative to the current serving (or source) base station, the UE may be handed over from the source base station to the target base station. Such techniques may be referred to as handover procedures or mobility procedures, and help provide continuous connectivity to the UE as it moves in a wireless communication system. In some systems, in response to a handover communication from a source base station, the UE may release an active connection with the source base station and establish a new connection with the target base station. Enhanced techniques for performing handovers may help enhance the overall efficiency and reliability of wireless communication systems. Therefore, improvements in mobility support are also desired for NR. Summary of the invention

[0005] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all the expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. The sole purpose of this summary is to present some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to more specific embodiments presented later.

[0006] According to various aspects of the present disclosure, the present disclosure describes methods, systems, and devices for detecting and reporting successful primary and secondary cell group cell (PScell) changes in wireless communication scenarios. For example, a user equipment (UE) may communicate with a network via two or more network nodes including a primary or master node (MN) and at least one secondary node (SN). In some instances, channel conditions observed and reported by the UE may trigger or otherwise cause the network to perform a PScell ​​change to reconfigure the UE with a different PScell ​​and / or SN. The present disclosure describes mechanisms that allow different types of nodes (e.g., MN, SN) to configure the UE for PScell ​​changes and successful PScell ​​change (SPC) reporting. In some aspects, a network node may be configured to generate or determine an SPC report configuration and communicate the configuration to the UE. In some aspects, the node that generates the SPC report configuration may be an MN. In another aspect, the node may be an SN. The call flow or protocol for configuring the UE for SPC determination and reporting may be based on the type of node that determines the SPC report configuration. In another aspect, the UE may be configured to detect an SCG failure during or after a PScell ​​change. The present disclosure provides a scheme and mechanism for UE to detect, store and / or report SCG failure related information to report to the network. Based on the SPC and / or SCG failure report from the UE, one or more network nodes can perform network optimization, which can reduce the chance of future MCG and / or SCG failures.

[0007] According to one aspect of the present disclosure, a method of wireless communication performed by a first network unit includes: sending an indication of a change in a primary and secondary cell group cell (PScell) associated with a user equipment (UE) to a second network unit; sending an SPC report configuration based on the indication; and receiving an SPC report, wherein the SPC report is based on the SPC report configuration and SPC information associated with the UE.

[0008] According to another aspect of the present disclosure, a method of wireless communication performed by a first master node includes: receiving a handover (HO) request from a second master node; sending a primary-secondary cell group cell (PScell) change request to a first secondary node (SN); receiving a first message from a user equipment (UE) indicating that successful HO information is available and successful PScell ​​change information is available; sending at least one request for successful HO information and successful PScell ​​change information to the UE based on the first message; and receiving a successful HO report indicating successful HO information and an SPC report indicating successful PScell ​​change information from the UE based on at least one request.

[0009] According to another aspect of the present disclosure, a method of wireless communication performed by a user equipment (UE) includes: receiving an SN modification indication from a secondary node (SN); receiving a successful primary-secondary cell group cell (PScell) change report configuration from the SN based on the SN modification indication; and sending an SPC report, wherein the SPC report is based on the SPC report configuration and PScell ​​change information associated with the UE.

[0010] According to another aspect of the present disclosure, a method of wireless communication performed by a user equipment (UE) includes: receiving a reconfiguration message for a PSCell change from a network node; detecting a PSCell change failure based on the reconfiguration message; sending an SCG failure report indicating information related to a secondary cell group (SCG) failure to the network node based on detecting the failure; and sending another SCG failure report indicating additional SCG failure related information to the network node after sending the SCG report.

[0011] According to another aspect of the present disclosure, a first network unit includes: a memory device; a transceiver; and a processor communicating with the processor and the transceiver, wherein the first network unit is configured to: send an indication of a change in a primary and secondary cell group cell (PScell) associated with a user equipment (UE) to a second network unit; send an SPC report configuration based on the indication; and receive an SPC report, wherein the SPC report is based on the SPC report configuration associated with the UE and successful PScell ​​change information.

[0012] According to another aspect of the present disclosure, a first master node includes: a memory device; a transceiver; and a processor communicating with the processor and the transceiver, wherein the first master node is configured to: receive a handover (HO) request from a second master node; send a primary-secondary cell group cell (PScell) change request to a first secondary node (SN); receive a first message from a user equipment (UE) indicating that successful HO information is available and successful PScell ​​change information is available; send at least one request for successful HO information and successful PScell ​​change information to the UE based on the first message; and receive a successful HO report indicating successful HO information and an SPC report indicating successful PScell ​​change information from the UE based on at least one request.

[0013] According to another aspect of the present disclosure, a user equipment (UE) includes: a memory device; a transceiver; and a processor communicating with the processor and the transceiver, wherein the UE is configured to: receive an SN modification indication from a secondary node (SN); receive a successful primary-secondary cell group cell (PScell) change report configuration from the SN based on the SN modification indication; and send an SPC report, wherein the SPC report is based on the SPC report configuration and PScell ​​change information associated with the UE.

[0014] According to another aspect of the present disclosure, a user equipment (UE) includes: a memory device; a transceiver; and a processor that communicates with the processor and the transceiver, wherein the UE is configured to: receive a reconfiguration message for a PSCell change from a network node; detect a PSCell change failure based on the reconfiguration message; send a secondary cell group (SCG) failure-related information to the network node based on the detection of the failure; and send an additional SCG failure report indicating additional SCG failure-related information to the network node after sending the SCG report.

[0015] According to another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon, wherein the program code includes instructions executable by a processor of a first network unit, wherein the instructions include code for causing the first network unit to perform the following operations: sending an indication of a change in a primary and secondary cell group cell (PScell) associated with a user equipment (UE) to a second network unit; sending an SPC report configuration based on the indication; and receiving an SPC report, wherein the SPC report is based on the SPC report configuration associated with the UE and successful PScell ​​change information.

[0016] According to another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon, wherein the program code includes instructions executable by a processor of a first master node, wherein the instructions include code for causing the first master node to perform the following operations: receiving a handover (HO) request from a second master node; sending a primary-secondary cell group cell (PScell) change request to a first secondary node (SN); receiving a first message from a user equipment (UE) indicating that successful HO information is available and successful PScell ​​change information is available; sending at least one request for successful HO information and successful PScell ​​change information to the UE based on the first message; and receiving a successful HO report indicating successful HO information and an SPC report indicating successful PScell ​​change information from the UE based on at least one request.

[0017] According to another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon, wherein the program code includes instructions executable by a processor of a user equipment (UE), wherein the instructions include code for causing the UE to perform the following operations: receiving an SN modification indication from a secondary node (SN); receiving a successful primary-secondary cell group cell (PScell) change report configuration from the SN based on the SN modification indication; and sending an SPC report, wherein the SPC report is based on the SPC report configuration and PScell ​​change information associated with the UE.

[0018] According to another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon, wherein the program code includes instructions executable by a processor of a user equipment (UE), wherein the instructions include code for causing the UE to perform the following operations: receiving a reconfiguration message for a PSCell change from a network node; detecting a PSCell change failure based on the reconfiguration message; sending an SCG failure report indicating information related to a secondary cell group (SCG) failure to the network node based on the code for causing the UE to detect the failure; and sending an additional SCG failure report indicating additional SCG failure related information to the network node after the code for causing the UE to send the SCG report.

[0019] According to another aspect of the present disclosure, a first network unit includes: a component for sending an indication of a change in a primary and secondary cell group cell (PScell) associated with a user equipment (UE) to a second network unit; a component for sending an SPC report configuration based on the indication; and a component for receiving an SPC report, wherein the SPC report is based on the SPC report configuration associated with the UE and successful PScell ​​change information.

[0020] According to another aspect of the present disclosure, a first master node includes: a component for receiving a handover (HO) request from a second master node; a component for sending a primary-secondary cell group cell (PScell) change request to a first secondary node (SN); a component for receiving a first message from a user equipment (UE) indicating that successful HO information is available and successful PScell ​​change information is available; a component for sending at least one request for successful HO information and successful PScell ​​change information to the UE based on the first message; and a component for receiving a successful HO report indicating successful HO information and an SPC report indicating successful PScell ​​change information from the UE based on at least one request.

[0021] According to another aspect of the present disclosure, a user equipment (UE) includes: a component for receiving an SN modification indication from a secondary node (SN); a component for receiving a successful primary-secondary cell group cell (PScell) change report configuration from the SN based on the SN modification indication; and a component for sending an SPC report, wherein the SPC report is based on the SPC report configuration and PScell ​​change information associated with the UE.

[0022] According to another aspect of the present disclosure, a user equipment (UE) includes: a component for receiving a reconfiguration message for a PSCell change from a network node; a component for detecting a PSCell change failure based on the reconfiguration message; a component for sending a secondary cell group (SCG) failure-related information to the network node based on the component for detecting the failure; and a component for sending an additional SCG failure report indicating additional SCG failure-related information to the network node after the component for sending the SCG report.

[0023] After reviewing the following description of specific, exemplary embodiments of the present invention in conjunction with the accompanying drawings, other aspects, features, and embodiments of the present invention will become apparent to those of ordinary skill in the art. Although the various features of the present invention may be discussed with respect to certain embodiments and drawings below, all embodiments of the present invention may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of these features may also be used according to the various embodiments of the present invention discussed herein. In a similar manner, although the exemplary embodiments may be discussed below as device, system, or method embodiments, it should be understood that these exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1A A wireless communication network according to some aspects of the present disclosure is illustrated.

[0025] Figure 1B is a diagram illustrating an example decomposed base station architecture according to some aspects of the present disclosure.

[0026] Figure 2

[0013] A wireless communication network that provides user equipment reporting in accordance with some aspects of the present disclosure is illustrated.

[0027] Figure 3 An example of a wireless communication system supporting a handover mechanism and a primary-secondary cell group cell (PScell) change mechanism in wireless communication according to some aspects of the present disclosure is illustrated.

[0028] Figure 4 is a signaling diagram illustrating a PScell ​​change procedure according to some aspects of the present disclosure.

[0029] Figure 5 is a signaling diagram illustrating a PScell ​​change and reporting procedure according to some aspects of the present disclosure.

[0030] Figure 6 is a signaling diagram illustrating a PScell ​​change and reporting procedure according to some aspects of the present disclosure.

[0031] Figure 7 is a signaling diagram illustrating a PScell ​​change and reporting procedure according to some aspects of the present disclosure.

[0032] Figure 8 is a signaling diagram illustrating a PScell ​​change and reporting procedure according to some aspects of the present disclosure.

[0033] Fig. 9 is a signaling diagram illustrating a PScell ​​change and reporting procedure according to some aspects of the present disclosure.

[0034] Fig.10 is a signaling diagram illustrating a PScell ​​change and reporting procedure according to some aspects of the present disclosure.

[0035] Fig.11 is a signaling diagram illustrating a PScell ​​change and reporting procedure according to some aspects of the present disclosure.

[0036] Fig.12 is a signaling diagram illustrating a PScell ​​change and reporting procedure according to some aspects of the present disclosure.

[0037] Fig.13 is a block diagram of user equipment according to some aspects of the present disclosure.

[0038] Fig.14 is a block diagram of an exemplary base station according to some aspects of the present disclosure.

[0039] Fig.15 is a flow chart of an example method for reporting successful PScell ​​change information according to some aspects of the present disclosure.

[0040] Fig.16 is a flow chart of an example method for reporting successful PS cell change information during a network handover procedure according to some aspects of the present disclosure.

[0041] Fig.17 is a flow chart of an example method for reporting successful PScell ​​change information according to some aspects of the present disclosure.

[0042] Fig.18 is a flow chart of an example method for reporting successful PScell ​​change information according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0043] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a comprehensive understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, in order to avoid obscuring such concepts, well-known structures and components are shown in block diagram form.

[0044] The present disclosure as a whole relates to wireless communication systems, which are also referred to as wireless communication networks. In various embodiments, each technology and device can be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, global mobile communication systems (GSM) networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0045] OFDMA network can implement radio technology such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA and GSM are part of Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS using E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunication association groups with the goal of defining globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP plan to improve UMTS mobile phone standards. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution from LTE, 4G, 5G, NR and beyond wireless technologies, where access to the wireless spectrum is shared between networks using a range of new and different radio access technologies or radio air interfaces.

[0046] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to (1) ultra-high density (e.g., about 1M nodes / km) 2 (1) provide coverage for the massive Internet of Things (IoT) with ultra-low complexity (e.g., on the order of tens of bits / second), ultra-low energy (e.g., on the order of 10+ years battery life), and deep coverage with the ability to reach challenging locations; (2) provide coverage including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., on the order of 99.9999% reliability), ultra-low latency (e.g., on the order of 1 millisecond), and for users with extensive mobility or lack of mobility; and (3) provide coverage with enhanced mobile broadband (including extremely high capacity (e.g., on the order of 10Tbps / km 2 ), extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness coverage with advanced discovery and optimization.

[0047] 5G NR can be implemented using an optimized OFDM-based waveform with scalable parameter sets and transmission time intervals (TTIs); with a common, flexible framework to efficiently multiplex services and features using dynamic low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and with advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5G NR and the scaling of subcarrier spacing can efficiently address various services operating across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, the subcarrier spacing may appear at 15kHz on bandwidths (BW) such as 5MHz, 10MHz, 20MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, the subcarrier spacing may appear at 30kHz on 80MHz / 100MHz BW. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur at 60 kHz over 160 MHz BW. Finally, for various deployments transmitting with the mmWave component at 28 GHz TDD, subcarrier spacing may occur at 120 kHz over 500 MHz BW.

[0048] 5G NR's scalable parameter sets facilitate scalable TTIs for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also envisions a self-contained integrated subframe design with UL / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive UL / downlink (which can be flexibly configured on a per-cell basis to dynamically switch between UL and downlink to meet current business needs).

[0049] The various other aspects and features of the present disclosure are further described below. It should be apparent that the teachings herein can be embodied in various forms, and any specific structure, function, or both disclosed herein are merely representative and not restrictive. Based on the teachings herein, it should be understood by those of ordinary skill in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice a method. In addition, such a device can be implemented or such a method can be practiced using other structures, functionality, or structures and functionality other than or different from one or more of the aspects set forth herein. For example, the method can be implemented as a part of a system, device, device, and / or as an instruction stored on a computer-readable medium for execution on a processor or computer. In addition, one aspect can include at least one element of a claim.

[0050] The wireless channel between the network (e.g., BS) and the UE may change over time. The BS may configure a beam set for the UE, and the UE may use one or two service beams to receive DL transmissions from the BS or send UL transmissions to the BS at any point in time. The BS and the UE may keep track of the service beams and the candidate beams. For example, the UE may perform one or more measurements of one or more reference signals configured for the UE, and may include the one or more measurements in a channel state information (CSI) report. If the service beam fails, the BS may reconfigure the UE to use a candidate beam. Because the channel quality between the BS and the UE may change over time, the candidate beams may be updated periodically. It is expected that the UE will update the service beam according to the channel state. The UE may report the link quality of the service beam and the candidate beam to the BS in a CSI report, and the BS may process the CSI report and determine whether the UE's service beam or candidate beam should be reconfigured. If the quality of the beam drops below a threshold, the BS may reconfigure the beam of the UE's service beam or the candidate beam. The BS may configure the threshold. Based on this determination, the BS may send a command to reconfigure the UE's serving beam and / or candidate beams in response to the CSI report.

[0051] The BS may configure the UE to periodically report CSI reports to the BS. The CSI report may include, for example, channel quality information (CQI) and / or reference signal received power (RSRP). CQI is an indicator that carries information about the quality of a communication channel. The BS may use CQI to assist in downlink (DL) scheduling. The BS may use RSRP to manage beams in multi-beam operation. The UE may perform different measurement combinations to include in the CSI report. Therefore, the UE may send a CSI report including CQI but not RSRP, a CSI report including RSRP but not CQI, and / or a CSI report including both CQI and RSRP.

[0052] Future cellular networks need to support data-hungry applications with data rates that may be enhanced via cell densification. In addition to providing high data rates, providing a reliable handover mechanism may be equally important as this directly affects the perceived quality of experience of the end user. In 5G NR, it remains a challenge to provide a reliable handover mechanism with high data rates for medium to high-speed users in urban environments. In some instances, network operators may deploy base stations and turn them on and off in a coordinated manner to save energy. Therefore, the radio channel conditions may change significantly for mobile users, and therefore the neighbor cell list changes rapidly.

[0053] In some aspects, the UE may be configured for dual connectivity with two or more network nodes and on two or more cells. The UE may receive services from a master node (MN) of a master cell group (MCG) and from a secondary node (SN) of a secondary cell group (SCG). In some aspects, the UE may communicate with the network via a primary SCG cell referred to as a PScell. In some instances, a channel condition report from the UE may cause the network to determine to change the PScell ​​and / or SN, thereby facilitating PScell ​​communications. The network node may coordinate the PScell ​​change, and the UE may be configured to detect and report a successful PScell ​​change (SPC). Because multiple network nodes are communicating with the UE, it may be advantageous to define, configure, or otherwise specify the roles and responsibilities of each node when configuring the UE to report PScell ​​change information and a call flow or signaling protocol for facilitating PScell ​​changes.

[0054] The present disclosure describes systems, devices, and methods for PScell ​​changes with SPC reporting. For example, a network node may be configured to generate or determine an SPC reporting configuration and communicate the configuration to a UE. In some aspects, the node that generates the SPC reporting configuration may be a master node (MN). In another aspect, the node may be a secondary node (SN). The call flow or protocol for configuring the UE for SPC determination and reporting may be based on the type of node that determines the SPC reporting configuration. In another aspect, the UE may be configured to detect SCG failures during or after a PScell ​​change. The present disclosure provides schemes and mechanisms for UEs to detect, store, and / or report SCG failure-related information for reporting to the network. Based on SPC and / or SCG failure reports from the UE, one or more network nodes may perform network optimization that may reduce the chance of future MCG and / or SCG failures.

[0055] Various aspects of the present disclosure provide several benefits and advantages. For example, various aspects of the present disclosure provide an efficient architecture and protocol for configuring a UE to detect and report PScell ​​conditions and / or successful changes and to perform network optimization based on the reports. Various aspects of the present disclosure also provide advantageous SCG fault reporting, so that additional useful SCG fault related information can be provided to the network to perform network optimization. In addition, the present disclosure describes methods and procedures for associating SCG fault information with SPC information with or without UE context to perform network optimization.

[0056] Figure 1A A wireless communication network 100 according to some aspects of the present disclosure is illustrated. The network 100 may be a 5G network. The network 100 includes several base stations (BSs) 105 (respectively labeled 105a, 105b, 105c, 105d, 105e, and 105f) and other network entities. The BS 105 may be a station that communicates with the UE 115, and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, and the like. Each BS 105 may provide communication coverage for a particular geographic area. For example, each BS 105 may provide communication coverage for a corresponding geographic coverage area 110. In 3GPP, the term "cell" may refer to the particular geographic coverage area of ​​the BS 105 and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0057] BS105 may provide communication coverage for macro cells or small cells (such as pico cells or femto cells) and / or other types of cells. Macro cells generally cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as pico cells) will generally cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as femto cells) will generally also cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cells (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1A In the example shown, BS105d and 105e may be conventional macro BSs, while BS105a-105c may be macro BSs with one of three-dimensional (3D), full-dimensional (FD), or massive MIMO capabilities. BS 105a-105c may utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. BS105f may be a small cell BS, which may be a home node or a portable access point. BS105 may support one or more (e.g., two, three, four, etc.) cells. Figure 1A In the illustrated example, BSs 105a, 105b, and 105c are examples of macro BSs for coverage areas 110a, 110b, and 110c, respectively. BS 105d is an example of a pico BS or a femto BS for coverage area 110d.

[0058] Network 100 may support synchronous operation or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.

[0059] UE 115 is dispersed throughout the wireless network 100, and each UE 115 can be stationary or mobile. UE 115 may also be referred to as a terminal, a mobile station, a subscriber unit, a station, etc. UE 115 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc. In one aspect, UE 115 may be a device including a universal integrated circuit card (UICC). In another aspect, UE may be a device that does not include a UICC. In some aspects, UE 115 that does not include a UICC may also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a-115d is an example of a mobile smart phone type device accessing the network 100. In one aspect, UE 115c and 115d communicate with each other by sending a side link between UE 115c and 115d in a coverage area 110f. UE 115 may also be a machine specifically configured for connected communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. UE 115e-115h are examples of various machines configured for communications to access network 100. UE 115i-115k are examples of vehicles in coverage area 110e that are equipped with wireless communication devices configured for communications to access network 100. UE 115 may be able to communicate with any type of BS, whether a macro BS, a small cell, etc. Figure 1A In the present invention, a lightning bolt (e.g., a communication link) indicates a wireless transmission between a UE 115 and a serving BS 105 (which is a BS designated to serve the UE 115 on a downlink (DL) and / or uplink (UL), a desired transmission between BSs 105, a backhaul transmission between BSs, or a sidelink transmission between UEs 115.

[0060] In operation, BSs 105a-105c use 3D beamforming and cooperative spatial techniques such as coordinated multipoint (CoMP) or multiple connections to serve UEs 115a and 115b. Macro BS 105d may perform backhaul communications with BSs 105a-105c and small cell BS 105f. Macro BS 105d may also transmit multicast services that UEs 115c and 115d subscribe to and receive. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.

[0061] The BSs 105 may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs 105 (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communications with the UE 115. In various examples, the BSs 105 may communicate with each other directly or indirectly (e.g., via a core network) via a backhaul link (e.g., X1, X2, etc.), which may be a wired communication link or a wireless communication link.

[0062] At least some network devices (such as base stations 105) may include subcomponents, such as access network entities, which may be examples of ANCs or centralized units (CUs). Each access network entity may communicate with each UE 115 through several other access network transmission entities, which may be referred to as radio heads, smart radio heads, transmission / reception points (TRPs), or distributed units (DUs). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or merged into a single network device (e.g., base station 105). For example, a CU may control two or more DUs, which may each be associated with a different cell.

[0063] The network 100 may also support mission-critical communications using ultra-reliable and redundant links for mission-critical devices such as UE 115e, which may be a drone. The redundant communication links with UE 115e may include links from macro BSs 105d and 105e, and links from small cell BS 105f. Other machine-type devices such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device) may communicate directly with BSs such as small cell BS 105f and macro BS 105e through the network 100, or communicate through the network in a multi-step configuration by communicating with another user device such as UE 115f that communicates temperature measurement information to a smart meter (UE 115g), which then reports to the network through the small cell BS 105f, which relays its information to the network. The network 100 may also provide additional network efficiency through dynamic low latency TDD / FDD communications, such as V2V, V2X, C-V2X communications between UE 115i, 115j, or 115k and other UEs 115 and / or vehicle-to-infrastructure (V2I) communications between UE 115i, 115j, or 115k and BS 105.

[0064] In some implementations, the network 100 utilizes an OFDM-based waveform for communication. An OFDM-based system may divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, frequency bins, etc. Each subcarrier may be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may depend on the system BW. The system BW may also be divided into subbands. In other instances, the subcarrier spacing and / or the duration of the TTI may be scalable.

[0065] In some aspects, BS105 may assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS105 to UE 115, and UL refers to the transmission direction from UE 115 to BS105. The communication may be in the form of a radio frame. A radio frame may be divided into a plurality of subframes or time slots, for example, about 10. Each time slot may also be divided into micro-time slots. In FDD mode, simultaneous UL transmission and DL transmission may occur in different frequency bands. For example, each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band. In TDD mode, UL transmission and DL transmission occur in different time periods using the same frequency band. For example, a subframe subset (e.g., a DL subframe) in a radio frame may be used for DL ​​transmission, and another subframe subset (e.g., an UL subframe) in a radio frame may be used for UL transmission.

[0066] DL subframes and UL subframes may also be divided into several zones. For example, each DL subframe or UL subframe may have a predefined zone for the transmission of reference signals, control information, and data. Reference signals are predetermined signals that facilitate communication between BS105 and UE 115. For example, a reference signal may have a specific pilot pattern or structure, wherein a pilot tone may span an operational BW or frequency band, and each pilot tone is located at a predefined time and a predefined frequency. For example, BS105 may send a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable UE 115 to estimate a DL channel. Similarly, UE 115 may send a sounding reference signal (SRS) to enable BS105 to estimate an UL channel. Control information may include resource assignments and protocol control. Data may include protocol data and / or operational data. In some aspects, BS105 and UE115 may communicate using self-contained subframes. Self-contained subframes may include a portion for DL ​​communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a DL communication duration that is longer than a UL communication duration. A UL-centric subframe may include a UL communication duration that is longer than a UL communication duration.

[0067] In some aspects, the network 100 may be an NR network deployed on a licensed spectrum. The BS 105 may send synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in the network 100 to facilitate synchronization. The BS 105 may broadcast system information associated with the network 100 (e.g., including a master information block (MIB), remaining system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some cases, the BS 105 may broadcast the PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) over a physical broadcast channel (PBCH), and may broadcast the RMSI and / or OSI over a physical downlink shared channel (PDSCH).

[0068] In some aspects, a UE 115 attempting to access the network 100 may perform an initial cell search by detecting a PSS from the BS 105. The PSS may enable synchronization of period timing and may indicate a physical layer identification value. The UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identification value that may be combined with the physical layer identification value to identify a cell. The PSS and SSS may be located in the center portion of a carrier or at any suitable frequency within a carrier.

[0069] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESET) for physical downlink control channel (e.g., PDCCH) monitoring, physical UL control channels (e.g., PUCCH), physical UL shared channels (PUSCH), power control, and SRS.

[0070] After obtaining the MIB, RMSI and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may send a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL grant, temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. Upon receiving the random access response, the UE 115 may send a connection request to the BS 105 and the BS 105 may respond with a connection response. The connection response may indicate contention resolution. In some examples, the random access preamble, the RAR, the connection request, and the connection response may be referred to as message 1 (MSG1), message 2 (MSG2), message 3 (MSG3), and message 4 (MSG4), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE 115 may send a random access preamble and a connection request in a single transmission, and the BS 105 may respond by sending a random access response and a connection response in a single transmission.

[0071] After establishing the connection, UE 115 and BS 105 may enter a normal operation phase, in which operational data may be exchanged. For example, BS 105 may schedule UE 115 for UL communication and / or DL ​​communication. BS 105 may send UL scheduling grant and / or DL ​​scheduling grant to UE 115 via PDCCH. Scheduling grant may be sent in the form of DL control information (DCI). BS 105 may send DL communication signals (e.g., carrying data) to UE 115 via PDSCH according to the DL scheduling grant. UE 115 may send UL communication signals to BS 105 via PUSCH and / or PUCCH according to the UL scheduling grant.

[0072] In some aspects, BS105 may communicate with UE 115 using HARQ technology to improve communication reliability, for example, to provide URLLC services. BS105 may schedule UE 115 to perform PDSCH communication by sending DL grant in PDCCH. BS105 may send DL data packets to UE 115 according to the scheduling in PDSCH. DL data packets may be sent in the form of transport blocks (TBs). If UE 115 successfully receives the DL data packet, UE 115 may send HARQ ACK to BS105. On the contrary, if UE115 fails to successfully receive the DL transmission, UE 115 may send HARQ NACK to BS105. Upon receiving HARQ NACK from UE 115, BS105 may retransmit the DL data packet to UE 115. The retransmission may include a decoded version of the DL data that is the same as the initial transmission. Alternatively, the retransmission may include a decoded version of the DL data that is different from the initial transmission. The UE 115 may apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding. The BS 105 and the UE 115 may also apply HARQ to UL communications using a substantially similar mechanism as DL HARQ.

[0073] In some aspects, the network 100 may operate on a system BW or a component carrier (CC) BW. The network 100 may divide the system BW into multiple BWPs (e.g., parts). The BS 105 may dynamically assign the UE 115 to operate on a specific BWP (e.g., a specific part of the system BW). The assigned BWP may be referred to as an active BWP. The UE 115 may monitor the active BWP to find signaling information from the BS 105. The BS 105 may schedule the UE 115 to perform UL or DL ​​communications in the active BWP. In some aspects, the BS 105 may assign a pair of BWPs within the CC to the UE 115 for UL and DL communications. For example, the BWP pair may include a BWP for UL communication and a BWP for DL ​​communication.

[0074] In some aspects, network 100 may operate on a shared channel, which may include a shared frequency band and / or an unlicensed frequency band. For example, network 100 may be an NR-U network operating on an unlicensed frequency band. In such aspects, BS105 and UE115 may be operated by multiple network operation entities. In order to avoid conflicts, BS105 and UE 115 may use a listen-before-talk (LBT) procedure to monitor a transmit opportunity (TXOP) in a shared channel. TXOP may also be referred to as COT. For example, a transmitting node (e.g., BS105 or UE 115) may perform LBT before transmitting in a channel. When LBT passes, the transmitting node may continue to transmit. When LBT fails, the transmitting node may prohibit transmitting in the channel.

[0075] LBT can be based on energy detection (ED) or signal detection. For LBT based on energy detection, when the signal energy measured from the channel is lower than a threshold, the result of LBT is passed. Conversely, when the signal energy measured from the channel exceeds a threshold, the LBT result is a fault. For LBT based on signal detection, when a channel reservation signal (e.g., a predetermined preamble signal) is not detected in the channel, the LBT result is passed. In addition, LBT can be in multiple modes. The LBT mode can be, for example, type 4 (CAT4) LBT, type 2 (CAT2) LBT, or type 1 (CAT1) LBT. CAT1 LBT is referred to as a no-LBT mode, in which no LBT is performed before sending. CAT2 LBT refers to LBT without a random backoff period. For example, a transmitting node can determine a channel measurement in a time interval and determine whether the channel is available based on a comparison of the channel measurement with an ED threshold. CAT4 LBT refers to an LBT with a random backoff and a variable contention window (CW). For example, the sending node may draw a random number and back off for a duration in a certain time unit based on the drawn random number.

[0076] In some aspects, the network 100 may support sidelink communications between UEs 115 on a shared radio frequency band (e.g., in a shared spectrum or an unlicensed spectrum). In some aspects, the UEs 115 may communicate with each other on a 2.4 GHz unlicensed band that may be shared by multiple network operating entities using various radio access technologies (RATs), such as NR-U, WiFi, and / or License Assisted Access (LAA). Figure 2 shown.

[0077] Figure 1B A diagram illustrating an example disaggregated base station 102 architecture is shown. The disaggregated base station 102 architecture may include one or more central units (CUs) 150 that may communicate directly with a core network 104 via a backhaul link, or indirectly with the core network 104 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 145 associated with a service management and orchestration (SMO) framework 135, or both. The CU 150 may communicate with one or more distributed units (DUs) 130 via respective midhaul links, such as an F1 interface. The DU 130 may communicate with one or more radio units (RUs) 140 via respective fronthaul links. The RU 140 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 140.

[0078] Each of the units (i.e., CU 150, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 145, and SMO framework 135) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or transmit signals, or both, to one or more of the other units via a wireless transmission medium.

[0079] In some aspects, the CU 150 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), or service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 150. The CU 150 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 150 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 150 may be implemented to communicate with the DU 130 for network control and signaling.

[0080] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 150.

[0081] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs. In some implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and CU 150 in a cloud-based RAN architecture (such as a vRAN architecture).

[0082] The SMO framework 135 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 135 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 135 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 150, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 135 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 135 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 135 may also include a non-RT RIC 145 configured to support the functionality of the SMO framework 135 .

[0083] The non-RT RIC 145 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 145 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 150, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0084] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 145 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 135 or the non-RT RIC 145. In some examples, the non-RT RIC 145 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 145 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 135 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0085] Figure 2 1 illustrates a wireless communication network 200 that provides user equipment reporting according to some aspects of the present disclosure. Network 200 may correspond to a portion of network 100. To simplify the discussion, Figure 2 Two BS205 (shown as 205a and 205b) and six UE 215 (shown as 215a1, 215a2, 215a3, 215a4, 215b1, and 215b2) are illustrated, but it should be appreciated that the embodiments of the present disclosure can be extended to any suitable number of UE 215 (e.g., about 2, 3, 4, 5, 7, or more) and / or BS205 (e.g., about 1, 3, or more). BS205 and UE 215 may be similar to BS105 and UE 115, respectively. BS205 and UE 215 may share the same radio band for communication. In some instances, the radio band may be a 2.4 GHz unlicensed band, a 5 GHz unlicensed band, or a 6 GHz unlicensed band. Generally speaking, the shared radio band may be at any suitable frequency.

[0086] BS205a and UE 215a1-215a4 may be operated by a first network operating entity. BS205b and UE 215b1-215b2 may be operated by a second network operating entity. In some aspects, the first network operating entity may use the same RAT as the second network operating entity. For example, BS205a and UE 215a1-215a4 of the first network operating entity and BS205b and UE 215b1-215b2 of the second network operating entity are NR-U devices. In some other aspects, the first network operating entity may use a different RAT from the second network operating entity. For example, BS205a and UE 215a1-215a4 of the first network operating entity may utilize NR-U technology, while BS205b and UE 215b1-215b2 of the second network operating entity may utilize WiFi or LAA technology.

[0087] In network 200, some UEs in UE 215a1-215a4 can communicate with each other in peer-to-peer communication. For example, UE 215a1 can communicate with UE 215a2 through side link 252, UE 215a3 can communicate with UE 215a4 through another side link 251, and UE 215b1 can communicate with UE 215b2 through another side link 254. Side links 251, 252 and 254 are unicast bidirectional links. Some UEs in UE 215 can also communicate with BS 205a or BS 205b in UL direction and / or DL ​​direction via communication link 253. For example, UE 215a1, 215a3 and 215a4 are in the coverage area 210 of BS 205a, and therefore can communicate with BS 205a. UE 215a2 is outside the coverage area 210, and therefore can not communicate directly with BS 205a. In some instances, UE 215a1 may operate as a repeater for UE 215a2 to reach BS 205a. Similarly, UE 215b1 is within the coverage area 212 of BS 205b, and therefore may communicate with BS 205b, and may operate as a repeater for UE 215b2 to reach BS 205b. In some aspects, some of UEs 215 are associated with vehicles (e.g., similar to UEs 115i-k), and the communications conducted through side links 251, 252, and 254 may be C-V2X communications. C-V2X communications may refer to communications between a vehicle and any other wireless communication device in a cellular network.

[0088] Figure 3 An example of a wireless communication system 300 that supports a handover mechanism and a primary and secondary cell group cell (PScell) change in wireless communication according to some aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 can implement aspects of the wireless communication system 100. In some examples, the wireless communication system 300 can implement aspects of the wireless communication system 100. The wireless communication system 300 may include a first base station 105A, a second base station 105B, a third base station 105C, a fourth base station 105D, and a UE 115B, which may be as described in reference Figure 1A Depicted are examples of base stations 105 and UEs 115. In some aspects, BS 105 may be referred to as a network node.

[0089] In a handover 315 of UE 115B from a first base station 105A to a second base station 105B, the first base station 105A may be a source base station 105 and the second base station 105B may be a target base station 105. The first base station 105A and the second base station 105B may communicate with each other, such as via a backhaul link 134 (e.g., via an X2, Xn, or other interface), which may be a wired or wireless interface. Figure 3 The example of FIG. 1 shows that the first base station 105A communicates directly with the second base station 105B, but in other cases, the communication may be indirect, such as via a core network (e.g., the core network 130 of FIG. 1 ). In this example, the UE 115B and the first base station 105A may establish a first connection 305. In the event that a handover is triggered, the UE 115B may establish a second connection 310 with the second base station 105B.

[0090] In a PSCell change 330 of UE 115B from a third base station 105C to a fourth base station 105D, the third base station 105B may be a source base station 105 for a secondary cell, and the fourth base station 105D may be a target base station 105 for the secondary cell. The third base station 105C and the fourth base station 105D may communicate with each other, such as via a backhaul link 136 (e.g., via an X2, Xn, or other interface), which may be a wired or wireless interface. Although Figure 3 The example of FIG. 1 shows that the third base station 105C communicates directly with the fourth base station 105D, but in other cases, the communication can be indirect, such as via a core network (e.g., the core network 130 of FIG. 1). In this example, the UE 115B and the third base station 105C can establish a first PScell ​​connection 320. In the event that a PScell ​​change is triggered, the UE 115B can establish a second connection 325 with the fourth base station 105D. The various techniques discussed herein provide efficient handover and PScell ​​changes, including mechanisms for initiating, configuring, and reporting PScell ​​changes.

[0091] Figure 4 1 is a signaling diagram illustrating a PScell ​​change procedure 400 facilitated or otherwise controlled by a master node (MN) according to some aspects of the present disclosure. The PScell ​​change procedure 400 may include a master node (MN) 105A, a source secondary node (S-SN) 105C, a target SN (T-SN) 105D, a UE 115, which may be a reference Figure 1A to Figure 2Examples of corresponding devices described. In some examples, the PScell ​​change procedure 400 can implement various aspects of the wireless communication systems 100 and 200. For example, the MN 105A, the S-SN 105C, the T-SN 105D and the UE 115 can support a PScell ​​change procedure in which the MN configures the UE 115 to determine a successful PScell ​​change and / or for a PScell ​​change report. As illustrated, the PScell ​​change procedure 400 includes several enumeration steps, but an implementation of the PScell ​​change procedure 400 may include additional steps before, after, and between these enumeration steps. In some implementations, one or more of these enumeration steps may be omitted or performed in a different order. In the following description of the PScell ​​change procedure 400, operations between the MN 105A, the S-SN 105C, the T-SN 105D and / or the UE 115 may be sent in an order different from the exemplary order shown or at different times. Certain operations may also be excluded from the PScell ​​change procedure 400 , or other operations may be added to the PScell ​​change procedure 400 .

[0092] At step 405, the master node (MN) 105A sends a secondary node (SN) add request to the target SN (T-SN) 105D. In some aspects, sending the SN add request may include sending an Xn message or signal indicating the SN add request. In some aspects, the SN add request message may provide or indicate RRC and / or data radio bearer (DRB) configuration information for changing the SN. In some aspects, the MN may send the SN add request based on one or more reports and / or measurements obtained by the UE 115. In this regard, the UE 115 may obtain one or more channel measurements of the primary and secondary cell group cells (PScell) facilitated by the source secondary node (S-SN) 105C. The UE 115 may send a report indicating the channel measurement to the MN 105A, the S-SN 105C, and / or any other network node or device. For example, the UE 115 may send a channel state information (CSI) report to the MN 105A and / or to the S-SN 105C based on the channel measurement. A network node such as MN 105A may determine to perform a PScell ​​change based on the report.

[0093] At step 410, the T-SN 105D sends an SN add confirmation to the MN 105A. In some aspects, the SN add confirmation may include an Xn message. In some aspects, the SN add confirmation may include information for allocating resources, providing SCG resource configuration, and / or for providing any other suitable information.

[0094] At step 415, the MN 105A sends an SN Release Request to the S-SN 105C, requesting the S-SN 105C to release or terminate communication with the UE 115. In some aspects, the SN Release Request may include an Xn message.

[0095] At step 420, the S-SN 105C sends an SN Release Request Acknowledgement to the MN 105A based on the SN Release Request. In some aspects, the SN Release Request Acknowledgement may include an Xn message.

[0096] At step 425, the MN 105A sends an RRCReconfiguration message to the UE 115. The RRCReconfiguration message may include or indicate a successful PScell ​​change (SPC) configuration. In some aspects, the SPC configuration may include an SPC-Config. In some aspects, the SPC-Config may include or indicate information for the PScell ​​change. For example, the SPC configuration may indicate one or more triggering events and / or conditions to determine whether the PScell ​​change is successful. In some aspects, the SPC configuration may include or indicate one or more timer values ​​or other thresholds that the UE 115 may use to determine whether the PScell ​​change is successful. For example, the SPC configuration may include at least one of a T304 threshold, a T310 threshold, and / or a T312 threshold. In the illustrated example, the MN 105A may autonomously configure the SPC configuration. However, in other examples (e.g., such as Figure 5 exemplified), the SPC configuration may be configured and / or determined by one or more other network nodes (such as S-SN 105C and / or T-SN 105D).

[0097] At step 430, the UE 115 determines that one or more trigger conditions have been met for the PScell ​​change based on the SPC configuration sent at step 425. In some aspects, the condition may be based on a timer value or threshold indicated in the SPC configuration. For example, the UE 115 may determine that the PScell ​​change is successful based on one or more of a T304 threshold, a T310 threshold, and / or a T312 threshold.

[0098] At step 435, the UE 115 sends an RRC reconfiguration complete message to the MN 105A based on the SPC configuration and the determination of step 430. The RRC reconfiguration complete message may include or indicate that successful PScell ​​change information is available. For example, the RRC reconfiguration complete message may include or indicate a successPSCellChange-InfoAvailable field or tag, which indicates to the network that successful PScell ​​change information is available. In some aspects, the successful PScell ​​change information may include sending a UCI to the MN 105A indicating that successful PScell ​​change information is available. In other aspects, the successful PScell ​​change information may be carried and / or indicated in an RRC message and / or a medium access control-control element (MAC-CE).

[0099] At step 440, the MN 105A sends an SN reconfiguration complete message to the T-SN 105D. In some aspects, the SN reconfiguration complete message includes sending an Xn message including or indicating the SN reconfiguration complete message.

[0100] At step 445, the MN 105A sends an information request to the UE 115 based on the indication that PScell ​​change information is available. In some aspects, the information request may include a UEInformationRequest message that includes or indicates an SPC report request. In some aspects, the UEInformationRequest message may include an RRC message or an IE.

[0101] At step 450, the UE 115 sends a UE information response or report to the MN 105A based on the information request sent at step 440. In some aspects, the UE information response includes a UEInformationResponse message that includes or indicates an SPC report. In some aspects, the SPC report may include information associated with the PScell ​​change. For example, the SPC report may indicate one or more conditional events or triggers detected by the UE indicating a successful PScell ​​change. In some aspects, the UEInformationResponse message may include an RRC message or IE.

[0102] At step 455, based on the SPC report, the MN 105A performs one or more network optimizations. For example, in some aspects, the MN 105A may update one or more timer thresholds associated with radio link monitoring (RLM) and / or beam failure detection (BFD) of the MCG and / or SCG. In another aspect, the MN 105A may detect a near failure scenario during a successful PScell ​​change and / or a successful handover (HO).

[0103] Figure 5 1 is a signaling diagram illustrating a PScell ​​change procedure 500 facilitated, initiated, and / or otherwise controlled by an SN according to some aspects of the present disclosure. The PScell ​​change procedure 500 may include MN 105A, S-SN 105C, T-SN 105D, UE 115, which may be reference Figures 1A to 2 Examples of corresponding devices described. In some examples, the PScell ​​change procedure 500 can implement various aspects of the wireless communication systems 100 and 200. For example, the MN 105A, the S-SN 105C, the T-SN 105D, and the UE 115 can support a PScell ​​change procedure, in which the SN initiates a PScell ​​change and at least partially participates in the configuration of the UE 115 to determine a successful PScell ​​change and / or for a PScell ​​change report. As illustrated, the PScell ​​change procedure 500 includes several enumeration steps, but the implementation of the PScell ​​change procedure 500 may include additional steps before, after, and between these enumeration steps. In some embodiments, one or more of these enumeration steps may be omitted or performed in a different order. In the following description of the PScell ​​change procedure 500, the operations between the MN 105A, the S-SN 105C, the T-SN 105D, and / or the UE 115 may be sent in an order different from the exemplary order shown or at different times. Certain operations may also be excluded from the PScell ​​change procedure 500 , or other operations may be added to the PScell ​​change procedure 500 .

[0104] At step 505, the S-SN 105C sends an SN change required message, and the MN 105A receives the SN change required message, so that the MN 105A proceeds with SN addition, release, or other SN modification. In another aspect, the SN change required message may include or indicate one or more SPC configuration parameters. For example, the SN change required message may include a first portion of the SPC configuration. The S-SN 105C may determine and indicate at least one timer value or threshold in the SN change required message. For example, the S-SN 105C may determine and indicate at least one of a T310 timer value or threshold, and / or a T312 timer value or threshold in the SN change required message.

[0105] At step 510, MN 105A sends an SN add request to T-SN 105D based on the SN change required message received from S-SN 105C. In some aspects, sending the SN add request may include sending an Xn message or signal indicating the SN add request. In some aspects, the SN add request message may provide or indicate RRC and / or data radio bearer (DRB) configuration information for changing the SN. In some aspects, the MN may send the SN add request based on one or more reports and / or measurements obtained by UE 115. In this regard, UE 115 may obtain one or more channel measurements of a primary and secondary cell group cell (PScell) facilitated by S-SN 105C. UE 115 may send a report indicating channel measurements to MN 105A, S-SN 105C, and / or any other network node or device. For example, UE 115 may send a channel state information (CSI) report to MN 105A and / or to S-SN 105C based on the channel measurements. A network node such as MN 105A may determine to perform a PScell ​​change based on the report.

[0106] At step 515, the T-SN 105D sends an SN add confirmation to the MN 105A. In some aspects, the SN add confirmation may include an Xn message. In some aspects, the SN add confirmation may include information for allocating resources, providing SCG resource configuration, and / or for providing any other suitable information. In some aspects, the SN add confirmation message may include one or more SPC configuration parameters. In this regard, the PSC configuration may include a second portion of the SPC configuration. For example, in some aspects, the SN add request confirmation message may include or indicate a T304 time value or threshold.

[0107] At step 520, MN 105A sends an RRCReconfiguration message to UE 115. The RRCReconfiguration message may include or indicate an SPC configuration. In some aspects, the SPC configuration may include an SPC-Config. In some aspects, the SPC-Config may include or indicate information for a PScell ​​change. For example, the SPC configuration may indicate a combination of SPC configuration parameters determined by the S-SN 105C and / or the T-SN 105D and indicated by the SN Change Required message sent at step 505 and / or the SN Add Request Confirmation message sent at step 515. In another aspect, MN 105A may determine one or more additional SPC configuration parameters to be included in the SPC-Config. Thus, MN 105A may combine or aggregate different portions of the SPC configuration from the S-SN 105C and / or the T-SN 105D and any SPC configuration parameters determined by MN 105A for the SPC-Config.

[0108] At step 525, the UE 115 determines that one or more trigger conditions have been met for the PScell ​​change based on the SPC configuration sent at step 520. In some aspects, the condition may be based on a timer value or threshold indicated in the SPC configuration. For example, the UE 115 may determine that the PScell ​​change is successful based on one or more of a T304 threshold, a T310 threshold, and / or a T312 threshold.

[0109] At step 530, the UE 115 sends an RRC reconfiguration complete message to the MN 105A based on the SPC configuration and the determination of step 525. The RRC reconfiguration complete message may include or indicate that successful PScell ​​change information is available. For example, the RRC reconfiguration complete message may include or indicate a successPSCellChange-InfoAvailable field or tag, which indicates to the network that successful PScell ​​change information is available. In some aspects, the successful PScell ​​change information may include sending a UCI to the MN 105A indicating that successful PScell ​​change information is available. In other aspects, the successful PScell ​​change information may be carried and / or indicated in an RRC message and / or a medium access control-control element (MAC-CE).

[0110] At step 535, the MN sends an SN Change Confirm to the S-SN 105C. In some aspects, the SN Change Confirm comprises an Xn message.

[0111] At step 540, the MN 105A sends an SN reconfiguration complete message to the T-SN 105D. In some aspects, sending the SN reconfiguration complete message includes sending an Xn message including or indicating the SN reconfiguration complete message.

[0112] At step 545, the MN 105A sends an information request to the UE 115 based on the indication that PScell ​​change information is available. In some aspects, the information request may include a UEInformationRequest message that includes or indicates an SPC report request. In some aspects, the UEInformationRequest message may include an RRC message or an IE.

[0113] At step 550, UE 115 sends a UE information response or report to MN 105A based on the information request sent at step 540. In some aspects, the UE information response includes a UEInformationResponse message that includes or indicates an SPC report. In some aspects, the SPC report may include information associated with a PScell ​​change. In some aspects, the UEInformationResponse message may include an RRC message or IE.

[0114] At step 555, the MN 105A sends or forwards the SPC report included in the UE Information Response to the S-SN 105C. In some aspects, step 555 may include sending an Xn message indicating one or more of the parameters of the SPC report included in the UE Information Response sent at step 550.

[0115] At step 560, based on the SPC report, the MN 105A performs one or more network optimizations. For example, in some aspects, the MN 105A may update one or more timer thresholds associated with radio link monitoring (RLM) and / or beam failure detection (BFD) of the MCG and / or SCG. In another aspect, the MN 105A may detect a near failure scenario during a successful PScell ​​change and / or a successful handover (HO).

[0116] Figure 6 1 is a signaling diagram illustrating a PScell ​​change procedure 600 facilitated or otherwise controlled by a MN according to some aspects of the present disclosure. The PScell ​​change procedure 600 may include the MN 105A, the S-SN 105C, the T-SN 105D, the UE 115, which may be reference Figure 1A to Figure 2Examples of corresponding devices described. In some examples, the PScell ​​change procedure 600 can implement various aspects of the wireless communication systems 100 and 200. For example, the MN 105A, the S-SN 105C, the T-SN 105D, and the UE 115 can support a PScell ​​change procedure in which the MN configures the UE 115 to determine a successful PScell ​​change and / or for a PScell ​​change report. As illustrated, the PScell ​​change procedure 600 includes several enumeration steps, but an implementation of the PScell ​​change procedure 600 may include additional steps before, after, and between these enumeration steps. In some implementations, one or more of these enumeration steps may be omitted or performed in a different order. In the following description of the PScell ​​change procedure 600, operations between the MN 105A, the S-SN 105C, the T-SN 105D, and / or the UE 115 may be sent in an order different from the exemplary order shown or at different times. Certain operations may also be excluded from the PScell ​​change procedure 600 , or other operations may be added to the PScell ​​change procedure 600 .

[0117] At step 605, MN 105A sends an SN add request to T-SN 105D. In some aspects, sending the SN add request may include sending an Xn message or signal indicating the SN add request. In some aspects, the SN add request message may provide or indicate RRC and / or data radio bearer (DRB) configuration information for changing the SN. In some aspects, the MN may send the SN add request based on one or more reports and / or measurements obtained by UE 115. In this regard, UE 115 may obtain one or more channel measurements of a primary and secondary cell group cell (PScell) facilitated by S-SN 105C. UE 115 may send a report indicating channel measurements to MN 105A, S-SN 105C, and / or any other network node or device. For example, UE 115 may send a channel state information (CSI) report to MN 105A and / or to S-SN 105C based on the channel measurements. A network node such as MN 105A may determine to perform a PScell ​​change based on the report.

[0118] At step 610, the T-SN 105D sends an SN add confirmation to the MN 105A. In some aspects, the SN add confirmation may include an Xn message. In some aspects, the SN add confirmation may include information for allocating resources, providing SCG resource configuration, and / or for providing any other suitable information.

[0119] At step 615, the MN 105A sends an SN release request to the S-SN 105C, requesting the S-SN 105C to release or terminate communication with the UE 115. In some aspects, the SN release request may include an Xn message.

[0120] At step 620, the S-SN 105C sends an SN Release Request Acknowledgement to the MN 105A based on the SN Release Request. In some aspects, the SN Release Request Acknowledgement may include an Xn message.

[0121] At step 625, the MN 105A sends an RRCReconfiguration message to the UE 115. The RRCReconfiguration message may include or indicate a successful PScell ​​change (SPC) configuration. In some aspects, the SPC configuration may include an SPC-Config. In some aspects, the SPC-Config may include or indicate information for the PScell ​​change. For example, the SPC configuration may indicate one or more triggering events and / or conditions to determine whether the PScell ​​change is successful. In some aspects, the SPC configuration may include or indicate one or more timer values ​​or other thresholds that the UE 115 may use to determine whether the PScell ​​change is successful. For example, the SPC configuration may include at least one of a T304 threshold, a T310 threshold, and / or a T312 threshold. In the illustrated example, the MN 105A may autonomously configure the SPC configuration. However, in other examples (e.g., such as Figure 5 exemplified), the SPC configuration may be configured and / or determined by one or more other network nodes (such as S-SN 105C and / or T-SN 105D).

[0122] At step 630, the UE 115 determines that one or more trigger conditions have been met for the PScell ​​change based on the SPC configuration sent at step 625. In some aspects, the condition may be based on a timer value or threshold indicated in the SPC configuration. For example, the UE 115 may determine that the PScell ​​change is successful based on one or more of a T304 threshold, a T310 threshold, and / or a T312 threshold.

[0123] At step 635, UE 115 sends an RRC reconfiguration complete message to MN 105A based on the SPC configuration and the determination of step 630. The RRC reconfiguration complete message may include or indicate that successful PScell ​​change information is available. For example, the RRC reconfiguration complete message may include or indicate a successPSCellChange-InfoAvailable field or tag, which indicates to the network that successful PScell ​​change information is available. In some aspects, the successful PScell ​​change information may include sending a UCI to MN105A indicating that successful PScell ​​change information is available. In other aspects, the successful PScell ​​change information may be carried and / or indicated in an RRC message and / or a medium access control-control element (MAC-CE).

[0124] At step 640, the MN 105A sends an SN reconfiguration complete message to the T-SN 105D. In some aspects, the SN reconfiguration complete message includes sending an Xn message including or indicating the SN reconfiguration complete message.

[0125] At step 645, the UE 115 determines or detects an SCG failure at the T-SN. In some aspects, the SCG failure may occur before the PScell ​​change has been completed. In some aspects, detecting the SCG failure may include determining that one or more signals or messages were not successfully received. In another aspect, determining the SCG failure may include determining or detecting a radio link failure, a failure of SCG reconfiguration, an SCG integrity failure, exceeding a maximum uplink transmit timing difference, a random access failure, and / or any other suitable method of detecting an SCG failure.

[0126] At step 650, based on detecting the SCG failure, the UE 115 sends SCG failure information to the MN 105A. In some aspects, the SCG failure information includes or indicates information associated with the SCG failure, such as the failure type or condition that caused the SCG failure. In some aspects, the failure type may include T310 timer expiration, random access problem, synchronization reconfiguration failure, SRB3 integrity failure, and / or any other relevant failure type. In some aspects, the network may use the SCG failure information to modify or update subsequent SCG configurations.

[0127] At step 655, the MN 105A sends an information request to the UE 115 based on the SCG failure information sent at step 650. In some aspects, the information request may include a UEInformationRequest message that includes or indicates an SPC report request. In some aspects, the UEInformationRequest message may include an RRC message or an IE.

[0128] At step 650, the UE 115 sends a UE information response or report to the MN 105A based on the information request sent at step 640. In some aspects, the UE information response includes a UEInformationResponse message that includes or indicates an SPC report. In some aspects, the SPC report may include information associated with a PScell ​​change. In some aspects, the UEInformationResponse message may include an RRC message or IE.

[0129] At step 655, based on the SPC report, the MN 105A performs one or more network optimizations, as explained above.

[0130] In some aspects, the MN may correlate information from the SPC report with the SCG fault information and use the correlated information to perform network optimization. In some aspects, the MN 105A may correlate the SPC report with the SCG fault information based on a UE context associated with the SPC report and the SCG fault information. In other instances, the UE context may not be available. For example, the MN 105A may periodically delete the UE context so that the SPC report and the SCG fault information may not be associated through the UE context. In some aspects, the MN 105A may be configured to correlate the SPC report with the SCG fault information based on one or more other identifiers or indicators in at least one of the SPC report and / or the SCG fault information.

[0131] For example, in some aspects, the SCG fault information may include an SPC report indicator indicating that an SPC report has been transmitted to the network for handover and / or SN change. In another example, the SCG fault information may include an SPC report indicator indicating that there is an SPC report associated with the handover. In another example, the SPC report and the SCG fault information may include or indicate the same C-RNTI. In another aspect, the MN 105A may associate the SCG fault information with the SPC report based on the associated timestamps of the SCG fault information and the SPC report. For example, the MN 105A may determine that the SPC report is associated with the SCG fault information received within a time threshold of the SPC report. In another aspect, if the SPC report has not been transmitted by the time the SCG fault information is generated, the MN 105A may merge the SPC report with the SCG fault information. In another aspect, if the SCG fault information has not been transmitted by the time the SPC report is generated, the MN 105A may merge the SCG fault information with the SPC report. In another aspect, if the SCG failure occurs within a certain time window after the SPC report is generated, the MN 105A can discard the SPC report. In another aspect, the UE 115 can report to the SPC and add a tag or reference indicator to the SCG failure information. The reference indicator can be used to associate the SPC report with the SCG failure information.

[0132] Figure 7 1 is a signaling diagram illustrating a PScell ​​change procedure 700 facilitated or otherwise controlled by a MN according to some aspects of the present disclosure. The PScell ​​change procedure 700 may include a first MN 105A, a second MN 105B, an S-SN 105C, a T-SN 105D, and a UE 115, which may be reference Figures 1A to 2Examples of corresponding devices described. In some examples, the PScell ​​change procedure 700 can implement various aspects of the wireless communication systems 100 and 200. For example, the first MN 105A, the S-SN 105C, the T-SN 105D and the UE 115 can support a PSCell change procedure in which the MN configures the UE 115 to determine a successful PSCell change and / or for a PSCell change report. As illustrated, the PScell ​​change procedure 700 includes several enumeration steps, but the implementation of the PScell ​​change procedure 700 may include additional steps before, after and between these enumeration steps. In some implementations, one or more of these enumeration steps may be omitted or performed in a different order. In the following description of the PScell ​​change procedure 700, the operations between the first MN 105A, the S-SN 105C, the T-SN 105D and / or the UE 115 may be sent in an order different from the exemplary order shown or at different times. Certain operations may also be excluded from the PScell ​​change procedure 700 , or other operations may be added to the PScell ​​change procedure 700 .

[0133] At step 705, MN 105A sends an SN add request to T-SN 105D. In some aspects, sending the SN add request may include sending an Xn message or signal indicating the SN add request. In some aspects, the SN add request message may provide or indicate RRC and / or data radio bearer (DRB) configuration information for changing the SN. In some aspects, the MN may send the SN add request based on one or more reports and / or measurements obtained by UE 115. In this regard, UE 115 may obtain one or more channel measurements of a primary and secondary cell group cell (PScell) facilitated by S-SN 105C. UE 115 may send a report indicating the channel measurement to the first MN 105A, S-SN 105C, and / or any other network node or device. For example, UE 115 may send a channel state information (CSI) report to the first MN 105A and / or to the S-SN 105C based on the channel measurement. A network node such as the first MN 105A may determine to perform a PScell ​​change based on the report.

[0134] At step 710, the T-SN 105D sends an SN add confirmation to the first MN 105A. In some aspects, the SN add confirmation may include an Xn message. In some aspects, the SN add confirmation may include information for allocating resources, providing SCG resource configuration, and / or for providing any other suitable information.

[0135] At step 715, the first MN 105A sends an SN release request to the S-SN 105C, requesting the S-SN 105C to release or terminate communication with the UE 115. In some aspects, the SN release request may include an Xn message.

[0136] At step 720, the S-SN 105C sends an SN release request confirmation to the first MN 105A based on the SN release request. In some aspects, the SN release request confirmation may include an Xn message.

[0137] At step 725, the first MN 105A sends an RRCReconfiguration message to the UE 115. The RRCReconfiguration message may include or indicate a successful PScell ​​change (SPC) configuration. In some aspects, the SPC configuration may include an SPC-Config. In some aspects, the SPC-Config may include or indicate information for the PScell ​​change. For example, the SPC configuration may indicate one or more triggering events and / or conditions to determine whether the PScell ​​change is successful. In some aspects, the SPC configuration may include or indicate one or more timer values ​​or other thresholds that the UE 115 may use to determine whether the PScell ​​change is successful. For example, the SPC configuration may include at least one of a T304 threshold, a T310 threshold, and / or a T312 threshold. In the illustrated example, the first MN 105A may autonomously configure the SPC configuration. However, in other examples (e.g., such as Figure 5 exemplified), the SPC configuration may be configured and / or determined by one or more other network nodes (such as S-SN 105C and / or T-SN 105D).

[0138] At step 730, the UE 115 determines that one or more trigger conditions have been met for the PScell ​​change based on the SPC configuration sent at step 725. In some aspects, the condition may be based on a timer value or threshold indicated in the SPC configuration. For example, the UE 115 may determine that the PScell ​​change is successful based on one or more of a T304 threshold, a T310 threshold, and / or a T312 threshold.

[0139] At step 735, the UE 115 sends an RRC reconfiguration complete message to the first MN 105A based on the SPC configuration and the determination of step 730. The RRC reconfiguration complete message may include or indicate that successful PScell ​​change information is available. For example, the RRC reconfiguration complete message may include or indicate a successPSCellChange-InfoAvailable field or tag, which indicates to the network that successful PScell ​​change information is available. In some aspects, the successful PScell ​​change information may include sending a UCI indicating that successful PScell ​​change information is available to the first MN 105A. In other aspects, the successful PScell ​​change information may be carried and / or indicated in an RRC message and / or a medium access control-control element (MAC-CE).

[0140] At step 740, the first MN 105A sends an SN reconfiguration complete message to the T-SN 105D. In some aspects, the SN reconfiguration complete message includes sending an Xn message including or indicating the SN reconfiguration complete message.

[0141] At step 745, the UE 115 determines or detects an SCG failure at the T-SN. In some aspects, the SCG failure may occur before the PScell ​​change has been completed. In some aspects, detecting the SCG failure may include determining that one or more signals or messages were not successfully received. In another aspect, determining the SCG failure may include determining or detecting a radio link failure, a failure of SCG reconfiguration, an SCG integrity failure, exceeding a maximum uplink transmit timing difference, a random access failure, and / or any other suitable method of detecting an SCG failure.

[0142] At step 750, based on detecting the SCG failure, the UE 115 sends SCG failure information to the first MN 105A. In some aspects, the SCG failure information includes or indicates information associated with the SCG failure, such as the failure type or condition that caused the SCG failure. In some aspects, the failure type may include T310 timer expiration, random access problem, synchronization reconfiguration failure, SRB3 integrity failure, and / or any other relevant failure type. In some aspects, the network may use the SCG failure information to modify or update subsequent SCG configurations.

[0143] At step 755, the first MN 105A stores at least a portion of the SCG failure information. In some aspects, the SCG failure information may be indicated in an SCG failure report. In some aspects, the SCG failure information may include one or more triggering events or conditions associated with the SCG failure.

[0144] At step 760, the UE 115 and the second MN 105B perform a handover (HO) procedure from the first MN 105A to the second MN 105B. In some aspects, performing the HO may include sending a handover command including an RRC reconfiguration message instructing the UE 115 to handover from the first MN 105A to the second MN 105B where a handover execution phase begins. The handover command may include information associated with the second MN 105B, such as a random access channel (RACH) preamble assignment for accessing the second MN 105B. During the handover execution phase, the UE 115 may perform the handover by performing a random access procedure with the second MN 105B.

[0145] At step 765, the UE 115 sends an SPC report or an indication that SPC information is available to the second MN 105B.

[0146] At step 770, the second MN 105B sends a UE information request to the UE 115 based on receiving the indication that the SPC report is available. In some aspects, the information request may include a UEInformationRequest message that includes or indicates an SPC report request. In some aspects, the UEInformationRequest message may include an RRC message or an IE.

[0147] At step 775, the UE 115 sends a UE information response or report to the second MN 105B based on the information request sent at step 770. In some aspects, the UE information response includes a UEInformationResponse message that includes or indicates an SPC report. In some aspects, the SPC report may include information associated with a PScell ​​change. In some aspects, the UEInformationResponse message may include an RRC message or IE.

[0148] At step 780, the second MN 105B sends an SPC report to the first MN 105A. In some aspects, the SPC report may include or indicate at least a portion of the SPC information included in the UE Information Response sent at step 775.

[0149] In some aspects, based on the SPC report, the first MN 105A performs one or more network optimizations as explained above with respect to procedures 400 and / or 500, for example.

[0150] In some aspects, the first MN 105A may correlate information from the SPC report with the SCG fault information and use the correlated information to perform network optimization. In some aspects, the first MN 105A may associate the SPC report with the SCG fault information based on a UE context associated with the SPC report and the SCG fault information. In other instances, the UE context may not be available. For example, the first MN 105A may periodically delete the UE context so that the SPC report and the SCG fault information may not be associated through the UE context. In some aspects, the first MN 105A may be configured to associate the SPC report with the SCG fault information based on one or more other identifiers or indicators in at least one of the SPC report and / or the SCG fault information.

[0151] For example, in some aspects, the SCG fault information may include an SPC report indicator indicating that an SPC report has been transmitted to the network for handover and / or SN change. In another example, the SCG fault information may include an SPC report indicator indicating that there is an SPC report associated with the handover. In another example, the SPC report and the SCG fault information may include or indicate the same C-RNTI. In another aspect, the first MN 105A may associate the SCG fault information with the SPC report based on the associated timestamps of the SCG fault information and the SPC report. For example, the first MN 105A may determine that the SPC report is associated with the SCG fault information received within a time threshold of the SPC report. In another aspect, if the SPC report has not been transmitted by the time the SCG fault information is generated, the first MN 105A may merge the SPC report with the SCG fault information. In another aspect, if the SCG fault information has not been transmitted by the time the SPC report is generated, the first MN 105A may merge the SCG fault information with the SPC report. In another aspect, if the SCG failure occurs within a certain time window after the SPC report is generated, the first MN 105A may discard the SPC report. In another aspect, the UE 115 may report to the SPC and add a tag or reference indicator to the SCG failure information. The reference indicator may be used to associate the SPC report with the SCG failure information.

[0152] Figure 8 1 is a signaling diagram illustrating a PScell ​​change procedure 800 facilitated, initiated, and / or otherwise controlled by an SN according to some aspects of the present disclosure. The PScell ​​change procedure 800 may include MN 105A, S-SN 105C, T-SN 105D, UE 115, which may be reference Figures 1A to 2An example of a corresponding device described. In some examples, the PScell ​​change procedure 800 can implement various aspects of the wireless communication systems 100 and 200. For example, the MN 105A, the S-SN 105C, the T-SN 105D, and the UE 115 can support a PScell ​​change procedure, wherein the SN initiates a PScell ​​change and at least partially participates in the configuration of the UE 115 to determine a successful PScell ​​change and / or for a PScell ​​change report. The procedure 800 may also include a mechanism for reporting SCG failure information and associating it with SPC information. As illustrated, the PScell ​​change procedure 800 includes several enumeration steps, but an implementation of the PScell ​​change procedure 800 may include additional steps before, after, and between these enumeration steps. In some implementations, one or more of these enumeration steps may be omitted or performed in a different order. In the following description of the PScell ​​change procedure 800, operations between the MN 105A, S-SN 105C, T-SN 105D and / or UE 115 may be performed in a different order than the exemplary order shown or at different times. Certain operations may also be excluded from the PScell ​​change procedure 800, or other operations may be added to the PScell ​​change procedure 800.

[0153] At step 805, the S-SN 105C sends an SN change required message, and the first MN 105A receives the SN change required message, so that the MN 105A proceeds with SN addition, release, or other SN modification. In another aspect, the SN change required message may include or indicate one or more SPC configuration parameters. For example, the SN change required message may include a first portion of the SPC configuration. The S-SN 105C may determine and indicate at least one timer value or threshold in the SN change required message. For example, the S-SN 105C may determine and indicate at least one of a T310 timer value or threshold, and / or a T312 timer value or threshold in the SN change required message.

[0154] At step 810, the first MN 105A sends an SN add request to the T-SN 105D based on the SN change required message received from the S-SN 105C. In some aspects, sending the SN add request may include sending an Xn message or signal indicating the SN add request. In some aspects, the SN add request message may provide or indicate RRC and / or data radio bearer (DRB) configuration information for changing the SN. In some aspects, the first MN 105A may send the SN add request based on one or more reports and / or measurements obtained by the UE 115. At this point, the UE 115 may obtain one or more channel measurements of the primary and secondary cell group cells (PScell) facilitated by the S-SN 105C. The UE 115 may send a report indicating the channel measurement to the first MN 105A, the S-SN 105C, and / or any other network node or device. For example, the UE 115 may send a channel state information (CSI) report to the first MN 105A and / or to the S-SN 105C based on the channel measurement. A network node such as the first MN 105A may determine to perform a PScell ​​change based on the report.

[0155] At step 815, the T-SN 105D sends an SN add confirmation to the first MN 105A. In some aspects, the SN add confirmation may include an Xn message. In some aspects, the SN add confirmation may include information for allocating resources, providing SCG resource configuration, and / or for providing any other suitable information. In some aspects, the SN add confirmation message may include one or more SPC configuration parameters. In this regard, the PSC configuration may include a second portion of the SPC configuration. For example, in some aspects, the SN add request confirmation message may include or indicate a T304 time value or threshold.

[0156] At step 820, the first MN 105A sends an RRCReconfiguration message to the UE 115. The RRCReconfiguration message may include or indicate an SPC configuration. In some aspects, the SPC configuration may include an SPC-Config. In some aspects, the SPC-Config may include or indicate information for a PScell ​​change. For example, the SPC configuration may indicate a combination of SPC configuration parameters determined by the S-SN 105C and / or the T-SN 105D and indicated by the SN Change Required message sent at step 805 and / or the SN Add Request Confirmation message sent at step 815. In another aspect, the first MN 105A may determine one or more additional SPC configuration parameters to be included in the SPC-Config. Thus, the first MN 105A may combine or aggregate different portions of the SPC configuration from the S-SN 105C and / or the T-SN 105D and any SPC configuration parameters determined by the first MN 105A for the SPC-Config.

[0157] At step 825, the UE 115 determines that one or more trigger conditions have been met for the PScell ​​change based on the SPC configuration sent at step 825. In some aspects, the condition may be based on a timer value or threshold indicated in the SPC configuration. For example, the UE 115 may determine that the PScell ​​change is successful based on one or more of a T304 threshold, a T310 threshold, and / or a T312 threshold.

[0158] At step 830, the UE 115 sends an RRC reconfiguration complete message to the first MN 105A based on the SPC configuration and the determination of step 825. The RRC reconfiguration complete message may include or indicate that successful PScell ​​change information is available. For example, the RRC reconfiguration complete message may include or indicate a successPSCellChange-InfoAvailable field or tag, which indicates to the network that successful PScell ​​change information is available. In some aspects, the successful PScell ​​change information may include sending a UCI indicating that successful PScell ​​change information is available to the first MN 105A. In other aspects, the successful PScell ​​change information may be carried and / or indicated in an RRC message and / or a medium access control-control element (MAC-CE).

[0159] At step 835, the first MN 105A sends an SN change confirmation to the S-SN 105C. In some aspects, the SN change confirmation comprises an Xn message.

[0160] At step 840, the first MN 105A sends an SN reconfiguration complete message to the T-SN 105D. In some aspects, sending the SN reconfiguration complete message includes sending an Xn message including or indicating the SN reconfiguration complete message.

[0161] At step 845, the UE 115 determines or detects an SCG failure at the T-SN. In some aspects, the SCG failure may occur before the PScell ​​change has been completed. In some aspects, detecting the SCG failure may include determining that one or more signals or messages were not successfully received. In another aspect, determining the SCG failure may include determining or detecting a radio link failure, a failure of SCG reconfiguration, an SCG integrity failure, exceeding a maximum uplink transmit timing difference, a random access failure, and / or any other suitable method of detecting an SCG failure.

[0162] At step 850, based on detecting the SCG failure, the UE 115 sends SCG failure information to the first MN 105A. In some aspects, the SCG failure information includes or indicates information associated with the SCG failure, such as the failure type or condition that caused the SCG failure. In some aspects, the failure type may include T310 timer expiration, random access problem, synchronization reconfiguration failure, SRB3 integrity failure, and / or any other relevant failure type. In some aspects, the network may use the SCG failure information to modify or update subsequent SCG configurations.

[0163] At step 855, the first MN 105A sends an SCG failure report to the S-SN 105C. In some aspects, the SCG failure report sent at step 855 includes an Xn message indicating the SCG failure information sent at step 850.

[0164] At step 860, the first MN 105A sends an information request to the UE 115 based on the SCG failure information sent at step 850. In some aspects, the information request may include a UEInformationRequest message that includes or indicates an SPC report request. In some aspects, the UEInformationRequest message may include an RRC message or an IE.

[0165] At step 865, the UE 115 sends a UE information response or report to the first MN 105A based on the information request sent at step 860. In some aspects, the UE information response includes a UEInformationResponse message that includes or indicates an SPC report. In some aspects, the SPC report may include information associated with the PScell ​​change. In some aspects, the UEInformationResponse message may include an RRC message or IE.

[0166] At step 870, the first MN 105A sends an SPC report to the S-SN 105C. In some aspects, the SPC report may include an Xn message indicating the SPC information sent at step 865.

[0167] At step 875, based on the SPC report, the MN 105A performs one or more network optimizations.

[0168] In some aspects, the S-SN 105C may correlate information from the SPC report with the SCG fault information and use the correlated information to perform network optimization. In some aspects, the S-SN 105C may correlate the SPC report with the SCG fault information based on a UE context associated with the SPC report and the SCG fault information. In other instances, the UE context may not be available. For example, the S-SN 105C may periodically delete the UE context so that the SPC report and the SCG fault information may not be associated through the UE context. In some aspects, the S-SN 105C may be configured to correlate the SPC report with the SCG fault information based on one or more other identifiers or indicators in at least one of the SPC report and / or the SCG fault information.

[0169] For example, in some aspects, the SCG fault information may include an SPC report indicator indicating that an SPC report has been transmitted to the network for handover and / or SN change. In another example, the SCG fault information may include an SPC report indicator indicating that there is an SPC report associated with the handover. In another example, the SPC report and the SCG fault information may include or indicate the same C-RNTI. In another aspect, the S-SN 105C may associate the SCG fault information with the SPC report based on the associated timestamps of the SCG fault information and the SPC report. For example, the S-SN 105C may determine that the SPC report is associated with the SCG fault information received within a time threshold of the SPC report. In another aspect, if the SPC report has not been transmitted by the time the SCG fault information is generated, the S-SN 105C may merge the SPC report with the SCG fault information. In another aspect, if the SCG fault information has not been transmitted by the time the SPC report is generated, the S-SN 105C may merge the SCG fault information with the SPC report. In another aspect, if the SCG failure occurs within a certain time window after the SPC report is generated, the S-SN 105C may discard the SPC report. In another aspect, the UE 115 may report to the SPC and add a tag or reference indicator to the SCG failure information. The reference indicator may be used to associate the SPC report with the SCG failure information.

[0170] Fig. 91 is a signaling diagram illustrating a PScell ​​change procedure 900 facilitated, initiated, and / or otherwise controlled by an SN according to some aspects of the present disclosure. The PScell ​​change procedure 900 may include MN 105A, S-SN 105C, T-SN 105D, UE 115, which may be reference Figures 1A to 2 Examples of corresponding devices described. In some examples, the PScell ​​change procedure 900 can implement various aspects of the wireless communication systems 100 and 200. For example, the MN 105A, the S-SN 105C, the T-SN 105D and the UE 115 can support the PScell ​​change procedure, wherein the SN initiates the PScell ​​change and at least partially participates in the configuration of the UE 115 to determine the successful PScell ​​change and / or for the PScell ​​change report. The procedure 900 may also include a mechanism for reporting SCG failure information and associating it with SPC information. In addition, the process 900 may involve initiating, resuming or otherwise performing a handover (HO) procedure. As illustrated, the PScell ​​change procedure 900 includes several enumeration steps, but the implementation of the PScell ​​change procedure 900 may include additional steps before, after and between these enumeration steps. In some embodiments, one or more of these enumeration steps may be omitted or performed in a different order. In the following description of the PScell ​​change procedure 900, operations between the MN 105A, S-SN 105C, T-SN 105D and / or UE 115 may be performed in a different order than the exemplary order shown or at different times. Certain operations may also be excluded from the PScell ​​change procedure 900, or other operations may be added to the PScell ​​change procedure 900.

[0171] At step 905, the S-SN 105C sends an SN change required message, and the first MN 105A receives the SN change required message, so that the MN 105A proceeds with SN addition, release, or other SN modification. In another aspect, the SN change required message may include or indicate one or more SPC configuration parameters. For example, the SN change required message may include a first portion of the SPC configuration. The S-SN 105C may determine and indicate at least one timer value or threshold in the SN change required message. For example, the S-SN 105C may determine and indicate at least one of a T310 timer value or threshold, and / or a T312 timer value or threshold in the SN change required message.

[0172] At step 910, the first MN 105A sends an SN add request to the T-SN 105D based on the SN change required message received from the S-SN 105C. In some aspects, sending the SN add request may include sending an Xn message or signal indicating the SN add request. In some aspects, the SN add request message may provide or indicate RRC and / or data radio bearer (DRB) configuration information for changing the SN. In some aspects, the first MN 105A may send the SN add request based on one or more reports and / or measurements obtained by the UE 115. At this point, the UE 115 may obtain one or more channel measurements of the primary and secondary cell group cells (PScell) facilitated by the S-SN 105C. The UE 115 may send a report indicating the channel measurement to the first MN 105A, the S-SN 105C, and / or any other network node or device. For example, the UE 115 may send a channel state information (CSI) report to the first MN 105A and / or to the S-SN 105C based on the channel measurement. A network node such as the first MN 105A may determine to perform a PScell ​​change based on the report.

[0173] At step 915, the T-SN 105D sends an SN add confirmation to the first MN 105A. In some aspects, the SN add confirmation may include an Xn message. In some aspects, the SN add confirmation may include information for allocating resources, providing SCG resource configuration, and / or for providing any other suitable information. In some aspects, the SN add confirmation message may include one or more SPC configuration parameters. In this regard, the PSC configuration may include a second portion of the SPC configuration. For example, in some aspects, the SN add request confirmation message may include or indicate a T304 time value or threshold.

[0174] At step 920, the first MN 105A sends an RRCReconfiguration message to the UE 115. The RRCReconfiguration message may include or indicate an SPC configuration. In some aspects, the SPC configuration may include an SPC-Config. In some aspects, the SPC-Config may include or indicate information for a PScell ​​change. For example, the SPC configuration may indicate a combination of SPC configuration parameters determined by the S-SN 105C and / or the T-SN 105D and indicated by the SN Change Required message sent at step 905 and / or the SN Add Request Confirmation message sent at step 915. In another aspect, the first MN 105A may determine one or more additional SPC configuration parameters to be included in the SPC-Config. Thus, the first MN 105A may combine or aggregate different portions of the SPC configuration from the S-SN 105C and / or the T-SN 105D and any SPC configuration parameters determined by the first MN 105A for the SPC-Config.

[0175] At step 925, the UE 115 determines that one or more trigger conditions have been met for the PScell ​​change based on the SPC configuration sent at step 925. In some aspects, the condition may be based on a timer value or threshold indicated in the SPC configuration. For example, the UE 115 may determine that the PScell ​​change is successful based on one or more of a T304 threshold, a T310 threshold, and / or a T312 threshold.

[0176] At step 930, the UE 115 sends an RRC reconfiguration complete message to the first MN 105A based on the SPC configuration and the determination of step 925. The RRC reconfiguration complete message may include or indicate that successful PScell ​​change information is available. For example, the RRC reconfiguration complete message may include or indicate a successPSCellChange-InfoAvailable field or tag, which indicates to the network that successful PScell ​​change information is available. In some aspects, the successful PScell ​​change information may include sending a UCI indicating that successful PScell ​​change information is available to the first MN 105A. In other aspects, the successful PScell ​​change information may be carried and / or indicated in an RRC message and / or a medium access control-control element (MAC-CE).

[0177] At step 935, the first MN 105A sends an SN change confirmation to the S-SN 105C. In some aspects, the SN change confirmation comprises an Xn message.

[0178] At step 940, the first MN 105A sends an SN reconfiguration complete message to the T-SN 105D. In some aspects, sending the SN reconfiguration complete message includes sending an Xn message including or indicating the SN reconfiguration complete message.

[0179] At step 945, the UE 115 determines or detects an SCG failure at the T-SN. In some aspects, the SCG failure may occur before the PScell ​​change has been completed. In some aspects, detecting the SCG failure may include determining that one or more signals or messages were not successfully received. In another aspect, determining the SCG failure may include determining or detecting a radio link failure, a failure of SCG reconfiguration, an SCG integrity failure, exceeding a maximum uplink transmit timing difference, a random access failure, and / or any other suitable method of detecting an SCG failure.

[0180] At step 950, based on detecting the SCG failure, the UE 115 sends SCG failure information to the first MN 105A. In some aspects, the SCG failure information includes or indicates information associated with the SCG failure, such as the failure type or condition that caused the SCG failure. In some aspects, the failure type may include T310 timer expiration, random access problem, synchronization reconfiguration failure, SRB3 integrity failure, and / or any other relevant failure type. In some aspects, the network may use the SCG failure information to modify or update subsequent SCG configurations.

[0181] At step 955, the first MN 105A sends an SCG failure report to the S-SN 105C. In some aspects, the SCG failure report sent at step 955 includes an Xn message indicating the SCG failure information sent at step 950.

[0182] At step 960, the UE 115 and the second MN 105B perform a handover (HO) procedure from the first MN 105A to the second MN 105B. In some aspects, performing the HO may include obtaining a measurement report from the UE 115, sending a HO request message to the second MN 105B, receiving a HO request confirmation message from the second MN 105B, sending an RRC reconfiguration message to the UE 115, performing a random access procedure; and / or receiving an RRCReconfigurationComplete message from the UE 115.

[0183] At step 965, the UE 115 sends an SPC report or an indication that SPC information is available to the second MN 105B.

[0184] At step 970, the second MN 105B sends a UE information request to the UE 115 based on receiving the indication that the SPC report is available. In some aspects, the information request may include a UEInformationRequest message that includes or indicates an SPC report request. In some aspects, the UEInformationRequest message may include an RRC message or an IE.

[0185] At step 975, the UE 115 sends a UE information response or report to the second MN 105B based on the information request sent at step 970. In some aspects, the UE information response includes a UEInformationResponse message that includes or indicates an SPC report. In some aspects, the SPC report may include information associated with a PScell ​​change. In some aspects, the UEInformationResponse message may include an RRC message or IE.

[0186] At step 980, the second MN 105B sends an SPC report to the S-SN 105C. In some aspects, the SPC report may include or indicate at least a portion of the SPC information included in the UE Information Response sent at step 975.

[0187] In some aspects, the S-SN 105C may correlate information from the SPC report with the SCG fault information and use the correlated information to perform network optimization. In some aspects, the S-SN 105C may correlate the SPC report with the SCG fault information based on a UE context associated with the SPC report and the SCG fault information. In other instances, the UE context may not be available. For example, the S-SN 105C may periodically delete the UE context so that the SPC report and the SCG fault information may not be associated through the UE context. In some aspects, the S-SN 105C may be configured to correlate the SPC report with the SCG fault information based on one or more other identifiers or indicators in at least one of the SPC report and / or the SCG fault information.

[0188] For example, in some aspects, the SCG fault information may include an SPC report indicator indicating that an SPC report has been transmitted to the network for handover and / or SN change. In another example, the SCG fault information may include an SPC report indicator indicating that there is an SPC report associated with the handover. In another example, the SPC report and the SCG fault information may include or indicate the same C-RNTI. In another aspect, the S-SN 105C may associate the SCG fault information with the SPC report based on the associated timestamps of the SCG fault information and the SPC report. For example, the S-SN 105C may determine that the SPC report is associated with the SCG fault information received within a time threshold of the SPC report. In another aspect, if the SPC report has not been transmitted by the time the SCG fault information is generated, the S-SN 105C may merge the SPC report with the SCG fault information. In another aspect, if the SCG fault information has not been transmitted by the time the SPC report is generated, the S-SN 105C may merge the SCG fault information with the SPC report. In another aspect, if the SCG failure occurs within a certain time window after the SPC report is generated, the S-SN 105C may discard the SPC report. In another aspect, the UE 115 may report to the SPC and add a tag or reference indicator to the SCG failure information. The reference indicator may be used to associate the SPC report with the SCG failure information.

[0189] Fig.10 105A, SN 105C, and UE 115, which may be reference MN ... Figures 1A to 2Examples of corresponding devices described. In some examples, the PScell ​​change procedure 1000 can implement various aspects of the wireless communication systems 100 and 200. For example, the MN 105A, the SN 105C, and the UE 115 can support a PScell ​​change procedure in which the SN 105C configures the UE 115 to determine a successful PScell ​​change and / or for a PScell ​​change report. As illustrated, the PScell ​​change procedure 1000 includes several enumeration steps, but an implementation of the PScell ​​change procedure 1000 may include additional steps before, after, and between these enumeration steps. In some implementations, one or more of these enumeration steps may be omitted or performed in a different order. In the following description of the PScell ​​change procedure 1000, operations between the MN 105A, the SN 105C, and / or the UE 115 may be sent in an order different from the exemplary order shown or at different times. Certain operations may also be excluded from the PScell ​​change procedure 1000 , or other operations may be added to the PScell ​​change procedure 1000 .

[0190] At step 1005, SN 105C sends an RRCReconfiguration message to UE 115. The RRCReconfiguration message may include or indicate a successful PScell ​​change (SPC) configuration. In some aspects, the SPC configuration may include an SPC-Config. In some aspects, the SPC-Config may include or indicate information for the PScell ​​change. For example, the SPC configuration may indicate one or more triggering events and / or conditions to determine whether the PScell ​​change is successful. In some aspects, the SPC configuration may include or indicate one or more timer values ​​or other thresholds that the UE 115 may use to determine whether the PScell ​​change is successful. For example, the SPC configuration may include at least one of a T304 threshold, a T310 threshold, and / or a T312 threshold. In the illustrated example, the SN 105C may autonomously configure the SPC configuration.

[0191] At step 1010, the UE 115 sends an RRC reconfiguration complete message to the SN 105C based on the SPC configuration. The RRC reconfiguration complete message may include or indicate that successful PScell ​​change information is available. For example, the RRC reconfiguration complete message may include or indicate a successPSCellChange-InfoAvailable field or tag, which indicates to the network that successful PScell ​​change information is available. In some aspects, the successful PScell ​​change information may include sending a UCI to the SN 105C indicating that successful PScell ​​change information is available. In other aspects, the successful PScell ​​change information may be carried and / or indicated in an RRC message and / or a medium access control-control element (MAC-CE).

[0192] At step 1015, the SN 105C and the UE 115 perform a random access procedure to change the PScell ​​or configuration within the SN. In some aspects, the random access procedure includes adding, modifying or releasing one SCG Scell ​​and / or releasing, modifying or adding another SCG Scell.

[0193] In procedure 1000, there may be at least two options for reporting SPC information to SN 105C. The first option is shown as step 1020. Dashed lines represent optional or alternative steps, where step 1025 is also optional or alternative to step 1020. In step 1020, UE 115 sends an SPC report to MN 105A, and MN 105A forwards the SPC report to SN 105C. In some aspects, step 1020 includes sending an UL signal from UE 115 to MN 105A, and MN 105A sends an Xn message indicating the SPC report to SN 105C. For example, step 1020 may include MN 105A and / or SN 105C sending a UE Information Request for an SPC report to UE 115, and UE 115 sending a UE Information Response to MN 105A based on the request, wherein the UE Information Response includes the SPC report. The MN 105A may then send or forward the SPC information in the SPC report to the SN 105C in an Xn message.In some aspects, the UE 115 may send the SPC report to the MN 105A via SRB1.

[0194] In step 1025 (which may be optional or alternative as described above), UE 115 sends the SPC report directly to SN 105C. In some aspects, step 1025 may include UE 115 sending the SPC report via a UL RRC message. In some aspects, if SRB3 is available, UE 115 may send the SPC report via SRB3.

[0195] Fig.11 105A, S-SN 105C, T-SN 105D, UE 115, which may be reference 106. Figure 1A to Figure 2 Examples of corresponding devices described. In some examples, the PScell ​​change procedure 1100 can implement various aspects of the wireless communication systems 100 and 200. For example, the MN 105A, the S-SN 105C, the T-SN 105D and the UE 115 can support a PScell ​​change procedure in which the MN configures the UE 115 to determine a successful PScell ​​change and / or for a PScell ​​change report. As illustrated, the PScell ​​change procedure 1100 includes several enumeration steps, but the implementation of the PScell ​​change procedure 1100 may include additional steps before, after and between these enumeration steps. In some implementations, one or more of these enumeration steps may be omitted or performed in a different order. In the following description of the PScell ​​change procedure 1100, the operations between the MN 105A, the S-SN 105C, the T-SN 105D and / or the UE 115 may be sent in an order different from the exemplary order shown or at different times. Certain operations may also be excluded from the PScell ​​change procedure 1100 , or other operations may be added to the PScell ​​change procedure 1100 .

[0196] At step 1105, the first MN 105A sends a handover (HO) request to the second MN 105B. In some aspects, the HO request may include an Xn message.

[0197] At step 1110, the second MN 105B sends an SN add request to the T-SN 105D. In some aspects, sending the SN add request may include sending an Xn message or signal indicating the SN add request. In some aspects, the SN add request message may provide or indicate RRC and / or data radio bearer (DRB) configuration information for changing the SN. In some aspects, the first MN 105A may send the SN add request based on one or more reports and / or measurements obtained by the UE 115. At this point, the UE 115 may obtain one or more channel measurements of the primary and secondary cell group cells (PScells) facilitated by the S-SN 105C. The UE 115 may send a report indicating the channel measurement to the first MN 105A, the S-SN 105C, and / or any other network node or device. For example, the UE 115 may send a channel state information (CSI) report to the first MN 105A and / or to the S-SN 105C based on the channel measurement. A network node such as the first MN 105A may determine to perform a PScell ​​change based on the report.

[0198] At step 1115, the T-SN 105D sends an SN add confirmation to the second MN 105B. In some aspects, the SN add confirmation may include an Xn message. In some aspects, the SN add confirmation may include information for allocating resources, providing SCG resource configuration, and / or for providing any other suitable information.

[0199] At step 1120, the second MN 105B sends a HO Request Confirmation to the first MN 105A. In some aspects, the HO Request Confirmation may include an Xn message.

[0200] At step 1125, the first MN 105A sends an SN release request to the S-SN 105C, requesting the S-SN 105C to release or terminate communication with the UE 115. In some aspects, the SN release request may include an Xn message.

[0201] At step 1130, the S-SN 105C sends an SN release request confirmation to the first MN 105A based on the SN release request. In some aspects, the SN release request confirmation may include an Xn message.

[0202] At step 1135, the first MN 105A sends an RRCReconfiguration message to the UE 115. The RRCReconfiguration message may include or indicate a successful PScell ​​change (SPC) configuration. In some aspects, the SPC configuration may include an SPC-Config. In some aspects, the SPC-Config may include or indicate information for the PScell ​​change. For example, the SPC configuration may indicate one or more triggering events and / or conditions to determine whether the PScell ​​change is successful. In some aspects, the SPC configuration may include or indicate one or more timer values ​​or other thresholds that the UE 115 may use to determine whether the PScell ​​change is successful. For example, the SPC configuration may include at least one of a T304 threshold, a T310 threshold, and / or a T312 threshold. In the illustrated example, the MN 105A may autonomously configure the SPC configuration. However, in other examples (e.g., such as Figure 5 exemplified), the SPC configuration may be configured and / or determined by one or more other network nodes (such as S-SN 105C and / or T-SN 105D).

[0203] At step 1140, the UE 115 determines that one or more trigger conditions have been met for a successful PScell ​​change based on the SPC configuration sent at step 1135, and one or more trigger conditions have been met for a HO procedure initiated with the HO request sent at step 1105. In some aspects, the condition may be based on a timer value or threshold indicated in the SPC configuration and / or in the HO request. For example, the UE 115 may determine that the PScell ​​change is successful based on one or more of a T304 threshold, a T310 threshold, and / or a T312 threshold.

[0204] At step 1145, the UE 115 sends an RRC reconfiguration complete message to the second MN 105B based on the determination of step 1140. At this point, the RRC reconfiguration complete message is sent to the second MN 105B and may not be sent to the first MN 105A that initiated the SN release of the S-SN 105C. The RRC reconfiguration complete message may include or indicate that successful PScell ​​change information is available. For example, the RRC reconfiguration complete message may include or indicate a successPSCellChange-InfoAvailable field or tag, which indicates to the network that successful PScell ​​change information is available. In some aspects, the successful PScell ​​change information may include sending a UCI indicating that successful PScell ​​change information is available to the MN 105A. In other aspects, the successful PScell ​​change information may be carried and / or indicated in an RRC message and / or a medium access control-control element (MAC-CE). In addition, the RRC reconfiguration complete message may include or indicate that successful HO information is available. For example, the RRC reconfiguration complete message may include or indicate a successHO-InfoAvailable field or tag, which indicates to the network that successful HO information is available.

[0205] At step 1150, the second MN 105B sends an SN reconfiguration complete message to the T-SN 105D based on the RRC reconfiguration complete message. In some aspects, the SN reconfiguration complete message includes sending an Xn message including or indicating the SN reconfiguration complete message.

[0206] At step 1155, the second MN 105B sends an information request to the UE 115 based on the indication that the PScell ​​change information is available and the indication that the HO information is available. In some aspects, the information request may include a UEInformationRequest message that includes or indicates an SPC report request and a successful HO report request. In some aspects, the UEInformationRequest message may include an RRC message or IE.

[0207] At step 1160, the UE 115 sends a UE information response or report to the second MN 105B based on the information request sent at step 1140. In some aspects, the UE information response includes a UEInformationResponse message that includes or indicates an SPC report and a successful HO report. In some aspects, the SPC report may include information associated with a PScell ​​change. The successful HO report may include information associated with the HO. In some aspects, the UEInformationResponse message may include an RRC message or IE. In some aspects, based on the SPC report and / or the successful HO report, the second MN 105B performs one or more network optimizations.

[0208] Fig.12 105C, T-SN 105D, UE 115, which may be reference SNs 105A, 105B, 105C, 105D, and 105D may be included in the PScell ​​change procedure 1200. Figure 1A to Figure 2 An example of the corresponding device described. In some examples, the PScell ​​change procedure 1200 can implement various aspects of the wireless communication systems 100 and 200. For example, the MN 105A, the S-SN 105C, the T-SN 105D and the UE 115 can support the PScell ​​change procedure, wherein the SN initiates the PScell ​​change and at least partially participates in the configuration of the UE 115 to determine the successful PScell ​​change and / or for the PScell ​​change report. The procedure 1200 may also include a mechanism for reporting SCG failure information and additional SCG failure information. As illustrated, the PScell ​​change procedure 1200 includes several enumeration steps, but the implementation of the PScell ​​change procedure 1200 may include additional steps before, after, and between these enumeration steps. In some embodiments, one or more of these enumeration steps may be omitted or performed in a different order. In the following description of the PScell ​​change procedure 1200, operations between the MN 105A, S-SN 105C, T-SN 105D and / or UE 115 may be performed in a different order than the exemplary order shown or at different times. Certain operations may also be excluded from the PScell ​​change procedure 1200, or other operations may be added to the PScell ​​change procedure 1200.

[0209] At step 1205, the S-SN 105C sends an SN change required message, and the first MN 105A receives the SN change required message, so that the MN 105A proceeds with SN addition, release, or other SN modification. In another aspect, the SN change required message may include or indicate one or more SPC configuration parameters. For example, the SN change required message may include a first portion of the SPC configuration. The S-SN 105C may determine and indicate at least one timer value or threshold in the SN change required message. For example, the S-SN 105C may determine and indicate at least one of a T310 timer value or threshold, and / or a T312 timer value or threshold in the SN change required message.

[0210] At step 1210, the first MN 105A sends an SN add request to the T-SN 105D based on the SN change required message received from the S-SN 105C. In some aspects, sending the SN add request may include sending an Xn message or signal indicating the SN add request. In some aspects, the SN add request message may provide or indicate RRC and / or data radio bearer (DRB) configuration information for changing the SN. In some aspects, the first MN 105A may send the SN add request based on one or more reports and / or measurements obtained by the UE 115. At this point, the UE 115 may obtain one or more channel measurements of the primary and secondary cell group cells (PScell) facilitated by the S-SN 105C. The UE 115 may send a report indicating the channel measurement to the first MN 105A, the S-SN 105C, and / or any other network node or device. For example, the UE 115 may send a channel state information (CSI) report to the first MN 105A and / or to the S-SN 105C based on the channel measurement. A network node such as the first MN 105A may determine to perform a PScell ​​change based on the report.

[0211] At step 1215, the T-SN 105D sends an SN add confirmation to the first MN 105A. In some aspects, the SN add confirmation may include an Xn message. In some aspects, the SN add confirmation may include information for allocating resources, providing SCG resource configuration, and / or for providing any other suitable information. In some aspects, the SN add confirmation message may include one or more SPC configuration parameters. In this regard, the PSC configuration may include a second portion of the SPC configuration. For example, in some aspects, the SN add request confirmation message may include or indicate a T304 time value or threshold.

[0212] At step 1220, the first MN 105A sends an RRC reconfiguration message to the UE 115. The RRC reconfiguration message may include or indicate an SPC configuration. In some aspects, the SPC configuration may include an SPC-Config. In some aspects, the SPC-Config may include or indicate information for a PScell ​​change. For example, the SPC configuration may indicate a combination of SPC configuration parameters determined by the S-SN 105C and / or the T-SN 105D and indicated by the SN Change Required message sent at step 1205 and / or the SN Add Request Confirmation message sent at step 1215. In another aspect, the first MN 105A may determine one or more additional SPC configuration parameters to be included in the SPC-Config. Thus, the first MN 105A may combine or aggregate different portions of the SPC configuration from the S-SN 105C and / or the T-SN 105D and any SPC configuration parameters determined by the first MN 105A for the SPC-Config.

[0213] At step 1225, the UE 115 sends an RRC reconfiguration complete message to the first MN 105A. In some instances, sending the RRC reconfiguration complete message may be based on determining that one or more trigger conditions for a successful PScell ​​change have been met. The RRC reconfiguration complete message may include or indicate that successful PScell ​​change information is available. For example, the RRC reconfiguration complete message may include or indicate a successPSCellChange-InfoAvailable field or tag, which indicates to the network that successful PScell ​​change information is available. In some aspects, the successful PScell ​​change information may include sending a UCI indicating that successful PScell ​​change information is available to the first MN 105A. In other aspects, the successful PScell ​​change information may be carried and / or indicated in an RRC message and / or a medium access control-control element (MAC-CE).

[0214] At step 1230, the first MN 105A sends an SN change confirmation to the S-SN 105C. In some aspects, the SN change confirmation comprises an Xn message.

[0215] At step 1235, the first MN 105A sends an SN reconfiguration complete message to the T-SN 105D. In some aspects, sending the SN reconfiguration complete message includes sending an Xn message including or indicating the SN reconfiguration complete message.

[0216] At step 1240, the UE 115 determines or detects an SCG failure at the T-SN 105D. In some aspects, the SCG failure may occur before the PScell ​​change has been completed. In some aspects, detecting the SCG failure may include determining that one or more signals or messages related to the PScell ​​change were not successfully received. In another aspect, determining the SCG failure may include determining or detecting a radio link failure, a failure of SCG reconfiguration, an SCG integrity failure, exceeding a maximum uplink transmit timing difference, a random access failure, and / or any other suitable method of detecting an SCG failure.

[0217] At step 1245, based on detecting the SCG failure, the UE 115 sends SCG failure information to the first MN 105A. In some aspects, the SCG failure information includes or indicates information associated with the SCG failure, such as the type of failure or condition that caused the SCG failure. In some aspects, the failure type may include T310 timer expiration, random access problem, synchronization reconfiguration failure, SRB3 integrity failure, and / or any other relevant failure type. In some aspects, the network may use the SCG failure information to modify or update subsequent SCG configurations. In some aspects, the SCG failure information may include an indicator that additional SCG failure information is available, as further discussed below.

[0218] At step 1250, the first MN 105A sends a SCG failure report to the S-SN 105C. In some aspects, the SCG failure report sent at step 1255 includes an Xn message indicating the SCG failure information sent at step 1250.

[0219] At step 1255, UE 115 stores the additional SCG failure information. In some aspects, UE 115 may store the additional SCG failure information in the VarSCGFailure-Report variable. In some aspects, as further explained below, the additional SCG failure information may be used to generate an additional SCG failure report. In some aspects, the additional SCG failure report may be similar to the SCG failure report sent at step 1250. The additional SCG failure information may include, for example, a first satisfying event performed by CPAC. At this point, there may be multiple event triggers for conditional reconfiguration. In some aspects, the first conditional event may include a channel condition (e.g., RSRP, RSRQ, SNR, etc.) that the conditional reconfiguration candidate (e.g., the target cell of the SCG) has a better configured offset than the serving Pcell and / or PScell. At this point, if the candidate RSRP, RSRQ and / or SNR exceeds the current serving Pcell or PScell ​​by the configured offset, the triggering event or condition may be satisfied. In another aspect, the second conditional event may include that the conditional reconfiguration candidate cell has a channel condition (e.g., RSRP, RSRQ, SNR, etc.) that is better than an absolute threshold. In another aspect, the third conditional event for conditional reconfiguration may include that the current serving Pcell and / or PScell ​​has a channel condition that drops below the first absolute threshold, and that the candidate cell has a channel condition that exceeds the second absolute threshold. In some instances, multiple conditional events may occur to trigger conditional reconfiguration. It may be beneficial for the network to receive information indicating which conditional events occur first to cause or trigger conditional reconfiguration. In another aspect, additional SCG fault information may include the time or duration between the fulfillment of different conditional events or triggering conditions. For example, additional SCG fault information may include or indicate the time between the occurrence of a first conditional event and the occurrence of a last conditional event. In another aspect, additional SCG fault information may include the time between the first conditional event and the second conditional event, and the time between the second conditional event and the occurrence of the last conditional event.

[0220] At step 1260, the first MN 105A sends an information request to the UE 115 based on the SCG failure information sent at step 1245 indicating that additional SCG failure information is available. In some aspects, the information request may include a UEInformationRequest message that includes or indicates an additional SCG failure information request. In some aspects, the UEInformationRequest message may include an RRC message or IE.

[0221] At step 1265, the UE 115 sends a UE information response or report to the first MN 105A based on the information request sent at step 1260. In some aspects, the UE information response includes a UEInformationResponse message that includes or indicates an additional SCG failure report. In some aspects, the UEInformationResponse message may include an RRC message or IE.

[0222] At step 1270, the first MN 105A sends an SCG failure report including the additional SCG failure information to the S-SN 105C. In some aspects, the SCG failure may include an Xn message indicating the SPC information sent at step 1265. In some aspects, the SCG failure report sent at step 1270 may have a format similar to or the same as the SCG failure report sent at step 1250. In other aspects, a new report or report format may be configured for reporting the additional SCG failure information.

[0223] In the illustrated example, UE 115 stores additional SCG fault information and reports the additional SCG fault information based on a request from the network. In another example, UE 115 may automatically report the additional SCG fault information rather than in response to a request for additional information. In another aspect, upon detecting a different SCG fault, the previously stored additional SCG fault information may be overwritten with the new additional SCG fault information. In some aspects, UE 115 may store the additional SCG fault information in a configured variable. In some aspects, UE 115 may store the additional SCG fault information for 24 hours, 48 ​​hours, 72 hours, or any other suitable amount of time that is longer or shorter. In another aspect, UE 115 may store the additional SCG fault information until it is retrieved.

[0224] In some aspects, UE 115 may indicate that additional SCG failure information is available via an RRC message. For example, UE 115 may use one or more of an RRCSetupComplete message, an RRCResumeComplete message, an RRCReestablishmentComplete message, and / or an RRCReconfigurationComplete message to indicate that SCG failure information is available.

[0225] At step 1275, based on the SPC report, the MN 105A performs one or more network optimizations.

[0226] In some aspects, the S-SN 105C may correlate information from the SPC report with the SCG fault information and use the correlated information to perform network optimization. In some aspects, the S-SN 105C may correlate the SPC report with the SCG fault information based on a UE context associated with the SPC report and the SCG fault information. In other instances, the UE context may not be available. For example, the S-SN 105C may periodically delete the UE context so that the SPC report and the SCG fault information may not be associated through the UE context. In some aspects, the S-SN 105C may be configured to correlate the SPC report with the SCG fault information based on one or more other identifiers or indicators in at least one of the SPC report and / or the SCG fault information.

[0227] For example, in some aspects, the SCG fault information may include an SPC report indicator indicating that an SPC report has been transmitted to the network for handover and / or SN change. In another example, the SCG fault information may include an SPC report indicator indicating that there is an SPC report associated with the handover. In another example, the SPC report and the SCG fault information may include or indicate the same C-RNTI. In another aspect, the S-SN 105C may associate the SCG fault information with the SPC report based on the associated timestamps of the SCG fault information and the SPC report. For example, the S-SN 105C may determine that the SPC report is associated with the SCG fault information received within a time threshold of the SPC report. In another aspect, if the SPC report has not been transmitted by the time the SCG fault information is generated, the S-SN 105C may merge the SPC report with the SCG fault information. In another aspect, if the SCG fault information has not been transmitted by the time the SPC report is generated, the S-SN 105C may merge the SCG fault information with the SPC report. In another aspect, if the SCG failure occurs within a certain time window after the SPC report is generated, the S-SN 105C may discard the SPC report. In another aspect, the UE 115 may report to the SPC and add a tag or reference indicator to the SCG failure information. The reference indicator may be used to associate the SPC report with the SCG failure information.

[0228] Fig.13 1 is a block diagram of an exemplary UE 1300 according to some aspects of the present disclosure. The UE 1300 may be Figure 1A UE 115 or Figure 2215 discussed in . As shown, UE 1300 may include a processor 1302, a memory 1304, a PScell ​​change module 1308, a transceiver 1310 including a modem subsystem 1312 and a radio frequency (RF) unit 1314, and one or more antennas 1316. These elements may communicate with each other directly or indirectly, for example, via one or more buses.

[0229] The processor 1302 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 1302 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0230] Memory 1304 may include cache memory (e.g., cache memory of processor 1302), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one aspect, memory 1304 includes a non-transitory computer-readable medium. Memory 1304 may store or have recorded thereon instructions 1306. Instructions 1306 may include instructions that, when executed by processor 1302, cause processor 1302 to perform various aspects of the present disclosure (e.g., Figures 1A to 4 and Figures 7 to 9 Instructions 1306 may also be referred to as program code. Program code may be used to cause the wireless communication device to perform these operations, for example, by causing one or more processors (such as processor 1302) to control or command the wireless communication device to do so. The terms "instructions" and "code" should be broadly interpreted to include any type of computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, procedures, etc. "Instructions" and "code" may include a single computer-readable statement or multiple computer-readable statements.

[0231] The PScell ​​change module 1308 may be implemented via hardware, software, or a combination thereof. For example, the PScell ​​change module 1308 may be implemented as a processor, circuit, and / or instructions 1306 stored in the memory 1304 and executed by the processor 1302. In some examples, the PScell ​​change module 1308 may be integrated within the modem subsystem 1312. For example, the PScell ​​change module 1308 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 1312.

[0232] The PScell ​​change module 1308 may be used in various aspects of the present disclosure, such as Figures 4 to 12 Aspects of the present invention. The PScell ​​change module 1308 may coordinate with the processor 1302 to obtain channel measurements of one or more cells in the master cell group (MCG) and / or the secondary cell group (SCG). The PScell ​​change module 1308 may also be configured to receive a successful PScell ​​change (SPC) report configuration and send an SPC report to the network based on the SPC report configuration. The PScell ​​change module 1308 may be configured to detect a successful PScell ​​change and send an SPC report based on the SPC report configuration and the detection of a successful PScell ​​change. In another aspect, the PScell ​​change module 1308 may be configured to detect an SCG failure during and / or after a PScell ​​change. The PScell ​​change module 1308 may be configured to detect an SCG failure based on one or more SCG failure conditions or events, such as expiration of a configured timer, a radio link failure, and / or any other suitable SCG failure condition. The PScell ​​change module 1308 may be configured to send an SCG failure report to one or more network nodes. The PScell ​​change module 1308 may be configured to store additional SCG failure information and report it to the network. For example, the PScell ​​change module 1308 may be configured to report the first occurrence of a triggering event or condition associated with an SCG failure and send an additional SCG failure report indicating additional SCG failure information to the network.

[0233] As shown, the transceiver 1310 may include a modem subsystem 1312 and an RF unit 1314. The transceiver 1310 may be configured to communicate bidirectionally with other devices, such as the BS 105. The modem subsystem 1312 may be configured to modulate and / or encode data from the memory 1304 and / or the PScell ​​change module 1308 according to a modulation and coding scheme (MCS) (e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional decoding scheme, a polarization decoding scheme, a digital beamforming scheme, etc.). The RF unit 1314 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data (e.g., uplink data, synchronization signals, SSB) from the modem subsystem 1312 (for outbound transmissions) or from another source (such as the UE 115 or the BS 105). The RF unit 1314 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 1310, the modem subsystem 1312 and the RF unit 1314 may be separate devices that are coupled together at the UE 115 to enable the UE 115 to communicate with other devices.

[0234] The RF unit 1314 may provide modulated and / or processed data, such as data packets (or more generally, data messages that may contain one or more data packets and other information), to the antenna 1316 for transmission to one or more other devices. The antenna 1316 may also receive data messages sent from other devices. The antenna 1316 may provide the received data messages for processing and / or demodulation at the transceiver 1310. The transceiver 1310 may provide the demodulated and decoded data (e.g., reference signals, synchronization signals, SSB) to the PScell ​​change module 1308 for processing. The antenna 1316 may include multiple antennas with similar or different designs in order to maintain multiple transmission links. The RF unit 1314 may configure the antenna 1316. In some aspects, the RF unit 1314 may include various RF components, such as a local oscillator (LO), an analog filter, and / or a mixer. The LO and the mixer may be configured based on a specific channel center frequency. The analog filter may be configured to have a specific passband depending on the channel BW. The RF components may be configured to operate in various power modes (eg, normal power mode, low power mode, power off mode) and may be switched between different power modes depending on the transmission and / or reception requirements at the UE 1300 .

[0235] In some aspects, the transceiver 1310 is configured to receive a measurement configuration from the BS, the measurement configuration comprising a first signal measurement offset and a plurality of predetermined parameters. In some aspects, the UE receives the measurement configuration in a radio resource control (RRC) message. The transceiver 1310 is also configured to communicate a measurement report with the BS in a first subband of the plurality of subbands, the measurement report comprising an indication of an occurrence of a specified measurement event for initiating a handover of the UE between the BS and one or more neighboring cells.

[0236] In one aspect, the UE 1300 may include multiple transceivers 1310 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 1300 may include a single transceiver 1310 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 1310 may include various components, where different combinations of components may implement different RATs.

[0237] Fig.14 is a block diagram of an exemplary network node 1400 according to some aspects of the present disclosure. The network node 1400 may be as described above in Figure 1A BS 105 in network 100 discussed in or as described above in Figure 2 14. As shown, the network node 1400 may include a processor 1402, a memory 1404, a PScell ​​change module 1408, a transceiver 1410 (which includes a modem subsystem 1412 and an RF unit 1414), and one or more antennas 1416. These elements may communicate with each other directly or indirectly, for example, via one or more buses.

[0238] The processor 1402 may have various features as a particular type of processor. For example, these features may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 1402 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0239] Memory 1404 may include cache memory (e.g., cache memory of processor 1402), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, memory 1404 may include non-transitory computer-readable media. Memory 1404 may store instructions 1406. Instructions 1406 may include instructions that, when executed by processor 1402, cause processor 1402 to perform operations described herein (e.g., Figures 1A to 4 and Figures 7 to 9 Instructions 1406 may also be referred to as code, which may be broadly interpreted to include any type of computer-readable statements, such as those described above with respect to Figure 3 discussed.

[0240] The PScell ​​change module 1408 may be implemented via hardware, software, or a combination thereof. For example, the PScell ​​change module 1408 may be implemented as a processor, circuit, and / or instructions 1406 stored in the memory 1404 and executed by the processor 1402. In some examples, the PScell ​​change module 1408 may be integrated within the modem subsystem 1412. For example, the PScell ​​change module 1408 may be implemented by a combination of software components (e.g., executed by a DSP or a general purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 1412.

[0241] The PScell ​​change module 1408 may be implemented via hardware, software, or a combination thereof. For example, the PScell ​​change module 1408 may be implemented as a processor, circuit, and / or instructions 1406 stored in the memory 1404 and executed by the processor 1402. In some examples, the BS may include the PScell ​​change module 1408.

[0242] The PScell ​​change module 1408 may be used in various aspects of the present disclosure, such as Figures 4 to 12Aspects of the present invention. The PScell ​​change module 1408 may coordinate with the processor 1302 to receive channel measurements from UEs of one or more cells in a primary cell group (MCG) and / or a secondary cell group (SCG). The PScell ​​change module 1408 may also be configured to send a successful PScell ​​change (SPC) report configuration and receive an SPC report from the UE based on the SPC report configuration. The PScell ​​change module 1408 may be configured to receive an SPC report from the UE, wherein the report is based on the SPC report configuration. In another aspect, the PScell ​​change module 1408 may be configured to receive an SCG fault report from the UE directly or via one or more other network nodes. The PScell ​​change module 1408 may be configured to store SCG fault information and / or SPC information. For example, the PScell ​​change module 1408 may be configured to report the first occurrence of a triggering event or condition associated with an SCG fault, and receive an additional SCG fault report indicating additional SCG fault information.

[0243] In some aspects, the PScell ​​change module 1408 may be configured to associate the SPC report with the SCG fault report based on the UE context associated with the SPC report and the SCG fault report. In another aspect, the PScell ​​change module 1408 may be configured to associate the SPC report with the SCG fault report based on one or more indicators in the SPC report and / or the SCG report. In another aspect, the PScell ​​change module 1408 may be configured to associate the SPC report with the SCG fault report based on the timing of the SPC report and / or the SCG report. In some aspects, the PScell ​​change module 1408 may be configured to configure the UE for SPC reporting. In some aspects, the SPC report configuration may indicate one or more timer thresholds (such as a T304 timer threshold, a T310 timer threshold, and / or a T312 timer threshold) for the UE to determine or detect a successful PScell ​​change. In other aspects, the PScell ​​change module 1408 may be configured to determine a portion of the SPC report configuration. In some aspects, the PScell ​​change module 1408 may be configured to aggregate SPC reporting configuration parameters determined by the PScell ​​change module 1408 and at least one other network node, and transmit an SPC reporting configuration including the aggregated SPC reporting parameters.

[0244] As shown, the transceiver 1410 may include a modem subsystem 1412 and an RF unit 1414. The transceiver 1410 may be configured to communicate bidirectionally with other devices (such as UE 115 and / or 500 and / or another core network element). The modem subsystem 1412 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC decoding scheme, a turbo decoding scheme, a convolutional decoding scheme, a polarization decoding scheme, a digital beamforming scheme, etc.). The RF unit 1414 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / encoded data (e.g., PDCCH, PDSCH, SSB, UE reporting configuration, network configuration based on machine learning, etc.) from the modem subsystem 1412 (for outbound transmission) or from another source (such as UE 115 and / or UE 500). The RF unit 1414 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 1410 , the modem subsystem 1412 and / or the RF unit 1414 may be separate devices that are coupled together at the BS 105 to enable the BS 105 to communicate with other devices.

[0245] The RF unit 1414 may provide modulated and / or processed data, such as data packets (or more generally, data messages that may include one or more data packets and other information), to the antenna 1416 for transmission to one or more other devices. For example, according to some aspects of the present disclosure, this may include the transmission of information to complete the attachment to the network and the communication with the pre-occupied UE 115 or 500. The antenna 1416 may also receive data messages sent from other devices and provide the received data messages for processing and / or demodulation at the transceiver 1410. The transceiver 1410 may provide the demodulated and decoded data (e.g., CBR reports and / or CR reports) to the PScell ​​change module 1408 for processing. The antenna 1416 may include multiple antennas of similar design or different designs to maintain multiple transmission links.

[0246] In an aspect, the network node 1400 may include multiple transceivers 1410 that implement different RATs (e.g., NR and LTE). In an aspect, the network node 1400 may include a single transceiver 1410 that implements multiple RATs (e.g., NR and LTE). In an aspect, the transceiver 1410 may include various components, where different combinations of components may implement different RATs.

[0247] Fig.151 is a flow chart of a wireless communication method 1500 according to some aspects of the present disclosure. Aspects of the method 1500 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for performing steps. For example, the wireless communication device may include a MN 105A, 105B or a SN 105C, 105D. For example, the wireless communication device may include a network node 1400, and the steps of the method 1500 may be performed using one or more components (such as a processor 1402, a memory 1404, a PScell ​​change module 1408, a transceiver 1410, a modem 1412, and one or more antennas 1416). As illustrated, the method 1500 includes a plurality of the enumerated steps, but aspects of the method 1500 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0248] In step 1510, the first network unit sends an indication of a change (SPC) of a primary and secondary group cell (PScell) associated with a user equipment (UE) to the second network unit. In some aspects, the first network unit includes a master node (MN). In another aspect, the first network unit includes a secondary node (SN). In some aspects, the SN may be a source SN (S-SN) or a target SN (T-SN). The second network unit may include an SN or a MN. In some aspects, if the first network unit is an MN, the second network unit may be an SN. In some aspects, sending the indication may include sending an Xn message including or carrying the indication. In some aspects, sending the indication of the SPC includes sending at least one of an SN change required message, an SN add request, an SN add request confirmation, an SN release request, and / or an SN release request confirmation. The first network unit may utilize one or more components (such as a processor 1402, a memory 1404, a PScell ​​change module 1408, a transceiver 1410, a modem 1412, and one or more antennas 1416) to perform the actions of step 1510.

[0249] At step 1520, the first network element sends a successful PScell ​​change report (SPC) configuration based on the indication of the PScell ​​change. In some examples, sending the SPC configuration may include sending an RRC message. For example, sending the SPC configuration may include sending an RRCReconfiguration message. In another aspect, sending the SPC configuration may include sending the configuration via an Xn message. In some aspects, sending the SPC configuration includes sending the SPC configuration directly from the MN to the UE. In another aspect, the SPC configuration may include sending the SPC configuration or at least a portion of the SPC configuration from the SN to the MN via an Xn message. The first network element may utilize one or more components (such as a processor 1402, a memory 1404, a PScell ​​change module 1408, a transceiver 1410, a modem 1412, and one or more antennas 1416) to perform the actions of step 1520.

[0250] At step 1530, the first network element receives an SPC report. In some aspects, the SPC report is based on an SPC configuration and SPC information associated with the UE. For example, in some aspects, the UE may obtain SPC information based on the SPC configuration. The SPC information may include, for example, a trigger event or condition being satisfied, associated with an SPC procedure. In some aspects, receiving the SPC report includes receiving the SPC report directly from the UE. In another aspect, receiving the SPC report includes receiving the SPC report via a network element (such as an MN or SN). In some aspects, receiving the SPC report may include receiving a UE information response including or indicating the SPC report. The UE information response may be sent by the UE in response to the UE receiving a UE information request. The UE information request may include or indicate a request for an SPC report. In another aspect, the first network element may be an SN and may receive the SPC report via the MN. The first network element may utilize one or more components (such as a processor 1402, a memory 1404, a PScell ​​change module 1408, a transceiver 1410, a modem 1412, and one or more antennas 1416) to perform the actions of step 1530.

[0251] In some aspects, the method 1500 also includes the first network element or another network element performing network optimization based on the SPC report. For example, in some aspects, the first network element or a different network element may update one or more timer thresholds associated with radio link monitoring (RLM) and / or beam fault detection (BFD) of the MCG and / or SCG. In another aspect, the network element may detect a near-failure scenario during a successful PScell ​​change and / or a successful handover (HO). In some aspects, the method 1500 also includes receiving an SCG fault report from the UE, wherein the SPC report is also received from the UE. The network element may perform network optimization based on the association of the SCG fault report with the SPC report.

[0252] In another aspect, the first network node receives an SPC report from a second MN different from the MN. In some aspects, performing network optimization is based on an association of the SCG failure report with a successful PScell ​​change report. In some aspects, the first MN or the second MN may perform network optimization.

[0253] In some aspects, sending an indication of the SPC to the second network element includes sending an SN add request message to the T-SN. In another aspect, sending the SPC reporting configuration includes sending an SPC-Config or an RRC message indicating the SPC-Config to the UE. In some aspects, the SPC reporting configuration indicates one or more triggering thresholds for one or more timers associated with the MCG and / or SCG.

[0254] In another aspect, the first network node includes a SN, and the SN sends an indication of the SPC by sending an SN change request to the MN. In some aspects, sending a successful PScell ​​change report configuration includes sending a first SPC report configuration to the MN, and receiving the SPC report includes receiving the SPC report from the MN. In some aspects, the SN change request indicates a threshold for a first timer. For example, the SN change request may include or indicate at least one of a T310 timer threshold and / or a T312 timer threshold. In some aspects, the SN determines the threshold. In another aspect, the MN may determine a second timer threshold. For example, the MN may determine at least one of a T304 timer threshold, a T310 timer threshold, and / or a T312 timer threshold. In some aspects, the MN may receive an SN change request indicating a first timer threshold, and may send an SPC configuration indicating a first timer threshold and a second timer threshold, so that the SN and the MN contribute to the SPC configuration.

[0255] In some aspects, method 1500 also includes receiving an SCG fault report. For example, the MN may receive the SCG fault report from the UE. In another aspect, the SN may receive the SCG fault report from the MN. In the SCG, the fault report may be based on the detection of an SCG fault. In some aspects, receiving the SCG fault report may include receiving an SCGFailureInformation information element from the UE. In another aspect, receiving the SCG fault report may include the SN receiving an Xn message indicating SCG fault information from the MN. In some aspects, the first network node performs network optimization based on the SCG fault information. In some aspects, the first network node performs an association between the SPC report and the SCG fault information, and performs network optimization based on the association. In another aspect, the first network may associate the SCG fault report with the SPC report based on one or more indicators included in the SCG fault report and / or the SPC report. For example, the SCG fault report may include a first indicator associated with the SPC report, the SPC report may include a second indicator associated with the SCG fault report, or a combination thereof.

[0256] Fig.16 1 is a flow chart of a wireless communication method 1600 according to some aspects of the present disclosure. Aspects of the method 1600 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for performing steps. For example, the wireless communication device may include a first MN 105A. The method 1600 may include Fig.11 One or more aspects of the illustrated procedure 1100. The first MN may include a network node 1400, and may utilize one or more components (such as a processor 1402, a memory 1404, a PScell ​​change module 1408, a transceiver 1410, a modem 1412, and one or more antennas 1416) to perform the steps of the method 1600. As illustrated, the method 1600 includes a plurality of the enumerated steps, but aspects of the method 1600 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0257] At step 1610, the first MN receives a HO request from the second MN. In some aspects, the HO request may include an Xn message. In some aspects, the second MN may trigger the HO based on a measurement report from the UE. In some aspects, the HO request may include an indication of the need for an AMF or triggering the HO. The first MN unit may utilize one or more components (such as a processor 1402, a memory 1404, a PScell ​​change module 1408, a transceiver 1410, a modem 1412, and one or more antennas 1416) to perform the actions of step 1610.

[0258] At step 1620, the first MN sends a PScell ​​change request to the first SN. In some aspects, sending the PScell ​​change request includes sending an SN add request message. In some aspects, the PScell ​​change request may include an Xn message. The first MN unit may utilize one or more components (such as processor 1402, memory 1404, PScell ​​change module 1408, transceiver 1410, modem 1412, and one or more antennas 1416) to perform the actions of step 1620.

[0259] At step 1630, the first MN receives a first message from the UE indicating that HO information is available and SPC information is available. In some aspects, the first message may include an RRCReconfigurationComplete message. The first MN unit may utilize one or more components (such as processor 1402, memory 1404, PScell ​​change module 1408, transceiver 1410, modem 1412, and one or more antennas 1416) to perform the actions of step 1630.

[0260] At step 1640, the first MN sends at least one request for HO information and SPC information to the UE based on the first message. In some aspects, the at least one request may include a UEInformationRequest indicating a request for both a successful HO (SHO) report and an SPC report. In another aspect, the at least one request may include separate UEInformationRequest messages, each indicating one of a SHO report request or an SPC report request.

[0261] At step 1650, the first MN receives a SHO report and an SPC report from the UE based on at least one request. In some aspects, the SHO report is triggered by at least one of a threshold of the MCG or the SCG. In some aspects, the SHO report indicates SHO information and the SPC report indicates SPC information. In some aspects, receiving the SHO report and receiving the SPC report include receiving a single UEInformationResponse. In another aspect, receiving the SHO report includes receiving a first UEInformationResponse and receiving the SPC report includes receiving a second UEInformationResponse different from the first UEInformationResponse.

[0262] Fig.171700 is a flow chart of a wireless communication method 1700 according to some aspects of the present disclosure. Aspects of the method 1700 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for performing steps. For example, the wireless communication device may include a UE, such as one of UEs 115. The method 1700 may include Fig.10 One or more aspects of the illustrated procedure 1000. In this regard, the method 1700 may include the SN initiating and / or otherwise controlling the PScell ​​change with limited or no participation of the MN. The UE may utilize one or more components (such as the processor 1302, the memory 1304, the PScell ​​change module 1308, the transceiver 1310, the modem 1312, and one or more antennas 1316) to perform the steps of the method 1700. As illustrated, the method 1700 includes a plurality of the enumerated steps, but aspects of the method 1700 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0263] At step 1710, the UE receives an SN modification indication from the SN. In some aspects, receiving the SN modification indication includes receiving an RRCReconfiguration message indicating a cell reconfiguration for the PScell. However, the UE may receive any suitable type of messaging, including RRC IE, MAC-CE, DCI, and / or any other suitable messaging.

[0264] At step 1720, the UE receives an SPC reporting configuration from the SN based on the SN modification indication. In some aspects, receiving the SPC reporting configuration includes receiving an RRCReconfiguration message indicating the SPC reporting configuration. In some aspects, steps 1720 and 1710 may include receiving the same RRCReconfiguration message indicating both the SN modification and the SPC reporting configuration. In other aspects, separate messages indicating the SN modification and the SPC reporting configuration may be received in steps 1710 and 1720, respectively.

[0265] At step 1730, the UE sends an SPC report based on the SPC reporting configuration and SPC information obtained by the UE. In some aspects, the UE sends the SPC report to the SN via SRB3. In another aspect, the UE sends the SPC report to the MN via SRB1, and the MN sends the SPC report to the SN. In some aspects, the UE may send a UEInformationResponse to the MN based on a UEInformationRequest from the MN. In other aspects, if SRB3 is available, the UE may send the SPC report directly to the SN in a UL RRC message via SRB3.

[0266] In some aspects, the method 1700 includes the UE and the network node performing a random access procedure, as described above. In another aspect, the method 1700 includes the UE sending an SN reconfiguration indication based on the SN modification indication. For example, the UE may send an RRCReconfigurationComplete message to the SN.

[0267] Fig.18 1800 is a flow chart of a wireless communication method 1800 according to some aspects of the present disclosure. Aspects of the method 1800 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for performing steps. For example, the wireless communication device may include a UE, such as one of UEs 115. The method 1800 may include Fig.12 One or more aspects of the procedure 1200 shown. The UE may utilize one or more components (such as a processor 1302, a memory 1304, a PScell ​​change module 1308, a transceiver 1310, a modem 1312, and one or more antennas 1316) to perform the steps of the method 1800. As illustrated, the method 1800 includes a plurality of the enumerated steps, but aspects of the method 1800 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0268] At step 1810, the UE receives an indication of cell reconfiguration from a network node. In some aspects, the indication may include an RRCReconfiguration message indicating reconfiguration of a PScell ​​or Scell. In some aspects, the UE may receive the indication from the MN. The MN may send the indication based on channel measurements obtained and / or reported by the UE. For example, the channel measurements may be reported in a CSI report. The network node may determine that one or more conditions for cell reconfiguration are met and may send the indication based on the determination. In another aspect, the network node may receive signals indicating that an SN change is required, such as an SN, from different network nodes.

[0269] At step 1820, the UE detects a failure of the cell reconfiguration. In some aspects, detecting the failure may include detecting an SCG failure associated with the cell reconfiguration. In this regard, the SCG failure detection may be associated with or based on an SCG radio link failure, a failure of SCG reconfiguration with synchronization, a control plane (e.g., SRB3) failure of the SCG configuration, an SCG integrity check failure, and / or exceeding a maximum UL transmit timing difference.

[0270] At step 1830, the UE sends an SCG failure report indicating SCG failure related information to the network node based on detecting the failure. In some aspects, the UE may send a UCI indicating the SCG failure information. In another example, the UE may send a MAC-CE indicating the SCG failure information. In some aspects, the SCG failure information includes or indicates which of multiple failure conditions occurred. In some aspects, the SCG failure information may indicate a timer expiration, a random access problem, a maximum RLC retransmission occurrence, and / or any other suitable information associated with a cell reconfiguration failure.

[0271] At step 1840, the UE sends an additional SCG fault report to the network node indicating additional SCG fault related information different from the first SCG fault information. In some aspects, the UE may receive a request from the network node to send an additional SCG fault report, and may send the additional SCG fault report based on the request. In some aspects, sending the additional SCG fault information may include sending a UE information request indicating a second SCG fault information.

[0272] In another aspect, the second SCG fault information includes at least one of: an indication of a first satisfied condition event for cell reconfiguration, or a time duration between a first satisfied condition for cell reconfiguration and a second satisfied condition for cell reconfiguration. In another aspect, the SCG fault report may indicate that the second SCG fault information is available for sending. Method 1800 may also include receiving an SCG fault information request from a network node, and sending another SCG fault report may be based on the SCG fault information request.

[0273] Exemplary Aspects of the Disclosure

[0274] The present disclosure also includes and provides the following exemplary aspects:

[0275] Aspect 1. A method of wireless communication performed by a first network unit, wherein the method comprises: sending an indication of a change of a primary and secondary cell group cell (PScell) associated with a user equipment (UE) to a second network unit; sending a successful PScell ​​change (SPC) report configuration based on the indication; and receiving an SPC report, wherein the SPC report is based on the SPC report configuration and SPC information associated with the UE.

[0276] Aspect 2. A method according to Aspect 1, wherein: the first network unit includes a master node; the second network unit includes a target secondary node (SN); sending the indication of the SPC to the second network unit includes sending an SN add request to the target SN; and sending the SPC report configuration includes sending the SPC report configuration to the UE.

[0277] Aspect 3. A method according to Aspect 2, wherein: the SPC reporting configuration indicates one or more triggering thresholds for one or more timers associated with a master cell group (MCG), a secondary cell group (SCG), or both.

[0278] Aspect 4. The method according to any one of Aspects 2 to 3 further includes: performing network optimization based on the SPC report, wherein performing the network optimization includes at least one of the following: updating a timer threshold associated with radio link monitoring (RLM) or beam failure detection (BFD); or detecting a near failure scenario during SPC or successful handover.

[0279] Aspect 5. The method according to Aspect 4 further includes: receiving a secondary cell group (SCG) failure report from the UE; wherein receiving the SPC report includes receiving the SPC report from the UE, and wherein performing the network optimization is based on the association of the SCG failure report with the SPC report.

[0280] Aspect 6. The method according to Aspect 4 also includes: receiving a secondary cell group (SCG) failure report from the UE; and wherein receiving the SPC report includes receiving the SPC report from a second master node different from the master node, and wherein performing the network optimization is based on the association of the SCG failure report with the SPC report.

[0281] Aspect 7. A method according to any one of Aspects 1 to 6, wherein: the first network unit includes a secondary node (SN); sending the indication of the PScell ​​change to the second network unit includes sending an SN change request to a master node; sending the SPC report configuration includes sending a first PScell ​​change report configuration to the master node; and receiving the SPC report includes receiving the SPC report from the master node.

[0282] Aspect 8. A method according to Aspect 7, wherein: the SN change request indicates a threshold for a first timer, and wherein the SPC report is based on the first PScell ​​change report configuration and a second PScell ​​change report configuration, wherein the second PScell ​​change report configuration indicates a threshold for a second timer associated with a target SN.

[0283] Aspect 9. The method according to any one of Aspects 7 to 8 further includes: performing network optimization based on the SPC report.

[0284] Aspect 10. The method according to Aspect 9 further includes: receiving a secondary cell group (SCG) fault report from the master node, wherein receiving the SPC report includes receiving the SPC report from the master node, and wherein performing the network optimization is based on the association of the SCG fault report with the SPC report.

[0285] Aspect 11. The method according to Aspect 9 further includes: receiving a secondary cell group (SCG) fault report from the master node, wherein receiving the SPC report includes receiving the SPC report from a second master node different from the master node, and wherein performing the network optimization is based on the association of the SCG fault report with the SPC report.

[0286] Aspect 12. The method according to any one of Aspects 1 to 11 further includes: receiving a secondary cell group (SCG) fault report, wherein: the SCG fault report includes a first indicator associated with the SPC report, and the SPC report includes a second indicator associated with the SCG fault report; or a combination thereof; and performing network optimization based on the association between the SCG fault report and the SPC report, wherein the association is based on at least one of the first indicator or the second indicator.

[0287] Aspect 13. A method of wireless communication performed by a first master node, wherein the method includes: receiving a handover (HO) request from a second master node; sending a primary-secondary cell group cell (PScell) change request to a first secondary node (SN); receiving a first message from a user equipment (UE) indicating that successful HO information is available and SPC information is available; sending at least one request for the successful HO information and the SPC information to the UE based on the first message; and receiving a successful HO report indicating the successful HO information and an SPC report indicating the SPC information from the UE based on the at least one request.

[0288] Aspect 14. The method according to Aspect 13 further includes: sending a successful HO report configuration indicating one or more triggering thresholds for one or more timers associated with at least one of a primary cell group (MCG) or a secondary cell group (SCG) to the UE, wherein the successful HO report is based on the successful HO report configuration.

[0289] Aspect 15. A method of wireless communication performed by a user equipment (UE), wherein the method comprises: receiving an SN modification indication from a secondary node (SN); receiving a successful primary-secondary cell group cell (PScell) change report configuration from the SN based on the SN modification indication; and sending an SPC report, wherein the SPC report is based on the SPC report configuration and PScell ​​change information associated with the UE.

[0290] Aspect 16. The method according to aspect 15, wherein sending the SPC report comprises sending the SPC report to a master node in communication with the SN.

[0291] Aspect 17. The method according to aspect 15, wherein sending the SPC report includes sending the SPC report to the SN.

[0292] Aspect 18. A method of wireless communication performed by a user equipment (UE), wherein the method comprises: receiving a reconfiguration message for a PSCell change from a network node; detecting a PSCell change failure based on the reconfiguration message; sending a secondary cell group (SCG) failure report indicating SCG failure-related information to the network node based on detecting the failure; and sending an additional SCG failure report indicating additional SCG failure-related information to the network node after sending the SCG report.

[0293] Aspect 19. A method according to Aspect 18, wherein the additional SCG fault report includes at least one of the following: an indication of a first satisfied condition associated with the reconfiguration message for the PSCell change; or a time duration between the first satisfied condition and the second satisfied condition associated with the reconfiguration message for the PSCell change.

[0294] Aspect 20. A method according to any one of Aspects 18 to 19, wherein: the UE indicates in at least one of the SCG fault report or the additional SCG fault report that the additional SCG fault-related information is available for sending; the method also includes: receiving an additional SCG fault information request from the network node; and sending the additional SCG fault report based on receiving the SCG fault information request.

[0295] Aspect 21. A first network unit, comprising: a memory device; a transceiver; and a processor in communication with the processor and the transceiver, wherein the first network unit is configured to perform the actions according to any one of aspects 1 to 12.

[0296] Aspect 22. A first master node, comprising: a memory device; a transceiver; and a processor in communication with the processor and the transceiver, wherein the first master node is configured to perform actions according to any one of aspects 13 to 14.

[0297] Aspect 23. A UE comprising: a memory device; a transceiver; and a processor in communication with the processor and the transceiver, wherein the UE is configured to perform the actions according to any one of aspects 15 to 17.

[0298] Aspect 24. A UE comprising: a memory device; a transceiver; and a processor in communication with the processor and the transceiver, wherein the UE is configured to perform the actions according to any one of aspects 18 to 20.

[0299] Aspect 25. A non-transitory computer-readable medium having program code recorded thereon, wherein the program code comprises instructions executable by a processor of a first network element, wherein the instructions comprise code for causing the first network element to perform actions according to any one of aspects 1 to 12.

[0300] Aspect 26. A non-transitory computer-readable medium having program code recorded thereon, wherein the program code comprises instructions executable by a processor of a first master node, wherein the instructions comprise code for causing the first master node to perform actions according to any one of Aspects 13 to 14.

[0301] Aspect 27. A non-transitory computer-readable medium having program code recorded thereon, wherein the program code comprises instructions executable by a processor of a UE, wherein the instructions comprise code for causing a UE node to perform actions according to any one of aspects 15 to 17.

[0302] Aspect 28. A non-transitory computer-readable medium having program code recorded thereon, wherein the program code comprises instructions executable by a processor of a UE, wherein the instructions comprise code for causing a UE node to perform actions according to any one of aspects 18 to 20.

[0303] Aspect 29. A first network element, comprising means for performing the actions according to any one of aspects 1 to 12.

[0304] Aspect 30. A first master node, comprising components for performing actions according to any one of aspects 13 to 14.

[0305] Aspect 31. A UE comprising means for performing actions according to any one of aspects 15 to 17.

[0306] Aspect 32. A UE comprising means for performing actions according to any one of aspects 18 to 20.

[0307] Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0308] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).

[0309] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software, hardware, firmware, hard wiring, or any combination thereof executed by a processor. The features that implement the functions may also be physically located at different locations, including being distributed so that the parts of the functions are implemented at different physical locations. In addition, as used herein (including in the claims), as used in an item enumeration (e.g., followed by an item enumeration such as "at least one of" or "one or more of"), "or" indicates an inclusive enumeration, such that, for example, an enumeration of [at least one of A, B, or C] means: A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0310] As those skilled in the art will understand by now and depending on the specific application at hand, many modifications, substitutions and changes may be made to the materials, devices, configurations and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the specific embodiments illustrated and described herein (as they are only some examples of the present disclosure), but should be fully equivalent to the appended claims and their functional equivalents.

Claims

1. A method of wireless communication performed by a first network element, wherein the method comprises: sending an indication of a change of a primary and secondary cell group cell (PScell) associated with a user equipment (UE) to a second network element; sending a successful PScell ​​change (SPC) configuration based on the indication; as well as An SPC report is received, wherein the SPC report is based on the SPC configuration and SPC information associated with the UE.

2. The method according to claim 1, wherein: The first network unit includes a master node; The second network element comprises a target secondary node (SN); sending the indication of the PScell ​​change to the second network element comprises sending an SN add request to the target SN; and Sending the SPC configuration includes sending the SPC configuration to the UE.

3. The method according to claim 2, wherein: The SPC configuration indicates one or more triggering thresholds for one or more timers associated with a master cell group (MCG), a secondary cell group (SCG), or both.

4. The method according to claim 2, further comprising: Network optimization is performed based on the SPC report.

5. The method of claim 4, wherein performing the network optimization comprises updating a timer threshold associated with radio link monitoring (RLM) or beam failure detection (BFD). The method of claim 4 , wherein performing the network optimization comprises detecting a near failure scenario during SPC or a successful handover.

7. The method according to claim 4, further comprising: receiving a secondary cell group (SCG) failure report from the UE, wherein receiving the SPC report comprises receiving the SPC report from the UE, and The network optimization is performed based on the association of the SCG fault report with the SPC report.

8. The method according to claim 4, further comprising: receiving a secondary cell group (SCG) failure report from the UE, wherein receiving the SPC report comprises receiving the SPC report from a second master node different from the master node, and The network optimization is performed based on the association of the SCG fault report with the SPC report.

9. The method according to claim 1, wherein: The first network element comprises a secondary node (SN); Sending the indication of the PScell ​​change to the second network element comprises sending an SN change request to a master node; Sending the SPC configuration includes sending a first PScell ​​change report configuration to the master node; and Receiving the SPC report includes receiving the SPC report from the master node.

10. The method according to claim 9, wherein: The SN change request indicates a threshold value for a first timer, and The SPC report is based on the first PScell ​​change reporting configuration and a second PScell ​​change reporting configuration, wherein the second PScell ​​change reporting configuration indicates a threshold value for a second timer associated with a target SN.

11. The method according to claim 9, further comprising: receiving a secondary cell group (SCG) fault report from the master node; as well as Network optimization is performed based on an association of the SCG fault report with the SPC report, wherein receiving the SPC report includes receiving the SPC report from the master node.

12. The method according to claim 9, further comprising: receiving a secondary cell group (SCG) fault report from the master node; as well as Network optimization is performed based on an association of the SCG fault report with the SPC report, wherein receiving the SPC report includes receiving the SPC report from a second master node different from the master node.

13. The method according to claim 1, further comprising: Receive a secondary cell group (SCG) fault report, where: The SCG fault report comprises a first indicator associated with the SPC report, The SPC report includes a second indicator associated with the SCG fault report; or combinations thereof; and Network optimization is performed based on an association of the SCG fault report with the SPC report, wherein the association is based on at least one of the first indicator or the second indicator.

14. A method of wireless communication performed by a user equipment (UE), wherein the method comprises: receiving a reconfiguration message for a PSCell change from a network node; detecting a PSCell change failure based on the reconfiguration message; sending a secondary cell group (SCG) fault report indicating SCG fault related information to the network node based on detecting the fault; as well as A further SCG failure report indicating additional SCG failure related information is sent to the network node after sending the SCG report.

15. The method according to claim 14, wherein the additional SCG fault related information comprises at least one of the following: an indication of a first satisfied condition associated with said reconfiguration message for a PSCell change; or The time duration between a first condition satisfied and a second condition satisfied associated with the reconfiguration message for the PSCell change.

16. A first network unit, comprising: Memory devices; Transceiver; and a processor in communication with the processor and the transceiver, wherein the first network element is configured to: sending an indication of a change of a primary and secondary cell group cell (PScell) associated with a user equipment (UE) to a second network element; sending a successful PScell ​​change (SPC) configuration based on the indication; as well as An SPC report is received, wherein the SPC report is based on the SPC configuration and SPC information associated with the UE.

17. The first network unit according to claim 16, wherein: The first network unit includes a master node; The second network element comprises a target secondary node (SN); The first network element configured to send the indication of the PScell ​​change to the second network element comprises the first network element configured to send an SN add request to the target SN; and The first network element is configured to send the SPC report to the UE.

18. The first network unit according to claim 17, wherein: The SPC configuration indicates one or more triggering thresholds for one or more timers associated with a master cell group (MCG), a secondary cell group (SCG), or both.

19. The first network unit according to claim 17, wherein the first network unit is further configured to: Network optimization is performed based on the SPC report.

20. The first network element of claim 19, wherein the network optimization comprises updating of a timer threshold associated with radio link monitoring (RLM) or beam failure detection (BFD).

21. The first network element of claim 19, wherein the network optimization comprises detecting a near failure scenario during SPC or a successful handover.

22. The first network unit according to claim 19, wherein the first network unit is further configured to: receiving a secondary cell group (SCG) failure report from the UE, wherein the first network element is configured to receive the SPC report from the UE, and The first network element is configured to perform the network optimization based on the association of the SCG fault report with the SPC report.

23. The first network unit according to claim 19, wherein the first network unit is further configured to: receiving a secondary cell group (SCG) failure report from the UE; and wherein the first network element is configured to receive the SPC report from the master node, and The first network element is configured to perform the network optimization based on the association of the SCG fault report with the SPC report.

24. The first network element according to claim 16, wherein: The first network element comprises a secondary node (SN); The first network element configured to send the indication of the PScell ​​change to the second network element comprises the first network element configured to send an SN change request to a master node; The first network element configured to send the SPC configuration includes the first network element configured to send a first PScell ​​change report configuration to the master node; and The first network element is configured to receive the SPC report from the master node.

25. The first network unit according to claim 24, wherein: The SN change request indicates a threshold value for a first timer, and The SPC report is based on the first PScell ​​change reporting configuration and a second PScell ​​change reporting configuration, wherein the second PScell ​​change reporting configuration indicates a threshold value for a second timer associated with a target SN.

26. The first network unit according to claim 24, wherein the first network unit is further configured to: receiving a secondary cell group (SCG) failure report from the master node; and Network optimization is performed based on an association of the SCG fault report with the SPC report, wherein the first network element is configured to receive the SPC report from the master node.

27. The first network unit according to claim 26, wherein the first network unit is further configured to: receiving a secondary cell group (SCG) failure report from the master node; and Network optimization is performed based on the association of the SCG fault report with the SPC report, wherein the first network element is configured to receive the SPC report from a second master node different from the master node.

28. The first network unit according to claim 16, wherein the first network unit is further configured to: Receive a secondary cell group (SCG) fault report, where: The SCG fault report comprises a first indicator associated with the SPC report, The SPC report includes a second indicator associated with the SCG fault report; or combinations thereof; and The first network element is configured to perform network optimization based on an association of the SCG fault report with the SPC report, wherein the association is based on at least one of the first indicator or the second indicator.

29. A user equipment (UE), comprising: Memory devices; Transceiver; and a processor in communication with the processor and the transceiver, wherein the UE is configured to: receiving a reconfiguration message for a PSCell change from a network node; detecting a PSCell change failure based on the reconfiguration message; sending a secondary cell group (SCG) fault report indicating SCG fault related information to the network node based on detecting the fault; as well as A further SCG failure report indicating additional SCG failure related information is sent to the network node after sending the SCG report.

30. The UE according to claim 29, wherein the additional SCG fault report comprises at least one of the following: an indication of a first satisfied condition associated with said reconfiguration message for a PSCell change; or The time duration between a first satisfied condition and a second satisfied condition associated with the reconfiguration message for a PSCell change.

Images