Configuration of multiplexed carrier repetitive transmission

Abstract

A computer-readable storage medium stores instructions for configuring a UE for multiple component carrier repetition transmission in a 5G NR network and causing the UE to perform operations including decoding DCI received via a PDCCH. The DCI includes transport block (TB) information and scheduling information. The scheduling information indicates a scheduled transmission of multiple repetitions of a PDSCH TB using multiple component carriers. A TB size associated with the scheduled transmission is determined using the TB information. The multiple repetitions of the PDSCH TB are decoded. The multiple repetitions are received from one or more base stations during the scheduled transmission. PDSCH data is determined based on the multiple repetitions of the PDSCH TB and the TB size.

Description

Technical Field

[0001] The present invention relates to wireless communication. Some aspects relate to fifth-generation (5G) networks and later, including 3GPP (Registered Trademark) (Third Generation Partnership Project) networks, 3GPP (Registered Trademark) LTE (Long Term Evolution) networks, 3GPP (Registered Trademark) LTE-A (LTE Advanced) networks, (Multifire, LTE-U), and 5G New Radio (NR) (or 5G-NR) networks, such as 5G-LTE networks (5G NR Unlicensed Spectrum (NR-U) networks, and other unlicensed networks including Wi-Fi (Registered Trademark), CBRS (OnGo), etc.). Other aspects are directed to techniques for configuring repeated transmission of multiple component carriers in 5G-NR (and later) networks.

Background Art

[0002] (Priority Claim) This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 155,679, filed on March 2, 2021, entitled "Method for Repeated Transmission of Multiple Component Carriers", which is hereby incorporated by reference in its entirety.

[0003] [[ID=]] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated integrated communication platforms. The increasing number of different types of devices communicating with various network devices has led to increased use of 3GPP® LTE systems. The penetration of mobile devices (user equipment or UE) in modern society continues to drive the demand for diverse network devices in many different environments. The emergence of fifth-generation (5G) wireless systems promises even greater speed, connectivity, and operability. Next-generation 5G networks (or NR networks) are expected to improve throughput, coverage, and robustness, while reducing latency, operational costs, and capital expenditures. 5G-NR networks continue to evolve, incorporating the potential of new radio access technologies (RATs) in addition to 3GPP® LTE-Advanced, to enrich people's lives with seamless wireless connectivity solutions that deliver high-speed, rich content and services. Because current cellular network frequencies are saturated, higher frequencies such as millimeter-wave (mmWave) frequencies are beneficial due to their higher bandwidth.

[0004] 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. According to this, LTE-based technologies that operate solely in unlicensed spectrum without requiring a "anchor" in licensed spectrum are referred to as MultiFire. Further enhanced operation of LTE and NR systems in licensed spectrum as well as unlicensed spectrum is expected in future releases and 5G (and beyond) systems. Such enhanced operation includes technologies that configure multiple component carrier repetition transmissions in 5G-NR (and beyond) networks. [Brief explanation of the drawing]

[0005] The figures are not necessarily drawn to scale, and may represent similar components in different views, as do the numbers. They may also represent different instances of the same component, as do the numbers with different letter suffixes. These figures are general examples, not limitations, of the various aspects discussed herein.

[0006] [Figure 1A] The network architecture is shown according to several aspects. [Figure 1B] The architecture of a non-roaming 5G system is shown according to several aspects. [Figure 1C] The architecture of a non-roaming 5G system is shown according to several aspects. [Figure 2] This document shows various systems, devices, and components that can implement aspects of the disclosed embodiments. [Figure 3] This document shows various systems, devices, and components that can implement aspects of the disclosed embodiments. [Figure 4] This document shows various systems, devices, and components that can implement aspects of the disclosed embodiments. [Figure 5] This describes physical downlink scaded channel (PDSCH) transmission with repetition in time and frequency from multiple transmit / receive points (TRPs) according to several aspects. [Figure 6] This is a diagram of a multiple component carrier (multi-CC) PDSCH iteration based on single downlink control information (single DCI), according to several aspects. [Figure 7] This diagram shows a multi-CC PDSCH iteration based on multiple downlink control information (multi-DCI) according to several aspects. [Figure 8] This is a diagram of a hybrid automated repetitive request (HARQ) reporting group for multi-CC PDSCH repetition, according to several aspects. [Figure 9] This illustrates push / puch transmission with carrier switching according to several aspects. [Figure 10] According to several aspects, we will show PDCCH / PDSCH / PUSCH / PUCCH repetitions with multi-CC repetitions and multi-TRP transmissions. [Figure 11] Block diagrams of communication equipment such as evolved Node-B (eNB), next-generation Node-B (gNB) (or other RAN nodes or base stations), transmit / receive points (TRP), access points (AP), radio stations (STA), mobile stations (MS), or user equipment (UE) are shown according to several aspects. [Modes for carrying out the invention]

[0007] The following description and drawings fully illustrate embodiments that enable those skilled in the art to carry them out. Other embodiments may include structural, logical, electrical, process, and other modifications. Parts and features of one embodiment may be included in or replaced by parts of other embodiments. The embodiments outlined in the claims encompass all available equivalents of these claims.

[0008] Figure 1A shows a network architecture in several embodiments. Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and 102 are shown as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or other computing devices including wired and / or wireless communication interfaces. UE 101 and 102 may be collectively referred to as UE 101 herein, and UE 101 can be used to perform one or more of the technologies disclosed herein.

[0009] Any of the wireless links described herein (for example, as used in network 140A or other illustrated networks) may operate in accordance with any exemplary wireless communication technology and / or standard.

[0010] LTE and LTE-Advanced are standards for high-speed data wireless communication for UEs such as cellular devices. Carrier aggregation is a technique in LTE-Advanced and various wireless systems that uses multiple carrier signals operating on different frequencies to communicate for a single UE, increasing the bandwidth available to a single device. In some aspects, carrier aggregation is used when one or more component carriers are operating on unlicensed frequencies. The aspects described herein can be used in the context of any spectrum management scheme, including, for example, dedicated licensed spectra, unlicensed spectra, and (licensed) shared spectra (such as Licensed Shared Access (LSAs) for frequencies 2.3–2.4 GHz, 3.4–3.6 GHz, 3.6–3.8 GHz and above, and Spectrum Access Systems (SAS) for frequencies 3.55–3.7 GHz and above).

[0011] The aspects described herein can also be applied to different single-carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank-Based Multicarrier (FBMC), OFDM, etc.), particularly 3GPP® NR (New Radio), by assigning OFDM carrier data bit vectors to corresponding symbolic resources.

[0012] In some respects, both UE101 and UE102 can include Internet of Things (IoT) UEs or Cellular IoT (CIoT) UEs, which can include a network access layer designed for low-power IoT applications that leverage short-term UE connectivity. In some respects, both UE101 and UE102 can include Narrowband (NB) IoT UEs (e.g., Enhanced NB-IoT (eNB-IoT) UEs and Further Enhanced (FeNB-IoT) UEs). IoT UEs can leverage technologies such as Public Land Mobile Networks (PLMN), Proximity Communication-Based Services (ProSe), or Device-to-Device (D2D) communication, sensor networks, or Machine-to-Machine (M2M) or Machine-Type Communication (MTC) to exchange data with MTC servers or devices over IoT networks. M2M or MTC data exchange may be machine-initiated data exchange. IoT networks involve interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), over short-term connectivity. IoT UE may run background applications (such as keep-alive messages and status updates) to facilitate connectivity within the IoT network.

[0013] In some respects, both UE101 and UE102 can include an extended MTC (eMTC) UE or a further extended MTC (FeMTC) UE.

[0014] UEs 101 and 102 can be configured to communicatively couple with, for example, a Radio Access Network (RAN) 110. The RAN 110 can be, for example, a Universal Mobile Telecommunications System (UMTS), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or other types of RANs. UEs 101 and 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in more detail below). In this example, connections 103 and 104 are illustrated as air interfaces enabling communication coupling and can be compatible with cellular communication protocols such as Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Push-to-Talk over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP (registered trademark) Long Term Evolution (LTE) protocol, Fifth Generation (5G) protocol, New Radio (NR) protocol, etc.

[0015] In one aspect, UEs 101 and 102 can further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 is also 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).

[0016] UE102 is configured to access access point (AP) 106 via connection 107. Connection 107 can include a local wireless connection, such as a connection compatible with any IEEE 802.11 protocol, and accordingly, AP106 can include a Wireless Fidelity (WiFi®) router. In this example, AP106 is shown to be connected to the internet without being connected to the core network of the wireless system (more details below).

[0017] RAN110 may include one or more access nodes that enable connections 103 and 104. These access nodes (ANs) may be called base stations (BS), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN network nodes, etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some embodiments, communication nodes 111 and 112 may be transmit / receive points (TRPs). If 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. RAN110 may include one or more RAN nodes to provide macrocells, e.g., macroRAN node 111, and one or more RAN nodes to provide femtocells or picocells (e.g., cells with smaller coverage areas, smaller user capacity, or larger bandwidth compared to macrocells), e.g., low-power (LP) RAN node 112 or unlicensed spectrum-based secondary RAN node 112.

[0018] Either of RAN nodes 111 and 112 can terminate the air interface protocol and can be the first contact points for UEs 101 and 102. In some aspects, either of RAN nodes 111 and 112 can perform various logical functions for RAN 110, including, but not limited to, radio bearer management, uplink and downlink dynamic radio resource management, and radio network controller (RNC) functions such as data packet scheduling and mobility management. In one example, either of nodes 111 and / or 112 can be a next generation node B (gNB), an evolved node B (eNB), or other types of RAN nodes.

[0019] RAN 110 is shown communicatively coupled to core network (CN) 120 via S1 interface 113. In an aspect, CN 120 can be an evolved packet core (EPC) network, a NextGen packet core (NPC) network, or other types of CN (e.g., as illustrated by reference to FIGS. 1B-1C). In this aspect, S1 interface 113 is split into two parts: an S1-U interface 114 that transmits user traffic data between RAN nodes 111 and 112 and service gateway (S-GW) 122, and an S1 mobility management entity (MME) interface 115 that is a signaling interface between RAN nodes 111 and 112 and MME 121.

[0020] In this embodiment, CN120 includes MME121, S-GW122, Packet Data Network (PDN) Gateway (P-GW)123, and Home Subscriber Server (HSS)124. The MME121 is functionally similar to the control plane of a conventional General Packet Radio Service (GPRS) Support Node (SGSN). The MME121 can manage mobility aspects of access, such as gateway selection and tracking area list management. The HSS124 can configure a database for network users, including subscriber-related information to support the processing of communication sessions of network entities. Depending on the number of mobile subscribers, equipment capacity, network organization, etc., CN120 can configure one or more HSS124s. For example, the HSS124 can provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc.

[0021] S-GW122 can terminate the S1 interface 113 toward RAN110 and route data packets between RAN110 and CN120. Furthermore, S-GW122 can serve as a local mobility anchor point for RAN node handovers and also provide an anchor for 3GPP® inter-node mobility. Other responsibilities of S-GW122 include lawful interception, billing, and certain policy enforcement.

[0022] The P-GW123 can terminate the SGi interface toward the PDN. The P-GW123 can route data packets between the EPC network 120 and external networks, such as the network containing the application server 184 (also known as the Application Function (AF)), via the Internet Protocol (IP) interface 125. The P-GW123 can also communicate data to other external networks 131A, which may include the Internet, IP Multimedia Subsystem (IPS) networks, and other networks. Generally, the application server 184 may be an element providing applications that use IP bearer resources in the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service). In this embodiment, the P-GW123 is shown to be communicably coupled to the application server 184 via the IP interface 125. The application server 184 can also be configured to support one or more communication services for UE101 and 102 via CN120 (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0023] P-GW123 can also serve as a node for policy enforcement and billing data collection. The Policy and Billing Rule Function (PCRF)126 is the policy and billing control element of CN120. In non-roaming scenarios, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In roaming scenarios with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session: the Home PCRF (H-PCRF) in the HPLMN and the Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). PCRF126 can be communicably coupled to the application server 184 via P-GW123.

[0024] In one embodiment, the communication network 140A may be an IoT network or 5G network that includes a new 5G wireless network using communications in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the things currently enabling IoT is narrowband IoT (NB-IoT).

[0025] The NG system architecture can include a RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 can include multiple nodes such as gNBs and NG-eNBs. The core network 120 (e.g., a 5G core network or 5GC) can include access and mobility functions (AMF) and / or user plane functions (UPF). The AMF and UPF can be communicatively coupled to the gNB and NG-eNB via NG interfaces. More specifically, in several aspects, the gNB and NG-eNB can connect to the AMF via the NG-C interface and to the UPF via the NG-U interface. The gNB and NG-eNB can be coupled to each other via the Xn interface.

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

[0027] Figure 1B shows a non-roaming 5G system architecture in several embodiments. Referring to Figure 1B, the 5G system architecture 140B in reference point representation is shown. More specifically, UE 102 can communicate with RAN 110 and one or more other 5G core (5GC) network entities. The 5G system architecture 140B includes several network functions (NFs) such as Access and Mobility Management Function (AMF) 132, Location Management Function (LMF) 133, Session Management Function (SMF) 136, Policy Control Function (PCF) 148, Application Function (AF) 150, User Plane Function (UPF) 134, Network Slice Selection Function (NSSF) 142, Authentication Server Function (AUSF) 144, and Unified Data Management (UDM) / Home Subscriber Server (HSS) 146. The UPF 134 can provide connectivity to the Data Network (DN) 152, which may include, for example, operator services, internet access, or third-party services. AMF132 can be used to manage access control and mobility and may also include network slice selection functionality. SMF136 can be configured to set up and manage various sessions according to network policies. UPF134 can be deployed in one or more configurations depending on the desired service type. PCF148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in 4G communication systems). UDM can be configured to store subscriber profiles and data (similar to HSS in 4G communication systems).

[0028] The LMF133 can be used in conjunction with 5G positioning capabilities. In some aspects, the LMF133 receives measurements and support information from the Next Generation Radio Access Network (NG-RAN) 110 and mobile devices (e.g., UE101) via the AMF132 through the NLs interface to calculate the position of the UE101. In some aspects, positioning information can be transmitted between the NG-RAN and the LMF133 via the Next Generation Control Plane Interface (NG-C) using the NR Positioning Protocol A (NRPPa). In some aspects, the LMF133 configures the UE using the LTE Positioning Protocol (LPP) via the AMF132. The NG-RAN 110 configures the UE101 using the Radio Resource Control (RRC) protocol on the LTE-Uu and NR-Uu interfaces.

[0029] In some aspects, the 5G system architecture 140B sets up different reference signals to enable positioning measurements. Examples of reference signals that may be used for positioning measurements include a downlink positioning reference signal (NR PRS) and an uplink sounding reference signal (SRS) for positioning. The downlink positioning reference signal (PRS) is a reference signal configured to support downlink-based positioning methods.

[0030] In some respects, the 5G system architecture 140B includes not only the IP Multimedia Subsystem (IMS) 168B but also multiple IP Multimedia Core Network Subsystem Entities, such as Call Session Control Functions (CSCFs). More specifically, the IMS 168B includes CSCFs that function as Proxy CSCFs (P-CSCF) 162BE, Service CSCFs (S-CSCF) 164B, Emergency CSCFs (E-CSCF) (not shown in Figure 1B), or Question CSCFs (I-CSCF) 166B.

[0031] P-CSCF162B can be configured as the first contact point for UE102 within the IM subsystem (IMS) 168B. S-CSCF164B can be configured to handle session state within the network, and E-CSCF can be configured to handle specific aspects of emergency sessions, such as routing emergency requests to the appropriate emergency center or PSAP. I-CSCF166B can be configured to function as a contact point within the operator's network for all IMS connections destined for subscribers of that network operator, or roaming subscribers currently located within that network operator's service area. In some embodiments, I-CSCF166B can connect to another IP multimedia network 170E, for example, an IMS operated by another network operator.

[0032] In some embodiments, the UDM / HSS146 can be coupled to an application server 160E which may include a telephony application server (TAS) or another application server (AS). The AS160B can be coupled to the IMS168B via the S-CSCF164B or I-CSCF166B.

[0033] Reference point representations indicate that interactions can exist between corresponding NF services. For example, Figure 1B shows the following reference points: N1 (between UE102 and AMF132), N2 (between RAN110 and AMF132), N3 (between RAN110 and UPF134), N4 (between SMF136 and UPF134), N5 (between PCF148 and AF150 (not shown)), N6 (between UPF134 and DN152), N7 (between SMF136 and PCF148 (not shown)), N8 (between UDM146 and AMF132 (not shown)), N9 (between two UPFs 134 (not shown)), N10 (between UDM146 and SMF136 (Figure 1B) N11 (between AMF132 and SMF136 (not shown)), N12 (between AUSF144 and AMF132 (not shown)), N13 (between AUSF144 and UDM146 (not shown)), N14 (between two AMF132s (not shown)), N15 (between PCF148 and AMF132 in non-roaming scenarios, and between PCF148, the visited network and AMF132 in roaming scenarios (not shown)), N16 (between two SMFs (not shown)), and N22 (between AMF132 and NSSF142 (not shown)). Other reference point representations not shown in Figure 1B can also be used.

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

[0035] In some embodiments, as shown in Figure 1C, a service-based representation can be used to represent a network function in the control plane that allows other authorized network functions to access that service. In this regard, the 5G system architecture 140C may include the following service-based interfaces: Namf158H (service-based interface represented by AMF132), Nsmf158I (service-based interface represented by SMF136), Nnef158B (service-based interface represented by NEF154), Npcf158D (service-based interface represented by PCF148), Nudm158E (service-based interface represented by UDM146), Naf158F (service-based interface represented by AF150), Nnrf158C (service-based interface represented by NRF156), Nnssf158A (service-based interface represented by NSSF142), and Nausf158G (service-based interface represented by AUSF144). Other service-based interfaces not shown in Figure 1C (e.g., Nudr, N5g-eir, Nudsf) can also be used.

[0036] Figures 2, 3, and 4 illustrate various systems, devices, and components that can implement aspects of the disclosed embodiments in different communication systems, such as 5G-NR (and later) networks. UEs, base stations (such as gNBs), and / or other nodes described in relation to Figures 1A-4 (e.g., satellites or other NTN nodes) can be configured to perform the disclosed technologies.

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

[0038] Network 200 may include UE202, which includes any mobile or non-mobile computing devices designed to communicate with RAN204 via a wireless connection. UE202 may include, but is not limited to, smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, automotive infotainment, automotive entertainment devices, instrument clusters, head-up display devices, automotive diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0039] In some embodiments, the network 200 may include multiple UEs directly coupled to one another via a sidelink interface. The UEs may be, but are not limited to, M2M / D2D devices that communicate using physical sidelink channels such as PSBCH, PSDCH, PSCH, PSCCH, and PSFCH.

[0040] In some embodiments, the UE202 may further communicate with the AP206 via a wireless connection. The AP206 can manage the WLAN connection, which helps offload some or all of the network traffic from the RAN204. The connection between the UE202 and the AP206 can be compatible with any IEEE 802.11 protocol, and the AP206 can be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, the UE202, RAN204, and AP206 can utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular WLAN aggregation may include the UE202 configured by the RAN204 to utilize both cellular wireless resources and WLAN resources.

[0041] RAN204 may include one or more access nodes, such as an access node (AN)208. AN208 can terminate the air interface protocol for UE202 by providing access layer protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and L1 protocols. In this way, AN208 can enable data / voice connectivity between the core network (CN)220 and UE202. In some embodiments, AN208 may be implemented as one or more software entities running on a server computer, either in a separate device or as part of a virtual network, such as a CRAN or virtual baseband unit pool. AN208 is referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN208 may be a macrocell base station or low-power base station for providing femtocells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0042] In embodiments where RAN204 includes multiple ANs, they may be coupled to each other via an X2 interface (if RAN204 is an LTE RAN) or an Xn interface (if RAN204 is a 5G RAN). The X2 / Xn interface may be separated into a control / user plane interface in some embodiments, but may allow ANs to communicate information related to handover, data / context transfer, mobility, load management, interference adjustment, etc.

[0043] Each AN of RAN204 can manage one or more cells, cell groups, component carriers, etc., and provide an air interface for network access to UE202. UE202 can be simultaneously connected to multiple cells provided by the same or different ANs of RAN204. For example, UE202 and RAN204 can use carrier aggregation to allow UE202 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual-connection scenario, the first AN might be the master node providing the MCG, and the second AN might be the secondary node providing the SCG. The first / second ANs could be any combination of eNBs, gNBs, ng-eNBs, etc.

[0044] The RAN204 can provide an air interface on licensed or unlicensed spectra. To operate on unlicensed spectra, nodes may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCells / SCells. Before accessing unlicensed spectra, nodes may perform medium / carrier sensing operations, for example, based on the listen-before-talk (LBT) protocol.

[0045] In a V2X scenario, UE202 or AN208 is or functions as a Roadside Unit (RSU) that references any transport infrastructure entity used for V2X communication. An RSU is implemented in or by a suitable AN or fixed (or relatively fixed) UE. An RSU implemented in or by a UE is sometimes called a “UE-type RSU.” An eNB is sometimes called an “eNB-type RSU.” A gNB is sometimes called a “gNB-type RSU.” And so on. In one example, an RSU is a computing device coupled with a radio frequency circuit positioned along the roadside to provide connectivity support for passing vehicle UEs. An RSU may also include internal data storage circuitry to store intersection map shapes, traffic statistics, and media, as well as applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. An RSU can provide very low-latency communication required for high-speed events such as collision avoidance and traffic warnings. Additionally, or alternatively, an RSU can provide other cellular / WLAN communication services. The RSU components are packaged in a weather-resistant enclosure suitable for outdoor installation and may include a network interface controller that provides a traffic signaling controller or wired connectivity (e.g., Ethernet) to a backhaul network.

[0046] In some embodiments, RAN204 may be an LTE RAN210 with an eNB, eNB212, for example. The LTE RAN210 may provide an LTE air interface having the following characteristics: 15 kHz subcarrier spacing (SCS); CP-OFDM waveforms for downlink (DL) and SC-FDMA waveforms for uplink (UL); turbo code for data and TBCC for control; 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 measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate in the sub-6 GHz band.

[0047] In some embodiments, the RAN204 may be an NG-RAN214 having a gNB, e.g., gNB216, or an ng-eNB, e.g., ng-eNB218. The gNB216 can connect to a 5G-enabled UE using a 5G NR interface. The gNB216 can connect to the 5G core via an NG interface which may include an N2 interface or an N3 interface. The ng-eNB218 can also connect to the 5G core via an NG interface, but it can also connect to the UE via an LTE Air interface. The gNB216 and ng-eNB218 can connect via an Xn interface.

[0048] In some embodiments, the NG interface can be divided into two parts: an NG user plane (NG-U) interface that transmits traffic data between the NG-RAN214 node and the UPF248 (e.g., the N3 interface), and an NG control plane (NG-C) interface that is a signaling interface between the NG-RAN214 node and the AMF244 (e.g., the N2 interface).

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

[0050] In some embodiments, the 5G-NR air interface can utilize Bandwidth Portions (BWPs) for various purposes. For example, BWPs can be used for dynamic adaptation of SCSs. For instance, a UE202 can be configured with multiple BWPs, each with a different SCS. When a change in a BWP is instructed to the UE202, the transmit SCS is also changed accordingly. Another use case for BWPs relates to power saving. In particular, multiple BWPs can be configured for a UE202 with different amounts of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. BWPs with a small number of PRBs can be used for data transmission with low traffic loads while enabling power saving in the UE202 and possibly the gNB216. BWPs with a large number of PRBs can be used for scenarios with high traffic loads.

[0051] RAN204 is communicatively coupled to CN220, which includes network elements, and provides various functions to support data and telecommunications services to customers / subscribers (e.g., users of UE202). The components of CN220 can be implemented on a single physical node or on separate physical nodes. In some embodiments, NFV can be used to virtualize some or all of the functions provided by the network elements of CN220 on physical computing / storage resources such as servers and switches. Logical instantiations of CN220 are called network slices, and some logical instantiations of CN220 are called network subslices.

[0052] In some embodiments, the CN220 may be connected to an LTE radio network as part of an Extended Packet System (EPS) 222, also known as the EPC (or Extended Packet Core). The EPC222 may include MME224, SGW226, SGSN228, HSS230, PGW232, and PCRF234 coupled to each other on an interface (or “reference point”), as shown in the figure. The function of each element of the EPC222 is briefly described below.

[0053] The MME224 can implement mobility management features that track the current location of the UE202 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and more.

[0054] SGW226 can terminate the S1 interface toward the RAN and route data packets between the RAN and EPC222. SGW226 may also be a local mobility anchor point for RAN node handovers and may provide anchors for 3GPP® inter-mobility. Other responsibilities may include lawful interception, indictment, and certain policy enforcement.

[0055] The SGSN228 can track the location of the UE202 and perform security functions and access control. Furthermore, the SGSN228 can perform EPC node-to-node signaling for movement between different RAT networks. Selection of PDN and S-GW specified by the MME224; selection of MME for handover; and an S3 reference point between the MME224 and SGSN228 enable user-bearer information exchange for 3GPP® inter-access network movement in idle / active states.

[0056] The HSS230 can include a database for network users, containing subscriber-related information to support the processing of communication sessions by network entities. The HSS230 can provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS230 and the MME224 can enable the transfer of subscriber and authentication data for authenticating / authorizing user access to the LTE CN220.

[0057] PGW232 can terminate the SGi interface to the data network (DN) 236, which may include an application / content server 238. PGW232 can route data packets between the LTE CN 220 and the data network 236. PGW232 can be coupled with SGW226 via an S5 reference point to facilitate user-plane tunneling and tunnel management. PGW232 can further include nodes for policy enforcement and billing data collection (e.g., PCEF). Furthermore, the SGi reference point between PGW232 and the data network 236 can be, for example, an operator-external public, private PDN, or an operator-internal packet data network for providing IMS services. PGW232 can be coupled with PCRF234 via a Gx reference point.

[0058] PCRF234 is the policy and billing control element of LTE CN220. PCRF234 may be communicatively coupled to the application / content server 238 to determine appropriate QoS and billing parameters for the service flow. PCRF234 can provision relevant rules to the PCEF (via the Gx reference point) with appropriate TFT and QCI.

[0059] In some embodiments, CN220 may be 5GC240. 5GC240 may include AUSF242, AMF244, SMF246, UPF248, NSSF250, NEF252, NRF254, PCF256, UDM258, and AF260 coupled to each other on an interface (or "reference point"), as shown in the figure. The functions of the elements in 5GC240 are briefly described below.

[0060] The AUSF242 can store data for UE202 authentication and handle authentication-related functions. The AUSF242 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC240 via a reference point, as illustrated, the AUSF242 can provide a Nausf service-based interface.

[0061] The AMF244 enables other functions of the 5GC240 to communicate with the UE202 and RAN204 and subscribe to notifications regarding mobility events related to the UE202. The AMF244 can be responsible for registration management (e.g., when registering the UE202), connectivity management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF244 provides transport for SM messages between the UE202 and SMF246 and acts as a transparent proxy for routing SM messages. The AMF244 may also provide transport for SMS messages between the UE202 and SMSF. The AMF244 can interact with the AUSF242 and UE202 to perform various security anchor and context management functions. Furthermore, the AMF244 may include an N2 reference point between the RAN204 and the AMF244, or may be the termination point of the RAN CP interface which is an N2 reference point. Furthermore, the AMF244 may be the termination point for NAS(N1) signaling and may perform NAS encryption and integrity protection. The AMF244 may also support NAS signaling by UE202 via the N3 IWF interface.

[0062] SMF246 performs the following: SM (e.g., session establishment and tunnel management between UPF248 and AN208); UE IP address allocation and management (including optional authorization); UP function selection and control; setting traffic steering on UPF248 to route traffic to appropriate destinations; interface termination processing to policy control functions; policy enforcement, billing, and some QoS control; lawful interception (for SM events and interface to LI systems); termination processing of the SM portion of NAS messages; downlink data notification; initiation of AN-specific SM information sent to AN208 via AMF244 over N2; and determining the session's SSC mode. SM may refer to the management of PDU sessions, and PDU sessions or “session” may refer to the aPDU connectivity service that provides or enables the exchange of PDUs between UE202 and data network 236.

[0063] UPF248 may function as an anchor point for intra- and inter-RAT movement, an external PDU session point interconnecting with data network 236, and a branch point to support multi-homed PDU sessions. UPF248 can 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., SDF-to-QoS flow mapping), perform transport-level packet marking on uplinks and downlinks, and perform downlink packet buffering and downlink data notification triggers. UPF248 may include an uplink classifier to support routing of traffic flows to the data network.

[0064] The NSSF250 can select a set of network slice instances to serve the UE202. The NSSF250 can also, if necessary, determine the mapping between authorized NSSAIs and joined S-NSSAIs. The NSSF250 can also determine a list of candidate AMFs, either by querying the NRF254, based on the set of AMFs used to serve the UE202, or, depending on the appropriate configuration. The selection of a set of network slice instances for the UE202 may be triggered by the AMF244 to which the UE202 is registered, through interaction with the NSSF250, potentially leading to a change in the AMF. The NSSF250 may interact with the AMF244 via the N22 reference point. It may also communicate with other NSSFs in the accessed network via the N31 reference point (not shown). Furthermore, the NSSF250 may exhibit an NNSSF service-based interface.

[0065] NEF252 can securely expose services and functions provided by third-party 3GPP® network functions, internal exposure / re-exposure, AFs (e.g., AF260), edge computing, or fog computing systems. In such embodiments, NEF252 can authenticate, authorize, or throttle AFs. NEF252 can also translate information exchanged with AF260 and information exchanged with internal network functions. For example, NEF252 can translate between AF service identifiers and internal 5GC information. NEF252 can also receive information from other NFs based on the exposed functions of those NFs. This information is stored in NEF252 as structured data or in a data storage NF using a standardized interface. Stored information can be re-exposed by NEF252 to other NFs and AFs, or used for other purposes such as analysis. Furthermore, NEF252 can also display Nnef service-based interfaces.

[0066] The NRF254 supports service discovery functionality, receiving NF discovery requests from NF instances and providing information about discovered NF instances to those instances. The NRF254 also maintains information about available NF instances and their supported services. Terms used herein, such as “instantiation,” may refer to the creation of an instance, while “instance” may refer to the specific occurrence of an object, such as during the execution of program code. Furthermore, the NRF254 may refer to an Nnrf service-based interface.

[0067] PCF256 can provide and enforce policy rules to control plane functions and can also support a unified policy framework for controlling network behavior. PCF256 can also implement a front-end for accessing subscription information related to policy decisions in the UDR of UDM258. In addition to communicating with functions via reference points as shown, PCF256 exhibits an Npcf service-based interface.

[0068] The UDM258 processes subscriber-related information to support the handling of communication sessions for network entities and can store subscriber data for the UE202. For example, subscriber data can be communicated via an N8 reference point between the UDM258 and the AMF244. The UDM258 can include two parts: an application frontend and a UDR. The UDR can store subscriber and policy data for the UDM258 and PCF256, and / or structured data for exposure and application data for the NEF252 (including a PFD for application discovery and application request information for multiple UEs). A Nudr service-based interface is displayed by the UDR and can allow the UDM258, PCF256, and NEF252 to access specific sets of data stored in the UDR, read notifications of relevant data changes in the UDR, and update (e.g., add, modify), delete, and subscribe. The UDM may include a UDM-FE responsible for credential processing, location management, subscription management, etc. Multiple different frontends may serve the same user in different transactions. UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points, as shown, UDM258 can represent a Nudm service-based interface.

[0069] The AF260 can influence traffic routing applications, provide access to the NEF, and interact with the policy framework for policy control.

[0070] In some embodiments, the 5GC240 can enable edge computing by selecting an operator / third-party service geographically close to the point where the UE202 is connected to the network. This can reduce latency and load on the network. To provide an implementation of edge computing, the 5GC240 can select a UPF248 close to the UE-202 and perform traffic steering from the UPF248 to the data network 236 via the N6 interface. This may be based on UE join data, UE location, and information provided by the AF260. In this way, the AF260 may influence UPF(re) selection and traffic routing. If the AF260 is considered a trusted entity based on the operator's placement, the network operator may allow the AF260 to interact directly with the relevant NF. Furthermore, the AF260 may represent a NAF service-based interface.

[0071] The data network 236 can represent various network operator services, internet access, or third-party services provided by one or more servers, including, for example, an application / content server 238.

[0072] Figure 3 schematically shows the wireless network 300 in various embodiments. The wireless network 300 may include UE302 in wireless communication with AN304. UE302 and AN304 are similar to and substantially interchangeable with similarly named components described elsewhere in this specification.

[0073] UE302 can be communicatively coupled to AN304 via connection 306. Connection 306 is illustrated as an air interface to enable communicative coupling and can be compatible with cellular communication protocols such as LTE or 5G NR protocols operating at mmWave or sub-6GHz frequencies.

[0074] The UE302 may include a host platform 308 coupled with a modem platform 310. The host platform 308 may include an application processing circuit 312 coupled with the protocol processing circuit 314 of the modem platform 310. The application processing circuit 312 can run various applications for the UE302 to source / sink application data. The application processing circuit 312 may further implement one or more layer operations for sending and receiving application data to and from a data network. These layer operations may include transport operations (e.g., IP) and internet operations.

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

[0076] The modem platform 310 may further include a digital baseband circuit 316 that can implement one or more layer operations, which are “lower” layer operations performed by the protocol processing circuit 314 in the network protocol stack. These operations include, for example, one or more HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bitmetric determination, multi-antenna port precoding / decoding, which may include one or more spatiotemporal, spatial frequency or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronous sequence generation / detection, control channel signal blind decoding, and other related functions.

[0077] The modem platform 310 further includes a transmit circuit 318, a receive circuit 320, an RF circuit 322, and an RF front end (RFFE) 324, which may include or be connected to one or more antenna panels 326. In short, the transmit circuit 318 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc. The receive circuit 320 may include an analog-to-digital converter, a mixer, an IF component, etc. The RF circuit 322 may include a low-noise amplifier, a power amplifier, a power tracking component, etc. The RFFE 324 may include filters (e.g., surface / bulk acoustic filters), switches, an antenna tuner, a beamforming component (e.g., a phase array antenna component), etc. The selection and arrangement of the components of the transmitting circuit 318, receiving circuit 320, RF circuit 322, RFFE 24, and antenna panel 326 (collectively referred to as the “transmitting / receiving components”) may be specific to particular implementation details, such as whether the communication is TDM or FDM, or whether it is mmWave or sub-6GHz frequency. In some embodiments, the transmitting / receiving components may be arranged in multiple parallel transmit / receive chains, or they may be arranged on the same or different chips / modules.

[0078] In some embodiments, the protocol processing circuit 314 may include one or more instances of a control circuit (not shown) that provides control functions for the transmit / receive components.

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

[0080] UE transmission can be established by or through the protocol processing circuit 314, digital baseband circuit 316, transmitting circuit 318, RF circuit 322, RFFE 324, and antenna panel 326. In some embodiments, the transmitting component of UE 302 can apply a spatial filter to the transmitted data to form a transmit beam radiated by the antenna elements of antenna panel 326.

[0081] Similar to the UE302, the AN304 may include a host platform 328 coupled with a modem platform 330. The host platform 328 may include an application processing circuit 332 coupled with the 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 AN304 are similar to and substantially interchangeable with similarly named components of the UE302. In addition to performing data transmission and reception as described above, the components of the AN304 can perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0082] Figure 4 is a block diagram showing a component capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transient machine-readable storage medium) and executing one or more of the methodologies described herein, according to some examples. Specifically, Figure 4 shows a schematic diagram of a hardware resource 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 processors may be communicatively coupled via a bus 440 or other interface circuitry. In embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 402 can be run to provide execution environments for one or more network slices / subslice for utilizing the hardware resource 400. Processor 410 may include, for example, processors 412 and 414. Processor 410 can be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a composite 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 described herein), or any suitable combination thereof.

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

[0084] The communication resource 430 may include an interconnect or network interface controller, component, or other suitable device for communicating with one or more peripheral devices 404 or one or more databases 406 or other network elements via the network 408. For example, the communication resource 430 may include a wired communication component (e.g., connected via USB, Ethernet, etc.), a cellular communication component, an NFC component, a Bluetooth® (or Bluetooth® Low Energy) component, a Wi-Fi® component, and other communication components.

[0085] Instruction 450 may include software, programs, applications, applets, apps, or other executable code to cause at least one of the processors 410 to perform one or more of the methodologies described herein. Instruction 450 may reside, whole or in part, within the processor 410 (e.g., within the processor's cache memory), the memory / storage device 420, or at least one of any suitable combination thereof. Furthermore, any part of instruction 450 may be transferred from any combination of peripheral devices 404 or the database 406 to the hardware resource 400. Thus, the memory of the processor 410, the memory / storage device 420, the peripheral devices 404, and the database 406 are examples of computer-readable and machine-readable media.

[0086] In one or more embodiments, at least one of the components outlined in one or more of the above figures may be configured to perform one or more operations, techniques, processes and / or methods, as outlined in the Examples section below. For example, a baseband circuit related to one or more of the above figures may be configured to operate according to one or more of the Examples section below. As another example, a circuit related to the above-mentioned UE, base station, satellite, network element, etc., related to one or more of the above figures may be configured to operate according to one or more of the Examples section below.

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

[0088] The term “machine learning” or “ML” refers to the use of computer systems that implement algorithms and / or statistical models to perform specific tasks without using explicit instructions, but instead relying on patterns and inference. An ML algorithm builds or estimates a mathematical model (called an “ML model” or similar) based on sample data (such as “training data” or “model training information”) to make predictions or decisions even if it is not explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with respect to a task and a performance measure, and an ML model may be any object or data structure created after an ML algorithm has been trained on one or more training datasets. After training, an ML model can be used to make predictions on a new dataset. The term “ML algorithm” refers to a different concept from the term “ML model,” but these terms are used interchangeably in this disclosure as discussed herein.

[0089] The terms "machine learning model" and "ML model" can also refer to the ML methods and concepts used by ML-assisted solutions. An "ML-assisted solution" is a solution that uses ML algorithms during operation to address a specific use case. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithm, 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-arm bandit learning, deep RL, etc.), neural networks, etc. Depending on the implementation, a particular ML model can have many submodels as components, and an ML model can train all submodels together. Individually trained ML models can also be linked together in an ML pipeline during inference. An "ML pipeline" is a set of features, functions, or feature entities specific to an ML-assisted solution. An ML pipeline can include a data pipeline, a model training pipeline, a model evaluation pipeline, and one or more data sources within an actor. An "actor" is an entity that hosts the 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 (which includes both model execution and, where applicable, online learning). The ML host informs actors about the output of the ML algorithm, and the actors decide on actions ("actions" are performed by the actors as a result of the output of the ML-assisted solution). "Model inference information" refers to the information used as input to the ML model to determine inference. While the data used to train the ML model and the data used to determine inference may overlap, "training data" and "inference data" refer to different concepts.

[0090] In 5G NR systems, gNB / UEs can transmit multiple PDSCH / PUSCH / PUCCH repetitions to improve transmission coverage. In some aspects, PDSCH / PUSCH / PUCCH repetitions are transmitted on different time resources determined by the DCI or RRC configuration. In some embodiments, the PDSCH / PUSCH / PUCCH repetition framework can be extended to support multiple TRP operations to improve transmission reliability. More specifically, as shown in Figure 5, PDSCH repetitions can be used at the same CC time and frequency.

[0091] Figure 5 shows PDSCH transmission from multiple TRPs with repetition in time and frequency according to several aspects.

[0092] In some embodiments, multi-TRP PDCCH transmission and multi-TRP PUSCH / PUCCH reception with repetition can be supported to enhance transmission robustness against potential link interruptions. The above repetitions can be limited to the same supply cell.

[0093] Carrier aggregation (CA) can be used in NR to aggregate multiple component carriers (CCs) and use them jointly for transmission to and from a single UE. In some aspects, it combines two or more carriers into a single data channel to expand the data capacity of the network.

[0094] In some embodiments, PDSCH / PUSCH / PUCCH reliability can be enhanced by using multi-component carrier (multi-CC) based repetition to achieve higher frequency diversity gain. More specifically, the disclosed techniques can be used to enhance the robustness and flexibility of PDSCH / PUSCH / PUCCH transmissions for URRLC applications.

[0095] In some embodiments, two approaches can be used to support multi-CC-based PDSCH / PUSCH repetition: single-DCI-based (e.g., Figure 6) and multi-DCI-based (Figure 7).

[0096] Figure 6 shows a single DCI-based multi-CC PDSCH iteration according to several aspects.

[0097] Figure 7 shows a multi-DCI based multi-CC PDSCH iteration according to several aspects.

[0098] Specifically, in a single DCI-based scheme, the DCI uses a cross-scheduling framework to schedule PDSCH / PUSCH repetitions to be sent across multiple CCs. In a multi-DCI-based scheme, each DCI schedules the transmission of groups of PDSCH / PUSCH repetitions across the same CC that carries the self-scheduling DCI.

[0099] In some respects, to improve reliability performance, the transport block (TB) size of PDSCH / PUSCH repetitions can be made the same to enable soft coupling or selective diversity reception of PDSCH / PUSCH repetitions in gNB / UE. Therefore, it can be guaranteed that the same TB size is maintained while using DCI to schedule PDSCH / PUSCH repetitions. Furthermore, redundant versions of each TB and HARQ-ACK reports can be configured.

[0100] In some embodiments, single DCI (cross-scheduling) based multi-CC PDSCH / PUSCH repetitions and multi-DCI (self-scheduling) based multi-CC PDSCH / PUSCH repetitions can be used. In multi-CC PDSCH / PUSCH repetition scenarios, to achieve frequency diversity, the gNB / UE transmits the same information through multiple CCs. The PDSCH / PUSCH repetitions received by the UE / gNB can be decoded by a soft-coupled or selective diversity receiver. In either method, the TB size (TBS), determined using the TB information communicated via DCI, can be the same for different PDSCH / PUSCH repetitions. In some aspects, the TB size is determined by a non-quantized intermediate variable (N info ) can be determined according to, where N info =N RE Race Queen m ν is N RE Q is the number of resource elements (REs) in the slot, R is the code rate, and Q is the number of resource elements (REs) in the slot. m n is the modulation order, and ν is the number of layers. info The variables related to the calculation can be communicated via DCI. In order to achieve the necessary operations, TBS can be determined using the above parameters based on one CC.

[0101] In some embodiments, to enable single DCI-based multi-CC PDSCH / PUSCH repetition, the carrier indicator field (CIF) of the DCI may be enhanced to indicate transmissions with repetitions across two or more CCs. The corresponding CIF can support indication of transmissions from any CC without repetition. If other fields of the DCI are enhanced for single DCI-based multi-CC PDSCH / PUSCH repetition, the same TB size can be guaranteed across repetitions.

[0102] In some embodiments, for single DCI multi-CC PDSCH / PUSCH repetitions, each CC uses its pool of HARQ processes, but for multi-DCI PDSCH / PUSCH repetitions, both CCs share all or a subset of the HARQ processes. For example, one subset of the HARQ processes on each CC can be used for non-repeating PDSCH / PUSCH transmissions, while another subset of the HARQ processes can be used for repeating PDSCH / PUSCH transmissions.

[0103] In some embodiments, redundant versions of the TB can be specified for both single-DCI and multi-DCI-based schemes. The RV mapping for a single-DCI-based scheme can be designed as follows: The 2-bit RV field of the DCI indicates the first RV for the first PDSCH / PUSCH iteration of the first CC. The RV pattern (0231) can be applied individually to the PDSCH / PUSCH iterations of different CCs and may constitute the RV offset of the starting RV for the first iteration of the remaining CCs, as shown in Figure 6, where the RV offset is 1. For a multi-CC-based scheme, the RV pattern (0231) can be applied, and the 2-bit RV field of the DCI indicates the first RV for the first PDSCH / PUSCH iteration, as shown in Figure 7, where the RV offset is 1.

[0104] Figure 8 shows the HARQ reporting group for multi-CC PDSCH repeats according to several aspects.

[0105] In some embodiments, the disclosed technology can be used in connection with a HARQ-ACK process for multi-CC PDSCH repetition. NR can support multiplexing HARQ acknowledgments of multiple transport blocks into an acknowledgment bitmap when multiple TBs need to be received simultaneously in carrier aggregation and codebook-grade (CBG) based retransmission scenarios, or when multiple acknowledgments need to be sent simultaneously on the uplink. This bitmap can be signaled via either a semi-static or dynamic codebook configured by RRC signaling. However, this process may be used in connections with different TB transmissions that may not be optimized for TB repetition.

[0106] To improve the efficiency of HARQ-ACK transmission for multi-CC PDSCH repeats, in some embodiments, one-shot ACKs or NACKs can be communicated for groups of PDSCH repeats. In particular, as shown in Figure 8, one or more HARQ-ACK reporting groups can be configured on the UE to send only one ACK / NACK for all PDSCH repeats. More specifically, the HARQ-ACK reporting groups can be indicated by DCI. The UE continues to decode the PDSCH repeats using soft coupling techniques. Once the UE has successfully decoded a PDSCH repeat, it stops decoding the remaining PDSCH repeats and sends the HARQ-ACK of the lowest group to which the successfully decoded PDSCH repeat belongs. For example, in Figure 8, PDSCH rep0 belongs to group 0, group 1, and group 2. Upon successful decoding of PDSCH rep0, the UE sends HARQ-ACK 0 to the gNB instead of HARQ-ACK 1 or 2. If none of the repetitions, or any soft combination thereof, are successfully decoded, the UE reports a HARQ-NACK2. This scheme saves resources if the PDSCH is successfully decoded and an ACK is reported before the last repetition is sent.

[0107] Figure 9 shows PUSCH / PUCCH transmission with carrier switching in several different configurations.

[0108] In some embodiments, multi-CC repetitions of PUCCH and PUSCH may be supported by carrier switching (e.g., as shown in Figure 9). For example, the UE may be composed of higher layers or may be indicated by DCI by one or more carrier indices to be used for the corresponding uplink transmission. In some aspects, different carriers may belong to one frequency band. In other embodiments, different carriers belong to different bands. In some embodiments, the UE may also have a switching gap between the last symbol of the first uplink transmission and the first symbol of the second uplink transmission.

[0109] In some embodiments, as shown in Figure 10, different carriers or component carriers can correspond to different TRPs.

[0110] Figure 10 shows PDCCH / PDSCH / PUSCH / PUCCH repetition with multi-CC repetition and multi-TRP transmission according to several aspects.

[0111] In some aspects, systems and methods for transmission with repetitions on two or more carriers are disclosed, which may include configurations for transmission with repetitions for a physical channel, a set of instructions for two or more carriers for transmission with repetitions according to the configuration, and transmissions according to the instructions. In some aspects, instructions for transmission with repetitions on multiple carriers are made by a single DCI transmitted from one component carrier. In some embodiments, instructions for transmission with repetitions are performed by two or more DCIs transmitted from two or more component carriers. In some embodiments, the physical channel is a physical downlink shared channel, a physical uplink shared channel, or a physical uplink control channel. In some embodiments, the DCI includes fields that provide information about the carrier on which the repetition transmission is performed. In some embodiments, one DCI indicates the initial transmission, and the other DCI indicates a retransmission by the same HARQ process. In some embodiments, the initial transmission is indicated as no later than the retransmission. In some embodiments, the redundant version of each repetition depends on the carrier index on which the transmission is performed. The redundant version is indicated in the DCI, and the redundant version offset is indicated in the upper layer or DCI. In some embodiments, HARQ is provided for a group of PDSCHs with repetitions. In some embodiments, a single ACK / NACK transmission is provided for all PDSCH repetitions. In some embodiments, one group of repetitions is a subset of another group of repetitions. In some embodiments, transmissions with repetitions are performed on different carriers with carrier switching, where time gaps can be allocated between repetitions on different carriers. In some embodiments, transmissions with repetitions are performed on different carriers, where different carriers are associated with different TRPs.

[0112] Figure 11 shows block diagrams of communication devices such as evolved Node-B (eNB), next-generation Node-B (gNB) (or other RAN nodes or base stations), transmit / receive points (TRP), access points (AP), radio stations (STA), mobile stations (MS), or user equipment (UE), according to several aspects. In an alternative embodiment, the communication device 1100 may operate as a standalone device or be connected to other communication devices (e.g., networked).

[0113] A circuit (e.g., a processing circuit) is a collection of circuits implemented in a tangible entity of a device 1100, including hardware (e.g., simple circuits, gates, logic, etc.). Circuit membership can be flexible over time. A circuit includes members that can perform specified operations at operating time, individually or in combination. In one example, the hardware of a circuit may be designed immutably to perform a particular operation (e.g., wired). In one example, the hardware of a circuit may include variable-connected physical components (e.g., execution units, transistors, simple circuits, etc.) that include a machine-readable medium (e.g., an arrangement of magnetic, electrical, or movable invariant mass particles) that has been physically modified to encode instructions for a particular operation.

[0114] When physical components are connected, the underlying electrical properties of the hardware components change, for example, from an insulator to a conductor, or vice versa. Instructions allow embedded hardware (e.g., an execution unit or loading mechanism) to create members of circuits within the hardware via variable connections to perform a specific part of an operation during operation. Thus, in one example, a machine-readable medium element is part of a circuit or is communicatively coupled to other components of a circuit while the device is operating. In one example, any of the physical components can be used in one or more components of one or more circuits. For example, during operation, an execution unit may be used in a first circuit of a first circuit at one point, and then reused by a second circuit of the first circuit, or at another point by a third circuit of the second circuit. Additional examples of these components relating to device 1100 are shown below.

[0115] In some embodiments, device 1100 may operate as a standalone device or be connected to other devices (e.g., networked). In a networked deployment, communication device 1100 may operate as a server communication device, a client communication device, or both in a server-client network environment. In one example, communication device 1100 may operate as a peer communication device in a peer-to-peer (P2P) (or other distributed) network environment. Communication device 1100 may be a UE, eNB, PC, tablet PC, STB, PDA, mobile phone, smartphone, web appliance, network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) specifying actions to be performed by that communication device. Furthermore, although only a single communication device is illustrated, the term “communication device” also includes any collection of communication devices that individually or collectively execute a set (or set) of instructions to perform one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.

[0116] As described herein, examples may include, or operate on, logic or a number of components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) capable of performing a specific operation and may be configured or arranged in a specific way. In an example, a circuit may be arranged in a specific way as a module (e.g., internally or with respect to external entities such as other circuits). In an example, one or more computer systems (e.g., standalone, client, or server computer systems) or one or more hardware processors, in whole or in part, may be configured by firmware or software (e.g., instructions, application parts, or applications) as a module that operates to perform a specific operation. In an example, the software may reside on a communication device-readable medium. In an example, the software, when executed by the underlying hardware of a module, causes the hardware to perform a specified operation.

[0117] Therefore, the term “module” is understood to include tangible entities that are physically constructed, specifically configured (e.g., wired), or temporarily configured (e.g., transiently) (e.g., programmed) to operate in a specified manner or to perform some or all of the operations described herein. Considering an example where a module is temporarily configured, each module does not need to be instantiated at any given time. For example, if a module includes 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 to, for example, configure a particular module at one time and different modules at different times.

[0118] The communication device (e.g., UE) 1100 includes a hardware processor 1102 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), main memory 1104, static memory 1106, and storage devices 1107 (e.g., a hard drive, tape drive, flash storage, or other block or storage devices), some or all of which may communicate with each other via an interlink (e.g., a bus) 1108.

[0119] The communication device 1100 may further include a display device 1110, an alphanumeric input device 1112 (e.g., a keyboard), and a user interface (UI) navigation device 1114 (e.g., a mouse). In one example, the display device 1110, the input device 1112, and the UI navigation device 1114 may be touchscreen displays. The communication device 1100 may further include a signal generator 1118 (e.g., a speaker), a network interface device 1120, and one or more sensors 1121 such as a Global Positioning System (GPS) sensor, a compass, an accelerometer, or another sensor. The communication device 1100 may also include an output controller 1128 for communicating with or controlling one or more peripheral devices (e.g., a printer, a card reader, etc.) via a serial (e.g., Universal Serial Bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near-field communication (NFC), etc.) connection).

[0120] The storage device 1107 may include a communication device-readable medium 1122 on which one or more sets of data structures or instructions 1124 (e.g., software) that embody or utilize one or more of the technologies or functions described herein are stored. In some embodiments, the registers of the processor 1102, main memory 1104, static memory 1106 and / or storage device 1107 may be a device-readable medium 1122 on which one or more sets of data structures or instructions 1124 that embody or utilize one or more of the technologies or functions described herein are stored, or may (all or at least partially) include one. In one example, one or any combination of the hardware processor 1102, main memory 1104, static memory 1106 or mass storage device 1116 may constitute the device-readable medium 1122.

[0121] As used herein, the term “device-readable medium” is interchangeable with “computer-readable medium” or “machine-readable medium.” Although the communication device-readable medium 1122 is illustrated as a single medium, the term “communication device-readable medium” may include a single medium or multiple mediums configured to store one or more instructions 1124 (e.g., a centralized or distributed database, and / or associated caches and servers). The term “communication device-readable medium” includes the term “machine-readable medium” or “computer-readable medium” and may include any medium capable of storing, encoding, or carrying instructions (e.g., instructions 1124) for execution by the communication device 1100, causing the communication device 1100 to execute one or more of the technologies of this disclosure, or storing, encoding, or carrying data structures used by or associated with such instructions. Examples of non-limiting communication device-readable mediums include solid memory and optical and magnetic media. Specific examples of communication device-readable media include semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and non-volatile memory such as 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, communication device-readable media may include non-transition communication device-readable media. In some examples, communication device-readable media may include communication device-readable media that are not non-transition propagating signals.

[0122] Instruction 1124 can further be transmitted or received over a communication network 1126 using a transmission medium via a network interface device 1120 that utilizes one of a number of transport protocols. In one example, the network interface device 1120 may include one or more physical jacks (such as Ethernet, coaxial, or telephone jacks) or one or more antennas for connecting to the communication network 1126. In one example, the network interface device 1120 may include multiple antennas for wireless communication using at least one of the following technologies: single input multiplexed output (SIMO), MIMO, or multiple input single output (MISO). In some examples, the network interface device 1120 may be able to wirelessly communicate using multiple user MIMO technology.

[0123] The term "transmission medium" includes any intangible medium on which instructions for execution by the communication device 1100 can be stored, encoded, or transmitted, and includes other intangible mediums that facilitate the communication of digital or analog communication signals or such software. In this regard, the transmission medium in the context of this disclosure is a device-readable medium.

[0124] The terms “machine-readable medium,” “computer-readable medium,” and “device-readable medium” mean the same thing and can be used interchangeably in this disclosure. These terms are defined to include both machine storage media and transmission media. Thus, the terms include both storage devices / mediums and carrier / modulated data signals.

[0125] A subject-described implementation may include one or more features, either individually or in combination as shown below as examples.

[0126] Example 1 is an apparatus for a user equipment (UE) configured to operate in a fifth-generation new radio (5G NR) network, the apparatus including a processing circuit, which configures the UE for multiple component carrier repeated transmissions in a 5G NR network, the processing circuit decodes the DCI, which includes downlink control information (DCI), transport block (TB) information and scheduling information received via a physical downlink control channel (PDCCH), scheduling information indicating scheduled transmissions of multiple repetitions of the physical downlink shared channel (PDSCH) TB using multiple component carriers; determines the TB size associated with the scheduled transmission using the TB information; decodes the multiple repetitions of the PDSCH TB (multiple repetitions received from one or more base stations during the scheduled transmission); determines PDSCH data based on the multiple repetitions of the PDSCH TB and the TB size; and a memory connected to the processing circuit and configured to store the DCI.

[0127] In Example 2, the subject of Example 1 includes a subject in which the processing circuit is configured to perform soft coupling of multiple iterations of PDSCH TB based on TB size in order to determine PDSCH data.

[0128] In Example 3, the subjects of Examples 1 and 2 include subjects in which the processing circuit is configured to perform multiple iterative selective diversity reception of PDSCH TB based on TB size to determine PDSCH data.

[0129] In Example 4, the subjects of Examples 1-3 include subjects in which the processing circuit is configured to decode the DCI to further determine the redundant version (RV) associated with the initial transmission of the scheduling transmission.

[0130] In Example 5, the subject of Example 4 includes a subject configured such that the processing circuit determines additional RVs related to subsequent transmissions of a scheduling transmission occurring after a subsequent transmission, based on the RV and a pre-configured RV offset applied to the pre-configured RV pattern.

[0131] In Example 6, the subject of Example 5 includes a subject in which the processing circuit is configured to further determine PDSCH data based on RV and additional RV. In Example 7, the themes of Examples 1-6 include themes in which processing circuits are configured to encode one-shot acknowledgments (ACKs) or one-shot non-acknowledgments (NACKs) for transmission to one or more base stations using a physical uplink control channel (PUCCH), and one-shot ACKs or one-shot NACKs associated with a subset of multiple repetitions of PDSCH TBs received from one or more base stations during a scheduled transmission.

[0132] In Example 8, the themes of Examples 1-7 include themes in which a processing circuit is configured to decode the DCI to further determine multiple carrier indices associated with multiple corresponding transmission frequencies.

[0133] In Example 9, the subject of Example 8 includes a subject in which a processing circuit is configured to encode uplink data for transmission to one or more base stations using multiple iterations of a physical uplink shared channel (PUSCH) TB that use multiple component carriers corresponding to multiple transmission frequencies.

[0134] In Example 10, the subject of Example 9 includes a subject in which one or more base stations include multiple transmit / receive points (TRPs), and uplink data is encoded for transmission to multiple TRPs using multiple transmit frequencies.

[0135] In Example 11, the subject of Examples 1-10 includes a transceiver circuit coupled to a processing circuit, and one or more antennas coupled to the transceiver circuit.

[0136] Example 12 is a computer-readable storage medium that stores instructions for causing a base station to perform operations including: instructions for execution by one or more processors of the base station; instructions for configuring the base station for repeated transmission of multiple component carriers in a fifth-generation new radio (5G NR) network; encoding first downlink control information (DCI) for transmission to a user equipment (UE) via a physical downlink control channel (PDCCH); first DCI including first transport block (TB) information and scheduling information; scheduling information indicating multiple repeated scheduled transmissions of a physical downlink shared channel (PDSCH) TB using the first component carrier of multiple available component carriers; and encoding second DCI including at least second DCI, second TB information and second scheduling information for transmission to the UE via the PDCCH; and second scheduling information indicating additional scheduled transmissions of multiple repeated PDSCH TB using the second component carrier of multiple available component carriers.

[0137] In Example 13, the subject of Example 12 includes a subject in which the first TB information and the second TB information are associated with the TB size of each scheduled transmission and additional scheduled transmission.

[0138] Example 14 is a computer-readable storage medium that stores instructions for execution by one or more processors of a user device (UE), instructions for configuring the UE for repeated transmission of multiple component carriers in a fifth-generation new radio (5G NR) network, and instructions for causing the UE to perform operations including decoding of downlink control information (DCI) received via a physical downlink control channel (PDCCH), DCI including transport block (TB) information and scheduling information, and scheduling information indicating scheduled transmission of multiple repetitions of a physical downlink shared channel (PDSCH) TB using multiple component carriers. Using the TB information, determine the TB size associated with the scheduled transmission; decode multiple repetitions of the PDSCH TB (multiple repetitions received from one or more base stations during the scheduled transmission); and determine the PDSCH data based on the multiple repetitions of the PDSCH TB and the TB size.

[0139] In Example 15, the subject of Example 14 further includes the operation of decoding the DCI to further determine the redundant version (RV) associated with the initial transmission of the scheduled transmission.

[0140] In Example 16, the subject of Example 15 further includes the operation of determining additional RVs related to subsequent transmissions of a scheduled transmission that occurs after a subsequent transmission, based on the RV and a pre-configured RV offset applied to a pre-configured RV pattern.

[0141] In Example 17, the subject of Example 16 further includes operations to determine PDSCH data based on RV and additional RV.

[0142] In Example 18, the subject matter of Examples 14–17 further includes the operation of encoding one-shot acknowledgments (ACKs) or one-shot non-acknowledgments (NACKs) for transmission to one or more base stations using a physical uplink control channel (PUCCH), and one-shot ACKs or one-shot NACKs associated with a subset of multiple repetitions of PDSCH TBs received from one or more base stations during a scheduled transmission.

[0143] In Example 19, the subject matter of Examples 14–18 further includes the operation of decoding the DCI to further determine multiple carrier indices, and multiple carrier indices associated with the corresponding multiple transmit frequencies.

[0144] In Example 20, the subject of Example 19 further includes the operation of encoding uplink data for transmission to one or more base stations using multiple component carriers, multiple component carriers corresponding to multiple transmit frequencies, and multiple repetitions of the physical uplink shared channel (PUSCH) TB.

[0145] Example 21 is at least one machine-readable medium that, when executed by a processing circuit, contains instructions that cause the processing circuit to perform an operation that performs one of the operations in Examples 1 through 20.

[0146] Example 22 is an apparatus that includes means for carrying out any of Examples 1 to 20.

[0147] Example 23 is a system that implements any of Examples 1 through 20.

[0148] Example 24 is a method that implements one of the methods from Example 1 to 20.

[0149] While some embodiments are described with reference to specific exemplary embodiments, it will be apparent that various modifications and changes can be made to these embodiments without departing from the broader scope of this disclosure. Therefore, the specification and drawings should be considered illustrative rather than restrictive. Accordingly, this specification should not be construed restrictively, and the scope of the various embodiments is defined solely by the appended claims and all equivalents to which such claims are entitled.

Claims

1. A device for a user equipment (UE) configured to operate within a fifth-generation new wireless (5G NR) network, the device is: A processing circuit, wherein in order to configure the UE for repeated transmission of multiple component carriers within the 5G NR network, the processing circuit comprises: A single downlink control information (DCI) is received via a physical downlink control channel (PDCCH) and decoded for use for multiple component carriers and multiple iterations, wherein the single DCI includes transport block (TB) information and scheduling information, and the scheduling information indicates the scheduled transmission of the multiple iterations of the physical downlink shared channel (PDSCH) TB using the multiple component carriers. Using the TB information, determine the TB size associated with the scheduled transmission. Decode the plurality of repetitions of the PDSCH TB received from one or more base stations during the scheduled transmission, and A processing circuit is configured to determine PDSCH data based on the plurality of repetitions of the PDSCH TB and the TB size. A memory coupled to the processing circuit and configured to store the single DCI, including, Device.

2. The apparatus according to claim 1, wherein the processing circuit softly couples the plurality of repetitions of the PDSCH TB based on the TB size and determines the PDSCH data.

3. The apparatus according to claim 1, wherein the processing circuit performs selective diversity reception of the PDSCH TB of the multiple repetitions based on the TB size and determines the PDSCH data.

4. The apparatus according to claim 1, wherein the processing circuit decodes the single DCI to further determine a redundant version (RV) associated with the first transmission of the scheduled transmission.

5. The apparatus according to claim 4, wherein the processing circuit determines additional RVs related to the subsequent transmission of a scheduled transmission that occurs after the subsequent transmission, based on the RV and a pre-configured RV offset applied to a pre-configured RV pattern.

6. The apparatus according to claim 5, wherein the processing circuit further determines the PDSCH data based on the RV and the additional RV.

7. The apparatus according to claim 1, wherein the processing circuit encodes one-shot acknowledgments (ACKs) or one-shot non-acknowledgments (NACKs) for transmission to one or more base stations using a physical uplink control channel (PUCCH), the one-shot ACKs or one-shot NACKs associated with the plurality of repetitions of the PDSCH TB received from the one or more base stations during the scheduled transmission.

8. The apparatus according to claim 1, wherein the processing circuit decodes the single DCI to further determine a plurality of carrier indices associated with a plurality of corresponding transmission frequencies.

9. The apparatus according to claim 8, wherein the processing circuit encodes uplink data for transmission to one or more base stations using multiple iterations of a physical uplink shared channel (PUSCH) TB that use multiple component carriers corresponding to the multiple transmission frequencies.

10. The apparatus according to claim 9, wherein the one or more base stations include a plurality of transmit / receive points (TRPs), and the uplink data is encoded for transmission to the plurality of TRPs using the plurality of transmit frequencies.

11. The apparatus according to any one of claims 1 to 10, further comprising a transceiver circuit coupled to the processing circuit and one or more antennas coupled to the transceiver circuit.

12. A computer-readable storage medium storing instructions executed by one or more processors of a base station, which configure the base station for repeated transmission of multiple component carriers in a fifth-generation new wireless (5G NR) network, wherein the base station Encoding a single downlink control information (DCI) to be transmitted to a user device (UE) via a physical downlink control channel (PDCCH) and used for multiple component carriers and multiple iterations, wherein the single DCI includes transport block (TB) information and scheduling information, and the scheduling information indicates the scheduled transmission of the multiple iterations of the physical downlink shared channel (PDSCH) TB using the multiple component carriers, and Transmitting the encoded single DCI to the UE via the PDCCH, wherein the encoded single DCI is decoded by the UE, and the TB size associated with the scheduled transmission is determined by using the TB information. Perform an operation that includes A computer-readable storage medium.

13. The computer-readable storage medium according to claim 12, wherein the TB information is associated with the respective TB sizes of the scheduled transmission and the additional scheduled transmission.

14. A computer-readable storage medium storing instructions for execution by one or more processors of a user device (UE), for setting the UE for repeated transmission of multiple component carriers in a fifth-generation new wireless (5G NR) network, wherein the UE contains, Decoding a single downlink control information (DCI) received via a physical downlink control channel (PDCCH) and used for multiple component carriers and multiple iterations, wherein the single DCI includes transport block (TB) information and scheduling information, and the scheduling information indicates the scheduled transmission of the multiple iterations of the physical downlink shared channel (PDSCH) TB using the multiple component carriers. Using the TB information, determine the TB size associated with the scheduled transmission. Decoding the multiple repetitions of the PDSCH TB received from one or more base stations during the scheduled transmission, and Determining PDSCH data based on the multiple repetitions and TB size of the PDSCH TB, Perform an operation that includes A computer-readable storage medium.

15. The computer-readable storage medium according to claim 14, wherein the operation further decodes the single DCI to determine the redundant version (RV) associated with the first transmission of the scheduled transmission.

16. The computer-readable storage medium according to claim 15, wherein the operation determines additional RVs related to the subsequent transmission of a scheduled transmission that occurs after the subsequent transmission, based on the RV and a pre-set RV offset applied to a pre-set RV pattern.

17. The computer-readable storage medium according to claim 16, wherein the operation further determines the PDSCH data based on the RV and the additional RV.

18. The computer-readable storage medium according to any one of claims 14 to 17, wherein the operation encodes a one-shot acknowledgment (ACK) or one-shot non-acknowledgment (NACK) for transmission to one or more base stations using a physical uplink control channel (PUCCH), the one-shot ACK or one-shot NACK associated with a subset of multiple repetitions of PDSCH TB received from one or more base stations during the scheduled transmission.

19. The computer-readable storage medium according to claim 14, wherein the operation decodes the single DCI to further determine a plurality of carrier indices associated with a plurality of corresponding transmit frequencies.

20. The computer-readable storage medium according to claim 19, wherein the operation encodes uplink data for transmission to one or more base stations using multiple component carriers corresponding to the multiple transmission frequencies and multiple repetitions of a physical uplink shared channel (PUSCH) TB.

Images