Methods and apparatus for handling a SPR in a wireless communication system

Abstract

The disclosure relates to a fifth generation (5G) or sixth generation (6G) communication system for supporting higher data rates. Embodiments herein provide a method and system for handling a successful PSCell report (SPR). The method includes receiving a configuration to report a successful PSCell change or addition information to a network apparatus and optionally a configuration that informs whether a PSCell change or a CPC is initiated by a SN or not from a PSCell or a PCell. Further, the method includes determining that the UE (102) is configured to provide the successful PSCell change or addition information by the PCell, the PSCell, and a source PSCell. Further, the method includes determining that the UE (102) is not configured to provide the successful PSCell change or addition information by a MCG and a SCG. Further, the method includes performing actions for the SPR based on determination of that the UE (102) is configured or not configured to provide the successful PSCell change or addition information.

Description

METHODS AND APPARATUS FOR HANDLING A SPR IN A WIRELESS COMMUNICATION SYSTEM

[0001] This application is based on and derives the benefit of Indian Provisional Applications 202441021484 filed on 21st March 2024 and 202441023904 filed on 26th March 2024 the contents of which are incorporated herein by reference. The present disclosure is related to the field of wireless communication. More particularly, the present disclosure is related to a method and system for handling a successful primary and secondary cell (PSCell) report (SPR) in a wireless network.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The present disclosure relates to wireless communication systems and, more specifically, the present disclosure relates to determining whether and how UE is configured to provide SPR in a 5G network in a wireless communication.

[0009] The principal object of the embodiments herein is to provide a system and method for handling a successful primary and secondary cell (PSCell) report (SPR) in a wireless network.

[0010] Another object of the embodiments herein is to provide methods and systems for self-optimization (including optimizations for minimization of drive tests) of mobility in dual connectivity.

[0011] Yet another object of the embodiments herein is to provide using target thresholds instead of source thresholds in optimizing the dual connectivity.

[0012] In an aspect, the objectives are achieved by providing a method for handling a SPR in a wireless network. The method includes receiving a configuration to report a successful PSCell change or addition information (SPR configuration) to a network apparatus and optionally a configuration that informs whether a PSCell change or a conditional PSCellChange (CPC) is initiated by a secondary node (SN) or not (sn-initiatedPSCellChange), from a PSCell or a Primary Cell (PCell). Further, the method includes determining that the UE is configured to provide the successful PSCell change or addition information by the PCell if a successPSCell-Config is setup and the successPSCell-Config is received from the PCell and a sn-initiatedPSCellChange is not received. Further, the method includes determining that the UE is configured to provide the successful PSCell change or addition information by the PSCell, if the successPSCell-Config is setup and the successPSCell-Config is received from the PSCell and the sn-initiatedPSCellChange is not received. Further, the method includes determining that the UE is configured to provide the successful PSCell change or addition information by a source PSCell if the successPSCell-Config is setup and the sn-initiatedPSCellChange is received. Further, the method includes determining that the UE is configured to provide the successful PSCell change or addition information by the source PSCell if the sn-initiatedPSCellChange is received and successPSCell-Config is already configured for a secondary cell group (SCG). Further, the method includes determining that the UE is not configured to provide the successful PSCell change or addition information by a master cell group (MCG) if the successPSCell-Config is set to release and the successPSCell-Config is received from the PCell. Further, the method includes determining that the UE is not configured to provide the successful PSCell change or addition information by the SCG if the successPSCell-Config is set to release and the successPSCell-Config is received from the PSCell. Further, the method includes performing actions for the SPR based on determination of that the UE is configured or not configured to provide the successful PSCell change or addition information.

[0013] In another aspect, the objectives are achieved by providing a UE for handling a SPR in a wireless network. The UE includes a memory, a processor, and a SPR handling controller coupled to the memory and the processor. The SPR handling controller receives a configuration to report a successful PSCell change or addition information to a network apparatus and optionally a configuration that informs whether a PSCell change or a conditional PSCellChange (CPC) is initiated by a secondary node (SN) or not from a PSCell or a Primary Cell (PCell). Further, the SPR handling controller determines that the UE is configured to provide the successful PSCell change or addition information by the PCell if a successPSCell-Config is setup and the successPSCell-Config is received from the PCell and a sn-initiatedPSCellChange is not received. Further, the SPR handling controller determines that the UE is configured to provide the successful PSCell change or addition information by the PSCell if the successPSCell-Config is setup and the successPSCell-Config is received from the PSCell and the sn-initiatedPSCellChange is not received. Further, the SPR handling controller determines that the UE is configured to provide the successful PSCell change or addition information by a source PSCell of the PSCell if the successPSCell-Config is setup and the sn-initiatedPSCellChange is received. Further, the SPR handling controller determines that the UE is configured to provide the successful PSCell change or addition information by the source PSCell if the sn-initiatedPSCellChange is received and successPSCell-Config is already configured for a secondary cell group (SCG). Further, the SPR handling controller determines that the UE is not configured to provide the successful PSCell change or addition information by a master cell group (MCG) if the successPSCell-Config is set to release and the successPSCell-Config is received from the PCell. Further, the SPR handling controller determines that the UE is not configured to provide the successful PSCell change or addition information by the SCG if the successPSCell-Config is set to release and the successPSCell-Config is received from the PSCell. Further, the SPR handling controller performs actions for the SPR based on determination of that the UE is configured or not configured to provide the successful PSCell change or addition information.

[0014] In another aspect, the objectives are achieved by providing a method performed by a user equipment (UE) in a communication system, the method comprising: receiving, from a base station, a radio resource control (RRC) reconfiguration message including an other configuration; identifying whether the other configuration includes information indicating whether a primary secondary cell (PSCell) change procedure is initiated by a secondary node (SN) and whether a configuration to report a successful PSCell change or addition information is received in the other configuration; and in case that the information indicating whether the PSCell change procedure is initiated by the SN is not included in the other configuration and in case that the configuration received in the other configuration is set to setup, determining to be configured to provide the successful PSCell change or addition information.

[0015] In another aspect, the objectives are achieved by providing a method performed by a base station in a communication system, the method comprising: transmitting, to a user equipment, a radio resource control (RRC) reconfiguration message including an other configuration; and identifying whether the other configuration includes information indicating whether a primary secondary cell (PSCell) change procedure is initiated by a secondary node (SN) and whether a configuration to report a successful PSCell change or addition information is received in the other configuration; in case that the information indicating whether the PSCell change procedure is initiated by the SN is not included in the other configuration and in case that the configuration received in the other configuration is set to setup, the UE is determined to be configured to provide the successful PSCell change or addition information.

[0016] In another aspect, the objectives are achieved by providing a user equipment (UE) in a communication system, the UE comprising: a transceiver; and at least one processor coupled with the transceiver, the at least one processor is configured to: receive, from a base station, a radio resource control (RRC) reconfiguration message including an other configuration, identify whether the other configuration includes information indicating whether a primary secondary cell (PSCell) change procedure is initiated by a secondary node (SN) and whether a configuration to report a successful PSCell change or addition information is received in the other configuration, and in case that the information indicating whether the PSCell change procedure is initiated by the SN is not included in the other configuration and in case that the configuration received in the other configuration is set to setup, determine to be configured to provide the successful PSCell change or addition information.

[0017] In another aspect, the objectives are achieved by providing a base station in a communication system, the base station comprising: a transceiver; and at least one processor coupled with the transceiver, the at least one processor is configured to: transmit, to a user equipment, a radio resource control (RRC) reconfiguration message including an other configuration; and identify whether the other configuration includes information indicating whether a primary secondary cell (PSCell) change procedure is initiated by a secondary node (SN) and whether a configuration to report a successful PSCell change or addition information is received in the other configuration; in case that the information indicating whether the PSCell change procedure is initiated by the SN is not included in the other configuration and in case that the configuration received in the other configuration is set to setup, the UE is determined to be configured to provide the successful PSCell change or addition information.

[0018] According to an embodiment of the disclosure, a wireless communication can be performed efficiently. Especially, determining whether and how UE is configured to provide SPR can be performed efficiently.

[0019] These and other features, aspects, and advantages of the present embodiments are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0020] Fig. 1 is a block diagram that illustrates a schematic of a UE implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein.

[0021] Fig. 2 is a flow diagram that illustrates the UE determining whether and how the UE is configured to provide SPR information according to an embodiment as disclosed herein.

[0022] Fig. 3 is a flow diagram that illustrates the UE handling the successPSCell-Config set as release according to an embodiment as disclosed herein.

[0023] Fig. 4 is a flow diagram that illustrates the UE handling SPR configuration at the SPR determination according to an embodiment as disclosed herein.

[0024] Fig. 5 is a flow diagram that illustrates using T310 / T312 thresholds from the target PSCell to determine the SPR according to an embodiment as disclosed herein.

[0025] Fig. 6 is a flow diagram that illustrates determination of a successful PSCellChange or addition information according to an embodiment as disclosed herein.

[0026] Fig. 7 is a flow diagram that illustrates a PSCell configuration to provide successful PSCellChange or addition information according to an embodiment as disclosed herein.

[0027] Fig. 8 is a flow diagram that illustrate a method for handling a SPR in a wireless network according to an embodiment as disclosed herein.

[0028] A 5G NR radio access network also known as NG-RAN (Next Generation Radio Network) includes a plurality of NR base stations knows as gNBs. The gNBs can be connected to each other through an Xn interface, and will be connected to various core network elements like AMF (Access and Mobility Management Function), UPF (User Plane Function) etc. Further, the gNBs can be divided into two physical entities named CU (Centralized Unit) and DU (Distributed Unit). The CU provides support for the higher layers of the protocol stack such as SDAP (Session Data Application Protocol), PDCP (Packet Data Convergence Protocol) and RRC (Radio Resource Control) while the DU provides support for the lower layers of the protocol stack such as RLC (Radio Link Control), MAC (Medium Access Control) and Physical layer. Each gNB can have multiple cells serving many UEs (User Equipment).

[0029] There are a large number of procedures and configuration parameters used in NG-RAN. Especially, it is a very difficult task to identify the most optimal radio parameters and operators used to resort to manual techniques like drive tests to identify the parameters. However, such manual parameter tuning is a costly operation since it depends on a lot of factors like the number of users, number of neighbors, maximum throughput in the cell, average throughput in the cell, and the like. Further, whenever a neighbor gNB is installed or a new service is introduced, many of these manual operations need to be repeated. To resolve this problem, 3GPP has introduced Self-Organizing Networks (SON) techniques in the wireless technologies like NR. SON was first introduced in 3gpp release 9, in LTE. SON solutions can be divided into three categories: Self-Configuration, Self-Optimization and Self-Healing. The SON architecture can be a centralized, distributed or a hybrid solution.

[0030] In conventional methods, configuring a Success PSCell Configuration (SPR configuration) (such as successPSCell-Config in NR) has certain issues. In conventional methods, the network always need to provide the T304 threshold (thresholdPercentageT304-SCG) even if the intention is only to optimize and prevent the source PScell's potential failure (T310 thresholds or T312 thresholds). This needs additional signaling overhead over the air interface and the computational overhead at the source node. In case the thresholds are not provided by the network to avoid the signaling and computational overhead, it leads to the additional processing at the UE.

[0031] In conventional methods, the UE decides whether it is configured by the PCell to provide the successful PSCell change or addition information based on the field which indicates whether the PSCell change procedure for which the successful PSCell change report is logged is SN initiated or not (such as sn-InitiatedPSCellChange). If the sn-InitiatedPSCellChange is included in received otherConfig, the UE considers itself to be configured by the source PSCell to provide the successful PSCell change or addition information and if the sn-InitiatedPSCellChange is not included in received otherConfig, the UE considers itself to be configured by the source PCell to provide the successful PSCell change or addition information. This works only for the case where the thresholds for successPSCell-Config are provided at the time of PSCell Change and PSCell addition (i.e. in the same RRC message). When the T310 / T312 thresholds are configured prior to the PSCellChange / PSCellAddition (in a different RRC message send prior to this), network cannot be aware of whether a PSCellChange will be SN initiated or not and cannot be able to provide the flag such as the sn-InitiatedPSCellChange. So the UE always considers itself to be configured by PCell even when it is configured by PSCell. Since the optimization requirements are different for PCell and PSCell, this will lead to wrong logging and reporting of information and wrong optimizations.

[0032] Further, in the conventional methods, the UE uses the sn-InitiatedPSCellChange included in the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for determining whether Success PSCell Report (SPR) needs to be logged. This restricts network implementations. For the flexibility of network implementation, T310 and T312 thresholds can be provided at the time of PSCellChange. However it is not possible in current systems. Currently, if the target PSCell includes only T304 threshold, the UE considers itself to be configured by the PCell to provide SPR, which leads to a wrong determination of the SPR.

[0033] Hence, is desirable to address the above mentioned problems and disadvantages or at least provide a useful alternative.

[0034] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with a plurality of other embodiments to form new embodiments. The term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples are not be construed as limiting the scope of the embodiments herein.

[0035] As is existing in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions.　These blocks, which referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, and the like, and optionally be driven by firmware and software. The circuits, for example, be embodied in a plurality of semiconductor chips, or on substrate supports such as printed circuit boards, and the like.　The circuits constituting a block be implemented by dedicated hardware, or by a processor (e.g., a plurality of programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method.　Likewise, the blocks of the embodiments be physically combined into more complex blocks without departing from the scope of the proposed method.

[0036] The accompanying drawings are used to help easily understand various technical features and it is understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the proposed method is construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. used herein to describe various elements, these elements are not be limited by these terms. These terms are generally used to distinguish one element from another.

[0037] A method is required to outline the UE actions for configurations that facilitate the successful change or addition of PSCell information, based on the cell that establishes the successPSCell-Config. Additionally, there is a necessity for a method that defines the UE actions for configurations to ensure the successful change or addition of PSCell information, based on the cell that terminates the successPSCell-Config.

[0038] Dual Connectivity:

[0039] Dual connectivity or more technically multi-radio dual connectivity is specified by 3gpp in specifications such as TS 37.340. A summary of the details on dual connectivity and measurement gap operations with dual connectivity are given below.

[0040] NG-RAN supports Multi-Radio Dual Connectivity (MR-DC) operation whereby a user equipment (UE) in RRC_CONNECTED is configured to utilize radio resources provided by two distinct schedulers, located in two different NG-RAN nodes connected via a non-ideal backhaul, one providing NR (New Radio) access and the other one providing either E-UTRA (Evolved UMTS Terrestrial Radio Access) or NR access. One node acts as the master node (MN) and the other as the secondary node (SN). The MN and SN are connected via a network interface and at least the MN is connected to the core network. NG-RAN supports NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), in which a UE is connected to one ng-eNB (an E-UTRA base station that can connect to 5G core) that acts as a MN and one gNB (5G base station) that acts as a SN. NG-RAN also supports NR-E-UTRA Dual Connectivity (NE-DC), in which a UE is connected to one gNB that acts as a MN and one ng-eNB that acts as a SN. MN can move the SCG to different states: deactivated and activated. When carrier aggregation is supported, the secondary cells can be moved to deactivated / activated. When a radio link failure occurs in the SCG, UE sends RRC message SCGFailureInformation.

[0041] PSCell change and PSCell Addition:

[0042] PSCell change can occur due to mobility and can or cannot be associated with the Secondary Node Change (SN change).The Secondary Node Change procedure is initiated either by MN or SN and used to transfer a UE context from a source SN to a target SN and to change the SCG configuration in UE from one SN to another.

[0043] A Conditional PSCell Change (CPC) is defined as a PSCell change that is executed by the UE when execution condition(s) is met. UE can be configured with execution condition and the RRC message like RRC Reconfiguration for executing when the conditions are met for one or more of candidate cells. The UE starts evaluating the execution condition(s) upon receiving the CPC configuration, and stops evaluating the execution condition(s) once PSCell change is triggered. Intra-SN CPC without MN involvement, inter-SN CPC initiated either by MN or SN are supported.

[0044] 3gpp release 18 enhances the CPC through selective activation of cell groups where the UE doesn't release the stored CPC configuration for one or more candidate PSCells and the source PSCell based on network's inputs. The UE can also store the CPA configuration for one or more candidate PSCells.

[0045] In an embodiment, MN adds PSCell during a PSCell addition procedure. A PSCell addition procedure that is executed only when PSCell addition condition(s) are met is called Conditional PSCell Addition (CPA).

[0046] One of the functions of Mobility Robustness Optimization is to detect a sub-optimal successful PSCell change or sub-optimal successful PSCell addition event.

[0047] The present disclosure proposes methods for SON for dual connectivity scenarios. The methods for configuration, reporting and releasing the configuration of the UE for reporting information related to successful PSCell Addition and Successful PSCell Change. These information could be configured to be stored and reported in a report called Successful PSCell Report (SPR as defined below).

[0048]

[0049] The network configures the UE for reporting SPR using successPSCell-Config in OtherConfig as given below using RRC messages such as RRCReconfiguration in NR.

[0050]

[0051] As seen from above, the sn-InitiatedPSCellChange is provided as a Need M parameter, which means a UE which has received an OtherConfig including sn-InitiatedPSCellChange maintains the value, and if it receives another RRCReconfiguration message without sn-InitiatedPSCellChange, it applies the value received in previous RRCReconfiguration message.

[0052] In conventional methods, SPR contents can be as below:

[0053]

[0054] Other configuration

[0055] The UE shall:

[0056] 1>if the received otherConfig includes the successPSCell-Config:

[0057] 2>if thresholdPercentageT304-SCG is included:

[0058] 3>consider itself to be configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0059] 2>if sn-InitiatedPSCellChange is included in the received otherConfig:

[0060] 3>consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0061] 2>else if sn-InitiatedPSCellChange is not included in the received otherConfig:

[0062] 3>consider itself to be configured by the PCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0063] As seen above the UE considers itself to be configured by source PSCell to provide SPR, if it has received sn-InitiatedPSCellChange from the network along with the successPSCell-Config (i.e. in the same RRC Reconfiguration message) for setting up SPR configuration. If the UE has not received sn-InitiatedPSCellChange from the network in the same RRC Reconfiguration message, UE considers itself to be configured by PCell to provide SPR. Since sn-InitiatedPSCellChange informs the UE whether a PSCellChange is SN initiated or MN initiated, it needs to be provided at the time of PSCell Change. As a result, a UE receiving the SPR configuration for as setup before the PSCellChange will always consider the SPR configuration is from the PCell.

[0064] SPR configuration may be received at the time of PSCellChange or PSCell Addition, within CPC configuration or in a RRC message such as RRC Reconfiguration received before the PSCellChange or PSCellAddition. In case of SN initiated inter-SN PSCell change procedure or SN configured inter-SN CPC, UE receives sn-initiatedPSCellChange in the MCG RRC Reconfiguration message from Master Node (MN). In case of intra-SN PSCell change, or intra-SN CPC, UE receives sn-initiatedPSCellChange from source SN in the SCG RRC Reconfiguration.

[0065] Actions for the successful PSCell change or addition report determination

[0066] <Steps for including the SPR>

[0067] 1>release successPSCell-Config configured by the source PSCell if available and thresholdPercentageT304 if configured by the target PSCell.

[0068] The UE can discard the successful PSCell change or addition information, i.e., release the UE variable VarSuccessPSCell-Report, 48 hours after the last successful PSCell change or addition information is added to the VarSuccessPSCell-Report or upon deregistration from the network as specified in

[0043] .

[0069] 3gpp V18.0.0 version of TS 38.331, and TS 38.300 are considered as relevant background for the present disclosure.

[0070] The proposed solution discloses provides a system and method for handling SPR in wireless network. The method includes determining whether and how UE is configured to provide the SPR. The method includes self-optimization (including optimizations for minimization of drive tests) of random access in wireless networks like 5G NR. Further, the method includes communicating and utilizing the sn-InitiatedPSCellChange. The present solution proposes methods for SON for dual connectivity scenarios. The method includes configuration, reporting and releasing the configuration of the UE for reporting information related to successful PSCell Addition and Successful PSCell Change. These information could be configured to be stored and reported in a report called SPR.

[0071] The proposed solution further provides a system and method for using target thresholds instead of source thresholds in optimizing dual connectivity in wireless network. The method includes self-optimization (including optimizations for minimization of drive tests) of mobility in dual connectivity. The present disclosure proposes methods for SON for dual connectivity scenarios. The method includes configuration, reporting and releasing the configuration of the UE for reporting information related to successful PSCell Addition and Successful PSCell Change. These information could be configured to be stored and reported in a report called SPR.

[0072] Fig. 1 is a block diagram that illustrates a schematic of a UE (102) implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein. Examples of the UE (102) can include, but are not limited to, Consumer Electronics (such as Mobile Phones and Smartphones), Tablets, Wearable Devices, Computing Devices (such as Laptops, Notebooks, Desktops, Workstations, etc.), IoT Devices, Automotive Systems (such as connected cars, Autonomous Vehicles, Vehicle-to-Everything (V2X) communication devices, etc.), Enterprise Devices such as robotics, Specialized Equipment (such as Medical Devices, Public Safety Devices, etc.), Media Devices (such as Gaming Consoles, Streaming Devices, etc.).

[0073] In an embodiment, in Fig. 1, the UE (102) includes a processor (104), a memory (106), an I / O interface (108), and a SPR handling controller (110) coupled to the processor (104) and the memory (106). The components of the UE (102) are explained in further detail below.

[0074] The processor (104) communicates with the memory (106), the I / O interface (108), and the SPR handling controller (110). The processor (104) is configured to execute instructions stored in the memory (106) and to perform various processes. The processor (104) includes one or a plurality of processors, is a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial Intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0075] The memory (106) includes storage locations to be addressable through the first processor (104). The memory (106) is not limited to a volatile memory and / or a non-volatile memory. Further, the memory (106) includes a plurality of computer-readable storage media. The memory (106) includes non-volatile storage elements. For example, non-volatile storage elements includes magnetic hard disks, optical disks, floppy disks, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. Further, the memory (106) includes successPSCell-Config message, an otherconfig message, and the like.

[0076] The I / O interface (108) transmits the information between the memory (106) and external peripheral devices. The peripheral devices are the input-output devices associated with the UE (102). Further, the SPR handling controller (110) communicates with the I / O interface (108) and the memory (106). The SPR handling controller (110) is coupled to the memory (106) and the processor (104). This coupling allows for efficient data transfer and communication between the components, ensuring that the SPR handling controller (110) can handle a reporting of the SPR in the wireless network. The SPR handling controller (110) is an innovative integrated circuit that is implemented UE (102). In an embodiment, the structure of such innovative integrated circuit include a multi-core architecture that enables dynamic handling while reporting the SPR in the wireless network. Each core is optimized for specific tasks, such as configuring the UE (102) based on a successPSCell-Config received from a source PSCell and PCell. The innovative integrated circuit for handling a reporting of the SPR in the wireless network is made of a combination of analog and digital components designed to configure the UE (102) appropriately based on the successPSCell-Config received from the source PSCell and PCell. The analog components include a low-noise amplifier and a high-precision analog-to-digital converter to ensure accurate signal processing. The digital components consist of a microcontroller unit (MCU) and a digital signal processor (DSP) that work in tandem to configure the UE (102) appropriately based on the successPSCell-Config received from the source PSCell and PCell.

[0077] In an embodiment, the SPR handling controller (110) receives a configuration to report a successful PSCell change or addition information to a network apparatus and optionally a configuration that informs whether a PSCell change or a conditional PSCellChange (CPC) is initiated by a secondary node (SN) or not from a PSCell or a PCell. The PSCell refers to a main serving cell of the SN where the UE (102) is connected to multiple network nodes (for example, LTE, NR, etc.). The PCell refers to the main serving cell for the UE (102) in a single-node connection. The PCell is part of a master node (MN) during dual connectivity.

[0078] The network apparatus includes various hardware and software components that facilitate communication between user equipment and network infrastructure. Examples of the network apparatus (501) can include, but is not limited to Base Stations (such as macro cells, small cells, femtocells, picocells) for wireless communication, Antennas and RF Units (e.g., MIMO, beamforming) to enhance signal coverage and data throughput, Core Network Equipment (e.g., MMEs, S-GWs, P-GWs in 4G; AMFs, UPFs in 5G) for data routing, mobility, and session control, Network Function Virtualization (NFV) and Software-Defined Networking (SDN) for dynamic resource allocation and scalability, Edge Computing Nodes (e.g., MEC servers) for low-latency processing,　 Backhaul and Transport Equipment (e.g., fiber-optic links, microwave relays, Ethernet switches) to connect base stations to the core network, Network Management Systems (NMS) and Operation Support Systems (OSS) for network configuration, fault management, and optimization, Radio Network Controllers (RNCs) in 3G, Distributed Units (DUs), and Centralized Units (CUs) in 5G, Network Slicing Components for virtualized resource allocation, Security elements (e.g., Firewalls, IDS, AAA Servers) for secure communication.

[0079] In an embodiment, the SPR handling controller (110) determines that the UE (102) is configured to provide the successful PSCell change or addition information by the PCell. This is determines if a successPSCell-Config is setup, the successPSCell-Config is received from the PCell, and a sn-initiatedPSCellChange is not received. successPSCell-Config may be received from the PCell at the time of PSCell Change or PSCell addition. Determining that the UE (102) is configured to provide the successful PSCell change or addition information by the PCell also means determining that the UE (102) is configured to provide the successful PSCell change or addition information by the MCG as it is the PCell that always provides the configuration for MCG in the existing wireless systems and the SPR from the UE (102) determined based on the configuration from PCell is used for optimizing the PSCell mobility configurations from the MN (configured in MCG). The successPSCell-Config is used when the SN is added or modified in an NR-DC. It helps configure a successful PSCell in an NR SN setup. The sn-initiatedPSCellChange is a feature that allows the SN to initiate the PSCell change without waiting for the MN.

[0080] In an embodiment, the SPR handling controller (110) determines that the UE (102) is configured to provide the successful PSCell change or addition information by the PSCell. This is determined if the successPSCell-Config is setup, the successPSCell-Config is received from the PSCell, and the sn-initiatedPSCellChange is not received. successPSCell-Config may be configured by the SN before sending sn-InitiatedPSCellChange in a SCG RRCReconfiguration message. By identifying that the successPSCell-Config for setting up SPR configuration is received in SCG RRCReconfiguration. The UE (102) determines that the SPR configuration is from source PSCell even though there is no presence of sn-initiatedPSCellChange.

[0081] In an embodiment, the SPR handling controller (110) determines that the UE (102) is configured to provide the successful PSCell change or addition information by a source PSCell of the PSCell. This is determined if the successPSCell-Config is setup and the sn-initiatedPSCellChange is received. The source PSCell refers to a primary serving cell on the SN before a PSCell change occurs. It carries user-plane data and sometimes control-plane signaling for the UE (102) from SN. This embodiment allows the SN to send the successPSCell-Config through the PCell, for instance at the time of PSCellChange. SN can send the successPSCell-Config to MN and MN sends the same to the UE (102) through the MCG RRCReconfiguration from the PCell during a SN initiated PSCellChange. MN also includes sn-initiatedPSCellChange in this case. By identifying the presence of sn-initiatedPSCellChange, the SPR handling controller (110) determines that the received SPR configuration which is setup is from source PSCell even though it is received from the PCell.

[0082] In an embodiment, the SPR handling controller (110) determines that the UE (102) is configured to provide the successful PSCell change or addition information by the source PSCell. This is determined if the sn-initiatedPSCellChange is received and successPSCell-Config is already configured for the SCG. If the SPR handling controller (110) has already received successPSCell-Config for setting up SPR configuration from SCG, the SPR handling controller (110) checks the presence of the sn-initiatedPSCellChange and determines that the configuration is from source PSCell when it is present. The SCG refers to a group of cells (PSCells) managed by the SN. The SCG is mainly used for offloading traffic and increasing data rates.

[0083] Determining that the UE (102) is configured to provide the successful PSCell change or addition information by the PSCell also means determining that the UE (102) is configured to provide the successful PSCell change or addition information by the SCG as the SPR from the UE (102) determined based on the configuration from PSCell is used for optimizing the PSCell mobility configurations from the SN. Determining that the UE (102) is configured to provide the successful PSCell change or addition information by the PSCell also means determining that the UE (102) is configured to provide the successful PSCell change or addition information by the source PSCell, as the T310 configuration and T312 configurations can be provided by source PSCell or PCell.

[0084] In an embodiment, the SPR handling controller (110) determines that the UE (102) is not configured to provide the successful PSCell change or addition information by a MCG. This is determined if the successPSCell-Config is set to release and the successPSCell-Config is received from the PCell. While the SPR handling controller (110) determines that the UE (102) is configured to provide the successful PSCell change or addition information by a MCG depending on the sn-InitiatedPSCellChange configuration and whether the PCell has send successPSCell-Config for setting up the configuration, the determination of that the UE (102) is not configured to provide the successful PSCell change or addition information by a MCG is made solely based on whether the PCell has send successPSCell-Config for releasing the configuration, so as to simplify the network co-ordination required for the release of SPR configuration. The MCG includes the PCell and can also include additional secondary cells (SCells). The MCG is mainly used for managing initial access, mobility, and core network connectivity.

[0085] In an embodiment, the SPR handling controller (110) determines that the UE (102) it is not configured to provide the successful PSCell change or addition information by the SCG. This is determined if the successPSCell-Config is set to release and the successPSCell-Config is received from the PSCell. While the SPR handling controller (110) determines that the UE (102) is configured to provide the successful PSCell change or addition information by a SCG depending on the sn-InitiatedPSCellChange configuration and whether the PSCell has send successPSCell-Config for setting up the configuration, the determination of that the UE (102) is not configured to provide the successful PSCell change or addition information by a SCG is made solely based on whether the PSCell has send successPSCell-Config for releasing the configuration so as to simplify the network co-ordination required for the release of SPR configuration. The PSCell change occurs when the UE (102) is moved from one PSCell to another PSCell within a SN of the wireless network. The PSCell change can lead to an improved signal strength, load balancing, mobility, and better inference management. The PSCell addition occurs when the SN is added and a PSCell is assigned to the UE (102).

[0086] In an embodiment, the SPR handling controller (110) performs actions for the SPR based on determination of that the UE (102) is configured or not configured to provide the successful PSCell change or addition information. For instance, the SPR handling controller (110) skips a configuration of the UE (102) by a source PSCell and a target PSCell of the PSCell to provide a successful PSCell change information or a PSCell addition information while reporting the SPR. This occurs when the successPSCell-Config is received from the PSCell. Else, the SPR handling controller (110) skips the configuration of the UE (102) by the PCell to provide the successful PSCell change information or the PSCell addition information while reporting the SPR. This occurs when the successPSCell-Config is received from the PCell.

[0087] Fig. 2 is a flow diagram that illustrates the UE (102) determining whether and how the UE (102) is configured to provide SPR information according to an embodiment as disclosed herein. The flow diagram includes steps (202-204). Each step is explained in further detail below.

[0088] At step (202), the UE (102) receives a successPSCell-Config set as setup in an OtherConfig. At step (204), it is determined that the UE (102) is configured to provide a successful PSCell change or addition information by a source PSCell or Pcell and / or a target PSCell based on configured thresholds. Upon determination of successful PSCell change or addition report, if the target PSCell has configured thresholds, the UE (102) considers itself to be configured by the target PSCell to provide the successful PSCell change or addition information.

[0089] Fig. 3 is a flow diagram that illustrates the UE (102) handling the successPSCell-Config set as release according to an embodiment as disclosed herein. The flow diagram includes steps (302-312). Each step is explained in further detail below.

[0090] At step (302), the UE (102) receives a successPSCell-Config set as release. At step (304), it is determined whether the successPSCell-Config is received from the PSCell. If yes, then at step (306), the UE (102) considers itself to not be configured by the source PSCell and the target PSCell to provide the successful PSCell change or addition information. In other words, the UE (102) considers itself not to be configured by the SCG to provide the successful PSCell change or addition information. If no, then at step (308), it is determined whether a sn-InitiatedPSCellChange is included in the received otherConfig message. If no, then at step (310), the UE (102) considers itself to not be configured by the PCell to provide the successful PSCell change or addition information. If yes, then at step (312), the UE (102) considers itself to not be configured by the source PSCell to provide the successful PSCell change or addition information.

[0091] Fig. 4 is a flow diagram that illustrates the UE (102) handling SPR configuration at the SPR determination according to an embodiment as disclosed herein. The flow diagram includes steps (402-406). Each step is explained in further detail below.

[0092] At step (402), it is determined whether the SPR is at PSCellChange or PSCellAddition. At step (404), it is determined whether the SPR configuration is configured by a target PSCell including a T310 threshold or a T312 threshold. At step (406), the UE (102) considers itself to be configured to provide the successful PSCell change or addition information by the source PSCell. This occurs when the SPR configuration is configured by the target PSCell including the T310 threshold or T312 threshold.

[0093] Fig. 5 is a flow diagram that illustrates using T310 / T312 thresholds from the target PSCell to determine the SPR according to an embodiment as disclosed herein. The flow diagram includes steps (502-506). Each step is explained in further detail below.

[0094] At step (502), T304 and T312 thresholds for SCG are received from the source PSCell, the PCell, and the target PSCell. T304 refers to a handover preparation timer. T304 is used to control the time the UE (102) waits for a handover command after receiving a handover preparation message. T312 refers to a radio link failure (RLF) timer. T312 is used to monitor a physical RLF. At step (504), the T310 threshold and T312 threshold is received from Target-r18. At step (506), the T304 and T312 thresholds are applied for SCG from the target PSCell for SPR determination.

[0095] Fig. 6 is a flow diagram that illustrates determination of a successful PSCellChange or addition information according to an embodiment as disclosed herein. The flow diagram includes steps (602-604). Each step is explained in further detail below.

[0096] At step (602), the UE (102) receives the sn-InitiatedPSCellChange configured in the last applied RRCReconfiguration with reconfigurationWithSync. The sn-InitiatedPSCellChange is part of the RRCReconfiguration and is related to the process of changing the PSCell in a multi-cell environment. This is necessary for optimizing network performance and ensuring seamless connectivity. At step (604), the T310 and / or T312 configuration are applied from the source PSCell to determine successful PSCellChange orAddition information.

[0097] Fig. 7 is a flow diagram that illustrates a PSCell configuration to provide successful PSCellChange or addition information according to an embodiment as disclosed herein. The flow diagram includes steps (702-706). At step (702), the UE (102) receives a successPSCell-Config. At step (704), it is determined whether the successPSCell-Config is received in SCG reconfiguration and it includes T310 / T312 thresholds. Then at step (706), the UE (102) considers itself to be configured by the source PSCell to provide successful PSCellChange or addition information.

[0098] In an embodiment, if the UE (102) receives a configuration for reporting successful PSCell change or addition information, such as successPSCell-Config (or successPSCell-Config which is setup) in NR without including thresholdPercentageT304-SCG, the UE (102) considers that it is not configured by the target PSCell to provide the successful PSCell change or addition information.

[0099] In an embodiment, in TS 38.331,

[0100] 1> if the received otherConfig includes the successPSCell-Config:

[0101] 2> if thresholdPercentageT304-SCG is included:

[0102] 3>consider itself to be configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0103] 2>else

[0104] 3>consider itself to be not configured by the target PSCell to provide the successful PSCell change or addition information;

[0105] In an embodiment, if the UE (102) receives the sn-InitiatedPSCellChange in the OtherConfig in a RRCReconfiguration message, it checks if one of the thresholds for T310 or T312 for evaluations for reporting SPR such as thresholdPercentageT310-SCG or thresholdPercentageT312-SCG (or equivalent IEs / message) is included in the same OtherConfig (or the same RRCReconfiguration message). If so, the UE (102) considers itself to be configured by the target PSCell to provide the successful PSCell change or addition information. In an embodiment, the thresholds for T310 or T312 can be received in successPSCell-Config (or successPSCell-Config which is setup).

[0106] In an embodiment, according to TS 38.331,

[0107] 1>if the received otherConfig includes the successPSCell-Config:

[0108] 2>if sn-InitiatedPSCellChange is included in the received otherConfig:

[0109] 3>if thresholdPercentageT310-SCG or thresholdPercentageT312-SCG is included:

[0110] 4>consider itself to be configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0111] In an embodiment, if the UE (102) receives one of the thresholds for T310 or T312 such as thresholdPercentageT310-SCG or thresholdPercentageT312-SCG for evaluations for reporting SPR included in OtherConfig in a RRCReconfiguration message and the sn-InitiatedPSCellChange is not included in the OtherConfig and if the thresholdPercentageT310-SCG or thresholdPercentageT312-SCG are included in SCG RRCReconfiguration message, the UE (102) considers itself to be configured by the source PSCell to provide the successful PSCell change or addition information. In an embodiment, the thresholds for T310 or T312 can be received in successPSCell-Config (or successPSCell-Config which is setup).

[0112] In an embodiment, if the UE (102) receives one of the thresholds for T310 or T312 such as thresholdPercentageT310-SCG or thresholdPercentageT312-SCG for evaluations for reporting the SPR included in the OtherConfig in a RRCReconfiguration message and the sn-InitiatedPSCellChange is not included in the OtherConfig and if the thresholdPercentageT310-SCG or thresholdPercentageT312-SCG are included in MCG RRCReconfiguration message, the UE (102) considers itself to be configured by the PCell to provide the successful PSCell change or addition information. In an embodiment, the thresholds for T310 or T312 can be received in the successPSCell-Config (or successPSCell-Config which is setup).

[0113] In an embodiment, MN can preconfigure the UE (102) with T310 or T312 thresholds, i.e. .can send in RRCReconfiguration message before the PSCellChange.

[0114] In an embodiment, if the UE (102) receives the OtherConfig and the sn-InitiatedPSCellChange is not included in the received otherConfig and only T304 threshold for evaluations for reporting SPR is configured (i.e. T310 / T312 thresholds are not configured), the UE (102) considers itself not to be configured by the PSCell or the PCell to provide the successful PSCell change or addition information. In an embodiment, the thresholds for T304 can be received in successPSCell-Config (or successPSCell-Config which is setup).

[0115] In an embodiment, according to TS 38.331,

[0116] 2> if sn-InitiatedPSCellChange is included in the received otherConfig:

[0117] 3> if thresholdPercentageT310-SCG or thresholdPercentageT312-SCG is included:

[0118] 4>consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0119] 2> else if sn-InitiatedPSCellChange is not included in the received otherConfig:

[0120] 3> if thresholdPercentageT310-SCG or thresholdPercentageT312-SCG is included in the received otherConfig:

[0121] 4>if thresholdPercentageT310-SCG or thresholdPercentageT312-SCG are received in SCG RRCReconfiguration message:

[0122] 5> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0123] 4>else:

[0124] 5> consider itself to be configured by the PCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0125] In an embodiment, upon receiving otherConfig including the successPSCell-Config, the UE (102) checks if the successPSCell-Config is setup. If so, it decides whether the configuration is by PCell or source PSCell and / or target PSCell.

[0126] In an embodiment, according to TS 38.331,

[0127] 1> if the received otherConfig includes the successPSCell-Config:

[0128] 2> if the successPSCell-Config is setup:

[0129] 3> if thresholdPercentageT304-SCG is included:

[0130] 4>consider itself to be configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0131] 3>else:

[0132] 4>consider itself to be not configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0133] 3>if sn-InitiatedPSCellChange is included in the received otherConfig:

[0134] 4>if thresholdPercentageT310-SCG or thresholdPercentageT312-SCG is included:

[0135] 5> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0136] 3> else if sn-InitiatedPSCellChange is not included in the received otherConfig:

[0137] 4>if thresholdPercentageT310-SCG or thresholdPercentageT312-SCG is included in the received otherConfig:

[0138] 5> if thresholdPercentageT310-SCG or thresholdPercentageT312-SCG are received in SCG RRCReconfiguration message:

[0139] 6> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0140] 5> else:

[0141] 6> consider itself to be configured by the PCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0142] In an embodiment, successPSCell-Config is not provided as SetupRelease. In an embodiment, network only sets successPSCell-Config as Setup.

[0143] In an embodiment, if the UE (102) receives the successPSCell-Config which is release, the UE (102) considers itself to be not configured by one of the PCell, source PSCell, target PSCell based on the sn-InitiatedPSCellChange flag and the cell.

[0144] In an embodiment, if the UE (102) receives the successPSCell-Config as release from a PSCell, it considers itself to be not configured by the source PSCell and target PSCell to provide the successful PSCell change or addition information. In other words, the UE (102) which receives the successPSCell-Config as release from a PSCell, considers itself to be not configured by the SCG for providing the successful PSCell change or addition information. This embodiment allows the network to release the SPR configuration for the PSCell without inter-node signaling between SN and MN.

[0145] In an embodiment, if the UE (102) receives the successPSCell-Config as release from source PSCell, it considers itself to be not configured by the source PSCell.

[0146] In an embodiment, if the UE (102) receives the successPSCell-Config as release from target PSCell, it considers itself to be not configured by the target PSCell.

[0147] In an embodiment, if the UE (102) receives the successPSCell-Config as release from PCell, it considers itself to be not configured by the PCell. In other words, the UE (102) which receives the successPSCell-Config as release from a PSCell, considers itself to be not configured by the MCG for providing the successful PSCell change or addition information. This embodiment allows the network to release the SPR configuration for the PCell without inter-node signaling between MN and SN.

[0148] In an embodiment, if the UE (102) receives the successPSCell-Config as release from PCell and if the sn-InitiatedPSCellChange is included in the received otherConfig, the UE (102) considers itself to be not configured by the source PSCell to provide the successful PSCell change or addition information.

[0149] In an embodiment, if the UE (102) receives the successPSCell-Config as release from PCell and if the sn-InitiatedPSCellChange is not included in the received otherConfig, the UE (102) considers itself to be not configured by the PCell to provide the successful PSCell change or addition information.

[0150] In an embodiment, if the UE (102) receives the successPSCell-Config as release, the UE (102) considers itself to be not configured by the source PSCell, target PSCell and PCell to provide the successful PSCell change or addition information.

[0151] In an embodiment, according to TS 38.331,

[0152] 1> if the received otherConfig includes the successPSCell-Config:

[0153] 2> if the successPSCell-Config is release:

[0154] 3> if successPSCell-Config is received from a PSCell:

[0155] 4>Consider itself to be not configured by the source PSCell and target PSCell to provide the successful PSCell change or addition information;

[0156] 3> else:

[0157] 4> if sn-InitiatedPSCellChange is included in the received otherConfig:

[0158] 5> consider itself to be not configured by the source PSCell to provide the successful PSCell change or addition information;

[0159] 4> else:

[0160] 5> consider itself to be not configured by the PCell to provide the successful PSCell change or addition information;

[0161] In an embodiment, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the source PSCell during SCG failure. In an embodiment, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the source PSCell upon transmission of SCGFailureInformation message.

[0162] In an embodiment, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the PCell and source PSCell and target PSCell during MR-DC release. In an embodiment, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the PCell and source PSCell and target PSCell upon MR-DC release if the UE (102) is configured with NR SCG.

[0163] In an embodiment, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the PCell and source PSCell and target PSCell during RRC Reestablishment. In an embodiment, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the PCell and source PSCell and target PSCell upon initiation of RRC Reestablishment.

[0164] In an embodiment, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the PCell and source PSCell and target PSCell during RRC Resume. In an embodiment, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the PCell and source PSCell and target PSCell upon initiation of RRC Resume.

[0165] In an embodiment, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the PCell during PCell change. In an embodiment, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the PCell upon the reconfigurationWithSync in spCellConfig of an MCG, if the UE (102) supports logging the successful PSCell change or addition information.

[0166] In an embodiment, upon determination of successful PSCell change or addition report, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the source PSCell, if the T310 and T312 thresholds are not configured by the target PSCell.

[0167] In an embodiment, upon determination of successful PSCell change or addition report, the UE (102) considers itself not to be configured to provide the successful PSCell change or addition information configured by the target PSCell.

[0168] In an embodiment, upon determination of successful PSCell change or addition report,if the target PSCell has configured thresholdPercentageT310-SCG or thresholdPercentageT312-SCG, the UE (102) considers itself to be configured by the source PSCell to provide the successful PSCell change or addition information.

[0169] In an embodiment,in TS 38.331,

[0170] Actions for the successful PSCell change or addition report determination

[0171] <Steps for including the SPR>

[0172] 1> release successPSCell-Config configured by the source PSCell if available and thresholdPercentageT304-SCG if configured by the target PSCell.

[0173] 1>consider itself not to be configured by target PSCell to provide the successful PSCell change or addition information.

[0174] 1> if thresholdPercentageT310-SCG or thresholdPercentageT312-SCG are configured by the target PSCell:

[0175] 2> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0176] The UE (102) can discard the successful PSCell change or addition information, i.e., release the UE variable VarSuccessPSCell-Report, 48 hours after the last successful PSCell change or addition information is added to the VarSuccessPSCell-Report or upon deregistration from the network as specified in

[0043] .

[0177] In an embodiment, according to TS 38.331

[0178] 1> if the received otherConfig includes the successPSCell-Config

[0179] 2> If succeessPSCellConfig is set as setup:

[0180] 3> if thresholdPercentageT304-SCG is included:

[0181] 1> consider itself to be configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0182] 3>else

[0183] consider itself to be not configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0184] 3>if thresholdPercentageT310-SCG or thresholdPercentageT312-SCG are included:

[0185] 4>consider itself to be configured by a source cell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0186] 3>else

[0187] 4>consider itself to be not configured by a source cell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0188] 2>else:

[0189] 3>If successPSCellConfig is received in otherConfig configured by target PSCell

[0190] 4>consider itself to be not configured by the target PSCell to provide the successful PSCell change or addition information.

[0191] 3> else

[0192] 4> consider itself to be not configured by a source cell to provide the successful PSCell change or addition information.

[0193] 1>if the UE (102) is configured with thresholdPercentageT310-SCG or thresholdPercentageT312-SCG while connected to the source PSCell

[0194] 2> if sn-InitiatedPSCellChange is included in the received otherConfig included in the last applied RRCReconfiguration with reconfigurationWithSync or the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the PSCellChange:

[0195] 3> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0196] 2> else

[0197] 3> consider itself to be configured by the PCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0198] In an embodiment, the IEs or messages in the embodiments such as successPSCellConfig and the sn-InitiatedPSCellChange or RRCReconfiguration in NR also signifies any such IEs or messages which has the same / similar functionality in any other technology like 4G LTE or 6G.

[0199] In an embodiment, the network can provide the sn-InitiatedPSCellChange in the RRCReconfiguration with reconfigurationWithSync for the SCG and not only in the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG as in the current system.

[0200] In an embodiment, the UE (102) considers the sn-InitiatedPSCellChange provided in the RRCReconfiguration with reconfigurationWithSync for SPR determination. In other words, the UE (102) considers the sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for SPR determination.

[0201] In an embodiment, according to TS 38.331,

[0202] 5.7.10.7 Actions for the successful PSCell change or addition report determination

[0203] The UE (102) shall for the PSCell:

[0204] 1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconfiguration message for the SCG including the reconfigurationWithSync, is greater than thresholdPercentageT304-SCG if included in the successPSCell-Config received before executing the last reconfiguration with sync for the SCG; or

[0205] 1> if sn-InitiatedPSCellChange is configured in the last applied RRCReconfiguration with reconfigurationWithSync or the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or

[0206] 1> if sn-InitiatedPSCellChange is configured in the last applied RRCReconfiguration with reconfigurationWithSync or the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:

[0207] 1> if sn-InitiatedPSCellChange is not configured in the last applied RRCReconfiguration with reconfigurationWithSync or the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or

[0208] 1> if sn-InitiatedPSCellChange is not configured in the last applied RRCReconfiguration with reconfigurationWithSync or the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:

[0209] 2>various steps for determining SPR.

[0210] In an embodiment, according to TS 38.331,

[0211] 1> if the UE (102) is configured by the source PSCell to provide the successful PSCell change or addition information and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or

[0212] 1> if the UE (102) is configured by the source PSCell to provide the successful PSCell change or addition information and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:

[0213] 1> if the UE (102) is configured by the PCell to provide the successful PSCell change or addition information and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or

[0214] 1> if the UE (102) is configured by the PCell to provide the successful PSCell change or addition information and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:

[0215] 2>various steps for determining SPR.

[0216] In an embodiment, according to TS 38.331,

[0217] 1> if sn-InitiatedPSCellChange is configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or

[0218] 1> if sn-InitiatedPSCellChange is configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:

[0219] 1> if sn-InitiatedPSCellChange is not configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or

[0220] 1> if sn-InitiatedPSCellChange is not configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:

[0221] 1> various steps for determining SPR.

[0222] In an embodiment according to TS 38.331,

[0223] 1> if sn-InitiatedPSCellChange is configured during this PSCellChange and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or

[0224] 1> if sn-InitiatedPSCellChange is configured during this PSCellChange and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:

[0225] 1> if sn-InitiatedPSCellChange is not configured during this PSCellChange and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or

[0226] 2> if sn-InitiatedPSCellChange is not configured during this PSCellChange and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE (102) was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:

[0227] 3> various steps for determining SPR.

[0228] In an embodiment, the network node configures the UE (102) whether the T310-SCG threshold (thresholdPercentageT310-SCG-r18) and T312-SCG threshold (thresholdPercentageT312-SCG-r18) in the target PScell (e.g. C2) configuration can be used instead of T310-SCG thresholds and T312-SCG thresholds in the source PScell (e.g. C1) configuration (or PCell configuration) for determining the successful PSCell Change or Addition Information for the successful PSCellChange from source PSCell C1 to target PSCell C2. The UE (102) uses T310-SCG thresholds and T312-SCG thresholds in the target PSCell (e.g. C2) configuration based on this configuration. If this configuration is not available, the UE (102) uses T310-SCG thresholds and T312-SCG thresholds in the source PSCell (e.g. C1) configuration (or PCell configuration). In an embodiment, this configuration is applicable for all the parameters from the source PSCell (or PCell) which are by default used for determining the successful PSCell Change or Addition Information.

[0229] In an embodiment, the network node configures the UE (102) to use the T310-SCG threshold (thresholdPercentageT310-SCG-r18) and T312-SCG threshold (thresholdPercentageT312-SCG-r18) in the target PScell (e.g. C2) configuration for determining the successful PSCell Change or Addition Information for the PSCellChange from a source PSCell C1 to target PSCell C2. The UE (102) uses T310-SCG threshold and T312-SCG threshold in the target PScell configuration (e.g. C2) if the above configuration is available. If the above configuration is not available, the UE (102) uses T310-SCG threshold and T312-SCG threshold in the source PScell (e.g. C1) configuration (or PCell configuration). In an embodiment, the configuration informs the UE (102) to use only target cell parameters for determining the successful PSCell Change or Addition Information.

[0230] In an embodiment, the network node indicates to the UE (102) which of the T310-SCG threshold (thresholdPercentageT310-SCG-r18) and T312-SCG threshold (thresholdPercentageT312-SCG-r18) configurations (i.e. in the target PScell (e.g. C2) configuration or the T310-SCG threshold and T312-SCG threshold in the source PScell(e.g. C2) configuration or PCell configuration) to be used for determining the successful PSCell Change or Addition Information for the PSCellChange from source PSCell C1 to target PSCell C2. The UE (102) uses the configuration indicated by the network node.

[0231] In an embodiment, the network node configures the UE (102) to use the T310-SCG threshold (thresholdPercentageT310-SCG-r18) and T312-SCG threshold (thresholdPercentageT312-SCG-r18) and T304-SCG threshold (thresholdPercentageT304-SCG-r18) in the source PScell (e.g. C1) configuration for determining the successful PSCell Change or Addition Information for the PSCellChange from a source PSCell C1 to target PSCell C2. The UE (102) uses T310-SCG threshold and / or T312-SCG threshold and / or T304-SCG threshold in the source PSCell (e.g. C1) configuration if configured. If not configured, the UE (102) uses T310-SCG threshold and / or T312-SCG threshold and / or in the target PScell (e.g. C2) configuration. In an embodiment, the configuration is applicable for all the parameters from the target PScell which are by default used for determining the successful PSCell Change or Addition Information.

[0232] In an embodiment, the configuration used by the network node to inform the UE (102) to use the T310-SCG threshold (thresholdPercentageT310-SCG-r18) and T312-SCG threshold (thresholdPercentageT312-SCG-r18) configured by target PSCell as in the above embodiments is an Information Element (IE) such as a flag or enumerated. If the information element is included (or if the flag is true), the UE (102) considers T310-SCG threshold and T312-SCG threshold configured by the target PSCell. In an embodiment, this IE can be send over SRB3. In an embodiment, this IE can be send over SRB1. In an embodiment, this IE can be send when the configuration for PSCellChange is send or when the configuration for determining the successful reporting of PSCellChange or PSCell addition information is send. In an embodiment, this IE is sent by target PSCell.

[0233] In an example, the UE (102) moves from PSCell C1 to PSCell C2. PCell is C3. The UE (102) receives T310-SCG threshold (thresholdPercentageT310-SCG-r18) and T312-SCG threshold (thresholdPercentageT312-SCG-r18) from source PSCell C1. The UE (102) also receives T310-SCG threshold and T312-SCG threshold from target PSCell C2. In the current system, the UE (102) uses the T310-SCG threshold and T312-SCG threshold from source PSCell C1 to determine the SPR. According to our embodiments, the network can instruct the UE (102) which T310-SCG threshold or T312-SCG threshold to be used. The network can instruct the UE (102) to use the thresholds from target PSCell, and the UE (102) uses T310-SCG threshold and T312-SCG threshold received from target PScell C2 for determining the successful PSCell Change or Addition Information during the PSCellChange from C1 to C2. If there is no specific instruction from the network to use the thresholds from targetC, the UE (102) uses T310-SCG threshold and T312-SCG threshold received from source PSCell C1.

[0234] In an embodiment, according to TS 38.331,

[0235] SuccessPSCell-Config-r18:= SEQUENCE {

[0236] thresholdPercentageT304-SCG-r18 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0237] thresholdPercentageT310-SCG-r18 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0238] thresholdPercentageT312-SCG-r18 ENUMERATED {p20, p40, p60, p80, spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0239] uset310T312Threshold-FromTarget-r18 ENUMERATED {true} OPTIONAL, --Need R

[0240] ...

[0241] }

[0242] Use T310, T312 Threshold-FromTarget-r18: If this field is included in target PSCell configuration, the UE (102) uses thresholdPercentageT310-SCG-r18 and thresholdPercentageT312-SCG-r18 configured by the targetPSCell (instead of the values in source PSCell configuration) during the determination of successful PSCell Addition or Change Information.

[0243] 5.3.5.9 Other configuration

[0244] 1> if the received otherConfig includes the successPSCell-Config:

[0245] 2> if useT310T312Threshold-FromTarget-r18 is included

[0246] 3>consider the thresholdPercentageT304-SCG-r18 and thresholdPercentageT312-SCG-r18, if included as configured by the source PSCell.

[0247] Alternatively,

[0248] 5.3.5.9 Other configuration

[0249] 1> if the received otherConfig from target PSCell includes the successPSCell-Config:

[0250] 2> if useT310T312Threshold-FromTarget-r18 is included

[0251] 3>consider the thresholdPercentageT304-SCG-r18 and thresholdPercentageT312-SCG-r18, if included as configured by the source PSCell.

[0252] In an embodiment, if the UE (102) receives useT310T312Threshold-FromTarget-r18, the UE (102) uses thresholdPercentageT310-SCG-r18 and thresholdPercentageT312-SCG-r18 from target PSCell for determining SPR. The UE (102) cannot use any thresholdPercentageT310-SCG-r18 and thresholdPercentageT312-SCG-r18 from source PSCell or PCell for the PSCellChange from current source to target.

[0253] In an embodiment, useT310T312Threshold-FromTarget-r18 is included only by target PSCell.

[0254] In an embodiment, if the UE (102) receives thresholdPercentageT310-SCG-r18 and / or thresholdPercentageT312-SCG-r18 from target PSCell (e.g. C2) over SRB3, the UE (102) uses these thresholds for determining the successful PSCell Addition or Change information from a source PSCell (e.g. C1) to the target PSCell C2.

[0255] In an embodiment, source PSCell preconfigures the thresholdPercentageT310-SCG-r18 and / or thresholdPercentageT312-SCG-r18, if the PSCellChange is triggered over SRB3. I.e. the source cell sends thresholdPercentageT310-SCG-r18 and / or thresholdPercentageT312-SCG-r18 in an RRCReconfiguration message from the source cell before the RRCReconfiguration including ReconfigurationWithSync from the target PSCell is forwarded to the UE (102).

[0256] In an embodiment, source SN can trigger PSCell change with MN involvement to configure thresholdPercentageT310-SCG-r18 and / or thresholdPercentageT312-SCG-r18 in the RRCReconfiguration including ReconfigurationWithSync.

[0257] In an embodiment, source SN can trigger PSCell change with MN involvement to configure thresholdPercentageT310-SCG-r18 and / or thresholdPercentageT312-SCG-r18 in the RRCReconfiguration including ReconfigurationWithSync,even when SRB3 is configured and the PSCellChange is Intra-SN PSCellChange.

[0258] In an embodiment, the UE (102) determines whether it is configured by source PSCell or PCell based on the RRCReconfiguration in which OtherConfig doesn't include thresholdPercentageT304-SCG.

[0259] In an embodiment, according to TS 38.331,

[0260] 1> if thresholdPercentageT304-SCG is included:

[0261] 2> consider itself to be configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0262] 2> else:

[0263] 1> if sn-InitiatedPSCellChange is included

[0264] <Other aspects>

[0265] In an embodiment, the UE (102) determines whether it is configured by source PSCell or PCell based on the RRCReconfiguration in which OtherConfig doesn't include thresholdPercentageT304-SCG except when it includes useT310T312Threshold-FromTarget-r18.

[0266] In an embodiment, if successPSCell-Config is included in SCG RRCReconfiguration, the UE (102) considers itself to be configured by the source PSCell to provide the successful PSCell change or addition information. If successPSCell-Config is not included in SCG RRCReconfiguration, the UE (102) determines whether it is configured by the source PSCell or PCell to provide the successful PSCell change or addition information, based on the sn-InitiatedPSCellChange flag.

[0267] In an embodiment, if successPSCell-Config is included in SCG RRCReconfiguration and thresholdPercentageT310-SCG-r18 and / or thresholdPercentageT312-SCG-r18 are configured, the UE (102) considers itself to be configured by the source PSCell to provide the successful PSCell change or addition information. In other words, the UE (102) determines that it is configured to provide the successful PSCell change or addition information by the PSCell if the successPSCell-Config is Setup and the successPSCell-Config is received from the PSCell and the sn-initiatedPSCellChange is not received. The UE (102) also determines that it is configured to provide the successful PSCell change or addition information by the source PSCell if the successPSCell-Config is Setup and the sn-initiatedPSCellChange is received.

[0268] In an embodiment, if successPSCell-Config is not included in SCG RRCReconfiguration and thresholdPercentageT310-SCG-r18 and / or thresholdPercentageT312-SCG-r18 are configured, the UE (102) determines whether it is configured by the source PSCell or PCell to provide the successful PSCell change or addition information, based on the sn-InitiatedPSCellChange flag.

[0269] In an embodiment, according to TS 38.331,

[0270] 2>If successPSCell-Config is included in SCG RRCReconfiguration and thresholdPercentageT310-SCG-r18 and / or thresholdPercentageT312-SCG-r18 are configured

[0271] 3> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7; i.e. The UE (102) considers itself to be configured by the source PSCell to provide the successful PSCell change or addition information when successPSCell-Config is included in SCG RRCReconfiguration when the sn-initiatedPSCellChange is received and also when the sn-initiatedPSCellChange is not received. In an embodiment, according to TS 38.331,

[0272] 2>If successPSCell-Config is included in SCG RRCReconfiguration

[0273] 3> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0274] 2>else:

[0275] 3>if sn-InitiatedPSCellChange is included in the received otherConfig:

[0276] 4> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0277] 3> else if sn-InitiatedPSCellChange is not included in the received otherConfig:

[0278] 4> consider itself to be configured by the PCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0279] In an embodiment, according to TS 38.331,

[0280] 1> if the successsPSCell-Config is setup

[0281] 2> if thresholdPercentageT304-SCG is included:

[0282] 3> consider itself to be configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0283] 2> if sn-InitiatedPSCellChange is included in the received otherConfig:

[0284] 3> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0285] 2> else if sn-InitiatedPSCellChange is not included in the received otherConfig:

[0286] 2>

[0287] 3> consider itself to be configured by the PCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7;

[0288] 3> else if the successsPSCell-Config is release

[0289] 1> consider itself to be not configured by the SpCells corresponding to the cell group which included the successsPSCell-Config.

[0290] This means that the UE (102) considers itself to be not configured the cell group which sends the successsPSCell-Config as release, irrespective of whether the sn-InitiatedPSCellChange is included or not.

[0291] Fig. 8 is a flow diagram that illustrate a method for handling a SPR in a wireless network according to an embodiment as disclosed herein. The method includes steps (802-816). Each step is explained in further detail below.

[0292] At step (802), the UE (102) receives a configuration to report a successful PSCell change or addition information to a network apparatus and optionally a configuration that informs whether a PSCell change or a conditional PSCellChange (CPC) is initiated by a secondary node (SN) or not from a PSCell or a PCell. The PSCell designates the primary serving cell of the SN to which the UE (102) is linked across various network nodes, such as LTE and NR. The PCell represents the primary serving cell for the UE (102) in a connection involving a single node. The PCell functions as a component of the MN when dual connectivity is established.

[0293] At step (804), the UE (102) determines that the UE (102) is configured to provide the successful PSCell change or addition information by the PCell. This is determines if a successPSCell-Config is setup, the successPSCell-Config is received from the PCell, and a sn-initiatedPSCellChange is not received. The successPSCell-Config is utilized when the SN is either added or modified within an NR-DC. It facilitates the configuration of a successful PSCell in an NR SN environment. The sn-initiatedPSCellChange feature enables the SN to initiate the PSCell change independently, without the need to wait for the MN.

[0294] At step (806), the UE (102) determines that the UE (102) is configured to provide the successful PSCell change or addition information by the PSCell. This is determined if the successPSCell-Config is setup, the successPSCell-Config is received from the PSCell, and the sn-initiatedPSCellChange is not received.

[0295] At step (808), the UE (102) determines that the UE (102) is configured to provide the successful PSCell change or addition information by a source PSCell of the PSCell. This is determined if the successPSCell-Config is setup and the sn-initiatedPSCellChange is received. The PSCell designation pertains to the primary serving cell on the signalling network prior to any changes in the PSCell. It is responsible for transmitting user-plane data and control-plane signalling for the UE (102).

[0296] At step (810), the UE (102) determines that the UE (102) is configured to provide the successful PSCell change or addition information by the source PSCell. This is determined if the sn-initiatedPSCellChange is received and successPSCell-Config is already configured for the SCG. The SCG represents a collection of cells (PSCells) directed by the SN. Its primary purpose is to offload traffic and enhance data transmission rates.

[0297] At step (812), the UE (102) determines that the UE (102) is not configured to provide the successful PSCell change or addition information by a MCG. This is determined if the successPSCell-Config is set to release and the successPSCell-Config is received from the PCell. The MCG incorporates the PCell and may also incorporate supplementary secondary cells (SCells). Its primary function is to direct initial access, mobility, and connectivity to the core network.

[0298] At step (814), the UE (102) determines that the UE (102) it is not configured to provide the successful PSCell change or addition information by the SCG. This is determined if the successPSCell-Config is set to release and the successPSCell-Config is received from the PSCell. The PSCell change takes place when the UE (102) shifts from one PSCell to another within the SN of the wireless network. This PSCell change can enhance signal strength, facilitate load balancing, improve mobility, and optimize interference management. Additionally, the PSCell addition happens when a new SN is introduced, resulting in a PSCell being allocated to the UE (102).

[0299] At step (816), the UE (102) performs actions for the SPR based on determination of that the UE (102) is configured or not configured to provide the successful PSCell change or addition information. For instance, the UE (102) skips a configuration of the UE (102) by a source PSCell and a target PSCell of the PSCell to provide a successful PSCell change information or a PSCell addition information while reporting the SPR. This occurs when the successPSCell-Config is received from the PSCell. Else, the UE (102) skips the configuration of the UE (102) by the PCell to provide the successful PSCell change information or the PSCell addition information while reporting the SPR. This occurs when the successPSCell-Config is received from the PCell.

[0300] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by a user equipment (UE) in a communication system, the method comprising:receiving, from a base station, a radio resource control (RRC) reconfiguration message including an other configuration;identifying whether the other configuration includes information indicating whether a primary secondary cell (PSCell) change procedure is initiated by a secondary node (SN) and whether a configuration to report a successful PSCell change or addition information is received in the other configuration; andin case that the information indicating whether the PSCell change procedure is initiated by the SN is not included in the other configuration and in case that the configuration received in the other configuration is set to setup, determining to be configured to provide the successful PSCell change or addition information.2.The method of claim 1, further comprising:in case that the information is included in the other configuration, determining not to be configured to provide the successful PSCell change or addition information.3.The method of claim 1, further comprising:in case that the configuration received in the other configuration is set to release, determining not to be configured to provide the successful PSCell change or addition information to the base station.4.The method of claim 3,wherein in case that the configuration is received from a primary cell (PCell), the UE is determined not to be configured to provide the successful PSCell change or addition information by a master cell group (MCG), andwherein in case that the configuration is received from the PSCell, the UE is determined not to be configured to provide the successful PSCell change or addition information by a secondary cell group (SCG),wherein the configuration includes at least one of a information associated with a T304 timer, a information associated with a T310 timer, or a information associated with a T312 timer,wherein the information associated with the T304 timer is a threshold for a ratio in percentage between an elapsed T304 timer and a configured value of the T304 timer,wherein the information associated with the T310 is a threshold for a ratio in percentage between an elapsed T310 timer and a configured value of the T310 timer, andwherein the information associated with the T312 is a threshold for a ratio in percentage between an elapsed T312 timer and a configured value of the T312 timer.5.A method performed by a base station in a communication system, the method comprising:transmitting, to a user equipment, a radio resource control (RRC) reconfiguration message including an other configuration; andidentifying whether the other configuration includes information indicating whether a primary secondary cell (PSCell) change procedure is initiated by a secondary node (SN) and whether a configuration to report a successful PSCell change or addition information is received in the other configuration;in case that the information indicating whether the PSCell change procedure is initiated by the SN is not included in the other configuration and in case that the configuration received in the other configuration is set to setup, the UE is determined to be configured to provide the successful PSCell change or addition information.6.The method of claim 5,in case that the information is included in the other configuration, the UE is determined not to be configured to provide the successful PSCell change or addition information.7.The method of claim 5,in case that the configuration received in the other configuration is set to release, the UE is determined not to be configured to provide the successful PSCell change or addition information to the base station.8.The method of claim 7,wherein in case that the configuration is received from a primary cell (PCell), the UE is determined not to be configured to provide the successful PSCell change or addition information by a master cell group (MCG), andwherein in case that the configuration is received from the PSCell, the UE is determined not to be configured to provide the successful PSCell change or addition information by a secondary cell group (SCG),wherein the configuration includes at least one of a information associated with a T304 timer, a information associated with a T310 timer, or a information associated with a T312 timer,wherein the information associated with the T304 timer is a threshold for a ratio in percentage between an elapsed T304 timer and a configured value of the T304 timer,wherein the information associated with the T310 is a threshold for a ratio in percentage between an elapsed T310 timer and a configured value of the T310 timer, andwherein the information associated with the T312 is a threshold for a ratio in percentage between an elapsed T312 timer and a configured value of the T312 timer.9.A user equipment (UE) in a communication system, the UE comprising:a transceiver; andat least one processor coupled with the transceiver, the at least one processor is configured to:receive, from a base station, a radio resource control (RRC) reconfiguration message including an other configuration,identify whether the other configuration includes information indicating whether a primary secondary cell (PSCell) change procedure is initiated by a secondary node (SN) and whether a configuration to report a successful PSCell change or addition information is received in the other configuration, andin case that the information indicating whether the PSCell change procedure is initiated by the SN is not included in the other configuration and in case that the configuration received in the other configuration is set to setup, determine to be configured to provide the successful PSCell change or addition information.10.The UE of claim 9, wherein the at least one processor is configured to:in case that the information is included in the other configuration, determine not to be configured to provide the successful PSCell change or addition information.11.The UE of claim 9, wherein the at least one processor is configured to:in case that the configuration received in the other configuration is set to release, determine not to be configured to provide the successful PSCell change or addition information to the base station.12.The UE of claim 11,wherein in case that the configuration is received from a primary cell (PCell), the UE is determined not to be configured to provide the successful PSCell change or addition information by a master cell group (MCG), andwherein in case that the configuration is received from the PSCell, the UE is determined not to be configured to provide the successful PSCell change or addition information by a secondary cell group (SCG),wherein the configuration includes at least one of a information associated with a T304 timer, a information associated with a T310 timer, or a information associated with a T312 timer,wherein the information associated with the T304 timer is a threshold for a ratio in percentage between an elapsed T304 timer and a configured value of the T304 timer,wherein the information associated with the T310 is a threshold for a ratio in percentage between an elapsed T310 timer and a configured value of the T310 timer, andwherein the information associated with the T312 is a threshold for a ratio in percentage between an elapsed T312 timer and a configured value of the T312 timer.13.A base station in a communication system, the base station comprising:a transceiver; andat least one processor coupled with the transceiver, the at least one processor is configured to:transmit, to a user equipment, a radio resource control (RRC) reconfiguration message including an other configuration; andidentify whether the other configuration includes information indicating whether a primary secondary cell (PSCell) change procedure is initiated by a secondary node (SN) and whether a configuration to report a successful PSCell change or addition information is received in the other configuration;in case that the information indicating whether the PSCell change procedure is initiated by the SN is not included in the other configuration and in case that the configuration received in the other configuration is set to setup, the UE is determined to be configured to provide the successful PSCell change or addition information.14.The base station of claim 13,in case that the information is included in the other configuration, the UE is determined not to be configured to provide the successful PSCell change or addition information, andin case that the configuration received in the other configuration is set to release, the UE is determined not to be configured to provide the successful PSCell change or addition information to the base station.15.The base station of claim 14,wherein in case that the configuration is received from a primary cell (PCell), the UE is determined not to be configured to provide the successful PSCell change or addition information by a master cell group (MCG), andwherein in case that the configuration is received from the PSCell, the UE is determined not to be configured to provide the successful PSCell change or addition information by a secondary cell group (SCG),wherein the configuration includes at least one of a information associated with a T304 timer, a information associated with a T310 timer, or a information associated with a T312 timer,wherein the information associated with the T304 timer is a threshold for a ratio in percentage between an elapsed T304 timer and a configured value of the T304 timer,wherein the information associated with the T310 is a threshold for a ratio in percentage between an elapsed T310 timer and a configured value of the T310 timer, andwherein the information associated with the T312 is a threshold for a ratio in percentage between an elapsed T312 timer and a configured value of the T312 timer.

Images