Spatial domain energy saving

Abstract

Configuration parameters sent to the wireless device can indicate resources (and the repetition scheme that the wireless device can use for communication). An activation command for scheduled reception can instruct the use of at least two transmission configuration states for the scheduled reception. The wireless device can use the indicated two transmissions and the configured repetition scheme to receive the scheduled reception.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 539,138, filed September 19, 2023. The entire contents of the application cited above are incorporated herein by reference. 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 the resources used for transmission.

[0003] The following summary presents a simplified overview of certain features. This summary is neither a comprehensive overview nor intended to identify important or key elements. Summary of the Invention

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

[0005] These and other features and advantages are described in more detail below. Attached Figure Description

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

[0007] Figure 1A and Figure 1B An example communication network is shown.

[0008] Figure 2A An example user plane is shown.

[0009] Figure 2B An example control plane configuration is shown.

[0010] Figure 3 An example of a protocol layer is shown.

[0011] Figure 4A An example downlink data flow for user plane configuration is shown.

[0012] Figure 4B An example format of the MAC subheader in a Media Access Control (MAC) protocol data unit (PDU) is shown.

[0013] Figure 5A An example mapping of the downlink channel is shown.

[0014] Figure 5B An example mapping of the uplink channel is shown.

[0015] Figure 6 Example Radio Resource Control (RRC) states and RRC state transitions are shown.

[0016] Figure 7 An example configuration of the frame is shown.

[0017] Figure 8 An example resource configuration for one or more carriers is shown.

[0018] Figure 9 An example configuration for the Bandwidth Part (BWP) is shown.

[0019] Figure 10A An example carrier aggregation configuration based on component carriers is shown.

[0020] Figure 10B An example cell group is shown.

[0021] Figure 11A An example mapping of one or more Synchronization Signal / Physical Broadcast Channel (SS / PBCH) blocks is shown.

[0022] Figure 11B An example mapping of one or more Channel State Information Reference Signals (CSI-RS) is shown.

[0023] Figure 12A An example of a downlink beam management procedure is shown.

[0024] Figure 12B An example of an uplink beam management procedure is shown.

[0025] Figure 13A An example four-step random access procedure is shown.

[0026] Figure 13B An example two-step random access procedure is shown.

[0027] Figure 13C An example two-step random access procedure is shown.

[0028] Figure 14A An example of a control resource set (CORESET) configuration is shown.

[0029] Figure 14B An example of a control channel element to resource element group (CCE to REG) mapping is shown.

[0030] Figure 15A An example of communication between a wireless device and a base station is shown.

[0031] Figure 15B Example elements of a computing device that can be used to implement any of the various devices described herein are shown.

[0032] Figure 16A , Figure 16B , Figure 16C and Figure 16D Examples of uplink and downlink signal transmission are shown.

[0033] Figure 17A and Figure 17B This is a flowchart illustrating an example of communication used for energy saving.

[0034] Figure 18 An example of communication used for energy saving is shown.

[0035] Figure 19 An example of the activation command is shown.

[0036] Figure 20A and Figure 20B An example of a control command is shown.

[0037] Figures 21 to 23 An example of communication used for energy saving is shown.

[0038] Figure 24A and Figure 24B This is a flowchart illustrating an example of communication used for energy saving.

[0039] Figure 25A and Figure 25B This is a flowchart illustrating an example of communication used for energy saving. Detailed Implementation

[0040] The accompanying drawings and description provide examples. It should be understood that the examples shown and / or described in the drawings are non-exclusive, and the features shown and described can be practiced in other examples. Examples of operation for wireless communication systems are provided.

[0041] Figure 1AAn example communication network 100 is illustrated. Communication network 100 may include a mobile communication network. Communication network 100 may include, for example, a Public Land Mobile Network (PLMN) operated / managed / run by a network operator. Communication network 100 may include one or more of a core network (CN) 102, a radio access network (RAN) 104, and / or a radio device 106. Communication network 100 may include one or more data networks (DNs) 108, and / or devices within communication network 100 may communicate with (e.g., via CN 102) one or more data networks. Radio device 106 may communicate with one or more DNs 108, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. Radio device 106 may communicate with one or more DNs 108 via RAN 104 and / or via CN 102. CN 102 may provide / configure one or more interfaces to radio device 106 that interface with one or more DNs 108. As part of the interface functionality, CN 102 can set up end-to-end connections between wireless device 106 and one or more DN 108, authenticate wireless device 106, provide / configure charging functionality, etc.

[0042] Radio device 106 can communicate with RAN 104 via radio communication through an air interface. RAN 104 can communicate with CN 102 via various communications (e.g., wired and / or wireless communications). Radio device 106 can establish a connection with CN 102 via RAN 104. RAN 104 can provide / configure scheduling, radio resource management, and / or retransmission protocols, for example, as part of radio communication. The communication direction from RAN 104 to radio device 106 via the air interface can be referred to as downlink and / or downlink communication direction. The communication direction from radio device 106 to RAN 104 via the air interface can be referred to as uplink and / or uplink communication direction. Downlink transmissions can be separated from and / or distinguished from uplink transmissions, for example, based on at least one of the following: frequency division duplex (FDD), time division duplex (TDD), any other duplex scheme, and / or one or more combinations thereof.

[0043] As used throughout, the term "wireless device" can include one or more of the following: mobile device, fixed (e.g., non-mobile) device configured or capable of wireless communication, computing device, node, device capable of wireless communication, or any other device capable of transmitting and / or receiving signals. As a non-limiting example, a wireless device can include, for example: telephone, cellular phone, Wi-Fi phone, smartphone, tablet computer, computer, laptop computer, sensor, instrument, wearable device, Internet of Things (IoT) device, hotspot, cellular repeater, vehicle roadside unit (RSU), relay node, automobile, wireless user equipment (e.g., user equipment (UE), user terminal (UT), etc.), access terminal (AT), mobile station, handheld device, wireless transmit and receive unit (WTRU), wireless communication device, and / or any combination thereof.

[0044] RAN 104 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), evolved 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), transmit and receive point (TRP), computing device, device capable of wireless communication, 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. As other non-limiting examples, a base station may include one or more of the following: a Node B (e.g., associated with Universal Mobile Telecommunications System (UMTS) and / or third-generation (3G) standards), an evolved Node B (eNB) (e.g., associated with Evolved Universal Terrestrial Radio Access (E-UTRA) and / or fourth-generation (4G) standards), a Remote Radio Header (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node for extending the coverage area of ​​a donor node, a Next Generation Evolved Node B (ng-eNB), a Second Generation Node B (gNB) (e.g., associated with NR and / or fifth-generation (5G) standards), an Access Point (AP) (e.g., associated with, for example, Wi-Fi or any other suitable wireless communication standard), any other generation of base stations, 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)).

[0045] A base station (e.g., in RAN 104) may include one or more sets of antennas for wireless communication with the wireless device 106 (e.g., via an air interface). One or more base stations may include multiple sets (e.g., three sets or any other number of sets) of antennas to control multiple cells or sectors (e.g., three cells, three sectors, any other number of cells, or any other number of sectors) respectively. The size of a cell may be determined by the range within which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in 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 wireless device 106 over a wide geographical area to support wireless device mobility. A base station including three sectors (e.g., or n sectors, where n represents any number of n) may be referred to as a three-sector site (e.g., or an n-sector site) or a three-sector base station (e.g., an n-sector base station).

[0046] One or more base stations (e.g., in RAN 104) can be implemented as sector sites with more or fewer than three sectors. One or more base stations in RAN 104 can be implemented as access points, baseband processing units / units coupled to several RRHs, and / or repeaters or relay nodes for extending the coverage area of ​​nodes (e.g., donor nodes). Baseband processing units / units coupled to RRHs can be part of a centralized or cloud RAN architecture, for example, where baseband processing units / units can be centralized in a pool of baseband processing units / units or virtualized. Repeater nodes can amplify and transmit (e.g., transmit, retransmit, rebroadcast, etc.) radio signals received from donor nodes. Relay nodes can perform substantially the same / similar functions as repeater nodes. Relay nodes can decode radio signals received from donor nodes, for example, to remove noise before amplifying and transmitting the radio signals.

[0047] RAN 104 can be deployed as a homogeneous network of base stations (e.g., macrocell base stations) with similar antenna patterns and / or similar high levels of transmission power. RAN 104 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, such as coverage areas overlapping 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 with high data traffic (or so-called "hot spots") or in areas with weak macrocell coverage. Examples of small cell base stations can include (in descending order of coverage area) microcell base stations, picocell base stations, femtocell base stations, or femtocell base stations.

[0048] The examples described herein can be used for various types of communications. For instance, communications can be based on the 3rd Generation Partnership Project (3GPP) (e.g., one or more network elements similar to a network element in a communications network 100), communications according to the Institute of Electrical and Electronics Engineers (IEEE), communications according to the International Telecommunication Union (ITU), communications according to the International Organization for Standardization (ISO), and so on. 3GPP specifies multiple generations of mobile networks: 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 can also specify other generations of communications networks (e.g., 6G and / or any other generation of communications networks). Examples can be described by referring to one or more elements (e.g., RAN) of a 3GPP 5G network (known as Next Generation RAN (NG-RAN)) or any other communications network (such as 3GPP networks and / or non-3GPP networks). The examples described herein can be applied to other communication networks, such as 3G and / or 4G networks, as well as communication networks that may not yet be finalized / designated (e.g., 3GPP 6G networks), satellite communication networks, and / or any other communication networks. NG-RAN implements and updates 5G radio access technology known as NR and can be configured to implement 4G radio access and / or other radio access technologies, such as other 3GPP and / or non-3GPP radio access technologies.

[0049] Figure 1B An example communication network 150 is illustrated. This communication network may include a mobile communication network. Communication network 150 may include, for example, a PLMN operated / managed / run by a network operator. 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., NG-RAN), and / or radio devices 156A and 156B (collectively referred to as radio devices 156). Communication network 150 may include one or more data networks (DN) 170, and / or devices within communication network 150 may communicate with (e.g., via CN 152) one or more data networks. These components are capable of communicating with... Figure 1A The corresponding components described are implemented and operated in essentially the same or similar manner.

[0050] A CN 152 (e.g., a 5G-CN) can provide / configure one or more interfaces to a radio device 156 that interface with one or more DNs 170 (such as public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs). As part of the interface functions, the CN 152 (e.g., a 5G-CN) can establish end-to-end connections between the radio device 156 and one or more DNs, authenticate the radio device 156, and / or provide / configure charging functions. The CN 152 (e.g., a 5G-CN) can be a service-based architecture, which may differ from other CNs (e.g., 3GPP 4G CNs). The architecture of a node of a CN 152 (e.g., a 5G-CN) can be defined as a network function that provides services to other network functions via interfaces. The network functions of a CN 152 (e.g., a 5G CN) can be implemented in several ways, such as 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).

[0051] CN 152 (e.g., 5G-CN) may include Access and Mobility Management Function (AMF) device 158A and / or User Plane Function (UPF) device 158B, which may be a separate component or a single AMF / UPF device 158. UPF device 158B may serve as a gateway between RAN 154 (e.g., NG-RAN) and one or more DNs 170. UPF device 158B may perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification supporting traffic flow routing to one or more DNs 170, user plane Quality of Service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink service authentication), downlink packet buffering, and / or downlink data notification triggering. UPF device 158B may serve as an anchor point for intra / inter-Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session point interconnected with one or more DNs, and / or a branch point supporting multi-homed PDU sessions. The wireless device 156 can be configured to receive services via a PDU session, which can be a logical connection between the wireless device and the DN.

[0052] The AMF device 158A can perform functions such as: Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN signaling for mobility between access networks (e.g., 3GPP access networks and / or non-3GPP networks), idle-mode radio device reachability (e.g., idle-mode UE reachability for controlling and performing paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights checks, mobility management control (e.g., subscriptions and policies), network slicing support, and / or Session Management Function (SMF) selection. NAS can refer to functions operating between the CN and the radio device, and AS can refer to functions operating between the radio device and the RAN.

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

[0054] RAN 154 (e.g., NG-RAN) may communicate with radio device 156 via radio communication (e.g., through an air interface). Radio device 156 may communicate with CN 152 via RAN 154. RAN 154 (e.g., NG-RAN) may include one or more first-type base stations (e.g., gNBs including gNB 160A and gNB 160B (collectively referred to as gNB 160)) and / or one or more second-type base stations (e.g., ng eNBs including ng-eNB 162A and ng-eNB 162B (collectively referred to as ng eNB 162)). RAN 154 may include one or more of any number of types of base stations. gNB 160 and ng eNB 162 may be referred to as base stations. Base stations (e.g., gNB 160 and ng eNB 162) may include one or more sets of antennas for wireless communication with radio device 156 (e.g., through an air interface). One or more base stations (e.g., gNB 160 and / or ng eNB 162) may include multiple sets of antennas to control multiple cells (or sectors) separately. The cells of the base stations (e.g., gNB 160 and ng-eNB 162) can provide radio coverage to the wireless device 156 over a wide geographical area to support the mobility of the wireless device.

[0055] Base stations (e.g., gNB 160 and / or ng-eNB 162) can connect to CN 152 (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 can be established using direct physical connections and / or indirect connections via underlying transport networks (such as Internet Protocol (IP) transport networks). Base stations (e.g., gNB 160 and / or ng-eNB 162) can communicate with wireless device 156 via a third interface (e.g., Uu interface). Base station (e.g., gNB 160A) can communicate with wireless device 156A via the Uu interface. The NG, Xn, and Uu interfaces can be associated with a protocol stack. The protocol stack associated with the interface can be... Figure 1B The network elements shown are used to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. Any other number of planes can be used (e.g., in the protocol stack). The user plane can handle data that is of interest to the user. The control plane can handle signaling messages that are of interest to the network elements.

[0056] One or more base stations (e.g., gNB 160 and / or ng-eNB 162) may communicate with one or more AMF / UPF devices (such as AMF / UPF 158) via one or more interfaces (e.g., NG interfaces). A base station (e.g., gNB 160A) may communicate and / or connect to UPF 158B of AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface may provide / perform the delivery (e.g., non-guaranteed delivery) of user plane PDUs between the base station (e.g., gNB 160A) and the UPF device (e.g., UPF 158B). A base station (e.g., gNB 160A) may communicate and / or connect to an AMF device (e.g., AMF 158A) via an NG control plane (NG-C) interface. The NG-C interface can provide / perform functions such as NG interface management, radio device context management (e.g., UE context management), radio device mobility management (e.g., UE mobility management), NAS message delivery, paging, PDU session management, configuration transfer, and / or warning message delivery.

[0057] The wireless device can access the base station via an interface (e.g., a Uu interface) for user plane and control plane configuration. The base station (e.g., gNB 160) can provide user plane and control plane protocol terminals to the wireless device 156 via the Uu interface. The base station (e.g., gNB 160A) can provide user plane and control plane protocol terminals to the wireless device 156A via a Uu interface associated with a first protocol stack. The base station (e.g., ng-eNB 162) can provide evolved UMTS Terrestrial Radio Access (E UTRA) user plane and control plane protocol terminals to the wireless device 156 via the Uu interface (e.g., where E UTRA may refer to 3GPP 4G radio access technology). The base station (e.g., ng-eNB 162B) can provide E UTRA user plane and control plane protocol terminals to the wireless device 156B via a Uu interface associated with a second protocol stack. The user plane and control plane protocol terminals may include, for example, NR user plane and control plane protocol terminals, 4G user plane and control plane protocol terminals, etc.

[0058] CN 152 (e.g., 5G-CN) can be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). The NR network / device (or any first network / device) can also 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 can be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although... Figure 1B Only one AMF / UPF 158 is shown, but one or more base stations (e.g., one or more gNBs and / or one or more ng-eNBs) can connect to multiple AMF / UPF nodes, for example, to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

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

[0060] Figure 1A The communication network 100 and / or Figure 1BThe communication network 150 may include any number and / or type of devices, such as computing devices, wireless devices, mobile devices, handheld devices, tablet computers, laptop computers, Internet of Things (IoT) devices, hotspots, cellular repeaters, and / or more generally user equipment (e.g., UE). Although reference may be made herein to one or more devices of the types described above (e.g., UE, wireless device, computing device, etc.), it should be understood that any device herein may include any one or more devices of the types described above or similar devices. The communication network and any other networks mentioned herein may include LTE networks, 5G networks, satellite networks, and / or any other networks used for wireless communication (e.g., any 3GPP network and / or any non-3GPP network). The devices, systems, and / or methods described herein may generally be described as being implemented on one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks; however, it should be understood that one or more features and steps may be implemented in any device and / or any network.

[0061] Figure 2A An example user plane configuration is shown. This user plane configuration may include, for example, the NR user plane protocol stack. Figure 2B An example control plane configuration is shown. This control plane configuration may include, for example, an NR control plane protocol stack. One or more of the user plane configuration and / or control plane configuration may use a Uu interface that may be located between the wireless device 210 and the base station 220. Figure 2A and Figure 2B The protocol stack shown can be used with, for example, Figure 1B The protocol stack of the Uu interface between the wireless device 156A and the base station 160A shown is basically the same or similar.

[0062] User plane configuration (e.g., NR user plane protocol stack) may be included in the wireless device 210 and base station 220 (e.g., ... Figure 2AThe protocol stack implements multiple layers (e.g., five layers or any other number of layers). At the bottom of the protocol stack, the physical layers (PHY) 211 and 221 can provide transport services to higher layers of the protocol stack and can correspond to Layer 1 of the Open Systems Interconnection (OSI) model. Protocol layers above PHY 211 may include Media Access Control (MAC) 212, Radio Link Control (RLC) 213, Packet Data Convergence Protocol (PDCP) 214, and / or Service Data Application Protocol (SDAP) 215. Protocol layers above PHY 221 may include Media Access Control (MAC) 222, Radio Link Control (RLC) 223, Packet Data Convergence Protocol (PDCP) 224, and / or Service Data Application Protocol (SDAP) 225. One or more of the four protocol layers above PHY 211 can correspond to Layer 2 or the data link layer of the OSI model. One or more of the four protocol layers above PHY 221 can correspond to Layer 2 or the data link layer of the OSI model.

[0063] Figure 3 An example of a protocol layer is shown. A protocol layer can include, for example, the NR user plane protocol stack. One or more services can be provided between protocol layers. SDAP (e.g., Figure 2A and Figure 3SDAPs 215 and 225 (shown) can perform Quality of Service (QoS) stream processing. Wireless devices (e.g., wireless devices 106, 156A, 156B, and 210) can receive services via / through a PDU session, which can be a logical connection between the wireless device and the DN. This PDU session can have one or more QoS streams 310. The DN's UPF (e.g., UPF 158B) can map IP packets to these one or more QoS streams of the PDU session, for example, based on one or more QoS requirements (e.g., based on latency, data rate, bit error rate, and / or any other quality / service requirements). SDAPs 215 and 225 can perform mapping / demapping between these one or more QoS streams 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / demapping between these one or more QoS streams 310 and radio bearers 320 can be determined by SDAP 225 of base station 220. The SDAP 215 of the wireless device 210 can be informed of the mapping between QoS flow 310 and radio bearer 320 via reflection mapping and / or control signaling received from base station 220. For reflection mapping, the SDAP 225 of base station 220 can mark downlink packets with QoS flow indicator (QFI), and the SDAP 215 of wireless device 210 can monitor / detect / identify / indicate / observe the QoS flow indicator to determine the mapping / demapping between the one or more QoS flows 310 and radio bearer 320.

[0064] PDCP (e.g., Figure 2A and Figure 3 PDCPs 214 and 224 (shown) can perform header compression / decompression, for example, to reduce the amount of data that may need to be transmitted (e.g., sent) over the air interface, perform encryption / decryption to prevent unauthorized decoding of data transmitted (e.g., sent) over the air interface, and / or perform integrity protection (e.g., to ensure that control messages originate from their intended source). PDCPs 214 and 224 can perform retransmission of undelivered packets, sequential delivery and reordering of packets, and / or removal of duplicate packets received due to, for example, handover (e.g., intra-gNB handover). PDCPs 214 and 224 can perform packet duplication, for example, to increase the likelihood of packets being received. The receiver can repeatedly receive packets and can remove any duplicate packets. Packet duplication can be used for certain services, such as those requiring high reliability.

[0065] PDCP layers (e.g., PDCP 214 and 224) can perform mapping / demapping between separate radio bearers and RLC channels (e.g., RLC channel 330) (e.g., in a dual-connectivity scenario / configuration). Dual connectivity can refer to a technique that allows a radio device to communicate with multiple cells (e.g., two cells) or more generally, multiple cell groups including a primary cell group (MCG) and a secondary cell group (SCG). For example, if a single radio bearer (e.g., one of the radio bearers provided / configured by PDCP 214 and 224 for service to SDAP 215 and 225) is handled by a cell group in dual connectivity, a separate bearer can be configured and / or used. PDCP 214 and 224 can perform mapping / demapping between the separate radio bearer and RLC channel 330 belonging to the cell group.

[0066] The RLC layer (e.g., RLC 213 and 223) can perform segmentation, retransmission via Automatic Repeat Request (ARQ), and / or removal of duplicate data units received from the MAC layer (e.g., MAC 212 and 222, respectively). The RLC layer (e.g., RLC 213 and 223) can support multiple transmission modes (e.g., three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM)). The RLC layer can perform one or more of the labeled functions, for example, based on the transmission mode in which the RLC layer is operating. RLC configuration can be per logical channel. RLC configuration may not depend on the parameter set and / or Transmission Time Interval (TTI) duration (or other durations). The RLC layer (e.g., RLC 213 and 223) can provide / configure the RLC channel as a service for the PDCP layer (e.g., PDCP 214 and 224, respectively), such as... Figure 3 As shown.

[0067] The MAC layer (e.g., MAC 212 and 222) can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing may include multiplexing data units / data portions belonging to one or more logical channels into transport blocks (TBs) delivered to the PHY layer (e.g., PHY 211 and 221, respectively), and demultiplexing may include demultiplexing data units / data portions from the TB delivered from the PHY layer. The MAC layer of the base station (e.g., MAC 222) may be configured to perform scheduling, scheduling information reporting, and / or priority processing between radio devices via dynamic scheduling. Scheduling may be performed by the base station (e.g., base station 220 at MAC 222) for downlink and / or uplink. The MAC layer (e.g., MAC 212 and 222) may be configured to perform error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), and to perform priority processing between logical channels of radio device 210 via logical channel priority ordering and / or padding. The MAC layer (e.g., MAC 212 and 222) can support one or more parameter sets and / or transmission timings. Mapping constraints in logical channel prioritization can control the parameter sets and / or transmission timings that logical channels can use. The MAC layer (e.g., MAC 212 and 222) can provide / configure logical channel 340 as a service against the RLC layer (e.g., RLC 213 and 223).

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

[0069] Figure 4A An example downlink data flow for user plane configuration is shown. This user plane configuration may include, for example... Figure 2A The NR user plane protocol stack is shown. One or more TBs can be generated, for example, based on the data stream transmitted via the user plane protocol stack. Figure 4A As shown, the downlink data flow via the NR user plane protocol stack, consisting of three IP packets (n, n+1, and m), can generate two TBs (e.g., at base station 220). The uplink data flow via the NR user plane protocol stack can be similar to... Figure 4AThe downlink data flow is shown. Three IP packets (n, n+1, and m) can be determined from two TBs, for example, based on the uplink data flow via the NR user plane protocol stack. A first number of packets (e.g., three or any other number) can be determined from a second number of TBs (e.g., two or another number).

[0070] For example, if SDAP 225 receives three IP packets (or another number of IP packets) from one or more QoS flows and maps those three packets (or other number of packets) to radio bearers (e.g., radio bearers 402 and 404), a downlink data flow can begin. SDAP 225 can map IP packets n and n+1 to the first radio bearer 402 and IP packet m to the second radio bearer 404. The SDAP header (in...) Figure 4A Each SDAP SDU shown (preceded by "H") can be added to an IP packet to generate an SDAP PDU, which can be called a PDCP SDU. Data units transmitted from / to higher protocol layers can be called lower protocol layer Service Data Units (SDUs), and data units transmitted from / to lower protocol layers can be called higher protocol layer Protocol Data Units (PDUs). For example... Figure 4A As shown, the data unit from SDAP 225 can be an SDU (e.g., PDCP SDU) of the lower protocol layer PDCP 224, and can also be a PDU (e.g., SDAP PDU) of SDAP 225.

[0071] Each protocol layer (e.g., Figure 4A The protocol layers shown) or at least some of the protocol layers can: perform their own functions (e.g., regarding...) Figure 3 Each protocol layer described may have one or more functions, such as adding corresponding headers and / or forwarding the corresponding output to the next lower layer (e.g., its corresponding lower layer). PDCP 224 may perform IP header compression and / or encryption. PDCP 224 may forward its output (e.g., PDCP PDU, which is an RLC SDU) to RLC 223. RLC 223 may optionally perform fragmentation (e.g., as described in the previous section). Figure 4A (As shown in IP packet m). RLC 223 can forward its output (e.g., two RLCPDUs, which are two MAC SDUs generated by adding appropriate subheaders to two SDU segments) to MAC 222. MAC 222 can multiplex a certain number of RLC PDUs (MAC SDUs). MAC 222 can attach MAC subheaders to RLC PDUs (MAC SDUs) to form a TB. MAC subheaders can be distributed on MAC PDUs (e.g., in...). Figure 4A(As shown in the NR configuration). The MAC sub-header can be located entirely at the beginning of the MAC PDU (e.g., in the LTE configuration). For example, if the MAC PDU sub-header is calculated before assembling the complete MAC PDU, the NR MAC PDU structure can reduce processing time and / or associated latency.

[0072] Figure 4B An example format of the MAC subheader in a MAC PDU is shown. A MAC PDU may include a MAC subheader (H) and a MAC SDU. Each of one or more MAC subheaders may include: an SDU length field indicating the length (e.g., in bytes) of the MAC SDU corresponding to the MAC subheader; a Logical Channel Identifier (LCID) field identifying / indicating the logical channel from which the MAC SDU originates to assist in demultiplexing processing; a flag (F) indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0073] One or more MAC control elements (CEs) can be added to or inserted into a MAC PDU through a MAC layer (such as MAC 223 or MAC 222). For example... Figure 4B As shown, two MAC CEs can be inserted / added before two MAC PDUs. MAC CEs can also be inserted / added at the beginning of a MAC PDU for downlink transmission (e.g., ...). Figure 4B (As shown). One or more MAC CEs can be inserted / added to the end of the MAC PDU for uplink transmission. MAC CEs can be used for in-band control signaling. Example MAC CEs may include scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs (e.g., activation / deactivation for PDCP replication detection, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and MAC CEs for previously configured components); discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. MAC CEs may be preceded by a MAC subheader with a format similar to that described in 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.

[0074] Figure 5A An example mapping of downlink channels is shown. Uplink channel mapping can include mappings between downlink channels (e.g., logical channels, transport channels, and physical channels). Figure 5BAn example mapping of uplink channels is shown. Uplink channel mapping can include mappings between uplink channels (e.g., logical channels, transport channels, and physical channels). Information can be transmitted via / through channels between the RLC, MAC, and PHY layers of a protocol stack (e.g., the NR protocol stack). Logical channels can be used between the RLC and MAC layers. Logical channels can be classified / indicated as control channels that can carry control and / or configuration information (e.g., in the NR control plane) or traffic channels that can carry data (e.g., in the NR user plane). Logical channels can be classified / indicated as dedicated logical channels that can be used exclusively by a specific radio device, and / or common logical channels that can be used by more than one radio device (e.g., a group of radio devices).

[0075] Logical channels can be defined by the type of information they carry. This set of logical channels (e.g., in an NR configuration) may include one or more channels as described below. The Paging Control Channel (PCCH) may include / carry one or more paging messages for paging a radio device whose location is unknown to the network at the cell level. The Broadcast Control Channel (BCCH) may include / carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs). Radio devices can use system information messages to obtain information about how the cell is configured and how to operate within the cell. The Common Control Channel (CCCH) may include / carry control messages along with random access. The Dedicated Control Channel (DCCH) may include / carry control messages destined for / from a specific radio device to configure the radio device with configuration information. The Dedicated Traffic Channel (DTCH) may include / carry user data destined for / from a specific radio device.

[0076] Transport channels can be used between the MAC and PHY layers. Transport channels can be defined according to how the information they carry is sent / transmitted (e.g., via the air interface). This set of transport channels (e.g., defined by 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) can provide access to the network for a radio device without any prior scheduling.

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

[0078] The physical layer can generate physical signals to support lower-level physical layer operations, which can resemble physical control channels. For example... Figure 5A and Figure 5B As shown, physical layer signals (e.g., which may be defined by 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 signal.

[0079] One or more of these 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 An example control plane configuration (e.g., the NR control plane protocol stack) is shown. Figure 2BAs shown, a control plane configuration (e.g., an NR control plane protocol stack) can use one or more substantially the same / similar protocol layers (e.g., PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224) as an example user plane configuration (e.g., an NR user plane protocol stack). The four similar protocol layers can include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. A control plane configuration (e.g., an NR control plane stack) can have Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 on top of the control plane configuration (e.g., an NR control plane protocol stack), for example, instead of having SDAP 215 and 225. A control plane configuration can include AMF 230, which includes NAS protocol 237.

[0080] NAS protocols 217 and 237 can provide control plane functionality between wireless device 210 and AMF 230 (e.g., AMF 158A or any other AMF) and / or more generally, between wireless device 210 and CN (e.g., CN 152 or any other CN). NAS protocols 217 and 237 can provide control plane functionality between wireless device 210 and AMF 230 via signaling messages referred to as NAS messages. There may not be a direct path for NAS messages to be transmitted between wireless device 210 and AMF 230. NAS messages can be transmitted using AS interfaces of Uu and NG. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, session management, and / or any other functions.

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

[0082] Figure 6 Example RRC states and RRC state transitions are shown. The RRC state of a wireless device can change to another RRC state (e.g., an RRC state transition of the wireless device). The wireless device can be substantially the same as or similar to wireless devices 106, 210, or any other wireless device. The wireless device can be in at least one of a plurality of states, such as three RRC states, including RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRC inactive state 604 (e.g., RRC_INACTIVE). RRC inactive state 604 can mean that the RRC is connected but inactive.

[0083] An RRC connection can be established for a wireless device. For example, this might occur during an RRC connection state. During an RRC connection state (e.g., during RRC connection 602), the wireless device may have an established RRC context and may have at least one RRC connection with a base station. The base station may resemble one of these base stations (e.g., Figure 1A One or more base stations of RAN 104 shown Figure 1BOne of gNB 160 or ng-eNB 162 shown. Figure 2A and Figure 2B (Base station 220 shown or any other base station). A base station connected to a radio device (e.g., with an established RRC connection) may have the radio device's RRC context. The RRC context may be referred to as the radio device context (e.g., UE context) and may include parameters for communication between the radio device and the base station. These parameters may include one or more of the following: AS context; radio link configuration parameters; bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information). During RRC connection states (e.g., RRC connection 602), the mobility of the radio device may be managed / controlled by the RAN (e.g., RAN 104 or NG RAN 154). The radio device may measure the received signal level (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 neighboring cells. The wireless device can report these measurements to the serving base station (e.g., the base station currently serving the wireless device). The serving base station of the wireless device can, for example, request a handover to a cell of a neighboring base station based on the reported measurements. The RRC state can be transitioned from an RRC connected state (e.g., RRC connected 602) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 608. The RRC state can be transitioned from an RRC connected state (e.g., RRC connected 602) to an RRC inactive state (e.g., RRC inactive state 604) via a connection termination procedure 610.

[0084] An RRC context may not be established for the radio device. For example, this could occur during an RRC idle state. During an RRC idle state (e.g., RRC Idle 606), an RRC context may not be established for the radio device. During an RRC idle state (e.g., RRC Idle 606), the radio device may not have an RRC connection with the base station. During an RRC idle state (e.g., RRC Idle 606), the radio device may be in a sleep state most of the time (e.g., to conserve battery power). The radio device may periodically wake up (e.g., once in each Discontinuous Receive (DRX) cycle) to monitor paging messages (e.g., paging messages set from the RAN). The mobility of the radio device can be managed by the radio device via a cell reselection procedure. The RRC state can 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.

[0085] Previously established RRC contexts can be maintained for radio devices. For example, this might occur during an RRC inactivity state. During an RRC inactivity state (e.g., RRC inactivity state 604), previously established RRC contexts can be maintained in both the radio device and the base station. Compared to a transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602), maintaining the RRC context allows for / permits a rapid transition to the RRC connected state (e.g., RRC connected 602) with reduced signaling overhead. During an RRC inactivity state (e.g., RRC inactivity state 604), the radio device can be in a sleep state, and its mobility can be managed / controlled by the radio device via cell reselection. The RRC state can transition from an RRC inactivity state (e.g., RRC inactivity state 604) to an RRC connected state (e.g., RRC connected 602) via a connection recovery procedure 614. The RRC state can be transitioned from an RRC inactive state (e.g., RRC inactive state 604) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 616 that is the same as or similar to connection release procedure 608.

[0086] 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 State 604), mobility can be managed / controlled by the radio device 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 State 604) can be to enable / permit the network to notify the radio device of events via paging messages without broadcasting paging messages across the mobile network. Mobility management mechanisms used during RRC idle states (e.g., RRC Idle 606) or RRC idle states (e.g., RRC Inactive State 604) can enable / permit the network to track the radio device, for example, at the cell group level, such that paging messages can be broadcast on the cells of the cell group where the radio device currently resides (e.g., instead of sending paging messages across the mobile network). Mobility management mechanisms for RRC idle states (e.g., RRC idle 606) and RRC inactive states (e.g., RRC inactive state 604) can track radio devices at the cell group level. These mobility management mechanisms can, for example, use different packet granularities for tracking. Multiple levels of cell packet granularity can exist (e.g., three levels of cell packet granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and a group of cells within a RAN area referred to as a tracking area and identified by a Tracking Area Identifier (TAI)).

[0087] A tracking area can be used to track radio devices (e.g., to track the location of radio devices at the CN level). A CN (e.g., CN 102, 5G CN 152, or any other CN) can send a list of TAIs associated with the radio device's registration area (e.g., UE registration area) to the radio device. For example, if a radio device moves (e.g., via cell reselection) to a cell associated with a TAI that may not be included in the list of TAIs associated with the UE registration area, the radio device can perform a registration update with the CN to allow the CN to update the radio device's location and provide the radio device with the new UE registration area.

[0088] RAN areas can be used to track radio devices (e.g., the location of radio devices at the RAN level). For radio devices in an RRC inactive state (e.g., RRC inactive state 604), RAN notification areas can be assigned / provided / configured to the radio device. RAN notification areas can include one or more cell identities (e.g., RAI lists and / or TAI lists). A base station can belong to one or more RAN notification areas. A cell can belong to one or more RAN notification areas. For example, if a radio device moves (e.g., via cell reselection) to a cell not included in a RAN notification area assigned / provided / configured to the radio device, the radio device can perform a notification area update with the RAN to update its RAN notification area.

[0089] The base station that stores the RRC context of the wireless device or the last serving base station of the wireless device may be referred to as the anchor base station. The anchor base station may maintain the RRC context of the wireless device at least during the period when the wireless device is in the RAN notification area of ​​the anchor base station and / or during the period when the wireless device is in an RRC inactive state (e.g., RRC inactive state 604).

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

[0091] Physical signals and physical channels (e.g., regarding Figure 5A and Figure 5BThe data (as described) can be mapped onto one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols in an NR configuration or any other symbol). OFDM is a multicarrier communication scheme that transmits / transmits data over F orthogonal subcarriers (or carriers). The data can be mapped onto a series of complex symbols called source symbols (e.g., M-QAM symbols, M-PSK symbols, or any other modulated symbols), and is divided into F parallel symbol streams, for example, before data transmission. 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 transforms them into the time domain. The IFFT block can receive F source symbols at a time, one source symbol from each of the F parallel symbol streams. The IFFT block can use each source symbol to modulate the amplitude and phase of a function corresponding to one of the F sinusoidal basis functions of the F orthogonal subcarriers. The output of the IFFT block can be F time-domain samples representing the sum of the F orthogonal subcarriers. F time-domain samples 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, for example, after one or more processes (e.g., adding a cyclic prefix) and upsampling. For example, before processing by the IFFT block, a Fast Fourier Transform (FFT) block can be used to mix the F parallel symbol streams. This operation can produce Discrete Fourier Transform (DFT) precoded OFDM symbols, which can be used by one or more radio devices in the uplink to reduce the peak-to-average power ratio (PAPR). The FFT block can be used at the receiver to perform inverse processing on the OFDM symbols to recover the data mapped to the source symbols.

[0092] Figure 7 An example configuration of a frame is shown. The frame may include, for example, an NR radio frame, into which OFDM symbols can be grouped. The frame (e.g., an NR radio frame) can be identified / indicated by the System Frame Number (SFN) or any other value. The SFN can repeat in a period of 1024 frames. The duration of an NR frame can be 10 milliseconds (ms) and can include 10 subframes with a duration of 1 ms. Subframes can be divided into one or more time slots (e.g., depending on the parameter set and / or different subcarrier spacing). Each of these one or more time slots can include, for example, 14 OFDM symbols per slot. Any number of symbols, time slots, or duration can be used for any time interval.

[0093] The duration of a time slot can depend on the parameter set of the OFDM symbols used for that time slot. Flexible parameter sets can be supported, for example, to accommodate different deployments (e.g., cells with carrier frequencies below 1 GHz to cells with carrier frequencies in the millimeter wave range). For example, flexible parameter sets can be supported in NR configurations or any other radio configurations. Parameter sets can be defined based on subcarrier spacing and / or cyclic prefix duration. Subcarrier spacing can be increased proportionally from a baseline subcarrier spacing of 15 kHz by a power of two. For example, for a parameter set in an NR configuration or any other radio configuration, the cyclic prefix duration can be decreased proportionally from a baseline cyclic prefix duration of 4.7 μs by a power of two. Parameter sets can be defined using the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; 240 kHz / 0.29 μs, and / or any other subcarrier spacing / cyclic prefix duration combination.

[0094] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A parameter set with higher subcarrier spacing can have shorter time slot durations and more time slots per subframe. Figure 7 The example shown illustrates the slot duration and per-subframe slot transmission structure associated with the parameter set. Figure 7 (A parameter set with a 240 kHz subcarrier spacing is not shown in the diagram). Subframes (e.g., in an NR configuration) can be used as parameter set-independent time references. Time slots can be used as units for scheduling uplink and downlink transmissions. Scheduling (e.g., in an NR configuration) can be decoupled from the time slot duration. Scheduling can begin at any OFDM symbol. Scheduling can last as many symbols as required for transmission, for example, to support low latency. These partial time slot transmissions can be referred to as micro-time slot or sub-time slot transmissions.

[0095] Figure 8 An example resource configuration for one or more carriers is shown. A resource configuration can include time slots in both the time and frequency domains for an NR carrier or any other carrier. These time slots can include resource elements (REs) and resource blocks (RBs). A resource element (RE) can be a minimum physical resource (e.g., in an NR configuration). An RE can span an OFDM symbol in the time domain via a subcarrier in the frequency domain, such as... Figure 8 As shown. RB can span twelve consecutive REs in the frequency domain, such as... Figure 8As shown. A carrier (e.g., an NR carrier) can be limited to a certain number of RBs and / or the width of subcarriers (e.g., 275 RBs or 275 × 12 = 3300 subcarriers). If this limitation is used, the carrier (e.g., an NR carrier) frequency can be limited based on the subcarrier spacing (e.g., for subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, the carrier frequencies are 50 MHz, 100 MHz, 200 MHz, and 400 MHz, respectively). A 400 MHz bandwidth can be set based on a 400 MHz bandwidth limit per carrier. Any other bandwidth can be set based on a per-carrier bandwidth limit.

[0096] It can be across the entire bandwidth of the carrier (e.g., as...) Figure 8 A single parameter set is used on the NR shown. In other example configurations, multiple parameter sets can be supported on the same carrier. NR and / or other access technologies can support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all wireless devices are able to receive the full carrier bandwidth (e.g., due to hardware limitations and / or different wireless device capabilities). For example, receiving and / or utilizing the full carrier bandwidth may be prohibited depending on the power consumption of the wireless device. The wireless device can adjust the size of its receive bandwidth, for example, based on the amount of traffic that the wireless device is scheduled to receive (e.g., to reduce power consumption and / or for other purposes). This adaptation can be referred to as bandwidth adaptation.

[0097] The configuration of one or more Bandwidth Parts (BWPs) can support one or more radio devices that cannot receive the full carrier bandwidth. BWPs can support bandwidth adaptation, for example, for such radio devices that cannot receive the full carrier bandwidth. A BWP (e.g., an NR-configured BWP) can be defined by a subset of consecutive RBs on a carrier. A radio device can be configured (e.g., via an RRC layer) to have one or more downlink BWPs per serving cell and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs per serving cell and up to four uplink BWPs per serving cell). One or more of the configured BWPs of the serving cell can be active, for example, at a given time. These one or more BWPs can be referred to as the active BWPs of the serving cell. For example, if the serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0098] A downlink BWP from a set of configured downlink BWPs can be linked to an uplink BWP from a set of configured uplink BWPs (e.g., for unpaired spectrum). For example, a downlink BWP can be linked to an uplink BWP if the downlink BWP index and the uplink BWP index are the same. The wireless device can expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP (e.g., for unpaired spectrum).

[0099] A base station can configure one or more control resource sets (CORESETs) for a radio device for at least one search space. The base station can configure one or more CORESETs for a radio device, such as a set of downlink BWPs configured in the downlink BWPs on the primary cell (PCell) or secondary cell (SCell). The search space can include a set of locations in the time and frequency domains where the radio device can monitor / find / detect / identify control information. The search space can be a radio device-specific search space (e.g., a UE-specific search space) or a common search space (e.g., possibly used by multiple radio devices or a group of radio user equipments). The base station can configure a common search space for a group of radio devices in the active downlink BWPs on the PCell or primary / secondary cell (PSCell).

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

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

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

[0103] The base station can configure a BWP inactivity timer value for the PCell for the wireless device. The wireless device can start or restart the BWP inactivity timer at any appropriate time. For example, the wireless device can start or restart the BWP inactivity timer if one or more conditions are met. These conditions may include at least one of the following: the wireless device detects a DCI indicating an active downlink BWP other than the default downlink BWP used for paired spectrum operation; the wireless device detects a DCI indicating an active downlink BWP other than the default downlink BWP used for unpaired spectrum operation; and / or the wireless device detects a DCI indicating an active uplink BWP other than the default uplink BWP used for unpaired spectrum operation. For example, if the wireless device does not detect a DCI during a time interval (e.g., 1 ms or 0.5 ms), the wireless device can start / run the BWP inactivity timer when it is close to expiration (e.g., increasing from zero to the BWP inactivity timer value, or decreasing from the BWP inactivity timer value to zero). For example, if the BWP inactivity timer expires, the wireless device can switch from the active downlink BWP to the default downlink BWP.

[0104] The base station can semi-statically configure one or more BWPs for the radio device. The radio device can, for example, switch the active BWP from the first BWP to the second BWP based on receiving a DCI indicating that the second BWP is the active BWP (e.g., after or in response to this). The radio device (e.g., if the second BWP is the default BWP) can, for example, switch the active BWP from the first BWP to the second BWP based on the expiration of a BWP inactivity timer (e.g., after or in response to this).

[0105] Downlink BWP handover can refer to switching the active downlink BWP from a first downlink BWP to a second downlink BWP (e.g., activating the second downlink BWP and deactivating the first downlink BWP). Uplink BWP handover can refer to switching the active uplink BWP from a first uplink BWP to a second uplink BWP (e.g., activating the second uplink BWP and deactivating the first uplink BWP). Downlink and uplink BWP handovers can be performed independently (e.g., in one or more paired spectrums). Downlink and uplink BWP handovers can also be performed simultaneously (e.g., in one or more unpaired spectrums). Handover between configured BWPs can occur, for example, based on RRC signaling, DCI signaling, the expiration of a BWP inactivity timer, and / or the initiation of random access.

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

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

[0108] Two or more carriers can be aggregated, and carrier aggregation (CA) can be used to simultaneously send / transmit data to / from the same wireless device (e.g., to increase the data rate). The aggregated carriers in CA can be referred to as component carriers (CCs). For example, if CA is configured / used, there may be a certain number of serving cells for the wireless device (e.g., one serving cell for the CC). The CCs can have multiple configurations in the frequency domain.

[0109] Figure 10A A sample CA configuration based on CC is shown. For example... Figure 10A As shown, the three types of CA configurations can include an in-band (contiguous) configuration 1002, an in-band (non-contiguous) configuration 1004, and / or an inter-band configuration 1006. In an in-band (contiguous) configuration 1002, two CCs can be aggregated in the same frequency band (band A) and can be directly adjacent to each other within the band. In an in-band (non-contiguous) configuration 1004, two CCs can be aggregated in the same frequency band (band A), but can be spaced apart from each other within the band. In an inter-band configuration 1006, two CCs can be located in different frequency bands (e.g., band A and band B, respectively).

[0110] The network can configure the 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 can have the same or different bandwidths, subcarrier spacings, and / or duplex schemes (TDD, FDD, or any other duplex scheme). The serving cell for a radio device using CA can have downlink CCs. One or more uplink CCs can optionally be configured for the serving cell (e.g., for FDD). For example, if the radio device has more data traffic in the downlink than in the uplink, the ability to aggregate more downlink carriers than uplink carriers can be useful.

[0111] For example, if CA is configured, one of the aggregated cells used by the radio device can be referred to as the primary cell (PCell). The PCell can be the serving cell for initial radio connection or access, for example, during or at the time of RRC connection establishment, RRC connection re-establishment, and / or handover. The PCell can provide / configure NAS mobility information and security input to the radio device. The radio device can have different PCells. For downlink, the carrier corresponding to the PCell can be referred to as the downlink primary CC (DL PCC). For uplink, the carrier corresponding to the PCell can be referred to as the uplink primary CC (UL PCC). Other aggregated cells used by the radio device (e.g., associated with CCs other than the DL PCC and UL PCC) can be referred to as secondary cells (SCells). For example, an SCell can be configured after a PCell is configured for the radio device. An SCell can be configured via an RRC connection reconfiguration procedure. For downlink, the carrier corresponding to the SCell can be referred to as the downlink secondary CC (DLSCC). For uplink, the carrier corresponding to the SCell can be referred to as the uplink secondary CC (UL SCC).

[0112] For example, SCells configured for wireless devices can be activated or deactivated based on service and channel conditions. Deactivation of a SCell can cause the wireless device to stop receiving PDCCH and PDSCH on the SCell, as well as transmitting PUSCH, SRS, and CQI on the SCell. For example, this can be achieved using MAC CE (e.g., regarding...). Figure 4B The MAC CE described herein activates or deactivates a configured SCell. The MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., a subset of configured SCells) are activated or deactivated for the wireless device. For example, a configured SCell may be deactivated based on the expiration (e.g., after or in response to) of a SCell deactivation timer (e.g., configurable one SCell deactivation timer per SCell).

[0113] DCI (Distributed Control Information) can include control information for the cell, such as scheduling assignment and scheduling permission. DCI can be transmitted / transmitted via the cell corresponding to the scheduling assignment and / or scheduling permission; this can be referred to as self-scheduling. DCI including control information for the cell can be transmitted / transmitted via another cell; this can be referred to as cross-carrier scheduling. Uplink Control Information (UCI) can include control information such as HARQ acknowledgments and channel state feedback (e.g., CQI, PMI, and / or RI) for the aggregated cell. UCI can be transmitted / transmitted via the uplink control channel (e.g., PUCCH) of the PCell or a SCell (e.g., a SCell configured with PUCCH). For a large number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells can be divided into multiple PUCCH groups.

[0114] Figure 10B An example cell group is shown. Aggregated cells can be configured as one or more PUCCH groups (e.g., such as...). Figure 10B(As shown). One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may each include one or more downlink CCs. PUCCH group 1010 may include one or more downlink CCs, for example, three downlink CCs: PCell 1011 (e.g., DL PCC), SCell 1012 (e.g., DL SCC), and SCell 1013 (e.g., DL SCC). PUCCH group 1050 may include one or more downlink CCs, for example, three downlink CCs: 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 PCell 1021 (e.g., UL PCC), SCell 1022 (e.g., UL SCC), and SCell 1023 (e.g., ULSCC). One or more uplink CCs of PUCCH group 1050 can be configured as PUCCH SCell (or PSCell) 1061 (e.g., UL SCC), SCell 1062 (e.g., UL SCC), and SCell 1063 (e.g., UL SCC). UCIs associated with the downlink CCs of PUCCH group 1010 can be transmitted / transmitted via the uplink of PCell 1021 (e.g., via the PUCCH of PCell 1021), shown as UCI 1031, UCI 1032, and UCI 1033. UCIs associated with the downlink CCs of PUCCH group 1050 can be transmitted / transmitted via the uplink of PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of PUCCH SCell 1061), shown as UCI 1071, UCI 1072, and UCI 1073. For example, if Figure 10B If the aggregated cell shown is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell can be configured to send / transmit UCIs associated with six downlink CCs. For example, if UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are sent / transmitted via PCell 1021, PCell 1021 may become overloaded. By partitioning the transmission of UCIs between PCell 1021 and PUCCHSCell (or PSCell) 1061, overload can be prevented and / or reduced.

[0115] A PCell may include a downlink carrier (e.g., PCell 1011) and an uplink carrier (e.g., PCell 1021). An SCell may include only a downlink carrier. A physical cell ID and a cell index may be assigned to a cell that includes a downlink carrier and an optional uplink carrier. The physical cell ID or cell index may indicate / identify the downlink carrier and / or uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. For example, the physical cell ID may be determined using synchronization signals (e.g., PSS and / or SSS) transmitted / transmitted via downlink component carriers. The cell index may be determined, for example, using one or more RRC messages. The physical cell ID may be referred to as a carrier ID, and the cell index may be referred to as a carrier index. The first physical cell ID for the first downlink carrier may refer to the first physical cell ID of the cell that includes the first downlink carrier. Essentially the same / similar concepts may be applied, for example, carrier activation. The activation of the first carrier may refer to the activation of the cell that includes the first carrier.

[0116] The multicarrier nature of the PHY layer can be exposed / indicated to the MAC layer (e.g., in a CA configuration). HARQ entities can operate on the serving cell. Transport blocks can be generated based on assignment / granting per serving cell. Transport blocks and their potential HARQ retransmissions can be mapped to serving cells.

[0117] For the downlink, the base station may send / 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 the uplink, the one or more radio devices may send / transmit one or more RS (e.g., DM-RS, PT-RS, and / or SRS) to the base station. PSS and SSS may be sent / transmitted by the base station and used by the one or more radio devices to synchronize the one or more radio devices with the base station. Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) blocks may include PSS, SSS, and PBCH. The base station may periodically send / transmit bursts of SS / PBCH blocks, which may be referred to as SSBs.

[0118] Figure 11A An example mapping of one or more SS / PBCH blocks is shown. A burst of SS / PBCH blocks can include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as...). Figure 11A(As shown in the diagram). Bursts can be sent / transmitted periodically (e.g., every 2 frames, 20 ms, or any other duration). Bursts can be limited to half-frames (e.g., a first half-frame lasting 5 ms). Such parameters (e.g., the number of SS / PBCH blocks per burst, the periodicity of the burst, the burst position within a frame) can be configured, for example, based on at least one of the following: the carrier frequency of the cell in which the SS / PBCH blocks are sent / transmitted; the parameter set or subcarrier spacing of the cell; the configuration performed by the network (e.g., using RRC signaling); and / or any other suitable factor. For example, unless the wireless network configures the wireless device to assume different subcarrier spacings, the wireless device can assume the subcarrier spacing of the SS / PBCH blocks based on the monitored carrier frequency.

[0119] SS / PBCH blocks can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as...). Figure 11A The PSS, SSS, and PBCH can have a common center frequency. The PSS can be transmitted first and can span, for example, one OFDM symbol and 127 subcarriers. The SSS can be transmitted after the PSS (e.g., two symbols later) and can span one OFDM symbol and 127 subcarriers. The PBCH can be transmitted after the PSS (e.g., across the next three OFDM symbols) and can span 240 subcarriers (e.g., in the frequency domain). Figure 11A (as shown in the second and fourth OFDM symbols) and / or may span fewer than 240 subcarriers (e.g., in such cases) Figure 11A (In the third OFDM symbol shown).

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

[0121] A radio device can use SS / PBCH blocks to determine one or more parameters of a cell. The radio device can determine the cell's Physical Cell Identifier (PCI) based, for example, on the sequences of PSS and SSS. The radio device can determine the location of the cell's frame boundary based, for example, on the location of the SS / PBCH block. The SS / PBCH block can indicate that it has been transmitted / transmitted according to a transmission mode. The SS / PBCH block in the transmission mode can be at a known distance from the frame boundary (e.g., a predefined distance in the RAN configuration between one or more networks, one or more base stations, and one or more radio devices).

[0122] The PBCH can use QPSK modulation and / or forward error correction (FEC). FEC can use polarity coding. One or more symbols spanned by the PBCH may include / carry one or more DM-RS for PBCH demodulation. The PBCH may include an indication of the cell's current system frame number (SFN) and / or SS / PBCH block timing index. These parameters can facilitate time synchronization between the radio device and the base station. The PBCH may include a MIB for sending / transmitting one or more parameters to the radio device. The radio device can use this MIB to locate the Residual Minimum System Information (RMSI) associated with the cell. The RMSI may include System Information Block Type 1 (SIB1). SIB1 may include information for the radio device to access the cell. The radio device can use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 can be decoded using parameters provided / included in the MIB. The PBCH may indicate the absence of SIB1. The radio device may be directed to a frequency, for example, based on the PBCH indicating the absence of SIB1. The wireless device can search for SS / PBCH blocks at the frequency to which the wireless device is directed.

[0123] A wireless device may assume quasi-co-located (QCLed) one or more SS / PBCH blocks transmitted / transmitted using the same SS / PBCH block index (e.g., having substantially the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). A wireless device may not assume QCL for transmissions of SS / PBCH blocks with different SS / PBCH block indices. SS / PBCH blocks (e.g., those within a half-frame) may be transmitted / transmitted in spatial directions (e.g., using different beams spanning a coverage area of ​​the cell). A first SS / PBCH block may be transmitted / transmitted in a first spatial direction using a first beam, a second SS / PBCH block in a second spatial direction using a second beam, a third SS / PBCH block in a third spatial direction using a third beam, a fourth SS / PBCH block in a fourth spatial direction using a fourth beam, and so on.

[0124] A base station can, for example, transmit / transmit multiple SS / PBCH blocks within the frequency span of a carrier. The first PCI of the first SS / PBCH block among these multiple SS / PBCH blocks may differ from the second PCI of the second SS / PBCH block among these multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted / transmitted at different frequency locations may be different or substantially the same.

[0125] CSI-RS can be sent / transmitted by the base station and used by the wireless device to collect / acquire / determine Channel State Information (CSI). The base station can configure one or more CSI-RS for the wireless device for channel estimation or any other suitable purpose. The base station can configure one or more of the same / similar CSI-RS for the wireless device. The wireless device can measure the one or more CSI-RS. The wireless device can, for example, estimate the downlink channel state and / or generate a CSI report based on the measurements of the one or more downlink CSI-RS. The wireless device can send / transmit CSI reports to the base station (e.g., based on periodic CSI reports, semi-persistent CSI reports, and / or aperiodic CSI reports). The base station can use feedback provided by the wireless device (e.g., estimated downlink channel state) to perform link adaptation.

[0126] A base station can semi-statically configure one or more CSI-RS resource sets for a wireless device. CSI-RS resources can be associated with location and periodicity in the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can instruct the wireless device that CSI-RS resources in the CSI-RS resource set be activated and / or deactivated.

[0127] The base station can configure the wireless device to report CSI measurement results. The base station can configure the wireless device to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the wireless device can be configured with multiple CSI reports at set times and / or periodically. For aperiodic CSI reporting, the base station can request CSI reports. The base station can command the wireless device to measure configured CSI-RS resources and provide CSI reports related to the measurement results. For semi-persistent CSI reporting, the base station can configure the wireless device to periodically send / transmit and selectively activate or deactivate periodic reports (e.g., via one or more activation / deactivation MAC CEs and / or one or more DCIs). The base station can, for example, use RRC signaling to configure the CSI-RS resource set and CSI reports for the wireless device.

[0128] CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports (or any other number of antenna ports). For example, if the downlink CSI-RS and CORESET are spatially QCL, and the resource element associated with the downlink CSI-RS is outside the Physical Resource Block (PRB) configured for the CORESET, the radio device can be configured to use / adopt the same OFDM symbols for both the downlink CSI-RS and CORESET. Similarly, if the downlink CSI-RS and SS / PBCH blocks are spatially QCL, and the resource element associated with the downlink CSI-RS is outside the PRB configured for the SS / PBCH blocks, the radio device can be configured to use / adopt the same OFDM symbols for both the downlink CSI-RS and SS / PBCH blocks.

[0129] Downlink DM-RS can be transmitted / transmitted by the base station and received / used by the radio device for channel estimation. Downlink DM-RS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). The network (e.g., NR network) can support one or more variable and / or configurable DM-RS modes for data demodulation. At least one downlink DM-RS configuration can support a preloaded DM-RS mode. Preloaded DM-RS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure a certain number (e.g., maximum number) of preloaded DM-RS symbols for the radio device to use for PDSCH. A DM-RS configuration can support one or more DM-RS ports. A DM-RS configuration can support up to eight orthogonal downlink DM-RS ports per radio device (e.g., for single-user MIMO). A DM-RS configuration can support up to four orthogonal downlink DM-RS ports per radio device (e.g., for multi-user MIMO). The radio network can support (e.g., at least for CP-OFDM) a common DM-RS structure for both downlink and uplink. The DM-RS location, DM-RS mode, and / or scrambling sequence can be the same or different. The base station can, for example, use the same precoding matrix to transmit / transmit the downlink DM-RS and the corresponding PDSCH. The radio device can use this one or more downlink DM-RS for coherent demodulation / channel estimation of the PDSCH.

[0130] A transmitter (e.g., a transmitter at a base station) 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. For example, the first and second precoder matrices may differ based on the difference between the first and second bandwidths. The wireless device may assume that the same precoder matrix is ​​used across a set of PRBs. This set of PRBs can be identified / indicated / identified / represented as a Precoded Resource Block Group (PRG).

[0131] A PDSCH may include one or more layers. A radio device may assume that at least one symbol with a DM-RS exists on one of these layers of the PDSCH. Higher layers may configure one or more DM-RS for the PDSCH (e.g., up to three DM-RSs for the PDSCH). Downlink PT-RS may be transmitted / transmitted by the base station and used by the radio device, for example, for phase noise compensation. The presence of downlink PT-RS may depend on RRC configuration. The presence and / or type of downlink PT-RS may be configured, for example, using a combination of RRC signaling and / or associated with one or more parameters that may be indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). If configured, the dynamic presence of downlink PT-RS may be associated with one or more DCI parameters including at least one MCS. The network (e.g., an NR network) may support multiple PT-RS densities defined in the time and / or frequency domains. Frequency domain density (if configured / existing) may be associated with at least one configuration of the scheduling bandwidth. The wireless device can assume the same precoding for both DM-RS and PT-RS ports. The number of PT-RS ports can be less than the number of DM-RS ports in the scheduling resources. Downlink PT-RS can be configured / assigned / limited within the scheduling time / frequency duration of the wireless device. Downlink PT-RS can be transmitted / transmitted via symbols, for example, to facilitate phase tracking at the receiver.

[0132] A radio device can transmit / transmit uplink DM-RS to a base station, for example, for channel estimation. The base station can use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. The radio device can utilize PUSCH and / or PUCCH to transmit / transmit uplink DM-RS. The uplink DM-RS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure one or more uplink DM-RS configurations for the radio device. At least one DM-RS configuration can support preloaded DM-RS mode. Preloaded DM-RS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS can be configured to be transmitted / transmitted at one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure a certain number (e.g., a maximum number) of preloaded DM-RS symbols for PUSCH and / or PUCCH, which the radio device can use to schedule single-symbol DM-RS and / or dual-symbol DM-RS. The network (e.g., an NR network) can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DM-RS structure for both downlink and uplink. The DM-RS location, DM-RS mode, and / or scrambling sequence of the DM-RS can be substantially the same or different.

[0133] The PUSCH may include one or more layers. A radio device may transmit / transmit at least one symbol where a DM-RS exists on one of these layers of the PUSCH. Higher layers may configure one or more DM-RSs (e.g., up to three DM-RSs) for the PUSCH. For example, depending on the radio device's RRC configuration, an uplink PT-RS (which may be used by the base station for phase tracking and / or phase noise compensation) may or may not exist. The presence and / or mode of the uplink PT-RS may be configured on a radio device-specific basis (e.g., a UE-specific basis), such as through RRC signaling and / or a combination of one or more parameters configured / used for other purposes (e.g., MCS), which may be indicated by the DCI. If configured, the dynamic presence of the uplink PT-RS may be associated with one or more DCI parameters including at least one MCS. The radio network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density (if configured / existing) may be associated with at least one configuration of the scheduling bandwidth. The radio device may assume the same precoding for both the DM-RS port and the PT-RS port. The number of PT-RS ports can be less than the number of DM-RS ports in the scheduling resources. Uplink PT-RS can be configured / assigned / limited to the scheduling time / frequency duration of the wireless device.

[0134] One or more SRSs can be transmitted / transmitted by a radio device to a base station, for example, for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted / transmitted by the radio device enables / allows the base station to estimate uplink channel states at one or more frequencies. The scheduler at the base station can use / adopt the estimated uplink channel states to assign one or more resource blocks for uplink PUSCH transmissions by the radio device. The base station can semi-statically configure one or more SRS resource sets for the radio device. For each SRS resource set, the base station can configure one or more SRS resources for the radio device. The suitability of the SRS resource set can be configured, for example, by higher-layer (e.g., RRC) parameters. For example, if higher-layer parameters indicate beam management, SRS resources in the one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodicity, aperiodicity, etc.) can be transmitted / transmitted at some time (e.g., simultaneously). The radio device can transmit / transmit one or more SRS resources in the SRS resource set. The network (e.g., an NR network) can support aperiodic, periodic, and / or semi-persistent SRS transmissions. A wireless device may transmit / transmit SRS resources, for example, based on one or more trigger types. These one or more trigger types may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. The wireless device may use / emulate at least one DCI format to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. If PUSCH and SRS are transmitted / transmitted in the same time slot, the wireless device may be configured to transmit / transmit SRS, for example, after the transmission of PUSCH and the corresponding uplink DM-RS. The base station may semi-statically configure one or more SRS configuration parameters for the radio device that indicate at least one of the following: SRS resource configuration identifier; number of SRS ports; temporal behavior of SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS); time slot, micro-time slot, and / or subframe-level periodicity; offset of periodic and / or aperiodic SRS resources; number of OFDM symbols in the SRS resources; start OFDM symbol of the SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0135] Antenna ports can be determined / defined such that the channel transmitting another symbol on the same antenna port can be inferred from the channel transmitting a symbol on that antenna port. For example, if a first symbol and a second symbol are transmitted / transmitted on the same antenna port, the receiver can infer / determine the channel (e.g., attenuation gain, multipath delay, etc.) used to transmit the second symbol on the antenna interface from the channel used to transmit the first symbol on the antenna port. For example, if one or more large-scale characteristics of the channel transmitting the first symbol on the first antenna port can be inferred from the channel transmitting the second symbol on the second antenna port, then the first and second antenna ports can be referred to as quasi-co-located (QCLed). These one or more large-scale characteristics can include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0136] Channels using beamforming may require beam management. Beam management can include beam measurement, beam selection, and / or beam indication. A beam can be associated with one or more reference signals. A beam can be identified by one or more beamforming reference signals. A wireless device can perform downlink beam measurements, for example, based on one or more downlink reference signals (e.g., CSI-RS), and generate a beam measurement report. For example, after establishing an RRC connection with a base station, the wireless device can perform a downlink beam measurement procedure.

[0137] Figure 11B Example mappings of one or more CSI-RS are shown. CSI-RS can be mapped in both the time and frequency domains. Figure 11BEach rectangular block shown may correspond to a resource block (RB) within the cell's bandwidth. The base station may send / transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more parameters in the parameters may be configured via higher-layer signaling (e.g., RRC and / or MAC signaling) used for CSI-RS resource configuration. The parameters may include at least one of the following: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-LS configuration (e.g., symbol and resource element (RE) positions in a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in a radio frame), CSI-RS power parameters, CSI-SS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi-co-address (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0138] One or more beams can be configured for a wireless device in a device-specific configuration. Figure 11B Three beams (beam #1, beam #2, and beam #3) are shown, but more or fewer beams can be configured. CSI-RS 1101 can be assigned to beam #1, which can be transmitted / transmitted on one or more subcarriers in the RB of the first symbol. CSI-RS 1102 can be assigned to beam #2, which can be transmitted / transmitted on one or more subcarriers in the RB of the second symbol. CSI-RS 1103 can be assigned to beam #3, which can be transmitted / transmitted on one or more subcarriers in the RB of the third symbol. The base station can use other subcarriers in the same RB (e.g., those not used to transmit / transmit CSI-RS 1101) to transmit another CSI-RS associated with the beam used for another wireless device, for example, by using frequency division multiplexing (FDM). The beam used for the wireless device can be configured such that the beam used for the wireless device uses symbols different from those used by the beams of other wireless devices, for example, by using time domain multiplexing (TDM). For example, by using TDM, beams in orthogonal symbols (e.g., without overlapping symbols) can be used to serve wireless devices.

[0139] CSI-RS (e.g., CSI-RS 1101, 1102, 1103) can be sent / transmitted by a base station and used by a wireless device for one or more measurements. The wireless device can measure the RSRP of the configured CSI-RS resources. The base station can configure a reporting configuration for the wireless device, and the wireless device can report the RSRP measurement results to the network (e.g., via one or more base stations) based on this reporting configuration. The base station can determine one or more Transmission Configuration Indicator (TCI) states, including a certain number of reference signals, based on the reported measurement results. The base station can indicate one or more TCI states to the wireless device (e.g., via RRC signaling, MAC CE, and / or DCI). The wireless device can receive downlink transmissions using the Rx beam determined based on the one or more TCI states. The wireless device may or may not have beam-matching capability. If the wireless device has beam-matching capability, it can determine the spatial domain filter of the transmission (Tx) beam, for example, based on the spatial domain filter corresponding to the Rx beam. For example, if the wireless device lacks beamforming capability, it can perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The wireless device can perform the uplink beam selection procedure, for example, based on one or more Sounding Reference Signal (SRS) resources configured for it by the base station. The base station can, for example, select and indicate the uplink beam for the wireless device based on measurements of these one or more SRS resources transmitted / transmitted by the wireless device.

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

[0141] Figure 12AAn example of a downlink beam management procedure is shown. One or more downlink beam management procedures (e.g., downlink beam management procedures P1, P2, and P3) can be executed. Procedure P1 can enable the measurement of the Tx beam of a TRP (or multiple TRPs) (e.g., wireless device measurement) (e.g., to support the selection of one or more base station Tx beams and / or wireless device Rx beams). The Tx beam of the base station (e.g., base station 1210) and the Rx beam of the wireless device (e.g., wireless device 1205) are shown as ellipses in the top and bottom rows of P1, respectively. Beamforming (e.g., at the TRP) can include a Tx beam scan for a set of beams (e.g., an elliptical beam scan shown in the top rows of P1 and P2 as an elliptical beam scan rotating counterclockwise as indicated by a dashed arrow). Beamforming (e.g., at the wireless device) may include an Rx beam scan of a set of beams (e.g., an elliptical beam scan rotating clockwise as indicated by dashed arrows in the bottom rows of P1 and P3). Procedure P2 may be used to enable the measurement of the Tx beam of the TRP (e.g., wireless device measurement) (shown as an elliptical beam rotating counterclockwise as indicated by dashed arrows in the top row of P2). The wireless device and / or base station may perform procedure P2, for example, by using a smaller set of beams than that set of beams used in procedure P1, or by using beams narrower than those used in procedure P1. Procedure P2 may be referred to as beam thinning. The wireless device may perform procedure P3 for Rx beam determination, for example, by using the same Tx beam of the base station and scanning the Rx beam of the wireless device.

[0142] Figure 12BAn example of an uplink beam management procedure is shown. One or more uplink beam management procedures (e.g., uplink beam management procedures U1, U2, and U3) can be executed. Procedure U1 can be used to enable a base station (e.g., base station 1210) to perform measurements on the Tx beam of a wireless device (e.g., wireless device 1205) (e.g., to support the selection of one or more Tx beams of the wireless device and / or the Rx beam of the base station). The Tx beam of the wireless device and the Rx beam of the base station are shown as ellipses in the top and bottom rows of U1, respectively. Beamforming (e.g., at the wireless device) can include one or more beam scans, such as a Tx beam scan from a set of beams (shown as an ellipse rotated clockwise in the bottom rows of U1 and U3, indicated by a dashed arrow). Beamforming (e.g., at a base station) may include one or more beam scans, such as an Rx beam scan from a set of beams (shown in the top row of U1 and U2 as an ellipse rotating counterclockwise as indicated by the dashed arrow). For example, if the radio device (e.g., UE) uses a fixed Tx beam, procedure U2 may be used to enable the base station to adjust its Rx beam. The radio device and / or base station may execute procedure U2, for example, using a smaller set of beams than that set of beams used in procedure P1, or using a narrower beam than the beams used in procedure P1. Procedure U2 may be referred to as beam thinning. For example, if the base station uses a fixed Rx beam, the radio device may execute procedure U3 to adjust its Tx beam.

[0143] A wireless device can, for example, initiate / start / execute a beam fault recovery (BFR) procedure based on the detection of a beam fault. The wireless device can, for example, send / transmit a BFR request (e.g., preamble, UCI, SR, MACCE, etc.) based on initiating a BFR procedure. The wireless device can, for example, detect a beam fault based on determining that the quality of the beam pair link associated with the control channel is unsatisfactory (e.g., a bit error rate higher than a bit error rate threshold, received signal power lower than a received signal power threshold, timer expiration, etc.).

[0144] A wireless device may, for example, use one or more reference signals (RS) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more DM-RSs to measure the quality of a beamp-link. The quality of the beamp-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 value measured on the RS resources. A base station may indicate the QCL of the RS resources and one or more DM-RSs for a channel (e.g., a control channel, a shared data channel, etc.). For example, if the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, etc.) from transmission to the wireless device via the RS resources are similar to or the same as the channel characteristics from transmission to the wireless device via that channel, then the RS resources and the one or more DM-RSs for that channel may be QCLs.

[0145] Networks (e.g., NR networks including gNBs and / or ng-eNBs) and / or radio devices can initiate / start / execute random access procedures. Radio devices in an RRC idle (e.g., RRC_IDLE) and / or RRC inactive (e.g., RRC_INACTIVE) state can initiate / execute random access procedures to request connection settings to the network. Radio devices can initiate / start / execute random access procedures from an RRC connected (e.g., RRC_CONNECTED) state. Radio devices can initiate / start / execute random access procedures to request uplink resources (e.g., for uplink transmission of SR if PUCCH resources are not available) and / or acquire / obtain / determine uplink timing (e.g., if the uplink synchronization state is asynchronous). Radio devices can initiate / start / execute random access procedures to request one or more System Information Blocks (SIBs) (e.g., other System Information Blocks such as SIB2, SIB3, etc.). Radio devices can initiate / start / execute random access procedures in response to beam fault recovery requests. The network can initiate / start / execute random access procedures, for example, for handover and / or for adding setup time alignment for SCells.

[0146] Figure 13AAn example four-step random access procedure is shown. A four-step random access procedure may include four contention-based random access procedures. A base station (e.g., base station 1302) may, for example, send / transmit configuration message 1310 to a radio device (e.g., radio device 1301) before initiating a random access procedure. The four-step random access procedure may include the transmission of four messages, including: a first message (e.g., Msg 1 1311), a second message (e.g., Msg 2 1312), a third message (e.g., Msg 3 1313), and a fourth message (e.g., Msg 4 1314). The first message (e.g., Msg 1 1311) may include a preamble (or random access preamble). The first message (e.g., Msg 1 1311) may be referred to as a preamble. The second message (e.g., Msg 2 1312) may include a random access response (RAR). The second message (e.g., Msg 2 1312) may be referred to as a RAR.

[0147] Configuration message 1310 may be sent / transmitted, for example, using one or more RRC messages. These one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the radio device. These one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may send / transmit (e.g., broadcast or multicast) these one or more RRC messages to one or more radio devices. These one or more RRC messages may be radio device-specific. Radio device-specific RRC messages may be, for example, dedicated RRC messages sent / transmitted to radio devices in an RRC connected (e.g., RRC_CONNECTED) state and / or in an RRC inactive (e.g., RRC_INACTIVE) state. The wireless device can determine the time and frequency resources and / or the uplink transmission power for transmitting the first message (e.g., Msg 11311) and / or the third message (e.g., Msg 3 1313) based on the one or more RACH parameters. The wireless device can, for example, determine the receive timing and downlink channel for receiving the second message (e.g., Msg 2 1312) and the fourth message (e.g., Msg 4 1314) based on the one or more RACH parameters.

[0148] The one or more RACH parameters provided / configured / included in configuration message 1310 may indicate one or more physical RACH (PRACH) timings available for transmitting the first message (e.g., Msg 1 1311). These one or more PRACH timings may be predefined (e.g., via a network including one or more base stations). These one or more RACH parameters may indicate one or more available sets of one or more PRACH timings (e.g., prach-ConfigIndex). These one or more RACH parameters may indicate a relationship between (a) one or more PRACH timings and (b) one or more reference signals. These one or more RACH parameters may indicate a relationship between (a) one or more preambles and (b) one or more reference signals. These one or more reference signals may be SS / PBCH blocks and / or CSI-RS. These one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH timings and / or the number of preambles mapped to SS / PBCH blocks.

[0149] The one or more RACH parameters provided / configured / included in configuration message 1310 can be used to determine the uplink transmission power of the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313). The one or more RACH parameters can indicate a reference power (e.g., the receive target power and / or initial power for preamble transmission) for the preamble transmission. One or more power offsets indicated by the one or more RACH parameters may exist. The one or more RACH parameters can indicate: power ramp-up steps; power offset between SSB and CSI-RS; power offset between the transmissions of the first message (e.g., Msg 1 1311) and the third message (e.g., Msg 3 1313); and / or power offset values ​​between preamble groups. The one or more RACH parameters may indicate one or more thresholds, for example, the wireless device may determine at least one reference signal (e.g. SSB and / or CSI-RS) and / or uplink carrier (e.g. normal uplink (NUL) carrier and / or supplementary uplink (SUL) carrier) based on the one or more thresholds.

[0150] The first message (e.g., Msg 1 1311) may contain one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). RRC messages may be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may contain one or more preambles. The wireless device may determine the preamble group, for example, based on path loss measurements and / or the magnitude of the third message (e.g., Msg 3 1313). The 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 with an RSRP higher than an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message, the wireless device may select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0151] For example, the wireless device can determine the preamble based on one or more RACH parameters provided / configured / included in configuration message 1310. The wireless device can determine the preamble, for example, based on path loss measurements, RSRP measurements, and / or the size of a third message (e.g., Msg 3 1313). The one or more RACH parameters can indicate: the preamble format; the maximum number / quantity of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station can use the one or more RACH parameters to configure an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the wireless device. For example, if an association is configured, the wireless device can determine the preamble to be included in a first message (e.g., Msg 1 1311) based on the association. The first message (e.g., Msg 1 1311) can be transmitted / transmitted to the base station via one or more PRACH timings. The wireless device may use one or more reference signals (e.g., SSB and / or CSI-RS) to select the preamble and determine the PRACH timing. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate the association between the PRACH timing and the one or more reference signals.

[0152] For example, if no response is received based on the preamble transmission (e.g., after or in response to it) (e.g., within a period of time, such as a monitoring window for monitoring RAR), the wireless device can perform a preamble retransmission. The wireless device can increase the uplink transmission power for preamble retransmission. The wireless device can select the initial preamble transmission power, for example, based on path loss measurements and / or the target receive preamble power configured by the network. The wireless device can determine to retransmit / re-transmit the preamble and can ramp up the uplink transmission power. The wireless device can receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramp step for preamble retransmission. The ramp step size can be the amount by which the uplink transmission power for retransmission is incrementally increased. For example, if the wireless device determines that the same reference signal (e.g., SSB and / or CSI-RS) is used as in the previous preamble transmission, the wireless device can ramp up the uplink transmission power. The wireless device can, for example, use a counter parameter (e.g., PREAMBLE_TRANSMISSION_COUNTER) to count the number of preamble transmissions and / or retransmissions. For example, if the number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax) without receiving a successful response (e.g., RAR), the wireless device can determine that the random access procedure was unsuccessful.

[0153] The second message (e.g., Msg 2 1312) (e.g., received by a wireless device) may contain a RAR. The second message (e.g., Msg 2 1312) may contain multiple RARs corresponding to multiple wireless devices. The second message (e.g., Msg 2 1312) may be received, for example, based on the transmission / transmission of the first message (e.g., Msg 1 1311) (e.g., after or in response to it). The second message (e.g., Msg 2 1312) may be scheduled on the DL-SCH and may be indicated by the PDCCH, for example, using a Random Access Radio Network Temporary Identifier (RA RNTI). The second message (e.g., Msg 2 1312) may indicate that the base station has received the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may include a timing alignment command (which can be used by the wireless device to adjust the transmission timing of the wireless device), scheduling permission for transmitting the third message (e.g., Msg 3 1313), and / or a temporary cell RNTI (TC-RNTI). For example, after sending / transmitting the first message (e.g., Msg 1 1311) (e.g., a preamble), the wireless device may determine / start a time window (e.g., a ra-ResponseWindow) to monitor the PDCCH for the second message (e.g., Msg 2 1312). The wireless device may determine the start time of the time window, for example, based on the PRACH timing used by the wireless device to send / transmit the first message (e.g., Msg 1 1311) (e.g., a preamble). The radio device may start one or more symbol start time windows after the last symbol of the first message containing the preamble (e.g., Msg 1 1311) (e.g., the symbol in which the first message containing the preamble transmission (Msg 1 1311) is completed, or the first PDCCH timing after the end of the preamble transmission). These one or more symbols may be determined based on a set of parameters. The PDCCH may be mapped into a common search space configured by RRC messages (e.g., the Type 1-PDCCH common search space). The radio device may identify / determine the RAR, for example, based on the RNTI. The Radio Network Temporary Identifier (RNTI) may be used based on one or more events that initiate / start the random access procedure. The radio device may use the RA-RNTI, for example, for one or more communications associated with random access or any other purpose. The RA-RNTI may be associated with the PRACH timing in which the radio device transmits / transmits the preamble. The radio device may determine the RA-RNTI, for example, based on at least one of the following: OFDM symbol index; time slot index; frequency domain index; and / or the UL carrier indicator of the PRACH timing. Example RA-RNTI can be determined as follows:

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

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

[0156] A wireless device may, for example, send / transmit a third message (e.g., Msg 3 1313) based on (e.g., after or in response to) the successful reception of a second message (e.g., Msg 2 1312). This third message (e.g., Msg 3 1313) can be used, for example, for contention resolution in a contention-based random access procedure. Multiple wireless devices may send / transmit the same preamble to the base station, and the base station may send / transmit a RAR corresponding to a wireless device. For example, a conflict may occur if the multiple wireless devices interpret the RAR as corresponding to themselves. Contention resolution (e.g., using a third message (e.g., Msg 3 1313) and a fourth message (e.g., Msg 4 1314)) can be used to increase the likelihood that a wireless device will not mistakenly use the identity of another wireless device. For example, a wireless device may include a device identifier (e.g., a TC RNTI in a second message (e.g., Msg2 1312) if a C-RNTI is assigned) in a third message (e.g., Msg 3 1313) to perform contention resolution.

[0157] A fourth message (e.g., Msg 4 1314) can be received, for example, based on the transmission / transmission of a third message (e.g., Msg 3 1313) (e.g., after or in response to it). For example, if a C-RNTI is included in the third message (e.g., Msg 3 1313), the base station can use the C-RNTI to address the radio on the PDCCH (e.g., the base station can send the PDCCH to the radio device). For example, if a unique C RNTI of the radio device is detected on the PDCCH (e.g., the PDCCH is scrambled by the C-RNTI), the random access procedure can be determined to have been successfully completed. For example, if a TC RNTI is included in the third message (e.g., Msg 3 1313) (e.g., if the radio device is in an RRC idle (e.g., RRC_IDLE) state or is not otherwise connected to the base station), the fourth message (e.g., Msg 4 1314) can be received using the DL-SCH associated with the TC RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU contains a radio device contention resolution identity MAC CE that matches or otherwise corresponds to the CCCHSDU sent / transmitted in a third message (e.g., Msg 3 1313), the radio device can determine that the contention resolution was successful and / or the radio device can determine that the random access procedure was successfully completed.

[0158] The radio device can be configured with SUL carriers and / or NUL carriers. Initial access (e.g., random access) can be supported via the uplink carrier. The base station can configure multiple RACH configurations for the radio device (e.g., two separate RACH configurations, one for the SUL carrier and the other for the NUL carrier). For random access in a cell configured with an SUL carrier, the network can indicate which carrier (NUL or SUL) to use. 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 below a broadcast threshold, the radio device can determine to use the SUL carrier. Uplink transmissions of random access procedures (e.g., a first message (e.g., Msg 1 1311) and / or a third message (e.g., Msg 3 1313)) can be maintained on or performed via the selected carrier. The radio device can switch the uplink carrier during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). The wireless device may determine and / or switch uplink carriers for the first message (e.g., Msg1 1311) and / or the third message (e.g., Msg 3 1313) based, for example, on channel idle assessment (e.g., listen-before-speak).

[0159] Figure 13BA two-step random access procedure is illustrated. This two-step random access procedure may include a two-step contention-free random access procedure. Similar to a four-step contention-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 initiating the procedure. Configuration message 1320 may be similar in some respects to configuration message 1310. Figure 13B The procedure shown may include the transmission of two messages: a first message (e.g., Msg 1 1321) and a second message (e.g., Msg 2 1322). The first message (e.g., Msg 1 1321) and the second message (e.g., Msg 2 1322) may be similar to the first message (e.g., Msg 1 1311) and the second message (e.g., Msg 2 1312), respectively. The two-step contention-free random access procedure may not include messages similar to a third message (e.g., Msg 3 1313) and / or a fourth message (e.g., Msg 4 1314).

[0160] A two-step (e.g., contention-free) random access procedure can be configured / initiated for beam failure recovery, other SI requests, SCell addition and / or handover. The base station can indicate or assign a preamble to the radio device for the first message (e.g., Msg 1 1321). The radio device can receive the preamble indication (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0161] A radio device can, for example, initiate a time window (e.g., ra-ResponseWindow) for monitoring PDCCH against RAR based on a transmit / transmit preamble (e.g., after or in response to it). A base station can configure one or more beam fault recovery parameters for the radio device, such as separate time windows and / or separate PDCCHs in the search space indicated by an RRC message (e.g., recoverySearchSpaceId). The base station can configure these one or more beam fault recovery parameters, for example, in association with a beam fault recovery request. A separate time window for monitoring PDCCH and / or RAR can be configured to begin after the transmit / transmit beam fault recovery request (e.g., the window can begin after any number of symbols and / or time slots after the transmit / transmit beam fault recovery request). The radio device can monitor PDCCH transmissions addressed to the cell RNTI (C-RNTI) in the search space. During a two-step (e.g., contention-free) random access procedure, for example, based on the transmission / transmission of a first message (e.g., Msg 1 1321) and the receipt of a corresponding second message (e.g., Msg 2 1322) (e.g., after or in response to this), the radio device can determine that the random access procedure was successful. For example, if the PDCCH transmission is addressed to the corresponding C-RNTI, the radio device can determine that the random access procedure has been successfully completed. For example, if the radio device receives a RAR containing a preamble identifier corresponding to a preamble sub-transmission by the radio device and / or the RAR contains a MAC sub-PDU with a preamble identifier, the radio device can determine that the random access procedure has been successfully completed. The radio device can determine the response as an indication of acknowledgment of the SI request.

[0162] Figure 13C An example two-step random access procedure is shown. Similar to... Figure 13A and Figure 13B In the random access procedure shown, the base station (e.g., base station 1302) may send / transmit configuration message 1330 to the wireless device (e.g., wireless device 1301) before initiating the procedure. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. Figure 13C The program shown may include the transmission of multiple messages (e.g., two messages, including: a first message (e.g., Msg A 1331) and a second message (e.g., Msg B 1332)).

[0163] Msg A 1320 can be sent / transmitted by a wireless device in an uplink transmission. Msg A 1320 may contain 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., Msg 3 1313). Figure 13A (As shown in the diagram). Transport block 1342 may contain UCIs (e.g., SR, HARQ ACK / NACK, etc.). The wireless device may receive a second message (e.g., Msg B 1332) for example, based on sending / transmitting a first message (e.g., Msg A 1331) (e.g., after or in response to this). The second message (e.g., Msg B 1332) may contain the same content as the second message (e.g., Msg 2 1312) (e.g., ...). Figure 13A The contents of the second message (e.g., Msg 2 1322) shown in the RAR (e.g., the RAR), are also shown in the RAR. Figure 13B The RAR shown in the image) and / or the fourth message (e.g., Msg 4 1314) (e.g., Figure 13A (as shown in the image) Similar and / or equivalent content.

[0164] Wireless devices can initiate / propose a two-step random access procedure for licensed and / or unlicensed spectrum (e.g., Figure 13C The two-step random access procedure is illustrated in the diagram. A radio device may determine whether to initiate / initiate a two-step random access procedure based on one or more factors. These factors may include at least one of the following: the radio access technology being used (e.g., LTE, NR, etc.); whether the radio device has a valid TA; cell size; the radio device's RRC status; spectrum type (e.g., licensed vs. unlicensed); and / or any other suitable factors.

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

[0166] Transport block 1342 may contain data (e.g., delay-sensitive data), a radio device identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send / transmit a second message (e.g., Msg B 1332) as a response to the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may contain at least one of the following: a preamble identifier; a timing advance command; a power control command; uplink grant (e.g., radio resource allocation and / or MCS); a radio device identifier (e.g., a UE identifier for contention resolution); and / or an RNTI (e.g., a C-RNTI or TC-RNTI). For example, if the preamble identifier in the second message (e.g., Msg B 1332) corresponds to or matches the preamble sent / transmitted by the wireless device and / or the identifier of the wireless device in the second message (e.g., Msg B 1332) corresponds to or matches the identifier of the wireless device in the first message (e.g., Msg A 1331) (e.g., transport block 1342), then the wireless device can determine that the two-step random access procedure was successfully completed.

[0167] The wireless device and the base station can exchange control signaling (e.g., control information). This control signaling may be referred to as 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 sent / transmitted from the base station to the wireless device and / or uplink control signaling sent / transmitted from the wireless device to the base station.

[0168] Downlink control signaling may include at least one of the following: downlink scheduling assignment; uplink scheduling permission indicating uplink radio resources and / or transmission format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. A radio device may receive downlink control signaling in the payload transmitted / transmitted by a base station via the PDCCH. The payload transmitted / transmitted via the PDCCH may be referred to as downlink control information (DCI). The PDCCH may be a group common PDCCH (GC-PDCCH) shared by a group of radio devices. The GC-PDCCH may be scrambled by a group common RNTI.

[0169] A base station can attach one or more Cyclic Redundancy Check (CRC) parity bits to a DCI, for example, to facilitate the detection of transmission errors. For instance, if the DCI is intended for use with a wireless device (or a group of wireless devices), the base station can scramble the CRC parity bits using the identifier of the wireless device (or the identifier of the group of wireless devices). Scrambling the CRC parity bits using the identifier can include a modulo-2 addition (or XOR operation) of the identifier value and the CRC parity bits. The identifier can include a 16-bit value of the RNTI.

[0170] DCIs can be used for various purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with CRC parity bits scrambled with the Paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. The P-RNTI can be predefined as hexadecimal "FFFE". A DCI with CRC parity bits scrambled with the System Information RNTI (SI-RNTI) can indicate broadcast transmission of system information. The SI-RNTI can be predefined as hexadecimal "FFFF". A DCI with CRC parity bits scrambled with the Random Access RNTI (RA-RNTI) can indicate a Random Access Response (RAR). A DCI with CRC parity bits scrambled with the Cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). Figure 13A The Msg 3 shown is Msg 3 of 1313. Other RNTIs configured by the base station for the radio device may include the configured scheduling RNTI (CS RNTI), transmission power control PUCCH RNTI (TPC PUCCH-RNTI), transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), transmission power control SRS RNTI (TPC-SRS-RNTI), interrupt RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C RNTI), etc.

[0171] A base station may transmit / transmit a DCI using one or more DCI formats, for example, depending on the purpose and / or content of the DCI. DCI format 0_0 can be used to schedule PUSCH within a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​can be used to schedule PUSCH within a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used to schedule PDSCH within a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used to schedule PDSCH within a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide a slot format indication to a group of radio devices. DCI format 2_1 can be used to notify / inform a group of radio devices of physical resource blocks and / or OFDM symbols, where the group of radio devices may assume that no transmissions are intended for that group of radio devices. DCI format 2_2 can be used to transmit Transmit Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission of one or more wireless devices. New DCI formats with new features can be defined in future versions. DCI formats can have different DCI sizes or can share the same DCI size.

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

[0173] Figure 14AAn example of a CORESET configuration is shown. CORESET configuration can be used for a bandwidth portion or any other frequency band. A base station can transmit / transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET can include time-frequency resources that a radio device attempts to decode the DCI using one or more search spaces. The base station can configure the size and location of the CORESET in the time-frequency domain. The first CORESET 1401 and the second CORESET 1402 can appear at the first symbol of a time slot, or can be set / configured at the first symbol of a time slot. The first CORESET 1401 can overlap with the second CORESET 1402 in the frequency domain. The third CORESET 1403 can appear at the third symbol of a time slot, or can be set / configured at the third symbol of a time slot. The fourth CORESET 1404 can appear at the seventh symbol of a time slot, or can be set / configured at the seventh symbol of a time slot. CORESETs can have different numbers / numbers of resource blocks in the frequency domain.

[0174] Figure 14B An example of CCE-to-REG mapping is shown. CCE-to-REG mapping for DCI transmission can be performed via CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved (e.g., for the purpose of providing frequency diversity) or non-interleaved (e.g., for the purpose of facilitating interference coordination and / or frequency-selective transmission in the control channel). The base station can perform different or the same CCE-to-REG mapping for different CORESETs. CORESETs can be associated with CCE-to-REG mapping (e.g., via RRC configuration). CORESETs can be configured with antenna port QCL parameters. Antenna port QCL parameters can indicate the QCL information for DM-RS received via the PDCCH of the CORESET.

[0175] The base station can send / transmit one or more RRC messages to the radio device, including configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters can indicate the association between the search space set and the CORESET. The search space set can include a set of PDCCH candidates formed by CCEs (e.g., at a given aggregation level). The configuration parameters can indicate at least one of the following: the number of PDCCH candidates to be monitored at each aggregation level; the PDCCH monitoring periodicity and PDCCH monitoring mode; one or more DCI formats to be 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). A set of CCEs in the common search space set can be predefined and known to the radio device. A set of CCEs in the radio device-specific search space set (e.g., a UE-specific search space set) can be configured, for example, based on the radio device's identity (e.g., C-RNTI).

[0176] like Figure 14B As shown, the wireless device can determine the time-frequency resources for the CORESET based on one or more RRC messages. The wireless device can determine the CCE-to-REG mapping (e.g., interleaved or non-interleaved and / or mapping parameters) for the CORESET, for example, based on the CORESET's configuration parameters. The wireless device can determine, for example, the number of search space sets configured on / for the CORESET (e.g., up to 10) based on the one or more RRC messages. The wireless device can monitor a set of PDCCH candidates based on the configuration parameters of the search space sets. The wireless device can monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates using possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the device-specific search space), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The device may determine that the DCI is valid for the device, for example, based on a CRC check (e.g., the scrambled bits of the CRC parity bit of the DCI match the RNTI value) (e.g., after or in response to this). The device may process information included in the DCI (e.g., scheduling assignment, uplink granting, power control, slot format indication, downlink preemption, etc.).

[0177] Uplink control signaling (e.g., UCI) can be sent / transmitted to the base station. This uplink control signaling may include HARQ acknowledgments for received DL-SCH transport blocks. The radio device may send / transmit HARQ acknowledgments, for example, based on the receipt of a DL-SCH transport block (e.g., after or in response to it). Uplink control signaling may include a Channel Quality Indicator (CSI) indicating the channel quality of the physical downlink channel. The radio device may send / transmit the CSI to the base station. Based on the received CSI, the base station may determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. Uplink control signaling may include a Schedule Request (SR). The radio device may send / transmit an SR indicating that uplink data is available for transmission to the base station. The radio device may send / transmit UCIs (e.g., HARQ acknowledgments, CSI reports, SRs, etc.) via PUCCH or PUSCH. The radio device may use one of several PUCCH formats to send / transmit uplink control signaling via PUCCH.

[0178] Multiple PUCCH formats can exist (e.g., five PUCCH formats). The radio device can determine the PUCCH format, for example, based on the size of the UCI (e.g., the number of uplink symbols and the number of UCI bits transmitted). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. If transmission is carried out via one or two symbols, and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the radio device can transmit / transmit the UCI via PUCCH resources, for example, using PUCCH format 0. PUCCH format 1 can occupy a certain number of OFDM symbols (e.g., between four and fourteen OFDM symbols) and can include two or fewer bits. For example, if transmission is carried out via four or more symbols, and the number of HARQ-ACK / SR bits is one or two, the radio device can use PUCCH format 1. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. For example, if the transmission is via one or two symbols and the number of UCI bits is two or more, the wireless device can use PUCCH format 2. PUCCH format 3 can occupy a certain number of OFDM symbols (e.g., between four and fourteen OFDM symbols) and can include more than two bits. For example, if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal coverage code (OCC), the wireless device can use PUCCH format 3. PUCCH format 4 can occupy a certain number of OFDM symbols (e.g., between four and fourteen OFDM symbols) and can include more than two bits. For example, if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an OCC, the wireless device can use PUCCH format 4.

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

[0180] For example, after determining a PUCCH resource set from multiple PUCCH resource sets, the radio device can determine the PUCCH resources from the PUCCH resource set used for UCI (HARQ-ACK, CSI, and / or SR) transmissions. The radio device can determine the PUCCH resources, for example, based on the PUCCH resource indicator in the DCI (e.g., a DCI with DCI format 1_0 or for 1_1) received on / via the PDCCH. The n-bit (e.g., three-bit) PUCCH resource indicator in the DCI can indicate one of multiple (e.g., eight) PUCCH resources in the PUCCH resource set. The radio device can, for example, use the PUCCH resource indicated by the PUCCH resource indicator in the DCI to transmit / transmit UCI (HARQ-ACK, CSI, and / or SR).

[0181] Figure 15A An example communication between a wireless device and a base station is illustrated. The wireless device 1502 and the base station 1504 can be part of a communication network, such as... Figure 1A The communication network 100 shown in the figure Figure 1B The communication network 150 shown may be any other communication network. The communication network may include more than one wireless device and / or more than one base station, having [equipment / features] with [other features]. Figure 15A The base stations shown are basically the same or similar in configuration.

[0182] Base station 1504 can connect wireless device 1502 to the core network (not shown) via radio communication through air interface (or radio interface) 1506. The communication direction from base station 1504 to wireless device 1502 via air interface 1506 can be referred to as the downlink. The communication direction from wireless device 1502 to base station 1504 via air interface 1506 can be referred to as the uplink. Various duplex schemes (e.g., a combination of FDD, TDD, and / or duplex technologies) can be used to separate downlink and uplink transmissions.

[0183] For the downlink, data to be sent from base station 1504 to wireless device 1502 can be provided / transmitted / sent to processing system 1508 of base station 1504. Data can be provided / transmitted / sent to processing system 1508 via, for example, a core network. For the uplink, data to be sent from wireless device 1502 to base station 1504 can be provided / transmitted / sent to processing system 1518 of wireless device 1502. Processing systems 1508 and 1518 can implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, regarding... Figure 2A , Figure 2B , Figure 3 and Figure 4A The description includes the SDAP layer, PDCP layer, RLC layer, and MAC layer. Layer 3 may include, for example, information regarding... Figure 2B The RRC layer is described.

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

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

[0186] Base station 1504 may include multiple antennas (e.g., multiple antenna panels, multiple TRPs, etc.). Wireless device 1502 may include multiple antennas (e.g., multiple antenna panels, etc.). These multiple antennas can be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. Wireless device 1502 and / or base station 1504 may have a single antenna.

[0187] Processing systems 1508 and 1518 may be associated with memories 1514 and 1524, respectively. Memories 1514 and 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code executable by processing systems 1508 and / or 1518 to perform one or more functions (e.g., one or more functions described herein and other functions of a general-purpose computer, processor, memory, and / or other peripheral devices). 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-transitory computer-readable media) storing computer program instructions or code executable to perform one or more of their respective functions. Transmission processing system 1520 and / or reception processing system 1522 may be coupled to memory 1524 and / or another memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code executable to perform one or more of their respective functions.

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

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

[0190] Figure 15BExample elements of a computing device that can be used to implement any of the various devices described herein are shown, including, for example, base stations 160A, 160B, 162A, 162B, 220, 1210, 1302, 1710 and / or 1910, wireless devices 106, 156A, 156B, 210, 1205, 1301 and / or 1705, NCR nodes 1720, 180 and / or 1905, or any other base station, wireless device, AMF, UPF, network device, or computing device described herein. The computing device 1530 may include one or more processors 1531 that can execute instructions stored in random access memory (RAM) 1533, removable media 1534 (such as a Universal Serial Bus (USB) drive, compact disk (CD) or digital versatile optical disc (DVD), or floppy disk drive), or any other desired storage medium. Instructions may also be stored in an attached (or internal) hard disk drive 1535. The computing device 1530 may also include a security processor (not shown) that can execute instructions of one or more computer programs to monitor processes executing 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 disk 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., screen, display device, monitor, television, etc.), and may include one or more output device controllers 1537, such as a video processor. One or more user input devices 1538 may also be present, such as a remote control, keyboard, mouse, touchscreen, microphone, etc. The computing device 1530 may also include one or more network interfaces (e.g., network interface 1539), which may be wired, wireless, or a combination of both. Network interface 1539 can provide the computing device 1530 with an interface to communicate with network 1540 (e.g., RAN or any other network). Network interface 1539 may include a modem (e.g., a cable modem), and external network 1540 may include a communication link, external network, home network, provider wireless, coaxial cable, fiber optic, or hybrid fiber / coaxial cable distribution system (e.g., DOCSIS network), or any other desired network. Additionally, computing device 1530 may include a location detection device, such as a Global Positioning System (GPS) microprocessor 1541, which can be configured to receive and process GPS signals and determine the geographic location of computing device 1530 with possible assistance from external servers and antennas.

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

[0192] Figure 16A An example architecture for uplink transmission is shown. Processing of the baseband signal representing the physical uplink shared channel can include / perform one or more functions. These functions can include at least one of the following: scrambling; modulating the scrambling bits to generate complex-valued symbols; mapping the complex-valued modulated symbols onto one or more transport layers; transform precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA), CP-OFDM signals for antenna ports, or any other signals; etc. For example, if transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. For example, if transform precoding is not enabled (e.g., as...), Figure 16A As shown, CP-OFDM signals for uplink transmission can be generated. These functions are examples, and other mechanisms for uplink transmission can be implemented.

[0193] Figure 16B An example structure for modulation and upsampling conversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued SC-FDMA, CP-OFDM baseband signal (or any other baseband signal) and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal for the antenna port. For example, filtering can be performed / applied before transmission.

[0194] Figure 16CAn example architecture for downlink transmission is shown. Processing of the baseband signal representing the physical downlink channel can include / perform one or more functions. These functions can include: scrambling the coded bits in the codeword to be transmitted / transmitted on / via the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transport layers; precoding the complex-valued modulation symbols on the layers for transmission at the antenna port; mapping the complex-valued modulation symbols at the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port; etc. These functions are examples, and other mechanisms for downlink transmission can be implemented.

[0195] Figure 16D An example structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal used for the antenna port or any other signal. For example, filtering can be performed / applied before transmission.

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

[0197] A timer can begin running, for example, after it has started (e.g., once started) and continue running until it stops or until it expires. For example, a timer can be started if it is not running, or restarted if it is running. A timer can be associated with a value (e.g., a timer can be started or restarted from a value, or it can be started from zero and expire after it reaches that value (e.g., once that value is reached)). For example, the duration of a timer may not be updated until it stops or expires (e.g., due to a BWP switch). A timer can be used to measure time periods / windows of a process. Regarding implementations and / or procedures associated with one or more timers or other parameters, it should be understood that there can be multiple ways to implement such timers or other parameters. One or more of these multiple ways of implementing a timer can be used to measure time periods / windows used for a program. A random access response window timer can be used to measure the time window used to receive a random access response. The time difference between two timestamps can be used, for example, instead of starting the random access response window timer and determining its expiration. For example, if the timer is restarted, the process used to measure the time window can be restarted. Other example implementations can be configured / provided to restart the measurement of the time window.

[0198] A wireless device can receive one or more messages that include one or more configuration parameters of a cell. For example, a wireless device can receive one or more messages that include one or more configuration parameters of a cell from a base station.

[0199] For a cell, one or more configuration parameters can indicate at least two discontinuous transmissions (DTXs) ​​for energy saving in the cell. For example, the first DTX of the at least two DTXs can be used for the first TRP (e.g., as described in this article). Figure 21 , Figure 22 and Figure 23 The TRP 1 described herein, and the second DTX of at least two DTXs can be used for the second TRP (e.g., as described herein). Figure 21 , Figure 22 and Figure 23 The TRP 2 described in [the document]

[0200] A wireless device may not receive downlink reception (e.g., PDSCH reception, CSI-RS, etc.). For example, if the inactivity time, duration, and / or period of a cell's DTX is present, the wireless device may not receive downlink reception (e.g., PDSCH reception, CSI-RS, etc.). For example, if downlink reception associated with two TCI states (or two receive beams) overlaps in time with the inactivity time, period, and / or duration of a first DTX (e.g., first TRP off), but overlaps in time with the active time, period, and / or duration of a second DTX (e.g., second TRP on), or vice versa, this may not be efficient. Not receiving downlink reception may not be efficient. For example, if the second TRP is on during the inactivity time, period, and / or duration of a first DTX, not receiving downlink reception may not be efficient. This may increase the latency of data communication.

[0201] Downlink reception can be enhanced by being associated with at least two TCI states during inactivity periods, durations, and / or periods of at least two DTXs. If the device is in an inactivity period, duration, and / or period of at least two DTXs, it can receive downlink reception based on one of the TCI states. For example, if the device is in an inactivity period, duration, and / or period of a second DTX, it can receive downlink reception based on a first TCI state. If the device is in an inactivity period, duration, and / or period of a first DTX, it can receive downlink reception based on a second TCI state. The first and second TCI states can be, for example, different. This can reduce latency in data communication.

[0202] The wireless device may not support dynamic switching between a single TRP and multiple TRPs for downlink reception (e.g., PDSCH reception). For example, if the device is inactive for a period, duration, and / or cycle of at least two DTXs, it may not receive downlink reception based on one of the at least two TCI states. The base station may not disable one of the power-saving TRPs.

[0203] Downlink reception associated with at least two TCI states during inactivity periods, durations, and / or periods of at least two DTXs can be enhanced. For example, if the radio device does not support dynamic handover between a single TRP and multiple TRPs, downlink reception associated with at least two TCI states during inactivity periods, durations, and / or periods of at least two DTXs can be enhanced. If the radio device supports dynamic handover between a single TRP and multiple TRPs, and is during an inactivity period, duration, and / or period of at least two DTXs, then the radio device can receive downlink reception based on one of the at least two TCI states. If the radio device does not support dynamic handover between a single TRP and multiple TRPs, and is during an inactivity period, duration, and / or period of at least two DTXs, then the radio device can receive downlink reception based on at least two TCI states. If the radio device does not support dynamic handover between a single TRP and multiple TRPs, and is during an inactivity period, duration, and / or period of at least two DTXs, then the radio device may not receive downlink reception.

[0204] A wireless device may receive (e.g., from a base station or network) one or more messages (e.g., RRC messages, RRC reconfiguration messages) including one or more configuration parameters. The one or more configuration parameters may include one or more MAC cell group configuration parameters (e.g., MAC-CellGroupConfig) for a cell group containing the cell. The one or more MAC cell group configuration parameters may include one or more cell DTX configuration parameters (e.g., celldtx-Config) for configuring and / or indicating cell discontinuous transmission (DTX) of the cell. The one or more MAC cell group configuration parameters may include one or more cell DRX configuration parameters (e.g., celldrx-Config) for configuring and / or indicating cell discontinuous reception (DRX) of the cell. The one or more configuration parameters may include one or more serving cell configuration parameters (e.g., ServingCellConfig). The one or more serving cell configuration parameters may include one or more cell DTX configuration parameters (e.g., celldtx-Config) for configuring and / or indicating cell DRX of the cell.

[0205] Cell DTX can be implicitly activated once configured by the base station. Cell DTX can also be implicitly activated by the radio device, for example, based on sending (e.g., transmitting) one or more cell DTX configuration parameters once configured by the base station. One or more cell DTX configuration parameters can indicate an on-duration timer (e.g., celldtx-onDurationTimer) for cell DTX. One or more cell DTX configuration parameters can indicate an offset for the start of a cell DTX cycle (e.g., celldtx-CycleStartOffset). One or more cell DTX configuration parameters can indicate a slot offset (e.g., celldtx-SlotOffset) for cell DTX. One or more cell DTX configuration parameters may include a joint cell DTX-DRX configuration parameter (e.g., jointCellDTXDRXconfig). For example, if the joint cell DTX-DRX configuration parameter is set to true, the radio device can 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, the radio device can use a cell DRX configuration with the same parameters as in CellDTX-Config. Cell DTX can be deactivated by the radio device, for example, by releasing one or more cell DTX configuration parameters.

[0206] Cell DRX can be implicitly activated once configured by the base station. Cell DRX can also be implicitly activated by the radio device, for example, by sending (e.g., transmitting) one or more cell DRX configuration parameters once configured by the base station. One or more cell DRX configuration parameters can indicate an on-duration timer for cell DRX (e.g., celldrx-onDurationTimer). One or more cell DRX configuration parameters can indicate an offset for the start of a cell DRX cycle (e.g., celldrx-CycleStartOffset). One or more cell DRX configuration parameters can indicate a slot offset for cell DRX (e.g., celldrx-SlotOffset). Cell DRX can be deactivated by the radio device, for example, by releasing one or more cell DRX configuration parameters.

[0207] The cycle start offset can be common between cell DTX and cell DRX. For example, if one or more configuration parameters include both one or more cell DTX configuration parameters and one or more cell DRX configuration parameters, the cycle start offset can be common between cell DTX and cell DRX. The cycle start offset for cell DRX can be signaled in one or more cell DTX configuration parameters. For example, if the joint cell DTX-DRX configuration parameter is set to true, then the cycle start offset for cell DTX can indicate the cycle start offset for cell DRX. For example, if the joint cell DTX-DRX configuration parameter is set to true, then the cycle start offset for cell DTX can be the cycle start offset for both cell DTX and cell DRX.

[0208] The enable duration timer can be common between cell DTX and cell DRX. For example, if one or more configuration parameters include both one or more cell DTX configuration parameters and one or more cell DRX configuration parameters, the enable duration timer can be common between cell DTX and cell DRX. The enable duration timer for cell DRX can be signaled in one or more cell DTX configuration parameters. For example, if the combined cell DTX-DRX configuration parameter is set to true, then the enable duration timer for cell DTX can indicate the enable duration timer for cell DRX. Alternatively, if the combined cell DTX-DRX configuration parameter is set to true, then the enable duration timer for cell DTX can be the enable duration timer for both cell DTX and cell DRX.

[0209] The time slot offset can be common between the cell DTX and cell DRX. For example, if one or more configuration parameters include both one or more cell DTX configuration parameters and one or more cell DRX configuration parameters, then the time slot offset can be common between the cell DTX and cell DRX. The cell DRX time slot offset can be signaled in one or more cell DTX configuration parameters. For example, if the joint cell DTX-DRX configuration parameter is set to true, then the cell DTX time slot offset can indicate the cell DRX time slot offset. For example, if the joint cell DTX-DRX configuration parameter is set to true, then the cell DTX time slot offset can be the time slot offset of both the cell DTX and cell DRX.

[0210] To facilitate reducing downlink transmission or uplink reception activity time at a base station (e.g., gNB), radio devices can be configured by the base station with cell DTX and / or DRX of the cell (e.g., via CellDTX-Config, CellDRX-Config). The cell DTX and / or DRX of the cell can have periodic cell DTX and / or DRX modes (i.e., active and inactive periods). The periodic cell DTX and / or DRX modes can be common to one or more radio devices configured with cell DTX and / or DRX in the cell. The periodic cell DTX mode and the periodic cell DRX mode can be configured and / or activated individually. For example, if cell DTX is configured and activated for the cell, and if the radio device is in the inactive duration of cell DTX, the radio device may not monitor PDCCH or SPS timings unless there is an pending retransmission, or unless the random access timer and / or window (e.g., ra-ResponseWindow, ra-ContentionResolutionTimer) is running, or unless an SR is sent (e.g., transmitted) and is pending. For example, if cell DRX is configured and activated for a cell, and if a radio device is in the inactive period of cell DRX, the radio device may not transmit (e.g., transfer) on / via configured-granted (CG) resources, or may not transmit (e.g., transfer) SRs. Cell DTX and / or DRX may only apply to radio devices in the RRC_CONNECTED state. Cell DTX and / or DRX may at least not affect: random access procedures, SSB transmissions, paging, and system information broadcasts.

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

[0212] Cell DTX and / or DRX can be characterized by activity duration and / or cyclicity. Activity duration can be the duration during which a radio device can wait and / or monitor for opportunities to receive PDCCH or SPS and transmit (e.g., transmit) SR or CG. For the purpose of conserving network energy during activity duration, base station transmission and / or reception of PDCCH, SPS, SR, and CG may be unaffected. Cycle can specify the periodic repetition of activity durations, followed by a period of inactivity. If both cell DTX and cell DRX are configured, the activity duration and / or cyclicity parameters can be common between cell DTX and cell DRX.

[0213] Once the base station identifies the presence of an emergency call or public safety-related service (e.g., MPS or MCS), the network can ensure that there is no impact on the emergency call or public safety-related service (e.g., the base station can release or deactivate cell DTX and / or DRX). The base station can ensure that there is at least partial overlap between the on duration of the radio device's connection mode DRX and the active duration of cell DTX and / or DRX (e.g., the periodicity of the radio device's connection mode DRX is a multiple of the periodicity of cell DTX and / or DRX).

[0214] If the radio device receives a DCI (Distributed Control Information) for scheduling downlink reception (e.g., PDSCH, aperiodic CSI-RS) within the cell DTX, the radio device may receive downlink reception regardless of whether the downlink reception overlaps with the cell DTX's active time, period, and / or duration or inactive time, period, and / or duration (e.g., is in, is within, is in, etc.). The DCI may include dynamic permission for downlink reception. For example, after downlink reception, the radio device may send (e.g., transmit) HARQ-ACK information feedback for downlink reception regardless of whether the transmission of HARQ-ACK information overlaps with the cell DTX's active time, period, and / or duration or inactive time, period, and / or duration (e.g., is in, is within, is in, is in, is in).

[0215] If, within a cell DRX, the radio device receives a DCI scheduling uplink transmission (e.g., PUSCH, PUCCH, aperiodic SRS), the radio device may send (e.g., transmit) the uplink transmission, regardless of whether the uplink transmission overlaps with the cell DRX's active time, period, and / or duration or inactive time, period, and / or duration (e.g., is in, is within, is in, is among, etc.). The DCI may include dynamic permission for the uplink transmission. For example, after an uplink transmission, the radio device may receive a PDCCH from the base station (e.g., a DCI, a response to an uplink transmission / response to an uplink transmission), regardless of whether the PDCCH received transmission overlaps with the cell DRX's active time, period, and / or duration or inactive time, period, and / or duration (e.g., is in, is within, is among, is among, is among). For example, after an uplink transmission, a wireless device can monitor the PDCCH for a DCI from a base station (or for a response to an uplink transmission / uplink transmission response), regardless of whether the transmission of the PDCCH with the DCI overlaps with the active time, period and / or duration or inactive time, period and / or duration of the cell DTX (e.g., is in, within, etc.).

[0216] The inactivity time, period, and / or duration of cell DTX may include time outside the activity time, period, and / or duration of cell DTX. The inactivity time, period, and / or duration of cell DRX may include time outside the activity time, period, and / or duration of cell DRX.

[0217] The wireless device can receive one or more messages (e.g., RRC messages) from the base station. These messages can configure and / or indicate the periodic cell DTX and / or cell DRX patterns (i.e., active and inactive periods) of the cell (e.g., serving cell, non-serving cell, candidate cell, target cell, etc.).

[0218] Cell DTX or the cell DTX function can control the monitoring activities of radio devices in RRC_CONNECTED mode on the PDCCH and configured downlink assignments (e.g., SPS PDSCH). For a cell configured and activated with cell DTX, radio devices can use cell DTX or cell DTX operation to monitor the PDCCH and configured downlink assignments via the cell.

[0219] For all active cells (e.g., active serving cells) configured with cell DTX, the radio device can use cell DTX or cell DTX operation to monitor the PDCCH and configured downlink assignments. For each active cell (e.g., each active serving cell) configured and activated with cell DTX, the radio device can use cell DTX or cell DTX operation to monitor the PDCCH and configured downlink assignments.

[0220] Cell DRX or the cell DRX function can control the transmission activity of scheduling requests (SRs) and configured uplink grants made by radio devices in RRC_CONNECTED. For a cell configured and activated with cell DRX, the radio device can use cell DRX or cell DRX operation to send (e.g., transmit) scheduling requests and configured uplink grants via the cell. For all active cells configured with cell DRX (e.g., active serving cells), the radio device can use cell DRX (or cell DRX operation) to send (transmit) scheduling requests and configured uplink grants. For each active cell configured and activated with cell DRX (e.g., each active serving cell), the radio device can use cell DRX or cell DRX operation to send (e.g., transmit) scheduling requests and configured uplink grants.

[0221] One or more messages (e.g., RRC messages) can control cell DTX or cell DTX operation by configuring, indicating, and / or including the following parameters in one or more cell DTX configuration parameters (e.g., CellDTX-Config): celldtx-onDurationTimer: the start time of a cell DTX cycle or the active duration of a cell DTX cycle; celldtx-StartOffset: the subframe that defines the start of a cell DTX cycle or a cell DTX cycle; celldtx-SlotOffset: the delay before starting a cell DTX start duration timer (e.g., celldtx-onDurationTimer); celldtx-Cycle: the cycle period of a cell DTX cycle, or the cell DTX cycle period.

[0222] One or more messages (e.g., RRC messages) can control cell DRX or cell DRX operation by configuring, indicating, and / or including the following parameters in one or more cell DRX configuration parameters (e.g., CellDRX-Config): celldrx-onDurationTimer: the start time of a cell DRX cycle or the active duration of a cell DRX cycle; celldrx-StartOffset: the subframe that defines the start of a cell DRX cycle or a cell DRX cycle; celldrx-SlotOffset: the delay before starting a cell DRX start duration timer (e.g., celldrx-onDurationTimer); celldrx-Cycle: the cycle period of a cell DRX cycle, or the cell DRX cycle period.

[0223] If one or more configuration parameters include one or more cell DTX configuration parameters (e.g., CellDTX-Config) indicating and / or configuring the cell DTX of the serving cell (e.g., the cell DTX-onDurationTimer of the cell) are running, or if the cell DTX deactivation indication (e.g., DCI format 2_9 or RRC signaling) of the cell has been received by the radio device, then the cell DTX activity time, period, and / or duration may include time.

[0224] If one or more configuration parameters include one or more cell DRX configuration parameters (e.g., CellDRX-Config) that indicate and / or configure the cell's (e.g., serving cell) cell DRX, if the cell's celldrx-onDurationTimer is running, or if the cell's cell DRX deactivation indication (e.g., DCI format 2_9 or RRC signaling) has been received by the radio device, then the cell DRX activity time, period, and / or duration may include time.

[0225] The wireless device can start a cell on-duration timer (e.g., celldtx-onDurationTimer) after a slot offset (e.g., celldtx-SlotOffset) from the start of a subframe, based on receiving a cell DTX activation indication for the cell DTX (e.g., via DCI format 2_9 or via RRC signaling).

[0226] The radio device may start a cell on-duration timer (e.g., celldtx-onDurationTimer) after a slot offset (e.g., celldtx-SlotOffset) from the start of a subframe, based on receiving an indication of cell DTX activation (e.g., via DCI format 2_9 or via RRC signaling).

[0227] The wireless device can stop the on-duration timer (e.g., celldtx-onDurationTimer) (if it is running) based on the cell DTX deactivation indication received for the cell DTX of the cell (e.g., via DCI format 2_9 or via RRC signaling).

[0228] The wireless device can stop the on-duration timer (e.g., celldtx-onDurationTimer) (if it is running) based on receiving an instruction to deactivate the cell DTX of the cell (e.g., via DCI format 2_9 or via RRC signaling).

[0229] The wireless device can start a cell on-duration timer (e.g., celldrx-onDurationTimer) after a slot offset (e.g., celldrx-SlotOffset) from the start of a subframe, based on receiving a cell DRX activation indication for the cell DRX (e.g., via DCI format 2_9 or via RRC signaling).

[0230] The radio device can start a cell on-duration timer (e.g., celldrx-onDurationTimer) after a slot offset (e.g., celldrx-SlotOffset) from the start of a subframe, based on receiving an indication that the cell DRX is activated (e.g., via DCI format 2_9 or via RRC signaling).

[0231] The wireless device can stop the on-duration timer (e.g., celldrx-onDurationTimer) (if it is running) based on the cell DRX deactivation indication received for the cell DRX of the cell (e.g., via DCI format 2_9 or via RRC signaling).

[0232] The wireless device can stop the on-duration timer (e.g., celldrx-onDurationTimer) (if it is running) based on receiving an indication to deactivate the cell DRX of the indicated cell (e.g., via DCI format 2_9 or via RRC signaling).

[0233] 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, then the MAC layer and / or entity of the radio device may not instruct the physical layer and / or entity of the radio device to receive transport blocks on the DL-SCH according to or for the configured downlink assignment (e.g., SPS).

[0234] 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, then the MAC layer and / or entity of the radio device may instruct the physical layer and / or entity of the radio device to receive transport blocks on the DL-SCH according to or for the configured downlink assignment (e.g., SPS).

[0235] 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, then the MAC layer and / or entity of the radio device may not indicate the presence of any configured downlink assignment and may not deliver the stored HARQ information to the HARQ entity.

[0236] 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, then the MAC layer and / or entity of the radio device may indicate the presence of the configured downlink assignment and may deliver the stored HARQ information to the HARQ entity.

[0237] If the cell is not in the active time, period, and / or duration of a cell DTX, or if the cell is not in the active period of a cell DTX, or if the cell is in the inactive time, period, and / or duration of a cell DTX, the radio device may not monitor the PDCCH used for RNTI. The radio device may not monitor the PDCCH used for DCI scrambled with RNTI. RNTI may include at least one of the following, for example: 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.

[0238] If drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is operating on at least one cell in the DRX group, and if the cell in the DRX group is not in the cell DTX active time, period, and / or duration, if the cell is not in the cell DTX active period, or if the cell is in the cell DTX inactive time, period, and / or duration, the radio device can monitor the PDCCH for RNTI.

[0239] If drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is not operating on any cell in the DRX group, and if the cell in the DRX group is not in the active time, period, and / or duration of cell DTX, if the cell is not in the active period of cell DTX, or if the cell is in the inactive time, period, and / or duration of cell DTX, the radio device may not monitor the PDCCH for RNTI.

[0240] If ra-ContentionResolutionTimer or ra-ResponseWindow or msgB-ResponseWindow is running, and if the cell is not in the active time, period and / or duration of cell DTX, if the cell is not in the active period of cell DTX, or if the cell is in the inactive time, period and / or duration of cell DTX, the radio device can monitor the PDCCH for RNTI.

[0241] If ra-ContentionResolutionTimer and ra-ResponseWindow and msgB-ResponseWindow are not running, and if the cell is not in the active time, period and / or duration of cell DTX, or if the cell is not in the active period of cell DTX, or if the cell is in the inactive time, period and / or duration of cell DTX, the radio device may not monitor the PDCCH for RNTI.

[0242] If the cell is not in the active time, period and / or duration of the cell DTX, 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, the radio device may monitor the PDCCH for RNTI based on sending (e.g., transmitting) scheduling requests (e.g. on the PUCCH) and / or scheduling requests pending.

[0243] If a scheduling request is sent by a radio device (e.g., on a PUCCH) and / or a scheduling request is pending, if the cell is not in the active time, period, and / or duration of a cell DTX, if the cell is not in the active period of a cell DTX, or if the cell is in the inactive time, period, and / or duration of a cell DTX, the radio device may monitor the PDCCH used for RNTI.

[0244] 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), the radio device may not monitor the PDCCH for RNTI based on not sending (e.g., transmitting) scheduling requests (e.g. on the PUCCH) and / or the scheduling requests are not pending.

[0245] If the scheduling request is not sent by the radio device (e.g., transmitted) (e.g., on the PUCCH) and / or the scheduling request is not pending, if the cell is not in the active time, period and / or duration of the cell DTX, 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, the radio device may not monitor the PDCCH for RNTI.

[0246] If the cell is not in the active time, period, and / or duration of the cell DTX, 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, the radio device may monitor the PDCCH for the RNTI based on the absence of a DCI indicating a new transmission to the C-RNTI or the MAC entity of the radio device after successfully receiving a random access response for a contention-free random access procedure or after receiving a random access response for a contention-free random access procedure. For a contention-free random access procedure, the radio device may not select a random access preamble from one or more random access preambles used for and / or configured for use in a contention-based random access procedure.

[0247] If the cell is not in the active time, period, and / or duration of a cell DTX, if the cell is not in the active period of a cell DTX, or if the cell is in the inactive time, period, and / or duration of a cell DTX, the radio device may receive a DCI indicating a new transmission addressed to the radio device's C-RNTI or the radio device's MAC entity without monitoring the PDCCH for the RNTI, based on a random access response for a contention-free random access procedure or a random access response for a contention-free random access procedure. For a contention-free random access procedure, the radio device may not select a random access preamble from one or more random access preambles used for and / or configured for use in a contention-based random access procedure.

[0248] 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, the MAC layer and / or entity of the radio device may not instruct the physical layer and / or entity of the radio device to send (e.g., transmit) a scheduling request on the PUCCH resource.

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

[0250] 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, the radio device may not increment the SR counter of the pending SR.

[0251] If the cell is in an active time, period, and / or duration of the cell DRX, if the cell is in an active period of the cell DRX, or if the cell is not in an inactive time, period, and / or duration of the cell DRX, the radio device may increment the SR counter of the SR to be processed, for example, based on the transmission (e.g., transfer) of the SR.

[0252] 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, the radio device may not activate the sr-ProhibitTimer for the pending SR.

[0253] If the cell is in an active time, period, and / or duration of the cell DRX, if the cell is in an active period of the cell DRX, or if the cell is not in an inactive time, period, and / or duration of the cell DRX, the radio device may, for example, initiate an sr-ProhibitTimer for the pending SR based on the transmission (e.g., transmission) of the SR.

[0254] If the cell is not in the cell DRX 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 inactive time, period and / or duration, the MAC layer and / or entity of the radio device may not deliver any configured uplink grant and associated HARQ information to the HARQ entity.

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

[0256] If the cell is not in the cell DRX 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 inactive time, period and / or duration, the MAC layer and / or entity of the radio device may not obtain the uplink-granted MAC PDU to be sent (e.g., transmitted) for configuration from the multiplexing and assembly entity.

[0257] If the cell is in an active time, period, and / or duration of the cell DRX, if the cell is in an active period of the cell DRX, or if the cell is not in an inactive time, period, and / or duration of the cell DRX, the MAC layer and / or entity of the radio device can obtain the uplink-granted MAC PDU to be sent (e.g., transmitted) for configuration from the multiplexing and assembly entity.

[0258] 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, the MAC layer and / or entity of the radio device may not instruct the HARQ procedure associated with the configured uplink permission to trigger a new transmission or retransmission.

[0259] If the cell is in an active time, period, and / or duration of the cell, if the cell is in an active period of the cell DRX, or if the cell is not in an inactive time, period, and / or duration of the cell DRX, the MAC layer and / or entity of the radio device may instruct the HARQ process associated with the configured uplink permission to trigger a new transmission or retransmission.

[0260] If configured, and if the cell is not in an active period, cycle, and / or duration of the cell DRX, or if the cell is in an inactive period, cycle, and / or duration of the cell DRX, the radio device may not start or restart the configuredGrantTimer. If configured, and if the cell is not in an active period, cycle, and / or duration of the cell DRX, the radio device may start or restart the configuredGrantTimer. If configured, and if the cell is not in an active period, cycle, and / or duration of the cell DRX, the radio device may not start or restart the cg-RetransmissionTimer. If configured, and if the cell is in an active time, period, and / or duration of the cell DRX, if the cell is in an active period of the cell DRX, or if the cell is not in an inactive time, period, and / or duration of the cell DRX, the radio device may start or restart the cg-RetransmissionTimer.

[0261] If the cell DTX is inactive for a period, period, and / or duration, the radio device configured and activated with the cell DTX (e.g., celldtx-Config) may not expect to receive periodic CSI-RS and / or semi-persistent CSI-RS configured in the CSI report configuration (e.g., in CSI-ReportConfig) associated with the higher-layer parameter reportQuantity, which includes at least a rank indicator (RI). If the cell DTX is inactive for a period, period, and / or duration, the base station may not send (e.g., transmit) the periodic CSI-RS and / or semi-persistent CSI-RS configured in the CSI report configuration (e.g., in CSI-ReportConfig) associated with the higher-layer parameter reportQuantity, which includes at least a rank indicator (RI), to the radio device configured and activated with the cell DTX (e.g., celldtx-Config).

[0262] If the activity time, period, and / or duration of a cell DTX are in progress, then a radio device configured and activated with cell DTX (e.g., celldtx-Config) can expect to receive periodic CSI-RS and / or semi-persistent CSI-RS configured in a CSI reporting configuration (e.g., in CSI-ReportConfig) associated with a higher-layer parameter reportQuantity including at least a rank indicator (RI). If the activity time, period, and / or duration of a cell DTX are in progress, then the base station can send (e.g., transmit) periodic CSI-RS and / or semi-persistent CSI-RS configured in a CSI reporting configuration (e.g., in CSI-ReportConfig) associated with a higher-layer parameter reportQuantity including at least a rank indicator (RI) to a radio device configured and activated with cell DTX (e.g., celldtx-Config).

[0263] If a radio device is inactive during a cell DRX period, period, and / or duration, it may not expect to transmit (e.g., transmit) periodic SRS and / or semi-persistent SRS for channel acquisition. A radio device configured and activated with cell DRX (e.g., celldrx-Config) may transmit (e.g., send) SRS for location. If a radio device is inactive during a cell DRX period, period, and / or duration, SRS transmission for location may be unaffected by cell DRX or cell DRX operation.

[0264] If the cell is inactive during its DRX period, period, and / or duration, the base station may not receive periodic SRS or semi-persistent SRS for channel acquisition from radio devices configured with the cell DRX (e.g., celldrx-Config) and activated. If the cell is inactive during its DRX period, period, and / or duration, the base station may receive SRS for location from radio devices configured with the cell DRX (e.g., celldrx-Config) and activated. Location-based SRS transmissions may be unaffected by the cell DRX or cell DRX operation.

[0265] If the cell DRX is active during its time period, period, and / or duration, a radio device configured and activated with the cell DRX (e.g., celldrx-Config) may expect to transmit (e.g., transmit) periodic SRS and / or semi-persistent SRS for channel acquisition. If the cell DRX is active during its time period, period, and / or duration, the base station can receive periodic or semi-persistent SRS for channel acquisition from a radio device configured and activated with the cell DRX (e.g., celldrx-Config).

[0266] A radio device configured to operate a cell according to one or both of cell DTX operation of the cell according to cellDTXConfig and cell DRX operation of the cell according to cellDRXConfig may be additionally provided by dci-Format 2-9 for monitoring the PDCCH according to the common search space to detect the search space set of DCI Format 2-9 and the position of the cell DTX and / or DRX of the cell in DCI Format 2-9 determined by position-inDCI-NES.

[0267] One or more configuration parameters may include parameters (e.g., dci-Format2-9) indicating a search space set (e.g., a common search space set) used to monitor the PDCCH to detect a DCI format (e.g., DCI format 2_9). One or more configuration parameters may include position parameters (e.g., position-inDCI-NES) indicating the location of a cell's cell DTX and / or DRX in a DCI format (e.g., DCI format 2_9).

[0268] If the radio device is configured with cell DTX operation (e.g., via cellDTXConfig) and cell DRX operation (e.g., via cellDRXConfig), then cell DTX and / or DRX may include two bits. 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.

[0269] If the radio device is configured with only one of the cell DTX operation (e.g., via cellDTXConfig) and the cell DRX operation (e.g., via cellDRXConfig), then the cell DTX and / or DRX may include a bit indicating one of the cell DTX operation and the cell DRX operation, respectively.

[0270] The first value (e.g., '0') of the bits for cell DTX and / or DRX can indicate the deactivation of cell DTX or cell DRX. The second value (e.g., '1') of the bits for cell DTX and / or DRX can indicate the activation of cell DTX or cell DRX.

[0271] If a cell is configured with a SUL carrier in addition to a UL carrier (e.g., NUL), the cell DTX / DRX indication for activating or deactivating the cell DRX can be used for both the UL carrier and the SUL carrier.

[0272] The radio device may not expect to monitor PDCCH for DCI format 2_9 on more than one cell (e.g., more than one serving cell). If the radio device receives a PDCCH providing / having DCI format 2_9 in slot m on the active downlink BWP of a first cell (e.g., the first serving cell), which indicates a change in activation or deactivation of the current cell DTX operation or the current cell DRX operation of a second cell (e.g., the second serving cell), the radio device can operate the second cell according to the indicated cell DTX operation or the indicated cell DRX operation, respectively starting from a slot on the active downlink BWP or the active uplink BWP of the second cell, which may not precede the start of slot m+d on the active downlink BWP of the first cell, where The number of time slots is determined based on the subcarrier spacing (SCS) of the active downlink BWP in the first cell. For example, if the SCS of the active downlink BWP is 15kHz, the number of time slots is equal to 3. For example, if the SCS of the active downlink BWP is 30kHz, the number of time slots is equal to 6.

[0273] Outside of the activity time, period, and / or duration (e.g., DTX activity time, period, and / or duration), if in the cell DTX of a cell and / or the cell DTX of a cell, the radio device may not receive the PDCCH candidate of the search space set 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) and / or by resources provided by CSI-ReportConfig with reportQuantity including rank indication.

[0274] Outside of the activity time, period, and / or duration (e.g., DRX activity time, period, and / or duration), if the radio device is in and / or belongs to the cell's cell DRX, the radio device may transmit (e.g., transmit) periodic or semi-persistent PUCCH or PUSCH (e.g., CSI reports, configured uplink grants) and / or periodic or semi-persistent SRS without cell transmission, except for SRS in resources provided by SRS-posResourceSet.

[0275] Cell DTX can be a cell DTX operation, or it can be used interchangeably with cell DTX operation. Cell DRX can be a cell DRX operation, or it can be used interchangeably with cell DTX operation.

[0276] DCI format 2_9 can 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 for one or more cells (e.g., one or more serving cells) for one or more radio devices.

[0277] Information can be transmitted (e.g., transmitted) via DCI format 2_9 with 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 can be determined by the wireless device and / or base station using position parameters (e.g., positionInDCI-cellDTRX). One or more configuration parameters may include the position parameters.

[0278] One or more blocks can be configured for the radio device by a higher layer. For example, if the radio device is configured with DTX and / or DRX parameters (e.g., NES-RNTI, cellDTRX-DCI-config), then one or more blocks can be configured for the radio device by a higher layer. Fields can be defined for each block's cell DTX / DRX indication. Two bits, for example, if both cellDTXConfig and cellDTXConfig are configured for the cell, 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); one bit, for example, if either cellDTXConfig or cellDTXConfig is configured for the cell. One or more configuration parameters can include DTX and / or DRX parameters.

[0279] The size of DCI format 2_9 can be indicated by the higher-level parameter sizeDCI-2-9. One or more configuration parameters may include the higher-level parameter sizeDCI-2-9. The number of information bits in DCI format 2_9 can be equal to or less than 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 can be reserved.

[0280] Figure 17A and Figure 17B This is a flowchart illustrating an example of communication used for energy conservation. Figure 17B In step 1755, the base station may send one or more messages, and Figure 17A In step 1705, the wireless device may receive one or more messages. The one or more messages may include an activation command.

[0281] The radio device may configure a list of TCI states (e.g., TCI-States) within and / or through the higher-layer parameter PDSCH-Config to decode the PDSCH based on a detected PDCCH having DCIs intended for use by the radio 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 radio device capability parameter maxNumberConfiguredTCIstatesPerCC. Each TCI state (e.g., TCI-State) may include and / or indicate a corresponding parameter for configuring a quasi-co-location relationship between one or two downlink reference signals and the DM-RS port of the PDSCH, the DM-RS port of the PDCCH, or the CSI-RS port of the CSI-RS resource. The quasi-co-location relationship may be configured by the higher-layer parameter qcl-Type1 for a first downlink reference signal among one or more downlink reference signals. The quasi-co-location relationship may be configured by the higher-layer parameter qcl-Type2 for a second downlink reference signal among one or more downlink reference signals. If two downlink reference signals, including a first downlink reference signal and a second downlink reference signal, are indicated by the TCI state, then the QCL types of these two downlink reference signals can be different, regardless of whether the first downlink reference signal and the second downlink reference signal are the same or different. The quasi-colocation type corresponding to one or more downlink reference signals can be given by the higher-layer parameter qcl-Type in the higher-layer parameter QCL-Info, and can take one of the following values: 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}; 'typeB': {Doppler shift, Doppler spread}; 'typeC': {Doppler shift, average delay}; 'typeD': {spatial Rx parameter}.

[0282] The radio device may configure a TCI state list (e.g., up to 128 TCI state configurations) within and / or through the higher-layer parameter dl-OrJointTCI-StateList in the PDSCH-Config. The TCI states in the TCI state list provide and / or indicate reference signals for quasi-co-location of: i) the DM-RS of the PDSCH, ii) the DM-RS of the PDCCH in the BWP / cell, and / or iii) the CSI-RS. The TCI states in the TCI state list provide and / or indicate reference signals for determining uplink transmission space filters for i) dynamically granted PUSCH, ii) PUSCH based on configured granted PUSCH, iii) PUCCH resources in the BWP / cell, and / or iv) the SRS.

[0283] exist Figure 17B In step 1760, the base station can send an activation command, and Figure 17A In step 1705, the wireless device may receive an activation command. The wireless device may receive an activation command (e.g., MAC-CE, DCI) for mapping up to multiple TCI states and / or TCI state pairs (e.g., up to 8 TCI states and / or TCI state pairs) to the code points of the "Transmission Configuration Indication" field of the DCI field of a cell or a group of cells (e.g., downlink BWP) and / or up to multiple sets of TCI states (e.g., up to 8 sets of TCI states), one of which is used for a downlink channel (e.g., signaling) and / or one TCI state is used for an uplink channel (e.g., signaling). For a cell or a group of cells (e.g., downlink BWP), and if applicable, for a cell or a group of cells (e.g., uplink BWP), each of the multiple groups may include up to multiple TCI states (e.g., signaling and up to two TCI states) for downlink and uplink channels, or up to multiple TCI states (e.g., up to two TCI states) for downlink channels (e.g., signaling), and up to multiple TCI states (e.g., up to two TCI states) for uplink channels (e.g., signaling) to the code point of the DCI field 'Transmission Configuration Indication'. If an activation command activates a set of TCI state IDs for a group of cells (e.g., downlink BWP) and, if applicable, for a group of cells (e.g., uplink BWP), where the applicable list of cells can be determined by the radio device through the cells indicated in the activation command, then that set of TCI state IDs (e.g., the same set of TCI state IDs) may be used by the radio device for all downlink BWPs and / or uplink BWPs in the indicated cells or the applicable list of cells. If the activation command maps the TCI state and / or TCI-UL state to only one (e.g., a single) TCI code point, then once the radio device uses the indicated mapping for a single TCI code point, the radio device can use the TCI state and / or TCI-UL state (e.g., the indicated TCI state and / or TCI-UL state) for a cell or a group of cells (e.g., downlink BWP), and, if applicable, for a cell or a group of cells (e.g., uplink BWP).

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

[0285] If a radio device configured with dl-OrJointTCI-StateList by one or more configuration parameters (e.g., RRC messages / parameters) transmits (e.g., 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 if the indicated TCI state differs from a previously indicated TCI state, the indicated TCI state may be used by the radio device starting from a first (e.g., start, earliest, etc.) time slot, which may be at least a number of symbols following the last symbol of the uplink transmission (e.g., ...). Symbols). The first (e.g., start, earliest, etc.) time slot and the number of symbols can be determined by the radio device based on the active BWP with the smallest subcarrier spacing among the BWPs of the cell using the indicated TCI states, which are active at the end of an uplink transmission carrying a positive HARQ-ACK. The number of symbols can be provided to the radio device (e.g., indicated) via RRC messages (e.g., one or more configuration parameters).

[0286] The wireless device can be configured by higher-layer parameters (e.g., cjtSchemePDSCH and dl-OrJointTCI-StateList), and the wireless device can indicate and / or report support for two joint TCI states for PDSCH-CJT using two TCI states for PDSCH reception. The wireless device can assume that the PDSCH DM-RS port for PDSCH reception is quasi-co-located (QCL-ed) with the downlink reference signal regarding the two indicated TCI states of QCL-Type A. For example, the wireless device can make this assumption if it is configured with the higher-layer parameter cjtSchemeA, if it is configured by the higher-layer parameters cjtSchemePDSCH and dl-OrJointTCI-StateList, and if it indicates and / or reports support for two joint TCI states for PDSCH-CJT using two TCI states for PDSCH reception.

[0287] Alternatively, the wireless device may assume that the PDSCH DM-RS port received by the PDSCH is quasi-QCL with respect to both of the two indicated TCI states of QCL-Type A, except for the QCL parameters {Doppler shift, Doppler spread} of the second indicated TCI state (e.g., the second joint TCI state). For example, the wireless device may make this assumption if it is configured with higher-layer parameters cjtSchemeB and if it uses the two TCI states for PDSCH reception to indicate and / or report support for the two joint TCI states for PDSCH-CJT.

[0288] exist Figure 17B In step 1765, the base station may send (e.g., transmit) PDSCH (e.g., based on TCI state), and Figure 17AIn step 1715, the wireless device can receive PDSCH. The wireless device can be configured with a higher-layer parameter dl-OrJointTCI-StateList, and the wireless device can 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 can be configured by a higher-layer parameter applyIndicatedTCIState to indicate, for example, whether the first TCI state, the second TCI state, or both indicated TCI states are used for PDSCH reception scheduled or activated by DCI format 1_0. The wireless device can be configured with a higher-layer parameter applyIndicatedTCIState that indicates whether the first TCI state, the second TCI state, or both indicated TCI states are used for PDSCH reception scheduled or activated by DCI format 1_0. For example, if the wireless device is in frequency range 1 (FR1) and is configured with the higher-layer parameter dl-OrJointTCI-StateList and two indicated TCI states, the wireless device can be configured by the higher-layer parameter regardless of 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. For example, if the wireless device is configured with the higher-layer parameter dl-OrJointTCI-StateList and two indicated TCI states including a first TCI state and a second TCI state (e.g., two indicated joint / DL TCI states), the wireless device can report the capability of two default beams in frequency range 2 (FR2) and is configured by the higher-layer parameter. For example, if the wireless device does not report the capability of the two default beams in FR2, and if 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 equal to or greater than a threshold (e.g., timeDurationForQCL), the wireless device can be configured by higher-layer parameters.

[0289] The higher-level parameter applyIndicatedTCIState can be one of the values ​​{'first', 'second', 'both'}. The radio device can only configure the higher-level parameter applyIndicatedTCIState with a value of 'both' if the radio device is configured with the higher-level parameter cjtSchemePDSCH and / or if the radio device reports support for two joint TCI states for PDSCH-CJT, or if the radio device is configured with the higher-level parameter sfnSchemePdsch. If the higher-level parameter applyIndicatedTCIState is set to 'both', the radio device can use both indicated TCI states for PDSCH reception scheduled or activated by DCI format 1_0, which resides on a search space set other than the Type 0 / 0A / 2 CSS set at index zero (e.g., CORESET#0). The wireless device can receive DCI format 1_0 via a search space set different from the Type 0 / 0A / 2 CSS set associated with the CORESET having index zero. If the wireless device is not configured with applyIndicatedTCIState, the first indicated TCI state can be used for PDSCH reception scheduled or activated by DCI format 1_0. If the wireless device is configured with the higher-layer parameter tciSelection-PresentInDCI, and if the wireless device receives DCI format 1_1 / 1_2 that is scheduled or activated for PDSCH reception during / via PDSCH transmission, the wireless device can determine the indicated TCI state (e.g., the indicated joint / DL TCI state) of the two indicated TCI states for PDSCH reception.

[0290] If DCI format 1_1 / 1_2 indicates code point "00" in the TCI selection field, the wireless device can use the first of the two indicated TCI states for all PDSCH DM-RS ports during PDSCH transmissions scheduled or activated by DCI format 1_1 / 1_2. If DCI format 1_1 / 1_2 indicates code point "01" in the TCI selection field, the wireless device can use the second of the two indicated TCI states for all PDSCH DM-RS ports during PDSCH transmissions scheduled or activated by DCI format 1_1 / 1_2. If DCI format 1_1 / 1_2 indicates code point "10" in the TCI selection field, the wireless device can use both indicated TCI states for PDSCH reception scheduled or activated by DCI format 1_1 / 1_2.

[0291] If the radio device is not configured with the higher-layer parameter tciSelection-PresentInDCI and if the radio device receives DCI format 1_1 / 1_2 for scheduling / activating PDSCH reception, the radio device can use both indicated TCI states for PDSCH reception scheduled or activated by DCI format 1_1 / 1_2. If the radio device does not report / support the ability to use the default beam of the SFN (e.g., sfn-DefaultDL-BeamSetup) for DCI format and schedule PDSCH reception without a TCI selection field, the radio device can expect to be configured with the higher-layer parameter tciSelection-PresentInDCI. If the base station does not receive from the radio device a report indicating support for and / or capability to use the default beam of the SFN (e.g., sfn-DefaultDL-BeamSetup) for the DCI format and to schedule PDSCH reception without a TCI selection field (e.g., a radio device capability message), the base station may send (e.g., transmit) one or more configuration parameters including the higher-layer parameter tciSelection-PresentInDCI to the radio device (e.g., in an RRC message). If the base station receives from the radio device a report indicating support for and / or capability to use the default beam of the SFN (e.g., sfn-DefaultDL-BeamSetup) for the DCI format and to schedule PDSCH reception without a TCI selection field (e.g., a radio device capability message), the base station may or may not send (e.g., transmit) one or more configuration parameters including the higher-layer parameter tciSelection-PresentInDCI to the radio device (e.g., in an RRC message).

[0292] The higher-layer parameter `applyIndicatedTCIState`, used to indicate whether a first TCI state, a second TCI state, or both indicated TCI states are used by a PDSCH received by DCI format 1_0 scheduling and / or activation, can be provided to the radio device by a downlink BWP indication (e.g., provided).

[0293] If the wireless device is configured with a higher-level 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, then for each, for and / or for an aperiodic CSI-RS resource set or an aperiodic CSI-RS resource within an aperiodic CSI-RS resource set, the wireless device may configure (e.g., set) a higher-level parameter `applyIndicatedTCIState` to instruct the wireless device to apply the first TCI state or the second TCI state to the aperiodic CSI-RS resource set or an aperiodic CSI-RS resource within an aperiodic CSI-RS resource set. For an aperiodic CSI-RS resource set used for CSI or beam management (BM), the wireless device may configure a higher-level parameter `followUnifiedTCIState`. The time and / or scheduling offset between the last symbol of the PDCCH carrying / having 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 DCI can be equal to or greater than a threshold (e.g., beamSwitchTiming).

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

[0295] The wireless device can apply a first TCI state or a second TCI state to aperiodic CSI-RS via aperiodic CSI-RS resources based on or according to a higher-layer parameter applyIndicatedTCIState indicating (e.g., provided) to / for aperiodic CSI-RS resources or to a set of aperiodic CSI-RS resources including aperiodic CSI-RS resources. For example, if the wireless device has the capability to report two default beams in frequency range 1 (FR1) or frequency range 2 (FR2), and there is no downlink signal in the same symbol as the aperiodic CSI-RS resources, and if the wireless device is configured with the higher-layer parameter dl-OrJointTCI-StateList and has two indicated TCI states including the first TCI state and the second TCI state (e.g., two indicated joint / DL states), then the wireless device may apply a first TCI state or a second TCI state to aperiodic CSI-RS resources. The radio device may apply the first TCI state or the second TCI state to aperiodic CSI-RS based on or according to the higher-layer parameter applyIndicatedTCIState indicated to / for aperiodic CSI-RS resources or to aperiodic CSI-RS resource set including aperiodic CSI-RS resources, if the time and / or scheduling offset between the last symbol of the PDCCH carrying / having DCI and the first (e.g., start, earliest, etc.) symbol of the aperiodic CSI-RS resource set triggered by DCI is less than a threshold (e.g., beamSwitchTiming).

[0296] For example, if the wireless device has the capability to report two default beams in frequency range 1 (FR1) or frequency range 2 (FR2), if the wireless device is configured with the 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 last symbol of the PDCCH carrying / having 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 DCI is less than a threshold (e.g., beamSwitchTiming), the wireless device may use the first TCI state for aperiodic CSI-RS via the aperiodic CSI-RS resource based on or according to the higher-layer parameter applyIndicatedTCIState indicated (e.g., provided) to / for the aperiodic CSI-RS resource or to the aperiodic CSI-RS resource set including the aperiodic CSI-RS resource.

[0297] The wireless device can apply a first TCI state or a second TCI state to aperiodic CSI-RS via aperiodic CSI-RS resources based on (or according to) a higher-level parameter applyIndicatedTCIState indicated to / targeted an aperiodic CSI-RS resource or to a set of aperiodic CSI-RS resources including the aperiodic CSI-RS resource. For example, if the wireless device i) is configured with a higher-level parameter dl-OrJointTCI-StateList, ii) is configured by a higher-level parameter PDCCH-Config that includes two different values ​​of the higher-level parameter CORESETPoolIndex in different CORESETs (e.g., ControlResourceSets), iii) has two indicated TCI states (e.g., two indicated joint / DL states) including the first TCI state and the second TCI state. (TCI state), and if the time and / or scheduling offset between the last symbol of the PDCCH carrying / having 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 DCI is less than a threshold (e.g., beamSwitchTiming), if there is no downlink signal in the same symbol as the aperiodic CSI-RS resource, and if the radio device is in frequency range 1 (FR1), or the radio device reports the default beam per coreset pool index in frequency range 2 (FR2), then the radio device may use the first TCI state or the second TCI state for aperiodic CSI-RS via the aperiodic CSI-RS resource based on (or according to) the higher-layer parameter applyIndicatedTCIState indicated (e.g., provided) to / for the aperiodic CSI-RS resource or to the aperiodic CSI-RS resource set including the aperiodic CSI-RS resource.

[0298] Otherwise, for example, if the wireless device i) is configured with a higher-level parameter dl-OrJointTCI-StateList, ii) is configured by a higher-level parameter PDCCH-Config that includes two different values ​​of the higher-level parameter CORESETPoolIndex in different CORESETs (e.g., ControlResourceSets), iii) has two indicated TCI states (e.g., two indicated joint / DL states) including a first TCI state and a second TCI state. (TCI state), and if the time and / or scheduling offset between the last symbol of the PDCCH carrying / having 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 DCI is less than a threshold (e.g., beamSwitchTiming), if there is no downlink signal in the same symbol as the aperiodic CSI-RS resource, and if the radio device is in frequency range 1 (FR1), or the radio device has the ability to report the default beam per coreset pool index in frequency range 2 (FR2), the radio device may use the first TCI state associated with (or specifically having or specifically belonging to) the higher layer parameter coresetPoolIndex with a value of 0 for aperiodic CSI-RS via the aperiodic CSI-RS resource.

[0299] A wireless device may send (e.g., transmit) capability messages (e.g., wireless device capability messages) to a base station. Capability messages may include dynamic handover parameters (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2). Dynamic handover parameters may indicate whether the wireless device supports (e.g., is capable of) dynamic handover between single TRPs and multiple TRPs for downlink reception (e.g., PDSCH reception, PDCCH reception, etc.). Dynamic handover parameters may indicate whether the wireless device supports dynamic handover between single TRPs and PDSCH SFN schemes (e.g., sfnSchemeA, sfnSchemeB). Dynamic handover parameters may indicate whether the wireless device supports dynamic handover between non-SFN schemes (e.g., single TRP mode / operation / scheme) and PDSCH SFN schemes (e.g., multiple TRP mode / operation / scheme) for downlink reception. Dynamic switching parameters can indicate whether a 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.

[0300] Radio devices supporting dynamic handover can indicate the SFN scheme (e.g., sfn-SchemeA) or the SFN scheme used only for PDSCH reception (e.g., sfn-SchemeA-PDSCH-only) in the capability message. Dynamic handover parameters can indicate whether the radio device supports dynamic handover between a single TRP and a PDSCH SFN scheme via the TCI status field in DCI formats 1_1 and 1_2. Dynamic handover parameters can also indicate whether the radio device supports dynamic handover between a single TRP and a PDSCH SFN scheme via the TCI selection field in DCI formats 1_1 and 1_2. The dynamic handover parameters indicating whether the radio device supports dynamic handover between a single TRP and a PDSCH SFN scheme via the TCI status field in DCI formats 1_1 and 1_2 can be the same as those indicating whether the radio device supports dynamic handover between a single TRP and a PDSCH SFN scheme via the TCI selection field in DCI formats 1_1 and 1_2. The dynamic handover parameters, which indicate whether a wireless device supports dynamic handover between a single TRP and a PDSCH SFN scheme through the TCI status field in DCI formats 1_1 and 1_2, and the dynamic handover parameters, which indicate whether a wireless device supports dynamic handover between a single TRP and a PDSCH SFN scheme through the TCI selection field in DCI formats 1_1 and 1_2, can be different.

[0301] If the wireless device does not send (e.g., transmit, report, or indicate) the capability and / or support for dynamic handover to the base station, or if the capability message does not include dynamic handover parameters, then the wireless device may not expect the base station to configure the higher-layer parameter tciSelection-PresentInDCI. If the wireless device is not configured with the higher-layer parameter tciSelection-PresentInDCI, then DCI formats 1_1 and 1_2 may not include the TCI selection field.

[0302] If the wireless device does not send (e.g., transmit, report, or indicate) dynamic handover capability and / or support to the base station, or if the capability message does not include dynamic handover parameters, then the wireless device may not expect the base station to configure the higher-layer parameter tciSelection-PresentInDCI. If the wireless device is not configured with the higher-layer parameter tciSelection-PresentInDCI, then the wireless device may not receive DCI formats with the TCI selection field (e.g., DCI format 1_1, DCI format 1_2). If the wireless device is not configured with the higher-layer parameter tciSelection-PresentInDCI, then the wireless device may receive DCI formats without the TCI selection field (e.g., DCI format 1_1, DCI format 1_2).

[0303] If the radio device does not send (e.g., transmit, report, or indicate) the capability and / or support for dynamic handover to the base station, or if the capability message does not include dynamic handover parameters, then the base station may not send (e.g., transmit) one or more configuration parameters including the higher-layer parameter tciSelection-PresentInDCI to the radio device (e.g., in an RRC message). If one or more configuration parameters do not include the higher-layer parameter tciSelection-PresentInDCI, then the base station may not send (e.g., transmit) the DCI format with the TCI selection field to the radio device (e.g., DCI format 1_1, DCI format 1_2). If one or more configuration parameters do not include the higher-layer parameter tciSelection-PresentInDCI, then the base station may send (e.g., transmit) the DCI format without the TCI selection field to the radio device (e.g., DCI format 1_1, DCI format 1_2).

[0304] If the wireless device reports the capability of sfn-SchemeA-DynamicSwitching or sfn-SchemeB-DynamicSwitching, and if the wireless device is configured with a higher-layer parameter sfnSchemePdsch set to 'sfnSchemeA' or 'sfnSchemeB', the wireless device can indicate this with one or two TCI states in the code point of the DCI field 'Transmission Configuration Indication' in DCI format 1_1 / 1_2.

[0305] The wireless device may not expect an activation command (e.g., MAC CE) to indicate each TCI code point with one TCI state, and the wireless device may indicate two TCI states in the code point of the DCI field 'Transmission Configuration Indication' in DCI format 1_1 / 1_2.

[0306] Figure 18 An example of energy saving is illustrated. Wireless device 1805 can receive one or more messages. Wireless device 1805 can receive one or more messages from base station 1810. Base station 1810 can send (e.g., transmit) one or more messages. Wireless device 1805 can receive one or more messages from a relay node. Wireless device 1805 can receive one or more messages from another wireless device (e.g., TRP, vehicle, remote radio head, etc.). The one or more messages may include one or more configuration parameters 1815 (e.g., at time T0). The one or more configuration parameters 1815 may be one or more RRC configuration parameters. The one or more configuration parameters 1815 may be one or more RRC reconfiguration parameters (e.g., RRCReconfiguration, reconfigurationWithSync). The one or more messages may be one or more RRC messages. The one or more messages may be one or more RRC reconfiguration messages (e.g., RRCReconfiguration, reconfigurationWithSync). The one or more configuration parameters 1815 may be used in a cell.

[0307] A cell can be, for example, a serving cell. At least one of the configuration parameters 1815 can be used for a cell. A cell can be a primary cell (PCell). A cell can be a primary-secondary cell (PSCell). A cell can be a secondary cell (SCell). A cell can be a secondary cell configured with a PUCCH (e.g., a PUCCH SCell). A cell can be a special cell (SpCell). A SpCell can refer to (e.g., indicate) the PCell of an MCG or the PUCell of an SCG used for dual connectivity (DC) operation; otherwise, a SpCell can refer to (e.g., indicate) a PCell. A cell can be a primary SCG cell (PSCell). If, for example, a reconfiguration procedure with synchronization is performed for dual connectivity operation, the radio device 1805 can perform a random access procedure via the PUCell. A cell can be, for example, an unlicensed cell operating in an unlicensed frequency band. A cell can be a licensed cell (e.g., operating in a licensed frequency band). A cell can operate in a first frequency range (FR1). FR1 can, for example, include frequency bands below 6 GHz. A cell can operate in a second frequency range (FR2). FR2 may, for example, encompass a frequency band from 24 GHz to 52.6 GHz. The cell may operate in a third frequency range (FR3). FR3 may, for example, encompass a frequency band from 52.6 GHz to 71 GHz. FR3 may, for example, encompass a frequency band starting at 52.6 GHz (or higher).

[0308] Radio device 1805 can perform uplink transmission (e.g., PUSCH, PUCCH, PUCCH) via the cell at a first time and a first frequency. Radio device 1805 can perform downlink reception (e.g., PDCCH, PDSCH) via the cell at a second time and a second frequency. The cell can operate in Time Division Duplex (TDD) mode. In TDD mode, the first frequency and the second frequency can be the same. In TDD mode, the first time and the second time can be different. The cell can operate in Frequency Division Duplex (FDD) mode. In FDD mode, the first frequency and the second frequency can be different. In FDD mode, the first time and the second time can be the same. Radio device 1805 can be in an RRC connected state (e.g., mode 1805). Radio device 1805 can be in an RRC idle state (e.g., mode 1805). Radio device 1805 can be in an RRC inactive state (e.g., mode 1805).

[0309] A cell may include multiple BWPs. One or more configuration parameters 1815 can indicate multiple BWPs for a cell. These multiple BWPs may include one or more uplink BWPs, which include the cell's uplink BWPs. These multiple BWPs may also include one or more downlink BWPs, which include the cell's downlink BWPs.

[0310] One of the multiple BWPs can be in an active state, an inactive state, or a deactivated state. The wireless device 1805 can monitor downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) via and / or for one or more downlink BWPs while they are active. The wireless device 1805 can receive PDSCH via and / or for one or more downlink BWPs while they are active. The wireless device 1805 can stop monitoring downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) via and / or for one or more downlink BWPs while they are inactive. The wireless device 1805 can stop monitoring or receiving downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) via and / or for one or more downlink BWPs while they are inactive. The wireless device 1805 may not receive PDSCH via and / or for a downlink BWP when one or more downlink BWPs are inactive. The wireless device 1805 may also stop receiving PDSCH via and / or for a downlink BWP when one or more downlink BWPs are inactive.

[0311] The wireless device 1805 may transmit (e.g., transmit) uplink channels and / or signals (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) via an uplink BWP while the uplink BWP is active in one or more uplink BWPs. The wireless device 1805 may not transmit (e.g., transmit) uplink channels and / or signals (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) via an uplink BWP while the uplink BWP is inactive in one or more uplink BWPs.

[0312] The wireless device 1805 can activate one or more downlink BWPs in a cell. Activating a downlink BWP may include setting (e.g., switching) the downlink BWP to 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.

[0313] Radio device 1805 may activate one or more uplink BWPs in a cell. Activating an uplink BWP may include radio device 1805 setting (e.g., switching to) the active uplink BWP of the cell. 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.

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

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

[0316] 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 indicating a list of TCI states (e.g., provided by a higher-level (e.g., RRC) parameter dl-OrJoint-TCIStateList). 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), such as including a TCI state list parameter indicating multiple TCI states 1820. Multiple TCI states 1820, for example, as described herein... Figure 18 The states described are TCI state 0, TCI state 1, ... and TCI state M-1.

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

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

[0319] One or more configuration parameters 1815 may include, for example, one or more PDSCH configuration parameters for a second downlink BWP for a second cell. One or more configuration parameters 1815 may indicate multiple TCI states 1820 for the second downlink BWP for the second cell. For the cell's downlink BWP, one or more configuration parameters 1815 may include a reference unified TCI state list parameter (e.g., unifiedTCI-StateRef) indicating the second downlink BWP of the second cell. The reference unified TCI state list parameter may include a BWP index (e.g., BWP-Id) identifying and / or indicating the second downlink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) identifying and / or indicating the second cell. The second downlink BWP of the second cell may be a reference BWP of a reference cell for the cell's downlink BWP. The cell's downlink BWP may be a target BWP of the target cell. One or more PDSCH configuration parameters of the cell's downlink BWP can, for example, be based on one or more configuration parameters 1815 for the cell's downlink BWP, including reference to the unified TCI state list parameter but excluding higher-layer (e.g., RRC) parameters dl-OrJoint-TCIStateList.

[0320] 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 have a unified TCI state type parameter. The unified TCI state type parameter may indicate the unified TCI state type of the cell.

[0321] For example, the unified TCI state type parameter can be set to "Joint". The radio device 1805 can, for example, use multiple TCI states 1820 (e.g., provided / indicated by dl-OrJoint-TCIStateList) for both cell-level and / or uplink transmissions (e.g., PUSCH / PUCCH / SRS transmissions) and cell-level and / or downlink receptions (e.g., PDCCH / PDSCH / CSI-RS receptions) based on one or more configuration parameters 1815, including the unified TCI state type parameter set to "Joint". The multiple TCI states 1820 can, for example, be multiple joint TCI states.

[0322] For example, the unified TCI state type parameter can be set to "Separate". Radio device 1805 can, for example, use multiple TCI states 1820 (e.g., provided / indicated by the higher-layer parameter dl-OrJoint-TCIStateList) for cell and / or via cell downlink reception (e.g., PDCCH / PDSCH / CSI-RS reception) based on one or more configuration parameters 1815 including the unified TCI state type parameter set to "Separate". Radio device 1805 can, for example, not use multiple TCI states 1820 for cell and / or via cell uplink transmission (e.g., PUSCH / PUCCH / SRS transmission) based on one or more configuration parameters 1815 including the unified TCI state type parameter set to "Separate". The multiple TCI states 1820 can, for example, be multiple downlink TCI states.

[0323] One or more configuration parameters 1815 may indicate a second or more TCI states. One or more configuration parameters 1815 may include an uplink TCI state list parameter indicating a list of uplink TCI states (e.g., provided / indicated by a higher-layer parameter ul-TCI-StateList). The uplink TCI state list may include a second or more 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 or more TCI states. The second or more TCI states may be, for example, TCI state 0, TCI state 1, ... and TCI state M-1.

[0324] 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 or more TCI states for the cell's uplink BWP.

[0325] One or more configuration parameters 1815 may include, for example, one or more uplink BWP configuration parameters for a second uplink BWP of a second cell. One or more configuration parameters 1815 indicate a second plurality of TCI states for the second uplink BWP of the second cell. For the cell's uplink BWP, one or more configuration parameters 1815 may include a reference unified TCI state list parameter (e.g., unifiedtci-StateType) indicating the second uplink BWP of the second cell. The reference unified TCI state list parameter may include a BWP index (e.g., BWP-Id) identifying and / or indicating the second uplink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) identifying and / or indicating the second cell. The second uplink BWP of the second cell may be a reference BWP of a reference cell for the cell's uplink BWP. The cell's uplink BWP may be a target BWP of the target cell. One or more uplink BWP configuration parameters of a cell's uplink BWP may, for example, be based on one or more configuration parameters 1815 for the cell's uplink BWP, including reference to the unified TCI state list parameter but excluding higher-layer (e.g., RRC) parameters ul-TCI-StateList.

[0326] The radio device 1805 may, for example, use a second plurality of TCI states for cell and / or uplink transmissions (e.g., PUSCH / PUCCH / SRS transmissions) via the cell, for example, based on one or more configuration parameters 1815 including a uniform TCI state type parameter set to "Separate". The radio device 1805 may, for example, not use the second plurality of TCI states for cell and / or downlink receptions (e.g., PDCCH / PDSCH / CSI-RS receptions) via the cell, for example, based on one or more configuration parameters 1815 including a uniform TCI state type parameter set to "Separate". The second plurality of TCI states may, for example, be multiple uplink TCI states.

[0327] For downlink reception via the cell's downlink BWP, the radio device 1805 may, for example, use multiple TCI states 1820 indicated by one or more configuration parameters 1815 for the cell's downlink BWP. For uplink transmission reception via the cell's uplink BWP, the radio device 1805 may, for example, use multiple TCI states 1820 indicated by one or more configuration parameters 1815 for the cell's downlink BWP. For downlink reception via the cell's downlink BWP, the radio device 1805 may, for example, use multiple TCI states 1820 of the second cell's second downlink BWP indicated by a reference to a unified TCI state list parameter for the cell's downlink BWP.

[0328] For uplink transmission reception via the cell's uplink BWP, radio device 1805 may, for example, use multiple TCI states 1820 of the second cell's second downlink BWP, indicating the second downlink BWP of the second cell for the cell's downlink BWP based on reference to unified TCI state list parameters. For uplink transmission reception via the cell's uplink BWP, radio device 1805 may, for example, use a second plurality of TCI states, indicating a second plurality of TCI states for the cell's uplink BWP, based on one or more configuration parameters 1815. For uplink transmission reception via the cell's uplink BWP, radio device 1805 may, for example, use a second plurality of TCI states of the second cell's second uplink BWP, indicating the second cell's uplink BWP for the cell's uplink BWP based on reference to unified TCI state list parameters.

[0329] The wireless device 1805 can 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.). The activation command may, for example, indicate the activation of a subset of TCI states (e.g., two TCI states 1825) from multiple TCI states 1820 (e.g., DLorJoint-TCIStateList). The TCI state subset (e.g., two TCI states 1825) may be, for example, a subset of joint TCI states from multiple joint TCI states. The TCI state subset (e.g., two TCI states 1825) may be, for example, a subset of downlink TCI states from multiple downlink TCI states.

[0330] An activation command (e.g., a first control command 1830) may, for example, instruct the activation of a subset of TCI states (e.g., two TCI states 1825) within a second plurality of TCI states (e.g., ul-TCI-StateList). The subset of TCI states (e.g., two TCI states 1825) may, for example, be a subset of uplink TCI states within a plurality of uplink TCI states.

[0331] Base station 1810 can activate and / or deactivate a subset of TCI states (e.g., two TCI states 1825), for example, by sending (e.g., transmitting) an activation command. Wireless device 1805 can map the subset of TCI states (e.g., two TCI states 1825) to one or more TCI code points. The activation command can indicate the mapping of the subset of TCI states (e.g., two TCI states 1825) to one or more TCI code points. Wireless device 1805 can map the corresponding TCI state of the subset of TCI states (e.g., two TCI states 1825) to the corresponding TCI code point in one or more TCI code points. One or more TCI code points can indicate and / or include the subset of TCI states (e.g., two TCI states 1825). Each TCI code point in one or more TCI code points can indicate or be mapped to the corresponding TCI state in the subset of TCI states (e.g., two TCI states 1825). Each TCI code point in one or more TCI code points can indicate / including (or be mapped to) one or more TCI states.

[0332] 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 states 5 and 8. The third TCI code point (e.g., TCI code point 010) may include TCI states 26 and 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) indicate 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) indicate two TCI states (e.g., two joint TCI states, two uplink TCI states, two downlink TCI states, etc.).

[0333] Figure 19 An example of an activation command is shown. An activation command may include multiple fields. The first field 1905 (e.g., Serving Cell ID) may include a serving cell index, indicator, and / or identifier for indicating and / or identifying the cell. The first field 1905 may include a serving cell index, indicator, and / or identifier for indicating and / or identifying the cell to which the activation command applies. If one or more configuration parameters indicate and / or configure cells in the synchronous TCI update cell list (e.g., simultaneousTCI-UpdateList1, simultaneousTCI-UpdateList2) or configure cells as part of the synchronous TCI update cell list, the activation command can use each cell in the synchronous TCI update cell list.

[0334] The second field 1910 (e.g., BWP ID) among multiple fields may include a BWP index, indicator, and / or identifier that indicates and / or identifies the downlink BWP of the cell. The second field 1910 may include a BWP index, indicator, and / or identifier that indicates and / or identifies the downlink BWP of the cell to which the activation command applies, as well as the code point of the bandwidth portion indicator field in the DCI.

[0335] The third field among multiple fields is 1915 (for example, Figure 19 TCI status ID i,jThis may include a TCI state index, indicator, and / or identifier (e.g., TCI-StateId) that identifies a TCI state among multiple TCI states. Multiple TCI state indices may include TCI state indices. Index i may be an index of a code point in the Transport Configuration Indicator (TCI) field in the DCI. TCI State ID i,j It can be in TCI status ID i,j The transport configuration indication field in the DCI is for the first i The code point indicates the first j TCI status. TCI status ID 0,1 This can, for example, represent the first TCI state (e.g., the 1st TCI state) indicated by TCI code point 000. TCI State ID 0,2 This can represent the second TCI state (e.g., the 2nd TCI state) indicated by TCI code point 000. TCI State ID 1,1 This can, for example, represent the first TCI state (e.g., the first TCI state) indicated by TCI code point 001. TCI State ID 1,2 This can represent the second TCI state (e.g., the second TCI state) indicated by TCI code point 001. TCI State ID N,1 This can represent the first TCI state (e.g., the first TCI state) indicated by TCI code point 111, for example, if Figure 19 N in the TCI is equal to 8. N,2 This can represent the second TCI state (e.g., the 2nd TCI state) indicated by TCI code point 111. For TCI code point i, TCI state ID i,1 It can be represented as the first TCI state (e.g., the 1st TCI state), and the TCI state ID i,2 This can be represented as the second TCI state (e.g., the 2nd TCI state).

[0336] The TCI state mapped to the TCI code point can be determined by the wireless device and / or base station through the ordinal position of the TCI code point. It has a TCI state ID. 0,1 and TCI status ID 0,2 The first TCI code point can, for example, be mapped to code point value 0 (e.g., TCI code point 000), having a TCI state ID. 1,1 and TCI status ID 1,2 The second TCI code point can be mapped to code point value 1 (e.g., TCI code point 001), and so on.

[0337] The 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 may be mapped to the second TCI code point (e.g., TCI code point 001).

[0338] The activation command may include the TCI status index, indicator, and / or identifier (e.g., TCI status ID) of TCI status 5. 1,1 ) and the TCI status index, indicator, and / or identifier (e.g., TCI status ID) of TCI status 8. 1,2 For example, TCI state indexes, indicators, and / or identifiers (e.g., TCI state IDs) based on TCI state 5. 1,1 The TCI state index, indicator, and / or identifier (e.g., TCI state ID) appear, are in, and / or are located in the activation command compared to TCI state 8. 1,2 In the lower octets, TCI state 5 can be the first TCI state, and TCI state 8 can be the second TCI state. The octet 4 of the activation command can, for example, include the TCI state index, indicator, and / or identifier (e.g., TCI state ID) of TCI state 5. 1,1 The octet 5 of the activation command may include the TCI status index, indicator, and / or identifier (e.g., TCI status ID) of TCI status 8. 1,2 ).

[0339] The activation command may include the TCI status index, indicator, and / or identifier (e.g., TCI status ID) of TCI status 8. 1,1 ) and the TCI status index, indicator, and / or identifier (e.g., TCI status ID) of TCI status 5. 1,2 For example, TCI state indexes, indicators, and / or identifiers (e.g., TCI state IDs) based on TCI state 8. 1,1 The TCI state index, indicator, and / or identifier (e.g., TCI state ID) appear, are in, and / or are located in the activation command compared to TCI state 5. 1,2 In the lower octets, TCI state 8 can be the first TCI state, and TCI state 5 can be the second TCI state. The octet 4 of the activation command can, for example, include the TCI state index, indicator, and / or identifier (e.g., TCI state ID) of TCI state 8. 1,1 The octet 5 of the activation command may include the TCI state index, indicator, and / or identifier (e.g., TCI state ID) of TCI state 5. 1,2 ).

[0340] The 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 may be mapped to the third TCI code point (e.g., TCI code point 010).

[0341] The activation command may include the TCI status index, indicator, and / or identifier (e.g., TCI status ID) of TCI status 26. 2,1 ) and the TCI status index, indicator, and / or identifier (e.g., TCI status ID) of TCI status 61. 2,2 For example, TCI state indexes, indicators, and / or identifiers (e.g., TCI state IDs) based on TCI state 26. 2,1 The TCI state index, indicator, and / or identifier (e.g., TCI state ID) appear, are in, and / or are located in the activation command compared to TCI state 61. 2,2 In the lower octets, TCI state 26 can be the first TCI state, and TCI state 61 can be the second TCI state. The octet 6 of the activation command can, for example, include the TCI state index, indicator, and / or identifier (e.g., TCI state ID) of TCI state 26. 2,1 The octet 7 of the activation command may include the TCI status index, indicator, and / or identifier (e.g., TCI status ID) of the TCI status 61. 2,2 ).

[0342] The activation command may include the TCI status index, indicator, and / or identifier (e.g., TCI status ID) of TCI status 61. 2,1 ) and the TCI status index, indicator, and / or identifier (e.g., TCI status ID) of TCI status 26. 2,2 For example, TCI state indexes, indicators, and / or identifiers (e.g., TCI state IDs) based on TCI state 61. 2,1 The TCI state index, indicator, and / or identifier (e.g., TCI state ID) appear, are in, and / or are located in the activation command compared to TCI state 26. 2,2 In the lower octets, TCI state 61 can be the first TCI state, and TCI state 26 can be the second TCI state. The octet 6 of the activation command can, for example, include the TCI state index, indicator, and / or identifier (e.g., TCI state ID) of TCI state 61. 2,1 The octet 7 of the activation command may include the TCI state index, indicator, and / or identifier (e.g., TCI state ID) of TCI state 26. 2,2 ).

[0343] The fourth field among multiple fields, 1920a-1920e (e.g., R), can be a reserved bit. Reserved bits can be set to, for example, zero.

[0344] Wireless devices can receive control commands (e.g., as described in this article) Figure 18 The first control command described in the document at time T1. The control command can be, for example, MAC-CE. The control command can be, for example, DCI (e.g., DCI format 1_1, DCI format 1_2). The control command can be, for example, a downlink control command (e.g., an activation command). The control command can indicate at least two TCI states in a subset of TCI states.

[0345] The number of one or more TCI code points can be equal to one (e.g., a single TCI code point). A single TCI code point can indicate at least two TCI states. A control command indicating at least two TCI states can be an activation command that activates a subset of TCI states based on the fact that the number of one or more TCI code points is equal to one. At least two TCI states can be based on a subset of TCI states where the number of one or more TCI code points is equal to one. An activation command can indicate at least two TCI states based on the fact that the number of one or more TCI code points is equal to one.

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

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

[0348] Wireless devices can receive control commands (e.g., as described in this article) Figure 18 The second control command described in this document at time T2). The control command can be, for example, a DCI (e.g., DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 1_3, etc.). Control commands (e.g., as described herein in this document) Figure 18 The second control command described in the document at time T2 can, for example, schedule downlink reception (e.g., as described herein). Figure 18 The control command can schedule downlink reception at time T4, as described herein. The control command may schedule downlink reception, for example, based on resources indicated by the control command for downlink reception. The control command may schedule downlink reception, for example, based on one or more fields (e.g., TDRA field, MCS field, FDRA field, BWP index, HARQ procedure index, etc.) used by the radio device for downlink reception. The control command (e.g., as described herein) Figure 18 The second control command described in the document at time T2 can, for example, activate downlink reception in the SPS configuration.

[0349] One or more configuration parameters may include one or more SPS configuration parameters for a semi-persistent scheduling (SPS) configuration. Control commands may indicate the activation of the SPS configuration. Control commands may include one or more fields (e.g., RV, HARQ process, MCS, etc.) set to predefined values ​​(e.g., 0, 1) indicating the activation of the SPS configuration. The wireless device may acknowledge the control command based on one or more fields (e.g., RV, HARQ process, MCS, etc.) being set to predefined values. The wireless device may activate the SPS configuration based on acknowledging the control command.

[0350] 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 used for downlink reception. The cell's downlink BWP may include resources.

[0351] Downlink reception may include, for example, aperiodic CSI-RS. Control commands may trigger reception of aperiodic CSI-RS via aperiodic CSI-RS resources. Control commands may include a CSI request field that triggers aperiodic CSI reporting, which includes radio link quality (e.g., RSRP, SINR, SNR) of the aperiodic CSI-RS.

[0352] One or more configuration parameters may indicate one or more aperiodic trigger states (e.g., indicated by the higher-level parameter CSI-AperiodicTriggerStateList). The code point of the CSI request field in a control command may be associated with, or indicate, an aperiodic trigger state among one or more aperiodic trigger states. An aperiodic trigger state may include one or more reporting configurations (e.g., provided by the higher-level parameters associatedReportConfigInfoList, NZP-CSI-RS-ResourceSet list). The wireless device may perform aperiodic CSI-RS measurements via aperiodic CSI-RS resources and, based on receiving a control command with a CSI request field indicating an aperiodic trigger state, send (e.g., transmit) an aperiodic CSI report according to one or more reporting configurations for the aperiodic trigger state.

[0353] Report configurations in one or more reporting configurations (e.g., provided by higher-level parameters CSI-AssociatedReportConfigInfo and NZP-CSI-RS-ResourceSet) can be indexed, indicated, and / or identified using report configuration indexes, indicators, and / or identifiers (e.g., provided by higher-level parameter CSI-ReportConfigId). Report configurations may include one or more aperiodic CSI-RS resources (e.g., NZP-CSI-RS resources). Aperiodic CSI-RS resources in one or more aperiodic CSI-RS resources may be associated with TCI states in multiple TCI states (e.g., provided by higher-level parameters qcl-info or applyIndicatedTCIState in IE CSI-AperiodicTriggerStateList). TCI states may provide QCL assumptions (e.g., RS, RS source, SS / PBCH block, CSI-RS) for aperiodic CSI-RS via aperiodic CSI-RS resources. TCI states can provide QCL types (e.g., QCL-TypeA, QCL-TypeD, etc.) to aperiodic CSI-RS via aperiodic CSI-RS resources. At least two TCI states can include this TCI state.

[0354] Control commands (e.g., as in this article) Figure 18 The second control command (described in the second control command at time T2) may include a TCI selection field whose value (e.g., '10') indicates that at least two TCI states will be used for downlink reception. The control command may indicate the value of the code point in the TCI selection field (e.g., '10'). A control command indicating the value of the code point in the TCI selection field (e.g., '10') may indicate that at least two TCI states (e.g., both or each of at least two TCI states) will be used for downlink reception. The control command may include the TCI selection field, for example, based on one or more configuration parameters including the higher-layer parameter tciSelection-PresentInDCI. The control command may be, for example, DCI format 1_1. The control command may be, for example, DCI format 1_2.

[0355] Control commands (e.g.) Figure 18The second control command at time T2 may not include the 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, for example, be based on one or more configuration parameters excluding the higher-layer parameter tciSelection-PresentInDCI and thus excluding the TCI selection field. A control command excluding the TCI selection field may instruct that at least two TCI states (e.g., both / each of at least two TCI states) be used for downlink reception. The TCI selection field may not be present in the control command.

[0356] Control commands can be, for example, DCI format 1_0. One or more configuration parameters may include apply-indicated-TCI-state parameters set to 'both' (e.g., applyIndicatedTCIState), indicating that at least two TCI states (e.g., both / each of at least two TCI states) are used for downlink reception scheduled and / or activated by DCI format 1_0.

[0357] The `apply-indicated-TCI-state` parameter (e.g., `applyIndicatedTCIState`) can be set to 'both', for example, based on one or more configuration parameters including the Coherent Joint Transmission (CJT) scheme parameter (e.g., `cjtSchemePDSCH`) for PDSCH reception. The `apply-indicated-TCI-state` parameter (e.g., `applyIndicatedTCIState`) can be set to 'both', for example, based on sending (e.g., transmitting) a capability message (e.g., a radio device capability message) to the base station 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`) can be set to 'both', for example, based on one or more configuration parameters including the Single Frequency Network (SFN) parameter (e.g., `sfnSchemePdsch`) for PDSCH reception.

[0358] The wireless device can receive downlink reception (e.g., as in this article) Figure 18(Time T4 as described in the text). The radio device can receive downlink reception via the cell's downlink BWP. The radio device can receive downlink reception based on one or more of at least two TCI states. The one or more TCI states can be the first TCI state of the at least two TCI states. The one or more TCI states can be the second TCI state of the at least two TCI states. The one or more TCI states can be at least two TCI states.

[0359] One or more configuration parameters can indicate at least two DTXs for the cell. The at least two DTXs for the cell can be at least two DTX configurations for the cell, or can be used interchangeably with at least two DTX configurations for the cell. The at least two DTXs for the cell can be at least two DTX operations for the cell, or can be used interchangeably with at least two DTX operations for the cell.

[0360] One or more configuration parameters may include an indication of the cell's first DTX (e.g., as described in this article). Figure 18 The first DTX (as described in the first DTX) 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.). At least two DTXs of a cell may include the cell's first DTX. The cell's first DTX may be the cell's first DTX configuration, or may be used interchangeably with the cell's first DTX configuration. The cell's first DTX may be the cell's first DTX operation, or may be used interchangeably with the cell's first DTX operation. The first DTX may be associated with a first TRP (e.g., TRP 1). One or more configuration parameters may indicate an energy-saving first DTX for the first TRP.

[0361] One or more configuration parameters may include a second DTX indicating the cell (e.g., as described in this article). Figure 18 The second DTX (as described in the second DTX) may include one or more second DTX configuration parameters (e.g., TRP-DTX-Config2, TRP2-DTX-Config, DTX-Config2, etc.). At least two DTXs of a cell may include the cell's second DTX. The cell's second DTX may be the cell's second DTX configuration, or may be interchangeable with the cell's second DTX configuration. The cell's second DTX may be the cell's second DTX operation, or may be interchangeable with the cell's second DTX operation. The second DTX may be associated with a second TRP (e.g., TRP 2). One or more configuration parameters may indicate energy-saving second DTXs for the second TRP.

[0362] A radio device may send (e.g., transmit) and / or report capability messages (e.g., radio device capability messages) indicating support for and / or capability (e.g., twoDTX capability) of 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 sending (e.g., transmit) and / or reporting a capability message indicating support for and / or capability (e.g., twoDTX capability) of two DTX configurations for a cell. A base station may send (e.g., transmit) one or more second DTX configuration parameters indicating a second DTX to the radio device, for example, based on receiving a capability message indicating support for and / or capability (e.g., twoDTX capability) of two DTX configurations for a cell. A base station may send (e.g., transmit) one or more configuration parameters indicating up to two DTXs (e.g., no DTX configuration, first DTX only, second DTX only, or both first and second DTX) to the radio device, for example, based on receiving a capability message indicating support for and / or capability (e.g., twoDTX capability) of two DTX configurations for a cell.

[0363] The radio device may not send (e.g., transmit) and / or report capability messages (e.g., radio device capability messages) indicating support and / or capability (e.g., twoDTX capability) for two DTX configurations for the cell. One or more configuration parameters may be omitted, for example, based on not sending (e.g., transmit) and / or reporting capability messages indicating support and / or capability (e.g., twoDTX capability) for two DTX configurations for the cell, without including one or more second DTX configuration parameters indicating a second DTX. The base station may, for example, not send (e.g., transmit) one or more second DTX configuration parameters indicating a second DTX to the radio device based on not receiving a capability message indicating support and / or capability (e.g., twoDTX capability) for two DTX configurations for the cell. The base station may, for example, send (e.g., transmit) one or more first DTX configuration parameters indicating a first DTX to the radio device based on not receiving a capability message indicating support and / or capability (e.g., twoDTX capability) for two DTX configurations for the cell. The base station may, for example, send (e.g., transmit) to the radio device one or more configuration parameters indicating at most one DTX (e.g., first DTX only or no DTX configuration) for the cell, based on the absence of a capability message indicating support and / or capability (e.g., twoDTXcapability) for two DTX configurations for the cell.

[0364] One or more configuration parameters can indicate at least two DRXs for a cell. The at least two DRXs for a cell can be at least two DRX configurations for the cell, or can be used interchangeably with at least two DRX configurations for the cell. The at least two DRXs for a cell can be at least two DRX operations for the cell, or can be used interchangeably with at least two DRX operations for the cell.

[0365] One or more configuration parameters may include an indication of the cell's first DRX (e.g., as described in this article). Figure 18 The first DRX (as described in the document) 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.). At least two DRXs of a cell may include the cell's first DRX. The cell's first DRX may be the cell's first DRX configuration, or may be interchangeable with the cell's first DRX configuration. The cell's first DRX may be the cell's first DRX operation, or may be interchangeable with the cell's first DRX operation. The first DRX may be associated with a first TRP (e.g., TRP 1). One or more configuration parameters may indicate an energy-saving first DRX for the first TRP.

[0366] One or more configuration parameters may include a second DRX indicating the cell (e.g., as described in this article). Figure 18 The second DRX (as described in the second DRX) may include one or more second DRX configuration parameters (e.g., TRP-DRX-Config2, TRP2-DRX-Config, DRX-Config2, etc.). At least two DRXs of a cell may include the cell's second DRX. The cell's second DRX may be the cell's second DRX configuration, or may be interchangeable with the cell's second DRX configuration. The cell's second DRX may be the cell's second DRX operation, or may be interchangeable with the cell's second DRX operation. The second DRX may be associated with a second TRP (e.g., TRP 2). One or more configuration parameters may indicate an energy-saving second DRX for the second TRP.

[0367] Wireless devices can receive control commands (e.g., as described in this article) Figure 18The third control command described in the document at time T3. The control command can be, for example, a DCI (e.g., DCI format 2_9, DCI format 2_10, etc.). The control command can indicate the activation of a DTX in at least two DTXs of the cell. The control command may include a DTX and / or a DRX (e.g., TRP DTX / DRX), the value of which (e.g., 1) indicates the activation of a DTX of the cell. The DTX and / or DRX can be associated with (or correspond to) a DTX of the cell. The radio device can activate a DTX of the cell based on the received control command.

[0368] The wireless device can respond to the first control command (e.g., as stated herein). Figure 18 The second control command is received after the second control command described in this document at time T3 (e.g., as described in this document). Figure 18 The third control command described in the document at time T3). The wireless device can be in the first control command (e.g., as described herein in the document). Figure 18 Receive the second control command (e.g., as described herein) before the second control command at time T3. Figure 18 The third control command described herein (at time T3). The wireless device can receive the second control command during the same PDCCH monitoring timing (e.g., as described herein). Figure 18 The third control command at time T3 as described in the document) and the first control command (e.g., as described herein) Figure 18 The second control command described herein (at time T3). If the activity time, duration, and / or cycle of DTX are in progress, the wireless device may receive the second control command (e.g., as described herein). Figure 18 The third control command described herein at time T3). If the device is inactive for a period, duration, and / or period of DTX, it may receive a second control command (e.g., as described herein). Figure 18 The third control command described in the document at time T3.

[0369] The value (e.g., '1') of the DTX and / or DRX bits in one or more blocks can indicate the activation of the cell's DTX. This block can be associated with a cell. One or more configuration parameters can indicate the start position of a block or the start position of a DTX for the cell. This bit can be associated with (or correspond to) the cell's DTX.

[0370] DTX can be, for example, the first DTX. DTX can be, for example, the second DTX. Cell DTX can be the cell's DTX configuration, or can be used interchangeably with the cell's DTX configuration. Cell DTX can be the cell's DTX operation, or can be used interchangeably with the cell's DTX operation.

[0371] Figure 20A and Figure 20B Examples of control commands are shown. Control commands (e.g., as described in this article) Figure 18 The third control command at time T3 described herein may include one or more blocks (e.g., Figure 20A Block 1 2005a, Block 2 2010a, Block 3 2015a... Block N-1 2020a, Block N 2025a and Figure 20B Block 1 2005b, Block 2 2010b, Block 3 2015b... Block N-1 2020b, Block N 2025b).

[0372] The size (e.g., length) of each of the one or more blocks can be one or more bits (e.g., 1 bit, 2 bits, 3 bits, 4 bits). Each block may include a corresponding DTX and / or DRX (e.g., a TRP DTX / DRX indicator field). Each bit of the DTX and / or DRX in the one or more blocks (e.g., a TRP DTX / DRX indicator field) may indicate the activation or deactivation of one of the following: a first DTX, a second DTX, a first DRX, and a second DRX. A first value (e.g., '0') of a bit in the DTX / DRX indicator field may indicate the deactivation of a DTX or DRX in the first DTX, second DTX, first DRX, and second DRX, wherein the bit corresponds to or is associated with a DTX or DRX. A second value (e.g., '1') of a bit in the DTX / DRX indicator field may indicate the activation of a DTX or DRX in the first DTX, second DTX, first DRX, and second DRX, wherein the bit corresponds to or is associated with a DTX or DRX.

[0373] If the first DTX, second DTX, first DRX, and second DRX are configured by one or more configuration parameters for cell indication and / or configuration, then one or more blocks in a block (e.g., Figure 20A The DTX / DRX indicator field in Block 1 2005a or Block 1 2005a can be, for example, 4 bits. The most significant bit (MSB) of the 4 bits in this block can correspond to the first DTX (e.g., Figure 20A DTX 1 in the block). The second MSB in the 4 bits of this block can correspond to the first DRX (e.g., Figure 20A DRX 1 in the block). The least significant bit (LSB) of the 4 bits in this block can correspond to the second DRX (e.g., Figure 20A DRX 2 in the block). The third MSB or second LSB in the 4 bits of this block can correspond to the second DTX (e.g., Figure 20A (DTX 2 in the block). This block may include a DTX / DRX indicator field (e.g., 4 bits).

[0374] The first value of the MSB of the DTX / DRX indicator field (e.g., '0') can indicate the deactivation of the first DTX. The second value of the MSB of the DTX / DRX indicator field (e.g., '1') can indicate the activation of the first DTX.

[0375] The first value (e.g., '0') of the second MSB of the DTX / DRX indicator field can indicate the deactivation of the first DRX. The second value (e.g., '1') of the second MSB of the DTX / DRX indicator field can indicate the activation of the first DRX.

[0376] The first value of the LSB of the DTX / DRX indicator field (e.g., '0') can indicate the deactivation of the second DRX. The second value of the LSB of the DTX / DRX indicator field (e.g., '1') can indicate the activation of the second DRX.

[0377] The first value (e.g., '0') of the second LSB of the DTX / DRX indicator field can indicate the deactivation of the second DTX. The second value (e.g., '1') of the second LSB of the DTX / DRX indicator field can indicate the activation of the second DTX.

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

[0379] The first value of the MSB of the DTX / DRX indicator field (e.g., '0') can indicate the deactivation of the first DTX. The second value of the MSB of the DTX / DRX indicator field (e.g., '1') can indicate the activation of the first DTX.

[0380] The first value of the LSB of the DTX / DRX indicator field (e.g., '0') can indicate the deactivation of the second DTX. The second value of the LSB of the DTX / DRX indicator field (e.g., '1') can indicate the activation of the second DTX.

[0381] For example, if the first DRX and the second DRX are configured as cell indicators and / or configured by one or more configuration parameters, then a block in one or more blocks can be 2 bits. The MSB in the 2 bits of the block can correspond to the first DRX. The LSB in the 2 bits of the block can correspond to the second DRX. The first DTX and the second DTX may not be configured as cell indicators and / or configured by one or more configuration parameters.

[0382] For example, if the first DTX and the second DRX are configured as cell indicators and / or configurable by one or more configuration parameters, then a block in one or more blocks can be 2 bits. The MSB in the 2 bits of this block can correspond to the first DTX. The LSB in the 2 bits of this block can correspond to the second DRX. The second DTX and the first DRX may not be configured as cell indicators and / or configurable by one or more configuration parameters.

[0383] For example, if two of the first DTX, second DTX, first DRX, and second DRX are configured as cell indicators and / or configured by one or more configuration parameters, then one or more blocks can be 2 bits. For example, the block may include one of {[DTX 1, DRX1], [DTX 1, DRX 2], [DTX 1, DTX 2], [DRX 1, DRX 2], [DRX 1, DTX 2], [DTX 2, DRX2]}.

[0384] For example, if the first DTX, the first DRX, and the second DRX are configured by one or more configuration parameters for cell indication and / or configuration, then one or more blocks in a block (e.g., Figure 20A The block N-1 or the DTX / DRX indicator field in block N-1 can be 3 bits. The MSB in the 3 bits of this block can correspond to the first DTX (e.g., Figure 20A DTX 1 in the block). The second MSB in the 3 bits of this block can correspond to the first DRX (e.g., Figure 20A DRX 1 in the block). The LSB in the 3 bits of this block can correspond to the second DRX (e.g., Figure 20A (DRX 2 in the context of DTX). The second DTX may not be determined by one or more configuration parameters for cell indication and / or configuration.

[0385] For example, if the first DTX, the first DRX, and the second DTX are configured by one or more configuration parameters for cell indication and / or configuration, then one or more blocks in a block (e.g., Figure 20A The block N or the DTX / DRX indicator field in block N can be 3 bits. The MSB in the 3 bits of this block can correspond to the first DTX (e.g., Figure 20A DTX 1 in the block). The second MSB in the 3 bits of this block can correspond to the first DRX (e.g., Figure 20ADRX 1 in the block). The LSB in the 3 bits of this block can correspond to the second DTX (e.g., Figure 20A (DTX 2 in the context of DTX). The second DRX may not be configured by one or more configuration parameters for cell indication and / or configuration.

[0386] For example, if three of the first DTX, second DTX, first DRX, and second DRX are configured as cell indicators and / or configured by one or more configuration parameters, then a block in one or more blocks can be 3 bits. For example, the block may include one of {[DTX 1, DRX1, DTX 2], [DTX 1, DRX 1, DRX 2], [DTX 1, DTX 2, DRX 2], [DRX 1, DTX 2, DRX 2]}.

[0387] For example, if one of the first DTX, second DTX, first DRX, and second DRX is a cell indication and / or configuration by one or more configuration parameters, then one or more blocks may be 1 bit. For example, the block may include one of {[DTX 1], [DRX 1], [DTX 2], [DRX 2]}.

[0388] The starting position of the DTX and / or DRX (or DTX / DRX indicator field) of a TRP in one or more blocks can be determined by the wireless device and / or base station via location parameters (e.g., positionInDCI-TRPDTRX). One or more configuration parameters may include location parameters. For example, a wireless device configured with both a first TRP and a second TRP (or served by both) can determine the starting position of the block via location parameters (e.g., positionInDCI-TRPDTRX). Figure 20A The starting position of DTX 1 in block 1 is indicated. The position parameter can indicate the starting position of a block. For example, a wireless device configured only with (or served by) the first TRP can be indicated by the starting position of the block (e.g., ...). Figure 20A The starting position of DTX 1 in block 1 is indicated. The position parameter can indicate the starting position of the block. The wireless device discards / ignores DTX 2 and DRX 2 associated with the second TRP in this block. For example, a wireless device configured only with (or served by) the second TRP can be indicated by the starting position of the DTX and / or DRX associated with the second TRP (or the DTX / DRX indicator field in the block). Figure 20A The location parameter indicates the starting position of DTX 2 in block 1. The location parameter can indicate the starting position of DTX and / or DRX associated with the second TRP in the block. DTX 1 and DRX 1 associated with the first TRP in the block are discarded / ignored wirelessly.

[0389] The size (e.g., length) of each of one or more blocks can be at least two bits (e.g., 2 bits, 3 bits). Each block may include a corresponding DTX / DRX indicator field (e.g., DTX / DRX indicator field) and corresponding index, indicator, and / or identifier fields (e.g., TRP index, indicator, and / or identifier, coreset 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 fields in one or more blocks can be 1 bit. The corresponding index, indicator, and / or identifier fields in each of one or more blocks can be 1 bit.

[0390] For example, if the values ​​of the block index, indicator, and / or identifier fields in one or more blocks are equal to and / or set to a first value (e.g., 0), then each bit of the DTX / DRX indicator field (e.g., the DTX / DRX indicator field) in the block can indicate the activation or deactivation of one of the following: a first DTX and a first DRX. A first value (e.g., '0') of a bit in the DTX / DRX indicator field in the block can indicate the deactivation of the first DTX or the first DRX, where the bit corresponds to or is associated with the first DTX or the first DRX, respectively. A second value (e.g., '1') of a bit in the DTX / DRX indicator field in the block can indicate the activation of the first DTX and the first DRX, where the bit corresponds to or is associated with the first DTX or the first DRX, respectively.

[0391] For example, if the values ​​of the index, indicator, and / or identifier fields in one or more blocks are equal to and / or set to a second value (e.g., 1), then each bit of the DTX / DRX indicator field (e.g., the DTX / DRX indicator field) in the block can indicate the activation or deactivation of one of the following: a second DTX and a second DRX. A first value (e.g., '0') of a bit in the DTX / DRX indicator field can indicate the deactivation of the second DTX or the second DRX, where the bit corresponds to or is associated with the second DTX or the second DRX, respectively. A second value (e.g., '1') of a bit in the DTX / DRX indicator field can indicate the activation of the second DTX and the second DRX, where the bit corresponds to or is associated with the second DTX or the second DRX, respectively.

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

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

[0394] The first value of the MSB of the DTX / DRX indicator field (e.g., '0') can indicate the deactivation of the first DTX. The second value of the MSB of the DTX / DRX indicator field (e.g., '1') can indicate the activation of the first DTX.

[0395] The first value (e.g., '0') of the second MSB of the DTX / DRX indicator field can indicate the deactivation of the first DRX. The second value (e.g., '1') of the second MSB of the DTX / DRX indicator field can indicate the activation of the first DRX.

[0396] For example, if the second DTX and the second DRX are configured by one or more configuration parameters for cell indication and / or configuration, and if one or more blocks are in block 2015b (e.g., Figure 20B If the index, indicator, and / or identifier field 2050f in block 3) is equal to and / or set to the second value (e.g., 1...

Claims

1. A method comprising: One or more messages are received by a wireless device, the one or more messages including: Indicates the repetition scheme parameters for the time-domain or frequency-domain scheme; and Downlink or Joint Transport Configuration Indicator (TCI) status list parameter, indicating the TCI status list used for both uplink transmission and downlink reception; Receive downlink control information (DCI) configured to be received via the Physical Downlink Shared Channel (PDSCH); and Based on the TCI selection field indication in the DCI, two TCI states are applied to the PDSCH reception, and the two TCI states are used to receive the PDSCH reception in non-overlapping resources indicated by the repetition scheme parameters.

2. The method of claim 1, wherein the DCI further includes a time-domain resource assignment field indicating the number of repetitions, and wherein using the two TCI states to receive the PDSCH reception includes: Based on the TCI selection field in the DCI indicating that two TCI states are applied to the PDSCH reception or that the TCI selection field does not exist in the DCI, the two TCI states are used to receive the PDSCH reception in consecutive time slots, wherein the number of consecutive time slots is equal to the number of repetitions.

3. The method as described in any one of claims 1 to 2, further comprising: The second DCI is configured to be received by scheduling the second PDSCH reception; as well as Based on the TCI selection field indication in the second DCI, two TCI states are applied to the second PDSCH reception, and the following items are used to receive the second PDSCH reception: The first demodulation reference signal (DM-RS) port associated with the first TCI state of the two TCI states; and The second DM-RS port associated with the second TCI state of the two TCI states.

4. The method according to any one of claims 1 to 2, further comprising: The second DCI is configured to be received by scheduling the second PDSCH reception; as well as Based on the fact that the second DCI is not configured with a TCI selection field, the two TCI states are used to receive the second PDSCH in non-overlapping resources indicated by the repetition parameter.

5. The method according to any one of claims 1 to 4, wherein: The repetition scheme parameters are set to the time-domain scheme; and Based on the repetition scheme parameters being set to the time-domain scheme, receiving the PDSCH using the two TCI states in non-overlapping resources includes receiving the PDSCH using the two TCI states in non-overlapping time-domain resources.

6. The method according to any one of claims 1 to 4, wherein: The repetition scheme parameters are set to the frequency domain scheme; and Based on the repetition scheme parameters being set to the frequency domain scheme, receiving the PDSCH using the two TCI states in non-overlapping resources includes receiving the PDSCH using the two TCI states in non-overlapping frequency domain resources.

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

8. The method of any one of claims 1 to 7, further comprising, after receiving the one or more messages and before receiving the DCI configured to schedule the reception of the PDSCH: The wireless device receives a Media Access Control (MAC) control element (CE) configured to activate one or more TCI states in the TCI state list; and Receive the DCI indicating the states of the two TCIs.

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

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

11. The method of any one of claims 1 to 10, wherein using the two TCI states to receive the PDSCH reception comprises: The first TCI state of the two TCI states is used in the first time-domain resource of the non-overlapping time-domain resource or in the first frequency-domain resource of the non-overlapping time-frequency resource; and The second TCI state of the two TCI states is used in the second time-domain resource of the non-overlapping time-domain resource or in the second frequency-domain resource of the non-overlapping time-frequency resource.

12. The method according to any one of claims 1 to 11, further comprising: Receive one or more second messages, the one or more second messages including second repetition scheme parameters indicating a second time-domain scheme or a second frequency-domain scheme; Receive scheduling or activation of a fourth DCI received via the second PDSCH of the cell, wherein the fourth DCI includes: The second antenna port field indicates one or more second DM-RS ports within a CDM group; and The TCI field indicating the second two TCI states received by the second PDSCH; Based on the fourth DCI indicating one or more DM-RS ports within a CDM group and the second two TCI states for the second PDSCH reception, the second two TCI states are used to receive the second PDSCH reception in the following: Non-overlapping time-domain resources, if the second repetition scheme parameter is set to the second time-domain scheme; and Non-overlapping frequency domain resources, if the second repetition scheme parameter is set to the second frequency domain scheme.

13. A wireless device, comprising: One or more processors; and A memory that stores instructions that, when executed by the one or more processors, cause the wireless device to perform the method as described in any one of claims 1 to 12.

14. A system comprising: A wireless device configured to perform the method as described in any one of claims 1 to 12; and A base station configured to transmit the DCI that is configured to schedule the PDSCH to receive.

15. A computer-readable medium storing instructions that, when executed, cause the method of any one of claims 1 to 12 to be performed.

Images