Method for power control adjustment of pucch with multiple pdsch scheduling

Abstract

A wireless device can receive configuration parameters for each of one or more cells indicating a maximum number of time domain resource allocations for a physical downlink shared channel (PDSCH) for each respective cell. The wireless device can further transmit feedback information over a physical uplink control channel (PUCCH). The wireless device can transmit the feedback information across the one or more cells using a transmission power determined based on a maximum of the maximum number of time domain resource allocations for the cells, scaled by a corresponding number of code words for the cell.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 230,408, filed August 6, 2021, the entire contents of which are incorporated herein by reference. Attached Figure Description

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0024] FIG. 17 An example is shown of HARQ feedback timing determination according to some embodiments.

[0025] FIG. 18 An example is shown of DAI indication for DCI with a single serving cell according to some embodiments.

[0026] FIG. 19 An example is shown of HARQ feedback / codebook determination for a wireless device configured with multiple serving cells according to some embodiments.

[0027] FIG. 20 An example is shown of HARQ-ACK transmission associated with DCI scheduling multiple PDSCHs according to some embodiments.

[0028] FIG. 21An example of DAI counting per DCI for multi-PDSCH scheduling is shown, according to some embodiments.

[0029] FIG. 22 An example of DAI counting per PDSCH for multi-PDSCH scheduling is shown, according to some embodiments.

[0030] FIG. 23A and FIG. 23B An example of determining counter DAI and total DAI values based on corresponding DCI indication is shown, according to some embodiments.

[0031] FIG. 24 An example DAI counting procedure is shown, according to some embodiments.

[0032] FIG. 25 An example DAI counting procedure is shown, according to some embodiments.

[0033] FIG. 26 An example of DAI counting in a single serving cell is shown, according to some embodiments.

[0034] FIG. 27 An example of generating HARQ-ACK information corresponding to multi-PDSCH scheduling DCI is shown, according to some embodiments. DETAILED DESCRIPTION

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

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

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

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

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

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

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

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

[0043] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is herein defined as an element that performs a defined function and has a defined interface to other elements. The modules described in the present disclosure can be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with a biological element) or combinations thereof, all of which are behaviorally equivalent. For example, a module can be implemented as a software routine in a computer language (e.g., C, C++, Fortran, Pascal, Java, Basic, Matlab, etc.) that is configured to execute on a hardware machine (e.g., a computer, a microprocessor, an embedded system, etc.). A module can also be implemented in firmware, such as a Verilog module, VHDL module, C code, etc. that is configured to execute on a hardware platform (e.g., a programmable logic array, etc.). It is possible to use physical hardware incorporating discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++, etc. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDLs), such as VHDL or Verilog, which configure the connections between less functional internal hardware modules. The mentioned technologies are often used in combination to implement the results of functional modules.

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

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

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

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

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

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

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

[0051] The RAN 104 can be deployed as a homogeneous network of macro cell base stations, each having similar antenna patterns and antenna gains, and / or as a heterogeneous network, including different types of base stations, e.g., macro cells, micro cells, femto cells, etc., which can have different antenna patterns, different antenna gains, and / or different coverage areas. The RAN 104 can be deployed, for example, using a centralized, distributed, and / or co-deployed RAN architecture.

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

[0053] FIG. 1B Another example mobile communication network 150 is shown in which embodiments of the disclosure can be implemented. The mobile communication network 150 can be, for example, a PLMN run by a network operator. As FIG. 1B 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, UEs 156). These components can be implemented and operate in a similar manner as described above with regard to the corresponding components of the mobile communication network 100. FIG. 1A These components can be implemented and operate in a similar manner as described above with regard to the corresponding components of the mobile communication network 100.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0095] - The Physical Uplink Control Channel (PUCCH), which carries the UCI, including HARQ acknowledgments, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0187] Msg A 1331 can be transmitted by the UE in uplink transmission. Msg A 1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include... FIG. 13A The content shown in Msg3 1313 is similar to and / or equivalent to that of Msg3 1313. Transport block 1342 may include UCIs (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 content similar to and / or equivalent to Msg3 1313. FIG. 13A and FIG. 13B The Msg 2 1312 shown (e.g., RAR) and / or FIG. 13A The content shown in Msg 4 1314 is similar to and / or equivalent to the content shown in Msg 4 1314.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0220] The Hybrid ARQ (Hybrid Automatic Repeat Request) mechanism in the MAC layer aims for very fast transmission. The radio device can provide feedback to the base station for each scheduled / candidate transport block regarding the success (e.g., ACK) or failure (e.g., NACK) of a downlink transmission (e.g., PDSCH). A HARQ-ACK bit value of 0 indicates a negative acknowledgment (NACK), while a HARQ-ACK bit value of 1 indicates a positive acknowledgment (ACK).

[0221] A very low error rate probability may be achieved with HARQ feedback, potentially at the expense of transmission resources (e.g., power). For example, a feedback error rate of 0.1–1% might be reasonable, which could result in a HARQ residual error rate of similar magnitude. In many cases, this residual error rate may be sufficiently low. In some services requiring ultra-reliable data delivery with low latency (e.g., URLLC), such a residual error rate may be intolerable. In such cases, the feedback error rate can be reduced, and the increased cost of feedback signaling can be accepted, and / or additional retransmissions can be performed without relying on feedback signaling, resulting in reduced spectral efficiency.

[0222] HARQ protocols are a primary method for handling retransmissions in wireless technologies such as NR. Retransmissions may be necessary in the case of erroneously received packets. Although it's impossible to decode the packet, the received signal may still contain information that could be lost due to the discarding of the erroneously received packet. HARQ protocols with soft combination address this drawback. In HARQ with soft combination, the wireless device can store erroneously received packets in a buffer and later combine the received packets with one or more retransmissions to obtain a single combined packet / transmission block that is more reliable than its individual components. Decoding of the error-correcting codes operates on the combined signal. Retransmission of the code block groups (CBGs) that form the transmission block can be handled by the physical layer and / or the MAC layer.

[0223] HARQ mechanisms typically consist of multiple stop-and-wait protocols, each operating on a single transport block. In a stop-and-wait protocol, the transmitter stops and waits for an acknowledgment after each transmitted transport block. This protocol requires a single bit indicating a positive or negative acknowledgment for the transport block; however, throughput is low due to the wait after each transmission. Multiple stop-and-wait processes can operate in parallel; for example, while waiting for an acknowledgment from one HARQ process, the transmitter can transmit data from another HARQ process. These multiple parallel HARQ processes can form a HARQ entity, allowing for continuous data transmission. A wireless device can have one HARQ entity per carrier. HARQ entities can support more than four layers to a single device spatial multiplexing in the downlink, where two transport blocks can be transmitted in parallel on the same transport channel. A HARQ entity can have two sets of HARQ processes with independent HARQ acknowledgments.

[0224] Wireless technologies can use asynchronous HARQ protocols in the downlink and / or uplink. For example, the HARQ process involved in downlink and / or uplink transmissions can be explicitly and / or implicitly signaled. For instance, downlink control information (DCI) scheduling downlink transmissions can be signaled to the corresponding HARQ process. Asynchronous HARQ operation can allow dynamic TDD operation and may be more efficient when operating in unlicensed spectrum, where the availability of radio resources scheduled for synchronous retransmission may not be guaranteed.

[0225] Before encoding, a large transport block size can be segmented into multiple code blocks, each with its own CRC in addition to the total TB CRC. Errors on individual code blocks can be detected based on their CRCs and the total TB. The base station can configure retransmissions for the radio device based on the group of code blocks (e.g., a code block group (CBG)). If retransmissions for each CBG are configured, feedback is provided for each CBG. A TB can include one or more CBGs. The CBG to which a code block belongs can be determined based on the initial transmission and can be fixed.

[0226] In the downlink, retransmissions can be scheduled in the same manner as new data. For example, retransmissions can be scheduled at any time and at any frequency location within the downlink cell and / or the cell's active downlink BWP. Downlink scheduling assignments may include: necessary HARQ-related control signaling, such as the HARQ process number; a New Data Indicator (NDI); a CBG Transmission Indicator (CBGTI) and a CBG Refresh Indicator (CBGFI) if CBG retransmission is configured; and / or information for scheduling acknowledgment (ACK / NACK) transmissions in the uplink (e.g., PUCCH), such as timing and resource indication information.

[0227] Once a downlink scheduling assignment is received in the DCI, the wireless device attempts to decode the TB, for example, after a soft combination with a previous attempt / reception of the TB. Transmissions and retransmissions can be scheduled within the same framework. The wireless device can determine whether a transmission is a new transmission or a retransmission based on the NDI field in the DCI. Explicit NDIs can be included for the scheduled TB as part of the scheduling information in the downlink. The NDI field can include one or more NDI bits for each TB (and / or CBG). NDI bits can be switched for new transmissions but not for retransmissions. In the case of a new transmission, the wireless device refreshes the soft buffer corresponding to the new transmission before receiving / storing it. In the case of a retransmission, the wireless device can soft-combine the received data with the data stored in the soft buffer based on the downlink scheduling assignment for use in the corresponding HARQ process.

[0228] The time slot / interval / offset (e.g., K1) from downlink data reception / resources to the transmission of the corresponding HARQ ACK / NACK can be fixed, such as multiple subframes / slots / symbols (e.g., three milliseconds, four slots). This scheme with predefined timing for ACK / NACK may not integrate well with dynamic TDD and / or unlicensed operations. A more flexible scheme that can dynamically control the timing of ACK / NACK transmission can be adopted. For example, the DL scheduling DCI can include a PDSCH-to-HARQ_feedback timing field to control / indicate the transmission timing of ACK / NACK corresponding to data scheduled by the DL scheduling DCI in uplink transmissions (e.g., PUCCH). The PDSCH-to-HARQ_feedback timing field in the DCI can be used as an index in one or more indices of the K1 value in a predefined and / or RRC configuration table (e.g., a HARQ timing table). The K1 value can provide information about the gap / interval / offset between the second time of HARQ ACK / NACK transmission and the first time of data reception (e.g., the Physical DL Shared Channel (PDSCH)).

[0229] FIG. 18 An example of HARQ feedback timing determination according to some implementation schemes is shown. In this example, three DCIs scheduled for three downlink assignments in the same time slot are received in time slots S0, S1, and S3. In each downlink assignment, a different HARQ feedback timing index is indicated, for example, in S0:3, in S1:2, and in S3:0. The indicated index (PDSCH-to-HARQ_feedback timing field) points to the HARQ timing table, for example, for S0:T3, indicating that uplink ACK / NACK transmissions point to S4; for S1:T2, indicating that uplink ACK / NACK transmissions point to S4; and for S3:T0, indicating that uplink ACK / NACK transmissions point to S4. As a result, all three downlink assignments are acknowledged in the same time slot S4. The radio device multiplexes these three acknowledgments and transmits them in time slot S4.

[0230] Wireless devices can support baseline processing time / capacity. Some wireless devices can support additional, aggressive / faster processing time / capacity. Wireless devices can report processing capacity to the base station, for example, per subcarrier interval.

[0231] Wireless devices can determine the resources used for HARQ ACK / NACK transmissions, such as frequency resources and / or PUCCH format and / or code fields, based on the location of the scheduled PDCCH (e.g., the Start Control Channel Element (CCE) index). The scheduled PDCCH / DCI may include fields indicating the frequency resources used for uplink transmissions of HARQ ACK / NACK transmissions, such as the PUCCH Resource Indicator (PRI) field. For example, the PRI field may be an index selecting one of several predefined and / or RRC-configured PUCCH resource sets.

[0232] For example, in carrier aggregation scenarios and / or when retransmission by CBG is configured, the radio device can multiplex multiple HARQ feedback bits scheduled for uplink transmission at the same time / slot. The radio device can multiplex multiple ACK / NACK bits from multiple TBs and / or CBGs into a single multi-bit HARQ feedback message / codebook. Multiple ACK / NACK bits can be multiplexed based on semi-static and / or dynamic codebooks. Through RRC configuration, the base station can configure semi-static or dynamic codebooks for cells configured with PUCCH resources (e.g., primary cell, PUCCH cell).

[0233] A semi-static codebook can be viewed as a matrix comprising a time-domain dimension and component carrier (and / or CBG and / or MIMO layer) dimensions, both of which can be semi-statically configured and / or predefined. The size of the time-domain dimension can be given by predefined HARQ ACK / NACK timings and / or the maximum and / or minimum HARQ ACK / NACK timings indicated in a table configured by RRC. The size of the component carrier domain can be given by the number of simultaneous TBs and / or CBGs across all component carriers. The codebook size can be determined based on the time-domain and component carrier dimensions for the semi-static codebook, regardless of the actual scheduled transport blocks / PDSCH. The number of bits to be transmitted in the HARQ feedback / report is determined based on one or more RRC configuration parameters. The appropriate format (e.g., PUCCH format) for uplink control signaling can be selected based on the codebook size (e.g., the number of HARQ ACK / NACK bits). Each entry in the matrix can represent the decoding result of the corresponding transmission, e.g., an affirmative (ACK) or negative (NACK) acknowledgment. One or more entries in the codebook matrix may not correspond to a downlink transmission opportunity that reports a NACK (e.g., a PDSCH timing). For example, this can increase codebook robustness in the event of a lost downlink assignment, and the base station can schedule retransmissions of lost TB / CBGs. The size of a semi-static codebook can be very large.

[0234] Dynamic codebooks can be used to address the potential large size issue of semi-static codebooks. With a dynamic codebook, only (including one or more semi-persistent schedules) scheduled assignments' ACK / NACK information can be included in the report, e.g., not for all carriers as in a semi-static codebook. The size of the dynamic codebook can vary dynamically, for example, as a function of the number of scheduled carriers and / or as a function of the number of scheduled transport blocks. To maintain a consistent understanding of the dynamic codebook size (which is prone to errors in downlink control signaling), a downlink assignment index (DAI) can be included in the scheduling DCI. The DAI field can include a counter DAI (cDAI) and a total DAI (tDAI), for example, in the case of carrier aggregation. The counter DAI in the scheduling DCI indicates the number of scheduled downlink transmissions (PDSCH receive / SPS PDSCH release) up to the point where the DCI is received, first as an index for the carrier, then as an index for the PDCCH monitoring timing. The total DAI in the scheduling DCI indicates the total number of scheduled downlink transmissions across all carriers up to the point where the DCI is received. The highest cDAI at the current time is equal to the tDAI at that time.

[0235] In the example, the wireless device may be configured with a dynamic HARQ feedback mode or HARQ-ACK codebook determination. Based on the dynamic HARQ feedback mode, the wireless device may multiplex one or more HARQ-ACK feedback bits based on a PDSCH scheduled in a DCI format that does not include / includes the counter DAI field. In the example, the wireless device may determine the monitoring timing of the DCI for receiving a PDCCH with one or more DCI formats released via the active downlink BWP of the serving cell, which is scheduled to receive a PDSCH or SPS PDSCH. The wireless device may determine one or more HARQ-ACK / HARQ feedback bits in the same PUCCH in slot n based on (1) the value of the HARQ feedback timing indicator field of the PDSCH in the DCI format of the scheduled PDSCH reception or SPS PDSCH release; and (2) the slot offset or timing offset (e.g., K0) between the PDCCH / DCI and PDSCH provided by time-domain resource assignment in the DCI format of the scheduled PDSCH or SPS PDSCH release; and (3) the aggregation of multiple slots released by the PDSCH or SPS PDSCH.

[0236] For example, a wireless device can determine a set of PDCCH monitoring opportunities for one or more DCI formats that schedule PDSCH reception or SPS PDSCH release. PDCCH monitoring opportunities can be monitoring opportunities within a time slot, hourly slot, subframe, frame, or span. The set of PDCCH monitoring opportunities may include one or more monitoring opportunities within one or more search spaces of the active DL BWP of the configured serving cell. The one or more monitoring opportunities can be indexed in ascending order of the start time associated with the PDCCH monitoring opportunity or the search space that determines the opportunity. The cardinality of the set of PDCCH monitoring opportunities can be defined as the total number M of the one or more monitoring opportunities. The value of the counter DAI field in one or more DCI formats can represent the cumulative number of PDCCH monitoring opportunity {serving cell, PDCCH monitoring opportunity} pairs up to the current time, where PDSCH reception or SPS PDSCH release is associated with one or more DCI formats.

[0237] The base station can update (e.g., increment by 1) the counter DAI value for each PDCCH monitoring time to indicate the cumulative number of PDSCH receptions and / or SPS PDSCH releases up to each PDCCH monitoring time. The wireless device can determine the order of DCIs based on the counter DAI in each PDCCH monitoring time.

[0238] When a radio device can support more than one PDSCH reception per PDCCH monitoring event (e.g., PDSCH-Numerber-perMOperCell greater than 1), the radio device can sort (e.g., list) the start times of one or more PDSCH receptions for the same {serving cell, PDCCH monitoring event}. The radio device can then sort the PDCCH monitoring events or PDSCH receptions based on the serving cell index (e.g., list them sequentially). The radio device can then sort the PDCCH monitoring event index (based on the start time of the PDCCH monitoring event). When ACKNACKFeedbackMode=JointFeedback is provided to the radio device, for the same serving cell, the first core pool index can be sorted before the second core pool index.

[0239] FIG. 18 An example of the DAI indication for a DCI with a single serving cell is shown. In the example, the total DAI value can represent the total number of {service, PDCCH monitoring time} pairs spanning one or more serving cells up to the current PDCCH monitoring time. FIG. 18 Examples of counter DAI (C-DAI or DAI) and / or total DAI (T-DAI) are shown when a wireless device is configured with a single serving cell. For example, the wireless device may determine... FIG. 19The diagram illustrates a first monitoring time (left box), a second monitoring time (middle box), and a third monitoring time (right box). A wireless device can schedule / receive a DCI based on one or more DCI formats via monitoring times (e.g., the first monitoring time, the second monitoring time, and the third monitoring time). For example, a wireless device can receive a first DCI (DCI 1) via the first monitoring time, where the first DCI indicates DAI=0 and / or T-DAI=0. The base station can set DAI=0 and / or T-DAI=0. A wireless device can receive a third DCI (DCI 3) via the third monitoring time, where the third DCI indicates DAI=2 and / or T-DAI=2. The first and third DCIs can indicate the same PUCCH resource for HARQ feedback. The wireless device can generate a first HARQ feedback bit released by the PDSCH or SPS PDSCH scheduled by the first DCI. The wireless device can generate a third HARQ feedback bit released by the second PDSCH or second SPS PDSCH of the third DCI. The wireless device can successfully receive a second DCI without using the second monitoring time. The wireless device can determine a lost (e.g., failed to receive, decoded, not received, or failed) DCI (e.g., the second DCI) based on the DAI value of the third DCI. The wireless device can generate a NACK (e.g., a negative ACK) for a third PDSCH or third SPS PDSCH release. For example, the third PDSCH or third SPS PDSCH release may have been scheduled by the second DCI. The wireless device may not receive the third PDSCH or third SPS PDSCH release because the second DCI has not yet been successfully received.

[0240] exist FIG. 19 In the example, the wireless device can generate 3 HARQ feedback bits, with the first bit corresponding to the first DCI, the second bit to the second DCI, and the third bit to the third DCI. The wireless device can determine the number of bits in the HARQ feedback / HARQ-ACK codebook based on the T-DAI or C-DAI of the most recent DCI for the PUCCH (or PUCCH resource). The wireless device can transmit the HARQ feedback bits via the PUCCH or PUCCH resource. The wireless device can determine the first HARQ-ACK bit for the PDSCH scheduled by the first DCI or the first DCI (e.g., DCI1) in the HARQ-ACK codebook. When the wireless device loses the second DCI, it can determine a NACK for the second HARQ-ACK bit. The wireless device can determine the third HARQ-ACK bit for the third DCI (e.g., DAI = 2).

[0241] FIG. 19An example of HARQ feedback / codebook determination for a radio device configured with multiple serving cells is shown according to some implementation schemes. For example, the radio device may be configured with a first cell (cell 0) and a second cell (cell 1). For example, the radio device may receive a first DCI via the first cell (DCI 1), which may indicate DAI = 0 and T-DAI = 1. The base station may determine the C-DAI (or DAI) and / or T-DAI for the DCI. The T-DAI may indicate the total number of PDCCH monitoring times across all serving cells up to the current PDCCH monitoring time and / or the number of DCIs. The first monitoring time of the first cell may overlap with the first monitoring time of the second cell and may have the same start time. The base station may set the T-DAI of the first DCI to two. The base station may set the T-DAI of the second DCI (DCI 2) via the second cell. The DAI value of the second DCI may be set to 1 (e.g., a counter DAI). For example, the base station may set the DAI value of the second DCI to 1. The wireless device may fail to receive a third DCI (DCI3) that indicates T-DAI=2 and DAI=2. The wireless device may receive a fourth DCI (DCI4) that indicates T-DAI=3 and DAI=3. The wireless device may receive a fifth DCI (DCI5) that indicates T-DAI=4 and DAI=4.

[0242] When the T-DAI value reaches its maximum value (e.g., n) or a threshold (e.g., based on 2 bits of the C-DAI / T-DAI field, maximum = 4, maximum = 2^K or 2^K-1, where K is the number of bits used for the C-DAI or T-DAI field in the DCI format), the T-DAI value can be wrapped back (e.g., modulo operation, such as modulo n, which can be represented as mode n or % n). The wireless device can determine the HARQ-ACK bit as follows. For example, based on the wrap-back mechanism, for the fifth DCI, the actual values ​​of T-DAI and C-DAI can be 0 (e.g., when n is 4, 4mod 4 = 0, 4%4 = 0, the actual value can be determined based on modulo n, where n is 2^K, and K bits are used for the DAI field).

[0243] For example, for each PDCCH monitoring opportunity (e.g., a first PDCCH monitoring opportunity is the first time when the radio device can monitor a first monitoring opportunity via a first cell and a second monitoring opportunity via a second cell), the radio device can determine the number of HARQ-ACK feedback bits for each serving cell based on the cell index (e.g., determine the first cell, and then determine the second cell when the index of the first cell is lower than the index of the second cell). For example, the PDCCH monitoring opportunity can indicate the start time in a time slot in which the radio device can begin monitoring one or more PDCCH candidates via the monitoring opportunity of the serving cell. For example, the PDCCH monitoring opportunity can indicate a monitoring opportunity determined / configured based on a search space configuration.

[0244] For example, a radio device can determine the number of HARQ-ACK bits for the serving cell based on the DAI field of each PDCCH monitoring time. For example, the radio device can determine the bit index in the HARQ-ACK bits to place the ACK or NACK released by the DCI for the serving cell's transport block or SPS PDSCH, where the radio device can receive the DCI via each PDCCH monitoring time. The radio device can determine the first HARQ-ACK bit of a transport block for a first cell at the first PDCCH monitoring time. The radio device can determine the second HARQ-ACK bit of a transport block for a second cell at the first PDCCH monitoring time. The radio device can move to the next PDCCH monitoring time, which occurs after the first monitoring time but before other monitoring times.

[0245] exist FIG. 19 In this process, the radio device can determine the second monitoring opportunity via the first cell because it can detect any DCI without using the second monitoring opportunity via the second cell. The radio device can determine the third HARQ ACK bit corresponding to the release of a PDSCH or SPS PDSCH scheduled via the fourth DCI (DCI 4). The radio device can move to the next PDCCH monitoring opportunity, where it receives a DCI with a DAI value. For example, the radio device can determine the third monitoring opportunity via the second cell as the next PDCCH monitoring opportunity. The radio device can determine the fourth HARQ ACK bit corresponding to a PDSCH or SPS PDSCH scheduled by the fifth DCI (DCI 5). The radio device can determine the total DAI value for a PUCCH resource based on the last DCI received for that PUCCH resource. For example, the fifth DCI could be the radio device's last DCI received for that PUCCH resource. FIG. 20 The last DCI received by the PUCCH resource. The fifth DCI indicator T-DAI=4 indicates that five DCIs have been scheduled up to the current PDCCH monitoring time.

[0246] The wireless device can determine the number of HARQ-ACK bits based on the T-DAI of the last DCI. The wireless device can determine the order (e.g., bit order) of each DCI or PDSCH scheduled by each DCI based on the C-DAI value of each DCI. For example, if the bit order of the fourth DCI (DCI 4) is 3, the wireless device can place the HARQ-ACK bits for the fourth DCI in the bit with index 3, such as... FIG. 20 As shown in the diagram, the wireless device can determine the NACK for a missed DCI between the second and fourth DCIs. The wireless device can generate aggregated HARQ-ACK feedback for each PDCCH monitoring event based on the ascending order of the start time of the PDCCH monitoring events (e.g., first DCI, second DCI → (third DCI) → fourth DCI → fifth DCI), and for each PDCCH monitoring event based on a cell index (e.g., first cell → second cell in the first monitoring event). The wireless device can determine the bit order of the HARQ-ACK feedback for one or more DCIs / PDSCHs based on the C-DAI / T-DAI values ​​of one or more DCIs.

[0247] The wireless device can determine a bitmap of ACK-NACK information. The bitmap of ACK-NACK information may include a HARQ-ACK codebook, where the HARQ-ACK codebook may include one or more HARQ-ACK sub-codebooks. For example, the wireless device can generate a first bitmap for a first HARQ-ACK sub-codebook. The wireless device can generate a second bitmap for a second HARQ-ACK sub-codebook. The PUCCH may include a HARQ-ACK codebook, which includes one or more HARQ-ACK sub-codebooks.

[0248] For example, a wireless device can perform encoding based on a HARQ-ACK codebook. When the HARQ-ACK codebook includes multiple HARQ-ACK sub-codebooks, the wireless device can append multiple HARQ-ACK sub-codebooks before performing encoding. Example implementations can generate multiple HARQ-ACK sub-codebooks for a single HARQ-ACK codebook. Example implementations can generate multiple HARQ-ACK codebooks, where each of the multiple HARQ-ACK codebooks can correspond to an example HARQ-ACK sub-codebook. In the example, the wireless device can generate a HARQ-ACK codebook that includes one or more HARQ-ACK sub-codebooks. The wireless device can encode the HARQ-ACK codebook and can transmit the encoded bits via PUCCH resources. For example, a first HARQ-ACK sub-codebook (e.g., codebook, sub-codebook, first HARQ-ACK codebook) can correspond to one or more downlink channels (e.g., PDSCH), where each downlink channel carries one or more transport blocks. The second HARQ-ACK subcodebook may correspond to one or more second downlink channels (e.g., PDSCH), where each second downlink channel carries one or more code block groups (CBGs). In the example, the radio device can determine a first C-DAI / T-DAI for the first HARQ-ACK subcodebook. The radio device can determine a second C-DAI / T-DAI for the second HARQ-ACK subcodebook.

[0249] Existing technologies define frequency ranges for wireless operation. For example, NR Rel-15 and Rel-16 define two frequency ranges (FRs): FR1 spans from 410 MHz to 7.125 GHz, and FR2 spans from 24.25 GHz to 52.6 GHz. Recent research has revealed global availability of frequency bands outside the current operating frequency ranges, for example, in the range of 52.6 GHz to 71 GHz. The proximity of higher frequency ranges to FR2 and the impending commercial opportunities for high data rate communications make it imperative for wireless technologies to address operation within this frequency range (e.g., NR operation). For example, 3GPP has decided to extend FR2 operation to 71 GHz to consider both licensed and unlicensed operation, employing one or more new sets of parameters (e.g., larger subcarrier spacing). These high-frequency bands include unlicensed bands (e.g., the unlicensed 60 GHz band). Existing procedures for operating in unlicensed spectrum (e.g., procedures defined by LAA / NR-U) can be used to operate in these high-frequency unlicensed bands. For channel access, both LBT and non-LBT modes can be supported to cover a wide range of use cases and regulatory requirements.

[0250] Supporting larger subcarrier spacings (e.g., 120kHz, 240kHz, 480kHz, and 960kHz) may require enhancing some existing processing timelines; for example, processing capabilities for PUSCHs scheduled under RAR·UL licenses; dynamic SFI and SPS / CG cancellation timing; and SPS response. Timelines for PDSCH release / sleep for HARQ-ACK information; minimum time gaps for wake-up and SCell sleep indications; BWP handover delay; multi-beam operation timing (timeDurationForQCL, beamSwitchTiming, beam switching gap, beamReportTiming, etc.); timelines for multiplexing multiple UCI types; minimum P_switch value for search space set group handover; appropriate configuration of scheduling time offsets, such as k0 (for PDSCH), k1 (for HARQ), k2 (for PUSCH); PDSCH processing time (N1), PUSCH preparation time (N2), HARQ-ACK multiplexing timeline (N3); CSI processing times Z1, Z2, and Z3 and CSI processing units; potential enhancements for CPU utilization calculation; relevant UE capabilities for processing timelines; minimum protection period between two SRS resources for SRS resource sets used for antenna handover.

[0251] Due to the higher processing requirements and significantly shorter slot durations in these high-frequency bands, limitations on PDCCH monitoring can be considered. For example, increased minimum PDCCH monitoring units could be supported to assist UE processing. Temporal scheduling enhancements for PDSCH / PUSCH could be supported, such as increasing the minimum temporal scheduling unit to more than one symbol, scheduling multiple PDSCHs by a single DCI (multi-TTI scheduling), mapping a TB to multiple slots (e.g., TTI bundles), etc. Scheduling each PUSCH and / or PDSCH via a separate DCI could be wasteful of resources, as many signaling parameters may be redundant across the respective DCI. For example, multiple PDSCH / PUSCH (PxSCH) scheduling with a single DCI (using existing or new DCI formats) could be supported to reduce scheduling overhead and the need for PDCCH monitoring in the temporal domain.

[0252] For radio devices and serving cells, scheduling multiple PDSCHs by a single DL DCI and multiple PUSCHs by a single ULDCI can be supported. Each PDSCH / PUSCH can have a single / individual TB. Each PDSCH / PUSCH can be limited to a time slot. A maximum of M PDSCHs or PUSCHs (e.g., M = 8, 16, or 32) can be scheduled using a single DCI. For multi-PUSCH / PDSCH scheduling, a TDRA table can be configured such that each row indicates up to X PUSCHs / PDSCHs, which can be consecutive and / or discontinuous in the time domain. Each PUSCH / PDSCH can have a separate SLIV and mapping type. The number (X) of PUSCHs / PDSCHs to be scheduled can be signaled by the number of valid SLIVs indicated in the rows of the TDRA table signaled in the DCI, such that the maximum number of PUSCHs / PDSCHs that the DCI can schedule can be determined based on the row in the TDRA table indicating the maximum number of (valid) SLIVs. The TDRA table can be configured such that each row indicates up to X (e.g., 8) PUSCH / PDSCH groups. PUSCH / PDSCH groups can be non-contiguous. Each PUSCH / PDSCH group can have a separate SLIV, mapping type, and / or time slot or number of PUSCH / PDSCHs (N). Within each group, N PUSCH / PDSCHs can occupy the same OFDM symbol indicated by the SLIV and mapping type. The number of scheduled PUSCH / PDSCHs can be the sum of the number of PUSCH / PDSCHs in all PUSCH / PDSCH groups in the rows of the TDRA table signaled in the DCI (e.g., 1 to M).

[0253] For multi-PUSCH / PDSCH scheduling, CBG (re)transmission may or may not be supported. For multiple scheduled PUSCH / PDSCHs, Ultra-Reliable Low-Latency Communication (URLLC) related fields, such as priority indicators and / or open-loop power control parameter sets, can be indicated in the DCI. For multiple PUSCH / PDSCHs scheduled by a single DCI, NDI and / or RV can be signaled for each PUSCH / PDSCH. The number of NDI bits and / or RV bits in the DCI can be determined based on the configured TDRA table. The HARQ process ID signaled in the DCI can be applied to the first scheduled PUSCH / PDSCH among the multiple PUSCH / PDSCHs scheduled by the DCI. For subsequent PUSCH / PDSCHs in the scheduling order, the HARQ process ID can be incremented by 1 (modulo operation as needed). The same FDRA and / or MCS values ​​indicated by the DCI can be applied to all scheduled PUSCH / PDSCHs.

[0254] For a DCI that schedules multiple PDSCHs, the slot offset k0 (indicated by the TDRA field in the DCI) can indicate the gap between the slot scheduling the DCI (e.g., the PDCCH receive slot) and the first slot among the multiple slots of the PDSCHs scheduled by the DCI. For example, k0 can indicate the slot offset between the DCI and the earliest PDSCH scheduled by the DCI.

[0255] For multi-PDSCH scheduling, multiple HARQ-ACKs corresponding to the multiple PDSCHs can be fed back. For DCI scheduling multiple PDSCHs, the HARQ-ACK information corresponding to the PDSCH scheduled by the DCI can be multiplexed in a single PUCCH in the first time slot. The first time slot can be determined based on a first offset K1. The first offset can be indicated by the DCI, for example, by the PDSCH-to-HARQ_feedback timing indicator field in the DCI. The first offset can be indicated by RRC signaling, for example, if the PDSCH-to-HARQ_feedback timing indicator field does not exist in the DCI, then the first offset is provided by dl-DataToUL-ACK. The first offset (K1) can indicate the time slot offset between the time slot of the last PDSCH scheduled by the DCI and the time slot carrying the HARQ-ACK information corresponding to the scheduled PDSCH.

[0256] FIG. 21 An example of HARQ-ACK transmission associated with a DCI that schedules multiple PDSCHs, according to some implementation schemes, is shown. FIG. 21 As shown, the DCI indicates the k0 and k1 time slot offsets. The wireless device determines the first time slot associated with the first PDSCH (PDSCH 1) among multiple scheduled PDSCHs by applying the k0 time slot offset to the time slot receiving the DCI. The wireless device determines the number of scheduled PDSCHs based on the DCI (e.g., the TDRA field in the DCI). In this figure, the wireless device determines four PDSCHs scheduled by the DCI. Multiple PDSCHs can be scheduled in one or more time slots starting from the first time slot indicated by the k0 time slot offset. Multiple PDSCHs can be in consecutive time slots. Multiple PDSCHs can be consecutive and / or non-consecutive, for example, non-zero gaps may or may not be between adjacent PDSCHs scheduled by the DCI. The wireless device can determine the second time slot for HARQ-ACK transmission of multiple PDSCHs via the PUCCH based on the k1 time slot offset. The wireless device can apply the k1 time slot offset to the time slot of the last scheduled PDSCH (PDSCH 4) to determine the second time slot. The wireless device can transmit HARQ-ACK information associated with all scheduled PDSCHs via PUCCH resources in the second time slot.

[0257] The PDSCH processing time can be considered. For example, the first symbol of a PUCCH that includes HARQ-ACK information for PDSCH scheduled by the DCI may not begin earlier than the start of a time slot after the last symbol of the PDSCH received associated with the HARQ-ACK information (e.g., the last PDSCH). This time slot can be provided by the UE PDSCH processing capability in the corresponding frequency band.

[0258] The UE can be configured with multiple PDSCH scheduling and a Type 2 (dynamic) HARQ-ACK codebook. The UE can generate a Type 2 HARQ-ACK codebook corresponding to a DCI that can schedule multiple PDSCHs. A DCI that schedules multiple PDSCHs may include a counter DAI and / or a total DAI field. In the first example, the counter DAI and / or total DAI can be counted for each DCI (also referred to as Alt 1). For example, the RRC configuration may include at least one parameter indicating that the counter DAI and / or total DAI are counted for each DCI.

[0259] For example, if multiple PDSCH scheduling is configured for at least one serving cell in a PUCCH cell group and / or a DAI count and / or an RRC indication for a first value of a first parameter are configured for each DCI, then for the PUCCH cell group, a Type 2 HARQ-ACK codebook may include two (or more) sub-codebooks. For example, the UE may generate a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook.

[0260] The first HARQ-ACK subcodebook may include HARQ-ACK information for one or more DCIs that each schedule a single PDSCH, or corresponding to those DCIs. For example, one or more DCIs may be configured with a TDRA table containing rows each having a single SLIV (e.g., an RRC configuration indicating single PDSCH scheduling for a DCI format). Alternatively, one or more DCIs may be configured with a TDRA table containing at least one row with multiple (valid) SLIVs (e.g., an RRC configuration indicating multiple PDSCH scheduling for a DCI format), and each of the one or more DCIs may schedule (e.g., via the TDRA field in one or more DCIs) a single PDSCH. One or more DCIs may not be configured with CBG-based scheduling.

[0261] The second HARQ-ACK subcodebook may include HARQ-ACK information corresponding to one or more DCIs (e.g., multi-PDSCH scheduling DCIs) that each schedule multiple PDSCHs. For example, one or more DCIs may be configured with a TDRA table via RRC configuration parameters, the TDRA table including at least one row with multiple (valid) SLIVs. Each of the one or more DCIs may include a TDRA field indicating that multiple PDSCHs are scheduled.

[0262] The UE can generate a fixed number of HARQ-ACK bits corresponding to each of one or more DCIs in the second HARQ-ACK sub-codebook, for example, to align the size of the HARQ-ACK feedback corresponding to different DCIs, such that if a DCI is lost, the UE and BS have mutual knowledge of the HARQ-ACK codebook based on this alignment. For example, the number of HARQ-ACK bits corresponding to each DAI in the second sub-codebook (for multi-PDSCH scheduling DCIs) can depend on a first quantity. For example, the first quantity can be a configured quantity. For example, the first quantity can be the maximum configured number of multi-PDSCH scheduling DCIs across serving cells belonging to the same PUCCH cell group (M) / the schedulable PDSCHs for that multi-PDSCH scheduling DCI. For example, the TDRA table of the RRC configuration for multi-PDSCH scheduling DCIs across serving cells can determine the number of HARQ-ACK bits for each DAI (each DCI). For example, the number of HARQ-ACK bits corresponding to each DAI (DCI) in the second subcodebook and / or the size of the second subcodebook may not depend on the number of PDSCHs actually scheduled for the corresponding DCI. For example, the number of HARQ-ACK bits for each DAI (DCI) can be fixed to the maximum number of PDSCHs (M) that a multi-PDSCH scheduled DCI can (can / may) schedule.

[0263] The BS can indicate the counter DAI and / or total DAI corresponding to the first and second subcodebooks separately / independently. For example, the first DCI for scheduling a single PDSCH associated with the first HARQ-ACK subcodebook may include a first c-DAI and / or t-DAI increment independent of the second DCI for scheduling multiple PDSCHs and / or CBGs associated with the second HARQ-ACK subcodebook. For example, the first DAI counter and the second DAI counter can be separate.

[0264] In the example, the first HARQ-ACK subcodebook may include HARQ-ACK bits for two PDSCHs scheduled by the multi-PDSCH scheduling DCI.

[0265] In the example, the second HARQ-ACK subcodebook may include HARQ-ACK information for / corresponding to one or more DCIs that are each scheduled based on a CBG-based PDSCH. In the example, the type 2 HARQ-ACK codebook may include a third HARQ-ACK subcodebook, which includes HARQ-ACK information for / corresponding to one or more DCIs that are each scheduled based on a CBG-based PDSCH. One or more DCIs may be configured with CBG-based scheduling. For example, the UE may be configured with a CBG for at least one serving cell in the PUCCH cell group.

[0266] Multiple PDSCH DCI can refer to DL DCI, where at least one entry in the TDRA table associated with the DCI allows scheduling more than one PDSCH.

[0267] In the example, time-domain bundles can be configured for the HARQ-ACK information bits of DCIs that schedule multiple PDSCHs. For example, the UE can generate one HARQ-ACK bit for each bundle, where the bundle can include two or more PDSCHs scheduled by the DCI. For example, all ACK / NACK bits can be bundled into a single bit for each DCI (e.g., based on logical AND / OR functions). In the example, for example, if time-domain bundles are configured, the UE can generate a single HARQ-ACK subcodebook that includes HARQ-ACK information for DCIs that schedule a single PDSCH and DCIs that schedule multiple PDSCHs.

[0268] FIG. 21 An example of DAI counts for each DCI used for multi-PDSCH scheduling is shown according to some implementation schemes. For example, a base station may configure three serving cells (a first cell, a second cell, and a third cell with cell 0 index, cell 1 index, and cell 2 index) for a radio device. The first cell may be configured with TB-based transmissions (e.g., no CBG transmissions and multi-PDSCH scheduling). The second cell may be configured with multi-PDSCH scheduling. For example, the second cell may also be configured with CBG transmissions when the DCI schedules a PDSCH based on a row in the TDRA table indicating a single SLIV. The third cell may be configured with CBG transmissions, where the maximum number of CBGs per TB is M. Configuration parameters may indicate / include one or more first search spaces for the first cell. For example, monitoring opportunities based on one or more first search spaces may occur (or exist) in time slot n. Configuration parameters may indicate / include one or more second search spaces for the second cell. For example, based on one or more second search spaces, three monitoring opportunities may occur (or may be configured to be monitored) in time slot n, time slot n+1, and time slot n+2.

[0269] A radio device can receive a first multiple PDSCH DCI (M-DCI) in time slot n for a second cell. In this example, the first multiple PDSCH DCI can be transmitted via the second cell. The first multiple PDSCH DCI can schedule three PDSCHs via time slots n to n+2. The multiple PDSCH DCI can indicate PUCCH resources for HARQ-ACK feedback of the three PDSCHs. The radio device can receive the first DCI (DCI) in time slot n via cell 2. The first DCI can schedule M CBGs via the first PDSCH, where the first PDSCH can be scheduled via time slot n+1. The first DCI can indicate PUCCH resources for HARQ-ACK feedback of the CBGs. The radio device can receive a second DCI (DCI 1) in time slot n+1 to schedule the second PDSCH in time slot n+1. The radio device can receive a third DCI (DCI 2) in time slot n+2 to schedule the third PDSCH in time slot n+2. The second and third DCIs can indicate the PUCCH resources used for corresponding HARQ-ACK transmissions.

[0270] exist FIG. 21 In the example, the wireless device can determine a first HARQ-ACK subcodebook that includes HARQ-ACK information of a second DCI (or second PDSCH) and a third DCI (or third PDSCH). For example, the first subcodebook may correspond to a single-TB scheduling DCI. FIG. 22 As shown, the C-DAI and T-DAI values ​​indicated by DCI 1 and DCI 2 are counted / incremented based on the first subcodebook and are independent of / separate from the second subcodebook.

[0271] The wireless device can determine a second HARQ-ACK subcodebook that includes the M-DCI (or three PDSCHs scheduled by the first multi-PDSCH DCI) and the HARQ-ACK information of the first DCI (or scheduling CBG) on cell 2. For example, the second subcodebook may correspond to multi-PDSCH and / or CBG-based scheduling DCI. FIG. 22 As shown, the C-DAI and T-DAI values ​​indicated by the first DCI and M-DCI are counted / incremented based on the second subcodebook and are independent of / separate from the first subcodebook.

[0272] For example, a HARQ feedback or HARQ-ACK codebook that is multiplexed in a PUCCH resource and transmitted via a PUCCH resource may include a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook.

[0273] The UE can be configured with multiple PDSCH scheduling and a Type 2 (dynamic) HARQ-ACK codebook. The UE can generate a Type 2 HARQ-ACK codebook corresponding to the DCI for multiple schedulable PDSCHs. The DCI for scheduling multiple PDSCHs can include a counter DAI and / or a total DAI field. In a second example, the counter DAI and / or total DAI can be counted for each PDSCH (also referred to as Alt 2). For example, the RRC configuration can include at least one parameter indicating that the counter DAI and / or total DAI are counted for each PDSCH.

[0274] For example, if multiple PDSCH scheduling is configured for at least one serving cell in a PUCCH cell group and / or a DAI count and / or an RRC indication for a second value of the first parameter are configured for each PDSCH, then for the PUCCH cell group, the Type 2 HARQ-ACK codebook may include a sub-codebook (for non-CBGs). For example, a single HARQ-ACK sub-codebook may include a first HARQ-ACK bit corresponding to a first DCI scheduling a single PDSCH and a second HARQ-ACK bit corresponding to a second DCI scheduling multiple PDSCHs. The HARQ-ACK codebook may include a second HARQ-ACK sub-codebook that includes HARQ-ACK information for the CBG. For example, the second HARQ-ACK sub-codebook may include HARQ-ACK information for / corresponding to one or more DCIs that each schedule a CBG-based PDSCH. One or more DCIs may be configured with CBG-based scheduling. For example, the UE may be configured with a CBG for at least one serving cell in the PUCCH cell group. The second subcodebook may not include HARQ-ACK for multi-PDSCH scheduling DCI.

[0275] In the example, when counting c-DAI and / or t-DAI for each PDSCH, the UE can generate one HARQ-ACK bit for each PDSCH. For example, the UE can generate one HARQ-ACK bit for each counter DAI. For example, the UE can generate a variable number of HARQ-ACK information bits corresponding to different DCIs in the first HARQ-ACK subcodebook. For example, the number of HARQ-ACK bits corresponding to each DCI in the first subcodebook (for single-PDSCH scheduled DCIs and multi-PDSCH scheduled DCIs) and / or the size of the first subcodebook can depend on the number of PDSCHs actually scheduled for the corresponding DCI. For example, the number of HARQ-ACK bits can depend on the number of scheduled PDSCHs.

[0276] The BS can jointly indicate the counter DAI and / or total DAI corresponding to the first subcodebook for both single PDSCH scheduling DCI and multi-PDSCH scheduling DCI. For example, the first DCI for scheduling a single PDSCH may include a first c-DAI and / or t-DAI increment, and the second c-DAI and / or t-DAI increment for the second DCI for scheduling multiple PDSCHs. For example, the single PDSCH scheduling DCI and the multi-PDSCH scheduling DCI may share the counter DAI and / or total DAI value.

[0277] In the example, the ordering of PDSCHs for DAI counting of type 2 codebook can be as follows: first, PDSCHs scheduled by a single DCI can be counted; second, serving cells in the same PUCCH cell group and the same PDCCH monitoring time can be counted; and third, PDCCH monitoring time can be counted.

[0278] FIG. 22 An example of the DAI count for each PDSCH for multi-PDSCH scheduling according to some implementation schemes is shown. The base station may transmit one or more RRC messages including / indicating configuration parameters. The radio device may be configured with two serving cells, including a first cell (cell 0) and a second cell (cell 1). The second cell may be configured for multi-PDSCH scheduling. For example, the configuration parameters may indicate a TDRA table including at least one row with multiple valid SLIVs for PDSCH scheduling via DCI format. The first cell may be configured for multi-PDSCH scheduling. The first cell may not be configured for multi-PDSCH scheduling.

[0279] For example, a multi-PDSCH DCI format can refer to a DCI format used for multi-PDSCH scheduling. For example, a multi-PDSCH DCI format can be a non-backoff DCI format (e.g., DCI format 1_1). For example, a multi-PDSCH DCI format can be DCI format 1_3. A multi-PDSCH DCI format can include multiple NDI bits, where each of the multiple NDI bits corresponds to each of one or more PDSCHs scheduled by the DCI based on the multi-PDSCH DCI format. A multi-PDSCH DCI format can include multiple RV fields / bits, where each of the multiple RV fields / bits corresponds to each of one or more PDSCHs. For example, a single-PDSCH DCI format can refer to a DCI format used for single-PDSCH scheduling. For example, a single-PDSCH DCI format can be a non-backoff DCI format (e.g., DCI format 1_1). For example, a multi-PDSCH DCI format can be DCI format 1_2. For example, a single-PDSCH DCI format can be a backoff DCI format (e.g., DCI format 1_0). A single PDSCH DCI format can include a single NDI bit for a single PDSCH.

[0280] In the example, the base station and radio equipment can determine the DCI counter DAI based on the number of PDSCH, SPS PDSCH releases, and / or SCell sleep indications scheduled by the previous DCI and the first counter DAI value of the previous DCI. The base station can increment the first counter DAI value by the number of PDSCH, SPS PDSCH releases, and / or SCell sleep indications scheduled by the previous DCI. In the example, the base station and radio equipment can determine the DCI counter DAI based on the accumulation of the number of PDSCH, SPS PDSCH releases, and / or SCell sleep indications up to the DCI scheduled via {serving cell, current PDCCH monitoring time}. In the example, the base station and radio equipment can determine the DCI counter DAI based on the accumulation of the number of transport blocks, SPS PDSCH releases, and / or SCell sleep indications up to the DCI scheduled via {serving cell, current PDCCH monitoring time}. The DCI and the previous DCI can share (e.g., count, consider, use) the DAI counter procedure used by the base station. The base station may have used the same DAI counter procedure to update the C-DAI and T-DAI values ​​of the DCI compared to (or from) the previous DCI. The previous DCI can be a DCI that appeared in the same PDCCH monitoring time as the current DCI or a DCI from a previous PDCCH monitoring time. Based on the DAI counter, the base station may not schedule any DCI between the previous DCI and this DCI. The base station and radio equipment may determine the total DAI of the DCI in the PDCCH monitoring time based on the number of PDSCH, SPS PDSCH releases, and / or SCell sleep indications scheduled by one or more DCIs up to the PDCCH monitoring time. One or more DCIs may include this DCI.

[0281] exist FIG. 22In the example, the UE can receive a multi-PDSCH scheduling DCI (M-DCI) in time slot n via cell 1. The M-DCI schedules, for example, three PDSCHs in time slots n through n+2. The UE can receive a second DCI (DCI 1) and a third DCI (DCI 2) via cell 0 in time slots n+1 and n+2, respectively. The second and third DCIs can be single-PDSCH scheduling DCIs. The multi-PDSCH scheduling DCI includes a DAI field indicating at least a first counter DAI and a first total DAI value. For example, the first counter DAI can correspond to the first PDSCH scheduled by the M-DCI. For example, the first PDSCH can be the earliest PDSCH (e.g., PDSCH 0 in time slot n). For example, the first PDSCH can be the last PDSCH scheduled by the M-DCI (e.g., PDSCH 2 in time slot n+2). In the example, the M-DCI can indicate multiple counter DAI values ​​for each of the PDSCHs scheduled by the M-DCI. FIG. 22 In the example, M-DCI indicates that for the first scheduled PDSCH (in slot n), C-DAI = 0. M-DCI indicates t-DAI, which corresponds to the cumulative number of PDCSHs received by M-DCI and any other possible DCI scheduled PDSCHs received at the same PDCCH monitoring time. FIG. 22In the example, M-DCI indicates T-DAI = 2 (counting the 3 PDSCHs scheduled in the PDCCH monitoring time in slot n). The second DCI shares the DAI counting procedure and indicates C-DAI = 3 and T-DAI = 3. For example, the C-DAI indicated by DCI-1 is determined by incrementing the last C-DAI value received in the last PDCCH monitoring time, for example assuming the virtual DCI indicates C-DAI = 1 for the second PDSCH scheduled by M-DCI and C-DAI = 2 for the third PDSCH. For example, the C-DAI indicated by DCI-1 can be determined based on: (1) the last C-DAI indicated by the last PDCCH monitoring time (e.g., C-DAI = 0); and (2) the number of PDSCHs scheduled by the DCI associated with the last received C-DAI (3 PDSCHs). The base station can increment the C-DAI value of the second DCI by the number of PDSCHs scheduled by the last DCI. For example, the C-DAI of the PDSCH scheduled by DCI 1 = the C-DAI (0) indicated by M-DCI + the number of PDSCHs scheduled by M-DCI (3) = 3. The base station can determine the T-DAI of the second DCI as 3, as the sum of the T-DAI indicated by the last DCI (M-DCI) and the second number of PDSCHs scheduled by the second DCI (e.g., 2+1). Similarly, the third DCI shares the DAI counting procedure and indicates C-DAI = 4 and T-DAI = 4.

[0282] for FIG. 23A For example, the UE can generate a HARQ-ACK codebook, which includes: first, the HARQ-ACK bits (in order of start symbol) of the PDSCHs scheduled by the multi-PDSCH scheduling DCI during the first PDCCH monitoring opportunity; second, the HARQ-ACK information associated with DCI 1 received during the second PDCCH monitoring opportunity; and third, the HARQ-ACK information associated with DCI 2 received during the third PDCCH monitoring opportunity. FIG. 23B In the example, no second DCI (DCI 1) is received. The UE can determine the number of PDSCHs associated with the lost DCI in the codebook and the corresponding ACK / NACK bits based on the detected gap between the T-DAI of M-DCI (2) and the C-DAI of DCI 2 (4), which means that one PDSCH (corresponding to C-DAI=3) is lost. The UE can generate a NACK for the lost PDSCH and place the NACK in the HARQ-ACK codebook at C-DAI=3.

[0283] A wireless device (UE) can determine the power used for PUCCH transmissions based on uplink power control. For example, if the UE is configured with a PUCCH SCell, PUCCH transmissions can be associated with a primary PUCCH group and / or a secondary PUCCH group.

[0284] The UE can transmit PUCCH on the active UL BWP of a UL carrier in a cell (e.g., primary cell and / or secondary cell). The UE can use the PUCCH power control adjustment state to determine the PUCCH transmission power in the PUCCH transmission timing (or PUCCH resource). For example, if the UE transmits PUCCH on the active UL BWP b of carrier f in primary cell c using the PUCCH power control adjustment state with index l, the UE can determine the PUCCH transmission power P in PUCCH transmission timing i. PUCCH,b,f,c (i,q u ,q d ,l) is

[0285]

[0286] in:

[0287] -P CMAX,f,c (i) can be the maximum output power configured for the UE for the carrier f of the primary cell c during PUCCH transmission timing i.

[0288] P O_PUCCH,b,f,c (q u The parameter can be the sum of the following: the first component of the carrier f for the primary cell c (e.g., P). O_NOMINAL _PUCCH It is composed of p0-nominal or (in the absence of p0-nominal) P O_NOMINAL_PUCCH =0dBm provided); and (if provided) the second component of the active UL BWP b for carrier f of primary cell c (e.g., P O_UE_PUCCH (q u (, which is provided by p0-PUCCH-Value in P0-PUCCH), where 0≤q u u and Q u It can be for a set of values ​​(e.g., P provided by maxNrofPUCCH-P0-PerSet). O_UE_PUCCH The size of the value. A set of P O_UE_PUCCH The value can be provided by a parameter (e.g., p0-Set). For example, if p0-Set is not provided to the UE, then P O_UE_PUCCH (q u )=0,0≤q u u . ​​

[0289] - It can be the bandwidth of PUCCH resource allocation expressed in multiple resource blocks of carrier f of primary cell c on the active UL BWP b of PUCCH transmission time i, and μ is the SCS configuration.

[0290] -PL b,f,c (q d This could be the UE's active DL BWPb using RS resource index q for carrier f of primary cell c. d Calculated downlink path loss estimate in dB.

[0291] - If provided, then parameter Δ F_PUCCH (F) For example, for PUCCH format 0, it can be the value of deltaF-PUCCH-f0; for PUCCH format 1, it can be the value of deltaF-PUCCH-f1; for PUCCH format 2, it can be the value of deltaF-PUCCH-f2; for PUCCH format 3, it can be the value of deltaF-PUCCH-f3; and for PUCCH format 4, it can be the value of deltaF-PUCCH-f4; otherwise, Δ F_PUCCH (F) = 0.

[0292] - The PUCCH power control adjustment state g for carrier f of primary cell c and PUCCH transmission timing i. b,f,c (i,l):g b,f,c (i,l) can be the current PUCCH power control adjustment state l for the active UL BWPb of carrier f in the primary cell c and the PUCCH transmission timing i.

[0293] -Δ TF,b,f,c (i) can be the PUCCH transmission power adjustment component on the active UL BWP b of the carrier f of the primary cell c.

[0294] Wireless devices can determine the PUCCH transmission power based on the PUCCH transmission power adjustment component. (δ function Δ) TF,b,f,c(i) The transmission power for different PUCCH formats can be adjusted based on the corresponding coding gain. For example, different coding schemes, such as simplex, Reed-Muller (RM), and polar coding schemes, can be used based on different UCI payload sizes. The coding gain may differ for different coding schemes. Furthermore, the coding gain can also depend on the CRC length, for example, since the CRC can be considered as data in the encoder. For example, for UCI with a polar coding scheme, a CRC of length 6 can be used for UCI payload sizes between 12 and 19 bits, and a CRC of length 11 can be used for UCI payload sizes greater than 19 bits. The δ function Δ can be specified based on the coding gain. TF,b,f,c (i). However, due to varying time and frequency diversity gains, the same UCI payload size carried by different PUCCH formats may exhibit different performance. We evaluated the performance of different PUCCH formats using BLER. The δ function Δ can be set for each PUCCH format. TF,b,f,c (i) To meet the required SINR. δ function Δ TF,b,f,c (i) can be a function of random variables of encoding gain and diversity gain. To achieve the target SINR, the δ function Δ TF,b,f,c (i) can be determined by the UCI payload size, resource allocation, diversity gain, and channel coding scheme. The coding gain can depend on the UCI payload size, the number of resource elements (REs) carrying the UCI, and the coding scheme.

[0295] δ function Δ TF,b,f,c (i) It can at least reflect the UCI payload size and / or UCI type (e.g., SR, HARQ-ACK, and / or CSI report) and / or different coding gains and / or PUCCH formats and / or coding schemes and / or different effective coding rates. For PUCCH power control, the wireless device can determine the δ function Δ based on the number of (valid) UCI ​​bits including (valid) HARQ-ACK information bits and / or the PUCCH format based on PUCCH resources / transmission timing. TF,b,f,c (i). For example, for the effective coding rate of the HARQ-ACK report / codebook, the network scheduler can know one or more HARQ-ACK information bits (e.g., NACK) corresponding to one or more untransmitted PDSCHs, and can exclude these one or more HARQ-ACK information bits from the coding rate. For example, in determining the δ function Δ used for PUCCH power control... TF,b,f,c In case (i), the number of HARQ-ACK bits can be determined by considering only the received PDSCH, for example, excluding known bits.

[0296] For PUCCH transmissions using PUCCH format 0 or PUCCH format 1, in:

[0297] - It can be multiple PUCCH format 0 symbols or PUCCH format 1 symbols used for PUCCH transmission.

[0298] -For PUCCH format 0,

[0299] -For PUCCH format 1,

[0300] -For PUCCH format 0, Δ UCI (i)=0

[0301] -For PUCCH format 1, Δ UCI (i) = 10log 10 (O UCI (i)), where O UCI (i) can be the number of UCI bits in time i during PUCCH transmission.

[0302] For PUCCH transmissions using PUCCH format 2, PUCCH format 3, or PUCCH format 4, and the number of UCI bits less than or equal to the first value (e.g., 11), Δ TF,b,f,c (i) = 10log 10 (K1·(n HARQ-ACK (i)+O SR (i)+O CSI (i)) / N RE (i)), where:

[0303] -K1=6

[0304] -n HARQ-ACK (i) can be the number of HARQ-ACK information bits that the UE can determine for both the Type 1 HARQ-ACK codebook and the Type 2 HARQ-ACK codebook. n HARQ-ACK (i) Can be used with O for type 3 HARQ-ACK codebooks (e.g., a one-time HARQ-ACK codebook that includes HARQ-ACK information for all downlink HARQ processes). ACK (i) The total number of HARQ-ACK information bits is the same. In one example, if the UE is not provided with any codebook configuration (e.g., pdsch-HARQ-ACK-Codebook, pdsch-HARQ-ACK-Codebook-r16 and / or pdsch-HARQ-ACK-OneShotFeedback), then if the UE includes HARQ-ACK information bits in the PUCCH transmission, then n HARQ-ACK (i) = 1; otherwise nHARQ-ACK (i) = 0.

[0305] -O SR (i) can be the number of SR information bits determined by the UE.

[0306] -O CSI (i) can be the number of CSI information bits determined by the UE.

[0307] -N RE (i) can be determined as The number of resource elements, where the PUCCH transmission timing i on the active UL BWPb of carrier f in primary cell c, This can be the number of subcarriers in each resource block, excluding the subcarriers used for DM-RS transmission, and It can be the number of symbols other than those used for DM-RS transmission, and The bandwidth of the PUCCH resource allocation can be represented by the number of resource blocks on the active ULBWPb of the carrier f for the primary cell c.

[0308] For PUCCH transmissions using PUCCH format 2, PUCCH format 3, or PUCCH format 4, and the number of UCI bits greater than the first value (e.g., 11), in:

[0309] -K2=2.4

[0310] -BPRE(i)=(O ACK (i)+O SR (i)+O CSI (i)+O CRC (i)) / N RE (i)

[0311] -O ACK (i) can be the number of HARQ-ACK information bits determined by the UE for a Type 1 HARQ-ACK codebook and a Type 2 HARQ-ACK codebook or a Type 3 HARQ-ACK codebook. In one example, if the UE is not provided with any codebook configuration (e.g., pdsch-HARQ-ACK-Codebook, pdsch-HARQ-ACK-Codebook-r16, or pdsch-HARQ-ACK-OneShotFeedback), and if the UE includes HARQ-ACK information bits in the PUCCH transmission, then O ACK =1; otherwise O ACK =0.

[0312] -O SR(i) can be the number of SR information bits determined by the UE.

[0313] -O CSI (i) can be the number of CSI information bits determined by the UE.

[0314] -O CRC (i) can be the number of CRC bits determined by the UE.

[0315] -N RE (i) can be determined by the UE as The number of resource elements, where the PUCCH transmission timing i on the active UL BWPb of carrier f in primary cell c, This can be the number of subcarriers in each resource block, excluding the subcarriers used for DM-RS transmission, and It can be the number of symbols other than those used for DM-RS transmission, and The bandwidth of the PUCCH resource allocation can be represented by the number of resource blocks on the active ULBWPb of the carrier f for the primary cell c.

[0316] For Δ TF,b,f,c (i) can be defined (e.g., at least for PUCCH formats 2, 3, and 4) to define the number of HARQ-ACK bits for a cell configured with a CBG. For example, one bit can be counted for each received CBG for PUCCH power control.

[0317] The wireless device can be configured with a Type 1 HARQ-ACK codebook. For example, the UE can receive the RRC parameter pdsch-HARQ-ACK-Codebook = semi-static. The UE can, for example, report HARQ-ACK information for corresponding PDSCH reception or SPS PDSCH release in the HARQ-ACK codebook transmitted by the UE in a time slot. This time slot can be indicated by the value of the PDSCH-to-HARQ_feedback timing indicator field in the corresponding DCI format. The UE can report NACK values ​​for the HARQ-ACK information bits in the HARQ-ACK codebook if the UE transmits the HARQ-ACK codebook in a time slot where the value of the PDSCH-to-HARQ_feedback timing indicator field in the corresponding DCI format is not indicated.

[0318] The UE can report HARQ-ACK information for PDSCH reception in the HARQ-ACK codebook included / multiplexed in its PUCCH or PUSCH transmission. The PUCCH or PUSCH transmission can occur in time slot n+k, where n is the UL time slot overlapping the end of PDSCH reception in the corresponding DL time slot, and k is the time offset. The time offset k can be indicated by the PDSCH-to-HARQ_feedback timing indicator field in the corresponding DCI format, or, in the case where the PDSCH-to-HARQ_feedback timing indicator field is not present in the DCI format, the number of time slots provided by dl-DataToUL-ACK. For example, if the UE reports HARQ-ACK information for PDSCH reception in time slots other than n+k, the UE can set the value for each corresponding HARQ-ACK information bit to NACK.

[0319] In the example, the UE can report HARQ-ACK information in the PUCCH for only the following: SPS PDSCH release indicated by the DCI (e.g., DCI format 1_0 with counter DAI field value of 1); or PDSCH reception scheduled by the DCI (e.g., DCI format 1_0 with counter DAI field value of 1 on the PCell); or SPS PDSCH reception within the timing for candidate PDSCH reception. The UE can determine the HARQ-ACK codebook for SPS PDSCH release, PDSCH reception, or a single SPS PDSCH reception based on the corresponding timing on the serving cell. The HARQ-ACK information bits in response to more than one SPS PDSCH reception that the UE can be configured to receive can be ordered according to pseudocode.

[0320] For O ACK The total number of HARQ-ACK information bits allows the UE to determine the HARQ-ACK codebook (e.g., based on a Type 1 codebook) to be used for transmission in the PUCCH. HARQ-ACK information bits. In the example, if the UE does not receive a Transport Block (TB) or CBG because it does not detect the corresponding DCI format, the UE can generate a NACK value for the Transport Block or CBG. The set M used for candidate PDSCH reception. A,c The cardinality of the timing can define the total number M of timings for PDSCH reception or SPS PDSCH release for serving cell c, corresponding to the HARQ-ACK information bits. c .

[0321] In the example, the UE can determine the number n of HARQ-ACK information bits used to obtain the transmission power for the PUCCH.HARQ-ACK for For example, PUCCH may include a HARQ-ACK codebook and / or SR and / or CSI reports. For example, the total number of HARQ-ACK information bits, SR bits, and CSI report bits in the codebook may be less than the first value (O). ACK +O SR +O CSI ≤11). For example, the number of HARQ-ACK information bits n HARQ-ACK This can include valid ACK / NACK bits from the HARQ-ACK codebook, excluding known information bits (e.g., NACK). For example, the valid number n of HARQ-ACK information bits. HARQ-ACK The number of HARQ-ACK bits in the codebook can be less than or equal to O. ACK .

[0322] In the formula for the number of HARQ-ACK bits in a Type 1 codebook,

[0323] - It can be the number of transport blocks (TB) received by the UE during the PDSCH reception time m for the serving cell c, for example, in the absence of harq-ACK-SpatialBundlingPUCCH and PDSCH-CodeBlockGroupTransmission. It can be the number of transport blocks received by the UE during the PDSCH reception time m for the serving cell c, for example, when PDSCH-CodeBlockGroupTransmission is provided and PDSCH reception is scheduled by a DCI format that does not support CBG-based PDSCH reception. It can be the number of PDSCH received, for example, in the case where harq-ACK-SpatialBundlingPUCCH or SPS PDSCH release is provided in the PDSCH reception timing m for serving cell c, and the UE reports the corresponding HARQ-ACK information in the PUCCH.

[0324] - It could be the number of CBGs received by the UE during the PDSCH reception time m for the serving cell c, for example, when PDSCH-CodeBlockGroupTransmission is provided and PDSCH reception is scheduled by a DCI format that supports CBG-based PDSCH reception, and the UE reports the corresponding HARQ-ACK information in the PUCCH.

[0325] -M cIt can be the total number of times for receiving PDSCH or releasing SPSPDSCH for serving cell c, corresponding to the HARQ-ACK information bits.

[0326] - It can be the number of serving cells configured by a higher layer for the UE.

[0327] The wireless device can be configured with a Type 2 HARQ-ACK codebook. For example, the UE can receive the RRC parameter pdsch-HARQ-ACK-Codebook = dynamicpdsch-HARQ-ACK-Codebook-r16. The UE may not expect to multiplex Type 2 HARQ-ACK codebook HARQ-ACK information in response to detection of a DCI format that does not include the counter DAI field. The UE can use the DCI format to schedule PDSCH reception or SPS PDSCH release or indicate SCell sleep on the active DL BWP of serving cell c to determine the timing of PDCCH monitoring. The UE can transmit HARQ-ACK information for PDSCH reception and / or SPS PDSCH release and / or SCell sleep indication in the same PUCCH in time slot n.

[0328] In response to PDSCH reception, SPS PDSCH release, or SCell sleep indication, the UE may determine the monitoring timing based on a first time slot offset (e.g., the PDSCH-to-HARQ_feedback timing indicator field value) used for PUCCH transmission using HARQ-ACK information in time slot n. The UE may also determine the monitoring timing based on the time-domain resource assignment field in the DCI format received by the scheduling PDSCH and a second time slot offset (e.g., K0) provided by pdsch-AggregationFactor, pdsch-AggregationFactor-r16, or repetitionNumber (when provided).

[0329] The set of PDCCH monitoring opportunities in DCI format used for scheduling PDSCH reception or SPS PDSCH release or indicating SCell hibernation can be defined as the union of PDCCH monitoring opportunities across the configured serving cell's active DL BWP. PDCCH monitoring opportunities can be arranged in ascending order of their start time. The cardinality of the PDCCH monitoring opportunity set can limit the total number M of PDCCH monitoring opportunities.

[0330] The value of the downlink assignment indicator (DAI) field in the DCI format represents the cumulative number of {serving cell, PDCCH monitoring timing} pairs that have been associated with the DCI format up to the current serving cell and the current PDCCH monitoring timing. The counter DAI can be incremented as follows: for example, if the UE indicates (e.g., via type2-HARQ-ACK-Codebook) that it supports more than one PDSCH reception on a serving cell scheduled from the same PDCCH monitoring timing, it first increments in ascending order of the PDSCH reception start time for the same {serving cell, PDCCH monitoring timing} pair; secondly, it increments in ascending order of the serving cell index; and thirdly, it increments in ascending order of the PDCCH monitoring timing index m, where 0 ≤ m. <M。

[0331] In the example, if for the active DL BWP of the serving cell, the UE is not provided with coresetPoolIndex or is provided with coresetPoolIndex (value of 0 for one or more first CORESETs) and is provided with coresetPoolIndex (value of 1 for one or more second CORESETs) and is provided with ackNackFeedbackMode=joint, then for the same serving cell index and the same PDCCH monitoring timing index, the value of counter DAI can be in the order of first CORESET, followed by second CORESET.

[0332] When present / configured, the total DAI value in the DCI format can represent the total number of {serving cell, PDCCH monitoring time} pairs that have occurred up to the current PDCCH monitoring time m and are associated with the DCI format, including PDSCH reception, SPS PDSCH release, or SCell sleep indication. The total DAI can be updated between PDCCH monitoring times. In the example, if for the active DL BWP of the serving cell, the UE is not provided with a coresetPoolIndex, or is provided with a coresetPoolIndex (value 0 for one or more first CORESETs) and is provided with a coresetPoolIndex (value 1 for one or more second CORESETs) and is provided with ackNackFeedbackMode=joint, then for the first and second CORESETs, the total DAI value can be counted for the {serving cell, PDCCH monitoring time} pairs.

[0333] This can represent the number of bits for the counter DAI. The UE can set this. It can represent the value of the counter DAI in the DCI format, which schedules PDSCH reception, SPS PDSCH release, or SCell sleep indication on the serving cell c during PDCCH monitoring time m. It can represent the total DAI value in the DCI format during PDCCH monitoring.

[0334] FIG. 22 and FIG. 22 An example is shown of determining the counter DAI and / or total DAI values ​​based on corresponding DCI indications (e.g., the DAI field in the DCI) according to some implementation schemes. The UE may assume that the total DAI value is the same for all DCI formats that include the total DAI field during PDCCH monitoring. The UE may not expect to multiplex HARQ-ACK information in response to the detection of a DCI format with different bit lengths for the counter DAI field in the same type of 2HARQ-ACK codebook.

[0335] UE can target O in Type 2 codebook ACK The total number of HARQ-ACK information bits is determined. HARQ-ACK information bits. The UE can transmit HARQ-ACK information in time slot n within the PUCCH and for any PUCCH format.

[0336] The UE can be configured to receive SPS PDSCH, and the UE can multiplex HARQ-ACK information for an active SPS PDSCH reception in the PUCCH within time slot n. The UE can generate a HARQ-ACK bit associated with the SPS PDSCH reception and can append this HARQ-ACK bit to O. ACK HARQ-ACK information bits. The UE can be configured to receive SPS PDSCH, and the UE can multiplex HARQ-ACK information for receiving multiple active SPS PDSCH in the PUCCH within time slot n. The UE can generate HARQ-ACK information and append it to O. ACK HARQ-ACK information bits.

[0337] For PDCCH monitoring timings with DCI format that schedules PDSCH reception, SPS PDSCH release, or indicates SCell sleep in the active DL BWP of the serving cell, when the UE receives a PDSCH with a transport block (TB) or an SPS PDSCH release or indicates SCell sleep, HARQ-ACK information can be associated with the first transport block, and the UE can generate NACK for the second transport block, for example, if two codewords are configured for each PDSCH (e.g., the value of maxNrofCodeWordsScheduledByDCI is 2) and / or no bundle is configured (e.g., no harq-ACK-SpatialBundlingPUCCH is provided). If a bundle is configured (e.g., harq-ACK-SpatialBundlingPUCCH is provided), the UE can generate HARQ-ACK information with an ACK value for the second transport block.

[0338] The UE can determine the number n of HARQ-ACK information bits in the Type 2 codebook. HARQ-ACK This is to obtain the transmission power for the corresponding PUCCH. For example, the PUCCH may include a HARQ-ACK codebook and / or SR and / or CSI reports. For example, the total number of HARQ-ACK information bits, SR bits, and CSI report bits in the codebook may be less than the first value (0). ACK +O SR +O CSI ≤11). For example, if for For each serving cell in the serving cells, or for PDSCH reception scheduled for a DCI format that does not support CBG-based PDSCH reception, or for SPS PDSCH reception, or for SPS PDSCH release, or for SCell sleep indication, the UE is not configured with code block groups (e.g., no PDSCH-CodeBlockGroupTransmission is provided), and if O ACK +O SR +N CSI If the number of bits is ≤11, then the UE can determine the number of HARQ-ACK information bits. HARQ-ACK for:

[0339]

[0340] in

[0341] - For any serving cell c detected by the UE within M PDCCH monitoring periods This could be the value of the counter DAI in the last DCI format of the scheduling PDSCH reception, the indication of SPS PDSCH release, or the indication of the SCell sleep, for example, when the UE is configured with a serving cell. In this case.

[0342] -If the UE is configured with more than one serving cell (e.g.) ):

[0343] - It could be the value of the counter DAI in the last DCI format detected by the UE in the last PDCCH monitoring time, for example, when the UE does not detect any DCI format including the total DAI field in the last PDCCH monitoring time within the last PDCCH monitoring time in which the UE detects at least one DCI format that schedules PDSCH reception for any serving cell c, indicates SPSPDSCH release, or indicates SCell sleep.

[0344] - It can be the value of the total DAI in at least one DCI format, for example, when the UE detects at least one DCI format including the total DAI field during the last PDCCH monitoring time within the MPDCCH monitoring time when the UE detects at least one DCI format that schedules PDSCH reception for any serving cell c, instructs SPS PDSCH release, or instructs SCell to sleep.

[0345] - If the UE does not detect any DCI format for scheduling PDSCH reception, indicating SPS PDSCH release, or indicating SCell hibernation for any serving cell c in any of the M PDCCH monitoring opportunities.

[0346] -U DAI,c This can be the total number of DCI formats that the UE detects within M PDCCH monitoring opportunities for serving cell c, including those indicating scheduled PDSCH reception, SPS PDSCH release, and / or SCell sleep. If the UE does not detect any DCI format that indicates scheduled PDSCH reception, SPS PDSCH release, or SCell sleep for serving cell c within any of the M PDCCH monitoring opportunities, then the U DAI,c =0.

[0347] - If two codewords are configured for each PDSCH for any serving cell c (e.g., maxNrofCodeWordsScheduledByDCI is 2) and no bundle is configured (e.g., no harq-ACK-SpatialBundlingPUCCH is provided), then otherwise,

[0348] - It could be the number of transport blocks received by the UE in the PDSCH scheduled by the DCI format detected by the UE in the PDCCH monitoring time m for the serving cell c, for example, in the absence of a bundle configuration (no harq-ACK-SpatialBundlingPUCCH provided). It can be the number of PDSCHs scheduled by the DCI format detected by the UE during PDCCH monitoring time m for serving cell c, for example, in the case of a bundled configuration (providing harq-ACK-SpatialBundlingPUCCH). It can be the number of DCI formats that the UE detects and indicates the release of by the SPS PDSCH during the PDCCH monitoring time m for the serving cell c. It can be the number of DCI formats that the UE detects and indicates SCell to be in sleep mode during PDCCH monitoring time m for serving cell c.

[0349] -N SPS,c It can be the number of SPS PDSCHs received by the UE in the serving cell c. For this serving cell, the UE transmits the corresponding HARQ-ACK information in the same PUCCH as the HARQ-ACK information received by the PDSCH within the M PDCCH monitoring time.

[0350] -M can be the total number of PDCCH monitoring opportunities corresponding to HARQ-ACK messages transmitted in the same PUCCH.

[0351] - It can be the number of serving cells configured by a higher layer for the UE.

[0352] - in This refers to the number of bits configured for the counter DAI.

[0353] UE can be configured to target CBG-based communication for each serving cell. For example, the UE can receive communication targeting... The PDSCH-CodeBlockGroup Transmission for each serving cell. The UE may not be configured with PDSCH-CodeBlockGroup Transmission. CBG-based communication in each serving cell (e.g., no PDSCH-CodeBlockGroupTransmission received), where (Total number of serving cells configured for the UE).

[0354] UE can determine the target The first HARQ-ACK subcodebook for each cell. The first subcodebook may include SPSPDSCH release and / or SPS PDSCH reception and / or DCI format indicating SCell sleep (e.g., DCI format 1_1) and / or include Service communities and TB-based PDSCH reception on any cell of a serving cell.

[0355] The UE can determine the second HARQ-ACK subcodebook. For example, the second subcodebook can correspond to the PDSCH reception based on CBG. One service community.

[0356] The UE can count the serving cell twice, for example, the first time corresponding to the first CORESET and the second time corresponding to the second CORESET. In the example, the UE may not be configured with multiple TRPs and / or may not have received the coresetPoolIndex for the active DL BWP for the serving cell. In the example, the UE can receive configuration parameters indicating a coresetPoolIndex with a value of 0 for one or more first CORESETs and a coresetPoolIndex with a value of 1 for one or more second CORESETs, and ackNackFeedbackMode = joint.

[0357] The UE can be configured for CBG-based communication, such as providing PDSCH-CodeBlockGroupTransmission for the serving cell. The UE can receive (e.g., scheduled by DCI format 1_1) PDSCHs comprising code block groups (CBGs) of transport blocks. The maximum number of CBGs used to generate the corresponding HARQ-ACK information bits for transport block reception for the serving cell can be provided to the UE by an RRC parameter (e.g., maxCodeBlockGroupsPerTransportBlock). For example, for a transport block containing C code blocks (CBs), the UE can base its decision on the maximum number of CBGs indicating each TB. The RRC parameters (e.g., maxCodeBlockGroupsPerTransportBlock) determine the number M of CBGs. The UE can determine the number of HARQ-ACK bits for a transport block.

[0358] If the UE correctly receives all code blocks of the CBG, the UE can generate an ACK for the HARQ-ACK information bits of the CBG; and if the UE incorrectly receives at least one code block of the CBG, the UE can generate a NACK for the HARQ-ACK information bits of the CBG. If the UE correctly detects... Each CBG in the CBG and did not correctly detect the target If a CBG is used for transmission blocks, then the UE can target... Each CBG in the CBG generates a NACK value. If the UE receives two transport blocks, the UE can append the HARQ-ACK information bits of the CBG for the second transport block to the HARQ-ACK information bits of the CBG for the first transport block.

[0359] HARQ-ACK codebook may include One HARQ-ACK bit, and if for a transport block, Then the UE can be the last block of the transport in the HARQ-ACK codebook. Each HARQ-ACK bit generates a NACK value to align the HARQ-ACK information size of all TBs based on the maximum value.

[0360] The number of HARQ-ACK bits used for retransmission can be the same. (bits). For example, if the UE generates a HARQ-ACK codebook in response to a retransmission of a transport block (corresponding to the same HARQ process as the previous transport block), the UE can generate an ACK for each CBG that the UE correctly decoded in the previous transport block.

[0361] UE may not be targeted (e.g., from) For each transport block of a serving cell configured with CBG, a HARQ-ACK bit is generated. Conversely, the UE can generate a HARQ-ACK bit for each transport block from a serving cell. Each transport block of the service cell generates One HARQ-ACK information bit, of which It can be across all Each service community The maximum value, and This can be the value of `maxNrofCodeWordsScheduledByDCI` for serving cell c. If the number of HARQ-ACK bits for serving cell c is less than the maximum value (e.g., ...), this will affect the HARQ-ACK bit count. If so, then the UE can be the last one for serving cell c. One HARQ-ACK bit is used to generate a NACK.

[0362] The counter DAI value and the total DAI value can be applied to each of the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook, respectively. The UE can generate the HARQ-ACK codebook by appending the second HARQ-ACK subcodebook to the first HARQ-ACK subcodebook.

[0363] UE can be based on n HARQ-ACK =n HARQ-ACK,TB +n HARQ-ACK,CBG To determine the number n of HARQ-ACK information bits used to determine the transmission power for the corresponding PUCCH (PUCCH power control). HARQ-ACK For example, the PUCCH may include a HARQ-ACK codebook and / or SR and / or CSI reports. The HARQ-ACK codebook may be a Type 2 (dynamic) codebook that includes CBG-based sub-codebooks. For example, the UE may be configured with CBG-based communication for at least one serving cell. For example, the total number of HARQ-ACK information bits, SR bits, and CSI report bits in the codebook may be less than a first value (0). ACK +O SR +O CSI ≤11).

[0364] The UE can determine the number n of HARQ-ACK information bits in the CBG subcodebook as follows: HARQ-ACK,CBG :

[0365]

[0366] in

[0367] - It could be the value of the counter DAI in the last DCI format of the PDSCH received based on CBG, which is detected by the UE within M PDCCH monitoring periods for the serving cell c scheduling. For example, when the UE is configured to have a serving cell In this case.

[0368] - It can be the total DAI value in the last DCI format of the PDSCH received based on CBG for any serving cell c detected by the UE within M PDCCH monitoring periods, for example, when the UE is configured with more than one serving cell. In this case.

[0369] - For example, if the UE does not detect any DCI format for CBG-based PDSCH reception for any serving cell c scheduling in any of the M PDCCH monitoring opportunities, then

[0370] - This can be the total number of DCI formats for scheduled CBG-based PDSCH reception detected by the UE within M PDCCH monitoring opportunities for serving cell c. If the UE does not detect any DCI formats for scheduled CBG-based PDSCH reception for serving cell c within any of the M PDCCH monitoring opportunities, then... - It can be the number of CBGs received by the UE in a PDSCH scheduled by a DCI format that supports CBG-based PDSCH reception. The UE detects the CBG-based PDSCH reception during the PDCCH monitoring time m for serving cell c, and the UE reports the corresponding HARQ-ACK information in the PUCCH.

[0371] Existing techniques for determining PUCCH power control, including HARQ-ACK codebooks, may fail to accurately capture the number of HARQ-ACK bits associated with multi-PDSCH scheduling DCIs in Type 2 dynamic codebooks. For example, existing mechanisms for PUCCH power control may be based on a 1:1 correspondence between the DCI format and a fixed count / number of ACK / NACK bits for each DCI format (e.g., 1 bit for a single TB and / or two codeword transmissions with bundled / joint feedback, 2 bits for two codeword transmissions without bundled / joint feedback, and...). (Bits are used for CBG-based communication). However, with the introduction of multi-PDSCH scheduling DCIs that include incrementing DAI for each PDSCH, the UE can report a different number of ACK / NACK bits for each DCI based on the actual number of scheduled PDSCHs, thereby reducing the HARQ-ACK codebook size. Therefore, traditional mechanisms may no longer be able to determine the accurate power used for PUCCH transmissions that include the HARQ-ACK codebook.

[0372] For the effective coding rate of the HARQ-ACK report used for PUCCH power control determination, the UCI size can be determined based on the effective ACK / NACK bit count against a type 2 dynamic codebook, which includes: (1) the number of transport blocks (TBs) / CBGs received in the PDSCH scheduled by the DCI format that contribute to the effective A / N in the codebook, and (2) the number of lost TBs / CBGs that contribute to the meaningful NACK in the codebook. For example, in the following formula for TB-based scheduling:

[0373]

[0374] item Corresponding to the number of received transmit blocks (e.g., one HARQ-ACK bit per TB), and the item The number of HARQ-ACK bits generated corresponding to the detected lost PDCCH (Lost DCI) is determined by the following operation: from the last received total DAI (or the last received counter DAI). Subtract the number of DCIs received And multiply the result by the maximum number of TBs that the PDSCH can include (e.g., in the case of configuring two codewords, such as when the value of maxNrofCodeWordsScheduledByDCI is 2 for any serving cell). otherwise This formula is based on the assumption that one DCI schedules one PDSCH and corresponds to one DAI value (C-DAI and T-DAI) and one HARQ-ACK bit (or two HARQ-ACK bits in the case of two codewords).

[0375] For example, in the following formula for CBG-based scheduling:

[0376]

[0377] item Corresponding to the number of CBGs received (e.g., one HARQ-ACK bit per CBG), and the item The number of HARQ-ACK bits generated corresponding to the detected lost PDCCH (Lost DCI) is determined by the following operation: from the CBG subcodebook The last received total DAI (or the last received counter DAI) is subtracted from the CBG subcodebook. The associated number of received DCIs, and this result is multiplied by the maximum number of CBGs that PDSCH can include. This formula is based on the assumption that one DCI schedules one PDSCH and corresponds to one DAI value (C-DAI and T-DAI) and a fixed number of HARQ-ACK bits.

[0378] In existing technologies, a fixed number of NACKs are reported for each lost DCI. The number of lost DCIs is estimated based on the 1:1 correspondence between DCI and C-DAI values. However, in the case of multi-PDSCH scheduling, a DCI can be scheduled for more than one PDSCH, and, for example, depending on the number of scheduled PDSCHs, the DCI can correspond to multiple and / or a variable number of HARQ-ACK bits. Furthermore, multi-PDSCH scheduled DCIs can (explicitly or implicitly) include / indicate / correspond to multiple DAI values ​​(e.g., multiple C-DAIs). For example, each C-DAI can correspond to one PDSCH scheduled by the DCI. Therefore, the above subtraction may no longer yield an accurate number of lost DCIs. Additionally, the UE can generate a different number of HARQ-ACK bits for each DCI, and the number of lost DCIs may no longer resemble the number of lost TB / CBGs. Therefore, for example, when at least one serving cell is configured to have multiple PDSCH scheduling and / or when the DAI value increases based on the number of scheduled PDSCHs, existing mechanisms may fail to capture the true number of HARQ-ACK bits in the HARQ-ACK codebook used to determine the PUCCH transmission power.

[0379] In the example, when the UE is configured with multi-PDSCH scheduling and the DAI value is counted / incremented for each DCI, the UE can generate a second HARQ-ACK subcodebook associated with the multi-PDSCH scheduled DCI. Existing technology may be unable to determine the number of HARQ-ACK bits in the new subcodebook because the DCI associated with the second subcodebook is no longer associated with a single PDSCH. Therefore, existing mechanisms may not be able to accurately capture the number of NACKs reported for each lost DCI.

[0380] In the example, one or more PDSCHs among multiple PDSCHs scheduled by the DCI may not be valid PDSCHs, for example, they may not have valid SLIVs (start and length indicator values). For example, in a TDD system, one or more symbols of a PDSCH indicated by the corresponding SLIV, as indicated by the TDRA field of the DCI, may overlap with UL symbols. The UE can report NACKs for one or more invalid PDSCHs scheduled by the DCI. However, these NACKs are meaningless NACKs that do not contribute to meaningful feedback information because the base station knows the invalidity of one or more PDSCHs, and the NACK is only to avoid ambiguity regarding the HARQ-ACK payload size. However, based on existing technology, the UE can increment the PUCCH power for such meaningless HARQ-ACK bits, which is unnecessary. The implementation scheme helps the UE determine the accurate and valid PUCCH power for HARQ feedback transmission in the case of multiple PDSCH scheduling by considering the validity of the PDSCHs, and thus avoids additional power increments for invalid PDSCHs. Based on existing technology, in the case of multiple PDSCH scheduling, the radio device may not be able to efficiently and accurately determine the transmission power for the PUCCH. Incorrect PUCCH power control can cause uplink collisions and / or unsuccessful uplink control transmissions. This is a serious problem, especially at higher frequencies where multi-PDSCH scheduling is more critical and efficient HARQ feedback procedures are required. The implementation scheme can enable accurate determination of PUCCH power control in multi-PDSCH scheduling scenarios.

[0381] Based on some implementation schemes, the wireless device can determine the transmission power for the PUCCH by considering the number of PDSCHs that the DCI may eventually schedule. Based on this implementation scheme, the number of NACKs for lost TB / CBG reports can be accurately calculated based on the new DAI definition for multi-PDSCH scheduling and the actual count of scheduled PDSCHs. When using the existing definition of DAI, the implementation scheme considers the maximum number of PDSCHs that the DCI can schedule. When configuring multi-PDSCH scheduling, and for different alternatives to the DAI definition: per PDSCH and per DCI, the implementation scheme can enhance PUCCH power control. Based on this implementation scheme, the UE can determine the transmission power for the PUCCH transmission timing based on the detected number of lost downlink assignments (e.g., PDSCHs). The UE can determine the number of lost downlink assignments / PDSCHs based on the number of received downlink assignments / PDSCHs. For example, the UE can determine the transmission power for a PUCCH transmission timing, including HARQ-ACK information, based on the number of detected / received downlink assignments (e.g., PDSCH receptions) and / or the received DAI value corresponding to the last downlink assignment (e.g., PDSCH). For example, the DAI value can be T-DAI and / or C-DAI. For example, the UE can determine the transmission power for a PUCCH transmission timing based on the number of PDSCHs scheduled by at least one multi-PDSCH scheduling DCI.

[0382] In the implementation, the radio device may receive one or more RRC messages including configuration parameters. The configuration parameters may indicate that at least one serving cell of the UE is configured for multiple PDSCH scheduling. For example, the configuration parameters may include one or more time-domain resource allocations (lists or tables) (e.g., PDSCH-TimeDomainResourceAllocationList) for PDSCH in one or more BWPs of at least one serving cell. For example, one or more time-domain resource allocations (e.g., TDRA table) may include one or more rows / entries indicating two or more (valid) time resources (e.g., SLIV: start symbol and length) used for PDSCH scheduling.

[0383] Configuration parameters can indicate which one or more serving cells to configure for the UE. One or more serving cells can be activated. The UE can determine that one or more serving cells belong to the same PUCCH cell group. For example, configuration parameters can indicate that the PUCCH cell group includes one or more serving cells.

[0384] Configuration parameters can indicate the timing for receiving PDCCH monitoring in one or more DCI formats. One or more DCI formats may include a TDRA field. The TDRA field can, for example, indicate the number of PDSCHs scheduled by the DCI format based on the number of valid SLIVs indicated by the TDRA field. If the configuration parameters of the TDRA list / table of the serving cell (e.g., the scheduling cell) indicate at least one entry / row with multiple valid SLIVs, then the DCI format can schedule multiple PDSCHs. In the example, configuration parameters may include a first parameter indicating that multiple PDSCH scheduling is enabled for the serving cell.

[0385] Configuration parameters can indicate the type of HARQ-ACK codebook for a cell group (e.g., pdsch-HARQ-ACK-Codebook = {semi-static, dynamic}). A cell group can include at least one serving cell. For example, configuration parameters can indicate a type 2 (dynamic) HARQ-ACK codebook.

[0386] Configuration parameters can indicate whether a DCI format includes a DAI field. A DCI format can schedule a single PDSCH. A DCI format can schedule multiple PDSCHs. A DCI format can schedule one or more PDSCHs based on CBG scheduling. For example, a PDSCH may include one or more CBGs. The DAI field can indicate the counter DAI (C-DAI) and / or the total DAI (T-DAI). Configuration parameters can indicate whether C-DAI and / or T-DAI are counted / incremented for each PDSCH or DCI format.

[0387] In the example, configuration parameters can instruct C-DAI and / or T-DAI to be counted / incremented for each PDSCH. The UE can receive DCI / DCI format. The DCI can schedule multiple PDSCHs. The DCI may include a DAI field indicating the first C-DAI. The first C-DAI may correspond to the first PDSCH among the multiple PDSCHs scheduled by the DCI (e.g., reference). FIG. 22For example, the first C-DAI can correspond to the earliest / first PDSCH among multiple PDSCHs. The UE can determine the C-DAI of the remaining PDSCHs among multiple PDSCHs by incrementing the first C-DAI by one for each subsequent PDSCH. In the example, the first C-DAI can correspond to the last PDSCH among multiple PDSCHs. The UE can determine the C-DAI of the remaining PDSCHs among multiple PDSCHs by decrementing the first C-DAI by one for each preceding / former PDSCH. In the example, the DAI field can indicate, for example, multiple DAIs that each correspond to one of the multiple PDSCHs in order of the start symbol.

[0388] A wireless device can receive multiple DCIs. These multiple DCIs can be based on one or more DCI formats (e.g., DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 and / or DCI format 1_3). At least one of the multiple DCIs can schedule the reception of one or more PDSCHs. At least one of the multiple DCIs can schedule / indicate the release of one or more SPSPDSCHs. At least one of the multiple DCIs can schedule / activate the reception of one or more SPS PDSCHs. At least one of the multiple DCIs can instruct the active DL BWP of the serving cell to sleep on one or more SCells.

[0389] At least one of the multiple DCIs can indicate a PUCCH resource used to report HARQ-ACK feedback associated with the multiple DCIs. For example, the UE can transmit HARQ-ACK information for multiple DCIs / multiple DCIs in the (same) PUCCH resource. For example, the at least one DCI can include a slot offset (e.g., a PDSCH-to-HARQ_feedback timing indicator field) that indicates the slot including the PUCCH resource based on a first slot. The first slot can be a DL slot corresponding to receiving at least one DCI. The first slot can be a DL slot for receiving a first PDSCH scheduled by at least one DCI.

[0390] The UE can determine one or more monitoring times for / to the PDCCH. Configuration parameters can indicate that the PDCCH is associated with one or more DCI formats. For example, one or more monitoring times for the PDCCH can be configured with one or more DCI formats. The UE can receive / detect multiple DCIs from / via one or more monitoring times.

[0391] The UE can transmit HARQ-ACK information for one or more PDCCH monitoring events, associated with one or more PDCCH monitoring events, or for one or more PDCCH monitoring events in (the same) PDCCH resource or via (the same) PDCCH resource.

[0392] The UE can determine / obtain the transmission power for PUCCH resources, for example, based on a power control / adjustment formula:

[0393]

[0394] The UE can determine the PUCCH transmission power adjustment component for the transmission power of the PUCCH (e.g., Δ on the active UL BWP b of carrier f in primary cell c). TF,b,f,c (i)). PUCCH transmission may include UCI. For example, the UE may determine the PUCCH transmission power adjustment component based on the UCI payload size, UCI type (e.g., SR and / or HARQ-ACK and / or CSI), coding gain, coding scheme, and / or effective coding rate. For example, the PUCCH UCI may include a HARQ-ACK codebook.

[0395] PUCCH transmission may include HARQ-ACK information bits. PUCCH transmission may include HARQ-ACK codebook / reports and / or other UL control information, such as SR and / or CSI reports. The UE may determine the PUCCH transmission power adjustment component based on the effective coding rate of the UCI. The UE may determine the PUCCH transmission power adjustment component based on the effective coding rate of the HARQ-ACK codebook / reports. The UE may determine the PUCCH transmission power adjustment component based on multiple (valid / information) HARQ-ACK information bits (e.g., n) in the HARQ-ACK codebook. HARQ-ACK To determine the effective coding rate of the HARQ-ACK codebook / report.

[0396] The UE can determine the HARQ-ACK codebook based on the codebook type configured by the RRC. For example, the configuration parameters can indicate a first-type (e.g., type 2 or dynamic) HARQ-ACK codebook. The UE can determine the size of the (dynamic) HARQ-ACK codebook based on the T-DAI indicated by the last DCI reported by the UE via the HARQ-ACK codebook. The UE can determine the position / location of each HARQ-ACK information bit in the HARQ-ACK codebook based on the corresponding C-DAI indicated by the corresponding DCI, for example, in ascending order of C-DAI values.

[0397] The UE can encode the HARQ-ACK codebook. The encoding mechanism can depend on the size of the UCI in the PUCCH transmission. The encoding mechanism can depend on the format of the PUCCH resources. The encoding mechanism can depend on, for example, including the total HARQ-ACK bits (0...). ACK The size of the HARQ-ACK codebook. The UE can reuse the encoded bits (O) of the HARQ-ACK codebook in the PUCCH resources. ACK (Units digit). The UE can reuse SR(O) in the PUCCH resource. SR ) and / or CSI report (O CSI The encoded bits of ) (if they exist).

[0398] For example, the UE can use a first PUCCH format (e.g., PUCCH format 2, PUCCH format 3, or PUCCH format 4) for PUCCH transmission. PUCCH transmission may include a UCI. The UCI size can be within a first range. For example, the number of UCI bits can be less than or equal to a first number (e.g., 11). For example, the UE can use a first encoding scheme (e.g., RM encoding) to encode the UCI and / or HARQ-ACK codebook. For example, CRC may not be added to the UCI / HARQ-ACK codebook. In the example, the UE can determine the PUCCH transmission power adjustment component as follows: Δ TF,b,f,c (i) = 10log 10 (K1·(n HARQ-ACK (i)+O SR (i)+O CSI (i)) / N RE (i))

[0399] The HARQ-ACK codebook may include the total number of coding bits (O ACK (Units). The UE can determine the number of HARQ-ACK information bits used to determine the transmission power for PUCCH transmission (e.g., n). HARQ-ACK (For example, when the timing of PUCCH transmission is i = n) HARQ-ACK (i)). The HARQ-ACK codebook can be a type 2 / dynamic codebook. The HARQ-ACK codebook can include HARQ-ACK information bits (e.g., n). HARQ-ACKIn addition to the HARQ-ACK information bits, the HARQ-ACK codebook may also include one or more ACK / NACK bits. For example, one or more ACK / NACK bits may include one or more NACK bits, which the UE may generate and / or append to the first HARQ-ACK information corresponding to the first DCI, for example, to align the size / length of the first HARQ-ACK information with the second (e.g., maximum) size / length of the HARQ-ACK information in the codebook. One or more HARQ-ACK information bits may be information / valid bits. The one or more ACK / NACK bits padded to one or more HARQ-ACK information bits may be known / no information / invalid bits. The UE may base its HARQ-ACK information bits (n) on the information bits. HARQ-ACK The count of ACK / NACK bits is used to determine the PUCCH transmission power, and this count is compared with the HARQ-ACK codebook (O) which includes one or more (known) ACK / NACK bits. ACK The total number of digits is relative.

[0400] A radio device can receive multiple DCIs. At least one of the multiple DCIs can schedule the reception of one or more PDSCHs. At least one of the multiple DCIs can schedule / indicate the release of one or more SPS PDSCHs. At least one of the multiple DCIs can schedule / activate the reception of one or more SPS PDSCHs. At least one of the multiple DCIs can instruct one or more SCells on the active DL BWP of the serving cell to sleep. At least one of the multiple DCIs can instruct PUCCH resources for reporting HARQ-ACK feedback associated with multiple DCIs. For example, the UE can transmit HARQ-ACK information for / for multiple DCIs in the (same) PUCCH resources. The UE can determine one or more monitoring opportunities for / for PDCCHs. Configuration parameters can instruct the PDCCH to be associated with one or more DCIs. The UE can receive / detect multiple DCIs from / via one or more monitoring opportunities. The UE can transmit HARQ-ACK information for one or more PDCCH monitoring events, associated with one or more PDCCH monitoring events, or for one or more PDCCH monitoring events within or via the same PUCCH resource. The UE can transmit a HARQ-ACK codebook generated based on a type 2 / dynamic codebook via the PUCCH resource. The HARQ-ACK codebook may include HARQ-ACK information for one or more PDCCH monitoring events.

[0401] In the example, the UE may be configured with TB-based scheduling in the serving cell of the PUCCH cell group. In the example, the UE may not be configured with CBG-based scheduling in the serving cell of the PUCCH cell group (e.g., no CBG-based scheduling is provided to the UE). PDSCH-CodeBlockGroup Transmission for each serving cell in the serving cells. For example, HARQ-ACK information may correspond to PDSCH reception scheduled by a DCI format that does not support CBG-based PDSCH reception. HARQ-ACK information may correspond to SPS PDSCH reception and / or SPS PDSCH release and / or SCell sleep indication. UCI size may be within a first range (e.g., O). ACK +O SR +O CSI ≤11). The UE can determine the number of HARQ-ACK information bits in the Type 2 / Dynamic Codebook used to determine the transmission power for PUCCH transmission as follows (e.g., n). HARQ-ACK ):

[0402]

[0403] HARQ-ACK information bits may include information across one or more (M) monitoring times and one or more (M) monitoring times. The first HARQ-ACK information bits associated with the transport block received by the UE across one or more serving cells. The first HARQ-ACK information bits may include the SPS PDSCH received by the UE across one or more serving cells (N... SPS,c The first HARQ-ACK information bit may include one or more received / detected HARQ-ACK messages in DCI format, indicating the presence of HARQ-ACK messages across one or more (M) monitoring events and one or more The serving cell's SPS PDSCH is released and / or SCell is hibernated.

[0404] Used to determine the number of HARQ-ACK bits in the Type 2 / Dynamic Codebook (e.g., n) HARQ-ACK The first term (left-hand side term) of the above formula: This can correspond to the first HARQ-ACK information bit associated with the received DCI / PDSCH. For example, the UE can base it on one or more (M) monitoring moments associated with PUCCH transmission and one or more (M) monitoring moments associated with PUCCH transmission. The number of HARQ-ACK bits is determined by the first number of DCI formats and / or PDSCHs received by the serving cell.

[0405] The HARQ-ACK codebook may include a second HARQ-ACK information bit associated with a lost DCI (a detected lost PDCCH reception). For example, one or more DCIs may be lost and / or not successfully detected / received.

[0406] Used to determine the number of HARQ-ACK bits in the Type 2 / Dynamic Codebook (e.g., n) HARQ-ACK The second term in the above formula (the term on the right:) This can correspond to the second HARQ-ACK information bits associated with the lost DCI. For example, the UE can base it on a second number of lost DCI formats. Multiply by each lost DCI The number of HARQ-ACK bits is determined by a fixed number of generated HARQ-ACK bits (NACK bits). This term in the formula is based on the 1:1 correspondence between DCI (or PDCCH monitoring timing) and C-DAI values ​​during the DAI counting process, ensuring that the number of lost C-DAI bits is equal to the number of lost DCI bits. Furthermore, based on the specific circumstances of each lost DCI bit... The existing mechanism generates a fixed number of NACK bits. However, it may not be suitable for multi-PDSCH scheduling of DCI, where DCI can schedule multiple PDSCH / downlink assignments, and C-DAI can correspond to the PDSCH / downlink assignment opposite to DCI. In fact, during the DAI counting process, the 1:1 correspondence between DCI and C-DAI values ​​no longer exists, and the number of lost C-DAI is no longer equivalent to the number of lost DCI. Therefore, the existing mechanism may produce erroneous PUCCH power control.

[0407] In some implementations, the UE may receive a DCI format. The DCI may include a DAI field. The DCI format may indicate at least one counter DAI value. The C-DAI value indicated by the DCI format may indicate / represent the cumulative number of pairs of {serving cell, downlink assignment}. The UE may receive one or more DCI formats via one or more monitoring opportunities. One or more DCI formats may indicate the (same) PUCCH resources used for HARQ-ACK feedback transmission. One or more DCI formats may schedule / indicate downlink assignments. Downlink assignments may be / include PDSCH reception. Downlink assignments may be / include SPS PDSCH reception. Downlink assignments may be / include SPS PDSCH release. Downlink assignments may be / include SCell sleep indications. Downlink assignments may be associated with one or more DCI formats received via one or more monitoring opportunities. The C-DAI value may indicate / represent the cumulative number of pairs of {serving cell, downlink assignment} up to (and including) the current serving cell and the current downlink assignment.

[0408] In the example, the DCI format can schedule multiple PDSCHs. The DCI format can include multiple downlink assignments, each scheduling the PDSCH reception. The DCI format can be associated with multiple C-DAI values. For example, each of the multiple C-DAIs can correspond to one of the multiple downlink assignments. The DCI format can include / indicate multiple C-DAIs. The DCI format can indicate at least one of the C-DAIs. The DCI format can indicate the first C-DAI among the multiple C-DAIs. For example, a C-DAI can correspond to the first / earliest downlink assignment / PDSCH among the multiple downlink assignments / PDSCHSs. For example, a C-DAI can correspond to the last downlink assignment / PDSCH among the multiple downlink assignments / PDSCHSs.

[0409] In the example, C-DAI can be counted / incremented in the following order: First, in ascending order of the PDSCH / downlink assignment reception start time scheduled for the same / single DCI. Second, in ascending order of the first PDSCH / downlink assignment reception start time for the same {serving cell, PDCCCH monitoring time} pair, for example, when the UE indicates support for more than one PDSCH reception scheduled from the same PDCCH monitoring time on the serving cell via type2-HARQ-ACK-Codebook. Third, in ascending order of the serving cell index within the same PUCCH cell group and the same PDCCH monitoring time. Fourth, in ascending order of the PDCCH monitoring time index.

[0410] If, for the active DL BWP of the serving cell, the UE is not provided with a coresetPoolIndex, or is provided with a coresetPoolIndex (value 0 for one or more first CORESETs) and is provided with a coresetPoolIndex (value 1 for one or more second CORESETs) and is provided with ackNackFeedbackMode=joint, then for the same serving cell index and the same downlink assignment, the value of the counter DAI is in the order of the first CORESET, followed by the second CORESET.

[0411] In some implementations, the UE may receive a DCI format. The DCI may include a DAI field. The DCI format may indicate at least one total DAI value. The T-DAI value indicated by the DCI format may indicate / represent the total number of {serving cell, downlink assignment} pairs. The T-DAI value may indicate / represent the total number of {serving cell, downlink assignment} pairs up to (and including) the last downlink assignment in the current PDCCH monitoring time. The BS / UE may update the T-DAI between PDCCH monitoring timeframes.

[0412] If, for the active DL BWP of the serving cell, the UE is not provided with a coresetPoolIndex, or is provided with a coresetPoolIndex (value 0 for one or more first CORESETs) and is provided with a coresetPoolIndex (value 1 for one or more second CORESETs) and is provided with ackNackFeedbackMode=joint, then for the first CORESET and the second CORESET, the total DAI value is counted for the {serving cell, downlink assignment} pair.

[0413] In Type 2 / Dynamic Codebook, the UE can determine at least one DCI loss based on gaps detected in the received DAI values ​​(e.g., reference). FIG. 24 For example, if the last DAI (e.g., T-DAI or maximum C-DAI) indication value x received in the first monitoring moment, and the first (e.g., earliest) C-DAI indication value y received in the second monitoring moment after the first monitoring moment, where y > x + 1, then a gap / discontinuity in the DAI counter (e.g., C-DAI = x + 1 lost) is detected, and the UE determines that at least one DCI has been lost. For example, in FIG. 24In the scenario, the UE receives T-DAI=2 during the first monitoring opportunity in time slot n, and C-DAI=4 during the third monitoring opportunity in time slot n+2. The UE determines that DCI (DCI 1) is lost because the UE expected to receive C-DAI=3. The UE can therefore determine that the DCI associated with C-DAI=3 was lost / not received.

[0414] FIG. 24 An example DAI counting procedure according to some implementation schemes is illustrated. The UE may receive configuration parameters indicating two serving cells (cell 0 and cell 1) for the UE. The configuration parameters may indicate that the two serving cells belong to the same PUCCH cell group. The configuration parameters may indicate type 2 / dynamic codebook for the PUCCH cell group. The configuration parameters may indicate that multiple PDSCH scheduling via at least one DCI format is configured for the two serving cells.

[0415] like FIG. 24 As shown, the UE can receive the first DCI via cell 0 during the first PDCCH monitoring time in time slot n. The first DCI can schedule 6 PDSCHs. The first DCI can include a DAI field. The DAI field can indicate the C-DAI of the first PDSCH among multiple PDSCHs (e.g., C-DAI = 1 corresponds to the first / earliest PDSCH). C-DAI can indicate the cumulative number of {serving cell, downlink assignment} pairs up to the first PDSCH (downlink assignment). The UE can determine the C-DAI value for each of the multiple PDSCHs. For example, the UE can determine / assign C-DAI as follows: for the first PDSCH in time slot n: C-DAI = 1, for the second PDSCH in time slot n+1: C-DAI = 2, for the third PDSCH in time slot n+2: C-DAI = 3, for the fourth PDSCH in time slot n+3: C-DAI = 4, for the fifth PDSCH in time slot n+4: C-DAI = 5, and for the sixth PDSCH in time slot n+5: C-DAI = 6. The DAI field in the first DCI can indicate T-DAI, which indicates the total number of {serving cell, downlink assignment} pairs scheduled / indicated up to the last downlink assignment scheduled / indicated in the current PDCCH monitoring time (T-DAI = 10). A T-DAI of 10 received in the first DCI means that a total of 10 downlink assignments are scheduled / indicated via one or more DCIs in this (first) PDCCH monitoring time. The UE receives the first DCI of 6 PDSCH (downlink assignment) schedules. The UE may or may not receive any other DCI format during the first PDCCH monitoring period.

[0416] The BS can transmit DCI 2 via cell 1 during the first PDCCH monitoring time. DCI 2 can include four downlink assignments. For example, DCI 2 can schedule four PDSCHs. The BS can indicate the index for the four downlink assignments via the DAI field in DCI 2. For example, DCI 2 can include C-DAI = 7 corresponding to the first PDSCH scheduled by DCI 2. For example, DCI 2 can include T-DAI = 10, which is consistent with the T-DAI indicated by DCI 1 during the same PDCCH monitoring time.

[0417] exist FIG. 25 In the example, the UE may not receive DCI 2 via cell 1. The UE can determine that 4 C-DAIs (10-6=4) are lost based on the C-DAIs and T-DAIs received via DCI 1 during the first PDCCH monitoring period. The UE can determine that at least one DCI is lost during the first PDCCH monitoring period. However, due to the configuration of multiple PDSCH scheduling (e.g., RRC configuration of a TDRA table for PDSCH, which includes at least one row with multiple valid SLIVs), DCIs can potentially be scheduled for one, two, or more PDSCHs (downlink assignments). Therefore, based on the existing mechanism, the UE may not be able to determine how many DCIs are lost.

[0418] The UE can receive a third DCI (DCI 3) via cell 1 during the second PDCCH monitoring time in time slot n+8. The first DCI and the second DCI can indicate the same PUCCH resource used for HARQ feedback transmission. The UE can generate a HARQ-ACK codebook including HARQ-ACK information associated with the first DCI and the third DCI, and can transmit the HARQ-ACK codebook via PUCCH resource. The third DCI can schedule two PDSCHs. The third DCI can include a DAI field. The DAI field can indicate the C-DAI of the first PDSCH among multiple PDSCHs (e.g., C-DAI = 11 corresponds to the first / earliest PDSCH). The UE can determine the C-DAI value for each of the multiple PDSCHs. For example, the UE can determine / assign the C-DAI as follows: for the first PDSCH in time slot n+8: C-DAI = 11; for the second PDSCH in time slot n+9: C-DAI = 12. The DAI field in the third DCI can indicate the T-DAI, which indicates the total number of {serving cell, downlink assignment} pairs scheduled / indicated up to the last downlink assignment in the current PDCCH monitoring time (T-DAI = 12). A T-DAI of 12 received in the third DCI means that a total of 12 downlink assignments were scheduled / indicated via one or more DCIs up to this (second) PDCCH monitoring time. And since the UE has determined the downlink assignment corresponding to C-DAI = 12, the UE determines that there are no more lost DCI downlink assignments.

[0419] exist FIG. 23A and FIG. 23B In the example, the size of the C-DAI and / or T-DAI fields can be 4 bits. For example, configuration parameters can indicate the size / bit length of the C-DAI and / or T-DAI in the DCI format. The UE can be based on... To determine the C-DAI and T-DAI values. For example... FIG. 25 and FIG. 24 As shown, the UE can be based on (modT) D Use functions to wrap numbers.

[0420] FIG. 24 An example DAI counting procedure according to some implementation schemes is shown. In this example, the UE receives DCI 1 via cell 0 during the first PDCCH monitoring opportunity in time slot n, and receives DCI 4 via cell 1 during the second PDCCH monitoring opportunity in time slot n+8. The received DAI values ​​(C-DAI and T-DAI) and the number of PDSCHs scheduled via each received DCI are compared with... FIG. 24The example in [the previous example] is the same. The UE determines that at least one DCI is lost. However, similar to [the previous example]... FIG. 25 The UE cannot determine how many DCIs are lost.

[0421] Based on the existing PUCCH power control mechanism FIG. 24 and FIG. 25 The examples generate the same HARQ-ACK codebook (as shown in the diagram below), but with different transmission power for PUCCH. For example, in FIG. 24 In the middle, the PUCCH power is determined based on one lost DCI, and in FIG. 25 In this study, PUCCH power is determined based on two missing DCIs.

[0422] FIG. 24 and FIG. 25 The example illustrates that, based on existing mechanisms, when multiple PDSCH scheduling is configured in at least one serving cell and / or when DAI is counted / incremented PDSCH / downlink assignment, the UE may not be able to determine the number of lost DCIs. In both examples, the UE has received the same information; however, in FIG. 26 In the middle, one DCI was lost, while FIG. 26 In this case, two DCIs are lost. Therefore, existing PUCCH power control mechanisms that operate based on the number of lost DCIs may no longer work accurately / effectively.

[0423] The implementation scheme can achieve accurate PUCCH power control determination when multiple PDSCH scheduling is configured for at least one serving cell of a PUCCH cell group.

[0424] In the implementation scheme, the UE can determine the transmission power for a PUCCH transmission timing based on the detected number of lost downlink assignments (e.g., PDSCH). The UE can also determine the number of lost downlink assignments / PDSCHs based on the number of received downlink assignments / PDSCHs. For example, the UE can determine the transmission power for a PUCCH transmission timing, including HARQ-ACK information, based on the number of detected / received downlink assignments (e.g., PDSCH reception) and / or the received DAI value corresponding to the last downlink assignment (e.g., PDSCH). For example, the DAI value can be T-DAI and / or C-DAI. Alternatively, the UE can determine the transmission power for a PUCCH transmission timing based on the number of PDSCHs scheduled by at least one multi-PDSCH scheduling DCI.

[0425] For example, the DAI value can be received in the last PDCCH monitoring opportunity associated with the HARQ-ACK codebook. The UE can determine the PDCCH monitoring opportunity associated with the HARQ-ACK codebook as a uniformity of PDCCH monitoring opportunities across the active DL BWP of the configured serving cells (e.g., in a PUCCH cell group). The UE can determine the monitoring opportunity for PDCCH on the active DL BWP of the serving cell using a DCI format that includes downlink assignments such as scheduling PDSCH reception and / or SPS PDSCH release and / or indicating SCell sleep. The UE can index the PDCCH monitoring opportunity in ascending order of its start time. The cardinality of the PDCCH monitoring opportunity set can limit the total number M of PDCCH monitoring opportunities across the serving cells.

[0426] For example, the DAI value can be received via at least one DCI format detected by the UE during the last PDCCH monitoring period. For example, the DAI value can be received via the minimum DCI format detected by the UE during the last PDCCH monitoring period. For example, the DAI value can be received via the minimum DCI format detected by the UE during the PDCCH monitoring period.

[0427] In the example, the UE can receive configuration parameters indicating one or more serving cells for the UE. The one or more serving cells can belong to the same PUCCH cell group. The UE can be configured with TB-based scheduling in the serving cells of the PUCCH cell group. In the example, the UE may not be configured with CBG-based scheduling in the serving cells of the PUCCH cell group (e.g., no TB-based scheduling is provided to the UE). PDSCH-CodeBlockGroupTransmission for each serving cell in each serving cell.

[0428] The UE can receive one or more DCIs via one or more PDCCH monitoring opportunities of at least one DCI format. The at least one DCI format can be configured for multiple PDSCH scheduling. For example, at least one DCI of one or more DCI formats can schedule multiple PDSCHs. The at least one DCI can include multiple downlink assignments, each scheduling one PDSCH. The one or more DCIs can indicate PUCCH resources used for HARQ-ACK transmission.

[0429] The UE can determine the PUCCH resources used to transmit a HARQ-ACK codebook that includes HARQ-ACK information corresponding to one or more DCIs. The HARQ-ACK information can correspond to all downlink assignments indicated by one or more DCIs. Downlink assignments can be / include PDSCH reception. Downlink assignments can be / include SPS PDSCH reception. Downlink assignments can be / include SPS PDSCH release. Downlink assignments can be / include SCell sleep indications. Downlink assignments can be associated with one or more DCI formats received via one or more monitoring events.

[0430] For example, HARQ-ACK information can correspond to PDSCH reception scheduled by a DCI format that does not support CBG-based PDSCH reception. HARQ-ACK information can correspond to SPS PDSCH reception and / or SPS PDSCH release and / or SCell sleep indication. UCI size can be within a first range (e.g., O). ACK +O SR +O CSI ≤11).

[0431] For example, the UE can determine the number of HARQ-ACK information bits (e.g., n) in the Type 2 / Dynamic Codebook used to determine the transmission power for PUCCH transmission as follows: HARQ-ACK ):

[0432]

[0433] M can be the total number of PDCCH monitoring opportunities associated with the HARQ-ACK codebook (reported via PUCCH transmission). This can be the number of serving cells of the UE associated with the PUCCH cell group.

[0434] A UE can be configured with a single serving cell. For example, a PUCCH cell group may include a single serving cell. The UE can be configured with C-DAI, but may not be configured with T-DAI. For example, configuration parameters can indicate the bit width of the C-DAI field in the DCI format. For example, configuration parameters can indicate that the bit width of the T-DAI field in the DCI format is zero. The DCI format can indicate at least one C-DAI for downlink assignment / PDSCH. The DCI may not indicate T-DAI.

[0435] UE can be based on The value determines the number of HARQ-ACK information bits (n) HARQ-ACKThe UE can determine the value of the counter DAI in the last DCI format detected by the UE within M PDCCH monitoring opportunities. For example, a UE can receive multiple DCIs via one or more (M) PDCCH monitoring opportunities. The last DCI format may or may not be received via the last PDCCH monitoring opportunity. Each of the multiple DCIs may include one or more downlink assignments, such as scheduling one or more PDSCH receptions and / or indicating SPS PDSCH releases and / or indicating SCell sleep for any serving cell c. The last DCI may schedule multiple PDSCH / downlink assignments. In the example, the UE can determine based on the value of the counter DAI. The counter DAI corresponds to the last downlink assignment / PDSCH scheduled by the last DCI format that the UE can detect within M PDCCH monitoring opportunities. In the example, the last DCI may include / indicate the counter DAI corresponding to the last downlink assignment / PDSCH. In the example, the counter DAI in the last DCI may correspond to the first PDSCH / downlink assignment scheduled / indicated by the last DCI. The UE can determine the counter DAI based on the first (e.g., earliest) PDSCH indicated by the last DCI and the number of PDSCHs scheduled by the last DCI.

[0436] FIG. 26An example of DAI counting in a single serving cell according to some implementation schemes is shown. The UE receives DCI 1 in the first PDCCH monitoring opportunity in time slot n. DCI 1 can schedule 6 PDSCHs. DCI 1 may include a C-DAI field indicating the C-DAI of one of the 6 PDSCHs. For example, the C-DAI in DCI 1 may correspond to the first PDSCH (C-DAI = 1). In another example not shown in this figure, the C-DAI in DCI 1 may correspond to the last PDSCH (C-DAI = 6). The UE can determine the C-DAI value corresponding to the remaining PDSCHs (e.g., PDSCH 2 to PDSCH 6) by incrementing the indicated C-DAI of PDSCH 1. The UE may lose DCI 2 in the second PDCCH monitoring opportunity. The UE may receive DCI 3 in the third PDCCH monitoring opportunity in time slot n+12. DCI 3 can schedule 2 PDSCHs. DCI 3 may include a C-DAI field indicating the C-DAI of one of the two PDSCHs. For example, the C-DAI in DCI 3 may correspond to the first PDSCH (C-DAI = 9). In another example not shown in this figure, the C-DAI in DCI 3 may correspond to the last PDSCH (C-DAI = 10). The UE can determine the C-DAI value corresponding to the remaining PDSCHs by incrementing the indicated C-DAI.

[0437] The UE can determine at least one DCI loss, including one or more downlink assignments and / or scheduling of one or more PDSCHs, based on the received C-DAI value and the number of PDSCHs scheduled by each received DCI. For example, in FIG. 26 In this case, the UE can determine that it has not received a downlink assignment / PDSCH associated with C-DAI=7C-DAI=8.

[0438] The UE can determine the value of the counter DAI corresponding to the last downlink assignment / PDSCH scheduled by DCI 3. exist FIG. 26 In the example, DCI 3 (the last DCI) indicates that C-DAI = 9 for the first scheduled PDSCH. The UE determines that C-DAI = 10 for the last PDSCH scheduled by DCI 3. Therefore, the UE determines...

[0439] UE can be based on The value determines the number of HARQ-ACK information bits (n) HARQ-ACKThe UE can determine the total number of downlink assignments / PDSCHs scheduled by one or more DCIs. DAI,c The UE can detect one or more DCIcs within M PDCCH monitoring periods for the serving cell. Each DCIc can include one or more downlink assignments. Downlink assignments can instruct PDSCH reception and / or SPS PDCCH reception and / or SPS PDSCH release and / or SCell sleep. The UE can detect one or more DCIcs based on one or more (… The sum of the total downlink assignments scheduled / indicated / received by the serving cell within a total of M PDCCH monitoring periods determines the number of serving cells. In the example, if the UE does not detect any DCI format for scheduling PDSCH reception, indicating SPSPDSCH release, or indicating SCell sleep for serving cell c in any of the M PDCCH monitoring opportunities, then the U DAI,c =0.

[0440] UE can be based on To determine the C-DAI and T-DAI values.

[0441] The UE can determine the number of codewords configured in the PDSCH and / or whether a spatial cluster is configured in at least one serving cell. For example, if the configuration parameter indicates that the value of maxNrofCodeWordsScheduledByDCI for any serving cell c is 2 and / or no spatial bundle is configured (e.g., no harq-ACK-SpatialBundlingPUCCH is provided), then For example, if the configuration parameter indicates that the value of maxNrofCodeWordsScheduledByDCI for any serving cell c is 2 and / or spatial bundling is configured (e.g., harq-ACK-SpatialBundlingPUCCH is not provided), then For example, if the configuration parameter indicates that the value of maxNrofCodeWordsScheduledByDCI is 1 for any serving cell c, then

[0442] The UE can determine the number of transport blocks received in the PDSCH scheduled by the DCI format detected by the UE during the PDCCH monitoring time m for serving cell c. For example, harq-ACK-SpatialBundling PUCCH may not be provided / configured. The UE can determine the number of DCI-formatted PDSCHs detected by the UE during PDCCH monitoring time m for serving cell c. For example, harq-ACK-SpatialBundlingPUCCH can be configured / provided. The UE can determine the appropriate DCI format based on the number of DCI formats detected by the UE. Furthermore, the SPS PDSCH release is indicated during the PDCCH monitoring timing m for serving cell c. The UE can determine the number of DCI formats detected by the UE based on this information. Furthermore, during the PDCCH monitoring time m for serving cell c, the SCell is instructed to hibernate.

[0443] The UE can determine N based on the SPS PDSCH received by the UE in serving cell c. SPS,c For this serving cell, the UE transmits the corresponding HARQ-ACK information SPS in the same PUCCH as the HARQ-ACK information received by the PDSCH within the M PDCCH monitoring periods.

[0444] for FIG. 24 For example, the UE can determine

[0445]

[0446] It is equivalent to targeting such FIG. 24 The bottom shows the HARQ-ACK codebook and the number of bits generated in that codebook (6 bits + 2 bits + 2 bits = 10 bits). Readers can confirm that the proposed implementation produces accurate calculations for PUCCH power determination, while the old (traditional) mechanism produces incorrect calculations.

[0447] A UE can be configured with multiple serving cells. For example, a PUCCH cell group can include multiple serving cells. The UE can be configured with C-DAI and T-DAI. For example, configuration parameters can indicate the bit width of the C-DAI field in the DCI format. Similarly, configuration parameters can indicate the bit width of the T-DAI field in the DCI format. The DCI format can indicate at least one C-DAI used for downlink assignment / PDSCH. The DCI can also indicate a T-DAI.

[0448] UE can be based on The value determines the number of HARQ-ACK information bits (n) HARQ-ACKThe UE can determine the total DAI value in at least one DCI format detected by the UE within the last PDCCH monitoring timeout of M PDCCH monitoring timeouts. For example, a UE can receive multiple DCIs via one or more (M) PDCCH monitoring opportunities. Each DCI may include one or more downlink assignments, such as scheduling one or more PDSCH receptions for any serving cell c and / or indicating SPS PDSCH release and / or indicating SCell sleep. For example, a UE may detect / receive at least one DCI format / DCI in the last PDCCH monitoring opportunity. The at least one DCI / DCI format may include a T-DAI field. The at least one DCI format may indicate the T-DAI associated with the last downlink assignment / PDSCH scheduled via the last PDCCH monitoring opportunity. The UE may determine the T-DAI based on the last received T-DAI within the M PDCCH monitoring opportunities. The UE can determine the number of PDSCH / downlink assignments scheduled by at least one DCI format. For example, the UE can determine the total DAI value in at least one DCI format and the number of PDSCH / downlink assignments scheduled by at least one DCI format. For example, the UE can receive / detect at least one DCI format including / indicating the T-DAI field in the last PDCCH monitoring time within M PDCCH monitoring times associated with the HARQ-ACK codebook.

[0449] In the example, the UE can determine based on the total DAI value. The counter DAI corresponds to the last downlink assignment / PDSCH scheduled by at least one DCI format detected by the UE in the last PDCCH monitoring time within M PDCCH monitoring times. In the example, at least one DCI may include / indicate the total DAI corresponding to the last downlink assignment / PDSCH scheduled by at least one DCI. In the example, the total DAI in at least one DCI may correspond to the first PDSCH / downlink assignment scheduled / indicated by at least one DCI. The UE may determine the total DAI based on the first (e.g., earliest) PDSCH indicated by at least one DCI and the number of PDSCHs scheduled by at least one DCI.

[0450] The UE can determine the total DAI value in the last DCI format detected by the UE within M PDCCH monitoring opportunities. For example, a UE can receive multiple DCIs via one or more (M) PDCCH monitoring opportunities. The last DCI format may or may not be received via the last PDCCH monitoring opportunity. Each of the multiple DCIs may include one or more downlink assignments, such as scheduling one or more PDSCH receptions and / or indicating SPS PDSCH release and / or indicating SCell sleep for any serving cell c. The last DCI may schedule multiple PDSCH / downlink assignments. In the example, the UE can determine based on the value of the total DAI. The counter DAI corresponds to the last downlink assignment / PDSCH scheduled by the last DCI format that the UE can detect within M PDCCH monitoring opportunities. In the example, the last DCI may include / indicate the total DAI corresponding to the last downlink assignment / PDSCH. In the example, the total DAI in the last DCI may correspond to the first PDSCH / downlink assignment scheduled / indicated by the last DCI. The UE can determine the total DAI based on the first (e.g., earliest) PDSCH indicated by the last DCI and the number of PDSCHs scheduled by the last DCI.

[0451] In the example, the UE may not receive / detect any DCI format in the last PDCCH monitoring timeout of the M PDCCH monitoring times. For example, the UE may not receive / detect any DCI format that includes / indicates the T-DAI field. The UE can receive at least one DCI via the M PDCCH monitoring times. Each of the at least one DCI may include one or more downlink assignments, such as scheduling one or more PDSCH receptions for any serving cell c and / or indicating SPS PDSCH release and / or indicating SCell sleep. This at least one DCI may not include / indicate the T-DAI field. In the example, one or more of the at least one DCIs received via the last PDCCH monitoring timeout may not include / indicate the T-DAI field. The UE can determine based on the value of C-DAI. For example, the last received DCI can indicate the C-DAI. For instance, the UE can determine the C-DAI based on the value indicated by the last DCI. The UE can receive the last DCI in the last PDCCH monitoring time out of M PDCCH monitoring times. For example, DCIs can be indexed / sorted in ascending order of serving cell index for the same PDCCH monitoring time, followed by ascending order of PDCCH monitoring time index. The last DCI can be received via the highest serving cell index in the last (most recent) PDCCH monitoring time. The UE can determine the C-DAI based on the first (e.g., earliest) PDSCH / downlink assignment indicated by the last DCI and the number of PDSCH / downlink assignments scheduled by the last DCI.

[0452] exist FIG. 24 In the example, the UE can determine the T-DAI (T-DAI=12) received via DCI 3 during the second (last) PDCCH monitoring session. for FIG. 25 For example, the UE can determine

[0453]

[0454] It is equivalent to targeting such FIG. 25 The bottom shows the HARQ-ACK codebook / the number of bits generated in the HARQ-ACK codebook (6 bits + 4 bits + 2 bits = 12 bits).

[0455] exist FIG. 24 In the example, the UE can determine the T-DAI (T-DAI=12) received via DCI 4 during the second (last) PDCCH monitoring session. for FIG. 27 For example, the UE can determine

[0456]

[0457]

[0458] It is equivalent to targeting such ​ The bottom shows the HARQ-ACK codebook / the number of bits generated in the HARQ-ACK codebook (6 bits + 4 bits + 2 bits = 12 bits).

[0459] In the example above, For example, the configuration parameter could indicate that the value of maxNrofCodeWordsScheduledByDCI is 2 for any serving cell c and / or that spatial bundling is configured (e.g., harq-ACK-SpatialBundlingPUCCH is not provided). Alternatively, the configuration parameter could indicate that the value of maxNrofCodeWordsScheduledByDCI is 1 for any serving cell c.

[0460] In the example, the UE can determine the number of HARQ-ACK information bits (e.g., n) in the Type 2 / Dynamic Codebook used to determine the transmission power for PUCCH transmission as follows: HARQ-ACK ):

[0461]

[0462] UE can be based on The value determines the number of HARQ-ACK information bits (n) HARQ-ACK The UE can determine the total number of downlink assignments / PDSCH / TB scheduled by DCI format 1. DAI,c,l The UE can detect one or more (U) cells within M PDCCH monitoring opportunities assigned to the serving cell c, including one or more downlink assignments. DAI,c Each DCI may include one or more downlink assignments. Downlink assignments may instruct PDSCH reception and / or SPS PDSCH reception and / or SPS PDSCH release and / or SCell sleep. The UE may determine the total number of downlink assignments / PDSCHs scheduled / instructed by the DCI format l for the serving cell c. The UE can receive DCI format l via one of the M PDCCH monitoring opportunities. The UE can receive DCI format l based on one or more (… The total number of downlink assignments scheduled / instructed / received within the total M PDCCH monitoring time of the serving cell is used to determine the determination. In the example, if the UE does not detect any DCI format for scheduling PDSCH reception, indicating SPS PDSCH release, or indicating SCell sleep in any of the M PDCCH monitoring opportunities, then the U DAI,c =0.

[0463] In the example, the UE can base its data on the number of DCIs received during M monitoring events across serving cell c and a first parameter (e.g., N). conf ) determines the number n of HARQ-ACK bits used to obtain the transmission power for PUCCH.HARQ-ACK The first parameter can be predefined. The UE can determine the first parameter based on one or more second parameters (e.g., subcarrier spacing) indicated by the RRC. The RRC can indicate the first parameter. For example, the first parameter can be configured by the RRC. In the example, the UE can determine the first parameter based on information received via one or more DCIs. For example, the UE can determine the first parameter as the average number of downlink assignments / PDSCHs scheduled by the DCI (e.g., for the same serving cell or across all serving cells). In the example, the first parameter can be the maximum number of schedulable PDSCHs in DCI format indicated by a row in the TDRA table indicated by the RRC configuration parameters. In the example, the UE can determine the first parameter as the average number of schedulable PDSCHs in DCI format based on the row / entry of the TDRA table indicated by the RRC configuration parameters. The first parameter can be the maximum number of schedulable PDSCHs in DCI format. In the example, the first parameter can be the time-domain bundle size configured / defined for HARQ-ACK reports for multiple PDSCHs. In the example, the first parameter can be indicated by the last DCI, such as the number of PDSCH / downlink assignments scheduled by the last DCI (e.g., received by / for the same serving cell).

[0464] In the example, the UE can determine the number n of HARQ-ACK information bits based on the following: HARQ-ACK :

[0465]

[0466] For example, U DAI,c It can be the total number of DCI formats detected by the UE within M PDCCH monitoring opportunities for the serving cell c (e.g., scheduling single and / or multiple PDSCH receptions).

[0467] In the example, the UE can determine the number n of HARQ-ACK information bits based on the following: HARQ-ACK :

[0468]

[0469] For example, U DAI,c This can be the total number of DCI formats detected by the UE within M PDCCH monitoring opportunities for serving cell c (e.g., scheduling single and / or multiple PDSCH receptions). For example, N cont,c It can be the first parameter for the serving cell c (e.g., configured / defined for each cell).

[0470] In the example, the UE can determine the number n of HARQ-ACK information bits based on the following: HARQ-ACK :

[0471]

[0472] For example, U DAI,c This can be the total number of DCI formats detected by the UE within M PDCCH monitoring opportunities for serving cell c (e.g., scheduling single and / or multiple PDSCH receptions). For example, It can be the normalized value of the first parameter. (e.g. N) conf For example, the UE can determine...

[0473] In the example, the UE can receive configuration parameters that indicate how to configure CBG-based scheduling for one or more serving cells. For example, it can be configured to... Each serving cell provides PDSCH-CodeBlockGroup Transmission. For example, the PUCCH cell group (total) Other serving cells (of the given cells) may not be configured with CBG-based scheduling. For example, they may not be. Each serving cell provides PDSCH-CodeBlockGroup Transmission, among which In the example, at least one of one or more serving cells configured with CBG-based scheduling can be configured for multi-PDSCH scheduling. For example, configuration parameters (such as TRDA tables) can indicate that the DCI format is compatible with... Multiple PDSCHs are scheduled for each serving cell.

[0474] The UE can determine the first HARQ-ACK subcodebook for / including the following: On each service community and SPS PDSCH reception / release and / or SCell sleep indication and / or TB-based scheduling / PDSCH reception on a serving cell (e.g., any serving cell). The UE can determine a first number (e.g., n) of HARQ-ACK information bits for the first HARQ-ACK subcodebook. HARQ-ACK,TB ).

[0475] UE can determine for / including The second HARQ-ACK codebook for HARQ-ACK information received by PDSCH based on CBG on each serving cell. Each serving cell can be configured with multiple PDSCH scheduling. For example, a UE can receive PDSCH scheduling for... A serving cell within a serving cell schedules DCIs for multiple PDSCHs (Downlink Assignments), where each PDSCH may include one or more CBGs. The UE can generate DCIs for each downlink assignment. One HARQ-ACK information bit (e.g., PDSCH), in which It is across all Maximum value of each serving cell and This refers to the value of maxNrofCodeWordsScheduledByDCI for the serving cell c. For example, if for the serving cell c, this value is... Then the UE can target the subsequent cells of serving cell c. One HARQ-ACK bit is used to generate a NACK.

[0476] The counter DAI value and the total DAI value are applied to each of the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook, respectively. The UE can generate a HARQ-ACK codebook by appending the second HARQ-ACK subcodebook to the first HARQ-ACK subcodebook.

[0477] The UE can determine the total number n of HARQ-ACK information bits used to obtain the PUCCH transmission power, including the HARQ-ACK codebook. HARQ-ACK =n HARQ-ACK,TB +n HARQ-ACK,CBG .

[0478] For example, the UE can determine the number of HARQ-ACK information bits (e.g., n) in the Type 2 / Dynamic Codebook used to determine the transmission power for PUCCH transmission as follows: HARQ-ACK,CBG ):

[0479]

[0480] M can be the total number of PDCCH monitoring opportunities associated with the HARQ-ACK codebook (reported via PUCCH transmission). It can be the total number of serving cells of the UE associated with the PUCCH cell group. This can be the number of serving cells configured with CBG-based scheduling.

[0481] A UE can be configured with a single serving cell. For example, a PUCCH cell group may include a single serving cell. The UE can be configured with C-DAI, but may not be configured with T-DAI. For example, configuration parameters can indicate the bit width of the C-DAI field in the DCI format. For example, configuration parameters can indicate that the bit width of the T-DAI field in the DCI format is zero. The DCI format can indicate at least one C-DAI for downlink assignment / PDSCH. The DCI may not indicate T-DAI.

[0482] UE can be based on The value determines the number of HARQ-ACK information bits (n) HARQ-ACK,CBG The UE can determine the value of the counter DAI in the last DCI format detected by the UE within M PDCCH monitoring opportunities. The last DCI format can be the last DCI format for serving cell scheduling based on CBG PDSCH reception. For example, the UE can receive multiple DCIs for scheduling CBG-based PDSCH reception via one or more (M) PDCCH monitoring opportunities. The last DCI format may or may not be received via the last PDCCH monitoring opportunity. Each of the multiple DCIs can include / indicate one or more downlink assignments / PDSCHs. The last DCI can schedule multiple PDSCHs / downlink assignments. In the example, the UE can determine the last DCI based on the value of the counter DAI. The counter DAI corresponds to the last downlink assignment / PDSCH scheduled in the last DCI format of the PDSCH received based on CBG, which can be detected by the UE within M PDCCH monitoring opportunities. In the example, the last DCI may include / indicate the counter DAI corresponding to the last downlink assignment / PDSCH. In the example, the counter DAI in the last DCI may correspond to the first PDSCH / downlink assignment scheduled / indicated by the last DCI. The UE can determine the number of PDSCHs scheduled by the last DCI based on the counter DAI of the first (e.g., earliest) PDSCH indicated by the last DCI.

[0483] The UE can determine based on the value of the counter DAI. The counter DAI corresponds to the last downlink assignment / PDSCH scheduled by the last CBG-based scheduling DCI within M PDCCH monitoring periods.

[0484] A UE can be configured with multiple serving cells. For example, a PUCCH cell group can include multiple serving cells. The UE can be configured with C-DAI and T-DAI. For example, configuration parameters can indicate the bit width of the C-DAI field in the DCI format. Similarly, configuration parameters can indicate the bit width of the T-DAI field in the DCI format. The DCI format can indicate at least one C-DAI used for downlink assignment / PDSCH. The DCI can also indicate a T-DAI.

[0485] UE can be based on The value determines the number of HARQ-ACK information bits (n) HARQ-ACK,CBG The UE can determine the total DAI value in the first CBG-based scheduling DCI format detected by the UE within M PDCCH monitoring opportunities. The first DCI format can be the last received DCI format of one or more CBG-based PDSCH receptions for (any) serving cell, received by the UE via M PDCCH monitoring opportunities. For example, the UE can receive multiple DCIs via one or more (M) PDCCH monitoring opportunities. Each of the multiple DCIs can include / schedule / indicate one or more downlink assignments / PDSCHs. For example, the UE can detect / receive the first DCI format / DCI in the last PDCCH monitoring opportunity. The first DCI / DCI format can include a T-DAI field. The first DCI format can indicate the T-DAI associated with the last downlink assignment / PDSCH scheduled via the last PDCCH monitoring opportunity. The UE can determine the T-DAI based on the last T-DAI received via CBG-based scheduling DCI within the M PDCCH monitoring opportunities. The UE can determine the number of PDSCH / downlink assignments based on the format scheduled by the first / last DCI using CBG. For example, the UE can determine the total DAI value in the first / last CBG-based DCI format and the number of PDSCH / downlink assignments scheduled by the first / last CBG-based DCI format. For example, the UE can receive / detect the first / last CBG-based DCI format including / indicating the T-DAI field in the last PDCCH monitoring time within M PDCCH monitoring times associated with the HARQ-ACK codebook.

[0486] In the example, the UE may not receive / detect any DCI format for CBG-based PDSCH reception for (any) serving cell scheduling in any of the M PDCCH monitoring opportunities. The UE may receive at least one DCI via the M PDCCH monitoring opportunities. In the example, at least one DCI received via the M PDCCH monitoring opportunities may not schedule CBG-based PDSCH. The UE can determine

[0487] UE can be based on The value determines the number of HARQ-ACK information bits (n) HARQ-ACK,CBG The UE can determine the total number of downlink assignments / PDSCHs scheduled by one or more DCIs based on CBG. The UE can detect one or more CBG-based scheduling DCIs within M PDCCH monitoring periods for the serving cell. Each DCI can schedule one or more downlink assignments / PDSCHs, each including one or more CBGs. Each DCI can include / schedule one or more downlink assignments / PDSCHs. Each PDSCH can include one or more CBGs. The UE can receive one or more CBG-based scheduling DCIs within M PDCCH monitoring periods for the serving cell c. The UE can receive one or more (…) CBG-based scheduling DCIs across the configured CBG-based PDSCHs. The total number of downlink assignments / PDSCHs scheduled / indicated / received by the serving cell within a total of M PDCCH monitoring periods determines the number of serving cells. In the example, if the UE does not detect any DCI format for CBG-based PDSCH reception for serving cell c scheduling in any of the M PDCCH monitoring opportunities, then

[0488] Configuration parameters can indicate the bit width (e.g., C) for the C-DAI field in the DCI format. DAI (bit length). UE can be based on To determine the C-DAI and T-DAI values.

[0489] UE can be based on all Maximum value of each serving cell Determine This could be the number of codewords configured in the PDSCH for serving cell c (e.g., the value of maxNrofCodeWordsScheduledByDCI). For example, the UE could determine this based on the number of codewords configured in the PDSCH and / or whether spatial clustering is configured in at least one serving cell. For example, if the configuration parameter indicates that the value of maxNrofCodeWordsScheduledByDCI for any serving cell c is 2 and / or no spatial bundle is configured (e.g., no harq-ACK-SpatialBundlingPUCCH is provided), then For example, if the configuration parameter indicates that the value of maxNrofCodeWordsScheduledByDCI for any serving cell c is 2 and / or spatial bundling is configured (e.g., harq-ACK-SpatialBundlingPUCCH is not provided), then For example, if the configuration parameter indicates that the value of maxNrofCodeWordsScheduledByDCI is 1 for any serving cell c, then

[0490] The UE can determine the maximum number of CBGs used to generate the corresponding HARQ-ACK information bits for transport block reception for the serving cell, for example, based on the RRC parameter maxCodeBlockGroupsPerTransportBlock.

[0491] The UE can determine the number of CBGs received by the UE in one or more PDSCHs scheduled by the DCI format. The DCI format supports CBG-based PDSCH reception / scheduling. The UE can detect the DCI format during PDCCH monitoring time m for serving cell c. The UE can report HARQ-ACK information corresponding to the CBG and / or DCI formats in / via PUCCH.

[0492] In this implementation, the wireless device can receive multiple downlink control information (DCIs). At least one of the multiple DCIs can schedule multiple physical downlink shared channels (PDSCHs). The wireless device can determine the number of bits in the hybrid automatic repeat request acknowledgment (HARQ-ACK) information corresponding to the multiple DCIs. The wireless device can determine the number of bits based on the count of the multiple PDSCHs and / or the value indicated by the first DCI of the multiple DCIs. This value can indicate the total number of downlink assignments via the multiple DCIs.

[0493] Multiple DCIs can be received on one or more serving cells of a radio device. The multiple DCIs may include one or more downlink assignments for one or more serving cells of the radio device. Downlink assignments may include / indicate PDSCH receive and / or semi-persistent scheduling (SPS) PDSCH release and / or semi-persistent scheduling (SPS) PDSCH receive and / or secondary cell sleep indication. At least one of the multiple DCIs may indicate PUCCH resources for the transmission of HARQ-ACK information. The radio device can determine one or more monitoring times for the Physical Downlink Control Channel (PDCCH) that includes multiple DCIs across one or more serving cells of the radio device.

[0494] This value can be the Total Downlink Assignment Index (DAI), which indicates the first total number of serving cells and downlink assignments indicated by multiple DCIs across one or more monitoring times across serving cells and across PDCCHs. The first DCI, including the total DAI, can be received in the last monitoring time of one or more monitoring times of the PDCCHs. The radio device can determine this value based on the counter Downlink Assignment Index (DAI) indicated by the first DCI. The counter DAI can indicate the cumulative number of serving cells and downlink assignments indicated by multiple DCIs across one or more monitoring times across serving cells and across PDCCHs up to the current monitoring time associated with the first DCI. The radio device can determine this value based on a second number of PDSCHs scheduled by the first DCI, where the first DCI can be the last of the multiple DCIs.

[0495] Wireless devices can determine the power used to transmit HARQ-ACK information via the Physical Uplink Control Channel (PUCCH) resource based on the number of bits. The wireless device can then use this power to transmit HARQ-ACK information via the PUCCH resource.

[0496] In the example, configuration parameters can instruct C-DAI and / or T-DAI to be counted / incremented for each DCI format. The UE can receive DCI / DCI formats. Multiple PDSCHs can be scheduled for the DCI. The DCI may include DAI fields indicating C-DAI and / or T-DAI values.

[0497] A wireless device can receive multiple DCIs. These multiple DCIs can be based on one or more DCI formats (e.g., DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 and / or DCI format 1_3). At least one of the multiple DCIs can indicate a PUCCH resource for reporting HARQ-ACK feedback associated with the multiple DCIs. For example, the UE can transmit HARQ-ACK information for / for multiple DCIs in the (same) PUCCH resource. For example, the at least one DCI may include a slot offset (e.g., a PDSCH-to-HARQ_feedback timing indicator field) that indicates the slot including the PUCCH resource based on a first slot. The first slot may be a DL slot corresponding to receiving at least one DCI. The first slot may be a DL slot for receiving a first PDSCH scheduled by at least one DCI.

[0498] The UE can determine one or more monitoring times for / to the PDCCH. Configuration parameters can indicate that the PDCCH is associated with one or more DCI formats. For example, one or more monitoring times for the PDCCH can be configured with one or more DCI formats. The UE can receive / detect multiple DCIs from / via one or more monitoring times.

[0499] The UE can transmit HARQ-ACK information for one or more PDCCH monitoring events, associated with one or more PDCCH monitoring events, or for one or more PDCCH monitoring events in (the same) PDCCH resource or via (the same) PDCCH resource.

[0500] One ...

Claims

1. A method for power control adjustment of PUCCH using multi-PDSCH scheduling, comprising: Receive configuration parameters for each of one or more cells, the configuration parameters indicating the maximum number of time-domain resource allocations (TDRAs) for the Physical Downlink Shared Channel (PDSCH) for the respective cells in the one or more cells; For each of the one or more cells, the maximum number of TDRAs for that cell is multiplied by the corresponding number of codewords for that cell to produce the corresponding TDRA multiplier. Determine the maximum value of the TDRA multiplier across the one or more cells; and Feedback information is transmitted via the Physical Uplink Control Channel (PUCCH) at a transmission power determined based on the maximum value.

2. The method of claim 1, further comprising: To determine the PUCCH transmission power, the number of bits in the feedback information is determined.

3. The method of claim 2, wherein the number of bits in the feedback information includes the first number of bits in the first feedback information, wherein: The feedback information includes the first feedback information; and The first feedback information is associated with one or more undetected DCIs.

4. The method of claim 2, further comprising: The number of digits is determined based on the maximum value.

5. The method of claim 3, further comprising: The number of bits is determined based on the number of one or more undetected DCIs across the one or more cells.

6. The method of claim 3, further comprising: The number of the one or more undetected DCIs is determined based on the difference between the received downlink assignment index (DAI) value and the number of one or more received DCIs across the one or more cells.

7. The method of claim 3, further comprising: The number of bits is determined based on the product of the number of the one or more undetected DCIs and the maximum value.

8. The method of claim 2, further comprising receiving one or more DCIs, wherein each of the one or more DCIs schedules multiple PDSCHs for cells in the one or more cells.

9. The method of claim 8, wherein the number of the plurality of PDSCHs scheduled by DCI for the cell is equal to or less than the corresponding maximum time-domain resource allocation number for the PDSCHs used for the cell.

10. The method of claim 8, wherein the feedback information further includes second feedback information associated with one or more received DCIs.

11. The method of claim 8, wherein the number of bits in the feedback information includes the second number of bits in the second feedback information.

12. The method of claim 11, further comprising: The second bit is determined based on the total number of PDSCHs or transport blocks scheduled across the one or more cells by the one or more DCIs.

13. The method of claim 8, wherein at least one of the one or more DCIs indicates a downlink assignment index (DAI) value.

14. The method of claim 8, wherein the configuration parameter further indicates the maximum number of codewords for a given cell among the one or more cells.

15. The method of claim 8, further comprising: Generate a hybrid automatic repeat request acknowledgment (HARQ-ACK) subcodebook that includes the feedback information, wherein the feedback information includes HARQ-ACK information corresponding to multiple PDSCH receptions scheduled by a single downlink control information (DCI) for one or more of the cells.

16. The method of claim 15, wherein the HARQ-ACK subcodebook includes at least one negative acknowledgment (NACK) for at least the last HARQ-ACK information bit of a cell having a first value less than the maximum value of the first value across the one or more cells.

17. The method of claim 15, wherein the total number of HARQ-ACK information bits in the HARQ-ACK subcodebook is equal to or greater than the number of bits in the feedback information determined for the PUCCH transmission power.

18. The method of claim 15, further comprising transmitting the HARQ-ACK subcodebook in the PUCCH.

19. A wireless device, comprising: One or more processors; as well as A memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform a process including: Receive configuration parameters for each of one or more cells, the configuration parameters indicating the maximum number of time-domain resource allocations (TDRAs) for the Physical Downlink Shared Channel (PDSCH) for the respective cells in the one or more cells; For each of the one or more cells, the maximum number of TDRAs for that cell is multiplied by the corresponding number of codewords for that cell to produce the corresponding TDRA multiplier. Determine the maximum value of the TDRA multiplier across the one or more cells; and Feedback information is transmitted via the Physical Uplink Control Channel (PUCCH) at a transmission power determined based on the maximum value.

20. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a process comprising: Receive configuration parameters for each of one or more cells, the configuration parameters indicating the maximum number of time-domain resource allocations (TDRAs) for the Physical Downlink Shared Channel (PDSCH) for the respective cells in the one or more cells; and For each of the one or more cells, the maximum number of TDRAs for that cell is multiplied by the corresponding number of codewords for that cell to produce the corresponding TDRA multiplier. Determine the maximum value of the TDRA multiplier across the one or more cells; and Feedback information is transmitted via the Physical Uplink Control Channel (PUCCH) at a transmission power determined based on the maximum value.

Images