Method for managing successful PSCell change or additional reporting in a wireless communication network and UE

Abstract

The present disclosure relates to a fifth-generation (5G) or sixth-generation (6G) communication system for supporting higher data transmission speeds. A method and a terminal are provided for being performed by a terminal (user equipment, UE) in a wireless communication system. The method comprises the steps of storing first information regarding a successful PSCell (primary secondary cell group, SCG) change or addition; transmitting a message to a base station containing a report of the successful PSCell change or addition; performing a deregistration procedure from the network; and discarding the first information regarding the successful PSCell change or addition during the deregistration procedure.

Description

Technology Field

[0001] The present disclosure relates to wireless communication networks. More specifically, the present disclosure relates to methods and systems for managing successful primary secondary cell group (SCG) cell (PSCell) addition or change reports (SPR) related to the self-optimization of random access. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz (THX) band (e.g., the 3 terahertz band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] 5G NR networks are known as Next-Generation Radio Networks (NG-RAN) and consist of multiple NR base stations, such as Next-Generation Node Bs (gNBs). gNBs can be interconnected via Xn interfaces and connected to various core network elements, such as the Access and Mobility Management Function (AMF) and User Plane Function (UPF). Additionally, gNBs can be divided into two physical entities: a Central Unit (CU) and a Distributed Unit (DU). The CU supports the upper layers of the protocol stack, such as the Session Data Application Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC). The DU supports the lower layers of the protocol stack, such as Radio Link Control (RLC), Medium Access Control (MAC), and the physical layer. Each gNB can have multiple cells, and these cells can service many user devices (UEs).

[0009] The foregoing information is provided for the sake of background information to aid in understanding the disclosure. No determination has been made, nor is any claim made, regarding which of the foregoing contents may be applied as prior art to the present disclosure. means of solving the problem

[0010] The embodiments of the present disclosure are intended to solve at least the aforementioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, one embodiment of the present disclosure provides methods and systems for managing a successful primary secondary cell group (SCG) cell (PSCell) addition or change report (SPR) in a wireless communication network.

[0011] Another aspect of the present disclosure is the 5th generation (5 th The purpose is to provide methods and systems for the self-optimization of random access (including optimization for minimizing drive tests) in wireless communication networks such as new radio (NR) of the 5G generation.

[0012] Another aspect of the present disclosure is to provide methods and systems for transmitting random access information to a network by a user terminal (user equipment, UE) in an NR.

[0013] Another aspect of the present disclosure provides methods and systems for a Self-Organizing Network (SON) for a dual connection scenario, wherein the configuration of a UE for reporting information related to successful PSCell addition and successful PSCell change, the reporting and releasing of said configuration are disclosed and configured to be stored and reported within an SPR report.

[0014] Another aspect of the present disclosure is to provide methods and systems for handling mnInitiatedPSCellChange or snInitiatedPSCellChange settings.

[0015] Another aspect of the present disclosure is to provide methods and systems for decommissioning an SPR based on deregistration.

[0016] Another aspect of the present disclosure is to provide methods and systems for determining whether to report location information within the SPR.

[0017] Another aspect of the present disclosure is to provide methods and systems for a UE to log location information based on a node that provides ObtainCommonLocation.

[0018] Another aspect of the present disclosure is to provide methods and systems in which a UE disables sn-InitiatedPSCellChange while receiving another OtherConfig that does not include sn-InitiatedPSCellChange.

[0019] Another aspect of the present disclosure provides methods and systems for a UE to log information regarding random access and UE-based timing advance (TA) acquisition for SCG lower layer-triggered mobility (LTM).

[0020] Additional aspects will be described in part in the following description, will be apparent from the description, or can be acquired through the practice of the presented embodiments.

[0021] According to one aspect of the present disclosure, a method performed by a UE in a wireless communication system is provided. The method comprises the steps of: storing first information regarding a successful PSCell change or addition; transmitting a message to a base station containing a report regarding the successful PSCell change or addition; performing an unregistration procedure from a network; and discarding the first information regarding the successful PSCell change or addition during the unregistration procedure.

[0022] According to another aspect of the present disclosure, a UE in a wireless communication system is provided. The UE includes a transceiver and a control unit coupled to the transceiver. The control unit stores first information regarding a successful PSCell change or addition, transmits a message to a base station containing a report regarding the successful PSCell change or addition, performs a deregistration procedure from the network, and is configured to discard the first information regarding the successful PSCell change or addition during the deregistration procedure.

[0023] Other aspects, advantages, and prominent features of the present disclosure will become apparent to those skilled in the art from the following detailed description disclosing various embodiments of the present disclosure when considered together with the accompanying drawings. Brief explanation of the drawing

[0024] The above and other aspects, features, and advantages of specific embodiments of the present disclosure will become more apparent from the following description when considered together with the accompanying drawings. FIG. 1 is an exemplary block diagram illustrating communication between a user terminal (UE) and a network entity for managing a successful primary secondary cell group (SCG) cell (PSCell) addition or change report (SPR) in a wireless communication network according to one embodiment of the present disclosure. FIG. 2 is an exemplary drawing illustrating a method for setting and reporting a master node (MN) initiated primary SCG cell (PSCellChange) according to one embodiment of the present disclosure. FIG. 3 is an exemplary diagram illustrating a method for handling MN initiation PSCellChange settings in a wireless communication network when an RRC Reconfiguration message is received by a UE, according to one embodiment of the present disclosure. FIG. 4 is an exemplary drawing illustrating a secondary node (SN) initiation PSCellChange setting handling method according to one embodiment of the present disclosure. FIG. 5 is an exemplary drawing illustrating a method of handling an SPR during deregistration according to one embodiment of the present disclosure. FIG. 6 is an exemplary drawing illustrating a method for handling ObtainCommonLocation according to one embodiment of the present disclosure. FIG. 7 is an exemplary flowchart for managing SPR in a wireless communication network according to one embodiment of the present disclosure. FIG. 8 illustrates a block diagram illustrating the structure of a UE according to one embodiment of the present disclosure. FIG. 9 illustrates a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure. Identical drawing symbols are used to represent identical elements throughout the drawings. Specific details for implementing the invention

[0025] The following description, with reference to the accompanying drawings, is provided to aid in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. While the following description includes various specific details to aid understanding, they should be considered merely illustrative. Accordingly, a person skilled in the art will recognize that various changes and modifications to the various embodiments described herein may be made without departing from the scope and spirit of the present disclosure. Additionally, descriptions of well-known functions and configurations may be omitted for clarity and brevity.

[0026] The terms and words used in the following description and claims are not limited to their bibliographical meanings but are used merely to enable a clear and consistent understanding of the present disclosure by the inventor. Accordingly, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0027] Unless the context clearly indicates otherwise, the singular forms "a," "an," and "the" should be understood to include multiple referents. Thus, for example, a reference to "component surfaces" includes a reference to one or more of such surfaces.

[0028] For the purpose of interpreting this specification, definitions (as defined herein) shall apply, and where appropriate, terms used in the singular shall also include the plural and vice versa. The terms used herein are for the purpose of describing specific embodiments and should not be understood as being intended to limit. Unless otherwise stated, the terms “comprising,” “having,” and “including” shall be interpreted as open-ended terms.

[0029] The words / phrases “exemplary,” “example,” “illustration,” “in an instance,” “and the like,” “and so on,” “etc.,” “etcetera,” “eg,” and “ie” are used herein merely to mean “serving as an example, case, or illustration.” Any embodiment or implementation of the subject matter described herein using the words / phrases “exemplary,” “example,” “illustration,” “in an instance,” “and the like,” “etc.,” “etcetera,” “eg,” and “ie” is not to be interpreted as being preferred or advantageous over other embodiments.

[0030] The embodiments in this specification may be described and illustrated in terms of the functions described or blocks that perform the functions. These blocks, which may be referred to in this specification as managers, units, modules, hardware components, etc., 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, etc., and may optionally be driven by firmware. For example, the circuits may be implemented on one or more semiconductor chips or on a substrate support such as a printed circuit board. The circuits constituting the blocks may be implemented by dedicated hardware, by a processor (e.g., one or more programmed microprocessors and related circuits), or by a combination of dedicated hardware for performing some functions of the blocks and a processor for performing other functions of the blocks. Each block of the embodiments may be physically separated into two or more interacting individual blocks without departing from the scope of this disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of this disclosure.

[0031] It should be noted that elements within the drawings are illustrative for the purpose of ease of description and understanding and may not necessarily be drawn to scale. For example, flowcharts / sequence diagrams illustrate methods in terms of steps necessary to understand aspects of the embodiments disclosed herein. Additionally, regarding the configuration of a device, one or more components of the device may be represented by conventional symbols in the drawings, and the drawings may show only specific details relevant to understanding the embodiments so as not to obscure the drawings with details that would be readily apparent to a person skilled in the art who benefits from the description in this specification. Additionally, regarding the system, one or more components / modules constituting the system may be represented by conventional symbols in the drawings, and the drawings may show only specific details relevant to understanding the embodiments so as not to obscure the drawings with details that would be readily apparent to a person skilled in the art who benefits from the description in this specification.

[0032] The accompanying drawings are used to aid in the easy understanding of various technical features, and it should be understood that the embodiments presented in this specification are not limited by the accompanying drawings. Accordingly, the present disclosure should be interpreted as extending to any modifications, equivalents, and substitutions in addition to those specifically described in the accompanying drawings and corresponding descriptions. The use of words such as first, second, third, etc., to describe components / elements / steps is for the purposes of this description and should not be interpreted as a sequential order / arrangement / occurrence unless otherwise specified.

[0033] User equipment (UE) registers with the network to use the services provided by the network. The UE may also unregister from the network by sending an unregister request, for example, when the user turns off the device or moves to airplane mode, or under any other conditions determined by the UE implementation. The network may initiate unregistration by sending a Non-Access Layer (NAS) message. In other words, the unregistration procedure allows the UE to notify the network that it no longer wishes to access the 5G system (5GS), the network to notify the UE that it no longer has access to the 5GS, or the network to notify the UE that the UE's registered public land mobile network (PLMN) is not permitted to operate at the UE's location. The unregistration request by the UE and the unregistration request by the network include whether the unregistration applies to Third-Generation Partnership Project (3GPP) access, non-3GPP access, or both. If the UE is registered for both accesses on the same PLMN, the unregistration message may be sent through either access, regardless of which access the unregistration applies to. Network-initiated deregistration may be initiated if the UE's registered PLMN is not allowed to operate at the current UE location.

[0034] In existing mechanisms, there are a large number of algorithms and configuration parameters used in NG-RAN. Identifying the most optimal radio parameters is a very difficult task, and operators traditionally rely on manual techniques such as drive tests to identify them. However, this manual parameter tuning is a costly operation because it depends on various factors, including the number of users, the number of neighboring cells, the maximum throughput within the cell, and the average throughput within the cell. Furthermore, many manual tasks must be repeated whenever an adjacent gNB is installed or a new service is introduced. To address this problem, the Third-Generation Partnership Project (3GPP) introduced self-organizing network (SON) techniques to radio technologies such as NR. SON was first introduced in 3GPP Release 9 of LTE (Long Term Evolution). SON techniques can be divided into three categories: self-configuration, self-optimization, and self-healing. The SON architecture can be a centralized, distributed, or hybrid solution.

[0035] Duplex, or more technically Multiple Radio Duplex (MR-DC), is specified by 3GPP in specifications such as TS 37.340. Duplex details and measurement gap operations associated with duplex are provided.

[0036] NG-RAN supports multi-radio dual connectivity (MR-DC) operation, and accordingly, a User Equipment (UE) in RRC_CONNECTED mode is configured to utilize radio resources provided by two separate schedulers located at two different NG-RAN nodes connected via a non-ideal backhaul. One node provides NR access, while the other node provides E-UTRA (Evolved UMTS Terrestrial Radio Access) or NR access. One node acts as the master node (MN), and the other node acts as the secondary node (SN). The MN and SN are connected via network interfaces, and at least the MN is connected to the core network.

[0037] NG-RAN supports NG-RAN E-UTRA (evolved universal mobile telecommunications system (UMTS) terrestrial radio access)-NR duplexing (NGEN-DC), where the UE is connected to one ng-eNB (an E-UTRA base station capable of connecting to the 5G core) acting as an MN and one gNB (a 5G base station) acting as an SN. NG-RAN supports NR-E-UTRA duplexing (NE-DC), where the UE is connected to one gNB acting as an MN and one ng-eNB acting as an SN. The MN can move a Secondary Cell Group (SCG) between different states, such as deactivated or enabled. When carrier aggregation is supported, secondary cells can also move between the deactivated and enabled states. When a radio link failure occurs in the SCG, the UE transmits the RRC message SCGFailureInformation.

[0038] Primary SCG cell (PSCell) changes may occur due to mobility and may or may not entail secondary node changes (SN changes). The secondary node change procedure may be initiated by either the MN or the SN and is used to transfer the UE context from the source SN to the target SN while updating the SCG settings within the UE.

[0039] A conditional PSCell change (CPC) is defined as a PSCell change executed by a UE when specific execution conditions are met. The UE may receive execution conditions, and if the conditions are met, an RRC message (e.g., RRC Reconfiguration) is executed for one or more candidate cells. When the UE receives a CPC setting, it begins evaluating the execution conditions and stops evaluation once the PSCell change is triggered. Both intra-SN CPCs without MN intervention and inter-SN CPCs initiated by either the MN or the SN are supported.

[0040] The following principles apply to CPC, and CPC configuration includes the configuration of CPC candidate PSCells and execution conditions, and may include MN configuration for CPC between SNs. Execution conditions may consist of one or two trigger conditions (CPC events A3 / A5 defined in TS 38.331). Only a single RS type is supported, and up to two different trigger quantities (e.g., RSRP and RSRQ, RSRP and SINR, etc.) may be configured simultaneously to evaluate the CPC execution conditions of a single candidate PSCell.

[0041] If a PSCell change command or PCell change command is received before any CPC execution condition is satisfied, the UE executes the PSCell change procedure described in provisions 10.3 and 10.5 of TS 38.300 or the PCell change procedure described in provision 9.2.3.2 of TS 36.300 or provision 10.1.2.1 of TS 38.300. When the PSCell change or PCell change procedure is successfully completed, the UE releases all stored CPC settings. During CPC execution, the UE does not need to continue evaluating the execution conditions of other candidate PSCells. Once the CPC procedure is successfully executed, the UE releases all stored CPC settings. When the SCG is released, the UE releases the stored CPC settings.

[0042] 3GPP Release 18 improves CPC through the selective activation of cell groups, wherein the UE does not release stored CPC settings for one or more candidate PSCells and source PSCells based on network inputs. The UE can also store Conditional PSCell Addition (CPA) settings for one or more candidate PSCells.

[0043] The MN adds a PSCell during the PSCell addition procedure. A PSCell addition procedure that runs only when the PSCell addition conditions are met is referred to as conditional PSCell addition (CPA). PSCell changes can be performed using a mobility procedure known as low layer triggered mobility (LTM) in Release 18. When the UE receives a MAC CE message known as LTM CellSwitchCommand, it performs LTM for the SCG and switches to the SCG cell that received the LTM candidate cell configuration.

[0044] Mobility robustness optimization is intended to detect non-optimal successful PSCell changes or non-optimal successful PSCell addition events.

[0045]

[0046]

[0047] The network configures the UE to report SPR using OtherConfig as follows, using RRC messages such as RRCReconfiguration in NR.

[0048]

[0049] Therefore, sn-InitiatedPSCellChange is provided as a Need M parameter, which means that if the UE receives an OtherConfig containing sn-InitiatedPSCellChange, it retains that value. If the UE receives another RRCReconfiguration message that does not contain the parameter sn-InitiatedPSCellChange, it applies the value received within the previous RRCReconfiguration message.

[0050] Therefore, the SPR content may include descriptions of the SuccessPSCell-Report fields. The measResultListNR field represents the most recent measurement results acquired from adjacent NR cells, depending on the initiating node settings, when a successful PSCell change or addition is executed.

[0051] The pCellId field is used to indicate the PCell to which the UE was connected when a successful PSCell change or addition triggered the SuccessPSCell-Report. The sn-InitiatedPSCellChange field indicates whether the PSCell change procedure for which the successful PSCell change report was logged was initiated by the SN. The spr-Cause field is used to indicate the cause of the successful PSCell change or addition report.

[0052] The sourcePSCellId field is used to indicate the source PSCell of the PSCell change that triggered the SuccessPSCell-Report. The sourcePSCellMeas field indicates the most recent measurement results obtained from the source PSCell of the PSCell change that triggered the SuccessPSCell-Report.

[0053] The targetPSCellId field is used to indicate the target PSCell of the successful PSCell change or addition that triggered the SuccessPSCell-Report.

[0054] The targetPSCellMeas field represents the most recent measurement results obtained from the PSCell change or additional target PSCell that triggered the successful PSCell change or additional SuccessPSCell-Report.

[0055] The timeSinceCPAC-Reconfig field indicates the time elapsed between the start of the last conditional reset execution toward the target PSCell and the reception of the latest conditional reset for the target PSCell. The actual value is calculated as the field value * 100ms. The maximum value of 1023 means 102.3 seconds or more.

[0056] The actions performed for a successful PSCell change or additional reporting decision are described in 5.7.10.7 of TS 38.331.

[0057] 3gpp V17.6.0 versions of TS 38.331, TS 38.321, TS 38.300, and TS 38.304, 3gpp CR R2-2313855 introducing SON / MDT features in Release 18, and 3gpp CR R2-2313672 introducing additional mobility enhancements in Release 18 may be considered as relevant background in this specification.

[0058] Therefore, in this technical field, solutions to overcome the aforementioned disadvantages are needed above all else.

[0059] The embodiments in this specification disclose methods and systems for managing successful primary SCG cell (PSCell) addition or change reports (SPR) in a wireless communication network. Further embodiments in this specification relate to providing self-optimization, such as optimization for minimizing drive tests of random access in a wireless communication network.

[0060] It should be understood that the blocks in each flowchart and combinations of flowcharts may be executed by one or more computer programs containing instructions. One or more computer programs as a whole may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored in multiple different memory devices.

[0061] Any of the functions or operations described in this specification may be processed by a single processor or a combination of processors. A single processor or a combination of processors is a circuit that performs processing and includes circuits such as an application processor (AP) (e.g., a central processing unit (CPU)), a communication processor (CP) (e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, etc.

[0062] Now, referring to the drawings, more specifically FIGS. 1 through 9, in which similar reference numerals consistently correspond to features throughout the drawings, at least one embodiment is illustrated.

[0063] FIG. 1 is an exemplary block diagram illustrating communication between a user terminal (UE) (102) and a network entity (110) for managing a successful primary SCG cell (PSCell) addition or change report in a wireless communication network (100) according to one embodiment of the present disclosure.

[0064] Referring to FIG. 1, a wireless communication network (100) includes a UE (102) and a network entity (110). The UE (102) includes a processor (104), a memory (106), and an SPR management control unit (108). The UE (102) communicates with the network entity (110).

[0065] The UE (102) referred to in this specification may be an electronic device / user device used by a user to connect to a plurality of other devices using a 3GPP network, interact with them, and / or control their operations. Examples of the UE (102) may include, but are not limited to, a smartphone, a mobile phone, a video phone, a computer, a tablet personal computer (PC), a laptop, a wearable device, a PDA (personal digital assistant), an IoT device, or any other device capable of using a 3GPP network or a non-3GPP network.

[0066] The processor (104) may include one or more processors. The one or more processors may be general-purpose processors such as a central processing unit (CPU) or an application processor (AP), graphics-only processing units such as a graphics processing unit (GPU) or a visual processing unit (VPU), and / or artificial intelligence (AI)-only processors such as a neural network processing unit (NPU).

[0067] The memory (106) mentioned in the present specification includes at least one type of storage medium among a flash memory type storage medium, a hard disk type storage medium, a multimedia card micro type storage medium, a card type memory (e.g., SD or XD memory), RAM (random-access memory), SRAM (static RAM), ROM (read-only memory), EEPROM (electrically erasable programmable ROM), PROM (programmable ROM), magnetic memory, a magnetic disk, or an optical disk.

[0068] A network entity (110) may represent a network element that communicates with a user terminal (UE) (102). The network entity (110) transmits configuration messages (such as an RRCReconfiguration message) containing instructions for handling PSCell changes, additions, and SPR management. The network entity (110) may trigger logging of the SPR and provide parameters such as ObtainCommonLocation.

[0069] In one embodiment, the UE (102) receives a configuration message containing a configuration for reporting at least one of successful PSCell change information and successful PSCell addition information to the network entity (110). The UE (102) logs at least one SPR when performing at least one of successful PSCell change and successful PSCell addition. The UE (102) determines that at least one unregister request is initiated or received from the network entity (110). The UE (102) discards at least one logged SPR based on at least one unregister request, wherein the SPR includes information associated with at least one of successful PSCell change and successful PSCell addition.

[0070] The configuration message includes a configuration to make detailed location information available using the global navigation satellite system (GNSS). A configuration for logging GNSS information is typically provided within a measurement configuration, such as a report configuration. For example, includeCommonLocationInfo within reportConfig notifies the UE to report location information within the measurement report. Additionally, the UE may receive instructions to obtain a common location for measurements, such as obtainCommonLocation. At least one unregister request is initiated by the UE (102) or triggered by the network entity (110). The UE (102) logs the available detailed location information in the SPR when obtainCommonLocation is received for the associated cell group. The UE (102) includes information in the successful PSCell change or addition report (SPR), including whether the UE (102) derived the timing advance using the UE-based timing advance during the execution of a successful PSCell change or successful PSCell addition.

[0071] The UE (102) receives an RRCReconfiguration message containing an OtherConfig field. The UE (102) can determine whether the OtherConfig field contains a secondary node (SN)-InitiatedPSCellChange parameter. The UE (102) releases SN-InitiatedPSCellChange in response to determining that the OtherConfig field does not contain the SN-InitiatedPSCellChange parameter. The SN-InitiatedPSCellChange parameter is set as a Need R parameter.

[0072] In another embodiment disclosed herein, the SPR management control unit (108) is configured to receive a configuration message containing a configuration for reporting at least one of successful PSCell change information and successful PSCell addition information to the network entity (110). The SPR management control unit (108) may log at least one SPR when performing at least one of successful PSCell change and successful PSCell addition. The SPR management control unit (108) determines that at least one unregister request is initiated or received from the network entity (110). The SPR management control unit (108) may discard at least one logged SPR based on at least one unregister request, wherein the SPR contains information associated with at least one of successful PSCell change and successful PSCell addition. Discarding the SPR based on unregistering is beneficial to both the network and the UE, as it allows the UE to retain only the relevant information for optimizing dual connectivity. This also allows the UE to store the SPR in volatile memory, thereby reducing the overall cost to the UEs. From a network perspective, this reduces signaling and processing overhead by preventing the reception of outdated reports. For example, the network may consider a UE to have remained in the network for too long, such as when a UE's subscription period is 3 months and has expired. Consequently, the network may initiate an unsubscription procedure, and any SPR from this UE may be considered outdated. It is unnecessary overhead for the network to retain outdated SPRs containing old information until it retrieves them, or until the UE is disconnected (by powering off or after switching between RATs).

[0073] In one embodiment, the UE (102) notifies the network entity (110) within SCGFailureInformation whether the PSCell change or addition is RACHless. In one embodiment, the UE (102) includes information within SPR or SCGFailureInformation regarding whether the UE (102) derived a timing advance using a UE (102)-based timing advance during a successful PSCell change or addition execution. In one embodiment of this specification, this may be notified for LTM.

[0074] The UE (102) transmits to the network additional details regarding PSCell changes or PSCell additions, which may include, but are not limited to, RACHless (Random Access Channel free) execution status, timing advance information, and relevance to lower-level trigger mobility (LTM) in certain scenarios. RACHless refers to RACH-free operation, which means that the UE (102) performs PSCell changes or additions without using RACH procedures.

[0075] Therefore, the UE (102) notifying the network entity (110) whether the PSCell change or addition was RACHless helps the network distinguish faster RACHless executions. The UE (102) reports UE-based timing advances if they are derived locally during the PSCell change or addition execution. Details are included in reports such as SCGFailureInformation and SPR. In the case of lower-layer triggered mobility (LTM), the reports provide additional context to the network entity (110) to assist in the optimization of mobility management at lower protocol layers.

[0076] FIG. 2 is an exemplary drawing illustrating a method for setting and reporting a master node (MN) initiating primary SCG cell (PSCellChange) according to one embodiment of the present disclosure.

[0077] Referring to FIG. 2, in operation (202), a user terminal (UE) (102) receives an RRC Reconfiguration message containing the master node (MN)-InitiatedPSCellChange parameter. The UE (102) receives an RRC Reconfiguration message containing the MN-InitiatedPSCellChange parameter, which indicates that a PSCell change or addition was initiated by the MN. Once the UE (102) processes the RRC Reconfiguration message, an SPR trigger condition is satisfied. In operation (204), the SPR trigger condition is predefined and involves specific network or UE (102) events, such as a successful PSCell change or addition. Accordingly, in operation (206), the UE (102) logs a successful PSCell change or addition report (SPR), and the logged SPR contains information associated with the MN-InitiatedPSCellChange setting as defined in the network.

[0078] Therefore, including the MN-InitiatedPSCellChange parameter in the SPR log ensures accurate recording of network-driven PSCell operations. The release and logging process improves SPR management and optimizes UE memory usage by reducing unnecessary retention of settings.

[0079] In one embodiment disclosed herein, a network node (such as a gNB) notifies the UE (102) whether the Reconfiguration message triggering ReconfigurationWithSync for a PSCell change was initiated by the MN using an enumerated value (i.e., a flag). In the NR, the gNB may include a field (e.g., MN-InitiatedPSCellChange) in OtherConfig, and if the field MN-InitiatedPSCellChange is included (i.e., if the field is set to true), the UE (102) identifies that the PSCell change was initiated by the MN. On the other hand, if the field is not included, the UE (102) identifies the PSCell change as initiated by the secondary node (SN).

[0080] In one embodiment, when UE (102) receives MN-InitiatedPSCellChange from a network entity (110) within an RRC Reconfiguration message that triggers a PSCell change, UE (102) notifies the network that the PSCell change was initiated by the MN. UE (102) includes the enumerated value MN-InitiatedPSCellChange in the SPR and sets the value of MN-InitiatedPSCellChange to true to notify the network that the PSCell change was initiated by the MN. In one embodiment, when UE (102) does not receive MN-InitiatedPSCellChange from the network within an RRC Reconfiguration message that triggers a PSCell change, UE (102) does not include MN-InitiatedPSCellChange in the SPR.

[0081] UE (102) includes an MN-InitiatedPSCellChange field based on whether MN-InitiatedPSCellChange has been received.

[0082] In one embodiment, MN-InitiatedPSCellChange is provided as a Need R parameter, which means that a UE (102) that receives OtherConfig containing MN-InitiatedPSCellChange does not retain the value, and when the UE (102) receives another RRCReconfiguration message that does not contain MN-InitiatedPSCellChange, the UE (102) releases MN-InitiatedPSCellChange.

[0083] FIG. 3 is an exemplary drawing illustrating a method for handling MN initiation PSCellChange settings in a wireless communication network when an RRC Reconfiguration message is received by a UE (102), according to one embodiment of the present disclosure.

[0084] Referring to FIG. 3, in operation (302), the UE (102) receives an RRC Reconfiguration message containing the MN-InitiatedPSCellChange parameter. The setting indicates that a PSCell change or addition process is initiated by the master node (MN). The UE (102) activates the MN-InitiatedPSCellChange setting and saves it as part of its operation state. In operation (304), the UE (102) receives another RRC Reconfiguration message that does not contain the MN-InitiatedPSCellChange parameter.

[0085] The absence of a parameter indicates that the network has no intention of causing the UE (102) to maintain the setting. In operation (306), in response to the absence of the MN-InitiatedPSCellChange parameter, the UE (102) releases the stored MN-InitiatedPSCellChange setting. This ensures that the UE (102) updates its setting to comply with the network's instructions.

[0086] Therefore, the UE (102) maintains only the settings necessary for network operations, thereby preventing redundant or outdated states. By disabling the MN-InitiatedPSCellChange setting when it is no longer needed, the UE (102) optimizes memory and processing resources.

[0087] In another embodiment, the UE (102) is initially instructed to monitor and log PSCell changes via MN-InitiatedPSCellChange as part of its operational setup. The network entity (110) decides to disable it (e.g., due to dynamic network conditions or completed PSCell operations). The network entity (110) omits the MN-InitiatedPSCellChange parameter in the next RRC Reconfiguration message. The UE (102) immediately releases the stored MN-InitiatedPSCellChange setup to ensure that its operational status is up-to-date.

[0088] FIG. 4 is an exemplary drawing illustrating a secondary node (SN) initiation PSCellChange setting handling method according to one embodiment of the present disclosure.

[0089] Referring to FIG. 4, the UE (102) manages the presence or absence of the SN-InitiatedPSCellChange parameter in successive RRC Reconfiguration messages and manages subsequent actions taken by the UE (102) to update or disable the settings. In action (402), the UE (102) receives an RRC Reconfiguration message containing the SN-InitiatedPSCellChange parameter.

[0090] The parameter indicates that the PSCell change or addition process is initiated by the secondary node (SN). Upon receiving the message, the UE (102) activates and saves the SN-InitiatedPSCellChange setting. In operation (404), the UE (102) receives another RRC Reconfiguration message, but this message does not contain the SN-InitiatedPSCellChange parameter. The absence of the parameter indicates that the network entity (110) no longer intends for the UE (102) to maintain the SN-InitiatedPSCellChange setting. In operation (406), in response to the absence of the SN-InitiatedPSCellChange parameter, the UE (102) releases the saved SN-InitiatedPSCellChange setting. This ensures that the UE does not log SPRs based on any previous PSCellChange or PSCellAddition. This also simplifies the network implementation for configuring SN-InitiatedPSCellChange because the network does not need to send an RRCReconfiguration message to disable SN-InitiatedPSCellChange. This also reduces signaling on the air interface and between network nodes.

[0091] In one embodiment, sn-InitiatedPSCellChange may be provided as a Need R parameter, which means that the UE (102) that receives OtherConfig containing sn-InitiatedPSCellChange does not retain the value. If the UE (102) receives another RRCReconfiguration message that does not contain sn-InitiatedPSCellChange, the UE (102) releases sn-InitiatedPSCellChange and performs the determination of SPR logging and the determination of the SPR content as if there were no received InitiatedPSCellChange.

[0092] FIG. 5 is an exemplary drawing illustrating a method for handling a successful primary SCG cell (PSCcell) addition or change report (SPR) during deregistration according to one embodiment of the present disclosure.

[0093] In operation (502), a specific event or condition occurs to satisfy the SPR trigger for the UE (102) (e.g., the UE is configured to log the SPR when the network exceeds the T310 or T312 or T304 timer value and the threshold set by the network is exceeded). Trigger conditions may include, but are not limited to, successful PSCell changes (e.g., a new cell is added to a serving group or replaced with a primary SCG cell) and successful PSCell addition.

[0094] When conditions are met, the UE (102) logs and saves the SPR. Depending on the network configuration, the SPR contains details regarding PSCell operations, such as location information, signal measurements, and timing advances. The logged SPR is stored in the UE's memory as part of the variable VarSuccessPSCell-Report.

[0095] Additionally, the UE (102) initiates or receives an unregister request from the network. In operation (504), unregistering may occur for several reasons, such as the UE (102) notifying the network entity (110) that it no longer wishes to access the service, or the network entity (110) notifying the UE (102) that the UE (102) can no longer access the service (e.g., due to location restrictions or service termination).

[0096] Accordingly, in operation (504), upon unregistration, the UE (102) discards all stored SPRs, which includes releasing the VarSuccessPSCell-Report variable and removing logged details regarding successful PSCell changes or additions from memory. Thus, it ensures that outdated information is not retained after the UE (102) is disconnected from the network.

[0097] In one embodiment, in operation (506), the UE (102) discards any logged SPR when unregistering from the network. When the UE (102) sends an unregister request or when a network-triggered unregister is received, the UE (102) discards the SPR. FIG. 5 illustrates a method for handling SPRs during unregistering.

[0098] In one embodiment disclosed in this specification, MN-InitiatedPSCellChange is provided as a Need R parameter, which means that a UE (102) that receives OtherConfig containing mn-InitiatedPSCellChange does not retain the value, and when the UE (102) receives another RRCReconfiguration message that does not contain mn-InitiatedPSCellChange, the UE (102) releases mn-InitiatedPSCellChange.

[0099] FIG. 6 is an exemplary drawing illustrating a method for handling ObtainCommonLocation according to one embodiment of the present disclosure.

[0100] Referring to FIG. 6, in operation (602), the UE (102) receives the ObtainCommonLocation parameter from either a master cell group (MCG) or a secondary cell group (SCG). In operation (604), the SPR is triggered. The ObtainCommonLocation parameter instructs the UE (102) to include detailed location information (e.g., GNSS-based location) in the SPR. In operation (606), the UE (102) evaluates whether the cell group (MCG or SCG) that set the ObtainCommonLocation parameter is the same as the cell group that set the SPR. The UE (102) identifies whether the cell group that set the SPR also set the ObtainCommonLocation. In operation (608), the UE (102) logs the available detailed location information to the SPR, and if not, in operation (610), the UE (102) does not log the detailed information to the SPR even if it is available. Therefore, it ensures compliance with network instructions and contains useful data for network optimization. If ObtainCommonLocation is not received from a specific node (MN or SN), this means that the node is not interested in receiving location information, even if the measurement settings, such as the reporting settings maintained by that node, have settings for performing location measurements. Settings for performing location measurements may be maintained to prevent additional downlink signaling for resetting, but ObtainCommonLocation controls logging location information to the SPR. Additional control reduces the UE memory and the overall signaling of the SPR. If it is identified that the cell group that set ObtainCommonLocation is different from the cell group that set the SPR, the UE (102) does not log detailed location information to the SPR even if it is available. Thus, unnecessary or redundant logging is prevented.

[0101] For example, consider the case where the UE (102) receives the ObtainCommonLocation parameter from the MCG. The SPR is also set by the MCG. The UE (102) logs detailed location information (e.g., GNSS-based data) to the SPR. The UE (102) receives the ObtainCommonLocation parameter from the SCG. The SPR is set by the MCG. The UE (102) does not log detailed location information to the SPR even if data is available. Thus, by conditionally logging location information, the UE (102) prevents unnecessary data collection and storage, thereby optimizing memory and processing resources.

[0102] FIG. 7 is an exemplary flowchart for managing a successful primary SCG cell (PSCcell) addition or change report (SPR) in a wireless communication network (100) according to one embodiment of the present disclosure.

[0103] As illustrated in operation (702), the SPR management control unit (108), combined with the processor (104) and memory (106), is configured to receive a configuration message containing a configuration for reporting at least one of successful PSCell change information and successful PSCell addition information to the network entity (110). In operation (704), the SPR management control unit (108) logs at least one SPR when performing at least one of successful PSCell change and successful PSCell addition. In operation (706), the SPR management control unit (108) determines that at least one unregister request must be initiated (i.e., by the UE) or received from the network entity (110). In operation (708), the SPR management control unit (108) discards at least one logged SPR based on at least one unregister request, wherein the SPR contains information associated with at least one of successful PSCell change and successful PSCell addition.

[0104] In one embodiment, according to TS 38.331,

[0105]

[0106]

[0107] SuccessPSCell-Report Field Descriptions:

[0108] The measResultListNR field represents the last measurement results acquired from adjacent NR cells according to the initiation node settings when a successful PSCell change / addition is executed.

[0109] The pCellId field is used to indicate the PCell to which the UE (102) was connected when a successful PSCell change or addition triggers the SuccessPSCell-Report.

[0110] The mn-InitiatedPSCellChange field indicates whether a PSCell change procedure for which a successful PSCell change report was logged was initiated by MN.

[0111] The spr-Cause field is used to indicate the cause of a successful PSCell change or additional report.

[0112] The sourcePSCellId field is used to indicate the source PSCell of the PSCell change that triggers the SuccessPSCell-Report when the PSCell change is successful.

[0113] The sourcePSCellMeas field represents the last measurement results obtained from the source PSCell of the PSCell change that triggers the SuccessPSCell-Report for the successful PSCell change.

[0114] The targetPSCellId field is used to indicate the target PSCell of the PSCell change / addition for which a successful PSCell change or addition triggers the SuccessPSCell-Report.

[0115] The targetPSCellMeas field represents the last measurement results obtained from the target PSCell of the successful PSCell change or addition that triggers the SuccessPSCell-Report.

[0116] The timeSinceCPAC-Reconfig field is used to indicate the time elapsed between the start of the last conditional reset execution toward the target PSCell and the reception of the latest conditional reset for this target PSCell. Actual value = Field value * 100ms. The maximum value of 1023 means 102.3 seconds or more.

[0117] OtherConfig may represent the mn-InitiatedPSCellChange field, which indicates whether the PSCell change procedure included in the RRCReconfiguration message was initiated by MN.

[0118] 5.7.10.7 Actions for Successful PSCell Change or Additional Reporting Decisions

[0119] Regarding PSCell, UE is:

[0120] 1> If the ratio between the elapsed time value of Timer T304 included in the last applied RRCReconfiguration message for the SCG containing reconfigurationWithSync and the set value of Timer T304 is greater than the thresholdPercentageT304-SCG included in the successPSCell-Config received before executing the last reconfiguration with sync for the SCG; or

[0121] 1> If mn-InitiatedPSCellChange is not set in the RRCReconfiguration containing the last applied RRCReconfiguration containing reconfigurationWithSync for SCG, and the ratio between the value of the elapsed time of timer T310 and the value of the set timer T310, which was set while the UE (102) was connected to the source PSCell before executing the last synchronization-through reset for SCG, is greater than the thresholdPercentageT310-SCG included in the successPSCell-Config that was set by the source PSCell before executing the last synchronization-through reset; or

[0122] 1> If mn-InitiatedPSCellChange is not set in the RRCReconfiguration containing the last applied RRCReconfiguration containing reconfigurationWithSync for SCG, and T312 associated with the measurement identity of the target PSCell was active at the time the execution of the reset procedure through synchronization for SCG is initiated, and the ratio between the value of the elapsed time of timer T312 and the value of timer T312, which was set while the UE (102) was connected to the source PSCell before the last reset through synchronization, is greater than the thresholdPercentageT312-SCG included in the successPSCell-Config, which was set by the source PSCell before the last reset through synchronization:

[0123] 1> If mn-InitiatedPSCellChange is set in the RRCReconfiguration containing the last applied RRCReconfiguration containing reconfigurationWithSync for SCG, and the ratio between the value of the elapsed time of timer T310 and the value of the set timer T310, which was set while the UE (102) was connected to the source PSCell before executing the last synchronization-through-reconfiguration for SCG, is greater than the thresholdPercentageT310-SCG included in the successPSCell-Config that was set by the PCell before executing the last synchronization-through-reconfiguration; or

[0124] 1> If mn-InitiatedPSCellChange is set in the RRCReconfiguration containing the last applied RRCReconfiguration containing reconfigurationWithSync for SCG, and T312 associated with the measurement identity of the target PSCell was active at the time the execution of the reset procedure through synchronization for SCG is initiated, and the ratio between the value of the elapsed time of timer T312 and the value of timer T312, which was set while the UE (102) was connected to the source PSCell before the last reset through synchronization, is greater than thresholdPercentageT312-SCG included in successPSCell-Config, which was set by the PCell before the last reset through synchronization was executed:

[0125] 2> If there is information contained in VarSuccessPSCell-Report, delete (clear) it;

[0126] 2> Save successful PSCell changes or additions to VarSuccessPSCell-Report and determine the contents within VarSuccessPSCell-Report as follows:

[0127] 3> If the UE (102) is not in SNPN access mode, set plmn-IdentityList to contain a list of EPLMNs stored by the UE (i.e., including RPLMN);

[0128] 3> Otherwise, if the UE is in SNPN access mode, if available, set snpn-IdentityList to include a list of equivalent SNPNs stored by the UE (i.e., including registered SNPNs);

[0129] 3> If available, set pCellId to the PCell's global cell identity and trace area code;

[0130] 3> For the source PSCell (if available) to which the last RRCReconfiguration message for the SCG containing reconfigurationWithSync was applied:

[0131] 4> Set sourcePSCellId in sourcePSCellInfo to the source PSCell's global cell identity and trace area code;

[0132] 4> Set sourcePSCellMeas in sourcePSCellInfo to include the cell-level RSRP, RSRQ, and available SINR of the source PSCell based on the available SSB and CSI-RS measurements collected up to the point when the UE successfully completed the random access procedure to the SCG;

[0133] 4> Set rsIndexResults in sourceCellMeas to include all available SSB and CSI-RS measurements of the source PSCell collected up to the point when the UE successfully completes the random access procedure for the SCG;

[0134] 3> For the target PSCell indicated in the last applied RRCReconfiguration message for the SCG containing reconfigurationWithSync:

[0135] 4> Set the targetPSCellID in targetPSCellInfo to the target PSCell's global cell identity and trace region code if available, and to the target PSCell's physical cell identity and carrier frequency otherwise;

[0136] 4> Set targetPSCellMeas within targetPSCellInfo to include the cell-level RSRP, RSRQ, and available SINR of the target PSCell based on available SSB and CSI-RS measurements collected up to the point when the UE successfully completes the random access procedure to the SCG;

[0137] 4> Set rsIndexResults within targetCellMeas to include all available SSB and CSI-RS measurements of the target PSCell collected up to the point when the UE successfully completes the random access procedure to the SCG;

[0138] 4> If the last applied RRCReconfiguration message for an SCG containing reconfigurationWithSync is included in the stored condRRCReconfig:

[0139] 5> timeSinceCPAC-Reconfig is set to the time elapsed between the start of execution of a conditional reset for the target PSCell and the reception of the last conditionalReconfiguration for the SCG, including the condRRCReconfig of the target PSCell;

[0140] 3> If the ratio between the elapsed time value of Timer T304 included in the last applied RRCReconfiguration message for the SCG containing reconfigurationWithSync and the set value of Timer T304 is greater than the thresholdPercentageT304-SCG included in the successPSCell-Config received before executing the last reconfiguration with sync for the SCG;

[0141] 4> Set t304-cause within spr-Cause to true;

[0142] 4> Configure ra-InformationCommon to include random access-related information associated with random access procedures in the target PSCell as specified in Clause 5.7.10.5;

[0143] 3> If the ratio between the elapsed time value of Timer T310, which was set while the UE was connected to the source PSCell before executing the reset via the last synchronization for the SCG, and the set value of Timer T310 is greater than the thresholdPercentageT310-SCG included in successPSCell-Config, which was set before executing the reset via the last synchronization;

[0144] 4> Set t310-cause within spr-Cause to true;

[0145] 3> If T312 associated with the measurement identity of the target PSCell was active at the time the execution of the reset procedure via synchronization with the SCG was initiated, and the ratio between the elapsed time value of Timer T312 and the set value of Timer T312, which was set while the UE was connected to the source PSCell before executing the last reset via synchronization, is greater than the thresholdPercentageT312-SCG included in successPSCell-Config when it was set before executing the last reset via synchronization:

[0146] 4> Set t312-cause within spr-Cause to true;

[0147] 3> If mn-InitiatedPSCellChange is not set on the RRCReconfiguration containing the last applied RRCReconfiguration that includes reconfigurationWithSync for SCG:

[0148] 4> Consider all measObjectNRs set by source PSCell;

[0149] 3> If not:

[0150] 4> Consider all measObjectNRs set by PCell;

[0151] 3> For each measObjectNR:

[0152] 4> When measurements for measObjectNR are available:

[0153] 5> Where SS / PBCH block-based measurements are available:

[0154] 6> Based on the available SS / PBCH block-based measurements collected up to the point when the UE successfully completes the random access procedure, all available measurements of the best measured cells other than the source PCell or target PCell are included in measResultListNR within measResultNeighCells by sorting such that if SS / PBCH block RSRP measurement results are available, the cell with the highest SS / PBCH block RSRP is listed first; otherwise, if SS / PBCH block RSRQ measurement results are available, the cell with the highest SS / PBCH block RSRQ is listed first; and otherwise, the cell with the highest SS / PBCH block SINR is listed first;

[0155] 6> For each included adjacent cell, include available optional fields (including CSI-RS based measurements, where available);

[0156] 5> If CSI-RS measurements are available for cells within measResultNeighCells that are not yet included in measResultListNR:

[0157] 6> Based on the available CSI-RS-based measurements collected up to the point when the UE successfully completes the random access procedure, the cells are sorted such that if CSI-RS RSRP measurement results are available, the cells with the highest CSI-RS RSRP are listed first; otherwise, if CSI-RS RSRQ measurement results are available, the cells with the highest CSI-RS RSRQ are listed first; and otherwise, the cells with the highest CSI-RS SINR are listed first, and all available measurements of the best measured cells, excluding the source PCell and target PCell, are included in measResultListNR within measResultNeighCells;

[0158] 6> For each included adjacent cell, include available optional fields;

[0159] 3> For each adjacent cell included in measResultNeighCells:

[0160] 4> If the cell is a candidate target cell included in condRRCReconfig within conditionalReconfiguration, to which the last RRCReconfiguration message for the SCG containing reconfigurationWithSync has been applied:

[0161] 5> Set choCandidate to true in measResultNR;

[0162] 3> If the RRCReconfiguration containing the applied RRCReconfiguration message including reconfigurationWithSync for SCG contains mn-InitiatedPSCellChange, include mn-InitiatedPSCellChange;

[0163] 3> If mn-InitiatedPSCellChange is not set on the RRCReconfiguration containing the last applied RRCReconfiguration that includes reconfigurationWithSync for SCG:

[0164] 4> If available, set locationInfo according to otherConfig associated with the source PSCell as in 5.3.3.7 7;

[0165] 3> If not:

[0166] 4> If available, set locationInfo according to otherConfig associated with PCell as in 5.3.3.7 7;

[0167] 1> If available, disable successPSCell-Config set by the source PSCell and thresholdPercentageT304 set by the target PSCell.

[0168] 48 hours have elapsed since the last successful PSCell change or addition information was added to VarSuccessPSCell-Report, or when unregistered from the network entity (110), the UE (102) can discard the successful PSCell change or addition information, that is, the UE (102) can release the variable VarSuccessPSCell-Report.

[0169] In one embodiment, the UE (102) receiving the obtainCommonLocation field (a field that notifies the UE (102) to attempt to make detailed location information available using GNSS) checks whether the obtainCommonLocation was received for the MCG or SCG (as illustrated in FIG. 6). In one embodiment, the UE (102) includes detailed location information available for any successful PSCell change or additional report associated with the cell group that set the ObtainCommonLocation (or the setting is associated with that cell group). For example, if the ObtainCommonLocation is set by the MCG and the SPR is associated with the SCG, the UE (102) may not log location information even if it is available. Similarly, if the ObtainCommonLocation is set by the SCG and the SPR is associated with the MCG, the UE (102) may not log location information even if it is available. However, if ObtainCommonLocation is set by MCG and SPR is associated with MCG, UE (102) logs location information if available. Similarly, if ObtainCommonLocation is set by SCG and SPR is associated with SCG, UE (102) logs location information if available.

[0170] In one embodiment, if obtainCommonLocation is received within an RRCReconfiguration message received via SRB3, ObtainCommonLocation is set by SCG. In one embodiment, if obtainCommonLocation is embedded within an MN RRCReconfiguration message and included in a received SCG RRCReconfiguration message, ObtainCommonLocation is set by SCG. In one embodiment, if obtainCommonLocation is included in an MCG RRCReconfiguration message, ObtainCommonLocation is set by MCG.

[0171] In one embodiment, if obtainCommonLocation is included in an MCG RRCReconfiguration message that carries an SCG RRCReconfiguration message such as an SCG RRCReconfiguration message containing ReconfigurationWithSync and includes mn-InitiatedPSCellChange, ObtainCommonLocation is set by the MCG. In one embodiment, if obtainCommonLocation is included in an MCG RRCReconfiguration message that carries an SCG RRCReconfiguration message such as an SCG RRCReconfiguration message containing ReconfigurationWithSync and does not include mn-InitiatedPSCellChange, ObtainCommonLocation is set by the SCG.

[0172] In one embodiment, if obtainCommonLocation is included in an MCG RRCReconfiguration message that carries an SCG RRCReconfiguration message such as an SCG RRCReconfiguration message containing ReconfigurationWithSync and includes sn-InitiatedPSCellChange, ObtainCommonLocation is set by the SCG. In one embodiment, if obtainCommonLocation is included in an MCG RRCReconfiguration message that carries an SCG RRCReconfiguration message such as an SCG RRCReconfiguration message containing ReconfigurationWithSync and does not include mn-InitiatedPSCellChange, ObtainCommonLocation is set by the MCG.

[0173] In one embodiment, the UE (102) includes information in the SPR regarding whether a successful PSCell change or addition is RACHless (i.e., whether random access was performed to (complete) a successful PSCell change or addition). In one embodiment of the specification, this may be performed for mobility or LTM in a Non-Terrestrial Network (NTN).

[0174] In one embodiment, the UE (102) notifies the network entity (110) within SCGFailureInformation whether the PSCell change or addition is RACHless.

[0175] In one embodiment, the UE (102) includes information in the SPR or SCGFailureInformation regarding whether the UE (102) derived a timing advance using a UE (102)-based timing advance during a successful PSCell change or additional execution. In one embodiment of the specification, this may be notified for the LTM.

[0176] In one embodiment, the UE (102) includes information in the SPR or SCGFailureInformation regarding whether the UE (102) used SRB1 to send a completion message (such as NR RRCReconfigurationComplete) during a successful PSCell change or additional execution. In one embodiment of the specification, this may be notified for the LTM.

[0177] In one embodiment of the specification, the UE (102) includes information in the SPR or SCGFailureInformation regarding whether the UE (102) sent a completion message (such as NR RRCReconfigurationComplete) using SRB3 during a successful PSCell change or additional execution. In one embodiment, this may be notified to the LTM.

[0178] FIG. 8 illustrates a block diagram illustrating the structure of a UE according to one embodiment of the present disclosure.

[0179] Referring to FIG. 8, a UE according to one embodiment may include a transceiver (810), memory (820), and a processor (830). The transceiver (810), memory (820), and processor (830) of the UE may operate according to the communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. Additionally, the processor (830), transceiver (810), and memory (820) may be implemented as a single chip. Furthermore, the processor (830) may include at least one processor.

[0180] The transceiver (810) collectively refers to a UE receiver and a UE transmitter and can transmit or receive signals to / from a base station. The signals transmitted or received to / from a base station may include control information and data. The transceiver (810) may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying and down-converting the frequency of a received signal. However, this is merely an example of the transceiver (810), and the components of the transceiver (810) are not limited to an RF transmitter and an RF receiver.

[0181] Additionally, the transceiver (810) can receive a signal through a wireless channel and output it to a processor (830), and transmit the signal output from the processor (830) through a wireless channel.

[0182] The memory (820) can store programs and data required for the operations of the UE. Additionally, the memory (820) can store control information or data included in signals acquired by the UE. The memory (820) may be a storage medium such as ROM (read-only memory), RAM (random access memory), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0183] The processor (830) can control a series of processes to enable the UE to operate as described above. For example, the transceiver (810) can receive a data signal including a control signal transmitted by the base station, and the processor (830) can determine the result of receiving the control signal and the data signal transmitted by the base station.

[0184] FIG. 9 illustrates a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0185] Referring to FIG. 9, a base station according to one embodiment may include a transceiver (910), a memory (920), and a processor (930). The transceiver (910), memory (920), and processor (930) of the base station may operate according to the communication method of the base station described above. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than those described above. Additionally, the processor (930), transceiver (910), and memory (920) may be implemented as a single chip. Furthermore, the processor (930) may include at least one processor.

[0186] The transceiver (910) collectively refers to a base station receiver and a base station transmitter, and can transmit or receive signals from a terminal. The signals transmitted or received from the terminal may include control information and data. The transceiver (910) may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying and down-converting the frequency of a received signal. However, this is merely an example of the transceiver (910), and the components of the transceiver (910) are not limited to an RF transmitter and an RF receiver.

[0187] Additionally, the transceiver (910) can receive a signal through a wireless channel and output it to a processor (930), and transmit the signal output from the processor (930) through a wireless channel.

[0188] The memory (920) can store programs and data necessary for the operations of the base station. Additionally, the memory (920) can store control information or data included in signals acquired by the base station. The memory (920) may be a storage medium such as ROM (read-only memory), RAM (random access memory), hard disk, CD-ROM, and DVD, or a combination of storage media.

[0189] The processor (930) can control a series of processes to enable the base station to operate as described above. For example, the transceiver (910) can receive a data signal including a control signal transmitted by the terminal, and the processor (930) can determine the result of receiving the control signal and the data signal transmitted by the terminal.

[0190] The embodiments disclosed herein may be implemented through at least one software program that executes on at least one hardware device and performs network management functions for controlling network elements. The elements include blocks that may be at least one of a hardware device or a combination of a hardware device and a software module.

[0191] The embodiments disclosed herein describe a circuit for performing analog calibration for an extensible multi-voltage memory interface driver. Accordingly, the scope of protection extends to such a program, and in addition to computer-readable means having a message therein, such computer-readable storage means is understood to include program code means for implementing one or more steps of a method when the program is executed on a server or mobile device or any suitable programmable device. In at least one embodiment, the method is implemented through or together with a software program written, for example, in the Very High Speed ​​Integrated Circuit Hardware Description Language (VHDL) or another programming language, or is implemented by one or more VHDL or several software modules executed on at least one hardware device. The hardware device may be any type of portable device capable of being programmable. The device may also include means that may be, for example, hardware means such as an ASIC, or a combination of hardware means and software means such as an ASIC and an FPGA, or at least one microprocessor and at least one memory in which software modules are located. The method embodiments described herein may be implemented partially in hardware and partially in software. Alternatively, the present disclosure may be implemented on different hardware devices, for example, using a plurality of CPUs.

[0192] Although the present disclosure has been illustrated and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various modifications in form and detail may be made without departing from the spirit and scope of the present disclosure as defined by the appended claims and equivalents.

Claims

Claim 1 As a terminal (user equipment, UE) in a wireless communication system, the device comprises: a transceiver; and a control unit coupled to the transceiver, wherein the control unit comprises: Stores first information regarding a successful change or addition of a PSCell (primary secondary cell group, SCG) cell, and Send a message to the base station containing a report on the successful PSCell change or addition, and Perform the deregistration procedure from the network, and A terminal configured to discard the first information regarding the successful PSCell change or addition during the above deregistration procedure. Claim 2 In claim 1, the deregistration procedure is initiated by one of the terminal or the network, the terminal. Claim 3 In claim 1, the terminal, wherein the first information regarding the successful PSCell change or addition is the variable VarSuccessPSCell-Report. Claim 4 In claim 1, the control unit is: A terminal further configured to receive second information from the base station for requesting the terminal to attempt to make detailed location information available using a GNSS (global navigation satellite system), wherein if the second information is associated with a cell group associated with the successful PSCell change or addition, the second information includes available detailed location information. Claim 5 In claim 4, the terminal, wherein the second information is obtainCommonLocation information. Claim 6 In claim 1, the control unit is: Receive a first RRC (radio resource control) reconfiguration message from the base station, the message including an indicator indicating whether a PSCell change procedure is initiated by a secondary node (SN), and A terminal further configured to receive a second RRC reset message from the base station, wherein if the second RRC reset message does not include the indicator, the configuration information for the successful PSCell change or addition associated with the first RRC reset is released. Claim 7 In claim 6, the above indicator is a terminal that is sn-initiatedPSCellChange information. Claim 8 A method performed by a terminal (user equipment, UE) in a wireless communication system, comprising: storing first information regarding a successful change or addition of a PSCell (primary secondary cell group, SCG) cell; transmitting a message to a base station including a report regarding the successful change or addition of the PSCell; performing a deregistration procedure from a network; and discarding the first information regarding the successful change or addition of the PSCell during the deregistration procedure. Claim 9 In claim 8, the above deregistration procedure is initiated by one of the terminal or the network. Claim 10 In claim 8, the method wherein the first information regarding the successful PSCell change or addition is the variable VarSuccessPSCell-Report. Claim 11 The method of claim 8 further comprises the step of receiving second information from the base station to request the terminal to attempt to make detailed location information available using a GNSS (navigation satellite system), wherein if the second information is associated with a cell group associated with the successful PSCell change or addition, the second information includes available detailed location information. Claim 12 In claim 11, the method wherein the second information is obtainCommonLocation information. Claim 13 A method according to claim 8, further comprising: receiving a first radio resource control (RRC) reconfiguration message from the base station including an indicator indicating whether a PSCell change procedure is initiated by a secondary node (SN); and receiving a second RRC reconfiguration message from the base station, wherein if the second RRC reconfiguration message does not include the indicator, the configuration information for the successful PSCell change or addition associated with the first RRC reconfiguration is released. Claim 14 In claim 13, the method wherein the indicator is sn-initiatedPSCellChange information.

Images