Transmission in control channel repetition

By introducing a multi-level channel management mechanism into the control channel repetition, optimizing the utilization of channel resources, solving the problems of low channel utilization efficiency and unstable system performance in the prior art, and achieving more efficient and stable channel management.

CN119814237APending Publication Date: 2025-04-11OFINNO LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411849809.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2020-10-22
Filing Date
2021-10-22
Publication Date
2025-04-11

AI Technical Summary

Technical Problem

In the process of control channel repetition, it is difficult to effectively manage and optimize channel resources, resulting in low channel utilization efficiency and unstable system performance.

Method used

Optimize the utilization of channel resources by introducing a multi-level channel management mechanism into the control channel repetition, including mapping of logical channels, transmission channels and physical channels, as well as dynamic scheduling and resource allocation strategies.

Benefits of technology

Improve channel utilization efficiency, enhance system performance stability, and enable more flexible and efficient management of channel resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119814237A_ABST
    Figure CN119814237A_ABST
Patent Text Reader

Abstract

A wireless device may determine a first uplink resource for transmitting a first Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) in a time slot. The wireless device may receive, via at least one of the monitoring occasions, at least one repetition of downlink control information (DCI) indicating a second uplink resource for transmission of a second HARQ-ACK in the time slot. The wireless device may transmit the second HARQ-ACK in the time slot and via an uplink resource based on a monitoring occasion of the monitoring occasion earlier than a duration starting from a start symbol of the first uplink resource, where an end time of the one monitoring occasion ends at the latest of end times of the monitoring occasion.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Divisional application

[0002] This application is a divisional application of the Chinese invention patent application with application number 2021800855474, filed on October 22, 2021, and entitled “TRANSMISSION IN CONTROL CHANNEL REPETITION”.

[0003] CROSS-REFERENCE TO RELATED APPLICATIONS

[0004] This application claims the benefit of U.S. Provisional Application No. 63 / 104,224, filed on October 22, 2020, the entire contents of which are hereby incorporated by reference. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0009] Figure 4A Shows the flow Figure 2A Figure 2 shows an exemplary downlink data flow of the NR user plane protocol stack.

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

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

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

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

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

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

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

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

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

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

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

[0021] Fig.13A , Fig. 13B and Fig. 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.

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

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

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

[0025] Fig.16A , Fig. 16B , Fig. 16C and Fig.16D Exemplary structures for uplink and downlink transmissions are shown.

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

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

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

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

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

[0031] Fig. 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.

[0032] Fig.23 An example of a MAC CE format for multiple TCI states of an activated core set according to aspects of an embodiment of the present disclosure is shown.

[0033] Fig.24 is an example of control channel repetition according to one aspect of an embodiment of the present disclosure.

[0034] Fig.25 is an example of control channel repetition according to one aspect of an embodiment of the present disclosure.

[0035] Fig.26 is an example of control channel repetition according to one aspect of an embodiment of the present disclosure. DETAILED DESCRIPTION

[0036] 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. Restrictions, features and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figure highlighting functionality and advantages is provided only for illustrative purposes. The disclosed architecture is flexible and configurable enough so 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.

[0037] Embodiments may be configured to operate as desired. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., when certain criteria are met, the disclosed mechanism may be executed. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various exemplary embodiments may be applied. Therefore, exemplary embodiments that selectively implement the disclosed protocol may be implemented.

[0038] 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 category 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 a given capability 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.

[0039] In the present disclosure, "a" and "an" and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will be interpreted as "at least one" and "one or more". In the present disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase after the term "may" is an example of a 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 that unlisted components are 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" should be interpreted as "based at least in part on" rather than, for example, "based only on". As used herein, the term "and / or" represents 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.

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

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

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

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

[0044] Many elements described in the disclosed embodiments can be implemented as modules.Modules are defined here as elements that perform defined functions and have defined interfaces to other elements.Modules described in the present disclosure can be implemented by hardware, software, firmware, wetware (for example, hardware with biological elements) in combination with hardware, or a combination thereof, all of which can be equivalent in behavior.For example, a module can be implemented as a software routine written in a computer language, which is 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 LabVIEWMathScript).It is possible to implement a module using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware.Examples of programmable hardware include: computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are often programmed using a hardware description language (HDL), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between less functional internal hardware blocks on the programmable device. The mentioned techniques are often used in combination to achieve the results of the functional blocks.

[0045] 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, the mobile communication network 100 includes a core network (CN) 102 , a radio access network (RAN) 104 , and wireless devices 106 .

[0046] The CN 102 may provide an interface to one or more data networks (DNs), such as a public DN (e.g., the Internet), a private DN, and / or an intra-carrier DN, 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.

[0047] The RAN 104 may connect the CN 102 to the wireless device 106 via radio communications over an air interface. As part of the radio communications, the RAN 104 may 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 may be separated from uplink transmissions using frequency division duplex (FDD), time division duplex (TDD), and / or some combination of the two duplex technologies.

[0048] The term "wireless device" may be used throughout this disclosure to mean 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, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicle roadside unit (RSU), a relay node, a car, 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.

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

[0050] The base stations included in the RAN 104 may include one or more sets of antennas for communicating with the 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 the 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. The cells of the base stations may together provide radio coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0051] In addition to three-sector sites, other implementations of the base station 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 unit coupled to the RRH may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be centralized in a baseband processing unit pool or virtualized. The repeater node may amplify and rebroadcast the radio signal received from the donor node. The relay node may perform the same / similar functions as the repeater node, but may decode the radio signal received from the donor node to eliminate noise before amplifying and rebroadcasting the radio signal.

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

[0053] The Third Generation Partnership Project (3GPP) was established in 1998 to Figure 1A 3GPP provides global specification standardization for mobile communication networks similar to the mobile communication network 100 in the mobile communication network 100. 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). 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 may be applicable to the RAN of other mobile communication networks, such as Figure 1A The RAN 104 in 5G networks, the RAN of early 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.

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

[0055] 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 operator's internal DN, to UE 156. As part of the interface function, 5G-CN 152 may set up an end-to-end connection between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CN of the 3GPP 4G network, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 may be defined as network functions that provide services to other network functions via interfaces. The network functions of 5G-CN 152 may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0056] like Figure 1B As shown, 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B. For ease of explanation, Figure 1BThey are shown as one component AMF / UPF 158 in FIG. 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 service flows to the one or more DNs, user plane quality of service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement and uplink service verification), downlink packet buffering and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected with the one or more DNs, and / or a fulcrum for supporting multi-host PDU sessions. UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and the DN.

[0057] 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 functions operating between the CN and the UE, and AS may refer to functions operating between the UE and the RAN.

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

[0059] The NG-RAN 154 may connect the 5G-CN 152 to the UE 156 via radio communications over an air interface. The NG-RAN 154 may include: one or more gNBs, shown as gNB 160A and gNB 160B (collectively referred to as gNB 160); and / or one or more ng-eNBs, shown as ng-eNB 162A and ng-eNB 162B (collectively referred to as ng-eNB 162). The gNB 160 and ng-eNB 162 may be more generally referred to as base stations. The gNB 160 and ng-eNB 162 may include one or more groups of antennas for communicating with the UE 156 over an air interface. For example, one or more gNBs in the gNB 160 and / or one or more ng-eNBs in the ng-eNB 162 may include three groups of 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.

[0060] 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 a direct physical connection and / or an indirect connection through an underlying transport network such as an Internet Protocol (IP) transport network. 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. 1 , gNB 160A may be connected to UE 156A via a Uu interface. NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface may be composed of Figure 1B The network elements in a network are used to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data that the user is interested in. The control plane may process signaling messages that the network elements are interested in.

[0061] 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, by means of one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by means of a NG user plane (NG-U) interface. The NG-U interface may provide 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 by means of a 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.

[0062] The gNB 160 may provide NR user plane and control plane protocol terminations to the UE 156 via a Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations to the UE 156A via a Uu interface associated with the first protocol stack. The ng-eNB 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations 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 may provide E-UTRA user plane and control plane protocol terminations to the UE 156B via a Uu interface associated with the second protocol stack.

[0063] 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 a 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.

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

[0065] Figure 2A and Figure 2B Examples of NR user plane and NR control plane protocol stacks for the Uu interface 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 UE156A and gNB 160A shown in are the same or similar.

[0066] Figure 2A An NR user plane protocol stack including five layers implemented in a UE 210 and a gNB 220 is shown. At the bottom of the protocol stack, a physical layer (PHY) 211 and 221 may provide transport services to higher layers of the protocol stack and may correspond to layer 1 of the open system interconnection (OSI) model. The next four protocols above the PHY 211 and 221 include a medium access control layer (MAC) 212 and 222, a radio link control layer (RLC) 213 and 223, a packet data convergence protocol layer (PDCP) 214 and 224, and a service data application protocol layer (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0067] 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 of , SDAPs 215 and 225 can perform QoS flow processing. UE 210 can receive services through a PDU session, which can be a logical connection between UE 210 and a DN. A PDU session can have one or more QoS flows. The UPF of the CN (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 delay, data rate, and / or error rate). SDAPs 215 and 225 can perform mapping / demapping between the one or more QoS flows and one or more data radio bearers. The mapping / demapping between the QoS flows and the data radio bearers can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the 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 / demapping between QoS flows and data radio bearers.

[0068] The PDCP 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, may perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and may perform integrity protection to ensure that control messages originate from the intended source. The PDCP 214 and 224 may perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate received packets due to, for example, intra-gNB handovers. The PDCP 214 and 224 may perform packet repetition to increase the likelihood that a packet is received, and remove any duplicate packets at the receiver. Packet repetition may be applicable to services that require high reliability.

[0069] although Figure 3 Not shown, but PDCP 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in a dual connectivity scenario. 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). A split bearer is a split bearer when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapped split radio bearers between RLC channels belonging to a cell group.

[0070] RLC 213 and 223 can perform segmentation, retransmission through 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 based on each logical channel, independent of parameter sets and / or transmission time interval (TTI) duration. As shown in FIG. Figure 3 As shown in FIG. 1 , RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

[0071] The MAC 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 a transport block (TB) delivered to / from the PHY 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs with the aid of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MAC 212 and 222 may be configured to perform error correction by hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between logical channels of the UE 210 with the aid of logical channel prioritization, and / or padding. The MAC 212 and 222 may support one or more parameter sets and / or transmission timings. In an example, mapping restrictions in the logical channel prioritization may control which parameter set and / or transmission timing may be used by the logical channel. like Figure 3 As shown, MAC 212 and 222 may provide logical channels as services to RLC 213 and 223 .

[0072] 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 , PHY 211 and 221 may provide one or more transport channels as a service to MAC 212 and 222 .

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

[0074] Figure 4A The downlink data flow of starts when 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 header (in Figure 4AThe 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 unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and is the PDU of SDAP 225.

[0075] Figure 4A The remaining protocol layers in can perform their associated functions (e.g., Figure 3 ), add the corresponding headers, and forward their corresponding outputs 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 222) and forwards its output to MAC 222. MAC 222 may multiplex many RLC PDUs and may attach MAC subheaders to the RLC PDUs to form a transport block. In NR, MAC subheaders may be distributed throughout the MAC PDU, as shown in FIG. 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.

[0076] Figure 4B An exemplary format of a MAC subheader in a MAC PDU is shown. 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.

[0077] 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 the MAC PDU. Figure 4B) and inserting a MAC CE at the end of a MAC PDU for uplink transmission. MAC CE 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 for a MAC SDU may be present before 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.

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

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

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

[0081] - 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;

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

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

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

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

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

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

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

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

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

[0091] 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 of one or more transport channels. The PHY may generate control information to support low-level operation of the PHY and provide control information to lower levels of the PHY via physical control channels (referred to as L1 / L2 control channels). The set of physical channels and physical control channels defined by NR includes, for example:

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

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

[0094] -- 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;

[0095] - 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;

[0096] -- 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

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

[0098] Similar to the physical control channel, the physical layer generates physical signals to support the lower-level operations of the physical layer. Figure 5A and Figure 5B As shown in , the physical layer signals defined by NR include: primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), sounding reference signal (SRS) and phase tracking reference signal (PT-RS). These physical layer signals will be described in more detail below.

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

[0100] The NAS protocols 217 and 237 may provide control plane functions 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 may provide control plane functions between the UE 210 and the AMF 230 via signaling messages referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which NAS messages may be transmitted. NAS messages may be transmitted using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0101] The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 or more generally between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 via signaling messages referred to as RRC messages. The RRC messages may be transported between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may 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 AS and NAS; paging initiated by CN or RAN; establishment, maintenance, and release of an RRC connection between UE 210 and RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of 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.

[0102] Figure 6 is an example diagram showing the RRC state transition of the UE. The UE can Figure 1A The wireless device 106 depicted in Figure 2A and Figure 2B The UE 210 depicted in FIG. 1 and any other wireless device described in the present disclosure may be the same or similar. Figure 6 As shown in , the 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).

[0103] 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 2BgNB220 depicted in ; or any other base station described in the present 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 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., involving data radio bearers, signaling radio bearers, logical channels, QoS flows and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP and / or SDAP layer configuration information. When in RRC connection 602, the mobility of the UE may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from a 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 .

[0104] 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. When in RRC idle 604, the UE may be in a sleep state for most of the time (e.g., to save battery power). The UE may wake up periodically (e.g., once in each discontinuous reception cycle) to monitor paging messages from the RAN. The mobility of the UE 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 through a connection establishment procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0105] In RRC Inactive 606, the previously established RRC context is maintained in the UE and the base station. This allows 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 mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connected 602 through a Connection Resumption Procedure 614, or to RRC Idle 604 through a Connection Release Procedure 616, which may be the same or similar to the Connection Release Procedure 608.

[0106] The RRC state may be associated with a mobility management mechanism. 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 an event via a paging message without broadcasting the paging message over the entire mobile communication network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE at a cell group level, so that the paging message may be broadcast over a cell in the cell group in which the UE currently resides instead of over the entire mobile communication network. The mobility management mechanism used for RRC idle 604 and RRC inactive 606 tracks the UE at a cell group level. These mobility management mechanisms may do so using groups of different granularities. For example, there may be three levels of cell grouping granularity: a single cell; a cell within a RAN area identified by a RAN area identifier (RAI); and a cell within a group of RAN areas referred to as tracking areas and identified by a tracking area identifier (TAI).

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

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

[0109] The base station storing 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 during the period of time that the UE remains in the RAN notification area of ​​the anchor base station and / or during the period of time that the UE remains in RRC inactivity 606.

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

[0111] In NR, physical signals and physical channels (about Figure 5A and Figure 5B Discussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data through F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to 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. The F parallel symbol streams can be treated as if they are in the frequency domain and used as input to the inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols at a time (one source symbol from each of the F parallel symbol streams), and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time domain samples representing the sum of the F orthogonal subcarriers. The F time domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using the FFT block before being processed by the IFFT block. This operation produces a discrete Fourier transform (DFT) precoded OFDM symbol 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 symbol at the receiver to restore the data mapped to the source symbol.

[0112] Figure 7 An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown. An NR frame may be identified by a system frame number (SFN). The SFN may be repeated with a period of 1024 frames. As shown, a NR frame may have a duration of 10 milliseconds (ms) and may include 10 subframes of duration 1 ms. A subframe may be divided into time slots that include, for example, 14 OFDM symbols per time slot.

[0113] The duration of a time slot may depend on the parameter set of the OFDM symbol used for the time 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 mm-wave 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.

[0114] A slot may have a fixed number of OFDM symbols (eg, 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 each subframe time slot associated with the parameter set is shown (for ease of explanation, Figure 7 Parameter sets with subcarrier spacing of 240kHz are not shown in Figure 1). Subframes in NR can be used as a time reference independent of the parameter set, while slots 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 to transmit as many symbols as needed. These partial slot transmissions can be called mini-slots or sub-slot transmissions.

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

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

[0117] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Moreover, 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 may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE plans to receive. This is referred to as bandwidth adaptation.

[0118] NR defines bandwidth parts (BWPs) to support UEs that cannot receive the full carrier bandwidth and supports bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. The UE may 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 the serving cell may be active. The one or more BWPs may be referred to as the active BWP of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

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

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

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

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

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

[0124] 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 an 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 towards expiration (e.g., an increment from zero to the BWP inactivity timer value, or a decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

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

[0126] Downlink and uplink BWP switching can be performed independently in paired spectrum (where BWP switching refers to switching from a currently active BWP to a 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 a BWP inactivity timer, and / or initiation of random access.

[0127] Fig. 9 An example of bandwidth adaptation using three configured BWPs of an NR carrier is shown. A UE configured with the three BWPs can switch from one BWP to another at a switching point. Fig. 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. Fig. 9 904. In the example of FIG. 906, 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 an 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 an 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 an 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 an active BWP.

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

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

[0130] Fig. 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 are located directly adjacent to each other in the frequency band. In the intra-band non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (Band A) and are separated by a gap in the frequency band. In the inter-band configuration 1006, the two CCs are located in the frequency bands (Band A and Band B).

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

[0132] When CA is used, one of the aggregated cells for the UE may be referred to as a primary cell (PCell). The PCell may be a serving cell to which the UE initially connects at RRC connection establishment, reestablishment and / or handover. The PCell may provide NAS mobility information and security input to the UE. The 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 via 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).

[0133] 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 The MAC CE may be used to activate and deactivate the configured SCells. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) are activated or deactivated for the UE. The configured SCells may be deactivated in response to the expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0134] The downlink control information of a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant, which is called self-scheduling. The DCI of a cell can be transmitted on another cell, which is called cross-carrier scheduling. Uplink control information for aggregated cells (e.g., HARQ confirmation 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. The cell can be divided into multiple PUCCH groups.

[0135] Fig. 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 include one or more downlink CCs, respectively. Fig. 10B, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053 in this example. 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 the example, if Fig. 10B If the aggregated cell depicted in FIG. 1 is not divided into PUCCH group 1010 and PUCCH group 1050 , a single uplink PCell transmits UCI associated with a downlink CC, and the PCell may become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061 , overload can be prevented.

[0136] 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 a downlink carrier and / or an uplink carrier of a 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.

[0137] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an 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 the transport block can be mapped to a serving cell.

[0138] In the downlink, the base station may transmit (e.g., unicast, multicast and / or broadcast) one or more reference signals (RS) 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 ). 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.

[0139] Fig.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 Fig.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 with a duration of 5 ms). It should be understood that Fig.11A are examples, and these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, burst position within a frame) may be configured based on, for example: the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; a parameter set or subcarrier spacing for 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.

[0140] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as Fig.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.

[0141] The UE may not know the location of the SS / PBCH blocks in the time and frequency domains (for example, when the UE is searching for cells). 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 based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block may be a cell definition SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, cell selection / search and / or reselection may be based on the CD-SSB.

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

[0143] The PBCH may use QPSK modulation and may use forward error correction (FEC). FEC may use polarity coding. One or more symbols spanned by the PBCH may carry one or more DMRS 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 contribute to the time synchronization of the UE with the base station. The PBCH may include a master information block (MIB) for providing 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 required for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH that 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 that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE may point to a frequency. The UE may search for SS / PBCH blocks at the frequency to which the UE is pointing.

[0144] 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 block transmissions with different SS / PBCH block indices.

[0145] 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 ​​a 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.

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

[0147] The 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-RS for channel estimation or any other suitable purpose. The base station may configure the UE with one or more CSI-RSs of the same / similar CSI-RS. 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.

[0148] The base station may semi-statically configure the UE with one or more CSI-RS resource sets. The CSI-RS resources may be associated with positions and periodicity in the time and frequency domains. The base station may selectively activate and / or deactivate CSI-RS resources. The base station may indicate to the UE that the CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

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

[0150] The CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbol for 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 employ the same OFDM symbol for 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.

[0151] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, the downlink DMRS can be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS mode. The 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 for PDSCH. The DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, the DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, the DMRS configuration can support up to 4 orthogonal downlink DMRS ports per UE. The radio network may (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, where the DMRS position, DMRS pattern and / or scrambling sequence may be the same or different. The base station may transmit the downlink DMRS and the corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRS to perform consistent demodulation / channel estimation on the PDSCH.

[0152] In an example, a transmitter (e.g., a base station) may use a precoder matrix for a portion of a 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 be different based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used throughout a set of PRBs. The set of PRBs may be represented as a precoding resource block group (PRG).

[0153] 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. The higher layers may configure up to 3 DMRS for the PDSCH.

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

[0155] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS to consistently demodulate one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a 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 front-load DMRS mode. The front-load DMRS may be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to be transmitted at 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 front-load DMRS symbols for the PUSCH and / or PUCCH, and the UE may use the front-load DMRS symbol to schedule a single-symbol DMRS and / or a dual-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.

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

[0157] Depending on the RRC configuration of the UE, an uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not exist. The presence and / or type of the uplink PT-RS can be configured based on UE-specific configuration through a combination of RRC signaling and / or one or more parameters for other purposes (e.g., modulation and coding scheme (MCS)) indicated by the DCI. When configured, the dynamic presence of the 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 DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS can be limited to the scheduled time / frequency duration of the UE.

[0158] The UE may transmit an SRS to a 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 an SRS resource set, the base station may configure the UE with one or more SRS resources. The applicability of the SRS resource set may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, the SRS resources in the SRS resource set in the one or more SRS resource sets (e.g., having the same / similar time domain behavior, periodic, aperiodic, etc.) may be transmitted at a certain time (e.g., at the same time). The UE may transmit one or more SRS resources in the SRS resource set. The NR network may support aperiodic, periodic, and / or semi-persistent SRS transmission. The UE may transmit SRS resources based on one or more trigger types, wherein 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 configured SRS resource set from one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in the same time slot, the UE may be configured to transmit SRS after transmission of PUSCH and corresponding uplink DMRS.

[0159] 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 non-periodic SRS); time slot, mini-slot, and / or subframe level periodicity; time slots of periodic and / or non-periodic SRS resources; the number of OFDM symbols in the SRS resources; the start OFDM symbol of the SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0160] The antenna ports are defined such that the channel through which a symbol on the antenna port is communicated can be inferred from the channel through 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, the receiver can infer the channel used to communicate the second symbol on the antenna port from the channel used to communicate the first symbol on the antenna port (e.g., fading gain, multipath delay, etc.). If one or more large-scale properties of the channel through which the first symbol on the first antenna port is communicated can be inferred from the channel through which the second symbol on the second antenna port is communicated, the first antenna port and the second antenna port can be referred to as quasi-co-located (QCLed). 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.

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

[0162] Fig. 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domain is shown. Fig. 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-RS. One or more of the following parameters may be configured for the CSI-RS resource configuration through 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 parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid) and / or other radio resource parameters.

[0163] Fig. 11B The three beams shown may be configured for a UE in a UE-specific configuration. Fig. 11B Three beams (beam #1, beam #2, and beam #3) are illustrated in FIG. 1 , and more or fewer beams may be configured. CSI-RS 1101 may be allocated to beam #1, which may be transmitted in one or more subcarriers in the RB of the first symbol. CSI-RS 1102 may be allocated to beam #2, which may be transmitted in one or more subcarriers in the RB of the second symbol. CSI-RS 1103 may be allocated to beam #3, which 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 subcarriers 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), a beam for a UE may be configured so that the beam for the UE uses symbols from beams of other UEs.

[0164] CSI-RS, such as Fig. 11BThose shown in (e.g., CSI-RS1101, 1102, 1103) may be transmitted by a base station and used by a UE for one or more measurement values. For example, a UE may measure a reference signal received power (RSRP) of a configured CSI-RS resource. The base station may configure the UE with a reporting configuration, and the UE may report the RSRP measurement value to the network (e.g., via one or more base stations) based on the reporting configuration. In the 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 the example, the base station may indicate 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 the example, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE may determine the spatial domain filter of the transmission (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam-corresponding capability, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate the uplink beam of the UE based on measurements of one or more SRS resources transmitted by the UE.

[0165] In the beam management procedure, the UE may assess (e.g., measure) the channel quality of one or more beam pair links, beam pair links including a transmit beam transmitted by a base station, and a receive beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters, the 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).

[0166] Fig. 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurements of 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 Tx beams of a TRP (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or the 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.

[0167] Fig. 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable a base station to perform measurements 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). Procedure U2 can be used to enable a base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or base station can perform procedure U2 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 U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0168] The UE may initiate a beam failure recovery (BFR) procedure based on detecting 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.).

[0169] The UE may measure the quality of a beam-to-link using one or more reference signals (RS), the one or more reference signals 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-to-link may 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 an RS resource. The base station may indicate that the RS resource is quasi-co-located (QCLed) with one or more DM-RS 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 a transmission to the UE via the RS resource are similar or identical to the channel characteristics from a transmission to the UE via the channel, the RS resource and the one or more DMRS of the channel may be QCLed.

[0170] 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 RRC_IDLE state and / or RRC_INACTIVE state may initiate a random access procedure to request a 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., uplink transmission for SR when there are no available PUCCH resources) and / or to obtain 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 a beam failure recovery request. The network may initiate a random access procedure for handover and / or for establishing time alignment for SCell addition.

[0171] Fig.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. Fig.13AThe procedure shown includes the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg3 1313, and Msg 4 1314. Msg 1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg2 1312 may include and / or be referred to as a random access response (RAR).

[0172] The 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 the UE 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.

[0173] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that can 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.

[0174] 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 Msg3 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 preamble transmission). There may be one or more power offsets 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 SSB and 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., SSB and / or CSI-RS) and / or uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplementary uplink (SUL) carrier).

[0175] 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). The 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 above 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.

[0176] The UE may determine the 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 an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the UE. If the association is configured, the UE 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., SSB and / or CSI-RS) for selecting a preamble and for determining 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.

[0177] If no response is received after the 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 the path loss measurement and / or the 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 the ramp-up step size for the preamble retransmission. The ramp-up step size may be the amount of incremental increase in the 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.

[0178] 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 is received by the base station. Msg 2 1312 may include a time alignment command that may be used by the UE to adjust the transmission timing of the UE, a scheduling grant for transmitting Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of 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 a PRACH opportunity. Examples of RA-RNTIs may be as follows:

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

[0180] Wherein 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 a NUL carrier and 1 for a SUL carrier).

[0181] The UE may transmit Msg3 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, Fig.13A Contention resolution in a contention-based random access procedure as shown in . In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to the UE. If the multiple UEs interpret the RAR as corresponding to themselves, a conflict may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) may 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., if a C-RNTI is assigned, the TC-RNTI included in Msg2 1312 and / or any other suitable identifier).

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

[0183] The 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 in an uplink carrier. For example, a base station may configure two separate RACH configurations for the UE: one for the SUL carrier and the other 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, if the measured quality of one or more reference signals is below a broadcast threshold, the UE may determine the SUL carrier. The uplink transmissions (e.g., Msg1 1311 and / or Msg 3 1313) of the random access procedure may remain on the selected carrier. In one or more cases, the UE may switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 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).

[0184] Fig. 13B The two-step contention-free random access procedure is shown. Fig.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. Fig. 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 Fig.13A As shown in Msg 1 1311 and Msg 2 1312. Fig.13A and Fig. 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 .

[0185] Can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover Fig. 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.

[0186] 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. Fig. 13B In the contention-free random access procedure shown, the UE may determine that the random access procedure is 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 is 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 a preamble identifier, the UE may determine that the random access procedure is successfully completed. The UE may determine that the response is an indication of a confirmation of the SI request.

[0187] Fig. 13C Another two-step random access procedure is shown. Fig.13A and Fig. 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. Fig. 13C The procedure shown includes the transmission of two messages: Msg A 1331 and Msg B 1332.

[0188] 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 Fig.13A The transmission block 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. Fig.13A and Fig. 13B Msg 2 1312 (eg, RAR) and / or Fig.13A The content of Msg 4 1314 shown is similar and / or identical.

[0189] The UE can initiate a call for licensed spectrum and / or unlicensed spectrum. Fig. 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 be: 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.

[0190] The UE may determine the radio resources and / or uplink transmission power of the preamble 1341 and / or the transport block 1342 included in the 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 of the preamble 1341 and / or the transport block 1342. The time-frequency resources (e.g., PRACH) used for transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) used for transmission of the transport block 1342 may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the reception timing and downlink channel for monitoring and / or receiving the Msg B 1332.

[0191] The transmission block 1342 may include data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 as a 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 a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if the following conditions exist: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 matches the identifier of the UE in Msg A 1331 (e.g., transmission block 1342).

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

[0193] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling grant indicating uplink radio resources and / or transport format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in a payload transmitted by the 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.

[0194] The base station may attach 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 a group of UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of UEs). Scrambling the CRC parity bits with the identifier may include a Modulo-2 addition (or an 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).

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

[0196] Depending on the purpose and / or content of the DCI, the base station may transmit DCI with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of 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 of 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 of 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 of 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 UE group. DCI format 2_1 may be used to notify a UE group 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 a transmission power control (TPC) command for PUCCH or PUSCH. DCI formats 2_3 may 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 may have different DCI sizes, or may share the same DCI size.

[0197] After scrambling the DCI with the RNTI, the base station may process the DCI with channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the coded and modulated DCI on resource elements used for and / or configured for 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. CCE may include the number of resource element groups (REGs) (e.g., 6). REG may include a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements may be based on the mapping of CCEs and REGs (e.g., CCE to REG mapping).

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

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

[0200] The base station may transmit an RRC message including configuration parameters of one or more CORESETs and one or more search space sets to the UE. The configuration parameters may indicate an association between a search space set and a 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 for each aggregation level; the PDCCH monitoring period and the PDCCH monitoring type; one or more DCI formats to be monitored by the UE; and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in the common search space set 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).

[0201] like Fig. 14B As shown, the UE may determine the time-frequency resources of the CORESET based on the RRC message. The UE may determine the CCE to REG mapping of the CORESET based on the configuration parameters of the CORESET (e.g., interlaced or non-interlaced and / or mapping parameters). The UE may determine the number of search space sets configured on the CORESET based on the RRC message (e.g., up to 10). The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates, which have possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the UE-specific search space) and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The UE 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, time slot format indications, downlink preemption, etc.).

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

[0203] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may 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 may use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 may occupy between four and fourteen OFDM symbols and may include two or fewer bits. If four or more symbols are transmitted and the number of HARQ-ACK / SR bits is one or two, the UE may use PUCCH format 1. PUCCH format 2 may occupy one or two OFDM symbols and may 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 may 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.

[0204] 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 multiple (e.g., maximum number) 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 (e.g., HARQ-ACK, SR, and / or CSI) based on the total bit length of the UCI information bits. 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".

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

[0206] Fig.15 An example of a wireless device 1502 communicating 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. Fig.15 Only one wireless device 1502 and one base station 1504 are shown in FIG. 1 , but it should be understood that the mobile communication network may include more than one UE and / or more than one base station, which have the same Fig.15 Configurations the same or similar to those shown.

[0207] The base station 1504 may connect the wireless device 1502 to a core network (not shown) by radio communication via 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 may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.

[0208] In the downlink, data to be sent from base station 1504 to wireless device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 via, for example, a core network. In the uplink, data to be sent from wireless device 1502 to base station 1504 may be provided to processing system 1518 of wireless device 1502. Processing system 1508 and 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 following: Figure 2B RRC layer.

[0209] 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, multiple-input multiple-output (MIMO) or multi-antenna processing, etc.

[0210] 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 reception 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, etc.

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

[0212] 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 codes that may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed herein. Fig.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 a 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.

[0213] 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 the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0214] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 may include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keyboard, a display, a touch pad, 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.). The processing system 1508 and / or the processing system 1518 may receive user input data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data to the one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from the 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 the GPS chipset 1517 and the GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide the geographical location information of the wireless device 1502 and the base station 1504, respectively.

[0215] Fig.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 to one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; and 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 Fig.16A Generate 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.

[0216] Fig. 16B An exemplary structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal for an antenna port. Filtering may be employed prior to transmission.

[0217] Fig. 16C An exemplary structure for downlink transmission is shown. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may include: scrambling coded bits in a codeword to be transmitted on a physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols on layers for transmission on antenna ports; mapping complex-valued modulation symbols for antenna ports to resource elements; generating complex-valued time-domain OFDM signals for antenna ports; and the like. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0218] Fig.16D Another exemplary structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex valued OFDM baseband signal at an antenna port. Filtering may be employed prior to transmission.

[0219] The wireless device may receive one or more messages (e.g., RRC messages) including configuration parameters of multiple cells (e.g., primary cells, secondary cells) from a base station. 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, and RRC layer. For example, the configuration parameters may include parameters for configuring physical layer and MAC layer channels, bearers, and the like. For example, the configuration parameters may include parameters indicating values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

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

[0221] The wireless device may receive / detect DCI in a PDCCH monitoring opportunity.

[0222] In an example, the DCI may schedule / activate / trigger a sidelink transmission (e.g., PSSCH, PSCCH, SPS). The wireless device may determine a time slot / symbol for the sidelink transmission based on a PDCCH monitoring occasion at which the wireless device receives the DCI. The wireless device may perform the sidelink transmission based on the time slot / symbol. The wireless device may perform the sidelink transmission, for example, after the time slot / symbol.

[0223] In an example, the DCI may indicate the transmission of HARQ-ACK information bits. The wireless device may determine a time slot / symbol based on the PDCCH monitoring opportunity at which the wireless device receives the DCI to multiplex the HARQ-ACK information bits in the uplink resources indicated by another DCI. For example, the wireless device may multiplex the HARQ-ACK information bits in the uplink resources based on the time slot / symbol occurring earlier than the duration starting from the first / starting / earliest symbol of the uplink resources / earlier than the duration. For example, the wireless device may not multiplex the HARQ-ACK information bits in the uplink resources based on the time slot / symbol occurring later than the duration starting from the first / starting / earliest symbol of the uplink resources / later than the duration (or after the duration).

[0224] In an example, the DCI may schedule an uplink transmission (e.g., a PUSCH). The wireless device may determine, based on a PDCCH monitoring opportunity, whether to consider the uplink transmission in a determination / calculation / calculation of a power headroom report in another uplink transmission scheduled by another DCI. For example, the wireless device may determine / calculate / calculate a power headroom report in another uplink transmission based on the uplink transmission in response to the PDCCH monitoring opportunity occurring before / before a PDCCH monitoring opportunity for receiving / detecting another DCI. For example, the wireless device may determine / calculate / calculate a power headroom report in another uplink transmission not based on the uplink transmission in response to the PDCCH monitoring opportunity occurring after / after a PDCCH monitoring opportunity for receiving / detecting another DCI.

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

[0226] In the prior art, the joint implementation of time slot / symbol determination and control channel repetition may cause ambiguity / misalignment. In an example, the wireless device may receive DCI via a first transmission / repetition opportunity among multiple transmission / repetition opportunities. The wireless device may determine the first time slot / symbol based on the first transmission / repetition opportunity for the wireless device to receive DCI.

[0227] The DCI may schedule / activate / trigger the sidelink transmission. In a prior art implementation, the wireless device may perform the sidelink transmission, for example, after the first time slot / symbol.

[0228] The DCI may indicate the transmission of the HARQ-ACK information bits. In an embodiment of the prior art, the wireless device may determine whether to multiplex the HARQ-ACK information bits in the uplink resources indicated by another DCI based on the first time slot / symbol.

[0229] The DCI may schedule an uplink transmission (eg, PUSCH). In a prior art implementation, the wireless device may determine based on the first transmission / repetition opportunity whether to consider the uplink transmission in determining / calculating / computing a power headroom report in another uplink transmission scheduled by another DCI.

[0230] In an example, the base station may not have information about which transmission / repetition opportunity among the multiple transmission / repetition opportunities the wireless device successfully received the DCI. In an example, the base station may determine the second time slot / symbol based on a second transmission / repetition opportunity among the multiple transmission / repetition opportunities. For example, the base station may randomly / blindly (or based on an unknown rule at the wireless device) determine the second time slot / symbol based on the second transmission / repetition opportunity.

[0231] The base station may determine whether to multiplex HARQ-ACK information bits by the wireless device in uplink resources indicated by another DCI based on the second slot / symbol.

[0232] The base station may determine based on the second transmission / repetition occasion whether the uplink transmission was considered by the wireless device in the determination / operation / calculation of the power headroom report in another uplink transmission scheduled by another DCI.

[0233] The first time slot / symbol (or first transmission / repetition opportunity) determined by the wireless device and the second time slot / symbol (or second transmission / repetition opportunity) determined by the base station may be different. Misalignment / ambiguity in the time slot / symbol may result in, for example, lost reception of sidelink transmissions. Misalignment / ambiguity in the time slot / symbol may result in, for example, lost reception of HARQ-ACK information bits. Misalignment / ambiguity in the time slot / symbol may result in, for example, inaccurate estimation / calculation of power headroom reports. This may result in increased retransmissions, increased latency / delay for successful communications, and increased power consumption.

[0234] The exemplary embodiment enhances / improves the time slot / symbol determination when the transmission of DCI is repeated by the base station in multiple transmission / repetition opportunities. In an exemplary embodiment, the wireless device and the base station can determine the reference transmission / repetition opportunity in multiple transmission / repetition opportunities based on predefined rules (for example, the last / end / first / starting transmission / repetition opportunity in multiple transmission / repetition opportunities, etc.). The wireless device and the base station can determine the common time slot / symbol based on the reference transmission / repetition opportunity. The use of common time slots / symbols (or reference transmission / repetition opportunities) can reduce the possibility of misalignment on the time slots / symbols used to determine power headroom reports, sidelink transmissions, and / or HARQ-ACK information bit multiplexing. This can reduce the waiting time / delay for successful communication, reduce power consumption, and reduce retransmissions.

[0235] The wireless device may perform a power headroom reporting procedure to indicate to the base station at least one of the following information: Type 1 power headroom (PH), which indicates the difference between the nominal maximum transmission power and the estimated power for UL-SCH transmission of each activated service cell configured with the wireless device; Type 2 PH, which indicates the difference between the nominal maximum transmission power and the estimated power for UL-SCH and PUCCH transmissions on the SpCell of another MAC entity (e.g., the E-UTRA MAC entity in EN-DC); Type 3 PH, which indicates the difference between the nominal maximum transmission power and the estimated power for SRS transmission of each activated service cell.

[0236] The wireless device may receive an RRC message indicating one or more parameters of a power headroom reporting procedure. The MAC entity of the wireless device may determine when to transmit a power headroom report (PHR) to a base station based on the one or more parameters. The wireless device may determine which cell and / or which type of power headroom needs to be reported via the PHR. For example, the one or more parameters may indicate a first value of a PHR periodic timer (e.g., phr-PeriodicTimer), a second value of a PHR prohibition timer (e.g., phr-ProhibitTimer), a PHR path loss change threshold (e.g., phr-Tx-PowerFactorChange), a presence / absence indicator of a PH value of other cells in the PHR (e.g., phr-Type2OtherCell), a mode (e.g., real or virtual) indicator of the PH (e.g., phr-ModeOtherCG), and / or a multiple PHR indicator (e.g., multiplePHR).

[0237] In an example, the MAC entity of the wireless device may trigger a PHR based on one or more conditions. For example, the wireless device may trigger a PHR under at least one of the following events: expiration of a first timer (e.g., phr-PeriodicTimer); when the power headroom reporting function is configured or reconfigured by an upper layer, which may not be used to disable the function; activation of the SCell of any MAC entity with a configured uplink; and / or addition of a PSCell (e.g., a PSCell may be added or changed).

[0238] In an example, for example, if the wireless device has UL resources allocated for a new transmission, the MAC entity of the wireless device may start a PHR periodicity timer if the first UL resource is allocated for the new transmission since the last MAC reset. For example, if the PHR procedure determines that at least one PHR has been triggered and not cancelled, and / or if the allocated UL resources accommodate the at least one PHR (e.g., as a result of logical channel prioritization, the MAC entity is configured to transmit a MAC CE of the PHR plus its subheader), the wireless device may transmit the at least one PHR to the base station. The PHR procedure and / or PHR format may be determined, for example, based on whether the base station configures the wireless device with a single-entry PHR format (e.g., multiple PHR indicators (e.g., multiplePHRs) are not configured) or a multiple-entry PHR format (e.g., multiple PHR indicators (e.g., multiplePHRs) are configured).

[0239] In an example, if the base station configures the wireless device with a multiple PHR indicator (e.g., by transmitting an RRC configuration parameter indicating a multiple-entry PHR format (e.g., multiplePHR)), the MAC entity of the wireless device may determine, for each of one or more activated cells with a configured uplink associated with the wireless device, a first value of a first type of power headroom (PH) (e.g., a type 1 PH determined based on a PUSCH transmission), or a third type of PH (e.g., a type 3 PH determined based on an SRS transmission). For example, the wireless device may determine whether the wireless device has UL resources allocated for transmission on at least one cell, or whether one or more other cells of the one or more activated cells have UL resources allocated for transmission on at least one cell, and the transmitted PHR configuration parameter indicating a PHR mode of the one or more cells indicates a real PH value (e.g., a mode (e.g., real or virtual) indicator of the PH (e.g., phr-ModeOtherCG) indicates a real PH value), a second value corresponding to PCMAX,c (described elsewhere in this specification), and the first value and the second value are transmitted via corresponding one or more fields in the PHR.

[0240] In an example, if a presence / absence indicator of a PH value of other cells in a PHR (e.g., phr-Type2OtherCell) is configured for the wireless device, and / or if the other MAC entity is a specific radio access technology (e.g., 4G) MAC entity, the MAC entity of the wireless device may determine a first value corresponding to a second type PH (e.g., Type 2 PH) of the SpCell of the other MAC entity. If the PHR mode of one or more cells indicates a true PH value (e.g., a mode (e.g., real or virtual) indicator of the PH (e.g., phr-ModeOtherCG) indicates a true PH value), the wireless device may determine a second value corresponding to PCMAX,c. The wireless device may transmit the first value and the second value via one or more corresponding fields in the PHR.

[0241] In an example, a MAC entity of a wireless device may trigger a multiplexing and assembly procedure for generating and transmitting a PHR (e.g., in the form of a PHR MAC CE). The PHR may include a first value of a first type PH, a second type PH, and / or a third type PH of at least one cell. For example, based on a configured serving cell index (e.g., ServCellIndex) and / or a configured PUCCH of the wireless device, the PHR may include a second value corresponding to PCMAX, c. The wireless device may, for example, start or restart a PHR periodic timer (e.g., periodicPHR-Timer) and / or a PHR prohibit timer (e.g., prohibitPHR-Timer) based on the transmitted PHR. The wireless device may, for example, cancel one or more triggered PHRs based on the transmitted PHR.

[0242] In an example, if the base station configures the wireless device with a single-entry PHR format (e.g., by transmitting a PHR configuration parameter indicating the single-entry PHR format, and / or by not configuring a PHR configuration parameter indicating the multiple-entry PHR format (e.g., if multiplePHR does not exist)), the wireless device may, for example, determine a first value of a first type PH or a third type PH for a corresponding uplink carrier of a cell (e.g., PCell). The wireless device may, for example, determine a second value corresponding to PCMAX,c. The wireless device may, for example, transmit a PHR to a base station (e.g., gNB) based on determining the first value and the second value. The PHR may include one or more fields indicating the first value and the second value. The wireless device may trigger a multiplexing and assembly procedure for generating and transmitting a PHR MAC CE including a value of the first type PH or the third type PH. The wireless device may, for example, start or restart a PHR periodic timer (e.g., periodicPHR-Timer) and / or a PHR prohibit timer (e.g., prohibitPHR-Timer) based on transmitting the PHR. The wireless device may, for example, cancel one or more triggered PHRs based on transmitting the PHR.

[0243] In an example, the MAC entity may determine whether the PH value of the activated serving cell is based on a real transmission or a (uplink) reference format based on a configured grant and downlink control information that may have been received up to and including a PDCCH opportunity in which, if a PHR MAC CE is reported on an uplink grant received on the PDCCH, or until the first uplink symbol of a PUSCH transmission minus a predefined PUSCH repair time, e.g., if a PHR MAC CE is reported on a configured grant, the first UL grant for a new transmission is received because the PHR has been triggered.

[0244] In an example, the PHR MAC CE may include at least one of the following:

[0245] A presence / absence indication field (e.g., Ci) indicating the presence of a PH field for a serving cell with cell ID i (e.g., ServCellIndex i). A Ci field set to "1" may indicate that a PH field for a serving cell with cell ID i (e.g., ServCellIndex i) is reported. A Ci field set to "0" may indicate that a PH field for a serving cell with cell ID i (e.g., ServCellIndex i) is not reported;

[0246] a reserved field (e.g., R) indicating one or more reserved bits (e.g., R is set to "0");

[0247] PH mode indicator (e.g., V), which indicates whether the PH value is based on a real transmission or a reference format. For type 1 PH, V=0 may indicate a real transmission on PUSCH, and V=1 may indicate the use of a PUSCH reference format. For type 2 PH, V=0 may indicate a real transmission on PUCCH, and V=1 may indicate the use of a PUCCH reference format. For type 3 PH, V=0 may indicate a real transmission on SRS, and V=1 may indicate the use of an SRS reference format. For type 1 PH, type 2 PH, and type 3 PH, V=0 may indicate the presence of an octet including the associated PCMAX, f, c fields, and V=1 may indicate that the octet including the associated PCMAX, f, c fields is omitted;

[0248] A PH field, which indicates the power headroom level;

[0249] A power backoff indicator field (e.g., P field) indicating whether the MAC entity applies power backoff due to power management. If the corresponding PCMAX, f, c fields have different values, the MAC entity may set P=1 if power backoff due to power management is not applied;

[0250] PCMAX,f,c field: If present, this field may indicate the PCMAX,f,c or P-CMAX,f,c of the serving cell used to determine the previous PH field.

[0251] In an example, the wireless device may determine whether the power headroom report of the activated serving cell is based on actual uplink transmission or reference uplink transmission based on the configured granted higher layer signaling. The wireless device may also determine whether the power headroom report is based on actual uplink transmission or reference uplink transmission based on one or more periodic / semi-persistent sounding reference signal transmissions. The wireless device may also determine whether the power headroom report is based on actual uplink transmission or reference uplink transmission based on downlink control information.

[0252] In an example, the wireless device may report the power headroom report on a PUSCH triggered / scheduled by a first DCI. The wireless device may receive downlink control information up to and including a PDCCH monitoring opportunity in which the wireless device detects a first DCI (e.g., DCI format 0_0 or DCI format 0_1) scheduling an initial transmission of a transport block due to triggering the power headroom report.

[0253] In an example, the wireless device may report the power headroom report on the PUSCH using the configured grant. The wireless device may receive downlink control information until the first uplink symbol of the configured PUSCH transmission minus a processing time (e.g., Tproc, 2). The processing time may be based on the capabilities of the wireless device. The processing time may be based on the subcarrier spacing of the active downlink BWP of the scheduling cell of the configured grant.

[0254] 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. The base station may transmit multiple PDCCHs within the control region to the wireless device. The wireless device may monitor multiple PDCCHs. The 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 error is detected, the wireless device may determine that the PDCCH carries its own control information.

[0255] Fig.17Exemplary 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 BWP downlinks). The one or more parameters of the serving cell configuration may indicate one or more uplink bandwidth parts (e.g., a list of BWP uplinks). 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 of a cell-common downlink bandwidth part (e.g., BWP-DownlinkCommon), and / or a configuration parameter of 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 index of the bandwidth part is a bandwidth part index. The bandwidth part configuration may include location and bandwidth information (locationAndBandwidth). locationAndBandwidth may indicate the starting resource block (RB) of the bandwidth part and the bandwidth of the bandwidth part based on a reference point (e.g., point A of the carrier / cell of the bandwidth part). The bandwidth part configuration may include a subcarrier spacing (e.g., subcarrierSpacing) and a cyclic prefix (e.g., cyclicPrefix). For example, the subcarrier spacing may be one of 15kHz, 30kHz, 60kHz, 120kHz, 240kHz, 480kHz, and 960kHz. For example, the cyclic prefix may be one of a normal cyclic prefix and an extended cyclic prefix.

[0256] The configuration parameters of 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 a cell-specific downlink bandwidth part (e.g., an initial BWP). For example, pdsch-ConfigCommon may include cell-specific parameters for receiving a PDSCH of a transport block (TB) via a cell-specific downlink bandwidth part. The configuration parameters of the UE-specific downlink bandwidth part (e.g., BWP-DownlinkDedicated) may include pdcch-Config, pdsch-Config, sps-Config and / or radioLinkMonitoringConfig (e.g., RLM-Config). The configuration parameters may include sps-ConfigList and / or beamFailureRecoverySCellConfig. For example, beamFailureRecoverySCellConfig may include reference signal parameters for beam failure recovery of 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 for a UE-specific downlink bandwidth portion. For example, sps-Config may include parameters for receiving a semi-persistently scheduled PDSCH. The base station may configure an SPS for a BWP or a list of SPSs for a BWP. For example, radioLinkMonitoringConfig may include parameters for radio link monitoring.

[0257] The configuration parameters of pdcch-Config may include at least one of a core set set, a search space set, downlink preemption (e.g., downlinkPreemption), a transmission power control (TPC) of PUSCH (e.g., tpc-PUSCH), a TPC of PUCCH, and / or a TPC of SRS. The configuration parameters may include a list of search space switching groups (e.g., searchesSpaceSwitchingGroup), a search space switching timer (e.g., searchSpaceSwitchingTimer), uplink cancellation, and / or a monitoring capability configuration (e.g., monitoringCapabilityConfig). The base station may configure a list of search space switching groups, where the 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 the BWP of the cell. Downlink preemption may indicate whether to monitor the downlink preemption indication of the cell. The monitoring capability configuration may indicate whether the monitoring capability of the wireless device will be configured for the cell, where the capability is based on a basic capability or an advanced capability. 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 of the monitoring cell.

[0258] The configuration parameters of pdcch-ConfigCommon may include a control resource set zero (e.g., controlResourceSetZero), a common control resource set (e.g., commonControlResourceSet), a 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. The control resource set zero may include parameters of a first core set with an index value of zero. Core set zero may be configured for an initial bandwidth portion of a cell. The wireless device may use control resource set zero in a BWP of a cell, where the BWP is not an initial BWP of the cell based on one or more conditions. For example, a parameter set of the BWP may be the same as a parameter set of an initial BWP. For example, the BWP may include an initial BWP. For example, the BWP may include control resource set zero. A common control resource set may be an additional common core set that may be used for a common search space (CSS) or a 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 the common control resource set is contained 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 a search space with an index of zero (e.g., SS#0). The first PDCCH monitoring opportunity may indicate the monitoring opportunity of the paging opportunity. 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 other SIBs outside SIB1 (e.g., searchSpaceOtherSystemInformation). A search space with an index of zero (e.g., searchSpaceZero, SS#0) may be configured for the initial BWP of the cell. Similar to corset#0, SS#0 may be used in the BWP of a cell based on one or more conditions.

[0259] Fig.18Exemplary configuration parameters of a core set according to aspects of an embodiment of the present disclosure are shown. 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., between interleaved and non-interleaved). When the CCE-REG mapping type is configured as interleaved, the base station may also configure the bundle size (e.g., reg-BundleSize) and interleaver size (e.g., interleaverSize) of the REG. 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 'same as the REG 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 in the contiguous RBs across the core set use the same precoder. The core set may include a list of TCI states, where the core set is not core set #0. The core set may include parameters for the presence of TCI in the DCI. If the core set is configured with the presence of TCI in the DCI, the wireless device may anticipate including a DCI format indicating TCI 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. The 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), a TCI that appears in the DCI for DCI format 1_2, and an RB offset. For example, when an enhanced core set index is present in the core set configuration, the wireless device may ignore the core set index. The enhanced core set index may indicate a value between [0, ..., 15], while the core set index may indicate a value between [0, ..., 11].

[0260] A core set is associated with a search space, wherein the wireless device can determine search space candidates and / or monitoring timing of 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 timing of 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 a core set is associated with a search space, a parameter of the search space may include an index of the core set.

[0261] 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 used for the period, an offset 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 each slot within the interval / period). The search space may include monitoring symbols within a slot (e.g., a bitmap of OFDM symbol sizes in a slot (e.g., 12 for extended cyclic prefix (CP) and 14 for normal CP)). The search space may include a set of multiple candidates for each 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 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 USS, the base station may configure a list of search space group indices (if configured). For 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.

[0262] 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, (virtual RB) VRB to (physical RB) PRB interleavers, resource allocation types (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, RBG (resource block group) size, MCS table (e.g., between QAM 256 and QAM64LowSE, between high MCS or low MCS), a maximum codeword (e.g., between 1 or 2), parameters related to PRB bundling, a maximum MIMO layer, a minimum scheduling offset related to power saving techniques, and / or one or more parameters related to DCI formats 1_2 (e.g., compact DCI or small DCI formats).

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

[0264] 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 correspond to an AL of sixteen (AL = 16).

[0265] 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...). 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 from 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 the fact that all RBs of the first symbol may have been indexed, the wireless device may move to the next symbol. The wireless device may map one or more REG indexes to one or more 6 RBs of the N_rb_coreset RBs within the N_symbol_coreset OFDM symbols of the core set.

[0266] 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 a 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 of the core set may be interlaced or non-interlaced to REGs. 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 can be interleaved, the function f(x) can be defined as (rC+c+n_shift) mod(N_reg_coreset / L), where x=cR+r, r=0, 1…R-1, c=0, 1…C-1, C=N_reg_coreset / (L*R), and R is one of {2,3,6}.

[0267] 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 the 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 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 adjacent RBs of a core set.

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

[0269] In an example, a base station may transmit one or more messages including configuration parameters. The configuration parameters may be used for multiple serving cells of a wireless device. The configuration parameters may include parameters for enabling control channel repetition. For example, control channel repetition may be transmitted via one or more serving cells. Control channel repetition may schedule one or more resources for a transport block. A transport block may be transmitted via one or more PDSCHs or one or more PUSCHs. For example, 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 in multiple carriers / cells) via one or more resources in different frequency resources (e.g., or multiple downlink control signal / channel transmission opportunities). 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 in multiple time slots) via one or more second resources in different time resources (e.g., or multiple downlink control signal / channel transmission opportunities). One or more second resources may overlap in the frequency domain. For example, the base station may transmit repetitions of control channel repetitions 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.

[0270] In an example, control channel repetition may be transmitted via multiple PDCCHs. For example, a PDCCH may indicate a physical control channel transmitted in one 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 PDCCH in multiple PDCCHs may be transmitted via a search space in multiple search spaces. Multiple PDCCHs may be transmitted via multiple search space candidates, wherein each PDCCH in multiple PDCCHs may be transmitted via a corresponding search space candidate in 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 on a monitoring opportunity. The 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 a DCI / PDCCH.

[0271] In an example, a PDCCH in a plurality of PDCCHs for control channel repetition may convey / transmit a DCI based on a DCI format. For example, a first DCI of a first PDCCH in a plurality of PDCCHs may be the same as a second DCI of a second PDCCH in a plurality of PDCCHs. For example, the content of a first DCI / PDCCH may be the same as the content of a second DCI / PDCCH. Based on the same content of a plurality of PDCCHs, a wireless device may aggregate a plurality of DCI / PDCCHs before decoding the DCI / PDCCH. For example, when a control channel repetition is transmitted / performed via a DCI / PDCCH of the same 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, a wireless device may determine an aggregated DCI / PDCCH by aggregating a plurality of DCI / PDCCHs. The wireless device may decode the aggregated DCI / PDCCH.

[0272] 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 the reference CCE index and / or the 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 multiple DCI / PDCCHs. For example, the minimum (or maximum) core set index of one or more CORESETs can be used for this determination.

[0273] The reference frequency domain (and / or time domain) resources of multiple DCI / PDCCHs can be determined based on the search space index of one or more search spaces for transmitting multiple DCI / PDCCHs. For example, the minimum (or maximum) index of one or more search spaces can be used for the determination. The reference frequency domain resources of multiple DCI / PDCCHs can be determined based on the cell index of one or more cells for transmitting multiple DCI / PDCCHs. For example, the minimum (or maximum) index of one or more cells can be used for the determination. Similarly, the reference time domain resources and / or the reference CCE index and / or the reference REG can be determined based on the CORESET index, the search space index and / or the cell index. A combination of transmission time, CORESET index, search space and / or cell index can be used. For example, the reference frequency domain resources can be first determined based on the transmission time of the DCI / PDCCH. When multiple DCI / PDCCHs are transmitted simultaneously, the wireless device can use the CORESET index or the search space index and / or the cell index to further identify the reference DCI / PDCCH in 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.

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

[0275] In an example, a first DCI / PDCCH in a plurality of DCI / PDCCHs may be different from a second DCI / PDCCH in a plurality of DCI / PDCCHs. For example, the wireless device may not aggregate the first DCI / PDCCH and the second DCI because the content of the first DCI / PDCCH may be different. The wireless device may attempt to decode the first DCI / PDCCH separately from the second DCI / PDCCH. For example, when the wireless device has received at least one DCI / PDCCH in a plurality of DCI / PDCCHs, the wireless device may complete decoding of the control channel repetition. For example, when the wireless device has received at least one DCI / PDCCH in a plurality of DCI / PDCCHs, the wireless device may be able to receive or transmit TBs scheduled by a plurality of DCI / PDCCHs. In the specification, this type of control channel repetition (e.g., transmitting content that may be different via a plurality of DCI / PDCCHs, a DCI / PDCCH in a plurality of DCI / PDCCHs may schedule one or more resources of a transport block) may be referred to as / 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 each DCI / PDCCH received by the wireless device.

[0276] Fig.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 scheduling carriers / cells for transmitting one or more PDCCH / DCI for repeating control channels (or control channel repetition). The parameters may include one or more search spaces for control channel repetition. Fig.19 An example of enabling control channel repetition via a first search space (SS#1) of a first carrier / cell (DL carrier #0) is shown. 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, the first PDCCH scheduling a TB via the first carrier. The base station may transmit a second PDCCH via the first search space of the first carrier, the second PDCCH scheduling a TB via the first carrier. The first PDCCH and the second PDCCH may be transmitted via multiple monitoring opportunities of the first search space. The wireless device may aggregate the first PDCCH and the second PDCCH based on the first control channel repetition mode, or may attempt to independently receive / decode each PDCCH based on the second control channel repetition mode. Based on the first PDCCH and / or the second PDCCH, the wireless device may receive a TB.

[0277] 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 of the first carrier / cell for the control channel repetition based on the active BWP of the first carrier / cell. For example, 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, one or more RRC messages may indicate one or more search space indexes of one or more first search spaces for control channel repetition. One or more RRC messages may indicate one or more DCI formats in which the wireless device may apply control channel repetition. The wireless device may determine one or more first search spaces of the first carrier / cell based on one or more DCI formats for control channel repetition.

[0278] In an example, a base station may transmit multiple DCI / PDCCHs via multiple TRPs or via multiple core set pools or via multiple core set groups, thereby scheduling resources for a transport block of a cell. For example, a base station may configure a first TRP (or a first core set pool) for a first cell via one or more RRC messages. One or more RRC messages may include configuration parameters. 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 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 a first core set pool. The base station may transmit a second DCI / PDCCH via a second search space of a second core set of a 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. A transport block may be transmitted based on multiple TCI states. The transport block may be transmitted based on a TCI state, wherein 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.

[0279] The configuration parameter may indicate control channel repetition enabled / configured for the first cell. For example, the parameters of the 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 a pair of a first core set and a second core set based on a rule, wherein repeated DCI / PDCCHs may be transmitted. For example, the wireless device may determine a first core set of a first core set pool based on a search space associated with the first core set, wherein the wireless device may monitor a DCI format via the search space. For example, the DCI format may be DCI format 1_1 or DCI format 0_1 ​​or DCI format 1_2 or DCI format 0_2 (or DCI format 3_0 or DCI format 3_1). When there are multiple first search spaces of the first core set pool configured with the DCI format, the wireless device can determine multiple first core sets of the first core set pool. Similarly, the wireless device can determine a second core set of the second core set pool based on the search space associated with the second core set, wherein the wireless device can monitor the DCI format via the search space. When there are multiple second search spaces of the second core set pool configured with the DCI format, the wireless device can determine multiple second search spaces. In an example, the wireless device can be configured with at most one search space for the DCI format in each core set pool.

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

[0281] In an example, a base station may indicate control channel repetition based on (or for) a core set. For example, a base station may transmit multiple DCI / PDCCHs via a core set. A base station may transmit multiple DCI / PDCCHs via multiple TRPs. A base station may transmit one of multiple RRC messages and / or MAC CEs indicating activation of multiple TCI states for a core set. For example, multiple TCI states may include a first TCI state corresponding to a first TRP in multiple TRPs, and a second TCI state corresponding to a second TRP in multiple TRPs. A base station may transmit one or more second RRC messages including configuration parameters for a core set. For example, a configuration parameter may indicate control channel repetition based on a core set. A configuration parameter may indicate control channel repetition across multiple TRPs. A configuration parameter may indicate a repetition pattern across multiple TRPs. For example, a repetition pattern (e.g., a TRP switching pattern) may be [0, ..., 0, 1, ..., 1], where 0 may represent a first TRP in multiple TRPs, and 1 may represent a second TRP in multiple TRPs. A base station may indicate a bitmap indicating the number of control channel repetitions, for example, by a configuration parameter. 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 a control channel repetition based on a TCI state among a plurality of TCI states. For example, when the repetition pattern indicates a first TRP, the wireless device may receive a control channel repetition based on the first TCI state. When the repetition indicates a second TRP, the wireless device may receive a control channel repetition based on a second TCI state.

[0282] Fig. 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 / include a first TRP (TRP#0) and a second TRP (TRP#1) associated with a cell. The configuration parameters may include / indicate control channel repetition across multiple TRPs (e.g., via the first TRP and the second TRP). The base station may transmit a first DCI / PDCCH (e.g., PDCCH#1) via the first TRP or the first core set pool. The first DCI / PDCCH may include / indicate resources for scheduling TBs via multiple TRPs. The base station may transmit a second DCI / PDCCH (e.g., PDCCH#2) via the second TRP or the second core set pool. The second DCI / PDCCH may include / indicate resources for scheduling TBs via multiple TRPs. The first DCI / PDCCH and the second DCI / PDCCH may indicate the same HARQ process index (e.g., HARQ-K) for scheduling 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 a second TRP. The control information for scheduling TBs may be repeated four times via multiple TRPs. The wireless device may monitor the first DCI / PDCCH and the third DCI / PDCCH based on a first TCI state associated with a first TRP or a first core set pool. The wireless device may monitor the second DCI / PDCCH and the fourth DCI / PDCCH based on a second TCI state associated with a second TRP or a second core set pool.

[0283] The base station may repeat the TB via four repetitions of the first TRP and four repetitions of the second TRP. When the wireless device may support simultaneous reception via the first TRP and the second TRP, the wireless device may repeat the TB via the first TRP and the second TRP simultaneously. 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.

[0284] 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 that schedule a transport block via multiple core sets of 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 in a set of first TCI states of 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 MACs may indicate a second TCI state in the set of second TCI states of 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.

[0285] In an example, a configuration parameter may indicate / include a search space associated with a first core set and a second core set. The configuration parameter may include a plurality of core set indices. The configuration parameter may include a core set index indicating the first core set in the plurality of core set indices. The configuration parameter may include one or more indices of a repeated / additional core set (e.g., a core set for control channel repetition in addition to the first core set and the second core set) in the plurality of core set indices. For example, an index in 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, a first parameter of the first core set and a second parameter of the second core set may be limited in configuration. For example, a set of resource blocks (RBs) in the frequency domain of the first core set may be the same as a set of resource blocks (or a subset or superset of the set of resource blocks) in the frequency domain of the second core set. The wireless device may determine a set of RBs belonging to the first core set and the second core set for control channel repetition. For example, a first duration of the first core set may be the same as a second duration of the second core set. For example, a plurality of REGs of the first core set may be the same as a plurality of REGs. For example, the number of CCEs of the first core set may be the same as (or less than or greater than) the number of CCEs of 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 of the first core set (e.g., between interlaced or non-interlaced) 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.

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

[0287] When the wireless device may receive a first configuration parameter for a first core set and a second configuration parameter 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 the determination, the wireless device may deem that the first core set and the second core set may be used for control channel repetition. Otherwise, the wireless device may determine that the first core set and the second core set are not available 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 of one or more core sets (e.g., determining a core set with a minimum number of CCEs in one or more core sets). For example, one or more core sets may be configured / indicated / used for control channel repetition. The wireless device may determine / assume / consider the top M candidates for each core set in one or more core sets for control channel repetition.

[0288] In an example, the wireless device may determine a 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 that the control channel repetition is configured via the first core set and the second core set. Otherwise, the wireless device may consider the configuration as an error condition and may not activate the 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 one or more core sets (e.g., determine a core set with a minimum number of REGs). The wireless device may assume a minimum number of REGs for control channel repetition.

[0289] The configuration parameters of the search space associated with the first core set and the second core set may include / indicate a switching mode or mapping mode of the first core set and the second core set. For example, the wireless device may determine the search space monitoring opportunity based on the configuration parameters of the search space. The wireless device may determine the search space monitoring opportunity based on the first core set. The wireless device may determine the second search space monitoring opportunity or the 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 of 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 several 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 the OFDM symbol, the wireless device may monitor the search space monitoring opportunity based on the first core set. When 1 is indicated for the second OFDM symbol, the wireless device may monitor the second search space monitoring opportunity based on the second core set.

[0290] 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 parameters of the search space 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 parameters of the search space may indicate a second monitoring period in units of a second duration. For example, the second duration may be one OFDM symbol or several OFDM symbols or one time slot. For example, the second duration may be less than the first duration. The wireless device may monitor one or more 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.

[0291] For example, the wireless device may receive / monitor the first DCI / PDCCH in one or more repeated DCI / PDCCHs via the first monitoring opportunity in one or more monitoring opportunities. The wireless device may receive / monitor the second DCI / PDCCH in one or more repeated DCI / PDCCHs via the 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 DCI may include one or more candidates for one or more monitoring opportunities. For example, the search space candidates may include the first candidate for the first monitoring opportunity and the 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.

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

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

[0294] Fig.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 or 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. Fig.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 two time slots). 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 a monitoring opportunity starting from the first OFDM symbol of the time slot. Fig.21 In an example of , 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.

[0295] In an example, a configuration parameter indicates one or more monitoring opportunities within a monitoring period for a search space. For example, monitoringSlotPeriodicityAndOffset can 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 the time slot based on monitoringSymbolWithinSlot. The wireless device may expect that the intervals between monitoring opportunities within the time slot are equal. 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 can be used to indicate one or more monitoring opportunities within the monitoring period determined based on monitoringSlotPeriodicityAndOffset. For example, a parameter for indicating enabling control channel repetition can be configured for a search space or 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 can be used to determine one or more monitoring opportunities within the monitoring period. For example, when the monitoring period is greater than the time slot, the wireless device can determine one or more monitoring opportunities based on the monitoring period and the duration. For example, when the monitoring period is P time slots and the duration is D, the wireless device may determine a first monitoring occasion among the one or more monitoring occasions based on monitoringSlotPeriodicityAndOffset. The wireless device may determine a second monitoring occasion among the one or more monitoring occasions as a next time slot of the first monitoring occasion. The wireless device may determine D monitoring occasions starting from the first monitoring occasion 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).

[0296] In an example, a 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 resource for a transport block. The first content of the first DCI / PDCCH may be the same 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 at one or more monitoring opportunities. The base station may transmit a single DCI / PDCCH at one or more monitoring opportunities. The base station may transmit a DCI / PDCCH at each monitoring opportunity. The base station may transmit any number of repeated DCI / PDCCHs at one or more monitoring opportunities.

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

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

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

[0300] The wireless device may not aggregate candidates, wherein the candidates may not include candidates from the first monitoring opportunity (or the first monitoring opportunity, 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 opportunity, the first+second+third+fourth monitoring opportunity, the first+second+third+fourth+fifth-sixth+seventh+eighth, etc.

[0301] In an example, the wireless device may determine a candidate list of aggregation levels 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.

[0302] 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 controlling channel repetition. The search space group may include one or more search spaces. For example, the search group may include a first search space of a first carrier and a second search space of a second carrier. For example, the search space group may include a first search space of a first BWP of a cell and a second search space of a second BWP of a cell. For example, the search space group may include a first search space of a first BWP of a first cell and a second search space of a second BWP of a second cell. For example, for a BWP of a cell, a configuration parameter may indicate one or more search space groups. A search space group in 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, wherein each of the one or more search spaces may be configured to monitor a DCI format in one or more DCI formats. For example, one or more DCI formats may include DCI format 1_1 and DCI format 0_1. For example, one or more DCI formats may include DCI format 0_0 and DCI format 1_0. For example, one or more DCI formats may include DCI format 1_2 and DCI format 0_2. For example, one or more DCI formats may include DCI format 3_0 and DCI format 3_1. For example, one or more DCI formats may include downlink / uplink DCI 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 a sidelink DCI.

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

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

[0305] In an example, the base station may associate multiple TCI states with a core set as an active TCI state. Fig. 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, the base station may indicate multiple monitoring opportunities in a time slot or a monitoring period of control channel repetition. The wireless device may monitor the first monitoring opportunity based on the first TCI state in the multiple TCI states. The wireless device may monitor the second monitoring opportunity based on the second TCI state in the multiple TCI states. The base station may indicate a mode of switching between multiple TCI states. For example, the configuration parameters of the search space associated with the core set may include / indicate enabling control channel repetition. The configuration parameters may include / indicate enabling TCI switching or enabling control channel repetition via multiple TCI states. The configuration parameters may include / indicate a switching mode. For example, the switching mode may be an alternation between a first TCI state in multiple TCI states and a second TCI state in multiple TCI states in each of one or more monitoring opportunities in a monitoring period or time slot or several time slots (e.g., between monitoring periods configured by the MonitoringSlotPeriodicityAndOffset parameter of the search space). For example, the switching mode may be half and half 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.

[0306] Fig.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) indicating / activating / updating / selecting one or more TCI states (e.g., TCI state 1 and TCI state 2) of a core set of a serving cell is shown. The 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 of a core set (indicated by a core set ID). The one or more TCI state indexes may indicate / identify one or more TCI states. Each TCI state index in the one or more TCI state indexes may indicate / identify a corresponding TCI state in the one or more TCI states. The MAC CE format may include one or more fields. The first field in 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), which 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. One or more TCI states may include a 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 of the MAC CE format may include a second TCI state index based on the value of the fourth field (e.g., R). For example, when the value of the fourth field is equal to zero, the MAC CE format may not include the second TCI state index (e.g., the fifth field may be a reserved field). When the value of the fourth field is equal to one, the MAC CE format may include the second TCI state index. One or more TCI states may include the second TCI state. The MAC CE format may be an activation command. The configuration parameter may indicate a first TCI state index of a first TCI state. The configuration parameter may indicate a second TCI state index of a second TCI state. The configuration parameter may indicate a core set index of a core set. The configuration parameter may indicate a serving cell index of a serving cell. The configuration parameter may indicate one or more TCI state indexes of 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.

[0307] Fig.24 , Fig.25 and Fig.26 is an example of control channel repetition according to one aspect of an embodiment of the present disclosure.

[0308] In an example, the 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.

[0309] In an example, one or more configuration parameters may be for a cell. In an example, at least one of the one or more configuration parameters may be for a cell. In an example, a cell may be a primary cell (PCell). In an example, a 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, a cell may be, for example, an unlicensed cell operating in an unlicensed band. In an example, a cell may be, for example, a licensed cell operating in a licensed band. In an example, a cell may operate in a first frequency range (FR1). For example, FR1 may include a frequency band below 6 GHz. In an example, a cell may operate in a second frequency range (FR2). For example, FR2 may include a frequency band from 24 GHz to 52.6 GHz.

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

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

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

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

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

[0315] 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 / 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 PDSCH on / via / for 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 / via / for 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 / via / for 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.

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

[0317] In an example, the wireless device may activate a downlink BWP among 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.

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

[0319] 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 configuration parameter of the one or more configuration parameters may be for a downlink BWP of a cell.

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

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

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

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

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

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

[0326] In an example, one or more configuration parameters may indicate, for example, multiple search space sets for a downlink BWP of a cell (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).

[0327] In an example, one or more configuration parameters may indicate a search space set index / identifier of 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 the 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.

[0328] In an example, one or more configuration parameters may indicate a PDCCH monitoring period (e.g., monitoringSlotPeriodicityAndOffset) for multiple 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 multiple 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 multiple 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 multiple search space sets.

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

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

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

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

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

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

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

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

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

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

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

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

[0341] 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 a plurality of DCI / PDCCHs (eg, Figure 24 to Figure 26 1 and DCI 2 in ). The wireless device may monitor the PDCCH candidate 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 to 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 to Figure 26 DCI 1 in ) and a second downlink control signal / channel (eg, Figure 24 to Figure 26 DCI 2).

[0342] In an example, a wireless device may be served by (e.g., receive from or transmit to) multiple TRPs (e.g., TRP 1 and TRP 2). Each downlink control signal / channel of the multiple DCI / PDCCHs may be transmitted by a corresponding TRP in the multiple TRPs. Figure 24 to Figure 26 In the embodiment, a first TRP (e.g., TRP 1) among multiple TRPs can transmit DCI1, and a second TRP (e.g., TRP 2) among multiple TRPs can transmit DCI 2.

[0343] 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 to Figure 26In the embodiment, DCI 1 and DCI 2 may be the same (or equal). The content of DCI 1 and DCI 2 may be the same. The payload of DCI 1 and DCI 2 may be the same. The DCI field (or the value of the DCI field) of DCI 1 and DCI 2 may be the same.

[0344] In an example, the first downlink control signal / channel and the second downlink control signal / channel may be the same (e.g., same content, same DCI field, same DCI size, same payload, same DCI field value, etc.). In an example, the first downlink control signal / channel and the second downlink control signal / channel may be the same as 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 a repetition of the downlink control signal / channel.

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

[0346] For multiple DCI / PDCCHs, the wireless device may monitor one or more core sets for repetitions of downlink control signals / channels. For each downlink control signal / channel in the multiple DCI / PDCCHs, the wireless device may monitor a corresponding core set in the one or more core sets. For multiple DCI / PDCCHs, monitoring one or more core sets for repetitions of downlink control signals / channels may include monitoring one or more core sets for repetitions of downlink control signals / channels. For multiple DCI / PDCCHs, monitoring one or more core sets for repetitions of downlink control signals / channels may include monitoring one or more core sets for repetitions of downlink control signals / channels. For multiple DCI / PDCCHs, the wireless device may monitor multiple search space sets associated with the one or more core sets for repetitions of downlink control signals / channels. 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 repetitions of downlink control signals / channels. For example, in Figure 24 to Figure 26 In the embodiment of the present invention, 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 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.

[0347] In an example, the wireless device may determine a plurality of downlink control signal / channel transmission / repetition opportunities (e.g., PDCCH transmission / repetition / monitoring opportunities) for control channel repetition. The wireless device may determine a plurality of downlink control signal / channel transmission / repetition opportunities (or a plurality of PDCCH monitoring opportunities or a plurality of time slots) for repetition of the downlink control signal / channel. The base station may determine a plurality of downlink control signal / channel transmission / repetition opportunities (e.g., PDCCH monitoring opportunities or a plurality of time slots) for repetition of the downlink control signal / channel via one or more core sets. Figure 24 to Figure 26The base station may transmit a downlink control signal / channel across multiple downlink control signal / channel transmission / repetition opportunities / within the multiple downlink control signal / channel transmission / repetition opportunities / on the multiple downlink control signal / channel transmission / repetition opportunities / in the multiple downlink control signal / channel transmission / repetition opportunities via one or more core sets. The base station may transmit a downlink control signal / channel across multiple downlink control signal / channel transmission / repetition opportunities / within the multiple downlink control signal / channel transmission / repetition opportunities / on the multiple downlink control signal / channel transmission / repetition opportunities via each core set in the one or more core sets across the corresponding downlink control signal / channel transmission / repetition opportunities / within the corresponding downlink control signal / channel transmission / repetition opportunities / on the corresponding downlink control signal / channel transmission / repetition opportunities / in the corresponding downlink control signal / channel transmission / repetition opportunities. The base station may repeat transmission of a downlink control signal / channel across multiple downlink control signal / channel transmissions / repetition opportunities / within multiple downlink control signal / channel transmissions / repetition opportunities / on multiple downlink control signal / channel transmissions / repetition opportunities. For example, in Figure 24 to 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.

[0348] The wireless device may monitor one or more core sets for multiple DCI / PDCCHs across multiple downlink control signals / channel transmissions / repetition opportunities / within multiple downlink control signals / channel transmissions / repetition opportunities / on multiple downlink control signals / channel transmissions / repetition opportunities. The wireless device may monitor one or more core sets for a downlink control signal / channel across multiple downlink control signals / channel transmissions / repetition opportunities / within multiple downlink control signals / channel transmissions / repetition opportunities / on multiple downlink control signals / channel transmissions / repetition opportunities. The wireless device may monitor each core set in the one or more core sets for a downlink control signal / channel across a corresponding downlink control signal / channel transmission / repetition opportunity in a plurality of downlink control signals / channel transmissions / repetition opportunities / within the corresponding downlink control signal / channel transmission / repetition opportunity / on the corresponding downlink control signal / channel transmission / repetition opportunity. The wireless device may monitor one or more core sets for repetition of a downlink control signal / channel across / within / on / in multiple downlink control signal / channel transmissions / repetition opportunities. For example, Figure 24 to Figure 26 In the embodiment, the wireless device monitors a first core set in a first downlink control signal / channel transmission / repetition opportunity for a first downlink control signal / channel. The wireless device monitors a second core set in a second downlink control signal / channel transmission / repetition opportunity for a second downlink control signal / channel.

[0349] The wireless device may monitor one or more core sets across / within / on / in multiple downlink control signal / channel transmission / repetition opportunities. The wireless device may monitor each core set in the one or more core sets across / within / on / in / 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 / a corresponding downlink control signal / channel transmission / repetition opportunity 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 one or more second downlink control signal / channel transmission / repetition opportunities in a plurality of downlink control signal / channel transmission / repetition opportunities / within / on / in the one or more second 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.

[0350] The base station may transmit the downlink control signal / channel via each core set in one or more core sets across a corresponding downlink control signal / channel transmission / repetition opportunity in a plurality of downlink control signal / channel transmission / repetition opportunities / within the corresponding downlink control signal / channel transmission / repetition opportunity / on the corresponding downlink control signal / channel transmission / repetition opportunity. For example, the base station may transmit the downlink control signal / channel via the first core set 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 / in one or more first downlink control signal / channel transmission / repetition opportunities. The base station may transmit the downlink control signal / channel via the second core set 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 / in one or more second downlink control signal / channel transmission / repetition opportunities.

[0351] In an example, the repetition of a downlink control signal / channel (or the transmission of multiple DCI / PDCCHs) may occur, for example, in a time unit (e.g., by TDM). For example, the time unit may be continuous. For example, the time unit may not be continuous. 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 micro-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 monitoring opportunity in time (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 a time unit / in a time unit. For example, a first downlink control signal / channel transmission opportunity among multiple downlink control signal / channel transmission opportunities may occur in a first time unit in a time unit / in the first time unit. A second downlink control signal / channel transmission opportunity among multiple downlink control signal / channel transmission opportunities may occur in a second time unit in a time unit / in the second time unit, and so on.

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

[0353] 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 the 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 repeated number. For example, in Figure 24 to 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 in the time unit (e.g., a first time slot, a first symbol, a first subframe, a first PDCCH monitoring opportunity) / in the first time unit. The second downlink control signal / channel transmission opportunity may occur in a second time unit in the time unit (e.g., a second time slot, a second symbol, a second subframe, a second PDCCH monitoring opportunity) / in the second time unit. The first downlink control signal / channel transmission opportunity may occur in a first frequency unit in the 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) / in the first frequency unit. The second downlink control signal / channel transmission opportunity may occur in a second frequency unit in the 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) / in the second frequency unit.

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

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

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

[0357] In an example, the repetition scheme may be a time domain repetition scheme (e.g., TDM scheme, intra-slot repetition, inter-slot repetition, TDM scheme A, TDM scheme B, etc.). In the time domain repetition scheme, multiple downlink control signal / channel transmission opportunities (e.g., the first TX opportunity and the second TX opportunity) may not overlap in time. In the time domain repetition scheme, multiple downlink control signal / channel transmission opportunities may or may not overlap in frequency. Each downlink control signal / channel transmission opportunity in multiple downlink control signal / channel transmission opportunities may have non-overlapping time domain resource allocation relative to other signals / channel transmission opportunities in multiple downlink control signal / channel transmission opportunities. For example, the first downlink control signal / channel transmission opportunity in multiple downlink control signal / channel transmission opportunities may not overlap in time with the second downlink control signal / channel transmission opportunity in 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, a first time unit and a second time unit may not overlap in time. The first time unit and the second time unit may be different.

[0358] In an example, the repetition scheme may be a frequency domain repetition scheme (e.g., FDM scheme, FDMSchemeA, FDMSchemeB, etc.). In a frequency domain repetition scheme, multiple downlink control signals / channel transmission opportunities may or may not overlap in time. In a frequency domain repetition scheme, multiple downlink control signals / channel transmission opportunities may not overlap in frequency. Each downlink control signal / channel transmission opportunity in multiple downlink control signals / channel transmission opportunities may have non-overlapping frequency domain resource allocation relative to other signals / channel transmission opportunities in multiple downlink control signals / channel transmission opportunities. For example, the first downlink control signal / channel transmission opportunity in multiple downlink control signals / channel transmission opportunities may not overlap in frequency with the second downlink control signal / channel transmission opportunity in multiple downlink control signals / channel transmission opportunities. The first downlink control signal / channel transmission opportunity and the second downlink control signal / channel transmission opportunity may be different. For example, in a frequency domain repetition scheme, the first downlink control signal / channel transmission opportunity (first TX opportunity) and the second downlink control signal / channel transmission opportunity (second TX opportunity) may not overlap in frequency. The first downlink control signal / channel transmission 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 part, 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.

[0359] In an example, the repetition scheme may be a spatial domain / code domain repetition scheme (e.g., SFN scheme, SDM scheme, CDM scheme, SDM scheme, CDM scheme, etc.). In the spatial domain / code domain repetition scheme, multiple downlink control signal / channel transmission opportunities may overlap in time. In the spatial domain / 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 downlink control signal / channel transmission opportunity in multiple downlink control signal / channel transmission opportunities may have non-overlapping frequency domain resource allocations with respect to other downlink control signal / channel transmission opportunities in multiple downlink control signal / channel transmission opportunities. Each downlink control signal / channel transmission opportunity in multiple downlink control signal / channel transmission opportunities may have non-overlapping time domain resource allocations with respect to other downlink control signal / channel transmission opportunities in multiple downlink control signal / channel transmission opportunities. Each downlink control signal / channel transmission opportunity in multiple downlink control signal / channel transmission opportunities may be the same. For example, a first downlink control signal / channel transmission opportunity among multiple downlink control signal / channel transmission opportunities may overlap with a second downlink control signal / channel transmission opportunity among multiple downlink control signal / channel transmission opportunities in time and frequency. 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 domain / 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 in 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.

[0360] 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 with respect 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 with respect 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 with respect to another downlink control signal / channel transmission opportunity among the plurality of downlink control signal / channel transmission opportunities.

[0361] In an example, multiple DCI / PDCCHs may be associated with (or linked to) multiple downlink control signal / channel transmission opportunities. Each downlink control signal / channel of the multiple DCI / PDCCHs may be associated with a corresponding downlink control signal / channel transmission opportunity in the multiple downlink control signal / channel transmission opportunities. The base station may transmit each downlink control signal / channel of the multiple DCI / PDCCHs in / via a corresponding downlink control signal / channel transmission opportunity in the multiple downlink control signal / channel transmission opportunities. The wireless device may monitor, for each downlink control signal / channel in the multiple DCI / PDCCHs, in / via a corresponding downlink control signal / channel transmission opportunity in the multiple downlink control signal / channel transmission opportunities. For example, in Figure 24 to Figure 26 In the embodiment, the 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. The 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.

[0362] The wireless device may receive / detect at least one downlink control signal / channel in a plurality of DCI / PDCCHs (or in a repetition of a downlink control signal / channel). Figure 24 to Figure 26 The wireless device detects / receives DCI 1 in the first downlink control signal / channel transmission opportunity. The wireless device does not receive / detect DCI 2. At least one downlink control signal / channel is DCI 1. The wireless device receives DCI 1 in the first downlink control signal / channel transmission opportunity. The wireless device does not receive / detect DCI 2 in the second downlink control signal / channel transmission opportunity.

[0363] 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, in Figure 24 to Figure 26 In the example, at least one downlink control signal / channel transmission / repetition opportunity is a second downlink control signal / channel transmission opportunity. In the example, each downlink control signal / channel in the at least one downlink control signal / channel and the downlink control signal / channel may be the same.

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

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

[0366] In an example, the wireless device may receive at least one downlink control signal / channel (or downlink control signals / channels) via at least one core set of the one or more core sets. The wireless device may receive each of the at least one downlink control signal / channel via a corresponding core set of the at least one core set. For example, in Figure 24 to Figure 26 In the at least one core set is a first core set.

[0367] The wireless device may determine a reference downlink control signal / channel transmission opportunity 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.

[0368] 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 to Figure 26 In 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.

[0369] 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 to Figure 26 In the embodiment, when the first downlink control signal / channel transmission / repetition opportunity is a reference downlink control signal / channel transmission opportunity, the first downlink control signal / channel (e.g., DCI 1) is a reference downlink control signal / channel. When the second downlink control signal / channel transmission / repetition opportunity is a reference downlink control signal / channel transmission opportunity, the second downlink control signal / channel (e.g., DCI 2) is a reference downlink control signal / channel.

[0370] 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, in Figure 24 to Figure 26, when the downlink control signal / channel transmission start timing is the first downlink control signal / channel transmission timing and the number of repetitions is equal to two, the reference downlink control signal / channel transmission timing may be the second downlink control signal / channel transmission timing. When the downlink control signal / channel transmission start timing is the first downlink control signal / channel transmission timing and the number of repetitions is equal to three, the reference downlink control signal / channel transmission timing may be the third downlink control signal / channel transmission timing among the multiple downlink control signal / channel transmission timings. When the downlink control signal / channel transmission start timing is the second downlink control signal / channel transmission timing and the number of repetitions is equal to two, the reference downlink control signal / channel transmission timing may be the third downlink control signal / channel transmission timing.

[0371] 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 a plurality of downlink control signal / channel transmission opportunities.

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

[0373] The last downlink control signal / channel transmission opportunity may, for example, have the latest start time among the start times of the plurality of downlink control signal / channel transmission opportunities. The second time unit may start later in time than the first time unit. The first / starting symbol of the second time unit may appear after (or later than) the first / starting symbol of the second time unit in time. 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 in time than the first time unit.

[0374] The last downlink control signal / channel transmission opportunity may, for example, have the latest end time among the end times of the multiple downlink control signal / channel transmission opportunities. The second time unit may end later in time than the first time unit. The last symbol of the second time unit may appear after (or later than) the last symbol of the first time unit in time. 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 in time than the first time unit.

[0375] The last downlink control signal / channel transmission opportunity may be associated with the last downlink control signal / channel in a 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.

[0376] For example, in Figure 24 to Figure 26 In the embodiment, 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.

[0377] In an example, the reference downlink control signal / channel transmission timing may be the earliest (or first or starting) downlink control signal / channel transmission timing among a plurality of downlink control signal / channel transmission timings.

[0378] The earliest (or first or start) 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 / start symbol of the first time unit may appear before (or earlier than) the first / start symbol of the second time unit in time. 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.

[0379] 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 in time than the second time unit. The last symbol of the first time unit may appear before the last symbol of the second time unit in time (or earlier than the last 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 ends earlier than the second time unit.

[0380] 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 in / via 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 in 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.

[0381] For example, in Figure 24 to Figure 26 , 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.

[0382] In an example, a reference downlink control signal / channel transmission opportunity may be associated with a core set in one or more core sets. The wireless device may monitor the core set in the reference downlink control signal / channel transmission opportunity for the downlink control signal / channel. The wireless device may monitor the core set in the reference downlink control signal / channel transmission opportunity for the DCI (or downlink control signal / channel). One or more configuration parameters may indicate a 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.

[0383] In an example, a core set may be identified / indicated by a core set index in one or more core set indexes. In an example, the core set index may be the lowest (or highest) of the one or more core set indexes. A core set may be identified / indicated by the lowest (or highest) core set index in one or more core set indexes.

[0384] The wireless device may determine / select a core set having the lowest (or highest) core set index among one or more core set indexes of one or more core sets. For example, the wireless device may monitor a core set in a downlink control signal / channel transmission opportunity among multiple 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 a core set in one or more downlink control signal / channel transmission opportunities among multiple downlink control signal / channel transmission opportunities for DCI. The last / latest / earliest / first / starting downlink control signal / channel transmission opportunity among one or more downlink control signal / channel transmission opportunities may be a reference downlink control signal / channel transmission opportunity. The wireless device may determine a reference downlink control signal / channel transmission opportunity based on the core set.

[0385] The reference downlink control signal / channel transmission opportunity may be associated with a reference downlink control signal / channel in a plurality of 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 for the reference downlink control signal / channel in / via the reference downlink control signal / channel transmission opportunity. The wireless device may monitor for the core set in the reference downlink control signal / channel transmission opportunity.

[0386] In an example, the wireless device may monitor a search space set in a plurality of search space sets in a reference downlink control signal / channel transmission opportunity (e.g., a PDCCH monitoring opportunity) for a downlink control signal / channel. 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 in a reference downlink control signal / channel transmission opportunity for a DCI (or downlink control signal / channel). 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.

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

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

[0389] The reference downlink control signal / channel transmission opportunity may be associated with a reference downlink control signal / channel in a plurality of 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 for the reference downlink control signal / channel in / via the reference downlink control signal / channel transmission opportunity. The wireless device may monitor the search space in the reference downlink control signal / channel transmission opportunity for the reference downlink control signal / channel.

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

[0391] The wireless device may determine the reference downlink control signal / channel transmission opportunity based on a repetition scheme that is a first repetition scheme. For example, the first repetition scheme may be a time domain repetition scheme (eg, TDM).

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

[0393] The wireless device may determine the reference downlink control signal / channel transmission timing based on a repetition scheme that is not 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 space / code domain repetition scheme (e.g., SFN, SDM).

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

[0395] At least one downlink control signal / channel (or downlink control signals / channels) may schedule / trigger one or more sidelink transmissions (e.g., Fig.24 Each of the at least one downlink control signal / channel may schedule / trigger one or more sidelink transmissions. The at least one downlink control signal / channel that schedules / trigger one or more sidelink transmissions may include a downlink control signal / channel that schedules / trigger one or more sidelink transmissions.

[0396] For example, the one or more sidelink transmissions may be one or more physical sidelink shared channel (PSSCH) transmissions. For example, the one or more sidelink transmissions may be transmissions of one or more transport blocks (e.g., PSSCH, PSCCH). For example, the one or more sidelink transmissions may be transmissions of one or more physical sidelink control channels (PSCCH).

[0397] In an example, the wireless device may determine a reference downlink control signal / channel transmission opportunity for reception / transmission of one or more sidelink transmissions.

[0398] In an example, the wireless device may determine a reference downlink control signal / channel transmission opportunity for reception / transmission of a first / start...

Claims

1. A method, comprising: Determining, by the wireless device, a first uplink resource for transmitting a first hybrid automatic repeat request acknowledgement (HARQ-ACK) in a first time slot; receiving at least one repetition of downlink control information (DCI) via a monitoring opportunity in a plurality of monitoring opportunities, the DCI indicating a second uplink resource for transmitting a second HARQ-ACK in the first time slot; and The second HARQ-ACK is transmitted via uplink resources in a second time slot following the first time slot, wherein: An end time of a first monitoring opportunity of the plurality of monitoring opportunities is earlier than a duration before a start symbol of the first uplink resource starts; An end time of a second monitoring occasion of the plurality of monitoring occasions is later than the duration; and The duration is determined for HARQ-ACK multiplexing.

2. The method according to claim 1 also includes multiplexing the second HARQ-ACK in the uplink resource.

3. The method according to claim 1, wherein: The monitoring opportunity is the first monitoring opportunity.

4. The method according to claim 1, wherein: The uplink resource is the first uplink resource.

5. The method of claim 4, further comprising not transmitting the second HARQ-ACK via the second uplink resource.

6. The method according to claim 1, wherein: The first monitoring opportunity has an earliest end time among the start times of the plurality of monitoring opportunities, and the second monitoring opportunity has a latest end time among the end times of the plurality of monitoring opportunities.

7. The method according to claim 1, wherein: The first uplink resource is a first physical uplink control channel (PUCCH) resource; and The second uplink resource is a second PUCCH resource. 8 . The method according to claim 1 , further comprising monitoring a plurality of control resource sets coresets in the monitoring opportunity for repetition of the DCI, wherein each coreset of the plurality of coresets is monitored in a corresponding monitoring opportunity of the plurality of monitoring opportunities.

9. The method of claim 1, wherein the duration is based on at least one of: a first subcarrier spacing of a first active downlink bandwidth part BWP used by the wireless device to receive the first DCI; a second subcarrier spacing of at least one repeated second active downlink BWP used by the wireless device to receive a second DCI; and A third subcarrier spacing of a third active uplink BWP used by the wireless device to transmit the first HARQ-ACK and the second HARQ-ACK.

10. A method comprising: Transmitting, by a base station, first downlink control information DCI to a wireless device, wherein the first DCI indicates a first uplink resource for transmitting a first hybrid automatic repeat request acknowledgement HARQ-ACK in a first time slot; transmitting, via a plurality of monitoring occasions, repetitions of a second DCI indicating a second uplink resource for transmitting a second HARQ-ACK in the first time slot; and receiving the first HARQ-ACK via uplink resources in a second time slot following the first time slot, wherein: An end time of a first monitoring opportunity of the plurality of monitoring opportunities is earlier than a duration before a start symbol of the first uplink resource starts; An end time of a second monitoring occasion of the plurality of monitoring occasions is later than the duration; and The duration is determined for HARQ-ACK multiplexing.

11. The method according to claim 10, wherein: The uplink resource is the first uplink resource.

12. The method according to claim 10, wherein: The first monitoring opportunity has an earliest end time among the start times of the plurality of monitoring opportunities, and the second monitoring opportunity has a latest end time among the end times of the plurality of monitoring opportunities.

13. The method of claim 10, wherein: The first uplink resource is a first physical uplink control channel (PUCCH) resource; and The second uplink resource is a second PUCCH resource.

14. An apparatus comprising: one or more processors; and A memory storing instructions which, when executed by the one or more processors, cause the apparatus to perform a method as claimed in any one of claims 1 to 13.

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