Method and apparatus for completing radio resource control procedures in a wireless communication system

The method enables efficient RRC procedure completion in 6G wireless communication systems by using non-RRC indications through secure MAC protocols, addressing inefficiencies in existing RRC procedures and improving signal coverage in terahertz bands.

WO2026235525A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096748
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2026-04-08
Filing Date
2026-05-08
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently completing radio resource control (RRC) procedures, particularly in 6G communication systems operating in the terahertz band, where severe path loss and atmospheric absorption necessitate improved signal transmission distance and coverage, and existing methods are inefficient in managing RRC procedures.

Method used

The method involves transmitting a request message (Msg3) from user equipment (UE) to a network node, followed by a non-RRC indication (Msg4) from the network node to complete the RRC procedure, allowing for efficient RRC procedure completion without relying on traditional RRC signaling, using secure Medium Access Control (MAC) protocols.

Benefits of technology

This approach enhances the efficiency of RRC procedure completion in 6G systems by reducing latency and improving signal coverage, particularly in terahertz bands, while ensuring secure communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096748_12112026_PF_FP_ABST
    Figure KR2026096748_12112026_PF_FP_ABST
Patent Text Reader

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). A method includes transmitting, to a base station, a request message (e.g. Msg3) including an RRC request of an RRC procedure; and if the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication: receiving, from the base station, a response message (e.g. Msg4) including a non-RRC indication that the RRC procedure is complete, and ending, in response to the non-RRC indication, the RRC procedure at the UE.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR COMPLETING RADIO RESOURCE CONTROL PROCEDURES IN A WIRELESS COMMUNICATION SYSTEM

[0001] Certain examples of the present disclosure provide methods and apparatus for completing radio resource control (RRC) procedures in wireless communications networks.

[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 method and apparatus for for completing radio resource control procedures 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] Aspects of the present disclosure provide efficient communication methods in a wireless communication system.

[0010] Embodiments / examples of the present disclosure are further described hereinafter with reference to the accompanying drawings, in which:

[0011] Figure 1a provides diagrams of example non-terrestrial networks (NTNs);

[0012] Figure 1b provides diagrams of example non-terrestrial networks (NTNs);

[0013] Figure 2 provides an example initial / random access procedure;

[0014] Figure 3 provides an example procedure for early data transmission;

[0015] Figure 4 provides an example preconfigured uplink resources procedure;

[0016] Figure 5 provides an example of ending an RRC procedure;

[0017] Figure 6 provides an example of ending an RRC procedure;

[0018] Figure 7 provides an example of ending an RRC procedure;

[0019] Figure 8a provides examples of a CB-Msg4 PDU;

[0020] Figure 8b provides examples of a CB-Msg4 PDU;

[0021] Figure 9a provides examples of a CB-Msg4 PDU;

[0022] Figure 9b provides examples of a CB-Msg4 PDU;

[0023] Figure 10 provides an example of a MAC CE; and

[0024] Figure 11 provides a block diagram of an exemplary network entity / function that may be used in certain examples of the present disclosure.

[0025] Figure 12 is a block diagram of a terminal or user equipment (UE) 1200 according to an embodiment of the disclosure;

[0026] Figure 13 is a block diagram of a base station (BS) 1300 according to an embodiment of the disclosure; and

[0027] Figure 14 is a block diagram of a network entity 1400 according to an embodiment of the disclosure.

[0028] It is an aim of certain examples of the present disclosure to address, solve and / or mitigate, at least partly, at least one of the problems and / or disadvantages associated with the related art, for example at least one of the problems and / or disadvantages described herein. It is an aim of certain examples of the present disclosure to provide at least one advantage over the related art, for example at least one of the advantages described herein.

[0029] In accordance with a first aspect of the present disclosure, there is provided a method for radio resource control (RRC) procedure completion in a wireless communications system comprising a user equipment (UE) and network node, the method comprising: transmitting, from the UE to the network node, a request message (e.g. Msg3) including an RRC request of an RRC procedure; and if the UE and the network node support ending and / or are configured to end an RRC procedure via a non-RRC indication: transmitting, from the network node to the UE and in response to the request message, a response message (e.g. Msg4) including a non-RRC indication that the RRC procedure is complete, and ending, in response to the non-RRC indication, the RRC procedure at the UE.

[0030] In an example, the request message includes an RRCResumeRequest or an RRCEarlyDataRequest.

[0031] In an example, if the network node supports ending and / or is configured to end an RRC procedure via a non-RRC indication, the network node transmits to the UE an indication that the network node supports ending and / or is configured to end an RRC procedure via a non-RRC indication.

[0032] In an example, the indication that the network node supports ending and / or is configured to end an RRC procedure via a non-RRC indication is included in a broadcast transmission.

[0033] In an example, if the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication, the UE transmits to the network node an indication that the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication.

[0034] In an example, the request message includes the indication that the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication.

[0035] In an example, the non-RRC indication is provided via a secure message.

[0036] In an example, the message is secured via access stratum (AS) security.

[0037] In an example, the non-RRC indication is provided via Medium Access Control (MAC).

[0038] In an example, the non-RRC indication is provided via Medium Access Control (MAC) Protocol Data Unit (PDU).

[0039] In an example, the MAC PDU includes a random access response, the random access response including a UE contention resolution ID and the indication that the RRC procedure is complete.

[0040] In an example, the random access response is included in a MAC header of the MAC PDU.

[0041] In an example, the random access response includes an indication of a MAC subPDU associated with the UE.

[0042] In an example, the MAC subPDU includes one or more of MAC Service Data Units (SDUs) associated with the UE.

[0043] In an example, the MAC subPDU includes a MAC sub-header.

[0044] In an example, the request message is a contention-based message.

[0045] In an example, the response message includes a contention resolution ID (CRID).

[0046] In an example, the UE ends the RRC procedure if the CRID matches a CRID of the UE.

[0047] In an example, the method further comprises transmitting, from the UE to the network node, a random access preamble (e.g. Msg1); and transmitting, from the network node to the UE, a random access response message (e.g. Msg2), wherein the request message is transmitted in response to the random access response message.

[0048] In an example, the wireless communications system is a 5th Generation (5G) 3GPP system or a 6th Generation (6G) 3GPP system.

[0049] In accordance with a second aspect of the present disclosure, there is provided a wireless communications system comprising a user equipment (UE) and a network node, wherein the wireless communications system is configured to perform the method of any preceding aspect or example.

[0050] In accordance with a third aspect of the present disclosure, there is provided a method of a user equipment (UE) for resource control (RRC) procedure completion in a wireless communications system comprising one or more UE and a network node, the method comprising: transmitting, from the UE to the network node, a request message (e.g. Msg3) including an RRC request of an RRC procedure; and if the UE and the network node support ending and / or are configured to end an RRC procedure via a non-RRC indication: receiving, from the network node, a response message (e.g. Msg4) including a non-RRC indication that the RRC procedure is complete, and ending, in response to the non-RRC indication, the RRC procedure at the UE.

[0051] In accordance with a fourth aspect of the present disclosure, there is provided a user equipment (UE) for use in a wireless communication comprising one or more UE and a network node, wherein the UE is configured to perform the method of the third aspect of the present disclosure.

[0052] In accordance with a fifth aspect of the present disclosure, there is provided a method of a network node for resource control (RRC) procedure completion in a wireless communications system comprising one or more user equipment (UE) and a network node, the method comprising: receiving, from the UE, a request message (e.g. Msg3) including an RRC request of an RRC procedure; and if the UE and the network node support ending and / or are configured to end an RRC procedure via a non-RRC indication: transmitting, to the UE and in response to the request message, a response message (e.g. Msg4) including a non-RRC indication that the RRC procedure is complete, and ending the RRC procedure at the network node.

[0053] In accordance with a sixth aspect of the present disclosure, there is provided a network node for use in a wireless communications system comprising a network node and one or more user equipment (UE), wherein the network node is configured to perform the method of the fifth aspect of the present disclosure.

[0054] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings.

[0055] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0056] In describing the embodiments, while numerous details are set forth for the purpose of illustration, it is understood that some aspects of the disclosure may be practiced with less than all of these details. Numerous variations and alternatives to the details provided herein are possible and are considered within the scope of the disclosure. In some instances, descriptions related to technical contents well-known in the art may be omitted so as to not obscure an understanding of the disclosure, and such omitted descriptions are understood to be within the scope of the disclosure.

[0057] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0058] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described herein in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth herein, but may be implemented in various different forms. Other features, aspects, and advantages of the subject matter described herein will become apparent from the disclosure. The following embodiments are merely examples to aid in an understanding of the disclosure and should not be construed to narrow the scope or spirit of the subject matter described herein in any way, but on the contrary, the disclosure covers all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims and equivalents thereof. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, terms which will be described herein are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0059] Herein, it will be understood that each block of flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0060] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0061] As used in embodiments of the disclosure, a “~unit / module” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit / module” does not always have a meaning limited to software or hardware. The “~unit / module” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit / module” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit / module” may be either combined into a smaller number of components and a “~unit / module,” or divided into additional components and a “~unit / module.” Moreover, the components and “~units / modules” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit / module” may include one or more processors.

[0062] The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0063] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the operating system, in order to control the overall operation of the device. Also, the one processor or the combination of processors is also capable of executing other processes and programs resident in the memory, such as processes for the disclosure.

[0064] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0065] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0066] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0067] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0068] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0069] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0070] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0071] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0072] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0073] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0074] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0075] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0076] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0077] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0078] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure. If a method step (e.g. transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as “in case that ~” or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state “~” (e.g. a bit length is above X), and then perform the method step in response to said determination.

[0079] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0080] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0081] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0082] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0083] In the embodiments of the present disclosure described herein, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0084] The drawings or flowcharts described herein illustrate example methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0085] The process of the flowchart may be performed by a device. One or more of the steps of the flowchart can be implemented by one or more processors / computer programs executing instructions to perform the noted functions.

[0086] The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0087] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0088] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0089] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms describedherein, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) or similar technical specifications, e.g., from the European telecommunications standards institute (ETSI), where appropriate.

[0090] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a wireless access unit, a BS controller, or a node on a network.

[0091] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5th generation (5G) base station architectures in which such CU and DU functional splits are implemented.

[0092] A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing communication functions.

[0093] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.

[0094] Furthermore, hereinafter, 5G mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0095] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0096] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), RRC, or MAC control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.

[0097] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), DCI, UE-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0098] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0099] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0100] The content of the following documents is referred to below and / or their content provides background information and context that the following disclosure should be considered in view of:

[0101] 3GPP TS 38.331 v18.1.0 April 2024

[0102] 3GPP TS 36.331 v18.1.0 April 2024

[0103] 3GPP TS 36.321 v18.4.0 March 2025

[0104] RP-211557 3GPP TSG RAN meeting #91-e e-meeting, March 22 - 26th, 2021

[0105] RP-202689 3GPP TSG RAN Meeting #90 Electronic Meeting, December 7 - 11, 2020

[0106] RP-220953 3GPP TSG RAN Meeting #95e Electronic Meeting, March 17 - 23, 2022

[0107] RP-220979 3GPP TSG RAN Meeting #95e Electronic Meeting, March 17 - 23, 2022

[0108] RP-243278 3GPP TSG RAN Meeting #106, Madrid, December 9 - 12, 2024

[0109] (Note: the example versions shown for each TS are non-limiting, other versions of the TS may be considered also)

[0110] Wireless or mobile (cellular) communications networks in which a mobile terminal (e.g., user equipment (UE), such as a mobile handset) communicates via a radio link with a network of base stations, or other wireless access points or nodes, have undergone rapid development through a number of generations. The 3rdGeneration Partnership Project (3GPP) design, specify and standardise technologies for mobile wireless communication networks. Fourth Generation (4G) and Fifth Generation (5G) systems are now widely deployed, and development of Sixth Generation (6G) Systems is in progress.

[0111] 3GPP standards for 4G systems include an Evolved Packet Core (EPC) and an Enhanced-UTRAN (E-UTRAN: an Enhanced Universal Terrestrial Radio Access Network). The E-UTRAN uses Long Term Evolution (LTE) radio technology. LTE is commonly used to refer to the whole system including both the EPC and the E-UTRAN, and LTE is used in this sense in the remainder of this document. LTE should also be taken to include LTE enhancements such as LTE Advanced and LTE Pro, which offer enhanced data rates compared to LTE.

[0112] In 5G systems a new air interface has been developed, which may be referred to as 5G New Radio (5G NR) or simply NR. NR is designed to support the wide variety of services and use case scenarios envisaged for 5G networks, though builds upon established LTE technologies. New frameworks and architectures are also being developed as part of 5G networks in order to increase the range of functionality and use cases available through 5G networks.

[0113] In recent years, Non-Terrestrial Network (NTN) and Air-To-Ground (ATG) networks have been considered and their operation integrated into 3GPP systems in order to enhance coverage and / or provide alternative coverage mechanisms.

[0114] Non-Terrestrial Networks (NTNs)

[0115] NR NTN (NR_NTN_solutions-Core) [RP-211557] was a 3GPP Work Item in 3GPP Release 17 to define solutions to enable New Radio (NR) and NG-RAN to support NTN. It addressed solutions for transparent payload for both Geostationary and non-Geostationary network scenarios, with the UE having Global Navigation Satellite System (GNSS) capability and the satellite beams being both earth-fixed or earth-moving.

[0116] Figure 1a provides an illustration of an example NTN where a gateway (GW) 106 provides a feeder link 108 to a satellite 110 and the satellite provides an NTN cell 114 and an access link 116 to a device, such as a UE, within the NTN cell. The gateway may be connected to a gNB / eNB 104 which in turn is connected to a core network 102. The gateway 106 may be part of the gNB / eNB 104, separate to or partially integrated. This configuration may be referred to as a transparent payload scenario.

[0117] Figure 1b provides an illustration of an example NTN similar to that of Figure 1a but where at least some of the functions of the gNB / eNB 104 are implemented in the satellite 110. This configuration may be referred to as a regenerative payload scenario, which is considered in 3GPP release 19.

[0118] Internet of Things (IoT) NTN was a 3GPP study and work item in 3GPP release 17 to provide NTN access for E-UTRAN IoT devices (NB-IoT and LTE-M / eMTC) [RP-202689]. NR NTN was a work item in Rel-17 to specify adaptation to allow NR to function over NTN [RP-211557]. NTN access may be through Lower Earth Orbit (LEO), Medium Earth Orbit (MEO) and Geostationary Orbit (GEO), as well as through High-Altitude Platform Systems (HAPS).

[0119] Following the work items in Release 17 there were work items to enhance NR NTN [RP-220953] and IoT NTN [RP-220979] in Release 18.

[0120] The work item description for IoT Rel-19 is the following [RP-243278].

[0121] -Support of Store&Forward (S&F) satellite operation with full eNB as regenerative payload, therefore:

[0122] --Define the necessary enhancements into E-UTRAN (network & UE) to support S&F operation for delay-tolerant services [RAN3, RAN2]

[0123] --Specify necessary enhancements for full eNB as regenerative payload e.g. related to S1 protocol, especially to address the feeder link switch over as needed [RAN3]

[0124] Note: Strive to minimise UE impact.

[0125] Note: Coordination with SA2 (Rel-19 SA2 led Sat-Arch ph3 SI) is needed on the detail requirements (e.g. traffic type, or QoS parameters for S&F), network architecture (e.g. whether consider (partial) core network on satellite) etc.; further coordination with CT1 might be required

[0126] -Support of Capacity enhancements for uplink

[0127] --Study then specify, if beneficial, enhancements to enable multiplexing of multiple UEs (e.g. up to the min of 4 and the maximum allowed by the existing UL and DL signalling) in a single 3.75 kHz or 15 kHz subcarrier via orthogonal cover codes (OCC) for NPUSCH format 1 and NPRACH [RAN1, RAN2, RAN4]

[0128] ⅰ. Multi-tone support for 15 kHz SCS should also be considered

[0129] ⅱ. Specify necessary signalling, if needed

[0130] ⅲ. Update RF requirements accordingly, if needed

[0131] Note: Impact of impairment shall be taken into account

[0132] --Study and specify, if beneficial the following enhancements to reduce the necessary uplink and downlink signaling to complete an Early Data Transmission (EDT) transaction [RAN2]:

[0133] ⅰ. Msg3 transmission without msg1 / Random Access Response (RAR)

[0134] ⅱ. Efficient delivery (reduced overhead) of msg4 / RRCEarlyDataComplete

[0135] ⅲ. Study and specify RRM requirement, if identified [RAN4]

[0136] -Support broadcast of PWS messages for NB-IoT re-using the LTE mechanisms [RAN2]

[0137] Note: The solutions will be developed for NTN but can be applicable to TN (if possible). Specific NB-IoT TN optimizations will not be considered as part of this WI.

[0138] Note: Support for indication of intended service area for ETWS will be considered based on NR NTN discussions / outcome.

[0139] Narrowband Internet of Things (IoT) and LTE-M

[0140] Narrowband Internet of Things (NB-IoT) is a 3GPP-defined network based on 4G E-UTRAN that supports ultra-low complexity devices with very narrow bandwidth that was introduced in 3GPP Release 13. It supports the massive Machine Type Communication (mMTC) 5G use case for IMT-2020. The use case of NB-IoT is to serve massive IoT application, where requirements for instance are to support enhanced coverage, power-efficient operation and a massive number of devices. Some of the features introduced are:

[0141] - Support for enhanced coverage through low bandwidth and extreme amounts of repetitions.

[0142] - Power efficient operation by allowing the UE to sleep for very long times, relaxed requirements and more efficient signal to establish with a cell.

[0143] LTE-M (or eMTC) is another technology that serves the mMTC 5G use case. Compared to NB-IoT, an LTE-M device is more like a simplified 4G E-UTRAN device with certain simplifications allowing for easier and cheaper implementation. It addressed a slight wider use case compared to NB-IoT, with higher data rates and is not quite as power efficient as NB-IoT. This type of device may also be referred to as a Cat M1 / 2 device or as Bandwidth Limited (BL) UE and UE in enhanced coverage.

[0144] Both LTE-M and NB-IoT are specified with what is known as User plane and Control plane enhancements for reduced signaling. In user plane solution, the UE supports AS security and Data radio bearers. In control plane, the UE does not support AS security and instead relies on NAS for security, which means that all data is routed through MME. Control plane is mandatory for NB-IoT and optional for LTE-M.

[0145] Initial / Random Access Procedure in IoT NTNs

[0146] Figure 2 provides an example initial / random access procedure that may take place in an IoT NTN between a UE 202 and an eNB 204.

[0147] Initially the UE may be in an RRC idle mode.

[0148] When an RRC connection is required, at step 0, the UE determines the timing advance pre-compensation using the UE position and the satellite position. The UE position may be obtained via GNSS, but other methods that do not rely on a network may also potentially be used, such as using inertial navigation system or similar. The satellite position is acquired via SIB19 and the UE also pre-compensates using TA-Common, which is the common timing advance from the satellite to the ground gateway where the base station resides.

[0149] At step 1, the UE uses the pre-compensation and sends Msg1 which is the RACH preamble. The RACH preamble will represent a number between 1 and 64. The number selected by the UE is random, but there exists several rules to determine the range of preambles, depending on configurations and conditions - sometimes referred to as preamble division.

[0150] At step 2, if the network is able to detect and the determine the RACH preamble, the eNB responds with Msg1 (i.e. a random access response - RAR).

[0151] At step 3, the UE sends Msg3, which is sent using PUSCH. This message will contain the first RRC message. The RRC message depends on the specific reason why the random access procedure was triggered. For example for initial access it will be RRCSetupRequest, for resuming it is RRCConnectionResumeRequest, for re-establishing RRC it is RRCConnectionReestablishmentRequest, for CP-EDT it is RRCEarlyDataRequest etc.

[0152] Since it is possible that two UEs select the same random access preamble ID (RAPID), there is a chance of collision. Therefore, at step 4, in Msg4, sent over PDSCH this contention may be resolved using the Contention Resolution Medium Access Control (MAC) Control Element (CE). The procedures are successful if the UE receives a Contention Resolution ID that matches the UEs Contention Resolution ID. The Contention Resolution ID consists of the first 48 bits of the SDU of Msg3. Msg4 also contains an RRC message that is a response to Msg3. This can for instance be RRCConnectionSetup, RRCConnectionResume, RRCConnectionReestablishment, RRCReject, RRCEarlyDataComplete etc.

[0153] At step 5, a further message, Msg5, is transmitted by the UE. Msg5 is a further message that is a scheduled uplink message which would consist of the reply to the downlink RRC message in Msg4. Msg5 is sometimes not considered a part of the random access procedure, but a part of any access procedure. The RRC message carried in Msg5 may be RRCConnectionSetupComplete, RRCConnectionResumeComplete, RRCConnectionReestablishmentComplete and so on.

[0154] Early Data Transmission

[0155] Early data transmission (EDT) is a feature that allows a UE to start to transmit data in Msg3. This is mostly for power-saving purposes where, in the best case, the UE would be able to transmit all of its data and then be released in Msg4. In RRC Resume, the UE may not start transmitting data until after RRCResumeComplete in Msg5.

[0156] Figure 3 provides an example EDT procedure from the perspective of PHY layer, MAC and RRC, where the EDT procedure may be between a UE 202 and eNB 204 in an NTN but is not limited to NTN or IoT.

[0157] Initially the UE may be in an RRC idle mode.

[0158] At step 0, as in a normal NTN random access procedure, such as described with reference to step 0 of Figure 2, the UE determines the timing advance pre-compensation using the UE position and the satellite position.

[0159] At step1, as in a normal random access procedure such as that of Figure 2, the UE uses the pre-compensation and sends Msg1 which is the RACH preamble. However, the UE selects a RACH preamble from a specific set of preambles that indicates that the UE will perform EDT.

[0160] At step 2, if the network is able to detect and determine the RACH preamble, the eNB responds with Msg1 or RAR.

[0161] At step 3, the UE send Msg3, where Msg3 includes, in a control plane solution, an RRCEarlyDataRequest, and, in a user plan solution, an RRCConnectionResumeRequest as well as uplink data.

[0162] Since it is possible that two UEs select the same RAPID, there is a chance of collision. Therefore, at step 4, a Msg4 is sent over PDSCH, where the contention may be resolved using the Contention Resolution MAC CE. Msg4 also contains an RRC message that is a response to Msg3. This can for instance be RRCSetup, RRCConnectionResume, RRCConnectionReestablishment, RRCReject, RRCEarlyDataComplete etc.

[0163] Preconfigured Uplink Resources

[0164] Preconfigured uplink resources (PUR) is a feature that allows for pre-configuration of uplink transmissions / resources without the need for random access. It also means that data can be transmitted without the UE needing to move to RRC connected, saving time and power consumption.

[0165] Figure 4 provides an example PUR procedure, from the perspective of PHY layer, MAC and RRC between a UE 202 and eNB 204, where the procedure may be in a NTN other form of network.

[0166] At step 1, the UE may optionally send a request to request the UE to be configured with PUR. This request contains the requested number of PUR occasions, the periodicity and offset as well as the Transport Block Size (TBS), i.e. the size of the allocation for PUR.

[0167] At step 2, if the network determines that the UE shall go to RRC idle and that it would be beneficial for the UE to be configured with PUR, then the network releases the UE and configures pur-Config in the RRCConnectionRelease message.

[0168] -The PUR configuration contain the parameters that gives the PUR resource, such as periodicity and offset, the startSFN, the start subframe, the number of PUR occasions, the PUR-RNTI, the pur-TimeAlignmentTimer, and RSRP threshold, a response window timer, the configurations for MPDCCH, PDSCH, PUCCH and PUSCH and the PDSCH frequency hopping.

[0169] At step 3, the UE suspends the RRC connection and moves to RRC idle.

[0170] At step 4, traffic arrives in the uplink buffer of the UE.

[0171] At step 5, in an NTN, the UE would at least have to self-precompensate the timing advance. The UE may potentially also have to acquire the GNSS position as well as acquire SIB31 to ensure that it has the most updated satellite ephemeris.

[0172] At step 6, the UE uses the configured PUR-resources and performs uplink transmission using PUSCH.

[0173] -In Control plane solution the PUR message consist of the RRC message RRCEarlyDataRequest, which contains the transparent NAS container which may contain data or NAS signalling.

[0174] -In User plane solution the PUR message consists of the RRCConnectionResumeRequest as well as uplink data from any of the radio bearers that triggered the PUR.

[0175] At step 7, the UE responds to the PUR:

[0176] -In control plane solution the response may consist of 1) a Layer 1 acknowledgement, 2) a Timing Advance MAC CE command that updates the TA or 3) an RRCEarlyDataComplete. If none of these are received, the UE considers the procedure to not be completed.

[0177] -In user plane solution the response either consist of the RRCConnectionRelease message which succesfully completes the PUR transmission. The response may also include downlink data transmissions.

[0178] Although the above procedures (e.g. EDT, PUR) and also further procedures such as small data transmission (SDT) may save time and reduce power consumption, procedures such as these that that deliver data or report information from RRC idle or RRC inactive usually require that a response in the RRC layer is sent.

[0179] Lately there has been a proposal in 3GPP Release 19 to enable contention-based Msg3 EDT, whereby a UE performs a random access procedure for EDT by directly transmitting the Msg3 without Msg1 and Msg2. As part of that proposal, it has been proposed that the RRC procedure can end after the Msg3 (RRCResumeRequest or RRCEarlyDataRequest) by sending an acknowledgement over MAC. However there are several open issues:

[0180] -Whether this can be applicable for normal EDT, i.e. EDT where Msg1 and Msg2 is transmitted, and how such a scheme works for legacy scheme

[0181] -How an acknowledgement over MAC can be performed for User Plane solution

[0182] -How to design the MAC PDU design for Msg4

[0183] The present disclosure considers and provides solutions for addressing these issues.

[0184] The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of certain examples of the present disclosure. The description includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the scope of the invention or disclosure.

[0185] The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings.

[0186] Detailed descriptions of techniques, structures, constructions, functions or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present disclosure.

[0187] The terms and words used herein are not limited to the bibliographical or standard meanings, but are merely used to enable a clear and consistent understanding of the disclosure.

[0188] Throughout the description of this specification, the words “comprise”, “include” and “contain” and variations of the words, for example “comprising” and “comprises”, means “including but not limited to”, and is not intended to (and does not) exclude other features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof.

[0189] Throughout the description of this specification, the singular form, for example “a”, “an” and “the”, encompasses the plural unless the context otherwise requires. For example, reference to “an object” includes reference to one or more of such objects.

[0190] Throughout the description, the expression “at least one of A, B and / or C” (or the like) and the expression “one or more of A, B and / or C” (or the like) should be seen to separately include all possible combinations, for example: A, B, C, A and B, A and C, A and B and C.

[0191] Throughout the description of this specification, language in the general form of “X for Y” (where Y is some action, process, operation, function, activity or step and X is some means for carrying out that action, process, operation, function, activity or step) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y.

[0192] Features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof described or disclosed in conjunction with a particular aspect, embodiment or example are to be understood to be applicable to any other aspect, embodiment or example described herein unless incompatible therewith.

[0193] The following examples are applicable to, and use terminology associated with, 3GPP 4G (e.g., LTE) and / or 5G (e.g., NR). However, the skilled person will appreciate that the techniques disclosed herein are not limited to these examples or to 3GPP 4G (e.g., LTE) and / or 5G (e.g., NR), and may be applied in any suitable system or standard, for example one or more existing and / or future generation wireless communication systems or standards (e.g., B5G, 5G-Advanced, 6G etc.). The skilled person will appreciate that the techniques disclosed herein may be applied in any existing or future releases of 3GPP 4G (e.g., LTE) and / or 5G (e.g., NR) and / or 5G Advanced and / or 6G, and / or (3GPP Release 17, 18, 19, 20, etc.) or any other relevant standard. For example, the functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in other communication systems or standards. Corresponding or equivalent entities or features may be regarded as entities or features that perform the same or similar role, function, operation or purpose within the network.

[0194] Furthermore. the following also applies to the present disclosure:

[0195] -The terms functionality / use-case / configuration / scenario / site may be used interchangeably.

[0196] -The terms model and model functionality may be used interchangeably.

[0197] -This disclosure also apply to non-3GPP entities.

[0198] -The concepts, proposals, solutions, methods, embodiments, figures, and / or examples, presented in this disclosure, would apply to various type of communication systems, such as 4G, 4G-Advanced, 5G, 5G-Advanced, and 6G.

[0199] A particular network entity may be implemented as a network element on dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0200] The skilled person will appreciate that the present disclosure is not limited to the specific examples disclosed herein. For example:

[0201] -The techniques disclosed herein are not limited to 3GPP 4G or 5G or 5G-Advanced and also apply to B5G and 6G systems.

[0202] -One or more entities in the examples disclosed herein may be replaced with one or more alternative entities performing equivalent or corresponding functions, processes or operations.

[0203] -One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information.

[0204] -One or more further elements, entities and / or messages may be added to the examples disclosed herein.

[0205] -One or more non-essential elements, entities and / or messages may be omitted in certain examples.

[0206] -The functions, processes or operations of a particular entity in one example may be divided between two or more separate entities in an alternative example.

[0207] -The functions, processes or operations of two or more separate entities in one example may be performed by a single entity in an alternative example.

[0208] -Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example.

[0209] -Information carried by two or more separate messages in one example may be carried by a single message in an alternative example.

[0210] -The order in which operations are performed may be modified, if possible, in alternative examples.

[0211] -The transmission of information between network entities is not limited to the specific form, type and / or order of messages described in relation to the examples disclosed herein.

[0212] In the following, although particular types of network or devices may be referred to, the approaches of the present disclosure apply to any of the networks and devices referred to herein, including NR NTN, LTE-M / eMTC NTN, E-UTRA NTN, 6G NTN, and equivalent terrestrial networks.

[0213] In the approaches described below, the term “Contention-based Msg3” (CB-Msg3) indicates

[0214] 1) a procedure where data along with control plane signaling can be transmitted in a contention-based manner without having to perform random access, and

[0215] 2) any procedure where random access is performed, but Msg1 and Msg2 is skipped.

[0216] “Contention-based Msg3” may also be called or the approaches may also apply for “contention-based PUR”, “EDT without msg1”, “RACH-less EDT” or similar. Contention-based Msg3 may be termed “Msg3 without random access”. This can be a generalization of RACH-less (E)DT where any procedure normally uses the random access procedure may perform the random access procedure but only transmit Msg3.

[0217] The term “Contention-based Msg3 transmission” may be used, which may be taken to mean transmitting the first message of the “Contention-based Msg3 procedures”. Due to similarities to the random access procedures, this message may also be referred to as “Msg3”, since it is an access procedure without the random access procedure, i.e. without Msg1 and Msg2.

[0218] Furthermore, reference to PDCCH in the context of the disclosure approaches may refer to any type of PDCCH, including normal LTE PDCCH, NR PDCCH, EPDCCH, Machine-type PDCCH (MPDCCH) or NB-IoT PDCCH (NPDCCH).

[0219] Ending RRC Procedures Early

[0220] In some instances, CB-Msg3-EDT procedures may be ended / completed early by the network transmitting sending and the UE receiving a Contention Resolution ID in the CB-Msg4. However, there may need to be additional signalling.

[0221] According to an example of the present disclosure, in addition to the Contention Resolution ID in Msg4, the network may also send an indication that the UE shall end the RRC procedure. In other words, the UE ends / completes the RRC procedure such as (but not limited to) an EDT procedure if the UE receives the indication to end the RRC procedure. This does not require any RRC message to be sent in a Msg4. This can for instance be an indication in a MAC header, MAC subheader or a MAC CE. If indicated via a MAC CE, it can be via a new empty MAC CE. Ending / completing the RRC procedure may mean that the UE moves back to RRC idle. This may also be considered to be a Layer 2 acknowledgement of the RRC procedures.

[0222] If the indication is provided via MAC, once the indication in MAC has been received, then the MAC entity in the UE will indicate to the RRC layer to end / complete the RRC procedure. This can for instance be done by considering the UE to have received the RRC message which should have been received in a certain manner. For instance the UE may consider to perform the procedures of receiving an RRC message without having received the RRC message. For instance for EDT, the UE may have considered to have received an empty RRCEarlyDataResponse message. This works as the specific RRC messages may be “empty”. This may trigger certain procedures to be performed as if RRC message was empty.

[0223] Figure 5 illustrates an approach for ending early an RRC procedure between a UE 202 and an eNB 204.

[0224] Initially, the UE is in RRC idle or RRC inactive.

[0225] At step 1, the UE transmits a CB-Msg3 to the eNB, where the CB-Msg3 may include an RRCResumeRequest and data or an RRCEarlyDataRequest.

[0226] At step 2, the eNB transmits to the UE a Msg4 with a contention resolution ID (CRID) and an indication to end RRC procedures, where the indication may take any form described by the present disclosure.

[0227] At step 3, if the CRID matches the UE CRID, the UE may end RRC procedures without further RRC messages bring transmitted or received.

[0228] The UE may also be configured to perform an RRC procedure as if having received an RRC message with certain fields set in certain scenarios. For instance, for certain scenarios, the UE may be considered to have received an RRCConnectionRelease message. This may contain an RRC transaction identifier that matches the last sent message, for instance the RRC message contained in the Msg3, or any other last received RRC message. The RRC message may be considered to contain a release cause to a certain value, such as rrc-Suspend, indicating that the UE is suspended. The RRC message may consider that certain elements of a suspend configuration shall be set in a specific way. For instance its resume identity shall remain the same, or that the resume identity received in the RRC message shall be different in a specific manner, for instance that a specific value is added to the resume identity, or the resume identity may be configured in advance. If configured in advance, this may be configured in an RRC Release message. This may mean that only certain number of procedures can be performed and that at some point the procedure may not continue as there are not enough resume identities. At this point the UE may be required to connect to receive new resume identities. This may be the resume identity or an Inactive-RNTI (I-RNTI). Such scenario may for instance be if the UE performs User Plane EDT, or any other message where the first message uses AS security, such as Small Data Transmissions.

[0229] In one example, an indication may be introduced which indicates that the UE does not end / complete the RRC procedures. This may be the case where the contention resolution is performed early, but the RRC procedures have yet to end / complete and the UE has received a matching contention resolution ID. This may mean that the UE receives the contention resolution ID, but does not yet end / complete the RRC procedure. This may mean that the UE needs to continue to monitor for the RRC message in order to end / complete the RRC procedure. The RRC procedure then finishes when the UE receives an RRC message addressed to it which ends / completes the procedure, or alternatively makes the UE enter RRC connected.

[0230] The above indications may be a part of the same field. For instance it may be a field in a MAC subheader, MAC header or MAC CE. An example of a MAC format is provided in Figure 10 and Specification Example 1.

[0231] In a further example, the Msg4 can contain an indication to end / complete the RRC procedures and also contain downlink data. This means that the Msg4 higher layer content is only downlink data without an RRC message. This can be useful for instance for Mobile terminated procedures, i.e. when the UE is paged to receive downlink data.

[0232] In a further example, the Contention Resolution ID must be acknowledged by the UE. In other words, there may be a requirement that the UE sends an HARQ acknowledgement when receiving an indication to end / complete the RRC procedures. Otherwise there is a risk that the network may not know whether the RRC procedure was completed.

[0233] Although the procedures described above have been described with reference to CB-Msg3-EDT, they may be applied to other procedures. For example, using MAC to end / complete the RRC procedures may be introduced for already existing access procedures. For instance, for EDT with RACH, the RRC procedures may be ended / completed via an indication in MAC, for instance by only receiving the contention resolution ID and potentially an indication to end / complete the RRC procedures. However, in these cases, where the same access procedure may be performed by UEs supporting this feature and UEs not supporting this feature, there may be confusion whether the UE is capable of ending / completing the RRC procedures via MAC indication or not, or whether the UE shall do so if the UE supports this feature.

[0234] In some implementations the UE and the network may need to indicate that ending a RRC procedure by MAC is supported and / or configured. For instance, a UE may indicate in a Msg3, which can be indicated via MAC or RRC that the UE supports ending / completing the RRC procedures via MAC. The network may indicate in a broadcasted indication that the RRC procedures may be ended / completed via MAC indication. This may mean that the RRC procedure is ended / completed via MAC indication if the network has indicated that it is configured and that the network supports it, and that the UE has indicated in the Msg3 that the UE supports the feature. If none of these conditions are fulfilled, then the UE will not end / complete the RRC procedure based on the MAC indication. An example procedure for providing an indication of support for ending RRC via MAC is provided by Figure 6.

[0235] Figure 6 provide an example based on a procedures where the UE performs Msg1 and Msg2 transmission; however, the procedure may also apply to 2-step Random access. For example, in a 2-step random access, the indication may be sent in a MsgA, and the procedure would be ended / completed using an indication in MsgB.

[0236] Initially (i.e. before transmissions of Msg1), the UE 202 may be in RRC idle or RRC inactive and the eNB 204 may transmit an indication that the network supports ending of RRC procedures via MAC. This indication may be provided via any suitable mechanism such as in broadcast information.

[0237] At steps 1 and 2, the UE and eNB exchange Msg1 and Msg2, as described above with reference to Figures 2 or 3 for example.

[0238] At step 3, the Msg3 transmitted by the UE additionally includes an indication that the UE supports ending RRC procedures (or a specific type of RRC procedure) via MAC. In some examples, the UE indication may be provided via an alternative mechanism or may have been previously provided when transmitting a previous Msg3.

[0239] At step 4, if the UE supports ending RRC procedures via MAC, a Msg4 including an indication (e.g. via MAC) to end the RRC procedure(s) may be transmitted by the eNB to the UE. In some examples the Msg 4 may include the indication even if the UE does not support ending RRC procedures via MAC in order to reduce variations in Msg4, as the network will know that the UE will not react to such an indication.

[0240] At step 5, in response to the reception of Msg4 including the indication of to end the RRC procedure, the UE ends the RRC procedure without the receipt or transmission of a further RRC message.

[0241] The ending / completion of an RRC procedure via a non-RRC indication may also be applied to other types of procedure, for example, EDT and / or CB-Msg3-EDT. It may also be applicable in cases where RRC resume is performed, for instance for RAN Notification Area Update is performed, i.e. when a UE sends the RRC resume request with the resume cause set to RNA update, which indicates that the UE is camping on a new RAN Notification area.

[0242] Figure 7 provides an example procedure in which ending / completing an RRC procedure via MAC ( or other form of non-RRC indication) is applied to an RRCResumeRequest indicating an RNA update. However, the approach of Figure 7 may also be applied to a number of other scenarios, such as when a UE is performing an tracking area update.

[0243] Initially the UE is in RRC idle or RRC inactive.

[0244] At step 0, the UE camps on a new RNA.

[0245] At steps 1 and 2, the UE and eNB exchange Msg1 and Msg2, as described above with reference to Figures 2 or 3 for example.

[0246] At step 3, the UE transmits Msg3 to the eNB, which includes an RRCResumeRequest indicating an RNA update.

[0247] At step 4, if the UE supports ending RRC procedures via MAC, a Msg4 including an indication (e.g. via MAC) to end the RRC procedure(s) may be transmitted by the eNB to the UE.

[0248] At step 5, in response to the reception of Msg4 including the indication to end the RRC procedure, the UE ends the RRC procedure without the receipt or transmission of a further RRC message.

[0249] If the MAC procedures are secured, i.e. the messages in MAC level are considered to be secured, then the MAC layer may end / complete the RRC procedures. In some cases where the MAC layer has not applied AS security, such as during initial registration, or other cases, then the MAC layer may not be able to end / complete the RRC procedures. Thus the condition that an indication in MAC is able to end / complete the RRC procedures without sending an RRC message may be based on whether MAC security has been activated, configured or setup.

[0250] Although the procedures described above with reference to Figures 5 to 7 for ending / completing a RRC procedure(s) without an RRC message have been described separately, elements of them may also be combined. For instance, approaches for indicating UE and / or network support for ending RRC procedures via MAC (or other non-RRC mechanism) may be combined with any of the proposed approaches / scenarios or other RRC / initial access / random access-based procedures. Similarly, the approach for the structure of the Msg4 may take any suitable form, such as any of those described below.

[0251] MAC PDU Design for Msg4

[0252] An important aspect of CB-Msg3 procedures such as CB-Msg3-EDT procedures is how to design the MAC PDU which is transmitted in response to the CB-Msg3-EDT.

[0253] One issue arises from the fact that a same CB-Msg4 may be sent to multiple UEs and contain information for a set of UEs. Accordingly, the UEs need to be able to efficiently identify which of the information, i.e. MAC Service Data Units (SDUs), MAC headers and / or subheaders that belongs to the UE and which do not belong to the UE.

[0254] Another issue may be that the CB-Msg4 message for a UE that is successful in the contention-based procedures, may receive zero, one or even two MAC SDUs containing data and or higher layer signalling.

[0255] In the case of the UE having its RRC procedure ended / completed using a MAC indication, the UE will not receive an RRC message, but receive one or more of the following information, which may or may not consist of a single MAC CE, MAC header or MAC subheader:

[0256] - Contention Resolution ID

[0257] - HARQ scheduling feedback information

[0258] - Timing advance information

[0259] - C-RNTI information

[0260] In the case of the UE receiving an RRC message, the UE will receive a single MAC SDU addressed to it in addition to the information required to end / complete the MAC-layer contention based procedure. This information may be the same as that of a UE having its RRC procedure ended / completed using MAC indication.

[0261] In the case of the UE receiving a downlink data message, the UE may either receive a single MAC SDU or two MAC SDUs addressed to it, in addition to the information required to end / complete the MAC-layer contention-based procedures.

[0262] It may be indicated to the UE how many MAC SDUs or how many MAC subPDUs are addressed to it. This can be indicated to zero, one, two or more. If for instance zero is indicated, then this may indicate that the RRC procedures are considered to be ended / completed and thus indicated to the higher layers as such. If one is indicated, then this may be an RRC message or a downlink data message. This can for instance allow for only downlink data without an RRC message, or it can allow for an RRC message only. If two is indicated then this allows for an RRC message and downlink data PDU to be received, which may be applicable to a user plane solution, such as UP EDT. This indication may be in the MAC subheader, header or MAC CE that is sent in case of a successful CB-Msg3-EDT procedures. This may also imply how many specific types of headers that are addressed to the UE. In other words, if two MAC SDUs or MAC subPDUs are addressed to the UE, then this may mean that there are two length and LCID headers that the UE needs to read.

[0263] Various examples of CB-Msg4 PDUs are provided by Figures 8a, 8b, 9a, and 9b.

[0264] In Figures 8a and 8b, the MAC layer procedures of the CB-Msg3-EDT is considered to be successfully completed if the UE receives the Msg3-EDT success RAR. Then the UE determines how many MAC SDUs in the MAC PDU that are addressed to it. The number of MAC SDUs may be indicated in the Msg3-EDT success RAR. Then the MAC subPDUs may then contain multiple MAC SDUs whose length are indicated in the MAC subPDU by the use of specific headers. This means that the MAC subPDU may consist of multiple MAC SDUs and their associated sub-headers (e.g. R / F2 / E / LCID / L MAC subheader).

[0265] More specifically, in Figure 8a, Msg3-EDT success RAR 802 indicates to UE#1 that its CB-Msg3-EDT has been successfully completed, and Msg3-EDT success RAR 804 indicates to UE#2 that its CB-Msg3-EDT has been successfully completed, where the Msg3-EDT success RARs are included in the MAC header 814. Msg3-EDT success RAR 802 also indicates to UE#1 the number of MAC SDUs and associated sub-headers in the MAC PDU 816 that are addressed to it (MAC SDUs 808 and 812 and sub-headers 806 and 810 in this case). The MAC payload may also include further MAC subPDUs 818 (e.g. associated with UE#2) and also further content such as padding or any other component of MAC PDUs.

[0266] In Figure 8b, similar information is contained in the MAC PDU compared to Figure 8a but each MAC subPDU includes a single MAC SDU and subheader. This means that each UE may have multiple MAC subPDUs addressed to it. How many, if any, MAC subPDUs addressed to it is determined based on information in the Msg3-EDT success RAR.

[0267] In Figure 9a, the headers 904 906 of the MAC SDUs 910 912 are in the MAC header 914, which follows after the Msg3-EDT success RAR 902 908 for a specific UE. The number of headers following a Msg3-EDT success RAR may be indicated by a field in the Msg3 EDT success RAR. The MAC subPDU 916 918 may consist of one or more MAC SDUs 910 912. The MAC payload may also include further content such as padding or any other component of MAC PDUs.

[0268] In Figure 9b, the structure of the MAC PDU is similar to that of Figure 9b but where each MAC subPDU includes a single MAC SDU.

[0269] The Msg3-EDT success RAR (Random access Response) is the MAC header or MAC subheader which indicates that the UE has succeeded at the CB-MSg3-EDT procedures or any other RRC procedure, which may be considered a success on MAC, RRC or MAC and RRC layers. This may consist of one or more MAC elements and may have one or more variants, for instance depending on whether one or more elements are present or not.

[0270] In some examples, the length and / or the logical channel ID (LCID) of the MAC SDU is indicated in the success subheader.

[0271] In another example, a subheader may indicate the length indicator and / or the logical channel ID (LCID) of multiple MAC SDUs. In another example, the LCID of the RRC message may not need to be indicated, which can be useful if the RRC message is always included. In this case only the length indicator needs to be included for the case of multiple MAC SDUs in Msg4. In another example, the length indicator may not need to be indicated, for instance if the RRC message in Msg4 has a constant length. In that case a subheader may only need to be present in case there is MAC SDU for downlink data PDU.

[0272] Further RRC Ending / Completion Indicators

[0273] In another approach to indicating that an RRC procedure has ended or is complete, the UE may be configured to monitor for a RNTI in order to receive an acknowledgement to end / complete or complete the RRC procedures. This can for instance be called an Acknowledgement RNTI, an ACK-RNTI. The UE may monitor this RNTI alongside other RNTIs, for instance the RA-RNTI, TC-RNTI or C-RNTI, which is used to receive messages containing RRC or downlink data.

[0274] Monitoring for a new RNTI may for instance allow for the acknowledgement to be made over physical layer or Layer 1, for instance via a PDCCH. The PDCCH may further contain an ID in order to acknowledge the UE.

[0275] The RNTI may be based on the UE CRID, i.e. the 48 first bits of the uplink message in Msg3. For instance a modulus operation of the UE CRID may be used.

[0276] Figure 10 provides an example CB-Msg4-RAR that may be included in a MAC CE, MAC header or MAC subheader for example. The CB-Msg4-RAR includes one or more of Contention Resolution ID, HARQ scheduling feedback information, Timing advance information, and C-RNTI information. With respect to indicating whether an RRC procedure is completed or should be carried, bit S may provide such an indication to a UE in combination with a contention resolution ID. For example, if set to 0, the UE shall indicate to upper layers to complete the CB-Msg3-EDT procedures if the Contention resolution ID matches the UE contention resolution ID. If set to 1 the CB-Msg3-EDT procedures shall be considered successfully completed if the contention resolution ID matches the UE contention resolution ID (i.e. RRC procedure is complete).

[0277] Certain examples of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or a method therefor. Such an apparatus / device / network entity may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). Certain examples of the present disclosure may be provided in the form of a system (e.g., a network) comprising one or more such apparatuses / devices / network entities, and / or a method therefor.

[0278] It will be appreciated that examples of the present disclosure may be realized in the form of hardware, software or a combination of hardware and software. Certain examples of the present disclosure may provide a computer program comprising instructions or code which, when executed, implement a method, system and / or apparatus in accordance with any aspect, example and / or embodiment disclosed herein. Certain embodiments of the present disclosure provide a machine-readable storage storing such a program.

[0279] Figure 11 is a block diagram of an exemplary network entity / function that may be used in examples of the present disclosure, such as the techniques disclosed in relation to any of the preceding figures. For example, any of the network entities, network function etc. (e.g. UE, BS, gNB / eNB, ATG entities, NTN nodes, etc.) may be provided in the form of the network entity illustrated in Figure 11. The skilled person will appreciate that a network entity / function may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0280] The entity 1100 comprises a processor (or controller) 1101, a transmitter 1103 and a receiver 1105. The receiver 1105 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 1103 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 1101 is configured for performing one or more operations, for example according to the operations as described above.

[0281] Figure 12 is a block diagram of a terminal or user equipment (UE) 1200 according to an embodiment of the disclosure.

[0282] The terminal is an electronic device capable of wireless communication and having various form factors, examples of the terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing wireless communication with a base station (BS) and / or another terminal through a wireless channel.

[0283] Referring to Figure 12, the UE 1200 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1201, at least one processor (hereinafter, referred to as simply “processor”) 1202, and at least one memory (hereinafter, referred to as simply “memory”) 1203. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1201, the processor 1202, and the memory 1203 of the UE 1200 may operate. However, components of the UE 1200 are not limited to the example components illustrated in Figure 12. In another embodiment, the UE 1200 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1201, the processor 1202, or the memory 1203 may be integrated in the form of one component.

[0284] The transceiver 1201 may be a communication circuit or communication circuitry that enables the UE 1200 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1201 may enable the UE 1200 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 1201 may support at least one of various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1201) may include all subsequent generations of evolved wireless communications.

[0285] According to an embodiment, the UE 1200 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) dual connectivity (EN-DC), the UE 1200 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 1200 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 1200 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0286] According to an embodiment, the transceiver 1201 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 1201 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1201 may output a signal received through a wireless channel to the processor 1202 and may transmit, through a wireless channel, a signal output from the processor 1202.

[0287] The processor 1202 may control general operations of the UE 1200 according to embodiments of the disclosure. The processor 1202 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1202 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1203, individually, collectively or in any combination thereof. Further, the processor 1202 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0288] The processor 1202 may be electrically, operatively, and / or communicatively coupled to the transceiver 1201 to control the transceiver 1201.

[0289] The processor 1202 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 1202 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer). In a specific embodiment, at least a part of the processor 1202 may be included in one chip (or IC) and the other part of the processor 1202 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1201 or the memory 1203.

[0290] The processor 1202 may perform or control or cause an operation of the UE 1200 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1202 may control operations of the UE 1200 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 1202 may execute a computer program, codes, or instructions stored in the memory 1203, so as to control other components of the UE 1200 to enable execution of various operations.

[0291] The memory 1203 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1203 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0292] The memory 1203 may be electrically, operatively, and / or communicatively coupled to the processor 1202 and may be accessed by the processor 1202.

[0293] The memory 1203 may store a computer program, codes, or instructions executable by the processor 1202. According to an embodiment, a computer program, codes, or instructions executable by the processor 1202 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1203, the processor 1202 may perform various functions according to an embodiment of the disclosure.

[0294] According to an embodiment of the disclosure, operations of the UE 1200 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1203 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0295] Figure 13 is a block diagram of a base station (BS) 1300 according to an embodiment of the disclosure.

[0296] The BS 1300 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 1300 through a wireless channel. The BS 1300 may perform communication with a node or an entity of a network through wired or wireless communication.

[0297] Referring to Figure 13, the BS 1300 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1301, at least one processor (hereinafter, referred to as simply “processor”) 1302, and at least one memory (hereinafter, referred to as simply “memory”) 1303. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1301, the processor 1302, and the memory 1303 of the BS 1300 may operate. However, components of the BS 1300 are not limited to the example components illustrated in Figure 13. In another embodiment, the BS 1300 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1301, the processor 1302, or the memory 1303 may be integrated in the form of one component.

[0298] The transceiver 1301 may be a communication circuit or communication circuitry that enables the BS 1300 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1301 may enable the BS 1300 to transmit or receive a signal to or from the UE 1200 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 1301 may support various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1301) may include all subsequent generations of evolved wireless communications.. According to an embodiment, the transceiver 1301 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 1301 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1301 may output a signal received through a wireless channel to the processor 1302 and may transmit, through a wireless channel, a signal output from the processor 1302.

[0299] Meanwhile, according to an embodiment of the present disclosure, the BS 1300 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 1300 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in Figure 13, when the BS 1300 performs wired communication, the BS 1300 may further include a separate network interface for wired communication in addition to the transceiver 1301. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0300] The processor 1302 may control general operations of the BS 1300 according to embodiments of the disclosure. The processor 1302 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1302 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1303, individually, collectively or in any combination thereof. Further, the processor 1302 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0301] The processor 1302 may be electrically, operatively, and / or communicatively coupled to the transceiver 1301 to control the transceiver 1301.

[0302] The processor 1302 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1302 may be included in one chip (or IC) and the other part of the processor 1302 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1301 or the memory 1303.

[0303] The processor 1302 may perform or control or cause an operation of the BS 1300 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1302 may control operations of the BS 1300 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 1300 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 1302 may execute a computer program, codes, or instructions stored in the memory 1303, so as to control other components of the BS 1300 to enable execution of various operations.

[0304] The memory 1303 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1303 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0305] The memory 1303 may be electrically, operatively, and / or communicatively coupled to the processor 1302 and may be accessed by the processor 1302.

[0306] The memory 1303 may store a computer program, codes, or instructions executable by the processor 1302. According to an embodiment, a computer program, codes, or instructions executable by the processor 1302 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1303, the processor 1302 may perform various functions according to an embodiment of the disclosure.

[0307] According to an embodiment of the disclosure, operations of the BS 1300 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1303 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0308] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with a network entity (for example, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), rtc.) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0309] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0310] Figure 14 is a block diagram of a network entity 1400 according to an embodiment of the disclosure.

[0311] The network entity 1400 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 1400.

[0312] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0313] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN), etc.

[0314] Referring to Figure 14, the network entity 1400 may include at least one network interface 1401, at least one processor 1402 (hereinafter, “processor”), and at least one memory 1403 (hereinafter, “memory”). As described above, a NF may be implemented in the form of a physical device such as the network entity 1400, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in Figure 14. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0315] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 1401, the processor 1402, and the memory 1403 of the network entity 1400 may operate. However, components of the network entity 1400 are not limited to the example components illustrated in Figure 14. In another embodiment, the network entity 1400 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 1401, the processor 1402, or the memory 1403 may be integrated in the form of one component.

[0316] The network interface 1401 is a collective term for a transmitter part of the network entity 1400 and a receiver part of the network entity 1400, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 1401 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 1401 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 1401 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0317] The processor 1402 may control general operations of the network entity 1400 according to embodiments of the disclosure. The processor 1402 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1402 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1403, individually, collectively or in any combination thereof. Further, the processor 1402 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0318] According to an embodiment, the processor 1402 may be electrically, operatively, and / or communicatively coupled to the network interface 1401 to control the network interface 1401.

[0319] The processor 1402 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1402 may be included in one chip (or IC) and the other part of the processor 1402 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the network interface 1401 or the memory 1403.

[0320] The processor 1402 may perform or control or cause an operation of the network entity 1400 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1402 may control operations of the network entity 1400 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 1402 may execute a computer program, codes, or instructions stored in the memory 1403, so as to control other components of the network entity 1400 to enable execution of various operations.

[0321] The memory 1403 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1403 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0322] The memory 1403 may be electrically, operatively, and / or communicatively coupled to the processor 1402 and may be accessed by the processor 1402.

[0323] The memory 1403 may store a computer program, codes, or instructions executable by the processor 1402. According to an embodiment, a computer program, codes, or instructions executable by the processor 1402 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1403, the processor 1402 may perform various functions according to an embodiment of the disclosure.

[0324] According to an embodiment of the disclosure, operations of the network entity 1400 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1403 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0325] In one embodiment, a method for radio resource control (RRC) procedure completion in a wireless communications system comprising a user equipment (UE) and network node is provided. The method comprises: transmitting, from the UE to the network node, a request message (e.g. Msg3) including an RRC request of an RRC procedure; and if the UE and the network node support ending and / or are configured to end an RRC procedure via a non-RRC indication: transmitting, from the network node to the UE and in response to the request message, a response message (e.g. Msg4) including a non-RRC indication that the RRC procedure is complete, and ending, in response to the non-RRC indication, the RRC procedure at the UE.

[0326] In another embodiment, wherein the request message includes an RRCResumeRequest or an RRCEarlyDataRequest.

[0327] In another embodiment, wherein, if the network node supports ending and / or is configured to end an RRC procedure via a non-RRC indication, the network node transmits to the UE an indication that the network node supports ending and / or is configured to end an RRC procedure via a non-RRC indication.

[0328] In another embodiment, wherein the indication that the network node supports ending and / or is configured to end an RRC procedure via a non-RRC indication is included in a broadcast transmission.

[0329] In another embodiment, wherein, if the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication, the UE transmits to the network node an indication that the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication

[0330] In another embodiment, wherein the request message includes the indication that the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication.

[0331] In another embodiment, wherein the non-RRC indication is provided via a secure message.

[0332] In another embodiment, wherein the message is secured via access stratum (AS) security.

[0333] In another embodiment, wherein the non-RRC indication is provided via Medium Access Control (MAC).

[0334] In another embodiment, wherein the non-RRC indication is provided via Medium Access Control (MAC) Protocol Data Unit (PDU).

[0335] In another embodiment, wherein the MAC PDU includes a random access response, the random access response including a UE contention resolution ID and the indication that the RRC procedure is complete.

[0336] In another embodiment, wherein the random access response is included in a MAC header of the MAC PDU.

[0337] In another embodiment, wherein the random access response includes an indication of a MAC subPDU associated with the UE.

[0338] In another embodiment, wherein the MAC subPDU includes one or more of MAC Service Data Units (SDUs) associated with the UE.

[0339] In another embodiment, wherein the MAC subPDU includes a MAC sub-header

[0340] In another embodiment, wherein the request message is a contention-based message.

[0341] In another embodiment, wherein the response message includes a contention resolution ID (CRID).

[0342] In another embodiment, wherein the UE ends the RRC procedure if the CRID matches a CRID of the UE.

[0343] In another embodiment, further comprises: transmitting, from the UE to the network node, a random access preamble (e.g. Msg1); and transmitting, from the network node to the UE, a random access response message (e.g. Msg2), wherein the request message is transmitted in response to the random access response message.

[0344] In another embodiment, wherein the wireless communications system is a 5th Generation (5G) 3GPP system or a 6th Generation (6G) 3GPP system.

[0345] In one embodiment, a wireless communications system comprissing a user equipment (UE) and a network node, wherein the wireless communications system is configured to perform the method of described above.

[0346] In one embodiment, a method of a user equipment (UE) for resource control (RRC) procedure completion in a wireless communications system comprising one or more UE and a network node is provided. The method comprises: transmitting, from the UE to the network node, a request message (e.g. Msg3) including an RRC request of an RRC procedure; and if the UE and the network node support ending and / or are configured to end an RRC procedure via a non-RRC indication: receiving, from the network node, a response message (e.g. Msg4) including a non-RRC indication that the RRC procedure is complete, and ending, in response to the non-RRC indication, the RRC procedure at the UE.

[0347] In one embodiment, a user equipment (UE) for use in a wireless communication comprising one or more UE and a network node, wherein the UE is configured to perform the method of described above.

[0348] In one embodiment, a method of a network node for resource control (RRC) procedure completion in a wireless communications system comprising one or more user equipment (UE) and a network node is provided. The method comprising: receiving, from the UE, a request message (e.g. Msg3) including an RRC request of an RRC procedure; and if the UE and the network node support ending and / or are configured to end an RRC procedure via a non-RRC indication: transmitting, to the UE and in response to the request message, a response message (e.g. Msg4) including a non-RRC indication that the RRC procedure is complete, and ending the RRC procedure at the network node.

[0349] In one embodiment, a network node for use in a wireless communications system comprising a network node and one or more user equipment (UE), wherein the network node is configured to perform the method of described above.

[0350] It will be appreciated that, in each example / embodiment / aspect etc. described above, one or more features or operations may be omitted, modified or moved (e.g., to change the order of the features or the operations), if desired and appropriate.

[0351] Additionally, where the figures illustrating example method flows include text in relation to a specific step / operation, it will be appreciated that this text is simply an example of the corresponding step / operation, where a more general definition (such as may be found in the description of the corresponding step) may apply for the step / operation.

[0352] Additionally, regarding all of the above, one or more features or operations etc. from any example / embodiment may be combined with features or operations from any other example / embodiment. That is, the present disclosure should be considered to include all combinations of examples / embodiments disclosed herein, as appropriate, as well as combinations of individual features within and between each example / embodiment, as appropriate.

[0353] The techniques described herein may be implemented using any suitably configured apparatus and / or system. Such an apparatus and / or system may be configured to perform a method according to any aspect, embodiment or example disclosed herein. Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). The one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software.

[0354] It will be appreciated that examples of the present disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a ROM, whether erasable or rewritable or not, or in the form of memory such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a CD, DVD, magnetic disk or magnetic tape or the like.

[0355] It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising instructions that, when executed, implement certain examples of the present disclosure. Accordingly, certain examples provide a program comprising code for implementing a method, apparatus or system according to any example, embodiment and / or aspect disclosed herein, and / or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication signal carried over a wired or wireless connection.

[0356] While the disclosure has been shown and described with reference to certain examples, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the disclosure.

[0357] The reader's attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference.

[0358] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

[0359] Example Specification

[0360] Example of certain 3GPP specifications are set out below, where the changes are shown in bold.

[0361] Example 1

[0362] The CB-Msg4-RAR is of fixed size as depicted in Figure XX, and consists of the following fields:

[0363] - UE Contention Resolution Identity: If this MAC control element is included in response to an uplink CCCH transmission, then this field contains the uplink CCCH SDU if the uplink CCCH SDU is 48 bits long. If the CCCH SDU is longer than 48 bits, this field contains the first 48 bits of the uplink CCCH SDU.

[0364] - R: Reserved bit, set to 0;

[0365] -S: If set to 0 , the UE shall indicate to upper layers to complete the CB-Msg3-EDT procedures if the Contention resolution ID matches the UE contention resolution ID. If set to 1 the CB-Msg3-EDT procedures shall be considered successfully completed if the contention resolution ID matches the UE contention resolution ID.

[0366] - PUCCH Resource Indicator.

[0367] - Timing Advance Command: The Timing Advance Command field indicates the index valueTAused to control the amount of timing adjustment that the MAC entity has to apply in TS 36.213 [X]. The size of the Timing Advance Command field is 11 bits;

[0368] - C-RNTI: The C-RNTI field indicates the identity that is used by the MAC entity upon completion of Random Access. The size of the C-RNTI field is 16 bits.

[0369] The CB-Msg4-RAR is octet aligned.

[0370] In one embodiment, a method for radio resource control (RRC) procedure completion in a wireless communications system comprising a UE and network node is provided. The method comprises: transmitting, from the UE to the network node, a request message (e.g. Msg3) including an RRC request of an RRC procedure; transmitting, from the network node to the UE from the network node and in response to the request message, a response message (e.g. Msg4) including a non-RRC indication that the RRC procedure is complete; and ending, in response to the non-RRC indication, the RRC procedure at the UE.

[0371] In another embodiment, wherein the request message includes an RRCResumeRequest or an RRCEarlyDataRequest.

[0372] In another embodiment, wherein the network node transmits an indication that the network supports ending an RRC procedure via a non-RRC indication.

[0373] In another embodiment, wherein the request message includes an indication that the UE supports RRC procedure completion via a non-RRC indication.

[0374] In another embodiment, wherein the non-RRC indication is provided via Medium Access Control (MAC).

[0375] In another embodiment, wherein the non-RRC indication is provided via Medium Access Control (MAC) Protocol Data Unit (PDU).

[0376] In another embodiment, wherein the MAC PDU includes a random access response, the random access response including a UE conflict resolution ID and the indication that the RRC procedure is complete.

[0377] In another embodiment, wherein the random access response is included in a MAC header of the MAC PDU.

[0378] In another embodiment, wherein the random access response includes an indication of a MAC subPDU associated with the UE.

[0379] In another embodiment, wherein the MAC subPDU includes one or more of MAC Service Data Units (SDUs) associated with the UE.

[0380] In another embodiment, wherein the MAC subPDU includes a MAC sub-header

[0381] In another embodiment, wherein the MAC PDU includes one or more of a contention resolution ID, HARQ scheduling feedback information, timing advance information, and C-RNTI information.

[0382] In another embodiment, wherein the request message is a contention-based message.

[0383] In another embodiment, wherein the response message includes a contention resolution ID (CRID).

[0384] In another embodiment, wherein the UE ends the RRC procedure if the CRID matches a CRID of the UE.

[0385] In another embodiment, wherein the non-RRC indication is provided via an RNTI.17.

[0386] In another embodiment, further comprises: transmitting, from the UE to the network node, a random access preamble (e.g. Msg1); and transmitting, from the network node to the UE, a random access response message (e.g. Msg2), wherein the request message is transmitted in response to the random access response message.

[0387] Acronyms and Definitions

[0388] 3GPP 3rdGeneration Partnership Project

[0389] 5G 5thGeneration

[0390] 5GC 5G Core

[0391] 5QI 5G QoS Identifier

[0392] 5GS 5G System

[0393] 5GSM 5G System Session Management

[0394] 5GMM 5G System Mobility Management

[0395] AF Application Function

[0396] AI Artificial Intelligence

[0397] AM Acknowledged Mode

[0398] AMF Access and Mobility Management Function

[0399] AS Access Stratum

[0400] ASP Application Service Provider

[0401] ATG Air-To-Ground

[0402] AUSF Authentication Server Function

[0403] CDN Content Delivery Network

[0404] DCAF Data Collection Application Function

[0405] DNAI Data Network Access Identifier

[0406] DNN Data Network Name

[0407] DNS Domain Name Server

[0408] DRB Data Radio Bearer

[0409] EDT Early Data Transmission

[0410] eMTC Enhanced Machine-Type Communications

[0411] eNB Evolved Node B

[0412] EPC Evolved Packet Core

[0413] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0414] FEC Forward Error Correction

[0415] FQDN Fully Qualified Domain Name

[0416] GBR Guaranteed Bit Rate

[0417] gNB Next generation Node B

[0418] GPSI Generic Public Subscription Identifier

[0419] HSS Home Subscriber Service

[0420] IAB Integrated Access and Backhaul

[0421] ID Identity / Identifier

[0422] IIoT Industrial Internet of Things

[0423] IMEI International Mobile Equipment Identities

[0424] IP Internet Protocol

[0425] I-SMF Intermediate SMF

[0426] LADN Local Area Data Network

[0427] LL SSM Lower Layer SSM

[0428] LTE Long Term Evolution

[0429] LTE-M LTE Machine-Type Communication

[0430] MBMS Multimedia Broadcast / Multicast Service

[0431] MBS Multicast / Broadcast Service

[0432] MBSF Multicast / Broadcast Service Function

[0433] MBSTF Multicast / Broadcast Service Transport Function

[0434] MB-SMF Multicast / Broadcast Session Management Function

[0435] MB-UPF Multicast / Broadcast User Plane Function

[0436] MTC Machine-Type Communication

[0437] MCCH Multicast Control Channel

[0438] MTCH Multicast Traffic Channel

[0439] ML Machine Learning

[0440] MME Mobility Management Entity

[0441] MN Master Node

[0442] MNF Monitoring Network Function

[0443] MNO Mobile Network Operator

[0444] MPDCCH MTC Physical Downlink Control Channel

[0445] MT Mobile Termination

[0446] NAS Non-Access Stratum

[0447] NR-IoT Narrowband Internet of Things

[0448] NEF Network Exposure Function

[0449] NRF Network Repository Function

[0450] NG-RAN Next Generation Radio Access Network

[0451] NG-eNB Next Generation eNB

[0452] NGAP Next Generation Application Protocol

[0453] NR New Radio

[0454] NSA Non-Standalone

[0455] NSSF Network Slice Selection Function

[0456] NTN Non-Terrestrial Networks

[0457] NW Network

[0458] NWDAF Network Data Analytics Function

[0459] OS Operating System

[0460] OSAPP OS Application

[0461] PCF Policy Control Function

[0462] PCO Protocol Configuration Options

[0463] PDR Packet Detection Rule

[0464] PDU Protocol Data Unit

[0465] PLMN Public Land Mobile Network

[0466] PTM Point To Multipoint

[0467] PTP Point to Point

[0468] PDSCH Physical Downlink Shared Channel

[0469] PUCCH Physical Uplink Control Channel

[0470] PUSCH Physical Uplink Shared Channel

[0471] PUR Preconfigured Uplink Resources

[0472] QFI QoS Flow Identifier (ID)

[0473] QoS Quality of Service

[0474] RACH Random Access Channel

[0475] RAN Radio Access Network

[0476] RRC Radio Resource Control

[0477] RSD Route Selection Descriptor

[0478] SA Standalone

[0479] SDAP Service Data Adaptation Protocol

[0480] SDU Service Data Unit

[0481] SGW Serving Gateway

[0482] SIM Subscriber Identity Module

[0483] SLA Service Level Agreement

[0484] SM Session Management

[0485] SMF Session Management Function

[0486] SN Secondary Node

[0487] S-NSSAI Single Network Slice Selection Assistance Information

[0488] SSB Synchronization Signal Block

[0489] SSM Source Specific IP Multicast address

[0490] SSC Session and Service Continuity

[0491] SRB Signaling Radio Bearer

[0492] SUPI Subscription Permanent Identifier

[0493] TA Tracking Area

[0494] TAI Tracking Area Identity

[0495] TE Terminal Equipment

[0496] TM Transparent Mode

[0497] TMGI Temporary Mobile Group Identity

[0498] TS Technical Specification

[0499] UAV Unmanned Aerial Vehicle

[0500] UDM Unified Data Manager

[0501] UDR Unified Data Repository

[0502] UE User Equipment

[0503] UL Uplink

[0504] UM Unacknowledged Mode

[0505] UP User Plane

[0506] UPF User Plane Function

[0507] URLLC Ultra-Reliable and Low-Latency Communication

[0508] URSP UE Route Selection Policy

Claims

1.A method performed by a user equipment (UE) for resource control (RRC) procedure completion in a wireless communications system, the method comprising:transmitting, to a base station, a request message (e.g. Msg3) including an RRC request of an RRC procedure; andif the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication:receiving, from the base station, a response message (e.g. Msg4) including a non-RRC indication that the RRC procedure is complete, andending, in response to the non-RRC indication, the RRC procedure at the UE.2.The method of claim 1, wherein the request message includes an RRCResumeRequest or an RRCEarlyDataRequest.3.The method of claim 1, wherein the method further comprising:receiving, from the base station, an indication that the base station supports ending and / or is configured to end an RRC procedure via a non-RRC indication, if the base station supports ending and / or is configured to end an RRC procedure via a non-RRC indication.4.The method of claim 3, wherein the indication that the base station supports ending and / or is configured to end an RRC procedure via a non-RRC indication is included in a broadcast transmission.5.The method of claim 1, wherein the method further comprising:transmitting, to the base station, an indication that the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication, if the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication.6.The method of claim 1, wherein the request message includes the indication that the UE supports ending and / or is configured to end an RRC procedure via a non-RRC indication.7.The method of claim 1, wherein the non-RRC indication is provided via a secure message.8.The method of claim 7, wherein the message is secured via access stratum (AS) security.9.The method of claim 1, wherein the non-RRC indication is provided via Medium Access Control (MAC).10.The method of claim 1, wherein the MAC PDU includes a random access response, the random access response including a UE contention resolution ID and the indication that the RRC procedure is complete.11.The method of claims 10, wherein the random access response includes an indication of a MAC subPDU associated with the UE.12.The method of claim 1, wherein the RRC procedure comprising: ending the RRC procedure if the CRID matches a CRID of the UE.13.A user equipment (UE) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to:perform the method of claim 12.14.A method by performed a base station for resource control (RRC) procedure completion in a wireless communications system, the method comprising:receiving, from a user equipment(UE), a request message (e.g. Msg3) including an RRC request of an RRC procedure; andif the base station supports ending and / or is configured to end an RRC procedure via a non-RRC indication:transmitting, to the UE and in response to the request message, a response message (e.g. Msg4) including a non-RRC indication that the RRC procedure is complete,and ending the RRC procedure at the base station.15.A base station comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the base station to:perform the method of claim 14.