Method and system for releasing and adding dual connectivity

Abstract

The disclosure provides a method and a user equipment (UE) for managing configuration in a multi-radio dual connectivity (MR-DC) in a wireless communication network system. The method includes receiving by UE an MR-DC release and add configuration and other configuration associated with a secondary cell group (SCG) and determining by the UE whether an MR-DC release is triggered due to the reception of the MR-DC release and add configuration. Further, the method includes releasing by the UE the other configuration associated with the SCG except a successful primary secondary (PS) cell addition or change report (SPR) configuration configured by a source PS cell based on the MR-DC release being triggered due to the reception of the MR-DC release and add configuration.

Description

METHOD AND SYSTEM FOR RELEASING AND ADDING DUAL CONNECTIVITY

[0001] The disclosure relates to wireless communication network systems. More particularly, the disclosure relates to a method and a system for releasing and adding dual connectivity.

[0002] In wireless communication, dual connectivity (DC), or more technically, multi-radio dual connectivity (MR-DC), is an advancement specified by the 3rd generation partnership project (3GPP) in specifications such as technical specification (TS) 37.340. MR-DC allows a user equipment (UE) in RRC_CONNECTED mode to utilize radio resources provided by two distinct schedulers located in two different next generation radio access network (NG-RAN) nodes. These nodes are connected via a non-ideal backhaul, with one node providing new radio (NR) access and the other providing either evolved universal mobile telecommunication system (UMTS) terrestrial radio access (E-UTRA) or NR access.

[0003] In MR-DC, one node acts as the master node (MN) and the other as the secondary node (SN). The MN and SN are interconnected via a network interface, and at least the MN is connected to the core network. The NG-RAN supports NG-RAN E-UTRA-NR dual connectivity (NGEN-DC), where a UE is connected to one ng-eNB (an E-UTRA base station that can connect to the 5G core) acting as the MN and one gNB (5G base station) acting as the SN. Similarly, NR-E-UTRA dual connectivity (NE-DC) is supported, where the UE is connected to one gNB acting as the MN and one ng-eNB acting as the SN.

[0004] The MN may perform release and addition of the NR secondary cell group (SCG) configuration towards the UE during both MN-initiated and SN-initiated primary secondary cell (PSCell) changes. Release and addition may also occur during MN-initiated and SN-initiated conditional PSCell changes. This mechanism is commonly used in inter-vendor deployments where the UE moves from a source SN of one vendor to a target SN of another vendor. Moreover, this mechanism is widely used in mobility scenarios such as lower lLayer triggered mobility when used for inter-SN mobility or configuring intra-SN mobility along with inter-SN mobility. However, in the existing system, the UE does not log the success PSCell change and addition reports (SPR) for these scenarios, depriving the network of the opportunity to optimize mobility robustness.

[0005] Furthermore, self-organizing networks (SON) have emerged as a critical technology in modern wireless networks. SON enables automated and intelligent management of network resources to enhance performance and reduce operational complexity. In the context of 5G NR, SON plays a pivotal role in optimizing dual connectivity using SPR. The UE makes the SPR available to gNB(s). When the gNB fetches the SPR from the UE, it forwards the SPR to the MN that was serving the UE at the time the SPR was generated, using the ACCESS AND MOBILITY INDICATION message over Xn or by means of the Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer over NG.

[0006] The UE can be configured to report the SPR due to a near failure during PSCell addition or PSCell change in otherConfig. However, when PSCell mobility occurs due to MRDC-ReleaseAndAdd in the existing mechanisms, the UE does not report the SPR as it releases the entire otherConfig. This makes SPR completely unusable for various mobility scenarios including MN initiated PSCellChange or inter-SN LTM. This results in a lack of critical data that could be used to improve network performance and mobility robustness.

[0007] Thus, there is a need to address the above-mentioned disadvantages and shortcomings or at least provide a useful alternative.

[0008] The above information is presented as background information only to assist with an understanding of the disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the disclosure.

[0009] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a method and a UE for releasing and adding dual connectivity.

[0010] Another aspect of the disclosure is to provide a UE that determines whether the MR-DC release is triggered by the reception of MRDC Release and Add.

[0011] Yet another aspect of the disclosure is to provide a UE that releases otherConfig associated with the SCG except the successPSCell-Config configured by the source PS Cell when the MR-DC release is due to the reception of MRDC Release and Add.

[0012] Yet another aspect of the disclosure is to provide a UE that releases otherConfig associated with the SCG and the SPR configuration configured by the PCell when the MR-DC release is not due to the reception of MRDC Release and Add.

[0013] According to an embodiment of the disclosure, there is provided a method for managing configuration in a multi-radio dual connectivity (MR-DC) in a wireless communication network system. The method includes receiving by a UE an MR-DC release and add configuration and other configurations associated with an SCG. Further, the method includes determining by the UE whether an MR-DC release is triggered due to the reception of the MR-DC release and add configuration. Furthermore, the method includes releasing by the UE the other configuration associated with the SCG except a successful primary secondary (PS) cell addition or change report (SPR) configuration configured by a source primary secondary (PS) cell based on the MR-DC release being triggered due to the reception of the MR-DC release and add configuration.

[0014] According to an embodiment of the disclosure, there is provided a UE for managing configuration in a multi-radio dual connectivity (MR-DC) in a wireless communication network system. The UE includes memory storing instructions, andat least one processor communicatively coupled to the memory. The instructions, when executed by the at least one processor individually or collectively, cause the UE to receive an MR-DC release and add configuration and other configurations associated with an SCG. Further, the instructions, when executed by the at least one processor individually or collectively, cause the UE to determine whether an MR-DC release is triggered due to the reception of the MR-DC release and add configuration, and release the other configuration associated with the SCG except a successful primary secondary (PS) cell addition or change report (SPR) configuration configured by a source primary secondary (PS) cell based on the MR-DC release being triggered due to the reception of the MR-DC release and add configuration.

[0015] According to an embodiment of the disclosure, there is provided one or more non-transitory computer-readable storage media storing one or more computer programs including computer-executable instructions that, when executed by one or more processors of a user equipment (UE) individually or collectively, cause the UE to perform operations. The operations comprises receiving an MR-DC release and add configuration and other configuration associated with an SCG, and releasing the other configuration associated with the SCG except a successful primary secondary (PS) cell addition or change report (SPR) configuration configured by a source primary secondary (PS) cell based on the MR-DC release being triggered due to the reception of the MR-DC release and add configuration.

[0016] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

[0017] The above and other aspects, features, and advantages certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0018] FIG. 1 is a flow diagram that illustrates an existing method for releasing an MR-DC in a wireless communication network system according to related art.

[0019] FIG. 2 is a block diagram that illustrates the hardware components associated with the UE according to various embodiments of the disclosure.

[0020] FIG. 3 is a flow diagram that illustrates a proposed method for releasing an MR-DC in a wireless communication network system according to various embodiments of the disclosure.

[0021] Throughout the drawings, it should be note that like reference numbers are used to depict the same or similar features, and structures.

[0022] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding, but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

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

[0024] It will be understood that, unless specifically stated, the singular forms "one", "a", "an", "the", and "said" used herein may also include the plural form. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces. When it refers to one element as being "connected" or "coupled" to another element, the one element may be directly connected or coupled to the other element, or it may refer to a connection relationship between the one element and the other element established through an intermediate element. In addition, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled.

[0025] The terms "includes" and "may include" mean the presentation of the corresponding disclosed functions, operations, or components that can be used in various embodiments of the disclosure, but do not limit the presentation of one or more additional functions, operations, or features. In addition, the terms such as "include" or "have" may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.

[0026] The term "or" used in various embodiments of the disclosure includes any or all of combinations of listed words. For example, the expression "A or B" may include A, may include B, or may include both A and B. When describing a plurality of (two or more) items, the plurality of items may refer to one, more, or all of the plurality of items if a relationship among the plurality of items is not explicitly defined. For example, for the description "a parameter A comprises A1, A2, A3", it may be implemented as parameter A comprising A1, A2 or A3, or as parameter A comprising at least two of the three items of the parameter A1, A2, A3.

[0027] All terms (including technical or scientific terms) used in the disclosure have the same meaning as understood by those skilled in the art to which the disclosure belongs, unless defined differently. Such terms as those defined in a generally used dictionary are to be interpreted to have the meanings equal to the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the disclosure.

[0028] At least part of the functions in a device or electronic apparatus provided in an embodiment of the disclosure may be implemented through an artificial intelligence (AI) model, such as, at least one of a plurality of modules of the device or electronic apparatus may be implemented through the AI model. A function associated with AI may be performed through the non-volatile memory, the volatile memory, and the processor.

[0029] It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by one or more computer programs which include instructions. The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0030] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like 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 processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a wireless fidelity (Wi-Fi) chip, a Bluetooth®chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print 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, or the like.

[0031] Throughout the specification, the terms "MR-DC release and add configuration" and "mrdc-ReleaseAndAdd" are used interchangeably and have the same meaning.

[0032] Throughout the specification, the definitions of the various terms used in the embodiments are as follows:

[0033] Multi-radio dual connectivity (MR-DC): It is a generalization of the Intra-E-UTRA dual connectivity (DC) described in TS 36.300, where a multiple Rx / Tx capable UE may be configured to utilize resources provided by two different nodes connected via non-ideal backhaul, one providing NR access and the other one providing either E-UTRA or NR access. One node acts as the MN and the other as the SN. Both MN and SN may support a group of cells by carrier aggregation. Cell Group associated to MN is called master cell group (MCG) and the cell group associated to SN is called secondary cell group (SCG). Most important cell configured for the UE by the MN is known as primary cell (PCell) and the most important cell configured for the UE by SN is known as primary SCG cell (PSCell).The MN and SN are connected via a network interface and at least the MN is connected to the core network. The MN and / or the SN may be operated with shared spectrum channel access.

[0034] Successful PSCell addition / change report (SPR): The objective of the SPR is to detect sub-optimal successful PSCell change / CPC or successful PSCell addition / CPA. For analysis of such sub-optimal successful PSCell change / CPC and successful PSCell addition / CPA, the UE may collect SPR based on the triggers configured by the network and makes the SPR available to the network as specified in TS 38.331. If the SPR available indication via SN RRCReconfigurationComplete is received by SN, SN should inform MN that an SPR is available at the UE via S-NODE MODIFICATION REQUIRED message. For PSCell addition / CPA and PSCell change / CPC (MN or SN initiated), the target SN always decides the T304 trigger for SPR and performs root cause analysis. For SN-initiated PSCell change / CPC, the source SN decides the T310 / T312 triggers for SPR and is responsible for SPR related optimizations e.g., to optimize PSCell change / CPC configuration or associated mobility thresholds or adjust T310 / T312 timer values. For MN-initiated PSCell change / CPC, the MN decides the T310 / T312 triggers for SPR. MN may optimize PSCell change / CPC configuration or associated mobility thresholds or both. Source SN may optimize lower layer issues e.g., adjust T310 / T312 timer values. The SPR may be fetched from the UE by the MN while the UE is still connected to the MN, or by a node different from the MN that was serving the UE when PSCell addition or PSCell change occurred if the UE is not connected to the MN anymore. In case the SPR is retrieved in a node different from the MN that was serving the UE when PSCell addition or PSCell change occurred, the SPR is first forwarded to that MN. The MN may forward the SPR to the appropriate SN(s) to perform the SPR related optimization.

[0035] MR-DC release: Network (MN) may release MR-DC anytime by sending RRC signalling. The UE may also autonomously release MR-DC when the radio link failure occurs or when it moves to RRC_IDLE or RRC_INACTIVE. Typically, in wireless networks during MR-DC release the UE and the network apparatus releases all the configurations associated to the SCG and the configurations in the MCG which are configured for the SCG operations. This is done to avoid resource wastage and to maintain a clean slate when MR-DC is established again. This is also because, if the UE keeps any of these configuration, master node (MN) and UE will be out of sync as network cannot keep this information, since the dedicated MN-SN connection for the UE is also lost. So, there is no scenario till Rel-18 where the UE keeps any configuration or performs any actions based on the configuration from the released PSCell in MR-DC release. Wireless systems also support MR-DC release including MR-DC Release and Add configuration for performing mobility where one PSCell (source PSCell) is released and another PSCell (target PSCell) is added.

[0036] In wireless technologies like 5G NR, devices may move across different cells. Mobility is performed using a procedure called cell reselection in RRC_IDLE mode. Till NR R17, mobility is performed using a procedure called handover in RRC_CONNECTED mode. Network controlled mobility applies to UEs in RRC_CONNECTED. It requires explicit RRC signalling to be triggered by the gNB in NR. Handover in NR usually consists of three operations: handover preparation, handover execution and handover completion. gNB may configure the UE to report measurements and based on the reported measurements or based on its own understanding of the network topology, gNB will send RRC reconfiguration message to handover the UE to another cell called target cell from the source cell. UE accesses the target cell and sends RRC reconfiguration complete message. In an alternative way introduced in 3gpp NR release 16, gNB may configure the UE with the execution conditions for triggering handover and once the execution conditions are satisfied, the UE may move to target cell and sends the RRC reconfiguration complete. In all these methods, UE performs handover by sending layer 3 (RRC) messages which causes considerable signalling overhead and latency issues. During handover, UE may be configured to apply full configuration during a L3 handover, and if configured UE applies full configuration as described in section 5.3.5.11 of TS 38.331.

[0037] The handover, and conditional handover (CHO) as layer 3 mobility may be referred. In case of dual connectivity, UE may perform PSCellChange or conditional PSCellChange. PSCellChange or conditional PSCellChange may be configured by either MN or SN. In the context of dual connectivity, PSCellChange or conditional PSCellChange may also be referred as layer 3 mobility. e.g. handover, conditional handover, PSCellChange, conditional PSCellChange etc. refers to L3 mobility. PSCellChange or conditional PSCellChange as SCG layer 3 mobility and the handover and the CHO as MCG layer 3 mobility in the context of dual connectivity may be referred.

[0038] Another type of mobility supported in wireless systems in lower layer triggered mobility (LTM). LTM may be based on L1 measurements or L3 measurements. It may be triggered by lower layer signaling or based on a condition or as part of a recovery from failure. In wireless technologies like NR, LTM is applicable for both MCG mobility and SCG mobility.

[0039] A 5G NR radio access network also known as next generation radio network (NG-RAN) may include a number of NR base stations knows as gNBs. gNBs may be connected to each other through Xn interface, and will be connected to various core network elements like access and mobility management function (AMF), user plane function (UPF) etc. Further gNBs may be divided into two physical entities named centralized unit (CU) and distributed unit (DU). CU provides support for the higher layers of the protocol stack such as session data application protocol (SDAP), packet data convergence protocol (PDCP) and radio resource control (RRC) while DU provides support for the lower layers of the protocol stack such as radio link control (RLC), medium access control (MAC) and physical layer. Each gNB may have multiple cells serving many user Equipments (UEs). There are a large number of algorithms 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 optimal 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 etc. 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 may be divided into three categories: Self-Configuration, Self-Optimization and Self-Healing. The SON architecture may be a centralized, distributed or a hybrid solution. Mobility robustness optimization (MRO) is a SON technique which is used to optimize various parameters related to mobility.

[0040] According to 3gpp specifications, the MRO aims at detecting and enabling correction of following problems: Connection failure due to intra-system or inter-system mobility; inter-system unnecessary HO (too early inter-system HO from NR to E-UTRAN with no radio link failure); and inter-system HO ping-pong. Further, MRO provides means to distinguish the above problems from NR coverage related problems and other problems, not related to mobility.

[0041] A UE may be configured for reporting information related to successful PSCell addition and successful PSCell change. SuccessPSCell-Config or SPR config may be defined as below in NR Release 18,

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

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

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

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

[0046] ...

[0047] }

[0048] These information could be configured to be stored and reported in a report called SuccessPSCell Report (SPR as defined below).

[0049] SuccessPSCell-Report-r18 ::= SEQUENCE {

[0050] pCellId-r18 CGI-Info-Logging-r16,

[0051] sourcePSCellInfo-r18 SEQUENCE {

[0052] sourcePSCellId-r18 CHOICE {

[0053] cellGlobalId-r18 CGI-Info-Logging-r16,

[0054] pci-arfcn-r18 PCI-ARFCN-EUTRA-r16

[0055] },

[0056] sourcePSCellMeas-r18 MeasResultSuccessHONR-r17 OPTIONAL

[0057] }

[0058] OPTIONAL,

[0059] targetPSCellInfo-r18 SEQUENCE {

[0060] targetPSCellId-r18 CHOICE {

[0061] cellGlobalId-r18 CGI-Info-Logging-r16,

[0062] pci-arfcn-r18 PCI-ARFCN-NR-r16

[0063] },

[0064] targetPSCellMeas-r18 MeasResultSuccessHONR-r17 OPTIONAL

[0065] },

[0066] measResultNeighCells-r18 SEQUENCE {

[0067] measResultListNR-r18 MeasResultList2NR-r16 OPTIONAL,

[0068] measResultListEUTRA-r18 MeasResultList2EUTRA-r16 OPTIONAL

[0069] }

[0070] OPTIONAL,

[0071] spr-Cause-r18 SPR-Cause-r18 OPTIONAL,

[0072] timeSinceCPAC-Reconfig-r18 TimeSinceCPAC-Reconfig-r18 OPTIONAL,

[0073] locationInfo-r18 LocationInfo-r16 OPTIONAL,

[0074] ra-InformationCommon-r18 RA-InformationCommon-r16 OPTIONAL,

[0075] sn-InitiatedPSCellChange-r18 ENUMERATED {true} OPTIONAL,

[0076] ...

[0077] }

[0078] The UE releases SPR configuration during the release of dual connectivity such as MR-DC release procedure in NR. This helps the UE to save the memory and processing. This will also ensure that the network and the UE are synchronized with respect to the configurations. 3gpp TS 38.331 v 18.3.0 is considered as background for the disclosure.

[0079] MN may use MR-DC "release and add" to perform a　release in one secondary node (SCG cell) and perform a clean establishment in another SN, for performing mobility. When this mobility was performed closer to a SCG radio link failure, there is no way by which the network can identify that there is a near failure, in the prior art, as any configuration related to SCG is released during the MR-DC release.

[0080] Below details from TS 38.331 v18.3.0 may specifically be considered as background:

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

[0082] The UE shall for the PSCell:

[0083] 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

[0084] 1>if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG 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 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

[0085] 1>if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG 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 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:

[0086] 1>if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG 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 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

[0087] 1>if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG 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 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:

[0088] 2>clear the information included in VarSuccessPSCell-Report, if any;

[0089] 2>store the successful PSCell change or addition information in VarSuccessPSCell-Report and determine the content in VarSuccessPSCell-Report as follows:

[0090] According to the background, the above section may be called during following procedures and conditions:

[0091] 2>if the scg-State is not included in the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message:

[0092] 3>perform SCG activation as specified in 5.3.5.13a;

[0093] 3>if reconfigurationWithSync was included in spCellConfig in nr-SCG:

[0094] 4>if the RRCReconfiguration message is not applied due to an LTM cell switch execution for which lower layer indicates to skip the Random Access procedure:

[0095] 5>initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];

[0096] 4>if the UE was configured with successPSCell-Config when connected to the source PSCell (for PSCell change) or to the PCell (for PSCell addition or change):

[0097] 5>perform the actions for the successful PSCell change or addition report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the SCG;

[0098] Another scenario is as below:

[0099] 2>if the RRCReconfiguration message was received within DLInformationTransferMRDC:

[0100] 3>if the RRCReconfiguration message was received within the nr-SCG within mrdc-SecondaryCellGroup (NR SCG RRC Reconfiguration):

[0101] 4>if the scg-State is not included in the RRCReconfiguration message containing the RRCReconfiguration message:

[0102] 5>if reconfigurationWithSync was included in spCellConfig in nr-SCG:

[0103] 6>initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];

[0104] 6>if the UE was configured with successPSCell-Config when connected to the source PSCell (for PSCell change) or to the PCell (for PSCell addition or change):

[0105] 7>perform the actions for the successful PSCell change report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the SCG

[0106] Yet another scenario is as follows:

[0107] 1>if the RRCReconfiguration message was received via SRB3 (UE in NR-DC):

[0108] 2>if the RRCReconfiguration message was received within DLInformationTransferMRDC:

[0109] 3>if the RRCReconfiguration message was received within the nr-SCG within mrdc-SecondaryCellGroup (NR SCG RRC Reconfiguration):

[0110] 4>if the scg-State is not included in the RRCReconfiguration message containing the RRCReconfiguration message:

[0111] 5>if reconfigurationWithSync was included in spCellConfig in nr-SCG:

[0112] 6>initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];

[0113] 6>if the UE was configured with successPSCell-Config when connected to the source PSCell (for PSCell change) or to the PCell (for PSCell addition or change):

[0114] 7>perform the actions for the successful PSCell change report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the SCG;

[0115] Configuration parameters may be defined as below:

[0116] -thresholdPercentageT304-SCG: This field indicates the threshold for the ratio in percentage between the elapsed T304 timer associated to the target PSCell and the configured value of the T304 timer. Value p40 corresponds to 40%, value p60 corresponds to 60% and so on. This field is set in the otherConfig configured by the target PSCell of the PSCell change or addition.

[0117] -thresholdPercentageT310-SCG: This field indicates the threshold for the ratio in percentage between the elapsed T310 timer associated to the source PSCell and the configured value of the T310 timer. Value p40 corresponds to 40%, value p60 corresponds to 60% and so on. This field is set in the otherConfig configured by the source PSCell of the PSCell change or CPC, or in the otherConfig configured by the PCell for the PSCell change or CPC. This field is not configured at the time of PSCell change via SRB3.

[0118] -thresholdPercentageT312-SCG: This field indicates the threshold for the ratio in percentage between the elapsed T312 timer associated to the measurement identity of the target PSCell and the configured value of the T312 timer. Value p20 corresponds to 20%, value p40 corresponds to 40% and so on. This field is set in the otherConfig configured by the source PSCell of the PSCell change or CPC, or in the otherConfig configured by the PCell for the PSCell change or CPC. This field is not configured in case of SN initiated PSCell change via SRB3.

[0119] FIG. 1 is a flow diagram that illustrates an existing method for releasing a MR-DC in a wireless communication network system according to related art.

[0120] Referring to FIG. 1, the UE behavior in the existing mechanism is as follows: At operation 101, the UE receives a MR-DC configuration from a network apparatus. This configuration typically may include parameters for SCG configurations, detailing the specific radio resources and parameters to be used. At operation 102, the UE performs MR-DC release, including MRDC release and Add configuration. This operation involves the UE initiating the release of SN configuration with the current primary SCG cell (PSCell). At operation 103, the UE releases all the configuration received in OtherConfig associated with the SCG. This may include releasing the configuration related to various operations for the SCG, such as handling the exchange of power saving information or SPR configuration. At operation 104, the UE releases the SPR configuration received from a PCell. As a result, the UE doesn't log or report SPR, and there is no optimization possible for the near failures in the PSCell before the release and add of the MR-DC. This lack of logging and reporting means that the network cannot gather data on the performance using the SPR, leading to potential inefficiencies and missed opportunities for optimization.

[0121] Embodiments disclosed herein provide a UE and a method for releasing a MR-DC in a wireless communication network system. The solution proposes that the UE checks whether the MR-DC release is due to the reception of Release and Add; if so, it releases all configuration in other configuration associated with SCG except SPR configuration from a source PSCell. This selective release ensures that critical configurations related to the SPR are retained, allowing for continued monitoring and optimization of the PSCellChange. It also keeps the SPR configuration received from a Pcell. By retaining these configurations, the UE may still perform SPR determination and logging. The UE logs and reports the SPR based on configuration. The configuration may be further released after the determination. This logging and reporting provide data to the network, enabling better resource management and optimization. When the MR-DC release is not due to the reception of release and add, the UE will not have MR-DC configuration till the MR-DC is added again in a new RRC message. So, releasing the SPR configuration during this time helps the UE to save memory. It allows the network to configure SPR without depending on a previous SPR configuration.

[0122] Referring now to the drawings and more particularly to FIGS. 2 through 3, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0123] FIG. 2 is a block diagram illustrating the hardware components associated with the UE (200) according to various embodiments of the disclosure.

[0124] Examples of the UE (200) can include, but are not limited to, consumer electronics (e.g., mobile phones and smartphones), tablets, wearable devices, computing devices (e.g., laptops, notebooks, desktops, workstations, etc.), IoT devices, automotive systems (e.g., connected cars, autonomous vehicles, vehicle-to-everything (V2X) communication devices, etc.), enterprise devices such as robotics, specialized equipment (e.g. medical devices, public safety devices, etc.), and media devices (such as gaming consoles, streaming devices, etc.).

[0125] Examples of the network apparatus can include, but are not limited to, base stations (e.g., macro cells, small cells, femtocells, picocells) for wireless communication, antennas and RF units (e.g., multiple input multiple output (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, ddge 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.

[0126] Referring to FIG. 2, the UE (200) may include a processor (201), memory (202), a communicator (203), and an MRDC controller (204). The communicator (203) and the MRDC controller (204) may be included in the processor (201).

[0127] The processor (201) may be used for releasing a MR-DC in a wireless communication network system. The processor (201) may handle the execution of instructions and manages the overall operation of the UE. Communication between the processor (201), the memory (202), the communicator (203), and the MRDC controller (204) may be facilitated by the processor (201). Instructions stored in the memory (202) may be executed by the processor (201), which also is used for releasing the MR-DC. The processor (201) may include one or a plurality of processors such as a central processing unit (CPU), an application processor (AP), a graphics processing unit (GPU), a visual processing unit (VPU), and / or a neural processing unit (NPU).

[0128] The memory (202) may store the operating system, application software, and temporary data used by the processor (201). The memory (202) may provide the necessary storage for the instructions and data required for the MR-DC release process. Instructions to be executed by the processor (201) may be stored in the memory (202). The memory (202) is not limited to volatile memory and / or non-volatile memory and may include a plurality of computer-readable storage media. Non-volatile storage elements such as magnetic hard disks, optical disks, floppy disks, flash memories, EPROM, or EEPROM memories may be included in the memory (202). In an example embodiment, the memory (202) may be considered a non-transitory storage medium, indicating that it is not embodied in a carrier wave or a propagated signal but not necessarily non-movable. The memory (202) may store the MR-DC configuration received from the network apparatus.

[0129] The communicator (203) may facilitate communication between the UE (200) and the network apparatus, supporting various communication protocols such as transmission control protocol / internet protocol (TCP / IP), user datagram protocol (UDP), and second-generation digital video broadcasting by satellite (DVB-S2). It ensures that the UE can communicate effectively with the network apparatus, sending and receiving the necessary data for the MR-DC release process. Internal communication between hardware components via one or more networks is also facilitated by the communicator (203). An electronic circuit specific to a standard that enables wired or wireless communication may be included in the communicator (203). The communicator (203) may receive the MR-DC configuration from the network apparatus.

[0130] In an embodiment, the MRDC controller (204) may be a hardware component designed for releasing a MR-DC in a wireless communication network system. This hardware implementation ensures efficient and reliable execution of processes integral to MR-DC release with MR-DC releasing and adding. The MRDC controller (204) may include a multi-core architecture tailored to optimize the release of a MR-DC in a wireless communication network system. Each core within the architecture may be specifically designed to execute distinct functions.

[0131] In an embodiment, the MRDC controller (204) may receive a MR-DC release and add configuration and other configuration associated with a SCG and where the other configuration may include at least one of a SPR configuration configured by a source PSCell and a SPR configuration configured by a PCell. The at least one of SPR configuration configured by a source PSCell and a SPR configuration configured by a PCell may comprise thresholdPercentageT310-SCG or thresholdPercentageT312-SCG. The MRDC controller (204) may determine whether a MR-DC release is triggered by a reception of MR-DC Release and add configuration from the network apparatus and may perform one of releases the other configuration associated with the SCG except the SPR configuration configured by the source PS cell and retaining the other configuration configured by the PCell upon the release of the MR-DC when the MR-DC release is triggered due to the reception of MR-DC release and add configuration from the network apparatus and releases the other configuration associated with the SCG and releasing the SPR configuration configured by the PCell when the MR-DC release is not triggered due to the reception of the MR-DC release and add configuration from the network apparatus. This selective release process ensures that relevant configurations are retained, allowing for continued monitoring and optimization.

[0132] The MRDC controller (204) may log and report the SPR after releasing the other configuration associated with the SCG except the SPR configuration configured by the source PS cell and retains the SPR configuration configured by the PCell. This logging process may provide data to the network, enabling better resource management and optimization. The MRDC controller (204) may retain the SPR configuration and performs SPR determination and SPR logging and reporting based on the determination using the SPR configuration which is retained after the MR-DC release including MR-DC release and add configuration.

[0133] FIG. 3 is a flow diagram that illustrates a proposed method for releasing a MR-DC in a wireless communication network system according to various embodiments of disclosure.

[0134] Referring to FIG. 3, at operaiton S301, the method may include receiving by a UE (200) a MR-DC release and add configuration and other configuration associated with a SCG and where the other configuration may include at least one of a SPR configuration configured by a source PS Cell and a SPR configuration configured by a PCell. The at least one of SPR configuration configured by a source PSCell and a SPR configuration configured by a PCell may comprise thresholdPercentageT310-SCG or thresholdPercentageT312-SCG. This may allow the UE (200) to have all the necessary information for the SPR logging. At operation S302, the method may include determining by the UE (200) whether a MR-DC release is triggered by a reception of MR-DC release and add configuration from the network apparatus. At operation S303, the method may include releasing the other configuration associated with the SCG except the SPR configuration configured by the source PS cell and retaining the other configuration configured by the PCell upon the release of the MR-DC when the MR-DC release is triggered due to the reception of MR-DC release and add configuration from the network apparatus. At operation S304, the method may include retaining by the UE (200) the SPR configuration configured by the PCell. This retention allows for continued monitoring and optimization using SPR. At operation S305, the method may include logging and reporting by the UE (200) the SPR after releasing the other configuration associated with the SCG except the SPR configuration configured by the source PS cell. This logging process may provide data to the network.

[0135] Further, the method may include determining by the UE (200) the SPR based on at least one of a threshold percentage T310-SCG or a threshold percentage T312-SCG received from the source PS cell, which is released due to the reception of MR-DC release and add configuration or the PCell, through checking by the UE (200) the current values of the T310 or the T312 timers in the SCG with the threshold percentage T310-SCG or the threshold percentage T312-SCG and logging the SPR (and performing other actions) according to section 5.7.10.7 of TS 38.331 if the thresholds are exceeded. This may ensure that the UE (200) can determine the SPR and take appropriate actions based on the thresholds.

[0136] At operation S306, the method may include releasing by the UE (200) the other configuration associated with the SCG when the MR-DC release is not triggered due to the reception of the MR-DC release and add configuration from the network apparatus. This may ensure that all configurations are released when the MR-DC release is not triggered by the specific configuration. At operation S307, the method may include releasing the SPR configuration configured by the PCell when the MR-DC release is not triggered due to the reception of the MR-DC release and add configuration from the network apparatus. This may ensure that the SPR configuration is also released when the MR-DC release is not triggered by the specific configuration. The UE (200) may not perform the SPR determination for T310 or T312 thresholds. This may ensure that the UE (200) performs the SPR determination when necessary. Further, the method may include the UE (200) retains the SPR configuration and performs SPR determination and SPR logging and reporting based on the determination using the SPR configuration which is retained after the MR-DC release including MR-DC release and add configuration.

[0137] In an embodiment in NR, the UE (200) may retain the SPR configuration received from MN during a MR-DC release when the MR-DC release is performed as a result of receiving mrdc-SecondaryCellGroupConfig set to setup and including MR-DC release and add configuration. This retention may ensure that the UE (200) can continue to operate even after the MR-DC release.

[0138] In an embodiment in NR, the UE (200) may retain the SPR configuration received from SN during a MR-DC release when the MR-DC release is performed as a result of receiving mrdc-SecondaryCellGroupConfig set to setup and including MR-DC release and add configuration. The UE (200) may release all the configuration in the OtherConfig associated with the SCG except the SPR configuration associated with the SCG. This selective release may ensure that critical configurations are retained, allowing for continued monitoring and optimization.

[0139] In an embodiment, according to TS 38.331, the UE (200) shall:

[0140] 1>as a result of MR-DC release triggered by E-UTRA or NR:

[0141] 2>release SRB3, if established, as specified in 5.3.5.6.2;

[0142] 2>release SRB5, if established, as specified in 5.3.5.6.2;

[0143] 2>release measConfig associated with SCG;

[0144] 2>if the UE is configured with NR SCG:

[0145] 3>release the SCG configuration as specified in clause 5.3.5.4;

[0146] 3>if this procedure is initiated due to the reception of mrdc-ReleaseAndAdd:

[0147] 4>release otherConfig associated with the SCG except the successPSCell-Config configured by the source PSCell, if configured;

[0148] 3>else:

[0149] 4>release otherConfig associated with the SCG, if configured;

[0150] 4>release successPSCell-Config configured by the PCell in the otherConfig, if configured;

[0151] 3> stop timers T346a, T346b, T346c, T346d, T346e, T346j and T346k associated with the SCG, if running;

[0152] 3> release bap-Config associated with the SCG, if configured;

[0153] 3> release the BAP entity as specified in TS 38.340

[0047] , if there is no configured bap-Config;

[0154] 3> release iab-IP-AddressConfigurationList associated with the SCG, if configured;

[0155] 3> perform the LTM configuration release procedure for the SCG as specified in clause 5.3.5.18.7;

[0156] 2> else if the UE is configured with E-UTRA SCG:

[0157] 3> release the SCG configuration as specified in TS 36.331

[0010] , clause 5.3.10.19 to release the E-UTRA SCG;

[0158] In the existing mechanisms, there is no special handling of MRDC Release and Add configuration during MRDC Release. The MN may perform release and add of the NR SCG configuration part towards the UE during both MN-initiated PSCellChange and SN-initiated PSCellChange when the target SN includes the indication of the full RRC configuration during PSCellChange. SgNB release and add may be performed also during MN-initiated conditional PSCellChange and SN-initiated conditional PSCellChange. The UE needs to use the thresholds for T310 and T312 configuration from source SN for determining SPR. As a result, the intended optimizations fails.

[0159] In an embodiment, the UE (200) may determine whether the MR-DC release is triggered by the reception of MRDC-Release and Add. If the MR-DC release is due to the reception of MRDC-ReleaseAndAdd, the UE may release otherConfig associated with the SCG except the successPSCell-Config configured by the source PSCell. If the MR-DC release is not due to the reception of MRDC-ReleaseAndAdd, the UE may release otherConfig associated with the SCG and the SPR configuration configured by the PCell.

[0160] In an embodiment, the solution may handle SPR configuration based on the reception of MRDC release and add configuration during MR-DC release. The solution may be required for supporting optimization of dual connectivity. The MRDC release and add configuration may be widely used for NR-DC, e.g., for full configuration and LTM cell switch. The solution may relate to the R18 WI for SON / MDT and is essential for optimization of SNPN. The solution may be commercialized by the networks and the UEs implementing SON / MDT for SPR.

[0161] In an embodiment, without the solution, the Release 18 feature SPR may not work in most of the scenarios. It is known that the network commonly sends mrdc-ReleaseAndAdd for the MN-initiated PSCell handovers and Inter-SN LTM cell switch or Intra-SN LTM cell switch, which can be configured together with Inter-LTM cell switch for some PSCells. As the UE releases SPR configuration without any check before actually performing the PSCell Change or addition, the UE will not be able to perform any optimization.

[0162] MN may use MR-DC "release and add" to perform a　release in one Secondary Node (SCG cell) and perform a clean establishment in another SN, for performing mobility. In the existing system including the frozen 3gpp release 18 specifications (V18.3.0 as in background), the UE may release all the configurations related to SCG　during the MR-DC release before the new cell is added through "release and add". This means the UE does not consider the MR-DC "release and add" as a mobility procedure with respect to the determination of SPR. As a result, when the MR-DC "release and add" was performed closer to a SCG radio link failure, there is no way by which the network can identify that there is a near failure, in the existing system. This will cause higher operational costs to the operator, as the operator needs to rely on costly drive tests for the mobility robustness optimization.

[0163] In an embodiment, the UE may keep SPR configuration and further performs SPR determination and SPR logging and reporting based on the determination using the SPR configuration which is kept after MR-DC release including release and add. For instance, in NR, the UE may further determine the SPR based on thresholdPercentageT310-SCG or thresholdPercentageT312-SCG received from the source PSCell which is released due to MR-DC release including "release and add" or from the PCell. Thus, the technical effect of the disclosure is that UE logs self-optimization information related to a released PSCell even after MR-DC is released. Since MRDC-ReleaseAndAdd is a commonly used procedure for many scenarios such as MCG LTM with SCG modification or PSCellChange, these embodiments allow the optimization of near failures.

[0164] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0165] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0166] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0167] While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.

Claims

1.A method for managing configuration in a multi-radio dual connectivity (MR-DC) in a wireless communication network system, the method comprising:receiving (S301), by a user equipment (UE) (200), an MR-DC release and add configuration and other configuration associated with a secondary cell group (SCG);determining (S302), by the UE (200), whether an MR-DC release is triggered due to the reception of the MR-DC release and add configuration; andreleasing (S303), by the UE (200), the other configuration associated with the SCG except a successful primary secondary (PS) cell addition or change report (SPR) configuration configured by a source PS cell based on the MR-DC release being triggered due to the reception of the MR-DC release and add configuration.2.The method of claim 1, further comprising:releasing, by the UE (200), the other configuration associated with the SCG and releasing the SPR configuration configured by a primary cell (PCell) based on the MR-DC release being not triggered due to the reception of the MR-DC release and add configuration.3.The method of claim 1, further comprising:logging and reporting, by the UE (200), an SPR after releasing the other configuration associated with the SCG except the SPR configuration configured by the source PS cell and retaining the SPR configuration configured by a primary cell (PCell).4.The method of claim 1, wherein at least one of the SPR configuration configured by the source PS cell and a SPR configuration configured by a primary cell (PCell) comprises of thresholdPercentageT310-SCG or thresholdPercentageT312-SCG.5.The method of claim 2, further comprising retaining the other configuration configured by the PCell based on the MR-DC release being triggered due to the reception of the MR-DC release and add configuration.6.A user equipment (200) for managing configuration in a multi-radio dual connectivity (MR-DC) in a wireless communication network system, the UE comprising:memory (202) storing instructions; andat least one processor (201) communicatively coupled to the memory (202), wherein the instructions, when executed by the at least one processor individually or collectively, cause the UE to:receive an MR-DC release and add configuration and other configuration associated with an SCG ;determine whether an MR-DC release is triggered due to the reception of the MR-DC release and add configuration; andrelease the other configuration associated with the SCG except a successful primary secondary (PS) cell addition or change report (SPR) configuration configured by a source primary secondary (PS) cell based on the MR-DC release being triggered due to the reception of the MR-DC release and add configuration.7.The UE (200) of claim 6, wherein the instructions, when executed by the at least one processor individually or collectively, cause the UE to:release the other configuration associated with the SCG and releasing the SPR configuration configured by a primary cell (PCell) based on the MR-DC release being not triggered due to the reception of the MR-DC release and add configuration.8.The UE (200) of claim 6, wherein the instructions, when executed by the at least one processor individually or collectively, cause the UE to:logs and reports an SPR after releasing the other configuration associated with the SCG except the SPR configuration configured by the source PS cell and retains the SPR configuration configured by the PCell.9.The UE (200) of claim 6, wherein at least one of the SPR configuration configured by the source PS cell and the SPR configuration configured by a primary cell (PCell) comprises of thresholdPercentageT310-SCG or thresholdPercentageT312-SCG.10.The UE (200) of claim 7, wherein the instructions, when executed by the at least one processor individually or collectively, cause the UE to retain the other configuration configured by the PCell based on the MR-DC release being triggered due to the reception of the MR-DC release and add configuration.11.One or more non-transitory computer-readable storage media storing one or more computer programs including computer-executable instructions that, when executed by one or more processors of a user equipment (UE) individually or collectively, cause the UE to perform operations, the operations comprising:receiving an MR-DC release and add configuration and other configuration associated with a secondary cell group (SCG);determining whether an MR-DC release is triggered due to the reception of the MR-DC release and add configuration; andreleasing the other configuration associated with the SCG except a successful primary secondary (PS) cell addition or change report (SPR) configuration configured by a source PS cell based on the MR-DC release being triggered due to the reception of the MR-DC release and add configuration.12.The one or more non-transitory computer-readable storage media of claim 11, wherein the instructions, when executed by the at least one processor individually or collectively, cause the UE to perform operations comprising:releasing the other configuration associated with the SCG and releasing the SPR configuration configured by a primary cell (PCell) based on the MR-DC release being not triggered due to the reception of the MR-DC release and add configuration.13.The one or more non-transitory computer-readable storage media of claim 11, wherein the instructions, when executed by the at least one processor individually or collectively, cause the UE to perform operations comprising:logging and reporting the SPR after releasing the other configuration associated with the SCG except the SPR configuration configured by the source PS cell and retains the SPR configuration configured by a primary cell (PCell).14.The one or more non-transitory computer-readable storage media of claim 11, wherein at least one of the SPR configuration configured by the source PS cell and the SPR configuration configured by the PCell comprises of thresholdPercentageT310-SCG or thresholdPercentageT312-SCG.15.The one or more non-transitory computer-readable storage media of claim 12, wherein the instructions, when executed by the at least one processor individually or collectively, cause the UE to perform operation comprising retaining the other configuration configured by the PCell based on the MR-DC release being triggered due to the reception of the MR-DC release and add configuration.

Images