Paging for small data transmission

Abstract

A method can include initiating, by a wireless device in a radio resource control (RRC) non-connected state, a small data transmission (SDT) procedure based on a downlink reference signal. The example method can include selecting, based on a paging monitoring occasion (PO) occurring during the SDT procedure, the PO associated with the downlink reference signal. The example method can include receiving, based on the downlink reference signal and during the SDT procedure, downlink control information (DCI) via the PO.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 156,050, filed March 3, 2021, the entire contents of which are incorporated herein by reference. Attached Figure Description

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

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

[0005] Figure 2A and Figure 2B The new radio (NR) user plane and control plane protocol stacks are shown respectively.

[0006] Figure 3 It shows in Figure 2A An example of the services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A It shows the flow through Figure 2A An example downlink data stream of the NR user plane protocol stack.

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

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

[0010] Figure 6 This is an example diagram illustrating the RRC state transition of the UE.

[0011] Figure 7 An exemplary configuration in which OFDM symbols are grouped into NR frames is shown.

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

[0013] Figure 9 Three examples of bandwidth adaptation using NR carriers with configured BWPs are shown.

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

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

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

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

[0018] Figure 12A and Figure 12B Examples of three downlink and uplink beam management procedures are shown respectively.

[0019] Figure 13A , Figure 13B and Figure 13C Four-step contention-based random access procedures, two-step contention-free random access procedures, and another two-step random access procedure are shown respectively.

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

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

[0022] Figure 15 An example of a wireless device communicating with a base station is shown.

[0023] Figure 16A , Figure 16B , Figure 16C and Figure 16D An exemplary structure for uplink and downlink transmission is shown.

[0024] Figure 17 Uplink data transmission in a non-RRC_CONNECTED state is illustrated in an exemplary embodiment of this disclosure.

[0025] Figure 18A A small data transfer (SDT) based on RA with a four-step random access (RA) procedure is illustrated according to an exemplary embodiment of the present disclosure.

[0026] Figure 18B An exemplary embodiment of the present disclosure is shown, which is a RA-based SDT with a two-step RA procedure.

[0027] Figure 19AAn example of (pre)configuration authorization of one or more uplink radio resources in a non-RRC_CONNECTED state according to an embodiment of this disclosure is shown.

[0028] Figure 19B An example of (pre)configuration authorization of one or more uplink radio resources in non-RRC_CONNECTED is shown in accordance with an embodiment of this disclosure.

[0029] Figure 20 Examples of one or more subsequent transmissions of an aspect of the SDT according to an embodiment of this disclosure are shown.

[0030] Figure 21A An example of time window management for one or more subsequent transmissions of an aspect of the SDT according to an embodiment of this disclosure is shown.

[0031] Figure 21B An example of time window management for one or more subsequent transmissions of an aspect of the SDT according to an embodiment of this disclosure is shown.

[0032] Figure 22 An example of beam management for transmission and / or reception in a non-RRC_CONNECTED state is shown, according to an embodiment of the present disclosure.

[0033] Figure 23 An example is shown of the association between one or more DL RSs in a non-RRC_CONNECTED state and one or more paging opportunities (POs) according to an embodiment of this disclosure.

[0034] Figure 24 Examples of one or more paging timings that overlap with the duration associated with SDT in an embodiment according to this disclosure are shown.

[0035] Figure 25 Examples of one or more paging timings that overlap with the duration associated with SDT in an embodiment according to this disclosure are shown.

[0036] Figure 26 An example of bandwidth portion (BWP) switching (e.g., frequency change) for paging message reception is shown according to an embodiment of the present disclosure. Detailed Implementation

[0037] In this disclosure, various embodiments are presented in the form of examples of how the disclosed techniques can be implemented and / or how the disclosed techniques can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention. Indeed, after reading the specification, it will be apparent to those skilled in the art how to implement alternative embodiments. Embodiments of the invention should not be limited to any of the described exemplary embodiments. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create additional embodiments within the scope of this disclosure. Any diagrams highlighting functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, actions listed in any flowchart may be reordered or optionally used only in certain embodiments.

[0038] The implementation scheme can be configured to operate as needed. For example, in wireless devices, base stations, radio environments, networks, combinations thereof, etc., the disclosed mechanisms can be executed when certain criteria are met. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, combinations thereof, etc. Various exemplary implementation schemes can be applied when one or more criteria are met. Therefore, exemplary implementation schemes that selectively implement the disclosed protocols can be implemented.

[0039] A base station can communicate with a hybrid of wireless devices. Wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices may have certain specific capabilities, depending on the wireless device category and / or capabilities. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure may refer to a subset of the total number of wireless devices in the coverage area. For example, this disclosure may refer to multiple wireless devices having a given capability and being in a given sector of a base station using a given LTE or 5G version. Multiple wireless devices in this disclosure may refer to a selected set of wireless devices, and / or a subset of the total number of wireless devices in the coverage area performing according to the disclosed method, etc. Multiple base stations or multiple wireless devices may exist in the coverage area that may not conform to the disclosed method; for example, these wireless devices or base stations may be based on older versions of LTE or 5G technology.

[0040] In this disclosure, “a” (“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 this disclosure, the term “may” is interpreted as “may, for example”. In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a number of suitable possibilities that may or may not be used in one or more embodiments of various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more components of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude the inclusion of unlisted components in the element being described. In contrast, “consisting of” provides a complete enumeration of the one or more components of the element being described. As used herein, the term “based on” should be interpreted as “at least partially based on” rather than, for example, “based on only”. As used herein, the term “and / or” indicates any possible combination of the enumerated 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.

[0041] 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, 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 following the term “based on” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “in response to” (or equivalently “at least in response to”) indicates that the phrase following the phrase “in response to” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “depends on” (or equivalently “at least depends on”) indicates that the phrase following the phrase “depends on” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “adopts / uses” (or equivalently “at least adopts / uses”) indicates that the phrase following the phrase “adopts / uses” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations.

[0042] The term "configurable" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configurable" can also mean specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Similarly, the term "control messages generated in the device" can mean that the control messages have parameters that can be used to configure specific characteristics in the device or to perform certain actions in the device, regardless of whether the device is in an operational or non-operational state.

[0043] In this 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 one exemplary embodiment, when one or more messages include multiple parameters, it means that a parameter among the multiple parameters is present in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0044] Many of the proposed features are described as optional using the word "may" or parentheses. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the group of optional features. This 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: having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0045] Many elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has defined interfaces to other elements. Modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or combinations thereof, all of which may be behaviorally equivalent. For example, a module can be implemented as software routines written in a computer language 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 LabVIEW MathScript). It is possible to implement modules using physical hardware incorporating 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 frequently programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure connections between limited internal hardware modules on a programmable device. The aforementioned techniques are often combined to achieve the desired functional module results.

[0046] Figure 1A An example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented is shown. The mobile communication network 100 may, for example, be a Public Land Mobile Network (PLMN) operated by a network operator. Figure 1A As shown, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0047] CN 102 can provide the wireless device 106 with an interface to one or more data networks (DNs) (such as public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs). As part of the interface functionality, CN 102 can establish an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0048] RAN 104 can connect CN 102 to radio device 106 via radio communication through an air interface. As part of the radio communication, RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from RAN 104 to radio device 106 via the air interface is referred to as the downlink, while the communication direction from radio device 106 to RAN 104 via the air interface is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using Frequency Division Duplex (FDD), Time Division Duplex (TDD), and / or some combination of these two duplex technologies.

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

[0050] 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: Node B (associated with UMTS and / or 3G standards); Evolved Node B (eNB, associated with E-UTRA and / or 4G standards); Remote Radio Header (RRH); Baseband Processing Unit coupled to one or more RRHs; Repeater Node or Relay Node for extending the coverage area of ​​the donor Node; Next Generation Evolved Node B (ng-eNB); Generation Node B (gNB, associated with NR and / or 5G standards); 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).

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

[0052] Besides three-sector sites, other implementations of the base stations are also possible. For example, one or more base stations in RAN 104 can be implemented as sectorized sites with more or fewer than three sectors. One or more base stations in RAN 104 can be implemented as access points, baseband processing units coupled to several remote radio heads (RRHs), and / or repeater or relay nodes for extending the coverage area of ​​the donor node. The baseband processing units coupled to the RRHs can be part of a centralized or cloud RAN architecture, where the baseband processing units can be centralized in a pool of baseband processing units or virtualized. Repeater nodes can amplify and replay radio signals received from the donor node. Relay nodes can perform the same / similar functions as repeater nodes, but can decode the radio signals received from the donor node to remove noise before amplifying and replaying the radio signals.

[0053] RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna configurations and similar high-level transmission power. RAN 104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as coverage areas overlapping with the relatively large coverage areas provided by macrocell base stations. Small coverage areas can 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, in descending order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

[0055] Figure 1BAnother 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, 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). This can be compared with... Figure 1A These components are implemented and operated in the same or similar ways as the corresponding components described.

[0056] 5G-CN 152 provides UE 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. As part of the interface functionality, 5G-CN 152 can establish end-to-end connections between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CNs in 3GPP 4G networks, the foundation of 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 can be defined as network functions that provide services to other network functions via the interface. The network functions of 5G-CN 152 can 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).

[0057] like Figure 1B As shown, 5G-CN 152 includes Access and Mobility Management Functions (AMF) 158A and User Plane Functions (UPF) 158B. For ease of explanation, in Figure 1B These are shown as a single component, AMF / UPF 158. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. Functions that UPF 158B can perform include: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification supporting the 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 authentication), 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 pivot point supporting multihomed PDU sessions. UE 156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0058] The AMF 158A can perform functions such as: Non-Access Layer (NAS) signaling termination, NAS signaling security, Access Layer (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policies), network slicing support, and / or Session Management Function (SMF) selection. NAS can refer to functions operating between the CN and the UE, and AS can refer to functions operating between the UE and the RAN.

[0059] 5G-CN 152 may include, for clarity, not listed here. Figure 1B One or more additional network functions are shown in the diagram. 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 Openness Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

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

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

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

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

[0064] 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that NR can potentially connect to the 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although Figure 1B The diagram shows only one AMF / UPF 158, but a gNB or ng-eNB can connect to multiple AMF / UPF nodes to provide redundancy and / or load sharing across those multiple AMF / UPF nodes.

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

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

[0067] Figure 2A The diagram illustrates a five-layer NR user plane protocol stack implemented in UE 210 and gNB 220. At the bottom of the stack, the Physical Layer (PHY) 211 and 221 provide transport services to the higher layers and can correspond to Layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHY 211 and 221 include Media Access Control (MAC) 212 and 222, Radio Link Control (RLC) 213 and 223, Packet Data Convergence Protocol (PDCP) 214 and 224, and Service Data Application Protocol (SDAP) 215 and 225. These four protocols together can constitute Layer 2 or the Data Link Layer of the OSI model.

[0068] Figure 3 This illustrates an example of services provided between protocol layers in the NR user plane protocol stack. From Figure 2A and Figure 3Starting from the top, 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 the DN. The PDU session can have one or more QoS flows. The CN's UPF (e.g., UPF 158B) can map IP packets to these one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or error rate). SDAPs 215 and 225 can perform mapping / demapping between these one or more QoS flows and one or more data radio bearers. The mapping / demapping between QoS flows and data radio bearers can be determined by SDAP 225 at gNB 220. SDAP 215 at UE 210 can learn the mapping between QoS flows and data radio bearers through reflected mapping or control signaling received from gNB 220. For reflective mapping, the SDAP 225 at gNB 220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP 215 at UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0069] PDCP 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, can perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from their intended source. PDCP 214 and 224 can perform retransmission of undelivered packets, reordering and repackaging of packets, and removal of duplicate packets received due to, for example, intra-gNB handover. PDCP 214 and 224 can perform packet duplication to increase the likelihood of packet reception and remove any duplicate packets at the receiver. Packet duplication can be suitable for services requiring high reliability.

[0070] although Figure 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique 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). Split bearers are those that occur 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 / demapping split radio bearers between RLC channels belonging to a cell group.

[0071] RLCs 213 and 223 can respectively perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222. RLCs 213 and 223 can support three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM). Based on the transmission mode the RLC is operating in, the RLC can perform one or more of the aforementioned functions. RLC configuration can be based on each logical channel, independent of parameter sets and / or Transmission Time Interval (TTI) duration. Figure 3 As shown, RLC 213 and 223 can provide RLC channels as services to PDCP 214 and 224, respectively.

[0072] MACs 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing data units belonging to one or more logical channels into / from transport blocks (TBs) delivered to / from PHYs 211 and 221. MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority processing between UEs by means of dynamic scheduling. Scheduling can be performed for downlink and uplink in gNB 220 (at MAC 222). MACs 212 and 222 can be configured to perform error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), priority processing between logical channels of UE 210 by means of logical channel priority ordering, and / or padding. MACs 212 and 222 may support one or more parameter sets and / or transmission timing. In the example, the mapping constraints in logical channel priority ordering can control which set of parameters and / or transmission timing the logical channel can use. For example... Figure 3 As shown, MAC 212 and 222 can provide logical channels as services to RLC 213 and 223.

[0073] PHYs 211 and 221 can perform transport-to-physical channel mapping and digital and analog signal processing functions for transmitting and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHYs 211 and 221 can perform multi-antenna mapping. For example... Figure 3 As shown, PHYs 211 and 221 can provide one or more transport channels as services to MACs 212 and 222.

[0074] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4AThe diagram illustrates the downlink data flow through the NR user plane protocol stack to generate three IP packets (n, n+1, and m) of two TB at the gNB 220. The uplink data flow through the NR user plane protocol stack can be compared with... Figure 4A The downlink data flow described in the text is similar.

[0075] Figure 4A The downlink data flow begins when SDAP 225 receives three IP packets from one or more QoS flows and maps those three packets to a radio bearer. Figure 4A In SDAP 225, IP packets n and n+1 are mapped to the first radio bearer 402, and IP packet m is mapped to the second radio bearer 404. The SDAP header (in...) Figure 4A Data units marked with "H" are added to IP packets. Data units originating from / going to a higher protocol layer are called lower protocol layer Service Data Units (SDUs), and data units originating from / going to a lower protocol layer are called higher protocol layer Protocol Data Units (PDUs). Figure 4A As shown, the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and is the PDU of SDAP 225.

[0076] Figure 4A The remaining protocol layers can perform their associated functions (e.g., regarding...). Figure 3 This involves adding the corresponding headers and forwarding their output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., as...). Figure 4A (As shown in the image regarding IP packet m) and forwards its output to MAC 222. MAC 222 can multiplex many RLC PDUs and can attach MAC subheaders to RLC PDUs to form transport blocks. In NR, MAC subheaders can be distributed throughout MAC PDUs, such as... Figure 4A As shown in the diagram. In LTE, the MAC sub-header 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 sub-header can be computed before the complete MAC PDU is assembled.

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

[0078] Figure 4B The diagram further illustrates the MAC control element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B This shows two MAC CEs inserted into the MAC PDU. Downlink transmissions can be initiated at the beginning of the MAC PDU (e.g., ...). Figure 4B (As shown in the diagram) and a MAC CE is inserted at the end of the uplink transmission of the MAC PDU. The MAC CE can 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 for PDCP repeated detection, channel state information (CSI) reports, 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 with a format similar to that described with respect to the MAC SDU may precede the MAC CE, and the MAC CE may be identified by a reserved value in the LCID field indicating the type of control information included in the MAC CE.

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

[0080] Figure 5A and Figure 5BThe mappings between logical channels, transport channels, and physical channels are shown for both downlink and uplink. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels carrying control and configuration information in the NR control plane, or as service channels carrying data in the NR user plane. Logical channels can be classified as dedicated logical channels for 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:

[0081] - Paging Control Channel (PCCH), which carries paging messages for paging UEs whose location is unknown to the network at the cell level;

[0082] - Broadcast Control Channel (BCCH), which carries system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIB), wherein the system information messages can be used by the UE to obtain information about how the cell is configured and how to operate within the cell;

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

[0084] - Dedicated Control Channel (DCCH), used to carry control messages to a specific UE / carry control messages from a specific UE to configure that UE; and

[0085] - Dedicated Service Channel (DTCH), which is used to carry user data to a specific UE or carry user data from a specific UE.

[0086] 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:

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

[0088] - Broadcast channel (BCH), which is used to carry MIBs from the BCCH;

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

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

[0091] - Random Access Channel (RACH), which is used to allow a UE to access the network without any prior scheduling.

[0092] The PHY can use physical channels to transfer information between processing levels of the PHY. A physical channel can be a set of associated time-frequency resources used to carry information from one or more transport channels. The PHY can generate control information to support lower-level PHY operations and provide this 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:

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

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

[0095] - The Physical Downlink Control Channel (PDCCH) carries downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorizations, and uplink power control commands;

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

[0097] - The Physical Uplink Control Channel (PUCCH), which carries the UCI, including HARQ acknowledgments, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and

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

[0099] Similar to the physical control channel, the physical layer generates physical signals to support low-level physical layer operations. For example... Figure 5A and Figure 5B As shown, 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.

[0100] Figure 2B An exemplary NR control plane protocol stack is shown. Figure 2BAs shown, the NR control plane protocol stack can 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 has Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

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

[0102] RRC 216 and 226 can provide control plane functionality between UE 210 and gNB 220, or more generally between UE 210 and RAN. RRC 216 and 226 can provide control plane functionality between UE 210 and gNB 220 via signaling messages known as RRC messages. RRC messages can be transmitted between UE 210 and RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. MAC can multiplex control plane and user plane data into the same transport block (TB). RRC 216 and 226 can provide control plane functions such as: broadcasting system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance, and release of RRC connections 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 such reporting; detection and recovery of radio link failures (RLFs); and / or NAS messaging. As part of establishing an RRC connection, RRC 216 and 226 can establish an RRC context, which may involve configuring parameters for communication between UE 210 and RAN.

[0103] Figure 6 This is an example diagram illustrating the RRC state transition of the UE. The UE can interact with... Figure 1A The wireless device 106 described in the document Figure 2A and Figure 2B The UE 210 depicted herein is the same as or similar to any other wireless device described in this disclosure. Figure 6 As shown, the UE can be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0104] 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 RAN 104 as depicted herein; Figure 1B One of gNB 160 or ng-eNB 162 described herein; Figure 2A and Figure 2B The gNB220 depicted in this disclosure; or any other base station described herein. A base station connected to a UE may have an RRC context for that 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., relating to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. When in RRC connection 602, the UE's mobility 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 the 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 a cell transfer to one of the neighboring base stations based on the reported measurements. The RRC state can be changed from RRC connection 602 to RRC idle 604 through connection release procedure 608, or to RRC inactive 606 through connection deactivation procedure 610.

[0105] In RRC idle 604, an RRC context may not have been established for the UE. In RRC idle 604, the UE may not have an RRC connection with the base station. When in RRC idle 604, the UE may be in sleep mode most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in each discontinuous reception cycle) to monitor paging messages from the RAN. The UE's mobility can be managed by the UE through a procedure called cell reselection. The RRC state can be transitioned from RRC idle 604 to RRC connected 602 via connection establishment procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0106] In RRC inactivity 606, the previously established RRC context is maintained in both the UE and the base station. This allows for a faster transition to RRC connection 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactivity 606, the UE can be in a sleep state, and the UE's mobility can be managed by the UE via cell reselection. The RRC state can transition from RRC inactivity 606 to RRC connection 602 via connection resumption procedure 614, or to RRC idle 604 via connection release procedure 616, which can be the same as or similar to connection release procedure 608.

[0107] RRC states can be associated with mobility management mechanisms. 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 events via paging messages without having to broadcast paging messages across the entire mobile network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 allow the network to track the UE at the cell group level, so that paging messages can be broadcast on the cells in the cell group where the UE is currently camped, rather than across the entire mobile network. Mobility management mechanisms for RRC Idle 604 and RRC Inactive 606 track the UE at the cell group level. These mobility management mechanisms can do this using groupings of different granularities. For example, there can be three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas called tracking areas and identified by a Tracking Area Identifier (TAI).

[0108] A tracking area can be used to track the UE at the CN level. The CN (e.g., CN 102 or 5G-CN 152) can provide the UE with a list of TAIs associated with the UE's registration area. If the UE moves to a cell associated with a TAI not included in the list of TAIs associated with the UE's registration area via cell reselection, the UE can 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.

[0109] RAN areas can be used to track UEs at the RAN level. For a UE in an RRC inactive 606 state, a RAN notification area can be assigned to that UE. A RAN notification area can include one or more cell identifiers, a list of RAIs, or a list of TAIs. In the example, a base station can belong to one or more RAN notification areas. In the example, a cell can belong to one or more RAN notification areas. If a UE moves via cell reselection to a cell not included in its assigned RAN notification area, the UE can perform a notification area update to update its RAN notification area.

[0110] The base station that stores the RRC context for the UE, or the UE's last serving base station, can 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 when the UE remains in the anchor base station's RAN notification area and / or during the period when the UE remains in RRC inactivity 606.

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

[0112] In NR, physical signals and physical channels (about Figure 5A and Figure 5BThe data discussed can be mapped onto Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data via F orthogonal subcarriers (or tones). Before transmission, the data can be mapped onto a series of complex symbols called source symbols (e.g., M-QAM or M-PSK symbols) and divided into F parallel symbol streams. These F parallel symbol streams can be treated as if they were in the frequency domain and used as input to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block takes F source symbols at a time (one source symbol from each of the F parallel symbol streams) and uses 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. These F time-domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and upsampling, 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 an FFT block before being processed by the IFFT block. This operation produces OFDM symbols precoded with Discrete Fourier Transform (DFT) and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The inverse processing of the OFDM symbols at the receiver can be performed using the FFT block to recover the data mapped to the source symbols.

[0113] Figure 7 An exemplary configuration of NR frames in which OFDM symbols are grouped is shown. NR frames can be identified by a System Frame Number (SFN). SFNs can repeat at a period of 1024 frames. As shown, the duration of an NR frame can be 10 milliseconds (ms) and can include 10 subframes with a duration of 1 ms. Subframes can be divided into time slots, which include, for example, 14 OFDM symbols per time slot.

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

[0115] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Parameter sets with higher subcarrier spacing have shorter time slot durations and correspondingly more time slots per subframe. Figure 7 This illustrates the transmission structure of the time slot duration and per subframe time slot related to the parameter set (for ease of explanation). Figure 7 (The parameter set with a subcarrier spacing of 240 kHz is not shown in the diagram). Subframes in NR can be used as a time reference independent of the parameter set, while time slots can be used as units for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be separated from the time slot duration and begin at any OFDM symbol, continuing to transmit as many symbols as needed. These partial time slot transmissions can be referred to as micro-time slots or sub-time slot transmissions.

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

[0117] Figure 8This illustrates a single set of parameters used across the entire bandwidth of an NR carrier. In other exemplary configurations, multiple parameter sets can be supported on the same carrier.

[0118] NR can support wide carrier bandwidths (e.g., up to 400MHz for a subcarrier spacing of 120kHz). Not all UEs can receive the full carrier bandwidth (e.g., due to hardware limitations). Moreover, receiving the full carrier bandwidth can be prohibitively expensive in terms of UE power consumption. In the example, to reduce power consumption and / or for other purposes, the UE can adjust the size of its receive bandwidth based on the amount of traffic it plans to receive. This is called bandwidth adaptation.

[0119] The NR defines a Bandwidth Component (BWP) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In the example, a BWP can be defined by a subset of consecutive Relays (RBs) on a carrier. A UE can be configured (e.g., via the RRC layer) to have 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 the serving cell can be active. These one or more BWPs can be referred to as the active BWPs of the serving cell. When the serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0120] For unpaired spectrum, if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP, then the downlink BWP from the set of configured downlink BWPs can link with the uplink BWP from the set of configured uplink BWPs. For unpaired spectrum, the UE can expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

[0121] For a set of configured downlink BWPs on a primary cell (PCell), the base station can 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 domains where a UE can locate control information. The search space can be a UE-specific search space or a shared search space (potentially usable by multiple UEs). For example, the base station can configure a shared search space for the UE on a PCell or primary / secondary cell (PSCell) within an active downlink BWP.

[0122] For an uplink BWP in the set of configured uplink BWPs, the BS can configure one or more resource sets for the UE to transmit one or more PUCCHs. The UE can receive downlink reception (e.g., PDCCH or PDSCH) in the downlink BWP based on the configured set of parameters (e.g., subcarrier spacing and cyclic prefix duration) used for the downlink BWP. The UE can transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP based on the configured set of parameters (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0123] One or more BWP indicator fields can be provided in the downlink control information (DCI). The value of the BWP indicator field can indicate which BWP in the 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 can indicate the active uplink BWP for one or more uplink transmissions.

[0124] The base station can semi-statically configure a default downlink BWP for the UE within a 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 can be the initial active downlink BWP. The UE can determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0125] The base station can configure the BWP inactivity timer value for the UE for the PCell. The UE can start or restart the BWP inactivity timer at any appropriate time. For example, the UE can start or restart the BWP inactivity timer when: (a) the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or (b) the UE detects a DCI indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect a DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE can run the BWP inactivity timer toward its 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 can switch from the active downlink BWP to the default downlink BWP.

[0126] In the example, the base station can semi-statically configure the UE using one or more BWPs. The UE can 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 the expiration of a BWP inactivity timer (e.g., in the case that the second BWP is the default BWP).

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

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

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

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

[0131] Figure 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 located directly adjacent to each other within the band. In the intra-band discontinuous configuration 1004, the two CCs are aggregated in the same frequency band (band A) and separated by a certain gap within the band. In the inter-band configuration 1006, the two CCs are located in frequency bands (band A and band B).

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

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

[0134] Configurable SCells for the UE can be activated and deactivated based on factors such as traffic and channel conditions. Deactivating an SCell can mean ceasing PDCCH and PDSCH reception on the SCell, and ceasing PUSCH, SRS, and CQI transmissions on the SCell. (The remaining text appears to be incomplete and requires further context.) Figure 4B The MAC CE is used to activate and deactivate configured SCells. For example, the MAC CE can use a bitmap (e.g., one bit per SCell) to indicate which SCells for the UE (e.g., in a subset of configured SCells) are activated or deactivated. Configured SCells can be deactivated in response to the expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

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

[0136] Figure 10B This illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. Figure 10BIn the example, 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 can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can 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) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In the example, if Figure 10B If the aggregated cell depicted is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell will transmit UCIs associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by allocating UCI transmissions between PCell 1021 and PSCell 1061.

[0137] A physical cell ID and a cell index can be assigned to a cell that includes a downlink carrier and an optional uplink carrier. The physical cell ID or cell index can identify the cell's downlink carrier and / or uplink carrier, for example, depending on the context in which the physical cell ID is used. The physical cell ID can be determined using synchronization signals transmitted on the downlink component carrier. The cell index can be determined using RRC messages. In this disclosure, the physical cell ID can be referred to as a carrier ID, and the cell index can be referred to as a carrier index. For example, when this disclosure relates to a first physical cell ID for a first downlink carrier, this disclosure can mean that the first physical cell ID is used for a cell that includes the first downlink carrier. The same / similar concepts can be applied, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, this specification can mean that a cell including that first carrier is activated.

[0138] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In the example, the HARQ entity can operate on the serving cell. Transport blocks can be generated based on the assignment / authorization of each serving cell. Transport blocks and their potential HARQ retransmissions can be mapped to the serving cell.

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

[0140] Figure 11A An example of the structure and location of SS / PBCH blocks is shown. A burst of SS / PBCH blocks can include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as...). Figure 11A (As shown). Bursts can be transmitted periodically (e.g., every 2 frames or 20 ms). Bursts can be limited to half-frames (e.g., the first half-frame lasting 5 ms). It should be understood that... Figure 11A This is an example, and these parameters (the number of SS / PBCH blocks per burst, the burst period, and the burst location within a frame) can be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the cell's parameter set or subcarrier spacing; configuration performed by the network (e.g., using RRC signaling); or any other suitable factor. In this example, the UE can 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.

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

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

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

[0144] The PBCH can use QPSK modulation and forward error correction (FEC). FEC can use polarity coding. One or more symbols spanned by the PBCH can carry one or more DMRS for PBCH demodulation. The PBCH can include an indication of the cell's current system frame number (SFN) and / or an SS / PBCH block timing index. These parameters can help the UE synchronize time with the base station. The PBCH can include a Master Information Block (MIB) to provide one or more parameters to the UE. The MIB can be used by the UE to locate the Residual Minimum System Information (RMSI) associated with the cell. The RMSI can include System Information Block Type 1 (SIB1). SIB1 can contain information required for the UE to access the cell. The UE can use one or more parameters of the MIB to monitor the PDCCH that can be used to schedule the PDSCH. The PDSCH can include SIB1. SIB1 can be decoded using the parameters provided in the MIB. The PBCH can indicate that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE can point to a frequency. The UE can search for SS / PBCH blocks at the frequency pointed to by the UE.

[0145] The UE may assume that one or more SS / PBCH blocks transmitted using 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 blocks transmitted with different SS / PBCH block indices.

[0146] SS / PBCH blocks (e.g., those within a half-frame) can be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​the cell). In the example, the first SS / PBCH block can be transmitted in the first spatial direction using the first beam, and the second SS / PBCH block can be transmitted in the second spatial direction using the second beam.

[0147] In the example, within the carrier's frequency range, the base station can transmit multiple SS / PBCH blocks. In the example, the first PCI of the first SS / PBCH block among the multiple SS / PBCH blocks can be different from the second PCI of the second SS / PBCH block among the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted at different frequency locations can be different or the same.

[0148] CSI-RS can be transmitted by the base station and used by the UE to acquire Channel State Information (CSI). The base station can utilize one or more CSI-RS to configure the UE for channel estimation or any other suitable purpose. The base station can utilize one or more of the same / similar CSI-RS to configure the UE. The UE can measure the one or more CSI-RS. The UE can estimate the downlink channel state and / or generate a CSI report based on the measurements of the one or more downlink CSI-RS. The UE can provide the CSI report to the base station. The base station can use the feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

[0149] The base station can semi-statically configure the UE using one or more CSI-RS resource sets. CSI-RS resources can be associated with location and periodicity in the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can instruct the UE that CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

[0150] The base station can configure the UE to report CSI measurements. The base station can configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with multiple CSI report timings and / or periods. For aperiodic CSI reporting, the base station can request CSI reports. For example, the base station can command the UE to measure configured CSI-RS resources and provide CSI reports related to the measurements. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reports. The base station can configure the UE using CSI-RS resource sets and CSI reports using RRC signaling.

[0151] CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE can be configured to use the same OFDM symbols for both the downlink CSI-RS and the 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 block (PRB) configured for the CORESET. The UE can also be configured to use the same OFDM symbols for both the downlink CSI-RS and the SS / PBCH block when the downlink CSI-RS and SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block.

[0152] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, 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. 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 using the number (e.g., maximum number) of frontload DMRS symbols used for PDSCH. A DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, a DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, a DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. The radio network can (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, where DMRS locations, DMRS types, and / or scrambling sequences can be the same or different. The base station can use the same precoding matrix to transmit downlink DMRS and the corresponding PDSCH. The UE can use one or more downlink DMRS to perform consistent demodulation / channel estimation of the PDSCH.

[0153] In the example, the transmitter (e.g., a base station) can use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter can use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices can differ based on the first and second bandwidths being different. The UE can assume that the same precoder matrix is ​​used across the set of PRBs. This set of PRBs can be represented as a Precoder Resource Block Group (PRG).

[0154] A PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS exists on one or more layers of the PDSCH. A higher layer may configure up to three DMRS for the PDSCH.

[0155] Downlink PT-RS can be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS can depend on RRC configuration. The presence and / or type of downlink PT-RS can be configured UE-specifically using a combination of RRC signaling and / or associated with one or more parameters (e.g., modulation and coding scheme (MCS)) that can be indicated by DCI for other purposes. When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters including at least one MCS. NR networks can support multiple 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 employ the same precoding for both 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. Downlink PT-RS can be limited to the UE's scheduled time / frequency duration. Downlink PT-RS can be transmitted on symbols to facilitate phase tracking at the receiver.

[0156] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station can use uplink DMRS to perform consistent demodulation of one or more uplink physical channels. For example, the UE can transmit uplink DMRS with PUSCH and / or PUCCH. Uplink DMRS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure the UE using one or more uplink DMRS configurations. At least one DMRS configuration can support a frontload DMRS mode. Frontload DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS can be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols for PUSCH and / or PUCCH, which the UE can use to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DMRS structure for both downlink and uplink, where the DMRS location, DMRS type, and / or scrambling sequence of the DMRS can be the same or different.

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

[0158] Depending on the UE's RRC configuration, the uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not be present. The presence and / or type of the uplink PT-RS can be configured based on the UE through a combination of RRC signaling and / or one or more parameters indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least one 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 both 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 UE's scheduled time / frequency duration.

[0159] The UE can transmit SRS to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE allows the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station can use the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmissions from the UE. The base station can semi-statically configure the UE using one or more SRS resource sets. For each SRS resource set, the base station can configure the UE using one or more SRS resources. SRS resource set suitability can be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources in one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodic, aperiodic, etc.) can be transmitted at certain times (e.g., simultaneously). The UE can transmit one or more SRS resources from the SRS resource set. The NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can transmit SRS resources based on one or more trigger types, where the trigger types may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. In the 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 the example, when PUSCH and SRS are transmitted in the same time slot, the UE can be configured to transmit SRS after the transmission of PUSCH and the corresponding uplink DMRS.

[0160] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: SRS resource configuration identifier; number of SRS ports; temporal behavior of SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS); time slot, micro-time slot, and / or subframe level period; time slots of periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; initiating OFDM symbols for SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0161] An antenna port is defined such that a symbol on the antenna port, through the channel through which it is transmitted, can be inferred from another symbol on the same antenna port, through the same channel through which it is transmitted. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel (e.g., fading gain, multipath delay, etc.) used to transmit the second symbol on the antenna port from the channel used to transmit the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi-co-located (QCLed) if one or more large-scale properties can be inferred from the channel through which the second symbol on the second antenna port is transmitted. These 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 reception (Rx) parameters.

[0162] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamforming reference signals. The UE can perform downlink beam measurements and generate a beam measurement report based on downlink reference signals (e.g., Channel State Information Reference Signal (CSI-RS)). After setting up an RRC connection with the base station, the UE can perform the downlink beam measurement procedure.

[0163] Figure 11B An example of a Channel State Information Reference Signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11BThe square shown may represent a resource block (RB) within the cell's bandwidth. 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 can be configured for CSI-RS resource configuration via higher-layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in radio frames), CSI-RS power parameters, CSI-RS sequence parameters, Code Division Multiplexing (CDM) type parameters, frequency density, transport 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.

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

[0165] CSI-RS, such as Figure 11BThose shown (e.g., CSI-RS1101, 1102, 1103) can be transmitted by the base station and used by the UE for one or more measurements. For example, the UE can measure the Reference Signal Received Power (RSRP) configured with CSI-RS resources. The base station can configure the UE using a reporting configuration, and the UE can report RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In the example, the base station can 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 can indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE can receive downlink transmissions with 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 can determine the spatial domain filter for the transmit (Tx) beam based on the spatial domain filter corresponding to the Rx beam. If the UE does not have beam correspondence capability, the UE can perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The UE can perform the uplink beam selection procedure based on one or more Sounding Reference Signal (SRS) resources configured for the UE by the base station. The base station can select and indicate the UE's uplink beam based on measurements of one or more SRS resources transmitted by the UE.

[0166] In the beam management procedure, the UE can assess (e.g., measure) the channel quality of one or more beampup links, including beampup links containing transmit beams transmitted by the base station, and receive beams received by the UE. Based on this assessment, the UE can transmit a beam measurement report indicating one or more beampup 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).

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

[0168] Figure 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable the base station to perform measurements on the UE's Tx beam, for example, to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, an Rx beam sweep from the beam set (shown as an ellipse rotating clockwise in the bottom rows of U1 and U3, indicated by the dashed arrow). Beamforming at the base station can include, for example, an Rx beam sweep from the beam set (shown as an ellipse rotating counterclockwise in the top rows of U1 and U2, indicated by the dashed arrow). When the UE uses a fixed Tx beam, procedure U2 can be used to enable the base station to adjust its Rx beam. The UE and / or base station can perform procedure U2 using a smaller beam set than that used in procedure P1, or using a narrower beam than that used in procedure P1. This can be called beam refinement. The UE can execute procedure U3 to adjust its Tx beam when the base station is using a fixed Rx beam.

[0169] The UE can initiate a beam fault recovery (BFR) procedure based on the detection of a beam fault. The UE can transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE can detect a beam fault based on the determination that the quality of the beam pair link in the associated control channel is unsatisfactory (e.g., an error rate higher than the error rate threshold, received signal power lower than the received signal power threshold, timer expiration, etc.).

[0170] The UE can use one or more reference signals (RS) to measure the quality of the beamp-link, which may include one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRS). The quality of the beamp-link can be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, reference signal reception quality (RSRQ) value, and / or CSI value measured on the RS resources. The base station may indicate one or more DM-RS quasi-co-located (QCLed) RS resources and channels (e.g., control channels, shared data channels, etc.). The one or more DMRS of the RS resources and channels may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, etc.) from the transmission to the UE via the RS resources are similar to or the same as the channel characteristics from the transmission to the UE via the channels.

[0171] The network (e.g., gNB and / or the network's ng-eNB) and / or the UE can initiate a random access procedure. A UE in the RRC_IDLE state and / or RRC_INACTIVE state can initiate a random access procedure to request connection settings to the network. A UE can initiate a random access procedure from the RRC_CONNECTED state. A UE can initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or to acquire uplink timing (e.g., when the uplink synchronization state is not synchronized). A UE can initiate a random access procedure to request one or more System Information Blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). A UE can initiate a random access procedure for beam fault recovery requests. The network can initiate random access procedures for handover and / or for establishing time alignment for SCell additions.

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

[0173] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. These one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. These 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 these one or more RRC messages to one or more UEs. These one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). The UE may determine the time and frequency resources and / or uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313 based on these one or more RACH parameters. Based on these one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0174] The one or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) timings available for transmitting Msg 11311. These one or more PRACH timings may be predefined. These one or more RACH parameters may indicate one or more available sets of one or more PRACH timings (e.g., prach-ConfigIndex). These one or more RACH parameters may indicate a relationship between (a) one or more PRACH timings and (b) one or more reference signals. These one or more RACH parameters may indicate a relationship between (a) one or more preambles and (b) one or more reference signals. These one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, these one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH timings and / or the number of preambles mapped to SS / PBCH blocks.

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

[0176] Msg 1 1311 may include one or more preamble transmissions (e.g., 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). A preamble group may include one or more preambles. The UE may determine the preamble group based on path loss measurements and / or the magnitude 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 with an RSRP higher than 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 can select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0177] The UE can determine the preamble based on the one or more RACH parameters provided in configuration message 1310. For example, the UE can determine the preamble based on path loss measurement, RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters can indicate: the preamble format; the maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station can 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 can determine the preamble included in Msg 1 1311 based on the association. Msg 1 1311 can be transmitted to the base station via one or more PRACH timings. The UE can use one or more reference signals (e.g., SSB and / or CSI-RS) for selecting the preamble and for determining the PRACH timing. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) can indicate the association between the PRACH timing and the one or more reference signals.

[0178] If no response is received after the preamble transmission, the UE may perform a preamble retransmission. The UE may increase the uplink transmission power used for the preamble retransmission. The UE may select the initial preamble transmission power based on path loss measurements and / or the target received preamble power configured by the network. The UE may determine the preamble to be retransmitted 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 step size used for the preamble retransmission. The ramp step size may be the amount by which the uplink transmission power used for the retransmission is incrementally increased. If the UE determines that the same reference signal (e.g., SSB and / or CSI-RS) is used as in 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 configured by one or more RACH parameters (e.g., preambleTransMax), the UE can determine that the random access procedure has not been successfully completed.

[0179] The 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 was received by the base station. Msg 2 1312 may include a time comparison command that the UE can use to adjust the UE's transmission timing, a scheduling grant for transmitting Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg 2 1312. The UE can determine when to initiate a time window based on the PRACH timing in which it transmits the preamble. For example, the UE can initiate a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH timing starting from the end of the preamble transmission). This one or more symbols can be determined based on a set of parameters. The PDCCH can be in a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The UE can identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI can be used depending on one or more events that initiate a random access procedure. The UE can use a Random Access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH timing in which the UE transmits the preamble. For example, the UE can determine the RA-RNTI based on: the OFDM symbol index; the time slot index; the frequency domain index; and / or the UL carrier indicator of the PRACH timing. An example of an RA-RNTI is as follows:

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

[0181] Where s_id can be the index of the first OFDM symbol of the PRACH timing (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH timing in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH timing in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for NUL carriers and 1 for SUL carriers).

[0182] The UE may transmit Msg3 1313 in response to successful reception of Msg 2 1312 (e.g., using the resource identified in Msg 2 1312). Msg 3 1313 can be used for, for example... Figure 13A The diagram illustrates contention resolution in a contention-based random access procedure. In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to each UE. If these 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) can be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier from Msg 3 1313 (e.g., the TC-RNTI included in Msg 2 1312 if a C-RNTI is assigned, and / or any other suitable identifier).

[0183] Msg 4 1314 can be received after or in response to the transmission of Msg 3 1313. If Msg 3 1313 includes a C-RNTI, the base station will use the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have been successfully completed. If Msg 3 1313 includes a TC-RNTI (e.g., if the UE is in RRC_IDLE state or 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 identity MAC CE that matches (e.g., is transmitted) the CCCH SDU sent in Msg 3 1313, the UE can determine that contention resolution was successful and / or the UE can determine that the random access procedure was successfully completed.

[0184] The UE can be configured with Supplemental Uplink (SUL) carriers and Normal Uplink (NUL) carriers. Initial access (e.g., random access procedure) can be supported on the uplink carriers. For example, the base station can configure two separate RACH configurations for the UE: one for the SUL carrier and another for the NUL carrier. To enable random access in a cell configured with an SUL carrier, the network can indicate which carrier (NUL or SUL) to use. For example, the UE can determine the SUL carrier if the measured quality of one or more reference signals is below a broadcast threshold. Uplink transmissions during the random access procedure (e.g., Msg 11311 and / or Msg 3 1313) can be preserved on the selected carrier. In one or more cases, the UE can switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE can determine and / or switch uplink carriers for Msg 1 1311 and / or Msg 3 1313 based on channel clarity assessment (e.g., listen before speaking).

[0185] Figure 13B This illustrates a two-step contention-free random access procedure. (Compared to...) Figure 13A Similar to the four-step contention-based random access procedure shown, the base station can transmit configuration message 1320 to the UE before the procedure is initiated. Configuration message 1320 may be similar to configuration message 1310 in some respects. Figure 13B The program shown involves the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 can be similar in some respects to... Figure 13A The Msg 1 1311 and Msg2 1312 are shown. (As from...) Figure 13A and Figure 13B It will be understood that a contention-free random access procedure may not include messages such as Msg 3 1313 and / or Msg 4 1314.

[0186] It can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover. Figure 13B The contention-free random access procedure is illustrated. For example, the base station may indicate or assign a preamble to the UE for Msg 1 1321. The UE may receive the preamble indication (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0187] After transmitting the preamble, the UE can initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of the RAR. In the event of a beam failure recovery request, the base station can configure the UE with a separate time window and / or a separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE can monitor the PDCCH transmission of the Cell RNTI (C-RNTI) addressed to the search space. Figure 13B In the contention-free random access procedure shown, the UE can determine that the random access procedure was 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 addresses to the C-RNTI, the UE can determine that the random access procedure was successfully completed. For example, if the UE receives a RAR including a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with the preamble identifier, the UE can determine that the random access procedure was successfully completed. The UE can determine that this response is an indication of confirmation of the SI request.

[0188] Figure 13C Another two-step random access procedure is shown. (Compared to...) Figure 13A and Figure 13B Similar to the random access procedure shown, the base station can transmit configuration message 1330 to the UE before the procedure is initiated. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. Figure 13C The program shown includes the transmission of two messages: Msg A1331 and Msg B1332.

[0189] Msg A1331 can be transmitted by the UE in uplink transmission. Msg A1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include... Figure 13A The content shown in Msg 3 1313 is similar to and / or equivalent to that of Msg 3 1313. Transport block 1342 may include UCIs (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 content similar to and / or equivalent to Msg 3 1313. Figure 13A and Figure 13B The Msg 2 1312 shown (e.g., RAR) and / or Figure 13A The content shown in Msg 4 1314 is similar to and / or equivalent to the content shown in Msg 4 1314.

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

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

[0192] Transport block 1342 may include data (e.g., delay-sensitive data), a UE identifier, security information, and / or device information (e.g., 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 advanced command; a power control command; an uplink grant (e.g., 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 can determine that the two-step random access procedure was successfully completed if: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342).

[0193] The UE and the base station can 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.

[0194] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling authorization indicating uplink radio resources and / or transmission format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in the payload transmitted by the base station on the 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-shared PDCCH (GC-PDCCH) common to the UE group.

[0195] A base station can attach one or more Cyclic Redundancy Check (CRC) parity bits to the DCI to aid in the detection of transmission errors. When the DCI is intended for use with a UE (or a group of UEs), the base station can scramble the CRC parity bits with the UE's identifier (or the UE group's identifier). Scrambling the CRC parity bits with the identifier can include a Modulo-2 appending (or an exclusive OR operation) of the identifier value and the CRC parity bits. This identifier can include the 16-bit value of the Radio Network Temporary Identifier (RNTI).

[0196] DCIs can be used for various 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 using the Paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. The P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled using the System Information RNTI (SI-RNTI) can indicate broadcast transmission of system information. The SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled using the Random Access RNTI (RA-RNTI) can indicate a Random Access Response (RAR). A DCI with CRC parity bits scrambled using the Cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled using the Temporary Cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). Figure 13AThe Msg 3 shown is Msg 3 of 1313. Other RNTIs configured by the base station for the UE may include: the 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), interrupt RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

[0197] 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 can be used for PUSCH scheduling in a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​can be used for PUSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used for PDSCH scheduling in a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used for PDSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide slot format indication to UE groups. DCI format 2_1 can be used to notify UE groups of physical resource blocks and / or OFDM symbols, where UEs may assume that transmission to UEs is not expected. DCI format 2_2 can be used to transmit Transmission Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission by one or more UEs. New DCI formats for new features can be defined in future versions. DCI formats can have different DCI sizes, or they can share the same DCI size.

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

[0199] Figure 14A An example of a CORESET configuration for the bandwidth portion is shown. A base station can transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET can include time-frequency resources in which a UE attempts to decode the DCI using one or more search spaces. The base station can configure the CORESET in the time-frequency domain. Figure 14A In the example, the first CORESET 1401 and the second CORESET 1402 appear at the first symbol in the time slot. The first CORESET 1401 overlaps with 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. CORESETs can have different numbers of resource blocks in the frequency domain.

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

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

[0202] like Figure 14B As shown, the UE can determine the time-frequency resources of the CORESET based on RRC messages. The UE can determine the CCE-to-REG mapping of the CORESET (e.g., interleaved or non-interleaved and / or mapping parameters) based on the CORESET's configuration parameters. The UE can determine the number of search space sets configured on the CORESET (e.g., up to 10) based on RRC messages. The UE can monitor a set of PDCCH candidates based on the configuration parameters of the search space sets. The UE can 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 locations, 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 can determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambling bits of the CRC parity bit of the DCI that match the RNTI value). The UE can process the information contained in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, etc.).

[0203] The UE can transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. Uplink control signaling transmission may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may transmit the HARQ acknowledgment after receiving the DL-SCH transport block. 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 can determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. 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 acknowledgment, CSI report, SR, etc.) via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The UE may use one of several PUCCH formats to transmit uplink control signaling via the PUCCH.

[0204] Five PUCCH formats can exist, and the UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols transmitted in the UCI and the number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. If more than one or two symbols are transmitted and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE can use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 can occupy between four and fourteen OFDM symbols and can 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 can use PUCCH format 1. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. If more than one or two symbols are transmitted and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 can occupy between four and fourteen OFDM symbols and can include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal overlay code, the UE can use PUCCH format 3. PUCCH format 4 can occupy between four and fourteen OFDM symbols and can include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal overlay code, the UE can use PUCCH format 4.

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

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

[0207] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of this 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. Figure 15 The diagram shows only one wireless device 1502 and one base station 1504, but it should be understood that a mobile communication network may include more than one UE and / or more than one base station, which have the same characteristics as... Figure 15 The same or similar configurations shown.

[0208] Base station 1504 can connect wireless device 1502 to the core network (not shown) via radio communication through air interface (or radio interface) 1506. The communication direction from base station 1504 to wireless device 1502 via air interface 1506 is referred to as the downlink, while the communication direction from wireless device 1502 to base station 1504 via air interface 1506 is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using some combination of FDD, TDD, and / or two duplex technologies.

[0209] In the downlink, data to be transmitted from base station 1504 to wireless device 1502 can be provided to processing system 1508 of base station 1504. This data can be provided to processing system 1508 via, for example, the core network. In the uplink, data to be transmitted from wireless device 1502 to base station 1504 can be provided to processing system 1518 of wireless device 1502. Processing systems 1508 and 1518 can implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, regarding… Figure 2A , Figure 2B , Figure 3 and Figure 4A The SDAP layer, PDCP layer, RLC layer, and MAC layer. Layer 3 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer. Figure 2B The RRC layer.

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

[0211] At base station 1504, receiving processing system 1512 can receive uplink transmissions from wireless device 1502. At wireless device 1502, receiving processing system 1522 can receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 can implement Layer 1 OSI functions. Layer 1 may include information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer. For receive processing, the PHY layer can perform tasks such as error detection, forward error correction decoding, deinterleaving, demapping of the transport channel to the physical channel, demodulation of the physical channel, MIMO or multi-antenna processing, etc.

[0212] like Figure 15 As shown, wireless device 1502 and base station 1504 may include multiple antennas. These multiple antennas can 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, wireless device 1502 and / or base station 1504 may have a single antenna.

[0213] Processing systems 1508 and 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 code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions discussed in this application. Although Figure 15 Although not shown, the transmission processing system 1510, transmission processing system 1520, receiving processing system 1512 and / or receiving 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 can be executed to perform one or more of their respective functions.

[0214] Processing system 1508 and / or 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 devices, discrete gate and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other function that enables wireless device 1502 and base station 1504 to operate in a wireless environment.

[0215] Processing system 1508 and / or 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 1526 may include software and / or hardware providing features and / or functions, such as speakers, microphones, keyboards, displays, touchpads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, FM radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or 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 aforementioned one or more peripheral devices. The processing system 1518 in wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in wireless device 1502. The power source may include one or more power sources, such as a battery, solar cell, fuel cell, or any combination thereof. Processing system 1508 and / or processing system 1518 may be connected to GPS chipset 1517 and GPS chipset 1527, respectively. GPS chipset 1517 and GPS chipset 1527 may be configured to provide geographic location information for wireless device 1502 and base station 1504, respectively.

[0216] Figure 16AAn exemplary structure for uplink transmission is shown. The baseband signal representing the physical uplink shared channel can perform one or more functions. These functions may include at least one of the following: scrambling; modulating scrambling bits to generate complex-valued symbols; mapping complex-valued modulation symbols onto one or more transport layers; transform precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals for antenna ports; and so on. 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, it can be achieved through... Figure 16A Generate CP-OFDM signals for uplink transmission. These functions are shown as examples, and other mechanisms are expected to be implemented in various implementation schemes.

[0217] Figure 16B An exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-value SC-FDMA or CP-OFDM baseband signal from the antenna port and / or a complex-value Physical Random Access Channel (PRACH) baseband signal. Filtering can be applied before transmission.

[0218] Figure 16C An exemplary structure for downlink transmission is shown. The baseband signal representing the physical downlink channel can perform one or more functions. These functions may include: scrambling coded bits in a codeword to be transmitted over the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transport layers; precoding the complex-valued modulation symbols for transmission at the antenna port; mapping the complex-valued modulation symbols for the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port; and so on. These functions are shown as examples, and other mechanisms are contemplated for implementation in various embodiments.

[0219] Figure 16D Another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-value OFDM baseband signal at the antenna port. Filtering can be applied before transmission.

[0220] A wireless device can receive one or more messages (e.g., RRC messages) from a base station, including configuration parameters for multiple cells (e.g., primary cell, secondary cell). The wireless device can communicate with at least one base station (e.g., two or more base stations in dual connectivity) via these cells. These 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, configuration parameters may include parameters for configuring physical and MAC layer channels, bearers, etc. For example, configuration parameters may include parameters indicating the values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0221] A timer can begin running once started and continues running until it stops or expires. If a 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 it can start from zero and expire once it reaches that value). The duration of a timer may not be updated until the timer stops or expires (e.g., due to BWP switching). Timers can be used to measure time periods / windows of a 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 these multiple ways of implementing a timer can be used to measure time periods / windows of a process. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In the example, instead of starting and expiring the random access response window timer, the time difference between two timestamps can be used. When the timer restarts, the measurement process for the time window can be restarted. Other exemplary implementations can be provided to restart the measurement of a time window.

[0222] Wireless devices can establish (e.g., set up, (re)establish, and / or restore) connections to the network (e.g., RRC connections) to transmit data. For example, to send data (e.g., data from a DTCH), the RRC state of the wireless device can be RRC_CONNECTED. For example, the wireless device may not perform (e.g., may not be allowed to perform, or may be prohibited) uplink transmissions in non-RRC_CONNECTED states (e.g., RRC_INACTIVE and / or RRC_IDLE states). This data can be DL (e.g., Mobile Termination (MT)) data and / or UL (e.g., Mobile Initiation (MO)) data.

[0223] For example, a wireless device may execute one or more procedures to establish a connection to the network in the RRC_INACTIVE state (or RRC_IDLE state). These procedures may include, for example, a connection setup procedure, a connection (re)establishment procedure, and / or a connection recovery procedure. For example, the wireless device may execute one or more procedures when, for example, DL (e.g., Mobile Termination (MT)) and / or UL (e.g., Mobile Initiation (MO)) data is available in the buffer. Based on one or more procedures (e.g., in response to successful completion of the connection setup or recovery procedure), the RRC state of the wireless device can transition from a non-RRC_CONNECTED state (or RRC_INACTIVE state and / or RRC_IDLE state) to the RRC_CONNECTED state. In the RRC_CONNECTED state, the wireless device may receive DL data and / or DL ​​signals via DL transmission, and / or may transmit UL data and / or UL signals via UL transmission. For example, after or in response to the absence of DL data (e.g., data to be received) and / or UL data (e.g., data to be transmitted) in the buffer, the wireless device can transition from the RRC_CONNECTED state to a non-RRC_CONNECTED state. To transition from the RRC_CONNECTED state to a non-RRC_CONNECTED state, the wireless device can execute a connection release procedure. A connection release procedure (e.g., an RRC release procedure) can cause a transition from the RRC state to the non-RRC_CONNECTED state.

[0224] Frequent RRC state transitions between RRC states (e.g., between non-RRC_CONNECTED and RRC_CONNECTED states) may require the wireless device to transmit and / or receive multiple control signals (e.g., RRC messages, MAC CE, and / or DCI) in one or more layers (e.g., RRC layer, MAC layer, and / or PHY layer).

[0225] For example, for RRC connection setup, the wireless device can transmit an RRC connection setup request to the base station and receive an RRC connection setup message as a response to the request. For example, for RRC connection restoration, the wireless device can transmit an RRC connection restoration request to the base station and receive an RRC connection restoration message as a response. For example, for RRC connection release, the wireless device can receive an RRC connection release request from the base station.

[0226] For example, for small data DL and / or UL transmissions that are available (or arrive) in a non-RRC_CONNECTED state, it may be inefficient for the wireless device to establish (or restore) a connection to the network (e.g., transition from a non-RRC_CONNECTED state to an RRC_CONNECTED state) and release the connection (e.g., transition from an RRC_CONNECTED state to a non-RRC_CONNECTED state) after performing the small data DL and / or UL transmission in the RRC_CONNECTED state, or in response to this. This can lead to increased unnecessary power consumption and / or signaling overhead. For example, the signaling overhead required to transmit the payload (e.g., control signaling overhead for RRC connection and / or RRC release) may be greater than the payload. For example, frequent RRC state transitions can lead to unnecessary power consumption and signaling overhead for the wireless device, for example, for small and infrequent DL and / or UL packets.

[0227] Examples of small and infrequent data packets can be traffic generated from smartphone applications, instant messaging (IM) services, heartbeat / keep-alive traffic from IM / email clients and other applications, push notifications from various applications, non-smartphone applications, wearable devices (e.g., location information), sensors (e.g., for periodically or event-triggered transmission of temperature and pressure readings), and / or smart meters and smart meter networks that send meter readings.

[0228] Transmissions in a non-RRC_CONNECTED state (e.g., DL and / or UL transmissions) can be beneficial. For example, a wireless device can transmit and / or receive one or more data packets in a non-RRC_CONNECTED state. Alternatively, a wireless device can transmit and / or receive one or more data packets without establishing a connection while maintaining the RRC state as non-RRC_CONNECTED.

[0229] For example, a wireless device can receive scheduling information (e.g., RRC messages and / or SIBs) from a base station, indicating one or more uplink radio resources in a non-RRC_CONNECTED state. One or more uplink radio resources can be used for infrequent data transmission. One or more uplink radio resources can be used for aperiodic data transmission. One or more uplink radio resources can be used for periodic data transmission. A wireless device can transmit one or more data packets via one or more radio resources while maintaining its RRC state in a non-RRC_CONNECTED state. For example, a wireless device can transmit one or more data packets without transitioning its RRC state to RRC_CONNECTED. Uplink transmission via one or more radio resources in a non-RRC_CONNECTED state can be efficient and flexible (e.g., for low-throughput short data bursts). Uplink transmission via one or more radio resources in a non-RRC_CONNECTED state can provide efficient signaling mechanisms (e.g., signaling overhead is less than payload). Uplink transmission via one or more radio resources in a non-RRC_CONNECTED state can reduce signaling overhead. Uplink transmissions via one or more radio resources in non-RRC_CONNECTED states can improve the battery performance of wireless devices. For example, a wireless device with intermittent small packets in a non-RRC_CONNECTED state can benefit from such uplink transmissions in that state.

[0230] Uplink transmissions in a non-RRC_CONNECTED state can be based on a random access (RA) procedure. For example, a wireless device can perform uplink transmissions by transmitting at least one preamble of the RA procedure. For example, a wireless device can transmit uplink data (e.g., SDU of DTCH) via Msg A PUSCH and / or Msg 3 PUSCH during the RA procedure. A wireless device can maintain (or preserve) the non-RRC_CONNECTED state in the RRC state during and / or after the RA procedure. For example, after completing the transmission of uplink data and / or completing the RA procedure, or in response to this, a wireless device can maintain (or preserve) the non-RRC_CONNECTED state in the RRC state.

[0231] Uplink transmissions in non-RRC_CONNECTED states can be based on pre-configured PUSCH resources. For example, a wireless device may receive resource configuration parameters indicating UL-authorized and / or UL-licensed pre-configured PUSCH resources. In non-RRC_CONNECTED states, a wireless device may use UL-authorized and / or UL-licensed pre-configured PUSCH resources to transmit uplink data (e.g., associated with DTCH).

[0232] Uplink data transmission in non-RRC_CONNECTED states can be referred to as Small Data Transmission (SDT), Early Data Transmission (EDT), and / or data transmission via (pre)configured uplink resources (PUR). For example, in this disclosure, SDT and / or EDT can be interchanged with uplink data transmission in non-RRC_CONNECTED states. For example, in this disclosure, radio resources used for SDT in non-RRC_CONNECTED states can be referred to as PUR. For example, uplink transmission based on RA procedures in non-RRC_CONNECTED states can be referred to as RA-based SDT, RA-based EDT, EDT, etc. For example, uplink transmission based on (pre)configured grant in non-RRC_CONNECTED states can be referred to as (pre)configured granted SDT (CG-based SDT). One or more (pre)configured granted radio resources can be referred to as (pre)configured uplink resources (PUR), SDT resources, SDT resources, etc.

[0233] Figure 17 Uplink data transmission in a non-RRC_CONNECTED state is illustrated according to an exemplary embodiment of this disclosure. The wireless device can receive one or more messages including configuration parameters for uplink data transmission. The wireless device can receive one or more messages in the RRC_CONNECTED state. The wireless device can receive one or more messages in the non-RRC_CONNECTED state. One or more messages, such as system information blocks, can be broadcast. The one or more messages can be wireless device-specific, such as RRC messages, MAC CEs, and / or DCIs specific to the wireless device. For example, one or more messages include RRC release messages. Configuration parameters can indicate the scheduled and / or configured uplink grants and / or radio resources available for SDT during the non-RRC_CONNECTED state. For example, the wireless device can maintain the RRC state as non-RRC_CONNECTED after or during an SDT.

[0234] exist Figure 17In this context, the wireless device can determine whether to transition its RRC state from the RRC_CONNECTED state to a non-RRC_CONNECTED state. Upon receiving an RRC message or in response to it, the wireless device can determine whether to transition its RRC state to a non-RRC_CONNECTED state.

[0235] For example, a wireless device can receive an RRC message (e.g., an RRC release message) from a base station. The RRC message (e.g., an RRC release message) can indicate the release of an RRC connection from the network. In response to receiving the RRC message, the wireless device can execute an RRC release procedure. The RRC release procedure may include releasing and / or suspending established radio bearers and / or configured radio resources. The RRC release procedure may include suspending the RRC connection (e.g., if a signaling radio bearer (SRB) (e.g., SRB2) and / or at least one dedicated radio bearer (DRB) is set) and / or suspending established radio bearers. After receiving the RRC message (or executing the RRC release procedure) and / or in response to this, the wireless device can determine to transition the wireless device's RRC state from the RRC_CONNECTED state to a non-RRC_CONNECTED state.

[0236] exist Figure 17 In this context, a wireless device can determine whether to transition its RRC state from a non-RRC_CONNECTED state to an RRC_CONNECTED state. For example, the wireless device can execute a random access procedure to transition to the RRC_CONNECTED state. Alternatively, the wireless device can transition to the RRC_CONNECTED state without requiring a random access procedure.

[0237] For example, a wireless device can transition to the RRC_CONNECTED state via a random access procedure. For example, a wireless device can execute (and / or initiate) a random access procedure for an SDT. For example, a wireless device can execute a random access procedure as an RA-based SDT. A wireless device can execute (and / or initiate) a random access procedure for initial access. For example, initial access can be initiated based on receiving a paging message by the wireless device. For example, initial access can be initiated based on a cell (re)selection procedure performed by the wireless device. A wireless device can receive messages including an indication to transition to the RRC_CONNECTED state (e.g., Msg B, Msg 4, RRC setting, and / or RRC recovery messages). For example, upon receiving or in response to such a message, the wireless device can transition to the RRC_CONNECTED state.

[0238] For example, a wireless device can perform (and / or initiate) a CG-based SDT for uplink transmission of uplink data in a non-RRC_CONNECTED state. The wireless device can monitor the PDCCH in a non-RRC_CONNECTED state based on the CG-based SDT. For example, the CG-based SDT can require the wireless device to monitor the PDCCH, e.g., to receive a response to an uplink transmission and / or to receive uplink grants and / or downlink assignments. For example, the wireless device can monitor the PDCCH in response to uplink data transmission via the CG-based SDT. The wireless device can monitor the PDCCH during a time period predefined and / or configured by the base station for the wireless device (e.g., within a time window and / or time interval). During this time period, the wireless device can receive downlink control messages (e.g., DCI) via the PDCCH, including downlink assignments (e.g., scheduling downlink transmissions). The wireless device can receive messages including indications of transition to the RRC_CONNECTED state (e.g., RRC setting and / or RRC recovery) based on the downlink assignments. For example, upon receiving or in response to this message, the wireless device can transition to the RRC_CONNECTED state. In this case, the wireless device can establish an RRC connection to the network (or base station) via CG-based SDT. For example, the wireless device can establish an RRC connection to the network (or base station) without a random access procedure.

[0239] A wireless device may receive one or more configuration parameters from a base station that indicate and / or include the number of times (e.g., exemplary parameter name: NumOccasions) are available for one or more uplink radio resources. The number of times may indicate that one or more uplink radio resources are one-time use resources (or licenses) for a single uplink transmission. The number of times may indicate that one or more uplink radio resources are multiple uplink radio resources. The number of times may indicate that one or more uplink radio resources are one or more periodic radio resources.

[0240] For example, one or more uplink radio resources can be used for CG-based SDT and / or RA-based SDT. For example, a wireless device can receive one or more RRC messages (e.g., broadcast, multicast, and / or wireless device-specific messages) that include one or more configuration parameters. A wireless device can receive at least one of the one or more RRC messages in the RRC_CONNECTED state. A wireless device can receive at least one of the one or more RRC messages in a non-RRC_CONNECTED state.

[0241] A radio device may initiate a random access (RA) procedure (e.g., RA-based SDT and / or EDT) on a cell to transmit uplink data via the cell in a non-RRC_CONNECTED state. For example, the uplink data may be associated with a specific logical channel. For example, the uplink data may include a Service Data Unit (SDU) from a specific logical channel (e.g., DTCH). While performing the RA procedure and / or transmitting uplink data during the RA procedure, the radio device may maintain its RRC state in a non-RRC_CONNECTED state. In response to or after the completion of the RA procedure and / or the completion of uplink data transmission, the radio device may maintain the non-RRC_CONNECTED state.

[0242] The network or base station can indicate which cell is available for uplink data transmission (e.g., SDT and / or EDT) in a non-RRC_CONNECTED state. Radio devices can receive messages (e.g., broadcast, multicast, and / or unicast messages) from the base station via the cell indicating whether uplink data transmission on the cell is available in a non-RRC_CONNECTED state. For example, a message (e.g., broadcast, multicast, and / or unicast message) can indicate whether RA-based SDT (e.g., EDT) is available on the cell in a non-RRC_CONNECTED state. For example, a message (e.g., broadcast, multicast, and / or unicast message) can indicate whether CG-based SDT (e.g., PUR) is available on the cell in a non-RRC_CONNECTED state. For example, a message (e.g., broadcast, multicast, and / or unicast message) can indicate whether SDT (e.g., RA-based SDT and / or CG-based SDT) is available on the cell in a non-RRC_CONNECTED state. For example, the message could be a cell’s broadcast (multicast) system information block and / or an RRC message dedicated to wireless devices.

[0243] In the example, an RRC message (e.g., a system information block) received by the wireless device via the cell may include one or more parameters indicating whether the wireless device is permitted to perform uplink data transmission via the cell in a non-RRC_CONNECTED state. One or more parameters may be fields indicating whether the wireless device is permitted to initiate RA-based SDT on the cell. This indication can be true (e.g., RA-based SDT permitted) or false (e.g., RA-based SDT not permitted). The indication can also be the presence of the field (e.g., RA-based SDT permitted) or the absence of the field (e.g., RA-based SDT not permitted).

[0244] This field can indicate whether a wireless device is permitted to initiate RA-based SDT on the cell to transmit specific types of data. For example, specific types of data may include control plane (CP) data, user plane (UP) data, mobile initiation (MO) data (or call) and / or mobile termination (MT) data (or call), etc. An exemplary format for the CP and UP data fields could be:

[0245] cp-SDT ENUMERATED{true}OPTIONAL,--Need OR

[0246] up-SDT ENUMERATED{true}OPTIONAL,--Need OR.

[0247] cp-SDT (=true) and up-SDT (=true) can respectively indicate to the wireless device that it is allowed to initiate SDT for transmitting CP data and UP data.

[0248] This field indicates whether a wireless device is permitted to initiate RA-based SDT on the cell when connected to a specific type of network. For example, the specific type of network may include an Evolved Packet Core (EPC) network, a 5G Core (5GC) network, etc. This field indicates whether a wireless device is permitted to initiate RA-based SDT on the cell to transmit a specific type of data when connected to a specific type of network. An exemplary format for the field transmitting CP data via EPC or 5GC could be:

[0249] cp-SDT-EPC ENUMERATED{true}OPTIONAL,--Need OR

[0250] cp-SDT-5GC ENUMERATED{true}OPTIONAL,--Need OR.

[0251] cp-SDT-EPC (= True) and cp-SDT-5GC (= True) can respectively instruct the wireless device to initiate RA-based SDT for transmitting CP data via EPC and 5GC.

[0252] A radio device can initiate a RA-based SDT on a cell when one or more conditions are met. For example, one or more conditions might be whether an upper layer requests the establishment or resumption of an RRC connection, whether the radio device supports SDT for a specific type of data, or whether one or more parameters (e.g., via broadcast of a system information block) indicate that the radio device should initiate a RA-based SDT for a specific type of data when connected to a specific type of network. For example, for CP-SDT, when a radio device connects to a 5GC, it can initiate a RA-based SDT for CP data based on at least one of the following: an upper layer requesting the establishment or resumption of an RRC connection, CP-SDT available to the radio device, and / or a system information block including cp-SDT-5GC=true.

[0253] For SDT (e.g., RA-based SDT and / or CG-based SDT), the wireless device can determine the size of the transport block (e.g., the size of the message including uplink data). The transport block can include uplink data transmitted by the wireless device via the SDT (e.g., data associated with the DTCH). The transport block can include (e.g., further include) one or more MAC headers (e.g., if needed) and / or one or more MAC CEs (e.g., if triggered). For example, a transport block transmitted by the wireless device via RA-based SDT can be a MAC PDU that includes uplink data, one or more MAC headers, and / or one or more MAC CEs.

[0254] A network or base station may transmit (e.g., broadcast, multicast, and / or unicast) one or more messages (e.g., system information blocks, RRC messages, MAC CE, DCI, and / or any combination thereof) that include one or more SDT-TBS values ​​for a cell. For example, one or more SDT-TBS values ​​may indicate the amount of uplink data (e.g., associated with DTCH) transmitted by a radio device via an on-cell SDT (e.g., RA-based SDT and / or CG-based SDT). A radio device receiving one or more messages may determine whether to initiate an on-cell SDT (e.g., RA-based SDT and / or CG-based SDT) based on one or more SDT-TBS values. The radio device may determine the size of a transport block that includes uplink data. For example, if the size is less than or equal to at least one of the one or more SDT-TBS values, the radio device may determine to transmit uplink data via an SDT (or initiate an SDT for transmitting uplink data). For example, if the size is less than or equal to at least one of one or more SDT-TBS values, the radio device may be allowed to initiate an on-cell SDT to transmit uplink data. For example, if the size is greater than at least one of one or more SDT-TBS values ​​(e.g., greater than all of one or more SDT-TBS values), the radio device may determine not to transmit uplink data via SDT. For example, if the size is greater than at least one of one or more SDT-TBS values ​​(e.g., greater than all of one or more SDT-TBS values), the radio device may not be allowed to initiate an on-cell RA-based SDT for transmitting uplink data.

[0255] One or more SDT-TBS values ​​can indicate whether a wireless device initiates an SDT (e.g., RA-based SDT and / or CG-based SDT) for transmitting uplink data (e.g., associated with DTCH) or initiates an RA procedure to establish a connection to the network or base station. For example, if the value is less than or equal to at least one of the one or more SDT-TBS values, the wireless device may determine to transmit uplink data via an SDT (or initiate an SDT for transmitting uplink data). During and / or after an RA-based SDT, the wireless device may maintain its RRC state as non-RRC_CONNECTED. For example, if the value is greater than at least one of the one or more SDT-TBS values ​​(e.g., greater than all of the one or more SDT-TBS values), the wireless device may determine not to perform (or initiate) uplink data transmission via an SDT. In this case, the wireless device may initiate an RA procedure to establish a connection. For example, after determining that the RA procedure has successfully completed or in response to this, the wireless device may transmit uplink data. After confirming the successful completion of the RA procedure, or in response to this, the wireless device can transition its RRC state from a non-RRC_CONNECTED state to the RRC_CONNECTED state. For example, in this case, the wireless device can transmit uplink data in the RRC_CONNECTED state.

[0256] The base station (or network) can transmit (broadcast, multicast, and / or unicast) one or more messages including the cell's SDT-TBS value (e.g., System Information Block, RRC message, MAC CE, DCI, and / or any combination thereof). One or more messages may include the SDT-TBS value for each RA type of the cell's RA procedure. For example, one or more RA types of the RA procedure may be available on the cell. One or more RA types may include a four-step contention-based RA procedure (e.g., Figure 13A Two-step non-competitive RA procedure (e.g., Figure 13A and / or Figure 13B ), and / or two-step RA procedures (e.g., Figure 13CThe SDT-TBS value can be a common parameter applied to one or more RA types for RA procedures configured on a cell. A radio device receiving one or more messages can determine the RA procedure for a specific RA type. The radio device can determine (e.g., select) a specific SDT-TBS value for the RA procedure for a specific RA type. The radio device can determine, based on the specific SDT-TBS value, whether the radio device transmits uplink data (e.g., associated with DTCH) via SDT (e.g., RA-based SDT and / or CG-based SDT). The SDT can use one or more parameters (and / or procedures) of a specific RA procedure. For example, if, for example, the size of a transport block including uplink data (e.g., the size of a message including uplink data) is less than or equal to the specific SDT-TBS value, the radio device can initiate an SDT on the cell using the specific RA procedure. For example, if, for example, the size of a transport block is greater than the specific SDT-TBS value, the radio device can initiate an RA-based SDT without using the specific RA procedure. For example, if the transport block size is greater than a specific SDT-TBS value, the wireless device can select a different RA type RA procedure for the cell and / or can use a different RA type RA procedure to initiate RA-based SDT. For example, the SDT-TBS value for different RA types can be greater than the transport block size.

[0257] An exemplary configuration parameter for an sdt-TBS (e.g., or edt-TBS) value can be a bit-based value. For example, an exemplary format for an sdt-TBS value could be...

[0258] sdt-TBS-r15 ENUMERATED{b328,b408,b504,b600,b712,b808,b936,b1000or456}, where, for example, the value b328 can correspond to 328 bits, b408 can correspond to 408 bits, and so on. For example, the value b1000 or 456 can correspond to 1000 bits of one or more first RA types of the RA program, and 456 bits of one or more second RA types of the RA program.

[0259] The base station (or network) can transmit (e.g., broadcast, multicast, and / or unicast) one or more messages including one or more SDT-TBS values ​​of the cell (e.g., System Information Block, RRC message, MAC CE, DCI, and / or any combination thereof). One or more SDT-TBS values ​​can be of the RA type according to the cell's RA procedure. For example, one or more RA types of the RA procedure may be available on the cell. One or more RA types may include a four-step contention-based RA procedure (e.g., Figure 13A Two-step non-competitive RA procedure (e.g., Figure 13A and / or Figure 13B), and / or two-step RA procedures (e.g., Figure 13C One or more SDT-TBS values ​​can be common parameters for one or more RA types applied to RA procedures configured on the cell. A radio device receiving one or more messages can determine the RA procedure for a specific RA type. The radio device can select a specific SDT-TBS value from one or more SDT-TBS values ​​for the RA procedure of a specific RA type. One or more messages can indicate that one or more SDT-TBS values ​​are configured for the RA procedure of a specific RA type. The radio device can determine whether to transmit uplink data (e.g., associated with DTCH) via SDT (e.g., RA-based SDT and / or CG-based SDT) based on the specific SDT-TBS value. The radio device can use one or more parameters (and / or procedures) of a specific RA procedure. For example, if the size of a transport block including uplink data (e.g., the size of a message including uplink data) is less than or equal to the specific SDT-TBS value, the radio device can initiate an RA-based SDT on the cell using the specific RA procedure. For example, if the size of a transport block is greater than the specific SDT-TBS value, the radio device can initiate an RA-based SDT without using the specific RA procedure. For example, if the transport block size is greater than a specific SDT-TBS value, the wireless device can select a different RA type RA procedure for the cell and / or can use a different RA type RA procedure to initiate RA-based SDT. For example, the SDT-TBS value for different RA types can be greater than the transport block size.

[0260] Figure 18A An exemplary embodiment of the present disclosure illustrates an RA-based SDT with a four-step RA procedure. According to an exemplary embodiment of the present disclosure, a wireless device can receive configuration parameters for the RA-based SDT. The wireless device can initiate a four-step RA procedure for the RA-based SDT. The wireless device can determine a preamble transmitted via PRACH resources (e.g., ...). Figure 13A (Msg1 1311 in the text). The wireless device can determine the preamble and / or PRACH resources to indicate to the base station via Msg3 (e.g., ... Figure 13B The Msg 3 1313 in the code represents a request to transmit uplink data (e.g., associated with DTCH). This request may be an indication to trigger and / or initiate RA-based SDT. The request may indicate the size of the TB including the uplink data (e.g., expected, measured, determined size). The wireless device may receive a response to the preamble (e.g., ...). Figure 13AThe response (Msg2 1312) can indicate whether the wireless device is permitted to transmit uplink data via Msg3. If the response indicates that the wireless device is not permitted to transmit uplink data, the wireless device can cancel the RA-based SDT. For example, after canceling the RA-based SDT or in response to this, the wireless device can transmit Msg3 without uplink data. If the response indicates that the wireless device is permitted to transmit uplink data, the wireless device transmits TB including uplink data via Msg3. The wireless device can receive a response to the Msg3 transmission (e.g., Figure 13A Msg 4 1314 (in the text).

[0261] Figure 18B An exemplary embodiment of the present disclosure illustrates an RA-based SDT with a two-step RA procedure. According to an exemplary embodiment of the present disclosure, a wireless device can receive configuration parameters for the RA-based SDT. The wireless device can initiate a two-step RA procedure for the RA-based SDT. The wireless device can determine a preamble transmitted via PRACH resources (e.g., ...). Figure 13C (Preamble 1341 in the code). The wireless device can determine the TB (e.g., associated with DTCH) transmitted via PUSCH resources, including uplink data (e.g., data associated with DTCH). Figure 13C (Transport block 1342 in the document). The radio device may determine the preamble, PRACH resources, and / or PUSCH resources to indicate to the base station a request to transmit uplink data via MsgA. This request may be an indication to trigger and / or initiate RA-based SDT. The request may indicate the size of the TB including the uplink data (e.g., expected, measured, determined size). The radio device may receive a response to MsgA (e.g., ...). Figure 13C The response can indicate the success of a MsgB1332 transmission (e.g., successRAR). The response can indicate a fallback for contention-resolved four-step RA procedure (e.g., fallbackRAR). The wireless device can (re)transmit the TB via a contention-resolved Msg 3 transmission. The response can indicate that the wireless device is not allowed to perform RA-based SDT. In this case, the wireless device can cancel the RA-based SDT.

[0262] A radio device can initiate an RA procedure on the cell for transmitting uplink data via an RA-based SDT (e.g., associated with DTCH). The radio device can select the RA type for the RA procedure in either a four-step RA type or a two-step RA type. The RA type can be associated with at least one SDT-TBS value. The radio device can determine the TBS of the TB based on at least one SDT-TBS value. For example, the TB may include a MAC PDU that includes uplink data and / or one or more padding bits. For example, if the size of the uplink data (e.g., an expected message including uplink data) is less than the TBS, the radio device can append one or more padding bits to the MAC PDU.

[0263] A wireless device can receive messages that include one or more configurations. The configurations in the one or more configurations may include an identifier (or index) of the configuration. Each configuration in the one or more configurations may include radio resource configuration parameters for one or more uplink radio resources that the wireless device can use in a non-RRC_CONNECTED state. For example, the wireless device can perform CG-based SDT via one or more uplink radio resources.

[0264] A wireless device can receive an RRC message indicating one or more uplink radio resources to be used by the wireless device in a non-RRC_CONNECTED state. For example, the wireless device can perform CG-based SDT via one or more uplink radio resources. The one or more uplink radio resources in a non-RRC_CONNECTED state can be one-time use resources, for example, for a single transmission. The one or more uplink radio resources in a non-RRC_CONNECTED state can be periodic resources, for example, for one or more uplink transmissions. The one or more uplink radio resources in a non-RRC_CONNECTED state can be referred to by various names in different systems and / or implementations. The one or more uplink radio resources in a non-RRC_CONNECTED state can be referred to as pre-configured uplink resources (PURs). The uplink grant indicating one or more uplink radio resources in a non-RRC_CONNECTED state can be referred to as a (pre)configured grant. A (pre)configured grant can include several types. For example, a (pre)configured grant can include (pre)configured grant type 1 and / or (pre)configured grant type 2.

[0265] One or more uplink radio resources determined (and / or indicated) by (pre)configured authorization type 1 may not require an indication to (re)initiate (and / or (re)activate) one or more uplink radio resources. For example, after receiving, for instance, an RRC message indicating that one or more uplink radio resources are in a non-RRC_CONNECTED state, or in response to this, one or more uplink radio resources determined (and / or indicated) by (pre)configured authorization type 1 may not require an indication to (re)initiate (and / or (re)activate) one or more uplink radio resources.

[0266] For example, upon receiving or in response to an RRC message including (pre)configuration authorization type 1, the wireless device may (re)initiate (and / or (re)activate) (pre)configuration authorization type 1 and / or one or more uplink radio resources indicated by (pre)configuration authorization type 1. For example, if, for instance, the wireless device receives configuration parameters for (pre)configuration authorization type 1 in a non-RRC_CONNECTED state, then upon receiving or in response to an RRC message including (pre)configuration authorization type 1, and / or after or in response to a change in the wireless device's RRC state to a non-RRC_CONNECTED state, the wireless device may (re)initiate (and / or (re)activate) (pre)configuration authorization type 1 and / or one or more uplink radio resources indicated by (pre)configuration authorization type 1.

[0267] One or more uplink radio resources determined (and / or indicated) by (pre)configured license type 2 may require (re)initiating (and / or (re)activating) one or more uplink radio resources. For example, after receiving an RRC message including (pre)configured license type 2 indicating one or more uplink radio resources, or in response to such a message, the wireless device may not (re)initiate (and / or (re)activate) one or more uplink radio resources. For example, after receiving an indication to (re)initiate (and / or (re)activate) one or more uplink radio resources in a non-RRC_CONNECTED state, or in response to such an indication, the wireless device may (re)initiate (and / or (re)activate) one or more uplink radio resources. The wireless device may receive such indication after receiving an RRC message including (pre)configured license type 2 indicating one or more uplink radio resources, or in response to such an indication. The wireless device may receive such indication in a non-RRC_CONNECTED state. If the wireless device receives this indication while in the RRC_CONNECTED state, it may (re)initiate (and / or (re)activate) one or more uplink radio resources after the wireless device's RRC state transitions to a non-RRC_CONNECTED state or in response to this indication. If the wireless device receives this indication while in the RRC_CONNECTED state, it may (re)initiate (and / or (re)activate) one or more uplink radio resources for the RRC_CONNECTED state. After the wireless device's RRC state transitions to a non-RRC_CONNECTED state or in response to this indication, the wireless device may determine that it has (re)initiated (and / or (re)activated) one or more uplink radio resources in the RRC_CONNECTED state and / or may maintain the (re)initiated (and / or (re)activated) one or more uplink radio resources in the RRC_CONNECTED state as if they were active in the non-RRC_CONNECTED state. An uplink grant indicating one or more uplink radio resources in a non-RRC_CONNECTED state can be referred to as a (pre)configured grant with a specific type indicator, such as (pre)configured grant type 3, 4, etc. For example, (pre)configured grant type 1 and (pre)configured grant type 2 can indicate one or more (periodic) uplink grants in an RRC_CONNECTED state. For example, (pre)configured grant type 3 (and / or other types of (pre)configured grants) can indicate one or more (periodic) uplink grants in a non-RRC_CONNECTED state.

[0268] The wireless device may receive one or more configuration parameters from the base station that indicate and / or include the number of times (e.g., exemplary parameter name: NumOccasions) are available for one or more uplink radio resources. The number of times may indicate that one or more uplink radio resources are one-time use resources (or licenses) for a single uplink transmission. The number of times may indicate that one or more uplink radio resources are multiple uplink radio resources. The number of times may indicate that one or more uplink radio resources are one or more periodic radio resources.

[0269] A wireless device may receive one or more configuration parameters, for example, via a wireless device-specific message (e.g., an RRC message). A wireless device-specific message may be an RRC release message. A wireless device-specific message may be an RRC message received by the wireless device in the RRC_CONNECTED state.

[0270] In the example, one or more configuration parameters received by the wireless device may indicate the resource allocation of one or more uplink radio resources. For example, one or more configuration parameters may indicate the periodicity of one or more uplink radio resources in a non-RRC_CONNECTED state (e.g., exemplary parameter name: Periodicity). For example, this periodicity may be used for uplink granting of SDT (e.g., CG-based SDT) and / or one or more uplink radio resources indicated by uplink granting.

[0271] For example, one or more configuration parameters may include a time offset. For example, a time offset may be used for uplink grants in an SDT (e.g., a CG-based SDT) and / or one or more uplink radio resources indicated by the uplink grant. The time offset may be a time-domain offset relative to (and / or about) a time base. The time base may be a specific SFN, a specific subframe number, a specific slot number, a specific symbol number, and / or a combination thereof (e.g., an H-SFN). The time base may be predefined (e.g., SFN=0 and / or H-SFN=0). For example, if a field for the time base is not present in one or more configuration parameters, the time base may be a predefined value (e.g., SFN=0 and / or H-SFN=0). For example, a wireless device may receive an uplink grant, for example, indicated by one or more configuration parameters. The uplink grant may indicate one or more uplink radio resources. One or more uplink radio resources may begin with a symbol indicated by the time offset (of the SFN slot in the H-SFN). One or more uplink radio resources may appear periodically from the symbol. For example, a wireless device can, for instance, determine sequentially, based on a time offset and an N* period, that the Nth uplink grant in one or more uplink grants occurs within a transmission time interval (TTI, e.g., time slot, micro-slot, symbol). The time offset can be defined based on the number of symbols, the number of time slots, the number of subframes, the number of SFNs, the number of H-SFNs, and / or combinations thereof. For example, one or more configuration parameters may include parameters such as timeDomainOffset. For example, timeDomainOffset indicates the time offset received by the wireless device from the base station. For example, one or more configuration parameters may include parameters such as timeReferenceSFN (e.g., a time reference base defined based on SFNs and / or H-SFNs). For example, timeReferenceSFN indicates that an SFN serves as a time reference for determining the time offset of a resource in the time domain. For example, an SFN may repeat at a period of 1024 frames. For example, a wireless device can receive one or more configuration parameters indicating timeReferenceSFN=0 via SFN=3. For example, timeReferenceSFN=0 may indicate that the time reference SFN for the three SFNs preceding SFN=3 is SFN=0. For example, timeReferenceSFN=0 can indicate that the time reference SFN=0 is 1021 SFNs after SFN=3. For example, a wireless device can determine the nearest SFN to the indicated number before receiving the configured authorization configuration. For example, in the example above, the wireless device can determine that timeReferenceSFN=0 indicates that the time reference SFN=0 is 3 SFNs before SFN=3.

[0272] For example, a wireless device can determine, for instance, sequentially, that the Nth uplink grant occurs (and / or the uplink grant recurs) in the following symbols:

[0273] [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (Slot number in frame × numberOfSymbolsPerSlot) + Symbol number in slot] = (timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity) modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot). For example, numberOfSlotsPerFrame is the number of slots in the frame. For example, numberOfSymbolsPerSlot is the number of symbols in the slot. For example, periodicity is the periodicity of one or more uplink radio resources indicated by one or more configuration parameters. For example, S is the symbol number (or symbol offset) indicated by one or more configuration parameters. The determination of the Nth uplink grant mentioned above may be a case where the (pre)configuration grant may not require the activation (and / or initiation) of additional activation messages (e.g., DCI, MACCE, and / or RRC) of one or more uplink radio resources (and / or (pre)configuration grants).

[0274] For example, a wireless device can determine, for instance, sequentially, that the Nth uplink grant occurs (and / or the uplink grant recurs) in the following symbols:

[0275] [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slot number in frame × numberOfSymbolsPerSlot) + symbol number in slot] = [(SFNstart time × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slotstart time × numberOfSymbolsPerSlot + symbolstart time) + N × periodicity] modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot). The determination of the Nth uplink grant mentioned above may be a case where (pre)configuration grants may require the activation (and / or initiation) of additional activation messages (e.g., DCI, MAC CE, and / or RRC) for one or more uplink radio resources (and / or (pre)configuration grants). For example, the SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol, respectively, when one or more uplink grants are (re)initiated. For example, the SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol at the time the wireless device receives an indication (e.g., DCI) to (re)initiate (and / or (re)activate) one or more uplink grants. For example, the SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol of a PUSCH transmission opportunity where one or more uplink grants are (re)initiated. For example, a PUSCH transmission opportunity is the first PUSCH opportunity where one or more uplink grants are (re)initiated.

[0276] A wireless device can (re)initiate a transmission via one or more uplink radio resources in a non-RRC_CONNECTED state based on one or more conditions. For example, the transmission could be a CG-based SDT. For example, the wireless device can receive configuration parameters indicating one or more conditions. For example, the wireless device can determine whether a cell configured with one or more uplink radio resources in a non-RRC_CONNECTED state supports transmission via one or more uplink radio resources. For example, the wireless device can receive an RRC message (e.g., SIB). The RRC message can include configuration parameters indicating whether the cell supports transmission via one or more uplink radio resources. The configuration parameters can indicate which type of transmission is supported (or available) via one or more uplink radio resources. For example, this type could include control plane (CP) transmissions and / or user plane (UP) transmissions. The configuration parameters can indicate which type of network the cell is connected to supports transmission via one or more uplink radio resources. Depending on the type of network the cell is connected to, the wireless device can determine whether transmission via one or more uplink radio resources is supported in the cell. For example, network type can include one or more generations of network systems (e.g., 5G core, Evolution Packet Core (EPC), etc.) and / or one or more wireless technologies (e.g., Wi-Fi, 5G, Bluetooth, etc.). For example, configuration parameters can indicate which type of spectrum (and / or band) supports transmission via one or more uplink radio resources. For example, spectrum type can include licensed spectrum and / or unlicensed spectrum. For example, spectrum type can include CBRS (Civil Broadband Radio Service) bands (e.g., broadband in the 3.5 GHz band). For example, spectrum type can include millimeter wave bands (e.g., bands exceeding 30 GHz). Configuration parameters in the RRC message can indicate a combination of network type, spectrum type, and / or transmission type. For example, the parameter cp-PUR-5GC in the RRC message (e.g., parameter values ​​can be 'true' / 'false' or 'enabled' / 'disabled') indicates whether CP transmission using CG-based SDT is supported in the cell when connected to a 5G core network. For example, the parameter cp-PUR-EPC in the RRC message (e.g., the parameter value can be 'true' / 'false' or 'enabled' / 'disabled') indicates whether CP transmission using CG-based SDT is supported in the cell when connected to the EPC. For example, if the RRC message received from the cell indicates that CP-PUR-EPC = 'true' (or 'enabled'), the radio device determines that CG-based SDT is supported in the cell when connected to the EPC.

[0277] Figure 19AAn example of (pre)configuration authorization of one or more uplink radio resources in a non-RRC_CONNECTED state is illustrated according to an embodiment of this disclosure. A wireless device can perform CG-based SDT via one or more (pre)configured uplink radio resources. (Pre)configuration authorization may not require additional activation messages (e.g., DCI, MACCE, and / or RRC) for activating (and / or initiating) one or more uplink radio resources (and / or (pre)configuration authorization). For example, the wireless device can receive an RRC message. An RRC message may include configuration parameters for the (pre)configuration authorization of the cell. An RRC message may include an indication and / or index of the configuration containing the configuration parameters. For example, an RRC message may be an RRC release message. Upon receiving or in response to an RRC message, the wireless device can determine (and / or store) the (pre)configuration authorization of the cell. Upon receiving or in response to an RRC message, the wireless device can (re)initiate (or activate) the (pre)configuration authorization. One or more uplink radio resources (and / or (pre)configuration grants) can be activated and / or initiated (or valid) in the RRC_INACTIVE state. For example, a radio device can (re)initiate (or activate) a (pre)configuration grant to begin within (and / or from) a time base. For example, a time base can be a symbol, time slot, subframe, SFN, and / or super SFN (H-SFN). For example, an H-SFN includes one or more SFNs (e.g., 1024 SFNs). For example, a time base can be a combination of one or more of a symbol, time slot, subframe, SFN, and / or super SFN (H-SFN). For example, a time base can be a symbol of the SFN's time slot indicated by configuration parameters (e.g., time domain offset (e.g., indicating H-SFN, SFN, and / or time slot)) and symbol number S (e.g., indicating symbol). For example, a radio device can determine that a (pre)configuration grant (re)occurs at the period indicated by the configuration parameters.

[0278] exist Figure 19AIn this context, a wireless device can establish a connection to the network (or base station) via a CG-based SDT. For example, during a CG-based SDT, the wireless device can transmit a first message via one or more uplink radio resources in a non-RRC_CONNECTED state. The first message may include an RRC connection setup request (e.g., for an RRC connection setup procedure) and / or an RRC connection recovery request (e.g., for an RRC connection recovery procedure). The first message may include an SDT (EDT) request message. The wireless device can receive a second message from the base station indicating a transition to the RRC_CONNECTED state. The second message may be a response to the first message. For example, the wireless device may receive an RRC connection setup message. For example, the wireless device may receive an RRC connection recovery message. After receiving or in response to the second message, the wireless device can transition to the RRC_CONNECTED state. The wireless device can disable and / or suspend (or clear) one or more uplink radio resources (and / or (pre)configured authorizations) used in the non-RRC_CONNECTED state in the RRC_CONNECTED state. For example, during a CG-based SDT, the wireless device can transmit a first message via one or more uplink radio resources in a non-RRC_CONNECTED state. Figure 18A After a base station is connected or in response to this, one or more uplink radio resources (and / or (pre)configured authorizations) may be disabled and / or suspended (cleared and / or invalidated).

[0279] Figure 19B An example of (pre)configuration authorization of one or more uplink radio resources not in RRC_CONNECTED, as indicated by an embodiment of this disclosure, is shown. A wireless device can perform CG-based SDT via one or more (pre)configured authorized uplink radio resources. Figure 18BThe (pre)configuration grant may require activating (and / or initiating) additional activation messages (e.g., DCI, MAC CE, and / or RRC) for one or more uplink radio resources (and / or (pre)configuration grants). For example, a radio device may receive an RRC message that includes configuration parameters of the cell's (pre)configuration grant. After receiving or in response to an RRC message, the radio device may determine (and / or store) the cell's (pre)configuration grant. For example, the RRC message may be an RRC release message. After receiving or in response to an RRC message, the radio device may not (re)initiate (or activate) the (pre)configuration grant, for example, until the radio device receives additional activation messages (e.g., DCI, MAC CE, and / or RRC). The radio device may monitor a PDCCH in a non-RRC_CONNECTED state to receive additional activation messages. The radio device may receive additional activation messages (e.g., DCI, MAC CE, and / or RRC) after receiving or in response to an RRC message. The DCI carried by the PDCCH may be an additional activation message. MAC CE and / or RRC messages received based on the DCI carried by the PDCCH in the downlink assignment reception can be additional activation messages. Configuration parameters in the RRC message can indicate the time and frequency resource allocation of the PDCCH, the monitoring timing of the PDCCH, and / or the monitoring period of the PDCCH. The radio device can determine (pre)configure grants to (re)occur at the period indicated by the configuration parameters and / or timing offset references (e.g., SFN, SFN, time slot, and / or symbol). For example, the radio device can determine (e.g., H-SFN) the SFN, time slot, and / or symbol based on the reception timing of the additional activation message received via the PDCCH. The radio device can receive deactivation messages indicating the deactivation and / or suspension (clearing and / or invalidation) of one or more uplink radio resources (and / or (pre)configuration grants). The radio device can receive deactivation messages in a non-RRC_CONNECTED state.

[0280] exist Figure 19BIn this context, a wireless device can establish a connection to the network (or base station) via a CG-based SDT. For example, during a CG-based SDT, the wireless device can transmit a first message via one or more uplink radio resources in a non-RRC_CONNECTED state. The first message may include an RRC connection setup request (e.g., for an RRC connection setup procedure) and / or an RRC connection recovery request (e.g., for an RRC connection recovery procedure). The first message may include an SDT (EDT) request message. The wireless device can receive a second message from the base station indicating a transition to the RRC_CONNECTED state. The second message may be a response to the first message. For example, the wireless device may receive an RRC connection setup message. For example, the wireless device may receive an RRC connection recovery message. After receiving or in response to the second message, the wireless device can transition to the RRC_CONNECTED state. The wireless device can disable and / or suspend (or clear) one or more uplink radio resources (and / or (pre)configured authorizations) used in the non-RRC_CONNECTED state in the RRC_CONNECTED state. For example, during a CG-based SDT, the wireless device can transmit a first message via one or more uplink radio resources in a non-RRC_CONNECTED state. Figure 18B After a base station is connected or in response to this, one or more uplink radio resources (and / or (pre)configured authorizations) may be disabled and / or suspended (cleared and / or invalidated).

[0281] One or more radio resources for RA-based SDT and / or CG-based SDT can be configured within a specific frequency (and / or frequency range) of the cell. In this disclosure, the cell's BWP and the specific frequency (and / or frequency range) of the cell can be interchangeable.

[0282] One or more radio resources used for RA-based SDT and / or CG-based SDT may be configured with cell-specific BWPs. Specific BWPs may include DL BWPs and / or UL BWPs. One or more downlink receptions of the SDT may be configured in the DL BWP. One or more uplink transmissions of the SDT may be configured in the UL BWP. Specific BWPs may be referred to by different names, such as contiguous (or non-contiguous) frequencies and / or radio ranges in which RA-based SDT and / or CG-based SDT are configured. Specific BWPs configured with RA-based SDT and / or CG-based SDT may be predefined (e.g., as the initial BWP of the cell). Specific BWPs configured with RA-based SDT and / or CG-based SDT may be semi-statically configured, for example via RRC messages such as RRC release messages.

[0283] In the example, the wireless device can receive a message (e.g., an RRC message) that includes configuration parameters for a specific BWP. A specific BWP may include a DL BWP and / or a UL BWP. Configuration parameters may indicate the set of parameters used in a specific BWP (e.g., subcarrier spacing). Configuration parameters may indicate the set of parameters applied to the DL BWP and / or UL BWP. Configuration parameters may include separate fields and / or indicators indicating parameter sets used in both the DL BWP and / or UL BWP. The parameter sets used by the DL BWP and / or UL BWP may be the same or different. Configuration parameters may include radio resource configuration parameters for DL ​​and / or UL control channels (e.g., PDCCH and / or PUCCH) for transmission via one or more radio resources. Configuration parameters may include radio resource configuration parameters for DL ​​and / or UL data channels (e.g., PDSCH and / or PUSCH) for transmission via one or more radio resources. DL control and / or data channels (e.g., PDCCH and / or PDSCH) can be configured within the DL BWP. UL control and / or data channels (e.g., PUCCH and / or PUSCH) can be configured within the UL BWP.

[0284] One or more radio resources used for RA-based SDT and / or CG-based SDT may be configured with a cell-specific BWP. The specific BWP may be an initial BWP. For example, at least one of a DL BWP and a UL BWP configured with RA-based SDT and / or CG-based SDT may be an initial BWP. For example, a DL BWP of a specific BWP may be an initial DL BWP. For example, a UL BWP of a specific BWP may be an initial UL BWP. For example, at least one of a DL BWP and a UL BWP may be an initial BWP. For example, both a DL BWP and a UL BWP may be initial BWPs, such as an initial DL BWP and an initial UL BWP.

[0285] The frequency range of the initial BWP can be within the frequency range that a specific BWP may include. For example, the frequency range of the initial UL BWP can be within the frequency range of the UL BWP of a specific UL BWP. For example, the frequency range of the initial DL BWP can be within the frequency range of the DL BWP of a specific DL BWP.

[0286] One or more radio resources used for RA-based SDT and / or CG-based SDT may be configured with cell-specific BWPs. Specific BWPs may be configured separately from the initial BWP. For example, at least one of the DL BWP and UL BWP configured with RA-based SDT and / or CG-based SDT may differ from the initial BWP. For example, the DL BWP of a specific BWP may differ from the initial DL BWP. For example, the UL BWP of a specific BWP may differ from the initial UL BWP. For example, one or more radio resources may be associated with DL BWPs and / or UL BWPs. For example, a DL BWP may be used to configure PDCCH (e.g., ACK, NACK, and / or backoff responses to transmissions via one or more radio resources) and / or PDSCH (e.g., RRC responses to RRC messages transmitted via one or more radio resources) associated with transmissions via one or more radio resources. For example, a UL BWP may be used to configure PUCCH (e.g., ACK and / or NACK responses to PDSCH) and / or PUSCH (e.g., data via one or more radio resources) associated with transmissions via one or more radio resources. A wireless device can determine that a particular BWP (e.g., a DL BWP and / or a UL BWP) is an initial BWP (e.g., an initial DL BWP and / or an initial ULBWP, respectively) if, for example, a field indicating a configuration (e.g., frequency location, bandwidth, and / or parameter set (e.g., subcarrier spacing)) for a particular BWP (e.g., different from the initial BWP) is not present in the configuration parameters indicating one or more radio resources.

[0287] One or more radio resources used for RA-based SDT and / or CG-based SDT may be configured with cell-specific BWPs. A specific BWP may be an active BWP used by the radio device in RRC_CONNECTED. For example, the DLBWP of a specific BWP may be the last DL BWP used by the radio device as an active DL BWP in the RRC_CONNECTED state. Similarly, the UL BWP of a specific BWP may be the last UL BWP used by the radio device as an active UL BWP in the RRC_CONNECTED state. For example, a radio device may transition from an RRC_CONNECTED state to a non-RRC_CONNECTED state. BWPs used by the radio device in the RRC_CONNECTED state (e.g., the last DL BWP and / or the last UL BWP) may be used in the transitioned non-RRC_CONNECTED state. A wireless device can determine that a particular BWP (e.g., a DL BWP and / or a UL BWP) is a BWP (e.g., the last DL BWP and / or the last UL BWP, respectively) if, for example, there is no field in the configuration parameters indicating one or more radio resources that indicates the configuration (e.g., different from the last BWP) of a particular BWP (e.g., frequency location, bandwidth, and / or parameter set (e.g., subcarrier spacing)).

[0288] One or more radio resources used for RA-based SDT and / or CG-based SDT may be configured with cell-specific BWPs. Specific BWPs may be configured separately from the initial BWP. For example, the DL BWP of a specific BWP may differ from the initial DLBWP. For example, the UL BWP of a specific BWP may differ from the initial UL BWP. For example, one or more radio resources may be associated with DL BWPs and / or UL BWPs. For example, DL BWPs may be used to configure PDCCHs (e.g., ACK, NACK, and / or backoff responses to transmissions via one or more radio resources) and / or PDSCHs (e.g., RRC responses to RRC messages transmitted via one or more radio resources) associated with transmissions via one or more radio resources. For example, UL BWPs may be used to configure PUCCHs (e.g., ACK and / or NACK responses to PDSCHs) and / or PUSCHs (e.g., data via one or more radio resources) associated with transmissions via one or more radio resources.

[0289] In the example, one or more configuration parameters may indicate the value of the Time Alignment Timer (TAT) for the cell (and / or the cell group that includes the cell) (e.g., exemplary parameter name: TimeAlignmentTimer), where one or more uplink radio resources are configured to be in a non-RRC_CONNECTED state. The cell group that includes the cell may be referred to as a Timing Advance Group (TAG). The TAT value may indicate how long the timing advance offset value is valid (e.g., effectively used) for adjusting the uplink timing of uplink transmissions to the cell (and / or cells in the cell group). For example, the TAT value may determine how long the radio device identifies the cell (and / or cells belonging to the associated TAG) as uplink time aligned. The radio device may determine (or adjust) the uplink timing of uplink transmissions (e.g., PRACH, PUSCH, SRS, and / or PUCCH transmissions) on the cell (and / or cells in the cell group) based on the timing advance offset value. For example, the timing advance offset value may indicate how much (and / or how long) the uplink timing for uplink transmissions is delayed or advanced for uplink synchronization. For example, a wireless device may run a TAT for the time interval (and / or duration) indicated by the TAT value. When a TAT is running, the wireless device may determine that the timing advance offset value is valid (and / or used) for adjusting uplink timing of uplink transmissions on the cell (or cells in a cell group). For example, if a TAT associated with a cell group (e.g., a TAG) to which the cell belongs is not running and / or has expired, the wireless device may determine that the uplink from the wireless device to the cell (e.g., a base station) is out of sync. For example, if a TAT associated with a cell group (e.g., a TAG) to which the cell belongs is not running and / or has expired, the wireless device may stop performing uplink transmissions on the cell (and / or cells in a cell group). The wireless device may stop uplink transmissions on the cell, for example, because the uplink transmission timing difference between the wireless device's TAGs (e.g., the maximum) or between the TAGs of any of the wireless device's MAC entities (e.g., two MAC entities configured for dual connectivity) has exceeded the maximum uplink transmission timing difference, the wireless device may determine that the TAT associated with the cell has expired. For example, when the TAT associated with the cell group (e.g., TAG) to which the cell belongs is not active and / or has expired, the radio device may perform random access preamble (re)transmission and / or MSG (re)transmission. The radio device may (re)start the TAT after receiving a timing advance command indicating a (new and / or updated) timing advance offset value for the cell (and / or a cell in the cell group) or in response to receiving such a timing advance command. The timing advance command may be received as MACCE and / or DCI.The timing advance command can indicate the timing advance offset value of a cell where one or more uplink radio resources are in a non-RRC_CONNECTED state.

[0290] For example, if the wireless device receives (and / or is configured with) one or more uplink radio resources for a non-RRC_CONNECTED state, the wireless device may (re)initiate the timing alignment timer after transitioning to a non-RRC_CONNECTED state or in response to such transition. For example, the wireless device may (re)start the timing alignment timer after receiving configuration parameters associated with the timing alignment timer (e.g., the timer value of the timing alignment timer) or in response to such receipt. The wireless device may (re)start the timing alignment timer after receiving a timing advance offset value or in response to such receipt. The wireless device may receive low-level control messages (e.g., DCI or PDCCH) indicating the timing advance offset value. The wireless device may receive MAC layer control messages (e.g., MAC CE and / or RAR) indicating the timing advance offset value. For example, the wireless device may (re)start the timing alignment timer after receiving a timing advance command MAC control element and / or PDCCH indicating timing advance adjustment or in response to such receipt. The wireless device may determine that the timing advance offset value is valid at least during TAT operation. A wireless device can verify the TA value based on one or more verification conditions. The wireless device can (re)start the time alignment timer after determining that the TA has been verified, or in response to this. For example, if the TAT has run for the time interval (or duration) indicated by the TAT value, the wireless device can determine that the TAT has expired. In response to the expiration of the TAT, the wireless device can determine that the timing advance offset value is invalid.

[0291] The terms used in this disclosure may be used interchangeably with and / or referred to as one or more different terms. For example, a timing advance value may be referred to as a timing alignment value. For example, a timing advance offset value may be referred to as a timing alignment offset value. For example, a timing alignment timer may be referred to as a time alignment timer, a timing advance timer, and / or a time advance timer. For example, a timing advance group may be referred to as a timing alignment group.

[0292] For example, a wireless device determines, for instance, whether it has a valid timing advance value based on one or more authentication conditions (e.g., TAT-based authentication and / or measurement-based authentication). For example, a wireless device may determine that the configuration of one or more uplink radio resources is valid, for instance, based on configuration parameters indicating the validity of the configuration of one or more uplink radio resources. For example, the wireless device receives a message that includes configuration parameters. The configuration is valid, for instance, if the `config` field in the message is set to `setup` (e.g., `true`). For instance, the configuration is valid if, for example, the `config` field is set to `release` (e.g., `false`).

[0293] A wireless device can determine whether a timing advance value is valid for transmission via one or more uplink radio resources in a non-RRC_CONNECTED state based on one or more authentication conditions. For example, the one or more authentication conditions may include TAT-based authentication and / or measurement-based authentication. The wireless device can determine the configuration conditions to apply among the one or more authentication conditions. For example, the wireless device receives a message including configuration parameters for a first authentication condition (e.g., TAT-based authentication) among the one or more authentication conditions. The message may not include configuration parameters for a second authentication condition (e.g., measurement-based authentication) among the one or more authentication conditions. In this case, the wireless device can determine whether the timing advance value is valid based at least on the first authentication condition. For example, if the message includes configuration parameters for both the first and second authentication conditions (e.g., TAT-based authentication and measurement-based authentication), the wireless device can determine whether the timing advance value is valid based at least on both the first and second authentication conditions.

[0294] For example, for TAT-based authentication, the wireless device determines the validity of the timing advance value based on the TAT. The wireless device may receive an RRC message that includes the TAT value. The TAT may be used for a cell (and / or a TAG for that cell) where one or more uplink radio resources are configured in a non-RRC_CONNECTED state. For example, if the TAT is active, the wireless device may determine that the timing advance value used for transmission via one or more uplink radio resources is valid. For example, if the TAT value is not configured (e.g., the RRC message does not include the TAT value), the wireless device may determine that the authentication of the timing advance value used for transmission is not at least TAT-based.

[0295] A wireless device can perform a SDT (Sustainable Targeting Transmission) followed by one or more subsequent transmissions in a non-RRC_CONNECTED state. The one or more subsequent transmissions may include at least one uplink transmission. The one or more subsequent transmissions may include at least one downlink reception. For example, the SDT and one or more subsequent transmissions may be grouped together. For example, a group of transmissions may include the SDT and / or one or more subsequent transmissions. The SDT may be the initial uplink transmission for that group.

[0296] One or more subsequent transmissions can be one or more transmissions following and / or associated with an SDT. For example, a wireless device can transmit uplink data via one or more radio resources in a non-RRC_CONNECTED state (e.g., performing an SDT). Based on the transmission of uplink data, the wireless device can monitor the PDCCH during a time window. The wireless device can receive DCIs that schedule one or more subsequent transmissions during the time window.

[0297] In the example, the wireless device can transmit uplink data via one or more radio resources in a non-RRC_CONNECTED state (e.g., performing SDT). The wireless device can monitor the PDCCH in response to the uplink data. For example, in response, the wireless device can monitor the PDCCH during a time window. For example, after transmitting uplink data or in response to this, the wireless device can start a time window. The wireless device can receive a DCI via the PDCCH during the time window. The DCI can be a response to the transmission of uplink data (e.g., ACK or NACK·HARQ feedback). The DCI can include uplink granting (e.g., dynamic granting) for scheduling a first subsequent transmission (e.g., downlink or uplink transmission) in one or more subsequent transmissions. For example, the first subsequent transmission is a new uplink transmission. For example, the first subsequent transmission is a new downlink reception. For example, the first subsequent transmission can be a retransmission of uplink data.

[0298] In the example, the wireless device may use one or more RNTIs and monitor the PDCCH in response to uplink data transmission during a time window. The one or more RNTIs may include the wireless device's C-RNTI. The one or more RNTIs may include RNTIs assigned to the SDT (e.g., CS-RNTI, PUR-RNTI, PUR C-RNTI, SDT-RNTI, etc.). In this disclosure, the RNTI assigned to the SDT may be referred to as the SDT-RNTI.

[0299] The wireless device can receive (and / or detect) the DCI via the PDCCH during a time window. The DCI may include a CRC parity bit scrambled with C-RNTI. A DCI including a CRC parity bit scrambled with C-RNTI may include dynamic granting, such as dynamic uplink granting for scheduling the PUSCH and / or dynamic downlink assignment for scheduling the PDSCH. A DCI whose CRC parity bit is scrambled with C-RNTI may include, for example, uplink granting for scheduling new UL transmissions in a non-RRC_CONNECTED state. A DCI whose CRC parity bit is scrambled with C-RNTI may include, for example, downlink assignment for scheduling new DL transmissions in a non-RRC_CONNECTED state.

[0300] The wireless device can receive (and / or detect) the DCI via the PDCCH during the time window. The DCI may include a CRC parity bit scrambled with SDT-RNTI. The DCI with its CRC parity bit scrambled with SDT-RNTI may include uplink grants, which may, for example, schedule retransmissions of uplink data (and / or SDT) in a non-RRC_CONNECTED state.

[0301] In the example, the wireless device may (re)start a time window after receiving a DCI or in response to it. For example, the DCI may include UL authorization for uplink data retransmission, UL authorization for a new UL transmission, and / or DL ​​assignment for a new DL transmission. The wireless device may use at least one RNTI (e.g., C-RNTI and / or SDT-RNTI) and monitor the PDCCH during the (re)started time window. The wireless device may receive a second DCI via the PDCCH during the (re)started time window. The second DCI has CRC parity bits scrambled with SDT-RNTI and / or C-RNTI. The second DCI may include UL authorization for uplink data retransmission, UL authorization for a new UL transmission, and / or DL ​​assignment for a new DL transmission. The wireless device may (re)start a time window after receiving a second DCI or in response to it, and / or monitor the PDCCH using at least one RNTI (e.g., C-RNTI and / or SDT-RNTI) during the (re)started time window. In this way, a wireless device can continue one or more subsequent transmissions by (re)starting a time window in response to receiving such a DCI.

[0302] In response to the expiration of a time window and / or a (re)started time window, the wireless device may cease monitoring the PDCCH. For example, if the wireless device does not receive a DCI during the time window and / or a (re)started time window, the wireless device may stop one or more subsequent transmissions in a non-RRC_CONNECTED state. For example, one or more subsequent transmissions associated with an SDT may be one or more transmissions performed after the SDT or in response to the SDT (e.g., the first initial transmission) and before the expiration of the time window following the SDT or in response to the (re)started time window of the SDT. In response to the expiration of a time window and / or a (re)started time window, the wireless device may cease using one or more RNTIs to monitor the PDCCH. One or more RNTIs may include the wireless device's C-RNTI and / or the RNTI assigned to the SDT (e.g., CS-RNTI, PUR-RNTI, PUR C-RNTI, SDT-RNTI, etc.).

[0303] Figure 20 Examples of one or more subsequent transmissions of an SDT according to an embodiment of this disclosure are shown. The wireless device may receive messages (e.g., RRC release messages) that include and / or indicate configuration parameters of the SDT. The configuration parameters may indicate uplink grants and / or one or more uplink radio resources for the SDT. For example, one or more uplink radio resources may include... Figure 20 The first SDT resource, the second SDT resource, and / or the third SDT resource. A wireless device may transmit uplink data via one of the one or more uplink radio resources. For example, if there is no uplink data in the wireless device's buffer, the wireless device may skip transmission via one of the one or more uplink radio resources. The one or more uplink radio resources may be those with, for example, […]. Figure 20 The periodic resources shown are cyclical.

[0304] A wireless device can perform one or more subsequent transmissions after or in response to an SDT. For example, an SDT and one or more subsequent transmissions can be grouped together. Figure 20In this process, the wireless device can determine a first SDT resource, a second SDT resource, and a third SDT resource. The wireless device can perform a first initial transmission (e.g., SDT) via the first SDT resource. The wireless device can initiate a time window in response to the first initial transmission. The wireless device can receive one or more DCIs scheduled for one or more first subsequent transmissions via the PDCCH. The wireless device can receive one or more DCIs during the time window. Based on this disclosure, the wireless device can receive one or more DCIs once or multiple times during the time window and / or (re)started time window. In response to the expiration of the time window (or (re)started time window), the wireless device can stop monitoring the PDCCH. One or more subsequent transmissions may include at least one uplink transmission (e.g., Figure 20 One or more first subsequent transmissions in the process). One or more subsequent transmissions may include at least one downlink reception (e.g., Figure 20 One or more second subsequent transmissions in the process). The wireless device may not perform one or more subsequent transmissions (e.g., Figure 20 (The third initial transmission in the process).

[0305] A wireless device may maintain a time window for SDT and / or one or more subsequent transmissions of SDT. The wireless device may receive a message from the base station including a value (e.g., length) of the time window. This value may instruct the wireless device to perform (e.g., be permitted to perform) the SDT and / or one or more subsequent transmissions of SDT for a period of time (or interval). This value may instruct the wireless device to monitor (e.g., be permitted to monitor) the PDCCH for a period of time (or interval) for receiving new UL and / or new DL transmissions and / or retransmissions of SDT and / or one or more UL and / or DL ​​authorizations for one or more subsequent transmissions of SDT. The wireless device may receive one or more DCIs via the PDCCH. One or more DCIs may include one or more UL and / or DL ​​authorizations. The wireless device may (re)start the time window without responding to receiving authorizations (e.g., UL authorizations and / or DL ​​authorizations) for one or more DCIs. The wireless device may (re)start the time window without responding to performing transmissions scheduled by authorizations (e.g., UL authorizations and / or DL ​​authorizations) in one or more UL and / or DL ​​authorizations for one or more subsequent transmissions of SDT. The wireless device may stop monitoring the PDCCH in response to the expiration of the time window. The wireless device may also stop executing the SDT and / or one or more subsequent transmissions of the SDT in response to the expiration of the time window.

[0306] Figure 21AAn example of time window management for one or more subsequent transmissions of an SDT according to an embodiment of this disclosure is illustrated. The wireless device may receive messages (e.g., RRC release messages) that include and / or indicate configuration parameters of the SDT. The configuration parameters may indicate uplink grants and / or one or more uplink radio resources for the SDT. Figure 21A In this context, the first SDT and the second SDT are transmissions via uplink grant and / or one or more uplink radio resources with periodicity. The wireless device may initiate a time window in response to transmitting uplink data via uplink grant and / or one or more uplink radio resources. For example, the wireless device may respond to performing... Figure 21A The first SDT (Short Term Distance) in the time window initiates the time window. This message may include the value of the time window. The radio device may monitor the PDCCH with one or more RNTIs during the time window. One or more RNTIs may be predefined and / or configured by the base station (e.g., indicated by one or more RRC messages that may include this message) for monitoring the PDCCH during the SDT and / or non-RRC_CONNECTED. For example, one or more RNTIs may include C-RNTIs. One or more RNTIs may include SDT-RNTIs. One or more RNTIs may include P-RNTIs (e.g., RNTIs for paging messages). During the time window, the radio device may receive one or more DCIs via the PDCCH. One or more DCIs may include UL authorizations for scheduling new UL transmissions. One or more DCIs may include UL authorizations for scheduling UL (re)transmissions. One or more DCIs may include DL authorizations for scheduling new DL transmissions. One or more DCIs may include DL authorizations for scheduling DL (re)transmissions. The radio device may maintain the operating time window independently of receiving one or more DCIs and / or independently of performing new UL and / or DL ​​transmissions and / or (re)transmissions. For example, a wireless device may stop or (re)start a time window without responding to receiving one or more DCIs and / or responding to performing a new UL and / or DL ​​transmission and / or (re)transmission. A wireless device may continue monitoring (and / or maintain monitoring) the PDCCH until the time window expires. A wireless device may stop monitoring the PDCCH in response to the expiration of the time window.

[0307] A wireless device may maintain a time window for SDT and / or one or more subsequent transmissions of SDT. The wireless device may receive a message from the base station including a value (e.g., length) of the time window. This value may instruct the wireless device to perform (e.g., be permitted to perform) the SDT and / or one or more subsequent transmissions of SDT for a period of time (or interval). This value may instruct the wireless device to monitor (e.g., be permitted to monitor) the PDCCH for a period of time (or interval) for receiving new UL and / or DL ​​transmissions and / or retransmissions of SDT and / or one or more UL and / or DL ​​authorizations for one or more subsequent transmissions of SDT. The wireless device may receive one or more DCIs via the PDCCH. One or more DCIs may include one or more UL and / or DL ​​authorizations. The wireless device may (re)start the time window in response to receiving authorizations (e.g., UL authorizations and / or DL ​​authorizations) for one or more DCIs. The wireless device may (re)start the time window in response to performing transmissions scheduled by authorizations (e.g., UL authorizations and / or DL ​​authorizations) of one or more subsequent transmissions of SDT. The wireless device may stop monitoring the PDCCH in response to the expiration of the time window. The wireless device may stop executing SDT and / or one or more subsequent transmissions of SDT in response to the expiration of the time window.

[0308] Figure 21B An example of time window management for one or more subsequent transmissions of an SDT according to an embodiment of this disclosure is illustrated. The wireless device may receive messages (e.g., RRC release messages) that include and / or indicate configuration parameters of the SDT. The configuration parameters may indicate uplink grants and / or one or more uplink radio resources for the SDT. Figure 21B In this context, the first SDT and the second SDT are transmissions via uplink grant and / or one or more uplink radio resources with periodicity. The wireless device may initiate a time window in response to transmitting uplink data via uplink grant and / or one or more uplink radio resources. For example, the wireless device may respond to performing... Figure 21BA first time window is initiated upon receiving the first SDT. This message may include the value of the first time window. During the first time window, the radio device may monitor the PDCCH with one or more RNTIs. One or more RNTIs may be predefined and / or configured by the base station (e.g., indicated by one or more RRC messages that may include this message) for monitoring the SDT and / or non-RRC_CONNECTED PDCCH. For example, one or more RNTIs may include C-RNTIs. One or more RNTIs may include SDT-RNTIs. One or more RNTIs may include P-RNTIs (e.g., RNTIs for paging messages). During the first time window, the radio device may receive a first DCI via the PDCCH. The first DCI may include a UL grant scheduling a new UL transmission. The first DCI may include a UL grant scheduling a UL (re)transmission of the first SDT. The first DCI may include a DL grant scheduling a new DL transmission. The radio device may initiate a second time window in response to receiving the first DCI and / or in response to performing a UL or DL ​​transmission scheduled by the first DCI. The second time window may have the same length as the first time window. For example, a wireless device may (re)start a first time window as a second time window in response to receiving a first DCI and / or in response to performing a UL or DL ​​transmission scheduled by the first DCI. The wireless device may monitor the PDCCH with one or more RNTIs during the second time window. The wireless device may initiate a new time window and / or (re)start the first time window in response to receiving a DCI and / or in response to performing a transmission scheduled by the DCI. Figure 21B In this context, the wireless device may initiate a third time window in response to receiving a second DCI during a second time window and / or in response to performing a UL or DL ​​transmission scheduled by the second DCI. The third time window may be a first time window that the wireless device (re)initiates in response to receiving a second DCI during a second time window and / or in response to performing a UL or DL ​​transmission scheduled by the second DCI. The wireless device may continue monitoring the PDCCH while a time window (e.g., a first time window, a second time window, and / or a third time window) is in operation for the SDT and / or its associated subsequent transmissions. If a time window expires, the wireless device may stop monitoring the PDCCH with one or more RNTIs. For example, in... Figure 21B In this context, if the wireless device has not yet received the DCI (e.g., based on one or more RNTIs) and / or if the third time window expires, the wireless device may stop monitoring the PDCCH.

[0309] Wireless devices can perform downlink and / or uplink beam management in conjunction with a base station. Downlink and / or uplink beam management may include downlink and / or uplink beam measurement procedures, (re)configuration of one or more beams (e.g., TCI status), beam (e.g., TCI status) activation of one or more beams, and beam selection in one or more beams. For example, TCI status may include DL TCI status and spatial relationship information (e.g., UL TCI status). Downlink and / or uplink beam management may include beam fault detection and / or beam fault recovery procedures. Wireless devices may perform downlink beam management and uplink beam management separately.

[0310] In this disclosure, the wireless device can perform downlink (e.g., PDSCH and / or PDCCH) and / or uplink beam management (e.g., PUSCH, PUCCH, and / or SRS) for transmission and / or reception in the RRC_CONNECTED state. In this disclosure, the wireless device can also perform downlink (e.g., PDSCH and / or PDCCH) and / or uplink (e.g., PUSCH, PUCCH, and / or SRS) beam management for transmission and / or reception in non-RRC_CONNECTED states (e.g., for SDT and one or more subsequent transmissions associated with the SDT).

[0311] Indicators of reference signals in downlink and / or uplink beam management can indicate the beam to be used (e.g., the TCI status of the wireless device, the TX beam, and / or the RX beam). For example, the wireless device can receive messages (e.g., RRC messages, RRC release messages, etc.) that include configuration parameters of one or more radio resources. Configuration parameters can include indications of one or more reference signals (e.g., indices). One or more reference signals can include an SSB identified by an SSB index / identifier, and a CSI-RS identified by a CSI-RS index / identifier (and / or a CSI-RS resource index / identifier). One or more reference signals can include an SRS identified by an SRS index / identifier (e.g., an SRS resource index / identifier, an SRS resource set index / identifier, and / or a combination thereof). Reference signals can represent and / or indicate a specific beam. For example, an SSB can represent and / or indicate a wide beam. For example, a CSI-RS can represent and / or indicate a narrow beam. For example, an SRS can represent and / or indicate the TX beam of the wireless device.

[0312] The configuration parameters in the message may include indicators that specify which reference signal is associated with which transmission (e.g., PUSCH, PUCCH, and / or SRS) and / or reception (e.g., PDCCH and / or PDSCH). Reference signals can be configured for radio link monitoring, radio link recovery, and / or transmission and / or reception in RRC_CONNECTED and / or non-RRC_CONNECTED states.

[0313] For example, configuration parameters may include indicators that specify which reference signals are associated with data reception (e.g., PDSCH) and / or control signal reception (e.g., PDCCH) in non-RRC_CONNECTED states. For example, data and / or control signals may be associated with transmissions via one or more radio resources. For example, reception may be used to receive responses to transmissions (e.g., RRC responses via PDSCH and / or L1 ACK / NACK / backoff via PDCCH). For example, the indicator may be a parameter for configuring QCL relationships between one or more DL reference signals (e.g., SSB and / or CSI-RS) and the DM-RS ports of the PDSCH, the DM-RS ports of the PDCCH, and / or the CSI-RS ports of the CSI-RS resources. Parameters may include one or more TCI states. Each of the one or more TCI states may include at least one of the following: one or more DL RSs (e.g., SSB, CSI-RS, and / or any combination thereof), cell index / identifier, BWP index / identifier, and / or QCL relationship type (e.g., indicating one or more large-scale attributes). For example, an indicator can be the TCI state of a specific channel configuration (e.g., PDSCH, PDCCH (e.g., CORESET)). For example, a PDSCH and / or PDCCH (e.g., CORESET) configuration can include at least one of one or more TCI states. For example, the TCI state of a PDSCH can indicate the QCL relationship between one or more DL reference signals (e.g., SSB and / or CSI-RS) and the DM-RS port of the PDSCH. A wireless device can determine the RX beam used for receiving data via the PDSCH based on the TCI state (e.g., the QCL relationship of the TCI state). For example, the TCI state of a PDCCH can indicate the QCL relationship between one or more DL reference signals (e.g., SSB and / or CSI-RS) and the DM-RS port of the PDCCH (e.g., CORESET). A wireless device can determine the RX beam used for receiving control signals via the PDCCH based on the TCI state (e.g., the QCL relationship of the TCI state).

[0314] A base station may transmit one or more messages to a radio device to indicate the TCI state to be used for receiving PDSCH and / or PDCCH (e.g., CORESET). The one or more messages may include RRC messages, MAC CE, and / or DCI. At least one of the one or more messages may configure the TCI state of the PDSCH and / or PDCCH. At least one of the one or more messages may activate the TCI state of the PDSCH and / or PDCCH. At least one of the one or more messages may schedule the PDSCH and / or PDCCH based on the TCI state.

[0315] In the example, the wireless device may receive one or more messages to (re)configure, update, and / or activate the TCI state of the PDSCH and / or PDCCH (e.g., CORESET). For example, a first control message (e.g., an RRC message) in one or more messages may indicate at least one TCI state to be used for the PDSCH and / or PDCCH (e.g., CORESET).

[0316] In the example, the wireless device may receive one or more messages that (re)configure, update, and / or activate the TCI states of the PDSCH and / or PDCCH (e.g., CORESET). For example, a first control message (e.g., an RRC message) in one or more messages may indicate one or more TCI states. A second control message (e.g., another RRC message, DCI, and / or MAC CE) in one or more messages may indicate at least one TCI state to be used for the one or more TCI states of the PDSCH and / or PDCCH (e.g., CORESET).

[0317] In the example, the wireless device may receive one or more messages that (re)configure, update, and / or activate the TCI states of the PDSCH and / or PDCCH (e.g., CORESET). For example, a first control message (e.g., an RRC message) in one or more messages may indicate one or more TCI states. A second control message (e.g., an RRC message, MAC CE, and / or DCI) in one or more messages may indicate (or activate) at least a first TCI state among one or more TCI states. A third control message (e.g., an RRC message, MAC CE, and / or DCI) in one or more messages may indicate at least a second TCI state among at least a first TCI state to be used for the PDSCH and / or PDCCH (e.g., CORESET).

[0318] The wireless device may receive configuration parameters including indicators that indicate which reference signals are associated with data (e.g., PUSCH) transmissions and / or control signal (e.g., PUCCH) transmissions associated with transmissions via one or more radio resources.

[0319] For example, indicators may include spatial relation information (e.g., UL TCI status). Spatial relation information can be used for transmissions via PUSCH, PUCCH, and / or SRS. Radio devices can determine (e.g., identify) specific spatial relation information based on its index and / or identifier. Spatial relation information can indicate at least one of the following: cell index / identifier, one or more DL RS (e.g., SSB, CSI-RS, and / or any combination thereof), SRS resource index / identifier, BWP index / identifier, path loss reference RS index / identifier, and / or power control parameters. Radio devices can determine the antenna port and / or precoder for transmissions via PUSCH and / or PUCCH based on spatial relation information.

[0320] For example, the indicator can be spatial relation information for a specific channel configuration (e.g., UL TCI status) (e.g., SRS-Spatial-Relationship-Information for PUSCH and / or PUCCH-PUCCH-Spatial-Relationship-Information for PUCCH). For example, a PUSCH configuration may include at least one spatial relation information. A PUCCH configuration may include at least one spatial relation information. The spatial relation information for PUSCH may differ from the spatial relation information for PUCCH. The spatial relation information for PUSCH may be the same as the spatial relation information for PUCCH. The spatial relation information for PUSCH and PUCCH may be configured separately and / or independently. There may be one or more spatial relation information applied to (and / or used for) PUSCH and PUCCH.

[0321] A wireless device can determine the antenna port and / or precoder for the PUSCH based on PUSCH spatial relation information. For example, the wireless device receives a message including configuration parameters for transmissions via one or more radio resources in and / or non-RRC_CONNECTED states. Configuration parameters (e.g., SRS resource indicators) can indicate the SRS resources of an SRS resource set. SRS resources can include spatial relation information. For transmissions via one or more radio resources, the wireless device can determine to use the same antenna port as the SRS port of the SRS resource. Based on this determination, the wireless device can transmit data via one or more radio resources using the same antenna port.

[0322] For example, a wireless device can determine the antenna port and / or precoder for the PUCCH based on the spatial relation information of the PUCCH. For instance, the wireless device receives a message including configuration parameters for the PUCCH in RRC_CONNECTED and / or non-RRC_CONNECTED states. The wireless device can transmit uplink control signals for HARQ feedback (e.g., ACK or NACK), SR transmission, and / or measurement reporting via the PUCCH to a PDSCH in a non-RRC_CONNECTED state. Configuration parameters (e.g., PUCCH spatial relation information) can indicate spatial settings (e.g., precoder and / or spatial domain filters) for PUCCH transmission and parameters for PUCCH power control. For PUCCH transmissions in a non-RRC_CONNECTED state, the wireless device can determine the spatial domain filter for receiving the DL RS indicated by the spatial relation information. For example, if the PUCCH spatial relation information includes the SSB index / identifier of the SSB, the wireless device can use the same spatial domain filter for receiving the SSB of the cell to transmit the PUCCH. For example, if the spatial relation information of the PUCCH includes the CSI-RS index / identifier of the CSI-RS (e.g., the NZP-CSI-RS resource index / identifier), the radio device can use the same spatial domain filter for receiving the cell's CSI-RS to transmit the PUCCH. Similarly, if the spatial relation information of the PUCCH includes the SRS index / identifier of the SRS (e.g., SRS resources), the radio device can use the same spatial domain filter for transmitting the cell's and / or UL BWP's SRS.

[0323] A base station may transmit one or more messages to a wireless device to indicate spatial relation information (e.g., UL TCI status) for transmissions of PUSCH, PUCCH, and / or SRS. The one or more messages may include RRC messages, MAC CE, and / or DCI. At least one of the one or more messages may configure the spatial relation information (e.g., UL TCI status) of PUSCH, PUCCH, and / or SRS. At least one of the one or more messages may activate the spatial relation information (e.g., UL TCI status) of PUSCH, PUCCH, and / or SRS. At least one of the one or more messages may schedule PUSCH, PUCCH, and / or SRS based on the spatial relation information (e.g., UL TCI status).

[0324] In the example, the wireless device may receive one or more messages that (re)configure, update, and / or activate spatial relation information for PUSCH, PUCCH, and / or SRS. For example, a first control message (e.g., an RRC message) in one or more messages may indicate at least one piece of spatial relation information (e.g., UL TCI status) to be used for PUSCH, PUCCH, and / or SRS.

[0325] In the example, the wireless device may receive one or more messages that (re)configure, update, and / or activate spatial relation information for PUSCH, PUCCH, and / or SRS. For example, a first control message (e.g., an RRC message) in one or more messages may indicate one or more spatial relation information (e.g., UL TCI status). A second control message (e.g., another RRC message, DCI, and / or MAC CE) in one or more messages may indicate at least one of the one or more spatial relation information to be used for PUSCH, PUCCH, and / or SRS.

[0326] In the example, the wireless device may receive one or more messages that (re)configure, update, and / or activate spatial relationship information for PUSCH, PUCCH, and / or SRS. For example, a first control message (e.g., an RRC message) in one or more messages may indicate one or more spatial relationship information (e.g., UL TCI status). A second control message (e.g., an RRC message, MAC CE, and / or DCI) in one or more messages may indicate (or activate) at least a first spatial relationship information among one or more spatial relationship information. A third control message (e.g., an RRC message, MAC CE, and / or DCI) in one or more messages may indicate at least a second spatial relationship information among at least the first spatial relationship information to be used for PUSCH, PUCCH, and / or SRS.

[0327] Figure 22An example of beam management for transmission and / or reception in a non-RRC_CONNECTED state is illustrated according to an embodiment of this disclosure. A wireless device may receive a message including configuration parameters for transmission / reception in a non-RRC_CONNECTED state. The configuration parameters may indicate the configuration of radio resources for PUSCH, PDCCH, PDSCH, and / or PUCCH in a non-RRC_CONNECTED state. The configuration parameters may indicate one or more radio resources for uplink transmission (e.g., via PUSCH) in a non-RRC_CONNECTED state. The configuration parameters may indicate which beams (e.g., reference signals) are used for transmission (e.g., via PUSCH and / or PUCCH) or reception (e.g., via PDSCH and / or PDCCH) in a non-RRC_CONNECTED state. For example, a wireless device may receive a MAC CE and / or DCI, which indicates which beams (e.g., reference signals) are used to transmit (e.g., via PUSCH and / or PUCCH) or receive (e.g., via PDSCH and / or PDCCH) in a non-RRC_CONNECTED state.

[0328] For example, by default, wireless devices can use the same beam for uplink transmissions (e.g., PUSCH and / or PUCCH). For example, by default, wireless devices can use the same beam for downlink transmissions (e.g., PDSCH and / or PDCCH). For example, by default, wireless devices can use the same beam between PUSCH and one or more transmissions (e.g., PDSCH, PDCCH, and / or PUCCH).

[0329] For example, in Figure 22 In the non-RRC_CONNECTED state, the wireless device uses a first beam to transmit data via one or more radio resources. The wireless device may begin using a third beam to monitor the PDCCH. The wireless device may receive a downlink assigned DCI, including the PDSCH, via the PDCCH. The wireless device may use a fourth beam to receive the PDSCH. The wireless device may use a second beam to transmit HARQ feedback (e.g., ACK or NACK) via the PUCCH. The base station may use different beams and / or the same beams to receive or transmit data, for example, a first beam for PUSCH reception, a second beam for PDCCH transmission, a third beam for PDSCH transmission, and / or a fourth beam for PUCCH reception. The wireless device may receive second messages (e.g., RRC messages, MAC CE, DCI, and / or combinations thereof) to reconfigure, change, activate / deactivate, and / or update the beam configuration of the PUSCH, PDCCH, PDSCH, and / or PUCCH.

[0330] In multi-beam operation, a cell may use one or more beams (e.g., the cell's TX beam) to transmit one or more DL RSs (e.g., multiple SSBs, CSI / RS, etc.). For example, each of the one or more beams may be associated with at least one of the one or more DL RSs. For example, each of the channels used for transmission and / or reception of the cell (e.g., PDCCH, PDSCH, PUSCH, and / or PUCCH) may be associated with at least one of the one or more beams (e.g., at least one of the one or more DL RSs).

[0331] For example, a wireless device may receive a message including radio resource configuration parameters (e.g., RRC messages, MACCE, DCI, and / or any combination thereof) indicating which beam is associated with which channel (e.g., PDCCH, PDSCH, PUSCH, and / or PUCCH). For example, the radio resource configuration parameters may indicate the beam configuration of a channel, such as TCI status (and / or DL ​​TCI status) and / or spatial relation information (and / or UL TCI status), including a first DL RS among multiple DLRSs. The first DL RS may represent and / or indicate a first beam (e.g., as shown in Figure 21). For example, one of the multiple DL RSs may be associated with one or more channels (e.g., PDCCH, PDSCH, PUSCH, and / or PUCCH). The wireless device may determine the antenna port and / or precoder (e.g., spatial domain filter) to be used for transmission and / or reception via the channel based on this association. For example, the wireless device may determine the antenna port and / or precoder (e.g., spatial domain filter) based on the antenna port and / or precoder used to receive the first DL RS.

[0332] For SDT, a radio device may, for example, use one or more beams (e.g., the TX beam of a cell) to receive messages from a base station indicating one or more DL RSs (e.g., multiple SSBs, CSI / RS, etc.). The radio device may determine the radio device's transmission parameters (e.g., TX antenna parameters) for PUSCH, PUCCH, and / or SRS based on at least one of the one or more DL RSs. The radio device may determine the radio device's reception parameters (e.g., RX antenna parameters) for PDSCH and / or PDCCH based on at least one of the one or more DL RSs.

[0333] In the example, a message from a radio device in an SDT can indicate a DL RS (e.g., SSB, CSI / RS, etc.) to be used for PDCCH, PDSCH, PUSCH, PUCCH, and / or SRS. In the example, the message can indicate a first DL RS (e.g., SSBs, CSI / RS, etc.) for uplink transmissions (e.g., PUSCH, PUCCH, and / or SRS). In the example, the message can indicate a second DL RS (e.g., SSB, CSI / RS, etc.) for downlink receptions (e.g., PDCCH and / or PDSCH). In the example, the message can indicate one or more DL RSs (e.g., SSBs, CSI / RS, etc.), each DL RS dedicated to a specific channel for PDCCH, PDSCH, PUSCH, PUCCH, and / or SRS. The DL RS indicated by a message from a first channel (e.g., PDCCH, PDSCH, PUSCH, PUCCH, and / or SRS) may be the same as the DL RS indicated by a message from a second channel (e.g., PDCCH, PDSCH, PUSCH, PUCCH, and / or SRS). Conversely, the DL RS indicated by a message from a first channel (e.g., PDCCH, PDSCH, PUSCH, PUCCH, and / or SRS) may be different from the DL RS indicated by a message from a second channel (e.g., PDCCH, PDSCH, PUSCH, PUCCH, and / or SRS).

[0334] For SDT, a radio device may, for example, use one or more beams (e.g., the TX beam of a cell) to receive messages from a base station indicating one or more DL RSs (e.g., multiple SSBs, CSI / RS, etc.). The radio device may select at least one of the one or more DL RSs. The radio device may select at least one transmission parameter (e.g., TX antenna parameters) from the radio device to determine the PUSCH, PUCCH, and / or SRS. The radio device may select at least one DL RS from the one or more DL RSs to determine the radio device's reception parameters (e.g., RX antenna parameters) from the radio device's PDSCH and / or PDCCH.

[0335] In the example, a message from a radio device in an SDT can indicate one or more DL RSs (e.g., one or more SSBs, CSI / RS, etc.) to be used for the PDCCH, PDSCH, PUSCH, PUCCH, and / or SRS. The radio device can select at least one DL RS from the one or more DL RSs in the SDT. For example, the radio device can initiate an SDT, for instance, in response to uplink data available in a buffer and / or in response to uplink grants (or uplink radio resources for uplink grants) available for the SDT. The radio device can determine or select at least one DL RS from the one or more DL RSs in the PDCCH, PDSCH, PUSCH, PUCCH, and / or SRS of the SDT.

[0336] The determination and / or selection of at least one DL RS can be based on measurements of one or more DL RSs (e.g., RSRP values). For example, the message may include and / or indicate a power threshold. The wireless device can measure the RSRP of one or more DL RSs. For example, the wireless device can select at least one DL RS based on the fact that the RSRP value of at least one DL RS is greater than a power threshold. For example, the wireless device can select at least one DL RS based on the fact that the RSRP value of at least one DL RS is the largest among the RSRP values ​​of one or more DL RSs.

[0337] A wireless device can select at least one DL RS from one or more DL RSs for use in the PUSCH of the SDT (and / or one or more subsequent transmissions of the SDT). The wireless device can determine the configuration of the PUSCH of the SDT and / or the uplink radio resources of the SDT based on at least one DL RS. For example, the wireless device can receive a message including a set of uplink radio resources. This message may include a configuration containing the set of uplink radio resources. The message may include one or more configurations. Each of the one or more configurations may include one uplink radio resource from the uplink radio resources. The message may indicate that each uplink radio resource is associated with one of the one or more DL RSs. For example, if the message indicates that a first uplink grant (and / or a first uplink radio resource) is associated with at least one DL RS from one or more DL RSs, the wireless device can select the first uplink grant (and / or the first uplink radio resource) from the set of uplink radio resources. Wireless devices can use the antenna configuration of at least one of one or more DL RSs (e.g., spatial relation information and / or UL TCI status) to transmit uplink data (via CG-based SDT and / or RA-based SDT).

[0338] Similarly, for SDT and / or one or more subsequent transmissions thereof, the wireless device can determine the uplink radio resources for PUCCH and / or SRS based on the selection of one of the one or more DL RSs. For example, the wireless device can receive a message indicating one or more radio resources for PUCCH and / or SRS. The one or more radio resources may be dedicated to a specific DL RS. For example, the wireless device can select one of the one or more DL RSs based on the RSRP of one or more DL RSs. For example, the RSRP value of a DL RS may be greater than a power threshold. For example, the RSRP value may be the largest RSRP value among the RSRP values ​​of one or more DL RSs. For example, the first DL RS among one or more DL RSs may be configured, for example, the spatial relation information (and / or ULTCI status) of the first radio resource of one or more radio resources. For transmissions via a first channel (e.g., PUSCH), the wireless device can determine (and / or select) one or more DL RSs (e.g., spatial relation information and / or ULTCI status) as the DL RS for transmissions via a second channel (e.g., PUCCH and / or SRS). Wireless devices can determine (and / or select) one or more DL RSs (e.g., spatial relation information and / or UL TCI status) in each transport channel (e.g., PUSCH, PUCCH, and / or SRS).

[0339] A wireless device can select at least one DL RS from one or more DL RSs for use in the SDT's PDCCH (e.g., CORESET) (and / or one or more subsequent transmissions of the SDT). The wireless device can determine the configuration of the downlink radio resources for the SDT's PDCCH (e.g., CORESET of PDCCH) and / or the SDT's PDCCH based on at least one DL RS. For example, the wireless device can receive a message containing a set of downlink radio resources (e.g., CORESET) that includes a downlink control channel. This message can include a configuration that includes the set of downlink radio resources (e.g., CORESET). The message can include one or more configurations. Each of the one or more configurations can include one downlink radio resource (e.g., CORESET) from the downlink radio resources. The message can indicate that each downlink radio resource is associated with one or more DL RSs. The association between each downlink radio resource and one or more DL RSs can be predefined. For example, the wireless device can select at least one DL RS from one or more DL RSs, for example, based on the RSRP value of one or more DL RSs. The RSRP value of at least one DL RS can be greater than a power threshold. The RSRP value of at least one DL RS can be the largest RSRP value among the RSRP values. For example, if a first downlink radio resource (e.g., CORESET) is associated with at least one of one or more DL RSs, the wireless device can select the first downlink radio resource (e.g., CORESET) from the set of downlink radio resources (e.g., CORESET). The wireless device can use the antenna configuration (e.g., TCI state) of at least one of one or more DL RSs to receive control signals (e.g., DCI) via the first downlink radio resource (via CG-based SDT and / or RA-based SDT).

[0340] Similarly, for SDT and / or one or more subsequent transmissions thereof, the wireless device can determine the downlink radio resources of the PDSCH based on the selection of one of the one or more DL RSs. For example, the wireless device can receive a message indicating one or more radio resources of the PDSCH. The one or more radio resources may be dedicated to a specific DL RS. For example, the wireless device can select one of the one or more DL RSs based on the RSRP of one or more DL RSs. For example, the RSRP value of a DL RS may be greater than a power threshold. For example, the RSRP value may be the largest RSRP value among the RSRP values ​​of one or more DL RSs. For example, the first DL RS among one or more DL RSs may be configured as, for example, the DL TCI state of the first radio resource of one or more radio resources. For reception via a first channel (e.g., PDCCH), the wireless device can determine (and / or select) one or more DL RSs (e.g., DL TCI state) as the DL RS for reception via a second transmission channel (e.g., PDSCH). The wireless device can determine (and / or select) one or more DL RSs (e.g., DL TCI state) for each transmission channel (e.g., PDCCH and / or PDSCH).

[0341] For reception via one or more channels (e.g., PDCCH and / or PDSCH), the wireless device may determine (and / or select) one or more DL RSs (e.g., DL TCI status) as reception via a second transmission channel (e.g., PDSCH). The wireless device may determine (and / or select) one or more DL RSs (e.g., spatial relation information and / or UL TCI status) for each transmission channel (e.g., PDCCH and / or PDSCH).

[0342] A wireless device can determine (and / or select) one or more DLRSs (e.g., DLRSs for spatial relation information) configured and / or selected for a transmission (e.g., PUSCH via SDT) as received DLRSs (e.g., DL RSs for DL ​​TCI status) via one or more channels (e.g., PDCCH and / or PDSCH) of the transmission. For example, a wireless device can select DLRSs for an uplink transmission of SDT and / or one or more associated subsequent transmissions of it, for example, based on the RSRP of one or more DLRSs. A wireless device can use DLRSs to receive PDCCH and / or PDSCH. For example, a wireless device can determine that the DM-RS antenna port associated with PDCCH reception and / or PDSCH reception is quasi-co-located with DLRSs (e.g., SS / PBCH blocks and / or CSI-RS resources) determined and / or selected by the wireless device for an uplink transmission of SDT and / or one or more associated subsequent transmissions of it.

[0343] In this disclosure, the DL RS selected for PUSCH, PDSCH, PDCCH, and / or PUCCH in a non-RRC_CONNECTED state may be referred to as the DL RS of the common TCI and / or default TCI. For example, the common TCI and / or default TCI may be referred to as the TCI for one or more uplink (e.g., PUSCH and / or PUCCH) and / or downlink (e.g., PDSCH and / or PDCCH) transmissions.

[0344] A radio device may, for example, in a non-RRC_CONNECTED state, monitor a set of one or more PDCCH candidates in a CORESET on an active DL BWP on a serving cell (e.g., each active serving cell) configured for PDCCH monitoring. An active DL BWP may be the initial DL BWP. An active DL BWP may be, for example, the first active DL BWP different from the initial DL BWP. For example, a message received by the radio device (e.g., an RRC release message) may indicate a transition to a non-RRC_CONNECTED state and may indicate the first active BWP in the non-RRC_CONNECTED state. An active DL BWP may be a DL BWP configured for the radio device to receive RA-based SDT and / or CG-based SDT. An active DL BWP may be a DL BWP that indicates the radio device transitioning from an RRC_CONNECTED state to a non-RRC_CONNECTED state. For example, an active DL BWP may be the last active DL BWP before the radio device transitions from an RRC_CONNECTED state to a non-RRC_CONNECTED state. An active DL BWP can be an RRC release message that indicates a transition from the RRC_CONNECTED state to a non-RRC_CONNECTED state received by a wireless device.

[0345] In a non-RRC_CONNECTED state, monitoring a set of PDCCH candidates in one or more CORESETs can be based on a corresponding search space set. Monitoring a set of PDCCH candidates in one or more CORESETs can be described as decoding (e.g., attempting to decode) at least one PDCCH candidate based on the DCI format monitored in one or more CORESETs. In this disclosure, receiving DCI via PDCCH can be described as detecting and / or receiving DCI having one of the monitored DCI formats based on decoding PDCCH candidates including PDCCH with the monitored DCI format. In this disclosure, receiving PDCCH can be interchanged with receiving DCI (e.g., DCI format). For example, receiving PDCCH can be described as detecting and / or receiving DCI having one of the monitored DCI formats based on decoding PDCCH candidates including PDCCH with the monitored DCI format.

[0346] For example, the set of PDCCH candidates to be monitored by the radio device can be defined in terms of the PDCCH search space (SS) set. The search space set may include a common search space (CSS) set and / or a radio device-specific search space set. The radio device-specific search space set may be referred to as the UE-specific search space (USS) set.

[0347] A wireless device in a non-RRC_CONNECTED state may monitor PDCCH candidates in at least one of the following search space sets: CSS for receiving MIBs and / or SIBs (e.g., Type 0-PDCCH CSS set); CSS for receiving other system information (e.g., information other than SIB1) (e.g., Type 0A-PDCCH CSS set); CSS for random access procedures (e.g., Type 1-PDCCH CSS set); CSS for paging procedures (e.g., Type 2-PDCCH CSS set); CSS for receiving group common information (e.g., DCI) (e.g., Type 3-PDCCH CSS); and / or one or more USS sets of the wireless device.

[0348] For example, the Type0-PDCCH CSS set (e.g., CSS for receiving MIB and / or SIB) can be configured by pdcch-ConfigSIB1 in the MIB, searchSpaceSIB1 in PDCCH-ConfigCommon, and / or searchSpaceZero in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by SI-RNTI, for example, on the cell (e.g., the primary cell of the MCG). The Type0A-PDCCH CSS set (e.g., CSS for receiving other system information) can be configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by SI-RNTI, for example, on the cell (e.g., the primary cell of the MCG). The Type1-PDCCH CSS set (e.g., CSS for random access procedures) can be configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by RA-RNTI, MsgB-RNTI, and / or TC-RNTI, for example, on the cell (e.g., the primary cell of the MCG). The Type 2-PDCCH CSS set (e.g., CSS for paging procedures) can be configured by the pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by P-RNTI, for example, on a cell (e.g., the primary cell of an MCG). The Type 3-PDCCH CSS set (e.g., CSS for receiving group common information) can be configured by the SearchSpace in PDCCH-Config with searchSpaceType=common for a DCI format with a CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, and / or CI-RNTI, and for example, on a cell (e.g., the primary cell), C-RNTI, MCS-C-RNTI, CS-RNTI, and / or PS-RNTI. The USS set can be configured by the SearchSpace in the PDCCH-Config with searchSpaceType=ue-Specific for a DCI format with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI and / or SL-L-CS-RNTI.

[0349] For example, a specific CORESET can be associated with a specific DL RS (e.g., SSB). For example, the position of a CORESET (e.g., for a Type0-PDCCH CSS set) can be relative to the position of a DL RS (e.g., SSB). A CORESET determined relative to a DL RS (e.g., SSB) (e.g., for a Type0-PDCCH CSS set) can be referred to as CORESET#0. CORESET#0 can be used for PDCCH monitoring of the Type0-PDCCH CSS set. CORESET#0 can be used for PDCCH monitoring of a specific search space (e.g., search space zero). For example, when the search space is set to a specific search space (e.g., search space zero), CORESET#0 can be used for PDCCH monitoring of the search space. For example, in a non-RRC_CONNECTED state, CORESET#0 can be used for PDCCH monitoring of the paging search space. For example, when the paging search space is set to search space zero, CORESET#0 can be used for PDCCH monitoring of the paging search space.

[0350] CORESET can be multiplexed with SS / PBCH blocks in the time and / or frequency domains. For example, for a given SS / PBCH block, a wireless device can determine its associated CORESET based on the multiplexing mode. Multiplexing CORESET and SS / PBCH blocks in the time domain can be referred to as multiplexing mode 1 (or any given number). For example, the size of the CORESET can be signaled so that it fits within the carrier bandwidth. Multiplexing CORESET and SS / PBCH blocks in the frequency domain can be referred to as multiplexing mode 2 and / or 3 (or any given number). Multiplexing modes 2 and / or 3 can be used, for example, for fast beam sweeping for FR2.

[0351] The wireless device can determine the CORESET (e.g., the location of CORESET#0) of the search space (SS) set (e.g., CSS and / or Type0-PDCCHCSS set) of the MIB and / or SIB. The wireless device can determine the number of resource blocks (e.g., contiguous resource blocks) and symbols (e.g., contiguous symbols) of the CORESET of the SS set (e.g., CSS and / or Type0-PDCCHCSS set). For example, the determination of the number of resource blocks and / or symbols can be based on configuration parameters received by the wireless device, such as controlResourceSetZero in pdcch-ConfigSIB1. For example, for this determination, one or more first sets (e.g., in a table) can be predefined and / or semi-statically configured by higher-level messages (e.g., SIB and / or RRC messages). Each of the one or more first sets can include one or more first values ​​for determining the number of resource blocks and / or symbols. For example, the configuration parameter (e.g., controlResourceSetZero) can include an identifier (e.g., the value of controlResourceSetZero) indicating a particular set among the one or more first sets. For example, one or more values ​​may include SS / PBCH blocks and CORESET multiplexing mode, the number of RBs (e.g., ), the number of symbols (e.g., And / or offset (RB). For example, for a frequency band with a specific channel bandwidth (e.g., minimum channel bandwidth), one or more first sets can be predefined and / or semi-statically configured by higher-layer messages (e.g., SIB and / or RRC messages) for the SCS of the SS / PBCH block and / or the SCS of the CORESET. One or more first sets may include different values ​​for spare spectrum channel access and non-shared spectrum channel access.

[0352] For example, for a frequency band with a specific channel bandwidth (e.g., minimum channel bandwidth), a table including one or more first sets can be predefined for a given SCS of the SS / PBCH block and / or the SCS of the CORESET. The wireless device can receive configuration parameters (e.g., controlResourceSetZero) that may include an identifier (e.g., the value of controlResourceSetZero) indicating a specific set within one or more first sets. This specific set may include values ​​for the SS / PBCH block and CORESET multiplexing mode, the number of RBs (e.g., ...). ), the number of symbols (e.g., ) and / or offset (RB). The wireless device can use the location of the SSB and / or the values ​​of the SS / PBCH block and CORESET multiplexing mode, the number of RBs (e.g., ), the number of symbols (e.g., The number of resource blocks (e.g., contiguous resource blocks) and symbols (e.g., contiguous symbols) in the CORESET of the SS set (e.g., CSS and / or Type0-PDCCH CSS set) are determined by offsets (RB) and / or offsets (RB).

[0353] The wireless device can determine the PDCCH monitoring timing based on configuration parameters (e.g., searchSpaceZero in pdcch-ConfigSIB1 included in the MIB). For example, for determining the PDCCH monitoring timing, one or more second sets (e.g., in a table) can be predefined and / or semi-statically configured by higher-layer messages (e.g., SIB and / or RRC messages). Each of the one or more second sets can include one or more second values ​​for determining the PDCCH monitoring timing. For example, configuration parameters (e.g., searchSpaceZero) can include identifiers (e.g., the value of searchSpaceZero) indicating a particular set among the one or more second sets. For example, one or more second values ​​can include the value of M, the value of O, the number of search space sets per time slot, and / or the first symbol index. One or more second sets can be predefined and / or semi-statically configured by higher-layer messages (e.g., SIB and / or RRC messages) for SS / PBCH blocks and CORESET multiplexing modes, frequency bands (e.g., FR1, FR2, FR3, etc.), SCS of SS / PBCH blocks, and / or SCS of CORESETs. One or more second sets may include different values ​​for backup spectrum channel access and non-shared spectrum channel access.

[0354] SFN C and n C It can be the intra-frame SFN and slot index of a CORESET-based SCS. SSB,i and n SSB,i These can be the SFN and slot index of the SCS based on CORESET, where the SS / PBCH block with index i is temporally related to the system frame SFN. SSB,i and time slot n SSB,i Overlap. Symbols of CORESET associated with pdcch-ConfigSIB1 in MIB and / or searchSpaceSIB1 in PDCCH-ConfigCommon can have normal cyclic prefixes.

[0355] In the example, for operations without shared spectrum channel access, the wireless device can determine that the offset in the indicated set of one or more first sets can be defined relative to the SCS of the CORESET of the Type0-PDCCH CSS set (e.g., provided by subCarrierSpacingCommon) from the RB index (e.g., minimum RB index) of the CORESET of the Type0-PDCCH CSS set to the RB index (e.g., minimum RB index) of the common RB that overlaps with the first RB of the corresponding SS / PBCH block.

[0356] In the example, for operations with shared spectrum channel access, the wireless device can determine an offset from the first RB index (e.g., the minimum RB index) of the CORESET of the Type 0-PDCCHCSS set to the second RB index (e.g., the minimum RB index) of a common RB that overlaps with the first RB of the corresponding SS / PBCH block. For example, if the frequency location of the SS / PBCH block corresponds to the GSCN (Global Synchronization Channel Number) of a predefined synchronization grating entry, the wireless device can determine the offset based on the offset in the indicated set of one or more first sets. If the frequency location of the SS / PBCH block is provided by ssbFrequency in a measurement configuration associated with a reporting configuration providing reportCGI, and does not correspond to the GSCN of a synchronization grating entry, the wireless device can determine the offset based on the sum of the first offset and the second offset. For example, the first offset can be an offset in the indicated set of one or more first sets. For example, the wireless device can determine the second offset as an offset from the minimum RB index of a common RB that overlaps with the first RB of the SS / PBCH block indicated in the measurement configuration to the minimum RB index of a common RB that overlaps with the first RB of the SS / PBCH block assumed to be located at the GSCN of the synchronization grating entry. A single synchronization grating entry can be located in the same channel as the SS / PBCH block used for the shared spectrum channel access procedure. For example, the offset can be defined relative to the SCS of the CORESET of the same Type 0-PDCCH CSS set as the corresponding SS / PBCH block.

[0357] In the example, for operations without shared spectrum channel access and / or for SS / PBCH blocks and CORESET multiplexing mode 1, the radio device can monitor the PDCCH in the Type0-PDCCH CSS set over two consecutive time slots (e.g., a predefined number of time slots) starting from time slot n0. For an SS / PBCH block with index i, the UE determines the index of time slot n0 as... if Then it is in the system frame number (SFN) SFN C Satisfy SFN CIn frames where mod2 = 0, or if Then it satisfies SFN in SFN. C In frames where mod2 = 1, M and O can be provided by the indicated set in one or more second sets, and μ ∈ {0,1,2,3} is based on the SCS used for PDCCH reception in CORESET. The index of the first symbol of CORESET in slots n0 and n0+1 can be the first symbol index provided by the indicated set in one or more second sets. It can be the number of time slots in a frame where SCS = μ (e.g., SCS of CORESET).

[0358] For operations with shared spectrum channel access and for SS / PBCH blocks and CORESET multiplexing mode 1, the wireless device can monitor PDCCHs in the Type 0-PDCCH CSS set on a time slot. This time slot can include Type 0-PDCCH monitoring timing associated with an SS / PBCH block that can be quasi-co-located with the SS / PBCH blocks of the CORESET that provide the Type 0-PDCCH CSS set with respect to average gain, quasi-co-location 'type A', and 'type D' properties. For candidate SS / PBCH block indexes... in Two consecutive time slots starting from time slot n0 can include associated Type 0-PDCCH monitoring opportunities. The wireless device can determine the index of time slot n0 as... For example, if Then it can be in the system frame number (SFN) SFN C Satisfy SFN C In frames where mod 2 = 0, or for example, if Then it can satisfy SFN. C In frames where mod 2 = 1, M and O are provided by the indicated set in one or more second sets, and μ ∈ {0,1} is based on the SCS used for PDCCH reception in CORESET. The index of the first symbol of CORESET in slots n0 and n0+1 is the first symbol index provided by the indicated set in one or more second sets. When At that time, the wireless device may not be configured with M=1 / 2 or M=2.

[0359] For SS / PBCH blocks and CORESET multiplexing modes 2 and 3, the radio device can monitor PDCCHs in the Type0-PDCCH CSS set on a single time slot (e.g., a predefined number of time slots), where the period of the Type0-PDCCH CSS set is equal to the period of the SS / PBCH block. For SS / PBCH blocks and CORESET multiplexing modes 2 and 3, if the active DL BWP is the initial DL BWP, the radio device can use SS / PBCH blocks that provide a CORESET with a Type0-PDCCH CSS set to perform radio link monitoring and / or measurements for radio resource management. For an SS / PBCH block with index i, the UE determines the time slot index n based on parameters provided by the indicated set from one or more second sets. C and SFN C .

[0360] If the wireless device detects the first SS / PBCH block and determines that there is no CORESET for the Type 0-PDCCH CSS set, and for FR1 24≤k SSB ≤29 or 12≤k for FR2 SSB ≤13, the wireless device can determine the closest Global Synchronization Channel Number (GSCN) (in the corresponding frequency direction) of the second SS / PBCH block of the CORESET with the associated Type0-PDCCH CSS set as It can be the GSCN of the first SS / PBCH block. The GSCN offset can be provided by a predefined table. The predefined table can be defined in response to frequency bands (e.g., FR1, FR2, FR3, etc.). The predefined table can include values ​​specific to k. SSB of One or more values. For example, the quantity k. SSB It can be from a public resource block The subcarrier offset from subcarrier 0 in the SS / PBCH block to subcarrier 0, where This can be obtained from higher-layer parameters (e.g., offsetToPointA). If the radio device detects a second SS / PBCH block, and the second SS / PBCH block does not provide a CORESET for the Type 0-PDCCH CSS set, the radio device can ignore the GSCN information related to the SS / PBCH block location to perform cell search.

[0361] If the wireless device detects the SS / PBCH block and determines that there is no CORESET for the Type 0-PDCCH CSS set, and for FR1 k SSB =31 or k for FR2SSB =15, wireless devices can be determined to be within GSCN range. There is no SS / PBCH block with an associated Type0-PDCCH CSS set. The wireless device can determine this based on controlResourceSetZero and searchSpaceZero in pdcch-ConfigSIB1. and If the GSCN range is The radio device can then determine that there is no information on a second SS / PBCH block with an associated Type 0-PDCCH CSS set in the detected SS / PBCH block. If the radio device does not detect any SS / PBCH block with a Type 0-PDCCH CSS set in the CORESET within a certain time period, the radio device can ignore the GSCN information related to the SS / PBCH location when performing a cell search.

[0362] For example, in a non-RRC_CONNECTED state, the wireless device can determine the DL RS for downlink reception. For example, downlink reception may include receiving downlink packets via PDSCH. For example, downlink reception may include monitoring, receiving, and / or detecting one or more PDCCH candidates. For example, downlink reception may include monitoring, receiving, and / or detecting one or more DCI formats via PDCCH and / or PDCCH CORESET. For example, the wireless device can use DL RS to determine antenna configuration parameters (e.g., DM-RS antenna ports) associated with downlink reception.

[0363] For example, a wireless device can determine a specific DL RS for downlink reception. The determination of a specific DL RS can be predefined and / or semi-statically configured by higher-layer messages (e.g., SIB and / or RRC messages). The DL RS can be an SS / PBCH block and / or CSI-RS resource. The wireless device can, for example, determine, based on the determined specific DL RS, the quasi-co-addressable DM-RS antenna port associated with downlink reception with the SS / PBCH block or CSI-RS resource of the DL RS.

[0364] In this disclosure, the determination of the downlink received DL RS can be referred to as the determination of the downlink received TCI and / or can be interchanged with that determination. In this disclosure, the determination of the downlink received DL RS can be referred to as the determination of the downlink received DM-RS antenna port and / or can be interchanged with that determination.

[0365] A wireless device can determine a DL RS for monitoring one or more PDCCH candidates. The wireless device can monitor one or more PDCCH candidates via a specific search space and / or a specific core set. The DL RS used for monitoring one or more PDCCH candidates can be indicated by configuration parameters of the specific search space and / or the specific core set. For example, the TCI of a specific search space and / or a specific core set (e.g., DL TCI, UL TCI, common (DL / UL) TCI, combined (DL / UL) TCI, etc.) can include a DL RS.

[0366] The wireless device can determine the DL RS for downlink reception (e.g., PDCCH and / or PDSCH) in a non-RRC_CONNECTED state based on the initial access procedure (MIB (or SIB) reception / acquisition) and / or random access procedure. For example, the wireless device can use the DL RS used for and / or selected for the initial access procedure and / or random access procedure to determine the antenna configuration parameters for downlink reception in a non-RRC_CONNECTED state.

[0367] The wireless device can receive paging messages from the base station via a paging procedure. The wireless device can monitor the PDCCH (e.g., paging search space). The wireless device can detect a DCI format with a CRC scrambled by a P-RNTI via the PDCCH. The DCI format may include downlink assignments for short messages and / or PDSCHs including paging messages. The P-RNTI may be an identifier used by the wireless device to receive downlink assignments for short messages and / or PDSCHs. The wireless device can monitor the PDCCH periodically and / or scheduled (e.g., based on paging configuration parameters). The wireless device can receive configuration parameters for the paging procedure. The wireless device can determine the timing of PDCCH monitoring based on the configuration parameters. For example, the wireless device can determine the period for monitoring the PDCCH, the PDCCH paging search space, and / or the PDCCH CORESET based on the configuration parameters. The wireless device can receive configuration parameters from broadcast messages (e.g., SIBs), private messages (e.g., RRC messages), and / or combinations thereof.

[0368] For example, when the wireless device is not in RRC_CONNECTED, a paging procedure (and / or paging message) can be used for network-initiated connection setup (e.g., network-initiated RRC connection setup). The paging procedure may include transmitting short messages (e.g., short messages defined as information carried by one or more bits in downlink control messages / signals such as DCI, MAC CE, and / or RRC messages) in one or more RRC states (e.g., non-RRC_CONNECTED and / or RRC_CONNECTED states). For example, the short message may include indications of system information updates and / or public warnings.

[0369] One or more wireless devices can receive short messages, such as the same short message. Each of the one or more wireless devices can be in the same RRC state. Each of the one or more wireless devices can be in a different RRC state. For example, the network and / or base station can transmit short messages to one or more wireless devices, regardless of whether the one or more wireless devices are in a non-RRC_CONNECTED state or an RRC_CONNECTED state.

[0370] The wireless device can receive and / or detect a PDCCH with a P-RNTI (e.g., a DCI format with a CRC scrambled by the P-RNTI). The wireless device can determine the contents of the PDCCH. One or more bits (e.g., 2 bits) in the PDCCH can be used to indicate the presence or absence of a short message on the PDCCH and / or the presence or absence of a paging message on the PDSCH.

[0371] The PDCCH (e.g., a DCI format with a CRC scrambled by P-RNTI) may include one or more bits (e.g., 8 bits) indicating a short message. One or more first features of these bits may indicate whether system information (or a portion of system information), such as one or more SIBs other than a specific SIB (e.g., SIB6, SIB7, and / or SIB8 including configuration parameters for earthquake and tsunami warning systems and / or commercial mobile alarm systems), has been updated. If one or more first features indicate that the system information has been updated, the wireless device can acquire the system information, such as the one or more SIBs. One or more second features of these bits may indicate that a public warning message, for example, regarding an earthquake and / or tsunami has been received.

[0372] Wireless devices can receive paging messages via the PDSCH. The PDCCH (e.g., a DCI format with a CRC scrambled by P-RNTI) may include downlink assignment (scheduling information). Wireless devices can use the downlink assignment scheduling information to receive the PDSCH.

[0373] Paging messages in PDSCH can include one or more paging requests for one or more wireless devices. For example, a wireless device not in the RRC_CONNECTED state can determine whether the paging message includes the wireless device's identifier. If the paging message includes the wireless device's identifier, the wireless device can initiate a RA procedure, such as transitioning from the non-RRC_CONNECTED state to the RRC_CONNECTED state.

[0374] A base station can configure a radio device using discontinuous reception of paging messages. A radio device receiving configuration parameters for discontinuous reception can sleep without receiver processing, for example, spending most of its time in a non-RRC_CONNECTED state. The radio device can wake up at one or more time points (e.g., with periodic paging times), for example, to determine whether the paging message includes the radio device's identifier.

[0375] A wireless device may monitor a PDCCH with a P-RNTI via one or more time slots. These one or more time slots may be referred to as paging time slots. A paging time slot may include one or more consecutive time slots. If the wireless device detects a PDCCH transmitted with a P-RNTI during a paging time slot, the wireless device may receive a paging message (e.g., a DCI in response to the PDCCH indicating the presence of a paging message on the PDSCH). If the wireless device detects a PDCCH transmitted with a P-RNTI during a paging time slot, the wireless device may not receive a paging message (e.g., a DCI in response to the PDCCH indicating the absence of a paging message on the PDSCH). If the wireless device does not detect a PDCCH transmitted with a P-RNTI during a paging time slot, the wireless device may sleep based on a paging cycle (e.g., a DRX cycle) until the next paging time slot.

[0376] A wireless device can determine paging timing based on one or more parameter values. For example, one or more parameter values ​​may include the system frame number, the wireless device's identifier, and / or (e.g., configured by the base station and / or network) paging period. The wireless device's identifier may be coupled to the wireless device's subscription information. For example, the identifier may be the wireless device's TMSI (e.g., 5G-S-TMSI). For example, the identifier may be the wireless device's recovery ID and / or C-RNTI. For example, the identifier may be an identifier previously configured in the wireless device. Different paging periods can be configured for paging initiated by the RAN and core network, such as once every 32, 64, 128, or 56 frames.

[0377] Different wireless devices can have different identifiers (e.g., 5G-S-TMSI). Different wireless devices can determine different paging instances, for example, based on different identifiers. Base stations and / or networks can transmit paging more frequently than the paging cycle configured for wireless devices (e.g., more frequently than once every 32 frames). For example, paging instances transmitted by base stations and / or networks can include paging instances from different wireless devices, such as a union of sets of paging instances from each wireless device.

[0378] Wireless devices can perform discontinuous reception (DRX) in non-RRC_CONNECTED states, for example, to reduce power consumption. The wireless device can monitor a paging opportunity (PO) in each DRX cycle. A PO can be a set of PDCCH monitoring opportunities and can include one or more time slots (e.g., subframes or OFDM symbols). The wireless device can receive paging DCIs (e.g., DCI format with CRC scrambled by P-RNTI) via one or more time slots. A paging frame (PF) can include at least one radio frame. A PF can include one or more POs and / or the start point of a PO.

[0379] In multi-beam operation, the wireless device can determine that the same paging message and the same short message are repeated in one or more transmission beams of the base station. The selection of the beam used to receive the paging message and short message can be predefined and / or can be based on configuration parameters (e.g., semi-statically configured). For RAN-initiated paging and CN-initiated paging, the paging message can be the same.

[0380] The wireless device may initiate an RRC connection procedure (e.g., an RRC connection restoration procedure) for example, after receiving a paging (e.g., a paging initiated by the RAN). The wireless device may transition (e.g., move) to RRC_IDLE for example, after receiving a paging (e.g., a paging initiated by the CN in the RRC_INACTIVE state). The wireless device may notify the NAS for example, after receiving a paging (e.g., a paging initiated by the CN in the RRC_INACTIVE state).

[0381] Wireless devices can use formulas to determine the paging PF and / or PO. These formulas can be functions of one or more paging configuration parameters, for example, configured by the base station. Exemplary formulas may be as follows: - The SFN of the PF is determined by (SFN + PF_offset) mod T = (T div N) * (UE_ID mod N). - The Index(i_s) indicating the PO is determined by i_s = floor(UE_ID / N) mod Ns.

[0382] For example, a wireless device can determine the PDCCH monitoring timing for paging based on one or more paging configuration parameters. These parameters may include pagingSearchSpace, firstPDCCH-MonitoringOccasionOfPO, and nrofPDCCH-MonitoringOccasionPerSSB-InPO.

[0383] For example, if a specific search space is configured for pagingSearchSpace (e.g., SearchSpaceId = 0 for pagingSearchSpace), the PDCCH monitoring timing for paging can be the same as the PDCCH monitoring timing for RMSI. For example, the PDCCH monitoring timing for paging can be based on the determination of the CORESET for the Type0-PDCCH CSS set and / or based on configuration parameters (e.g., the value of searchSpaceZero). For example, if a specific search space is configured for pagingSearchSpace (e.g., SearchSpaceId = 0 for pagingSearchSpace), the wireless device can monitor one or more PDCCH candidates for paging via the PDCCH monitoring timing of the CORESET (e.g., CORESET#0 of the Type0-PDCCH CSS set). When a specific search space is configured for pagingSearchSpace, Ns can be predefined as a specific value, such as 1 or 2. For example, for Ns = 1, there is a PO that can start from the first PDCCH monitoring timing for paging from the PF. For example, for Ns=2, PO can be in the first half of the frame (i_s=0) or the second half of the frame (i_s=1) of PF.

[0384] This disclosure describes the determination of the CORESET (e.g., CORESET#0) for the Type0-PDCCH CSS set. The CORESET determined based on the determination of the CORESET for the Type0-PDCCH CSS set may be referred to as CORESET#0, controlResourceSetZero, CORESET zero, default CORESET, etc. This disclosure also describes the determination of the PDCCH monitoring timing for paging based on configuration parameters (e.g., the value of searchSpaceZero). The determination of the PDCCH monitoring timing for paging may be further based on the determination of the CORESET (e.g., CORESET#0) for the Type0-PDCCH CSS set.

[0385] The pagingSearchSpace does not have to be a specific search space. For example, the search space ID of pagingSearchSpace does not have to be a specific number of specific search spaces (e.g., non-zero). For example, if no specific search space is configured for pagingSearchSpace (e.g., when a non-zero SearchSpaceId is configured for pagingSearchSpace), the wireless device can monitor the (i_s+1)th PO. A PO can be a set of one or more PDCCH monitoring moments. For example, a PO can be a set of 'S*X' consecutive PDCCH monitoring moments. For example, 'S' can be the number of SSBs actually transmitted. Configuration parameters received by the wireless device (e.g., ssb-PositionsInBurst in SIB1) can indicate the number of SSBs actually transmitted. For example, X can be a value indicated by a configuration parameter (e.g., nrofPDCCH-MonitoringOccasionPerSSB-InPO). For example, if the wireless device does not receive a configuration parameter indicating X (e.g., nrofPDCCH-MonitoringOccasionPerSSB-InPO), X can be a predefined value (e.g., 1). For example, the (x*S+K)th PDCCH monitoring timing in a PO can correspond to the SSB of the Kth transmission, where x = 0, 1, ..., X-1, and K = 1, 2, ..., S. PDCCH monitoring timings for paging that do not overlap with UL symbols (e.g., determined based on tdd-UL-DL-ConfigurationCommon) can be numbered sequentially from zero (e.g., or any other starting value), for example, starting from the first PDCCH monitoring timing in the PF. The wireless device can receive configuration parameters indicating the starting PDCCH monitoring timing number. For example, the configuration parameter may include firstPDCCH-MonitoringOccasionOfPO. For example, when the wireless device receives a message indicating the existence of firstPDCCH-MonitoringOccasionOfPO, the wireless device can determine the starting PDCCH monitoring timing number of the (i_s+1)th PO as the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter; otherwise, it can be equal to i_s*S*X. For example, if X > 1, when a wireless device detects a PDCCH transmission addressed to a P-RNTI within a PO, the wireless device may not monitor subsequent PDCCH monitoring events for that PO. A PO associated with a PF can begin within or after the PF. PDCCH monitoring events for a PO can span one or more radio frames.When no specific search space is configured for pagingSearchSpace (e.g., when a non-zero SearchSpaceId is configured for pagingSearchSpace), the PDCCH monitoring timing of the PO can span one or more time periods of the paging search space.

[0386] In this disclosure, the wireless device can determine the PF and i_s based on the following parameters: -T: DRX cycle of the wireless device -N: Total number of paging frames in T -Ns: Number of paging opportunities for the PF -PF_offset: Offset used for PF determination -UE_ID: 5G-S-TMSI mod 1024

[0387] For example, a wireless device may determine T based on one or more paging DRX values. For example, the one or more paging DRX values ​​may include, for example, wireless device-specific DRX values ​​configured by RRC and / or upper layers. For example, the one or more DRX values ​​may include DRX values ​​broadcast in system information (e.g., SIBs such as SIB1) (e.g., which may be referred to as the default DRX value). For example, a wireless device may determine T based on the shortest of one or more DRX values, which may include, for example, wireless device-specific DRX values ​​configured by RRC and / or upper layers and / or DRX values ​​broadcast in system information (e.g., the default DRX value). For example, a wireless device may use a DRX value (e.g., the default DRX value) to determine T. For example, if a wireless device-specific DRX is not configured by an upper layer, the wireless device may use a DRX value (e.g., the default DRX value) to determine T. For example, a wireless device may use a DRX value (e.g., the default DRX value) to determine T in the RRC_IDLE state. For example, a wireless device may use a DRX value (e.g., the default DRX value) to determine T. In this disclosure, the paging DRX value may be referred to as a DRX cycle or a paging cycle. For example, a DRX value broadcast in system information (e.g., a default DRX value) may be referred to as a default DRX cycle. For example, a radio device-specific DRX value configured by RRC and / or an upper layer may be referred to as a radio device-specific DRX cycle and / or a radio device-specific paging cycle.

[0388] The wireless device can receive paging configuration parameters via system information (e.g., SIB1). For example, the wireless device can receive parameters Ns, nAndPagingFrameOffset, nrofPDCCH-MonitoringOccasionPerSSB-InPO, and the length of the default DRX cycle from SIB1. The wireless device can determine the values ​​of N and PF_offset based on the parameter nAndPagingFrameOffset. The wireless device can receive the parameter first-PDCCH-MonitoringOccasionOfPO from SIB1, for example, for paging in the initial DL BWP. The wireless device can receive the parameter first-PDCCH-MonitoringOccasionOfPO from the configuration (e.g., BWP configuration) of the DL BWP (e.g., the DL BWP can be another DL BWP besides the initial DL BWP). For example, when the wireless device has not yet registered to the network, it may not have a 5G-S-TMSI. If the wireless device does not have subscription information (e.g., 5G-S-TMSI), the wireless device can use UE_ID = 0 in the above PF and i_s formulas as the default identifier. For example, 5G-S-TMSI can be a 48-bit string. For instance, in the formula above, 5G-S-TMSI can be interpreted as a binary number, where the leftmost bit represents the most significant bit. Any other information about the wireless device can be used for the UE_ID in the formula above.

[0389] Figure 23An example of the association between one or more DL RSs and one or more POs in a non-RRC_CONNECTED state according to an embodiment of this disclosure is illustrated. For example, a wireless device in a non-RRC_CONNECTED state may receive one or more DL RSs. The one or more DL RSs may be one or more SSBs, CSI-RS, etc. The wireless device may receive a message including configuration parameters of the paging search space in the non-RRC_CONNECTED state. The wireless device may determine the CORESET of the paging search space and / or the POs (e.g., one or more monitoring opportunities) of the PDCCH candidates in the paging search space. The wireless device may use one or more DL RSs to determine the CORESET of the paging search space and / or determine the POs (e.g., one or more monitoring opportunities). For example, each PO may be associated with one of the one or more DL RSs. For example, the association between a PO and one or more DL RSs may be based on configuration parameters (e.g., nrofPDCCH-MonitoringOccasionPerSSB-InPO) and / or may be predefined. The wireless device may determine one of the POs to monitor the PDCCH candidates of the paging search space. For example, the wireless device may select at least one of the one or more DL RSs. The wireless device can select one of the POs based on this association. The wireless device can receive a DCI with a CRC scrambled by P-RNTI via one of the POs. The DCI may include downlink transmission scheduling information and a PDSCH carrying a paging message. For example, the DCI may include downlink assignment of the PDSCH. The wireless device can receive the paging message based on the downlink assignment.

[0390] A wireless device may monitor one or more PDCCH monitoring times for paging message reception and / or short message reception during one or more paging times. The wireless device may receive a PDCCH in a DCI format with a CRC scrambled by P-RNTI via one or more PDCCH monitoring times. The DCI format may include a short message indicator. For example, the DCI format may include a short message. For example, the DCI format may include downlink assignment (e.g., scheduling information) for the paging message. For example, the short message indicator (e.g., a 2-bit indicator) may indicate whether the DCI format includes a short message. For example, the short message indicator may indicate whether the DCI format includes a downlink assignment for the paging message. Based on the value of the short message indicator, the wireless device may determine fields (e.g., one or more bits in the DCI format) corresponding to the short message and / or downlink assignment in the DCI format as reserved bits. For example, if the short message indicator indicates that the DCI format includes a short message, the wireless device may determine one or more first bits of the DCI format as the first field indicating a short message. For example, if the Short Message Indicator (SMI) indicates that no Short Message Service (SMS) is present in the DCI format, the wireless device may designate one or more first bits of the DCI format as reserved bits. The positions of one or more first bits in the DCI format may be predefined and / or semi-statically configured by higher-layer messages (e.g., RRC messages). For example, if the SMI indicates that the DCI format includes downlink assignment for a paging message, the wireless device may designate one or more second bits of the DCI format as a second field indicating the downlink assignment. For example, if the SMI indicates that no downlink assignment is present in the DCI format (e.g., no paging message), the wireless device may designate one or more second bits of the DCI format as reserved bits. The positions of one or more second bits in the DCI format may be predefined and / or semi-statically configured by higher-layer messages (e.g., RRC messages).

[0391] An exemplary field of the short message indicator in the DCI format may include two bits. For example, the first field value of the exemplary field (e.g., '00') may be reserved. For example, if the exemplary field is set to the second field value (e.g., exemplary field = '01'), the short message indicator may indicate the presence of a paging message in the DCI format. For example, a short message indicator with the second field value (e.g., exemplary field = '01') may indicate the absence of a short message in the DCI format. For example, if the exemplary field is set to the third field value (e.g., exemplary field = '10'), the short message indicator may indicate the absence of a paging message in the DCI format. For example, a short message indicator with the third field value (e.g., exemplary field = '10') may indicate the presence of a short message in the DCI format. For example, if the exemplary field is set to the fourth field value (e.g., exemplary field = '11'), the short message indicator may indicate the presence of a paging message in the DCI format. For example, a short message indicator with a fourth field value (e.g., example field = '11') can indicate the presence of a short message in the DCI format.

[0392] In the example, if the short message indicator indicates the presence of a downlink assignment for...

Claims

1. A method, the method comprising: The wireless device receives a Radio Resource Control (RRC) release message, which includes the following configuration parameters: Small data transmission SDT procedure for the wireless device in RRC disconnected state; as well as The downlink bandwidth portion BWP used for the SDT procedure, the downlink BWP being different from the initial downlink BWP; During the SDT procedure and in the RRC disconnected state, the physical downlink control channel (PDCCH) in the downlink BWP is monitored; When the SDT procedure is not executed and the RRC disconnected state is not in the paging timing, the PDCCH used for downlink control information (DCI) in the initial downlink BWP is monitored via paging timing; as well as The DCI is received via the paging timing.

2. The method of claim 1, wherein the RRC release message further includes one or more uplink grants for transmission via the downlink BWP in the RRC disconnected state.

3. The method of claim 1, further comprising switching from a non-initial downlink BWP to the initial downlink BWP based on determining that the DCI has been received, wherein monitoring of the PDCCH used for the DCI is a response to the switching.

4. The method of claim 3, wherein the handover is further based on the paging timing being an overlap of the duration of a transmission of the wireless device in at least one symbol and in the RRC disconnected state, the transmission being performed via one or more uplink grants in the downlink BWP.

5. The method of claim 4, further comprising: Initiate the SDT procedure including the transmission; and In response to the duration of the transmission start.

6. The method of claim 4, wherein the transmission includes an RRC recovery request.

7. The method of claim 1, wherein the DCI comprises at least one of the following: Instructions indicating the presence or absence of public warning notices; or Downlink assignment of paging messages in the initial downlink BWP.

8. The method of claim 1, wherein the wireless device is a RedCap-enabled wireless device.

9. A wireless device, comprising: One or more processors; as well as A memory storing instructions that, when executed by the one or more processors, cause the wireless device to: Receive a Radio Resource Control (RRC) release message, the RRC release message including the following configuration parameters: Small data transmission SDT procedure for the wireless device in RRC disconnected state; as well as The downlink bandwidth portion BWP used for the SDT procedure, the downlink BWP being different from the initial downlink BWP; During the SDT procedure and in the RRC disconnected state, the physical downlink control channel (PDCCH) in the downlink BWP is monitored; When the SDT procedure is not executed and the RRC disconnected state is not in the paging timing, the PDCCH used for downlink control information (DCI) in the initial downlink BWP is monitored via paging timing; as well as The DCI is received via the paging timing.

10. The wireless device of claim 9, wherein the RRC release message further includes one or more uplink grants for transmission via the downlink BWP in the RRC disconnected state.

11. The wireless device of claim 9, wherein the instruction further causes the wireless device to switch from a non-initial downlink BWP to the initial downlink BWP based on determining that the DCI has been received, wherein monitoring of the PDCCH used for the DCI is a response to the switch to the initial downlink BWP.

12. The wireless device of claim 11, wherein the handover to the initial downlink BWP is further based on the paging timing being an overlap of the duration of a transmission of the wireless device in at least one symbol and in the RRC disconnected state, the transmission being carried out via one or more uplink grants in the downlink BWP.

13. The wireless device of claim 12, wherein the instructions further cause the wireless device to: Initiating the SDT procedure including the transmission; and The duration begins in response to the start of the transmission.

14. The wireless device of claim 12, wherein the transmission includes an RRC recovery request.

15. The wireless device of claim 9, wherein the DCI comprises at least one of the following: Instructions indicating the presence or absence of public warning notices; or Downlink assignment of paging messages in the initial downlink BWP.

16. The wireless device of claim 9, wherein the wireless device is a RedCap-reduced wireless device.

17. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device, cause the wireless device to: Receive a Radio Resource Control (RRC) release message, the RRC release message including the following configuration parameters: Small data transmission SDT procedure for the wireless device in RRC disconnected state; as well as The downlink bandwidth portion BWP used for the SDT procedure, the downlink BWP being different from the initial downlink BWP; During the SDT procedure and in the RRC disconnected state, the physical downlink control channel (PDCCH) in the downlink BWP is monitored; When the SDT procedure is not executed and the RRC disconnected state is not in the paging timing, the PDCCH used for downlink control information (DCI) in the initial downlink BWP is monitored via paging timing; as well as The DCI is received via the paging timing.

18. The non-transitory computer-readable medium of claim 17, wherein the RRC release message further includes one or more uplink grants for transmission via the downlink BWP in the RRC disconnected state.

19. The non-transitory computer-readable medium of claim 17, wherein the instructions further cause the wireless device to switch from a non-initial downlink BWP to the initial downlink BWP based on determining that the DCI has been received, wherein monitoring of the PDCCH used for the DCI is a response to the switch to the initial downlink BWP.

20. The non-transitory computer-readable medium of claim 17, wherein the DCI comprises at least one of the following: Instructions indicating the presence or absence of public warning notices; or Downlink assignment of paging messages in the initial downlink BWP.

Images