Method and system for handling temporary capability restriction due to multi-SIM operations in wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present invention relates to a method and a User Equipment (UE) (101) for handling temporary capability restrictions during a Multi-Subscriber Identity Module (MUSIM) operation in a communication network system. The method includes generating a MUSIM cell release information by adding a serving cell index of a Primary Serving Cell (PSCell). The method further includes transmitting the MUSIM cell release information to a network apparatus, indicating that the serving cell needs to be released due to a MUSIM operation. Additionally, the method involves determining whether a MUSIM wait timer has expired at the UE (101). If the serving cell index of the PSCell is included in the MUSIM cell release information, a temporary capability restriction is applied, indicating that a Secondary Cell Group (SCG) is not supported.

Description

METHOD AND SYSTEM FOR HANDLING TEMPORARY CAPABILITY RESTRICTION DUE TO MULTI-SIM OPERATIONS IN WIRELESS COMMUNICATION SYSTEM

[0001] The present discloser relate to a wireless communication network. More particularly, the present disclosure relates to handling temporary capability restrictions due to Multi- Subscriber Identity Module (MUSIM) operations.

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

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

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

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

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

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

[0008] The principal object of the embodiments herein is to handle temporary capability restrictions due to MUSIM operations.

[0009] Another object of the invention is to handle MUSIM wait timer expiry while reporting serving cell index ofPSCell as the cell to release.

[0010] Yet another object of the invention is to handle interaction of reporting maxCC and band / bands combination and prohibit timers.

[0011] Yet another object of the invention is to handle gaps and interruptions on NR.

[0012] In an aspect, the objectives are achieved by providing a method for handling temporary capability restrictions during a MUSIM operation in the communication network system. The method includes generating by a UE a MUSIM cell to release information by adding a serving cell Index of a PSCell. Further, the method includes transmitting by the UE the MUSIM cell to release information to a network apparatus indicating that the serving cell needs to be released due to a MUSIM operation. Further, the method includes determining by the UE whether a MUSIM wait timer has expired at the UE. Further, the method includes applying by the UE a temporary capability restriction that a Secondary cell group (SCG) is not supported if the serving cell Index of the PSCell is included in the MUSIM cell to release information.

[0013] In yet another aspect, the objectives are achieved by providing a UE for handling temporary capability restrictions during MUSIM operation in a communication network system. The UE includes a processor, a memory, and a temporary capability restriction controller coupled with the memory and the processor. The temporary capability restriction controller generates a MUSIM cell to release information by adding a serving cell Index of a PSCell. Further, the temporary capability restriction controller transmits the MUSIM cell to release information to a network apparatus indicating that the serving cell needs to be released due to a MUSIM operation. Further, the temporary capability restriction controller determines whether a MUSIM wait timer has expired at the UE. Further, the temporary capability restriction controller applies a temporary capability restriction that a Secondary cell group (SCG) is not supported if the serving cell Index of the PSCell is included in the MUSIM cell to release information.

[0014] These and other aspects of the embodiments will be better understood with the following description and accompanying drawings. The descriptions, indicating preferred embodiments and specific details, are for illustration only and not for limitation. Many changes and modifications can be made within the scope of the embodiments.

[0015] The principal advantage of the embodiments herein is to handle temporary capability restrictions due to MUSIM operations, ensuring seamless network performance.

[0016] Another advantage of the invention is to enable MUSIM wait timer expiry handling while reporting the serving cell index of PSCell as the cell to release, preventing configuration mismatches.

[0017] Yet another advantage of the invention is to optimize the interaction of reporting maxCC and band / bands combination with prohibit timers, reducing unnecessary signaling overhead.

[0018] Yet another advantage of the invention is to manage gaps and interruptions on NR, enhancing dual connectivity and inter-frequency measurements.

[0019] The features, aspects, and advantages of the present embodiments are illustrated in the accompanying drawings, where like reference letters indicate corresponding parts across various figures. The embodiments will be better understood from the following description and drawings.

[0020] Fig. 1 is a block diagram of a UE for handling temporary capability restrictions during MUSIM operations in a communication network system according to embodiments disclosed herein.

[0021] Fig. 2 is a flow diagram that illustrates a method for handling temporary capability restrictions during MUSIM operations in a communication network system according to embodiments disclosed herein.

[0022] Fig. 3 is a flow diagram that illustrates handling of MUSIM wait timer expiry by the UE according to embodiments disclosed herein.

[0023] Fig. 4 is a flow diagram that illustrates the events of max CC reporting for MUSIM operations according to embodiments disclosed herein.

[0024] Fig. 5 is a flow diagram that illustrates the events of max CC reporting for MUSIM operations according to the embodiments as disclosed herein.

[0025] Fig. 6 is a flow diagram that illustrates the events of band restriction reporting for MUSIM operations according to the embodiments as disclosed herein.

[0026] Fig. 7 is a flow diagram that illustrates the events of band restriction reporting for MUSIM operations according to the embodiments as disclosed herein.

[0027] Fig. 8 is a flow diagram that illustrates a scenario of UE handling the temporary capability restrictions at RRC Reestablishment according to the embodiments as disclosed herein.

[0028] Fig. 9 is a flow diagram that illustrates a scenario of the UE handling the temporary capability restrictions at the RRC Reestablishment according to the embodiments as disclosed herein.

[0029] Fig. 10 is a flow diagram that illustrates events of the UE handling temporary capability restrictions at RRC Reestablishment when the radio link failure has occurred according to the embodiments as disclosed herein.

[0030] Fig. 11 is a flow diagram that illustrates events of network handling the temporary capability restrictions at RRC Reestablishment according to the embodiments as disclosed herein.

[0031] Fig. 12 is a flow diagram that illustrates events of SN handling of WaitTimer in dual connectivity according to the embodiments as disclosed herein.

[0032] Fig. 13 is a flow diagram that illustrates handling gap-related requirements after reporting MUSIM NeedForGaps according to the embodiments as disclosed herein.

[0033] Fig. 14 is a flow diagram that illustrates handling HandoverPreparationInformation for MUSIM NCSG and interruption requirements according to the embodiments as disclosed herein.

[0034] Due to the popularity of MUSIM devices that host more than one SIM to have the facility to connect to two or more different NWs in order to avail different data plans, have user profiles like home and office, increased connectivity / reliability with multiple connections, etc., MUSIM UEs were operating without network control by creating arbitrary gaps till 3GPP decided to introduce support for MUSIM device operations in Release 17. From Release 17, a connected USIM (USIM in the context of this invention means radio protocol stack associated with the User Equipment (UE, or terminal) in a MUSIM device can notify the connected mode network on network switching for multi-SIM operations. There are two types of network switching supported wherein one type connected USIM leaves the connected network and completely switches to the other USIM, i.e., the other USIM becomes connected. In the other type, the connected USIM requests a gap from its network for the MUSIM operations like listening for paging or performing measurements in the idle USIM.

[0035] Considering the case of a MUSIM UE with two USIMs (i.e., two UEs in the same MUSIM device) UE-A and UE-B, UE-A informs its network NW-A of temporary capability restrictions for the MUSIM operations. The issues with respect to handling of temporary capability restrictions are:

[0036] UE-A has informed NW-A of temporary capability restrictions which include the Primary Secondary CellGroup Cell (PSCell)'s unsupported status as a serving cell because of MUSIM operations. If the MUSIM wait timer expires, UE can apply the temporary capability restrictions. However, UE needs additional steps to handle any secondary cells related to the PSCell, which is not available in the current system. So there needs to be a method to handle this situation.

[0037] If the old gNodeB (gNB) fails to send the temporary capability limits to the network during Radio Resource Control (RRC) Reestablishment, it is possible that temporary capability constraints do not support the settings that UE has set up. There must be a way to specify how the UE and the network treat these configurations as the UE is unable to apply them.

[0038] Upon expiry of the MUSIM wait timer, the UE may apply the temporary capability restrictions. In dual connectivity, SN also needs to handle this application of temporary capability restrictions. There are no methods available currently to handle this.

[0039] In current systems, the UE initiates UE Assistance Information (UAI) for reporting temporary capability restriction for bands / band combinations if it has not reported such a restriction after being configured irrespective of any previous transmission of the UAI to report temporary restriction of Maximum number of Component Carriers (maxCC) and the prohibit timer started for the same. Similarly, UE initiates the UAI for reporting temporary capability restriction for maxCC if it has not reported such a restriction after being configured irrespective of any previous transmission of the UAI to report temporary restriction of bands / band combinations and the prohibit timer started for the same. This will lead to signalling overhead in the wireless networks. There needs to be a method to remove these restrictions.

[0040] In Release 17, MUSIM UE uses RRC UE Assistance Information (UAI) procedure to request gaps or to notify about leaving. The network (gNB) configures the UE whether it can provide the assistance information for MUSIM gaps or MUSIM Leave using otherConfig in RRC messages. Musim-GapAssistanceConfig in otherConfig is used for informing UE whether it can provide MUSIM assistance information for providing gap information. In Release 17, only per-UE gaps are supported for MUSIM operations.

[0041] In a technology like 5G NR, different UEs may have different hardware and software capabilities. Varying capabilities across devices could be hardware capabilities including radio frequency capabilities like bands or band combinations supported, processing capabilities (e.g., baseband computational capabilities), software capabilities like the support of various features, layer 1 capabilities, layer 2 capabilities, layer 3 capabilities, and so on. In general, the UE reports its UE radio access capabilities which are static at least when the network requests the capabilities. To limit signaling overhead, the gNB (5G NR base station) can request the UE to provide NR capabilities for a restricted set of bands. When responding, the UE can skip a subset of the requested band combinations when the corresponding UE capabilities are the same. A prohibit timer may be applied to reporting restrictions on a set of capabilities such as maxCC or bands, while as the prohibit timer may not be applied for reporting restrictions on yet another set of capability restrictions such as request to release SCG or a component carrier.

[0042] A 5G gNB provides a UE with various configurations / features through RRC messages like RRC reconfiguration or RRC resume based on the reported UE capability. Further, 5G gNB may comprise CU and DU.

[0043] Consider the case of a MUSIM UE with two USIMs (i.e., two UEs in the same MUSIM device) UE-A and UE-B. The UE-A informs its network NW-A of temporary capability restrictions for the MUSIM operations. In conventional methods, how the UE indicates its capabilities for reporting measurement gap and Network Controlled Small Gaps (NCSG) requirements for E-UTRA bands in UE Assistance Information (UAI) is not disclosed. How the UE handles NCSG and interruption requirements when the measurement gap requirements are reported in the UAI is not disclosed. How the UE reports the interruption requirements and how the source gNB reports the NCSG and interruption requirements to the target gNB is not disclosed. Hence, there remains a need for a method to handle the gaps and interruptions and MUSIM temporary capability restrictions.

[0044] Thus, it is desired to address the above-mentioned disadvantages, issues, or other shortcomings, or at least provide a useful alternative.

[0045] Like reference numerals represent like elements in the drawing. Elements are illustrated for simplicity and may not be to scale; some dimensions may be exaggerated for clarity. Conventional symbols may be used, and only pertinent details are shown to avoid obscuring the drawing with readily apparent information to those skilled in the art.

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

[0047] Embodiments disclosed herein provide a method for handling temporary capability restriction during MUSIM operations in wireless networks. The method includes generating by a UE a MUSIM cell to release information by adding a serving cell Index of a PSCell. Further, the method includes transmitting by the UE the MUSIM cell to release information to a network apparatus indicating that the serving cell needs to be released due to a MUSIM operation. Further, the method includes determining by the UE whether a MUSIM wait timer has expired at the UE. Further, the method includes applying by the UE a temporary capability restriction that a Secondary cell group (SCG) is not supported if the serving cell Index of the PSCell is included in the MUSIM cell to release information.

[0048] In an embodiment, when the UE receives RRCReconfiguration which contains a configuration that is not supported by the temporary capability restrictions while the Reestablishment procedure is ongoing, the UE moves to RRC_IDLE. Also, the UE which has temporary capability restriction at the time of RRC Reestablishment moves to RRC_IDLE state. If the UE has indicated temporary capability restriction to the old gNB or if the UE has temporary capability restriction due to other SIM action at the time of initiating RRC Reestablishment, the UE moves to RRC_IDLE. The UE may further send RRCSetupRequest to establish RRC connection.

[0049] In an embodiment, the Network Handling of temporary capability restrictions at RRCReestablishment is included where upon reception of musim-CapRestrictionInd in RRCReestablishmentComplete, the network node configures the UE with a limited configuration that is used until the network sends RRCReconfiguration based on actual restricted UE capabilities received, except when the RRCReconfiguration that resumes SRB2 / DRB is sent in parallel to sending the RRCReestablishment.

[0050] In an embodiment, the method includes SN handling of WaitTimer in dual connectivity where the temporary capability restriction is applied after the maximum value of wait timer.

[0051] In an embodiment, max CC reporting for MUSIM operations is included where based on the prohibit timer running due to UAI for sending other temporary capability restriction information, the UAI transmission is initiated.

[0052] In an embodiment, band restriction reporting for MUSIM operations is included where the transmission of the UEAssistanceInformation message is initiated to provide the current musim-AffectedBandsList and / or musim-AvoidedBandsList.

[0053] Due to the popularity of Multi-SIM (MUSIM) devices that host more than one SIM to have the facility to connect to two or more different NWs in order to avail different data plans, have user profiles like home and office, increased connectivity / reliability with multiple connections, etc., MUSIM UEs were operating without network control by creating arbitrary gaps till 3GPP decided to introduce support for MUSIM device operations in Release 17. From Release 17, a connected USIM (USIM in the context of this invention means radio protocol stack associated with the UE) in a MUSIM device can notify the connected mode network on network switching for multi-SIM operations. There are two types of network switching supported. In one type, the connected USIM leaves the connected network and completely switches to the other USIM, i.e., the other USIM becomes connected. In the other type, the connected USIM requests a gap from its network for the MUSIM operations like listening for paging or performing measurements in the idle USIM.

[0054] In Release 17, MUSIM UE uses RRC UE Assistance Information (UAI) procedure to request for gaps or to notify about leaving. The network (gNB) configures the UE whether it can provide the assistance information for MUSIM gaps or MUSIM Leave using other Config in RRC messages. Musim-Gap Assistance Config in otherConfig is used for informing UE whether it can provide MUSIM assistance information for providing gap information where only per-UE gaps are supported for MUSIM operations.

[0055] UE Capabilities:

[0056] In a technology like 5G NR, different UEs may have different hardware and software capabilities. Varying capabilities across devices could be hardware capabilities, including radio frequency capabilities like bands or band combinations supported, processing capabilities (e.g., baseband computational capabilities), software capabilities like the support of various features, layer 1 capabilities, layer 2 capabilities, layer 3 capabilities, and so on. In general, the UE reports its UE radio access capabilities, which are static at least when the network requests the capabilities to limit signaling overhead.

[0057] The gNB (5G NR base station) can request the UE to provide NR capabilities for a restricted set of bands. When responding, the UE can skip a subset of the requested band combinations when the corresponding UE capabilities are the same.

[0058] A 5G gNB provides a UE with various configurations / features through RRC messages like RRC reconfiguration or RRC resume based on the reported UE capability. Further, 5G gNB may comprise CU and DU.

[0059] Framework for supporting capability change:

[0060] Considering the case of a MUSIM UE with two USIMs (i.e., two UEs in the same MUSIM device) UE-A (USIM-A) and UE-B, the MUSIM UE supports dual transmission and reception, i.e., both UE-A and UE-B can be connected (RRC_CONNECTED) at the same time. Both UE-A and UE-B can transmit or receive data at the same time. It is possible that UE-A and UE-B may share some RF / radio / hardware / software resources. The UE capabilities (such as UE Radio Access Capabilities as described in 3GPP specifications like TS 38306) of UE-A may be different at different times depending on whether UE-B is connected (i.e., depending on whether UE-B uses the RF / radio / hardware / software resources).

[0061] Considering UE-A is in RRC-CONNECTED state with NWK-A, UE-B (USIM-B) is moving to RRC_CONNECTED or is transitioning to RRC_CONNECTED. UE-A provides the information to NWK-A to release some resources or update some parameters for the MUSIM operations. This information pertains to the change of some of the capabilities in UE-A, release of SCG or SCells in UE-A, deactivation of SCG or SCells in UE-A, information that SCG or SCells can be set up or activated in UE-A, etc., measurement gaps requirements related information in UE-A to facilitate MUSIM operations. The change can be temporary capability restrictions or removal of temporary capability restrictions. When UE-A is in RRC_CONNECTED mode and the UE capability changes due to activities in UE-B, UE-A informs NWK-A about the capability change through an RRC message such as UE Assistance Information. If the capability of UE-A has changed due to UE-B's activities when UE-A was in RRC_IDLE or RRC_INACTIVE mode, a similar approach as in RRC_CONNECTED can be used. UE-A may also indicate that the capability has changed in RRC setup complete or RRC resume complete. Capabilities may be retrieved later through UAI, etc. NWK-A may configure UE-A on whether it can inform changed capabilities, e.g., through otherConfig in the RRC Reconfiguration message.

[0062] In case of dual connectivity, UE-A may report the change of capabilities such as restriction in capabilities and removal of restriction of capabilities to the MN of NWK-A even when the capabilities are related to SN of NWK-A or when they are applicable for both MN and SN of NWK-A.

[0063] The network utilizes the updated capability received from the UE and reconfigures the UE with updated parameters. The network may update the configuration of dual connectivity, carrier aggregation, power control, interference coordination, DAPS configuration, number of layers, etc., based on the capability information including supported bands, supported band combination, scheduling pattern, and / or TDD UL / DL config information, etc.

[0064] A sample set of changes for reporting the temporary capability restrictions is given below based on 3gpp TS 38.331:

[0065]

[0066]

[0067]

[0068]

[0069]

[0070] Details of some of the Multi SIM operations are as given below:

[0071]

[0072]

[0073]

[0074] The UE behavior for Multi sim operations for dual active is captured in TS 38.331 as below (only the relevant sections included). Other Configuration can include:

[0075]

[0076] UE Assistance Information: The purpose of this procedure is for the UE to inform the network of: its preference on the MUSIM gaps, or; its preference on the MUSIM gap priority, or; its preference on the MUSIM temporary capability restriction.

[0077] Initiation includes:

[0078]

[0079]

[0080]

[0081] Actions related to transmission of UEAssistanceInformation message:

[0082] The UE shall set the contents of the UEAssistanceInformation message as follows:

[0083]

[0084]

[0085]

[0086]

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

[0088] NG-RAN supports Multi-Radio Dual Connectivity (MR-DC) operation whereby a user equipment (UE) in RRC_CONNECTED is configured to utilize radio resources provided by two distinct schedulers, located in two different NG-RAN nodes connected via a non-ideal backhaul, one providing NR (New Radio) access and the other one providing either E-UTRA (Evolved UMTS Terrestrial Radio Access) or NR access. One node acts as the master node (MN) and the other as the secondary node (SN). The MN and SN are connected via a network interface and at least the MN is connected to the core network. NG-RAN supports NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), in which a UE is connected to one ng-eNB (a E-UTRA base station that can connect to 5G core) that acts as a MN and one gNB (5G base station) that acts as a SN. NG-RAN also supports NR-E-UTRA Dual Connectivity (NE-DC), in which a UE is connected to one gNB that acts as a MN and one ng-eNB that acts as a SN. Primary cell of a master or secondary cell group is called SpCell. SpCell of a master cell group is called PCell while SpCell of a secondary cell group is called PSCell. In MR-DC, a group of serving cells associated with the Master Node, comprising of the SpCell (PCell) and optionally one or more SCells is called MCG or Master Cell Group. A group of serving cells associated with the Secondary Node, comprising of the SpCell (PSCell) and optionally one or more SCells. is known as Secondary Cell Group (SCG) in MR-DC the Frame timing and SFN between the cells in MCG and SCG may not be aligned.

[0089] MN may inform the received temporary capability restriction and the band filter it has configured to the SN. An example ASN.1 structure for informing the same from TS 38.331 is given below.

[0090] Referring now to the drawings, and more particularly to Fig. 1 through Fig. 14 where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0091] Fig. 1 is a block diagram of a UE for handling temporary capability restrictions during MUSIM operations in a communication network system according to embodiments disclosed herein. The UE (101) includes a processor (103), a memory (105), an I / O interface (107), and a temporary restriction capability controller (109). Furthermore, the processor (103) of the UE (101) communicates with the memory (105), the I / O interface (107), and the temporary restriction capability controller (109). The processor (103) is configured to execute instructions stored in the memory (105) and to perform various processes. The processor (103) can include one or a plurality of processors, can be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial Intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0092] Furthermore, the memory (105) of the UE (101) includes storage locations that can be addressed through the processor (103). The memory (105) is not limited to volatile or non-volatile memory and can include one or more computer-readable storage media. Non-volatile storage elements such as magnetic hard disks, optical discs, floppy discs, flash memories, EPROM, or EEPROM memories can also be included in the memory (105). Further, the memory (105) of the UE (101) can store various information about the network apparatus. The information can include, but is not limited to, the name of the network apparatus, the address of the network apparatus, and the location of the network apparatus.

[0093] The I / O interface (107) transmits information between the memory (105) and external peripheral devices, which are input-output devices associated with the UE (101). The I / O interface (107) receives various information from the network apparatus. This interface is used to maintain seamless communication between the UE (101) and external devices, ensuring that data is transmitted and received.

[0094] The temporary restriction capability controller (109) is coupled to the I / O interface (107) and the memory (105) for handling temporary capability restriction during MUSIM operations in the communication network system. This coupling allows for efficient data transfer and communication between the components, ensuring that the temporary restriction capability controller (109) can handle the temporary capability restriction. The temporary restriction capability controller (109) is an innovative integrated circuit that is implemented in the UE (101). In an embodiment, the structure of such an innovative integrated circuit includes a multi-core architecture that ensures enhanced MUSIM operations. Each core is optimized for specific tasks such as handling MUSIM wait timer expiry while reporting serving cell index as PSCell and interaction of reporting maxCC and the bands / band combination and the prohibit timers. The innovative integrated circuit for handling temporary capability restriction during MUSIM operations in the communication network system is made of a combination of analog and digital components designed to enhance the MUSIM operation. The analog components include a low-noise amplifier and a high-precision analog-to-digital converter to ensure accurate signal processing. The digital components consist of a microcontroller unit (MCU) and a digital signal processor (DSP) that work in tandem to handle the temporary capability restriction during MUSIM operations in the communication network system.

[0095] The temporary restriction capability controller (109) generates a MUSIM cell to release information by adding a serving cell index of PSCell. Further, the temporary restriction capability controller (109) transmits the MUSIM cell to release information to a network apparatus indicating that the serving cell needs to be released due to a MUSIM operation. The information may be send in RRC messages such as UE Assistance Information as described previously. Further, the temporary restriction capability controller (109) determines whether a MUSIM wait timer has expired at the UE (101). Further, the temporary restriction capability controller (109) applies the temporary capability restriction that an SCG is not supported if the serving cell index of the PSCell is included in the MUSIM cell to release a information.

[0096] In an embodiment, the temporary restriction capability controller (109) releases the SCG by releasing the PSCell and any SCell configured by the network apparatus on the SCG.

[0097] These embodiments provide a simple way to handle MUSIM wait timer when the UE has included MUSIM cell to release information by adding a serving cell index of PSCell in the RRC message. Alternative methods include the network preconfiguring the UE with a new SCG configuration with a different PSCell to be applied, which involves changes in multiple network interfaces and air interface and are very complex methods. Hence we provide a simpler method for handling this scenario.

[0098] In an embodiment, the temporary restriction capability controller (109) determines that the UE (101) has the temporary capability restriction on the combination of bands or on a maximum number of CCs. The combination of bands can include, but is not limited to, the band included in a MUSIM-Candidate band list and the MUSIM-Avoided bands list. Further, the temporary restriction capability controller (109) determines whether the UE (101) has transmitted the UAI message with the combination of bands or on the maximum number of CCs when the UE (101) is configured by the network apparatus to provide the UAI for the temporary capability restriction. Further, the temporary restriction capability controller (109) detects whether the timer T346n or any timer with equivalent functionality is running or expired. Further, the temporary restriction capability controller (109) prohibits the transmission of the UAI message while the timer T346n or any timer with equivalent functionality is running and when the UE has not transmitted the UAI message with the combination of bands or on the maximum number of CCs. Further, the temporary restriction capability controller (109) transmits the UAI message upon the timer T346n or any timer with equivalent functionality expiring. The embodiment is different from the normal way of UAI reporting as the initial transmission of sending a UAI for a particular information is not generally affected by whether another UAI is send for a different information within certain time interval. However, the embodiment ensures that UE doesn't send too many UAI messages for transmitting the band or band combination related information or maxCC. Since maxCC and band or band combination related information is related to an action that network may take in future, for e.g. while configuring in the future, deviation from the existing UAI way for the initial UAI transmission for these information is a better way.

[0099] Fig. 2 is a flow diagram that illustrates the method for handling temporary capability restrictions during MUSIM operations in a communication network system according to embodiments disclosed herein. At block 201, the method includes generating the MUSIM cell to release information by adding the serving cell index of a Primary Serving Cell. At block 203, the method includes transmitting the MUSIM cell to release information to the network apparatus indicating that the serving cell needs to be released due to a MUSIM operation. At block 205, the method includes determining whether the MUSIM wait timer has expired at the UE (101). At block 207, the method includes applying the temporary capability restriction that the SCG is not supported if the serving cell index of the PSCell is included in the MUSIM cell to release information. Embodiments disclosed herein provide the method for handling temporary capability restrictions due to MUSIM operations. The method includes releasing the SCG when the MUSIM wait timer has expired.

[0100] Fig. 3 is the flow diagram that illustrates the handling of MUSIM wait timer expiry by the UE according to embodiments disclosed herein. At block 301, determining if the UE-A (101) has sent the serving cell index of the PSCell in the list of serving cells to be released for the MUSIM operations and starts the MUSIM wait timer. Further, at block 303, the method includes whether the MUSIM wait timer expires. At block 305, the UE-A (101) releases SCG. Also, in an embodiment in NR, if the UE-A (101) has included ServCellIndex of PSCell in MUSIM-CellToRelease-r18 and the T348 expires, the UE (101) releases SCG. In an embodiment, if UE-A (101) has informed the NW-A that a serving cell has to be released due to MUSIM operations and the serving cell is the PSCell and the MUSIM wait timer expires, the UE-A (101) releases the SCG. The UE-A (101) releases the PSCell and any SCell configured by NW-A on the SCG.

[0101] The functions of the timer T348 at different instances is as shown in the table 1:

[0102]

[0103] In an embodiment, the network (hereinafter the network apparatus is interchangeably used as network) informs the UE (101) which serving cell can be used as PSCell if the UE (101) has included the serving cell index of PSCell in the list of serving cells to be released and the wait timer expires. The network also provides the configuration to be used when a new serving cell is used as PSCell upon wait timer expiry. In this case, the UE (101) uses the configured serving cell as the PSCell using the provided configuration.

[0104] In an embodiment, if MN has received MUSIM capability restrictions from the UE (101) and the capability restrictions indicate that the serving cell has to be released due to MUSIM operations and the serving cell is the PSCell, the MN releases SCG upon the expiry of the MUSIM wait timer.

[0105] Fig. 4 is a flow diagram that illustrates the events of max CC reporting for MUSIM operations according to embodiments disclosed herein. At block 401, the UE (101) determines whether the UE (101) has a temporary capability restriction on musim-MaxCC and the UE (101) did not transmit a UEAssistanceInformation message with musim-MaxCC since it was configured to provide MUSIM assistance information for temporary capability restriction.

[0106] Further, at block 403, the UE (101) determines whether the prohibit timer is running due to UAI for sending other temporary capability restriction information. Prohibit timer may be started during initial transmission of capability restriction related to maxCC due to the transmission of temporary capability restriction information related to bands or band combinations. Transmission of some other temporary capability restrictions like SCG to be released on serving cell to be released may not result in starting the prohibit timer. At block 405, the UE (101) initiates the UAI transmission when the prohibit timer is not running. At block 407, the UE (101) transmits the UAI after the prohibit timer expiry or along with other UAI transmission when the prohibit timer is running due to UAI for sending other temporary capability restriction information.

[0107] Fig. 5 is a flow diagram that illustrates the events of maxCC reporting for MUSIM operations according to the embodiments as disclosed herein. At block 501, the UE (101) determines whether it has a temporary capability restriction on musim-MaxCC and whether the UE did not transmit a UEAssistanceInformation message with musim-MaxCC since it was configured to provide MUSIM assistance information for temporary capability restriction. Further, at block 503, the UE (101) initiates UAI transmission and starts or restarts T346n. In an embodiment, upon expiry of the MUSIM wait timer and if the UE has sent musim-MaxCC in the temporary capability restrictions, the UE identifies the SCells to be released and releases them.

[0108] Fig. 6 is a flow diagram that illustrates the events of band restriction reporting for MUSIM operations according to the embodiments as disclosed herein. At block 601, the UE (101) determines whether it has the temporary capability restriction on the combination(s) of bands comprising band(s) included in the musim-CandidateBandList. Also, the UE (101) did not transmit a UEAssistanceInformation message with musim-AffectedBandsList and / or musim-AvoidedBandsList since it was configured to provide MUSIM assistance information for temporary capability restriction and the timer T346n is not running.

[0109] Further, at block 603, the UE (101) determines whether the prohibit timer is running due to UAI for sending other temporary capability restriction information. Prohibit timer may be started during initial transmission of capability restriction related to bands or band combinations due to the transmission of temporary capability restriction information related to maxCC. Transmission of some other temporary capability restrictions like SCG to be released on serving cell to be released may not result in starting the prohibit timer. At block 605, the UE (101) initiates the UAI transmission when the prohibit timer is not running. At block 607, the UE (101) transmits the UAI after the prohibit timer expiry or along with other UAI transmission when the prohibit timer is running due to UAI for sending other temporary capability restriction information.

[0110] Fig. 7 is a flow diagram that illustrates the events of band restriction reporting for MUSIM operations according to the embodiments as disclosed herein. At block 701, the UE (101) determines whether it has a temporary capability restriction on the combination(s) of bands comprising band(s) included in the musim-CandidateBandList. Also, the UE (101) did not transmit a UEAssistanceInformation message with musim-AffectedBandsList and / or musim-AvoidedBandsList since it was configured to provide MUSIM assistance information for temporary capability restriction. At block 703, the UE (101) initiates UAI transmission and starts or restarts T346n.

[0111] Fig. 8 is a flow diagram that illustrates the scenario of UE handling the temporary capability restrictions at RRC Reestablishment according to the embodiments as disclosed herein. At block 801, the UE (101) determines whether it has temporary capability restrictions during the applicable RRC reestablishment and while sending the RRC reestablishment complete message to the network. At block 803, the UE (101) determines whether the MUSIM capability restriction (musim-Cap) is allowed in the SIB1. Further, at block 805, the UE (101) includes the musim-CapRestrictionInd in the RRCReestablishmentComplete when the MUSIM capability restriction (musim-Cap) is allowed in the SIB1 and when the UE (101) has temporary capability restrictions at the time of sending RRCReestablishmentComplete.

[0112] Fig. 9 is the flow diagram that shows the scenario of the UE handling the temporary capability restrictions at the RRC Reestablishment according to the embodiments as disclosed herein. At block 901, the UE (101) receives a configuration in the RRC reconfiguration indicating that the temporary capability restriction is not supported while the RRC reestablishment procedure is ongoing. At block 903, the UE (101) moves to the RRC-IDLE state upon receiving the configuration indicating that temporary capability restriction is not supported.

[0113] In an embodiment, the UE (101), which has temporary capability restriction at the time of initiating the RRC Reestablishment procedure (for example, at the time of sending the NR RRC ReestablishmentComplete message), sends a single bit of information to indicate that it has temporary capability restrictions. The UE (101) sends this information if it has received information from the network that early capability restriction indication is allowed during RRC Reestablishment. In NR, if the UE (101) has received musim-CapRestrictionAllowed in SIB1 and if the UE (101) has temporary capability restrictions at the time of sending RRCReestablishmentComplete, the UE includes the musim-CapRestrictionInd in the RRCReestablishmentComplete.

[0114] Reception of the RRCReestablishment by the UE (101): The UE (101) shall:

[0115]

[0116] In an embodiment in NR, musim-CapRestrictionAllowed indicates the UE (101) is allowed to send the musim-CapRestrictionInd in RRCSetupComplete, RRCResumeComplete, and RRCReestablishmentComplete messages. After receiving an indication from the UE (101) that there is MUSIM capability restriction in RRCReestablishmentComplete, the network node configures the UE (101) with a limited configuration that is used until the network sends RRCReconfiguration based on actual restricted UE capabilities received. The network node waits for the UAI from the UE (101) to configure additional configurations like carrier aggregation, dual connectivity, interfrequency measurements, conditional handover, or LTM and the like after receiving RRCReestablishmentComplete. After receiving the temporary capability restriction in UAI, the network configures the UE (101) with additional configurations like carrier aggregation, dual connectivity, interfrequency measurements, conditional handover, or LTM and the like.

[0117] In an embodiment, upon reception of musim-CapRestrictionInd in RRCReestablishmentComplete, it is up to network implementation to configure the UE (101) with a limited configuration that is used until the network sends RRCReconfiguration based on the actual restricted UE capabilities included in UEAssistanceInformation.

[0118] In an embodiment, upon reception of musim-CapRestrictionInd in RRCReestablishmentComplete, the network node configures the UE (101) with a limited configuration that is used until the network sends RRCReconfiguration based on actual restricted UE capabilities received, except when the RRCReconfiguration that resumes SRB2 / DRB is sent in parallel to sending the RRCReestablishment.

[0119] Fig. 10 is a flow diagram that illustrates an event of the UE handling temporary capability restrictions at RRC Reestablishment when the radio link failure has occurred according to the embodiments as disclosed herein. At block 905, the UE (101) determines whether the radio link failure or any other failure has occurred that can trigger the reestablishment when the UE (101) is having temporary capability restriction. At block 907, the UE (101) moves to the RRC-IDLE state when the radio link failure or any other failure has occurred.

[0120] When the UE (101) has radio link failure and there is temporary capability restriction for the UE (101), it moves to RRC_IDLE. In an embodiment, if the UE (101) has radio link failure or any other failure which triggers the RRC Reestablishment procedure and there is temporary capability restriction for the UE (101), the UE (101) moves to RRC_IDLE.

[0121] Fig. 11 is a flow diagram that illustrates events of network handling the temporary capability restrictions at RRC Reestablishment according to the embodiments as disclosed herein. At block 911, the network apparatus receives musim-CapRestrictionIndication in the RRC ReestablishmentComplete message. At block 913, the network apparatus provides only limited configuration in the RRC Reconfiguration to resume SRB2 / DRB to the UE (101). At block 915, the network apparatus receives temporary capability restrictions in UAI. At block 917, the network apparatus configures the UE (101) with configurations according to received temporary capability restrictions.

[0122] Upon reception of musim-CapRestrictionInd in RRC ReestablishmentComplete, it is up to network implementation to configure the UE (101) with a limited configuration that is used until the network sends RRC Reconfiguration based on the actual restricted UE capabilities included in UE Assistance Information, except when the RRC Reconfiguration that resumes SRB2 / DRB is sent in parallel to sending the RRC Reestablishment.

[0123] If the RRC Reconfiguration that resumes SRB2 / DRB is sent in parallel to sending the RRC Reestablishment and the RRC Reconfiguration contains configuration that is not supported by the temporary capability restrictions, the UE (101) fails the RRC Reconfiguration procedure. The UE (101) can further send another RRC Reestablishment. In an embodiment, in this scenario, the UE (101) moves to idle (RRC_IDLE). Further, UE (101) may send RRC SetupRequest to move to RRC_CONNECTED.

[0124] In an embodiment, if the UE (101) receives RRC Reconfiguration which contains a configuration that is not supported by the temporary capability restrictions while the RRC Reestablishment procedure is ongoing, the UE (101) moves to RRC_IDLE.

[0125] In an embodiment, the UE (101) which has temporary capability restriction at the time of RRC Reestablishment moves to RRC_IDLE state. If the UE (101) has indicated temporary capability restriction to the old gNB or if the UE (101) has temporary capability restriction due to other SIM action at the time of initiating RRC Reestablishment, the UE (101) moves to RRC_IDLE. UE may further send RRC SetupRequest to establish RRC connection.

[0126] In an embodiment, if the UE (101) has temporary capability restriction on the combination(s) of bands comprising of band(s) included in musim-CandidateBandList and the UE (101) did not transmit a UE Assistance Information message with musim-AffectedBandsList and / or musim-AvoidedBandsList since it was configured to provide MUSIM assistance information for temporary capability restriction and the timer T346n (or any timer with equivalent functionality) is running, the UE (101) prohibits itself from initiating the UAI. The UE (101) may further initiate the UAI upon expiry of the timer.

[0127] In an embodiment, if the UE (101) has temporary capability restriction on musim-MaxCC and the UE (101) did not transmit a UE Assistance Information message with musim-MaxCC since it was configured to provide MUSIM assistance information for temporary capability restriction and the timer T346n (or any timer with equivalent functionality) is running, the UE (101) prohibits itself from initiating the UAI. The UE (101) may further initiate the UAI upon expiry of the timer.

[0128] According to TS 38.331, this may be represented as:

[0129]

[0130]

[0131] In an embodiment, if the UE (101) has temporary capability restriction on the combination(s) of bands comprising of band(s) included in musim-CandidateBandList and the UE (101) did not transmit a UEAssistanceInformation message with musim-AffectedBandsList and / or musim-AvoidedBandsList since it was configured to provide MUSIM assistance information for temporary capability restriction and the timer T346n ( or any timer with equivalent functionality) is running, the UE (101) initiates UAI. If the timer T346n or an equivalent timer is running, the UE (101) restarts T346n (or the equivalent timer).

[0132] In an embodiment, if the UE (101) has temporary capability restriction on musim-MaxCC and the UE (101) did not transmit a UEAssistanceInformation message with musim-MaxCC since it was configured to provide MUSIM assistance information for temporary capability restriction, and the timer T346n (or any timer with equivalent functionality) is running, the UE (101) initiates UAI. If the timer T346n or an equivalent timer is running, the UE (101) restarts T346n (or the equivalent timer).

[0133]

[0134]

[0135] Fig. 12 is the flow diagram that illustrates the events of SN handling of WaitTimer in dual connectivity according to the embodiments as disclosed herein. At block 919, the UE (101) receives the temporary capability restriction from the MN. At block 921, the UE (101) applies the temporary capability restriction after the maximum value of the wait timer.

[0136] In an embodiment in dual connectivity, upon expiry of the maximum possible value of musim-WaitTimer (100 ms in NR R18), SN understands that UE (101) will autonomously apply temporary capability restrictions. The SN also applies the temporary capability restrictions reported by the UE (101), i.e., SN releases any SCG in as musim-Cell-SCG-ToRelease upon expiry of the maximum possible value of musim-WaitTimer. SN also applies the restricted configurations from musim-CellToAffectList or the restricted configurations based on musim-MaxCC upon expiry of the maximum possible value of musim-WaitTimer. In an embodiment, SN receives musim-WaitTimer from MN and applies the restricted configurations based on musim-MaxCC upon expiry of this musim-WaitTimer.

[0137] Embodiments disclosed herein provide a system and method for handling gaps and interruptions in NR. A UE indicates to the network whether the UE supports reporting of the NCSG and measurement gap requirement information for E-UTRA target bands in UAI. In an embodiment, the UE sends the indication when the UE supports eutra-NeedForGapNCSG-Reporting-r17. In an embodiment, the indication may be sent in the capability musim-CapabilityRestriction-r18. When the UE supports a capability such as eutra-NeedForGapNCSG-Reporting-r17, UE sends musim-CapabilityRestriction-r18 to indicate whether UE supports reporting of the NCSG and measurement gap requirement information for E-UTRA target bands in UAI for MUSIM. In an embodiment, a MUSIM UE having temporary capability restrictions indicates that idle / inactive measurements are available only if at least one frequency for which idle / inactive measurements need to be reported is supported by the UE according to the current temporary capability restrictions.

[0138] Measurement Gaps: In wireless technologies like NR and LTE, a RRC connected UE performs various measurements for RRM purpose, positioning etc. For RRM, UE measures the reference signals such as SSB, CSI-RS etc. and reports the measurement results to the network.

[0139] According to the NR specification TS 38.300, measurements to be performed by a UE for connected mode mobility are classified in at least four measurement types: Intra-frequency NR measurements, Inter-frequency NR measurements, Inter-RAT measurements for E-UTRA, and Inter-RAT measurements for UTRA.

[0140] For each measurement type, one or several measurement objects can be defined (a measurement object defines, e.g., the carrier frequency to be monitored). For each measurement object, one or several reporting configurations can be defined (a reporting configuration defines the reporting criteria). Three reporting criteria are used: event-triggered reporting, periodic reporting, and event-triggered periodic reporting. The association between a measurement object and a reporting configuration is created by a measurement identity (a measurement identity links together one measurement object and one reporting configuration of the same RAT). The measurement identity is used as well when reporting results of the measurements.

[0141] For positioning, UE may report SSB / CSI-RS measurements and may also report measurements based on additional reference signals like PRS.

[0142] When the UE needs to measure inter-frequency NR or inter-RAT measurements or intra-frequency measurements outside the active downlink BWP when SSB is not completely contained in the active DL BWP, UE may use measurement gaps. Measurement gaps are configured by the network (e.g., gNB in NR), and there will not be any transmission or reception during the gap period. Measurement gap configuration includes a gap offset, gap length, repetition period, and measurement gap timing advance. Gap offset specifies the sub-frame where the start of the measurement gap occurs. Gap length gives the duration of the gap, while the repetition period defines how often the measurement gap can occur.

[0143] NeedForGaps: An NR UE reports NeedForGaps to indicate whether the UE needs gaps for measuring specific NR bands. In Release 17, NeedForGaps has been extended so that the UE can report whether it needs gaps or network-controlled small gaps (NCSG) for measuring specific NR bands. Starting from 3GPP Release 17, the UE can also indicate whether it needs gaps or NCSG for measuring E-UTRA bands.

[0144] The Network configures UE to provide the measurement gap requirement information of NR target bands by setting needForGapsConfigNR to setup in RRC Reconfiguration or RRC Resume. In Release 17, the Network configures UE to provide the measurement gap and NCSG requirement information of E-UTRA target bands by setting needForNCSG-ConfigEUTRA to setup in RRC Reconfiguration or RRC Resume. Similarly, in R17, the Network configures UE to provide the measurement gap and NCSG requirement information of NR target bands by setting needForNCSG-ConfigNR to setup in RRC Reconfiguration or RRC Resume.

[0145] Once configured, UE keeps the configuration until released or modified and informs the network of the gap requirements for NR bands or gap and NCSG requirements for NR and E-UTRA bands. UE includes gap (or gap and NCSG) requirements in RRC Resume Complete and RRC Reconfiguration Complete. If the gap or gap and NCSG requirements change after a reconfiguration, UE reports the changed requirements in RRC Reconfiguration Complete.

[0146] Network may also configure UE with a band filter. If the band filter is configured, UE reports gap requirements or gap and NCSG requirements for NR and E-UTRA bands that are included in the band filter. If the band filter is not configured, UE reports the gap requirements or gap and NCSG requirements for all the bands supported by the UE.

[0147] An extract from Release 18 RRC specification on NeedForgaps or NeedforNCSG reporting during RRC Reconfiguration is given below:

[0148] 2> if the RRCReconfiguration message was received via SRB1, but not within mrdc-SecondaryCellGroup or E-UTRA RRCConnectionReconfiguration or E-UTRA RRCConnectionResume:

[0149] 3> if the UE is configured to provide the measurement gap requirement information of NR target bands:

[0150] 4> if the RRCReconfiguration message includes the needForGapsConfigNR; or

[0151] 4> if the NeedForGapsInfoNR information is changed compared to last time the UE reported this information; or

[0152] 4> if the RRCReconfiguration message includes the needForInterruptionConfigNR and set it to enabled; or

[0153] 4> if the needForInterruptionConfigNR is enabled and the NeedForInterruptionInfoNR information is changed compared to last time the UE reported this information:

[0154] 5> include the NeedForGapsInfoNR and set the contents as follows:

[0155] 6> include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell;

[0156] 6> if requestedTargetBandFilterNR is configured:

[0157] 7> for each supported NR band that is also included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band;

[0158] 6> else:

[0159] 7> include an entry in interFreq-needForGap and set the corresponding gap requirement information for each supported NR band;

[0160] 5> if the needForInterruptionConfigNR is enabled:

[0161] 6> include the needForInterruptionInfoNR and set the contents as follows:

[0162] 7> include intraFreq-needForInterruption with the same number of entries, and listed in the same order, as in intraFreq-needForGap;

[0163] 7> for each entry in intraFreq-needForInterruption:

[0164] 8> include interruptionIndication and set the interruption requirement information if the corresponding entry in intraFreq-needForGap is set to no-gap;

[0165] 7> include interFreq-needForInterruption with the same number of entries, and listed in the same order, as in interFreq-needForGap;

[0166] 7> for each entry in interFreq-needForInterruption:

[0167] 8> include interruptionIndication and set the interruption requirement information if the corresponding entry in interFreq-needForGap is set to no-gap;

[0168] 3> if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands:

[0169] 4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR; or

[0170] 4> if the needForGapNCSG-InfoNR information is changed compared to last time the UE reported this information:

[0171] 5> include the NeedForGapNCSG-InfoNR and set the contents as follows:

[0172] 6> include intraFreq-needForNCSG and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell;

[0173] 6> if requestedTargetBandFilterNCSG-NR is configured:

[0174] 7> for each supported NR band included in requestedTargetBandFilterNCSG-NR, include an entry in interFreq-needForNCSG and set the NCSG requirement information for that band;

[0175] 6> else:

[0176] 7> include an entry for each supported NR band in interFreq-needForNCSG and set the corresponding NCSG requirement information;

[0177] 3> if the UE is configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands:

[0178] 4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA; or

[0179] 4> if the needForGapNCSG-InfoEUTRA information is changed compared to last time the UE reported this information:

[0180] 5> include the NeedForGapNCSG-InfoEUTRA and set the contents as follows:

[0181] 6> if requestedTargetBandFilterNCSG-EUTRA is configured, for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA, include an entry in needForNCSG-EUTRA and set the NCSG requirement information for that band; otherwise, include an entry for each supported E-UTRA band in needForNCSG-EUTRA and set the corresponding NCSG requirement information;

[0182] Similarly, an extract from Release 17 RRC specification on musim-NeedForGaps reporting in UAI is given below:

[0183] 5.7.4.2 Initiation

[0184]

[0185]

[0186]

[0187] 5.7.4.3 Actions related to transmission of UEAssistanceInformation message

[0188]

[0189]

[0190]

[0191]

[0192] v18.1.0 of the 3GPP specifications such as TS 38.331, TS 38.300, TS 38.306, TS 38.321 are considered as the relevant background for the present disclosure.

[0193] Fig. 13 is a flow diagram that illustrates handling gap-related requirements after reporting MUSIM NeedForGaps according to the embodiments as disclosed herein. At block 931, the method includes reporting the MUSIM-NeedForGaps in UAI. At block 933, the method includes receiving the RRCReconfiguration message. At block 935, the method includes including the gaps NCSG and interruption requirements in the RRCReconfigurationComplete message.

[0194] In an embodiment, UE indicates to the network whether the UE supports reporting of the NCSG and measurement gap requirement information for E-UTRA target bands in UAI (as specified in TS 38.331). In an embodiment, UE sends this indication if it supports eutra-NeedForGapNCSG-Reporting-r17. In an embodiment, this indication may be send in the capability musim-CapabilityRestriction-r18. If the UE supports a capability such as eutra-NeedForGapNCSG-Reporting-r17, UE sends musim-CapabilityRestriction-r18 to indicate whether UE supporting reporting of the NCSG and measurement gap requirement information for E-UTRA target bands in UAI for MUSIM. In an embodiment, UE includes eutra-NeedForGapNCSG in the UAI if it supports both the capabilities musim-CapabilityRestriction-r18 and eutra-NeedForGapNCSG-Reporting-r17. Otherwise, UE doesn't include the capabilities. In an embodiment, according to TS 38.331.

[0195]

[0196] In an embodiment, a MUSIM UE having temporary capability restrictions indicates to the network that idle / inactive measurements are available only if at least one frequency for which idle / inactive measurements need to be reported is supported by the UE according to the current temporary capability restrictions (e.g., for MUSIM operations). In NR, this applies to RRCSetupComplete, RRCResumeComplete, RRCReconfigurationComplete, and other RRC messages where this indication is sent.

[0197] In an embodiment, a MUSIM UE having temporary capability restrictions sends the idle / inactive measurements to the network only if at least one frequency for which idle / inactive measurements need to be reported is supported by the UE according to the current temporary capability restrictions. In NR, this applies to RRCResumeComplete, UEInformationResponse, and other RRC messages where this information is sent.

[0198] In an embodiment, a MUSIM UE having temporary capability restrictions indicates that cell reselection measurements are available to the network only if at least one frequency for which cell reselection measurements need to be reported is supported by the UE according to the current temporary capability restrictions. In NR, this applies to RRCSetupComplete, RRCResumeComplete, RRCReconfigurationComplete, and other RRC messages where this indication is sent.

[0199] In an embodiment, a MUSIM UE having temporary capability restrictions sends the cell reselection measurements to the network only if at least one frequency for which cell reselection measurements need to be reported is supported by the UE according to the current temporary capability restrictions. In NR, this applies to RRCResumeComplete, UEInformationResponse, and other RRC messages where this information is sent.

[0200] In an embodiment, if a UE has last reported measurement gap requirements in UAI (such as musim-NeedForGapsInfoNR) and if the UE is configured for reporting interruption requirements, it sends measurement gap requirements and interruption requirements in the ReconfigurationComplete message. This may be sent irrespective of the absence of any change in interruption requirements or measurement gap requirements.

[0201] In an embodiment, if a UE has last reported measurement gap requirements in UAI (such as musim-NeedForGapsInfoNR) and if the UE is configured for reporting the measurement gap and NCSG requirement information, it sends measurement gap requirements and NCSG requirement information in the ReconfigurationComplete message. This may be sent irrespective of the absence of any change in measurement gap and NCSG requirements.

[0202] In an embodiment, according to TS 38.331:

[0203]

[0204]

[0205]

[0206] In an embodiment, a NR UE sends NeedForGapsInfoNR if the RRCReconfiguration message includes configuration for need for interruptions and the UE needs gaps for performing measurements on at least one serving cell or at least one band which needs to be reported (according to requestedTargetBandFilterNR when requestedTargetBandFilterNR is configured or all the supported NR bands when requestedTargetBandFilterNR is not configured).

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

[0208]

[0209]

[0210]

[0211]

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

[0213]

[0214]

[0215]

[0216] In an embodiment, the source gNB sends the last received measurement gaps and NCSG requirements considering RRCReconfigurationComplete,RRCResumeComplete and UAI (for MUSIM operation).

[0217] In an embodiment, the source gNB sends the last received interruption requirements considering RRCReconfigurationComplete, RRCResumeComplete and UAI (for MUSIM operation).

[0218] Fig. 14 is a flow diagram that illustrates handling HandoverPreparationInformation for MUSIM NCSG and interruption requirements according to the embodiments as disclosed herein. At block 937, the method includes receiving gaps, NCSG, and interruption requirements in UAI and a complete message (Reconfiguration Complete or Resume Complete message). At block 939, the method includes including the last received gaps, NCSG, and interruption requirements in HandoverPreparationInformation.

[0219] HandoverPreparationInformation: This message is used to transfer the NR RRC information used by the target gNB during handover preparation or UE context retrieval, e.g. in case of resume or re-establishment, including UE capability information. This message is also used for transferring the information between the CU and DU.

[0220] Direction: source gNB / source RAN to target gNB or CU to DU.

[0221]

[0222]

[0223]

[0224]

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

Claims

1.A method performed by a terminal in a communication network system, the method comprising:determining whether the terminal is configured to provide multi-universal subscriber identity module (MUSIM) assistance information for temporary capability restriction;determining whether the terminal has temporary capability restriction on a current configuration and a wait timer is not running, based on the determination whether the terminal is configured to provide the MUSIM assistance information for temporary capability restriction;initiating a transmission of first user equipment (UE) assistance information, to a network apparatus, and starting the wait timer, in case that the terminal has the temporary capability restriction on the current configuration and the wait timer is not running; andreleasing a secondary cell group (SCG), in case that an index of a primary secondary cell (PSCell) to be released is included in the first UE assistance information, based on the expiry of the wait timer.2.The method of claim 1, wherein the first UE assistance information is transmitted to provide at least one of information indicating a temporary capability restriction on at least one serving cell, or information indicating a serving cell list to be released.3.The method of claim 1, further comprising:determining whether at least one condition is satisfied and a prohibit timer is running; andinitiating a transmission of second UE assistance information, to a network apparatus, and starting the prohibit timer, in case that the at least one condition is satisfied and the prohibit timer is not running.4.The method of claim 3, wherein the at least one condition is satisfied in case that:the terminal has temporary capability restriction on at least one band, andthe terminal did not transmit the second UE assistance information with the temporary capability restriction on the at least one band, since the terminal is configured to provide the MUSIM assistance information for temporary capability restriction.5.The method of claim 3, wherein the at least one condition is satisfied in case that:the terminal has temporary capability restriction on a maximum component carrier (CC) number, andthe terminal did not transmit the second UE assistance information with the maximum CC number, since the terminal is configured to provide the MUSIM assistance information for temporary capability restriction.6.The method of claim 4, wherein the temporary capability restriction on the at least one band comprise at least one of:an affected band list indicating at least one band with restricted capability for MUSIM operation; oran avoided band list indicating at least one band to be avoided for MUSIM operation.7.A terminal in a communication network system, the terminal comprising:a transceiver;memory storing at least one of computer programs; andat least one processor communicatively coupled to the transceiver and the memory,wherein the at least one of programs include computer-executable instructions that, when executed by the at least one processor individually or collectively, cause the terminal to:determine whether the terminal is configured to provide multi-universal subscriber identity module (MUSIM) assistance information for temporary capability restriction;determine whether the terminal has temporary capability restriction on a current configuration and a wait timer is not running, based on the determination whether the terminal is configured to provide the MUSIM assistance information for temporary capability restriction;initiate a transmission of first user equipment (UE) assistance information, to a network apparatus, and start the wait timer, in case that the terminal has the temporary capability restriction on the current configuration and the wait timer is not running; andrelease a secondary cell group (SCG), in case that an index of a primary secondary cell (PSCell) to be released is included in the first UE assistance information, based on the expiry of the wait timer.8.The terminal of claim 7, wherein the first UE assistance information is transmitted to provide at least one of information indicating a temporary capability restriction on at least one serving cell, or information indicating a serving cell list to be released.9.The terminal of claim 7, the at least one of programs further include computer-executable instructions that, when executed by the at least one processor individually or collectively, cause the terminal to:determine whether at least one condition is satisfied and a prohibit timer is running; andinitiate a transmission of second UE assistance information, to a network apparatus, and start the prohibit timer, in case that the at least one condition is satisfied and the prohibit timer is not running.10.The terminal of claim 9, wherein the at least one condition is satisfied in case that:the terminal has temporary capability restriction on at least one band, andthe terminal did not transmit the second UE assistance information with the temporary capability restriction on the at least one band, since the terminal is configured to provide the MUSIM assistance information for temporary capability restriction.11.The terminal of claim 9, wherein the at least one condition is satisfied in case that:the terminal has temporary capability restriction on a maximum component carrier (CC) number, andthe terminal did not transmit the second UE assistance information with the maximum CC number, since the terminal is configured to provide the MUSIM assistance information for temporary capability restriction.12.The terminal of claim 10, wherein the temporary capability restriction on the at least one band comprise at least one of:an affected band list indicating at least one band with restricted capability for MUSIM operation; oran avoided band list indicating at least one band to be avoided for MUSIM operation.

Images