Methods and apparatus for handling temporary capability restriction and removal in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein provide a method and a system for handling temporary capability restriction and removal in a 5G network. The method includes transmitting an informing message to a network apparatus (202). The informing message indicates that a user equipment (UE) (102) has a temporary capability restriction. Further, receiving a configuration for reporting the temporary capability restrictions. Further, determining that the UE (102) does not has the temporary capability restriction as configured by the network apparatus (202). Further, generating a UE assistance information (UAI) message to be transmitted to the network apparatus (202) in response to determining that the UE (102) does not has temporary capability restriction. In addition, transmitting the UAI message to the network apparatus (202). The UAI message is transmitted with an empty capability restriction that indicates a removal of the temporary capability restriction.

Description

METHODS AND APPARATUS FOR HANDLING TEMPORARY CAPABILITY RESTRICTION AND REMOVAL IN A WIRELESS COMMUNICATION SYSTEM

[0001] This application is based on and derives the benefit of Indian Provisional Applications 202341061581 filed on 13th September 2023 and 202341071870 filed on 20th October 2023, the contents of which are incorporated herein by reference. The present disclosure is related to wireless communication. More particularly, the present disclosure is related to a method and system for handling temporary capability restriction and removal of a user equipment (UE) in a 5G network.

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

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

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

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

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

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

[0008] The present disclosure relates to wireless communication systems and, more specifically, the present disclosure relates to handle handling temporary capability restriction and removal associated with the UE in a 5G network in a wireless communication.

[0009] The principal object of the embodiments herein is to handle handling temporary capability restriction and removal associated with the UE in a 5G network.

[0010] Yet another object of the embodiments herein is to report UE assistance information (UAI) when temporary capability restrictions are indicated in at least one of a RRC setup complete message, a RRC resume complete message, and a RRC reestablishment complete message, but not restrictions are available at the time of reporting.

[0011] Yet another object of the embodiments herein is to handle wait timer associated with the UE during a handover, conditional handover, and lower-layer triggered motility (LTM) cell switch procedure.

[0012] Yet another object of the embodiments herein is to start or restart MUSIM wait timers associated with the UE based on a timer period within which a reconfiguration with sync message is received by the UE.

[0013] Yet another object of the embodiments herein is to report capability restrictions between a master node (MN) and a secondary node (SN) when the temporary capability restrictions of the UE have been reported based on a filter configured by the MN.

[0014] In one aspect, the objectives are achieved by providing a method for handling temporary capability restriction and removal in a 5G network. The method includes transmitting an informing message to a network apparatus. The informing message indicates that the UE has a temporary capability restriction. Further, the method includes receiving a configuration for reporting the temporary capability restrictions. Further, the method includes determining that the UE does not has the temporary capability restriction as configured by the network apparatus. Further, the method includes generating a UE assistance information (UAI) message to be transmitted to the network apparatus in response to determining that the UE does not has temporary capability restriction. In addition, the method includes transmitting the UAI message to the network apparatus. The UAI message is transmitted with an empty capability restriction that indicates a removal of the temporary capability restriction.

[0015] In an embodiment, the temporary capability restriction is a multi-SIM (MUSIM) capability restriction.

[0016] In an embodiment, the informing message is included in at least one of a RRC setup complete message, a RRC resume complete message, and a RRC reestablishment complete message.

[0017] In one aspect, the objectives are achieved by providing a method for handling temporary capability restriction and removal in a 5G network. The method includes receiving a reconfiguration with sync message from a network apparatus. Further, the method includes determining whether the UE has initiated a transmission of a UE assistance information (UAI) message requesting for a temporary capability restriction before receiving the reconfiguration with sync message within a fixed time. In addition, the method includes starting a multi-SIM (MUSIM) wait timer associated with the UE or restarting the MUSIM wait timer associated with the UE. A timer value of the MUSIM wait timer is set to a value present in a MUSIM capability restriction configuration when the MUSIM wait timer is started or restarted.

[0018] In an embodiment, the fixed time is 1 second.

[0019] In an embodiment, the method includes receiving a radio resource control (RRC) reconfiguration message from the network apparatus. Further, the method includes determining whether the RRC reconfiguration message is applied due to at least one of a conditional reconfiguration execution and a lower-layer triggered motility (LTM) cell switch procedure, and whether the UE has initiated the transmission of the UAI message requesting for the temporary capability restriction. In addition, the method includes starting the MUSIM wait timer associated with the UE or restarting the MUSIM wait timer associated with the UE. The timer value of the MUSIM wait timer is set to the value present in a MUSIM capability restriction configuration.

[0020] In an embodiment, the method includes retransmitting the UAI message to the network apparatus to request for the temporary capability restriction.

[0021] In one aspect, the objectives are achieved by providing a method for handling temporary capability restriction and removal in a 5G network. The method includes configuring at least one configuration for a user equipment (UE) to report temporary capability restrictions. The configuration comprises at least one filter. Further, the method includes generating a capability restriction message to be transmitted to a second network apparatus. The capability restriction message includes at least one of the temporary capability restrictions reported by the UE and the at least one filter configured. In addition, the method includes transmitting the capability restriction message to the second network apparatus.

[0022] In an embodiment, the at least one filter includes a band filter, a band combination filter, and a frequency filter.

[0023] In an embodiment, the temporary capability restrictions include a preference of the UE on secondary cells (SCells) to be released, serving cells of the UE having a restricted capability, at least one band of the UE having a restricted capability, and at least one band of the UE to be avoided for temporary capabilities restriction purposes.

[0024] In an embodiment, the network apparatus is a master node (MN) and the second network apparatus is a secondary node (SN), and wherein the network apparatus and the second network apparatus are in communication using a new radio dual connectivity (NR-DC).

[0025] In one aspect, the objectives are achieved by providing a user equipment (UE) for handling temporary capability restriction and removal in a 5G network. The UE includes a memory, a processor coupled to the memory, and a first controller communicatively coupled to the processor and the memory. The first controller transmits an informing message to a network apparatus. The informing message indicates that the UE has a temporary capability restriction. Further, the first controller receives a configuration for reporting the temporary capability restrictions. Further, the first controller determines that the UE does not have the temporary capability restriction to be reported based on the configuration from the network apparatus. Further, the first controller generates a UE assistance information (UAI) message to be transmitted to the network apparatus. The UAI message is transmitted with an empty capability restriction that indicates a removal of the temporary capability restriction. In addition, the first controller transmits the UAI message to the network apparatus. The UAI message is transmitted with an empty capability restriction that indicates a removal of the temporary capability restriction.

[0026] In an embodiment, the temporary capability restriction is a multi-SIM (MUSIM) capability restriction.

[0027] In an embodiment, the informing message is included in at least one of a RRC setup complete message, a RRC resume complete message, and a RRC reestablishment complete message.

[0028] In an embodiment, the first controller receives a reconfiguration with sync message from a network apparatus. Further, the first controller determines whether the UE has initiated a transmission of a UE assistance information (UAI) message requesting for a temporary capability restriction before receiving the reconfiguration with sync message within a fixed time. In addition, the first controller starts a multi-SIM (MUSIM) wait timer associated with the UE or restarts the MUSIM wait timer associated with the UE. A timer value of the MUSIM wait timer is set to a value present in a MUSIM capability restriction configuration when the MUSIM wait timer is started or restarted.

[0029] In an embodiment, the fixed time is 1 second.

[0030] In an embodiment, the first controller receives a radio resource control (RRC) reconfiguration message from a network apparatus. Further, the first controller determines whether the RRC reconfiguration message is applied due to at least one of a conditional reconfiguration execution and a lower-layer triggered motility (LTM) cell switch procedure, and whether the UE has initiated the transmission of the UAI message requesting for the temporary capability restriction. In addition, the first controller starts the MUSIM wait timer associated with the UE or restarts the MUSIM wait timer associated with the UE. The timer value of the MUSIM wait timer is set to the value present in a MUSIM capability restriction configuration.

[0031] In an embodiment, the first controller retransmits the UAI message to the network apparatus to request for the temporary capability restriction.

[0032] In one aspect, the objectives are achieved by providing a network apparatus for handling temporary capability restriction and removal in a 5G network. The network apparatus includes a memory, a processor coupled to the memory, and a second controller communicatively coupled to the processor and the memory. The second controller configures at least one configuration for a user equipment (UE) to report the temporary capability restrictions. The configuration comprises at least one filter. Further, the second controller generates a capability restriction message to be transmitted to a second network apparatus. The capability restriction message includes at least one of the temporary capability restrictions reported by the UE and the at least one filter configured. In addition, the second controller transmits the capability restriction message to the second network apparatus.

[0033] In an embodiment, the at least one filter includes a band filter, a band combination filter, and a frequency filter.

[0034] In an embodiment, the temporary capability restrictions include a preference of the UE on secondary cells (SCells) to be released, serving cells of the UE having a restricted capability, at least one band of the UE having a restricted capability, and at least one band of the UE to be avoided for temporary capabilities restriction purposes.

[0035] In an embodiment, the network apparatus is a master node (MN) and the second network apparatus is a secondary node (SN), and wherein the network apparatus and the second network apparatus are in communication using a new radio dual connectivity (NR-DC).

[0036] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications be made within the scope of the embodiments herein.

[0037] According to an embodiment of the disclosure, a wireless communication can be performed efficiently. Especially, a handle handling temporary capability restriction and removal associated with the UE can be performed efficiently.

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

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

[0040] Fig. 2 is a block diagram that illustrates a schematic of a network apparatus implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein.

[0041] Fig. 3 is a flow diagram that illustrates a method for removing temporary capability restrictions in the UE during a RRC setup complete procedure according to an embodiment as disclosed herein.

[0042] Fig. 4 is a flow diagram that illustrates a method for handling temporary capability restrictions using a filter during the RRC setup complete procedure according to an embodiment as disclosed herein.

[0043] Fig. 5 is a flow diagram that illustrates a method for removing temporary capability restrictions in the UE during a RRC resume procedure according to an embodiment as disclosed herein.

[0044] Fig. 6 is a flow diagram that illustrates a method for handling temporary capability restrictions using a filter during the RRC resume complete procedure according to an embodiment as disclosed herein.

[0045] Fig. 7 is a flow diagram that illustrates a method for starting or restarting of the MUSIM wait timer associated with the UE according to an embodiment as disclosed herein.

[0046] Fig. 8 is a flow diagram that illustrates a method for interacting between the MUSIM wait timers based on a reconfiguration with sync according to an embodiment as disclosed herein.

[0047] Fig. 9 is a flow diagram that illustrates a method for interacting between the MUSIM wait timers during a LTM cell switch procedure according to an embodiment as disclosed herein.

[0048] Fig. 10 is a flow diagram that illustrates a method for interacting between the MUSIM wait timers during a conditional reconfiguration execution according to an embodiment as disclosed herein.

[0049] Fig. 11 is a flow diagram that illustrates a method for requesting for temporary capability restriction according to an embodiment as disclosed herein.

[0050] Fig. 12 is a flow diagram that illustrates a method for temporary capability restriction or the removal of temporary capability restrictions during MN-SN interactions according to an embodiment as disclosed herein.

[0051] Fig. 13 is a flow diagram that illustrates a method for handling temporary capability restriction and removal in a 5G network according to an embodiment as disclosed herein.

[0052] Fig. 14 is a flow diagram that illustrates a method for temporary capability restriction and removal in a 5G network by managing a MUSIM wait timer based on a reconfiguration with sync message according to an embodiment as disclosed herein.

[0053] Fig. 15 is a flow diagram that illustrates a method for managing the MUSIM wait timer based on a RRC reconfiguration message.

[0054] Fig. 16 is a flow diagram that illustrates a method for temporary capability restriction and removal in a 5G network based on a configured filter according to an embodiment as disclosed herein.

[0055] It may be noted that to the extent possible, like reference numerals have been used to represent like elements in the drawing. Further, those of ordinary skill in the art will appreciate that elements in the drawing are illustrated for simplicity and may not have been necessarily drawn to scale. For example, the dimension of some of the elements in the drawing may be exaggerated relative to other elements to help to improve the understanding of aspects of the invention. Furthermore, the elements may have been represented in the drawing by conventional symbols, and the drawings may show only those specific details that are pertinent to the understanding the embodiments of the invention so as not to obscure the drawing with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

[0056] Temporary capability restrictions are short-term limits put on the UE's access to or performance on the 5G network. These limitations may be impacted by the network operator, the UE, or other external factors. For example, the temporary capability restrictions may include restrictions due to the operations of multi-SIM (MUSIM) devices, network congestion, device based restrictions, policy based restrictions, location based restrictions, network outages, and the like. The temporary capability restrictions are resolved once the conditions or restrictions causing them are improved or alleviated.

[0057] Further, due to the popularity of multi-SIM (MUSIM) devices that host more than one subscriber identity module (SIM), users can connect to different networks to access different data plans, have user profiles such as home and office, and have increased connectivity / reliability with multiple connections, among other things. To reduce costs, the UE's RF circuitry is shared by numerous SIMs. That is, many SIMs must arbitrate and share a shared RF resource in order to accomplish their operations and / or utilize services. Effectively, only one SIM and its protocol stack may be serviced. Meanwhile, all other SIMs and protocol stacks will be waiting for the RF resource to become accessible to them. One or more of the multiple SIMs may be engaged in paging reception, system information block (SIB) acquisition, measurement, data or voice call, multimedia broadcast multicast service (MBMS), emergency call, access stratum (AS) signaling, non-access stratum (NAS) signaling, and the like.

[0058] MUSIM UEs operated without network management, resulting in random gaps, until 3gpp chose to include support for MUSIM device operations in Release 17. From Release 17, a connected USIM (USIM in the context of this invention refers to the radio protocol stack associated with the UE) in a MUSIM device can inform the connected mode network of network switching for multi-SIM operations. There are two types of network switching supported―In one form, the connected USIM leaves the linked network and entirely switches to the other USIM, resulting in the other USIM being connected. In other cases, a connected USIM requests a network gap for MUSIM activities such as paging or measuring in an idle USIM.

[0059] In release　17, MUSIM UE employs the RRC UE Assistance Information (UAI) method to seek gaps or inform of departure. The Network (gNB) determines whether the UE can give support information for MUSIM gaps or MUSIM Leave via otherConfig in RRC messages. Musim-GapAssistanceConfig in otherConfig is used to notify the UE if it can give MUSIM help information for gap information. For MUSIM operations, version 17 only supports per-UE gaps.

[0060] Traditionally, a UE informs the network about the removal of a restriction after it has informed the network of the restriction. Especially in the design of UE Assistance Information, removal of an assistance information such as a preference information is not informed to the network, if the UE has not informed about the assistance information.

[0061] In 3gpp release 18, MUSIM UE may support multiple USIMs in RRC_CONNECTED state. MUSIM UE may send an early indication while connecting to the network such as through RRC Setup or RRC resume and the network may configure the UE to report the temporary capability restrictions in RRC messages such as UE Assistance Information (UAI).

[0062] After sending the early indication during the RRC setup / resume procedure to signal temporary capability limits, the UE may not transmit the UAI message containing MUSIM capability restriction information after switching to the RRC connected state. For example, the UE provides an early notification to NW A that it has temporary capability restrictions since some bands cannot be supported owing to NW B's RRC connection. NW A transmitted the RRC configuration for reporting temporary capability restrictions to the UE. It may occur that the setup is compliant with the UE's capability or temporary capability limitation at the moment, and no bands from the NW's candidate band list are restricted. Depending on the MUSIM band list filter, this scenario may occur frequently since detailed MUSIM temporary capability constraints may be on bands that are of little concern to the network operator.

[0063] Furthermore, it is probable that the UE shifted to RRC_IDLE in NW B between sending the early signal and receiving the RRCReconfiguration, including OtherConfig, allowing the UE to communicate temporary capability limits. In the above example, if the UE switches to the RRC_IDLE state in NW B while maintaining the RRC connection with NW A, the early indication owing to the temporary capability limitation in NW A is no longer valid.

[0064] A MUSIM UE may send the temporary capability restrictions in Radio Resource Control (RRC) messages such as UE Assistance Information (UAI). Various events such as handovers, conditional mobility,Lower Layer Triggered Mobility (LTM) may occur after the temporary capability restrictions are reported. It needs to be defined how these events affect the MUSIM operations.

[0065] In dual connectivity, the reported temporary capability restrictions may be applicable for both master node (MN) and secondary node (SN). It needs to be defined how the restrictions can be communicated between them and how the SN understands the restrictions from the UE.

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

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

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

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

[0070] The various actions, acts, blocks, steps, or the like in the method is performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like are omitted, added, modified, skipped, or the like without departing from the scope of the proposed method.

[0071] Let us consider the case of a MUSIM device, where one USIM is attached to Network A (NW A) and other USIM is attached to Network B (NW B). In the prior art, after sending the early indication during the RRC setup / resume procedure to indicate temporary capability restrictions, the UE would not transmit the UAI message containing MUSIM capability restriction information after transitioning to the RRC connected state. For example, the UE notifies NW A that it has temporary capability restriction since some bands cannot be supported due to NW B's RRC connection. NW A sent the RRC configuration for reporting the temporary capability restriction to the UE. It is possible that the configuration is in accordance with the UE's capability or temporary capability at the moment, and no bands from the NW's candidate band list are restricted. Depending on the MUSIM band list filter, this scenario may occur frequently since detailed MUSIM temporary capability limits may be on bands of minimal interest to the network operator.

[0072] Also, it is likely that the UE switched to RRC_IDLE in NW B between transmitting the indication of capability restriction and receiving the configuration, such as RRCReconfiguration, which included OtherConfig, allowing it to communicate temporary capability restrictions. In the above example, if the UE enters the RRC_IDLE state in NW B while retaining an RRC connection with NW A, the early indication due to the temporary capacity restriction in NW A is no longer valid.

[0073] The proposed solution discloses a method and system for handling temporary capability restriction and removal. The proposed solution includes　a UE RRC that starts or restarts musim-WaitTimer upon successful transmission of an RRC message reporting a temporary capability restrictions, as successfully send by the lower layers. When the RRC in the UE sends an RRC message, such as UAI, to report temporary capability restrictions, the UE forwards the message to the lower layers. The lowest layers send the message using the resources allocated by the network. The lower levels must notify the network that they require resources via mechanisms such as scheduling requests or buffer status reports before the network provides the resources. Further, the message transmission may fail during first attempts, prompting the lower levels to retransmit the message. When the transmission is successful, the RRC message is regarded successfully delivered. Lower layers　may provide information to the RRC.

[0074] Since the UE restricts its capabilities in accordance with the temporary capability restrictions communicated to the network, when the musim-WaitTimer expires, it is critical that the timer be started or resumed simultaneously in both the UE and the network. The proposed solution includes starting or restarting the musim-WaitTimer upon successful delivery of a UAI requesting a temporary capability restriction, which is confirmed by the lower layers. This ensures that both the UE and network have similar timer values, resulting in both the UE and network side timers running until completion simultaneously.

[0075] UE Capabilities:

[0076] 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 signalling 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. If supported by the UE and the network, the UE may provide an ID in NAS signalling that represents its radio capabilities for one or more RATs in order to reduce signalling overhead. The ID may be assigned either by the manufacturer or by the serving PLMN. The manufacturer-assigned ID corresponds to a pre-provisioned set of capabilities. In the case of the PLMN-assigned ID, assignment takes place in NAS signaling. Detailed list of UE capabilities that are exchanged based on aforementioned methods is specified in 3GPP technical specifications like TS 38.306.

[0077] 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.

[0078] RRC States:

[0079] In NR, RRC can be in one of the three states- RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED. A RRC_CONNECTED UE is in CM-CONNECTED (i.e. Connected to 5G Core network) and can do unicast and multicast / broadcast traffic with the network. In the NR control plane protocol stack, lower layers for RRC include PDCP,RLC,MAC and physical layer. Network stores the UE AS context, knows the UE at cell level and controls the UE mobility. UE may perform measurements and report to the network, provides channel quality and feedback information etc.

[0080] RRC_INACTIVE is a state where a UE remains in CM-CONNECTED and can move within an area configured by NG-RAN (5G RAN consisting of gNB(s)) without notifying NG-RAN. In RRC_INACTIVE, the last serving gNB node keeps the UE context and the UE-associated NG connection (i.e. the connection to the core network). Since the RRC configurations and the connection to core network is kept in RRC_INACTIVE, UE can transition immediately to RRC connected state and perform data transfer with the core network / applications. UE initiates transition to RRC_CONNECTED from RRC_INACTIVE by sending RRC resume request.

[0081] In RRC_IDLE, UE or gNB doesn't store any Access Stratum (AS) context. UE is in CM_IDLE (there is no connection to core network). UE sets up a new connection by sending RRC Setup Request message and gNB sends RRC setup message to transition to RRC connected. UE and NW (both radio access network (RAN) and core network) exchanges messages to move the UE to CM_CONNECTED. A UE in RRC_CONNECTED may send power head room to the network according to the TS 38.321 and other relevant 3gpp specs.

[0082] 3gpp also consider Lower Layer Triggered Mobility (LTM) for performing handover.

[0083] Carrier Aggregation:

[0084] In Carrier Aggregation (CA), two or more Component Carriers (CCs) are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities: CA is supported for both contiguous and non-contiguous CCs. When CA is deployed frame timing and SFN are aligned across cells that can be aggregated (synchronous CA), or an offset in multiples of slots between the PCell / PSCell and an SCell is configured to the UE (Asynchronous CA). A UE in inactive mode may store the CA configuration. In CA, PCell or Primary Cell is the cell that is used for initial access while other cells are called Scells or secondary cells.

[0085] Multi-Radio Dual Connectivity:

[0086] 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.

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

[0088] 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] Framework for supporting capability change:

[0090] Let us consider the case of a MUSIM UE with two USIMs (i.e. two UEs in same MUSIM device), UE-A (USIM-A) and UE-B. The MUSIM UE supports dual transmission and reception. ie. 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 38.306) of UE-A may be different at different times depending on whether UE-B is in connected (i.e. depending on whether UE-B uses the RF / radio / hardware / software resources).

[0091] Let us consider 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 is pertaining 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 setup or activated in UE-A etc., measurement gaps requirements (needforgaps / needforgapsorncsg) related information in UE-A to facilitate MUSIM operations. This may be referred to as reporting of temporary capability restriction or requesting of temporary capability restriction.

[0092] When UE-A is in RRC_CONNECTED mode and the UE capability changes due to activities in UE-B, UE-A informs NW-A about the capability change through a RRC message such as UE Assistance Information(UAI). For example, UE-A may inform NW-A about temporary capability restrictions. UE-A also may inform NW-A about the removal of temporary capability restrictions through UAI.

[0093] 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 or if the temporary capability restrictions apply while the UE-A is connecting to NW-A, a similar approach as in RRC_CONNECTED can be used. UE-A may also indicate that the capability has changed in RRC setup request / RRC resume request, RRC setup complete or RRC resume complete. Temporary capability restrictions may be retrieved later through UAI etc.

[0094] NW-A may configure UE-A on whether it can inform changed capabilities, e.g. through “otherConfig” in the RRC Reconfiguration message. In other words through “otherConfig” network may control whether UE-A can update the changed capabilities (i.e. temporary capability restrictions and the removal of temporary capability restrictions). There may be a single enumerated or some other parameter that could be used to control in otherConfig which informs the UE-A to report the changed capabilities. Alternatively, each of these individual capabilities that could be changed may have separate flags in otherConfig. Accordingly, UE can report the updated or changed capabilities (temporary capability restrictions and the removal of temporary capability restrictions)) with UE assistance information message. The information contents in UAI can pertain to MUSIM assistance information or MUSIM UE capability information.

[0095] Reporting of temporary capability restrictions (and / or the removal of temporary capability restrictions) can be reactive reporting or proactive reporting. If the reported temporary capability restrictions (such as in UAI) is applicable for the current RRC configuration of the UE, it is called reactive reporting. For reactive reporting, as an example, UE may report the SCells to release, SCG to release, set of bands in which measurement objects are configured for its NR-ARFCNs etc. If the reported temporary capability restrictions (such as in UAI) is not applicable for the current RRC configuration of the UE, it is called proactive reporting. Proactive reporting may include bands or band combinations, measurement gap requirements etc. which are not part of current configuration.

[0096] A prohibit timer, musim-ProhibitTimer may be configured to control how frequently the UE can report the capability update. The capability update, for e.g. the scheduling pattern and / or TDD UL / DL config information pertaining to the UE-B as capability limitation (e.g. number of Tx / Rx) to UE-A are not static or fully prohibitive. So UE can initiate UAI while prohibit timer is not running to handle such updates. Prohibit timer may be applicable only for proactive case.

[0097] NW-A may configure UE-A with a wait timer, musim-WaitTimer to be started during the capability restriction communication. Traditionally, the musim-WaitTimer is a UE RRC timer and it is started upon sending the UAI from the RRC layer. While the wait timer, musim-WaitTimer expires, UE-A may autonomously reduce the capabilities as indicated in the temporarily restricted capabilities. Alternatively UA- may move to RRC_IDLE state upon the expiry of the wait timer. In some implementations, musim-WaitTimer may be applicable only for reactive capability restriction reporting, i.e. when the capability restrictions are pertaining to the current configuration, UE may start musim-WaitTimer and if the capability restrictions are not pertaining to the current configuration, UE may not start musim-WaitTimer.

[0098] NW-A may configure UE-A with a filter and UE-A will report the change of capabilities based on the filter. For e.g. the filter may be a bandfilter or a band combination filter or a frequency filter. If the UE capability of a band included in the filter changes, UE-A reports the capability change, for e.g. by sending UAI including temporary capability restrictions or the removal of temporary capability restrictions. If none of the capability in the filter changes due to UE-B actions, UE-A may not initiate the messages to indicate UE capability change.

[0099] If the temporary capabilities supported by the changed capability is different from the older capability, NW-A may reconfigure UE-A to release one or more SCells, SCG or perform handover etc. NW-A may configure UE-A to report any available measurements when the capabilities are changed. Since the changed capability can be different from older capability, NW-A may prefer to change the SCells or SCG rather than releasing them, or in a case perform handover to a different frequency. Measurements from the UE can aid the network to take such decisions.

[0100] The static or dynamic capability signaling reported by UE may include but not limited to.

[0101] Number of Rx links

[0102] Number of Tx links

[0103] Maximum Number of MIMO layers

[0104] Processing capability in terms of supportable component carriers or dual connectivity on NW A

[0105] Request for at least one of configuration, activation, deactivation and release of one or more SCell / SCG on NW A

[0106] UL or DL TDD configuration

[0107] DRX configuration on NW B

[0108] Measurement configuration on NW B

[0109] Frequencies or bands or band combinations which are supported or the frequencies or bands or band combinations which are restricted.

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

[0111] Network utilizes the updated capability received from the UE based on UAI which informs temporary capability restrictions and removal of temporary capability restrictions and reconfigures the UE with updated parameters. Network may update 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.

[0112] Change of UE capabilities, as described in this invention can be the temporary restriction in the UE capabilities and the removal of those temporary restrictions i.e. when we say capabilities are changed, it may mean some of the capabilities are temporarily restricted or some of the temporary restrictions are removed. UE may report the supported capabilities (e.g. the bands that are supported or band combinations that are supported or the frequencies that are supported, measurement gap requirements after the restrictions are applied, maximum number of MIMO layers supported after the restriction) after the restriction in the UE capabilities for informing the restriction. Alternatively, UE may report the restricted capabilities (e.g. the bands that are not supported or band combinations that are not supported or the frequencies that are not supported). Reporting of changed capabilities or restricted capabilities may mean reporting the restricted capabilities and reporting the supported capabilities after restriction.

[0113] Reporting of changed capabilities or reporting of removal of restricted capabilities may mean reporting the supported capabilities after restriction is removed or reporting that the previously reported capability restrictions are no longer applicable. We also use the terms temporary capability change, temporary capability restriction etc. to refer to the change of capabilities or restriction in capabilities as explained.

[0114] Reporting of changed capabilities for MUSIM operation or reporting of removal of restricted capabilities for MUSIM operation, temporary capability change for MUSIM operation, temporary capability restriction for MUSIM operation,removal of temporary capability restriction for MUSIM operation etc. also may be used to refer to the change of capabilities or restriction in capabilities or removal of restriction in capabilities as explained when the change is for MUSIM operations.

[0115] Capabilities UE-A has when UE-B is not in RRC_CONNECTED may be referred to as permanent UE capabilities of UE-A.. i.e. Capabilities in UE-A when UE-B is in RRC_IDLE or RRC_INACTIVE may be referred to as permanent UE capabilities of UE-A. In other words, capabilities in UE-A when UE-B is not sharing the radio or software or RF or hardware or any other resources for dual Reception and transmission can be referred to as permanent UE capabilities of UE-A.

[0116] In the current system, permanent UE capabilities are reported using UE Capability Transfer procedure. gNB requests the UE to report the UE capabilities by sending UECapabilityEnquiry message and the UE reports the capabilities using UE CapabilityInformation message.The reported capabilities are send to the core network and stored there so that everytime the UE moves from RRC_IDLE or RRC_INACTIVE to RRC_CONNECTED, there is no need to send the capabilities over the air. UECapabilityEnquiry message may include CapabilityRequestFilter, so that UE reports only the required information for the network.

[0117] A UE reporting temporary capability restrictions may send the list of restricted capabilities or the list of supported capabilities or the list of changed capabilities. UE may also inform the network that the temporary restriction of capabilities due to MUSIM operations are removed, once the temporary restrictions are removed. This may be performed by sending a UAI without including any of the temporary capability restrictions.

[0118] UE-A may report temporary capability restrictions proactively or reactively. In proactive approach UE-A may report the restriction in the capabilities irrespective of current RRC configuration from NW-A. For reactive approach, UE-A may report restriction on a subset of these capabilities to the NW-A at a time based on the current RRC configuration of UE-A.

[0119] UE-A in RRC_IDLE may inform NW-A about temporary capability restrictions at the time of moving to RRC_CONNCTED through an indication in MSG5 (such as RRCSetupComplete in NR).

[0120] UE-A in RRC_INACTIVE may inform NW-A about temporary capability restrictions at the time of moving to RRC_CONNCTED through an indication in MSG5 (such as RRCResumeComplete in NR). UE-A in RRC_INACTIVE may inform NW-A about temporary capability restriction at the time of moving to RRC_CONNECTED using dedicated logical channel identifiers-i.e. if the UE-A in RRC_INACTIVE has temporary capability restriction at the time of moving to RRC_CONNECTED,UE-A may transmit the RRCResumeRequest or RRCResumeRequest1 using dedicated logical channel identifiers (LCID) or Enhanced LCID (eLCID) to inform the network that there is a temporary capability restriction. Alternatively, this information may be provided in RRCResumeComplete message.

[0121] In general NW-A refers to the Radio Access Network (gNB) to which the UE-A is connected. In case of dual connectivity, UE sends UAI to the Master Node.

[0122] An example TS 38.331 specification which captures the background is given below:

[0123]

[0124]

[0125]

[0126]

[0127] We consider v17.6.0 of 3gpp specifications such as TS 38.331, TS 38.300,TS 38.306,TS 38.321 as the relevant background.

[0128] Let us consider the case of a MUSIM UE with two USIMs (i.e. two UEs in same MUSIM device), UE-A and UE-B. UE-A informs the temporary capability restrictions or the removal of temporary capability restrictions to NW-A through RRC messages such as UE Assistance Information.

[0129] The present disclosure addresses the following scenarios about the reporting of capability restrictions.

[0130] - How to start the wait timer, musim-WaitTimer when the UE-A sends a UAI to report the temporary capability restrictions

[0131] - Handling of musim-WaitTimer during a handover

[0132] - Handling of musim-WaitTimer during conditional handover

[0133] - Handling of musim-WaitTimer during lower layer triggered mobility (LTM)

[0134] - UE actions upon musim-WaitTimer expiry and communication of the same to NW-A.

[0135] - How does MN of NW-A communicate the restricted capabilities to the SN of NW-A

[0136] The UE-A in the RRC_IDLE may inform the NW-A about temporary capability restrictions at the time of moving to the RRC_CONNCTED through an indication in MSG5 (such as RRCSetupComplete in NR). This may be represented as below in 3gpp TS 38.331.

[0137]

[0138]

[0139]

[0140]

[0141]

[0142]

[0143]

[0144]

[0145] The UE-A in the RRC_INACTIVE may inform the NW-A about temporary capability restrictions at the time of moving to the RRC_CONNCTED through an indication in MSG5 (such as RRCResumeComplete in NR). The UE-A in the RRC_INACTIVE may inform the NW-A about temporary capability restriction at the time of moving to RRC_CONNECTED using dedicated logical channel identifiers i.e., if the UE-A in RRC_INACTIVE has temporary capability restriction at the time of moving to RRC_CONNECTED, UE-A may transmit the RRCResumeRequestorRRCResumeRequest1 using dedicated logical channel identifiers (LCID) or Enhanced LCID (eLCID) to inform the network that there is a temporary capability restriction.

[0146] An example specification which shows the transmission of UAI to inform temporary capability restrictions is given below:

[0147]

[0148]

[0149]

[0150]

[0151]

[0152]

[0153]

[0154]

[0155] v17.5.0 of 3gpp specifications such as TS 38.331, TS 38.300, TS 38.306, TS 38.321 are considered as the relevant background.

[0156] Further, consider a case of a MUSIM UE with two USIMs (i.e. two UEs in same MUSIM device), the UE-A (USIM-A) is moving from the RRC_IDLE or the RRC_INACTIVE state to the RRC-CONNECTED state with the NW-A. If the UE capability (UE capability in this invention refers to the UE radio access capabilities such as maximum number of MIMO layers, supported bands or band combinations or frequencies etc. which may be changed and whose restriction or removal of restriction which may be reported for the MUSIM purpose) of the UE-A is (temporarily) restricted due to the MUSIM purpose, the UE-A informs the NW-A that its capability is (temporarily) restricted due to the MUSIM purpose in messages such as RRCSetupComplete or RRCResumeComplete or by using a separate logical channel identifier while sending RRCResumeRequest or RRCResumeRequest1. The UE-A further reports the (temporary) restrictions in capabilities later, such as through messages like UAI after being configured by the network. The UE-A can report the UAI only after the security is activated and only after the network has configured the UE-A to do so through other RRC messages such as RRCReconfiguration. Further, there may be a filter (this filter is referred to as musim-CapRestrictionFilter in this invention) configured by the NW-A and the UE-A will report the (temporary) capability restriction according to the filter. For e.g., the UE-A may report the restricted bands or restricted frequencies or restricted band combinations or other information if those bands / frequencies / band combinations are included in the musim-CapRestrictionFilter.

[0157] According to the current system, the UE indicates (temporary) restriction in capabilities or removal of (temporary) restriction in capabilities only when there is a change in (temporary) restrictions after sending the UAI or if there is a (temporary) restriction in capabilities after the configuration, before reporting the (temporary) restrictions even once through UAI.

[0158] In a scenario for the UE-A which has indicated to the network that there is a temporary capability restriction while moving to the RRC_CONNECTED, the restriction in capabilities may be removed by the time, the UE-A sends the UAI to report temporary capability restrictions. In another scenario, the UE-A may not be required to report its restricted capabilities according to the configured filter by NW-A.

[0159] The NW-A may not be able to configure the UE-A with any advanced capabilities like carrier aggregation, dual connectivity, conditional handover, lower layer triggered mobility (LTM) inter-frequency measurements or measurement gaps etc. in these scenarios according to the current system.

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

[0161] Fig. 1 is a block diagram that illustrates a schematic of a user equipment (UE) (102) implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein. As shown, the UE (102) includes a processor (104), a memory (106), an I / O interface (108), and a first controller (110). Each component is explained in further detail below.

[0162] The processor (104) communicates with the memory (106), the I / O interface (108) and the first controller (110). The processor (104) is configured to execute instructions stored in the memory (106) and to perform various processes. The processor (104) may include one or a plurality of processors, may 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).

[0163] The memory (106) includes storage locations to be addressable through the processor (104). The memory (106) is not limited to a volatile memory and / or a non-volatile memory. Further, the memory (106) may include a plurality of computer-readable storage media. The memory (106) may include non-volatile storage elements. For example, non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

[0164] The I / O interface (108) transmits the information between the memory (106) and external peripheral devices. The peripheral devices are the input-output devices associated with the UE (102). Further, the first controller (110) communicates with the I / O interface (108) and the memory (106). The first controller (110) may be communicatively coupled to the memory (106) and the processor (104). The first controller (110) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0165] In an embodiment, the first controller (110) transmits an informing message to a network apparatus (202). The informing message indicates that the UE (102) has a temporary capability restriction. Temporary capability restrictions are short-term restrictions put on the access of the UE (102) to or performance on the 5G network. These restrictions may be impacted by the network apparatus (202), the UE (102), or other external factors. For example, the temporary capability restrictions may include network congestion, device based restrictions such as the restrictions due to MUSIM operations, policy based restrictions, location based restrictions, network outages, and the like. The temporary capability restrictions are resolved once the conditions or restrictions causing them are improved or alleviated.

[0166] For instance, the temporary capability restriction is a multi-SIM (MUSIM) capability restriction. The MUSIM capability restriction refers to the temporary restrictions in capability due to the usage of multiple SIMs within the UE (102). Multi-SIM devices allow users to have more than one SIM card active on the UE (102). For instance, MUSIM capability restrictions may arise due to factors such as, but not limited to RF limitations, hardware limitations, software limitations, network coverage, data / voice restrictions, bandwidth limitations, power management, policy based regulations, and the like.

[0167] Further, the informing message received is included in at least one of a RRC setup complete message, a RRC resume complete message, and a RRC reestablishment complete message. The RRC setup complete message is part of the initial connection setup procedure between the UE (102) and the network apparatus (202). It occurs when the UE (102) first establishes an RRC connection with the network apparatus (202), allowing the exchange of data. The RRC setup complete message confirms that the UE (102) is ready to communicate with the network apparatus (202) after successfully completing the RRC connection setup. The RRC resume message is used during the resumption of an RRC connection that was previously suspended, typically when the UE (102) moves from an inactive state (such as RRC Inactive or) back to a connected state (RRC Connected). The RRC resume complete message informs the network apparatus (202) that the UE (102) has successfully resumed its RRC connection and is ready to continue communication. Further, the RRC reestablishment complete message is used when the RRC connection has been disrupted (for example, due to signal loss or handover failure) and needs to be reestablished. This message is part of the recovery process to restore the connection. The RRC reestablishment complete message signals to the network apparatus (202) that the UE (102) has successfully recovered from a connection failure and has reestablished its RRC connection.

[0168] In an embodiment, the first controller (108) receives a configuration for reporting the temporary capability restrictions. The configuration for reporting temporary capability restrictions in the UE (102) ensures that the network apparatus (202) is kept aware of any temporary restrictions in the capabilities of the UE (102). For instance, the temporary capability restrictions reporting may be configured using RRC signaling, and the like. This enables the network apparatus (202) to optimize resource allocation and maintain efficient communication despite temporary capability restrictions in the UE (102).

[0169] In an embodiment, the first controller (108) determines that the UE (102) does not have the temporary capability restriction as configured by the network apparatus (202). In such a case, the UE (102) needs to inform the network apparatus (202) regarding this empty capability restriction.

[0170] In an embodiment, the first controller (108) generates a UE assistance information (UAI) message to be transmitted to the network apparatus (202). The UAI message allows the UE (102) to inform the network apparatus (202) about its preferences or constraints, such as requesting reduced data rates, longer inactivity timers, or lower frequency of paging messages, to reduce power consumption and optimize network efficiency. The UAI message is transmitted with an empty capability restriction that indicates a removal of the temporary capability restriction.

[0171] In an embodiment, the first controller (110) transmits the UAI message to the network apparatus (202). The UAI message is transmitted with an empty capability restriction that indicates a removal of the temporary capability restriction. This helps the network apparatus (202) to t stop waiting for the temporary capability restrictions.

[0172] In an embodiment, the first controller (110) receives a reconfiguration with sync message from the network apparatus (202). The reconfiguration with sync message may be used to modify the radio configuration of the UE (102) while ensuring that the UE (102) maintains or regains synchronization with the 5G network. This synchronization is necessary for the UE (102) to continue receiving and transmitting data correctly after the configuration changes. For instance, reconfiguration with sync may be used in scenarios such as handovers, where the UE (102) is transitioning from one cell to another. This requires the UE (102) to adjust its timing and frequency synchronization with the target cell.

[0173] In an embodiment, the first controller (110) determines whether the UE (102) has initiated a transmission of the UAI message requesting for a temporary capability restriction before receiving the reconfiguration with sync message within a fixed time. For example, the fixed time may be one second.

[0174] In an embodiment, the first controller (110) starts or restarts the MUSIM wait timer if the UAI message requesting for temporary capability restriction has been transmitted within the fixed time (1 second) of receiving the reconfiguration with sync message. Starting or restarting the MUSIM wait timer serves a specific purpose in ensuring that the network is aware of the temporary capability restrictions even when the source cell is not able to communicate the temporary capability restrictions to the target cell. Further, a timer value of the MUSIM wait timer is set or adjusted to a value present in a MUSIM capability restriction configuration.

[0175] In an embodiment, the first controller (110) applies a radio resource control (RRC) reconfiguration message from the network apparatus (202). The RRC reconfiguration message instructs the UE (102) to modify or update its radio resource configurations to support new or changed network parameters. For instance, the modifications or updates may include establishing / modifying / releasing bearers, activating / deactivating certain features, facilitating mobility procedures like handovers, and the like. The RRC reconfiguration message may be applied immediately or later after certain conditions such as conditions for conditional mobility are met or upon receiving specific instructions like a MAC command for LTM cell switch.

[0176] In an embodiment, the first controller (110) determines whether the RRC reconfiguration message is applied due a conditional reconfiguration execution, a lower-layer triggered motility (LTM) cell switch procedure, and whether the UE (102) has initiated the transmission of the UAI message requesting for the temporary capability restriction. The conditional reconfiguration execution makes handovers more flexible and robust. Instead of forcing the UE (102) to switch to a new cell or beam immediately upon receiving a handover command, conditional reconfiguration allows the UE (102) to wait for specific conditions to be met before executing the handover. This approach minimizes the risk of failed or unnecessary handovers, improving user experience and network performance.

[0177] The LTM cell switch procedure attempts to minimize latency and increase mobility performance by allowing choices to be taken and carried out at lower levels rather than depending entirely on higher-layer (RRC) signaling protocols. In the LTM technique, the lower levels of the protocol stack (for example, the physical layer or MAC layer) make the choice to switch cells or beams based on real-time measurements like as signal strength, signal quality, or other physical layer parameters. When the lower levels such as MAC layer receives a command to switch to a new cell, they can initiate a cell switch without waiting for an explicit instruction from the RRC layer.

[0178] In an embodiment, the first controller (108) starts or restarts the MUSIM wait timer when the RRC reconfiguration message is applied due the conditional reconfiguration execution or the LTM cell switch procedure. Starting or resuming the MUSIM wait timer has a specific purpose. It ensures that the UE (102) can successfully manage communication for many SIMs without conflict, while managing resources like as power and connection. The MUSIM wait timer is set or changed to a value specified in a MUSIM capability restriction configuration.

[0179] In an embodiment, the first controller (108) retransmits the UAI message to the network apparatus (202) to request for the temporary capability restriction. The retransmission ensures that even if the UAI message is lost or not received　during execution of conditional handover or LTM, the network apparatus　(202) can still receive it after many attempts. This is critical since omitting UAI information might result in inefficient MUSIM operations at the UE (102).

[0180] Fig. 2 is a block diagram that illustrates a schematic of the network apparatus (202) implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein. As shown, the UE (102) includes the processor (104), the memory (106), the I / O interface (108), and a second controller (204)

[0181] The second controller (204) communicates with the I / O interface (108) and the memory (106). The second controller (204) may be communicatively coupled to the memory (106) and the processor (104). The second controller (204) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0182] In an embodiment, the second controller (204) configures at least one filter based on which the UE (102) reports temporary capability restrictions. For instance, the filters may be configured based on factors such as the bands supported by the UE (102) and the network deployment, and the like. For example, the filter may include a band filter, a band combination filter, and a frequency filter. The band filter allows the UE (102) to report the temporary capability restrictions for specific band(s). The band combination filter allows the UE (102) to report the temporary capability restrictions for specific band combination(s). The frequency filter allows the UE (102) to report the temporary capability restrictions for specific frequencies.

[0183] In an embodiment, the second controller (204) determines whether the temporary capability restrictions of the UE (102) have been reported based on the at least one filter configured. Based on this determination, the second controller (204) generates a capability restriction message to be transmitted to a second network apparatus when the temporary capability restrictions of the UE (102) have been reported based on the filter(s) configured. The network apparatus (202) may correspond to a master node (MN) and the second network apparatus may correspond to a secondary node (SN). The capability restriction message includes the temporary capability restrictions of the UE (102) reported along with the configured filter. The second controller (204) may also send the band filter at a different point of time than the sending the temporary capability restriction message.

[0184] For instance, the temporary capability restrictions may include a preference of the UE (102) on secondary cells (SCells) to be released, serving cells of the UE (102) having a restricted capability, band(s) of the UE (102) having a restricted capability, band(s) of the UE (102) to be avoided for temporary capabilities restriction purposes, and the like. The capability restriction message allows the UE (102) to temporarily limit or disable specific features or capabilities based on internal conditions (for example, battery or thermal state) or network instructions (for example, congestion control or policy enforcement). These restrictions are dynamically managed and ensure optimal performance and resource usage both for the UE (102) and the network apparatus (202). Further, the second controller (204) transmits the capability restriction message generated to the second network apparatus.

[0185] Fig. 3 is a flow diagram that illustrates a method for removing temporary capability restrictions in the UE (102) during the RRC setup complete procedure according to an embodiment as disclosed herein. The method includes steps (302-308). Each step is explained in further detail below.

[0186] At step (302), the UE (102) transitions from a RRC_IDLE state to a RRC_CONNECTED state. During the transition, the UE (102) may indicate that there are temporary capability restrictions. The RRC_IDLE state is a low-power state where the UE (102) is not actively engaged in communication with the network apparatus (202), but remains registered and connected at a higher level. In this state, the UE (102) may perform basic monitoring and mobility tasks, but does not have an active radio link with the 5G network. The RRC_CONNECTED state is an active communication state in which the UE (102) has an established RRC connection with the network apparatus (202). This state allows the UE (102) to transmit data, receive data, perform handovers, and engage in other signaling and communication processes. The UE (102) transitions from the RRC_IDLE to RRC_CONNECTED when there is a need for data transmission or reception. This process starts with the UE (102) initiating a random access procedure to establish an RRC connection.

[0187] At step (304), the UE (102) receives a configuration for temporary capability reporting. Here, the temporary capability restrictions are removed before the UE (102) receives the configuration or before UE transmits that it has temporary capability restrictions.

[0188] At step (306), the UE (102) determines that there are no temporary capability restrictions. This may enable the UE (102) to operate without any temporary limitations or restrictions, due to which it has full access to all its capabilities and may utilize the 5G network fully (for example, in terms of speed, access to features like voice, video, and data services).

[0189] At step (308), the UE (102) initiates transmission of the UAI message to the network apparatus (202). The UAI message includes information stating that the temporary capability restriction has been removed. If the UE (102) informs the network apparatus (202) that it has a temporary capability restriction, such as MUSIM capability restriction, while transitioning to RRC_CONNECTED (during RRC Setup or RRC Resume procedures), but the capability restriction is not applicable while the UE (102) receives the configuration to provide MUSIM assistance information for temporary capability restriction, the UE (102) may transmit the UAI message. The UE (102) may use this UAI message to notify that the temporary capability constraints have been eliminated or that no temporary capability restrictions exist.

[0190] Fig. 4 is a flow diagram that illustrates a method for handling temporary capability restrictions using a filter during the RRC setup complete procedure according to an embodiment as disclosed herein. The method includes steps (402-408). Each step is explained in further detail below.

[0191] At step (402), the UE (102) transitions from a RRC_IDLE state to a RRC_CONNECTED state. During the transition, the UE (102) may indicate that there are temporary capability restrictions. When data transmission or reception is required, the UE (102) changes state from RRC_IDLE to RRC_CONNECTED. This process begins when the UE (102) initiates a random access method to establish an RRC connection.

[0192] At step (404), the UE (102) receives a configuration for temporary capability reporting where a temporary capability restriction is not applicable according to a received filter. Here, the temporary capability restriction is not applicable according to the received filter in configuration for temporary capability restriction reporting.

[0193] At step (406), the UE (102) determines that there are no temporary capability restrictions. This may enable the UE (102) to function without any temporary constraints or restrictions, allowing it to fully leverage the 5G network (for example, in terms of speed and access to features such as voice, video, and data services).

[0194] At step (408), the UE (102) initiates transmission of the UAI message indicating that the temporary capability restriction is removed based on the received filter. If the UE (102) has informed the network apparatus (202) that it has temporary capability restriction, such as temporary MUSIM capability restriction while transitioning to RRC_CONNECTED (during RRC Setup or RRC Resume procedures), but the UE (102) has received the configuration from the network apparatus (202) to report the temporary capability restrictions according to the filter, and the temporary capability restriction is not present according to the configured filter The UE (102) may use this UAI message to notify that the temporary capability constraints have been eliminated or that no temporary capability restrictions exist.

[0195] Fig. 5 is a flow diagram that illustrates a method for removing temporary capability restrictions in the UE (102) during the RRC resume procedure according to an embodiment as disclosed herein. The method includes steps (502-508). Each step is explained in further detail below.

[0196] At step (502), the UE (102) transitions from a RRC_INACTIVE state to a RRC_CONNECTED state. During the transition, the UE (102) may indicate that there are temporary capability restrictions. The UE (102) may notify the network apparatus　(202) that it has temporary capability restrictions when transitioning to the RRC_CONNECTED using RRCSetupComplete (when transitioning from RRC_IDLE), RRCResumeComplete (when transitioning from RRC_INACTIVE), or RRCReestablishmentComplete.

[0197] At step (504), the UE (102) receives a configuration for temporary capability reporting where a temporary capability restriction removed before receiving the configuration. Here, the temporary capability restriction is not applicable according to the received filter in configuration for temporary capability restriction reporting.

[0198] At step (506), the UE (102) determines that there are no temporary capability restrictions. This may allow the UE (102) to function without any temporary constraints or restrictions, giving it complete access to all of its capabilities and the ability to effectively utilize the 5G network.

[0199] At step (508), the UE (102) initiates transmission of the UAI message indicating that the temporary capability restriction is removed based on the received filter. The UE (102) may notify the network apparatus　(202) that it has temporary capability limits when transitioningfrom RRC_INACTIVE to RRC_CONNECTED by broadcasting RRCResumeRequest or RRCRequest1 with a particular value of LCID or eLCID. The maximum number of MIMO layers, the list of restricted frequencies, the list of affected frequencies, the preferred frequencies for the addition of SCells or SCGs, the list of restricted (affected) bands, the list of restricted band combinations, the list of supported bands, the list of supported frequencies, the list of supported band combinations, so on are examples of capability restrictions that can be updated or removed. Thus, the UE (102) may notify the network apparatus　(202) of the removal of the temporary capability limitation even before informing the network apparatus (202) of the capabilities that are restricted.

[0200] Fig. 6 is a flow diagram that illustrates a method for handling temporary capability restrictions using a filter during the RRC resume complete procedure according to an embodiment as disclosed herein. The method includes steps (602-608). Each step is explained in further detail below.

[0201] At step (602), the UE (102) transitions from a RRC_INACTIVE state to a RRC_CONNECTED state. During the transition, the UE (102) may indicate that there are temporary capability restrictions. The RRC_INACTIVE state allows the UE (102) to maintain its connection with the network apparatus (202) while reducing power consumption and signaling overhead. In RRC_INACTIVE, the UE (102) maintains an RRC connection with the network apparatus (202), but does not engage in continuous signaling, thus reducing the need for constant handovers or updates. The UE (102) transitions to the RRC_CONNECTED state when there is incoming data or signaling for it, and it can transmission back to RRC_INACTIVE when the activity subsides.

[0202] At step (604), the UE (102) receives a configuration for temporary capability reporting where a temporary capability restriction is not applicable according to a received filter. Here, the temporary capability restriction is not applicable according to the received filter in configuration for temporary capability restriction reporting.

[0203] At step (606), the UE (102) determines that there are no temporary capability restrictions. This may enable the UE (102) to operate without any temporary limitations or restrictions, due to which it has full access to all its capabilities and may utilize the 5G network fully, For example, the UE (102) may utilize the 5G network in terms of speed, access to features like voice, video, data services, and the like.

[0204] At step (608), the UE (102) initiates transmission of the UAI message indicating that the temporary capability restriction is removed based on the received filter. If the UE (102) informs the network apparatus (202) that it has capability restriction such as MUSIM capability restriction while transitioning to RRC_CONNECTED, but the capability restriction is not present for at least some of the capabilities when the UE (102) has received configuration to provide the MUSIM assistance information for temporary capability restriction (according to the filter, if configured), the UE (102) initiates the transmission of UAI and reports that the capability restrictions are removed for some of the capabilities.

[0205] The capability restrictions can be updated / removed to include the maximum number of MIMO layers, a list of restricted frequencies, a list of affected frequencies, preferred frequencies for adding SCells or SCGs, a list of restricted (affected) bands, a list of restricted band combinations, a list of supported bands, a list of supported frequencies, a list of supported band combinations, and the like. The UE (102) may commence the UAI communication to notify the network apparatus　(202) that the restrictions on some of the capabilities have been updated, even if it has not notified the network apparatus (202) of the specific capabilities that are limited.

[0206] In an embodiment, the UE (102) may report that the temporary capability restrictions are removed by sending a flag to the network. In an embodiment, the UE (102) reports that temporary capability restrictions are removed by sending the UAI message without including the field containing restricted capabilities (such as not including the field musim-MIMO-Layers-DL, any value for the restricted capability, or not including musim-ForbiddenFreq or msuim-affectedFreq and so on ) or by including the field but not including any value for the field such as musim-ForbiddenFreq or msuim-affectedFreq and so on or by including the field but including a special value for the field such as musim-MIMO-Layers-DL or musim-MIMO-Layers-UL and so on.

[0207] In an embodiment, some of the embodiments may be captured as below in 3gpp TS 38.331.

[0208]

[0209] In an embodiment, some of the embodiments may be captured as below in 3gpp TS 38.331.

[0210]

[0211] In an embodiment, some of the embodiments may be captured as below in 3gpp TS 38.331.

[0212]

[0213] In an embodiment, some of the embodiments may be captured as below in 3gpp TS 38.331.

[0214]

[0215] In the below sections, various ways of capturing the above embodiments considering the filter are proposed.

[0216] In an embodiment, some of the embodiments may be captured as below in 3gpp TS 38.331.

[0217]

[0218] In an embodiment, some of the embodiments may be captured as below in 3gpp TS 38.331.

[0219]

[0220] In an embodiment, some of the embodiments may be captured as below in 3gpp TS 38.331.

[0221]

[0222] In an embodiment, some of the embodiments may be captured as below in 3gpp TS 38.331.

[0223]

[0224] In an embodiment, if the UE (102) has informed the network apparatus (202) that it has temporary capability restriction such as temporary MUSIM capability restriction while transitioning to RRC_CONNECTED, but the temporary capability restriction is not present (or at least some of the temporary capability restrictions are updated / not present) at the time of reporting the capability restrictions, the UE (102) initiates the transmission of the UAI message and reports that the temporary capability restrictions are removed / updated (or that there are no capability restrictions or that there are no capability restrictions for some of the capabilities).

[0225] In an embodiment, the temporary capability restrictions that may be updated / removed in the previous embodiment include the maximum number of MIMO layers, list of restricted frequencies, list of affected frequencies, preferred frequencies for addition of SCells or SCGs,list of restricted (affected) bands, list of restricted band combinations, list of supported bands, list of supported frequencies, list of supported band combinations, and the like. The UE (102) initiates the UAI transmission to inform the network apparatus (202) that the temporary restriction of some of the capabilities which are updated, even though it has not informed the network apparatus (202) the actual capabilities that are restricted.

[0226] In an embodiment, if the UE (102) has informed the network apparatus (202) that it has (temporary) capability restriction such as (temporary) MUSIM capability restriction while transitioning to RRC_CONNECTED, but the UE (102) has received the configuration from the network apparatus (202) to report the (temporary) capability restrictions based on a filter and the (temporary) capability restriction is not present or at least some of the (temporary) capability restrictions are not present according to the configured filter at the time of reporting the (temporary) capability restrictions, the UE (102) initiates the transmission of the UAI and reports that the (temporary)capability restrictions are removed (or that there are no (temporary) capability restrictions or that there are no (temporary) capability restrictions for some of the capabilities).

[0227] In an embodiment, the (temporary) capability restrictions that may be updated / removed in the previous embodiment include the maximum number of MIMO layers, list of restricted frequencies, list of affected frequencies, preferred frequencies for addition of SCells or SCGs,list of restricted (affected) bands, list of restricted band combinations, list of supported bands, list of supported frequencies, list of supported band combinations, and the like. The UE (102) initiates the UAI transmission to inform the network apparatus (202) that the (temporary) restriction of some of the capabilities are updated according to the configured filter, even though it has not informed the network apparatus (202) of the actual capabilities that are restricted.

[0228] In an embodiment, if the UE (102) has informed the network apparatus (202) that it has capability restriction such as MUSIM capability restriction while transitioning to RRC_CONNECTED, but some of the capability restrictions are not present at the time of being configured for reporting the (temporary) capability restrictions, the UE (102) initiates the transmission of UAI and reports that some of the capability restrictions are removed. Alternatively, the UE (102) may report the temporary capabilities that are restricted.

[0229] In an embodiment, the network apparatus (202) may inform the UE (102) whether it needs to inform the restricted frequencies (frequencies here means frequency, bands or band combinations). For example, the network apparatus (202) may inform the UE (102), a flag which informs it not to report restricted frequencies (or a flag which informs it to report restricted frequencies). If the network apparatus (202) informs the UE (102) to report restricted frequencies as above (for example, by not including / configuring the flag which asks the UE (102) not to report restricted frequencies or by including / configuring the flag which asks the UE (102) to report restricted frequencies), the UE (102) may exclude the request for releasing SCG or the list of SCells to be released in the UAI. The network apparatus (202) identifies the SCG or SCells to be released based on the information of restricted frequencies.

[0230] In an embodiment, if the network apparatus (202) informs the UE (102) to report restricted frequencies as above (for example, by not including / configuring the flag which asks the UE (102) not to report restricted frequencies or by including / configuring the flag which asks the UE (102) to report restricted frequencies), the UE (102) excludes configuring the maximum DL MIMO layers or the maximum UL MIMO layers per SCell or SCG and configure it for frequencies (for example, frequency, bands or band combination).

[0231] In general, the network apparatus (202) refers to the radio access network (gNB) to which the UE (102) is connected. In the case of dual connectivity, UE (102) sends the UAI message to the master node.

[0232] Fig. 7 is a flow diagram that illustrates a method for starting or restarting of the MUSIM wait timer associated with the UE according to an embodiment as disclosed herein. The method includes steps (702-706). Each step is explained in further detail below.

[0233] At step (702), the UE (102) transmits the UAI message for requesting restricted capabilities to the lower layers. When the RRC in the UE (102) transmits an RRC message, such as the UAI, to seek temporary capability limits, it routes the message to lower layers. The lower layers convey the message using the resources assigned by the network apparatus　(202). Before the network apparatus (202) allocates resources, the lower layers may need to notify it of the need for resources via a method such as a scheduling request or a buffer status report. Furthermore, the message transmission may fail (due to Hybrid Automatic Repeat Request (HARQ) or Automatic Repeat Request (ARQ) problems) during first efforts, causing the lower layers to retransmit the message.

[0234] At step (704), the UE (102) receives a configuration from the lower layers about the successful delivery of the UAI message. When the transmission is successful, the RRC message is regarded successfully delivered. The lower levels may communicate this information to the RRC.

[0235] At step (706), the UE (102) starts or restarts the MUSIM wait timer. The UE (102) starts or restarts (for example, if the timer is already running) the musim-WaitTimer upon successful receipt of the RRC message (such as UAI) seeking temporary capability restriction, as validated by the lower layers. This may apply if the temporary capability restriction is a limitation in the UE capabilities connected to the present configuration (for a reactive approach). When the musim-WaitTimer expires, the UE (102) may restrict its capabilities in accordance with the capacity constraints communicated to the network apparatus (202). Therefore, it is critical that the timer be started simultaneously in both the UE (102) and the network apparatus (202). When the lower layers validate the successful transmission of the UAI seeking temporary capability restriction, they start the musim-WaitTimer to verify that both the UE (102) and the network apparatus　(202) have the same timer value. Thus for reactive approach, the UE (102) starts or restarts (for example, if the timer is already running) the musim-WaitTimer upon successful delivery of the UAI requesting for temporary capability restriction confirmed by the lower layers.

[0236] In an embodiment, the UE (102) starts or restarts (for example, if the timer is already running) musim-WaitTimer upon successful delivery of the UAI message requesting for temporary capability restriction confirmed by lower layers for proactive approach also (for example, requesting of capability restrictions which are not part of current RRC configuration).

[0237] In an embodiment, the UE (102) starts or restarts (for example, if the timer is already running) musim-ProhibitTimer upon successful delivery of the UAI message requesting for temporary capability restriction is confirmed by lower layers.

[0238] An example specification extract in TS 38.331 is given below:

[0239]

[0240] Fig. 8 is a flow diagram that illustrates a method for interacting between the MUSIM wait timers based on a reconfiguration with sync according to an embodiment as disclosed herein. The method includes steps (802-806). Each step is explained in further detail below.

[0241] At step (802), the UE (102) transmits the UAI message requesting for restricted capabilities. For example, the restricted capabilities may be for reactive reporting.

[0242] At step (804), the UE (102) receives a reconfiguration with sync message within 1 second of transmission of the UAI. At step (806), the UE (102) starts or restarts the MUSIM wait timers based on the reconfiguration with sync message received. If the UE (102) initiated transmission of the UAI message for the corresponding cell group (MCG / SCG) during a fixed time (for example, the last 1 second) prior to receiving reconfiguration with sync and the UE (102) is still configured to provide the UAI for the corresponding cell group, the UE (102) starts or restarts musim-waitTimer, if configured. The UE (102) begins or restarts the musim-waitTimer, setting the timer value to the value specified in the respective configuration. The UE (102) may also retransmit the UAI to seek a temporary capability restriction.In NR, UE may send the UAI for MUSIM temporary capability restrictions to the Master Cell Group (MCG).

[0243] If the UE (102) sends the UAI message seeking temporary capability limitation and receives reconfiguration with sync within 1 second, it starts or restarts the musim-waitTimer. In one embodiment, if the UE (102) sends a UAI message requesting a temporary capability restriction for a reactive capability (for example, a capability that is part of the current UE RRC configuration) and receives the reconfiguration with sync within 1 second, the UE (102) starts or restarts the musim-waitTimer. The UE (102) begins or restarts the musim-waitTimer, setting the timer value to the value specified in the respective configuration.

[0244] Fig. 9 is a flow diagram that illustrates a method for interacting between the MUSIM wait timers during a LTM cell switch procedure according to an embodiment as disclosed herein. The method includes steps (902-906). Each step is explained in further detail below.

[0245] At step (902), the UE (102) transmits the UAI message requesting for restricted capabilities. For example, the restricted capabilities may be for reactive reporting.

[0246] At step (904), the UE (102) performs the LTM cell switch procedure. At step (906), the UE (102) starts or restarts the MUSIM wait timer based on the LTM cell switch procedure being performed. In an embodiment, if the RRCReconfiguration message is applied due to an LTM cell switch procedure, and the UE (102) is configured to provide the UAI for the corresponding cell group, and the UE (102) has initiated transmission of the UAI message for the corresponding cell group since it was configured to do so, the UE (102) starts or restarts musim-waitTimer. The UE (102) also may retransmit the UAI to request for the temporary capability restriction. If the UE (102) has send the UAI requesting for temporary capability restriction and the UE (102) has applied the RRCReconfiguration message due to an LTM cell switch procedure, the UE (102) starts or restarts musim-waitTimer.

[0247] In an embodiment, if the UE (102) has send the UAI requesting for temporary capability restriction and the temporary capability restriction is for reactive capability (for example, a capability that is part of current UE RRC configuration) and the UE (102) has applied the RRC Reconfiguration message due to an LTM cell switch procedure, the UE (102) starts or restarts the musim-waitTimer. In an embodiment, the LTM cell switch procedure includes the LTM cell switch upon the reception of a LTM Cell switch command MAC CE from the network apparatus. In an embodiment, the LTM cell switch procedure includes LTM cell switch upon the selection of a LTM candidate cell after a radio link failure or LTM cell switch failure.

[0248] In an embodiment, this may be captured as below in TS 38.331.

[0249]

[0250] In an embodiment, if the UE (102) has send the UAI requesting for temporary capability restriction and the temporary capability restriction is for proactive capability (for example, a capability that is part of current UE RRC configuration) and the UE (102) has applied the RRC Reconfiguration message due to an LTM cell switch procedure, the UE (102) starts or restarts a musim-prohibitTimer.

[0251] In an embodiment, if the UE (102) has send the UAI requesting for temporary capability restriction and the temporary capability restriction is for proactive capability (for example, a capability that is part of current UE RRC configuration) and the UE (102) has applied the RRCReconfiguration message due to a conditional reconfiguration execution, the UE (102) starts or restarts the musim-prohibitTimer.

[0252] In an embodiment, if the UE (102) initiated transmission of the UAI message for the corresponding cell group during the last 1 second, and the UE (102) is still configured to provide the concerned UAI message for the corresponding cell group, the UE (102) starts or restarts the musim-prohibitTimer.

[0253] Fig. 10 is a flow diagram that illustrates a method for interacting between the MUSIM wait timers during a conditional reconfiguration execution according to an embodiment as disclosed herein. The method includes steps (1002-1006). Each step is explained in further detail below.

[0254] At step (1002), the UE (102) transmits the UAI message requesting for restricted capabilities. For example, the restricted capabilities may be for reactive reporting.

[0255] At step (1004), the UE (102) performs a conditional reconfiguration execution. At step (1006), the UE (102) starts or restarts the MUSIM wait timer based on the conditional reconfiguration execution being performed. In an embodiment, if the RRCReconfiguration message is applied due to a conditional reconfiguration execution, and the UE (102) is configured to provide the UAI for the corresponding cell group, and the UE (102) has initiated transmission of UAI message for the corresponding cell group since it was configured to do so, the UE (102) starts or restarts the musim-waitTimer. The UE (102) also may retransmit the UAI to request for the temporary capability restriction. If the UE (102) has send the UAI requesting for temporary capability restriction and the UE (102) has applied the RRC Reconfiguration message due to a conditional reconfiguration execution, the UE (102) starts or restarts the musim-waitTimer.

[0256] In an embodiment, if the UE (102) has send the UAI requesting for temporary capability restriction and the temporary capability restriction is for reactive capability (for example, a capability that is part of current UE RRC configuration) and the UE (102) has applied the RRC Reconfiguration message due to a conditional reconfiguration execution, the UE (102) starts or restarts the musim-waitTimer.

[0257] In an embodiment, the UE (102) will stop the musim-WaitTimer upon LTM cell switch procedure or conditional reconfiguration execution procedure or if the UAI requesting the temporary capability restriction was send within 1 second of receiving the reconfiguration with sync and will not retransmit the UAI requesting for temporary capability restriction.

[0258] Fig. 11 is a flow diagram that illustrates a method for requesting for temporary capability restriction according to an embodiment as disclosed herein. The method includes steps (1102-1106). Each step is explained in further detail below.

[0259] At step (1102), the UE (102) transmits the UAI message requesting for restricted capabilities. For example, the restricted capabilities may be for reactive reporting.

[0260] At step (1104), the UE (102) generates the UAI message. The UAI message generated may include whether the UE (102) will perform autonomous capability reduction upon expiry of the MUSIM wait timer. At step (1106), the UE (102) starts or restarts the MUSIM wait timer. In an embodiment, the UE (102) informs its preferred action (for example, action it may perform) to the network apparatus (202) if it does not accept (or respond for or configure the UE (102) according to the changed temporary capabilities) for the temporary capability restriction. In an embodiment, the UE (102) informs its preferred action (for example, action it may perform) for the musim-waitTimer expiry to the network apparatus (202). In an embodiment, the UE (102) informs the network apparatus (202) that it will apply the requested temporary capability restrictions if the musim-waitTimer expires. In an embodiment, the UE (102) informs the network apparatus (202) that it will apply the requested restricted capabilities (for example, temporary capability restrictions) if the musim-waitTimer expires in the UAI message.

[0261] In an embodiment, the UE (102) informs the network apparatus (202) that it will apply the requested restricted capabilities (for example, temporary capability restrictions) if the musim-waitTimer expires in the same UAI message which is used to request for restricted capabilities.

[0262] In an embodiment, the UE (102) informs the network apparatus (202) that it will not apply the requested restricted capabilities (for example, temporary capability restrictions) if the musim-waitTimer expires. In an embodiment, the UE (102) informs the network apparatus (202) that it will not apply the requested restricted capabilities (for example, temporary capability restrictions) if the musim-waitTimer expires in the UAI message. In an embodiment, the UE (102) informs the network apparatus (202) that it will not apply the requested restricted capabilities (for example, temporary capability restrictions) if the musim-waitTimer expires in the same UAI message which is used to request for restricted capabilities.

[0263] In an embodiment, the UE (102) informs the network apparatus (202) whether it will apply the requested restricted capabilities (for example, temporary capability restrictions) if the musim-waitTimer expires. In an embodiment, the UE (102) informs the network apparatus (202) whether it will apply the requested restricted capabilities (for example, temporary capability restrictions) if the musim-waitTimer expires in the UAI message. In an embodiment, the UE (102) informs the network apparatus (202) whether it will apply the requested restricted capabilities (for example, temporary capability restrictions) if the musim-waitTimer expires in the same UAI message which is used to request for restricted capabilities.

[0264] Fig. 12 is a flow diagram that illustrates a method for temporary capability restriction or the removal of temporary capability restrictions during MN-SN interactions according to an embodiment as disclosed herein. The method includes steps (1202-1206). Each step is explained in further detail below.

[0265] At step (1202), the UE (102) is configured with a filter for reporting capability restrictions. For instance, the configuring of the UE (102) may be performed using the MN.

[0266] At step (1204), the UAI message is received. The UAI message informs a capability restriction or the removal of the capability restriction by the MN. At step (1206), the MN informs the SN regarding the capability restriction or the removal of the capability restriction.

[0267] In an embodiment, in dual connectivity, the MN (such as gNB which serves as Master Node) informs the SN (such as gNB which serves as Master Node), the information about the UE capability restriction (for example, temporary capability restrictions) or the removal of the UE capability restriction (for example, the removal of temporary capability restrictions) it has received from the UE. In an embodiment, the MN informs the SN the UE capability restriction (for example, temporary capability restrictions) or the removal of the UE capability restriction (for example, the removal of temporary capability restrictions) using RRC inter node message INM CG-Config message. In an embodiment, MN informs SN the UE capability restriction (for example, temporary capability restrictions) or the removal of the UE capability restriction (for example, the removal of temporary capability restrictions) using the IE ueAssistanceInformationSCG-r16.

[0268] In an embodiment, the MN informs the SN the filter (such as band filter or band combination filter or frequency filter) it has configured the UE (102) for requesting the capability restriction (i.e. temporary capability restrictions). For example, if the MN has configured band filter to the UE (102) and it has received capability restriction from the UE (102) based on the band filter, the MN informs the received restricted capabilities and the band filter to the SN. MN may inform the band filter to the SN along with the restricted capabilities or the band filter may be informed in a separate inter node message.

[0269] In an embodiment, if the MN has received measurement gap requirements from the UE (102) due to MUSIM operation, it informs the same to the SN. The MN may send the received measurement gap requirements from the UE (102) such as musim-NeedForGapsInfoNR to the SN. In an embodiment, this may be send by including the received measurement gap requirements in RRC INM message such as CG-Config.

[0270] In an embodiment, the source gNB includes the received measurement gap requirements from the UE (102) and the filter configured at the UE (102) for reporting temporary capability restrictions due to MUSIM operation to the target gNB in handover preparation Information message.

[0271]

[0272]

[0273] -- ASN1START

[0274] -- TAG-HANDOVER-PREPARATION-INFORMATION-START

[0275]

[0276] HandoverPreparationInformation ::= SEQUENCE {

[0277] criticalExtensions CHOICE {

[0278] c1 CHOICE{

[0279] handoverPreparationInformation HandoverPreparationInformation-IEs,

[0280] spare3 NULL, spare2 NULL, spare1 NULL

[0281] },

[0282] criticalExtensionsFuture SEQUENCE {}

[0283] }

[0284] }

[0285]

[0286] HandoverPreparationInformation-IEs ::= SEQUENCE {

[0287] ue-CapabilityRAT-List UE-CapabilityRAT-ContainerList,

[0288] sourceConfig AS-Config OPTIONAL, -- Cond HO

[0289] rrm-Config RRM-Config OPTIONAL,

[0290] as-Context AS-Context OPTIONAL,

[0291] nonCriticalExtension SEQUENCE {} OPTIONAL

[0292] }

[0293]

[0294] AS-Config ::= SEQUENCE {

[0295] rrcReconfiguration OCTET STRING (CONTAINING RRCReconfiguration),

[0296] ...,

[0297] [[

[0298] sourceRB-SN-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL,

[0299] sourceSCG-NR-Config OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL,

[0300] sourceSCG-EUTRA-Config OCTET STRING OPTIONAL

[0301] ]],

[0302] [[

[0303] sourceSCG-Configured ENUMERATED {true} OPTIONAL

[0304] ]],

[0305] [[

[0306] sdt-Config-r17 SDT-Config-r17 OPTIONAL

[0307] ]]

[0308] }

[0309]

[0310] AS-Context ::= SEQUENCE {

[0311] reestablishmentInfo ReestablishmentInfo OPTIONAL,

[0312] configRestrictInfo ConfigRestrictInfoSCG OPTIONAL,

[0313] ...,

[0314] [[ ran-NotificationAreaInfo RAN-NotificationAreaInfo OPTIONAL

[0315] ]],

[0316] [[ ueAssistanceInformation OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL -- Cond HO2

[0317] ]],

[0318] [[

[0319] selectedBandCombinationSN BandCombinationInfoSN OPTIONAL

[0320] ]],

[0321] [[

[0322] configRestrictInfoDAPS-r16 ConfigRestrictInfoDAPS-r16 OPTIONAL,

[0323] sidelinkUEInformationNR-r16 OCTET STRING OPTIONAL,

[0324] sidelinkUEInformationEUTRA-r16 OCTET STRING OPTIONAL,

[0325] ueAssistanceInformationEUTRA-r16 OCTET STRING OPTIONAL,

[0326] ueAssistanceInformationSCG-r16 OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL, -- Cond HO2

[0327] needForGapsInfoNR-r16 NeedForGapsInfoNR-r16 OPTIONAL

[0328] ]],

[0329] [[

[0330] configRestrictInfoDAPS-v1640 ConfigRestrictInfoDAPS-v1640 OPTIONAL

[0331] ]],

[0332] [[

[0333] needForGapNCSG-InfoNR-r17 NeedForGapNCSG-InfoNR-r17 OPTIONAL,

[0334] needForGapNCSG-InfoEUTRA-r17 NeedForGapNCSG-InfoEUTRA-r17 OPTIONAL,

[0335] mbsInterestIndication-r17 OCTET STRING (CONTAINING MBSInterestIndication-r17) OPTIONAL

[0336] ]]

[0337] [[

[0338] musim-NeedForGapsInfoNR-r18NeedForGapsInfoNR-r16 OPTIONAL,

[0339] musim-candidateBandList-r18 MUSIM-CandidateBandList-r18 OPTIONAL, -- Need M

[0340] ]]

[0341] }

[0342]

[0343] ConfigRestrictInfoDAPS-r16 ::= SEQUENCE {

[0344] powerCoordination-r16 SEQUENCE {

[0345] p-DAPS-Source-r16 P-Max,

[0346] p-DAPS-Target-r16 P-Max,

[0347] uplinkPowerSharingDAPS-Mode-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic }

[0348] } OPTIONAL

[0349] }

[0350]

[0351] ConfigRestrictInfoDAPS-v1640 ::= SEQUENCE {

[0352] sourceFeatureSetPerDownlinkCC-r16 FeatureSetDownlinkPerCC-Id,

[0353] sourceFeatureSetPerUplinkCC-r16 FeatureSetUplinkPerCC-Id

[0354] }

[0355]

[0356] ReestablishmentInfo ::= SEQUENCE {

[0357] sourcePhysCellId PhysCellId,

[0358] targetCellShortMAC-I ShortMAC-I,

[0359] additionalReestabInfoList ReestabNCellInfoList OPTIONAL

[0360] }

[0361]

[0362] ReestabNCellInfoList ::= SEQUENCE ( SIZE (1..maxCellPrep) ) OF ReestabNCellInfo

[0363]

[0364] ReestabNCellInfo::= SEQUENCE{

[0365] cellIdentity CellIdentity,

[0366] key-gNodeB-Star BIT STRING (SIZE (256)),

[0367] shortMAC-I ShortMAC-I

[0368] }

[0369]

[0370] RRM-Config ::= SEQUENCE {

[0371] ue-InactiveTime ENUMERATED {

[0372] s1, s2, s3, s5, s7, s10, s15, s20,

[0373] s25, s30, s40, s50, min1, min1s20, min1s40,

[0374] min2, min2s30, min3, min3s30, min4, min5, min6,

[0375] min7, min8, min9, min10, min12, min14, min17, min20,

[0376] min24, min28, min33, min38, min44, min50, hr1,

[0377] hr1min30, hr2, hr2min30, hr3, hr3min30, hr4, hr5, hr6,

[0378] hr8, hr10, hr13, hr16, hr20, day1, day1hr12, day2,

[0379] day2hr12, day3, day4, day5, day7, day10, day14, day19,

[0380] day24, day30, dayMoreThan30} OPTIONAL,

[0381] candidateCellInfoList MeasResultList2NR OPTIONAL,

[0382] ...,

[0383] [[

[0384] candidateCellInfoListSN-EUTRA MeasResultServFreqListEUTRA-SCG OPTIONAL

[0385] ]]

[0386] }

[0387]

[0388] -- TAG-HANDOVER-PREPARATION-INFORMATION-STOP

[0389] -- ASN1STOP

[0390] In an embodiment, one or more of the embodiments applicable for temporary capability restrictions in this invention are applicable for removal of temporary capability restrictions also. In an embodiment, one or more of the embodiments applicable for reactive method of reporting of temporary capability restrictions are applicable for proactive reporting of temporary capability restrictions also. In an embodiment, one or more of the embodiments for temporary capability restrictions are applicable for the temporary capability restrictions for MUSIM operations. In an embodiment, one or more of the embodiments for temporary capability restrictions are applicable for the temporary capability restrictions for causes other than MUSIM operations.

[0391] Fig. 13 is a flow diagram that illustrates a method for handling temporary capability restriction and removal in a 5G network according to an embodiment as disclosed herein. The method includes steps (1302-1310). Each step is explained in further detail below.

[0392] At step (1302), the UE (102) transmits an informing message to a network apparatus (202). The informing　message informs that the UE (102) has a temporary capability restriction. Temporary capability constraints are short-term limitations imposed on the UE's (102) access to or performance on the 5G network. These limits may be influenced by the network apparatus (202), the UE (102), or other external variables. For example, temporary capability constraints may include network congestion, device-based restrictions such as those imposed by MUSIM operations, policy-based restrictions, location-based restrictions, network outages, and so on. Temporary capability constraints are lifted whenever the underlying problems or restrictions are remedied or relieved.

[0393] For example, the temporary capability restriction is a multi-SIM (MUSIM) capability restriction. The MUSIM capability restriction refers to the temporary or permanent restrictions placed on the use of multiple SIMs within the UE (102). Multi-SIM devices allow customers to have many SIM cards active on the same UE (102). For example, MUSIM capacity constraints may occur as a result of variables such as RF restrictions when other USIM is connected, hardware restrictions when other USIM is connected, software restrictions when other USIM is connected, network coverage, data / voice restrictions, bandwidth limitations, power management, policy-based rules, and the like.

[0394] Furthermore, the informing　message received is included in at least one of the following messages: RRC setup complete, RRC resume complete, and RRC reestablishment complete. The RRC setup complete message is part of the initial connection setup operation for the UE (102) and the network apparatus　(202). It occurs when the UE (102) initially establishes an RRC connection with the network equipment (202) to facilitate data exchange. The RRC setup complete message indicates that the UE (102) is now ready to interact with the network apparatus　(202) after successfully completing the RRC connection setup.

[0395] The RRC resume complete message is used when a previously interrupted RRC connection is resumed, often when the UE (102) transitions from an inactive state (such as RRC Inactive) to a connected state (RRC Connected). The RRC resume complete message notifies the network that the UE has successfully resumed its RRC connection and is ready to continue communication. Further, the RRC reestablishment complete message is used when the RRC connection has been weakened (for example, by signal loss or handover failure) and must be restored. This message is part of the recovery procedure that will re-establish the connection. The RRC reestablishment complete message informs the network apparatus (202)　that the UE (102)　successfully recovered from a connection failure and restored its RRC connection.

[0396] At step (1304), the UE (102) receives a configuration for reporting the temporary capability restrictions. The configuration that is used for reporting temporary capability constraints in the UE (102) guarantees that the network apparatus (202) is alerted to any changes in the　performance or capabilities of the UE (102), for example, due to MUSIM operations. For example, RRC signaling, measurement reporting, dynamic adaption, and other techniques can be used to set temporary capability limits reporting. This allows the network apparatus　(202) to configure the UE with full capabilities, optimize resource allocation and sustain efficient communication after the UE (102) experiences temporary restrictions.

[0397] At step (1306), the UE (102) determines that it does not have the temporary capability restriction to be reported based on the configuration from the network apparatus. In such a case, the UE (102) informs the network apparatus (202) regarding this empty capability restriction.

[0398] At step (1308), the UE (102) generates the UAI message to be transmitted to the network apparatus (202). The UAI message may be used primarily to optimize resource management in cases where the UE (102) does not require full network resources owing to reasons such as low data demand, power-saving requirements, or continued idle activities. The UAI message enables the UE (102) to advise the network apparatus (202) of its preferences or limits, such as requesting lower data rates, longer inactivity durations, or lower paging message frequency, in order to decrease power consumption and maximize network efficiency and also about the temporary capability restrictions. The UAI notification includes an empty capability restriction, indicating that the temporary capability restriction has been removed.

[0399] At step (1310), the UE (102) transmits the UAI message to the network apparatus (202). The UAI message is transmitted with an empty capability restriction that indicates a removal of the temporary capability restriction. This helps the network apparatus (202) configure the UE with the entire capabilities to improve overall performance and user experience.

[0400] Fig. 14 is a flow diagram that illustrates a method for temporary capability restriction and removal in a 5G network by managing a MUSIM wait timer according to an embodiment as disclosed herein. The method includes steps (1402-1406). Each step is explained in further detail below.

[0401] At step (1402), the UE (102) receives a reconfiguration with sync message from the network apparatus (202). The reconfiguration with sync message may be used to change the radio configuration of the UE (102) while ensuring that it remains or regains synchronization with the 5G network. This synchronization is required for the UE (102) to continue receiving and delivering data properly following configuration modifications. For example, reconfiguration with sync might be employed in cases like handovers, when the UE (102) switches from one cell to another. The UE (102) needs to adjust its time and frequency synchronization with the target cell.

[0402] At step (1404), the UE (102) determines whether the UE (102) has initiated a transmission of the UAI message requesting for a temporary capability restriction before receiving the reconfiguration with sync message within a fixed time. For example, the fixed time may be one second.

[0403] At step (1406), the UE (102) starts or restarts the MUSIM wait timer if the UAI message requesting for temporary capability restriction has been transmitted within the fixed time (1 second) of receiving the reconfiguration with sync message. Starting or resuming the MUSIM wait timer has a specific purpose: to ensure that the UE (102) can ensure that the target cell receives information about the restrictions. Furthermore, a timer value for the MUSIM wait timer is established or altered to a value found in a MUSIM capability restriction configuration.

[0404] Fig. 15 is a flow diagram that illustrates a method for managing the MUSIM wait timer based on a RRC reconfiguration message. The method includes steps (1502-1508)

[0405] At step (1502), the UE (102) applies a RRC reconfiguration message from the network apparatus (202). The RRC reconfiguration message configures the UE (102) to adapt or update its radio resource settings to accommodate new or altered network parameters. For example, revisions or updates might involve establishing / modifying / releasing bearers, activating / deactivating certain features, enabling mobility processes such as handovers, and the like. The RRC Reconfiguration message may be applied due to conditional reconfiguration execution or LTM cell switch.

[0406] At step (1504), the UE (102) determines whether the RRC reconfiguration message is applied due a conditional reconfiguration execution, a lower-layer triggered motility (LTM) cell switch procedure, and whether the UE (102) has initiated the transmission of the UAI message requesting for the temporary capability restriction. Conditional reconfiguration execution improves handover flexibility and robustness. Instead of requiring the UE (102) to switch to a new cell immediately after receiving a handover command, conditional reconfiguration allows the UE (102) to wait for particular criteria to be satisfied before carrying out the handover. This technique reduces the likelihood of unsuccessful or needless handovers, hence enhancing user experience and network performance.

[0407] The LTM cell switch technique aims to reduce latency and improve mobility performance by allowing decisions to be made and implemented at lower layers rather than relying solely on higher-layer (RRC) communication protocols. In the LTM approach, the lower layers of the protocol stack (for example, the physical layer or the MAC layer) decide whether to switch cells depending on real-time measurements like as signal strength, signal quality, or other physical layer factors. When the lower layers in the UE receive an instruction from the lower layers in the network, they can begin a cell switch without waiting for an explicit command from the RRC layer.

[0408] At step (1506), the UE (102) starts or restarts the MUSIM wait timer when the RRC reconfiguration message is applied due the conditional reconfiguration execution or the LTM cell switch procedure. Starting or restarting the MUSIM wait timer serves a specific function. It assures that the UE (102) can ensure that the restriction is properly communicated to the new serving cell. The MUSIM wait timer is set or adjusted to the value given in the MUSIM capability restriction configuration.

[0409] At step (1508), the UE (102) retransmits the UAI message to the network apparatus (202) to request for the temporary capability restriction. The retransmission assures that even if the UAI message is lost or cannot be send during transmission, the network apparatus　(202) can still receive it after many attempts. This is crucial because ignoring UAI information may result in inefficient network decisions for the UE (102).

[0410] Fig. 16 is a flow diagram that illustrates a method for temporary capability restriction and removal in a 5G network based on a configured filter according to an embodiment as disclosed herein. The method includes steps (1602-1606). Each step is explained in further detail below.

[0411] At step (1602), the network apparatus (202) configures at least one configuration (for example, at least one filter) based on which the UE (102) reports temporary capability restrictions. For example, the filters may be adjusted based on criteria such as the bands supported by the UE, bands supported by the network, battery level of the UE (102), heat conditions, network optimization, and the like. For example, the filter may include a band filter, a band combination filter, and a frequency filter.The band filter allows the UE (102) to report the temporary capability restrictions for specific band(s). The band combination filter allows the UE (102) to report the temporary capability restrictions for specific band combination(s). The frequency filter allows the UE (102) to report the temporary capability restrictions for specific frequencies.

[0412] At step (1604), the network apparatus (202) generates a capability restriction message to be transmitted to a second network apparatus when the temporary capability restrictions of the UE (102) have been reported based on the filter(s) configured. The network apparatus (202) may correspond to the MN and the second network apparatus may correspond to the SN. The network apparatus (202) and the second network apparatus may be in communication using a new radio dual connectivity (NR-DC). The capability restriction message includes the temporary capability restrictions of the UE (102) reported along with the configured filter.

[0413] At step (1606), the network apparatus (202) transmits the capability restriction message to the second network apparatus.

[0414] For example, the temporary capability restrictions may include a　preference for secondary cells (SCells) to be released, serving cells of the UE (102) with a restricted capability, band(s) of the UE (102) with a restricted capability, band(s) of the UE (102) to be avoided for temporary capability restriction purposes, and so on. The capability restriction message enables the UE (102) to temporarily limit or deactivate particular features or capabilities in response to internal circumstances (for example, battery or thermal status) or network instructions (such as congestion control or policy enforcement). These limits are dynamically maintained to guarantee optimal performance and resource utilization for both the UE (102) and the network apparatus　(202).

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

Claims

1.A method for handling temporary capability restriction and removal in a 5G network, comprising:transmitting, by a user equipment (UE) (102), an informing message to a network apparatus (202), wherein the informing message indicates that the UE (102) has a temporary capability restriction;receiving, by the UE (102), a configuration for reporting the temporary capability restrictions;determining, by the UE (102), that the UE (102) does not have the temporary capability restriction to be reported based on the configuration from the network apparatus (202);generating, by the UE (102), a UE assistance information (UAI) message to be transmitted to the network apparatus (202) in response to determining that the UE (102) does not have temporary capability restriction; andtransmitting, by the UE (102), the UAI message to the network apparatus (202), wherein the UAI message is transmitted with an empty capability restriction that indicates a removal of the temporary capability restriction.2.The method of claim 1, wherein the temporary capability restriction is a multi-SIM (MUSIM) capability restriction, andwherein the informing message is included in at least one of a RRC setup complete message, a RRC resume complete message, and a RRC reestablishment complete message.3.A method for handling temporary capability restriction and removal in a 5G network, comprising:receiving, by a user equipment (UE) (102), a reconfiguration with sync message from a network apparatus (202);determining, by the UE (102), whether the UE (102) has initiated a transmission of a UE assistance information (UAI) message requesting for a temporary capability restriction before receiving the reconfiguration with sync message within a fixed time;starting, by the UE (102), a multi-SIM (MUSIM) wait timer associated with the UE (102); orrestarting, by the UE (102), the MUSIM wait timer associated with the UE (102);wherein a timer value of the MUSIM wait timer is set to a value present in a MUSIM capability restriction configuration when the MUSIM wait timer is started or restarted, andwherein the fixed time is 1 second.4.The method of claim 3, comprising:receiving, by the UE (102), a radio resource control (RRC) reconfiguration message from the network apparatus (202);determining, by the UE (102), whether the RRC reconfiguration message is applied due to at least ne of a conditional reconfiguration execution and a lower-layer triggered motility (LTM) cell switch procedure, and whether the UE (102) has initiated the transmission of the UAI message requesting for the temporary capability restriction;starting, by the UE (102), the MUSIM wait timer associated with the UE (102); orrestarting, by the UE (102), the MUSIM wait timer associated with the UE (102);wherein the timer value of the MUSIM wait timer is set to the value present in a MUSIM capability restriction configuration.5.The method of claim 4, comprising:retransmitting, by the UE (102), the UAI message to the network apparatus (202) to request for the temporary capability restriction.6.A method for handling temporary capability restriction and removal in a 5G network, comprising:configuring, by a network apparatus (202), at least one configuration for a user equipment (UE) (102) to reports the temporary capability restrictions, wherein the configuration comprises at least one filter;generating, by the network apparatus (202), a capability restriction message to be transmitted to a second network apparatus, wherein the capability restriction message includes at least one of the temporary capability restrictions reported by the UE (102) and the at least one filter configured; andtransmitting, by the network apparatus (202), the capability restriction message to the second network apparatus7.The method of claim 6, wherein the at least one filter includes a band filter, a band combination filter, and a frequency filter, wherein the temporary capability restrictions include a preference of the UE (102) on secondary cells (SCells) to be released, serving cells of the UE (102) having a restricted capability, at least one band of the UE (102) having a restricted capability, and at least one band of the UE (102) to be avoided for temporary capabilities restriction purposes, andwherein the network apparatus (202) is a master node (MN) and the second network apparatus is a secondary node (SN), and wherein the network apparatus (202) and the second network apparatus are in communication using a new radio dual connectivity (NR-DC).8.A user equipment (UE) (102) for handling temporary capability restriction and removal in a 5G network, comprising:a memory (106);a processor (104) coupled to the memory (106); anda first controller (110) communicatively coupled to the memory (106) and the processor (104), wherein the first controller (110):transmits an informing message to a network apparatus (202), wherein the informing message indicates that the UE (102) has a temporary capability restriction;receiving a configuration for reporting the temporary capability restrictions;determines that the UE (102) does not have the temporary capability restriction to be reported based on the configuration from the network apparatus (202);generates a UE assistance information (UAI) message to be transmitted to the network apparatus (202), wherein the UAI message is transmitted with an empty capability restriction that indicates a removal of the temporary capability restriction; andtransmits the UAI message to the network apparatus (202), wherein the UAI message is transmitted with an empty capability restriction that indicates a removal of the temporary capability restriction.9.The UE (102) of claim 8, wherein the temporary capability restriction is a multi-SIM (MUSIM) capability restriction, andwherein the informing message is included in at least one of a RRC setup complete message, a RRC resume complete message, and a RRC reestablishment complete message.10.The UE (102) of claim 8, wherein the first controller (110):receives a reconfiguration with sync message from the network apparatus (202);determines whether the UE (102) has initiated a transmission of a UE assistance information (UAI) message requesting for a temporary capability restriction before receiving the reconfiguration with sync message within a fixed time; andstarts a multi-SIM (MUSIM) wait timer associated with the UE (102); orrestarts the MUSIM wait timer associated with the UE (102), wherein a timer value of the MUSIM wait timer is set to a value present in a MUSIM capability restriction configuration when the MUSIM wait timer is started or restarted,wherein the fixed time is 1 second.11.The UE (102) of claim 9, wherein the first controller (110):receives a radio resource control (RRC) reconfiguration message from the network apparatus (202);determines whether the RRC reconfiguration message is applied due to at least one of a conditional reconfiguration execution and a lower-layer triggered motility (LTM) cell switch procedure, and whether the UE (102) has initiated the transmission of the UAI message requesting for the temporary capability restriction; andstarts the MUSIM wait timer associated with the UE (102); orrestarts the MUSIM wait timer associated with the UE (102), wherein the timer value of the MUSIM wait timer is set to the value present in a MUSIM capability restriction configuration.12.The UE (102) of claim 10, wherein the first controller:retransmits the UAI message to the network apparatus (202) to request for the temporary capability restriction.13.A network apparatus (202) for handling temporary capability restriction and removal in a 5G network, comprising:a memory (106);a processor (104) coupled to the memory (106); anda second controller (204) communicatively coupled to the memory (106) and the processor (104), wherein the second controller (204):configures at least one configuration for a user equipment (UE) (102) to report the temporary capability restrictions, wherein the configuration comprises at least one filter;generates a capability restriction message to be transmitted to a second network apparatus, wherein the capability restriction message includes at least one of the temporary capability restrictions reported by the UE (102) and the at least one filter configured; andtransmits the capability restriction message to the second network apparatus.14.The network apparatus (202) of claim 13, wherein the at least one filter includes a band filter, a band combination filter, and a frequency filter.15.The network apparatus (202) of claim 19, wherein the temporary capability restrictions include a preference of the UE (102) on secondary cells (SCells) to be released, serving cells of the UE (102) having a restricted capability, at least one band of the UE (102) having a restricted capability, and at least one band of the UE (102) to be avoided for temporary capabilities restriction purposes, andwherein the network apparatus (202) is a master node (MN) and the second network apparatus is a secondary node (SN), and wherein the network apparatus (202) and the second network apparatus are in communication using a new radio dual connectivity (NR-DC).

Images