Apparatus for user equipment and base station

Abstract

The present disclosure relates to an apparatus for a user equipment and a base station. An apparatus, system and method of a base station are disclosed. The apparatus comprises: a memory; and processing circuitry configured to: determine a physical downlink control channel (PDCCH) on a first component carrier; encode a first signal to be transmitted on the PDCCH, the first signal comprising downlink control information (DCI) about resources for a second signal to be transmitted on a second component carrier, wherein the DCI is based on a predetermined numerology, and wherein respective numerologies of the first component carrier and the second component carrier are different from each other. The processing circuitry is further configured to cause the first signal to be transmitted on the PDCCH, wherein a receiver of the second signal processes the second signal based on the control information in the first signal.

Description

[0001] This application is a divisional application of Chinese patent application No. 2018800202461, filed on March 22, 2018, entitled "Scheduling and Hybrid Automatic Repeat Request Operation and Codebook Design for New Radio Carrier Aggregation".

[0002] Cross-references to related applications

[0003] This application claims the benefit and priority of U.S. Provisional Patent Application No. 62 / 475,475, filed March 23, 2017, entitled “Scheduling And Hybrid Automatic Repeat Request Operation For Carrier Aggregation With Mixed Numerologies”, and U.S. Provisional Patent Application No. 62 / 476,053, filed March 24, 2017, entitled “Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) Codebook Design For New Radio (NR) Carrier Aggregation (CA)”, the entire disclosure of which is incorporated herein by reference. Technical Field

[0004] This disclosure generally relates to the use of new air interface carrier aggregation that uses the same or mixed set of parameters between component carriers. Background Technology

[0005] Wireless mobile communication technologies use various standards and protocols to transmit data between nodes (e.g., transmission stations) and wireless devices (e.g., mobile devices). Some wireless devices use Orthogonal Frequency Division Multiple Access (OFDMA) for downlink (DL) transmission and Single Carrier Frequency Division Multiple Access (SC-FDMA) for uplink (UL) transmission. Standards and protocols that use Orthogonal Frequency Division Multiplexing (OFDM) for signal transmission include 3GPP Long Term Evolution (LTE) and New Radio (NR), IEEE 802.16 standards (e.g., 802.16e, 802.16m) (commonly referred to in the industry as WiMAX (Global Microwave Access Interoperability)), and IEEE 802.11 standards (commonly referred to in the industry as Wi-Fi).

[0006] In 3GPP Radio Access Network (RAN) Long Term Evolution (LTE) and NR systems, a node can be a combination of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as Evolved Node B, Enhanced Node B, eNodeB, or eNB) and a Radio Network Controller (RNC), which communicates with radio equipment called User Equipment (UE). Downlink (DL) transmissions can be communication from a node (e.g., eNodeB) to a radio equipment (e.g., UE), while uplink (UL) transmissions can be communication from a radio equipment to a node.

[0007] In LTE and NR, data can be transmitted from the eNodeB to the UE via the Physical Downlink Shared Channel (PDSCH). The Physical Downlink Control Channel (PDCCH) can be used to provide control information about the downlink PDSCH. The Physical Uplink Control Channel (PUCCH) can be used to acknowledge received data. Downlink and uplink channels or transmissions can use Time Division Duplex (TDD) or Frequency Division Duplex (FDD). Time Division Duplex (TDD) applies Time Division Multiplexing (TDM) to separate downlink and uplink signals. In TDD, downlink and uplink signals can be carried on the same carrier frequency (i.e., a shared carrier frequency), where the downlink signal uses a different time interval than the uplink signal, so the downlink and uplink signals do not interfere with each other. Frequency Division Multiplexing (FDM) is a type of digital multiplexing in which two or more bit streams or signals (e.g., downlink or uplink) are ostensibly transmitted simultaneously as sub-channels in one communication channel, but are physically transmitted on different resources. In Frequency Division Duplex (FDD), uplink and downlink transmissions can operate using carriers of different frequencies (i.e., a separate carrier frequency is used for each transmission direction). Interference can be avoided in FDD because the downlink signal uses a carrier at a different frequency than the uplink signal. Summary of the Invention

[0008] One aspect of this disclosure relates to an apparatus for a user equipment (UE), the apparatus including a radio frequency (RF) circuit interface and processing circuitry, the processing circuitry being coupled to the RF interface and configured to: decode control information from a base station, the control information including HARQ-ACK codebook information for a hybrid automatic repeat request acknowledgment (HARQ-ACK) signal in a physical uplink control channel (PUCCH) from the UE to the base station, wherein the HARQ-ACK codebook information is based on a dynamic HARQ-ACK codebook; decode physical downlink shared channel (PDSCH) transmission from the base station; and based on the control information and based on the... The PDSCH encodes the HARQ-ACK signal for transmission to the base station; wherein the HARQ-ACK codebook information includes information about the size of the HARQ-ACK aggregation window for the HARQ-ACK signal; wherein the control information is in the downlink control information (DCI), and the processing circuitry is used to configure the size of the HARQ-ACK aggregation window based on the decoding of the DCI; wherein the DCI includes information about the downlink allocation index C-DAI; and wherein the C-DAI has a value that increases in a frequency-first, time-later manner corresponding to the PDSCH transmission.

[0009] One aspect of this disclosure relates to an apparatus for a user equipment (UE), the apparatus including a radio frequency (RF) circuit interface and processing circuitry coupled to the RF interface and configured to: decode control information from a base station, the control information including HARQ-ACK codebook information for a hybrid automatic repeat request acknowledgment (HARQ-ACK) signal in a physical uplink control channel (PUCCH) from the UE to the base station; decode physical downlink shared channel (PDSCH) transmission from the base station; and encode the HARQ-ACK signal based on the control information and based on the PDSCH for transmission to the base station; wherein the HARQ-ACK codebook information includes information about the size of a HARQ-ACK aggregation window for the HARQ-ACK signal; and wherein the control information is at least one of downlink control information (DCI) or radio resource control (RRC) signaling, the processing circuitry being configured to configure the size of the HARQ-ACK aggregation window based on at least one of decoding the DCI or decoding the RRC signaling and further based on the subcarrier spacing of a component carrier (CC) for transmitting the PUCCH.

[0010] One aspect of this disclosure relates to an apparatus for a base station, the apparatus including a radio frequency (RF) circuit interface and processing circuitry, the processing circuitry being coupled to the RF interface and configured to: encode control information for transmission to a user equipment (UE), the control information including HARQ-ACK codebook information for a hybrid automatic repeat request acknowledgment (HARQ-ACK) signal in a physical uplink control channel (PUCCH) from the UE to the base station; encode a physical downlink shared channel (PDSCH) transmission to the UE based on the control information; and decode the HARQ-ACK signal from the UE; wherein... The HARQ-ACK codebook information includes information about the size of the HARQ-ACK aggregation window for the HARQ-ACK signal; wherein the control information is at least one of downlink control information (DCI) or radio resource control (RRC) signaling, and the control information can be decoded by the UE so that the UE can determine the size of the HARQ-ACK aggregation window based on at least one of the decoding of the DCI or the RRC signaling; and wherein the HARQ-ACK aggregation window is based on the subcarrier spacing of the component carrier CC used to transmit the PUCCH. Attached Figure Description

[0011] Figure 1 The architecture of a system 100 of a network according to some embodiments is shown;

[0012] Figure 2 Example components of a device according to some embodiments are shown;

[0013] Figure 3 An example interface of a baseband circuit according to some embodiments is shown;

[0014] Figure 4 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein, according to some example embodiments.

[0015] Figure 5 This is a New Radio (NR) signaling diagram, which illustrates an example of cross-carrier scheduling with different parameter sets in two CCs using slot indexing;

[0016] Figure 6 This is an NR signaling diagram, which illustrates another embodiment of cross-carrier scheduling with different parameter sets in CC using slot indexing;

[0017] Figure 7 This is an NR signaling diagram, which illustrates an example of cross-carrier scheduling based on the mini-slot principle;

[0018] Figure 8 This is an NR signaling diagram, which illustrates an example of cross-carrier and cross-slot scheduling with single-element delay indication;

[0019] Figure 9 This is an NR signaling diagram, which illustrates an example of cross-carrier and cross-slot scheduling using two-element timing indicators;

[0020] Figure 10 This is an NR signaling diagram illustrating an embodiment of cross-carrier multi-slot scheduling;

[0021] Figure 11 This is an NR signaling diagram, which illustrates an example of cross-carrier multi-slot scheduling using slot group indexing;

[0022] Figure 12 This is an NR signaling diagram, which illustrates an example of cross-carrier scheduling with two-level DCI;

[0023] Figure 13 This is an NR signaling diagram, which illustrates an example of HARQ-ACK feedback on a PCell or PUCCH SCell with a mixed set of parameters using a two-element timing indication process;

[0024] Figure 14 This is an NR signaling diagram, which illustrates another embodiment of HARQ-ACK feedback on a PCell or PUCCH SCell with a mixed set of parameters or TTI duration with the SCell;

[0025] Figure 15a This is an NR signaling diagram, which shows an example of multiple time slots used to transmit PUCCH carrying HARQ-ACK for PDSCH data transmission;

[0026] Figure 15b This is an NR signaling diagram, which illustrates an embodiment of a micro-slot structure for transmitting PUCCH carrying HARQ-ACK;

[0027] Figure 16 This is an NR signaling diagram, which illustrates an example of a HARQ-ACK aggregation window for a CC in the case of aggregated HARQ-ACK feedback;

[0028] Figure 17a This is an NR signaling diagram, which illustrates an embodiment for cross-carrier multi-slot scheduling involving HARQ-ACK feedback, where the bits are ordered in the UCI in a time-first-frequency-second manner.

[0029] Figure 17bThis is an NR signaling diagram, which illustrates an embodiment for cross-carrier multi-slot scheduling involving HARQ-ACK feedback, wherein the bits are ordered in the UCI in a frequency-first, time-later manner;

[0030] Figure 18a This is an NR signaling diagram, which illustrates another embodiment for cross-carrier multi-slot scheduling involving HARQ-ACK feedback, wherein the bits are ordered in the UCI in a time-first-frequency-later manner;

[0031] Figure 18b This is an NR signaling diagram, which illustrates another embodiment for cross-carrier multi-slot scheduling involving HARQ-ACK feedback, wherein the bits are ordered in the UCI in a frequency-first-time manner;

[0032] Figure 19 This is an NR signaling diagram, which illustrates another embodiment for cross-carrier multi-slot scheduling involving HARQ-ACK feedback, wherein the bits are ordered in the UCI such that they increment first in a time manner and then in a frequency manner after reaching the slot boundary;

[0033] Figure 20a This is an NR signaling diagram, which illustrates an embodiment for dynamic cross-carrier multi-slot scheduling involving HARQ-ACK feedback, wherein the bits are ordered first by time and then by frequency.

[0034] Figure 20b This is an NR signaling diagram illustrating an embodiment for dynamic cross-carrier multi-slot scheduling involving HARQ-ACK feedback, where the bits are ordered first by frequency and then by time; and

[0035] Figure 20c This is an NR signaling diagram illustrating an embodiment for dynamic cross-carrier multi-slot scheduling involving HARQ-ACK feedback, wherein the bits are ordered in the UCI such that they increment first in a time manner and then in a frequency manner after reaching the slot boundary. Detailed Implementation

[0036] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details such as particular structures, architectures, interfaces, and technologies are set forth for purposes of explanation and not limitation in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be implemented in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and processes are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0037] Mobile communication has evolved significantly from early voice systems to today's highly complex integrated communication platforms. The next generation of wireless communication systems, 5G or NR, will provide a wide range of users and applications with access to information and data sharing anytime, anywhere. NR is envisioned as a unified network / system designed to meet extremely different and sometimes conflicting performance dimensions and services. This diverse, multidimensional demand is driven by various services and applications. Generally, NR will be based on 3GPP LTE-Advanced evolution with the addition of potential new Radio Access Technologies (RATs) to enrich people's lives through better, simpler, and more seamless wireless connectivity solutions. NR will enable everything to be wirelessly connected, providing fast, rich content and services.

[0038] For NR systems, high-frequency communication (i.e., communication in frequency bands with a center frequency above 6 GHz) has recently attracted significant attention from the industry because it offers wider bandwidth to support future integrated communication systems. Beamforming represents a key technology for realizing high-frequency systems because beamforming gain can compensate for severe path loss caused by atmospheric attenuation, improve the signal-to-noise ratio (SNR), and extend the coverage area. By aligning the transmit beam with the target user equipment (UE), radiated energy can be focused for higher energy efficiency and mutual UE interference can be suppressed.

[0039] The embodiments generally pertain to apparatus, systems, and methods for providing location information about a second transmission in another CC within a first transmission in one CC. According to one embodiment, the indication may include, within control information in the PDCCH of one CC, a scheduling indication of the timing of corresponding data transmission in the PDSCH of another different CC, wherein the CCs may have a mixed set of parameters. According to another embodiment, the indication may include, within control information in the PUCCH of one CC, an indication of the size and order of bits of a HARQ-ACK feedback signal or HARQ-ACK signal in another CC, the HARQ-ACK feedback being for data transmission within the PDSCH corresponding to the control information in the PDCCH.

[0040] Long Term Evolution (LTE) Release 10 (Rel-10) introduces and supports cross-carrier scheduling, where the component carriers (CCs) on which the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) are scheduled are different from the CCs on which the Physical Downlink Control Channel (PDCCH) is scheduled. Specifically, for cross-carrier scheduling, Rel-10 uses the Carrier Indication Field (CIF) in the Downlink Control Information (DCI) of the PDCCH to indicate which CC is used for data transmission on the PDSCH and PUSCH.

[0041] For NR, similar mechanisms for cross-carrier scheduling can be considered. Key advantages include: (1) mitigating control channel interference; (2) assistance from low-frequency bands (e.g., carrier frequencies below 6 GHz) to schedule data transmission in high-frequency bands (e.g., carrier frequencies above 6 GHz)—given that transmission in low-frequency bands is more robust than transmission in high-frequency bands, it may be desirable to transmit PDCCH in low-frequency bands to achieve a better link budget; (3) reducing UE power consumption by monitoring a limited number of CCs for DCI; (4) avoiding control channel congestion on a single CC; etc.

[0042] However, given the fact that different parameter sets or transmission time interval (TTI) durations may be applied to transmissions on different CCs in NR, certain enhancements to cross-carrier scheduling can be considered, especially when using a low-frequency PDCCH to schedule high-frequency data transmissions.

[0043] Some embodiments of this document may include scheduling and hybrid automatic repeat request (HARQ) operations for NR using a hybrid parameter set for carrier aggregation.

[0044] First, the following will be about Figure 1-4 Example networks and architectures that can be used to implement some exemplary embodiments are shown and described.

[0045] Specifically, Figure 1 The architecture of a system 100 of a network according to some embodiments is shown. System 100 is shown as including user equipment (UE) 101 and UE 102. UE 101 and 102 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, wireless handheld device, or any computing device including a wireless communication interface.

[0046] In some embodiments, either UE 101 or 102 may include an Internet of Things (IoT) UE, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a Public Land Mobile Network (PLMN), ProSe or Device-to-Device (D2D) communication, sensor network, or IoT network. M2M or MTC data exchange may be machine-initiated. The IoT network describes interconnecting IoT UEs (which may include uniquely identifiable embedded computing devices within the Internet infrastructure) using short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, state updates, etc.) to facilitate connectivity within the IoT network.

[0047] UEs 101 and 102 can be configured to connect (e.g., be communicatively coupled) to a radio access network (RAN) 110—RAN 110 can be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. UEs 101 and 102 utilize connections 103 and 104, respectively, each connection including a physical communication interface or layer (discussed in further detail below). In this example, connections 103 and 104 are shown as air interfaces for implementing communication coupling and can conform to cellular communication protocols such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) network protocols, Push-to-Talk (PTT) protocols, PTT on Cellular (POC) protocols, Universal Mobile Telecommunications System (UMTS) protocols, 3GPP Long Term Evolution (LTE) protocols, 5G protocols, New Radio (NR) protocols, etc.

[0048] RAN 110 may include one or more access nodes that enable connectivity between 103 and 104. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). RAN 110 may include one or more RAN nodes (e.g., macro RAN node 111) for providing macro cells and one or more RAN nodes (e.g., low-power (LP) RAN node 112) for providing femtocells or picocells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells).

[0049] Either RAN node 111 or 112 can terminate the air interface protocol and can be the first contact point for UEs 101 and 102. In some embodiments, either RAN node 111 or 112 can perform various logical functions of RAN 110, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0050] According to some embodiments, UEs 101 and 102 can be configured to communicate with each other or with either RAN nodes 111 and 112 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals, based on various communication technologies (e.g., but not limited to orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication)). However, the scope of the embodiments is not limited thereto. The OFDM signal may include multiple orthogonal subcarriers.

[0051] In some embodiments, the downlink resource grid can be used for downlink transmissions from either RAN nodes 111 and 112 to UEs 101 and 102, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in each time slot of the downlink. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is called a resource element. Each resource grid comprises multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Several different physical downlink channels exist that use such resource blocks for transmission.

[0052] The Physical Downlink Shared Channel (PDSCH) can carry user data and higher-layer signaling to UEs 101 and 102. The Physical Downlink Control Channel (PDCCH) can carry information such as transmission format and resource allocation related to the PDSCH in the form of control information. It can also inform UEs 101 and 102 of transmission format, resource allocation, and HARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control channel resource blocks and shared channel resource blocks to UEs 101 and 102 within the cell) can be performed at either RAN node 111 or 112 based on channel quality information fed back from either UE 101 or 102. Downlink resource allocation information can be transmitted on the PDCCH used (e.g., assigned to) each of UEs 101 and 102.

[0053] PDCCH can use Control Channel Elements (CCEs) to transmit control information. Before being mapped to resource elements, PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE can correspond to four physical resource elements in nine groups called resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. One or more CCEs can be used to transmit PDCCH, depending on the size of the downlink control information (DCI) and the channel conditions. In LTE, four or more different PDCCH formats (e.g., aggregation levels, L = 1, 2, 4, or 8) with different numbers of CCEs can be defined.

[0054] In this embodiment, UEs 101 and 102 can also directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may also be referred to as a sidelink interface, which includes one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0055] UE 102 is shown configured to access access point (AP) 106 via connection 107. Connection 107 may include a local wireless connection, such as a connection compliant with any IEEE 802.11 protocol, wherein AP 106 will include Wireless Fibre Channel. Router. In this example, AP 106 is shown connected to the Internet but not to the core network of the wireless system (described in further detail below).

[0056] RAN 110 may include one or more access nodes that enable connectivity between 103 and 104. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). RAN 110 may include one or more RAN nodes (e.g., macro RAN node 111) for providing macro cells and one or more RAN nodes (e.g., low-power (LP) RAN node 112) for providing femtocells or picocells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells).

[0057] Either RAN node 111 or 112 can terminate the air interface protocol and can be the first contact point for UEs 101 and 102. In some embodiments, either RAN node 111 or 112 can perform various logical functions of RAN 110, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0058] According to some embodiments, UEs 101 and 102 can be configured to communicate with each other or with either RAN nodes 111 and 112 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals, based on various communication technologies (e.g., but not limited to orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication)). However, the scope of the embodiments is not limited thereto. The OFDM signal may include multiple orthogonal subcarriers.

[0059] In some embodiments, the downlink resource grid can be used for downlink transmissions from either RAN nodes 111 and 112 to UEs 101 and 102, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in each time slot of the downlink. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is called a resource element. Each resource grid comprises multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Several different physical downlink channels exist that use such resource blocks for transmission.

[0060] The Physical Downlink Shared Channel (PDSCH) can carry user data and higher-layer signaling to UEs 101 and 102. The Physical Downlink Control Channel (PDCCH) can carry information such as transmission format and resource allocation related to the PDSCH channel in the form of control information. It can also inform UEs 101 and 102 of transmission format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control channel resource blocks and shared channel resource blocks to UEs 101 and 102 within the cell) can be performed at either RAN node 111 or 112 based on channel quality information fed back from either UE 101 or 102. Downlink resource allocation information can be transmitted on the PDCCH used (e.g., assigned to) each of UEs 101 and 102.

[0061] PDCCH can use Control Channel Elements (CCEs) to transmit control information. Before being mapped to resource elements, PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE can correspond to four physical resource elements in nine groups called resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. One or more CCEs can be used to transmit PDCCH, depending on the size of the downlink control information (DCI) and the channel conditions. In LTE, four or more different PDCCH formats (e.g., aggregation levels, L = 1, 2, 4, or 8) with different numbers of CCEs can be defined.

[0062] Some embodiments may use a concept that extends the above-described approach for resource allocation of control channel information. For example, some embodiments may utilize an Enhanced Physical Downlink Control Channel (EPDCCH), which uses PDSCH resources for control information transmission. One or more Enhanced Control Channel Elements (ECCEs) may be used to transmit the EPDCCH. Similar to the above, each ECCE may correspond to four physical resource elements in nine groups called Enhanced Resource Element Groups (EREGs). In some cases, an ECCE may have a different number of EREGs.

[0063] RAN 110 is shown communicatively coupled to core network (CN) 120 via S1 interface 113. In embodiments, CN 120 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 113 is divided into two parts: S1-U interface 114, which carries service data between RAN nodes 111 and 112 and serving gateway (S-GW) 122; and S1 mobility management entity (MME) interface 115, which is the signaling interface between RAN nodes 111 and 112 and MME 121.

[0064] In this embodiment, CN 120 includes MME 121, S-GW 122, Packet Data Network (PDN) Gateway (P-GW) 123, and Home Subscriber Server (HSS) 124. MME 121 can functionally resemble the control plane of a Legacy Service General Packet Radio Service (GPRS) Support Node (SGSN). MME 121 can manage mobility aspects of access, such as gateway selection and tracking area list management. HSS 124 can include a database for network users, including subscription-related information to support network entities in handling communication sessions. CN 120 can include one or more HSS 124s, depending on the number of mobile subscribers, device capacity, network organization, etc. For example, HSS 124 can provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependencies, etc.

[0065] The S-GW 122 can terminate the S1 interface 113 leading to RAN 110 and route data packets between RAN 110 and CN 120. Furthermore, the S-GW 122 can serve as a local mobility anchor for inter-RAN node handover and can also provide anchoring for inter-3GPP mobility. Other responsibilities may include statutory interception, charging, and some form of policy enforcement.

[0066] P-GW 123 can terminate an SGi interface leading to the PDN. P-GW 123 can route data packets between EPC network 123 and external networks (e.g., a network including application server 130 (alternately referred to as Application Function (AF)) via Internet Protocol (IP) interface 125. Typically, application server 130 can be an element that provides applications (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.) using IP bearer resources to the core network. In this embodiment, P-GW 123 is shown communicatively coupled to application server 130 via IP communication interface 125. Application server 130 can also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UEs 101 and 102 via CN 120.

[0067] P-GW 123 can also be a node for policy enforcement and charging data collection. The Policy and Charging Rule Function (PCRF) 126 is the policy and charging control element of CN 120. In non-roaming scenarios, a single PCRF associated with the UE's Internet Protocol Connectivity (IP-CAN) session can exist in the Home Public Land Mobile Network (HPLMN). In roaming scenarios where services are not local, two PCRFs associated with the UE's IP-CAN session can exist: the Home PCRF (H-PCRF) within the HPLMN and the Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). PCRF 126 can be communicatively coupled to application server 130 via P-GW 123. Application server 130 can signal PCRF 126 to indicate new service flows and select appropriate Quality of Service (QoS) and charging parameters. PCRF 126 can assign the rule to the Policy and Charging Enforcement Function (PCEF) (not shown) with an appropriate Service Flow Template (TFT) and QoS Class Identifier (QCI), which enables QoS and charging to begin as specified by application server 130.

[0068] Figure 2Example components of a device 200 according to some embodiments are shown. In some embodiments, device 200 may include application circuitry 202, baseband circuitry 204, radio frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 212, coupled together, at least as shown, by way of example. Components of the illustrated device 200 may be included in a UE or RAN node. In some embodiments, device 200 may include fewer components (e.g., the RAN node may not utilize application circuitry 202, but instead include a processor / controller to process IP data received from the EPC or Evolved Packet Core). In some embodiments, device 200 may include additional components such as memory / storage, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., for a cloud RAN (C-RAN) implementation, the circuitry may be separately included in more than one device).

[0069] Application circuitry 202 may include one or more application processors. For example, application circuitry 202 may include circuitry with, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include memory / storage, and may be configured to execute instructions stored in memory / storage to enable various applications or operating systems to run on device 200. In some embodiments, the processor of application circuitry 202 may process IP data packets received from the EPC.

[0070] Baseband circuitry 204 may include, for example, but not limited to, processing circuitry of one or more single-core or multi-core processors. Baseband circuitry 204 may include one or more baseband processors and one or more memories for storing instructions or control logic. The baseband processors implement control logic to process baseband signals received from the receive signal path of RF circuitry 206 and generate baseband signals for the transmit signal path of RF circuitry 206. Baseband circuitry 204 may interface with application circuitry 202 for generating and processing baseband signals and controlling the operation of RF circuitry 206. Therefore, baseband circuitry 204 can induce the transmission of data or control information by generating signals that cause the RF circuitry and antenna to transmit data or control information. For example, in some embodiments, baseband circuitry 204 may include a third-generation (3G) baseband processor 204A, a fourth-generation (4G) baseband processor 204B, a fifth-generation (5G) baseband processor 204C, or other baseband processors 204D for other existing, developing, or future generations (e.g., second-generation (2G), sixth-generation (6G), etc.). The baseband circuitry 204 (e.g., one or more of the baseband processors 204A-D) can process various radio control functions that enable communication with one or more radio networks via the RF circuitry 206. In other embodiments, some or all of the functions of the baseband processors 204A-D may be included in a module stored in memory 204G and executed via a central processing unit (CPU) 204E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 204 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Embodiments of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

[0071] In some embodiments, baseband circuitry 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSP 204F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the constituent components of baseband circuitry 204 and application circuitry 202 may be implemented together on, for example, a system-on-a-chip (SoC).

[0072] In some embodiments, baseband circuitry 204 can provide communication compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 204 can support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Embodiments in which baseband circuitry 204 is configured to support radio communication with more than one radio protocol may be referred to as multimode baseband circuitry.

[0073] RF circuit 206 enables communication with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various embodiments, RF circuit 206 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 206 may include a receive signal path, which may include circuitry for down-converting RF signals received from FEM circuit 208 and providing baseband signals to baseband circuit 204. RF circuit 206 may also include a transmit signal path, which may include circuitry for up-converting the baseband signals provided by baseband circuit 204 and providing RF output signals to FEM circuit 208 for transmission.

[0074] In some embodiments, the receive signal path of RF circuit 206 may include mixer circuit 206A, amplifier circuit 206B, and filter circuit 206C. In some embodiments, the transmit signal path of RF circuit 206 may include filter circuit 206C and mixer circuit 206A. RF circuit 206 may also include synthesizer circuit 206D for synthesizing the frequency used by mixer circuit 206A in both the receive and transmit signal paths. In some embodiments, mixer circuit 206A in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 208 based on the synthesized frequency provided by synthesizer circuit 206D. Amplifier circuit 206B may be configured to amplify the down-converted signal, and filter circuit 206C may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 204 for further processing. In some embodiments, the output baseband signal may be a zero-frequency baseband signal, but this is not required. In some embodiments, the mixer circuit 206A of the received signal path may include a passive mixer, but the scope of the embodiments is not limited thereto.

[0075] FEM circuit 208 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals, and provide an amplified version of the received signals to RF circuit 206 for further processing. FEM circuit 208 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuit 206 for transmission by one or more of the one or more antennas 210. In various embodiments, amplification via the transmit or receive signal path may be performed solely in RF circuit 206, solely in FEM 208, or both RF circuit 206 and FEM 208.

[0076] In some embodiments, FEM circuit 208 may include a TX / RX switch to switch between transmit and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include a low-noise amplifier (LNA) for amplifying the received RF signal and providing the amplified received RF signal as an output (e.g., to RF circuit 206). The transmit signal path of FEM circuit 208 may include: a power amplifier (PA) for amplifying (e.g., provided by RF circuit 206) the input RF signal; and one or more filters for generating RF signals for subsequent transmission (e.g., performed by one or more of one or more antennas 210).

[0077] In some embodiments, the PMC 212 can manage the power supplied to the baseband circuitry 204. Specifically, the PMC 212 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 212 is often included when the device 200 can be powered by a battery, such as when the device 200 is included in a UE. The PMC 212 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0078] Figure 2 The diagram shows that PMC 212 is coupled only to baseband circuitry 204. However, in other embodiments, PMC 212 may additionally or alternatively couple to other components, such as, but not limited to, application circuitry 202, RF circuitry 206, or FEM 208, and perform similar power management operations for other components.

[0079] In some embodiments, PMC 212 may control, or be part of, various power-saving mechanisms of device 200. For example, if device 200 is in the RRC_Connected state (where it remains connected to the RAN node because it expects to receive traffic soon), it may enter a state called Discontinuous Receive Mode (DRX) after an inactive period. During this state, device 200 may be powered down for short time intervals to save power.

[0080] The processors of application circuit 202 and baseband circuit 204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of baseband circuit 204 (alone or in combination) can be used to execute layer 3, layer 2, or layer 1 functions, while the processor of application circuit 202 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, layer 3 may include the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include the physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0081] Figure 3 An example interface of a baseband circuit according to some embodiments is shown. As discussed above, Figure 2 The baseband circuit 204 may include processors 204A-204E and a memory 204G used by the processors. Each of the processors 204A-204E may respectively include a memory interface 304A-304E for sending / receiving data to / from the memory 204G.

[0082] Baseband circuit 204 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as memory interface 312 (e.g., an interface for sending / receiving data to / from a memory external to baseband circuit 204) and application circuit interface 314 (e.g., an interface for sending / receiving data to / from a memory external to baseband circuit 204). Figure 2 Application circuit 202 (interface for sending / receiving data), RF circuit interface 316 (e.g., for sending / receiving data to / from...). Figure 2 The RF circuit 206 is an interface for transmitting / receiving data, and the wireless hardware connection interface 318 is used for transmitting / receiving data to / from near field communication (NFC) components. Components (e.g., ), Interfaces for sending / receiving data to / from components and other communication components) and power management interface 320 (e.g., an interface for sending / receiving power or control signals to / from PMC 212).

[0083] Figure 4 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein, according to some example embodiments. Specifically, Figure 4 A graphical representation of hardware resources 400 is shown, including one or more processors (or processor cores) 410, one or more memory / storage devices 420, and one or more communication resources 430, each of which may be communicatively coupled via bus 440. In embodiments utilizing node virtualization (e.g., NFV), a hypervisor 402 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resources 400.

[0084] Processor 410 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), such as a baseband processor, an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 412 and processor 414.

[0085] Memory / storage device 420 may include main memory, disk storage, or any suitable combination thereof. Memory / storage device 420 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0086] Communication resource 430 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 404 or one or more databases 406 via network 408. For example, communication resource 430 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB), cellular communication components, NFC components, etc. Components (e.g., ), Components and other communication components.

[0087] Instructions 450 may include software, programs, applications, applets, or other executable code for causing at least any processor 410 to perform any one or more of the methods discussed herein. Instructions 450 may reside wholly or partially within at least one of the processor 410 (e.g., within the processor's cache), memory / storage device 420, or any suitable combination thereof. Furthermore, any portion of instructions 450 may be transferred from any combination of peripheral device 404 or database 406 to hardware resource 400. Therefore, the memory of processor 410, memory / storage device 420, peripheral device 404, and database 406 are examples of computer-readable and machine-readable media.

[0088] In some embodiments, Figure 1-4 The electronic devices, networks, systems, chips, or components, or portions thereof, or implementations thereof, shown in certain other accompanying drawings may be configured to perform one or more processes, techniques, or methods as described herein with respect to embodiments or portions thereof.

[0089] According to some exemplary embodiments, the apparatus, system, and method include control information in a first transmission in a first CC, the control information including an indication of timing information for a second transmission in a second CC, wherein the indication is based on a subcarrier spacing of one of the first CC and the second CC. According to one embodiment, the first CC and the second CC have different subcarrier spacings.

[0090] In some embodiments, the indication may include scheduling information, and the second transmission may include data transmission of the PDSCH or HARQ-ACK feedback of the PUCCH. These later embodiments are described in more detail in the section entitled “Cross-carrier scheduling with mixed parameter sets or TTI durations between a first CC carrying a PDCCH and a second CC carrying a corresponding PDSCH” and the subsection “HARQ-ACK feedback on a PCell with different parameter sets or TTI durations than the SCell” in this specification.

[0091] In an alternative embodiment, the indication may include HARQ-ACK codebook information. In one embodiment, the second transmission may include data transmission of the PDSCH. These later embodiments are described in more detail below in the section entitled "HARQ-ACK Codebook Design for NR Carrier Aggregation," wherein the subsections are "Semi-static HARQ-ACK Codebook for Carrier Aggregation with the Same or Mixed Parameter Sets or TTI Durations" and "Dynamic HARQ-ACK Codebook for Carrier Aggregation with the Same or Mixed Parameter Sets or TTI Durations."

[0092] According to one embodiment, the first transmission may include DCI in the PDCCH.

[0093] In this specification, the time slot index is referred to as Sn, where n corresponds to the time slot number. Therefore, as an example, time slot index 1 will be referred to as S1, and so on. Additionally, a time slot according to an embodiment may include 14 symbols or any other number of symbols.

[0094] Cross-carrier scheduling with mixed parameter sets or TTI durations between the first CC carrying the PDCCH and the second CC carrying the corresponding PDSCH:

[0095] According to some exemplary embodiments, mechanisms are provided for cross-carrier scheduling with mixed parameter sets or TTI durations. Such scheduling includes: scheduling PDSCH data transmission on one CC, wherein the corresponding control information for PDCCH is on another CC with a different parameter set; and scheduling HARQ-ACK feedback on a primary cell (PCell) with a different parameter set or TTI duration than the secondary cell (SCell).

[0096] According to some exemplary embodiments, in cross-carrier scheduling, the NR control channel (e.g., PDCCH) on one CC can be used to schedule data transmission on dissimilar / different CCs. To achieve cross-carrier scheduling, the Carrier Indication Field (CIF) in the DCI of the PDCCH can indicate which CC is used for data transmission, i.e., for transmitting PDSCH or PUSCH. Considering that different parameter sets or subcarrier spacings may be used for different CCs in NR, the parameter set or subcarrier spacing used for data transmission in the scheduled other CC can be configured via higher-layer signaling, dynamically indicated in the DCI, or a combination thereof. For NR, it has been agreed that symbol-level alignment should be maintained across different subcarrier spacings while maintaining the same cyclic prefix (CP) overhead.

[0097] In some exemplary embodiments described herein, although only the scheduled PDSCH may be mentioned at times, the described embodiments can be equally applied to the scheduling of PUSCH, as is known to those skilled in the art.

[0098] Now refer to Figure 5-7This illustrates different embodiments for indicating scheduling information in the form of slot indexes in the control information for PDCCH on a first CC, the scheduling information relating to the data transmission of PDSCH or PUSCH in a second CC that is different from and has a different parameter set relative to the first CC. Embodiments may include the use of slot indexes in cross-carrier scheduling with different parameter sets or TTI durations. The slot indexes may be explicitly indicated in the DCI or configured by higher-layer signaling via Radio Resource Control (RRC) signaling for scheduling PDSCH or PUSCH data transmission. In each case, when indicating a slot index for an upcoming PDSCH or PUSCH transmission on the second CC, it becomes useful to define the slot index as a reference point based on the parameter set of the known / predetermined CC (based on the predetermined parameter set) so that, in practice, scheduling can be indicated according to the time granularity specified by the subcarrier spacing in the known / predetermined CC.

[0099] Figure 5 This is NR signaling diagram 500, which illustrates an embodiment of cross-carrier scheduling with different parameter sets in two CCs using slot indexes. In the example shown, subcarrier spacings of 15 kHz and 60 kHz are used in CC#1 and CC#2, respectively. Therefore, the slot duration of CC#1, shown as slot 501, is 1 millisecond (ms), while the slot duration of CC#2, shown as four slots 505, is approximately 0.25 ms. Furthermore, it is shown that a PDCCH control transmission (i.e., transmission including control information) 502 at CC#1 can be used to schedule PDSCH or PUSCH data transmission 504 at CC#2 in S1 of CC#2. As an example... Figure 5 As shown, each of time slots 501 and 505 may include 14 symbols, or any other number of symbols. In the case of CC#1, the time slot duration of time slot 501 corresponds to a subframe duration of 1 ms, while in CC#2, there are four time slots 505: S0, S1, S2, and S3.

[0100] In some exemplary embodiments, the slot index used to indicate slot scheduling in another CC can be defined in a variety of exemplary ways: (1) based on a subframe boundary or using the slot boundary of the minimum subcarrier interval between the two CCs used for PDCCH or scheduled data transmission (in Figure 5 In the case of, for example, using a 1ms subcarrier interval of CC#1); (2) according to the subcarrier interval in the CC transmitted according to the PDCCH or data channel (in Figure 5 In some cases, for example, using the 1ms subframe boundary for transmitting PDSCH, which is aligned with the slot boundary of CC#2; or (3) according to the slot boundary with the minimum subcarrier spacing within the configured CC (which will be combined below). Figure 6(Further explanation).

[0101] Still refer to Figure 5 Therefore, the scheduling of PDSCH or PUSCH data transmission 504 can be explicitly indicated in the DCI within PDCCH 502, or configured by higher-layer signaling via RRC signaling, and can indicate the slot index defined according to the subcarrier interval of the predetermined CC as described above.

[0102] Now refer to Figure 6 The diagram 600 illustrates an NR signaling diagram showing an embodiment of cross-carrier scheduling with different parameter sets in CCs using slot indices to indicate scheduling. According to some exemplary embodiments, the slot indices can be derived from the slot boundaries with the minimum subcarrier spacing within the configured CCs. In the example shown, subcarrier spacings of 30 kHz, 60 kHz, and 120 kHz are used in CCs#1, CC#2, and CC#3, respectively. Therefore, the slot duration of CC#1, shown as slot 601, is 0.5 milliseconds (ms), the slot duration of CC#2, shown as four slots 605, is approximately 0.25 ms, and the slot duration of CC#3, shown as eight slots 607, is approximately 0.125 ms. Furthermore, it is shown that the PDCCH control transmission 602 at CC#2 can be used to schedule PDSCH data transmission 604 at CC#3 in S2 of CC#3.

[0103] Still refer to Figure 6 CC#1 can have the smallest subcarrier spacing among the three configured CCs, which is 30kHz, even though CC#1 is not used for transmitting PDCCH or PDSCH. In this case, the time slot boundary can be aligned with 0.5ms in CC#1, i.e., aligned according to the time slot boundary with the smallest subcarrier spacing within the configured CC. Furthermore, as shown, the control transmission of PDCCH in S0 of CC#2 with a 60kHz subcarrier spacing can be used to schedule data transmission in S2 of CC#3 with a 120kHz subcarrier spacing.

[0104] In other embodiments, the joint resource allocation field in the DCI may indicate the allocated time slots and symbols within those time slots for cross-carrier allocation. In one example, the resource block group used to allocate resources on the CC may depend on the CC bandwidth.

[0105] In other embodiments, the “micro-slot principle” can be employed when scheduling data transmission on another CC with different parameter sets or TTI durations. According to such an embodiment, when scheduling data transmission for a second CC in a first CC, information in the first CC can indicate the scheduling by explicitly indicating the start and end symbols or micro-slot indexes of the data transmission scheduled for the second CC. This indication can be in the DCI, where symbol boundaries are defined in several different ways: (1) based on the minimum subcarrier spacing between the two CCs used for the PDCCH or the scheduled data transmission; (2) based on a constant reference (e.g., 15 kHz) subcarrier spacing; or (3) based on the subcarrier spacing in the PDCCH or the CC where the data is transmitted. According to one embodiment, the start or end symbol can be signaled from a subset of the symbol index. For example, a rule can be established that the start or end symbol can be either an even number of symbols or an odd number of symbols.

[0106] Now refer to Figure 7 This diagram, in the form of NR signaling diagram 700, illustrates an example of an embodiment of cross-carrier scheduling based on the micro-slot principle. In the example shown, subcarrier spacings of 15 kHz and 60 kHz are used in CC#1 and CC#2, respectively. It shows that the PDCCH control transmission 702 at CC#1 can be used to schedule PDSCH or PUSCH data transmission 704 at CC#2 in the symbols corresponding to symbols #4 to #7 of CC#1 (i.e., according to the subcarrier spacing of CC#1). In the case of CC#1, the slot duration of slot 701 corresponds to the subframe duration, while in CC#2, there are four slots 705, S0, S1, S2, and S3, each with 14 symbols, as described above. The PDSCH or PUSCH data transmission 704 is scheduled to begin at S1 and span to S2. According to one embodiment, the time slot index for data, i.e., the time slot index for PDSCH or PUSCH data transmission 704 on CC#2, can be implicitly derived from information in the PDCCH, wherein the PDCCH control transmission (which is aligned with the first time slot of CC#2 and indicates the symbol # in CC#2 that will span S1 and S2 of CC#2) will allow the receiver of the data transmission to understand that the data transmission of PDSCH or PUSCH is scheduled in S1 and S2 of CC#2.

[0107] In some exemplary embodiments, in the case of cross-carrier and cross-slot scheduling, an indication of the timing delay between the PDCCH control transmission and the data transmission of the scheduled PDSCH or PUSCH can be used to indicate the scheduling of data transmission. The timing delay can be configured via higher-layer signaling, can be indicated as a combination of higher-layer signaling and dynamic indication in the DCI, or can be indicated explicitly using only the DCI. Furthermore, in some embodiments, the slot delay is defined based on the minimum subcarrier spacing of the two CCs used for the control transmission in the PDCCH or the scheduled data transmission, or based on a consistently 15kHz subcarrier spacing, or based on the subcarrier spacing of the CCs in which the PDCCH or data channel is transmitted.

[0108] In some exemplary embodiments, timing can be defined based on the subcarrier spacing in the CCs that the PDCCH can transmit. Furthermore, the scheduling timing delay can be derived according to Equation 1, as follows:

[0109]

[0110] in, and These can be the subcarrier spacings of CC#1 and CC#2, used respectively for transmitting PDCCH and PDSCH or PUSCH, and N delay This can be the scheduling timing delay relative to the slot boundary of CC#2. In Equation 1, the left side represents the lower limit value, and the right side represents the upper limit value. According to some embodiments, the NR evolved Node B (gNB) can determine the scheduling timing delay based on the subcarrier spacing of the first CC and the second CC, and can appropriately configure the delay for UE operation.

[0111] Now refer to Figure 8-12 It shows the use of a one-step timing indicator ( Figure 8 Two-step timing indication ( Figure 9 Using multi-slot scheduling Figure 10-11 ) and two levels of DCI ( Figure 12 Various embodiments of cross-carrier scheduling are described in further detail below. Figure 8-12 .

[0112] Now refer to Figure 8The figure illustrates an example of an embodiment of cross-carrier and cross-slot scheduling with an element (which may be referred to as a "step" in the figure) delay indication, in the form of NR signaling diagram 800. In the example shown, subcarrier spacings of 30 kHz and 120 kHz are used in CC#1 and CC#2, respectively. A PDCCH control transmission 802 at CC#2 is shown, which can be used to schedule PDSCH or PUSCH data transmission 804 at CC#1. CC#1 comprises a total of two time slots, S0 and S1, as shown, and CC#2 comprises a total of eight time slots, numbered S0 to S3 within the first time slot boundary of CC#1 and returning to S0 to S3 within the second time slot boundary of CC#1, as shown. Figure 8 In the example shown, the scheduling / timing delay (one slot delay) of the slot between the end slot of PDCCH control transmission 802 and the start slot of PDSCH or PUSCH data transmission 804 can be derived based on the minimum subcarrier interval (which is 30 kHz in CC#1). (That is, the delay will be indicated as one slot delay based on the slot duration of CC with the minimum subcarrier interval (i.e., CC#1).

[0113] In some exemplary embodiments, a two-step timing indication mechanism can be used to schedule data transmission in another CC. For example, in the first step of the scheduling indication, a first timing indication can be defined based on the time slots of the subcarrier intervals in the CC that is transmitting using PDCCH, while in the second step of the scheduling indication, a second timing indication can be defined based on the time slots of the subcarrier intervals in the CC that is transmitting using PDSCH or PUSCH data.

[0114] Now refer to Figure 9 The diagram, in the form of NR signaling diagram 900, illustrates an example of an embodiment of cross-slot and cross-carrier scheduling using two-step timing indication. In the example shown, subcarrier spacings of 30 kHz and 120 kHz are used in CC#1 and CC#2, respectively. A PDCCH control transmission 902 at CC#1 is shown to be used to schedule PDSCH or PUSCH data transmission 904 at CC#2. CC#1 comprises a total of two slots, S0 and S1, as shown. CC#2 comprises a total of eight slots, numbered S0 to S3 within the first slot boundary of CC#1 and returning to S0 to S3 within the second slot boundary of CC#1, as shown. In the first step of the scheduling indication, a first timing indication can be defined based on the slot of the subcarrier spacing in the CC where PDCCH is transmitted. In the second step of the scheduling indication, a second timing indication can be defined based on the slot of the subcarrier spacing in the CC where PDSCH or PUSCH data transmission is performed.

[0115] exist Figure 9In the example, the first step of the scheduling instruction would use the slot delay of one slot based on the 30kHz subcarrier spacing (in this case, the minimum subcarrier spacing between the two CCs) in CC#1 where PDSCH data is transmitted, for example, providing information in the DCI, and thus pointing to S1 of CC#1. The second step of the scheduling instruction would also provide timing delay information in the form of a slot index within the timing / slot boundary of S1 of CC#1 up to PDSCH or PUSCH data transmission 904, for example, also in the DCI. The latter slot index would correspond to S1 in CC#2, which is measured as S1 starting from the timing / slot boundary of S1 of CC#1 determined in the first step.

[0116] In some exemplary embodiments, the use of a one-step timing indication or a two-element timing / scheduling indication can be configured by higher-layer signaling or predefined in the specification. According to some embodiments, the use of a one-step or two-step timing / scheduling indication can depend on whether the CC used for PDCCH transmission has a larger subcarrier spacing, a smaller subcarrier spacing, or a shorter TTI duration (e.g., micro-slots) compared to the CC used for PDSCH or PUSCH transmission. For example, a two-step or two-element timing indication can be applied when the CC used for PDCCH transmission may have a smaller subcarrier spacing than the CC used for PDSCH or PUSCH transmission. One reason for the latter is that a smaller subcarrier spacing on the CC where PDSCH or PUSCH data is transmitted means that the slot size on that CC is larger than the slot size of the CC where data transmission occurs, making it easier to indicate the first step based on the smaller subcarrier spacing / larger slot size of the PDCCH CC. Conversely, a one-step or one-element timing indication can be applied when the CC used for PDCCH transmission may have a larger subcarrier spacing than the CC used for PDSCH / PUSCH transmission.

[0117] In some exemplary embodiments, cross-carrier scheduling can be used to schedule data transmission across multiple time slots. For example, in the case where multiple corresponding PDSCH or PUSCH data transmissions exist in multiple time slots within a CC (e.g., in CC#2), to reduce signaling overhead in the DCI of CC#1, a bitmap can be applied to the time slot index to indicate which time slot(s) can be used for data transmission. A bit value of "1" in the bitmap indicates that a time slot is to be used for data transmission, while a bit value of "0" indicates that a time slot is not to be used for data transmission. In some exemplary embodiments, cross-carrier multi-slot scheduling can be configured via higher-layer signaling via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), or via RRC signaling.

[0118] In some exemplary embodiments concerning multi-slot scheduling, some information in the DCI can be common across multiple PDSCH or PUSCH data transmissions to help achieve a desired reduction in signaling overhead. For example, resource allocation can be common across PDSCH / PUSCH data transmissions in different time slots. Furthermore, the DCI can indicate the starting HARQ process identifier (ID) for data transmission in the first time slot, and the HARQ process ID for data transmission in subsequent time slots can be derived accordingly. For example, the HARQ process ID can be incremented by 1. In one example, the HARQ process ID could be 3 for data transmission in the first time slot, 4 for data transmission in the second time slot, and so on.

[0119] In some exemplary embodiments of continuous multi-slot scheduling of data transmission, the demodulation reference symbol (DM-RS) may not be present in every slot, and in some slots, the DM-RS may be absent. The latter can further help improve the spectral efficiency of data transmission in the case of continuous multi-slot data transmission scheduling. The presence of the DM-RS in one or more slots can be configured via higher-layer signaling, dynamically indicated in the DCI, or a combination thereof.

[0120] Figure 10 An example of an embodiment for cross-carrier multi-slot scheduling is illustrated in NR signaling diagram 1000. In the example shown, subcarrier spacing of 30 kHz and 120 kHz are used in CC#1 and CC#2, respectively. PDCCH control transmission 1002 at CC#1 is shown to be used to schedule PDSCH or PUSCH data transmissions 1004a and 1004b at CC#2. CC#1 comprises a total of two slots, S0 and S1, as shown. CC#2 comprises a total of eight slots, numbered S0 to S3 within the first slot boundary of CC#1 and returning to S0 to S3 within the second slot boundary of CC#1, as shown. In this example, PDCCH control transmission 1002 in S0 of CC#1 is used to schedule data transmissions in S1 and S2 of CC#2 within the slot boundary of CC#1 (within the time boundary of the next slot S1 of CC#1). In DCI, a bitmap with “0110” can be used to schedule data transfer in CC#2 to indicate that within the S1 boundary of CC#1 in CC#2, S0 and S3 have no data, but S1 and S2 have data.

[0121] In some exemplary embodiments, where the number of time slots within a time slot boundary in one CC is relatively large (e.g., eight or more), a time slot group index can be used to specify contiguous time slot clusters when providing scheduling information about cross-CC data transmission. The use of a time slot group index can help reduce signaling overhead in the DCI by effectively reducing the need to specify each time slot when data is to be transmitted individually. More specifically, the number of time slots within a time slot group can be predefined in the specification or configured by higher-layer signaling via NR MSI, NR RMSI, NR OSI, or RRC signaling.

[0122] Now refer to Figure 11 An example illustration of an embodiment of cross-carrier multi-slot scheduling using slot group indexing is provided in the form of NR signaling diagram 1100. In the example shown, subcarrier spacings of 15 kHz and 120 kHz are used in CC#1 and CC#2, respectively. PDCCH control transmission 1102 at CC#1 is shown to be used to schedule PDSCH or PUSCH data transmissions 1104a, 1104b, 1104c, and 1104d at CC#2. CC#1 comprises a total of 1 slot, as shown, and CC#2 comprises a total of 8 slots, numbered S0 to S7 within the slot boundaries of CC#1. Furthermore, S0 and S1 are shown in slot group #0, S2 and S3 in slot group #1, S4 and S5 in slot group #2, and S6 and S7 in slot group #3. In this example, the bitmap used to specify scheduling refers to the time slot group within the time slot boundary of CC#1. Therefore, the bitmap with "0110" in the DCI can be used to schedule data transmission in time slot groups #1 and #2, while time slot groups #0 and #3 do not include data transmission. According to some embodiments, two or more time slots can be grouped into one time slot group. Figure 11 In the example shown, data can be sent in S2 through S5 on CC#2.

[0123] In other embodiments, the start symbol for data transmission can be configured by higher-layer signaling via NR MSI, NR RMSI, NR OSU, or RRC signaling, or dynamically indicated in the DCI, or a combination thereof. In some exemplary embodiments of cross-carrier multi-subframe scheduling, the start symbol for data transmission can be common across multiple time slots. Furthermore, dynamic resource sharing between DL control transmissions and DL data transmissions can be implemented to improve spectral efficiency. More specifically, when the start symbol for DL ​​data transmission is equal to or less than the duration of the control resource set, the DL data channel can be rate-matched around the control resource set, or the control resource set or the resources actually used for transmitting the DL control channel can be punctured.

[0124] In other embodiments, when using a low-frequency PDCCH to schedule high-frequency data transmission, beam-to-link indexes can be indicated in the DCI. More specifically, for scheduling high-frequency DL data transmission, the use of beam-to-link indexes can be achieved through an indication of the spatial quasi-co-station (QCL) assumption between the DL reference signal (RS) antenna port and the demodulation RS (DM-RS) antenna port of the DL data channel. Similarly, for UE UL data transmission in the high-frequency band, an indication of the probe reference signal (SRS) resource (SRI) in the DCI (transmitted by the UE in a previous time instance) can also be used to indicate the transmit (Tx) beam for UL data transmission. In some exemplary embodiments where phase tracking reference signals (PT-RS) are used in the high-frequency band, information regarding the scheduling of PT-RS in the time and frequency domains and the code domain can be indicated in the DCI.

[0125] In some exemplary embodiments, a two-level DCI can be applied, wherein the first-level DCI can be transmitted in a first CC, while the second-level DCI and scheduled DL data can be transmitted in a second CC. The fact that the second-level DCI is in the second CC can be indicated in the first-level DCI. As an example, the first-level DCI may include the following information: (1) resource allocation for the second-level DCI or data transmission; (2) indication of the payload size, aggregation level, and / or candidates of the second-level DCI; (3) a DL control resource set for monitoring the second-level DCI; and / or (4) a beamp-link index for transmitting the second-level DCI or data channel in a high-frequency band.

[0126] Figure 12 An example of an embodiment of cross-carrier scheduling with two-level DCI is shown in NR signaling diagram 1200. In the example shown, subcarrier spacing of 15 kHz and 60 kHz are used in CC#1 and CC#2, respectively. Therefore, the slot duration of CC#1 is 1 millisecond (ms), and the duration of CC#2, shown as 4 slots, is approximately 0.25 ms. Furthermore, a PDCCH control transmission 1202 including the first-level DCI 1211a at CC#1 and a second-level DCI 1211b at CC#2 are shown, which can be used to schedule PDSCH or PUSCH data transmission 1204 at CC#2 in S2. In the case of CC#1, the slot duration corresponds to the subframe duration, while in CC#2, there are 4 slots, S0, S1, S2, and S3. Figure 12In the example, the first-level DCI 1211a can be transmitted in CC#1, while the second-level DCI 1211b, along with the PDSCH / PUSCH data transmission, can be transmitted in CC#2 as transmission 1204. The use of multi-level DCIs can be advantageous in situations where the amount of information to be included in the DCI of the PDCCH may be too large for the DCI to carry, such as when there may be two or more users whose data may need to be addressed. In this case, transmitting information in two levels reduces signaling overhead on the control channel while still allowing the transmission of necessary control information.

[0127] HARQ-ACK feedback on PCells with different parameter sets or TTI durations than SCells

[0128] As mentioned earlier, for carrier aggregation in LTE Rel-10, multiple carriers (CCs) can be configured and aggregated to support wider transmission bandwidth and higher peak data rates. Furthermore, a UE may have one PCell and multiple SCells, where the PUCCH is transmitted only in the PCell. This indicates that HARQ-ACK feedback for DL ​​data transmission over multiple CCs can be aggregated and carried by the PUCCH on the PCell.

[0129] In LTE Release 13 (Rel-13) Enhanced Carrier Aggregation (eCA), the number of CCs is expanded to 32 for both DL and UL. Furthermore, in addition to being configured to transmit UCIs on the PCell, the UE can also be configured to transmit UCIs on the PUCCH SCell. The latter is motivated by reducing the control signaling overhead of the PCell. More specifically, in Rel-13, CCs are grouped into primary PUCCH groups and secondary PUCCH groups. The PUCCH on the PCell is used to carry UCIs for the PCell and SCells within the primary PUCCH group, while the PUCCH on the PUCCH SCell is used to carry UCIs for the SCells within the secondary PUCCH group.

[0130] The following describes some embodiments of providing HARQ-ACK feedback. Specifically, the following embodiments are provided: indicating the timing difference between the transmission of DL data transmission on a SCell in one CC and the transmission of HARQ-ACK feedback on a PCell or PUCCHSCell in another CC that has a different parameter set or TTI duration (hereinafter, "different parameter set or TTI duration with SCell") than the SCell used for DL ​​data transmission.

[0131] In some exemplary embodiments, the timing difference between a DL data transmission on a SCell in one CC and a HARQ-ACK feedback transmission on a PCell or PUCCH SCell in another CC with a different parameter set or TTI duration can be determined by a combination of higher-layer signaling and dynamic indications in the DCI of the PDCCH prior to the DL data transmission on the SCell. Specifically, a set of values ​​can be configured by higher-layer signaling, and the DCI can indicate a value from the configured values ​​for HARQ-ACK feedback timing. In this way, the transmitter of the data will know when to look for the HARQ-ACK corresponding to its data because that timing will be indicated in its DCI.

[0132] In some exemplary embodiments, the timing indication for HARQ-ACK feedback on a PCell or PUCCH SCell having a different parameter set or TTI duration than the SCell can be defined as follows: (1) based on the minimum subcarrier spacing of the two CCs used for PDSCH or PUCCH carrying HARQ-ACK; (2) based on the subcarrier spacing of the constant reference (e.g., 15 kHz); or (3) based on the subcarrier spacing of the CCs in which PDSCH or PUCCH is transmitted.

[0133] In some exemplary embodiments of HARQ-ACK feedback on PCells or PUCCH SCells with different parameter sets than the SCell, similar to the above... Figure 9 The cross-carrier scheduling between the PDCCH and PDSCH or PUSCH can define a two-element or two-step timing indication, as described below. Figure 13 As shown, in the first step, the timing in the time slot can be defined based on the parameter set used for transmitting the PDSCH, while in the second element or second step, the timing in the time slot can be defined based on the parameter set used for transmitting the PUCCH carrying HARQ-ACK feedback. Additionally, similar to the above... Figure 8 For example, in this context, single-element or single-step timing indicators can be further defined, as will be discussed below. Figure 14 More detailed description.

[0134] Figure 13An example of an embodiment of HARQ-ACK feedback on a PCell or PUCCH SCell with a mixed parameter set using a two-step timing indication process is shown in NR signaling diagram 1300. In the example shown, subcarrier spacings of 30 kHz and 120 kHz are used in CC#1 and CC#2, respectively. The DCI (not shown, and transmitted before PDSCH data transmission 1302) in PDCCH control transmission 1302 at CC#1 can be used to indicate the timing of HARQ-ACK 1304 at CC#2. CC#1 comprises a total of 3 time slots S0, S1, and S2, as shown, and CC#2 comprises a total of 12 time slots, numbered S0 to S3 within the first time slot boundary of CC#1, returning to S0 to S3 within each subsequent time slot boundary of CC#1, as shown. In the first step of the scheduling indication in DCI, a first timing indication can be defined based on the time slots of the subcarrier intervals in the CC transmitted using PDSCH, while in the second step of the scheduling indication, a second timing indication can be defined based on the time slots of the subcarrier intervals in the CC transmitted using HARQ-ACK. Figure 13 In this example, a slot delay in the DCI can be based on the subcarrier spacing used for transmitting the PDSCH in CC#1. Furthermore, the slot index S1 in the DCI can indicate which slot is used to transmit the PUCCH carrying HARQ-ACK feedback.

[0135] Although the PUCCH carrying HARQ-ACK in the attached diagram can span one time slot, this design can be extended to situations where a short PUCCH can be used to carry HARQ-ACK feedback for one or more symbols within a time slot. For example, in this case, a similar approach could be used. Figure 7 The micro-slot scheduling mechanism includes a micro-slot indication mechanism. For example, the PDSCH parameter set at CC#1 can be used to indicate the timing of the HARQ-ACK carried in the PUCCH at CC#2 by indicating the symbol of the PUCCH at CC#2 according to the symbol # of CC#1 (i.e., according to the subcarrier spacing of CC#1).

[0136] In some exemplary embodiments, the delay of HARQ-ACK timing can be derived as shown with respect to Formula 2 previously described.

[0137] Figure 14An example of an embodiment of HARQ-ACK feedback on a PCell or PUCCH SCell with different parameter sets or TTI durations is shown in NR signaling diagram 1400. In the example shown, subcarrier spacing of 30 kHz and 120 kHz are used in CC#1 and CC#2, respectively. The parameter set associated with PDSCH data transmission 1402 at CC#2 is shown and can be used to indicate PUCCH 1404 at CC#1. CC#1 includes a total of 3 time slots S0, S1, and S3, as shown in the diagram, and CC#2 includes a total of 12 time slots, numbered S0 to S3 within the first time slot boundary of CC#1, returning to S0 to S3 within each subsequent time slot boundary of CC#1, as shown in the diagram. Figure 14 In the example shown, the scheduling / timing delay (one slot delay) in the time slot between the end slot of PDSCH data transmission 1402 and the start slot of PUCCH control transmission 1404 can be derived based on the minimum subcarrier interval (which is 30 kHz in CC#1). (That is, the delay will be indicated as one slot delay based on the slot duration of the CC with the minimum subcarrier interval (i.e., CC#1). In particular, using Equation 1, in Figure 14 In the example, N delay =6, which can be indicated in the DCI. Therefore, I delay = 1 time slot.

[0138] In some exemplary embodiments, the use of one-step or two-step timing indication can be configured by higher-layer signaling, or predefined in the specification, or may depend on whether the SCell for PDSCH transmission has a larger subcarrier spacing or a shorter TTI duration (e.g., micro-slots) compared to the PCell or PUCCH SCell used for PUCCH transmission. For example, in cases where the SCell used for PDSCH transmission may have a smaller subcarrier spacing than the PCell or PUCCH SCell used for PUCCH transmission (e.g., as described above)... Figure 13 In cases where a two-element timing indicator can be applied, a PUCCH carrying HARQ-ACK feedback can be transmitted on the PCell or PUCCH SCell for the same duration as the duration the SCell is used to transmit the PDSCH.

[0139] In some exemplary embodiments, a single timing indication in the DCI can be used to indicate the HARQ-ACK feedback timing from a set of values ​​that can be configured by higher-level signaling. In this regard, reference is now made to… Figure 15a and 15bThe diagrams, within the context of NR signaling diagrams 1500a and 1500b, illustrate other embodiments of HARQ-ACK feedback on PCells or PUCCHSCells with different parameter sets or TTI durations than the SCell. The signaling diagrams also illustrate other embodiments of HARQ-ACK feedback on PCells or PUCCHSCells with different parameter sets or TTI durations than those already discussed. Figure 14 The parameter set described is the same as the parameter set.

[0140] exist Figure 15a In the diagram, multiple time slots are shown as PUCCH 1504a for transmitting HARQ-ACKs carrying PDSCH data transmission 1502a, and... Figure 15b The diagram illustrates a micro-slot structure for transmitting PUCCH 1504b carrying HARQ-ACK, to align the slot durations in the SCell where PDSCH data is transmitted. Figure 15b In this embodiment, in addition to RRC signaling, the ACK / NAK Resource Indicator (ARI) in the DCI of the PDCCH control transmission 1502b prior to PSDCH can indicate which of a set of resources can be used for the UE's HARQ-ACK feedback. For Figure 15a and 15b In two embodiments, a delay indicator can be indicated in the DCI only for the time slot using the minimum subcarrier interval in the CC, for scheduling PDSCH transmission.

[0141] In some exemplary embodiments, when the UE is configured with multiple CCs for HARQ-ACK feedback, dynamic CC switching for the transmission of the PUCCH carrying HARQ-ACK feedback can be employed for cross-carrier HARQ operation. Specifically, a field in the DCI or Media Access Control element (MAC-CE) can be used to indicate which CC can be used to transmit the PUCCH carrying HARQ feedback.

[0142] HARQ-ACK codebook design for NR carrier aggregation:

[0143] For carrier aggregation (CA) in LTE Rel-10, up to five component carriers (CCs) can be aggregated to support wider transmission bandwidths for peak data rates of 100MHz and higher. Furthermore, the UE can be configured with one primary cell (PCell) and multiple secondary cells (SCells), where the Physical Uplink Control Channel (PUCCH) is transmitted only in the PCell. This indicates that in cases where DL transmissions occur simultaneously on multiple CCs, HARQ-ACK feedback needs to be aggregated and transmitted on a single uplink CC.

[0144] In Rel-13 Enhanced Carrier Aggregation (eCA), the number of CCs is expanded to 32 for both DL and UL. Furthermore, Rel-13 compliant UEs can be configured to transmit UCIs on the PUCCH SCell in addition to the PCell, motivated by a desire to reduce control signaling overhead on the PCell. More specifically, CCs in Rel-13 can be grouped into primary PUCCH groups and secondary PUCCH groups. The PUCCH on the PCell is used to carry UCIs for the PCell and SCells within the primary PUCCH group, while the PUCCH on the PUCCH SCell is used to carry UCIs for SCells in the secondary PUCCH group.

[0145] For NR, it is anticipated that more spectrum, including unlicensed and carrier frequencies above 6 GHz, will become available. Given the support for a large number of CCs, it is more desirable to consider the LTE Rel-13eCA framework as a starting point for NR CAs, especially considering that PUCCHs carrying UCIs can be transmitted on both the PCell and the PUCCH SCell.

[0146] Considering that, for example, different parameter sets may be applied for DL ​​data transmission on different CCs when forming low-frequency bands (i.e., carrier frequencies below 6 GHz) and high-frequency bands (i.e., carrier frequencies above 6 GHz) for carrier aggregation, certain enhancements need to be considered for the design of HARQ-ACK codebooks for carrier aggregation with the same or mixed parameter sets and different transmission time interval (TTI) durations.

[0147] Some embodiments of this document relate to the design of HARQ-ACK codebooks for NR carrier aggregation. Specifically, embodiments may include one or more of the following aspects: (1) a semi-static HARQ-ACK codebook for carrier aggregation with the same or mixed parameter sets or TTI durations; (2) a dynamic HARQ-ACK codebook for carrier aggregation with the same or mixed parameter sets or TTI durations. Embodiments can be applied when different CCs have different slot durations. For example, HARQ-ACK feedback for corresponding PDSCH data transmission at a high frequency band can be transmitted on a low-frequency PUCCH, where different parameter sets or slot durations are used for the low-frequency and high-frequency CCs, respectively. Furthermore, different TTI durations can refer to the application of slots or microslots to the transmission.

[0148] For HARQ-ACK codebook design used in NR carrier aggregation, a key issue is ensuring that the gNB and UE have the same understanding of the total number and order of HARQ-ACK feedback bits. More specifically, NR can support semi-static or dynamic HARQ-ACK codebooks for carrier aggregation, and embodiments of each are described below. The use of a semi-static or dynamic HARQ-ACK codebook can be configured by higher layers via NR MSI, NR RMSI, NR OSI, and / or RRC signaling.

[0149] According to some exemplary embodiments, if the UE does not support simultaneous transmission of different parameter sets, it can be assumed that the same parameter set or TTI duration is applied to the PUCCHs transmitted on PCell and PUCCHSCell. Furthermore, if the gNB schedules different parameter sets or TTI durations for the two PUCCH transmissions, it may be necessary to define certain drop rules or priority rules. For example, the UE may drop a PUCCH with a larger subcarrier spacing.

[0150] Semi-static HARQ-ACK codebook for carrier aggregation with the same or mixed parameter sets or TTI durations

[0151] According to the first embodiment, for a semi-static HARQ-ACK codebook, the total number of HARQ-ACK bits can be derived based on the number of configured CCs and / or the size of the corresponding HARQ-ACK aggregation window. The latter can be applied to Frequency Division Duplex (FDD) or Dynamic Time Division Duplex (TDD) systems, where HARQ-ACK feedback for multiple DL transmissions can be aggregated and carried by a single PUCCH. If the UE misses detecting the PDCCH used for scheduling data transmission or fails to decode the PDSCH data transmission, the UE can feed back a negative acknowledgment (NACK) in the corresponding CC and time slot.

[0152] According to one embodiment, the number of CCs used for carrier aggregation can be configured via dedicated RRC signaling. Additionally, the HARQ-ACK aggregation window size can be predefined in the NR specification, or configured via NR MSI, NR RMSI, NR OSI, or RRC signaling, or dynamically indicated in the downlink control information (DCI) within the PDCCH control transmission prior to PDSCH data transmission, or a combination thereof. In the latter case, a set of values ​​can be configured by a higher layer, and a field in the DCI can be used to indicate which of the configured values ​​is used to indicate the HARQ-ACK aggregation window size.

[0153] Figure 16An example of an embodiment for HARQ-ACK feedback for carrier aggregation with the same or mixed parameter sets or TTI durations is shown in the form of NR signaling diagram 1600. In the example shown, downlink transmission 1602 includes a series of PDCCH control transmissions 1604 and a series of corresponding PDSCH data transmissions 1606, and uplink transmission 1608 represents a PUCCH control transmission, which is separated from the downlink transmission by a guard period GP 1610. Time slots are named S1-S8. Figure 16 An example embodiment of a CC HARQ-ACK aggregation window is shown. In the example shown, the HARQ-ACK aggregation window size is 4 time slots, as shown in the figure, where HARQ-ACK feedback for 4 DL transmissions S0 to S7 can be aggregated and carried by PUCCH control transmission 1608.

[0154] The following describes some embodiments of a semi-static HARQ-ACK codebook for carrier aggregation with the same or mixed parameter sets.

[0155] In some embodiments, when the same or different parameter sets or TTI durations are used for multiple CCs, the order of HARQ-ACK bits can be incremented in either a time-first-frequency or frequency-first-time manner for both TDD and FDD. Figure 17a and 17b This pertains to a corresponding embodiment for ordering HARQ-ACK bits when using the same parameter set or TTI duration for multiple CCs, while Figure 18a and 18b This relates to a corresponding embodiment for ordering HARQ-ACK bits when using different parameter sets or TTI durations among multiple CCs. Figure 17a and 18a The illustrated embodiment sorts the HARQ-ACK bits in a time-first, then frequency-second manner, while Figure 17b and 18b The HARQ-ACK bits are sorted in a frequency-first, then time manner.

[0156] Figure 17a An example of an embodiment for cross-carrier multi-slot scheduling is shown in NR signaling diagram 1700a. In the example shown, the same parameter set or TTI duration is used in CC#0, CC#1, and CC#2, respectively. In this case, the HARQ-ACK feedback can order its bits in the UCI in a time-first, frequency-second manner, as follows: Figure 17aThe dashed arrow 1702a in the diagram shows four time slots per CC, S1-S12, where the aggregation window for HARQ-ACK is four time slots. The bits in HARQ-ACK will track the data transmission in the CC, starting at CC#0, from S1 through S4, then tracking different frequencies at CC#1, starting at S5 through S8, then tracking different frequencies at CC#2 until the end, passing through S9 through S12 of CC#2.

[0157] Figure 17b An example of an embodiment for cross-carrier multi-slot scheduling is shown in the form of NR signaling diagram 1700b. In the example shown, similar to... Figure 17a The same parameter set or TTI duration is used in CC#0, CC#1, and CC#2, respectively. In this case, the HARQ-ACK feedback can order its bits in the UCI in a frequency-first, time-second manner, such as... Figure 17b The dashed arrows in the diagram illustrate this. It shows four time slots per CC, and the aggregation window for HARQ-ACK is four time slots. Therefore, the bits in HARQ-ACK will track the data transmission in the CCs, starting from S1 of CC#0, moving to S5 of CC#1 and S9 of CC#2, first moving in frequency, then tracking S2# of CC#0, S6 of CC#1 and S10 of CC#2, and then returning in time to S3 of CC#0, S7 of CC#1 and S11 of CC#2, finally returning in time to S4 of CC#0 to S8 of CC#1, and finally to S12 of CC#2.

[0158] When using different parameter sets or TTI durations for multiple CCs, according to some embodiments, the HARQ-ACK aggregation window can be defined based on the minimum subcarrier spacing or maximum TTI duration among the configured CCs, or based on the 1ms subframe duration, regarding the slot duration. For semi-static HARQ-ACK codebook designs with different parameter sets, the total codebook size can be determined by the number of configured CCs, the HARQ-ACK aggregation window size, and the difference in subcarrier spacing or slot duration between CCs. The following... Figure 18a and 18b An example embodiment is described for sorting bits in HARQ-ACK feedback for transmissions in CC with different parameter sets or TTI durations.

[0159] Figure 18a and 18bAn example of a corresponding embodiment for cross-carrier multi-slot scheduling with different or mixed parameter sets among multiple CCs is shown in the form of respective NR signaling diagrams 1800a and 1800b. In the example shown, different parameter sets or TTI durations are used between CC#0 and CC#2 and CC#1. CC#0 and CC#2 have subcarrier spacing corresponding to 30 kHz, while CC#1 has subcarrier spacing corresponding to 15 kHz. Four slots S1 to S4 are shown for CC#0, slots S5 to S6 are shown for CC#1, and slots S7 to S10 are shown for CC#2, wherein the aggregation window for HARQ-ACK is defined based on the slot duration of the CC with the smallest subcarrier spacing (in the illustrated embodiment, the slot spacing of CC#0 or CC#2 corresponding to 15 kHz). Therefore, here, the HARQ-ACK window corresponds to two slots in the 15 kHz subcarrier spacing CC.

[0160] As in Figure 18a As seen in NR signaling diagram 1800a, HARQ-ACK feedback allows its bits to be ordered in the UCI in a time-first, then frequency-second manner, such as... Figure 18a As shown by the dashed arrow in the diagram. The bits in HARQ-ACK will track the data transmission of CC, starting from S1 to S4 of CC#0, then tracking S5 to S6 of CC#1, and then tracking S7 to S10 of CC#2.

[0161] As in Figure 18b As seen in NR signaling diagram 1800b, HARQ-ACK feedback allows its bits to be ordered in the UCI in a frequency-first, time-second manner, such as... Figure 18b As shown by the dashed arrow in the diagram. The bits in HARQ-ACK will track the data transmission in CC, starting from S1 of CC#0, moving to S5 of CC#1, then to S7 of CC#2, then tracking S2 of CC#0, S8 of CC#2, then tracking S3 of CC#0, S6 of CC#1, S9 of CC#2, S4 of CC#0, and S10 of CC#2.

[0162] In another embodiment, when different parameter sets or TTI durations are used for multiple CCs, the following can be used: Figure 18a and 18b This involves a hybrid approach. According to this embodiment, the order of the HARQ-ACK bits can first increment temporally, and then, after reaching the slot boundary, it can increment frequency-wise. Subsequently, after reaching all configured CCs within the slot time, it can again increment temporally. Note that the slot boundary or slot duration can be defined based on the minimum subcarrier spacing or maximum TTI duration of the configured CCs, or based on the 1ms subframe duration.

[0163] Figure 19 An example of the above embodiment is shown, illustrating the order of HARQ-ACK bits for carrier aggregation with different parameter sets or TTI durations. In this example, NR signaling diagram 1900 is similar to... Figure 18a and 18b One of the examples shown has all CCs having the same parameter set. Additionally, similar to... Figure 18a and 18b Implementation examples, Figure 19 In this embodiment, the slot boundaries are defined using a 15kHz SC in CC#1. Here, the bits in the HARQ-ACK will track the data transmission in CC, starting at S1 of CC#0, continuing to S2 of CC#0, until they reach slot boundary 1903, which is defined with respect to the slot duration of CC#1 (with the shortest subcarrier spacing of 15kHz). Then, the bits will track S5 of CC#1, and once they reach slot boundary 1903 again, the bits will track S7 of CC#2, then S8 of CC#2, at which point, once they reach slot boundary 1903 again, they will move in the same manner to track S3, S4, S6, S9, and S10.

[0164] In another embodiment, when different parameter sets or TTI durations are used for multiple CCs, HARQ-ACK feedbacks for each parameter set or TTI duration can be grouped and transmitted on the corresponding PUCCHs in the SCell. In other words, according to this embodiment, only HARQ-ACK feedbacks for the same parameter set or TTI duration can be aggregated and carried by the same PUCCH SCell. The above embodiments can be applied to the semi-static HARQ-ACK codebook determination as described above and the dynamic HARQ-ACK codebook determination described below.

[0165] If the number of PUCCH SCells is less than the parameter set or TTI duration in the configured CC, discarding rules or priority rules can be defined to allow the UE to discard some PUCCHs on the PUCCH SCells. Discarding rules can be defined according to the order of subcarrier intervals in the CC. For example, the smallest subcarrier interval can have the highest priority, and the largest subcarrier interval can have the lowest priority. Alternatively, discarding rules can be configured by higher layers via NRMSI, NR RMSI, NR OSI, or RRC signaling, or can be defined according to the UE's capabilities.

[0166] Dynamic HARQ-ACK codebook for carrier aggregation with the same or mixed parameter sets or TTI duration:

[0167] Use a static HARQ-ACK codebook when different parameter sets or TTI durations are used among the configured CCs (e.g.) Figure 18a , 18b As taught in 19, HARQ-ACK feedback uses bits to correspond to time slots that may or may not be scheduled for data. To conserve resources regarding the HARQ-ACK codebook, a dynamic HARQ-ACK mechanism for carrier aggregation can be used to allow HARQ-ACK feedback to use bits only for the scheduled time slots used to carry data.

[0168] For the dynamic HARQ-ACK codebook used for carrier aggregation, the downlink dispatch index (C-DAI) and total DAI (T-DAI) can be indicated in the DCI of the PDCCH used to schedule DL data transmission over multiple CCs. Furthermore, the sizes of C-DAI and T-DAI can be fixed, for example, 2 bits each. Although both C-DAI and T-DAI are used in the following embodiments, in some cases, only C-DAI may be used for dynamic HARQ-ACK determination.

[0169] DAI can be divided into two types: Counter DAI (C-DAI) and Total DAI (T-DAI). For PDSCH data transmission scheduled for different cells within the same subframe, C-DAI can have a continuously increasing value. Alternatively, for PDSCH data transmission scheduled for different cells in different subframes, C-DAI can have a continuously increasing value. The T-DAI value can be increased for each subframe in which each cell is scheduled for PDSCH data. For dynamic HARQ-ACK codebook determination, if spatial binding is not configured, two HARQ-ACK bits can be reported per serving cell, regardless of the transport mode, as long as there is at least one serving cell configured to support a 2-Transport Block (TB) transport mode. This helps avoid uncertainty in the total number of HARQ-ACK bits between the gNB and the UE.

[0170] The following will be about Figure 20a , 20b Articles 20c describe some embodiments of dynamic HARQ-ACK codebooks for carrier aggregation with the same or mixed parameter sets.

[0171] When using different parameter sets or TTI durations for multiple CCs, according to some embodiments, the HARQ-ACK aggregation window can be defined with respect to the slot duration based on a predetermined subcarrier interval (e.g., maximum or minimum subcarrier interval) or a predetermined TTI duration in the configured CCs, or based on the 1ms subframe duration. The following... Figures 20a-20cAn example embodiment is described for sorting bits in HARQ-ACK feedback for transmissions in CC with different parameter sets or TTI durations.

[0172] In particular, Figures 20a-20c Various options for C-DAI and T-DAI mapping for different parameter sets or TTI durations are depicted. As seen in the figures, according to one embodiment, C-DAI can be incremented in a time-first-frequency manner or a frequency-first-time manner, or by using a combination of both methods. Furthermore, in the case of using the frequency-first-time method, according to one embodiment, the T-DAI of each time slot can be determined and incremented in each time slot until the current time slot. Additionally, when using different parameter sets or TTI durations for multiple CCs, the time slot boundary can be based on the maximum subcarrier spacing or minimum TTI duration among the scheduled or configured CCs, or it can be based on a 1ms subframe duration. Alternatively, the time slot boundary can be based on the minimum subcarrier spacing or 1ms subframe duration among the configured or scheduled CCs. In this case, the number of scheduled CCs can be counted to determine the T-DAI within the time slot duration using the minimum subcarrier spacing or 1ms subframe duration.

[0173] Although Figures 20a-20c As shown, T-DAI is represented as the exact total number of scheduled DL transmissions, but in DCI, according to one embodiment, it can be signaled as a modulo operation. For example, for 2-bit T-DAI, DCI can signal T-DAI as mod(T-DAI+1,4).

[0174] Figures 20a-20cA corresponding embodiment of cross-carrier multi-slot scheduling for carrier aggregation using a dynamic HARQ-ACK codebook is shown in the form of corresponding NR signaling diagrams 2000a-2000c. In the example shown, different parameter sets or TTI durations are used between CC#0 and CC#2 and CC#1. CC#0 and CC#2 have subcarrier spacing corresponding to 30 kHz, while CC#1 has a subcarrier spacing corresponding to 15 kHz. Four slots S1 to S4 are shown for CC#0, slots S5 and S6 are shown for CC#1, and slots S7 to S10 are shown for CC#2. In the embodiment shown, the aggregation window for HARQ-ACK is defined with respect to duration based on the CC with the smallest subcarrier spacing (in the embodiment shown, corresponding to a slot spacing of 15 kHz for CC#0 or CC#2). Therefore, here, the HARQ-ACK window corresponds to two slots in the 15 kHz subcarrier spacing CC. According to the dynamic HARQ-ACK codebook scheme used for carrier aggregation, the bits in the HARQ-ACK codebook corresponding to the DL time slots used for data transmission (i.e., representing ACK or NACK for DL ​​data transmission) only correspond to the DL time slots that are to contain the scheduled data, and do not include any bits corresponding to the unscheduled DL time slots within the configured CC.

[0175] Furthermore, when using different parameter sets or TTI durations for multiple CCs, the slot boundaries can be based on the maximum subcarrier spacing or minimum TTI duration among the scheduled or configured CCs. Figure 20c (as in the case mentioned above), or it can be based on the 1ms subframe duration. Alternatively, the slot boundary can be based on the minimum subcarrier spacing or the 1ms subframe duration among the configured or scheduled CCs. The number of scheduled CCs can be counted to determine the T-DAI within the aforementioned slot duration (minimum or maximum) or 1ms subframe duration.

[0176] As in Figure 20a As seen in NR signaling diagram 2000a, HARQ-ACK feedback allows its bits to be ordered in the UCI in a time-first, then frequency-second manner, such as... Figure 20a As shown by the dashed arrow in the diagram. According to the dynamic scheme, the bits in HARQ-ACK will track the data transmission in CC, starting with S1 of CC#0, then S4 of CC#0, skipping unscheduled S2 and S3, then skipping unscheduled S5 and tracking S6 in CC#1, then tracking S7 in CC#2, then skipping unscheduled S8 and tracking S9 and S10.

[0177] Using the time-first-frequency method Figure 20aIn this case, according to one embodiment, the T-DAI of each time slot can be determined and incremented in each time slot until the current time slot. For example, in Figure 20a In the HARQ-ACK window, the T-DAI (based on a minimum subcarrier spacing of 15 kHz) for the duration of the first slot is 6 scheduled slots. For different scheduled CC slots, C-DAI can have values ​​that increase continuously in a frequency-first, then time manner. Note that C-DAI cannot exceed a value of 4, so when it is about to reach 5, it returns to 1, as shown in the figure, and then increments again starting from 1.

[0178] As in Figure 20b As seen in the NR signaling diagram 2000b, HARQ-ACK feedback allows its bits to be ordered in the UCI in a frequency-first, time-second manner, such as... Figure 20b As shown by the dashed arrows in the diagram. According to the dynamic scheme, the bits in HARQ-ACK will track the data transmission in CC, starting with S1 in CC#0, then skipping the unscheduled S5 in CC#1, tracking S7 in CC#2, then skipping the unscheduled S2 in CC#0, then skipping the unscheduled S5 in CC#1, then tracking S8 in CC#2, then skipping the unscheduled S3 in CC#0, then tracking S6 in CC#1, then skipping the unscheduled S9 in CC#2, then tracking S4 in CC#0, S6 in CC#1, and S10 in CC#2.

[0179] Using the frequency-first-time-later method Figure 20b In this case, according to one embodiment, the T-DAI of each time slot can be determined and incremented in each time slot until the current time slot. For example, in Figure 20bIn the HARQ-ACK window, the T-DAI for the first time slot duration (based on the maximum subcarrier spacing of 30 kHz) is 2 (2 scheduled time slots); the T-DAI for the second time slot duration is 3 (2 scheduled time slots from the first time slot duration and 1 scheduled time slot from the second time slot duration); the T-DAI for the third time slot duration is 4 (2 scheduled time slots from the first time slot duration, 1 scheduled time slot from the second time slot duration, and 1 scheduled time slot from the third time slot duration); and the T-DAI for the fourth (last) time slot duration is 6 (2 scheduled time slots from the first time slot duration, 1 scheduled time slot from the second time slot duration, 1 scheduled time slot from the third time slot duration, and 2 scheduled time slots from the fourth time slot duration). Furthermore, when using different parameter sets or TTI durations for multiple CCs, the slot boundaries can be based on the maximum subcarrier spacing or minimum TTI duration among the scheduled or configured CCs. Figure 20c (as in the case mentioned above), or it can be based on a 1ms subframe duration. Alternatively, the slot boundary can be based on the minimum subcarrier spacing or a 1ms subframe duration among the configured or scheduled CCs. In this case, the number of scheduled CCs can be counted to determine the T-DAI within the slot duration using the minimum subcarrier spacing or the 1ms subframe duration.

[0180] As in Figure 20c As seen in the NR signaling diagram 2000c, it can be used Figure 20a and 20b This involves a hybrid approach. According to this embodiment, the HARQ-ACK bits can be incremented sequentially, first time-wise, and then frequency-wise after reaching the time slot boundary. Subsequently, after reaching all configured CCs within the time slot, it is incremented again sequentially. Figure 20c In the HARQ-ACK, the bits will track the data transmission in CC, starting with S1 of CC#0, then skipping the unscheduled S2 of CC#0 until it reaches the slot boundary 2003 defined for the slot duration of CC#1 (which has a minimum subcarrier spacing of 15 kHz). The bits will then track S5 of CC#1, and once again reach slot boundary 2003, the bits will track S7 of CC#2, then S8 of CC#2. At this point, once again reaching slot boundary 1903, they will move in the same manner to track S3, S4, S6, S9, and S10.

[0181] for Figure 20cIn one embodiment, the T-DAI of each time slot can be determined and incremented in each time slot until the current time slot. Here, the time slot boundaries are based on a time-first, frequency-second approach, reaching the duration of the first time slot, and then the duration of the second time slot. Figure 20c In this context, the time slot duration is based on a minimum subcarrier spacing of 15 kHz. The T-DAI used for the first time slot duration is 4 scheduled time slots, and the T-DAI used for the second time slot duration is 6 scheduled time slots (4 scheduled time slots from the first time slot duration and 2 scheduled time slots from the second time slot duration).

[0182] Depending on the implementation, when using the same parameter set or TTI duration for multiple CCs, the C-DAI can be incremented for both TDD and FDD using either a frequency-first, time-later approach or a time-first, frequency-later approach. Furthermore, in the frequency-first, time-later approach, the T-DAI for each scheduled time slot can be determined and incremented until the currently scheduled time slot, where the time slot duration can be based on the subcarrier spacing within the scheduled or configured CCs, or it can be based on a 1ms subframe duration. In the time-first, frequency-later approach, the individual T-DAI within the HARQ-ACK aggregation window can be determined based on the total number of scheduled CCs within the HARQ-ACK aggregation window. In the time-first, frequency-later approach, the individual T-DAI within the HARQ-ACK aggregation window can be determined based on the total number of scheduled CCs within the HARQ-ACK aggregation window, where the HARQ-ACK aggregation window can be defined based on the minimum subcarrier spacing or the maximum TTI duration among the CCs.

[0183] Example

[0184] Example 1 includes an apparatus for a base station, the apparatus comprising: a memory storing logic; and processing circuitry coupled to the memory for implementing the following logic: determining a physical downlink control channel (PDCCH) on a first component carrier; encoding a first signal to be transmitted on the PDCCH, the first signal including downlink control information (DCI) on resources for a second signal to be transmitted on a second component carrier, wherein the DCI is based on a predetermined set of parameters, and wherein the parameter sets of the first component carrier and the second component carrier are different from each other; and causing the first signal to be transmitted on the PDCCH, wherein a receiver of the second signal processes the second signal based on the control information in the first signal.

[0185] Example 2 includes the apparatus described in Example 1, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the processing circuitry is further configured to: determine a physical downlink shared channel (PDSCH) on the second component carrier; encode the data signal for transmission on the PDSCH; and, based on the downlink control information, induce the transmission of the data signal to the receiver.

[0186] Example 3 includes the apparatus described in Example 1, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal being a data signal, and the base station being a receiver of the second signal, and the processing circuitry is further configured to: detect the Physical Uplink Shared Channel (PUSCH) on the second component carrier; and decode the data signal received on the PUSCH based on the downlink control information.

[0187] Example 4 includes the apparatus described in Example 2, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the base station is a receiver of the second signal, and the processing circuitry is further configured to: determine a Physical Downlink Shared Channel (PDSCH); encode a data signal for transmission on the PDSCH; induce transmission of the data signal; detect a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); and decode the HARQ-ACK signal received on the PUCCH, the HARQ-ACK signal being associated with the data signal on the PDSCH, based on the downlink control information.

[0188] Example 5 includes the apparatus described in Example 1, and optionally, the downlink control information includes a time slot index of the transmission of the second signal for indicating the time slot of the resource.

[0189] Example 6 includes the apparatus described in Example 5, and optionally, wherein the DCI includes a joint resource allocation field for indicating the downlink control information, and the downlink control information includes information about the time slot and the symbols within the time slot.

[0190] Example 7 includes the apparatus described in Example 1, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the timing between the first signal on the PDCCH and the second signal on the scheduled PDSCH or Physical Uplink Shared Channel (PUSCH) is configured via higher-layer signaling, indicated by a combination of the higher-layer signaling and dynamic indications in the DCI of the first signal, or only explicitly indicated in the DCI.

[0191] Example 8 includes the apparatus described in Example 1, and optionally, wherein the downlink control information provides a two-element timing indication regarding the resource, wherein a first timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a component carrier (CC) transmitted using the PDCCH, and a second timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a CC transmitted using one of the PDSCH, the Physical Uplink Shared Channel (PUSCH), or the Physical Uplink Control Channel (PUCCH) carrying a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal.

[0192] Example 9 includes the subject matter described in Example 1, and optionally, the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the downlink control information includes micro-timeslot information, the micro-timeslot information including a symbol index for indicating symbols of resources.

[0193] Example 10 includes the subject matter of any one of Examples 1-3, wherein the resource includes at least one of a time slot index, a symbol index, or a timing indication of the resource, and the predetermined parameter set is defined according to: a subframe boundary; a time slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carrier in which the PDCCH or the data signal is transmitted; or a parameter set that is always 15 kHz.

[0194] Example 11 includes the subject matter of any one of Examples 1-3, and optionally, wherein: the downlink control information includes scheduling information regarding scheduling resources for the data signal, the scheduling information including a timing indication; and wherein the timing indication includes an indication of a timing delay between the end of the PDCCH and the data signal, a predetermined set of parameters for the indication of the timing delay being based on a parameter set of the data signal.

[0195] Example 12 includes the subject matter described in Example 4, and optionally, the resource includes a timing indication, the predetermined parameter set being defined according to: a subframe boundary; a slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carriers in which the PDSCH or the PUCCH is transmitted; or a parameter set always 15 kHz.

[0196] Example 13 includes the subject matter described in Example 4, and optionally, wherein: the scheduling information includes a timing indication; the first signal includes a downlink control information (DCI) signal on the PDCCH; and wherein the timing indication includes an indication of a timing delay, the predetermined set of parameters for the indication of the timing delay being based on the parameter set of the PDCCH.

[0197] Example 14 includes the subject matter described in Example 1, and optionally, wherein: the downlink control information includes scheduling information regarding scheduling resources for a data signal; the second signal includes the data signal; and the resources include multiple time slots.

[0198] Example 15 includes the subject matter described in Example 14, and optionally, the downlink control information includes a slot group index for indicating each slot group among the plurality of slots.

[0199] Example 16 includes the subject matter described in Example 1, wherein: the first signal includes a first-level downlink control information (DCI) signal on the PDCCH; the downlink control information is a first-level DCI; the processing circuitry is further configured to: encode a second-level DCI for transmission on the PDSCH, the second-level DCI including a second-level DCI on the resource; and cause the transmission of the first-level DCI and the second-level DCI to the receiver; and cause the transmission of a data signal to the receiver based on the first-level DCI and the second-level DCI.

[0200] Example 17 includes the subject matter of any one of Examples 2-3, and optionally, wherein the PDCCH is used to schedule high-frequency data signals, and wherein the downlink control information includes at least one of beampup link index, configuration parameters of phase tracking reference signal (PT-RS), or indication of probe reference signal (SRS) resource (SRI).

[0201] Example 18 includes the subject matter described in Example 1, and optionally, wherein the resource includes the size and order of bits in a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the base station being a receiver of the second signal, and the processing circuitry is further configured to: determine a Physical Downlink Shared Channel (PDSCH); encode a data signal for transmission on the PDSCH; induce transmission of the data signal; detect a Physical Uplink Control Channel (PUCCH) on the second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); and decode the HARQ-ACK signal based on the control information, the HARQ-ACK signal being received on the PUCCH and associated with the data signal on the PDSCH.

[0202] Example 19 includes the subject matter described in Example 18, and optionally, the processing circuitry is further configured to: encode and induce transmission of a dedicated radio resource control (RRC) signal, the RRC signal indicating the number of configured component carriers, including the first component carrier and the second component carrier, and the size of the HARQ-ACK aggregation window for the HARQ-ACK signal.

[0203] Example 20 includes the subject matter described in Example 18, and optionally, wherein the first signal includes a downlink control information (DCI) signal, and the processing circuitry is further configured to: configure a HARQ-ACK aggregation window size for the HARQ-ACK signal via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling; or indicate the HARQ-ACK aggregation window size in the DCI.

[0204] Example 21 includes the subject matter described in Example 18, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the order of bits in the HARQ-ACK signal corresponds to the incrementing order of resources in the PDSCH: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding time slot used for the PDSCH.

[0205] Example 22 includes the subject matter described in Example 21, and optionally, wherein the DCI is based on the HARQ-ACK aggregation window size for the HARQ-ACK signal, and wherein the HARQ-ACK aggregation window size is based on the predetermined parameter set, which is defined according to: the minimum subcarrier interval among the configured component carriers including the first component carrier and the second component carrier; or a 1ms subframe duration.

[0206] Example 23 includes the subject matter described in Example 18, and optionally, wherein the HARQ-ACK feedback includes an aggregation of HARQ-ACK feedbacks, each HARQ-ACK feedback on a corresponding PCell or PUCCH SCell having a corresponding parameter set, each corresponding parameter set also corresponding to a parameter set of the data signal associated with each HARQ-ACK feedback.

[0207] Example 24 includes the subject matter described in Example 18, and optionally, wherein the HARQ-ACK feedback is based on: the size and order of the bits in the HARQ-ACK feedback corresponding to a static HARQ-ACK codebook on which all slots of the PDSCH are based; or the size and order of the bits in the HARQ-ACK feedback corresponding only to a dynamic HARQ-ACK codebook on which the scheduled slots of the PDSCH are based.

[0208] Example 25 includes the subject matter described in Example 24, and optionally, when the HARQ-ACK feedback is based on a dynamic HARQ-ACK codebook, the downlink control information includes information about the counter downlink dispatch index (C-DAI) and the total downlink dispatch index (T-DAI) corresponding to the PDSCH.

[0209] Example 26 includes the subject matter described in Example 25, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the C-DAI is incremented in the following manner: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding subframe used for the PDSCH.

[0210] Example 27 includes the subject matter described in Example 1, and optionally includes a front-end module coupled to the processing circuitry.

[0211] Example 28 includes the subject matter described in Example 1, and optionally includes at least one antenna coupled to the front-end module.

[0212] Example 29 includes the topics described in Example 28, and optionally also includes NR Evolution Node B (gNodeB).

[0213] Example 30 is a product comprising one or more tangible computer-readable non-transitory storage media, including computer-executable instructions operable to, when executed by at least one computer processor of a base station, enable the at least one computer processor to perform operations at the base station, the operations comprising: determining a physical downlink control channel (PDCCH) on a first component carrier; encoding a first signal to be transmitted on the PDCCH, the first signal including downlink control information (DCI) on resources for a second signal to be transmitted on a second component carrier, wherein the DCI is based on a predetermined set of parameters, and wherein the parameter sets of the first component carrier and the second component carrier are different from each other; and causing transmission of the first signal on the PDCCH, wherein a receiver of the second signal processes the second signal based on the control information in the first signal.

[0214] Example 31 includes the subject matter described in Example 30, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the operation further includes: determining a physical downlink shared channel (PDSCH) on the second component carrier; encoding the data signal for transmission on the PDSCH; and inducing transmission of the data signal to the receiver based on the downlink control information.

[0215] Example 32 includes the subject matter described in Example 30, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal being a data signal, and the base station being a receiver of the second signal, and the operation further includes: detecting a physical uplink shared channel (PUSCH) on the second component carrier; and decoding the data signal received on the PUSCH based on the downlink control information.

[0216] Example 33 includes the subject matter described in Example 31, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the base station being a receiver of the second signal, the operation further includes: determining a Physical Downlink Shared Channel (PDSCH); encoding a data signal for transmission on the PDSCH; inducing transmission of the data signal; detecting a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); and decoding the HARQ-ACK signal received on the PUCCH, the HARQ-ACK signal being associated with the data signal on the PDSCH, based on the downlink control information.

[0217] Example 34 includes the subject matter described in Example 30, and optionally, the downlink control information includes a time slot index of the transmission of the second signal to indicate the time slot of the resource.

[0218] Example 35 includes the subject matter described in Example 34, and optionally, wherein the DCI includes a joint resource allocation field for indicating the downlink control information, and the downlink control information includes information about the time slot and the symbols within the time slot.

[0219] Example 36 includes the subject matter described in Example 30, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the timing between the first signal on the PDCCH and the second signal on the scheduled PDSCH or Physical Uplink Shared Channel (PUSCH) is configured via higher-layer signaling, indicated by a combination of dynamic indications in the higher-layer signaling and the DCI of the first signal, or only explicitly indicated in the DCI.

[0220] Example 37 includes the subject matter described in Example 30, and optionally, wherein the downlink control information provides a two-element timing indication regarding the resource, wherein a first timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a component carrier (CC) transmitted using the PDCCH, and a second timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a CC transmitted using one of the PDSCH, the Physical Uplink Shared Channel (PUSCH), or the Physical Uplink Control Channel (PUCCH) carrying a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal.

[0221] Example 38 includes the subject matter described in Example 30, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the downlink control information includes micro-timeslot information, the micro-timeslot information including a symbol index for indicating symbols of resources.

[0222] Example 39 includes the subject matter of any one of Examples 30-32, wherein the resource includes at least one of a time slot index of the resource, a symbol index of the resource, or a timing indication, and the predetermined parameter set is defined according to: a subframe boundary; a time slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carrier in which the PDCCH or the data signal is transmitted; or a parameter set that is always 15 kHz.

[0223] Example 40 includes the subject matter of any one of Examples 30-32, wherein: the downlink control information includes scheduling information regarding scheduling resources for a data signal, the scheduling information including a timing indication; and wherein the timing indication includes an indication of a timing delay between the end of the PDCCH and the data signal, a predetermined set of parameters for the indication of the timing delay being based on a parameter set of the data signal.

[0224] Example 41 includes the subject matter described in Example 33, and optionally, the resource includes a timing indication, the predetermined parameter set being defined according to: a subframe boundary; a slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carriers in which the PDSCH or the PUCCH is transmitted; or a parameter set always 15 kHz.

[0225] Example 42 includes the subject matter described in Example 33, and optionally, wherein: the scheduling information includes a timing indication; the first signal includes a downlink control information (DCI) signal on the PDCCH; and wherein the timing indication includes an indication of a timing delay, the predetermined set of parameters for the indication of the timing delay being based on the parameter set of the PDCCH.

[0226] Example 43 includes the subject matter described in Example 30, and optionally, wherein: the downlink control information includes scheduling information regarding scheduling resources for a data signal; the second signal includes the data signal; and the resources include multiple time slots.

[0227] Example 44 includes the subject matter described in Example 43, and optionally, the downlink control information includes a slot group index for indicating each slot group among the plurality of slots.

[0228] Example 45 includes the subject matter described in Example 30, wherein: the first signal includes a first-level downlink control information (DCI) signal on the PDCCH; the downlink control information is a first-level DCI; the operation further includes: encoding a second-level DCI for transmission on the PDSCH, the second-level DCI including a second-level DCI on the resource; and inducing the transmission of the first-level DCI and the second-level DCI to the receiver; and inducing the transmission of a data signal to the receiver based on the first-level DCI and the second-level DCI.

[0229] Example 46 includes the subject matter of any one of Examples 31-32, wherein the PDCCH is used to schedule high-frequency data signals, and wherein the downlink control information includes at least one of beampup link index, configuration parameters of phase tracking reference signal (PT-RS), or indication of probe reference signal (SRS) resource (SRI).

[0230] Example 47 includes the subject matter described in Example 30, and optionally, wherein the resource includes the size and order of bits in a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the base station being a receiver of the second signal, the operation further including: determining a Physical Downlink Shared Channel (PDSCH); encoding a data signal for transmission on the PDSCH; inducing transmission of the data signal; detecting a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); and decoding the HARQ-ACK signal based on the control information, the HARQ-ACK signal being received on the PUCCH and associated with the data signal on the PDSCH.

[0231] Example 48 includes the subject matter described in Example 47, and optionally, the operation further includes: encoding and causing the transmission of a dedicated radio resource control signal (RRC signal), the RRC signal indicating the number of configured component carriers, including the first component carrier and the second component carrier, and the size of the HARQ-ACK aggregation window for the HARQ-ACK signal.

[0232] Example 49 includes the subject matter described in Example 47, and optionally, wherein the first signal includes a downlink control information (DCI) signal, and the operation further includes at least one of the following: configuring a HARQ-ACK aggregation window size for the HARQ-ACK signal via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling; or indicating the HARQ-ACK aggregation window size in the DCI.

[0233] Example 50 includes the subject matter described in Example 47, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the order of bits in the HARQ-ACK signal corresponds to the incrementing order of resources in the PDSCH: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding time slot used for the PDSCH.

[0234] Example 51 includes the subject matter described in Example 50, and optionally, wherein the DCI is based on the HARQ-ACK aggregation window size for the HARQ-ACK signal, and wherein the HARQ-ACK aggregation window size is based on the predetermined parameter set, which is defined according to: the minimum subcarrier interval among the configured component carriers including the first component carrier and the second component carrier; or a 1ms subframe duration.

[0235] Example 52 includes the subject matter described in Example 47, and optionally, wherein the HARQ-ACK feedback includes an aggregation of HARQ-ACK feedbacks, each HARQ-ACK feedback on a corresponding PCell or PUCCH SCell having a corresponding parameter set, each corresponding parameter set also corresponding to a parameter set of the data signal associated with each HARQ-ACK feedback.

[0236] Example 53 includes the subject matter described in Example 47, and optionally, wherein the HARQ-ACK feedback is based on: the size and order of the bits in the HARQ-ACK feedback corresponding to a static HARQ-ACK codebook on which all slots of the PDSCH are based; or the size and order of the bits in the HARQ-ACK feedback corresponding only to a dynamic HARQ-ACK codebook on which the scheduled slots of the PDSCH are based.

[0237] Example 54 includes the subject matter described in Example 53, and optionally, when the HARQ-ACK feedback is based on a dynamic HARQ-ACK codebook, the downlink control information includes information about the counter downlink dispatch index (C-DAI) and the total downlink dispatch index (T-DAI) corresponding to the PDSCH.

[0238] Example 55 includes the subject matter described in Example 54, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the C-DAI is incremented in the following manner: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding subframe used for the PDSCH.

[0239] Example 56 includes a method executed at a processing circuit of a base station, the method comprising: determining a physical downlink control channel (PDCCH) on a first component carrier; encoding a first signal to be transmitted on the PDCCH, the first signal including downlink control information (DCI) on resources for a second signal to be transmitted on a second component carrier, wherein the DCI is based on a predetermined set of parameters, and wherein the parameter sets of the first component carrier and the second component carrier are different from each other; and causing transmission of the first signal on the PDCCH, wherein a receiver of the second signal processes the second signal based on the control information in the first signal.

[0240] Example 57 includes the subject matter described in Example 56, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the method further includes: determining a physical downlink shared channel (PDSCH) on the second component carrier; encoding the data signal for transmission on the PDSCH; and inducing transmission of the data signal to the receiver based on the downlink control information.

[0241] Example 58 includes the subject matter described in Example 56, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal being a data signal, and the base station being a receiver of the second signal, the method further includes: detecting a physical uplink shared channel (PUSCH) on the second component carrier; and decoding the data signal received on the PUSCH based on the downlink control information.

[0242] Example 59 includes the subject matter described in Example 57, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the base station is a receiver of the second signal, the method further comprising: determining a Physical Downlink Shared Channel (PDSCH); encoding a data signal for transmission on the PDSCH; inducing transmission of the data signal; detecting a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); and decoding the HARQ-ACK signal received on the PUCCH, the HARQ-ACK signal being associated with the data signal on the PDSCH, based on the downlink control information.

[0243] Example 60 includes the subject matter described in Example 56, and optionally, the downlink control information includes a time slot index of the transmission of the second signal to indicate the time slot of the resource.

[0244] Example 61 includes the subject matter described in Example 60, and optionally, wherein the DCI includes a joint resource allocation field for indicating the downlink control information, and the downlink control information includes information about the time slot and the symbols within the time slot.

[0245] Example 62 includes the subject matter described in Example 56, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the timing between the first signal on the PDCCH and the second signal on the scheduled PDSCH or Physical Uplink Shared Channel (PUSCH) is configured via higher-layer signaling, indicated by a combination of higher-layer signaling and dynamic indications in the DCI of the first signal, or only explicitly indicated in the DCI.

[0246] Example 63 includes the subject matter described in Example 56, and optionally, wherein the downlink control information provides a two-element timing indication regarding the resource, wherein a first timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a component carrier (CC) transmitted using the PDCCH, and a second timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a CC transmitted using one of the PDSCH, the Physical Uplink Shared Channel (PUSCH), or the Physical Uplink Control Channel (PUCCH) carrying a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal.

[0247] Example 64 includes the subject matter described in Example 56, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the downlink control information includes micro-timeslot information, the micro-timeslot information including a symbol index for indicating symbols of resources.

[0248] Example 65 includes the subject matter of any one of Examples 56-58, and optionally, wherein the resource includes at least one of a time slot index of the resource, a symbol index of the resource, or a timing indication, and the predetermined parameter set is defined according to: a subframe boundary; a time slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carrier in which the PDCCH or the data signal is transmitted; or a parameter set always 15 kHz.

[0249] Example 66 includes the subject matter of any one of Examples 56-58, and optionally, wherein: the downlink control information includes scheduling information regarding scheduling resources for the data signal, the scheduling information including a timing indication; and wherein the timing indication includes an indication of a timing delay between the end of the PDCCH and the data signal, a predetermined set of parameters for the indication of the timing delay being based on a set of parameters of the data signal.

[0250] Example 67 includes the subject matter described in Example 59, and optionally, the resource includes a timing indication, the predetermined parameter set being defined according to: a subframe boundary; a slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carriers in which the PDSCH or the PUCCH is transmitted; or a parameter set always 15 kHz.

[0251] Example 68 includes the subject matter described in Example 59, and optionally, wherein: the scheduling information includes a timing indication; the first signal includes a downlink control information (DCI) signal on the PDCCH; and wherein the timing indication includes an indication of a timing delay, the predetermined set of parameters for the indication of the timing delay being based on the parameter set of the PDCCH.

[0252] Example 69 includes the subject matter described in Example 56, and optionally, wherein: the downlink control information includes scheduling information regarding scheduling resources for a data signal; the second signal includes the data signal; and the resources include multiple time slots.

[0253] Example 70 includes the subject matter described in Example 69, and optionally, the downlink control information includes a slot group index for indicating each slot group among the plurality of slots.

[0254] Example 71 includes the subject matter described in Example 56, and optionally, wherein: the first signal includes a first-level downlink control information (DCI) signal on the PDCCH; the downlink control information is a first-level DCI; the method further includes: encoding a second-level DCI for transmission on the PDSCH, the second-level DCI including a second-level DCI on the resource; inducing the transmission of the first-level DCI and the second-level DCI to the receiver; and inducing the transmission of a data signal to the receiver based on the first-level DCI and the second-level DCI.

[0255] Example 72 includes the subject matter of any one of Examples 57-58, and optionally, wherein the PDCCH is used to schedule high-frequency data signals, and wherein the downlink control information includes at least one of beampup link index, configuration parameters of phase tracking reference signal (PT-RS), or indication of sounding reference signal (SRS) resource (SRI).

[0256] Example 73 includes the subject matter described in Example 56, and optionally, wherein the resource includes the size and order of bits in a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the base station being a receiver of the second signal, the method further comprising: determining a Physical Downlink Shared Channel (PDSCH); encoding a data signal for transmission on the PDSCH; inducing transmission of the data signal; detecting a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); and decoding the HARQ-ACK signal based on the control information, the HARQ-ACK signal being received on the PUCCH and associated with the data signal on the PDSCH.

[0257] Example 74 includes the subject matter described in Example 73, and optionally, the method further includes: encoding and causing transmission of a dedicated radio resource control (RRC) signal, the RRC signal indicating the number of configured component carriers, including the first component carrier and the second component carrier, and the size of a HARQ-ACK aggregation window for the HARQ-ACK signal.

[0258] Example 75 includes the subject matter described in Example 73, and optionally, wherein the first signal includes a downlink control information (DCI) signal, and the method further includes at least one of: configuring a HARQ-ACK aggregation window size for the HARQ-ACK signal via NR minimum system information (MSI), NR residual minimum system information (RMSI), NR other system information (OSI), or radio resource control (RRC) signaling; or indicating the HARQ-ACK aggregation window size in the DCI.

[0259] Example 76 includes the subject matter described in Example 73, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the order of bits in the HARQ-ACK signal corresponds to the incrementing order of resources in the PDSCH: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding time slot used for the PDSCH.

[0260] Example 77 includes the subject matter described in Example 76, and optionally, wherein the DCI is based on the HARQ-ACK aggregation window size for the HARQ-ACK signal, and wherein the HARQ-ACK aggregation window size is based on the predetermined parameter set, which is defined according to: the minimum subcarrier interval among the configured component carriers including the first component carrier and the second component carrier; or a 1ms subframe duration.

[0261] Example 78 includes the subject matter described in Example 73, and optionally, wherein the HARQ-ACK feedback includes an aggregation of HARQ-ACK feedbacks, each HARQ-ACK feedback on a corresponding PCell or PUCCH SCell having a corresponding parameter set, each corresponding parameter set also corresponding to a parameter set of the data signal associated with each HARQ-ACK feedback.

[0262] Example 79 includes the subject matter described in Example 73, and optionally, wherein the HARQ-ACK feedback is based on: the size and order of the bits in the HARQ-ACK feedback corresponding to the static HARQ-ACK codebook on which all slots of the PDSCH are based; or the size and order of the bits in the HARQ-ACK feedback corresponding only to the dynamic HARQ-ACK codebook on which the scheduled slots of the PDSCH are based.

[0263] Example 80 includes the subject matter described in Example 79, and optionally, when the HARQ-ACK feedback is based on a dynamic HARQ-ACK codebook, the downlink control information includes information about the counter downlink dispatch index (C-DAI) and the total downlink dispatch index (T-DAI) corresponding to the PDSCH.

[0264] Example 81 includes the subject matter described in Example 80, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the C-DAI is incremented in the following manner: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding subframe used for the PDSCH.

[0265] Example 82 includes an apparatus for a base station, comprising: a module for determining a physical downlink control channel (PDCCH) on a first component carrier; a module for encoding a first signal to be transmitted on the PDCCH, the first signal including downlink control information (DCI) on resources for a second signal to be transmitted on a second component carrier, wherein the DCI is based on a predetermined set of parameters, and wherein the parameter sets of the first component carrier and the second component carrier are different from each other; and a module for inducing transmission of the first signal on the PDCCH, wherein a receiver of the second signal processes the second signal based on the control information in the first signal.

[0266] Example 83 includes the apparatus of Example 82, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the apparatus includes: a module for determining a physical downlink shared channel (PDSCH) on the second component carrier; a module for encoding the data signal for transmission on the PDSCH; and a module for inducing transmission of the data signal to the receiver based on the downlink control information.

[0267] Example 84 includes the apparatus described in Example 82, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal being a data signal, and the base station being a receiver of the second signal, the apparatus comprising: a module for detecting a physical uplink shared channel (PUSCH) on the second component carrier; and a module for decoding the data signal received on the PUSCH based on the downlink control information.

[0268] Example 85 includes an apparatus for a user equipment, the apparatus comprising: a memory storing logic; and processing circuitry coupled to the memory for implementing the following logic: detecting a physical downlink control channel (PDCCH) on a first component carrier; and decoding a first signal from a base station on the PDCCH, the first signal including downlink control information (DCI) on resources for a second signal to be transmitted on a second component carrier, wherein the DCI is based on a predetermined set of parameters, and the parameter sets of the first component carrier and the second component carrier are different from each other, and further wherein a receiver of the second signal processes the second signal based on the control information in the first signal.

[0269] Example 86 includes the subject matter described in Example 85, and optionally, wherein the UE is a receiver of the second signal, the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal includes the data signal, and the processing circuitry is further configured to: detect the physical downlink shared channel (PDSCH) on the second component carrier; and decode the data signal based on the downlink control information.

[0270] Example 87 includes the subject matter described in Example 85, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal being a data signal, and the base station being a receiver of the second signal, and the processing circuitry is further configured to: determine a Physical Uplink Shared Channel (PUSCH) on the second component carrier; encode the data signal based on the control information; and cause the data signal to be transmitted to an NR Evolution NodeB (gNB) on the PUSCH.

[0271] Example 88 includes the subject matter described in Example 86, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the UE is a receiver of the second signal, and the processing circuitry is further configured to: detect a Physical Downlink Shared Channel (PDSCH); decode a data signal transmitted on the PDSCH; determine a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); encode the HARQ-ACK signal based on the control information, the HARQ-ACK signal being associated with the data signal on the PDSCH; and cause the HARQ-ACK signal to be transmitted on the PUCCH.

[0272] Example 89 includes the subject matter described in Example 85, and optionally, the downlink control information includes a time slot index of the transmission of the second signal to indicate the time slot of the resource.

[0273] Example 90 includes the subject matter described in Example 89, and optionally, wherein the DCI includes a joint resource allocation field for indicating the downlink control information, and the downlink control information includes information about the time slot and the symbols within the time slot.

[0274] Example 91 includes the subject matter described in Example 85, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the timing between the first signal on the PDCCH and the second signal on the scheduled PDSCH or Physical Uplink Shared Channel (PUSCH) is configured via higher-layer signaling, indicated by a combination of higher-layer signaling and dynamic indications in the DCI of the first signal, or only explicitly indicated in the DCI.

[0275] Example 92 includes the apparatus described in Example 85, and optionally, wherein the downlink control information provides a two-element timing indication regarding the resource, wherein a first timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a component carrier (CC) transmitted using the PDCCH, and a second timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a CC transmitted using one of the PDSCH, the Physical Uplink Shared Channel (PUSCH), or the Physical Uplink Control Channel (PUCCH) carrying a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal.

[0276] Example 93 includes the subject matter described in Example 85, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the downlink control information includes micro-timeslot information, the micro-timeslot information including a symbol index for indicating symbols of resources.

[0277] Example 94 includes the subject matter of any one of Examples 85-87, and optionally, wherein the resource includes at least one of a time slot index of the resource, a symbol index of the resource, or a timing indication, and the predetermined parameter set is defined according to: a subframe boundary; a time slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carrier in which the PDCCH or the data signal is transmitted; or a parameter set always 15 kHz.

[0278] Example 95 includes the subject matter of any one of Examples 85-87, and optionally, wherein: the downlink control information includes scheduling information regarding scheduling resources for the data signal, the scheduling information including a timing indication; and wherein the timing indication includes an indication of a timing delay between the end of the PDCCH and the data signal, a predetermined set of parameters for the indication of the timing delay being based on a set of parameters of the data signal.

[0279] Example 96 includes the subject matter described in Example 88, and optionally, the resource includes a timing indication, the predetermined parameter set being defined according to: a subframe boundary; a slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carriers in which the PDSCH or the PUCCH is transmitted; or a parameter set always 15 kHz.

[0280] Example 97 includes the subject matter described in Example 88, and optionally, wherein: the scheduling information includes a timing indication; the first signal includes a downlink control information (DCI) signal on the PDCCH; and wherein the timing indication includes an indication of a timing delay, the predetermined set of parameters for the indication of the timing delay being based on the parameter set of the PDCCH.

[0281] Example 98 includes the subject matter described in Example 85, and optionally, wherein: the downlink control information includes scheduling information regarding scheduling resources for a data signal; the second signal includes the data signal; and the resources include multiple time slots.

[0282] Example 99 includes the subject matter described in Example 98, and optionally, the downlink control information includes a slot group index for indicating each slot group among the plurality of slots.

[0283] Example 100 includes the subject matter described in Example 98, and optionally, wherein: the first signal includes a first-level downlink control information signal (DCI) on the PDCCH; the downlink control information is a first-level DCI; the processing circuitry is further configured to: decode a second-level DCI on the PDSCH, the second-level DCI including a second-level DCI on the resource; and decode the data signal based on the first-level DCI and the second-level DCI.

[0284] Example 101 includes the subject matter of any one of Examples 86-87, and optionally, wherein the PDCCH is used to schedule high-frequency data signals, and wherein the downlink control information includes at least one of beampup link index, configuration parameters of phase tracking reference signal (PT-RS), or indication of probe reference signal (SRS) resource (SRI).

[0285] Example 102 includes the subject matter described in Example 85, and optionally, wherein the resource includes the size and order of bits in a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the base station being a receiver of the second signal, and the processing circuitry is further configured to: detect a Physical Downlink Shared Channel (PDSCH); decode data signals on the PDSCH; determine a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); encode the HARQ-ACK signal based on the control information; and cause the HARQ-ACK signal to be transmitted to the base station on the PUCCH, the HARQ-ACK signal being associated with the data signals on the PDSCH.

[0286] Example 103 includes the subject matter described in Example 102, and optionally, the operation further includes: processing a dedicated radio resource control signal (RRC signal) indicating the number of configured component carriers, including the first component carrier and the second component carrier, and the size of the HARQ-ACK aggregation window for the HARQ-ACK signal.

[0287] Example 104 includes the subject matter described in Example 102, and optionally, wherein the first signal includes a downlink control information (DCI) signal, and the processing circuitry is further configured to: determine the HARQ-ACK aggregation window size for the HARQ-ACK signal via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling; or determine the HARQ-ACK aggregation window size from the DCI on the PDCCH.

[0288] Example 105 includes the subject matter described in Example 102, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the order of bits in the HARQ-ACK signal corresponds to the incrementing order of resources in the PDSCH: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding time slot used for the PDSCH.

[0289] Example 106 includes the subject matter described in Example 105, and optionally, wherein the DCI is based on the HARQ-ACK aggregation window size for the HARQ-ACK signal, and wherein the HARQ-ACK aggregation window size is based on the predetermined parameter set, which is defined according to: the minimum subcarrier interval among the configured component carriers including the first component carrier and the second component carrier; or a 1ms subframe duration.

[0290] Example 107 includes the subject matter described in Example 102, and optionally, wherein the HARQ-ACK feedback includes an aggregation of HARQ-ACK feedbacks, each HARQ-ACK feedback on a corresponding Physical Uplink Control Channel (PUCCH) SCell having a corresponding set of parameters, each corresponding set of parameters also corresponding to a set of parameters of the data signal associated with each HARQ-ACK feedback.

[0291] Example 108 includes the subject matter described in Example 102, and optionally, wherein the HARQ-ACK feedback is based on: the size and order of the bits in the HARQ-ACK feedback corresponding to the static HARQ-ACK codebook on which all slots of the PDSCH are based; or the size and order of the bits in the HARQ-ACK feedback corresponding only to the dynamic HARQ-ACK codebook on which the scheduled slots of the PDSCH are based.

[0292] Example 109 includes the topic described in Example 108, and optionally, when the HARQ-ACK feedback is based on a dynamic HARQ-ACK codebook, the downlink control information includes information about the counter downlink dispatch index (C-DAI) and the total downlink dispatch index (T-DAI) corresponding to the PDSCH.

[0293] Example 110 includes the subject matter described in Example 109, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the C-DAI is incremented in the following manner: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding subframe used for the PDSCH.

[0294] Example 111 includes the subject matter described in Example 85, and optionally includes a front-end module coupled to the processing circuitry.

[0295] Example 112 includes the subject matter described in Example 111, and optionally includes at least one antenna coupled to the front-end module.

[0296] Example 113 includes the subject matter described in Example 112, and optionally, also includes the UE.

[0297] Example 114 includes a product comprising one or more tangible computer-readable non-transitory storage media, including computer-executable instructions operable when executed by at least one computer processor of a user equipment (UE), causing the at least one computer processor to perform operations at the UE, the operations including: detecting a physical downlink control channel (PDCCH) on a first component carrier; and decoding a first signal from a base station on the PDCCH, the first signal including downlink control information (DCI) on resources for a second signal to be transmitted on a second component carrier, wherein the DCI is based on a predetermined set of parameters, and the parameter sets of the first component carrier and the second component carrier are different from each other, and further wherein a receiver of the second signal processes the second signal based on the control information in the first signal.

[0298] Example 115 includes the subject matter described in Example 114, and optionally, wherein the UE is a receiver of the second signal, the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal includes the data signal, and the operation further includes: detecting the physical downlink shared channel (PDSCH) on the second component carrier; and decoding the data signal based on the downlink control information.

[0299] Example 116 includes the subject matter described in Example 114, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal being a data signal, and the base station being a receiver of the second signal, and the operation further includes: determining a Physical Uplink Shared Channel (PUSCH) on the second component carrier; encoding the data signal based on the control information; and causing the data signal to be transmitted to an NR Evolution NodeB (gNB) on the PUSCH.

[0300] Example 117 includes the subject matter described in Example 115, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the UE is a receiver of the second signal, the operation further includes: detecting a Physical Downlink Shared Channel (PDSCH); decoding a data signal transmitted on the PDSCH; determining a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); encoding the HARQ-ACK signal based on the control information, the HARQ-ACK signal being associated with the data signal on the PDSCH; and causing the HARQ-ACK signal to be transmitted on the PUCCH.

[0301] Example 118 includes the subject matter described in Example 114, and optionally, the downlink control information includes a time slot index of the transmission of the second signal for indicating the time slot of the resource.

[0302] Example 119 includes the subject matter described in Example 118, and optionally, wherein the DCI includes a joint resource allocation field for indicating the downlink control information, and the downlink control information includes information about the time slot and the symbols within the time slot.

[0303] Example 120 includes the subject matter described in Example 114, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the timing between the first signal on the PDCCH and the second signal on the scheduled PDSCH or Physical Uplink Shared Channel (PUSCH) is configured via higher-layer signaling, indicated by a combination of higher-layer signaling and dynamic indications in the DCI of the first signal, or only explicitly indicated in the DCI.

[0304] Example 121 includes the apparatus of Example 114, and optionally, wherein the downlink control information provides a two-element timing indication regarding the resource, wherein a first timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a component carrier (CC) transmitted using the PDCCH, and a second timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a CC transmitted using one of the PDSCH, the Physical Uplink Shared Channel (PUSCH), or the Physical Uplink Control Channel (PUCCH) carrying a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal.

[0305] Example 122 includes the subject matter described in Example 114, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the downlink control information includes micro-timeslot information, the micro-timeslot information including a symbol index for indicating symbols of resources.

[0306] Example 123 includes the subject matter of any one of Examples 114-116, wherein the resource includes at least one of a time slot index of the resource, a symbol index of the resource, or a timing indication, and the predetermined parameter set is defined according to: a subframe boundary; a time slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carrier in which the PDCCH or the data signal is transmitted; or a parameter set always 15 kHz.

[0307] Example 124 includes the subject matter of any one of Examples 114-116, wherein: the downlink control information includes scheduling information regarding scheduling resources for a data signal, the scheduling information including a timing indication; and wherein the timing indication includes an indication of a timing delay between the end of the PDCCH and the data signal, a predetermined set of parameters for the indication of the timing delay being based on a parameter set of the data signal.

[0308] Example 125 includes the subject matter described in Example 117, and optionally, the resource includes a timing indication, the predetermined parameter set being defined according to: a subframe boundary; a slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carriers in which the PDSCH or the PUCCH is transmitted; or a parameter set always 15 kHz.

[0309] Example 126 includes the subject matter described in Example 117, and optionally, wherein: the scheduling information includes a timing indication; the first signal includes a downlink control information (DCI) signal on the PDCCH; and wherein the timing indication includes an indication of a timing delay, the predetermined set of parameters for the indication of the timing delay being based on the parameter set of the PDCCH.

[0310] Example 127 includes the subject matter described in Example 114, and optionally, wherein: the downlink control information includes scheduling information regarding scheduling resources for a data signal; the second signal includes the data signal; and the resources include multiple time slots.

[0311] Example 128 includes the topic described in Example 127, and optionally, the downlink control information includes a slot group index for indicating each slot group among the plurality of slots.

[0312] Example 129 includes the subject matter described in Example 127, and optionally, wherein: the first signal includes a first-level downlink control information signal (DCI) on the PDCCH; the downlink control information is a first-level DCI; the method further includes: decoding a second-level DCI on the PDSCH, the second-level DCI including a second-level DCI on the resource; and decoding the data signal based on the first-level DCI and the second-level DCI.

[0313] Example 130 includes the subject matter of any one of Examples 115-116, and optionally, wherein the PDCCH is used to schedule high-frequency data signals, and wherein the downlink control information includes at least one of beampup link index, configuration parameters of phase tracking reference signal (PT-RS), or indication of probe reference signal (SRS) resource (SRI).

[0314] Example 131 includes the subject matter described in Example 114, and optionally, wherein the resource includes the size and order of bits in a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the base station being a receiver of the second signal, the operation further including: detecting a Physical Downlink Shared Channel (PDSCH); decoding data signals on the PDSCH; determining a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); encoding the HARQ-ACK signal based on the control information; and causing the HARQ-ACK signal to be transmitted to the base station on the PUCCH, the HARQ-ACK signal being associated with the data signals on the PDSCH.

[0315] Example 132 includes the subject matter described in Example 131, and optionally, the operation further includes: processing a dedicated radio resource control signal (RRC signal) indicating the number of configured component carriers, including the first component carrier and the second component carrier, and the size of the HARQ-ACK aggregation window for the HARQ-ACK signal.

[0316] Example 133 includes the subject matter described in Example 131, and optionally, wherein the first signal includes a downlink control information (DCI) signal, and the operation further includes at least one of the following: determining a HARQ-ACK aggregation window size for the HARQ-ACK signal via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling; or determining the HARQ-ACK aggregation window size from the DCI on the PDCCH.

[0317] Example 134 includes the subject matter described in Example 131, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the order of bits in the HARQ-ACK signal corresponds to the incrementing order of resources in the PDSCH: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding time slot used for the PDSCH.

[0318] Example 135 includes the subject matter described in Example 134, and optionally, wherein the DCI is based on the HARQ-ACK aggregation window size for the HARQ-ACK signal, and wherein the HARQ-ACK aggregation window size is based on the predetermined parameter set, which is defined according to: the minimum subcarrier interval among the configured component carriers including the first component carrier and the second component carrier; or a 1ms subframe duration.

[0319] Example 136 includes the subject matter described in Example 131, and optionally, wherein the HARQ-ACK feedback includes an aggregation of HARQ-ACK feedbacks, each HARQ-ACK feedback on a corresponding Physical Uplink Control Channel (PUCCH) SCell having a corresponding set of parameters, each corresponding set of parameters also corresponding to a set of parameters of the data signal associated with each HARQ-ACK feedback.

[0320] Example 137 includes the subject matter described in Example 131, and optionally, wherein the HARQ-ACK feedback is based on: the size and order of the bits in the HARQ-ACK feedback corresponding to a static HARQ-ACK codebook on which all slots of the PDSCH are based; or the size and order of the bits in the HARQ-ACK feedback corresponding only to a dynamic HARQ-ACK codebook on which the scheduled slots of the PDSCH are based.

[0321] Example 138 includes the subject matter described in Example 137, and optionally, when the HARQ-ACK feedback is based on a dynamic HARQ-ACK codebook, the downlink control information includes information about the counter downlink dispatch index (C-DAI) and the total downlink dispatch index (T-DAI) corresponding to the PDSCH.

[0322] Example 139 includes the subject matter described in Example 138, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the C-DAI is incremented in the following manner: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding subframe used for the PDSCH.

[0323] Example 140 includes a method executed at at least one computer processor of a user equipment (UE), the method comprising: detecting a physical downlink control channel (PDCCH) on a first component carrier; and decoding a first signal from a base station on the PDCCH, the first signal including downlink control information on resources for a second signal to be transmitted on a second component carrier, wherein the DCI is based on a predetermined parameter set, and the parameter sets of the first component carrier and the second component carrier are different from each other, and further wherein a receiver of the second signal processes the second signal based on the control information in the first signal.

[0324] Example 141 includes the subject matter described in Example 111, and optionally, wherein the UE is a receiver of the second signal, the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal includes the data signal, and the method further includes: detecting a physical downlink shared channel (PDSCH) on the second component carrier; and decoding the data signal based on the downlink control information.

[0325] Example 142 includes the subject matter described in Example 111, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal being a data signal, and the base station being a receiver of the second signal, the method further includes: determining a Physical Uplink Shared Channel (PUSCH) on the second component carrier; encoding the data signal based on the control information; and causing the data signal to be transmitted to an NR Evolution NodeB (gNB) on the PUSCH.

[0326] Example 143 includes the subject matter described in Example 112, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the UE is a receiver of the second signal, the method further includes: detecting a Physical Downlink Shared Channel (PDSCH); decoding a data signal transmitted on the PDSCH; determining a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); encoding the HARQ-ACK signal based on the control information, the HARQ-ACK signal being associated with the data signal on the PDSCH; and causing the HARQ-ACK signal to be transmitted on the PUCCH.

[0327] Example 144 includes the subject matter described in Example 111, and optionally, the downlink control information includes a time slot index of the transmission of the second signal to indicate the time slot of the resource.

[0328] Example 145 includes the subject matter described in Example 115, and optionally, wherein the DCI includes a joint resource allocation field for indicating the downlink control information, and the downlink control information includes information about the time slot and the symbols within the time slot.

[0329] Example 146 includes the subject matter described in Example 111, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the timing between the first signal on the PDCCH and the second signal on the scheduled PDSCH or Physical Uplink Shared Channel (PUSCH) is configured via higher-layer signaling, indicated by a combination of higher-layer signaling and dynamic indications in the DCI of the first signal, or only explicitly indicated in the DCI.

[0330] Example 147 includes the apparatus of Example 111, and optionally, wherein the downlink control information provides a two-element timing indication regarding the resource, wherein a first timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a component carrier (CC) transmitted using the PDCCH, and a second timing indication of the two-element timing indication is defined based on the time slot of a parameter set in a CC transmitted using one of the PDSCH, the Physical Uplink Shared Channel (PUSCH), or the Physical Uplink Control Channel (PUCCH) carrying a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal.

[0331] Example 148 includes the subject matter described in Example 111, and optionally, wherein the downlink control information includes scheduling information regarding scheduling resources for a data signal, the second signal including the data signal, and the downlink control information includes micro-timeslot information, the micro-timeslot information including a symbol index for indicating symbols of resources.

[0332] Example 149 includes the subject matter of any one of Examples 111-113, wherein the resource includes at least one of a time slot index, a symbol index, or a timing indication of the resource, and the predetermined parameter set is defined according to: a subframe boundary; a time slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carrier in which the PDCCH or the data signal is transmitted; or a parameter set always 15 kHz.

[0333] Example 150 includes the subject matter of any one of Examples 111-113, wherein: the downlink control information includes scheduling information regarding scheduling resources for a data signal, the scheduling information including a timing indication; and wherein the timing indication includes an indication of a timing delay between the end of the PDCCH and the data signal, a predetermined set of parameters for the indication of the timing delay being based on a parameter set of the data signal.

[0334] Example 151 includes the subject matter described in Example 114, and optionally, the resource includes a timing indication, the predetermined parameter set being defined according to: a subframe boundary; a slot boundary using the minimum parameter set of the first component carrier and the second component carrier; a parameter set in the component carriers in which the PDSCH or the PUCCH is transmitted; or a parameter set always 15 kHz.

[0335] Example 152 includes the subject matter described in Example 114, and optionally, wherein: the scheduling information includes a timing indication; the first signal includes a downlink control information (DCI) signal on the PDCCH; and wherein the timing indication includes an indication of a timing delay, the predetermined set of parameters for the indication of the timing delay being based on the parameter set of the PDCCH.

[0336] Example 153 includes the subject matter described in Example 111, and optionally, wherein: the downlink control information includes scheduling information regarding scheduling resources for a data signal; the second signal includes the data signal; and the resources include multiple time slots.

[0337] Example 154 includes the subject matter described in Example 124, and optionally, the downlink control information includes a slot group index for indicating each slot group among the plurality of slots.

[0338] Example 155 includes the subject matter described in Example 124, and optionally, wherein: the first signal includes a first-level downlink control information signal (DCI) on the PDCCH; the downlink control information is a first-level DCI; the method further includes: decoding a second-level DCI on the PDSCH, the second-level DCI including a second-level DCI on the resource; and decoding the data signal based on the first-level DCI and the second-level DCI.

[0339] Example 156 includes the subject matter of any one of Examples 112-113, wherein the PDCCH is used to schedule high-frequency data signals, and wherein the downlink control information includes at least one of beampup link index, configuration parameters of phase tracking reference signal (PT-RS), or indication of probe reference signal (SRS) resource (SRI).

[0340] Example 157 includes the subject matter described in Example 111, and optionally, wherein the resource includes the size and order of bits in a Hybrid Automatic Repeat Request-Acknowledgement Feedback (HARQ-ACK) signal, the second signal including the HARQ-ACK signal, and the base station being a receiver of the second signal, the method further comprising: detecting a Physical Downlink Shared Channel (PDSCH); decoding data signals on the PDSCH; determining a Physical Uplink Control Channel (PUCCH) on a second component carrier, the PUCCH being on a primary cell (PCell) or a secondary cell (SCell); encoding the HARQ-ACK signal based on the control information; and inducing the transmission of the HARQ-ACK signal to the base station on the PUCCH, the HARQ-ACK signal being associated with the data signals on the PDSCH.

[0341] Example 158 includes the subject matter described in Example 128, and optionally, the method further includes: processing a dedicated radio resource control (RRC) signal, the RRC signal indicating the number of configured component carriers, including the first component carrier and the second component carrier, and the size of a HARQ-ACK aggregation window for the HARQ-ACK signal.

[0342] Example 159 includes the subject matter described in Example 128, and optionally, wherein the first signal includes a downlink control information (DCI) signal, and the method further includes at least one of the following: determining a HARQ-ACK aggregation window size for the HARQ-ACK signal via NR minimum system information (MSI), NR residual minimum system information (RMSI), NR other system information (OSI), or radio resource control (RRC) signaling; or determining the HARQ-ACK aggregation window size from the DCI on the PDCCH.

[0343] Example 160 includes the subject matter described in Example 128, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the order of bits in the HARQ-ACK signal corresponds to the incrementing order of resources in the PDSCH: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing again in a mixed manner until the end of the corresponding time slot used for the PDSCH.

[0344] Example 161 includes the subject matter described in Example 131, and optionally, wherein the DCI is based on the HARQ-ACK aggregation window size for the HARQ-ACK signal, and wherein the HARQ-ACK aggregation window size is based on the predetermined parameter set, which is defined according to: the minimum subcarrier interval among the configured component carriers including the first component carrier and the second component carrier; or a 1ms subframe duration.

[0345] Example 162 includes the subject matter described in Example 128, and optionally, wherein the HARQ-ACK feedback includes an aggregation of HARQ-ACK feedbacks, each HARQ-ACK feedback on a corresponding Physical Uplink Control Channel (PUCCH) SCell having a corresponding set of parameters, each corresponding set of parameters also corresponding to a set of parameters of the data signal associated with each HARQ-ACK feedback.

[0346] Example 163 includes the subject matter described in Example 128, and optionally, wherein the HARQ-ACK feedback is based on: the size and order of the bits in the HARQ-ACK feedback corresponding to a static HARQ-ACK codebook on which all slots of the PDSCH are based; or the size and order of the bits in the HARQ-ACK feedback corresponding only to a dynamic HARQ-ACK codebook on which the scheduled slots of the PDSCH are based.

[0347] Example 164 includes the subject matter described in Example 134, and optionally, when the HARQ-ACK feedback is based on a dynamic HARQ-ACK codebook, the downlink control information includes information about the counter downlink dispatch index (C-DAI) and the total downlink dispatch index (T-DAI) corresponding to the PDSCH.

[0348] Example 165 includes the subject matter described in Example 135, and optionally, for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), the C-DAI is incremented in the following manner: incrementing in a time-first, frequency-second manner; incrementing in a frequency-first, time-second manner; or incrementing in a mixed manner, including incrementing in a time-first manner, then in a frequency-second manner after reaching the time slot boundary, through all configured CCs, and then incrementing in a mixed manner again until the end of the corresponding subframe used for the PDSCH.

[0349] The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in accordance with the foregoing teachings, or may be obtained from practice with various embodiments.

Claims

1. An apparatus for a user equipment (UE), the apparatus comprising a radio frequency (RF) circuit interface and processing circuitry, the processing circuitry being coupled to the RF circuit interface and configured to: Decode downlink control information (DCI) from the base station, the DCI including HARQ-ACK codebook information for the hybrid automatic repeat request acknowledgment (HARQ-ACK) signal in the physical uplink control channel (PUCCH) from the UE to the base station, and the DCI including information about the counter downlink allocation index (C-DAI), wherein the HARQ-ACK codebook information is based on a dynamic HARQ-ACK codebook, and the HARQ-ACK codebook information includes information about the size of the HARQ-ACK aggregation window for the HARQ-ACK signal; Decode the Physical Downlink Shared Channel (PDSCH) transmission from the base station, wherein the C-DAI has a value that increases first in frequency and then in time corresponding to the PDSCH transmission; and The HARQ-ACK signal is encoded based on the C-DAI, the HARQ-ACK aggregation window, and the PDSCH transmission for transmission to the base station.

2. The apparatus according to claim 1, wherein the processing circuit is further configured as follows: The physical downlink control channel (PDCCH) including the DCI is decoded. The DCI includes information about the timing delay between the PDCCH and the PDSCH or between the PDCCH and the PUSCH, wherein the PUSCH is to be sent by the UE to the base station and corresponds to the DCI.

3. The apparatus according to claim 1, wherein, The HARQ-ACK aggregation window is based on the subcarrier spacing of the component carrier CC used to transmit the PUCCH.

4. The apparatus of claim 1 further includes a front-end module coupled to the processing circuit.

5. An apparatus for a user equipment (UE), the apparatus comprising a radio frequency (RF) circuit interface and processing circuitry, the processing circuitry being coupled to the RF circuit interface and configured to: Decode control information from the base station, the control information including HARQ-ACK codebook information for a hybrid automatic repeat request acknowledgment (HARQ-ACK) signal in the physical uplink control channel (PUCCH) from the UE to the base station, wherein the HARQ-ACK codebook information includes information about the size of the HARQ-ACK aggregation window of the HARQ-ACK signal, and wherein the control information is at least one of downlink control information (DCI) or radio resource control (RRC) signaling; The size of the HARQ-ACK aggregation window is configured based on the information about the size of the HARQ-ACK aggregation window included in the control information and further based on the subcarrier spacing of the component carrier CC used to transmit the PUCCH; Decode the Physical Downlink Shared Channel (PDSCH) transmission from the base station; as well as The HARQ-ACK signal is encoded based on the configured HARQ-ACK aggregation window and the PDSCH transmission for transmission to the base station in the PUCCH.

6. The apparatus according to claim 5, wherein, The HARQ-ACK codebook information is based on either a dynamic HARQ-ACK codebook or a semi-static HARQ-ACK codebook.

7. The apparatus according to claim 6, wherein: The HARQ-ACK codebook information is based on the dynamic HARQ-ACK codebook; The control information is in the DCI and includes information about the counter downlink allocation index C-DAI; and The C-DAI has a value that increases in a frequency-first, time-later manner corresponding to the PDSCH transmission.

8. The apparatus of claim 5, wherein the processing circuit decodes a physical downlink control channel (PDCCH) including the control information, the control information including information about a timing delay between the PDCCH and the PDSCH or a timing delay between the PDCCH and the physical uplink shared channel (PUSCH), the PUSCH being sent by the UE to the base station and corresponding to the control information.

9. The apparatus of claim 5 further includes a front-end module coupled to the processing circuit.

10. An apparatus for a base station, the apparatus comprising a radio frequency (RF) circuit interface and processing circuitry, the processing circuitry being coupled to the RF circuit interface and configured to: Encoded control information for transmission to a user equipment (UE), the control information including HARQ-ACK codebook information for a hybrid automatic repeat request acknowledgment (HARQ-ACK) signal in the physical uplink control channel (PUCCH) from the UE to the base station, wherein the HARQ-ACK codebook information includes information about the size of the HARQ-ACK aggregation window of the HARQ-ACK signal; The Physical Downlink Shared Channel (PDSCH) transmission to the UE is encoded based on the control information; and Decode the HARQ-ACK signal in the PUCCH from the UE; in, The control information is at least one of downlink control information (DCI) or radio resource control (RRC) signaling, and the control information can be decoded by the UE so that the UE can determine the size of the HARQ-ACK aggregation window based on at least one of the decoding of the DCI or the RRC signaling and further based on the subcarrier spacing of the component carrier CC used to transmit the PUCCH.

11. The apparatus according to claim 10, wherein, The HARQ-ACK codebook information is based on either a dynamic HARQ-ACK codebook or a semi-static HARQ-ACK codebook.

12. The apparatus according to claim 11, wherein: The HARQ-ACK codebook information is based on the dynamic HARQ-ACK codebook; The control information is in the DCI and includes information about the counter downlink allocation index (C-DAI); and The C-DAI has a value that increases in a frequency-first, time-later manner corresponding to the PDSCH transmission.

13. The apparatus of claim 10, wherein the processing circuit encodes a physical downlink control channel (PDCCH) including the control information, the control information including information about a timing delay between the PDCCH and the PDSCH or between the PDCCH and the physical uplink shared channel (PUSCH), the PUSCH being transmitted by the UE to the base station and corresponding to the control information.

Images