Apparatus and method for handling user equipment capability framework in a wireless communication system

Abstract

The present disclosure relates to a 5G communication system or a 6G communication system for supporting higher data rates beyond a 4G communication system such as long term evolution (LTE). Disclosed a system (1800) and a method (1600) of handling Multi Radio Access Technology (multi-RAT) -Dual Connectivity (MR-DC) filter for User Equipment (UE) Capability Enquiry (UCE) in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2). The method includes generating a combined MR-DC filter for a MN RAT container by a logical OR operation of a first MR-DC filter and a second MR-DC filter. The first MR-DC filter is for the SN1 and one or more MN-SN1 RAT containers. Further, the second MR-DC filter is for the SN2 and one or more MN-SN2 RAT containers.

Description

APPARATUS AND METHOD FOR HANDLING USER EQUIPMENT CAPABILITY FRAMEWORK IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present invention generally relates to wireless communication networks, and more specifically, relates to a system and a method for handling User Equipment (UE) capability negotiation framework aspects in a Sixth Generation (6G) architecture.

[0002] Considering the development of wireless communication from generation to generation, the technologies have been developed mainly for services targeting humans, such as voice calls, multimedia services, and data services. Following the commercialization of 5G (5th generation) communication systems, it is expected that the number of connected devices will exponentially grow. Increasingly, these will be connected to communication networks. Examples of connected things may include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machines, and factory equipment. Mobile devices are expected to evolve in various form-factors, such as augmented reality glasses, virtual reality headsets, and hologram devices. In order to provide various services by connecting hundreds of billions of devices and things in the 6G (6th generation) era, there have been ongoing efforts to develop improved 6G communication systems. For these reasons, 6G communication systems are referred to as beyond-5G systems.

[0003] 6G communication systems, which are expected to be commercialized around 2030, will have a peak data rate of tera (1,000 giga)-level bit per second (bps) and a radio latency less than 100μsec, and thus will be 50 times as fast as 5G communication systems and have the 1 / 10 radio latency thereof.

[0004] In order to accomplish such a high data rate and an ultra-low latency, it has been considered to implement 6G communication systems in a terahertz (THz) band (for example, 95 gigahertz (GHz) to 3THz bands). It is expected that, due to severer path loss and atmospheric absorption in the terahertz bands than those in mmWave bands introduced in 5G, technologies capable of securing the signal transmission distance (that is, coverage) will become more crucial. It is necessary to develop, as major technologies for securing the coverage, Radio Frequency (RF) elements, antennas, novel waveforms having a better coverage than Orthogonal Frequency Division Multiplexing (OFDM), beamforming and massive Multiple-input Multiple-Output (MIMO), Full Dimensional MIMO (FD-MIMO), array antennas, and multiantenna transmission technologies such as large-scale antennas. In addition, there has been ongoing discussion on new technologies for improving the coverage of terahertz-band signals, such as metamaterial-based lenses and antennas, Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS).

[0005] Moreover, in order to improve the spectral efficiency and the overall network performances, the following technologies have been developed for 6G communication systems: a full-duplex technology for enabling an uplink transmission and a downlink transmission to simultaneously use the same frequency resource at the same time; a network technology for utilizing satellites, High-Altitude Platform Stations (HAPS), and the like in an integrated manner; an improved network structure for supporting mobile base stations and the like and enabling network operation optimization and automation and the like; a dynamic spectrum sharing technology via collision avoidance based on a prediction of spectrum usage; an use of Artificial Intelligence (AI) in wireless communication for improvement of overall network operation by utilizing AI from a designing phase for developing 6G and internalizing end-to-end AI support functions; and a next-generation distributed computing technology for overcoming the limit of UE computing ability through reachable super-high-performance communication and computing resources (such as Mobile Edge Computing (MEC), clouds, and the like) over the network. In addition, through designing new protocols to be used in 6G communication systems, developing mechanisms for implementing a hardware-based security environment and safe use of data, and developing technologies for maintaining privacy, attempts to strengthen the connectivity between devices, optimize the network, promote softwarization of network entities, and increase the openness of wireless communications are continuing.

[0006] It is expected that research and development of 6G communication systems in hyper-connectivity, including person to machine (P2M) as well as machine to machine (M2M), will allow the next hyper-connected experience. Particularly, it is expected that services such as truly immersive eXtended Reality (XR), high-fidelity mobile hologram, and digital replica could be provided through 6G communication systems. In addition, services such as remote surgery for security and reliability enhancement, industrial automation, and emergency response will be provided through the 6G communication system such that the technologies could be applied in various fields such as industry, medical care, automobiles, and home appliances.

[0007] According to an aspect of an exemplary embodiment, there is provided a communication method in a wireless communication.

[0008] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the disclosure. This summary is neither intended to identify key or essential inventive concepts of the disclosure nor is it intended for determining the scope of the disclosure.

[0009] In an embodiment, the present disclosure discloses a method of handling Multi Radio Access Technology (multi-RAT) -Dual Connectivity (MR-DC) filter for User Equipment (UE) Capability Enquiry (UCE) in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2). The method includes generating a combined MR-DC filter for a MN RAT container by a logical OR operation of a first MR-DC filter and a second MR-DC filter. The first MR-DC filter is for the SN1 and one or more MN-SN1 RAT containers. The second MR-DC filter is for the SN2 and one or more MN-SN2 RAT containers.

[0010] In another embodiment, the present disclosure discloses a method of handling User Equipment (UE) Capability framework aspect in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2). The method includes defining a database containing a plurality of combinations of rf featureSets. Each combination of the rf featureSets is stored as a definition in the database. Each definition is mapped to a unique pre-defined identifier. The unique pre-defined identifier is an index value based on max possible number of combinations of the rf featureSets. The method also includes storing the database at a User Equipment (UE) and the MN.

[0011] In another embodiment, the present disclosure discloses an apparatus for handling Multi Radio Access Technology (multi-RAT) -Dual Connectivity (MR-DC) filter for User Equipment (UE) Capability Enquiry (UCE) in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2). The apparatus includes at least one processor configured to generate a combined MR-DC filter for a MN RAT container by a logical OR operation of a first MR-DC filter and a second MR-DC filter. The first MR-DC filter is for the SN1 and one or more MN-SN1 RAT containers. The second MR-DC filter is for the SN2 and one or more MN-SN2 RAT containers.

[0012] In another embodiment, the present disclosure discloses an apparatus for handling User Equipment (UE) Capability framework aspects in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2). The apparatus includes at least one processor configured to define a database containing a plurality of combinations of RF featureSets. Each combination of the RF featureSets is stored as a definition in the database. Each definition is mapped to a unique pre-defined identifier. The unique pre-defined identifier is an index value based on maximum possible number of combinations of the rf featureSets.

[0013] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the disclosure and are therefore not to be considered limiting of its scope. The disclosure will be described and explained with additional specificity and detail with the accompanying drawings.

[0014] Aspects of the present disclosure provide efficient communication methods in a wireless communication system.

[0015] These and other features, aspects, and advantages of the present disclosure will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:

[0016] FIG. 1 illustrates non-standalone (NSA) architecture 'option 3' and 'option 4' in 5G specification, according to an existing technique;

[0017] FIG. 2A illustrates an architecture option to leverage existing LTE RAN and core network along with ENDC infrastructure and deploy 6G RAN, according to an existing technique;

[0018] FIG. 2B illustrates another architecture option to leverage the existing 5GC (core) and RAN with the LTE RAN in NE-DC deployment and further 6G RAN is deployed as a secondary RAT, according to an existing technique;

[0019] FIG. 3 illustrates a sequence flow diagram for a method of sharing a UE's Capability Information (UCI) with an LTE MN, according to an existing technique;

[0020] FIG. 4 illustrates a sequence flow diagram for a method of sharing a UE's Capability Information (UCI) with an NR MN, according to an existing technique;

[0021] FIG. 5 illustrates a sequence flow diagram depicting UE's capability enquiry using a MRDCfilter1 and a MRDCfilter2, according to an existing technique;

[0022] FIG. 6 illustrates a diagram depicting the content of a UE capability information (UCI) message, according to an existing technique;

[0023] FIG. 7 illustrates a generation of a combined MRDCfilter3 at a network entity, according to an embodiment of the present disclosure;

[0024] FIG. 8A illustrates a sequence diagram depicting a method for UE capability enquiry using a single UCE message by an LTE MN, in accordance with an embodiment of the present disclosure;

[0025] FIG. 8B illustrates a RAT-type corresponding to a MRDC filter mapping for each RAT type to generate the UCI message, in accordance with an embodiment of the present disclosure;

[0026] FIG. 9 illustrates a sequence diagram of a method for UE capability enquiry using MRDCfilter1, MRDCfilter2, and MRDCfilter3 in a single UCE message by an NR MN, in accordance with an embodiment of the present disclosure;

[0027] FIG. 10 illustrates a sequence flow diagram depicting a method for UE capability enquiry using MRDCfilter1, MRDCfilter2, and MRDCfilter3 by an LTE MN, in accordance with an embodiment of the present disclosure;

[0028] FIG. 11 illustrates a sequence flow diagram depicting a method for UE capability enquiry using MRDCfilter1, MRDCfilter2, and MRDCfilter3 by an NR MN, in accordance with an embodiment of the present disclosure;

[0029] FIG. 12 illustrates a set of information element containers which are of large size and are repetitive in the UE capability information message, in accordance with an embodiment of the present disclosure;

[0030] FIG. 13 illustrates an example of 'a proposed database' containing all possible featureSetDL definitions per CC mapped to 'proposed identifiers', in accordance with an embodiment of the present disclosure;

[0031] FIG. 14 illustrates an example of the UCI message in the LTE or the NR with 6G NSA using database-mapped identifiers, in accordance with an embodiment of the present disclosure;

[0032] FIG. 15 illustrates a flow chart of a method for size-optimized UE capability negotiation, in accordance with an embodiment of the present disclosure;

[0033] FIG. 16 illustrates a flow chart of a method of handling Multi RAT-Dual Connectivity (MR-DC) filter for UE Capability Enquiry (UCE) in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2), according to an embodiment of the present disclosure;

[0034] FIG. 17 illustrates a flow chart of a method for handling the UE Capability framework aspect in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2), according to an embodiment of the present disclosure; and

[0035] FIG. 18 illustrates an example diagram of an apparatus, according to embodiments of the present disclosure.

[0036] FIG. 19 illustrates an example diagram of a user equipment, according to embodiments of the present disclosure.

[0037] FIG. 20 illustrates an example diagram of a base station, according to embodiments of the present disclosure.

[0038] Further, skilled artisans will appreciate that those elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0039] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the disclosure and are not intended to be restrictive thereof.

[0040] Reference throughout this specification to "an aspect", "another aspect" or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0041] The terms "comprises", "comprising", "includes", "comprise", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method.

[0042] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skilled in the art to which this disclosure belongs. The system, method, and examples provided herein are illustrative only and not intended to be limiting.

[0043] In one or more embodiments, the present disclosure discloses the system and method for handling the UE capability negotiation framework aspects for the 6G, including 'UE capability enquiry' related enhancements for Multi-RAT Dual-Connectivity (MRDC) filter handling as well as 'UE capability information' size reduction for efficient radio resource utilization and reduced signalling overhead. The present disclosure relates to the initial 6G deployment as the Non standalone Architecture (NSA), where existing Radio Access Technologies (RATs) such as the 4G (LTE) or the 5G (NR) act as the MN and the 6G deployed as the SN. But the present disclosures do not confine the solution to 6G NSA only and can be easily extendable to 6G standalone deployments in future as well.

[0044] Embodiments of the present invention will be described below in detail with reference to the accompanying drawings.

[0045] In the current 3GPP standard specification, 37.340, for the MRDC, a UE capability information message has multiple information containers."In (NG) ENDC and the NE-DC, the capabilities of the UE-supporting MRDC are carried by different capability containers. Some MRDC-related capabilities are in the MRDC container e.g. MRDC band combinations, while other MRDC-related capabilities are contained in the E-UTRA and NR capability container."In general, MRDC capabilities shall be carried in the MN, the SN and the MRDC (common container for MN-SN capabilities) containers. But all these information containers of the UE Capability Information (UCI) message are created using a common / same MRDC filter which is provided in the UE Capability Enquiry (UCE) message by the network (NW).

[0046] Accordingly, as per 3GPP,"when retrieving MRDC-related capabilities, the MN shall provide an MRDC filter that affects the MRDC-related capabilities in the MRDC, the E-UTRA and the NR capability containers. When using different UE capability enquiry messages to retrieve the different containers, the MN shall employ the same MRDC filter in all enquiry messages."Therefore, a common MRDC filter shall be provided by the NW for all the affected containers of the MN, the SN and their MRDC enquiry containers.

[0047] Wireless technology has been continuously evolving over the years to provide for the growing demand for services and requirements of end users. The earliest generation called a Second-Generation (2G) wireless communication provided mobility and voice services, while a Third-Generation (3G) wireless communication provided voice and data services. Further, there was an evolution to a Fourth-Generation (4G) wireless communication for meeting the growing demand for high-speed data. Furthermore, newer use cases like enhanced Mobile Broad Band (eMBB), Ultra Reliable Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC) paved the way for the next generation of the wireless communication, a Fifth-Generation (5G) wireless communication.

[0048] As part of a Non-Standalone (NSA) architecture design in the 3rd Generation Partnership Project (3GPP), multiple NSA architecture options have been defined in the specifications for the 5G.Figure 1illustrates the architecture 'option 3' and 'option 4' in the 5G specification, according to an existing technique. The multiple NSA architectures 100 include E-UTRA New Radio (NR) - Dual Connectivity (ENDC) as the 'option 3' where an anchor node is the 'Long Term Evolution (LTE) radio access network (RAN) with Evolved Packet Core (EPC)'. Further, the LTE is a Master Node (MN), and NR is added as a secondary node (SN). In 'option 4', called NR-EUTRA Dual Connectivity (NE-DC), the anchor is the 'NR RAN with NR core' wherein the NR is the master node, and the LTE is added as the SN.

[0049] In the above-mentioned NSA architecture, the UE must report the UE capability for all Radio Access Technology (RATs) and for the Evolved Universal Terrestrial Radio Access- New Radio (EUTRA-NR) or NR-EUTRA wherever applicable. As a result, an overall size of the UE capability information is huge, and several features and optimizations were required in the 5G to handle the UE capability information.

[0050] Further, with reference to 6G communication, an initial deployment may follow a similar trend as was in the NR case i.e. NSA architecture with the NR or the LTE as the MN while supporting the 6G as the SN in a dual connectivity (DC) manner.

[0051] In particular, it may be considered that network operators would be inclined to leverage their existing network infrastructure and in order to provide a faster 6G experience to the users, may choose to deploy 6G RAN together with existing 4G and 5G infrastructure.

[0052] Figure 2Aillustrates an architecture option to leverage existing LTE RAN and core network along with ENDC infrastructure and deploy 6G RAN.Figure 2Billustrates another architecture option to leverage the existing 5GC (core) and RAN with the LTE RAN in NE-DC deployment and a further 6G RAN is deployed as a secondary RAT.

[0053] In such infrastructures, multiple RAT deployments are possible and correspondingly the UE's capability information needs to capture associated information for all the RATs. Therefore, the existing problem of UE's capability information size which already exists in the NR specifications is further increased due to the existence of the multiple RAT simultaneously in the deployments.

[0054] Hence, there is a need to provide systems and methods that can overcome the above-discussed problems.

[0055] As per the deployment architectures shown in FIG.2a and FIG.2b, with the introduction of the 6G as a third RAT, a supporting MN may enquire the UE for more than one MRDC-supported RAT capability containers.

[0056] FIG. 3illustrates a sequence flow diagram for a method 300 of sharing a UE's capability information (UCI) with an LTE MN 301, according to an existing technique. The method 300 may involve a sequence of operations between the LTE MN 301 and a UE 307. The LTM MN 301 may be implemented in communication with a MRDC SN1 303 corresponding to the 6G network and a MRDC SN2 305 corresponding to the NR network. The MN may correspond to the LTE network, therefore referred to as the MN LTE 301.

[0057] Referring to FIG.3, at operation 302, the LTE MN 301 may enquire the UE 307 about both the 6G and the NR-related MRDC capabilities which may involve a plurality of sets of RAT containers. In one embodiment, the UE capabilities may involve at least five sets of RAT containers. Moreover, the LTE MN 301 may enquire about the UE's capabilities by transmitting a UE Capability Enquiry (UCE) message to the UE 307. The UE's capability may be MRDC RAT type container and related capabilities such as, but are limited to, EUTRA, 6G, EUTRA-6G, NR, and EUTRA-NR. At operation 304, in response to the received UCE message from the LTE MN 301, the UE 307 may transmit the UCI to the MN LTE 301.

[0058] FIG. 4 illustrates a sequence flow diagram for a method 300 of sharing a UE's capability information (UCI) with an NR MN 401, according to an existing technique. The method 400 may involve a sequence of operations between the NR MN 401 and a UE 407. The NR MN 401 may be implemented in communication with a MRDC SN1 403 corresponding to a 6G network and a MRDC SN2 405 corresponding to the LTE network. The MN may correspond to the NR network, therefore referred to as the NR MN 401.

[0059] Similar to operation 302, at operation 402, the NR MN 401 may enquire the UE 407 about both the 6G and the LTE-related MRDC capabilities which may involve a plurality of sets of RAT containers via a UCE message. In one embodiment, the request includes at least five sets of RAT containers for UE Capability Enquiry purpose. The at least five sets of RAT containers may include, but are not limited to, NR, 6G, NR-6G, EUTRA, and EUTRA-NR. At operation 404, in response to the received UCE message from the NR MN 401, the UE 407 may transmit the UCI to the MN LTE 301.

[0060] Further, using the current 3GPP specification methods for the 6G UCE framework, one possible way to implement the UCE with the same MRDC filters is shown below:

[0061] -1st UCE forEUTRAcontainer for MRDC1 (LTE-6G-DC),

[0062] -2nd UCE for6G&EUTRA-6Gfor MRDC1 (can be again split into two UCEs),

[0063] -3rd UCE forEUTRAcontainer for MRDC2 (ENDC), and

[0064] -4th UCE forNR&EUTRA-NRfor MRDC2 (can be again split into two UCEs).

[0065] In the current 3GPP specification method, there are 4 UCE messages that are sent with belowMRDCfilter1andMRDCfilter2according to current 3GPP specifications.

[0066] FIG. 5illustrates a sequence flow diagram depicting a method 500 for UE's capability enquiry using a MRDCfilter1 and a MRDCfilter2, according to an existing technique. As shown in FIG.5, at operation 1, the network (i.e., MN LTE 501) enquires EUTRA capability using theMRDCfilter1. This applies toEUTRA, 6G and EUTRA-6Gcontainers. In response, the MN LTE 501 may receive the UCI from a UE 507.

[0067] Further, at operation 2, the network (i.e., the MN LTE 501) enquires the UE's capability (i.e., the6G, EUTRA-6Gcapability using the sameMRDCfilter1).This applies toEUTRA, 6G and EUTRA-6Gcontainers. In response, the MN LTE 501 may receive the UCI from a UE 507.

[0068] Next, at operation 3, the network (i.e., the MN LTE 501) enquires EUTRA capability using theMRDCfilter2, applicable toEUTRA, NR, and EUTRA-NRcontainers. In response, the MN LTE 501 may receive the UCI from a UE 507.

[0069] Further, at operation 4, the network (i.e., the MN LTE 501) enquiring NR, EUTRA-NR capability using the sameMRDCfilter2,applicable toEUTRA, NR, and EUTRA-NRcontainers. In response, the MN LTE 501 may receive the UCI from a UE 507.

[0070] However, in the current 3GPP approach for 'UCE' of the 6G NSA system: there exist at least the below problems:

[0071] -At least 4 sets of layer3 / RRC signalling messages are required just to exchange the UCI.

[0072] -At least 2 times processing ofEUTRA(MN) capabilities corresponding to each MRDC set is required to be prepared and sent.

[0073] -Such an approach leads to signalling overhead and increased latency during initial device camping in the cell. Also, the same problems are applicable to scenarios where the NR is the MN node.

[0074] In one or more embodiments, in ENDC and MRDC, the UCI size is majorly dominated by the following 3 features:

[0075] -rf-features

[0076] -featureSetCombinations

[0077] -featureSets(for downlink (DL) and uplink (UL)).

[0078] FIG. 6illustrates a diagram depicting the content of a UE capability information (UCI) message 600. The UE capability information message 600 mainly includes:

[0079] -Radio Frequency (RF) / Physical layer information associated to:

[0080] --each band of a RAT,

[0081] --Carrier Aggregation (CA) combinations of a RAT,

[0082] --MRDC combinations are supported for the RAT pair under query.

[0083] -These set of rf / physical layer information are standard / 3GPP supported valueslike:

[0084] --bandwidth information,

[0085] --bandwidth (for single carrier),

[0086] --bandwidth combination (for carrier aggregation),

[0087] --multiple input multiple output (MIMO), sub-carrier spacing, numerology, quadrature amplitude modulation (QAM) support etc.

[0088] As shown in FIG. 6, UCI contents include various kinds of radio frequency (RF) parameters that are repetitive and defined in various combination(s) per band, per carrier aggregation (CA) combination, per MRDC combination, as per UE chipset support.

[0089] Several solution(s) and features have been discussed in 3GPP standards to reduce the UE capability size for both the LTE and the NR including below, such as:

[0090] -requestedMaxCCsDL / UL, skipFallbackCombinations, requestReducedFormatetc. in LTE

[0091] -Radio Capability Signalling Optimization (RACS)in rel.16 including UE radio capability ID mapping and transfer on non-access stratum (NAS)

[0092] -RRCsegmentationfor transferring large-sized UCI messages etc.

[0093] However, the current 3GPP approach for 'UCI' of a 6G NSA system says, "If the UE cannot include all feature sets and feature set combinations due to message size or list size constraints, it is up to UE implementation which feature sets and feature set combinations it prioritizes."

[0094] Furthermore, despite the above mentioned multiple features to manage the UE radio capability message size, it is expected to increase further manifolds with multiple RATs under enquiry like the LTE, the NR and the 6G with the NSA architecture deployment. Hence, there is a need to redesign the UCI message framework for 6G with efficiently reduced the UE capability size.

[0095] In one or more embodiments, the present disclosure discloses the system and method for handling the UE capability negotiation framework aspects for the 6G deployment including the UCE and the UCI message framework for the two aforementioned embodiments of the problem statement.

[0096] The one or more embodiments disclose a technique of creating the MRDC filters which can be applied to both the architectures where the LTE is the MN as well as the NR is the MN.

[0097] Referring to FIG 5, it is seen that each set of the RAT containers requires a MRDC filter to be applied as provided in the UCE message. According to the current specifications of 3GPP, this MRDC filter needs to be the same for the same set of MRDC RAT containers. But this causes different filters to be applied on the same MN leading to multiple times processing of the same MN. For e.g., in FIG.5, two filters viz. MRDCfilter1 and MRDCfilter2 are applied on EUTRA MN causing EUTRA RAT to be processed twice. So, the present disclosure aims to solve the issue of 'multiple filters for the same MN' and 'reduce the number of signalling messages exchanged' for UCE and UCI.

[0098] FIG. 7illustrates a generation of a combined MRDCfilter3 704 at a network (NW) entity, in accordance with an embodiment of the present disclosure. In an embodiment, the combinedMRDCfilter3704 is generated at the NW entityas shown in FIG.7. Further, the generated combinedMRDCfilter3704 may be applied to the MN enquiry message only once. Further, theMRDCfilter3704 may be generated by a logical OR operation 703 of the MRDCfilter1 701 and MRDCfilter2 702.

[0099] The MRDCfilter3 704 may be a single MN RAT-specific filter, which is a subset of "MRDCfilter1 || MRDCfilter2", where a symbol "||" represents logical OR operation 703. Further, the MRDCfilter1 701 may be the filter network used on SN1 and MN-SN1 RAT containers. The MRDCfilter2 may be the filter network used on SN2 and MN-SN2 RAT containers. In the following specification, any reference to the combinedMRDCfilter3704 shall refer to the method 700 where combined values of the MRDC filter1 701 and the MRDCfilter2 702 are utilized.

[0100] FIG. 8Aillustrates a sequence diagram depicting a method 800 for UE capability enquiry using a single UCE message by an LTE MN 801, in accordance with an embodiment of the present disclosure. Further,FIG. 8Billustrates a RAT-type corresponding to a MRDC filter mapping for each RAT type to generate the UCI message, in accordance with an embodiment of the present disclosure. In an exemplary embodiment, FIGS. 8A-8B may correspond to MRDC multiple filter(s) mapping techniques (wherein, the MN corresponds to the LTE) for with a single UCE message transmission.

[0101] In one or more embodiments, the LTE MN 801 may enquire a UE 807 regarding corresponding MRDC capabilities in a single step via the UCE message. Specifically, at operation 802, the LTE MN 801 may enquire about all the five RAT type containers i.e. EUTRA, 6G, EUTRA-6G, NR, EUTRA-NR, in a single UCE message as shown in FIG.8A. In response, the UE 807 may transmit the UCI to the LTE MN 801. In response, at operation 804, the UE 807 may transmit the UCI to the LTE MN 801.

[0102] In one embodiment, to handle multiple MRDC filters for various RAT type containers, the LTE MN 801 may provide the UE 807 with a disclosed 'RAT-type to MRDC filter' mapping via a disclosed 'non-critical extension IE' in the UCE message as represented in FIG.8b, whereinMRDCfilter3is generated as discussed in the above paragraphs.

[0103] Further, in some embodiments, to aid the UE 807 to maintain a UCI size as per max Packet Data Convergence Protocol (PDCP) service data unit (SDU) size, the LTE MN 801 may include a "rrc-SegAllowed" IE in the UCE message transmitted at the operation 802. The UE 807 may then apply the disclosed 'RAT-type to MRDC filter' mapping for each RAT type and prepare the UCI message accordingly. As illustrated in FIG.8B, the UE Capability Enquiry (or UE capability request) may include all the RATs including EUTRA, 6G, EUTRA-6G, NR, and EUTRA-NR. Further, a non-critical extension in the UCE message may include a sequence of numbers which are indices mapped to the corresponding filter type. Further in the non-critical extension IE, below the sequence of indices, actual filter values may be listed where the first entry which is MRDCfilter1-rXY maps to index 1 and so on. In an embodiment, each of the RAT may use the in-sequence indexed numbers to check the MRDC filter value to apply on that specific RAT container.

[0104] -In a non-limiting example,

[0105] --EUTRARAT maps to index 3 and shall apply correspondingMRDCfilter3-rXY,

[0106] --6GRAT maps to index 1 and shall apply correspondingMRDCfilter1-rXY,

[0107] --EUTRA-6GRAT maps to index 1 and shall apply correspondingMRDCfilter1-rXY,

[0108] --NRRAT maps to index 2 and shall apply correspondingMRDCfilter2-rXY,

[0109] --EUTRA-NRRAT maps to index 2 and shall apply correspondingMRDCfilter2-rXY.

[0110] FIG. 9illustrates a sequence diagram of a method 900 for UE capability enquiry using MRDCfilter1, MRDCfilter2, and MRDCfilter3 in a single UCE message by an NR MN, in accordance with an embodiment of the present disclosure.In an exemplary embodiment, FIG. 9 may correspond to a MRDC multiple filter(s) mapping technique (where MN corresponds to NR) for allowing single UCE message transmission.

[0111] In one or more embodiments, the NR MN 901 may enquire the UE 907 about the corresponding MRDC capabilities in a single step via a UCE message. Specifically, at operation 902, the NR MN 901 may enquire about all the five RAT type containers i.e. NR, 6G, NR-6G, EUTRA, EUTRA-NR, in a single UCE message. In response, at operation 904, the UE 907 may transmit the UCI to the NR MN 901.

[0112] In one or more embodiments, to handle multiple MRDC filters for various RAT type containers, the NR MN 901 may introduce 'new filter categories' incapabilityRequestFilterIE 'per RAT type' in the UCE message as shown at operation 902. TheMRDCfilter3is generated as discussed in the previous paragraphs, specifically in reference to FIG. 7.

[0113] Further, to aid the UE 907 to maintain a UCI size as per max PDCP SDU size, the NR MN 901 may include a "rrc-SegAllowed" IE (from spec) in the UCE message transmitted to the UE 907 at operation 902. Thereafter, the UE 907 may apply the introduced MRDC filters mapped, one to one, for each RAT type and prepare the UCI message accordingly, for transmission at the operation 904.

[0114] -In a non-limiting example,

[0115] --NRRAT shall apply mappedMRDCfiler3,

[0116] --6GRAT shall apply mappedMRDCfiler1,

[0117] --NR-6GRAT shall apply mappedMRDCfiler1,

[0118] --EUTRARAT shall apply mappedMRDCfiler2,

[0119] --EUTRA-NRRAT shall apply mappedMRDCfiler2.

[0120] FIG. 10illustrates a sequence flow diagram depicting a method 1000 for UE capability enquiry using MRDCfilter1, MRDCfilter2, and MRDCfilter3 by an LTE MN 1001, in accordance with an embodiment of the present disclosure.In an exemplary embodiment, FIG. 10 may correspond to a combined MRDC filter method for allowing 3 steps UCE message transmission (wherein, the MN corresponds to the LTE).

[0121] In one or more embodiments, the LTE MN 1001 may enquire a UE 1007 regarding corresponding MRDC capabilities in at least 3 steps as shown in FIG.10.

[0122] -At step 1, the LTE MN 1001 may enquire EUTRA capabilities, related to the 6G network and NR in DC, using the MRDCfilter3.

[0123] --This reduces an additional step for EUTRA capability enquiry due to the presence of at least two MRDC filters.

[0124] In response, the UE 1007 may transmit the UCI to the LTE MN 1001.

[0125] -At step 2, the LTE MN 1001 may enquire the 6G and EUTRA-6G capabilities, related to 6G in DC, using an associated MRDCfilter1 and the UE 1007 may apply the same while forming the UCI.

[0126] --In one embodiment, the LTE MN 1001 may decide to further split 6G and EUTRA-6G enquiries into two separate UCE messages.

[0127] In response, the UE 1007 may transmit the UCI to the LTE MN 1001.

[0128] -At step 3, the LTE MN 1001 may enquire about NR and EUTRA-NR capabilities, related to ENDC, using an associated MRDCfilter2 and the UE 1007 may apply the associated MRDCfilter2 while forming the UCI.

[0129] --In one embodiment, the LTE MN 1001 may decide to further split NR and EUTRA-NR enquiries into two separate UCE messages.

[0130] In response, the UE 1007 may transmit the UCI to the LTE MN 1001.

[0131] -In one embodiment, to aid the UE 1007 to maintain a UCI size as per max PDCP SDU size, the LTE MN 1001 may decide to include a "rrc-SegAllowed" IE (from spec) at any and all UCE messages.

[0132] FIG. 11illustrates a sequence flow diagram depicting a method 1100 for the UE capability enquiry using MRDCfilter1, MRDCfilter2, and MRDCfilter3 by an NR MN 1101, in accordance with an embodiment of the present disclosure.In an exemplary embodiment, the method 1100 may correspond to a combined MRDC filter method for allowing 3 steps UCE message transmission (wherein, the MN corresponds to the NR).

[0133] In the illustrated embodiment of FIG. 11, the NR MN 1101 may enquire a UE 1107 regarding corresponding MRDC capabilities in at least 3 steps.

[0134] -At step 1, the NR MN 1101 may enquire NR capabilities, related to 6G and LTE in DC, using the MRDCfilter3 and the UE 1107 may apply the same while forming the UCI. Accordingly, the UE 1107 may respond with the UCI.

[0135] --In one embodiment, the MRDCfilter3 may be derived as discussed in the above paragraphs, specifically in reference to FIG. 7.

[0136] --This reduces an additional step for NR capability enquiry due to the presence of at least two MRDC filters.

[0137] -At step 2, the NR MN 1101 may enquire 6G and NR-6G capabilities, related to 6G in DC, using an associated MRDCfilter1 and the UE 1107 may apply the same while forming the UCI. Accordingly, the UE 1107 may respond with the UCI.

[0138] --In an embodiment, the NR MN 1101 may decide to further split 6G and NR-6G enquiries into two separate UCE messages.

[0139] -At step 3, the NR MN 1101 may enquire EUTRA and EUTRA-NR capabilities, related to (NG)ENDC / NEDC, using an associated MRDCfilter2 and the UE 1107 may apply the same while forming UCI. Accordingly, the UE 1107 may respond with the UCI.

[0140] --In an embodiment, the NR MN 1101 may decide to further split EUTRA and EUTRA-NR enquiries into two separate UCE messages.

[0141] -In some embodiments, to aid the UE 1107 to maintain UCI size as per max PDCP SDU size, the NR MN 1101 may decide to include a "rrc-SegAllowed" IE (from spec) at any and all UCE messages.

[0142] Further, when introducing multiple RAT(s) as part of MRDC, including 6G as NSA, the below spec section ofLTE RRC spec 36.331may be changed to incorporate the disclosed 'MRDCfilter mapping per RAT-Type' methods given in the FIG. 8B. The below illustrates reflects change to theLTE RRC spec 36.331for LTE as MN.

[0143]

[0144] For NR as MN, when introducing multiple RAT(s) as part of MRDC, including 6G as NSA, below spec section ofNR RRC spec 38.331may be changed as suggested to incorporate the disclosed 'MRDCfilter mapping per RAT-Type' methods as given in FIG. 9.

[0145]

[0146] Further, when introducing multiple RAT(s) as part of MRDC in spec 37.340, including 6G as NSA, below spec section(s) may be changed as suggested to incorporate the disclosed 'MRDCfilter mapping per RAT-Type' methods 800 and 900 as defined in FIG.8B and FIG. 9.

[0147]

[0148] FIG. 12illustrates a set of information element containers which are of large size and are repetitive in a UE capability information (UCI) message 1200, in accordance with an embodiment of the present disclosure.

[0149] In one or more embodiments, to reduce a size of the UCI message 1200 significantly, the present disclosure identifies 'three sets of information element containers' which are of large size and are repetitive in nature. For instance, the following set of IE containers may be identified based on:

[0150] -per band of a RAT,

[0151] -per band of each CA combination and

[0152] -per band of each MRDC combination.

[0153] Further, the identified set of information element (IE) containers may be defined as:

[0154] 1)RFfeatures per band of a RAT

[0155] -rf-Parameters{supportedBandListEUTRA{...

[0156] --as defined in 36.331, it is a list of LTE bands and corresponding rf features container.

[0157] -rf-Parameters{supportedBandListNR{...

[0158] --as defined in 38.331, it is a list of NR bands and corresponding rf features container.

[0159] -rf-Parameters{supportedBandList6G{...

[0160] --shall be defined for 6G and is a list of 6G bands and corresponding rf featurescontainer.

[0161] 2)FeatureSet per CA band combination of a RAT

[0162] -rf-Parameters{supportedBandCombinationList{bandList{...

[0163] --as defined in 3GPP, these are a list of CA (LTE-CA,NR-CA, shall include 6G-CA as well) band combinations, containing multiple possiblefeatureSets (set of parameters)in DL and UL for each component carrier of the RAT (EUTRA / NR / 6G).

[0164] 3)FeatureSet per MRDC band combination of a RAT pair

[0165] -rf-ParametersMRDC {supportedBandCombinationList {bandList {...

[0166] --as defined in 3GPP, these are a list of MRDC (NG)ENDC / NEDC, shall include LTE-6G-DC, NR-6G-DC) band combinations, containing multiple possiblefeatureSets (set of parameters)in DL and UL for each band of a RAT (EUTRA / NR / 6G).

[0167] Realizing rf featureSets as 'Database'mapped to proposed 'Indexes': FIG. 13illustrates an example of 'a proposed database' containing all possible featureSetDL definitions per CC mapped to 'proposed identifiers' ranging for max possible combination, in accordance with an embodiment of the present disclosure.

[0168] FIG. 13illustrates an example of 'a proposed database' containing all possible featureSetDL definitions per CC mapped to 'proposed identifiers', in accordance with an embodiment of the present disclosure. Referring to FIG.13,

[0169] -As a first step,a database may be definedcontaining all possible combinations of rffeature-sets(as per 3GPP supported values)

[0170] -Each of these combinations may then bestoredas a definitionin the proposed database.

[0171] -Each of these definitions may bemapped to unique pre-defined identifiers.

[0172] -Theseidentifiersmay be simple indexes based on a maximum possible number of combinations of such feature sets.

[0173] -This database may be known and pre-defined / saved at the UE (for instance, the UE 507, the UE 807, the UE 907, the UE 1007, and the UE 1107) as well as corresponding network side entities as shown in FIGS. 5 to 11.

[0174] -At the NW side, such database may be maintained in the CN within a UCMF kind of entity, or as a separate NW function, or at the RAN side.

[0175] -Theseidentifiersmay be standardized within 3GPP based on inputs from PLMN / NW defined and / or UE Vendor defined and agreed upon.

[0176] -FIG.13 shows a simplified example for,

[0177] --realizing thefeatureSetDLdefinitiondatabaseof DL features per CC for all possible combinations, and

[0178] --disclosed mappedidentifiers,

[0179] --herein, the combination contents such as Combination1 to Combination 2772 are saved in the proposed database, while identifiers ranging from 1 to 2772 are saved as mapped identifiers in both UE and the NW side (standardized).

[0180] --Similarly, featureSetUL and rf feature per CC database can be realized as well.

[0181] FIG. 14illustrates an example of the UCI message 1400 in the LTE or the NR with 6G NSA using database-mapped identifiers, in accordance with an embodiment of the present disclosure.

[0182] Referring to FIG.14, upon UE Capability Enquiry reception by the UE, the UE may prepare the UE Capability Information 1400 by includingthe disclosed Indexesfor featureSet combination(s) as per enquiredMRDCfilter, wherein:

[0183] -x identifier represents rf featureSet per band of a RAT,

[0184] -y1 / y2 represents DL / UL featureSet identifiers for band1 of the CA combo of a RAT,

[0185] -y3 / y4 represents DL / UL featureSet identifiers for band2 of the CA combo of same RAT and so on...

[0186] -z1 / z2 represents DL / UL featureSet identifiers for band1 of the MRDC combo of one RAT,

[0187] -z3 / z4 represents DL / UL featureSet identifiers for band2 of the MRDC combo of another RAT and so on.

[0188] -All above identifiers are integer indexes ranging from 1 to maximum possible combinations as supported in 3GPP for corresponding containers.

[0189] -All above identifiers are directly mapped to a set of featureSet definitions in DL and UL as illustrated in FIG.13 earlier.

[0190] While preparing the UCI message 1400, the UE may include the corresponding mappedidentifiersinstead of actual definitions for the respective DL / UL containers per Component Carrier (CC) (of the band, the CA, MRDC band combination(s)) by enquiring the same from the proposeddatabase(saved at the UE), as explained in reference to FIG. 13. The UE may thereby reduce the UCI size significantly. Upon receiving the UCI message 1400, the NW may use theidentifiersmentioned in the UCI message 1400 to reverse-query thedatabase(saved at the NW side as well) for actual container definitions, and then make further use of fetched definitions as per intended in 3GPP.

[0191] FIG. 15illustrates a flow chart of a method 1500 for size-optimized UE capability negotiation, in accordance with an embodiment of the present disclosure. FIG.15 represents an overall solution approach for UCI size optimization according to an exemplary embodiment of the present disclosure.

[0192] At step 1501: A UE receives a UE Capability Enquiry message from a NW entity containing MRDCfilter(s).

[0193] At step 1503: The UE may prepare the UE Capability Information message by fetchingidentifiersfor the featureSet(s) to include in UCI (instead of actual definitions).

[0194] At step 1505: The UE may include the fetchedidentifiersas part of a reduced size UCI message by querying the localdatabase.

[0195] At step 1507: The queried local database may be a standardized rf featureSet database implemented at the UE.

[0196] At step 1509: The UE may send the UCI to the NW entity and the NW entity may receive the UCI from the UE.

[0197] At step 1511: while decoding the UCI, the NW entity may perform reverse query (by usingidentifierssent by the UE) to the NW sidedatabaseentity for actual featureSet definitions of each rf container.

[0198] At step 1513: The queried database may be a standardized rf featureSet database implemented at the NW side.

[0199] At step 1515: After fetching the definitions from the stored database, the NW entity may proceed with further UE capability negotiation process as intended.

[0200] In one or more embodiments, the UE may correspond to any one of the UE 507, the UE 807, the UE 907, the UE 1007, or the UE 1107, as illustrated in FIGS. 5-11. Further, the network entity may correspond to any of the corresponding MN 501, the MN 801, the MN 901, the MN 1001, and the MN 1101.

[0201] FIG. 16illustrates a flow chart of a method 1600 of handling Multi RAT-Dual Connectivity (MR-DC) filter for UE Capability Enquiry (UCE) in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2), according to an embodiment of the present disclosure. The MN may correspond to any one of the MN 501, the MN 801, the MN 901, the MN 1001, and the MN 1101, as explained above.

[0202] At step 1601, the method 1600 may include generating a combined MR-DC filter for a MN RAT container by a logical OR operation of a first MR-DC filter and a second MR-DC filter. The first MR-DC filter may be for SN1 and MN-SN1 RAT containers and the second MR-DC filter may be for SN2 and MN-SN2 RAT containers.

[0203] At step 1603, the method 1600 may include generating a RAT container type to MR-DC filter mapping upon generation of the combined MR-DC filter.

[0204] Further, at step 1605, the method 1600 may include sending, by the MN to a User Equipment (UE), a UCE message to enquire UE's capability for each type of RAT containers. The UE may correspond to any one of the UE 507, the UE 807, the UE 907, the UE 1007, or the UE 1107, as explained above. The UCE message may include the RAT container type to MR-DC filter mapping that is via a non-critical extension Information Element (IE). In one embodiment, the non-critical extension IE may include a sequence of numbers which are indices mapped to the corresponding filter. Further, each of the RAT container types uses the in-sequence indexed numbers to determine the MR-DC filter value to apply on a specific RAT container.

[0205] At step 1607, the method 1600 may include providing, by the MN to the UE, a type of filter for each type of RAT containers via a capability request filter Information Element (IE). In one embodiment, the capability request filter IE includes a mapping information of RAT container type to MR-DC filter. In an embodiment, the method 1600 may include sending, by the MN to a User Equipment (UE), a first UCE message to enquire UE capability for the MN RAT container using the combined MR-DC filter. The method 1600 may also include sending, by the MN to the UE, a second UCE message to enquire the UE capability for the SN1 and MN-SN1 RAT containers using the first MR-DC filter. Moreover, the method 1600 may include sending, by the MN to the UE, a third UCE message to enquire the UE capability for the SN2 and MN-SN2 RAT containers using the second MR-DC filter. In some embodiments, the method 1600 may also include splitting, by the MN, the second UCE message and the third UCE message into two separate messages. Moreover, the method 1600 may also include adding, by the MN, a rrc-SegAllowed Information Element (IE) in the UCE messages to aid the UE to maintain UE Capability Information (UCI) message size based on a maximum Packet Data Convergence Protocol Service Data Unit (PDCP SDU) size.

[0206] At step 1609, the method 1600 may include receiving, by the UE from the MN, a UCE message to enquire UE's capability for each type of RAT containers.

[0207] At step 1611, the method 1600 may include determining, by the UE, whether a non-critical extension Information Element (IE) included in the UCE message includes MR-DC filters.

[0208] At step 1613, the method 1600 may include using, by the UE, an MR-DC filter index which is provided by a value present at corresponding RAT container position in the non-critical extension IE. Further, when the UCE message includes a 6G container and the UE supports the 6G, the method 1600 may also include including, by the UE, radio access capabilities for the 6G and band combinations within a corresponding UE capability RAT container with RAT type set as the 6G. Furthermore, in a case when the UCE message includes one of eutra-6G or nr-6G and the UE supports the eutra-6G or the nr-6G, the method 1600 may include including, by the UE, radio access capabilities for one of the eutra-6G or the nr-6G and band combinations within a corresponding UE capability RAT container with RAT type set as one of the eutra-6G or the nr-6G.

[0209] Embodiments are exemplary in nature, and the method 1600 may be performed with any suitable variations to the steps performed, including addition / omission of the steps.

[0210] FIG. 17illustrates a flow chart of a method 1700 for handling the UE Capability framework aspect in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2), according to an embodiment of the present disclosure. The MN may correspond to any one of the MN 501, the MN 801, the MN 901, the MN 1001, and the MN 1101, as explained above.

[0211] At step 1701, the method 1700 may include defining a database containing a plurality of combinations of rf featureSets. In one embodiment, each combination of the rf featureSets is stored as a definition in the database. Each definition is mapped to a unique pre-defined identifier and the unique pre-defined identifier is an index value based on max possible number of combinations of the rf featureSets.

[0212] Further, at step 1703, the method 1700 may include storing, the database, at a User Equipment (UE) and the MN. The UE may correspond to any one of the UE 507, the UE 807, the UE 907, the UE 1007, or the UE 1107, as explained above.

[0213] At step 1705, the method 1700 may include receiving, by the UE from the MN, a UE Capability Enquiry (UCE) message including a Multi RAT-Dual Connectivity (MR-DC) filter.

[0214] At step 1707, the method 1700 may include generating, by the UE, a UE Capability Information (UCI) message by fetching proposed identifiers for the feature set to include in the UCI message.

[0215] At step 1709, the method 1700 may include including, by the UE, the proposed identifiers as part of the UCI message by querying the database of the UE.

[0216] At step 1711, the method 1700 may include sending, by the UE to the MN, the generated UCI message.

[0217] At step 1713, the method 1700 may include receiving, by the MN from the UE, the generated UCI message.

[0218] At step 1715, the method 1700 may include decoding, by the MN, the UCI by performing a reverse-query to the MN side database for actual featureSet definitions of each rf container.

[0219] Embodiments are exemplary in nature, and the method 1700 may be performed with any suitable variations to the steps performed, including addition / omission of the steps.

[0220] FIG. 18illustrates an example diagram of an apparatus 1800, according to embodiments of the present disclosure. In one embodiment, the apparatus 1800 may correspond to any one of the UE 507, the UE 807, the UE 907, the UE 1007, or the UE 1107, as explained above. In other embodiments, the apparatus 1800 may correspond to any one of the MN 501, the MN 801, the MN 901, the MN 1001, the MN 1101, or the SN1 and SN2.

[0221] Referring to FIG. 18, the apparatus 1800 may include at least one processor 1802 (generally referred to herein as the processor 1802), a communication unit 1804 (e.g., communicator or communication interface), and / or a memory unit 1806 (e.g., a memory). By way of example, the apparatus 1800 may be a User Equipment, such as a cellular phone or other device that communicates over a plurality of cellular networks (such as a 3G, 4G, a 5G or pre-5G, 6G network or any future wireless communication network). The communication unit 1804 may perform functions for transmitting and receiving signals via a wireless channel.

[0222] As an example, the processor 1802 may be a single processing unit or a number of units, all of which could include multiple computing units. The processor 1802 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and / or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 1802 is configured to fetch and execute computer-readable instructions and data stored in the memory. The processor 1802 may include one or a plurality of processors. At this time, one or a plurality of processors 1302 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 AI-dedicated processor such as a neural processing unit (NPU). The one or a plurality of processors 1302 may control the processing of the input data in accordance with a predefined (or alternatively, given) operating rule or artificial intelligence (AI) model stored in the non-volatile memory and the volatile memory, e.g., the memory unit 1806. The predefined (or alternatively, given) operating rule or artificial intelligence model is provided through training or learning.

[0223] The memory unit 1806 may include any non-transitory computer-readable medium known in the art including, for example, volatile memory, such as Static Random Access Memory (SRAM) and Dynamic Random Access Memory (DRAM), and / or non-volatile memory, such as Read-Only Memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.

[0224] FIG. 19 illustrates a block diagram of an internal configuration of a UE, according to an embodiment.

[0225] As shown in FIG. 19, the UE according to an embodiment may include a transceiver 1910, a memory 1920, and a processor 1930. The transceiver 1910, the memory 1920, and the processor 1930 of the UE may operate according to a communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. In addition, the processor 1930, the transceiver 1910, and the memory 1920 may be implemented as a single chip. Also, the processor 1930 may include at least one processor. Furthermore, the UE of Fig 19 may correspond to the apparatus of Fig. 18.

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

[0227] Also, the transceiver 1910 may receive and output, to the processor 1930, a signal through a wireless channel, and transmit a signal output from the processor 1930 through the wireless channel.

[0228] The memory 1920 may store a program and data required for operations of the UE. Also, the memory 1920 may store control information or data included in a signal obtained by the UE. The memory 1920 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0229] The processor 1930 may control a series of processes such that the UE operates as described above. For example, the transceiver 1910 may receive a data signal including a control signal transmitted by the base station or the network entity, and the processor 1930 may determine a result of receiving the control signal and the data signal transmitted by the base station or the network entity.

[0230] FIG. 20 illustrates a block diagram of an internal configuration of a base station or a network entity, according to an embodiment.

[0231] As shown in FIG. 20, the base station or the network entity according to an embodiment may include a transceiver 2010, a memory 2020, and a processor 2030. The transceiver 2010, the memory 2020, and the processor 2030 of the base station or the network entity may operate according to a communication method of the base station or the network entity described above. However, the components of the base station or the network entity are not limited thereto. For example, the base station or the network entity may include more or fewer components than those described above. In addition, the processor 2030, the transceiver 2010, and the memory 2020 may be implemented as a single chip. Also, the processor 2030 may include at least one processor. Furthermore, the base station of Fig 20 may correspond to the apparatus of Fig. 18.

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

[0233] Also, the transceiver 2010 may receive and output, to the processor 2030, a signal through a wireless channel, and transmit a signal output from the processor 2030 through the wireless channel.

[0234] The memory 2020 may store a program and data required for operations of the base station or the network entity. Also, the memory 2020 may store control information or data included in a signal obtained by the base station or the network entity. The memory 2020 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0235] The processor 2030 may control a series of processes such that the base station or the network entity operates as described above. For example, the transceiver 2010 may receive a data signal including a control signal transmitted by the terminal or the network entity or the base station, and the processor 2030 may determine a result of receiving the control signal and the data signal transmitted by the terminal or the network entity or the base station.

[0236] The various operations of methods described above may be performed by any suitable device capable of performing the operations, such as the processing circuitry discussed above. For example, as discussed above, the operations of methods described above may be performed by various hardware and / or software implemented in some form of hardware (e.g., processor, ASIC, etc.).

[0237] The software may comprise an ordered listing of executable instructions for implementing logical functions and may be embodied in any "processor-readable medium" for use by or in connection with an instruction execution system, apparatus, or device, such as a single or multiple-core processor or processor-containing system.

[0238] The blocks or operations of a method or algorithm and functions described in connection with embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a tangible, non-transitory computer-readable medium. A software module may reside in Random Access Memory (RAM), flash memory, Read Only Memory (ROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a CD ROM, or any other form of storage medium known in the art.

[0239] The present disclosure enables the UE to reduce the size of the UCI significantly in 6G.

[0240] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one ordinary skilled in the art to which this invention belongs. The system, methods, and examples provided herein are illustrative only and not intended to be limiting.

[0241] While specific language has been used to describe the present subject matter, any limitations arising on account thereto, are not intended. As would be apparent to a person in the art, various working modifications may be made to the method to implement the inventive concept as taught herein. The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment.

[0242] 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 should and 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 practised with modification within the scope of the embodiments as described herein.

[0243] List of Terms and their Definitions:

[0244] SA: Standalone

[0245] NSA: Non-standalone

[0246] MCG: Master Cell Group

[0247] SCG: Secondary Cell Group

[0248] MN: Master Node

[0249] SN: Secondary Node

[0250] UCE: UE Capability Enquiry

[0251] UCI: UE Capability Information

[0252] RAT: Radio Access Technology

[0253] NCE: nonCriticalExtension container

[0254] RAN: Radio Access Network

[0255] CN: Core Network

[0256] DL: Downlink

[0257] UL: Uplink

[0258] RACS: Radio Capability Signalling optimization

[0259] UCMF: UE Capability Management Function

[0260] DC: Dual Connectivity

[0261] MR-DC: Multi RAT-Dual Connectivity

[0262] ENDC: Eutra NR Dual Connectivity

[0263] NR-6G-DC: NR 6G Dual Connectivity

[0264] LTE-6G-DC: LTE 6G Dual Connectivity

[0265] (NG)ENDC: Next Gen ENDC

[0266] NEDC: NR Eutra Dual Connectivity

[0267] CA: Carrier Aggregation

[0268] MIMO: Multiple Input Multiple Output

[0269] QAM: Quadrature Amplitude Modulation

[0270] CA: Carrier Aggregation

[0271] CC: Component Carrier.

Claims

1.A method (1600) of handling Multi Radio Access Technology (multi-RAT) -Dual Connectivity (MR-DC) filter for User Equipment (UE) Capability Enquiry (UCE) in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2), the method (1600) comprising:generating (1601) a combined MR-DC filter for a MN RAT container by a logical OR operation of a first MR-DC filter and a second MR-DC filter, whereinthe first MR-DC filter is for the SN1 and one or more MN-SN1 RAT containers, andthe second MR-DC filter is for the SN2 and one or more MN-SN2 RAT containers.2.The method (1600) of claim 1, further comprising:generating (1603) a RAT container type to MR-DC filter mapping upon generation of the combined MR-DC filter.3.The method (1600) of claim 2, further comprising:sending (1605), by the MN to a User Equipment (UE), a UCE message to enquire UE's capability for each type of RAT containers, wherein the UCE message includes the RAT container type to the MR-DC filter mapping that is via a non-critical extension Information Element (IE).4.The method (1600) of claim 3, wherein:the non-critical extension IE includes a sequence of numbers which are indices mapped to the corresponding filter; andeach of the RAT container type uses the in-sequence indexed numbers to determine the MR-DC filter value to apply on a specific RAT container.5.The method (1600) of claim 1, further comprising:sending (1605), by the MN to a User Equipment (UE), a UCE message to enquire UE's capability for each type of RAT containers; andproviding (1607), by the MN to the UE, a type of filter for each type of RAT containers via a capability request filter Information Element (IE),wherein the capability request filter IE includes a mapping information of RAT container type to MR-DC filter.6.The method (1600) of claim 1, further comprising:sending, by the MN to a User Equipment (UE), a first UCE message to enquire UE's capability for the MN RAT container using the combined MR-DC filter;sending, by the MN to the UE, a second UCE message to enquire the UE's capability for the SN1 and MN-SN1 RAT containers using the first MR-DC filter; andsending, by the MN to the UE, a third UCE message to enquire about the UE's capability for the SN2 and MN-SN2 RAT containers using the second MR-DC filter.7.The method (1600) of claim 6, further comprising splitting, by the MN, the second UCE message and the third UCE message into two separate messages.8.The method (1600) of claim 6, further comprising adding, by the MN, a rrc-SegAllowed Information Element (IE) in the UCE messages to aid the UE to maintain UE Capability Information (UCI) message size based on a maximum Packet Data Convergence Protocol Service Data Unit (PDCP SDU) size.9.The method (1600) of claim 1, further comprising:receiving (1609), by a User Equipment (UE) from the MN, a UCE message to enquire UE's capability for each type of RAT containers;determining (1611), by the UE, whether a non-critical extension Information Element (IE) included in the UCE message includes MR-DC filters; andusing (1613), by the UE, an MR-DC filter index which is provided by a value present at corresponding RAT container position in the non-critical extension IE.10.The method (1600) of claim 9, further comprising:when the UCE message includes a 6G container and the UE supports the 6G:including, by the UE, radio access capabilities for the 6G and band combinations within a corresponding UE capability RAT container with RAT type set as the 6G.11.The method (1600) of claim 9, further comprising:in a case when the UCE message includes one of eutra-6G or nr-6G and the UE supports the eutra-6G or the nr-6G:including, by the UE, radio access capabilities for one of the eutra-6G or the nr-6G and band combinations within a corresponding UE capability RAT container with RAT type set as one of the eutra-6G or the nr-6G.12.A method (1700) of handling User Equipment (UE) Capability framework aspect in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2), the method (1700) comprising:defining (1701) a database containing a plurality of combination of rf featureSets, whereineach combination of the rf featureSets is stored as a definition in the database,each definition is mapped to a unique pre-defined identifier, andthe unique pre-defined identifier is an index value based on max possible number of combinations of the rf featureSets; andstoring (1703), the database, at a User Equipment (UE) and the MN.13.The method (1700) of claim 12, further comprising:receiving (1705), by the UE from the MN, a UE Capability Enquiry (UCE) message including Multi RAT-Dual Connectivity (MR-DC) filter;generating (1707), by the UE, a UE Capability Information (UCI) message by fetching proposed identifiers for the feature set to include in the UCI message;including (1709), by the UE, the proposed identifiers as part of the UCI message by querying the database of the UE;sending (1711), by the UE to the MN, the generated UCI message;receiving (1713), by the MN from the UE, the generated UCI message; anddecoding (1715), by the MN, the UCI by performing a reverse-query to the MN side database for actual featureSet definitions of each rf container.14.An apparatus (1800) for handling Multi Radio Access Technology (multi-RAT) -Dual Connectivity (MR-DC) filter for User Equipment (UE) Capability Enquiry (UCE) in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2), the apparatus (1800) comprising:at least one processor (1802) configured to:generate a combined MR-DC filter for a MN RAT container by a logical OR operation of a first MR-DC filter and a second MR-DC filter, whereinthe first MR-DC filter is for the SN1 and one or more MN-SN1 RAT containers, andthe second MR-DC filter is for the SN2 and one or more MN-SN2 RAT containers.15.An apparatus (1800) for handling User Equipment (UE) Capability framework aspect in 6G including a Master Node (MN), a first Secondary Node (SN1), and a second Secondary Node (SN2), the apparatus (1800) comprising:at least one processor (1802) configured to:define a database containing a plurality of combination of rf featureSets, whereineach combination of the rf featureSets is stored as a definition in the database,each definition is mapped to a unique pre-defined identifier, andthe unique pre-defined identifier is an index value based on max possible number of combinations of the rf featureSets; andstore, the database, at a User Equipment (UE) and the MN.

Images