Method and system for optimizing the processing of radio capability signaling information encoding of user equipment using wireless capability signaling

Abstract

The present disclosure relates to a communication method and system for integrating a fifth generation (5G) communication system supporting a higher data rate than a fourth generation (4G) system with an Internet of Things (IoT) technology. The present disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, smart retail, safety and security services. A method and system for processing UE radio capability information encoding using RACS. The method disclosed herein includes encoding radio capability information of a user equipment (UE) in a format of multiple radio access technologies (RATs), wherein the multiple RATs are supported by a public land mobile network (PLMN) in which the UE is registered. The method also includes allocating a radio capability identifier (RAC‑ID) to the UE for signaling radio capability information encoded in multiple formats over multiple RATs. The method also includes encoding the radio capability information in a specific format of the indicated RAT, and allocating a RAC‑ID to the UE for signaling the radio capability information and the associated encoding format.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communication systems, and more particularly, to using Radio Capability Signaling Optimization (RACS) to process encoding of radio capability signaling information of a user equipment (UE) in a wireless communication system. Background Art

[0002] In order to meet the demand for increased wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also called "beyond 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands, such as the 60GHz band, in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference elimination, etc. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coded modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet, a human-centered connected network in which humans generate and consume information, is now evolving toward the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, which is a combination of IoT technology and big data processing technology through connection with cloud servers. As IoT implementation requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology", sensor networks, machine-to-machine (M2M) communication, machine-type communication (MTC), etc. have been recently studied. Such an IoT environment can provide intelligent Internet technology services to create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services, through the integration and combination of existing information technology (IT) with various industrial applications.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. Cloud radio access networks (RANs) as an application of the above-mentioned big data processing technologies can also be considered as an example of the convergence of 5G technologies and IoT technologies. Summary of the invention

[0005]

Technical issues

[0006] A primary object of the embodiments herein is to disclose a method and system for handling encoding of radio capability signaling information / radio capability information of a user equipment (UE) in a wireless network using a radio capability signaling optimization (RACS) feature.

[0007] Another object of the embodiments herein is to disclose a method and system for encoding radio capability information of a UE in the formats of multiple radio access technologies (RATs) that the UE has supported, and assigning a radio capability identifier (RAC-ID) to the UE for signaling the radio capability information encoded in multiple formats over multiple RATs.

[0008] Another object of embodiments herein is to disclose a method and system for encoding radio capability information in a specific format of an indicated RAT and assigning a RAC-ID to a UE for signaling the radio capability information and the associated encoding format.

[0009]

Problem Solution

[0010] Embodiments herein provide methods, UE radio capability management functions (UCMFs), and network functions (NFs). A method performed by a user equipment radio capability management function (UCMF), the method comprising: receiving user equipment (UE) radio capability information and at least one first radio access technology (RAT) type from a first network function (NF), wherein the at least one first RAT type is associated with at least one coding format; allocating a UE radio capability identifier (ID) associated with the UE radio capability information and the at least one first RAT type; and sending the UE radio capability ID to the first NF. And a method performed by a network function (NF) in a wireless communication system, the method comprising: sending user equipment (UE) radio capability information and at least one first radio access technology (RAT) type to a user equipment radio capability management function (UCMF), wherein the at least one first RAT type is associated with at least one coding format; and receiving a UE radio capability identifier (ID) from the UCMF, wherein the UE radio capability ID associated with the UE radio capability information and the at least one first RAT type is allocated by the UCMF.

[0011] Therefore, embodiments herein provide a user equipment radio capability management function (UCMF) in a wireless communication system, the UCMF comprising: a transceiver; and a controller configured to: receive user equipment (UE) radio capability information and at least one first radio access technology (RAT) type from a first network function (NF) via the transceiver, wherein the at least one first RAT type is associated with at least one coding format, allocate a UE radio capability identifier (ID) associated with the UE radio capability information and the at least one first RAT type, and send the UE radio capability ID to the first NF via the transceiver. And a network function (NF) in a wireless communication system, the NF comprising: a transceiver; and a controller configured to: send user equipment (UE) radio capability information and at least one first radio access technology (RAT) type to a user equipment radio capability management function (UCMF) via the transceiver, wherein the at least one first RAT type is associated with at least one coding format; and receive a UE radio capability identifier (ID) from the UCMF via the transceiver, wherein the UE radio capability ID associated with the UE radio capability information and the at least one first RAT type is allocated by the UCMF.

[0012] [Advantageous Effects of the Invention]

[0013] The RACS method can reduce the signaling overhead of the radio capability information on the UE by assigning a unique identifier to the radio capability information of the UE. The unique identifier can be a RAC-ID. The UE can share the RAC-ID corresponding to its radio capability information through various interfaces. The RACS method can also provide a node (UE radio capability management function (UCMF)) for storing the radio capability information of the UE, assigning the RAC-ID to the radio capability information of the UE, and parsing the RAC-ID assigned to the radio capability information of the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The embodiments herein are shown in the accompanying drawings, in which the same reference numerals represent corresponding parts in the different drawings. The embodiments herein will be better understood from the following description with reference to the accompanying drawings, in which:

[0015] Figure 1 is an example sequence diagram describing a conventional method of encoding user equipment (UE) radio capability information;

[0016] Figure 2 A wireless communication system according to embodiments disclosed herein is depicted;

[0017] Figure 3 is a block diagram depicting various components of a core network (CN) of a radio access technology (RAT) according to embodiments disclosed herein;

[0018] Figure 4 is a block diagram depicting various components of a radio access network (RAN) according to embodiments disclosed herein;

[0019] Figure 5 is a block diagram depicting various components of a UE Radio Capability Management Function (UCMF) for allocating and resolving Radio Capability Identifiers (RAC-IDs) according to embodiments disclosed herein;

[0020] Figure 6 is an example sequence diagram illustrating encoding of UE radio capability information for signaling on various interfaces of a RAT according to embodiments disclosed herein;

[0021] Figure 7 is another exemplary sequence diagram describing encoding of UE radio capability information for signaling on various interfaces of a RAT according to embodiments disclosed herein;

[0022] Figure 8a is a flowchart depicting a method for processing encoding of UE radio capability information using RACS according to an embodiment disclosed herein; and

[0023] Figure 8bis a flow chart depicting a method for resolving a RAC-ID of a UE into UE radio capability information according to embodiments disclosed herein. DETAILED DESCRIPTION

[0024] The exemplary embodiments herein and their various features and advantageous details will be explained more fully with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. The description of well-known components and processing techniques is omitted so as not to unnecessarily obscure the embodiments herein. The description herein is merely to facilitate understanding of the manner in which the exemplary embodiments herein may be practiced, and further to enable those skilled in the art to practice the exemplary embodiments herein. Therefore, the present disclosure should not be interpreted as limiting the scope of the exemplary embodiments herein.

[0025] In a wireless communication system, a radio capability signaling optimization (RACS) method may be implemented to avoid the overhead of signaling the radio capability information of a user equipment (UE) across various interfaces (e.g., radio as well as non-radio interfaces). For example, in a wireless network, a new radio (NR) / 5G core may request a UE to signal its radio capability information for an NR radio access technology (RAT), a 4G RAT, or any other supported RAT. Similarly, a 4G packet core may request a UE to signal its radio capability information for a 4G RAT, an NR RAT, or any other supported RAT.

[0026] However, the size of such radio capability information may become very large and may therefore become an overhead for the UE to send the radio capability information through the radio interface signal. The RACS method can reduce the signaling overhead of the radio capability information on the UE by assigning a unique identifier to the radio capability information of the UE. The unique identifier can be a RAC-ID. The UE can share the RAC-ID corresponding to its radio capability information through various interfaces. The RACS method can also provide a node (UE radio capability management function (UCMF)) for storing the radio capability information of the UE, assigning a RAC-ID to the radio capability information of the UE, and parsing the RAC-ID assigned to the radio capability information of the UE.

[0027] In the traditional version of the 3GPP specification, when the UE switches from one RAT (source RAT) to another RAT (target RAT) or moves in idle mode, the radio access network (RAN) of the target RAT receives the RAC-ID from the UE and downloads the radio capability information of the UE corresponding to the received RAC-ID from the UCMF. The RAN of the target RAT decodes the downloaded radio capability information to determine the radio capability information of the UE. The radio capability information of the UE may be uploaded to the UCMF by the source RAT. The RAN of the target RAT can successfully decode the radio capability information of the UE corresponding to the received RAC-ID only when the source RAT and the target RAT are the same. However, when the source RAT and the target RAT are different, the decoding of the radio capability information of the UE corresponding to the RAC-ID received on the RAN of the target RAT may fail because the encoding of the radio capability information of the UE may be different depending on the RAT.

[0028] Consider an example scenario such as Figure 1 As shown, the UE initiates registration with the 5G RAT. The UE sends a registration request to the access and mobility function (AMF) of the 5G RAT through the RAN (gNodeB (gNB)) of the 5G RAT (hereinafter referred to as NG-RAN). The NG-RAN sends a UE radio capability request to the UE to obtain the radio capability information of the UE. When receiving the UE radio capability request from the NG-RAN, the UE sends its radio capability information to the NG-RAN, and then the NG-RAN uploads the radio capability information of the UE to the AMF. The AMF sends the radio capability information of the UE to the UCMF for allocating the RAC-ID. The UCMF allocates a RAC-ID (e.g., RAC-ID-1) to the received radio capability information of the UE, where the radio capability information can be encoded in the 5G format. The UCMF sends the RAC-ID-1 allocated to the radio capability information of the UE to the AMF, and the AMF forwards the received RAC-ID-1 to the UE through the NG-RAN. The UE stores the mapping of the RAC-ID relative to the signaled radio capability information.

[0029] After a period of time, the UE may be turned off and on in the area of ​​the 4G RAT. In this case, the UE sends a registration request including RAC-ID-1 (which is assigned to the UE by the UCMF when the UE registers with the 5G RAT) to the mobility management entity (MME) of the 4G RAT. The MME sends a request including the received RAC-ID-1 of the UE to the UCMF to parse the received RAC-ID-1 of the UE. The UCMF obtains the radio capability information of the UE corresponding to the received RAC-ID-1, and blindly sends the obtained radio capability information of the UE to the RAN (eNodeB (eNB)) of the 4G RAT, where the obtained radio capability information may be encoded using the 5G format. Upon receiving the radio capability information, the RAN node of the 4G RAT assumes that the received radio capability information may be encoded using the 4G format and erroneously decodes the received radio capability information. Incorrect decoding of the radio capability information may occur because the UCMF cannot distinguish the format in which the radio capability information must be encoded and returned and / or the RAN node of the 4G RAT cannot determine the encoding format of the received radio capability information.

[0030] Consider another example scenario where the UE is registered in 4G / LTE RAT. In this case, the UE obtains the RAC-ID-1 corresponding to its radio capability information from the MME through the RAN node / eNB of the 4G RAT. After some time, the UE may move towards the area of ​​5G RAT, so the network initiates the handover of the UE from 4G RAT to 5G RAT. When initiating the handover, the eNB sends the "UE Transparent Container" and the RAC-ID-1 of the UE to the MME, and the MME sends the received "UE Transparent Container" and RAC-ID-1 of the UE to the AMF, which in turn forwards the received "UE Transparent Container" and RAC-ID-1 of the UE to the gNB of the 5G RAT. After receiving the "UE Transparent Container" and RAC-ID-1 of the UE, the gNB checks the radio capability information of the UE in the local database. If the gNB does not have the radio capability information of the UE in the local database, the gNB requests the AMF to resolve the RAC-ID 1 of the UE. The AMF requests the UCMF to resolve the RAC-ID-1 of the UE. The UCMF obtains the radio capability information of the UE corresponding to the received RAC-ID-1 of the UE, and sends the obtained radio capability information to the AMF, wherein the obtained radio capability information may be encoded using the 4G / LTE format. The AMF sends the received radio capability information of the UE to the gNB, wherein the gNB erroneously decodes the received radio capability information of the UE by assuming that the received radio capability information has been encoded using the 5G format.

[0031] Consider another example scenario, where the UE is switched on in an area of ​​an LTE RAT and is registered with the LTE RAT. In this case, the UE obtains the RAC-ID-1 corresponding to its radio capability information from the MME through the RAN node / eNB of the 4G RAT. After a period of time, the UE enters idle mode and reselects the NR / 5G RAT. In this case, the UE triggers mobility registration and notifies the AMF of the NR RAT of the RAC-ID-1. The AMF requests the UCMF to resolve the RAC-ID-1 of the UE. The UCMF obtains the radio capability information of the UE corresponding to the received RAC-ID-1 of the UE and sends the obtained radio capability information to the AMF, where the obtained radio capability information may be encoded in a 4G / LTE format. The AMF sends the received radio capability information of the UE to the gNB, where the gNB incorrectly decodes the received radio capability information of the UE by assuming that the received radio capability information has been encoded in a 5G format, which causes further anomalies.

[0032] Consider another example scenario where a first UE (UE-A) is switched on in an LTE RAT and registered with the LTE RAT. In this case, the UE obtains a RAC-ID-1 corresponding to its radio capability information from the MME via the RAN node / eNB of the 4G RAT. The UCMF may store the RAC-ID-1 against the UE's radio capability information. A second UE (UE-B) has the same radio capability information as UE-A and is registered in an NR RAT. When UE-B registers with the AMF of the NR RAT, the AMF sends the radio capability information of UE-B (in NR format) to the UCMF and requests the UCMF to allocate a RAC-ID for the radio capability information of UE-B. Even though the capabilities of UE-A and UE-B are the same, the UCMF allocates a new RAC-ID for the radio capability information of UE-B. Assigning different RAC-IDs to the same capabilities of different UEs may create duplication issues. Similar duplication issues may arise when manufacturer-assigned IDs are used to represent the radio capability information of the UE.

[0033] Therefore, in the conventional method, the UCMF, which is currently unaware of the RAT, cannot distinguish the encoding format of the UE's radio capability information, nor can it check whether the encoding format of the radio capability information can be used by the RAT requesting the UE's radio capability information. In addition, the UCMF cannot match the UE's existing radio capability information with the same set of radio capability information of the UE received from a different RAT (due to different encoding), which leads to the creation of a large database of UE's RAC-ID and radio capability information.

[0034] Furthermore, in the conventional method, the RAN node of the target RAT cannot perform conversion of the radio capability information from the encoding format of the source RAT to the encoding format of the target RAT because the RAN node of the target RAT is not assigned information about the encoding format of the received radio capability information of the UE.

[0035] A primary object of the embodiments herein is to disclose methods and systems for handling encoding of radio capability signaling information / radio capability information of a user equipment (UE) in a wireless network using a radio capability signaling optimization (RACS) feature.

[0036] Another object of the embodiments herein is to disclose methods and systems for encoding radio capability information of a UE in the formats of multiple radio access technologies (RATs) that the UE has supported, and assigning a radio capability identifier (RAC-ID) to the UE for signaling the radio capability information encoded in multiple formats over multiple RATs.

[0037] Another object of embodiments herein is to disclose methods and systems for encoding radio capability information in a specific format of an indicated RAT and assigning a RAC-ID to a UE for signaling the radio capability information and the associated encoding format.

[0038] Therefore, embodiments herein provide methods and systems for processing radio capability signaling information of a user equipment (UE) using radio capability signaling optimization (RACS). The method disclosed herein includes receiving a request from a core network (CN) by a UE radio capability management function (UCMF) for allocating a radio capability identifier (RAC-ID) to a UE registered in a public land mobile network (PLMN), wherein the request for allocating the RAC-ID includes the radio capability information of the UE (UE radio capability information) and the radio access technology (RAT) type. The method also includes encoding the UE radio capability information by the UCMF based on at least one RAT type indicated in the received request and at least one other RAT type supported by the PLMN. The method also includes allocating the RAC-ID corresponding to the encoded UE radio capability information to the UE by the UCMF. The method also includes receiving a request by the UCMF from the CN for parsing the RAC-ID of the UE, wherein the request for parsing the RAC-ID includes a combination of the RAC-ID of the UE and the RAT type or includes the RAC-ID of the UE. The method also includes the UCMF resolving the RAC-ID of the UE into the UE radio capability information based on the encoding of the UE radio capability information and the received request for resolving the RAC-ID.

[0039] Therefore, an embodiment herein provides a wireless communication system, comprising a plurality of user equipments (UEs), a public land mobile network (PLMN) comprising a plurality of radio access technologies (RATs), wherein each RAT comprises a radio access network (RAN) and a core network (CN), and a UE radio capability management function (UCMF) coupled to each RAT. The UCMF is configured to receive a request from the core network (CN) to allocate a radio capability identifier (RAC-ID) to a UE registered in the public land mobile network (PLMN), wherein the request to allocate the RAC-ID comprises the radio capability information (UE radio capability information) and the radio access technology (RAT) type of the UE. The UCMF is also configured to encode the UE radio capability information based on at least one RAT type indicated in the received request and at least one other RAT type supported by the PLMN. The UCMF is also configured to allocate the RAC-ID corresponding to the encoded UE radio capability information to the UE. The UCMF is further configured to receive a request from the CN to resolve the RAC-ID of the UE, wherein the request to resolve the RAC-ID includes a combination of the RAC-ID of the UE and the RAT or includes the RAC-ID of the UE. The UCMF is further configured to resolve the RAC-ID of the UE into the UE radio capability information based on the encoding of the UE radio capability information and the received request for resolving the RAC-ID.

[0040] When considered in conjunction with the following description and the accompanying drawings, these and other aspects of the exemplary embodiments herein will be better understood and appreciated. However, it should be understood that although the following description indicates exemplary embodiments and many specific details thereof, it is provided in an illustrative and non-restrictive manner. Without departing from the spirit of the present invention, many changes and modifications may be made within the scope of the exemplary embodiments of the present invention, and the exemplary embodiments of the present invention include all such modifications.

[0041] Embodiments herein disclose methods and systems for processing encoding of radio capability signaling information of a user equipment (UE) using radio capability signaling optimization (RACS). Referring now to the drawings, and more particularly to Figure 2 8 , wherein like reference numerals represent corresponding features consistently throughout the drawings, an example embodiment is shown.

[0042] Figure 2A wireless communication system 200 according to an embodiment disclosed herein is depicted. The wireless communication system 200 mentioned herein may be configured to enable at least one user equipment (UE) to signal its radio capability information through various interfaces using a radio capability signaling optimization (RACS) method / approach / feature. Examples of interfaces may be, but are not limited to, a radio interface, a non-radio interface, etc. The RACS method assigns a unique ID to the UE, which represents a set of radio capability information of the UE. The unique ID may be referred to as a radio capability identifier (RAC-ID). Therefore, RACS optimizes the signaling of the radio capability information of the UE by improving network throughput, efficiency, etc.

[0043] The radio capability information of the UE (hereinafter referred to as UE radio capability information) includes information about radio resources supported by the UE, such as but not limited to frequency bands, radio bearers, power classes, carrier aggregation (CA) band combinations supported by the UE, etc. The embodiments herein use terms such as "radio capability information of the UE", "radio capability signaling information", "UE radio capability information", "UE RACS information", "RACS information", etc., which can interchangeably refer to information indicating radio resources supported by the UE.

[0044] The wireless communication system 200 includes a plurality of user equipments (UEs) 202 , a public land mobile network (PLMN) 208 including a plurality of radio access technologies (RATs) 204 , and a UE radio capability management function (UCMF) (UCMF node) 206 .

[0045] The UE 202 mentioned here may be a UE capable of supporting one or more RATs 204 of the wireless communication system 200. Examples of the UE 202 may be, but are not limited to, a mobile phone, a smartphone, a tablet, a tablet computer, a personal digital assistant (PDA), a laptop, a computer, a wearable computing device, a vehicle infotainment device, an Internet of Things (IoT) device, a virtual reality (VR) device, a wireless fidelity (Wi-Fi) router, a universal serial bus (USB) dongle, a robot, an automatic guided vehicle, or any other device supporting one or more RATs of the wireless communication system 200. The UE 202 may include one or more processors / central processing units (CPUs), memory, storage, transceivers, etc., for performing at least one intended function / operation.

[0046] The UE 202 may be configured to register with the PLMN 208 in order to access communication services from one of the RATs 204 of the PLMN 208. Examples of communication services may be, but are not limited to, voice-based services and data-based services, etc. Examples of data-based services may be, but are not limited to, web surfing, chat sessions, map-based services, voice over Internet Protocol (IP) (VoIP), etc. The UE 202 may connect / register to one of the RATs 204 of the PLMN 208 to obtain communication services by performing a registration procedure specified in the 3rd Generation Partnership Project (3GPP) specification TS 23.502. In an example, the UE 202 may register with the RAT 204 of the PLMN 208 when the UE 202 is switched on in the area / location of the corresponding RAT 204. In an example, the UE 202 may register with the RAT 204 when the UE 202 switches from another RAT to the corresponding RAT 204 by performing a handover. In an example, when the UE 202 reselects the corresponding RAT 204, the UE 202 can register with the RAT 204. In an example, due to idle mode mobility, the UE 202 can register with the RAT 204. Idle mode mobility includes moving the UE 202 to a new RAT while the UE 202 is not engaged in active communication with the serving network / RAT 204.

[0047] The UE 202 may also be configured to signal UE radio capability information to the registered RAT 204 to access communication services. As defined in 3GPP specification TS 23.501, the UE 202 may use RACS to signal the UE radio capability information.

[0048] The PLMN 208 mentioned here may be a home network to which the UE 202 registers for communication services. The PLMN 208 includes a plurality of RATs 204 for providing communication services to the UE 202. Examples of the RATs 204 may be, but are not limited to, 3GPP third generation (3G), long term evolution (LTE / 4G), advanced LTE (LTE-A), fifth generation (5G) new radio, universal mobile telecommunication service (UMTS), global system for mobile communications (GSM) enhanced data rates for GSM evolution (EDGE) radio access network (GERAN) system wireless local area network (WLAN), worldwide interoperability for microwave access (WiMAX / IEEE 802.16), Wi-Fi (IEEE802.11), evolved UTRA (E-UTRA), or any other next generation network.

[0049] RAT 204 includes a radio access network (RAN) 204a and a core network (CN) 204b. RAN 204a and CN 204b may include one or more processors / (CPU), memory, storage, transceiver, etc., for performing at least one intended function / operation. In an example, RAN 204a and CN 204b may support RACS methods, which may be referred to as RACS support nodes hereinafter. In another example, RAN 204a and CN 204b may not support RACS methods, which may be referred to as non-RACS support nodes hereinafter.

[0050] The RAN 204a may include a node / base station (BS), such as, but not limited to, an evolved node (eNB), a new radio node (gNB), etc. The RAN 204a may communicate with the UE 202 and the CN 204b via an interface (wireless interface or non-wireless interface) supported by an associated RAT. The RAN 204a may be configured to connect the UE 202 to the CN 204b. The RAN 204a may be configured to perform radio resource management functions, such as, but not limited to, radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources (scheduling) to the UE 202 in uplink / downlink, etc.

[0051] The CN 204b may include, but is not limited to, one of an evolved packet core (EPC), a 5G core (5GC) network, etc. The CN 204b may be connected to the RAN 204a and an external data network (not shown) via an interface (radio interface or non-radio interface) supported by a related RAT. Examples of external data networks may be, but are not limited to, the Internet, a packet data network (PDN), an Internet Protocol (IP) multimedia core network subsystem, etc. The CN 204b connects the UE 202 (connected to the associated RAN 204a) to an external data network for communication services.

[0052] The CN 204b may be configured to receive UE radio capability information from the UE 202 through the associated RAN 204a when the UE 202 registers for communication services with the associated RAN 204a. The CN 204b may also be configured to send a request to the UCMF 206 to assign a RAC-ID to the UE radio capability information. In an embodiment, the request to assign a RAC-ID may include the UE radio capability information and the RAT type. The RAT type indicates the RAT supported by the RAN 204a associated / connected to the CN 204b. For example, consider that the RAT 204 including the CN 204b is an LTE network and the RAN 204a is an eNB. In this case, the RAT type indicated by the CN 204b may be "LTE / 4G RAT".

[0053] The CN 204b may also be configured to receive the RAC-ID of the UE 202 from the associated RAN 204a, and send a request to the UCMF 206 to resolve the received RAC-ID of the UE 202. Resolving the RAC-ID includes obtaining UE radio capability information about the corresponding RAC-ID. In an embodiment, the request to resolve the RAC-ID may include the RAC-ID and RAT type of the UE 202. The CN 204b may also be configured to receive the UE radio capability information corresponding to the transmitted RAC-ID of the UE 202 from the UCMF 206, and provide the received UE radio capability information to the associated RAN 204a.

[0054] The UCMF 206 mentioned here can be a node in the wireless communication system 200, which can be configured to maintain / store UE radio capability ID mapping. The UE radio capability ID mapping provides information about the radio capability information of the UE 202 relative to the RAC-ID. The UCMF 206 can also be configured to maintain / store the RAC-ID pre-configured for the UE 202 by the manufacturer of the UE 202 (as defined in the 3GPP specification TS 23.501).

[0055] UCMF 206 may also be configured to allocate a RAC-ID corresponding to UE radio capability information to UE 202 upon receiving a request from CN 204b to allocate a RAC-ID to UE 202. The request to allocate the RAC-ID includes the UE radio capability information and the RAT type. UCMF 206 may also be configured to resolve the RAC-ID of UE 202 into the encoded UE radio capability information upon receiving a request from CN 204b to resolve the RAC-ID of UE 202. The request to resolve the RAC-ID of UE 202 includes the RAC-ID of UE 202 and the RAT type of RAN 204a associated with CN 204b. Resolving the RAC-ID refers to determining the UE radio capability information for the received RAC-ID of UE 202.

[0056] Embodiments herein enable UCMF 206 to allocate a RAC-ID for UE 202 by storing UE radio capability information in multiple encoding formats, and to resolve the RAC-ID of UE 202 based on the RAT type indicated in a received request for resolving the RAC-ID.

[0057] UCMF 206 receives a request from CN 204b to allocate a RAC-ID for UE 202. The request to allocate a RAC-ID includes UE radio capability information and RAT types supported by RAN 204a associated with CN 204b. Upon receiving the request from CN 204b to allocate a RAC-ID to UE 202, UCMF 206 encodes the UE radio capability information in all formats of multiple RAT types / RATs supported by PLMN 208. The format may correspond to the encoding format of the RAT supported by PLMN 208. The embodiments herein may interchangeably use terms such as "format", "encoding format", "RAT format", etc. to refer to the encoding rules of the RAT. UCMF 206 maps the UE radio capability information encoded in multiple formats to the corresponding RAT types. UCMF 206 allocates the same RAC-ID to the UE radio capability information that has been encoded in all formats of the multiple RAT types supported by PLMN 208. UCMF 206 stores the RAC-ID allocated to UE 202 against the UE radio capability information encoded in multiple encoding formats and the associated RAT type in the UE radio capability ID mapping. In response to the request (for allocating RAC-ID) received from CN 204b, UCMF 206 sends the RAC-ID allocated to the UE radio capability information to CN 204b. CN 204b sends the received RAC-ID to UE 202 through the associated RAN 204a.

[0058] UCMF 206 also receives a request from CN 204b to resolve the RAC-ID of UE 202. The request to resolve the RAC-ID of UE 202 includes the RAC-ID of UE 202 and the RAT type supported by RAN 204a associated with CN 204b. Upon receiving the request to resolve the RAC-ID from CN 204b, UCMF 206 identifies the RAT type indicated in the request. Upon identifying the RAT type, UCMF 206 accesses the stored UE radio capability ID mapping and obtains UE radio capability information corresponding to the received RAC-ID and RAT type. The UE radio capability ID mapping includes UE radio capability information of all formats of the RAT types supported by UE 202 and the RAC-ID of the associated RAT type with respect to the PLMN 208. The obtained UE radio capability information corresponds to the UE radio capability information encoded in the format of the RAT type indicated in the received request for resolving the RAC-ID. In response to the received request to resolve the RAC-ID, the UCMF 206 sends the acquired UE radio capability information corresponding to the received RAC-ID to the CN 204b.

[0059] The embodiments herein enable the UCMF 206 to allocate a RAC-ID for the UE 202 by storing the UE radio capability information in a single encoding format, and resolve the RAC-ID of the UE 202 into the UE radio capability information and the corresponding RAT type.

[0060] UCMF 206 receives a request from CN 204b to allocate a RAC-ID to UE 202, wherein the received request to allocate a RAC-ID includes UE radio capability information and a RAT type. Upon receiving the request to allocate a RAC-ID from CN 204b, UCMF 206 encodes the UE radio capability information in the encoding format of the RAT type indicated in the received request. UCMF 206 allocates a RAC-ID for the radio capability information. UCMF 206 maps the RAC-ID using the UE radio capability information (encoded radio capability information) and the associated RAT type.

[0061] UCMF 206 stores the mapped RAC-ID against the UE radio capability information and the associated RAT type in the UE radio capability ID mapping. In response to the request (for allocating RAC-ID) received from CN 204b, UCMF 206 sends the RAC-ID (corresponding to the UE radio capability information) allocated to UE 202 to CN 204b. CN 204b sends the received RAC-ID to UE 202 through the associated RAN 204a.

[0062] UCMF 206 also receives a request to resolve the RAC-ID of UE 202 from CN 204b. The request to resolve the RAC-ID includes the RAC-ID of UE 202. Upon receiving the request from CN 204b to resolve the RAC-ID, UCMF 206 accesses the stored UE radio capability ID mapping and obtains the UE radio capability information and the associated RAT type of the received RAC-ID. The UE radio capability ID mapping includes the RAC-ID mapped for the UE radio capability information and the associated RAT type in a single format. In an embodiment, UCMF 206 sends the obtained UE radio capability information and the associated RAT type to CN 204b in response to the received request to resolve the RAC-ID. In an embodiment, UCMF 206 sends the RAT type in the UE radio capability information (i.e., the encoded information) itself, thereby eliminating the need to send the RAT type to CN 204b separately.

[0063] The CN 204b sends the received UE radio capability information and the associated RAT type to the associated RAN 204a. Upon receiving the UE radio capability information and the associated RAT type, the RAN 204a checks the coding format of the received UE radio capability information. Based on the RAT type associated with the received UE radio capability information, the RAN 204a checks whether the coding format of the received UE radio capability information is the same as the coding format of the RAT 204 supported by the RAN 204a. If the coding format of the received UE radio capability information is different from the coding format of the RAT 204 supported by the RAN 204a (i.e., the received UE radio capability information is encoded in the format of a different RAT 204), the RAN 204a converts the coding format of the received UE radio capability information to the coding format of the RAT 204 associated with the RAN 204a. Therefore, the RAN 204a can perform correct decoding of the UE radio capability information. If the encoding format of the received UE radio capability information is the same as the encoding format of the RAT 204 associated with the RAN 204a, the RAN 204a decodes the UE radio capability information for further purposes.

[0064] Embodiments herein enable the UCMF 206 to assign a RAT-specific RAC-ID to the UE 202 .

[0065] UCMF 206 receives a request from CN 204b to allocate a RAC-ID to UE 202, wherein the received request to allocate a RAC-ID includes UE radio capability information and a RAT type. Upon receiving the request to allocate a RAC-ID from CN 204b, UCMF 206 allocates a RAC-ID to UE 202, which may be valid only specifically for the RAT type on which the RAC-ID has been allocated to UE 202 (i.e., specific to the RAT type indicated in the received request to allocate a RAC-ID). When UE 202 switches to a new RAT 204, UCMF 206 may allocate a new RAC-ID to UE 202, which may be valid only for the new RAT 204. In an example, if UE 202 has not been allocated any RAC-ID of the corresponding new RAT 204, UCMF 206 may allocate a new RAC-ID to UE 202. In another example, the UCMF 206 may assign a RAC-ID to the UE 202 that has previously been assigned to the UE 202 of the corresponding new RAT 204. Thus, the UE 202 and the RAN 204a of the RAT 204 may associate the RAT 204 to which the particular RAC-ID has been assigned to the UE 202, and may use the RAC-ID only within the same RAT.

[0066] The embodiments herein enable the UCMF 206 to allocate a RAC-ID to the UE 202 by storing the UE radio capability information in a common encoding format, and to resolve the RAC-ID of the UE 202 based on the UE radio capability information stored in the common encoding format.

[0067] UCMF 206 receives a request to allocate a RAC-ID to UE 202 from CN 204b, wherein the received request to allocate a RAC-ID includes UE radio capability information and RAT type. Upon receiving the request to allocate a RAC-ID from CN 204b, UCMF 206 encodes the UE radio capability information in a common coding format (e.g., a common "RACS format"). UCMF 206 allocates a RAC-ID corresponding to the UE radio capability information encoded in the common coding format to UE 202. In this case, when a request to parse the RAC-ID of UE 102 is received from CN 204b, UCMF 206 parses the received RAC-ID by identifying a common coding format (e.g., a "RACS format") in which the UE radio access capability information corresponding to the received RAC-ID has been stored. UCMF 206 provides the identified common coding format including the UE radio capability information to the requested CN 204b. Furthermore, the CN 204b and the RAN 204a may be configured to receive and / or send UE radio capability information between each other in a common coding format.

[0068] Embodiments herein enable exchange of UE radio capability information between a RACS supporting node and a non-RACS supporting node.

[0069] The CN 204b (i.e., RACS supporting node) of a RAT 204 configured to support the RACS method and encode the UE radio capability information in a common encoding format receives the UE radio capability information from the CN of another RAT (i.e., non-RACS supporting node) that does not support the RACS method. When the UE 202 switches from another RAT (including the non-RACS supporting node) to the RAT 204, the CN 204b / RACS supporting node 204b may receive the UE radio capability information from the non-RACS supporting node as part of the handover / context transfer. In this case, the CN 204b determines whether the associated RAN 204a is able to decode the received UE radio capability information because the UE 202 is accessing the CN 204b via the CN of another RAT that does not support RACS. Upon determining that the associated RAN 204a is unable to decode the received UE radio capability information, the CN 204b discards the received UE radio capability information and reacquires the UE radio capability information from the corresponding UE 202.

[0070] The embodiments herein enable UCMF 206 to allocate a RAC-ID to UE 202, wherein the RAC-ID may be a RAC-ID allocated by the manufacturer of UE 202, and resolve the RAC-ID upon receiving a request from CN 204b for resolving the RAC-ID. UCMF 206 resolves the RAC-ID by acquiring UE radio capability information corresponding to the RAC-ID and RAT type specified in the received request. UCMF 206 provides the acquired UE radio capability information to CN 204b.

[0071] Figure 2 An exemplary block diagram of the wireless communication system 200 is shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the wireless communication system 200 may include fewer or more blocks. In addition, the labels or names of the blocks are only for illustrative purposes and do not limit the scope of the embodiments herein. One or more blocks may be combined together to perform the same or substantially similar functions in the wireless communication system 200.

[0072] Figure 3 2 is a block diagram depicting various components of a CN 204b of a RAT 204 according to embodiments disclosed herein. The CN 204b may include, but is not limited to, at least one of an EPC, a 5GC network, etc. The CN 204b includes a memory 302, a communication interface 304, and a mobility management module 306. The CN 204a may also include other management modules / functional elements (not shown).

[0073] The memory 302 may store information related to at least one of the UE 202, the associated RAN 204a, the coding format of the associated RAT 204, etc., but is not limited thereto.

[0074] The communication interface 304 may be configured to enable the CN 204 b of the RAT 204 to communicate with at least one of the UE 202, the RAN 204 a, the CN 204 b of other RATs 204, etc., via an interface supported by the corresponding RAT 204. Examples of interfaces may be at least one of a wired or wireless front-end interface, a wired / non-radio or wireless / radio interface, or any structure that supports communication over a wired or wireless connection.

[0075] The mobility management module 306 may be a core functional element / module depending on the RAT type / RAT 204. In an example, consider that the RAT 204 including the CN 204b is an LTE / 4G network. In this case, the CN 204b of the LTE RAT may be an EPC, and the mobility management module 306 of the EPC 204b may be a mobility management entity (MME) 306. In another example, consider that the RAT 204 including the CN 204b is an NR / 5G RAT. In this case, the CN 204b may be a 5GC network, and the mobility management module 306 of the 5GC network may be an access and mobility management function (AMF) 306.

[0076] The mobility management module 306 may be configured to receive a registration request from the UE 202 for a communication service. In an example, the mobility management module 306 may receive a registration request when the UE 202 is switched on in an area / location of a RAT 204 supported by the CN 204b. In another example, the mobility management module 306 may receive a registration request when the UE 202 switches from another RAT to an associated CN 204b. In another example, the mobility management module 306 may receive a registration request when the UE 202 reselects a RAT 204 associated with the CN 204b. In another example, the mobility management module 306 may receive a registration request due to idle mode mobility of the UE 202. The received registration request may include a RAC-ID. Alternatively, the received request may not include a RAC-ID.

[0077] When receiving a registration request without RAC-ID, the mobility management module 306 sends a request for UE radio capability information to UE 202 through the associated RAN 204a, and receives UE radio capability information from UE 202 through RAN 204a. The mobility management module 306 sends a request including UE radio capability information and RAT type to UCMF 206, and requests UCMF to allocate RAC-ID to UE 202. The RAT type may be a RAT supported by RAN 204a associated with CN 204b. The mobility management module 306 of CN204b may determine the access type and RAT type based on the 3GPP specification. In an example, the mobility management module 306 of CN204b may determine the RAT type based on the global RAN node ID associated with the N2 interface. In an example, if CN 204b is an EPC, the RAT type may be "4G RAT". In another example, if CN 204b is a 5GC network, the RAT type may be "NR / 5G RAT". In response to the request (for allocation of a RAC-ID) sent to the UCMF 206, the mobility management module 306 receives the RAC-ID of the UE 202 from the UCMF 206. The mobility management module 306 sends the RAC-ID to the UE 202 through the associated RAN 204a.

[0078] Upon receiving the registration request including the RAC-ID, the mobility management module 306 sends a request to the UCMF 206 to resolve the received RAC-ID. The request includes the RAC-ID and the RAT type. The mobility management module 306 receives the UE radio capability information corresponding to the sent RAC-ID from the UCMF 206. In an example, the UE radio capability information may include UE radio capability information encoded in the format of the RAT supported by the CN204b / RAN 204a. In another example, the UE radio capability information may include the encoded UE radio capability information and the RAT type. For further purposes, the mobility management module 306 forwards the UE radio capability information to the associated RAN 204a.

[0079] If the UE radio capability information has been received from the non-RACS support node, the mobility management module 306 can also determine whether the associated RAN 204a is able to decode the received UE radio capability information. If the associated RAN 204a cannot decode the received UE radio capability information, the mobility management module 306 discards the received UE radio capability information and requests the UE radio capability information from the UCMF 206, which can be in the format of the RAT type supported by the RAN 204a associated with the CN 204b. In an example, consider that the CN 204b is an EPC and the mobility management module / MME 306 of the CN 204b receives the UE radio capability information encoded in the "NR / 5G RAT" format. In this case, the mobility management module 306 discards the received UE radio capability information when it is determined that the associated RAN 204a may not be able to decode the received UE radio capability information. The mobility management module / MME 306 requests the UE radio capability information encoded in the "4GRAT" format from the UCMF 206.

[0080] Figure 3 An exemplary block of CN 204b is shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, CN 204b may include fewer or more blocks. In addition, the labels or names of the blocks are only for illustrative purposes and do not limit the scope of the embodiments herein. One or more blocks may be combined together to perform the same or substantially similar functions in CN 204b.

[0081] Figure 4 4 is a block diagram depicting various components of the RAN 204a according to embodiments disclosed herein. The RAN 204a includes a memory 402, a communication interface 404, and a controller 406. The RAN 204a also includes antennas, transceivers, processing circuits, etc. (not shown).

[0082] The memory 402 may store information related to at least one of the UE 202, the associated CN 204b, the coding format of the RAT 204 supported by the RAN 204a, etc., but is not limited thereto.

[0083] The communication interface 404 may be configured to enable the RAN 204 a of the RAT 204 to communicate with at least one of the UE 202 , the CN 204 b of the same RAT 204 , etc. through an interface supported by the corresponding RAT 204 .

[0084] The controller 406 may be at least one of a single processor, multiple processors, multiple homogeneous or heterogeneous cores, multiple central processing units (CPUs) of different kinds, a microcontroller, a special medium, and the like.

[0085] The controller 406 may be configured to receive and decode UE radio capability information of the UE 202 to enable the UE 202 to access the communication service. The controller 406 receives the UE radio capability information of the UE 202 from the associated CN 204b. In an example, the UE radio capability information may include UE radio capability information encoded in a format of a RAT supported by the RAN 204a. In another example, the UE radio capability information may include the encoded UE radio capability information and the RAT type. In an example, the RAT type may be included in the encoded UE radio capability information. In another example, the RAT type may be indicated separately.

[0086] In an embodiment, upon receiving the UE radio capability information encoded in a format of a RAT supported by the RAN 204a, the controller 406 decodes the received UE radio capability information using a decoding format of the RAT type supported by the RAN 204a.

[0087] In an embodiment, upon receiving the encoded UE radio capability information and the associated RAT type, the controller 406 uses the received RAT type and checks whether the received UE radio capability information has been encoded in the format of the RAT type supported by RAN 204a. If the received UE radio capability information has been encoded in the format of the RAT type supported by RAN 204a, the controller 206 decodes the received UE radio capability information using the decoding format of the RAT type supported by RAN 204a. For example, consider that RAN 204a includes an eNB of LTE / 4G RAT, and the controller 406 of RAN 204a receives UE radio capability information from CN / EPC204b. The received UE radio capability information includes the encoded UE radio capability information and the associated RAT type. In the example herein, consider that the RAT type may be "4G RAT". In this case, the controller 406 of RAN / eNB204a determines that the received UE radio capability information is the same encoding format supported by LTE / 4G RAT, and decodes the UE radio capability information using the decoding format of LTE / 4G RAT.

[0088] If the received UE radio capability information is not encoded in a format of a RAT type supported by RAN 204a, the controller 406 converts the received UE radio capability information into a format of a RAT type supported by RAN 204a. The controller 406 then decodes the converted UE radio capability information using a decoding format of a RAT type supported by RAN 204a. For example, consider that RAN 204a includes a gNB of NR / 5G RAT, and the controller 406 of RAN 204a receives UE radio capability information from CN / 5GC network 204b. The UE radio capability information includes encoded UE radio capability information and an associated RAT type. In the example herein, consider that the RAT type may be "4G RAT". In this case, the controller 406 of RAN / gNB 204a determines that the received UE radio capability information is in a different encoding format (i.e., the received UE radio capability information is in an encoding format supported by the LTE / 4G network). Thereafter, the controller 406 converts the received UE radio capability information into a format supported by NR / 5GRAT and decodes the converted UE radio capability information.

[0089] The controller 406 may also be configured to receive a request for UE radio capability information of UE 202 from a non-RACS supporting node (i.e., a CN of a RAT that does not support RACS) through an associated CN 204b. In this case, the controller 406 sends the UE radio capability information to CN204b instead of the RAC-ID of UE202. CN 204b forwards the UE radio capability information to the non-supporting RACS node. Alternatively, upon receiving a request for UE radio capability information from a non-RACS supporting node, the controller 406 converts the UE radio capability information into a format supported by the format of the non-RACS supporting node according to the capabilities of the non-RACS node. The controller 406 sends the converted UE radio capability information to the associated CN 204b. CN 204b forwards the received UE radio capability information to the non-supporting RACS node.

[0090] Figure 4 Exemplary blocks of RAN 204a are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, RAN 204a may include fewer or more blocks. In addition, the labels or names of the blocks are only for illustrative purposes and do not limit the scope of the embodiments herein. One or more blocks may be combined together to perform the same or substantially similar functions in RAN 204a.

[0091] Figure 5 is a block diagram depicting various components of the UCMF 206 for allocating and resolving RAC-IDs according to embodiments disclosed herein.

[0092] UCMF 206 includes a receiving module 502, a RAC-ID allocation module 504, and a RAC-ID resolution module 506. UCMF 206 may also be coupled to a database 508. UCMF 206 stores a unique ID configured for UE 202 by at least one of the manufacturer of UE 202, etc., in database 508, but is not limited thereto. The unique ID allocated to UE 202 may represent UE radio capability information. UCMF 206 may also store UE radio capability ID mapping in database 508.

[0093] The receiving module 502 may be configured to receive a request from the CN 204 of the RAT 204 to allocate a RAC-ID for the UE 202. The request to allocate a RAC-ID may include UE radio capability information and a RAT type. The receiving module 502 sends the request to allocate a RAC-ID to the RAC-ID allocation module 504.

[0094] The receiving module 502 may also be configured to receive a request from the CN 204 of the RAT 204 to resolve the RAC-ID to the UE 202. The request to resolve the RAC-ID may include the RAC-ID and the RAT type of the UE 202. Alternatively, the request to resolve the RAC-ID may include only the RAC-ID of the UE 202. The receiving module 502 sends the request to resolve the RAC-ID to the RAC-ID resolving module 506.

[0095] The RAC-ID allocation module 504 may be configured to allocate a RAC-ID to the UE 202 upon receiving a request to allocate a RAC-ID. The request includes UE radio capability information and a RAT type. When receiving a request to allocate a RAC-ID, the RAC-ID allocation module 504 encodes the received UE radio capability information.

[0096] In an embodiment, the RAC-ID allocation module 504 encodes the UE radio capability information in multiple formats for multiple RATs that the PLMN 208 has supported.

[0097] In another embodiment, the RAC-ID allocation module 504 encodes the received UE radio capability information in a common encoding format (eg, a common “RACS format”).

[0098] In the example here, the UE radio capability information encoded in a common encoding format is as follows:

[0099] {0, (aaaa)}{1, (bbbb)}{2, (cccc)}{3, (dddd)}{4, (eeee)}...

[0100] Wherein, 0, 1, 2, 3, 4... may correspond to the RAT type according to the enumeration provided below:

[0101] RAT type = ENUMERATED {eutra(0),utra,geran-cs,geran-ps,cdma2000-1XRTT,nr(5),eutra-nr,spare1,...}

[0102] Among them, aaaa, bbbb, cccc, dddd, eeee, ... may represent UE radio capability information corresponding to their RAT types (already supported by the PLMN 208).

[0103] Encoding the UE radio capability information in a common encoding format solves the problem of encoding mismatch and makes the UCMF 206 and other participating RACS support nodes unaware of the per-RAT type encoding of the UE radio capability information.

[0104] In another embodiment, the RAC-ID allocation module 504 encodes the UE radio capability information in a specific format for the RAT type indicated in the received request to allocate a RAC-ID to the UE 202 .

[0105] When encoding the UE radio capability information, the RAC-ID allocation module 504 maps the encoded UE radio capability information and the associated RAT type. The RAC-ID allocation module 504 allocates a RAC-ID to the UE radio capability information encoded in the format of the RAT type indicated in the received request. In an example, the RAC-ID allocation module 504 allocates a RAC-ID regardless of the RAT type. In another example, the RAC-ID allocation module 504 allocates a unique RAC-ID for each RAT type. Therefore, the RAC-ID allocated for one RAT type cannot be used for another RAT type. The RAC-ID allocation module 504 maps the RAC-ID with the UE radio capability information encoded in a specific format and the associated RAT type. The RAC-ID allocation module 504 stores the mapping of the RAC-ID with the UE radio capability information encoded in a specific format and the associated RAT type in the UE wireless capability ID mapping.

[0106] The RAC-ID resolution module 506 may be configured to resolve the RAC-ID of the UE 202 upon receiving a request to resolve the RAC-ID of the UE 202. The request includes the RAC-ID and the RAT type of the UE 202. Resolving the RAC-ID includes obtaining UE radio capability information corresponding to the RAC-ID in the received request from a stored UE radio capability ID mapping.

[0107] In an embodiment, to resolve the RAC-ID, the RAC-ID resolution module 506 identifies the RAT type indicated in the received request for resolving the RAC-ID. The RAC-ID resolution module 506 accesses the stored UE radio capability ID mapping from the database 508 and compares the received RAC-ID with the RAC-ID stored in the UE radio capability ID mapping. The UE radio capability ID mapping includes a mapping of the RAC-ID with the UE radio capability information encoded in multiple formats and the associated RAT type. The RAC-ID resolution module 506 retrieves the stored UE radio capability information and the associated RAT type encoded in all formats from the UE radio capability ID mapping corresponding to the RAC-ID matching the received RAC-ID. The RAC-ID resolution module 506 obtains the UE radio capability information corresponding to the received RAT type from the retrieved UE radio capability information and the associated RAT type. The RAC-ID resolution module 506 sends the obtained UE radio capability information to the requested CN 204b.

[0108] For example, consider that the RAC-ID resolution module 506 receives a request from the CN 204b to resolve the RAC-ID of the UE 202, wherein the request includes the RAC-ID and the RAT type (e.g., the RAT type may be "NR / 5G RAT"). In this case, the RAC-ID resolution module 506 retrieves the UE radio capability information and the associated RAT type of the received RAC-ID from the UE radio capability ID mapping stored in the database 508. The RAC-ID resolution module 506 obtains the UE radio capability information from the retrieved UE radio capability information and the associated RAT type, which is associated with "NR / 5G RAT". The obtained UE radio capability information has been encoded in the format of the NR / 5G RAT. The RAC-ID resolution module 506 sends the obtained UE radio capability information to the requested CN 204b.

[0109] In an embodiment, to resolve the RAC-ID, the RAC-ID resolution module 506 identifies the RAT type indicated in the received request for resolving the RAC-ID. The RAC-ID resolution module 506 accesses the stored UE radio capability ID mapping from the database 508 and compares the received RAC-ID with the RAC-ID stored in the UE radio capability ID mapping. The UE radio capability ID mapping includes a mapping of the RAC-ID to the UE radio capability information encoded in a single format and the associated RAT type. The RAC-ID resolution module 506 retrieves the stored UE radio capability information and the associated RAT type from the UE radio capability ID mapping corresponding to the RAC-ID that matches the received RAC-ID. The RAC-ID resolution module 506 sends the acquired UE radio capability information and RAT type to the requested CN 204b.

[0110] Figure 5 Exemplary blocks of UCMF 206 are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, UCMF 206 may include fewer or more blocks. In addition, the labels or names of the blocks are only for illustrative purposes and do not limit the scope of the embodiments herein. One or more blocks may be combined together to perform the same or substantially similar functions in UCMF 206.

[0111] Figure 6 is an example sequence diagram illustrating encoding of UE radio capability information for signaling on various interfaces of a RAT according to embodiments disclosed herein.

[0112] The embodiments herein further explain the encoding of the UE radio capability information by considering the switching of the UE from NR / 5G RAT to LTE / 4G RAT, but it is obvious to those skilled in the art that the switching of the UE between any other RATs may be considered.

[0113] Consider an example scenario such as Figure 6As shown, where UE 202 is powered on in the area of NR / 5G RAT 204. In this case, at step 601, UE 202 sends a registration request (without RAC-ID) to the mobility management module / AMF 306 of the CN / 5GC network in NR / 5G RAT 204 to access communication services. As part of the registration process, at step 602, when RAN / gNB 204a of NR / 5G RAT 204 does not receive UE capability information from AMF 306 in response to the registration request of UE 202, RAN / gNB 204a of NR / 5G RAT 204 sends a UE radio capability request to UE 202. Upon receiving the UE radio capability request, at step 603, UE 202 sends UE radio capability information to gNB 204a, and gNB 204a uploads the UE radio capability information to AMF 306. At step 604, AMF 306 sends a request to UCMF 206 to assign a RAC-ID to UE 202. This request includes UE radio capability information and the RAT type (i.e., "NR / 5G RAT" in this example). At step 605, UCMF 206 encodes the received UE radio capability information in multiple formats supported by PLMN 208. UCMF 206 maps the multiple formats of UE radio capability information with the associated RAT type. In this example, UCMF 206 encodes the received UE radio capability information in the format supported by NR / 5G RAT (e.g., aaa) and the format supported by LTE / 4G RAT (e.g., bbb). UCMF 206 maps the UE radio capability information aaa encoded in the NR / 5G RAT format to the RAT type "NR / 5G RAT" (i.e., <NR / 5G(aaa)). UCMF 206 also maps the UE radio capability information bbb encoded in the LTE / 4G RAT format to the RAT type "LTE / 4G RAT" (i.e., <LTE / 4G(bbb)). UCMF 206 assigns a RAC-ID (e.g., RAC-ID-1) to UE 202, and this RAC-ID corresponds to a set of UE radio capability information encoded in multiple formats of the RAT type supported by UE 202. UCMF 206 stores the mapping of RAC-ID-1 with the UE radio capability information encoded in multiple formats and the associated RAT type in the UE radio capability ID mapping. For example, the mapping may include RAC-ID-1 associated with the UE radio capability information (<NR / 5G(aaa), LTE / 4G(bbb)>). At step 606, UCMF 206 sends the RAC-ID-1 assigned to UE 202 to the requested AMF 306.In step 607, AMF 306 transmits the RAC-ID-1 received from UCMF 206 to UE 202 through gNB 204a. In step 608, UE 202 stores the received RAC-ID-1 against its signaling capability.

[0114] At step 609, UE 202 switches off and on in the area / location of LTE / 4G RAT 204. Thereafter, at step 610, UE 202 sends a registration request to the mobility management module / MME 306 of CN / EPC 204b in LTE / 4G RAT. The registration request includes the RAC-ID-1 of UE 202, which corresponds to the UE radio capability information. At step 611, MME 306 sends a request to UCMF 206 to resolve RAC-ID-1. The request for resolving RAC-ID-1 includes the RAC-ID-1 of UE 202 and the RAT type (i.e., "LTE / 4G RAT" in the example here). At step 612, UCMF 206 obtains the UE radio capability information encoded in the format of LTE / RAT and corresponding to the received wireless RAC-ID-1 from the stored UE radio capability ID mapping. In the example here, UCMF 206 obtains UE radio capability information bbb. UCMF 206 sends the acquired UE radio capability information (encoded in the format of LTE / 4G RAT) to the requested MME 306, which in turn forwards the received UE radio capability information to RAN / eNB 204a of LTE / 4G RAT 204. In step 613, eNB 204a decodes the received UE radio capability information to determine the radio capability of UE 202.

[0115] Figure 7 is another example sequence diagram illustrating encoding of UE radio capability information for transmission via various interface signals according to embodiments disclosed herein.

[0116] The embodiments herein further explain the encoding of the UE radio capability information by considering the switching of the UE from NR / 5G RAT to LTE / 4G RAT, but it is obvious to those skilled in the art that the switching of the UE between any other RATs may be considered.

[0117] Consider an example scenario such as Figure 7As shown, where the UE 202 is powered on in the area of the NR / 5G RAT 204. In this scenario, at step 701, the UE 202 sends a registration request (without RAC-ID) to the mobility management module / AMF 306 of the CN / 5GC network in the NR / 5G RAT 204 to access communication services. As part of the registration process, at step 702, when the RAN / gNB 204a of the NR / 5G RAT 204 does not receive UE capability information from the AMF 306 in response to the registration request of the UE 202, the RAN / gNB 204a of the NR / 5G RAT 204 sends a UE radio capability request to the UE 202. Upon receiving the UE radio capability request, at step 703, the UE 202 sends the UE radio capability information to the gNB 204a, and the gNB 204a uploads the UE radio capability information to the AMF 306. At step 704, the AMF 306 sends a request to the UCMF 206 to assign a RAC-ID to the UE 202. This request includes the UE radio capability information and the RAT type (i.e., "NR / 5G RAT" in this example).

[0118] At step 705, the UCMF 206 encodes the received UE radio capability information in a single format of the RAT type (i.e., "NG / 5G RAT") indicated in the received request. For example, the encoded UE radio capability information can be "aaa". The UCMF 206 assigns a RAC-ID (e.g., RAC-ID-1) to the UE radio capability information encoded in the format of the RAT type indicated in the received request. The UCMF 206 stores the mapping of RAC-ID-1 with the UE radio capability information and the associated RAT type in the UE radio capability ID mapping. For example, the mapping can include RAC-ID-1 associated with the UE radio capability information (<NR / 5G(aaa)). At step 706, the UCMF 206 sends the RAC-ID-1 assigned to the UE 202 to the requested AMF 306. At step 707, the AMF 306 sends the RAC-ID-1 received from the UCMF 206 to the UE 202 via the gNB 204a. At step 708, the UE 202 stores the received RAC-ID-1 in accordance with its signal transmission capability.

[0119] In step 709, UE 202 switches off and on in the area / location of LTE / 4G RAT 204. Thereafter, in step 710, UE 202 sends a registration request to the mobility management module / MME 306 of the CN / EPC 204b in the LTE / 4G RAT. The registration request includes the RAC-ID-1 of UE 202, which corresponds to the UE radio capability information. In step 711, MME 306 sends a request to UCMF 206 to resolve RAC-ID-1. The request to resolve RAC-ID-1 includes the RAC-ID-1 of UE 202. In step 712, UCMF 206 obtains the UE radio capability information and the corresponding RAT type of the received RAC-ID 1 from the stored UE radio capability ID mapping. In the example of this article, the obtained UE radio capability information may be “<NR / 5G(aaa)> In step 713 , UCMF 206 sends the acquired UE radio capability information to the requested MME 306 , and MME 306 forwards the received UE radio capability information to RAN / eNB 204 a of LTE / 4G RAT 204 .

[0120] Upon receiving the UE radio capability information including the RAT type, the eNB 204a determines in step 714 that the received UE radio capability information is 5G / NR RAT, and converts / transcodes the received UE radio capability information into the format of LTE / 4G RAT.

[0121] Figure 8a 800a is a flowchart illustrating a method for processing encoding of UE radio capability information using RACS according to embodiments disclosed herein.

[0122] At step 802, the method includes receiving, by the UCMF 206, a request from the CN 204b for allocating a RAC-ID to a UE 202 registered in the PLMN 208. The request for allocating a RAC-ID to the UE 202 includes UE radio capability information and a RAT type. The RAT type indicates a RAT supported by the RAN 204a connected to the CN 204b.

[0123] At step 804, the method includes encoding, by the UCMF 206, the UE radio capability information based on at least one RAT type indicated in the received request and at least one other RAT type supported by the PLMN 208. In an embodiment, the UCMF 206 encodes the UE radio capability information in a plurality of encoding formats, including an encoding format of the RAT type indicated in the received request and at least one encoding format of at least one other RAT type supported by the PLMN 208. In another embodiment, the UCMF 206 encodes the UE radio capability information in an encoding format of the RAT type indicated in the received request. In another embodiment, the UCMF 206 encodes the UE radio capability information in a common RACS format. The common RACS format includes the UE radio capability information encoded in an encoding format of a RAT supported by the PLMN 208, and a provision indicating a RAT type corresponding to each encoded UE radio capability information.

[0124] At step 806, the method includes assigning, by the UCMF 206, a RAC-ID corresponding to the encoded UE radio capability information to the UE 202. The UCMF 206 performs mapping of the RAC-ID for the encoded UE radio capability information and the corresponding RAT type, and stores the mapping in a UE radio capability ID mapping. The encoded UE radio capability information may be UE radio capability information encoded in a plurality of encoding formats, or UE radio capability information encoded in an encoding format of the RAT type indicated in the received request. Optionally, the UCMF 206 performs mapping of the RAC-ID relative to a common RACS format, and stores the mapping in a UE radio capability ID mapping. The various actions in method 800a may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, the actions may be omitted. Figure 8a Some of the actions listed in .

[0125] Figure 8b 800b is a flow chart depicting a method for resolving the RAC-ID of the UE 202 into UE radio capability information according to embodiments disclosed herein.

[0126] At step 808, the method includes receiving, by UCMF 206, a request from CN 204b for resolving the RAC-ID of UE 202. The request for resolving the RAC-ID includes the RAC-ID and RAT type of UE 202. Optionally, the request for resolving the RAC-ID includes the RAC-ID of UE 202.

[0127] At step 810, the method includes resolving, by the UCMF 206, the RAC-ID of the UE 202 based on the encoding of the UE radio capability information and the received request for resolving the RAC-ID. In an embodiment, if the UE radio capability information is encoded in multiple encoding formats and the received request includes the RAT type and the RAC-ID, the UCMF 206 determines the encoded UE radio capability information of the received RAC-ID and the RAT type from the UE radio capability ID mapping. The UCMF 206 sends the determined encoded UE radio capability information to the CN 204b, which in turn forwards the encoded UE radio capability information to the RAN 204a for decoding.

[0128] In another embodiment, if the UE radio capability information is encoded in a single encoding format and the received request includes a RAC-ID, the UCMF 206 determines the encoded UE radio capability information for the received RAC-ID and the corresponding RAT type according to the UE radio capability ID mapping. The UCMF 206 sends the determined encoded UE radio capability information and the corresponding RAT type to the CN 204b, which in turn forwards the encoded UE radio capability information and the corresponding RAT type to the RAN 204a for decoding.

[0129] In another embodiment, if the UE radio capability information is encoded in a public RACS format and the received request includes a RAC-ID, the UCMF 206 determines the public RACS format for the received RAC-ID from the UE radio capability ID mapping. The UCMF 206 sends the determined public RACS format to the CN 204b, which in turn forwards the received public RACS format to the RAN 204a for decoding.

[0130] The various actions in method 800b may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, the Figure 8b Some of the actions listed in .

[0131] The embodiments disclosed herein may be implemented by at least one software program running on at least one hardware device and performing network management functions to control the elements. Figure 2 , 3 The elements shown in , 4 and 5 may be at least one of a hardware device or a combination of a hardware device and a software module.

[0132] The embodiments disclosed herein describe methods and systems for processing radio capability signaling information of a UE using radio capability signaling optimization (RACS). Therefore, it should be understood that the scope of protection extends to such a program, and in addition to a computer-readable device having a message therein, such a computer-readable storage device contains program code means for implementing one or more steps of the method when the program is run on a server or a mobile device or any suitable programmable device. In a preferred embodiment, the method is implemented by or in conjunction with a software program written in, for example, a very high speed integrated circuit hardware description language (VHDL) or another programming language, or by one or more VHDL or several software modules executed on at least one hardware device. The hardware device can be any kind of programmable portable device. The device can also include, for example, a hardware device, such as an ASIC, or a combination of hardware and software devices, such as an ASIC and an FPGA, or at least one microprocessor and at least one memory having a software module located therein. The method embodiments described herein can be implemented partially in hardware and partially in software. Alternatively, the present invention can be implemented on different hardware devices, for example using multiple CPUs.

[0133] The foregoing description of specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, easily modify and / or adapt such specific embodiments for various applications without departing from the general concepts, and therefore, such adaptations and modifications should and are intended to be understood to be within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the words or terms used herein are for descriptive purposes and not for limitation. Therefore, although the embodiments herein have been described in terms of embodiments, those skilled in the art will recognize that the embodiments herein may be practiced with modifications within the spirit and scope of the embodiments described herein.

Claims

1. A method performed by a user equipment radio capability management function UCMF in a wireless communication system, the method comprising: receiving a first request message for allocating a radio capability identifier ID of a user equipment UE from a first network function NF associated with mobility management, in, The first request message includes UE radio capability information and information about a RAT type associated with an encoding format of the UE radio capability information; assigning the UE radio capability ID associated with the RAT type to the UE radio capability information encoded in the encoding format; and Send the UE radio capability ID to the first NF.

2. The method according to claim 1, further comprising: receiving, from the second NF, a second request message for resolving a second UE radio capability ID, wherein the second request message includes the second UE radio capability ID and a second RAT type; identifying, from mapping information between at least one UE radio capability information and a corresponding UE radio capability ID, second UE radio capability information corresponding to the second UE radio capability ID and the second RAT type; and The second UE radio capability information encoded by a coding format associated with the second RAT type is sent to the second NF.

3. The method according to claim 1, in, The UE radio capability ID is assigned by the manufacturer or the public land mobile network PLMN, and The encoding format of the UE radio capability information is one of the fifth generation system 5GS format or the evolved packet system EPS format.

4. The method according to claim 1, further comprising: include: A mapping between the UE radio capability ID and corresponding UE radio capability information is stored.

5. A method performed by a network function NF associated with mobility management in a wireless communication system, the method comprising: Sending a first request message for allocating a radio capability identifier ID of a user equipment UE to a user equipment radio capability management function UCMF, in, The first request message includes UE radio capability information and information about a RAT type associated with an encoding format of the UE radio capability information; and receiving, from a UCMF, the UE radio capability ID assigned to the UE radio capability information encoded in the encoding format, The UE radio capability ID is associated with the RAT type.

6. The method according to claim 5, further comprising: sending a second request message for resolving a second UE radio capability ID to the UCMF, in, The second request message includes the second UE radio capability ID and a second RAT type; and receiving, from the UCMF, second UE radio capability information corresponding to the second UE radio capability ID, wherein the second UE radio capability information is obtained based on the second UE radio capability ID and the second RAT type from mapping information between at least one UE radio capability information and a corresponding UE radio capability ID, and The second UE radio capability information is encoded in a coding format associated with the second RAT type.

7. The method according to claim 5, in, The UE radio capability ID is assigned by the manufacturer or the public land mobile network PLMN, and The encoding format of the UE radio capability information is one of the fifth generation system 5GS format or the evolved packet system EPS format.

8. The method according to claim 5, in, A mapping between the UE radio capability ID and corresponding UE radio capability information is stored in the UCMF.

9. A user equipment radio capability management function (UCMF) in a wireless communication system, the UCMF comprising: transceiver; and The controller is configured as: receiving, via the transceiver, a first request message for allocating a radio capability identifier ID of a user equipment UE from a first network function NF associated with mobility management, in, The first request message includes UE radio capability information and information about a RAT type associated with an encoding format of the UE radio capability information, assigning the UE radio capability ID associated with the RAT type to the UE radio capability information encoded in the encoding format, and The UE radio capability ID is sent to the first NF via the transceiver.

10. The UCMF according to claim 9, in, The controller is also configured to: receiving, via the transceiver, from a second NF a second request message for resolving a second UE radio capability ID, wherein the second request message includes the second UE radio capability ID and a second RAT type; and The second UE radio capability information encoded by a coding format associated with the second RAT type is sent to the second NF via the transceiver.

11. The UCMF according to claim 9, in, The UE radio capability ID is assigned by the manufacturer or the public land mobile network PLMN, and The encoding format of the UE radio capability information is one of the fifth generation system 5GS format or the evolved packet system EPS format.

12. The UCMF according to claim 9, in, The controller is further configured to store a mapping between the UE radio capability ID and corresponding UE radio capability information.

13. A network function NF associated with mobility management in a wireless communication system, the NF comprising: transceiver; and The controller is configured as: sending, via the transceiver, a first request message for allocating a radio capability identifier ID of a user equipment UE to a user equipment radio capability management function UCMF, in, The first request message includes UE radio capability information and information about a RAT type associated with an encoding format of the UE radio capability information; and receiving, via the transceiver from the UCMF, the UE radio capability ID assigned to the UE radio capability information encoded in the encoding format, The UE radio capability ID is associated with the RAT type.

14. The NF according to claim 13, in, The controller is also configured to: sending, via the transceiver, to the UCMF a second request message for resolving a second UE radio capability ID, wherein the second request message includes the second UE radio capability ID and a second RAT type; and receiving, via the transceiver, from the UCMF, second UE radio capability information corresponding to the second UE radio capability ID, wherein the second UE radio capability information is obtained based on the second UE radio capability ID and the second RAT type from mapping information between at least one UE radio capability information and a corresponding UE radio capability ID, and The second UE radio capability information is encoded in a coding format associated with the second RAT type.

15. The NF according to claim 13, in, The UE radio capability ID is assigned by the manufacturer or the public land mobile network PLMN, and The encoding format of the UE radio capability information is one of the fifth generation system 5GS format or the evolved packet system EPS format.

Images