Method and apparatus for managing radio resource control message 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). The present disclosure discloses methods, apparatuses and systems for managing Radio Resource Control (RRC) message in a wireless communication system. The method includes transmitting, by a network entity, a Radio Resource Control (RRC) message to a User Equipment (UE), wherein the RRC message comprises one or more information blocks. Each of the one or more information blocks comprises a plurality of containers based on a category of the information, wherein the category of information corresponds to at least one of a device type, a service type, and a feature type.

Description

METHOD AND APPARATUS FOR MANAGING RADIO RESOURCE CONTROL MESSAGE IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present disclosure relates to wireless communication, and more particularly relates to method and apparatus, and system for managing radio resource control (RRC) messages in a wireless communication system.

[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] The present disclosure relates to wireless communication, and more particularly relates to method and apparatus, and system for managing radio resource control (RRC) messages in a wireless communication system.

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

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

[0010] According to an embodiment of the present disclosure, disclosed herein is a method. The method includes transmitting, by a network entity, a Radio Resource Control (RRC) message to a User Equipment (UE), wherein the RRC message comprises one or more information blocks. Each of the one or more information blocks comprises a plurality of containers based on a category of the information, wherein the category of information corresponds to at least one of a device type, a service type, and a feature type.

[0011] According to an embodiment of the present disclosure, disclosed herein is a system. The system is configured to transmit a Radio Resource Control (RRC) message to a User Equipment (UE), wherein the RRC message comprises one or more information blocks. Each of the one or more information blocks comprises a plurality of containers based on a category of the information, wherein the category of information corresponds to at least one of a device type, a service type, and a feature type.

[0012] According to an embodiment of the present disclosure, a method is disclosed. The method includes receiving, by a User Equipment (UE), a Radio Resource Control (RRC) message to a user equipment (UE), wherein the RRC message comprises one or more information blocks. Each of the one or more information blocks comprises a plurality of containers based on a category of the information, wherein the category of information corresponds to at least one of a device type, a service type, and a feature type.

[0013] According to an embodiment of the present disclosure, disclosed herein is a system. The system is configured to receive a Radio Resource Control (RRC) message from a network entity, wherein the RRC message comprises one or more information blocks. Each of the one or more information blocks comprises a plurality of containers based on a category of the information, wherein the category of information corresponds to at least one of a device type, a service type, and a feature type.

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

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

[0016] These and other features, aspects, and advantages of the present invention 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:

[0017] FIG. 1 illustrates the NR protocol stack, in accordance with existing art;

[0018] FIG. 2 illustrates Radio Resource Control (RRC) Abstract Syntax Notation One (ASN.1) structure when introducing a new service, in accordance with existing art;

[0019] FIG. 3 illustrates a RRC ASN.1 structure, in accordance with existing art;

[0020] FIG. 4 illustrates verticals and services introduced in Fifth-Generation (5G) network, in accordance with existing art;

[0021] FIG. 5 illustrates a 5G Core Network (5GC) architecture, in accordance with an embodiment of the present disclosure;

[0022] FIG. 6 illustrates a flow chart depicting a method for managing RRC message in the 5GC network, in accordance with an embodiment of the present disclosure;

[0023] FIG. 7A illustrates an RRC message, in accordance with existing art;

[0024] FIG. 7B illustrates the RRC message with containers arranged in a sequential manner, in accordance with an embodiment of the present disclosure;

[0025] FIG. 8A illustrates an RRC ASN.1 structure with containers arranged in the sequential manner, in accordance with an embodiment of the present disclosure;

[0026] FIG. 8B illustrates an exemplary System Information Block 1 (SIB 1) block with containers arranged in the sequential manner, in accordance with an embodiment of the present disclosure;

[0027] FIGS. 9A-9B illustrate the RRC message with containers arranged in a hierarchical manner, in accordance with an embodiment of the present disclosure;

[0028] FIG. 9C illustrates an exemplary SIB 1 block with containers arranged in the hierarchical manner, in accordance with an embodiment of the present disclosure;

[0029] FIG. 10 illustrates a flow chart depicting a method for managing RRC message in the 5GC network, in accordance with an embodiment of the present disclosure;

[0030] FIG. 11 illustrates an environment for managing RRC message in the 5GC network, in accordance with an embodiment of the present disclosure;

[0031] FIG. 12 illustrates a block diagram of a UE according to various embodiments of the present disclosure; and

[0032] FIG. 13 illustrates a block diagram of a base station or a network entity according to various embodiments of the present disclosure.

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

[0034] For the purpose of promoting an understanding of the principles of the present disclosure, reference will now be made to the various embodiments and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the present disclosure is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the present disclosure as illustrated therein being contemplated as would normally occur to one skilled in the art to which the present disclosure relates.

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

[0036] Whether or not a certain feature or element was limited to being used only once, it may still be referred to as “one or more features” or “one or more elements” or “at least one feature” or “at least one element.” Furthermore, the use of the terms “one or more” or “at least one” feature or element does not preclude there being none of that feature or element, unless otherwise specified by limiting language including, but not limited to, “there needs to be one or more…” or “one or more elements is required.”

[0037] Reference is made herein to some “embodiments.” It should be understood that an embodiment is an example of a possible implementation of any features and / or elements of the present disclosure. Some embodiments have been described for the purpose of explaining one or more of the potential ways in which the specific features and / or elements of the proposed disclosure fulfill the requirements of uniqueness, utility, and non-obviousness.

[0038] Use of the phrases and / or terms including, but not limited to, “a first embodiment,” “a further embodiment,” “an alternate embodiment,” “one embodiment,” “an embodiment,” “multiple embodiments,” “some embodiments,” “other embodiments,” “further embodiment”, “furthermore embodiment”, “additional embodiment” or other variants thereof do not necessarily refer to the same embodiments. Unless otherwise specified, one or more particular features and / or elements described in connection with one or more embodiments may be found in one embodiment, or may be found in more than one embodiment, or may be found in all embodiments, or may be found in no embodiments. Although one or more features and / or elements may be described herein in the context of only a single embodiment, or in the context of more than one embodiment, or in the context of all embodiments, the features and / or elements may instead be provided separately or in any appropriate combination or not at all. Conversely, any features and / or elements described in the context of separate embodiments may alternatively be realized as existing together in the context of a single embodiment.

[0039] Any particular and all details set forth herein are used in the context of some embodiments and therefore should not necessarily be taken as limiting factors to the proposed disclosure.

[0040] The terms “comprises”, “comprising”, 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. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by “comprises... a” does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.

[0041] The term “couple” and the derivatives thereof refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with each other. The terms “transmit”, “receive”, and “communicate” as well as the derivatives thereof encompass both direct and indirect communication. The term “or” is an inclusive term meaning “and / or”. The phrase “associated with,” as well as derivatives thereof, refer to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term “controller” refers to any device, system, or part thereof that controls at least one operation. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C, and any variations thereof. As an additional example, the expression “at least one of a, b, or c” may indicate only a, only b, only c, both a and b, both a and c, both b and c, all of a, b, and c, or variations thereof. Similarly, the term “set” means one or more. Accordingly, the set of items may be a single item or a collection of two or more items.

[0042] Moreover, multiple functions described below may be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as Read Only Memory (ROM), Random Access Memory (RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data may be permanently stored and media where data may be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0043] The present disclosure discloses an advanced Abstract Syntax Notation One (ASN.1) structure for Radio Resource Control (RRC) in a Fifth-Generation (5G) network. In one embodiment, information related to devices, services, and features associated with the 5G network are reorganized based on specific categorization to form the RRC ASN.1 structure. In another embodiment, the information related to devices, services, and features is re-organized under different categories based on the device types, services, etc., to form the RRC ASN.1 structure. In yet another embodiment, the information related to the devices, the services, and the features are organized hierarchically to form the RRC ASN.1 structure.

[0044] It should be noted that the terms "services," "features," and "verticals" are often used interchangeably. In one embodiment, a device type may be defined based on radio and performance requirements. For example, Redcap devices have reduced New Radio (NR) complexity along with substantially good data rate, latency, and power performance. While Enhanced Mobile Broadband (eMBB) devices may have all the advanced features to support high data rates and latency requirements. 5G has introduced multiple device types and 6G standards may even formalize these device types. Examples of such device types may include, but are not limited to eMBB devices, Ultra-Reliable, Low-Latency Communication (uRLLC) devices, Massive Machine-Type Communication (MMTC) devices, RedCap devices, and enhanced RedCap devices. Further, any enhancement performed over the current radio capability is a horizontal service or feature of RRC. For example, carrier aggregation combines multiple frequency bands to provide improved data rates, which is an enhancement over the existing radio protocol stack. Another example is Discontinuous Reception (DRX), which is used to enable power-efficient radio operation. The vertical services provide a specific use case to UE and are generally built on top of existing horizontal features. For instance, Time Sensitive Communication (TSN) uses the existing capabilities to enable deterministic latencies in the system.

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

[0046] For the sake of clarity, the first digit of a reference numeral of each component of the present disclosure is indicative of the Figure number, in which the corresponding component is shown. For example, reference numerals starting with digit “1” are shown at least in Figure 1. Similarly, reference numerals starting with digit “2” are shown at least in Figure 2. Further, similar reference numerals have been used to represent similar components in the Figures.

[0047] It should be noted that the terms “RRC ASN.1 structure” and “RRC message” have been interchangeably used throughout the description and the drawings.

[0048] The wireless communication industry has seen significant advancements over the past few decades, driven by the increasing demands of mobile users. Initially, Second Generation (2G) standards supported basic calling and text messaging. As technology evolved, Third Generation (3G) standards introduced internet access on mobile devices, and Fourth Generation (4G) technology ushered in the era of mobile broadband, enabling high-speed data services such as video streaming. Further, Fifth Generation (5G) technology addresses the growing demand for high-speed data and ultra-reliable, low-latency communication, supporting a wide range of use cases including immersive experiences and ubiquitous connectivity.

[0049] With technological advancements, there is a noticeable demand for immersive experiences and ubiquitous connectivity, in addition to sustainability and security. Currently, the device ecosystem is expanding, encompassing different types of wearables, smartphones, and Internet of Things (IoT) devices. However, such devices pose challenges for existing 5G networks, which must accommodate their diverse requirements. Consequently, there is a need to develop advanced 5G and Sixth Generation (6G) technologies capable of meeting these increasing demands.

[0050] The 5G network supports three primary use case categories, i.e., Enhanced Mobile Broadband (eMBB), Massive Machine-Type Communication (mMTC), and Ultra-Reliable, Low-Latency Communication (uRLLC). 5G network architecture includes a Radio Access Network (RAN) and a Core Network (CN), which are structured to meet diverse communication needs. The RAN manages radio-related functions, including scheduling and resource management, while the CN is responsible for higher-level functions such as authentication and charging. The 5G network architecture further includes a Next-Generation NodeB (gNB). The gNB provides user plane and control plane protocol termination for New Radio (NR) devices. The gNB is based on NR protocol and plays a crucial role in managing communication between User Equipment (UE) and the 5G network. The NR protocol includes both user plane and control plane protocols, as shown in FIG. 1. FIG. 1 illustrates the NR protocol stack, in accordance with existing art. As shown in FIG. 1, the NR user plane protocol stack 101a consists of a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. The NR control plane protocol stack 101b of a Radio Resource Control (RRC) layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer. These protocol entities are responsible for managing various aspects of data transmission across the network, ensuring the efficient transfer of information between devices and the network. It can be noted that the control plane protocol stack 101b is similar to the user plane protocol stack 101a, with a notable difference being the inclusion of the RRC layer in place of the SDAP layer.

[0051] The primary responsibilities of the RRC layer involve managing the setup of connections, supporting mobility, and ensuring security within the cellular network. Further, the RRC layer is responsible for delivering system information to users, performing channel measurements, and overseeing mobility management. For example, the Master Information Block MIB broadcasts parameters to acquire System Information Block 1 (SIB1) from the cell. Further, SIB1 is responsible for cell selection information, Public Land Mobile Network (PLMN) identity, and scheduling info. Additionally, the RRC layer handles cell selection and reselection, facilitates handovers, and manages the establishment, maintenance, and release of RRC connections. The RRC layer is also responsible for allocating temporary identifiers, configuring Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs), controlling access, and ensuring security. Furthermore, the RRC layer plays a role in Quality of Service (QoS) management and the transfer of Non-Access Stratum (NAS) information.

[0052] As the mobile network grows increasingly heterogeneous, the complexity of RRC has also grown. This presents several challenges, including the expansion of RRC specifications, which continue to increase with each new standard release. For instance, 3GPP Release 18 consists of over 1,600 pages of specifications, much of which is driven by the need to support an increasingly diverse range of devices and services. Additionally, RRC specifications are tightly interwoven, making it difficult to implement a modular framework for the protocol. Dependencies between various components, such as system information and connection management, hinder the development of a modular codebase. For example, system information and connection management are interdependent for establishing a radio connection with a UE. This leads to internal dependencies which do not allow for modular architecture.

[0053] The complexity of RRC specifications and code also poses significant challenges when introducing new services. Any change to the network or the addition of a new service requires a deep understanding of the intricate specifications and dependencies within the RRC code. As a result, introducing new services can be both time-consuming and error-prone. Moreover, testing new services is complicated due to the tight interdependencies among RRC components, making it difficult to isolate and test specific modules.

[0054] FIG. 2 illustrates the RRC Abstract Syntax Notation One (ASN.1) structure when introducing a new service, in accordance with existing art. FIG. 2 illustrates the contents of SIB1 and MIB, highlighting how different parameters, such as the intraFreqReselection parameter, are added to these blocks. For instance, in the ASN.1 structure, the intraFreqReselection parameter may be included in the MIB signal for conventional UE, while it is included in SIB1 under a different Information Element (IE) for specialized devices like Redcap UEs. This modification process, as shown in FIG. 2, is often carried out in an ad-hoc manner, leading to inconsistencies in how new services are added to the network. FIG. 2 underscores the lack of a clear framework for incorporating new services and the potential complications that arise when different verticals require different data elements.

[0055] FIG. 3 illustrates a RRC ASN.1 structure, in accordance with existing art. As shown, ASN.1 is a formal notation used for describing the structure and encoding of data exchanged between different entities in a wireless system. ASN.1 provides a standardized way to describe the syntax and semantics of messages. ASN.1 enables interoperability between different vendors and equipment. RRC uses ASN.1 encoding to send data or air interface.

[0056] Further, 5G RRC handles multiple device types, enables different services, and provides multiple features to enable flexibility to support multiple use cases. The different devices supported by 5G may include 6G mobile broadband, 6G URLLC, 6G IOT, 6G A-IOT, integrating communication sensing and positioning devices, sidelink and mesh network devices, Non-terrestrial mobile, and ambient IoT devices. The services or verticals provided by the 5G include uRLLC, Internet Protocol (IP) Multimedia Subsystem (IMS), Multicast and Broadcast Services (MBS), RedCap, sidelink, sensing and localization, mobility, and Minimization of Drive Tests (MDT). The verticals are functional services provided by the 5G network in addition to connectivity service. These services may or may not use horizontal services. The features or horizontal services include data rate enhancements, power efficiency, and access control. The horizontal services are derived from enhancements to basic radio protocol functionalities. The basic radio protocol functionalities include measurements, connection management, System Information (SI), and AS security. The basic radio functionalities are essential for establishing radio connection and all the services / verticals depend on these functionalities.

[0057] Further, new verticals or services have been introduced in the 5G network, as shown in FIG. 4. Vertical-related information is spread across multiple messages and IEs. However, the existing specifications are not designed considering the verticals from the start, therefore every IE is added in an ad-hoc manner.

[0058] In addition, as the network evolves, the integration of multiple services into the RRC specifications is anticipated. Consequently, there is a need for a well-defined framework governing the introduction of services within the network, with a particular emphasis on the RRC specification. Further, the rapid evolution of network technologies and the increasing diversity of connected devices will lead to a highly heterogeneous ecosystem in 6G networks. As the number and variety of devices continue to grow, there is a critical need for an RRC framework capable of efficiently supporting this diverse environment. The framework must be adaptable enough to cater to a wide range of devices with varying communication capabilities and requirements.

[0059] Accordingly, there is a need for techniques to overcome the above-mentioned and other related problems.

[0060] FIG. 5 illustrates a 5G Core Network (5GC) architecture 500, in accordance with an embodiment of the present disclosure. As shown, at the user end, a User Equipment (UE) 501 connects to a Radio Access Network (RAN) 503, which then interfaces with the Core Network (CN). The 5GC architecture 500 consists of various Network Functions (NFs). For example, an Access and Mobility Management Function (AMF) 505 handles user access and mobility, while a Session Management Function (SMF) 507 is responsible for managing sessions and controlling data flow. A User Plane Function (UPF) 509 facilitates the routing of user data between the RAN 503 and Data Network (DN) 511, which represents external networks like the Internet or private enterprise systems.

[0061] Supporting functions within the 5GC architecture 500 include an Authentication Server Function (AUSF) 513 for user authentication, Unified Data Management (UDM) 515 for subscriber data management, and Policy Control Function (PCF) 517 which regulates network policies. Additionally, Network Repository Function (NRF) 519 maintains a registry of available network functions, Network Exposure Function (NEF) 521 allows external applications to access network capabilities, and Network Slice Selection Function (NSSF) 523 ensures appropriate network slicing for different services. An Application Function (AF) 525 enables interaction with application-specific services.

[0062] FIG. 5 also highlights key interfaces within the 5G core. The N1 interface connects the UE 501 to the AMF 505 for control signaling, while N2 links the RAN 503 and the AMF 505 for control plane communication. N3 facilitates the user data path between the RAN 503 and the UPF 509, while N4 connects the SMF 507 and the UPF 509 for session management. The N6 interface links the UPF 509 to external data networks, and N9 allows communication between different UPFs. This modular and service-based architecture enhances flexibility, scalability, and performance in the 5G CN, offering significant improvements over previous generations.

[0063] FIG. 6 illustrates a flow chart depicting a method 600 for managing RRC message in the 5GC network 500, in accordance with an embodiment of the present disclosure. In an embodiment, the method 600 may be performed by a network entity, such as a Base Station (not shown in FIG.) included in the 5GC network 500. As shown, at step 601, the method 600 may include transmitting a Radio Resource Control (RRC) message to the UE 501. In an embodiment, the RRC message comprises one or more information blocks. Each of the one or more information blocks comprises a plurality of containers based on a category of the information. The category of information may correspond to at least one of a device type, a service type, and a feature type. The device type may include, but is not limited to eMBB devices, uRLLC devices, MMTC devices, RedCap devices, and enhanced RedCap devices. The service type may include, but is not limited to Internet Protocol (IP) Multimedia Subsystem (IMS), Multicast and Broadcast Services (MBS), and joint sensing and communication services. The feature type may include, but is not limited to carrier aggregation, mobility, dual connectivity, and Discontinuous Reception (DRX).

[0064] In an embodiment, prior to transmitting the RRC message, at step 601A, the method 600 may include identifying the category of information among a plurality of information. Thereafter, at step 601B, the method 600 may include defining the plurality of containers based on the category of information. For example, based on the diversity of device types and the service / features used by the device types, different RRC ASN.1 structure can be adopted. If each device type has a very distinct service / feature configurations, then the plurality of containers may be arranged in a hierarchical manner. If multiple device types use similar configurations then the plurality of containers may be arranged in a sequential manner. The dependency between features / services and device types governs which type of ASN structure is adopted. The hierarchical and sequential manners are discussed in detail in the following paragraphs.

[0065] In an embodiment, when the plurality of containers is based on the category of information, the plurality of containers may be arranged in one of a sequential manner or a hierarchical manner based on the corresponding category of the information. The sequential manner of the plurality of containers is further explained in reference to FIGS. 7A-8B. The hierarchical manner of the plurality of containers is further explained in reference to FIGS. 9A-9C.

[0066] FIG. 7A illustrates an RRC message, in accordance with existing art. As shown in FIG. 7A, two verticals and one service are defined in SIB 1. Accordingly, multiple parameters need to be added for each vertical. Accordingly, the addition of new services is difficult. Further, the UE 501 needs to filter the relevant parameters based on the verticals supported by the UE 501. On the contrary, in an embodiment, the one or more information blocks in the RRC message comprise a common container. The common container includes a list of at least one of the supported devices corresponding to the device type, supported services corresponding to the service type, supported features corresponding to the feature type, and common information for camping on a cell. The one or more information blocks make it easier to add new services. Such RRC messages are further defined in reference to FIGS. 7B-8B.

[0067] FIG. 7B illustrates the RRC message with containers arranged in the sequential manner, in accordance with an embodiment of the present disclosure. In an embodiment of the present disclosure, the information related to the devices, the services, and the features are reorganized based on specific categorization to form the RRC ASN.1 structure, as shown in FIG. 7B. Accordingly, the conventional RRC ASN.1 structure is retained while re-organizing the information related to the devices, the services, and the features based on the specific categorization. As shown in FIG. 7B, Information Elements (IEs) are typically added in an ad-hoc manner within the System Information(SI), reflecting modifications across different releases. Accordingly, in an embodiment, the IEs are reorganized based on categorizations like device types, features, or services. As shown in FIG. 7B, each of the plurality of containers may be structured around the device type, the feature type, and / or the service type. Each of the plurality of containers may consolidate all relevant parameters for the respective feature or device type. Consequently, the UE 501 can efficiently filter pertinent information from the received SI, enhancing its ability to process data effectively. Such modular information architecture fosters the development of cloud-friendly networks, enabling more flexible and scalable deployments. In an exemplary embodiment, the plurality of containers may include three types of containers, i.e., the device type container, the feature type container, and the service type container. The device type container may be defined as a Redcap Device. The vertical or feature-type container may be defined as Feature-Mobility. The service type container may be defined as Service-MBS. These containers serve to organize and encapsulate relevant parameters and information associated with their respective categories.

[0068] In a further embodiment, the information related to the devices, the services, and the features may be re-organized under different categories based on the device types, services, etc., to form the RRC ASN.1 structure. FIG. 8A illustrates an RRC ASN.1 structure 800A with containers arranged in the sequential manner, in accordance with an embodiment of the present disclosure. As shown, the RRC ASN.1 structure 800A facilitates the dynamic organization of information, exemplified by the inclusion of SIB1. In an embodiment, each of the plurality of containers may aggregate details regarding various features, device types, and services provided by the 5GC network 500. As shown, the RRC ASN.1 structure 800A includes the common container, termed as CommonInfo. The common container is capable of accommodating additional types of information beyond its initial scope. Further, new IEs need to be defined for CommonInfo and are given below.

[0069]

[0070] Further, the CommonInfo container may also have other parameters to inform UE about the details of system information. For example, in SIB1, only limited information may be shared, and the network can dynamically allocate other SIBs from SIB2-25 to other features, devices, or services. For instance, CommonInfo can have the following IE as given below.

[0071]

[0072] This information may be used by the UE 501 to further get the relevant information. Unlike the current 5G network, this information may be changed dynamically based on network requirements and configurations. Further, each service type or device type may have its own parameters in the container. An example of each service type is given below.

[0073]

[0074] An example of device type is shown below.

[0075]

[0076] An example of vertical is given below.

[0077]

[0078] Accordingly, in an exemplary embodiment, the device-type container may have various parameters, such as Cell Barred, Config related parameters, and Cell Selection / Reselection parameters. Similarly, the service type container may have various parameters, such as Configuration related to service and list of frequency. Further, FIG. 8B illustrates an exemplary SIB 1 block 800B with containers arranged in the sequential manner, in accordance with an embodiment of the present disclosure. As shown, each category, i.e., the feature, the device, and the service has its container. Some Information may be common and may be mentioned in the common container. Information organization is done in the sequential manner and hence each type has its container. Further, as shown, the SIB1 800B includes the commonInfo. It should be noted that FIGS. 8A-8B only illustrates some examples for explanation purposes and multiple options are possible to arrange the information under each block.

[0079] FIGS. 9A-9B illustrate the RRC messages 900A, and 900B with containers arranged in a hierarchical manner, in accordance with an embodiment of the present disclosure. In one embodiment, each of the plurality of containers is organized in the hierarchical manner to form the RRC ASN.1 structure. Specifically, the information is organized in a hierarchical manner, which often mirrors the network’s utilization of network capabilities. The RRC ASN.1 structure may also contain dynamic information. The dynamic information may be hierarchically organized. For example, the device may support specific services, that can form part of the container. Service can also be based on multiple features, that can be part of the service-based container. Accordingly, each container in the hierarchical manner corresponding to the device type comprises one or more containers corresponding to the service type, and each container corresponding to the service type comprises one or more containers corresponding to the feature type. Further, the one or more information blocks may comprise a common container. The common container may include a common block containing common information applicable to the plurality of containers. Common information elements can be cell selection information, cell barred information, et. In an embodiment, the common block may contain information similar to the commonInfo of FIGS. 8A-8B.

[0080] As shown in FIG. 9A, each of the two different device types, device-1 and device-2 has its relevant features and services. Accordingly, the device-1 container includes a service-type container and a feature-type container. The device-2 container includes only a feature-type container. In another example shown in FIG. 9B, the device-1 container includes a service-type container which includes a feature-type container. However, the device-2 container includes only a service-type container.

[0081] FIG. 9C illustrates an exemplary SIB 1 block 900C with containers arranged in the hierarchical manner, in accordance with an embodiment of the present disclosure. As shown, two distinct devices, RedCap and eMBB are shown in the SIB 1 block. Each device type has its relevant features and services. For instance, an eMBB user may require access to mobility services, IMS services, and other high-bandwidth services. On the other hand, these services may not be relevant for RedCap users. The RedCap container may have services that are relevant for Redcap users such as DRX or SDT. In the hierarchical framework, an eMBB container may encompass services specifically designed for the eMBB users. Similarly, the RedCap container may encompass services specifically designed for the RedCap users, such as DRX or SDT. Further, as shown, the SIB1 900C includes the common block.

[0082] FIG. 10 illustrates a flow chart depicting a method 1000 for managing RRC message in the 5GC network, in accordance with an embodiment of the present disclosure. In an embodiment, the method 1000 may be performed by the UE 501. As shown, at step 1001, the method 1000 may include receiving a Radio Resource Control (RRC) message from the network entity. In an embodiment, the RRC message may comprise one or more information blocks. Each of the one or more information blocks comprises a plurality of containers based on a category of the information. The category of information may correspond to at least one of a device type, a service type, and a feature type. The plurality of containers may be arranged in manners as described in reference to FIGS. 7A-9C. Hence, the description of the same is not provided here for the sake of brevity of the disclosure.

[0083] FIG. 11 illustrates an environment for managing RRC messages in the 5GC network 500, in accordance with an embodiment of the present disclosure. As shown, the environment 1000 may include a network entity 1110 connected to a UE 1120. The network entity 1110 may include a system 1130 and the UE 1120 may include a system 1140. In an embodiment, the network entity 1110 may correspond to a BS included in the 5GC network 500. Further, the UE 1120 may correspond to the UE 501.

[0084] In an embodiment, the system 1130 may include, but is not limited to at least one processor 1102 (herein referred to as a processor), a memory 1104, and an interface 1106. The memory 1104, and the interface 1106 may be coupled to the processor 1102. In an embodiment, the system 1130 may be configured to perform the techniques described in reference to FIGS. 6-9C. In another embodiment, the processor 1102 may be configured to perform the techniques described in reference to FIGS. 6-9C.

[0085] The processor 1102 can be a single processing unit or several units, all of which could include multiple computing units. The processor 1102 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and / or any device that manipulates signals based on operational instructions. Among other capabilities, the processor 1102 is configured to fetch and execute computer-readable instructions and data stored in the memory 1104.

[0086] The memory 1104 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. Further, the memory 1104 may include an operating system for performing one or more tasks of the system 1130, as performed by a generic operating system in the communications domain.

[0087] In an embodiment, the system 1140 may include, but is not limited to at least one processor 1101 (herein referred to as a processor), a memory 1103, and an interface 1105. The memory 1103, and the interface 1105 may be coupled to the processor 1101. In an embodiment, the system 1140 may be configured to perform the techniques described in reference to FIG. 10. In another embodiment, the processor 1101 may be configured to perform the techniques described in reference to FIG. 10.

[0088] The processor 1101 can be a single processing unit or several units, all of which could include multiple computing units. The processor 1101 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and / or any device that manipulates signals based on operational instructions. Among other capabilities, the processor 1101 is configured to fetch and execute computer-readable instructions and data stored in the memory 1103.

[0089] The memory 1103 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. Further, the memory 1103 may include an operating system for performing one or more tasks of the system 1140, as performed by a generic operating system in the communications domain.

[0090] FIG. 12 illustrates a block diagram of a UE according to various embodiments of the present disclosure. Furthermore, the UE of FIG. 12 corresponds to the UE of FIG. 5 and FIG. 11.

[0091] As shown in FIG. 12, the UE according to an embodiment may include a transceiver 1210, a memory 1220, and a processor 1230. The transceiver 1210, the memory 1220, and the processor 1230 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 1230, the transceiver 1210, and the memory 1220 may be implemented as a single chip. Also, the processor 1230 may include at least one processor.

[0092] The transceiver 1210 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 1210 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 1210 and components of the transceiver 1210 are not limited to the RF transmitter and the RF receiver.

[0093] Also, the transceiver 1210 may receive and output, to the processor 1230, a signal through a wireless channel, and transmit a signal output from the processor 1230 through the wireless channel.

[0094] The memory 1220 may store a program and data required for operations of the UE. Also, the memory 1220 may store control information or data included in a signal obtained by the UE. The memory 1220 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.

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

[0096] FIG. 13 illustrates a block diagram of a base station or a network entity according to various embodiments of the present disclosure. Furthermore, the network entity of FIG. 13 corresponds to the network entity of FIG. 5 and FIG. 11.

[0097] As shown in FIG. 13, the base station(or the network entity receiver) according to an embodiment may include a transceiver 1310, a memory 1320, and a processor 1330. The transceiver 1310, the memory 1320, and the processor 1330 of the base station(or the network entity receiver) may operate according to a communication method of the base station(or the network entity receiver) described above. However, the components of the base station(or the network entity receiver) are not limited thereto. For example, the base station may include more or fewer components than those described above. In addition, the processor 1330, the transceiver 1310, and the memory 1320 may be implemented as a single chip. Also, the processor 1330 may include at least one processor.

[0098] The transceiver 1310 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 1310 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 1310 and components of the transceiver 1310 are not limited to the RF transmitter and the RF receiver.

[0099] Also, the transceiver 1310 may receive and output, to the processor 1330, a signal through a wireless channel, and transmit a signal output from the processor 1330 through the wireless channel.

[0100] The memory 1320 may store a program and data required for operations of the base station(or the network entity receiver). Also, the memory 1320 may store control information or data included in a signal obtained by the base station. The memory 1320 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.

[0101] The processor 1330 may control a series of processes such that the base station(or the network entity receiver) operates as described above. For example, the transceiver 1310 may receive a data signal including a control signal transmitted by the terminal or the network entity or the base station, and the processor 1330 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.

[0102] Accordingly, the present disclosure provides various advantages. For example, the services / verticals are organized to omit the redundant information and to facilitate the UE / network to only read the relevant information thereby reducing the latency as well as processing. Further, the disclosed RRC ASN.1 structure (RRC message) reduces the development and testing effort due to a cleaner and more organized way of adding information in the RRC. Further, the disclosed RRC message is more structured, facilitating efficient management and retrieval of information pertaining to specific device types, features, or services. The disclosed techniques may also be extended to other components of RRC, such as measurements, security, and UE capability.

[0103] In this application, unless specifically stated otherwise, the use of the singular includes the plural, and the use of “or” means “and / or.” Furthermore, the use of the terms “including” or “having” is not limiting. Any range described herein will be understood to include the endpoints and all values between the endpoints. Features of the disclosed embodiments may be combined, rearranged, omitted, etc., within the scope of the invention to produce additional embodiments. Furthermore, certain features may sometimes be used to advantage without a corresponding use of other features.

[0104] While at least one exemplary embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist.

Claims

1.A method performed by a network entity in a wireless communication system, the method comprising:transmitting, to a user equipment (UE), a Radio Resource Control (RRC) message,wherein the RRC message comprises one or more information blocks, wherein each of the one or more information blocks comprises:a plurality of containers based on a category of the information, wherein the category of information corresponds to at least one of a device type, a service type, and a feature type.2.The method of in claim 1, wherein in case the plurality of containers is based on the category of information, the plurality of containers are arranged in one of a:sequential manner based on the corresponding category of the information;hierarchical manner based on the corresponding category of the information, wherein each container corresponding to the device type comprises one or more containers corresponding to the service type, and each container corresponding to the service type comprises one or more containers corresponding to the feature type.3.The method of in claim 2, wherein when the plurality of containers are arranged in the sequential manner, the one or more information blocks comprises a common container including a list of at least one of supported devices corresponding to the device type, supported services corresponding to the service type, supported features corresponding to the feature type, and common information for camping on a cell.4.The method of in claim 2, wherein when the plurality of containers are arranged in the hierarchical manner, the one or more information blocks comprises a common container including a common block containing common information applicable to the plurality of containers.5.The method of claim 1, wherein prior to transmitting the RRC message, the method comprises:identifying the category of information among a plurality of information; anddefining the plurality of containers based on the category of information.6.A network entity in a wireless communication system, comprising:transceiver; andat least one processor coupled with the transceiver, and configured to:transmit a Radio Resource Control (RRC) message to a User Equipment (UE),wherein the RRC message comprises one or more information blocks, wherein each of the one or more information blocks comprises:a plurality of containers based on a category of the information, wherein the category of information corresponds to at least one of a device type, a service type, and a feature type.7.The network entity of claim 6, wherein in case the plurality of containers is based on the category of information, the plurality of containers are arranged in one of a:sequential manner based on the corresponding category of the information;hierarchical manner based on the corresponding category of the information, wherein each container corresponding to the device type comprises one or more containers corresponding to the service type, and each container corresponding to the service type comprises one or more containers corresponding to the feature type.8.The network entity of claim 7, wherein when the plurality of containers are arranged in the sequential manner, the one or more information blocks comprises a common container including a list of at least one of supported devices corresponding to the device type, supported services corresponding to the service type, and supported features corresponding to the feature type, and common information for camping on a cell.9.The network entity of claim 7, wherein when the plurality of containers are arranged in the hierarchical manner, the one or more information blocks comprises a common container including a common block containing common information applicable to the plurality of containers.10.The network entity of claim 6, wherein prior to transmitting the RRC message, the system is configured to:identify the category of information among a plurality of information; anddefine the plurality of containers based on the category of information.11.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:receiving, from a network entity, a Radio Resource Control (RRC) message,wherein the RRC message comprises one or more information blocks, wherein each of the one or more information blocks comprises:a plurality of containers based on a category of the information, wherein the category of information corresponds to at least one of a device type, a service type, and a feature type.12.The method of claim 11, wherein in case the plurality of containers is based on the category of information, the plurality of containers are arranged in one of a:sequential manner based on the corresponding category of the information; andhierarchical manner based on the corresponding category of the information, wherein each container corresponding to the device type comprises one or more containers corresponding to the service type, and each container corresponding to the service type comprises one or more containers corresponding to the feature type.13.The method of claim 12, wherein when the plurality of containers are arranged in the sequential manner, the one or more information blocks comprises a common container including a list of at least one of supported devices corresponding to the device type, supported services corresponding to the service type, supported features corresponding to the feature type, and common information for camping on a cell.14.The method of claim 12, wherein when the plurality of containers are arranged in the hierarchical manner, the one or more information blocks comprises a common container including a common block containing common information applicable to the plurality of containers.15.A user equipment (UE) in a wireless communication system, comprising:transceiver; andat least one processor coupled with the transceiver, and configured to:receive a Radio Resource Control (RRC) message from a network entity, wherein the RRC message comprises one or more information blocks,wherein each of the one or more information blocks comprises:a plurality of containers based on a category of the information, wherein the category of information corresponds to at least one of a device type, a service type, and a feature type.

Images