Communication Method

Abstract

A wireless device receives a first radio resource control release message from a first base station, the first radio resource control release message including a first configured authorized configuration for a first cell in a radio resource control non-connected state of the wireless device. The wireless device transmits a second radio resource control message via a second cell, the second radio resource control message including a release indication for the first configured authorized configuration.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 058,134, filed on July 29, 2020, which is hereby incorporated by reference in its entirety. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Examples of several of the various embodiments of the present disclosure are described herein with reference to the accompanying drawings.

[0004] Figure 1A and Figure 1B An exemplary mobile communication network is shown in which embodiments of the present disclosure may be implemented.

[0005] Figure 2A and Figure 2B New Radio (NR) user plane and control plane protocol stacks are shown separately.

[0006] Figure 3 Shown in Figure 2A Examples of services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A Shows the flow Figure 2A Figure 2 shows an exemplary downlink data flow of the NR user plane protocol stack.

[0008] Figure 4B An exemplary format of a MAC subheader in a MAC PDU is shown.

[0009] Figure 5A and Figure 5B The mapping between logical channels, transport channels and physical channels for downlink and uplink are shown respectively.

[0010] Figure 6 is an example diagram showing RRC state transition of a UE.

[0011] Figure 7 An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown.

[0012] Figure 8 An exemplary configuration of time slots in the time and frequency domain of an NR carrier is shown.

[0013] Fig. 9 An example of bandwidth adaptation using three configured BWPs for NR carriers is shown.

[0014] Fig. 10A Three carrier aggregation configurations with two component carriers are shown.

[0015] Fig. 10B An example of how aggregated cells may be configured into one or more PUCCH groups is shown.

[0016] Fig.11A An example of SS / PBCH block structure and location is shown.

[0017] Fig. 11B An example of CSI-RS mapped in the time and frequency domains is shown.

[0018] Fig. 12A and Fig. 12B Three examples of downlink and uplink beam management procedures are shown respectively.

[0019] Fig.13A , Fig. 13B and Fig. 13C A four-step contention-based random access procedure, a two-step contention-free random access procedure and another two-step random access procedure are shown respectively.

[0020] Fig.14A An example of a CORESET configuration for the bandwidth portion is shown.

[0021] Fig. 14B An example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing is shown.

[0022] Fig.15 An example of a wireless device in communication with a base station is shown.

[0023] Fig.16A , Fig. 16B , Fig. 16C and Fig.16D Exemplary structures for uplink and downlink transmissions are shown.

[0024] Fig.17 An example of an RRC connection re-establishment procedure is shown.

[0025] Fig.18 An example of an RRC connection resumption procedure is shown.

[0026] Fig.19 An example of configured authorization is shown.

[0027] Fig. 20 An example of user plane configured authorization and control plane configured authorization is shown.

[0028] Fig.21 An example of releasing configured-grant (CG) configuration parameters is shown.

[0029] Fig. 22 An example of an enhanced CG release procedure is shown.

[0030] Fig.23 An example of an enhanced CG release procedure for recovering from RRC connection failure is shown.

[0031] Fig.24 An example of CG release in a CU DU architecture is shown.

[0032] Fig.25 An example of a CG configuration request including a cell identifier is shown. DETAILED DESCRIPTION

[0033] In the present disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope of the present invention. In fact, after reading the specification, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. The embodiments of the present invention should not be limited by any described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Restrictions, features and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figure highlighting functionality and advantages is provided only for illustrative purposes. The disclosed architecture is flexible and configurable enough so that it can be utilized in a manner different from that shown. For example, the actions listed in any flow chart can be reordered or only optionally used in certain embodiments.

[0034] Embodiments may be configured to operate as desired. When certain criteria are met, such as in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., the disclosed mechanism may be executed. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various exemplary embodiments may be applied. Therefore, exemplary embodiments that selectively implement the disclosed protocol may be implemented.

[0035] A base station may communicate with a mixture of wireless devices. A wireless device and / or base station may support multiple technologies and / or multiple versions of the same technology. A wireless device may have certain specific capabilities, depending on the wireless device category and / or capabilities. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure may refer to a subset of the total wireless devices in the coverage area. For example, the present disclosure may refer to multiple wireless devices of a given LTE or 5G version with a given capability and in a given sector of a base station. The multiple wireless devices in the present disclosure may refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in the coverage area that perform according to the disclosed methods, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not comply with the disclosed methods, for example, these wireless devices or base stations may perform based on older versions of LTE or 5G technology.

[0036] In the present disclosure, "a" and "an" and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will be interpreted as "at least one" and "one or more". In the present disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase after the term "may" is an example of a suitable possibility among multiple suitable possibilities that may or may not be used for one or more embodiments in various embodiments. As used herein, the terms "comprising" and "consisting of..." list one or more components of the element being described. The terms "comprising" and "including" are interchangeable and do not exclude that unlisted components are included in the element being described. In contrast, "consisting of..." provides a complete listing of the one or more components of the element being described. As used herein, the term "based on" should be interpreted as "based at least in part on" rather than, for example, "based only on". As used herein, the term "and / or" represents any possible combination of the listed elements. For example, “A, B and / or C” can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0037] If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, the possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase after the term "based on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase after the phrase "in response to" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "depends on" (or equivalently "at least depends on") indicates that the phrase after the phrase "depends on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "adopting / using" (or equivalently "at least adopting / using") indicates that the phrase after the phrase "adopting / using" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments.

[0038] The term configured may relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. "Configured" may also mean a specific setting in a device that affects the operational characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device to provide specific characteristics to the device, whether the device is in an operational state or a non-operational state. Terms such as "a control message caused in a device" may mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational state or a non-operational state.

[0039] In the present disclosure, a parameter (or equivalently referred to as a field or information element: IE) may include one or more information objects, and an information object may include one or more other objects. For example, if parameter (IE) N includes parameter (IE) M, and parameter (IE) M includes parameter (IE) K, and parameter (IE) K includes parameter (information element) J. Then, for example, N includes K, and N includes J. In an exemplary embodiment, when one or more messages include multiple parameters, it means that a parameter of the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0040] Many of the features set forth are described as optional, either by the use of "may" or by the use of parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation that can be obtained by selecting from the set of optional features. The present disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, i.e., having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0041] Many elements described in the disclosed embodiments can be implemented as modules.Modules are defined here as elements that perform defined functions and have defined interfaces to other elements.Modules described in the present disclosure can be implemented by hardware, software, firmware, wetware (for example, hardware with biological elements) in combination with hardware, or a combination thereof, all of which can be equivalent in behavior.For example, a module can be implemented as a software routine written in a computer language, which is configured to be executed by a hardware machine (such as, C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as, Simulink, Stateflow, GNU Octave or LabVIEWMathScript).It is possible to implement a module 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, C++, etc. FPGAs, ASICs, and CPLDs are often programmed using a hardware description language (HDL), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between less functional internal hardware blocks on the programmable device. The mentioned techniques are often used in combination to achieve the results of the functional blocks.

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

[0043] The CN 102 may provide 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-carrier DN, for the wireless device 106. As part of the interface functionality, the CN 102 may set up an end-to-end connection between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0044] The RAN 104 may connect the CN 102 to the wireless device 106 via radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The direction of communication from the RAN 104 to the wireless device 106 over the air interface is referred to as downlink, while the direction of communication from the wireless device 106 to the RAN 104 over the air interface is referred to as uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplex (FDD), time division duplex (TDD), and / or some combination of the two duplex technologies.

[0045] The term "wireless device" may be used throughout this disclosure to mean and encompass any mobile or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device may be a phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicle roadside unit (RSU), a relay node, a car, and / or any combination thereof. The term "wireless device" encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0046] The RAN 104 may include one or more base stations (not shown). The term "base station" may be used throughout this disclosure to mean and encompass: a Node B (associated with UMTS and / or 3G standards); an evolved Node B (eNB, associated with E-UTRA and / or 4G standards); a remote radio head (RRH); a baseband processing unit coupled to one or more RRHs; a repeater node or relay node used to extend the coverage area of ​​a donor node; a next generation evolved Node B (ng-eNB); a generation Node B (gNB, associated with NR and / or 5G standards); an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard); 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).

[0047] The base stations included in the RAN 104 may include one or more sets of antennas for communicating with the wireless devices 106 over the air interface. For example, one or more of the base stations may include three sets of antennas to control three cells (or sectors) respectively. The size of the cell may be determined by the range at which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. The cells of the base stations may together provide radio coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0048] In addition to three-sector sites, other implementations of the base station are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectorized site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, a baseband processing unit coupled to several remote radio heads (RRHs), and / or a repeater or relay node for extending the coverage area of ​​a donor node. The baseband processing unit coupled to the RRH may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be centralized in a baseband processing unit pool or virtualized. The repeater node may amplify and rebroadcast the radio signal received from the donor node. The relay node may perform the same / similar functions as the repeater node, but may decode the radio signal received from the donor node to eliminate noise before amplifying and rebroadcasting the radio signal.

[0049] The RAN 104 may be deployed as a homogeneous network of macrocell base stations with similar antenna types and similar high levels of transmit power. The RAN 104 may be deployed as a heterogeneous network. In a heterogeneous network, a small cell base station may be used to provide a small coverage area, such as a coverage area that overlaps with a relatively large coverage area provided by a macrocell base station. Small coverage areas may be provided in areas with high data traffic (or so-called "hot spots") or in areas where macrocell coverage is weak. Examples of small cell base stations include, in descending order of coverage area: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0050] The Third Generation Partnership Project (3GPP) was established in 1998 to Figure 1A 3GPP provides global specification standardization for mobile communication networks similar to the mobile communication network 100 in the mobile communication network 100. To date, 3GPP has developed specifications for three generations of mobile networks: the third generation (3G) network known as the Universal Mobile Telecommunications System (UMTS), the fourth generation (4G) network known as the Long Term Evolution (LTE), and the fifth generation (5G) network known as the 5G System (5GS). Embodiments of the present disclosure are described with reference to the RAN of the 3GPP 5G network known as the Next Generation RAN (NG-RAN). These embodiments may be applicable to the RAN of other mobile communication networks, such as Figure 1A The RAN 104 in 5G networks, the RAN of early 3G and 4G networks, and those of yet-to-be-specified future networks (e.g., 3GPP 6G networks). The NG-RAN implements the 5G radio access technology known as New Radio (NR) and may be configured to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0051] Figure 1B Another exemplary mobile communication network 150 in which embodiments of the present disclosure may be implemented is shown. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown in FIG. 1 , the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UE 156). Figure 1A The corresponding components described are implemented and operate in the same or similar manner.

[0052] 5G-CN 152 provides an interface to one or more DNs, such as a public DN (e.g., the Internet), a private DN, and / or an operator's internal DN, to UE 156. As part of the interface function, 5G-CN 152 may set up an end-to-end connection between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CN of the 3GPP 4G network, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 may be defined as network functions that provide services to other network functions via interfaces. The network functions of 5G-CN 152 may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0053] like Figure 1B As shown in FIG. 1 , 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B. For ease of explanation, Figure 1BThey are shown as one component AMF / UPF 158 in FIG. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. UPF 158B can perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification to support routing of service flows to the one or more DNs, user plane quality of service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement and uplink service verification), downlink packet buffering and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected with the one or more DNs, and / or a fulcrum for supporting multi-host PDU sessions. UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and the DN.

[0054] The AMF 158A may perform functions such as: non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policy), network slicing support and / or session management function (SMF) selection. NAS may refer to functions operating between the CN and the UE, and AS may refer to functions operating between the UE and the RAN.

[0055] 5G-CN 152 may include Figure 1B . For example, 5G-CN 152 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).

[0056] The NG-RAN 154 may connect the 5G-CN 152 to the UE 156 through radio communications over an air interface. The NG-RAN 154 may include: one or more gNBs, such as gNB 160A and gNB 160B (collectively referred to as gNB 160); and / or one or more ng-eNBs, such as ng-eNB 162A and ng-eNB 162B (collectively referred to as ng-eNB 162). The gNB 160 and ng-eNB 162 may be more generally referred to as base stations. The gNB 160 and ng-eNB 162 may include one or more groups of antennas for communicating with the UE 156 over the air interface. For example, one or more gNBs in the gNB 160 and / or one or more ng-eNBs in the ng-eNB 162 may include three groups of antennas to control three cells (or sectors) respectively. The cells of gNB 160 and ng-eNB 162 may together provide radio coverage to UE 156 over a wide geographic area to support UE mobility.

[0057] like Figure 1B As shown in FIG. 1 , gNB 160 and / or ng-eNB 162 may be connected to 5G-CN 152 via an NG interface and to other base stations via an Xn interface. The NG and Xn interfaces may be established using a direct physical connection and / or an indirect connection through an underlying transport network such as an Internet Protocol (IP) transport network. gNB 160 and / or ng-eNB 162 may be connected to UE 156 via a Uu interface. For example, Figure 1B As shown in FIG. 1 , gNB 160A may be connected to UE 156A via a Uu interface. NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface may be composed of Figure 1B The network elements in a network are used to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data that the user is interested in. The control plane may process signaling messages that the network elements are interested in.

[0058] The gNB 160 and / or ng-eNB 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by means of one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by means of a NG user plane (NG-U) interface. The NG-U interface may provide delivery of user plane PDUs (e.g., non-guaranteed delivery) between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A by means of a NG control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, delivery of NAS messages, paging, PDU session management, and configuration delivery and / or warning message transmission.

[0059] The gNB 160 may provide NR user plane and control plane protocol terminations to the UE 156 via a Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations to the UE 156A via a Uu interface associated with the first protocol stack. The ng-eNB 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations to the UE 156 via a Uu interface, where E-UTRA refers to a 3GPP 4G radio access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations to the UE 156B via a Uu interface associated with the second protocol stack.

[0060] 5G-CN 152 is described as being configured to handle both NR and 4G radio access. One of ordinary skill in the art will appreciate that it is possible for NR to be connected to a 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 Figure 1B Only one AMF / UPF 158 is shown in the figure, but a gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

[0061] As discussed, Figure 1B The interfaces between network elements in a network (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, while the control plane may process signaling messages of interest to the network elements.

[0062] Figure 2A and Figure 2B Examples of NR user plane and NR control plane protocol stacks for the Uu interface between UE 210 and gNB 220 are shown, respectively. Figure 2A and Figure 2B The protocol stack shown in can be used with e.g. Figure 1B The protocol stacks of the Uu interface between UE156A and gNB 160A shown in are the same or similar.

[0063] Figure 2A An NR user plane protocol stack including five layers implemented in a UE 210 and a gNB 220 is shown. At the bottom of the protocol stack, the physical layer (PHY) 211 and 221 may provide transport services to higher layers of the protocol stack and may correspond to layer 1 of the open system interconnection (OSI) model. The next four protocols above the PHY 211 and 221 include a medium access control layer (MAC) 212 and 222, a radio link control layer (RLC) 213 and 223, a packet data convergence protocol layer (PDCP) 214 and 224, and a 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.

[0064] Figure 3 An example of services provided between protocol layers of the NR user plane protocol stack is shown. Figure 2A and Figure 3 Starting from the top of , SDAPs 215 and 225 can perform QoS flow processing. UE 210 can receive services through a PDU session, which can be a logical connection between UE 210 and a DN. A PDU session can have one or more QoS flows. The UPF of the CN (e.g., UPF 158B) can map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and / or error rate). SDAPs 215 and 225 can perform mapping / demapping between the one or more QoS flows and one or more data radio bearers. The mapping / demapping between the QoS flows and the data radio bearers can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0065] The PDCP 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, may perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and may perform integrity protection to ensure that control messages originate from the intended source. The PDCP 214 and 224 may perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate received packets due to, for example, intra-gNB handovers. The PDCP 214 and 224 may perform packet repetition to increase the likelihood that a packet is received, and remove any duplicate packets at the receiver. Packet repetition may be applicable to services that require high reliability.

[0066] although Figure 3 Not shown, but PDCP 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technology that allows a UE to connect to two cells or more generally to two cell groups: a primary cell group (MCG) and a secondary cell group (SCG). A split bearer is a split bearer when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapped split radio bearers between RLC channels belonging to a cell group.

[0067] RLC 213 and 223 can perform segmentation, retransmission through automatic repeat request (ARQ), and removal of duplicate data units received from MAC 212 and 222, respectively. RLC 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode in which the RLC is operating, the RLC can perform one or more of the functions described. RLC configuration can be based on each logical channel, independent of parameter sets and / or transmission time interval (TTI) duration. As shown in FIG. Figure 3 As shown in FIG. 1 , RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

[0068] The MAC 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing data units belonging to the one or more logical channels into / from a transport block (TB) delivered to / from the PHY 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs with the aid of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MAC 212 and 222 may be configured to perform error correction by hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between logical channels of the UE 210 with the aid of logical channel prioritization, and / or padding. The MAC 212 and 222 may support one or more parameter sets and / or transmission timing. In an example, mapping restrictions in logical channel prioritization may control which parameter sets and / or transmission timings a logical channel may use. Figure 3 As shown, MAC 212 and 222 may provide logical channels as services to RLC 213 and 223 .

[0069] PHY 211 and 221 can perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHY 211 and 221 can perform multi-antenna mapping. Figure 3 As shown in , PHY 211 and 221 may provide one or more transport channels as a service to MAC 212 and 222 .

[0070] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4A The downlink data flow of three IP packets (n, n+1, and m) flowing through the NR user plane protocol stack to generate two TBs at the gNB 220 is shown. The uplink data flow flowing through the NR user plane protocol stack can be the same as Figure 4A The downlink data flow is similar to that depicted in .

[0071] Figure 4A The downlink data flow of starts when SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. Figure 4A In the SDAP header (in Figure 4AThe data unit from / to a higher protocol layer is called a service data unit (SDU) of the lower protocol layer, and the data unit to / from a lower protocol layer is called a protocol data unit (PDU) of the higher protocol layer. Figure 4A As shown in , the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and is the PDU of SDAP 225.

[0072] Figure 4A The remaining protocol layers in can perform their associated functions (e.g., Figure 3 ), add the corresponding headers, and forward their corresponding outputs to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., Figure 4A 222) and forwards its output to MAC 222. MAC 222 may multiplex many RLC PDUs and may attach MAC subheaders to the RLC PDUs to form a transport block. In NR, MAC subheaders may be distributed throughout the MAC PDU, as shown in FIG. Figure 4A In LTE, the MAC subheader can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU subheader can be calculated before assembling the complete MAC PDU.

[0073] Figure 4B An exemplary format of a MAC subheader in a MAC PDU is shown. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originates to assist in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0074] Figure 4B Further shown is a MAC Control Element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B Two MAC CEs are shown inserted into the MAC PDU. Figure 4B) and inserting a MAC CE at the end of a MAC PDU for uplink transmission. MAC CE may be used for in-band control signaling. Exemplary MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those used for PDCP duplicate detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC subheader having a format similar to that described for a MAC SDU may be present before the MAC CE, and the MAC CE may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

[0075] Before describing the NR control plane protocol stack, the mapping between logical channels, transport channels, and physical channels and channel types is first described. One or more of these channels can be used to perform functions associated with the NR control plane protocol stack described later below.

[0076] Figure 5A and Figure 5B The mapping between logical channels, transport channels and physical channels is shown for downlink and uplink respectively. Information is passed through channels between RLC, MAC and PHY of the NR protocol stack. Logical channels can be used between 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 dedicated to a specific UE, or as common logical channels that can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example:

[0077] - Paging Control Channel (PCCH), which is used to carry paging messages used to page UEs whose location is unknown to the network at the cell level;

[0078] - Broadcast Control Channel (BCCH), which is used to carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), which can be used by UEs to obtain information about how a cell is configured and how it operates within the cell;

[0079] - Common Control Channel (CCCH), which is used to carry control messages and random access;

[0080] - a dedicated control channel (DCCH) used to carry control messages to / from a specific UE to configure the UE; and

[0081] - Dedicated Traffic Channel (DTCH), which is used to carry user data to / from a specific UE.

[0082] Transport channels are used between the MAC layer and the PHY layer and can be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example:

[0083] - Paging Channel (PCH), which is used to carry paging messages originating from PCCH;

[0084] - Broadcast Channel (BCH), which is used to carry the MIB from the BCCH;

[0085] - Downlink Shared Channel (DL-SCH), which is used to carry downlink data and signaling messages, including SIBs from BCCH;

[0086] - Uplink Shared Channel (UL-SCH), which is used to carry uplink data and signaling messages; and

[0087] - Random Access Channel (RACH), which is used to allow a UE to contact the network without any previous scheduling.

[0088] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have a set of associated time-frequency resources for carrying information of one or more transport channels. The PHY may generate control information to support low-level operation of the PHY and provide control information to lower levels of the PHY via physical control channels (referred to as L1 / L2 control channels). The set of physical channels and physical control channels defined by NR includes, for example:

[0089] - Physical Broadcast Channel (PBCH), which is used to carry the MIB from the BCH;

[0090] - Physical Downlink Shared Channel (PDSCH), which is used to carry downlink data and signaling messages from DL-SCH and paging messages from PCH;

[0091] - Physical Downlink Control Channel (PDCCH), which is used to carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

[0092] - Physical Uplink Shared Channel (PUSCH), which is used to carry uplink data and signaling messages from the UL-SCH, and in some cases uplink control information (UCI) as described below;

[0093] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, which may include HARQ acknowledgment, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI) and scheduling request (SR); and

[0094] - Physical Random Access Channel (PRACH), which is used for random access.

[0095] Similar to the physical control channel, the physical layer generates physical signals to support the lower-level operations of the physical layer. Figure 5A and Figure 5B As shown in , the physical layer signals defined by NR include: 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 will be described in more detail below.

[0096] Figure 2B An exemplary NR control plane protocol stack is shown. Figure 2B As shown in , 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 protocol stack instead has radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0097] The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 (e.g., AMF 158A) or more generally between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 via signaling messages referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which NAS messages may be transmitted. NAS messages may be transmitted using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0098] The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 or more generally between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 via signaling messages referred to as RRC messages. The RRC messages may be transported between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control plane and user plane data into the same transport block (TB). The RRC 216 and 226 may provide control plane functions such as: broadcast of system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance, and release of an RRC connection between UE 210 and RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of the reporting; detection of radio link failure (RLF) and recovery from radio link failure; and / or NAS messaging. As part of establishing an RRC connection, the RRC 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

[0099] Figure 6 is an example diagram showing the RRC state transition of the UE. The UE can Figure 1A The wireless device 106 depicted in Figure 2A and Figure 2B The UE 210 depicted in FIG. 1 and any other wireless device described in the present disclosure may be the same or similar. Figure 6 As shown in , the UE may be in at least one of three RRC states: RRC connected 602 (eg, RRC_CONNECTED), RRC idle 604 (eg, RRC_IDLE), and RRC inactive 606 (eg, RRC_INACTIVE).

[0100] 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 similar to one of the following: Figure 1A The one or more base stations included in the RAN 104 depicted in FIG. Figure 1B One of the gNB 160 or ng-eNB 162 depicted in FIG. Figure 2A and Figure 2BgNB220 depicted in ; or any other base station described in the present disclosure. A base station connected to a UE may have an RRC context for the UE. 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., involving 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. When in RRC connection 602, the mobility of the UE may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from a serving cell and neighboring cells, and report these measurements to the base station currently serving the UE. The UE's serving base station may request handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 via a connection release procedure 608 , or to RRC inactive 606 via a connection deactivation procedure 610 .

[0101] In RRC idle 604, an RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with a base station. When in RRC idle 604, the UE may be in a sleep state for most of the time (e.g., to save battery power). The UE may wake up periodically (e.g., once in each discontinuous reception 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 connected 602 through a connection establishment procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0102] In RRC Inactive 606, the previously established RRC context is maintained in the UE and the base station. This allows a quick transition to RRC Connected 602 with reduced signaling overhead compared to the transition from RRC Idle 604 to RRC Connected 602. While in RRC Inactive 606, the UE may be in a sleep state, and the mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connected 602 through a Connection Resumption Procedure 614, or to RRC Idle 604 through a Connection Release Procedure 616, which may be the same or similar to the Connection Release Procedure 608.

[0103] The RRC state may 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 allow the network to notify the UE of an event via a paging message without broadcasting the paging message over the entire mobile communication network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE at a cell group level, so that the paging message may be broadcast over a cell in the cell group in which the UE currently resides instead of over the entire mobile communication network. The mobility management mechanism used for RRC idle 604 and RRC inactive 606 tracks the UE at a cell group level. These mobility management mechanisms may do so using groups of different granularities. For example, there may be three levels of cell grouping granularity: a single cell; a cell within a RAN area identified by a RAN area identifier (RAI); and a cell within a group of RAN areas referred to as tracking areas and identified by a tracking area identifier (TAI).

[0104] Tracking areas may be used to track UEs at the CN level. A CN (e.g., CN 102 or 5G-CN 152) may provide a list of TAIs associated with UE registration areas to a UE. If a UE moves through cell reselection to a cell associated with a TAI that is not included in the list of TAIs associated with a UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0105] The RAN area may be used to track the UE at the RAN level. For a UE in the RRC inactive 606 state, a RAN notification area may be assigned to the UE. The RAN notification area may include one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves to a cell not included in the RAN notification area assigned to the UE through cell reselection, the UE may perform a notification area update on the RAN to update the RAN notification area of ​​the UE.

[0106] The base station storing the RRC context for the UE or the last serving base station of the UE may be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least during the period of time that the UE remains in the RAN notification area of ​​the anchor base station and / or during the period of time that the UE remains in RRC inactivity 606.

[0107] gNBs, such as Figure 1BThe gNB 160 in the embodiment of the present invention 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 the F1 interface. The gNB-CU can include RRC, PDCP, and SDAP. The gNB-DU can include RLC, MAC, and PHY.

[0108] In NR, physical signals and physical channels (about Figure 5A and Figure 5B Discussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data through F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols) and divided into F parallel symbol streams. The F parallel symbol streams can be treated as if they are in the frequency domain and used as input to the inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols at a time (one source symbol from each of the F parallel symbol streams), 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 can be F time domain samples representing the sum of the F orthogonal subcarriers. The F time domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using the FFT block before being processed by the IFFT block. This operation produces a discrete Fourier transform (DFT) precoded OFDM symbol and can be used by the UE in the uplink to reduce the peak to average power ratio (PAPR). The FFT block can be used to perform inverse processing on the OFDM symbol at the receiver to restore the data mapped to the source symbol.

[0109] Figure 7 An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown. An NR frame may be identified by a system frame number (SFN). The SFN may repeat for a period of 1024 frames. As shown, a NR frame may have a duration of 10 milliseconds (ms) and may include 10 subframes of duration 1 ms. A subframe may be divided into slots, which may include, for example, 14 OFDM symbols per slot.

[0110] The duration of a time slot may depend on the parameter set of the OFDM symbol used for the time slot. In NR, flexible parameter sets are supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mm-wave range). Parameter sets may be defined in terms of subcarrier spacing and cyclic prefix duration. For parameter sets in NR, the subcarrier spacing may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines parameter sets 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.

[0111] A slot may have a fixed number of OFDM symbols (eg, 14 OFDM symbols). Parameter sets with higher subcarrier spacing have shorter slot durations and correspondingly more slots per subframe. Figure 7 The transmission structure of the time slot duration and each subframe time slot associated with the parameter set is shown (for ease of explanation, Figure 7 Parameter sets with subcarrier spacing of 240kHz are not shown in Figure 1). Subframes in NR can be used as a time reference independent of the parameter set, while slots can be used as the unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from the slot duration and start at any OFDM symbol and continue to transmit as many symbols as needed. These partial slot transmissions can be called mini-slots or sub-slot transmissions.

[0112] Figure 8 An exemplary configuration of a time slot in the time and frequency domain of an NR carrier is shown. The time slot includes a resource element (RE) and a resource block (RB). RE is the smallest physical resource in NR. RE spans one OFDM symbol in the time domain through one subcarrier in the frequency domain, such as Figure 8 As shown in Figure 1. RB spans twelve consecutive REs in the frequency domain, as Figure 8 As shown. The NR carrier can be limited to a width of 275RB or 275×12=3300 subcarriers. If this restriction is used, the NR carrier can be limited to 50MHz, 100MHz, 200MHz and 400MHz for subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively, where the 400MHz bandwidth can be set based on the 400MHz bandwidth limitation for each carrier.

[0113] Figure 8A single parameter set is shown used across the entire bandwidth of the NR carrier. In other example configurations, multiple parameter sets may be supported on the same carrier.

[0114] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Moreover, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, the UE may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE plans to receive. This is referred to as bandwidth adaptation.

[0115] NR defines bandwidth parts (BWPs) to support UEs that cannot receive the full carrier bandwidth and supports bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. The UE may be configured (e.g., via the RRC layer) with 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). At a given time, one or more of the configured BWPs for a serving cell may be active. The one or more BWPs may be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0116] For unpaired spectrum, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP. For unpaired spectrum, the UE may expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

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

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

[0119] One or more BWP indicator fields may be provided in downlink control information (DCI). The value of the BWP indicator field may indicate which BWP in a set of configured BWPs is the active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions.

[0120] The base station may semi-statically configure a default downlink BWP for the UE within the set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP to 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.

[0121] The base station may configure the BWP inactivity timer value for the PCell for the UE. The UE may start or restart the BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer in the following circumstances: (a) when the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or (b) when the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer towards expiration (e.g., an increment from zero to the BWP inactivity timer value, or a decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0122] In an example, the base station may semi-statically configure the UE with 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 that the second BWP is the active BWP and / or in response to expiration of a BWP inactivity timer (e.g., when the second BWP is the default BWP).

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

[0124] Fig. 9 An example of bandwidth adaptation using three configured BWPs of an NR carrier is shown. A UE configured with the three BWPs can switch from one BWP to another at a switching point. Fig. 9 In the example shown in , the BWPs include: BWP 902, whose bandwidth is 40 MHz and subcarrier spacing is 15 kHz; BWP 904, whose bandwidth is 10 MHz and subcarrier spacing is 15 kHz; and BWP 906, whose bandwidth is 20 MHz and subcarrier spacing is 60 kHz. BWP 902 may be the initial active BWP, and BWP 904 may be the default BWP. The UE may switch between BWPs at a switching point. Fig. 9 904. In the example of , the UE may switch from BWP 902 to BWP 904 at switch point 908. The switch at switch point 908 may occur for any suitable reason, such as in response to expiration of a BWP inactivity timer (indicating a switch to a default BWP) and / or in response to receiving a DCI indicating that BWP 904 is an active BWP. The UE may switch from active BWP 904 to BWP 906 at switch point 910 in response to receiving a DCI indicating that BWP 906 is an active BWP. The UE may switch from active BWP 906 to BWP 904 at switch point 912 in response to expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating that BWP 904 is an active BWP. The UE may switch from active BWP 904 to BWP 902 at switch point 914 in response to receiving a DCI indicating that BWP 902 is an active BWP.

[0125] If the UE is configured for a secondary cell with a default downlink BWP and timer values ​​from the set of configured downlink BWPs, the UE procedures for switching the BWP on the secondary cell may be the same / similar to those on the primary cell. For example, the UE may use the timer values ​​and default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values ​​for the primary cell.

[0126] To provide higher data rates, two or more carriers may be aggregated and transmitted to / from the same UE simultaneously using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CC). When CA is used, there are many serving cells for the UE, one serving cell per CC. CCs may have three configurations in the frequency domain.

[0127] Fig. 10A Three CA configurations with two CCs are shown. In the intra-band contiguous configuration 1002, the two CCs are aggregated in the same frequency band (Band A) and are located directly adjacent to each other within the frequency band. In the intra-band non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (Band A) and are separated by a gap in the frequency band. In the inter-band configuration 1006, the two CCs are located in frequency bands (Band A and Band B).

[0128] In an example, up to 32 CCs may be aggregated. Aggregated CCs may have the same or different bandwidths, subcarrier spacings, and / or duplex schemes (TDD or FDD). A serving cell for a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may optionally be configured for the serving cell. For example, the ability to aggregate more downlink carriers than uplink carriers may be useful when the UE has more data traffic in the downlink than in the uplink.

[0129] When CA is used, one of the aggregated cells for the UE may be referred to as a primary cell (PCell). The PCell may be a serving cell to which the UE initially connects at RRC connection establishment, reestablishment and / or handover. The PCell may provide NAS mobility information and security input to the UE. The UE may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as a downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as an uplink primary CC (UL PCC). Other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCell may be configured after the PCell is configured for the UE. For example, the SCell may be configured via an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to the SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as an uplink secondary CC (UL SCC).

[0130] The configured SCell for a UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmission on the SCell. Figure 4B The MAC CE may be used to activate and deactivate the configured SCells. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) are activated or deactivated for the UE. The configured SCells may be deactivated in response to the expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0131] The downlink control information of a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant, which is called self-scheduling. The DCI of a cell can be transmitted on another cell, which is called cross-carrier scheduling. Uplink control information for aggregated cells (e.g., HARQ confirmation and channel state feedback, such as CQI, PMI and / or RI) can be transmitted on the PUCCH of the PCell. For a large number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. The cell can be divided into multiple PUCCH groups.

[0132] Fig. 10B An example of how aggregated cells can be configured into one or more PUCCH groups is shown. PUCCH group 1010 and PUCCH group 1050 may include one or more downlink CCs, respectively. Fig. 10BIn the example of , PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 in this example includes 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 SCell (PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) may be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) may be transmitted in the uplink of PSCell 1061. In the example, if Fig. 10B If the aggregated cell depicted in FIG. 1 is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell transmits UCI associated with a downlink CC, and the PCell may become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061, overload can be prevented.

[0133] A physical cell ID and a cell index may be assigned to a cell comprising a downlink carrier and an optional uplink carrier. The physical cell ID or cell index may identify a downlink carrier and / or an uplink carrier of a cell, for example, depending on the context in which the physical cell ID is used. The physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. The cell index may be determined using an RRC message. In the present disclosure, the physical cell ID may be referred to as a carrier ID, and the cell index may be referred to as a carrier index. For example, when the present disclosure relates to a first physical cell ID of a first downlink carrier, the present disclosure may mean that the first physical cell ID is used for a cell comprising the first downlink carrier. The same / similar concepts may apply, for example, to carrier activation. When the present disclosure indicates that a first carrier is activated, the present specification may mean that a cell comprising the first carrier is activated.

[0134] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an example, the HARQ entity can operate on the serving cell. A transport block can be generated based on the assignment / grant of each serving cell. A transport block and potential HARQ retransmissions of the transport block can be mapped to a serving cell.

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

[0136] Fig.11A An example of the structure and location of SS / PBCH blocks is shown. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as Fig.11A As shown). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). Bursts may be limited to half a frame (e.g., the first half frame with a duration of 5 ms). It should be understood that Fig.11A are examples, and these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, burst position within a frame) may be configured based on, for example: the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; a parameter set or subcarrier spacing for the cell; configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume the subcarrier spacing of the SS / PBCH blocks based on the carrier frequency being monitored unless the radio network configures the UE to assume a different subcarrier spacing.

[0137] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as Fig.11A ) and may span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., spanning the next 3 OFDM symbols) and may span 240 subcarriers.

[0138] The UE may not know the location of the SS / PBCH blocks in the time and frequency domains (for example, when the UE is searching for cells). In order 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 (for example, 20ms), the UE may search for the PSS at different frequency positions within the carrier, as indicated by the synchronization raster. If the PSS is found at a certain position in the time and frequency domains, the UE may determine the location of the SSS and PBCH based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block may be a cell definition SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, cell selection / search and / or reselection may be based on the CD-SSB.

[0139] The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine the physical cell identifier (PCI) of the cell based on the sequence of the PSS and SSS, respectively. The UE may determine the location of the frame boundary of the cell based on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it has been transmitted according to a transmission pattern in which the SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0140] The PBCH may use QPSK modulation and may use forward error correction (FEC). FEC may use polarity coding. One or more symbols spanned by the PBCH may carry one or more DMRS for demodulating the PBCH. The PBCH may include an indication of the current system frame number (SFN) of the cell and / or an SS / PBCH block timing index. These parameters may contribute to the time synchronization of the UE with the base station. The PBCH may include a master information block (MIB) for providing one or more parameters to the UE. The MIB may be used by the UE to locate the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a system information block type 1 (SIB1). SIB1 may contain information required for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH that may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE may point to a frequency. The UE may search for SS / PBCH blocks at the frequency to which the UE is pointing.

[0141] The UE may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index are quasi-co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH block transmissions with different SS / PBCH block indices.

[0142] SS / PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​a cell). In an example, 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.

[0143] In an example, within a frequency range of a carrier, a base station may transmit multiple SS / PBCH blocks. In an example, a first PCI of a first SS / PBCH block of the multiple SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block of the multiple SS / PBCH blocks. PCIs of SS / PBCH blocks transmitted in different frequency positions may be different or the same.

[0144] The CSI-RS may be transmitted by a base station and used by a UE to obtain channel state information (CSI). The base station may configure the UE with one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure the UE with one or more CSI-RSs of the same / similar CSI-RS. The UE may measure the one or more CSI-RSs. The UE may estimate the downlink channel state and / or generate a CSI report based on the measurement of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use the feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

[0145] The base station may semi-statically configure the UE with one or more CSI-RS resource sets. The CSI-RS resources may be associated with positions and periodicity in the time and frequency domains. The base station may selectively activate and / or deactivate CSI-RS resources. The base station may indicate to the UE that the CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

[0146] The base station may configure the UE to report CSI measurement values. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with timing and / or periodicity of multiple CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure the configured CSI-RS resources and provide a CSI report related to the measurement value. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically and selectively activate or deactivate periodic reporting. The base station may configure the UE with a CSI-RS resource set and a CSI report using RRC signaling.

[0147] The CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbol for downlink CSI-RS and control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbol for downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRBs configured for the SS / PBCH blocks.

[0148] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, the downlink DMRS can be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS mode. The frontload DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols for PDSCH. The DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, the DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, the DMRS configuration can support up to 4 orthogonal downlink DMRS ports per UE. The radio network may (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, where the DMRS position, DMRS pattern and / or scrambling sequence may be the same or different. The base station may transmit the downlink DMRS and the corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRS to perform consistent demodulation / channel estimation on the PDSCH.

[0149] In an example, a transmitter (e.g., a base station) may use a precoder matrix for a portion of a 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 precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used throughout a set of PRBs. The set of PRBs may be represented as a precoding resource block group (PRG).

[0150] The PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer in the one or more layers of the PDSCH. The higher layers may configure up to 3 DMRS for the PDSCH.

[0151] The downlink PT-RS may be transmitted by a base station and used by a UE for phase noise compensation. Whether a downlink PT-RS exists may depend on an RRC configuration. The presence and / or type of a downlink PT-RS may be configured based on a UE-specific configuration using a combination of RRC signaling and / or an association with one or more parameters for other purposes (e.g., a modulation and coding scheme (MCS)) that may be indicated by a DCI. When configured, the dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters including at least an MCS. The NR network may support multiple PT-RS densities defined in the time / frequency domain. When present, the frequency domain density may be associated with at least one configuration of the scheduled bandwidth. The UE may use 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. The downlink PT-RS may be limited to the scheduled time / frequency duration of the UE. The downlink PT-RS may be transmitted on a symbol to facilitate phase tracking at the receiver.

[0152] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS to consistently demodulate one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS 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-load DMRS mode. The front-load DMRS may be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to be transmitted at one or more symbols of the PUSCH and / or PUCCH. The base station may semi-statically configure the UE with the number (e.g., maximum number) of front-load DMRS symbols for the PUSCH and / or PUCCH, and the UE may use the front-load DMRS symbol to schedule a single-symbol DMRS and / or a dual-symbol DMRS. NR networks may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS positions, DMRS patterns, and / or scrambling sequences of the DMRS may be the same or different.

[0153] The PUSCH may include one or more layers, and the UE may transmit at least one symbol having a DMRS present on a layer in the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.

[0154] Depending on the RRC configuration of the UE, an uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not exist. The presence and / or type of the uplink PT-RS can be configured based on UE-specific configuration through a combination of RRC signaling and / or one or more parameters for other purposes (e.g., modulation and coding scheme (MCS)) indicated by the DCI. When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least the MCS. The radio network can support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS can be limited to the scheduled time / frequency duration of the UE.

[0155] The UE may transmit an SRS to a base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE may allow the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station may use the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. The applicability of the SRS resource set may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, the SRS resources in the SRS resource set in the one or more SRS resource sets (e.g., having the same / similar time domain behavior, periodic, aperiodic, etc.) may be transmitted at a certain time (e.g., at the same time). The UE may transmit one or more SRS resources in the SRS resource set. The NR network may support aperiodic, periodic, and / or semi-persistent SRS transmission. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format may be used for the UE to select at least one configured SRS resource set from one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in the same time slot, the UE may be configured to transmit SRS after transmission of PUSCH and corresponding uplink DMRS.

[0156] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: an SRS resource configuration identifier; the number of SRS ports; the time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or non-periodic SRS); time slot, mini-slot, and / or subframe level periodicity; time slots of periodic and / or non-periodic SRS resources; the number of OFDM symbols in the SRS resources; the starting OFDM symbol of the SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0157] The antenna ports are defined such that the channel through which a symbol on the antenna port is communicated can be inferred from the channel through which another symbol on the same antenna port is communicated. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel used to communicate the second symbol on the antenna port from the channel used to communicate the first symbol on the antenna port (e.g., fading gain, multipath delay, etc.). If one or more large-scale properties of the channel through which the first symbol on the first antenna port is communicated can be inferred from the channel through which the second symbol on the second antenna port is communicated, the first antenna port and the second antenna port can be referred to as quasi-co-located (QCLed). The one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0158] Channels using beamforming require beam management. Beam management may include beam measurement, beam selection, and beam indication. 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 and generate beam measurement reports based on downlink reference signals (e.g., channel state information reference signals (CSI-RS)). After setting up an RRC connection with a base station, the UE may perform a downlink beam measurement procedure.

[0159] Fig. 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domain is shown. Fig. 11BThe squares shown in the figure may represent resource blocks (RBs) within the bandwidth of the cell. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters may be configured for the CSI-RS resource configuration through higher layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identifier, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in a subframe), CSI-RS subframe configuration (e.g., subframe position, offset and periodicity in a radio frame), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid) and / or other radio resource parameters.

[0160] Fig. 11B The three beams shown may be configured for a UE in a UE-specific configuration. Fig. 11B Three beams (beam #1, beam #2, and beam #3) are illustrated in FIG. 1 , and more or fewer beams may be configured. CSI-RS 1101 may be allocated to beam #1, which may be transmitted in one or more subcarriers in the RB of the first symbol. CSI-RS 1102 may be allocated to beam #2, which may be transmitted in one or more subcarriers in the RB of the second symbol. CSI-RS 1103 may be allocated to beam #3, which may be transmitted in one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in the same RB (e.g., those subcarriers not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam of another UE. By using time domain multiplexing (TDM), a beam for a UE may be configured so that the beam for the UE uses symbols from beams of other UEs.

[0161] CSI-RS, such as Fig. 11BThose shown in (e.g., CSI-RS1101, 1102, 1103) may be transmitted by a base station and used by a UE for one or more measurement values. For example, a UE may measure a 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 value to the network (e.g., via one or more base stations) based on the reporting configuration. In the example, the base station may determine one or more transmission configuration indication (TCI) states including multiple reference signals based on the reported measurement results. In the example, 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 having a receive (Rx) beam determined based on the one or more TCI states. In the example, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE may determine the spatial domain filter of the transmission (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam-corresponding capability, the UE 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 to the UE by the base station. The base station may select and indicate the uplink beam of the UE based on measurements of one or more SRS resources transmitted by the UE.

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

[0163] Fig. 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurements of transmit (Tx) beams of a transmit reception point (TRP) (or multiple TRPs), for example to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top and bottom rows of P1, respectively). Beamforming at the TRP can include Tx beam sweeping for a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of P1 and P2). Beamforming at the UE can include Rx beam sweeping for a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements of Tx beams of a TRP (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or the base station may perform procedure P2 using a smaller beam set than the beam set 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 P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0164] Fig. 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable a base station to perform measurements on a UE's Tx beams, for example, to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, Rx beam sweeping from a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station can include, for example, Rx beam sweeping from a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of U1 and U2). Procedure U2 can be used to enable a base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or base station can perform procedure U2 using a smaller beam set than the beam set 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 its Tx beam when the base station uses a fixed Rx beam.

[0165] The UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE may detect a beam failure based on a determination that the quality of the beam-pair link of the associated control channel is unsatisfactory (e.g., having an error rate above an error rate threshold, a received signal power below a received signal power threshold, expiration of a timer, etc.).

[0166] The UE may measure the quality of a beam-to-link using one or more reference signals (RS), the one or more reference signals including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRS). The quality of a beam-to-link may be based on one or more of the following: a block error rate (BLER), an RSRP value, a signal-to-interference-plus-noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and / or a CSI value measured on an RS resource. The base station may indicate that the RS resource is quasi-co-located (QCLed) with one or more DM-RS of a channel (e.g., a control channel, a shared data channel, etc.). When the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from a transmission to the UE via the RS resource are similar or identical to the channel characteristics from a transmission to the UE via the channel, the RS resource and the one or more DMRS of the channel may be QCLed.

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

[0168] Fig.13A A four-step contention-based random access procedure is shown.Before initiating the procedure, the base station may transmit a configuration message 1310 to the UE. Fig.13AThe procedure shown includes the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg3 1313, and Msg 4 1314. Msg 1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg2 1312 may include and / or be referred to as a random access response (RAR).

[0169] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The 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 the RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE may determine the reception timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0170] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that can be used to transmit Msg 11311. The one or more PRACH opportunities may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between: (a) one or more PRACH opportunities, and (b) one or more reference signals. The one or more RACH parameters may indicate an association between: (a) one or more preambles, and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunity and / or the number of preambles mapped to the SS / PBCH block.

[0171] The one or more RACH parameters provided in the configuration message 1310 may be used to determine the uplink transmission power of Msg 1 1311 and / or Msg3 1313. For example, the one or more RACH parameters may indicate a reference power for preamble transmission (e.g., a received target power and / or an initial power for preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate: a power ramp step size; a power offset between SSB and CSI-RS; a power offset between transmissions of Msg 1 1311 and Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplementary uplink (SUL) carrier).

[0172] Msg 1 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 configure one or more preamble groups (e.g., group A and / or group B). The preamble group may include one or more preambles. The UE may determine the preamble group based on the path loss measurement value and / or the size of Msg 3 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 having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by the RRC message, the UE may select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0173] The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a path loss measurement, an RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a 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 the one or more RACH parameters to configure an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the UE. If the association is configured, the UE may determine the preamble included in Msg 1 1311 based on the association. Msg 1 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 selecting a preamble and for determining a PRACH opportunity. One or more RACH parameters (eg, ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and the one or more reference signals.

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

[0175] Msg 2 1312 received by the UE may include a RAR. In some scenarios, Msg 2 1312 may include multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a random access RNTI (RA-RNTI). Msg 2 1312 may indicate that Msg 1 1311 is received by the base station. Msg 2 1312 may include a time alignment command that may be used by the UE to adjust the transmission timing of the UE, a scheduling grant for transmitting Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg 2 1312. The UE may determine when to start the time window based on the PRACH opportunity used by the UE to transmit the preamble. For example, the UE may start a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH opportunity starting from the end of the preamble transmission). The one or more symbols may be determined based on a parameter set. The PDCCH may be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a radio network temporary identifier (RNTI). The RNTI may be used depending on one or more events that initiate a random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a time slot index; a frequency domain index; and / or a UL carrier indicator of a PRACH opportunity. Examples of RA-RNTIs may be as follows:

[0176] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0177] Wherein s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≤s_id<14), t_id may be the index of the first time slot of the PRACH opportunity in the system frame (e.g., 0≤t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≤f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for a NUL carrier and 1 for a SUL carrier).

[0178] The UE may transmit Msg 3 1313 in response to successfully receiving Msg 2 1312 (e.g., using the resources identified in Msg 2 1312). Msg 3 1313 may be used, for example, Fig.13A Contention resolution in a contention-based random access procedure as shown in . In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to the UE. If the multiple UEs interpret the RAR as corresponding to themselves, a conflict may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) may be used to increase the likelihood that a UE does not mistakenly use an identifier of another UE. To perform contention resolution, the UE may include a device identifier in Msg 3 1313 (e.g., if a C-RNTI is assigned, the TC-RNTI included in Msg 2 1312 and / or any other suitable identifier).

[0179] Msg 4 1314 may be received after or in response to the transmission of Msg 3 1313. If a C-RNTI is included in Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If a unique C-RNTI of the UE is detected on the PDCCH, it is determined that the random access procedure is successfully completed. If a TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in an RRC_IDLE state or is not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identifier MAC CE that matches or otherwise corresponds to the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.

[0180] The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., a random access procedure) may be supported in an uplink carrier. For example, a base station may configure two separate RACH configurations for the UE: one for the SUL carrier and the other for the NUL carrier. For random access in a cell configured with a SUL carrier, the network may indicate which carrier (NUL or SUL) to use. For example, if the measured quality of one or more reference signals is below a broadcast threshold, the UE may determine the SUL carrier. The uplink transmissions (e.g., Msg1 1311 and / or Msg 3 1313) of the random access procedure may remain on the selected carrier. In one or more cases, the UE may switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE may determine and / or switch an uplink carrier for Msg 1 1311 and / or Msg 3 1313 based on channel clarity assessment (eg, listen before talk).

[0181] Fig. 13B The two-step contention-free random access procedure is shown. Fig.13A Similar to the four-step contention-based random access procedure shown, the base station may transmit a configuration message 1320 to the UE before the procedure is initiated. The configuration message 1320 may be similar to the configuration message 1310 in some aspects. Fig. 13B The procedure shown includes the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 may be similar in some respects to Fig.13A As shown in Msg 1 1311 and Msg 2 1312. Fig.13A and Fig. 13B It will be appreciated that the contention-free random access procedure may not include messages similar to Msg 3 1313 and / or Msg 4 1314.

[0182] Can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover Fig. 13B For example, the base station may indicate or assign a preamble to be used for Msg 1 1321 to the UE. The UE may receive an indication of the preamble (eg, ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0183] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for the RAR. 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 in the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. Fig. 13B In the contention-free random access procedure shown, the UE may determine that the random access procedure is successfully completed after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, if the PDCCH transmission is addressed to the C-RNTI, the UE may determine that the random access procedure is successfully completed. For example, if the UE receives a RAR including a preamble identifier corresponding to a preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with a preamble identifier, the UE may determine that the random access procedure is successfully completed. The UE may determine that the response is an indication of a confirmation of the SI request.

[0184] Fig. 13C Another two-step random access procedure is shown. Fig.13A and Fig. 13B Similar to the random access procedure shown, the base station may transmit a configuration message 1330 to the UE before the procedure is initiated. Configuration message 1330 may be similar to configuration message 1310 and / or configuration message 1320 in some aspects. Fig. 13C The procedure shown includes the transmission of two messages: Msg A 1331 and Msg B 1332.

[0185] Msg A 1331 may be transmitted by the UE in an uplink transmission. Msg A 1331 may include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. Transport block 1342 may include Fig.13A The transmission block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, etc.). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include the same content as the content of Msg 3 1313 shown in FIG. Fig.13A and Fig. 13B Msg 2 1312 (eg, RAR) and / or Fig.13A The content of Msg 4 1314 shown is similar and / or identical.

[0186] The UE can initiate a call for licensed spectrum and / or unlicensed spectrum. Fig. 13C The UE may determine whether to initiate a two-step random access procedure based on one or more factors. The one or more factors may be: the radio access technology being used (e.g., LTE, NR, etc.); whether the UE has a valid TA; the cell size; the RRC state of the UE; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0187] The UE may determine the radio resources and / or uplink transmission power of the preamble 1341 and / or the transport block 1342 included in the Msg A 1331 based on the two-step RACH parameters included in the configuration message 1330. The RACH parameters may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control of the preamble 1341 and / or the transport block 1342. The time-frequency resources (e.g., PRACH) used for transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) used for transmission of the transport block 1342 may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the reception timing and downlink channel for monitoring and / or receiving the Msg B 1332.

[0188] The transmission block 1342 may include data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier; a timing high-level command; a power control command; an uplink grant (e.g., a radio resource assignment and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if the following conditions exist: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 matches the identifier of the UE in Msg A 1331 (e.g., transmission block 1342).

[0189] The UE and the base station may exchange control signaling. The 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). The 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.

[0190] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling grant indicating uplink radio resources and / or transport format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in a payload transmitted by the 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.

[0191] The base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of UEs). Scrambling the CRC parity bits with the identifier may include a Modulo-2 addition (or an 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).

[0192] DCI can be used for different purposes. The purpose can 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) can indicate paging information and / or system information change notification. The P-RNTI can be predefined as hexadecimal "FFFE". A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. The SI-RNTI can be predefined as hexadecimal "FFFF". A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate a dynamically scheduled unicast transmission and / or the triggering of a PDCCH ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to Fig.13AThe other RNTIs configured by the base station to the UE may include: configured scheduling RNTI (CS-RNTI), transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), transmission power control SRS RNTI (TPC-SRS-RNTI), interruption RNTI (INT-RNTI), time slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

[0193] Depending on the purpose and / or content of the DCI, the base station may transmit DCI with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in 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 of PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in 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 of PDSCH in 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 indication to a UE group. DCI format 2_1 may be used to notify a UE group of physical resource blocks and / or OFDM symbols, where the UE may assume that no transmission to the UE is expected. DCI format 2_2 may be used to transmit a transmission power control (TPC) command for PUCCH or PUSCH. DCI formats 2_3 may be used to transmit a set of TPC commands for SRS transmission by one or more UEs. DCI formats for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

[0194] After scrambling the DCI with the RNTI, the base station may process the DCI with channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the coded and modulated DCI on resource elements used for and / or configured for PDCCH. Based on the payload size of the DCI and / or the coverage of the base station, the base station may transmit the DCI via a PDCCH occupying multiple consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. CCE may include the number of resource element groups (REGs) (e.g., 6). REG may include a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements may be based on the mapping of CCEs and REGs (e.g., CCE to REG mapping).

[0195] Fig.14A An example of a CORESET configuration for a bandwidth portion is shown. A base station may transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources in which a UE attempts to decode DCI using one or more search spaces. A base station may configure a CORESET in the time-frequency domain. Fig.14A In the example of FIG. 1401 , the first CORESET 1401 and the second CORESET 1402 appear at the first symbol in the time slot. The first CORESET 1401 overlaps the second CORESET 1402 in the frequency domain. The third CORESET 1403 appears at the third symbol in the time slot. The fourth CORESET 1404 appears at the seventh symbol in the time slot. The CORESETs may have different numbers of resource blocks in the frequency domain.

[0196] Fig. 14B An example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing is shown. The CCE to REG mapping can be an interlaced mapping (e.g., for the purpose of providing frequency diversity) or a non-interlaced mapping (e.g., for the purpose of facilitating interference coordination and / or frequency selective transmission of control channels). The base station can perform different or the same CCE to REG mapping for different CORESETs. A CORESET can be associated with the CCE to REG mapping through RRC configuration. A CORESET can be configured with antenna port quasi-co-location (QCL) parameters. The antenna port QCL parameters can indicate the QCL information of the demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

[0197] The base station may transmit an RRC message including configuration parameters of one or more CORESETs and one or more search space sets to the UE. The configuration parameters may indicate an association between a search space set and a CORESET. The search space set may include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: the number of PDCCH candidates to be monitored for each aggregation level; the PDCCH monitoring period and the PDCCH monitoring type; one or more DCI formats to be 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 the common search space set may be predefined and known to the UE. The set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

[0198] like Fig. 14B As shown, the UE may determine the time-frequency resources of the CORESET based on the RRC message. The UE may determine the CCE to REG mapping of the CORESET based on the configuration parameters of the CORESET (e.g., interlaced or non-interlaced and / or mapping parameters). The UE may determine the number of search space sets configured on the CORESET based on the RRC message (e.g., up to 10). 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 for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates, which have possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the UE-specific search space) and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The UE may determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambled bits of the CRC parity bits of the DCI matching the RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink grants, power control, time slot format indications, downlink preemption, etc.).

[0199] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling transmission may include a hybrid automatic repeat request (HARQ) confirmation for the received DL-SCH transport block. The UE may transmit the HARQ confirmation after receiving the DL-SCH transport block. The uplink control signaling may include channel state 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 (e.g., including multiple antennas and beamforming schemes) for downlink transmission. The uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ confirmation (HARQ-ACK), CSI report, SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via PUCCH using one of several PUCCH formats.

[0200] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. If the transmission exceeds one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the wireless device may use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 may occupy between four and fourteen OFDM symbols and may include two or fewer bits. If four or more symbols are transmitted and the number of HARQ-ACK / SR bits is one or two, the UE may use PUCCH format 1. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. If the transmission exceeds one or two symbols and the number of UCI bits is two or more, the UE may use PUCCH format 2. PUCCH format 3 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources do not include orthogonal cover codes, the UE may use PUCCH format 3. PUCCH format 4 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources include orthogonal cover codes, the UE may use PUCCH format 4.

[0201] The base station may transmit configuration parameters of multiple PUCCH resource sets to the UE using, for example, an RRC message. The multiple PUCCH resource sets (e.g., up to four sets) may be configured on the uplink BWP of the cell. The PUCCH resource set may be configured with: a PUCCH resource set index; multiple PUCCH resources having PUCCH resources identified by a PUCCH resource identifier (e.g., pucch-Resourceid); and / or multiple (e.g., maximum number) UCI ​​information bits that the UE may 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 (e.g., HARQ-ACK, SR, and / or CSI) based on the total bit length of the UCI information bits. If the total bit length of the UCI information bits is two or less, the UE may select the first PUCCH resource set with a PUCCH resource set index equal to "0". If the total bit length of the UCI information bits is greater than two and less than or equal to the first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configured value and less than or equal to the second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3".

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

[0203] Fig.15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure is shown. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as Figure 1A The mobile communication network 100 shown, Figure 1B The mobile communication network 150 shown or any other communication network. Fig.15 Only one wireless device 1502 and one base station 1504 are shown in FIG. 1 , but it should be understood that the mobile communication network may include more than one UE and / or more than one base station, which have the same Fig.15 Configurations the same or similar to those shown.

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

[0205] In the downlink, data to be sent from base station 1504 to wireless device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 via, for example, a core network. In the uplink, data to be sent from wireless device 1502 to base station 1504 may be provided to processing system 1518 of wireless device 1502. Processing system 1508 and processing system 1518 may implement layer 3 and layer 2 OSI functions to process data for transmission. Layer 2 may include, for example, information about Figure 2A , Figure 2B , Figure 3 and Figure 4A Layer 3 may include the following: Figure 2B RRC layer.

[0206] After processing by processing system 1508, data to be transmitted to wireless device 1502 may be provided to transmission processing system 1510 of base station 1504. Similarly, after processing by processing system 1518, data to be transmitted to base station 1504 may be provided to transmission processing system 1520 of wireless device 1502. Transmission processing system 1510 and transmission processing system 1520 may implement layer 1 OSI functions. Layer 1 may include information about Figure 2A , Figure 2B , Figure 3 and Figure 4A For transmission processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple-input multiple-output (MIMO) or multi-antenna processing, etc.

[0207] At base station 1504, receive processing system 1512 may receive uplink transmissions from wireless device 1502. At wireless device 1502, receive processing system 1522 may receive downlink transmissions from base station 1504. Receive processing system 1512 and receive processing system 1522 may implement layer 1 OSI functions. Layer 1 may include information about Figure 2A , Figure 2B , Figure 3 and Figure 4A For reception 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, etc.

[0208] like Fig.15 As shown, the wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to perform 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 examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0209] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or codes that may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed herein. Fig.15 Not shown, transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that may be executed to perform one or more of their respective functions.

[0210] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0211] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 may include software and / or hardware that provides features and / or functions, such as a speaker, a microphone, a keyboard, a display, a touch pad, a power supply, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle) and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, etc.). The processing system 1508 and / or the processing system 1518 may 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 to the one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from the power source and / or can be configured to distribute power to other components in 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. The processing system 1508 and / or the processing system 1518 can be connected to the GPS chipset 1517 and the GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographical location information of the wireless device 1502 and the base station 1504, respectively.

[0212] Fig.16AAn exemplary structure for uplink transmission is shown. The baseband signal representing the physical uplink shared channel can perform one or more functions. The one or more functions may include at least one of the following: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulated symbols to one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; and the like. In the example, when transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. In the example, when transform precoding is not enabled, the uplink transmission can be performed by Fig.16A Generate a CP-OFDM signal for uplink transmission. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0213] Fig. 16B An exemplary structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. 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 for an antenna port. Filtering may be employed prior to transmission.

[0214] Fig. 16C An exemplary structure for downlink transmission is shown. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may include: scrambling coded bits in a codeword to be transmitted on a physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols on layers for transmission on antenna ports; mapping complex-valued modulation symbols for antenna ports to resource elements; generating complex-valued time-domain OFDM signals for antenna ports; and the like. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0215] Fig.16D Another exemplary structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex valued OFDM baseband signal at an antenna port. Filtering may be employed prior to transmission.

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

[0217] Once started, a timer can start running and continue running until it stops or until it expires. If the timer is not running, it can be started, or if it is running, it can be restarted. A timer can be associated with a value (e.g., a timer can start or restart from a certain value, or can start from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer stops or expires (e.g., due to BWP switching). A timer can be used for a time period / window of a measurement process. When the specification refers to implementations and procedures related to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of the multiple ways of implementing the timer can be used for a time period / window of a measurement procedure. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In an example, instead of the start and expiration of the random access response window timer, the time difference between two timestamps can be used. When the timer is restarted, the measurement process of the time window can be restarted. Other exemplary embodiments can be provided to restart the measurement of the time window.

[0218] The UE may receive an RRC release message including a suspension configuration parameter (or a suspension indication), wherein the suspension configuration parameter includes a resume flag and an NCC value. Based on the suspension configuration parameter, the UE may suspend the RRC connection. Based on the RRC release message, the UE may transition from the RRC connection state to an RRC inactive state or an RRC idle state. Based on the suspended RRC connection in the RRC idle state, the UE is in an RRC idle state with a suspended RRC connection.

[0219] The RRC connection establishment may include the establishment of a signaling radio bearer 1 (SRB1). The base station may complete the RRC connection establishment before completing the establishment of the S1 connection (e.g., before receiving UE context information from a core network entity (e.g., AMF)). In the initial stage of the RRC connection, access stratum (AS) security is not activated. In the initial stage of the RRC connection, the base station may configure the UE to perform measurement reporting. After AS security activation is successful, the UE may send a corresponding measurement report. When AS security is activated, the UE may receive or accept a handover message (e.g., a handover command).

[0220] The base station may initiate the establishment of SRB2 and DRB after the initial (AS) security activation procedure has been initiated. For example, the base station may initiate the establishment of SRB2 and DRB before receiving confirmation of the initial security activation from the UE. The base station may apply encryption and integrity protection to the RRC (connection) reconfiguration message, where the RRC reconfiguration message is used to establish SRB2 and DRB. The base station may release the RRC connection based on the failure of the initial security activation and / or radio bearer establishment. For example, the security activation and DRB establishment may be triggered by a joint S1 procedure, where the joint S1 procedure may not support partial success. For SRB2 and DRB, (AS) security may be activated from the beginning. For example, the base station may not establish these bearers before activating security.

[0221] The UE-RRC layer can initiate an RRC connection establishment procedure, an RRC connection recovery procedure, or an RRC connection re-establishment procedure. Based on initiating the RRC connection establishment procedure or the RRC connection recovery procedure, the UE may perform one or more procedures, wherein the one or more procedures include at least one of the following: performing a unified access control procedure (e.g., access barring check) on the access attempt of the RRC establishment / recovery procedure on the serving cell; applying default configuration parameters and the configuration / parameters provided by SIB1 (e.g., based on the allowed access attempt, applying the default configuration and the configuration / parameters provided by SIB1); for example, based on the access attempt being allowed, performing sending a random access preamble to the serving cell; sending an RRC request message to the serving cell (e.g., based on determining that the random access response is successfully received, sending an RRC request message to the serving cell 0; starting a timer based on sending the RRC request message; receiving an RRC response message or an RRC rejection message from the serving cell (e.g., in response to the RRC request message); or sending an RRC completion message (e.g., in response to receiving the RRC response message, sending an RRC completion message). For the RRC connection reestablishment procedure, the UE may not perform a unified access procedure (e.g., access barring check) on the access attempt of the RRC reestablishment procedure.

[0222] Based on initiating the RRC connection reestablishment procedure, if one or more prohibition timers T309 are running, the UE may stop one or more prohibition timers T309 for all access categories. Based on stopping one or more prohibition timers T309, the UE may determine that the prohibition of all access categories is being alleviated. The UE may perform the RRC connection reestablishment procedure based on the prohibition of all access categories being alleviated. For example, based on the prohibition for all access categories being alleviated, the UE may send an RRC reestablishment request without prohibition.

[0223] In order to initiate the RRC connection establishment / recovery / re-establishment procedure, the UE-RRC layer can use the parameters in the received SIB1. The UE-RRC layer can use the L1 parameter value and time alignment timer in SIB1. The UE-RRC layer can use the UAC prohibition information in SIB1 to perform the unified access control procedure. Based on the unified access control procedure, the UE-RRC layer can determine whether the access attempts of these RRC procedures are prohibited or allowed. Based on determining that the access attempt is allowed, the UE-RRC layer can determine to send an RRC request message to the base station. The UE-NAS layer may or may not provide the S-TMSI as the UE identity. The UE-RRC layer can set the UE identity in the RRC request message.

[0224] For the RRC setup request message, the UE in the RRC idle state may initiate an RRC connection establishment procedure. Based on the initiation of the RRC connection establishment procedure, if the UE-NAS layer provides the S-TMSI, the UE-RRC layer in the RRC idle state may set the UE identity to the S-TMSI. Otherwise, the UE-RRC layer in the RRC idle state may extract a 39-bit random value and set the UE identity to the random value.

[0225] For the RRC recovery request message, a UE in an RRC inactive or RRC idle state and with a suspended RRC connection may initiate an RRC connection recovery procedure. A UE in an RRC inactive or idle state may initiate an RRC connection procedure to resume (suspend) an RRC connection; or perform / initiate UP small data transmission. Based on initiating the RRC connection recovery procedure, the UE may select an access category based on the triggering conditions of the RRC connection recovery procedure, and perform a unified access control procedure based on the access category. Based on the unified access control procedure, the UE may regard the access attempt of the RRC connection recovery procedure as allowed. Based on regarding the access attempt as allowed, the UE may apply the default L1 parameter values ​​as specified in the corresponding physical layer specification, 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, start timer T319 and initiate the transmission of the RRC recovery request message.

[0226] Based on initiating the transmission of the RRC recovery request message, in addition to the primary cell group configuration parameters, MR-DC related configuration parameters (e.g., secondary cell group configuration parameters) and PDCP configuration parameters, the UE can recover the stored configuration parameters and the stored security keys from the (stored) UE inactive AS context. The configuration parameters may include at least one of the following: the C-RNTI used in the source PCell, the global cell identity and physical cell identity of the source PCell, and all other parameters configured except the parameters within the synchronized reconfiguration and serving cell configuration common parameters in the SIB. Based on the current (recovered) K associated with the stored NCC value gNB or next hop (NH) parameter, the UE can derive the new key (K gNB Based on the new key of the base station, the UE can derive the security keys for integrity protection and encryption of RRC signaling (for example, K RRCenc and K RRCint ) and the security keys for integrity protection and encryption of user plane data (e.g., K UPint and K UPenc ). Configuration-based algorithms and K RRCint and K UPint , the UE may configure the lower layers (e.g., PDCP layer) to apply integrity protection to all radio bearers except SRB0. Based on the configured algorithm and K RRCenc and K UPenc , the UE may configure lower layers (eg, PDCP layer) to apply encryption to all radio bearers except SRB0.

[0227] Based on the security key, the UE-RRC layer in the RRC inactive or idle state can set the recovery MAC-I value to the 16 least significant bits of the MAC-I calculated based on the variable recovery MAC input, the security key for integrity protection of the RRC layer in the UE inactive AS context, the previously configured integrity protection algorithm, and other security parameters (e.g., count, bearer, and direction). The variable recovery MAC input may include at least one of the following: a physical cell identifier of the source cell; a C-RNTI of the source cell; and a cell identifier of the target cell (e.g., a selected cell), wherein the cell identifier is a cell identifier in a system information block (e.g., SIB1) of the target cell (e.g., the selected cell). The UE-RRC layer in the RRC inactive or idle state can reestablish the PDCP entity for one or more bearers. The UE-RRC layer can recover one or more bearers. For example, based on recovering the RRC connection, the UE-RRC layer can recover SRB1. Based on performing UP small data transmission, the UE-RRC layer can recover one or more SRBs and DRBs. The UE can set the content of the RRC recovery request message. The RRC recovery request message may include at least one of a recovery identifier, a recovery MAC-I, or a recovery reason. The recovery reason may include at least one of emergency, high priority access, mt access, mo signaling, mo data, mo voice call, mo sms, ran update, mps priority access, and mcs priority access.

[0228] For the RRC reestablishment request message, the UE in the RRC connected state may initiate an RRC connection reestablishment procedure. Based on initiating the RRC connection reestablishment procedure, the UE-RRC layer in the RRC connected state may include the physical cell identifier and short MAC-I of the source PCell in the RRC reestablishment message. The UE-RRC layer in the RRC connected state may set the short MAC-I to the 16 least significant bits of the MAC-I calculated based on the variable short MAC input, the security key and integrity protection algorithm of the RRC layer for integrity protection (which is used in the source PCell or in the PCell in which the reestablishment trigger occurs), and other security parameters (e.g., count, bearer, and direction). The variable short MAC input may include at least one of the following: the physical cell identifier of the source PCell; the C-RNTI of the source PCell; and the cell identifier of the target cell (e.g., the selected cell), wherein the cell identifier is the cell identifier in the system information block (e.g., SIB1) of the target cell (e.g., the selected cell). The UE-RRC layer in the RRC connected state may reestablish the PDCP entity and the RLC entity for SRB1, and apply the default SRB1 configuration parameters for SRB1. The UE-RRC layer in the RRC connected state may configure a lower layer (eg, a PDCP layer) to suspend integrity protection and ciphering of SRB1 and resume SRB1.

[0229] The UE-RRC layer may send an RRC request message to a lower layer (eg, a PDCP layer, an RLC layer, a MAC layer, and / or a PHY layer) for transmission, wherein the RRC request message may be an RRC setup request message, an RRC recovery request message, or an RRC reestablishment message.

[0230] The UE-RRC layer may receive an RRC setup message in response to an RRC recovery request message or an RRC reestablishment request message. Based on the RRC setup message, the UE-RRC layer may discard any stored AS context, suspension configuration parameters, and current AS security context. The UE-RRC layer may release the radio resources of all established RBs except SRB0, including releasing the associated PDCP entity and RLC entity of SDAP. The UE-RRC layer may release the RRC configuration except for the default L1 parameter value, the default MAC cell group configuration, and the CCCH configuration. The UE-RRC layer may indicate the fallback of the RRC connection to the upper layer (e.g., the NAS layer). If the timer T380 is running as a periodic RNA update timer, the UE-RRC layer may stop the timer T380.

[0231] The UE-RRC layer may receive an RRC setup message in response to an RRC setup request message, an RRC recovery request message, or an RRC reestablishment request message. The RRC setup message may include a cell group configuration parameter and a radio bearer configuration parameter. The radio bearer configuration parameter may include at least one of a signaling bearer configuration parameter, a data radio bearer configuration parameter, and / or a security configuration parameter. The security configuration parameter may include a security algorithm configuration parameter and a key usage indication, which indicates whether the radio bearer configuration parameter uses a primary key or a secondary key. The signaling radio bearer configuration parameter may include one or more signaling radio bearer configuration parameters. Each signaling radio configuration parameter may include at least one of an SRB identifier, a PDCP configuration parameter, a reestablishment PDCP indication, and / or a discard PDCP indication. The data radio bearer configuration parameter may include one or more data radio bearer configuration parameters. Each data radio configuration parameter may include at least one of a drb identifier, a PDCP configuration parameter, a SDAP configuration parameter, a reestablishment PDCP indication, and / or a restoration PDCP indication. The radio bearer configuration in the RRC setup message may include a signaling radio configuration parameter for 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 prohibition timer and the waiting timer to facilitate the cell to send the RRC setup message. Based on receiving the RRC setup message, the UE-RRC layer may perform one or more of the following: transition to the RRC connected state; stop the cell reselection procedure; regard the current cell to which the UE sends the RRC setup message as a PCell or / and send an RRC setup complete message.

[0232] The UE-RRC layer may receive an RRC resume message in response to an RRC resume request message. Based on the RRC resume message, the UE-RRC layer may discard the UE inactive AS context and release the suspension configuration parameters except the RAN notification area information. Based on the configuration parameters in the RRC resume message, the UE-RRC layer may perform cell group configuration, radio bearer configuration, security key update procedure, and measurement configuration procedure. Based on receiving the RRC resume message, the UE-RRC layer may perform one or more of the following: indicating to the upper layer (e.g., NAS layer) that the suspended RRC connection has been resumed; resuming SRB2, all DRBs, and measurements; entering the RRC connected state; stopping the cell (re)selection procedure; treating the current cell that sends the RRC resume message as a PCell or / and sending an RRC resume complete message by setting the content of the RRC resume complete message.

[0233] The UE-RRC layer in an RRC inactive or idle state may receive an RRC reject message in response to an RRC setup request message or an RRC recovery request message. The RRC reject message may include a waiting timer. Based on the waiting timer, the UE-RRC layer may start timer T302, where the timer value is set to the waiting timer. Based on the RRC reject message, the UE-RRC layer may notify the upper layer (e.g., the UE-NAS layer) about the failure to set up an RRC connection or restore an 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 notify the upper layer (e.g., the NAS layer) that access prohibition applies to all access categories except categories '0' and '2'.

[0234] The UE-RRC layer in the RRC inactive or idle state may receive an RRC reject message in response to the RRC resume request message. Based on the RRC reject message, the UE-RRC layer may discard the current security key. If the recovery is triggered due to RNA update, the UE-RRC layer may set the pending RNA update value to true.

[0235] The UE-RRC layer in the RRC inactive or idle state may 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 may change the cell on which the UE resides and stop the RRC procedure. The UE-RRC layer may notify the upper layer (e.g., NAS layer) about the failure of the RRC procedure.

[0236] A UE in an RRC idle or RRC inactive state can perform one of two procedures (such as initial cell selection and cell selection) by utilizing stored information. When the UE has not yet stored the cell information of the selected PLMN, the UE can perform initial cell selection. Otherwise, the UE can perform cell selection by utilizing stored information. For initial cell selection, the UE can scan all RF channels in the NR band based on its ability to find a suitable cell. Based on the results of the scan, the UE can search for the strongest cell on each frequency. The UE can select a cell as a suitable cell. For cell selection by utilizing stored information, the UE may need stored frequency information, and optionally information about cell parameters from a previously received measurement control information element or from a previously detected cell. Based on the stored information, if the UE finds a suitable cell, the UE can search for a suitable cell and select a suitable cell. If the UE does not find a suitable cell, the UE can perform initial cell selection.

[0237] The base station may configure cell selection criteria for cell selection. The UE may seek to identify a suitable cell for cell selection. A suitable cell is a cell in which the UE can camp to obtain normal service. A suitable cell is a cell that satisfies the following conditions: (1) the measured cell attributes satisfy the cell selection criteria; (2) the cell PLMN is the selected PLMN, a registered or equivalent PLMN; (3) the cell is not prohibited or reserved; and (4) the cell is not part of a tracking area in the "roaming prohibited tracking area" list. The RRC layer in the UE may notify the NAS layer in the UE of cell selection and reselection results based on changes in received system information related to the NAS. For example, the cell selection and reselection results may be a cell identity, a tracking area code, and a PLMN identity.

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

[0239] The radio link failure may be a radio link failure of a primary cell of a base station. The base station may send a synchronized reconfiguration to a UE in an RRC connected state in an RRC message. The synchronized reconfiguration may include a reconfiguration timer (e.g., T304). Based on receiving the synchronized reconfiguration, the UE may start the reconfiguration timer and perform a synchronized reconfiguration (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 a mobility from NR command message to the UE in an RRC connected state. Based on receiving the mobility from the NR command message, the UE may perform a handover from NR to a cell using other RATs (e.g., E-UTRA). The UE may determine a mobility failure from NR based on satisfying at least one of the conditions: if the UE does not successfully establish a connection to the target radio access technology; or if the UE cannot comply with any part of the configuration included in the mobility from the NR command message; or if there is a protocol error in the inter-RAT information included in the mobility from the NR message.

[0240] Based on the detection of the failure, the UE in the RRC connected state can initiate an RRC connection reestablishment procedure. Based on the initiation of the RRC connection reestablishment procedure, the UE can start the timer T311, suspend all radio bearers except SRB0, and reset the MAC (layer). Based on the initiation of the RRC connection reestablishment procedure, the UE in the RRC connected state can release the MCG SCell, release the special cell (SpCell) configuration parameters and the multi-radio dual connection (MR-DC) related configuration parameters. For example, based on the initiation of the RRC connection reestablishment procedure, the UE can release the master cell group configuration parameters.

[0241] Based on initiating the RRC connection reestablishment procedure, the UE in the RRC connection state can perform a cell selection procedure. Based on the cell selection procedure, the UE can select a cell. Based on selecting a suitable cell, the UE in the RRC connection state can stop timer 311 and start timer T301. Based on selecting a suitable cell, the UE in the RRC connection state can stop the prohibition timer T390 for all access categories. Based on stopping the prohibition timer T390, the UE in the RRC connection state can consider alleviating the prohibition of all access categories for the cell. Based on selecting a cell, the UE in the RRC connection state can apply the default L1 parameter values ​​in addition to the parameters provided in SIB1, apply the default MAC cell group configuration, apply the CCCH configuration, apply the timer alignment timer in SIB1, and initiate the transmission of the RRC reestablishment request message. Based on initiating transmission of the RRC re-establishment request message, the UE (RRC layer) in the RRC connected state 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, resume SRB1 and submit the RRC re-establishment request message to the lower layer (PDCP layer) for transmission. The RRC re-establishment request message may include at least one of the C-RNTI used in the source PCell, the physical cell identity (PCI) of the source PCell, a short MAC-I, or a re-establishment cause. The re-establishment cause may include at least one of a reconfiguration failure, a handover failure, or other failures.

[0242] The UE in the RRC connected state may stop the timer T301 based on the reception of the RRC response message in response to the RRC reestablishment request message. The RRC response message may include at least one of an RRC reestablishment message, an RRC setup message, or an RRC reestablishment rejection message. When the selected cell becomes unsuitable, the UE in the RRC connected state may stop the timer T301.

[0243] Based on the cell selection procedure triggered by initiating the RRC connection reestablishment procedure, the UE in the RRC connected state may select an inter-RAT cell. Based on the selection of the inter-RAT cell, the UE in the RRC connected state (UE-AS layer) may transition to the RRCIDLE state, and may provide the release cause "RRC connection failure" to the upper layer (UE-NAS layer) of the UE.

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

[0245] Based on receiving the release cause "RRC connection failure", when the UE has no pending signaling and user data pending, the UE in RRC idle state (UE-NAS layer) can perform the NAS signaling connection recovery procedure. Based on performing the NAS signaling connection recovery procedure, the UE in RRC idle state can initiate the registration procedure by sending a registration request message to the AMF.

[0246] Upon receiving the release cause "RRC Connection Failure", the UE in RRC Idle state (UE-NAS layer) may perform a service request procedure by sending a Service Request message to the AMF when the UE has pending signalling or pending user data.

[0247] Based on receiving the RRC Reestablishment Request message, the target base station may check whether the UE context of the UE is locally available. Based on the UE context being locally unavailable, the target base station may perform a UE context retrieval procedure by sending a UE context retrieval request message to the source base station (last serving base station) of the UE.

[0248] For the RRC connection reestablishment procedure, the retrieve UE context request message may include at least one of a UE context ID, an integrity protection parameter, or a new cell identifier. The UE context ID may include at least one of: a C-RNTI containing the RRC reestablishment request message; and a PCI of the source PCell (the last serving PCell). The integrity protection parameter for the RRC reestablishment procedure may be a short MAC-I. The new cell identifier may be an identifier of a target cell, where the target cell is a cell for which reestablishment of the RRC connection has been requested. The new cell identifier is a cell identifier in a system information block (e.g., SIB1) of the target cell (e.g., the selected cell).

[0249] For the RRC connection reestablishment procedure, upon receiving the retrieve UE context request message, the source base station may check the retrieve UE context request message. If the source base station is able to identify the UE context by means of the UE context ID, and is able to successfully verify the UE by means of the integrity protection contained in the retrieve UE context request message, and decides to provide the UE context to the target base station, the source base station may respond to the target base station with a retrieve UE context response message. If the source base station cannot identify the UE context by means of the UE context ID, or if the integrity protection contained in the retrieve UE context request message is not valid, the source base station may respond to the target base station with a retrieve UE context failure message.

[0250] For the RRC connection reestablishment procedure, the retrieve UE context response message may include at least one of the Xn Application Protocol (XnAP) ID of the target base station, the XnAP ID of the source base station, a globally unique AMF identifier (GUAMI), or UE context information (e.g., UE context information retrieve UE context response). The UE context information may include at least one of an NG-C UE associated signaling reference, UE security capabilities, AS security information, UE aggregate maximum bit rate, a list of PDU sessions to be set, an RRC context, a mobility restriction list, or an index to a RAT / frequency selection priority. The NG-C UE associated signaling reference may be an NG application protocol ID assigned at the AMF of the UE on the NG-C connection with the source base station. The AS security information may include a security key (K gNB ) and next hop link count (NCC) value. The PDU session list to be set may include PDU session resource related information used at the UE context in the source base station. PDU session resource related information may include PDU session ID, PDU session resource aggregation maximum bit rate, security indication, PDU session type, or QoS flow list to be set. The security indication may include a user plane integrity protection indication and a confidentiality protection indication, which respectively indicate the requirements for user plane (UP) integrity protection and encryption for the corresponding PDU session. The security indication may also include an indication of whether UP integrity protection is applied to the PDU session, an indication of whether UP encryption is applied to the PDU session, and at least one of the maximum integrity protection data rate values ​​(uplink and downlink) for each UE of the integrity protection DRB. The PDU session type may indicate at least one of Internet Protocol version 4 (IPv4), IPv6, IPv4v6, Ethernet, or unstructured. The QoS flow list to be set may include at least one of a QoS flow identifier, a QoS flow level QoS parameter (QoS parameter to be applied to the QoS flow), or a bearer identifier.

[0251] For the RRC connection reestablishment procedure, the retrieval UE context failure message may include at least the XnAP ID of the target base station and a cause value.

[0252] For the RRC connection reestablishment procedure, upon receiving the retrieve UE context response message, the target base station may send an RRC reestablishment message to the UE. The RRC reestablishment message may include at least a network hop link count (NCC) value.

[0253] Upon receiving the RRC reestablishment message, the UE may determine the current K value associated with the NCC value. gNB or next hop (NH) parameters to derive a new security key (K gNB Based on the new security key of the base station and the previously configured integrity protection algorithm, the UE can derive the security key (K RRCint ) and the security key (K UPint Based on the new security key of the base station and the previously configured encryption algorithm, the UE can derive the security key (K RRCenc ) and the security key (K UPenc ). Based on K RRCint Based on the previously configured integrity protection algorithm, the UE can verify the integrity protection of the RRC reestablishment message. Based on the verification failure, the UE (UE-AS layer) can enter the RRC IDLE state and provide the release reason "RRC connection failure" to the upper layer of the UE (UE-NAS layer). Based on the verification success, the UE can be configured to use the previously configured integrity protection algorithm and K RRCint To restore the integrity protection of SRB1, and configure it based on the previously configured encryption algorithm and K RRCenc To restore the encryption of SRB1. The UE may send an RRC reestablishment completion message to the target base station.

[0254] Based on receiving the retrieval UE context failure message, the target base station may send an RRC release message to the UE. For example, based on the retrieval UE context failure message including the RRC release message, the target base station may send an RRC release message to the UE. Based on receiving the retrieval UE context failure message, the target base station may send an RRC setup message or an RRC rejection message. Based on receiving the retrieval UE context failure message, the target base station may not send any response message to the UE.

[0255] Fig.17An example of an RRC connection reestablishment procedure is shown. A UE in an RRC connected state may send and receive data to / from a first base station (e.g., a source base station) via cell 1, where cell 1 is a primary cell (PCell) of the first base station. The UE may detect a failure in connection with the first base station. Based on the failure, the UE may initiate an RRC reestablishment procedure. Based on initiating the RRC connection reestablishment procedure, the UE may start a timer T311, suspend all radio bearers except SRB0, and / or reset the MAC (layer). Based on initiating the RRC connection reestablishment procedure, the UE may release the MCG SCell, release the special cell (SpCell) configuration parameters, and the multi-radio dual connection (MR-DC) related configuration parameters. Based on initiating the RRC connection reestablishment 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 suitable cell. Based on selecting a suitable cell, the UE may stop timer T311 and start timer T301. Based on selecting a suitable cell, if one or more prohibition timers T309 are running, the UE may stop one or more prohibition timers T309 for all access categories. Based on stopping one or more prohibition timers T309, the UE may consider alleviating prohibition of all access categories for the cell. Based on selecting a cell, the UE may apply default L1 parameter values ​​other than the parameters provided in SIB1, apply a default MAC cell group configuration, apply a CCCH configuration, apply a timer alignment timer in SIB1, and initiate transmission of an RRC reestablishment request message. The RRC reestablishment message may include at least one of the C-RNTI used in the source PCell (e.g., cell 1), the physical cell identity (PCI) of the source PCell, a short MAC-I, or a reestablishment cause. Based on initiating transmission of the RRC reestablishment request message, the UE (RRC layer) may reestablish the PDCP of SRB1, reestablish 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, resume SRB1 and submit the RRC reestablishment request message to the lower layer (PDCP layer) for transmission. Based on initiating transmission of the RRC reestablishment request message, the UE may send an RRC reestablishment request message to the second base station via cell 2. Based on receiving the RRC reestablishment request message, the second base station may check whether the UE context of the UE is locally available. Based on the UE context being unavailable locally, the second base station may perform a retrieval UE context procedure by sending a retrieve UE context request message to the source base station of the UE. The retrieve UE context request message may include at least one of the following: a UE context ID; an integrity protection parameter; or a new cell identifier.The UE context ID may include at least one of the following: a C-RNTI containing an RRC reestablishment request message; and a PCI of a source PCell (the last serving PCell). The integrity protection parameter of the RRC reestablishment procedure may be a short MAC-I. The new cell identifier may be an identifier of a target cell, where the target cell is a cell that has requested to reestablish an RRC connection. The new cell identifier is a cell identifier in a system information block (e.g., SIB1) of a target cell (e.g., a selected cell). Based on receiving a retrieve UE context request message, the source base station may check the retrieve UE context request message. If the source base station is able to identify the UE context with the aid of a C-RNTI, and is able to successfully verify the UE with the aid of a short MAC-I, and decides to provide the UE context to the second base station, the source base station may respond to the second base station with a retrieve UE context response message. The retrieve UE context response message may include at least a GUAMI or UE context information. Based on receiving the retrieve UE context response message, the second base station may send an RRC reestablishment message to the UE. The RRC reestablishment message may include a network hop link count (NCC) value. Based on receiving the RRC reestablishment message, the UE may be based on the current K associated with the NCC value. gNB or next hop (NH) parameters to derive a new security key (K gNB ). Based on the new security key of the base station (K gNB ) and the previously configured security algorithm, the UE can derive the security keys for integrity protection and encryption of the RRC signaling (for example, K RRCint and K RRCenc ) and the security keys for integrity protection and encryption of user plane (UP) data (e.g., K UPint and K UPenc ). Security key (K RRCint ), the UE can verify the integrity protection of the RRC reestablishment message. Based on the successful verification, the UE can be configured to use the previously configured integrity protection algorithm and K RRCint to restore integrity protection for one or more bearers (e.g., signaling radio bearers or RRC messages) and is configured based on a previously configured encryption algorithm and K RRCencTo restore encryption for one or more bearers. The second base station may send a first RRC reconfiguration message. The RRC first reconfiguration message may include SpCell configuration parameters. Based on receiving the SpCell configuration parameters, the UE may initiate transmission and reception of data to / from the second base station. The UE may send an RRC reconstruction completion message to the second base station. The RRC reconstruction completion message may include a measurement report. Based on receiving the measurement report, the second base station may determine to configure the SCell and / or the secondary cell group (e.g., SCG or PSCell). Based on the determination, the second base station may send a second RRC reconfiguration message including SCell configuration parameters and / or MR-DC related configuration parameters. Based on receiving the second RRC reconfiguration message, the UE may transmit and receive data via the SCell and / or SCG.

[0256] The RRC reconfiguration message may include at least one of a cell group configuration parameter of the MCG and / or SCG, a radio bearer configuration parameter, or an AS security key parameter.

[0257] The target base station may receive the RRC recovery request message. Based on receiving the RRC recovery request message, the target base station may check whether the UE context of the UE is locally available. Based on the UE context being locally unavailable, the target base station may perform a retrieval UE context procedure by sending a retrieve UE context request message to a source base station (last serving base station) of the UE. The retrieve UE context request message may include at least one of a UE context ID, an integrity protection parameter, a new cell identifier, or a recovery cause, wherein the recovery cause is in the RRC recovery request message.

[0258] For the RRC connection recovery procedure, based on receiving the Retrieve UE Context Request message, the source base station may check the Retrieve UE Context Request message. If the source base station is able to identify the UE context with the aid of the UE Context ID, and is able to successfully authenticate the UE with the aid of the integrity protection contained in the Retrieve UE Context Request message, and decides to provide the UE context to the target base station, the source base station may respond to the target base station with a Retrieve UE Context Response message. If the source base station cannot identify the UE context with the aid of the UE Context ID, or if the integrity protection contained in the Retrieve UE Context Request message is not valid, or if the source base station decides not to provide the UE context to the target base station, the source base station may respond to the target base station with a Retrieve UE Context Failure message.

[0259] For the RRC connection recovery procedure, the retrieval UE context failure message may include at least the XnAPID of the target base station, an RRC release message or a cause value.

[0260] For the RRC connection recovery procedure, based on receiving the retrieve UE context response message, the target base station may send an RRC recovery message to the UE. The RRC recovery message may include at least one of a radio bearer configuration parameter, a cell group configuration parameter of an MCG and / or an SCG, a measurement configuration parameter, or an sk counter, wherein the sk counter is used to gNB The security key of the secondary base station is exported.

[0261] Based on receiving the retrieval UE context failure message, the target base station may send an RRC release message to the UE. For example, based on the retrieval UE context failure message including the RRC release message, the target base station may send an RRC release message to the UE. Based on receiving the retrieval UE context failure message, the target base station may send an RRC setup message or an RRC rejection message. Based on receiving the retrieval UE context failure message, the target base station may not send any response message to the UE.

[0262] Fig.18 An example of an RRC connection recovery procedure is shown. A UE in an RRC connected state may transmit and receive data to / from a first base station (source base station) via cell 1. The first base station may determine to convert the UE in an RRC connected state to an RRC inactive state. Based on the determination, the base station may send an RRC release message including a suspension configuration parameter. Based on receiving the RRC release message including the suspension configuration parameter, the UE may transfer the current security key (e.g., K gNB and K RRCintKey) and current configuration parameters are stored in the UE inactive AS context. For example, the UE may store some current configuration parameters. The stored (current) configuration parameters may be at least one of the following: robust header compression (ROHC) state; QoS flow to DRB mapping rules; C-RNTI used in the source PCell; global cell identity and physical cell identity of the source PCell; and all other parameters configured except for the parameters within the synchronized reconfiguration and serving cell configuration common parameters in the SIB. The robust header compression (ROHC) state may include the ROHC state of all PDCP entities (or all bearers), where each PDCP entity (or each bearer) of each bearer may have one ROHC state. The QoS flow to DRB mapping rules may be QoS flow to DRB mapping rules for all data radio bearers (DRBs), where each DRB may have one QoS flow to DRB mapping rule. Based on receiving an RRC release message including the suspension configuration parameter, the UE may suspend all SRBs and DRBs except SRB0. Based on receiving the RRC release message including the suspension configuration parameters, the UE may start timer T380, enter the RRC inactive state, and perform a cell selection procedure. Based on the cell selection procedure, the UE may select cell 2 of the second base station (target base station). The UE in the RRC inactive state may initiate an RRC connection recovery procedure. The UE may perform a unified access control procedure. Based on the unified access control procedure, the UE may regard the access attempt of the RRC connection recovery procedure as allowed. The UE may apply the default L1 parameter values ​​as specified in the corresponding physical layer specification, 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, start timer T319 and initiate the transmission of an RRC recovery request message. Based on initiating the transmission of the RRC recovery request message, the UE may recover the stored configuration parameters and the stored security keys from the (stored) UE inactive AS context. For example, in addition to the primary cell group configuration parameters, MR-DC related configuration parameters (e.g., secondary cell group configuration parameters), and PDCP configuration parameters, the UE may restore the stored configuration parameters and the stored security keys (e.g., K gNB and K RRCint ). Based on the current (recovered) K associated with the stored NCC value gNB or next hop (NH) parameter, the UE can derive the new key (K gNB Based on the new key of the base station, the UE can derive the security keys for integrity protection and encryption of RRC signaling (for example, K RRCenc and K RRCint) and the security keys for integrity protection and encryption of user plane data (e.g., K UPint and K UPenc ). Configuration-based algorithms and K RRCint and K UPint , the UE (RRC layer) can configure the lower layers (e.g., PDCP layer) to apply integrity protection to all radio bearers except SRB0. Based on the configured algorithm and K RRCenc and K UPenc , the UE may configure a lower layer (e.g., a 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 the integrity protection and / or encryption, the UE may be able to transmit and receive data to / from the second base station. The UE may transmit and receive data to / from the second base station using the restored configuration parameters. Based on initiating the transmission of an RRC recovery request message, the UE may reestablish the PDCP entity for one or more bearers, restore one or more bearers, and submit the RRC recovery request message to the lower layer. Based on receiving the RRC recovery request message, the second base station may check whether the UE context of the UE is locally available. Based on the UE context being locally unavailable, the second base station may perform a retrieval UE context procedure by sending a retrieval UE context request message to the first base station (the last serving base station) of the UE. The retrieval UE context request message may include at least one of the following: a recovery identifier; a recovery MAC-I; or a recovery reason. Based on receiving the retrieval UE context request message, the first base station may check the retrieval UE context request message. If the first base station is able to identify the UE context by means of the UE context ID, and is able to successfully verify the UE by means of the recovery MAC-I, and decides to provide the UE context to the second base station, the first base station may respond to the second base station with a retrieve UE context response message. Based on receiving the retrieve UE context response message, the second base station may send an RRC recovery message to the UE. Based on receiving the RRC recovery message, the UE may recover the primary cell group configuration parameters, secondary cell group configuration parameters, and PDCP configuration parameters in the UE inactive AS context. Based on recovering the primary cell group configuration parameters and / or secondary cell group configuration parameters, the UE may configure the SCell of the MCG and / or SCG by configuring the lower layers to treat the recovered MCG and / or SCG SCell as being in an inactive state, discard the UE inactive AS context, and release the suspension configuration parameters. The UE may transmit and receive data via the SCell and / or SCG.

[0263] When a UE in an RRC idle state is resuming a suspended RRC connection and at least one of the conditions is met, the UE may use early security reactivation, wherein the condition may include: based on satisfying the UP EDT condition, the UE is initiating (UP) a small data transfer; based on satisfying the UP CG condition, the UE initiates (UP) a small data transfer (SDT) procedure using a configured grant (CG) (e.g., preconfigured uplink resources / grant, PUR); the UE is resuming an RRC connection suspended in 5G-CN; and the UE supports early security reactivation, the system information block includes a support indication for early security reactivation, and the UE has a stored value of NCC (next hop link count) provided in an RRC release message, the RRC release message includes a suspension configuration parameter (or suspension indication) during a previous suspension procedure. Resuming a suspended RRC connection may include at least one of the following: initiating an RRC connection resumption procedure; and transmitting an RRC resumption request message.

[0264] A UE in RRC idle state may initiate an RRC connection resumption procedure to resume a suspended RRC connection. Based on using early security reactivation, the UE may resume the PDCP state and re-establish the PDCP entity for all SRBs and all DRBs, and resume all SRBs and all DRBs.

[0265] A UE in an RRC inactive or idle state may send an RRC request message. Based on sending the RRC request message, the UE (UE-RRC layer) may start an RRC timer (e.g., T300 or T319). A UE in an RRC inactive or idle state may receive an RRC response message in response to the RRC request message. Based on receiving the RRC response message, the UE in an RRC inactive or idle state may stop the RRC timer.

[0266] When the RRC timer is running, a UE in RRC inactive or idle state may detect a failure to resume a (suspended) RRC connection. The failure may include at least one of the following: expiration of the RRC timer; cell (re)selection; receipt of an RRC reject message; and integrity check failure of SRB1 or SRB2.

[0267] The UE in the RRC idle state may initiate an RRC connection establishment procedure to establish an RRC connection. Based on the initiation, the UE may transmit an RRC setup request message to the base station. Based on the transmission, the UE may start an RRC timer. Based on detecting that a failure to restore the RRC connection is detected when the RRC timer is running and the RRC request message is not an RRC recovery request message (RRC setup request is being transmitted), the UE in the RRC idle state may perform at least one of the following: resetting MAC; releasing MAC configuration (parameters); and reestablishing RLC for one or more established bearers.

[0268] The UE may initiate an RRC connection resumption procedure in the RRC idle state to resume a suspended RRC connection. Based on the initiation, the UE may transmit an RRC resumption request message to the base station. Based on the transmission, the UE may start an RRC timer. Based on detecting a failure to resume the RRC connection when the RRC timer is running and the RRC request message is an RRC resumption request message (the RRC resumption request message is being transmitted), the UE may reset the MAC. Based on the failure being an RRC timer expiration or a cell (re)selection, an RRC rejection message is received, wherein the RRC rejection message includes an RRC suspension indication, the UE may perform as follows: If the UE resumes the RRC connection after early security reactivation, the UE may abort the early security reactivation; otherwise, the UE may reestablish RLC for one or more established / suspended radio bearers and suspend SRB1.

[0269] The termination of early security reactivation may include at least one of: deleting (or discarding) security keys; reestablishing the RLC entity for one or more SRBs and DRBs; suspending one or more SRBs and DRBs except signaling radio bearer 0 (SRB0); and configuring suspension of integrity protection and encryption.

[0270] Based on the expiration of the RRC timer, the UE in the RRC inactive state may perform at least one of the following: resetting MAC; discarding the UE inactive AS context; releasing the suspension configuration parameters; deleting (or discarding) the security key; releasing all radio resources and transitioning to the RRC idle state, wherein the release of all radio resources may include releasing the MAC configuration (parameters), RLC entity and PDCP entity and SDAP for one or more established bearers; and transitioning to the RRC idle state.

[0271] Based on the cell (re)selection while the RRC timer is running, the UE in the RRC inactive state may perform at least one of the following: resetting MAC; discarding the UE inactive AS context; releasing the suspension configuration parameters; deleting (or discarding) the security key; releasing all radio resources and transitioning to the RRC idle state, wherein the release of all radio resources may include releasing the MAC configuration (parameters), RLC entity and PDCP entity and SDAP for one or more established bearers; and transitioning to the RRC idle state.

[0272] When the RRC timer is running, a UE in an RRC inactive or idle state may receive an RRC rejection message. Based on receiving the RRC rejection message, the UE in an RRC inactive or idle state may stop the RRC timer. Based on the RRC rejection message not including an RRC suspension indication and the RRC request message being an RRC recovery request message, the UE in an RRC idle state performs at least one of the following: resetting MAC; discarding the UE inactive AS context; and releasing all radio resources and transitioning to an RRC idle state, wherein releasing all radio resources may include releasing the MAC configuration (parameters), RLC entity and PDCP entity and SDAP for one or more established bearers. Based on the RRC rejection message and the RRC request message not being an RRC recovery request message, the UE in an RRC idle state may perform at least one of the following: resetting MAC; and releasing default MAC configuration parameters. Based on the RRC rejection message, the UE in an RRC inactive state may perform at least one of the following: resetting MAC; releasing default MAC configuration (parameters); deleting (or discarding) security keys; (re) suspending the RRC connection; and remaining in an RRC inactive state.

[0273] The integrity check failure occurs when the RRC timer is running and the UE is in an RRC inactive or idle state. For example, when the RRC timer is running, the UE in the RRC inactive or idle state may detect an integrity check failure on SRB1 or SRB2. Based on the integrity check failure and the RRC request message is an RRC recovery request message, the UE in the RRC idle state performs at least one of the following: resetting the MAC; discarding the UE inactive AS context; and releasing all radio resources and transitioning to the RRC idle state, wherein releasing all radio resources may include releasing the MAC configuration (parameters), RLC entity and PDCP entity and SDAP for one or more established bearers. Based on the integrity check failure and the RRC request message being an RRC recovery request message, the UE in the RRC inactive state may perform at least one of the following: resetting MAC; discarding the UE inactive AS context; releasing suspension configuration parameters; deleting (or discarding) security keys; releasing all radio resources and transitioning to the RRC idle state, wherein releasing all radio resources may include releasing the MAC configuration (parameters), RLC entity and PDCP entity and SDAP for one or more established bearers; and transitioning to the RRC idle state.

[0274] When the RRC timer is running, the UE in the RRC idle state may detect that the RRC connection has failed to be restored. The UE in the RRC idle state may (re)suspend one or more radio bearers (or RRC connections) based on the failure. Based on suspending one or more radio bearers, the UE in the RRC idle state may send an RRC recovery request message to restore the RRC connection. For example, based on suspending one or more radio bearers, when the UE in the RRC idle state has data or signaling to transmit or receive a paging message from a base station, the UE may send an RRC recovery request message to the base station. The UE in the RRC idle state may not suspend one or more radio bearers (or RRC connections) based on the failure (e.g., release all radio resources). Based on not suspending one or more radio bearers (or RRC connections), the UE in the RRC idle state may release all radio resources and may send an RRC setup request message. For example, based on not suspending one or more radio bearers (or RRC connections), when the UE in the RRC idle state has data or signaling to transmit or receive a paging message from a base station, the UE may send an RRC setup request message to the base station.

[0275] The base station may initiate an RRC connection release procedure to transition the RRC state of the UE from an RRC connected state to an RRC idle state, from an RRC connected state to an RRC inactive state, from an RRC inactive state to an RRC inactive state when the UE attempts to recover, or from an RRC inactive state to an RRC idle state when the UE attempts to recover. The RRC connection procedure may also be used to release the RRC connection of the UE and redirect the UE to another frequency. When the RRC state of the UE is transitioned to an RRC inactive state, the base station may send an RRC release message including a suspension configuration parameter. The suspension configuration parameter may include at least one of the following: a recovery identifier, an RNA configuration, a RAN paging cycle, or a network hop link count (NCC) value, wherein the RNA configuration may include RNA notification area information or a periodic RNA update timer value (e.g., a T380 value). When the UE is in an RRC inactive state, the base station may use a recovery identifier (e.g., an inactive RNTI (I-RNTI)) to identify the UE context.

[0276] If the base station has a new and unused {NCC, next hop (NH)} pair, the base station may include the NCC in the pause configuration parameters. Otherwise, the base station may include the NCC in the pause configuration parameters. gNB The same NCC associated with the AS. The NCC is used for AS security. After sending an RRC release message including the suspension configuration parameters to the UE, the base station may delete the current AS key (e.g., K RRCenc , K UPenc ) and K UPint , but the current AS key K can be kept RRCint If the sent NCC value is new and belongs to an unused {NCC, NH} pair, the base station may save the {NCC, NH} pair in the current UE AS security context and may delete the current AS key K gNB If the NCC value sent is equal to the current K gNB The associated NCC value, the base station can maintain the current AS key K gNB The base station may store the sent recovery flag together with the current UE context, which includes the remaining part of the AS security context.

[0277] After receiving the RRC release message including the suspension configuration parameters from the base station, the UE can verify that the integrity of the received RRC release message including the suspension configuration parameters is correct by checking the PDCP MAC-I. If the verification is successful, the UE can obtain the received NCC value and save it as the stored NCC with the current UE context. The UE can delete the current AS key K RRCenc , K UPenc and KUPint , but keep the current AS key K RRCint If the stored NCC value is different from the current K gNB The UE can delete the current AS key K if the associated NCC value is gNB If the stored NCC is equal to the current K gNB If the associated NCC value is not found, the UE shall keep the current AS key KgNB. The UE may store the received recovery identifier together with the current UE context including the rest of the AS security context for the next state transition.

[0278] Based on receiving the RRC release message including the suspension configuration parameters, the UE may reset the MAC, release the default MAC cell group configuration, and reestablish the RLC entity for one or more bearers. Based on receiving the RRC release message including the suspension configuration parameters, the UE may store the current configuration parameters and the current security keys in the UE inactive AS context. For example, the UE may store some current configuration parameters. The stored current configuration parameters may include the robust header compression (ROHC) state, the quality of service (QoS) flow to DRB mapping rules, the C-RNTI used in the source PCell, the global cell identity and physical cell identity of the source PCell, and all other parameters configured except the parameters in the synchronized reconfiguration and serving cell configuration common parameters in the SIB. The stored security keys may include K gNB and K RRCint At least one of the following. The serving cell configuration common parameters in the SIB may be used to configure the cell-specific parameters of the serving cell of the UE in SIB1. Based on receiving the RRC release message including the suspension configuration parameters, the UE may suspend all SRBs and DRBs except SRB0. Based on receiving the RRC release message including the suspension configuration parameters, the UE may start the timer T380, enter the RRC inactive state, and perform the cell selection procedure.

[0279] The UE may receive an RRC release message from a base station of a serving cell (or PCell). Based on the RRC release message, the UE may perform a UE action for the RRC release message from the base station. The UE may delay the UE action for the RRC release message for a period of time (e.g., 60 ms) from the moment the RRC release message is received or when the RRC release message is successfully confirmed to have been received. The UE may send a HARQ confirmation to the base station to confirm the RRC release message. Based on an RLC protocol data unit (PDU) including the RRC release message and an RLC PDU including a polling bit, the UE may send an RLC message (e.g., a status report) to the base station to confirm the RRC release message.

[0280] The UE action for the RRC release message from the base station may include at least one of: suspending the RRC connection; releasing the RRC connection; a cell (re)selection procedure; and / or idle / inactive measurements.

[0281] The RRC release message from the base station may include a suspension configuration parameter. Based on the suspension configuration parameter, the UE may perform suspension of the RRC connection. Suspension of the RRC connection may include at least one of: a media access control (MAC) reset (or reset MAC); release of a default MAC cell group configuration; reestablishment of an RLC entity for one or more radio bearers; storage of current configuration parameters and current security keys; suspension of one or more bearers, wherein the bearers include signaling radio bearers and data radio bearers; and / or transition to an RRC idle state or an RRC inactive state.

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

[0283] Based on considering the time alignment timer to be expired, the UE may perform at least one of the following: flush all HARQ buffers for all serving cells; notify the RRC to release PUCCH for all serving cells, if configured; notify the RRC to release SRS for all serving cells, if configured; clear any configured downlink assignments and configured uplink grants; clear any PUSCH resources used for semi-persistent CSI reporting; and / or consider all running time alignment timers to have expired.

[0284] The default MAC cell group configuration parameters may include buffer status report (BSR) configuration parameters of the cell group of the base station (e.g., BSR timer) and power headroom report (PHR) configuration parameters of the cell group of the base station (e.g., PHR timer or PHR transmission power factor change parameter).

[0285] Reestablishing the RLC entity may include at least one of: discarding all RLC SDUs, RLC SDU segments and RLC PDUs, if any; stopping and resetting timers of all RLC entities; and resetting all state variables of the RLC entity to their initial values.

[0286] The RRC release message from the base station may not include the suspension configuration parameter. Based on the RRC release message not including the suspension configuration parameter, the UE may perform the release of the RRC connection. For example, based on the RRC release message not including the suspension configuration parameter, the RRC release message may indicate the release of the RRC connection. The UE may perform the release of the RRC connection. Releasing the RRC connection may include at least one of the following: MAC reset (or resetting MAC); discarding stored configuration parameters and stored security keys (or discarding stored UE inactive AS contexts); releasing the suspension configuration parameters; releasing all radio resources, including releasing the RLC entity, MAC configuration, and associated PDCP entity and SDAP for all established radio bearers; and / or transitioning to an RRC idle state.

[0287] The RRC release message may be an RRC early data complete message.

[0288] Based on performing small data transmission, the UE can send or receive a small amount of data without transitioning from an RRC idle state or an RRC inactive state to an RRC connected state. When in an RRC idle state or an RRC inactive state (e.g., without transitioning to an RRC connected state), performing small data transmission may include at least one of the following: initiating small data transmission; sending small data; and / or receiving a response message.

[0289] For example, based on small data transmission, a UE in an RRC idle state or an RRC inactive state may perform initiation of small data transmission. In response to initiation of small data transmission, a UE in an RRC idle state or an RRC inactive state may perform sending small data. In response to sending small data, the UE may receive a response message. For example, the response message may include downlink data (or downlink signaling). For example, based on small data transmission, a UE in an RRC idle state or an RRC inactive state may perform sending small data. In response to sending small data, a UE in an RRC idle state or an RRC inactive state may receive a response message. Sending small data may include at least one of: sending at least one of an RRC request message, uplink data (or uplink signaling), or a buffer status report (BSR). For example, sending small data may include sending an RRC request message. For example, sending small data may include sending an RRC request message and uplink data. For example, sending small data may include sending an RRC request message, first uplink data, and a BSR requesting uplink resources for second uplink data. The RRC request message may include at least one of the following: an RRC recovery request message; or an RRC early data request message. The response message may include at least one of the following: an RRC response message in response to the RRC request message; downlink data; or confirmation of uplink data (e.g., first uplink data); or uplink resources for uplink data (e.g., second uplink data). The RRC response message to the RRC request message may include at least one of the following: an RRC release message; an RRC early data complete message; an RRC setup message; an RRC recovery message; or an RRC reject message.

[0290] Based on receiving an RRC release message, a UE in an RRC idle state or an RRC inactive state may transition to an RRC idle state or an RRC inactive state, or remain in an RRC idle state or an RRC inactive state. Based on receiving an RRC early data completion message, a UE in an RRC idle state or an RRC inactive state may transition to an RRC idle state (or remain in an RRC idle state). Based on receiving an RRC release message or an RRC early data completion message, the UE may consider that sending small data is successful. Based on receiving an RRC setup message or an RRC recovery message, a UE in an RRC idle state or an RRC inactive state may transition to an RRC connected state. Based on receiving an RRC setup message or an RRC recovery message, the UE may consider that sending small data is successful. Based on receiving an RRC rejection message, a UE in an RRC idle state or an RRC inactive state may transition to an RRC idle state. Based on receiving an RRC rejection message, the UE may consider that sending small data is unsuccessful.

[0291] Based on receiving the first RRC release message, the UE may transition to an RRC inactive or idle state. A UE in an RRC inactive or idle state may perform small data transmission. A UE in an RRC inactive or idle state may initiate / trigger small data transmission based on having small data to transmit or based on receiving a paging message. The paging message may indicate small data transmission. Based on performing small data transmission, a UE in an RRC idle state or an RRC inactive state may send uplink data via Msg 3. Msg 3 may be a message transmitted on a UL-SCH containing a C-RNTI MAC CE or CCCH SDU that is optionally multiplexed with a DTCH. For example, as part of a random access procedure, a CCCH SDU may be associated with a UE contention resolution identifier. For example, a UE in an RRC idle state or an RRC inactive state may send a CCCH SDU using a preconfigured uplink resource (PUR). The CCCH SDU may include at least one of an RRC request message and uplink data (e.g., first uplink data). DTCH may include uplink data (e.g., first uplink data). Based on performing small data transmission, a UE in an RRC idle state or an RRC inactive state may receive downlink data in response to sending small data without transitioning to an RRC connected state. For example, based on performing small data transmission, a UE in an RRC idle state or an RRC inactive state may send an RRC request message, and in response to the RRC request message, receive at least one of an RRC response message and / or downlink data. The RRC release message may include a second RRC release message, wherein the RRC release message may include downlink data. Based on the second RRC release message, the UE may transition to an RRC inactive or idle state.

[0292] Small data transmission may include user plane (UP) small data transmission and control plane (CP) small data transmission. Based on UP small data transmission, a UE in RRC idle state or RRC inactive state may send uplink data via a user plane (e.g., DTCH). Based on CP small data transmission, a UE in RRC idle state or RRC inactive state may send uplink data via a control plane (e.g., CCCH). Based on UP small data transmission, a base station of a UE may receive downlink data from a UPF of a UE via a user plane. Based on CP small data transmission, a base station of a UE may receive downlink data from an AMF of a UE via a control plane. In response to CCCH SDU and / or DTCH SDU, a base station may send a response message to a UE in RRC idle state or RRC inactive state.

[0293] Small data transmission may include at least one of initiating small data transmission, sending small data, and receiving a response message. UP small data transmission may include at least one of initiating UP small data transmission, sending UP small data, and receiving a response message. CP small data transmission may include at least one of sending CP small data via a control plane and receiving a response message.

[0294] Initiating small data transmission may include initiating UP small data transmission. Sending small data may include sending UP small data and / or sending at least one of CP small data via a control plane. The response message may be a response message in response to at least one of the RRC request message and / or the (first) uplink data.

[0295] For UP small data transmission, the DTCH SDU may include uplink data. For example, for UP small data transmission, the UE may send a DTCH SDU multiplexed with a CCCH SDU. For example, for UP small data transmission, the CCCH SDU may include at least one of uplink data and an RRC request message. For example, for UP small data transmission, the RRC request message may be an RRC recovery request message. For CP small data transmission, the UE may send a CCCH SDU including uplink data. For example, for CP small data transmission, the RRC request message includes uplink data. For example, for CP small data transmission, the RRC request message may be an RRC early data request message.

[0296] In an example, a small data transfer (SDT) procedure may include exchanging user data between a wireless device and a base station when the wireless device is in a non-connected state (e.g., a radio resource control (RRC) non-connected state) (e.g., an idle state, an inactive state, etc.). The amount of data exchanged in an SDT transmission of the SDT procedure may be less than a threshold amount of data. The SDT procedure may include a single SDT transmission and / or a sequence of SDT transmissions of a small amount of data. For example, using the SDT procedure, a wireless device and / or a base station may transmit and / or receive data via a user plane (UP) or a control plane (CP) while the wireless device remains in a non-connected state (e.g., idle, inactive, etc.). For example, using the SDT procedure, a wireless device may transmit and / or receive data without completing a connection setup or recovery procedure (and without control plane signaling associated with the setup and / or recovery). The data may include user data and signals.

[0297] In an example, a wireless device may need an authorization to transmit data (e.g., uplink data) associated with an SDT procedure. The wireless device may receive an authorization from / via a base station. The authorization may be an uplink authorization for one or more uplink resources, and the wireless device may use the one or more uplink resources to transmit data (e.g., uplink data). The 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 specific time. A configured uplink authorization may indicate repeated, intermittent, and / or periodic resources. For example, a configured uplink authorization configuration may indicate the periodicity of a configured uplink authorization, and one or more uplink resources configured by a configured uplink authorization configuration may be used and reused at periodic intervals. For example, a configured uplink authorization may be configured / activated, and resources associated with a configured uplink authorization configuration of a configured uplink authorization may be used until the configured uplink authorization is released / deactivated. As an illustration, a dynamic uplink grant may indicate resources at time k, while a configured uplink grant may grant resources at time k+nT, where T is the period of the configured uplink grant and n is an integer [0, 1, 2, ...].

[0298] In an example, the wireless device may obtain an uplink grant via a physical or MAC signal (e.g., DCI or a random access (RA) response) indicating an uplink grant. For example, in a random access (RA) based procedure (e.g., an early data transfer (EDT) procedure), the wireless device may send an RA preamble requesting one or more uplink resources. Based on the RA preamble, the wireless device may receive an uplink grant indicating one or more uplink resources for transmitting small data.

[0299] In an example, the wireless device may obtain an uplink grant based on a configured uplink grant. The configured uplink grant may be associated with a configured uplink grant configuration (e.g., a preconfigured uplink resource (PUR) configuration). The wireless device may receive the configured uplink grant configuration via an RRC message (e.g., an RRC release message). The configured uplink grant configuration may indicate a grant of one or more uplink resources, and the wireless device may use and / or reuse one or more uplink resources (e.g., preconfigured uplink resources) to transmit small data.

[0300] For a configured uplink grant transmission (e.g., an uplink transmission using preconfigured uplink resources (PUR)), the UE may send a configured uplink grant configuration request message to the base station, wherein the configured uplink grant configuration request message may include at least one of: the number of configured uplink grant opportunities requested, wherein the number may be one or infinity; the request period for the configured uplink grant; the transport block size (TBS) requested for the configured uplink grant; and / or the time offset requested for the first configured uplink grant opportunity.

[0301] The base station may send a configured uplink grant configuration (parameters) including pre-configured uplink resources to the UE. For example, in response to a configured uplink grant configuration request message, the base station may send a configured uplink grant configuration parameter including pre-configured uplink resources to the UE. For example, the base station may send an RRC release message including the configured uplink grant configuration parameter.

[0302] The configured uplink grant configuration parameters may include at least one of the following: an indication of setting or releasing the configured uplink grant configuration parameters; the number of configured uplink grant opportunities; a configured uplink grant resource identifier (configured uplink grant RNTI); a configured uplink grant configuration identifier (configured uplink grant configID); a time offset value of the first configured uplink grant opportunity (configured uplink grant start time); a periodicity of the configured uplink grant resources (configured uplink grant periodicity); a duration of the configured uplink grant response window (configured uplink grant response window time); a threshold for a serving cell RSRP change in dB for TA verification (configured uplink grant change threshold), wherein the threshold includes an RSRP increase threshold and an RSRP decrease threshold; a value of a time calibration timer for a configured uplink grant; and / or physical configuration parameters for a configured uplink grant. The physical configuration parameters for the configured uplink grant may include at least one of: a PUSCH configuration parameter for the configured uplink grant; a PDCCH configuration parameter for the configured uplink grant; a PUCCH configuration parameter for the configured uplink grant; a downlink carrier configuration parameter for the configured uplink grant; and / or an uplink carrier frequency for the uplink carrier of the configured uplink grant. The configured uplink grant RNTI may be assigned to more than one UE. The configured uplink grant configID may be unique in one base station.

[0303] Based on satisfying the configured uplink grant conditions, the UE may determine to use the configured uplink grant to perform initiated SDT (CG-based SDT). The configured uplink grant conditions may include at least one of the following: the UE has valid configured uplink grant configuration parameters; the UE has a valid timing alignment (TA) value; the system information of the serving cell indicates that the configured uplink grant is supported; the establishment or resumption request is for a mobile originated call, and the establishment reason is mo data or mo exception data or delay tolerant access; the UE supports the configured uplink grant; the size of the result MAC PDU including the total uplink data is expected to be less than or equal to the TBS configured for the configured uplink grant and the UE has a stored NCC value provided in the RRC release message, which includes the suspension configuration parameters during the previous suspension procedure.

[0304] The UE may determine that the timing alignment value for the small data transmission of the configured uplink grant is valid based on satisfying the TA verification condition of the configured uplink grant. The TA verification condition for the configured uplink grant may include at least one of the following: the time alignment timer for the configured uplink grant is running; or the serving cell RSRP has not increased by more than the RSRP increase threshold and has not decreased by more than the RSRP increase threshold.

[0305] In response to receiving the configured uplink grant configuration parameter, the UE may store or replace the configured uplink grant configuration parameter provided by the configured uplink grant configuration parameter based on the indication of requesting to set the configured uplink grant configuration parameter. In response to receiving the configured uplink grant configuration parameter, the UE may start the time alignment timer for the configured uplink grant with the value of the time alignment timer for the configured uplink grant, and configure the configured uplink grant configuration parameter. For example, based on the indication of requesting to set the configured uplink grant configuration parameter, the UE may start the time alignment timer for the configured uplink grant with the value of the time alignment timer for the configured uplink grant, and configure the configured uplink grant configuration parameter. In response to receiving the configured uplink grant configuration parameter, the UE may discard the configured uplink grant configuration parameter based on the indication of requesting to release the configured uplink grant configuration parameter. In response to configuring the configured uplink grant configuration parameter, the UE may generate a configured uplink grant based on the configured uplink grant configuration parameter. For example, based on the configured uplink grant configuration parameters, the UE may determine when to generate the configured uplink grant. For example, based on the configured uplink grant start time and the configured uplink grant period, the UE may determine when to generate the configured uplink grant. For example, based on the PUSCH configuration parameters, the UE may determine (the transport block of) the configured uplink grant. For example, based on the PUSCH configuration parameters, the UE may determine (the transport block of) the configured uplink grant.

[0306] Fig.19 An example of data transmission based on a configured uplink grant (e.g., a preconfigured uplink resource (PUR)) is shown. Based on receiving the first RRC release message, the UE may transition to an RRC non-connected state (e.g., an RRC idle state or an RRC inactive state). Fig.19As shown, the UE may send a configuration request for the configuration of a configured uplink grant ("CUG" in the figure). The UE may receive the parameters of the configured uplink grant configuration via an RRC release message. The previous RRC release message may be the first RRC release message. In response to receiving the configured uplink grant configuration parameters, the UE in the RRC idle state or the RRC inactive state may start the time alignment timer for the configured uplink grant with the value of the time alignment timer for the configured uplink grant, and configure the configured uplink grant configuration parameters. In response to configuring the configured uplink grant configuration parameters, the UE in the RRC idle state or the RRC inactive state may generate a configured uplink grant based on the configured uplink grant 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, the UE in the RRC idle state or the RRC inactive state may select cell 2 of the second base station (target base station). A UE in an RRC idle state or an RRC inactive state may have the first uplink data in an uplink buffer, or may receive a paging message. A UE in an RRC idle state or an RRC inactive state may determine to perform small data transmission based on satisfying the UP configured uplink authorization condition or the CP configured uplink authorization condition. For example, in response to having the first uplink data or receiving a paging message, a UE in an RRC idle state or an RRC inactive state may determine to perform small data transmission based on satisfying the UP configured uplink authorization condition or the CP configured uplink authorization condition. Based on this determination, the UE may perform small data transmission. Based on the uplink resources / authorization for configuring the uplink authorization, the UE may perform sending small data. For example, a UE in an RRC idle state or an RRC inactive state may use the uplink resources for configuring the uplink authorization to send at least one of the RRC request message and / or the first uplink data. For example, based on sending small, a UE in an RRC idle state or RRC inactive may send Msg 3 including at least one of a CCCH SDU and / or a DTCH SDU, wherein the CCCH SDU includes an RRC request message and the DTCH SDU includes the first uplink data. In response to sending small data using a configured uplink grant, the UE (UE-MAC entity) may start a configured uplink grant response window timer with a configured uplink grant response window time. Based on the start, the UE may monitor the PDCCH identified by the configured uplink grant RNTI until the configured uplink grant response window timer expires. The UE (UE-MAC entity) may receive a downlink message (e.g., DCI) identified by a configured uplink grant RNTI on the PDCCH.Based on receiving a downlink message indicating an uplink grant for retransmission, the UE can restart the configured uplink grant response window timer at the last subframe, pulse time interval (e.g., 4 subframes) of the PUSCH transmission indicating the uplink grant. Based on the restart, the UE in the RRC idle state or the RRC inactive state can monitor the PDCCH identified by the configured uplink grant RNTI until the configured uplink grant response window timer expires. Based on receiving a downlink message indicating the L1 (layer 1) ack for the configured uplink grant, the UE in the RRC idle state or the RRC inactive state can stop the configured uplink grant response window timer and consider the small data transmission using the configured uplink grant to be successful. Based on receiving a downlink message indicating the fallback for the configured uplink grant, the UE in the RRC idle state or the RRC inactive state can stop the configured uplink grant response window timer and consider the small data transmission using the configured uplink grant to fail. Based on receiving a downlink message indicating a PDCCH transmission (downlink grant or downlink assignment) addressed to a configured uplink grant RNTI and / or MAC PDU including successfully decoded uplink data, a UE in an RRC idle state or an RRC inactive state may stop a configured uplink grant response window timer and consider that a small data transmission using a configured uplink grant is successful. Based on PDCCH transmission, a UE in an RRC idle state or an RRC inactive state may receive at least one of an RRC response message and downlink data, wherein the RRC response message is at least one of an RRC release message or an RRC early data completion message. Based on not receiving any downlink message until the configured uplink grant response window timer expires, a UE in an RRC idle state or an RRC inactive state may consider that a small data transmission using a configured uplink grant has failed. Based on considering that a small data transmission using a configured uplink grant has failed, the UE may perform a random access procedure. For example, the random access procedure may include an EDT RACH procedure.

[0307] Fig. 20An example of a UP configured uplink grant and a CP configured uplink grant is shown. A UE in an RRC connected state can communicate with a first base station based on a first configuration parameter and a first security key. The first base station can send an RRC release message to the UE. Based on receiving an RRC release message including a first suspension configuration parameter, the UE can perform a suspension of the RRC connection based on the first suspension configuration parameter. The UE can transition to an RRC idle state or an RRC inactive state. The UE can receive a configured uplink grant configuration parameter via a previous RRC release message. The previous RRC release message can be an RRC release message. In response to receiving a configured uplink grant configuration parameter, a UE in an RRC idle state or an RRC inactive state can start a time alignment timer for a configured uplink grant with a value for a time alignment timer for a configured uplink grant, and configure the configured uplink grant configuration parameter. In response to configuring the configured uplink grant configuration parameter, a UE in an RRC idle state or an RRC inactive state can generate a configured uplink grant based on the configured uplink grant configuration parameter. Based on the RRC release message, the UE in the RRC idle state or the RRC inactive state can perform a cell (re) selection procedure. Based on the cell (re) selection procedure, the UE in the RRC idle state or the RRC inactive state can select the cell 2 of the second base station (target base station). The UE in the RRC idle state or the RRC inactive state can determine to execute the initiation of UP small data transmission based on satisfying the UP configured uplink authorization condition. Based on the determination to execute the initiation of UP small data transmission, the UE in the RRC idle state or the RRC inactive state can use the first suspension configuration parameter to execute the initiation of UP small data transmission. Based on the (pre-configured) uplink resources for the configured uplink authorization, the UE in the RRC idle state or the RRC inactive state can use the first suspension configuration parameter to perform the transmission of UP small data. For example, the UE in the RRC idle state or the RRC inactive state can use the uplink resources configured with the uplink authorization to send uplink data.

[0308] exist Fig. 20In an example of , a UE in an RRC connected state may communicate with a first base station based on a first configuration parameter and a first security key. The first base station may send an RRC release message to the UE. Based on receiving an RRC release message that does not include a first suspension configuration parameter, the UE may perform release of the RRC connection based on the RRC release message. The UE may transition to an RRC idle state. The UE may receive a configured uplink grant configuration parameter via a previous RRC release message. The previous RRC release message may be an RRC release message. In response to receiving the configured uplink grant configuration parameter, the UE in the RRC idle state may start a time alignment timer for a configured uplink grant with a value of a time alignment timer for a configured uplink grant, and configure the configured uplink grant configuration parameter. In response to configuring the configured uplink grant configuration parameter, the UE in the RRC idle state may generate a configured uplink grant for a configured uplink grant based on the configured uplink grant configuration parameter. Based on the RRC release message, the UE in the RRC idle state may perform a cell (re)selection procedure. Based on the cell (re) selection procedure, the UE in the RRC idle state can select the cell 2 of the second base station (target base station). The UE in the RRC idle state can determine to send CP small data via the control plane based on satisfying the CP configured uplink authorization condition. Based on this determination, the UE in the RRC idle state can send CP small data via the control plane. For example, based on the (pre-configured) uplink resources for configuring the uplink authorization, the UE in the RRC idle state can send CP small data via the control plane. For example, the UE in the RRC idle state can use the uplink resources for configuring the uplink authorization to send at least one of the RRC request message and / or the uplink data. For example, the RRC request message can be an RRC early data request message and / or include uplink data.

[0309] The first base station (source base station) sends an RRC release message to the wireless device, wherein the RRC release message includes a suspension configuration and a configuration of at least one configured uplink grant of the first cell. The suspension configuration may include a resume identifier. Based on the RRC release message, the first base station may store a mapping of the resume identifier and the configuration of at least one configured uplink grant of the first cell. Based on the suspension configuration, the wireless device may suspend the RRC connection. The wireless device may determine to resume the RRC connection. Based on the determination, the wireless device that suspends the RRC connection may send an RRC resume request message including the resume identifier. The resume identifier may be passed to the first base station based on a retrieval UE context procedure. Based on the resume identifier, the first base station may release the configuration.

[0310] The UE may receive a configured uplink grant configuration (parameters) for the first cell. The configured uplink grant configuration may include at least one of the following: a configured uplink grant configuration identifier; and a configured uplink grant for the first cell. In the accompanying drawings, for simplicity, the configured uplink grant configuration identifier may be abbreviated as "CULG-configID". The UE may send an RRC setup request message via the first cell and not use the configured uplink grant of the first cell. Based on sending an RRC setup message that does not use the configured uplink grant and has the configured uplink grant configuration, the UE may send an RRC setup completion message including the configured uplink grant configuration identifier. In response to receiving the RRC setup message, the UE may send an RRC setup completion message. The UE may receive an RRC setup message in response to the RRC setup request message. Based on receiving the configured uplink grant configuration identifier, the base station of the first cell may identify the configured uplink grant configuration associated with the configured uplink grant configuration identifier. Based on identifying the configured uplink grant configuration, the base station may manage the configured uplink grant configuration. For example, management may include release. The configured uplink grant configuration identifier is a unique identifier for each base station.

[0311] In the prior art, a wireless device may receive a first configured uplink grant configuration of a first cell from a first base station. Based on receiving the first configured uplink grant configuration of the first cell, the wireless device may store the first configured uplink grant configuration of the first cell. A wireless device in an RRC idle state may select a second cell. For example, the second cell may be selected for connection based on the signal strength of the second cell. The wireless device may initiate a random access procedure on the second cell, wherein the random access procedure includes an RRC connection establishment procedure. Based on initiating the random access procedure, the wireless device may disconnect from the first cell and / or release the first configured uplink grant configuration of the first cell. The first base station may not be aware that the first configured uplink grant is no longer in use. The first base station may maintain the first configured uplink grant configuration parameters. Based on maintaining the first configured uplink grant configuration parameters, the first cell may keep allocating resources associated with the first configured uplink grant, which may waste the allocated resources by preventing other network entities from using them.

[0312] Fig.21An example of a wireless device release of a configured uplink grant configuration parameter is shown. A wireless device in an RRC connected state may send a configured uplink grant configuration request message to a first base station via a first cell. The first base station may send an RRC release message including a configured uplink grant configuration (parameters) to the wireless device. The first base station may store the configured uplink grant configuration. Based on the RRC release message, the wireless device may transition to an RRC idle state. The wireless device may select a second cell based on a cell (re)selection. The wireless device may initiate a random access procedure via the second cell, wherein the random access procedure includes an RRC connection establishment procedure. Based on the random access procedure, the wireless device may release the configured uplink grant configuration. The first base station may not recognize that the configured uplink grant configuration is being released by the wireless device. The first base station may maintain the configured uplink grant configuration, and the first cell may keep allocating the configured uplink grant of the wireless device.

[0313] In an embodiment of the present disclosure, a wireless device in an RRC idle state may send one or more RRC messages indicating the release of at least one configured uplink grant of the first cell to the second base station. Based on the first cell being a cell of the first base station, the second base station may send one or more RRC messages to the first base station. Based on the one or more RRC messages, the first base station may release the configured uplink grant configuration of the first cell. Based on the implementation scheme, the first base station may avoid wasting radio resources due to unnecessary allocation of configured uplink grants.

[0314] In an example, the UE may select a second cell. The UE may determine to establish an RRC connection via the second cell. Based on the determination, the UE may send one or more RRC messages indicating to release at least one configured uplink grant of the one or more configurations (configured uplink grant configurations) of the first cell. Based on the determination, the UE may send one or more RRC messages indicating to release the one or more configurations (configured uplink grant configurations) of the first cell.

[0315] In an example, the one or more RRC messages may include at least one of: one or more cell identifiers of the first cell; or one or more configured uplink grant configuration identifiers; a recovery identifier.

[0316] In an example, the UE may select a second cell. The UE may determine to establish an RRC connection via the second cell. Based on the determination, the UE may initiate an RRC procedure to establish the RRC connection. For example, based on initiation via the second cell, the UE may decide to release at least one of: at least one configured uplink grant of one or more configured first cells; or one or more configurations of at least one configured uplink grant of the first cell. Based on the decision, the UE may send one or more RRC messages indicating the release of at least one of: at least one configured uplink grant of one or more configurations of the first cell; or one or more configurations of at least one configured uplink grant of the first cell. The RRC procedure includes an RRC connection establishment procedure.

[0317] In an example, the UE may receive at least one first radio resource control (RRC) message from a first cell, the message including one or more configurations of at least one configured uplink grant of the first cell. The one or more RRC messages may include at least one of: one or more cell identifiers of the one or more configured cells; one or more configured uplink grant configuration identifiers of the one or more configurations. The one or more configurations may not include a configuration of a second cell and a cell identifier of the second cell.

[0318] In an example, based on receiving one or more configurations, the UE may store the one or more configurations. For example, at least one first RRC message may include an RRC release message. Based on the RRC release message, the UE may transition from an RRC connected state to an RRC idle state. The RRC release message may include one or more configurations. The configuration may be an indication for maintaining a configured uplink grant configuration stored by the UE.

[0319] In the example, based on at least one of the following: the second cell is different from the first cell; and determining to establish an RRC connection via the second cell, the UE may determine to release at least one of the following: at least one configured uplink grant of one or more configured first cells; or one or more configurations of at least one configured uplink grant of the first cell.

[0320] In an example, one or more RRC messages may include one or more cell identifiers of a first cell, wherein the first cell includes one or more cells associated with one or more configurations. For example, the UE may select a second cell. The UE may initiate an RRC procedure to establish an RRC connection via the second cell. Based on the initiation, the UE may determine to release at least one of: at least one configured uplink grant of the first cell of one or more configurations; or one or more configurations of at least one configured uplink grant of the first cell. Based on the determination, the UE may send one or more RRC messages including one or more cell identifiers of the first cell. For example, the UE may send one or more cell identifiers of the first cell to indicate the release of at least one configured uplink grant of the first cell or one or more configurations of the first cell.

[0321] In an example, the UE may send one or more RRC messages including one or more configured uplink grant configuration identifiers (configured uplink grant configuration identifiers) of the wireless device. For example, the UE may send one or more RRC messages including one or more configured uplink grant configuration identifiers based on at least one of the following: one or more RRC messages are not in response to the transmission of at least one configured uplink grant using one or more configured uplink grant configuration identifiers; and determine to release at least one configured uplink grant or one or more configured uplink grant configurations of one or more configured uplink grant configuration identifiers. For example, the UE may send one or more RRC messages including one or more configured uplink grant configuration identifiers associated with the first cell based on at least one of the following: determine to establish an RRC connection via the second cell; and send one or more RRC messages without using at least one configured uplink grant of the configuration of the second cell. For example, the UE may send one or more RRC messages including one or more configured uplink grant configuration identifiers of one or more configurations of the first cell based on not sending one or more RRC messages (e.g., RRC setup request messages) in response to the transmission of at least one configured uplink grant using one or more configurations. The configuration may include a configured uplink grant configuration identifier.

[0322] In an example, the UE may send one or more RRC messages including at least one of one or more cell identifications of the first cell and one or more configured uplink grant configuration identifiers of the one or more configurations.

[0323] In an example, the one or more RRC messages may include at least one of: one or more cell identifiers of the first cell; and one or more configured uplink grant configuration identifiers of one or more configurations of the first cell. For example, the UE may select a second cell. The UE may initiate an RRC procedure to establish an RRC connection via the second cell. Based on the initiation, the UE may determine to release at least one of: at least one configured uplink grant of the one or more configured first cells; or one or more configurations of at least one configured uplink grant of the first cell. Based on the determination, the UE may send one or more RRC messages.

[0324] In an example, at least one first RRC message may include one or more configurations of at least one configured uplink grant. Each configured uplink grant configuration in the one or more configurations may include a configured uplink grant configuration identifier. Each configured uplink grant configuration may be associated with at least one cell identifier. The UE may send one or more RRC messages indicating the release of at least one of: at least one configured uplink grant of one or more configured first cells; or one or more configurations of at least one configured uplink grant of the first cell. The one or more RRC messages may include a list of configured uplink grant configuration identifiers and at least one cell identifier associated with a single configuration. For example, the UE may send one or more RRC messages including a list associated with a first cell. The first cell may include one or more cells different from the second cell.

[0325] In an example, a UE may receive three configurations, wherein a first configuration includes a configuration of at least one configured uplink grant for a first cell, a second configuration includes a configuration of at least one configured uplink grant for a second cell, and a third configuration includes a configuration of at least one configured uplink grant for a third cell. The UE may select a second cell. The UE may determine to establish an RRC connection via the second cell. Based on the determination, the UE may send one or more RRC messages indicating the release of at least one of: at least one configured uplink grant of the first configuration and the third configuration; or the first configuration and the third configuration. The one or more RRC messages may include a list including at least one of: a configured uplink grant configuration identifier of the first configuration and a cell identity of the first cell; and a configured uplink grant configuration identifier of the third configuration and a cell identity of the third cell. The UE may determine not to use the configured uplink grant of the second configuration to establish an RRC connection. For example, the UE may send one or more RRC messages (e.g., an RRC setup request message) that are not in response to the transmission of at least one configured uplink grant using the second configuration. Based on the determination, one or more RRC messages may include at least one of the following: a configured uplink grant configuration identifier of the second configuration; and a cell identity of the second cell. Based on the determination, the UE may decide to release at least one of the following: at least one configured uplink grant of the second configuration; or the second configuration. Based on the decision, one or more RRC messages may include at least one of the following: a configured uplink grant configuration identifier of the second configuration; and a cell identity of the second cell. For example, the UE may send one or more RRC messages without using at least one configured uplink grant of the first configuration or the third configuration. For example, the UE may send one or more RRC messages (e.g., an RRC setup request message) that are not responsive to a transmission of at least one configured uplink grant using the first configuration or the third configuration. Based on the transmission, the UE may determine to release the first configuration and the third configuration. The UE may determine to send one or more RRC messages using the configured uplink grant of the second configuration. Based on the determination, the one or more RRC messages may include a list including at least one of: a configured uplink grant configuration identifier of the first configuration and a cell identity of the first configuration; a configured uplink grant configuration identifier of the third configuration and a cell identity of the third configuration.

[0326] In an example, the UE may receive a confirmation indication to release one or more configurations in response to one or more RRC messages. The UE may release one or more configurations of at least one configured uplink grant based on at least one of: receiving a confirmation indication; or receiving an RRC response message in response to one or more RRC messages. For example, the UE may receive an RRC response message in response to one or more RRC messages. The RRC response message may include a confirmation indication. Based on the RRC response message, the UE may release one or more configurations.

[0327] In an example, the confirmation indication may include one or more indications. The indication may indicate that one of the one or more configurations is released. The UE may receive a confirmation indication including one or more indications. Based on the one or more indications, the UE may release one or more configurations associated with the one or more indications. For example, the UE may maintain one or more configurations based on at least one of the following: no confirmation indication (e.g., one or more indications) associated with one or more configurations is received; or an indication to maintain one or more configurations is received. The RRC response message may include the indication. For example, the UE may suspend one or more configurations based on at least one of the following: no confirmation indication (e.g., one or more indications) associated with one or more configurations is received; or an indication to suspend one or more configurations is received. The UE may receive an indication to resume one or more configurations (e.g., one or more configurations that are suspended). Based on receiving an indication to resume one or more configurations, the UE may resume one or more configurations associated with the resume indication. The indication to maintain or suspend or resume the indication may include a configured uplink grant configuration ID. The RRC response message may include an indication or a confirmation indication.

[0328] In an example, the UE may select a second cell. The UE may determine to establish an RRC connection via the second cell. Based on the determination, the UE may initiate an RRC procedure to establish the RRC connection. For example, based on the initiation via the second cell, the UE may decide to release at least one of: at least one configured uplink grant of one or more configurations of the first cell; or one or more configurations of the first cell. Based on the decision, the UE may send one or more RRC messages indicating the release of at least one of: at least one configured uplink grant of one or more configurations of the first cell; or one or more configurations of the first cell. The RRC procedure includes an RRC connection establishment procedure.

[0329] In an example, the UE may send one or more RRC messages including at least one of: one or more cell identifiers of one or more configurations; and one or more configured uplink grant configuration identifiers of one or more configurations. The one or more configurations may not include a configuration of a second cell. The UE may receive an RRC response message in response to the one or more RRC messages. Based on the RRC response message, the UE may release one or more configurations. For example, based on determining to establish an RRC connection via a second cell, the UE may release at least one configured uplink grant of a first cell of one or more configurations; or one or more configurations of at least one configured uplink grant of a first cell. The UE may send one or more RRC messages indicating the release of at least one of: at least one configured uplink grant of a first cell of one or more configurations; or one or more configurations of at least one configured uplink grant of a first cell. Based on the RRC response message, the UE may release one or more configurations. For example, the UE may store at least one of: a configured uplink grant configuration identifier of one or more configurations; and one or more cell identifiers associated with one or more configurations. For example, based on determining to establish an RRC connection via the second cell, the UE may store at least one of: a configured uplink grant configuration identifier of one or more configurations; one or more cell identifiers associated with the one or more configurations. In response to the storing, the UE may release the one or more configurations. In response to the releasing, the UE may send one or more RRC messages, the one or more RRC messages including at least one of: one or more cell identifiers of one or more configurations; one or more configured uplink grant configuration identifiers of one or more configurations.

[0330] In an example, the one or more RRC messages may include at least one of: an RRC setup request message; an RRC setup complete message; a configured uplink grant configuration request message; a configured uplink grant configuration release request message; and a UE information request message.

[0331] In an example, the UE may receive an RRC setup message in response to the RRC setup request message. The UE may send an RRC setup complete message in response to the RRC setup message.

[0332] In an example, the RRC setup request message may include at least one of: a serving temporary mobile subscriber identity (S-TMSI); or a random value for contention resolution.

[0333] In an example, the RRC setup complete message may include at least one of: one or more cell identities of cells associated with one or more configurations; and one or more configured uplink grant configuration identifiers of one or more configurations. For example, the RRC setup complete message may include a list of configured uplink grant configuration identifiers and cell identities associated with the configured uplink grant configuration identifiers, wherein the configured uplink grant configuration identifiers are configured uplink grant configuration identifiers of one or more configurations.

[0334] In an example, the configured uplink grant configuration release request message may include at least one of the following: one or more configured cell identities; and one or more configured configured uplink grant configuration identifiers. For example, the configured uplink grant configuration release request message may include a configured uplink grant configuration identifier and a list of cell identities associated with the configured uplink grant configuration identifier, wherein the configured uplink grant configuration identifier is one or more configured configured uplink grant configuration identifiers. In response to transitioning to the RRC connected state, the UE may send a configured uplink grant configuration release request message. For example, the UE may send a configured uplink grant configuration release request message via SRB2.

[0335] In an example, based on receiving the RRC setup message, the UE may release at least one of: at least one configured uplink grant of the one or more configured first cells; or one or more configurations of at least one configured uplink grant of the first cell.

[0336] In an example, the UE may select the second cell. For example, the UE in the RRC idle state may select the second cell based on cell (re)selection.

[0337] In an example, the second cell may be different from the first cell. The second base station of the second cell may be different from the first base station of the first cell.

[0338] In an example, the cell identity may include at least one of the following: a physical cell identity; or a global cell identity. For example, the cell identity of the first cell may include at least one of the following: a physical cell identity; or a global cell identity.

[0339] In an example, the UE may determine to establish an RRC connection in at least one of the following situations: there is uplink data to be transmitted; or a paging message is received. For example, the UE may initiate an RRC procedure to establish an RRC connection in at least one of the following situations: there is uplink data to be transmitted; or a paging message is received.

[0340] In an example, the RRC response message may include at least one of the following: an RRC setup message; an RRC reconfiguration message; and a UE information response message. The UE may receive the UE information response message in response to the UE information request message. The UE may receive the RRC reconfiguration message in response to the RRC setup complete message.

[0341] In an example, the second base station may receive one or more RRC messages from the UE, the one or more RRC messages indicating the release of at least one of: at least one configured uplink grant of one or more configurations; or one or more configurations. The one or more RRC messages include at least one of: one or more cell identifiers of one or more configurations; one or more configured uplink grant configuration identifiers of one or more configurations. The second base station may include a second cell.

[0342] In an example, the second base station may determine one or more first base stations of the first cell based on one or more cell identifiers of the first cell. The first cell includes one or more cells associated with one or more configurations. The second base station may classify one or more RRC messages according to the base station, wherein the base station includes one or more first base stations. The second base station may send one or more RRC messages to the base station. For example, the second base station may classify one or more cell identifiers according to the base station. The second base station may classify one or more cell identifiers of the base station as the cell identifier of the base station. Based on the classification, the second base station sends an Xn message to the base station, wherein the Xn message includes a cell identifier and a configured uplink authorization configuration identifier associated with the cell identifier. The second base station may send one or more Xn messages to one or more first base stations.

[0343] In an example, in response to the one or more Xn messages, the second base station may receive one or more Xn response messages from the one or more first base stations. Each of the one or more Xn response messages may include an acknowledgement indication.

[0344] In an example, the second base station may send one or more confirmation indications to the UE. The second base station may send one or more Xn response messages to the UE. The RRC response message may include one or more confirmation indications or one or more Xn response messages.

[0345] In an example, the first base station may send at least one first RRC message to the UE via the first cell, wherein the at least one first RRC message may include a configuration of at least one preconfigured uplink resource (configured uplink grant) of the first cell. From the second base station, the first base station may receive one or more RRC messages (or Xn messages), the one or more RRC messages indicating the release of at least one of the following: at least one configured uplink grant of one or more configured first cells; or one or more configurations of at least one configured uplink grant of the first cell. Based on the one or more RRC messages, the first base station may release or suspend the configuration.

[0346] In an example, in response to one or more RRC messages, the first base station may determine to release or suspend or update one or more configurations of at least one configured uplink authorization of the first cell. Based on the determination of the one or more configurations, the first base station may send a message indicating the determination (e.g., release or suspension or update) to the UE via the second base station. For example, based on the determination to release the one or more configurations, the first base station may send a confirmation indication that the one or more configurations are released to the UE via the second base station. For example, the first base station may determine to maintain or suspend or resume one or more configurations. Based on the determination, the first base station may send an indication to maintain or suspend or resume one or more configurations.

[0347] Fig. 22An example of an enhanced configured uplink grant release procedure is shown. A UE in an RRC connected state may send a configured uplink grant request message to a first base station via a first cell. Based on the configured uplink grant request message, the first base station may send an RRC release message, the RRC release message including a configuration of at least one configured uplink grant of the first cell. The configuration may include a configured uplink grant configuration identifier. The first base station may store a mapping of the configured uplink grant configuration identifier and the configuration. Based on the RRC release message, the UE may transition from the RRC connected state to the RRC idle state and release the RRC connection. The UE in the RRC idle state may select a second cell. The second cell may be a cell of a second base station. The UE in the RRC idle state may determine to establish an RRC connection via the second cell. Based on the determination, the UE may release at least the configured uplink grant of the configuration. Based on the release, the UE may send one or more RRC messages, the one or more RRC messages including a cell identifier of the first cell and a configured uplink grant configuration identifier of the configuration. Based on the cell identifier of the first cell, the second base station may determine that the first cell is a cell of the first base station. Based on the determination, the second base station may send one or more RRC messages to the first base station. Based on the configured uplink grant configuration identifier of the one or more RRC messages, the first base station may identify the configuration of the configured uplink grant configuration identifier. Based on the one or more RRC messages, the first base station may release or suspend or maintain the configuration of the UE. Based on the release or suspension or maintenance, the first base station may send a message indicating the release or suspension or maintenance to the UE via the second base station.

[0348] In the prior art, when the RRC connection of the wireless device is suspended, the first base station (source base station) may store a mapping of a recovery identifier and a configuration of at least one configured uplink grant of the first cell. The wireless device that suspends the RRC connection may send a recovery identifier. The recovery identifier may include an identifier of the first cell and a UE identifier. The recovery identifier may be transmitted to the first base station based on a retrieval UE context request message. Based on the recovery identifier, the first base station may identify the configuration. When a failure to restore the RRC connection is detected, the wireless device that suspends the RRC connection may release the RRC connection. Based on releasing the RRC connection, the wireless device may not send a recovery identifier. Based on not sending the recovery identifier, the first base station may not identify the configuration and may not release the configuration. The first base station may maintain a configured uplink grant configuration parameter. Based on maintaining the configured uplink grant configuration parameter, the first cell may keep allocating the configured uplink grant, which may result in a waste of the configured uplink grant.

[0349] In an embodiment of the present disclosure, a wireless device that suspends an RRC connection may release the RRC connection. The wireless device may determine to establish an RRC connection. Based on the determination, the wireless device may send one or more RRC messages indicating the release of at least one of: at least one configured uplink grant of one or more configured first cells; or one or more configurations of at least one configured uplink grant of the first cell. Based on receiving one or more RRC messages, the second base station may send one or more RRC messages to a first base station based on the first cell, wherein the first cell is a cell of the first base station. Based on one or more RRC messages, the first base station may release the configured uplink grant configuration of the first cell. Based on the implementation scheme, the first base station may avoid wasting radio resources due to unnecessary allocation of configured uplink grants.

[0350] In an example, a UE that suspends an RRC connection may release the RRC connection based on a failure to resume the RRC connection. The UE may select a second cell. The UE may determine to establish an RRC connection via the second cell. Based on the determination, the UE may send one or more RRC messages indicating the release of at least one of: at least one configured uplink grant of one or more configured first cells; or one or more configurations of at least one configured uplink grant of the first cell.

[0351] In an example, one or more RRC messages may include one or more cell identifiers or recovery identifiers of the first cell. The one or more RRC messages include one or more cell identifiers of the first cell, and the one or more RRC messages may include one or more configured uplink grant configuration identifiers. For example, based on the indication, the one or more RRC messages may include one or more cell identifiers of the first cell and one or more configured uplink grant configuration identifiers. Based on the indication, the one or more RRC messages may include a recovery identifier.

[0352] In an example, the first base station may send at least one RRC message to the UE, wherein the at least one RRC message includes a suspension configuration for suspending the RRC connection and a configuration of at least one configured uplink grant of the first cell. The suspension configuration may include a resume identifier. The configuration may include a configured uplink grant configuration identifier. The first base station may store a mapping of the resume identifier and the configuration or a mapping of the configured uplink grant configuration identifier and the configuration. Based on receiving the configuration, the UE may store the configuration. Based on receiving the suspension configuration, the UE may suspend the RRC connection.

[0353] In the example, based on the suspension configuration, the UE may suspend the RRC connection. The RRC release message may include the suspension configuration. Based on the RRC release message, the UE may transition to an RRC inactive state or an RRC idle state. The UE may determine to resume the suspended RRC connection. Based on the determination, the UE may initiate an RRC connection recovery procedure. Based on the initiation, the UE may send an RRC recovery request message via a third cell, wherein the RRC recovery request message includes a recovery identifier. Based on the sending, the UE may start an RRC timer for the RRC recovery request message. If the RRC timer is running, the UE may detect a failure to resume the RRC connection. Based on the detection of the failure, the UE may release the suspended RRC connection.

[0354] In an example, based on releasing the suspended RRC connection, the UE may perform a release of the RRC connection. The UE may determine to establish an RRC connection. Based on the determination, the UE may send one or more RRC messages for the RRC connection. The one or more RRC messages may include an RRC setup request message.

[0355] In an example, the failure to restore the RRC connection may include at least one of: expiration of an RRC timer; if the RRC timer is running, selecting a cell other than the third cell; receiving a fallback indication; receiving a (RRC) rejection message; or failing to comply with an RRC response message. If the RRC timer is running, the UE may receive an RRC response message in response to the RRC recovery request message. The RRC response message may include at least one of: an RRC recovery message; an RRC setup message; and an RRC release message.

[0356] Fig.23An example of an enhanced configured uplink grant release procedure for recovering an RRC connection failure is shown. A UE in an RRC connected state may send a configured uplink grant request message to a first base station via a first cell. Based on the configured uplink grant request message, the first base station may send an RRC release message, which includes a configuration of a suspension configuration and at least one configured uplink grant of the first cell. The configuration may include a configured uplink grant configuration identifier. The suspension configuration may include a recovery identifier of the UE. The first base station may store a mapping of the configured uplink grant configuration identifier and a configuration or mapping of the recovery identifier and configuration. Based on the RRC release message, the UE may transition from an RRC connected state to an RRC inactive state or an RRC idle state. Based on the suspension configuration, the UE may suspend the RRC connection. The UE may detect a failure to recover the RRC connection. Based on the failure, the UE may release the suspended RRC connection. Based on releasing the suspended RRC connection, if the UE is in an RRC inactive state, the UE may transition to an RRC idle state. The UE in the RRC idle state may select a second cell. A UE in an RRC idle state may determine to establish an RRC connection via a second cell. Based on the determination, the UE may release at least the configured uplink authorization of the configuration. Based on the release, the UE may send one or more RRC messages indicating the release of at least the configured uplink authorization. Based on the indication, one or more RRC messages may include a configured uplink authorization configuration identifier and a cell identifier of the first cell, or a recovery identifier. Based on the cell identifier or the recovery identifier of the first cell, the second base station may determine that the first cell is a cell of the first base station. Based on the determination, the second base station may send one or more RRC messages to the first base station. Based on the configured uplink authorization configuration identifier or the recovery identifier, the first base station may identify the configuration. Based on the identification, the first base station may release, suspend or maintain the configuration of the UE. Based on the release, suspension or maintenance, the first base station may send a message indicating the release, suspension or maintenance to the UE via the second base station.

[0357] exist Fig.23 In the example of , Option 1 shows an example of a mapping of a configured uplink grant configuration identifier and a configured uplink grant configuration. The first base station may store a mapping of a configured uplink grant configuration identifier and a configuration. The UE may send one or more RRC messages including a configured uplink grant configuration identifier and a cell identifier of the first cell. Option 2 shows an example of a mapping of a recovery identifier and a configuration. The first base station may store a mapping of a recovery identifier and a configuration. The UE may send one or more RRC messages including a recovery identifier.

[0358] In the prior art, a base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU), wherein the base station may be a first base station or a second base station. Based on sending at least one RRC message including a configured uplink grant configuration, the gNB-CU may store the (configured uplink grant) configuration, and the gNB-DU may allocate at least one configured uplink grant of one or more configured first cells. The wireless device may send one or more RRC messages to the base station, the one or more RRC messages including one or more cell identifiers of one or more configured first cells and one or more configured uplink grant configuration identifiers. The one or more RRC messages may be delivered to the gNB-CU via the gNB-DU. The gNB-DU may not be aware of the release of at least the configured uplink grant of the first cell (or the release of one or more configurations). The first cell of the gNB-DU may keep allocating at least the configured uplink grant, which may result in a waste of the configured uplink grant.

[0359] In an embodiment of the present disclosure, a gNB-CU may receive one or more RRC messages from a wireless device, the one or more RRC messages indicating the release of at least a configured uplink grant of a first cell of one or more configurations (or the release of one or more configurations), wherein the one or more RRC messages include a cell identifier of the first cell and a configured uplink grant configuration identifier. Based on receiving the one or more RRC messages, the gNB-CU may send a message indicating the release of at least a configured uplink grant of a first cell of one or more configurations (or the release of one or more configurations) to the gNB-DU, wherein the message includes at least one of the following: a cell identifier of the first cell and an identifier indicating the configuration of the first cell, wherein the identifier includes at least one of the following: a configured uplink grant configuration identifier; a configured uplink grant RNTI; or a recovery identifier. Based on the embodiment, the gNB-DU avoids wasting radio resources due to unnecessary allocation of configured uplink grants.

[0360] In an example, the gNB-CU may receive one or more RRC messages from a wireless device indicating release of at least a configured uplink grant of the first cell (or release of one or more configurations) of one or more configurations of the first cell, wherein the one or more RRC messages include at least one of: one or more cell identifiers of the first cell; one or more configured uplink grant configuration identifiers; or a recovery identifier.

[0361] In an example, based on a cell identifier, the gNB-CU may identify that the first cell is a cell of the gNB-DU. Based on one or more RRC messages, the gNB-CU may determine to send an F1AP (F1 Application Protocol) message indicating a release of at least a configured uplink grant of the first cell (or a release of a configured uplink grant configuration). The F1AP message may include one or more RRC messages. The F1AP message may include at least one of: one or more cell identifiers of the first cell, and one or more identifiers indicating one or more configurations of at least one configured uplink grant of the first cell, wherein the identifier includes at least one of: a configured uplink grant configuration identifier; a configured uplink grant RNTI; or a recovery identifier. Based on the identification, the gNB-CU may send the F1AP message to the gNB-DU.

[0362] In an example, the F1AP message may include a configured uplink grant configuration identifier. For example, the F1AP message may include a recovery identifier. The F1AP message may include a configured uplink grant RNTI and a cell identifier of the first cell.

[0363] In an example, the F1AP message may include an indication of releasing or suspending or resuming or updating at least one configured uplink grant of the configured first cell (or a configuration of at least one configured uplink grant of the first cell). Based on at least one of the identity of the first cell and / or the cell identity, the indication may be associated with the at least one configured uplink grant (or configuration). Based on the identity of the first cell and / or at least one of the cell identity, the gNB-DU may identify at least one configured uplink grant (or configuration). Based on the identification, the gNB-DU may release or suspend or resume or update at least one configured uplink grant or configuration based on the indication. Based on the release or suspension or resumption or update, the gNB-DU may send an F1AP response message indicating the release or suspension or resumption or update. Based on the indication to be updated, the F1AP message may include a configured uplink grant configuration parameter, wherein the configured uplink grant configuration parameter is associated with the indication. Based on receiving the update indication, the gNB-DU may replace at least one configured uplink grant of the configured first cell (or the configuration of at least one configured uplink grant of the first cell) with the configured uplink grant configuration parameters. Based on receiving the release indication, the gNB-DU may release at least one configured uplink grant (or configuration) associated with the identity of the first cell and / or the cell identity in the F1AP message. Based on receiving the suspend indication, the gNB-DU may suspend at least one configured uplink grant (or configuration) associated with the identity of the first cell and / or the cell identity in the F1AP message. Based on receiving the resume indication, the gNB-DU may resume the suspended at least one configured uplink grant (or suspended configuration) associated with the identity of the first cell and / or the cell identity in the F1AP message.

[0364] In an example, the gNB-DU may store at least one configured uplink grant of the configured first cell or a configuration of at least one configured uplink grant of the first cell. Based on at least one of an identifier of the first cell and a cell identifier, the gNB-DU may identify at least one configured uplink grant of the configured first cell or a configuration of at least one configured uplink grant of the first cell. The identifier includes at least one of: a configured uplink grant configuration identifier; a configured uplink grant RNTI; or a recovery identifier. For example, the gNB-DU may store a mapping of an identifier and at least one of: at least one configured uplink grant of the configured first cell; or a configuration of at least one configured uplink grant of the first cell.

[0365] In an example, the gNB-DU may store a mapping of a configured uplink grant configuration identifier and at least one configured uplink grant of the configured first cell (or a configuration of at least one configured uplink grant of the first cell). The gNB-DU may store a mapping of a configured recovery identifier of the first cell and at least one configured uplink grant. The gNB-DU may store a mapping of parameters and at least one configured uplink grant of the configured first cell, wherein the parameters include a configured uplink grant RNTI of the at least one configured uplink grant of the first cell and a cell identifier of the first cell. Based on the mapping, the gNB-DU may identify the at least one configured uplink grant of the first cell.

[0366] Fig.24 An example of a configured uplink grant release in a CU DU architecture is shown. The UE may release at least one configured uplink grant of a configured first cell (or a configuration of at least one configured uplink grant of the first cell). Based on the release, the UE may send one or more RRC messages to the gNB-CU, wherein the one or more RRC messages include at least one of: a configured configured uplink grant configuration identifier; and a cell identity of the first cell. The first base station may include at least one gNB-CU and at least one gNB-DU. For example, the UE may send one or more RRC messages to the first base station via the second base station. Based on receiving the one or more RRC messages, the gNB-CU may send a F1AP message including at least one of an identity of the first cell and a cell identity. Based on receiving the F1AP message, the gNB-DU may release at least one configured uplink grant of the configured first cell (or a configuration of at least one configured uplink grant of the first cell). In response to the F1AP message, the gNB-DU may send a F1AP response message to the gNB-CU.

[0367] In the prior art, a wireless device may send a configured uplink grant configuration request message to a base station via a serving cell. In response to the configured uplink grant configuration request message, the base station may send the configured uplink grant configuration parameters of the serving cell via an RRC release message. The wireless device may require the configured uplink grant configuration parameters of another cell different from the serving cell. The wireless device may not send a configured uplink grant configuration request message to the base station until the other cell becomes the serving cell. The wireless device may lose the opportunity to request or use the configured uplink grant (configuration), which may result in an increase in power consumption and latency of uplink transmissions of the wireless device.

[0368] In an embodiment of the present disclosure, the wireless device may send a configured uplink grant configuration request message indicating one or more cells to the base station, wherein the one or more cells include cells for which the wireless device requests configured uplink grant configuration parameters or configured uplink grants. Based on the configured uplink grant configuration request message, the base station may send configured uplink grant configuration parameters for the one or more cells. The configured uplink grant configuration parameters may include at least one configured uplink grant for the one or more cells.

[0369] In an example, the UE may send a configured uplink grant configuration request message including one or more cell identifiers. The configured uplink grant configuration request message may include the requested configured uplink grant parameters, wherein the requested configured uplink grant configuration parameters may include at least one of the following: the number of configured uplink grant opportunities requested, wherein the number may be one or infinity; the request period of the configured uplink grant; the transport block size (TBS) requested for the configured uplink grant; and / or the time offset requested for the first configured uplink grant opportunity. For example, the configured uplink grant configuration request message may include one or more cell identifiers and at least one of the one or more requested configured uplink grant parameters. For example, the configured uplink grant configuration request message may include a list of cell identifiers and request the configured uplink grant parameters associated with the cell identifiers.

[0370] In an example, based on the configured uplink grant configuration request message, the base station may send one or more (configured uplink grant) configurations including at least one of the following: one or more cell identifiers and one or more configured uplink grant configuration identifiers. For example, each configured uplink grant configuration in the one or more configurations may include at least one of the following: one or more cell identifiers and a configured uplink grant configuration identifier.

[0371] In an example, a base station may determine one or more first base stations based on one or more cell identifiers. For example, based on the one or more cell identifiers, the base station may determine that the one or more first base stations may include one or more first cells of the one or more cell identifiers. The base station may send one or more Xn messages to the one or more first base stations. The base station may generate each Xn message associated with a first base station, wherein the first base station is a first base station in the one or more first base stations. Each Xn message of the first base station may include at least one of the following: a requested configured uplink grant parameter associated with the first base station; a configured uplink grant configuration identifier; and a UE identifier. The requested configured uplink grant parameter associated with the first base station may include a requested configured uplink grant parameter for one or more cells of the first base station. The base station may determine a configured uplink grant configuration identifier of the requested configured uplink grant parameter associated with the first base station. The UE identifier may include at least one of the following: a C-RNTI of the base station; a recovery identifier; and an S-TMSI. Based on receiving the one or more Xn messages, the one or more first base stations may send the configured uplink grant configuration parameters of the one or more first cells to the base station. The base station may send the configured uplink grant configuration parameters to the UE.

[0372] In an example, based on one or more configurations, the UE may send an uplink packet via the first cell using at least a configured uplink grant of the one or more configured first cells, wherein the one or more cell identifiers include a cell identifier of the first cell. For example, the UE may select the first cell. The UE may initiate an RRC procedure to establish or resume an RRC connection. The UE may find the cell identifier of the first cell among the one or more cell identifiers. The UE may identify the configuration of at least one configured uplink grant of the first cell based on the cell identifier of the first cell. Based on the identification, the UE may send an uplink packet using at least one configured uplink grant of the configuration.

[0373] Fig.25 An example of a configured uplink grant configuration request including a cell identifier is shown. A UE in an RRC connected state may send a configured uplink grant configuration request message to a base station, wherein the configured uplink grant configuration request message includes a cell identifier of a first cell. The UE may send a configured uplink grant configuration request message to the base station via a second cell. Based on the configured uplink grant configuration request message, the base station may send a configured uplink grant configuration parameter of the first cell.

[0374] The wireless device may receive at least one first radio resource control (RRC) message from a first cell, the first RRC message including: an indication of an RRC connection release; and a configuration of at least one preconfigured uplink resource (configured uplink grant) of the first cell. The wireless device may select a second cell. The wireless device may determine to establish an RRC connection via the second cell. Based on the determination, the wireless device may send one or more RRC messages for the RRC connection, wherein the one or more RRC messages include a cell identity of the first cell, the cell identity indicating the release of the at least one configured uplink grant.

[0375] The second cell may be different from the first cell.

[0376] The wireless device may send an identification of a configured uplink grant configuration of the wireless device (configured uplink grant configuration identifier).

[0377] Sending the configured uplink grant configuration identifier may include sending the configured uplink grant configuration identifier based on at least one of: one or more RRC messages not being responsive to transmission using at least one configured uplink grant; and releasing at least one configured uplink grant.

[0378] The one or more RRC messages may include a configured uplink grant configuration identifier.

[0379] The configuration of at least configuring the uplink grant may include a cell identity of the first cell.

[0380] In response to the one or more RRC messages, the wireless device may receive a confirmation indication that the configuration was released.

[0381] The wireless device may release the configuration of at least one configured uplink grant including releasing the configuration of at least one configured uplink grant based on at least one of: receiving an acknowledgement indication; or receiving an RRC response message in response to one or more RRC messages.

[0382] The one or more RRC messages include at least one of: an RRC setup request message;

[0383] RRC setup complete message; configured uplink grant configuration release request message; and configured uplink grant configuration request message.

[0384] Based on the determination to establish the RRC connection, the wireless device may send an RRC setup request message, wherein the RRC setup request message includes at least one of: a serving temporary mobile subscriber identity (S-TMSI); or a random value for contention resolution.

[0385] In response to the RRC setup request message, the wireless device may receive an RRC setup message.

[0386] In response to the RRC setup message, the wireless device may send an RRC setup complete message.

[0387] The RRC setup complete message may include at least one of: a cell identity of the first cell; and a configured uplink grant configuration identifier.

[0388] The configured uplink grant release request message includes at least one of: a cell identity of the first cell; and a configured uplink grant configuration identifier.

[0389] Releasing at least one configured uplink grant may include releasing at least the configured uplink grant in response to receiving an RRC setup message.

[0390] Releasing at least one configured uplink grant may include releasing the configuration.

[0391] The wireless device may select the second cell based on the signal quality of the cell exceeding a threshold.

[0392] The cell identity of the first cell may include at least one of the following: a physical cell identity; or a global cell identity.

[0393] Determining to establish the RRC connection may include determining to establish the RRC connection based on at least one of: there is uplink data to be transmitted; or a paging message is received.

[0394] The configuration of at least one configured uplink grant may include a configured uplink grant configuration identifier.

[0395] The at least one first RRC message may include an RRC release message.

[0396] The RRC response message may include at least one of: an RRC setup message; an RRC reconfiguration message; and a UE information response message.

[0397] The second base station may receive one or more radio resource control (RRC) messages from the wireless device, the one or more RRC messages instructing the wireless device to release at least one preconfigured uplink resource (configured uplink grant) of the first cell, wherein the one or more RRC messages include at least one of the following: a cell identifier of the first cell; and a configured uplink grant configuration identifier (configured uplink grant configuration identifier). The second base station may determine the first base station of the first cell based on the cell identifier. The second base station may send one or more RRC messages to the first base station.

[0398] The second base station may receive a confirmation indication from the first base station that the configuration is released in response to the one or more RRC messages.

[0399] The second base station may send an acknowledgement indication to the wireless device.

[0400] The first base station may send at least one first radio resource control (RRC) message to the wireless device, wherein the at least one first RRC message includes: an indication of RRC connection release; and a configuration of at least one preconfigured uplink resource (configured uplink grant) of the first cell. The first base station may receive one or more RRC messages from the second base station indicating that the wireless device releases at least one configured uplink grant, wherein the one or more RRC messages include at least one of the following: a cell identifier of the first cell; and a configured uplink grant configuration identifier (configured uplink grant configuration identifier). The first base station may release the configuration based on the one or more RRC messages.

[0401] In response to the one or more RRC messages, the first base station may send a confirmation indication to the wireless device via the second base station that the configuration is being released.

[0402] The wireless device may receive at least one first radio resource control (RRC) message from a first cell, the at least one first RRC message including: a suspension configuration to suspend an RRC connection; and a configuration of at least one preconfigured uplink resource (configured uplink grant) of the first cell. The wireless device may detect a failure to resume the RRC connection. Based on the failure, the wireless device may release the RRC connection. The wireless device may select a second cell. The wireless device may determine to establish an RRC connection via the second cell. Based on the determination, the wireless device may send one or more RRC messages indicating the release of at least one configured uplink grant.

[0403] The one or more RRC messages may include a cell identity or a recovery identity of the first cell.

[0404] Based on the one or more RRC messages including the cell identity of the first cell, the one or more RRC messages may include a configured uplink grant configuration identification (configured uplink grant configuration identifier) ​​of the wireless device.

[0405] The failure may include at least one of: expiration of an RRC timer; selection of a cell other than the third cell if the RRC timer is running; receipt of a fallback indication; receipt of a (RRC) rejection message; or failure to comply with an RRC response message.

[0406] The wireless device may send an RRC resume request message requesting to resume the RRC connection via the third cell.

[0407] Based on sending the RRC recovery request message, the wireless device may start an RRC timer.

[0408] The RRC response message may include at least one of: an RRC resume message; an RRC setup message; and an RRC release message.

[0409] The RRC reject message may not include a suspend indication.

[0410] The pause configuration may include a resume flag.

[0411] The wireless device may receive at least one first radio resource control (RRC) release message from a first cell, the at least one first RRC release message including a configuration of at least one pre-configured uplink resource (configured uplink grant) of the first cell. The wireless device may select a second cell. The wireless device may determine to establish an RRC connection via the second cell. Based on the determination, the wireless device may send one or more RRC messages indicating the release of the configuration.

[0412] The one or more RRC messages may include a cell identity and a configured uplink grant configuration identifier based on at least one of: releasing the RRC connection; and / or the first base station storing a mapping of the configured uplink grant configuration identifier and the configuration, wherein the first base station includes the first cell.

[0413] Releasing the RRC connection may include releasing the RRC connection based on at least one of: at least one RRC message indicating the RRC connection release; and detecting a failure to resume a suspended / suspended RRC connection.

[0414] The one or more RRC messages may include a resumption indicator based on at least one of: suspending the RRC connection; releasing a suspended / suspended RRC connection; or the first base station storing a mapping of the resumption indicator and the configuration.

[0415] Suspending the RRC connection may include suspending the RRC connection based on a suspension configuration, wherein the at least one configured uplink grant includes the suspension configuration.

[0416] The wireless device may send an RRC resume request message requesting to resume a suspended / suspended RRC connection.

[0417] Detecting the failure may include detecting the failure in response to sending the RRC recovery request message.

[0418] The pause configuration may include a resume flag.

[0419] The wireless device may select a second cell. The wireless device may initiate an RRC procedur...

Claims

1. A communication method, comprising: One or more radio resource control (RRC) messages are received by a base station central unit (BS-CU) from a wireless device via a second cell, wherein the one or more RRC messages: including a recovery identifier of the wireless device; as well as instructing the wireless device to release a first configured uplink grant configuration for a first cell in an RRC inactive state or an RRC idle state of the wireless device received from the BS-CU; as well as A message indicating a release of the first configured uplink grant configuration is sent to a base station distributed unit, BS-DU, associated with the first cell.

2. The method of claim 1, further comprising receiving, by the BS-CU from the BS-DU, the first configured uplink grant configuration of the first cell.

3. The method of claim 1, wherein: The message indicating the release includes a first configured uplink grant configuration identifier of the first configured uplink grant configuration.

4. The method of claim 1, wherein: The message indicating the release includes a first cell identifier of the first cell.

5. The method of claim 1, further comprising determining that the first cell is associated with the BS-DU.

6. The method of claim 1, wherein: The message indicating the release is an F1 application protocol message.

7. The method of claim 1, further comprising: determining, based on a first cell identifier, that the BS-DU is associated with the first cell; as well as Based on determining that the BS-DU is associated with the first cell, the message is sent to the BS-DU.

8. The method of claim 1, wherein: A first configured uplink grant configuration for the RRC inactive state or the RRC idle state is associated with a small data transmission (SDT) procedure.

9. A base station central unit BS-CU, comprising: one or more processors; and a memory storing instructions which, when executed by the one or more processors, cause the BS-CU to: One or more radio resource control (RRC) messages are received from the wireless device via the second cell, wherein the one or more RRC messages: including recovery identification for wireless devices; and instructing the wireless device to release a first configured uplink grant configuration for a first cell in an RRC inactive state or an RRC idle state of the wireless device received from the BS-CU; and A message indicating a release of the first configured uplink grant configuration is sent to a base station distributed unit, BS-DU, associated with the first cell.

10. The BS-CU according to claim 9, wherein: The instructions also cause the BS-CU to receive the first configured uplink grant configuration for the first cell from the BS-DU.

11. The BS-CU according to claim 9, wherein: The message indicating the release includes a first configured uplink grant configuration identifier of the first configured uplink grant configuration.

12. The BS-CU according to claim 9, wherein: The message indicating the release includes a first cell identifier of the first cell.

13. The BS-CU of claim 9, wherein: The instructions also cause the BS-CU to determine that the first cell is associated with the BS-DU.

14. The BS-CU according to claim 9, wherein: The message indicating the release is an F1 application protocol message.

15. The BS-CU of claim 9, wherein: The instructions also cause the BS-CU to: determining, based on a first cell identifier, that the BS-DU is associated with the first cell; and Based on determining that the BS-DU is associated with the first cell, the message is sent to the BS-DU.

16. The BS-CU of claim 9, wherein: A first configured uplink grant configuration for the RRC inactive state or the RRC idle state is associated with a small data transmission (SDT) procedure.

17. A non-transitory computer readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to: One or more radio resource control (RRC) messages are received from the wireless device via the second cell, wherein: The one or more RRC messages: Includes recovery identification for wireless devices; as well as instructing the wireless device to release a first configured uplink grant configuration for a first cell in an RRC inactive state or an RRC idle state of the wireless device received from a BS-CU; as well as A message indicating a release of the first configured uplink grant configuration is sent to a base station distributed unit, BS-DU, associated with the first cell.

18. The non-transitory computer readable medium of claim 17, wherein: The instructions cause the one or more processors to receive a first configured uplink grant configuration for the first cell from the BS-DU.

19. The non-transitory computer readable medium of claim 17, wherein: The message indicating the release includes a first configured uplink grant configuration identifier of the first configured uplink grant configuration.

20. The non-transitory computer readable medium of claim 17, wherein: The message indicating the release includes at least one of the following: a first configured uplink grant configuration identifier of the first configured uplink grant configuration; or a first cell identifier of the first cell.

Images