Reference opportunity determination in control channel repetition

Abstract

A wireless device may receive a repetition of downlink control information (DCI) that schedules a transport block via a first one of the monitoring occasions. The wireless device may receive the transport block based on a start symbol of a monitoring opportunity having a latest start time among start times of the monitoring opportunity.

Description

[0001] Divisional application

[0002] This application is a divisional application of the invention application filed on October 22, 2021, with application number 202180087144.3 and titled "Reference Timing Determination in Control Channel Repetition".

[0003] Cross-references to related applications

[0004] This application claims priority to U.S. Provisional Application No. 63 / 104,221, filed October 22, 2020, the entire contents of which are hereby incorporated by reference. Attached Figure Description

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0026] Figure 17 Exemplary configuration parameters for the control and / or data of aspects according to embodiments of this disclosure are shown.

[0027] Figure 18 Exemplary configuration parameters for the core set of aspects of an embodiment according to this disclosure are shown.

[0028] Figure 19 An example of PDCCH repetition in an embodiment according to this disclosure is shown.

[0029] Figure 20 An example of control channel repetition across multiple TRPs is shown in accordance with an embodiment of this disclosure.

[0030] Figure 21 An example of control channel repetition in an embodiment according to this disclosure is shown.

[0031] Figure 22 An example of a core set associated with multiple TCI states as active TCI states is shown, according to an embodiment of this disclosure.

[0032] Figure 23 An example of a MAC CE format for activating multiple TCI states of the core set according to one aspect of an embodiment of this disclosure is shown.

[0033] Figure 24 This is an example of control channel repetition according to one aspect of the embodiments of this disclosure.

[0034] Figure 25 This is an example of control channel repetition according to one aspect of the embodiments of this disclosure.

[0035] Figure 26 This is an example of control channel repetition according to one aspect of the embodiments of this disclosure. Detailed Implementation

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

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

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

[0039] In this disclosure, “a” (“a” and “an”) and similar phrases will be interpreted as “at least one” and “one or more”. Similarly, any term ending with the suffix “(s)” will be interpreted as “at least one” and “one or more”. In this disclosure, the term “may” is interpreted as “may, for example”. In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a number of suitable possibilities that may or may not be used in one or more embodiments of various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more components of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude the inclusion of unlisted components in the element being described. In contrast, “consisting of” provides a complete enumeration of the one or more components of the element being described. As used herein, the term “based on” should be interpreted as “at least partially based on” rather than, for example, “based on only”. As used herein, the term “and / or” indicates any possible combination of the enumerated elements. For example, "A, B and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0040] If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on” (or equivalently “at least based on”) indicates that the phrase following the term “based on” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “in response to” (or equivalently “at least in response to”) indicates that the phrase following the phrase “in response to” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “depends on” (or equivalently “at least depends on”) indicates that the phrase following the phrase “depends on” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “adopts / uses” (or equivalently “at least adopts / uses”) indicates that the phrase following the phrase “adopts / uses” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations.

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

[0042] In this disclosure, a parameter (or equivalently referred to as a field or information element: IE) may include one or more information objects, and an information object may include one or more other objects. For example, if parameter (IE)N includes parameter (IE)M, and parameter (IE)M includes parameter (IE)K, and parameter (IE)K includes parameter (information element)J, then, for example, N includes K, and N includes J. In one exemplary embodiment, when one or more messages include multiple parameters, it means that a parameter among the multiple parameters is present in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0043] Many of the proposed features are described as optional using the word "may" or parentheses. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the group of optional features. This disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways: having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0044] Many elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has defined interfaces to other elements. Modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or combinations thereof, all of which may be behaviorally equivalent. For example, a module can be implemented as software routines written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement modules using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are frequently programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure connections between limited internal hardware modules on a programmable device. The techniques mentioned are often combined to achieve the desired functional modules.

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

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

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

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

[0049] RAN 104 may include one or more base stations (not shown). The term "base station" may be used throughout this disclosure to mean and encompass: Node B (associated with UMTS and / or 3G standards); Evolved Node B (eNB, associated with E-UTRA and / or 4G standards); Remote Radio Header (RRH); Baseband Processing Unit coupled to one or more RRHs; Repeater Node or Relay Node for extending the coverage area of ​​the donor Node; Next Generation Evolved Node B (ng-eNB); Generation Node B (gNB, associated with NR and / or 5G standards); Access Point (AP, associated with, for example, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station may include at least one gNB Central Unit (gNB-CU) and at least one gNB Distributed Unit (gNB-DU).

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

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

[0052] RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna configurations and similar high-level transmission power. RAN 104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as coverage areas overlapping with the relatively large coverage areas provided by macrocell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hot spots") or in areas where macrocell coverage is weak. Examples of small cell base stations, in descending order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

[0054] Figure 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. Figure 1B As shown, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UE 156). This can be compared with... Figure 1A These components are implemented and operated in the same or similar ways as the corresponding components described.

[0055] 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).

[0056] like Figure 1B As shown, 5G-CN 152 includes Access and Mobility Management Functions (AMF) 158A and User Plane Functions (UPF) 158B. For ease of explanation, in Figure 1BThese are shown as a single component, AMF / UPF 158. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. Functions that UPF 158B can perform include: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification supporting the routing of service flows to the one or more DNs, user plane Quality of Service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink service authentication), downlink packet buffering, and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session point interconnected with the one or more DNs, and / or a pivot point supporting multihomed PDU sessions. UE 156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

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

[0058] 5G-CN 152 may include, for clarity, not listed here. Figure 1B One or more additional network functions are shown in the diagram. For example, 5G-CN 152 may include one or more of the following: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Openness Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

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

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

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

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

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

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

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

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

[0067] Figure 3 This illustrates an example of services provided between protocol layers in the NR user plane protocol stack. From Figure 2A and Figure 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.

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

[0069] although Figure 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or more generally to two cell groups: a primary cell group (MCG) and a secondary cell group (SCG). Split bearers are those that occur when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapping split radio bearers between RLC channels belonging to a cell group.

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

[0071] 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 via dynamic scheduling. Scheduling can be performed on 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 via logical channel priority ordering, and / or padding. MACs 212 and 222 may support one or more parameter sets and / or transmission timing. In the example, the mapping constraints in logical channel priority ordering can control which set of parameters and / or transmission timing the logical channel can use. For example... Figure 3 As shown, MAC 212 and 222 can provide logical channels as services to RLC 213 and 223.

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

[0073] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 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... Figure 4A The downlink data flow described in the text is similar.

[0074] Figure 4A The downlink data flow begins when SDAP 225 receives three IP packets from one or more QoS flows and maps those three packets to a radio bearer. Figure 4A In SDAP 225, IP packets n and n+1 are mapped to the first radio bearer 402, and IP packet m is mapped to the second radio bearer 404. The SDAP header (in...) Figure 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). Figure 4A As shown, the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and the PDU of SDAP 225.

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

[0076] Figure 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.

[0077] Figure 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, Figure 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., ...). Figure 4B(As shown in the diagram) and a MAC CE is inserted at the end of the uplink transmission of the MAC PDU. The MAC CE can be used for in-band control signaling. Exemplary MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for PDCP repeated detection, channel state information (CSI) reports, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC subheader with a format similar to that described with respect to the MAC SDU may precede the MAC CE, and the MAC CE may be identified by a reserved value in the LCID field indicating the type of control information included in the MAC CE.

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

[0079] Figure 5A and Figure 5B The mappings between logical channels, transport channels, and physical channels are shown for both downlink and uplink. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels carrying control and configuration information in the NR control plane, or as service channels carrying data in the NR user plane. Logical channels can be classified as dedicated logical channels for a specific UE, or as common logical channels that can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example:

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

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

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

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

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

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

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

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

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

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

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

[0091] The PHY can use physical channels to transfer information between processing levels of the PHY. A physical channel can be a set of associated time-frequency resources used to carry information from one or more transport channels. The PHY can generate control information to support lower-level PHY operations and provide this control information to lower levels of the PHY via physical control channels (referred to as L1 / L2 control channels). The set of physical channels and physical control channels defined by NR includes, for example:

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

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

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

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

[0096] - Physical Uplink Control Channel (PUCCH), which carries a UCI that may include HARQ acknowledgment, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and - Physical Random Access Channel (PRACH), which is used for random access.

[0097] Similar to the physical control channel, the physical layer generates physical signals to support low-level physical layer operations. For example... Figure 5A and Figure 5B As shown, the physical layer signals defined by NR include: Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Sounding Reference Signal (SRS), and Phase Tracking Reference Signal (PT-RS). These physical layer signals will be described in more detail below.

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

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

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

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

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

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

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

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

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

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

[0108] The base station that stores the RRC context for the UE, or the UE's last serving base station, can be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least during the period when the UE remains in the anchor base station's RAN notification area and / or during the period when the UE remains in RRC inactivity 606.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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, a process known as self-scheduling. A cell's DCI can be transmitted on another cell, a process known as cross-carrier scheduling. Uplink control information used for aggregation cells (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or RI) can be transmitted on the PCell's PUCCH. For a large number of aggregated downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0134] Figure 10B This illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. Figure 10BIn the example, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 in this example includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In the example, if Figure 10B If the aggregated cell depicted is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell will transmit UCIs associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by allocating UCI transmissions between PCell 1021 and PSCell 1061.

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

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

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

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

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

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

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

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

[0143] The UE may assume that one or more SS / PBCH blocks transmitted using the same SS / PBCH block index are quasi-co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH blocks transmitted with different SS / PBCH block indices.

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

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

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

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

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

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

[0150] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, downlink DMRS can be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS mode. Frontload DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE using the number (e.g., maximum number) of frontload DMRS symbols used for PDSCH. A DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, a DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, a DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. The radio network can (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, where DMRS locations, DMRS types, and / or scrambling sequences can be the same or different. The base station can use the same precoding matrix to transmit downlink DMRS and the corresponding PDSCH. The UE can use one or more downlink DMRS to perform consistent demodulation / channel estimation of the PDSCH.

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

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

[0153] Downlink PT-RS can be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS can depend on RRC configuration. The presence and / or type of downlink PT-RS can be configured UE-specifically using a combination of RRC signaling and / or associated with one or more parameters (e.g., modulation and coding scheme (MCS)) that can be indicated by DCI for other purposes. When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters including at least one MCS. NR networks can support multiple PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can employ the same precoding for both DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. Downlink PT-RS can be limited to the UE's scheduled time / frequency duration. Downlink PT-RS can be transmitted on symbols to facilitate phase tracking at the receiver.

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

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

[0156] Depending on the UE's RRC configuration, the uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not be present. The presence and / or type of the uplink PT-RS can be configured based on the UE through a combination of RRC signaling and / or one or more parameters indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least one MCS. The radio network can support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use the same precoding for both DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS can be limited to the UE's scheduled time / frequency duration.

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

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

[0159] An antenna port is defined such that a symbol on the antenna port, through the channel through which it is transmitted, can be inferred from another symbol on the same antenna port, through the same channel through which it is transmitted. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel used to transmit the second symbol on the antenna port (e.g., fade gain, multipath delay, etc.) from the channel used to transmit 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 allow the channel used to transmit the first symbol on the first antenna port to be inferred from the channel through which the second symbol on the second antenna port is transmitted. These one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[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 beamforming reference signals. The UE can perform downlink beam measurements and generate a beam measurement report based on downlink reference signals (e.g., Channel State Information Reference Signal (CSI-RS)). After setting up an RRC connection with the base station, the UE can perform the downlink beam measurement procedure.

[0161] Figure 11B An example of a Channel State Information Reference Signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11BThe square shown may represent a resource block (RB) within the cell's bandwidth. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters can be configured for CSI-RS resource configuration via higher-layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in radio frames), CSI-RS power parameters, CSI-RS sequence parameters, Code Division Multiplexing (CDM) type parameters, frequency density, transport comb, Quasi-Co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

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

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

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

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

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

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

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

[0170] Figure 13A A four-step contention-based random access procedure is shown. Before initiating this procedure, the base station may transmit configuration message 1310 to the UE. Figure 13AThe procedure shown includes the transmission of four messages: Msg 11311, Msg 21312, Msg 31313, and Msg 41314. Msg 11311 may include and / or be referred to as a preamble (or random access preamble). Msg 21312 may include and / or be referred to as a random access response (RAR).

[0171] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. These one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. These one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast these one or more RRC messages to one or more UEs. These one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). The UE may determine the time and frequency resources and / or uplink transmission power for transmitting Msg 11311 and / or Msg 31313 based on these one or more RACH parameters. Based on these one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg21312 and Msg 41314.

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

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

[0174] Msg 11311 may include one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). RRC messages can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The UE may determine the preamble group based on path loss measurements and / or the magnitude of Msg 31313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal with an RSRP higher than an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message, the UE can select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

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

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

[0177] The Msg 21312 received by the UE may include a RAR. In some scenarios, Msg 21312 may include multiple RARs corresponding to multiple UEs. Msg 21312 may be received after or in response to the transmission of Msg 11311. Msg 21312 may be scheduled on the DL-SCH and indicated on the PDCCH using a Random Access RNTI (RA-RNTI). Msg 21312 may indicate that Msg 11311 was received by the base station. Msg 21312 may include a time comparison command that the UE can use to adjust the UE's transmission timing, a scheduling grant for transmitting Msg 31313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg 21312. The UE may determine when to initiate the time window based on the PRACH timing used by the UE to transmit the preamble. For example, the UE may initiate a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH timing starting from the end of the preamble transmission). These one or more symbols may be determined based on a set of parameters. The PDCCH may be in a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI may be used depending on one or more events that initiate the random access procedure. The UE may use a Random Access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH timing in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: the OFDM symbol index; the time slot index; the frequency domain index; and / or the UL carrier indicator of the PRACH timing. An example of an RA-RNTI may be as follows:

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

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

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

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

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

[0183] Figure 13B This illustrates a two-step contention-free random access procedure. (Compared to...) Figure 13A Similar to the four-step contention-based random access procedure shown, the base station can transmit configuration message 1320 to the UE before the procedure is initiated. Configuration message 1320 may be similar to configuration message 1310 in some respects. Figure 13B The program shown involves the transmission of two messages: Msg 11321 and Msg 21322. Msg 11321 and Msg 21322 can be similar in some respects to... Figure 13A The Msg 11311 and Msg 21312 are shown. (As from...) Figure 13A and Figure 13B It will be understood that a contention-free random access procedure may not include messages such as Msg 31313 and / or Msg41314.

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

[0185] After transmitting the preamble, the UE can initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of the RAR. In the event of a beam failure recovery request, the base station can configure the UE with a separate time window and / or a separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE can monitor the PDCCH transmission of the Cell RNTI (C-RNTI) addressed to the search space. Figure 13B In the contention-free random access procedure shown, the UE can determine that the random access procedure was successfully completed after or in response to the transmission of Msg 11321 and the reception of the corresponding Msg 21322. 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.

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

[0187] MsgA 1331 can be transmitted by the UE in uplink transmission. MsgA 1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include... Figure 13A The content shown in Msg 3 1313 is similar to and / or equivalent to that of Msg 3 1313. Transport block 1342 may include UCIs (e.g., SR, HARQACK / NACK, etc.). The UE may receive Msg B 1332 after or in response to the transmission of MsgA 1331. Msg B 1332 may include content similar to and / or equivalent to MsgA 13313. Figure 13A and Figure 13B The Msg 2 1312 shown (e.g., RAR) and / or Figure 13A The content shown in Msg 4 1314 is similar to and / or equivalent to the content shown in Msg 4 1314.

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

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

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

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

[0192] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling authorization indicating uplink radio resources and / or transmission format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in the payload transmitted by the base station on the Physical Downlink Control Channel (PDCCH). The payload transmitted on the PDCCH may be referred to as Downlink Control Information (DCI). In some scenarios, the PDCCH may be a group-shared PDCCH (GC-PDCCH) common to the UE group.

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

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

[0195] 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.

[0196] 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).

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

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

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

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

[0201] The UE can transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. Uplink control signaling transmission may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may transmit the HARQ acknowledgment after receiving the DL-SCH transport block. Uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station can determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. Uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgment, CSI report, SR, etc.) via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The UE may use one of several PUCCH formats to transmit uplink control signaling via the PUCCH.

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

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

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

[0205] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of this disclosure is shown. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as... Figure 1A The mobile communication network 100 shown Figure 1B The mobile communication network 150 shown or any other communication network. Figure 15 The diagram shows only one wireless device 1502 and one base station 1504, but it should be understood that a mobile communication network may include more than one UE and / or more than one base station, which have the same characteristics as... Figure 15 The same or similar configurations shown.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0219] A timer can begin running once started and continues running until it stops or expires. If a timer is not running, it can be started, or if it is running, it can be restarted. A timer can be associated with a value (e.g., a timer can start or restart from a certain value, or it can start from zero and expire once it reaches that value). The duration of a timer may not be updated until the timer stops or expires (e.g., due to BWP switching). Timers can be used to measure time periods / windows of a process. When the specification refers to implementations and procedures related to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of these multiple ways of implementing a timer can be used to measure time periods / windows of a process. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In the example, instead of starting and expiring the random access response window timer, the time difference between two timestamps can be used. When the timer restarts, the measurement process for the time window can be restarted. Other exemplary implementations can be provided to restart the measurement of a time window.

[0220] Wireless devices can receive / detect DCI during PDCCH monitoring.

[0221] In the example, the DCI can schedule transport blocks (e.g., PDSCH). The wireless device can determine the symbol for the reception of a transport block based on the timing of the PDCCH monitoring received by the wireless device from the DCI. The wireless device can then receive the transport block starting from that symbol.

[0222] In the example, DCI can schedule transport blocks (e.g., PUSCH). The wireless device can determine the symbols for transport block transmission based on the timing of the PDCCH monitoring received by the wireless device from the DCI. The wireless device can transmit the transport block based on whether the first / start / earliest symbol of the transport block is later than, appears after, or is later than, or is after, that symbol. The wireless device can discard the transmission of the transport block based on whether the first / start / earliest symbol of the transport block is earlier than, appears before, or is earlier than, or is before, that symbol.

[0223] In the example, the wireless device can perform beam fault recovery of the cell based on the received DCI. The wireless device can determine / identify candidate reference signals for beam fault recovery. The wireless device can determine the symbol based on the PDCCH monitoring timing of the received DCI. The wireless device can transmit the cell's uplink signals (e.g., PUCCH) after the symbol based on the candidate reference signals. The wireless device can monitor the PDCCH of one or more core sets of the cell after the symbol based on the candidate reference signals.

[0224] In the example, the wireless device may receive configuration parameters from a base station, for example. These configuration parameters may indicate control channel repetition, whereby the base station transmits DCI repetition via one or more core sets. Repetition may be transmitted at multiple transmission / repetition times (e.g., PDCCH monitoring times or time slots). The wireless device may monitor one or more core sets at multiple transmission times for DCI repetition. Therefore, control channel repetition can increase control channel reliability and robustness.

[0225] In the prior art, the combined implementation of symbol determination and control channel repetition can lead to ambiguity / misalignment. In the example, the wireless device may receive the DCI via the first transmission / repetition timing out of multiple transmission / repetition timings.

[0226] DCI can schedule transport blocks (e.g., PDSCH, PUSCH). In prior art implementations, the wireless device can determine the first symbol for the transmission / reception of a transport block based on the first transmission / repetition timing of the DCI received by the wireless device. The wireless device can, for example, receive the transport block starting from the first symbol (e.g., PDSCH). For example, the wireless device can transmit the transport block based on the first / start symbol of the transport block appearing after / after the first symbol (e.g., PUSCH).

[0227] For example, a wireless device can perform beam fault recovery of a cell based on received DCI. The wireless device can transmit uplink signals (e.g., PUCCH) of the cell after the first symbol based on candidate reference signals identified for the beam fault recovery procedure. The wireless device can monitor PDCCHs in one or more core sets of the cell after the first symbol based on the candidate reference signals.

[0228] In the example, the base station may not have information about which transmission / repetition timing the wireless device successfully received the DCI among multiple transmission / repetition timings. In the example, the base station can determine the second symbol for the transmission / reception of a transport block based on a second transmission / repetition timing among multiple transmission / repetition timings. For example, the base station can determine the second symbol randomly / blindly (or based on unknown rules at the wireless device) based on the second transmission / repetition timing.

[0229] For example, a base station may transmit a transport block starting from the second symbol (e.g., PDSCH). For example, a base station may not receive (or monitor) a transport block based on the first / start symbol of the transport block appearing before / before the second symbol (e.g., PUSCH).

[0230] The base station can receive the cell's uplink signal (e.g., PUCCH) after the second symbol based on candidate reference signals identified for beam fault recovery procedures. The base station can transmit PDCCHs from one or more core sets of the cell after the second symbol based on the candidate reference signals.

[0231] The first symbol determined by the wireless device and the second symbol determined by the base station may differ. Misalignment / ambiguity on the symbol may lead to, for example, the loss of transmission block reception. Misalignment / ambiguity on the symbol may lead to, for example, the misaligned beam being used for uplink and downlink transmissions after beam failure recovery is complete. This may result in increased retransmissions, increased latency / delay for successful communication, and increased power consumption.

[0232] When the base station repeatedly schedules the transmission of a transport block's DCI across multiple transmission / repetition times, the exemplary implementation enhances / improves symbol determination. In the exemplary implementation, the wireless device and base station can determine a reference transmission / repetition time among the multiple transmission / repetition times based on predefined rules (e.g., the last / end / first / start transmission / repetition time among multiple transmission / repetition times). The wireless device and base station can determine symbols for the transmission / reception of the transport block based on the reference transmission / repetition time. The wireless device and base station can determine symbols for the transmission / reception of downlink / uplink signals after beam fault recovery is complete, based on the reference transmission / repetition time. This can reduce the likelihood of misalignment on symbols used for transmitting / receiving the transport block. This can reduce latency / delay for successful communication, reduce power consumption, and reduce retransmissions.

[0233] PDCCH can carry scheduling assignments and other control information in the form of DCI messages. The information carried by the PDCCH can be referred to as DCI. A base station can transmit multiple PDCCHs within a control area to a radio device. The radio device can monitor multiple PDCCHs. A PDCCH can include an aggregation of one or more Control Channel Elements (CCEs). Monitoring can include performing blind decoding on multiple candidate PDCCHs. Blind decoding can include performing Cyclic Redundancy Check (CRC) demasking on each of the multiple candidate PDCCHs using a Radio Network Temporary Identifier (RNTI). Blind decoding can be used to detect PDCCHs. If no CRC error is detected, the radio device can determine that the PDCCH carries its own control information.

[0234] Figure 17Exemplary configuration parameters for control and / or data are illustrated according to one aspect of an embodiment of this disclosure. A wireless device may receive one or more Radio Resource Control (RRC) messages including cell configuration parameters. The configuration parameters may include one or more parameters of the serving cell configuration (e.g., ServingCellConfig). The one or more parameters of the serving cell configuration may indicate one or more downlink bandwidth portions (e.g., a list of BWP downlinks). The one or more parameters of the serving cell configuration may indicate one or more uplink bandwidth portions (e.g., a list of BWP uplinks). Downlink bandwidth portions (e.g., BWP downlinks) and / or uplink bandwidth portions (e.g., BWP uplinks) may include bandwidth portion indices (e.g., bwp-Id), configuration parameters for cell common downlink bandwidth portions (e.g., BWP-DownlinkCommon), and / or UE-specific downlink bandwidth portions (e.g., BWP-DownlinkDedicated). For example, the bandwidth portion index (bwp-Id) may indicate a bandwidth portion configuration, where the index of the bandwidth portion is a bandwidth portion index. The bandwidth portion configuration may include location and bandwidth information (locationAndBandwidth). `locationAndBandwidth` can indicate the starting resource block (RB) and bandwidth of the bandwidth portion based on a reference point (e.g., point A of the carrier / cell in the bandwidth portion). The bandwidth portion configuration can include subcarrier spacing (e.g., subcarrier spacing) and a cyclic prefix (e.g., cyclic prefix). 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.

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

[0236] The configuration parameters of pdcch-Config can include at least one of the following: core set set, search space set, downlink preemption (e.g., downlinkPreemption), transmission power control (TPC) of PUSCH (e.g., tpc-PUSCH), TPC of PUCCH, and / or TPC of SRS. Configuration parameters can include a list of search space switching groups (e.g., searchesSpaceSwitchingGroup), search space switching timers (e.g., searchSpaceSwitchingTimer), uplink cancellation, and / or monitoring capability configuration (e.g., monitoringCapabilityConfig). The base station can configure the list of search space switching groups, where radio devices can switch from a first search space group to a second search space group based on search space switching timers or rules, indications, or events. The base station can configure up to K (e.g., K=3) core sets for the cell's BWP. Downlink preemption can indicate whether monitoring is performed in response to downlink preemption indications for the cell. Monitoring capability configuration can indicate whether monitoring capabilities for radio devices will be configured for the cell, where the capability is based on basic or advanced capabilities. The base station can configure up to M (e.g., M = 10) search spaces for the cell's BWP. TPC-PUCCH, TPC-PUSCH, or TPC-SRS can be enabled and / or configured to receive TPC commands for PUCCH, PUSCH, or SRS, respectively. Uplink cancellation can indicate uplink cancellation for the monitored cell.

[0237] The configuration parameters of pdcch-ConfigCommon may include control resource set zero (e.g., controlResourceSetZero), common control resource set zero (e.g., commonControlResourceSet), search space zero (e.g., searchSpaceZero), a list of common search spaces (e.g., commonSearchSpaceList), the search space for SIB1 (e.g., searchSpaceSIB1), the search space for other SIBs (e.g., searchSpaceOtherSystemInformation), the search space for paging (e.g., pagingSearchSpace), the search space for random access (e.g., ra-SearchSpace), and / or the first PDCCH monitoring timing. Control resource set zero may include parameters of a first core set with an index value of zero. Core set zero can be configured for the initial bandwidth portion of the cell. Radio devices may use control resource set zero in the cell's BWP, where the BWP is not the initial BWP of the cell based on one or more conditions. For example, the parameter set of the BWP may be the same as the parameter set of the initial BWP. For example, the BWP may include the initial BWP. For example, the BWP may include control resource set zero. A common control resource set can be an additional common core set available for the common search space (CSS) or the UE-specific search space (USS). The base station can configure the bandwidth of the common control resource set to be less than or equal to the bandwidth of control resource set zero. The base station can configure the common control resource set such that it is included 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 may exclude search spaces with index zero (e.g., SS#0). The first PDCCH monitoring timing can indicate the monitoring timing of paging timing. The base station can configure search spaces for monitoring DCIs used for paging (e.g., pagingSearchSpace), for RAR monitoring (e.g., ra-SearchSpace), for SIB1 (e.g., searchSpaceSIB1), and / or for other SIBs besides SIB1 (e.g., searchSpaceOtherSystemInformation). A search space with index zero (e.g., searchSpaceZero, SS#0) can be configured for the initial BWP of the cell. Similar to corset#0, SS#0 can be used in the BWP of the cell based on one or more conditions.

[0238] Figure 18Exemplary configuration parameters for a core set according to an embodiment of this disclosure are shown. The ControlResourceSet (core set) may include a core set index (e.g., ControlResourceSetId), frequency domain resources (e.g., frequencyDomainResources), the duration of the core set (e.g., the 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., interleaved vs. non-interleaved). When the CCE-REG mapping type is configured as interleaved, the base station may also configure the REG bundle size (e.g., reg-BundleSize) and interleaver size (e.g., interleaverSize). The core set may also include a precoder granularity (e.g., between same as REG bundle (e.g., sameAsREG-bundle) and spans all contiguous RBs (e.g., allContiguousRBs)). For example, when the precoder granularity is configured as "same as REG bundle," the radio device may assume that REGs spanning bundles use the same precoder. For example, when the precoder granularity is configured to "across all consecutive RBs", the wireless device can assume that the same precoder is used across consecutive RBs in the core set. The core set may include a list of TCI states where the core set is not core set #0. The core set may include parameters indicating the presence of a TCI in the DCI. If the core set is configured with a TCI present in the DCI, the wireless device can expect the DCI format, including the TCI indication based on the DCI format, to be scheduled via a search space associated with the core set. For example, the DCI format could be DCI format 1_1 and / or DCI format 0_1. The core set may optionally include one or more of the following: DMRS scrambling identity, core set pool index, enhanced core set index (e.g., ControlResourceSetId-v16xy), TCI present in the DCI of DCI format 1_2, and RB offset. For example, when an enhanced core set index is present in the core set configuration, the wireless device may ignore the core set index. The enhanced core set index can indicate values ​​between [0, ..., 15], while the core set index can indicate values ​​between [0, ..., 11].

[0239] A core set is associated with a search space, where wireless devices can determine search space candidates and / or the timing of search space monitoring based on the configuration of the search space and the core set. When a search space is associated with a core set or vice versa, the parameters of the search space may include the index of the core set.

[0240] The search space may include an index of the search space (e.g., searchSpaceId), an index of the associated core set (e.g., controlResourceSetId), monitoring periodicity, and offset (e.g., periodicity based on the number of time slots and offset based on the number of time slots, periodicity between [1, 2560] time slots, and offset between [0, ..., P-1], where P is periodicity). The search space may include a duration, where the wireless device can monitor the search space in consecutive time slots starting from the monitoring time based on the duration. The base station may not configure a duration for the search space of the scheduling DCI format 2_0. The maximum duration value may be periodicity -1 (e.g., repeating in each time slot within an interval / period). The search space may include monitoring symbols within a time slot (e.g., a bitmap of OFDM symbol sizes in a time slot (e.g., 12 for extended cyclic prefix (CP) and 14 for normal CP)). The search space may include a set of multiple candidates for each aggregation level (e.g., the first number of candidates for aggregation level L=1, the second number of candidates for aggregation level L=2, etc.). The search space may 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 formats 0_0 / 1_0, 2_0, 2_1, 2_2, and 2_3 can be configured. For a USS, the base station can configure a list of search space group indices (if configured). For a USS, the base station can configure frequency monitoring timing / location for broadband operations on unlicensed or licensed spectrum. In the specification, DCI format 0_0 / 1_0 can be used interchangeably with DCI format 0-0 / 1-0 or a fallback DCI format. DCI format 0_1 / 1_1 can be used interchangeably with DCI format 0-1 / 1-1 or a non-fallback DCI format. DCI format 0_2 / 1_2 can be used interchangeably with DCI format 0-2 / 1-2 or a non-fallback DCI format.

[0241] The configuration parameters of pdsch-Config can include parameters for receiving transport blocks. For example, configuration parameters can include the PDSCH data scrambling identity, DM-RS mapping type (e.g., between mapping type A and mapping type B), a list of Transport Configuration Indicator (TCI) states, parameters for the (virtual RB)VRB to (physical RB)PRB interleaver, resource allocation type (e.g., dynamic switching between resource allocation type 0, resource allocation type 1, or both), a list of time-domain allocations, aggregation factor, a list of rate matching modes, RBG (Resource Block Group) size, MCS table (e.g., between QAM 256 and QAM64 LowSE, between high MCS and low MCS), maximum codeword (e.g., between 1 and 2), parameters related to PRB bundles, maximum MIMO layer, 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 DCI format).

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

[0243] In the example, the Physical Downlink Control Channel (PDCCH) may include one or more Control Channel Elements (CCEs). For example, the PDCCH may include one CCE corresponding to Aggregation Level (AL) = 1. For example, the PDCCH may include two CCEs corresponding to AL = 2. For example, the PDCCH may include four CCEs corresponding to AL = 4. For example, the PDCCH may include eight CCEs corresponding to AL = 8. For example, the PDCCH may include sixteen CCEs corresponding to AL = 16.

[0244] In the example, a PDCCH can be carried on one or more control resource sets (core sets). A core set can include N_rb_coreset resource blocks (RBs) in the frequency domain and N_symbol_coreset symbols in the 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, during an OFDM symbol, a REG can include one RB. REGs in the core set can be sorted / numbered in ascending order in time priority, starting from 0 for the first OFDM symbol and the lowest numbered (e.g., lowest frequency) RB in the core set. The radio device can increment the number in the first OFDM symbol by incrementing the frequency position or RB index. In response to all RBs in the first symbol potentially being indexed, the radio device can move to the next symbol. The radio device can map one or more 6 RBs in the N_rb_coreset Rb within the N_symbol_coreset OFDM symbol of the core set to one or more REG indices.

[0245] In the example, the wireless device can receive configuration parameters from the base station. The configuration parameters can indicate one or more core sets. A core set can be associated with a CCE-to-REG mapping. For example, a single core set can have a single CCE mapping to a physical RB / resource of that single core set. For example, the CCE-to-REG mapping of a core set 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 the REG bundle size (e.g., for N_symbol_coreset = 1, L = 2 or 6, and when N_symbol_coreset is 2 or 3, L = N_symbol_coreset or 6). The index of the REG bundle (e.g., i) can be in the range [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 core set). For example, the CCE at index j 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 interleaving function. In the example, when the mapping from CCE to REG can be non-interleaved, f(x) can be x (e.g., the j-th CCE can include 6j / L, 6j / L+1, ..., and 6j / L+6 / L-1). When the mapping from CCE to REG 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 mapping from CCE to REG 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}.

[0246] For example, configuration parameters may include the frequencyDomainResources that can define N_rb_coreset. Configuration parameters may include the duration that can define N_symbol_coreset. Configuration parameters may include cce-REG-MappingType, which can be selected between interleaved and non-interleaved mapping. Configuration parameters may include reg-BundleSize, which can define the value of L for interleaved mapping. For non-interleaved mapping, L = 6 can be predetermined. Configuration parameters may include shiftIndex, which can determine n_shift as one of {0, 1, ..., 274}. When the precoder granularity (e.g., precoderGranularity indicated / configured by configuration parameters) is configured as sameAsREG-bundle, the wireless device can determine / assume the same precode for REGs within a REG bundle. When precoderGranularity is configured as allContiguousRBs, the wireless device can determine / assume the same precode for all REGs within a set of consecutive RBs of the core set.

[0247] For the first core set (e.g., CORESET#0), it can be defined / configured using L=6, R=2, n_shift=cell ID, and precoderGranularity=sameAsREG-bundle.

[0248] In the example, the base station can transmit one or more messages including configuration parameters. The configuration parameters can be used for multiple serving cells of the wireless device. The configuration parameters can include parameters that enable control channel repetition. For example, control channel repetition can be transmitted via one or more serving cells. 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, control channel repetition can be transmitted via a single cell, where the single cell can operate with a single transmit and receive point (TRP) or multiple TRPs. The base station can transmit one or more control channels of control channel repetition via one or more resources (e.g., or multiple downlink control signal / channel transmission opportunities) in different frequency resources (e.g., repetition in the frequency domain or in multiple carriers / cells). One or more resources can overlap in the time domain. The base station can transmit one or more second control channels of control channel repetition via one or more second resources (e.g., or multiple downlink control signal / channel transmission opportunities) in different time resources (e.g., repetition in the time domain or in multiple time slots). One or more second resources can overlap in the frequency domain. For example, the base station can transmit repetition of control channel repetition via multiple core sets of a single cell. For example, a base station can transmit control channels repeatedly via multiple search spaces within a single cell.

[0249] In the example, control channel repetition can be transmitted via multiple PDCCHs. For example, a PDCCH can indicate a physical control channel transmitted in a search space candidate. Based on the aggregation level, a search space candidate can include one or more CCEs. Multiple PDCCHs can be transmitted via multiple core sets of multiple cells. For example, a base station can transmit multiple PDCCHs via the core sets of cells in multiple cells. Multiple PDCCHs can be transmitted via multiple core sets of cells. For example, a base station can transmit multiple PDCCHs via the core sets of multiple core sets. Multiple PDCCHs can be transmitted via multiple search spaces, where a PDCCH within a multiple PDCCH can be transmitted via a search space within a multiple search space. Multiple PDCCHs can be transmitted via multiple search space candidates, where each of the multiple PDCCHs can be transmitted via a corresponding search space candidate among the multiple search space candidates. 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 at a monitoring time. The monitoring time of a search space can refer to the timing at which a radio device can monitor search space candidates used for receiving DCI / PDCCHs.

[0250] In the example, the PDCCHs in multiple PDCCHs with control channel repetition can transmit / transmit DCI based on the DCI format. For example, the first DCI of the first PDCCH in the multiple PDCCHs can be the same as the second DCI of the second PDCCH in the multiple PDCCHs. For example, the content of the first DCI / PDCCH can be the same as the content of the second DCI / PDCCH. Based on the same content of multiple PDCCHs, the wireless device can aggregate multiple DCI / PDCCHs before decoding them. For example, when transmitting / performing control channel repetition via DCI / PDCCHs with the same content, the wireless device may need to determine reference frequency domain resources (e.g., reference downlink control signal / channel transmission / repetition timing) and / or reference time domain resources (e.g., reference downlink control signal / channel transmission / repetition timing) and / or reference CCE index and / or reference REG index. For example, the wireless device can determine the aggregated DCI / PDCCH by aggregating multiple DCI / PDCCHs. The wireless device can then decode the aggregated DCI / PDCCH.

[0251] For example, the reference frequency domain resources for multiple DCI / PDCCHs can be determined based on the earliest (or latest) PDCCH among multiple PDCCHs. For instance, when the first PDCCH is transmitted in slot n and the second PDCCH is transmitted in slot n+1, the first PDCCH can determine the reference frequency domain resources. Similarly, reference time domain resources and / or reference CCE indices and / or reference REGs can be determined based on the earliest or latest PDCCH. The reference frequency domain (and / or time domain) resources for multiple DCI / PDCCHs can be determined based on the CORESET index of one or more CORESETs transmitting multiple DCI / PDCCHs. For example, the minimum (or maximum) core set index of one or more CORESETs can be used for determination.

[0252] Reference frequency domain (and / or time domain) resources for multiple DCI / PDCCHs can be determined based on search space indices of one or more search spaces transmitting multiple DCI / PDCCHs. For example, the minimum (or maximum) index of one or more search spaces can be used for determination. Reference frequency domain resources for multiple DCI / PDCCHs can be determined based on cell indices of one or more cells transmitting multiple DCI / PDCCHs. For example, the minimum (or maximum) index of one or more cells can be used for determination. Similarly, reference time domain resources and / or reference CCE indices and / or reference REGs can be determined based on CORESET indices, search space indices, and / or cell indices. Combinations of transmission time, CORESET indices, search space indices, and / or cell indices can be used. For example, reference frequency domain resources can first be determined based on the transmission time of the DCI / PDCCH. When multiple DCI / PDCCHs are transmitted simultaneously, the wireless device can use CORESET indices or search space indices and / or cell indices to further identify a reference DCI / PDCCH among the multiple DCI / PDCCHs. Wireless devices can determine the reference DCI / PDCCH used to determine reference frequency domain resources, reference time domain resources, reference CCE index and / or reference REG index.

[0253] In the example, the base station can configure / indicate the maximum number K of control channel repetitions via configuration parameters. The base station can transmit a repetition number M less than K. In response to M being less than K, the radio device can determine the reference DCI / PDCCH based on the candidate DCI / PDCCH in the Kth repetition, regardless of whether the Kth repetition has been actually transmitted (or received). The radio device can determine the reference DCI / PDCCH based on the first DCI / PDCCH as the first repetition. The radio device can determine the reference DCI / PDCCH based on the last DCI / PDCCH that has been actually transmitted (e.g., the Mth repetition). 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 the first control channel repetition mode (e.g., mode 1, repetition mode 1, first repetition mode). In the example, the base station can configure a list of time-domain resource allocation entries. The time-domain resource allocation entries can include the number of control channel repetitions, the scheduling offset between the control channel and the PDSCH, and / or the number of PDSCH repetitions. For example, the number of repetitions in the control channel can be represented by the repetition number K. Based on the repetition number, the wireless device can determine the reference DCI / PDCCH timing based on the Kth DCI / PDCCH repetition. The repetitive DCI / PDCCH can indicate entries in the time-domain resource allocation entry list.

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

[0255] Figure 19 An example of PDCCH repetition according to an embodiment of this disclosure is shown. The base station may transmit one or more RRC messages including configuration parameters. The configuration parameters may include parameters for control channel repetition. The parameters may include one or more scheduled carriers / cells for transmitting one or more PDCCH / DCIs for repetitive control channels (or control channel repetition). The parameters may include one or more search spaces for control channel repetition. Figure 19 An example of enabling control channel repetition via a first search space (SS#1) of a first carrier / cell (DL carrier #0) is illustrated. Parameters may indicate one or more indices of one or more search spaces of the first carrier and / or the carrier / cell index of the first carrier. The base station may transmit a first PDCCH via the first search space of the first carrier, which is scheduled via a TB on the first carrier. The base station may transmit a second PDCCH via the first search space of the first carrier, which is scheduled via a TB on the first carrier. The first and second PDCCHs may be transmitted via multiple monitoring opportunities of the first search space. The radio device may aggregate the first and second PDCCHs based on a first control channel repetition mode, or may attempt to independently receive / decode each PDCCH based on a second control channel repetition mode. Based on the first and / or second PDCCHs, the radio device may receive a TB.

[0256] In the example, the base station may transmit one or more RRC messages indicating control channel repetition enabled for a first carrier / cell. Based on the control channel repetition indication, the radio device may determine one or more first search spaces for the first carrier / cell based on the active BWP of the first carrier / cell. For example, the one or more first search spaces may be configured with a non-backoff DCI format, or configured with DCI format 1_1 and / or DCI format 1_2 and / or DCI format 0_1 ​​and / or DCI format 0_2. In the example, the one or more RRC messages may indicate one or more search space indices for the one or more first search spaces of the control channel repetition. The one or more RRC messages may indicate one or more DCI formats, where the radio device may apply control channel repetition. The radio device may determine one or more first search spaces for the first carrier / cell based on one or more DCI formats of the control channel repetition.

[0257] In the example, a base station can transmit multiple DCI / PDCCHs and scheduling resources for cell transport blocks via multiple TRPs, multiple core set pools, or multiple core cluster groups. For example, a base station can configure a first TRP (or a first core set pool) for a first cell via one or more RRC messages. One or more RRC messages may include configuration parameters. Configuration parameters may include a first core set pool for the first cell. Configuration parameters may include a second core set pool for the first cell. For example, the second core set pool may correspond to a second TRP for 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 transport block resources. The first / PDCCH and the second DCI / PDCCH may be retransmissions of control information (e.g., DCI). Transport blocks can be transmitted, for example, via a first TRP and a second TRP. Transport blocks can be transmitted based on multiple TCI states. Transport blocks can be transmitted based on TCI states, where a TCI state is associated with multiple TCI states. Transport blocks can be transmitted, for example, via a first TRP or a second TRP.

[0258] Configuration parameters can indicate whether control channel repetition is enabled / configured for the first cell. For example, parameters for the control channel repetition mode can be configured. The control channel repetition mode can be a first control channel repetition mode or a second control channel repetition mode. Configuration parameters can indicate a first core set associated with (or configured with) a first core set pool. Configuration parameters can indicate a second core set associated with (or configured with) a second core set pool. The radio device can determine a pair of first and second core sets based on rules, where repetitive DCI / PDCCH can be transmitted. For example, the radio device can determine the first core set of the first core set pool based on a search space associated with the first core set, where the radio device can monitor the 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 multiple first search spaces exist for a first core set pool configured with DCI format, the wireless device can determine multiple first core sets for the first core set pool. Similarly, the wireless device can determine a second core set for a second core set pool based on a search space associated with a second core set, wherein the wireless device can monitor the DCI format via the search space. When multiple second search spaces exist for a second core set pool configured with DCI format, the wireless device can determine multiple second search spaces. In the example, the wireless device can be configured to have at most one search space with DCI format in each core set pool.

[0259] In the example, the wireless device can determine the second core set of the second core set pool based on the first core set index 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, GAP can be a determined / predetermined value (e.g., 0, 12). For example, configuration parameters can include parameters indicating the value of GAP. In the example, the wireless device can determine the second core set based on the 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, 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 associations configured by configuration parameters. For example, configuration parameters can indicate the association between each core set / search space associated with the first core set pool and each core set / search space associated with the second core set pool. In the example, configuration parameters can include the first core set and / or the first search space of the first core set pool. The wireless device can monitor the first DCI / PDCCH via the first search space of the first core set pool. Configuration parameters may indicate / include parameters indicating control channel repetition across multiple TRPs or multiple core set pools for a first core set or a first search space. Based on these parameters, the wireless device can determine a second core set or a second search space for a second core set pool. For example, the wireless device may 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 may be used for the second core set. For example, the monitoring timing of the first search space may be used to determine the monitoring timing of the second search space.

[0260] In the example, the base station may indicate control channel repetition based on (or for) a core set. For example, the base station may transmit multiple DCI / PDCCHs via the core set. The base station may transmit multiple DCI / PDCCHs on multiple TRPs. The base station may transmit one of multiple RRC messages and / or MAC CEs indicating the activation of multiple TCI states for the core set. For example, the multiple TCI states may include a first TCI state corresponding to a first TRP among the multiple TRPs, and a second TCI state corresponding to a second TRP among the multiple TRPs. The base station may transmit one or more second RRC messages including configuration parameters of the core set. For example, the configuration parameters may indicate control channel repetition based on the core set. The configuration parameters may indicate control channel repetition across multiple TRPs. The configuration parameters may indicate a repetition pattern across multiple TRPs. For example, the repetition pattern (e.g., TRP switching pattern) may be [0,…,0,1,…,1], where 0 may represent the first TRP among the multiple TRPs, and 1 may represent the second TRP among the multiple TRPs. The base station may, for example, indicate a bitmap via configuration parameters that indicates the number of control channel repetitions. Each bit in the bitmap can represent which TRP can transmit the i-th repetition. The repetition pattern can be [0,1,0,1,…,0,1]. Various repetition patterns can be considered. Based on this repetition pattern, the wireless device can receive control channel repetitions based on the TCI states among 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.

[0261] Figure 20An example of control channel repetition across multiple TRPs according to an embodiment of this disclosure is illustrated. The base station may transmit one or more RRC messages including configuration parameters. The configuration parameters may indicate / include a first TRP (TRP#0) and a second TRP (TRP#1) associated with the cell. The configuration parameters may include / indicate control channel repetition across multiple TRPs (e.g., via the first TRP and the second TRP). The base station may transmit a first DCI / PDCCH (e.g., PDCCH#1) via the first TRP or a first core pool. The first DCI / PDCCH may include / indicate resources for scheduling TBs via multiple TRPs. The base station may transmit a second DCI / PDCCH (e.g., PDCCH#2) via a second TRP or a second core pool. The second DCI / PDCCH may include / indicate resources for scheduling TBs via multiple TRPs. The first DCI / PDCCH and the second DCI / PDCCH may indicate the same HARQ procedure index (e.g., HARQ-K) for scheduling TBs. The base station may transmit a third DCI / PDCCH via the first TRP. The base station can transmit the fourth DCI / PDCCH (e.g., PDCCH#4) via the second TRP. Control information for scheduling the TB can be repeated four times via multiple TRPs. The radio device can monitor the first and third DCI / PDCCHs based on the first TCI state associated with the first TRP or the first core pool. The radio device can monitor the second and fourth DCI / PDCCHs based on the second TCI state associated with the second TRP or the second core pool.

[0262] The base station can repeat the TB via four repetitions of the first TRP and four repetitions of the second TRP. When the radio device can support simultaneous reception via the first and second TRPs, it can simultaneously repeat the TB via both TRPs. When the radio device may not support simultaneous reception via the first and second TRPs, the base station can transmit the repeated TB via the first and second TRPs based on time-domain multiplexing. For example, the base station can transmit the first repetition of the repeated transmission via the first TRP. The base station can transmit the second repetition of the repeated transmission via the second TRP. The handover mode between the first and second TRPs can be configured by the base station based on RRC / MAC-CE / DCI signaling. The first and second DCIs can schedule the repeated transmission of the TB. The implementation of repeating the control channel via multiple TRPs can enhance reliability and deliver a better QoS experience.

[0263] In the example, the base station can transmit one or more RRC messages including configuration parameters. Configuration parameters can indicate control channel repetition enabled for the cell. The base station can transmit multiple DCI / PDCCHs scheduling transport blocks via multiple core sets of the cell. For example, configuration parameters can configure a first core set and a second core set for control channel repetition. Configuration parameters can include / indicate a first search space associated with the first core set. Configuration parameters can include / indicate a second search space associated with the second core set. Configuration parameters can include / indicate a first TCI state associated with the first core set. Configuration parameters can include / indicate a second TCI state associated with the second core set. The first TCI state can be the same as or different from the second TCI state. Configuration parameters can include / indicate a set of first TCI states associated with the first core set. One or more MAC CEs can indicate a first TCI state in the set of first TCI states of the first core set. For example, configuration parameters can include / indicate a set of second TCI states associated with the second core set. One or more second MAC CEs can indicate a second TCI state in the set of second TCI states of the second core set. Configuration parameters can indicate that the first core set and the second core set are associated to schedule repeated DCI / PDCCH for transport blocks.

[0264] In the example, configuration parameters may indicate / include the search space associated with the first core set and the second core set. Configuration parameters may include multiple core set indices. Configuration parameters may include a core set index among multiple core set indices that indicates the first core set. Configuration parameters may include multiple core set indices, one or more indices of repeating / attached core sets (e.g., core sets used for control channel repeating in addition to the first core set and the second core set). For example, one or more indices may indicate the second core set. When the first core set and the second core set are associated for control channel repeating, the first parameter of the first core set and the second parameter of the second core set may have configurational limitations. For example, the set of resource blocks (RBs) in the frequency domain of the first core set may be the same as the set of resource blocks (or a subset or superset thereof) in the frequency domain of the second core set. The wireless device may determine the set of RBs belonging to the first core set and the second core set for control channel repeating. For example, the first duration of the first core set may be the same as the second duration of the second core set. For example, the number of REGs in the first core set may be the same as the number of REGs. For example, the number of CCEs in the first core set can be the same as (or less than or greater than) the number of CCEs in the second core set. The wireless device can determine the number of REGs based on the determined RB set or based on the RB set of the first core set. For example, the first CCE-to-REG mapping type of the first core set (e.g., between interleaved and non-interleaved) can be the same as the second CCE-to-REG mapping type of the second core set. For example, the precoder granularity of the first core set can be configured to be the same as the precoder granularity of the second core set. For example, the first tci-PresenceInDCI of the first core set can be the same as the second tci-PresenceInDCI of the second core set. For example, the first rb-Offset of the first core set can be the same as the second rb-Offset of the second core set.

[0265] The first and second core sets may have potentially different configurations for one or more parameters. For example, one or more parameters may include one or more TCI states. For example, one or more parameters may include DM-RS scrambling identities (e.g., pdcch-DMRS-ScramblingID). For example, one or more parameters may include core set pool indexes (e.g., coresetPoolIndex). For example, one or more parameters may include core set indexes.

[0266] When the wireless device can receive first configuration parameters for a first core set and second configuration parameters for a second core set, the wireless device determines whether a first number of CCEs in the first core set is equal to or less than (or greater than) a second number of CCEs in the second core set. Based on this determination, the wireless device may consider the first and second core sets as usable for control channel repetition. Otherwise, the wireless device may determine that the first and second core sets are not usable for control channel repetition. Alternatively, the wireless device may determine the minimum number of CCEs (e.g., M) among one or more numbers of CCEs in one or more core sets (e.g., determining the core set with the minimum number of CCEs in one or more core sets). For example, one or more core sets may be configured / indicated / used for control channel repetition. The wireless device may determine / assume / consider the top M candidates for each core set in one or more core sets for control channel repetition.

[0267] In the example, the wireless device can determine the number of REGs in a first core set of one or more core sets configured for control channel repetition. The wireless device can determine a second number of REGs in a second core set of one or more core sets. The wireless device can determine whether the number of REGs equals the second number of REGs. In response to determining that the number of REGs equals the second number of REGs, the wireless device can consider configuring control channel repetition via the first and second core sets. Otherwise, the wireless device can treat this configuration as an error condition and can activate control channel repetition without using the first and second core sets. In the example, the wireless device can determine a minimum number of REGs in one or more core sets (e.g., determine a core set with a minimum number of REGs). The wireless device can assume a minimum number of REGs for control channel repetition.

[0268] Configuration parameters for the search space associated with the first and second core sets can include / indicate a switching or mapping mode for the first and second core sets. For example, a wireless device can determine the search space monitoring timing based on the search space configuration parameters. A wireless device can determine the search space monitoring timing based on the first core set. A wireless device can determine the second search space monitoring timing or extended monitoring timing based on rules. For example, a wireless device can determine the second search space monitoring timing as the next time slot after the first monitoring timing. A wireless device can determine the second search space monitoring timing based on the second search space. Configuration parameters can indicate a bitmap of the number of OFDM symbols (or the number of time slots, e.g., multiple time slots) in a time slot. For each corresponding OFDM symbol or time slot, the bitmap can indicate 0 for the first core set or 1 for the second core set. When 0 is indicated for an OFDM symbol, the wireless device can monitor the search space monitoring timing based on the first core set. When 1 is indicated for a second OFDM symbol, the wireless device can monitor the second search space monitoring timing based on the second core set.

[0269] In the example, the wireless device may receive one or more RRC messages that include configuration parameters. The configuration parameters may indicate / include a core set representing a portion of the cell bandwidth. The configuration parameters may include parameters of the search space associated with the core set. The search space parameters may indicate a first monitoring period in units of a first duration. For example, the first duration may be one or several time slots. The search space parameters may indicate a second monitoring period in units of a second duration. For example, the second duration may be one or several OFDM symbols or one time slot. For example, the second duration may be less than the first duration. The wireless device may monitor one or more repeating DCI / PDCCH events via one or more monitoring opportunities (e.g., multiple downlink control signal / channel transmission opportunities) determined within the first monitoring period based on the second monitoring period. For example, the configuration parameters may indicate one or more monitoring opportunities within the first monitoring period.

[0270] For example, a wireless device may receive / monitor a first DCI / PDCCH in one or more repeating DCI / PDCCHs via a first monitoring time in one or more monitoring times. The wireless device may receive / monitor a second DCI / PDCCH in one or more repeating DCI / PDCCHs via a second monitoring time in one or more monitoring times. The first DCI / PDCCH may be the same as the second DCI / PDCCH. The first DCI / PDCCH and the second DCI / PDCCH may indicate the same resource of the transport block. The wireless device may receive / monitor a DCI via one or more monitoring times, wherein the search space candidate for the DCI may include one or more candidates from one or more monitoring times. For example, the search space candidate may include a first candidate from the first monitoring time and a second candidate from the second monitoring time. For example, the first starting CCE index of the first candidate from the first monitoring time may be the same as the second starting CCE index of the second candidate from the second monitoring time.

[0271] Wireless devices can receive / monitor DCI / PDCCH via one or more monitoring times, wherein the search space candidates for DCI / PDCCH may include one or more CCEs from one or more monitoring times.

[0272] For example, a core set can be associated with multiple TCI states that are active TCI states. Multiple TCI states can be activated, for example, via one or more RRC messages, MAC CE, or DCI. A wireless device can monitor a first monitoring opportunity based on a first TCI among the multiple TCI states. A wireless device can monitor a second monitoring opportunity based on a second TCI among the multiple TCI states.

[0273] Figure 21 An example of control channel repetition according to an embodiment of this disclosure is shown. For example, a base station may transmit one or more RRC messages including configuration parameters. The configuration parameters may include / indicate a core set associated with an active TCI state. The base station may activate the active TCI state via one or more RRC messages, one or more MAC CEs, or one or more DCIs. The configuration parameters may include / indicate a bitmap that indicates one or more monitoring opportunities for control channel repetition. Figure 21 The diagram shows a bitmap of size 14 (e.g., the bitmap corresponds to each bit mapped to a time slot for each OFDM symbol). The bitmap indicates the monitoring timings for the first and sixth OFDM symbols of the time slot. Configuration parameters can indicate / compile the first monitoring period into two time slots (e.g., monitoring every two time slots). Within each monitoring period, the wireless device can determine one or more monitoring timings based on the bitmap. For example, when the bitmap is not available, the wireless device can determine monitoring timings starting from the first OFDM symbol of the time slot. Figure 21 In the example, the wireless device can determine a first monitoring timing and a second monitoring timing based on a bitmap in each monitoring cycle. The wireless device can monitor the first and second monitoring timings for receiving one or more DCI / PDCCHs scheduled to transport blocks.

[0274] In the example, for the search space, configuration parameters indicate one or more monitoring opportunities within a monitoring period. For example, `monitoringSlotPeriodicityAndOffset` can determine the monitoring period. When the parameter can include `monitoringSymbolWithinSlot`, the wireless device can determine the monitoring period based on the interval between each monitoring opportunity within a time slot based on `monitoringSymbolWithinSlot`. The wireless device may expect the intervals between monitoring opportunities within a time slot to be equal. Alternatively, when the search space is used for control channel repetition, the parameter may not include `monitoringSymbolsWithinSlot`. In the example, when control channel repetition is enabled, `monitoringSymbolsWithinSlot` can be used to indicate one or more monitoring opportunities within a monitoring period determined based on `monitoringSlotPeriodicityAndOffset`. For example, parameters indicating the enabling of control channel repetition can be configured for the search space or for the core set associated with the search space or the DCI format monitored via the search space. For example, the duration of the search space can be used to determine one or more monitoring opportunities within a monitoring period. For example, when the monitoring period is longer than a time slot, the wireless device can determine one or more monitoring opportunities based on the monitoring period and duration. For example, when the monitoring period is P time slots and the duration is D, the wireless device can determine the first monitoring opportunity among one or more monitoring opportunities based on monitoringSlotPeriodicityAndOffset. The wireless device can determine the second monitoring opportunity among one or more monitoring opportunities as the next time slot of the first monitoring opportunity. The wireless device can determine a number of monitoring opportunities starting from the first monitoring opportunity in consecutive time slots, up to D. For example, when the search space is configured with multiple core sets / associated with multiple core sets, the search space can include multiple control resource set IDs (e.g., controlResourceSetID and a second controlResourceSetID).

[0275] In the example, the base station may transmit a first DCI / PDCCH via a first monitoring time in one or more monitoring times. The base station may transmit a second DCI / PDCCH via a second monitoring time in one or more monitoring times. The first DCI / PDCCH and the second DCI / PDCCH may indicate the same resources of a transport block. The first content of the first DCI / PDCCH may be the same as or different from the second content of the second DCI / PDCCH. The radio device may attempt to decode the first DCI / PDCCH independently of the second DCI / PDCCH. The radio device may not assume that the base station can transmit the first DCI / PDCCH and the second DCI / PDCCH. The base station may transmit one or more DCI / PDCCHs within one or more monitoring times. The base station may transmit a single DCI / PDCCH within one or more monitoring times. The base station may transmit a DCI / PDCCH within each monitoring time. The base station may transmit any number of repeated DCI / PDCCHs within one or more monitoring times.

[0276] The base station can instruct a first control channel repetition pattern for one or more monitoring opportunities. Based on the first control channel repetition pattern, the wireless device can determine the number of monitoring opportunities O in one or more monitoring periods within a monitoring cycle. Based on a time-priority approach, the monitoring opportunities in the one or more monitoring opportunities are indexed from 0, ..., O-1. The wireless device can attempt to decode one or more search space candidates, which aggregate candidates from monitoring opportunities 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, which aggregates candidates from the first monitoring opportunity in the one or more monitoring opportunities. The wireless device can attempt to decode a second candidate, which aggregates candidates from the second monitoring opportunity in the one or more monitoring opportunities and another candidate. The wireless device can attempt to decode a fourth candidate, which aggregates each candidate from each monitoring opportunity in the one or more monitoring opportunities. The wireless device can aggregate candidates from one or more monitoring opportunities where the starting CCE index of the candidates is the same, or the wireless device can determine the candidates based on rules. For example, the wireless device can determine candidates for the same frequency resource in each monitoring opportunity. For example, wireless devices can identify candidates for the same REG (or the same REG index) at each monitoring time.

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

[0278] In an example of determining one or more search space candidates for an aggregation level spanning one or more monitoring moments, the base station may indicate four monitoring moments in a monitoring period indexed from the first to the fourth monitoring moment. In this example, it is assumed that a set of candidates for the aggregation level is consistent across the four monitoring moments. For example, the first candidate for aggregation level 2 may begin in the third CCE, and the second candidate for aggregation level 2 may begin in the fifth CCE. Similarly, the first candidate for aggregation level 4 may begin in N_CCE (e.g., the number of CCEs) - the 8th CCE, and the second candidate for aggregation level 4 may begin in N_CCE - the 4th CCE. The wireless device can determine a candidate list with aggregation level 8 by combining / aggregating four candidates from aggregation level 2 (each candidate from one monitoring moment) and / or by combining / aggregating two candidates from aggregation level 4 (each candidate from one monitoring moment). In this example, the first box on the left and the second small box on the right show candidates with AL = 8. The wireless device can determine multiple candidates by aggregating / combining the second candidate with AL = 2 and / or the second candidate with AL = 4. Similarly, the wireless device can determine candidates with aggregation level (AL) = 16 by combining / aggregating four candidates with AL = 4. The wireless device can determine two AL=16.

[0279] Wireless devices may not aggregate candidates, where candidates may not include those from the first monitoring time (or the earliest monitoring time in the monitoring period). Wireless devices may determine possible aggregation levels and / or candidates by aggregating candidates from the first monitoring time, the first monitoring time + the second monitoring time, the first monitoring time + the second monitoring time + the third monitoring time + the fourth monitoring time, the first monitoring time + the second monitoring time + the third monitoring time + the fourth monitoring time + the fifth monitoring time - the sixth monitoring time + the seventh monitoring time + the eighth monitoring time, and so on.

[0280] In the example, the wireless device can determine a candidate list for the aggregation level based on a hash function applied in each time slot. The same candidates can be mapped when the first and second monitoring times reside in the same time slot. Otherwise, different candidates may be determined. The base station can transmit DCIs across candidates in one or more monitoring times.

[0281] In the example, the base station may transmit one or more messages including configuration parameters. The configuration parameters may include / indicate search space groups for controlling channel repetition. Search space groups may include one or more search spaces. For example, a search group may include a first search space of a first carrier and a second search space of a second carrier. For example, a search space group may include a first search space of a cell's first BWP and a second search space of a cell's second BWP. For example, a search space group may include a first search space of a first cell's first BWP and a second search space of a second cell's second BWP. For example, for a cell's BWP, the configuration parameters may indicate one or more search space groups. Search space groups in one or more search space groups may be associated with / configured with one or more DCI formats. In the example, the radio device may determine search space groups based on one or more search spaces configured with / associated with a cell's BWP, wherein each of the one or more search spaces may be configured to monitor a DCI format in one or more DCI formats. For example, one or more DCI formats may include DCI format 1_1 and DCI format 0_1. For example, one or more DCI formats may include DCI format 0_0 and DCI format 1_0. For example, one or more DCI formats may include DCI format 1_2 and DCI format 0_2. For example, one or more DCI formats may include DCI format 3_0 and DCI format 3_1. For example, one or more DCI formats may include downlink / uplink DCI with non-fallback DCI. For example, one or more DCI formats may include downlink / uplink DCI with fallback DCI. For example, one or more DCI formats may include DCI formats for sidelink DCI.

[0282] A wireless device can determine search space candidates on one or more search spaces of a search space group based on multiple core sets in a similar manner to addressing for control repetition. In an example, the wireless device can determine one or more monitoring opportunities in a time slot based on one or more search spaces. For example, in time slot n, the wireless device can determine one or more first monitoring opportunities based on a first search space in one or more search spaces. The wireless device can determine one or more second monitoring opportunities in time slot n based on a second search space in one or more search spaces. The wireless device can monitor one or more first monitoring opportunities and one or more second monitoring opportunities in time slot n. The wireless device may not expect overlap between the monitoring opportunities of the search spaces in one or more search spaces and the second monitoring opportunities of the second search spaces in one or more search spaces in the time domain. The wireless device can monitor one or more repeating DCIs based on the DCI format via one or more monitoring opportunities in a time slot.

[0283] In the example, the 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 the same content or different content. When each DCI may have the same content, the wireless device can aggregate one or more repeated DCIs. In the example, one or more repeated DCIs can be sent via PDCCHs, where PDCCHs can be transmitted on one or more search space candidates in one or more search spaces. In the example, DCIs can be repeatedly transmitted via one or more PDCCHs, where each PDCCH can repeatedly carry / transmit DCIs.

[0284] In the example, the base station can associate multiple TCI states with a core set that serves as the active TCI state. Figure 22An example of a core set associated with multiple TCI states as active TCI states, according to an embodiment of this disclosure, is shown. In this example, the base station may indicate multiple monitoring opportunities within a time slot or a monitoring period in which control channels repeat. A wireless device may monitor a first monitoring opportunity based on a first TCI state among the multiple TCI states. A wireless device may monitor a second monitoring opportunity based on a second TCI state among the multiple TCI states. The base station may indicate a switching mode between the multiple TCI states. For example, configuration parameters of the search space associated with the core set may include / indicate enabling control channel repeating. Configuration parameters may include / indicate enabling TCI switching or enabling control channel repeating via multiple TCI states. Configuration parameters may include / indicate a switching mode. For example, within a monitoring period or a time slot or several time slots (e.g., between monitoring periods configured by the monitoringSlotPeriodicityAndOffset parameter of the search space), in each of one or more monitoring opportunities, the switching mode may be an alternation between the first TCI state and the second TCI state among the multiple TCI states. For example, the switching mode may be a 50 / 50 split between the first TCI state and the second TCI state. For example, the number of one or more monitoring opportunities is K. The wireless device can monitor the first layer (K / 2) monitoring opportunities based on a first TCI state. The wireless device can monitor the remaining monitoring opportunities within a monitoring period based on a second TCI state. For example, the switching mode can be a bitmap to indicate the TCI state in each of the one or more monitoring opportunities.

[0285] Figure 23An example of a MAC CE format (e.g., a TCI state indication for a UE-specific PDCCH MAC CE, an enhanced TCI state indication for a UE-specific PDCCH MAC CE) is shown, indicating / activating / updating / selecting one or more TCI states (e.g., TCI state 1 and TCI state 2) of a core set for a serving cell. A base station can indicate one or more TCI state indices (e.g., TCI state ID 1 and TCI state ID 2) in MAC CE format to activate one or more TCI states of a core set (indicated by the core set ID). One or more TCI state indices can indicate / identify one or more TCI states. Each TCI state index in the one or more TCI state indices can indicate / identify the corresponding TCI state in the one or more TCI states. The MAC CE format can include one or more fields. The 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 to / identifies / indicates the serving cell. A second field among one or more fields may indicate / include a core set index (e.g., core set ID) that belongs to / identifies / indicates the core set of the serving cell. A third field among one or more fields may indicate / include a first TCI state index (e.g., TCI state ID 1) that belongs to / identifies / indicates the first TCI state. One or more TCI states may include the first TCI state. A fourth field among one or more fields (e.g., R) may be a reserved field. A fifth field among one or more fields may indicate / include a second TCI state index (e.g., TCI state ID 2) that belongs to / identifies / indicates the second TCI state. In the example, one or more fields of the MAC CE format may include a second TCI state index based on the 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 may not include the second TCI state index (e.g., the fifth field may be a reserved field). When the value of the fourth field is equal to one, the MAC CE format may include the second TCI state index. One or more TCI states may include the second TCI state. The MAC CE format may be an activation command. Configuration parameters can indicate the first TCI state index of a first TCI state. Configuration parameters can indicate the second TCI state index of a second TCI state. Configuration parameters can indicate the core set index of a core set. Configuration parameters can indicate the serving cell index of a serving cell. Configuration parameters can indicate one or more TCI state indices for one or more TCI states. One or more TCI states may include a first TCI state and a second TCI state.One or more TCI status indices may include a first TCI status index and a second TCI status index.

[0286] Figure 24 , Figure 25 and Figure 26 This is an example of control channel repetition according to one aspect of the embodiments of this disclosure.

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

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

[0289] In the example, the wireless device can perform uplink transmission (e.g., PUSCH, PUCCH, SRS) via the cell at a first time and a first frequency. The wireless device can perform downlink reception (e.g., PDCCH, PDSCH) via the cell at a second time and a second frequency. In the example, the cell can operate in Time Division Duplex (TDD) mode. In TDD mode, the first and second frequencies can be the same. In TDD mode, the first and second times can be different. In the example, the cell can operate in Frequency Division Duplex (FDD) mode. In FDD mode, the first and second frequencies can be different. In FDD mode, the first and second times can be the same.

[0290] In the example, the wireless device can be in RRC connection mode.

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

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

[0293] In the example, a cell may include multiple BWPs. These multiple BWPs may include one or more uplink BWPs, which include the cell's uplink BWPs. These multiple BWPs may also include one or more downlink BWPs, which include the cell's downlink BWPs.

[0294] In the example, one of the multiple downlink BWPs can be in an active or inactive state. In the example, when one or more downlink BWPs is active, the wireless device can monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / via the downlink BWP. In the example, when one or more downlink BWPs is active, the wireless device can receive PDSCH on / through / for the downlink BWP. In the example, when one or more downlink BWPs is inactive, the wireless device cannot monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / for the downlink BWP. In the example, when one or more downlink BWPs is inactive, the wireless device cannot monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / for the downlink BWP. When one or more downlink BWPs is inactive, the wireless device can stop monitoring (or receiving) downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / for the downlink BWP. In the example, when one or more downlink BWPs are inactive, the radio device cannot receive PDSCH on / via / for the downlink BWP. When one or more downlink BWPs are inactive, the radio device can stop receiving PDSCH on / via / for the downlink BWP.

[0295] In the example, when one or more uplink BWPs is active, the wireless device can transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) on / via the uplink BWP. In the example, when one or more uplink BWPs is inactive, the wireless device cannot transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) on / via the uplink BWP.

[0296] In the example, the wireless device can activate one or more downlink BWPs in the cell. In the example, activating a downlink BWP can include the wireless device setting (or switching) the downlink BWP to the cell's active downlink BWP. In the example, activating a downlink BWP can include the wireless device setting the downlink BWP to an active state. In the example, activating a downlink BWP can include switching the downlink BWP from an inactive state to an active state.

[0297] In the example, the wireless device can activate one or more uplink BWPs of the cell. In the example, activating an uplink BWP can include the wireless device setting (or switching) the uplink BWP to the cell's active uplink BWP. In the example, activating an uplink BWP can include the wireless device setting the uplink BWP to an active state. In the example, activating an uplink BWP can include switching the uplink BWP from an inactive state to an active state.

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

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

[0300] In the example, one or more configuration parameters can indicate one or more core sets. One or more configuration parameters can indicate one or more core sets of the (active) downlink BWP for a cell. In the example, the (active) downlink BWP for a cell may include one or more core sets. One or more core sets may include a first core set. One or more core sets may include a second core set.

[0301] In the example, one or more configuration parameters may indicate one or more core set indices for one or more core sets (e.g., provided by the higher-level parameter ControlResourceSetId). In the example, each core set in one or more core sets may be identified / indicated by a corresponding core set index among the one or more core set indices. In the example, a first core set in one or more core sets may be identified by a first core set index among the one or more core set indices. A second core set in one or more core sets may be identified by a second core set index among the one or more core set indices.

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

[0303] In the example, the first core set and the second core set can be the same. The index of the first core set and the index of the second core set can be the same.

[0304] In the example, the first core set and the second core set can be different. The index of the first core set and the index of the second core set can also be different.

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

[0306] In the example, one or more configuration parameters can indicate the search space set index / identifier for multiple search space sets (e.g., provided by the higher-level parameter `searchSpaceId`). In the example, each search space set in the multiple search space sets can be identified by its corresponding search space set index within the search space set index. In the example, the first search space set in the multiple search space sets can be identified by the first search space set index within the search space set index. In the example, the second search space set in the multiple search space sets can be identified by the second search space set index within the search space set index.

[0307] In the example, one or more configuration parameters can indicate the PDCCH monitoring period (e.g., monitoringSlotPeriodicityAndOffset) for multiple search space sets. One or more configuration parameters can indicate the corresponding PDCCH monitoring period (e.g., monitoringSlotPeriodicityAndOffset) within the PDCCH monitoring period of each search space set in the multiple search space sets. One or more configuration parameters can indicate the first PDCCH monitoring period (e.g., 2 time slots) for the first search space set in the multiple search space sets. One or more configuration parameters can indicate the second PDCCH monitoring period (e.g., 10 time slots) for the second search space set in the multiple search space sets.

[0308] In the example, search space sets within multiple search space sets can be associated with (or linked to) core sets within one or more core sets. In the example, one or more configuration parameters can indicate the core set (or core set index) of a search space set (e.g., provided by the higher-level parameter controlResourceSetId in the SearchSpace parameter). In the example, this association (or link) can be one-to-one. A one-to-one association may include a search space set associated with (or linked to) a core set not being associated with (or linked to) a second core set different from that core set. One or more core sets may include a second core set.

[0309] In the example, based on the association (or link) between the search space set and the core set, the wireless device can monitor downlink control signal / channel PDCCH candidates (e.g., DCI, PDCCH, RS, GC-PDCCH, DMRS, etc.) during PDCCH monitoring for the search space set associated (or linked) with that core set. In the example, based on the association (or link) between the search space set and the core set, the wireless device can monitor PDCCH candidates for DCI during PDCCH monitoring for the search space set within the core set associated (or linked) with the search space set. In the example, based on the association (or link) between the search space set and the core set, the wireless device can monitor the PDCCH for the search space set within the core set associated (or linked) with the search space set for DCI.

[0310] A wireless device can monitor downlink control channels in a core set for DCI. Monitoring downlink control channels in the core set for DCI can include monitoring one or more PDCCH candidates for DCI during one or more PDCCH monitoring times associated with one or more search space sets / one or more search space sets. Multiple search space sets can include one or more search space sets. The wireless device can determine one or more PDCCH monitoring times for one or more search space sets based on one or more search space set configuration parameters (e.g., IESearchSpace). One or more search space set configuration parameters can indicate one or more PDCCH monitoring periods for one or more search space sets (e.g., monitoringSlotPeriodicityAndOffset). One or more search space set configuration parameters can indicate PDCCH monitoring symbols for one or more search space sets (e.g., monitoringSymbolsWithinSlot).

[0311] In the example, one or more configuration parameters may indicate one or more core set indices of multiple search space sets (e.g., provided by the higher-level parameter controlResourceSetId in the higher-level parameter SearchSpace). In the example, each search space set in the multiple search space sets may be associated (or linked) to a corresponding core set in one or more core sets, identified by a corresponding core set index in one or more core set indices. In the example, one or more configuration parameters may indicate the first core set index of the first core set of the first search space set. These one or more configuration parameters may indicate the first core set index of the first core set in the first core set index field of the first search space set (e.g., provided by the higher-level parameter controlResourceSetId in the higher-level parameter SearchSpace). Based on these one or more configuration parameters indicating the first core set index of the first core set of the first search space set, the first search space set may be associated (or linked) to the first core set. In the example, these one or more configuration parameters may indicate the first core set index of the first core set of the second search space set. These one or more configuration parameters may indicate the first core set index of the first core set in the second core set index field of the second search space set (e.g., provided by the higher-level parameter controlResourceSetId in the higher-level parameter SearchSpace). Based on one or more configuration parameters that indicate the index of the first core set of the first core set of the second search space set, the second search space set can be associated with (or linked to) the first core set. In the example, the one or more configuration parameters can indicate the index of the second core set of the second core set of the first search space set. Based on one or more configuration parameters that indicate the index of the second core set of the second core set of the first search space set, the first search space set can be associated with (or linked to) the second core set. In the example, the one or more configuration parameters can indicate the index of the second core set of the second core set of the second search space set. Based on one or more configuration parameters that indicate the index of the second core set of the second core set of the second search space set, the second search space set can be associated with (or linked to) the second core set.

[0312] In the example, one or more first search space sets among multiple search space sets can be associated with (or linked to) a first core set. One or more configuration parameters can indicate the first core set (or the first core set index of the first core set) of one or more first search space sets. For a first core set, one or more configuration parameters can indicate one or more first search space sets. One or more second search space sets among multiple search space sets can be associated with (or linked to) a second core set. One or more configuration parameters can indicate the second core set (or the second core set index of the second core set) of one or more second search space sets. For a second core set, one or more configuration parameters can indicate one or more second search space sets.

[0313] The wireless device may monitor one or more PDCCH candidates for DCI during one or more first PDCCH monitoring times for one or more first search space sets associated with the first core set or the one or more first search space sets.

[0314] The wireless device may monitor one or more PDCCH candidates for DCI during one or more second PDCCH monitoring times for one or more second search space sets associated with the second core set or the one or more second search space sets.

[0315] One or more configuration parameters may indicate control channel repetition (e.g., PDCCH repetition / aggregation). One or more configuration parameters may include a control channel repetition enable parameter that enables (or activates or indicates) control channel repetition. Control channel repetition may include the repetition of downlink control signals / channels (e.g., PDCCH, DCI).

[0316] In the example, one or more configuration parameters can indicate the number of repetitions for the control channel.

[0317] In the example, one or more configuration parameters can indicate the number of repetitions of the control channel for one or more core sets. One or more configuration parameters can indicate the number of repetitions of the control channel for each core set within one or more core sets. In the example, one or more configuration parameters can indicate the number of repetitions of the control channel for multiple search space sets within one or more core sets. One or more configuration parameters can indicate the number of repetitions of the control channel for the corresponding search space set within each core set within one or more core sets. In the example, one or more configuration parameters can indicate the number of repetitions of the control channel for at least one search space set within multiple search space sets.

[0318] In the example, one or more configuration parameters can indicate one or more core sets for control channel repetition. One or more configuration parameters can link / map / associate one or more core sets used for control channel repetition.

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

[0320] 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., ...). Figures 24 to 26 (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...). Figures 24 to 26 In this context, the number of repetitions equals 2. Multiple DCI / PDCCHs may include a first downlink control signal / channel (e.g., Figures 24 to 26 DCI 1) and second downlink control signals / channels (e.g., Figures 24 to 26 DCI 2 in the middle.

[0321] In the example, the wireless device can be served (e.g., receive from or transmit to multiple TRPs) by multiple TRPs (e.g., receive from or transmit to multiple TRPs). Each downlink control signal / channel of multiple DCI / PDCCHs can be transmitted by the corresponding TRP among the multiple TRPs. For example, in Figures 24 to 26 In this context, the first TRP (e.g., TRP 1) of a plurality of TRPs can transmit DCI1, while the second TRP (e.g., TRP 2) of a plurality of TRPs can transmit DCI2.

[0322] 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... Figures 24 to 26In this context, DCI 1 and DCI 2 can be the same (or equal). The content of DCI Protocol 1 and DCI Protocol 2 can be the same. The payloads of DCI 1 and DCI 2 can be the same. The DCI fields (or the values ​​of the DCI fields) of DCI 1 and DCI 2 can be the same.

[0323] In the example, the first downlink control signal / channel and the second downlink control signal / channel can be the same (e.g., the same content, the same DCI field, the same DCI size, the same payload, the same DCI field value, etc.). In the example, the first downlink control signal / channel and the second downlink control signal / channel can be the same as the downlink control signal / channel. The first downlink control signal / channel can be a downlink control signal / channel. The second downlink control signal / channel can be a downlink control signal / channel. The first downlink control signal / channel and the second downlink control signal / channel can be a repetition of the downlink control signal / channel.

[0324] A base station can transmit multiple DCI / PDCCHs via one or more core sets / in one or more core sets for the repetition of downlink control signals / channels. The base station can transmit each downlink control signal / channel of the multiple DCI / PDCCHs via the corresponding core set of one or more core sets. Transmitting multiple DCI / PDCCHs via one or more core sets / in one or more core sets for the repetition of downlink control signals / channels can include transmitting downlink control signals / channels via one or more core sets / in one or more core sets. Transmitting multiple DCI / PDCCHs via one or more core sets / in one or more core sets for the repetition of downlink control signals / channels can include repeating the transmission of downlink control signals / channels via one or more core sets / in one or more core sets. For the repetition of downlink control signals / channels, the base station can transmit multiple DCI / PDCCHs via multiple search space sets associated with one or more core sets / in those multiple search space sets. For the repetition of downlink control signals / channels, the base station can transmit each downlink control signal / channel of the multiple DCI / PDCCHs via the corresponding search space set of the multiple search space sets / in those corresponding search space sets. For example, in Figures 24 to 26 In this configuration, the base station transmits a first downlink control signal / channel via a first core set. The base station may transmit the first downlink control signal / channel via one or more first search space sets associated with the first core set. The base station transmits a second downlink control signal / channel via a second core set. The base station may transmit the second downlink control signal / channel via one or more second search space sets associated with the second core set.

[0325] For multiple DCI / PDCCHs, a wireless device can monitor one or more core sets for the repetition of downlink control signals / channels. For each downlink control signal / channel in the multiple DCI / PDCCHs, the wireless device can monitor the corresponding core set in one or more core sets. For multiple DCI / PDCCHs, monitoring one or more core sets for the repetition of downlink control signals / channels can include monitoring one or more core sets for the repetition of downlink control signals / channels. For multiple DCI / PDCCHs, monitoring one or more core sets for the repetition of downlink control signals / channels can include monitoring one or more core sets for the repetition of downlink control signals / channels. For multiple DCI / PDCCHs, a wireless device can monitor multiple search space sets associated with one or more core sets for the repetition of downlink control signals / channels. For each downlink control signal / channel in the multiple DCI / PDCCHs, the wireless device can monitor the corresponding search space set in multiple search space sets for the repetition of downlink control signals / channels. For example, in Figures 24 to 26 In this context, the wireless device can monitor a first core set for a first downlink control signal / channel. The wireless device can also monitor one or more first search space sets associated with the first core set for the first downlink control signal / channel. The wireless device can monitor a second core set for a second downlink control signal / channel. The wireless device can monitor one or more second search space sets associated with the second core set for the second downlink control signal / channel.

[0326] In the example, the wireless device can determine multiple downlink control signal / channel transmission / repetition timings (e.g., PDCCH transmission / repetition / monitoring timings) that repeat on the control channel. The wireless device can determine multiple downlink control signal / channel transmission / repetition timings that repeat on the downlink control signal / channel. The base station can cross multiple downlink control signal / channel transmission / repetition timings (e.g., via one or more core sets) Figures 24 to 26The PDCCH transmission / repetition timing 1 and PDCCH transmission / repetition timing 2) refers to the transmission of multiple DCI / PDCCHs within the multiple downlink control signal / channel transmission / repetition timings, on the multiple downlink control signal / channel transmission / repetition timings, and during the multiple downlink control signal / channel transmission / repetition timings. A base station can transmit downlink control signals / channels across multiple downlink control signal / channel transmission / repetition timings via one or more core sets. A base station can also transmit downlink control signals / channels across the corresponding downlink control signal / channel transmission / repetition timings within the corresponding downlink control signal / channel transmission / repetition timings via each core set within one or more core sets. A base station can repeat the transmission of downlink control signals / channels across multiple downlink control signal / channel transmission / repetition times, within multiple downlink control signal / channel transmission / repetition times, on multiple downlink control signal / channel transmission / repetition times, or during multiple downlink control signal / channel transmission / repetition times. For example, in Figures 24 to 26 In this context, multiple downlink control signal / channel transmission / repetition timings include a first downlink control signal / channel transmission / repetition timing (e.g., PDCCH transmission / repetition timing 1) and a second downlink control signal / channel transmission / repetition timing (e.g., PDCCH transmission / repetition timing 2). The base station can transmit the first downlink control signal / channel during the first downlink control signal / channel transmission / repetition timing via a first core set. The base station can transmit the second downlink control signal / channel during the second downlink control signal / channel transmission / repetition timing via a second core set.

[0327] A wireless device can monitor one or more core sets for multiple DCI / PDCCHs across multiple downlink control signals / channel transmissions / repetitions, within multiple downlink control signals / channel transmissions / repetitions, on multiple downlink control signals / channel transmissions / repetitions, and during multiple downlink control signals / channel transmissions / repetitions. A wireless device can monitor one or more core sets for downlink control signals / channels across multiple downlink control signals / channel transmissions / repetitions, within multiple downlink control signals / channel transmissions / repetitions, on multiple downlink control signals / channel transmissions / repetitions, and during multiple downlink control signals / channel transmissions / repetitions. A wireless device can monitor each core set within one or more core sets for downlink control signals / channels across multiple downlink control signals / channel transmissions / repetitions, within that corresponding downlink control signal / channel transmission / repetition, on that corresponding downlink control signal / channel transmission / repetition, and during that corresponding downlink control signal / channel transmission / repetition. Wireless devices can monitor one or more core sets for the repetition of downlink control signals / channels across multiple downlink control signal / channel transmissions / repetition times, within multiple downlink control signal / channel transmissions / repetition times, on multiple downlink control signal / channel transmissions / repetition times, or during multiple downlink control signal / channel transmissions / repetition times. For example, in Figures 24 to 26 In this context, the wireless device monitors the first core set for the first downlink control signal / channel during its transmission / repetition. The wireless device also monitors the second core set for the second downlink control signal / channel during its transmission / repetition.

[0328] A wireless device can monitor one or more core sets across multiple downlink control signals / channel transmissions / repetitions, within multiple downlink control signals / channel transmissions / repetitions, on multiple downlink control signals / channel transmissions / repetitions, and during multiple downlink control signals / channel transmissions / repetitions. Specifically, a wireless device can monitor each core set within one or more core sets across multiple downlink control signals / channel transmissions / repetitions. For example, a wireless device can monitor a first core set for downlink control signals / channels across one or more first downlink control signals / channel transmissions / repetitions across multiple downlink control signals / channel transmissions / repetitions, within one or more first downlink control signals / channel transmissions / repetitions, on one or more first downlink control signals / channel transmissions / repetitions, and during one or more first downlink control signals / channel transmissions / repetitions. A wireless device can monitor a second core set for downlink control signals / channels across one or more second downlink control signal / channel transmission / repetition times, within one or more second downlink control signal / channel transmission / repetition times, on one or more second downlink control signal / channel transmission / repetition times, or during one or more second downlink control signal / channel transmission / repetition times. One or more first downlink control signal / channel transmission / repetition times may include first downlink control signal / channel transmission / repetition times. One or more second downlink control signal / channel transmission / repetition times may include second downlink control signal / channel transmission / repetition times.

[0329] A base station can transmit downlink control signals / channels via each core set in one or more core sets across multiple downlink control signal / channel transmission / repetition times, within each of those corresponding downlink control signal / channel transmission / repetition times, on each of those corresponding downlink control signal / channel transmission / repetition times, or during each of those corresponding downlink control signal / channel transmission / repetition times. For example, a base station can transmit downlink control signals / channels via a first core set across one or more first downlink control signal / channel transmission / repetition times, within one or more first downlink control signal / channel transmission / repetition times, on each of those one or more first downlink control signal / channel transmission / repetition times, or during each of those one or more first downlink control signal / channel transmission / repetition times. Similarly, a base station can transmit downlink control signals / channels via a second core set across one or more second downlink control signal / channel transmission / repetition times, within one or more second downlink control signal / channel transmission / repetition times, on each of those one or more second downlink control signal / channel transmission / repetition times, or during each of those one or more second downlink control signal / channel transmission / repetition times.

[0330] In the example, the repetition of downlink control signals / channels (or the transmission of multiple DCI / PDCCHs) can occur, for example, within a time unit (e.g., by TDM). For example, time units can be consecutive. For example, time units can be non-consecutive. The number of time units can equal the number of repetitions. For example, a time unit can be a time slot. For example, a time unit can be a micro-slot. For example, a time unit can be a time symbol (e.g., an OFDM symbol). For example, a time unit can be a subframe. For example, a time unit can be a timing monitoring opportunity (e.g., a PDCCH monitoring opportunity). The number of multiple downlink control signal / channel transmission opportunities can equal the number of repetitions. Multiple downlink control signal / channel transmission opportunities can occur within a time unit. For example, the first downlink control signal / channel transmission opportunity among multiple downlink control signal / channel transmission opportunities can occur within the first time unit of a time unit. The second downlink control signal / channel transmission opportunity among multiple downlink control signal / channel transmission opportunities can occur within the second time unit of a time unit, and so on.

[0331] In the example, the repetition of downlink control signals / channels (or the transmission of multiple DCI / PDCCHs) can occur, for example, within a frequency cell (by FDM). The number of frequency cells can be equal to the number of repetitions. For example, a frequency cell can be a frequency band. For example, a frequency cell can be a physical resource block (PRB). For example, a frequency cell can be a resource element group (REG). For example, a frequency cell can be a REG bundle. A frequency cell can be, for example, a control element (CE). For example, a frequency cell can be a BWP. For example, a frequency cell can be a cell. The number of multiple downlink control signal / channel transmission opportunities can be equal to the number of repetitions. Multiple downlink control signal / channel transmission opportunities can be within a frequency cell. For example, the first downlink control signal / channel transmission opportunity in multiple downlink control signal / channel transmission opportunities can be within a first frequency cell within a frequency cell. The second downlink control signal / channel transmission opportunity in multiple downlink control signal / channel transmission opportunities can be within a second frequency cell within a frequency cell, and so on.

[0332] A base station can transmit multiple DCI / PDCCHs across time units / within a time unit / within a time unit. A base station can transmit multiple DCI / PDCCHs across frequency units / within a frequency unit / within a frequency unit. A base station can repeat the transmission of downlink control signals / channels across multiple uplink signal / channel transmission opportunities / within multiple uplink signal / channel transmission opportunities. A base station can transmit downlink control signals / channels in repetitions. For example, in... Figures 24 to 26In this context, multiple downlink control signal / channel transmission opportunities include a first downlink control signal / channel transmission opportunity (first TX opportunity) and a second downlink control signal / channel transmission opportunity (second TX opportunity). The first downlink control signal / channel transmission opportunity can occur in a first time unit within a time unit (e.g., a first timeslot, a first symbol, a first subframe, or a first PDCCH monitoring opportunity). The second downlink control signal / channel transmission opportunity can occur in a second time unit within a time unit (e.g., a second timeslot, a second symbol, a second subframe, or a second PDCCH monitoring opportunity). The first downlink control signal / channel transmission opportunity can also occur in a first frequency unit within a frequency unit (e.g., a first PRB, a first cell, a first frequency, a first BWP, a first subband, a first REG bundle, or a first CE). The second downlink control signal / channel transmission opportunity can occur in a second frequency unit within a frequency unit (e.g., a second PRB, a second cell, a second frequency, a second BWP, a second subband, a second REG bundle, or a second CE).

[0333] In the example, one or more configuration parameters can indicate the repetition scheme for control channel repetition (e.g., via higher-level parameters RepetitionSchemeConfig, FDM scheme, TDM scheme, SDM scheme, CDM scheme).

[0334] 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.

[0335] In the example, the wireless device can monitor one or more core sets for multiple DCI / PDCCHs across multiple downlink control signals / channel transmission times / within multiple downlink control signals / channel transmission times / in multiple downlink control signals / channel transmission times based on one or more configuration parameters indicating the repetition scheme.

[0336] In the example, the repetition scheme can be a time-domain repetition scheme (e.g., TDM scheme, intra-slot repetition, inter-slot repetition, TDMSchemeA, TDMSchemeB, etc.). In a time-domain repetition scheme, multiple downlink control signal / channel transmission opportunities (e.g., a first TX opportunity and a second TX opportunity) may not overlap in time. In a time-domain repetition scheme, multiple downlink control signal / channel transmission opportunities may or may not overlap in frequency. Each of the multiple downlink control signal / channel transmission opportunities may have a non-overlapping time-domain resource allocation relative to the other signals / channel transmission opportunities in the multiple downlink control signal / channel transmission opportunities. For example, a first downlink control signal / channel transmission opportunity in the multiple downlink control signal / channel transmission opportunities may not overlap in time with a second downlink control signal / channel transmission opportunity in the multiple downlink control signal / channel transmission opportunities. The first downlink control signal / channel transmission opportunity and the second downlink control signal / channel transmission opportunity may be different. For example, in a time-domain repetition scheme, the first downlink control signal / channel transmission timing (first TX timing) and the second downlink control signal / channel transmission timing (second TX timing) may not overlap in time. Multiple downlink control signal / channel transmission timings can occur in different time units. For example, the first time unit and the second time unit may not overlap in time. The first time unit and the second time unit may be different.

[0337] In the example, the repetition scheme can be a frequency domain repetition scheme (e.g., FDM scheme, FDMSchemeA, FDMSchemeB, etc.). In a frequency domain repetition scheme, multiple downlink control signal / channel transmission opportunities may or may not overlap in time. In a frequency domain repetition scheme, multiple downlink control signal / channel transmission opportunities may not overlap in frequency. Each of the multiple downlink control signal / channel transmission opportunities may have a non-overlapping frequency domain resource allocation relative to the other signals / channel transmission opportunities in the multiple downlink control signal / channel transmission opportunities. For example, a first downlink control signal / channel transmission opportunity in the multiple downlink control signal / channel transmission opportunities may not overlap in frequency with a second downlink control signal / channel transmission opportunity in the multiple downlink control signal / channel transmission opportunities. The first downlink control signal / channel transmission opportunity and the second downlink control signal / channel transmission opportunity may be different. For example, in a frequency domain repetition scheme, the first downlink control signal / channel transmission opportunity (first TX opportunity) and the second downlink control signal / channel transmission opportunity (second TX opportunity) may not overlap in frequency. The first downlink control signal / channel transmission timing (first TX timing) and the second downlink control signal / channel transmission timing (second TX timing) can overlap in time. Multiple downlink control signal / channel transmission timings can occur in different frequency units (e.g., frequency, REG, CE, PRB, frequency band, bandwidth portion, cell). For example, the first frequency unit of the first downlink control signal / channel transmission timing and the second frequency unit of the second downlink control signal / channel transmission timing may not overlap in frequency. The first frequency unit and the second frequency unit can be different.

[0338] In the examples, the repetition scheme can be a spatial domain / code domain repetition scheme (e.g., SFN scheme, SDM scheme, CDM scheme, SDMScheme, CDMScheme, etc.). In a spatial domain / code domain repetition scheme, multiple downlink control signal / channel transmission opportunities can overlap in time. In a spatial domain / code domain repetition scheme, multiple downlink control signal / channel transmission opportunities can overlap in frequency. In a spatial / code domain repetition scheme, multiple downlink control signal / channel transmission opportunities can be a single downlink control signal / channel transmission opportunity. Each of the multiple downlink control signal / channel transmission opportunities can have overlapping frequency domain resource allocations relative to other downlink control signal / channel transmission opportunities. Each of the multiple downlink control signal / channel transmission opportunities can have non-overlapping time domain resource allocations relative to other downlink control signal / channel transmission opportunities. Each of the multiple downlink control signal / channel transmission opportunities can be identical. For example, a first downlink control signal / channel transmission timing among multiple downlink control signal / channel transmission timings can overlap in time and frequency with a second downlink control signal / channel transmission timing among multiple downlink control signal / channel transmission timings. The first downlink control signal / channel transmission timing and the second downlink control signal / channel transmission timing can be the same. For example, in a spatial domain / code domain repetition scheme, the first downlink control signal / channel transmission timing (first TX timing) and the second downlink control signal / channel transmission timing (second TX timing) can overlap in frequency. The first downlink control signal / channel transmission timing (first TX timing) and the second downlink control signal / channel transmission timing (second TX timing) can overlap in time. Multiple downlink control signal / channel transmission timings can occur in the same frequency unit (e.g., frequency, PRB, frequency band, bandwidth portion, sub-band, cell, REG, REG bundle, CE). For example, the first frequency unit of the first downlink control signal / channel transmission timing and the second frequency unit of the second downlink control signal / channel transmission timing can overlap in frequency. The first frequency unit and the second frequency unit can be the same. Multiple downlink control signal / channel transmission opportunities can occur within the same time unit (e.g., symbol, micro-slot, time slot, subframe, PDCCH monitoring opportunity, etc.). For example, the first time unit of the first downlink control signal / channel transmission opportunity and the second time unit of the second downlink control signal / channel transmission opportunity can overlap in time. The first time unit and the second time unit can be the same.

[0339] For example, in a time-domain repetition scheme, the downlink control signal / channel transmission timings among multiple downlink control signal / channel transmission timings can have non-overlapping time-domain resource allocations relative to another downlink control signal / channel transmission timing. Similarly, in a frequency-domain repetition scheme, the downlink control signal / channel transmission timings among multiple downlink control signal / channel transmission timings can have non-overlapping frequency-domain resource allocations relative to another downlink control signal / channel transmission timing. Finally, in a spatial / code-domain repetition scheme, the downlink control signal / channel transmission timings among multiple downlink control signal / channel transmission timings can have overlapping time-domain and frequency-domain resource allocations relative to another downlink control signal / channel transmission timing.

[0340] In the example, multiple DCI / PDCCHs can be associated with (or linked to) multiple downlink control signal / channel transmission times. Each downlink control signal / channel of the multiple DCI / PDCCHs can be associated with a corresponding downlink control signal / channel transmission time among the multiple downlink control signal / channel transmission times. The base station can transmit each downlink control signal / channel of the multiple DCI / PDCCHs within / via the corresponding downlink control signal / channel transmission time among the multiple downlink control signal / channel transmission times. The wireless device can monitor each downlink control signal / channel of the multiple DCI / PDCCHs within / via the corresponding downlink control signal / channel transmission time among the multiple downlink control signal / channel transmission times. For example, in Figures 24 to 26 In this context, a first downlink control signal / channel (e.g., DCI 1) is associated with a first downlink control signal / channel transmitted by a base station or monitored by a radio device during / via the first downlink control signal / channel transmission / repetition timing (e.g., PDCCH transmission / repetition timing 1). A second downlink control signal / channel (e.g., DCI 2) is associated with a second downlink control signal / channel transmitted by a base station or monitored by a radio device during / via the second downlink control signal / channel transmission / repetition timing (e.g., PDCCH transmission / repetition timing 2).

[0341] Wireless devices can receive / detect at least one downlink control signal / channel from multiple DCI / PDCCH (or from repetitions of downlink control signals / channels). For example, in Figures 24 to 26 In this scenario, the wireless device detects / receives DCI1. The wireless device does not receive / detect DCI2. At least one downlink control signal / channel is DCI1. The wireless device receives DCI1 during the first downlink control signal / channel transmission. The wireless device does not receive / detect DCI2 during the second downlink control signal / channel transmission.

[0342] A wireless device can receive a downlink control signal / channel during at least one downlink control signal / channel transmission / repetition timing among a plurality of downlink control signal / channel transmission / repetition timings. The wireless device can receive each downlink control signal / channel during the corresponding downlink control signal / channel transmission / repetition timing of at least one downlink control signal / channel. For example, in Figures 24 to 26 In this example, at least one downlink control signal / channel transmission / repetition timing is a second downlink control signal / channel transmission timing. In the example, each downlink control signal / channel in at least one downlink control signal / channel can be the same as the given downlink control signal / channel.

[0343] Wireless devices can receive / detect downlink control signals / channels based on receiving / detecting at least one downlink control signal / channel among multiple DCI / PDCCHs.

[0344] In the example, at least one downlink control signal / channel (or downlink control signal / channel) may indicate the number of repetitions. At least one downlink control signal / channel may include a DCI indicating the number of repetitions.

[0345] In the example, the wireless device can receive at least one downlink control signal / channel (or downlink control signal / channel) via at least one core set from one or more core sets. The wireless device can receive each of the at least one downlink control signal / channel via a corresponding core set from the at least one core set. For example, in Figures 24 to 26 In this context, at least one core set is the first core set.

[0346] A wireless device can determine a reference downlink control signal / channel transmission timing among multiple downlink control signal / channel transmission timings. The wireless device can determine the reference downlink control signal / channel transmission timing, for example, based on receiving / detecting at least one downlink control signal / channel. The wireless device can determine the reference downlink control signal / channel transmission timing, for example, based on receiving / detecting a downlink control signal / channel. The wireless device can determine the reference downlink control signal / channel transmission timing, for example, based on one or more configuration parameters indicating control channel repetition.

[0347] A wireless device may receive / detect at least one downlink control signal / channel during / via / at least one downlink control signal / channel transmission timing among a plurality of downlink control signal / channel transmission timings. At least one downlink control signal / channel transmission timing may or may not include a reference downlink control signal / channel transmission timing. Figures 24 to 26 In this context, at least one downlink control signal / channel transmission timing is the first downlink control signal / channel transmission timing. A reference downlink control signal / channel transmission timing can be the second downlink control signal / channel transmission timing.

[0348] In the example, determining a reference downlink control signal / channel transmission timing among multiple downlink control signal / channel transmission timings may, for example, be based on multiple DCI / PDCCHs associated with the multiple downlink control signal / channel transmission timings to determine a reference downlink control signal / channel among the multiple DCI / PDCCHs. For example, in Figures 24 to 26 In this context, when the first downlink control signal / channel transmission / repetition timing is the reference downlink control signal / channel transmission timing, the first downlink control signal / channel (e.g., DCI 1) is the reference downlink control signal / channel. When the second downlink control signal / channel transmission / repetition timing is the reference downlink control signal / channel transmission timing, the second downlink control signal / channel (e.g., DCI 2) is the reference downlink control signal / channel.

[0349] In the example, the wireless device can determine a reference downlink control signal / channel transmission timing based on the number of repetitions and the initial downlink control signal / channel transmission timing (or initial time slot) among multiple downlink control signal / channel transmission timings. For example, one or more configuration parameters can indicate the start of the downlink control signal / channel transmission timing. At least one downlink control signal / channel can, for example, indicate the start of the downlink control signal / channel transmission timing. For example, in... Figures 24 to 26In this context, when the start of downlink control signal / channel transmission is the first downlink control signal / channel transmission timing and the repetition count is equal to two, the reference downlink control signal / channel transmission timing can be the second downlink control signal / channel transmission timing. When the start of downlink control signal / channel transmission is the first downlink control signal / channel transmission timing and the repetition count is equal to three, the reference downlink control signal / channel transmission timing can be the third downlink control signal / channel transmission timing among multiple downlink control signal / channel transmission timings. When the start of downlink control signal / channel transmission is the second downlink control signal / channel transmission timing and the repetition count is equal to two, the reference downlink control signal / channel transmission timing can be the third downlink control signal / channel transmission timing.

[0350] In the example, the reference downlink control signal / channel transmission timing can be the last (latest or end) downlink control signal / channel transmission timing among multiple downlink control signal / channel transmission timings.

[0351] The wireless device monitors the first core set during the transmission of the first downlink control signal / channel in a first time unit (e.g., the first time slot, the first time symbol, the first subframe, etc.). The wireless device monitors the second core set during the transmission / repetition of the second downlink control signal / channel in a second time unit.

[0352] The last downlink control signal / channel transmission timing may, for example, have the latest start time among multiple downlink control signal / channel transmission timing start times. The second time unit may begin later than the first time unit. The first / start symbol of the second time unit may appear after (or later than) the first / start symbol of the second time unit. The second downlink control signal / channel transmission timing may be based on a reference downlink control signal / channel transmission timing of a second time unit that begins later than the first time unit.

[0353] The last downlink control signal / channel transmission timing may, for example, have the latest end time among multiple downlink control signal / channel transmission timings. The second time unit may end later than the first time unit. The last symbol of the second time unit may appear after (or later than) the last symbol of the first time unit. The second downlink control signal / channel transmission timing may be a reference downlink control signal / channel transmission timing based on a second time unit that ends later than the first time unit.

[0354] The timing of the last downlink control signal / channel transmission can be associated with the last downlink control signal / channel among multiple DCI / PDCCHs. The base station can transmit the last downlink control signal / channel during / via the last downlink control signal / channel transmission timing. The radio device can monitor for the last downlink control signal / channel during / via the last downlink control signal / channel transmission timing. The last downlink control signal / channel can be a reference downlink control signal / channel. The base station can transmit the last repetition of the downlink control signal / channel during the last downlink control signal / channel transmission timing. The radio device can monitor for the last repetition of the downlink control signal / channel during the last downlink control signal / channel transmission timing. The last repetition of the downlink control signal / channel can be the last downlink control signal / channel.

[0355] For example, in Figures 24 to 26 In this context, the last downlink control signal / channel transmission timing is the second downlink control signal / channel transmission timing (e.g., PDCCH transmission / repetition timing 2). The reference downlink control signal / channel transmission timing is the second (or last) downlink control signal / channel transmission timing.

[0356] In the example, the reference downlink control signal / channel transmission timing can be the earliest (or first or initial) downlink control signal / channel transmission timing among multiple downlink control signal / channel transmission timings.

[0357] The earliest (or first or starting) reference downlink control signal / channel transmission timing can, for example, have the earliest start time among multiple downlink control signal / channel transmission timing start times. For example, a first time unit may begin earlier than a second time unit. The first / start symbol of the first time unit may appear before (or earlier than) the first / start symbol of the second time unit. The first downlink control signal / channel transmission timing can be a reference downlink control signal / channel transmission timing based on a first time unit that begins earlier than the second time unit.

[0358] The earliest (or first or initial) reference downlink control signal / channel transmission timing can, for example, have the earliest end time among multiple downlink control signal / channel transmission timing end times. For example, a first time unit may end earlier than a second time unit. The last symbol of the first time unit may appear before (or earlier than) the last symbol of the second time unit. The first downlink control signal / channel transmission timing can be a reference downlink control signal / channel transmission timing based on a first time unit that ends earlier than the second time unit.

[0359] The earliest (or first or initial) downlink control signal / channel transmission timing can be associated with the first / initial downlink control signal / channel among multiple DCI / PDCCHs. The base station can transmit the first / initial downlink control signal / channel during / via the earliest downlink control signal / channel transmission timing. The radio device can monitor for the first / initial downlink control signal / channel during / via the earliest downlink control signal / channel transmission timing. The first / initial downlink control signal / channel can be a reference downlink control signal / channel. The base station can transmit the first / initial repetition of the downlink control signal / channel during the earliest downlink control signal / channel transmission timing. The radio device can monitor for the first / initial repetition of the downlink control signal / channel during the earliest downlink control signal / channel transmission timing. The first / initial repetition of the downlink control signal / channel can be the first / initial downlink control signal / channel.

[0360] For example, in Figures 24 to 26 In this context, the earliest (or first or initial) downlink control signal / channel transmission timing is the first downlink control signal / channel transmission timing (e.g., PDCCH transmission / repetition timing 1). The reference downlink control signal / channel transmission timing is the first (or earliest / first / initial) downlink control signal / channel transmission timing.

[0361] In the example, the reference downlink control signal / channel transmission timing can be associated with a core set in one or more core sets. The wireless device can monitor the core set during the reference downlink control signal / channel transmission timing for downlink control signals / channels. The wireless device can monitor the core set during the reference downlink control signal / channel transmission timing for DCI (or downlink control signal / channel). One or more configuration parameters can indicate the reference downlink control signal / channel transmission timing for the core set. The wireless device can determine the reference downlink control signal / channel transmission timing based on receiving one or more configuration parameters.

[0362] In the example, the core set can be identified / indicated by the core set index among one or more core set indexes. In the example, the core set index can be the lowest (or highest) of one or more core set indexes. The core set can be identified / indicated by the lowest (or highest) core set index among one or more core set indexes.

[0363] A wireless device can determine / select a core set with the lowest (or highest) core set index among one or more core set indices. For example, a wireless device can monitor a core set for a DCI across multiple downlink control signal / channel transmission times. The downlink control signal / channel transmission time can be a reference downlink control signal / channel transmission time. For example, a wireless device can monitor a core set for a DCI across one or more downlink control signal / channel transmission times. The last / latest / earliest / first / starting downlink control signal / channel transmission time among one or more downlink control signal / channel transmission times can be a reference downlink control signal / channel transmission time. The wireless device can determine the reference downlink control signal / channel transmission time based on the core set.

[0364] The reference downlink control signal / channel transmission timing can be associated with reference downlink control signals / channels in multiple DCI / PDCCHs. The base station can transmit reference downlink control signals / channels during / via the reference downlink control signal / channel transmission timing. The radio device can monitor the core set for reference downlink control signals / channels during / via the reference downlink control signal / channel transmission timing.

[0365] In the example, the wireless device can monitor a search space set from multiple search space sets for a reference downlink control signal / channel transmission timing (e.g., PDCCH monitoring timing). The reference downlink control signal / channel transmission timing can be associated with a search space set. The wireless device can monitor the search space set for a reference downlink control signal / channel transmission timing for a DCI (or downlink control signal / channel). One or more configuration parameters can indicate the reference downlink control signal / channel transmission timing for the search space set. The wireless device can determine the reference downlink control signal / channel transmission timing based on receiving one or more configuration parameters.

[0366] In the example, the search space set can be identified / indicated by the search space set index within the search space set index. In the example, the search space set index can be the lowest (or highest) of the search space set indexes. The search space set can be identified / indicated by the lowest (or highest) search space set index.

[0367] A wireless device can determine / select a search space set that has the lowest (or highest) search space set index among multiple search space set indices. For example, a wireless device can monitor a search space set for a DCI in the downlink control signal / channel transmission timing. The downlink control signal / channel transmission timing can be a reference downlink control signal / channel transmission timing. For example, a wireless device can monitor a search space set for a DCI in one or more downlink control signal / channel transmission timings. The last / latest / earliest / first / starting downlink control signal / channel transmission timing among one or more downlink control signal / channel transmission timings can be a reference downlink control signal / channel transmission timing. The wireless device can determine the reference downlink control signal / channel transmission timing based on the search space set.

[0368] The reference downlink control signal / channel transmission timing can be associated with reference downlink control signals / channels in multiple DCI / PDCCHs. The base station can transmit reference downlink control signals / channels during / via the reference downlink control signal / channel transmission timing. The radio device can monitor the search space for reference downlink control signals / channels during / via the reference downlink control signal / channel transmission timing.

[0369] In the example, the wireless device may determine the timing of a reference downlink control signal / channel transmission based on receiving at least one downlink control signal / channel (or downlink control signal / channel) via at least one core set in one or more core sets.

[0370] The wireless device can determine the timing of reference downlink control signal / channel transmission based on a repetition scheme that serves as the first repetition scheme. For example, the first repetition scheme could be a time-domain repetition scheme (e.g., TDM).

[0371] For example, the first repetition scheme can be a frequency domain repetition scheme (e.g., FDM). Alternatively, the first repetition scheme can be a spatial / code domain repetition scheme (e.g., SFN, SDM).

[0372] Wireless devices can determine the timing of reference downlink control signal / channel transmission based on a repetition scheme that is not the second repetition scheme. For example, the second repetition scheme could be a frequency domain repetition scheme (e.g., FDM). Alternatively, the second repetition scheme could be a spatial / code domain repetition scheme (e.g., SFN, SDM).

[0373] For example, the second repetition scheme could be a time-domain repetition scheme (e.g., TDM).

[0374] At least one downlink control signal / channel (or downlink control signal / channel) can schedule transport blocks (e.g., Figure 24 (Transport blocks in the process). Each downlink control signal / channel in at least one downlink control signal / channel can schedule a transport block. Scheduling at least one downlink control signal / channel of a transport block may include scheduling the downlink control signal / channel of the transport block.

[0375] For example, a transport block can be a PDSCH. For example, a transport block can be a reference signal (e.g., CSI-RS, SS / PBCH block).

[0376] In the example, the wireless device can determine the timing of reference downlink control signals / channel transmissions for receiving transport blocks.

[0377] At least one downlink control signal / channel (or downlink control signal / channel) can be in DCI format. For example, the DCI format can be DCI format 1-0. For example, the DCI format can be DCI format 1-1. For example, the DCI format can be DCI format 1-2. For example, the DCI format can be DCI format 1-x, where x = 0, 1, 2, 3, 4, ...

[0378] One or more configuration parameters can indicate the RNTI. The CRC of the downlink control signal / channel (or DCI format) can be scrambled using the RNTI. For example, the RNTI could be C-RNTI. For example, the RNTI could be CS-RNTI. For example, the RNTI could be MCS-C-RNTI.

[0379] Wireless devices can determine the start symbol (e.g., for the reception of a transport block) based on a reference to downlink control signals / channel transmission timing. Figure 24 (The start symbol in the reference downlink control signal / channel transmission timing). For example, a wireless device may determine the start symbol based on a reference PDCCH monitoring timing within a reference downlink control signal / channel transmission timing. The wireless device may monitor the downlink control signal / channel within one or more PDCCH monitoring timings in the reference downlink control signal / channel transmission timing. One or more PDCCH monitoring timings may include the reference PDCCH monitoring timing.

[0380] For example, a wireless device may determine the start symbol based on a reference PDCCH monitoring timing in response to one or more configuration parameters indicating control channel repetition.

[0381] Wireless devices may or may not receive downlink control signals / channels during reference PDCCH monitoring.

[0382] In the example, the reference PDCCH monitoring time can be the last (latest or end) PDCCH monitoring time among one or more PDCCH monitoring times. For example, the last PDCCH monitoring time can have the latest start time among one or more start times of one or more PDCCH monitoring times. For example, the last PDCCH monitoring time can have the latest end time among one or more end times of one or more PDCCH monitoring times.

[0383] In the example, the reference PDCCH monitoring time can be the first (or earliest or starting) PDCCH monitoring time among one or more PDCCH monitoring times. For example, the first (or earliest or starting) PDCCH monitoring time can have the earliest start time among one or more start times of one or more PDCCH monitoring times. For example, the first (or earliest or starting) PDCCH monitoring time can have the earliest end time among one or more end times of one or more PDCCH monitoring times.

[0384] Wireless devices can receive transport blocks. For example, a wireless device can receive transport blocks via the cell's active downlink BWP or on that active downlink BWP. A wireless device can receive transport blocks based on a start symbol.

[0385] For example, a wireless device may receive a transport block starting with a start symbol. The start symbol may be the first / earliest / start symbol of the transport block. A transport block may include one or more symbols (e.g., OFDM symbols). One or more symbols may include the first / earliest / start symbol.

[0386] For example, a wireless device can receive a transport block after the start symbol. The first / earliest / start symbol of the transport block can appear after the start symbol.

[0387] In the example, one or more configuration parameters may indicate / include the higher-layer parameter ReferenceofSLIV-ForDCIFormat1_2 in the PDSCH-Config. The higher-layer parameter ReferenceofSLIV-ForDCIFormat1_2 can be (or set to) enabled. For example, the higher-layer parameter ReferenceofSLIV-ForDCIFormat1_2 may enable the use of the start / earliest / first symbol of the PDCCH monitoring timing as a reference value for the SLIV used for DCI format 1_2. The wireless device can receive downlink assignments (e.g., downlink grants) during the PDCCH monitoring timing.

[0388] At least one downlink control signal / channel (or downlink control signal / channel) may include a Time Domain Resource Assignment (TDRA) field. Each downlink control signal / channel in the at least one downlink control signal / channel may include a TDRA field. The value of the TDRA field may indicate a row in the Time Domain Resource Assignment table. This row may indicate / define, for example, a slot offset (e.g., K0). This row may indicate / define, for example, a Start and Length Indication (SLIV). SLIV may indicate a start symbol (e.g., S). SLIV may indicate an assigned length (e.g., L). This row may indicate / define, for example, a PDSCH mapping type (e.g., Type A, Type B).

[0389] A wireless device can determine a receive time slot for receiving a transport block. The wireless device can determine the receive time slot, for example, based on a time slot offset. The wireless device can determine the receive time slot, for example, based on the subcarrier spacing of the downlink BWP of the received transport block. The wireless device can determine the receive time slot, for example, based on the subcarrier spacing of the downlink BWP of one or more core sets (or at least one downlink control signal / channel) detected by the wireless device. The wireless device can determine the receive time slot, for example, based on a reference to the transmission / repetition timing of the downlink control signal / channel. The wireless device can receive the transport block within the receive time slot.

[0390] In the example, the PDSCH mapping type can be PDSCH mapping type B.

[0391] In the example, the time slot offset can be equal to zero (e.g., K0 = 0).

[0392] In the example, the length / size of the transport block can be equal to the allocation length. The number of one or more symbols in the transport block can also be equal to the allocation length.

[0393] In the example, the start symbol (e.g., Figure 24 The start symbol in the reference PDCCH can be relative to the reference start symbol of the timing of the PDCCH monitoring (e.g., Figure 24 The reference start symbol (S0) can be, for example, the first / start / earliest symbol of the PDCCH monitoring timing. The reference start symbol can also be, for example, the last / end / latest symbol of the PDCCH monitoring timing. In the example, the start symbol (e.g., Figure 24 The start symbol in the reference downlink control signal / channel transmission timing can be relative to the reference start symbol (e.g., Figure 24 The reference start symbol (S0) can be the first / start / earliest symbol of the reference downlink control signal / channel transmission timing. Alternatively, the reference start symbol can be, for example, the last / end / latest symbol of the reference downlink control signal / channel transmission timing.

[0394] A wireless device may determine the start symbol, for example, based on a reference start symbol. The start symbol may be equal to, for example, the reference start symbol plus the start symbol. For example, when the reference start symbol is symbol n and the start symbol is three, the start symbol is equal to symbol n+3. When the reference start symbol is symbol n and the start symbol is five, the start symbol is equal to symbol n+5. The start symbol may also be equal to, for example, the reference start symbol plus the start symbol minus 1. For example, when the reference start symbol is symbol n and the start symbol is three, the start symbol is equal to symbol n+2. When the reference start symbol is symbol n and the start symbol is five, the start symbol is equal to symbol n+4.

[0395] In the example, one or more configuration parameters may not indicate control channel repetition. The wireless device may receive / detect the DCI (e.g., DCI 1-2) of the scheduled transport block (e.g., PDSCH) during PDCCH monitoring.

[0396] The CRC of DCI can be scrambled using RNTI. For example, RNTI could be C-RNTI, CS-RNTI, or MCS-RNTI.

[0397] The DCI may include a TDRA field indicating the start symbol (e.g., S). The TDRA field may indicate PDSCH mapping type B. The TDRA field may indicate a slot offset equal to zero.

[0398] The start symbol can be a reference start symbol relative to the timing of the PDCCH monitoring of the DCI received by the wireless device. The wireless device can determine the start symbol for the reception of a transport block based on this reference start symbol at the time of the PDCCH monitoring of the DCI received by the wireless device. The reference start symbol can be, for example, the first / starting / earliest symbol of the PDCCH monitoring timing.

[0399] For example, a wireless device may determine the start symbol based on a reference start symbol at the timing of the PDCCH monitoring of the DCI, in response to one or more configuration parameters that do not indicate control channel repetition.

[0400] Wireless devices can receive transport blocks. For example, a wireless device can receive transport blocks via the cell's active downlink BWP or on that active downlink BWP. A wireless device can receive transport blocks based on a start symbol.

[0401] At least one downlink control signal / channel (or downlink control signal / channel) can schedule transport blocks (e.g., Figure 25 (TB in the context). Each downlink control signal / channel in at least one downlink control signal / channel can schedule a transport block. At least one downlink control signal / channel for scheduling a transport block may include the downlink control signal / channel for scheduling the transport block.

[0402] For example, a transport block can be a PUSCH. For example, a transport block can be a reference signal (e.g., SRS).

[0403] In the example, the wireless device can determine the timing of reference downlink control signals / channel transmissions for the transmission of transport blocks.

[0404] Wireless devices can determine symbols (e.g., based on reference downlink control signals / channel transmission timing) for the transmission of transport blocks. Figure 25 The symbol (e.g., L_2) in the reference downlink control signal / channel transmission timing. For example, the wireless device can determine the symbol based on a reference PDCCH monitoring timing within the reference downlink control signal / channel transmission timing. The wireless device can monitor the downlink control signal / channel within one or more PDCCH monitoring timings in the reference downlink control signal / channel transmission timing. One or more PDCCH monitoring timings may include the reference PDCCH monitoring timing.

[0405] Wireless devices can determine symbols, for example, based on timing advance (or the value of timing advance or the effect of timing advance).

[0406] The transmission of a transport block based on the reference downlink control signal / channel transmission timing can include the transmission of a transport block based on the reference symbol (e.g., reference downlink control signal / channel transmission timing). Figure 25 The reference symbol is used to determine the symbol. For example, the reference symbol could be the first / start / earliest symbol referring to the downlink control signal / channel transmission timing. The reference symbol could also be, for example, the last / end / latest symbol referring to the downlink control signal / channel transmission timing.

[0407] The determination of symbols for transmission of a transport block based on the reference PDCCH monitoring timing may include the reference symbols for the transport block based on the reference PDCCH monitoring timing (e.g., Figure 25 The reference symbol is used to determine the symbol. The reference symbol can be, for example, the first / starting / earliest symbol of the PDCCH monitoring time. The reference symbol can also be, for example, the last / ending / latest symbol of the PDCCH monitoring time.

[0408] For example, a wireless device may determine a symbol based on a reference PDCCH monitoring timing in response to one or more configuration parameters indicating that the control channel is repeated.

[0409] Wireless devices may or may not receive downlink control signals / channels during reference PDCCH monitoring. Base stations may transmit downlink control signals / channels during reference PDCCH monitoring.

[0410] The reference PDCCH monitoring timing can be, for example, the last (latest or end) PDCCH monitoring timing among one or more PDCCH monitoring timings. The reference PDCCH monitoring timing can also be, for example, the first (earliest or start) PDCCH monitoring timing among one or more PDCCH monitoring timings.

[0411] At least one downlink control signal / channel (or downlink control signal / channel) may include a Time Domain Resource Assignment (TDRA) field. Each downlink control signal / channel in the at least one downlink control signal / channel may include a TDRA field. The value of the TDRA field may indicate a row in the Time Domain Resource Assignment table. This row may indicate / define, for example, a time slot offset (e.g., K2). This row may indicate / define, for example, a Start and Length Indication (SLIV). The SLIV may indicate a start symbol (e.g., S). The SLIV may indicate an assigned length (e.g., L).

[0412] Wireless devices can determine the first / earliest / start symbol (or the first / earliest / starting uplink symbol) of a transport block based on the time slot offset. Wireless devices can also determine the first / earliest / starting symbol of a transport block based on the SLIV. Finally, wireless devices can determine the first / earliest / starting symbol of a transport block based on the start symbol.

[0413] Wireless devices can transmit transport blocks. Wireless devices can transmit transport blocks, for example, via the cell's active uplink BWP or on that active uplink BWP.

[0414] Wireless devices can transmit transport blocks based on symbols. A wireless device can transmit a transport block after a symbol. The first / earliest / start symbol of the transport block (e.g., Figure 25The first / start / earliest symbol in the transport block may appear after / before that symbol. A transport block may include one or more symbols (e.g., OFDM symbols). One or more symbols may include the first / earliest / start symbol. One or more symbols may include one or more DM-RS symbols for the transport block. For example, a wireless device may transmit a transport block based on the first / earliest / start symbol appearing after / before (or no earlier than) that symbol. For example, a wireless device may transmit a transport block based on the first / earliest / start symbol of the transport block, including the effect of timing advance, appearing after / before (or no earlier than) that symbol.

[0415] A wireless device can determine transmission time slots for the transmission of a transport block. The wireless device can determine transmission time slots, for example, based on time slot offsets. The wireless device can determine transmission time slots, for example, based on the subcarrier spacing of the uplink BWP for transmitting the transport block. The wireless device can determine transmission time slots, for example, based on the subcarrier spacing of the downlink BWP for which the wireless device has detected one or more core sets (or received at least one downlink control signal / channel). The wireless device can determine transmission time slots, for example, based on reference to the transmission / repetition timing of downlink control signals / channels. The wireless device can transmit the transport block within the transmission time slot.

[0416] Processing time (e.g., Figure 25 The processing time (in the context) can begin based on a reference symbol. The processing time can begin, for example, from the reference symbol or after it. The processing time can begin, for example, from the end of the reference symbol or after it. The processing time can begin, for example, from the end of a reference downlink control signal / channel transmission timing or after it. The processing time can begin from the end of a reference PDCCH monitoring timing.

[0417] Symbols (e.g., Figure 25 The symbol in the code can be the first / next / earliest symbol (or the first / next / earliest uplink symbol) appearing after / after the processing time. The symbol can be the first / next / earliest symbol appearing after the processing time from the reference symbol. The symbol can be the first / next / earliest symbol appearing after / from the reference symbol during the processing time. The symbol can be the first / next / earliest symbol appearing after / from the end of the reference PDCCH monitoring timing during the processing time. The symbol can be the first / next / earliest symbol appearing after / from the end of the reference downlink control signal / channel transmission / repetition timing during the processing time. For example, in... Figure 25In this context, processing ends at time T1. A symbol can be the first, next, or earliest symbol appearing after T1. A symbol can begin at time T2 (T2>=T1).

[0418] The cyclic prefix (CP) of the first / next / earliest symbol can begin processing after / from the reference symbol.

[0419] In the example, the processing time can be equal to T. proc,2 =max((N2+d 2,1 +d2)(2048+144)·κ2 -μ ·T C +T ext +T switch ,d 2,2 The wireless device can determine processing time, for example, based on the subcarrier spacing of the downlink BWP (e.g., μ). The wir...

Claims

1. A method comprising: transmitting, by a wireless device and for a beam failure recovery of a cell, a first uplink signal indicating a candidate reference signal; receiving, via at least one monitoring occasion of a plurality of monitoring occasions configured for physical downlink control channel, PDCCH, repetition, at least one repetition of downlink control information, DCI; and transmitting, via the cell and after a plurality of symbols of one monitoring occasion of the plurality of monitoring occasions, a second uplink signal using the candidate reference signal, wherein the one monitoring occasion has a latest ending time of ending times of the plurality of monitoring occasions.

2. The method of claim 1, further comprising completing the beam failure recovery based on receiving the at least one repetition of the DCI.

3. The method of any one of claims 1-2, wherein the plurality of symbols are from a last symbol of the one monitoring occasion.

4. The method of any one of claims 1-3, wherein the transmitting the second uplink signal comprises transmitting the second uplink signal with a spatial domain transmission filter determined based on the candidate reference signal.

5. The method of any one of claims 1-4, wherein the transmitting the second uplink signal comprises transmitting the second uplink signal with a transmission power determined based on the candidate reference signal.

6. The method of any one of claims 1-5, further comprising monitoring, after the plurality of symbols of the one monitoring occasion, one or more control resource sets, CORESETs, of the cell using the candidate reference signal.

7. The method of any one of claims 1-6, wherein the second uplink signal comprises one of: a physical uplink control channel, PUCCH; a sounding reference signal, SRS; a physical uplink shared channel, PUSCH.

8. A method comprising: receiving, by a base station from a wireless device and for a beam failure recovery of a cell, a first uplink signal indicating a candidate reference signal; transmitting, based on the beam failure recovery, physical downlink control channel, PDCCH, repetitions of downlink control information, DCI, via a plurality of monitoring occasions; and receiving, via the cell and after a plurality of symbols of one monitoring occasion of the plurality of monitoring occasions, a second uplink signal using the candidate reference signal, wherein the one monitoring occasion has a latest ending time of ending times of the plurality of monitoring occasions.

9. The method of claim 8, wherein the plurality of symbols are from a last symbol of the one monitoring occasion.

10. The method of any one of claims 8-9, wherein the first uplink signal is at least one of: a random access preamble; a scheduling request, SR; or a beam failure recovery medium access control control element, BFR MAC-CE.

11. The method of any one of claims 8-10, further comprising transmitting, after a plurality of symbols of the one monitoring occasion, a PDCCH repetition of DCI via one or more control resource sets, coresets, of the cell based on the candidate reference signal.

12. The method of claim 11, wherein the one or more coresets comprise a coreset with a coreset index equal to zero.

13. The method of any one of claims 8-12, wherein the second uplink signal comprises one of: a physical uplink control channel, PUCCH; a sounding reference signal, SRS; a physical uplink shared channel, PUSCH.

14. An apparatus, the apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1-13.

15. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform the method of any one of claims 1-13. ​ ​ ​ ​ ​ ​

Images