Default downlink signaling in control channel repetition

Abstract

A wireless device can receive at least one repetition of downlink control information (DCI) scheduling a transport block via at least one control resource set (coreset) configured for repetition of the coreset of the DCI. In response to: the DCI not including a TCI field, and a time offset between the DCI and the transport block being equal to or greater than a threshold, the wireless device can receive the transport block using a transmission configuration indicator (TCI) state of a coreset of the coreset having a lowest coreset index.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application 63 / 083,027, filed on September 24, 2020, the entire contents of which are incorporated herein by reference. Attached Figure Description

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

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

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

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

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

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

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

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

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

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

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

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

[0015] FIG. 10B An example is shown of how a poly cell can be configured into one or more PUCCH groups.

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

[0017] FIG. 11B An example is shown of a CSI-RS mapped in time and frequency domain.

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

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

[0020] FIG. 14A An example is shown of CORESET configuration of a bandwidth part.

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

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

[0023] FIG. 16A , FIG. 16B , FIG. 16C And FIG. 16D Example structures for uplink and downlink transmissions are shown.

[0024] FIG. 17 Example configuration parameters of control and / or data in accordance with aspects of embodiments of the present disclosure are shown.

[0025] FIG. 18 Example configuration parameters of a core set in accordance with aspects of embodiments of the present disclosure are shown.

[0026] FIG. 19 Examples of PDCCH repetition in accordance with aspects of embodiments of the present disclosure are shown.

[0027] FIG. 20 Examples of control channel repetition across multiple TRPs in accordance with aspects of embodiments of the present disclosure are shown.

[0028] FIG. 21 Examples of control channel repetition in accordance with aspects of embodiments of the present disclosure are shown.

[0029] FIG. 22 An example of a MAC CE format activating multiple TCI states of a core set is shown in accordance with an aspect of the embodiments of the present disclosure.

[0030] FIG. 23 An example of a MAC CE format activating multiple TCI states of a core set is shown in accordance with an aspect of the embodiments of the present disclosure.

[0031] FIG. 24 An example of downlink signal reception with control channel repetition in accordance with an aspect of the embodiments of the present disclosure.

[0032] FIG. 25 An example of downlink signal reception with control channel repetition in accordance with an aspect of the embodiments of the present disclosure.

[0033] FIG. 26 An example of downlink signal reception with control channel repetition in accordance with an aspect of the embodiments of the present disclosure.

[0034] FIG. 27 An example of downlink signal reception with control channel repetition in accordance with an aspect of the embodiments of the present disclosure. DETAILED DESCRIPTION

[0035] In this disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those of ordinary skill in the relevant arts that various changes can be made thereto without departing from scope of the invention. Indeed, after understanding the specification, it will be apparent to those of ordinary skill in the relevant arts how to implement alternative embodiments. The embodiments of the present invention should not be limited by any described exemplary embodiments. Embodiments of the present disclosure will be described with reference to the drawings. Limitations, features and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. The diagrams are given only for example purposes and are not limiting. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways different from that shown. For example, the actions listed in any flow diagram can be reordered or only optionally utilized in some embodiments.

[0036] Embodiments can be configured to operate as desired. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., the disclosed mechanisms can be performed when certain criteria are met. Exemplary criteria can be based at least in part on, for example, a wireless device or network node configuration, traffic load, initial system setup, packet size, traffic characteristics, a combination of the above, etc. Various exemplary embodiments can be applied when one or more criteria are met. Thus, exemplary embodiments that selectively implement the disclosed protocols can be implemented.

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

[0038] In the present disclosure, "a" and "an" and similar phrases generally connote "at least one," and "one or more." Similarly, any term in the suffix "(s)" is generally intended to convey "one or more." In the present disclosure, the term "may" is interpreted to mean "may, for example." In other words, the term "may" indicates one or more possibilities of what is being expressed after the term "may." As used herein, the terms "comprises" and "consists of" recite one or more components of what is being described. The term "comprises" is interchangeable with "includes" and does not exclude components that are unrecited. In contrast, "consists of" provides a complete recitation of one or more components of what is being described. As used herein, the term "based on" shall mean "based at least in part on" and not "based solely on," for example. As used herein, the term "and / or" means any possible combination of the elements listed. For example, "A, B, and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B, and C.

[0039] A is called a subset of B if every element of A is also an element of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {celll, cell2} are: {celll}, {cell2}, and {celll, cell2}. The phrase "based on" (or, equivalently, "at least based on") indicates that the phrase after "based on" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments. The phrase "in response to" (or, equivalently, "at least in response to") indicates that the phrase after "in response to" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments. The phrase "in dependence of" (or, equivalently, "at least in dependence of") indicates that the phrase after "in dependence of" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments. The phrase "employing / using" (or, equivalently, "at least employing / using") indicates that the phrase after "employing / using" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments.

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

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

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

[0043] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is herein defined as an element or component that performs a defined function and has a defined interface to other elements or components. Modules described in the present disclosure can be implemented in hardware, software, firmware, wetware, or combinations thereof, all of which are behaviorally equivalent. For example, a module can be implemented as a software routine in a computer language such as C, C++, Fortran, Pascal, Java, Basic, Matlab, or others, which is structured to perform the defined function and is compiled into machine language suitable for execution by the hardware machine. Wetware modules are defined as physical hardware that is not programmable but has specific behavior suitable for the defined function. For example, a wetware module can be a resistor, capacitor, transistor, or others, which are strung together to process input signals to produce output signals in a manner suitable for the defined function. It is noted that the modules described herein can be implemented in software, hardware, and / or a combination thereof. Modules implemented in software can be stored in memory 110, which can be implemented as a computer-readable medium that can be external to or integral with the machine 100. Software modules can be stored on RAM, disk drives, or other computer-readable media, which can be removable and / or integral to the machine 100. The machine 100 can include a file server for transferring the software modules to the machine 100. The machine 100 can include or be connected to a communications network for receiving software modules. The network can be or include the Internet, Local Area Network, Wide Area Network, Wireless Network, or any other communications network or combination of networks. The machine 100 can be connected to the communications network through a wired medium, a wireless medium, or a combination of wired and wireless media. Examples of a wireless medium include cellular, Wi-Fi, Bluetooth, and others. The machine 100 can be connected to the communications network through an access point, gateway, or any other device suitable for connecting to the communications network.

[0044] FIG. 1A An example of a mobile communication network 100 in which embodiments of the present disclosure can be implemented is shown. The mobile communication network 100 can be, for example, a public land mobile network (PLMN) operated by a network operator. As shown, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106. FIG. 1A The mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0045] CN 102 can provide the wireless device 106 with an interface to one or more data networks (DNs) such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of the interface function, the CN 102 can setup end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functions.

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

[0047] The term “wireless device” can be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device that needs or can use wireless communication. For example, a wireless device can be a telephone, a smartphone, a tablet, a computer, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicle road-side unit (RSU), a relay node, an automobile, and / or any combination thereof. The term “wireless device” encompasses other terms, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0048] The RAN 104 can include one or more base stations (not shown). The term “base station” can be used throughout this disclosure to refer to and encompass: a Node B (associated with UMTS and / or 3G standards); an evolved Node B (eNB, associated with E-UTRA and / or 4G standards); a remote radio head (RRH); a baseband processing unit coupled to one or more RRHs; a repeater node or relay node used to extend the coverage area of a donor node; a next generation evolved Node B (ng-eNB); a generation Node B (gNB, associated with NR and / or 5G standards); an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station can include at least one gNB-central unit (gNB-CU) and at least one gNB-distributed unit (gNB-DU).

[0049] The base stations included in the RAN 104 can include one or more sets of antennas, which can be used to communicate with the wireless devices 106 through the use of the air interface. For example, one or more of the base stations can include three sets of antennas to control three cells (or sectors). The size of a cell can be determined by the range of the transmitters and receivers (e.g., base station receivers) that can successfully communicate with the transmitters (e.g., wireless device transmitters) operating in the cell. The cells of the base stations can together provide radio coverage to the wireless devices 106 over a wide geographic area to support the movement (e.g., roaming) of wireless devices.

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

[0051] The RAN 104 can be deployed as a homogeneous network of macro cell base stations, each having similar antenna patterns and antenna gains, and / or similar transmit power levels. The RAN 104 can be deployed as a heterogeneous network. In a heterogeneous network, some of the base stations can be macro cell base stations (for example, macro cells, micro cells, pico cells, and / or femto cells) that can provide the radio coverage over large, medium, or small cells. The macro cell base stations can be deployed in the RAN 104 to provide high throughput and / or high capacity. The small cell base stations can be deployed in the RAN 104 to provide, for example, more reliable service, higher throughput, and / or lower latency.

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

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

[0054] 5G-CN 152 provides UE 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. As part of the interface functionality, 5G-CN 152 can establish end-to-end connections between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CNs in 3GPP 4G networks, the foundation of 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 can be defined as network functions that provide services to other network functions via the interface. The network functions of 5G-CN 152 can be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0055] like FIG. 1B As shown, 5G-CN 152 includes Access and Mobility Management Functions (AMF) 158A and User Plane Functions (UPF) 158B. For ease of explanation, in FIG. 1BThe AMF / UPF 158 can be implemented as one component for clarity. The UPF 158B can act as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B can 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, quality of service (QoS) handling for user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering and downlink data notification triggering. The UPF 158B can act as an anchor point for intra- / inter-Radio Access Technology (RAT) mobility, a point of interconnect with the one or more DNs, and / or a branching point to support multi-homed PDU session. The UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and a DN.

[0056] The AMF 158A can 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 3 GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including check of roaming rights, mobility management control (subscription and policies), network slice support, and / or session management function (SMF) selection. NAS can mean functionality operating between the CN and the UE, and AS can mean functionality operating between the UE and the RAN.

[0057] The 5G-CN 152 can include one or more additional network functions not shown in FIG. 1B the middle for clarity. For example, the 5G-CN 152 can include one or more of the following: a session management function (SMF), an NR repository function (NRF), a policy control function (PCF), a network exposure function (NEF), a unified data management (UDM), an application function (AF), and / or an authentication server function (AUSF).

[0058] The NG-RAN 154 can connect the 5G-CN 152 to the UEs 156 through wireless communication over the air interface. The NG-RAN 154 can include one or more gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160), and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 can be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 can include one or more sets of antennas, which can be used to communicate with UEs 156 through the air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 can include three sets of antennas to respectively control three cells (or sectors). The cells of the gNBs 160 and ng-eNBs 162 can together provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

[0059] As shown in FIG. 1B , the gNBs 160 and / or ng-eNBs 162 can be connected by means of the NG interfaces to the 5G-CN 152, and by means of the Xn interface to other base stations. The NG and Xn interfaces can be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or ng-eNBs 162 can be connected by means of the Uu interface to the UEs 156. For example, as shown in FIG. 1B , the gNB 160A can be connected by means of the Uu interface to the UE 156A. The NG, Xn, and Uu interfaces are associated with protocol stacks. The protocol stacks associated with the interfaces can be used by the network elements in FIG. 1B to exchange data and signaling messages, and can include two planes: the user plane and the control plane. The user plane can handle data of interest to the user. The control plane can handle signaling messages of interest to the network elements.

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

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

[0062] The 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those of ordinary skill in the art will understand that it is possible for NR to connect to a 4G core network in a mode referred to as “non-standalone.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functionality (e.g., initial access, mobility, and paging). Although FIG. 1B Only one AMF / UPF 158 is shown in FIG. 1, but one gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

[0063] As discussed, FIG. 1B Interfaces between network elements in FIG. 1 (e.g., Uu, Xn, and NG interfaces) can be associated with a protocol stack that the network elements use to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. The user plane can handle data of interest to users, while the control plane can handle signaling messages of interest to the network elements.

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

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

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

[0067] The PDCPs 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, can perform ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from an intended source. The PDCPs 214 and 224 can perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets that are received in repetition due to, for example, an intra-gNB handover. The PDCPs 214 and 224 can perform packet duplication to improve the likelihood that a packet will be received, and remove any duplicate packets at the receiver. Packet duplication can be applicable to services that require high reliability.

[0068] Although FIG. 3 Although not shown in FIG. 2, the PDCPs 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or more generally to two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by the cell groups in dual connectivity. The PDCPs 214 and 224 can map / de-map the split radio bearers between RLC channels that belong to the cell groups.

[0069] The RLCs 213 and 223 can perform segmentation, retransmission by automatic repeat request (ARQ), and removal of duplicate data units received from the MACs 212 and 222, respectively. The RLCs 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode that the RLC is operating, the RLC can perform one or more of the functions described. The RLC configuration can be on a per logical channel basis, independent of numerology and / or transmission time interval (TTI) duration. As FIG. 3 As shown in FIG. 2, the RLCs 213 and 223 can provide RLC channels as a service to the PDCPs 214 and 224, respectively.

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

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

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

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

[0074] FIG. 4A The remaining protocol layers can perform their associated functions (e.g., regarding...). FIG. 3 This involves adding the corresponding headers and forwarding their output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., as...). FIG. 4A (As shown in the image regarding IP packet m) and forwards its output to MAC 222. MAC 222 can multiplex many RLC PDUs and can attach MAC subheaders to RLC PDUs to form transport blocks. In NR, MAC subheaders can be distributed throughout MAC PDUs, such as... FIG. 4A As shown in the diagram. In LTE, the MAC sub-header can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU sub-header can be computed before the complete MAC PDU is assembled.

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

[0076] FIG. 4B The diagram further illustrates a MAC control element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, FIG. 4B This shows two MAC CEs inserted into the MAC PDU. These can be used at the beginning of downlink transmissions within the MAC PDU (e.g., ...). FIG. 4BMAC CEs can be used for in-band control signaling. Exemplary MAC CEs include: scheduling related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. There can be a MAC subheader with a similar format as described with respect to MAC SDUs before the MAC CE, and the MAC CE can be identified with a reserved value in the LCID field indicating the type of control information included in the MAC CE.

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

[0078] FIG. 5A And FIG. 5B The mapping between logical channels, transport channels, and physical channels is shown for downlink and uplink, respectively. Information is transferred through channels between RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between RLC and MAC, and can be classified as control channels, which carry control and configuration information in the NR control plane, or as traffic channels, which carry data in the NR user plane. Logical channels can be classified as dedicated to a specific UE, or as common logical channels, which can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example:

[0079] - a paging control channel (PCCH), which is used to carry paging messages for paging UEs whose location is not known by the network on a cell level;

[0080] - a broadcast control channel (BCCH), which is used to carry system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), which can be used by UEs to obtain information about how the cell is configured and how to operate within the cell;

[0081] - a common control channel (CCCH), which is used to carry control messages and random access;

[0082] - a dedicated control channel (DCCH) for carrying control messages to / from specific UEs to configure the UEs;

[0083] - a dedicated traffic channel (DTCH) for carrying user data to / from specific UEs.

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

[0085] - a paging channel (PCH) for carrying paging messages originating from the PCCH;

[0086] - a broadcast channel (BCH) for carrying the MIB from the BCCH;

[0087] - a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including SIBs from the BCCH;

[0088] - an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and

[0089] - a random access channel (RACH) for allowing UEs to access the network without any prior scheduling.

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

[0091] - a physical broadcast channel (PBCH) for carrying the MIB from the BCH;

[0092] - a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH and paging messages from the PCH;

[0093] - a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which can include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

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

[0095] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, which can include HARQ acknowledgements, Channel Quality Indicators (CQIs), Precoding Matrix Indicators (PMIs), Rank Indicators (RIs), and Scheduling Requests (SRs); and

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

[0097] Similar to the physical control channels, the physical layer generates physical signals to support the low-level operations of the physical layer. As shown in FIG. 2B and FIG. 2B The physical layer signals defined by NR include: primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), sounding reference signal (SRS), and phase tracking reference signal (PT-RS). These physical layer signals are described in more detail below.

[0098] FIG. 6 An example NR control plane protocol stack is shown. As shown in FIG. 1A The first four protocol layers of the NR control plane protocol stack can use the same / similar as the example NR user plane protocol stack. The four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Rather than having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack has Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

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

[0100] The RRC 216 and 226 can provide control plane functionality between the UE 210 and gNB 220, or more generally, between the UE 210 and the RAN. The RRC 216 and 226 can provide control plane functionality between the UE 210 and gNB 220 via signaling messages, referred to as RRC messages. RRC messages can be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC can multiplex control plane and user plane data into the same transport block (TB). The RRC 216 and 226 can provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by a CN or RAN; establishment, maintenance, and release of an RRC connection between the UE 210 and the RAN; security functions including key management; signaling radio bearers and data radio bearers establishment, configuration, maintenance, and release; mobility functions; QoS management functions; UE 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, the RRC 216 and 226 can establish an RRC context, which can involve configuring parameters for communication between the UE 210 and the RAN.

[0101] FIG. 2A is an example diagram illustrating RRC state transitions of a UE. The UE can be the same or similar to the wireless device 106, FIG. 2B depicted in FIG. 1, FIG. 6 and FIG. 1A depicted in FIG. 2, or any other wireless device described in the present disclosure. As shown in FIG. 1B , the UE can be in at least one of three RRC states: RRC connected 602 (e.g., RRC CONNECTED), RRC idle 604 (e.g., RRC IDLE), and RRC inactive 606 (e.g., RRC INACTIVE).

[0102] In the RRC connected 602, the UE has an established RRC context and can have at least one RRC connection with a base station. The base station can be similar to one of: FIG. 2A the one or more base stations included in the RAN 104 depicted in FIG. 1; FIG. 2B one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1; FIG. 1B and FIG. 5Athe gNB 220 depicted in the figures herein; or any other base station described in the present disclosure. A base station with which a UE is connected can have an RRC context for the UE. The RRC context, referred to as the UE context, can include parameters for communication between the UE and the base station. These parameters can include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. When in the RRC connected 602, mobility of the UE can be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE can measure signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE’s serving base station can request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state can transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608, or to RRC inactive 606 through a connection suspend procedure 610.

[0103] In the RRC idle 604, no RRC context can be established for the UE. In the RRC idle 604, the UE can not have an RRC connection with a base station. While in the RRC idle 604, the UE can be in a sleep state for most of the time (e.g., to conserve battery power). The UE can periodically wake up (e.g., once per each discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility of the UE can be managed by the UE through a procedure known as cell reselection. The RRC state can transition from the RRC idle 604 to the RRC connected 602 through a connection establishment procedure 612, which can involve a random access procedure, as discussed in more detail below.

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

[0105] RRC states can be associated with mobility management mechanisms. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to inform the UE of events via a paging message without having to broadcast the paging message over the entire mobile communication network. The mobility management mechanisms used in RRC idle 604 and RRC inactive 606 can allow the network to track the UE at a cell group level, such that a paging message can be broadcast on a cell in the cell group in which the UE is currently camped rather than over the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE at a cell group level. These mobility management mechanisms can use different granularities of grouping to do so. For example, there can be three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN area identifier (RAI); and a group of RAN areas, referred to as tracking areas and identified by a tracking area identifier (TAI).

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

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

[0108] A last serving base station of a base station or UE storing an RRC context for the UE can be referred to as an anchor base station. The anchor base station can maintain the RRC context for the UE at least for a period of time that the UE remains in the RAN notification area of the anchor base station and / or for a period of time that the UE remains in RRC inactive 606.

[0109] A gNB, such as gNB 104, can be configured to operate in a RRC connected 602 state, a RRC idle 604 state, or a RRC inactive 606 state. In the RRC connected 602 state, the UE can have an RRC context stored at the gNB. The gNB can be able to communicate with the UE in the RRC connected 602 state. In the RRC idle 604 state, the UE can not have an RRC context stored at the gNB. The gNB can not be able to communicate with the UE in the RRC idle 604 state. In the RRC inactive 606 state, the UE can have an RRC context stored at the gNB. The gNB can be able to communicate with the UE in the RRC inactive 606 state. FIG. 5BThe gNBs 160 in the RAN 104 can interface with the core network 106 through backhaul links 132 (e.g., an SI interface). The gNBs 160 can also communicate with one another using the backhaul links 132, which can be or include an X2 interface. The gNBs 160 can perform scheduling and resource allocation, as well as other techniques (e.g., power control and load balancing). These techniques are known in the art.

[0110] In NR, physical signals and physical channels (about which FIG. 7 and FIG. 7 are discussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data over F orthogonal subcarriers, or tones. Prior to transmission, data can be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and split into F parallel symbol streams. The F parallel symbol streams can be treated as if they are in the frequency domain and used as inputs to an inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols (one from each of the F parallel symbol streams) at a time and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block can be F time-domain samples that represent the sum of the F orthogonal subcarriers. The F time-domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and upconversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at a carrier frequency. The F parallel symbol streams can be mixed using a FFT block prior to being processed by the IFFT block. This operation results in a discrete Fourier transform (DFT) precoded OFDM symbol and can be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). An inverse of the processing can be performed on the OFDM symbol at the receiver using a FFT block to recover the data mapped to the source symbols.

[0111] FIG. 7 An example configuration of an NR frame into which OFDM symbols are grouped is shown. An NR frame can be identified by a system frame number (SFN). The SFN can repeat with a period of 1024 frames. As shown, the duration of one NR frame can be 10 milliseconds (ms) and can include 10 subframes of duration 1 ms. The subframes can be divided into slots, which include, for example, 14 OFDM symbols per slot.

[0112] The duration of a slot can depend on the numerology of the OFDM symbols used for the slot. In NR, flexible numerologies are supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mmWave range). A numerology can be defined in terms of subcarrier spacing and cyclic prefix duration. For numerologies in NR, the subcarrier spacing can be scaled up from a baseline subcarrier spacing of 15 kHz by powers of two, and the cyclic prefix duration can be scaled down from a baseline cyclic prefix duration of 4.7 μ8 by powers of two. For example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μ8; 30 kHz / 2.3 μ8; 60 kHz / 1.2 μ8; 120 kHz / 0.59 μ8; and 240 kHz / 0.29 μ8.

[0113] A slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations, and correspondingly more slots per subframe. FIG. 8 The slot duration and transmission structure per slot in terms of numerology are shown for illustration, FIG. 8 (not shown in the middle for 240 kHz subcarrier spacing). A subframe in NR can be used as a time reference independent of numerology, while a slot can be used as a unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from the slot duration, and start at any OFDM symbol, and continue for as many symbols as needed for the transmission. These partial slot transmissions can be referred to as mini-slot or sub-slot transmissions.

[0114] FIG. 8 An exemplary configuration of a slot in time and frequency domain for an NR carrier is shown. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one subcarrier in the frequency domain and one OFDM symbol in the time domain, as shown. FIG. 8 An RB spans twelve consecutive REs in the frequency domain, as shown. FIG. 9 An NR carrier can be limited to a width of 275 RBs or 275 x 12 = 3300 subcarriers. If such a limit is used, for subcarrier spacing of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, the NR carrier can be limited to 50 MHz, 100 MHz, 200 MHz, and 400 MHz, respectively, where the 400 MHz bandwidth can be set based on a bandwidth limit of 400 MHz per carrier.

[0115] FIG. 9A single numerology is shown that is used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies can be supported on the same carrier.

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

[0117] NR defines bandwidth parts (BWPs) to support UEs that are not able to receive the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP can be defined by a subset of contiguous RBs on a carrier. A UE can be configured (e.g., via an RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell can be active. The one or more BWPs can be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

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

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

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

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

[0122] A base station can semi-statically configure a default downlink BWP for a UE within a set of configured downlink BWPs associated with a PCell. If the base station does not provide a default downlink BWP for the UE, the default downlink BWP can be an initial active downlink BWP. The UE can determine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using a PBCH.

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

[0124] In an example, a base station can semi-statically configure a UE with one or more BWPs. The UE can switch the active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as the active BWP and / or in response to an expiration of a BWP inactivity timer (e.g., in a case where the second BWP is a default BWP).

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

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

[0127] If a UE is configured for a secondary cell with a default downlink BWP and a timer value in a set of configured downlink BWPs, the UE procedures for switching BWP on the secondary cell can be the same / similar to those on the primary cell. For example, the UE can use the timer value and default downlink BWP of the secondary cell in the same / similar way that the UE would use those of the primary cell.

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

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

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

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

[0132] Configured SCells for a UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmission on the SCell. Configured SCells can be activated and deactivated using MAC CEs for SCell Activation / Deactivation. FIG. 10B For example, a MAC CE can indicate which SCells for a UE (e.g., in a subset of configured SCells) are activated or deactivated using a bitmap (e.g., one bit per SCell). Configured SCells can be deactivated in response to expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

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

[0134] FIG. 10B Examples of how aggregated cells can be configured into one or more PUCCH groups are shown. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. In FIG. 5AIn the example of PUCCH group 1010, the PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes, in this example, three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary Scell (PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In an example, if FIG. 5B If the aggregated cells depicted in FIG. 10 were not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell would transmit UCI related to the downlink CCs, and the PCell can become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061, overloading can be prevented.

[0135] A physical cell ID and a cell index can be assigned for a cell that includes a downlink carrier and optional uplink carriers. The physical cell ID or the cell index can identify the downlink carrier and / or the uplink carrier of the cell, depending on the context in which the physical cell ID is used, for example. The physical cell ID can be determined using a synchronization signal transmitted on a downlink component carrier. The cell index can be determined using an RRC message. In this disclosure, the physical cell ID can be referred to as a carrier ID, and the cell index can be referred to as a carrier index. By way of example, when this disclosure refers to a first physical cell ID of a first downlink carrier, this disclosure can mean that the first physical cell ID is used for a cell that includes the first downlink carrier. The same / similar concept can apply to, for example, carrier activation. When this disclosure indicates that a first carrier is activated, this specification can mean that a cell that includes the first carrier is activated.

[0136] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an example, a HARQ entity can operate on a serving cell. Transport blocks can be generated according to assignments / grants of each serving cell. Transport blocks and potential HARQ retransmissions of the transport blocks can be mapped to the serving cells.

[0137] In the downlink, a base station can transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RSs) (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as shown in FIG. 1) to a UE. In the uplink, a UE can transmit one or more RSs to a base station (e.g., DMRS, PT-RS, and / or SRS, as shown in FIG. 1). The PSS and SSS can be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and SSS can be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block including the PSS, SSS, and PBCH. The base station can periodically transmit a burst of SS / PBCH blocks. FIG. 11A FIG. 11A An example of a structure and location of a SS / PBCH block is shown. A burst of SS / PBCH blocks can include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as shown in FIG. 2). The burst can be periodically transmitted (e.g., every 2 frames or 20 ms). The burst can be limited to a half frame (e.g., the first half frame with a duration of 5 ms). It should be understood that

[0138] FIG. 11A FIG. 11A is an example, and these parameters (number of SS / PBCH blocks per burst, periodicity of the burst, burst location within a frame) can be configured based on, for example, a carrier frequency of a cell in which the SS / PBCH block is transmitted; a numerology or subcarrier spacing of the cell; configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, a UE can assume a subcarrier spacing of a SS / PBCH block based on a carrier frequency being monitored, unless the radio network configures the UE to assume a different subcarrier spacing. FIG. 11B

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

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

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

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

[0143] A UE can assume that one or more SS / PBCH blocks transmitted with a same SS / PBCH block index are quasi co-located (QCLed) (e.g., have a same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameter). The UE can not assume QCL for SS / PBCH block transmissions with different SS / PBCH block indexes.

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

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

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

[0147] A base station can semi-statically configure a UE with one or more CSI-RS resource sets. A CSI-RS resource can be associated with a location in a time domain and a frequency domain and a periodicity. A base station can selectively activate and / or deactivate a CSI-RS resource. A base station can indicate to a UE that a CSI-RS resource in a CSI-RS resource set is activated and / or deactivated.

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

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

[0150] A downlink DMRS can be transmitted by a base station and used by a UE for channel estimation. For example, a downlink DMRS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network can support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration can support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station can semi-statically configure a UE with a number (e.g., a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, a DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, a DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. A radio network can support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, where a DMRS location, a DMRS pattern, and / or a scrambling sequence can be the same or different. A base station can transmit a downlink DMRS and a corresponding PDSCH using a same precoding matrix. A UE can use the one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.

[0151] In an example, a transmitter (e.g., a base station) can use a precoder matrix for a portion of a transmission bandwidth. For example, a transmitter can 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 can be different based on the first bandwidth being different than the second bandwidth. A UE can assume a same precoding matrix is used across a set of PRBs. The set of PRBs can be denoted as a precoding resource block group (PRG).

[0152] A PDSCH can include one or more layers. A UE can assume that at least one symbol with a DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer can configure a PDSCH with up to 3 DMRSs.

[0153] Downlink PT-RS can be transmitted by a base station and used by a UE for phase noise compensation. Whether or not a downlink PT-RS is present can depend on RRC configuration. The presence and / or pattern of a downlink PT-RS can be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters that can be indicated by DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of a downlink PT-RS can be associated with one or more DCI parameters including at least MCS. An NR network can support multiple PT-RS densities defined in time / frequency domain. When present, a frequency domain density can be associated with at least one configuration of a scheduled bandwidth. A UE can take a same precoding for a DMRS port and a PT-RS port. The number of PT-RS ports can be fewer than the number of DMRS ports in a scheduled resource. A downlink PT-RS can be confined in a scheduled time / frequency duration for a UE. A downlink PT-RS can be transmitted on a symbol to facilitate phase tracking at a receiver.

[0154] A UE can transmit an uplink DMRS to a base station for channel estimation. For example, a base station can use an uplink DMRS for consistent demodulation of one or more uplink physical channels. For example, a UE can transmit an uplink DMRS with a PUSCH and / or a PUCCH. An uplink DM-RS can span a similar frequency range as a frequency range associated with a corresponding physical channel. A base station can configure a UE with one or more uplink DMRS configurations. At least one DMRS configuration can support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs can be configured to be transmitted at one or more symbols of a PUSCH and / or a PUCCH. A base station can semi-statically configure a UE with a number (e.g., a maximum number) of front-loaded DMRS symbols of a PUSCH and / or a PUCCH that the UE can use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network can support a common DMRS structure (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) for downlink and uplink, where a DMRS location, a DMRS pattern, and / or a scrambling sequence of a DMRS can be the same or different.

[0155] A PUSCH can include one or more layers, and a UE can transmit at least one symbol with a DMRS present on a layer of the one or more layers of the PUSCH. In an example, an upper layer can configure a PUSCH with up to three DMRSs.

[0156] Uplink PT-RS (which can be used by a base station for phase tracking and / or phase noise compensation) can or can not be present depending on the UE's RRC configuration. The presence and / or pattern of uplink PT-RS can be configured on a UE- specific basis by a combination of RRC signaling and / or one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) that can be indicated by DCI. When configured, the dynamic presence of uplink PT-RS can be associated with one or more DCI parameters including at least MCS. A radio network can support multiple uplink PT-RS densities defined in time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can take a same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports can be fewer than the number of DMRS ports in the scheduled resources. By way of example, uplink PT-RS can be confined in the scheduled time / frequency duration for the UE.

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

[0158] A base station can semi-statically configure a UE with one or more SRS configuration parameters indicating at least one of: an SRS resource configuration identifier; a number of SRS ports; a time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); a slot, mini-slot, and / or subframe level periodicity; a slot of periodic and / or aperiodic SRS resources; a 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.

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

[0160] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamformed reference signals. A UE can perform downlink beam measurements based on downlink reference signals (e.g., channel state information reference signals (CSI-RS)) and generate a beam measurement report. A UE can perform a downlink beam measurement procedure after setting up an RRC connection with a base station.

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

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

[0163] CSI-RS, such as FIG. 12BThose illustrated in FIG. 11 (e.g., CSI-RSs 1101, 1102, 1103) can be transmitted by a base station and used by a UE for one or more measurements. For example, a UE can measure a reference signal received power (RSRP) of a configured CSI-RS resource. A base station can configure a UE with a reporting configuration, and the UE can report the RSRP measurement to the network (e.g., via one or more base stations) based on the reporting configuration. In an example, a base station can determine one or more transmission configuration indication (TCI) states including a plurality of reference signals based on the reported measurements. In an example, a base station can indicate the one or more TCI states to a UE (e.g., via RRC signaling, a MAC CE, and / or a DCI). A UE can receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, a UE can or can not have a beam correspondence capability. If a UE has a beam correspondence capability, the UE can determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of a corresponding Rx beam. If a UE does not have a beam correspondence capability, the UE can perform an uplink beam selection procedure to determine a spatial domain filter of a Tx beam. The UE can perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by a base station. The base station can select and indicate an uplink beam of the UE based on measurements of the one or more SRS resources transmitted by the UE.

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

[0165] FIG. 13AExamples of three downlink beam management procedures are shown: PI, P2, and P3. Procedure PI can enable UE measurements of transmission (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of PI, respectively). Beamforming at the TRP can include a Tx beam sweep for a set of beams (shown as ellipses rotating in a counterclockwise direction indicated by dashed arrows in the top row of PI and P2). Beamforming at the UE can include an Rx beam sweep for a set of beams (shown as ellipses rotating in a clockwise direction indicated by dashed arrows in the bottom row of PI and P3). Procedure P2 can be used to enable UE measurements of Tx beams of a TRP (shown as ellipses rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or base station can perform procedure P2 using a smaller set of beams than used in procedure PI, or using narrower beams than used in procedure PI. This can be referred to as beam refinement. The UE can perform procedure P3 for Rx beam determination by using the same Tx beams at the base station and sweeping Rx beams at the UE.

[0166] FIG. 13A Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable a base station to perform measurements of Tx beams of a UE, e.g., to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE can include, e.g., an Rx beam sweep from a set of beams (shown as ellipses rotating in a clockwise direction indicated by dashed arrows in the bottom row of U1 and U3). Beamforming at the base station can include, e.g., an Rx beam sweep from a set of beams (shown as ellipses rotating in a counterclockwise direction indicated by dashed arrows in the top row of U1 and U2). Procedure U2 can be used to enable a base station to adjust its Rx beams when the UE uses a fixed Tx beam. The UE and / or base station can perform procedure U2 using a smaller set of beams than used in procedure PI, or using narrower beams than used in procedure PI. This can be referred to as beam refinement. The UE can perform procedure U3 to adjust its Tx beams when the base station uses a fixed Rx beam.

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

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

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

[0170] FIG. 13A A four-step contention-based random access procedure is shown. Prior to initiating the procedure, a base station can transmit a configuration message 1310 to a UE. FIG. 13BThe illustrated procedure includes the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg 3 1313, and Msg 4 1314. Msg 1 1311 can include and / or be referred to as a preamble (or random access preamble). Msg 2 1312 can include and / or be referred to as a random access response (RAR).

[0171] The configuration message 1310 can be transmitted, for example, using one or more RRC messages. The one or more RRC messages can indicate, to a UE, one or more random access channel (RACH) parameters. The one or more RACH parameters can include 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 one or more RRC messages can be broadcast or multicast by a base station to one or more UEs. The one or more RRC messages can be UE-specific (e.g., a dedicated RRC message transmitted to a UE in an RRC CONNECTED state and / or an RRC INACTIVE state). The UE can determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313. Based on the one or more RACH parameters, the UE can determine a reception timing and a downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0172] The one or more RACH parameters provided in the configuration message 1310 can indicate one or more physical RACH (PRACH) occasions available for transmitting Msg 1 1311. The one or more PRACH occasions can be predefined. The one or more RACH parameters can indicate one or more available sets of one or more PRACH occasions (e.g., prach-ConfigIndex). The one or more RACH parameters can indicate an association between: (a) one or more PRACH occasions, and (b) one or more reference signals. The one or more RACH parameters can indicate an association between: (a) one or more preambles, and (b) one or more reference signals. The one or more reference signals can be SS / PBCH blocks and / or CSI-RSs. For example, the one or more RACH parameters can indicate a number of SS / PBCH blocks mapped to a PRACH occasion and / or a number of preambles mapped to a SS / PBCH block.

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

[0174] Msg 1 1311 can include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group can include one or more preambles. The UE can determine a preamble group based on a path loss measurement value and / or a size of Msg 3 1313. The UE can measure an RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, the UE can select at least one preamble associated with the one or more reference signals and / or a selected preamble group if an association between the one or more preambles and the at least one reference signal is configured by the RRC message.

[0175] The UE can determine a preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE can determine a preamble based on a path loss measurement, an RSRP measurement, and / or a size of Msg 3 1313. As another example, the one or more RACH parameters can indicate: a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station can use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and / or CSI-RSs). If the association is configured, the UE can determine a preamble included in Msg 1 1311 based on the association. Msg 1 1311 can be transmitted to the base station via one or more PRACH occasions. The UE can use one or more reference signals (e.g., SSBs and / or CSI-RSs) for selecting a preamble and for determining a PRACH occasion. The one or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) can indicate an association between a PRACH occasion and the one or more reference signals.

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

[0177] Msg 2 1312 received by the UE can include a RAR. In some scenarios, Msg 2 1312 can include multiple RARs corresponding to multiple UEs. Msg 2 1312 can be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 can be scheduled on a DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). Msg 2 1312 can indicate that Msg 1 1311 was received by the base station. Msg 2 1312 can include a time alignment command that can be used by the UE to adjust the transmission timing of the UE, a scheduling grant for transmission of Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting a preamble, the UE can start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg 2 1312. The UE can determine when to start the time window based on the PRACH occasion used by the UE to transmit the preamble. For example, the UE can start the time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH occasion starting from the end of the preamble transmission). The one or more symbols can be determined based on a numerology. The PDCCH can be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE can identify the RAR based on a radio network temporary identifier (RNTI). The RNTI can be used depending on one or more events that initiated the random access procedure. The UE can use a random access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH occasion in which the UE transmitted the preamble. For example, the UE can determine the RA-RNTI based on: where s_id can be an index of the first OFDM symbol of the PRACH occasion (e.g., 0≤ s_id< 14), t_id can be an index of the first slot in a system frame of the PRACH occasion (e.g., 0≤ t_id< 80), f_id can be an index of the PRACH occasion in the frequency domain (e.g., 0≤ f_id< 8), and ul_carrier_id can be the UL carrier used for the preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier).

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

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

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

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

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

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

[0184] FIG. 13B Another two-step random access procedure is shown. (Compared to...)FIG. 13C And FIG. 13A Similar to the random access procedure illustrated in FIG. 13, the base station can transmit a configuration message 1330 to the UE prior to initiation of the procedure. The configuration message 1330 can be similar in some aspects to the configuration message 1310 and / or the configuration message 1320. FIG. 13A The procedure illustrated includes the transmission of two messages: a Msg A 1331 and a Msg B 1332.

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

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

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

[0188] The transport block 1342 can include data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an international mobile subscriber identity (IMSI)). The base station can transmit the Msg B 1332 as a response to the Msg A 1331. The Msg B 1332 can include 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 UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE can determine that the two-step random access procedure is successfully completed if: the preamble identifier in the Msg B 1332 matches the preamble transmitted by the UE; and / or the identifier of the UE in the Msg B 1332 matches the identifier of the UE in the Msg A 1331 (e.g., the transport block 1342).

[0189] The UE and the base station can exchange control signaling. The control signaling can be referred to as L1 / L2 control signaling and can originate from a PHY layer (e.g., layer 1) and / or a MAC layer (e.g., layer 2). The control signaling can include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0190] The downlink control signaling can include: a downlink scheduling assignment; an uplink scheduling grant indicating an uplink radio resource and / or a transport format; slot format information; a pre-emption indication; a power control command; and / or any other suitable signaling. The UE can receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH can be referred to as downlink control information (DCI). In some scenarios, the PDCCH can be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

[0191] The base station can attach one or more cyclic redundancy check (CRC) parity bits to the DCI in order to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of UEs), the base station can scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of UEs). Scrambling the CRC parity bits with the identifier can include a Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier can include a 16-bit value of a radio network temporary identifier (RNTI).

[0192] DCI can be used for different purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) can indicate paging information and / or a system information change notification. The P-RNTI can be predefined as “FFFE” in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. The SI-RNTI can be predefined as “FFFF” in hexadecimal. A DCI with CRC parity bits scrambled with a random access-RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate a dynamically scheduled unicast transmission and / or a trigger for PDCCH-ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate a contention resolution (e.g., similar to Msg 3 1313 of Msg 3 shown). Other RNTIs configured by a base station to a UE can include: a configured scheduling RNTI (CS-RNTI), a transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), a transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), a transmission power control SRS RNTI (TPC-SRS-RNTI), an interruption RNTI (INT-RNTI), a slot format indication RNTI (SFI-RNTI), a semi-persistent CSI RNTI (SP-CSI-RNTI), a modulation and coding scheme cell RNTI (MCS-C-RNTI), and / or the like. FIG. 14B The other RNTIs configured by the base station to the UE can include: a configured scheduling RNTI (CS-RNTI), a transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), a transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), a transmission power control SRS RNTI (TPC-SRS-RNTI), an interruption RNTI (INT-RNTI), a slot format indication RNTI (SFI-RNTI), a semi-persistent CSI RNTI (SP-CSI-RNTI), a modulation and coding scheme cell RNTI (MCS-C-RNTI), and / or the like.

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

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

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

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

[0197] The base station can transmit, to the UE, an RRC message including configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters can indicate an association between a search space set and a CORESET. A search space set can include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters can indicate: a number of PDCCH candidates per aggregation level to be monitored; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and / or whether the search space set is a common search space set or a UE-specific search space set. A set of CCEs in a common search space set can be predefined and known to the UE. A set of CCEs in a UE-specific search space set can be configured based on an identity (e.g., C-RNTI) of the UE.

[0198] As FIG. 15As shown, the UE can determine time-frequency resources of a CORESET based on the RRC message. The UE can determine CCE-to-REG mapping (e.g., interleaved or non-interleaved and / or mapping parameters) of the CORESET based on configuration parameters of the CORESET. The UE can determine a number of search space sets (e.g., up to 10) configured on the CORESET based on the RRC message. The UE can monitor a set of PDCCH candidates according to configuration parameters of the search space sets. The UE can monitor the set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. The monitoring can include decoding one or more PDCCH candidates in the set of PDCCH candidates according to monitored DCI formats. The monitoring can include decoding DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search space, and / or number of PDCCH candidates in UE-specific search space), and possible (or configured) DCI formats. The decoding can be referred to as blind decoding. The UE can determine that a DCI is valid for the UE in response to a CRC check (e.g., scrambled bits of CRC parity of a DCI matching an RNTI value). The UE can process information (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, etc.) contained in the DCI.

[0199] A UE can transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. Uplink control signaling transmission can include a hybrid automatic repeat request (HARQ) acknowledgement for a received DL-SCH transport block. The UE can transmit the HARQ acknowledgement after receiving the DL-SCH transport block. Uplink control signaling can include channel state information (CSI) indicating a channel quality of a physical downlink channel. The UE can transmit the CSI to the base station. Based on the received CSI, the base station can determine transmission format parameters (e.g., including multi-antenna and beamforming schemes) for downlink transmissions. Uplink control signaling can include a scheduling request (SR). The UE can transmit the SR indicating that uplink data is available for transmission to the base station. The UE can transmit UCI (e.g., HARQ-ACK, CSI report, SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE can transmit uplink control signaling via the PUCCH using one of several PUCCH formats.

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

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

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

[0203] FIG. 15 An example of a wireless device 1502 in communication with a base station 1504 is shown in accordance with embodiments of the present disclosure. The wireless device 1502 and the base station 1504 can be part of a mobile communication network, such as FIG. 2A the mobile communication network 100 shown, FIG. 2BThe mobile communication network 150 shown or any other communication network. FIG. 3 Only one wireless device 1502 and one base station 1504 are illustrated in the middle, but it should be understood that a mobile communication network can include more than one UE and / or more than one base station, which have the same or similar configurations as those shown. FIG. 4A

[0204] The base station 1504 can connect the wireless device 1502 to a core network (not shown) through radio communication 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 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. Downlink transmissions can be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.

[0205] In the downlink, data to be sent from the base station 1504 to the wireless device 1502 can be provided to a processing system 1508 of the base station 1504. The data can be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent from the wireless device 1502 to the base station 1504 can be provided to a processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 can implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 can include, for example, an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer with respect to FIG. 2B FIG. 2A FIG. 2B and FIG. 3 Layer 3 can include an RRC layer with respect to FIG. 4A .

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

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

[0208] like FIG. 16B As shown, wireless device 1502 and base station 1504 may include multiple antennas. These multiple antennas can be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, wireless device 1502 and / or base station 1504 may have a single antenna.

[0209] Processing systems 1508 and 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions discussed in this application. Although FIG. 16C Although not shown, the transmission processing system 1510, transmission processing system 1520, receiving processing system 1512 and / or receiving processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that can be executed to perform one or more of their respective functions.

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

[0211] The processing system 1508 and / or the processing system 1518 can be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 can include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keyboard, a display, a touchpad, a power supply, 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, etc.). The processing system 1508 and / or the processing system 1518 can receive user input data from and / or provide user output data to the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power supply and / or can be configured to distribute the power to the other components in the wireless device 1502. The power supply can include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 can be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

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

[0213] FIG. 18 Another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal for an antenna port. Filtering can be employed prior to transmission.

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

[0215] FIG. 19 Another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal for an antenna port. Filtering can be employed prior to transmission.

[0216] A wireless device can receive, from a base station, one or more messages (e.g., RRC messages) that include configuration parameters for a plurality of cells (e.g., primary cells, secondary cells). The wireless device can 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 part of the configuration parameters) can include parameters of physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer for configuring the wireless device. By way of example, the configuration parameters can include parameters for configuring physical layer and MAC layer channels, bearers, and the like. By way of example, the configuration parameters can include parameters that indicate values of timers for physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

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

[0218] In an example, a wireless device can receive, via / in a downlink control signal / channel transmission occasion (e.g., PDCCH monitoring occasion), a DCI that schedules a downlink signal (e.g., PDSCH, aperiodic CSI-RS).

[0219] In an example, the DCI can not include the TCI field. The time offset between the DCI and the downlink signal can be equal to or greater than the threshold. In the prior art, the wireless device can receive the downlink signal based on the TCI state activated / configured for the coreset in which the wireless device receives the DCI. For example, in response to i) the DCI not including the TCI field, and ii) the time offset being equal to or greater than the threshold, the wireless device can receive the downlink signal based on the TCI state activated / configured for the coreset. The TCI state for the coreset can correspond to a receive beam of the wireless device.

[0220] In an example, the time offset between the DCI and the downlink signal can be less than the threshold. In the prior art, the wireless device can receive the downlink signal based on the (default) TCI state activated / configured for the coreset with the lowest coreset index. For example, in response to the time offset being less than the threshold, the wireless device can receive the downlink signal based on the TCI state activated / configured for the coreset.

[0221] In an example, the wireless device can receive, e.g., from a base station, one or more configuration parameters of a cell. The configuration parameters can indicate control channel repetition. The one or more configuration parameters can indicate a repetition scheme (e.g., TDM scheme, FDM scheme) for the control channel repetition. The base station can transmit, via multiple coresets, multiple DCIs / PDCCHs (or repetitions of downlink control signals / channels) in multiple downlink control signal / channel transmission / repetition occasions (e.g., PDCCH monitoring occasions) for the control channel repetition. The multiple DCIs / PDCCHs (or downlink control signals / channels) can schedule / trigger downlink signals (e.g., PDSCH, aperiodic CSI-RS). The wireless device can monitor the multiple coresets in the multiple downlink control signal / channel transmission occasions for the multiple DCIs / PDCCHs (or repetitions of downlink control signals / channels). The wireless device can monitor PDCCH candidates in the multiple coresets based on at least two TCI states. The at least two TCI states can correspond to different receive beams of the wireless device. This can increase control channel reliability and robustness.

[0222] In prior art implementations, a wireless device can receive a downlink control signal / channel (e.g., DCI) scheduling a downlink signal (e.g., PDSCH, aperiodic CSI-RS) via a single core set. The wireless device can receive the downlink signal based on a TCI state of the core set. This can not be efficient when the wireless device receives the downlink control signal / channel scheduling the downlink signal via multiple core sets. This can not be efficient when the wireless device monitors multiple core sets for the downlink control signal / channel scheduling the downlink signal. For example, the wireless device can receive the downlink signal based on a first TCI state of the at least two TCI states. The base station can not have information that the wireless device receives the downlink signal based on the first TCI state. The base station can assume that the wireless device receives the downlink signal based on a different TCI state (e.g., a second TCI state of the at least two TCI states). The beams indicated by the first TCI state and the second TCI state can point in different directions and can be subject to different channel conditions. Misalignment of beams at the wireless device and the base station (e.g., using the first TCI state at the wireless device and employing the second TCI state at the base station) can result in missing reception of the downlink signal. This can reduce data rates, increase power consumption due to retransmission of the downlink signal, and increase latency for successful communication.

[0223] In prior art implementations, a wireless device can receive a downlink control signal / channel (e.g., DCI) scheduling a downlink signal (e.g., PDSCH, aperiodic CSI-RS) via a single core set. The wireless device can determine whether to apply a default TCI state (e.g., a TCI state of a core set with a lowest core set index or two activated TCI states indicated by a lowest TCI codepoint) to receive the downlink signal based on a threshold between the (received) downlink control signal / channel and the downlink signal. In control channel repetition, when a base station transmits repetitions of a downlink control signal / channel, the base station can not have information about which repetition(s) of the downlink control signal / channel the wireless device has successfully received. The wireless device and the base station can determine a time offset of misalignment between the downlink control signal / channel and the downlink signal. In response to the time offset at the wireless device being less than the threshold, the wireless device can receive the downlink signal based on the default TCI state. In response to the time offset at the base station being equal to or greater than the threshold, the base station can transmit the downlink signal based on an assumption that a different TCI state than the default TCI state is being used. This can result in missing reception of the downlink signal.

[0224] Exemplary embodiments enhance / improve reception of downlink signals when a downlink control signal / channel scheduling / triggering the downlink signals is transmitted via multiple coresets activated with at least two TCI states. When multiple coresets are activated with at least two TCI states, a wireless device can determine / select a selected TCI state among the at least two TCI states based on a predefined rule. The wireless device can receive the downlink signals based on the selected TCI state. Based on the predefined rule, a base station can have information that the wireless device receives the downlink signals based on the selected TCI state. Determining / selecting the selected TCI state based on the predefined rule can reduce beam misalignment between the base station and the wireless device. In an exemplary predefined rule, the wireless device can determine the selected TCI state based on at least two TCI state indexes of the at least two TCI states. In an exemplary predefined rule, the wireless device can determine the selected TCI state based on periodicities of search space sets associated with (e.g., mapped to) the at least two TCI states. In an exemplary predefined rule, the wireless device can determine the selected TCI state based on search space set indexes of search space sets associated with (e.g., mapped to) the at least two TCI states. In an exemplary predefined rule, the wireless device can determine the selected TCI state of a selected coreset having a lowest coreset index among multiple coreset indexes of the multiple coresets. In an exemplary predefined rule, the wireless device can determine the selected TCI state of a selected coreset monitored in a last downlink control signal / channel transmission / repetition occasion among multiple downlink control signal / channel transmission / repetition occasions. Exemplary embodiments can increase data rates, reduce power consumption, and reduce latency for successful communications.

[0225] In example implementations, a wireless device can determine whether to apply a default TCI state (e.g., a TCI state of a coreset with a lowest coreset index or two activated TCI states indicated by a lowest TCI codepoint) to receive a downlink signal based on a threshold between a reference downlink control signal / channel transmission / repetition occasion and the downlink signal among multiple downlink control signal / channel transmission / repetition occasions. In an example, the reference downlink control signal / channel transmission / repetition occasion can be a last downlink control signal / channel transmission / repetition occasion among the multiple downlink control signal / channel transmission / repetition occasions. This can result in the wireless device and the base station determining a time offset of an alignment between a downlink control signal / channel and a downlink signal. In response to the time offset at the wireless device being less than the threshold, the wireless device can receive the downlink signal based on the default TCI state. In response to the time offset at the base station being less than the threshold, the base station can transmit the downlink signal based on an assumption that the default TCI state is being used. The wireless device and the base station can determine a same (or similar or substantially similar) time offset between the downlink control signal / channel and the downlink signal.

[0226] In an example, a base station can configure one or more aperiodic trigger states (e.g., 1, 64, 128 aperiodic trigger states) for a wireless device using an information element (IE) CSI-AperiodicTriggerStateList. A codepoint of a CSI request field in a DCI can be associated with (or indicate) an aperiodic trigger state among the one or more aperiodic trigger states. In one example, an aperiodic trigger state can include one or more reporting configurations (e.g., 1, 8, 16 reporting configurations provided by a higher layer parameter associatedReportConfigInfoList). Based on receiving the DCI with the CSI request field indicating the aperiodic trigger state, the wireless device can perform measurements of CSI-RS and aperiodic reporting according to the one or more reporting configurations (e.g., in associatedReportConfigInfoList) for the aperiodic trigger state.

[0227] In one example, a reporting configuration (e.g., provided by a higher layer parameter CSI-AssociatedReportConfigInfo) of the one or more reporting configurations can be identified / associated with a reporting configuration index (e.g., provided by a higher layer parameter CSI-ReportConfigId). In one example, a reporting configuration can include one or more CSI resources (e.g., 1, 8, 16 CSI resources). In one example, an aperiodic CSI resource of the one or more CSI resources can be associated with one or more TCI-State configured TCI states (provided by a higher layer parameter qcl-info in an IE CSI-AperiodicTriggerStateList). A TCI state can provide a QCL assumption (e.g., RS, RS source, SS / PBCH block, CSI-RS). A TCI state can provide a QCL type (e.g., QCL-TypeA, QCL-TypeD, etc.).

[0228] In one example, a wireless device can receive, from a base station, a DCI with a CSI request field. The wireless device can receive the DCI in a PDCCH. The wireless device can receive the DCI while monitoring the PDCCH. In one example, the DCI with the CSI request field can initiate / indicate / trigger an aperiodic trigger state of the one or more aperiodic trigger states. In one example, a codepoint of the CSI request field in the DCI can indicate the aperiodic trigger state. In one example, the aperiodic trigger state can include one or more reporting configurations (e.g., a list of NZP-CSI-RS-ResourceSet). In one example, a reporting configuration (e.g., NZP-CSI-RS-ResourceSet) of the one or more reporting configurations can include one or more CSI resources (e.g., aperiodic CSI-RS resources, NZP-CSI-RS-Resources).

[0229] In one example, the base station can not configure a higher layer parameter trs-Info for the reporting configuration. In one example, configuring the reporting configuration without the higher layer parameter trs-Info can include a first antenna port for a first aperiodic CSI resource of the one or more CSI resources being different from a second antenna port for a second aperiodic CSI resource of the one or more CSI resources. In one example, configuring the reporting configuration without the higher layer parameter trs-Info can include the antenna port for each aperiodic CSI-RS resource of the one or more CSI resources being different. In one example, the base station can not configure a higher layer parameter repetition for the reporting configuration. In one example, a scheduling offset between a last symbol of the PDCCH carrying the DCI and a first symbol of the one or more CSI resources in the reporting configuration can be less than a second threshold (e.g., beamSwitchTiming). In one example, the wireless device can report the second threshold. In one example, the second threshold can be a first value (e.g., 14, 28, 48 symbols).

[0230] In one example, an aperiodic CSI resource of the one or more CSI resources can be associated with a first TCI state of the one or more TCI-State configurations. In one example, the first TCI state can indicate at least one first RS. In one example, the first TCI state can indicate at least one first QCL type. In one example, the aperiodic CSI resource being associated with the first TCI state can include the wireless device receiving an aperiodic CSI-RS of the aperiodic CSI resource, the aperiodic CSI-RS having the at least one first RS (indicated by the first TCI state) with respect to the at least one first QCL type indicated by the first TCI state.

[0231] In one example, the base station can transmit a downlink signal with a second TCI state. In one example, the second TCI state can indicate at least one second RS. In one example, the second TCI state can indicate at least one second QCL type. The wireless device can receive the downlink signal in one or more first symbols. The wireless device can receive an aperiodic CSI-RS for an aperiodic CSI resource in one or more second symbols. In one example, the one or more first symbols and the one or more second symbols can overlap (e.g., in whole or in part). In one example, the downlink signal and the aperiodic CSI-RS (or aperiodic CSI-RS resource) can overlap based on the one or more first symbols and the one or more second symbols overlapping.

[0232] In one example, the downlink signal and the aperiodic CSI-RS (or aperiodic CSI-RS resource) can overlap in time duration. In one example, the time duration can be at least one symbol. In one example, the time duration can be at least one slot. In one example, the time duration can be at least one subframe. In one example, the time duration can be at least one mini-slot. In one example, the time duration can be the one or more second symbols. In one example, the time duration can be the one or more first symbols.

[0233] In one example, the downlink signal can be a PDSCH scheduled with an offset greater than or equal to a first threshold (e.g., Threshold-Sched-Offset, timeDurationForQCL). In one example, the downlink signal can be a second aperiodic CSI-RS scheduled with an offset greater than or equal to a second threshold (e.g., beamSwitchTiming) when the second threshold is a first value (e.g., 14, 28, 48 symbols). In one example, the downlink signal can be an RS (e.g., periodic CSI-RS, semi-persistent CSI-RS, SS / PBCH block, etc.).

[0234] In one example, the wireless device can apply the QCL assumption provided / indicated by the second TCI state when receiving the aperiodic CSI-RS based on the downlink signal with the second TCI state overlapping with the aperiodic CSI-RS (or aperiodic CSI-RS resource) when the scheduling offset between the last symbol of the PDCCH and the first symbol is less than the second threshold. In one example, applying the QCL assumption (provided / indicated by the second TCI state) when receiving the aperiodic CSI can include: the wireless device receiving the aperiodic CSI-RS, the aperiodic CSI-RS having the at least one second RS (indicated by the second TCI state) with respect to the at least one second QCL type (indicated by the second TCI state).

[0235] In one example, a scheduling offset between a last symbol of the PDCCH carrying the DCI and a first symbol of the one or more CSI resources in the reporting configuration can be equal to or greater than a second threshold (e.g., beamSwitchTiming). In one example, the wireless device can report the second threshold. In one example, the second threshold can be a first value (e.g., 14, 28, 48 symbols). Based on the scheduling offset being equal to or greater than the second threshold, the wireless device can apply the QCL assumption (provided by the first TCI state) for an aperiodic CSI resource of the one or more CSI resources in the reporting configuration. In an example, applying the QCL assumption (provided by the first TCI state) for the aperiodic CSI resource can include the wireless device receiving an aperiodic CSI-RS for the aperiodic CSI resource, the aperiodic CSI-RS having the at least one first RS (indicated by the first TCI state) with respect to the at least one first QCL type (indicated by the first TCI state).

[0236] FIG. 20Exemplary configuration parameters of control and / or data in accordance with aspects of the embodiments of this disclosure are shown. A wireless device can receive one or more radio resource control (RRC) messages including configuration parameters of a cell. The configuration parameters can include one or more parameters of a serving cell configuration (e.g., ServingCellConfig). The one or more parameters of the serving cell configuration can indicate one or more downlink bandwidth parts (e.g., a list of BWP-Downlink). The one or more parameters of the serving cell configuration can indicate one or more uplink bandwidth parts (e.g., a list of BWP-Uplink). The downlink bandwidth part (e.g., BWP-Downlink) and / or the uplink bandwidth part (e.g., BWP-Uplink) can include a bandwidth part index (e.g., bwp-Id), configuration parameters of a cell-common downlink bandwidth part (e.g., BWP-DownlinkCommon), and / or a UE-specific downlink bandwidth part (e.g., BWP-DownlinkDedicated). For example, the bandwidth part index (bwp-Id) can indicate a bandwidth part configuration, where the index of the bandwidth part is the bandwidth part index. The bandwidth part configuration can include location and bandwidth information (locationAndBandwidth). The locationAndBandwidth can indicate a starting resource block (RB) of the bandwidth part and a bandwidth of the bandwidth part based on a reference point (e.g., point A of the carrier / cell of the bandwidth part). The bandwidth part configuration can include a subcarrier spacing (e.g., subcarrierSpacing) and a cyclic prefix (e.g., cyclicPrefix). For example, the subcarrier spacing can be one of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, and 960 kHz. For example, the cyclic prefix can be one of a normal cyclic prefix and an extended cyclic prefix.

[0237] Configuration parameters for a cell-specific downlink bandwidth (e.g., BWP-DownlinkCommon) can include genericParameters, pdcch-ConfigCommon, and / or pdsch-ConfigCommon. For example, pdcch-ConfigCommon can include cell-specific parameters for receiving downlink control information (DCI) via a cell-specific downlink bandwidth part (e.g., initial BWP). For example, pdsch-ConfigCommon can include cell-specific parameters for receiving transport blocks (TBs) PDSCHs via a cell-specific downlink bandwidth part. Configuration parameters for a UE-specific downlink bandwidth part (e.g., BWP-DownlinkDedicated) can include pdcch-Config, pdsch-Config, sps-Config, and / or radioLinkMonitoringConfig (e.g., RLM-Config). Configuration parameters can include sps-ConfigList and / or beamFailureRecoverySCellConfig. For example, beamFailureRecoverySCellConfig can include reference signal parameters for beam failure recovery for a secondary cell. For example, pdcch-Config can include parameters for receiving DCI for a UE-specific downlink bandwidth part. For example, pdsch-Config can include parameters for receiving PDSCHs of TBs for a UE-specific downlink bandwidth part. For example, sps-Config can include parameters for receiving semi-persistent scheduling PDSCHs. A base station can configure SPS for a BWP or a list of SPSs for a BWP. For example, radioLinkMonitoringConfig can include parameters for radio link monitoring.

[0238] Configuration parameters of pdcch-Config can include at least one of a coreset set, a search space set, a downlink preemption (e.g., downlinkPreemption), a transmission power control (TPC) for PUSCH (e.g., tpc-PUSCH), a TPC for PUCCH, and / or a TPC for SRS. Configuration parameters can include a list of search space switching groups (e.g., searchsSpaceSwitchingGroup), a search space switching timer (e.g., searchSpaceSwitchingTimer), an uplink cancellation, and / or a monitoring capability configuration (e.g., monitoringCapabilityConfig). A base station can configure a list of search space switching groups, where a wireless device can switch from a first search space group to a second search space group based on a search space switching timer or rule, an indication, or an event. A base station can configure up to K (e.g., K = 3) coresets for a BWP of a cell. Downlink preemption can indicate whether to monitor for downlink preemption indications for a cell. A monitoring capability configuration can indicate whether to configure a monitoring capability of a wireless device for a cell, where the capability is based on a basic capability or an advanced capability. A base station can configure up to M (e.g., M = 10) search spaces for a BWP of a cell. tpc-PUCCH, tpc-PUSCH, or tpc-SRS can enable and / or configure reception of TPC commands for PUCCH, PUSCH, or SRS, respectively. An uplink cancellation can indicate to monitor for an uplink cancellation of a cell.

[0239] Configuration parameters of pdcch-ConfigCommon can include control resource set zero (e.g., controlResourceSetZero), common control resource set (e.g., commonControlResourceSet), search space zero (e.g., searchSpaceZero), list of common search spaces (e.g., commonSearchSpaceList), search space for SIB1 (e.g., searchSpaceSIB1), search space for other SIBs (e.g., searchSpaceOtherSystemInformation), search space for paging (e.g., pagingSearchSpace), search space for random access (e.g., ra-SearchSpace), and / or first PDCCH monitoring occasion. Control resource set zero can include parameters of a first coreset with index value zero. Corest zero can be configured for an initial bandwidth part of a cell. A wireless device can use control resource set zero in a BWP of the cell, where the BWP is not the initial BWP of the cell based on one or more conditions. For example, a numerology of the BWP can be the same as a numerology of the initial BWP. For example, the BWP can include the initial BWP. For example, the BWP can include control resource set zero. Common control resource set can be an additional common coreset that can be used for common search space (CSS) or UE-specific search space (USS). A base station can configure a bandwidth of the common control resource set to be less than or equal to a bandwidth of control resource set zero. The base station can configure the common control resource set such that it is contained within control resource set zero (e.g., CORESET#0). The list of common search spaces can include one or more CSSs. The list of common search spaces can not include a search space with index zero (e.g., SS#0). The first PDCCH monitoring occasion can indicate a monitoring occasion for a paging occasion. The base station can configure a search space for monitoring DCI for paging (e.g., pagingSearchSpace), for RAR monitoring (e.g., ra-SearchSpace), for SIB1 (e.g., searchSpaceSIB1), and / or for other SIBs other than SIB1 (e.g., searchSpaceOtherSystemInformation). The search space with index zero (e.g., searchSpaceZero, SS#0) can be configured for an initial BWP of a cell. Similar to corset#0, SS#0 can be used in a BWP of the cell based on one or more conditions.

[0240] FIG. 21Exemplary configuration parameters of a coreset are shown in accordance with aspects of embodiments of the present disclosure. A ControlResourceSet (coreset) can include a coreset index (e.g., ControlResourceSetld), frequency domain resources (e.g., frequencyDomainResources), a duration of the coreset (e.g., a number of OFDM symbols between [1, maxCoReSetDuration] where maxCoReSetDuration = 3), and a control channel element (CCE) to resource element group (REG) mapping type (e.g., between interleaved and non-interleaved). When the CCE-REG mapping type is configured as interleaved, the base station can also configure a bundle size of the REGs (e.g., reg-BundleSize) and an interleaver size (e.g., interleaverSize). The coreset can also include a precoder granularity (e.g., between same as REG bundle (e.g., sameAsREG-bundle) and across all contiguous RBs (e.g., allContiguousRBs)). For example, when the precoder granularity is configured as “same as REG bundle,” the wireless device can assume the same precoder is used across the REGs in the bundle. For example, when the precoder granularity is configured as “across all contiguous RBs,” the wireless device can assume the same precoder is used across the RBs in the contiguous RBs of the coreset. The coreset can include a list of TCI states, where the coreset is not coreset #0. The coreset can include a parameter of TCI presence in DCI. If the coreset is configured with TCI presence in DCI, the wireless device can expect that the DCI format including the TCI indication in the DCI based on the DCI format is scheduled via the search space associated with the coreset. For example, the DCI format can be DCI format 1_1 and / or DCI format 0_1. The coreset can optionally include one or more of a DMRS scrambling identity, a coreset pool index, an enhanced coreset index (e.g., ControlResourceSetld-v16xy), TCI presence in DCI for DCI format 1_2, and an RB offset. For example, when the enhanced coreset index is present in the coreset configuration, the wireless device can ignore the coreset index. The enhanced coreset index can indicate a value between [0, …, 15] while the coreset index can indicate a value between [0, …, 11].

[0241] A search space can be associated with a control resource set, where a wireless device can determine a search space candidate and / or a monitoring occasion of the search space based on a configuration of the search space and the control resource set. A search space can be associated with a control resource set, where a wireless device can determine a search space candidate and / or a monitoring occasion of the search space based on a configuration of the search space and the control resource set. When a search space is associated with a control resource set or a control resource set is associated with a search space, parameters of the search space can include an index of the control resource set.

[0242] A search space can include an index of the search space (e.g., searchSpaceId), an index of an associated control resource set (e.g., controlResourceSetld), a monitoring periodicity and an offset (e.g., a periodicity in terms of a number of slots and an offset in terms of a number of slots, a periodicity between [1, 2560] slots, an offset between [0, …, P-1], where P is the periodicity). A search space can include a duration, where a wireless device can monitor the search space in consecutive slots starting from a monitoring occasion based on the duration. A base station can not configure a duration for a search space scheduling DCI format 2_0. A maximum duration value can be periodicity - 1 (e.g., repeating in every slot within the interval / periodicity). A search space can include monitoring symbols within a slot (e.g., a bitmap of OFDM symbol sizes in a slot (e.g., 12 for extended cyclic prefix (CP), 14 for normal CP)). A search space can include a set of multiple candidates per aggregation level (e.g., a first number of candidates for aggregation level L = 1, a second number of candidates for aggregation level L = 2, and so on). A search space can include a search space type (e.g., between CSS and USS). Each CSS or USS can include one or more DCI formats monitored in the search space. For example, for a CSS, one or more of DCI format 0_0 / 1_0, DCI format 2_0, DCI format 2_1, DCI format 2_2, and DCI format 2_3 can be configured. For a USS, a base station can configure a list of search space group indexes (if configured). For a USS, a base station can configure a frequency monitoring occasion / location for wideband operation for unlicensed spectrum or licensed spectrum. In the specification, DCI format 0_0 / 1_0 can be used interchangeably with DCI format 0-0 / 1-0 or fallback DCI format. DCI format 0_1 / 1_1 can be used interchangeably with DCI format 0-1 / 1-1 or non-fallback DCI format. DCI format 0_2 / 1_2 can be used interchangeably with DCI format 0-2 / 1-2 or non-fallback DCI format.

[0243] Configuration parameters of pdsch-Config can include parameters for receiving a transport block. For example, the configuration parameters can include a data scrambling identity for PDSCH, a DM-RS mapping type (e.g., between mapping type A and mapping type B), a list of transmission configuration indicator (TCI) states, parameters of a (virtual RB) to (physical RB) interlacer, a resource allocation type (e.g., between resource allocation type 0, resource allocation type 1, or a dynamic switch between the two), a list of time domain allocations, an aggregation factor, a list of rate matching patterns, an RBG (resource block group) size, an MCS table (e.g., between QAM 256 and QAM 64 Low SE, between high MCS or low MCS), a maximum code word (e.g., between 1 or 2), parameters related to PRB bundling, a maximum MIMO layer, a minimum scheduling offset related to power saving techniques, and / or one or more parameters related to DCI format 1_2 (e.g., compact DCI or smaller size DCI format).

[0244] In an example, a base station can configure a coreset with multiple TCI states. The base station can indicate a TCI of the multiple TCI states of the coreset as an active TCI state via a MAC CE command or a DCI command. For example, a serving cell index (e.g., a serving cell ID) can indicate an index of a serving cell to which the MAC CE command applies. A coreset index (e.g., a coreset ID) can indicate a coreset index to which the MAC CE command applies. A TCI state index (e.g., a TCI state ID) can indicate a TCI state identified by TCI-StateId. For example, when the coreset is CORESET#0, the TCI state ID can indicate one of the first 64 TCI states of pdsch-Config configured for a BWP of the serving cell. The BWP of the serving cell can be an active BWP of the cell. When the coreset is not CORESET#0 (e.g., the CORESET ID is not zero), the TCI state ID can indicate a TCI state of the multiple TCI states configured for the coreset in pdcch-Config.

[0245] In an example, a physical downlink control channel (PDCCH) can include one or more control channel elements (CCEs). For example, the PDCCH can include one CCE that can correspond to an aggregation level (AL) = 1. For example, the PDCCH can include two CCEs that correspond to an AL of two (AL = 2). For example, the PDCCH can include four CCEs that correspond to an AL of four (AL = 4). For example, the PDCCH can include eight CCEs that correspond to an AL of eight (AL = 8). For example, the PDCCH can include sixteen CCEs that correspond to an AL of sixteen (AL = 16).

[0246] In an example, a PDCCH can be carried on one or more control resource sets (coresets). A coreset can include N rb coreset resource blocks (RBs) in a frequency domain and N symbol coreset symbols in a time domain. For example, N rb coreset can be a multiple of 6 RBs (e.g., 6, 12, 18,...). For example, N symbol coreset can be 1, 2, or 3. A CCE can include M (e.g., M = 6) resource element groups (REGs). For example, one REG can include one RB during one OFDM symbol. REGs within a coreset can be ordered / numbered in an increasing order in a time-first manner, starting from 0 for the first OFDM symbol and the lowest number (e.g., lowest frequency) RBs in the coreset. A wireless device can increase the numbering in the first OFDM symbol by increasing the frequency location or RB index. Responsive to all RBs of the first symbol can have been indexed, the wireless device can move to the next symbol. The wireless device can map one or more REG indices for one or more 6 RBs in one or more of N rb coreset Rbs within N symbol coreset OFDM symbols of a coreset.

[0247] In an example, a wireless device can receive configuration parameters from a base station. The configuration parameters can indicate one or more coreset(s). One coreset can be associated with one CCE-to-REG mapping. For example, a single coreset can have a single CCE mapping to physical RB / resources of the single coreset. For example, the CCE-to-REG of a coreset can be interleaved or non-interleaved. For example, a REG bundle can include L consecutive REGs (e.g., iL, iL+1, …, iL+L-1). For example, L can be a REG bundle size (e.g., L=2 or 6 for N_symbol_coreset=1, and L=N_symbol_coreset or 6 when N_symbol_coreset is 2 or 3). An index (e.g., i) of a REG bundle can be in the range of [0, 1, …, N_reg_coreset / L-1]. For example, N_reg_coreset can be defined as N_rb_coreset*N_symbol_coreset (e.g., the total number of REGs in a single coreset). For example, a CCE of the jth index can include one or more REG bundles of {f(6j / L), f(6j / L+1), …, f(6j / L+6 / L-1)}. For example, f(x) can be an interleaver function. In an example, when the CCE-to-REG mapping can be non-interleaved, f(x) can be x (e.g., the jth CCE can include 6j / L, 6j / L+1, …, and 6j / L+6 / L-1). When the CCE-to-REG mapping can be interleaved, L can be defined as one of {2, 6} when N_symbol_coreset is 1, or L can be defined as one of {N_symbol_coreset, 6} when N_symbol_coreset is 2 or 3. When the CCE-to-REG mapping can be interleaved, the function f(x) can be defined as (rC+c+n_shift) mod(N_reg_coreset / L), where x=cR+r, r=0, 1, …, R-1, c=0, 1, …, C-1, C=N_reg_coreset / (L*R), and R is one of {2, 3, 6}.

[0248] For example, the configuration parameters can include frequencyDomainResources, which can define N rb coreset. The configuration parameters can include a duration, which can define N symbol coreset. The configuration parameters can include cce-REG-MappingType, which can select between interleaved or non-interleaved mapping. The configuration parameters can include reg-BundleSize, which can define a value of L for interleaved mapping. For non-interleaved mapping, L = 6 can be predetermined. The configuration parameters can include shiftIndex, which can determine n shift as one of {0, 1, …, 274}. When precoder granularity (e.g., precoderGranularity indicated / configured by the configuration parameters) is configured as sameAsREG-bundle, the wireless device can determine / assume a same precoding for REGs within a REG bundle. When precoderGranularity is configured as allContiguousRBs, the wireless device can determine / assume a same precoding for all REGs within a set of contiguous RBs of the coreset.

[0249] For a first coreset (e.g., CORESET#0), L = 6, R = 2, n shift = cell ID, and precoderGranularity = sameAsREG-bundle can be defined / configured.

[0250] In an example, a base station can transmit one or more messages including configuration parameters. The configuration parameters can be for a plurality of serving cells of a wireless device. The configuration parameters can include parameters to enable control channel repetition. For example, the control channel repetition can be transmitted via one or more serving cells. The control channel repetition can schedule one or more resources for a transport block. The transport block can be transmitted via one or more PDSCHs or one or more PUSCHs. For example, the control channel repetition can be transmitted via a single cell, where the single cell can operate with a single transmission and reception point (TRP) or multiple TRPs. The base station can transmit one or more control channels of the control channel repetition via one or more resources (e.g., or multiple downlink control signal / channel transmission occasions) in different frequency resources (e.g., repetition in frequency domain or in multiple carriers / cells). The one or more resources can overlap in time domain. The base station can transmit one or more second control channels of the control channel repetition via one or more second resources (e.g., or multiple downlink control signal / channel transmission occasions) in different time resources (e.g., repetition in time domain or in multiple slots). The one or more second resources can overlap in frequency domain. For example, the base station can transmit repetitions of the control channel repetition via multiple coreset of a single cell. For example, the base station can transmit the control channel repetition via multiple search spaces of a single cell.

[0251] In an example, the control channel repetition can be transmitted via multiple PDCCHs. For example, a PDCCH can indicate a physical control channel transmitted in one search space candidate. The search space candidate can include one or more CCEs based on an aggregation level. The multiple PDCCHs can be transmitted via multiple coresets of multiple cells. For example, the base station can transmit a PDCCH of the multiple PDCCHs via a coreset of a cell of the multiple cells. The multiple PDCCHs can be transmitted via multiple coresets of a cell. For example, the base station can transmit a PDCCH of the multiple PDCCHs via a coreset of the multiple coresets. The multiple PDCCHs can be transmitted via multiple search spaces, where a PDCCH of the multiple PDCCHs can be transmitted via a search space of the multiple search spaces. The multiple PDCCHs can be transmitted via multiple search space candidates, where each PDCCH of the multiple PDCCHs can be transmitted via a respective search space candidate of the multiple search space candidates. The multiple search space candidates can belong to a single search space or multiple search spaces. A search space can include a set of search space candidates on a monitoring occasion. The monitoring occasion of a search space can refer to a timing occasion in which a wireless device can monitor the search space candidates for receiving DCI / PDCCH.

[0252] In an example, a PDCCH of the plurality of PDCCHs that control channel repetition can convey / transmit a DCI based on a DCI format. For example, a first DCI of a first PDCCH of the plurality of PDCCHs can be the same as a second DCI of a second PDCCH of the plurality of PDCCHs. For example, a content of the first DCI / PDCCH can be the same as a content of the second DCI / PDCCH. Based on the same content of the plurality of PDCCHs, the wireless device can aggregate the plurality of DCI / PDCCHs before decoding the DCI / PDCCH. For example, when control channel repetition is transmitted / performed via the same content of the DCI / PDCCH, the wireless device can need to determine a reference frequency domain resource (e.g., reference downlink control signal / channel transmission / repetition occasion) and / or a reference time domain resource (e.g., reference downlink control signal / channel transmission / repetition occasion) and / or a reference CCE index and / or a reference REG index. For example, the wireless device can determine an aggregated DCI / PDCCH by aggregating the plurality of DCI / PDCCHs. The wireless device can decode the aggregated DCI / PDCCH.

[0253] For example, a reference frequency domain resource of the plurality of DCI / PDCCHs can be determined based on an earliest PDCCH (or a latest PDCCH) of the plurality of PDCCHs. For example, when a first PDCCH of the plurality of PDCCHs is transmitted in slot n and a second PDCCH of the plurality of PDCCHs is transmitted in slot n+1, the first PDCCH can determine the reference frequency domain resource. Similarly, a reference time domain resource and / or a reference CCE index and / or a reference REG can be determined based on the earliest PDCCH or the latest PDCCH. A reference frequency domain (and / or time domain) resource of the plurality of DCI / PDCCHs can be determined based on a CORESET index of one or more CORESETs that transmit the plurality of DCI / PDCCHs. For example, a minimum (or maximum) CORESET index of the one or more CORESETs can be used for the determination.

[0254] The reference frequency domain (and / or time domain) resource of the multiple DCI / PDCCHs can be determined based on a search space index of one or more search spaces where the multiple DCI / PDCCHs are transmitted. For example, the smallest (or largest) index of the one or more search spaces can be used for the determination. The reference frequency domain resource of the multiple DCI / PDCCHs can be determined based on a cell index of one or more cells where the multiple DCI / PDCCHs are transmitted. For example, the smallest (or largest) index of the one or more cells can be used for the determination. Similarly, the reference time domain resource and / or reference CCE index and / or reference REG can be determined based on a CORESET index, search space index, and / or cell index. A combination of transmission time, CORESET index, search space, and / or cell index can be used. For example, first, the reference frequency domain resource can be determined based on the transmission time of the DCI / PDCCH. When there are multiple DCI / PDCCHs transmitted simultaneously, the wireless device can use the CORESET index or search space index and / or cell index to further identify the reference DCI / PDCCH among the multiple DCI / PDCCHs. The wireless device can determine the reference DCI / PDCCH used for determining the reference frequency domain resource, reference time domain resource, reference CCE index, and / or reference REG index.

[0255] In an example, a base station can configure / indicate a maximum number of repetitions K of control channel repetition through / via a configuration parameter. The base station can transmit a number of repetitions M that is less than K. In response to M being less than K, a wireless device can determine the reference DCI / PDCCH based on a candidate DCI / PDCCH in the Kth repetition regardless of whether the Kth repetition has been actually transmitted (or whether the Kth repetition has been actually received). The wireless device can determine the reference DCI / PDCCH based on a first DCI / PDCCH that is a first repetition. The wireless device can determine the reference DCI / PDCCH based on a last DCI / PDCCH (e.g., Mth repetition) that has been actually transmitted. For convenience in the specification, this type of control channel repetition (e.g., repeating the same content on multiple DCI / PDCCHs) can be referred to as / termed a first control channel repetition mode (e.g., mode 1, repetition mode 1, first repetition mode). In an example, a base station can configure a list of time domain resource allocation entries. The time domain resource allocation entries can include a number of repetitions of a control channel, a scheduling offset between the control channel and a PDSCH, and / or a number of repetitions of the PDSCH. For example, the number of repetitions of the control channel can represent the number of repetitions K. Based on the number of repetitions, the wireless device can determine the reference DCI / PDCCH timing based on the Kth DCI / PDCCH repetition. The repeated DCI / PDCCHs can indicate an entry of the list of time domain resource allocation entries.

[0256] In an example, a first DCI / PDCCH of the plurality of DCI / PDCCHs can be different from a second DCI / PDCCH of the plurality of DCI / PDCCHs. For example, the wireless device can not aggregate the first DCI / PDCCH and the second DCI because the content of the first DCI / PDCCH can be different. The wireless device can attempt to decode the first DCI / PDCCH separately from the second DCI / PDCCH. For example, the wireless device can complete decoding of the control channel repetition when the wireless device has received at least one DCI / PDCCH of the plurality of DCI / PDCCHs. For example, the wireless device can be able to receive or transmit a TB scheduled by the plurality of DCI / PDCCHs when the wireless device has received at least one DCI / PDCCH of the plurality of DCI / PDCCHs. In the specification, this type of control channel repetition (e.g., via a plurality of DCI / PDCCHs conveying potentially different content, a DCI / PDCCH of the plurality of DCI / PDCCHs can schedule one or more resources of a transport block) can be referred to as / termed a second control channel repetition mode (e.g., mode 2, repetition mode 2, second repetition mode). For example, a reference DCI / PDCCH of the plurality of DCI / PDCCHs based on the second control channel repetition mode can be every DCI / PDCCH received by the wireless device.

[0257] FIG. 21 An example of PDCCH repetition is shown in accordance with aspects of the embodiments of this disclosure. A base station can transmit one or more RRC messages including configuration parameters. The configuration parameters can include parameters for control channel repetition. The parameters can include one or more scheduling carriers / cells for transmitting one or more PDCCHs / DCIs that repeat a control channel (or control channel repetition). The parameters can include one or more search spaces for control channel repetition. FIG. 21 An example of enabling control channel repetition via a first search space (SS#1) of a first carrier / cell (DL carrier #0) is shown. The parameters can indicate one or more indices of one or more search spaces of the first carrier and / or a carrier / cell index of the first carrier. The base station can transmit, via the first search space of the first carrier, a first PDCCH that schedules a TB via the first carrier. The base station can transmit, via the first search space of the first carrier, a second PDCCH that schedules a TB via the first carrier. The first PDCCH and the second PDCCH can be transmitted via multiple monitoring occasions of the first search space. The wireless device can aggregate the first PDCCH and the second PDCCH based on a first control channel repetition mode or can attempt to receive / decode each PDCCH independently based on a second control channel repetition mode. Based on the first PDCCH and / or the second PDCCH, the wireless device can receive a TB.

[0258] In an example, a base station can transmit one or more RRC messages indicating control channel repetition enabled for a first carrier / cell. Based on the indication of control channel repetition, a wireless device can determine one or more first search spaces of the first carrier / cell for control channel repetition based on an active BWP of the first carrier / cell. For example, the one or more first search spaces can be configured with non-fallback DCI formats, or configured with DCI format 11 and / or DCI format 12 and / or DCI format 0_1 and / or DCI format 0_2. In an example, the one or more RRC messages can indicate one or more search space indexes of the one or more first search spaces of control channel repetition. The one or more RRC messages can indicate one or more DCI formats where the wireless device can apply control channel repetition. The wireless device can determine the one or more first search spaces of the first carrier / cell based on the one or more DCI formats of control channel repetition.

[0259] In an example, a base station can transmit multiple DCI / PDCCHs, scheduling resources of a transport block of a cell, via multiple TRPs or via multiple core set pools or via multiple core set groups. For example, the base station can configure a first TRP (or a first core set pool) for a first cell via one or more RRC messages. The one or more RRC messages can include configuration parameters. The configuration parameters can include a first core set pool of the first cell. The configuration parameters can include a second core set pool of the first cell. For example, the second core set pool can correspond to a second TRP of the first cell. The base station can transmit a first DCI / PDCCH via a first search space of a first core set of the first core set pool. The base station can transmit a second DCI / PDCCH via a second search space of a second core set of the second core set pool. The first DCI / PDCCH and the second DCI / PDCCH can schedule resources of a transport block. The first / PDCCH and the second DCI / PDCCH can be a repetition transmission of control information (e.g., DCI). The transport block can be transmitted via the first TRP and the second TRP, for example. The transport block can be transmitted based on multiple TCI states. The transport block can be transmitted based on a TCI state, where the TCI state is associated with the multiple TCI states. The transport block can be transmitted via the first TRP or the second TRP, for example.

[0260] The configuration parameter can indicate a control channel repetition enabled / configured for the first cell. For example, parameters of a control channel repetition pattern can be configured. The control channel repetition pattern can be a first control channel repetition pattern or a second control channel repetition pattern. The configuration parameter can indicate a first coreset associated with (or configured with or of) a first coreset pool. The configuration parameter can indicate a second coreset associated with (or configured with or of) a second coreset pool. The wireless device can determine a pair of the first coreset and the second coreset based on a rule, where the repeated DCI / PDCCH can be transmitted. For example, the wireless device can determine the first coreset of the first coreset pool based on a search space associated with the first coreset, where the wireless device can monitor a DCI format via the search space. For example, the DCI format can be DCI format 1 1 or DCI format 0 1 or DCI format 1 2 or DCI format 0 2 (or DCI format 3 0 or DCI format 3 1). When there are multiple first search spaces of the first coreset pool configured with the DCI format, the wireless device can determine multiple first coresets of the first coreset pool. Similarly, the wireless device can determine the second coreset of the second coreset pool based on a search space associated with the second coreset, where the wireless device can monitor the DCI format via the search space. When there are multiple second search spaces of the second coreset pool configured with the DCI format, the wireless device can determine the multiple second search spaces. In an example, the wireless device can be configured to have at most one search space of the DCI format in each coreset pool.

[0261] In an example, the wireless device can determine the second core set of the second core set pool based on a first core set index of a first core set of the first core set pool. For example, the second index of the second core set can be the first core set index + GAP. For example, the GAP can be a determined / predetermined value (e.g., 0, 12). For example, the configuration parameter can include a parameter indicating the value of the GAP. In an example, the wireless device can determine the second core set based on a second search space associated with the second core set and the first search space. For example, the index of the second search space can be the first index of the first search space + SS-GAP. For example, the SS-GAP can be a predetermined value (e.g., 20, 0). For example, the wireless device can determine the second core set and / or the second search space based on an association configured by the configuration parameter. For example, the configuration parameter can indicate an association between each of the core sets / search spaces associated with the first core set pool and each of the core sets / search spaces associated with the second core set pool. In an example, the configuration parameter can include the first core set of the first core set pool and / or the first search space. The wireless device can monitor the first DCI / PDCCH via the first search space of the first core set pool. The configuration parameter can indicate / include a parameter indicating control channel repetition across multiple TRPs or multiple core set pools for the first core set or the first search space. Based on the parameter, the wireless device can determine the second core set of the second core set pool or the second search space. For example, the wireless device can determine the second core set based on one or more parameters of the first core set. For example, the same set of resource blocks configured for the first core set can be used for the second core set. For example, a monitoring occasion of the first search space can be used to determine a monitoring occasion of the second search space.

[0262] In an example, a base station can indicate control channel repetition based on (or for) a core set. For example, the base station can transmit multiple DCIs / PDCCHs via the core set. The base station can transmit the multiple DCIs / PDCCHs on multiple TRPs. The base station can transmit one of multiple RRC messages and / or MAC CEs indicating multiple TCI states activated for the core set. For example, the multiple TCI states can include a first TCI state corresponding to a first TRP of the multiple TRPs, and a second TCI state corresponding to a second TRP of the multiple TRPs. The base station can transmit one or more second RRC messages including configuration parameters for the core set. For example, the configuration parameters can indicate control channel repetition based on the core set. The configuration parameters can indicate control channel repetition across the multiple TRPs. The configuration parameters can indicate a repetition pattern across the multiple TRPs. For example, the repetition pattern (e.g., a TRP switching pattern) can be [0, …, 0, 1, …, 1], where 0 can represent the first TRP of the multiple TRPs, and 1 can represent the second TRP of the multiple TRPs. The base station can indicate, e.g., via the configuration parameters, a bitmap indicating a number of control channel repetitions. Each bit of the bitmap can represent which TRP can transmit the ith repetition. The repetition pattern can be [0, 1, 0, 1, …, 0, 1]. The repetition pattern can be [0, 0, …, 0, 1, 1, …, 1, 0, 0, …, 0, 1, 1, …, 1]. Various repetition patterns can be considered. Based on the repetition pattern, a wireless device can receive control channel repetitions based on a TCI state of the multiple TCI states. For example, when the repetition pattern indicates the first TRP, the wireless device can receive control channel repetitions based on the first TCI state. When the repetition indicates the second TRP, the wireless device can receive control channel repetitions based on the second TCI state.

[0263] FIG. 22An example of control channel repetition across multiple TRPs is shown in accordance with aspects of the embodiments of this disclosure. A base station can transmit one or more RRC messages including configuration parameters. The configuration parameters can indicate / include a first TRP (TRP#0) and a second TRP (TRP#1) associated with a cell. The configuration parameters can include / indicate control channel repetition across multiple TRPs (e.g., via the first TRP and the second TRP). The base station can transmit a first DCI / PDCCH (e.g., PDCCH#1) via the first TRP or a first coreset pool. The first DCI / PDCCH can include / indicate resources scheduling a TB via multiple TRPs. The base station can transmit a second DCI / PDCCH (e.g., PDCCH#2) via the second TRP or a second coreset pool. The second DCI / PDCCH can include / indicate resources scheduling the TB via multiple TRPs. The first DCI / PDCCH and the second DCI / PDCCH can indicate a same HARQ process index (e.g., HARQ-K) scheduling the TB. The base station can transmit a third DCI / PDCCH via the first TRP. The base station can transmit a fourth DCI / PDCCH (e.g., PDCCH#4) via the second TRP. Control information scheduling the TB can be repeated four times via multiple TRPs. A wireless device can monitor the first DCI / PDCCH and the third DCI / PDCCH based on a first TCI state associated with the first TRP or the first coreset pool. The wireless device can monitor the second DCI / PDCCH and the fourth DCI / PDCCH based on a second TCI state associated with the second TRP or the second coreset pool.

[0264] The base station can repeat the TB with four repetitions via the first TRP and four repetitions via the second TRP. When the wireless device can support simultaneous reception via the first TRP and the second TRP, the wireless device can simultaneously repeat the TB via the first TRP and the second TRP. When the wireless device can not support simultaneous reception via the first TRP and the second TRP, the base station can transmit repeated transmissions of the TB via the first TRP and the second TRP based on time domain division multiplexing. For example, the base station can transmit a first repetition of the repeated transmissions via the first TRP. The base station can transmit a second repetition of the repeated transmissions via the second TRP. A switching pattern between the first TRP and the second TRP can be configured by the base station based on RRC / MAC-CE / DCI signaling. The first DCI and the second DCI can schedule the repeated transmissions of the TB. Embodiments of control channel repetition via multiple TRPs can enhance reliability and bring better QoS experience.

[0265] In an example, a base station can transmit one or more RRC messages including configuration parameters. The configuration parameters can indicate control channel repetition enabled for a cell. The base station can transmit, via a plurality of coresets of the cell, a plurality of DCIs / PDCCHs scheduling a transport block. For example, the configuration parameters can configure a first coreset and a second coreset for control channel repetition. The configuration parameters can include / indicate a first search space associated with the first coreset. The configuration parameters can include / indicate a second search space associated with the second coreset. The configuration parameters can include / indicate a first TCI state associated with the first coreset. The configuration parameters can include / indicate a second TCI state associated with the second coreset. The first TCI state can be the same or different from the second TCI state. The configuration parameters can include / indicate a set of first TCI states associated with the first coreset. One or more MAC CEs can indicate a first TCI state of the set of first TCI states of the first coreset. For example, the configuration parameters can include / indicate a set of second TCI states associated with the second coreset. One or more second MAC CEs can indicate a second TCI state of the set of second TCI states of the second coreset. The configuration parameters can indicate that the first coreset and the second coreset are associated to schedule repeated DCIs / PDCCHs for the transport block.

[0266] In an example, the configuration parameters can indicate / include search spaces associated with the first coreset and the second coreset. The configuration parameters can include a plurality of coreset indexes. The configuration parameters can include a coreset index of the plurality of coreset indexes that indicates the first coreset. The configuration parameters can include one or more indexes of the plurality of coreset indexes, a repetition / additional coreset (e.g., a coreset for control channel repetition in addition to the first coreset, the second coreset). For example, an index of the one or more indexes can indicate the second coreset. When the first coreset and the second coreset are associated for control channel repetition, a first parameter of the first coreset and a second parameter of the second coreset can have a restriction in configuration. For example, a set of resource blocks (RBs) in a frequency domain of the first coreset can be the same as a set of resource blocks (or a subset or superset thereof) in the frequency domain of the second coreset. The wireless device can determine, for control channel repetition, a set of RBs belonging to the first coreset and the second coreset. For example, a first duration of the first coreset can be the same as a second duration of the second coreset. For example, a number of REGs of the first coreset can be the same as a number of REGs. For example, a number of CCEs of the first coreset can be the same as (or less than or greater than) a number of CCEs of the second coreset. The wireless device can determine the number of REGs based on the determined set of RBs or based on a set of RBs of the first coreset. For example, a first CCE-to-REG mapping type (e.g., between interleaved or non-interleaved) of the first coreset can be the same as a second CCE-to-REG mapping type of the second coreset. For example, a precoder granularity of the first coreset can be configured to be the same as a precoder granularity of the second coreset. For example, a first tci-PresenceInDCI of the first coreset can be the same as a second tci-PresenceInDCI of the second coreset. For example, a first rb-Offset of the first coreset can be the same as a second rb-Offset of the second coreset.

[0267] The first coreset and the second coreset can have potentially different configurations for one or more parameters. For example, the one or more parameters can include one or more TCI states. For example, the one or more parameters can include a DM-RS scrambling identity (e.g., pdcch-DMRS-ScramblingID). For example, the one or more parameters can include a coreset pool index (e.g., coresetPoolIndex). For example, the one or more parameters can include a coreset index.

[0268] When the wireless device can receive the first configuration parameters of the first coreset and the second configuration parameters of the second coreset, the wireless device determines whether a first number of CCEs of the first coreset is equal to or less than (or greater than) a second number of CCEs of the second coreset. Based on the determination, the wireless device can consider that the first coreset and the second coreset are available for control channel repetition. Otherwise, the wireless device can determine that the first coreset and the second coreset are not available for control channel repetition. Alternatively, the wireless device can determine a minimum number (e.g., M) of CCEs among the one or more numbers of CCEs of the one or more coresets (e.g., determine a coreset among the one or more coresets that has the minimum number of CCEs). For example, the one or more coresets can be configured / indicated / used for control channel repetition. The wireless device can determine / assume / consider a first number of REGs of a first coreset among the one or more coresets for control channel repetition. The wireless device can determine a second number of REGs of a second coreset among the one or more coresets. The wireless device can determine whether the first number of REGs is equal to the second number of REGs. In response to determining that the first number of REGs is equal to the second number of REGs, the wireless device can consider that control channel repetition is configured via the first coreset and the second coreset. Otherwise, the wireless device can treat the configuration as an error case and can not activate control channel repetition via the first coreset and the second coreset. In an example, the wireless device can determine a minimum number of REGs of the one or more coresets (e.g., determine a coreset that has the minimum number of REGs). The wireless device can assume the minimum number of REGs for control channel repetition.

[0269] In an example, the wireless device can determine a number of REGs of a first coreset among the one or more coresets that are configured for control channel repetition. The wireless device can determine a second number of REGs of a second coreset among the one or more coresets. The wireless device can determine whether the number of REGs is equal to the second number of REGs. In response to determining that the number of REGs is equal to the second number of REGs, the wireless device can consider that control channel repetition is configured via the first coreset and the second coreset. Otherwise, the wireless device can treat the configuration as an error case and can not activate control channel repetition via the first coreset and the second coreset. In an example, the wireless device can determine a minimum number of REGs of the one or more coresets (e.g., determine a coreset that has the minimum number of REGs). The wireless device can assume the minimum number of REGs for control channel repetition.

[0270] The configuration parameters of the search space associated with the first coreset and the second coreset can include / indicate a switching pattern or a mapping pattern of the first coreset and the second coreset. For example, the wireless device can determine a search space monitoring occasion based on the configuration parameters of the search space. The wireless device can determine the search space monitoring occasion based on the first coreset. The wireless device can determine a second search space monitoring occasion or an extended monitoring occasion based on the rule. For example, the wireless device can determine the second search space monitoring occasion as the next slot of the first monitoring occasion. The wireless device can determine the second search space monitoring occasion based on the second search space. The configuration parameters can indicate a bitmap of the number of OFDM symbols in a slot (or the number of slots, e.g., multiple slots). For each corresponding OFDM symbol or slot, the bitmap can indicate 0 for the first coreset or 1 for the second coreset. When 0 is indicated for an OFDM symbol, the wireless device can monitor the search space monitoring occasion based on the first coreset. When 1 is indicated for the second OFDM symbol, the wireless device can monitor the second search space monitoring occasion based on the second coreset.

[0271] In an example, the wireless device can receive one or more RRC messages including configuration parameters. The configuration parameters can indicate / include a coreset of a cell bandwidth part. The configuration parameters can include parameters of a search space associated with the coreset. The parameters of the search space can indicate a first monitoring periodicity in a first duration. For example, the first duration can be one slot or several slots. The parameters of the search space can indicate a second monitoring periodicity in a second duration. For example, the second duration can be one OFDM symbol or several OFDM symbols or one slot. For example, the second duration can be less than the first duration. The wireless device can monitor one or more repeated DCIs / PDCCHs via one or more monitoring occasions (e.g., multiple downlink control signal / channel transmission occasions) determined within the first monitoring periodicity based on the second monitoring periodicity. For example, the configuration parameters can indicate the one or more monitoring occasions within the first monitoring periodicity.

[0272] For example, a wireless device can receive / monitor a first DCI / PDCCH of one or more repeated DCI / PDCCH via a first monitoring occasion of the one or more monitoring occasions. The wireless device can receive / monitor a second DCI / PDCCH of the one or more repeated DCI / PDCCH via a second monitoring occasion of the one or more monitoring occasions. The first DCI / PDCCH can be the same as the second DCI / PDCCH. The first DCI / PDCCH and the second DCI / PDCCH can indicate a same resource of a transport block. The wireless device can receive / monitor the DCI via the one or more monitoring occasions, where a search space candidate of the DCI can include one or more candidates of the one or more monitoring occasions. For example, the search space candidate can include a first candidate of the first monitoring occasion and a second candidate of the second monitoring occasion. For example, a first starting CCE index of the first candidate of the first monitoring occasion can be the same as a second starting CCE index of the second candidate of the second monitoring occasion.

[0273] The wireless device can receive / monitor the DCI / PDCCH via the one or more monitoring occasions, where a search space candidate of the DCI / PDCCH can include one or more CCEs from the one or more monitoring occasions.

[0274] For example, a core set can be associated with a plurality of TCI states as active TCI states. For example, the plurality of TCI states can be activated via one or more RRC messages or MAC CEs or DCIs. The wireless device can monitor a first monitoring occasion based on a first TCI of the plurality of TCI states. The wireless device can monitor a second monitoring occasion based on a second TCI of the plurality of TCI states.

[0275] FIG. 23 An example of control channel repetition is shown in accordance with an aspect of the embodiments of the present disclosure. For example, a base station can transmit one or more RRC messages including configuration parameters. The configuration parameters can include / indicate a core set associated with active TCI states. The base station can activate the active TCI states via one or more RRC messages or one or more MAC CEs or one or more DCIs. The configuration parameters can include / indicate a bitmap indicating one or more monitoring occasions of control channel repetition. FIG. 24 A bitmap size of 14 is shown (e.g., the bitmap corresponds to a slot of every OFDM symbol mapped to every bit). The bitmap indicates monitoring occasions of a 1st OFDM symbol and a 6th OFDM symbol of a slot. The configuration parameters can indicate / include a first monitoring periodicity of two slots (e.g., monitor every two slots). In each monitoring periodicity, the wireless device can determine one or more monitoring occasions based on the bitmap. For example, when the bitmap is not present, the wireless device can determine a monitoring occasion starting from the first OFDM symbol of the slot. In each monitoring occasion, the wireless device can monitor the control channel.FIG. 25 In an example, the wireless device can determine the first monitoring occasion and the second monitoring occasion based on the bitmap in each monitoring period. The wireless device can monitor the first monitoring occasion and the second monitoring occasion for receiving one or more DCI / PDCCH scheduling a transport block.

[0276] In an example, for a search space, a configuration parameter indicates one or more monitoring occasions within a monitoring period. For example, monitoringSlotPeriodicityAndOffset can determine the monitoring period. When the parameter can include monitoringSymbolsWithinSlot, the wireless device can determine the monitoring period based on a gap between each monitoring occasion within a slot based on monitoringSymbolsWithinSlot. The wireless device can expect the gap between monitoring occasions within a slot to be equal. Alternatively, when the search space is for control channel repetition, the parameter can not include monitoringSymbolsWithinSlot. In an example, when control channel repetition is enabled, monitoringSymbolsWithinSlot can be used to indicate one or more monitoring occasions within a monitoring period determined based on monitoringSlotPeriodicityAndOffset. For example, a parameter to indicate the enablement of control channel repetition can be configured for a search space or for a coreset associated with the search space or a DCI format monitored via the search space. For example, a duration of the search space can be used to determine one or more monitoring occasions within a monitoring period. For example, when the monitoring period is greater than a slot, the wireless device can determine one or more monitoring occasions based on the monitoring period and the duration. For example, when the monitoring period is P slots and the duration is D, the wireless device can determine a first monitoring occasion of the one or more monitoring occasions based on monitoringSlotPeriodicityAndOffset. The wireless device can determine a second monitoring occasion of the one or more monitoring occasions as the next slot of the first monitoring occasion. The wireless device can determine monitoring occasions of the number D starting from the first monitoring occasion in consecutive slots. For example, when the search space is configured with / associated with multiple coresets, the search space can include multiple control resource set Ids (e.g., controlResourceSetID and a second controlResourceSetID).

[0277] In an example, a base station can transmit a first DCI / PDCCH via a first monitoring occasion of one or more monitoring occasions. The base station can transmit a second DCI / PDCCH via a second monitoring occasion of the one or more monitoring occasions. The first DCI / PDCCH and the second DCI / PDCCH can indicate a same resource of a transport block. A first content of the first DCI / PDCCH can be same or different from a second content of the second DCI / PDCCH. A wireless device can attempt to decode the first DCI / PDCCH independent of the second DCI / PDCCH. The wireless device can not assume that the base station can transmit the first DCI / PDCCH and the second DCI / PDCCH. The base station can transmit one or more DCI / PDCCHs within the one or more monitoring occasions. The base station can transmit a single DCI / PDCCH within the one or more monitoring occasions. The base station can transmit a DCI / PDCCH within each monitoring occasion. The base station can transmit any number of repeated DCI / PDCCHs within the one or more monitoring occasions.

[0278] A base station can indicate a first control channel repetition pattern for one or more monitoring occasions. Based on the first control channel repetition pattern, a wireless device can determine a number of one or more monitoring occasions O in a monitoring period. Monitoring occasions in the one or more monitoring occasions are indexed from 0, …, O-1 based on a time-first manner. The wireless device can attempt to decode one or more search space candidates that aggregate candidates from monitoring occasions from 0 to i (e.g., i = 0, …, O-1 or i = 0, 1, 3, 7, …). For example, when O is 4, the wireless device can attempt to decode a first candidate that aggregates candidates from a first monitoring occasion of the one or more monitoring occasions. The wireless device can attempt to decode a second candidate that aggregates a candidate from a second monitoring occasion of the one or more monitoring occasions and another candidate. The wireless device can attempt to decode a fourth candidate that aggregates each candidate of each monitoring occasion of the one or more monitoring occasions. The wireless device can aggregate candidates from the one or more monitoring occasions where a starting CCE index of candidates of the candidates is same, or the wireless device can determine the candidates based on a rule. For example, the wireless device can determine a candidate of a same frequency resource at each monitoring occasion. For example, the wireless device can determine a candidate of a same REG (or a same REG index) at each monitoring occasion.

[0279] In an example, a wireless device can determine each candidate list via each of the one or more monitoring occasions within a monitoring period of a search space. The wireless device can determine a candidate list over the one or more monitoring occasions based on each candidate list. The candidate list can include one or more candidates of an aggregation level. For example, the wireless device can determine a first candidate list of a first aggregation level 2*L based on two candidates within two monitoring occasions of an aggregation level L or four candidates within four monitoring occasions of an aggregation level L / 2.

[0280] In an example of determining one or more search space candidates of an aggregation level spanning one or more monitoring occasions, a base station can indicate four monitoring occasions in a monitoring period from a first to a fourth monitoring occasion index. In this example, assume a set of candidates of an aggregation level is consistent across the four monitoring occasions. For example, a first candidate of an aggregation level 2 can start in a third CCE and a second candidate of an aggregation level 2 can start in a fifth CCE. For example, a first candidate of an aggregation level 4 can start in N CCE (e.g., number of CCEs) - 8th CCE and a second candidate of an aggregation level 4 can start in N CCE - 4th CCE. The wireless device can determine a candidate list with an aggregation level 8 by combining / aggregating the four candidates of an aggregation level 2 (each candidate from one monitoring occasion) and / or by combining / aggregating the two candidates of an aggregation level 4 (each candidate from one monitoring occasion). In this example, the first block on the left and the second small block on the right illustrate AL = 8 candidates. The wireless device can determine multiple candidates by aggregating / combining the second candidate of AL = 2 and / or the second candidate of AL = 4. Similarly, the wireless device can determine a candidate of an aggregation level (AL) = 16 by combining / aggregating the four candidates of AL = 4. The wireless device can determine two AL = 16.

[0281] The wireless device can not aggregate candidates where the candidates can not include a candidate from a first monitoring occasion (or first monitoring occasion, earliest monitoring occasion in a monitoring period). The wireless device can determine possible aggregation levels and / or candidates by aggregating candidates from a first monitoring occasion, a first monitoring occasion + a second monitoring occasion, a first monitoring occasion + a second monitoring occasion + a third monitoring occasion + a fourth monitoring occasion, a first monitoring occasion + a second monitoring occasion + a third monitoring occasion + a fourth monitoring occasion + a fifth monitoring occasion - a sixth monitoring occasion + a seventh monitoring occasion + an eighth monitoring occasion, and so on.

[0282] In an example, a wireless device can determine a candidate list of an aggregation level based on a hash function applied in each slot. When a first monitoring occasion and a second monitoring occasion reside in a same slot, a same candidate can be mapped. Otherwise, different candidates can be determined. A base station can transmit a DCI on a candidate spanning one or more monitoring occasions.

[0283] In an example, a base station can transmit one or more messages including configuration parameters. The configuration parameters can include / indicate a search space group for controlling channel repetition. The search space group can include one or more search spaces. For example, the search group can include a first search space of a first carrier and a second search space of a second carrier. For example, the search space group can include a first search space of a first BWP of a cell and a second search space of a second BWP of the cell. For example, the search space group can include a first search space of a first BWP of a first cell and a second search space of a second BWP of a second cell. For example, the configuration parameters can indicate one or more search space groups for a BWP of a cell. A search space group of the one or more search space groups can be associated / configured with one or more DCI formats. In an example, a wireless device can determine a search space group based on one or more search spaces configured / associated with a BWP of a cell, where each search space of the one or more search spaces can be configured to monitor a DCI format of the one or more DCI formats. For example, the one or more DCI formats can include DCI format 1 1 and DCI format 0 1. For example, the one or more DCI formats can include DCI format 0 0 and DCI format 1 0. For example, the one or more DCI formats can include DCI format 1 2 and DCI format 0 2. For example, the one or more DCI formats can include DCI format 3 0 and DCI format 3 1. For example, the one or more DCI formats can include downlink / uplink DCI of non-fallback DCI. For example, the one or more DCI formats can include downlink / uplink DCI of fallback DCI. For example, the one or more DCI formats can include DCI formats of sidelink DCI.

[0284] A wireless device can determine search space candidates on one or more search spaces of a search space group in a similar manner addressed for control repetition based on the plurality of coreset sets. In an example, a wireless device can determine one or more monitoring occasions in a slot based on one or more search spaces. For example, in slot n, a wireless device can determine one or more first monitoring occasions based on a first search space of the one or more search spaces. A wireless device can determine one or more second monitoring occasions in slot n based on a second search space of the one or more search spaces. A wireless device can monitor the one or more first monitoring occasions and the one or more second monitoring occasions in slot n. A wireless device can not expect to have an overlap in time domain between a monitoring occasion of a search space of the one or more search spaces and a second monitoring occasion of a second search space of the one or more search spaces. A wireless device can monitor one or more repeated DCIs based on a DCI format via the one or more monitoring occasions in a slot.

[0285] In an example, a base station can transmit one or more repeated DCIs via one or more PDCCHs, where each PDCCH can carry / transmit each DCI. Each DCI of the one or more repeated DCIs can have a same content or different content. When each DCI can have a same content, a wireless device can aggregate the one or more repeated DCIs. In an example, the one or more repeated DCIs can be transmitted via a PDCCH, where the PDCCH can be transmitted on one or more search space candidates of one or more search spaces. In an example, a DCI can be repeatedly transmitted via one or more PDCCHs, where each PDCCH can repeatedly carry / transmit the DCI.

[0286] In an example, a base station can associate a plurality of TCI states with a coreset set as an active TCI state. FIG. 24An example of a core set associated with multiple TCI states as active TCI states is shown in accordance with aspects of the embodiments of this disclosure. In this example, a base station can indicate multiple monitoring occasions in a monitoring period of a slot or control channel repetition. A wireless device can monitor a first monitoring occasion based on a first TCI state of the multiple TCI states. The wireless device can monitor a second monitoring occasion based on a second TCI state of the multiple TCI states. The base station can indicate a pattern of switching between the multiple TCI states. For example, a configuration parameter of a search space associated with the core set can include / indicate that control channel repetition is enabled. The configuration parameter can include / indicate that TCI switching is enabled or that control channel repetition via multiple TCI states is enabled. The configuration parameter can include / indicate a switching pattern. For example, within a monitoring period or one slot or a few slots (e.g., between monitoring periods configured by the monitoringSlotPeriodicityAndOffset parameter of the search space), in each of the one or more monitoring occasions, the switching pattern can be an alternation between a first TCI state of the multiple TCI states and a second TCI state of the multiple TCI states. For example, the switching pattern can be a one-half one-half between the first TCI state and the second TCI state. For example, the number of the one or more monitoring occasions is K. The wireless device can monitor a first tier (K / 2) of monitoring occasions based on the first TCI state. The wireless device can monitor the remaining monitoring occasions within the monitoring period based on the second TCI state. For example, the switching pattern can be a bitmap to indicate a TCI state in each of the one or more monitoring occasions.

[0287] FIG. 25An example of a MAC CE format (e.g., TCI state indication for UE-specific PDCCH MAC CE, enhanced TCI state indication for UE-specific PDCCH MAC CE) indicating / activating / updating / selecting one or more TCI states (e.g., TCI state 1 and TCI state 2) of a coreset of a serving cell is shown. A base station can indicate one or more TCI state indices (e.g., TCI state ID 1 and TCI state ID 2) in the MAC CE format to activate one or more TCI states of a coreset (indicated by a coreset ID). The one or more TCI state indices can indicate / identify the one or more TCI states. Each TCI state index of the one or more TCI state indices can indicate / identify a respective TCI state of the one or more TCI states. The MAC CE format can include one or more fields. A first field of the one or more fields can indicate / include a serving cell index (e.g., a serving cell ID provided by a higher layer parameter ServCellIndex or indicated by one or more configuration parameters) that belongs / identifies / indicates a serving cell. A second field of the one or more fields can indicate / include a coreset index (e.g., a coreset ID) that belongs / identifies / indicates a coreset of the serving cell. A third field of the one or more fields can indicate / include a first TCI state index (e.g., TCI state ID 1) that belongs / identifies / indicates a first TCI state. The one or more TCI states can include the first TCI state. A fourth field (e.g., R) of the one or more fields can be a reserved field. A fifth field of the one or more fields can indicate / include a second TCI state index (e.g., TCI state ID 2) that belongs / identifies / indicates a second TCI state. In an example, the one or more fields of the MAC CE format can include the second TCI state index based on a value of the fourth field (e.g., R). For example, when the value of the fourth field is equal to zero, the MAC CE format can not include the second TCI state index (e.g., the fifth field can be a reserved field). When the value of the fourth field is equal to one, the MAC CE format can include the second TCI state index. The one or more TCI states can include the second TCI state. The MAC CE format can be an activation command. The configuration parameters can indicate the first TCI state index of the first TCI state. The configuration parameters can indicate the second TCI state index of the second TCI state. The configuration parameters can indicate the coreset index of the coreset. The configuration parameters can indicate the serving cell index of the serving cell. The configuration parameters can indicate the one or more TCI state indices of the one or more TCI states. The one or more TCI states can include the first TCI state and the second TCI state.The one or more TCI state indexes can include a first TCI state index and a second TCI state index.

[0288] FIG. 24 And FIG. 25 are examples of downlink signal reception with control channel repetition in accordance with aspects of the present disclosure.

[0289] In an example, the wireless device can receive one or more messages. In an example, the wireless device can receive the one or more messages from a base station. The one or more messages can include one or more configuration parameters. In an example, the one or more configuration parameters can be RRC configuration parameters. In an example, the one or more configuration parameters can be RRC reconfiguration parameters.

[0290] In an example, the one or more configuration parameters can be for a cell. In an example, at least one of the one or more configuration parameters can be for a cell. In an example, the cell can be a primary cell (PCell). In an example, the cell can be a secondary cell (SCell). The cell can be a PUCCH-configured secondary cell (e.g., PUCCH SCell). In an example, the cell can be an unlicensed cell operating, for example, in an unlicensed band. In an example, the cell can be a licensed cell operating, for example, in a licensed band. In an example, the cell can operate in a first frequency range (FR1). For example, FR1 can include frequency bands below 6 GHz. In an example, the cell can operate in a second frequency range (FR2). For example, FR2 can include frequency bands from 24 GHz to 52.6 GHz.

[0291] In an example, the wireless device can perform uplink transmission (e.g., PUSCH, PUCCH, SRS) via the cell at a first time and at a first frequency. The wireless device can perform downlink reception (e.g., PDCCH, PDSCH) via the cell at a second time and at a second frequency. In an example, the cell can operate in a time division duplex (TDD) mode. In the TDD mode, the first frequency and the second frequency can be the same. In the TDD mode, the first time and the second time can be different. In an example, the cell can operate in a frequency division duplex (FDD) mode. In the FDD mode, the first frequency and the second frequency can be different. In the FDD mode, the first time and the second time can be the same.

[0292] In an example, the wireless device can be in an RRC connected mode.

[0293] In an example, the wireless device can be in an RRC idle mode.

[0294] In an example, the wireless device can be in an RRC inactive mode.

[0295] In an example, a cell can comprise a plurality of BWPs. The plurality of BWPs can comprise one or more uplink BWPs comprising uplink BWPs of the cell. The plurality of BWPs can comprise one or more downlink BWPs comprising downlink BWPs of the cell.

[0296] In an example, a BWP of the plurality of BWPs can be in one of an active state and an inactive state. In an example, in the active state of a downlink BWP of the one or more downlink BWPs, the wireless device can monitor a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWP. In an example, in the active state of a downlink BWP of the one or more downlink BWPs, the wireless device can receive a PDSCH on / via / for the downlink BWP. In an example, in the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device can not monitor a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / via / for the downlink BWP. In the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device can stop monitoring (or receiving) a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / via / for the downlink BWP. In an example, in the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device can not receive a PDSCH on / via / for the downlink BWP. In the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device can stop receiving a PDSCH on / via / for the downlink BWP.

[0297] In an example, in the active state of an uplink BWP of the one or more uplink BWPs, the wireless device can transmit an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) on / via the uplink BWP. In an example, in the inactive state of an uplink BWP of the one or more uplink BWPs, the wireless device can not transmit an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) on / via the uplink BWP.

[0298] In an example, the wireless device can activate a downlink BWP of the one or more downlink BWPs of the cell. In an example, activating the downlink BWP can comprise the wireless device setting (or switching) the downlink BWP to an active downlink BWP of the cell. In an example, activating the downlink BWP can comprise the wireless device setting the downlink BWP to be in an active state. In an example, activating the downlink BWP can comprise switching the downlink BWP from an inactive state to an active state.

[0299] In an example, the wireless device can activate an uplink BWP of the one or more uplink BWPs of the cell. In an example, activating the uplink BWP can comprise the wireless device setting (or switching) the uplink BWP to an active uplink BWP of the cell. In an example, activating the uplink BWP can comprise the wireless device setting the uplink BWP to be in an active state. In an example, activating the uplink BWP can comprise switching the uplink BWP from an inactive state to an active state.

[0300] In an example, the one or more configuration parameters can be for the (active) downlink BWP of the cell. In an example, at least one of the one or more configuration parameters can be for a downlink BWP of the cell.

[0301] In an example, the one or more configuration parameters can be for the (active) uplink BWP of the cell. In an example, at least one of the one or more configuration parameters can be for a uplink BWP of the cell.

[0302] In an example, the one or more configuration parameters can indicate a plurality of coreset(s) (e.g., coreset 1 and coreset 2 in FIG. 24 and FIG. 25 ). The one or more configuration parameters can indicate a plurality of coreset(s) for the (active) downlink BWP of the cell. In an example, the (active) downlink BWP of the cell can comprise a plurality of coreset(s).

[0303] In an example, the one or more configuration parameters can indicate a coreset index (e.g., provided by a higher layer parameter ControlResourceSetld) of the plurality of coreset(s). In an example, each coreset of the plurality of coreset(s) can be identified / indicated by a respective coreset index of a plurality of coreset index. In an example, a first coreset (e.g., coreset 1 in FIG. 23 and FIG. 24 ) of the plurality of coreset(s) can be identified by a first coreset index of a plurality of coreset index. A second coreset (e.g., coreset 2 in FIG. 25 and FIG. 24The first core set among the plurality of core sets can be identified by a first core set index among a plurality of core set indexes.

[0304] In an example, the core set index can be a core set identifier / indicator.

[0305] In an example, the one or more configuration parameters can indicate a plurality of search space sets (e.g., by a higher layer parameter SearchSpace) of a downlink BWP of the cell, for example. In an example, the one or more configuration parameters can indicate a plurality of search space sets (e.g., by a higher layer parameter SearchSpace) of the cell, for example.

[0306] In an example, the one or more configuration parameters can indicate search space set indexes / identifiers (e.g., provided by a higher layer parameter searchSpaceId) of the plurality of search space sets. In an example, each search space set among the plurality of search space sets can be identified by a respective search space set index among the search space set indexes. In an example, a first search space set among the plurality of search space sets can be identified by a first search space set index among the search space set indexes. In an example, a second search space set among the plurality of search space sets can be identified by a second search space set index among the search space set indexes.

[0307] In an example, the one or more configuration parameters can indicate PDCCH monitoring periodicities (e.g., monitoringSlotPeriodicityAndOffset) of the plurality of search space sets. The one or more configuration parameters can indicate a respective PDCCH monitoring periodicity among the PDCCH monitoring periodicities (e.g., monitoringSlotPeriodicityAndOffset) of each search space set among the plurality of search space sets. The one or more configuration parameters can indicate a first PDCCH monitoring periodicity (e.g., 2 slots) of a PDCCH monitoring periodicity of a first search space set among the plurality of search space sets. The one or more configuration parameters can indicate a second PDCCH monitoring periodicity (e.g., 10 slots) of a PDCCH monitoring periodicity of a second search space set among the plurality of search space sets.

[0308] In an example, a search space set of the plurality of search space sets can be associated with (or linked to) a core set of the plurality of core sets. In an example, one or more configuration parameters can indicate a core set (or a core set index of a core set) of a search space set (e.g., provided by a higher layer parameter controlResourceSetld in a higher layer parameter SearchSpace). In an example, the association (or linkage) can be one-to-one. The association being one-to-one can include that a search space set associated with (or linked to) a core set is not associated with (or linked to) a second core set different from the core set. The plurality of core sets can include the second core set.

[0309] In an example, based on a search space set being associated with (or linked to) a core set, the wireless device can monitor a PDCCH candidate (e.g., DCI, PDCCH, RS, GC-PDCCH, DMRS, etc.) of a downlink control signal / channel in a PDCCH monitoring occasion for the search space set associated with (or linked to) the core set. In an example, based on a search space set being associated with (or linked to) a core set, the wireless device can monitor a PDCCH candidate of a DCI in a PDCCH monitoring occasion for a search space set of the core set associated with (or linked to) the search space set. In an example, based on a search space set being associated with (or linked to) a core set, the wireless device can monitor a PDCCH for a DCI of a search space set of the core set associated with (or linked to) the search space set.

[0310] In an example, the one or more configuration parameters can indicate a plurality of coreset indexes for a plurality of search space sets (e.g., provided by a higher layer parameter controlResourceSetld in a higher layer parameter SearchSpace). In an example, each search space set of the plurality of search space sets can be associated with (or linked to) a respective coreset of the plurality of coresets identified by a respective coreset index of the plurality of coreset indexes. In an example, the one or more configuration parameters can indicate a first coreset index of a first coreset of a first search space set. The one or more configuration parameters can indicate the first coreset index of the first coreset in a first coreset index field of the first search space set (e.g., provided by a higher layer parameter controlResourceSetld in a higher layer parameter SearchSpace). Based on the one or more configuration parameters indicating the first coreset index of the first coreset of the first search space set, the first search space set can be associated with (or linked to) the first coreset. In an example, the one or more configuration parameters can indicate a first coreset index of a first coreset of a second search space set. The one or more configuration parameters can indicate the first coreset index of the first coreset in a second coreset index field of the second search space set (e.g., provided by a higher layer parameter controlResourceSetld in a higher layer parameter SearchSpace). Based on the one or more configuration parameters indicating the first coreset index of the first coreset of the second search space set, the second search space set can be associated with (or linked to) the first coreset. In an example, the one or more configuration parameters can indicate a second coreset index of a second coreset of the first search space set. Based on the one or more configuration parameters indicating the second coreset index of the second coreset of the first search space set, the first search space set can be associated with (or linked to) the second coreset. In an example, the one or more configuration parameters can indicate a second coreset index of a second coreset of the second search space set. Based on the one or more configuration parameters indicating the second coreset index of the second coreset of the second search space set, the second search space set can be associated with (or linked to) the second coreset.

[0311] In an example, one or more first search space sets of the plurality of search space sets can be associated with (or linked to) a first coreset. The one or more configuration parameters can indicate the first coreset (or a first coreset index of the first coreset) of the one or more first search space sets. For the first coreset, the one or more configuration parameters can indicate the one or more first search space sets. One or more second search space sets of the plurality of search space sets can be associated with (or linked to) a second coreset. The one or more configuration parameters can indicate the second coreset (or a second coreset index of the second coreset) of the one or more second search space sets. For the second coreset, the one or more configuration parameters can indicate the one or more second search space sets.

[0312] In an example, a wireless device can monitor a downlink control channel (e.g., a PDCCH, a PDCCH transmission / reception) in / via a plurality of coresets for a DCI based on at least two TCI states. The wireless device can monitor the downlink control channel in / via each coreset of the plurality of coresets for the DCI based on a respective TCI state of the at least two TCI states. For example, the wireless device can monitor the downlink control channel in a first coreset for the DCI based on a first TCI state (e.g., TCI state 1) of the at least two TCI states. The wireless device can monitor the downlink control channel in a second coreset for the DCI based on a second TCI state (e.g., TCI state 2) of the at least two TCI states.

[0313] For example, the wireless device can receive one or more activation commands (e.g., a MAC-CE in DCI 1_0, a TCI state indication for a UE-specific PDCCH MAC CE, an enhanced TCI state indication for a UE-specific PDCCH MAC CE) that indicate / select / activate / update at least two TCI states (e.g., TCI state 1 and TCI state 2) of the plurality of coresets. Each activation command of the one or more activation commands can indicate / select / activate / update a respective TCI state of the at least two TCI states for a respective coreset of the plurality of coresets. For example, a first activation command of the one or more activation commands can activate / select / indicate / update a first TCI state of a first coreset. A second activation command of the one or more activation commands can activate / select / indicate / update a second TCI state of a second coreset. FIG. 25

[0314] ​The wireless device can monitor, for the DCI, a downlink control channel (e.g., PDCCH, PDCCH transmission / reception) in / via the plurality of coresets based on the at least two TCI states in response to receiving one or more activation commands indicating / selecting / activating / updating the at least two TCI states of the plurality of coresets. The second TCI state indicates / selects / activates / updates the second coreset. The wireless device can monitor, for the DCI, a downlink control channel in / via the first coreset based on the first TCI state in response to receiving a first activation command indicating / selecting / activating / updating the first TCI state of the first coreset. The wireless device can monitor, for the DCI, a downlink control channel in / via the second coreset based on the second TCI state in response to receiving a second activation command indicating / selecting / activating / updating the second TCI state of the second coreset.

[0315] In an example, the one or more configuration parameters can indicate at least two TCI state indices (e.g., provided by a higher layer parameter TCI-StateId) for the at least two TCI states. In an example, each TCI state of the at least two TCI states can be identified / indicated by a respective TCI state index of the at least two TCI state indices. In an example, a first TCI state of the at least two TCI states can be identified by a first TCI state index of the at least two TCI state indices. A second TCI state of the at least two TCI states can be identified by a second TCI state index of the at least two TCI state indices.

[0316] The at least two TCI states can comprise / indicate / be at least two antenna port quasi co-location (QCL) assumptions / properties / structures. Each TCI state of the at least two TCI states can comprise / indicate / be a respective antenna port QCL assumption / property / structure of the at least two antenna port QCL assumptions / properties / structures. An antenna port QCL assumption / property / structure of a coreset of the plurality of coresets can indicate, for the coreset, at least one of a channel property, a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial receive filter. The at least two antenna port QCL assumptions / properties / structures can comprise the antenna port QCL assumption / property / structure. For example, a first TCI state of the at least two TCI states can comprise / indicate / be a first antenna port QCL assumption / property / structure of the at least two antenna port QCL assumptions / properties / structures for a first coreset. A second TCI state of the at least two TCI states can comprise / indicate / be a second antenna port QCL assumption / property / structure of the at least two antenna port QCL assumptions / properties / structures for a second coreset.

[0317] In an example, the at least two TCI states can indicate at least two reference signals (e.g., CSI-RS, SSB / PBCH block, SRS, DM-RS). Each of the at least two TCI states can indicate a respective reference signal of the at least two reference signals. For example, a first TCI state (e.g., TCI state 1) can indicate / include a first reference signal index (e.g., provided by the higher layer parameter referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-Resourceld) that identifies (or indicates or belongs to) a first reference signal of the at least two reference signals. One or more configuration parameters can indicate the first reference signal index of the first reference signal. A second TCI state (e.g., TCI state 2) can indicate / include a second reference signal index (e.g., provided by the higher layer parameter referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-Resourceld) that identifies (or indicates or belongs to) a second reference signal of the at least two reference signals. One or more configuration parameters can indicate the second reference signal index of the second reference signal.

[0318] In an example, the at least two TCI states can indicate at least two quasi co- location types for the at least two reference signals. Each of the at least two TCI states can indicate a respective quasi co-location type of the at least two quasi co-location types. For example, the at least two quasi co-location types can be QCL Type D. For example, a first TCI state (e.g., TCI state 1) can indicate / include a first quasi co-location type of the at least two quasi co-location types for a first reference signal. A second TCI state (e.g., TCI state 2) can indicate / include a second quasi co-location type of the at least two quasi co-location types for a second reference signal. For example, the first quasi co-location type can be QCL Type D. For example, the second quasi co-location type can be QCL Type D.

[0319] In an example, monitoring, for a DCI, a downlink control channel (or a PDCCH candidate) in a coreset based on a TCI state can include one or more DM-RS antenna ports of the downlink control channel in the coreset being quasi co-located with a reference signal indicated by the TCI state. The one or more DM-RS antenna ports of the downlink control channel in the coreset can be quasi co-located with the reference signal with respect to a quasi co-location type indicated by the TCI state. The downlink control channel can carry the DCI. The one or more DM-RS antenna ports of the downlink control channel in the coreset can be quasi co-located with the reference signal in one or more REGs / CCEs of the downlink control channel. A plurality of coresets can include the coreset. At least two TCI states can include the TCI state. For example, the coreset can be a first coreset and the TCI state can be a first TCI state. The coreset can be a second coreset and the TCI state can be a second TCI state. Monitoring, for the DCI, the downlink control channel in the coreset can include monitoring, for the DCI, one or more PDCCH candidates in one or more PDCCH monitoring occasions of / for one or more search space sets associated with the coreset. A plurality of search space sets can include the one or more search space sets. The wireless device can determine the one or more PDCCH monitoring occasions of the one or more search space sets based on one or more search space set configuration parameters (e.g., IESearchSpace) of one or more configuration parameters. The one or more search space set configuration parameters can indicate one or more PDCCH monitoring periodicities (e.g., monitoringSlotPeriodicityAndOffset) of the one or more search space sets. The one or more search space set configuration parameters can indicate a PDCCH monitoring symbol (e.g., monitoringSymbolsWithinSlot) of the one or more search space sets.

[0320] For example, monitoring, for a DCI, a downlink control channel in a first coreset based on a first TCI state can include one or more first DM-RS antenna ports of the downlink control channel in the first coreset being quasi co-located with a first reference signal indicated by the first TCI state. The one or more first DM-RS antenna ports of the downlink control channel in the first coreset can be quasi co-located with the first reference signal with respect to a first quasi co-location type indicated by the first TCI state. The wireless device can monitor, for the DCI, one or more PDCCH candidates in one or more first PDCCH monitoring occasions of / for one or more first search space sets associated with the first coreset.

[0321] For example, monitoring the downlink control channels in the second coreset based on the second TCI state for the DCI can include one or more second DM-RS antenna ports of the downlink control channels in the second coreset being quasi co-located with a second reference signal indicated by the second TCI state. The one or more second DM-RS antenna ports of the downlink control channels in the second coreset can be quasi co-located with the second reference signal with respect to a second quasi co-location type indicated by the second TCI state. The wireless device can monitor, for the DCI, one or more PDCCH candidates in one or more second PDCCH monitoring occasions of / for the one or more second search space sets associated with the second coreset.

[0322] In an example, the one or more first DM-RS antenna ports and the one or more second DM-RS antenna ports can be different.

[0323] In an example, the one or more first DM-RS antenna ports and the one or more second DM-RS antenna ports can be the same.

[0324] The one or more configuration parameters can indicate control channel repetition (e.g., PDCCH repetition / aggregation). The one or more configuration parameters can include a control channel repetition enabling parameter that enables (or activates or indicates) control channel repetition. The control channel repetition can include repetition of a downlink control signal / channel (e.g., PDCCH, DCI).

[0325] In an example, the one or more configuration parameters can indicate a repetition number of the control channel repetition.

[0326] In an example, the one or more configuration parameters can indicate a repetition number of the control channel repetition for a plurality of coresets. The one or more configuration parameters can indicate a repetition number of the control channel repetition for each coreset of the plurality of coresets. In an example, the one or more configuration parameters can indicate a repetition number of the control channel repetition for a plurality of search space sets of a plurality of coresets. The one or more configuration parameters can indicate a repetition number of the control channel repetition for a respective search space set of each coreset of the plurality of coresets. In an example, the one or more configuration parameters can indicate a repetition number of the control channel repetition for at least one search space set of a plurality of search space sets.

[0327] In an example, the one or more configuration parameters can indicate a plurality of coresets for the control channel repetition.

[0328] In an example, the wireless device can receive a DCI indicating a repetition number of the control channel repetition. The DCI can include a field (e.g., DCI subframe / slot repetition number field) indicating the repetition number.

[0329] In the example, the number of repetitions could be, for example, the number of repetitions of downlink control signals / channels (e.g., PDCCH, DCI). The base station can transmit multiple repetitions of downlink control signals / channels, such as DCI / PDCCH (e.g., ...). FIG. 24 and FIG. 25 (DCI 1 and DCI 2 in the original text). Wireless devices can monitor PDCCH candidates for multiple DCI / PDCCHs (or for repetitions of downlink control signals / channels). The number of multiple DCI / PDCCHs can be equal to the number of repetitions (e.g., in...). FIG. 24 and FIG. 25 In this context, the number of repetitions equals 2. Multiple DCI / PDCCHs may include a first downlink control signal / channel (e.g., FIG. 24 and FIG. 25 DCI 1) and second downlink control signals / channels (e.g., FIG. 24 and FIG. 24 DCI 2 in the middle.

[0330] In the example, the wireless device can consist of multiple TRPs (e.g., FIG. 24 and FIG. 24 This refers to services such as TRP 1 and TRP 2 (e.g., receiving from or transmitting to multiple TRPs). Each downlink control signal / channel of multiple DCI / PDCCHs can be transmitted by the corresponding TRP in the multiple TRPs. For example, in FIG. 24 and FIG. 25 In this context, the first TRP (e.g., TRP1) of a plurality of TRPs can transmit DCI 1, while the second TRP (e.g., TRP2) of a plurality of TRPs can transmit DCI 2.

[0331] In the example, each downlink control signal / channel of multiple DCI / PDCCHs can be identical (or can have the same content, such as the same DCI field, the same DCI size, the same payload, the same DCI field value, etc.). Each downlink control signal / channel of multiple DCI / PDCCHs can be the same as a downlink control signal / channel. Each downlink control signal / channel of multiple DCI / PDCCHs can be a repetition of the downlink control signal / channel. A base station can repeat downlink control signals / channels by transmitting multiple DCI / PDCCHs. For example, in... FIG. 24 In this context, DCI 1 and DCI 2 can be the same (or equal). The contents of DCI 1 and DCI 2 can be identical. The payloads of DCI 1 and DCI 2 can be identical. The DCI fields (or the values ​​of the DCI fields) of DCI 1 and DCI 2 can be identical.

[0332] In an example, the first and second downlink control signals / channels can be the same (e.g., same content, same DCI fields, same DCI size, same payload, same DCI field values, etc.). In an example, the first and second downlink control signals / channels can be the same as the downlink control signal / channel. The first downlink control signal / channel can be the downlink control signal / channel. The second downlink control signal / channel can be the downlink control signal / channel.

[0333] The base station can transmit, for the repetition of the downlink control signal / channel, the multiple DCIs / PDCCHs via multiple coresets (e.g., FIG. 25 The base station can transmit, for the repetition of the downlink control signal / channel, the multiple DCIs / PDCCHs via multiple coresets (e.g., FIG. 24 The base station can transmit, for the repetition of the downlink control signal / channel, the multiple DCIs / PDCCHs via multiple coresets (e.g.,

[0334] A wireless device can monitor, for multiple DCIs / PDCCHs, multiple coresets for repetition of downlink control signals / channels. The wireless device can monitor, for each downlink control signal / channel of the multiple DCIs / PDCCHs, a respective coreset of the multiple coresets. Monitoring, for multiple DCIs / PDCCHs, multiple coresets for repetition of downlink control signals / channels can include monitoring multiple coresets for downlink control signals / channels. Monitoring, for multiple DCIs / PDCCHs, multiple coresets for repetition of downlink control signals / channels can include monitoring multiple coresets for repetition of downlink control signals / channels. The wireless device can monitor, for multiple DCIs / PDCCHs, multiple search space sets associated with multiple coresets for repetition of downlink control signals / channels. For each downlink control signal / channel of the multiple DCIs / PDCCHs, the wireless device can monitor, for repetition of the downlink control signal / channel, a respective search space set of the multiple search space sets. For example, in FIG. 24 a wireless device can monitor, for a first downlink control signal / channel, a first coreset. The wireless device can monitor, for the first downlink control signal / channel, one or more first search space sets associated with the first coreset. The wireless device can monitor, for a second downlink control signal / channel, a second coreset. The wireless device can monitor, for the second downlink control signal / channel, one or more second search space sets associated with the second coreset.

[0335] In an example, a wireless device can determine multiple downlink control signal / channel transmissions / repetition occasions (e.g., PDCCH transmissions / repetition / monitoring occasions) of control channel repetition. The wireless device can determine multiple downlink control signal / channel transmissions / repetition occasions of repetition of downlink control signals / channels. A base station can transmit, via multiple coresets across multiple downlink control signal / channel transmissions / repetition occasions (e.g., FIG. 25 and FIG. 24The base station can transmit the downlink control signal / channel via the multiple coresets across / through / on the multiple downlink control signal / channel transmission / repetition occasions. The base station can transmit the downlink control signal / channel via each of the multiple coresets across / through / on a respective downlink control signal / channel transmission / repetition occasion of the multiple downlink control signal / channel transmission / repetition occasions. The base station can repeat transmission of the downlink control signal / channel across / through / on the multiple downlink control signal / channel transmission / repetition occasions. For example, in FIG. 25 and FIG. 24 The multiple downlink control signal / channel transmission / repetition occasions include a first downlink control signal / channel transmission / repetition occasion (e.g., PDCCH transmission / repetition occasion 1) and a second downlink control signal / channel transmission / repetition occasion (e.g., PDCCH transmission / repetition occasion 2). The base station can transmit a first downlink control signal / channel in the first downlink control signal / channel transmission / repetition occasion via a first cored set. The base station can transmit a second downlink control signal / channel in the second downlink control signal / channel transmission / repetition occasion via a second cored set.

[0336] A wireless device can monitor a plurality of coreset(s) across / over / for a plurality of downlink control signal / channel transmission / repetition occasions for a plurality of DCI / PDCCH. A wireless device can monitor a plurality of coreset(s) across / over / for a plurality of downlink control signal / channel transmission / repetition occasions for a downlink control signal / channel. A wireless device can monitor each coreset of a plurality of coreset(s) across / over / for a respective downlink control signal / channel transmission / repetition occasion of a plurality of downlink control signal / channel transmission / repetition occasions for a downlink control signal / channel. A wireless device can monitor a plurality of coreset(s) across / over / for a plurality of downlink control signal / channel transmission / repetition occasions for a repetition of a downlink control signal / channel. For example, in FIG. 24 a wireless device monitors a first coreset in a first downlink control signal / channel transmission / repetition occasion for a first downlink control signal / channel. A wireless device monitors a second coreset in a second downlink control signal / channel transmission / repetition occasion for a second downlink control signal / channel.

[0337] A wireless device can monitor a plurality of coreset across / through / on a plurality of downlink control signal / channel transmission / repetition occasions. The wireless device can monitor each coreset of a plurality of coreset across / through / on a respective downlink control signal / channel transmission / repetition occasion of a plurality of downlink control signal / channel transmission / repetition occasions. For example, the wireless device can monitor a first coreset for downlink control signals / channels across / through / on one or more first downlink control signal / channel transmission / repetition occasions of a plurality of downlink control signal / channel transmission / repetition occasions. The wireless device can monitor a second coreset for downlink control signals / channels across / through / on one or more second downlink control signal / channel transmission / repetition occasions of a plurality of downlink control signal / channel transmission / repetition occasions. The one or more first downlink control signal / channel transmission / repetition occasions can comprise a first downlink control signal / channel transmission / repetition occasion. The one or more second downlink control signal / channel transmission / repetition occasions can comprise a second downlink control signal / channel transmission / repetition occasion.

[0338] A wireless device can monitor a plurality of coreset(s) across / based on / over a plurality of downlink control signal / channel transmission / repetition occasion(s) based on at least two TCI states. The wireless device can monitor each coreset of the plurality of coreset(s) across / based on / over a respective downlink control signal / channel transmission / repetition occasion of the plurality of downlink control signal / channel transmission / repetition occasion(s) based on a respective TCI state of the at least two TCI states. For example, the wireless device can monitor a first coreset across / based on / over one or more first downlink control signal / channel transmission / repetition occasion(s) for a downlink control signal / channel based on a first TCI state of the at least two TCI states. The wireless device can monitor a second coreset across / based on / over one or more second downlink control signal / channel transmission / repetition occasion(s) for a downlink control signal / channel based on a second TCI state of the at least two TCI states.

[0339] A base station can transmit a downlink control signal / channel across / based on / over a respective downlink control signal / channel transmission / repetition occasion of a plurality of downlink control signal / channel transmission / repetition occasion(s) via each coreset of a plurality of coreset(s). For example, the base station can transmit a downlink control signal / channel across / based on / over one or more first downlink control signal / channel transmission / repetition occasion(s) via a first coreset. The base station can transmit a downlink control signal / channel across / based on / over one or more second downlink control signal / channel transmission / repetition occasion(s) via a second coreset.

[0340] The base station can transmit the downlink control signals / channels via the multiple cores across the multiple downlink control signal / channel transmission / repetition occasions based on the at least two TCI states. The base station can transmit the downlink control signals / channels via each core of the multiple cores across a respective downlink control signal / channel transmission / repetition occasion of the multiple downlink control signal / channel transmission / repetition occasions based on a respective TCI state of the at least two TCI states. For example, the base station can transmit the downlink control signals / channels via a first core across one or more first downlink control signal / channel transmission / repetition occasions based on a first TCI state of the at least two TCI states. The base station can transmit the downlink control signals / channels via a second core across one or more second downlink control signal / channel transmission / repetition occasions based on a second TCI state of the at least two TCI states.

[0341] In an example, the repetition of the downlink control signal / channel (or the transmission of multiple DCIs / PDCCHs) can occur, e.g., in / on time units (e.g., be TDMed). For example, the time units can be consecutive. For example, the time units can not be consecutive. The number of time units can be equal to the number of repetitions. For example, the time units can be slots. For example, the time units can be mini-slots. For example, the time units can be time symbols (e.g., OFDM symbols). For example, the time units can be subframes. For example, the time units can be monitoring occasions in time (e.g., PDCCH monitoring occasions). The number of multiple downlink control signal / channel transmission occasions can be equal to the number of repetitions. The multiple downlink control signal / channel transmission occasions can be in / on time units. For example, a first downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions can be in / on a first time unit of the time units. A second downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions can be in / on a second time unit of the time units, and so on.

[0342] In an example, the repetition of the downlink control signal / channel (or the transmission of multiple DCIs / PDCCHs) can occur, e.g., in / on frequency units (be FDMed). The number of frequency units can be equal to the number of repetitions. For example, the frequency units can be frequency bands. For example, the frequency units can be physical resource blocks (PRBs). For example, the frequency units can be resource element groups (REGs). For example, the frequency units can be REG bundles. The frequency units can be, e.g., control elements (CEs). For example, the frequency units can be BWPs. For example, the frequency units can be cells. The number of multiple downlink control signal / channel transmission occasions can be equal to the number of repetitions. The multiple downlink control signal / channel transmission occasions can be in / on frequency units. For example, a first downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions can be in / on a first frequency unit of the frequency units. A second downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions can be in / on a second frequency unit of the frequency units, and so on.

[0343] A base station can transmit multiple DCIs / PDCCHs across / in / within time units. A base station can transmit multiple DCIs / PDCCHs across / in / within frequency units. A base station can repeat transmission of a downlink control signal / channel across / in / within multiple uplink signal / channel transmission occasions. A base station can transmit a downlink control signal / channel with a repetition number. For example, in FIG. 24 and FIG. 24 The multiple downlink control signal / channel transmission occasions include a first downlink control signal / channel transmission occasion (first TX occasion) and a second downlink control signal / channel transmission occasion (second TX occasion). The first downlink control signal / channel transmission occasion can be in / occur in a first time unit (e.g., first slot, first symbol, first subframe, first PDCCH monitoring occasion) of the time units. The second downlink control signal / channel transmission occasion can be in / occur in a second time unit (e.g., second slot, second symbol, second subframe, second PDCCH monitoring occasion) of the time units. The first downlink control signal / channel transmission occasion can be in / occur in a first frequency unit (e.g., first PRB, first cell, first frequency, first BWP, first subband, first REG bundle, first CE) of the frequency units. The second downlink control signal / channel transmission occasion can be in / occur in a second frequency unit (e.g., second PRB, second cell, second frequency, second BWP, second subband, second REG bundle, second CE) of the frequency units.

[0344] In an example, the one or more configuration parameters can indicate a repetition scheme of the control channel repetition (e.g., by a higher layer parameter RepetitionSchemeConfig, FDM-scheme, TDM-scheme, SDM-scheme, CDM-scheme).

[0345] For example, the repetition scheme can be a time domain repetition scheme. For example, the repetition scheme can be a frequency domain repetition scheme. For example, the repetition scheme can be a spatial domain / code domain repetition scheme.

[0346] In an example, the wireless device can monitor, for the multiple DCIs / PDCCHs, the multiple downlink control signal / channel transmission occasions based on the one or more configuration parameters indicating the repetition scheme.

[0347] In an example, the repetition scheme can be a time-domain repetition scheme (e.g., a TDM scheme, intra-slot repetition, inter-slot repetition, TDMSchemeA, TDMSchemeB, etc.). In the time-domain repetition scheme, the multiple downlink control signal / channel transmission occasions (e.g., the first TX occasion and the second TX occasion) can not overlap in time. In the time-domain repetition scheme, the multiple downlink control signal / channel transmission occasions can or can not overlap in frequency. Each of the multiple downlink control signal / channel transmission occasions can have non-overlapping time-domain resource allocations with respect to other signal / channel transmission occasions of the multiple downlink control signal / channel transmission occasions. For example, a first downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions can not overlap in time with a second downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions. The first downlink control signal / channel transmission occasion and the second downlink control signal / channel transmission occasion can be different. For example, in the time-domain repetition scheme, the first downlink control signal / channel transmission occasion (the first TX occasion) and the second downlink control signal / channel transmission occasion (the second TX occasion) can not overlap in time. The multiple downlink control signal / channel transmission occasions can occur in different time units. For example, the first time unit and the second time unit can not overlap in time. The first time unit and the second time unit can be different.

[0348] In an example, the repetition scheme can be a frequency domain repetition scheme (e.g., FDM scheme, FDMSchemeA, FDMSchemeB, etc.). In the frequency domain repetition scheme, the multiple downlink control signal / channel transmission occasions can or can not overlap in time. In the frequency domain repetition scheme, the multiple downlink control signal / channel transmission occasions can not overlap in frequency. Each of the multiple downlink control signal / channel transmission occasions can have non-overlapping frequency domain resource allocations with respect to other signal / channel transmission occasions of the multiple downlink control signal / channel transmission occasions. For example, a first downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions can not overlap in frequency with a second downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions. The first downlink control signal / channel transmission occasion and the second downlink control signal / channel transmission occasion can be different. For example, in the frequency domain repetition scheme, the first downlink control signal / channel transmission occasion (first TX occasion) and the second downlink control signal / channel transmission occasion (second TX occasion) can not overlap in frequency. The first downlink control signal / channel transmission occasion (first TX occasion) and the second downlink control signal / channel transmission occasion (second TX occasion) can overlap in time. The multiple downlink control signal / channel transmission occasions can occur in different frequency units (e.g., frequencies, REGs, CEs, PRBs, frequency bands, bandwidth parts, cells). For example, a first frequency unit of the first downlink control signal / channel transmission occasion and a second frequency unit of the second downlink control signal / channel transmission occasion can not overlap in frequency. The first frequency unit and the second frequency unit can be different.

[0349] In an example, the repetition scheme can be a spatial / code domain repetition scheme (e.g., SFN scheme, SDM scheme, CDM scheme, SDM Scheme, CDM Scheme, etc.). In a spatial / code domain repetition scheme, multiple downlink control signal / channel transmission occasions can overlap in time. In a spatial / code domain repetition scheme, multiple downlink control signal / channel transmission occasions can overlap in frequency. In a spatial / code domain repetition scheme, multiple downlink control signal / channel transmission occasions can be a single downlink control signal / channel transmission occasion. Each of the multiple downlink control signal / channel transmission occasions can have an overlapping frequency domain resource allocation with respect to other of the multiple downlink control signal / channel transmission occasions. Each of the multiple downlink control signal / channel transmission occasions can have a non-overlapping time domain resource allocation with respect to other of the multiple downlink control signal / channel transmission occasions. Each of the multiple downlink control signal / channel transmission occasions can be the same. For example, a first downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions can overlap in time and frequency with a second downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions. The first downlink control signal / channel transmission occasion and the second downlink control signal / channel transmission occasion can be the same. For example, in a spatial / code domain repetition scheme, a first downlink control signal / channel transmission occasion (first TX occasion) and a second downlink control signal / channel transmission occasion (second TX occasion) can overlap in frequency. The first downlink control signal / channel transmission occasion (first TX occasion) and the second downlink control signal / channel transmission occasion (second TX occasion) can overlap in time. The multiple downlink control signal / channel transmission occasions can occur in a same frequency unit (e.g., frequency, PRB, frequency band, bandwidth part, sub-band, cell, REG, REG bundle, CE). For example, a first frequency unit of the first downlink control signal / channel transmission occasion and a second frequency unit of the second downlink control signal / channel transmission occasion can overlap in frequency. The first frequency unit and the second frequency unit can be the same. The multiple downlink control signal / channel transmission occasions can occur in a same time unit (e.g., symbol, mini-slot, slot, subframe, PDCCH monitoring occasion, etc.). For example, a first time unit of the first downlink control signal / channel transmission occasion and a second time unit of the second downlink control signal / channel transmission occasion can overlap in time. The first time unit and the second time unit can be the same.

[0350] For example, in a time-domain repetition scheme, a downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions can have non-overlapping time-domain resource allocation with respect to another downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions. For example, in a frequency-domain repetition scheme, a downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions can have non-overlapping frequency-domain resource allocation with respect to another downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions. For example, in a spatial / code-domain repetition scheme, a downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions can have overlapping time-domain and frequency-domain resource allocation with respect to another downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions.

[0351] In an example, multiple DCIs / PDCCHs can be associated (or linked) with multiple downlink control signal / channel transmission occasions. Each downlink control signal / channel of the multiple DCIs / PDCCHs can be associated with a respective downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions. The base station can transmit each downlink control signal / channel of the multiple DCIs / PDCCHs in / via a respective downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions. The wireless device can monitor for each downlink control signal / channel of the multiple DCIs / PDCCHs in / via a respective downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions. For example, in FIG. 25 and FIG. 25 In an example, a first downlink control signal / channel (e.g., DCI 1) is associated with a first downlink control signal / channel transmission / repetition occasion (e.g., PDCCH transmission / repetition occasion 1), for example, based on the first downlink control signal / channel being transmitted by the base station or monitored by the wireless device in / via the first downlink control signal / channel transmission / repetition occasion. A second downlink control signal / channel (e.g., DCI 2) is associated with a second downlink control signal / channel transmission / repetition occasion (e.g., PDCCH transmission / repetition occasion 2), for example, based on the second downlink control signal / channel being transmitted by the base station or monitored by the wireless device in / via the second downlink control signal / channel transmission / repetition occasion.

[0352] The wireless device can receive / detect at least one downlink control signal / channel of the multiple DCIs / PDCCHs (or in the repetitions of the downlink control signals / channels). For example, in FIG. 25 , the wireless device detects / receives DCI 1. The wireless device does not receive / detect DCI 2. The at least one downlink control signal / channel is DCI 1. The wireless device receives DCI 1 in the first downlink control signal / channel transmission occasion. The wireless device does not receive / detect DCI 2 in the second downlink control signal / channel transmission occasion. The wireless device can receive / detect the downlink control signal / channel based on receiving / detecting the at least one downlink control signal / channel of the multiple DCIs / PDCCHs.

[0353] In an example, the at least one downlink control signal / channel can indicate the number of repetitions. The at least one downlink control signal / channel can include a DCI that indicates the number of repetitions.

[0354] In an example, the wireless device can receive the at least one downlink control signal / channel via at least one core set (e.g., core set 1 in FIG. 24 ) of the multiple core sets. The wireless device can receive each of the at least one downlink control signal / channel via a respective core set of the at least one core set. For example, in FIG. 24 , the at least one core set is the first core set (e.g., core set 1).

[0355] The at least one downlink control signal / channel can schedule / trigger a downlink signal (e.g., the downlink signal in FIG. 24 and FIG. 25 ). Each of the at least one downlink control signal / channel can schedule / trigger the downlink signal. The at least one downlink control signal / channel that schedules / trigger the downlink signal can include the downlink control signal / channel that schedules / trigger the downlink signal. For example, the downlink signal can be a transport block (e.g., PDSCH). For example, the downlink signal can be an aperiodic CSI-RS.

[0356] In an example, the wireless device can determine a plurality of time offsets between the plurality of downlink control signal / channel transmission occasions and the downlink signal (e.g., offset 1 and offset 2 in FIG. 24 ). The wireless device can determine each of the plurality of time offsets between a respective downlink control signal / channel transmission occasion of the plurality of downlink control signal / channel transmission occasions and the downlink signal. For example, in FIG. 25In an example, a first time offset (e.g., offset 1) of the plurality of time offsets can be between the first downlink control signal / channel transmission occasion and the downlink signal. A second time offset (e.g., offset 2) of the plurality of time offsets can be between the second downlink control signal / channel transmission occasion and the downlink signal.

[0357] The wireless device can determine a time offset between a reference downlink control signal / channel transmission occasion of the plurality of downlink control signal / channel transmission occasions and the downlink signal (e.g., offset in FIG. 24 The plurality of time offsets can include a time offset. When the reference downlink control signal / channel transmission occasion is the first downlink control signal / channel transmission occasion, the time offset is the first time offset. When the reference downlink control signal / channel transmission occasion is the second downlink control signal / channel transmission occasion, the time offset is the second time offset. The wireless device can determine the time offset of the reception of the downlink signal.

[0358] The wireless device can determine a reference downlink control signal / channel transmission occasion of the plurality of downlink control signal / channel transmission occasions. The wireless device can determine the reference downlink control signal / channel transmission occasion based on receiving / detecting at least one downlink control signal / channel, for example. The wireless device can determine the reference downlink control signal / channel transmission occasion based on receiving / detecting a downlink control signal / channel, for example. The wireless device can determine the reference downlink control signal / channel transmission occasion based on one or more configuration parameters indicating control channel repetition, for example.

[0359] The wireless device can receive / detect at least one downlink control signal / channel during / in / via at least one downlink control signal / channel transmission occasion of the plurality of downlink control signal / channel transmission occasions. The at least one downlink control signal / channel transmission occasion can or can not include the reference downlink control signal / channel transmission occasion. In an example, the at least one downlink control signal / channel transmission occasion is the first downlink control signal / channel transmission occasion. FIG. 24

[0360] In an example, determining a reference downlink control signal / channel transmission occasion of the plurality of downlink control signal / channel transmission occasions can include determining a reference downlink control signal / channel of the plurality of DCIs / PDCCHs based on the plurality of DCIs / PDCCHs being associated with the plurality of downlink control signal / channel transmission occasions, for example. For example, in FIG. 25 and FIG. 25 ​In examples, a reference downlink control signal / channel transmission occasion can be determined based on a starting downlink control signal / channel transmission occasion (or starting slot) and a number of repetitions. For example, one or more configuration parameters can indicate the starting downlink control signal / channel transmission occasion. At least one downlink control signal / channel, for example, can indicate the starting downlink control signal / channel transmission occasion. For example, in

[0361] In examples, a wireless device can determine a reference downlink control signal / channel transmission occasion based on a number of repetitions and a starting downlink control signal / channel transmission occasion (or starting slot) of a plurality of downlink control signal / channel transmission occasions. For example, one or more configuration parameters can indicate the starting downlink control signal / channel transmission occasion. At least one downlink control signal / channel, for example, can indicate the starting downlink control signal / channel transmission occasion. For example, in FIG. 25 and FIG. 24 In examples, a reference downlink control signal / channel transmission occasion can be determined based on a starting downlink control signal / channel transmission occasion (or starting slot) and a number of repetitions. For example, one or more configuration parameters can indicate the starting downlink control signal / channel transmission occasion. At least one downlink control signal / channel, for example, can indicate the starting downlink control signal / channel transmission occasion. For example, in

[0362] For example, in FIG. 24 In examples, a wireless device can determine a reference downlink control signal / channel transmission occasion based on a starting downlink control signal / channel transmission occasion (or starting slot) and a number of repetitions. For example, one or more configuration parameters can indicate the starting downlink control signal / channel transmission occasion. At least one downlink control signal / channel, for example, can indicate the starting downlink control signal / channel transmission occasion. For example, in

[0363] In examples, a reference downlink control signal / channel transmission occasion can be determined based on a starting downlink control signal / channel transmission occasion (or starting slot) and a number of repetitions. For example, one or more configuration parameters can indicate the starting downlink control signal / channel transmission occasion. At least one downlink control signal / channel, for example, can indicate the starting downlink control signal / channel transmission occasion. For example, in

[0364] The last reference downlink control signal / channel transmission occasion can have, for example, the latest start time of the start times of the multiple downlink control signal / channel transmission occasions. The second time unit can start later in time than the first time unit. The first / starting symbol of the second time unit can occur after (or later than) the first / starting symbol of the first time unit in time. The second downlink control signal / channel transmission occasion can be the reference downlink control signal / channel transmission occasion based on the second time unit that starts later in time than the first time unit.

[0365] The last reference downlink control signal / channel transmission occasion can have, for example, the latest end time of the end times of the multiple downlink control signal / channel transmission occasions. The second time unit can end later in time than the first time unit. The last symbol of the second time unit can occur after (or later than) the last symbol of the first time unit in time. The second downlink control signal / channel transmission occasion can be the reference downlink control signal / channel transmission occasion based on the second time unit that ends later in time than the first time unit.

[0366] The last reference downlink control signal / channel transmission occasion can be associated with a last downlink control signal / channel of the multiple DCIs / PDCCHs. The base station can transmit the last downlink control signal / channel in / via the last reference downlink control signal / channel transmission occasion. The wireless device can monitor for the last downlink control signal / channel in / via the last reference downlink control signal / channel transmission occasion. The last downlink control signal / channel can be the reference downlink control signal / channel. The base station can transmit a last repetition of the downlink control signal / channel in the last reference downlink control signal / channel transmission occasion. The wireless device can monitor for the last repetition of the downlink control signal / channel in the last reference downlink control signal / channel transmission occasion.

[0367] In an example, the reference downlink control signal / channel transmission occasion can be an earliest (or first or starting) downlink control signal / channel transmission occasion of the multiple downlink control signal / channel transmission occasions.

[0368] The earliest (or first or starting) reference downlink control signal / channel transmission occasion can have, for example, the earliest start time of the start times of the multiple downlink control signal / channel transmission occasions. For example, in FIG. 24 and FIG. 26In particular embodiments, a first time unit can start earlier in time than a second time unit. A first / starting symbol of the first time unit can occur earlier in time than (or before) a first / starting symbol of the second time unit. A first downlink control signal / channel transmission occasion can be a reference downlink control signal / channel transmission occasion based on the first time unit starting earlier than the second time unit.

[0369] A first (or earliest or starting) reference downlink control signal / channel transmission occasion can have an earliest ending time of ending times of a plurality of downlink control signal / channel transmission occasions. For example, a first time unit can end earlier in time than a second time unit. A last symbol of the first time unit can occur earlier in time than (or before) a last symbol of the second time unit. A first downlink control signal / channel transmission occasion can be a reference downlink control signal / channel transmission occasion based on the first time unit ending earlier than the second time unit.

[0370] A first (or earliest or starting) reference downlink control signal / channel transmission occasion can be associated with a first / starting downlink control signal / channel of a plurality of DCIs / PDCCHs. A base station can transmit a first downlink control signal / channel in / via the first reference downlink control signal / channel transmission occasion. A wireless device can monitor for the first downlink control signal / channel in / via the first reference downlink control signal / channel transmission occasion. The first downlink control signal / channel can be a reference downlink control signal / channel. A base station can transmit a first / starting repetition of a downlink control signal / channel in the first reference downlink control signal / channel transmission occasion. A wireless device can monitor for the first repetition of the downlink control signal / channel in the first reference downlink control signal / channel transmission occasion.

[0371] In an example, a reference downlink control signal / channel transmission occasion can be associated with a core set of a plurality of core sets. A wireless device can monitor for a downlink control signal / channel in the reference downlink control signal / channel transmission occasion for the core set. A wireless device can monitor for a DCI (or downlink control signal / channel) in the reference downlink control signal / channel transmission occasion for the core set. One or more configuration parameters can indicate the reference downlink control signal / channel transmission occasion for the core set. A wireless device can determine the reference downlink control signal / channel transmission occasion based on receiving the one or more configuration parameters.

[0372] In an example, a core set can be identified / indicated by a core set index of a plurality of core set indexes. In an example, the core set index can be a lowest (or a highest) of the plurality of core set indexes. The core set can be identified / indicated by the lowest (or the highest) core set index of the plurality of core set indexes.

[0373] A wireless device can determine / select a core set having a lowest (or a highest) core set index of a plurality of core set indexes of a plurality of core sets. The wireless device can monitor the core set in a downlink control signal / channel transmission occasion for a DCI. The downlink control signal / channel transmission occasion can be a reference downlink control signal / channel transmission occasion. The wireless device can determine the reference downlink control signal / channel transmission occasion based on the core set.

[0374] The reference downlink control signal / channel transmission occasion can be associated with a reference downlink control signal / channel of a plurality of DCIs / PDCCHs. A base station can transmit the reference downlink control signal / channel in / via the reference downlink control signal / channel transmission occasion. A wireless device can monitor in / via the reference downlink control signal / channel transmission occasion for the reference downlink control signal / channel. The wireless device can monitor the core set in the reference downlink control signal / channel transmission occasion for the reference downlink control signal / channel.

[0375] In an example, a wireless device can monitor a search space set of a plurality of search space sets in a reference downlink control signal / channel transmission occasion (e.g., a PDCCH monitoring occasion) for a downlink control signal / channel. The reference downlink control signal / channel transmission occasion can be associated with the search space set. The wireless device can monitor the search space set in the reference downlink control signal / channel transmission occasion for a DCI (or a downlink control signal / channel). One or more configuration parameters can indicate the reference downlink control signal / channel transmission occasion of the search space set. The wireless device can determine the reference downlink control signal / channel transmission occasi...

Claims

1. A method of communication, the method comprising: receiving, by a wireless device, one or more configuration parameters indicating a single frequency network (SFN) scheme; receiving, via at least one of multiple control resource sets (coresets) configured for physical downlink control channel (PDCCH) repetition, a repetition of downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH); and in response to each of: the one or more configuration parameters indicating the SFN scheme; the DCI not including a TCI field; and a time offset between the DCI and the PDSCH being equal to or greater than a threshold, receiving the PDSCH using transmission configuration indicator (TCI) states of the multiple coresets.

2. The method of claim 1, wherein the one or more configuration parameters further indicate the threshold.

3. The method of claim 1, wherein the time offset between the DCI and the PDSCH is a time offset between a reference transmission occasion of multiple transmission occasions for receiving the repetition of the DCI and the PDSCH.

4. The method of claim 3, wherein the reference transmission occasion ends later in time than each of the multiple transmission occasions.

5. The method of claim 1, wherein the threshold is a timeDurationForQCL.

6. A wireless device, the wireless device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform the method of claim 1.

7. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of claim 1.

8. A method of communication, the method comprising: transmitting, by a base station, one or more configuration parameters indicating a single frequency network (SFN) scheme; transmitting, via multiple control resource sets (coresets) configured for physical downlink control channel (PDCCH) repetition, a repetition of downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH); and in response to each of: the one or more configuration parameters indicating the SFN scheme; the DCI not including a TCI field; and a time offset between the DCI and the PDSCH being equal to or greater than a threshold, transmitting the PDSCH based on transmission configuration indicator (TCI) states of the multiple coresets.

9. The method of claim 8, wherein the one or more configuration parameters indicate the threshold.

10. The method of claim 8, wherein the time offset between the DCI and the PDSCH is a time offset between a reference transmission occasion of multiple transmission occasions for the repetition of the DCI and the PDSCH.

11. The method of claim 10, wherein the reference transmission occasion ends later in time than each of the plurality of transmission occasions.

12. The method of claim 8, wherein the threshold is a time duration for quasi co-location (timeDurationForQCL).

13. A base station, the base station comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the base station to perform the method of claim 8.

14. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of claim 8.

15. A communication system, the system comprising: a base station, the base station comprising one or more first processors and a first memory storing first instructions that, when executed by the one or more first processors, cause the base station to: transmit one or more configuration parameters indicating a single frequency network, SFN, scheme; transmit, via a plurality of control resource sets, coresets, configured for physical downlink control channel, PDCCH, repetition, repetitions of a downlink control information, DCI, scheduling a physical downlink shared channel, PDSCH; and in response to each of: the one or more configuration parameters indicating the SFN scheme; the DCI not including a transmission configuration indicator, TCI, field; and a time offset between the DCI and the PDSCH being equal to or greater than a threshold, transmit the PDSCH based on a TCI state of the plurality of coresets; and a wireless device, the wireless device comprising one or more second processors and a second memory storing second instructions that, when executed by the one or more second processors, cause the wireless device to: receive one or more configuration parameters indicating a single frequency network, SFN, scheme; receive, via at least one of a plurality of coresets, repetitions of a downlink control information, DCI, scheduling a physical downlink shared channel, PDSCH; and in response to each of: the one or more configuration parameters indicating the SFN scheme; the DCI not including the TCI field; and a time offset between the DCI and the PDSCH being equal to or greater than the threshold, receive the PDSCH using the TCI state.

Images