Energy conservation in the spatial domain

Abstract

Configuration parameters sent to a wireless device may indicate resources (and repeating schemes that the wireless device may use for communication). An activation command to schedule a receive may indicate the use of at least two transmission configuration states for a scheduled receive. The wireless device may receive the scheduled receive using the two indicated transmission and configured repeating schemes.

Description

[Technical Field]

[0001] Cross-reference of related applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 539,138, filed on 19 September 2023. The aforementioned application is incorporated herein by reference in its entirety. [Background technology]

[0002] The wireless device communicates with the base station. The wireless device receives configuration parameters for communication via the cell. Transmission configuration indicator status parameters are used to indicate resources for transmission.

[0003] The following summary provides a simplified overview of a specific feature. It is not intended as a comprehensive overview or to identify key or important elements. [Overview of the project]

[0004] A wireless device may configure wireless communication by receiving one or more parameters from a base station. Configuration parameters may represent values ​​associated with using at least two resources (e.g., transmission configuration indicator states) for reception (e.g., physical downlink shared channel reception). Also, if the wireless device is configured to have a unified transmission configuration state framework and is configured to apply multiple resources to reception, for example, based on a transmission configuration indicator selection field in a message scheduling reception, and / or based on the absence of such a field, the wireless device may receive repetitions at reception using frequency division schemes and / or time division schemes (e.g., using non-overlapping resources and / or consecutive time slots). Additionally or alternatively, if the wireless device is configured to have a unified transmission configuration state framework and a demodulation reference signal port is indicated, the wireless device may multiplex receptions using the indicated port. If the base station switches off the transmission and reception points, and the radio device is unable to dynamically switch between resources (e.g., a unified transmission configuration indicator state) or switch to a single transmission configuration state, the radio device may stop receiving, or alternatively, continue receiving using the previously configured resources (e.g., a unified transmission configuration indicator state).

[0005] These and other features and benefits will be explained in more detail below. [Brief explanation of the drawing]

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

[0007] [Figure 1A] An exemplary communication network is shown. [Figure 1B] An exemplary communication network is shown. [Figure 2A] An exemplary user plane is shown. [Figure 2B]Shows an exemplary control plane configuration. [Figure 3] Shows an example of protocol layers. [Figure 4A] Shows an exemplary downlink data flow for a user plane configuration. [Figure 4B] Shows an exemplary format of a MAC subheader in a Medium Access Control (MAC) Protocol Data Unit (PDU). [Figure 5A] Shows an exemplary mapping of downlink channels. [Figure 5B] Shows an exemplary mapping of uplink channels. [Figure 6] Shows exemplary Radio Resource Control (RRC) states and RRC state transitions. [Figure 7] Shows an exemplary structure of a frame. [Figure 8] Shows an exemplary resource configuration of one or more carriers. [Figure 9] Shows an exemplary configuration of Bandwidth Part (BWP). [Figure 10A] Shows an exemplary carrier aggregation configuration based on component carriers. [Figure 10B] Shows an exemplary group of cells. [Figure 11A] Shows an exemplary mapping of one or more Synchronization Signal / Physical Broadcast Channel (SS / PBCH) blocks. [Figure 11B] Shows an exemplary mapping of one or more Channel State Information Reference Signals (CSI-RS). [Figure 12A] Shows an example of a downlink beam management procedure. [Figure 12B] Shows an example of an uplink beam management procedure. [Figure 13A] Shows an exemplary 4-step random access procedure. [Figure 13B] Shows an exemplary 2-step random access procedure. [Figure 13C] Shows an exemplary 2-step random access procedure. [Figure 14A]An example of a control resource set (CORESET) configuration is shown. [Figure 14B] This shows an example of a (CCE-to-REG) mapping of a control channel element to a resource element group. [Figure 15A] This shows an example of communication between a wireless device and a base station. [Figure 15B] This specification shows exemplary elements of a computing device that may be used to implement any of the various devices described herein. [Figure 16A] Examples of uplink and downlink signal transmission are shown. [Figure 16B] Examples of uplink and downlink signal transmission are shown. [Figure 16C] Examples of uplink and downlink signal transmission are shown. [Figure 16D] Examples of uplink and downlink signal transmission are shown. [Figure 17A] This flowchart shows examples of communication methods for energy conservation. [Figure 17B] This flowchart shows examples of communication methods for energy conservation. [Figure 18] This shows an example of communication for energy conservation. [Figure 19] An example of an activation command is shown below. [Figure 20A] Examples of control commands are shown below. [Figure 20B] Examples of control commands are shown below. [Figure 21] This shows an example of communication for energy conservation. [Figure 22] This shows an example of communication for energy conservation. [Figure 23] This shows an example of communication for energy conservation. [Figure 24A] This flowchart shows examples of communication methods for energy conservation. [Figure 24B] This flowchart shows examples of communication methods for energy conservation. [Figure 25A] This flowchart shows examples of communication methods for energy conservation. [Figure 25B] This flowchart shows examples of communication methods for energy conservation. [Modes for carrying out the invention]

[0008] The attached drawings and descriptions provide examples. The examples shown in the drawings and / or descriptions are non-exclusive, and it should be understood that the features illustrated and described may be practiced in other examples. Examples for the operation of wireless communication systems are provided.

[0009] Figure 1A shows an exemplary communication network 100. The communication network 100 may include a mobile communication network. The communication network 100 may include, for example, a public land mobile communication network (PLMN) operated / managed / executed by a network operator. The communication network 100 may include one or more of the following: a core network (CN) 102, a radio access network (RAN) 104, and / or a wireless device 106. The communication network 100 may include one or more data networks (DNs) 108, and / or devices within the communication network 100 may communicate with one or more data networks (DNs) 108 (e.g., via CN 102). The wireless device 106 may communicate with one or more DNs 108, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. The wireless device 106 may communicate with one or more DNs 108 via RAN 104 and / or CN 102. CN102 may provide / configure the wireless device 106 with one or more interfaces to one or more DN108s. As part of its interface functionality, CN102 may set up an end-to-end connection between the wireless device 106 and one or more DN108s, authenticate the wireless device 106, and provide / configure charging functionality.

[0010] The wireless device 106 may communicate with RAN 104 via wireless communication over an air interface. RAN 104 may communicate with CN 102 via various communications (e.g., wired communications and / or wireless communications). The wireless device 106 may establish a connection with CN 102 via RAN 104. RAN 104 may, for example, provide / configure scheduling, wireless resource management, and / or retransmission protocols as part of wireless communication. The communication direction from RAN 104 to the wireless device 106 across / over the air interface may be called the downlink and / or downlink communication direction. The communication direction from the wireless device 106 to RAN 104 across / over the air interface may be called the uplink and / or uplink communication direction. Downlink transmission may be separated and / or distinguished from uplink transmission based on, for example, frequency division duplication (FDD), time division duplication (TDD), any other duplication scheme, and / or at least one of a combination thereof.

[0011] When used as a whole, the term “wireless device” may include one or more of the following: mobile devices, fixed (e.g., non-mobile) devices on which wireless communication is configured or enabled, computing devices, nodes, wirelessly radioactive devices, or any other devices capable of transmitting and / or receiving signals. In non-limiting examples, wireless devices may include, for example, telephones, mobile phones, Wi-Fi phones, smartphones, tablets, computers, laptops, sensors, meters, wearable devices, Internet of Things (IoT) devices, hotspots, cellular repeaters, vehicle roadside units (RSUs), relay nodes, automobiles, wireless user devices (e.g., user equipment (UE), user terminals (UT), etc.), access terminals (AT), mobile stations, handsets, wireless transmission and receiving units (WTRUs), wireless communication devices, and / or any combination thereof.

[0012] RAN104 may include one or more base stations (not shown). As used throughout, the term “base station” may include one or more of the following: base station, node, node B (NB), evolutionary node B (eNB), gNB, ng-eNB, relay node (e.g., integrated access and backhaul (IAB) node), donor node (e.g., donor eNB, donor gNB, etc.), access point (e.g., Wi-Fi access point), transmission and reception point (TRP), computing device, wireless communication capable device, or any other device capable of transmitting and / or receiving signals. A base station may include one or more of each of the elements listed above. For example, a base station may include one or more TRPs. Other non-limiting examples include, for example, a base station may include one or more of the following: Node B (e.g., associated with Universal Mobile Communications System (UMTS) and / or 3G standards), Evolutionary Node B (eNB) (e.g., associated with Evolutionary Universal Terrestrial Radio Access (E-UTRA) and / or 4G standards), Remote Radio Heads (RRHs), Baseband Processing Units coupled to one or more Remote Radio Heads (RRHs), Repeater Nodes or Transit Nodes used to extend the coverage area of ​​a donor node, Next Generation Evolutionary Node B (ng-eNB), Generation Node B (gNB) (e.g., associated with NR and / or 5G standards), Access Points (APs) (e.g., associated with Wi-Fi or any other suitable wireless communication standard), base stations of any other generation, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central device (e.g., a gNB central unit (gNB-CU)) and at least one base station distributed device (e.g., a gNB distributed unit (gNB-DU)).

[0013] A base station (e.g., within RAN 104) may include one or more sets of antennas for communicating wirelessly (e.g., via an over-the-air interface) with a radio device 106. One or more base stations may include sets of antennas (e.g., three sets or sets of any other quantities) for controlling multiple cells or sectors (e.g., three cells, three sectors, any other quantity of cells, or any other quantity of sectors), respectively. The size of a cell may be determined by the range over which a receiver (e.g., a base station receiver) can successfully receive transmissions from transmitters (e.g., radio device transmitters) operating within the cell. One or more cells of a base station (e.g., individually or in combination with other cells) may provide / configure radio coverage to the radio device 106 over a wide geographical area to support radio device mobility. A base station containing three sectors (e.g., or n sectors, where n refers to any quantity n) may be called a three-sector site (e.g., or an n-sector site) or a three-sector base station (e.g., an n-sector base station).

[0014] One or more base stations (e.g., in RAN104) may be implemented as sector sites having more or fewer than three sectors. One or more base stations in RAN104 may be implemented as access points, as baseband processing devices / units coupled to multiple RRHs, and / or as repeaters or relay nodes used to extend the coverage area of ​​a node (e.g., a donor node). Baseband processing devices / units coupled to RRHs may be part of a centralized or cloud RAN architecture, for example, the baseband processing devices / units may be centralized within a pool of baseband processing devices / units, or they may be virtualized. Repeater nodes may amplify and transmit (e.g., transmission, retransmission, rebroadcast, etc.) radio signals received from donor nodes. Relay nodes may perform substantially the same / similar functions as repeater nodes. Relay nodes may decode radio signals received from donor nodes to remove noise before amplifying and transmitting the radio signals.

[0015] RAN104 can be deployed as a homogeneous network of base stations (e.g., macrocell base stations) having similar antenna patterns and / or similar high-level transmission power. RAN104 can also be deployed as a heterogeneous network of base stations (e.g., different base stations with different antenna patterns). In a heterogeneous network, small cell base stations can be used to provide / configure small coverage areas, e.g., coverage areas that overlap with relatively large coverage areas provided / configured by other base stations (e.g., macrocell base stations). Small coverage areas can be provided / configured in areas of high data traffic (or so-called "hotspots") or areas with weak macrocell coverage. Examples of small cell base stations, in order of decreasing coverage area, may include microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0016] The examples described herein may be used in various types of communications. For example, the communications may be from the Third Generation Partnership Project (3GPP) (e.g., one or more network elements similar to those of communications network 100), from the Institute of Electrical and Electronics Engineers (IEEE), from the International Telecommunication Union (ITU), from the International Organization for Standardization (ISO), etc. 3GPP has produced specifications for multiple generations of mobile networks, including 3G networks known as UMTS, 4G networks known as Long-Term Evolution (LTE) and LTE Advanced (LTE-A), and 5G networks known as 5G systems (5GS) and NR systems. 3GPP may produce specifications for additional generations of communications networks (e.g., 6G and / or any other generations of communications networks). Examples may be described by referring to one or more elements (e.g., RAN) of a 3GPP 5G network called Next Generation RAN (NG-RAN), or to any other communications networks such as 3GPP networks and / or non-3GPP networks. The examples described herein may apply to other communication networks such as 3G and / or 4G networks, as well as communication networks that have not yet been finalized / documented (e.g., 3GPP 6G networks), satellite communication networks, and / or any other communication networks. NG-RAN may be provided to implement and update 5G radio access technology, known as NR, and to implement 4G radio access technology, as well as other radio access technologies such as other 3GPP and / or non-3GPP radio access technologies.

[0017] Figure 1B shows an exemplary communication network 150. The communication network may include a mobile communication network. The communication network 150 may include, for example, a PLMN operated / managed / executed by a network operator. The communication network 150 may include one or more of the following: CN 152 (e.g., a 5G core network (5G-CN)), RAN 154 (e.g., an NG-RAN), and / or radio devices 156A and 156B (collectively, radio device 156). The communication network 150 may include one or more data networks (DNs) 170, and / or devices within the communication network 150 may communicate with one or more data networks (DNs) 170 (e.g., via CN 152). These components may be implemented and operated in substantially the same or similar manner as the corresponding components described with respect to Figure 1A.

[0018] CN152 (e.g., 5G-CN) may provide / configure a radio device 156 to one or more interfaces to one or more DNs 170, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of its interface functionality, CN152 (e.g., 5G-CN) may set up an end-to-end connection between the radio device 156 and one or more DNs, authenticate the radio device 156, and / or provide / configure charging functionality. CN152 (e.g., 5G-CN) may be a service-based architecture that differs from other CNs (e.g., 3GPP 4G CN). The node architecture of CN152 (e.g., 5G-CN) may be defined as a network function that provides services via interfaces to other network functions. The network functionality of CN152 (e.g., 5G CN) can be implemented in several ways, for example, as a network element on dedicated or shared hardware, as a software instance running on dedicated or shared hardware, and / or as a virtualized function instantiated on a platform (e.g., a cloud-based platform).

[0019] CN152 (e.g., 5G-CN) may include an Access and Mobility Management Function (AMF) device 158A and / or a User Plane Function (UPF) device 158B, which may be separate components or a single component AMF / UPF device 158. The UPF device 158B may function as a gateway between RAN154 (e.g., NG-RAN) and one or more DN170s. The UPF device 158B may perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic usage reporting, uplink classification supporting routing of traffic flows to one or more DN170s, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and / or downlink data notification triggers. UPF device 158B may support multi-homed PDU sessions by functioning as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branch point. Radio device 156 may be configured to receive services via PDU sessions, which may be logical connections between the radio device and the DN.

[0020] The AMF device 158A may perform functions such as termination of non-access layer (NAS) signaling, NAS signaling security, access layer (AS) security management, inter-CN node signaling for mobility between access networks (e.g., 3GPP access networks and / or non-3GPP networks), reachability of idle-mode wireless devices (e.g., idle-mode UE reachability for control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, roaming right verification, access grants including mobility management controls (e.g., subscriptions and policies), network slicing support, and / or selection of session management functions (SMF). NAS may refer to functions operating between CN and wireless devices, and AS may refer to functions operating between wireless devices and RAN.

[0021] CN152 (e.g., 5G-CN) may include one or more additional network functions not shown in Figure 1B. CN152 (e.g., 5G-CN) may include one or more devices implementing at least one of the following functions: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Exposure Function (NEF), Unified Data Management (UDM), Application Function (AF), Authentication Server Function (AUSF), and / or any other functions.

[0022] RAN154 (e.g., NG-RAN) may communicate with radio device 156 via radio communication (e.g., via an air interface). Radio device 156 may communicate with CN152 via RAN154. RAN154 (e.g., NG-RAN) may include one or more base stations of a first type (e.g., gNB160A and gNB160B (collectively gNB160)) and / or one or more base stations of a second type (e.g., ng-eNB162A and ng-eNB162B (collectively ng eNB162)). RAN154 may include one or more of any number of base station types. gNB160 and ng eNB162 may be called base stations. A base station (e.g., gNB160 and ng eNB162) may include one or more sets of antennas for radio communication (e.g., via an air interface) with radio device 156. One or more base stations (e.g., gNB160 and / or ng-eNB162) may include multiple antenna sets for controlling multiple cells (or sectors), each of which may include multiple antenna sets. The cells of the base stations (e.g., gNB160 and ng-eNB162) may provide radio coverage to radio devices 156 over a wide geographical area to support radio device mobility.

[0023] A base station (e.g., gNB160 and / or ng-eNB162) may be connected to CN152 (e.g., 5G CN) via a first interface (e.g., NG interface) and to other base stations via a second interface (e.g., Xn interface). The NG and Xn interfaces may be established on an underlying transport network, such as an Internet Protocol (IP) transport network, using direct physical and / or indirect connections. A base station (e.g., gNB160 and / or ng-eNB162) may communicate with a radio device 156 via a third interface (e.g., Uu interface). A base station (e.g., gNB160A) may communicate with a radio device 156A via the Uu interface. The NG, Xn, and Uu interfaces may be associated with a protocol stack. The protocol stack associated with the interfaces may be used by the network elements shown in Figure 1B to exchange data and signaling messages. The protocol stack may include two planes, namely the user plane and the control plane. Any other amount of planes may be used (e.g., within the protocol stack). The user plane may process data of interest to the user. The control plane may process signaling messages of interest to network elements.

[0024] One or more base stations (e.g., gNB160 and / or ng-eNB162) may communicate with one or more AMF / UPF devices, such as AMF / UPF158, via one or more interfaces (e.g., NG interfaces). A base station (e.g., gNB160A) may communicate with and / or connect to the UPF158B of the AMF / UPF158 via the NG user plane (NG-U) interface. The NG-U interface may provide / implement the delivery (e.g., unguaranteed delivery) of user plane PDUs between the base station (e.g., gNB160A) and the UPF device (e.g., UPF158B). A base station (e.g., gNB160A) may communicate with and / or connect to an AMF device (e.g., AMF158A) via the NG control plane (NG-C) interface. The NG-C interface may provide / implement, for example, NG interface management, wireless device context management (e.g., UE context management), wireless device mobility management (e.g., UE mobility management), NAS message transport, paging, PDU session management, configuration transfer, and / or alert message transmission.

[0025] A radio device may access a base station via an interface (e.g., a Uu interface) for user plane and control plane configurations. A base station (e.g., gNB160) may provide user plane and control plane protocol terminations to radio device 156 via a Uu interface. A base station (e.g., gNB160A) may provide user plane and control plane protocol terminations to radio device 156A on a Uu interface associated with a first protocol stack. A base station (e.g., ng-eNB162) may provide Evolutionary UMTS Terrestrial Radio Access (E UTRA) user plane and control plane protocol terminations to radio device 156 via a Uu interface (e.g., E UTRA may refer to 3GPP 4G radio access technology). A base station (e.g., ng-eNB162B) may provide E UTRA user plane and control plane protocol terminations to radio device 156B via a Uu interface associated with a second protocol stack. User plane and control plane protocol terminations may include, for example, NR user plane and control plane protocol terminations, 4G user plane and control plane protocol terminations, and so on.

[0026] A CN152 (e.g., 5G-CN) may be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). An NR network / device (or any first network / device) may also be able to connect to a 4G core network / device (or any second network / device) in non-standalone mode (e.g., non-standalone operation). In non-standalone mode / operation, the 4G core network may be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although only one AMF / UPF158 is shown in Figure 1B, one or more base stations (e.g., one or more gNBs and / or one or more ng-eNBs) may be connected to multiple AMF / UPF nodes, for example, to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0027] Interfaces between network elements (e.g., network elements shown in Figure 1B) (e.g., Uu, Xn, and / or NG interfaces) may be associated with a protocol stack that network elements can use to exchange data and signaling messages. The protocol stack may include two planes: a user plane and a control plane. Any other number of planes may be used (e.g., within the protocol stack). The user plane may process data associated with a user (e.g., data of interest to the user). The control plane may process data associated with one or more network elements (e.g., signaling messages of interest to the network elements).

[0028] The communication network 100 in Figure 1A and / or the communication network 150 in Figure 1B may include any quantity / number and / or type of devices, such as computing devices, wireless devices, mobile devices, handsets, tablets, laptops, Internet of Things (IoT) devices, hotspots, cellular repeaters, computing devices, and / or more generally, user equipment (e.g., UEs). One or more of the above-mentioned types of devices may be referenced herein (e.g., UEs, wireless devices, computing devices, etc.), but it should be understood that any device herein may include any one or more of the above-mentioned types of devices or similar devices. The communication network, and any other network referenced herein, may include LTE networks, 5G networks, satellite networks, and / or any other networks for wireless communication (e.g., any 3GPP network and / or any non-3GPP network). The apparatus, systems, and / or methods described herein may generally be described as being implemented in one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks, but it will be understood that one or more features and steps may be implemented in any device and / or any network.

[0029] Figure 2A shows an exemplary user plane configuration. The user plane configuration may include, for example, an NR user plane protocol stack. Figure 2B shows an exemplary control plane configuration. The control plane configuration may include, for example, an NR control plane protocol stack. One or more of the user plane configurations and / or control plane configurations may use a possible Uu interface between the radio device 210 and the base station 220. The protocol stacks shown in Figures 2A and 2B may be substantially the same as or similar to those used for the Uu interface between the radio device 156A and the base station 160A shown in Figure 1B.

[0030] The user plane configuration (e.g., the NR user plane protocol stack) may include multiple layers (e.g., five layers or any other number of layers) implemented in the radio device 210 and base station 220 (e.g., as shown in Figure 2A). At the bottom of the protocol stack, the physical layers (PHYs) 211 and 221 may provide transport services to the upper layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The protocol layers above PHY 211 may include the Medium Access Control Layer (MAC) 212, the Radio Link Control Layer (RLC) 213, the Packet Data Convergence Protocol Layer (PDCP) 214, and / or the Service Data Application Protocol Layer (SDAP) 215. The protocol layers above PHY 221 may include the Medium Access Control Layer (MAC) 222, the Radio Link Control Layer (RLC) 223, the Packet Data Convergence Protocol Layer (PDCP) 224, and / or the Service Data Application Protocol Layer (SDAP) 225. One or more of the four protocol layers on PHY211 may correspond to layer 2 or the data link layer of the OSI model. One or more of the four protocol layers on PHY221 may correspond to layer 2 or the data link layer of the OSI model.

[0031] Figure 3 shows an example of a protocol layer. The protocol layer may include, for example, the protocol layer of the NR user plane protocol stack. One or more services may be provided between the protocol layers. SDAP (e.g., SDAP215 and 225 shown in Figures 2A and 3) may perform quality of service (QoS) flow processing. Radio devices (e.g., radio devices 106, 156A, 156B, and 210) may receive services through / via a PDU session, which may be a logical connection between the radio device and the DN. A PDU session may have one or more QoS flows 310. The CN's UPF (e.g., UPF158B) may map IP packets to one or more QoS flows of the PDU session based on, for example, one or more QoS requirements (e.g., delay, data rate, error rate, and / or any other quality / service requirements). SDAP215 and 225 may perform mapping / unmapping between one or more QoS flows 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / demapping between one or more QoS flows 310 and radio bearers 320 may be determined by the SDAP 225 of the base station 220. The SDAP 215 of the radio device 210 may be informed of the mapping between QoS flows 310 and radio bearers 320 via reflected mapping and / or control signaling received from the base station 220. For reflected mapping, the SDAP 225 of the base station 220 may determine the mapping / demapping between one or more QoS flows 310 and radio bearers 320 by marking downlink packets with QoS flow indicators (QFIs) that can be monitored / detected / identified / indicated / observed by the SDAP 215 of the radio device 210.

[0032] PDCPs (e.g., PDCPs 214 and 224 shown in Figures 2A and 3) may perform, for example, header compression / decompression to reduce the amount of data that may need to be transmitted (e.g., sent) over the air interface, encryption / decryption to prevent unauthorized decoding of data transmitted (e.g., sent) over the air interface, and / or integrity protection (e.g., to ensure that control messages originate from the intended source). PDCPs 214 and 224 may perform, for example, retransmission of undelivered packets, continuous delivery and rearrangement of packets, and / or removal of duplicate packets, due to handover (e.g., handover within a gNB). PDCPs 214 and 224 may perform packet duplication to improve the likelihood of receiving packets. Receivers may receive duplicate packets and can remove any duplicate packets. Packet duplication may be useful for certain services, such as services requiring high reliability.

[0033] The PDCP layer (e.g., PDCP214 and 224) may perform mapping / demapping between segmented radio bearers and RLC channels (e.g., RLC channel 330) (e.g., in dual-connectivity scenarios / configurations). Dual-connectivity may refer to a technique that enables a radio device to communicate with multiple cells (e.g., two cells), or more broadly, multiple cell groups, including a master cell group (MCG) and secondary cell groups (SCG). Segmented bearers may be configured and / or used, for example, when a single radio bearer (e.g., one of the radio bearers provided / configured by PDCP214 and 224 as a service to SDAP215 and 225) is handled by a cell group in a dual-connectivity scenario. PDCP214 and 224 may map / demap segmented radio bearers to RLC channels 330 belonging to the cell group.

[0034] The RLC layer (e.g., RLC213 and 223) may perform segmentation, retransmission via automatic repeating requests (ARQ), and / or removal of duplicate data units received from the MAC layer (e.g., MAC212 and 222, respectively). The RLC layer (e.g., RLC213 and 223) may support multiple transmission modes (e.g., three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM)). The RLC layer may perform one or more of the above functions, for example, based on the transmission mode in which the RLC layer is operating. The RLC configuration may be per logical channel. The RLC configuration may not depend on the duration (or other duration) of the numerology and / or the transmission time interval (TTI). The RLC layer (e.g., RLC213 and 223) may provide / configure RLC channels as a service to the PDCP layer (e.g., PDCP214 and 224, respectively), as shown in Figure 3.

[0035] The MAC layer (e.g., MAC212 and 222) may perform logical channel multiplexing / demultiplexing and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing of data units / data portions belonging to one or more logical channels to / from transport blocks (TBs) delivered to / from the PHY layer (e.g., PHY211 and 221, respectively). The MAC layer of a base station (e.g., MAC222) may be configured to perform scheduling between radio devices, scheduling information reporting, and / or priority processing via dynamic scheduling. Scheduling may be performed by the base station (e.g., base station 220 of MAC222) for downlink / or and uplink. The MAC layer (e.g., MAC212 and 222) may be configured to perform error correction via hybrid automatic retransmission requests (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority processing between logical channels of radio device 210, and / or padding via logical channel prioritization. The MAC layer (e.g., MAC212 and 222) may support one or more numerologies and / or transmission timings. Mapping restrictions in logical channel prioritization may control which numerologies and / or transmission timings a logical channel may use. The MAC layer (e.g., MAC212 and 222) may, as a service, provide / configure logical channels 340 to the RLC layer (e.g., RLC213 and 223).

[0036] The PHY layer (e.g., PHY211 and 221) may perform mapping of transport channels to physical channels and / or digital and analog signal processing functions for transmitting and / or receiving information (e.g., via an air interface). Digital and / or analog signal processing functions may include, for example, coding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHY211 and 221) may perform multi-antenna mapping. The PHY layer (e.g., PHY211 and 221) may provide / configure one or more transport channels (e.g., transport channel 350) as a service to the MAC layer (e.g., MAC212 and 222, respectively).

[0037] Figure 4A shows an exemplary downlink data flow for a user plane configuration. A user plane configuration may include, for example, the NR user plane protocol stack shown in Figure 2A. One or more TBs may be generated based on, for example, the data flow through the user plane protocol stack. As shown in Figure 4A, a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack may generate two TBs (e.g., base station 220). An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow shown in Figure 4A. Three IP packets (n, n+1, and m) may be determined from two TBs based on, for example, the uplink data flow through the NR user plane protocol stack. A first quantity of packets (e.g., three or any other quantity) may be determined from a second quantity of TBs (e.g., two or another quantity).

[0038] A downlink data flow may be initiated, for example, when SDAP225 receives three IP packets (or other amounts of IP packets) from one or more QoS flows and maps the three packets (or other amounts of packets) to radio bearers (e.g., radio bearers 402 and 404). SDAP225 may map IP packets n and n+1 to the first radio bearer 402 and IP packet m to the second radio bearer 404. An SDAP header (labeled with "H" before each SDAP SDU shown in Figure 4A) may be added to the IP packets to generate an SDAP PDU, which may be called a PDCP SDU. Data units transferred to and from higher protocol layers may be called service data units (SDUs) at lower protocol layers, and data units transferred to and from lower protocol layers may be called protocol data units (PDUs) at higher protocol layers. As shown in Figure 4A, the data unit from SDAP225 can be an SDU of the lower protocol layer PDCP224 (e.g., a PDCP SDU) or a PDU of SDAP225 (e.g., an SDAP PDU).

[0039] Each protocol layer (e.g., the protocol layer as shown in Figure 4A), or at least some protocol layers, may perform its own function (e.g., one or more functions of each protocol layer as described with respect to Figure 3), add the corresponding header, and / or forward its respective output to the next lower layer (e.g., the layer below it). PDCP224 may perform IP header compression and / or encryption. PDCP224 may forward its output (e.g., a PDCP PDU which is an RLC SDU) to RLC223. RLC223 may optionally perform segmentation (e.g., as shown for the IP packet in Figure 4A). RLC223 may forward its output (e.g., two RLC PDUs which are two MAC SDUs generated by adding their respective subheaders to two SDU segments (SDU Segs)) to MAC222. MAC222 may multiplex the quantity / number of RLC PDUs (MAC SDUs). MAC222 can form a TB by attaching a MAC subheader to the RLC PDU (MAC SDU). The MAC subheader can be distributed across the MAC PDU (e.g., in an NR configuration, as shown in Figure 4A). The MAC subheader can be located entirely at the beginning of the MAC PDU (e.g., in an LTE configuration). The NR MAC PDU structure can reduce processing time and / or associated delays, for example, if the MAC PDU subheader is computed before assembling the complete MAC PDU.

[0040] Figure 4B shows an exemplary format of a MAC subheader in a MAC PDU. A MAC PDU may include a MAC subheader (H) and a MAC SDU. Each of the one or more MAC subheaders may include an SDU length field to indicate the length (e.g., bytes) of the MAC SDU to which the MAC subheader corresponds, a logical channel identifier (LCID) field to identify / indicate the logical channel initiated by the MAC SDU to assist in the multiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0041] One or more MAC control elements (CEs) may be added to or inserted into a MAC PDU by a MAC layer such as MAC223 or MAC222. As shown in Figure 4B, two MAC CEs may be inserted / added before two MAC PDUs. MAC CEs may be inserted / added at the beginning of a MAC PDU for downlink transmission (as shown in Figure 4B). One or more MAC CEs may be inserted / added at the end of a MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Examples of MAC CEs include scheduling-related MAC CEs such as buffer status reports and power headroom reports, activation / deactivation MAC CEs (e.g., activation / deactivation of PDCP duplicate detection, channel status information (CSI) reports, sounding reference signal (SRS) transmission, and MAC CEs for pre-configured components), discontinuous receive (DRX)-related MAC CEs, timing advance MAC CEs, and random access-related MAC CEs. A MAC CE may be preceded by a MAC subheader in a format similar to that described for the MAC subheader for the MAC SDU, and may be identified by a reserved value in the LCID field indicating the type of control information contained in the corresponding MAC CE.

[0042] Figure 5A shows an exemplary mapping of downlink channels. Uplink channel mapping may include mappings between downlink channels (e.g., logical channels, transport channels, and physical channels). Figure 5B shows an exemplary mapping of uplink channels. Uplink channel mapping may include mappings between uplink channels (e.g., logical channels, transport channels, and physical channels). Information may be passed through / via channels between the RLC, MAC, and PHY layers of the protocol stack (e.g., the NR protocol stack). Logical channels may be used between the RLC layer and the MAC layer. Logical channels may be classified / represented as control channels that can carry control and / or configuration information (e.g., within the NR control plane) or as traffic channels that can carry data (e.g., within the NR user plane). Logical channels may be classified / represented as dedicated logical channels that may be exclusive to a particular radio device and / or as common logical channels that may be used by one or more radio devices (e.g., a group of radio devices).

[0043] A logical channel can be defined by the type of information it carries. A set of logical channels (for example, in an NR configuration) may include one or more channels as described below: A paging control channel (PCCH) may contain / carry one or more paging messages used for paging wireless devices whose location is unknown to the network at the cell level. A broadcast control channel (BCCH) may contain / carry system information messages in the form of master information blocks (MIBs) and several system information blocks (SIBs). System information messages may be used by wireless devices to obtain information about how a cell is configured and how it operates within the cell. A common control channel (CCCH) may contain / carry control messages along with random access. A dedicated control channel (DCCH) may contain / carry control messages to / from a specific wireless device and configure the wireless device with configuration information. A dedicated traffic channel (DTCH) may contain / carry user data to / from a specific wireless device.

[0044] Transport channels may be used between the MAC layer and the PHY layer. Transport channels may be defined by how the information they carry is transmitted / transmitted (e.g., via an air interface). A set of transport channels (e.g., defined by an NR configuration or any other configuration) may include one or more of the following channels: Paging Channel (PCH) may include / carry paging messages originating from the PCCH. Broadcast Channel (BCH) may include / carry MIBs from the BCCH. Downlink Shared Channel (DL-SCH) may include / carry downlink data and signaling messages, including SIBs from the BCCH. Uplink Shared Channel (UL-SCH) may include / carry uplink data and signaling messages. Random Access Channel (RACH) may provide wireless devices with access to the network without any prior scheduling.

[0045] The PHY layer may use physical channels to pass / transfer information between processing levels of the PHY layer. A physical channel may have an associated set of time-frequency resources for carrying information from one or more transport channels. The PHY layer may generate control information to support the lower-level operation of the PHY layer. The PHY layer may provide / transfer control information to lower levels of the PHY layer via physical control channels (e.g., called L1 / L2 control channels). The set of physical channels and physical control channels (e.g., which may be defined by an NR configuration or any other configuration) may include one or more of the following channels: A physical broadcast channel (PBCH) may contain / carry MIBs from a BCH. A physical downlink shared channel (PDSCH) may contain / carry downlink data and signaling messages from a DL-SCH, as well as paging messages from a PCH. A physical downlink control channel (PDCCH) may contain / carry downlink control information (DCI), which may contain downlink scheduling commands, uplink scheduling grants, and uplink power control commands. The Physical Uplink Shared Channel (PUSCH) may contain / carry uplink data and signaling messages from the UL-SCH, and in some cases uplink control information (UCI), as described below. The Physical Uplink Control Channel (PUCCH) may contain / carry UCI, including HARQ acknowledgments, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR). The Physical Random Access Channel (PRACH) may be used for random access.

[0046] The physical layer may generate physical signals to support the low-level operation of the physical layer, which may be analogous to a physical control channel. As shown in Figures 5A and 5B, the physical layer signals (which may be defined, for example, by an NR configuration or any other configuration) may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DM-RS), a sounding reference signal (SRS), a phase tracking reference signal (PT-RS), and / or any other signals.

[0047] One or more channels (e.g., logical channels, transport channels, physical channels, etc.) can be used to perform functions associated with the control plan protocol stack (e.g., the NR control plane protocol stack). Figure 2B shows an exemplary control plane configuration (e.g., the NR control plane protocol stack). In Figure 2B, the control plane configuration (e.g., the NR control plane protocol stack) may use one or more substantially identical / similar protocol layers (e.g., PHY211 and 221, MAC212 and 222, RLC213 and 223, and PDCP214 and 224) as an exemplary user plane configuration (e.g., the NR user plane protocol stack). Four similar protocol layers may include PHY211 and 221, MAC212 and 222, RLC213 and 223, and PDCP214 and 224. The control plane configuration (e.g., NR control plane stack) may have, for example, the Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the control plane configuration (e.g., NR control plane protocol stack), instead of having SDAP 215 and 225. The control plane configuration may also include the AMF 230, which includes the NAS protocol 237.

[0048] NAS protocols 217 and 237 may provide control plane functions between the wireless device 210 and the AMF 230 (e.g., AMF158A or any other AMF) and / or more generally between the wireless device 210 and the CN (e.g., CN152 or any other CN). NAS protocols 217 and 237 may provide control plane functions between the wireless device 210 and the AMF 230 via signaling messages called NAS messages. There may or may not be a direct path through which NAS messages can be transported between the wireless device 210 and the AMF 230. NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, session management, and / or any other functions.

[0049] RRC layers 216 and 226 may provide / configure control plane functionality between the radio device 210 and the base station 220 and / or more generally between the radio device 210 and the RAN (e.g., base station 220). RRC layers 216 and 226 may provide / configure control plane functionality between the radio device 210 and the base station 220 via signaling messages, which may be called RRC messages. RRC messages may be transmitted between the radio device 210 and the RAN (e.g., base station 220) using a signaling radio bearer and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC layer may multiplex control plane and user plane data into the same TB. RRC layers 216 and 226 may provide / configure control plane functions such as broadcasting system information related to the AS and NAS, paging initiated by the CN or RAN, establishing, maintaining, and releasing RRC connections between the radio device 210 and the RAN (e.g., base station 220), security functions including key management, establishing, configuring, maintaining, and releasing signaling radio bearers and data radio bearers, mobility functions, QoS management functions, radio device measurement reports (e.g., radio device measurement reports) and control of reports, detection and recovery from radio link failures (RLFs), and / or functions for forwarding NAS messages. As part of establishing an RRC connection, RRC layers 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the radio device 210 and the RAN (e.g., base station 220).

[0050] Figure 6 shows exemplary RRC states and RRC state transitions. The RRC state of a wireless device can be changed to another RRC state (e.g., an RRC state transition for the wireless device). A wireless device may be substantially identical or similar to wireless devices 106, 210, or any other wireless device. A wireless device may be in at least one of several states, such as three RRC states including RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRC inactive 604 (e.g., RRC_INACTIVE). RRC inactive 604 may be RRC connected but inactive.

[0051] An RRC connection may be established for a radio device. For example, this may occur during an RRC connection state. During an RRC connection state (e.g., during RRC connection 602), the radio device may have an established RRC context and may have at least one RRC connection with a base station. The base station may be one of several base stations (e.g., one or more base stations of RAN104 shown in Figure 1A, one of gNB160 or ng-eNB162 shown in Figure 1B, base station 220 shown in Figures 2A and 2B, or any other base station). The base station to which the radio device is connected (e.g., which has established an RRC connection) may have an RRC context for the radio device. The RRC context, which may be called the radio device context (e.g., UE context), may contain parameters for communication between the radio device and the base station. These parameters may include, for example, one or more of the following: AS context, radio link configuration parameters, bearer configuration information (e.g., related to data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session), security information, and / or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information). During an RRC connection state (e.g., RRC connection 602), the mobility of the radio device may be managed / controlled by the RAN (e.g., RAN104 or NG RAN154). The radio device may measure received signal levels (e.g., reference signal level, reference signal received power, reference signal received quality, received signal strength indicator, etc.) based on one or more signals transmitted from the serving cell and adjacent cells. The radio device may report these measurements to the serving base station (e.g., the base station currently providing service to the radio device). The serving base station of the radio device may, for example, request a handover to one of the adjacent base stations' cells based on the reported measurements. The RRC state may transition from an RRC connected state (e.g., RRC connected 602) to an RRC idle state (e.g., RRC idle 606) via the connection release procedure 608.The RRC state may transition from an RRC connected state (e.g., RRC connected 602) to an RRC inactive state (e.g., RRC inactive 604) via the connection deactivation procedure 610.

[0052] An RRC context cannot be established for a radio device. For example, this may be during an RRC idle state. During an RRC idle state (e.g., RRC idle 606), an RRC context cannot be established for a radio device. During an RRC idle state (e.g., RRC idle 606), a radio device cannot have an RRC connection with a base station. During an RRC idle state (e.g., RRC idle 606), a radio device may be in a sleep state (e.g., to conserve battery power) for most of the time. A radio device may wake up periodically (e.g., once per discontinuous receive (DRX) cycle) to monitor paging messages (e.g., paging messages set from RAN). The mobility of a radio device may be managed by the radio device through a cell reselection procedure. The RRC state may transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602) via a connection establishment procedure 612 which may involve a random access procedure.

[0053] A previously established RRC context may be maintained for a radio device. For example, this may be during an RRC inactive state. During an RRC inactive state (e.g., RRC inactive 604), a previously established RRC context may be maintained within the radio device and the base station. Maintaining the RRC context may enable a fast transition to an RRC connected state (e.g., RRC connected 602) with less signaling overhead compared to the transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602). During an RRC inactive state (e.g., RRC inactive 604), the radio device may be in a sleep state, and the mobility of the radio device may be managed / controlled by the radio device via cell reselection. The RRC state may transition from an RRC inactive state (e.g., RRC inactive 604) to an RRC connected state (e.g., RRC connected 602) via a connection restart procedure 614. The RRC state may transition from an RRC inactive state (e.g., RRC inactive 604) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 616, which may be identical or similar to the connection release procedure 608.

[0054] RRC states can be associated with mobility management mechanisms. During RRC idle states (e.g., RRC idle 606) and RRC inactive states (e.g., RRC inactive 604), mobility can be managed / controlled by radio devices via cell reselection. The purpose of mobility management during RRC idle states (e.g., RRC idle 606) or RRC inactive states (e.g., RRC inactive 604) may be to enable / enable the network to notify radio devices of events via paging messages without having to broadcast paging messages across the entire mobile communications network. Mobility management mechanisms used during RRC idle states (e.g., RRC idle 606) or RRC inactive states (e.g., RRC inactive 604) may enable / enable the network to track radio devices at the cell group level so that paging messages can be broadcast across cells in the cell group in which the radio device is currently located (e.g., rather than sending paging messages across the entire mobile communications network). The mobility management mechanism in the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive 604) may track wireless devices at the cell group level. The mobility management mechanism may perform tracking using, for example, different levels of grouping. There may be multiple levels of cell grouping granularity (e.g., three levels of cell grouping granularity: individual cells, cells within a RAN area identified by a RAN area identifier (RAI), and cells within a group of RAN areas identified by a tracking area identifier (TAI), called a tracking area).

[0055] A tracking area can be used to track a radio device (e.g., to track the location of a radio device at the CN level). A CN (e.g., CN102, 5G CN152, or any other CN) may transmit to the radio device a list of TAIs associated with radio device registration areas (e.g., UE registration areas). The radio device may perform a registration update in the CN to allow the CN to update the radio device's location, for example, to provide the radio device with a new UE registration area if the radio device moves to a cell associated with a TAI that is not included in the list of TAIs associated with UE registration areas (e.g., via cell reselection).

[0056] RAN areas may be used to track radio devices (e.g., the location of a radio device at the RAN level). For radio devices in an RRC inactive state (e.g., RRC inactive 604), the radio device may be assigned / provided / configured in a RAN notification area. A RAN notification area may contain one or more cell identification information (e.g., a list of RAIs and / or a list of TAIs). A base station may belong to one or more RAN notification areas. A cell may belong to one or more RAN notification areas. A radio device may perform a notification area update in the RAN to update its RAN notification area, for example, if the radio device moves to a cell that is not included in the RAN notification area to which it is assigned / provided / configured (e.g., via cell reselection).

[0057] A base station that stores the RRC context for a radio device, or the final serving base station of a radio device, may be called an anchor base station. The anchor base station may maintain the RRC context for the radio device for at least the duration that the radio device remains in the anchor base station's RAN notification area and / or the duration that the radio device remains in an RRC inactive state (e.g., RRC inactive 604).

[0058] A base station (e.g., gNB160 in Figure 1B or any other base station) may be divided into two parts: a central unit (e.g., a base station central unit such as gNB CU) and one or more distributed units (e.g., base station distributed units such as gNB DU). The base station central unit (CU) may be coupled to one or more base station distributed units (DU) using an F1 interface (e.g., an F1 interface as defined in the NR configuration). The base station CU may include the RRC layer, PDCP layer, and SDAP layer. The base station distributed unit (DU) may include the RLC layer, MAC layer, and PHY layer.

[0059] A physical signal and physical channel (as described with respect to Figures 5A and 5B, for example) can be mapped onto one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols in an NR configuration, or any other symbols). OFDM is a multicarrier communication scheme that transmits / transmits data via F orthogonal subcarriers (or tones). The data, called source symbols, can be mapped to a set of complex symbols (e.g., M orthogonal amplitude modulation (M-QAM) symbols or M phase shift key (M PSK) symbols or any other modulation symbols) which are divided into F parallel symbol streams before the data is transmitted. The F parallel symbol streams can be treated as if they were in the frequency domain. The F parallel symbols can be used as input to an inverse fast Fourier transform (IFFT) block that converts them to the time domain. The IFFT block can take F source symbols at a time, one from each of the F parallel symbol streams. The IFFT block can use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be an F-time domain sample representing the sum of F orthogonal subcarriers. An F-time domain sample can form a single OFDM symbol. The OFDM symbol provided / output by the IFFT block can be transmitted / transmitted over the air interface at the carrier frequency after, for example, one or more processes (e.g., the addition of a cyclic prefix) and upconversion. The F parallel symbol streams may be mixed using a Fast Fourier Transform (FFT) block before being processed by the IFFT block. This operation can generate an OFDM symbol precoded with a Discrete Fourier Transform (DFT), which may be used by one or more radio devices on the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at the receiver using an FFT block to reconstruct the data mapped to the source symbol.

[0060] Figure 7 shows an exemplary frame configuration. A frame may include, for example, an NR radio frame in which OFDM symbols may be grouped. A frame (e.g., an NR radio frame) may be identified / indicated by a System Frame Quantity / Number (SFN) or any other value. The SFN may repeat over a period of 1024 frames. A single NR frame may have a duration of 10 milliseconds (ms) and may contain 10 subframes with a duration of 1 ms. A subframe may be divided into one or more slots (e.g., depending on the numerology and / or different subcarrier intervals). Each of the one or more slots may contain, for example, 14 OFDM symbols per slot. Any amount of symbols, slots, or durations may be used for any time interval.

[0061] The duration of a slot may depend on the numerology used for the OFDM symbol of the slot. For example, flexible numerology may be supported to accommodate different deployments (e.g., from cells with carrier frequencies less than 1 GHz to cells with carrier frequencies in the mm-wave range). Flexible numerology may be supported, for example, in an NR configuration or any other radio configuration. The numerology may be defined in terms of subcarrier spacing and / or cyclic prefix duration. Subcarrier spacing may be scaled up by a power of 2 from a baseline subcarrier spacing of 15 kHz. Cyclic prefix duration may be scaled down by a power of 2 from a baseline cyclic prefix duration of 4.7 microseconds, for example, for numerology in an NR configuration or any other radio configuration. The numerology can be defined by the following combinations of subcarrier intervals / cyclic prefix durations: 15 kHz / 4.7 microseconds, 30 kHz / 2.3 microseconds, 60 kHz / 1.2 microseconds, 120 kHz / 0.59 microseconds, 240 kHz / 0.29 microseconds, and / or any other combination of subcarrier intervals / cyclic prefix durations.

[0062] A slot can have a fixed amount / number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacings may have shorter slot durations and more slots per subframe. An example of a numerology-dependent slot duration and slot transmission structure per subframe is shown in Figure 7 (a numerology with a 240 kHz subcarrier spacing is not shown in Figure 7). A subframe (e.g., in an NR configuration) can be used as a numerology-independent time reference. A slot can be used as a unit on which uplink and downlink transmissions are scheduled. Scheduling (e.g., in an NR configuration) can be separated from slot duration. Scheduling can begin with any OFDM symbol. Scheduling can continue for as many symbols as needed for transmission, for example, to support low latency. These partial slot transmissions may be called minislot or subslot transmissions.

[0063] Figure 8 shows an exemplary resource configuration for one or more carriers. The resource configuration may include slots in the time and frequency domains for an NR carrier or any other carrier. The slots may include resource elements (REs) and resource blocks (RBs). A resource element (RE) may be the smallest physical resource (e.g., an NR configuration). An RE may span one OFDM symbol in the time domain by one subcarrier in the frequency domain, as shown, for example, in Figure 8. An RB may span 12 consecutive REs in the frequency domain, as shown in Figure 8. A carrier (e.g., an NR carrier) may be limited to a width of a certain amount of RBs and / or subcarriers (e.g., 275 RBs or 275 × 12 = 3300 subcarriers). Such limitations, when used, may limit the carrier (e.g., NR carrier) frequency based on the subcarrier spacing (e.g., carrier frequencies of 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively). A 400MHz bandwidth can be set based on a 400MHz bandwidth limit per carrier. Any other bandwidth can be set based on a bandwidth limit per carrier.

[0064] A single numerology may be used across the entire carrier bandwidth (e.g., NR as shown in Figure 8). In other exemplary configurations, multiple numerologies may be supported on the same carrier. NR and / or other access technologies may support a wide range of carrier bandwidths (e.g., up to 400 MHz for a 120 kHz subcarrier spacing). Not all radio devices can receive the entire carrier bandwidth (e.g., due to hardware limitations and / or different radio device capabilities). Receiving and / or utilizing the entire carrier bandwidth may be prohibited, for example, with respect to the power consumption of the radio device. A radio device may adapt the size of its receiving bandwidth based on the amount of traffic it is expected to receive (e.g., to reduce power consumption and / or for other purposes). Such adaptation may be called bandwidth adaptation.

[0065] The configuration of one or more Bandwidth Parts (BWPs) may support one or more radio devices that cannot receive the full carrier bandwidth. BWPs may, for example, support bandwidth adaptation for such radio devices that cannot receive the full carrier bandwidth. A BWP (e.g., a BWP in an NR configuration) may be defined by a subset of consecutive RBs on the carrier. A radio device may be configured 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) (e.g., via the RRC layer). One or more of the BWPs configured for a serving cell may be active, for example, at a given time. One or more BWPs may be called the active BWPs of a serving cell. A serving cell may have one or more first active BWPs on the uplink carrier and, for example, one or more second active BWPs on the secondary uplink carrier if the serving cell is configured to have a secondary uplink carrier.

[0066] A downlink BWP from a set of configured downlink BWPs can be linked with an uplink BWP from a set of configured uplink BWPs (for example, for unpaired spectra). Downlink BWPs and uplink BWPs can be linked, for example, if the downlink BWP index of one downlink BWP and the uplink BWP index of the other uplink BWP are the same. A wireless device can expect that the center frequency of a downlink BWP is the same as the center frequency of an uplink BWP (for example, for unpaired spectra).

[0067] A base station may configure a radio device with one or more control resource sets (CORESETs) for at least one search space. For example, a base station may configure a radio device with one or more CORESETs for a set of downlink BWPs configured on a primary cell (PCell) or secondary cell (SCell). The search space may include a set of locations in the time and frequency domains where a radio device can monitor / discover / detect / identify control information. The search space may be radio device-specific (e.g., UE-specific search space) or a common search space (e.g., potentially available to a group of multiple radio devices or radio user devices). In an active downlink BWP, a base station may configure a group of radio devices in a common search space on a PCell or on a primary / secondary cell (PSCell).

[0068] A base station may configure a radio device with one or more resource sets for one or more PUCCH transmissions for uplink BWPs in a set of configured uplink BWPs. The radio device may receive downlink receptions (e.g., PDCCH or PDSCH) on a downlink BWP according to a configured numerology (e.g., configured subcarrier spacing and / or configured cyclic prefix duration) for a downlink BWP. The radio device may transmit / transmit uplink transmissions (e.g., PUCCH or PUSCH) on an uplink BWP according to a configured numerology (e.g., configured subcarrier spacing and / or configured cyclic prefix length for an uplink BWP).

[0069] One or more BWP indicator fields may be provided / included in the Downlink Control Information (DCI). The value of a BWP indicator field may indicate which of the configured set of BWPs is the active downlink BWP for one or more downlink receptions. The value of one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions.

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

[0071] A base station may configure a radio device with a BWP inactivity timer value for PCell. The radio device may start or restart the BWP inactivity timer at any appropriate time. The radio device may start or restart the BWP inactivity timer if, for example, one or more conditions are met. One or more conditions may include at least one of the following: the radio device detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectral operations; the radio device detects a DCI indicating an active downlink BWP other than the default downlink BWP for unpaired spectral operations; and / or the radio device detects a DCI indicating an active uplink BWP other than the default uplink BWP for unpaired spectral operations. The radio device may start / run the BWP inactivity timer toward expiration (e.g., increment from zero to the BWP inactivity timer value or decrement from the BWP inactivity timer value to zero) if the radio device does not detect a DCI during a time interval (e.g., 1 ms or 0.5 ms). A wireless device may switch from an active downlink BWP to a default downlink BWP, for example, when the BWP non-activity timer expires.

[0072] A base station may semi-statically configure a radio device with one or more BWPs. The radio device may switch the active BWP from the first BWP to the second BWP based on (for example, subsequently, or in response to) receiving a DCI indicating a second BWP as the active BWP. The radio device may also switch the active BWP from the first BWP to the second BWP based on (for example, subsequently, or in response to) the expiration of a BWP inactivity timer (for example, if the second BWP is the default BWP).

[0073] Downlink BWP switching may refer to switching the active downlink BWP from the first downlink BWP to the second downlink BWP (e.g., the second downlink BWP is activated and the first downlink BWP is deactivated). Uplink BWP switching may refer to switching the active uplink BWP from the first uplink BWP to the second uplink BWP (e.g., the second uplink BWP is activated and the first uplink BWP is deactivated). Downlink and uplink BWP switching may be performed independently (e.g., for paired spectra / spectrums). Downlink and uplink BWP switching may be performed simultaneously (e.g., for unpaired spectra / spectrums). Switching between configured BWPs may occur based on, for example, RRC signaling, DCI signaling, the expiration of the BWP non-activity timer, and / or the start of random access.

[0074] Figure 9 shows an example of a configured BWP. Bandwidth matching using multiple BWPs (e.g., three configured BWPs for an NR carrier) may be available. A radio device configured to have multiple BWPs (e.g., three BWPs) may switch from one BWP to another at a switching point. The BWPs may include BWP902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz, BWP904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz, and BWP906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP902 may be the initial active BWP, and BWP904 may be the default BWP. The radio device may switch between BWPs at a switching point. The radio device may switch from BWP902 to BWP904 at switching point 908. Switching at switching point 908 may be done for any preferred reason. A switch at switching point 908 may occur, for example, based on (for example, after or in response to) the expiration of a BWP inactivity timer (e.g., indicating a switch to the default BWP). A switch at switching point 908 may occur, for example, based on (for example, after or in response to) the reception of a DCI indicating BWP 904 as the active BWP. The wireless device may switch at switching point 910 from active BWP 904 to BWP 906, for example, after or in response to receiving a DCI indicating BWP 906 as the new active BWP. The wireless device may switch at switching point 912 from active BWP 906 to BWP 904, for example, based on (for example, after or in response to) the expiration of a BWP inactivity timer. The wireless device may switch at switching point 912 from active BWP 906 to BWP 904, for example, after or in response to receiving a DCI indicating BWP 904 as the new active BWP. The wireless device may, for example, switch from active BWP904 to BWP902 at switching point 914 after receiving a DCI indicating BWP902 as the new active BWP, or in response to such a DCI.

[0075] The wireless device procedure for switching BWPs on a secondary cell may be identical / similar to that on a primary cell, for example, if the wireless device is configured for the secondary cell with a set of configured downlink BWPs and a default downlink BWP in timer values. The wireless device may use timer values ​​and a default downlink BWP for a secondary cell in the same / similar manner as the wireless device uses timer values ​​and / or a default BWP for a primary cell. Timer values ​​(e.g., BWP inactivity timers) may be configured for each cell (e.g., for one or more BWPs) for example, via RRC signaling or any other signaling. One or more active BWPs may switch to another BWP, for example, based on the expiration of a BWP inactivity timer.

[0076] Two or more carriers can be aggregated, and data can be transmitted simultaneously between the same radio device using carrier aggregation (CA) (for example, to increase the data rate). The aggregated carriers in CA may be called component carriers (CCs). For example, when CA is configured / used, there may be multiple quantities / numbers of serving cells for the radio device (e.g., one serving cell for the CC). A CC can have multiple configurations within the frequency domain.

[0077] Figure 10A shows an exemplary CA configuration based on CCs. As shown in Figure 10A, the three types of CA configurations may include an in-band (continuous) configuration 1002, an in-band (discontinuous) configuration 1004, and / or an interband configuration 1006. In the in-band (continuous) configuration 1002, two CCs may be aggregated in the same frequency band (frequency band A) and may be directly adjacent to each other within the frequency band. In the in-band (discontinuous) configuration 1004, two CCs may be aggregated in the same frequency band (frequency band A), but may be separated from each other within the frequency band by a gap. In the interband configuration 1006, two CCs may be located in different frequency bands (e.g., frequency band A and frequency band B, respectively).

[0078] The network may set a maximum number of CCs that can be aggregated (e.g., up to 32 CCs can be aggregated in NR, or any other number can be aggregated in other systems). Aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplication schemes (TDD, FDD, or any other duplication scheme). Serving cells for wireless devices using CA may have downlink CCs. One or more uplink CCs may optionally be configured for serving cells (e.g., for FDD). The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when a wireless device has more data traffic on the downlink than on the uplink.

[0079] One of the aggregation cells for a wireless device may be called a primary cell (PCell) when a CA is configured. A PCell may be the serving cell to which the wireless device first connects or accesses, for example, during or at the time of RRC connection establishment, RRC connection re-establishment, and / or handover. A PCell may provide / have NAS mobility information and security inputs to a wireless device. A wireless device may have different PCells. For downlinks, the carrier corresponding to a PCell may be called a downlink primary cell CC (DL PCC). For uplinks, the carrier corresponding to a PCell may be called an uplink primary cell CC (UL PCC). Other aggregation cells for a wireless device (e.g., associated with CCs other than DL PCC and UL PCC) may be called secondary cells (SCells). SCells may be configured, for example, after a PCell has been configured for a wireless device. SCells may be configured via an RRC connection reconfiguration procedure. Regarding downlink, a carrier corresponding to SCell can be called a downlink secondary CC (DL SCC). Regarding uplink, a carrier corresponding to SCell can be called an uplink secondary CC (UL SCC).

[0080] A configured SCell for a wireless device may be activated or deactivated, for example, based on traffic and channel conditions. Deactivating a SCell may cause the wireless device to stop PDCCH and PDSCH reception on the SCell, as well as PUSCH, SRS, and CQI transmission on the SCell. A configured SCell may be activated or deactivated, for example, using a MAC CE (e.g., the MAC CE described with respect to Figure 4B). The MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCell (e.g., within a subset of configured SCells) will be activated or deactivated for the wireless device. A configured SCell may be deactivated, for example, based on (e.g., thereafter or in response to) the expiration of a SCell deactivation timer (e.g., one SCell deactivation timer may be configured per SCell).

[0081] DCI may include control information such as scheduling assignments and scheduling grants for cells. DCI may be transmitted / transmitted through the cell corresponding to the scheduling assignment and / or scheduling grant, which may be called self-scheduling. DCI containing cell control information may be transmitted / transmitted through another cell, which may be called cross-carrier scheduling. Uplink control information (UCI) may include control information such as HARQ acknowledgments and channel state feedback (e.g., CQI, PMI, and / or RI) for aggregation cells. UCI may be transmitted / transmitted through the uplink control channel (e.g., PUCCH) of a PCell or a specific SCell (e.g., a SCell configured to have PUCCH). If the amount / number of aggregated downlink CCs is large, the PUCCH of the PCell may become overloaded. A cell may be divided into multiple PUCCH groups.

[0082] Figure 10B shows an exemplary group of cells. An aggregation cell may consist of one or more PUCCH groups (for example, as shown in Figure 10B). One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may each contain one or more downlink CCs. PUCCH group 1010 may contain one or more downlink CCs, for example, three downlink CCs, i.e., PCell 1011 (e.g., DL PCC), SCell 1012 (e.g., DL SCC), and SCell 1013 (e.g., DL SCC). PUCCH group 1050 may contain one or more downlink CCs, for example, three downlink CCs, i.e., PUCCH SCell (or PSCell) 1051 (e.g., DL SCC), SCell 1052 (e.g., DL SCC), and SCell 1053 (e.g., DL SCC). One or more uplink CCs of PUCCH group 1010 may be configured as PCell1021 (e.g., UL PCC), SCell1022 (e.g., UL SCC), and SCell1023 (e.g., UL SCC). One or more uplink CCs of PUCCH group 1050 may be configured as PUCCH SCell (or PSCell)1061 (e.g., UL SCC), SCell1062 (e.g., UL SCC), and SCell1063 (e.g., UL SCC). UCIs associated with downlink CCs of PUCCH group 1010, indicated as UCI1031, UCI1032, and UCI1033, may be transmitted / transmitted via the uplink of PCell1021 (e.g., via the PUCCH of PCell1021). The UCIs associated with the downlink CC of PUCCH group 1050, indicated as UCI1071, UCI1072, and UCI1073, may be transmitted / transmitted via the uplink of PUCCH SCell (or PSCell) 1061 (for example, via the PUCCH of PUCCH SCell 1061).A single uplink PCell may be configured to transmit / transmit UCIs associated with six downlink CCs, for example, when the aggregation cell shown in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050. PCell 1021 may become overloaded if, for example, UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are transmitted / transmitted through PCell 1021. Overload can be prevented and / or reduced by separating the transmission of UCIs between PCell 1021 and PUCCH SCell (or PSCell) 1061.

[0083] A PCell may include a downlink carrier (e.g., PCell1011) and an uplink carrier (e.g., PCell1021). An SCell may include only a downlink carrier. A cell containing a downlink carrier and optionally an uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may, for example, display / identify the cell's downlink carrier and / or uplink carrier, depending on the context in which the physical cell ID is used. The physical cell ID may be determined, for example, using synchronization signals (e.g., PSS and / or SSS) transmitted over the downlink component carrier. The cell index may be determined, for example, using one or more RRC messages. The physical cell ID may be called a carrier ID, and the cell index may be called a carrier index. A first physical cell ID for a first downlink carrier may refer to a first physical cell ID for a cell containing the first downlink carrier. Substantially the same / similar concepts may apply, for example, to carrier activation. Activation of the first carrier may refer to the activation of the cell containing the first carrier.

[0084] The multi-carrier nature of the PHY layer may be exposed / indicated in the MAC layer (e.g., in a CA configuration). HARQ entities may operate on serving cells. Transport blocks may be generated per serving cell allocation / grant. Transport blocks and potential HARQ retransmissions of transport blocks may be mapped to serving cells.

[0085] For downlink, a base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RS) (e.g., PSS, SSS, CSI-RS, DM-RS, and / or PT-RS) to one or more radio devices. For uplink, one or more radio devices may transmit one or more RS to a base station (e.g., DM-RS, PT-RS, and / or SRS). PSS and SSS are transmitted by the base station and used by one or more radio devices to synchronize one or more radio devices with the base station. A synchronization signal (SS) / physical broadcast channel (PBCH) block may include PSS, SSS, and PBCH. The base station may periodically transmit bursts of SS / PBCH blocks, which may be called SSB.

[0086] Figure 11A shows an exemplary mapping of one or more SS / PBCH blocks. A burst of SS / PBCH blocks may consist of one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in Figure 11A). Bursts may be transmitted / transmitted periodically (e.g., every two frames, every 20ms, or at any other duration). Bursts may be limited to half frames (e.g., a first half frame with a duration of 5ms). These parameters (e.g., the amount / number of SS / PBCH blocks per burst, the periodicity of the burst, the location of the burst within a frame) may be configured based on at least one of the following: for example, the carrier frequency of the cell on which the SS / PBCH blocks are transmitted / transmitted, the cell's numerology or subcarrier spacing, the network configuration (e.g., using RRC signaling), and / or any other preferred factors. A wireless device may assume subcarrier spacing for SS / PBCH blocks based on the monitored carrier frequency, for example, unless the wireless network configures a wireless device that assumes different subcarrier spacings.

[0087] An SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols as shown in Figure 11A, or any other quantity / number of symbols) and one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers or any other quantity / number of subcarriers). PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted / transmitted first, e.g., spanning one OFDM symbol and 127 subcarriers. The SSS may be transmitted / transmitted after the PSS (e.g., after two symbols), e.g., spanning one OFDM symbol and 127 subcarriers. PBCH may be transmitted / transmitted after PSS (e.g., across the following three OFDM symbols), may span 240 subcarriers (e.g., in the second and fourth OFDM symbols as shown in Figure 11A), and / or span fewer than 240 subcarriers (e.g., in the third OFDM symbol as shown in Figure 11A).

[0088] The location of the SS / PBCH block in the time and frequency domains does not need to be known to the radio device (e.g., when the radio device is searching for a cell). The radio device may monitor the carrier of the PSS to find and select a cell, for example. The radio device may monitor the frequency location within the carrier. The radio device may search for the PSS at a different frequency location within the carrier if the PSS is not found after a certain duration (e.g., 20 ms). The radio device may search for the PSS at a different frequency location within the carrier, for example, as indicated by a synchronous raster. Once the PSS is found at a location in the time and frequency domains, the radio device may determine the locations of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block, for example. The SS / PBCH block may be a cell-defining SS block (CD-SSB). A primary cell may be associated with a CD-SSB. A CD-SSB may be located on a synchronous raster. Cell selection / searching and / or re-selection may be based on the CD-SSB.

[0089] SS / PBCH blocks can be used by a radio device to determine one or more parameters of a cell. For example, a radio device may determine the physical cell identifier (PCI) of a cell based on the PSS and SSS arrays, respectively. A radio device may determine the location of a cell's frame boundary based on the location of an SS / PBCH block. An SS / PBCH block may indicate that it was transmitted / transmitted according to a transmission pattern. In a transmission pattern, an SS / PBCH block may be a known distance from the frame boundary (e.g., a predefined distance for a RAN configuration between one or more networks, one or more base stations, and one or more radio devices).

[0090] The PBCH may use QPSK modulation and / or forward error correction (FEC). FEC may use polar coding. One or more symbols strung by the PBCH may include / carry one or more DM-RS for demodulation of the PBCH. The PBCH may include indications of the cell's current system frame quantity / number (SFN) and / or SS / PBCH block timing index. These parameters may facilitate time synchronization of the radio device to the base station. The PBCH may include an MIB used to transmit one or more parameters to the radio device. The MIB may contain the remaining minimum system information (RMSI) used by the radio device and associated with the cell. The RMSI may include a system information block type 1 (SIB1). The SIB1 may contain information for the radio device to access the cell. The radio device may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include the SIB1. The SIB1 can be decoded using parameters provided / included in the MIB. A PBCH may indicate the absence of SIB1. For example, based on the PBCH indicating the absence of SIB1, a wireless device may point to a frequency. The wireless device may then search for an SS / PBCH block at the frequency to which it is directed.

[0091] A wireless device may assume that one or more SS / PBCH blocks transmitted / transmitted with the same SS / PBCH block index are quasi-identical (QCL-ified) (e.g., have substantially the same / similar Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial Rx parameters). A wireless device cannot assume QCL for SS / PBCH block transmissions with different SS / PBCH block indices. An SS / PBCH block (e.g., a block within a half-frame) can be transmitted / transmitted in a spatial direction (e.g., using different beams across the coverage area of ​​a cell). A first SS / PBCH block may be transmitted / transmitted in a first spatial direction using a first beam, a second SS / PBCH block may be transmitted / transmitted in a second spatial direction using a second beam, a third SS / PBCH block may be transmitted / transmitted in a third spatial direction using a third beam, and a fourth SS / PBCH block may be transmitted / transmitted in a fourth spatial direction using a fourth beam.

[0092] A base station may transmit / transmit multiple SS / PBCH blocks, for example, within the carrier's frequency span. The first PCI of the first SS / PBCH block of the multiple SS / PBCH blocks may be different from the second PCI of the second SS / PBCH block of the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted / transmitted at different frequency locations may be different or substantially identical.

[0093] CSI-RS may be transmitted by a base station and used by a radio device to obtain / acquire / determine channel status information (CSI). A base station may configure a radio device with one or more CSI-RS for channel estimation or any other suitable purpose. A base station may configure a radio device with one or more identical / similar CSI-RS. A radio device may measure one or more CSI-RS. A radio device may estimate the downlink channel status and / or generate a CSI report, for example, based on measurements of one or more downlink CSI-RS. A radio device may transmit a CSI report to a base station (e.g., based on periodic CSI reports, semi-sustained CSI reports, and / or aperiodic CSI reports). A base station may perform link fitting using feedback provided by the radio device (e.g., estimated downlink channel status).

[0094] A base station may semi-statically configure a radio device using one or more CSI-RS resource sets. CSI-RS resources may be associated with location and periodicity in the time and frequency domains. The base station may selectively activate and / or deactivate CSI-RS resources. The base station may indicate to the radio device that a CSI-RS resource in a CSI-RS resource set is being activated and / or deactivated.

[0095] A base station may configure a radio device to report CSI measurements. A base station may configure a radio device to provide CSI reports periodically, aperiodicly, or semi-persistently. For periodic CSI reports, a radio device may be configured to have the timing and / or periodicity of multiple CSI reports. For aperiodic CSI reports, a base station may request a CSI report. A base station may instruct a radio device to measure configured CSI-RS resources and provide a CSI report related to the measurements. For semi-persistent CSI reports, a base station may configure a radio device to periodically transmit / transmit and selectively activate or deactivate periodic reports (e.g., via one or more activation / deactivation MAC CEs and / or one or more DCIs). A base station may configure a radio device with a CSI-RS resource set and CSI reports using, for example, RRC signaling.

[0096] A CSI-RS configuration may include one or more parameters, for example, indicating up to 32 antenna ports (or any other number of antenna ports). A wireless device may be configured to use / adopt the same OFDM symbols for downlink CSI-RS and CORESET, for example, when downlink CSI-RS and CORESET are spatially QCL-ified and the resource elements associated with downlink CSI-RS are outside the physical resource block (PRB) configured for CORESET. A wireless device may be configured to use / adopt the same OFDM symbols for downlink CSI-RS and SS / PBCH blocks, for example, when downlink CSI-RS and SS / PBCH blocks are spatially QCL-ified and the resource elements associated with downlink CSI-RS are outside the PRB configured for SS / PBCH blocks.

[0097] Downlink DM-RS can be transmitted / transmitted by a base station and received / used by a radio device for channel estimation. Downlink DM-RS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCHs). A network (e.g., an NR network) may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a frontloaded DM-RS pattern. A frontloaded DM-RS can be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure a radio device with a quantity / number (e.g., maximum quantity / number) of frontloaded DM-RS symbols on a PDSCH. A DM-RS configuration may support one or more DM-RS ports. A DM-RS configuration may support up to eight orthogonal downlink DM-RS ports per radio device (e.g., for a single user MIMO). A DM-RS configuration may support up to four orthogonal downlink DM-RS ports per radio device (e.g., for multi-user MIMO). A radio network may support a common DM-RS structure for downlink and uplink (e.g., for at least CP-OFDM). DM-RS locations, DM-RS patterns, and / or scramble sequences may be identical or different. A base station may transmit / transmit downlink DM-RS and the corresponding PDSCH using, for example, the same precoding matrix. A radio device may use one or more downlink DM-RS for coherent demodulation / channel estimation of the PDSCH.

[0098] A transmitter (e.g., a base station transmitter) may use a precoder matrix for a portion of the transmission bandwidth. The transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices may differ, for example, based on the fact that the first bandwidth is different from the second bandwidth. A wireless device may assume that the same precoder matrix is ​​used across a set of PRBs. The set of PRBs may be determined / suggested / identified / indicated as a precoder resource block group (PRG).

[0099] A PDSCH may contain one or more layers. A radio device may assume that at least one symbol with DM-RS exists on one or more layers of the PDSCH. The upper layers may constitute one or more DM-RS for the PDSCH (e.g., up to three DM-RS for the PDSCH). Downlink PT-RS may be transmitted / transmitted by a base station and may be used by a radio device for, for example, phase noise compensation. Whether or not downlink PT-RS exists may depend on the RRC configuration. The presence and / or pattern of downlink PT-RS may be configured on radio device-specific criteria using association with one or more parameters used / adopted for other purposes (e.g., modulation and coding scheme (MCS)) that may be indicated by, for example, a combination of RRC signaling and / or DCI. The dynamic presence of downlink PT-RS may be associated with one or more DCI parameters, including at least MCS, if configured. A network (e.g., an NR network) may support multiple PT-RS densities defined in the time and / or frequency domains. The frequency domain density (configuration / if any) may be associated with at least one configuration of the planned bandwidth. A wireless device may assume the same precoding for DM-RS and PT-RS ports. The quantity / number of PT-RS ports may be less than the quantity / number of DM-RS ports in the planned resources. Downlink PT-RS may be configured / allocated / limited for the planned time / frequency duration for the wireless device. Downlink PT-RS may be transmitted / transmitted via symbols, for example, to facilitate phase tracking in the receiver.

[0100] A wireless device may transmit / transmit uplink DM-RS to a base station, for example, for channel estimation. A base station may use uplink DM-RS for coherent demodulation of one or more uplink physical channels. A wireless device may transmit / transmit uplink DM-RS on PUSCH and / or PUCCH. Uplink DM-RS may span frequency ranges similar to the frequency range associated with the corresponding physical channel. A base station may configure a wireless device with one or more uplink DM-RS configurations. At least one DM-RS configuration may support a frontload DM-RS pattern. A frontload DM-RS may be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS may be configured to transmit / transmit on one or more symbols of PUSCH and / or PUCCH. A base station may semi-statically configure a radio device with a quantity / number (e.g., maximum quantity / number) of front-loaded DM-RS symbols for PUSCH and / or PUCCH that the radio device can use to schedule single-symbol DM-RS and / or double-symbol DM-RS. A network (e.g., an NR network) may support a common DM-RS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)). The DM-RS locations, DM-RS patterns, and / or DM-RS scramble sequences may be substantially identical or different.

[0101] A PUSCH may include one or more layers. A wireless device may transmit / transmit at least one symbol using DM-RS present on one or more layers of the PUSCH. The upper layers may constitute one or more DM-RS (e.g., up to three DM-RS) for the PUSCH. Uplink PT-RS (which may be used by the base station for phase tracking and / or phase noise compensation) may or may not be present, depending, for example, the RRC configuration of the wireless device. The presence and / or pattern of uplink PT-RS may be configured on a wireless device-specific basis (e.g., UE-specific basis) by a combination of one or more parameters configured / adopted for, for example, RRC signaling and / or other purposes (e.g., MCS), which may be indicated by DCI. The dynamic presence of uplink PT-RS may be associated with one or more DCI parameters, including at least MCS, if configured. A wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density (if configured / present) may be associated with at least one configuration of the intended bandwidth. A wireless device may assume the same precoding for DM-RS and PT-RS ports. The quantity / number of PT-RS ports may be less than the quantity / number of DM-RS ports in the allocated resources. Uplink PT-RS may be configured / allocated / limited for the allocated time / frequency duration for the wireless device.

[0102] One or more SRSs may be transmitted / transmitted by a radio device to a base station for channel state estimation, for example, to support uplink channel-dependent scheduling and / or link fitting. SRSs transmitted / transmitted by a radio device may enable / enable the base station to estimate uplink channel states at one or more frequencies. The base station scheduler may use / adopt the estimated uplink channel states to allocate one or more resource blocks for uplink push transmissions for the radio device. A base station may semi-statically configure a radio device with one or more SRS resource sets. In the case of SRS resource sets, a base station may configure a radio device with one or more SRS resources. SRS resource set applicability may be configured, for example, by higher-layer (e.g., RRC) parameters. SRS resources in a set of SRS resource sets (e.g., having identical / similar time-domain behavior, periodic, aperiodic, and / or homogeneous) may be transmitted / transmitted instantaneously (e.g., simultaneously), for example, when higher-layer parameters indicate beam management. A wireless device may transmit / transmit one or more SRS resources in an SRS resource set. A network (e.g., an NR network) may support aperiodic, periodic, and / or semi-persistent SRS transmission. A wireless device may transmit / transmit SRS resources based, for example, one or more trigger types. One or more trigger types may include upper-layer signaling (e.g., RRC) and / or one or more DCI formats. At least one DCI format may be used / adopted for the wireless device to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to an SRS triggered based on upper-layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. A wireless device may be configured to transmit / transmit an SRS after the transmission of a PUSCH and the corresponding uplink DM-RS, for example, when the PUSCH and SRS are transmitted / transmitted in the same slot.A base station may quasi-statistically configure a radio device using one or more SRS configuration parameters that indicate at least one of the following: SRS resource configuration identifier, quantity / number of SRS ports, time-domain behavior of the SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS), slots, minislots, and / or subframe-level periodicity, offsets for periodic and / or aperiodic SRS resources, quantity / number of OFDM symbols in the SRS resource, starting OFDM symbol of the SRS resource, SRS bandwidth, frequency-hopping bandwidth, cyclic shift, and / or SRS sequence ID.

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

[0104] Channels that use beamforming may require beam management. Beam management may include beam measurement, beam selection, and / or beam indication. A beam may be associated with one or more reference signals. A beam may be identified by one or more beamforming reference signals. A wireless device may perform downlink beam measurement and generate a beam measurement report based on, for example, one or more downlink reference signals (e.g., CSI-RS). A wireless device may perform downlink beam measurement procedures after, for example, an RRC connection has been set up with a base station.

[0105] Figure 11B shows an exemplary mapping of one or more CSI-RS. CSI-RS can be mapped within the time and frequency domains. Each rectangular block shown in Figure 11B may correspond to a resource block (RB) within the cell bandwidth. A base station may send / transmit one or more RRC messages containing CSI-RS resource configuration parameters that represent one or more CSI-RS. One or more of the parameters may be configured by higher-layer signaling for CSI-RS resource configuration (e.g., RRC and / or MAC signaling). One or more of the parameters may include at least one of the following: CSI-RS resource configuration identity, CSI-RS port quantity / number, CSI-RS configuration (e.g., position of symbols and resource elements (REs) in subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity of radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi-identical location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0106] One or more beams may be configured for radio devices with configurations specific to the radio device. Three beams are shown in Figure 11B (beam #1, beam #2, and beam #3), but more or fewer beams may be configured. Beam #1 may be assigned to CSI-RS1101 which can be transmitted / transmitted on one or more subcarriers of the RB of a first symbol. Beam #2 may be assigned to CSI-RS1102 which can be transmitted / transmitted on one or more subcarriers of the RB of a second symbol. Beam #3 may be assigned to CSI-RS1103 which can be transmitted / transmitted on one or more subcarriers in the RB of a third symbol. The base station may transmit another CSI-RS associated with a beam for another radio device using other subcarriers in the same RB (e.g., those not used to transmit / transmit CSI-RS1101), for example by using frequency division multiplexing (FDM). The beam used for a wireless device may be configured, for example, by using time-domain multiplexing (TDM), so that the beam for the wireless device uses different symbols than those used by the beams of other wireless devices. The wireless device may be delivered with a beam of orthogonal symbols (e.g., no overlapping symbols) by using TDM, for example.

[0107] CSI-RS (e.g., CSI-RS1101, 1102, 1103) may be transmitted by a base station and used by a radio device for one or more measurements. The radio device may measure the RSRP of the configured CSI-RS resources. The base station may configure the radio device in a reporting configuration, and the radio device may report the RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. The base station may determine one or more Transmission Configuration Indicators (TCI) states, including several quantities / numbers of reference signals, based on the reported measurements. The base station may indicate one or more TCI states to the radio device (e.g., via RRC signaling, MAC CE, and / or DCI). The radio device may receive downlink transmissions on an Rx beam determined based on one or more TCI states. The radio device may or may not have beam correspondence capability. A wireless device may determine the spatial domain filter of a transmission (Tx) beam, for example, based on the spatial domain filter of the corresponding Rx beam, if the wireless device has beam correspondence capability. A wireless device may perform an uplink beam selection procedure to determine the spatial domain filter of a Tx beam, for example, if the wireless device does not have beam correspondence capability. A wireless device may perform an uplink beam selection procedure based, for example, one or more sounding reference signal (SRS) resources configured to the wireless device by a base station. A base station may select and display an uplink beam for a wireless device, for example, based on measurements of one or more SRS resources transmitted by the wireless device.

[0108] A wireless device may, for example, determine / evaluate (e.g., measure) the channel quality of one or more beampair links in a beam management procedure. A beampair link may include the base station's Tx beam and the wireless device's Rx beam. The base station's Tx beam may transmit downlink signals, and the wireless device's Rx beam may receive downlink signals. The wireless device may, for example, transmit a beam measurement report based on the evaluation / determination. The beam measurement report may show one or more beampair quality parameters, including one or more beam identifiers (e.g., beam index, reference signal index, or similar), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0109] Figure 12A shows an example of a downlink beam management procedure. One or more downlink beam management procedures (e.g., downlink beam management procedures P1, P2, and P3) may be performed. Procedure P1 may enable measurements on the Tx beam of a TRP (or multiple TRPs) (e.g., radio device measurements) (e.g., to support the selection of one or more base station Tx beams and / or radio device Rx beams). The Tx beam of a base station (e.g., base station 1210) and the Rx beam of a radio device (e.g., radio device 1205) are shown as ellipses in the upper and lower rows of P1, respectively. Beamforming (e.g., at a TRP) may include a Tx beam sweep on a set of beams (e.g., a beam sweep shown in the upper rows of P1 and P2 as ellipses rotated counterclockwise, indicated by dashed arrows). Beamforming (e.g., in a wireless device) may include an Rx beam sweep on a set of beams (e.g., a beam sweep shown in the bottom rows of P1 and P3 as an ellipse rotated in the direction indicated by dashed arrows). Procedure P2 may be used to enable measurements on the Tx beam of the TRP (e.g., wireless device measurements) (shown in the top row of P2 as an ellipse rotated in the direction indicated by dashed arrows). The wireless device and / or base station may perform procedure P2 using, for example, a smaller set of beams than the set of beams used in procedure P1, or a narrower beam than the beams used in procedure P1. Procedure P2 may be called beam refinement. The wireless device may perform procedure P3 for Rx beam determination by, for example, using the same Tx beam of the base station and sweeping the Rx beam of the wireless device.

[0110] Figure 12B shows an example of an uplink beam management procedure. One or more uplink beam management procedures (e.g., uplink beam management procedures U1, U2, and U3) may be performed. Procedure U1 may be used to enable a base station (e.g., base station 1210) to perform measurements on the Tx beam of a radio device (e.g., radio device 1205) (e.g., to support the selection of one or more Tx beams of the radio device and / or Rx beams of the base station). The Tx beam of the radio device and the Rx beam of the base station are shown as ellipses in the upper and lower rows of U1, respectively. Beamforming (e.g., in the radio device) may include one or more beam sweeps, e.g., Tx beam sweeps from a set of beams (shown in the lower rows of U1 and U3 as ellipses rotated in the direction indicated by dashed arrows). Beamforming (e.g., at a base station) may include one or more beam sweeps, e.g., Rx beam sweeps from a set of beams (shown in the upper rows of U1 and U2 as ellipses rotated counterclockwise, indicated by dashed arrows). Procedure U2 may be used, for example, to allow a base station to tune its Rx beam when a radio device (e.g., a UE) is using a fixed Tx beam. The radio device and / or base station may perform procedure U2, for example, using a smaller set of beams than the set of beams used in procedure P1, or using a narrower beam than the beam used in procedure P1. Procedure U2 may be called beam refinement. The radio device may perform procedure U3 to tune its Tx beam, for example, when a base station is using a fixed Rx beam.

[0111] A wireless device may initiate / start / perform a beam fault recovery (BFR) procedure, for example, based on the detection of a beam fault. A wireless device may transmit / transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or similar) based on the initiation of a BFR procedure. A wireless device may detect a beam fault, for example, based on the determination that the quality of the beam pair link of the relevant control channel is insufficient (e.g., having an error rate higher than the error rate threshold, a received signal power lower than the received signal power threshold, a timer expiring, and / or similar).

[0112] A wireless device may measure the quality of a beampair link using, for example, one or more reference signals (RS) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more DM-RS. The quality of a beampair link may be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, RSRQ value, and / or CSI values ​​measured on the RS resources. A base station may indicate that an RS resource has been QCL-ified with one or more DM-RS of a channel (e.g., a control channel, a shared data channel, and / or similar). An RS resource and one or more DM-RS of a channel may be QCL-ified if, for example, the channel characteristics transmitted to the wireless device via the RS resource (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameter, fade, and / or similar) are similar to or identical to the channel characteristics transmitted to the wireless device via the channel.

[0113] A network (e.g., an NR network including gNB and / or ng-eNB) and / or a radio device may initiate / start / execute a random access procedure. A radio device in an RRC idle state (e.g., RRC_IDLE) and / or RRC inactive state (e.g., RRC_INACTIVE) may initiate / execute a random access procedure to request network connection setup. A radio device may initiate / start / execute a random access procedure from an RRC connected state (e.g., RRC_CONNECTED). A radio device may initiate / start / execute a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or obtain / determine uplink timing (e.g., if the uplink synchronization state is asynchronous). A radio device may initiate / start / execute a random access procedure to request one or more System Information Blocks (SIBs) (e.g., other System Information Blocks such as SIB2, SIB3, and / or similar). A wireless device may initiate / start / implement a random access procedure for beam fault recovery requests. A network may initiate / start / implement a random access procedure, for example, to establish time alignment for handover and / or SCell addition.

[0114] Figure 13A shows an exemplary four-step random access procedure. The four-step random access procedure may include a four-step race-based random access procedure. A base station (e.g., base station 1302) may send / transmit a configuration message 1310 to a radio device (e.g., radio device 1301) before, for example, initiating the random access procedure. The four-step random access procedure may include the transmission of four messages, including a first message (e.g., Msg1 1311), a second message (e.g., Msg2 1312), a third message (e.g., Msg3 1313), and a fourth message (e.g., Msg4 1314). The first message (e.g., Msg1 1311) may include a preamble (or random access preamble). The first message (e.g., Msg1 1311) may be called a preamble. The second message (e.g., Msg2 1312) may be included as a Random Access Response (RAR). The second message (e.g., Msg2 1312) may be called a RAR.

[0115] Configuration message 1310 may be transmitted using, for example, one or more RRC messages. One or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to a radio device. One or more RACH parameters may include at least one of one or more general parameters of a random access procedure (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-configCommon), and / or dedicated parameters (e.g., RACH-configDedicated). A base station may send / transmit (e.g., broadcast or multicast) one or more RRC messages to one or more radio devices. One or more RRC messages may be radio device-specific. One or more radio device-specific RRC messages may be dedicated RRC messages sent / transmitted to radio devices in an RRC connected state (e.g., RRC_CONNECTED) and / or RRC inactive state (e.g., RRC_INACTIVE). A wireless device may determine, based on one or more RACH parameters, the time-frequency resources and / or uplink transmission power for transmitting a first message (e.g., Msg1 1311) and / or a third message (e.g., Msg3 1313). The wireless device may also determine, based on one or more RACH parameters, the receive timing and downlink channel for receiving a second message (e.g., Msg2 1312) and a fourth message (e.g., Msg4 1314).

[0116] One or more RACH parameters provided / configured / included in configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for the transmission of the first message (e.g., Msg1 1311). One or more PRACH opportunities may be predefined (e.g., by a network including one or more base stations). One or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). One or more RACH parameters may indicate an association between (a) one or more PRACH opportunities and (b) one or more reference signals. One or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. One or more reference signals may be SS / PBCH blocks and / or CSI-RS. One or more RACH parameters may indicate the quantity / number of SS / PBCH blocks mapped to the PRACH opportunities and / or the quantity / number of preambles mapped to the SS / PBCH blocks.

[0117] One or more RACH parameters provided / configured / included in configuration message 1310 may be used to determine the uplink transmission power for the first message (e.g., Msg1 1311) and / or the third message (e.g., Msg3 1313). One or more RACH parameters may indicate the reference power for preamble transmission (e.g., the received target power and / or the initial power for preamble transmission). There may be one or more power offsets indicated by one or more RACH parameters. One or more RACH parameters may indicate the power ramping step, the power offset between the SSB and CSI-RS, the power offset between the transmission of the first message (e.g., Msg1 1311) and the third message (e.g., Msg3 1313), and / or the power offset values ​​between preamble groups. One or more RACH parameters may indicate one or more thresholds, for example, based on the fact that the wireless device can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carriers (e.g., a normal uplink (NUL) carrier and / or a complementary uplink (SUL) carrier).

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

[0119] A wireless device may determine a preamble based on one or more RACH parameters provided / configured / included in, for example, configuration message 1310. The wireless device may determine a preamble based on, for example, path loss measurement, RSRP measurement, and / or the size of a third message (e.g., Msg3 1313). One or more RACH parameters may indicate a preamble format, a maximum amount / number of preamble transmissions, and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station may use one or more RACH parameters to configure a wireless device with associations between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS). The wireless device may, for example, determine the preamble included in a first message (e.g., Msg1 1311) based on the association, if the association is configured. The first message (e.g., Msg1 1311) may be transmitted / transmitted to the base station via one or more RACH opportunities. A wireless device may use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and determination of PRACH opportunities. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate the association between a PRACH opportunity and one or more reference signals.

[0120] A wireless device may perform a preamble retransmission if, for example, no response is received based on (e.g., subsequently or in response to) a preamble transmission (e.g., during a period such as a monitoring window for monitoring RAR). The wireless device may increase the uplink transmission power for the preamble retransmission. The wireless device may select an initial preamble transmission power based, for example, on a target received preamble power configured by path loss measurement and / or the network. The wireless device may decide to retransmit / re-transmit the preamble and ramp up the uplink transmission power. The wireless device may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be the amount of the increment increase in uplink transmission power for the retransmission. The wireless device may increase the uplink transmission power if, for example, the wireless device determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission. A wireless device may, for example, use a counter parameter (e.g., PREAMBLE_TRANSMISSION_COUNTER) to count the amount / number of preamble transmissions and / or retransmissions. A wireless device may determine that a random access procedure has failed, for example, if the amount / number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax) without receiving a success response (e.g., RAR).

[0121] The second message (e.g., Msg2 1312) (e.g., received by a radio device) may contain a RAR. The second message (e.g., Msg2 1312) may contain multiple RARs corresponding to multiple radio devices. The second message (e.g., Msg2 1312) may be received based on (e.g., subsequently, or in response to) the transmission of the first message (e.g., Msg1 1311). The second message (e.g., Msg2 1312) may be scheduled on the DL-SCH and indicated by the PDCCH using, for example, a Random Access Radio Network Temporary Identifier (RA RNTI). The second message (e.g., Msg2 1312) may indicate that the first message (e.g., Msg1 1311) was received by a base station. A second message (e.g., Msg2 1312) may include a time alignment command that can be used by the wireless device to adjust the transmission timing of the wireless device, a scheduling grant for the transmission of a third message (e.g., Msg3 1313), and / or a temporary cell RNTI (TC-RNTI). The wireless device may determine / start a time window (e.g., ra-ResponseWindow) for monitoring PDCCH for the second message (e.g., Msg2 1312) after sending / transmitting the first message (e.g., Msg1 1311) (e.g., preamble). The wireless device may determine the start time of the time window based on the PRACH opportunity that the wireless device uses to send / transmit the first message (e.g., Msg1 1311) (e.g., preamble). A wireless device may begin a time window after one or more symbols of the last symbol of a first message (e.g., Msg1 1311) that includes a preamble (e.g., symbols indicating that the first message (e.g., Msg1 1311) has completed or is in the first PDCCH opportunity since the end of the preamble transmission). One or more symbols may be determined based on numerology. PDCCH may be mapped to a common search space (e.g., Type1-PDCCH common search space) composed of RRC messages.A wireless device may identify / determine a RAR, for example, based on an RNTI. A wireless network temporary identifier (RNTI) may be used in response to one or more events that initiate / start a random access procedure. A wireless device may use an RA-RNTI for one or more communications related to random access or any other purpose. An RA-RNTI may be associated with a PRACH opportunity in which the wireless device transmits / transmits a preamble. A wireless device may determine an RA-RNTI based, for example, on at least one of the OFDM symbol index, slot index, frequency domain index, and / or UL carrier indicators of a PRACH opportunity. An exemplary RA-RNTI may be determined as follows:

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

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

[0124] A wireless device may, for example, send / transmit a third message (e.g., Msg3 1313) based on (e.g., subsequently or in response to) the successful reception of a second message (e.g., Msg2 1312) (e.g., using the resource identified in Msg2 1312). The third message (e.g., Msg3 1313) may be used, for example, for conflict resolution in a conflict-based random access procedure. Multiple wireless devices may send / transmit the same preamble to a base station, and the base station may send / transmit RARs corresponding to the wireless devices. Conflicts can occur, for example, if multiple wireless devices interpret the RAR as corresponding to themselves. Conflict resolution (e.g., using a third message (e.g., Msg3 1313) and a fourth message (e.g., Msg4 1314)) can be used to increase the likelihood that a wireless device will not mistakenly use the identity of another wireless device. A wireless device may include a device identifier in a third message (e.g., Msg3 1313) (e.g., C-RNTI, if assigned, TC RNTI included in the second message (e.g., Msg2 1312), and / or any other suitable identifier) ​​to perform, for example, conflict resolution.

[0125] A fourth message (e.g., Msg4 1314) may be received based on (e.g., subsequently or in response to) the transmission of a third message (e.g., Msg3 1313). The base station may use the C-RNTI to address a radio on the PDCCH (e.g., the base station may send the PDCCH to the radio device), for example, if the C-RNTI was included in the third message (e.g., Msg3 1313). The random access procedure may be determined to be successful if, for example, the radio device's unique C-RNTI is found on the PDCCH (e.g., the PDCCH is scrambled by the C-RNTI). A fourth message (e.g., Msg4 1314) may be received using the DL-SCH associated with the TC RNTI if, for example, the TC RNTI is included in the third message (e.g., Msg3 1313) (e.g., if the radio device is in an RRC idle state (e.g., RRC_IDLE) or otherwise connected to a base station). For example, if the MAC PDU is successfully decoded and the MAC PDU matches the CCCH SDU transmitted / transmitted in the third message (e.g., Msg3 1313), or otherwise includes a corresponding radio device conflict resolution identity MAC CE, the radio device may determine that conflict resolution was successful and / or that the random access procedure was successfully completed.

[0126] A wireless device may be configured to have a SUL carrier and / or a NUL carrier. Initial access (e.g., random access) may be supported via the uplink carrier. A base station may configure a wireless device having multiple RACH configurations (e.g., two separate RACH configurations, one for the SUL carrier and the other for the NUL carrier). In the case of random access in a cell configured to have a SUL carrier, the network may indicate which carrier (NUL or SUL) to use. A wireless device may decide to use the SUL carrier, for example, if the measured quality of one or more reference signals (e.g., one or more reference signals associated with the NUL carrier) is lower than the broadcast threshold. Uplink transmission of random access procedures (e.g., a first message (e.g., Msg1 1311) and / or a third message (e.g., Msg3 1313)) may remain on or be carried out via the selected carrier. A wireless device may switch uplink carriers during a random access procedure (e.g., between Msg1 1311 and Msg3 1313). The wireless device may determine and / or switch uplink carriers for a first message (e.g., Msg1 1311) and / or a third message (e.g., Msg3 1313) based, for example, a channel clear evaluation (e.g., listen before talk).

[0127] Figure 13B illustrates a two-step random access procedure. A two-step random access procedure may include a two-step non-conflict random access procedure. Similar to a four-step conflict-based random access procedure, a base station (e.g., base station 1302) may send / transmit a configuration message 1320 to a radio device (e.g., radio device 1301) before the procedure begins. The configuration message 1320 may be similar in some respects to the configuration message 1310. The procedure shown in Figure 13B may include the transmission of two messages, a first message (e.g., Msg1 1321) and a second message (e.g., Msg2 1322). The first message (e.g., Msg1 1321) and the second message (e.g., Msg2 1322) may be similar in some respects to the first message (e.g., Msg1 1311) and the second message (e.g., Msg2 1312), respectively. A two-step, non-conflicting random access procedure cannot contain messages similar to a third message (e.g., Msg3 1313) and / or a fourth message (e.g., Msg4 1314).

[0128] A two-step (e.g., no-conflict) random access procedure may be configured / initiated for beam fault recovery, other SI requests, SCell addition, and / or handover. The base station may display or assign to the radio device the preamble to be used for the first message (e.g., Msg1 1321). The radio device may receive instructions for the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0129] A radio device may initiate a time window (e.g., ra-ResponseWindow) for monitoring the PDCCH for the RAR based on (e.g., after or in response to) the transmission of a preamble. A base station may configure a radio device with one or more beam fault recovery parameters, such as a separate time window and / or a separate PDCCH, in the search space indicated by an RRC message (e.g., recoverySearchSpaceId). A base station may configure one or more beam fault recovery parameters in association with a beam fault recovery request. A separate time window for monitoring the PDCCH and / or RAR may be configured to begin after the transmission of a beam fault recovery request (e.g., the window may begin with any number of symbols and / or slots after the transmission of the beam fault recovery request). A radio device may monitor a PDCCH transmission addressed to a cell RNTI (C-RNTI) in the search space. During a two-step (e.g., no-conflict) random access procedure, the radio device may determine that the random access procedure was successful, for example, based on having transmitted a first message (e.g., Msg1 1321) and received a corresponding second message (e.g., Msg2 1322) (e.g., subsequently or in response to it). The radio device may determine that the random access procedure was successfully completed, for example, if the PDCCH transmission is addressed to the corresponding C-RNTI. The radio device may determine that the random access procedure was successfully completed, for example, if the radio device receives a RAR containing a preamble identifier corresponding to the preamble transmitted by the radio device, and / or if the RAR contains a MAC sub-PDU having the preamble identifier. The radio device may determine a response as an instruction for acknowledgment of an SI request.

[0130] Figure 13C shows an exemplary two-step random access procedure. Similar to the random access procedures shown in Figures 13A and 13B, a base station (e.g., base station 1302) may send / transmit a configuration message 1330 to a radio device (e.g., radio device 1301) before the procedure begins. The configuration message 1330 may be similar in some respects to configuration messages 1310 and / or 1320. The procedure shown in Figure 13C may involve the transmission of multiple messages (e.g., two messages, including a first message (e.g., Msg A1331) and a second message (e.g., Msg B1332)).

[0131] Msg A1320 may be transmitted / transmitted by a wireless device via uplink transmission. Msg A1320 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include content similar to and / or equivalent to the content of a third message (e.g., Msg3 1313) (e.g., shown in Figure 13A). Transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or similar). The wireless device may receive a second message (e.g., Msg B1332) based on (e.g., subsequently in response to) a first message (e.g., Msg A1331). The second message (e.g., Msg B1332) may contain content similar to and / or equivalent to the content of the second message (e.g., Msg2 1312) (e.g., the RAR shown in Figure 13A), the content of the second message (e.g., Msg2 1322) (e.g., the RAR shown in Figure 13B), and / or content similar to and / or equivalent to the fourth message (e.g., Msg4 1314) (e.g., shown in Figure 13A).

[0132] A wireless device may initiate a two-step random access procedure (e.g., the two-step random access procedure shown in Figure 13C) for licensed and / or unlicensed spectra. The wireless device may decide whether to initiate a two-step random access procedure based on one or more factors. One or more factors may include at least one of the following: the wireless access technology in use (e.g., LTE, NR, and / or similar), whether the wireless device has a valid TA, cell size, the RRC status of the wireless device, the type of spectrum (e.g., licensed versus unlicensed), and / or any other suitable factors.

[0133] A wireless device may determine the wireless resources and / or uplink transmission power of the preamble 1341 and / or transport block 1342 (e.g., included in the first message (e.g., Msg A1331)) based on a two-step RACH parameter contained in configuration message 1330. The RACH parameter may indicate the MCS, time-frequency resources, and / or power control of the preamble 1341 and / or transport block 1342. The time-frequency resources for the transmission of the preamble 1341 (e.g., PRACH) and the time-frequency resources for the transmission of the transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameter may enable the wireless device to determine the receive timing and downlink channel for monitoring and / or receiving the second message (e.g., Msg B1332).

[0134] Transport block 1342 may include data (e.g., delay-sensitive data), a radio device identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). A base station may send / transmit a second message (e.g., Msg B1332) in response to a first message (e.g., Msg A1331). The second message (e.g., Msg B1332) may include at least one of a preamble identifier, a timing advance command, a power control command, an uplink grant (e.g., radio resource allocation and / or MCS), a radio device identifier (e.g., a UE identifier for conflict resolution), and / or an RNTI (e.g., C-RNTI or TC-RNTI). The wireless device may determine that the two-step random access procedure has been successfully completed, for example, if the preamble identifier of the second message (e.g., Msg B1332) corresponds to or matches the preamble transmitted by the wireless device and / or if the wireless device identifier of the second message (e.g., Msg B1332) corresponds to or matches the wireless device identifier of the first message (e.g., Msg A1331) (e.g., transport block 1342).

[0135] Wireless devices and base stations may exchange control signaling (e.g., control information). Control signaling may be called L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or MAC layer (e.g., layer 2) of the wireless device or base station. Control signaling may include downlink control signaling transmitted from the base station to the wireless device and / or uplink control signaling transmitted from the wireless device to the base station.

[0136] Downlink control signaling may include at least one of the following: downlink scheduling assignments, uplink scheduling grants indicating uplink radio resources and / or transport format, slot format information, preemption instructions, power control commands, and / or any other suitable signaling. A radio device may receive downlink control signaling in a payload transmitted / transmitted by a base station via a PDCCH. The payload transmitted / transmitted via a PDCCH may be called downlink control information (DCI). The PDCCH may be a group-common PDCCH (GC-PDCCH) common to a group of radio devices. The GC-PDCCH may be scrambled by a group-common RNTI.

[0137] A base station may connect one or more cyclic redundancy check (CRC) parity bits to the DCI, for example, to facilitate the detection of transmission errors. The base station may scramble the CRC parity bits with a radio device identifier (or an identifier for a group of radio devices) if the DCI is intended for a radio device (or a group of radio devices). Scrambling the CRC parity bits with an identifier may involve a Modulo-2 addition (or exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a 16-bit value of the RNTI.

[0138] DCIs can be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with scrambled CRC parity bits using a paging RNTI (P-RNTI) may indicate paging information and / or system information change notifications. P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with scrambled CRC parity bits using a system information RNTI (SI-RNTI) may indicate broadcast transmission of system information. SI-RNTI may be predefined as "FFFF" in hexadecimal. A DCI with scrambled CRC parity bits using a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with scrambled CRC parity bits using a cell RNTI (C-RNTI) may indicate unicast transmission of dynamic schedules and / or triggers for random access in PDCCH sequences. A DCI with scrambled CRC parity bits in a temporary cell RNTI (TC-RNTI) may indicate conflict resolution (e.g., Msg3 similar to Msg3 1313 shown in Figure 13A). Other RNTIs configured by the base station for radio devices may include configured scheduling RNTIs (CS RNTIs), transmission power control PUCCH RNTIs (TPC PUCCH-RNTIs), transmission power control PUSCH RNTIs (TPC-PUSCH-RNTIs), transmission power control SRS RNTIs (TPC-SRS-RNTIs), interruption RNTIs (INT-RNTIs), slot formatting indicator RNTIs (SFI-RNTIs), semi-persistent CSI RNTIs (SP-CSI-RNTIs), modulation and coding scheme cell RNTIs (MCS-C RNTIs), and / or similar.

[0139] A base station may transmit / transmit DCI in one or more DCI formats, depending on the purpose and / or content of the DCI. DCI format 0_0 may be used for scheduling PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used for scheduling PDSCH in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide slot format instructions to a group of radio devices. DCI format 2_1 may be used to inform / notify a group of radio devices of a physical resource block and / or OFDM symbol, where a group of radio devices may assume there is no intended transmission to the group of radio devices. DCI format 2_2 may be used for transmitting Transmission Power Control (TPC) commands to PUCCH or PUSCH. DCI format 2_3 may be used for transmitting a group of TPC commands for SRS transmission by one or more radio devices. DCI formats for new features may be defined in future releases. DCI formats may have different DCI sizes or may share the same DCI size.

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

[0141] Figure 14A shows an example of a CORESET configuration. A CORESET configuration may be for a bandwidth portion or any other frequency band. A base station may transmit / transmit DCIs via PDCCHs on one or more control resource sets (CORESETs). A CORESET may contain time-frequency resources that radio devices attempt to decode / try using one or more search spaces. A base station may configure the size and location of a CORESET in a time-frequency domain. A first CORESET 1401 and a second CORESET 1402 may occur or be set / configured in a first symbol in a slot. The first CORESET 1401 may overlap with the second CORESET 1402 in the frequency domain. A third CORESET 1403 may occur or be set / configured in a third symbol in a slot. A fourth CORESET 1404 may occur or be set / configured in a seventh symbol in a slot. A CORESET may have different amounts / numbers of resource blocks in a frequency domain.

[0142] Figure 14B shows an example of CCE-to-REG mapping. CCE-to-REG mapping can be performed for DCI transmissions via CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference adjustment and / or frequency-selective transmission of control channels). A base station may perform different or identical CCE-to-REG mappings with different CORESETs. A CORESET can be associated with a CCE-to-REG mapping (e.g., by an RRC configuration). A CORESET may be configured to have antenna port QCL parameters. The antenna port QCL parameters may indicate DM-RS QCL information for PDCCH reception via the CORESET.

[0143] A base station may transmit one or more RRC messages to a radio device, each containing one or more CORESET and one or more search space set configuration parameters. The configuration parameters may indicate the relationship between the search space set and the CORESET. The search space set may include a set of PDCCH candidates formed by the CCE (e.g., at a given aggregation level). The configuration parameters may indicate at least one of the following: several quantities / numbers of PDCCH candidates monitored at each aggregation level, PDCCH monitoring periodicity and PDCCH monitoring patterns, one or more DCI formats monitored by the radio device, and / or whether the search space set is a common search space set or a radio device-specific search space set (e.g., a UE-specific search space set). The set of CCEs in a common search space set may be predefined and known to the radio device. The set of CCEs in a radio device-specific search space set (e.g., a UE-specific search space set) may be configured, for example, based on the identity of the radio device (e.g., C-RNTI).

[0144] As shown in Figure 14B, a wireless device may determine the time-frequency resources of a CORESET based on one or more RRC messages. A wireless device may determine the CCE-to-REG mapping of a CORESET (e.g., interleaved or non-interleaved, and / or mapping parameters) based, for example, the configuration parameters of a CORESET. A wireless device may determine a certain amount / number (e.g., up to 10) of search space sets configured on / for a CORESET based, for example, one or more RRC messages. A wireless device may monitor a set of PDCCH candidates according to the configuration parameters of a certain search space set. A wireless device may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates from the set of PDCCH candidates according to the monitored DCI format. Monitoring may include the possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the quantity / number of CCEs, the quantity / number of PDCCH candidates in a common search space, and / or the quantity / number of PDCCH candidates in a radio device-specific search space), and decoding the DCI content of one or more PDCCH candidates in a possible (or configured) DCI format. Decoding may be called blind decoding. The radio device may determine that the DCI is valid for the radio device based on (e.g., subsequently or in response to) a CRC check (e.g., a scrambled bit of the CRC parity bit of the DCI that matches the RNTI value). The radio device may process the information contained in the DCI (e.g., scheduling assignments, uplink grants, power control, slot format instructions, downlink preemption, and / or similar).

[0145] Uplink control signaling (e.g., UCI) may be transmitted to the base station. Uplink control signaling may include a HARQ acknowledgment for a received DL-SCH transport block. The radio device may transmit a HARQ acknowledgment based on (e.g., subsequently or in response to) receiving a DL-SCH transport block. Uplink control signaling may include a CSI indicating the channel quality of the physical downlink channel. The radio device may transmit a CSI to the base station. The base station may determine the transmission format parameters for the downlink transmission (e.g., including multi-antenna and beamforming schemes) based on the received CSI. Uplink control signaling may include a scheduling request (SR). The radio device may transmit an SR indicating that uplink data is available for transmission to the base station. The radio device may transmit UCI (e.g., HARQ acknowledgment (HARQ-ACK), CSI report, SR, etc.) via PUCCH or PUSCH. A wireless device may transmit uplink control signaling via PUCCH using one of several PUCCH formats.

[0146] There may be multiple PUCCH formats (e.g., five PUCCH formats). A wireless device may determine the PUCCH format based, for example, on the size of the UCI (e.g., the amount / number of uplink symbols and the amount / number of UCI bits in the UCI transmission). PUCCH format 0 may have the length of one or two OFDM symbols and may contain two or fewer bits. A wireless device may use PUCCH format 0 to transmit / transmit a UCI via a PUCCH resource, for example, when the transmission is via one or two symbols and the amount / number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is 1 or 2. PUCCH format 1 may occupy a certain amount / number of OFDM symbols (e.g., 4 to 14 OFDM symbols) and may contain two or fewer bits. A wireless device may use PUCCH format 1, for example, when the transmission is via four or more symbols and the amount / number of HARQ-ACK / SR bits is 1 or 2. PUCCH format 2 may occupy one or two OFDM symbols and may contain more than two bits. A wireless device may use PUCCH format 2 if, for example, transmission is via one or two symbols and the amount / number of UCI bits is 2 or more. PUCCH format 3 may occupy a certain amount / number of OFDM symbols (e.g., 4 to 14 OFDM symbols) and may contain more than two bits. A wireless device may use PUCCH format 3 if, for example, transmission is four or more symbols, the amount / number of UCI bits is 2 or more, and the PUCCH resource does not contain orthogonal cover codes (OCCs). PUCCH format 4 may occupy a certain amount / number of OFDM symbols (e.g., 4 to 14 OFDM symbols) and may contain more than two bits. A wireless device may use PUCCH format 4 if, for example, transmission is four or more symbols, the amount / number of UCI bits is 2 or more, and the PUCCH resource contains OCCs.

[0147] A base station may transmit / transmit configuration parameters to a radio device of multiple PUCCH resource sets, for example, using RRC messages. Multiple PUCCH resource sets (e.g., up to 4 sets in NR, or up to any other number of sets in other systems) may be configured on the cell's uplink BWP. A PUCCH resource set may be configured to have multiple PUCCH resources, each having a PUCCH resource identified by a PUCCH resource set index, a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a radio device having a certain amount / number (e.g., maximum amount / number) of UCI information bits that can be transmitted / transmitted using one of the multiple PUCCH resources in the PUCCH resource set. When a radio device is configured to have multiple PUCCH resource sets, it may select one of the multiple PUCCH resource sets, for example, based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). A wireless device may select a first PUCCH resource set with a PUCCH resource set index equal to "0" if, for example, the total bit length of the UCI information bits is 2 or less. A wireless device may select a second PUCCH resource set with a PUCCH resource set index equal to "1" if, for example, the total bit length of the UCI information bits is greater than 2 and less than or equal to a first configuration value. A wireless device may select a third PUCCH resource set with a PUCCH resource set index equal to "2" if, for example, the total bit length of the UCI information bits is greater than a first configuration value and less than or equal to a second configuration value. A wireless device may select a fourth PUCCH resource set with a PUCCH resource set index equal to "3" if, for example, the total bit length of the UCI information bits is greater than a second configuration value and less than or equal to a third value (e.g., 1406, 1706, or any other bit amount).

[0148] A wireless device may, for example, determine a PUCCH resource set from multiple PUCCH resource sets, and then determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. A wireless device may, for example, determine a PUCCH resource based on a PUCCH resource indicator in DCI (e.g., in DCI format 1_0 or DCI format 1_1) received over / via PDCCH. An n-bit (e.g., 3-bit) PUCCH resource indicator in DCI may indicate one of several (e.g., 8) PUCCH resources in a PUCCH resource set. A wireless device may, for example, transmit / transmit UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in DCI, based on the PUCCH resource indicator.

[0149] Figure 15A shows an exemplary communication between a wireless device and a base station. The wireless device 1502 and base station 1504 may be part of a communication network, such as the communication network 100 shown in Figure 1A, the communication network 150 shown in Figure 1B, or any other communication network. The communication network may include one or more wireless devices and / or one or more base stations having substantially the same or similar configuration as shown in Figure 15A.

[0150] Base station 1504 may connect radio device 1502 to a core network (not shown) via radio communication over an air interface (or radio interface) 1506. The communication direction from base station 1504 to radio device 1502 over air interface 1506 may be called downlink. The communication direction from radio device 1502 to base station 1504 over air interface may be called uplink. Downlink transmission may be isolated from uplink transmission using, for example, various redundancy schemes (e.g., FDD, TDD, and / or some combination of redundancy techniques).

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

[0152] Data transmitted to the wireless device 1502 may, for example, be processed by the processing system 1508 and then provided / transmitted to the transmission processing system 1510 of the base station 1504. Data transmitted to the base station 1504 may, for example, be processed by the processing system 1518 and then provided / transmitted to the transmission processing system 1520 of the wireless device 1502. The transmission processing systems 1510 and 1520 may implement the OSI functions of layer 1. Layer 1 may include, for example, the PHY layer described in relation to Figures 2A, 2B, 3, and 4A. For transmission processing, the PHY layer may perform, for example, forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to a physical channel, modulation of the physical channel, multiple input multiple output (MIMO) or multi-antenna processing, and / or similar.

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

[0154] The base station 1504 may include multiple antennas (e.g., multiple antenna panels, multiple TRPs, etc.). The wireless device 1502 may include multiple antennas (e.g., multiple antenna panels, etc.). Multiple antennas may be used to implement one or more MIMO or multi-antenna technologies such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmission / reception diversity, and / or beamforming. The wireless device 1502 and / or base station 1504 may have a single antenna.

[0155] Processing systems 1508 and 1518 may be associated with memories 1514 and 1524, respectively. Memories 1514 and 1524 (e.g., one or more non-temporary computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518, respectively, to perform one or more functions (e.g., one or more functions described herein, and other functions of a general computer, processor, memory, and / or other peripheral device). Transmission processing system 1510 and / or reception processing system 1512 may be coupled to memory 1514 and / or another memory (e.g., one or more non-temporary computer-readable media) that stores computer program instructions or code that can be executed to perform one or more of their respective functions. The transmission processing system 1520 and / or the reception processing system 1522 may be coupled to memory 1524 and / or another memory (e.g., one or more non-temporary computer-readable media) that stores computer program instructions or code that can be executed to perform one or more of their respective functions.

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

[0157] Processing system 1508 may be connected to one or more peripheral devices 1516. Processing system 1518 may be connected to one or more peripheral devices 1526. One or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware that provides features and / or functions, such as a speaker, microphone, keypad, display, touchpad, power supply, satellite transceiver, Universal Serial Bus (USB) port, hands-free headset, frequency modulation (FM) radio unit, media player, internet browser, electronic control unit (e.g., for a vehicle), and / or one or more sensors (e.g., accelerometer, gyroscope, temperature sensor, radar sensor, lidar sensor, ultrasonic sensor, light sensor, camera, and / or similar). Processing system 1508 and / or processing system 1518 may receive input data (e.g., user input data) from one or more peripheral devices 1516 and / or one or more peripheral devices 1526 and / or provide output data (e.g., user output data) to them. The processing system 1518 of the wireless device 1502 may be configured to receive power from a power source and / or distribute power to other components of the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 may be connected to a global positioning system (GPS) chipset 1517. The processing system 1518 may be connected to a global positioning system (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 may be configured to determine and provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0158] Figure 15B shows exemplary elements of a computing device that may be used to implement any of the various devices described herein, including, for example, base stations 160A, 160B, 162A, 162B, 220, 1210, 1302, 1710, and / or 1910, radio devices 106, 156A, 156B, 210, 1205, 1301, and / or 1705, NCR nodes 1720, 180, and / or 1905, or any other base stations, radio devices, AMFs, UPFs, network devices, or computing devices described herein. The computing device 1530 may include one or more processors 1531 capable of executing instructions stored in random access memory (RAM) 1533, removable media 1534 (such as a Universal Serial Bus (USB) drive, a compact disk (CD) or digital multipurpose disk (DVD), or a floppy disk drive), or any other desired storage medium. Instructions may also be stored in a connected (or internal) hard drive 1535. The computing device 1530 may also include a security processor (not shown) capable of executing instructions for one or more computer programs to monitor processes running on the processor 1531 and any processes requesting access to any hardware and / or software components of the computing device 1530 (e.g., ROM 1532, RAM 1533, removable media 1534, hard drive 1535, device controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). The computing device 1530 may include one or more output devices such as a display 1536 (e.g., a screen, display device, monitor, television, etc.) and one or more output device controllers 1537 such as a video processor. There may also be one or more user input devices 1538 such as a remote control, keyboard, mouse, touchscreen, microphone, etc.The computing device 1530 may also include one or more network interfaces, such as a network interface 1539, which may be a wired interface, a wireless interface, or a combination of the two. The network interface 1539 may provide an interface for the computing device 1530 to communicate with a network 1540 (e.g., a RAN, or any other network). The network interface 1539 may include a modem (e.g., a cable modem), and the external network 1540 may include a communication link, an external network, a home network, a provider's wireless, coaxial, fiber, or hybrid fiber / coaxial distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, the computing device 1530 may include a location detection device, such as a global positioning system (GPS) microprocessor 1541, which may be configured to receive and process global positioning signals and determine the geographical location of the computing device 1530 with possible assistance from an external server and antenna.

[0159] Figure 15B may show a hardware configuration, but the components shown can also be implemented as software. Modifications can be made to add, remove, combine, or split components of computing device 1530, as desired. Furthermore, components can be implemented using basic computing devices and components, and the same components (e.g., processor 1531, ROM storage 1532, display 1536, etc.) can be used to implement any of the other computing devices and components described herein. For example, various components described herein can be implemented using a computing device having components such as a processor that executes computer-executable instructions stored in a computer-readable medium, as shown in Figure 15B. Some or all entities described herein may be software-based and may coexist on a common physical platform (e.g., a requesting entity may be a separate software process and program from a dependent entity, both of which may run as software on a common computing device).

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

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

[0162] Figure 16C shows an exemplary structure of downlink transmission. Processing of the baseband signal representing the physical downlink channel may include / implement one or more functions. These one or more functions may include scrambling of encoded bits in a codeword to be transmitted / transmitted on / through the physical channel, modulating the scrambled bits to generate a complex-valued modulation symbol, mapping the complex-valued modulation symbol to one or more transmission layers, precoding of the complex-valued modulation symbol on the layer for transmission over antenna ports, mapping of the complex-valued modulation symbol to resource elements at antenna ports, generation of a complex-valued time-domain OFDM signal per antenna port, and / or similar. These functions are examples, and other mechanisms for downlink transmission may be implemented.

[0163] Figure 16D shows an exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal to an antenna port or any other signal. Filtering may be performed / applied, for example, before transmission.

[0164] A wireless device may receive one or more messages (e.g., RRC messages) from a base station that contain configuration parameters for multiple cells (e.g., a primary cell, one or more secondary cells). The wireless device may communicate with at least one base station (e.g., two or more base stations in a dual connection) via multiple cells. One or more messages (e.g., as part of configuration parameters) may contain parameters for the PHY, MAC, RLC, PCDP, SDAP, and RRC layers for configuring the wireless device. Configuration parameters may include parameters for configuring PHY and MAC layer channels, bearers, etc. Configuration parameters may include parameters indicating timer values ​​for the PHY, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels.

[0165] A timer may start running, for example, after being started (e.g., immediately after starting), and continue running until it is stopped or expires. A timer may be started when it is not running, or restarted when it is running. A timer may be associated with a value (e.g., a timer may start or restart from a certain value, or start from zero and expire after reaching a value (e.g., immediately after reaching it)). The duration of a timer may not be updated, for example, until the timer stops or expires (e.g., due to a BWP switch). A timer may be used to measure the time duration / window of a process. With respect to implementations and / or procedures relating to one or more timers or other parameters, it will be understood that there may be multiple ways to implement one or more timers or other parameters. One or more of the multiple ways of implementing a timer may be used to measure the time duration / window of a procedure. A random access response window timer may be used to measure the time window for receiving a random access response. The time difference between two timestamps may be used, for example, instead of starting a random access response window timer and determining the timer's expiration. The process for measuring the time window may be restarted, for example, when the timer is restarted. Other exemplary implementations may be configured / provided for restarting the measurement of the time window.

[0166] A wireless device may receive one or more messages containing one or more configuration parameters of a cell. For example, a wireless device may receive one or more messages containing one or more configuration parameters of a cell from a base station.

[0167] One or more configuration parameters may indicate at least two discontinuous transmissions (DTXs) ​​for a cell to save energy. For example, the first of the at least two DTXs may be for a first TRP (e.g., TRP1 as described herein in Figures 21, 22, and 23), and the second of the at least two DTXs may be for a second TRP (e.g., TRP2 as described herein in Figures 21, 22, and 23).

[0168] A wireless device does not have to receive downlink reception (e.g., PDSCH reception, CSI-RS, etc.). A wireless device does not have to receive downlink reception (e.g., PDSCH reception, CSI-RS, etc.) if, for example, the cell's DTX is inactive during its inactive time, duration, and / or period. This may be inefficient if, for example, a downlink reception associated with two TCI states (or two received beams) temporally overlaps with the inactive time, duration, and / or period of the first DTX (e.g., the first TRP is off), but the downlink reception temporally overlaps with the active time, duration, and / or period of the second DTX (e.g., the second TRP is on), or vice versa. Not receiving downlink reception may be inefficient. Not receiving downlink reception may be inefficient if, for example, the second TRP is on during the inactive time, duration, and / or period of the first DTX. This may increase data communication latency.

[0169] Downlink reception may be enhanced in association with at least two TCI states during an inactive time, duration, and / or period of at least two DTXs. A wireless device may receive downlink reception based on one of at least two TCI states when it is in an inactive time, duration, and / or period of at least two DTXs. For example, a wireless device may receive downlink reception based on a first TCI state of at least two TCI states when it is in an inactive time, duration, and / or period of a second DTX of at least two DTXs. A wireless device may receive downlink reception based on a second TCI state of at least two TCI states when it is in an inactive time, duration, and / or period of a first DTX of at least two DTXs. The first and second TCI states may be different, for example. This may reduce data communication latency.

[0170] A wireless device may not have to support dynamic switching between a single TRP and multiple TRPs for downlink reception (e.g., PDSCH reception). A wireless device may not have to receive downlink reception based on one of at least two TCI states if, for example, one of at least two DTX is inactive for a certain time, duration, and / or period. A base station may not have to turn off one of the TRPs that reduces energy consumption.

[0171] Downlink reception associated with at least two TCI states during an inactive time, duration, and / or period of at least two DTXs may be enhanced. Downlink reception associated with at least two TCI states during an inactive time, duration, and / or period of at least two DTXs may be enhanced, for example, if the wireless device does not support dynamic switching between a single TRP and multiple TRPs. If the wireless device is in an inactive time, duration, and / or period of at least two DTXs, and the wireless device supports dynamic switching between a single TRP and multiple TRPs, it may receive downlink reception based on one of at least two TCI states. If the wireless device is in an inactive time, duration, and / or period of at least two DTXs, and the wireless device does not support dynamic switching between a single TRP and multiple TRPs, it may receive downlink reception based on at least two TCI states. If a wireless device is in an inactive period, duration, and / or duration of at least one of two DTXs, it may not receive a downlink reception if the wireless device does not support dynamic switching between a single TRP and multiple TRPs.

[0172] A wireless device may receive (e.g., from a base station or network) one or more messages (e.g., RRC messages, RRC reconfiguration messages) containing one or more configuration parameters. One or more configuration parameters may include one or more MAC cell group configuration parameters (e.g., MAC-CellGroupConfig) for a cell group containing a cell. One or more MAC cell group configuration parameters may include one or more cell discontinuous transmission (DTX) configuration parameters (e.g., celldtx-Config) used to configure and / or indicate the cell DTX of the cell. One or more MAC cell group configuration parameters may include one or more cell discontinuous receive (DRX) configuration parameters (e.g., celldrx-Config) used to configure and / or indicate the cell DRX of the cell. One or more configuration parameters may include one or more serving cell configuration parameters (e.g., ServingCellConfig) for the cell. One or more serving cell configuration parameters may include one or more cell DTX configuration parameters (e.g., celldtx-Config) used to configure and / or indicate the cell DTX of the cell. One or more serving cell configuration parameters may include one or more cell DRX configuration parameters (e.g., celldrx-Config) used to configure and / or indicate the cell's cell DRX.

[0173] A cell DTX may be implicitly activated when configured by a base station. A cell DTX may be implicitly activated when configured by a base station, for example, based on the transmission (e.g., transmission) of one or more cell DTX configuration parameters. A cell DTX may be implicitly activated by a radio device when configured by a base station, for example, based on the reception of one or more cell DTX configuration parameters. One or more cell DTX configuration parameters may indicate a duration timer for the cell DTX (e.g., celldtx-onDurationTimer). One or more cell DTX configuration parameters may indicate an offset relative to the cycle start of the cell DTX (e.g., celldtx-CycleStartOffset). One or more cell DTX configuration parameters may indicate a slot offset for the cell DTX (e.g., celldtx-SlotOffset). One or more cell DTX configuration parameters may include joint cell DTX-DRX configuration parameters (e.g., jointCellDTXDRXconfig). A wireless device may use one or more cell DTX configuration parameters for cell DRX, for example, if the joint cell DTX-DRX configuration parameter is set to true. A wireless device may use a cell DRX configuration with the same parameters as CellDTX-Config, for example, if the joint cell DTX-DRX configuration parameter is set to true. Cell DTX may be deactivated by a wireless device, for example, by releasing one or more cell DTX configuration parameters.

[0174] A cell DRX may be implicitly activated when configured by a base station. A cell DRX may be implicitly activated when configured by a base station, for example, by transmitting (e.g., transmitting) one or more cell DRX configuration parameters. A cell DRX may be implicitly activated by a radio device when configured by a base station, for example, by receiving one or more cell DRX configuration parameters. One or more cell DRX configuration parameters may indicate a duration timer for the cell DRX (e.g., celldrx-onDurationTimer). One or more cell DRX configuration parameters may indicate an offset relative to the cycle start of the cell DRX (e.g., celldrx-CycleStartOffset). One or more cell DRX configuration parameters may indicate a slot offset for the cell DRX (e.g., celldrx-SlotOffset). A cell DRX may be deactivated by a radio device, for example, by releasing one or more cell DRX configuration parameters.

[0175] The offset to the start of the cycle may be common to both cell DTX and cell DRX. The offset to the start of the cycle may be common to both cell DTX and cell DRX if, for example, one or more configuration parameters include both one or more cell DTX configuration parameters and one or more cell DRX configuration parameters. The offset to the start of the cycle for cell DRX may be signaled by one or more cell DTX configuration parameters. The offset to the start of the cycle for cell DTX may indicate the offset to the start of the cycle for cell DRX if, for example, the joint cell DTX-DRX configuration parameter is set to true. The offset to the start of the cycle for cell DTX may be the offset to the start of the cycle for both cell DTX and cell DRX if, for example, the joint cell DTX-DRX configuration parameter is set to true.

[0176] The duration timer may be common to both cell DTX and cell DRX. The duration timer may be common to both cell DTX and cell DRX if, for example, one or more configuration parameters include both one or more cell DTX configuration parameters and one or more cell DRX configuration parameters. The duration timer of cell DRX may be signaled by one or more cell DTX configuration parameters. The duration timer of cell DTX may indicate the duration timer of cell DRX if, for example, the joint cell DTX-DRX configuration parameter is set to true. The duration timer of cell DTX may be the duration timer for both cell DTX and cell DRX if, for example, the joint cell DTX-DRX configuration parameter is set to true.

[0177] The slot offset may be common to both cell DTX and cell DRX. The slot offset may be common to both cell DTX and cell DRX if, for example, one or more configuration parameters include both one or more cell DTX configuration parameters and one or more cell DRX configuration parameters. The slot offset of cell DRX may be signaled by one or more cell DTX configuration parameters. The slot offset of cell DTX may indicate the slot offset of cell DRX, for example, if the joint cell DTX-DRX configuration parameter is set to true. The slot offset of cell DTX may be the slot offset of both cell DTX and cell DRX, for example, if the joint cell DTX-DRX configuration parameter is set to true.

[0178] To facilitate the reduction of downlink transmission or uplink reception activity time at a base station (e.g., gNB), radio devices may be configured by the base station to have a cell DTX and / or DRX (e.g., by CellDTX-Config, CellDRX-Config). The cell DTX and / or DRX may have a periodic cell DTX and / or DRX pattern (i.e., active and inactive periods). The periodic cell DTX and / or DRX pattern may be common to one or more radio devices configured to have a cell DTX and / or DRX within a cell. The periodic cell DTX pattern and the periodic cell DRX pattern may be configured and / or activated separately. A wireless device may not monitor PDCCH or SPS opportunities unless there are pending retransmissions, or the random access timer and / or window (e.g., ra-ResponseWindow, ra-ContentionResolutionTimer) is running, or an SR is being transmitted and pending, for example, when a cell DTX is configured and activated for a cell and the wireless device is in the inactive duration of the cell DTX. A wireless device may not transmit on / through a configured grant (CG) resource, or transmit an SR, for example, when a cell DRX is configured and activated for a cell and the wireless device is in the inactive duration of the cell DRX. Cell DTX and / or DRX may only apply to wireless devices in the RRC_CONNECTED state. Cell DTX and / or DRX may not affect, at least, random access procedures, SSB transmissions, paging, and broadcasting of system information.

[0179] Cell DTX and / or DRX may be activated or deactivated by RRC signaling or Layer 1 (L1) group common signaling (e.g., DCI). One or more configuration parameters may include a parameter indicating whether the activation or deactivation of Cell DTX and / or DRX is based on RRC signaling or L1 group common signaling. A base station and / or radio device may activate or deactivate Cell DTX and / or DRX based on RRC signaling, for example, if the parameter is set to a first value (e.g., 0, "RRC"). A radio device may activate Cell DTX and / or DRX based on receiving RRC signaling (e.g., CellDTX-Config, CellDRX-Config). A base station and / or radio device may activate or deactivate Cell DTX and / or DRX based on L1 group common signaling, for example, if the parameter is set to a second value (e.g., 1, "DCI", or "L1"). A wireless device may activate the cell DTX and / or DRX based on receiving DCI (e.g., DCI format 2_9). A wireless device may not activate the cell DTX and / or DRX based on receiving RRC signaling (e.g., CellDTX-Config, CellDRX-Config) if, for example, the parameter is set to a second value. A wireless device may not activate the cell DTX and / or DRX until it receives DCI (e.g., DCI format 2_9) if, for example, the parameter is set to a second value.

[0180] Cell DTX and / or DRX may be characterized by active duration and / or cycle. Active duration may be the duration during which a radio device can wait and / or monitor for receiving a PDCCH or SPS opportunity and transmitting (e.g., transmitting) an SR or CG. Transmission and / or reception of PDCCH, SPS, SR, and CG by the base station may be unaffected for network energy conservation purposes during the active duration. Cycle may specify a periodic repetition of the active duration, followed by a period of inactive duration. Active duration and / or cycle parameters may be common to both cell DTX and cell DRX if both are configured.

[0181] The network can ensure that when a base station recognizes the presence of an emergency call or public safety-related service (e.g., MPS or MCS), it does not affect the emergency call or public safety-related service (e.g., the base station may release or deactivate the cell DTX and / or DRX). The base station can ensure that there is at least partial overlap between the duration of the wireless device's connection mode DRX and the active duration of the cell DTX and / or DRX (e.g., the periodicity of the wireless device's connection mode DRX is a multiple of the periodicity of the cell DTX and / or DRX).

[0182] If a wireless device is located within a cell DTX and receives a DCI that schedules a downlink reception (e.g., PDSCH, aperiodic CSI-RS), the wireless device may receive the downlink reception regardless of whether the downlink reception overlaps with the active time, period, and / or duration, or inactive time, period, and / or duration, of the cell DTX (e.g., being at that time, within that time, at that time, etc.). The DCI may include dynamic authorization for downlink reception. After a downlink reception, the wireless device may, for example, transmit (e.g., transmit) HARQ-ACK information feedback for the downlink reception, regardless of whether the transmission of HARQ-ACK information overlaps with the active time, period, and / or duration, or inactive time, period, and / or duration, of the cell DRX (e.g., being at that time, within that time, at that time, etc.).

[0183] If a radio device is located within a cell DRX and receives a DCI scheduling an uplink transmission (e.g., PUSCH, PUCCH, aperiodic SRS), the radio device may transmit (e.g., transmit) the uplink transmission regardless of whether the uplink transmission overlaps with the active time, period, and / or duration, or inactive time, period, and / or duration, of the cell DRX (e.g., being in that time, within that time, at that time, etc.). The DCI may include dynamic authorization for the uplink transmission. The radio device may, for example, receive a PDCCH reception (e.g., DCI, response to / from the uplink transmission) from the base station after an uplink transmission, regardless of whether the transmission of the PDCCH reception overlaps with the active time, period, and / or duration, or inactive time, period, and / or duration, of the cell DRX (e.g., being in that time, within that time, at that time, etc.). A wireless device may, for example, monitor the PDCCH for DCI from the base station (or for / responds to the uplink transmission) regardless of whether the transmission of the PDCCH with DCI after the uplink transmission overlaps with the active time, period, and / or duration, or inactive time, period, and / or duration of the cell DTX (e.g., in that time, within that time, at that time, etc.).

[0184] The inactivity time, period, and / or duration of cell DTX may include time other than the active time, period, and / or duration of cell DTX. The inactivity time, period, and / or duration of cell DRX may include time other than the active time, period, and / or duration of cell DRX.

[0185] A wireless device may receive one or more messages (e.g., RRC messages) from a base station. One or more messages may constitute and / or indicate a periodic cell DTX and / or cell DRX pattern (i.e., active and inactive periods) for the cell's cell DTX and / or cell DRX (e.g., serving cell, non-serving cell, candidate cell, target cell, etc.).

[0186] Cell DTX, or Cell DTX functionality, can control the monitoring activity of PDCCH and configured downlink assignments (e.g., SPS PDSCH) by a wireless device in RRC_CONNECTED mode. A wireless device can use Cell DTX or Cell DTX operation to monitor PDCCH and configured downlink assignments through a cell for a cell configured to have and activated by Cell DTX.

[0187] A wireless device may monitor the PDCCH and configured downlink assignments using the cell DTX or cell DTX operation for all activated cells (e.g., activated serving cells) configured to have a cell DTX. A wireless device may monitor the PDCCH and configured downlink assignments using the cell DTX or cell DTX operation for each activated cell (e.g., each activated serving cell) configured to have a cell DTX and activated by it.

[0188] Cell DRX or Cell DRX functionality can control the transmission activity of scheduling requests (SRs) and configured uplink permissions by the radio device in RRC_CONNECTED. The radio device may transmit scheduling requests and configured uplink permissions through a cell using Cell DRX, or Cell DRX operation for cells configured to have and activated by Cell DRX. The radio device may transmit scheduling requests and configured uplink permissions using Cell DRX (or Cell DRX operation) for all activated cells (e.g., activated serving cells) configured to have Cell DRX. The radio device may transmit scheduling requests and configured uplink permissions using Cell DRX or Cell DRX operation for each activated cell (e.g., each activated serving cell) configured to have and activated by Cell DRX.

[0189] One or more messages (e.g., RRC messages) may control a Cell DTX or Cell DTX operation by configuring, indicating, and / or including one or more Cell DTX configuration parameters (e.g., CellDTX-Config): celldtx-onDurationTimer: the active duration at the start of a Cell DTX cycle, or a Cell DTX cycle, a Cell DTX cycle, or a subframe that starts a Cell DTX cycle; celldtx-StartOffset, celldtx-SlotOffset: the delay time before starting a Cell DTX duration timer (e.g., celldtx-onDurationTimer); celldtx-Cycle: the duration of a Cell DTX cycle, or parameters during a Cell DTX cycle duration.

[0190] One or more messages (e.g., RRC messages) may control CellDRX or CellDRX operation by configuring, indicating, and / or including one or more CellDRX configuration parameters (e.g., CellDRX-Config): celldrx-onDurationTimer: the active duration at the start of a CellDRX cycle, or celldrx-StartOffset: defining a CellDRX cycle, a CellDRX cycle, or a subframe that starts a CellDRX cycle, celldrx-SlotOffset: the delay time before starting a CellDRX duration timer (e.g., celldrx-onDurationTimer), celldrx-Cycle: the duration of a CellDRX cycle, or parameters during a CellDRX cycle duration.

[0191] The active time, duration, and / or duration of the cell DTX, or the active time, duration, and / or duration of the cell DTX, may include time if, for a cell, one or more configuration parameters (e.g., CellDTX-Config) indicate and / or constitute the cell DTX of the cell (e.g., a serving cell), if celldtx-onDurationTimer is running on the cell, or if a cell DTX deactivation instruction (e.g., DCI format 2_9 or RRC signaling) is received by the wireless device.

[0192] The active time, duration, and / or duration of the cell DRX (or cell DRX active time, duration, and / or duration) may include time if, for a cell, one or more configuration parameters (e.g., CellDRX-Config) indicate and / or constitute the cell DRX of the cell (e.g., a serving cell), if celldrx-onDurationTimer is running on the cell, or if a cell DRX deactivation instruction (e.g., DCI format 2_9 or RRC signaling) is received by the wireless device.

[0193] A wireless device may, based on receiving a cell DTX activation instruction for the cell's cell DTX (e.g., by DCI format 2_9 or RRC signaling), start a duration timer for the cell (e.g., celldtx-onDurationTimer) after a slot offset (e.g., celldtx-SlotOffset) from the start of the subframe.

[0194] A wireless device may, based on receiving an instruction indicating the activation of the cell's cell DTX (e.g., by DCI format 2_9 or RRC signaling), start a duration timer for the cell (e.g., celldtx-onDurationTimer) after a slot offset (e.g., celldtx-SlotOffset) from the start of the subframe.

[0195] If the wireless device is operating, it may stop a duration timer (e.g., celldtx-onDurationTimer) based on receiving a cell DTX deactivation instruction for the cell's cell DTX (e.g., by DCI format 2_9 or RRC signaling).

[0196] If the wireless device is operating, it may stop a duration timer (e.g., celldtx-onDurationTimer) based on receiving an instruction (e.g., by DCI format 2_9 or RRC signaling) indicating the deactivation of the cell's cell DTX.

[0197] A wireless device may, based on receiving a cell DRX activation instruction for the cell's cell DRX (e.g., by DCI format 2_9 or RRC signaling), start a duration timer for the cell (e.g., celldrx-onDurationTimer) after a slot offset (e.g., celldrx-SlotOffset) from the start of the subframe.

[0198] A wireless device may, based on receiving an instruction indicating the activation of the cell's cell DRX (e.g., by DCI format 2_9 or RRC signaling), start a duration timer for the cell (e.g., celldrx-onDurationTimer) after a slot offset (e.g., celldrx-SlotOffset) from the start of the subframe.

[0199] If the wireless device is operating, it may stop a duration timer (e.g., celldrx-onDurationTimer) based on receiving a cell DRX deactivation instruction (e.g., by DCI format 2_9 or RRC signaling) to the cell's cell DRX.

[0200] If the wireless device is operating, it may stop a duration timer (e.g., celldrx-onDurationTimer) based on receiving an instruction (e.g., by DCI format 2_9 or RRC signaling) indicating the deactivation of the cell's cell DRX.

[0201] The MAC layer and / or entities of a wireless device do not need to instruct the physical layer and / or entities of the wireless device to receive a transport block on the DL-SCH in accordance with a configured downlink assignment (e.g., SPS) if the cell is not in the active time, period, and / or duration of the cell DTX, or if the cell is not in the active period of the cell DTX, or if the cell is in the inactive time, period, and / or duration of the cell DTX.

[0202] The MAC layer and / or entities of a wireless device may instruct the physical layer and / or entities of the wireless device to receive a transport block on the DL-SCH in accordance with a configured downlink assignment (e.g., SPS) if the cell is in the active time, period, and / or duration of the cell DTX, or if the cell is in the active period of the cell DTX, or if the cell is not in the inactive time, period, and / or duration of the cell DTX.

[0203] The MAC layer and / or entities of a wireless device do not have to indicate the presence of any configured downlink assignment, and do not have to deliver stored HARQ information to the HARQ entity if the cell is not in the active time, period, and / or duration of the cell DTX, or if the cell is not in the active period of the cell DTX, or if the cell is in the inactive time, period, and / or duration of the cell DTX.

[0204] The MAC layer and / or entities of a wireless device may indicate the presence of a configured downlink assignment and may deliver stored HARQ information to the HARQ entity if the cell is in the active time, period, and / or duration of the cell DTX, or if the cell is in the active period of the cell DTX, or if the cell is not in the inactive time, period, and / or duration of the cell DTX.

[0205] A wireless device does not need to monitor PDCCH for an RNTI if the cell is not within the active time, period, and / or duration of the cell DTX, or if the cell is not within the active period of the cell DTX, or if the cell is within the inactive time, period, and / or duration of the cell DTX. A wireless device does not need to monitor PDCCH for DCI scrambled with an RNTI. An RNTI may include, for example, at least one of C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SLCS-RNTI, and SL semi-persistent scheduling V-RNTI.

[0206] The wireless device may monitor the PDCCH for RNTI if drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is running on at least one cell in the DRX group, and if a cell in the DRX group is not within the active time, period, and / or duration of cell DTX, if the cell is not within the active period of cell DTX, or if the cell is within the inactive time, period, and / or duration of cell DTX.

[0207] The wireless device does not need to monitor PDCCH for RNTI if drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is not running on a cell in the DRX group, and if a cell in the DRX group is not within the active time, period, and / or duration of cell DTX, if the cell is not within the active period of cell DTX, or if the cell is within the inactive time, period, and / or duration of cell DTX.

[0208] The wireless device may monitor the PDCCH for RNTI if ra-ContentionResolutionTimer, ra-ResponseWindow, or msgB-ResponseWindow is running, and if the cell is not within the active time, period, and / or duration of the cell DTX, or if the cell is not within the active period of the cell DTX, or if the cell is within the inactive time, period, and / or duration of the cell DTX.

[0209] The wireless device does not need to monitor the PDCCH for RNTI if ra-ContentionResolutionTimer, ra-ResponseWindow, and msgB-ResponseWindow are not running, and if the cell is not within the active time, period, and / or duration of the cell DTX, or if the cell is not within the active period of the cell DTX, or if the cell is within the inactive time, period, and / or duration of the cell DTX.

[0210] A wireless device may monitor the PDCCH for RNTI based on whether the cell is not within the active time, period, and / or duration of the cell DTX, whether the cell is not within the active period of the cell DTX, or whether the cell is within the inactive time, period, and / or duration of the cell DTX, whether the scheduling request (e.g., in PUCCH) has been transmitted (e.g., transmitted) and / or whether the scheduling request is pending.

[0211] The wireless device may monitor the PDCCH for RNTI if a scheduling request is transmitted by the wireless device (e.g., over PUCCH) and / or the scheduling request is pending, if the cell is not within the active time, period, and / or duration of the cell DTX, if the cell is not within the active period of the cell DTX, or if the cell is within the inactive time, period, and / or duration of the cell DTX.

[0212] A wireless device does not need to monitor PDCCH for RNTI if the cell is not within the active time, period, and / or duration of the cell DTX (or if the cell is not within the active period of the cell DTX, or if the cell is within the inactive time, period, and / or duration of the cell DTX), does not send a scheduling request (e.g., in PUCCH), and / or if the scheduling request is not pending.

[0213] A wireless device does not need to monitor the PDCCH for RNTI if a scheduling request is not transmitted by the wireless device (e.g., over PUCCH) and / or the scheduling request is not pending, if the cell is not within the active time, period, and / or duration of the cell DTX, if the cell is not within the active period of the cell DTX, or if the cell is within the inactive time, period, and / or duration of the cell DTX.

[0214] The wireless device may monitor the PDCCH for the RNTI based on the fact that it does not receive a DCI indicating a new transmission addressed to the wireless device's C-RNTI, or the wireless device's MAC entity, if the cell is not within the active time, period, and / or duration of the cell DTX, or if the cell is within the inactive time, period, and / or duration of the cell DTX, after successfully receiving a random access response for / for a non-conflict random access procedure. The wireless device does not have to select a random access preamble for a non-conflict random access procedure from one or more random access preambles used and / or configured for a conflict-based random access procedure.

[0215] The wireless device does not need to monitor the PDCCH for the RNTI based on receiving a DCI indicating a new transmission addressed to the wireless device's C-RNTI, or the wireless device's MAC entity, if the cell is not within the active time, period, and / or duration of the cell DTX, or if the cell is within the inactive time, period, and / or duration of the cell DTX, after successfully receiving a random access response for / for a non-conflict random access procedure. The wireless device does not need to select a random access preamble for a non-conflict random access procedure from one or more random access preambles used and / or configured for a conflict-based random access procedure.

[0216] The MAC layer and / or entities of a wireless device do not need to instruct the physical layer and / or entities of the wireless device to send a scheduling request (e.g., transmit) on the PUCCH resource if the cell is not in the active time, period, and / or duration of the cell DRX, if the cell is not in the active period of the cell DRX, or if the cell is in the inactive time, period, and / or duration of the cell DRX.

[0217] The MAC layer and / or entities of the wireless device may instruct the physical layer and / or entities of the wireless device to send a scheduling request (e.g., transmit) on the PUCCH resource if the cell is in the active time, period, and / or duration of the cell DRX, if the cell is in the active period of the cell DRX, or if the cell is not in the inactive time, period, and / or duration of the cell DRX.

[0218] The wireless device may not increment the SR counter for pending SRs if the cell is not within the active time, period, and / or duration of the cell DRX, or if the cell is not within the active period of the cell DRX, or if the cell is within the inactive time, period, and / or duration of the cell DRX.

[0219] A wireless device may increment an SR counter for pending SRs based on transmitting (e.g., transmitting) an SR if, for example, the cell is within the active time, period, and / or duration of the cell DRX, or if the cell is within the active period of the cell DRX, or if the cell is not within the inactive time, period, and / or duration of the cell DRX.

[0220] A wireless device does not need to start the sr-ProhibitTimer for a pending SR if the cell is not within the active time, period, and / or duration of the cell DRX, or if the cell is not within the active period of the cell DRX, or if the cell is within the inactive time, period, and / or duration of the cell DRX.

[0221] A wireless device may, for example, initiate an sr-ProhibitTimer for pending SRs based on transmitting an SR (e.g., transmission) if the cell is within the active time, period, and / or duration of the cell DRX, if the cell is within the active period of the cell DRX, or if the cell is not within the inactive time, period, and / or duration of the cell DRX.

[0222] If a cell is not in the active time, period, and / or duration of the cell DRX, if the cell is in the active period of the cell DRX, or if the cell is not in the inactive time, period, and / or duration of the cell DRX, the MAC layer and / or entities of the wireless device may not have to deliver the configured uplink grant and associated HARQ information to the HARQ entity.

[0223] The MAC layer and / or entities of a wireless device may deliver configured uplink authorization and associated HARQ information to the HARQ entity when the cell is in the active time, period, and / or duration of the cell DRX, when the cell is in the active period of the cell DRX, or when the cell is not in the inactive time, period, and / or duration of the cell DRX.

[0224] The MAC layer and / or entities of a wireless device may not need to obtain a MAC PDU to transmit (e.g., transmit) for configured uplink authorization from the multiplexing and assembly entities if the cell is not during the active time, period, and / or duration of the cell DRX, if the cell is in the active period of the cell DRX, or if the cell is not during the inactive time, period, and / or duration of the cell DRX.

[0225] The MAC layer and / or entities of a wireless device may obtain MAC PDUs to transmit (e.g., transmit) for configured uplink authorization from the multiplexing and assembly entities when the cell is in the active time, period, and / or duration of the cell DRX, when the cell is in the active period of the cell DRX, or when the cell is not in the inactive time, period, and / or duration of the cell DRX.

[0226] The MAC layer and / or entities of a wireless device do not need to instruct the HARQ process associated with the configured uplink authorization to trigger a new transmission or retransmission if the cell is not in the active time, period, and / or duration of the cell DRX, if the cell is not in the active period of the cell DRX, or if the cell is in the inactive time, period, and / or duration of the cell DRX.

[0227] The MAC layer and / or entities of a wireless device may instruct the HARQ process associated with the configured uplink authorization to trigger a new transmission or retransmission if the cell is in the cell's active time, period, and / or duration, if the cell is in the cell DRX active period, or if the cell is not in the cell DRX's inactive time, period, and / or duration.

[0228] A wireless device may not start or restart configuredGrantTimer if configured, and if the cell is not within the active time, period, and / or duration of the cell DRX, or if the cell is not within the active period of the cell DRX, or if the cell is within the inactive time, period, and / or duration of the cell DRX. A wireless device may start or restart configuredGrantTimer if configured, and if the cell is within the active time, period, and / or duration of the cell DRX, or if the cell is not within the inactive time, period, and / or duration of the cell DRX. A wireless device may not start or restart cg-RetransmissionTimer if configured, and if the cell is not within the active time, period, and / or duration of the cell DRX, or if the cell is not within the inactive time, period, and / or duration of the cell DRX. The wireless device may start or restart the cg-RetransmissionTimer if configured, and if the cell is within the active time, period, and / or duration of the cell DRX, if the cell is within the active period of the cell DRX, or if the cell is not within the inactive time, period, and / or duration of the cell DRX.

[0229] A radio device configured to have a cell DTX (e.g., celldtx-Config) and activated by the cell DTX cannot be expected to receive periodic CSI-RS and / or semi-persistent CSI-RS configured with a CSI report configuration (e.g., CSI-ReportConfig) associated with a higher-layer parameter reportQuantity that includes at least a rank indicator (RI) during the inactivity time, period, and / or duration of the cell DTX. A base station does not have to transmit (e.g., transmit) periodic CSI-RS and / or semi-persistent CSI-RS configured with a CSI report configuration (e.g., CSI-ReportConfig) associated with a higher-layer parameter reportQuantity that includes at least a rank indicator (RI) to a radio device configured to have a cell DTX (e.g., celldtx-Config) and activated by the cell DTX during the inactivity time, period, and / or duration of the cell DTX.

[0230] A radio device configured to have a cell DTX (e.g., celldtx-Config) and activated by the cell DTX can expect to receive periodic CSI-RS and / or semi-persistent CSI-RS configured with a CSI report configuration (e.g., CSI-ReportConfig) associated with a higher-layer parameter reportQuantity that includes at least a rank indicator (RI), during the active time, period, and / or duration of the cell DTX. A base station can transmit (e.g., transmit) periodic CSI-RS and / or semi-persistent CSI-RS to a radio device configured to have a cell DTX (e.g., celldtx-Config) and activated by the cell DTX, during the active time, period, and / or duration of the cell DTX, configured with a CSI report configuration (e.g., CSI-ReportConfig) associated with a higher-layer parameter reportQuantity that includes at least a rank indicator (RI).

[0231] A wireless device configured to have a cell DRX (e.g., celldrx-Config) and activated by the cell DRX cannot be expected to transmit (e.g., transmit) periodic SRS and / or semi-persistent SRS for channel acquisition when the cell DRX is inactive. A wireless device configured to have a cell DRX (e.g., celldrx-Config) and activated may transmit (e.g., transmit) SRS for positioning when the cell DRX is inactive. SRS transmission for positioning may not be affected by the cell DRX or cell DRX operation when the cell DRX is inactive.

[0232] A base station may not receive periodic SRS and / or semi-persistent SRS for channel acquisition from a radio device that has been activated by the cell DRX (e.g., celldrx-Config) during the inactive time, period, and / or duration of the cell DRX. A base station may receive SRS for positioning from a radio device that has been activated by the cell DRX (e.g., celldrx-Config) during the inactive time, period, and / or duration of the cell DRX. SRS transmission for positioning may not be affected by the cell DRX or cell DRX operation.

[0233] A radio device configured to have a cell DRX (e.g., celldrx-Config) and activated by the cell DRX can be expected to transmit (e.g., transmit) periodic SRS and / or semi-persistent SRS for channel acquisition when it is in the active time, period, and / or duration of the cell DRX. A base station can receive periodic SRS and / or semi-persistent SRS for channel acquisition from a radio device configured to have a cell DRX (e.g., celldrx-Config) and activated by the cell DRX when it is in the active time, period, and / or duration of the cell DRX.

[0234] A wireless device configured for operation on a cell by either or both of the following: cell DTX operation by cellDTXConfig and cell DRX operation by cellDRXConfig, may additionally be provided by dci-Format2-9: a set of search spaces for monitoring PDCCH for detection of DCI Format 2_9 by common search space, and the location of DCI Format 2_9 for the cell DTX and / or DRX by position-inDCI-NES.

[0235] One or more configuration parameters may include a parameter (e.g., dci-Format2-9) indicating a set of search spaces (e.g., common search space set) for monitoring PDCCH to detect the DCI format (e.g., DCI format2_9). One or more configuration parameters may include a location parameter (e.g., position-inDCI-NES) indicating the location of cell DTX and / or DRX relative to cells in the DCI format (e.g., DCI format2_9).

[0236] Cell DTX and / or DRX may include two bits if the wireless device is configured to have both cell DTX operation (e.g., by cellDTXConfig) and cell DRX operation (e.g., by cellDRXConfig) for a cell. The first bit of the two bits may indicate cell DTX operation, and the second bit of the two bits may indicate cell DRX operation.

[0237] Cell DTX and / or DRX may include one bit indicating the cell DTX operation and / or cell DRX operation, respectively, if the wireless device is configured to have only one of the cell DTX operation (e.g., by cellDTXConfig) and cell DRX operation (e.g., by cellDRXConfig) for a cell.

[0238] A first value (e.g., "0") for the bits of cell DTX and / or DRX may indicate deactivation of cell DTX or cell DRX. A second value (e.g., "1") for the bits of cell DTX and / or DRX may indicate activation of cell DTX or cell DRX.

[0239] Cell DTX / DRX instructions for activating or deactivating cell DRX can be used for both UL carriers and SUL carriers if the cell is configured to have SUL carriers in addition to UL carriers (e.g., NUL).

[0240] A wireless device is not expected to monitor PDCCH for the detection of DCI format 2_9 on two or more cells (e.g., two or more serving cells). A wireless device may operate on a second cell in accordance with an indicated cell DTX operation or indicated cell DRX operation that starts from a slot on the active downlink BWP or active uplink BWP of the second cell, which may not be before the start of slot m+d on the active downlink BWP of the first cell, where the wireless device receives a PDCCH that provides / has a DCI format 2_9 indicating a change in activation or deactivation of the current cell DTX operation or current cell DRX operation for the second cell (e.g., the second serving cell) in slot m on the active downlink BWP of the first cell (e.g., the first serving cell), where d is the number of slots determined based on the subcarrier spacing (SCS) of the active downlink BWP of the first cell. The number of slots is equal to 3, for example, if the SCS of the active downlink BWP is 15 kHz. The number of slots is equal to 6, for example, if the SCS of the active downlink BWP is 30kHz.

[0241] Apart from the active time, period, and / or duration (e.g., DTX active time, period, and / or duration), the wireless device does not need to receive the CSI-RS in the cell DTX of the cell, and / or of the cell DTX of the cell, in the resources provided by the CSI-ReportConfig, which has a reportQuantity containing PDCCH candidates and / or rank indications for a set of search spaces associated with the detection of DCI formats (e.g., DCI format 2_0, DCI format 2_1, DCI format 2_2, DCI format 2_3, DCI format 2_4, and DCI format 2_5, DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 1_3, DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_3), via the cell.

[0242] Apart from the active time, period, and / or duration (e.g., DRX active time, period, and / or duration), the wireless device does not have to transmit (e.g., transmit) periodic or semi-persistent PUCCH or PUSCH (e.g., CSI reports, configured uplink authorizations) and / or periodic or semi-persistent SRS in the resources provided by the SRS-posResourceSet, if they are in and / or of the cell's cell DRX, through the cell.

[0243] Cell DTX may operate in cell DTX mode, or may be used interchangeably thereafter. Cell DRX may operate in cell DRX mode, or may be used interchangeably thereafter.

[0244] DCI format 2_9 may be used to activate or deactivate cell DTX and / or DRX, or cell DTX and / or DRX configuration, or cell DTX and / or DRX operation of one or more cells (e.g., one or more serving cells) for one or more wireless devices.

[0245] The information may be transmitted (e.g., transmitted) in DCI format 2_9 using a CRC scrambled by NES-RNTI. The information may include block number 1, block number 2, ..., block number N. The starting position of a block may be determined by a position parameter (e.g., positionInDCI-cellDTRX) by the radio device and / or base station. One or more configuration parameters may include the position parameter.

[0246] One or more blocks may be configured for a wireless device by a higher layer. One or more blocks may be configured for a wireless device by a higher layer, for example, if the wireless device is configured to have DTX and / or DRX parameters (e.g., NES-RNTI, cellDTRX-DCI-config). Fields may be defined for each block cell DTX / DRX instruction. For example, if both cellDTXConfig and cellDTXConfig are configured for a cell, there are 2 bits, where the most significant bit (MSB) corresponds to the cell's cell DTX (or cell DTX configuration) and the least significant bit (LSB) corresponds to the cell's cell DRX (or cell DRX configuration). For example, if either cellDTXConfig or cellDTXConfig is configured for a cell, there is 1 bit. One or more configuration parameters may include DTX and / or DRX parameters.

[0247] The size of DCI format 2_9 can be indicated by the upper-layer parameter sizeDCI-2-9. One or more configuration parameters may include the upper-layer parameter sizeDCI-2-9. The number of information bits in DCI format 2_9 may be less than or equal to the payload size of DCI format 2_9. For example, if the number of information bits in DCI format 2_9 is less than the size of DCI format 2_9, the remaining bits may be reserved.

[0248] Figures 17A and 17B are flowcharts illustrating examples of communication for energy saving. In step 1755 of Figure 17B, the base station may send one or more messages, and in step 1705 of Figure 17A, the radio device may receive one or more messages. One or more messages may include activation commands.

[0249] A wireless device may be configured to have a list of TCI states (e.g., TCI-State) within the upper-layer parameter PDSCH-Config, and / or by means of, in order to decode a PDSCH according to a detected PDCCH having an intended DCI for the wireless device and a given cell (e.g., a given serving cell, a given non-serving / candidate / target cell, etc.). The number of TCI states in the list may depend on the wireless device capability parameter maxNumberConfiguredTCIstatesPerCC. Each TCI state (e.g., TCI-State) may include and / or indicate the respective parameters for configuring a quasi-identical positional relationship between one or two downlink reference signals of a PDSCH and a DM-RS port, a DM-RS port of a PDCCH, or a CSI-RS port of a CSI-RS resource. The quasi-identical positional relationship may be configured by an upper-layer qcl-Type1 for the first downlink reference signal of one or more downlink reference signals. A quasi-identical relationship may be constructed by the upper layer parameter qcl-Type2 of the second downlink reference signal of one or more downlink reference signals. When two downlink reference signals, including the first and second downlink reference signals, are indicated by the TCI state, the QCL types of the two downlink reference signals may not be the same, regardless of whether the first and second downlink reference signals are identical or different. The quasi-identical type corresponding to the downlink reference signals of one or more downlink reference signals may be given by the upper layer parameter qcl-Type of the upper layer parameter QCL-Info, and can take one of the following values: "typeA": {Doppler shift, Doppler spread, mean delay, delay spread}, "typeB": {Doppler shift, Doppler spread}, "typeC": {Doppler shift, mean delay}, "typeD": {Spatial Rx parameter}.

[0250] A wireless device may be configured, and / or by means of, the upper-layer parameter dl-OrJointTCI-StateList in PDSCH-Config to have a list of TCI states (e.g., up to 128 TCI-State configurations). A TCI state in the list of TCI states may provide and / or indicate a reference signal for quasi-identical positions to i) the DM-RS of the PDSCH, ii) the DM-RS of the PDCCH in the BWP / cell, and / or iii) the CSI-RS. A TCI state in the list of TCI states may provide and / or indicate a reference signal for determining the uplink transmission space filter to i) the dynamic grant PUSCH, ii) the configuration grant-based PUSCH, iii) the PUCCH resource in the BWP / cell, and / or iv) the SRS.

[0251] In step 1760 of Figure 17B, the base station may transmit an activation command, and in step 1705 of Figure 17A, the radio device may receive an activation command. The radio device may receive an activation command (e.g., MAC-CE, DCI) used to map a maximum number of TCI states and / or pairs of TCI states (e.g., up to eight TCI states and / or pairs of TCI states), having one TCI state for a downlink channel (e.g., a signal) and / or one TCI state for an uplink channel (e.g., a signal), to a DCI field code point of a cell or set of cells (e.g., a downlink BWP) and / or a set of up to several TCI states (e.g., a set of up to eight TCI states). Each of several sets may consist of a maximum number of TCI states for downlink and uplink channels (e.g., signal and up to two TCI states) for a single cell or set of cells (e.g., downlink BWP) and, where applicable, for a DCI field "Transmission Configuration Instruction" code point for a single cell or set of cells (e.g., uplink BWP), or for a maximum number of TCI states for downlink channels (e.g., signal) (e.g., up to two TCI states) and for uplink channels (e.g., signal) (e.g., up to two TCI states). When a set of TCI state IDs is activated by an activation command for a set of cells (e.g., downlink BWP) and, where applicable, for a set of cells (e.g., uplink BWP), the applicable list of cells may be determined by the radio device by the cell indicated in the activation command, but the set of TCI state IDs (e.g., the same set of TCI state IDs) may be used by the radio device for the indicated cell or for all downlink BWPs and / or uplink BWPs in the applicable list of cells.A wireless device may use a TCI-State and / or a TCI-UL-State (e.g., the indicated TCI-State and / or TCI-UL-State) for one cell or one set of cells (e.g., a downlink BWP) and, if applicable, one cell or one set of cells (e.g., an uplink BWP), when an activation command maps the TCI-State and / or the TCI-UL-State to only one TCI codepoint (e.g., for a signal), and the indicated mapping for the single TCI codepoint is used by the wireless device.

[0252] A wireless device may receive a DCI format (e.g., DCI format 1_1 / 1_2) that provides (e.g., indicates) a TCI state (e.g., TCI-State and / or TCI-UL-State) for a cell configured by a simultaneous TCI update parameter (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4) or for all cells in the same cell list, if 1) the wireless device is configured with a dl-OrJointTCI-StateList by one or more configuration parameters (e.g., RRC messages / parameters) and is activated with a TCI-State by an activation command, or 2) the wireless device is configured with an ul-TCI-StateList by one or more configuration parameters (e.g., RRC messages / parameters) and is activated with a TCI-UL-State by an activation command. If tci-PresentInDCI is set to "enabled", or if tci-PresentDCI-1-2 is configured for a CORESET, the DCI format may or may not have a downlink assignment. The simultaneous TCI update parameter may be a higher layer parameter (e.g., an RRC parameter).

[0253] The indicated TCI-State may be used by a wireless device configured to have dl-OrJointTCI-StateList by one or more configuration parameters (e.g., RRC messages / parameters), starting from a first (e.g., starting, earliest, etc.) slot that may be at least several symbols (e.g., symbols of beamAppTime) from the last symbol of uplink transmission, when the wireless device transmits an uplink transmission (e.g., PUCCH transmission, PUSCH transmission) with a positive HARQ-ACK corresponding to a DCI format indicating the indicated TCI state (e.g., TCI-State and / or TCI-UL-State), and when the indicated TCI state is different from a previously indicated TCI state. The number of the first (e.g., starting, earliest, etc.) slot and symbols may both be determined by the wireless device based on an active BWP with the smallest subcarrier spacing among BWPs of a cell, using the indicated TCI-State that is active at the end of the uplink transmission carrying the positive HARQ-ACK. The number of symbols may be provided (e.g., indicated) to the wireless device by an RRC message (e.g., one or more configuration parameters).

[0254] A wireless device may be configured by higher-layer parameters (e.g., cjtSchemePDSCH and dl-OrJointTCI-StateList), and may be indicated by two TCI states used for PDSCH reception and / or may report support for two joint TCI states for PDSCH-CJT. A wireless device may assume that the PDSCH DM-RS port for PDSCH reception can be quasi-identical (QCL-ed) with respect to both downlink reference signals of the two indicated TCI states with respect to QCL-TypeA. A wireless device may make this assumption, for example, if it is configured to have the higher-layer parameter cjtSchemeA, if it is configured by the higher-layer parameters cjtSchemePDSCH and dl-OrJointTCI-StateList, and if it is indicated by two TCI states used for PDSCH reception and / or reports support for two joint TCI states for PDSCH-CJT.

[0255] Alternatively, a wireless device may assume that the PDSCH DM-RS port of a PDSCH receiver can be quasi-QCLed with respect to QCL-TypeA, except for the QCL parameters {Doppler shift, Doppler spread} of the second indicated TCI state (e.g., the second joint TCI state) of the two indicated TCI states. A wireless device may make this assumption, for example, if the wireless device is configured to have the upper layer parameter cjtSchemeB, and the wireless device is indicated for two TCI states used for PDSCH reception, and / or reports support for two joint TCI states for PDSCH-CJT.

[0256] In step 1765 of Figure 17B, the base station may transmit (e.g., transmit) a PDSCH (e.g., based on a TCI state), and in step 1715 of Figure 17A, the radio device may receive a PDSCH. The radio device may be configured to have a higher-layer parameter dl-OrJointTCI-StateList, and the radio device may have two indicated TCI states (e.g., two indicated joint / DL TCI states), including a first TCI state and a second TCI state. The radio device may be configured with a higher-layer parameter applyIndicatedTCIState to indicate, for example, whether the first TCI state, the second TCI state, or both of the two indicated TCI states are used for PDSCH reception scheduled or activated by DCI format 1_0. A wireless device may be configured to have a higher-layer parameter applyIndicatedTCIState indicating that a first TCI state, a second TCI state, or both of the two indicated TCI states are used for PDSCH reception scheduled or activated by DCI format 1_0. Regardless of the time and / or scheduling offset between reception of DCI format 1_0 / 1_1 / 1_2 and PDSCH reception scheduled and / or activated by DCI format 1_0 / 1_1 / 1_2, the wireless device may be configured by a higher-layer parameter, for example, if the wireless device is in frequency range 1 (FR1) and the wireless device is configured to have a higher-layer parameter dl-OrJointTCI-StateList and two indicated TCI states. A wireless device may report the capability of two default beams in frequency range 2 (FR2), which may be configured by the upper layer parameter dl-OrJointTCI-StateList, for example, if the wireless device is configured to have two indicated TCI states (e.g., two indicated joint / DL TCI states) including a first TCI state and a second TCI state.The wireless device may be configured by upper-layer parameters if, for example, the wireless device does not report the capability of two default beams within FR2, and the time and / or scheduling offset between the reception of DCI format 1_0 / 1_1 / 1_2 and the PDSCH reception scheduled and / or activated by DCI format 1_0 / 1_1 / 1_2 is greater than or equal to a threshold (e.g., timeDurationForQCL).

[0257] The upper layer parameter applyIndicatedTCIState can have a value of {"first", "second", or "both"}. A wireless device may be configured to have an upper layer parameter applyIndicatedTCIState with a value set to "both" only if the wireless device is configured to have an upper layer parameter cjtSchemePDSCH AND / or the wireless device supports two joint TCI states for PDSCH-CJT OR the wireless device is configured to have an upper layer parameter sfnSchemePdsch. When the value of the upper layer parameter applyIndicatedTCIState is set to "both", the wireless device may use both of the two indicated TCI states for PDSCH reception scheduled or activated by DCI format 1_0 on a search space set other than the CORESET / CORESET Type0 / 0A / 2 CSS set with index zero (e.g., CORESET#0). A wireless device may receive DCI format 1_0 via a different search space set than the Type0 / 0A / 2 CSS set associated with a CORESET having index zero. The first indicated TCI state may be used for PDSCH reception scheduled or activated by DCI format 1_0 if the wireless device is not configured to have applyIndicatedTCIState. For PDSCH reception, the wireless device may determine one of the two indicated TCI states (e.g., indicated joint / DL TCI state) if the wireless device is configured to have the upper layer parameter tciSelection-PresentInDCI and the wireless device receives DCI format 1_1 / 1_2 to schedule or activate PDSCH reception via / on a PDSCH transmission opportunity.

[0258] If DCI format 1_1 / 1_2 indicates a code point "00" for the TCI selection field, the wireless device may use the first of the two indicated TCI states for all PDSCH DM-RS ports of a PDSCH transmission opportunity of a PDSCH receiver scheduled or activated by DCI format 1_1 / 1_2. If DCI format 1_1 / 1_2 indicates a code point "00" for the TCI selection field, the wireless device may use the second of the two indicated TCI states for all PDSCH DM-RS ports of a PDSCH transmission opportunity of a PDSCH receiver scheduled or activated by DCI format 1_1 / 1_2. If DCI format 1_1 / 1_2 indicates a code point "10" for the TCI selection field, the wireless device may use both of the two indicated TCI states for a PDSCH receiver scheduled or activated by DCI format 1_1 / 1_2.

[0259] If the wireless device is not configured to have the upper-layer parameter tciSelection-PresentInDCI, and the wireless device receives DCI format 1_1 / 1_2 to schedule / activate PDSCH reception, then both of the two indicated TCI states may be used for PDSCH reception scheduled or activated by DCI format 1_1 / 1_2. If the wireless device does not report / support the ability to use default beam for SFN (e.g., sfn-DefaultDL-BeamSetup) for DCI format to schedule PDSCH reception without a TCI selection field, then it may be expected that the wireless device is configured to have the upper-layer parameter tciSelection-PresentInDCI. If the base station does not receive a report (e.g., a radio device capability message) from the radio device indicating support and / or capability to use a default beam (e.g., sfn-DefaultDL-BeamSetup) for an SFN to DCI format that schedules PDSCH reception without a TCI selection field, the base station may transmit (e.g., in an RRC message) one or more configuration parameters (e.g., in an RRC message) including the upper-layer parameter tciSelection-PresentInDCI to the radio device.

[0260] The upper-layer parameter applyIndicatedTCIState may be shown (for example, provided) to the radio device for each downlink BWP to indicate whether the first TCI state, the second TCI state, or both of the two indicated TCI states are being used for PDSCH reception scheduled and / or activated by DCI format 1_0.

[0261] If a wireless device is configured to have a higher-layer parameter dl-OrJointTCI-StateList and has two indicated TCI states (e.g., two indicated joint / DL TCI states) including a first TCI state and a second TCI state, the wireless device may be configured (e.g., provided) to have a higher-layer parameter applyIndicatedTCIState for each aperiodic CSI-RS resource set or aperiodic CSI-RS resource in the aperiodic CSI-RS resource set, and / or for it, in order to indicate that the wireless device is applying the first or second TCI state. The wireless device may also be configured to have a higher-layer parameter followUnifiedTCIState for aperiodic CSI-RS resource set for CSI or beam management (BM). The time and / or scheduling offset between the last symbol of the PDCCH carrying / having a DCI and the first (e.g., start, earliest, etc.) symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set triggered by the DCI may be greater than or equal to a threshold (e.g., beamSwitchTiming).

[0262] If a wireless device is configured by a top-layer parameter PDCCH-Config that includes two different values ​​of the top-layer parameter CORESETPoolIndex in different CORESETs (e.g., ControlResourceSets), then the first and second TCI states may correspond to two indicated TCI states specific to the top-layer parameter coresetPoolIndex having a value of 0 and the top-layer parameter coresetPoolIndex having a value of 1, respectively.

[0263] A wireless device may use a first TCI state or a second TCI state for a periodic CSI-RS via a periodic CSI-RS resource, based on or in accordance with the upper layer parameter applyIndicatedTCIState, which is indicated (e.g., provided) for / for a periodic CSI-RS resource or a set of periodic CSI-RS resources that includes a periodic CSI-RS resource. For example, if the wireless device is in frequency range 1 (FR1) or reports the capability of two default beams in frequency range 2 (FR2) and there is no downlink signal to the same symbol as the periodic CSI-RS resource, the wireless device may be configured to have the upper layer parameter dl-OrJointTCI-StateList, and two indicated TCI states including a first TCI state and a second TCI state (e.g., two indicated joints / DL If a DCI has a TCI state, and the time and / or scheduling offset between the DCI and the last symbol of the PDCCH carrying / having the first (e.g., start, earliest, etc.) symbol of a nonperiodic CSI-RS resource in a nonperiodic CSI-RS resource set triggered by the DCI is less than a threshold (e.g., beamSwitchTiming), then the first or second TCI state may be used for the nonperiodic CSI-RS resource via the nonperiodic CSI-RS resource based on or in accordance with the higher-level parameter applyIndicatedTCIState, which is indicated (e.g., provided) for / about the nonperiodic CSI-RS resource or for a nonperiodic CSI-RS resource set containing the nonperiodic CSI-RS resource.

[0264] If the wireless device is configured to have a higher-layer parameter dl-OrJointTCI-StateList and has two indicated TCI states (e.g., two indicated joint / DL TCI states) including a first TCI state and a second TCI state, and if the time and / or scheduling offset between the DCI and the last symbol of the PDCCH carrying / having the first (e.g., start, earliest, etc.) symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set triggered by the DCI is smaller than a threshold (e.g., beamSwitchTiming), then the first TCI state may be used for the aperiodic CSI-RS resource, or for the aperiodic CSI-RS resource, via the aperiodic CSI-RS resource, based on or in accordance with the higher-layer parameter applyIndicatedTCIState indicated (e.g., provided) for / about the aperiodic CSI-RS resource, or for the aperiodic CSI-RS resource set including the aperiodic CSI-RS resource.

[0265] A wireless device may use a first TCI state or a second TCI state for aperiodic CSI-RS via aperiodic CSI-RS resources based on (or in accordance with) the upper layer parameter applyIndicatedTCIState, which is indicated (e.g., provided) for / for aperiodic CSI-RS resources or a set of aperiodic CSI-RS resources that includes aperiodic CSI-RS resources. For example, a wireless device may be configured such that i) it has the upper layer parameter dl-OrJointTCI-StateList, ii) it has the upper layer parameter PDCCH-Config which includes two different values ​​of the upper layer parameter CORESETPoolIndex in different CORESETs (e.g., ControlResourceSets), and iii) it has two indicated TCI states including a first TCI state and a second TCI state (e.g., two indicated joints / DL If a TCI state is present, and the time and / or scheduling offset between the last symbol of the PDCCH carrying / having the DCI and the first (e.g., start, earliest, etc.) symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set triggered by the DCI is less than a threshold (e.g., beamSwitchTiming), and there is no downlink signal on the same symbol as the aperiodic CSI-RS resource, and the radio device is in frequency range 1 (FR1), or the radio device reports the default beam capability per coreset pool index in frequency range 2 (FR2), then the first or second TCI state may be used for the aperiodic CSI-RS resource via the aperiodic CSI-RS resource based on (or in accordance with) the higher-layer parameter applyIndicatedTCIState indicated (e.g., provided) for / about the aperiodic CSI-RS resource or for the aperiodic CSI-RS resource set containing the aperiodic CSI-RS resource.

[0266] Otherwise, the wireless device is configured such that i) it has a higher layer parameter dl-OrJointTCI-StateList, ii) it has a higher layer parameter PDCCH-Config which includes two different values ​​of the higher layer parameter CORESETPoolIndex in different CORESETs (e.g., ControlResourceSets), and iii) it has two indicated TCI states which include a first TCI state and a second TCI state (e.g., two indicated joints / DL If a TCI state is present, and the time and / or scheduling offset between the last symbol of the PDCCH carrying / having the DCI and the first (e.g., start, earliest, etc.) symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set triggered by the DCI is less than a threshold (e.g., beamSwitchTiming), and there is a downlink signal on the same symbol as the aperiodic CSI-RS resource, and the radio device is in frequency range 1 (FR1), or the radio device reports the default beam capability per coreset pool index in frequency range 2 (FR2), then the first TCI state associated with the upper layer parameter coresetPoolIndex having a value of 0 (or its specific or its) may be used for the aperiodic CSI-RS via the aperiodic CSI-RS resource.

[0267] A wireless device may transmit a capability message (e.g., a wireless device capability message) to a base station. The capability message may include dynamic switching parameters (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2). The dynamic switching parameters may indicate whether the wireless device supports (e.g., can enable) dynamic switching between single TRP and multi-TRP for downlink reception (e.g., PDSCH reception, PDCCH reception, etc.). The dynamic switching parameters may indicate whether the wireless device supports dynamic switching between single TRP and PDSCH SFN schemes (e.g., sfnSchemeA, sfnSchemeB). The dynamic switching parameter may indicate whether the wireless device supports dynamic switching between a non-SFN scheme (e.g., single TRP mode / operation / scheme) and a PDSCH SFN scheme (e.g., multi-TRP mode / operation / scheme) for downlink reception. The dynamic switching parameter may indicate whether the wireless device supports dynamic switching between a single TCI state (e.g., one TCI state) and multiple TCI states (e.g., two TCI states) for downlink reception.

[0268] A wireless device that supports dynamic switching may indicate in its capability message whether it supports an SFN scheme (e.g., sfn-SchemeA) or an SFN scheme for PDSCH reception only (e.g., sfn-SchemeA-PDSCH-only). A dynamic switching parameter may indicate whether the wireless device supports dynamic switching between a single TRP and a PDSCH SFN scheme by the TCI state field in DCI formats 1_1 and 1_2. A dynamic switching parameter may indicate whether the wireless device supports dynamic switching between a single TRP and a PDSCH SFN scheme by the TCI selection field in DCI formats 1_1 and 1_2. The dynamic switching parameter indicating whether the wireless device supports dynamic switching between a single TRP and a PDSCH SFN scheme by the TCI state field in DCI formats 1_1 and 1_2 may be the same as the dynamic switching parameter indicating whether the wireless device supports dynamic switching between a single TRP and a PDSCH SFN scheme by the TCI selection field in DCI formats 1_1 and 1_2. The dynamic switching parameters indicating whether a wireless device supports dynamic switching between a single TRP and a PDSCH SFN scheme by the TCI state fields of DCI formats 1_1 and 1_2 may be different from the dynamic switching parameters indicating whether a wireless device supports dynamic switching between a single TRP and a PDSCH SFN scheme by the TCI selection fields of DCI formats 1_1 and 1_2.

[0269] If the wireless device does not transmit (e.g., transmit, report, or instruct) the base station of its ability and / or support for dynamic switching, or if the ability message does not include dynamic switching parameters, the base station may not assume that the wireless device is configured to have the upper-layer parameter tciSelection-PresentInDCI. DCI formats 1_1 and 1_2 may not include the TCI selection field if the wireless device is not configured to have the upper-layer parameter tciSelection-PresentInDCI.

[0270] If a wireless device does not transmit (e.g., transmit, report, or instruct) the base station of its ability and / or support for dynamic switching, or if the ability message does not include dynamic switching parameters, the base station may not assume that the wireless device is configured to have the upper-layer parameter tciSelection-PresentInDCI. If the wireless device is not configured to have the upper-layer parameter tciSelection-PresentInDCI, the wireless device may not receive DCI formats with a TCI selection field (e.g., DCI format 1_1, DCI format 1_2). If the wireless device is not configured to have the upper-layer parameter tciSelection-PresentInDCI, the wireless device may receive DCI formats without a TCI selection field (e.g., DCI format 1_1, DCI format 1_2).

[0271] If the radio device does not transmit (e.g., transmit, report, or instruct) the base station of the ability to perform dynamic switching and / or support to the base station, or if the ability message does not include dynamic switching parameters, the base station may not transmit (e.g., transmit) one or more configuration parameters (e.g., in an RRC message) including the upper-layer parameter tciSelection-PresentInDCI to the radio device. If one or more configuration parameters do not include the upper-layer parameter tciSelection-PresentInDCI, the base station may not transmit (e.g., transmit) DCI formats with a TCI selection field (e.g., DCI format 1_1, DCI format 1_2) to the radio device. If one or more configuration parameters do not include the upper-layer parameter tciSelection-PresentInDCI, the base station may transmit (e.g., transmit) DCI formats without a TCI selection field (e.g., DCI format 1_1, DCI format 1_2) to the radio device. If a wireless device reports the capability of sfn-SchemeA-DynamicSwitching or sfn-SchemeB-DynamicSwitching, and if the wireless device is configured to have a higher-layer parameter sfnSchemePdsch set to either "sfnSchemeA" or "sfnSchemeB", then the code point of the DCI field "Transmission Configuration Indication" in DCI format 1_1 / 1_2 may be indicated by one TCI state or two TCI states.

[0272] It is not assumed that a wireless device is represented by only one TCI state per TCI code point by an activation command (e.g., MAC CE); a wireless device may be represented by two TCI states in the code point of the DCI field "Transmission Configuration Instruction" in DCI format 1_1 / 1_2.

[0273] Figure 18 shows an example of energy saving. Wireless device 1805 may receive one or more messages. Wireless device 1805 may receive one or more messages from base station 1810. Base station 1810 may transmit (e.g., transmit) one or more messages. Wireless device 1805 may receive one or more messages from relay nodes. Wireless device 1805 may receive one or more messages from other wireless devices (e.g., TRP, vehicle, remote wireless head, etc.). One or more messages may contain one or more configuration parameters 1815 (e.g., at time T0). One or more configuration parameters 1815 may be one or more RRC configuration parameters. One or more configuration parameters 1815 may be one or more RRC reconfiguration parameters (e.g., RRCReconfiguration, reconfigurationWithSync). One or more messages may be one or more RRC messages. One or more messages may be one or more RRC reconfiguration messages (e.g., RRCReconfiguration, reconfigurationWithSync). One or more configuration parameters 1815 may be for cells.

[0274] The cell can be, for example, a serving cell. At least one configuration parameter among the one or more configuration parameters 1815 may be for the cell. The cell may be a primary cell (PCell). The cell may be a primary secondary cell (PSCell). The cell may be a secondary cell (SCell). The cell may be a secondary cell configured with PUCCH (e.g., a PUCCH SCell). The cell may be a special cell (SpCell). An SpCell may refer to (e.g., indicate) a PCell of an MCG or a PSCell of an SCG for dual connectivity (DC) operation, otherwise, the SpCell may refer to (e.g., indicate) a PCell. The cell may be a primary SCG cell (PSCell). The wireless device 1805 may perform a random access procedure via the PSCell, for example, when performing reconfiguration with a Sync procedure for dual connectivity operation. The cell may be, for example, an unlicensed cell operating in an unlicensed band. The cell may be, for example, a licensed cell operating in a licensed band. The cell may operate in a first frequency range (FR1). FR1 may include, for example, frequency bands below 6 GHz. The cell may operate in a second frequency range (FR2). FR2 may include, for example, frequency bands from 24 GHz to 52.6 GHz. The cell may operate in a third frequency range (FR3). FR3 may include, for example, frequency bands from 52.6 GHz to 71 GHz. FR3 may include, for example, frequency bands starting from (or exceeding) 52.6 GHz.

[0275] The wireless device 1805 may perform uplink transmission (e.g., PUSCH, PUCCH, PUCCH) through the cell at a first time and a first frequency. The wireless device 1805 may perform downlink reception (e.g., PDCCH, PDSCH) through the cell at a second time and a second frequency. The cell may operate in time-division duplex (TDD) mode. The first and second frequencies may be the same in TDD mode. The first and second times may be different in TDD mode. The cell may operate in frequency-division duplex (FDD) mode. The first and second frequencies may be different in FDD mode. The first and second times may be the same in FDD mode. The wireless device 1805 may be in an RRC connected state (e.g., mode). The wireless device 1805 may be in an RRC idle state (e.g., mode). The wireless device 1805 may be in an RRC inactive state (e.g., mode).

[0276] A cell may contain multiple BWPs. One or more configuration parameters 1815 may indicate multiple BWPs for a cell. Multiple BWPs may include one or more uplink BWPs, including the cell's uplink BWP. Multiple BWPs may include one or more downlink BWPs, including the cell's downlink BWP.

[0277] One of several BWPs may be in either an active or inactive state. The wireless device 1805 may monitor downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) via and / or on the downlink BWP when one of the downlink BWPs is active. The wireless device 1805 may receive PDSCH via and / or on the downlink BWP when one of the downlink BWPs is active. The wireless device 1805 does not need to monitor downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) via and / or on the downlink BWP when one of the downlink BWPs is in an inactive state. The wireless device 1805 may stop monitoring or receiving downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) via and / or on the downlink BWP when one of the downlink BWPs is inactive. The wireless device 1805 does not have to receive PDSCH via and / or on the downlink BWP when one of the downlink BWPs is inactive. The wireless device 1805 may stop receiving PDSCH via and / or on the downlink BWP when one of the downlink BWPs is inactive.

[0278] The wireless device 1805 may transmit (e.g., transmit) uplink channels and / or signals (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) over the uplink BWP when one of the uplink BWPs is active. The wireless device 1805 does not have to transmit (e.g., transmit) uplink channels and / or signals (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) over the uplink BWP when one of the uplink BWPs is inactive.

[0279] The wireless device 1805 may activate one of the downlink BWPs of a cell. Activating a downlink BWP may include setting (e.g., switching) the downlink BWP as the active downlink BWP of the cell. Activating a downlink BWP may include setting the downlink BWP to an active state. Activating a downlink BWP may include switching the downlink BWP from an inactive state to an active state.

[0280] The wireless device 1805 may activate one of the uplink BWPs of the cell. Activating an uplink BWP may include the wireless device 1805 setting the uplink BWP as the active uplink BWP of the cell (e.g., switching it). Activating an uplink BWP may include setting the uplink BWP to an active state. Activating an uplink BWP may include switching the uplink BWP from an inactive state to an active state.

[0281] One or more configuration parameters 1815 may be for the cell's downlink BWP (e.g., active downlink BWP). At least one of the one or more configuration parameters 1815 may be for the cell's downlink BWP.

[0282] One or more configuration parameters 1815 may be for the cell's uplink BWP (e.g., active). At least one of the one or more configuration parameters 1815 may be for the cell's uplink BWP.

[0283] One or more configuration parameters 1815 may indicate multiple TCI states 1820 (e.g., TCI state 0, TCI state 1, ..., TCI state M-1). One or more configuration parameters may include a TCI state list parameter (e.g., provided by a higher layer (e.g., RRC) dl-OrJoint-TCIStateList) indicating a TCI state list. The TCI state list may include multiple TCI states 1820. One or more configuration parameters 1815 may include one or more PDSCH configuration parameters (e.g., PDSCH-Config) including, for example, a TCI state list parameter indicating multiple TCI states 1820. For example, as illustrated herein in Figure 18, the multiple TCI states 1820 are TCI state 0, TCI state 1, ..., and TCI state M-1.

[0284] One or more configuration parameters 1815 may indicate multiple TCI state indices, indicators, and / or identifiers (e.g., TCI-StateId) for multiple TCI states 1820. One or more configuration parameters 1815 may indicate each TCI state index of multiple TCI state indices for each TCI state of multiple TCI states 1820. Each TCI state of multiple TCI states 1820 can be indexed, indicated, and / or identified by each TCI state index of multiple TCI state indices. One or more configuration parameters 1815 may indicate, for example, a first TCI state index of multiple TCI state indices for a first TCI state among multiple TCI states 1820. One or more configuration parameters 1815 may indicate a second TCI state index of multiple TCI state indices for a second TCI state among multiple TCI states 1820. One or more configuration parameters 1815 may indicate multiple TCI states 1820 that indicate and / or identify a unified TCI state for a cell.

[0285] One or more configuration parameters 1815 may include, for example, one or more PDSCH configuration parameters for the cell's downlink BWP. One or more configuration parameters 1815 may indicate multiple TCI states 1820 for the cell's downlink BWP.

[0286] One or more configuration parameters 1815 may include, for example, one or more PDSCH configuration parameters for the second downlink BWP of the second cell. One or more configuration parameters 1815 may indicate multiple TCI states 1820 for the second downlink BWP of the second cell. One or more configuration parameters 1815 may include a standard unified TCI state list parameter (e.g., unifiedTCI-StateRef) that indicates the second downlink BWP of the second cell for the cell's downlink BWP. The standard unified TCI state list parameter may include a BWP index (e.g., BWP-Id) that identifies and / or indicates the second downlink BWP. The standard unified TCI state list parameter may include a cell index (e.g., ServCellIndex) that identifies and / or indicates the second cell. The second downlink BWP of the second cell may be the base BWP of the base cell for the cell's downlink BWP. The cell's downlink BWP may be the target BWP of the target cell. One or more PDSCH configuration parameters of a cell's downlink BWP may not include the higher-level (e.g., RRC) parameter dl-OrJoint-TCIStateList, for example, based on one or more configuration parameters 1815 that include the standard unified TCI state list parameter for the cell's downlink BWP.

[0287] One or more configuration parameters 1815 may include a unified-TCI-state-type parameter (e.g., unifiedtci-StateType). One or more configuration parameters 1815 may include one or more serving cell parameters (e.g., ServingCellConfig) that include a unified-TCI-state-type parameter. The unified-TCI-state-type parameter may indicate the unified TCI state type of the cell.

[0288] The unified-TCI-state-type parameter may be set to, for example, "Joint". The wireless device 1805 may use multiple TCI states 1820 (e.g., provided / indicated by dl-OrJoint-TCIStateList) for both uplink transmissions of and / or through a cell (e.g., PUSCH / PUCCH / SRS transmissions) and downlink receptions of and / or through a cell (e.g., PDCCH / PDSCH / CSI-RS receptions), based on, for example, that one or more configuration parameters 1815 include a unified-TCI-state-type parameter set to "Joint". Multiple TCI states 1820 may be, for example, multiple joint TCI states.

[0289] The unified-TCI-state-type parameter may be set to, for example, "Separate". The wireless device 1805 may use multiple TCI states 1820 (e.g., provided / indicated by the upper-layer parameter dl-OrJoint-TCIStateList) for downlink reception (e.g., PDCCH / PDSCH / CSI-RS reception) of and / or through a cell, for example, based on the fact that one or more configuration parameters 1815 include a unified-TCI-state-type parameter set to "Separate". The wireless device 1805 does not have to use multiple TCI states 1820 for uplink transmission (e.g., PUSCH / PUCCH / SRS transmission) of and / or through a cell, for example, based on the fact that one or more configuration parameters 1815 include a unified-TCI-state-type parameter set to "Separate". Multiple TCI states 1820 may be, for example, multiple downlink TCI states.

[0290] One or more configuration parameters 1815 may indicate a second set of TCI states. One or more configuration parameters 1815 may include an uplink TCI state list parameter (e.g., provided / indicated by the higher-level parameter ul-TCI-StateList) that indicates an uplink TCI state list. The uplink TCI state list may include a second set of TCI states. One or more configuration parameters 1815 may include one or more uplink BWP configuration parameters that include an uplink TCI state list parameter indicating a second set of TCI states. The second set of TCI states may be, for example, TCI state 0, TCI state 1, ... and TCI state M-1.

[0291] One or more configuration parameters 1815 may include, for example, one or more uplink BWP configuration parameters for the cell's uplink BWP. One or more configuration parameters 1815 may indicate a second set of TCI states for the cell's uplink BWP.

[0292] One or more configuration parameters 1815 may include, for example, one or more uplink BWP configuration parameters for the second uplink BWP of the second cell. One or more configuration parameters 1815 may indicate a second set of TCI states for the second uplink BWP of the second cell. One or more configuration parameters 1815 may include a standard unified TCI state list parameter (e.g., unifiedtci-StateType) for the uplink BWP of the cell that indicates the second uplink BWP of the second cell. The standard unified TCI state list parameter may include a BWP index (e.g., BWP-Id) that identifies and / or indicates the second uplink BWP. The standard unified TCI state list parameter may include a cell index (e.g., ServCellIndex) that identifies and / or indicates the second cell. The second uplink BWP of the second cell may be the base BWP of the base cell for the cell's uplink BWP. The cell's uplink BWP may be the target BWP of the target cell. One or more uplink BWP configuration parameters of a cell's uplink BWP may not include the higher-level (e.g., RRC) parameter ul-TCI-StateList, for example, based on the fact that one or more configuration parameters 1815 for the cell's uplink BWP include the standard unified TCI state list parameter.

[0293] The wireless device 1805 may use a second set of TCI states for uplink transmissions of and / or through a cell (e.g., PUSCH / PUCCH / SRS transmissions), for example, based on the fact that one or more configuration parameters 1815 include a unified-TCI-state-type parameter set to "Separate". The wireless device 1805 does not have to use a second set of TCI states for downlink receptions of and / or through a cell (e.g., PDCCH / PDSCH / CSI-RS receptions), for example, based on the fact that one or more configuration parameters 1815 include a unified-TCI-state-type parameter set to "Separate". The second set of TCI states may be, for example, a set of uplink TCI states.

[0294] The wireless device 1805 may use multiple TCI states 1820 for downlink reception via a cell's downlink BWP, for example, based on one or more configuration parameters 1815 indicating multiple TCI states 1820 for a cell's downlink BWP. The wireless device 1805 may use multiple TCI states 1820 for uplink transmission reception via a cell's uplink BWP, for example, based on one or more configuration parameters 1815 indicating multiple TCI states 1820 for a cell's downlink BWP. The wireless device 1805 may use multiple TCI states 1820 for a second downlink BWP of a second cell for downlink reception via a cell's downlink BWP, for example, based on a standard unified TCI state list parameter indicating a second downlink BWP of a second cell.

[0295] The wireless device 1805 may use a plurality of TCI states 1820 for the second downlink BWP of a second cell, for example, for the downlink BWP of a cell, based on a standard unified TCI state list parameter indicating the second downlink BWP of a second cell. The wireless device 1805 may use a second plurality of TCI states, for example, for the uplink BWP of a cell, based on one or more configuration parameters 1815 indicating a second plurality of TCI states for the uplink BWP of a cell. The wireless device 1805 may use a second plurality of TCI states for the second uplink BWP of a second cell, for example, for the uplink BWP of a cell, based on a standard unified TCI state list parameter indicating the second uplink BWP of a second cell.

[0296] The wireless device 1805 may receive activation commands (e.g., MAC-CE, DCI, RRC, control commands, downlink control commands / messages, control commands / messages, unified TCI state activation / deactivation MAC CE, enhanced unified TCI state activation / deactivation MAC CE, etc.). An activation command may indicate the activation of a subset of TCI states (e.g., two TCI states 1825) from among multiple TCI states 1820 (e.g., DLorJoint-TCIStateList). The subset of TCI states (e.g., two TCI states 1825) may be, for example, a subset of joint TCI states from among multiple joint TCI states. The subset of TCI states (e.g., two TCI states 1825) may be, for example, a subset of downlink TCI states from among multiple downlink TCI states.

[0297] An activation command (e.g., a first control command 1830) may indicate the activation of a subset of TCI states (e.g., two TCI states 1825) from a second set of TCI states (e.g., ul-TCI-StateList). The subset of TCI states (e.g., two TCI states 1825) may be a subset of uplink TCI states from a set of uplink TCI states.

[0298] The base station 1810 may activate and / or deactivate a subset of TCI states (e.g., two TCI states 1825) by, for example, transmitting an activation command. The radio device 1805 may map a subset of TCI states (e.g., two TCI states 1825) to one or more TCI code points. An activation command may indicate a mapping of a subset of TCI states (e.g., two TCI states 1825) to one or more TCI code points. The radio device 1805 may map each TCI state of the subset of TCI states (e.g., two TCI states 1825) to each TCI code point of one or more TCI code points. One or more TCI code points may represent and / or contain a subset of TCI states (e.g., two TCI states 1825). Each TCI code point in one or more TCI code points may represent or map to each of a subset of TCI states (e.g., two TCI states 1825). Each TCI code point in one or more TCI code points may represent / contain (or map to) one or more TCI states.

[0299] A subset of TCI states may be TCI state 4, TCI state 5, TCI state 8, TCI state 26, and TCI state 61. One or more TCI code points may include a first TCI code point (e.g., TCI code point 000), a second TCI code point (e.g., TCI code point 001), a third TCI code point (e.g., TCI code point 010), and a fourth TCI code point (e.g., TCI code point 011). The first TCI code point (e.g., TCI code point 000) may include TCI state 4. The second TCI code point (e.g., TCI code point 001) may include TCI state 5 and TCI state 8. The third TCI code point (e.g., TCI code point 010) may include TCI state 26 and TCI state 61. The fourth TCI code point (e.g., TCI code point 011) may include TCI state 26. For example, the first TCI code point (e.g., TCI code point 000) and the fourth TCI code point (e.g., TCI code point 011) represent a single TCI state. The second TCI code point (e.g., TCI code point 001) and the third TCI code point (e.g., TCI code point 010) represent two TCI states (e.g., two joint TCI states, two uplink TCI states, two downlink TCI states, etc.).

[0300] Figure 19 shows an example of an activation command. An activation command may include multiple fields. The first field 1905 of the multiple fields (e.g., Serving Cell ID) may include a serving cell index, instruction, and / or identifier that indicates and / or identifies a cell. The first field 1905 may include a serving cell index, instruction, and / or identifier that indicates and / or identifies the cell to which the activation command applies. An activation command may use each cell in a simultaneous TCI update cell list (e.g., simultaneousTCI-UpdateList1, simultaneousTCI-UpdateList2) if one or more configuration parameters indicate and / or configure a cell in or as part of a simultaneous TCI update cell list.

[0301] The second field 1910 of the multiple fields (e.g., BWP ID) may include a BWP index, indication, and / or identifier that indicates and / or identifies the cell's downlink BWP. The second field 1910 may include a BWP index, indication, and / or identifier that indicates and / or identifies the cell's downlink BWP to which the activation command is applied as a code point in the DCI's bandwidth partial indicator field.

[0302] The third field among multiple fields, 1915 (for example, the TCI status ID in Figure 19). i、j ) may include a TCI state index, indicator, and / or identifier (e.g., TCI-StateId) that identifies one of several TCI states. Multiple TCI state indices may include TCI state indices. Index i may be an index of the code point in the Transmission Configuration Instruction (TCI) field in DCI. TCI State ID i、j This is the TCI status ID. i、j i in the DCI transmission configuration instruction field 番目の j shown for codepoint 番目の Possibly in TCI state. TCI state ID 0、1may indicate, for example, the first TCI state (e.g., 1 番目の TCI state) indicated for TCI code point 000. TCI state ID 0、2 may indicate the second TCI state (e.g., 2 番目の TCI state) indicated for TCI code point 000. TCI state ID 1、1 may indicate, for example, the first TCI state (e.g., 1 番目の TCI state) indicated for TCI code point 001. TCI state ID 1、2 may indicate the second TCI state (e.g., 2 番目の TCI state) indicated for TCI code point 001. TCI state ID N、1 may indicate, for example, when N in FIG. 19 is equal to 8, the first TCI state (e.g., 1 番目の TCI state) indicated for TCI code point 111. TCI state ID N、2 may indicate the second TCI state (e.g., 2 番目の TCI state). For TCI code point i, TCI state ID i、1 may indicate / be the first TCI state (e.g., 1 番目の TCI state), and TCI state ID i、2 may indicate / be the second TCI state (e.g., 2 番目の TCI state).

[0303] The TCI code point to which the TCI state is mapped may be determined by the wireless device and / or the base station according to the sequential position of the TCI code point among the sequential positions of the TCI code points. TCI state ID 0、1 and TCI state ID 0、2 The first TCI code point having the same may be mapped to, for example, code point value 0 (e.g., TCI code point 000), and TCI state ID 1、1 and TCI state ID 1、2 The second TCI code point having the same may be mapped to code point value 1 (e.g., TCI code point 001).

[0304] A second TCI code point (e.g., TCI code point 001) may include TCI state 5 and TCI state 8. TCI state 5 and TCI state 8 can be mapped to the second TCI code point (e.g., TCI code point 001).

[0305] The activation command uses the TCI state index, indicator, and / or identifier (e.g., TCI state ID) of TCI state 5. 1、1 ), as well as the TCI state index, indicator, and / or identifier of TCI state 8 (e.g., TCI state ID 1、2 ) may include. TCI state 5 may be the first TCI state, and TCI state 8 may be, for example, the TCI state index, indicator, and / or identifier of TCI state 5 (e.g., TCI state ID 1、1 ) is the TCI state index, indicator, and / or identifier of TCI state 8 (e.g., TCI state ID). 1、2 Octet 4 of the activation command may be a second TCI state based on its appearance, presence, and / or positioning in a lower octet within the activation command. Octet 4 of the activation command may be, for example, the TCI state index, indicator, and / or identifier of TCI state 5 (e.g., TCI state ID). 1、1 ) may include, and octet 5 of the activation command may include the TCI state index, indicator, and / or identifier of TCI state 8 (e.g., TCI state ID). 1、2 ) may include.

[0306] The activation command uses the TCI state index, indicator, and / or identifier (e.g., TCI state ID) of TCI state 8. 1、1 ), as well as the TCI state index, indicator, and / or identifier of TCI state 5 (e.g., TCI state ID 1、2 ) may include. TCI state 8 may be the first TCI state, and TCI state 5 may be, for example, the TCI state index, indicator, and / or identifier of TCI state 8 (e.g., TCI state ID 1、1) is the TCI state index, indicator, and / or identifier of TCI state 5 (e.g., TCI state ID 1、2 Octet 4 of the activation command may be a second TCI state based on its appearance, presence, and / or positioning in a lower octet within the activation command. Octet 4 of the activation command may be, for example, the TCI state index, indicator, and / or identifier of TCI state 8 (e.g., TCI state ID). 1、1 ) may include, and octet 5 of the activation command may include the TCI state index, indicator, and / or identifier of TCI state 5 (e.g., TCI state ID). 1、2 ) may include.

[0307] A third TCI code point (e.g., TCI code point 010) may include TCI state 26 and TCI state 61. TCI state 26 and TCI state 61 can be mapped to a third TCI code point (e.g., TCI code point 010).

[0308] The activation command uses the TCI state index, indicator, and / or identifier (e.g., TCI state ID) of TCI state 26. 2、1 ), as well as the TCI state index, indicator, and / or identifier of TCI state 61 (e.g., TCI state ID 2、2 ) may include. TCI state 26 may be a first TCI state, and TCI state 61 may be, for example, the TCI state index, indicator, and / or identifier of TCI state 26 (e.g., TCI state ID 2、1 ) is the TCI state index, indicator, and / or identifier of TCI state 61 (e.g., TCI state ID 2、2 Octet 6 of the activation command may be a second TCI state based on its appearance, presence, and / or positioning in a lower octet within the activation command. Octet 6 of the activation command may be, for example, the TCI state index, indicator, and / or identifier of TCI state 26 (e.g., TCI state ID). 2、1) may include, and octet 7 of the activation command may include the TCI state index, indicator, and / or identifier of TCI state 61 (e.g., TCI state ID 2、2 ) may include.

[0309] The activation command uses the TCI state index, indicator, and / or identifier (e.g., TCI state ID) of TCI state 61. 2、1 ), as well as the TCI state index, indicator, and / or identifier of TCI state 26 (e.g., TCI state ID 2、2 ) may include. TCI state 61 may be a first TCI state, and TCI state 26 may be, for example, a TCI state index, indicator, and / or identifier of TCI state 61 (e.g., TCI state ID 2、1 ) is the TCI state index, indicator, and / or identifier of TCI state 26 (e.g., TCI state ID 2、2 Octet 6 of the activation command may be a second TCI state based on its appearance, presence, and / or positioning in a lower octet within the activation command. Octet 6 of the activation command may be, for example, the TCI state index, indicator, and / or identifier of TCI state 61 (e.g., TCI state ID). 2、1 ) may include, and octet 7 of the activation command may include the TCI state index, indicator, and / or identifier of TCI state 26 (e.g., TCI state ID 2、2 ) may include.

[0310] The fourth field among multiple fields, 1920a-1920e (e.g., R), may be a reserved bit. A reserved bit may be set to zero, for example.

[0311] The wireless device may receive control commands (e.g., a first control command at time T1, as described herein in Figure 18). The control command may be, for example, MAC-CE. The control command may be, for example, DCI (e.g., DCI format 1_1, DCI format 1_2). The control command may be, for example, a downlink control command (e.g., an activation command). The control command may indicate at least two TCI states from a subset of TCI states.

[0312] The number of one or more TCI code points may be equal to 1 (e.g., a single TCI code point). A single TCI code point may represent at least two TCI states. A control command representing at least two TCI states may be an activation command that activates a subset of TCI states based on the number of one or more TCI code points being equal to 1. At least two TCI states may be a subset of TCI states based on the number of one or more TCI code points being equal to 1. An activation command may represent at least two TCI states based on the number of one or more TCI code points being equal to 1.

[0313] The number of one or more TCI code points may be greater than 1. A control command indicating at least two TCI states may differ from an activation command that activates a subset of TCI states based on the number of one or more TCI code points being greater than 1. A radio device may receive a control command after receiving an activation command. A control command (e.g., DCI) may include a TCI field indicating at least two TCI states. The value of the TCI field may be equal to one or more TCI code points indicating at least two TCI states. At least two TCI states may be mapped to TCI code points.

[0314] At least two TCI states may, for example, be at least two joint TCI states. At least two TCI states may, for example, be at least two downlink TCI states. At least two TCI states may, for example, be at least two uplink TCI states. At least two TCI states may include a first TCI state and a second TCI state. The first TCI state may include a first reference signal (e.g., CSI-RS, SSB / PBCH block, DM-RS, SRS, etc.). The first TCI state may include a first quasi-identical type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D). The second TCI state may include a second reference signal (e.g., CSI-RS, SSB / PBCH block, DM-RS, SRS, etc.). The second TCI state may include a second quasi-identical type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D).

[0315] The wireless device may receive a control command (e.g., a second control command at time T2 as described herein in Figure 18). The control command may be, for example, a DCI (e.g., DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 1_3, etc.). The control command (e.g., a second control command at time T2 as described herein in Figure 18) may schedule a downlink reception (e.g., a downlink reception at time T4 as described herein in Figure 18). The control command may schedule a downlink reception based on, for example, that the control command indicates resources for downlink reception. The control command may schedule a downlink reception based on, for example, that the control command includes one or more fields used by the wireless device for downlink reception (e.g., TDRA field, MCS field, FDRA field, BWP index, HARQ process index, etc.). A control command (for example, a second control command at time T2 as described herein in Figure 18) may, for example, activate downlink reception in an SPS configuration.

[0316] One or more configuration parameters may include one or more semi-persistent scheduling (SPS) configuration parameters of the SPS configuration. A control command may indicate the activation of the SPS configuration. A control command may include one or more fields (e.g., RV, HARQ process, MCS, etc.) set to predefined values ​​(e.g., 0, 1) that indicate the activation of the SPS configuration. A wireless device may validate a control command based on the fact that one or more fields (e.g., RV, HARQ process, MCS, etc.) are set to predefined values. A wireless device may activate the SPS configuration based on validating the control command.

[0317] Downlink reception may include, for example, PDSCH reception. PDSCH reception may include one or more transport blocks (e.g., downlink data). Control commands may include one or more fields (e.g., TDRA field, FDRA field) indicating resources for downlink reception. A cell's downlink BWP may include resources.

[0318] Downlink reception may include, for example, aperiodic CSI-RS. A control command may trigger the reception of aperiodic CSI-RS via aperiodic CSI-RS resources. A control command may include a CSI request field that triggers an aperiodic CSI report. A control command may include a CSI request field that triggers an aperiodic CSI report that includes the radio link quality (e.g., RSRP, SINR, SNR) of the aperiodic CSI-RS.

[0319] One or more configuration parameters may indicate one or more aperiodic trigger states (e.g., by the higher-layer parameter CSI-AperiodicTriggerStateList). Code points in the CSI request field within a control command may be associated with or indicate one or more aperiodic trigger states. Aperiodic trigger states may include one or more report configurations (e.g., provided by the higher-layer parameter associatedReportConfigInfoList, NZP-CSI-RS-ResourceSet list). A wireless device may perform aperiodic CSI-RS measurements via an aperiodic CSI-RS resource and, based on receiving a control command with a CSI request field indicating an aperiodic trigger state, transmit (e.g., transmit) an aperiodic CSI report according to one or more report configurations for the aperiodic trigger state.

[0320] A report configuration of one or more report configurations (e.g., provided by the upper-level parameters CSI-AssociatedReportConfigInfo and NZP-CSI-RS-ResourceSet) may be indexed, indicated, and / or identified by a report configuration index, indicator, and / or identifier (e.g., provided by the upper-level parameter CSI-ReportConfigId). A report configuration may include one or more aperiodic CSI-RS resources (e.g., NZP-CSI-RS-Resource). An aperiodic CSI-RS resource among one or more aperiodic CSI-RS resources may be associated with a TCI state among multiple TCI states (e.g., provided by the upper-level parameters qcl-info or applyIndicatedTCIState of IE CSI-AperiodicTriggerStateList). A TCI state may provide QCL assumptions for aperiodic CSI-RS (e.g., RS, RS source, SS / PBCH block, CSI-RS) via the aperiodic CSI-RS resource. A TCI state may provide a QCL type (e.g., QCL-TypeA, QCL-TypeD, etc.) to a periodic CSI-RS via a periodic CSI-RS resources. At least two TCI states may include other TCI states.

[0321] A control command (for example, a second control command at time T2 as described herein in Figure 18) may include a TCI selection field having a value (e.g., "10") indicating the use of at least two TCI states for downlink reception. A control command may indicate a value (e.g., "10") for the code point of the TCI selection field. A control command indicating a value (e.g., "10") for the code point of the TCI selection field may indicate the use of at least two TCI states (e.g., both or each of at least two TCI states) for downlink reception. A control command may include a TCI selection field based, for example, on the fact that one or more configuration parameters include the higher-layer parameter tciSelection-PresentInDCI. A control command may be, for example, DCI format 1_1. A control command may be, for example, DCI format 1_2.

[0322] A control command (for example, the second control command at time T2 in Figure 18) does not have to include a TCI selection field. The control command may be, for example, DCI format 1_1. The control command may be, for example, DCI format 1_2. The control command may not have to include a TCI selection field, for example, based on the fact that one or more configuration parameters do not include the higher-layer parameter tciSelection-PresentInDCI. A control command that does not include a TCI selection field may indicate the use of at least two TCI states (e.g., both / each of at least two TCI states) for downlink reception. The TCI selection field does not have to be present in the control command.

[0323] The control command may be, for example, DCI format 1_0. One or more configuration parameters may include an apply-indicatedTCIState parameter (e.g., applyIndicatedTCIState) set to "both" to indicate that at least two TCI states (e.g., both / each of at least two TCI states) will be used for downlink reception scheduled and / or activated by DCI format 1_0.

[0324] The apply-indicated TCI state parameter (e.g., applyIndicatedTCIState) may be set to "both" based on, for example, that one or more configuration parameters include coherent coupled transmission (CJT) scheme parameters for PDSCH reception (e.g., cjtSchemePDSCH). The apply-indicated TCI state parameter (e.g., applyIndicatedTCIState) may be set to "both" based on, for example, that a base station is sent (e.g., transmitted) a capability message (e.g., radio device capability message) indicating support for two TCI states (e.g., two joint TCI states) for CJT-based PDSCH reception. The apply-indicated TCI state parameter (e.g., applyIndicatedTCIState) may be set to "both" based on, for example, that one or more configuration parameters include single-frequency network (SFN) parameters for PDSCH reception (e.g., sfnSchemePdsch).

[0325] A wireless device may receive a downlink reception (for example, at time T4 as described herein in Figure 18). A wireless device may receive a downlink reception via the cell's downlink BWP. A wireless device may receive a downlink reception based on one or more TCI states of at least two TCI states. One or more TCI states may be a first TCI state of at least two TCI states. One or more TCI states may be a second TCI state of at least two TCI states. One or more TCI states may be at least two TCI states.

[0326] One or more configuration parameters may indicate at least two DTXs for a cell. At least two DTXs of a cell may be at least two DTX configurations of the cell, or may be interchangeable. At least two DTXs of a cell may be at least two DTX operations of the cell, or may be interchangeable.

[0327] One or more configuration parameters may include one or more first DTX configuration parameters (e.g., TRP-DTX-Config, TRP-DTX-Config1, TRP1-DTX-Config, DTX-Config, DTX-Config1, etc.) that indicate a first DTX of a cell (e.g., a first DTX as described herein in Figure 18). At least two DTXs of a cell may constitute the first DTX of the cell. The first DTX of a cell may be a first DTX configuration of the cell, or may be used interchangeably therewith. The first DTX of a cell may be a first DTX operation of the cell, or may be used interchangeably therewith. The first DTX may be associated with a first TRP (e.g., TRP1). One or more configuration parameters may indicate a first DTX for energy saving of a first TRP.

[0328] One or more configuration parameters may include one or more second DTX configuration parameters (e.g., TRP-DTX-Config2, TRP2-DTX-Config, DTX-Config2, etc.) that indicate a second DTX of the cell (e.g., a second DTX as described herein in Figure 18). At least two DTXs of a cell may include a second DTX of the cell. A second DTX of a cell may be a second DTX configuration of the cell, or may be used interchangeably therewith. A second DTX of a cell may be a second DTX operation of the cell, or may be used interchangeably therewith. A second DTX may be associated with a second TRP (e.g., TRP2). One or more configuration parameters may indicate a second DTX for energy saving of a second TRP.

[0329] A wireless device may transmit and / or report capability messages (e.g., wireless device capability messages) indicating support and / or capability (e.g., twoDTXcapability) for two DTX configurations for a cell. One or more configuration parameters may include one or more second DTX configuration parameters indicating a second DTX, for example, based on transmitting and / or reporting capability messages indicating support and / or capability (e.g., twoDTXcapability) for two DTX configurations for a cell. A base station may transmit to a wireless device one or more second DTX configuration parameters indicating a second DTX, for example, based on receiving capability messages indicating support and / or capability (e.g., twoDTXcapability) for two DTX configurations for a cell. Based on receiving a capability message indicating, for example, support and / or capability (e.g., twoDTXcapability) for a cell, the base station may transmit (e.g., transmit) one or more configuration parameters to a cell indicating up to two DTXs (e.g., no DTX configuration, first DTX only, second DTX only, both first and second DTXs).

[0330] A wireless device does not have to transmit (e.g., transmit) and / or report capability messages indicating support and / or capability (e.g., twoDTXcapability) for a cell, and one or more configuration parameters do not have to include one or more second DTX configuration parameters indicating a second DTX, for example, based on not transmitting (e.g., transmit) and / or reporting capability messages indicating support and / or capability (e.g., twoDTXcapability) for a cell. A base station does not have to transmit (e.g., transmit) one or more second DTX configuration parameters indicating a second DTX to a wireless device, for example, based on not receiving capability messages indicating support and / or capability (e.g., twoDTXcapability) for a cell. A base station may transmit (e.g., transmit) one or more first DTX configuration parameters indicating a first DTX to a wireless device, for example, based on not receiving capability messages indicating support and / or capability (e.g., twoDTXcapability) for a cell. Based on the fact that the base station does not receive a capability message indicating support for and / or capability of two DTX configurations for a cell (e.g., twoDTXcapability), it may transmit (e.g., transmit) one or more configuration parameters to the radio device indicating a maximum of one DTX for a cell (e.g., only the first DTX or no DTX configuration).

[0331] One or more configuration parameters may indicate at least two DRXs for a cell. These at least two DRXs of a cell may constitute, or be used interchangeably with, at least two DRX configurations of the cell. These at least two DRXs of a cell may constitute, or be used interchangeably with, at least two DRX operations of the cell.

[0332] One or more configuration parameters may include one or more first DRX configuration parameters (e.g., TRP-DRX-Config, TRP-DRX-Config1, TRP1-DRX-Config, DRX-Config, DRX-Config1, etc.) that indicate a first DRX of the cell (e.g., a first DRX as described herein in Figure 18). At least two DRXs of a cell may constitute the first DRX of the cell. The first DRX of a cell may be a first DRX configuration of the cell, or may be used interchangeably therewith. The first DRX of a cell may be a first DRX operation of the cell, or may be used interchangeably therewith. The first DRX may be associated with a first TRP (e.g., TRP1). One or more configuration parameters may indicate a first DRX for energy saving of a first TRP.

[0333] One or more configuration parameters may include one or more second DRX configuration parameters (e.g., TRP-DRX-Config2, TRP2-DRX-Config, DRX-Config2, etc.) indicating a second DRX of the cell (e.g., a second DRX as described herein in Figure 18). At least two DRXs of a cell may include a second DRX of the cell. A second DRX of a cell may be a second DRX configuration of the cell, or may be used interchangeably therewith. A second DRX of a cell may be a second DRX operation of the cell, or may be used interchangeably therewith. A second DRX may be associated with a second TRP (e.g., TRP2). One or more configuration parameters may indicate a second DRX for energy saving of a second TRP.

[0334] The wireless device may receive control commands (e.g., a third control command at time T3 as described herein in Figure 18). The control commands may be, for example, DCIs (e.g., DCI format 2_9, DCI format 2_10, etc.). The control commands may indicate the activation of at least two DTXs of the cell. The control commands may include DTXs and / or DRXs (e.g., TRP DTX / DRX) having a value (e.g., 1) indicating the activation of the cell's DTXs. The DTXs and / or DRXs may be associated with (or correspond to) the cell's DTXs. The wireless device may activate the cell's DTXs based on receiving the control commands.

[0335] A wireless device may receive a second control command (e.g., a third control command at time T3, as described herein in Figure 18) after a first control command (e.g., a second control command at time T3, as described herein in Figure 18). A wireless device may receive a second control command (e.g., a third control command at time T3, as described herein in Figure 18) before a first control command (e.g., a second control command at time T3, as described herein in Figure 18). A wireless device may receive a second control command (e.g., a third control command at time T3, as described herein in Figure 18) and a first control command (e.g., a second control command at time T3, as described herein in Figure 18) during the same PDCCH monitoring opportunity. A wireless device may receive a second control command (e.g., a third control command at time T3, as described herein in Figure 18) if it is in the active time, duration, and / or period of the DTX. The wireless device may receive a second control command (e.g., a third control command at time T3, as described herein in Figure 18) when it is in an inactive time, duration, and / or period of the DTX.

[0336] The value of the DTX and / or DRX bit within one or more blocks (e.g., "1") may indicate the activation of the cell's DTX. Blocks may be associated with cells, and one or more configuration parameters may indicate the starting position of the block or the starting position of the DTX for a cell. Bits may be associated with or correspond to the cell's DTX.

[0337] DTX can be, for example, a first DTX. DTX can be, for example, a second DTX. The cell's DTX can be the cell's DTX configuration, or can be used interchangeably therewith. The cell's DTX can be the cell's DTX operation, or can be used interchangeably therewith.

[0338] Figures 20A and 20B show examples of control commands. A control command (e.g., a third control command at time T3 as described herein in Figure 18) may include one or more blocks (e.g., block 1 2005a, block 2 2010a, block 3 2015a, ..., block N-1 2020a, block N 2025a in Figure 20A, and block 1 2005b, block 2 2010b, block 3 2015b, ..., block N-1 2020b, block N 2025b in Figure 20B).

[0339] The size (e.g., length) of each block in one or more blocks may be one or more bits (e.g., 1 bit, 2 bits, 3 bits, 4 bits). Each block may contain its respective DTX and / or DRX (e.g., TRP DTX / DRX indicator field). Each bit of the DTX and / or DRX (e.g., TRP DTX / DRX indicator field) within one or more blocks may indicate the activation or deactivation of one of the first DTX, second DTX, first DRX, and second DRX. A first value (e.g., "0") for a bit in the DTX / DRX indicator field may indicate the deactivation of a DTX or DRX among the first DTX, second DTX, first DRX, and second DRX, and the bit corresponds to or is associated with a DTX or DRX. A second value (e.g., "1") for a bit in the DTX / DRX indicator field may indicate the activation of either the DTX or DRX among the first DTX, second DTX, first DRX, and second DRX, and the bit corresponds to or is associated with the DTX or DRX.

[0340] A block among one or more blocks (for example, block 1 2005a or the DTX / DRX indicator field of block 1 2005a in Figure 20A) may be 4 bits if, for example, a first DTX, a second DTX, a first DRX, and a second DRX are indicated and / or configured for a cell by one or more configuration parameters. The most significant bit (MSB) of the 4 bits of the block may correspond to the first DTX (e.g., DTX1 in Figure 20A). The second MSB of the 4 bits of the block may correspond to the first DRX (e.g., DRX1 in Figure 20A). The least significant bit (LSB) of the 4 bits of the block may correspond to the second DRX (e.g., DRX2 in Figure 20A). The third MSB or second LSB of the 4 bits of the block may correspond to the second DTX (e.g., DTX2 in Figure 20A). The block may include a DTX / DRX indicator field (e.g., 4 bits).

[0341] A first value (e.g., "0") for the MSB in the DTX / DRX indicator field may indicate the deactivation of the first DTX. A second value (e.g., "1") for the MSB in the DTX / DRX indicator field may indicate the activation of the first DTX.

[0342] A first value (e.g., "0") for the second MSB in the DTX / DRX indicator field may indicate the deactivation of the first DRX. A second value (e.g., "1") for the second MSB in the DTX / DRX indicator field may indicate the activation of the first DRX.

[0343] A first value (e.g., "0") for the LSB in the DTX / DRX indicator field may indicate the deactivation of the second DRX. A second value (e.g., "1") for the LSB in the DTX / DRX indicator field may indicate the activation of the second DRX.

[0344] A first value (e.g., "0") for the second LSB in the DTX / DRX indicator field may indicate the deactivation of the second DTX. A second value (e.g., "1") for the second LSB in the DTX / DRX indicator field may indicate the activation of the second DTX.

[0345] For example, a block among one or more blocks (e.g., block 3 in Figure 20A or the DTX / DRX indicator field of block 3) may be 2 bits if the first DTX and the second DTX are indicated and / or configured for the cell by one or more configuration parameters. The 2-bit MSB of the block may correspond to the first DTX (e.g., DTX1 in Figure 20A). The 2-bit LSB of the block may correspond to the second DTX (e.g., DTX2 in Figure 20A). The first and second DRX may or may not be indicated and / or configured for the cell by one or more configuration parameters. A block may include a DTX / DRX indicator field (e.g., 2 bits).

[0346] A first value (e.g., "0") for the MSB in the DTX / DRX indicator field may indicate the deactivation of the first DTX. A second value (e.g., "1") for the MSB in the DTX / DRX indicator field may indicate the activation of the first DTX.

[0347] A first value (e.g., "0") for the LSB in the DTX / DRX indicator field may indicate the deactivation of the second DTX. A second value (e.g., "1") for the LSB in the DTX / DRX indicator field may indicate the activation of the second DTX.

[0348] For example, a block among one or more blocks may have 2 bits if the first DRX and the second DRX are indicated and / or configured for the cell by one or more configuration parameters. The 2 bits MSB of the block may correspond to the first DRX. The 2 bits LSB of the block may correspond to the second DRX. The first DTX and the second DTX may or may not be indicated and / or configured for the cell by one or more configuration parameters.

[0349] For example, a block among one or more blocks may have 2 bits if the first DTX and second DRX are indicated and / or configured for the cell by one or more configuration parameters. The 2 bits MSB of the block may correspond to the first DTX. The 2 bits LSB of the block may correspond to the second DRX. The second DTX and the first DRX may or may not be indicated and / or configured for the cell by one or more configuration parameters.

[0350] For example, a block among one or more blocks may be 2 bits if two of the first DTX, second DTX, first DRX, and second DRX are indicated and / or configured for a cell by one or more configuration parameters. For example, a block may contain one of {[DTX1, DRX1], [DTX1, DRX2], [DTX1, DTX2], [DRX1, DRX2], [DRX1, DTX2], [DTX2, DRX2]}.

[0351] For example, a block among one or more blocks (e.g., block N-1 in Figure 20A or the DTX / DRX indicator field of block N-1) may be 3 bits if the first DTX, first DRX, and second DRX are indicated and / or configured for the cell by one or more configuration parameters. The 3-bit MSB of the block may correspond to the first DTX (e.g., DTX1 in Figure 20A). The 3-bit second MSB of the block may correspond to the first DRX (e.g., DRX1 in Figure 20A). The 3-bit LSB of the block may correspond to the second DRX (e.g., DRX2 in Figure 20A). The second DTX may or may not be indicated and / or configured for the cell by one or more configuration parameters.

[0352] For example, a block among one or more blocks (e.g., block N in Figure 20A or the DTX / DRX indicator field of block N) may be 3 bits if the first DTX, first DRX, and second DTX are indicated and / or configured for the cell by one or more configuration parameters. The 3-bit MSB of the block may correspond to the first DTX (e.g., DTX1 in Figure 20A). The 3-bit second MSB of the block may correspond to the first DRX (e.g., DRX1 in Figure 20A). The 3-bit LSB of the block may correspond to the second DTX (e.g., DTX2 in Figure 20A). The second DRX may or may not be indicated and / or configured for the cell by one or more configuration parameters.

[0353] For example, a block among one or more blocks may be 3 bits if three of the first DTX, second DTX, first DRX, and second DRX are indicated and / or configured for a cell by one or more configuration parameters. For example, a block may contain one of {[DTX1, DRX1, DTX2], [DTX1, DRX1, DRX2], [DTX1, DTX2, DRX2], [DRX1, DTX2, DRX2]}.

[0354] For example, a block among one or more blocks may be 1 bit if one of the first DTX, second DTX, first DRX, and second DRX is indicated and / or configured for a cell by one or more configuration parameters. For example, a block may contain one of {[DTX1], [DRX1], [DTX2], [DRX2]}.

[0355] The starting positions of the DTX and / or DRX (or DTX / DRX indicator fields) of a TRP in a block of one or more blocks may be determined by the radio device and / or base station by a position parameter (e.g., positionInDCI-TRPDTRX). One or more configuration parameters may include a position parameter. For example, a radio device configured to have (or function by having) both a first TRP and a second TRP may be indicated by the starting position of the block (e.g., the starting position of DTX1 in block 1 in Figure 20A). The position parameter may indicate the starting position of the block. For example, a radio device configured to have (or function by having) only a first TRP may be indicated by the starting position of the block (e.g., the starting position of DTX1 in block 1 in Figure 20A). The position parameter may indicate the starting position of the block. The radio discards / ignores DTX2 and DRX2 in the block that are associated with the second TRP. For example, a wireless device configured to have only a second TRP (or functioning thereby) may be indicated by the starting position of the DTX and / or DRX (or the DTX / DRX indicator fields in the block) associated with the second TRP (e.g., the starting position of DTX2 in block 1 in Figure 20A). The position parameter may indicate the starting position of the DTX and / or DRX in the block associated with the second TRP. The wireless device discards / ignores DTX1 and DRX1 in the block associated with the first TRP.

[0356] The size (e.g., length) of each block in one or more blocks may be at least two bits (e.g., 2 bits, 3 bits). Each block may contain its respective DTX / DRX indicator field (e.g., DTX / DRX indicator field), and its respective index, indicator, and / or identifier field (e.g., TRP index, indicator, and / or identifier, core set pool index, SRS resource set index, indicator, and / or identifier, antenna panel index, indicator, and / or identifier, physical cell index, indicator, and / or identifier, etc.). The index, indicator, and / or identifier field within one or more blocks may be 1 bit. The index, indicator, and / or identifier field within each block in one or more blocks may be 1 bit.

[0357] Each bit in the DTX / DRX indicator field within a block (e.g., DTX / DRX indicator field) may indicate the activation or deactivation of one of the first DTX and first DRX if, for example, the value of the index, indicator, and / or identifier field within one or more blocks is equal to and / or set to a first value (e.g., 0). A first value (e.g., "0") for a bit in the DTX / DRX indicator field within a block may indicate the deactivation of the first DTX or first DRX, with the bit corresponding to or associated with the first DTX or first DRX, respectively. A second value (e.g., "1") for a bit in the DTX / DRX indicator field within a block may indicate the activation of the first DTX and first DRX, with the bit corresponding to or associated with the first DTX or first DRX, respectively.

[0358] Each bit in the DTX / DRX indicator field within a block (e.g., DTX / DRX indicator field) may indicate the activation or deactivation of one of the second DTX and second DRX if, for example, the value of the index, indicator, and / or identifier field within one or more blocks is equal to and / or set to a second value (e.g., 1). A first value for a bit in the DTX / DRX indicator field (e.g., "0") may indicate the deactivation of the second DTX or second DRX, with each bit corresponding to or associated with the second DTX or second DRX, respectively. A second value for a bit in the DTX / DRX indicator field (e.g., "1") may indicate the activation of the second DTX or second DRX, with each bit corresponding to or associated with the second DTX or second DRX, respectively.

[0359] Index, indicator, and / or identifier fields within a block may be located after (e.g., positioned before) the DTX / DRX indicator field within the block. Index, indicator, and / or identifier fields within a block may not be located before (e.g., not positioned before) the DTX / DRX indicator field within the block.

[0360] A block can be 3 bits if, for example, the index, indicator, and / or identifier fields within one or more blocks (e.g., block 1 2005b in Figure 20B) are equal to and / or set to a first value (e.g., 0), and the first DTX and first DRX are indicated and / or configured for a cell by one or more configuration parameters. The most significant bit (MSB) of the 3 bits of the block may correspond to the first DTX (e.g., DTX1 2030e in Figure 20B). The second MSB of the 3 bits of the block may correspond to the first DRX (e.g., DRX1 2035e in Figure 20B). The least significant bit (LSB) of the 3 bits of the block may correspond to the index, indicator, and / or identifier field 2050ed (e.g., 0 in block 1 2005 in Figure 20B). A block may include an index, indicator, and / or identifier field (e.g., 1 bit) and a DTX / DRX indicator field (e.g., 2 bits).

[0361] A first value (e.g., "0") for the MSB in the DTX / DRX indicator field may indicate the deactivation of the first DTX. A second value (e.g., "1") for the MSB in the DTX / DRX indicator field may indicate the activation of the first DTX.

[0362] A first value (e.g., "0") for the second MSB in the DTX / DRX indicator field may indicate the deactivation of the first DRX. A second value (e.g., "1") for the second MSB in the DTX / DRX indicator field may indicate the activation of the first DRX.

[0363] A block can be 3 bits if, for example, a second DTX and a second DRX are indicated and / or configured for a cell by one or more configuration parameters, and if the index, indicator, and / or identifier field 2050f in block 2015b (e.g., block 3 in Figure 20B) of one or more blocks is equal to and / or set to a second value (e.g., 1). The most significant bit (MSB) of the 3 bits of the block may correspond to the second DTX 2040f (e.g., DTX2 in Figure 20B). The second MSB of the 3 bits of the block may correspond to the second DRX 2045f (e.g., DRX2 in Figure 20B). The least significant bit (LSB) of the 3 bits of the block may correspond to the index, indicator, and / or identifier field 2050f (e.g., 1 in block 3 in Figure 20B). A block may include an index, indicator, and / or identifier field (e.g., 1 bit) and a DTX / DRX indicator field (e.g., 2 bits).

[0364] A first value (e.g., "0") for the MSB in the DTX / DRX indicator field may indicate the deactivation of the second DTX. A second value (e.g., "1") for the MSB in the DTX / DRX indicator field may indicate the activation of the second DTX.

[0365] A first value (e.g., "0") for the second MSB in the DTX / DRX indicator field may indicate the deactivation of the second DRX. A second value (e.g., "1") for the second MSB in the DTX / DRX indicator field may indicate the activation of the second DRX.

[0366] A block can be 2 bits if, for example, the index, indicator, and / or identifier field 2030g in block 2020b (e.g., block N-1 in Figure 20B) of one or more blocks is equal to and / or set to a first value (e.g., 0), and either the first DTX or the first DRX (e.g., only one of the first DTX and the first DRX) is indicated to and / or configured for a cell by one or more configuration parameters. The most significant bit (MSB) of the 2 bits of the block may correspond to the first DTX2030g (e.g., DTX1 in Figure 20B) or the first DRX. The least significant bit (LSB) of the 2 bits of the block may correspond to the index, indicator, and / or identifier field 2050g (e.g., 0 in block N-1 in Figure 20B). A block may include an index, indicator, and / or identifier field (e.g., 1 bit) and a D...

Claims

1. It is a method, By wireless devices, A repeating scheme parameter indicating a time-domain scheme or a frequency-domain scheme, Receiving one or more messages that include a downlink or joint TCI status list parameter indicating a list of transmission configuration instruction (TCI) statuses for both uplink transmission and downlink reception, Receiving downlink control information (DCI) configured to schedule the reception of a physical downlink shared channel (PDSCH), A method comprising receiving the PDSCH reception using the two TCI states in non-overlapping resources indicated by the repeating scheme parameter, based on a TCI selection field in the DCI indicating that two TCI states are applied to the PDSCH reception.

2. The DCI further includes a time domain resource allocation field indicating the number of repetitions, and the PDSCH reception is received using the two TCI states. The method according to claim 1, comprising receiving the PDSCH reception using the two TCI states in consecutive time slots, based on the TCI selection field in the DCI indicating that two TCI states are to be applied to the PDSCH reception, or based on the absence of the TCI selection field in the DCI, wherein the number of consecutive time slots is equal to the number of repetitions.

3. Receiving a second DCI configured to schedule the reception of a second PDSCH, Based on the fact that the TCI selection field in the second DCI indicates that two TCI states are applied to the second PDSCH reception, the second PDSCH reception is performed A first demodulation reference signal (DM-RS) port associated with the first TCI state among the two TCI states, and The method according to claim 1 or 2, further comprising receiving using a second DM-RS port associated with a second TCI state among the two TCI states.

4. Receiving a second DCI configured to schedule the reception of a second PDSCH, The method according to claim 1 or 2, further comprising receiving the second PDSCH reception using the two TCI states in non-overlapping resources indicated by the repeating parameter, based on the fact that the second DCI is not configured to have a TCI selection field.

5. The aforementioned repeating scheme parameters are set in the time domain scheme, The method according to any one of claims 1 to 4, wherein, based on the repetition scheme parameter being set in the time domain scheme, receiving the PDSCH reception using the two TCI states in non-overlapping resources is a method according to any one of claims 1 to 4, wherein receiving the PDSCH reception using the two TCI states in non-overlapping time domain resources is a method according to any one of claims 1 to 4.

6. The aforementioned repetition scheme parameters are set in the frequency domain scheme, The method according to any one of claims 1 to 4, wherein, based on the repetition scheme parameter being set in the frequency domain scheme, receiving the PDSCH reception using the two TCI states in non-overlapping resources is a method according to any one of claims 1 to 4, wherein receiving the PDSCH reception using the two TCI states in non-overlapping frequency domain resources is a method according to any one of claims 1 to 4.

7. The method according to any one of claims 1 to 6, wherein the DCI includes an antenna port field indicating one or more demodulated reference signal (DM-RS) ports in a code division multiplexing (CDM) group.

8. After receiving one or more of the aforementioned messages, and before receiving the DCI configured to schedule the PDSCH reception, The wireless device receives a media access control (MAC) control element (CE) configured to activate one or more TCI states in the list of TCI states, The method according to any one of claims 1 to 7, further comprising receiving a DCI indicating the two TCI states.

9. The method according to any one of claims 1 to 8, wherein the frequency domain scheme is one of a first frequency domain scheme and a second frequency domain scheme different from the first frequency domain scheme.

10. The method according to any one of claims 3 to 9, wherein the second DCI includes a TCI field different from the TCI selection field.

11. Using the two TCI states, the PDSCH reception is received as described above. Using the first TCI state among the two TCI states in the first time domain resource of the non-overlapping time domain resources, or in the first frequency domain resource of the non-overlapping time frequency resources, and The method according to any one of claims 1 to 10, comprising using the second TCI state of the two TCI states in the second time domain resource of the non-overlapping time domain resources, or in the second frequency domain resource of the non-overlapping time frequency resources.

12. Receiving one or more second messages containing a second repeating scheme parameter indicating a second time-domain scheme or a second frequency-domain scheme, Receiving a fourth DCI via a cell for scheduling or activating a second PDSCH reception, wherein the fourth DCI is A second antenna port field indicating one or more second DM-RS ports within a single CDM group, and Receiving includes a TCI field indicating two second TCI states for the second PDSCH reception, Based on the fact that the fourth DCI indicates the one or more DM-RS ports in a CDM group and the two second TCI states for the second PDSCH reception, In the case where the second repetition scheme parameter is set in the second time domain scheme, and in the non-overlapping time domain resources, The method according to any one of claims 1 to 11, further comprising receiving the second PDSCH reception using the second two TCI states in non-overlapping frequency domain resources when the second repetition scheme parameter is set to the second frequency domain scheme.

13. A wireless device, One or more processors, A wireless device comprising a memory for storing instructions, wherein when an instruction is executed by one or more processors, the wireless device causes the wireless device to perform the method according to any one of claims 1 to 12.

14. It is a system, A wireless device configured to carry out the method described in any one of claims 1 to 12, A system comprising: a base station configured to transmit the DCI, which is configured to schedule the reception of the PDSCH.

15. A computer-readable medium for storing instructions, wherein when an instruction is executed, the method described in any one of claims 1 to 12 is performed.

Images