Method, wireless device and system for resource determination in control channel repetition

Abstract

A wireless device may receive at least one repetition of downlink control information (DCI) triggering an acknowledgement message via at least one control resource set (core set) of a core set configured for repetition of DCI. A wireless device may transmit an acknowledgement message via a physical uplink control channel (PUCCH) resource based on: an index of a starting control channel element (CCE) of the core set associated with a search space set identified by a lowest search space set index in the core set; and a number of one or more CCEs of the core set.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 088,136, filed on October 6, 2020, the entire contents of which are hereby incorporated by reference. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0005] Figure 2A and Figure 2B The New Radio (NR) user plane and control plane protocol stacks are shown separately.

[0006] Figure 3 Shown in Figure 2A Examples of services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A Shows the flow Figure 2A Example downlink data flow of the NR user plane protocol stack.

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

[0009] Figure 5A and Figure 5B The mapping between logical channels, transport channels and physical channels is shown for downlink and uplink respectively.

[0010] Figure 6 is an example diagram showing RRC state transition of a UE.

[0011] Figure 7 An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown.

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

[0013] Figure 9 An example of bandwidth adaptation using three configured BWPs for NR carriers is shown.

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

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

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

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

[0018] Figure 12A and Figure 12B Three examples of downlink and uplink beam management procedures are shown respectively.

[0019] Figure 13A 、 Figure 13B and Figure 13C A four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure are shown respectively.

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

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

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

[0023] Figure 16A 、 Figure 16B 、 Figure 16C and Figure 16D Exemplary structures for uplink and downlink transmissions are shown.

[0024] Figure 17 Exemplary configuration parameters for control and / or data according to one aspect of an embodiment of the present disclosure are shown.

[0025] Figure 18 Exemplary configuration parameters for a core set according to one aspect of an embodiment of the present disclosure are shown.

[0026] Figure 19 An example of PDCCH repetition according to one aspect of an embodiment of the present disclosure is shown.

[0027] Figure 20 An example of control channel repetition across multiple TRPs is shown according to one aspect of an embodiment of the present disclosure.

[0028] Figure 21An example of control channel repetition according to one aspect of an embodiment of the present disclosure is shown.

[0029] Figure 22 An example of a core set associated with multiple TCI states as active TCI states is shown according to one aspect of an embodiment of the present disclosure.

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

[0031] Figure 24 is an example of repeatedly determining uplink resources using a control channel according to one aspect of an embodiment of the present disclosure.

[0032] Figure 25 is an exemplary flow chart of iterative uplink resource determination using a control channel according to one aspect of an embodiment of the present disclosure.

[0033] Figure 26 is an example of repeatedly determining downlink resources using a control channel according to one aspect of an embodiment of the present disclosure.

[0034] Figure 27 is an exemplary flow chart of iterative downlink resource determination using a control channel according to one aspect of an embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] In the present disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope of the present invention. In fact, after reading the specification, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. The embodiments of the present invention should not be limited by any described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figures that highlight functionality and advantages are provided for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in a manner different from that shown. For example, the actions listed in any flow chart can be reordered or only optionally used in certain embodiments.

[0036] Implementations can be configured to operate as desired. For example, the disclosed mechanisms can be implemented when certain criteria are met in a wireless device, base station, radio environment, network, or combinations thereof. Exemplary criteria can be based, at least in part, on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, traffic characteristics, or combinations thereof. When one or more criteria are met, various exemplary implementations can be applied. Thus, exemplary implementations that selectively implement the disclosed protocol can be implemented.

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

[0038] Throughout this disclosure, “a” and “an” and similar phrases are to be interpreted as meaning “at least one” and “one or more.” Similarly, any term ending in the suffix “(s)” is to be interpreted as meaning “at least one” and “one or more.” Throughout this disclosure, the term “may” is to be interpreted as meaning “may, for example.” In other words, the term “may” indicates that the phrase following the term “may” is an example of one suitable possibility among multiple suitable possibilities that may or may not be used for one or more embodiments in various embodiments. As used herein, the terms “comprising” and “consisting of” list one or more components of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude unlisted components from being included in the element being described. In contrast, “consisting of” provides a complete listing of the one or more components of the element being described. As used herein, the term “based on” is to be interpreted as meaning “based, at least in part, on,” rather than, for example, “based only on.” As used herein, the term “and / or” refers to any possible combination of the listed 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.

[0039] 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, the possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently, "based at least on") indicates that the phrase following the term "based on" is an example of one of multiple suitable possibilities that may or may not be used in one or more different embodiments. The phrase "in response to" (or equivalently, "in response to at least") indicates that the phrase following the phrase "in response to" is an example of one of multiple suitable possibilities that may or may not be used in one or more different embodiments. The phrase "depending on" (or equivalently, "depending at least on") indicates that the phrase following the phrase "depending on" is an example of one of multiple suitable possibilities that may or may not be used in one or more different embodiments. The phrase "using" (or equivalently, "at least using") indicates that the phrase following the phrase "using" is an example of one of multiple suitable possibilities that may or may not be used in one or more different embodiments.

[0040] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can also refer to specific settings in a device that affect the operational characteristics of the device, 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 a device to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Terms such as "a control message induced in a device" can mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0041] In the present disclosure, a parameter (or equivalently, 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 an exemplary embodiment, when one or more messages include multiple parameters, it means that the parameters in the multiple parameters are in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0042] Many of the features presented are described as optional, either by using the word "may" or by using parentheses. For the sake of brevity and readability, this disclosure does not explicitly recite every permutation that can be obtained by selecting from the set 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, namely, having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0043] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs a defined function and has defined interfaces to other elements. The modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, all of which may be behaviorally equivalent. For example, a module can be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement the module 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, and C++. FPGAs, ASICs, and CPLDs are often programmed using a hardware description language (HDL), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between the smaller internal hardware blocks on the programmable device. The mentioned techniques are often used in combination to achieve the results of the functional blocks.

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

[0045] The CN 102 may provide an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or intra-carrier DNs, for the wireless device 106. As part of the interface functionality, the CN 102 may set up an end-to-end connection between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

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

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

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

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

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

[0051] The RAN 104 can be deployed as a homogeneous network with macrocell base stations having similar antenna types and similar high levels of transmit power. The 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 overlapping coverage areas provided by relatively large macrocell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hotspots") or in areas where macrocell coverage is weak. Examples of small cell base stations include, in descending order of coverage area: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

[0053] Figure 1B Another exemplary mobile communication network 150 is shown in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown in FIG, a 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). Figure 1A The corresponding components described herein are implemented and operate in the same or similar manner.

[0054] 5G-CN 152 provides an interface to one or more DNs, such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN, for UE 156. As part of this interface functionality, 5G-CN 152 can set up an end-to-end connection between UE 156 and the one or more DNs, authenticate UE 156, and provide billing functionality. Compared to the CN of a 3GPP 4G network, the foundation of 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes that make up 5G-CN 152 can be defined as network functions that provide services to other network functions via interfaces. The network functions of 5G-CN 152 can be implemented in a number of ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0055] like Figure 1B As shown, 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B, which are not shown in FIG. Figure 1BIn the figure, they 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. UPF 158B can perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification to support routing of traffic 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 verification), downlink packet buffering, and downlink data notification triggering. UPF 158B can serve as an anchor point for intra- and inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnecting the one or more DNs, and / or a fulcrum for supporting multi-homed PDU sessions. UE 156 can be configured to receive services via a PDU session, which is a logical connection between the UE and a DN.

[0056] The AMF 158A may perform functions such as: non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policy), network slicing support and / or session management function (SMF) selection. NAS may refer to a function operating between a CN and a UE, and AS may refer to a function operating between a UE and a RAN.

[0057] 5G-CN 152 may include Figure 1B . For example, the 5G-CN 152 may include one or more of the following: a session management function (SMF), an NR repository function (NRF), a policy control function (PCF), a network exposure function (NEF), a unified data management (UDM), an application function (AF), and / or an authentication server function (AUSF).

[0058] The NG-RAN 154 can connect the 5G-CN 152 to the UE 156 via radio communications over the air interface. The NG-RAN 154 may include one or more gNBs, illustrated as gNB 160A and gNB 160B (collectively, gNB 160), and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively, ng-eNB 162). The gNBs 160 and ng-eNB 162 may be more generally referred to as base stations. The gNBs 160 and ng-eNB 162 may include one or more antennas for communicating with the 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 antennas to control three cells (or sectors), respectively. The cells of gNB 160 and ng-eNB 162 may together provide radio coverage to UE 156 over a wide geographic area to support UE mobility.

[0059] like Figure 1B As shown in FIG, gNB 160 and / or ng-eNB 162 may be connected to 5G-CN 152 via an NG interface and to other base stations via an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections through underlying transport networks, such as Internet Protocol (IP) transport networks. gNB 160 and / or ng-eNB 162 may be connected to UE 156 via a Uu interface. For example, Figure 1B As shown in FIG, gNB 160A can be connected to UE 156A via a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface can be composed of Figure 1B Network elements in a network exchange data and signaling messages and may include two planes: the user plane and the control plane. The user plane processes data of interest to users, while the control plane processes signaling messages of interest to network elements.

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

[0061] The gNB 160 can provide NR user plane and control plane protocol termination to the UE 156 via a Uu interface. For example, the gNB 160A can provide NR user plane and control plane protocol termination to the UE 156A via a 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 the UE 156 via a Uu interface, where E-UTRA refers to a 3GPP 4G radio access technology. For example, the ng-eNB 162B can provide E-UTRA user plane and control plane protocol termination to the UE 156B via a Uu interface associated with the second protocol stack.

[0062] The 5G-CN 152 is described as being configured to handle both NR and 4G radio access. One of ordinary skill in the art will appreciate that it is possible for NR to be connected to a 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 Only one AMF / UPF 158 is shown in the figure, but one gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

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

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

[0065] Figure 2A The NR user plane protocol stack is shown, including five layers implemented in UE 210 and gNB 220. At the bottom of the protocol stack, physical layers (PHY) 211 and 221 can provide transport services to higher layers of the protocol stack and may correspond to Layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHY 211 and 221 include medium 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. Together, these four protocols may constitute Layer 2, or the data link layer, of the OSI model.

[0066] Figure 3 An example of services provided between protocol layers of the NR user plane protocol stack is shown. Figure 2A and Figure 3 Starting from the top, SDAPs 215 and 225 can perform QoS flow processing. UE 210 can receive services via a PDU session, which can be a logical connection between UE 210 and a DN. A PDU session can have one or more QoS flows. The CN's UPF (e.g., UPF 158B) can map IP packets to the 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 / de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping / de-mapping 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 reflective mapping or control signaling received from gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between QoS flows and data radio bearers.

[0067] PDCPs 214 and 224 can perform header compression / decompression to reduce the amount of data transmitted over the air interface, encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection to ensure that control messages originate from the intended source. PDCPs 214 and 224 can also perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate packets received due to, for example, intra-gNB handovers. PDCPs 214 and 224 can also 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.

[0068] although Figure 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in dual connectivity scenarios. Dual connectivity is a technology 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 when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service for SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapply split radio bearers between RLC channels belonging to the cell group.

[0069] RLC 213 and 223 can perform segmentation, retransmission via automatic repeat request (ARQ), and removal of duplicate data units received from MAC 212 and 222, respectively. RLC 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode in which the RLC is operating, the RLC can perform one or more of the functions described. RLC configuration can be on a per-logical channel basis, independent of parameter sets and / or transmission time interval (TTI) durations. Figure 3 As shown in FIG, RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

[0070] MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing data units belonging to one or more logical channels into / from transport blocks (TBs) delivered to / from PHYs 211 and 221. MAC 222 may be configured to perform scheduling, scheduling information reporting, and inter-UE prioritization using dynamic scheduling. Scheduling for both downlink and uplink may be performed in gNB 220 (at MAC 222). MACs 212 and 222 may be configured to perform error correction using hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), prioritization between logical channels of UE 210 using logical channel prioritization, and / or padding. MACs 212 and 222 may support one or more parameter sets and / or transmission timings. In some examples, mapping restrictions in logical channel prioritization may control which parameter sets and / or transmission timings a logical channel may use. like Figure 3 As shown, MAC 212 and 222 may provide logical channels as a service to RLC 213 and 223 .

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

[0072] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4A Three IP packets are shown flowing through the NR user plane protocol stack to generate two TBs at the gNB 220 ( n 、 n+1 and m ) downlink data flow. The uplink data flow flowing through the NR user plane protocol stack can be Figure 4A The downlink data flow is similar to that depicted in .

[0073] Figure 4A The downlink data flow of starts when the SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. Figure 4A In the SDAP 225, the IP packet n and n+1Mapped to the first radio bearer 402, and the IP packet m Mapped to the second radio bearer 404. SDAP header (in Figure 4A The data unit from / to a higher protocol layer is called a service data unit (SDU) of the lower protocol layer, and the data unit to / from a lower protocol layer is called a protocol data unit (PDU) of the higher protocol layer. Figure 4A As shown in , the data units from SDAP 225 are SDUs of the lower protocol layer PDCP 224 and are PDUs of SDAP 225 .

[0074] Figure 4A The remaining protocol layers in the Figure 3 ), add the corresponding headers and forward their corresponding output to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., Figure 4A About IP Packet m ) and forwards its output to MAC 222. MAC 222 may multiplex many RLC PDUs and may append MAC subheaders to the RLC PDUs to form a transport block. In NR, MAC subheaders may be distributed throughout the MAC PDUs, as shown. Figure 4A In LTE, the MAC subheader 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 subheader can be calculated before assembling the complete MAC PDU.

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

[0076] Figure 4B Further shown is a MAC Control Element (CE) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, Figure 4B Two MAC CEs are shown inserted into a MAC PDU. Figure 4B) and a MAC CE is inserted at the end of a MAC PDU for uplink transmission. MAC CEs may 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 used for PDCP duplicate detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC subheader having a format similar to that described with respect to a MAC SDU may precede the MAC CE, and the MAC CE may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

[0077] Before describing the NR control plane protocol stack, we 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 described later below.

[0078] Figure 5A and Figure 5B The mapping between logical channels, transport channels and physical channels is shown for downlink and uplink respectively. Information is passed through channels between RLC, MAC and PHY of the NR protocol stack. Logical channels can be used between RLC and MAC and can be classified as control channels that carry control and configuration information in the NR control plane, or as traffic channels that carry data in the NR user plane. Logical channels can be classified as dedicated logical channels dedicated to 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:

[0079] - Paging Control Channel (PCCH), which is used to carry paging messages for UEs whose locations are unknown to the network at the cell level;

[0080] - Broadcast Control Channel (BCCH), which is used to carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), which can be used by UEs to obtain information about how a cell is configured and how it operates within the cell;

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

[0082] - a dedicated control channel (DCCH), which is used to carry control messages to / from a specific UE to configure the UE; and

[0083] - Dedicated Traffic Channel (DTCH), which is used to carry user data to / from a specific UE.

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

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

[0086] - Broadcast Channel (BCH), which is used to carry the MIB from the BCCH;

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

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

[0089] - Random Access Channel (RACH), which is used to allow a UE to contact the network without any previous scheduling.

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

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

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

[0093] - Physical Downlink Control Channel (PDCCH), which is used to carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

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

[0095] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, which may include HARQ acknowledgment, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and scheduling request (SR); and

[0096] - 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 the low-level operations of the physical layer. Figure 5A and Figure 5B As shown in [1], the physical layer signals defined by NR include: Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Sounding Reference Signal (SRS), and Phase Tracking Reference Signal (PT-RS). These physical layer signals are described in more detail below.

[0098] Figure 2B An exemplary NR control plane protocol stack is shown. Figure 2B As shown in , the NR control plane protocol stack may 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 instead has radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

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

[0100] RRCs 216 and 226 can provide control plane functionality between UE 210 and gNB 220, or more generally, between UE 210 and the RAN. RRCs 216 and 226 can provide control plane functionality between UE 210 and gNB 220 via signaling messages, referred to as RRC messages. RRC messages can be transported between UE 210 and the 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). The RRC 216 and 226 may provide control plane functions such as: broadcast of system information related to the AS and NAS; paging initiated by the CN or RAN; establishment, maintenance, and release of an RRC connection between the UE 210 and the 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 the reporting; detection of radio link failure (RLF) and recovery from radio link failure; and / or NAS messaging. As part of establishing an RRC connection, the RRC 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

[0101] Figure 6 is an example diagram showing the RRC state transition of the UE. Figure 1A The wireless device 106 depicted in Figure 2A and Figure 2B The UE 210 depicted in FIG or any other wireless device described in this disclosure is the same or similar. Figure 6 As shown in FIG, a UE may be in at least one of three RRC states: RRC connected 602 (eg, RRC_CONNECTED), RRC idle 604 (eg, RRC_IDLE), and RRC inactive 606 (eg, 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 the RAN 104 depicted in FIG; Figure 1B One of the gNB 160 or ng-eNB 162 depicted in FIG; Figure 2A and Figure 2BgNB 220 depicted in FIG602; or any other base station described in this disclosure. A base station connected to a UE may have an RRC context for the UE. The RRC context, referred to as the UE context, may include parameters used 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. While in RRC connection 602, the UE's mobility may be managed by a RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from its 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 handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 via a connection release procedure 608 , or to RRC inactive 606 via a connection deactivation procedure 610 .

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

[0104] In RRC Inactive 606, the previously established RRC context is maintained in the UE and the base station. This allows for a quick transition to RRC Connected 602 with reduced signaling overhead compared to the transition from RRC Idle 604 to RRC Connected 602. While in RRC Inactive 606, the UE may be in a sleep state, and the UE's mobility may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connected 602 via a Connection Resumption Procedure 614, or to RRC Idle 604 via a Connection Release Procedure 616, which may be the same as or similar to the Connection Release Procedure 608.

[0105] The RRC state 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 broadcasting the paging messages across the entire mobile communications network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 can allow the network to track the UE at a cell group level, so that paging messages can be sent to cells in the cell group where the UE is currently residing, rather than broadcasting the entire mobile communications network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 track the UE at a cell group level. These mobility management mechanisms can do so using different levels of grouping granularity. For example, there can be three levels of cell grouping granularity: individual cells; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas, known as tracking areas and identified by a Tracking Area Identifier (TAI).

[0106] Tracking areas can be used to track UEs 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 that is not included in the list of TAIs associated with the UE's registration area through 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 the new UE registration area.

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

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

[0109] gNBs, such as Figure 1BThe gNB 160 in the NB-LTE network can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DUs). The gNB-CU can be coupled to one or more gNB-DUs using the 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 OFDM is a multi-carrier communication scheme that uses F Before transmission, the data can be mapped into a series of complex symbols called source symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols) and divided into F parallel symbol streams. F The 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 can take F Source symbols (from F parallel symbol streams) and uses each source symbol to modulate F The orthogonal subcarriers correspond to F The output of the IFFT block can be represented by the amplitude and phase of one of the sinusoidal basis functions. F The sum of the orthogonal subcarriers F time domain samples. F The time domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. F The parallel symbol streams can be mixed using the FFT block before being processed by the IFFT block. This operation produces discrete Fourier transform (DFT) precoded OFDM symbols and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The FFT block can be used to perform inverse processing on the OFDM symbols at the receiver to recover the data mapped to the source symbols.

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

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

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

[0114] Figure 8 An exemplary configuration of a slot in the time and frequency domains of an NR carrier is shown. The slot consists of resource elements (REs) and resource blocks (RBs). REs are the smallest physical resources in NR. REs span one OFDM symbol in the time domain through one subcarrier in the frequency domain, as shown in Figure 1. Figure 8 As shown in . RB spans twelve consecutive REs in the frequency domain, as Figure 8As shown in Figure 2, the NR carrier can be limited to a width of 275 RBs or 275×12=3300 subcarriers. If this restriction is used, the NR carrier can be limited to 50 MHz, 100 MHz, 200 MHz, and 400 MHz for subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively, where the 400 MHz bandwidth can be set based on the 400 MHz bandwidth limit per carrier.

[0115] Figure 8 A single parameter set is shown as being used across the entire bandwidth of the NR carrier. In other example configurations, multiple parameter sets may be supported on the same carrier.

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

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

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

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

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

[0121] One or more BWP indicator fields may be provided in downlink control information (DCI). The value of the BWP indicator field may indicate which BWP in a 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 may indicate the active uplink BWP for one or more uplink transmissions.

[0122] The base station may semi-statically configure a default downlink BWP for the UE within the 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 may be the initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0123] The base station may configure the BWP inactivity timer value for the PCell for the UE. The UE may start or restart the BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer in the following circumstances: ( a ) when the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or ( b) When 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 the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (e.g., increment the BWP inactivity timer value from zero to, or decrement the BWP inactivity timer value from zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0124] In an example, the base station may semi-statically configure the UE with one or more BWPs. The UE may 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 expiration of a BWP inactivity timer (e.g., when the second BWP is the default BWP).

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

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

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

[0128] To provide higher data rates, carrier aggregation (CA) can be used to aggregate two or more carriers and transmit them simultaneously to / from the same UE. The aggregated carriers in CA are referred to as component carriers (CCs). When CA is used, there are multiple serving cells for the UE, one for each CC. CCs 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 non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (Band A) and separated by a 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 an example, up to 32 CCs can be aggregated. Aggregated CCs can have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD or FDD). A serving cell for a UE using CA can have downlink CCs. For FDD, one or more uplink CCs can optionally be configured for the serving cell. The ability to aggregate more downlink carriers than uplink carriers can be useful, for example, when a UE has more data traffic in the downlink than in the uplink.

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

[0132] The configured SCell for a UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmission on the SCell. Figure 4B MAC CEs are used to activate and deactivate configured SCells. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., a subset of configured SCells) are activated or deactivated for the UE. A configured SCell may be deactivated in response to the expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

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

[0134] Figure 10B An example of how aggregated cells can be configured into one or more PUCCH groups is shown. PUCCH group 1010 and PUCCH group 1050 may each include one or more downlink CCs. Figure 10B In the example shown in FIG1 , PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. In this example, PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may 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) may be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) may be transmitted in the uplink of PSCell 1061. In this example, if Figure 10B If the aggregated cell depicted in FIG is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell transmits UCI associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by dividing the transmission of UCI between PCell 1021 and PSCell 1061.

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

[0136] In carrier aggregation, the multi-carrier nature of the PHY can be exposed to the MAC. In this example, the HARQ entity can operate on the serving cell. A transport block can be generated based on the assignment / grant of each serving cell. A transport block and potential HARQ retransmissions of that transport block can be mapped to the serving cell.

[0137] In the downlink, the base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RSs) to the UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, such as Figure 5A In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in FIG. Figure 5B (as shown). The PSS and SSS may be transmitted by a base station and used by a UE to synchronize the UE with the base station. The PSS and SSS may be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes the PSS, SSS, and PBCH. The base station may 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 may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as Figure 11A As shown). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). Bursts may be limited to half a frame (e.g., the first half frame having a duration of 5 ms). It will be understood that Figure 11Aare examples, and these parameters (number of SS / PBCH blocks per burst, periodicity of the burst, position of the burst within the frame) may be configured based on, for example: the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the numerology or subcarrier spacing of the cell; configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may 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 may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as Figure 11A ), and may span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., spanning the next 3 OFDM symbols) and may span 240 subcarriers.

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

[0141] The SS / PBCH block can be used by the UE to determine one or more parameters of a 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 pattern in which the SS / PBCH block is a known distance from the frame boundary.

[0142] The PBCH may use QPSK modulation and forward error correction (FEC). FEC may use polarity coding. One or more symbols spanning the PBCH may carry one or more DMRSs for demodulating the PBCH. The PBCH may include an indication of the current system frame number (SFN) of the cell and / or an SS / PBCH block timing index. These parameters may facilitate time synchronization between the UE and the base station. The PBCH may include a master information block (MIB) that provides one or more parameters to the UE. The MIB may be used by the UE to locate the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a system information block type 1 (SIB1). SIB1 may contain information necessary for the UE to access the cell. The UE may use one or more parameters from the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may navigate to a frequency. The UE may search for SS / PBCH blocks on the frequency to which the UE is directed.

[0143] The UE may assume that one or more SS / PBCH blocks transmitted with 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) may be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​the cell). In an example, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

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

[0146] A CSI-RS may be transmitted by a base station and used by a UE to obtain channel state information (CSI). The base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure the UE with one or more of the same / similar CSI-RSs. The UE may measure the one or more CSI-RSs. The UE may estimate the downlink channel state and / or generate a CSI report based on the measurement of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may 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 with one or more CSI-RS resource sets. CSI-RS resources can be associated with a location in the time and frequency domains, as well as a periodicity. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can indicate to the UE that CSI-RS resources in a CSI-RS resource set are activated and / or deactivated.

[0148] The base station can configure the UE to report CSI measurement values. 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 the timing and / or period of multiple CSI reports. For aperiodic CSI reporting, the base station can request a CSI report. For example, the base station can command the UE to measure the configured CSI-RS resources and provide a CSI report related to the measurement value. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reporting. The base station can configure the UE with a CSI-RS resource set and CSI reporting using RRC signaling.

[0149] The CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and 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 blocks (PRBs) configured for the CORESET. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRBs configured for the SS / PBCH blocks.

[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). NR networks can support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS pattern. 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 with 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 support a common DMRS structure for downlink and uplink (e.g., at least for CP-OFDM), where the DMRS location, DMRS pattern, and / or scrambling sequence can be the same or different. The base station can use the same precoding matrix to transmit the downlink DMRS and the corresponding PDSCH. The UE can use the one or more downlink DMRS to perform consistent demodulation / channel estimation on the PDSCH.

[0151] In an example, a transmitter (e.g., a base station) may use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may differ based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used across a set of PRBs. This set of PRBs may be denoted as a precoding resource block group (PRG).

[0152] The PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer in the one or more layers of the PDSCH. Higher layers 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 may depend on RRC configuration. The presence and / or type of downlink PT-RS can be UE-specifically configured using a combination of RRC signaling and / or association with one or more parameters that may be indicated by DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters, including at least the 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 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. The downlink PT-RS can be restricted to the UE's scheduled time / frequency duration. The downlink PT-RS can be transmitted on a symbol basis to facilitate phase tracking at the receiver.

[0154] The UE may transmit uplink DMRS to the base station for channel estimation. For example, the base station may use uplink DMRS to uniformly demodulate one or more uplink physical channels. For example, the UE may transmit uplink DMRS with PUSCH and / or PUCCH. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a frontload DMRS pattern. The frontload DMRS may be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to be transmitted on one or more symbols of the PUSCH and / or PUCCH. The base station may semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols for the PUSCH and / or PUCCH, which the UE may use to schedule single-symbol DMRS and / or double-symbol DMRS. NR networks may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS positions, DMRS patterns, and / or scrambling sequences of the DMRS may be the same or different.

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

[0156] Depending on the UE's RRC configuration, 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 uplink PT-RS can be configured on a UE-specific basis through a combination of RRC signaling and / or one or more parameters indicated by DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of uplink PT-RS can be associated with one or more DCI parameters, including at least the 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 restricted to the UE's scheduled time / frequency duration.

[0157] The UE may transmit an 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 may allow the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station may use the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For each SRS resource set, the base station may configure the UE with one or more SRS resources. The applicability of an SRS resource set may be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources (e.g., having the same / similar time-domain behavior, periodic, aperiodic, etc.) in the one or more SRS resource sets may be transmitted at a certain time (e.g., simultaneously). The UE may transmit one or more SRS resources in the SRS resource set. NR networks may support aperiodic, periodic, and / or semi-persistent SRS transmission. The UE may transmit SRS resources based on one or more trigger types, where the one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format may be used for the UE to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in the same time slot, the UE may 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: an SRS resource configuration identifier; the number of SRS ports; the time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); time slot, mini-slot, and / or subframe level periodicity; time slot of periodic and / or aperiodic SRS resources; the number of OFDM symbols in the SRS resources; the starting OFDM symbol of the SRS resources; the SRS bandwidth; the frequency hopping bandwidth; the cyclic shift; and / or the SRS sequence ID.

[0159] Antenna ports are defined such that the channel over which a symbol on the antenna port is communicated can be inferred from the channel over which another symbol on the same antenna port is communicated. If a first symbol and a second symbol are transmitted on the same antenna port, a receiver can infer the channel (e.g., fading gain, multipath delay, etc.) used to communicate the second symbol on the antenna port from the channel used to communicate the first symbol on the antenna port. A first antenna port and a second antenna port can be referred to as quasi-co-located (QCLed) if one or more large-scale properties of the channel over which the first symbol on the first antenna port is communicated can be inferred from the channel over which the second symbol on the second antenna port is communicated. The 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 receive (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 beam measurement reports based on downlink reference signals (e.g., Channel State Information Reference Signal (CSI-RS)). After establishing an RRC connection with the base station, the UE can perform downlink beam measurement procedures.

[0161] Figure 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domain is shown. Figure 11BThe squares shown in the figure may represent resource blocks (RBs) within the bandwidth of the cell. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured for the 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 a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in a radio frame), CSI-RS power parameter, CSI-RS sequence parameter, code division multiplexing (CDM) type parameter, frequency density, transmit 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 may be configured for the UE in a UE-specific configuration. Figure 11B Three beams (beam #1, beam #2, and beam #3) are illustrated in FIG. More or fewer beams may be configured. CSI-RS 1101 may be assigned to beam #1 and may be transmitted in one or more subcarriers in the RB of the first symbol. CSI-RS 1102 may be assigned to beam #2 and may be transmitted in one or more subcarriers in the RB of the second symbol. CSI-RS 1103 may be assigned to beam #3 and may be transmitted in one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in the same RB (e.g., those not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam of another UE. By using time domain multiplexing (TDM), beams for a UE may be configured such that the beam for the UE uses symbols from beams of other UEs.

[0163] CSI-RS, such as Figure 11BThose shown in FIG. 1 (e.g., CSI-RS 1101, 1102, 1103) may be transmitted by a base station and used by a UE for one or more measurement values. For example, the UE may measure the reference signal received power (RSRP) of the configured CSI-RS resources. The base station may configure the UE with a reporting configuration, and the UE may report the RSRP measurement values ​​to the network (e.g., via one or more base stations) based on the reporting configuration. In an example, the base station may determine one or more transmission configuration indication (TCI) states including multiple reference signals based on the reported measurement results. In an example, the base station may indicate the one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE may receive a downlink transmission having a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have beam-matching capability. If the UE has beam-matching capability, the UE may determine the spatial domain filter for the transmit (Tx) beam based on the spatial domain filter for the corresponding Rx beam. If the UE does not have beam-matching capability, the UE may perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The UE may 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 may select and instruct the UE on an uplink beam based on measurements of the one or more SRS resources transmitted by the UE.

[0164] During the beam management procedure, the UE may assess (e.g., measure) the channel quality of one or more beam pair links, including the transmit beams transmitted by the base station, and the receive beams received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair 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 12AThree examples of downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurements of the transmit (Tx) beams of a transmit reception point (TRP) (or multiple TRPs), for example, to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top and bottom rows of P1, respectively). Beamforming at the TRP can include Tx beam sweeping for a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of P1 and P2). Beamforming at the UE can include Rx beam sweeping for a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements of the Tx beams of the TRPs (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or base station may perform procedure P2 using a smaller beam set than the beam set used in procedure P1, or using a narrower beam than the beam 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 Three examples of uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable a base station to perform measurements on a UE's Tx beams, for example, to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, Rx beam sweeping from a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station can include, for example, Rx beam sweeping from a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of U1 and U2). When a 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 used in procedure P1, or using a narrower beam than used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

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

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

[0169] The network (e.g., gNB and / or ng-eNB of the network) and / or the UE may initiate a random access procedure. A UE in the RRC_IDLE state and / or the RRC_INACTIVE state may initiate a random access procedure to request connection setup to the network. The UE may initiate a random access procedure from the RRC_CONNECTED state. The UE may 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). The UE may initiate a random access procedure to request one or more system information blocks (SIBs) (e.g., other system information, such as SIB2, SIB3, etc.). The UE may initiate a random access procedure for beam failure recovery requests. The network may initiate a random access procedure for handover and / or to establish time alignment for SCell addition.

[0170] Figure 13A A four-step contention-based random access procedure is shown. Before initiating the procedure, the base station may transmit a configuration message 1310 to the UE. Figure 13AThe procedure shown includes the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg 3 1313, and Msg 4 1314. Msg 1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg 2 1312 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. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The 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 the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to UEs in the RRC_CONNECTED state and / or the RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE may determine the reception timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0172] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that may be used to transmit Msg 11311. The one or more PRACH opportunities may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between: (a) one or more PRACH opportunities and (b) one or more reference signals. The one or more RACH parameters may indicate an association between: (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunity and / or the number of preambles mapped to the SS / PBCH block.

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

[0174] Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may 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 the path loss measurement value and / or the size of Msg 3 1313. 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 having an RSRP greater 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 the RRC message, the UE may select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

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

[0176] If no response is received after a preamble transmission, the UE may perform a preamble retransmission. The UE may increase the uplink transmission power for the preamble retransmission. The UE may select the initial preamble transmission power based on a path loss measurement and / or a target received preamble power configured by the network. The UE may determine to retransmit the preamble and may ramp up the uplink transmission power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramp-up step size for preamble retransmission. The ramp-up step size may be the amount of incremental increase in uplink transmission power for retransmission. If the UE determines the same reference signal (e.g., SSB and / or CSI-RS) as 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 (eg, preambleTransMax) configured by the one or more RACH parameters, the UE may determine that the random access procedure is not successfully completed.

[0177] Msg 2 1312 received by the UE may include a RAR. In some scenarios, Msg 2 1312 may include multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a random access RNTI (RA-RNTI). Msg 2 1312 may indicate that Msg 1 1311 was received by the base station. Msg 2 1312 may include a time alignment command, which the UE may use to adjust its transmission timing, a scheduling grant for transmitting Msg 3 1313, 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 for Msg 2 1312. The UE may determine when to start the time window based on the PRACH opportunity used by the UE to transmit the preamble. For example, the UE may start a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH opportunity starting from the end of the preamble transmission). The one or more symbols may be determined based on a parameter set. The PDCCH may be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. 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 a random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a time slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH opportunity. Examples of 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 may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0 ≤ s_id < 14), t_id may be the index of the first time slot of the PRACH opportunity in the system frame (e.g., 0 ≤ t_id < 80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for the NUL carrier and 1 for the SUL carrier).

[0180] The UE may transmit Msg 3 1313 in response to successfully receiving Msg 2 1312 (eg, using the resources identified in Msg 2 1312). Msg 3 1313 may be used, for example, Figure 13A Contention resolution in the contention-based random access procedure shown in . In some scenarios, multiple UEs may transmit the same preamble to the base station, and the base station may provide RARs corresponding to the UEs. If the multiple UEs interpret the RARs as corresponding to themselves, a collision may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE does 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 may 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 successfully completed. If Msg 3 1313 includes a TC-RNTI (e.g., if the UE is in the RRC_IDLE state or is not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and includes a UE Contention Resolution Identity (MAC CE) that matches or otherwise corresponds to the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that contention resolution was successful and / or the UE may determine that the random access procedure was successfully completed.

[0182] A UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., a random access procedure) may be supported on the uplink carrier. For example, the base station may configure two separate RACH configurations for the UE: one for the SUL carrier and another for the NUL carrier. For random access in a cell configured with a SUL carrier, the network may indicate which carrier (NUL or SUL) to use. For example, the UE may determine the SUL carrier if the measured quality of one or more reference signals is below a broadcast threshold. Uplink transmissions for the random access procedure (e.g., Msg1 1311 and / or Msg3 1313) may remain on the selected carrier. In one or more scenarios, the UE may switch uplink carriers during the random access procedure (e.g., between Msg1 1311 and Msg3 1313). For example, the UE may determine and / or switch an uplink carrier for Msg 1 1311 and / or Msg 3 1313 based on channel clarity assessment (eg, listen before talk).

[0183] Figure 13B The two-step contention-free random access procedure is shown. Figure 13A Similar to the four-step contention-based random access procedure shown, the base station may transmit a configuration message 1320 to the UE before the procedure is initiated. The configuration message 1320 may be similar to the configuration message 1310 in some aspects. Figure 13B The procedure shown includes the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 may be similar in some respects to Figure 13A As shown in Msg 1 1311 and Msg 2 1312. Figure 13A and Figure 13B It will be appreciated that the contention-free random access procedure may not include messages similar to Msg 3 1313 and / or Msg 4 1314 .

[0184] Can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover Figure 13B For example, the base station may indicate or assign a preamble to be used for Msg 1 1321 to the UE. The UE may receive an indication of the preamble (eg, ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0185] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for the RAR. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. Figure 13B In the illustrated contention-free random access procedure, the UE may determine that the random access procedure has been successfully completed after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, if the PDCCH transmission is addressed to the C-RNTI, the UE may determine that the random access procedure has been successfully completed. For example, if the UE receives a RAR including a preamble identifier corresponding to a preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with the preamble identifier, the UE may determine that the random access procedure has been successfully completed. The UE may determine that the response is an indication of confirmation of the SI request.

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

[0187] Msg A 1331 may be transmitted by the UE in an uplink transmission. Msg A 1331 may include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. Transport block 1342 may include Figure 13A The content of Msg 3 1313 shown in FIG. 1342 may include UCI (e.g., SR, HARQ ACK / NACK, etc.). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include the same content as the content of Msg 3 1313 shown in FIG. Figure 13A and Figure 13B Msg 2 1312 (eg, RAR) and / or Figure 13A The content of Msg 4 1314 is similar and / or identical to that of Msg 4 1314 shown.

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

[0189] The UE may determine the radio resources and / or uplink transmission power for the preamble 1341 and / or transport block 1342 included in Msg A 1331 based on the two-step RACH parameters included in the configuration message 1330. The RACH parameters may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or transport block 1342. The time-frequency resources used for transmitting the preamble 1341 (e.g., PRACH) and the time-frequency resources used for transmitting the transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the reception timing and downlink channel used 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., an International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 in response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier; a timing high-level command; a power control command; an uplink grant (e.g., a radio resource assignment and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure has been 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 Msg A 1331 (e.g., transport block 1342).

[0191] The UE and the base station may exchange control signaling. This control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., Layer 1) and / or 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 assignments; uplink scheduling grants indicating uplink radio resources and / or transport formats; time slot format information; preemption indications; power control commands; and / or any other suitable signaling. A UE may receive downlink control signaling in a payload transmitted by a base station on a 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 common PDCCH (GC-PDCCH) common to a group of UEs.

[0193] The base station may append one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. When the DCI is intended for a UE (or group of UEs), the base station may scramble the CRC parity bits with an identifier for the UE (or group of UEs). Scrambling the CRC parity bits with the identifier may include a Modulo-2 addition (or exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a 16-bit value of a Radio Network Temporary Identifier (RNTI).

[0194] DCI may be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or system information change notification. The P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. The SI-RNTI may be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of a PDCCH ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate contention resolution (e.g., similar to Figure 13AThe other RNTIs configured by the base station to the UE may include: the configured scheduling RNTI (CS-RNTI), transmit power control PUCCH RNTI (TPC-PUCCH-RNTI), transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), transmit power control SRS RNTI (TPC-SRS-RNTI), interruption 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, a base station may transmit DCI using one or more DCI formats. For example, DCI format 0_0 may be used for scheduling the PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling the PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling the PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used for scheduling the PDSCH in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a group of UEs. DCI format 2_1 may be used to notify a group of UEs of physical resource blocks and / or OFDM symbols, where the UE may assume that no transmission to the UE is expected. DCI format 2_2 may be used to transmit transmit power control (TPC) commands for the PUCCH or PUSCH. DCI formats 2_3 can be used to transmit a set of TPC commands for SRS transmission by one or more UEs. DCI formats for new functions may be defined in future releases. DCI formats can have different DCI sizes or can share the same DCI size.

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

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

[0198] Figure 14B This section shows an example of CCE-to-REG mapping for DCI transmission across a core set and PDCCH processing. The CCE-to-REG mapping can be interleaved (e.g., to provide frequency diversity) or non-interleaved (e.g., to facilitate interference coordination and / or frequency-selective transmission of control channels). A base station can perform different or identical CCE-to-REG mapping for different core sets. A core set can be associated with the CCE-to-REG mapping through RRC configuration. A core set can be configured with an antenna port quasi-co-location (QCL) parameter. The antenna port QCL parameter can indicate the QCL information of the demodulation reference signal (DMRS) used for PDCCH reception in the core set.

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

[0200] like Figure 14B As shown, the UE may determine the time-frequency resources of a CORESET based on an RRC message. The UE may determine the CCE-to-REG mapping of the CORESET based on configuration parameters of the CORESET (e.g., interleaving or non-interleaving and / or mapping parameters). The UE may determine the number of search space sets configured on the CORESET (e.g., up to 10) based on the RRC message. The UE may monitor a set of PDCCH candidates based on the configuration parameters of the search space sets. The UE may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates based on the monitored DCI format. Monitoring may include decoding DCI content of the one or more PDCCH candidates, including possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in a common search space, and / or number of PDCCH candidates in a UE-specific search space), and possible (or configured) DCI formats. This decoding may be referred to as blind decoding. The UE may determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambled bits of the CRC parity bits of the DCI matching the RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink grants, power control, slot format indication, downlink preemption, etc.).

[0201] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The 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. The 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 may determine the transport format parameters for the downlink transmission (e.g., including multiple antennas and beamforming schemes). The uplink control signaling may include a scheduling request (SR). The UE may transmit the SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgments (HARQ-ACKs), CSI reports, SRs, etc.) via the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via the PUCCH using one of several PUCCH formats.

[0202] There can be five PUCCH formats, and the UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for the UCI transmission 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 the transmission exceeds one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE can use PUCCH format 0 to transmit UCI in the PUCCH resources. PUCCH format 1 can occupy between four and fourteen OFDM symbols and can include two or fewer bits. If the transmission is four or more symbols 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 the transmission exceeds one or two symbols and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources do not include orthogonal cover codes, the UE may use PUCCH format 3. PUCCH format 4 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources include orthogonal cover codes, the UE may use PUCCH format 4.

[0203] The base station may transmit configuration parameters of multiple PUCCH resource sets to the UE using, for example, an RRC message. The multiple PUCCH resource sets (e.g., up to four sets) may be configured on the uplink BWP of the cell. The PUCCH resource set may be configured with: a PUCCH resource set index; multiple PUCCH resources having PUCCH resources identified by a PUCCH resource identifier (e.g., pucch-Resourceid); and / or a plurality (e.g., a maximum number) of UCI information bits that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE may 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 less, the UE may select the first PUCCH resource set with a PUCCH resource set index equal to "0". If the total bit length of the UCI information bits is greater than two and less than or equal to the first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configured value and less than or equal to the second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3".

[0204] After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE can determine the PUCCH resources 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., with DCI format 1_0 or 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 in communication with a base station 1504 according to an embodiment of the present 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 Only one wireless device 1502 and one base station 1504 are shown in FIG. 1 , but it should be understood that a mobile communication network may include more than one UE and / or more than one base station with the same Figure 15 The same or similar configurations as those shown.

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

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

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

[0209] At base station 1504, receive processing system 1512 may receive uplink transmissions from wireless device 1502. At wireless device 1502, receive processing system 1522 may receive downlink transmissions from base station 1504. Receive processing system 1512 and receive processing system 1522 may implement layer 1 OSI functions. Layer 1 may include information about Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4A For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and the like.

[0210] like Figure 15 As shown, wireless device 1502 and base station 1504 may include multiple antennas. These multiple antennas may be used to implement 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 system 1508 and processing system 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 may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed herein. Figure 15 Not shown, transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 may be coupled to memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that may be executed to perform one or more of their respective functions.

[0212] The processing system 1508 and / or the 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 device, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal encoding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0213] Processing system 1508 and / or processing system 1518 can be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 can include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keyboard, a display, a touchpad, a power supply, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, etc.). Processing system 1508 and / or processing system 1518 can 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 one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source can include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. The processing system 1508 and / or the processing system 1518 can be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[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. The one or more functions may include at least one of the following: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulated symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals for antenna ports; and the like. 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, the uplink transmission can be performed by Figure 16A Generates a CP-OFDM signal for uplink transmission. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0215] Figure 16B An exemplary structure for modulating and upconverting a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued physical random access channel (PRACH) baseband signal. Filtering can be employed prior to 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 one or more functions may include: scrambling coded bits in a codeword to be transmitted on the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transmission layers; precoding the complex-valued modulation symbols on the layers for transmission on the antenna ports; mapping the complex-valued modulation symbols for the antenna ports to resource elements; generating a complex-valued time-domain OFDM signal for the antenna ports; and so on. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

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

[0218] A wireless device may receive one or more messages (e.g., RRC messages) from a base station including configuration parameters for multiple cells (e.g., a primary cell, a secondary cell). The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the multiple cells. The one or more 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, or RRC layer. For example, the configuration parameters may include parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may include parameters indicating timer values ​​for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0219] Once started, a timer begins running and continues running until it is stopped 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 (for example, a timer can start or restart at a certain value, or can start at zero and expire once it reaches that value). The duration of a timer may not be updated until the timer is stopped or expires (for example, due to a BWP handover). A timer can be used to measure a time period / window in a measurement procedure. When the description refers to implementations and procedures related to one or more timers, it should be understood that there are various ways to implement these one or more timers. For example, it should be understood that one or more of these various ways of implementing a timer can be used to measure a time period / window in a measurement procedure. For example, a random access response window timer can be used to measure the time window for receiving a random access response. In an example, instead of the start and expiration of the random access response window timer, the time difference between two timestamps can be used. When the timer is restarted, the time window measurement procedure can be restarted. Other exemplary implementations for restarting the time window measurement are also provided.

[0220] The wireless device may receive / detect DCI via a core set. The DCI may trigger the transmission of HARQ-ACK information bits. For example, the DCI may schedule a transport block (e.g., PDSCH), and the wireless device may transmit HARQ-ACK information bits for the transport block. For example, the DCI may indicate an SPS release, and the wireless device may transmit HARQ-ACK information bits to acknowledge receipt of the DCI indicating the SPS release. In the prior art, the wireless device may determine uplink resources (e.g., PUCCH resources) for transmission of HARQ-ACK information bits based on the core set in which the wireless device receives the DCI. The wireless device may determine the uplink resources, for example, based on the number of control channel elements (CCEs) of the core set. The wireless device may determine the uplink resources on which the wireless device receives the DCI, for example, based on the first / earliest / starting CCE of the core set.

[0221] In an example, a wireless device may receive configuration parameters, for example, from a base station. The configuration parameters may indicate control channel repetition, wherein the base station transmits multiple DCI / PDCCHs (or DCI repetitions) via multiple core sets. The repetitions may be transmitted in multiple transmission / repetition occasions (e.g., time slots). The wireless device may monitor multiple core sets for multiple DCI / PDCCHs (or DCI repetitions) in multiple transmission occasions. Therefore, control channel repetition may increase control channel reliability and robustness.

[0222] In the prior art, the joint implementation of uplink resource determination and control channel repetition may result in ambiguity / misalignment regarding the uplink resources used to transmit HARQ-ACK information bits. In an example, a wireless device may receive DCI via a first core set from a plurality of core sets. The DCI may trigger the transmission of the HARQ-ACK information bits. In an implementation of the prior art, the wireless device may determine a first uplink resource for the transmission of the HARQ-ACK information bits based on the first core set. The wireless device may transmit the HARQ-ACK information bits via the first uplink resource. In an example, the base station may not have information regarding the core set on which the wireless device successfully received the DCI.

[0223] In an example, the base station may determine a second uplink resource based on a second core set from the plurality of core sets for reception of HARQ-ACK information bits. The base station may determine the second uplink resource based on the second core set, for example, randomly / blindly (or based on a rule unknown to the wireless device). The base station may monitor the second uplink resource for reception of the HARQ-ACK information bits. The first uplink resource determined by the wireless device and the second uplink resource determined by the base station may be different. Misalignment / ambiguity in the uplink resource may result in lost reception of the HARQ-ACK information bits. This may result in increased retransmissions, increased latency / delay for successful communication, and increased power consumption.

[0224] In an example, the base station may monitor the first uplink resource and the second uplink resource for reception of the HARQ-ACK information bits. This may increase power consumption at the base station. In an example, the wireless device may transmit the HARQ-ACK information bits via the first uplink resource and the second uplink resource. This may increase power consumption at the wireless device.

[0225] When the DCI that triggers the transmission of the HARQ-ACK information bits is transmitted by the base station via multiple core sets, the exemplary embodiment enhances / improves the uplink resource determination. In an exemplary embodiment, the wireless device and the base station can determine a selected core set among the multiple core sets based on predefined rules (e.g., the core set with the lowest core set index, or the core set with the lowest / highest bandwidth, or the core set monitored in the last monitoring opportunity, etc.). The wireless device and the base station can determine the uplink resources based on the selected core set for the HARQ-ACK information bits. This can reduce the possibility of misalignment on the uplink resources used to transmit the HARQ-ACK information bit symbols. This can reduce the wait time / delay for successful communication, reduce power consumption, and reduce retransmissions.

[0226] The wireless device may receive / detect DCI (e.g., DCI 1-0) scheduling a transport block (e.g., PDSCH) via the core set. The wireless device may receive DCI via the common search space set (CSS) of the core set. In the prior art, the wireless device may receive a transport block based on the lowest resource block (RB) of the core set.

[0227] In an example, a wireless device may receive configuration parameters, for example, from a base station. The configuration parameters may indicate control channel repetition, wherein the base station transmits multiple DCI / PDCCHs (or DCI repetitions) via multiple core sets. The repetitions may be transmitted in multiple transmission / repetition occasions (e.g., time slots). The wireless device may monitor multiple core sets for multiple DCI / PDCCHs (or DCI repetitions) in multiple transmission occasions. Therefore, control channel repetition may increase control channel reliability and robustness.

[0228] In the prior art, the combined implementation of resource block determination and control channel repetition may result in ambiguity / misalignment regarding the starting resource block for receiving a transport block. In an example, a wireless device may receive DCI scheduling a transport block via a first core set among multiple core sets. The wireless device may not receive (or may miss receiving) the DCI scheduling a transport block via a second core set among the multiple core sets. In prior art implementations, the wireless device may receive a transport block based on the lowest RB of the first core set. In an example, the base station may not have information regarding the core set from which the wireless device successfully received DCI.

[0229] In an example, the base station may transmit a transport block based on the lowest RB of the second core set. The base station may determine the lowest RB of the second core set, for example, randomly / blindly (or based on a rule unknown to the wireless device). The lowest RB of the first core set used by the wireless device to receive the transport block may be different from the lowest RB of the second core set used by the base station to transmit the transport block. Misalignment / ambiguity in the lowest RB may result in lost reception of the transport block. This may result in increased retransmissions, increased latency / delay for successful communication, and increased power consumption.

[0230] In an example, the base station may transmit a transport block based on the lowest RB of the first core set and the lowest RB of the second core set. This may increase power consumption at the base station. This may increase resource overhead.

[0231] When the DCI scheduling a transport block is transmitted by the base station via multiple core sets, the exemplary embodiment enhances / improves resource block determination. In an exemplary embodiment, the wireless device and the base station can determine a selected core set from the multiple core sets based on predefined rules (e.g., the core set with the lowest core set index, or the core set with the lowest / highest bandwidth, or the core set monitored in the last monitoring opportunity, etc.). The wireless device can receive the transport block based on the lowest RB of the selected core set, and the base station can transmit the transport block based on the lowest RB of the selected core set. This can reduce the possibility of misalignment on the lowest RB used to transmit / receive the transport block. This can reduce latency / delay for successful communication, reduce resource overhead, reduce power consumption, and reduce retransmissions.

[0232] The PDCCH may carry scheduling assignments and other control information in the form of a DCI message. The information carried by the PDCCH may be referred to as DCI. A base station may transmit multiple PDCCHs within a control region to a wireless device. The wireless device may monitor multiple PDCCHs. A PDCCH may include an aggregation of one or more control channel elements (CCEs). Monitoring may include performing blind decoding on multiple candidate PDCCHs. Blind decoding may include performing cyclic redundancy check (CRC) demasking on each of the multiple candidate PDCCHs using a radio network temporary identifier (RNTI). Blind decoding may be used to detect the PDCCH. If no CRC errors are detected, the wireless device may determine that the PDCCH carries its own control information.

[0233] Figure 17 Example configuration parameters for control and / or data according to one aspect of an embodiment of the present disclosure are shown. 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 a serving cell configuration (e.g., ServingCellConfig). The one or more parameters of the serving cell configuration may indicate one or more downlink bandwidth parts (e.g., a list of BWPs downlink). The one or more parameters of the serving cell configuration may indicate one or more uplink bandwidth parts (e.g., a list of BWPs uplink). The downlink bandwidth part (e.g., BWP downlink) and / or the uplink bandwidth part (e.g., BWP uplink) may include a bandwidth part index (e.g., bwp-Id), a configuration parameter for a cell-common downlink bandwidth part (e.g., BWP-DownlinkCommon), and / or a configuration parameter for a UE-specific downlink bandwidth part (e.g., BWP-DownlinkDedicated). For example, the bandwidth part index (bwp-Id) may indicate a bandwidth part configuration, where the bandwidth part index is the bandwidth part index. The bandwidth part configuration may include location and bandwidth information (locationAndBandwidth). The locationAndBandwidth field can indicate the starting resource block (RB) of the bandwidth portion and the bandwidth of the bandwidth portion based on a reference point (e.g., point A of the carrier / cell of the bandwidth portion). The bandwidth portion configuration can include subcarrier spacing (e.g., subcarrierSpacing) and a cyclic prefix (e.g., cyclicPrefix). For example, the subcarrier spacing can be one of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, and 960 kHz. For example, the cyclic prefix can be one of a normal cyclic prefix and an extended cyclic prefix.

[0234] Configuration parameters for the 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 the cell-specific downlink bandwidth portion (e.g., the initial BWP). For example, pdsch-ConfigCommon may include cell-specific parameters for receiving the PDSCH for transport blocks (TBs) via the cell-specific downlink bandwidth portion. Configuration parameters for the UE-specific downlink bandwidth portion (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 failure recovery in a secondary cell. For example, pdcch-Config may include parameters for receiving DCI for a UE-specific downlink bandwidth portion. For example, pdsch-Config may include parameters for receiving PDSCH for a TB in a UE-specific downlink bandwidth portion. For example, sps-Config may include parameters for receiving semi-persistently scheduled PDSCH. The base station may configure an SPS for a BWP or a list of SPSs for the BWP. For example, radioLinkMonitoringConfig may include parameters for radio link monitoring.

[0235] Configuration parameters for pdcch-Config may include at least one of a core set set, a search space set, downlink preemption (e.g., downlinkPreemption), transmit power control (TPC) for PUSCH (e.g., tpc-PUSCH), TPC for PUCCH, and / or TPC for SRS. Configuration parameters may include a list of search space switching groups (e.g., searchsSpaceSwitchingGroup), a search space switching timer (e.g., searchSpaceSwitchingTimer), uplink cancellation, and / or monitoring capability configuration (e.g., monitoringCapabilityConfig). The base station may configure a list of search space switching groups, where a wireless device may switch from a first search space group to a second search space group based on a search space switching timer or a rule, indication, or event. The base station may configure up to K (e.g., K=3) core sets for a cell's BWP. Downlink preemption may indicate whether to monitor a cell's downlink preemption indication. Monitoring capability configuration may indicate whether the wireless device's monitoring capabilities will be configured for the cell, where the capabilities are based on basic capabilities or advanced capabilities. The base station may configure up to M (e.g., M=10) search spaces for the BWP of a cell. tpc-PUCCH, tpc-PUSCH, or tpc-SRS may enable and / or configure the reception of TPC commands for PUCCH, PUSCH, or SRS, respectively. Uplink cancellation may indicate uplink cancellation for the monitoring cell.

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

[0237] Figure 18Example configuration parameters for a core set according to aspects of an embodiment of the present disclosure are shown. A 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 the same as the REG bundle (e.g., sameAsREG-bundle) and across all contiguous RBs (e.g., allContiguousRBs)). For example, when the precoder granularity is configured as 'sameAsREG-bundle', the wireless device may assume that the same precoder is used across the REGs in the bundle. For example, when the precoder granularity is configured as 'across all contiguous RBs,' the wireless device may assume that the RBs across contiguous RBs in a core set use the same precoder. A core set may include a list of TCI states, where the core set is not core set #0. A core set may include parameters for the presence of TCI in DCI. If a core set is configured with the presence of TCI in DCI, the wireless device may anticipate a DCI format that includes a TCI indication in the DCI based on the DCI format scheduled via the search space associated with the core set. For example, the DCI format may be DCI format 1_1 and / or DCI format 0_1. A core set may optionally include one or more of a DMRS scrambling identifier, a core set pool index, an enhanced core set index (e.g., ControlResourceSetId-v16xy), TCI appearing in the DCI for DCI format 1_2, and an RB offset. For example, when the 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 may indicate a value between [0, ..., 15], and the core set index may indicate a value between [0, ..., 11].

[0238] A core set is associated with a search space, wherein the wireless device can determine search space candidates and / or monitoring timings for the search space based on the configuration of the search space and the core set. A search space is associated with a core set, wherein the wireless device can determine search space candidates and / or monitoring timings for the search space 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, parameters of the search space may include an index of the core set.

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

[0240] The configuration parameters of pdsch-Config may include parameters for receiving transport blocks. For example, the configuration parameters may include a data scrambling identifier for PDSCH, a DM-RS mapping type (e.g., between mapping type A and mapping type B), a list of transmission configuration indicator (TCI) states, parameters for a (virtual RB) VRB to (physical RB) PRB interleaver, a resource allocation type (e.g., resource allocation type 0, resource allocation type 1, or dynamic switching between the two), a list of time domain allocations, an aggregation factor, a list of rate matching modes, an RBG (resource block group) size, an MCS table (e.g., between QAM 256 and QAM 64 Low SE, between high MCS and low MCS), a maximum codeword (e.g., between 1 and 2), parameters related to PRB bundling, a maximum MIMO layer, a minimum scheduling offset related to power saving techniques, and / or one or more parameters related to DCI formats 1_2 (e.g., compact DCI or small DCI formats).

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

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

[0243] In an example, the PDCCH may be carried on one or more control resource sets (core sets). A core set may 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 may be a multiple of 6 RBs (e.g., 6, 12, 18, etc.). For example, N_symbol_coreset may be 1, 2, or 3. A CCE may include M (e.g., M=6) resource element groups (REGs). For example, during one OFDM symbol, one REG may include one RB. The REGs in the core set may be sorted / numbered in ascending order in a time-first manner, starting with 0 for the first OFDM symbol and the lowest-numbered (e.g., lowest-frequency) RB in the core set. The wireless device may increase the number in the first OFDM symbol by increasing the frequency position or RB index. In response to all RBs in the first symbol being indexed, the wireless device may move to the next symbol. The wireless device may map one or more REG indices to one or more of the N_rb_coreset RBs within the N_symbol_coreset OFDM symbols of the core set.

[0244] In an example, the wireless device may receive configuration parameters from a base station. The configuration parameters may indicate one or more core sets. A core set may be associated with one CCE to REG mapping. For example, a single core set may have a single CCE mapping to the physical RBs / resources of the single core set. For example, the CCEs to REGs of a core set may be interleaved or non-interleaved. For example, a REG bundle may include L consecutive REGs (e.g., iL, iL+1…iL+L-1). For example, L may 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 (e.g., i) of the REG bundle may be in the range of [0, 1, …N_reg_coreset / L-1]. For example, N_reg_coreset may be defined as N_rb_coreset * N_symbol_coreset (e.g., the total number of REGs in a single core set). For example, the j-th index CCE may include one or more REG bundles of {f(6j / L), f(6j / L+1), …, f(6j / L + 6 / L-1)}. For example, f(x) may be an interleaver function. In an example, when the CCE to REG mapping may be non-interleaved, f(x) may be x (e.g., the j-th CCE may include 6j / L, 6j / L+1…, and 6j / L+6 / L-1). When the CCE to REG mapping may be interleaved, when N_symbol_coreset is 1, L may be defined as one of {2, 6}, or when N_symbol_coreset is 2 or 3, L may be defined as one of {N_symbol_coreset, 6}. When the CCE to REG mapping may be interleaved, the function f(x) may 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}.

[0245] For example, the configuration parameters may include frequencyDomainResources that may define N_rb_coreset. The configuration parameters may include a duration that may define N_symbol_coreset. The configuration parameters may include a cce-REG-MappingType that may be selected between staggered or non-staggered mapping. The configuration parameters may include a reg-BundleSize that may define a value of L for staggered mapping. For non-staggered mapping, L=6 may be predetermined. The configuration parameters may include a shiftIndex that may determine n_shift as one of {0, 1, …, 274}. When the precoder granularity (e.g., the precoder granularity indicated / configured by the configuration parameters) is configured as sameAsREG-bundle, the wireless device may determine / assume the same precoding for the REGs within a REG bundle. When the precoder granularity is configured as allContiguousRB, the wireless device may determine / assume the same precoding for all REGs within a set of contiguous RBs of a core set.

[0246] For the first core set (eg, CORESET#0), it may be defined / configured with L=6, R=2, n_shift=cell ID, and precoderGranularity=sameAsREG-bundle.

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

[0248] In an example, control channel repetitions may be transmitted via multiple PDCCHs. For example, a PDCCH may indicate a physical control channel transmitted in a search space candidate. The search space candidate may include one or more CCEs based on an aggregation level. Multiple PDCCHs may be transmitted via multiple core sets of multiple cells. For example, a base station may transmit a PDCCH in multiple PDCCHs via a core set of cells in multiple cells. Multiple PDCCHs may be transmitted via multiple core sets of cells. For example, a base station may transmit a PDCCH in multiple PDCCHs via a core set in multiple core sets. Multiple PDCCHs may be transmitted via multiple search spaces, wherein the PDCCHs in the multiple PDCCHs may be transmitted via search spaces in multiple search spaces. Multiple PDCCHs may be transmitted via multiple search space candidates, wherein each of the multiple PDCCHs may be transmitted via a corresponding search space candidate in the multiple search space candidates. Multiple search space candidates may belong to a single search space or multiple search spaces. A search space may include a set of search space candidates at a monitoring opportunity. A monitoring opportunity of a search space may refer to a timing opportunity at which a wireless device may monitor a search space candidate for receiving DCI / PDCCH.

[0249] In an example, a PDCCH among multiple PDCCHs used for control channel repetition may convey / transmit DCI based on a DCI format. For example, a first DCI of a first PDCCH among the multiple PDCCHs may be identical to a second DCI of a second PDCCH among the multiple PDCCHs. For example, the content of the first DCI / PDCCH may be identical to the content of the second DCI / PDCCH. Based on the identical content of the multiple PDCCHs, the wireless device may aggregate the multiple DCI / PDCCHs before decoding the DCI / PDCCHs. For example, when control channel repetition is transmitted / performed via DCI / PDCCHs with identical content, the wireless device may need to determine a reference frequency domain resource (e.g., a reference downlink control signal / channel transmission / repetition timing) and / or a reference time domain resource (e.g., a reference downlink control signal / channel transmission / repetition timing) and / or a reference CCE index and / or a reference REG index. For example, the wireless device may determine an aggregated DCI / PDCCH by aggregating the multiple DCI / PDCCHs. The wireless device may decode the aggregated DCI / PDCCH.

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

[0251] Reference frequency-domain (and / or time-domain) resources for multiple DCI / PDCCHs may be determined based on search space indices of one or more search spaces used to transmit the multiple DCI / PDCCHs. For example, the minimum (or maximum) index of the one or more search spaces may be used for this determination. Reference frequency-domain resources for the multiple DCI / PDCCHs may be determined based on cell indices of the one or more cells that transmit the multiple DCI / PDCCHs. For example, the minimum (or maximum) index of the one or more cells may be used for this determination. Similarly, reference time-domain resources and / or reference CCE indices and / or reference REGs may be determined based on a core set index, a search space index, and / or a cell index. A combination of transmission time, core set index, search space index, and / or cell index may be used. For example, reference frequency-domain resources may be first determined based on the transmission time of the DCI / PDCCH. When multiple DCI / PDCCHs are transmitted simultaneously, the wireless device may use the core set index, search space index, and / or cell index to further identify a reference DCI / PDCCH among the multiple DCI / PDCCHs. The wireless device may determine a reference DCI / PDCCH for determining a reference frequency domain resource, a reference time domain resource, a reference CCE index, and / or a reference REG index.

[0252] In an example, a base station may configure / indicate a maximum number of repetitions, K, for control channel repetitions via a configuration parameter. The base station may transmit a number of repetitions, M, that is less than K. In response to M being less than K, the wireless device may determine a reference DCI / PDCCH based on a candidate DCI / PDCCH in the Kth repetition, regardless of whether the Kth repetition has actually been transmitted (or whether the Kth repetition has actually been received). The wireless device may determine the reference DCI / PDCCH based on the first DCI / PDCCH, which is the first repetition. The wireless device may determine the reference DCI / PDCCH based on the last DCI / PDCCH actually transmitted (e.g., the Mth repetition). For convenience, this type of control channel repetition (e.g., repeating the same content on multiple DCI / PDCCHs) may be referred to as a first control channel repetition mode (e.g., mode 1, repetition mode 1, or first repetition mode). In an example, the base station may configure a list of time-domain resource allocation entries. The time-domain resource allocation entries may 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 of the control channel may represent a repetition number K. Based on the repetition number, the wireless device may determine a reference DCI / PDCCH timing based on the Kth DCI / PDCCH repetition. The repeated DCI / PDCCH may indicate an entry in the time domain resource allocation entry list.

[0253] In an example, a first DCI / PDCCH among the multiple DCI / PDCCHs may be different from a second DCI / PDCCH among the multiple DCI / PDCCHs. For example, the wireless device may not aggregate the first DCI / PDCCH with the second DCI 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, the wireless device may complete decoding of the control channel repetition when it has received at least one DCI / PDCCH among the multiple DCI / PDCCHs. For example, when the wireless device has received at least one DCI / PDCCH among the multiple DCI / PDCCHs, the wireless device may be able to receive or transmit TBs scheduled by the multiple DCI / PDCCHs. In the specification, this type of control channel repetition (e.g., transmitting potentially different content via multiple DCI / PDCCHs, where the DCI / PDCCHs among the multiple DCI / PDCCHs may schedule one or more resources of a transport block) may be referred to as a second control channel repetition mode (e.g., mode 2, repetition mode 2, second repetition mode). For example, the reference DCI / PDCCH among the plurality of DCI / PDCCHs based on the second control channel repetition pattern may be every DCI / PDCCH received by the wireless device.

[0254] Figure 19 An example of PDCCH repetition according to one aspect of an embodiment of the present disclosure is shown. A 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 PDCCHs / DCI for repeated control channels (or control channel repetitions). The parameters may also include one or more search spaces for control channel repetition. Figure 19 An example is shown of enabling control channel repetition via the first search space (SS#1) of a first carrier / cell (DL carrier #0). Parameters may indicate one or more indices of one or more search spaces of the first carrier and / or a carrier / cell index of the first carrier. The base station may transmit a first PDCCH via the first search space of the first carrier, with the first PDCCH scheduling TBs via the first carrier. The base station may transmit a second PDCCH via the first search space of the first carrier, with the second PDCCH scheduling TBs via the first carrier. The first and second PDCCHs may be transmitted via multiple monitoring opportunities in the first search space. The wireless device may aggregate the first and second PDCCHs based on the first control channel repetition pattern, or may attempt to receive / decode each PDCCH independently based on the second control channel repetition pattern. The wireless device may receive TBs based on the first and / or second PDCCHs.

[0255] In an example, a base station may transmit one or more RRC messages indicating control channel repetition enabled for a first carrier / cell. Based on the indication of the control channel repetition, the wireless device may determine one or more first search spaces for the first carrier / cell for the control channel repetition 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-fallback 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 an example, the one or more RRC messages may indicate one or more search space indices for the one or more first search spaces for the control channel repetition. The one or more RRC messages may indicate one or more DCI formats in which the wireless device may apply the control channel repetition. The wireless device may determine the one or more first search spaces for the first carrier / cell based on the one or more DCI formats for the control channel repetition.

[0256] In an example, a base station may transmit multiple DCI / PDCCHs via multiple Transition Relays (TRPs), multiple core set pools, or multiple core set groups to schedule resources for transport blocks for a cell. For example, the base station may configure a first TRP (or first core set pool) for a first cell via one or more RRC messages. The one or more RRC messages may include configuration parameters. The configuration parameters may include a first core set pool for the first cell. The 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 Transition Relay Relay (TRP) for the first cell. The base station may transmit a first DCI / PDCCH via a first search space of a first core set of the first core set pool. The base station may 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 may schedule resources for a transport block. The first / PDCCH and the second DCI / PDCCH may be repeated transmissions of control information (e.g., DCI). For example, a transport block may be transmitted via a first TRP and a second TRP. Transport blocks may be transmitted based on multiple TCI states. The transport block may be transmitted based on a TCI state, where the TCI state is associated with a plurality of TCI states. For example, the transport block may be transmitted via a first TRP or a second TRP.

[0257] A configuration parameter may indicate control channel repetition enabled / configured for the first cell. For example, a parameter for a control channel repetition mode may be configured. The control channel repetition mode may be a first control channel repetition mode or a second control channel repetition mode. The configuration parameter may indicate a first core set associated with (or configured with, or belonging to) a first core set pool. The configuration parameter may indicate a second core set associated with (or configured with, or belonging to) a second core set pool. The wireless device may determine, based on a rule, a pair of the first core set and the second core set, in which repeated DCI / PDCCHs may be transmitted. For example, the wireless device may determine the first core set of the first core set pool based on a search space associated with the first core set, where the wireless device may monitor a DCI format via the search space. For example, the DCI format may be DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 (or DCI format 3_0 or DCI format 3_1). When there are multiple first search spaces for a first core set pool configured with a DCI format, the wireless device may determine multiple first core sets for the first core set pool. Similarly, the wireless device may determine a second core set for a second core set pool based on a search space associated with the second core set, where the wireless device may monitor the DCI format via the search space. When there are multiple second search spaces for a second core set pool configured with a DCI format, the wireless device may determine multiple second search spaces. In an example, the wireless device may be configured with at most one search space for a DCI format in each core set pool.

[0258] In an example, the wireless device may determine a second core set in a second core set pool based on a first core set index of a first core set in a first core set pool. For example, the second index of the second core set may be the first core set index + a gap (GAP). For example, the GAP may be a determined / predetermined value (e.g., 0, 12). For example, the configuration parameters may include a parameter indicating the value of the GAP. In an example, the wireless device may determine the second core set based on a second search space associated with the second core set and the first search space. For example, the index of the second search space may be the first index of the first search space + the SS-GAP. For example, the SS-GAP may be a predetermined value (e.g., 20, 0). For example, the wireless device may determine the second core set and / or the second search space based on an association configured by the configuration parameters. For example, the configuration parameters may indicate an association between each core set / search space in the core sets / search spaces associated with the first core set pool and each core set / search space in the core sets / search spaces associated with the second core set pool. In an example, the configuration parameters may include the first core set and / or the first search space in the first core set pool. The wireless device may monitor the first DCI / PDCCH via the first search space in the first core set pool. The configuration parameters may indicate / include a parameter indicating control channel repetition across multiple TRPs or multiple core set pools for a first core set or first search space. Based on the parameter, the wireless device may determine a second search space for a second core set or 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.

[0259] In an example, a 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 via multiple TRPs. The base station may transmit one of multiple RRC messages and / or MAC CEs indicating 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 for 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 the multiple TRPs. For example, the repetition pattern (e.g., a 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 indicating the number of control channel repetitions via the configuration parameters. Each bit of the bitmap may indicate which TRP may transmit the i-th repetition. The repetition pattern may be [0, 1, 0, 1, …, 0, 1]. The repetition pattern may be [0, 0, …,0, 1, 1, …,1, 0, 0, …, 0, 1, 1, …, 1]. Various repetition patterns may be considered. Based on the repetition pattern, the wireless device may receive control channel repetitions based on a TCI state from among a plurality of TCI states. For example, when the repetition pattern indicates a first TRP, the wireless device may receive control channel repetitions based on the first TCI state. When the repetition indicates a second TRP, the wireless device may receive control channel repetitions based on the second TCI state.

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

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

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

[0263] In an example, a configuration parameter may indicate / include search spaces associated with a first core set and a second core set. The configuration parameter may include multiple core set indices. The configuration parameter may include a core set index indicating the first core set from the multiple core set indices. The configuration parameter may include one or more indices of repeated / additional core sets (e.g., core sets used for control channel repetition in addition to the first core set and the second core set) from the multiple core set indices. For example, an index from the 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 repetition, the first parameters of the first core set and the second parameters of the second core set may have configuration restrictions. 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 in the frequency domain of the second core set (or a subset or superset of the set of resource blocks). The wireless device may determine the set of RBs belonging to the first core set and the second core set for control channel repetition. 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 may be the same as (or less than or greater than) the number of CCEs in the second core set. The wireless device may 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 (e.g., between interleaved and non-interleaved) of the first core set may 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 may 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 may be the same as the second TCI-PresenceInDCI of the second core set. For example, the first RB offset of the first core set may be the same as the second RB offset of the second core set.

[0264] The first core set and the second core set may have different configurations for one or more parameters. For example, the one or more parameters may include one or more TCI states. For example, the one or more parameters may include a DM-RS scrambling identifier (e.g., pdcch-DMRS-ScramblingID). For example, the one or more parameters may include a core set pool index (e.g., coresetPoolIndex). For example, the one or more parameters may include a core set index.

[0265] When the wireless device receives 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 of the first core set is equal to or less than (or greater than) a second number of CCEs of the second core set. Based on this determination, the wireless device may determine that the first core set and the second core set can be used for control channel repetition. Otherwise, the wireless device may determine that the first core set and the second core set cannot be used for control channel repetition. Alternatively, the wireless device may determine a 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 the one or more core sets). For example, the 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 the one or more core sets for control channel repetition.

[0266] In an example, the wireless device may determine the number of REGs for a first core set of one or more core sets configured for control channel repetition. The wireless device may determine a second number of REGs for a second core set of the one or more core sets. The wireless device may determine whether the number of REGs is equal to the second number of REGs. In response to determining that the number of REGs is equal to the second number of REGs, the wireless device may consider control channel repetition to be configured via the first core set and the second core set. Otherwise, the wireless device may consider the configuration to be an error condition and may not activate control channel repetition via the first core set and the second core set. In an example, the wireless device may determine a minimum number of REGs for the one or more core sets (e.g., determine a core set with a minimum number of REGs). The wireless device may assume the minimum number of REGs for control channel repetition.

[0267] The search space configuration parameters associated with the first core set and the second core set may include / indicate a switching pattern or mapping pattern between the first core set and the second core set. For example, the wireless device may determine a search space monitoring opportunity based on the search space configuration parameters. The wireless device may determine the search space monitoring opportunity based on the first core set. The wireless device may determine a second search space monitoring opportunity or an extended monitoring opportunity based on a rule. For example, the wireless device may determine the second search space monitoring opportunity as the next time slot after the first monitoring opportunity. The wireless device may determine the second search space monitoring opportunity based on the second search space. The configuration parameters may indicate a bitmap of multiple OFDM symbols in a time slot (or a bitmap of a number of time slots (e.g., multiple time slots)). For each corresponding OFDM symbol or time slot, the bitmap may 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 may monitor the search space monitoring opportunity based on the first core set. When 1 is indicated for a second OFDM symbol, the wireless device may monitor the second search space monitoring opportunity based on the second core set.

[0268] In an example, a wireless device may receive one or more RRC messages including configuration parameters. The configuration parameters may indicate / include a core set of a cell bandwidth portion. The configuration parameters may include parameters of a 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 time slot 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 OFDM symbol, 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 repeated DCI / PDCCHs 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.

[0269] For example, the wireless device may receive / monitor a first DCI / PDCCH in one or more repeated DCI / PDCCHs via a first monitoring opportunity in one or more monitoring opportunities. The wireless device may receive / monitor a second DCI / PDCCH in one or more repeated DCI / PDCCHs via a second monitoring opportunity in one or more monitoring opportunities. 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 resources for a transport block. The wireless device may receive / monitor DCI via one or more monitoring opportunities, wherein the search space candidates for the DCI may include one or more candidates for one or more monitoring opportunities. For example, the search space candidates may include a first candidate for the first monitoring opportunity and a second candidate for the second monitoring opportunity. For example, the first starting CCE index of the first candidate for the first monitoring opportunity may be the same as the second starting CCE index of the second candidate for the second monitoring opportunity.

[0270] The wireless device may receive / monitor DCI / PDCCH via one or more monitoring occasions, wherein the search space candidates of the DCI / PDCCH may include one or more CCEs from the one or more monitoring occasions.

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

[0272] Figure 21 An example of control channel repetition according to one aspect of an embodiment of the present 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 indicating one or more monitoring opportunities for control channel repetition. Figure 21The bitmap size is shown as 14 (e.g., the bitmap corresponds to a time slot where each bit is mapped to each OFDM symbol). The bitmap indicates monitoring opportunities for the first OFDM symbol and the sixth OFDM symbol of the time slot. The configuration parameters may indicate / include a first monitoring period as two time slots (e.g., monitoring every second time slot). In each monitoring period, the wireless device may determine one or more monitoring opportunities based on the bitmap. For example, when the bitmap is not present, the wireless device may determine the monitoring opportunity starting from the first OFDM symbol of the time slot. Figure 21 In an example, the wireless device may determine a first monitoring opportunity and a second monitoring opportunity based on a bitmap in each monitoring period. The wireless device may monitor the first monitoring opportunity and the second monitoring opportunity to receive one or more DCI / PDCCHs that schedule a transport block.

[0273] In an example, a configuration parameter indicates one or more monitoring opportunities within a monitoring period for a search space. For example, monitoringSlotPeriodicityAndOffset may determine the monitoring period. When the parameter may include monitoringSymbolWithinSlot, the wireless device may determine the monitoring period based on the gap between each monitoring opportunity within a timeslot based on monitoringSymbolWithinSlot. The wireless device may desire equal spacing between monitoring opportunities within a timeslot. Alternatively, when the search space is used for control channel repetition, the parameter may not include monitoringSymbolsWithinSlot. In an example, when control channel repetition is enabled, monitoringSymbolsWithinSlot may be used to indicate one or more monitoring opportunities within a monitoring period determined based on monitoringSlotPeriodicityAndOffset. For example, a parameter indicating the enablement of control channel repetition may be configured for a search space, a core set associated with the search space, or a DCI format monitored via the search space. For example, the duration of the search space may be used to determine one or more monitoring opportunities within a monitoring period. For example, when the monitoring period is greater than a timeslot, the wireless device may 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 may determine a first monitoring opportunity among one or more monitoring opportunities based on monitoringSlotPeriodicityAndOffset. The wireless device may determine a second monitoring opportunity among the one or more monitoring opportunities as the next time slot after the first monitoring opportunity. The wireless device may determine D monitoring opportunities starting from the first monitoring opportunity in consecutive time slots. For example, when the search space is configured / associated with multiple core sets, the search space may include multiple control resource set IDs (e.g., controlResourceSetID and a second controlResourceSetID).

[0274] In an example, the base station may transmit a first DCI / PDCCH via a first monitoring opportunity in one or more monitoring opportunities. The base station may transmit a second DCI / PDCCH via a second monitoring opportunity in one or more monitoring opportunities. The first DCI / PDCCH and the second DCI / PDCCH may indicate the same resources for 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 wireless device may attempt to decode the first DCI / PDCCH independently of the second DCI / PDCCH. The wireless device may not assume that the base station may transmit the first DCI / PDCCH and the second DCI / PDCCH. The base station may transmit one or more DCI / PDCCHs on one or more monitoring opportunities. The base station may transmit a single DCI / PDCCH on one or more monitoring opportunities. The base station may transmit a DCI / PDCCH on each monitoring opportunity. The base station may transmit any number of repeated DCI / PDCCHs on one or more monitoring opportunities.

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

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

[0277] In an example of determining one or more search space candidates for aggregation levels across one or more monitoring occasions, the base station may indicate four monitoring occasions in a monitoring cycle indexed from the first to the fourth monitoring occasions. In this example, it is assumed that the set of candidates for the aggregation levels is consistent across the four monitoring occasions. For example, the first candidate for aggregation level 2 may begin at the third CCE, and the second candidate for aggregation level 2 may begin at the fifth CCE. For example, the first candidate for aggregation level 4 may begin at N_CCE (e.g., the number of CCEs) – the eighth CCE, and the second candidate for aggregation level 4 may begin at N_CCE – the fourth CCE. The wireless device may determine a candidate list with aggregation level 8 by combining / aggregating four candidates for aggregation level 2 (each candidate from one monitoring occasion) and / or by combining / aggregating two candidates for aggregation level 4 (each candidate from one monitoring occasion). In this example, the first box on the left and the second small box on the right illustrate AL = 8 candidates. The wireless device may determine more candidates by aggregating / combining the second candidate for AL = 2 and / or the second candidate for AL = 4. Similarly, the wireless device may determine candidates for aggregation level (AL) = 16 by combining / aggregating the four candidates for AL = 4. The wireless device may determine both AL=16.

[0278] The wireless device may not aggregate candidates, where the candidates may not include candidates from the first monitoring opportunity (or the first monitoring opportunity, which is the earliest monitoring opportunity in the monitoring cycle). The wireless device may determine possible aggregation levels and / or candidates by aggregating candidates from the first monitoring opportunity, the first + second monitoring opportunities, the first + second + third + fourth monitoring opportunities, the first + second + third + fourth + fifth - sixth + seventh + eighth, and so on.

[0279] In an example, the wireless device may determine a candidate list for the aggregation level based on a hash function applied in each time slot. When the first monitoring opportunity and the second monitoring opportunity are in the same time slot, the same candidate may be mapped. Otherwise, different candidates may be determined. The base station may transmit DCI on the candidates across one or more monitoring periods.

[0280] In an example, a base station may transmit one or more messages including configuration parameters. The configuration parameters may include / indicate a search space group for control channel repetition. A search space group may include one or more search spaces. For example, a search space group may include a first search space for a first carrier and a second search space for a second carrier. For example, a search space group may include a first search space for a first BWP of a cell and a second search space for a second BWP of a cell. For example, a search space group may include a first search space for a first BWP of the first cell and a second search space for a second BWP of the second cell. For example, a configuration parameter may indicate one or more search space groups for a BWP of a cell. A search space group in the one or more search space groups may be associated with / configured with one or more DCI formats. In an example, a wireless device may determine a search space group based on one or more search spaces configured with / associated with a BWP of a cell, where each of the one or more search spaces may be configured to monitor a DCI format from the one or more DCI formats. For example, the one or more DCI formats may include DCI format 1_1 and DCI format 0_1. For example, the 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 for non-fallback DCI. For example, one or more DCI formats may include downlink / uplink DCI for fallback DCI. For example, one or more DCI formats may include a DCI format for sidelink DCI.

[0281] The wireless device may determine search space candidates for one or more search spaces of a search space group based on multiple core sets in a similar manner as for controlling repetitions. In an example, the wireless device may determine one or more monitoring opportunities in a time slot based on the one or more search spaces. For example, in time slot n, the wireless device may determine one or more first monitoring opportunities based on a first search space in the one or more search spaces. The wireless device may determine one or more second monitoring opportunities in time slot n based on a second search space in the one or more search spaces. The wireless device may monitor the one or more first monitoring opportunities and the one or more second monitoring opportunities in time slot n. The wireless device may not desire a time domain overlap between a monitoring opportunity of one of the one or more search spaces and a second monitoring opportunity of a second search space in the one or more search spaces. The wireless device may monitor DCI based on one or more repetitions of a DCI format via the one or more monitoring opportunities in the time slot.

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

[0283] In an example, the base station may associate multiple TCI states with a core set as the active TCI state. Figure 22 An example of a core set associated with multiple TCI states as active TCI states, according to one aspect of an embodiment of the present disclosure, is shown. In this example, a base station may indicate multiple monitoring opportunities within a time slot or a monitoring period for control channel repetition. A wireless device may monitor a first monitoring opportunity based on a first TCI state from the multiple TCI states. The wireless device may monitor a second monitoring opportunity based on a second TCI state from the multiple TCI states. The base station may indicate a switching pattern between the multiple TCI states. For example, a configuration parameter of a search space associated with the core set may include or indicate enabling control channel repetition. The configuration parameter may include or indicate enabling TCI switching or enabling control channel repetition across multiple TCI states. The configuration parameter may include or indicate a switching pattern. For example, the switching pattern may include alternating between a first TCI state from the multiple TCI states and a second TCI state from the multiple TCI states in each of one or more monitoring opportunities within a monitoring period or time slot or slots (e.g., between monitoring periods configured by the MonitoringSlotPeriodicityAndOffset parameter of the search space). For example, the switching pattern may be a 50 / 50 split between the first TCI state and the second TCI state. For example, the number of the one or more monitoring opportunities is K. The wireless device may monitor the first layer (K / 2) monitoring opportunities based on the first TCI state. The wireless device may monitor the remaining monitoring opportunities based on the second TCI state within the monitoring period. For example, the switching pattern may be a bitmap to indicate the TCI state in each of the one or more monitoring opportunities.

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

[0285] Figure 24 is an example of repeatedly determining uplink resources using a control channel according to one aspect of an embodiment of the present disclosure.

[0286] Figure 26 is an example of repeatedly determining downlink resources using a control channel according to one aspect of an embodiment of the present disclosure.

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

[0288] In an example, one or more configuration parameters may be cell-specific. In an example, at least one of the one or more configuration parameters may be cell-specific. In an example, the cell may be a primary cell (PCell). In an example, the cell may be a secondary cell (SCell). The cell may be a secondary cell configured with a PUCCH (e.g., a PUCCH SCell). In an example, the cell may be, for example, an unlicensed cell operating in an unlicensed frequency band. In an example, the cell may be, for example, a licensed cell operating in a licensed frequency band. In an example, the cell may operate in a first frequency range (FR1). For example, FR1 may include frequency bands below 6 GHz. In an 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 an example, a wireless device may perform uplink transmissions (e.g., PUSCH, PUCCH, SRS) via a cell at a first time and at a first frequency. The wireless device may perform downlink receptions (e.g., PDCCH, PDSCH) via the cell at a second time and at a second frequency. In an example, the cell may operate in time division duplex (TDD) mode. In TDD mode, the first frequency and the second frequency may be the same. In TDD mode, the first time and the second time may be different. In an example, the cell may operate in frequency division duplex (FDD) mode. In FDD mode, the first frequency and the second frequency may be different. In FDD mode, the first time and the second time may be the same.

[0290] In an example, the wireless device may be in RRC connected mode.

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

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

[0293] In an example, a cell may include multiple BWPs. The multiple BWPs may include one or more uplink BWPs, the one or more uplink BWPs including the uplink BWP of the cell. The multiple BWPs may include one or more downlink BWPs, the one or more downlink BWPs including the downlink BWP of the cell.

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

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

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

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

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

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

[0300] In an example, one or more configuration parameters may indicate a plurality of core sets. One or more configuration parameters may indicate a plurality of core sets for a (active) downlink BWP of a cell. In an example, a (active) downlink BWP of a cell may include a plurality of core sets. The plurality of core sets may include a first core set (e.g., Figure 24 and Figure 26 The plurality of core sets may include a second core set (e.g., Figure 24 and Figure 26 Core set 2).

[0301] In an example, one or more configuration parameters may indicate a core set index of the plurality of core sets (e.g., provided by a higher layer parameter ControlResourceSetId). In an example, each core set in the plurality of core sets may be identified / indicated by a corresponding core set index in the plurality of core set indexes. In an example, a first core set in the plurality of core sets (e.g., Figure 24 and Figure 26 A core set 1 in a plurality of core sets may be identified by a first core set index in the plurality of core set indexes. A second core set in the plurality of core sets (e.g., Figure 24 and Figure 26 The core set 2) in may be identified by a second core set index in the plurality of core set indices.

[0302] In an example, the coreset index may be a coreset identifier / indicator.

[0303] In an example, the first core set and the second core set may be different.The first core set index and the second core set index may be different.

[0304] In an example, one or more configuration parameters may indicate, for example, multiple search space sets for a cell's downlink BWP (e.g., via a higher layer parameter SearchSpace). In an example, one or more configuration parameters may indicate, for example, multiple search space sets for a cell (e.g., via a higher layer parameter SearchSpace).

[0305] In an example, one or more configuration parameters may indicate a search space set index / identifier for a plurality of search space sets (e.g., provided by a higher-layer parameter searchSpaceId). In an example, each search space set in the plurality of search space sets may be identified by a corresponding search space set index in a search space set index. In an example, a first search space set in the plurality of search space sets may be identified by a first search space set index in the search space set index. In an example, a second search space set in the plurality of search space sets may be identified by a second search space set index in the search space set index.

[0306] In an example, one or more configuration parameters may indicate a PDCCH monitoring period (e.g., monitoringSlotPeriodicityAndOffset) for a plurality of search space sets. One or more configuration parameters may indicate a corresponding PDCCH monitoring period in the PDCCH monitoring period (e.g., monitoringSlotPeriodicityAndOffset) for each search space set in the plurality of search space sets. One or more configuration parameters may indicate a first PDCCH monitoring period (e.g., 2 slots) for a PDCCH monitoring period for a first search space set in the plurality of search space sets. One or more configuration parameters may indicate a second PDCCH monitoring period (e.g., 10 slots) for a PDCCH monitoring period for a second search space set in the plurality of search space sets.

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

[0308] In an example, based on a search space set associated (or linked) with a core set, the wireless device may monitor for PDCCH candidates in a PDCCH monitoring opportunity for / of a search space set associated (or linked) with the core set for downlink control signals / channels (e.g., DCI, PDCCH, RS, GC-PDCCH, DMRS, etc.). In an example, based on a search space set associated (or linked) with a core set, the wireless device may monitor for PDCCH candidates in a PDCCH monitoring opportunity for / of a search space set in the core set associated (or linked) with the search space set for DCI. In an example, based on a search space set associated (or linked) with a core set, the wireless device may monitor for DCI a PDCCH of a search space set in the core set associated (or linked) with the search space set.

[0309] The wireless device may monitor downlink control channels in a core set of multiple core sets for DCI. Monitoring the downlink control channels in the core set for DCI may include monitoring one or more PDCCH candidates for the DCI in one or more PDCCH monitoring opportunities for / of one or more search space sets associated with the core set. The multiple search space sets may include one or more search space sets. One or more configuration parameters may indicate the one or more search space sets for the core set. The wireless device may determine one or more PDCCH monitoring opportunities for the one or more search space sets based on one or more PDCCH monitoring periods (e.g., monitoringSlotPeriodicityAndOffset) of the one or more search space sets. The PDCCH monitoring period may include one or more PDCCH monitoring periods.

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

[0311] In an example, one or more first search space sets in a plurality of search space sets may be associated with (or linked to) a first core set. One or more configuration parameters may indicate a first core set (or a first core set index of the first core set) for the one or more first search space sets. One or more configuration parameters may indicate a first core set (or a first core set index of the first core set) for each of the one or more search space sets. For the first core set, one or more configuration parameters may indicate the one or more first search space sets. One or more second search space sets in a plurality of search space sets may be associated with (or linked to) a second core set. One or more configuration parameters may indicate a second core set (or a second core set index of the second core set) for one or more second search space sets. One or more configuration parameters may indicate a second core set (or a second core set index of the second core set) for each of the one or more second search space sets. For the second core set, one or more configuration parameters may indicate one or more second search space sets.

[0312] The wireless device may monitor, for the DCI, one or more PDCCH candidates in one or more first PDCCH monitoring occasions for / of one or more first search space sets associated with the first core set.

[0313] The wireless device may monitor, for the DCI, one or more PDCCH candidates in one or more second PDCCH monitoring occasions for / of one or more second search space sets associated with the second core set.

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

[0315] In an example, one or more configuration parameters may indicate a number of repetitions for the control channel repetitions.

[0316] In an example, one or more configuration parameters may indicate a number of repetitions of control channel repetitions for a plurality of core sets. One or more configuration parameters may indicate a number of repetitions of control channel repetitions for each core set in the plurality of core sets. In an example, one or more configuration parameters may indicate a number of repetitions of control channel repetitions for a plurality of search space sets in the plurality of core sets. One or more configuration parameters may indicate a number of repetitions of control channel repetitions for a corresponding search space set in each core set in the plurality of core sets. In an example, one or more configuration parameters may indicate a number of repetitions of control channel repetitions for at least one search space set in the plurality of search space sets.

[0317] In an example, the one or more configuration parameters may indicate a plurality of core sets for control channel repetition.The one or more configuration parameters may link / map / associate the plurality of core sets for control channel repetition.

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

[0319] In an example, the number of repetitions may be, for example, the number of repetitions of a downlink control signal / channel (eg, PDCCH, DCI). The base station may transmit multiple DCI / PDCCHs (eg, Figure 24 and Figure 26 1 and DCI 2 in ). The wireless device may monitor PDCCH candidates for multiple DCI / PDCCHs (or for repetitions of downlink control signals / channels). The number of multiple DCI / PDCCHs may be equal to the number of repetitions (e.g., Figure 24 and Figure 26 The number of repetitions is equal to 2). The multiple DCI / PDCCHs may include a first downlink control signal / channel (eg, Figure 24 and Figure 26 1) and a second downlink control signal / channel (e.g., Figure 24 and Figure 26 DCI 2 in ).

[0320] In an example, a wireless device may be comprised of multiple TRPs (e.g., Figure 24 and Figure 26 Each downlink control signal / channel of the multiple DCI / PDCCHs may be transmitted by a corresponding TRP in the multiple TRPs. For example, in Figure 24 and Figure 26In the embodiment, a first TRP (eg, TRP1) among the multiple TRPs may transmit DCI 1, and a second TRP (eg, TRP 2) among the multiple TRPs may transmit DCI 2.

[0321] In an example, each downlink control signal / channel of the multiple DCI / PDCCHs may be the same (or may have the same content, e.g., the same DCI field, the same DCI size, the same payload, the same DCI field value, etc.). Each downlink control signal / channel of the multiple DCI / PDCCHs may be the same as the downlink control signal / channel. Each downlink control signal / channel of the multiple DCI / PDCCHs may be a repetition of the downlink control signal / channel. The base station may repeat the downlink control signal / channel by transmitting multiple DCI / PDCCHs. For example, in Figure 24 and Figure 26 In this protocol, DCI 1 and DCI 2 may be identical (or equivalent). The content of DCI protocol 1 and DCI protocol 2 may be identical. The payload of DCI 1 and DCI 2 may be identical. The DCI fields (or DCI field values) of DCI 1 and DCI 2 may be identical.

[0322] In an example, the first downlink control signal / channel and the second downlink control signal / channel may be identical (e.g., identical content, identical DCI fields, identical DCI size, identical payload, identical DCI field values, etc.). In an example, the first downlink control signal / channel and the second downlink control signal / channel may be identical to the downlink control signal / channel. The first downlink control signal / channel may be a downlink control signal / channel. The second downlink control signal / channel may be a downlink control signal / channel. The first downlink control signal / channel and the second downlink control signal / channel may be repetitions of the downlink control signal / channel.

[0323] The base station may repeat the downlink control signal / channel via / in multiple core sets (e.g., Figure 24 and Figure 26The base station may transmit multiple DCI / PDCCHs via / in multiple core sets for repetition of downlink control signals / channels. The base station may transmit multiple DCI / PDCCHs via / in multiple core sets for repetition of downlink control signals / channels, including transmitting the downlink control signals / channels via / in multiple core sets. The base station may transmit multiple DCI / PDCCHs via / in multiple search space sets associated with the multiple core sets for repetition of downlink control signals / channels, including transmitting the downlink control signals / channels via / in multiple core sets. The base station may transmit multiple DCI / PDCCHs via / in multiple search space sets associated with the multiple core sets for repetition of downlink control signals / channels. For repetition of downlink control signals / channels, the base station may transmit each downlink control signal / channel of the multiple DCI / PDCCHs via / in the corresponding search space sets in the multiple search space sets. For example, in Figure 24 and Figure 26 In the embodiment of the present invention, 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 may transmit the first downlink control signal / channel via at least one first search space set of the one or more first search space sets. 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. The base station may transmit the second downlink control signal / channel via at least one second search space set of the one or more second search space sets.

[0324] The wireless device may monitor multiple core sets for repetition of downlink control signals / channels for multiple DCI / PDCCHs. The wireless device may monitor a corresponding core set in the multiple core sets for each downlink control signal / channel in the multiple DCI / PDCCHs. Monitoring multiple core sets for repetition of downlink control signals / channels for multiple DCI / PDCCHs may include monitoring multiple core sets for repetition of downlink control signals / channels. Monitoring multiple core sets for repetition of downlink control signals / channels for multiple DCI / PDCCHs may include monitoring multiple core sets for repetition of downlink control signals / channels. The wireless device may monitor multiple search space sets associated with the multiple core sets for repetition of downlink control signals / channels for multiple DCI / PDCCHs. For each downlink control signal / channel in the multiple DCI / PDCCHs, the wireless device may monitor a corresponding search space set in the multiple search space sets for repetition of downlink control signals / channels. For example, in Figure 24 and Figure 26 In one embodiment, the wireless device may monitor a first core set for a first downlink control signal / channel. The wireless device may monitor one or more first search space sets associated with the first core set for the first downlink control signal / channel. The wireless device may monitor at least one first search space set of the one or more first search space sets for the first downlink control signal / channel. The wireless device may monitor a second core set for a second downlink control signal / channel. The wireless device may monitor one or more second search space sets associated with the second core set for the second downlink control signal / channel. The wireless device may monitor at least one second search space set of the one or more second search space sets for the second downlink control signal / channel.

[0325] In an example, the wireless device may determine multiple downlink control signal / channel transmission / repetition opportunities (e.g., PDCCH transmission / repetition / monitoring opportunities) for control channel repetition. The wireless device may determine multiple downlink control signal / channel transmission / repetition opportunities for repetition of the downlink control signal / channel. The base station may determine multiple downlink control signal / channel transmission / repetition opportunities (e.g., PDCCH transmission / repetition / monitoring opportunities) for repetition of the downlink control signal / channel via multiple core sets. Figure 24 and Figure 26The base station may transmit a plurality of DCI / PDCCHs across a plurality of downlink control signal / channel transmission / repetition opportunities, within a plurality of downlink control signal / channel transmission / repetition opportunities, on a plurality of downlink control signal / channel transmission / repetition opportunities, and in a plurality of downlink control signal / channel transmission / repetition opportunities via a plurality of core sets. The base station may transmit a downlink control signal / channel across a corresponding downlink control signal / channel transmission / repetition opportunity, within a corresponding downlink control signal / channel transmission / repetition opportunity, on a corresponding downlink control signal / channel transmission / repetition opportunity, and in a corresponding downlink control signal / channel transmission / repetition opportunity, via each core set in the plurality of core sets. The base station may repeat transmission of the downlink control signal / channel across multiple downlink control signal / channel transmission / repetition opportunities / within multiple downlink control signal / channel transmission / repetition opportunities / on multiple downlink control signal / channel transmission / repetition opportunities / in multiple downlink control signal / channel transmission / repetition opportunities. For example, Figure 24 and Figure 26 In the embodiment, the multiple downlink control signal / channel transmission / repetition opportunities include a first downlink control signal / channel transmission / repetition opportunity (e.g., PDCCH transmission / repetition opportunity 1) and a second downlink control signal / channel transmission / repetition opportunity (e.g., PDCCH transmission / repetition opportunity 2). The base station may transmit the first downlink control signal / channel in the first downlink control signal / channel transmission / repetition opportunity via the first core set. The base station may transmit the second downlink control signal / channel in the second downlink control signal / channel transmission / repetition opportunity via the second core set.

[0326] The wireless device may monitor multiple core sets for multiple DCI / PDCCHs across multiple downlink control signals / channel transmissions / repetition occasions / through the multiple downlink control signals / channel transmissions / repetition occasions / on the multiple downlink control signals / channel transmissions / repetition occasions. The wireless device may monitor multiple core sets for a downlink control signal / channel across multiple downlink control signals / channel transmissions / repetition occasions / within the multiple downlink control signals / channel transmissions / repetition occasions / on the multiple downlink control signals / channel transmissions / repetition occasions. The wireless device may monitor each core set in the multiple core sets for a downlink control signal / channel across a corresponding downlink control signal / channel transmission / repetition occasion / within the corresponding downlink control signal / channel transmission / repetition occasion / on the corresponding downlink control signal / channel transmission / repetition occasion. The wireless device may monitor multiple core sets for repetition of a downlink control signal / channel across multiple downlink control signal / channel transmissions / repetition occasions / within multiple downlink control signal / channel transmissions / repetition occasions / on multiple downlink control signal / channel transmissions / repetition occasions. For example, Figure 24 and Figure 26 In the embodiment, the wireless device monitors a first core set for a first downlink control signal / channel in a first downlink control signal / channel transmission / repetition opportunity. The wireless device monitors a second core set for a second downlink control signal / channel in a second downlink control signal / channel transmission / repetition opportunity.

[0327] The wireless device may monitor multiple core sets across / within / on / in multiple downlink control signal / channel transmission / repetition opportunities. The wireless device may monitor each core set in the multiple core sets across / within / on / in a corresponding downlink control signal / channel transmission / repetition opportunity in the multiple downlink control signal / channel transmission / repetition opportunities. For example, the wireless device may monitor a first core set for a downlink control signal / channel across / within / on / in / in one or more first downlink control signal / channel transmission / repetition opportunities in the multiple downlink control signal / channel transmission / repetition opportunities. The wireless device may monitor a second core set for a downlink control signal / channel across / within / on / in one or more second downlink control signal / channel transmission / repetition opportunities of / among the plurality of downlink control signal / channel transmission / repetition opportunities. The one or more first downlink control signal / channel transmission / repetition opportunities may include a first downlink control signal / channel transmission / repetition opportunity. The one or more second downlink control signal / channel transmission / repetition opportunities may include a second downlink control signal / channel transmission / repetition opportunity.

[0328] The base station may transmit a downlink control signal / channel across a corresponding downlink control signal / channel transmission / repetition opportunity in a plurality of downlink control signal / channel transmission / repetition opportunities via each core set in the plurality of core sets. For example, the base station may transmit a downlink control signal / channel across one or more first downlink control signal / channel transmission / repetition opportunities, within one or more first downlink control signal / channel transmission / repetition opportunities, on one or more first downlink control signal / channel transmission / repetition opportunities, or in one or more first downlink control signal / channel transmission / repetition opportunities via a first core set. The base station may transmit a downlink control signal / channel across one or more second downlink control signal / channel transmission / repetition opportunities, within one or more second downlink control signal / channel transmission / repetition opportunities, on one or more second downlink control signal / channel transmission / repetition opportunities, or in one or more second downlink control signal / channel transmission / repetition opportunities via a second core set.

[0329] In an example, repetition of a downlink control signal / channel (or transmission of multiple DCI / PDCCHs) may occur, for example, in / within time units (e.g., by time division multiplexing). For example, the time units may be contiguous. For example, the time units may not be contiguous. The number of time units may be equal to the number of repetitions. For example, the time unit may be a time slot. For example, the time unit may be a mini-time slot. For example, the time unit may be a time symbol (e.g., an OFDM symbol). For example, the time unit may be a subframe. For example, the time unit may be a temporal monitoring opportunity (e.g., a PDCCH monitoring opportunity). The number of downlink control signal / channel transmission opportunities may be equal to the number of repetitions. Multiple downlink control signal / channel transmission opportunities may occur in / within a time unit. For example, a first downlink control signal / channel transmission opportunity among the multiple downlink control signal / channel transmission opportunities may occur in / within a first time unit among the time units. A second downlink control signal / channel transmission opportunity among the multiple downlink control signal / channel transmission opportunities may occur in / within a second time unit among the time units, and so on.

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

[0331] The base station may transmit multiple DCI / PDCCHs across / through / in a time unit. The base station may transmit multiple DCI / PDCCHs across / through / in a frequency unit. The base station may repeat transmission of a downlink control signal / channel across / through / in multiple uplink signal / channel transmission opportunities. The base station may transmit a downlink control signal / channel with a repetition number. For example, Figure 24 and Figure 26In the embodiment, the 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 may occur in a first time unit (e.g., a first time slot, a first symbol, a first subframe, a first PDCCH monitoring opportunity) among the time units. The second downlink control signal / channel transmission opportunity may occur in a second time unit (e.g., a second time slot, a second symbol, a second subframe, a second PDCCH monitoring opportunity) among the time units. The first downlink control signal / channel transmission opportunity may occur in a first frequency unit (e.g., a first PRB, a first cell, a first frequency, a first BWP, a first subband, a first REG bundle, a first CE) among the frequency units. The second downlink control signal / channel transmission opportunity may occur in a second frequency unit (e.g., a second PRB, a second cell, a second frequency, a second BWP, a second subband, a second REG bundle, a second CE) among the frequency units.

[0332] In an example, one or more configuration parameters may indicate a repetition scheme of the control channel repetition (eg, via a higher layer parameter RepetitionSchemeConfig, FDM-scheme, TDM-scheme, SDM-scheme, CDM-scheme).

[0333] For example, the repetition scheme may be a time domain repetition scheme, a frequency domain repetition scheme, or a space domain / code domain repetition scheme.

[0334] In an example, a wireless device may monitor multiple core sets across / through / in multiple downlink control signal / channel transmission opportunities for multiple DCI / PDCCHs based on one or more configuration parameters indicating a repetition scheme.

[0335] In an example, the repetition scheme may be a time domain repetition scheme (e.g., a TDM scheme, intra-slot repetition, inter-slot repetition, TDM scheme A, TDM scheme B, 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 other downlink control signal / 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, a first downlink control signal / channel transmission opportunity (first TX opportunity) and a second downlink control signal / channel transmission opportunity (second TX opportunity) may not overlap in time. Multiple downlink control signal / channel transmission opportunities may 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.

[0336] In an example, the repetition scheme may be a frequency-domain repetition scheme (e.g., an FDM scheme, FDM scheme A, FDM scheme B, 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 other downlink control signal / 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, a first downlink control signal / channel transmission opportunity (a first TX opportunity) and a second downlink control signal / channel transmission opportunity (a second TX opportunity) may not overlap in frequency. The first downlink control signal / channel transmission opportunity (first TX opportunity) and the second downlink control signal / channel transmission opportunity (second TX opportunity) may overlap in time. Multiple downlink control signal / channel transmission opportunities may 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 opportunity and the second frequency unit of the second downlink control signal / channel transmission opportunity may not overlap in frequency. The first frequency unit and the second frequency unit may be different.

[0337] In an example, the repetition scheme may be a spatial / code domain repetition scheme (e.g., an SFN scheme, an SDM scheme, a CDM scheme, an SDMScheme, a CDMScheme, etc.). In the spatial / code domain repetition scheme, multiple downlink control signal / channel transmission opportunities may overlap in time. In the spatial / code domain repetition scheme, multiple downlink control signal / channel transmission opportunities may overlap in frequency. In the spatial / code domain repetition scheme, multiple downlink control signal / channel transmission opportunities may be a single downlink control signal / channel transmission opportunity. Each of the multiple downlink control signal / channel transmission opportunities may have non-overlapping frequency domain resource allocations relative to other downlink control signal / channel transmission opportunities in the multiple downlink control signal / channel transmission opportunities. Each of the multiple downlink control signal / channel transmission opportunities may have non-overlapping time domain resource allocations relative to other downlink control signal / channel transmission opportunities in the multiple downlink control signal / channel transmission opportunities. Each of the multiple downlink control signal / channel transmission opportunities may be identical. For example, a first downlink control signal / channel transmission opportunity among multiple downlink control signal / channel transmission opportunities may overlap in time and frequency with a second downlink control signal / channel transmission opportunity among 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 the same. For example, in a spatial / code 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 overlap in frequency. The first downlink control signal / channel transmission opportunity (first TX opportunity) and the second downlink control signal / channel transmission opportunity (second TX opportunity) may overlap in time. Multiple downlink control signal / channel transmission opportunities may occur in the same frequency unit (e.g., frequency, PRB, frequency band, bandwidth part, subband, cell, REG, REG bundle, CE). For example, the first frequency unit of the first downlink control signal / channel transmission opportunity and the second frequency unit of the second downlink control signal / channel transmission opportunity may overlap in frequency. The first frequency unit and the second frequency unit may be the same. Multiple downlink control signal / channel transmission opportunities may occur within the same time unit (e.g., symbol, mini-slot, time slot, subframe, PDCCH monitoring opportunity, etc.). For example, a first time unit of a first downlink control signal / channel transmission opportunity and a second time unit of a second downlink control signal / channel transmission opportunity may overlap in time. The first time unit and the second time unit may be the same.

[0338] For example, in a time domain repetition scheme, a downlink control signal / channel transmission opportunity among a plurality of downlink control signal / channel transmission opportunities may have non-overlapping time domain resource allocations relative to another downlink control signal / channel transmission opportunity among the plurality of downlink control signal / channel transmission opportunities. For example, in a frequency domain repetition scheme, a downlink control signal / channel transmission opportunity among a plurality of downlink control signal / channel transmission opportunities may have non-overlapping frequency domain resource allocations relative to another downlink control signal / channel transmission opportunity among the plurality of downlink control signal / channel transmission opportunities. For example, in a space / code domain repetition scheme, a downlink control signal / channel transmission opportunity among a plurality of downlink control signal / channel transmission opportunities may have overlapping time domain and frequency domain resource allocations relative to another downlink control signal / channel transmission opportunity among the plurality of downlink control signal / channel transmission opportunities.

[0339] In an example, a plurality of DCI / PDCCHs may be associated with (or linked to) a plurality of downlink control signal / channel transmission opportunities. Each downlink control signal / channel of the plurality of DCI / PDCCHs may be associated with a corresponding downlink control signal / channel transmission opportunity in the plurality of downlink control signal / channel transmission opportunities. The base station may transmit each downlink control signal / channel of the plurality of DCI / PDCCHs in / via a corresponding downlink control signal / channel transmission opportunity in the plurality of downlink control signal / channel transmission opportunities. The wireless device may monitor for each downlink control signal / channel in the plurality of DCI / PDCCHs in / via a corresponding downlink control signal / channel transmission opportunity in the plurality of downlink control signal / channel transmission opportunities. For example, Figure 24 and Figure 26 In the embodiment, a first downlink control signal / channel (e.g., DCI 1) is associated with a first downlink control signal / channel transmission / repetition opportunity (e.g., PDCCH transmission / repetition opportunity 1), e.g., based on a first downlink control signal / channel transmitted by the base station in / via the first downlink control signal / channel transmission / repetition opportunity or monitored by the wireless device. A second downlink control signal / channel (e.g., DCI 2) is associated with a second downlink control signal / channel transmission / repetition opportunity (e.g., PDCCH transmission / repetition opportunity 2), e.g., based on a second downlink control signal / channel transmitted by the base station in / via the second downlink control signal / channel transmission / repetition opportunity or monitored by the wireless device.

[0340] The wireless device may receive / detect at least one downlink control signal / channel from among the multiple DCI / PDCCHs (or repetitions of the downlink control signal / channel). Figure 24 In the second downlink control signal / channel transmission opportunity, the wireless device detects / receives DCI 2. The wireless device does not receive / detect DCI 1. At least one downlink control signal / channel is DCI 2. The wireless device receives DCI 2 in the second downlink control signal / channel transmission opportunity. The wireless device does not receive / detect DCI 1 in the first downlink control signal / channel transmission opportunity. For example, in Figure 26 In an embodiment, the wireless device detects / receives DCI 1. The wireless device does not receive / detect DCI 2. The at least one downlink control signal / channel is DCI 1. The wireless device receives DCI 1 in a first downlink control signal / channel transmission opportunity. The wireless device does not receive / detect DCI 2 in a second downlink control signal / channel transmission opportunity. In an example, each of the at least one downlink control signal / channel and the downlink control signal / channel may be the same.

[0341] The wireless device may receive a downlink control signal / channel in at least one downlink control signal / channel transmission / repetition opportunity of the plurality of downlink control signal / channel transmission / repetition opportunities. The wireless device may receive each downlink control signal / channel of the at least one downlink control signal / channel in a corresponding downlink control signal / channel transmission / repetition opportunity of the at least one downlink control signal / channel transmission / repetition opportunity. For example, Figure 24 In the at least one downlink control signal / channel transmission / repetition opportunity is a second downlink control signal / channel transmission opportunity. Figure 26 , at least one downlink control signal / channel transmission / repetition opportunity is a first downlink control signal / channel transmission opportunity.

[0342] The wireless device may receive / detect a downlink control signal / channel based on receiving / detecting at least one downlink control signal / channel in a plurality of DCI / PDCCHs.

[0343] In an example, at least one downlink control signal / channel (or downlink control signal / channel) may indicate a repetition number. The at least one downlink control signal / channel may include a DCI indicating a repetition number.

[0344] In an example, the wireless device may communicate with the user via at least one core set of the plurality of core sets (e.g., Figure 24 Core Set 2 and Figure 26The wireless device may receive at least one downlink control signal / channel (or downlink control signal / channel) via a corresponding core set of at least one core set. For example, in Figure 24 In , at least one core set is a second core set (eg, core set 2). Figure 26 , at least one core set is a first core set (eg, core set 1).

[0345] In an example, the wireless device may receive at least one downlink control signal / channel (or downlink control signal / channel) via at least one search space set of at least one core set. Each search space set of the at least one search space set may be associated with a corresponding core set of the at least one core set. The plurality of search space sets may include at least one search space set. For example, in Figure 24 In the one or more second search space sets of the second core set, the one or more second search space sets include at least one search space set. Figure 26 , the one or more first search space sets of the first core set include at least one search space set.

[0346] The wireless device may determine a reference downlink control signal / channel transmission opportunity from among a plurality of downlink control signal / channel transmission opportunities. The wireless device may determine the reference downlink control signal / channel transmission opportunity, for example, based on receiving / detecting at least one downlink control signal / channel. The wireless device may determine the reference downlink control signal / channel transmission opportunity, for example, based on receiving / detecting a downlink control signal / channel. The wireless device may determine the reference downlink control signal / channel transmission opportunity, for example, based on one or more configuration parameters indicating control channel repetition.

[0347] The wireless device may receive / detect at least one downlink control signal / channel during / in / via at least one downlink control signal / channel transmission opportunity among a plurality of downlink control signal / channel transmission opportunities. The at least one downlink control signal / channel transmission opportunity may or may not include a reference downlink control signal / channel transmission opportunity. Figure 24 In the embodiment, at least one downlink control signal / channel transmission opportunity is a second downlink control signal / channel transmission opportunity. The reference downlink control signal / channel transmission opportunity may be a first downlink control signal / channel transmission opportunity. Figure 26In the embodiment, at least one downlink control signal / channel transmission opportunity is a first downlink control signal / channel transmission opportunity. The reference downlink control signal / channel transmission opportunity may be a second downlink control signal / channel transmission opportunity.

[0348] In an example, determining a reference downlink control signal / channel transmission opportunity among a plurality of downlink control signal / channel transmission opportunities may include, for example, determining a reference downlink control signal / channel among a plurality of DCI / PDCCHs based on a plurality of DCI / PDCCHs associated with the plurality of downlink control signal / channel transmission opportunities. Figure 24 and Figure 26 In the embodiment, when the first downlink control signal / channel transmission / repetition opportunity is the reference downlink control signal / channel transmission opportunity, 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 opportunity is the reference downlink control signal / channel transmission opportunity, the second downlink control signal / channel (e.g., DCI 2) is the reference downlink control signal / channel.

[0349] In an example, the wireless device may determine a reference downlink control signal / channel transmission timing based on the number of repetitions and a starting downlink control signal / channel transmission timing (or starting time slot) among a plurality of downlink control signal / channel transmission timings. For example, one or more configuration parameters may indicate a starting downlink control signal / channel transmission timing. At least one downlink control signal / channel may, for example, indicate a starting downlink control signal / channel transmission timing. For example, Figure 24 and Figure 26 In the embodiment of the present invention, when the starting downlink control signal / channel transmission opportunity is the first downlink control signal / channel transmission opportunity and the number of repetitions is equal to two, the reference downlink control signal / channel transmission opportunity may be the second downlink control signal / channel transmission opportunity. When the starting downlink control signal / channel transmission opportunity is the first downlink control signal / channel transmission opportunity and the number of repetitions is equal to three, the reference downlink control signal / channel transmission opportunity may be the third downlink control signal / channel transmission opportunity among the multiple downlink control signal / channel transmission opportunities. When the starting downlink control signal / channel transmission opportunity is the second downlink control signal / channel transmission opportunity and the number of repetitions is equal to two, the reference downlink control signal / channel transmission opportunity may be the third downlink control signal / channel transmission opportunity.

[0350] In an example, the reference downlink control signal / channel transmission opportunity may be the last (or latest or ending) downlink control signal / channel transmission opportunity among the plurality of downlink control signal / channel transmission opportunities.

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

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

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

[0354] The last downlink control signal / channel transmission opportunity may be associated with the last downlink control signal / channel in the plurality of DCI / PDCCHs. The base station may transmit the last downlink control signal / channel in / via the last downlink control signal / channel transmission opportunity. The wireless device may monitor for the last downlink control signal / channel in / via the last downlink control signal / channel transmission opportunity. The last downlink control signal / channel may be a reference downlink control signal / channel. The base station may transmit the last repetition of the downlink control signal / channel in the last downlink control signal / channel transmission opportunity. The wireless device may monitor for the last repetition of the downlink control signal / channel in the last downlink control signal / channel transmission opportunity. The last repetition of the downlink control signal / channel may be the last downlink control signal / channel.

[0355] For example, in Figure 24 and Figure 26 , the last downlink control signal / channel transmission opportunity is the second downlink control signal / channel transmission opportunity (eg, PDCCH transmission / repetition opportunity 2). The reference downlink control signal / channel transmission opportunity is the second (or last) downlink control signal / channel transmission opportunity.

[0356] In an example, the reference downlink control signal / channel transmission opportunity may be the earliest (or first or starting) downlink control signal / channel transmission opportunity among the plurality of downlink control signal / channel transmission opportunities.

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

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

[0359] The earliest (or first or starting) downlink control signal / channel transmission opportunity may be associated with a first / starting downlink control signal / channel in a plurality of DCI / PDCCHs. The base station may transmit the first / starting downlink control signal / channel in / via the earliest downlink control signal / channel transmission opportunity. The wireless device may monitor the earliest downlink control signal / channel transmission opportunity for the first / starting downlink control signal / channel. The first / starting downlink control signal / channel may be a reference downlink control signal / channel. The base station may transmit the first / starting repetition of the downlink control signal / channel in the earliest downlink control signal / channel transmission opportunity. The wireless device may monitor the earliest downlink control signal / channel transmission opportunity for the first / starting repetition of the downlink control signal / channel. The first / starting repetition of the downlink control signal / channel may be the first / starting downlink control signal / channel.

[0360] For example, in Figure 24 and Figure 26 In the present invention, the earliest (or first or starting) downlink control signal / channel transmission opportunity is the first downlink control signal / channel transmission opportunity (e.g., PDCCH transmission / repetition opportunity 1). The reference downlink control signal / channel transmission opportunity is the first (or earliest / first / starting) downlink control signal / channel transmission opportunity.

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

[0362] In an example, a core set may be identified / indicated by a core set index among a plurality of core set indexes. In an example, the core set index may be the lowest (or highest) among the plurality of core set indexes. A core set may be identified / indicated by the lowest (or highest) core set index among the plurality of core set indexes.

[0363] The wireless device may determine / select a core set having a lowest (or highest) core set index among a plurality of core set indices of a plurality of core sets. For example, the wireless device may monitor the core set in a downlink control signal / channel transmission opportunity among a plurality of downlink control signal / channel transmission opportunities for DCI. The downlink control signal / channel transmission opportunity may be a reference downlink control signal / channel transmission opportunity. For example, the wireless device may monitor the core set in one or more downlink control signal / channel transmission opportunities among a plurality of downlink control signal / channel transmission opportunities for DCI. The last / latest / earliest / first / starting downlink control signal / channel transmission opportunity among the one or more downlink control signal / channel transmission opportunities may be the reference downlink control signal / channel transmission opportunity. The wireless device may determine the reference downlink control signal / channel transmission opportunity based on the core set.

[0364] The reference downlink control signal / channel transmission opportunity may be associated with a reference downlink control signal / channel in multiple DCI / PDCCHs. The base station may transmit the reference downlink control signal / channel in / via the reference downlink control signal / channel transmission opportunity. The wireless device may monitor the reference downlink control signal / channel in / via the reference downlink control signal / channel transmission opportunity. The wireless device may monitor the core set for the reference downlink control signal / channel in the reference downlink control signal / channel transmission opportunity.

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

[0366] In an example, a search space set may be identified / indicated by a search space set index in a search space set index. In an example, the search space set index may be the lowest (or highest) of the search space set indexes. A search space set may be identified / indicated by the lowest (or highest) search space set index in the search space set indexes.

[0367] The wireless device may determine / select a search space set having a lowest (or highest) search space set index among the search space set indices of the plurality of search space sets. For example, the wireless device may monitor the search space set in a downlink control signal / channel transmission opportunity for DCI. The downlink control signal / channel transmission opportunity may be a reference downlink control signal / channel transmission opportunity. For example, the wireless device may monitor the search space set in one or more downlink control signal / channel transmission opportunities for DCI. The last / latest / earliest / first / starting downlink control signal / channel transmission opportunity among the one or more downlink control signal / channel transmission opportunities may be the reference downlink control signal / channel transmission opportunity. The wireless device may determine the reference downlink control signal / channel transmission opportunity based on the search space set.

[0368] The reference downlink control signal / channel transmission opportunity may be associated with a reference downlink control signal / channel in multiple DCI / PDCCHs. The base station may transmit the reference downlink control signal / channel in / via the reference downlink control signal / channel transmission opportunity. The wireless device may monitor the reference downlink control signal / channel in / via the reference downlink control signal / channel transmission opportunity. The wireless device may monitor the search space for the reference downlink control signal / channel in the reference downlink control signal / channel transmission opportunity.

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

[0370] The wireless device may trigger transmission of uplink signals (e.g., HARQ-ACK information bits, PUCCH, PUSCH, SRS, UCI, SR) based on detecting / receiving at least one downlink control signal / channel (or downlink control signal / channel). Figure 24 The transmission of an uplink signal in the communication channel (or an uplink signal in the communication channel) may be associated with (or indicated by) at least one downlink control signal / channel (or downlink control signal / channel).

[0371] The wireless device may transmit an uplink signal (e.g., HARQ-ACK information bits, PUCCH, PUSCH, SRS, UCI, SR) based on detecting / receiving at least one downlink control signal / channel (or downlink control signal / channel). The transmission of the uplink signal may be associated with (or indicated by) the at least one downlink control signal / channel (or downlink control signal / channel). The wireless device may transmit the uplink signal via an active uplink BWP of an uplink carrier of a cell. For example, the uplink carrier may be a NUL. For example, the uplink carrier may be a SUL.

[0372] In an example, at least one downlink control signal / channel (or downlink control signals / channels) may schedule a transport block (e.g., a PDSCH). In an example, each of the at least one downlink control signal / channel may schedule a transport block. The uplink signal may be / include a HARQ-ACK (or HARQ-ACK information bits) for the transport block.

[0373] In an example, at least one downlink control signal / channel (or downlink control signal / channel) may indicate an SPS PDSCH release for an SPS configuration. One or more configuration parameters may indicate the SPS configuration. The wireless device may receive one or more PDSCHs for the SPS configuration (e.g., via periodic resources). In an example, each of the at least one downlink control signal / channel may indicate an SPS PDSCH release. The uplink signal may include / include a HARQ-ACK (or HARQ-ACK information bit) for / for an SPS PDSCH release. The HARQ-ACK (or HARQ-ACK information bit) for the SPS PDSCH release may indicate an acknowledgement of receipt of the at least one downlink control signal / channel (or downlink control signal / channel) indicating an SPS PDSCH release.

[0374] In an example, at least one downlink control signal / channel (or downlink control signal / channel) may indicate SCell sleep. In an example, each downlink control signal / channel of the at least one downlink control signal / channel may indicate SCell sleep. The at least one downlink control signal / channel may not schedule a transport block (e.g., PDSCH). The uplink signal may be / include HARQ-ACK (or HARQ-ACK information bit) for / for SCell sleep. The HARQ-ACK (or HARQ-ACK information bit) for SCell sleep may indicate confirmation of receipt of at least one downlink control signal / channel (or downlink control signal / channel), the at least one downlink control signal / channel indicating SCell sleep. The at least one downlink control signal / channel may include an SCell sleep indication field indicating SCell sleep.

[0375] In an example, at least one downlink control signal / channel may schedule a transport block (e.g., PUSCH). In an example, each downlink control signal / channel of the at least one downlink control signal / channel may schedule a transport block. The uplink signal may be / include a transport block.

[0376] In an example, at least one downlink control signal / channel may trigger / indicate the transmission of an SRS. For example, the SRS may be an aperiodic SRS. The uplink signal may be / include an SRS (or an aperiodic SRS).

[0377] In an example, the uplink signal may be / include a PUCCH. The PUCCH may be / include uplink control information (UCI). The UCI may include / be at least one of the following: SR, HARQ-ACK, CSI report, beam report, etc.

[0378] In an example, the uplink signal may be / include a PUSCH. The PUSCH may be / include a transport block.

[0379] In an example, the uplink signal may be / include an SRS. For example, the SRS may be an aperiodic SRS.

[0380] In an example, the wireless device may select / determine a selected core set among a plurality of core sets.

[0381] In an example, the wireless device may select / determine a selected core set for transmission of uplink signals. The wireless device may determine uplink resources (e.g., Figure 24The wireless device may determine uplink resources for transmission of uplink signals. The wireless device may transmit uplink signals via the uplink resources. The active uplink BWP of the cell may include uplink resources. The active uplink BWP of the uplink carrier of the cell may include uplink resources. One or more configuration parameters may indicate uplink resources for the active uplink BWP of the cell. One or more configuration parameters may indicate uplink resources for the active uplink BWP of the uplink carrier of the cell.

[0382] In an example, the at least one core set may include a selected core set. The wireless device may receive at least one of the at least one downlink control signal / channel (or downlink control signal / channel) via the selected core set. The wireless device may receive the downlink control signal / channel via the selected core set. For example, Figure 24 In , at least one core set is a second core set (eg, core set 2), and the selected core set may be the second core set. Figure 26 , at least one core set is a first core set (eg, core set 1), and the selected core set may be the first core set.

[0383] In an example, at least one core set may not include the selected core set. The wireless device may not receive at least one of the at least one downlink control signal / channel (or downlink control signal / channel) via the selected core set. The wireless device may not receive the downlink control signal / channel via the selected core set. For example, Figure 24 In , at least one core set is the second core set (eg, core set 2), and the selected core set may be the first core set (eg, core set 1). Figure 26 , at least one core set is a first core set (eg, core set 1), and the selected core set may be a second core set (eg, core set 2).

[0384] The wireless device may select / determine the selected core set among the plurality of core sets based on one or more configuration parameters indicating control channel repetition. The wireless device may select / determine the selected core set among the plurality of core sets, for example, based on one or more configuration parameters indicating control channel repetition for the plurality of core sets.

[0385] The wireless device may select / determine the selected core set among the plurality of core sets based on receiving at least one downlink control signal / channel (or downlink control signals / channels) via at least one core set among the plurality of core sets.

[0386] The wireless device may select / determine the selected core set from the plurality of core sets based on the repetition scheme being a first repetition scheme. For example, the first repetition scheme may be a time domain repetition scheme (eg, TDM).

[0387] For example, the first repetition scheme may be a frequency domain repetition scheme (eg, FDM). For example, the first repetition scheme may be a space / code domain repetition scheme (eg, SFN, SDM).

[0388] The wireless device may select / determine the selected core set from the plurality of core sets based on the repetition scheme not being the second repetition scheme. For example, the second repetition scheme may be a frequency domain repetition scheme (e.g., FDM). For example, the second repetition scheme may be a spatial / code domain repetition scheme (e.g., SFN, SDM).

[0389] For example, the second repetition scheme may be a time domain repetition scheme (eg, TDM).

[0390] The uplink resource may be, for example, a PUCCH resource. The uplink resource may be, for example, a PUSCH resource. The uplink resource may be, for example, an SRS resource.

[0391] The multiple core sets can include selected core sets and unselected core sets. For example, in Figure 24 and Figure 26 , when the selected core set is the first core set (e.g., core set 1), the unselected core set is the second core set (e.g., core set 2). When the selected core set is the second core set (e.g., core set 2), the unselected core set is the first core set (e.g., core set 1).

[0392] In an example, the selected core set may include one or more first CCEs. The one or more configuration parameters may indicate the one or more first CCEs of the selected core set. For example, the one or more configuration parameters may indicate a set of resource blocks for the selected core set (e.g., determined by a higher layer parameter frequencyDomainResources The one or more configuration parameters may include CCE to REG mapping parameters for the first core set (eg, provided by a higher layer parameter cce-REG- MappingType Provided). The wireless device may determine one or more first CCEs based on the set of resource blocks. The wireless device may determine one or more first CCEs based on a CCE to REG mapping parameter. For example, Figure 24 In the embodiment, when the selected core set is a first core set, the one or more first CCEs are first CCEs of the first core set. When the selected core set is a second core set, the one or more first CCEs are second CCEs of the second core set.

[0393] The wireless device may determine the uplink resource based on, for example, the number of the one or more first CCEs of the selected core set. For example, when the one or more first CCEs are CCE-1, CCE-2, and CCE-3, the number of the one or more first CCEs (e.g., ) is three. When the one or more first CCEs are CCE-1, CCE-2, CCE-3, CCE-4, and CCE-5, the number of the one or more first CCEs (e.g., ) is five. Determining the uplink resource based on the selected core set may include determining the uplink resource based on a number of the one or more first CCEs of the selected core set.

[0394] The wireless device may determine the uplink resource based on, for example, a first CCE of one or more first CCEs of the selected core set. Determining the uplink resource based on the first CCE may include determining the uplink resource based on an index of the first CCE (e.g., 、 ) to determine uplink resources.

[0395] For example, a first CCE may be the starting / earliest / lowest CCE of one or more first CCEs. For example, a first CCE may have the earliest / latest start time among one or more start times of the one or more first CCEs. For example, a first CCE may have the lowest / highest start frequency among one or more start frequencies of the one or more first CCEs. For example, the one or more first CCEs may include / be CCE-1, CCE-2, CCE-3, and CCE-4. In an example, CCE-1, CCE-2, CCE-3, and CCE-4 may occur at times n, n+1, n+2, and n+3, respectively. The first CCE of the one or more first CCEs may be, for example,...

Claims

1. A communication method, the method comprising: Receiving, by a wireless device, a physical downlink control channel (PDCCH), the PDCCH comprising downlink control information (DCI), the DCI scheduling a physical downlink shared channel (PDSCH), wherein the PDCCH comprises PDCCH candidates configured for repetition from a search space set, associated with a control resource set (coreset); as well as A transport block is received via the PDSCH, wherein resource blocks RBs numbering the PDSCH start from a lowest RB of a coreset having a lowest index in the coreset.

2. The method of claim 1, further comprising monitoring a repeated coreset for the DCI.

3. The method of claim 2, wherein the monitoring comprises monitoring a plurality of search space sets associated with the coreset.

4. The method of claim 3, wherein each of the plurality of search space sets is associated with a corresponding coreset of the coresets. The method of claim 1 , wherein the set of search spaces is a plurality of common search space sets.

6. The method of claim 1, wherein the DCI is DCI format 1_0.

7. The method of claim 1, further comprising receiving one or more radio resource control (RRC) messages including one or more configuration parameters, wherein The one or more configuration parameters indicate that the coresets are chained for replication; and RB numbering starts from the lowest RB of the lowest indexed coreset among the coresets linked for repetition. 8 . The method of claim 1 , wherein the lowest RB of the coreset is an RB having a lowest frequency among one or more frequencies of one or more RBs of the coreset. 9 . The method of claim 1 , wherein the lowest RB of the coreset is an RB having a lowest starting frequency among one or more starting frequencies of one or more RBs of the coreset.

10. The method of claim 1, wherein the DCI includes a resource indication field having a value.

11. A wireless device, comprising: one or more processors; as well as a memory storing instructions that, when executed by the one or more processors, cause the wireless device to: Receiving a physical downlink control channel PDCCH, the PDCCH comprising downlink control information DCI, the DCI scheduling a physical downlink shared channel PDSCH, wherein the PDCCH comprises PDCCH candidates from a search space set, associated with a control resource set coreset, and configured for repetition; as well as A transport block is received via the PDSCH, wherein resource blocks RBs numbering the PDSCH start from a lowest RB of a coreset having a lowest index in the coreset.

12. The wireless device of claim 11, the instructions further causing the wireless device to monitor a repeated coreset for the DCI.

13. The wireless device of claim 12, wherein the monitoring comprises monitoring a plurality of search space sets associated with the coreset.

14. The wireless device of claim 13, wherein each of the plurality of search space sets is associated with a corresponding coreset of the coresets.

15. The wireless device of claim 11, wherein the set of search spaces is a plurality of common search space sets.

16. The wireless device of claim 11, wherein the DCI is DCI format 1_0.

17. The wireless device of claim 11, the instructions further causing the wireless device to receive one or more radio resource control (RRC) messages including one or more configuration parameters, wherein The one or more configuration parameters indicate that the coresets are chained for replication; and RB numbering starts from the lowest RB of the lowest indexed coreset among the coresets linked for repetition.

18. The wireless device of claim 11, wherein the lowest RB of the coreset is an RB having a lowest frequency among one or more frequencies of one or more RBs of the coreset.

19. The wireless device of claim 11, wherein the lowest RB of the coreset is an RB having a lowest starting frequency among one or more starting frequencies of one or more RBs of the coreset.

20. A communication system, the system comprising: A wireless device comprising one or more first processors and a first memory storing first instructions, the first instructions, when executed by the one or more first processors, causing the wireless device to: Receiving a physical downlink control channel PDCCH, the PDCCH comprising downlink control information DCI, the DCI scheduling a physical downlink shared channel PDSCH, wherein the PDCCH comprises PDCCH candidates from a search space set, associated with a control resource set coreset, and configured for repetition; as well as receiving a transport block via the PDSCH, wherein resource blocks RBs for numbering the PDSCH start from a lowest RB of a coreset having a lowest index in the coreset; and A base station comprising one or more second processors and a first memory storing second instructions, wherein the second instructions, when executed by the one or more second processors, cause the base station to: Transmitting the physical downlink control channel PDCCH, wherein the PDCCH includes the downlink control information DCI; as well as The transport block is transmitted via the PDSCH.

Images