Cross-Carrier Scheduling with Different Cell Numerologies

Abstract

A computer-readable storage medium stores instructions for configuring a UE for cross-carrier scheduling of data transmissions in 5G NR and beyond wireless networks and causing the UE to perform operations including decoding configuration signaling received from a base station. The configuration signaling indicates a first numerology parameter for a scheduling cell of the base station and a second numerology parameter for a scheduled cell of the base station. The DCI is received via a PDCCH of the scheduling cell. The DCI schedules DL data transmissions in the scheduled cell of the base station. If a difference between the first numerology parameter and the second numerology parameter is less than or equal to a preconfigured numerology threshold, the DL data transmission is received via a PDSCH of the scheduled cell. If the difference is greater than the threshold, the UE refrains from decoding the DL data transmission.

Description

[Technical field]

[0001] [Priority claim] This application claims the benefit of priority to the following patent applications:

[0002] International Application No. PCT / CN2021 / 104966, filed on July 7, 2021, and entitled “TIME BUNDLING FOR SEMI-STATIC HARQ-ACK CODEBOOK FOR MULTI-PDSCH SCHEDULING.”

[0003] U.S. Provisional Patent Application No. 63 / 246,264, filed on September 20, 2021, and entitled “TIME BUNDLING FOR SEMI-STATIC HARQ-ACK CODEBOOK FOR MULTI-PDSCH SCHEDULING.”

[0004] U.S. Provisional Patent Application No. 63 / 296,131, filed on January 3, 2022, and entitled “CROSS-CARRIER SCHEDULING WITH DIFFERENT NUMEROLOGIES OF THE SCHEDULING CELL AND THE SCHEDULED CELL.”

[0005] The entire contents of each of the above patent applications are incorporated by reference.

[0006] [Technical field] Aspects relate to wireless communications. Some aspects relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3GPP (Long Term Evolution) networks, 3GPP (LTE) LTE Advanced (LTE-A) networks, (MultiFire, LTE-U), and 5G (fifth-generation) networks and beyond, including 5G-LTE networks such as 5G new radio (NR) (or 5G-NR) networks, 5G NR unlicensed spectrum (NR-U) networks, and other unlicensed networks including Wi-Fi, CBRS (OnGo), etc. Other aspects are directed to a mechanism for time bundling for semi-static hybrid automatic repeat request acknowledgment (HARQ ACK) for multi-physical downlink shared channel (multi-PDSCH) scheduling in 5G-NR and beyond network communications. Further aspects relate to mechanisms for cross-carrier scheduling with different numerologies of scheduling and scheduled cells in 5G-NR and beyond networks. [Background technology]

[0007] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated and integrated communications platforms. The use of 3GPP® LTE systems is increasing with an increase in different types of devices communicating with various network devices. The penetration of mobile devices (user equipment or UE) in modern society continues to drive the demand for a wide variety of networked devices in many different environments. Fifth-generation (5G) wireless systems are emerging and are expected to enable even greater speed, connectivity and availability. Next-generation 5G networks (or NR networks) are expected to increase throughput, coverage and robustness, and reduce latency and operational and capital expenditures. 5G-NR networks will continue to evolve based on 3GPP® LTE-Advanced with additional potential new radio access technologies (RATs) to enrich people's lives with seamless wireless connectivity solutions that deliver high-speed, rich content and services. As current cellular network frequencies are saturated, higher frequencies such as millimeter wave (mmWave) frequencies may be beneficial due to their higher bandwidth.

[0008] Potential LTE operation in unlicensed spectrum includes, but is not limited to, LTE operation in unlicensed spectrum via dual connectivity (DC) or DC-based LAA, and standalone LTE systems in unlicensed spectrum, where LTE-based technologies operate alone in unlicensed spectrum without the need for an "anchor" in licensed spectrum, called MulteFire. Further enhanced operation of LTE and NR systems in licensed and unlicensed spectrum is envisioned in future releases and 5G-NR (and beyond) systems. Such enhanced operation may include mechanisms for handling overlap between DL reception and UL transmission for HD-FDD multiplexing operation in 5G-NR and beyond network communications. [Brief description of the drawings]

[0009] In the drawings, which are not necessarily to scale, like numbers may describe like components in different views. Like numbers with different subscripts may represent different instances of the like component. The drawings illustrate generally, by way of example, but not by way of limitation, various aspects discussed in the present document. [Figure 1A] 1 illustrates a network architecture in accordance with some aspects. [Figure 1B] 1 illustrates a non-roaming 5G system architecture according to some aspects. [Figure 1C] 1 illustrates a non-roaming 5G system architecture according to some aspects. [Diagram 2] 1 illustrates various systems, devices and components in which aspects of the disclosed embodiments may be implemented. [Diagram 3] 1 illustrates various systems, devices and components in which aspects of the disclosed embodiments may be implemented. [Figure 4]1 illustrates various systems, devices and components in which aspects of the disclosed embodiments may be implemented. [Diagram 5] 1 illustrates an illustration of short slot duration with larger subcarrier spacing in accordance with some aspects. [Figure 6] 1 illustrates an illustration of cross-carrier scheduling when a scheduled cell becomes inapplicable, according to some aspects. [Figure 7] 1 illustrates an illustration of automatic bandwidth part (BWP) switching on a scheduled cell, according to some aspects. [Figure 8] 1 illustrates a diagram of multiple transmission time interval (TTI) scheduling for a PDSCH, in accordance with some aspects. [Figure 9] 1 illustrates a diagram of occasion bundles in consecutive slots, according to some embodiments. [Figure 10] 1 illustrates a diagram of occasion bundling in a determined downlink (DL) slot, in accordance with some aspects. [Figure 11] 1 illustrates a diagram of an occasion bundle in a determined DL slot with assigned occasions, according to some aspects. [Figure 12] 1 illustrates a diagram of a determined DL slot bundle flexible size, according to some aspects. [Figure 13] 1 illustrates a diagram of flexible sizes of determined DL slot bundles with assigned occasions, according to some aspects. [Figure 14] 1 illustrates a diagram of a HARQ-ACK codebook based on a reference start and length indicator value (SLIV), in accordance with some aspects. [Figure 15] 1 illustrates a diagram of a HARQ-ACK codebook based on the criteria SLIV, in accordance with some aspects. [Figure 16]1 illustrates a diagram of a HARQ-ACK codebook based on sequentially assigned reference SLIVs, in accordance with some aspects. [Figure 17] FIG. 1 illustrates a block diagram of a communications device, such as an evolved Node-B (eNB), new generation Node-B (gNB) (or another RAN node or base station), transmission / reception point (TRP), access point (AP), wireless station (STA), mobile station (MS), or user equipment (UE), in accordance with some aspects. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The following description and drawings sufficiently illustrate the embodiments to enable those skilled in the art to practice the embodiments. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in or substituted for those of other embodiments. The embodiments outlined in the claims encompass all available equivalents of those claims.

[0011] 1A illustrates a network architecture according to some aspects. Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, a drone, or any other computing device that includes a wired and / or wireless communication interface. UE 101 and 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

[0012] Any of the wireless links described herein (eg, as used in network 140A or any other illustrated network) may operate according to any example wireless communication technology and / or standard.

[0013] LTE and LTE-Advanced are standards for high-speed data wireless communications for UEs such as mobile phones. In LTE-Advanced and various wireless systems, carrier aggregation is a technique in which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some aspects, carrier aggregation may be used when one or more component carriers operate on unlicensed frequencies.

[0014] The aspects described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in the 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and beyond frequencies, and Spectrum Access System (SAS) in the 3.55-3.7 GHz and beyond frequencies).

[0015] The aspects described herein may also be applied to different single carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.), and in particular to 3GPP NR by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0016] In some aspects, any of the UEs 101 and 102 may include an Internet-of-Things (IoT) UE or a Cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. In some aspects, any of the UEs 101 and 102 may include a narrowband (NB) IoT UE (e.g., enhanced NB-IoT (eNB-IoT) UE and Further Enhanced IoT (FeNB-IoT) UE, etc.). The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with an MTC server or device over a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communications, sensor network, or IoT network. M2M or MTC exchanges of data may be machine-initiated exchanges of data. An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-term connections. IoT UEs may run background applications (e.g., key alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0017] In some aspects, either of the UEs 101 and 102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0018] UEs 101 and 102 may be configured to connect, for example, be communicatively coupled, to a radio access network (RAN) 110. RAN 110 may be, for example, a Universal Mobile Telecommunications System (UMTS), an Evolved 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 of which includes a physical communication interface or layer (discussed in further detail below), which in this example are shown as air interfaces for enabling communication coupling and may be consistent with cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP (registered trademark) Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.

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

[0020] The UE 102 is shown configured to access an access point (AP) 106 via a connection 107. The connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 may include a wireless fidelity (WiFi) router. In this example, the AP 106 is shown connected to the Internet without connecting to a core network of a wireless system (discussed in more detail below).

[0021] The RAN 110 may include one or more access nodes that enable the connections 103 and 104. These access nodes (AN) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN network nodes, etc., and may include terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 may be transmission / reception points (TRPs). If the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may function within the communication cell of the NodeB. The RAN 110 may include one or more RAN nodes for providing a macro cell, such as a macro RAN node 111, and one or more RAN nodes for providing a femto cell or a pico cell (e.g., a cell having a smaller coverage area, smaller user capacity or higher bandwidth compared to a macro cell), such as a low power (LP) RAN node 112 or an unlicensed spectrum based secondary RAN node 112.

[0022] Either of the RAN nodes 111 and 112 may terminate air interface protocols and may be the initial point of contact for the UEs 101 and 102. In some aspects, either of the RAN nodes 111 and 112 may implement various logical functions for the 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. In one example, either of the nodes 111 and / or 112 may be a new generation Node-B (gNB), an evolved Node-B (eNB), or another type of RAN node.

[0023] The RAN 110 is shown communicatively coupled to a core network (CN) 120 via an S1 interface 113. In an aspect, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as described with reference to FIGS. 1B-1C). In this aspect, the S1 interface 113 is split into two parts: an S1-U interface 114 that carries user traffic data between the RAN nodes 111 and 112 and a serving gateway (S-GW) 122, and an S1-MME interface 115 that is a signaling interface between the RAN nodes 111 and 112 and a mobility management entity (MME) 121.

[0024] In this aspect, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MME 121 may be functionally similar to the control plane of a legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may include a database for network users, including subscription related information to support network entity handling of communication sessions. The CN 120 may include one or several HSSs 124, depending on the number of mobile subscribers, equipment capabilities, network organization, etc. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc.

[0025] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. Additionally, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and may provide an anchor for inter-3GPP mobility. Other functions of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0026] The P-GW 123 may terminate the SGi interface towards the PDN. The P-GW 123 may route data packets between the EPC network 120 and external networks, such as a network including an application server 184 (alternatively referred to as an application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data to other external networks 131A, which may include the Internet, an IP multimedia subsystem (IPS) network, and other networks. In general, the application server 184 may be an element that provides applications that use IP bearer resources in conjunction with a core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may 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 the UEs 101 and 102 via the CN 120.

[0027] Additionally, the P-GW 123 may be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in a Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session, namely, a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0028] In some aspects, the communication network 140A may be an IoT network or a 5G network, including a 5G New Radio Network that uses communication in licensed (5G NR) and unlicensed (5G NR-U) spectrums. One of the current enablers of IoT is narrowband-IoT (NB-IoT).

[0029] The NG system architecture may include a RAN 110 and a 5G core (5GC, 5G core) network 120. The NG-RAN 110 may include multiple nodes such as gNBs and NG-eNBs. The core network 120 (e.g., 5G core network or 5GC) may include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and UPF may be communicatively coupled to the gNBs and NG-eNBs via an NG interface. More specifically, in some aspects, the gNBs and NG-eNBs may be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNBs and NG-eNBs may be coupled to each other via an Xn interface.

[0030] In some aspects, the NG system architecture can use reference points between various nodes such as those provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some aspects, each of the gNB and NG-eNB can be implemented as a base station, a mobile edge server, a small cell, a home eNB, a RAN network node, etc. In some aspects, in a 5G architecture, the gNB can be a master node (MN) and the NG-eNB can be a secondary node (SN). In some aspects, the master / primary node can operate in a licensed band and the secondary node can operate in an unlicensed band.

[0031] 1B illustrates a non-roaming 5G system architecture in accordance with some aspects. With reference to FIG. 1B, a 5G system architecture 140B is illustrated in a reference point representation. More specifically, a UE 102 can communicate with a RAN 110 and one or more other 5G core (5GC, 5G core) network entities. The 5G system architecture 140B includes a number of network functions (NFs), such as an access and mobility management function (AMF) 132, a location management function (LMF) 133, a session management function (SMF) 136, a policy control function (PCF) 148, an application function (AF) 150, a user plane function (UPF) 134, a network slice selection function (NSSF) 142, an authentication server function (AUSF) 144, and a unified data management (UDM) / home subscriber server (HSS) 146. The UPF 134 can provide connectivity to a data network (DN) 152, which can include, for example, operator services, internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and can also include a network slice selection function. The SMF 136 can be configured to set up and manage various sessions according to network policies. The UPF 134 can be deployed in one or more configurations according to the type of service desired.The PCF 148 can be configured to provide a policy framework using network slicing, mobility management and roaming (similar to a PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0032] The LMF 133 may be used in conjunction with 5G positioning functions. In some aspects, the LMF 133 receives measurements and assistance information from the next generation radio access network (NG-RAN) 110 and the mobile device (e.g., UE 101) via the AMF 132 over the NL interface to calculate the position of the UE 101. In some aspects, the NR positioning protocol A (NRPPa) may be used to carry positioning information between the NG-RAN and the LMF 133 over the next generation control plane interface (NG-C). In some aspects, the LMF 133 configures the UE using the LTE positioning protocol (LPP) via the AMF 132. The NG RAN 110 configures the UE 101 using radio resource control (RRC) protocol over the LTE-Uu and NR-Uu interfaces.

[0033] In some aspects, the 5G system architecture 140B configures different reference signals to enable positioning measurements. Exemplary reference signals that may be used for positioning measurements include a positioning reference signal (NR PRS, positioning reference signal) in the downlink and a sounding reference signal (SRS, sounding reference signal) for positioning in the uplink. The downlink positioning reference signal (PRS, positioning reference signal) is a reference signal configured to support a downlink-based positioning method.

[0034] In some aspects, the 5G system architecture 140B includes multiple IP multimedia core network subsystem entities, such as an IP multimedia subsystem (IMS) 168B and a call session control function (CSCF). More specifically, the IMS 168B includes a CSCF that can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first point of contact for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session state within the network, and the E-CSCF can be configured to handle certain aspects of the emergency session, such as routing the emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to act as a contact point within the network of the network operator for all IMS connections destined for its subscribers or roaming subscribers currently located within its service area. In some aspects, the I-CSCF 166B can connect to another IP multimedia network 170B, e.g., an IMS operated by a different network operator.

[0035] In some aspects, the UDM / HSS 146 can be coupled to an application server 160B, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to an IMS 168B via an S-CSCF 164B or an I-CSCF 166B.

[0036] The reference point representation indicates that there may be interactions between the corresponding NF services. For example, FIG. 1B shows the following reference points: N1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF 148 and AF 150, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148, not shown), N8 (between UDM 146 and AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between UDM 146 and SMF 136, not shown), N11 (between UE 102 and AMF 132, not shown), N12 (between UE 102 and AMF 132, not shown), N13 (between UE 102 and AMF 132, not shown), N14 (between UE 102 and AMF 132, not shown), N15 (between UE 102 and AMF 132, not shown), N16 (between UPF 134 and DN 152, not shown), N17 (between SMF 136 and PCF 148, not shown), N18 (between UDM 146 and AMF 132, not shown), N19 (between two UPFs 134, not shown), N20 (between UE 102 and AMF 132, not shown), N21 (between UE 102 and AMF 132, not shown), N22 (between UE 1B shows N11 (between AMF 132 and SMF 136, not shown), N12 (between AUSF 144 and AMF 132, not shown), N13 (between AUSF 144 and UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between PCF 148 and AMF 132 in case of a non-roaming scenario, or between PCF 148 and visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. 1B may also be used.

[0037] 1C illustrates a 5G system architecture 140C and a service-based representation. In addition to the network entities illustrated in FIG. 1B, the system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, the 5G system architecture can be service-based, and interactions between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0038] In some aspects, a service-based representation can be used to represent network functions in the control plane that allow other authorized network functions to access these services, as shown in Figure 1C. In this regard, the 5G system architecture 140C can include the following service-based interfaces: Namf 158H (service-based interface indicated by AMF 132), Nsmf 158I (service-based interface indicated by SMF 136), Nnef 158B (service-based interface indicated by NEF 154), Npcf 158D (service-based interface indicated by PCF 148), Nudm 158E (service-based interface indicated by UDM 146), Naf 158F (service-based interface indicated by AF 150), Nnrf 158C (service-based interface indicated by NRF 156), Nnssf 158A (service-based interface indicated by NSSF 142), Nausf 158G (service-based interface indicated by AUSF 144). Other service-based interfaces not shown in FIG. 1C (e.g., Nudr, N5g-eir, and Nudsf) can also be used.

[0039] 2, 3, and 4 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments in different communication systems, such as 5G-NR (and beyond) networks. The UEs, base stations (such as gNBs), and / or other nodes (e.g., satellites or other NTN nodes) discussed in connection with FIGS. 1A-4 may be configured to perform the disclosed techniques.

[0040] 2 illustrates a network 200 in accordance with various embodiments. Network 200 may operate in a manner consistent with 3GPP® technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this respect and the described embodiments may be applied to other networks that would benefit from the principles described herein, such as future 3GPP® systems, etc.

[0041] The network 200 may include a UE 202, which may include any mobile or non-mobile computing device designed to communicate over a wireless connection with a RAN 204. The UE 202 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, a heads-up display device, an in-vehicle diagnostic device, a dash-top mobile instrument, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a network appliance, a machine type communication device, an M2M or D2D device, an IoT device, etc.

[0042] In some embodiments, the network 200 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0043] In some embodiments, the UE 202 may further communicate with the AP 206 via a wireless connection. The AP 206 may manage a WLAN connection, which may function to offload some / all network traffic from the RAN 204. The connection between the UE 202 and the AP 206 may be consistent with any IEEE 802.11 protocol, and the AP 206 may be a wireless fidelity (Wi-Fi) router. In some embodiments, the UE 202, the RAN 204, and the AP 206 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular WLAN aggregation may involve the UE 202 being configured by the RAN 204 to utilize both cellular radio resources and WLAN resources.

[0044] The RAN 204 may include one or more access nodes, such as the access node (AN) 208. The AN 208 may terminate air interface protocols for the UE 202 by providing access stratum protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and L1 protocols. In this manner, the AN 208 may enable data / voice connectivity between the core network (CN) 220 and the UE 202. In some embodiments, the AN 208 may be implemented in a discrete device or as one or more software entities running on a server computer as part of a virtual network, which may be referred to as, for example, a CRAN or a virtual baseband unit pool. The AN 208 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 208 may be a macrocell base station or a low power base station for providing a femtocell, picocell or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0045] In embodiments in which the RAN 204 includes multiple ANs, the multiple ANs may be coupled to one another via an X2 interface (if the RAN 204 is an LTE RAN) or an Xn interface (if the RAN 204 is a 5G RAN). The X2 / Xn interface, which in some embodiments may be separated into a control / user plane interface, may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference control, and the like.

[0046] Each of the ANs of the RAN 204 may manage one or more cells, cell groups, component carriers, etc., to provide the UE 202 with an air interface for network access. The UE 202 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 204. For example, the UE 202 and the RAN 204 may use carrier aggregation to enable the UE 202 to connect to multiple component carriers, each corresponding to a Pcell or an Scell. In a dual connectivity scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0047] The RAN 204 may provide an air interface over a licensed or unlicensed spectrum. To operate in an unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA techniques with a PCell / Scell. Before accessing the unlicensed spectrum, the node may perform a medium / carrier sensing operation, for example, based on a listen-before-talk (LBT) protocol.

[0048] In a V2X scenario, the UE 202 or the AN 208 may be or function as a roadside unit (RSU), which may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable AN or a static (or relatively static) UE. An RSU implemented in or by a UE may be referred to as a "UE type RSU", an eNB may be referred to as an "eNB type RSU", a gNB may be referred to as a "gNB type RSU", and so forth. In one example, the RSU is a computing device coupled to radio frequency circuits located on the roadside that provide connectivity support to passing vehicular UEs. The RSU may also include internal data storage circuits that store intersection map geometry, traffic statistics, media, and applications / software to detect and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

[0049] In some embodiments, the RAN 204 may be an LTE RAN 210 including an eNB, e.g., eNB 212. The LTE RAN 210 may provide the LTE air interface with the following features: 15 kHz sub-carrier spacing (SCS), CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL, turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management, PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate in sub-6 GHz bands.

[0050] In some embodiments, the RAN 204 may be an NG-RAN 214 having a gNB, e.g., gNB 216, or an ng-eNB, e.g., ng-eNB 218. The gNB 216 may connect to a 5G-capable UE using a 5G NR interface. The gNB 216 may connect to a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 218 may also connect to a 5G core through an NG interface, but may connect to the UE through an LTE air interface. The gNB 216 and the ng-eNB 218 may connect to each other through an Xn interface.

[0051] In some embodiments, the NG interface may be split into two parts: an NG user plane (NG-U) interface (e.g., N3 interface), which carries traffic data between the nodes of the NG-RAN 214 and the UPF 248, and an NG control plane (NG-C) interface (e.g., N2 interface), which is the signaling interface between the nodes of the NG-RAN 214 and the AMF 244.

[0052] The NG-RAN 214 may provide the 5G NR air interface with the following features: variable SCS, CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL, polar, repetition, simplex and Reed-Muller codes for data control and LDPC. The 5G NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for PDSCH phase tracking, and tracking reference signals for time tracking. The 5G NR air interface may operate in the sub-6 GHz bands, including the 24.25 GHz to 52.6 GHz bands, or the FR1 bands, including the FR2 bands. The 5G NR air interface may include a synchronization signal and physical broadcast channel (SS / PBCH, synchronization signal and physical broadcast channel) block (SSB, SS / PBCH block), which is an area of ​​the downlink resource grid that includes the PSS / SSS / PBCH.

[0053] In some embodiments, the 5G NR air interface may utilize bandwidth parts (BWPs) for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For example, a UE 202 can be configured with multiple BWPs, each BWP configuration having a different SCS. When a change in BWP is indicated to the UE 202, the SCS of the transmission is changed as well. Another use case of BWPs relates to power saving. In particular, multiple BWPs with different amounts of frequency resources (e.g., PRBs) can be configured for a UE 202 to support data transmission under different traffic load scenarios. A BWP with a smaller number of PRBs can be used for data transmission with small traffic, enabling power saving at the UE 202 and, in some cases, at the gNB 216. A BWP with a larger number of PRBs can be used for scenarios with higher traffic load.

[0054] The RAN 204 is communicatively coupled to the CN 220, which includes network elements for providing various functions to support data and telecommunication services to customers / subscribers (e.g., users of UEs 202). The components of the CN 220 may be implemented on one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 220 onto physical computational / storage resources in servers, switches, etc. A logical instantiation of the CN 220 may be referred to as a network slice, and a logical instantiation of a portion of the CN 220 may be referred to as a network sub-slice.

[0055] In some embodiments, the CN 220 may be connected to an LTE wireless network as part of an Enhanced Packet System (EPS) 222, which may also be referred to as an EPC (or Evolved Packet Core). The EPC 222 may include an MME 224, an SGW 226, an SGSN 228, an HSS 230, a PGW 232, and a PCRF 234 coupled together over interfaces (or "reference points") as shown. The functionality of the elements of the EPC 222 may be briefly introduced as follows.

[0056] The MME 224 may implement mobility management functions to track the current location of the UE 202 and facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and the like.

[0057] The SGW 226 may terminate the S1 interface towards the RAN and route data packets between the RAN and the EPC 222. The SGW 226 may be the local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other roles may include lawful interception, charging and some policy enforcement.

[0058] The SGSN 228 may track the location of the UE 202 and perform security functions and access control. Additionally, the SGSN 228 may perform EPC inter-node signaling for mobility between different RAT networks, PDN and S-GW selection as specified by the MME 224, MME selection for handover, etc. The S3 reference point between the MME 224 and the SGSN 228 may enable exchange of user and bearer information for inter-3GPP access network mobility in idle / active state.

[0059] The HSS 230 may include a database for network users, including subscription-related information, to support handling of communication sessions by network entities. The HSS 230 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS 230 and the MME 224 may enable transfer of subscription and authentication data to authenticate / authorize user access to the LTE CN 220.

[0060] The PGW 232 may terminate an SGi interface towards a data network (DN) 236, which may include an application / content server 238. The PGW 232 may route data packets between the LTE CN 220 and the data network 236. The PGW 232 may be coupled to the SGW 226 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 232 may further include a node for policy enforcement and charging data collection (e.g., PCEF). Furthermore, the SGi reference point between the PGW 232 and the data network 236 may be an operator-external public, private PDN or an intra-operator packet data network, e.g., for the provision of IMS services. The PGW 232 may be coupled to the PCRF 234 via a Gx reference point.

[0061] The PCRF 234 is the policy and charging control element of the LTE CN 220. The PCRF 234 may be communicatively coupled to an app / content server 238 to determine appropriate QoS and charging parameters for a service flow. The PCRF 234 may provide the associated rules to the PCEF (over the Gx reference point) with the appropriate TFT and QCI.

[0062] In some embodiments, CN 220 may be 5GC 240. 5GC 240 may include AUSF 242, AMF 244, SMF 246, UPF 248, NSSF 250, NEF 252, NRF 254, PCF 256, UDM 258, and AF 260 coupled together over interfaces (or "reference points") as shown. The functionality of the elements of 5GC 240 may be briefly introduced as follows.

[0063] The AUSF 242 may store data and handle authentication related functions for authentication of the UE 202. The AUSF 242 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 240 over reference points as shown, the AUSF 242 may exhibit a Nausf service based interface.

[0064] The AMF 244 may enable other functions of the 5GC 240 to communicate with the UE 202 and the RAN 204, and to subscribe to notifications about mobility events related to the UE 202. The AMF 244 may be responsible for registration management (e.g., for registration of the UE 202), connection management, reachability management, mobility management, lawful interception of AMF related events, and access authentication and authorization. The AMF 244 may provide forwarding of SM messages between the UE 202 and the SMF 246 and act as a transparent proxy for routing of SM messages. The AMF 244 may also provide forwarding of SMS messages between the UE 202 and the SMSF. The AMF 244 may interact with the AUSF 242 and the UE 202 to perform various security anchor and context management functions. Additionally, the AMF 244 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between the RAN 204 and the AMF 244, and the AMF 244 may be the termination point of the NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 244 may also support NAS signaling with the UE 202 over the N3 IWF interface.

[0065] The SMF 246 may be responsible for SM (e.g., session establishment between the UPF 248 and the AN 208, tunnel management), UE IP address allocation and management (including optional authorization), selection and control of UP functions, configuration of traffic steering in the UPF 248 to route traffic to the appropriate destination, termination of the interface towards the policy control function, policy enforcement, control of charging and part of QoS, lawful interception (for SM events and interface to the LI system), termination of the SM part of NAS messages, downlink data notification, initiation of AN specific SM information sent over N2 to the AN 208 via the AMF 244, and determination of the SSC mode of the session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between the UE 202 and the data network 236.

[0066] The UPF 248 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 236, and a branching point to support multi-homed PDU sessions. The UPF 248 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform user plane QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., mapping flows from SDF to QoS), mark transport level packets in the uplink and downlink, buffer downlink packets, and trigger downlink data notifications. The UPF 248 may include an uplink classifier to support routing traffic flows to the data network.

[0067] The NSSF 250 may select a set of network slice instances to serve the UE 202. The NSSF 250 may also determine the allowed NSSAI and, if necessary, the mapping to the subscribed S-NSSAI. The NSSF 250 may also determine the AMF set to be used to serve the UE 202, or a list of candidate AMFs, based on a preferred configuration and possibly by querying the NRF 254. The selection of a set of network slice instances for the UE 202 may be triggered by the AMF 244 to which the UE 202 is registered, by interacting with the NSSF 250, which may result in a change of AMF. The NSSF 250 may interact with the AMF 244 via the N22 reference point and may communicate with another NSSF in the visited network via the N31 reference point (not shown). Additionally, the NSSF 250 may present an Nnssf service-based interface.

[0068] The NEF 252 may securely expose services and capabilities offered by 3GPP network functions for third parties, internal publication / republication, AFs (e.g., AF 260), edge computing or fog computing systems, etc. In such an embodiment, the NEF 252 may authenticate, authorize or throttle the AFs. The NEF 252 may also translate information exchanged with the AF 260 and with internal network functions. For example, the NEF 252 may translate between AF service identifiers and internal 5GC information. The NEF 252 may also receive information from other NFs based on the published capabilities of the other NFs. This information may be stored in the NEF 252 as structured data or may be stored in a data storage NF using a standardized interface. The stored information can then be republished by the NEF 252 to other NFs and AFs or used for other purposes such as analytics. Additionally, the NEF 252 may present an Nnef service-based interface.

[0069] The NRF 254 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to the NF instances. The NRF 254 may also maintain information about available NF instances and their supported services. As used herein, terms such as "instantiate" and "instantiation" may refer to the creation of an instance, and an "instance" may refer to a specific occurrence of an object that may occur, for example, during the execution of program code. Additionally, the NRF 254 may present an Nnrf service-based interface.

[0070] The PCF 256 may provide policy rules to the control plane functions to enforce them and may support a unified policy framework to govern network behavior. The PCF 256 may also implement a front end to access subscription information relevant to policy decisions in the UDRs of the UDM 258. In addition to communicating with functions over reference points as shown, the PCF 256 may present an Npcf service-based interface.

[0071] The UDM 258 may process subscription related information to support processing of communication sessions by network entities and may store subscription data of the UE 202. For example, the subscription data may be communicated over the N8 reference point between the UDM 258 and the AMF 244. The UDM 258 may include two parts: an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 258 and the PCF 256, and / or structured data for publishing and application data for the NEF 252 (including PFD for application discovery, application request information for multiple UEs 202). A Nudr service-based interface may be presented by the UDR 221 to allow the UDM 258, the PCF 256, and the NEF 252 to access a particular set of stored data, and to read, update (e.g., add, modify), delete, subscribe notifications of changes of the relevant data in the UDR. The UDM may include a UDM-FE responsible for certificate processing, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 258 may present a Nudm service-based interface.

[0072] The AF 260 may provide application influence over traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0073] In some embodiments, the 5GC 240 may enable edge computing by selecting an operator / third-party service that will be geographically close to the point where the UE 202 attaches to the network. This may reduce latency and load on the network. To provide edge computing implementation, the 5GC 240 may select a UPF 248 that is close to the UE 202 and perform traffic steering from the UPF 248 to the data network 236 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 260. In this way, the AF 260 may influence the UPF (re)selection and traffic routing. Based on the operator deployment, once the AF 260 is considered a trusted entity, the network operator may allow the AF 260 to directly interact with the associated NFs. Additionally, the AF 260 may present a Naf service-based interface.

[0074] Data network 236 may represent various network operator services, Internet access, or third party services, which may be provided by one or more servers, including, for example, application / content server 238 .

[0075] 3 illustrates a schematic of a wireless network 300 in accordance with various embodiments. The wireless network 300 may include a UE 302 in wireless communication with an AN 304. The UE 302 and the AN 304 may be similar to, and substantially interchangeable with, similarly named components described elsewhere herein.

[0076] The UE 302 may be communicatively coupled to the AN 304 via a connection 306. The connection 306 is shown as an air interface that enables the communicative coupling and may be consistent with a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.

[0077] The UE 302 may include a host platform 308 coupled to a modem platform 310. The host platform 308 may include an application processing circuit 312 that may be coupled to a protocol processing circuit 314 of the modem platform 310. The application processing circuit 312 may execute various applications for the UE 302 to source / sink application data. The application processing circuit 312 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0078] The protocol processing circuitry 314 may implement one or more of the layer operations to facilitate transmission or reception of data over the connection 306. The layer operations implemented by the protocol processing circuitry 314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0079] The modem platform 310 may further include digital baseband circuitry 316 that may implement one or more layer operations "below" the layer operations performed by the protocol processing circuitry 314 in a network protocol stack. These operations may include PHY operations including, for example, HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding which may include one or more of space-time, space-frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0080] The modem platform 310 may include transmit circuitry 318, receive circuitry 320, RF circuitry 322, and an RF front end (RFFE) 324 that may include or connect to one or more antenna panels 326. Briefly, the transmit circuitry 318 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc., the receive circuitry 320 may include analog-to-digital converters, mixers, IF components, etc., the RF circuitry 322 may include low noise amplifiers, power amplifiers, power tracking components, etc., and the RFFE 324 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and configuration of the transmit circuitry 318, receive circuitry 320, RF circuitry 322, RFFE 324, and antenna panel 326 components (commonly referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as, for example, whether communications are TDM or FDM, mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be configured with multiple parallel transmit / receive chains, located on the same or different chips / modules, etc.

[0081] In some embodiments, the protocol processing circuit 314 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.

[0082] UE reception may be established by and through the antenna panel 326, the RFFE 324, the RF circuitry 322, the receive circuitry 320, the digital baseband circuitry 316, and the protocol processing circuitry 314. In some embodiments, the antenna panel 326 may receive transmissions from the AN 304 by receive beamforming signals received by multiple antennas / antenna elements of one or more of the antenna panels 326.

[0083] UE transmissions may be established by and through the protocol processing circuitry 314, the digital baseband circuitry 316, the transmit circuitry 318, the RF circuitry 322, the RFFE 324, and the antenna panel 326. In some embodiments, the transmit components of the UE 302 may apply spatial filters to data to be transmitted in order to form transmit beams that are radiated by antenna elements of the antenna panel 326.

[0084] Similar to the UE 302, the AN 304 may include a host platform 328 coupled to a modem platform 330. The host platform 328 may include an application processing circuit 332 coupled to a protocol processing circuit 334 of the modem platform 330. The modem platform may further include a digital baseband circuit 336, a transmit circuit 338, a receive circuit 340, an RF circuit 342, an RFFE circuit 344, and an antenna panel 346. The components of the AN 304 may be similar to, or substantially interchangeable with, similarly named components of the UE 302. In addition to performing data transmission / reception as described above, the components of the AN 304 may perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0085] 4 is a block diagram illustrating components that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein, according to some example embodiments. Specifically, FIG. 4 illustrates a schematic representation of hardware resources 400 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 a bus 440 or other interface circuitry. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 402 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 400.

[0086] Processors 410 may include, for example, processor 412 and processor 414. Processor 410 may be, for example, 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 DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0087] Memory / storage device 420 may include main memory, disk storage, or any suitable combination thereof. Memory / storage device 420 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, 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.

[0088] Communications resources 430 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 404 or one or more databases 406 or other network elements over network 408. For example, communications resources 430 may include wired communications components (e.g., for coupling via USB, Ethernet, etc.), cellular communications components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communications components.

[0089] The instructions 450 may include software, programs, applications, applets, apps, or other executable code to cause at least one of the processors 410 to perform any one or more of the methodologies discussed herein. The instructions 450 may reside completely or partially within at least one of the processors 410 (e.g., in a cache memory of the processor), the memory / storage device 420, or any suitable combination thereof. Additionally, any portion of the instructions 450 may be transferred to the hardware resources 400 from any combination of the peripheral device 404 or the database 406. Thus, the memory of the processor 410, the memory / storage device 420, the peripheral device 404, and the database 406 are examples of computer-readable and machine-readable media.

[0090] For one or more embodiments, at least one of the components outlined in one or more of the figures above may be configured to perform one or more operations, techniques, processes, and / or methods as outlined in the example section below. For example, baseband circuitry associated with one or more of the figures above may be configured to operate according to one or more of the examples described below. In another example, circuitry associated with a UE, base station, satellite, network element, etc. as described above in connection with one or more of the figures above may be configured to operate according to one or more of the examples described below in the example section.

[0091] The term "application" may refer to a complete, deployable package or environment for achieving a particular function in an operating environment. Terms such as "AI / ML application" may be an application that includes several artificial intelligence (AI) / machine learning (ML) models and application-level descriptions. In some embodiments, an AI / ML application may be used to configure or implement one or more aspects of the disclosure.

[0092] The term "machine learning" or "ML" refers to the use of a computer system that implements algorithms and / or statistical models to perform a particular task without explicit instructions, relying instead on patterns and inference. An ML algorithm builds or infers a mathematical model (called an "ML model", etc.) based on sample data (called "training data", "model training information", etc.) to make predictions or decisions without being explicitly programmed to perform such a task. In general, an ML algorithm is a computer program that learns from experience with respect to some task and some performance indicators, and an ML model may be any object or data structure created after an ML algorithm is trained on one or more training data sets. After training, the ML model may be used to make predictions on new data sets. Although the term "ML algorithm" refers to a different concept than the term "ML model", these terms discussed herein may be used interchangeably in this disclosure.

[0093] Terms such as "machine learning model", "ML model", etc. may also refer to ML methods and concepts used by an ML-assisted solution. An "ML-assisted solution" is a solution that uses ML algorithms to address a particular use case during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithms, ensemble algorithms, etc.), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, etc. Depending on the implementation, a particular ML model may have many sub-models as components, and the ML model may train all the sub-models together. Separately trained ML models may also be chained together in an ML pipeline during inference. An "ML pipeline" is a set of functionality, functions, or functional entities specific to an ML-assisted solution, and the ML pipeline may include one or several data sources among a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. An "actor" is an entity that hosts an ML-assisted solution using the output of ML model inference. The term "ML training host" refers to an entity, such as a network function, that hosts the training of a model. The term "ML inference host" refers to an entity, such as a network function, that hosts a model during inference mode (including both model execution and any online learning, if applicable). The ML host informs the actor about the output of the ML algorithm, and the actor decides on an action (an "action" is taken by the actor as a result of the output of the ML-assisted solution).The term "model inference information" refers to information used as input to an ML model to determine inferences, and although the data used to train the ML model and the data used to determine inferences may overlap, "training data" and "inference data" refer to different concepts.

[0094] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated and integrated communications platforms. The next generation wireless communications system, 5G or new radio (NR), provides access to information and sharing of data anywhere, anytime by various users and applications. NR is envisioned to be a unified network / system that targets to meet very different and sometimes competing performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with further potential new Radio Access Technologies (RATs) to enrich people's lives with better, easier and seamless wireless connectivity solutions. NR will enable everything connected by wireless, delivering high speed and rich content and services.

[0095] As defined in NR, one slot has 14 symbols. For systems operating at carrier frequencies above 52.6 GHz, if a larger subcarrier spacing (SCS) is used, e.g., 960 kHz, the slot duration can be very short. For example, for an SCS of 960 kHz, one slot duration is approximately 15.6 μs, as shown in FIG. 5.

[0096] FIG. 5 illustrates a diagram 500 of short slot duration with larger subcarrier spacing in accordance with some aspects.

[0097] In NR, a control resource set (CORESET) is a set of time / frequency resources that carry PDCCH transmissions. The CORESET is divided into multiple control channel elements (CCEs). A physical downlink control channel (PDCCH) candidate with aggregation level (AL) L is composed of L CCEs. L may be 1, 2, 4, 8, or 16. A search space set can be configured for a UE, which configures the timing for PDCCH monitoring and the set of CCEs that carry PDCCH candidates for the UE.

[0098] For carrier aggregation (CA) with cells in different frequency ranges (FR, radio frequency), the difference in subcarrier spacing (SCS) on the active bandwidth part (BWP) of two cells can be very large. For example, the length of a slot with SCS of 15 kHz is 64 times that of a slot with SCS of 960 kHz. When the scheduling cell and the scheduled cell have SCS of 15 kHz and 960 kHz, respectively, in cross-carrier scheduling (CCS), the number of PDCCHs processed for the scheduled cell per scheduling cell slot needs to be increased to a large number for flexible scheduling. In this case, a certain restriction may be applied to the difference in subcarrier spacing between the scheduling cell and the scheduled cell when CCS is applied.

[0099] The disclosed techniques can be used to handle cross-carrier scheduling in systems operating at carrier frequencies above 52.6 GHz when the scheduling cell and the scheduled cell have large differences in numerology.

[0100] In some aspects, for CA with cells in different frequency ranges (FR, radio frequency), the difference in SCS on the active BWPs of two cells can be very large. For example, the length of a slot with SCS of 15 kHz is 64 times that of a slot with SCS of 960 kHz. If the scheduling cell and the scheduled cell have SCSs of 15 kHz and 960 kHz, respectively, in cross-carrier scheduling (CCS), the number of PDCCHs processed for the scheduled cell per scheduling cell slot needs to be increased to a large number for flexible scheduling. However, the increase in PDCCHs processed on the scheduling cell results in high UE complexity. Therefore, it may be considered to have a limit on the difference between the SCS of the scheduling cell and the SCS of the scheduled cell. The SCS of the current active BWPs on the scheduling cell and the scheduled cell may be set to 250 kHz, respectively. μDCI 15kHz and 2 μDATA ·15kHz. The limit is |μ DCI -μ DATA |≦d max For example, d max may be 3, 4 or 5. The UE selects |μ DCI -μ DATA |>d max In some embodiments, μ DCI is the numerology used in the primary (e.g., scheduling) cell, and μ DATA is the numerology used in the secondary (e.g., scheduled) cell of the base station.

[0101] In some embodiments, |μ DCI -μ DATA |≦d max With the above restriction, for a configured scheduling cell and a configured scheduled cell, it is conceivable that the CCS is applicable to some combinations of the BWPs of the scheduling cell and the scheduled cell. However, for other combinations of the BWPs of the scheduling cell and the scheduled cell, the CCS is not applicable. When the CCS is configured, the scheduling cell is a scheduled cell that is also scheduled by the scheduling cell. A solution for handling the inapplicable combinations of the BWPs of the scheduling cell and the scheduled cell can be configured using the disclosed techniques.

[0102] In some embodiments, the numerology μ on the scheduling cell DCI For an active BWP with DATA,1 When a BWP with |μ DCI -μ DATA,1 |>d max The BWP switch for the scheduled cell may be indicated by a BWP indicator field in the DCI, unless a dedicated restriction is explicitly captured, or may be triggered by a timer, e.g., bwp-InactivityTimer. The DCI may be a DCI for single-cell PDSCH / PUSCH scheduling or a DCI for multi-cell PDSCH / PUSCH scheduling.

[0103] In some aspects, the UE determines whether an active BWP on a scheduled cell is |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1 In this option, only a subset of the configured BWPs on the scheduled cell can be used for CCS from the scheduling cell.

[0104] In some aspects, an active BWP on a scheduled cell is |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1 If the scheduled cell is changed to the first BWP having |μ DCI,1 -μ DATA,2 |≦d max The PDSCH / PUSCH transmission is not available for dynamically scheduled PDSCH / PUSCH transmission until the BWP is changed to satisfy μ DCI,1 is the numerology of the new active BWP on the scheduling cell if the active BWP is switched, otherwise, μ DCI,1 μ is the numerology of the currently active BWP of the scheduling cell. DATA,2 is the numerology of the new active BWP on the scheduled cell if the active BWP is switched, otherwise μ DATA,2 is the numerology of the currently active BWP of the scheduled cell. In this option, the UE may still transmit or receive higher layer configured signals / channels on the first BWP. Alternatively, the UE may not transmit or receive any signals / channels on the first BWP.

[0105] FIG. 6 illustrates a diagram 600 of cross-carrier scheduling when a scheduled cell becomes inapplicable, in accordance with some aspects. More specifically, FIG. 6 illustrates a cross-carrier scheduling diagram 600 of a scheduled cell when a scheduled cell becomes inapplicable due to |μ DCI -μ DATA,1 |>d max This shows an example where cross-carrier scheduling is not possible when switching to BWP2, which results in:

[0106] In some aspects, the BWP indicator field in the DCI is |μ DCI -μ DATA,1 |>dmax The numerology μ on the scheduled cell that results in DATA,1 If the DCI indicates a BWP with a BWP indicator field, the UE ignores the BWP indicator field and does not change the BWP for the scheduled cell. The UE may interpret the DCI as scheduling a PDSCH or PUSCH on the currently active BWP of the scheduled cell. Alternatively, the UE ignores the DCI.

[0107] In some embodiments, the BWP indicator field in the DCI is |μ DCI -μ DATA,1 |>d max The numerology μ on the scheduled cell that results in DATA,1 If the UE indicates a BWP with |μ DCI -μ DATA,2 |≦d max Numerology μ that satisfies DATA,2 The automatically switched BWP on the scheduled cell may be a default BWP, the first active BWP after SCell activation, or a dormant BWP, a BWP configured separately by higher layer signaling. Alternatively, the automatically switched BWP may be configured respectively depending on the active BWP of the scheduling cell. Alternatively, the automatically switched BWP may be configured respectively for each BWP of the scheduled cell. Alternatively, the automatically switched BWP for each BWP of the scheduled cell may be configured respectively depending on the active BWP of the scheduling cell. In some aspects, the automatically switched BWP on the scheduled cell has |μ DCI -μ DATA,2 |≦d max It may be up to the gNB implementation to ensure that the above condition is met. The UE may interpret the DCI as scheduling a PDSCH or PUSCH on the automatically switched BWP of the scheduled cell.

[0108] In some aspects, an active BWP on a scheduled cell is |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1 If the BWP is changed to one with |μ, then self-scheduling is applied to the BWP on the scheduled cell. The search space (SS) set for self-scheduling on the BWP of the scheduled cell can be configured separately from the SS set for cross-carrier scheduling. The SS set for self-scheduling is |μ DCI -μ DATA,1 |>d max The UE monitors only if

[0109] In some aspects, the numerology μ on the scheduled cell DATA For an active BWP with numerology μ on the scheduling cell DCI,1 When a BWP with |μ DCI,1 -μ DATA |>d max The BWP switch for the scheduling cell may be indicated by a BWP indicator field in the DCI, unless a dedicated restriction is explicitly captured, or may be triggered by a timer, e.g., bwp-InactivityTimer. The DCI may be a DCI for single-cell PDSCH / PUSCH scheduling or a DCI for multi-cell PDSCH / PUSCH scheduling.

[0110] In some embodiments, the UE may be configured to detect whether an active BWP on a scheduling cell is |μ DCI,1 -μ DATA |>d max The result is numerology μ DCI,1In this option, only a subset of the configured BWPs on the scheduling cell can be used for CCS from the scheduling cell.

[0111] In some embodiments, an active BWP on a scheduling cell may be configured to receive |μ DCI,1 -μ DATA |>d max The result is numerology μ DCI,1 If the scheduled cell is changed to a BWP with |μ DCI,2 -μ DATA,1 |≦d max The PDSCH / PUSCH transmission is not available for dynamically scheduled PDSCH / PUSCH transmission until the BWP is changed to satisfy μ DCI,2 is the numerology of the new active BWP on the scheduling cell if the active BWP is switched, otherwise, μ DCI,2 μ is the numerology of the currently active BWP of the scheduling cell. DATA,1 is the numerology of the new active BWP on the scheduled cell if the active BWP is switched, otherwise μ DATA,1 is the numerology of the currently active BWP of the scheduled cell. In this option, the UE still DCI,1 -μ DATA |>d max Alternatively, the UE may transmit or receive higher layer configured signals / channels on the active BWP of the scheduled cell, which results in |μ DCI,1 -μ DATA |>d max This results in no need to transmit or receive any signals / channels on the active BWP of the scheduled cell.

[0112] In some embodiments, an active BWP on a scheduling cell may be configured or activated for a scheduled cell or a currently scheduled cell or a currently not scheduled scheduled cell. DCI,1 -μ DATA |>d max The result is numerology μ DCI,1 If the UE is switched to a BWP having |μ, the UE ignores the BWP indicator field and does not change the BWP for the scheduling cell. DCI,1 -μ DATA |≦d max For the currently scheduled cell that satisfies DCI, the UE may process the PDSCH or PUSCH transmission on the scheduled cell. Alternatively, the UE ignores the DCI.

[0113] In another option, an active BWP on a scheduling cell may use |μ DCI,1 -μ DATA |>d max The result is numerology μ DCI,1 If the scheduled cell is changed to a BWP with |μ DCI,1 -μ DATA,1 |≦d max Numerology μ that satisfies DATA,1The automatically switched BWP on the scheduled cell may be a default BWP, the first active BWP after SCell activation, or a dormant BWP, or a BWP configured separately by higher layer signaling. Alternatively, the automatically switched BWP may be configured respectively depending on the active BWP of the scheduling cell. Alternatively, the automatically switched BWP may be configured respectively for each BWP of the scheduled cell. Alternatively, the automatically switched BWP for each BWP of the scheduled cell may be configured respectively depending on the active BWP of the scheduling cell. If the automatically switched BWP on the scheduled cell has |μ DCI,1 -μ DATA,1 |≦d max It is up to the gNB implementation to ensure that

[0114] 7 illustrates a diagram 700 of automatic bandwidth portion (BWP) switching on a scheduled cell, in accordance with some aspects. More specifically, FIG. 7 illustrates an example of a scheduled cell switching from |μ DCI,1 -μ DATA,1 |≦d max 6 shows an example in which the BWP on the scheduled cell that satisfies the above condition can be automatically changed to BWP2.

[0115] In some embodiments, an active BWP on a scheduling cell may be configured or activated for a scheduled cell or a currently scheduled cell or a currently not scheduled scheduled cell. DCI,1 -μ DATA |>d max The result is numerology μ DCI,1If the BWP is changed to one with |μ, then self-scheduling is applied to the BWP on the scheduled cell. The search space set for self-scheduling on the BWP of the scheduled cell can be configured separately from the SS set for cross-carrier scheduling. The SS set for self-scheduling is |μ DCI,1 -μ DATA |>d max The UE monitors only if

[0116] In some aspects, in multi-cell PDSCH / PUSCH scheduling, the BWP on the scheduling cell and / or the scheduled cell, when activated, may be DCI,1 -μ DATA,1 |>d max This may result in μ DCI,1 is the numerology of the BWP on the scheduling cell after the BWP switch if the BWP indicator in the DCI indicates a BWP different from the active BWP on the scheduling cell, otherwise μ DCI,1 μ is the numerology of the currently active BWP of the scheduling cell. DATA,1 μ is the numerology of the BWP on the scheduled cell after the BWP switch if the BWP indicator in the DCI indicates a BWP different from the active BWP on the scheduled cell, otherwise μ DATA,1 is the numerology of the currently active BWP of the scheduled cell. The DCI format for multi-cell scheduling can schedule PDSCH or PUSCH transmissions on multiple cells. BWP switching for the scheduling cell or the scheduled cell may be indicated by a BWP indicator field in the DCI, unless a dedicated restriction is explicitly captured, or may be triggered by a timer, e.g., bwp-InactivityTimer.

[0117] In some embodiments, the UE may be configured to receive the BWP indicator in the DCI for any configured or activated scheduled cell or any currently scheduled cell according to the DCI. DCI,1 -μ DATA,1 |>d max It is not intended to indicate a BWP on the scheduling cell and / or the scheduled cell which would result in

[0118] In some aspects, the BWP indicator in the DCI is |μ for any configured or activated scheduled cell or any currently scheduled cell or currently not scheduled by the DCI. DCI,1 -μ DATA,1 |>d max If the scheduled cell indicates a BWP on the scheduling cell and / or the scheduled cell that results in |μ DCI,2 -μ DATA,2 |≦d max The PDSCH / PUSCH transmission is not available for dynamically scheduled PDSCH / PUSCH transmission until the BWP is changed to satisfy μ DCI,2 is the numerology of the new active BWP on the scheduling cell if the active BWP is switched, otherwise, μ DCI,2 μ is the numerology of the currently active BWP of the scheduling cell. DATA,2 is the numerology of the new active BWP on the scheduled cell if the active BWP is switched, otherwise μ DATA,2 is the numerology of the currently active BWP of the scheduled cell. In this aspect, the UE still DCI,1 -μ DATA,1 |>d max Alternatively, the UE may transmit or receive higher layer configured signals / channels on the active BWP of the scheduled cell, which results in |μ DCI,1 -μDATA,1 |>d max This results in no need to transmit or receive any signals / channels on the active BWP of the scheduled cell.

[0119] In some aspects, the BWP indicator in the DCI is |μ for any configured or activated scheduled cell or any currently scheduled cell or currently not scheduled by the DCI. DCI,1 -μ DATA,1 |>d max If the DCI indicates a BWP on the scheduling cell and / or scheduled cell that results in |μ, the UE ignores the BWP indicator field and does not change the BWP for the scheduling cell and / or scheduled cell. The UE may interpret the DCI as scheduling a PDSCH or PUSCH on the current active BWP of the scheduling cell and / or scheduled cell. DCI,1 -μ DATA,1 |≦d max For the currently scheduled cell that satisfies DCI, the UE may process the PDSCH or PUSCH transmission on the scheduled cell. Alternatively, the UE ignores the DCI.

[0120] In another aspect, the BWP indicator in the DCI is |μ DCI,1 -μ DATA,1 |>d max If the BWP on the scheduling cell and / or the scheduled cell that results in |μ DCI,1 -μ DATA,2 |≦d max Numerology μ that satisfies DATA,2The automatically switched BWP on the scheduled cell may be a default BWP, the first active BWP after SCell activation, a dormant BWP, or a BWP configured separately by higher layer signaling. Alternatively, an automatically switched BWP may be configured for each BWP of the scheduled cell respectively. Alternatively, an automatically switched BWP may be configured respectively depending on the active BWP of the scheduling cell. If an automatically switched BWP on a scheduled cell has |μ DCI,1 -μ DATA,2 |≦d max It is up to the gNB implementation to ensure that

[0121] In another option, the active BWP on the scheduling cell and / or the scheduled cell is changed, and |μ DCI,1 -μ DATA,1 |>d max If this results in a self-scheduling, then self-scheduling is applied to the BWP on the scheduled cell. The search space set for self-scheduling on the BWP of the scheduled cell can be configured separately from the SS set for cross-carrier scheduling. The SS set for self-scheduling is |μ DCI,1 -μ DATA,1 |>d max The UE monitors only if

[0122] In some embodiments, a wireless communication system and method for cross-carrier scheduling of DL or UL transmissions includes the disclosed techniques. For example, a UE detects a PDCCH transmitted on an active BWP of a scheduling cell. The ... DCI -μ DATA |≦d maxIn this case, a PUSCH is transmitted or a PDSCH is received based on a PDCCH on an active BWP on a scheduled cell, and the SCS of the scheduling cell and the active BWP on the scheduled cell are 2 μDCI 15kHz and 2 μDATA -15kHz.

[0123] In some aspects, the BWP on the scheduled cell, when activated, DCI -μ DATA |>d max In some embodiments, the UE determines whether the active BWP on the scheduled cell is |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1 In some embodiments, an active BWP on a scheduled cell is not assumed to change to a BWP with |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1 , then the scheduled cell will not be available for dynamically scheduled PDSCH / PUSCH transmission on the first BWP.

[0124] In some aspects, the BWP indicator field in the DCI is |μ DCI -μ DATA,1 |>d max The numerology μ on the scheduled cell that results in DATA,1 If the UE indicates a BWP with 0, the UE does not change the BWP for the scheduled cell.

[0125] In some aspects, the BWP indicator field in the DCI is |μ DCI -μ DATA,1 |>d max The numerology μ on the scheduled cell that results in DATA,1 If the UE indicates a BWP with |μ DCI -μDATA,2 |≦d max Numerology μ that satisfies DATA,2 In some aspects, an active BWP on a scheduled cell automatically switches to a BWP having |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1 If the scheduled cell is changed to a BWP having a self-scheduling, self-scheduling is applied to the BWP on the scheduled cell.

[0126] In some embodiments, the BWP on the scheduling cell, when activated, DCI -μ DATA |>d max In some aspects, the UE may determine whether an active BWP on the scheduling cell is greater than |μ DCI,1 -μ DATA |>d max The result is numerology μ DCI,1 In some embodiments, an active BWP on a scheduling cell is not assumed to change to a BWP with |μ DCI,1 -μ DATA |>d max The result is numerology μ DCI,1 , then the scheduled cell will not be available for dynamically scheduled PDSCH / PUSCH transmission on the first BWP.

[0127] In some aspects, in a DCI for self-scheduling of a scheduling cell, the DCI may be DCI,1 -μ DATA |>d max The numerology μ on the scheduling cell that results in DCI,1If the UE indicates an active BWP with |μ DCI,1 -μ DATA |>d max The result is numerology μ DCI,1 If the scheduled cell is changed to a BWP with |μ DCI,1 -μ DATA,1 |≦d max Numerology μ that satisfies DATA,1 The system will automatically switch to a BWP with

[0128] In some aspects, an active BWP on a scheduling cell may be DCI,1 -μ DATA |>d max The result is numerology μ DCI,1 If the scheduled cell is changed to a BWP having a self-scheduling, self-scheduling is applied to the BWP on the scheduled cell.

[0129] In some embodiments, in multi-cell PDSCH / PUSCH scheduling, the BWP on the scheduling cell and / or the scheduled cell, when activated, is DCI,1 -μ DATA,1 |>d max In some aspects, the UE may determine whether the BWP indicator in the DCI is greater than |μ DCI,1 -μ DATA,1 |>d max It is not intended to indicate a BWP on the scheduling cell and / or the scheduled cell which would result in

[0130] In some embodiments, the BWP indicator in the DCI is |μ DCI,1 -μ DATA,1 |>d maxIn some aspects, if the BWP indicator in the DCI indicates a first BWP on the scheduling cell and / or the scheduled cell that results in |μ DCI,1 -μ DATA,1 |>d max In some aspects, if the BWP indicator in the DCI indicates a BWP on the scheduling cell and / or the scheduled cell that results in |μ DCI,1 -μ DATA,1 |>d max If the BWP on the scheduling cell and / or the scheduled cell that results in |μ DCI,1 -μ DATA,2 |≦d max Numerology μ that satisfies DATA,2 In some embodiments, the active BWP on the scheduling cell and / or the scheduled cell is changed to one having |μ DCI,1 -μ DATA,1 |>d max If this results in self-scheduling being applied to the BWP on the scheduled cell.

[0131] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated and integrated communications platforms. The next generation wireless communications system, 5G or new radio (NR), provides access to information and sharing of data anywhere, anytime by various users and applications. NR is envisioned as a unified network / system that aims to meet very different and sometimes competing performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with further potential new Radio Access Technologies (RATs) to enrich people's lives with better, easier and seamless wireless connectivity solutions. NR will enable everything connected by wireless and deliver high speed and rich content and services.

[0132] In NR, HARQ-based PDSCH transmission may be adopted. The gNB schedules PDSCH transmission by transmitting DCI. The PDSCH transmission carries only one TB if the number of MIMO layers is four or less. Otherwise, two TBs are transmitted. The UE detects the DCI, decodes the PDSCH, and then reports HARQ-ACK information to the gNB. As a result, the gNB may schedule a new transport block (TB) or a retransmission of a previous TB depending on the HARQ-ACK information from the UE.

[0133] For a Type 1 HARQ-ACK codebook in NR, the set of occasions for candidate PDSCH reception is determined based on the configured set of slot timing values ​​K1, the configured time division duplex (TDD) UL-DL configuration (i.e., TDD UL-DL configuration Common and TDD UL-DL configuration Dedicated), and the time domain resource allocation (i.e., Start and Length Indicator Value or SLIV) table. Depending on the UE capabilities, the number of occasions for a slot associated with a value n-K1 is either at most 1 or is determined by the non-overlapping SLIVs in the slot.

[0134] For systems operating at carrier frequencies above 52.6 GHz, the subcarrier spacing increases and the slot duration decreases. The DCI may schedule PDSCH transmissions using one or more TBs. FIG. 8 illustrates an example of multi-PDSCH scheduling. More specifically, FIG. 8 illustrates a diagram 800 of multi-transmission time interval (TTI) scheduling for PDSCH according to some aspects. In diagram 800, four PDSCHs (PDSCH#0-3) with different transport blocks (TBs) are scheduled by a single DCI.

[0135] The disclosed techniques include designs for HARQ-ACK transmission assuming that multiple PDSCHs can be scheduled by DCI. The disclosed techniques also include designs for performing time bundling for semi-static HARQ-ACK codebooks for multi-PDSCH scheduling in systems operating above 52.6 GHz carrier frequencies, taking into account potential limitations on multi-PDSCH scheduling for codebook size reduction.

[0136] In some aspects, a DCI may be capable of scheduling one or more PDSCHs using separate TBs. The number of PDSCHs scheduled by a DCI may be explicitly indicated by a field in the DCI. Alternatively, the number of PDSCHs scheduled by a DCI is coded together with other information fields. For example, the number of PDSCHs scheduled for a row in a time-domain resource allocation (TDRA) table is equal to the number of configured SLIVs of the row. The maximum number of PDSCHs scheduled by a multi-TTI DCI is the maximum number of scheduled PDSCHs among all rows. For a row of a TDRA table, each SLIV can be configured in a different slot. Alternatively, one or more SLIVs may be configured in the same slot.

[0137] The use of multi-TTI scheduling for PDSCH transmission does not necessarily mean that the uplink channel condition is good, so it is beneficial to apply a certain bundling scheme to reduce the HARQ-ACK payload on the PUCCH or PUSCH.

[0138] In some embodiments, a value K in the set K 1,k One or more end DL slots for PDSCH transmission can be determined corresponding to the value K 1,k and UL slot n U For HARQ-ACK transmission in, PUSCH transmission is DL slot

[0139]

number

[0140] Value K in set K1 1,kFor each DL slot determined by, the pair (d k,j ,r) can be determined. k,j ,r) is the value K 1,k and indicates a PDSCH transmission that can be scheduled by the DCI indicating row r in the TDRA table, and DL slot

[0141]

number

[0142] To assign an occasion for the determined DL slot, the pair (d k,j ,r) sets. Alternatively, duplicate checking can be done using pairs (d k,j This can be done using the SLIV in the DL slot determined from the set of (d , r). For one determined DL slot, at most one occasion can be assigned. In particular, for the determined DL slot, k,jIf at least one SLIV from the set of (r, r) is available for PDSCH transmission in the determined DL slot, then one occasion can be assigned for the determined DL slot. Alternatively, zero, one or multiple occasions may be assigned for a determined DL slot, assuming that one or more PDSCHs can be scheduled in the slot.

[0143] In some aspects, an occasion may be first assigned for each slot in the determined set of DL slots, and then multiple occasions may be bundled to generate a bundled occasion. The payload size of the Type-1 codebook may be determined by the number of bundled occasions.

[0144] In some aspects, the occasions in a bundle of N consecutive DL slots are bundled into one bundled occasion, where N is predefined or configured by higher layer signaling. For HARQ-ACK transmission in a UL slot, the minimum and maximum indices of the determined DL slots are denoted by D min , D max The set of DL slots considered in generating the Type 1 HARQ-ACK codebook is denoted as DL slot index D min ,D min +1...,D max The bundles of DL slots can be assigned sequentially in ascending order of slot index or descending order of slot index. The last bundle may have less than N DL slots. For example,

[0145]

number

[0146]

number

[0147] FIG. 9 illustrates a diagram 900 of occasion bundling in consecutive slots according to some aspects. More specifically, FIG. 9 illustrates an example of occasion bundling in every two consecutive slots. It can be assumed that three values ​​of K1 are configured, namely 2, 4, and 8, and the maximum number of SLIVs among all rows in the TDRA table is 3. Thus, for a PUCCH transmission in slot n, the set of determined DL slots is n-10, n-9, n-8, n-6, n-5, n-4, n-3, and n-2. It can be assumed that the bundles of DL slots are assigned starting from slot n-2 in descending order of slot index. At most one occasion can be assigned in each of the determined DL slots. Slots n-7 and n-6 ​​form a bundle. Since slot n-7 cannot carry PDSCH with HARQ-ACK in PUCCH in slot n, the bundled HARQ-ACK for the bundle is determined purely by the HARQ-ACK information in slot n-6. Slot n-10 is also a separate bundle.

[0148] In some aspects, the occasions in a bundle of N determined DL slots are bundled into one bundled occasion. The bundles of determined DL slots can be assigned sequentially in ascending order of slot index or descending order of slot index. The final bundle may have less than N determined DL slots. For example, for a HARQ-ACK transmission in a UL slot, the set of determined DL slots may be assigned as

[0149]

number

[0150]

number

[0151]

number

[0152] FIG. 10 illustrates a diagram 1000 of occasion bundling in determined downlink (DL) slots, according to some aspects. More specifically, FIG. 10 illustrates an example of occasion bundling in every two determined DL slots. This uses the same assumptions for K1 and set of TDRA tables as in FIG. 9. Assume that the bundles of determined DL slots are assigned starting from slot n-10 in ascending order of slot index. Slot n-7 is skipped in the bundling since it is not a determined DL slot for UL slot n.

[0153] In some embodiments, occasions in a bundle of N determined DL slots with assigned occasions are bundled into one bundled occasion. If there is no SLIV schedulable by considering the TDD UL-DL configuration for the determined DL slot, no occasion is assigned for the determined DL slot. The bundles of determined DL slots with assigned occasions can be assigned sequentially in ascending order of slot index or descending order of slot index. The last bundle may have less than N DL slots with assigned occasions. For example, for a HARQ-ACK transmission in a UL slot, the set of determined DL slots with assigned occasions may be assigned as

[0154]

number

[0155]

number

[0156]

number

[0157] FIG. 11 illustrates a diagram 1100 of occasion bundling in determined downlink DL slots with assigned occasions, according to some aspects. More specifically, FIG. 11 illustrates an example of occasion bundling in every two determined DL slots with assigned occasions. This uses the same assumptions for K1 and set of TDRA tables as in FIG. 9. Assume that the bundles of determined DL slots with assigned occasions are assigned starting from slot n-2 in descending order of slot index. Slot n-7 is skipped in the bundling since it is not a determined DL slot for UL slot n. No occasion is assigned to slot n-5 since it is an uplink slot and cannot be used for PDSCH transmission. Therefore, slot n-5 is also skipped in the bundling.

[0158] In some aspects, each bundle of N consecutive occasions is bundled into one bundled occasion. The bundles of occasions can be assigned sequentially in ascending order of occasion index or descending order of occasion index. The final bundle may have less than N occasions. For example, for a HARQ-ACK transmission in a UL slot, the set of occasions may be

[0159]

number

[0160]

number

[0161]

number

[0162] In some embodiments, an occasion is assigned only if at least one potential SLIV corresponding to the occasion does not overlap any UL symbol according to the TDD UL-DL configuration. Each bundle of N consecutive occasions is bundled into one bundled occasion. The bundles of occasions can be assigned sequentially in ascending order of occasion index or descending order of occasion index. The last bundle may have less than N occasions. For example, for a HARQ-ACK transmission in a UL slot, the set of assigned occasions can be

[0163]

number

[0164]

number

[0165]

number

[0166] Since multiple PDSCHs are scheduled by the same DCI, they are either received in their entirety or not. As a result, there is no error case of losing a subset of multiple PDSCHs. Therefore, bundling of HARQ-ACK bits for PDSCHs scheduled by multi-TTI DCI can be error-free. In the above options, the gNB does not have to schedule two PDSCHs by two DCIs corresponding to the same bundled occasion. In this regard, confusion regarding the interpretation of bundled HARQ-ACK information at the gNB can be limited.

[0167] In some embodiments, the last PDSCH of a PDSCH transmission schedulable by a DCI cannot end earlier than the start of the first PDSCH of another PDSCH transmission schedulable by another DCI if the last PDSCH and the first PDSCH correspond to the same bundle of slots or occasions. In other words, a PDSCH transmission corresponding to a bundle of slots or occasions can only be scheduled by a single DCI. Multiple slots or occasions in a bundle share the bundled occasion. The payload size of the Type 1 codebook is determined by the number of bundled occasions. The maximum number of slots or occasions in a bundle is denoted as N and is predefined or configured by higher layer signaling. In this embodiment, the number of pairs (d k,j If at least one SLIV from the set of (r, . . . r) is available for PDSCH transmission in the determined DL slot, then one occasion may be allocated for the determined DL slot.

[0168] In some aspects, the bundle may correspond to up to N consecutive DL slots. For HARQ-ACK transmission in a UL slot, the determined minimum and maximum DL slot indices are denoted by D min , Dmax The bundle of DL slots is denoted as slot index D min From D max or slot index D max From D min N consecutive DL slots in a bundle can be assigned sequentially up to N UL symbols. Different bundles may contain different numbers of DL slots. The number of slots in each bundle should be maximized in order to reduce the HARQ payload size. If none of the N consecutive DL slots in a bundle is assigned an occasion, the corresponding bundled occasion can be omitted. If none of the N consecutive slots in a bundle can be used for PDSCH transmission, e.g., if any potential SLIV in a slot overlaps with at least one UL symbol according to the TDD UL-DL configuration, the corresponding bundled occasion can be omitted.

[0169] In some aspects, the bundle may correspond to up to N determined DL slots. For a HARQ-ACK transmission in a UL slot, the set of determined DL slots is denoted by D m ,m==0,1,...M-1. The determined bundles of DL slots can be assigned sequentially in ascending order of m or descending order of m. Different bundles may contain different numbers of DL slots. If none of the determined DL slots in a bundle can be used for PDSCH transmission with HARQ-ACK in the UL slot, e.g., if any potential SLIV in the determined DL slot overlaps with at least one UL symbol according to the TDD UL-DL configuration, the corresponding bundled occasion can be omitted.

[0170] FIG. 12 illustrates a diagram 1200 of flexible sizes of bundles of determined DL slots, according to some aspects. More specifically, FIG. 12 illustrates an example of an occasion bundle with up to two determined DL slots. Assume that two values ​​of K1 are configured, namely 2 and 5, and two rows are configured in the TDRA table, each consisting of four and three SLIVs. Thus, for a PUCCH transmission in slot n, the set of determined DL slots is slots n-8 to n-2. Assume that the bundles of determined DL slots are assigned starting from slot n-2 in descending order of slot index. One occasion can be assigned in each of the determined DL slots. Slots n-3 and n-2 form a bundle. Slots n-5 and n-4 cannot be a bundle, since row 1 with K1=2 and either row with K1=5 can be scheduled simultaneously. Thus, slot n-4 is a separate bundle. Slots n-6 and n-5 form a bundle. Slots n-8 and n-7 form a bundle. With such a bundling scheme, the bundled HARQ-ACK is only associated with PDSCHs scheduled by a single DCI.

[0171] In some embodiments, a bundle may correspond to up to N determined DL slots with assigned occasions. If there is no SLIV schedulable by considering the TDD UL-DL configuration for a determined DL slot, no occasion is assigned for the determined DL slot. For HARQ-ACK transmission in a UL slot, denote the set of determined DL slots with assigned occasions as Dm, m=0,1,...M-1. The bundles of determined DL slots can be assigned sequentially in ascending or descending order of m. Different bundles may contain different numbers of DL slots.

[0172] FIG. 13 illustrates a diagram 1300 of flexible sizes of bundles of determined DL slots with assigned occasions, according to some aspects. More specifically, FIG. 13 illustrates an example of an occasion bundle with two determined DL slots with assigned occasions. We use the same assumptions for the set of K1 and TDRA table as in FIG. 12. We assume that the bundles of determined DL slots are assigned starting from slot n-2 in descending order of slot index. No occasion is assigned to slot n-6 since it is an uplink slot and cannot be used for PDSCH transmission. Thus, slot n-6 is skipped in the determination of bundled occasions. Slots n-3 and n-2 form a bundle. Slot n-4 is a separate bundle. Slots n-7 and n-5 form a bundle. Slot n-8 forms a bundle.

[0173] In some embodiments, the bundled HARQ-ACK is an ACK if all HARQ-ACKs are ACKs in a bundle of N slots or occasions, otherwise the bundled HARQ-ACK is a NACK. If a slot is not scheduled with a PDSCH transmission in the N slots, it may be ignored in determining the bundled HARQ-ACK, or the HARQ-ACK for the slot may be considered as an ACK in the bundling operation.

[0174] In some aspects, occasions are described in a manner in which occasions are first assigned for each determined DL slot, and then occasions are bundled. Alternatively, occasions can be directly assigned considering a bundle of up to N consecutive slots or N determined DL slots. In one example, a bundled occasion is assigned if at least one potential SLIV does not overlap with any UL symbol in the N consecutive slots in the bundle according to the TDD UL-DL configuration. In another example, a bundled occasion is assigned if at least one potential SLIV does not overlap with any UL symbol in the N determined DL slots in the bundle according to the TDD UL-DL configuration.

[0175] In some embodiments, a set of SLIVs of a row r in the TDRA table can be divided into at most B bundles (B≧1), and the at most B bundles are associated one by one with the at most B reference SLIVs of row r. The HARQ-ACKs associated with the SLIVs of a bundle are bundled. The reference SLIV of a bundle may not be an element of the bundle of SLIVs. The reference SLIV for the bundle of row r must be an element of row r. A reference SLIV is considered available for PDSCH transmission if at least one SLIV in the bundle of SLIVs associated with the reference SLIV is available for PDSCH transmission. SLIVs other than the at most B reference SLIVs are removed from row r. Finally, occasions for candidate PDSCH reception can be assigned by a set of K1 values ​​and a modified TDRA table, where each row r contains only reference SLIVs.

[0176] In some aspects, the above set of SLIVs for row r is a set of configured SLIVs for row r by higher layer signaling. The number of configured SLIVs is denoted as L, and the configured SLIVs are indexed by 0, 1, ..., L-1. A maximum number of bundles, B, can be configured by higher layers. The L configured SLIVs are then split into at most B bundles. Each bundle is

[0177]

number

[0178]

number

[0179] In some embodiments, for a PDSCH transmission that ends in a DL slot, the above set of SLIVs in row r includes only available SLIVs in row r if the SLIVs do not overlap with UL symbols according to the configured TDD UL-DL configuration. Let us denote the number of available SLIVs as LA, and the available SLIVs are 0, 1, ..., L A The maximum number of bundles, B, can be configured by higher layers. The LA available SLIVs are then divided into at most B bundles. Each bundle is

[0180]

number

[0181]

number

[0182] In some embodiments, to allocate occasions for HARQ-ACK transmissions using time bundling, (a) A set of DL slots is determined that includes all unique DL slots obtained by considering all combinations of configured K1 values ​​and reference SLIVs in all rows of the modified TDRA table.

[0183] (b) A set of reference SLIVs corresponding to the determined DL slot is determined, which includes all reference SLIVs for the determined DL slot obtained by considering all combinations of configured K1 values ​​and reference SLIVs in all rows of the modified TDRA table.

[0184] (c) Given the configured TDD UL-DL configuration, an occasion is determined with a set of reference SLIVs corresponding to each determined DL slot, where a reference SLIV is considered available for PDSCH transmission if at least one SLIV in the bundle of SLIVs associated with the reference SLIV is available for PDSCH transmission. For example, the existing procedure for Type-1 HARQ-ACK codebook generation in Rel-16 (TS 38.213, Section 9.1.2.1) can be reused, except for adopting the above rule in checking the availability of the reference SLIV.

[0185] Alternatively, to allocate occasions for HARQ-ACK transmission using time bundling, (a) A set of DL slots is determined that includes all unique DL slots obtained by considering all combinations of configured K1 values ​​and reference SLIVs in all rows of the modified TDRA table.

[0186] (b) A pair (d) corresponding to the determined DL slot, including all pairs for the determined DL slot, obtained by considering all combinations of the configured K1 value and the reference SLIV in all rows of the modified TDRA table. k,j, the set of (d, r) is determined.

[0187] Considering the configured TDD UL-DL configuration, for each determined DL slot, the occasion is determined by the set of pairs (d k,j , r). Here, the duplicate check can be performed considering the reference SLIVs within one or more slots of the set of pairs (d k,j , r).

[0188] In some embodiments, the maximum of B reference SLIVs in row r may be any maximum of B SLIVs in row r. Specifically, it may be the last min(B, L) SLIVs in row r. Alternatively, the maximum of B reference SLIVs in row r may be any maximum of B available SLIVs in row r. Specifically, it may be the last min(B, L A ) available SLIVs in row r.

[0189] FIG. 14 shows FIG. 1400 of a HARQ-ACK codebook based on reference start and length indicator values (SLIVs) according to some aspects. More specifically, FIG. 14 shows an example for generating an occasion using time bundles. It can be assumed that two values of K1, namely {2, 3}, are configured. Each bundle can be assumed to include HARQ-ACKs for up to 4 PDSCHs. The TDRA table consists of 4 rows. Column 0 is composed of a single SLIV, namely SLIV0. Column 1 is composed of 3 SLIVs, namely SLIV0 to 2. Column 2 is composed of 6 SLIVs, namely SLIV0 to 5. Column 3 is composed of 8 SLIVs, namely SLIV0 to 7.

[0190] In some aspects, a reference SLIV can be determined for each row in the TDRA table per bundle: Row 0 maps to one bundle and SLIV0 is used as the reference SLIV; Row 1 maps to one bundle and SLIV2 is used as the reference SLIV; Row 2 maps to two bundles and SLIV4 and 5 are used as the reference SLIVs for the two bundles, respectively; Row 3 maps to two bundles and SLIV6 and 7 are used as the reference SLIVs for the two bundles, respectively.

[0191] In some aspects, the TDRA table can be modified so that each row consists of only reference SLIVs. Row 0 contains only SLIV0. Row 1 contains only SLIV2. Row 2 contains SLIV4 and 5. Row 3 contains SLIV6 and 7.

[0192] In some aspects, the occasions in the Type 1 HARQ-ACK codebook can be assigned using a set of K1 values ​​{2,3} and a modified TDRA table by reusing the Rel-16 pseudocode. An exemplary exception is that the original SLIVs included in the bundle are used to check whether the associated reference SLIV is available for PDSCH transmission based on the configured TDD UL-DL configuration. For row 0, the availability of SLIV0 is checked. For row 1, the reference SLIV2 is available if at least one SLIV from SLIV0-2 in row 1 is available for PDSCH transmission. For row 2, the reference SLIV4 is available if at least one SLIV from SLIV0-1 in row 2 is available for PDSCH transmission, while the reference SLIV5 is available if at least one SLIV from SLIV2-5 in row 2 is available for PDSCH transmission. For row 3, criterion SLIV6 is available if at least one SLIV from SLIVs 0-3 in row 3 is available for PDSCH transmission, while criterion SLIV7 is available if at least one SLIV from SLIVs 4-7 in row 3 is available for PDSCH transmission. In some aspects, the number of occasions in a Type 1 HARQ-ACK codebook is at most three.

[0193] FIG. 15 illustrates a diagram 1500 of a HARQ-ACK codebook based on a reference SLIV, according to some aspects. More specifically, FIG. 15 illustrates another example for generating occasions in different ways for time bundles. This uses the same K1 value and TDRA table assumptions as FIG. 14. It can be assumed that at most two bundles are generated for each row. A reference SLIV can be determined for each bundle for each row in the TDRA table.

[0194] Row 0 maps to one bundle and SLIV0 is used as the reference SLIV. Row 1 maps to two bundles with one and two SLIVs respectively. SLIV1 and 2 are used as the reference SLIVs for the two bundles respectively. Row 2 maps to two bundles with three SLIVs. SLIV4 and 5 are used as the reference SLIVs for the two bundles respectively. Row 3 maps to two bundles with four SLIVs. SLIV6 and 7 are used as the reference SLIVs for the two bundles respectively.

[0195] In some aspects, the TDRA table can be modified such that each row consists of only reference SLIVs. Row 0 contains only SLIV0. Row 1 contains SLIV1 and 2. Row 2 contains SLIV4 and 5. Row 3 contains SLIV6 and 7.

[0196] In some aspects, occasions in the Type 1 HARQ-ACK codebook can be assigned using a set of K1 values ​​{2,3} and a modified TDRA table by reusing the Rel-16 pseudocode. An exemplary exception is that the original SLIV included in the bundle is used to check whether the associated reference SLIV is available for PDSCH transmission based on the configured TDD UL-DL configuration.

[0197] For row 0, the availability of SLIV0 is checked. For row 1, criterion SLIV1 is available if SLIV0 of row 1 is available for PDSCH transmission, while criterion SLIV2 is available if at least one SLIV from SLIV1-2 of row 1 is available for PDSCH transmission. For row 2, criterion SLIV4 is available if at least one SLIV from SLIV0-2 of row 2 is available for PDSCH transmission, while criterion SLIV5 is available if at least one SLIV from SLIV3-5 of row 2 is available for PDSCH transmission. For row 3, criterion SLIV6 is available if at least one SLIV from SLIV0-3 of row 3 is available for PDSCH transmission, while criterion SLIV7 is available if at least one SLIV from SLIV4-7 of row 3 is available for PDSCH transmission. In some aspects, the number of occasions in a Type 1 HARQ-ACK codebook is at most three.

[0198] In some embodiments, the above-mentioned at most B reference SLIVs for row r may be determined separately for each K1 value in the sequence. For example, they may be determined in descending order of K1 values. In some aspects, for the largest K1 value, the above-mentioned at most B reference SLIVs for row r may be the last min(B,L) SLIVs of row r. Alternatively, the last min(B,L) SLIVs of row r may be determined in descending order of K1 values. A ) available SLIVs.

[0199] In some embodiments, the K value K 1,k About K 1,k The set of slots containing the reference SLIVs associated with bundles for larger K1 values ​​is denoted as set R. First, for K1 values ​​K 1,k The above-mentioned maximum B reference SLIVs for row r may be determined from the SLIVs of row r in the slots of set R that include any SLIVs of row r corresponding to row r. If all reference SLIVs are not assigned, the remaining reference SLIVs are assigned a K1 value K 1,kAlternatively, the remaining reference SLIVs may be the last SLIV of row r corresponding to K1 value K 1,k It may be the last available SLIV of row r corresponding to

[0200] FIG. 16 illustrates a diagram 1600 of a HARQ-ACK codebook based on sequentially assigned reference SLIVs, according to some aspects. More specifically, FIG. 16 illustrates another example for generating occasions with time bundles using sequential determination of reference SLIVs. It can be assumed that two values ​​of K1 value, namely {1, 3}, are configured. It is assumed that each bundle includes HARQ-ACKs for up to four PDSCHs and the same TDRA table as in FIG. 14. A reference SLIV can be determined for each bundle for each row in the TDRA table.

[0201] For K1=3, the criterion SLIV of the four rows is the same as that in FIG.

[0202] For K1=1, (a) Row 0 does not overlap with any slots that already have a reference SLIV assigned, therefore SLIV0 is used as the reference SLIV.

[0203] (b) Row 1 overlaps with slot n-3 and contains an assigned reference SLIV, therefore SLIV0 in row 1 is used as the reference SLIV.

[0204] (c) Row 2 overlaps with slots n-4 and n-3 which contain assigned reference SLIVs, and therefore SLIVs 2 and 3 in row 2 are used as the reference SLIVs for the two bundles, respectively.

[0205] (d) Row 3 overlaps with slots n-4 and n-3 which contain assigned reference SLIVs, and therefore SLIVs 4 and 5 in row 3 are used as the reference SLIVs for the two bundles, respectively.

[0206] In some aspects, the TDRA table can be modified such that each row consists of only reference SLIVs: Row 0 contains only SLIV0. Row 1 contains only SLIV0. Row 2 contains SLIV2 and 3. Row 3 contains SLIV4 and 5.

[0207] In some aspects, the occasions in the Type 1 HARQ-ACK codebook can be allocated using a set of K1 values ​​{1,3} and a modified TDRA table by reusing the Rel-16 pseudocode. The only exception is that the original SLIVs included in the bundle are used to check whether the associated reference SLIV is available for PDSCH transmission based on the configured TDD UL-DL configuration. The case of K1=3 is the same as in FIG. 14.

[0208] In some aspects, the occasions in the Type 1 HARQ-ACK codebook can be assigned using a set of K1 values ​​{1,3} and a modified TDRA table by reusing the Rel-16 pseudocode. The only exception is that the original SLIVs included in the bundle are used to check whether the associated reference SLIVs are available for PDSCH transmission based on the configured TDD UL-DL configuration. Same as in Figure 14 for K1=3.

[0209] For K1=1, (a) For row 0, check the availability of SLIV0.

[0210] (b) For row 1, reference SLIV0 is available if at least one SLIV from SLIV0-2 in row 1 is available for PDSCH transmission.

[0211] (c) For row 2, reference SLIV2 is available if at least one SLIV from SLIV0-1 in row 2 is available for PDSCH transmission, while reference SLIV3 is available if at least one SLIV from SLIV2-5 in row 2 is available for PDSCH transmission.

[0212] (d) For row 3, reference SLIV4 is available if at least one SLIV from SLIV0 to 3 in row 3 is available for PDSCH transmission, while reference SLIV5 is available if at least one SLIV from SLIV4 to 7 in row 3 is available for PDSCH transmission.

[0213] In some aspects, the number of occasions in a Type 1 HARQ-ACK codebook is at most 3. If the occasions are generated according to FIG. 14, it may include up to 4 occasions.

[0214] In some embodiments, the disclosed techniques include wireless communication systems and methods for HARQ-ACK transmissions when one or more TTIs are scheduled by downlink control information (DCI). In some aspects, the DCI is decoded by the UE from a physical downlink control channel (PDCCH). One or more physical downlink shared channels (PDSCHs) scheduled by the DCI are decoded by the UE. In some aspects, the UE transmits a HARQ-ACK codebook carrying bundled HARQ-ACK information for PDSCH transmissions scheduled by the DCI.

[0215] In some embodiments, an occasion is first assigned for each slot in the set of determined DL slots, and then the multiple occasions are bundled to generate a bundled occasion. In some embodiments, occasions in a bundle of N consecutive DL slots are bundled into one bundled occasion. In some aspects, occasions in a bundle of N determined DL slots are bundled into one bundled occasion. In some embodiments, occasions in a bundle of N determined DL slots having an assigned occasion are bundled into one bundled occasion. In some embodiments, each bundle of N consecutive occasions is bundled into one bundled occasion. In some aspects, the PDSCH corresponding to the bundled occasion is scheduled by a single DCI.

[0216] In some embodiments, the last PDSCH of a PDSCH transmission schedulable by a DCI ends no earlier than the start of the first PDSCH of another PDSCH transmission schedulable by another DCI if the last PDSCH and the first PDSCH correspond to the same bundle of slots or occasions. In some aspects, a bundle corresponds to up to N consecutive DL slots. In some aspects, a bundle corresponds to up to N determined DL slots. In some aspects, a bundle corresponds to up to N determined DL slots with assigned occasions.

[0217] In some embodiments, a set of SLIVs of row r in the TDRA table is divided into one or more bundles, each bundle being associated with a SLIV of row r, and occasions for candidate PDSCH reception are assigned by a set of K1 values ​​and the modified TDRA table, and each row r includes only reference SLIVs. In some aspects, the reference SLIV for a bundle of row r is an element of row r. In some aspects, a reference SLIV is considered available for PDSCH transmission if at least one SLIV in the bundle of SLIVs associated with the reference SLIV is available for PDSCH transmission. In some aspects, the above set of SLIVs of row r is a set of configured SLIVs of row r by higher layer signaling. In some aspects, the above set of SLIVs of row r includes only available SLIVs of row r if the SLIVs do not overlap with UL symbols according to the configured TDD UL-DL configuration. In some aspects, the reference SLIV of row r is the last SLIV of row r.

[0218] In some embodiments, the K value K 1,k About K 1,k The set of slots containing the reference SLIVs associated with bundles for larger K1 values ​​is denoted as set R. First, for K1 values ​​K 1,k The reference SLIV for row r is determined from the SLIVs for row r in the slots of set R that contain any SLIV for row r corresponding to 1,k is the last SLIV of row r corresponding to

[0219] 17 illustrates a block diagram of a communications device such as an evolved Node-B (eNB), new generation Node-B (gNB) (or another RAN node or base station), transmission / reception point (TRP), access point (AP), wireless station (STA), mobile station (MS), or user equipment (UE), according to some aspects. In alternative aspects, communications device 1700 may operate as a standalone device or may be connected (e.g., networked) to other communications devices.

[0220] A circuit (e.g., processing circuit) is a collection of circuits implemented in a tangible entity of device 1700 that includes hardware (e.g., simple circuits, gates, logic, etc.). The membership of a circuit may be flexible over time. A circuit includes elements that, when operational, may perform specified operations, either alone or in combination. In one example, the hardware of a circuit may be invariably designed (e.g., hardwired) to perform a particular operation. In one example, the hardware of a circuit may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) that include a machine-readable medium that is physically modified (e.g., magnetically, electrically, a movable arrangement of invariant assembled particles, etc.) to encode instructions for a particular operation.

[0221] In connecting the physical components, the underlying electrical properties of the hardware components are changed, for example, from an insulator to a conductor or vice versa. The instructions enable the embedded hardware (e.g., an execution unit or a loading mechanism) to create members of a circuit within the hardware through the variable connections to perform some of the specific operations during operation. Thus, in one example, the machine-readable media element is part of a circuit or is communicatively coupled to other components of a circuit when the device is operating. In one example, any of the physical components may be used in more than one member of more than one circuit. For example, during operation, an execution unit may be used in a first circuit of a first circuit at one time and reused by a second circuit of the first circuit or by a third circuit of the second circuit at a different time. Further examples of these components with respect to device 1700 follow below.

[0222] In some aspects, the device 1700 may operate as a standalone device or may be connected (e.g., networked) to other devices. In a networked deployment, the communications device 1700 may operate in the capacity of a server communications device, a client communications device, or both in a server-client type network environment. In one example, the communications device 1700 may operate as a peer communications device in a peer-to-peer (P2P) (or other distributed) network environment. The communications device 1700 may be a UE, eNB, PC, tablet PC, STB, PDA, mobile phone, smartphone, web appliance, network router, switch or bridge, or any communications device capable of executing instructions (sequential or other) that specify actions to be taken by the communications device. Additionally, although only a single communications device is shown, the term "communications device" shall also be construed to include any collection of communications devices that individually or collectively execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), or other computer cluster configurations.

[0223] The examples described herein may include or operate on logic or multiple components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) that can perform a specified operation and may be configured or arranged in a particular manner. In one example, a circuit may be arranged (e.g., internally or with respect to an external entity such as another circuit) as a module in a specified manner. In one example, one or more computer systems (e.g., stand-alone, client, or server computer systems) or one or more hardware processors may be configured in whole or in part with firmware or software (e.g., instructions, application portions, or applications) as modules that operate to perform specified operations. In one example, the software may reside on a communication device readable medium. In one example, the software, when executed by the hardware underlying the module, causes the hardware to perform the specified operations.

[0224] The term "module" is therefore understood to encompass a tangible entity that is physically constructed, specifically configured (e.g., wired), or temporarily (e.g., transiently) configured (e.g., programmed) to operate in a specified manner or to perform some or all of any of the operations described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one time. For example, if the modules include a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as different modules at different times. Thus, the software may configure the hardware processor, for example, to configure a particular module at one time and a different module at a different time.

[0225] A communications device (e.g., a UE) 1700 may include a hardware processor 1702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1704, a static memory 1706, and a storage device 1707 (e.g., a hard drive, a tape drive, flash storage, or other block or storage device), some or all of which may communicate with each other via an interlink (e.g., a bus) 1708.

[0226] The communication device 1700 may further include a display device 1710, an alphanumeric input device 1712 (e.g., a keyboard), and a user interface (UI) navigation device 1714 (e.g., a mouse). In one example, the display device 1710, the input device 1712, and the UI navigation device 1714 may be touch screen displays. The communication device 1700 may further include a signal generating device 1718 (e.g., a speaker), a network interface device 1720, and one or more sensors 1721, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. Communications device 1700 may include an output controller 1728, such as a serial (e.g., universal serial bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection, to communicate with or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0227] The storage device 1707 may include a communication device readable medium 1722 on which one or more sets of data structures or instructions 1724 (e.g., software) are stored that embody or are utilized by any one or more of the techniques or functions described herein. In some aspects, the registers, main memory 1704, static memory 1706, and / or storage device 1707 of the processor 1702 may be, or may include (completely or at least partially) the device readable medium 1722 on which one or more sets of data structures or instructions 1724 are stored that embody or are utilized by any one or more of the techniques or functions described herein. In one example, one or any combination of the hardware processor 1702, main memory 1704, static memory 1706, or storage device 1707 may constitute the device readable medium 1722.

[0228] The term "device readable medium" as used herein is interchangeable with "computer readable medium" or "machine readable medium." Although the communication device readable medium 1722 is depicted as a single medium, the term "communication device readable medium" may include a single medium or multiple media (e.g., centralized or distributed databases and / or associated caches and servers) configured to store one or more instructions 1724. The term "communication device readable medium" may include any medium that can store, encode, or carry instructions (e.g., instructions 1724) for execution by the communication device 1700 and cause the communication device 1700 to perform any one or more of the techniques of this disclosure, or any medium that can store, encode, or carry data structures used by or associated with such instructions. Non-limiting examples of communication device readable media may include solid-state memory, optical and magnetic media. Specific examples of communication device readable media may include non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices, magnetic disks such as internal hard disks and removable disks, magneto-optical disks, Random Access Memory (RAM), and CD-ROM and DVD-ROM disks. In some examples, the communication device readable medium may include a non-transitory communication device readable medium. In some examples, the communication device readable medium may include a communication device readable medium that is not a transitory propagating signal.

[0229] Additionally, the instructions 1724 may be transmitted or received over a communications network 1726 using a transmission medium via the network interface device 1720 utilizing any one of a number of transport protocols. In one example, the network interface device 1720 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas for connecting to the communications network 1726. In one example, the network interface device 1720 may include multiple antennas for communicating wirelessly using at least one single-input-multiple-output (SIMO), MIMO, or multiple-input-single-output (MISO) technology.

[0230] The term "transmission medium" shall be construed as including any intangible medium capable of storing, encoding or carrying instructions for execution by communication device 1700, including digital or analog communication signals or other intangible media for facilitating the communication of such software. In this regard, transmission media in the context of this disclosure are device-readable media.

[0231] The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure. These terms are defined to include both mechanical storage media and transmission media. Thus, these terms include both storage devices / media and carrier waves / modulated data signals.

[0232] Implementations of the described subject matter can include one or more of the features, either alone or in combination, such as, by way of example, the following:

[0233] Example 1 is an apparatus for a user equipment (UE) configured for operation in a fifth generation new radio (5G NR) and beyond wireless network, the apparatus comprising: To configure a UE for cross-carrier scheduling of data transmissions in NR and beyond wireless networks, the UE includes a processing circuit that decodes configuration signaling received from a base station indicating a first numerology parameter for a scheduling cell of the base station and a second numerology parameter for a scheduled cell of the base station, schedules a downlink (DL) data transmission in the scheduled cell of the base station, decodes downlink control information (DCI) received via a physical downlink control channel (PDCCH) of the scheduling cell, decodes a DL data transmission received via a physical downlink shared channel (PDSCH) of the scheduled cell if a difference between the first numerology parameter and the second numerology parameter is less than or equal to a preconfigured numerology threshold, and refrains from decoding the DL data transmission if a difference between the first numerology parameter and the second numerology parameter is greater than the preconfigured numerology threshold, and a memory coupled to the processing circuit and configured to store the configuration signaling.

[0234] In Example 2, the subject matter of Example 1 includes the DCI scheduling an uplink (UL) data transmission in a scheduled cell of the base station, and the processing circuitry configured to encode the UL data for the UL data transmission via a physical uplink shared channel (PUSCH) of the scheduled cell if a difference between the first numerology parameter and the second numerology parameter is less than or equal to a preconfigured numerology threshold.

[0235] In Example 3, the subject matter of Example 2 includes the processing circuitry being configured to refrain from encoding the UL data for the UL data transmission if a difference between the first numerology parameter and the second numerology parameter is greater than a preconfigured numerology threshold.

[0236] In Example 4, the subject matter of Examples 1 to 3 is The first numerology parameter is μ DCI and the second numerology parameter is μ DATA and the preconfigured numerology threshold is d max This includes being.

[0237] In Example 5, the subject matter of Example 4 is further characterized in that the processing circuitry is DCI -μ DATA |≦d max and configured to decode DL data transmission if a first subcarrier spacing (SCS) of an active bandwidth portion (BWP) used for transmission of DCI in the scheduling cell is 2 μDCI 15 kHz and the second SCS of the active BWP used for receiving DL data transmission in the scheduled cell is 2 μDATA Including being 15kHz.

[0238] In Example 6, the subject of Examples 4-5 is that the configuration signaling is |μ DCI -μ DATA |>d max If so, activating a bandwidth portion (BWP) on the scheduled cell.

[0239] In Example 7, the subject matter of Example 6 further comprises: a processing circuit for decoding the DCI to determine whether the BWP on the scheduled cell is |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1 determining a BWP indicator field indicating that the scheduled cell has a BWP indicator field indicating a DL data transmission; refraining from modifying the BWP on the scheduled cell; and utilizing the BWP for receiving DL data transmissions.

[0240] In Example 8, the subject matter of Examples 6-7 is further characterized in that the processing circuitry decodes the DCI to determine whether the BWP on the scheduled cell is |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1Determine a BWP indicator field that indicates that |μ DCI -μ DATA,2 |≦d max Numerology μ that satisfies DATA,2 and utilizing the second BWP for receiving DL data transmissions.

[0241] In Example 9, the subject matter of Examples 1-8 includes the DCI scheduling multiple PDSCH transmissions of the DL data, and the processing circuitry encoding a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) codebook for transmission to the base station, the HARQ-ACK codebook including bundled HARQ-ACK information for the multiple PDSCH transmissions.

[0242] In Example 10, the subject matter of Examples 1-9 includes a transceiver circuit coupled to the processing circuit and two or more antennas coupled to the transceiver circuit.

[0243] Example 11 is a computer-readable storage medium having stored thereon instructions for execution by one or more processors of a user equipment (UE), the instructions causing the UE to perform operations including configuring the UE for cross-carrier scheduling of data transmissions in fifth generation new radio (5G NR) and beyond wireless networks, decoding configuration signaling received from a base station indicating a first numerology parameter for a scheduling cell of the base station and a second numerology parameter for a scheduled cell of the base station, scheduling a downlink (DL) data transmission in the scheduled cell of the base station, decoding downlink control information (DCI) received via a physical downlink control channel (PDCCH) of the scheduling cell, if a difference between the first numerology parameter and the second numerology parameter is less than or equal to a preconfigured numerology threshold, decoding a DL data transmission received via a physical downlink shared channel (PDSCH) of the scheduled cell, if a difference between the first numerology parameter and the second numerology parameter is less than or equal to a preconfigured numerology threshold, and refraining from decoding the DL data transmission if the difference between the first numerology parameter and the second numerology parameter is greater than the preconfigured numerology threshold.

[0244] In Example 12, the subject matter of Example 11 includes the DCI scheduling an uplink (UL) data transmission in a scheduled cell of the base station, and the instructions further including encoding UL data for UL data transmission via a physical uplink shared channel (PUSCH) of the scheduled cell if a difference between the first numerology parameter and the second numerology parameter is less than or equal to a preconfigured numerology threshold.

[0245] In Example 13, the subject matter of Example 12 includes the operations further including refraining from encoding the UL data for the UL data transmission if a difference between the first numerology parameter and the second numerology parameter is greater than a preconfigured numerology threshold.

[0246] In Example 14, the subject matter of Examples 11-13 is further characterized in that the first numerology parameter is μ DCI and the second numerology parameter is μ DATA and the preconfigured numerology threshold is d max This includes being.

[0247] In Example 15, the subject of Example 14 is that the action is |μ DCI -μ DATA |≦d max and decoding the DL data transmission if a first subcarrier spacing (SCS) of an active bandwidth portion (BWP) used for transmission of the DCI in the scheduling cell is 2 μDCI 15 kHz and the second SCS of the active BWP used for receiving DL data transmission in the scheduled cell is 2 μDATA Including being 15kHz.

[0248] In Example 16, the subject matter of Examples 14-15 is further characterized in that the configuration signaling is |μ DCI -μ DATA |>d max If so, activating a bandwidth portion (BWP) on the scheduled cell.

[0249] In Example 17, the subject matter of Example 16 further comprises: an operation for decoding the DCI and determining whether the BWP on the scheduled cell is |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1 determining a BWP indicator field indicating that the scheduled cell has a BWP indicator field indicating a DL data transmission; refraining from modifying the BWP on the scheduled cell; and utilizing the BWP for receiving DL data transmission.

[0250] In Example 18, the subject matter of Examples 16-17 further comprises: an operation for decoding the DCI and determining whether the BWP on the scheduled cell is |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1Determine a BWP indicator field that indicates that |μ DCI -μ DATA,2 |≦d max Numerology μ that satisfies DATA,2 and utilizing the second BWP for receiving DL data transmission.

[0251] Example 19 is a computer-readable storage medium having stored thereon instructions for execution by one or more processors of a base station, the instructions causing the base station to perform operations including configuring the base station for cross-carrier scheduling of data transmissions in fifth generation new radio (5G NR) and beyond wireless networks, encoding configuration signaling for transmission to a user equipment (UE) indicating a first numerology parameter for a scheduling cell of the base station and a second numerology parameter for a scheduled cell of the base station, scheduling downlink (DL) data transmissions in the scheduled cell of the base station, encoding downlink control information (DCI) for transmission via a physical downlink control channel (PDCCH) of the scheduling cell, and encoding DL data for DL ​​data transmission via a physical downlink shared channel (PDSCH) of the scheduled cell if a difference between the first numerology parameter and the second numerology parameter is less than or equal to a preconfigured numerology threshold.

[0252] In Example 20, the subject matter of Example 19 includes the DCI scheduling multiple PDSCH transmissions of the DL data, and the operations further including decoding a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) codebook received from the UE, the HARQ-ACK codebook including bundled HARQ-ACK information for the multiple PDSCH transmissions.

[0253] Example 21 is at least one machine-readable medium containing instructions that, when executed by a processing circuit, cause the processing circuit to perform operations to implement any of Examples 1-20.

[0254] Example 22 is an apparatus including means for carrying out any of Examples 1 to 20.

[0255] Example 23 is a system for carrying out any one of Examples 1 to 20.

[0256] Example 24 is a method for carrying out any of Examples 1-20.

[0257] Although the embodiments have been described with reference to certain exemplary embodiments, it will be apparent that various modifications and changes may be made thereto without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative and not a restrictive sense. Thus, this detailed description is not to be construed in a limiting sense, and the scope of the various embodiments is defined solely by the appended claims, along with the full scope of equivalents to which such claims are entitled.

Claims

1. An apparatus for user equipment (UE) configured for operation in a fifth generation new radio (5G NR) network, comprising: To configure the UE to report control information in the 5G NR network, Decoding a downlink control information (DCI) format received from a base station on a physical downlink control channel (PDCCH), where the DCI format schedules a physical downlink shared channel (PDSCH) and includes resource allocation of consecutive physical resource blocks (PRBs), the DCI format further indicating a PRB size indicator for a PRB bundle; Decoding downlink data received from the base station on the successive PRBs; a processing circuit for encoding a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) for transmission to the base station on a Physical Uplink Control Channel (PUCCH), where a payload size of the HARQ-ACK is based on the number of consecutive PRBs corresponding to the PRB bundle; a memory coupled to the processing circuit and configured to store the DCI format; An apparatus comprising:

2. The device described in claim 1, wherein the number of consecutive PRBs corresponds to the number of start and length indicator values ​​(SLIVs) of a row in a time domain resource allocation (TDRA) table.

3. The processing circuit, Decoding configuration signaling received from a base station, where the configuration signaling indicates a first numerology parameter for a scheduling cell of the base station and a second numerology parameter for a scheduled cell of the base station, and a DCI for scheduling the PDSCH in the scheduled cell of the base station; If a difference between the first numerology parameter and the second numerology parameter is less than or equal to a preconfigured numerology threshold, decoding a downlink (DL) data transmission received via the PDSCH of the scheduled cell; 2. The apparatus of claim 1, further comprising: a step of: refraining from decoding the DL data transmission if the difference between the first numerology parameter and the second numerology parameter is greater than the preconfigured numerology threshold.

4. The DCI schedules uplink (UL) data transmissions in the scheduled cell of the base station, and the processing circuitry 4. The apparatus of claim 3, configured to encode UL data for the UL data transmission via a Physical Uplink Shared Channel (PUSCH) of the scheduled cell if the difference between the first numerology parameter and the second numerology parameter is less than or equal to the preconfigured numerology threshold.

5. The processing circuitry includes:

5. The apparatus of claim 4, configured to refrain from encoding the UL data for the UL data transmission if the difference between the first numerology parameter and the second numerology parameter is greater than the preconfigured numerology threshold.

6. The first numerology parameter is μ DCI and the second numerology parameter is μ DATA and the preconfigured numerology threshold is d max The apparatus of claim 3 .

7. The processing circuitry is DCI -μ DATA |≦d max and configured to decode the DL data transmission if a first subcarrier spacing (SCS) of an active bandwidth portion (BWP) used for transmission of the DCI in the scheduling cell is 2 μDCI 15 kHz and the second SCS of the active BWP used for receiving the DL data transmission in the scheduled cell is 2 μDATA 15 kHz.

8. The configuration signaling is |μ DCI -μ DATA |>d max 7. The apparatus of claim 6, further comprising: activating a bandwidth portion (BWP) on the scheduled cell if .

9. The processing circuit decodes the DCI and determines whether the BWP on the scheduled cell is |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1 9. The apparatus of claim 8, further comprising: determining a BWP indicator field indicating that the scheduled cell has a BWP indicator field indicating ...

10. The processing circuitry includes: The DCI is decoded, and the BWP on the scheduled cell is |μ DCI -μ DATA,1 |>d max The result is numerology μ DATA,1 determining a BWP indicator field indicating |μ DCI -μ DATA,2 |≦d max Numerology μ that satisfies DATA,2 and switching to a second BWP on the scheduled cell having The apparatus of claim 8 , further comprising: a second BWP for receiving the DL data transmission.

11. The DCI schedules a plurality of PDSCH transmissions of DL data, and the processing circuitry 4. The apparatus of claim 3, further comprising: encoding a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) codebook for transmission to the base station, the HARQ-ACK codebook including bundled HARQ-ACK information for the multiple PDSCH transmissions.

12. a transceiver circuit coupled to the processing circuit; two or more antennas coupled to the transceiver circuitry; The apparatus of claim 1 further comprising:

13. A computer program comprising instructions for execution by one or more processors of a user equipment (UE), comprising: The instructions configure the UE to report control information in a New Radio (NR) network, and for the UE: encoding a downlink control information (DCI) format for transmission to a user equipment (UE) on a physical downlink control channel (PDCCH), where the DCI format schedules a physical downlink shared channel (PDSCH) and includes resource allocation of consecutive physical resource blocks (PRBs), the DCI format further indicating a PRB size indicator for a PRB bundle; encoding downlink data for transmission to the UE on the successive PRBs; Decode a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) received from the UE on a Physical Uplink Control Channel (PUCCH), where a payload size of the HARQ-ACK is based on the number of the consecutive PRBs corresponding to the PRB bundle. A computer program that causes a computer to perform operations including:

14. The computer program product of claim 13, wherein the number of consecutive PRBs corresponds to a number of start and length indicator values ​​(SLIVs) of rows in a time domain resource allocation (TDRA) table.

15. A user equipment (UE) configured to operate in a New Radio (NR) network, comprising: a front-end circuit coupled to one or more antennas; a processing circuit coupled to the front-end circuit; Including, The processing circuitry includes: Decoding a downlink control information (DCI) format received from a base station on a physical downlink control channel (PDCCH), where the DCI format schedules a physical downlink shared channel (PDSCH) and includes resource allocation of consecutive physical resource blocks (PRBs), the DCI format further indicating a PRB size indicator for a PRB bundle; Decoding downlink data received from the base station on the successive PRBs; a UE encoding a hybrid automatic repeat request acknowledgement (HARQ-ACK) for transmission to the base station on a physical uplink control channel (PUCCH), where a payload size of the HARQ-ACK is based on the number of consecutive PRBs corresponding to the PRB bundle.

16. The UE of claim 15, wherein the number of consecutive PRBs corresponds to the number of start and length indicator values ​​(SLIVs) of a row in a time domain resource allocation (TDRA) table.

17. The processing circuitry comprises: Decoding configuration signaling received from a base station, where the configuration signaling indicates a first numerology parameter for a scheduling cell of the base station and a second numerology parameter for a scheduled cell of the base station, and the DCI indicates scheduling of the PDSCH in the scheduled cell of the base station; If a difference between the first numerology parameter and the second numerology parameter is less than or equal to a preconfigured numerology threshold, decoding a downlink (DL) data transmission received via the PDSCH of the scheduled cell; 16. The UE of claim 15, wherein the UE refrains from decoding the DL data transmission if the difference between the first numerology parameter and the second numerology parameter is greater than the preconfigured numerology threshold.

18. The UE of claim 17, wherein the DCI schedules uplink (UL) data transmission in the scheduled cell of the base station, and the processing circuit is configured to encode UL data for the UL data transmission via a physical uplink shared channel (PUSCH) of the scheduled cell when the difference between the first numerology parameter and the second numerology parameter is less than or equal to the preconfigured numerology threshold.

19. The UE of claim 18, wherein the processing circuitry is configured to refrain from encoding the UL data for the UL data transmission if the difference between the first numerology parameter and the second numerology parameter is greater than the preconfigured numerology threshold.

20. The UE of claim 17, wherein the first numerology parameter is μ DCI , the second numerology parameter is μ DATA , and the preconfigured numerology threshold is d max .

21. A non-transitory computer-readable storage medium storing a computer program according to claim 13 or 14.

Images