Method and apparatus for small data transmission, SDT.

Abstract

To provide a method and an apparatus for suitable small data transmission, SDT.SOLUTION: A wireless device receives, from a base station, radio resource control, RRC, and a RRC release message comprising a measurement configuration for one or more measurements by the wireless device while the wireless device is in an inactive state and small data transmission, SDT, a configuration of a SDT procedure for transmission by the wireless device while the wireless device is in a RRC inactive state. While the wireless device is, on the basis of the RRC release message, in the RRC inactive state, the wireless device initiates the SDT procedure on the basis of the SDT configuration and does not perform, during the SDT procedure, measurements associated with the measurement configuration.SELECTED DRAWING: Figure 22

Description

[Background technology]

[0001] Cross-reference of related applications This application claims priority to U.S. Provisional Patent Application No. 63 / 226,882, filed on 29 July 2021, which is incorporated herein by reference in its entirety. [Overview of the project] [Means for solving the problem]

[0002] In this disclosure, various embodiments are presented as examples of how the disclosed technology may be implemented and / or practiced in various environments and scenarios. It will be apparent to those skilled in the art that various modifications of form and detail can be made without departing from the scope. Indeed, after reading the specification, it will be apparent to those skilled in the art how to implement alternative embodiments. These embodiments should not be limited by any of the exemplary embodiments. Embodiments in this disclosure are described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create further embodiments within the scope of this disclosure. Figures highlighting features and benefits are shown for illustrative purposes only. The disclosed architecture is sufficiently flexible and configurable to be used in ways other than those shown. For example, any action listed in any flowchart can be rearranged in some embodiments or used only at will.

[0003] Embodiments can be configured to operate as needed. The disclosed mechanisms can be implemented, for example, in a wireless device, a base station, a wireless environment, a network, the above combinations, etc., when certain criteria are met. Exemplary criteria can be at least partially based on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, traffic characteristics, the above combinations, etc. When one or more criteria are met, various exemplary embodiments can be applied. Thus, it may be possible to implement exemplary embodiments that selectively implement the disclosed protocol.

[0004] A base station can communicate with a mixture of wireless devices. A wireless device and / or a base station can support multiple technologies and / or multiple releases of the same technology. A wireless device can have some specific capabilities depending on the category and / or capabilities of the wireless device. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure can refer to a subset of all wireless devices within a coverage area. The present disclosure can refer to, for example, multiple wireless devices of a given LTE or 5G release that include a given capability and are in a given sector of a base station. The multiple wireless devices in the present disclosure can refer to a selected multiple wireless devices and / or a subset of all wireless devices within a coverage area implemented according to the disclosed method, etc. There can be multiple base stations or multiple wireless devices in a coverage area that do not conform to the disclosed method. For example, those wireless devices or base stations are implemented based on an old release of LTE or 5G technology.

[0005] As used herein, the terms “a” and “an” and similar phrases are to be construed as “at least one” and “one or more”. Similarly, any term ending with the suffix “(s)” should be construed as “at least one” and “one or more”. As used herein, the term “may” should be construed as “for example, may be”. In other words, the term “may” indicates that the phrase following the term “may” is a plurality of suitable possible examples and may or may not be used by one or more of the various embodiments. As used herein, the terms “comprises” and “consists of” enumerate one or more components of the recited element. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components included in the recited element. In contrast, “consists of” provides a complete enumeration of one or more components of the recited element. As used herein, the term “based on” should be construed as “at least partially based on” rather than, for example, “based only on”. As used herein, the term “and / or” represents any possible combination of the recited elements. For example, “A, B, and / or C” may represent A, B, C, A and B, A and C, B and C, or A, B, and C.

[0006] If A and B are a set and all elements of A are also elements of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell 1, cell 2} are {cell 1}, {cell 2}, and {cell 1, cell 2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase following the term "based on" is an embodiment of many preferred possibilities in which one or more of the various embodiments may or may not be used. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is an embodiment of many preferred possibilities in which one or more of the various embodiments may or may not be used. The phrase "according to" (or equivalently "at least in accordance with") indicates that the phrase following the phrase "according to" is an embodiment of many preferred possibilities in which one or more of the various embodiments may or may not be used. The phrase “adopt / use” (or equivalently “at least adopt / use”) indicates that the phrase following “adopt / use” is used in one or more of the various embodiments, or is an embodiment of one of many preferred possibilities that may not be used.

[0007] The term "configured" can relate to the capacity of a device, regardless of whether the device is operational or non-operating. "Configured" can refer to specific settings of a device that affect its operational characteristics, regardless of whether the device is operational or non-operating. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within a device, regardless of whether the device is operational or non-operating, in order for the device to provide certain characteristics. Terms such as "control messages generated in a device" can mean that control messages, regardless of whether the device is operational or non-operating, have parameters that can be used to configure certain characteristics in the device or to implement certain actions in the device.

[0008] In this disclosure, a parameter (or equivalently referred to as a field, or information element: IE) may contain one or more information objects, and an information object may contain one or more other objects. For example, if parameter (IE)N contains parameter (IE)M, parameter (IE)M contains parameter (IE)K, and parameter (IE)K contains parameter (information element)J, then for example, N contains K and N contains J. In exemplary embodiments, when one or more messages contain multiple parameters, it means that one of the multiple parameters is contained in at least one of the one or more messages, but not in each of the one or more messages.

[0009] Many of the features presented are described as optional through the use of "may" or parentheses. For brevity and readability, this disclosure does not expressly describe all possible changes that may result from selecting from a set of optional features. This disclosure should be construed as expressly disclosing all such changes. For example, a system described as having three optional features can be embodied in seven ways: by just one of the three possible features, by any two of the three features, or by three of the three features.

[0010] Many of the elements described in the disclosed embodiments can be implemented as modules, where a module is defined as an element that performs a defined function and has a defined interface to other elements. Modules described in this disclosure may be implemented in hardware, software combined with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, and they can be behaviorally equivalent. For example, a module may be implemented in a hardware machine (such as C, C++, Fortran, Java®, Basic, Matlab®) or in software routines written in a computer language configured to run in Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Modules may also be implemented using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and complex-programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are often programmed using hardware description languages ​​(HDLs) such as VHSIC (VHDL) or Verilog, which constitute connections between internal hardware modules with limited functionality in the programmable device. These techniques are often used in combination to achieve the results of the functional modules. The present invention provides, for example, the following: (Item 1) It is a method, From the base station via wireless device, A measurement configuration for one or more measurements by the wireless device while the wireless device is in a radio resource control (RRC) inactive state, Receiving an RRC release message, including an SDT configuration of a Small Data Transmission (SDT) procedure for transmission by the wireless device while the wireless device is in the RRC inactive state, Based on the receipt of the aforementioned RRC release message, The wireless device causes the RRC to transition to the inactive state, The wireless device starts the timer T331 for measurement in the RRC inactive state, While T331 is running, the measurements associated with the aforementioned measurement configuration are performed, While the wireless device is in the RRC inactive state, the SDT procedure is initiated based on the SDT configuration. A method comprising not performing the measurement associated with the measurement configuration during the SDT procedure. (Item 2) The method according to item 1, wherein the measurement configuration includes the value of T331. (Item 3) The method according to item 1 or 2, further comprising stopping and / or pausing T331 based on the commencement of the SDT procedure, wherein the measurement associated with the measurement configuration is not performed based on the stopping and / or pausing of T331. (Item 4) Based on the failure of the SDT procedure, the wireless device, T331 and / or The method according to any one of items 1 to 3, further comprising restarting, starting, and / or restarting the measurement associated with the measurement configuration. (Item 5) It is a method, From the base station via wireless device, A measurement configuration for one or more measurements by the wireless device while the wireless device is in a radio resource control (RRC) inactive state, Receiving an RRC release message, including an SDT configuration of a Small Data Transmission (SDT) procedure for transmission by the wireless device while the wireless device is in the RRC inactive state, Based on receiving the RRC release message, the wireless device transitions to the RRC inactive state and performs the measurement associated with the measurement configuration. While the wireless device is in the RRC inactive state, The SDT procedure is initiated based on the aforementioned SDT configuration, A method comprising not performing the measurement associated with the measurement configuration during the SDT procedure. (Item 6) The method according to item 5, wherein the wireless device starts a timer T331 for measurement in the RRC inactive state based on receiving the RRC release message. (Item 7) The method according to item 6, wherein the measurement associated with the measurement configuration is performed while T331 is running. (Item 8) The measurement configuration is the method according to item 6 or 7, including the value of T331. (Item 9) The method according to any one of items 6 to 8, further comprising stopping and / or pausing the measurement timer based on the commencement of the SDT procedure, wherein the failure to perform the measurement associated with the measurement configuration is based on the stopping and / or pausing of the measurement timer. (Item 10) Based on the failure of the SDT procedure, the wireless device, The aforementioned measuring timer, and / or The method according to any one of items 6 to 9, further comprising restarting, starting, and / or restarting the measurement associated with the measurement configuration. (Item 11) It is a method, From the base station via wireless device, A measurement configuration for one or more measurements by the wireless device while the wireless device is in a radio resource control (RRC) inactive state, Receiving an RRC release message, including an SDT configuration of a Small Data Transmission (SDT) procedure for transmission by the wireless device while the wireless device is in the RRC inactive state, Based on the RRC release message, while the wireless device is in the RRC inactive state, The SDT procedure is initiated based on the aforementioned SDT configuration, A method comprising not performing the measurement associated with the measurement configuration during the SDT procedure. (Item 12) The method according to item 11, further comprising the wireless device transitioning to the RRC inactive state based on the RRC release message. (Item 13) The method according to item 11 or 12, wherein the measurement configuration includes a carrier frequency list and / or an effective area list. (Item 14) The method according to any one of items 11 to 13, further comprising starting a measurement timer based on the RRC release message using the wireless device. (Item 15) The aforementioned measurement timer, The method according to item 14, wherein one or more of the timer for measurement in the RRC inactive state and / or T331. (Item 16) The method according to item 14 or 15, wherein the measurement configuration includes the value of the measurement timer. (Item 17) The method according to any one of items 14 to 16, further comprising using the wireless device to perform the measurement associated with the measurement configuration while the measurement timer is activated based on the RRC release message. (Item 18) The method according to any one of items 14 to 17, further comprising stopping and / or pausing the measurement timer based on the commencement of the SDT procedure. (Item 19) The method of item 18, wherein the failure to perform the measurement associated with the measurement configuration is based on stopping and / or pausing the measurement timer. (Item 20) Based on the failure of the SDT procedure, the wireless device, The aforementioned measuring timer, and / or The method according to item 19, further comprising restarting, starting, and / or restarting the measurement associated with the measurement configuration. (Item 21) The failure of the aforementioned SDT procedure The failure timer for the aforementioned SDT procedure has expired. Selecting a serving cell that is different from the serving cell through which the wireless device performs the SDT procedure, Receiving a fallback indicator, Receiving a rejection message, and / or The method described in any one of items 11-20, based on at least one of the reasons for determining that compliance with the RRC message is not possible. (Item 22) The method according to any one of items 11 to 21, further comprising performing the measurement associated with the measurement configuration based on the RRC release message using the wireless device. (Item 23) The method of item 22, wherein the failure to perform the measurement associated with the measurement configuration includes stopping the performance of the measurement and / or temporarily suspending the performance of the measurement. (Item 24) The aforementioned wireless device, Initiating the SDT procedure, and / or The method according to any one of items 11 to 23, further comprising transmitting the results of one or more of the one or more measurements associated with the measurement configuration based on the failure to perform the measurement associated with the measurement configuration. (Item 25) The aforementioned SDT configuration is Next hop chain number (NCC), The resumed identity of the wireless device, and The method according to any one of items 11 to 24, wherein the configured wireless bearer includes at least one of the markings shown in the SDT procedure. (Item 26) Initiating the aforementioned SDT procedure is The wireless device receives a paging message indicating the SDT procedure, and / or The method according to any one of items 11 to 25, based on one or more of the following: the data of the SDT procedure is available to the wireless device. (Item 27) During the SDT procedure, the measurement associated with the measurement configuration is not performed. Based on the determination of the commencement of the SDT procedure, the measurement associated with the measurement configuration is not performed. Based on sending a first uplink message regarding the SDT procedure, the measurement associated with the measurement configuration will not be performed. Based on receiving a message regarding the SDT procedure, the measurement associated with the measurement configuration will not be performed, and / or The method according to any one of items 11 to 27, comprising not performing the measurement associated with the measurement configuration based on the wireless device determining that the cell in which the SDT procedure was initiated is invalid for the measurement. (Item 28) The wireless device supports carrier aggregation and / or dual connection, and / or The method according to any one of items 11 to 27, wherein the measurement configuration is for the carrier aggregation and / or duplication of the wireless device. (Item 29) A wireless device comprising one or more processors and a memory storing instructions, wherein when an instruction is executed by the one or more processors, the wireless device causes the wireless device to perform the method described in any one of items 1 to 28. (Item 30) A non-temporary computer-readable medium comprising instructions, wherein when the instructions are executed by one or more processors, the one or more processors cause the one or more processors to perform the method described in any one of items 1 to 28. (Item 31) It is a method, From the base station via wireless device, A measurement configuration for one or more measurements by the wireless device while the wireless device is in a radio resource control (RRC) inactive state, Receiving an RRC release message, including an SDT configuration of a Small Data Transmission (SDT) procedure for transmission by the wireless device while the wireless device is in the RRC inactive state, Based on the receipt of the aforementioned RRC release message, The wireless device causes the RRC to transition to the inactive state, The wireless device starts the timer T331 for measurement in the RRC inactive state, While T331 is running, the measurements associated with the aforementioned measurement configuration are performed, During the SDT procedure, the measurement associated with the measurement configuration is not performed. A method comprising using the wireless device to perform the measurement associated with the measurement configuration based on the failure of the SDT procedure. (Item 32) The method according to item 31, further comprising stopping and / or pausing T331 based on initiating the SDT procedure, wherein the measurement associated with the measurement configuration is not performed based on stopping and / or pausing T331. (Item 33) Based on the failure of the SDT procedure, the wireless device, T331 and / or The method according to item 31 or 32, further comprising restarting, starting, and / or restarting the measurement associated with the measurement configuration. (Item 34) The failure of the aforementioned SDT procedure The failure timer for the aforementioned SDT procedure has expired. Selecting a serving cell that is different from the serving cell through which the wireless device performs the SDT procedure, Receiving a fallback indicator, Receiving a rejection message, and / or The method described in any one of items 31-33, based on at least one of the reasons for determining that compliance with the RRC message is not possible. (Item 35) It is a method, From the base station via wireless device, A measurement configuration for one or more measurements by the wireless device while the wireless device is in a radio resource control (RRC) inactive state, Receiving an RRC release message, including an SDT configuration of a Small Data Transmission (SDT) procedure for transmission by the wireless device while the wireless device is in the RRC inactive state, Based on receiving the RRC release message, the wireless device transitions to the RRC inactive state and performs the measurement associated with the measurement configuration. During the SDT procedure, the measurement associated with the measurement configuration is not performed. A method comprising using the wireless device to perform the measurement associated with the measurement configuration based on the failure of the SDT procedure. (Item 36) The method according to item 35, wherein the wireless device starts a timer T331 for measurement in the RRC inactive state based on receiving the RRC release message. (Item 37) The method according to item 36, wherein the measurement associated with the measurement configuration is performed while T331 is running. (Item 38) The method according to item 36 or 37, further comprising stopping and / or pausing T331 based on initiating the SDT procedure, wherein the measurement associated with the measurement configuration is not performed based on stopping and / or pausing T331. (Item 39) Based on the failure of the SDT procedure, the wireless device, T331 and / or The method according to any one of items 35 to 38, further comprising restarting, starting, and / or restarting the measurement associated with the measurement configuration. (Item 40) The failure of the aforementioned SDT procedure The failure timer for the aforementioned SDT procedure has expired. Selecting a serving cell that is different from the serving cell through which the wireless device performs the SDT procedure, Receiving a fallback indicator, Receiving a rejection message, and / or The method described in any one of items 35-39, based on at least one of the reasons for determining that compliance with the RRC message is not possible. (Item 41) It is a method, From the base station via wireless device, A measurement configuration for one or more measurements by the wireless device while the wireless device is in a radio resource control (RRC) inactive state, Receiving an RRC release message, including an SDT configuration of a Small Data Transmission (SDT) procedure for transmission by the wireless device while the wireless device is in the RRC inactive state, During the aforementioned SDT procedure, the measurement associated with the measurement configuration is not performed. A method comprising using the wireless device to perform the measurement associated with the measurement configuration based on the failure of the SDT procedure. (Item 42) The method according to item 41, further comprising the wireless device transitioning to the RRC inactive state based on the RRC release message. (Item 43) The method according to item 41 or 42, wherein the measurement configuration includes a carrier frequency list and / or an effective area list. (Item 44) The method according to any one of items 41 to 43, further comprising starting a measurement timer based on the RRC release message using the wireless device. (Item 45) The aforementioned measurement timer, The method according to item 44, which is one or more of the timer for measurement in the RRC inactive state and / or T331. (Item 46) The method according to item 44 or 45, wherein the measurement configuration includes the value of the measurement timer. (Item 47) The method according to any one of items 44 to 46, wherein the measurement associated with the measurement configuration is performed while the measurement timer is activated. (Item 48) The method according to any one of items 44 to 47, further comprising stopping and / or pausing the measurement timer based on initiating the SDT procedure associated with the SDT configuration. (Item 49) The method of item 48, wherein the failure to perform the measurement associated with the measurement configuration is based on stopping and / or pausing the measurement timer. (Item 50) Based on the failure of the SDT procedure, the wireless device, The aforementioned measuring timer, and / or The method according to any one of items 41 to 49, further comprising restarting, starting, and / or restarting the measurement associated with the measurement configuration. (Item 51) The failure of the aforementioned SDT procedure The failure timer for the aforementioned SDT procedure has expired. Selecting a serving cell that is different from the serving cell through which the wireless device performs the SDT procedure, Receiving a fallback indicator, Receiving a rejection message, and / or The method described in any one of items 41-50, based on at least one of the reasons for determining that compliance with the RRC message is not possible. (Item 52) The method according to any one of items 41 to 51, further comprising using the wireless device to perform the measurement associated with the measurement configuration based on the RRC release message. (Item 53) The failure to perform the measurement associated with the measurement configuration is This includes stopping the measurement and / or temporarily suspending the measurement, and / or The method according to any one of items 41 to 52, based on initiating the SDT procedure associated with the SDT configuration. (Item 54) The aforementioned wireless device, Initiating the SDT procedure associated with the SDT configuration, and / or The method according to any one of items 41 to 53, further comprising transmitting the results of one or more of the one or more measurements associated with the measurement configuration based on the failure to perform the measurement associated with the measurement configuration. (Item 55) The aforementioned SDT configuration is Next hop chain number (NCC), The resumed identity of the wireless device, and The method according to any one of items 41 to 54, wherein the configured wireless bearer includes at least one of the markings shown in the SDT procedure. (Item 56) Initiating the aforementioned SDT procedure is The wireless device receives a paging message indicating the SDT procedure, and / or The method according to any one of items 41 to 55, based on one or more of the following: the data of the SDT procedure is available to the wireless device. (Item 57) During the SDT procedure, the measurement associated with the measurement configuration is not performed. Based on the determination to initiate the SDT procedure, the measurement associated with the measurement configuration is not performed. Based on sending a first uplink message regarding the SDT procedure, the measurement associated with the measurement configuration will not be performed. Based on receiving a message regarding the SDT procedure, the measurement associated with the measurement configuration will not be performed, and / or The method according to any one of items 41 to 56, which includes not performing the measurement associated with the measurement configuration based on the wireless device determining that the cell in which the SDT procedure was initiated is invalid for the measurement. (Item 58) The wireless device supports carrier aggregation and / or dual connection, and / or The method according to any one of items 41 to 57, wherein the measurement configuration is for the carrier aggregation and / or duplication of the wireless device. (Item 59) A wireless device comprising one or more processors and memory storing instructions, wherein when an instruction is executed by the one or more processors, the wireless device causes the wireless device to perform the method described in any one of items 1 to 58. (Item 60) A non-temporary computer-readable medium that, when executed by one or more processors, includes instructions causing one or more processors to perform the method described in any one of items 1 to 58. [Brief explanation of the drawing]

[0011] Some examples of various embodiments of this disclosure are described herein with reference to the drawings.

[0012] [Figure 1A] An exemplary mobile communications network in which embodiments of the present disclosure may be implemented is shown. [Figure 1B] An exemplary mobile communications network in which embodiments of the present disclosure may be implemented is shown. [Figure 2A] The new radio (NR) user plane and control plane protocol stacks are shown, respectively. [Figure 2B] The new radio (NR) user plane and control plane protocol stacks are shown, respectively. [Figure 3] Figure 2A shows an example of services provided between the protocol layers of the NR user plane protocol stack. [Figure 4A] Figure 2A shows an exemplary downlink data flow through the NR user plane protocol stack. [Figure 4B] This shows an exemplary format for the MAC subheader in a MAC PDU. [Figure 5A]This shows the mapping between the logical channels, transport channels, and physical channels for downlink and uplink, respectively. [Figure 5B] This shows the mapping between the logical channels, transport channels, and physical channels for downlink and uplink, respectively. [Figure 6] This is an illustrative diagram showing the RRC state transition of a UE. [Figure 7] This shows an example configuration of an NR frame with grouped OFDM symbols. [Figure 8] This shows an exemplary configuration of slots in the time and frequency domains of the NR carrier. [Figure 9] This example demonstrates bandwidth adaptation using three configured BWPs for an NR carrier. [Figure 10A] This shows three carrier aggregation configurations, each with two component carriers. [Figure 10B] This example illustrates how aggregation cells can be configured into one or more PUCCH groups. [Figure 11A] Examples of SS / PBCH block structure and position are shown. [Figure 11B] An example of CSI-RS mapped to the time and frequency domains is shown. [Figure 12A] Three examples of downlink and uplink beam management procedures are shown below. [Figure 12B] Three examples of downlink and uplink beam management procedures are shown below. [Figure 13A] This document presents a 4-step competition-based random access procedure, a 2-step competition-free random access procedure, and another 2-step random access procedure. [Figure 13B] This document presents a 4-step competition-based random access procedure, a 2-step competition-free random access procedure, and another 2-step random access procedure. [Figure 13C]This document presents a 4-step competition-based random access procedure, a 2-step competition-free random access procedure, and another 2-step random access procedure. [Figure 14A] An example of a CORESET configuration for the bandwidth portion is shown. [Figure 14B] This document shows an example of CCE~REG mapping for DCI transmissions during CORESET and PDCCH processing. [Figure 15] This shows an example of a wireless device that communicates with a base station. [Figure 16A] An exemplary structure for uplink and downlink transmission is shown. [Figure 16B] An exemplary structure for uplink and downlink transmission is shown. [Figure 16C] An exemplary structure for uplink and downlink transmission is shown. [Figure 16D] An exemplary structure for uplink and downlink transmission is shown. [Figure 17] An example of the RRC connection re-establishment procedure is shown. [Figure 18] An example of the procedure for resuming RRC connection is shown. [Figure 19] An example of subsequent Small Data Transmission (SDT) is shown. [Figure 20A] This example demonstrates time window management for one or more subsequent transmissions of an SDT. [Figure 20B] This example demonstrates time window management for one or more subsequent transmissions of an SDT. [Figure 21] An example of idle / inactive measurement using the SDT procedure is shown. [Figure 22] This example demonstrates how to manage idle / inactive measurements using the SDT procedure. [Figure 23] This example demonstrates how to manage idle / inactive measurements using a timer, based on the SDT procedure. [Figure 24] This example demonstrates how to detect failures in the SDT procedure using idle / inactive measurements. [Figure 25]This example demonstrates how to manage idle / inactive measurements using the SDT procedure. [Figure 26] This example demonstrates how to manage idle / inactive measurements using a timer with an SDT procedure. [Modes for carrying out the invention]

[0013] Figure 1A shows an embodiment of a mobile communications network 100 in which embodiments of the present disclosure may be implemented. The mobile communications network 100 may be, for example, a public land mobile network (PLMN) activated by a network operator. As shown in Figure 1A, the mobile communications network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and radio devices 106.

[0014] CN102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of its interface function, CN102 may establish an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging capabilities.

[0015] RAN104 can connect CN102 to radio device 106 via radio communication over an air interface. As part of the radio communication, RAN104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from RAN104 to radio device 106 over the air interface is known as the downlink, and the communication direction from radio device 106 to RAN104 over the air interface is known as the uplink. Downlink transmissions can be isolated from uplink transmissions using frequency division duplication (FDD), time division duplication (TDD), and / or some combination of the two duplication techniques.

[0016] The term "wireless device" may be used throughout this disclosure to mean and include any mobile or fixed (non-portable) device that requires or is capable of wireless communication. For example, a wireless device could be a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term "wireless device" also includes other terms, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transceiver unit (WTRU), and / or wireless communication device.

[0017] RAN104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to include and encompass Node B (associated with UMTS and / or 3G standards), evolved Node B (associated with eNB, E-UTRA and / or 4G standards), remote radio head (RRH), baseband processing unit coupled to one or more RRHs, repeater or relay node used to extend the coverage area of ​​a donor node, next-generation evolved Node B (ng-eNB), generation Node B (associated with gNB, NR and / or 5G standards), access point (AP, associated with e.g., WiFi or other suitable wireless communication standards), and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

[0018] A base station included in RAN104 may include one or more sets of antennas for communicating with the radio device 106 over an air interface. For example, one or more base stations may include three sets of antennas, each for controlling three cells (or sectors). The size of a cell may be determined by the range over which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a radio device transmitter) operating in the cell. Together, the base station cells may provide radio coverage to the radio device 106 over a wide geographical area to support radio device mobility.

[0019] In addition to the three sector sites, other implementations of base stations are possible. For example, one or more of the RAN104 base stations may be implemented as sector sites with more or fewer than three sectors. One or more of the RAN104 base stations may be implemented as access points, as baseband processing units coupled to multiple remote radio heads (RRHs), and / or as repeater or relay nodes used to extend the coverage area of ​​a donor node. Baseband processing units coupled to RRHs may be part of a centralized or cloud RAN architecture, and the baseband processing units may be centralized or virtualized within a pool of baseband processing units. Repeater nodes may amplify and rebroadcast radio signals received from donor nodes. Relay nodes may perform the same / similar functions as repeater nodes, but may decode radio signals received from donor nodes and remove noise before amplifying and rebroadcasting the radio signals.

[0020] RAN104 can be deployed as a homogeneous network of macrocell base stations having similar antenna patterns and similar high-level transmit power. RAN104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide smaller coverage areas, for example, overlapping with the relatively large coverage areas provided by macrocell base stations. Smaller coverage areas can be provided in areas with high data traffic (or so-called "hotspots") or in areas with weak macrocell coverage. Examples of small cell base stations, in order of decreasing coverage area, include microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0021] The Third Generation Partnership Project (3GPP®) was formed in 1998 to provide global standardization for mobile communication network specifications, similar to mobile communication network 100 in Figure 1A. To date, 3GPP® has produced specifications for three generations of mobile networks: third-generation (3G) networks known as Universal Mobile Communications Systems (UMTS), fourth-generation (4G) networks known as Long-Term Evolution (LTE), and fifth-generation (5G) networks known as 5G Systems (5GS). Embodiments of this disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as Next Generation RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as RAN 104 in Figure 1A, earlier RANs of 3G and 4G networks, and future networks that have not yet been specified (e.g., 3GPP 6G networks). NG-RAN can be supplied to implement 5G radio access technology, also known as New Radio (NR), and to implement other radio access technologies, including 4G radio access technology or non-3GPP® radio access technology.

[0022] Figure 1B shows another exemplary mobile communications network 150 in which embodiments of the present disclosure may be implemented. The mobile communications network 150 may be, for example, a PLMN activated by a network operator. As shown in Figure 1B, the mobile communications network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UE156A and UE156B (collectively referred to as UE156). These components may be implemented and operate in the same or similar manner as the corresponding components described with respect to Figure 1A.

[0023] 5G-CN152 provides UE156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of its interface function, 5G-CN152 may set up end-to-end connectivity between UE156 and one or more DNs, authenticate UE156, and provide charging capabilities. Compared to the CNs of 3GPP 4G networks, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN152 may be defined as network functions that provide services through interfaces to other network functions. The network functions of 5G-CN152 may be implemented in several ways, such as network elements on dedicated or shared hardware, software instances running on dedicated or shared hardware, or virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0024] As shown in Figure 1B, the 5G-CN152 includes Access and Mobility Management Function (AMF) 158A and User Plane Function (UPF) 158B, which for ease of explanation are shown in Figure 1B as a single component AMF / UPF158. The UPF158B may function as a gateway between the NG-RAN154 and one or more DNs. The UPF158B may perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic utilization reporting, uplink classification supporting routing of traffic flows to one or more DNs, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and downlink data notification triggering. The UPF158B may support multi-homed PDU sessions by functioning as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branch point. UE156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0025] The AMF158A may perform functions such as termination of non-access layer (NAS) signaling, NAS signaling security, access layer (AS) security control, inter-CN node signaling for mobility between 3GPP® access networks, idle-mode UE reachability (e.g., control and execution of paging retransmission), registered area management, intra-system and inter-system mobility support, access authentication, access permission including roaming privilege checks, mobility management control (subscriptions and policies), network slicing support, and / or selection of session management functions (SMF). NAS may refer to functions operating between CN and UE, and AS may refer to functions operating between UE and RAN.

[0026] For clarity, 5G-CN152 may include one or more additional network functions not shown in Figure 1B. For example, 5G-CN152 may include one or more of the following: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Exposure Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

[0027] NG-RAN154 can connect 5G-CN152 to UE156 via radio communication over an air interface. NG-RAN154 may include one or more gNBs (collectively gNB160) illustrated as gNB160A and gNB160B and / or one or more ng-eNBs (collectively ng-eNB162) illustrated as ng-eNB162A and ng-eNB162B. gNB160 and ng-eNB162 may more commonly be referred to as base stations. gNB160 and ng-eNB162 may include one or more sets of antennas for communicating with UE156 over an air interface. For example, one or more gNB160s and / or one or more ng-eNB162s may include three sets of antennas for controlling three cells (or sectors), each. In addition, the gNB160 and ng-eNB162 cells can provide wireless coverage to the UE156 over a wide geographical area to support UE mobility.

[0028] As shown in Figure 1B, gNB160 and / or ng-eNB162 may be connected to 5G-CN152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces may be established on an underlying transport network, such as an Internet Protocol (IP) transport network, using direct physical and / or indirect connections. gNB160 and / or ng-eNB162 may be connected to UE156 via the Uu interface. For example, as shown in Figure 1B, gNB160A may be connected to UE156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interfaces may be used by the network elements in Figure 1B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data of interest to the user. The control plane may process signaling messages of interest to the network elements.

[0029] The gNB160 and / or ng-eNB162 may be connected to one or more AMF / UPF functions of the 5G-CN152, such as the AMF / UPF158, by one or more NG interfaces. For example, the gNB160A may be connected to the UPF158B of the AMF / UPF158 by an NG-User Plane (NG-U) interface. The NG-U interface may provide the supply of user plane PDUs between the gNB160A and the UPF158B (e.g., unguaranteed delivery). The gNB160A may be connected to the AMF158A using an NG Control Plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, NAS message transport, paging, PDU session management and configuration transfer and / or warning message transmission.

[0030] The gNB160 can provide NR user plane and control plane protocol termination to UE156 on a Uu interface. For example, the gNB160A can provide NR user plane and control plane protocol termination to UE156A on a Uu interface associated with a first protocol stack. The ng-eNB162 can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to UE156 on a Uu interface, where E-UTRA refers to 3GPP 4G radio access technology. For example, the ng-eNB162B can provide E-UTRA user plane and control plane protocol termination to UE156B on a Uu interface associated with a second protocol stack.

[0031] The 5G-CN152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that it may be possible for NR to connect to the 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although only one AMF / UPF158 is shown in Figure 1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or load shares across multiple AMF / UPF nodes.

[0032] As can be considered, in Figure 1B, interfaces between network elements (e.g., Uu, Xn, and NG interfaces) may be associated with a protocol stack used by the network elements to exchange data and signaling messages. The protocol stack may include two planes: a user plane and a control plane. The user plane may process data of interest to the user, and the control plane may process signaling messages of interest to the network elements.

[0033] Figures 2A and 2B show examples of NR user plane and NR control plane protocol stacks for the Uu interface between UE210 and gNB220, respectively. The protocol stacks shown in Figures 2A and 2B may be the same as or similar to those used for the Uu interface between UE156A and gNB160A shown in Figure 1B.

[0034] Figure 2A shows the NR user plane protocol stack, which includes five layers, implemented in the UE210 and gNB220. At the bottom of the protocol stack, the physical layers (PHYs) 211 and 221 can provide transport services to the upper layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The following four protocols above PHYs 211 and 221 include the Media Access Control Layer (MAC) 212 and 222, the Radio Link Control Layer (RLC) 213 and 223, the Packet Data Convergence Protocol Layer (PDCP) 214 and 224, and the Service Data Application Protocol Layer (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0035] Figure 3 shows an example of services provided between the protocol layers of the NR user plane protocol stack. Starting from the top of Figures 2A and 3, SDAP215 and 225 may perform QoS flow processing. UE210 may receive services via a PDU session, which may be a logical connection between UE210 and DN. A PDU session may have one or more QoS flows. CN's UPF (e.g., UPF158B) may map IP packets to one or more QoS flows in the PDU session based on QoS requirements (e.g., with respect to delay, data rate, and / or error rate). SDAP215 and 225 may perform mapping / unmapping between one or more QoS flows and one or more data radio bearers. Mapping / unmapping between QoS flows and data radio bearers may be determined by SDAP225 at gNB220. SDAP215 at UE210 may be notified about the mapping between QoS flows and data radio bearers via reflected mapping or control signaling received from gNB220. Regarding reflection mapping, the SDAP225 on the gNB220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP215 on the UE210 to determine mapping / unmapping between the QoS flow and the data radio bearer.

[0036] PDCP214 and 224 may implement header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decryption of data transmitted over the air interface, and integrity protection (to ensure that control messages originate from the intended source). PDCP214 and 224 may implement, for example, retransmission of undelivered packets, intra-sequence delivery and rearrangement of packets, and removal of duplicate packets for handover within gNB. PDCP214 and 224 may implement packet duplication to improve the likelihood of receiving packets and to remove any duplicate packets at the receiver. Packet duplication may be useful for services requiring high reliability.

[0037] Although not shown in Figure 3, PDCP214 and 224 can perform mapping / unmapping between split radio bearers and RLC channels in a dual-connection scenario. Dual-connection is a technique that allows a UE to connect to two cells, or more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split radio bearer is when a single radio bearer, such as one of the radio bearers provided by PDCP214 and 224 as a service to SDAP215 and 225, is handled by a cell group in a dual-connection. PDCP214 and 224 can map / unmap split radio bearers between RLC channels belonging to the cell group.

[0038] RLC213 and 223 can perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of replicated data units received from MAC212 and 222, respectively. RLC213 and 223 can support three transmission modes: Transparent Mode (TM), Unacknowledged Response Mode (UM), and Acknowledged Response Mode (AM). Based on the transmission mode in which the RLC is operating, the RLC can perform one or more of the indicated functions. This RLC configuration can be per logical channel, independent of numerology and / or transmission time interval (TTI) duration. As shown in Figure 3, RLC213 and 223 can provide RLC channels as a service to PDCP214 and 224, respectively.

[0039] MAC212 and 222 may perform logical channel multiplexing / demultiplexing and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing of data units belonging to one or more logical channels to / from transport blocks (TBs) delivered to / from PHY211 and 221. MAC222 may be configured to perform scheduling, scheduling information reporting, and priority processing between UEs by dynamic scheduling. Scheduling may be performed by gNB220 (on MAC222) for downlink and uplink. MAC212 and 222 may be configured to perform error correction, priority processing between logical channels of UE210 by logical channel prioritization, and / or padding through Hybrid Automatic Repeating Requests (HARQ) (e.g., one HARQ entity per carrier in the case of Carrier Aggregation (CA)). MAC212 and 222 may support one or more numerology and / or transmit timings. In the embodiment, mapping restrictions in logical channel prioritization can control which numerology and / or transmission timing a logical channel may use. As shown in Figure 3, MACs 212 and 222 may provide logical channels to RLCs 213 and 223 as a service.

[0040] PHY211 and 221 can perform transport channel mapping to physical channels and digital and analog signal processing functions for transmitting and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding / decoding and modulation / demodulation. PHY211 and 221 can perform multi-antenna mapping. As shown in Figure 3, PHY211 and 221 may provide one or more transport channels to MAC212 and 222 as a service.

[0041] Figure 4A shows an exemplary downlink data flow through the NR user plane protocol stack. Figure 4A shows the downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack, generating two TBs on the gNB220. The uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow shown in Figure 4A.

[0042] The downlink data flow in Figure 4A starts when SDAP225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. In Figure 4A, SDAP225 maps IP packets n and n+1 to the first radio bearer 402 and IP packet m to the second radio bearer 404. An SDAP header (labeled "H" in Figure 4A) is added to the IP packets. Data units from / to higher protocol layers are called service data units (SDUs) of lower protocol layers, and data units to / from lower protocol layers are called protocol data units (PDUs) of higher protocol layers. As shown in Figure 4A, the data unit from SDAP225 is an SDU of the lower protocol layer PDCP224 and a PDU of SDAP225.

[0043] The remaining protocol layers in Figure 4A may perform relevant functions (e.g., with respect to Figure 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, PDCP224 may perform IP header compression and encryption and forward its output to RLC223. RLC223 may optionally perform segmentation (e.g., as shown for IP packet m in Figure 4A) and forward its output to MAC222. MAC222 may multiplex several RLC PDUs and attach MAC subheaders to the RLC PDUs to form transport blocks. In NR, as shown in Figure 4A, MAC subheaders may be distributed throughout the MAC PDU. In LTE, MAC subheaders may be placed entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated delays because the MAC PDU subheaders may be computed before the complete MAC PDU is assembled.

[0044] Figure 4B shows an exemplary format of a MAC subheader in a MAC PDU. The MAC subheader includes an SDU length field to indicate the length (e.g., in bytes) of the MAC SDU that the MAC subheader corresponds to, a logical channel identifier (LCID) field to identify the logical channel that the MAC SDU started to assist in the multiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0045] Figure 4B further illustrates MAC control elements (CEs) inserted into a MAC PDU by a MAC such as MAC223 or MAC222. For example, Figure 4B shows two MAC CEs inserted into a MAC PDU. MAC CEs may be inserted at the start of a MAC PDU for downlink transmission (as shown in Figure 4B) and at the end of a MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Examples of MAC CEs include scheduling-related MAC CEs such as buffer status reporting and power headroom reporting, start / stop MAC CEs for PDCP duplicate detection start / stop, channel status information (CSI) reporting, sounding reference signal (SRS) transmission, and pre-configured components, discontinuous receive (DRX)-related MAC CEs, timing progression MAC CEs, and random access-related MAC CEs. The MAC CE may be preceded by a MAC subheader in a format similar to that described in the MAC SDU, and may be identified by a reserved value in the LCID field, which indicates the type of control information contained in the MAC CE.

[0046] Before describing the NR control plane protocol stack, we will first explain the logical channels, transport channels, and physical channels, as well as the mapping between channel types. One or more channels can be used to perform functions related to the NR control plane protocol stack, which will be discussed later.

[0047] Figures 5A and 5B show the mapping between logical channels, transport channels, and physical channels for downlink and uplink, respectively. Information is passed through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels that carry control and configuration information in the NR control plane, or as traffic channels that carry data in the NR user plane. Logical channels can be classified as dedicated logical channels for a particular UE, or as common logical channels that can be used by two or more UEs. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example, - A paging control channel (PCCH) for carrying paging messages used to page UEs whose location is not known to the network at the cell level, - A broadcast control channel (BCCH) for transmitting system information messages in the form of master information blocks (MIBs) and several system information blocks (SIBs), wherein the system information messages are used by the UE to obtain information about how the cell is configured and how it operates within the cell. - A common control channel (CCCH) for carrying control messages along with random access, -To configure the UE, a dedicated control channel (DCCH) is used to carry control messages to and from a specific UE. - Includes a dedicated traffic channel (DTCH) for transporting user data to and from specific UEs.

[0048] A transport channel is used between the MAC layer and the PHY layer and can be defined by how they transmit the information they carry over the air interface. The set of transport channels defined by NR includes, for example, - A paging channel (PCH) for carrying paging messages transmitted from the PCCH, - A broadcast channel (BCH) for carrying MIBs from BCCH, - A downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including SIBs from BCCH, - Uplink Shared Channel (UL-SCH) for carrying uplink data and signaling messages, - Includes Random Access Channels (RACH) that allow UEs to access the network without prior scheduling.

[0049] A PHY can pass information between its processing levels using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information across one or more transport channels. The PHY can generate control information to support its low-level operation and provide control information to the lower levels of the PHY via physical control channels known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR is, for example, - A physical broadcast channel (PBCH) for carrying MIBs from the BCH, - A physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from DL-SCH, and paging messages from PCH, - A physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorization, and uplink power control commands. -UL-SCH and, as described below, in some examples, a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from uplink control information (UCI), - A physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgment responses, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR), - Includes a physical random access channel (PRACH) for random access.

[0050] Similar to the physical control channel, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in Figures 5A and 5B, the physical layer signals defined by NR include the primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), sounding reference signal (SRS), and phase tracking reference signal (PT-RS). These physical layer signals are described in more detail below.

[0051] Figure 2B shows an exemplary NR control plane protocol stack. In Figure 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as the exemplary NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack, as in the NR user plane protocol stack, the NR control plane stack has Radio Resource Control (RRC) 216 and 226, and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0052] NAS protocols 217 and 237 can provide control plane functions between the UE210 and the AMF230 (e.g., AMF158A), or more generally, between the UE210 and the CN. NAS protocols 217 and 237 can provide control plane functions between the UE210 and the AMF230 via signaling messages referred to as NAS messages. There is no direct path for NAS messages to be transported between the UE210 and the AMF230. NAS messages can be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0053] RRC216 and 226 may provide control plane functionality between UE210 and gNB220, or more generally, between UE210 and RAN. RRC216 and 226 may provide control plane functionality between UE210 and gNB220 via signaling messages referred to as RRC messages. RRC messages may be transmitted between UE210 and RAN using a signaling radio bearer and the same / similar PDCP, RLC, MAC, and PHY protocol layers. MAC may multiplex control plane and user plane data within the same transport block (TB). RRC216 and 226 may provide control plane functions such as broadcasting system information related to the AS and NAS, paging initiated by the CN or RAN, establishing, maintaining, and releasing RRC connections between the UE210 and the RAN, security functions including key management, establishing, configuring, maintaining, and releasing signaling radio bearers and data radio bearers, mobility functions, QoS management functions, UE measurement reporting and reporting control, radio link failure (RLF) detection and recovery, and / or NAS message forwarding. As part of establishing the RRC connection, RRC216 and 226 may establish an RRC context, which may involve setting parameters for communication between the UE210 and the RAN.

[0054] Figure 6 is an exemplary diagram illustrating the RRC state transitions of a UE. The UE may be identical or similar to the wireless device 106 shown in Figure 1A, the UE 210 shown in Figures 2A and 2B, or any other wireless device described herein. As shown in Figure 6, the UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0055] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be one of more base stations included in RAN104 shown in Figure 1A, one of gNB160 or ng-eNB162 shown in Figure 1B, gNB220 shown in Figures 2A and 2B, or any other base station similar to any other base station described herein. The base station to which the UE is connected may have the UE's RRC context. The RRC context, referred to as the UE context, may include parameters for communication between the UE and the base station. These parameters may include, for example, one or more AS contexts, one or more radio link configuration parameters, bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions), security information, and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. In RRC connection 602, the UE's mobility may be managed by the RAN (e.g., RAN104 or NG-RAN154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and adjacent cells and report these measurements to the base station currently serving the UE. Based on the reported measurements, the UE's serving base station may request a handover to one of the adjacent base stations. The RRC state may transition from RRC connection 602 to RRC idle 604 via connection release procedure 608, or to RRC inactive 606 via connection deactivation procedure 610.

[0056] In RRC idle 604, an RRC context cannot be established for the UE. In RRC idle 604, the UE cannot have an RRC connection with the base station. While in RRC idle 604, the UE may be in a sleep state for most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once per discontinuous receive cycle) to monitor paging messages from the RAN. The mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connection 602 via a connection establishment procedure 612, which may involve a random access procedure, as will be discussed in more detail below.

[0057] In RRC inactive 606, the previously established RRC context is maintained at the UE and base station. This reduces signaling overhead compared to the transition from RRC idle 604 to RRC connected 602, enabling a faster transition to RRC connected 602. In RRC inactive 606, the UE is in a sleep state, and the UE's mobility can be managed by the UE through cell reselection. The RRC state can transition from RRC inactive 606 to RRC connected 602 via connection restart procedure 614, or to RRC idle 604 via connection release procedure 616, which is identical or similar to connection release procedure 608.

[0058] The RRC state can be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to enable the network to notify the UE of events via paging messages without broadcasting paging messages across the entire mobile communications network. The mobility management mechanisms used in RRC idle 604 and RRC inactive 606 may enable the network to track the UE at the cell group level so that paging messages can be broadcast on the cells of the cell group in which the UE currently resides, instead of across the entire mobile communications network. The mobility management mechanisms in RRC idle 604 and RRC inactive 606 track the UE at the cell group level. They can do this using grouping at different granularities. For example, there may be three levels of granularity for cell grouping: individual cells, cells within a RAN area identified by a RAN Area Identifier (RAI), and cells within a group of RAN areas, referred to as a tracking area and identified by a Tracking Area Identifier (TAI).

[0059] A tracking area can be used to track a UE at the CN level. The CN (e.g., CN102 or 5G-CN152) may provide the UE with a list of TAIs associated with the UE registration area. If the UE moves to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area through cell reselection, the UE may perform a registration update in the CN and provide the UE with a new UE registration area, allowing the CN to update the UE's location.

[0060] RAN areas can be used to track UEs at the RAN level. For UEs in an RRC inactive 606 state, a RAN notification area may be assigned to the UE. A RAN notification area may contain one or more cell identities, a list of RAIs, or a list of TAIs. In embodiments, a base station may belong to one or more RAN notification areas. In embodiments, a cell may belong to one or more RAN notification areas. If a UE moves to a cell that is not included in the RAN notification area assigned to the UE through cell reselection, the UE may perform a notification area update in the RAN and update the UE's RAN notification area.

[0061] A base station that stores the RRC context for a UE, or the last serving base station of the UE, may be referred to as an anchor base station. The anchor base station may maintain the RRC context for the UE for at least a period of time while the UE remains in the anchor base station's RAN notification area and / or for a period of time while the UE remains in an RRC inactive 606.

[0062] A gNB, such as the gNB160 in Figure 1B, can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0063] In NR, physical signals and physical channels (considered in relation to Figures 5A and 5B) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols (e.g., M orthogonal amplitude modulation (M-QAM) or M phase-shift keying (M-PSK) symbols) which are divided into F parallel symbol streams, referred to as source symbols. The F parallel symbol streams can be used as input to an inverse fast Fourier transform (IFFT) block that converts them to the time domain as if they were in the frequency domain. The IFFT block can take one from each of the F parallel symbol streams at a time into an F source symbol, and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be an F time domain sample representing the sum of the F orthogonal subcarriers. An F time domain sample can form a single OFDM symbol. After some processing (e.g., adding cyclic prefixes) and upconversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This processing generates OFDM symbols precoded with discrete Fourier transform (DFT), which can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The reverse processing can be performed on the OFDM symbols at the receiver using an FFT block to reconstruct the data mapped to the source symbols.

[0064] Figure 7 shows an exemplary configuration of an NR frame in which OFDM symbols are grouped. An NR frame can be identified by a System Frame Number (SFN). An SFN may repeat over a period of 1024 frames. As shown, one NR frame may have a duration of 10 milliseconds (ms) and may contain 10 subframes, each with a duration of 1 millisecond. A subframe may be divided into slots, for example, each containing 14 OFDM symbols.

[0065] The duration of a slot may depend on the numerology used for the OFDM symbol of the slot. NR supports flexible numerology to accommodate different cell deployments (e.g., cells with carrier frequencies less than 1 GHz up to a maximum of mm-wavelengths). Numerology can be defined with respect to subcarrier spacing and cyclic prefix duration. For numerology in NR, subcarrier spacing can be scaled up by a power of 2 from a baseline subcarrier spacing of 15 kHz, and cyclic prefix duration can be scaled down by a power of 2 from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerology with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs, 30 kHz / 2.3 μs, 60 kHz / 1.2 μs, 120 kHz / 0.59 μs, and 240 kHz / 0.29 μs.

[0066] A slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier intervals have shorter slot durations and, accordingly, more slots per subframe. Figure 7 shows this numerology-dependent slot duration and the slot transmission structure per subframe (for ease of illustration, numerologies with a 240 kHz subcarrier interval are not shown in Figure 7). Subframes within the NR can be used as a numerology-independent time reference, while slots can be used as units on which uplink and downlink transmissions are scheduled. To support low latency, scheduling in the NR is separated from slot duration and can start with any OFDM symbol and continue for as many symbols as needed for transmission. These partial slot transmissions may be referred to as mini-slot transmissions or sub-slot transmissions.

[0067] Figure 8 shows an exemplary configuration of slots in the time and frequency domains of an NR carrier. Slots contain resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in the NR. As shown in Figure 8, an RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain. An RB spans 12 consecutive REs in the frequency domain, as shown in Figure 8. An NR carrier may be limited to a width of 275 RBs or 275 × 12 = 3300 subcarriers. When used, such limitations can restrict the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, with the 400 MHz bandwidth being set based on a carrier bandwidth limit of 400 MHz per unit.

[0068] Figure 8 shows a single numerology used across the entire bandwidth of the NR carrier. In other exemplary configurations, multiple numerologies may be supported on the same carrier.

[0069] NR can support a wide range of carrier bandwidths (e.g., up to 400 MHz for a 120 kHz subcarrier spacing). Not all UEs can receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibited from a power consumption standpoint for the UE. In some embodiments, to reduce power consumption and / or for other purposes, the UE may adapt the size of its receive bandwidth based on the amount of traffic scheduled to be received by the UE. This is called bandwidth adaptation.

[0070] NR supports UEs that cannot receive the full carrier bandwidth and defines a Bandwidth Portion (BWP) that supports bandwidth adaptation. In embodiments, a BWP may be defined by a subset of consecutive RBs on the carrier. A UE may consist of one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell) (e.g., via the RRC layer). At a given time, one or more of the BWPs configured for a serving cell may be active. These one or more BWPs may be referred to as the active BWPs of the serving cell. When a serving cell consists of a secondary uplink carrier, the serving cell may have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0071] For non-paired spectra, if the downlink BWP index of a downlink BWP is the same as the uplink BWP index of an uplink BWP, then a downlink BWP from a configured set of downlink BWPs can be linked with an uplink BWP from a configured set of uplink BWPs. For non-paired spectra, the UE can expect that the center frequency of a downlink BWP is the same as the center frequency of an uplink BWP.

[0072] For a downlink BWP within a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE for at least one search space with one or more control resource sets (CORESETs). A search space is a set of locations in the time and frequency domains from which a UE can find control information. A search space can be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, in an active downlink BWP, a base station may configure a UE in a common search space on a PCell or on a primary / secondary cell (PSCell).

[0073] For uplink BWPs within a configured set of uplink BWPs, the BS may configure the UE with one or more resource sets for one or more PUCCH transmissions. The UE may receive downlink receptions (e.g., PDCCH or PDSCH) within the downlink BWP according to the configured numerology (e.g., subcarrier interval and cyclic prefix duration) to the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) within the uplink BWP according to the configured numerology (e.g., subcarrier interval and cyclic prefix length of the uplink BWP).

[0074] One or more BWP indicator fields may be provided to the Downlink Control Information (DCI). The values ​​of the BWP indicator fields may indicate which of the configured set of BWPs is the active downlink BWP for one or more downlink receptions. The values ​​of one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions.

[0075] A base station may semi-statically configure a UE with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. If the base station does not provide a default downlink BWP for the UE, the default downlink BWP may be the initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0076] A base station may configure the UE with a PCell BWP inactive timer value. The UE may start or restart the BWP inactive timer at any appropriate time. For example, the UE may start or restart the BWP inactive timer when (a) the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired-spectrum operation, or (b) the UE detects a DCI indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP for non-paired-spectrum operation. If the UE does not detect a DCI for a certain period (e.g., 1 millisecond or 0.5 milliseconds), the UE may start the BWP inactive timer toward expiration (e.g., increasing it from zero to the BWP inactive timer value, or decreasing it from the BWP inactive timer value to zero). When the BWP inactive timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0077] In the embodiment, a base station may semi-statically configure a UE having one or more BWPs. The UE may switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating a second BWP as the active BWP, and / or in response to the expiration of a BWP inactivity timer (for example, if the second BWP is the default BWP).

[0078] Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a currently inactive BWP) can occur independently in a paired spectrum. In a non-paired spectrum, downlink and uplink BWP switching can occur simultaneously. Switching between configured BWPs can occur based on RRC signaling, DCI, expiration of BWP inactivity timers, and / or the initiation of random access.

[0079] Figure 9 shows an example of bandwidth adaptation using three configured BWPs for an NR carrier. The UE, consisting of the three BWPs, can switch from one BWP to another at a switching point. In the example shown in Figure 9, the BWPs include BWP902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz, BWP904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz, and BWP906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP902 may be the initial active BWP, and BWP904 may be the default BWP. The UE can switch between BWPs at a switching point. In the embodiment of Figure 9, the UE may switch from BWP902 to BWP904 at switching point 908. Switching at switching point 908 may occur for any preferred reason, for example, in response to the expiration of a BWP inactive timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP904 as the active BWP. The UE may switch from active BWP904 to BWP906 at switching point 910 in response to receiving a DCI indicating BWP906 as the active BWP. The UE may switch from active BWP906 to BWP904 at switching point 912 in response to the expiration of the BWP inactive timer and / or in response to receiving a DCI indicating BWP904 as the active BWP. The UE may switch from active BWP904 to BWP902 at switching point 914 in response to receiving a DCI indicating BWP902 as the active BWP.

[0080] If a UE is configured for a secondary cell with a set of configured downlink BWPs and a default downlink BWP in the timer value, the UE procedure for switching BWPs on the secondary cell may be identical / similar to that on the primary cell. For example, the UE may use the timer value and default downlink BWP on the secondary cell in the same / similar manner that the UE uses these values ​​on the primary cell.

[0081] To provide higher data rates, carrier aggregation (CA) can be used to aggregate two or more carriers and transmit them simultaneously to the same UE. The aggregated carriers in CA may be called component carriers (CCs). When CA is used, there are multiple serving cells for the UE and one for the CC. A CC can have three configurations within the frequency domain.

[0082] Figure 10A shows three CA configurations with two CCs. In the in-band, continuous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are positioned directly adjacent to each other within the frequency band. In the in-band, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and separated into frequency bands by a gap. In the in-band configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).

[0083] In the embodiment, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacings, and / or duplication schemes (TDD or FDD). A serving cell of a UE using a CA may have downlink CCs. In the case of FDD, one or more uplink CCs may be optionally configured for the serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when a UE has more data traffic on the downlink than on the uplink.

[0084] When using a Carrier Aggregation (CA), one of the aggregation cells of the UE may be referred to as the primary cell (PCell). The PCell may be the serving cell to which the UE first connects during RRC connection establishment, re-establishment, and / or handover. The PCell may provide the UE with NAS mobility information and security inputs. The UE may have different PCells. On the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). On the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). Other aggregation cells for the UE may be referred to as secondary cells (SCells). In some embodiments, the SCell may be configured after the PCell has been configured for the UE. For example, the SCell may be configured via an RRC connection reconfiguration procedure. On the downlink, the carrier corresponding to the SCell may be referred to as the downlink secondary CC (DL SCC). On the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC).

[0085] SCells configured for a UE can be started and stopped, for example, based on traffic and channel conditions. Stopping a SCell may mean that PDCCH and PDSCH reception on the SCell is stopped, and PUSCH, SRS, and CQI transmission on the SCell is stopped. Configured SCells can be started and stopped using MAC CEs with respect to Figure 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., from a subset of configured SCells) for the UE are started or stopped. Configured SCells can be stopped in response to the expiration of SCell stop timers (e.g., one SCell stop timer per SCell).

[0086] Downlink control information, such as cell scheduling assignments and scheduling authorizations, may be transmitted on the cell corresponding to the assignment and authorization, known as self-scheduling. DCIs for a cell may be transmitted on another cell, known as cross-carrier scheduling. Uplink control information for aggregation cells (e.g., HARQ acknowledgments and channel state feedback such as CQI, PMI, and / or RI) may be transmitted on the PCell's PUCCH. A large number of aggregated downlink CCs can overload the PCell's PUCCH. A cell may be divided into multiple PUCCH groups.

[0087] Figure 10B shows an example of how aggregation cells may be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 may each contain one or more downlink CCs. In the example in Figure 10B, PUCCH group 1010 contains three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050, in this example, contains three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as primary SCells (PSCells) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CC of PUCCH group 1010, indicated as UCI1031, UCI1032, and UCI1033, can be transmitted on the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050, indicated as UCI1071, UCI1072, and UCI1073, can be transmitted on the uplink of PSCell 1061. In this embodiment, if the aggregation cell depicted in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050, the single uplink PCell and PCell for transmitting UCI related to the downlink CC may become overloaded. Overload can be prevented by dividing the transmission of UCI between PCell 1021 and PSCell 1061.

[0088] A cell containing a downlink carrier and optionally an uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may, depending on the context in which the physical cell ID is used, identify the downlink carrier and / or uplink carrier of the cell. The physical cell ID may be determined using synchronization signals transmitted on the downlink component carrier. The cell index may be determined using RRC messages. In this disclosure, the physical cell ID may be referred to as the carrier ID, and the cell index may be referred to as the carrier index. For example, if this disclosure refers to a first physical cell ID for a first downlink carrier, this disclosure may mean that the first physical cell ID is for a cell containing the first downlink carrier. The same / similar concepts may apply, for example, to carrier activation. If this disclosure indicates that a first carrier is activated, this specification may mean that the cell containing the first carrier is activated.

[0089] In a CA, the multi-carrier nature of the PHY may be exposed to the MAC. In the embodiment, HARQ entities may operate on a serving cell. Transport blocks may be generated per allocation / authorization per serving cell. Transport blocks and potential HARQ retransmissions of transport blocks may be mapped to serving cells.

[0090] On the downlink, the base station may transmit one or more reference signals (RS) (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as shown in Figure 5A) to the UE (e.g., unicast, multicast, and / or broadcast). On the uplink, the UE may transmit one or more RS to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in Figure 5B). PSS and SSS may be transmitted by the base station, used by the UE, and synchronize the UE to the base station. PSS and SSS may be provided within a synchronization signal (SS) / physical broadcast channel (PBCH) block, which includes PSS, SSS, and PBCH. The base station may periodically transmit bursts of SS / PBCH blocks.

[0091] Figure 11A shows an embodiment of the structure and location of an SS / PBCH block. A burst of SS / PBCH blocks may consist of one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in Figure 11A). Bursts may be transmitted periodically (e.g., every two frames or every 20 milliseconds). Bursts may be limited to half frames (e.g., a first half frame with a duration of 5 milliseconds). Figure 11A is an embodiment, and it will be understood that these parameters (number of SS / PBCH blocks per burst, burst period, burst location within a frame) may be configured based on, for example, the carrier frequency of the cell from which the SS / PBCH block is transmitted, the cell's numerology or subcarrier spacing, the network configuration (e.g., using RRC signaling), or any other preferred factor. In the embodiment, the UE may assume a subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless the radio network is configured to assume a different subcarrier spacing.

[0092] An SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols as shown in the embodiment of Figure 11A) and one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). PSS, SSS, and PBCH may have a common center frequency. A PSS may be transmitted first, e.g., spanning one OFDM symbol and 127 subcarriers. An SSS may be transmitted after a PSS (e.g., the next two symbols), spanning one OFDM symbol and 127 subcarriers. A PBCH may be transmitted after a PSS (e.g., spanning the next three OFDM symbols), spanning 240 subcarriers.

[0093] The location of SS / PBCH blocks in the time and frequency domains may be unknown to the UE (e.g., when the UE is searching for a cell). To find and select a cell, the UE may monitor the carrier of the PSS. For example, the UE may monitor the frequency position within the carrier. If the PSS is not found after a certain duration (e.g., 20 milliseconds), the UE may search for the PSS at a different frequency position within the carrier, as indicated by the synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine the locations of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). In the embodiment, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on the synchronization raster. In the embodiment, cell selection / search and / or re-selection may be based on the CD-SSB.

[0094] SS / PBCH blocks can be used by the UE to determine one or more parameters of a cell. For example, the UE may determine the physical cell identifier (PCI) of a cell based on the PSS and SSS sequences, respectively. The UE may also determine the position of a cell's frame boundary based on the position of the SS / PBCH block. For example, an SS / PBCH block may indicate that it was transmitted according to a transmission pattern, and the SS / PBCH block in the transmission pattern is at a known distance from the frame boundary.

[0095] The PBCH may use QPSK modulation and forward error correction (FEC). FEC may use polar coding. One or more symbols spanning the PBCH may carry one or more DMRS for demodulation of the PBCH. The PBCH may include a representation of the cell's current system frame number (SFN) and / or SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a Master Information Block (MIB) used to provide one or more parameters to the UE. The MIB is used by the UE to identify the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may include information necessary for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include the SIB1. The SIB1 can be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of the SIB1. Based on the PBCH indicating the absence of SIB1, a frequency may be pointed to the UE. The UE may then search the SS / PBCH block at the frequency pointed to by the UE.

[0096] A UE may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index will be quasi-copositioned (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial Rx parameters). A UE cannot assume that QCLs for transmitted SS / PBCH blocks will have different SS / PBCH block indices.

[0097] SS / PBCH blocks (e.g., blocks within a half-frame) can be transmitted in a spatial direction (e.g., using different beams across the cell's coverage area). In the embodiment, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

[0098] In the embodiment, within the carrier frequency span, a base station may transmit multiple SS / PBCH blocks. In the embodiment, the first PCI of the first SS / PBCH block of the multiple SS / PBCH blocks may be different from the second PCI of the second SS / PBCH block of the multiple SS / PBCH blocks. PCIs of SS / PBCH blocks transmitted at different frequency locations may be different or the same.

[0099] CSI-RS can be transmitted by a base station and used by an UE to obtain channel status information (CSI). A base station may configure an UE with one or more CSI-RS for channel estimation or any other preferred purpose. A base station may configure an UE with one or more identical / similar CSI-RS. An UE may measure one or more CSI-RS. Based on the measurement of one or more downlink CSI-RS, an UE may estimate the downlink channel status and / or generate a CSI report. An UE may provide the CSI report to the base station. The base station may use the feedback provided by the UE (e.g., estimated downlink channel status) to perform link fitting.

[0100] A base station can semi-statically configure a UE with one or more sets of CSI-RS resources. CSI-RS resources may be associated with location and periodicity within the time and frequency domains. A base station may selectively activate and / or deactivate CSI-RS resources. A base station may indicate to the UE that CSI-RS resources within a set of CSI-RS resources are being activated and / or deactivated.

[0101] A base station may configure a UE to report CSI measurements. The base station may configure a UE to provide CSI reports periodically, aperiodicly, or semi-persistently. For periodic CSI reporting, the UE may consist of multiple CSI reports with varying timing and / or periodicity. For aperiodic CSI reporting, the base station may request CSI reports. For example, the base station may instruct a UE to measure configured CSI-RS resources and provide CSI reports on the measurements. For semi-persistent CSI reporting, the base station may configure a UE to periodically transmit periodic reports and selectively activate or deactivate them. The base station may configure a UE with CSI-RS resource sets and CSI reports using RRC signaling.

[0102] A CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to use the same OFDM symbols for the downlink CSI-RS and the control resource set (CORESET) if the downlink CSI-RS and CORESET are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the physical resource block (PRB) configured for the CORESET. The UE may also be configured to use the same OFDM symbols for the downlink CSI-RS and the SS / PBCH block if the downlink CSI-RS and the SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block.

[0103] Downlink DMRS may be transmitted by a base station and used by an UE for channel estimation. For example, downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCHs). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station can semi-statically configure an UE using the number of front-loaded DMRS symbols (e.g., maximum number) of the PDSCH. A DMRS configuration may support one or more DMRS ports. For example, in the case of single-user MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. In the case of multi-user MIMO, a DMRS configuration may support up to four orthogonal downlink DMRS ports per UE. A wireless network can support common DMRS structures for downlink and uplink (e.g., at least for CP-OFDM). DMRS locations, DMRS patterns, and / or scrambling sequences may be the same or different. A base station may transmit downlink DMRS and corresponding PDSCHs using the same precoding matrix. A UE may use one or more downlink DMRSs for coherent demodulation / channel estimation of PDSCHs.

[0104] In the embodiment, a transmitter (e.g., a base station) may use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices may differ based on the fact that the first bandwidth is different from the second bandwidth. The UE may assume that the same precoder matrix is ​​used across a set of PRBs. A set of PRBs may be represented as a precoder resource block group (PRG).

[0105] A PDSCH may contain one or more layers. The UE may assume that at least one symbol with a DMRS exists on one or more layers of the PDSCH. The upper layers may constitute up to three DMRSs for the PDSCH.

[0106] Downlink PT-RS may be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS depends on the RRC configuration. The presence and / or pattern of downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters used for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, the dynamic presence of downlink PT-RS may be associated with one or more DCI parameters, including at least the MCS. An NR network may support multiple PT-RS densities defined in the time and / or frequency domains. The frequency domain density, if present, may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. Downlink PT-RS may be limited to the UE's scheduled time / frequency duration. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

[0107] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station may use uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit uplink DMRS on PUSCH and / or PUCCH. Uplink DMRS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to transmit on one or more symbols of PUSCH and / or PUCCH. The base station may semi-statically configure the UE with a number (e.g., maximum number) of front-loaded DMRS symbols for PUSCH and / or PUCCH that the UE may use to schedule single-symbol DMRS and / or dual-symbol DMRS. The NR network may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS location, DMRS pattern, and / or DMRS scrambling sequence may be identical or different.

[0108] A PUSCH may include one or more layers, and a UE may transmit at least one symbol having DMRS present on one or more layers of the PUSCH. In the embodiment, the upper layers may constitute up to three DMRS for the PUSCH.

[0109] Uplink PT-RS (which may be used by base stations for phase tracking and / or phase noise compensation) may or may not exist depending on the UE's RRC configuration. The presence and / or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) which may be indicated by RRC signaling and / or DCI. When configured, the dynamic presence of uplink PT-RS may be associated with one or more DCI parameters, including at least the MCS. A radio network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density may be associated with at least one configuration of the scheduled bandwidth, if it exists. A UE may assume the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. For example, uplink PT-RS may be limited to the UE's scheduled time / frequency duration.

[0110] SRS can be transmitted by the UE to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link fitting. The SRS transmitted by the UE may enable the base station to estimate the uplink channel state at one or more frequencies. The base station's scheduler can use the estimated uplink channel state to allocate one or more resource blocks for uplink push transmissions from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. In the case of an SRS resource set, the base station may configure the UE with one or more SRS resources. SRS resource set applicability may be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources within one or more SRS resource sets (e.g., having identical / similar time-domain behavior, periodic, aperiodic, and / or similar) may be transmitted instantaneously (e.g., simultaneously). The UE may transmit one or more SRS resources within an SRS resource set. NR networks may support aperiodic, periodic, and / or semi-persistent SRS transmissions. A UE may transmit SRS resources based on one or more trigger types, which may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. In embodiments, at least one DCI format may be used by the UE to select at least one of one or more configured sets of SRS resources. SRS trigger type 0 may refer to an SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In embodiments, if a PUSCH and an SRS are transmitted in the same slot, the UE may be configured to transmit the SRS after the PUSCH and the corresponding uplink DMRS transmission.

[0111] A base station may quasi-statistically configure a UE with one or more SRS configuration parameters indicating at least one of the following: SRS resource configuration identifier, number of SRS ports, time-domain behavior of the SRS resource configuration (e.g., representation of periodic, semi-persistent, or aperiodic SRS), slots, minislots, and / or subframe-level periodicity, offsets for periodic and / or aperiodic SRS resources, number of OFDM symbols in the SRS resource, start OFDM symbol of the SRS resource, SRS bandwidth, frequency-hopping bandwidth, period shift, and / or SRS sequence ID.

[0112] Antenna ports are defined such that the channel on which a symbol on an antenna port is carried can be inferred from the channel on which another symbol on the same antenna port is carried. When a first symbol and a second symbol are transmitted on the same antenna port, a receiver can infer the channel for carrying the second symbol on the antenna port (e.g., fade gain, multipath delay, and / or similar) from the channel for carrying the first symbol on the antenna port. The first and second antenna ports may be said to be quasi-copositional (QCL) if one or more large-scale characteristics of the channel on which the first symbol on the first antenna port is carried can be inferred from the channel on which the second symbol on the second antenna port is carried. One or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial receive (Rx) parameters.

[0113] In channels using beamforming, beam management is required. Beam management may include beam measurement, beam selection, and beam display. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamforming reference signals. The UE may perform downlink beam measurements based on a downlink reference signal (e.g., Channel Status Information Reference Signal (CSI-RS)) and generate a beam measurement report. The UE may perform downlink beam measurement procedures after the RRC connection is set up at the base station.

[0114] Figure 11B shows an example of a Channel State Information Reference Signal (CSI-RS) mapped to time and frequency domains. The square shown in Figure 11B may span resource blocks (RBs) within the cell bandwidth. A base station can transmit one or more RRC messages containing CSI-RS resource configuration parameters that indicate one or more CSI-RSs. One or more of the following parameters can be set by higher-layer signaling (e.g., RRC and / or MAC signaling) for the CSI-RS resource configuration. CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., position of symbols and resource elements (REs) within subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity of radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmit comb, pseudo-collocation (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0115] The three beams shown in Figure 11B can be configured for a UE with a UE-specific configuration. Three beams are shown in Figure 11B (beam #1, beam #2, and beam #3), and more or fewer beams can be configured. Beam #1 may be assigned to CSI-RS1101, which can be transmitted on one or more subcarriers within the RB of a first symbol. Beam #2 may be assigned to CSI-RS1102, which can be transmitted on one or more subcarriers within the RB of a second symbol. Beam #3 may be assigned to CSI-RS1103, which can be transmitted on one or more subcarriers within the RB of a third symbol. By using frequency division multiplexing (FDM), a base station may transmit another CSI-RS associated with a beam from another UE using other subcarriers within the same RB (e.g., those not used to transmit CSI-RS1101). By using time-domain multiplexing (TDM), the beams used for a UE may be configured so that the UE's beam uses symbols from the beams of other UEs.

[0116] The CSI-RS signals shown in Figure 11B (e.g., CSI-RS 1101, 1102, 1103) are transmitted by a base station and may be used by a UE for one or more measurements. For example, a UE may measure the reference signal received power (RSRP) of a configured CSI-RS resource. The base station may configure the UE with a reporting configuration, and the UE may report the RSRP measurement to the network (e.g., via one or more base stations) based on the reporting configuration. In an embodiment, the base station may determine one or more transmit configuration indication (TCI) states, including several reference signals, based on the reported measurement results. In an embodiment, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE may receive a downlink transmission with a received (Rx) beam determined based on one or more TCI states. In an embodiment, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, it may determine the spatial domain filter of the transmit (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam correspondence capability, it may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured for the UE by the base station. The base station may select and display an uplink beam for the UE based on measurements of one or more SRS resources transmitted by the UE.

[0117] In beam management procedures, the UE may evaluate (e.g., measure) the channel quality of a beam pair link, including one or more beam pair links, a transmit beam transmitted by a base station, and a receive beam received by the UE. Based on the evaluation, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters, including, for example, one or more beam identities (e.g., beam index, reference signal index, or similar), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0118] Figure 12A shows examples of three downlink beam management procedures, P1, P2, and P3. Procedure P1 may enable UE measurements on the transmit (Tx) beam of a transmit / receive point (TRP) (or multiple TRPs) to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at the TRP may include a Tx beam sweep of the beam set (shown in the top rows of P1 and P2 as ellipses rotating counterclockwise, indicated by dashed arrows). Beamforming at the UE may include an Rx beam sweep for the beam set (shown in the bottom rows of P1 and P3 as ellipses rotating counterclockwise, indicated by dashed arrows). Procedure P2 may be used to enable UE measurements on the Tx beam of a TRP (shown in the top row of P2 as ellipses rotating counterclockwise, indicated by dashed arrows). The UE and / or base station may perform step P2 using a smaller set of beams than those used in step P1, or using a narrower beam than those used in step P1. This may be referred to as beam refinement. The UE may perform step P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0119] Figure 12B shows examples of three uplink beam management procedures, U1, U2, and U3. Procedure U1 may be used to allow a base station to perform measurements on a UE's Tx beam to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE may include, for example, a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ellipses rotating counterclockwise when indicated by dashed arrows). Beamforming at the base station may include, for example, an Rx beam sweep from a set of beams (shown in the top rows of U1 and U2 as ellipses rotating counterclockwise when indicated by dashed arrows). Procedure U2 may be used to allow a base station to adjust its Rx beam when the UE is using a fixed Tx beam. The UE and / or base station may perform procedure U2 using a smaller set of beams than used in procedure P1, or using a narrower beam than the beam used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust the Tx beam when the base station is using a fixed Rx beam.

[0120] Based on the detection of a beam failure, the UE may initiate a beam failure recovery (BFR) procedure. Based on the initiation of the BFR procedure, the UE may send a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or similar). The UE may detect a beam failure based on the determination that the quality of the beam pair link of the relevant control channel is unsatisfactory (e.g., having an error rate higher than the error rate threshold, a received signal power lower than the received signal power threshold, a timer expiring, and / or similar).

[0121] A UE may measure the quality of a beampair link using one or more reference signals (RS) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulated reference signals (DMRS). The quality of a beampair link may be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference plus noise ratio (SINR) value, reference signal reception quality (RSRQ) value, and / or CSI values ​​measured on the RS resources. A base station may indicate that an RS resource is quasi-co-located (QCL) with one or more DMRS of a channel (e.g., control channel, shared data channel, and / or similar). An RS resource and one or more DMRS of a channel may be QCLed if the channel characteristics from a transmission to the UE via the RS resources (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameter, fade, and / or similar) are similar to or identical to the channel characteristics from a transmission to the UE via the channel.

[0122] A network (e.g., the network's gNB and / or ng-eNB) and / or UE may initiate a random access procedure. A UE in the RRC_IDLE state and / or the RRC_INACTIVE state may initiate a random access procedure to request network connection setup. A UE may initiate a random access procedure from the RRC_CONNECTED state. A UE may initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or obtain uplink timing (e.g., if the uplink synchronization state is not synchronized). A UE may initiate a random access procedure to request one or more System Information Blocks (SIBs) (e.g., SIB2, SIB3, and / or other system information such as similar ones). A UE may initiate a random access procedure for beam failure recovery requests. A network may initiate a random access procedure to establish time alignment for handover and / or SCell addition.

[0123] Figure 13A shows a four-step competition-based random access procedure. Before the procedure begins, the base station may send a configuration message 1310 to the UE. Figure 13A includes the sending of four messages: Msg1 1311, Msg2 1312, Msg3 1313, and Msg4 1314. Msg1 1311 may contain and / or be referred to as a preamble (or random access preamble). Msg2 1312 may contain and / or be referred to as a random access response (RAR).

[0124] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. One or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. One or more RACH parameters may include at least one of the following: one or more general parameters for a random access procedure (e.g., RACH-configGeneral), one or more cell-specific parameters (e.g., RACH-configCommon), and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast one or more RRC messages to one or more UEs. One or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). Based on one or more RACH parameters, the UE may determine the time-frequency resources and / or uplink transmit power for transmitting Msg1 1311 and / or Msg3 1313. Based on one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg2 1312 and Msg4 1314.

[0125] One or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for sending Msg1 1311. One or more PRACH opportunities may be predefined. One or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). One or more RACH parameters may indicate an association between (a) one or more PRACH opportunities and (b) one or more reference signals. One or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. One or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunities and / or the number of preambles mapped to the SS / PBCH blocks.

[0126] One or more RACH parameters provided in configuration message 1310 can be used to determine the uplink transmit power of Msg1 1311 and / or Msg3 1313. For example, one or more RACH parameters may indicate reference power for preamble transmission (e.g., received target power and / or initial power for preamble transmission). There may be one or more power offsets indicated by one or more RACH parameters. For example, one or more RACH parameters may indicate a power ramping step, a power offset between SSB and CSI-RS, a power offset between transmissions of Msg1 1311 and Msg3 1313, and / or a power offset value between preamble groups. One or more RACH parameters may indicate one or more thresholds for the UE to determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carriers (e.g., normal uplink (NUL) carrier and / or complementary uplink (SUL) carrier).

[0127] Msg1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to constitute one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The UE may determine the preamble groups based on the path loss measurement and / or the size of Msg3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal that has an RSRP exceeding an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may, for example, select at least one preamble associated with one or more reference signals and / or the selected preamble group if the association between one or more preambles and at least one reference signal is constituted by the RRC message.

[0128] The UE may determine the preamble based on one or more RACH parameters provided in configuration message 1310. For example, the UE may determine the preamble based on path loss measurements, RSRP measurements, and / or the size of Msg3 1313. In another embodiment, one or more RACH parameters may indicate the preamble format, the maximum number of preamble transmissions, and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station may use one or more RACH parameters to configure the UE with associations between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS). If associations are configured, the UE may determine, based on the associations, to include the preamble in Msg1 1311. Msg1 1311 may be transmitted to the base station via one or more PRACH opportunities. The UE may use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and PRACH opportunity determination. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and one or more reference signals.

[0129] The UE may perform a preamble retransmission if no response is received after a preamble transmission. The UE may increase the uplink transmit power for preamble retransmission. The UE may select an initial preamble transmit power based on path loss measurements and / or target received preamble power configured by the network. The UE may decide to retransmit the preamble and ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramping step of the preamble retransmission. The ramping step may be the amount of incremental increase in uplink transmit power for retransmission. The UE may ramp up the uplink transmit power if it determines that the reference signal (e.g., SSB and / or CSI-RS) is the same as the previous preamble transmission. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that a random access procedure has failed and completed if, for example, the number of preamble transmissions exceeds a threshold determined by one or more RACH parameters (e.g., preambleTransMax).

[0130] Msg2 1312 received by a UE may contain RARs. In some scenarios, Msg2 1312 may contain multiple RARs corresponding to multiple UEs. Msg2 1312 may be received after or in response to the transmission of Msg1 1311. Msg2 1312 may be scheduled on the DL-SCH and displayed on the PDCCH using a Random Access RNTI (RA-RNTI). Msg2 1312 may indicate that Msg1 1311 has been received by the base station. Msg2 1312 may contain time alignment commands that the UE can use to adjust the UE's transmission timing, scheduling permission for the transmission of Msg3 1313, and / or a temporary cell RNTI (TC-RNTI). After the UE has transmitted the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg2 1312. A UE may determine when to start a time window based on the PRACH opportunity that the UE uses to transmit a preamble. For example, a UE may start a time window after one or more symbols of the last symbol of the preamble (e.g., on the first PDCCH opportunity from the end of preamble transmission). One or more symbols may be determined based on numerology. PDCCH may be in a common lookup space composed of RRC messages (e.g., a Type1-PDCCH common lookup space). A UE may identify a RAR based on a Radio Network Temporary Identifier (RNTI). An RNTI may be used in response to one or more events that initiate a Random Access Procedure. A UE may use a Random Access RNTI (RA-RNTI). An RA-RNTI may be associated with a PRACH opportunity that the UE uses to transmit a preamble. For example, a UE may determine an RA-RNTI based on the OFDM symbol index, slot index, frequency domain index, and / or the UL carrier indicator of the PRACH opportunity. An embodiment of an RA-RNTI may be as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id In the formula, s_id can be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH opportunity in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for a NUL carrier, 1 for a SUL carrier).

[0131] A UE may send Msg3 1313 in response to the successful reception of Msg2 1312 (for example, using the resources identified in Msg2 1312). Msg3 1313 may be used for conflict resolution in a conflict-based random access procedure, for example, as shown in Figure 13A. In some scenarios, multiple UEs may send the same preamble to a base station, and the base station may provide a RAR corresponding to the UEs. If multiple UEs interpret the RAR as corresponding to themselves, a mismatch may occur. Conflict resolution (e.g., using Msg3 1313 and Msg4 1314) can be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To implement conflict resolution, a UE may include a device identifier in Msg3 1313 (e.g., C-RNTI, if assigned, TC-RNTI included in Msg2 1312, and / or any other suitable identifier).

[0132] Msg4 1314 may be received after or in response to the transmission of Msg3 1313. If a C-RNTI was included in Msg3 1313, the base station uses the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is found on the PDCCH, the random access procedure is determined to have completed successfully. If a TC-RNTI was included in Msg3 1313 (e.g., if the UE is in the RRC_IDLE state or otherwise not connected to the base station), Msg4 1314 is received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU matches the CCCH SDU transmitted in Msg3 1313 (e.g., transmitted), or otherwise contains the corresponding UE conflict resolution identity MAC CE, the UE may determine that conflict resolution was successful, and / or the UE may determine that the random access procedure has completed successfully.

[0133] A UE may consist of a complementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedures) may be supported on the uplink carrier. For example, a base station may configure a UE with two separate RACH configurations, namely one for the SUL carrier and one for the NUL carrier. In the case of random access within a cell configured with SUL carriers, the network may indicate which carrier (NUL or SUL) to use. A UE may determine a SUL carrier, for example, if the measured quality of one or more reference signals is below the broadcast threshold. Uplink transmissions of random access procedures (e.g., Msg1 1311 and / or Msg3 1313) may remain on the selected carrier. In one or more instances, a UE may switch uplink carriers during a random access procedure (e.g., between Msg1 1311 and Msg3 1313). For example, the UE may determine and / or switch the uplink carriers for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (e.g., listen before talk).

[0134] Figure 13B illustrates a two-step, non-conflict random access procedure. Similar to the four-step, conflict-based random access procedure shown in Figure 13A, the base station may send a configuration message 1320 to the UE before the procedure begins. Configuration message 1320 may be similar in some respects to configuration message 1310. Figure 13B includes the sending of two messages, Msg1 1321 and Msg2 1322. Msg1 1321 and Msg2 1322 may be similar in some respects to Msg1 1311 and Msg2 1312 shown in Figure 13A, respectively. As can be understood from Figures 13A and 13B, a non-conflict random access procedure may not include messages similar to Msg3 1313 and / or Msg4 1314.

[0135] The uncontested random access procedure shown in Figure 13B may be initiated for beam failure recovery, other SI requests, SCell addition, and / or handover. For example, a base station may display or assign to the UE the preamble to be used for Msg1 1321. The UE may receive a display of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0136] After sending the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the RAR's PDCCH. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions addressed to Cell RNTI (C-RNTI) in the search space. In the uncontested random access procedure shown in Figure 13B, the UE may determine that the random access procedure has completed successfully after sending Msg1 1321 and receiving the corresponding Msg2 1322, or in response to it. The UE may determine that the random access procedure has completed successfully, for example, if the PDCCH transmission is addressed to C-RNTI. The UE may determine that the random access procedure has completed successfully, for example, if the UE receives a RAR containing a preamble identifier corresponding to a preamble sent by the UE, and / or if the RAR contains a MAC sub-PDU containing the preamble identifier. The UE may determine the response as an acknowledgment of the response to the SI request.

[0137] Figure 13C shows another two-step random access procedure. Similar to the random access procedures shown in Figures 13A and 13B, the base station may send a configuration message 1330 to the UE before the procedure begins. The configuration message 1330 may be similar in some respects to the configuration messages 1310 and / or 1320. Figure 13C includes the transmission of two messages, namely MsgA 1331 and MsgB 1332.

[0138] MsgA 1331 may be transmitted by the UE via uplink transmission. MsgA 1331 may include one or more transmissions of the preamble 1341 and / or one or more transmissions of the transport block 1342. The transport block 1342 may include content similar to and / or equivalent to the content of Msg3 1313 shown in Figure 13A. The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or similar). The UE may receive MsgB 1332 after or in response to the transmission of MsgA 1331. MsgB 1332 may include content similar to and / or equivalent to the content of Msg2 1312 (e.g., RAR) shown in Figures 13A and 13B, and / or the content of Msg4 1314 shown in Figure 13A.

[0139] The UE may initiate the two-step random access procedure shown in Figure 13C for authorized and / or unauthorized spectra. The UE may determine whether to initiate the two-step random access procedure based on one or more factors. One or more factors may be the radio access technology in use (e.g., LTE, NR, and / or similar), whether the UE has a valid TA, cell size, the UE's RRC status, the spectrum type (e.g., authorized vs. unauthorized), and / or any other suitable factors.

[0140] The UE may determine the radio resources and / or uplink transmit power for the transport block 1342 contained in the preamble 1341 and / or MsgA 1331 based on the two-step RACH parameters contained in the configuration message 1330. The RACH parameters may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or transport block 1342. The time-frequency resources for transmitting the preamble 1341 (e.g., PRACH) and the time-frequency resources for transmitting the transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the receive timing and downlink channel for monitoring and / or receiving MsgB 1332.

[0141] Transport block 1342 may include data (e.g., latency-sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may transmit MsgB 1332 in response to MsgA 1331. MsgB 1332 may include at least one of the following: a preamble identifier, timing advance commands, power control commands, uplink authorization (e.g., radio resource allocation and / or MCS), a UE identifier for conflict resolution, and / or RNTI (e.g., C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure has been successfully completed if the preamble identifier in MsgB 1332 matches a preamble transmitted by the UE, and / or the UE identifier in MsgB 1332 matches the UE identifier in MsgA 1331 (e.g., transport block 1342).

[0142] UEs and base stations may exchange control signaling. Control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). Control signaling may include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0143] Downlink control signaling may include downlink scheduling assignments, uplink scheduling authorizations indicating uplink radio resources and / or transport formats, slot format information, preemption indications, power control commands, and / or other optional signaling. A UE may receive downlink control signaling in a payload transmitted by a base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group-common PDCCH (GC-PDCCH) common to a group of UEs.

[0144] A base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate the detection of transmission errors. When the DCI is intended for a UE (or group of UEs), the base station may scramble the CRC parity bits with the UE identifier (or identifier of the group of UEs). Scrambling the CRC parity bits with an identifier may involve Modulo-2 addition (or exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a 16-bit value of a Radio Network Temporary Identifier (RNTI).

[0145] DCIs can be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or system information change notifications. P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. SI-RNTI may be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a unicast transmission of dynamic scheduling and / or a random access trigger for a PDCCH sequence. A DCI with a scrambled CRC parity bit in a temporary cell RNTI (TC-RNTI) may indicate a conflict resolution (e.g., Msg3 similar to Msg3 1313 shown in Figure 13A). Other RNTI encodings configured in the UE by the base station include Configured Scheduling RNTI (CS-RNTI), Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or similar.

[0146] Depending on the purpose and / or content of the DCI, a base station may transmit DCI in one or more DCI formats. For example, DCI format 0_0 can be used for scheduling pushes within a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling pushes within a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling PDSCHs within a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used for scheduling PDSCHs within a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format representation to a group of UEs. DCI format 2_1 may be used to notify a group of UEs of physical resource blocks and / or OFDM symbols that the UEs assume are not intended for transmission to the UEs. DCI format 2_2 may be used for transmitting transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 may be used for transmitting a group of TPC commands for SRS transmission by one or more UEs. DCI formats for new features may be defined in future releases. DCI formats may have different DCI sizes or share the same DCI size.

[0147] After scrambling the DCI with RNTI, the base station may process the DCI with channel coding (e.g., polar coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the coded and modulated DCI onto resource elements used and / or configured for the PDCCH. Based on the DCI payload size and / or base station coverage, the base station may transmit the DCI over a PDCCH occupying several consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) can be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may contain a number of resource element groups (REGs) (e.g., 6). A REG may contain resource blocks in OFDM symbols. Mapping the coded and modulated DCI onto resource elements may be based on mappings of CCEs and REGs (e.g., CCE-REG mappings).

[0148] Figure 14A shows an example of a CORESET configuration for a bandwidth portion. A base station may transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may contain time-frequency resources that the UE attempts to decode the DCI using one or more lookup spaces. A base station may configure a CORESET within a time-frequency domain. In the embodiment of Figure 14A, the first CORESET 1401 and the second CORESET 1402 occur at the first symbol in the slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. The third CORESET 1403 occurs at the third symbol in the slot. The fourth CORESET 1404 occurs at the seventh symbol in the slot. A CORESET may have a different number of resource blocks within the frequency domain.

[0149] Figure 14B shows an example of CCE-REG mapping for DCI transmissions on CORESET and PDCCH processing. CCE-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference adjustment and / or frequency-selective transmission of control channels). A base station may implement different or the same CCE-REG mapping on different CORESETs. A CORESET may be associated with CCE-REG mapping in an RRC configuration. A CORESET may consist of antenna port pseudo-collocation (QCL) parameters. The antenna port QCL parameters may indicate QCL information for demodulated reference signals (DMRS) for PDCCH reception within the CORESET.

[0150] A base station may send an RRC message to the UE containing configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters may indicate the relationship between the search space sets and the CORESETs. A search space set may contain a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate the number of PDCCH candidates monitored per aggregation level, the PDCCH monitoring period and PDCCH monitoring pattern, one or more DCI formats monitored by the UE, and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in a common search space set may be predefined and known to the UE. The set of CCEs in a UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

[0151] As shown in Figure 14B, the UE may determine the time-frequency resources of the CORESET based on the RRC message. The UE may determine the CCE~REG mapping to the CORESET (e.g., interleaved or non-interleaved, and / or mapping parameters) based on the CORESET configuration parameters. The UE may determine the number of search space sets configured on the CORESET (e.g., up to 10) based on the RRC message. The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates from the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates having possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs in a common search space, the number of PDCCH candidates, and / or the number of PDCCH candidates in a UE-specific search space), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The UE may determine a valid DCI for the UE in response to a CRC check (e.g., a scramble bit against the CRC parity bit of a DCI that matches an RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink permission, power control, slot format indication, downlink preemption, and / or similar).

[0152] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. After receiving the DL-SCH transport block, the UE may transmit a HARQ acknowledgment. The uplink control signaling may include channel status information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station may determine the transmission format parameters for downlink transmission (e.g., multi-antenna and beamforming schemes). The uplink control signaling may include a scheduling request (SR). The UE may transmit an SR to the base station indicating that uplink data is available for transmission. The UE may transmit UCI (e.g., HARQ acknowledgment (HARQ-ACK), CSI report, SR, etc.) over the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via PUCCH using one of several PUCCH formats.

[0153] There are five possible PUCCH formats, and a UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols and UCI bits in the UCI transmission). PUCCH format 0 may have the length of one or two OFDM symbols and may contain two or fewer bits. A UE may use PUCCH format 0 to transmit a UCI in a PUCCH resource if the transmission exceeds one or two symbols and has one or two HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits). PUCCH format 1 may occupy a number between 4 and 14 OFDM symbols and may contain two or fewer bits. A UE may use PUCCH format 1 if the transmission is four or more symbols and has one or two HARQ-ACK / SR bits. PUCCH format 2 may occupy one or two OFDM symbols and may contain more than two bits. A UE may use PUCCH format 2 if the transmission consists of more than one or two symbols and has two or more UCI bits. PUCCH format 3 may occupy a number between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 3 if the transmission consists of four or more symbols, has two or more UCI bits, and the PUCCH resource does not contain orthogonal cover codes. PUCCH format 4 may occupy a number between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 4 if the transmission consists of four or more symbols, has two or more UCI bits, and the PUCCH resource contains orthogonal cover codes.

[0154] A base station may, for example, use an RRC message to send configuration parameters for multiple PUCCH resource sets to the UE. Multiple PUCCH resource sets (e.g., up to four sets) may be configured on the cell's uplink BWP. A PUCCH resource set may consist of multiple PUCCH resources, each having a PUCCH resource identified by a PUCCH resource set index, a PUCCH resource identifier (e.g., pucch-Resourceid), and / or the number of UCI information bits (e.g., maximum number) that the UE can transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE may select one of the multiple PUCCH resource sets based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of the UCI information bits is 2 or less, the UE may select the first PUCCH resource set whose index is equal to "0". If the total bit length of the UCI information bits is greater than 2 and less than or equal to the first configuration value, the UE may select a second PUCCH resource set with a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configuration value and less than or equal to the second configuration value, the UE may select a third PUCCH resource set with a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configuration value and less than or equal to the third value (e.g., 1406), the UE may select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

[0155] After determining a PUCCH resource set from multiple PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine a PUCCH resource based on the PUCCH resource indicator in the DCI (e.g., DCI format 1_0 or DCI format 1_1) received on the PDCCH. The 3-bit PUCCH resource indicator in the DCI may indicate one of the eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0156] Figure 15 shows an embodiment of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 shown in Figure 1A, the mobile communication network 150 shown in Figure 1B, or other communication networks. Although only one wireless device 1502 and one base station 1504 are shown in Figure 15, it will be understood that a mobile communication network may include more than one UE and / or more base stations having the same or similar configuration as shown in Figure 15.

[0157] Base station 1504 may connect radio device 1502 to a core network (not shown) via radio communication over an air interface (or radio interface) 1506. The communication direction from base station 1504 to radio device 1502 over air interface 1506 is known as the downlink, and the communication direction from radio device 1502 to base station 1504 over air interface is known as the uplink. Downlink transmissions may be isolated from uplink transmissions using FDD, TDD, and / or some combination of two redundancy techniques.

[0158] In the downlink, data transmitted from base station 1504 to radio device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 by, for example, the core network. In the uplink, data transmitted from radio device 1502 to base station 1504 may be provided to processing system 1518 of radio device 1502. Processing systems 1508 and 1518 may process the data for transmission by implementing OSI functions of layers 3 and 2. Layer 2 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer with respect to Figures 2A, 2B, 3, and 4A. Layer 3 may include the RRC layer with respect to Figure 2B.

[0159] Data that has been processed by processing system 1508 and is to be transmitted to radio device 1502 may be provided to the transmission processing system 1510 of base station 1504. Similarly, data that has been processed by processing system 1518 and is to be transmitted to base station 1504 may be provided to the transmission processing system 1520 of radio device 1502. Transmission processing systems 1510 and 1520 may implement the OSI functions of layer 1. Layer 1 may include a PHY layer with respect to Figures 2A, 2B, 3, and 4A. For transmission processing, the PHY layer may perform, for example, forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to a physical channel, modulation of the physical channel, multiple input multiple output (MIMO) or multi-antenna processing, and / or similar.

[0160] At base station 1504, receiving processing system 1512 may receive uplink transmissions from radio device 1502. At radio device 1502, receiving processing system 1522 may receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 may implement OSI functions of layer 1. Layer 1 may include a PHY layer with respect to Figures 2A, 2B, 3, and 4A. For receiving processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or similar.

[0161] As shown in Figure 15, the wireless device 1502 and the base station 1504 may include multiple antennas. Multiple antennas may be used to implement one or more MIMO or multi-antenna techniques such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other embodiments, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0162] Processing systems 1508 and 1518 may be associated with memories 1514 and 1524, respectively. Memories 1514 and 1524 (e.g., one or more non-temporary computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions considered in this application. Although not shown in Figure 15, transmitting processing systems 1510, 1520, receiving processing system 1512, and / or receiving processing system 1522 may be coupled to memories (e.g., one or more non-temporary computer-readable media) that store computer program instructions or code that can be executed to perform one or more of their respective functions.

[0163] Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. One or more controllers and / or one or more processors may include, for example, general-purpose processors, digital signal processors (DSPs), microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) and / or other programmable logic devices, discrete gates and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and base station 1504 to operate in a wireless environment.

[0164] Processing system 1508 and / or processing system 1518 can each be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 include software and / or hardware that provide features and / or functions, such as speakers, microphones, keypads, displays, touch pads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, frequency modulation (FM) radio units, media players, Internet browsers, electronic control units (e.g., for vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, optical sensors, cameras, and / or the like). Processing system 1508 and / or processing system 1518 can receive user input data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data. The processing system 1518 within the wireless device 1502 can receive power from a power source and / or be configured to distribute power to other components within the wireless device 1502. The power source can include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. Processing system 1508 and / or processing system 1518 can each be connected to a GPS chipset 1517 and a GPS chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 can each be configured to provide geographical location information of the wireless device 1502 and the base station 1504, respectively.

[0165] Figure 16A shows an exemplary structure for uplink transmission. The baseband signal representing the physical uplink shared channel may perform one or more functions. These one or more functions may include at least one of the following: scrambling, modulation of scrambled bits to generate complex-valued symbols, mapping of complex-valued modulated symbols onto one or more transmitting layers, conversion precoding to generate complex-valued symbols, precoding of complex-valued symbols, mapping of precoded complex-valued symbols to resource elements, generation of complex-valued time-domain single-carrier frequency-division multiplexing (SC-FDMA) or CP-OFDM signals to antenna ports, and / or similar. In the embodiment, if conversion precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In the embodiment, if conversion precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by Figure 16A. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

[0166] Figure 16B shows an exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal to the antenna port. Filtering may be used before transmission.

[0167] FIG. 16C shows an exemplary structure of downlink transmission. A baseband signal representing a physical downlink channel can perform one or more functions. These one or more functions include scrambling of encoded bits in a codeword to be transmitted on a physical channel, modulation of the scrambled bits to generate complex-valued modulation symbols, mapping of the complex-valued modulation symbols onto one or several transmission layers, precoding of the complex-valued modulation symbols on a layer for transmission on an antenna port, mapping of the complex-valued modulation symbols of an antenna port to resource elements, generation of a complex-valued time-domain OFDM signal for each antenna port, and / or the like. These functions are shown as examples, and it is expected that other mechanisms can be implemented in various embodiments.

[0168] FIG. 16D shows another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal can be a complex-valued OFDM baseband signal for an antenna port. Filtering can be used before transmission.

[0169] A wireless device can receive from a base station one or more messages (e.g., RRC messages) including configuration parameters of a plurality of cells (e.g., a primary cell, a secondary cell). The wireless device can communicate with at least one base station (e.g., two or more base stations for dual connectivity) via a plurality of cells. One or more messages (e.g., as part of the configuration parameters) can include physical, MAC, RLC, PCDP, SDAP, RRC layer parameters for configuring the wireless device. For example, the configuration parameters can include parameters for configuring physical layer and MAC layer channels, bearers, etc. For example, the configuration parameters can include parameters indicating values of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0170] When a timer is started, it starts a process and may continue to run until it is stopped or expires. A timer may be started when it is not running, or restarted when it is running. A timer may be associated with a value (for example, a timer may start or restart from a certain value, or start from zero and expire when it reaches a value). The duration of a timer may not be updated until the timer is stopped or expires (for example, by BWP switching). A timer may be used to measure a time period / window for a process. Where this specification refers to implementations and procedures related to one or more timers, it will be understood that there are multiple ways to implement one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period / window for a procedure. For example, a random access response window timer may be used to measure a window time for receiving a random access response. In embodiments, instead of the start and expiration of a random access response window timer, a time difference between two timestamps may be used. When a timer is restarted, a process for measuring a time window may be restarted. Other exemplary implementations may be provided to restart the measurement of the time window.

[0171] The UE can be either in an RRC connected state or in an RRC inactive state when an RRC connection is established. If an RRC connection is not established, the UE is in an RRC idle state.

[0172] When a UE is in an RRC idle state, the UE (or its RRC layer) or base station may enable PLMN selection, broadcasting of system information, cell reselection mobility, and mobile termination data paging to be initiated by 5GC, and support DRX for core network (CN) paging configured by the non-access layer (NAS). When a UE is in an RRC idle state, UE-specific DRX may be configured by UE-controlled mobility based on the upper layers and / or network configuration. When a UE is in an RRC idle state, the UE (or its RRC layer) may monitor short messages transmitted via DCI in P-RNTI, monitor paging channels for core network (CN) paging using Serving Temporary Mobile Subscriber Identity (S-TMSI) (e.g., 5G-S-TMSI), perform adjacent cell measurement and cell (re)selection, obtain system information, send SI requests, and perform logging of available measurements along with the location and time of the logged measurement-configured UE.

[0173] When a UE is in an RRC inactive state, the UE (or its RRC layer) or base station may support PLMN selection, broadcasting of system information, cell reselection mobility, paging being initiated by NG-RAN (RAN paging), RAN-based notification areas (RNAs) being managed by NG-RANs, DRX for RAN paging configured by NG-RANs, core network (e.g., 5G core, 5GC)-RAN (e.g., base station) connectivity (both control and / or user plane) being established for the UE, UE AS contexts being stored in the RAN and UEs, and RANs knowing which RNA the UE belongs to. For example, when a UE (or its RRC layer) is in an RRC inactive state, the UE-specific DRX may be configured by a higher layer or by the RRC layer, the UE may implement / support UE-controlled mobility based on the network configuration, the UE may store UE inactive AS contexts, and RAN-based notification areas (RNAs) may be configured by the RRC layer. When a UE is in an RRC inactive state, the UE (or its RRC layer) may monitor short messages transmitted via DCI in P-RNTI, monitor paging channels for CN paging using S-TMSI and RAN paging with fully inactive RNTI (I-RNTI) (or fully reactivated identity), perform adjacent cell measurements and cell (re)selection, perform RAN-based notification area (RNA) updates periodically and when moving outside the configured RAN-based notification area, acquire system information, send SI requests, and perform logging of available measurements along with the location and time of logged measurement-configured UEs.

[0174] When a UE is in an RRC connected state, the UE (or its RRC layer) or base station may support the establishment of a 5GC-NG-RAN connection (both C / U planes) to the UE, the storage of the UE AS context in the RAN (e.g., base station) and the UE, the RAN knowing which cell the UE belongs to, the transfer of unicast data to and from the UE, and network control mobility including measurement. For example, when a UE is in an RRC connected state, the UE (its RRC layer) can store the AS context, transfer / receive unicast data, and in the lower layers, it can perform / support network control mobility within the NR and between the E-UTRA, using one or more SCells for UEs that support CA, aggregated with SpCells for increased bandwidth, and using one SCG for UEs that support DC, aggregated with MCG for increased bandwidth, and when a UE is in an RRC connected state, it can monitor short messages transmitted over P-RNTI via DCI, monitor control channels associated with shared data channels to determine if data is scheduled for it, provide channel quality and feedback information, perform adjacent cell measurements and measurement reports, acquire system information, and perform immediate minimization of drive test (MDT) measurements along with available location reports.

[0175] Radio bearers can be classified into two groups: data radio bearers (DRBs) for user plane data and signaling radio bearers (SRBs) for control plane data.

[0176] A signaling radio bearer (SRB) can be defined as a radio bearer (RB) used solely for transmitting RRC and NAS messages. The following SRBs can be defined: SRB0 may be for RRC messages using a common control channel (CCCH) logical channel; SRB1 may be for RRC messages (including piggyback NAS messages) as well as NAS messages before SRB2 is established, using an all-dedicated control channel (DCCH) logical channel; SRB2 may be for NAS and RRC messages, including logged measurement information, using an all-DCCH logical channel; SRB2 may have a lower priority than SRB1 and may be configured by the network after access layer (AS) security activation; and SRB3 may be for specific RRC messages using an all-DCCH logical channel when the UE is dual-connected (e.g., (NG)EN-DC or NR-DC). Downlink, piggybacking of NAS messages may be used for a single dependent procedure (e.g., success / failure of joint), namely bearer establishment / modification / release. Uplink piggybacking of NAS messages may be used to forward initial NAS messages during (RRC) connection setup and (RRC) connection restart. NAS messages forwarded via SRB2 may be contained in RRC messages that do not contain RRC protocol control information. When AS security is activated, all RRC messages on SRB1, SRB2, and SRB3, including those containing NAS messages, may be integrity protected and encrypted by PDCP. The NAS may independently apply integrity protection and encryption to NAS messages. Split SRB may be supported for dual connections (e.g., multi-radio (MR)-DC option) on both SRB1 and SRB2. Split SRB may not be supported for SRB0 and SRB3. For operation with shared spectral channel access, SRB0, SRB1, and SRB3 may be assigned a highest priority channel access class (CAPC) (e.g., CAPC=1), while the CAPC for SRB2 is configurable.

[0177] The MAC layer of a UE or base station can provide different types of data transfer services. Each logical channel type can be defined by the type of information being transferred. Logical channels can be classified into two groups: control channels and traffic channels. Control channels can be used to transfer control plane information, including broadcast control channels (BCCH), which are downlink channels for broadcasting system control information; paging control channels (PCCH), which are downlink channels for carrying paging messages; and common control channels (CCCH), which are channels for transmitting control information between the UE and the network. This channel is used by UEs without RRC connectivity to the network, and by dedicated control channels (DCCH), which are point-to-point bidirectional channels for transmitting dedicated control information between the UE and the network. Traffic channels, i.e., dedicated traffic channels (DTCH), which are point-to-point channels dedicated to one UE for the transfer of user information, can be used to transfer user plane information. DTCHs can exist on both uplink and downlink.

[0178] A UE may transition to the RRC connected state when an RRC connection is established or resumed. A UE may transition to the RRC idle state when an RRC connection is released or suspended. A UE may transition to the RRC inactive state when an RRC connection is suspended. While a UE is in the RRC idle state, it may have suspended RRC connections. Based on suspended RRC connections in the RRC idle state, a UE is in the RRC idle state with suspended RRC connections.

[0179] RRC connection establishment may include SRB1 establishment. The base station may complete RRC connection establishment before completing the establishment of the connection to the core network (e.g., N2 / N3 connection) (e.g., before receiving UE context information from a core network entity (e.g., AMF)). Access layer (AS) security may not be activated in the initial stages of RRC connection. During the initial stages of RRC connection, the base station may configure the UE to perform measurement reporting. The UE may send a corresponding measurement report if AS security activation is successful. The UE may receive or accept a handover message (e.g., a handover command) when AS security is activated.

[0180] Upon receiving a UE context from the core network (e.g., AMF), the RAN (base station) can activate AS security (both encryption and integrity protection) using the initial AS security activation procedure. RRC messages for initiating AS security (commands and success responses) may be integrity protected while encryption is initiated after the procedure is complete. Responses to RRC messages used to activate AS security may not be encrypted, while subsequent messages (e.g., used to establish SRB2 and DRB) may be integrity protected and encrypted. After initiating the initial AS security activation procedure, the network (e.g., base station) can begin establishing SRB2 and DRB, for example, before receiving confirmation of initial AS security activation from the UE. The network may apply both encryption and integrity protection to RRC reconfiguration messages used to establish SRB2 and DRB. If initial AS security activation and / or radio bearer establishment fails, the network must release the RRC connection. Configurations using SRB2 without a DRB or DRB without an SRB2 may not be supported (i.e., SRB2 and at least one DRB must be configured with the same RRC reconfiguration message, and it may not be permitted to release all DRBs without releasing the RRC connection). For Integrated Access and Backhaul Mobile Termination (IAB-MT), configurations using SRB2 without a DRB may be supported.

[0181] The RRC connection release can be initiated by the network. The release procedure may be redirected to re-direct the UE to an NR frequency or an E-UTRA carrier frequency.

[0182] RRC connection suspension can be initiated by the network. When RRC connection is suspended, the UE may remember the UE inactive AS context and any configuration received from the network, and transition to an RRC inactive state. RRC messages for suspending RRC connection may be integrity protected and encrypted.

[0183] The resumption of a suspended RRC connection can be initiated by a higher layer when the UE needs to transition from an RRC inactive state to an RRC connected state, or by the RRC layer to perform RNA updates, or by RAN paging from a RAN (e.g., a base station). Once the RRC connection is resumed, the network may configure the UE according to the RRC connection resumption procedure, based on the stored UE inactive AS context and any RRC configuration received from the network. The RRC connection resumption procedure reactivates AS security and re-establishes the SRB and DRB.

[0184] In response to a request to resume an RRC connection, the network may resume the suspended RRC connection and send / transition the UE to the RRC connection state, or reject the request to resume and send the UE to the RRC inactive state (using a standby timer), or directly suspend the RRC connection again and send the UE to RRC_INACTIVE, or directly release the RRC connection and send / transition the UE to the RRC idle state, or instruct the UE to initiate NAS level recovery (in this case, the network sends an RRC setup message). For user data (DRB), encryption may provide confidentiality of user data, and integrity protection may provide integrity of user data. For RRC signaling (SRB), encryption may provide confidentiality and integrity protection of signaling data. Encryption and integrity protection may be optionally configured, except for RRC signaling, where integrity protection may always be configured. Encryption and integrity protection may be configured per DRB.

[0185] For key management and data handling, network entities or UE-processed cleartext may be protected from physical attacks and placed in a secure environment. Base station (e.g., gNB or eNB) (AS) keys may be cryptographically separated from (NAS) keys. Separate AS and NAS-level security mode command (SMC) procedures may be used. A sequence number (COUNT) may be used as input for encryption and integrity protection, and a given sequence number may be used once for a given key (excluding identical retransmissions) on the same radio bearer in the same direction.

[0186] The security keys are organized and derived as follows: Core network entity keys (e.g., AMF or Mobility Management Entity (MME) keys) may include KAMF (or KMME). Core network entity keys may be keys derived by the Security Anchor Function (SEAF) from the UE's Mobile Device (ME) and SEAF (KSEAF) keys. NAS signaling keys may include KNASint, which is a key derived by the UE and core network's Mobile Device (ME) from the core network entity keys, and which may be used to protect NAS signaling using a specific integrity algorithm, and KNASenc, which is a key derived by the ME and core network entities from the core network entity (e.g., KAMF / KMME) keys, and which may be used to protect NAS signaling using a specific encoding algorithm. The key of a base station (e.g., gNB or eNB) may include KgNB (or KeNB) being a key derived by the core network entity (e.g., AMF / MME) from the key of the ME and core network entity (e.g., KAMF / KMME). The base station key may be further derived by the ME and source base station when performing horizontal or vertical key derivation. The key of UP traffic may include KUPenc being a key derived by the ME and base station from the base station key, which can be used to protect UP traffic between the ME and base station using a specific coding algorithm, and KUPint being a key derived by the ME and base station from the base station key, which can be used to protect UP traffic between the ME and base station using a specific integrity algorithm. The RRC signaling key may include KRRCint being a key derived from the base station's key and the base station's ME, which can be used to protect RRC signaling using a specific encoding algorithm, and KRRCenc being a key derived from the base station's key and the base station's ME, which can be used to protect RRC signaling using a specific encryption algorithm.The intermediate key may include the following: the next hop parameter (NH) is a key derived by the ME and core network entities (e.g., AMF / MME) to provide forward security; and the KgNB* (or KeNB*) is a key derived by the ME and base station when performing horizontal or vertical key derivation.

[0187] Primary authentication enables mutual authentication between the UE and the network and may provide an anchor key called KSEAF. From KSEAF, keys for core network entities (e.g., KAMF / KMME) may be created, for example, during primary authentication or NAS key rekeying and key reload events. Based on the core network entity keys, KNASint and KNASenc may be derived when initiating a successful NAS SMC procedure.

[0188] When it is necessary to establish an initial AS security context between the UE and the base station, the core network entity (e.g., AMF / MME) and the UE can derive the key of the base station (e.g., KgNB / KeNB) and the next-hop parameter (NH). The key of the base station and NH can be derived from the key of the core network entity. The next-hop chain counter (NCC) can be associated with each key of the base station and NH parameter. The key of the base station can be associated with the NCC corresponding to the NH value from which it is derived. In the initial setup, the key of the base station can be directly derived from the key of the core network entity and then can be considered to be associated with a virtual NH parameter having an NCC value equal to 0. In the initial setup, the derived NH value can be associated with the NCC value 1. In the handover, the base of the key of the base station used between the UE and the target base station called KgNB* (or KeNB*) can be derived from either the current active key of the base station or the NH parameter. If KgNB* (or KeNB*) can be derived from the current active key of the base station, this is referred to as horizontal key derivation and is shown to the UE using a non-increasing NCC. If KgNB* (or KeNB*) is derived from the NH parameter, the derivation is referred to as vertical key derivation and is shown to the UE with an NCC increase. KRRCint, KRRCenc, KUPint, and KUPenc can be derived based on the key of the base station after the new key of the base station is derived.

[0189] Based on the key derivation, the base station having knowledge of the key of the base station (e.g., KgNB / KeNB) shared with the UE cannot calculate any previous KgNB used between the same UE and the previous base station and thus can provide backward security. The base station having knowledge of the key of the base station shared with the UE may not be able to predict any future key of the base station used between the same UE and another base station after n or more handovers (since the NH parameter can only be calculated by the UE and the core network entity (e.g., AMF / MME)).

[0190] The AS SMC procedure may be for RRC and UP security algorithm negotiation and RRC security activation. Once the AS security context is established at the base station, the AMF (or MME) may transmit the UE's security capabilities to the base station. The base station may select an encryption algorithm. The selected encryption algorithm may have the highest priority from its constituent list and may also be present in the security capabilities. The base station may select an integrity algorithm. The selected integrity algorithm may have the highest priority from its constituent list and may also be present in the security capabilities. The selected algorithm may be indicated to the UE in the AS SMC, and this message may be integrity protected. RRC downlink encryption (encoding) at the base station may start after sending the AS SMC message. RRC uplink decryption (decryption) at the base station may start after receiving the integrity protected AS security mode completion message from the UE and successfully verifying it. The UE may verify the validity of the AS SMC message from the base station by verifying the integrity of the received message. RRC uplink encryption (encoding) at the UE may start after sending the AS security mode completion message. RRC downlink decryption (decryption) at the UE can be initiated after the AS SMC message has been successfully received and verified. The RRC connection reconfiguration procedure used to add a DRB can only be performed after RRC security has been activated as part of the AS SMC procedure.

[0191] The UE may support integrity protection DRB. If the integrity check fails (e.g., a defective or missing message authentication code for integrity (MAC-I)), the associated packet data unit (PDU) may be discarded by the receiving PDCP entity. Key reloading is performed by the base station (K gNB / K eNB ), K RRC-enc , K RRC-int , K UP-enc , and K UP-intIt may be possible for the key, and if the PDCP COUNT is the same radio bearer identity and the same K gNB is to be reused, it may be initiated by the base station. Key re - keying may be possible for the keys of the base station (K gNB / K eNB ), K RRC-enc , K RRC-int , K UP-enc , and K UP-int , and it may be initiated by a core network entity (e.g., AMF / MME) when a different AS security context than the currently active one can be activated.

[0192] When the UE transitions from the RRC idle state to the RRC connected state, RRC protection keys and UP protection keys may be generated, but the NAS protection keys and upper - layer keys are assumed to be already available. These upper - layer keys may be established as a result of authentication and key agreement (AKA) activation or as a result of transfer from another AMF during handover or idle - mode mobility. When the UE transitions from the RRC connected state to the RRC idle state, the base station may delete the keys stored for that UE so that it only needs to maintain the state information of the idle - mode UE for the core network entity (e.g., AMF / MME). The base station may no longer need to store the state information regarding the corresponding UE and may delete the current keys from memory (e.g., when transitioning the RRC connected state to the RRC idle state), and the base station and the UE may delete NH, the base station's keys, KgNB, KRRCint, KRRCenc, KUPint, and KUPenc, and the associated NCC. The core network entity (e.g., AMF / MME) and the UE may continue to store the keys of the core network entity (e.g., KAMF / KMME), KNASint, and KNASenc.

[0193] In mobility with vertical key derivation, the NH may be further coupled to the target physical cell identifier (PCI) and its frequency absolute radio frequency channel number downlink (ARFCN-DL) before being used as the key for the base station within the target base station. In mobility with horizontal key derivation, the base station's currently active key may be further coupled to the target PCI (the PCI of the target cell) and its frequency ARFCN-DL before being used as the key for the base station within the target gNB. In either case, the ARFCN-DL can be the absolute frequency of the SSB of the target primary cell (PCell). It may not be necessary to change the AS security algorithm during a gNB-to-central unit (CU) handover. If the UE does not receive an indication of a new AS security algorithm during a gNB-to-CU handover, the UE may continue to use the same algorithm as before the handover.

[0194] AS security may include integrity protection and encryption of RRC signaling (SRB) and user data (DRB). The AS may apply four different security keys: one for RRC signaling (KRRCint) integrity protection, one for RRC signaling (KRRCenc) encryption, one for user data (KUPint) integrity protection, and one for user data (KUPenc) encryption. The four AS keys may be derived from the base station (e.g., KgNB / KgNB) key. The base station key may be based on the key of a core network entity (KAMF / KMME) that can be processed by a higher layer (e.g., the NAS layer). Integrity protection and encryption algorithms may be modified by synchronous reconfiguration (e.g., handover command). The AS keys (KgNB, KRRCint, KRRCenc, KUPint, and KUPenc) may be modified during synchronous reconfiguration, as well as during connection re-establishment and connection reactivation. For each wireless bearer, an independent counter (count) may be maintained for each direction. For each wireless bearer, the count may be used as input for encryption and integrity protection.

[0195] Paging may enable base stations to reach UEs in RRC idle and RRC inactive states via paging messages, and may enable notifying UEs in RRC idle, RRC inactive, and RRC connection states of system information changes of Earthquake and Tsunami Warning System (ETWS) or Commercial Mobile Warning Service (CMAS) indications via short messages. Both paging messages and short messages may be addressed by P-RNTI on PDCCH. Paging messages may be transmitted on PCCH, and short messages may be transmitted directly via PDCCH.

[0196] While a UE is in an RRC idle state, it may monitor the paging channel for core network (CN) initiation paging. While a UE is in an RRC inactive state, it may monitor the paging channel for RAN initiation paging. A UE may not need to continuously monitor the paging channel. Paging DRX is defined when a UE in an RRC idle or RRC inactive state may only need to monitor the paging channel during one paging opportunity (PO) per DRX cycle. Paging DRX cycles may be configured by the network (e.g., base station or core network entity (e.g., AMF / MME)), for CN initiation paging, the default cycle may be broadcast in system information, for CN initiation paging, the UE-specific cycle may be configured via NAS signaling, for RAN initiation paging, the UE-specific cycle may be configured via RRC signaling, and the UE may use the shortest applicable DRX cycle. For example, a UE in an RRC idle state may use the shortest of the first two cycles described above. The UE within RRC_INACTIVE can use the shortest of the three cycles mentioned above.

[0197] The UE's PO for CN-start paging and RAN-start paging may be based on the same UE identity (ID), resulting in overlapping POs. The number of different POs within a DRX cycle may be configurable via system information, and the network may distribute UEs to those POs based on their IDs.

[0198] When RRC_CONNECTED, a UE may monitor paging channels within any PO that are signaled with system information for SI change indication and PWS notification. A UE in the RRC connected state may only monitor paging channels on active BWPs where a common search space is configured. To operate with shared spectral channel access, a UE may be configured for an additional number of PDCCH monitoring opportunities within its PO to monitor paging. If a UE detects a PDCCH transmission within a PO of a UE addressed by P-RNTI, the UE may not need to monitor subsequent PDCCH monitoring opportunities within that PO.

[0199] A network (e.g., a base station) may initiate a paging procedure by sending a paging message at a UE's paging opportunity. The network may address multiple UEs in a paging message by including one paging record for each UE. A paging message may include a paging record list. A paging record list may contain one or more paging records. Each paging record may include at least one of the following: UE identity (ID) and access type. The UE identity may include S-TMSI or I-RNTI (Restart Identity). The access type may indicate whether the paging message originated from a PDU session from non-3GPP® access.

[0200] Cell selection may be required during transitions from Registration Management (RM)-DEREGISTERED to RM-REGISTERED, from CM-IDLE to CM-CONNECTED, and from CM-CONNECTED to CM-IDLE. In RM-DEREGISTERED, the UE does not need to be registered with the network. The UE context within the core network entity (e.g., AMF / MME) cannot hold valid location or routing information for the UE. The UE may not be reachable by the AMF. In the RM-REGISTERED state, the UE can be registered with the network. In the RM-REGISTERED state, the UE can receive services that require registration with the network. A UE in the CM idle state does not need to have an established NAS signaling connection with the core network entity (e.g., AMF / MME) (e.g., via the N1 / S1 interface). The UE can perform cell selection / cell reselection and PLMN selection. A UE in the CM-CONNECTED state may have NAS signaling connectivity with core network entities (e.g., via the N1 / S1 interface). NAS signaling connectivity may use RRC connectivity between the UE and base stations (e.g., RAN), and Next Generation Application Protocol (NGAP) / S1AP UE associations between access networks (ANs) (e.g., the AN of the base station) and core network entities (e.g., AMF / MME).

[0201] Cell selection may be based on the following principles: The UE NAS layer can identify the selected PLMN and equivalent PLMNs. Cell selection may be based on cells (CD-SSB) that define SSBs located on the synchronization raster. The UE may search the frequency (NR) band and, for each carrier frequency, can identify the strongest cell according to the CD-SSB. Next, the UE can read the cell system information broadcast and identify its PLMN. The UE can search each carrier sequentially ("initial cell selection") or use stored information to shorten the search ("stored information cell selection"). The UE may attempt to identify a suitable cell if it cannot identify a suitable cell from which it is attempting to identify an acceptable cell. If a suitable cell is found, or if only acceptable cells are found, the UE may camp on that cell and initiate the cell reselection procedure. A preferred cell is one in which the measured cell attribute meets the cell selection criteria, the cell PLMN is a selected PLMN, registered or equivalent PLMN, the cell is not prohibited or reserved, and the cell is not part of a tracking area on the list of "Roaming Prohibited Tracking Areas". An acceptable cell is one in which the measured cell attribute meets the cell selection criteria and the cell is not prohibited.

[0202] When transitioning from an RRC connected state or an RRC inactive state to an RRC idle state, the UE may camp on a cell as a result of cell selection according to the frequency assigned by the RRC in the state transition message. The UE may attempt to find a suitable cell using the stored information or the method described above for initial cell selection. If no suitable cell is found for any frequency or RAT, the UE may attempt to find an acceptable cell. In multibeam operation, cell quality may be derived between beams corresponding to the same cell.

[0203] During RRC idle, a UE may perform cell reselection. The principles of the procedure are as follows: Cell reselection may be based on CD-SSBs located on a synchronous raster. The UE may enable the reselection process by measuring the attributes of the serving cell and adjacent cells. The carrier frequency must be indicated for the search and measurement of inter-frequency adjacent cells. Cell reselection may identify the cells that the UE should camp on. Cell reselection may be based on cell reselection criteria involving measurements of serving and adjacent cells. Intra-frequency reselection is based on cell ranking. Inter-frequency reselection is based on absolute priority, with the UE attempting to camp the highest priority frequency available. An adjacent cell list (NCL) may be provided by the serving cell to handle specific cases for intra-frequency and inter-frequency adjacent cells. A blacklist may be provided to prevent the UE from reselecting specific intra-frequency and inter-frequency adjacent cells. A whitelist may be provided to request the UE to reselect only specific intra-frequency and inter-frequency adjacent cells. Cell reselection may be speed-dependent and may be service-specific prioritization. In multi-beam operation, cell quality can be derived from the beams corresponding to the same cell.

[0204] The UE can perform one of two procedures, initial cell selection and cell selection, by utilizing stored information. If the UE does not have stored cell information for the selected PLMN, the UE may perform initial cell selection. Otherwise, the UE may perform cell selection by utilizing stored information. For initial cell selection, the UE may, according to its capabilities, scan all RF channels within the (NR) frequency band to find a suitable cell. Based on the scan results, the UE may search for the strongest cell at each frequency. The UE may select the cell that is the suitable cell. For cell selection by utilizing stored information, the UE may request stored frequency information and, optionally, information about previously received measurement control information elements or cell parameters from previously detected cells. Based on the stored information, the UE searches for a suitable cell, and if the UE finds a suitable cell, it may select it. If the UE does not find a suitable cell, the UE may perform initial cell selection.

[0205] A base station may configure cell selection criteria for cell selection. A UE may attempt to identify a cell suitable for cell selection. A suitable cell is one that meets the following conditions: (1) the cell attributes being measured meet the cell selection criteria, (2) the cell PLMN is a selected PLMN, registered, or equivalent PLMN, (3) the cell is not prohibited or reserved, and (4) the cell is not part of a tracking area on the list of "Prohibited Tracking Areas for Roaming". The RRC layer within the UE may notify the NAS layer within the UE of cell selection and re-selection results based on changes in received system information related to the NAS. For example, cell selection and re-selection results may include cell identity, tracking area code, and PLMN identity.

[0206] The UE-RRC layer may initiate an RRC connection establishment procedure, an RRC connection reactivation procedure, or an RRC connection re-establishment procedure. Based on the initiation of an RRC connection establishment procedure or an RRC connection reactivation procedure, the UE may perform one or more steps, where one or more steps include: performing a unified access control procedure (e.g., an access deny check) for access attempts to the RRC establishment / reactivation procedure in the serving cell; applying default configuration parameters and configurations / parameters provided by SIB1 (e.g., applying default configuration and configurations / parameters provided by SIB1 based on whether an access attempt is permitted); sending a random access preamble to the serving cell (e.g., based on whether an access attempt is permitted); and sending an RRC request message to the serving cell. The procedure includes at least one of the following: sending an RRC request message to serving cell 0 based on trusting (for example, determining that the receipt of a random access response was successful); starting a timer based on the sending of the RRC request message; receiving an RRC response message or an RRC rejection message from the serving cell (for example, in response to the RRC request message); or sending an RRC completion message (for example, sending an RRC completion message in response to receiving an RRC response message). For the RRC connection re-establishment procedure, the UE for access attempts of the RRC re-establishment procedure does not have to perform a unified access procedure (for example, an access deny check).

[0207] Base stations (e.g., NG-RAN) may support overload and access control functions such as RACH backoff, RRC connection denial, RRC connection release, and UE-based access prohibition mechanisms. A unified access control framework applies to all UE states (e.g., RRC idle state, inactive state, and connected state). Base stations may broadcast prohibition control information associated with access categories and access identities (for network shares, prohibition control information may be configured individually for each PLMN). UEs may determine whether an access attempt is authorized based on the prohibited information broadcast to the selected PLMN, the selected access category, and the access identity for the access attempt. For NAS trigger requests, the UE-NAS layer may determine the access category and access identity. For AS trigger requests, the UE-RRC layer determines the access category, while the NAS determines the access identity. The base station will process access attempts with established causes "Emergency," "MPS Priority Access," and "MCS Priority Access" (i.e., Emergency Call, MPS, MCS Subscriber) with high priority, and will only respond to these access attempts with RRC rejection under extreme network load conditions that could threaten the stability of the base station.

[0208] Based on the initiation of the RRC connection establishment procedure or the RRC connection resumption procedure, an RRC inactive or idle UE may perform or initiate an access deny check (or Unified Access Control procedure) for access attempts in the RRC connection establishment procedure or the RRC connection resumption procedure. Based on the performance or initiation of the access deny check, the UE may determine the access category and access identity for the access attempt. The UE may determine that the access attempt is denied based on at least one of the following: timer T309 is activated for the access category for the access attempt, timer T302 is activated, and the access category is neither "2" nor "0". The UE may determine that the access attempt is permitted based on at least one of the following: the access category is "0", and a system information block (system information block type 25) containing Unified Access Control (UAC) deny parameters is not broadcast by the serving cell. The UE can determine whether an access attempt is prohibited based on at least one of the following: the cause of establishment (e.g., an access attempt) is not urgent; access prohibition per RSRP parameter in a system information block that includes (or is set to) threshold 0; and, if the wireless device is in extended coverage, access prohibition per RSRP parameter in a system information block that includes (or is set to) threshold 1 and the measured RSRP is less than the first entry in the RSRP threshold PRACH information list; access prohibition per RSRP parameter in a system information block that includes (or is set to) threshold 2 and the measured RSRP is less than the second entry in the RSRP threshold PRACH information list; and access prohibition per RSRP parameter in a system information block that includes (or is set to) threshold 3 and the measured RSRP is less than the third entry in the RSRP threshold PRACH information list.

[0209] The UE may determine that an access attempt is permitted based on the fact that its system information block does not contain UAC prohibit parameters for the access attempt. For example, the UE may determine that an access attempt is permitted based on the fact that its system information block does not contain UAC prohibit parameters for a PLMN selected by the UE and UAC prohibit parameters for common. The UE may determine that an access attempt is permitted based on UAC prohibit parameters for common that do not contain the access category of the access attempt. UAC prohibit parameters may include at least one of the following: UAC prohibit parameters for each PLMN, and UAC prohibit parameters for common. The UE may perform an access prohibition check against the access category of the access attempt based on the UAC prohibit parameters in the system information block. The UE may determine that an access attempt is permitted based on the fact that at least one corresponding bit of the access identity in the UAC prohibit parameter is zero. The UE may draw a first random number uniformly distributed within a range of 0 or greater and less than 1.

[0210] The UE may determine that an access attempt is permitted based on whether a first random number is lower than the UAC prohibition coefficient of the UAC prohibition parameter. The UE may determine that an access attempt is prohibited based on whether a first random number is greater than the UAC prohibition coefficient of the UAC prohibition parameter. In response to determining that an access attempt is prohibited, the UE may draw a second random number uniformly distributed within the range of 0 or greater and less than 1. Based on the second random number, the UE may start the prohibition timer T309 for the access category. When the prohibition timer T309 is activated, access attempts associated with the access category are prohibited (e.g., transmission is not permitted). Based on the expiration of the prohibition timer T309, the UE may consider mitigating the prohibition for the access category. Based on the mitigation of the prohibition for the access category, the UE may perform an access prohibition check for the access category if the UE has an access attempt for the access category.

[0211] Based on the initiation of the RRC connection re-establishment procedure, the UE may deactivate one or more prohibit timers T309 for all access categories if one or more prohibit timers T309 are activated. Based on deactivating one or more prohibit timers T309, the UE may determine to prohibit relaxation of all access categories. Based on prohibiting relaxation of all access categories, the UE may perform the RRC connection re-establishment procedure. For example, based on prohibiting relaxation of all access categories, the UE may send an RRC establishment request without prohibition.

[0212] To initiate the RRC connection establishment / restart / re-establishment procedure, the UE-RRC layer may use parameters in the received SIB1. The UE-RRC layer may use L1 parameter values ​​and time alignment timers in the SIB1. The UE-RRC layer may use the UAC prohibition information in the SIB1 to implement unified access control procedures. Based on the unified access control procedures, the UE-RRC layer may determine whether access attempts for those RRC procedures are prohibited or permitted. Based on determining that access attempts are permitted, the UE-RRC layer may determine to send an RRC request message to the base station, which may be an RRC setup request message, an RRC restart request message, or an RRC re-establishment message. The UE-NAS layer may or may not provide the S-TMSI as the UE identity. The UE-RRC layer may set the UE identity in the RRC request message.

[0213] For an RRC setup request message, an RRC idle UE may initiate the RRC connection establishment procedure. Based on the initiation of the RRC connection establishment procedure, the RRC idle UE-RRC layer may set the UE identity to the S-TMSI if the UE-NAS layer provides the S-TMSI. Otherwise, the RRC idle UE-RRC layer may draw a 39-bit random value and set the UE identity to the random value. For an RRC restart request message, an RRC inactive or idle UE-RRC layer may set the UE identity to the restart identity that is stored. For an RRC re-establishment request message, an RRC connected UE-RRC layer may set the UE identity to the C-RNTI used by the source PCell. The UE-NAS layer may provide the establishment cause (e.g., UE-NAS layer). The UE-RRC layer sets the establishment cause for the RRC request message.

[0214] In an RRC restart request message, a UE in an RRC inactive state may initiate the RRC connection restart procedure. A UE of an RRC with a suspended RRC connection may initiate the RRC connection restart procedure. A UE may be in an RRC inactive or RRC idle state and may initiate the RRC connection procedure based on at least one of restarting (suspending) an RRC connection and performing / starting an UP small data transmission. Based on the initiation of the RRC connection restart procedure, the UE-RRC layer may recover stored configuration parameters and stored security keys from the stored UE inactive AS context. Based on the security key / parameter, the RRC inactive or idle UE-RRC layer may set a restart MAC-I value in the least significant 16 bits of a MAC-I calculated based on a variable restart MAC input, the security key for integrity protection to the RRC layer in the UE inactive AS context, a previously configured integrity protection algorithm, and other security parameters (e.g., count, bearer, and direction). The variable restart MAC input may include at least one of the following: the physical cell identity of the source cell, the C-RNTI of the source cell, and the cell identity of the target cell (e.g., the selected cell), where the cell identity is the cell identity in the system information block (e.g., SIB1) of the target cell (e.g., the selected cell). Based on the security key and the next hop chain count (NCC) value, the RRC inactive or idle UE-RRC layer configures the lower layer (e.g., the UE-PDCP layer) to derive and apply new security keys for integrity protection and encryption. The UE may have stored NCC values ​​and restart identities. The UE may receive an RRC release message with a pause indicator (or pause configuration parameter), where the RRC release message includes at least one of the restart identity and NCC values. The RRC inactive or idle UE-RRC layer may re-establish PDCP entities for one or more bearers. The UE-RRC layer may restart one or more bearers.For example, based on the resumption of RRC connectivity, the UE-RRC layer may reactivate SRB1. Based on the execution of UP small data transmission, the UE-RRC layer may reactivate one or more SRBs and DRBs. A UE-RRC layer that is RRC inactive or idle may send an RRC reactivation request message to a base station, which may include at least one of a reactivation identity, a reactivation MAC-I, and a reactivation cause.

[0215] In response to an RRC re-establishment request message, a UE in the RRC connection state may initiate the RRC connection re-establishment procedure. Based on the initiation of the RRC connection re-establishment procedure, the UE-RRC layer in the RRC connection state may include the source PCell's physical cell identity and short MAC-I in the RRC re-establishment message. The UE-RRC layer in the RRC connection state may set the short MAC-I in the 16 least significant bits of the MAC-I calculated based on a variable short MAC input, the integrity protection security key for the RRC layer, the integrity protection algorithm used in the source PCell or PCell that triggered the re-establishment, and other security parameters (e.g., count, bearer, and direction). The variable short MAC input may include at least one of the following: the source cell's physical cell identity, the source cell's C-RNTI, and the target cell's (e.g., selected cell's) cell identity, where the cell identity is the cell identity in the system information block (e.g., SIB1) of the target cell (e.g., selected cell). A UE-RRC layer in RRC connectivity state can re-establish the PDCP and RLC entities of SRB1 and apply the default SRB1 configuration parameters. The UE-RRC layer in RRC connectivity state can also configure lower layers (e.g., the PDCP layer) to suspend and then resume SRB1's integrity protection and encryption.

[0216] The UE-RRC layer may send an RRC request message to a lower layer (e.g., the PDCP layer, RLC layer, MAC layer, and / or PHY layer) for transmission, the RRC request message may be an RRC setup request message, an RRC restart request message, or an RRC re-establishment message.

[0217] The UE-RRC layer may receive an RRC setup message in response to an RRC restart request message or an RRC re-establishment request message. Based on the RRC setup message, the UE-RRC layer may discard the stored AS context, pause configuration parameters, and current AS security context. The UE-RRC layer may release radio resources to all established RBs except SRB0, including RLC entities, associated PDCP entities, and SDAP releases. The UE-RRC layer may release RRC configurations except default L1 parameter values, default MAC cell group configurations, and CCCH configurations. The UE-RRC layer may indicate fallbacks for RRC connections to upper layers (e.g., the NAS layer). If timer T380 is activated as a periodic RAN-based notification area (RNA) update timer, the UE-RRC layer may stop timer T380.

[0218] The UE-RRC layer may receive an RRC setup message in response to an RRC setup request message, an RRC restart request message, or an RRC re-establishment request message. The RRC setup message may include cell group configuration parameters and radio bearer configuration parameters. The radio bearer configuration parameters may include at least one of the following: signaling bearer configuration parameters, data radio bearer configuration parameters, and / or security configuration parameters. The security configuration parameters may include security algorithm configuration parameters and keys, and may use an indicator to show whether the radio bearer configuration parameter is using a master key or a secondary key. The signaling radio bearer configuration parameters may include one or more signaling radio bearer configuration parameters. Each signaling radio configuration parameter may include at least one of the following: SRB identity, PDCP configuration parameters, re-establishment PDCP indicator, and / or discard PDCP indicator. The data radio bearer configuration parameters may include one or more data radio bearer configuration parameters. Each data radio configuration parameter may include at least one of the following: DRB identity, PDCP configuration parameter, SDAP configuration parameter, re-establish PDCP indicator, and / or recover PDCP indicator. The radio bearer configuration in the RRC setup message may include the signaling radio configuration parameter of SIB1. Based on the RRC setup message, the UE-RRC layer may establish SRB1. Based on the RRC setup message, the UE-RRC layer may perform cell group configuration or radio bearer configuration. The UE-RRC layer may stop the prohibit timer and standby timer for the cell that sends the RRC setup message. Based on the receipt of the RRC setup message, the UE-RRC layer may perform one or more of the following: transition to the RRC connection state, stop the cell reselection procedure, consider the current cell that sent the RRC setup message to be a PCell, or / or send an RRC setup complete message by setting the contents of the RRC setup complete message.

[0219] The UE-RRC layer may receive an RRC restart message in response to an RRC restart request message. Based on the RRC restart message, the UE-RRC layer may discard the UE inactive AS context and release the paused configuration parameters, excluding the RNA notification area information. The RRC restart message may include at least one of the following: radio bearer configuration parameters, cell group configuration parameters, measurement configuration parameters, sk counter for AS security, a first indication for requesting idle / inactive measurement results, a second indication for restoring secondary cells (SCells) of a master cell group (MCG), a third indication for restoring a secondary cell group (SCG), and SCG configuration parameters. Based on the RRC restart message, the UE-RRC layer may perform procedures to configure or restore configuration parameters (e.g., cell group configuration, radio bearer configuration, and / or SCG configuration), security key update procedures, and / or measurement (configuration) procedures. Based on the receipt of the RRC restart message, the UE-RRC layer may perform one or more of the following actions: indicate to the upper layer (e.g., the NAS layer) that the suspended RRC connection has been restarted; restart SRB2, all DRBs and measurements; enter the RRC connection state; stop the cell reselection procedure; consider the current cell sending the RRC restart message to be a PCell; and / or send an RRC restart complete message by setting the content of the RRC restart complete message.

[0220] Cell group configuration parameters can be used to configure a master cell group (MCG) or a secondary cell group (SCG). When configuring an MCG using cell group configuration parameters, the cell group configuration parameters are master cell group configuration parameters. When configuring an SCG using cell group configuration parameters, the cell group configuration parameters are secondary cell group configuration parameters. A cell group includes one MAC entity, a set of logical channels with associated RLC entities, and a set of primary cells (SpCells) and one or more secondary cells (SCells). Cell group configuration parameters (e.g., master cell group configuration parameters or secondary cell group configuration parameters) may include at least one of the following: RLC bearer configuration parameters for a cell group, MAC cell group configuration parameters for a cell group, physical cell group configuration parameters for a cell group, SpCell configuration parameters for a cell group, or SCell configuration parameters for a cell group. MAC cell group configuration parameters may include MAC parameters for a cell group, and MAC parameters may include at least DRX parameters. Physical cell group configuration parameters may include cell group-specific L1 (layer 1) parameters.

[0221] A special cell (SpCell) may include a primary cell (PCell) for MCG or a primary SCG cell (PSCell) for SCG. SpCell configuration parameters may include the serving cell-specific MAC and PHY parameters for the SpCell. MR-DC configuration parameters may include at least one of the following: SRB3 configuration parameters, measurement configuration parameters for SCG, and SCG configuration parameters.

[0222] The cell group configuration parameters may include at least one of the following: RLC bearer configuration parameters, MAC cell group configuration parameters, physical cell group configuration parameters, SpCell configuration parameters for the first cell group, or SCell configuration parameters for other cells of the second base station. The SpCell configuration parameters may include at least one of the following: radio link failure timers and constraints, out-of-sync radio link monitoring thresholds, and / or serving cell configuration parameters for the first cell. The serving cell configuration parameters may include at least one of the following: downlink BWP configuration parameters, uplink configuration parameters, uplink configuration parameters for complementary uplink carriers (SULs), PDCCH parameters applicable to all BWPs of the serving cell, PDSCH parameters applicable to all BWPs of the serving cell, CSI measurement configuration parameters, SCell deactivation timer, serving cell cross-carrier scheduling configuration parameters, serving cell timing advance group (TAG) identity (ID), path loss criterion link indicating whether the UE applies either a SpCell or a SCell downlink as the path loss criterion for this uplink, serving cell measurement configuration parameters, and channel access configuration parameters for access procedures for operation using shared spectral channel access.

[0223] The CSI measurement configuration parameters may be for configuring the CSI-RS (reference signal) belonging to the serving cell, the channel status information report that constitutes the CSI-RS (reference signal) belonging to the serving cell, and the channel status information report related to PUSCH triggered by DCI received on the serving cell.

[0224] In the embodiment, downlink BWP configuration parameters may be used to configure dedicated (UE-specific) parameters for one or more downlink BWPs. One or more downlink BWPs may include at least one of the initial downlink BWP, default downlink BWP, and first active downlink BWP. Downlink BWP configuration parameters may include at least one of the following: configuration parameters for one or more downlink BWPs, one or more downlink BWP IDs for one or more downlink BWPs, and BWP inactive timers. Downlink BWP configuration parameters may include at least one of the following: PDCCH configuration parameters for downlink BWPs, PDSCH configuration parameters for downlink BWPs, semi-persistent scheduling (SPS) configuration parameters for downlink BWPs, beam failure recovery SCell configuration parameters for candidate RSs, and / or radio link monitoring configuration parameters for detecting cell and beam radio link failure opportunities for downlink BWPs. One or more downlink BWPs The ID may include at least one of the following: the initial downlink BWP ID, the default downlink BWP identity (ID), and the first active downlink BWP ID.

[0225] In the embodiment, the uplink configuration parameters may be uplink configuration parameters for a normal uplink carrier (a non-complementary uplink carrier). The uplink configuration parameters (or the uplink configuration parameters of the SUL) may be used to configure dedicated (UE-specific) parameters for one or more uplink BWPs. One or more uplink BWPs may include at least one of the initial uplink BWP and the first active uplink BWP. The uplink BWP configuration parameters may include at least one of the following: configuration parameters for one or more uplink BWPs, one or more uplink BWP IDs for one or more uplink BWPs, PUSCH parameters common across the BWPs of the UE in the serving cell, SRS carrier switching information, and power control configuration parameters. The configuration parameters for an uplink BWP may include at least one of the following: one or more PUCCH configuration parameters for the uplink BWP, a PUSCH configuration parameter for the uplink BWP, one or more configured uplink permission configuration parameters for the uplink BWP, an SRS configuration parameter for the uplink BWP, a beam failure recovery configuration parameter for the uplink BWP, and / or a cyclic prefix (CP) extension parameter for the uplink BWP.

[0226] One or more uplink BWP IDs may include at least one of the initial uplink BWP ID (e.g., initial uplink BWP ID=0) and / or the first active uplink BWP ID. SRS carrier switching information may be used for SRS power control that is independent of PUSCH and configured for SRS carrier switching when PUSCH is not configured. Power control configuration parameters may include at least one of the power control configuration parameters for PUSCH, power configuration control parameters for PUCCH, and power control parameters for SRS.

[0227] A UE-RRC layer that is RRC inactive or idle may receive an RRC rejection message in response to an RRC setup request message or an RRC restart request message. The RRC rejection message may include a standby timer. Based on the standby timer, the UE-RRC layer may start timer T302 by setting the timer value to the standby timer. Based on the RRC rejection message, the UE-RRC layer may notify the upper layer (e.g., the UE-NAS layer) of the failure to set up or restart the RRC connection. The UE-RRC layer may reset the MAC and release the default MAC cell group configuration. Based on the RRC rejection received in response to a request from the upper layer, the UE-RRC layer may inform the upper layer (e.g., the NAS layer) that the access ban is applicable to all access categories except categories "0" and "2".

[0228] A UE-RRC layer that is RRC inactive or idle may receive an RRC rejection message in response to an RRC resume request message. Based on the RRC rejection message, the UE-RRC layer discards the current security key. The UE-RRC layer may suspend the RRC connection again. If the resumption is triggered by an RNA update, the UE-RRC layer may set the pending RNA update value to true.

[0229] A UE-RRC layer that is RRC inactive or idle can perform a cell (re)selection procedure while performing an RRC procedure to establish an RRC connection. Based on cell selection or cell reselection, the UE-RRC layer can change cells on a camped UE and stop the RRC procedure. The UE-RRC layer may notify the upper layer (e.g., the NAS layer) of the failure of the RRC procedure.

[0230] A UE in an RRC connection state can detect a failure to connect to the base station. A UE in an RRC connection state may activate AS security at the base station before detecting a failure. Failures include at least one of the following: radio link failure (RLF), reconfiguration with synchronization failure, mobility failure from a new radio (NR), integrity check failure indication from a lower layer (e.g., PDCP layer) relating to signaling radio bearer 1 (SRB1) or signaling radio bearer 2 (SRB2), or RRC connection reconfiguration failure.

[0231] A radio link failure may be a radio link failure of the base station's primary cell. The base station may send a reconfiguration with synchronization in an RRC message to a UE in RRC connectivity state. Reconfiguration with synchronization may include a reconfiguration timer (e.g., T304). Based on the receipt of the reconfiguration synchronization, the UE may activate the reconfiguration timer and perform a reconfiguration with synchronization (e.g., handover). Based on the expiration of the reconfiguration timer, the UE determines that the reconfiguration synchronization has failed. The base station may send mobility from an NR command message to a UE in RRC connectivity state. Based on the receipt of mobility from an NR command message, the UE may perform a handover from the NR to the cell using another RAT (e.g., E-UTRA). The UE can determine that mobility from an NR has failed if at least one of the following conditions is met: the UE is unable to establish a connection to the target radio access technology, or the UE is unable to comply with any part of the configuration included in mobility from an NR command message, or there is a protocol error in the inter-RAT information included in mobility from an NR message.

[0232] Based on the detection of a failure, the UE in the RRC connection state can initiate the RRC connection re-establishment procedure. Based on the initiation of the RRC connection re-establishment procedure, the UE can activate timer T311, stop all radio bearers except SRB0, and reset the MAC (layer). Based on the initiation of the RRC connection re-establishment procedure, the UE in the RRC connection state may release the MCG SCell and release special cell (SpCell) configuration parameters and multi-radio duplex (MR-DC) related configuration parameters. For example, based on the initiation of the RRC connection re-establishment procedure, the UE may release the master cell group configuration parameters.

[0233] Based on the initiation of the RRC connection re-establishment procedure, a UE in an RRC connection state may perform a cell selection procedure. Based on the cell selection procedure, the UE may select a cell based on whether the cell's signal quality exceeds a threshold. A UE in an RRC connection state may select a cell based on whether the cell's signal quality exceeds a threshold. Based on the cell selection procedure, the UE may determine which selected cells exceed the threshold. Signal quality includes at least one of the following: reference signal received power, received signal strength indicator, reference signal received quality, or signal-to-interference + noise ratio.

[0234] Based on the selection of a suitable cell, a UE in the RRC connected state can stop timer 311 and start timer T301. Based on the selection of a suitable cell, a UE in the RRC connected state can stop the prohibit timer T390 for all access categories. Based on the stopping of prohibit timer T390, a UE in the RRC connected state may consider the prohibition for all access categories to be relaxed for the cell. Based on the cell selection, a UE in the RRC connected state can apply default L1 parameter values, excluding the parameters provided in SIB1, apply the default MAC cell group configuration, apply the CCCH configuration, apply the timer alignment timer to SIB1, and start sending an RRC re-establishment request message.

[0235] A UE in the RRC connection state may stop timer T301 based on the receipt of an RRC response message, which is a response to an RRC re-establishment request message. The RRC response message may include at least one of the following: an RRC re-establishment message, an RRC setup message, or an RRC re-establishment rejection message. A UE in the RRC connection state may also stop timer T301 if the selected cell becomes unsuitable.

[0236] Based on the cell selection procedure triggered by initiating the RRC connection re-establishment procedure, a UE in the RRC connected state can select an inter-RAT cell. Based on the selection of the inter-RAT cell, the RRC connected UE (UE-AS layer) can transition to the RRC IDLE state and provide the release cause "RRC connection failure" to the upper layer of the UE (UE-NAS layer).

[0237] Based on the initiation of sending an RRC re-establishment request message, a UE in an RRC connection state may send an RRC re-establishment request message. The RRC re-establishment request message may include at least one of the following: the C-RNTI used by the source PCIe, the source PCIe's physical cell identity (PCI), the short MAC-I, or the re-establishment cause. The re-establishment cause may include at least one of the following: reconfiguration failure, handover failure, or other failure.

[0238] Based on the initiation of sending the RRC re-establishment request message, the RRC-connected UE (RRC layer) may re-establish the PDCP for SRB1, re-establish the RLC for SRB1, apply the default SRB configuration for SRB1, configure the lower layer (PDCP layer) to deactivate integrity protection and encryption for SRB1, restart SRB1, and send the RRC re-establishment request message to the lower layer (PDCP layer) for transmission. Based on sending the RRC re-establishment request message to the lower layer, the RRC-connected UE may send the RRC re-establishment request message to a target base station via a cell selected based on the cell selection procedure, the target base station may not be the source base station.

[0239] Based on the expiration of T311 or T301, the UE (UE-AS layer) may transition to an RRC idle state and provide the release cause "RRC connection failure" to the upper layer of the UE (UE-NAS layer).

[0240] Based on the receipt of the release cause "RRC connection failure," if the UE in the RRC idle state is not in signaling pending or user data pending, the UE (UE-NAS layer) can perform the NAS signaling connection recovery procedure. Based on the performance of the NAS signaling connection recovery procedure, the UE in the RRC idle state may initiate the registration procedure by sending a registration request message to the AMF.

[0241] Based on the receipt of the release cause "RRC connection failure," an RRC idle UE (UE-NAS layer) can perform a service request procedure by sending a service request message to the AMF when the UE is in signaling pending or user data pending.

[0242] Based on the receipt of the RRC re-establishment request message, the target base station may check whether the UE context of the UE is locally available. Based on the finding that the UE context is not locally available, the target base station may perform the UE context acquisition procedure by sending an UE context acquisition request message to the UE's source base station (the last serving base station).

[0243] In the RRC connection re-establishment procedure, the retrieved UE context request message may include at least one of the following: UE context ID, integrity protection parameters, or new cell identifier. The UE context ID may include at least one of the following: C-RNTI containing the RRC re-establishment request message, and PCI (last serving PCell) of the source PCell. The integrity protection parameter in the RRC re-establishment procedure may be a short MAC-I. The new cell identifier may be the identifier of the target cell, which is the cell on which the RRC connection is requested to be re-established. The new cell identifier is the cell identity in the system information block (e.g., SIB1) of the target cell (e.g., selected cell).

[0244] In the RRC connection re-establishment procedure, based on the receipt of the acquired UE context request message, the source base station can check the acquired UE context request message. If the source base station can identify the UE context by the UE context ID, successfully verify the UE with the integrity protection included in the acquired UE context request message, and determine that it can provide the UE context to the target base station, the source base station may respond to the target base station with an acquired UE context response message. If the source base station cannot identify the UE context by the UE context ID, or if the integrity protection included in the acquired UE context request message is not effective, the source base station may respond to the target base station with an acquired UE context failure message.

[0245] In the RRC connection re-establishment procedure, the UE context acquisition response message may include at least one of the following: the target base station's Xn Application Protocol (XnAP) ID, the source base station's XnAP ID, the Global Unique AMF Identifier (GUAMI), or UE context information (e.g., UE context information UE context acquisition response). The UE context information may include at least one of the following: NG-C UE-related signaling criteria, UE security capability, AS security information, UE aggregate maximum bitrate, PDU sessions set up in the list, RRC context, mobility constraint list, or RAT / mobility selection priority index. The NG-C UE-related signaling criteria may be the NG Application Protocol ID assigned in the UE's AMF on the NG-C connection with the source base station. The AS security information may be the base station (K gNBThe security key and next hop chain count (NCC) value may be included. The PDU session set up in the list may include PDU session resource-related information used in the source base station's UE context. The PDU session resource-related information may include the PDU session ID, PDU session resource aggregation maximum bitrate, security indicator, PDU session type, or QoS flow set up in the list. The security indicator may include user plane integrity indicators and confidentiality indicators, respectively, indicating the user plane (UP) integrity and encryption requirements for the corresponding PDU session. The security indicator may also include at least one of the following: an indicator of whether UP integrity protection applies to the PDU session, an indicator of whether UP encryption applies to the PDU session, and the maximum integrity data rate value per UE (uplink and downlink) for the integrity DRB. The PDU session type may indicate at least one of Internet Protocol version 4 (IPv4), IPv6, IPv4v6, Ethernet®, or unstructured. A QoS flow set up in the list may include at least one of the following: a QoS flow identifier, QoS flow level QoS parameters (QoS parameters applied to the QoS flow), or a bearer identity.

[0246] In the RRC connection re-establishment procedure, the UE context acquisition failure message may include at least the target base station's XnAP ID and a cause value.

[0247] In the RRC connection re-establishment procedure, based on the receipt of the UE context acquisition response message, the target base station may send an RRC re-establishment message to the UE. The RRC re-establishment message may include at least the network hop chain count (NCC) value.

[0248] Based on the receipt of the RRC re-establishment message, the UE will determine the current K associated with the NCC value. gNB Alternatively, based on at least one of the following hop (NH) parameters, base station (KgNB A new security key can be derived from the base station. Based on the new security key and the previously configured integrity protection algorithm, the UE can derive the RRC signaling (K RRCint Security key for protecting the integrity of ) and user plane (UP) data (K UPint ) can derive a security key for the integrity protection of the base station. Based on the new security key of the base station and the previously configured encryption algorithm, the UE can derive RRC signaling (K RRCenc Security key and user plane (UP) data (K) for encryption of ) UPenc A security key can be derived to encrypt ). K RRCint Based on the previously configured integrity protection algorithm, the UE may verify the integrity protection of the RRC re-establishment message. Based on the verification failure, the UE (UE-AS layer) may transition to the RRC IDLE state and provide the release cause "RRC connection failure" to the upper layer of the UE (UE-NAS layer). Based on the verification success, the UE may use the previously configured integrity protection algorithm and K RRCint Configure SRB1 to restart integrity protection based on the previously configured cryptographic algorithm and K RRCenc Based on this, SRB1 encryption may be configured to resume. The UE may send an RRC re-establishment complete message to the target base station.

[0249] Based on receiving a UE context acquisition failure message, the target base station may send an RRC release message to the UE. For example, based on a UE context acquisition failure message that includes an RRC release message, the target base station may send an RRC release message to the UE. Based on receiving a UE context acquisition failure message, the target base station may send an RRC setup message or an RRC rejection message. Based on receiving a UE context acquisition failure message, the target base station may not send a response message to the UE.

[0250] Figure 17 shows an example of the RRC connection re-establishment procedure. An UE in an RRC connection state may send and receive data to and from a first base station (e.g., a source base station) via a cell, the cell including the primary cell (PCell) of the first base station. The UE can detect a failure in connection with the first base station. Based on the failure, the UE may initiate the RRC re-establishment procedure.

[0251] In the embodiment shown in Figure 17, upon the start of the RRC connection re-establishment procedure, the UE may activate timer T311, suspend all radio bearers except SRB0, and / or reset the MAC(layer). Upon the start of the RRC connection re-establishment procedure, the UE may release the MCG SCell and release special cell (SpCell) configuration parameters and multi-radio duplex (MR-DC) related configuration parameters. Upon the start of the RRC connection re-establishment procedure, the UE may perform a cell selection procedure. Based on the cell selection procedure, the UE may select cell 2 of a second base station (e.g., a target base station), where cell 2 is a preferred cell. Based on the selection of a preferred cell, the UE may deactivate timer T311 and activate timer T301. Based on the selection of a preferred cell, the UE may deactivate one or more prohibit timers T309 for all access categories if one or more prohibit timers T309 are activated. Based on deactivating one or more prohibit timers T309, the UE may consider the prohibition for all access categories to be relaxed for the cell. Based on the cell selection, the UE can apply default L1 parameter values, excluding the parameters provided in SIB1, apply the default MAC cell group configuration, apply the CCCH configuration, apply the timer alignment timer to SIB1, and initiate sending of an RRC re-establishment request message.

[0252] In the embodiment shown in Figure 17, the RRC re-establishment message may include at least one of the following: C-RNTI used by the source PCIell (e.g., cell 1), the source PCIell's physical cell identity (PCI), a short MAC-I, or a re-establishment cause. Based on the initiation of sending the RRC re-establishment request message, the UE (RRC layer) may re-establish the PDCP of SRB1, re-establish the RLC of SRB1, apply the default SRB configuration of SRB1, configure the lower layer (PDCP layer) to suspend integrity protection and encryption of SRB1, restart SRB1, and send the RRC re-establishment request message to the lower layer (PDCP layer) for transmission. Based on the initiation of sending the RRC re-establishment request message, the UE may send the RRC re-establishment request message to a second base station via cell 2.

[0253] In the embodiment shown in Figure 17, based on the receipt of the RRC re-establishment request message, the second base station may check whether the UE context of the UE is locally available. Based on the finding that the UE context is not locally available, the second base station may perform the Retrieve UE Context procedure by sending a Retrieve UE Context Request message to the UE's source base station. The Retrieve UE Context Request message may include at least one of the following: a UE context ID, integrity protection parameters, or a new cell identifier. The UE context ID may include at least one of the C-RNTI containing the RRC re-establishment request message and the PCI (Last Serving PCell) of the source PCell. The integrity protection parameter of the RRC re-establishment procedure may be a short MAC-I. The new cell identifier may be the identifier of the target cell, which is the cell from which the RRC connection has been requested to be re-established. The new cell identifier is the cell identity in the System Information Block (e.g., SIB1) of the target cell (e.g., the selected cell).

[0254] In the embodiment shown in Figure 17, the source base station can check the acquired UE context request message based on its receipt. If the source base station successfully identifies the UE context by C-RNTI, successfully verifies the UE by short MAC-I, and determines that it can provide the UE context to the second base station, the source base station may respond to the second base station with an acquired UE context response message. The acquired UE context response message may include at least GUAMI or UE context information. Based on the receipt of the acquired UE context response message, the second base station may send an RRC re-establishment message to the UE. The RRC re-establishment message may include a network hop chain count (NCC) value.

[0255] In the embodiment shown in Figure 17, based on the receipt of the RRC re-establishment message, the UE receives the current K associated with the NCC value. gNB Alternatively, based on at least one of the following hop (NH) parameters, base station (K gNB A new security key can be derived from the base station (K). gNB Based on the new security key and previously configured security algorithm, the UE will perform RRC signaling (e.g., K, respectively). RRCint , and K RRCenc ), and user plane (UP) data (for example, K UPint , and K UPenc ) can be used to derive security keys for integrity protection and encryption. RRC signaling (K RRCint Based on the security key for integrity protection of the RRC re-establishment message, the UE may verify the integrity protection of the RRC re-establishment message. Based on the success of the verification, the UE may configure the previously configured integrity protection algorithm and K RRCint Based on this, configure to reinstate integrity protection for one or more bearers (e.g., signaling radio bearers or RRC messages), and configure previously configured cryptographic algorithms and K RRCenc Based on this, it may be configured to resume encryption for one or more bearers.

[0256] In the embodiment shown in Figure 17, the second base station may transmit a first RRC reconfiguration message. The first RRC reconfiguration message may include SpCell configuration parameters. Based on the receipt of the SpCell configuration parameters, the UE may initiate data transmission and reception with the second base station. The UE may transmit an RRC re-establishment complete message to the second base station. The RRC re-establishment complete message may include a measurement report. Based on the receipt of the measurement report, the second base station may determine to configure an SCell and / or a secondary cell group (e.g., an SCG or PSCell). Based on the determination, the second base station may transmit a second RRC reconfiguration message including SCell configuration parameters and / or MR-DC related configuration parameters. Based on the receipt of the second RRC reconfiguration message, the UE may transmit and receive data via the SCell and / or SCG.

[0257] In the embodiment shown in Figure 17, the RRC reconfiguration message may include at least one of the following: MCG and / or SCG cell group configuration parameters, radio bearer configuration parameters, or AS security key parameters.

[0258] The base station may initiate an RRC connection release procedure to transition the UE's RRC state from RRC connected state to RRC idle state, from RRC connected state to RRC inactive state, from RRC inactive state to RRC inactive state when the UE attempts to resume, or from RRC inactive state to RRC idle state when the UE attempts to resume. The RRC connection procedure can also be used to release the UE's RRC connection and redirect the UE to a different frequency. The base station may send an RRC release message to the UE that includes pause configuration parameters. Based on the RRC release message, the UE may terminate the RRC connection. The UE may transition its RRC state to RRC inactive state or RRC idle state. The pause configuration parameters may include at least one of the following: resume identity, RNA configuration, RAN paging cycle, or network hop chain count (NCC) value, where the RNA configuration may include RNA notification area information or a periodic RNA update timer value (e.g., T380 value). The base station may use a restart identity (e.g., inactive-RNTI (I-RNTI)) to identify the UE context when the UE is in an RRC inactive state.

[0259] If a base station has a fresh, unused pair of {NCC, next hop (NH)}, the base station may include NCC in its pause configuration parameter. Otherwise, the base station will include the current K gNB The same NCC associated with it can be included in the pause configuration parameter. The NCC is used for AS security. After the base station sends an RRC release message containing the pause configuration parameter to the UE, the current AS key (e.g., K RRCenc , K UPenc ), and K UPint It can be deleted, but the current AS key K RRCint It may retain the following: If the transmitted NCC value is fresh and belongs to an unused {NCC, NH} pair, the base station will store the {NCC, NH} pair in the current UE AS security context and the current AS key K gNB It can be deleted. The submitted NCC value is the current KgNB If it is equal to the associated NCC value, the base station will use the current AS key K gNB The base station may also retain the NCC. The base station may remember the transmitted reactivation identity along with the current UE context, including the rest of the AS security context.

[0260] When the UE receives an RRC release message containing pause configuration parameters from the base station, it may verify the integrity of the received RRC release message containing the pause configuration parameters by checking the PDCP MAC-I. If this verification is successful, the UE retrieves the received NCC value and stores it as an NCC to be stored along with the current UE context. The UE then uses the current AS key K RRCenc , K UPenc , and K UPint It can be deleted, but the current AS key K RRCint The key can be held. The stored NCC value is the current K gNB If it differs from the associated NCC value, UE will use the current AS key K gNB It can be deleted. The stored NCC is the current K gNB If it is equal to the associated NCC value, the UE shall retain the current AS key KgNB. The UE may store the received reactivation identity, along with the current UE context, including the rest of the AS security context, for the next state transition.

[0261] Based on the receipt of an RRC release message containing pause configuration parameters, the UE may reset the MAC, release the default MAC cell group configuration, and re-establish the RLC entities for one or more bearers. Based on the receipt of an RRC release message containing pause configuration parameters, the UE may store the current configuration parameters and the current security key in the UE inactive AS context. For example, the UE may store some of the current configuration parameters. The current configuration parameters to be stored may include the Robust Header Compression (ROHC) state, the Quality of Service (QoS) flow to the DRB mapping rules, the C-RNTI used by the source PCell, the global cell identity and physical cell identity of the source PCell, and all other parameters configured except those in the reconfiguration with synchronization and the serving cell configuration common parameters of the SIB. The stored security key is K gNB and K RRCint It may include at least one of the following. The cell-specific parameters of a UE's serving cell in SIB1 can be configured using the serving cell configuration common parameters in the SIB. Based on the receipt of an RRC release message containing the pause configuration parameter, the UE may pause all SRBs and DRBs except SRB0. Based on the receipt of an RRC release message containing the pause configuration parameter, the UE may activate timer T380, enter an RRC inactive state, and perform the cell selection procedure.

[0262] A UE in an RRC inactive state may initiate the RRC connection restart procedure. For example, a UE in an RRC inactive state may initiate the RRC connection restart procedure based on having data or signaling to transmit or receiving a RAN paging message. Based on the initiation of the RRC connection restart procedure, the UE may select an access category based on the trigger conditions of the RRC connection restart procedure and implement a unified access control procedure based on the access category. Based on the unified access control procedure, the UE may consider the access attempt of the RRC connection restart procedure to be authorized. Based on considering the access attempt to be authorized, the UE may apply the default L1 parameter values ​​specified in the corresponding physical layer specification, except for parameters whose values ​​are provided to the SIB1, apply the default SRB1 configuration, apply the CCCH configuration, apply the common time alignment timer included in the SIB1, apply the default MAC cell group configuration, activate timer T319, and begin sending an RRC restart request message.

[0263] Based on the initiation of sending an RRC resume request message, the UE may set the context for the RRC resume request message. The RRC resume request message may include at least one of the following: resume identity, resume MAC-I, or resume cause. The resume cause may include at least one of the following: urgent, high priority access, mt access, mo signaling, mo data, mo voice call, mo sms, ran update, mps priority access, or mcs priority access.

[0264] Based on the initiation of the RRC restart request message, the UE may recover stored configuration parameters and stored security keys from the (stored) UE inactive AS context, with the exception of master cell group configuration parameters, MR-DC related configuration parameters (e.g., secondary cell group configuration parameters), and PDCP configuration parameters. Configuration parameters may include at least one of all other configured parameters, excluding the C-RNTI used by the source PCell, the source PCell's global cell identity and physical cell identity, and serving cell configuration common parameters in reconfigurations with synchronization and in SIBs. The current (recovered) K associated with the stored NCC value. gNB Alternatively, based on the next hop (NH) parameter, the UE will determine the base station (K gNB A new key can be derived from the base station. Based on the new key, the UE can derive a security key (e.g., K, respectively) for the integrity protection and encryption of RRC signaling. RRCenc and K RRCint ), and security keys (e.g., K, respectively) for protecting the integrity and encrypting user plane data. UPint and K UPenc ) can be derived. The constructed algorithm and K RRCint and K UPint Based on this, the UE may configure the lower layer (e.g., the PDCP layer) to apply integrity protection to all radio bearers except SRB0. The configured algorithm, and K RRCenc and K UPenc Based on this, the UE can configure a lower layer (e.g., the PDCP layer) to apply encryption to all radio bearers except SRB0.

[0265] Based on the initiation of sending an RRC restart request message, the UE may re-establish the PDCP entities of one or more bearers, restart one or more bearers, and send an RRC restart request message to a lower layer, which may include at least one of the PDCP layer, RLC layer, MAC layer, or physical (PHY) layer.

[0266] The target base station may receive an RRC restart request message. Based on the receipt of the RRC restart request message, the target base station may check whether the UE context of the UE is locally available. Based on the finding that the UE context is not locally available, the target base station may perform the UE context procedure by sending a UE context acquisition request message to the UE source base station (the last serving base station). The UE context acquisition request message may include at least one of the following: the UE context ID, integrity protection parameters, a new cell identifier, or a restart cause, the restart cause being present in the RRC restart request message.

[0267] In the RRC connection resumption procedure, based on the receipt of the UE context acquisition request message, the source base station can check the UE context acquisition request message. If the source base station can identify the UE context by the UE context ID and successfully verify the UE through the integrity protection included in the UE context acquisition request message, and can determine that it will provide the UE context to the target base station, the source base station may respond to the target base station with a UE context acquisition response message. If the source base station cannot identify the UE context by the UE context ID, or if the integrity protection included in the UE context acquisition request message is not effective, or if the source base station determines that it will not provide the UE context to the target base station, the source base station may respond to the target base station with a UE context acquisition failure message.

[0268] In the RRC connection reactivation procedure, the UE context acquisition failure message may include at least the target base station's XnAP ID, the RRC release message, or a cause value.

[0269] In the RRC connection restart procedure, based on the receipt of the UE context acquisition response message, the target base station may send an RRC restart message to the UE. The RRC restart message may include at least one of the following: radio bearer configuration parameters, MCG and / or SCG cell group configuration parameters, measurement configuration parameters, or sk counters, where the sk counter is K gNB This is used to derive the security key for the secondary base station based on this.

[0270] Based on receiving a UE context acquisition failure message, the target base station may send an RRC release message to the UE. For example, based on a UE context acquisition failure message that includes an RRC release message, the target base station may send an RRC release message to the UE. Based on receiving a UE context acquisition failure message, the target base station may send an RRC setup message or an RRC rejection message. Based on receiving a UE context acquisition failure message, the target base station may not send a response message to the UE.

[0271] Based on the receipt of the RRC restart message, the UE may stop timers T319 and T380. Based on the receipt of the RRC restart message, the UE may restore the master cell group configuration parameters, secondary cell group configuration parameters, and PDCP configuration parameters to the UE inactive AS context. Based on the restoration of the master cell group configuration parameters and / or secondary cell group configuration parameters, the UE may configure the SCells of the MCG and / or SCG by configuring the lower layers to consider the restored MCG and / or SCG SCells as being in an inactive state, discard the UE inactive AS context, and release the pause configuration parameters.

[0272] Based on receiving cell group configuration parameters in the RRC restart message, the UE may perform cell group configuration of the MCG and / or SCG. Based on receiving radio bearer configuration parameters in the RRC restart message, the UE may perform radio bearer configuration. Based on the sk counter in the RRC restart message, the UE may perform updating the security key of the secondary base station.

[0273] A UE remains in CM-CONNECTED and can move within the region defined by the base station without notifying the base station when the UE is in an RRC inactive state where its region is RNA. In the RRC inactive state, the last serving base station may maintain the UE context and UE-related NG connections with the serving AMF and UPF. While the UE is in the RRC inactive state, based on downlink data received from the UPF or downlink UE-related signaling from the AMF, the last serving base station may page with the cell corresponding to the RNA if the RNA contains cells from neighboring base stations, and may send RAN paging to neighboring base stations via the Xn interface.

[0274] The AMF may provide the base station with core network support information to help the base station determine whether a UE can be transmitted to an RRC inactive state. This core network support information may include the registration area configured for the UE, a periodic registration update timer, a UE identity index value, a UE-specific DRX, an indication of whether the UE is configured by the AMF in Mobile Initiated Connection Only (MICO) mode, or expected UE behavior. The base station may use the UE-specific DRX and UE identity index value to determine paging opportunities for RAN paging. The base station may use the periodic registration update timer to configure a periodic RNA update timer (e.g., Timer T380). The base station may use expected UE behavior to assist in determining UE RRC state transitions.

[0275] Figure 18 shows an example of the RRC connection reactivation procedure. A UE in the RRC connection state can send and receive data to and from a first base station (source base station) via cell 1. The first base station may determine that the UE in the RRC connection state should transition to the RRC inactive state. Based on this determination, the base station may send an RRC release message containing pause configuration parameters.

[0276] In the embodiment of Figure 18, based on the receipt of an RRC release message containing suspended configuration parameters, the UE can store the current security keys (e.g., KgNB and KRRCint keys) and current configuration parameters in the UE inactive AS context. For example, the UE may store some of the current configuration parameters. The stored (current) configuration parameters are at least one of the following: Robust Header Compression (ROHC) state, QoS flow to mapping rules to DRBs, C-RNTI used by the source PCell, the global cell identity and physical cell identity of the source PCell, and all other configuration parameters except those in reconfiguration with synchronization and serving cell configuration common parameters for SIBs. The Robust Header Compression (ROHC) state may include ROHC states for all PDCP entities (or all bearers), where each PDCP entity per bearer (or each bearer) may have one ROHC state. The QoS flow to DRB mapping rules may be QoS flows for all data radio bearers (DRBs) to DRB mapping rules, where each DRB may have one QoS according to the DRB mapping rules.

[0277] In the embodiment shown in Figure 18, upon receiving an RRC release message containing pause configuration parameters, the UE can stop all SRBs and DRBs except SRB0. Upon receiving the RRC release message containing pause configuration parameters, the UE may activate timer T380, enter an RRC inactive state, and perform a cell selection procedure. Based on the cell selection procedure, the UE may select cell 2 of a second base station (target base station). In the RRC inactive state, the UE may initiate the RRC reactivation procedure. The UE may perform a unified access control procedure. Based on the unified access control procedure, the UE may consider the access attempt for the RRC reactivation procedure to be authorized. The UE may apply default L1 parameter values ​​specified in the corresponding physical layer specification, except for parameters whose values ​​are provided to SIB1, apply the default SRB1 configuration, apply the CCCH configuration, apply the common time alignment timer included in SIB1, apply the default MAC cell group configuration, activate timer T319, and initiate the transmission of an RRC reactivation request message.

[0278] In the embodiment shown in Figure 18, based on the initiation of sending an RRC restart request message, the UE can recover stored configuration parameters and stored security keys from the (stored) UE inactive AS context. For example, the UE can recover stored configuration parameters and stored security keys (e.g., K) from the stored UE inactive AS context, except for master cell group configuration parameters, MR-DC related configuration parameters (e.g., secondary cell group configuration parameters), and PDCP configuration parameters. gNB and K RRCint ) can be restored. The current (restored) K associated with the stored NCC value. gNB Alternatively, based on the next hop (NH) parameter, the UE will determine the base station (K gNB A new key can be derived from the base station. Based on the new key, the UE can derive a security key (e.g., K, respectively) for the integrity protection and encryption of RRC signaling. RRCenc and K RRCint), and security keys (e.g., K, respectively) for protecting the integrity and encrypting user plane data. UPint and K UPenc ) can be derived. The constructed algorithm and K RRCint and K UPint Based on this, the UE (RRC layer) may configure lower layers (e.g., the PDCP layer) to apply integrity protection to all radio bearers except SRB0. The configured algorithm, and K RRCenc and K UPenc Based on this, the UE may configure the lower layers (e.g., the PDCP layer) to apply encryption to all radio bearers except SRB0. Integrity protection and / or encryption may be required for communication between the UE and the base station. Based on integrity protection and / or encryption, the UE can send and receive data with a second base station. The UE may send and receive data with a second base station using the recovered configuration parameters.

[0279] In the embodiment shown in Figure 18, upon initiation of sending an RRC restart request message, the UE may re-establish the PDCP entities of one or more bearers, restart one or more bearers, and send an RRC restart request message to a lower layer. Upon receipt of the RRC restart request message, a second base station may check whether the UE's UE context is locally available. Based on the finding that the UE context is not locally available, the second base station may perform a UE context procedure by sending a retrieve UE context request message to the UE's first base station (the last serving base station). The retrieve UE context request message may include at least one of the restart identity, restart MAC-I, or restart cause.

[0280] In the embodiment shown in Figure 18, the first base station can check the acquired UE context request message upon receiving it. If the first base station can identify the UE context by the UE context ID, successfully verify the UE by the restart MAC-I, and determine to provide the UE context to the second base station, the first base station may respond to the second base station with a UE context acquired response message. Based on the receipt of the UE context acquired response message, the second base station can send an RRC restart message to the UE. Based on the receipt of the RRC restart message, the UE may restore the master cell group configuration parameters, secondary cell group configuration parameters, and PDCP configuration parameters to the UE inactive AS context. Based on the restoration of the master cell group configuration parameters and / or secondary cell group configuration parameters, the UE may configure the SCells of the MCG and / or SCG by configuring the lower layers to consider the restored MCG and / or SCG SCells as being in an inactive state, discard the UE inactive AS context, and release the pause configuration parameters. The UE may send and receive data via the SCells and / or SCG.

[0281] The base station may send an RRC release message to the UE to release the UE's RRC connection. Based on the RRC release message, the UE may release established radio bearers and all radio resources.

[0282] A base station may suspend an RRC connection by sending an RRC release message to the UE. Based on the RRC release message, the UE may suspend all radio bearers except for signaling radio bearer 0 (SRB0). The RRC release message may include suspension configuration parameters. These parameters may include the next hop chain count (NCC) and the reactivation identity (e.g., ID or identifier).

[0283] The base station may send an RRC release message to transition a UE in the RRC connected state to the RRC idle state, or a UE in the RRC connected state to the RRC inactive state, or to transition a UE in the RRC inactive state back to the RRC inactive state when the UE attempts to resume, or to transition a UE in the RRC inactive state to the RRC idle state when the UE attempts to resume.

[0284] The base station may send an RRC release message to redirect the UE to a different frequency.

[0285] The UE may receive an RRC release message from the base station of the serving cell (or PCell). Based on the RRC release message, the UE can take UE actions in response to the RRC release message from the base station. The UE may delay its UE actions in response to the RRC release message for a certain period of time (e.g., 60 milliseconds) from the time it receives the RRC release message or successfully acknowledges receipt of the RRC release message. The UE may send a HARQ acknowledgment to the base station in recognition of the RRC release message. Based on the fact that an RLC protocol data unit (PDU) contains the RRC release message and the RLC PDU contains polling bits, the UE may send an RLC message (e.g., a status report) to the base station in recognition of the RRC release message.

[0286] UE actions in response to an RRC release message from a base station may include at least one of the following: suspending the RRC connection, releasing the RRC connection, cell (re)selection procedure, and / or idle / inactive measurement.

[0287] An RRC release message from a base station may include a pause configuration parameter. Based on the pause configuration parameter, the UE may pause the RRC connection. Pausing the RRC connection may include at least one of the following: a media access control (MAC) reset (or MAC reset), the release of the default MAC cell group configuration, the re-establishment of the RLC entity for one or more radio bearers, the storage of the current configuration parameters and the current security key, the pausing of one or more bearers, including signaling radio bearers and data radio bearers, and / or a transition to an RRC idle state or an RRC inactive state.

[0288] For example, a pause configuration parameter may further include RNA configuration parameters. Based on the RNA configuration parameters, the UE may transition to an RRC inactive state. For example, based on the pause configuration parameter not including RNA configuration parameters, the UE may transition to an RRC idle state. For example, an RRC release message including pause configuration parameters may include an indication of transition to an RRC inactive state. Based on this indication, the UE may transition to an RRC inactive state. For example, based on the RRC release message not including this indication, the UE may transition to an RRC idle state.

[0289] Based on the MAC reset, the UE may perform at least one of the following: stop all timers initiated at the UE-MAC layer, consider all time alignment timers to be expired, set the new data indicator (NDI) for all uplink HARQ processes to value 0, stop any ongoing RACH procedures, discard any explicitly signaled non-contoured random access resources, flush the Msg3 buffer, cancel any triggered scheduling request procedures, cancel any triggered buffer status reporting procedures, cancel any triggered power headroom reporting procedures, flush the soft buffer for all DL HARQ processes, consider the next received transmission to TB as the first transmission for each DL HARQ process, and / or release a temporary C-RNTI.

[0290] Based on the assumption that the time alignment timer has expired, the UE may perform at least one of the following actions: flush all HARQ buffers for all serving cells; (if configured) notify the RRC to release PUCCH for all serving cells; (if configured) notify the RRC to release SRS for all serving cells; clear any configured downlink assignments and configured uplink permissions; clear any PUSCH resources for semi-persistent CSI reporting; and / or assume that all running time alignment timers have expired.

[0291] Default MAC cell group configuration parameters may include buffer state reporting (BSR) configuration parameters for the base station cell group (e.g., BSR timer) and power headroom reporting (PHR) configuration parameters for the base station cell group (e.g., PHR timer or PHR transmit power factor change parameter).

[0292] Re-establishing an RLC entity may include at least one of the following: discarding all RLC SDUs, RLC SDU segments, and RLC PDUs (if any); stopping and resetting all timers of the RLC entity; and resetting all state variables of the RLC entity to their initial values.

[0293] An RRC release message from a base station may not contain a pause configuration parameter. Based on the absence of a pause configuration parameter in the RRC message, the UE may perform a release of the RRC connection. The release of the RRC connection may include at least one of the following: MAC reset (or MAC reset), discarding stored configuration parameters and stored security keys (or discarding stored UE inactive AS contexts), release of pause configuration parameters, release of all radio resources including RLC entities, MAC configuration, and associated PDCP entities, and SDAP release to all established radio bearers, and / or transition to an RRC idle state.

[0294] RRC release messages may include RRC early data completion messages.

[0295] Small Data Transmission (SDT) is a procedure that enables data transmission / reception while a wireless device remains in an RRC inactive or RRC idle state (e.g., without transitioning to an RRC connected state).

[0296] In embodiments, a Small Data Transmission (SDT) procedure may include the exchange of user data between a radio device and a base station while the radio device is in a disconnected state (e.g., Radio Resource Control (RRC) disconnected state) (e.g., idle state, inactive state, etc.). The amount of data exchanged in an SDT transmission of an SDT procedure may be less than a threshold amount of data. An SDT procedure may include a small amount of data and / or one SDT transmission of a series of SDT transmissions. For example, using an SDT procedure, a radio device and / or a base station may transmit and / or receive data via the user plane (UP) or control plane (CP) while the radio device remains in a disconnected state (e.g., idle, inactive, etc.). For example, using an SDT procedure, a radio device may transmit and / or receive data without completing a connection setup or restart procedure (and without control plane signaling associated with setup and / or restart). The data may include user data and signals.

[0297] In an embodiment, a radio device may require authorization to transmit data associated with the SDT procedure (e.g., uplink data). The radio device may receive authorization from / through a base station. Authorization may be an uplink authorization for one or more uplink resources, and the radio device may use one or more uplink resources to transmit data (e.g., uplink data). Authorization may be a dynamic uplink authorization or a configured uplink authorization for one or more uplink resources. A dynamic uplink authorization may indicate one or more specific uplink resources used for uplink transmission at a given time. A configured uplink authorization may indicate resources that are repetitive, intermittent, and / or periodic. For example, a configured uplink authorization configuration may indicate the periodicity of configured uplink authorizations and may be periodically reused using one or more uplink resources of the configured uplink authorization configuration. For example, a configured uplink authorization may be configured / activated, and the resources associated with the configured uplink authorization configuration may be used until the configured uplink authorization is released / deactivated. For example, a dynamic uplink grant may indicate a resource at time k, while a configured uplink grant may grant a resource at time k+nT, where T is the duration of the configured uplink grant and n is an integer [0, 1, 2, ...].

[0298] In the embodiment, a wireless device may obtain uplink permission via a physical or MAC signal indicating uplink permission (e.g., DCI or Random Access (RA) response). For example, in a Random Access (RA)-based procedure (e.g., an Early Data Transmission (EDT) procedure), the wireless device may transmit an RA preamble requesting one or more uplink resources. Based on the RA preamble, the wireless device may receive uplink permission indicating one or more uplink resources for transmitting small data.

[0299] In the embodiment, a wireless device may obtain uplink permission based on a configured uplink permission (CG). A configured uplink permission may be associated with a configured uplink permission configuration (e.g., a pre-configured uplink resource (PUR) configuration). A wireless device may receive a configured uplink permission configuration via an RRC message (e.g., an RRC release message). A configured uplink permission configuration may indicate permission for one or more uplink resources, and the wireless device may use and / or reuse one or more uplink resources (e.g., pre-configured uplink resources) to transmit small data.

[0300] SDT can be configured to be performed on either RACH or a configured uplink authorization (CG) resource (e.g., a Type 1 CG resource). An SDT configured to be performed on RACH may be called a RACH-based SDT (or EDT). An SDT configured to be performed on a CG resource may be called a CG-based SDT (or uplink transmission using PUR). For example, a radio device may transmit a first uplink message for an SDT procedure based on an uplink authorization from a RACH-based SDT or a CG-based SDT. For example, a radio device may transmit a first uplink message for an SDT procedure based on an RA response indicating an uplink authorization for an SDT procedure or a configured uplink authorization for an SDT procedure. For example, for subsequent transmissions, a radio device may transmit data / signals using a dynamic uplink authorization or a configured uplink authorization. A base station may transmit a dynamic uplink authorization or a configured uplink authorization to a radio device.

[0301] A configured uplink authorization for an SDT (e.g., an SDT resource) can consist of either an initial BWP or a dedicated BWP. A configured uplink authorization for an SDT can consist of a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier. A configured uplink authorization for an SDT can be provided to a radio device in RRC-connected state via / within an RRC release message. For RACH, the base station can configure the radio device regardless of whether two-step and four-step RA types are used for the SDT. If both are available, the UE can choose one of the RA types.

[0302] A radio device can select a RACH resource for SDT. A RACH resource may differ from a RACH resource for RRC connectivity. A RACH resource may include at least one of the RA preamble and a RACH opportunity (RO). The radio device may use the RACH resource to perform a RACH procedure to the SDT. The radio device may receive a Random Access Response (RAR) via the base station's serving cell. A RAR may include / indicate an uplink grant to the SDT. Based on the RAR, a radio device in an RRC inactive or RRC idle state may send a first (uplink) message to the base station for the SDT.

[0303] SDT may include user plane (UP) small data transmissions and control plane (CP) small data transmissions. Based on UP small data transmissions, UEs in an RRC idle or RRC inactive state may transmit / receive data via the user plane (e.g., via the DTCH). Based on CP small data transmissions, UEs in an RRC idle or RRC inactive state may transmit / receive data via the control plane (e.g., the CCCH). Based on UP small data transmissions, a base station of a UE may receive downlink data from the UE's UPF via the user plane. Based on CP small data transmissions, a base station of a UE may receive downlink data from the UE's AMF / non-SDT via the control plane.

[0304] A base station may configure / indicate a first radio bearer to a radio device. The first radio bearer may be configured in an SDT. For example, the base station may send an RRC release message to the radio device that configures / indicates a first radio bearer. The base station may send an SDT configuration (SDT configuration) to the radio device. The SDT configuration may include parameters for the first radio bearer. The RRC release message may include the SDT configuration. The radio device may send SDT data for the first radio bearer during the SDT procedure.

[0305] SDT data may be data on the first logical channel of the first radio bearer. The data may include user data and signals. The first radio bearer may include a data radio bearer (DRB) and a signaling radio bearer (SRB). The SRB may include SRB1 and SRB2. The base station may enable radio devices to transmit SDT data during the SDT procedure.

[0306] User data may be DRB user data. Signals may be SRB signals. A wireless device may transmit user data via the DRB. A wireless device may transmit signals via the SRB. For example, a signal may be an RRC message or a NAS message.

[0307] The second radio bearer may not be part of the SDT procedure. The second radio bearer may not be the first radio bearer. The base station may not allow radio devices to transmit data for the second radio bearer during the SDT procedure. Non-SDT data may be data for the second logical channel of the second radio bearer. The data may include user data and signals. The second radio bearer may include a data radio bearer (DRB) and a signaling radio bearer (SRB). The SRB may include SRB1 and SRB2. User data may be user data for the DRB. The base station may not have to allow radio devices to transmit non-SDT data during the SDT procedure.

[0308] A wireless device may determine to initiate an SDT procedure. For example, a wireless device may determine to initiate an SDT procedure based on at least one of the following: the amount of configured uplink (UL) data is below the amount of transmission through the wireless bearer for which SDT is enabled, and the measured signal strength in the cell (e.g., RSRP) is above a configured threshold.

[0309] Based on the initiation of the SDT procedure, the radio device may (re)activate AS security. For example, the radio device may have a sold value for the Next Hop Chain Count (NCC) provided in the RRC release message during the previous RRC connection release procedure. For example, the RRC release message may include a pause configuration parameter. Based on the initiation of the SDT procedure, the radio device may use the NCC to derive the base station key (e.g., KgNB / KeNB). Based on the base station key, the radio device may derive the integrity protection key and the encryption key. The integrity protection key may include the RRC message, the KRRCint integrity protection key, and the user plane (data), the KUPint integrity protection key. The encryption key may include the RRC message, the KRRCenc encryption key, and the user plane (data), the KUPenc encryption key. The radio device may be configured to reactivate integrity protection using the integrity protection key for data / signals received and transmitted by the radio device during the SDT procedure. A wireless device may be configured to resume encryption using a key for encrypting data / signals received and transmitted by the wireless device during the SDT procedure.

[0310] Once initiated, the SDT procedure may continue unless the radio device is explicitly directed to RRC idle or RRC inactive (via RRC release) or to a connected RRC (via RRC restart).

[0311] An SDT (procedure) may include at least one of an initial SDT transmission and subsequent transmissions. Based on the initiation of an SDT procedure, a radio device may transmit a first (uplink) message for the SDT procedure. The radio device may transmit the first message via an SDT resource. An SDT resource may be a CG resource or uplink grant in response to a RACH preamble for the SDT procedure.

[0312] The first message may be Msg3 or MsgA. The first message may include at least one of the following: an RRC request message, first uplink data, support parameters (or support information for the SDT procedure), and a request for uplink permission for the second uplink data. The RRC request message may be transmitted via a common control channel (CCCH). A CCCH message may include the RRC request message. The first uplink data may include user data and signals (e.g., an RRC message). The user data of the first uplink data may be transmitted via a dedicated traffic channel (DTCH). The signals of the first uplink data may be transmitted via a dedicated control channel (DCCH). A DTCH message may include the user data of the first uplink data. A DCCH message may include the signals of the first uplink data. CCCH messages and DTCH / DCCH messages may be multiplexed into the first message. The first message may include at least one of the CCCH message, DTCH message, and DCCH message. Support parameters (or support information) may include (expected) traffic information for the wireless device. Traffic information may indicate at least one of the following: whether subsequent transmissions to the uplink and / or downlink are expected, and the amount of data for the subsequent transmissions. For example, support parameters may include release support information (RAI). A request for uplink permission for second uplink data may be a buffer status report (BSR).

[0313] A radio device may receive a response from the base station to a first message. The response may include an RRC response message to the RRC request message of the first uplink message. Based on the response including the RRC response message, the radio device may complete the SDT procedure. The RRC response message may be an RRC release message, an RRC restart message, or an RRC setup message. Based on the RRC response message being an RRC release message, the radio device may transition back to the RRC idle state or RRC inactive state. Based on the RRC message being an RRC restart / setup message, the radio device may transition to the RRC connected state.

[0314] A radio device may receive a response from the base station to the first message. The response may not include an RRC response message. The base station may determine that the radio device is RRC inactive or RRC idle and is able to proceed with subsequent transmissions. The response may indicate uplink permission for subsequent transmissions. The response may indicate subsequent transmissions. Based on the response, the radio device may proceed with subsequent transmissions while remaining in an RRC inactive or RRC idle state. For example, the response may be Msg4 or MsgB.

[0315] Following the initial SDT transmission, subsequent transmissions may be handled differently depending on the type of resource being configured. If a CG resource is used, the network may schedule subsequent UL transmissions using dynamic authorization or at the next CG resource opportunity. If a RACH resource is used, the network may schedule subsequent UL and downlink DL transmissions using dynamic authorization and allocation after the completion of the RA procedure.

[0316] During subsequent transmissions, the wireless device may receive an RRC response message to the RRC request message of the first uplink message. Based on the RRC response message, the wireless device may complete the SDT procedure. The RRC response message may be an RRC release message, an RRC restart message, or an RRC setup message. Based on the RRC response message being an RRC release message, the wireless device may transition back to the RRC idle state or RRC inactive state. Based on the RRC response message being an RRC restart / setup message, the wireless device may transition to the RRC connected state.

[0317] Based on the receipt of a paging message indicating an SDT(procedure), the wireless device may determine to initiate an SDT procedure. The wireless device may send a first uplink message for the SDT procedure, which may include an RRC request message. The RRC request message may indicate an SDT(procedure).

[0318] The UE may determine to initiate an SDT using a configured uplink grant (CG-based SDT) based on the fulfillment of the configured uplink grant conditions. The configured uplink grant conditions may include at least one of the following: the UE has a valid configured uplink grant configuration parameter; the UE has a valid timing alignment (TA) value; the serving cell's system information indicates configured uplink grant support; the establishment or restart request relates to a call from a mobile phone and the establishment cause is mo data or mo exception data or delayed-tolerant access; the UE supports configured uplink grant; the size of the resulting MAC PDU, including total uplink data, is expected to be equal to or less than the TBS configured for the configured uplink grant; and the UE has a stored NCC value provided in the RRC release message, including the pause configuration parameter, during the pause procedure described above.

[0319] The UE may determine the timing alignment value for a small data transmission that is valid for a configured uplink grant based on whether the TA verification conditions for the configured uplink grant are met. The TA verification conditions for a configured uplink grant may include at least one of the following: the time alignment timer for the configured uplink grant is activated, or the serving cell RSRP does not increase beyond an RSRP increase threshold and does not decrease beyond an RSRP increase threshold.

[0320] In the case of CG-based SDT (or uplink transmission using PUR), a UE in RRC connection state may send a CG (or PUR) configuration request message (or support information message) to the base station, which may include at least one of a requested number of CG opportunities, which may be one or infinite; the periodicity of the requested CG; the requested transport block size (TBS) for the CG; and / or the requested time offset for the first CG opportunity.

[0321] A base station can transmit a configured uplink authorization configuration (parameters), including (pre)configured uplink authorization (resources), to a radio device. For example, in response to a configured uplink authorization configuration request message, the base station may transmit configured uplink authorization configuration parameters, including preconfigured uplink resources, to the UE. For example, the base station may transmit an RRC release message, including the configured uplink authorization configuration parameters.

[0322] The configured uplink grant configuration parameters may include at least one of the following: the display for setting up or releasing the configured uplink grant configuration parameters, the number of configured uplink grant opportunities, the configured uplink grant resource identifier (configured uplink grant RNTI), the configured uplink grant configuration identity (configured uplink grant configID), the time offset value for the first configured uplink grant opportunity (configured uplink grant start time), the periodicity of the configured uplink grant resource (configured uplink grant periodicity), the duration of the configured uplink grant response window (configured uplink grant response window time), the threshold for the change in serving cell RSRP in dB for TA verification (configured uplink grant change threshold) (the threshold includes RSRP increase threshold and RSRP decrease threshold), the time alignment timer value for the configured uplink grant, and / or the physical configuration parameters of the configured uplink grant. The physical configuration parameters of the configured uplink grant may include at least one of the following: The configured uplink authorization's PUSCH configuration parameter, the configured uplink authorization's PDCCH configuration parameter, the configured uplink authorization's PUCCH configuration parameter, the downlink carrier configuration parameter used for the configured uplink authorization, and / or the uplink carrier frequency used for the configured uplink authorization. A configured uplink authorization RNTI can be assigned to two or more radio devices. A configured uplink authorization configID can be unique at a single base station.

[0323] Based on the configured uplink permission configuration parameters, the UE may store or replace the configured uplink permission configuration parameters provided by the configured uplink permission configuration parameters, based on an indication requesting the setup of the configured uplink permission configuration parameters. In response to receiving the configured uplink permission configuration parameters, the UE may configure the configured uplink permission configuration parameters by activating the time alignment timer for the configured uplink permission with the value of the time alignment timer for the configured uplink permission. For example, in response to receiving the configured uplink permission configuration parameters, the UE may configure the configured uplink permission configuration parameters by activating the time alignment timer for the configured uplink permission with the value of the time alignment timer for the configured uplink permission. In response to receiving the configured uplink permission configuration parameters, the UE may discard the configured uplink permission configuration parameters based on an indication requesting the release of the configured uplink permission configuration parameters. In response to configuring the configured uplink permission configuration parameters, the UE may generate a configured uplink permission based on the configured uplink permission configuration parameters. For example, based on the configured uplink permission configuration parameters, the UE may determine when to generate a configured uplink permission. For example, based on the start time and periodicity of the configured uplink authorization, the UE may determine when to generate a configured uplink authorization. For example, based on the PUSCH configuration parameters, the UE may determine (transfer a block) a configured uplink authorization. For example, based on the PUSCH configuration parameters, the UE may determine (transfer a block) a configured uplink authorization.

[0324] Based on the CG configuration parameters, a UE in an RRC idle or RRC inactive state may start the CG time alignment timer with the value of the CG time alignment timer and configure the CG configuration parameters. In response to the configuration of the CG configuration parameters, a UE in an RRC idle or RRC inactive state may generate pre-configured uplink resources / permissions for the CG based on the CG configuration parameters. Based on the first RRC release message, the UE may perform a cell (re)selection procedure. Based on the cell (re)selection procedure, a UE in an RRC idle or RRC inactive state may select cell 2 of a second base station (target base station). A UE in an RRC idle or RRC inactive state may have the first uplink data in the uplink buffer. A UE in an RRC idle or RRC inactive state may determine to initiate CG-based SDT based on the fulfillment of one or more conditions.

[0325] A wireless device may transmit a message (e.g., a first uplink message for an SDT procedure) using CG (or uplink resource / permission for CG), and a UE (UE-MAC entity) may start a CG response window timer at the CG response window time. Based on the start, the UE may monitor the PDCCH identified by the CG RNTI until the CG response window timer expires. The UE (UE-MAC entity) may receive a downlink message (e.g., DCI) identified by the CG RNTI on the PDCCH. Based on the receipt of the downlink message indicating uplink permission for retransmission, the UE may restart the configured CG response window timer in the last subframe (e.g., 4 subframes) of the PUSCH transmission indicating the uplink permission pulse time gap. Based on the restart, a UE in an RRC idle or RRC inactive state may monitor the PDCCH identified by the CG RNTI until the CG response window timer expires. Based on the receipt of a downlink message indicating an L1 (Layer 1) acknowledgment to the CG, an RRC idle or RRC inactive UE may stop the CG response window timer and consider the CG-based SDT to have been successful. Based on the receipt of a downlink message indicating a PUR fallback, an RRC idle or RRC inactive UE may stop the CG response window timer and consider the CG-based SDT to have failed. Based on the receipt of a downlink message indicating a PDCCH transmission (downlink permission or downlink assignment) to the CG RNTI and / or MAC PDU, including successful decoding of uplink data, an RRC idle or RRC inactive UE may stop the CG response window timer and consider the CG-based SDT to have been successful. Based on the PDCCH transmission, an RRC idle or RRC inactive UE may receive at least one of an RRC response message and downlink data. The RRC response message may include at least one of an RRC release message or an RRC early data completion message.A UE in an RRC idle or RRC inactive state may consider a CG-based SDT to have failed based on the fact that it has not received any downlink messages until the CG response window timer expires. Based on the assumption that a CG-based SDT has failed, the UE may perform a random access procedure. For example, a random access procedure may include a RACH procedure for a RACH-based SDT.

[0326] CG resources for the SDT procedure may be configured on NUL and / or SUL. A radio device may start a (response) window after a CG transmission or dynamic grant (DG) transmission for a CG-based SDT. Based on the start of the window, the radio device may start a window timer.

[0327] When a wireless device receives a TAT-SDT configuration from a base station (e.g., via an RRC release message), it may start the Timer Alignment Timer (TAT) associated with the CG-SDT resource (TAT-SDT). When the wireless device receives a TA command, it may restart the TAT-SDT. The wireless device may determine that the CG resource for the SDT procedure is valid based on the TA verification mechanism. For example, the wireless device may determine that the CG resource for the SDT procedure is valid based on the RSRP associated with the CG resource and the RSRP threshold associated with the CG resource.

[0328] In the case of CG-based SDT, subsequent data transmissions may use CG resources or DG (e.g., dynamic authorization addressed to the UE's C-RNTI). The C-RNTI may be a C-RNTI explicitly allocated or configured by the base station. The base station may transmit multiple CG-SDT configurations for each carrier in an RRC idle or RRC inactive state. A CG-SDT resource may be active in a single cell. A radio device may release a CG-SDT resource when the TAT-SDT expires in an RRC idle or RRC inactive state.

[0329] The base station may transmit the configuration of the SDT procedure to the radio device via an RRC release message. The configuration may indicate the configured radio bearers in the SDT procedure (e.g., SDT Bearers). Based on receiving the RRC release message, the radio device may suspend one or more radio bearers. The radio device may suspend the RRC connection. The radio device may reactivate SDT bearers based on initiating the SDT procedure while keeping non-SDT bearers suspended. During the SDT procedure, the radio device may transmit / receive data / signals associated with the SDT bearers.

[0330] During the SDT procedure, the wireless device may receive an RRC message (e.g., an RRC restart message) that transitions it to an RRC connected state. Based on the receipt of the RRC restart message, the wireless device may restart as a non-SDT bearer. The wireless device may then transition to an RRC connected state.

[0331] During the SDT procedure, a radio device may send a message based on having data / signals associated with a non-SDT bearer. The message may indicate the arrival of data / signals associated with a non-SDT bearer. The message may request a transition to the RRC connection state. The message may be a Common Control Channel (CCCH) message or a Dedicated Control Channel (DCCH) message. For example, a CCCH message may include an RRC (restart) request message. A DCCH message may include an informational message. Based on the receipt of the message, the base station may send an RRC message (e.g., an RRC restart message) to transition to the RRC connection state.

[0332] A radio device performing the SDT procedure may detect SDT procedure failures. Failures include at least one of the following: the SDT failure detection timer has expired; cell (re)selection / change; inability to comply with RRC messages; radio link failure (RLF); RLC (PDU) maximum retransmission failure; receiving a rejection / fallback indication from the base station; or the CG response window timer has expired.

[0333] The wireless device may start an SDT failure detection timer based on the initiation of the SDT procedure. The wireless device does not have to start T319 or T300, which are configured to start based on an RRC restart request message.

[0334] Based on the detection of a failure in the SDT procedure, the wireless device may release the RRC connection. For example, by releasing the RRC connection, the wireless device may transition to an RRC idle state. The wireless device may perform high-layer (e.g., application layer) retransmission.

[0335] Based on the detection of a failure in the SDT procedure, the wireless device may continue to suspend the RRC connection. For example, the wireless device may remain in an RRC inactive state. The wireless device may remain in an RRC idle state with the RRC connection suspended. The wireless device may send an RRC resume request to a new cell. For example, in response to the detection of a failure, the wireless device may select a new cell based on a cell (re)selection procedure.

[0336] Figure 19 shows an example of Small Data Transmission (SDT). The wireless device may be in a disconnected state (e.g., RRC idle state, RRC inactive state, etc.). For example, the wireless device may receive a release message. The release message may be an RRC release message. The wireless device may transition to a disconnected state based on the release message. The wireless device may decide to initiate the SDT procedure. The decision may occur while the wireless device is in a disconnected state. The decision may be based on the fact that the wireless device is in a disconnected state.

[0337] In the embodiment of Figure 19, the wireless device may determine to initiate an SDT procedure (for example, based on the fulfillment of one or more SDT conditions). The determination may occur while the UE is in a disconnected state. The determination may be based on the UE being in a disconnected state. Initiating an SDT may include at least one of the following: activating / deriving a security key for integrity protection and / or encryption; configuring to reactivate integrity protection; applying the security key for encryption to data / signals; configuring to use SDT; and generating an RRC request message.

[0338] In the embodiment of Figure 19, based on the initiation of SDT, the radio device may transmit a first (uplink) message (to the initial SDT). The first message may be transmitted while in a disconnected state. The first message may be transmitted to a base station (via the base station's serving cell). The first message may be Msg3 and / or MsgA. The first message may include at least one of the following: an RRC request message to the SDT, first uplink data, and support parameters to the SDT (or support information for the SDT procedure). The first message may indicate that subsequent transmissions (and receptions) are expected / required. For example, support parameters may indicate the (expected) traffic pattern / size for subsequent transmissions. Msg3 and / or MsgA may be transmitted over an uplink shared channel (UL-SCH). Msg3 and / or MsgA may include a C-RNTI MAC CE and / or CCCH SDU as part of a random access procedure and may be associated with a UE conflict resolution identity. A wireless device may perform a RACH procedure against an SDT. For example, a wireless device may perform a RACH procedure using a RACH resource configured in the SDT. The RACH resource may include at least one of the SDT and a RA preamble for a RACH opportunity (RO).

[0339] In the embodiment of Figure 19, the SDT(procedure) may include an initial small data transmission (or initial small data transmission phase) and a subsequent transmission (or subsequent transmission phase or subsequent SDT(phase)). For example, a wireless device may initiate an SDT procedure. The wireless device may decide to initiate an SDT procedure based on the reception of a paging message indicating an SDT, or based on having a packet associated with an SDT. For example, the packet may be a packet of a configured wireless bearer for an SDT. The wireless device may initiate an SDT based on the fulfillment of an SDT condition, where the SDT condition includes at least one of a first condition for an RA-based SDT or a second condition for a CG-based SDT. Based on the initiation of an SDT, the wireless device may transmit a first (uplink) message for an initial SDT. The initial SDT may include the transmission of the first message and the reception of a response to the first message. The initial SDT phase may be a duration from the time of transmission of the first message to the time for determining whether the transmission was successfully completed. The time may be the time it takes to receive a response to the first message. A wireless device may initiate a subsequent SDT (phase) after the initial (SDT) transmission has been successfully completed. The wireless device may complete the (subsequent) SDT procedure based on receiving a message indicating completion of the SDT procedure or detecting a failure of the SDT procedure. The message may be an RRC release message.

[0340] In the embodiment of Figure 19, based on the second condition being met, the wireless device may transmit a first message using the CG configured in the SDT. The wireless device may start the CG (or PUR) response window timer and monitor the cell's PDCCH for responses to the first message. Based on the reception of a response, the wireless device may determine that the initial SDT (or transmission of the first message) has been successfully completed. Based on the absence of a response (e.g., until the CG response window timer expires), the wireless device may determine that the initial SDT (or transmission of the first message) has not been successfully completed.

[0341] In the embodiment shown in Figure 19, based on the first condition being met, the wireless device may transmit an RA preamble using an RA resource for the (initial) SDT. Based on the receipt of an RA response indicating an uplink resource for the (initial) SDT, the wireless device may transmit a first message using the uplink...

Claims

1. An apparatus for a wireless device, wherein the apparatus is One or more processors, The memory that stores the instructions and The instruction, when executed by one or more processors, is transmitted to the wireless device. Processing a radio resource control (RRC) message received by the radio device from a base station, wherein the RRC message is: A measurement configuration for one or more measurements by the wireless device while the wireless device is in an RRC inactive state, The SDT configuration of the Small Data Transmission (SDT) procedure for transmission by the wireless device while the wireless device is in the RRC inactive state and This includes, While the wireless device is in the RRC inactive state, To initiate the SDT procedure based on the SDT configuration, and During the SDT procedure, the measurement associated with the measurement configuration is not performed. To do A device that performs an action.

2. When the instruction is executed by the one or more processors, the wireless device further: After the wireless device is in the RRC inactive state, Before the wireless device initiates the SDT procedure, The apparatus according to claim 1, which causes the measurement associated with the measurement configuration to be performed.

3. The RRC message includes an RRC release message, Performing the aforementioned measurement means The wireless device receives the RRC release message, or The wireless device is in the RRC inactive state. The apparatus according to claim 2, based on one or more of the following.

4. When the instruction is executed by the one or more processors, the wireless device further: The apparatus according to claim 3, which transitions to the RRC inactive state based on the RRC release message.

5. When the instruction is executed by the one or more processors, the wireless device further: The apparatus according to claim 3, which starts a measurement timer based on the RRC release message.

6. The apparatus according to claim 5, wherein the measurement timer is one or more of the timer for measurement in the RRC inactive state, or T331.

7. When the instruction is executed by one or more processors, the wireless device further: The apparatus according to claim 6, wherein the measurement associated with the measurement configuration is performed while the measurement timer is running.

8. The aforementioned SDT configuration is, Next hop chain number (NCC), The resumed identity of the wireless device, and The configured wireless bearer is shown in the SDT procedure. The apparatus according to claim 1, comprising at least one of the following.

9. Initiating the aforementioned SDT procedure means The wireless device receives a paging message indicating the SDT procedure, and / or The data from the aforementioned SDT procedure is available to the wireless device. The apparatus according to claim 1, based on one or more of the following.

10. The wireless device supports carrier aggregation and / or dual connection, and / or The apparatus according to claim 1, wherein the measurement configuration is for the carrier aggregation and / or dual connection of the wireless device.

11. A method, wherein the method is The wireless device receives a radio resource control (RRC) message from a base station, wherein the RRC message is: A measurement configuration for one or more measurements by the wireless device while the wireless device is in an RRC inactive state, The SDT configuration of the Small Data Transmission (SDT) procedure for transmission by the wireless device while the wireless device is in the RRC inactive state and This includes, While the wireless device is in the RRC inactive state, To initiate the SDT procedure based on the SDT configuration, and During the SDT procedure, the measurement associated with the measurement configuration is not performed. To do Methods that include...

12. The wireless device, After the wireless device is in the RRC inactive state, Before the wireless device initiates the SDT procedure, The method according to claim 11, further comprising performing the measurement associated with the measurement configuration.

13. The RRC message includes an RRC release message, Performing the aforementioned measurement means The wireless device receives the RRC release message, or The wireless device is in the RRC inactive state. The method according to claim 12, based on one or more of the following.

14. The method of claim 13, further comprising causing the wireless device to transition to the RRC inactive state based on the RRC release message.

15. The method according to claim 13, further comprising the wireless device starting a measurement timer based on the RRC release message.

16. The method according to claim 15, wherein the measurement timer is one or more of the timer for measurement in the RRC inactive state, or T331.

17. The method according to claim 16, further comprising causing the wireless device to perform the measurement associated with the measurement configuration while the measurement timer is activated.

18. The SDT configuration is, Next hop chain number (NCC), The resumed identity of the wireless device, and The configured wireless bearer is shown in the SDT procedure. The method according to claim 11, comprising at least one of the following.

19. Initiating the SDT procedure means The wireless device receives a paging message indicating the SDT procedure, and / or The data from the aforementioned SDT procedure is available to the wireless device. The method according to claim 11, based on one or more of the following.

20. The wireless device supports carrier aggregation and / or dual connection, and / or The method according to claim 11, wherein the measurement configuration is for the carrier aggregation and / or dual connection of the wireless device.

Images