Patent Application
20250097838
A wireless device communicates with a base station. The wireless device receives configuration parameters for communicating via a cell. A transmission configuration indicator state parameter is used to indicate resources for a transmission.
The following summary presents a simplified summary of certain features. The summary is not an extensive overview and is not intended to identify key or critical elements.
A wireless device may receive one or more parameters from a base station to configure wireless communications. A configuration parameter may indicate a value associated with using at least two resources (e.g., transmission configuration indicator states) for reception (e.g., a physical downlink shared channel reception). Also, if the wireless device is configured with a unified transmission configuration state framework and is configured to apply multiple resources to a reception, for example, based on a transmission configuration indicator selection field in a message scheduling the reception and/or based on an absence of such a field, the wireless device may receive repetitions on the reception using a frequency division scheme and/or a time division scheme (e.g., using non-overlapping resources and/or consecutive time slots). Additionally or alternatively, if the wireless device is configured with the unified transmission configuration state framework, and if demodulation reference signal ports are indicated, the wireless device may multiplex the reception using the indicated ports. If the base station switches off a transmission and reception point, and the wireless device is not capable of dynamically switching between resources (e.g., unified transmission configuration indicator states) or switching to a single transmission configuration state, the wireless device may stop receptions or, alternatively, continue receiving receptions using prior configured resources (e.g., unified transmission configuration indicator states).
These and other features and advantages are described in greater detail below.
Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.
The accompanying drawings and descriptions provide examples. It is to be understood that the examples shown in the drawings and/or described are non-exclusive, and that features shown and described may be practiced in other examples. Examples are provided for operation of wireless communication systems.
The wireless device 106 may communicate with the RAN 104 via radio communications over an air interface. The RAN 104 may communicate with the CN 102 via various communications (e.g., wired communications and/or wireless communications). The wireless device 106 may establish a connection with the CN 102 via the RAN 104. The RAN 104 may provide/configure scheduling, radio resource management, and/or retransmission protocols, for example, as part of the radio communications. The communication direction from the RAN 104 to the wireless device 106 over/via the air interface may be referred to as the downlink and/or downlink communication direction. The communication direction from the wireless device 106 to the RAN 104 over/via the air interface may be referred to as the uplink and/or uplink communication direction. Downlink transmissions may be separated and/or distinguished from uplink transmissions, for example, based on at least one of: frequency division duplexing (FDD), time-division duplexing (TDD), any other duplexing schemes, and/or one or more combinations thereof.
As used throughout, the term “wireless device” may comprise one or more of: a mobile device, a fixed (e.g., non-mobile) device for which wireless communication is configured or usable, a computing device, a node, a device capable of wirelessly communicating, or any other device capable of sending and/or receiving signals. As non-limiting examples, a wireless device may comprise, for example: a telephone, a cellular phone, a Wi-Fi phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a hotspot, a cellular repeater, a vehicle road side unit (RSU), a relay node, an automobile, a wireless user device (e.g., user equipment (UE), a user terminal (UT), etc.), an access terminal (AT), a mobile station, a handset, a wireless transmit and receive unit (WTRU), a wireless communication device, and/or any combination thereof.
The RAN 104 may comprise one or more base stations (not shown). As used throughout, the term “base station” may comprise one or more of: a base station, a node, a Node B (NB), an evolved NodeB (eNB), a gNB, an ng-eNB, a relay node (e.g., an integrated access and backhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an access point (e.g., a Wi-Fi access point), a transmission and reception point (TRP), a computing device, a device capable of wirelessly communicating, or any other device capable of sending and/or receiving signals. A base station may comprise one or more of each element listed above. For example, a base station may comprise one or more TRPs. As other non-limiting examples, a base station may comprise for example, one or more of: 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 head (RRH), a baseband processing unit coupled to one or more remote radio heads (RRHs), a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB) (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 base station, and/or any combination thereof. A base station may comprise 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)).
A base station (e.g., in the RAN 104) may comprise one or more sets of antennas for communicating with the wireless device 106 wirelessly (e.g., via an over the air interface). One or more base stations may comprise sets (e.g., three sets or any other quantity of sets) of antennas to respectively control multiple cells or sectors (e.g., three cells, three sectors, any other quantity of cells, or any other quantity of sectors). The size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) may successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. One or more cells of base stations (e.g., by alone or in combination with other cells) may provide/configure a radio coverage to the wireless device 106 over a wide geographic area to support wireless device mobility. A base station comprising three sectors (e.g., or n-sector, where n refers to any quantity 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).
One or more base stations (e.g., in the RAN 104) may be implemented as a sectored site with more or less than three sectors. One or more base stations of the RAN 104 may be implemented as an access point, as a baseband processing device/unit coupled to several RRHs, and/or as a repeater or relay node used to extend the coverage area of a node (e.g., a donor node). A baseband processing device/unit coupled to RRHs may be part of a centralized or cloud RAN architecture, for example, where the baseband processing device/unit may be centralized in a pool of baseband processing devices/units or virtualized. A repeater node may amplify and send (e.g., transmit, retransmit, rebroadcast, etc.) a radio signal received from a donor node. A relay node may perform the substantially the same/similar functions as a repeater node. The relay node may decode the radio signal received from the donor node, for example, to remove noise before amplifying and sending the radio signal.
The RAN 104 may be deployed as a homogenous network of base stations (e.g., macrocell base stations) that have similar antenna patterns and/or similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network of base stations (e.g., different base stations that have different antenna patterns). In heterogeneous networks, small cell base stations may be used to provide/configure small coverage areas, for example, coverage areas that overlap with comparatively larger coverage areas provided/configured by other base stations (e.g., macrocell base stations). The small coverage areas may be provided/configured in areas with high data traffic (or so-called “hotspots”) or in areas with a weak macrocell coverage. Examples of small cell base stations may comprise, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.
Examples described herein may be used in a variety of types of communications. For example, communications may be in accordance with the Third-Generation Partnership Project (3GPP) (e.g., one or more network elements similar to those of the communication network 100), communications in accordance with Institute of Electrical and Electronics Engineers (IEEE), communications in accordance with International Telecommunication Union (ITU), communications in accordance with International Organization for Standardization (ISO), etc. The 3GPP has produced specifications for multiple generations of mobile networks: a 3G network known as UMTS, a 4G network known as Long-Term Evolution (LTE) and LTE Advanced (LTE-A), and a 5G network known as 5G System (5GS) and NR system. 3GPP may produce specifications for additional generations of communication networks (e.g., 6G and/or any other generation of communication network). Examples may be described with reference to one or more elements (e.g., the RAN) of a 3GPP 5G network, referred to as a next-generation RAN (NG-RAN), or any other communication network, such as a 3GPP network and/or a non-3GPP network. Examples described herein may be applicable to other communication networks, such as 3G and/or 4G networks, and communication networks that may not yet be finalized/specified (e.g., a 3GPP 6G network), satellite communication networks, and/or any other communication network. NG-RAN implements and updates 5G radio access technology referred to as NR and may be provisioned to implement 4G radio access technology and/or other radio access technologies, such as other 3GPP and/or non-3GPP radio access technologies.
The CN 152 (e.g., 5G-CN) may provide/configure the wireless device(s) 156 with one or more interfaces to one or more DNs 170, such as public DNs (e.g., the Internet), private DNs, and/or intra-operator DNs. As part of the interface functionality, the CN 152 (e.g., 5G-CN) may set up end-to-end connections between the wireless device(s) 156 and the one or more DNs, authenticate the wireless device(s) 156, and/or provide/configure charging functionality. The CN 152 (e.g., the 5G-CN) may be a service-based architecture, which may differ from other CNs (e.g., such as a 3GPP 4G CN). The architecture of nodes of the CN 152 (e.g., 5G-CN) may be defined as network functions that offer services via interfaces to other network functions. The network functions of the CN 152 (e.g., 5G CN) may be implemented in several ways, for example, as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, and/or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).
The CN 152 (e.g., 5G-CN) may comprise an Access and Mobility Management Function (AMF) device 158A and/or a User Plane Function (UPF) device 158B, which may be separate components or one component AMF/UPF device 158. The UPF device 158B may serve as a gateway between a RAN 154 (e.g., NG-RAN) and the one or more DNs 170. The 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 to support routing of traffic flows to the one or more DNs 170, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink/downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and/or downlink data notification triggering. The 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 of interconnect to the one or more DNs, and/or a branching point to support a multi-homed PDU session. The wireless device(s) 156 may be configured to receive services via a PDU session, which may be a logical connection between a wireless device and a DN.
The AMF device 158A may perform functions, such as: Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between access networks (e.g., 3GPP access networks and/or non-3GPP networks), idle mode wireless device reachability (e.g., idle mode UE reachability for control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (e.g., subscription and policies), network slicing support, and/or session management function (SMF) selection. NAS may refer to the functionality operating between a CN and a wireless device, and AS may refer to the functionality operating between a wireless device and a RAN.
The CN 152 (e.g., 5G-CN) may comprise one or more additional network functions that may not be shown in
The RAN 154 (e.g., NG-RAN) may communicate with the wireless device(s) 156 via radio communications (e.g., an over the air interface). The wireless device(s) 156 may communicate with the CN 152 via the RAN 154. The RAN 154 (e.g., NG-RAN) may comprise one or more first-type base stations (e.g., gNBs comprising a gNB 160A and a gNB 160B (collectively gNBs 160)) and/or one or more second-type base stations (e.g., ng eNBs comprising an ng-eNB 162A and an ng-eNB 162B (collectively ng eNBs 162)). The RAN 154 may comprise one or more of any quantity of types of base station. The gNBs 160 and ng eNBs 162 may be referred to as base stations. The base stations (e.g., the gNBs 160 and ng eNBs 162) may comprise one or more sets of antennas for communicating with the wireless device(s) 156 wirelessly (e.g., an over an air interface). One or more base stations (e.g., the gNBs 160 and/or the ng eNBs 162) may comprise multiple sets of antennas to respectively control multiple cells (or sectors). The cells of the base stations (e.g., the gNBs 160 and the ng-eNBs 162) may provide a radio coverage to the wireless device(s) 156 over a wide geographic area to support wireless device mobility.
The base stations (e.g., the gNBs 160 and/or the ng-eNBs 162) may be connected to the CN 152 (e.g., 5G CN) via a first interface (e.g., an NG interface) and to other base stations via a second interface (e.g., an Xn interface). The NG and Xn interfaces may be established using direct physical connections and/or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The base stations (e.g., the gNBs 160 and/or the ng-eNBs 162) may communicate with the wireless device(s) 156 via a third interface (e.g., a Uu interface). A base station (e.g., the gNB 160A) may communicate with the wireless device 156A via a Uu interface. The NG, Xn, and Uu interfaces may be associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements shown in
One or more base stations (e.g., the gNBs 160 and/or the ng-eNBs 162) may communicate with one or more AMF/UPF devices, such as the AMF/UPF 158, via one or more interfaces (e.g., NG interfaces). A base station (e.g., the gNB 160A) may be in communication with, and/or connected to, the UPF 158B of the AMF/UPF 158 via an NG-User plane (NG-U) interface. The NG-U interface may provide/perform delivery (e.g., non-guaranteed delivery) of user plane PDUs between a base station (e.g., the gNB 160A) and a UPF device (e.g., the UPF 158B). The base station (e.g., the gNB 160A) may be in communication with, and/or connected to, an AMF device (e.g., the AMF 158A) via an NG-Control plane (NG-C) interface. The NG-C interface may provide/perform, for example, NG interface management, wireless device context management (e.g., UE context management), wireless device mobility management (e.g., UE mobility management), transport of NAS messages, paging, PDU session management, configuration transfer, and/or warning message transmission.
A wireless device may access the base station, via an interface (e.g., Uu interface), for the user plane configuration and the control plane configuration. The base stations (e.g., gNBs 160) may provide user plane and control plane protocol terminations towards the wireless device(s) 156 via the Uu interface. A base station (e.g., the gNB 160A) may provide user plane and control plane protocol terminations toward the wireless device 156A over a Uu interface associated with a first protocol stack. A base station (e.g., the ng-eNBs 162) may provide Evolved UMTS Terrestrial Radio Access (E UTRA) user plane and control plane protocol terminations towards the wireless device(s) 156 via a Uu interface (e.g., where E UTRA may refer to the 3GPP 4G radio-access technology). A base station (e.g., the ng-eNB 162B) may provide E UTRA user plane and control plane protocol terminations towards the wireless device 156B via a Uu interface associated with a second protocol stack. The user plane and control plane protocol terminations may comprise, for example, NR user plane and control plane protocol terminations, 4G user plane and control plane protocol terminations, etc.
The CN 152 (e.g., 5G-CN) may be configured to handle one or more radio accesses (e.g., NR, 4G, and/or any other radio accesses). It may also be possible for an NR network/device (or any first network/device) to connect to a 4G core network/device (or any second network/device) in a non-standalone mode (e.g., non-standalone operation). In a non-standalone mode/operation, a 4G core network may be used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and/or paging). Although only one AMF/UPF 158 is shown in
An interface (e.g., Uu, Xn, and/or NG interfaces) between network elements (e.g., the network elements shown in
The communication network 100 in
A user plane configuration (e.g., an NR user plane protocol stack) may comprise multiple layers (e.g., five layers or any other quantity of layers) implemented in the wireless device 210 and the base station 220 (e.g., as shown in
PDCPs (e.g., the PDCPs 214 and 224 shown in
The PDCP layers (e.g., PDCPs 214 and 224) may perform mapping/de-mapping between a split radio bearer and RLC channels (e.g., RLC channels 330) (e.g., in a dual connectivity scenario/configuration). Dual connectivity may refer to a technique that allows a wireless device to communicate with multiple cells (e.g., two cells) or, more generally, multiple cell groups comprising: a master cell group (MCG) and a secondary cell group (SCG). A split bearer may be configured and/or used, for example, if a single radio bearer (e.g., such as one of the radio bearers provided/configured by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225) is handled by cell groups in dual connectivity. The PDCPs 214 and 224 may map/de-map between the split radio bearer and RLC channels 330 belonging to the cell groups.
RLC layers (e.g., RLCs 213 and 223) may perform segmentation, retransmission via Automatic Repeat Request (ARQ), and/or removal of duplicate data units received from MAC layers (e.g., MACs 212 and 222, respectively). The RLC layers (e.g., RLCs 213 and 223) may support multiple transmission modes (e.g., three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM)). The RLC layers may perform one or more of the noted functions, for example, based on the transmission mode an RLC layer is operating. The RLC configuration may be per logical channel. The RLC configuration may not depend on numerologies and/or Transmission Time Interval (TTI) durations (or other durations). The RLC layers (e.g., RLCs 213 and 223) may provide/configure RLC channels as a service to the PDCP layers (e.g., PDCPs 214 and 224, respectively), such as shown in
The MAC layers (e.g., MACs 212 and 222) may perform multiplexing/demultiplexing of logical channels and/or mapping between logical channels and transport channels. The multiplexing/demultiplexing may comprise multiplexing/demultiplexing of data units/data portions, belonging to the one or more logical channels, into/from Transport Blocks (TBs) delivered to/from the PHY layers (e.g., PHYs 211 and 221, respectively). The MAC layer of a base station (e.g., MAC 222) may be configured to perform scheduling, scheduling information reporting, and/or priority handling between wireless devices via dynamic scheduling. Scheduling may be performed by a base station (e.g., the base station 220 at the MAC 222) for downlink/or and uplink. The MAC layers (e.g., MACs 212 and 222) may be configured to perform error correction(s) via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the wireless device 210 via logical channel prioritization and/or padding. The MAC layers (e.g., MACs 212 and 222) may support one or more numerologies and/or transmission timings. Mapping restrictions in a logical channel prioritization may control which numerology and/or transmission timing a logical channel may use. The MAC layers (e.g., the MACs 212 and 222) may provide/configure logical channels 340 as a service to the RLC layers (e.g., the RLCs 213 and 223).
The PHY layers (e.g., PHYs 211 and 221) may perform mapping of transport channels to physical channels and/or digital and analog signal processing functions, for example, for sending and/or receiving information (e.g., via an over the air interface). The digital and/or analog signal processing functions may comprise, for example, coding/decoding and/or modulation/demodulation. The PHY layers (e.g., PHYs 211 and 221) may perform multi-antenna mapping. The PHY layers (e.g., the PHYs 211 and 221) may provide/configure one or more transport channels (e.g., transport channels 350) as a service to the MAC layers (e.g., the MACs 212 and 222, respectively).
The downlink data flow may begin, for example, if the SDAP 225 receives the three IP packets (or other quantity of IP packets) from one or more QoS flows and maps the three packets (or other quantity of packets) to radio bearers (e.g., radio bearers 402 and 404). The SDAP 225 may map the IP packets n and n+1 to a first radio bearer 402 and map the IP packet m to a second radio bearer 404. An SDAP header (labeled with “H” preceding each SDAP SDU shown in
Each protocol layer (e.g., protocol layers shown in
One or more MAC control elements (CEs) may be added to, or inserted into, the MAC PDU by a MAC layer, such as MAC 223 or MAC 222. As shown in
A logical channel may be defined by the type of information it carries. The set of logical channels (e.g., in an NR configuration) may comprise one or more channels described below. A paging control channel (PCCH) may comprise/carry one or more paging messages used to page a wireless device whose location is not known to the network on a cell level. A broadcast control channel (BCCH) may comprise/carry system information messages in the form of a master information block (MIB) and several system information blocks (SIBs). The system information messages may be used by wireless devices to obtain information about how a cell is configured and how to operate within the cell. A common control channel (CCCH) may comprise/carry control messages together with random access. A dedicated control channel (DCCH) may comprise/carry control messages to/from a specific wireless device to configure the wireless device with configuration information. A dedicated traffic channel (DTCH) may comprise/carry user data to/from a specific wireless device.
Transport channels may be used between the MAC and PHY layers. Transport channels may be defined by how the information they carry is sent/transmitted (e.g., via an over the air interface). The set of transport channels (e.g., that may be defined by an NR configuration or any other configuration) may comprise one or more of the following channels. A paging channel (PCH) may comprise/carry paging messages that originated from the PCCH. A broadcast channel (BCH) may comprise/carry the MIB from the BCCH. A downlink shared channel (DL-SCH) may comprise/carry downlink data and signaling messages, including the SIBs from the BCCH. An uplink shared channel (UL-SCH) may comprise/carry uplink data and signaling messages. A random access channel (RACH) may provide a wireless device with an access to the network without any prior scheduling.
The PHY layer may use physical channels to pass/transfer information between processing levels of the PHY layer. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY layer may generate control information to support the low-level operation of the PHY layer. The PHY layer may provide/transfer the control information to the lower levels of the PHY layer via physical control channels (e.g., referred to as L1/L2 control channels). The set of physical channels and physical control channels (e.g., that may be defined by an NR configuration or any other configuration) may comprise one or more of the following channels. A physical broadcast channel (PBCH) may comprise/carry the MIB from the BCH. A physical downlink shared channel (PDSCH) may comprise/carry downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH. A physical downlink control channel (PDCCH) may comprise/carry downlink control information (DCI), which may comprise downlink scheduling commands, uplink scheduling grants, and uplink power control commands. A physical uplink shared channel (PUSCH) may comprise/carry uplink data and signaling messages from the UL-SCH and in some instances uplink control information (UCI) as described below. A physical uplink control channel (PUCCH) may comprise/carry UCI, which may comprise HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR). A physical random access channel (PRACH) may be used for random access.
The physical layer may generate physical signals to support the low-level operation of the physical layer, which may be similar to the physical control channels. As shown in
One or more of the channels (e.g., logical channels, transport channels, physical channels, etc.) may be used to carry out functions associated with the control plan protocol stack (e.g., NR control plane protocol stack).
The NAS protocols 217 and 237 may provide control plane functionality between the wireless device 210 and the AMF 230 (e.g., the AMF 158A or any other AMF) and/or, more generally, between the wireless device 210 and a CN (e.g., the CN 152 or any other CN). The NAS protocols 217 and 237 may provide control plane functionality between the wireless device 210 and the AMF 230 via signaling messages, referred to as NAS messages. There may be no direct path between the wireless device 210 and the AMF 230 via which the NAS messages may be transported. The NAS messages may be transported using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functionality, such as authentication, security, a connection setup, mobility management, session management, and/or any other functionality.
The RRCs 216 and 226 may provide/configure control plane functionality between the wireless device 210 and the base station 220 and/or, more generally, between the wireless device 210 and the RAN (e.g., the base station 220). The RRC layers 216 and 226 may provide/configure control plane functionality between the wireless device 210 and the base station 220 via signaling messages, which may be referred to as RRC messages. The RRC messages may be sent/transmitted between the wireless device 210 and the RAN (e.g., the base station 220) using signaling radio bearers and the same/similar PDCP, RLC, MAC, and PHY protocol layers. The MAC layer may multiplex control-plane and user-plane data into the same TB. The RRC layers 216 and 226 may provide/configure control plane functionality, such as one or more of the following functionalities: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the wireless device 210 and the RAN (e.g., the 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; wireless device measurement reporting (e.g., the wireless device measurement reporting) and control of the reporting; detection of and recovery from radio link failure (RLF); and/or NAS message transfer. As part of establishing an RRC connection, RRC layers 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the wireless device 210 and the RAN (e.g., the base station 220).
An RRC connection may be established for the wireless device. For example, this may be during an RRC connected state. During the RRC connected state (e.g., during the RRC connected 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 be similar to one of the one or more base stations (e.g., one or more base stations of the RAN 104 shown in
An RRC context may not be established for the wireless device. For example, this may be during the RRC idle state. During the RRC idle state (e.g., the RRC idle 606), an RRC context may not be established for the wireless device. During the RRC idle state (e.g., the RRC idle 606), the wireless device may not have an RRC connection with the base station. During the RRC idle state (e.g., the RRC idle 606), the wireless device may be in a sleep state for the majority of the time (e.g., to conserve battery power). The wireless device may wake up periodically (e.g., once in every discontinuous reception (DRX) cycle) to monitor for paging messages (e.g., paging messages set from the RAN). Mobility of the wireless device may be managed by the wireless device via a procedure of a cell reselection. The RRC state may transition from the RRC idle state (e.g., the RRC idle 606) to the RRC connected state (e.g., the RRC connected 602) via a connection establishment procedure 612, which may involve a random access procedure.
A previously established RRC context may be maintained for the wireless device. For example, this may be during the RRC inactive state. During the RRC inactive state (e.g., the RRC inactive 604), the RRC context previously established may be maintained in the wireless device and the base station. The maintenance of the RRC context may enable/allow a fast transition to the RRC connected state (e.g., the RRC connected 602) with reduced signaling overhead as compared to the transition from the RRC idle state (e.g., the RRC idle 606) to the RRC connected state (e.g., the RRC connected 602). During the RRC inactive state (e.g., the RRC inactive 604), the wireless device may be in a sleep state and mobility of the wireless device may be managed/controlled by the wireless device via a cell reselection. The RRC state may transition from the RRC inactive state (e.g., the RRC inactive 604) to the RRC connected state (e.g., the RRC connected 602) via a connection resume procedure 614. The RRC state may transition from the RRC inactive state (e.g., the RRC inactive 604) to the RRC idle state (e.g., the RRC idle 606) via a connection release procedure 616 that may be the same as or similar to connection release procedure 608.
An RRC state may be associated with a mobility management mechanism. During the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., the RRC inactive 604), mobility may be managed/controlled by the wireless device via a cell reselection. The purpose of mobility management during the RRC idle state (e.g., the RRC idle 606) or during the RRC inactive state (e.g., the RRC inactive 604) may be to enable/allow the network to be able to notify the wireless device of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used during the RRC idle state (e.g., the RRC idle 606) or during the RRC idle state (e.g., the RRC inactive 604) may enable/allow the network to track the wireless device on a cell-group level, for example, so that the paging message may be broadcast over the cells of the cell group that the wireless device currently resides within (e.g. instead of sending the paging message over the entire mobile communication network). The mobility management mechanisms for the RRC idle state (e.g., the RRC idle 606) and the RRC inactive state (e.g., the RRC inactive 604) may track the wireless device on a cell-group level. The mobility management mechanisms may do the tracking, for example, using different granularities of grouping. There may be a plurality of levels of cell-grouping granularity (e.g., three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI)).
Tracking areas may be used to track the wireless device (e.g., tracking the location of the wireless device at the CN level). The CN (e.g., the CN 102, the 5G CN 152, or any other CN) may send to the wireless device a list of TAIs associated with a wireless device registration area (e.g., a UE registration area). A wireless device may perform a registration update with the CN to allow the CN to update the location of the wireless device and provide the wireless device with a new the UE registration area, for example, if the wireless device moves (e.g., via a 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.
RAN areas may be used to track the wireless device (e.g., the location of the wireless device at the RAN level). For a wireless device in an RRC inactive state (e.g., the RRC inactive 604), the wireless device may be assigned/provided/configured with a RAN notification area. A RAN notification area may comprise one or more cell identities (e.g., a list of RAIs and/or a list of TAIs). A base station may belong to one or more RAN notification areas. A cell may belong to one or more RAN notification areas. A wireless device may perform a notification area update with the RAN to update the RAN notification area of the wireless device, for example, if the wireless device moves (e.g., via a cell reselection) to a cell not included in the RAN notification area assigned/provided/configured to the wireless device.
A base station storing an RRC context for a wireless device or a last serving base station of the wireless device may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the wireless device at least during a period of time that the wireless device stays in a RAN notification area of the anchor base station and/or during a period of time that the wireless device stays in an RRC inactive state (e.g., RRC inactive 604).
A base station (e.g., gNBs 160 in
The physical signals and physical channels (e.g., described with respect to
The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. A flexible numerology may be supported, for example, to accommodate different deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range). A flexible numerology may be supported, for example, in an NR configuration or any other radio configurations. A numerology may be defined in terms of subcarrier spacing and/or cyclic prefix duration. Subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz. Cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs, for example, for a numerology in an NR configuration or any other radio configurations. Numerologies may be defined with the following subcarrier spacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3 μs; 60 kHz/1.2 μs; 120 kHz/0.59 s; 240 kHz/0.29 s, and/or any other subcarrier spacing/cyclic prefix duration combinations.
A slot may have a fixed quantity/number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing may have a shorter slot duration and more slots per subframe. Examples of numerology-dependent slot duration and slots-per-subframe transmission structure are shown in
A single numerology may be used across the entire bandwidth of a carrier (e.g., an NR such as shown in
Configuration of one or more bandwidth parts (BWPs) may support one or more wireless devices not capable of receiving the full carrier bandwidth. BWPs may support bandwidth adaptation, for example, for such wireless devices not capable of receiving the full carrier bandwidth. A BWP (e.g., a BWP of an NR configuration) may be defined by a subset of contiguous RBs on a carrier. A wireless device may be configured (e.g., via an RRC layer) with 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 for a serving cell may be active, for example, at a given time. The one or more BWPs may be referred to as active BWPs of the serving cell. A serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier, for example, if the serving cell is configured with a secondary uplink carrier.
A downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs (e.g., for unpaired spectra). A downlink BWP and an uplink BWP may be linked, for example, if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. A wireless device may expect that the center frequency for a downlink BWP is the same as the center frequency for an uplink BWP (e.g., for unpaired spectra).
A base station may configure a wireless device with one or more control resource sets (CORESETs) for at least one search space. The base station may configure the wireless device with one or more CORESETS, for example, for a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell) or on a secondary cell (SCell). A search space may comprise a set of locations in the time and frequency domains where the wireless device may monitor/find/detect/identify control information. The search space may be a wireless device-specific search space (e.g., a UE-specific search space) or a common search space (e.g., potentially usable by a plurality of wireless devices or a group of wireless user devices). A base station may configure a group of wireless devices with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.
A base station may configure a wireless device with one or more resource sets for one or more PUCCH transmissions, for example, for an uplink BWP in a set of configured uplink BWPs. A wireless device may receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP, for example, according to a configured numerology (e.g., a configured subcarrier spacing and/or a configured cyclic prefix duration) for the downlink BWP. The wireless device may send/transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP, for example, according to a configured numerology (e.g., a configured subcarrier spacing and/or a configured cyclic prefix length for the uplink BWP).
One or more BWP indicator fields may be provided/comprised in Downlink Control Information (DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.
A base station may semi-statically configure a wireless device with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. A default downlink BWP may be an initial active downlink BWP, for example, if the base station does not provide/configure a default downlink BWP to/for the wireless device. The wireless device may determine which BWP is the initial active downlink BWP, for example, based on a CORESET configuration obtained using the PBCH.
A base station may configure a wireless device with a BWP inactivity timer value for a PCell. The wireless device may start or restart a BWP inactivity timer at any appropriate time. The wireless device may start or restart the BWP inactivity timer, for example, if one or more conditions are satisfied. The one or more conditions may comprise at least one of: the wireless device detects DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; the wireless device detects DCI indicating an active downlink BWP other than a default downlink BWP for an unpaired spectra operation; and/or the wireless device detects DCI indicating an active uplink BWP other than a default uplink BWP for an unpaired spectra operation. The wireless device may start/run the BWP inactivity timer toward expiration (e.g., increment from zero to the BWP inactivity timer value, or decrement from the BWP inactivity timer value to zero), for example, if the wireless device does not detect DCI during a time interval (e.g., 1 ms or 0.5 ms). The wireless device may switch from the active downlink BWP to the default downlink BWP, for example, if the BWP inactivity timer expires.
A base station may semi-statically configure a wireless device with one or more BWPs. A wireless device may switch an active BWP from a first BWP to a second BWP, for example, based on (e.g., after or in response to) receiving DCI indicating the second BWP as an active BWP. A wireless device may switch an active BWP from a first BWP to a second BWP, for example, based on (e.g., after or in response to) an expiry of the BWP inactivity timer (e.g., if the second BWP is the default BWP).
A downlink BWP switching may refer to switching an active downlink BWP from a first downlink BWP to a second downlink BWP (e.g., the second downlink BWP is activated and the first downlink BWP is deactivated). An uplink BWP switching may refer to switching an active uplink BWP from a first uplink BWP to a second uplink BWP (e.g., the second uplink BWP is activated and the first uplink BWP is deactivated). Downlink and uplink BWP switching may be performed independently (e.g., in paired spectrum/spectra). Downlink and uplink BWP switching may be performed simultaneously (e.g., in unpaired spectrum/spectra). Switching between configured BWPs may occur, for example, based on RRC signaling, DCI signaling, expiration of a BWP inactivity timer, and/or an initiation of random access.
Wireless device procedures for switching BWPs on a secondary cell may be the same/similar as those on a primary cell, for example, if the wireless device is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value. The wireless device may use the timer value and the default downlink BWP for the secondary cell in the same/similar manner as the wireless device uses the timer value and/or default BWPs for a primary cell. The timer value (e.g., the BWP inactivity timer) may be configured per cell (e.g., for one or more BWPs), for example, via RRC signaling or any other signaling. One or more active BWPs may switch to another BWP, for example, based on an expiration of the BWP inactivity timer.
Two or more carriers may be aggregated and data may be simultaneously sent/transmitted to/from the same wireless device using carrier aggregation (CA) (e.g., to increase data rates). The aggregated carriers in CA may be referred to as component carriers (CCs). There may be a quantity/number of serving cells for the wireless device (e.g., one serving cell for a CC), for example, if CA is configured/used. The CCs may have multiple configurations in the frequency domain.
A network may set the maximum quantity of CCs that can be aggregated (e.g., up to 32 CCs may be aggregated in NR, or any other quantity may be aggregated in other systems). The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and/or duplexing schemes (TDD, FDD, or any other duplexing schemes). A serving cell for a wireless device using CA may have a downlink CC. One or more uplink CCs may be optionally configured for a serving cell (e.g., for FDD). The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, if the wireless device has more data traffic in the downlink than in the uplink.
One of the aggregated cells for a wireless device may be referred to as a primary cell (PCell), for example, if a CA is configured. The PCell may be the serving cell that the wireless initially connects to or access to, for example, during or at an RRC connection establishment, an RRC connection reestablishment, and/or a handover. The PCell may provide/configure the wireless device with NAS mobility information and the security input. Wireless device may have different PCells. For the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). For the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The other aggregated cells (e.g., associated with CCs other than the DL PCC and UL PCC) for the wireless device may be referred to as secondary cells (SCells). The SCells may be configured, for example, after the PCell is configured for the wireless device. An SCell may be configured via an RRC connection reconfiguration procedure. For the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). For the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC).
Configured SCells for a wireless device may be activated or deactivated, for example, based on traffic and channel conditions. Deactivation of an SCell may cause the wireless device to stop PDCCH and PDSCH reception on the SCell and PUSCH, SRS, and CQI transmissions on the SCell. Configured SCells may be activated or deactivated, for example, using a MAC CE (e.g., the MAC CE described with respect to
DCI may comprise control information, such as scheduling assignments and scheduling grants, for a cell. DCI may be sent/transmitted via the cell corresponding to the scheduling assignments and/or scheduling grants, which may be referred to as a self-scheduling. DCI comprising control information for a cell may be sent/transmitted via another cell, which may be referred to as a cross-carrier scheduling. Uplink control information (UCI) may comprise control information, such as HARQ acknowledgments and channel state feedback (e.g., CQI, PMI, and/or RI) for aggregated cells. UCI may be sent/transmitted via an uplink control channel (e.g., a PUCCH) of the PCell or a certain SCell (e.g., an SCell configured with PUCCH). For a larger quantity/number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups.
A PCell may comprise a downlink carrier (e.g., the PCell 1011) and an uplink carrier (e.g., the PCell 1021). An SCell may comprise only a downlink carrier. A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index. The physical cell ID or the cell index may indicate/identify a downlink carrier and/or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined, for example, using a synchronization signal (e.g., PSS and/or SSS) sent/transmitted via a downlink component carrier. A cell index may be determined, for example, using one or more RRC messages. A physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. A first physical cell ID for a first downlink carrier may refer to the first physical cell ID for a cell comprising the first downlink carrier. Substantially the same/similar concept may apply to, for example, a carrier activation. Activation of a first carrier may refer to activation of a cell comprising the first carrier.
A multi-carrier nature of a PHY layer may be exposed/indicated to a MAC layer (e.g., in a CA configuration). A HARQ entity may operate on a serving cell. A transport block may be generated per assignment/grant per serving cell. A transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell.
For the downlink, a base station may send/transmit (e.g., unicast, multicast, and/or broadcast), to one or more wireless devices, one or more reference signals (RSs) (e.g., PSS, SSS, CSI-RS, DM-RS, and/or PT-RS). For the uplink, the one or more wireless devices may send/transmit one or more RSs to the base station (e.g., DM-RS, PT-RS, and/or SRS). The PSS and the SSS may be sent/transmitted by the base station and used by the one or more wireless devices to synchronize the one or more wireless devices with the base station. A synchronization signal (SS)/physical broadcast channel (PBCH) block may comprise the PSS, the SSS, and the PBCH. The base station may periodically send/transmit a burst of SS/PBCH blocks, which may be referred to as SSBs.
The SS/PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in
The location of the SS/PBCH block in the time and frequency domains may not be known to the wireless device (e.g., if the wireless device is searching for the cell). The wireless device may monitor a carrier for the PSS, for example, to find and select the cell. The wireless device may monitor a frequency location within the carrier. The wireless device may search for the PSS at a different frequency location within the carrier, for example, if the PSS is not found after a certain duration (e.g., 20 ms). The wireless device may search for the PSS at a different frequency location within the carrier, for example, as indicated by a synchronization raster. The wireless device may determine the locations of the SSS and the PBCH, respectively, for example, based on a known structure of the SS/PBCH block if the PSS is found at a location in the time and frequency domains. The SS/PBCH block may be a cell-defining SS block (CD-SSB). A primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. A cell selection/search and/or reselection may be based on the CD-SSB.
The SS/PBCH block may be used by the wireless device to determine one or more parameters of the cell. The wireless device may determine a physical cell identifier (PCI) of the cell, for example, based on the sequences of the PSS and the SSS, respectively. The wireless device may determine a location of a frame boundary of the cell, for example, based on the location of the SS/PBCH block. The SS/PBCH block may indicate that it has been sent/transmitted in accordance with a transmission pattern. An SS/PBCH block in the transmission pattern may be a known distance from the frame boundary (e.g., a predefined distance for a RAN configuration among one or more networks, one or more base stations, and one or more wireless devices).
The PBCH may use a QPSK modulation and/or forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may comprise/carry one or more DM-RSs for demodulation of the PBCH. The PBCH may comprise an indication of a current system frame quantity/number (SFN) of the cell and/or a SS/PBCH block timing index. These parameters may facilitate time synchronization of the wireless device to the base station. The PBCH may comprise a MIB used to send/transmit to the wireless device one or more parameters. The MIB may be used by the wireless device to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may comprise a System Information Block Type 1 (SIB1). The SIB1 may comprise information for the wireless device to access the cell. The wireless device may use one or more parameters of the MIB to monitor a PDCCH, which may be used to schedule a PDSCH. The PDSCH may comprise the SIB1. The SIB1 may be decoded using parameters provided/comprised in the MIB. The PBCH may indicate an absence of SIB1. The wireless device may be pointed to a frequency, for example, based on the PBCH indicating the absence of SIB1. The wireless device may search for an SS/PBCH block at the frequency to which the wireless device is pointed.
The wireless device may assume that one or more SS/PBCH blocks sent/transmitted with a same SS/PBCH block index are quasi co-located (QCLed) (e.g., having substantially the same/similar Doppler spread, Doppler shift, average gain, average delay, and/or spatial Rx parameters). The wireless device may not assume QCL for SS/PBCH block transmissions having different SS/PBCH block indices. SS/PBCH blocks (e.g., those within a half-frame) may be sent/transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell). A first SS/PBCH block may be sent/transmitted in a first spatial direction using a first beam, a second SS/PBCH block may be sent/transmitted in a second spatial direction using a second beam, a third SS/PBCH block may be sent/transmitted in a third spatial direction using a third beam, a fourth SS/PBCH block may be sent/transmitted in a fourth spatial direction using a fourth beam, etc.
A base station may send/transmit a plurality of SS/PBCH blocks, for example, within a frequency span of a carrier. A first PCI of a first SS/PBCH block of the plurality of SS/PBCH blocks may be different from a second PCI of a second SS/PBCH block of the plurality of SS/PBCH blocks. The PCIs of SS/PBCH blocks sent/transmitted in different frequency locations may be different or substantially the same.
The CSI-RS may be sent/transmitted by the base station and used by the wireless device to acquire/obtain/determine channel state information (CSI). The base station may configure the wireless device with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure a wireless device with one or more of the same/similar CSI-RSs. The wireless device may measure the one or more CSI-RSs. The wireless device may estimate a downlink channel state and/or generate a CSI report, for example, based on the measuring of the one or more downlink CSI-RSs. The wireless device may send/transmit the CSI report to the base station (e.g., based on periodic CSI reporting, semi-persistent CSI reporting, and/or aperiodic CSI reporting). The base station may use feedback provided by the wireless device (e.g., the estimated downlink channel state) to perform a link adaptation.
The base station may semi-statically configure the wireless device with one or more CSI-RS resource sets. A CSI-RS resource may be associated with a location in the time and frequency domains and a periodicity. The base station may selectively activate and/or deactivate a CSI-RS resource. The base station may indicate to the wireless device that a CSI-RS resource in the CSI-RS resource set is activated and/or deactivated.
The base station may configure the wireless device to report CSI measurements. The base station may configure the wireless device to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the wireless device may be configured with a timing and/or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. The base station may command the wireless device to measure a configured CSI-RS resource and provide a CSI report relating to the measurement(s). For semi-persistent CSI reporting, the base station may configure the wireless device to send/transmit periodically, and selectively activate or deactivate the periodic reporting (e.g., via one or more activation/deactivation MAC CEs and/or one or more DCIs). The base station may configure the wireless device with a CSI-RS resource set and CSI reports, for example, using RRC signaling.
The CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports (or any other quantity of antenna ports). The wireless device may be configured to use/employ the same OFDM symbols for a downlink CSI-RS and a CORESET, for example, if the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET. The wireless device may be configured to use/employ the same OFDM symbols for a downlink CSI-RS and SS/PBCH blocks, for example, if the downlink CSI-RS and SS/PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS/PBCH blocks.
Downlink DM-RSs may be sent/transmitted by a base station and received/used by a wireless device for a channel estimation. The downlink DM-RSs may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). A network (e.g., an NR network) may support one or more variable and/or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure the wireless device with a quantity/number (e.g. a maximum quantity/number) of front-loaded DM-RS symbols for a PDSCH. A DM-RS configuration may support one or more DM-RS ports. A DM-RS configuration may support up to eight orthogonal downlink DM-RS ports per wireless device (e.g., for single user-MIMO). A DM-RS configuration may support up to 4 orthogonal downlink DM-RS ports per wireless device (e.g., for multiuser-MIMO). A radio network may support (e.g., at least for CP-OFDM) a common DM-RS structure for downlink and uplink. A DM-RS location, a DM-RS pattern, and/or a scrambling sequence may be the same or different. The base station may send/transmit a downlink DM-RS and a corresponding PDSCH, for example, using the same precoding matrix. The wireless device may use the one or more downlink DM-RSs for coherent demodulation/channel estimation of the PDSCH.
A transmitter (e.g., a transmitter of a base station) may use a precoder matrices for a part of a transmission bandwidth. The transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different, for example, based on the first bandwidth being different from the second bandwidth. The wireless device may assume that a same precoding matrix is used across a set of PRBs. The set of PRBs may be determined/indicated/identified/denoted as a precoding resource block group (PRG).
A PDSCH may comprise one or more layers. The wireless device may assume that at least one symbol with DM-RS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure one or more DM-RSs for a PDSCH (e.g., up to 3 DM-RSs for the PDSCH). Downlink PT-RS may be sent/transmitted by a base station and used by a wireless device, for example, for a phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and/or the pattern of the downlink PT-RS may be configured on a wireless device-specific basis, for example, using a combination of RRC signaling and/or an association with one or more parameters used/employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. A dynamic presence of a downlink PT-RS, if configured, may be associated with one or more DCI parameters comprising at least MCS. A network (e.g., an NR network) may support a plurality of PT-RS densities defined in the time and/or frequency domains. A frequency domain density (if configured/present) may be associated with at least one configuration of a scheduled bandwidth. The wireless device may assume a same precoding for a DM-RS port and a PT-RS port. The quantity/number of PT-RS ports may be fewer than the quantity/number of DM-RS ports in a scheduled resource. Downlink PT-RS may be configured/allocated/confined in the scheduled time/frequency duration for the wireless device. Downlink PT-RS may be sent/transmitted via symbols, for example, to facilitate a phase tracking at the receiver.
The wireless device may send/transmit an uplink DM-RS to a base station, for example, for a channel estimation. The base station may use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. The wireless device may send/transmit an uplink DM-RS with a PUSCH and/or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the wireless device with one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. The front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RSs may be configured to send/transmit at one or more symbols of a PUSCH and/or a PUCCH. The base station may semi-statically configure the wireless device with a quantity/number (e.g., the maximum quantity/number) of front-loaded DM-RS symbols for the PUSCH and/or the PUCCH, which the wireless device may use to schedule a single-symbol DM-RS and/or a double-symbol DM-RS. A network (e.g., an NR network) may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DM-RS structure for downlink and uplink. A DM-RS location, a DM-RS pattern, and/or a scrambling sequence for the DM-RS may be substantially the same or different.
A PUSCH may comprise one or more layers. A wireless device may send/transmit at least one symbol with DM-RS present on a layer of the one or more layers of the PUSCH. A higher layer may configure one or more DM-RSs (e.g., up to three DM-RSs) for the PUSCH. Uplink PT-RS (which may be used by a base station for a phase tracking and/or a phase-noise compensation) may or may not be present, for example, depending on an RRC configuration of the wireless device. The presence and/or the pattern of an uplink PT-RS may be configured on a wireless device-specific basis (e.g., a UE-specific basis), for example, by a combination of RRC signaling and/or one or more parameters configured/employed for other purposes (e.g., MCS), which may be indicated by DCI. A dynamic presence of an uplink PT-RS, if configured, may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time/frequency domain. A frequency domain density (if configured/present) may be associated with at least one configuration of a scheduled bandwidth. The wireless device may assume a same precoding for a DM-RS port and a PT-RS port. A quantity/number of PT-RS ports may be less than a quantity/number of DM-RS ports in a scheduled resource. An uplink PT-RS may be configured/allocated/confined in the scheduled time/frequency duration for the wireless device.
One or more SRSs may be sent/transmitted by a wireless device to a base station, for example, for a channel state estimation to support uplink channel dependent scheduling and/or a link adaptation. SRS sent/transmitted by the wireless device may enable/allow a base station to estimate an uplink channel state at one or more frequencies. A scheduler at the base station may use/employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission for the wireless device. The base station may semi-statically configure the wireless device with one or more SRS resource sets. For an SRS resource set, the base station may configure the wireless device with one or more SRS resources. An SRS resource set applicability may be configured, for example, by a higher layer (e.g., RRC) parameter. An SRS resource in an SRS resource set of the one or more SRS resource sets (e.g., with the same/similar time domain behavior, periodic, aperiodic, and/or the like) may be sent/transmitted at a time instant (e.g., simultaneously), for example, if a higher layer parameter indicates beam management. The wireless device may send/transmit one or more SRS resources in SRS resource sets. A network (e.g., an NR network) may support aperiodic, periodic, and/or semi-persistent SRS transmissions. The wireless device may send/transmit SRS resources, for example, based on one or more trigger types. The one or more trigger types may comprise higher layer signaling (e.g., RRC) and/or one or more DCI formats. At least one DCI format may be used/employed for the wireless device to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. The wireless device may be configured to send/transmit an SRS, for example, after a transmission of a PUSCH and a corresponding uplink DM-RS if a PUSCH and an SRS are sent/transmitted in a same slot. A base station may semi-statically configure a wireless device with one or more SRS configuration parameters indicating at least one of following: an SRS resource configuration identifier; a quantity/number of SRS ports; time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/or subframe level periodicity; an offset for a periodic and/or an aperiodic SRS resource; a quantity/number of OFDM symbols in an SRS resource; a starting OFDM symbol of an SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and/or an SRS sequence ID.
An antenna port may be determined/defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. The receiver may infer/determine the channel (e.g., fading gain, multipath delay, and/or the like) for conveying a second symbol on an antenna port, from the channel for conveying a first symbol on the antenna port, for example, if the first symbol and the second symbol are sent/transmitted on the same antenna port. A first antenna port and a second antenna port may be referred to as quasi co-located (QCLed), for example, if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and/or spatial Receiving (Rx) parameters.
Channels that use beamforming may require beam management. Beam management may comprise a beam measurement, a beam selection, and/or a beam indication. A beam may be associated with one or more reference signals. A beam may be identified by one or more beamformed reference signals. The wireless device may perform a downlink beam measurement, for example, based on one or more downlink reference signals (e.g., a CSI-RS) and generate a beam measurement report. The wireless device may perform the downlink beam measurement procedure, for example, after an RRC connection is set up with a base station.
One or more beams may be configured for a wireless device in a wireless device-specific configuration. Three beams are shown in
CSI-RSs (e.g., CSI-RSs 1101, 1102, 1103) may be sent/transmitted by the base station and used by the wireless device for one or more measurements. The wireless device may measure an RSRP of configured CSI-RS resources. The base station may configure the wireless device with a reporting configuration, and the wireless device may report the RSRP measurements to a network (e.g., via one or more base stations) based on the reporting configuration. The base station may determine, based on the reported measurement results, one or more transmission configuration indication/indicator (TCI) states comprising a quantity/number of reference signals. The base station may indicate one or more TCI states to the wireless device (e.g., via RRC signaling, a MAC CE, and/or DCI). The wireless device may receive a downlink transmission with an Rx beam determined based on the one or more TCI states. The wireless device may or may not have a capability of beam correspondence. The wireless device may determine a spatial domain filter of a transmit (Tx) beam, for example, based on a spatial domain filter of the corresponding Rx beam, if the wireless device has the capability of beam correspondence. The wireless device may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam, for example, if the wireless device does not have the capability of beam correspondence. The wireless device may perform the uplink beam selection procedure, for example, based on one or more sounding reference signal (SRS) resources configured to the wireless device by the base station. The base station may select and indicate uplink beams for the wireless device, for example, based on measurements of the one or more SRS resources sent/transmitted by the wireless device.
A wireless device may determine/assess (e.g., measure) a channel quality of one or more beam pair links, for example, in a beam management procedure. A beam pair link may comprise a Tx beam of a base station and an Rx beam of the wireless device. The Tx beam of the base station may send/transmit a downlink signal, and the Rx beam of the wireless device may receive the downlink signal. The wireless device may send/transmit a beam measurement report, for example, based on the assessment/determination. The beam measurement report may indicate one or more beam pair quality parameters comprising at least one of: one or more beam identifications (e.g., a beam index, a reference signal index, or the like), an RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and/or a rank indicator (RI).
A wireless device may initiate/start/perform a beam failure recovery (BFR) procedure, for example, based on detecting a beam failure. The wireless device may send/transmit a BFR request (e.g., a preamble, UCI, an SR, a MAC CE, and/or the like), for example, based on the initiating the BFR procedure. The wireless device may detect the beam failure, for example, based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and/or the like).
The wireless device may measure a quality of a beam pair link, for example, using one or more reference signals (RSs) comprising one or more SS/PBCH blocks, one or more CSI-RS resources, and/or one or more DM-RSs. A quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, an RSRQ value, and/or a CSI value measured on RS resources. The base station may indicate that an RS resource is QCLed with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and/or the like). The RS resource and the one or more DM-RSs of the channel may be QCLed, for example, if the channel characteristics (e.g., Doppler shift, Doppler spread, an average delay, delay spread, a spatial Rx parameter, fading, and/or the like) from a transmission via the RS resource to the wireless device are similar or the same as the channel characteristics from a transmission via the channel to the wireless device.
A network (e.g., an NR network comprising a gNB and/or an ng-eNB) and/or the wireless device may initiate/start/perform a random access procedure. A wireless device in an RRC idle (e.g., an RRC_IDLE) state and/or an RRC inactive (e.g., an RRC_INACTIVE) state may initiate/perform the random access procedure to request a connection setup to a network. The wireless device may initiate/start/perform the random access procedure from an RRC connected (e.g., an RRC_CONNECTED) state. The wireless device may initiate/start/perform the random access procedure to request uplink resources (e.g., for uplink transmission of an SR if there is no PUCCH resource available) and/or acquire/obtain/determine an uplink timing (e.g., if an uplink synchronization status is non-synchronized). The wireless device may initiate/start/perform the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information blocks, such as SIB2, SIB3, and/or the like). The wireless device may initiate/start/perform the random access procedure for a beam failure recovery request. A network may initiate/start/perform a random access procedure, for example, for a handover and/or for establishing time alignment for an SCell addition.
The configuration message 1310 may be sent/transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the wireless device. The one or more RACH parameters may comprise at least one of: 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) the one or more RRC messages to one or more wireless devices. The one or more RRC messages may be wireless device-specific. The one or more RRC messages that are wireless device-specific may be, for example, dedicated RRC messages sent/transmitted to a wireless device in an RRC connected (e.g., an RRC_CONNECTED) state and/or in an RRC inactive (e.g., an RRC_INACTIVE) state. The wireless devices may determine, based on the one or more RACH parameters, a time-frequency resource and/or an uplink transmit power for transmission of the first message (e.g., Msg 1 1311) and/or the third message (e.g., Msg 3 1313). The wireless device may determine a reception timing and a downlink channel for receiving the second message (e.g., Msg 2 1312) and the fourth message (e.g., Msg 4 1314), for example, based on the one or more RACH parameters.
The one or more RACH parameters provided/configured/comprised in the configuration message 1310 may indicate one or more Physical RACH (PRACH) occasions available for transmission of the first message (e.g., Msg 1 1311). The one or more PRACH occasions may be predefined (e.g., by a network comprising one or more base stations). The one or more RACH parameters may indicate one or more available sets of one or more PRACH occasions (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH occasions and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS/PBCH blocks and/or CSI-RSs. The one or more RACH parameters may indicate a quantity/number of SS/PBCH blocks mapped to a PRACH occasion and/or a quantity/number of preambles mapped to a SS/PBCH blocks.
The one or more RACH parameters provided/configured/comprised in the configuration message 1310 may be used to determine an uplink transmit power of first message (e.g., Msg 1 1311) and/or third message (e.g., Msg 3 1313). The one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and/or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. The one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the first message (e.g., Msg 1 1311) and the third message (e.g., Msg 3 1313); and/or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds, for example, based on which the wireless device may determine at least one reference signal (e.g., an SSB and/or CSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier).
The first message (e.g., Msg 1 1311) may comprise one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g., group A and/or group B). A preamble group may comprise one or more preambles. The wireless device may determine the preamble group, for example, based on a pathloss measurement and/or a size of the third message (e.g., Msg 3 1313). The wireless device may measure an RSRP of one or more reference signals (e.g., SSBs and/or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The wireless device may select at least one preamble associated with the one or more reference signals and/or a selected preamble group, 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 determine the preamble, for example, based on the one or more RACH parameters provided/configured/comprised in the configuration message 1310. The wireless device may determine the preamble, for example, based on a pathloss measurement, an RSRP measurement, and/or a size of the third message (e.g., Msg 3 1313). The one or more RACH parameters may indicate: a preamble format; a maximum quantity/number of preamble transmissions; and/or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station may use the one or more RACH parameters to configure the wireless device with an association between one or more preambles and one or more reference signals (e.g., SSBs and/or CSI-RSs). The wireless device may determine the preamble to be comprised in first message (e.g., Msg 1 1311), for example, based on the association if the association is configured. The first message (e.g., Msg 1 1311) may be sent/transmitted to the base station via one or more PRACH occasions. The wireless device may use one or more reference signals (e.g., SSBs and/or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.
The wireless device may perform a preamble retransmission, for example, if no response is received based on (e.g., after or in response to) a preamble transmission (e.g., for a period of time, such as a monitoring window for monitoring an RAR). The wireless device may increase an uplink transmit power for the preamble retransmission. The wireless device may select an initial preamble transmit power, for example, based on a pathloss measurement and/or a target received preamble power configured by the network. The wireless device may determine to resend/retransmit a preamble and may ramp up the uplink transmit power. The wireless device may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The wireless device may ramp up the uplink transmit power, for example, if the wireless device determines a reference signal (e.g., SSB and/or CSI-RS) that is the same as a previous preamble transmission. The wireless device may count the quantity/number of preamble transmissions and/or retransmissions, for example, using a counter parameter (e.g., PREAMBLE_TRANSMISSION_COUNTER). The wireless device may determine that a random access procedure has been completed unsuccessfully, for example, if the quantity/number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax) without receiving a successful response (e.g., an RAR).
The second message (e.g., Msg 2 1312) (e.g., received by the wireless device) may comprise an RAR. The second message (e.g., Msg 2 1312) may comprise multiple RARs corresponding to multiple wireless devices. The second message (e.g., Msg 2 1312) may be received, for example, based on (e.g., after or in response to) the sending/transmitting of the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may be scheduled on the DL-SCH and may be indicated by a 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 first message (e.g., Msg 1 1311) was received by the base station. The second message (e.g., Msg 2 1312) may comprise a time-alignment command that may be used by the wireless device to adjust the transmission timing of the wireless device, a scheduling grant for transmission of the third message (e.g., Msg 3 1313), and/or a Temporary Cell RNTI (TC-RNTI). The wireless device may determine/start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the second message (e.g., Msg 2 1312), for example, after sending/transmitting the first message (e.g., Msg 1 1311) (e.g., a preamble). The wireless device may determine the start time of the time window, for example, based on a PRACH occasion that the wireless device uses to send/transmit the first message (e.g., Msg 1 1311) (e.g., the preamble). The wireless device may start the time window one or more symbols after the last symbol of the first message (e.g., Msg 1 1311) comprising the preamble (e.g., the symbol in which the first message (e.g., Msg 1 1311) comprising the preamble transmission was completed or at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be mapped in a common search space (e.g., a Type1-PDCCH common search space) configured by an RRC message. The wireless device may identify/determine the RAR, for example, based on an RNTI. Radio network temporary identifiers (RNTIs) may be used depending on one or more events initiating/starting the random access procedure. The wireless device may use a RA-RNTI, for example, for one or more communications associated with random access or any other purpose. The RA-RNTI may be associated with PRACH occasions in which the wireless device sends/transmits a preamble. The wireless device may determine the RA-RNTI, for example, based on at least one of: an OFDM symbol index; a slot index; a frequency domain index; and/or a UL carrier indicator of the PRACH occasions. An example RA-RNTI may be determined as follows:
where s_id may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0<s_id<14), t_id may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0<t_id<80), f_id may be an index of the PRACH occasion in the frequency domain (e.g., 0<f_id<8), and ul_carrier_id may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).
The wireless device may send/transmit the third message (e.g., Msg 3 1313), for example, based on (e.g., after or in response to) a successful reception of the second message (e.g., Msg 2 1312) (e.g., using resources identified in the Msg 2 1312). The third message (e.g., Msg 3 1313) may be used, for example, for contention resolution in the contention-based random access procedure. A plurality of wireless devices may send/transmit the same preamble to a base station, and the base station may send/transmit an RAR that corresponds to a wireless device. Collisions may occur, for example, if the plurality of wireless device interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the third message (e.g., Msg 3 1313) and the fourth message (e.g., Msg 4 1314)) may be used to increase the likelihood that the wireless device does not incorrectly use an identity of another the wireless device. The wireless device may comprise a device identifier in the third message (e.g., Msg 3 1313) (e.g., a C-RNTI if assigned, a TC RNTI comprised in the second message (e.g., Msg 2 1312), and/or any other suitable identifier), for example, to perform contention resolution.
The fourth message (e.g., Msg 4 1314) may be received, for example, based on (e.g., after or in response to) the sending/transmitting of the third message (e.g., Msg 3 1313). The base station may address the wireless on the PDCCH (e.g., the base station may send the PDCCH to the wireless device) using a C-RNTI, for example, If the C-RNTI was included in the third message (e.g., Msg 3 1313). The random access procedure may be determined to be successfully completed, for example, if the unique C RNTI of the wireless device is detected on the PDCCH (e.g., the PDCCH is scrambled by the C-RNTI). fourth message (e.g., Msg 4 1314) may be received using a DL-SCH associated with a TC RNTI, for example, if the TC RNTI is comprised in the third message (e.g., Msg 3 1313) (e.g., if the wireless device is in an RRC idle (e.g., an RRC_IDLE) state or not otherwise connected to the base station). The wireless device may determine that the contention resolution is successful and/or the wireless device may determine that the random access procedure is successfully completed, for example, if a MAC PDU is successfully decoded and a MAC PDU comprises the wireless device contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent/transmitted in third message (e.g., Msg 3 1313).
The wireless device may be configured with an SUL carrier and/or an NUL carrier. An initial access (e.g., random access) may be supported via an uplink carrier. A base station may configure the wireless device with multiple RACH configurations (e.g., two separate RACH configurations comprising: one for an SUL carrier and the other for an NUL carrier). For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The wireless device may determine to use the SUL carrier, for example, if a measured quality of one or more reference signals (e.g., one or more reference signals associated with the NUL carrier) is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the first message (e.g., Msg 1 1311) and/or the third message (e.g., Msg 3 1313)) may remain on, or may be performed via, the selected carrier. The wireless device may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313). The wireless device may determine and/or switch an uplink carrier for the first message (e.g., Msg 1 1311) and/or the third message (e.g., Msg 3 1313), for example, based on a channel clear assessment (e.g., a listen-before-talk).
The two-step (e.g., contention-free) random access procedure may be configured/initiated for a beam failure recovery, other SI request, an SCell addition, and/or a handover. A base station may indicate, or assign to, the wireless device a preamble to be used for the first message (e.g., Msg 1 1321). The wireless device may receive, from the base station via a PDCCH and/or an RRC, an indication of the preamble (e.g., ra-PreambleIndex).
The wireless device may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR, for example, based on (e.g., after or in response to) sending/transmitting the preamble. The base station may configure the wireless device with one or more beam failure recovery parameters, such as a separate time window and/or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceld). The base station may configure the one or more beam failure recovery parameters, for example, in association with a beam failure recovery request. The separate time window for monitoring the PDCCH and/or an RAR may be configured to start after sending/transmitting a beam failure recovery request (e.g., the window may start any quantity of symbols and/or slots after sending/transmitting the beam failure recovery request). The wireless device may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. During the two-step (e.g., contention-free) random access procedure, the wireless device may determine that a random access procedure is successful, for example, based on (e.g., after or in response to) sending/transmitting first message (e.g., Msg 1 1321) and receiving a corresponding second message (e.g., Msg 2 1322). The wireless device may determine that a random access procedure has successfully been completed, for example, if a PDCCH transmission is addressed to a corresponding C-RNTI. The wireless device may determine that a random access procedure has successfully been completed, for example, if the wireless device receives an RAR comprising a preamble identifier corresponding to a preamble sent/transmitted by the wireless device and/or the RAR comprises a MAC sub-PDU with the preamble identifier. The wireless device may determine the response as an indication of an acknowledgement for an SI request.
Msg A 1320 may be sent/transmitted in an uplink transmission by the wireless device. Msg A 1320 may comprise one or more transmissions of a preamble 1341 and/or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and/or equivalent to the contents of the third message (e.g., Msg 3 1313) (e.g., shown in
The wireless device may start/initiate the two-step random access procedure (e.g., the two-step random access procedure shown in
The wireless device may determine, based on two-step RACH parameters comprised in the configuration message 1330, a radio resource and/or an uplink transmit power for the preamble 1341 and/or the transport block 1342 (e.g., comprised in the first message (e.g., Msg A 1331)). The RACH parameters may indicate an MCS, a time-frequency resource, and/or a power control for the preamble 1341 and/or the transport block 1342. A time-frequency resource for transmission of the preamble 1341 (e.g., a PRACH) and a time-frequency resource for transmission of the transport block 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACH parameters may enable the wireless device to determine a reception timing and a downlink channel for monitoring for and/or receiving second message (e.g., Msg B 1332).
The transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the wireless device, security information, and/or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may send/transmit the 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 comprise at least one of: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and/or an MCS); a wireless device identifier (e.g., a UE identifier for contention resolution); and/or an RNTI (e.g., a C-RNTI or a TC-RNTI). The wireless device may determine that the two-step random access procedure is successfully completed, for example, if a preamble identifier in the second message (e.g., Msg B 1332) corresponds to, or is matched to, a preamble sent/transmitted by the wireless device and/or the identifier of the wireless device in second message (e.g., Msg B 1332) corresponds to, or is matched to, the identifier of the wireless device in the first message (e.g., Msg A 1331) (e.g., the transport block 1342).
A wireless device and a base station may exchange control signaling (e.g., control information). The control signaling may be referred to as L1/L2 control signaling and may originate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g., layer 2) of the wireless device or the base station. The control signaling may comprise 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.
The downlink control signaling may comprise at least one of: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and/or a transport format; slot format information; a preemption indication; a power control command; and/or any other suitable signaling. The wireless device may receive the downlink control signaling in a payload sent/transmitted by the base station via a PDCCH. The payload sent/transmitted via the PDCCH may be referred to as downlink control information (DCI). The PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of wireless devices. The GC-PDCCH may be scrambled by a group common RNTI.
A base station may attach one or more cyclic redundancy check (CRC) parity bits to DCI, for example, in order to facilitate detection of transmission errors. The base station may scramble the CRC parity bits with an identifier of a wireless device (or an identifier of a group of wireless devices), for example, if the DCI is intended for the wireless device (or the group of the wireless devices). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive-OR operation) of the identifier value and the CRC parity bits. The identifier may comprise a 16-bit value of an RNTI.
DCIs may be used for different purposes. A purpose may be indicated by the type of an RNTI used to scramble the CRC parity bits. DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and/or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal. DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and/or a triggering of PDCCH-ordered random access. DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 shown in
A base station may send/transmit DCIs with one or more DCI formats, for example, depending on the purpose and/or content of the DCIs. DCI format 00 may be used for scheduling of a PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 01 may be used for scheduling of a PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 10 may be used for scheduling of a PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 11 may be used for scheduling of a PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 20 may be used for providing a slot format indication to a group of wireless devices. DCI format 21 may be used for informing/notifying a group of wireless devices of a physical resource block and/or an OFDM symbol where the group of wireless devices may assume no transmission is intended to the group of wireless devices. DCI format 22 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more wireless devices. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.
The base station may process the DCI with channel coding (e.g., polar coding), rate matching, scrambling and/or QPSK modulation, for example, after scrambling the DCI with an RNTI. A base station may map the coded and modulated DCI on resource elements used and/or configured for a PDCCH. The base station may send/transmit the DCI via a PDCCH occupying a quantity/number of contiguous control channel elements (CCEs), for example, based on a payload size of the DCI and/or a coverage of the base station. The quantity/number of the contiguous CCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/or any other suitable quantity/number. A CCE may comprise a number (e.g., 6) of resource-element groups (REGs). A REG may comprise a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements may be based on mapping of CCEs and REGs (e.g., CCE-to-REG mapping).
The base station may send/transmit, to the wireless device, one or more RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs (e.g., at a given aggregation level). The configuration parameters may indicate at least one of: a quantity/number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the wireless device; and/or whether a search space set is a common search space set or a wireless device-specific search space set (e.g., a UE-specific search space set). A set of CCEs in the common search space set may be predefined and known to the wireless device. A set of CCEs in the wireless device-specific search space set (e.g., the UE-specific search space set) may be configured, for example, based on the identity of the wireless device (e.g., C-RNTI).
As shown in
The may send/transmit uplink control signaling (e.g., UCI) to a base station. The uplink control signaling may comprise HARQ acknowledgements for received DL-SCH transport blocks. The wireless device may send/transmit the HARQ acknowledgements, for example, based on (e.g., after or in response to) receiving a DL-SCH transport block. Uplink control signaling may comprise CSI indicating a channel quality of a physical downlink channel. The wireless device may send/transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for downlink transmission(s). Uplink control signaling may comprise scheduling requests (SR). The wireless device may send/transmit an SR indicating that uplink data is available for transmission to the base station. The wireless device may send/transmit UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a PUCCH or a PUSCH. The wireless device may send/transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.
There may be multiple PUCCH formats (e.g., five PUCCH formats). A wireless device may determine a PUCCH format, for example, based on a size of UCI (e.g., a quantity/number of uplink symbols of UCI transmission and a quantity/number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may comprise two or fewer bits. The wireless device may send/transmit UCI via a PUCCH resource, for example, using PUCCH format 0 if the transmission is over/via one or two symbols and the quantity/number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bits) is one or two. PUCCH format 1 may occupy a quantity/number of OFDM symbols (e.g., between four and fourteen OFDM symbols) and may comprise two or fewer bits. The wireless device may use PUCCH format 1, for example, if the transmission is over/via four or more symbols and the quantity/number of HARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may comprise more than two bits. The wireless device may use PUCCH format 2, for example, if the transmission is over/via one or two symbols and the quantity/number of UCI bits is two or more. PUCCH format 3 may occupy a quantity/number of OFDM symbols (e.g., between four and fourteen OFDM symbols) and may comprise more than two bits. The wireless device may use PUCCH format 3, for example, if the transmission is four or more symbols, the quantity/number of UCI bits is two or more, and the PUCCH resource does not comprise an orthogonal cover code (OCC). PUCCH format 4 may occupy a quantity/number of OFDM symbols (e.g., between four and fourteen OFDM symbols) and may comprise more than two bits. The wireless device may use PUCCH format 4, for example, if the transmission is four or more symbols, the quantity/number of UCI bits is two or more, and the PUCCH resource comprises an OCC.
The base station may send/transmit configuration parameters to the wireless device for a plurality of PUCCH resource sets, for example, using an RRC message. The plurality of PUCCH resource sets (e.g., up to four sets in NR, or up to any other quantity of sets in other systems) may be configured on an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and/or a quantity/number (e.g. a maximum quantity/number) of UCI information bits the wireless device may send/transmit using one of the plurality of PUCCH resources in the PUCCH resource set. The wireless device may select one of the plurality of PUCCH resource sets, for example, based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and/or CSI) if configured with a plurality of PUCCH resource sets. The wireless device may select a first PUCCH resource set having a PUCCH resource set index equal to “0,” for example, if the total bit length of UCI information bits is two or fewer. The wireless device may select a second PUCCH resource set having a PUCCH resource set index equal to “1,” for example, if the total bit length of UCI information bits is greater than two and less than or equal to a first configured value. The wireless device may select a third PUCCH resource set having a PUCCH resource set index equal to “2,” for example, if the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value. The wireless device may select a fourth PUCCH resource set having a PUCCH resource set index equal to “3,” for example, if the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406, 1706, or any other quantity of bits).
The wireless device may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and/or SR) transmission, for example, after determining a PUCCH resource set from a plurality of PUCCH resource sets. The wireless device may determine the PUCCH resource, for example, based on a PUCCH resource indicator in DCI (e.g., with DCI format 1_0 or DCI for 1_1) received on/via a PDCCH. An n-bit (e.g., a three-bit) PUCCH resource indicator in the DCI may indicate one of multiple (e.g., eight) PUCCH resources in the PUCCH resource set. The wireless device may send/transmit the UCI (HARQ-ACK, CSI and/or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI, for example, based on the PUCCH resource indicator.
The base station 1504 may connect the wireless device 1502 to a core network (not shown) via radio communications over the air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 may be referred to as the downlink. The communication direction from the wireless device 1502 to the base station 1504 over the air interface may be referred to as the uplink. Downlink transmissions may be separated from uplink transmissions, for example, using various duplex schemes (e.g., FDD, TDD, and/or some combination of the duplexing techniques).
For the downlink, data to be sent to the wireless device 1502 from the base station 1504 may be provided/transferred/sent to the processing system 1508 of the base station 1504. The data may be provided/transferred/sent to the processing system 1508 by, for example, a core network. For the uplink, data to be sent to the base station 1504 from the wireless device 1502 may be provided/transferred/sent to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 may comprise an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, described with respect to
The data to be sent to the wireless device 1502 may be provided/transferred/sent to a transmission processing system 1510 of base station 1504, for example, after being processed by the processing system 1508. The data to be sent to base station 1504 may be provided/transferred/sent to a transmission processing system 1520 of the wireless device 1502, for example, after being processed by the processing system 1518. The transmission processing system 1510 and the transmission processing system 1520 may implement layer 1 OSI functionality. Layer 1 may comprise a PHY layer, for example, described with respect to
A reception processing system 1512 of the base station 1504 may receive the uplink transmission from the wireless device 1502. The reception processing system 1512 of the base station 1504 may comprise one or more TRPs. A reception processing system 1522 of the wireless device 1502 may receive the downlink transmission from the base station 1504. The reception processing system 1522 of the wireless device 1502 may comprise one or more antenna panels. The reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer, for example, described with respect to
The base station 1504 may comprise multiple antennas (e.g., multiple antenna panels, multiple TRPs, etc.). The wireless device 1502 may comprise multiple antennas (e.g., multiple antenna panels, etc.). The multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit/receive diversity, and/or beamforming. The wireless device 1502 and/or the base station 1504 may have a single antenna.
The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and/or the processing system 1518, respectively, to carry out one or more of the functionalities (e.g., one or more functionalities described herein and other functionalities of general computers, processors, memories, and/or other peripherals). The transmission processing system 1510 and/or the reception processing system 1512 may be coupled to the memory 1514 and/or another memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities. The transmission processing system 1520 and/or the reception processing system 1522 may be coupled to the memory 1524 and/or another memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.
The processing system 1508 and/or the processing system 1518 may comprise one or more controllers and/or one or more processors. The one or more controllers and/or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and/or other programmable logic device, discrete gate and/or transistor logic, discrete hardware components, an on-board unit, or any combination thereof. The processing system 1508 and/or the processing system 1518 may perform at least one of signal coding/processing, data processing, power control, input/output processing, and/or any other functionality that may enable the wireless device 1502 and/or the base station 1504 to operate in a wireless environment.
The processing system 1508 may be connected to one or more peripherals 1516. The processing system 1518 may be connected to one or more peripherals 1526. The one or more peripherals 1516 and the one or more peripherals 1526 may comprise software and/or hardware that provide features and/or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and/or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and/or the like). The processing system 1508 and/or the processing system 1518 may receive input data (e.g., user input data) from, and/or provide output data (e.g., user output data) to, the one or more peripherals 1516 and/or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and/or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 may be connected to a Global Positioning System (GPS) chipset 1517. The processing system 1518 may be connected to a Global Positioning System (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 may be configured to determine and provide geographic location information of the wireless device 1502 and the base station 1504, respectively.
The example in
A wireless device may receive, from a base station, one or more messages (e.g. RRC messages) comprising configuration parameters of a plurality of cells (e.g., a primary cell, one or more secondary cells). The wireless device may communicate with at least one base station (e.g., two or more base stations in dual-connectivity) via the plurality of cells. The one or more messages (e.g. as a part of the configuration parameters) may comprise parameters of PHY, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. The configuration parameters may comprise parameters for configuring PHY and MAC layer channels, bearers, etc. The configuration parameters may comprise parameters indicating values of timers for PHY, MAC, RLC, PCDP, SDAP, RRC layers, and/or communication channels.
A timer may begin running, for example, after (e.g., as soon as) it is started and continue running until it is stopped or until it expires. A timer may be started, for example, if it is not running or restarted if it is running. A timer may be associated with a value (e.g., the timer may be started or restarted from a value or may be started from zero and expire after (e.g., as soon as) it reaches the value). The duration of a timer may not be updated, for example, until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period/window for a process. With respect to an implementation and/or procedure related to one or more timers or other parameters, it will be understood that there may be multiple ways to implement the one or more timers or other parameters. One or more of the multiple ways to implement a timer may be used to measure a time period/window for the procedure. A random access response window timer may be used for measuring a window of time for receiving a random access response. The time difference between two time stamps may be used, for example, instead of starting a random access response window timer and determine the expiration of the timer. A process for measuring a time window may be restarted, for example, if a timer is restarted. Other example implementations may be configured/provided to restart a measurement of a time window.
A wireless device may receive one or more messages comprising one or more configuration parameters of a cell. A wireless device may receive the one or more messages comprising the one or more configuration parameters of a cell, for example, from a base station.
One or more configuration parameters may indicate, for a cell, at least two discontinuous transmission (DTXs) for an energy saving of the cell. For example, a first DTX of the at least two DTXs may be for a first TRP (e.g., TRP 1 as described herein in
A wireless device may not receive a downlink reception (e.g., PDSCH reception, CSI-RS, etc.). The wireless device may not receive a downlink reception (e.g., PDSCH reception, CSI-RS, etc.), for example, if in a non-active time, duration, and/or period of a DTX of the cell. This may not be efficient, for example, if a downlink reception associated with two TCI states (or two receiving beams) overlaps in time a non-active time, period, and/or duration of the first DTX (e.g., the first TRP is off), but the downlink reception overlaps in time an active time, period, and/or duration of the second DTX (e.g., the second TRP is on), or vice versa. Not receiving the downlink reception may not be efficient. Not receiving the downlink reception may not be efficient, for example, if in the non-active time, period, and/or duration of the first DTX the second TRP is on. This may increase latency of data communication.
Downlink receptions associated with at least two TCI states in a non-active time, duration, and/or period of one of the at least two DTXs may be enhanced. The wireless device may receive the downlink reception based on one TCI state of the at least two TCI states if in a non-active time, duration, and/or period of one of the at least two DTXs. The wireless device may receive the downlink reception based on a first TCI state of the at least two TCI states, for example, if in a non-active time, duration, and/or period of the second DTX of the at least two DTXs. The wireless device may receive the downlink reception based on a second TCI state of the at least two TCI states if in a non-active time, duration, and/or period of the first DTX of the at least two DTXs. The first TCI state and the second TCI state may be, for example, different. This may reduce latency of data communication.
A wireless device may not support dynamic switching between a single TRP and multiple TRPs for downlink receptions (e.g., PDSCH receptions). The wireless device may not receive the downlink reception based on one TCI state of the at least two TCI states, for example, if in a non-active time, duration, and/or period of one of the at least two DTXs. The base station may not switch off one of the TRPs that reduces energy saving.
Downlink receptions associated with at least two TCI states in a non-active time, duration, and/or period of one of the at least two DTXs may be enhanced. The downlink receptions associated with at least two TCI states in a non-active time, duration, and/or period of one of the at least two DTXs may be enhanced, for example, if the wireless device does not support dynamic switching between a single TRP and multiple TRPs. The wireless device may receive, if in a non-active time, duration, and/or period of one of the at least two DTXs, the downlink reception based on one TCI state of the at least two TCI states if the wireless device supports dynamic switching between a single TRP and multiple TRPs. The wireless device may receive, if in a non-active time, duration, and/or period of one of the at least two DTXs, the downlink reception based on the at least two TCI states if the wireless device does not support dynamic switching between a single TRP and multiple TRPs. The wireless device may not receive, if in a non-active time, duration, and/or period of one of the at least two DTXs, the downlink reception if the wireless device does not support dynamic switching between a single TRP and multiple TRPs.
A wireless device may receive (e.g., from a base station or a network) one or more messages (e.g., RRC messages, RRC reconfiguration messages) comprising one or more configuration parameters. The one or more configuration parameters may comprise one or more MAC cell group configuration parameters (e.g., MAC-CellGroupConfig) of a cell group comprising a cell. The one or more MAC cell group configuration parameters may comprise one or more cell discontinuous-transmission (DTX) configuration parameters (e.g., celldtx-Config) used to configure and/or indicate a cell DTX of the cell. The one or more MAC cell group configuration parameters may comprise one or more cell discontinuous-reception (DRX) configuration parameters (e.g., celldrx-Config) used to configure and/or indicate a cell DRX of the cell. The one or more configuration parameters may comprise one or more serving cell configuration parameters (e.g., ServingCellConfig) of a cell. The one or more serving cell configuration parameters may comprise one or more cell DTX configuration parameters (e.g., celldtx-Config) used to configure and/or indicate a cell DTX of the cell. The one or more serving cell configuration parameters may comprise one or more cell DRX configuration parameters (e.g., celldrx-Config) used to configure and/or indicate a cell DRX of the cell.
A cell DTX may be activated implicitly once configured by the base station. The cell DTX may be activated implicitly once configured by the base station, for example, based on sending (e.g., transmitting) the one or more cell DTX configuration parameters. The cell DTX may be activated implicitly by the wireless device once configured by the base station, for example, based on receiving the one or more cell DTX configuration parameters. The one or more cell DTX configuration parameters may indicate an on-duration timer (e.g., celldtx-onDurationTimer) for the cell DTX. The one or more cell DTX configuration parameters may indicate an offset for a cycle start of the cell DTX (e.g., celldtx-CycleStartOffset). The one or more cell DTX configuration parameters may indicate a slot offset (e.g., celldtx-SlotOffset) for the cell DTX. The one or more cell DTX configuration parameters may comprise a joint cell DTX-DRX configuration parameter (e.g., jointCellDTXDRXconfig). The wireless device may use the one or more cell DTX configuration parameters to a cell DRX, for example, if the joint cell DTX-DRX configuration parameter is set to true. The wireless device may use a cell DRX configuration with the same parameters as in CellDTX-Config, for example, if the joint cell DTX-DRX configuration parameter is set to true. The cell DTX may be deactivated by the wireless device, for example, based on releasing the one or more cell DTX configuration parameters.
A cell DRX may be activated implicitly once configured by a base station. The cell DRX may be activated implicitly once configured by the base station, for example, based on sending (e.g., transmitting) the one or more cell DRX configuration parameters. The cell DRX may be activated implicitly by the wireless device once configured by the base station, for example, based on receiving the one or more cell DRX configuration parameters. The one or more cell DRX configuration parameters may indicate an on-duration timer (e.g., celldrx-onDurationTimer) for the cell DRX. The one or more cell DRX configuration parameters may indicate an offset for a cycle start of the cell DRX (e.g., celldrx-CycleStartOffset). The one or more cell DRX configuration parameters may indicate a slot offset (e.g., celldrx-SlotOffset) for the cell DRX. The cell DRX may be deactivated by the wireless device, for example, based on releasing the one or more cell DRX configuration parameters.
An offset for a cycle start may be common between a cell DTX and a cell DRX. The offset for a cycle start may be common between the cell DTX and the cell DRX, for example, if the one or more configuration parameters comprise both the one or more cell DTX configuration parameters and the one or more cell DRX configuration parameters. The offset for the cycle start of the cell DRX may be signaled in the one or more cell DTX configuration parameters. The offset for the cycle start of the cell DTX may indicate the offset for the cycle start of the cell DRX, for example, if the joint cell DTX-DRX configuration parameter is set to true. The offset for the cycle start of the cell DTX may be the offset for the cycle start of both the cell DTX and the cell DRX, for example, if the joint cell DTX-DRX configuration parameter is set to true.
An on-duration timer may be common between a cell DTX and a cell DRX. The on-duration timer may be common between the cell DTX and the cell DRX, for example, if the one or more configuration parameters comprise both the one or more cell DTX configuration parameters and the one or more cell DRX configuration parameters. The on-duration timer of the cell DRX may be signaled in the one or more cell DTX configuration parameters. The on-duration timer of the cell DTX may indicate the on-duration timer of the cell DRX, for example, if the joint cell DTX-DRX configuration parameter is set to true. The on-duration timer of the cell DTX may be the on-duration timer of both the cell DTX and the cell DRX, for example, if the joint cell DTX-DRX configuration parameter is set to true.
A slot offset may be common between a cell DTX and a cell DRX. The slot offset may be common between the cell DTX and the cell DRX, for example, if the one or more configuration parameters comprise both the one or more cell DTX configuration parameters and the one or more cell DRX configuration parameters. The slot offset of the cell DRX may be signaled in the one or more cell DTX configuration parameters. The slot offset of the cell DTX may indicate the slot offset of the cell DRX, for example, if the joint cell DTX-DRX configuration parameter is set to true. The slot offset of the cell DTX may be the slot offset of both the cell DTX and the cell DRX, for example, if the joint cell DTX-DRX configuration parameter is set to true.
To facilitate reducing downlink transmission or uplink reception activity time of a base station (e.g., gNB), a wireless device may be configured, by the base station, with a cell DTX and/or DRX of a cell (e.g., by CellDTX-Config, CellDRX-Config). The cell DTX and/or DRX of the cell may have a periodic cell DTX and/or DRX pattern (i.e., active and non-active periods). The periodic cell DTX and/or DRX pattern may be common for one or more wireless devices, that are configured with a cell DTX and/or DRX, in the cell. The periodic cell DTX pattern and the periodic cell DRX pattern may be configured and/or activated separately. The wireless device may not monitor PDCCH or SPS occasions, for example, if the cell DTX is configured and activated for the cell and if the wireless device is in a non-active duration of the cell DTX, unless there is a pending retransmission, or unless a 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. The wireless device may not send (e.g., transmit) on/via configured grant (CG) resources or may not send (e.g., transmit) an SR, for example, if the cell DRX is configured and activated for the cell and if the wireless device is in a non-active duration of the cell DRX. A cell DTX and/or DRX may be only applicable to wireless devices in an RRC_CONNECTED state. The cell DTX and/or DRX may not impact at least: Random Access procedure, SSB transmission, paging, and system information broadcasting.
A cell DTX and/or DRX may be activated or deactivated by RRC signaling or layer 1 (L1) group common signaling (e.g., DCI). one or more configuration parameters may comprise a parameter indicating whether activation or deactivation of the cell DTX and/or DRX is based on the RRC signaling or the L1 group common signaling. A base station and/or the wireless device may activate or deactivate the cell DTX and/or DRX based on the RRC signaling, for example, if the parameter is set to a first value (e.g., 0, ‘RRC’). The wireless device may activate the cell DTX and/or DRX based on receiving the RRC signaling (e.g., CellDTX-Config, CellDRX-Config). The base station and/or the wireless device may activate or deactivate the cell DTX and/or DRX based on the L1 group common signaling, for example, if the parameter is set to a second value (e.g., 1, ‘DCI’, or ‘L1’). The wireless device may activate the cell DTX and/or DRX based on receiving DCI (e.g., DCI format 2_9). The wireless device may not activate the cell DTX and/or DRX based on receiving the RRC signaling (e.g., CellDTX-Config, CellDRX-Config), for example, if the parameter is set to the second value. The wireless device may not activate the cell DTX and/or DRX until receiving the DCI (e.g., DCI format 2_9), for example, if the parameter is set to the second value.
A cell DTX and/or DRX may be characterized by an active duration and/or a cycle. Active duration may be a duration that a wireless device may wait for and/or monitor to receive PDCCHs or SPS occasions and send (e.g., transmit) SR or CG. The transmission and/or reception of PDCCH, SPS, SR and CG by a base station may not be impacted for the purpose of network energy saving in the active duration. Cycle may specify the periodic repetition of the active duration followed by a period of non-active duration. The active duration and/or cycle parameters may be common between a cell DTX and a cell DRX, if both the cell DTX and the cell DRX are configured.
A network may ensure that there is no impact to the emergency call or public safety related service (e.g., the base station may release or deactivate the cell DTX and/or DRX) once the base station recognizes there is an emergency call or public safety related service (e.g., MPS or MCS). The base station may ensure that there may be at least partial overlapping between an on-duration of a connected mode DRX of the wireless device and an active duration of a cell DTX and/or DRX (e.g., a periodicity of the connected mode DRX of the wireless device is a multiple of a periodicity of the cell DTX and/or DRX).
A wireless device may receive the downlink reception regardless of the downlink reception overlapping (e.g., being in, within, in, etc.) an active time, period, and/or duration or a non-active time, period, and/or duration of the cell DTX if in the cell DTX and if the wireless device receives DCI scheduling a downlink reception (e.g., PDSCH, aperiodic CSI-RS). The DCI may comprise a dynamic grant for the downlink reception. The wireless device may send (e.g., transmit) a HARQ-ACK information feedback of the downlink reception regardless of the transmission of the HARQ-ACK information overlapping (e.g., being in, within, in, etc.) an active time, period, and/or duration or a non-active time, period, and/or duration of the cell DRX, for example, after the downlink reception.
A wireless device may send (e.g., transmit) the uplink transmission regardless of the uplink transmission overlapping (e.g., being in, within, in, etc.) an active time, period, and/or duration or a non-active time, period, and/or duration of the cell DRX if in the cell DRX and if the wireless device receives DCI scheduling an uplink transmission (e.g., PUSCH, PUCCH, aperiodic SRS). The DCI may comprise a dynamic grant for the uplink transmission. The wireless device may receive a PDCCH reception (e.g., DCI, a response to/of the uplink transmission) from the base station regardless of the transmission of the PDCCH reception overlapping (e.g., being in, within, in, etc.) an active time, period, and/or duration or a non-active time, period, and/or duration of the cell DTX, for example, after the uplink transmission. The wireless device may monitor PDCCH for DCI (or for a response to/of the uplink transmission) from the base station regardless of the transmission of the PDCCH with the DCI overlapping (e.g., being in, within, in, etc.) an active time, period, and/or duration or a non-active time, period, and/or duration of the cell DTX, for example, after the uplink transmission.
A non-active time, period, and/or duration of a cell DTX may comprise a time outside an active time, period, and/or duration of the cell DTX. A non-active time, period, and/or duration of the cell DRX may comprise the time outside an active time, period, and/or duration of the cell DRX.
A wireless device may receive, from a base station, one or more messages (e.g., RRC message(s)). The one or more messages may configure and/or indicate a periodic cell DTX and/or a cell DRX pattern (i.e., an active period and a non-active period) for a cell DTX and/or a cell DRX of a cell (e.g., a serving cell, a non-serving cell, a candidate cell, a target cell, etc.).
A cell DTX, or a cell DTX functionality, may control monitoring activity of PDCCH and configured downlink assignments (e.g., SPS PDSCH) by the wireless device in an RRC_CONNECTED mode. The wireless device may monitor PDCCH and configured downlink assignments via the cell using the cell DTX, or a cell DTX operation, for the cell configured and activated with the cell DTX.
A wireless device may monitor PDCCH and configured downlink assignments using the cell DTX, or a cell DTX operation, for all activated cells (e.g., activated serving cells) configured with a cell DTX. A wireless device may monitor PDCCH and configured downlink assignments using the cell DTX, or a cell DTX operation, for each activated cell (e.g., each activated serving cell) configured and activated with cell DTX.
A cell DRX, or a cell DRX functionality, may control transmission activity of scheduling request (SR) and configured uplink grant by the wireless device in an RRC_CONNECTED. A wireless device may send (e.g., transmit) scheduling request and configured uplink grant via the cell using the cell DRX, or a cell DRX operation for the cell configured and activated with the cell DRX. The wireless device may send (e.g., transmit) scheduling request and configured uplink grant using the cell DRX (or a cell DRX operation) For all activated cells (e.g., activated serving cells) configured with a cell DRX. The wireless device may send (e.g., transmit) scheduling request and configured uplink grant using the cell DRX, or a cell DRX operation, for each activated cell (e.g., each activated serving cell) configured and activated with cell DRX.
One or more messages (e.g., the RRC message(s)) may control a cell DTX, or the cell DTX operation, by configuring, indicating, and/or comprising the following parameters in one or more cell DTX configuration parameters (e.g., CellDTX-Config): celldtx-onDurationTimer: an active duration at the beginning of a cycle of the cell DTX, or a cell DTX cycle; celldtx-StartOffset: defines the subframe where the cycle of the cell DTX, or the cell DTX cycle, starts; celldtx-SlotOffset: the delay before starting the on-duration timer of the cell DTX (e.g., celldtx-onDurationTimer); celldtx-Cycle: the period of the cycle of the cell DTX, or a cell DTX cycle period.
One or more messages (e.g., the RRC message(s)) may control a cell DRX, or the cell DRX operation, by configuring, indicating, and/or comprising the following parameters in the one or more cell DRX configuration parameters (e.g., CellDRX-Config): celldrx-onDurationTimer: an active duration at the beginning of a cycle of the cell DRX, or a cell DRX cycle; celldrx-StartOffset: defines the subframe where the cycle of a cell DRX, or the cell DRX cycle, starts; celldrx-SlotOffset: a delay before starting an on-duration timer of a cell DRX (e.g., celldrx-onDurationTimer); celldrx-Cycle: a period of a cycle of a cell DRX, or a cell DRX cycle period.
An active time, period, and/or duration, or a cell DTX active time, period, and/or duration, of a cell DTX may comprise a time, if one or more configuration parameters comprise one or more cell DTX configuration parameters (e.g., CellDTX-Config) indicating and/or configuring a cell DTX of a cell (e.g., a serving cell), if celldtx-onDuration Timer is running for the cell, or if a cell DTX deactivation indication (e.g., DCI format 2_9 or RRC signaling) has been received, by the wireless device, for the cell.
An active time, period, and/or duration (or a cell DRX active time, period, and/or duration) of a cell DRX may comprise a time, if one or more configuration parameters comprise one or more cell DRX configuration parameters (e.g., CellDRX-Config) indicating and/or configuring a cell DRX of a cell (e.g., a serving cell), if celldrx-onDurationTimer is running for the cell, or if a cell DRX deactivation indication (e.g., DCI format 2_9 or RRC signaling) has been received, by the wireless device, for the cell.
A wireless device may start an on-duration timer (e.g., celldtx-onDurationTimer) for a cell after a slot offset (e.g., celldtx-SlotOffset) from a beginning of a subframe based on receiving a cell DTX activation indication (e.g., by DCI format 2_9 or by RRC signaling) for the cell DTX of the cell.
A wireless device may start an on-duration timer (e.g., celldtx-onDurationTimer) for a cell after a slot offset (e.g., celldtx-SlotOffset) from a beginning of a subframe based on receiving an indication (e.g., by DCI format 2_9 or by RRC signaling) indicating activation of the cell DTX of the cell.
A wireless device may stop an on-duration timer (e.g., celldtx-onDurationTimer) based on receiving a cell DTX deactivation indication (e.g., by DCI format 2_9 or by RRC signaling) for the cell DTX of a cell, if running.
A wireless device may stop an on-duration timer (e.g., celldtx-onDurationTimer) based on receiving an indication (e.g., by DCI format 2_9 or by RRC signaling) indicating deactivation of the cell DTX of the cell, if running.
A wireless device may start an on-duration timer (e.g., celldrx-onDurationTimer) for a cell after a slot offset (e.g., celldrx-SlotOffset) from a beginning of a subframe based on receiving a cell DRX activation indication (e.g., by DCI format 2_9 or by RRC signaling) for the cell DRX of the cell.
A wireless device may start an on-duration timer (e.g., celldrx-onDurationTimer) for a cell after a slot offset (e.g., celldrx-SlotOffset) from a beginning of a subframe based on receiving an indication (e.g., by DCI format 2_9 or by RRC signaling) indicating activation of a cell DRX of the cell.
A wireless device may stop an on-duration timer (e.g., celldrx-onDurationTimer) based on receiving a cell DRX deactivation indication (e.g., by DCI format 2_9 or by RRC signaling) for the cell DRX of the cell, if running.
A wireless device may stop an on-duration timer (e.g., celldrx-onDurationTimer) based on receiving an indication (e.g., by DCI format 2_9 or by RRC signaling) indicating deactivation of a cell DRX of the cell, if running.
A MAC layer and/or entity of the wireless device may not instruct a physical layer and/or entity of the wireless device to receive a transport block on a DL-SCH according to, or for, a configured downlink assignment (e.g., SPS) if the cell is not in an active time, period, and/or duration of the cell DTX, or if the cell is not in the cell DTX active period, or if the cell is in a non-active time, period, and/or duration of the cell DTX.
A MAC layer and/or entity of a wireless device may instruct a physical layer and/or entity of the wireless device to receive a transport block on a DL-SCH according to, or for, a configured downlink assignment (e.g., SPS) if the cell is in an active time, period, and/or duration of the cell DTX, or if the cell is in the cell DTX active period or if the cell is not in a non-active time, period, and/or duration of the cell DTX.
A MAC layer and/or entity of a wireless device may not indicate a presence of any configured downlink assignment and may not deliver a stored HARQ information to a HARQ entity if the cell is not in an active time, period, and/or duration of the cell DTX, or if the cell is not in the cell DTX active period or if the cell is in a non-active time, period, and/or duration of the cell DTX.
A MAC layer and/or entity of a wireless device may indicate a presence of a configured downlink assignment and may deliver a stored HARQ information to a HARQ entity if the cell is in an active time, period, and/or duration of the cell DTX, or if the cell is in the cell DTX active period or if the cell is not in a non-active time, period, and/or duration of the cell DTX.
A wireless device may not monitor PDCCH for an RNTI if a cell is not in an active time, period, and/or duration of a cell DTX, or if the cell is not in the cell DTX active period or if the cell is in a non-active time, period, and/or duration of the cell DTX. The wireless device may not monitor PDCCH for DCI scrambled with the RNTI. The RNTI may comprise, for example, at least one of: C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SLCS-RNTI and SL Semi-Persistent Scheduling V-RNTI.
A wireless device may monitor PDCCH for a RNTI if drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or drx-RetransmissionTimerSL is running on at least one cell in the DRX group, and if a cell in a DRX group is not in an active time, period, and/or duration of the cell DTX, if the cell is not in the cell DTX active period, or if the cell is in a non-active time, period, and/or duration of the cell DTX.
A wireless device may not monitor PDCCH for a RNTI if drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or drx-RetransmissionTimerSL is not running on any cell in the DRX group, and if a cell in a DRX group is not in an active time, period, and/or duration of the cell DTX, if the cell is not in the cell DTX active period, or if the cell is in a non-active time, period, and/or duration of the cell DTX.
A wireless device may monitor PDCCH for a RNTI if ra-ContentionResolutionTimer, or ra-ResponseWindow, or msgB-ResponseWindow is running, and if a cell is not in an active time, period, and/or duration of the cell DTX, if the cell is not in the cell DTX active period, or if the cell is in a non-active time, period, and/or duration of the cell DTX).
A wireless device may not monitor PDCCH for a RNTI if ra-ContentionResolutionTimer, and ra-ResponseWindow, and msgB-ResponseWindow is not running, and if a cell is not in an active time, period, and/or duration of the cell DTX, or if the cell is not in the cell DTX active period or if the cell is in a non-active time, period, and/or duration of the cell DTX.
A wireless device may monitor PDCCH for a RNTI based on sending (e.g., transmitting) a scheduling request (e.g., on PUCCH) and/or the scheduling request being pending, if a cell is not in an active time, period, and/or duration of the cell DTX, if the cell is not in the cell DTX active period, or if the cell is in a non-active time, period, and/or duration of the cell DTX.
A wireless device may monitor PDCCH for a RNTI if a scheduling request is sent (e.g., on PUCCH) by the wireless device and/or the scheduling request is pending, if the cell is not in an active time, period, and/or duration of the cell DTX, if the cell is not in the cell DTX active period, or if the cell is in a non-active time, period, and/or duration of the cell DTX.
A wireless device may not monitor PDCCH for a RNTI based on not sending (e.g., transmitting) a scheduling request (e.g., on PUCCH) and/or the scheduling request not being pending, if the cell is not in an active time, period, and/or duration of the cell DTX (or if the cell is not in the cell DTX active period or if the cell is in a non-active time, period, and/or duration of the cell DTX).
A wireless device may not monitor PDCCH for a RNTI if a scheduling request is not sent (e.g., transmitted) (e.g., on PUCCH) by the wireless device and/or the scheduling request is not pending, if the cell is not in an active time, period, and/or duration of the cell DTX, if the cell is not in the cell DTX active period or if the cell is in a non-active time, period, and/or duration of the cell DTX.
A wireless device may monitor PDCCH for a RNTI based on not receiving, after a successful reception of a random-access response of/for a contention-free random-access procedure, DCI indicating a new transmission addressed to the C-RNTI of the wireless device, or the MAC entity of the wireless device, if the cell is not in an active time, period, and/or duration of the cell DTX, if the cell is not in the cell DTX active period, or if the cell is in a non-active time, period, and/or duration of the cell DTX. The wireless device may not select, for the contention-free random-access procedure, a random-access preamble among one or more random-access preambles used and/or configured for a contention-based random-access procedure.
A wireless device may not monitor PDCCH for a RNTI based on receiving, after a successful reception of a random-access response of/for a contention-free random-access procedure, DCI indicating a new transmission addressed to the C-RNTI of the wireless device, or the MAC entity of the wireless device, if the cell is not in an active time, period, and/or duration of the cell DTX, if the cell is not in the cell DTX active period, or if the cell is in a non-active time, period, and/or duration of the cell DTX. The wireless device may not select, for the contention-free random-access procedure, a random-access preamble among one or more random-access preambles used and/or configured for a contention-based random-access procedure.
A MAC layer and/or entity of a wireless device may not instruct a physical layer and/or entity of the wireless device to send (e.g., transmit) a scheduling request on a PUCCH resource if the cell is not in an active time, period, and/or duration of the cell DRX, if the cell is not in the cell DRX active period, or if the cell is in a non-active time, period, and/or duration of the cell DRX.
A MAC layer and/or entity of a wireless device may instruct a physical layer and/or entity of the wireless device to send (e.g., transmit) a scheduling request on a PUCCH resource if the cell is in an active time, period, and/or duration of the cell DRX, if the cell is in the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX.
A wireless device may not increment an SR counter for a pending SR if a cell is not in an active time, period, and/or duration of the cell DRX, if the cell is not in the cell DRX active period, or if the cell is in a non-active time, period, and/or duration of the cell DRX.
A wireless device may increment an SR counter for a pending SR, for example, based on sending (e.g., transmitting) an SR, if a cell is in an active time, period, and/or duration of the cell DRX, if the cell is in the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX.
A wireless device may not start an sr-ProhibitTimer for a pending SR if a cell is not in an active time, period, and/or duration of the cell DRX, if the cell is not in the cell DRX active period, or if the cell is in a non-active time, period, and/or duration of the cell DRX.
A wireless device may start an sr-ProhibitTimer for a pending SR, for example, based on sending (e.g., transmitting) an SR, if the cell is in an active time, period, and/or duration of the cell DRX, if the cell is in the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX.
If the cell is not in an active time, period, and/or duration of the cell DRX, if the cell is in the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX, a MAC layer and/or entity of the wireless device may not deliver any configured uplink grant and an associated HARQ information to a HARQ entity.
A MAC layer and/or entity of a wireless device may deliver a configured uplink grant and an associated HARQ information to a HARQ entity if a cell is in an active time, period, and/or duration of the cell DRX, if the cell is in the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX.
A MAC layer and/or entity of a wireless device may not obtain, from a multiplexing and assembly entity, a MAC PDU to send (e.g., transmit) for a configured uplink grant if the cell is not in an active time, period, and/or duration of a cell DRX, if the cell is in the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX.
A MAC layer and/or entity of the wireless device may obtain, from a multiplexing and assembly entity, a MAC PDU to send (e.g., transmit) for a configured uplink grant if the cell is in an active time, period, and/or duration of the cell DRX, if the cell is in the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX.
A MAC layer and/or entity of the wireless device may not instruct a HARQ process associated with a configured uplink grant to trigger a new transmission or a retransmission if the cell is not in an active time, period, and/or duration of the cell DRX, if the cell is not in the cell DRX active period, or if the cell is in a non-active time, period, and/or duration of the cell DRX.
A MAC layer and/or entity of a wireless device may instruct a HARQ process associated with a configured uplink grant to trigger a new transmission or a retransmission if a cell is in an active time, period, and/or duration of the cell, if the cell is in the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX.
A wireless device may not start or restart a configuredGrantTimer, if configured, and if a cell is not in an active time, period, and/or duration of the cell DRX, if the cell is not in the cell DRX active period, or if the cell is in a non-active time, period, and/or duration of the cell DRX. The wireless device may start or restart a configuredGrantTimer, if configured, and if the cell is in an active time, period, and/or duration of the cell DRX, if the cell is in the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX. The wireless device may not start or restart a cg-RetransmissionTimer, if configured, and if the cell is not in an active time, period, and/or duration of the cell DRX, if the cell is in the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX. The wireless device may start or restart a 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 the cell DRX active period, or if the cell is not in a non-active time, period, and/or duration of the cell DRX.
A wireless device configured (e.g., celldtx-Config) and activated with the cell DTX may not expect to receive a periodic CSI-RS and/or a semi-persistent CSI-RS configured in a CSI report configuration (e.g., in CSI-ReportConfig) associated with a higher layer parameter reportQuantity comprising at least rank indicator (RI) if in a non-active time, period, and/or duration of the cell DTX. A base station may not send (e.g., transmit), to a wireless device configured (e.g., celldtx-Config) and activated with the cell DTX, a periodic CSI-RS and/or a semi-persistent CSI-RS configured in a CSI report configuration (e.g., in CSI-ReportConfig) associated with a higher layer parameter reportQuantity comprising at least rank indicator (RI) if in a non-active time, period, and/or duration of the cell DTX.
A wireless device configured (e.g., celldtx-Config) and activated with the cell DTX may expect to receive a periodic CSI-RS and/or a semi-persistent CSI-RS configured in a CSI report configuration (e.g., in CSI-ReportConfig) associated with a higher layer parameter reportQuantity comprising at least rank indicator (RI) if in an active time, period, and/or duration of the cell DTX. A base station may send (e.g., transmit), to a wireless device configured (e.g., celldtx-Config) and activated with the cell DTX, a periodic CSI-RS and/or a semi-persistent CSI-RS configured in a CSI report configuration (e.g., in CSI-ReportConfig) associated with a higher layer parameter reportQuantity comprising at least rank indicator (RI) if in an active time, period, and/or duration of the cell DTX.
A wireless device configured (e.g., celldrx-Config) and activated with the cell DRX may not expect to send (e.g., transmit) a periodic SRS and/or a semi-persistent SRS for channel acquisition if in a non-active time, period, and/or duration of the cell DRX. The wireless device configured (e.g., celldrx-Config) and activated with the cell DRX may send (e.g., transmit) an SRS for positioning. SRS transmission for positioning may not be impacted by the cell DRX, or the cell DRX operation, if in a non-active time, period, and/or duration of the cell DRX.
A base station may not receive, from a wireless device configured (e.g., celldrx-Config) and activated with a cell DRX, a periodic SRS or a semi-persistent SRS for channel acquisition if in a non-active time, period, and/or duration of the cell DRX. The base station may receive, from the wireless device configured (e.g., celldrx-Config) and activated with the cell DRX, an SRS for positioning if in a non-active time, period, and/or duration of the cell DRX. SRS transmission for positioning may not be impacted by the cell DRX, or the cell DRX operation.
A wireless device configured (e.g., celldrx-Config) and activated with a cell DRX may expect to send (e.g., transmit) a periodic SRS and/or a semi-persistent SRS for channel acquisition if in an active time, period, and/or duration of the cell DRX. A base station may receive, from the wireless device configured (e.g., celldrx-Config) and activated with the cell DRX, a periodic SRS or a semi-persistent SRS for channel acquisition if in an active time, period, and/or duration of the cell DRX.
A wireless device configured for operation on a cell according to one or both of a cell DTX operation by cellDTXConfig and a cell DRX operation by cellDRXConfig for a cell may be additionally provided by dci-Format2-9 a search space set to monitor PDCCH for detection of DCI format 2_9 according to a common search space, and a location in the DCI format 29 by position-inDCI-NES of a cell DTX and/or DRX for the cell.
One or more configuration parameters may comprise a parameter (e.g., dci-Format2-9) indicating a search space set (e.g., a common search space set) to monitor PDCCH for detection of DCI format (e.g., DCI format 2_9). The one or more configuration parameters may comprise a location parameter (e.g., position-inDCI-NES) indicating a location of a cell DTX and/or DRX for the cell in the DCI format (e.g., the DCI format 2_9).
A cell DTX and/or DRX may comprise two bits if a wireless device is configured with both the cell DTX operation (e.g., by cellDTXConfig) and the cell DRX operation (e.g., by cellDRXConfig) for the cell. The first bit of the two bits may indicate the cell DTX operation and the second bit of the two bits may indicate the cell DRX operation.
A cell DTX and/or DRX may comprise one bit indicating one of a cell DTX operation and the cell DRX operation, respectively, for the cell if a wireless device is configured with only one of the cell DTX operation (e.g., by cellDTXConfig) and the cell DRX operation (e.g., by cellDRXConfig) for the cell.
A first value (e.g., ‘0’) for a bit of a cell DTX and/or DRX may indicate deactivation of the cell DTX or of the cell DRX. A second value (e.g., ‘1’) for a bit of a cell DTX and/or DRX may indicate activation of the cell DTX or of the cell DRX.
A cell DTX/DRX indication for activation or deactivation of a cell DRX may use to both a UL carrier and a SUL carrier if the cell is configured with an SUL carrier, in addition to an UL carrier (e.g., NUL).
A wireless device may not expect to monitor PDCCH for detection of the DCI format 2_9 on more than one cell (e.g., more than one serving cells). The wireless device may operate on a second cell according to an indicated cell DTX operation or an indicated cell DRX operation starting from a slot on an active downlink BWP or on an active uplink BWP of the second cell, respectively, that may not be before the beginning of the slot m+d on the active downlink BWP of the first cell, where d is a number of slots determined based on a subcarrier spacing (SCS) of the active downlink BWP of the first cell, if a wireless device receives, in slot m on an active downlink BWP of a first cell (e.g., a first serving cell), a PDCCH providing/with DCI format 2_9 that indicates a change in activation or deactivation of a current cell DTX operation or a current cell DRX operation for a second cell (e.g., a second serving cell). The number of slots is equal to 3, for example, if the SCS of the active downlink BWP is 15 kHz. The number of slots is equal to 6, for example, if the SCS of the active downlink BWP is 30 kHz.
Outside of an active time, period, and/or duration (e.g., a DTX active time, period, and/or duration) a wireless device may not receive, via a cell, if in and/or of the cell DTX of the cell, PDCCH candidates for search space sets associated with detection of DCI format (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 CSI-RS in resources provided by CSI-ReportConfig with reportQuantity that includes rank indication.
Outside of an active time, period, and/or duration (e.g., a DRX active time, period, and/or duration) the wireless device may not send (e.g., transmit), via a cell, if in and/or of the cell DRX of the cell, periodic or semi-persistent PUCCH or PUSCH (e.g., CSI report, configured uplink grant), and/or periodic or semi-persistent SRS except for SRS in resources provided by SRS-posResourceSet.
A cell DTX may be, or may be interchangeably used with, a cell DTX operation. A cell DRX may be, or may be interchangeably used with, a cell DRX operation.
A DCI format 2_9 may be used for activating or deactivating a cell DTX and/or DRX, or a cell DTX and/or DRX configuration or a cell DTX and/or DRX operation, of one or more cells (e.g., one or multiple serving cells) for one or more wireless devices.
Information may be sent (e.g., transmitted) by means of DCI format 2_9 with CRC scrambled by a NES-RNTI. The information may comprise block number 1, block number 2, . . . , block number N. A starting position of a block may be determined, by the wireless device and/or the base station, by a position parameter (e.g., positionInDCI-cellDTRX). The one or more configuration parameters may comprise the position parameter.
One or more blocks may be configured for a wireless device by higher layers. The one or more blocks may be configured for a wireless device by higher layers, for example, if the wireless device is configured with a DTX and/or DRX parameter (e.g., NES-RNTI, cellDTRX-DCI-config). A field may be defined for each block cell DTX/DRX indication. 2 bits, for example, if cellDTXConfig and cellDTXConfig are both configured for a cell, with the most-significant bit (MSB) corresponding to a cell DTX (or a cell DTX configuration) of the cell and the least significant bit (LSB) corresponding to a cell DRX (or a cell DRX configuration) of the cell; 1 bit, for example, if either cellDTXConfig or cellDTXConfig is configured for a cell. The one or more configuration parameters may comprise the DTX and/or DRX parameter.
A size of DCI format 2_9 may be indicated by a higher layer parameter sizeDCI-2-9. The one or more configuration parameters may comprise the higher layer parameter sizeDCI-2-9. A number of information bits in the DCI format 2_9 may be equal to or less than a payload size of the DCI format 2_9. The remaining bits may be reserved, for example, if the number of information bits in the DCI format 2_9 is less than a size of the DCI format 2_9.
A wireless device may be configured with a list of TCI states (e.g., TCI-State) within and/or by a higher layer parameter PDSCH-Config to decode PDSCH according to a detected PDCCH with DCI intended for the wireless device and a given cell (e.g., a given serving cell, a given non-serving/candidate/target cell, etc.). A number of TCI states in the list may depend on a wireless device capability parameter maxNumberConfiguredTCIstatesPerCC. Each TCI state (e.g., TCI-State) may comprise and/or indicate respective parameters for configuring a quasi co-location relationship between one or two downlink reference signals and DM-RS port(s) of a PDSCH, a DM-RS port of a PDCCH, or CSI-RS port(s) of a CSI-RS resource. The quasi co-location relationship may be configured by a higher layer parameter qcl-Type1 for a first downlink reference signal of the one or more downlink reference signals. The quasi co-location relationship may be configured by a higher layer parameter qcl-Type2 for a second downlink reference signal of the one or more downlink reference signals. QCL types of the two downlink reference signals may not be the same, regardless of whether the first downlink reference signal and the second downlink reference signal are the same or different if two downlink reference signals comprising a first downlink reference signal and a second downlink reference signal are indicated by a TCI state. A quasi co-location type corresponding to a downlink reference signal of the one or more downlink reference signals may be given by a higher layer parameter qcl-Type in a higher layer parameter QCL-Info and may 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}.
A wireless device may be configured with a list of TCI states (e.g., up to 128 TCI-State configurations) within and/or by a higher layer parameter dl-OrJointTCI-StateList in PDSCH-Config. A TCI state in the list of TCI states may provide and/or indicate a reference signal for a quasi co-location for i) DM-RS of a PDSCH, ii) DM-RS of a PDCCH in a BWP/cell, and/or iii) a CSI-RS. A TCI state in the list of TCI states may provide and/or indicate a reference signals for determining uplink transmission spatial filter for i) a dynamic-grant PUSCH, ii) a configured-grant based PUSCH, iii) a PUCCH resource in a BWP/cell, and/or, iv) an SRS.
In step 1760 of
A wireless device 1) configured with dl-OrJointTCI-StateListby one or more configuration parameters (e.g., RRC messages/parameters) and activated with TCI-State by the activation command, or 2) configured with ul-TCI-StateList by one or more configuration parameters (e.g., RRC messages/parameters) and activated with TCI-UL-State by the activation command may receive DCI format (e.g., DCI format 1_1/1_2) providing (e.g., indicating) TCI state(s) (e.g., TCI-State(s) and/or TCI-UL-State(s)) for a cell or all cells in the same cell list configured by a simultaneous TCI update parameter (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4). The DCI format may be with or without a downlink assignment if tci-PresentInDCI is set as ‘enabled’ or tci-PresentDCI-1-2 is configured for a CORESET. The simultaneous TCI update parameter may be a higher layer parameter (e.g., RRC parameter).
Indicated TCI-State(s) may be used, by a wireless device, starting from a first (e.g., starting, earliest, etc.) slot that may be at least a number of symbols (e.g., beamAppTime symbols) after the last symbol of the uplink transmission, if a wireless device configured with dl-OrJointTCI-StateList by one or more configuration parameters (e.g., RRC messages/parameters) sends (e.g., transmits) an uplink transmission (e.g., a PUCCH transmission, a PUSCH transmission) with a positive HARQ-ACK corresponding to the DCI format indicating the indicated TCI state(s) (e.g., TCI-State(s) and/or TCI-UL-State(s)), and if the indicated TCI State(s) is/are different from the previously indicated TCI state(s). The first (e.g., starting, earliest, etc.) slot and the number of symbols may be both determined, by the wireless device, based on an active BWP with the smallest subcarrier spacing among BWP(s) of the cells using the indicated TCI-State(s) that are active at the end of the uplink transmission carrying the positive HARQ-ACK. The number of symbols may be provided (e.g., indicated) to the wireless device by RRC messages (e.g., one or more configuration parameters).
A wireless device may be configured by higher layer parameters (e.g., cjtSchemePDSCH and dl-OrJointTCI-StateList), and the wireless device may be indicated with two TCI states used for a PDSCH reception and/or may report support for two joint TCI states for PDSCH-CJT. A wireless device may presume that PDSCH DM-RS port(s) of the PDSCH reception may be quasi co-located (QCL-ed) with downlink reference signals of both of two indicated TCI states with respect to QCL-TypeA. The wireless device may make this presumption, for example, if the wireless device is configured with a higher layer parameter cjtSchemeA, if the wireless device is configured by higher layer parameters cjtSchemePDSCH and dl-OrJointTCI-StateList, and if the wireless device is indicated with two TCI states used for a PDSCH reception and/or reports support for two joint TCI states for PDSCH-CJT.
Alternatively, the wireless device may presume that PDSCH DM-RS port(s) of the PDSCH reception may be quasi QCL-ed with downlink reference signals of both of the two indicated TCI states with respect to QCL-TypeA except for QCL parameters {Doppler shift, Doppler spread} of a second indicated TCI state (e.g., second joint TCI state) of the two (indicated) TCI states. The wireless device may make this presumption, for example, if the wireless device is configured with a higher layer parameter cjtSchemeB, and if the wireless device is indicated with two TCI states used for a PDSCH reception and/or reports support for two joint TCI states for PDSCH-CJT.
In step 1765 of
The higher layer parameter applyIndicatedTCIState may be one of values={‘first’, ‘second’, ‘both’}. The wireless device may be configured with the higher layer parameter applyIndicatedTCIState with a value set to ‘both’ only if the wireless device is configured with a higher layer parameter cjtSchemePDSCH and/or the wireless device reports support for two joint TCI states for PDSCH-CJT, or if the wireless device is configured with a higher layer parameter sfnSchemePdsch. If the value of the higher layer parameter applyIndicatedTCIState is set to ‘both’, the wireless device may use both of the two indicated TCI states to the PDSCH reception scheduled or activated by the DCI format 1_0 on a search space set other than Type0/0A/2 CSS set on/of a CORESET with index zero (e.g., CORESET #0). The wireless device may receive the DCI format 1_0 via the search space set different from the Type0/0A/2 CSS set associated with the CORESET with index zero. The first indicated TCI-state may be used to PDSCH reception scheduled or activated by DCI format 1_0, if the wireless device is not configured with applyIndicatedTCIState. The wireless device may determine, for the PDSCH reception, indicated TCI state(s) (e.g., indicated joint/DL TCI state(s)) among the two indicated TCI states, if the wireless device is configured with a higher layer parameter tciSelection-PresentInDCI and if the wireless device receives DCI format 1_1/1_2 that schedules or activates a PDSCH reception in/via PDSCH transmission occasions(s).
A wireless device may use a first TCI state of two indicated TCI states to all PDSCH DM-RS port(s) of a PDSCH transmission occasions(s) of a PDSCH reception scheduled or activated by the DCI format 1_1/1_2, if the DCI format 1_1/1_2 indicates codepoint “00” for a TCI selection field. The wireless device may use the second TCI state of the two indicated TCI states to all PDSCH DM-RS port(s) of the PDSCH transmission occasions(s) of the PDSCH reception scheduled or activated by the DCI format 1_1/1_2, if the DCI format 1_1/1_2 indicates codepoint “01” for a TCI selection field. The wireless device may use both of the two indicated TCI states to the PDSCH reception scheduled or activated by the DCI format 1_1/1_2, if the DCI format 1_1/1_2 indicates codepoint “10” for a TCI selection field.
A wireless device may use both of two indicated TCI states to the PDSCH reception scheduled or activated by the DCI format 1_1/1_2, if the wireless device is not configured with a higher layer parameter tciSelection-PresentInDCI and if the wireless device receives DCI format 1_1/1_2 that schedules/activates a PDSCH reception. The wireless device may expect to be configured with a higher layer parameter tciSelection-PresentInDCI if the wireless device does not report/support a capability of using a default beam for SFN (e.g., sfn-DefaultDL-BeamSetup) for DCI format, scheduling a PDSCH reception, without a TCI selection field. The base station may send (e.g., transmit), to the wireless device, one or more configuration parameters (e.g., in RRC message(s)) comprising the higher layer parameter tciSelection-PresentInDCI if the base station does not receive, from the wireless device, a report (e.g., a wireless device capability message) indicating support and/or capability of using a default beam for SFN (e.g., sfn-DefaultDL-BeamSetup) for DCI format, scheduling a PDSCH reception, without a TCI selection field. The base station may or may not send (e.g., transmit), to the wireless device, one or more configuration parameters (e.g., in RRC message(s)) comprising a higher layer parameter tciSelection-PresentInDCI if the base station receives, from the wireless device, a report (e.g., a wireless device capability message) indicating support and/or capability of using a default beam for SFN (e.g., sfn-DefaultDL-BeamSetup) for DCI format, scheduling a PDSCH reception, without a TCI selection field.
The higher layer parameter applyIndicatedTCIState for indicating whether the first TCI state, the second TCI state, or both of the two indicated TCI states is/are used to a PDSCH reception scheduled and/or activated by DCI format 1_0 may be indicated (e.g., provided), to the wireless device, per downlink BWP.
A wireless device may be configured (e.g., provided) with a higher layer parameter applyIndicatedTCIState per, for, and/or to an aperiodic CSI-RS resource set or an aperiodic CSI-RS resource in an aperiodic CSI-RS resource set to inform that the wireless device applies the first TCI state or the second TCI state to the aperiodic CSI-RS resource set or to the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set, if a wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList and is having two indicated TCI states (e.g., two indicated joint/DL TCI states) comprising a first TCI state and a second TCI state. The wireless device may be configured with a higher layer parameter followUnifiedTCIState for the aperiodic CSI-RS resource set for CSI or beam management (BM). A time and/or scheduling offset between the last symbol of a PDCCH carrying/with DCI and a first (e.g., starting, earliest, etc.) symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set triggered by the DCI may be equal to or larger than a threshold (e.g., beamSwitchTiming).
A first TCI state and a second TCI state may correspond to two indicated TCI states specific to a higher layer parameter coresetPoolIndex with value 0 and a higher layer parameter coresetPoolIndex with value 1, respectively, if the wireless device is configured by a higher layer parameter PDCCH-Config that comprises two different values of a higher layer parameter CORESETPoolIndex in different CORESETS (e.g., ControlResourceSets).
A wireless device may use a first TCI state or a second TCI state to an aperiodic CSI-RS via an aperiodic CSI-RS resource based on, or according to, a higher layer parameter applyIndicatedTCIState indicated (e.g., provided) to/for the aperiodic CSI-RS resource or to the aperiodic CSI-RS resource set comprising the aperiodic CSI-RS resource. The wireless device may use the first TCI state or the second TCI state to the aperiodic CSI-RS via the aperiodic CSI-RS resource based on, or according to, a higher layer parameter applyIndicatedTCIState indicated (e.g., provided) to/for the aperiodic CSI-RS resource or to the aperiodic CSI-RS resource set comprising the aperiodic CSI-RS resource, for example, if the wireless device is in frequency range 1 (FR1) or reports a capability of two default beams in frequency range 2 (FR2), there is no downlink signal in the same symbols as the aperiodic CSI-RS resource, if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList and is having two indicated TCI states (e.g., two indicated joint/DL TCI states) comprising the first TCI state and the second TCI state, and if a time and/or scheduling offset between the last symbol of a PDCCH carrying/with DCI and a first (e.g., starting, earliest, etc.) symbol of an aperiodic CSI-RS resource in an aperiodic CSI-RS resource set triggered by the DCI is smaller than a threshold (e.g., beamSwitchTiming).
The wireless device may use the first TCI state to the aperiodic CSI-RS via the aperiodic CSI-RS resource based on, or according to, a higher layer parameter applyIndicatedTCIState indicated (e.g., provided) to/for the aperiodic CSI-RS resource or to the aperiodic CSI-RS resource set comprising the aperiodic CSI-RS resource, for example, if the wireless device is in frequency range 1 (FR1) or reports a capability of two default beams in frequency range 2 (FR2), if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList and is having two indicated TCI states (e.g., two indicated joint/DL TCI states) comprising the first TCI state and the second TCI state, and if a time and/or scheduling offset between the last symbol of a PDCCH carrying/with DCI and a first (e.g., starting, earliest, etc.) symbol of an aperiodic CSI-RS resource in an aperiodic CSI-RS resource set triggered by the DCI is smaller than a threshold (e.g., beamSwitchTiming).
A wireless device may use a first TCI state or a second TCI state to an aperiodic CSI-RS via an aperiodic CSI-RS resource based on (or according to) a higher layer parameter applyIndicatedTCIState indicated (e.g., provided) to/for the aperiodic CSI-RS resource or to the aperiodic CSI-RS resource set comprising the aperiodic CSI-RS resource. The wireless device may use the first TCI state or the second TCI state to the aperiodic CSI-RS via the aperiodic CSI-RS resource based on (or according to) a higher layer parameter applyIndicatedTCIState indicated (e.g., provided) to/for the aperiodic CSI-RS resource or to the aperiodic CSI-RS resource set comprising the aperiodic CSI-RS resource, for example, if a wireless device i) is configured with a higher layer parameter dl-OrJointTCI-StateList, ii) is configured by a higher layer parameter PDCCH-Config that comprises two different values of a higher layer parameter CORESETPoolIndex in different CORESETS (e.g., ControlResourceSets), iii) is having two indicated TCI states (e.g., two indicated joint/DL TCI states) comprising a first TCI state and a second TCI state, and if a time and/or scheduling offset between the last symbol of a PDCCH carrying/with DCI and a first (e.g., starting, earliest, etc.) symbol of an aperiodic CSI-RS resource in an aperiodic CSI-RS resource set triggered by the DCI is smaller than a threshold (e.g., beamSwitchTiming), if there is no downlink signal in the same symbols as the aperiodic CSI-RS resource, and if the wireless device is in frequency range 1 (FR1), or the wireless device reports a capability of default beam per coreset pool index in frequency range 2 (FR2).
Otherwise, the wireless device may use the first TCI state associated with (or specific with or of) a higher layer parameter coresetPoolIndex with value 0 to an aperiodic CSI-RS via the aperiodic CSI-RS resource, for example, if a wireless device i) is configured with a higher layer parameter dl-OrJointTCI-StateList, ii) is configured by a higher layer parameter PDCCH-Config that comprises two different values of a higher layer parameter CORESETPoolIndex in different CORESETS (e.g., ControlResourceSets), iii) is having two indicated TCI states (e.g., two indicated joint/DL TCI states) comprising a first TCI state and a second TCI state, and if a time and/or scheduling offset between the last symbol of a PDCCH carrying/with DCI and a first (e.g., starting, earliest, etc.) symbol of an aperiodic CSI-RS resource in an aperiodic CSI-RS resource set triggered by the DCI is smaller than a threshold (e.g., beamSwitchTiming), if there is a downlink signal in the same symbols as the aperiodic CSI-RS resource, and if the wireless device is in frequency range 1 (FR1), or the wireless device reports a capability of default beam per coreset pool index in frequency range 2 (FR2).
A wireless device may send (e.g., transmit) a capability message (e.g., a wireless device capability message) to a base station. The capability message may comprise a dynamic switching parameter (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2). The dynamic switching parameter may indicate whether the wireless device supports (e.g., capable of) dynamic switching between a single-TRP and a multi-TRP for downlink receptions (e.g., PDSCH receptions, PDCCH receptions, and the like). The dynamic switching parameter may indicate whether the wireless device supports dynamic switching between a single-TRP and a PDSCH SFN scheme (e.g., sfnSchemeA, sfnSchemeB). The dynamic switching parameter may indicate whether the wireless device supports dynamic switching between a non-SFN scheme (e.g., a single-TRP mode/operation/scheme) and a PDSCH SFN scheme (e.g., a multi-TRP mode/operation/scheme) for the downlink receptions. The dynamic switching parameter may indicate whether the wireless device supports dynamic switching between a single TCI state (e.g., one TCI state) and multiple TCI states (e.g., two TCI states) for the downlink receptions.
A wireless device supporting dynamic switching may indicate, in a capability message, an SFN scheme (e.g., sfn-SchemeA) or an SFN scheme for PDSCH receptions only (e.g., sfn-SchemeA-PDSCH-only). A dynamic switching parameter may indicate whether the wireless device supports dynamic switching between a single-TRP and a PDSCH SFN scheme by a TCI state field in DCI formats 1_1 and 1_2. The dynamic switching parameter may indicate whether the wireless device supports dynamic switching between a single-TRP and a PDSCH SFN scheme by a TCI selection field in DCI formats 1_1 and 1_2. The dynamic switching parameter indicating whether the wireless device supports dynamic switching between a single-TRP and a PDSCH SFN scheme by the TCI state field in DCI formats 1_1 and 1_2 and the dynamic switching parameter indicating whether the wireless device supports dynamic switching between a single-TRP and a PDSCH SFN scheme by the TCI selection field in DCI formats 1_1 and 1_2 may be the same. The dynamic switching parameter indicating whether the wireless device supports dynamic switching between a single-TRP and a PDSCH SFN scheme by the TCI state field in DCI formats 1_1 and 1_2 and the dynamic switching parameter indicating whether the wireless device supports dynamic switching between a single-TRP and a PDSCH SFN scheme by the TCI selection field in DCI formats 1_1 and 12 may be different.
A wireless device may not expect to be configured, by a base station, with a higher layer parameter tciSelection-PresentInDCI, if the wireless device does not send (e.g., transmit, report, or indicate) a capability and/or support of the dynamic switching to the base station, or if the capability message does not comprise the dynamic switching parameter. DCI formats 1_1 and 12 may not comprise a TCI selection field, if the wireless device is not configured with a higher layer parameter tciSelection-PresentInDCI.
A wireless device may not expect to be configured, by a base station, with a higher layer parameter tciSelection-PresentInDCI, if the wireless device does not send (e.g., transmit, report, or indicate) a capability and/or support of the dynamic switching to the base station, or if the capability message does not comprise the dynamic switching parameter. The wireless device may not receive DCI format (e.g., DCI format 1_1, DCI format 1_2) with a TCI selection field, if the wireless device is not configured with the higher layer parameter tciSelection-PresentInDCI. The wireless device may receive DCI format (e.g., DCI format 1_1, DCI format 1_2) without a TCI selection field, if the wireless device is not configured with the higher layer parameter tciSelection-PresentInDCI.
A base station may not send (e.g., transmit), to the wireless device, one or more configuration parameters (e.g., in RRC message(s)) comprising a higher layer parameter tciSelection-PresentInDCI, if the wireless device does not send (e.g., transmit, report, or indicate) a capability and/or support of the dynamic switching to the base station, or if the capability message does not comprise the dynamic switching parameter. The base station may not send (e.g., transmit), to the wireless device, DCI format (e.g., DCI format 1_1, DCI format 1_2) with a TCI selection field, if the one or more configuration parameters do not comprise the higher layer parameter tciSelection-PresentInDCI. The base station may send (e.g., transmit), to the wireless device, DCI format (e.g., DCI format 1_1, DCI format 1_2) without a TCI selection field, if the one or more configuration parameters do not comprise the higher layer parameter tciSelection-PresentInDCI. A wireless device may be indicated with one TCI state or two TCI states in a codepoint of DCI field ‘Transmission Configuration Indication’ in DCI format 1_1/1_2, if the wireless device reports a capability of sfn-SchemeA-DynamicSwitching or sfn-SchemeB-DynamicSwitching and if a wireless device is configured with a higher layer parameter sfnSchemePdsch set to either ‘sfnSchemeA’ or ‘sfnSchemeB’.
The wireless device may not expect to be indicated with one TCI state per any of TCI codepoint by the activation command (e.g., MAC CE), and the wireless device may be indicated with two TCI states in a codepoint of DCI field ‘Transmission Configuration Indication’ in DCI format 1_1/1_2.
A cell may be, for example, a serving cell. At least one configuration parameter of the one or more configuration parameters 1815 may be for the cell. The cell may be a primary cell (PCell). The cell may be a primary secondary cell (PSCell). The cell may be a secondary cell (SCell). The cell may be a secondary cell configured with PUCCH (e.g., PUCCH SCell). A cell may be a special Cell (SpCell). The SpCell may refer to (e.g., indicate) the PCell of the MCG or the PSCell of the SCG for dual connectivity (DC) operation; otherwise the SpCell may refer to (e.g., indicate) the PCell. A cell may be a primary SCG cell (PSCell). A wireless device 1805 may perform a random-access procedure via the PSCell if performing the Reconfiguration with Sync procedure, for example, for dual connectivity operation. A cell may be an unlicensed cell, for example, operating in an unlicensed band. The cell may be a licensed cell, for example, operating in a licensed band. The cell may operate in a first frequency range (FR1). The FR1 may, for example, comprise frequency bands below 6 GHz. The cell may operate in a second frequency range (FR2). The FR2 may, for example, comprise frequency bands from 24 GHz to 52.6 GHz. The cell may operate in a third frequency range (FR3). The FR3 may, for example, comprise frequency bands from 52.6 GHz to 71 GHz. The FR3 may, for example, comprise frequency bands starting from (or above) 52.6 GHz.
A wireless device 1805 may perform uplink transmissions (e.g., PUSCH, PUCCH, PUCCH) via a cell in a first time and in a first frequency. The wireless device 1805 may perform downlink receptions (e.g., PDCCH, PDSCH) via the cell in a second time and in a second frequency. The cell may operate in a time-division duplex (TDD) mode. The first frequency and the second frequency may be the same in the TDD mode. The first time and the second time may be different, in the TDD mode. The cell may operate in a frequency-division duplex (FDD) mode. The first frequency and the second frequency may be different, in the FDD mode. The first time and the second time may be the same, in the FDD mode. A wireless device 1805 may be in an RRC connected state (e.g., mode). The wireless device 1805 may be in an RRC idle state (e.g., mode). The wireless device 1805 may be in an RRC inactive state (e.g., mode).
A cell may comprise a plurality of BWPs. one or more configuration parameters 1815 may indicate, for the cell, the plurality of BWPs. The plurality of BWPs may comprise one or more uplink BWPs comprising an uplink BWP of the cell. The plurality of BWPs may comprise one or more downlink BWPs comprising a downlink BWP of the cell.
A BWP of the plurality of BWPs may be in one of an active state and an inactive state or in a deactivated state. The wireless device 1805 may monitor a downlink channel and/or signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) via and/or for the downlink BWP in the active state of a downlink BWP of the one or more downlink BWPs. The wireless device 1805 may receive a PDSCH via and/or for the downlink BWP, in the active state of a downlink BWP of the one or more downlink BWPs. The wireless device 1805 may not monitor a downlink channel and/or signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) via and/or for the downlink BWP in the inactive state of a downlink BWP of the one or more downlink BWPs. The wireless device 1805 may stop monitoring, or receiving, a downlink channel and/or signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) via and/or for the downlink BWP, in the inactive state of a downlink BWP of the one or more downlink BWPs. The wireless device 1805 may not receive a PDSCH via and/or for the downlink BWP, in the inactive state of a downlink BWP of the one or more downlink BWPs. The wireless device 1805 may stop receiving a PDSCH via and/or for the downlink BWP, in the inactive state of a downlink BWP of the one or more downlink BWPs.
A wireless device 1805 may send (e.g., transmit) an uplink channel and/or signal (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) via the uplink BWP, in the active state of an uplink BWP of the one or more uplink BWPs. The wireless device 1805 may not send (e.g., transmit) an uplink channel and/or signal (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) via the uplink BWP, in the inactive state of an uplink BWP of the one or more uplink BWPs.
A wireless device 1805 may activate a downlink BWP of one or more downlink BWPs of a cell. Activating the downlink BWP may comprise setting (e.g. switching to) the downlink BWP as an active downlink BWP of the cell. The activating the downlink BWP may comprise setting the downlink BWP in the active state. The activating the downlink BWP may comprise switching the downlink BWP from the inactive state to the active state.
A wireless device 1805 may activate an uplink BWP of one or more uplink BWPs of a cell. Activating the uplink BWP may comprise the wireless device 1805 setting (e.g., switching to) the uplink BWP as an active uplink BWP of the cell. The activating the uplink BWP may comprise setting the uplink BWP in the active state. The activating the uplink BWP may comprise switching the uplink BWP from the inactive state to the active state.
One or more configuration parameters 1815 may be for a downlink BWP (e.g., active downlink BWP) of a cell. At least one configuration parameter of the one or more configuration parameters 1815 may be for the downlink BWP of the cell.
One or more configuration parameters 1815 may be for an uplink BWP (e.g., active) of a cell. At least one configuration parameter of the one or more configuration parameters 1815 may be for the uplink BWP of the cell.
One or more configuration parameters 1815 may indicate a plurality of TCI states 1820 (e.g., TCI state 0, TCI state 1, . . . , TCI state M−1). The one or more configuration parameter may comprise a TCI state list parameter (e.g., provided by a higher layer (e.g., RRC) parameter dl-OrJoint-TCIStateList) indicating a TCI state list. The TCI state list may comprise the plurality of TCI states 1820. The one or more configuration parameters 1815 may comprise one or more PDSCH configuration parameters (e.g., PDSCH-Config), for example, comprising the TCI state list parameter indicating the plurality of TCI states 1820. The plurality of TCI states 1820, for example, as described herein in
One or more configuration parameters 1815 may indicate, for a plurality of TCI states 1820, a plurality of TCI state indexes, indicators, and/or identifiers (e.g., TCI-StateId). The one or more configuration parameters 1815 may indicate, for each TCI state of the plurality of TCI states 1820, a respective TCI state index of the plurality of TCI state indexes. Each TCI state of the plurality of TCI states 1820 may be indexed, indicated, and/or identified by a respective TCI state index of the plurality of TCI state indexes. The one or more configuration parameters 1815 may indicate, for example, for a first TCI state of the plurality of TCI states 1820, a first TCI state index of the plurality of TCI state indexes. The one or more configuration parameters 1815 may indicate, for a second TCI state of the plurality of TCI states 1820, a second TCI state index of the plurality of TCI state indexes. The one or more configuration parameters 1815 may indicate the plurality of TCI states 1820 that indicate and/or identify a unified TCI state for the cell.
One or more configuration parameters 1815 may comprise one or more PDSCH configuration parameters, for example, for a downlink BWP of the cell. The one or more configuration parameters 1815 may indicate a plurality of TCI states 1820 for the downlink BWP of the cell.
One or more configuration parameters 1815 may comprise one or more PDSCH configuration parameters, for example, for a second downlink BWP of a second cell. The one or more configuration parameters 1815 may indicate a plurality of TCI states 1820 for the second downlink BWP of the second cell. The one or more configuration parameters 1815 may comprise, for the downlink BWP of the cell, a reference unified TCI state list parameter (e.g., unfiedTCI-StateRef) indicating the second downlink BWP of the second cell. The reference unified TCI state list parameter may comprise a BWP index (e.g., BWP-Id) identifying and/or indicating the second downlink BWP. The reference unified TCI state list parameter may comprise 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 downlink BWP of the cell. The downlink BWP of the cell may be a target BWP of a target cell. The one or more PDSCH configuration parameters of the downlink BWP of the cell may not comprise a higher layer (e.g., RRC) parameter dl-OrJoint-TCIStateList, for example, based on the one or more configuration parameters 1815 comprising, for the downlink BWP of the cell, the reference unified TCI state list parameter.
One or more configuration parameters 1815 may comprise a unified-TCI-state-type parameter (e.g., unifiedtci-StateType). The one or more configuration parameters 1815 may comprise one or more serving cell parameters (e.g., ServingCellConfig) comprising the unified-TCI-state-type parameter. The unified-TCI-state-type parameter may indicate the unified TCI state type of the cell.
A unified-TCI-state-type parameter may, for example, be set to “Joint”. The wireless device 1805 may use a plurality of TCI states 1820 (e.g., provided/indicated by dl-OrJoint-TCIStateList) for both uplink transmissions (e.g., PUSCH/PUCCH/SRS transmissions) of and/or via the cell and downlink receptions (e.g., PDCCH/PDSCH/CSI-RS receptions) of and/or via the cell, for example, based on the one or more configuration parameters 1815 comprising the unified-TCI-state-type parameter set to “Joint”. The plurality of TCI states 1820 may be, for example, a plurality of joint TCI states.
A unified-TCI-state-type parameter may, for example, be set to “Separate”. The wireless device 1805 may use the plurality of TCI states 1820 (e.g., provided/indicated by a higher layer parameter dl-OrJoint-TCIStateList) for downlink receptions (e.g., PDCCH/PDSCH/CSI-RS receptions) of and/or via the cell, for example, based on the one or more configuration parameters 1815 comprising the unified-TCI-state-type parameter set to “Separate”. The wireless device 1805 may not use the plurality of TCI states 1820 for uplink transmissions (e.g., PUSCH/PUCCH/SRS transmissions) of and/or via the cell, for example, based on the one or more configuration parameters 1815 comprising the unified-TCI-state-type parameter set to “Separate”. The plurality of TCI states 1820 may be, for example, a plurality of downlink TCI states.
One or more configuration parameters 1815 may indicate a second plurality of TCI states. The one or more configuration parameters 1815 may comprise an uplink TCI state list parameter (e.g., provided/indicated by a higher layer parameter ul-TCI-StateList) indicating an uplink TCI state list. The uplink TCI state list may comprise the second plurality of TCI states. The one or more configuration parameters 1815 may comprise one or more uplink BWP configuration parameters comprising the uplink TCI state list parameter that indicates the second plurality of TCI states. The second plurality of TCI states may, for example, be TCI state 0, TCI state 1, . . . , and TCI state M−1.
One or more configuration parameters 1815 may comprise one or more uplink BWP configuration parameters, for example, for an uplink BWP of the cell. The one or more configuration parameters 1815 may indicate a second plurality of TCI states for the uplink BWP of the cell.
One or more configuration parameters 1815 may comprise one or more uplink BWP configuration parameters, for example, for a second uplink BWP of a second cell. The one or more configuration parameters 1815 indicate a second plurality of TCI states for the second uplink BWP of the second cell. The one or more configuration parameters 1815 may comprise, for the uplink BWP of the cell, 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 comprise a BWP index (e.g., BWP-Id) identifying and/or indicating the second uplink BWP. The reference unified TCI state list parameter may comprise 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 uplink BWP of the cell. The uplink BWP of the cell may be a target BWP of a target cell. The one or more uplink BWP configuration parameters of the uplink BWP of the cell may not comprise a higher layer (e.g., RRC) parameter ul-TCI-StateList, for example, based on the one or more configuration parameters 1815 comprising, for the uplink BWP of the cell, the reference unified TCI state list parameter.
A wireless device 1805 may use a second plurality of TCI states for uplink transmissions (e.g., PUSCH/PUCCH/SRS transmissions) of and/or via the cell, for example, based on one or more configuration parameters 1815 comprising a unified-TCI-state-type parameter set to “Separate”. The wireless device 1805 may not use the second plurality of TCI states for downlink receptions (e.g., PDCCH/PDSCH/CSI-RS receptions) of and/or via the cell, for example, based on the one or more configuration parameters 1815 comprising the unified-TCI-state-type parameter set to “Separate”. The second plurality of TCI states may be, for example, a plurality of uplink TCI states.
A wireless device 1805 may use, for downlink receptions via a downlink BWP of a cell, a plurality of TCI states 1820, for example based on one or more configuration parameters 1815 indicating the plurality of TCI states 1820 for the downlink BWP of the cell. A wireless device 1805 may use, for uplink transmissions receptions via an uplink BWP of the cell, a plurality of TCI states 1820, for example, based on one or more configuration parameters 1815 indicating the plurality of TCI states 1820 for the downlink BWP of the cell. A wireless device 1805 may use, for downlink receptions via a downlink BWP of the cell, a plurality of TC states 1820 of a second downlink BWP of a second cell, for example, based on a reference unified TCI state list parameter indicating, for the downlink BWP of the cell, the second downlink BWP of the second cell.
A wireless device 1805 may use, for uplink transmissions receptions via an uplink BWP of a cell, a plurality of TCI states 1820 of a second downlink BWP of the second cell, for example, based on a reference unified TCI state list parameter indicating, for the downlink BWP of the cell, the second downlink BWP of the second cell. A wireless device 1805 may use, for uplink transmissions receptions via an uplink BWP of the cell, a second plurality of TCI states, for example based on the one or more configuration parameters 1815 indicating the second plurality of TC states for the uplink BWP of the cell. A wireless device 1805 may use, for uplink transmissions receptions via an uplink BWP of the cell, a second plurality of TCI states of the second uplink BWP of the second cell, for example, based on the reference unified TCI state list parameter indicating, for the uplink BWP of the cell, the second uplink BWP of the second cell.
A wireless device 1805 may receive an activation command (e.g., MAC-CE, DCI, RRC, control command, downlink control command/message, control command/message, Unified TCI States Activation/Deactivation MAC CE, Enhanced Unified TCI States Activation/Deactivation MAC CE, and the like). The activation command may, for example, indicate activation of a subset of TCI states (e.g., two TCI states 1825) of the plurality of TC states 1820 (e.g., DLorJoint-TCIStateList). The subset of TC states (e.g., two TCI states 1825) may be, for example, a subset of joint TCI states of the plurality of joint TCI states. The subset of TC states (e.g., two TCI states 1825) may be, for example, a subset of downlink TCI states of the plurality of downlink TCI states.
An activation command (e.g., first control command 1830) may, for example, indicate activation of a subset of TC states (e.g., two TCI states 1825) of a second plurality of TC states (e.g., ul-TCI-StateList). The subset of TC states (e.g., two TCI states 1825) may be, for example, a subset of uplink TCI states of the plurality of uplink TCI states.
A base station 1810 may activate and/or deactivate the subset of TCI states (e.g., two TCI states 1825), for example, by sending (e.g., transmitting) the activation command. A wireless device 1805 may map the subset of TCI states (e.g., two TCI states 1825) to one or more TCI codepoints. The activation command may indicate mapping of the subset of TCI states (e.g., two TCI states 1825) to the one or more TCI codepoints. The wireless device 1805 may map respective TCI state(s) of the subset of TCI states (e.g., two TCI states 1825) to a respective TCI codepoint of the one or more TCI codepoints. The one or more TCI codepoints may indicate and/or comprise the subset of TCI states (e.g., two TCI states 1825). Each TCI codepoint of the one or more TCI codepoints may indicate, or be mapped to, respective TCI state(s) of the subset of TCI states (e.g., two TCI states 1825). Each TCI codepoint of the one or more TCI codepoints may indicate/comprise (or be mapped to) one or more TCI states.
A subset of TCI states may be TCI state 4, TCI state 5, TCI state 8, TCI state 26, and TCI state 61. The one or more TCI codepoints may comprise a first TCI codepoint (e.g., TCI codepoint 000), a second TCI codepoint (e.g., TCI codepoint 001), a third TCI codepoint (e.g., TCI codepoint 010), and a fourth TCI codepoint (e.g., TCI codepoint 011). The first TCI codepoint (e.g., TCI codepoint 000) may comprise the TCI state 4. The second TCI codepoint (e.g., TCI codepoint 001) may comprise the TCI state 5 and the TCI state 8. The third TCI codepoint (e.g., TCI codepoint 010) may comprise the TCI state 26 and TCI state 61. The fourth TCI codepoint (e.g., TCI codepoint 011) may comprise the TCI state 26. For example, the first TCI codepoint (e.g., TCI codepoint 000) and the fourth TCI codepoint (e.g., TCI codepoint 011) indicate a single TCI state. The second TCI codepoint (e.g., TCI codepoint 001) and the third TCI codepoint (e.g., TCI codepoint 010) indicate two TCI states (e.g., two joint TCI states, two uplink TCI states, two downlink TCI states, and the like).
A second field 1910 (e.g., BWP ID) of a plurality of fields may comprise a BWP index, indication, and/or identifier indicating and/or identifying a downlink BWP of a cell. The second field 1910 may comprise the BWP index, indication, and/or identifier indicating and/or identifying the downlink BWP of the cell for which the activation command applies as a codepoint of a bandwidth part indicator field in DCI
A third field 1915 (e.g., TCI state IDi,j in
A TCI codepoint to which TCI state(s) are mapped may be determined, by a wireless device and/or a base station, by an ordinal position of the TCI codepoint among ordinal position(s) of TCI codepoint(s). The first TCI codepoint with TCI state ID0,1 and TCI state ID0,2 may, for example, be mapped to the codepoint value 0 (e.g., TCI codepoint 000), the second TCI codepoint with TCI state ID1,1 and TCI state ID1,2 may be mapped to the codepoint value 1 (e.g., TCI codepoint 001) and so on.
A second TCI codepoint (e.g., TCI codepoint 001) may comprise a TCI state 5 and a TCI state 8. The TCI state 5 and the TCI state 8 may be mapped to the second TCI codepoint (e.g., TCI codepoint 001).
An activation command may comprise a TCI state index, indicator, and/or identifier (e.g., TCI state ID1,1) of a TCI state 5 and a TCI state index, indicator, and/or identifier (e.g., TCI state ID1,2) of a TCI state 8. The TCI state 5 may be a first TCI state and the TCI state 8 may be a second TCI state, for example, based on the TCI state index, indicator, and/or identifier (e.g., TCI state ID1,1) of the TCI state 5 occurring, being, and/or positioning in a lower octet in the activation command than the TCI state index, indicator, and/or identifier (e.g., TCI state ID1,2) of the TCI state 8. Octet 4 of the activation command may, for example, comprise the TCI state index, indicator, and/or identifier (e.g., TCI state ID1,1) of the TCI state 5 and Octet 5 of the activation command may comprise the TCI state index, indicator, and/or identifier (e.g., TCI state ID1,2) of the TCI state 8.
An activation command may comprise a TCI state index, indicator, and/or identifier (e.g., TCI state ID1,1) of a TCI state 8 and a TCI state index, indicator, and/or identifier (e.g., TCI state ID1,2) of a TCI state 5. The TCI state 8 may be the first TCI state and the TCI state 5 may be the second TCI state, for example, based on the TCI state index, indicator, and/or identifier (e.g., TCI state ID1,1) of the TCI state 8 occurring, being, and/or positioning in a lower octet in the activation command than the TCI state index, indicator, and/or identifier (e.g., TCI state ID1,2) of the TCI state 5. Octet 4 of the activation command may, for example, comprise the TCI state index, indicator, and/or identifier (e.g., TCI state ID1,1) of the TCI state 8 and Octet 5 of the activation command may comprise the TCI state index, indicator, and/or identifier (e.g., TCI state ID1,2) of the TCI state 5.
A third TCI codepoint (e.g., TCI codepoint 010) may comprise a TCI state 26 and TCI state 61. The TCI state 26 and the TCI state 61 may be mapped to a third TCI codepoint (e.g., TCI codepoint 010).
An activation command may comprise a TCI state index, indicator, and/or identifier (e.g., TCI state ID2,1) of a TCI state 26 and a TCI state index, indicator, and/or identifier (e.g., TCI state ID2,2) of a TCI state 61. The TCI state 26 may be a first TCI state and the TCI state 61 may be a second TCI state, for example, based on the TCI state index, indicator, and/or identifier (e.g., TCI state ID2,1) of the TCI state 26 occurring, being, and/or positioning in a lower octet in the activation command than the TCI state index, indicator, and/or identifier (e.g., TCI state ID2,2) of the TCI state 61. Octet 6 of the activation command may, for example, comprise the TCI state index, indicator, and/or identifier (e.g., TCI state ID2,1) of the TCI state 26 and Octet 7 of the activation command may comprise the TCI state index, indicator, and/or identifier (e.g., TCI state ID2,2) of the TCI state 61.
An activation command may comprise a TCI state index, indicator, and/or identifier (e.g., TCI state ID2,1) of a TCI state 61 and a TCI state index, indicator, and/or identifier (e.g., TCI state ID2,2) of a TCI state 26. The TCI state 61 may be a first TCI state and the TCI state 26 may be a second TCI state, for example, based on the TCI state index, indicator, and/or identifier (e.g., TCI state ID2,1) of the TCI state 61 occurring, being, and/or positioning in a lower octet in the activation command than the TCI state index, indicator, and/or identifier (e.g., TCI state ID2,2) of the TCI state 26. Octet 6 of the activation command may, for example, comprise the TCI state index, indicator, and/or identifier (e.g., TCI state ID2,1) of the TCI state 61 and Octet 7 of the activation command may comprise the TCI state index, indicator, and/or identifier (e.g., TCI state ID2,2) of the TCI state 26.
A fourth field 1920a-1920e (e.g., R) of the plurality of fields may be a reserved bit. The reserved bit may be set to, for example, zero.
A wireless device may receive a control command (e.g., a first control command at time T1 as described herein in
A number of one or more TCI codepoints may be equal to one (e.g., a single TCI codepoint). A single TCI codepoint may indicate at least two TCI states. The control command indicating the at least two TCI states may be an activation command activating the subset of TCI states based on the number of the one or more TCI codepoints being equal to one. The at least two TCI states may be the subset of TCI states based on the number of the one or more TCI codepoints being equal to one. The activation command may indicate the at least two TCI states based on the number of the one or more TCI codepoints being equal to one.
A number of one or more TCI codepoints may be more than one. A control command indicating the at least two TCI states may be different from the activation command activating the subset of TCI states based on the number of the one or more TCI codepoints being more than one. A wireless device may receive the control command after receiving the activation command. The control command (e.g., DCI) may comprise a TCI field indicating the at least two TCI states. A value of the TCI field may be equal to a TCI codepoint, of the one or more TCI codepoints, indicating the at least two TCI states. The at least two TCI states may be mapped to the TCI codepoint.
At least two TCI states may be, for example, at least two joint TCI states. The at least two TCI states may be, for example, at least two downlink TCI states. The at least two TCI states may be, for example, at least two uplink TCI states. The at least two TCI states may comprise a first TCI state and a second TCI state. The first TCI state may comprise a first reference signal (e.g., CSI-RS, SSB/PBCH block, DM-RS, SRS, and the like). The first TCI state may comprise a first quasi co-location type (e.g., QCL TypeA, QCL TypeB, QCL TypeC, QCL TypeD). The second TCI state may comprise a second reference signal (e.g., CSI-RS, SSB/PBCH block, DM-RS, SRS, and the like). The second TCI state may comprise a second quasi co-location type (e.g., QCL TypeA, QCL TypeB, QCL TypeC, QCL TypeD).
A wireless device may receive a control command (e.g., Second control command at time T2 as described herein in
One or more configuration parameters may comprise one or more semi-persistent scheduling (SPS) configuration parameters of a SPS configuration. A control command may indicate activation of the SPS configuration. The control command may comprise one or more fields (e.g., RV, HARQ process, MCS, and the like) set to predefined values (e.g., 0, 1) that indicate activation of the SPS configuration. The wireless device may validate the control command based on the one or more fields (e.g., RV, HARQ process, MCS, and the like) being set to the predefined values. The wireless device may activate the SPS configuration based on the validating the control command.
A downlink reception may comprise, for example, a PDSCH reception. The PDSCH reception may comprise one or more transport blocks (e.g., downlink data). The control command may comprise one or more fields (e.g., TDRA field, FDRA field) indicating resources for the downlink reception. The downlink BWP of the cell may comprise the resources.
A downlink reception may comprise, for example, an aperiodic CSI-RS. A control command may trigger reception of the aperiodic CSI-RS via an aperiodic CSI-RS resource. The control command may comprise a CSI request field triggering an aperiodic CSI report. The control command may comprise the CSI request field triggering the aperiodic CSI report that comprises a radio link quality (e.g., RSRP, SINR, SNR) of the aperiodic CSI-RS.
One or more configuration parameters may indicate one or more aperiodic trigger states (e.g., by a higher layer parameter CSI-AperiodicTriggerStateList). A codepoint of the CSI request field in the control command may be associated with, or may indicate, an aperiodic trigger state of the one or more aperiodic trigger states. The aperiodic trigger state may comprise one or more report configurations (e.g., provided by a higher layer parameter associatedReportConfigInfoList, a list of NZP-CSI-RS-ResourceSet). A wireless device may perform measurement of the aperiodic CSI-RS via the aperiodic CSI-RS resource and send (e.g., transmit) an aperiodic CSI report according to one or more report configurations for the aperiodic trigger state, based on receiving the control command with the CSI request field indicating the aperiodic trigger state.
A report configuration (e.g., provided by a higher layer parameter CSI-AssociatedReportConfigInfo, a higher layer parameter NZP-CSI-RS-ResourceSet) of one or more report configurations may be indexed, indicated, and/or identified with a report configuration index, indicator, and/or identifier (e.g., provided by a higher layer parameter CSI-ReportConfigId). The report configuration may comprise one or more aperiodic CSI-RS resources (e.g., NZP-CSI-RS-Resources). The aperiodic CSI-RS resource of the one or more aperiodic CSI-RS resources may be associated with a TCI state (e.g., provided by a higher layer parameter qcl-info in IE CSI-AperiodicTriggerStateList or a higher layer parameter applyIndicatedTCIState) of a plurality of TCI states. The TCI state may provide a QCL assumption (e.g., an RS, an RS source, SS/PBCH block, CSI-RS) for the aperiodic CSI-RS via the aperiodic CSI-RS resource. The TCI state may provide a QCL type (e.g., QCL-TypeA, QCL-TypeD, etc.) for the aperiodic CSI-RS via the aperiodic CSI-RS resource. The at least two TCI states may comprise the TCI state.
A control command (e.g., Second control command at time T2 as described herein in
A control command (e.g., Second control command at time T2 in
A control command may be, for example, DCI format 1_0. One or more configuration parameters may comprise an apply-indicated-TCI-state parameter (e.g., applyIndicatedTCIState) set to ‘both’ indicating to use the at least two TCI states (e.g., both/each of the at least two TCI states) for the downlink reception scheduled and/or activated by the DCI format 1_0.
An apply-indicated-TCI-state parameter (e.g., applyIndicatedTCIState) may be set to ‘both’, for example, based on one or more configuration parameters comprising a coherent-joint-transmission (CJT) scheme parameter (e.g., cjtSchemePDSCH) for PDSCH receptions. The apply-indicated-TCI-state parameter (e.g., applyIndicatedTCIState) may be set to ‘both’, for example, based on sending (e.g., transmitting), to a base station, a capability message (e.g., a wireless device capability message) indicating support of two TCI states (e.g., two joint TCI states) for CJT-based PDSCH receptions. An apply-indicated-TCI-state parameter (e.g., applyIndicatedTCIState) may be set to ‘both’, for example, based on one or more configuration parameters comprising a single-frequency-network (SFN) parameter for PDSCH receptions (e.g., sfnSchemePdsch).
A wireless device may receive a downlink reception (e.g., at time T4 as described herein in
One or more configuration parameters may indicate at least two DTXs for a cell. The at least two DTXs of the cell may be, or may be interchangeably used with, at least two DTX configurations of the cell. The at least two DTXs of the cell may be, or may be interchangeably used with, at least two DTX operations of the cell.
One or more configuration parameters may comprise one or more first DTX configuration parameters (e.g., TRP-DTX-Config, TRP-DTX-Config1 TRP1-DTX-Config, DTX-Config, DTX-Config1, and the like) indicating a first DTX of a cell (e.g., first DTX as described herein in
One or more configuration parameters may comprise one or more second DTX configuration parameters (e.g., TRP-DTX-Config2, TRP2-DTX-Config, DTX-Config2, and the like) indicating a second DTX of a cell (e.g., Second DTX as described herein in
A wireless device may send (e.g., transmit) and/or report a capability message (e.g., a wireless device capability message) indicating a support and/or capability (e.g., twoDTXcapability) of two DTX configurations for a cell. The one or more configuration parameters may comprise one or more second DTX configuration parameters indicating a second DTX, for example, based on sending (e.g., transmitting) and/or reporting the capability message indicating the support and/or capability (e.g., twoDTXcapability) of two DTX configurations for the cell. A base station may send (e.g., transmit), to the wireless device, the one or more second DTX configuration parameters indicating the second DTX, for example, based on receiving the capability message indicating support and/or capability (e.g., twoDTXcapability) of two DTX configurations for the cell. The base station may send (e.g., transmit), to the wireless device, the one or more configuration parameters indicating at most two DTXs (e.g., no DTX configuration, the first DTX only, the second DTX only, both the first DTX and the second DTX) for the cell, for example, based on receiving the capability message indicating support and/or capability (e.g., twoDTXcapability) of two DTX configurations for the cell.
A wireless device may not send (e.g., transmit) and/or report a capability message (e.g., a wireless device capability message) indicating support and/or capability (e.g., twoDTXcapability) of two DTX configurations for a cell. one or more configuration parameters may not comprise one or more second DTX configuration parameters indicating a second DTX, for example, based on not sending (e.g., transmitting) and/or reporting the capability message indicating support and/or capability (e.g., twoDTXcapability) of two DTX configurations for the cell. A base station may not send (e.g., transmit), to the wireless device, the one or more second DTX configuration parameters indicating the second DTX, for example, based on not receiving the capability message indicating support and/or capability (e.g., twoDTXcapability) of two DTX configurations for the cell. The base station may send (e.g., transmit), to the wireless device, the one or more first DTX configuration parameters indicating the first DTX, for example, based on not receiving the capability message indicating support and/or capability (e.g., twoDTXcapability) of two DTX configurations for the cell. The base station may send (e.g., transmit), to the wireless device, the one or more configuration parameters indicating at most one DTX (e.g., the first DTX only or no DTX configuration) for the cell, for example, based on not receiving the capability message indicating support and/or capability (e.g., twoDTXcapability) of two DTX configurations for the cell.
One or more configuration parameters may indicate at least two DRXs for a cell. The at least two DRXs of the cell may be, or may be interchangeably used with, at least two DRX configurations of the cell. The at least two DRXs of the cell may be, or may be interchangeably used with, at least two DRX operations of the cell.
One or more configuration parameters may comprise one or more first DRX configuration parameters (e.g., TRP-DRX-Config, TRP-DRX-Config1 TRP1-DRX-Config, DRX-Config, DRX-Config1, and the like) indicating a first DRX of the cell (e.g., first DRX as described herein in
One or more configuration parameters may comprise one or more second DRX configuration parameters (e.g., TRP-DRX-Config2, TRP2-DRX-Config, DRX-Config2, and the like) indicating a second DRX of the cell (e.g., Second DRX as described herein in
A wireless device may receive a control command (e.g., Third control command at time T3 as described herein in
A wireless device may receive a second control command (e.g., Third control command at time T3 as described herein in
A value (e.g., ‘1’) of a bit of a DTX and/or DRX in a block of one or more blocks may indicate activation of a DTX of the cell. The block may be associated with a cell. one or more configuration parameters may indicate, for the cell, a starting position of the block or a starting position of the DTX. The bit may be associated with, or may correspond to, the DTX of the cell.
A DTX may be, for example, A first DTX. The DTX may be, for example, a second DTX. The DTX of a cell may be, or may be interchangeably used with, a DTX configuration of the cell. The DTX of the cell may be, or may be interchangeably used with, a DTX operation of the cell.
A size (e.g., length) of each block of one or more blocks may be one or more bits (e.g., 1 bit, 2 bits, 3 bits, 4 bits). Each block may comprise respective DTX and/or DRX (e.g., TRP DTX/DRX indicator field). Each bit of a DTX and/or DRX (e.g., TRP DTX/DRX indicator field) in a block of the one or more blocks may indicate activation or deactivation of one of: a first DTX, a second DTX, a first DRX, and a second DRX. A first value (e.g., ‘0’) for a bit of the DTX/DRX indicator field may indicate deactivation of a DTX or of a DRX among the first DTX, the second DTX, the first DRX, and the second DRX, where the bit corresponds to, or is associated with, the DTX or the DRX. A second value (e.g., ‘1’) for a bit of the DTX/DRX indicator field may indicate activation of a DTX or of a DRX among the first DTX, the second DTX, the first DRX, and the second DRX, where the bit corresponds to, or is associated with, the DTX or the DRX.
A block (e.g., Block 1 2005a of
A first value (e.g., ‘0’) for the MSB of the DTX/DRX indicator field may indicate deactivation of the first DTX. A second value (e.g., ‘1’) for the MSB of the DTX/DRX indicator field may indicate activation of the first DTX.
A first value (e.g., ‘0’) for the second MSB of the DTX/DRX indicator field may indicate deactivation of the first DRX. A second value (e.g., ‘1’) for the second MSB of the DTX/DRX indicator field may indicate activation of the first DRX.
A first value (e.g., ‘0’) for the LSB of the DTX/DRX indicator field may indicate deactivation of the second DRX. A second value (e.g., ‘1’) for the LSB of the DTX/DRX indicator field may indicate activation of the second DRX.
A first value (e.g., ‘0’) for the second LSB of the DTX/DRX indicator field may indicate deactivation of the second DTX. A second value (e.g., ‘1’) for the second LSB of the DTX/DRX indicator field may indicate activation of the second DTX.
For example, a block (e.g., Block 3 in
A first value (e.g., ‘0’) for the MSB of the DTX/DRX indicator field may indicate deactivation of the first DTX. A second value (e.g., ‘1’) for the MSB of the DTX/DRX indicator field may indicate activation of the first DTX.
A first value (e.g., ‘0’) for the LSB of the DTX/DRX indicator field may indicate deactivation of the second DTX. A second value (e.g., ‘1’) for the LSB of the DTX/DRX indicator field may indicate activation of the second DTX.
For example, a block of the one or more blocks may be 2 bits if the first DRX and the second DRX are indicated and/or configured, by the one or more configuration parameters, for the cell. The MSB of the 2 bits of the block may correspond to the first DRX. The LSB of the 2 bits of the block may correspond to the second DRX. The first DTX and the second DTX may not be indicated and/or configured, by the one or more configuration parameters, for the cell.
For example, a block of the one or more blocks may be 2 bits if the first DTX and the second DRX are indicated and/or configured, by the one or more configuration parameters, for the cell. The MSB of the 2 bits of the block may correspond to the first DTX. The LSB of the 2 bits of the block may correspond to the second DRX. The second DTX and the first DRX may not be indicated and/or configured, by the one or more configuration parameters, for the cell.
For example, a block of the one or more blocks may be 2 bits if two of: the first DTX, the second DTX, the first DRX, and the second DRX are indicated and/or configured, by the one or more configuration parameters, for the cell. For example, the block may comprise one of {[DTX 1, DRX 1], [DTX 1, DRX 2], [DTX 1, DTX 2], [DRX 1, DRX 2], [DRX 1, DTX 2], [DTX 2, DRX 2]}.
For example, a block (e.g., Block N−1 in
For example, a block (e.g., Block N in
For example, a block of the one or more blocks may be 3 bits if three of: the first DTX, the second DTX, the first DRX, and the second DRX are indicated and/or configured, by the one or more configuration parameters, for the cell. For example, the block may comprise one of {[DTX 1, DRX 1, DTX 2], [DTX 1, DRX 1, DRX 2], [DTX 1, DTX 2, DRX 2], [DRX 1, DTX 2, DRX 2]}.
For example, a block of the one or more blocks may be 1 bit if one of: the first DTX, the second DTX, the first DRX, and the second DRX are indicated and/or configured, by the one or more configuration parameters, for the cell. For example, the block may comprise one of {[DTX 1], [DRX 1], [DTX 2], [DRX 2]}.
A starting position of a DTX and/or DRX (or a DTX/DRX indicator field) of a TRP in a block of the one or more blocks may be determined, by the wireless device and/or the base station, by a position parameter (e.g., positionInDCI-TRPDTRX). The one or more configuration parameters may comprise the position parameter. For example, a wireless device configured with (or served by) both the first TRP and the second TRP may be indicated by a starting position of the block (e.g., starting position of DTX 1 in Block 1 in
A size (e.g., length) of each block of the one or more blocks may be at least two bits (e.g., 2 bits, 3 bits). Each block may comprise a respective DTX/DRX indicator field (e.g., DTX/DRX indicator field) and a respective index, indicator, and/or identifier field (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, and the like). An index, indicator, and/or identifier field in a block of the one or more blocks may be 1 bit. A respective index, indicator, and/or identifier field in each block of the one or more blocks may be 1 bit.
Each bit of a DTX/DRX indicator field (e.g., DTX/DRX indicator field) in a block may indicate activation or deactivation of one of: a first DTX and a first DRX, for example, if a value of an index, indicator, and/or identifier field in a block of the one or more blocks is equal and/or set to a first value (e.g., 0). A first value (e.g., ‘0’) for a bit of the DTX/DRX indicator field in the block may indicate 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’) for a bit of the DTX/DRX indicator field in the block may indicate 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.
Each bit of a DTX/DRX indicator field (e.g., DTX/DRX indicator field) in a block may indicate activation or deactivation of one of: a second DTX and a second DRX, for example, if a value of an index, indicator, and/or identifier field in a block of the one or more blocks is equal and/or set to a second value (e.g., 1). A first value (e.g., ‘0’) for a bit of the DTX/DRX indicator field may indicate 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’) for a bit of the DTX/DRX indicator field may indicate 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.
An index, indicator, and/or identifier field in a block may be located (e.g., positioned) after a DTX/DRX indicator field in the block. The index, indicator, and/or identifier field in the block may not be located (e.g., positioned) before the DTX/DRX indicator field in the block.
A block may be 3 bits, for example, if an index, indicator, and/or identifier field in a block (e.g., Block 1 2005b in
A first value (e.g., ‘0’) for a MSB of a DTX/DRX indicator field may indicate deactivation of a first DTX. A second value (e.g., ‘1’) for the MSB of the DTX/DRX indicator field may indicate activation of the first DTX.
A first value (e.g., ‘0’) for a second MSB of a DTX/DRX indicator field may indicate deactivation of a first DRX. A second value (e.g., ‘1’) for the second MSB of the DTX/DRX indicator field may indicate activation of the first DRX.
A block may be 3 bits, for example, if a second DTX and a second DRX are indicated and/or configured, by one or more configuration parameters, for a cell, and if an index, indicator, and/or identifier field 2050f in a block 2015b (e.g., Block 3 in
A first value (e.g., ‘0’) for a MSB of a DTX/DRX indicator field may indicate deactivation of a second DTX. A second value (e.g., ‘1’) for the MSB of the DTX/DRX indicator field may indicate activation of the second DTX.
A first value (e.g., ‘0’) for a second MSB of a DTX/DRX indicator field may indicate deactivation of a second DRX. A second value (e.g., ‘1’) for the second MSB of the DTX/DRX indicator field may indicate activation of the second DRX.
A block may be 2 bits, for example, if an index, indicator, and/or identifier field 2030g in a block 2020b (e.g., Block N−1 in
A first value (e.g., ‘0’) for a MSB of a DTX/DRX indicator field may indicate deactivation of a first DTX or a first DRX. A second value (e.g., ‘1’) for the MSB of the DTX/DRX indicator field may indicate activation of the first DTX or the first DRX.
A block may be 2 bits, for example, if an index, indicator, and/or identifier field 2050h in a block 2025b (e.g., Block N in
A first value (e.g., ‘0’) for a MSB of a DTX/DRX indicator field may indicate deactivation of a second DTX or a second DRX. A second value (e.g., ‘1’) for the MSB of the DTX/DRX indicator field may indicate activation of the second DTX or the second DRX.
In
In
A wireless device may receive a downlink reception based on at least two TCI states, for example, in response to the control command (e.g., Second control command at time T2 as described herein in
One or more configuration parameters may comprise a repetition scheme parameter (e.g., repetitionScheme) indicating a repetition scheme. The repetition scheme may be a frequency domain repetition scheme (e.g., ‘fdmSchemeA’, ‘fdmSchemeB’). The repetition scheme may be a time domain repetition scheme (e.g., ‘tdmSchemeA’).
A wireless device may receive repetitions of a downlink reception based on at least two TCI states, for example, in response to one or more configuration parameters comprising a repetition scheme parameter (e.g., repetitionScheme) that indicates the repetition scheme.
A control command scheduling and/or activating a downlink reception may comprise a TDRA field indicating an entry, in an TDRA table (e.g., PDSCH-TimeDomainResourceAllocation), that comprises a number of repetitions (e.g., repetitionNumber). The wireless device may receive repetitions of the downlink reception based on at least two TCI states, for example, in response to the control command comprising the TDRA field indicating the number of repetitions. A number of the repetitions of the downlink reception may be equal to the number of repetitions in the entry.
A number of repetitions of the downlink reception may be equal to the number of repetitions in the entry, for example, if a wireless device is configured by the higher layer parameter repetitionNumber in PDSCH-TimeDomainResourceAllocation, together with the DCI field ‘Time domain resource assignment’ indicating an entry which contains repetitionNumber in PDSCH-TimeDomainResourceAllocation and DM-RS port(s).
A wireless device may receive one or more first repetitions of a downlink reception based on a first TCI state. The wireless device may receive one or more second repetitions of a downlink reception based on a second TCI state. At least one DM-RS antenna port of the downlink reception may be quasi co-located with a first reference signal indicated by the first TCI state, for example, in one or more first repetitions, or one or more first transmission occasions of the one or more first repetitions. The at least one DM-RS antenna port of the downlink reception may be quasi co-located with the first reference signal with respect to the first quasi co-location type indicated by the first TCI state. The at least one DM-RS antenna port of the downlink reception may be quasi co-located with the second reference signal indicated by the second TCI state, for example, in the one or more second repetitions, or one or more second transmission occasions of the one or more second repetitions. The at least one DM-RS antenna port of the downlink reception may be quasi co-located with the second reference signal with respect to the second quasi co-location type indicated by the second TCI state. Repetitions of the downlink reception may comprise one or more first repetitions of a downlink reception and one or more second repetitions of a downlink reception.
One or more configuration parameters may comprise an SFN parameter (e.g., sfnSchemePdsch) indicating an SFN scheme for PDSCH receptions. At least one DM-RS antenna port of a downlink reception may be quasi co-located with a first reference signal indicated by a first TCI state. The at least one DM-RS antenna port of the downlink reception may be quasi co-located with the first reference signal with respect to the first quasi co-location type indicated by the first TCI state. The at least one DM-RS antenna port of the downlink reception may be quasi co-located with the second reference signal indicated by the second TCI state. The at least one DM-RS antenna port of the downlink reception may be quasi co-located with the second reference signal with respect to the second quasi co-location type indicated by the second TCI state. At least one DM-RS antenna port of the downlink reception may be quasi co-located with both the first reference signal indicated by the first TCI state and the second reference signal indicated by the second TCI state.
A control command scheduling and/or activating a downlink reception may comprise an antenna ports field indicating at least one DM-RS port within two code-division-multiplexing (CDM) groups. A wireless device may receive one or more first layers, or data streams, of the downlink reception based on a first TCI state. The wireless device may receive one or more second layers, or data streams, of the downlink reception based on a second TCI state. At least one first DM-RS antenna port of the downlink reception may be quasi co-located with the first reference signal indicated by the first TCI state. The at least one first DM-RS antenna port of the downlink reception may be quasi co-located with the first reference signal with respect to the first quasi co-location type indicated by the first TCI state. At least one second DM-RS antenna port of the downlink reception may be quasi co-located with the second reference signal indicated by the second TCI state. The at least one second DM-RS antenna port of the downlink reception may be quasi co-located with the second reference signal with respect to the second quasi co-location type indicated by the second TCI state. The at least one first DM-RS antenna port and the at least one second DM-RS antenna port may be, for example, different. The first TCI state may correspond to a first CDM group of the two CDM groups. The second TCI state may correspond to a second CDM group of the two CDM groups.
One or more configuration parameters may comprise a CJT scheme parameter (e.g., cjtSchemePDSCH) indicating and/or configuring a CJT transmission and/or reception scheme for PDSCH receptions. A first quasi co-location type of a first TCI state may comprise one or more first QCL parameters. The one or more first QCL parameters may comprise a first doppler shift, a first doppler spread, a first average delay, and/or a first delay spread. A second quasi co-location type of a second TCI state may comprise one or more second QCL parameters. The one or more second QCL parameters may comprise a second doppler shift, a second doppler spread, a second average delay, and a second delay spread. The CJT scheme parameter may be set to a first CJT scheme (e.g., cjtSchemeA).
In a first CJT scheme, at least one DM-RS port of a downlink reception may be quasi co-located with a first reference signal with respect to a first quasi co-location type (e.g., QCL Type A). The at least one DM-RS port of the downlink reception may be quasi co-located with a second reference signal with respect to a second quasi co-location type (e.g., QCL Type A).
In a first CJT scheme, at least one DM-RS port of a downlink reception may be quasi co-located with a first reference signal with respect to a first quasi co-location type (e.g., QCL Type A) that comprises and/or indicates a first doppler shift, a first doppler spread, a first average delay, and/or a first delay spread. The at least one DM-RS port of the downlink reception may be quasi co-located with the second reference signal with respect to the second quasi co-location type (e.g., QCL Type A) that comprises and/or indicates a second doppler shift, a second doppler spread, a second average delay, and/or a second delay spread. In the first CJT scheme, at least one DM-RS port of the downlink reception may be quasi co-located with a first reference signal with respect to the one or more first QCL parameters. The at least one DM-RS port of the downlink reception may be quasi co-located with the second reference signal with respect to the one or more second QCL parameters.
A CJT scheme parameter may be set to a second CJT scheme (e.g., cjtSchemeB). In a second CJT scheme, at least one DM-RS port of a downlink reception may be quasi co-located with a first reference signal with respect to a first quasi co-location type (e.g., QCL Type A). The at least one DM-RS port of the downlink reception may be quasi co-located with a second reference signal with respect to a second quasi co-location type (e.g., QCL Type A) except a second doppler shift and a second doppler spread of a second TCI state.
In a second CJT scheme, at least one DM-RS port of the a reception may be quasi co-located with a first reference signal with respect to a first quasi co-location type (e.g., QCL Type A) that comprises and/or indicates a first doppler shift, a first doppler spread, a first average delay, and/or a first delay spread. The at least one DM-RS port of a downlink reception may be quasi co-located with a second reference signal with respect to a second average delay and a second delay spread of a second TCI state. The at least one DM-RS port of the downlink reception may not be quasi co-located with the second reference signal with respect to the second doppler shift and the second doppler spread.
In a second CJT scheme, at least one DM-RS port of a downlink reception may be quasi co-located with a first reference signal with respect to one or more first QCL parameters. The at least one DM-RS port of the downlink reception may be quasi co-located with a second reference signal with respect to one or more second QCL parameters except a second doppler shift and a second doppler spread.
One or more configuration parameters may comprise one or more first DTX configuration parameters of a first DTX of the cell and one or more second DTX configuration parameters of a second DTX of the cell (e.g., both the first DTX and the second DTX are configured). A control command (e.g., Third control command as described herein in
A wireless device may receive a control command scheduling and/or activating a downlink reception, for example, if in an active time, duration, and/or period of a first DTX. The wireless device may receive the downlink reception based on at least two TCI states, for example, in response to receiving the control command scheduling and/or activating the downlink reception if in the active time, duration, and/or period of the first DTX.
A wireless device may receive a control command scheduling and/or activating a downlink reception, for example, if in an active time, duration, and/or period of a second DTX. The wireless device may receive the downlink reception based on at least two TCI states, for example, in response to receiving the control command scheduling and/or activating the downlink reception if in the active time, duration, and/or period of the second DTX.
A wireless device may receive a control command scheduling and/or activating a downlink reception, for example, if in an active time, duration, and/or period of a first DTX and an active time, duration, and/or period of a second DTX. The wireless device may receive the downlink reception based on at least two TCI states, for example, in response to receiving the control command scheduling and/or activating the downlink reception if in the active time, duration, and/or period of the first DTX and the active time, duration, and/or period of the second DTX.
A wireless device may receive a downlink reception based on at least two TCI states, for example, in response to the downlink reception being in an active time, duration, and/or period of a first DTX and the active time, duration, and/or period of a second DTX. At least one symbol of the downlink reception may be in the active time, duration, and/or period of the first DTX. The at least one symbol of the downlink reception may be in the active time, duration, and/or period of the second DTX. each symbol of the downlink reception may be in the active time, duration, and/or period of the first DTX.
One or more configuration parameters may comprise one or more first DTX configuration parameters of a first DTX of the cell. The one or more configuration parameters may not comprise one or more second DTX configuration parameters of a second DTX of a cell (e.g., the first DTX is configured and the second DTX is not configured). A control command (e.g., Third control command as described herein in
One or more configuration parameters may comprise one or more second DTX configuration parameters of a second DTX of a cell. The one or more configuration parameters may not comprise one or more first DTX configuration parameters of a first DTX of the cell (e.g., the second DTX is configured and the first DTX is not configured). A control command (e.g., Third control command as described herein in
One or more configuration parameters may comprise one or more first DTX configuration parameters of a first DTX of a cell. The one or more configuration parameters may comprise one or more second DTX configuration parameters of a second DTX of the cell. The control command (e.g., Third control command as described herein in
One or more configuration parameters may comprise one or more first DTX configuration parameters of a first DTX of a cell. The one or more configuration parameters may comprise one or more second DTX configuration parameters of a second DTX of the cell. A control command (e.g., Third control command as described herein in
A wireless device may receive, from a base station, one or more messages (e.g., RRC messages, RRC reconfiguration messages) comprising one or more configuration parameters. The base station may send (e.g., transmit) the one or more messages. The one or more configuration parameters may indicate, provide, and/or comprise, by a first DTX higher layer parameter (e.g., TRP-DTX-Config) of the one or more configuration parameters, a first DTX configuration of a cell (e.g., a serving cell, a non-serving cell, a candidate/target/neighbor cell). The one or more configuration parameters may indicate, provide, and/or comprise, by a second DTX higher layer parameter (e.g., TRP-DTX-Config2) of the one or more configuration parameters, a second DTX configuration of the cell, and if the wireless device sends (e.g., transmits(, provides, and/or reports a capability of two DTX for a cell (e.g., twoDTXcapability).
A wireless device may use two indicated TCI states, or both indicated TCI states or each TCI state of the two indicated TCI states, to a scheduled or an activated PDSCH reception if the first DTX configuration and the second DTX configuration are not configured by one or more messages, or the one or more configuration parameters.
A wireless device may use two indicated TCI states, or both indicated TCI states or each TCI state of the two indicated TCI states, to a scheduled or an activated PDSCH reception if the first DTX configuration is not configured by the one or more messages, or the one or more configuration parameters, and the scheduled and/or activated PDSCH reception overlaps with, or is in, an active time, period, and/or duration of a second DTX configuration.
A wireless device may use two indicated TCI states, or both indicated TCI states or each TCI state of the two indicated TCI states, to a scheduled or an activated PDSCH reception if the second DTX configuration is not configured by the one or more messages, or the one or more configuration parameters, and the scheduled and/or activated PDSCH reception overlaps with, or is in, an active time, period, and/or duration of a first DTX configuration.
A wireless device may use two indicated TCI states, or both indicated TCI states or each TCI state of the two indicated TCI states, to a scheduled or an activated PDSCH reception if the scheduled and/or activated PDSCH reception overlaps with, or is in, an active time, period, and/or duration of the first DTX configuration and an active time, period, and/or duration of a second DTX configuration.
Using a TCI state to a downlink reception may comprise receiving a downlink reception based on a reference signal indicated by the TCI state. At least one DM-RS port, or at least one DM-RS antenna port, of the downlink reception may be quasi co-located with the reference signal. A wireless device may receive the downlink reception with and/or using a spatial domain that receives a filter and/or beam that is the same as, or substantially the same as, a spatial domain that receives a filter and/or beam of the reference signal.
Using a TCI state to a downlink reception may comprise measuring a radio link quality (e.g., RSRP, SINR, SNR) of the downlink reception based on a reference signal indicated by the TCI state. At least one CSI-RS port, or at least one CSI-RS antenna port, of the downlink reception may be quasi co-located with the reference signal. The wireless device may measure the downlink reception with and/or using a spatial domain that receives a filter and/or beam that is the same as, or substantially the same as, a spatial domain that receives a filter and/or beam of the reference signal.
A wireless device may be indicated (e.g., provided), by a first DTX higher layer parameter (e.g., TRP-DTX-Config, DTX-Config1), a first DTX configuration of a cell, and, if the wireless device provides a capability of two DTXs per cell (e.g., twoDTXcapability), the wireless device may be provided, by a second DTX higher layer parameter (e.g., TRP2-DTX-Config, DTX-Config2), a second DTX configuration of the cell.
A wireless device may apply both of two indicated TCI states to a scheduled or an activated PDSCH reception if a first DTX configuration and/or a second DTX configuration are not configured, or the scheduled and/or activated PDSCH reception overlaps with, or is in, an active time, period, and/or duration of the first DTX configuration and an active time, period, and/or duration of the second DTX configuration.
A wireless device may receive a downlink reception (e.g., Downlink reception 2 2110 and Downlink reception 3 2115 in
A wireless device may fall back to a TCI state for a downlink reception associated and/or indicated with at least two TCI states. The wireless device may fall back to the TCI state from the at least two TCI states for the downlink reception associated and/or indicated with the at least two TCI states. The wireless device may fall back to using the TCI state for the downlink reception associated and/or indicated with the at least two TCI states.
A wireless device may receive a downlink reception based on a TCI state, for example, if in a non-active time of a DTX of a cell. The wireless device may use the TCI state for the downlink reception, for example, if in the non-active time of the DTX. The wireless device may fall back to the TCI state for the downlink reception, for example, if in the non-active time of the DTX.
DTX of a cell activated by a control command (e.g., Third control command as described herein in
A wireless device may receive a downlink reception (e.g., Downlink reception 2 2110 and Downlink reception 3 2115 in
A wireless device may receive a control command scheduling and/or activating a downlink reception, for example, if in a non-active time, duration, and/or period of a first DTX. The wireless device may receive the downlink reception based on a second TCI state, for example, in response to receiving the control command scheduling and/or activating the downlink reception if in the non-active time, duration, and/or period of the first DTX.
A wireless device may receive a control command scheduling and/or activating a downlink reception, for example, if in an active time, duration, and/or period of a second DTX. The wireless device may receive the downlink reception based on the second TCI state, for example, in response to receiving the control command scheduling and/or activating the downlink reception if in the active time, duration, and/or period of the second DTX.
A wireless device may receive a downlink reception based on a second TCI state of at least two TCI states, for example, in response to the downlink reception overlapping in time with a non-active time, duration, and/or period of the first DTX. The wireless device may receive the downlink reception based on the second TCI state of the at least two TCI states, for example, in response to the downlink reception being in the non-active time, duration, and/or period of the first DTX. The downlink reception may overlap in at least one symbol with the non-active time, duration, and/or period of the first DTX. each symbol of the downlink reception may overlap in time with the non-active time, duration, and/or period of the first DTX.
A wireless device may not receive a downlink reception based on a first TCI state of at least two TCI states, for example, in response to the downlink reception overlapping in time with a non-active time, duration, and/or period of a first DTX. The wireless device may not receive the downlink reception based on the first TCI state of the at least two TCI states, for example, in response to the downlink reception being in the non-active time, duration, and/or period of the first DTX.
One or more configuration parameters may comprise one or more second DTX configuration parameters of the second DTX of a cell. A control command (e.g., Third control command as described herein in
One or more configuration parameters may not comprise one or more second DTX configuration parameters of a second DTX of a cell (e.g., the second DTX is not configured). A wireless device may receive a downlink reception based on a second TCI state of at least two TCI states, for example, in response to the one or more configuration parameters not comprising the one or more second DTX configuration parameters of the second DTX of the cell.
One or more configuration parameters may comprise one or more second DTX configuration parameters of a second DTX of a cell (e.g., the second DTX is configured). The second DTX may not be activated by a wireless device and/or a base station. The wireless device may not receive a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the second DTX. The wireless device may receive the downlink reception based on a second TCI state of at least two TCI states, for example, in response to not receiving a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the second DTX of the cell.
In a second CJT scheme (e.g., cjtSchemeB), at least one DM-RS port of a downlink reception may be quasi co-located with a second reference signal with respect to a second quasi co-location type (e.g., QCL Type A) that comprises and/or indicates a second doppler shift, a second doppler spread, a second average delay, and/or a second delay spread. In the second CJT scheme, at least one DM-RS port of the downlink reception may be quasi co-located with a second reference signal with respect to the one or more second QCL parameters. The at least one DM-RS port of the downlink reception may be quasi co-located with the second reference signal with respect to the one or more second QCL parameters, for example, if in the non-active time, duration, and/or period of the first DTX. The at least one DM-RS port of the downlink reception may be quasi co-located with the second reference signal with respect to the one or more second QCL parameters, for example, if in the active time, duration, and/or period of the second DTX. The at least one DM-RS port of the downlink reception may be quasi co-located with the second reference signal with respect to the one or more second QCL parameters, for example, if the one or more configuration parameters do not comprise the one or more second DTX configuration parameters of the second DTX of the cell. The at least one DM-RS port of the downlink reception may be quasi co-located with the second reference signal with respect to the one or more second QCL parameters, for example, in response to not receiving a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the second DTX of the cell.
A DTX of a cell activated by a control command (e.g., Third control command as described herein in
A wireless device may receive a downlink reception based on a first TCI state of at least two TCI states, for example, if in a non-active time, duration, and/or period of the second DTX. The wireless device may not receive the downlink reception based on the second TCI state of the at least two TCI states, for example, if in the non-active time, duration, and/or period of the second DTX. The wireless device may apply the first TCI state for the downlink reception. The wireless device may use the first TCI state for the downlink reception.
A wireless device may fall back to a first TCI state from at least two TCI states for a downlink reception associated and/or indicated with the at least two TCI states, if in the non-active time, duration, and/or period of a second DTX. A wireless device may receive a control command scheduling and/or activating the downlink reception, for example, if in the non-active time, duration, and/or period of the second DTX. The wireless device may receive the downlink reception based on the first TCI state, for example, in response to receiving the control command scheduling and/or activating the downlink reception if in the non-active time, duration, and/or period of the second DTX.
A wireless device may receive a control command scheduling and/or activating a downlink reception, for example, if in an active time, duration, and/or period of a first DTX. The wireless device may receive the downlink reception based on a first TCI state, for example, in response to receiving the control command scheduling and/or activating the downlink reception if in the active time, duration, and/or period of the first DTX.
A wireless device may receive a downlink reception based on a first TCI state of at least two TCI states, for example, in response to the downlink reception overlapping in time with a non-active time, duration, and/or period of a second DTX. The wireless device may receive the downlink reception based on the first TCI state of the at least two TCI states, for example, in response to the downlink reception being in the non-active time, duration, and/or period of the second DTX. The downlink reception may overlap in at least one symbol with the non-active time, duration, and/or period of the second DTX. each symbol of the downlink reception may overlap in time with the non-active time, duration, and/or period of the second DTX.
A wireless device may not receive a downlink reception based on a second TCI state of at least two TCI states, for example, in response to the downlink reception overlapping in time with a non-active time, duration, and/or period of the second DTX. The wireless device may not receive the downlink reception based on the second TCI state of the at least two TCI states, for example, in response to the downlink reception being in the non-active time, duration, and/or period of the second DTX.
One or more configuration parameters may comprise one or more first DTX configuration parameters of a first DTX of a cell. A control command (e.g., Third control command as described herein in
One or more configuration parameters may not comprise one or more first DTX configuration parameters of a first DTX of a cell (e.g., the first DTX is not configured). A wireless device may receive a downlink reception based on the first TCI state of the at least two TCI states, for example, in response to the one or more configuration parameters not comprising the one or more first DTX configuration parameters of the first DTX of the cell.
One or more configuration parameters may comprise one or more first DTX configuration parameters of a first DTX of a cell (e.g., the first DTX is configured). The first DTX may not be activated by a wireless device and/or a base station. The wireless device may not receive a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the first DTX. The wireless device may receive the downlink reception based on a first TCI state of at least two TCI states, for example, in response to not receiving a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the first DTX of the cell.
A wireless device may apply a first indicated TCI state of two indicated TCI states to a scheduled or activated PDSCH reception. The wireless device may apply the first indicated TCI state of two indicated TCI states to a scheduled or activated PDSCH reception, for example, if the wireless device is configured and/or indicated to apply two indicated TCI states to a scheduled or an activated PDSCH reception (e.g., if a TCI selection field of DCI format 1_1/1_2 scheduling and/or activating the PDSCH reception is set/equal to ‘10’, or if the wireless device is not configured, indicated, and/or provided with a higher layer parameter tciSelection-PresentInDCI, or if the wireless device is configured, indicated, and/or provided with a higher layer parameter applyIndicatedTCIState set to ‘both’), and if the PDSCH reception overlaps with, or is in, a non-active time, period, and/or duration of the second DTX configuration, and if the first DTX configuration is not configured, indicated, and/or provided or if the PDSCH reception overlaps with, or is in, an active time, period, and/or duration of the first DTX configuration.
A wireless device may apply a second indicated TCI state of the two indicated TCI states to the scheduled or activated PDSCH reception. The wireless device may apply a second indicated TCI state of the two indicated TCI states to the scheduled or activated PDSCH reception, for example, if the wireless device is configured and/or indicated to apply two indicated TCI states to a scheduled or an activated PDSCH reception (e.g., if a TCI selection field of DCI format 1_1/1_2 scheduling and/or activating the PDSCH reception is set/equal to ‘10’, or if the wireless device is not configured, indicated, and/or provided with a higher layer parameter tciSelection-PresentInDCI, or if the wireless device is configured, indicated, and/or provided with a higher layer parameter applyIndicatedTCIState set to ‘both’), and if the PDSCH reception overlaps with, or is in, a non-active time, period, and/or duration of the first DTX configuration, and if the second DTX configuration is not configured, indicated, and/or provided or if the PDSCH reception overlaps with, or is in, an active time, period, and/or duration of the second DTX configuration. The wireless device may assume that PDSCH DM-RS port(s) of the PDSCH reception are quasi co-located (QCLed) with downlink reference signal(s) of the second indicated TCI state with respect to QCL-TypeA {Doppler shift, Doppler spread, average delay, delay spread}, for example, If the wireless device is configured, indicated, and/or provided with a higher layer parameter cjtSchemeB.
A base station may apply a first indicated TCI state of two indicated TCI states to a scheduled or activated PDSCH reception. The base station may apply the first indicated TCI state of two indicated TCI states to a scheduled or activated PDSCH reception, for example, if the base station indicates, to a wireless device, to apply two indicated TCI states to a scheduled or an activated PDSCH reception (e.g., if a TCI selection field of DCI format 1_1/1_2 scheduling and/or activating the PDSCH reception is set/equal to ‘10’, or if the base station configures, indicates, and/or provides the wireless device with a higher layer parameter tciSelection-PresentInDCI, or if the base station configures, indicates, and/or provides the wireless device with a higher layer parameter applyIndicatedTCIState set to ‘both’), and if the PDSCH reception overlaps with, or is in, a non-active time, period, and/or duration of the second DTX configuration, and if the first DTX configuration is not configured, indicated, and/or provided or if the PDSCH reception overlaps with, or is in, an active time, period, and/or duration of the first DTX configuration.
A base station may apply a second indicated TCI state of the two indicated TCI states to the scheduled or activated PDSCH reception. The base station may apply a second indicated TCI state of the two indicated TCI states to the scheduled or activated PDSCH reception, for example, if the base station indicates, to a wireless device, to apply two indicated TCI states to a scheduled or an activated PDSCH reception (e.g., if a TCI selection field of DCI format 1_1/1_2 scheduling and/or activating the PDSCH reception is set/equal to ‘10’, or if the base station configures, indicates, and/or provides the wireless device with a higher layer parameter tciSelection-PresentInDCI, or if the base station configures, indicates, and/or provides the wireless device with a higher layer parameter applyIndicatedTCIState set to ‘both’), and if the PDSCH reception overlaps with, or is in, a non-active time, period, and/or duration of the first DTX configuration, and if the second DTX configuration is not configured, indicated, and/or provided or if the PDSCH reception overlaps with, or is in, an active time, period, and/or duration of the second DTX configuration. If the base station configures, indicates, and/or provides the wireless device with a higher layer parameter cjtSchemeB, the wireless device and/or the base station may assume that PDSCH DM-RS port(s) of the PDSCH reception are quasi co-located (QCLed) with downlink reference signal(s) of the second indicated TCI state with respect to QCL-TypeA {Doppler shift, Doppler spread, average delay, delay spread}.
A wireless device may receive a downlink reception (e.g., Downlink reception 2 2110 and Downlink reception 3 2115 in
A wireless device may receive, if in a non-active time of the DTX of a cell, a downlink reception based on a TCI state of at least two TCI states, for example, in response to the wireless device supporting, being capable of, and/or reporting dynamic switching between a single TRP and a multi-TRP for downlink receptions, or between the single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states. The wireless device may use, if in the non-active time of the DTX, the TCI state for the downlink reception, for example, in response to the wireless device supporting, being capable of, and/or reporting dynamic switching between the single TRP and the multi-TRP for downlink receptions, or between the single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states. The wireless device may fall back to the TCI state for the downlink reception if in the non-active time of the DTX, for example, in response to the wireless device supporting, being capable of, and/or reporting dynamic switching between the single TRP and the multi-TRP for downlink receptions, or between the single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states.
Falling back to a TCI state for a downlink reception may comprise switching to a TCI state for the downlink reception. The wireless device may not receive, if in a non-active time of a DTX, the downlink reception based on a different TCI state than the TCI state. The wireless device may not receive, if in the non-active time of the DTX, the downlink reception based on a different TCI state than the TCI state, for example, after falling back to the TCI state for the downlink reception.
A wireless device may receive, if in a non-active time, duration, and/or period of a first DTX, a downlink reception (e.g., Downlink reception 2 2110 and Downlink reception 3 2115 in
A wireless device may receive, if in a non-active time, duration, and/or period of a first DTX, a downlink reception (e.g., Downlink reception 2 2110 and Downlink reception 3 2115 in
A wireless device may receive, if in a non-active time, duration, and/or period of a second DTX, a downlink reception based on a first TCI state of at least two TCI states, for example, in response to a capability message comprising a dynamic switching parameter (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2). The downlink reception may overlap in time with an active time, duration, and/or period of the first DTX. one or more configuration parameters may not comprise one or more first DTX configuration parameters of a first DTX of the cell (e.g., the first DTX is not configured). The wireless device may not receive a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the first DTX of the cell.
A wireless device may receive, if in a non-active time, duration, and/or period of a second DTX, a downlink reception based on a first TCI state of at least two TCI states, for example, in response to the wireless device supporting, being capable of, and/or reporting dynamic switching between a single TRP and a multi-TRP for downlink receptions, or between a single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states. The downlink reception may overlap in time with an active time, duration, and/or period of the first DTX. one or more configuration parameters may not comprise one or more first DTX configuration parameters of a first DTX of the cell (e.g., the first DTX is not configured). The wireless device may not receive a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the first DTX of the cell.
A wireless device may receive a downlink reception (e.g., Downlink reception 2 and Downlink reception 3 in
A wireless device may receive, if in a non-active time of a DTX of a cell, a downlink reception based on at least two TCI states, for example, in response to the wireless device not supporting, not being capable of, and/or not reporting, dynamic switching between a single TRP and a multi-TRP for downlink receptions, or between a single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states. The wireless device may use, if in the non-active time of the DTX, the at least two TCI states for the downlink reception, for example, in response to the wireless device not supporting, not being capable of, and/or not reporting, dynamic switching between the single TRP and the multi-TRP for downlink receptions, or between the single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states. The wireless device may not fall back to a TCI state of the at least two TCI states for the downlink reception if in the non-active time of the DTX, for example, in response to the wireless device not supporting, not being capable of, and/or not reporting, dynamic switching between the single TRP and the multi-TRP for downlink receptions, or between the single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states.
A wireless device may receive, if in a non-active time, duration, and/or period of a first DTX, a downlink reception (e.g., Downlink reception 2 and Downlink reception 3 in
A wireless device may receive, if in a non-active time, duration, and/or period of a first DTX, a downlink reception (e.g., Downlink reception 2 and Downlink reception 3 in
A wireless device may receive, if in a non-active time, duration, and/or period of a second DTX, a downlink reception based on at least two TCI states, for example, in response to a capability message not comprising a dynamic switching parameter (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2). The downlink reception may overlap in time with an active time, duration, and/or period of a first DTX. one or more configuration parameters may not comprise one or more first DTX configuration parameters of a first DTX of the cell (e.g., the first DTX is not configured). The wireless device may not receive a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the first DTX of the cell.
A wireless device may receive, if in a non-active time, duration, and/or period of a second DTX, a downlink reception based on at least two TCI states, for example, in response to the wireless device not supporting, not being capable of, and/or not reporting, dynamic switching between a single TRP and a multi-TRP for downlink receptions, or between a single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states. The downlink reception may overlap in time with an active time, duration, and/or period of the first DTX. one or more configuration parameters may not comprise one or more first DTX configuration parameters of a first DTX of the cell (e.g., the first DTX is not configured). The wireless device may not receive a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the first DTX of the cell.
A wireless device may not receive a downlink reception (e.g., Downlink reception 2 and Downlink reception 3 in
Not receiving a downlink reception may comprise, for example, ignoring the downlink reception. A wireless device may ignore the downlink reception by not receiving the downlink reception.
Not receiving a downlink reception may comprise, for example, not monitoring the downlink reception. A wireless device may not monitor the downlink reception.
Not receiving a downlink reception may comprise, for example, discarding the downlink reception. A wireless device may discard the downlink reception by not receiving the downlink reception.
Not receiving a downlink reception may comprise, for example, cancelling the downlink reception. A wireless device may cancel the downlink reception by not receiving the downlink reception.
A wireless device may not receive, if in a non-active time of a DTX of a cell, a downlink reception, for example, in response to the wireless device not supporting, not being capable of, and/or not reporting, dynamic switching between a single TRP and a multi-TRP for downlink receptions, or between a single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states. The wireless device may not use, if in an non-active time of the DTX, one or more TCI states of at least two TCI states for the downlink reception, for example, in response to the wireless device not supporting, not being capable of, and/or not reporting, dynamic switching between the single TRP and the multi-TRP for downlink receptions, or between the single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states.
A wireless device may not receive, if in a non-active time, duration, and/or period of a first DTX, a downlink reception (e.g., Downlink reception 2 and Downlink reception 3 in
A wireless device may not receive, if in a non-active time, duration, and/or period of a first DTX, a downlink reception (e.g., Downlink reception 2 and Downlink reception 3 in
A wireless device may not receive, if in a non-active time, duration, and/or period of a second DTX, a downlink reception, for example, in response to a capability message not comprising a dynamic switching parameter (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2). The downlink reception may overlap in time with an active time, duration, and/or period of the first DTX. one or more configuration parameters may not comprise one or more first DTX configuration parameters of a first DTX of a cell (e.g., the first DTX is not configured). The wireless device may not receive a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the first DTX of the cell.
A wireless device may not receive, if in a non-active time, duration, and/or period of a second DTX, a downlink reception, for example, in response to the wireless device not supporting, not being capable of, and/or not reporting, dynamic switching between a single TRP and a multi-TRP for downlink receptions, or between a single-TRP and a PDSCH SFN scheme, or between a single TCI state and multiple TCI states. The downlink reception may overlap in time with an active time, duration, and/or period of a first DTX. one or more configuration parameters may not comprise one or more first DTX configuration parameters of a first DTX of the cell (e.g., the first DTX is not configured). The wireless device may not receive a control command (e.g., DCI format 2_9, DCI format 2_10, and the like) indicating activation of the first DTX of the cell.
A wireless device may not receive, if in a non-active time, duration, and/or period of a first DTX and a non-active time, duration, and/or period of a second DTX, a downlink reception.
A scheduled or an activated PDSCH reception associated with two indicated TCI states (e.g., both indicated TCI states) may not be impacted by a first DTX configuration or a second DTX configuration, if a wireless device does not support a dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, or sfn-SchemeB-DynamicSwitching2). The wireless device may receive the scheduled and/or activated PDSCH reception based on the two indicated TCI states (e.g., both or each of the two indicated TCI states).
A scheduled or an activated PDSCH reception associated with two indicated TCI states (e.g., both indicated TCI states) may not be impacted by a non-active time, duration, and/or period of a first DTX configuration or a non-active time, duration, and/or period of a second DTX configuration, if a wireless device does not support a dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, or sfn-SchemeB-DynamicSwitching2). The wireless device may receive, if in an non-active time, duration, and/or period of the first DTX configuration or the non-active time, duration, and/or period of the second DTX configuration, the scheduled and/or activated PDSCH reception based on the two indicated TCI states (e.g., both or each of the two indicated TCI states).
A base station may send (e.g., transmit), to a wireless device, a scheduled or an activated PDSCH reception and/or transmission based on two indicated TCI states, if the base station does not receive, from the wireless device, a capability message indicating support and/or capability of a dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, or sfn-SchemeB-DynamicSwitching2).
A base station may send (e.g., transmit), to a wireless device, and if in a non-active time, duration, and/or period of the first DTX configuration or a non-active time, duration, and/or period of the second DTX configuration, a scheduled or an activated PDSCH reception and/or transmission based on two indicated TCI states, if the base station does not receive, from the wireless device, a capability message indicating support and/or capability of a dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, or sfn-SchemeB-DynamicSwitching2).
A wireless device configured with a first DTX configuration or a second DTX configuration may not expect to receive, if in a non-active time, period, and/or duration of the first DTX configuration or the second DTX configuration, a scheduled and/or activated PDSCH reception, if the wireless device is configured, scheduled, and/or indicated to apply two indicated TCI states to a scheduled or an activated PDSCH reception, and if the wireless device does not support a dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, or sfn-SchemeB-DynamicSwitching2).
A wireless device configured and activated with a first DTX configuration or with a second DTX configuration may not expect to receive, if in a non-active time, period, and/or duration of the first DTX configuration or the second DTX configuration, a scheduled and/or activated PDSCH reception, if a wireless device is configured, scheduled, and/or indicated to apply two indicated TCI states to a scheduled or an activated PDSCH reception, and if the wireless device does not support a dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, or sfn-SchemeB-DynamicSwitching2).
A base station may not send (e.g., transmit), to a wireless device configured with a first DTX configuration or a second DTX configuration, and if in non-active time, period, and/or duration of the first DTX configuration or the second DTX configuration, a scheduled and/or activated PDSCH reception and/or transmission, if the base station configures, schedules, and/or indicates, to the wireless device, to apply two indicated TCI states to a scheduled or an activated PDSCH reception and/or transmission, and if the base station does not receive, from the wireless device, a capability message indicating support and/or capability of a dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, or sfn-SchemeB-DynamicSwitching2).
A base station may not send (e.g., transmit), to a wireless device configured and activated with a first DTX configuration or with a second DTX configuration, and if in non-active time, period, and/or duration of the first DTX configuration or the second DTX configuration, a scheduled and/or activated PDSCH reception and/or transmission, if the base station configures, schedules, and/or indicates, to the wireless device, to apply two indicated TCI states to a scheduled or an activated PDSCH reception and/or transmission, and if the base station does not receive, from the wireless device, a capability message indicating support and/or capability of a dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, or sfn-SchemeB-DynamicSwitching2).
The one or more configuration parameters may indicate at least two DTXs (e.g., at least two DTX configurations) for/of the cell. The at least two DTXs of the cell may comprise a first DTX of the cell and a second DTX of the cell. In step 2450 of
The base station may send (e.g., transmit) a control command (e.g., MAC-CE, DCI, downlink control command, downlink message, activation command, and the like) indicating at least two TCI states (e.g., at least two joint TCI states, at least two downlink TCI states) for the cell or a downlink BWP of the cell. The wireless device may receive the control command. The at least two TCI states may comprise a first TCI state and a second TCI state.
In step 2455 of
The control command may schedule the downlink reception. The control command may activate the downlink reception of an SPS configuration. The downlink reception may be, for example, an SPS PDSCH reception. The control command may indicate activation of the SPS configuration.
The downlink reception, of 2455 of
The downlink reception may overlap in time with an active time, duration, and/or period of the first DTX of the cell and an active time, duration, and/or period of the second DTX of the cell. The downlink reception may not overlap in time with a non-active time, duration, and/or period of the first DTX of the cell and a non-active time, duration, and/or period of the second DTX of the cell.
The downlink reception may be in (e.g., within, during, concurrent with, etc.) an active time, duration, and/or period of the first DTX of the cell and an active time, duration, and/or period of the second DTX of the cell. The downlink reception may not be in (e.g., within, during, concurrent with, etc.) a non-active time, duration, and/or period of the first DTX of the cell and a non-active time, duration, and/or period of the second DTX of the cell.
In step 2415 of
In step 2420 of
In step 2465 of
The downlink reception may not overlap in time with an active time, duration, and/or period of the first DTX of the cell and an active time, duration, and/or period of the second DTX of the cell. The downlink reception may overlap in time with a non-active time, duration, and/or period of the first DTX of the cell and a non-active time, duration, and/or period of the second DTX of the cell.
the downlink reception may not be in (e.g., within, during, concurrent with, etc.) an active time, duration, and/or period of the first DTX of the cell and an active time, duration, and/or period of the second DTX of the cell. The downlink reception may be in (e.g., within, during, concurrent with, etc.) a non-active time, duration, and/or period of the first DTX of the cell and a non-active time, duration, and/or period of the second DTX of the cell.
The wireless device may not receive (or may discard or may ignore or may cancel) the downlink reception, for example, in response to the downlink reception not overlapping in time with the active time, duration, and/or period of the first DTX and the active time, duration, and/or period of the second DTX. The wireless device may not receive (or may discard or may ignore or may cancel) the downlink reception, for example, in response to the downlink reception overlapping in time with the non-active time, duration, and/or period of the first DTX and the non-active time, duration, and/or period of the second DTX.
The base station may not send (e.g., transmit) (or may discard or may ignore or may cancel) the downlink reception, for example, in response to the downlink reception not overlapping in time with the active time, duration, and/or period of the first DTX and the active time, duration, and/or period of the second DTX. The base station may not send (e.g., transmit) (or may discard or may ignore or may cancel) the downlink reception, for example, in response to the downlink reception overlapping in time with the non-active time, duration, and/or period of the first DTX and the non-active time, duration, and/or period of the second DTX.
In step 2425 of
The downlink reception may be in (e.g., within, during, concurrent with, etc.) an active time, duration, and/or period of the first DTX of the cell. The downlink reception may not be in (e.g., within, during, concurrent with, etc.) an active time, duration, and/or period of the second DTX of the cell. The downlink reception may not be in (e.g., within, during, concurrent with, etc.) a non-active time, duration, and/or period of the first DTX of the cell. The downlink reception may be in/with a non-active time, duration, and/or period of the second DTX of the cell.
In step 2430 of
In step 2475 of
In step 2430 of
In step 2475 of
The downlink reception may overlap in time with an active time, duration, and/or period of the second DTX of the cell. The downlink reception may not overlap in time with an active time, duration, and/or period of the first DTX of the cell. The downlink reception may not overlap in time with a non-active time, duration, and/or period of the second DTX of the cell. The downlink reception may overlap in time with a non-active time, duration, and/or period of the first DTX of the cell.
The downlink reception may be in (e.g., within, during, concurrent with, etc.) an active time, duration, and/or period of the second DTX of the cell. The downlink reception may not be in (e.g., within, during, concurrent with, etc.) an active time, duration, and/or period of the first DTX of the cell. The downlink reception may not be in (e.g., within, during, concurrent with, etc.) a non-active time, duration, and/or period of the second DTX of the cell. The downlink reception may be in/with a non-active time, duration, and/or period of the first DTX of the cell.
In step 2435 of
In step 2480 of
In step 2435 of
In step 2480 of
The wireless device may receive, if in a non-active time, duration, and/or period of a DTX of the at least two DTXs of a cell, the downlink reception based on the TCI state or the at least two TCI states. In step 2555 of
In step 2560 of
The wireless device may receive, if in a non-active time, duration, and/or period of a DTX of the at least two DTXs of the cell, the downlink reception using a TCI state (e.g., one TCI state, a single TCI state, etc.) among the at least two TCI states or using the at least two TCI states, based on whether the wireless device supports dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2) between a single TRP and a multi-TRP for downlink receptions, between a single-TRP and a PDSCH SFN scheme, between a single-TRP mode and/or operation and a multi-TRP mode and/or operation, or between a single TCI state and multiple TCI states.
The wireless device may receive, if in a non-active time, duration, and/or period of a DTX of the cell, the downlink reception using a TCI state (e.g., one TCI state, a single TCI state, etc.) among the at least two TCI states or using the at least two TCI states, based on whether the wireless device supports dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2) between a single TRP and a multi-TRP for downlink receptions, between a single-TRP and a PDSCH SFN scheme, between a single-TRP mode and/or operation and a multi-TRP mode and/or operation, or between a single TCI state and multiple TCI states. The downlink reception may overlap in time with (e.g., be in, be within, be during, be concurrent with, etc.) an active time, period, and/or duration of a different DTX, of the at least two DTXs, from the DTX.
In step 2515 of
In step 2530, the wireless device may receive the downlink reception using the TCI state (e.g., one TCI state, a single TCI state, etc.) among the at least two TCI states, for example, based on sending (e.g., transmitting) the capability message comprising the dynamic switching parameter. The wireless device may receive the downlink reception using the TCI state (e.g., one TCI state, a single TCI state, etc.) among the at least two TCI states, for example, based on the wireless device supporting, being capable of, and/or reporting dynamic switching between the single TRP and the multi-TRP for downlink receptions.
The TCI state may be the first TCI state of the at least two TCI states. The DTX may be the second DTX of the at least two DTXs of the cell. The wireless device may receive, if in a non-active time, duration, and/or period of the second DTX, the downlink reception based on the first TCI state. The wireless device may receive, if in an active time, duration, and/or period of the first DTX, the downlink reception based on the first TCI state. The wireless device may not receive, if in the non-active time, duration, and/or period of the second DTX, the downlink reception based on the second TCI state.
The TCI state may be the second TCI state of the at least two TCI states. The DTX may be the first DTX of the at least two DTXs of the cell. The wireless device may receive, if in a non-active time, duration, and/or period of the first DTX, the downlink reception based on the second TCI state. The wireless device may receive, if in an active time, duration, and/or period of the second DTX, the downlink reception based on the second TCI state. The wireless device may not receive, if in the non-active time, duration, and/or period of the first DTX, the downlink reception based on the first TCI state.
In step 2520 of
In step 2535 of
The wireless device may receive, if in a non-active time, duration, and/or period of the second DTX, the downlink reception based on the at least two TCI states. The wireless device may receive, if in an active time, duration, and/or period of the first DTX, the downlink reception based on the at least two TCI states.
The wireless device may receive, if in a non-active time, duration, and/or period of the first DTX, the downlink reception based on the at least two TCI states. The wireless device may receive, if in an active time, duration, and/or period of the second DTX, the downlink reception based on the at least two TCI states.
In step 2580, the base station may send (e.g., transmit) the downlink reception using a TCI state (e.g., one TCI state, a single TCI state, etc.) among the at least two TCI states or using the at least two TCI states, based on whether the wireless device supports dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2) between a single TRP and a multi-TRP for downlink receptions, between a single-TRP and a PDSCH SFN scheme, between a single-TRP mode and/or operation and a multi-TRP mode and/or operation, or between a single TCI state and multiple TCI states.
The base station may send (e.g., transmit), if in a non-active time, duration, and/or period of a DTX of the at least two DTXs of the cell, the downlink reception based on the TCI state or the at least two TCI states.
The base station may send (e.g., transmit), if in a non-active time, duration, and/or period of a DTX of the at least two DTXs of the cell, the downlink reception using a TCI state (e.g., one TCI state, a single TCI state, etc.) among the at least two TCI states or using the at least two TCI states, based on whether the wireless device supports dynamic switching (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2) between a single TRP and a multi-TRP for downlink receptions, between a single-TRP and a PDSCH SFN scheme, between a single-TRP mode and/or operation and a multi-TRP mode and/or operation, or between a single TCI state and multiple TCI states.
The downlink reception may overlap in time with (or may be in (e.g., within, during, concurrent with, etc.)) an active time, period, and/or duration of a different DTX, of the at least two DTXs, from the DTX.
In step 2570, the base station may receive, from the wireless device, a capability message (e.g., wireless device capability message). The capability message may comprise a dynamic switching parameter (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2).
In step 2580, the base station may send (e.g., transmit) the downlink reception using the TCI state (e.g., one TCI state, a single TCI state, etc.) among the at least two TCI states, for example, based on receiving the capability message comprising the dynamic switching parameter. The base station may send (e.g., transmit) the downlink reception using the TCI state (e.g., one TCI state, a single TCI state, etc.) among the at least two TCI states, for example, based on the wireless device supporting, being capable of, and/or reporting dynamic switching between the single TRP and the multi-TRP for downlink receptions.
The TCI state may be the first TCI state of the at least two TCI states. The DTX may be the second DTX of the at least two DTXs of the cell. The base station may send (e.g., transmit), if in a non-active time, duration, and/or period of the second DTX, the downlink reception based on the first TCI state. The base station may send (e.g., transmit), if in an active time, duration, and/or period of the first DTX, the downlink reception based on the first TCI state. The base station may not send (e.g., transmit), if in the non-active time, duration, and/or period of the second DTX, the downlink reception based on the second TCI state.
The TCI state may be the second TCI state of the at least two TCI states. The DTX may be the first DTX of the at least two DTXs of the cell. The base station may send (e.g., transmit), if in a non-active time, duration, and/or period of the first DTX, the downlink reception based on the second TCI state. The base station may send (e.g., transmit), if in an active time, duration, and/or period of the second DTX, the downlink reception based on the second TCI state. The base station may not send (e.g., transmit), if in the non-active time, duration, and/or period of the first DTX, the downlink reception based on the first TCI state.
In step 2570, the base station may receive, from the wireless device, a capability message (e.g., wireless device capability message). The capability message may not comprise a dynamic switching parameter (e.g., sfn-SchemeA-DynamicSwitching, sfn-SchemeB-DynamicSwitching, sfn-SchemeA-DynamicSwitching2, sfn-SchemeB-DynamicSwitching2).
In step 2585, the base station may send (e.g., transmit) the downlink reception using the at least two TCI states, for example, based on receiving the capability message that does not comprise the dynamic switching parameter. The base station may send (e.g., transmit) the downlink reception using the at least two TCI states, for example, based on the wireless device not supporting, not being capable of, and/or not reporting, dynamic switching between the single TRP and the multi-TRP for downlink receptions.
The base station may send (e.g., transmit), if in a non-active time, duration, and/or period of the second DTX, the downlink reception based on the at least two TCI states. The base station may send (e.g., transmit), if in an active time, duration, and/or period of the first DTX, the downlink reception based on the at least two TCI states.
The base station may send (e.g., transmit), if in a non-active time, duration, and/or period of the first DTX, the downlink reception based on the at least two TCI states. The base station may send (e.g., transmit), if in an active time, duration, and/or period of the second DTX, the downlink reception based on the at least two TCI states.
A downlink reception by a wireless device (or from the perspective of a wireless device) may be seen as (or may be replaced with) a downlink transmission by a base station (or from the perspective of a base station).
A base station may send (e.g., transmit) a downlink reception (or a downlink transmission) based on a TCI state. The base station may send (e.g., transmit) the downlink reception with and/or using a spatial domain transmission/transmitting filter/beam that is determined based on a reference signal indicated by the TCI state.
A base station may send (e.g., transmit) a downlink reception (or a downlink transmission) based on a TCI state. The base station may send (e.g., transmit) the downlink reception with and/or using a spatial domain transmission/transmitting filter/beam. The base station may determine the spatial domain transmission/transmitting filter/beam based on a spatial domain that receives a filter and/or beam used, by the wireless device, for reception of a reference signal indicated by the TCI state.
A wireless device may receive a single PDSCH transmission occasion of the transport block with each TCI state associated to a non-overlapping frequency domain resource allocation. The wireless device may receive the single PDSCH transmission occasion of the transport block with each TCI state associated to a non-overlapping frequency domain resource allocation, for example, if the wireless device is configured by a higher layer parameter repetitionScheme set to one of ‘fdmSchemeA’, ‘fdmSchemeB’, ‘tdmSchemeA’, and if the wireless device is indicated with DM-RS port(s) within one CDM group by ‘Antenna Port(s)’ field in DCI scheduling and/or activating a transport block (e.g., or a PDSCH reception or a downlink reception), if the wireless device is not configured with a higher layer parameter dl-OrJointTCI-StateList and is indicated with two TCI states in a codepoint of ‘Transmission Configuration Indication’ field in the DCI, or if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList and is indicated with two joint and/or downlink TCI states in a codepoint of ‘TCI selection’ field in the DCI, or if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList and the wireless device is not configured with a higher layer parameter tciSelection-PresentInDCI, and if the two TCI states or the two joint and/or downlink TCI states are indicated in the DCI and the higher layer parameter repetitionScheme is set to ‘fdmSchemeA’.
A wireless device may receive two PDSCH transmission occasions of the (same) transport block with each TCI state associated to a PDSCH transmission occasion which has non-overlapping frequency domain resource allocation with respect to the other PDSCH transmission occasion. The wireless device may receive two PDSCH transmission occasions of the (same) transport block with each TCI state associated to a PDSCH transmission occasion which has non-overlapping frequency domain resource allocation with respect to the other PDSCH transmission occasion, for example, if the wireless device is configured by a higher layer parameter repetitionScheme set to one of ‘fdmSchemeA’, ‘fdmSchemeB’, ‘tdmSchemeA’, and if the wireless device is indicated with DM-RS port(s) within one CDM group by ‘Antenna Port(s)’ field in DCI scheduling and/or activating a transport block (e.g., or a PDSCH reception or a downlink reception), if the wireless device is not configured with a higher layer parameter dl-OrJointTCI-StateList and is indicated with two TCI states in a codepoint of ‘Transmission Configuration Indication’ field in the DCI, or if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList and is indicated with two joint and/or downlink TCI states in a codepoint of ‘TCI selection’ field in the DCI, or if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList and the wireless device is not configured with a higher layer parameter tciSelection-PresentInDCI, and if the two TCI states or the two joint and/or downlink TCI states are indicated in the DCI and the higher layer parameter repetitionScheme is set to ‘fdmSchemeB’.
A wireless device may receive two PDSCH transmission occasions of the (same) transport block with each TCI state associated to a PDSCH transmission occasion which has non-overlapping time domain resource allocation with respect to the other PDSCH transmission occasion and both PDSCH transmission occasions may be received, by the wireless device, within a slot. The wireless device may receive two PDSCH transmission occasions of the (same) transport block with each TCI state associated to a PDSCH transmission occasion which has non-overlapping time domain resource allocation with respect to the other PDSCH transmission occasion and both PDSCH transmission occasions may be received, by the wireless device, within a slot, for example, if the wireless device is configured by a higher layer parameter repetitionScheme set to one of ‘fdmSchemeA’ ‘fdmSchemeB’, ‘tdmSchemeA’, and if the wireless device is indicated with DM-RS port(s) within one CDM group by ‘Antenna Port(s)’ field in DCI scheduling and/or activating a transport block (e.g., or a PDSCH reception or a downlink reception), if the wireless device is not configured with a higher layer parameter dl-OrJointTCI-StateList and is indicated with two TCI states in a codepoint of ‘Transmission Configuration Indication’ field in the DCI, or if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList and is indicated with two joint and/or downlink TCI states in a codepoint of ‘TCI selection’ field in the DCI, or if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList and the wireless device is not configured with a higher layer parameter tciSelection-PresentInDCI, and if the two TCI states or the two joint and/or downlink TCI states are indicated in the DCI and the higher layer parameter repetitionScheme is set to ‘tdmSchemeA’.
A wireless device, may expect to be indicated, by a base station with one or two TCI states in a codepoint of ‘Transmission Configuration Indication’ field in DCI scheduling and/or activating a transport block (or a PDSCH reception or a downlink reception), for example, if the wireless device is not configured with a higher layer parameter dl-OrJointTCI-StateList, and if the wireless device is configured by a higher layer parameter repetitionNumber in a higher layer parameter PDSCH-TimeDomainResourceAllocation.
A wireless device, may expect to be indicated, by a base station with one or two joint and/or downlink TCI states in a codepoint of ‘TCI selection’ field in DCI scheduling and/or activating a transport block (or a PDSCH reception or a downlink reception), for example, if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList, and if the wireless device is configured by a higher layer parameter repetitionNumber in a higher layer parameter PDSCH-TimeDomainResourceAllocation. This, together with a ‘Time domain resource assignment’ field, in the DCI, indicating an entry which comprises the higher layer parameter repetitionNumber in the higher layer parameter PDSCH-TimeDomainResourceAllocation and DM-RS port(s) within one CDM group in ‘Antenna Port(s)’ field in the DCI. The wireless device may expect to receive multiple slot level PDSCH transmission occasions of the (same) transport block with the two TCI states or the two joint and/or downlink TCI states used across multiple PDSCH transmission occasions in the higher layer parameter repetitionNumber consecutive slots, for example, if two TCI states or two joint and/or downlink TCI states are indicated in the DCI. The wireless device may expect to receive multiple slot level PDSCH transmission occasions of the (same) transport block with one TCI state or one joint and/or downlink TCI state used across multiple PDSCH transmission occasions in the higher layer parameter repetitionNumber consecutive slots, for example, if one TCI state or one joint and/or downlink TCI state is indicated in the DCI.
A wireless device may receive, or may expect to receive, multiple slot level PDSCH transmission occasions of a transport block (e.g., a same transport block) with two joint and/or downlink TCI states used across multiple PDSCH transmission occasions in the higher layer parameter repetitionNumber consecutive slots, if a wireless device is configured by a higher layer parameter repetitionNumber in a higher layer parameter PDSCH-TimeDomainResourceAllocation and is not configured with a higher layer parameter tciSelection-PresentInDCI, and if the wireless device is indicated with a ‘Time domain resource assignment’ field, in DCI scheduling and/or activating a transport block, indicating an entry which comprises the higher layer parameter repetitionNumber in the higher layer parameter PDSCH-TimeDomainResourceAllocation and indicated with DM-RS port(s) within one CDM group in ‘Antenna Port(s)’ field in the DCI.
A wireless device may receive a single PDSCH scheduled and/or activated by the DCI. A first DM-RS port of the DM-RS ports may be associated with a first TCI state of the two TCI states or a first joint and/or downlink TCI state of the two joint and/or downlink TCI states. A second DM-RS port of the DM-RS ports may be associated with a second TCI state of the two TCI states or a second joint and/or downlink TCI state of the two joint and/or downlink TCI states.
The wireless device may receive a single PDSCH scheduled and/or activated by the DCI, for example, if a wireless device is not indicated with ‘Time domain resource assignment’ field, in DCI, indicating an entry which comprises a higher layer parameter repetitionNumber in a higher layer parameter PDSCH-TimeDomainResourceAllocation, and if the wireless device. The indication may be for states in a codepoint of ‘Transmission Configuration Indication’ field in the DCI, for example, if the wireless device is not configured with a higher layer parameter dl-OrJointTCI-StateList. The indication may be for two joint and/or downlink TCI states in a codepoint of ‘TCI selection’ field in the DCI, for example, if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList. The indication may not be configured with a higher layer parameter tciSelection-PresentInDCI, for example, if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList, if the wireless device is indicated with DM-RS ports within two CDM groups in ‘Antenna Port(s)’ field in the DCI, and if the wireless device is not configured with a higher layer parameter sfnSchemePdsch.
An entry, comprising a higher layer parameter repetitionNumber in a higher layer parameter PDSCH-TimeDomainResourceAllocation, may be indicated, for example, if a wireless device is not indicated with ‘Time domain resource assignment’ field, in DCI scheduling and/or activating a PDSCH reception. A wireless device may be indicated with one TCI state in a codepoint of ‘Transmission Configuration Indication’ field in the DCI, for example, if the wireless device is not configured with a higher layer parameter dl-OrJointTCI-StateList. The wireless device may be indicated with one joint and/or downlink TCI state in a codepoint of ‘TCI selection’ field in the DCI, for example, if the wireless device is configured with a higher layer parameter dl-OrJointTCI-StateList. The wireless device may receive the PDSCH reception based on the one TCI state or the one joint and/or downlink TCI state.
A wireless device may receive one or more messages. The one or more messages may comprise a repetition scheme parameter that may indicate a time domain scheme or a frequency domain scheme and/or and a downlink-or-joint transmission configuration indication (TCI) state list. The wireless device may receive downlink control information (DCI) that may be configured to schedule a physical downlink shared channel (PDSCH) reception. The wireless device may receive the PDSCH reception using the two TCI states in non-overlapping resources indicated by the repetition scheme parameter, for example, based on a TCI selection field in the DCI that may indicate to apply two TCI states to the PDSCH reception, The DCI may further comprise a time domain resource assignment field that may indicate a number of repetitions. The wireless device may receive the PDSCH reception using the two TCI states. The wireless device may receive, in consecutive time slots, the PDSCH reception using the two TCI states. A number of consecutive time slots may be equal to the number of repetitions. The wireless device may receive the PDSCH reception using the two TCI states, for example, based on the TCI selection field in the DCI comprising an indication to apply two TCI states to the PDSCH reception or the TCI selection field being absent in the DCI. The wireless device may receive second DCI configured to schedule a second PDSCH reception. The wireless device may receive the second PDSCH reception using a first demodulation reference signal (DM-RS) port that may be associated with a first TCI state of the two TCI states, and/or a second DM-RS port that may be associated with a second TCI state of the two TCI states. The wireless device the second PDSCH reception using a first demodulation reference signal (DM-RS) port that is associated with a first TCI state of the two TCI states; and/or a second DM-RS port that is associated with a second TCI state of the two TCI states, for example, based on a TCI selection field in the second DCI that may indicate to apply two TCI states to the second PDSCH reception. The wireless device may receive a second DCI configured to schedule a second PDSCH reception. The wireless device may receive the second PDSCH reception using the two TCI states in non-overlapping resources indicated by the repetition parameter. The wireless device may receive the second PDSCH reception using the two TCI states in non-overlapping resources indicated by the repetition parameter, for example, based on the second DCI not being configured with a TCI selection field, the repetition scheme parameter may be set to the time domain scheme the wireless device may receive the PDSCH reception using the two TCI states in non-overlapping resources. Receiving the PDSCH reception using the two TCI states in non-overlapping resources may comprise receiving the PDSCH reception using the two TCI states in non-overlapping time domain resources, for example, based on the repetition scheme parameter being set to the time domain scheme. the repetition scheme parameter may be set to the frequency domain scheme. the wireless device may receive the PDSCH reception using the two TCI states in non-overlapping resources. Receiving a PDSCH reception using two TCI states in non-overlapping resources may comprise receiving the PDSCH reception using the two TCI states in non-overlapping frequency domain resources, for example, based on the repetition scheme parameter being set to the frequency domain scheme. the DCI may comprise an antenna port field that may indicate one or more demodulation reference signal (DM-RS) ports within one code division multiplexing (CDM) group. The wireless device may receive a medium access control (MAC) control element (CE) configured to activate the one or more TCI states of the list of TCI states and receive DCI indicating the two TCI states. The wireless device may receive a medium access control (MAC) control element (CE) configured to activate the one or more TCI states of the list of TCI states and receive DCI indicating the two TCI states, for example, after receiving the one or more messages and before receiving the DCI configured to schedule the PDSCH reception.
A wireless device may receive one or more messages. The one or more messages may comprise a downlink-or-joint transmission configuration indication (TCI) state list parameter. The TCI state list parameter may indicate a list of TCI states for both uplink transmissions and/or downlink receptions. The wireless device may receive downlink control information (DCI) that may be configured to schedule a physical downlink shared channel (PDSCH) reception. the DCI may comprise a time domain resource assignment field that may indicate a number of repetitions. The wireless device may receive the PDSCH reception using the two TCI states. The wireless device may receive the PDSCH reception using the two TCI states, in consecutive time slots, for example, based on a TCI selection field in the DCI that may indicate to apply two TCI states to the PDSCH reception. the one or more messages may comprise a repetition scheme parameter that may indicate a time domain scheme or a frequency domain scheme. The wireless device may receive second DCI configured to schedule a second PDSCH reception. The wireless device may receive the second PDSCH reception using a first demodulation reference signal (DM-RS) port that may be associated with a first TCI state of the two TCI states and/or a second DM-RS port that may be associated with a second TCI state of the two TCI states. The wireless device may receive the second PDSCH reception using a first demodulation reference signal (DM-RS) port that may be associated with a first TCI state of the two TCI states and/or a second DM-RS port that may be associated with a second TCI state of the two TCI states, for example, based on a TCI selection field in the second DCI that may indicate to apply two TCI states to the second PDSCH reception. the DCI may comprise an antenna port field that may indicate one or more demodulation reference signal (DM-RS) ports within one code division multiplexing (CDM) group. The wireless device may receive second DCI configured to schedule a second PDSCH reception. The wireless device may receive the second PDSCH reception using the two TCI states in non-overlapping resources indicated by the repetition parameter. The wireless device may receive the second PDSCH reception using the two TCI states in non-overlapping resources indicated by the repetition parameter, for example, based the second DCI not being configured with a TCI selection field. The wireless device may receive second DCI comprising two TCI states for both uplink transmissions and/or downlink receptions. The wireless device may receive third DCI scheduling and/or activating a second PDSCH reception via an antenna port field that may indicate one or more DM-RS ports within one CDM group and/or a second time domain resource assignment field that may indicate a second number of repetitions. The wireless device may receive, in second consecutive time slots, the second PDSCH reception using the TCI state. The wireless device may receive, in second consecutive time slots, the second PDSCH reception using the TCI state, for example, based on the third DCI that may indicate the one or more DM-RS ports within one CDM group. a number of the second consecutive time slots is equal to the second number of repetitions, the one or more messages may comprise one or more configuration parameters. the one or more configuration parameters may comprise a PDSCH time domain resource allocation parameter.
a wireless device may receive one or more messages comprising a downlink-or-joint transmission configuration indication (TCI) state list parameter. The TCI state list parameter may indicate a list of TCI states for both uplink transmissions and/or downlink receptions. The wireless device may receive downlink control information (DCI) that may be configured to schedule a physical downlink shared channel (PDSCH) reception. the DCI may comprise an antenna port field that may indicate demodulation reference signal (DM-RS) ports within two code division multiplexing (CDM) groups. The wireless device may receive the PDSCH reception using the two TCI states. The wireless device may receive the PDSCH reception using the two TCI states, for example, based on a TCI selection field in the DCI that may indicate to apply two TCI states to the PDSCH reception. a first DM-RS port, of the DM-RS ports, may be associated with a first TCI state of the two TCI states. a second DM-RS port, of the DM-RS ports, may be associated with a second TCI state of the two TCI states. The wireless device may receive second DCI configured to schedule a second PDSCH reception. The wireless device may receive the second PDSCH reception using the two TCI states in non-overlapping resources indicated by the repetition parameter. The wireless device may receive the second PDSCH reception using the two TCI states in non-overlapping resources indicated by the repetition parameter, for example, based the second DCI not being configured with a TCI selection field. the DCI may comprise a time domain resource assignment field that may indicate a number of repetitions, the PDSCH reception may be received in consecutive time slots. a number of consecutive time slots is equal to the number of repetitions. a second DCI may comprise a TCI selection field with a value that may indicate to apply the two TCI states to the PDSCH reception. The wireless device may receive the PDSCH reception using the two TCI states. The wireless device may receive a single PDSCH reception using the two TCI states. the one or more messages may comprise one or more configuration parameters. the one or more configuration parameters may comprise a PDSCH time domain resource allocation parameter.
A wireless device may receive one or more messages comprising a repetition scheme parameter that may indicate a time domain scheme and/or a frequency domain scheme. The wireless device may receive a first downlink control information (DCI) that may indicate two transmission configuration indication (TCI) states for both uplink transmissions and/or downlink receptions via a cell. The wireless device may receive a second DCI scheduling and/or activating a physical downlink shared channel (PDSCH) reception via the cell, wherein the second DCI may comprise an antenna port field that may indicate one or more demodulation reference signal (DM-RS) ports within one code division multiplexing (CDM) group. The wireless device may receive the PDSCH reception using the two TCI states. The wireless device may receive the PDSCH reception using the two TCI states, for example, based on the second DCI that may indicate the one or more DM-RS ports within one CDM group. The wireless device may receive the PDSCH reception using the two TCI states in non-overlapping time domain resources if the repetition scheme parameter may be set to the time domain scheme and/or non-overlapping frequency domain resources if the repetition scheme parameter may be set to the frequency domain scheme. The one or more messages comprise a TCI state parameter that may indicate a list of TCI states for both uplink transmissions and/or downlink receptions via the cell. the wireless device receiving the PDSCH reception using the two TCI states may be further based on the one or more messages comprising the TCI state parameter. the list of TCI states comprise the two TCI states. the second DCI may comprise a TCI selection field with a value that may indicate to apply the two TCI states to the PDSCH reception. the wireless device may receive the PDSCH reception using the two TCI states is further based on the value of the TCI selection field in the second DCI that may indicate to apply the two TCI states to the PDSCH reception. the one or more messages may not comprise a TCI selection parameter that indicates a presence of a TCI selection field in a DCI format. the second DCI may be with the DCI format. the wireless device may receive the PDSCH reception using the two TCI states. Receiving the PDSCH reception may be, for example, further based on the one or more messages not comprising the TCI selection parameter. the wireless device may receive the PDSCH reception in two PDSCH transmission occasions. The wireless device may receive the PDSCH reception with the non-overlapping time domain resources. The wireless device may receive the PDSCH reception in a time slot, for example, if the repetition scheme parameter is set to the time domain scheme. each TCI state of the two TCI states may be associated with a respective PDSCH transmission occasion of the two PDSCH transmission occasions. the frequency domain scheme may be a first frequency domain scheme (e.g., fdmSchemeA). the wireless device may receive the PDSCH reception in a single PDSCH transmission occasion with the non-overlapping frequency domain resources. The wireless device may receive the PDSCH reception in a single PDSCH transmission occasion with the non-overlapping frequency domain resources, for example, if the repetition scheme parameter is set to the first frequency domain scheme. each TCI state of the two TCI states may be associated with a respective frequency domain resource of the non-overlapping frequency domain resources. the frequency domain scheme may be a second frequency domain scheme (e.g., fdmSchemeB). the wireless device may receive the PDSCH reception in two PDSCH transmission occasions with the non-overlapping frequency domain resources, for example, if the repetition scheme parameter is set to the second frequency domain scheme. each TCI state of the two TCI states may be associated with a respective PDSCH transmission occasion of the two PDSCH transmission occasions. Receiving the PDSCH reception using the two TCI states may comprise using a first TCI state of the two TCI states in a first time domain resource of the non-overlapping time domain resources or in a first frequency domain resource of the non-overlapping time frequency resources and/or a second TCI state of the two TCI states in a second time domain resource of the non-overlapping time domain resources or in a second frequency domain resource of the non-overlapping time frequency resources. the TCI state parameter may be a downlink-or-joint TCI state list parameter (e.g., dl-OrJointTCI-StateList). The wireless device may receive one or more second messages comprising a second repetition scheme parameter that may indicate a second time domain scheme or a second frequency domain scheme. The wireless device may receive a third DCI scheduling and/or activating a second PDSCH reception via the cell. The third DCI may comprise a second antenna port field that may indicate one or more second DM-RS ports within one CDM group and a TCI field that may indicate second two TCI states for the second PDSCH reception. The wireless device may receive the second PDSCH reception using the second two TCI states. The wireless device may receive the second PDSCH reception using the second two TCI states, for example, based on the third DCI indicating the one or more DM-RS ports within one CDM group and the second two TCI states for the second PDSCH reception, The wireless device may receive the second PDSCH reception using the second two TCI states in: non-overlapping time domain resources, for example, if the second repetition scheme parameter is set to the second time domain scheme, and the wireless device may receive the second PDSCH reception using the second two TCI states in non-overlapping frequency domain resources, for example, if the second repetition scheme parameter is set to the second frequency domain scheme. the one or more second messages do not comprise a TCI state parameter that may indicate a list of TCI states for both uplink transmissions and/or downlink receptions via the cell (e.g., dl-OrJointTCI-StateList). the second DCI may comprise a TCI field different from the TCI selection field.
A wireless device may receive a first downlink control information (DCI) that may indicate two transmission configuration indication (TCI) states for both uplink transmissions and/or downlink receptions via a cell. The wireless device may receive a second DCI scheduling and/or activating a physical downlink shared channel (PDSCH) reception via the cell. the second DCI may comprise an antenna port field that may indicate one or more demodulation reference signal (DM-RS) ports within one code division multiplexing (CDM) group, and/or a time domain resource assignment field that may indicate a number of repetitions. The wireless device may receive the PDSCH reception using the two TCI states. The wireless device may receive the PDSCH reception using the two TCI states in consecutive time slots. The wireless device may receive, in consecutive time slots, the PDSCH reception using the two TCI states, for example, based on the second DCI that may indicate the one or more DM-RS ports within one CDM group, wherein a number of the consecutive time slots is equal to the number of repetitions. The wireless device may receive one or more messages comprising one or more configuration parameters. the one or more configuration parameters may comprise a PDSCH time domain resource allocation parameter (e.g., PDSCH-TimeDomainResourceAllocation) that may comprise a repetition number parameter (e.g., repetitionNumber). the time domain resource assignment field may indicate an entry that may comprise the repetition number parameter that may indicate the number of repetitions. The wireless device may receive, in the consecutive time slots, the PDSCH reception using the two TCI states, for example, further based on the time domain resource assignment field that may indicate the entry comprising the repetition number parameter. the one or more configuration parameters may comprise a TCI state parameter that may indicate a list of TCI states for both uplink transmissions and/or downlink receptions via the cell, wherein the list of TCI states may comprise the two TCI states. the TCI state parameter may be a downlink-or-joint TCI state list parameter (e.g., dl-OrJointTCI-StateList). The wireless device may receive, in the consecutive time slots, the PDSCH reception using the two TCI states, for example, further based on the one or more configuration parameters comprising the downlink-or-joint TCI state list parameter. receiving, in the consecutive time slots, the PDSCH reception using the two TCI states may comprise receiving the PDSCH reception using a first TCI state of the two TCI states in one or more first time slots of the consecutive time slots and/or a second TCI state of the two TCI states in one or more second time slots of the consecutive time slots. the second DCI may comprise a TCI selection field with a value that may indicate to apply the two TCI states to the PDSCH reception. The wireless device may receive, in the consecutive time slots, the PDSCH reception using the two TCI states, for example, further based on the value of the TCI selection field in the second DCI that may indicate to apply the two TCI states to the PDSCH reception. the one or more messages may not comprise a TCI selection parameter indicating a presence of a TCI selection field in a DCI format. The second DCI may be with the DCI format. The wireless device may receive, in the consecutive time slots, the PDSCH reception using the two TCI states, for example, further based on the one or more messages not comprising the TCI selection parameter. the wireless device may receive one or more second messages. the wireless device may receive a third DCI scheduling and/or activating a second PDSCH reception via the cell. the third DCI may comprise a TCI field that may indicate a second two TCI states for the second PDSCH reception, a second antenna port field that may indicate one or more DM-RS ports within one CDM group, and a second time domain resource assignment field that may indicate a second number of repetitions. The wireless device may receive, in second consecutive time slots, the second PDSCH reception using the second two TCI states. the wireless device may receive, in second consecutive time slots, the second PDSCH reception using the second two TCI states, for example, based on the third DCI indicating the one or more DM-RS ports within one CDM group. a number of the second consecutive time slots may be equal to the second number of repetitions, the one or more second messages may not comprise a TCI state parameter that may indicate a list of TCI states for both uplink transmissions and/or downlink receptions via the cell (e.g., dl-OrJointTCI-StateList). A wireless device may receive first downlink control information (DCI) that may indicate two transmission configuration indication (TCI) states for both uplink transmissions and/or downlink receptions via a cell. The wireless device may receive a second DCI scheduling and/or activating a physical downlink shared channel (PDSCH) reception via the cell. the second DCI may comprise an antenna port field that may indicate demodulation reference signal (DM-RS) ports within two code division multiplexing (CDM) groups. The wireless device may receive the PDSCH reception using the two TCI states based on the second DCI that may indicate the one or more DM-RS ports within two CDM groups. a first DM-RS ports of the DM-RS ports may be associated with a first TCI state of the two TCI states, and a second DM-RS ports of the DM-RS ports may be associated with a second TCI state of the two TCI states. The wireless device may receive one or more messages comprising one or more configuration parameters. the one or more configuration parameters may comprise a PDSCH time domain resource allocation parameter (e.g., PDSCH-TimeDomainResourceAllocation). a time domain resource assignment field in the second DCI may not indicate an entry that may comprise a repetition number parameter (e.g., repetitionNumber) in the PDSCH time domain resource allocation parameter. the one or more configuration parameters may not comprise a single-frequency-network (SFN) scheme parameter for PDSCH receptions (e.g., sfnSchemePdsch). the one or more configuration parameters may comprise a TCI state parameter that may indicate a list of TCI states for both uplink transmissions and/or downlink receptions via the cell. the list of TCI states may comprise the two TCI states. the TCI state parameter may be a downlink-or-joint TCI state list parameter (e.g., dl-OrJointTCI-StateList). receiving the PDSCH reception using the two TCI states may, for example, be based on the value of the TCI selection field in the second DCI indicating to apply the two TCI states to the PDSCH reception. the one or more messages may not comprise a TCI selection parameter that may indicate a presence of a TCI selection field in a DCI format. the second DCI may be with the DCI format. receiving the PDSCH reception using the two TCI states may, for example, be further based on the one or more messages not comprising the TCI selection parameter. A wireless device may receive one or more messages that may indicate at least two discontinuous transmission (DTX) configurations of a cell. The wireless device may receive first downlink control information (DCI) that may indicate at least two transmission configuration indication (TCI) states for the cell. The wireless device may receive second DCI that may indicate activation of a semi-persistent scheduling (SPS) configuration of the cell. the second DCI may comprise a TCI selection field with a value that may indicate to apply the at least two TCI states to physical downlink shared channel (PDSCH) receptions of the SPS configuration. The wireless device may receive a first PDSCH reception of the SPS configuration using the at least two TCI states. The wireless device may receive a first PDSCH reception of the SPS configuration using the at least two TCI states, for example, if in an active time/period/duration of a DTX configuration of the at least two DTX configurations, a first PDSCH reception of the SPS configuration using the at least two TCI states. The wireless device may receive a PDSCH reception of the SPS configuration. The wireless device may receive a PDSCH reception of the SPS configuration, for example, if in a non-active time/period/duration of the DTX configuration. The wireless device may receive a PDSCH reception of the SPS configuration, for example, based on whether the wireless The wireless device may receive a PDSCH reception of the SPS configuration using a TCI state among the at least two TCI states and/or the at least two TCI states.
The wireless device may receive downlink control information (DCI) that may indicate activation of a semi-persistent scheduling (SPS) configuration of a cell and/or application of at least two transmission configuration indicator (TCI) states to physical downlink shared channel (PDSCH) receptions of the SPS configuration. The wireless device may receive a PDSCH reception of the SPS configuration. The wireless device may receive a PDSCH reception of the SPS configuration, for example, if in a non-active time/period/duration of a DTX configuration of the cell. The wireless device may receive a PDSCH reception of the SPS configuration, for example, based on whether the wireless device supports dynamic switching between a single TCI state and multiple TCI states for PDSCH receptions, receiving, during a non-active time/period/duration of a DTX configuration of the cell, a PDSCH reception of the SPS configuration using one TCI state of the at least two TCI states, and/or the at least two TCI states. the one or more configuration parameters may comprise one or more first DTX configuration parameters (e.g., TRP-DTX-Config) for a first DTX configuration of the at least two DTX configurations, and/or one or more second DTX configuration parameters (e.g., TRP-DTX-Config2) for a second DTX configuration of the at least two DTX configurations, the one or more configuration parameters may comprise the one or more second DTX configuration parameters. The one or more configuration parameters may comprise the one or more second DTX configuration parameters, for example, based on transmitting, to a base station, a capability message that may indicate support/capability of two DTX configurations for a (single) cell. the wireless device may transmit a capability message that may indicate support/capability of the dynamic switching (e.g., sfn-SchemeA-DynamicSwitching or sfn-SchemeB-DynamicSwitching, DTX-DynamicSwitching). receiving the PDSCH reception the SPS configuration may use the TCI state, for example, based on the capability message that may indicate support/capability of the dynamic switching. the TCI state may be a first TCI state of the at least two TCI states based on the DTX configuration being the second DTX configuration (e.g., the PDSCH reception overlaps with (or is in) the non-active time/period/duration of the second DTX configuration) and the PDSCH reception overlapping with (or being in) an active time/period/duration of the first DTX configuration, and/or a second TCI state of the at least two TCI states based on the DTX configuration being the first DTX configuration (e.g., the PDSCH reception overlaps with (or is in) the non-active time/period/duration of the first DTX configuration) and the PDSCH reception overlapping with (or being in) an active time/period/duration of the second DTX configuration, the wireless device may not transmit a capability message that may indicate support/capability of the dynamic switching (e.g., sfn-SchemeA-DynamicSwitching or sfn-SchemeB-DynamicSwitching, DTX-DynamicSwitching). receiving the PDSCH reception the SPS configuration may use the at least two TCI states, for example, based on not transmitting the capability message that may indicate support/capability of the dynamic switching. the one or more messages may comprise one or more configuration parameters that indicate the at least two DTX configurations, the PDSCH receptions of the SPS configuration may be associated with the at least two TCI states. The PDSCH receptions of the SPS configuration may be associated with the at least two TCI states, for example, based on the second DCI (e.g., DCI format 1_1/1_2) comprising a TCI selection field with a value (e.g., ‘10’) that may indicate to apply the at least two TCI states to the PDSCH receptions of the SPS configuration, the PDSCH receptions of the SPS configuration may be associated with the at least two TCI states, for example, based on the second DCI (e.g., DCI format 1_1/1_2) may not comprise a TCI selection field. the PDSCH receptions of the SPS configuration may be associated with the at least two TCI states, for example, based on the one or more configuration parameters comprising an apply-indicated-TCI state parameter, for a downlink bandwidth part (BWP) of the cell, set to ‘both’ that may indicate to apply both of the at least two TCI states to the PDSCH receptions and the second DCI being a DCI format 1_0 received on/via a search space set other than Type0/0A/2 common search space set on (or associated with) a coreset with index zero (e.g., CORESET #0). the one or more configuration parameters may comprise a coherent-joint-transmission scheme parameter (e.g., cjtSchemePDSCH) that may indicate a coherent-joint-transmission scheme for PDSCH receptions, the wireless device may transmit a capability message that may indicate support/capability for/of two joint TCI states for the coherent-joint-transmission scheme. the one or more configuration parameters may comprise a single frequency network (SFN) scheme parameter (e.g., sfnSchemePdsch) that may indicate an SFN scheme for PDSCH receptions.
One or more of the operations described herein may be conditional. For example, one or more operations may be performed if certain criteria are met, such as in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based on one or more conditions such as wireless device and/or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. If the one or more criteria are met, various examples may be used. It may be possible to implement any portion of the examples described herein in any order and based on any condition.
A base station may communicate with one or more of wireless devices. Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies). A base station may comprise multiple sectors, cells, and/or portions of transmission entities. A base station communicating with a plurality of wireless devices may refer to a base station communicating with a subset of the total wireless devices in a coverage area. Wireless devices referred to herein may correspond to a plurality of wireless devices compatible with a given LTE, 5G, 6G, or other 3GPP or non-3GPP release with a given capability and in a given sector of a base station. A plurality of wireless devices may refer to a selected plurality of wireless devices, a subset of total wireless devices in a coverage area, and/or any group of wireless devices. Such devices may operate, function, and/or perform based on or according to drawings and/or descriptions herein, and/or the like. There may be a plurality of base stations and/or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, because those wireless devices and/or base stations may perform based on older releases of LTE, 5G, 6G, or other 3GPP or non-3GPP technology.
One or more parameters, fields, and/or Information elements (IEs), may comprise one or more information objects, values, and/or any other information. An information object may comprise one or more other objects. At least some (or all) parameters, fields, IEs, and/or the like may be used and can be interchangeable depending on the context. If a meaning or definition is given, such meaning or definition controls.
One or more elements in examples described herein may be implemented as modules. A module may be an element that performs a defined function and/or that has a defined interface to other elements. The modules may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with a biological element) or a combination thereof, all of which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Additionally or alternatively, it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware may comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and/or complex programmable logic devices (CPLDs). Computers, microcontrollers and/or microprocessors may be programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL), such as VHSIC hardware description language (VHDL) or Verilog, which may configure connections between internal hardware modules with lesser functionality on a programmable device. The above-mentioned technologies may be used in combination to achieve the result of a functional module.
One or more features described herein may be implemented in a computer-usable data and/or computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other data processing device. The computer executable instructions may be stored on one or more computer readable media such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc. The functionality of the program modules may be combined or distributed as desired. The functionality may be implemented in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA), and the like. Particular data structures may be used to more effectively implement one or more features described herein, and such data structures are contemplated within the scope of computer executable instructions and computer-usable data described herein.
A non-transitory tangible computer readable media may comprise instructions executable by one or more processors configured to cause operations of multi-carrier communications described herein. An article of manufacture may comprise a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a device (e.g., a wireless device, wireless communicator, a wireless device, a base station, and the like) to allow operation of multi-carrier communications described herein. The device, or one or more devices such as in a system, may include one or more processors, memory, interfaces, and/or the like. Other examples may comprise communication networks comprising devices such as base stations, wireless devices or user equipment (wireless device), servers, switches, antennas, and/or the like. A network may comprise any wireless technology, including but not limited to, cellular, wireless, WiFi, 4G, 5G, 6G, any generation of 3GPP or other cellular standard or recommendation, any non-3GPP network, wireless local area networks, wireless personal area networks, wireless ad hoc networks, wireless metropolitan area networks, wireless wide area networks, global area networks, satellite networks, space networks, and any other network using wireless communications. Any device (e.g., a wireless device, a base station, or any other device) or combination of devices may be used to perform any combination of one or more of steps described herein, including, for example, any complementary step or steps of one or more of the above steps.
Although examples are described herein, features and/or steps of those examples may be combined, divided, omitted, rearranged, revised, and/or augmented in any desired manner. Various alterations, modifications, and improvements will readily occur to those skilled in the art. Such alterations, modifications, and improvements are intended to be part of this description, though not expressly stated herein, and are intended to be within the spirit and scope of the descriptions herein. Accordingly, the foregoing description is by way of example only, and is not limiting.
This application claims the benefit of U.S. Provisional Application No. 63/539,138 filed on Sep. 19, 2023. The above-referenced application is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63539138 | Sep 2023 | US |
