Repetition for ultra-reliable low latency communications

Abstract

Embodiments include a method performed by a user equipment (UE) for communicating via a plurality of nodes in a wireless network. Such a method includes receiving a plurality of transmission configuration indication (TCI) states; and receiving, via the single physical control channel, scheduling information for the plurality of physical data channels carrying the respective plurality of repetitions of the data block. The physical data channels may be respective layers of the PDSCH, or each physical data channel may be a subset of all layers of the PDSCH. Such a method includes: assigning one or more of the TCI states to a plurality of repetitions; and receiving a plurality of repetitions via the plurality of physical data channels based on the scheduling information and the allocated TCI state. Embodiments also include supplemental methods performed by the wireless network, as well as UEs and wireless networks configured to perform such methods.

Description

[0001] Divisional Application

[0002] This application is a divisional application of the patent application with application number 202080018064.8, filing date January 3, 2020, and invention title "Repetition for Ultra-Reliable Low-Latency Communication". Technical Field

[0003] Embodiments of the present disclosure generally relate to wireless communication networks, and more particularly to performance improvements in ultra-reliable low-latency communication (URLLC) in wireless communication networks. Background Art

[0004] In general, all terms used herein will be interpreted according to their ordinary meaning in the relevant technical field, unless explicitly given a different meaning and / or a meaning different from that implied in the context in which it is used. Unless otherwise explicitly stated, all references to elements, devices, components, methods, steps, etc. will be interpreted openly as referring to at least one instance of the element, device, component, method, step, etc. The steps of any method and / or process disclosed herein are not necessarily to be executed in the exact order disclosed, unless the steps are explicitly described as after or before another step and / or it is implied that the steps must be after or before another step. Whenever appropriate, any feature of any embodiment disclosed herein can be applied to any other embodiment. Similarly, any advantage of any embodiment can be applied to any other embodiment, and vice versa. From the following description, other objects, features, and advantages of the disclosed embodiments will be apparent.

[0005] Long Term Evolution (LTE) is a general term for the so-called fourth generation (4G) radio access technology developed within the Third Generation Partnership Project (3GPP) and initially standardized in Releases 8 and 9, also known as Evolved UTRAN (E-UTRAN). LTE targets various licensed frequency bands and is accompanied by improvements in non-radio aspects commonly referred to as System Architecture Evolution (SAE), which includes the Evolved Packet Core (EPC) network. LTE continues to evolve through subsequent releases developed according to the standard-setting process regarding 3GPP and its working groups (WG) (including the Radio Access Network (RAN) WG, and sub-working groups (e.g., RAN1, RAN2, etc.)).

[0006] LTE Release 10 (Rel-10) supports bandwidths greater than 20 MHz. An important requirement for Rel-10 is to ensure backward compatibility with LTE Release-8. Thus, a wideband LTE Rel-10 carrier (e.g., wider than 20 MHz) should appear as many carriers to LTE Rel-8 (“legacy”) terminals. Each such carrier may be referred to as a component carrier (CC). For the efficient use of wide carriers also by legacy terminals, legacy terminals may be scheduled in all parts of a wideband LTE Rel-10 carrier. An exemplary way to achieve this is by means of carrier aggregation (CA), where a Rel-10 terminal may receive multiple CCs, each CC preferably having the same structure as a Rel-8 carrier. One of the enhancements in LTE Rel-11 is the enhanced physical downlink control channel (ePDCCH), which has the goals of increasing capacity and improving the spatial multiplexing of control channel resources, improving inter-cell interference coordination (ICIC), and supporting antenna beamforming and / or transmit diversity for the control channel. Additionally, LTE Rel-12 introduced dual connectivity (DC), whereby a UE may be connected to two network nodes simultaneously, thus improving connection robustness and / or capacity.

[0007] Figure 1 Fig. shows an overall exemplary architecture of a network including LTE and SAE. The E-UTRAN 100 includes one or more evolved Node Bs (eNBs), such as eNBs 105, 110, and 115, and one or more user equipments (UEs), such as UE 120. As used within the 3GPP standards, “user equipment” or “UE” means any wireless communication device (e.g., a smart phone or a computing device) capable of communicating with a 3GPP standard-compliant network device, including the E-UTRAN as well as the UTRAN and / or GERAN, as the third-generation (“3G”) and second-generation (“2G”) 3GPP radio access networks are generally well known.

[0008] As specified by 3GPP, the E-UTRAN 100 is responsible for all radio-related functions in the network, including radio bearer control, radio access control, radio mobility control, scheduling, and dynamic allocation of resources to the UE in the uplink and downlink, as well as the security of communication with the UE. These functions reside in the eNBs, such as eNBs 105, 110, and 115. The eNBs in the E-UTRAN communicate with each other via the X1 interface, as Figure 1 shown. The eNBs are also responsible for the E-UTRAN interfaces to the EPC 130, in particular for the S1 interfaces to the mobility management entity (MME) and the serving gateway (SGW), shown together as Figure 1The MME / S-GWs 134 and 138 in it. Generally speaking, the MME / S-GW handles the overall control of the data flow between the UE and the rest of the EPC. More particularly, the MME processes the signaling (e.g., control plane) protocol between the UE and the EPC, which is called the non-access stratum (NAS) protocol. The S-GW processes all Internet Protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC, and serves as a local mobility anchor for data bearers when the UE moves between multiple eNBs (such as eNBs 105, 110, and 115).

[0009] The EPC 130 may also include a Home Subscriber Server (HSS) 131, which manages user-related information and subscriber-related information. The HSS 131 may also provide support functions in mobile management, call and session setup, user authentication, and access authorization. The functions of the HSS 131 may be related to the functions of a traditional Home Location Register (HLR) and an Authentication Center (AuC) or operations.

[0010] In some embodiments, the HSS 131 may communicate with a User Data Repository (UDR) (the EPC-UDR 135 labeled in Figure 1 via the Ud interface. The EPC-UDR 135 may store user credentials after they have been encrypted by AuC algorithms. These algorithms are not standardized (i.e., are vendor-specific), such that the encrypted credentials stored in the EPC-UDR 135 cannot be accessed by any other vendor except the vendor of the HSS 131.

[0011] Figure 2A A high-level block diagram of an exemplary LTE architecture is shown in terms of its constituent entities - UE, E-UTRAN, and EPC - and the high-level functional partitioning into the access stratum (AS) and non-access stratum (NAS). Figure 2A Also shown are two specific interface points, namely, Uu (UE / E-UTRAN radio interface) and S1 (E-UTRAN / EPC interface), each using a specific set of protocols (i.e., radio protocols and S1 protocols). Although not shown in Figure 2A each protocol set in the protocol set may also be split into user plane and control plane protocol functions. The user and control planes are also referred to as the U plane and C plane, respectively. On the Uu interface, the U plane carries user information (e.g., data packets), while the C plane carries control information between the UE and the E-UTRAN.

[0012] Figure 2BA block diagram showing an exemplary C-plane protocol stack among a UE, an eNB, and an MME is shown. The exemplary protocol stack includes Physical (PHY), Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC) layers between the UE and the eNB. The PHY layer is concerned with how and what characteristics are used to transmit data over the transport channel on the LTE radio interface. The MAC layer provides data transfer services on the logical channel, maps the logical channel to the PHY transport channel, and reallocates PHY resources to support these services. The RLC layer provides error detection and / or correction, concatenation, segmentation, and reassembly, reordering of data transmitted to or from the upper layer. The PHY, MAC, and RLC layers perform the same functions for both the U-plane and the C-plane. The PDCP layer provides encryption / decryption and integrity protection for both the U-plane and the C-plane, and provides other functions for the U-plane, such as header compression. The exemplary protocol stack also includes non-access stratum (NAS) signaling between the UE and the MME.

[0013] Figure 2C A block diagram showing an exemplary LTE radio interface protocol architecture from the perspective of the PHY layer is shown. The interfaces between the layers are provided by service access points (SAPs), which are indicated by the Figure 2C ellipses in the figure. The PHY layer interfaces with the MAC and RRC protocol layers described above. The PHY, MAC, and RRC are also respectively referred to as layers 1-3 in the figure. The MAC provides different logical channels to the RLC protocol layer (also as described above), characterized by the type of information to be transmitted, while the PHY provides the transport channel to the MAC, characterized by how the information is transmitted over the radio interface. In providing this transport service, the PHY performs various functions, including: error detection and correction; rate matching of the coded transport channel and mapping the coded transport channel to the physical channel; power weighting, modulation, and demodulation of the physical channel; transmit diversity; and beamforming multiple-input multiple-output (MIMO) antenna processing. The PHY layer also receives control information (e.g., commands) from the RRC and provides various information to the RRC, such as radio measurement results.

[0014] The RRC layer controls the communication between the UE and the eNB at the radio interface and the mobility of the UE between cells in the E-UTRAN. After the UE powers on, it will be in the RRC_IDLE state until an RRC connection is established with the network, at which time the UE will transition to the RRC_CONNECTED state (where data transfer can occur). The UE returns to RRC_IDLE after the connection to the network is released. In the RRC_IDLE state, the UE's radio is active on a discontinuous reception (DRX) schedule configured by the upper layer. During the DRX active period (also known as the "On duration"), the RRC_IDLE UE receives the system information (SI) broadcast by the serving cell, performs measurements on neighboring cells to support cell reselection, and monitors paging from the EPC via the eNB on the paging channel on the PDCCH. The RRC_IDLE UE is known in the EPC and has an assigned IP address, but is unknown to the serving eNB (e.g., there is no stored context).

[0015] Generally speaking, a physical channel corresponds to a set of resource elements that carry information originating from a higher layer. The downlink (i.e., eNB to UE) physical channels provided by the LTE PHY include the Physical Downlink Shared Channel (PDSCH), the Physical Multicast Channel (PMCH), the Physical Downlink Control Channel (PDCCH), the Relay Physical Downlink Control Channel (R-PDCCH), the Physical Broadcast Channel (PBCH), the Physical Control Format Indicator Channel (PCFICH), and the Physical Hybrid ARQ Indicator Channel (PHICH). Additionally, the LTE PHY downlink includes various reference signals, synchronization signals, and discovery signals.

[0016] The PBCH carries the basic system information required by the UE to access the network. The PDSCH is the main physical channel for unicast DL data transfer and is also used for the transmission of RAR (Random Access Response), certain system information blocks, and paging information. The PHICH carries HARQ feedback (e.g., ACK / NAK) for UL transmissions made by the UE. Similarly, the PDCCH carries DL scheduling assignments (e.g., for the PDSCH), UL resource grants (e.g., for the PUSCH), channel quality feedback for UL channels (e.g., CSI), and other control information.

[0017] The uplink (i.e., UE to eNB) physical channels provided by the LTE PHY include the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Physical Random Access Channel (PRACH). Additionally, the LTE PHY uplink includes various reference signals, including: the Demodulation Reference Signal (DM-RS), which is transmitted to assist the eNB in the reception of the associated PUCCH or PUSCH; and the Sounding Reference Signal (SRS), which is not associated with any uplink channel.

[0018] The PRACH is used for random access preamble transmission. The PUSCH is the counterpart of the PDSCH and is mainly used for individual UL data transmission. Similar to the PDCCH, the PUCCH carries uplink control information (UCI), such as a scheduling request, CSI for DL channels, HARQ feedback for eNB DL transmission, and other control information.

[0019] The multiple access schemes for the LTE PHY are based on Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) in the downlink and Single Carrier Frequency Division Multiple Access (SC-FDMA) with a cyclic prefix in the uplink. To support transmissions in paired and unpaired spectrums, the LTE PHY supports both Frequency Division Duplexing (FDD) (including both full-duplex operation and half-duplex operation) and Time Division Duplexing (TDD). Figure 3A An exemplary radio frame structure (“Type 1”) for LTE FDD downlink (DL) operation is shown. The DL radio frame has a fixed duration of 10 ms and includes 20 time slots labeled from 0 to 19, each time slot having a fixed duration of 0.5 ms. A 1-ms subframe includes two consecutive time slots, where subframe i includes time slots 2i and 2i + 1. Each exemplary FDD DL time slot includes N DL symb OFDM symbols, and each of these OFDM symbols includes N sc OFDM subcarriers. Exemplary values of N DL symb for a subcarrier spacing (SCS) of 15 kHz can be 7 (with normal CP) or 6 (with extended CP). The value of N sc is configurable based on the available channel bandwidth. Since those of ordinary skill in the art are familiar with the principles of OFDM, further details are omitted in this specification.

[0020] As Figure 3AAs shown, a combination of specific subcarriers in a specific symbol is referred to as a resource element (RE). Each RE is used to transmit a specific number of bits depending on the type of modulation and / or bit mapping constellation used for that RE. For example, some REs may carry two bits using QPSK modulation, while other REs may carry four or six bits using 16-QAM or 64-QAM respectively. The radio resources of LTE PHY are also defined in terms of physical resource blocks (PRBs). A PRB spans N DL symb symbols during the duration of a time slot, i.e., N RB sc subcarriers, where N RB sc is typically 12 (with a 15-kHz subcarrier bandwidth) or 24 (7.5-kHz bandwidth). A PRB that spans the same N DL symb subcarriers during the entire subframe (i.e., 2N RB sc symbols) is referred to as a PRB pair. Thus, the resources available in a subframe of LTE PHY DL include N DL RB PRB pairs, each of which includes 2N DL symb ·N RB sc REs. For normal CP and 15-KHz SCS, a PRB pair includes 168 REs.

[0021] An exemplary characteristic of a PRB is that consecutively numbered PRBs (e.g., PRB i and PRB i+1 ) include consecutive blocks of subcarriers. For example, in the case of normal CP and a 15-KHz subcarrier bandwidth, PRB0 includes subcarriers 0 to 11, while PRB1 includes subcarriers 12 to 23. LTE PHY resources can also be defined in terms of virtual resource blocks (VRBs), which are the same size as PRBs but have a localized or distributed type. Localized VRBs can be directly mapped to PRBs such that VRBn VRB corresponds to PRBn PRB = n VRB . On the other hand, distributed VRBs can be mapped to non-consecutive PRBs according to various rules, as described in 3GPP Technical Specification (TS) 36.213 or otherwise known to those of ordinary skill in the art. However, the term "PRB" should be used in this disclosure to refer to both physical and virtual resource blocks. Additionally, unless otherwise specified, the term "PRB" will thus be used to refer to the resource block for the duration of a subframe, i.e., a PRB pair.

[0022] Figure 3B illustrates an exemplary LTE FDD uplink (UL) radio frame configured in a manner similar to the exemplary FDD DL radio frame shown Figure 3A Using techniques consistent with the above DL description, each UL time slot includes N UL symb OFDM symbols, each of which includes N sc OFDM subcarriers.

[0023] As discussed above, the LTE PHY maps the various DL and UL physical channels to resources as shown in Figure 3A and Figure 3B respectively. For example, the PHICH carries HARQ feedback (e.g., ACK / NAK) for UL transmissions made by the UE. Similarly, the PDCCH carries scheduling assignments, channel quality feedback for UL channels (e.g., CSI), and other control information. Likewise, the PUCCH carries uplink control information such as scheduling requests, CSI for downlink channels, HARQ feedback for eNB DL transmissions, and other control information. Both the PDCCH and the PUCCH can be transmitted on an aggregation of one or more consecutive control channel elements (CCEs), and the CCEs are mapped to physical resources based on resource element groups (REGs), each of which includes multiple resource elements (REs). For example, a CCE can include nine (9) REGs, where each REG can include four (4) REs.

[0024] Figure 4 illustrates an exemplary manner in which CCEs and REGs can be mapped to physical resources (e.g., PRBs). As Figure 4 shown, the REGs of the CCEs including the PDCCH can be mapped to the first three symbols of a subframe, while the remaining symbols can be used for other physical channels such as the PDSCH carrying user data. In the exemplary arrangement of Figure 4 , each of the REGs includes four REs, which are represented by small dashed rectangles. Although Figure 4 shows two CCEs, the number of CCEs can vary depending on the required PDCCH capacity, which can be based on the number of users, the amount of measurements, and / or control signaling, etc. On the uplink, the PUCCH can be configured similarly.

[0025] In LTE, DL transmissions are dynamically scheduled, i.e., in each subframe, the base station transmits control information indicating the terminals to which data is to be sent in the current downlink subframe and on which resource blocks the data is to be sent. This control signaling is typically sent in the first n OFDM symbols in each subframe, and the number n (= 1, 2, 3, or 4) is referred to as the control format indicator (CFI) indicated by the PCFICH in the first symbol of the control region.

[0026] While LTE is mainly designed for user-to-user communication, 5G (also known as "NR") cellular networks are envisioned to support both high single-user data rates (e.g., 1 Gb / s) and massive machine-to-machine communication involving short burst transmissions from multiple different devices sharing a frequency bandwidth. The 5G radio standard (also known as "New Radio" or "NR") currently targets a variety of data services, including eMBB (enhanced mobile broadband), URLLC (ultra-reliable low-latency communication), and machine type communication (MTC). These services can have different requirements and goals. For example, URLLC aims to provide data services with extremely strict error and latency requirements, e.g., an error probability as low or lower than -5 10 and an end-to-end latency of 1 ms or less.

[0027] Similar to LTE, NR uses CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) in the downlink and CP-OFDM and DFT-spread OFDM (DFT-S-OFDM) in the uplink. In the time domain, the NR downlink and uplink physical resources are each organized into 1-ms equal-sized subframes. The subframes are also divided into multiple time slots of equal duration, where each time slot includes multiple OFDM-based symbols. NR also shares various other features of LTE discussed above.

[0028] For NR Rel-16, support for multi-source transmission of PDSCH to UEs has been discussed. In this context, "source" can refer to beams, panels, transmit / receive points (TRPs), etc. For example, to support URLLC, it may be beneficial to send multiple versions of a transport block (TB) of data from different TRPs to a UE. This requires scheduling multiple PDSCHs to the same UE, which requires the UE to use the scheduling information for the corresponding PDSCHs to correctly decode multiple PDCCHs. Multiple PDCCHs for a single UE can increase UE complexity and also consume more control channel resources, which reduces the flexibility for scheduling other UEs within the same time slot and / or increases the PDCCH blocking probability. These effects are undesirable. Summary of the Invention

[0029] Embodiments of the present disclosure provide certain improvements to communication between a user equipment (UE) and a network node in a wireless communication network, such as through technical solutions that help overcome the exemplary problems described above.

[0030] Some exemplary embodiments of the present disclosure include methods (e.g., procedures) for communicating via multiple nodes in a wireless network. These exemplary methods may be performed by a user equipment (UE, e.g., a wireless device, an IoT device, a modem, etc., or components thereof) communicating with one or more network nodes (e.g., a base station, a gNB, an en-gNB, etc., or components thereof) in a wireless network (e.g., E-UTRAN, NG-RAN).

[0031] These exemplary methods may include: receiving, from a wireless network, a plurality of transmission configuration indication (TCI) states. In some embodiments, the plurality of TCI states may be associated with one of the following: a corresponding plurality of nodes in the wireless network; or a corresponding plurality of beams associated with one or more nodes in the wireless network.

[0032] These exemplary methods may further include: receiving, via a single physical control channel, scheduling information for a corresponding plurality of physical data channels carrying respective repetitions of a data block. For example, the physical control channel may be a PDCCH, and the scheduling information may be scheduling DCI, as discussed above. In some embodiments, the plurality of physical data channels may be respective layers of a physical downlink shared channel (PDSCH). In other embodiments, each physical data channel may be a subset of all layers of the PDSCH.

[0033] In some embodiments, the scheduling information may further include an indicator for a resource for receiving one or more of the repetitions. The indicated resource may be in at least one of the following dimensions: time, frequency, and spatial layer. In some embodiments, the resources for at least two of the repetitions may be in the same symbol set within a time slot.

[0034] In other embodiments, the scheduling information may include an indicator for a first resource for receiving a first repetition of the repetitions. In such embodiments, these exemplary methods may further include receiving one or more offsets to be applied to the first resource to determine other resources for receiving the remaining repetitions of the repetitions. In such embodiments, the other resources may be in one of the following: one or more subsequent time slots relative to the first resource, or one or more subsequent symbols within the same time slot relative to the first resource.

[0035] In some embodiments, the indicated resources for at least two of the repetitions may be fully frequency-overlapped. In such embodiments, the scheduling information further includes at least one of the following items for each of the fully overlapped repetitions: a unique set of demodulation reference signal (DMRS) ports; DMRS ports from a unique code division multiplexing (CDM) group; and a unique data scrambling seed.

[0036] In some embodiments, the scheduling information may further include an indicator of the mapping between the multiple repetitions and multiple redundant versions (RVs) of a data block.

[0037] These exemplary methods may further include assigning one or more of the TCI states to the multiple repetitions. In some embodiments, the multiple TCI states are less than the multiple repetitions, and the multiple TCI states are assigned to the repetitions in a predefined order. In other embodiments, the scheduling information may further include an indicator of the mapping between one or more of the TCI states and the multiple repetitions. In such embodiments, one or more of the TCI states are assigned to the repetitions based on the indicated mapping. In some of these embodiments, the indicator is included in a field having multiple code points, and the multiple TCI states are less than the multiple code points. In such embodiments, a first subset of the code points may be associated with individual TCI states, and a second subset of the code points may be associated with combinations of individual TCI states.

[0038] In some embodiments, each TCI state includes one or more source reference signal (RS) pairs, wherein each source RS pair has a corresponding quasi-co-location (QCL) relationship pair for the DM-RS mapped to a specific physical data channel. In such embodiments, these exemplary methods may further include: for each of the multiple TCI states, determining channel parameters based on the source RS pairs included in the specific TCI state.

[0039] These exemplary methods may further include: receiving the multiple repetitions via multiple physical data channels based on the scheduling information and the assigned TCI states. In some embodiments, for each of the physical data channels, these operations may include the following: receiving the DM-RS mapped to the physical data channel based on the channel parameters (e.g., determined for the source RS pairs); determining further channel parameters based on the received DM-RS; and receiving the physical data channel based on the further channel parameters.

[0040] Other exemplary embodiments include methods (e.g., procedures) for communicating with a single user equipment (UE) via multiple physical data channels. These exemplary methods may be performed by one or more network nodes (e.g., base stations, eNBs, gNBs, en-gNBs, etc. or their components) of a radio network (e.g., NG-RAN, E-UTRAN).

[0041] These exemplary methods may include: sending a plurality of transmission configuration indication (TCI) states to the UE. In some embodiments, the plurality of TCI states may be associated with one of the following: a corresponding plurality of nodes in the radio network; or a corresponding plurality of beams associated with one or more nodes in the radio network.

[0042] These exemplary methods may further include: assigning one or more of the TCI states to a plurality of repetitions of data blocks to be carried by the corresponding plurality of physical data channels. In some embodiments, the plurality of TCI states may be less than the plurality of repetitions, and the plurality of TCI states may be assigned to the repetitions in a predefined order. The UE may also know the predefined order and assign the TCI states to the repetitions in a corresponding manner.

[0043] These exemplary methods may further include: sending scheduling information for the corresponding plurality of physical data channels carrying data blocks via a single physical control channel. In some embodiments, the plurality of physical data channels may be respective layers of a physical downlink shared channel (PDSCH). In other embodiments, each physical data channel may be a subset of all layers of the PDSCH.

[0044] In some embodiments, the scheduling information may further include an indicator for resources for receiving one or more of the repetitions. The indicated resources may be in at least one of the following dimensions: time, frequency, and spatial layer. In some embodiments, the resources for at least two of the repetitions may be in the same symbol set within a time slot.

[0045] In other embodiments, the scheduling information may include an indicator for a first resource for receiving a first repetition of the repetitions. In such embodiments, these exemplary methods may further include sending one or more offsets to be applied to the first resource to determine other resources for receiving the remaining repetitions of the repetitions. In such embodiments, the other resources may be in one of the following: one or more subsequent time slots relative to the first resource, or one or more subsequent symbols within the same time slot relative to the first resource.

[0046] In some embodiments, the indicated resources for at least two repetitions among repetitions may completely overlap in frequency. In such embodiments, the scheduling information may further include at least one of the following items for each of the repetitions that completely overlap: a unique set of demodulation reference signal (DMRS) ports; DMRS ports from a unique code division multiplexing (CDM) group; and a unique data scrambling seed.

[0047] In some embodiments, the scheduling information may further include an indicator of the mapping between multiple repetitions and multiple redundant versions (RVs) of a data block.

[0048] In some embodiments, the scheduling information may further include an indicator of the mapping between one or more transmit configuration indicator (TCI) states among TCI states and multiple repetitions. For example, the mapping may reflect and / or indicate the assignment of TCI states to repetitions. In some of these embodiments, the indicator is included in a field having multiple code points, and the multiple TCI states are less than the multiple code points. In such embodiments, a first subset of the code points may be associated with individual TCI states, and a second subset of the code points may be associated with combinations of individual TCI states.

[0049] In some embodiments, each TCI state may include one or more pairs of source reference signals (RSs), where each source RS pair has a corresponding quasi co-location (QCL) relationship pair for a DM-RS with an antenna port, and the DM-RS is mapped to a specific physical data channel. In such embodiments, these exemplary methods may further include: for each of the multiple TCI states, transmitting the source RS pairs included in the specific TCI state.

[0050] These exemplary methods may further include: transmitting multiple repetitions via multiple physical data channels based on the scheduling information and the assigned TCI states. In some embodiments, these operations may include transmitting the corresponding DM-RS associated with the physical data channel to which they are mapped. This may facilitate the UE to receive the target RS (e.g., DM-RS) associated with a specific physical data channel by using the source RS pairs and the QCL relationships.

[0051] Other exemplary embodiments include a wireless network that includes one or more network nodes (e.g., base stations, eNBs, gNBs, CU / DUs, TRPs, controllers, etc.) and a user equipment (UE, e.g., a wireless device, an IoT device, or a component thereof, such as a modem), and the user equipment is configured to perform operations corresponding to any of the exemplary methods described herein. Other exemplary embodiments include a non-transitory computer-readable medium storing program instructions that, when executed by a processing circuit, configure such a wireless network or UE to perform operations corresponding to any of the exemplary methods described herein.

[0052] In view of the accompanying drawings briefly described below, these and other objects, features, and advantages of the embodiments of the present disclosure will become apparent after reading the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 is a high-level block diagram of an exemplary architecture of a Long-Term Evolution (LTE) evolved UTRAN (E-UTRAN) and an evolved packet core (EPC) network standardized by 3GPP.

[0054] Figure 2A is a high-level block diagram of an exemplary E-UTRAN architecture in terms of its constituent components, protocols, and interfaces.

[0055] Figure 2B is a block diagram of an exemplary protocol layer of the control plane portion of the radio (Uu) interface between a user equipment (UE) and the E-UTRAN.

[0056] Figure 2C is a block diagram of an exemplary LTE radio interface protocol architecture from the perspective of the PHY layer.

[0057] Figure 3A and Figure 3B are block diagrams of exemplary downlink and uplink LTE radio frame structures for frequency division duplex (FDD) operation, respectively.

[0058] Figure 4 illustrates an exemplary manner in which CCEs and REGs can be mapped to physical resources.

[0059] Figure 5 illustrates an exemplary time-frequency resource grid for an NR time slot.

[0060] Figures 6A to 6B illustrates various exemplary NR time slot configurations.

[0061] Figure 7 illustrates a high-level view of a 5G network architecture.

[0062] FIG. 8 (which includes Figures 8A to 8D ) illustrates four exemplary mappings of the preamble demodulation reference signal (DM-RS).

[0063] Figures 9 to 10 illustrates a flowchart of an exemplary operation scenario according to various exemplary embodiments of the present disclosure, in which a UE communicates with two gNBs that can provide PDSCH diversity transmission.

[0064] Figure 11A flowchart of an exemplary method (e.g., process) performed by a user equipment (UE, e.g., a wireless device, an IoT device, etc.) according to various exemplary embodiments of the present disclosure is shown.

[0065] Figure 12 A flowchart of an exemplary method (e.g., process) performed by a wireless network including one or more nodes (e.g., a base station, a gNB, an eNB, an en-gNB, etc.) according to various exemplary embodiments of the present disclosure is shown.

[0066] Figure 13 A block diagram of an exemplary wireless device or UE according to various exemplary embodiments of the present disclosure.

[0067] Figure 14 A block diagram of an exemplary network node according to various exemplary embodiments of the present disclosure.

[0068] Figure 15 A block diagram of an exemplary network configured to provide an over-the-top (OTT) data service between a host computer and a UE according to various exemplary embodiments of the present disclosure.

[0069] Figure 16 Shows various exemplary arrangements showing PDSCH repetitions based on time slots, mini-slots, frequencies, and layers according to various exemplary embodiments of the present disclosure. Detailed Description

[0070] Some embodiments of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example only to convey the scope of the subject matter to those skilled in the art. Additionally, the various terms discussed below will be used throughout the application.

[0071] The term "network node" as used herein can be any type of network node included in a radio network, which can also include any one of the following: base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node (such as MSR BS), multi-cell / multicast coordination entity (MCE), relay node, donor node controlled relay, radio access point (AP), transmission point, transmission node, remote radio unit (RRU), remote radio head (RRH), core network node (e.g., mobility management entity (MME), self-organizing network (SON) node, coordination node, positioning node, MDT node, etc.), external node (e.g., third-party node, node external to the current network), node in a distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS), etc. The network node can also include test equipment. The term "radio node" as used herein can also be used to denote a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0072] The term "radio network node" can refer to any type of network node, which can include any type of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), relay node, access point, radio access point, remote radio unit (RRU), remote radio head (RRH), integrated access backhaul (IAB) node, etc.

[0073] In some embodiments, a TRP can be associated with a network node or a radio network node. In some embodiments, a multi-TRP scenario can include multiple TRPs associated with one or more network nodes.

[0074] Unless otherwise stated, the terms "wireless device" (or simply "WD") and "user equipment" (or simply "UE") may be used interchangeably. A WD can be any type of wireless device capable of communicating with a network node or another WD via radio signals, such as a wireless device (WD). A WD can also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine type WD or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, a narrowband IoT (NB-IoT) device, an aerial device (e.g., a drone), a ProSe UE, a V2V UE, a V2X UE, etc.

[0075] Unless otherwise stated, the functions described herein, as performed by a network node or a UE, may be distributed over multiple network nodes or UEs. In other words, it should be anticipated that the functions of the network nodes and UEs described herein are not limited to being performed by a single physical device and, in fact, may be distributed among multiple physical devices.

[0076] Unless otherwise stated, the term "time resource" may correspond to any type of physical resource or radio resource expressed in terms of a time length or a time interval or a duration. In some embodiments, the term "time slot" is used to indicate a radio resource; however, it should be understood that the techniques described herein may be advantageously used with other types of radio resources, such as any type of physical resource or radio resource expressed in terms of a time length. Examples of time resources are: symbols, time slots, mini-slots, sub-frames, radio frames, transmission time intervals (TTIs), interleaving times, time resource numbers, etc.

[0077] Unless otherwise stated, the term "TTI" may correspond to any time period (e.g., during a TTI) during which a physical channel may be encoded and interleaved for transmission. The physical channel may be decoded by a receiver during the same time period (T0) in which it is encoded. A TTI may also be used interchangeably with a short TTI (sTTI), a transmission time, a time slot, a sub-time slot, a mini-slot, a short sub-frame (SSF), a mini-sub-frame, etc.

[0078] In some embodiments, a transmitter (e.g., a network node) and a receiver (e.g., a WD) may have a common pre-determined understanding of (one or more) rules for determining which resources are allocated for the transmission and / or reception of one or more physical channels. In some embodiments, such rules may be referred to as "mapping". In other embodiments, the term "mapping" may have other meanings.

[0079] Unless otherwise stated, the term "channel" may refer to a logical, transport, or physical channel. A channel may include one or more carriers and / or be arranged on one or more carriers, e.g., multiple subcarriers. A channel that carries and / or is used to carry control signaling / control information may be considered a control channel, e.g., if it is a physical layer channel and / or if it carries control plane information. Similarly, a channel that carries - and / or is used to carry - data signaling / user information may be considered a data channel (e.g., PDSCH), particularly if it is a physical layer channel and / or if it carries user plane (UP) information. A channel may be defined for a specific communication direction or for two complementary communication directions (e.g., UL and DL, or sidelink in both directions), in which case it may be considered to have two component channels, one for each direction.

[0080] Although embodiments may be described below in the context of a downlink (DL) channel (e.g., PDSCH), it should be understood that the principles based on such embodiments may also apply to other channels, e.g., other DL channels and / or certain uplink channels (e.g., PUSCH).

[0081] Although the term "cell" is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used in place of cells, and as such, the concepts described herein apply equally to both cells and beams.

[0082] Although terms from one or more specific wireless systems (e.g., LTE and / or NR) may be used herein, this should not be construed as limiting the scope of the present disclosure to those specific wireless systems. Other wireless systems, including Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from the principles and / or embodiments of the present disclosure.

[0083] As briefly mentioned above, for NR Rel-16, support for multi-source transmission of PDSCH to a UE has been discussed. In this context, the term "source" may refer to a beam, panel, transmit / receive point (TRP), etc. For example, to support URLLC, it may be beneficial to send multiple versions of a transport block (TB) from different TRPs to a UE, also known as "multi-TRP diversity". This requires scheduling multiple PDSCHs to the same UE. However, this increases UE complexity because the UE needs to correctly decode multiple PDCCHs in order to receive multiple PDSCHs to benefit from the multi-TRP diversity of the transmission. Multiple PDCCHs for a single UE also reduce the flexibility for scheduling other UEs in the same time slot and / or increase the PDCCH blocking probability. These issues are discussed in more detail below.

[0084] In Rel-15 NR, a UE can be configured with up to four carrier bandwidth parts (BWPs) in the downlink (DL), where a single DL carrier BWP is active at a given time. The UE can also be configured with up to four uplink (UL) carrier BWPs, where a single UL carrier BWP is active at a given time. If the UE is configured with supplementary UL, the UE can be configured with up to four additional carrier BWPs in supplementary UL, where a single supplementary UL carrier BWP is active at a given time.

[0085] Figure 5 An exemplary time-frequency resource grid for an NR time slot is shown. As Figure 5 shown, a resource block (RB) consists of a set of 12 consecutive OFDM subcarriers for the duration of a time slot with 14 symbols. As in LTE, a resource element (RE) consists of one subcarrier in a time slot. The common resource blocks (CRBs) are numbered from 0 to the end of the system bandwidth. Each BWP configured for the UE has a common reference of CRB 0 such that a specifically configured BWP can start at a CRB greater than zero. In this way, the UE can be configured with narrow BWPs (e.g., 10 MHz) and wide BWPs (e.g., 100 MHz) each starting at a specific CRB, but only one BWP can be active for the UE at a given time point.

[0086] Within a BWP, the RBs are defined in the frequency domain and numbered from 0 to where i is the index of the specific BWP for the carrier. Similar to LTE, each NR resource element (RE) corresponds to one OFDM subcarrier during one OFDM symbol interval. NR supports various SCS values Δf = (15 × 2 μ ) kHz, where μ ∈ (0, 1, 2, 3, 4) is called the "parameter set". The parameter set μ = 0 (i.e., Δf = 15 kHz) provides the basic (or reference) SCS also used in LTE. According to 1 / 2 μ ms, the time slot length is inversely proportional to the SCS or the parameter set. For example, for Δf = 15 kHz, there is one (1-ms) time slot per subframe, and for Δf = 30 kHz, there are two 0.5-ms time slots per subframe, and so on. Additionally, according to 2 μ × 180 kHz, the RB bandwidth is directly related to the parameter set.

[0087] Table 1 below outlines the supported NR parameter sets and associated parameters. Different DL and UL parameter sets can be configured by the network.

[0088] Table 1.

[0089]

[0090]

[0091] An NR time slot may include 14 OFDM symbols for a normal cyclic prefix and 12 symbols for an extended cyclic prefix. Figure 6A An exemplary NR time slot configuration including 14 symbols is shown, where the time slot and symbol durations are denoted as T s and T symb . Additionally, NR includes Type-B scheduling, also known as "mini-slots". These are shorter than time slots, typically ranging from one symbol to up to fewer symbols than the number of symbols in a time slot (e.g., 13 or 11), and can start at any symbol of a time slot. Mini-slots can be used if the transmission duration of a time slot is too long and / or the start of the occurrence of the next time slot (time slot alignment) is too late. Applications of mini-slots include unlicensed spectrum and latency-critical transmissions (e.g., URLLC). However, mini-slots are not service-specific and can also be used for eMBB or other services.

[0092] Figure 6B Another exemplary NR time slot structure including 14 symbols is shown. In this arrangement, the PDCCH is limited to an area containing a specific number of symbols and a specific number of subcarriers, called a control resource set (CORESET). In Figure 6B the exemplary structure shown, the first two symbols contain the PDCCH, and each of the remaining 12 symbols contains a physical data channel (PDCH), i.e., PDSCH or PUSCH. However, depending on the specific CORESET configuration, the first two time slots can also carry PDSCH or other information as needed.

[0093] A CORESET includes multiple RBs in the frequency domain (i.e., a multiple of 12 REs) and 1 - 3 OFDM symbols in the time domain, as further defined in 3GPP TS 38.211 §7.3.2.2. A CORESET is functionally similar to the control region in an LTE subframe, such as Figure 4 shown. However, in NR, each REG includes all 12 REs of one OFDM symbol in an RB, while an LTE REG only includes four REs, as Figure 4 shown. Similar to LTE, the CORESET time domain size can be indicated by the PCFICH. In LTE, the frequency bandwidth of the control region is fixed (i.e., for the total system bandwidth), while in NR, the frequency bandwidth of the CORESET is variable. The CORESET resources can be indicated to the UE via RRC signaling.

[0094] The smallest unit used to define a CORESET is a REG, which spans one PRB in frequency and one OFDM symbol in time. Except for the PDCCH, each REG contains a Demodulation Reference Signal (DM-RS) to assist in the estimation of the radio channel over which the REG is transmitted. When transmitting the PDCCH, a precoder can be used to apply weights at the transmit antennas based on some knowledge of the radio channel before transmission. If the precoders used at the transmitter for the REGs are not different, it is possible to improve the channel estimation performance at the UE by estimating the channels over multiple REGs that are approximately the same in terms of time and frequency. To assist the UE in channel estimation, multiple REGs can be grouped together to form a REG bundle, and the REG bundle size (i.e., 2, 3, or 6 REGs) for the CORESET can be indicated to the UE. The UE can assume that any precoder used for the transmission of the PDCCH is the same for all REGs in the REG bundle.

[0095] An NR Control Channel Element (CCE) consists of six REGs. These REGs can be contiguous or distributed in frequency. When the REGs are distributed in frequency, the CORESET is said to use an interleaved mapping of REGs to CCEs, while if the REGs are contiguous in frequency, a non-interleaved mapping is said to be used. Interleaving can provide frequency diversity. For cases where knowledge of the channel allows the use of a precoder in a specific part of the spectrum to improve the SINR at the receiver, not using interleaving is beneficial.

[0096] Similar to LTE, NR data scheduling can be done dynamically on a per-slot basis. In each slot, the base station (e.g., gNB) sends Downlink Control Information (DCI) via the PDCCH, which indicates which UE is scheduled to receive data in that slot and which RBs will carry that data. The UE first detects and decodes the DCI, and if the DCI includes DL scheduling information for the UE, it receives the corresponding PDSCH based on the DL scheduling information. DCI formats 1_0 and 1_1 are used to convey PDSCH scheduling.

[0097] Similarly, the DCI on the PDCCH can include a UL grant, which indicates which UE is scheduled to transmit data on the PUCCH in that slot and which RBs will carry that data. The UE first detects and decodes the DCI, and if the DCI includes an uplink grant for the UE, it transmits the corresponding PUSCH on the resources indicated by the UL grant. DCI formats 0_0 and 0_1 are used to convey the UL grant for the PUSCH, while other DCI formats (2_0, 2_1, 2_2, and 2_3) are used for other purposes, including the transmission of slot format information, reserved resources, transmit power control information, etc.

[0098] The DCI includes a payload supplemented with a Cyclic Redundancy Check (CRC) of the payload data. Since the DCI is transmitted on the PDCCH received by multiple UEs, the identifier of the target UE needs to be included. In NR, this is done by scrambling the CRC with the Radio Network Temporary Identifier (RNTI) assigned to the UE. Most commonly, the Cell RNTI (C-RNTI) assigned to the target UE by the serving cell is used for this purpose.

[0099] The DCI payload together with the identifier-scrambled CRC is encoded and transmitted on the PDCCH. Given a previously configured search space, each UE attempts to detect the PDCCH addressed to it based on multiple hypotheses (also known as "candidates") in a process called "blind decoding". PDCCH candidates can span 1, 2, 4, 8, or 16 Control Channel Elements (CCEs), where the number of CCEs is called the Aggregation Level (AL) of the PDCCH candidate. If more than one CCE is used, the information in the first CCE is repeated in the other CCEs. By varying the AL, the PDCCH can be made more or less robust to a particular payload size. In other words, PDCCH link adaptation can be performed by adjusting the AL. Depending on the AL, the PDCCH candidate can be located at multiple time-frequency positions within the CORESET.

[0100] After the UE decodes the DCI, it descrambles the CRC using the (one or more) RNTIs assigned to it and / or associated with a particular PDCCH search space. In the case of a match, the UE considers the detected DCI to be addressed to it and follows the instructions (e.g., scheduling information) in the DCI.

[0101] A hash function can be used to determine the CCEs corresponding to the PDCCH candidates that a UE must monitor within a set of search spaces. Hashing is done differently for different UEs so that the CCEs used by a UE are randomized, thus reducing the probability of collisions between multiple UEs whose PDCCH messages are included in the CORESET. The monitoring periodicity is also configured for different PDCCH candidates. In any particular time slot, a UE can be configured to monitor multiple PDCCH candidates in multiple search spaces that can be mapped to one or more CORESETs. The PDCCH candidates may need to be monitored multiple times within a time slot, once per time slot or multiple times per time slot.

[0102] The DCI may also include information on various timing offsets (e.g., in terms of time slots or sub - frames) between the PDCCH and the PDSCH, PUSCH, HARQ, and / or CSI - RS. For example, the offset K0 represents the number of time slots between the PDCCH reception of the PDSCH scheduling DCI (e.g., format 1_0 or 1_1) for the UE and the subsequent PDSCH transmission. Similarly, the offset K1 represents the number of time slots between this PDSCH transmission and the responsive HARQ ACK / NACK transmission on the PUSCH by the UE. Additionally, the offset K3 represents the number of time slots between this responsive ACK / NACK and the corresponding repetition of the data on the PDSCH. Further, the offset K2 represents the number of time slots between the PDCCH reception of the PUSCH grant DCI (e.g., format 0_0 or 0_1) for the UE and the subsequent PUSCH transmission. Each of these offsets may have values of zero and positive integers.

[0103] Finally, DCI format 0_1 may also include a network request for UE reporting of channel state information (CSI) or channel quality information (CQI). Before transmitting the report, the UE receives and measures CSI - RS sent by the network. The parameter aperiodicTriggeringOffset represents the integer number of time slots between the reception of the DCI including the CSI request by the UE and the transmission of the network's CSI - RS. This parameter may have values of 0 - 4.

[0104] In addition to the dynamic scheduling on a time - slot basis discussed above, NR also supports semi - persistent scheduling in the DL. In this method, the network configures the periodicity of the PDSCH transmission via RRC and then controls the start and stop of the transmission via DCI in the PDCCH. One advantage of this technique is the reduction of control signaling overhead on the PDCCH.

[0105] NR also supports a similar feature on the UL, referred to as configured grant (CG). Generally, CG type 2 is similar to DL semi - persistent scheduling in the downlink (e.g., RRC plus DCI), while CG type 1 is controlled only by RRC, including the start and stop of the transmission.

[0106] Figure 7Shows a high-level view of a 5G network architecture, including a Next Generation RAN (NG-RAN) 799 and a 5G Core (5GC) 798. The NG-RAN 799 may include a set of gNodeBs (gNBs) connected to the 5GC via one or more NG interfaces, such as gNB 700 and 750 connected via interfaces 702 and 752 respectively. Additionally, the gNBs may be connected to each other via one or more Xn interfaces, such as the Xn interface 740 between gNB 700 and 750. Regarding the NR interface to the UE, each of the gNBs may support Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), or a combination thereof.

[0107] Figure 7 The NG RAN logical nodes shown (and described in TS 38.401 and TR 38.801) include a Central (or centralized) Unit (CU or gNB-CU) and one or more Distributed (or decentralized) Units (DU or gNB-DU). For example, Figure 7 gNB 700 in includes a gNB-CU 710 and gNB-DUs 720 and 730. The CU (e.g., gNB-CU 710) is a logical node that hosts higher layer protocols and performs various gNB functions, such as controlling the operation of the DUs. Each DU is a logical node that hosts lower layer protocols and may include various subsets of gNB functions depending on the function split. Thus, each of the CU and DU may include multiple circuits required to perform their respective functions, including processing circuits, transceiver circuits (e.g., for communication), and power circuits. Also, the terms "Central Unit" and "centralized unit" may be used interchangeably herein, as are the terms "Distributed Unit" and "decentralized unit".

[0108] The gNB-CU is connected to the gNB-DUs via corresponding F1 logical interfaces, such as interfaces 722 and 732 shown in Figure 3. The gNB-CU and the connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. For example, the F1 interface is not visible outside the gNB-CU. As briefly mentioned above, the CU may host higher layer protocols, such as, for example, the F1 Application Part protocol (F1-AP), the Stream Control Transmission Protocol (SCTP), the GPRS Tunneling Protocol (GTP), the Packet Data Convergence Protocol (PDCP), the User Datagram Protocol (UDP), the Internet Protocol (IP), and the Radio Resource Control (RRC) protocol. In contrast, the DU may host lower layer protocols, such as, for example, the Radio Link Control (RLC), the Media Access Control (MAC), and the Physical Layer (PHY) protocol.

[0109] However, other variants of the protocol distribution between the CU and the DU can exist, such as hosting a part of the RRC, PDCP, and RLC protocols in the CU (e.g., the automatic repeat request (ARQ) function), while hosting the remaining part of the RLC protocol in the DU together with the MAC and PHY. In some embodiments, the CU can host the RRC and PDCP, where the PDCP is assumed to handle both the UP traffic and the CP traffic. However, other exemplary embodiments can use other protocol splits by hosting certain protocols in the CU and certain other protocols in the DU. Exemplary embodiments can also position the centralized control plane protocols (e.g., PDCP-C and RRC) in different CUs with respect to the centralized user plane protocol (e.g., PDCP-U).

[0110] Multiple signals can be sent from the same base station (e.g., gNB) from different antenna ports. These signals can have the same large-scale characteristics, such as according to the Doppler shift / spread, the average delay spread, or the average delay. These antenna ports are then said to be "quasi-co-located" or "QCL". The network can signal to the UE that two antenna ports are QCL. After the UE knows that two antenna ports are QCL with respect to a certain parameter (Doppler spread), the UE can estimate the parameter based on one of the antenna ports and use the estimate when receiving the other antenna port. Generally, the first antenna port is represented by a measurement reference signal such as CSI-RS (referred to as the "source RS"), and the second antenna port is the demodulation reference signal (DMRS) (referred to as the "target RS").

[0111] For example, if antenna ports A and B are QCL with respect to the average delay, the UE can estimate the average delay based on the signal received from antenna port A (source RS) and assume that the signal received from antenna port B (target RS) has the same average delay. This can be useful for demodulation because when trying to measure the channel using the DMRS, the UE can know in advance the characteristics of the channel.

[0112] Information about what assumptions can be made about QCL is signaled from the network to the UE. In NR, the following four types of QCL relationships between the transmitted source RS and the transmitted target RS are defined:

[0113] · Type A: {Doppler shift, Doppler spread, average delay, delay spread};

[0114] · Type B: {Doppler shift, Doppler spread};

[0115] · Type C: {average delay, Doppler shift}; and

[0116] · Type D: {spatial Rx parameter}.

[0117] QCL type D is introduced to facilitate beam management using analog beamforming and is referred to as "spatial QCL". There is currently no strict definition of spatial QCL, but the understanding is that if two transmitted antenna ports are spatially QCL, the UE can use the same Rx beam to receive them.

[0118] QCL type D is the most relevant for beam management, but it is also necessary to convey type A QCL RS relationships to the UE so that they can estimate all relevant large-scale parameters. Typically, this can be done by configuring the UE with a tracking reference signal (TRS, e.g., CSI-RS) for time / frequency offset estimation. To be able to use any QCL reference, the UE will have to receive it with a sufficiently good signal-to-interference-plus-noise ratio (SINR). In many cases, this limits the transmission of the TRS for a particular UE in a particular beam and / or beam configuration.

[0119] To introduce dynamics in beam and TRP selection, the UE can be configured via RRC signaling with N transmission configuration indication (TCI) states, where N is up to 128 in frequency range 2 (FR2) and up to eight in FR1, depending on UE capabilities. Each configured TCI state contains parameters for the QCL association between a source RS (e.g., CSI-RS or SS / PBCH) and a target RS (e.g., PDSCH / PDCCH DMRS port). The TCI state can also be used to convey QCL information for the reception of CSI-RS. Each of the N states in the list of TCI states can be interpreted as a list of N possible beams transmitted from the network, or a list of N possible TRPs used by the network to communicate with the UE.

[0120] More specifically, each TCI state can contain QCL information including one or two source DL RSs, where each source RS is associated with a QCL type. For example, two different CSI-RSs {CSI-RS1, CSI-RS2} can be configured in a TCI state as {qcl-Type1, qcl-Type2} = {type A, type D}. The UE can interpret this TCI state as meaning that the UE can obtain the Doppler frequency shift, Doppler spread, average delay, and delay spread from CSI-RS1, and spatial Rx parameters (e.g., the RX beam used) from CSI-RS2. In cases where QCL type D is not applicable (e.g., low or mid-band operation), then the TCI state contains only a single source RS.

[0121] In addition, a first list of available TCI states can be configured for the PDSCH, and a second list can be configured for the PDCCH. This second list can contain pointers to a subset of the TCI states configured for the PDSCH, which are referred to as TCI state IDs. For a UE operating in FR1, the network then activates one TCI state for the PDCCH (i.e., by providing the TCI to the UE) and up to eight TCI states for the PDSCH, depending on the UE capabilities.

[0122] As an example, the UE is configured with four active TCI states from a list of a total of 64 configured TCI states. Thus, the other 60 configured TCI states are inactive, and the UE does not need to prepare to estimate the large-scale parameters for those states. On the other hand, the UE continuously tracks and updates the large-scale parameters for those four active TCI states by performing measurements and analysis on the source RS indicated for each of the four active TCI states. Each DCI for PDSCH scheduling includes a pointer to one active TCI for the scheduled UE. Based on this pointer, the UE knows which large-scale parameter estimate to use when performing PDSCH DMRS channel estimation and PDSCH demodulation.

[0123] The Demodulation Reference Signal (DM-RS) facilitates coherent demodulation of the physical layer data channel (e.g., PDSCH) and PDCCH by the UE. Each DM-RS is associated with one of these physical layer channels and, as such, is limited to carrying the resource blocks of the associated physical layer channel. Each DM-RS is mapped onto the allocated REs of the time-frequency grid so that the receiver can effectively handle the time / frequency selective fading radio channel.

[0124] The mapping of the DM-RS to the RE is configurable in both the frequency domain and the time domain, where two mapping types in the frequency domain (Configuration Type 1 or Type 2) and two mapping types in the time domain (Mapping Type A or Type B) define the symbol position of the first DM-RS within the transmission interval. The DM-RS mapping in the time domain can also be single-symbol or double-symbol based (i.e., pairs of adjacent symbols). In addition, the UE can be configured with one, two, three, or four single-symbol DM-RSs and one or two double-symbol DM-RSs. In a scenario with low Doppler, configuring only the precoded DM-RS (i.e., one single-symbol DM-RS or double-symbol DM-RS) may be sufficient, while additional DM-RSs will be required in a scenario with high Doppler.

[0125] Figure 8 (which includes Figures 8A to 8D ) shows four exemplary mappings of the precoded DM-RS with Type A time domain mapping, where the first DM-RS is in the third symbol of a slot with 14 symbols. More particularly,Figures 8A to 8B The mappings for Configuration Type 1 for single-symbol and double-symbol DM-RS are shown respectively. Similarly, Figures 8C to 8D The mappings for Configuration Type 2 for single-symbol and double-symbol DM-RS are shown respectively. As shown in Figure 8, Type 1 and Type 2 differ in both the mapping structure and the number of supported DM-RS CDM groups. As indicated by the different shadings of the DM-RS REs, Type 1 supports two CDM groups (e.g., λ = 0, 1), and Type 2 supports three CDM groups (e.g., λ = 0, 1, 2).

[0126] The mapping structure of Type 1 is sometimes referred to as a 2-comb structure, which has two CDM groups defined by sets of subcarriers {0, 2, 4,...} and {1, 3, 5,...} in the frequency domain. Since it facilitates low peak-to-average power ratio (PAPR) transmission, the comb mapping structure is used in combination with DFT-S-OFDM in NR UL. In contrast, both Type 1 and Type 2 mappings are supported for CP-OFDM operations (e.g., in UL and DL).

[0127] The DM-RS antenna ports are mapped to the REs within only one CDM group. For single-symbol DM-RS, two antenna ports can be mapped to each CDM group, while for double-symbol DM-RS, four antenna ports can be mapped to each CDM group. Thus, the maximum number of DM-RS ports is four or eight for Type 1 and six or twelve for Type 2. Orthogonal cover codes (OCC) of length two ([+1, +1], [+1, -1]) are used to separate the antenna ports mapped to the same RE within a CDM group. When double-symbol DM-RS is configured, the OCC is applied in both the frequency domain and the time domain.

[0128] In NR Rel-15, for the parameter set index μ, the mapping of the PDSCH DM-RS sequence r(m), m = 0, 1,... on the subcarrier k in the antenna port p j and OFDM symbol l is specified in 3GPP TS 38.211 according to the following formula:

[0129]

[0130] k′ = 0, 1

[0131]

[0132] n = 0, 1,...

[0133] where

[0134]

[0135] represents applying the OCC in the frequency domain wf (k′) and time domain w t (l′) and then in the CDM group at port p in j The reference signals mapped thereon. Table 2-3 below shows the PDSCH DM-RS mapping parameters for configuration types 1 and 2, respectively.

[0136] Table 2.

[0137]

[0138] Table 3.

[0139]

[0140]

[0141] The DCI also includes a bit field indicating which antenna ports (i.e., the number of data layers) are scheduled. For example, if port 1000 is indicated, then the PDSCH is single-layer transmission and the UE will use the DMRS defined by port 1000 to demodulate the PDSCH. The DCI value also indicates the number of CDM groups without data, which means that if 1 is indicated, then another CDM group contains data for the UE (PDSCH case), and if 2 is indicated, then these two CDM groups may contain DMRS ports and no data is mapped to the OFDM symbols containing DMRS. Table 4 below shows the bit field values and corresponding configurations for DM-RS type 1 with a single preloaded DM-RS (maxlength = 1).

[0142]

[0143] Antenna Port Indication Table

[0144] For DMRS type 1, ports 1000, 1001, 1004, and 1005 are in CDM group λ = 0, and ports 1002, 1003, 1006, and 1007 are in CDM group λ = 1 (also shown in Table 2). Conversely, Table 5 shows the corresponding exemplary configurations for DMRS type 2. For DMRS type 2, ports 1000, 1001, 1006, and 1007 are in CDM group λ = 0; ports 1002, 1003, 1008, and 1009 are in CMD group λ = 1; and ports 1004, 1005, 1010, and 1011 are in CMD group λ = 2 (also shown in Table 3).

[0145]

[0146] QCL relationship with the DMRS CDM group

[0147] Currently, the 3GPP NR specification includes the following restrictions: A UE may assume that the PDSCH DM-RS within the same CDM group is quasi-co-located with respect to Doppler shift, Doppler spread, average delay, average spread, and spatial Rx. In the case where a first UE is not scheduled on all DMRS ports of a CDM group, another UE may simultaneously schedule for the remaining ports of that CDM group. The first UE may then estimate the channel for that other UE, which is regarded by the first UE as an interference signal. That facilitates coherent interference suppression by the first UE.

[0148] Multi-TRP / Multi-panel / Multi-beam extension

[0149] As mentioned above, multi-source transmission of PDSCH to a UE has been considered for 3GPP NR Rel-16. This can be used, for example, to improve URLLC performance by sending multiple copies of a PDSCH transport block (TB) from different TRPs to the UE, also known as "multi-TRP diversity". To support this feature, it has been discussed to extend the Rel-15 pair of TCI states from two source RSs with QCL type 1 and type 2 (e.g., TCI state = {qcl-Type1, qcl-Type2}) to an extended TCI state with two pairs A and B or even three pairs A, B, and C. These options can be expressed as:

[0150] TCI state = { {qcl-Type1, qcl-Type2} A , {qcl-Type1, qcl-Type2} B}, and

[0151] TCI state = { {qcl-Type1, qcl-Type2} A , {qcl-Type1, qcl-Type2} B , {qcl-Type1, qcl-Type2} C}.

[0152] In the above, A, B, and C may represent three different TRPs, three different antenna panels at one gNB, or three different beams in the case of FR2 operation (also known as "millimeter wave" or simply mmW).

[0153] As briefly mentioned above, URLLC aims to provide data services with extremely strict requirements for reliability and latency, e.g., data error probability and 10 -5Or lower and an end-to-end latency of 1 ms or lower. One technique to address such reliability requirements is to transmit multiple copies of a transport block from different TRPs to the UE in a diversity manner. 3GPP Rel-16 supports multi-PDCCH scheduling, whereby multiple PDCCH transmissions are used to schedule multiple PDSCHs carrying the transport block from different TRPs respectively. However, this diversity increases the UE complexity because the UE has to correctly decode multiple PDCCHs (e.g., DCI) in order to receive the multiple PDSCHs and thus benefit from the multi-TRP diversity transmission. This places an even greater requirement on the PDCCH reliability (e.g., a reduced error rate), which is already problematic in some scenarios. The detection of multiple PDCCHs also increases the UE complexity and consumes multiple PDCCH resources, thus reducing the possibility of scheduling other UEs in the same time slot (e.g., an increased PDCCH blocking probability). Thus, there are various issues, problems, and / or difficulties associated with diversity transmission that need to be addressed to meet the stringent reliability requirements associated with URLLC and other services.

[0154] Exemplary embodiments of the present disclosure can address these and other issues, problems, and / or difficulties by configuring the UE to receive multiple PDSCHs in the same OFDM symbol set of a time slot by a single DCI and / or PDCCH, where each of the multiple PDSCHs is a version (e.g., a repetition) of the same data payload. Additionally, the exemplary embodiments can configure the TCI state for each PDSCH to support multi-source (e.g., multi-TRP) transmission. In this way, the PDSCH diversity caused by multi-TRP transmission can be achieved even with a single PDCCH, which can increase the reliability, reduce the latency, reduce the PDCCH blocking probability, and / or reduce the UE complexity.

[0155] In the following description, "repetition" of a PDSCH or PUSCH generally refers to multiple copies of a data block (e.g., a transport block, TB) being transmitted in different frequency resources and / or different spatial resources (e.g., MIMO layers) within a single OFDM symbol during a time slot or in multiple OFDM symbols during one or more time slots. However, exemplary embodiments of the present disclosure differ from conventional solutions at least in that they use non-overlapping frequency resources (e.g., REs or RBs) and / or non-overlapping spatial resources (e.g., layers) to facilitate the transmission of multiple PDSCHs in a single OFDM symbol.

[0156] In other words, some embodiments facilitate a more generalized repetition of PDSCH or PUSCH, where multiple copies of a packet are sent in different frequency resources and / or different spatial resources (i.e., MIMO layers) and at a single transmission time instant, but may be sent via a configuration of transmissions in different time occasions (different OFDM symbols in one or more time slots). The distinguishing feature from NR Release 15 is that multiple PDSCHs are sent in the same OFDM symbol (non-overlapping (FDM) or overlapping (spatial repetition)).

[0157] Additionally, the exemplary embodiments of the present disclosure differ from conventional solutions (e.g., NR Rel-15) at least in that each repetition of multiple repetitions (e.g., of PDSCH) is associated with a source RS (or RS pair when QCL type D applies), which can potentially be different for each PDSCH. This can facilitate sending different repetitions of data blocks from different sources (e.g., TRPs). For practical convenience, the following description will refer to this as assigning a TCI state to each PDSCH repetition.

[0158] In other words, some embodiments facilitate the repetition of PDSCH or PUSCH, where multiple copies of a packet are sent in different frequency resources and / or different spatial resources (or RS pair, in the case where QCL type D applies), which can then potentially be different for each PDSCH. This allows for sending repetitions of the packet from different TRPs. This can actually be described as assigning a TCI state to each PDSCH. This is another exemplary distinguishing feature compared to conventional solutions (e.g., NR Rel-15).

[0159] Assigning TCI States per PDSCH Repetition

[0160] Various exemplary embodiments can assign a TCI state to each PDSCH in various ways. In some embodiments, the TCI state for each PDSCH is configured via RRC or MAC control elements, e.g., by having the MAC CE indicate a set of multiple active TCI states. For example, the MAC CE can indicate a set of two, four, or eight active TCI states, and each PDSCH repetition can use the active states of the set in a predefined order (e.g., cyclic order) that does not overlap with a predefined order associated with other PDSCH repetitions. As a more specific example, the 2, 4, or 8 active TCI states selected by the MACCE in NR Rel-15 can also be used in a cyclic manner for PDSCH repetitions. For example, each PDSCH uses one of the activated TCI states in a predefined order.

[0161] Alternatively, to give the network scheduler more flexibility when selecting multiple resources (e.g., TRPs) to be used in PDSCH repetitions, the selected active TCI state can be indicated in the scheduling DCI for PDSCH repetitions. In other words, when scheduling a PDSCH with repetitions, the DCI can select among the active TCI states. Table 6 below shows an exemplary arrangement in which the set of active states (e.g., TCI states 0 - 3) for PDSCH repetitions can be configured by RRC or MAC CE, but the assignment of individual active TCI states to individual PDSCH repetitions is provided by the DCI on the PDCCH. In this example, a two-bit DCI field selects a table row with a specific assignment of four active TCI states to four DPSCH repetitions sent by four different sources (e.g., TRPs or beams). In other words, the content of Table 6 (in italics) can be configured by RRC and / or MAC CE, and then the two-bit DCI field (as used in this example) selects a row in the table.

[0162] In the embodiment shown in Table 6 below, the scheduler can also dynamically select which TRPs are involved in the repetitions via the DCI value. This can be beneficial, for example, if some TRPs are busy transmitting to other UEs. For example, DCI = 00 involves four TRPs, each assigned a different active TCI state. Conversely, the scheduling can be restricted by selecting the second row (e.g., where DCI = 01) or the third row (e.g., where DCI = 10), each of which involves only two TRPs, where each TRP is assigned two different active TCI states. It is also possible to configure a row where only a single TRP is used, such as the fourth row indicating that only TCI state 0 is used for all repetitions. This row can be selected by DCI = 11. It is also possible that the number of repetitions is greater than the number of columns in the configuration table (i.e., in this example, >4). Such embodiments can use wrapping or modulo arithmetic on the repetitions (e.g., repetition 4 uses the same TRP as repetition 0, etc.).

[0163] Table 6. Example of mapping TCI state values to the TCI state to be used for each PDSCH repetition, where the italicized values (TCI states) in the table are configured by RRC.

[0164]

[0165] In some embodiments, the time domain repetition count may be encoded and conveyed via the TCI field in DCI, rather than being semi-statically configured via the RRC parameter pdsch-AggregationFactor. For example, each RRC-configured candidate TCI state may be associated with the number of time domain repetitions. In other embodiments, a separate RRC configuration parameter maps each code point of the TCI field in DCI to the repetition count and may additionally configure the mapping order of the activated TCI states to PDSCH repetitions, similar to the arrangement shown. In other embodiments, in addition to which TCT state candidates are mapped to which code points of the TCI field, the MAC CE TCI state activation message includes an indication of the repetition count associated with the code points of the TCI field in DCI.

[0166] In Rel-15 NR, the number of bits of the TCI field in DCI is 0 or 3, depending on whether the higher layer parameter tci-PresentInDCI is enabled. Thus, a total of eight TCI code point values can be indicated with this three-bit field. According to 3GPP TS38.321, when two TCI states are activated, then these activated TCI fields are mapped to the first two TCI code point values (i.e., '000' and '001') of the TCI field in DCI. In such cases, the remaining six TCI code point values (i.e., '010', '011', '100', '101', '110', and '111') do not have any activated TCI states mapped to them. More generally, in NR Rel-15, if N < 8 TCI states are activated by the MAC CE, then 8 - N code point values will not have any active TCI states mapped to them.

[0167] Thus, in some exemplary embodiments, when N out of the maximum M TCT states are activated (e.g., M = 8) and N < M, M - N unused code points can be used for multi-TRP repetitions of the PDSCH. For example, each PDSCH sent from a different TRP uses one of the activated TCI states in a predefined order. As in NR Rel-15, the first N code points are used for a single TRP transmission with a single TCI state. Thus, this embodiment facilitates a dynamic switch between single-TRP and multi-TRP transmissions with PDSCH diversity.

[0168] As briefly mentioned above, PDSCH repetition can be mapped across different frequency resources (e.g., within a symbol) or across layers in the same frequency resource (e.g., spatial repetition on the same RE). In some embodiments, time-domain PDSCH repetition can be configured, which can facilitate an even larger number of repetitions. In this case, the modulo or wrap-around scheme discussed above can be used, so that the TRP is selected cyclically for each PDSCH transmitted. For example, if two repetitions are configured in the frequency domain and time domain, then repetitions 0 and 1 are in the same first OFDM symbol set and repetitions 2 and 3 are in a second OFDM symbol set that occurs later, such as in the next available DL time slot.

[0169] In some embodiments, the DCI can also contain information on whether PDSCH repetition (e.g., according to resources configured per repetition in RRC) should apply. In the PDCCH region of a time slot, a particular PDCCH can be located in multiple places, which differ based on whether the PDCCH is UE-specific or common and the aggregation level (AL) used. Each PDCCH carries a DCI and is identified by a radio network temporary identifier (RNTI), which is implicitly encoded in the CRC attachment of the DCI. In some embodiments, the PDCCH RNTI can be used to distinguish whether PDSCH repetition should apply. For example, if the PDCCH is associated with the cell RNTI (C-RNTI), the repetition is not applicable, but if the PDCCH is associated with the modulation and coding scheme cell RNTI (MCS-C-RNTI), it is applicable according to a previous higher layer configuration.

[0170] To increase the reliability of data packets, the data payload can be encoded with different redundancy versions (RVs). This is commonly used in retransmissions in LTE and NR, where, in each retransmission, a different RV is used (e.g., RV = 0, 1, 2, 3, etc.). In NR, it is possible to schedule the PDSCH or PUSCH with time repetition separately based on the RRC parameters pdsch-AggregationFactor or pusch-AggregationFactor for dynamic scheduling; and repK for the PUSCH with UL configured grant. In this case, the PxSCH is scheduled but transmitted in multiple adjacent time slots until the number of repetitions determined by the configured RRC parameters.

[0171] In some embodiments, when mapped to different frequency resources in the same OFDM symbol set, each PDSCH repetition may also carry different redundancy versions (RVs) of data including a transport block (TB). The mapping between the RV and the PDSCH repetition / TRP may be indicated, for example, by a field in the DCI. Table 7 below shows an exemplary arrangement in which a two-bit DCI value indicates one of four mappings between the RV and individual PDSCH repetitions.

[0172] Table 7. Example of mapping the indicated redundancy version values to the RVs to be used for each PDSCH repetition, where the italicized values (TCI states) in the table are configured by RRC.

[0173]

[0174] Although the above discussion is based on dynamic scheduling PDSCH where each transmission has an associated scheduling DCI, similar techniques can be applied to semi-persistent scheduling (SPS) PDSCH where each transmission does not have an associated DCI. For example, the UE may receive the PDSCH on the RRC-configured resources after receiving the DCI with a CRC scrambled by the CS-RNTI that activates the SPS resources. In this way, the content of the TCI state table can be configured by the RRC IE, and subsequent activation of the TCI can select the table row to be applied to the PDSCH for the corresponding DL SPS process.

[0175] Frequency resource allocation

[0176] To support frequency division multiplexing (FDM), multi-TRP PDSH transmission, multiple frequency resources must be allocated and / or defined, one frequency resource per PDSCH repetition. Such allocation facilitates TCI state cycling, or more precisely, cycling of the source RS for the QCL relationship between the source RS and each PDSCH DMRS. In some embodiments, multiple (e.g., N>1) resources with a fixed size (e.g., the number of PRBs and / or the number of OFDM symbols per resource) may be preconfigured via RRC and / or MAC CE using higher layer signaling. Subsequently, the DCI that triggers the PDSCH repetition transmission may initiate or trigger the use of these preconfigured resources.

[0177] In other embodiments, the DCI may include scheduling of a single primary PDSCH resource plus an indication of repetition of an additional N-1 PDSCHs in the same OFDM symbol as the primary PDSCH. For example, the arrangement or location of the resources for these additional (one or more) PDSCHs may be indicated relative to the primary PDSCH resource, e.g., using a frequency offset measured according to RBs, precoded RB groups (PRGs), or RB groups (RBGs). The indication of the relative offset for each PDSCH may be configured by a higher layer, such as RRC or MAC CE. In some variants, the relative offset value may depend on the scheduling bandwidth of the primary PDSCH in the frequency domain, the bandwidth of the carrier, and / or the bandwidth of the BWP containing the primary resource.

[0178] In some embodiments, the network (e.g., serving gNB) may configure multiple UEs with the same offset value and schedule multiple UEs using primary PDSCH resources that are adjacent in the frequency domain. In this way, the frequency-domain PDSCH repetition resources for each UE may be arranged in a comb pattern such that PDSCH repetitions for multiple UEs may be scheduled using non-overlapping PDSCH combs. This may facilitate preferred and / or optimal (e.g., full) use of the available frequency resources while providing frequency diversity for each scheduled UE.

[0179] In other embodiments, virtual RB (VRB) allocation may be used and multiple PDSCH repetitions may always be allocated in the VRBs following the VRB allocation of the primary PDSCH resource. In these embodiments, frequency diversity may be achieved by configuring the VRB-to-PRB mapping of the PDSCHs distributed across frequencies. This VRB-to-PRB mapping may be preconfigured via RRC, indicated in the DCI from a set of candidates from the RRC configuration using the DCI VRB-to-PRB indicator field, or encoded in a TCI state. The VRB-to-PRB mapping may also be PDCCH-specific and depend on the actual resource allocation of the PDSCH such that each repeated PDSCH is always mappable to contiguous PRBs.

[0180] In some embodiments, the relative offset may be indicated by the TCI state indicator provided in the DCI, thereby facilitating the scheduler to dynamically select the value N. Each TCI state may be configured using one or more resource allocation offset values offset#n. Table 8 below shows an exemplary variation of Table 6 above, where the TCI state indicator values in the DCI are also mapped to specific offsets for the corresponding PDSCH repetitions. As in Table 6, DCI = 00 implies transmissions from four different TRPs and at three different offset values (which may be configured by a higher layer) relative to the primary PDSCH. On the other hand, if the TCI state DCI indicates '01' or '10', then only two TRPs are used and the second PDSCH is transmitted at offset#1 relative to the primary PDSCH.

[0181] Alternatively, the higher layer may directly configure the exact resource allocation for all repetitions and map it to such a table (Table 8) without a relative offset from the primary PDSCH.

[0182] In some embodiments, if the frequency offset of the PDSCH repetition falls outside the allocated BWP, the repetition may be discarded. Alternatively, a modulo method may be used to wrap the PDSCH repetition around to resources in the lower end of the BWP.

[0183] Table 8. Example mapping of TCI states and resource allocation offset values to the TCI states to be used for each PDSCH repetition, where the italicized values in the table are configured by RRC.

[0184]

[0185]

[0186] Semi-persistent transmission of PDSCH

[0187] The embodiments described above using relative frequency offsets may also be applicable to SPS PDSCH according to similar principles (e.g., each transmission does not have an associated DCI). For example, the UE may receive the PDSCH on the RRC-configured DL-SPS resource after activating the pre-configured DL-SPS resource with a DCI having a CRC scrambled by the CS-RNTI. The content of the TCI state and offset table (e.g., Table 8) may be configured by RRC IE, and the subsequent activation DCI may select the table row to be applied to the SPS PDSCH.

[0188] Support for spatial repetition of PDSCH

[0189] Other exemplary embodiments may configure PDSCH transmissions on resources that overlap in the frequency domain but do not overlap in the spatial domain. This may be effective in terms of the bandwidth used at the cost of increased UE receiver complexity required to support multi-layer reception (including inter-layer interference cancellation). Even so, for large data blocks, it may not be possible to repeat frequency multiplexing for multiple PDSCHs, in which case spatial repetition of the PDSCH is the only possibility. In some embodiments, PDSCH repetition may be configured in both the frequency domain and the spatial domain. For example, N = 4 repetitions in two different frequency resources, where each frequency resource carries spatial repetition of two PDSCHs.

[0190] In such embodiments where at least two of the N PDSCH repetitions in a time slot or the same scheduled OFDM symbol set are assigned to the same frequency resource, the selection of DMRS ports for the PDSCH is different such that they are orthogonal, which ensures good performance of channel estimation. In other words, the DMRS ports for each PDSCH can be configured to be orthogonal to other PDSCH repetitions that overlap in the frequency domain, which facilitates good channel estimation performance. The DMRS assignment for the PDSCH can be done in various ways, as described below.

[0191] In some embodiments, different sets of DMRS ports may be configured for each TCI state. This can be done via higher layer signaling, such as by including DMRS ports in the TCI configuration, for example, by RRC or MAC CE. To comply with the NR Rel-15 requirement that all ports in a CDM group must be QCL with each other, different TCI states may be associated with DMRS ports of different CDM groups. For example, if DMRS type 1 is configured, TCI_state#0 may use DMRS ports 1000 and 1001, while TCI_state#1 may use DMRS ports 1002 and 1003. If PDSCH is scheduled with rank 1, then the first port of each TCI_state (e.g., ports 1000 and 1002) may be used. On the other hand, if PDSCH is scheduled with rank 2, then two ports from the associated CDM group may be used.

[0192] In other embodiments, different sets of DMRS ports may be configured for each PDSCH repetition. For example, assume that each repetition can be identified by a sequence number (e.g., based on the frequency resource allocation configuration). In such cases, between PDSCH repetitions in overlapping resources, the PDSCH with the lowest number can be configured to use DMRS ports from the first CDM group, the PDSCH with the second lowest number can be configured to use DMRS ports from the second CDM group, and so on. In another variant, if two PDSCHs have the same TCI state (e.g., transmitted from the same TRP), then the DMRS ports are selected from the same CDM group (since they are QCL), and PDSCHs with different TCI states can use DMRS ports from the next CDM group.

[0193] As an illustrative example, consider the transmission of four overlapping PDSCHs sent in pairs from two TRPs configured with DMRS type 1. The first two PDSCHs may use the same TCI state and thus can be assigned DMRS ports 1000 and 1001 (CDM group λ = 0), while the third and fourth PDSCHs may use another TCI state and thus can be assigned DMRS ports 1002 and 1003 (CDM group λ = 1).

[0194] More general rules can also be defined, such as for the (one or more) PDSCHs with the same TCI state, the DMRS port numbers increase with the CDM group, and the DMRS ports for the next TCI state are assigned to the next CDM group. Such rules can facilitate support for two TRPs configured with DMRS type 1 (two CDM groups) and three TRPs configured with DMRS type 2 (three CDM groups).

[0195] Data scrambling

[0196] In other embodiments, when multiple PDSCH repetitions overlap in frequency resources, different scrambling can be configured for each PDSCH. This can provide performance benefits, such as those seen for dual-codeword (CW) transmission in one PDSCH in LTE and NR. Different scrambling can be configured by defining different scrambling initialization seeds for each CW. In Rel-15, the initialization seed for generating scrambling is defined by:

[0197] c_init = 2 15 *n_RNTI + 2 14 *q + n_ID,

[0198] Where, n_RNTI is the RNTI for the scheduled PDSCH, q is the CW index {0,1}, and n_ID is the value of the UE-specific RRC configuration. To achieve scrambling by PDSCH in the case of overlap, the above relationship can be modified according to the following:

[0199] c_init = 2 15 *n_RNTI + 2 14 *q + n_ID + 2 10 *N,

[0200] Where, N = 0, 1, 2, … is an identifier for the repetition of a specific PDSCH. In some embodiments, N can be incremented for each overlapping PDSCH in a given resource, where N = 0 is reused for the lowest numbered PDSCH in the next frequency resource with overlapping PDSCHs. In other embodiments, N can be incremented sequentially for all PDSCHs transmitted in the same OFDM symbol set or the same time slot (e.g., without resetting to zero).

[0201] In a variant of these embodiments, each repeated copy of the PDSCH can be configured to be associated with an n_ID value, which is configured separately by RRC, for example, to apply to the general configuration of PDSCH repetition regarding any involved TRP. Alternatively, different n_ID values can be indirectly associated with the scheduled repetition by being configured to be associated with a TCI state or a QCL source.

[0202] Similar to PUSCH transmission

[0203] Although the above description focuses on PDSCH repetition, the described principles can also apply to PUSCH repetition with certain appropriate modifications. For example, PUSCH TCI states are not defined in Rel-15, but such features may be introduced in the future. Alternatively, a SRS resource indicator (SRI) can achieve the same role as the TCI state for PDSCH. For example, the SRI cycle can be used across PUSCH transmissions in a similar manner to the TCI state cycle discussed above, where the same data block (with different RVs as needed) is carried in each PUSCH repetition. In addition, each SRI can indicate a specific UE antenna panel that can be transmitted separately, thereby providing spatial diversity in PUSCH repetition.

[0204] In addition, the DMRS port selection and data scrambling selection for PUSCH can be based on the same principles as discussed above for PDSCH. Even so, for PUSCH, there is no requirement that DMRS ports within the same CDM group must belong to the same SRI (i.e., the same panel). Therefore, for PUSCH, DMRS ports can be linearly allocated without considering (e.g., independently of) the CDM group.

[0205] In PUSCH repetition embodiments, it can be beneficial to allocate frequency domain resources for PUSCH repetitions in consecutive blocks of OFDM symbols (e.g., consecutive PRBs). In such cases, it may not be necessary to explicitly signal the frequency resource offset per repetition for PDSCH. Instead, the offset between two adjacent repetitions of PUSCH can be implied from the number of PRBs for a single repetition of PUSCH.

[0206] For semi-persistent UL scheduling, two types of UL configuration grants (CG) are provided in Rel-15. Type 2 CG is very similar to DL SPS, whereby the UE can transmit PUSCH on the RRC-configured resources after activating the UL CG resources with a DCI scrambled with CS-RNTI. Thus, the embodiments described above for DL SPS can be applied for use with type 2 UL CG. For example, the content of the SRI state table can be configured by an RRC IE, after which the activated DCI selects the table row to apply to the SPS PUSCH.

[0207] In contrast, for type 1 UL CG, PUSCH transmission can be configured only by RRC; no activating DCI is involved. Thus, all configurations of PUSCH repetition should be provided via RRC. For example, the RRC configuration of type 1 UL CG provides a sequence of SRI states (e.g., similar to the rows of the TCI states shown in Table 6) for use.

[0208] Configurable repetition pattern

[0209] Configurable repetition pattern

[0210] In other embodiments, multiple repetition patterns can be configured by RRC, where each pattern indicates the time and / or frequency resources, spatial relationship (or TRP or TCI state), RV, and / or DMRS ports for subsequent repetitions of PDSCH (or PUSCH) scheduled by DCI. For K PDSCH (or PUSCH) transmissions, the repetition pattern can include K - 1 states {(t2,f2,s2,v2,d2),…,(t K ,f K ,s K ,v K ,d K)}, and each state is associated with a PDSCH (or PUSCH) transmission instance. The tuple (t k , f k ) represents the time and frequency resources for the k-th transmission, while the tuple (s k , v k , d k ) represents the TCI state, RV, and DMRS ports respectively associated with the k-th transmission. The DMRS ports can be configured as the indices in the first column of Table 4 or Table 5. In a similar manner as described with reference to the various tables, the time and frequency resources, spatial relation (or TCI state), RV version, and / or DMRS ports for the first PDSCH (or PUSCH) transmission can be indicated by bit fields in the DCI used to schedule the PDSCH / PUSCH repetitions. The repetition pattern to be used can be dynamically selected from among multiple configured repetition patterns and can also be indicated to the UE using bit fields in the scheduling DCI.

[0211] In some embodiments, (t k , f k ) can represent the time and frequency offsets respectively relative to the time and frequency resources for the first PDSCH (or PUSCH) transmission or more generally for the (k - 1)-th PDSCH (or PUSCH) transmission. The time resource offset can be in terms of time slots, mini-slots, or OFDM symbols, and the frequency offset can be in terms of RBs, precoded RB groups (PRGs), or RBGs. The condition t k = t k-1 indicates that the k-th and (k - 1)-th transmissions use the same time resource. Similarly, if f k = f k-1 , then the k-th and (k - 1)-th transmissions use the same frequency resource. If t k = t k-1 and f k = f k-1 , but s k ≠ s k-1 , then the k-th and (k - 1)-th transmissions are in the same time and frequency resources but from different spatial resources (e.g., TRP or panel). In some embodiments, one or more of (t k , f k , s k , v k , d k ) can be predefined or implicitly related and / or linked to other parameters.

[0212] Figure 9An exemplary operation scenario is shown in which a UE communicates with two gNBs that can provide PDSCH diversity transmission according to various exemplary embodiments of the present disclosure. In this example, the resources for PDSCH repetition do not overlap in frequency. The UE can be configured by gNB1 (e.g., activated via a MAC CE) to actively track multiple TCI states. The UE starts tracking these multiple TCI states by performing measurements on the associated RSs for each TCI state. Note that the RS associated with a TCI state is sent from the same gNB as the PDSCH associated with the same TCI state.

[0213] Then, the UE receives DCI that schedules multiple PDSCHs in one time slot, e.g., in the same OFDM symbol set. Then, the UE receives these multiple PDSCHs (usually containing the same data block, optionally with different RVs) according to different active TCI states associated with each PDSCH repetition. In this way, different repetitions can be sent by different TRPs shown as gNB1 and gNB2 in Figure 9 the figure.

[0214] Figure 10 Another exemplary operation scenario is shown in which a UE communicates with two gNBs that can provide PDSCH diversity transmission according to other exemplary embodiments of the present disclosure. In this scenario, the resources for PDSCH repetition overlap in frequency but do not overlap in space, creating a multi-layer MIMO transmission of two PDSCHs. Each PDSCH can contain more than one layer. In some embodiments, the UE can signal support for this PDSCH repetition pattern of the layered PDSCH before the network configures the UE in this way.

[0215] Various embodiments of the present disclosure, including the embodiments described above, can be implemented within the framework of one or more 3GPP TSG RAN specifications (e.g., multi-TRP operation in NR Rel.16). The following description shows how certain aspects and / or enhancements related to these embodiments can be specified and / or standardized in an exemplary manner (e.g., based on proposals and / or observations). However, these and other aspects and / or enhancements can be specified and / or standardized in other suitable ways, such as in 3GPP specifications and / or in other specifications or standards.

[0216] Category 1: Multi-TRP Scheduling Based on Multiple PDCCHs

[0217] In this operation mode, multiple PDCCHs can be received in a time slot and each PDCCH schedules a PDSCH. Generally, Rel-15 NR can be reused in principle, including the configuration of TCI states for each CORESET and the DMRS scrambling for the PDSCH. Therefore, not many specification changes are envisaged for this operation mode.

[0218] In multi-PDCCH scheduling, there will be implementation-based semi-dynamic coordination between schedulers of different TRPs. Through semi-static to semi-dynamic resource reservation, the complexity of this coordination can be simple, depending on the bound of the backhaul delay. Due to various deployment conditions, it is difficult to make assumptions about what kind of scheduler coordination will be used for RAN1 specification guidance.

[0219] Therefore, it is better to focus on what is expected by the UE, what scheduling scenarios the UE should be prepared to handle, and what scheduling combinations the UE can ignore in its implementation to limit the complexity. Therefore, it is recommended that RAN1 focus on the requirements of the UE and reach an agreement on what scheduling conditions are not required for the UE to support.

[0220] Recommendation : Each PDCCH schedules a PDSCH for a UE that supports receiving multiple PDCCHs (at least for eMBB), and Rel.16 UEs do not expect to be scheduled in the following cases:

[0221] ● PDSCHs with partially overlapping resource allocations in the time domain and frequency domain

[0222] · More than one PDSCH with DMRS in the same CDM group for overlapping PDSCH resource allocations

[0223] ● Aggregate number of layers of all PDSCHs across overlapping time-frequency resources greater than the maximum number of layers supported / configured by the UE

[0224] ● Aggregate number of CWs of all PDSCHs across overlapping time-frequency resources greater than two

[0225] This means that when overlapping PDSCH scheduling occurs, each PDSCH supports at most one CW, and therefore each PDSCH only needs to support rank 1-4 in this multi-PDCCH case.

[0226] Regarding monitoring and receiving multiple PDCCHs, issues regarding search space capacity or blocking have to be shown, because the gain of multi-TRP transmission is only visible at low load, and therefore the demand for the required PDCCH capacity is low. In the case where PDCCHs are expected to be configured per TRP, the configuration of multiple CORESETs (with separate TCI states) has already been supported.

[0227] i. Antenna Port Indication Table

[0228] To support multi-TRP transmission, the DMRS ports sent from one TRP must belong to the same CDM group. Therefore, the antenna port table must be able to indicate the flexible number of layers within the CDM group according to the TRP.

[0229] The Rel-15 table for DMRS type 1 supports the scheduling of these layers (L1, L2) in the first and second CDM groups respectively:

[0230] · For single DMRS symbol, (L1, L2) = (1, 0), (2, 0), (0, 1), (0, 2)

[0231] · For double DMRS symbols, (L1, L2) = (1, 0), (2, 0), (3, 0), (4, 0), (0, 1), (0, 2), (0, 3), (0, 4)

[0232] Therefore, in the case of DMRS type 1, there is no need to update the antenna port table for multi-PDCCH scheduling. The PDCCH can flexibly indicate 1 - 4 layers from those layers included in any CDM group.

[0233] Note that when the DMRS ports from the second CDM group are indicated by a PDCCH by using the Rel-15 antenna port indication table (e.g., rank 2 scheduled with ports 2, 3), then the associated PDSCH cannot be mapped to the 1st CDM group (because these two CDM groups are indicated in the current table "without data"). However, the selection of only one CDM group by the PDCCH occurs only when one TRP is sent, and then the semi-dynamic coordination scheduler can instead indicate that the TRP should use the DMRS in the first CMD group (e.g., ports 0, 1). Therefore, the Rel-15 antenna port indication table can be used unchanged, where the second CDM group is used only when the first CDM group is also used for DMRS.

[0234] The Rel-15 table for DMRS type 2 supports the scheduling of these layers (L1, L2, L3) in the first, second, and third CDM groups respectively:

[0235] · For single DMRS symbol, (L1, L2, L3) = (1, 0, 0), (0, 1, 0) (0, 0, 1), (2, 0, 0), (0, 2, 0), (0, 0, 2)

[0236] · For dual DMRS symbols, (L1,L2,L3) = (1,0,0), (0,1,0), (0,0,1), (2,0,0), (0,2,0), (0,0,2), (3,0,0), (0,3,0), (0,0,3), (4,0,0), (0,4,0), (0,0,4)

[0237] Therefore, in the case of DMRS type 2, there is no need to update the antenna port table for multi-PDCCH scheduling. The PDCCH can flexibly indicate 1-4 from any CDM group and is included within that CDM group.

[0238] Suggestion: For multi-PDCCH operation, the Rel-15 antenna port indication table can be reused without modification.

[0239] ii. PDSCH rate matching

[0240] PDSCH rate matching is important for multi-TRP scheduling because semi-static RS and channel configurations in more than one TRP must be considered. For example, in multiple PDCCH methods, the UE can receive multiple PDCCHs scheduling the PDSCH in some time slots, which indicate different PDSCH resource mapping information. In this case, whether and how the UE should perform PDSCH resource mapping (i.e., PDSCH rate matching) is an open question because NR Rel-15 only specifies receiving a single PDDCH that simultaneously schedules a single PDSCH. Also, different TRPs have different configurations of TRS and LTE CRS (when applicable). Therefore, the suggestion is as follows:

[0241] Suggestion: Support a mechanism to extend PDSCH resource mapping around multiple reserved resources from different gNBs, i.e., the configured CORESET, ZP-CSI-RS-ResourceSet, and lte-CRS-ToMatchAround, which includes dynamic resource mapping around the detected PDCCH.

[0242] Category 2: Multi-TRP Scheduling Based on a Single PDCCH

[0243] i. Codeword to layer mapping and the number of CWs

[0244] An open question for discussion is whether to also maintain the Rel-15 codeword to layer mapping when using a single PDSCH for multi-TRP transmission, or whether there are benefits in considering a specification change in the mapping. In NR, a single CW is mapped to up to 4 layers, and therefore there are two options in Rel-16 for considering CW to TRP mapping, i.e.,

[0245] · Option 1 (New mapping): For the scheduled PDSCH, a separate CW is sent for each TRP.

[0246] · Option 2 (Rel-15 mapping): For the scheduled PDSCH, one CW is sent and mapped across all TRPs.

[0247] In Option 1, since different MCSs can be assigned to different CWs each mapped to a TRP, it has the potential benefit of better link adaptation when the path loss difference to different TRPs is quite large. In the case of decoding error on one CW, only that CW needs to be retransmitted. The drawback is that in order to support more than two TRPs, there are large specifications that need to be changed because each CW is associated with a HARQ-ACK. Additionally, the current CW-to-layer mapping needs to be extended to support two CWs for 2, 3, and 4 layers, and the issue of semi-static or dynamic switching between Rel-15 and Rel-16 codeword-to-layer mappings needs to be solved. Moreover, two CWs imply an overhead for additional CRC compared to a single CW.

[0248] For Option 2, it can be supported with the existing Rel-15 CW-to-layer mapping and thus does not require a specification change. Therefore, each layer is associated with a specific TRP by using DMRS CDM groups. Up to three TRPs can be supported with a single PDCCH and a single PDSCH by using all three CDM groups and extended TCI states (see Section 2.2.2). The drawback can be that since a single CW is used and thus a single MCS is used, link adaptation may not be as good as using separate MCSs per TRP when the path loss difference to multiple TRPs is large. However, this is anyway not an operating point for NC-JT because if the path loss difference is large, it is better to send all layers from the best TRP.

[0249] As already observed in the discussion of multi-TRP in Rel.15, Option 2 slightly outperforms Option 1. Similar results have also been observed by additional companies, such as in 3GPP Tdoc R1-1900731 for NC-JT in an indoor scenario (see Figure 3 in [8]). One reason is that for NC-JT to perform better than DPS, the UE should be at the cell edge and have comparable path losses to two TRPs, and in this case, link adaptation based on per-TRP does not provide a benefit. Another reason is that link adaptation based on multi-MCS is more sensitive to CSI feedback delay and error compared to the single MCS method. A slightly higher retransmission probability has also been observed for Option 1. Similar results are shown in 3GPP Tdoc R1-1900731, where for single-TRP MIMO, for ranks up to 4, a single CW performs better than two CWs.

[0250] Table 9. NC-JT performance comparison between the new (Option 1) CW-to-layer mapping and the Rel-15 (Option 2) CW-to-layer mapping.

[0251]

[0252] In an indoor scenario, NC-JT with Option 2 (single CW) slightly outperforms NC-JT with Option 1 (two CWs). Given that Option 2 slightly outperforms Option 1 in the most promising indoor NC-JT scenarios and does not require any change to the existing CW-to-layer mapping, there is no reason to change the mapping in Rel-16. Additionally, if there is a strong desire to perform MCS adaptation by TRP based on deployment in certain scenarios, the multi-PDCCH method can be used.

[0253] Recommendation: RAN1 concludes that there is no change in the CW-to-layer mapping and the number of CWs per transmission rank in Rel-16.

[0254] ii. Extended TCI states

[0255] To support multi-TRP transmission with a single PDCCH, the DMRS ports sent from each TRP must belong to the same CDM group. Since there are two and three CDM groups for DMRS type 1 and 2 respectively, up to three TRP transmissions can be supported. The TCI state then needs to be extended to include multiple source RSs by QCL type. The following recommendations are made:

[0256] When the UE is configured for DMRS type 1 and 2 respectively and the source RS pair λ can be used to derive the QCL characteristics of the DMRS ports for CDM group λ, the TCI state can be configured with one, two, or three source RS pairs for QCL.

[0257] · For DMRS type 1, the TCI state can be configured to include: for each of the two CDM groups respectively, {{qcl-Type 1, qcl-Type2} λ＝0 , {qcl-Type 1, qcl-Type2} λ＝1}

[0258] · For DMRS type 2, the TCI state can be configured to include: for each of the three CDM groups respectively, {{qcl-Type1,qcl-Type2} λ＝0 ,{qcl-Type1,qcl-Type2} λ＝1 ,{qcl-Type1,qcl-Type2} λ＝2}.

[0259] Therefore, some TCI states have a single source RS pair (or a single RS if QCL type D is not applicable) as in Rel-15 and are used for DPS, while some other states have two or three source RS pairs and are used for NC-JT scheduling.

[0260] In Rel-15, there are at most eight (8) active TCI states for DPS that can support up to 8 different TRPs (which should be sufficient for most deployments). In the case of extended TCI states, since there is a possibility of selecting two or three TRPs per TCI state, there are more combinations. Therefore, it is necessary to consider whether allowing more (extended) than 8 TCI states is beneficial for Rel-16. Note, however, that the number of TRSs or SSBs tracked simultaneously can remain the same as in Rel-15, and the introduction of extended TCI states should not extend the tracking requirements.

[0261] Recommendation : Study whether it is beneficial to increase the number of bits in DCI for selecting active TCI states to accommodate more transmission assumptions (without increasing the maximum number of active tracked QCL source RSs).

[0262] iii. Antenna port indication table

[0263] To support multi-TRP transmission with a single PDCCH, the DMRS ports sent from each TRP must belong to the same CDM group. Therefore, the antenna port table must be able to indicate the flexible number of layers within the CDM group per TRP.

[0264] The Rel-15 table for DMRS type 1 supports the scheduling of these layers (L1, L2) in the first and second CDM groups respectively:

[0265] · For single DMRS symbol, (L1, L2) = (1, 0), (2, 0), (0, 1), (0, 2), (1, 1), (2, 1), (2, 2), and

[0266] ● For double DMRS symbols, (L1, L2) =

[0267] (1, 0), (2, 0), (3, 0), (4, 0), (0, 1), (0, 2), (0, 3), (0, 4), (1, 1), (2, 1), (2, 2).

[0268] Here, it can be seen that (1,2) is missing, i.e., the ability to schedule one layer from the first TRP and two layers from the second TRP. Although this can be supported at the cost of an additional extended TCI status code point in the DCI, where the two pairs of source RSs of the two TRPs are swapped to effectively support (2,1) and (1,2), a solution based on this configuration that may be quite common in practice can be avoided by adding a row to the antenna port indication table. Therefore, in the case of DMRS type 1, the antenna port table needs to be slightly updated.

[0269] Recommendation : Add a row to the DMRS type 1 antenna port indication table using ports 0, 2, 3 to allow scheduling of (1,2) layers in two CDM groups respectively.

[0270] The PDCCH can flexibly indicate 1 - 4 from any CDM group and is included within that CDM group, thus supporting DPS with up to rank 4. DPS for ranks 5 - 8 can also be supported by configuring additional TCI states with a single source RS pair for the participating TRPs.

[0271] A further optimization of the antenna port index could be to also add (3,1) and (1,3) states to the table, but this is a rather asymmetric layer distribution and the benefits are less obvious, and the gain needs to be proven through evaluation.

[0272] The Rel-15 table for DMRS type 2 supports scheduling of these layers (L1, L2, L3) in the first, second, and third CDM groups (i.e., the first, second, and third TRPs) respectively:

[0273] ● For single DMRS symbol, (L1, L2, L3) = (1, 0, 0), (0, 1, 0), (0, 0, 1), (2, 0, 0), (0, 2, 0),

[0274] (0, 0, 2), (1, 1, 0), (2, 1, 0), (0, 1, 2), (2, 2, 0).

[0275] ● For double DMRS symbol, (L1, L2, L3) = (1, 0, 0), (0, 1, 0) (0, 0, 1), (2, 0, 0), (0, 2, 0), (0, 0, 2),

[0276] (3, 0, 0), (0, 3, 0), (0, 0, 3), (4, 0, 0), (0, 4, 0), (0, 0, 4), (1, 1, 0), (2, 1, 0), (0, 1, 2), (2, 2, 0).

[0277] Here, it can be seen that the layer distribution is biased towards the first and second TRP / source QCL and has more flexibility in selecting the TRP set. Additional active TCI states must be configured. This can be avoided by adding some more states to the antenna port index table, and since there are some reserved states, these additional most likely transmission assumptions can be added.

[0278] Recommendation : Add rows to the DMRS type 2 antenna port indication table for PDSCH using the following:

[0279] a. Allow ports 0, 2, 4 for scheduling layer (1,1,1);

[0280] b. Allow ports 0, 2 for scheduling layer (1,1,0);

[0281] c. Allow ports 0, 4 for scheduling layer (1,0,1);

[0282] d. Allow ports 0, 2, 3 for scheduling layer (1,2,0).

[0283] Category 3: CSI Framework Extension

[0284] In previous meetings, suggestions for the CSI framework extension for multi-TRP / panel were made by some companies, where the NR Rel-15 CSI framework was used as the starting point and possible extensions were considered. For example, the gNB can configure the UE with two CSI reporting settings, where

[0285] · One reporting setting can be used for DPS, and

[0286] · The second reporting setting can be used for NC-JT.

[0287] By using the Rel-15 framework, the gNB can thus obtain single-TRP and NC-JT CSI in two CSI reports corresponding to the two CSI reporting settings and then dynamically decide whether to use DPS or NC-JT for PDSCH transmission.

[0288] For a measurement set with 3 TRPs, this means three individual TRP CSIs each associated with one TRP, and three NC-JT CSIs each associated with a pair of TRPs, assuming NC-JT on two TRPs. If two CWs are used, each of the NC-JT CSIs will include a pair (RI,PMI,CQI), or if a single CW is used, each of the NC-JT CSIs will include a pair (RI,PMI) and a single CQI. Compared to the CSI transmitted for a single TRP, this CSI feedback has an almost 9x feedback overhead, so there is a strong motivation for enhanced overhead reduction. Therefore, more efficient CSI feedback with low feedback overhead for multi-TRP should be investigated.

[0289] If configured to support dynamic switching between single-TRP and multi-TRP transmissions, the Rel-15 CSI feedback framework directly applied to multi-TRP scenarios may cause large CSI feedback overhead.

[0290] A possible Rel-16 enhancement to the CSI framework is to specify a method where the UE adopts an even larger active subset in the hypothesis selection, similar to using CRI for beam selection in the current Rel.15 framework, but extended to multi-TRP transmission hypotheses. By having the UE select a preferred transmission hypothesis (i.e., a set of multiple TRPs in this context), the overhead can be reduced because the UE is removing "bad" hypotheses (i.e., instead of blindly reporting all hypotheses) before sending the feedback.

[0291] Therefore, further multi-hypothesis types for CSI feedback for multi-TRP / panel transmissions in NR are investigated in the case of downward selection of hypotheses at the UE side. An example of such feedback is that the UE selects a subset from the configured number of TRPs for data transmission. For example, the gNB can configure the UE with N>1 NZP CSI-RS resources in the resource setting for channel measurement, where each of the N NZP CSI-RS resources is associated with one TRP. Then, in the corresponding CSI report, the UE can select a subset M of the NZP CSI-RS resources used for channel measurement, where M<N.

[0292] The discussion on CSI enhancements is useful to start as soon as possible in order to be able to conduct evaluations. However, for the most upcoming meetings, the priority on the consistency of details can be slightly reduced because agreements need to be reached on details of multi-TRP / panel PDSCH transmissions, such as the number of supported TRPs / panels, the extension of the TCI framework for multi-TRP / panels, antenna port indication, etc., before it is possible to accurately specify the CSI feedback framework to support these consistencies.

[0293] Recommendation : For CSI feedback, study UE-assisted multi / single TRP hypothesis selection feedback, where the UE decides on single or multi-TRP transmission based on measurement results and indicates the preferred hypothesis to the network.

[0294] In Rel-16 NR-MIMO, before deciding whether CSI framework enhancements and details are needed, agreement on the details of multi-TRP / panel PDSCH is required.

[0295] Category 4: Specific Extensions for Reliability / Robustness

[0296] From a multi-TRP perspective, the rationale for increasing the reliability and robustness of the transmitted data packets is to send multiple copies of the same data payload so that the UE can combine them in an "instantaneous retransmission" manner. Each "copy" is then associated with a different active TCI state (assuming PDSCH is used for the following discussion). Then, the open question for RAN1 is how to specify the resources for each "copy" and how to determine which TCI state is used for which "copy".

[0297] In 3GPP Tdoc R1-1900731, the analysis of several different strategies for achieving multi-TRP diversity gain was discussed, and it was concluded that repetition in time and frequency is beneficial for URLLC applications. In 3GPP Tdoc R1-1901116, the study on the impact of the number of TRPs used for achieving robustness was discussed, and it was shown that even with 4 TRPs, there are significant benefits compared to 2 TRPs in the case of an uneven received power distribution among 4 TRPs (as low as a 9 dB difference between the best and worst TRPs).

[0298] Then, it should be noted that the repetition function already exists in Rel-15, using the higher layer parameter pdsch-AggregationFactor, where each PDSCH is transmitted in a cycle with a predefined RV, and single-layer PDSCH is restricted. This principle can be extended to also include TCI states. Therefore, when the UE is configured for such robustness operations, the PDCCH can trigger a set of PDSCH transmissions, where each PDSCH can use a different TCI state from the set of active TCI states in a predefined manner.

[0299] Recommendation : A DCI can trigger the repetition of PDSCH transmissions with the same payload, where each PDSCH can be configured with a different TCI state from the set of active TCI states.

[0300] In Rel-15, these multiple PDSCHs are sent in different time slots and using a single layer. However, to reduce latency, in Rel-16, it should be possible to trigger multiple such PDSCHs in the same time slot (using type B scheduling, i.e., micro-slot based repetition), in the same OFDM symbol set via FDM (frequency-based repetition), or in overlapping resources (SDM or layer-based repetition). Further study and discussion can be carried out on how similar the repetition "patterns" should be and how to configure them (e.g., via RRC or via RRC+DCI). Figure 16 Shows various exemplary arrangements showing PDSCH repetition based on time slot, micro-slot, frequency, and layer.

[0301] As in Rel-15, the DCI that triggers the "first" PDSCH contains the necessary information about resource and antenna port allocation, number of layers for the PDSCH, etc., and then the same payload is repeated in each of the PDSCH repetition resources configured at the higher layer except for the RV and TCI states that can be swapped.

[0302] Note that PDSCH repetition options can be combined with, for example, micro-slot based and frequency based simultaneously. Also, the Rel-15 single layer limit for PDSCH can be removed to further give the possibility of reducing latency by increasing the spectral efficiency of PDSCH transmission.

[0303] Thus, if the UE supports four-layer reception, the resources for each PDSCH can be configured to be overlapping (via RRC) and then the DCI triggers two PDSCHs each with two layers. The same data payload is sent in the two PDSCHs but from different TRP / TCI states / CDM groups.

[0304] The RRC configures resources (time slot aggregation) for repetition as in Rel.15, and the DCI schedules one PDSCH. Further study can be carried out on what DCI can indicate, e.g., whether the DCI can select between overlapping or non-overlapping resources, the number of repetitions, which TCI states should be used for the PDSCH, etc.

[0305] Recommendation : The higher layer configures the UE with the possible resource locations for each repetition of the PDSCH, including repetition locations in time (e.g., based on single or multiple time slots or based on micro-slots) and frequency (e.g., non-overlapping or overlapping). FFS: Whether and how the DCI can dynamically select between these higher layer configured repetition resources and the associated TCI states.

[0306] For PDCCH robustness, a method similar to that for PDSCH can be adopted, where the same DCI is repeated across multiple CORESETs because each CORESET is configured with a separate TCT state. Note that, as discussed above, PDCCH repetition and PDSCH repetition can be configured independently as needed. For the PDSCH repetition to be enabled, only a single DCI needs to be received, and whether this DCI is also repeated using multiple PDCCHs in different CORESETs is a separate discussion.

[0307] Recommendation : The UE can be configured with a search space repetition set across N > 1 CORESETs, where the same search space is repeated in each CORESET. For a given PDCCH candidate with a given DCI size, in one search space / CORESET, there is a corresponding candidate in each search space within the repetition set of N. All corresponding candidates have the same DCI size and aggregation level.

[0308] Through this repetition, the UE can perform soft combining of N PDCCH candidates to improve DCI detection reliability.

[0309] Conclusion

[0310] The above discussion identifies the various suggestions outlined below:

[0311] Recommendation 1 : Schedule one PDSCH for each PDCCH of the UE that supports multiple PDCCH receptions (at least for eMBB), and Rel.16 UEs are not expected to be scheduled in the following cases:

[0312] ● Partially overlapping PDSCHs in time-domain and frequency-domain resource allocations

[0313] · More than one PDSCH with DMRS in the same CDM group for overlapping PDSCH resource allocations

[0314] · The aggregated number of layers of all PDSCHs across overlapping time-frequency resources that is greater than the maximum number of layers supported / configured by the UE

[0315] · The aggregated number of CWs of all PDSCHs across overlapping time-frequency resources that is greater than two

[0316] Recommendation 2 : Support a mechanism to extend the PDSCH resource mapping around multiple reserved resources from different gNBs, i.e., the configured CORESET, ZP-CSI-RS-ResourceSet, and lte-CRS-ToMatchAround, which includes dynamic resource mapping around the detected PDCCH

[0317] Recommendation 3 : RAN1 concludes that there is no change in the CW-to-layer mapping and the number of CWs per transmission rank in Rel-16.

[0318] Recommendation 4 : When the UE is configured for DMRS type 1 and type 2 respectively and the source RS pair λ can be used to derive the QCL characteristics of the DMRS ports for the CDM group λ, the TCI state can be configured with one, two, or three source RS pairs for QCL.

[0319] · For DMRS type 1, the TCI state can be configured to include: for each of the two CDM groups respectively, {{qcl-Type 1, qcl-Type2}λ = 0, {qcl-Type 1, qcl-Type2}λ = 1}

[0320] ● For DMRS type 2, the TCI state can be configured to include: for each of the three CDM groups respectively, {{qcl-Type1,qcl-Type2}λ = 0,{qcl-Type1,qcl-Type2}λ = 1,{qcl-Type1,qcl-Type2}

[0321] λ = 2}

[0322] Recommendation 5 : Study whether it is beneficial to increase the number of bits in the DCI for selecting the active TCI state to accommodate more transmission hypotheses (without increasing the maximum number of active tracked QCL source RSs).

[0323] Recommendation 6 : Add a row to the DMRS type 1 antenna port indication table using ports 0, 2, 3 to allow scheduling of (1, 2) layers in two CDM groups respectively.

[0324] Recommendation 7 : Add rows to the DMRS type 2 antenna port indication table for PDSCH using the following:

[0325] ● Ports 0, 2, 4 to allow scheduling of (1, 1, 1) layers

[0326] ● Ports 0, 2 to allow scheduling of (1, 1, 0) layers

[0327] ● Ports 0, 4 to allow scheduling of (1, 0, 1) layers

[0328] ● Ports 0, 2, 3 to allow scheduling of (1, 2, 0) layers

[0329] Recommendation 8: For CSI feedback, study UE-assisted multi / single TRP hypothesis selection feedback, where the UE decides on single or multi-TRP transmission based on measurement results and indicates the preferred hypothesis to the network.

[0330] Recommendation 9 : A DCI can trigger the repetition of PDSCH transmissions with the same payload, where each PDSCH can be configured with a TCI state different from the active TCI state set.

[0331] Recommendation 10 : The higher layers configure the UE with possible resource locations for each repetition of the PDSCH, including repetition locations in time (e.g., based on single or multiple time slots or based on mini-slots) and frequency (e.g., non-overlapping or overlapping). FFS: Whether and how the DCI can dynamically select between these higher layer-configured repetition resources and the associated TCI states.

[0332] Recommendation 11 : The UE can be configured with a search space repetition set across N > 1 CORESTs, where the same search space is repeated in each CORESET. For a given PDCCH candidate with a given DCI size, in one search space / CORESET, there is a corresponding candidate in each search space in the repetition set of N. All corresponding candidates have the same DCI size and aggregation level.

[0333] The embodiments described above can be referred to Figures 11 to 12 Further shown, Figures 10 to 11 Exemplary methods (e.g., procedures) performed by the UE and network nodes are depicted respectively. In other words, the various features of the operations described below correspond to the various embodiments described above.

[0334] In particular, Figure 11 A flowchart of an exemplary method (e.g., procedure) for communicating via multiple nodes in a wireless network according to various exemplary embodiments of the present disclosure is shown. The exemplary method can be performed by a user equipment (UE, e.g., a wireless device, an IoT device, a modem, etc. or its components) communicating with one or more network nodes (e.g., a base station, a gNB, an en-gNB, etc. or its components) in a wireless network (RAN, e.g., an NG-RAN). For example, Figure 11 The exemplary method shown can be implemented in a UE configured as described herein with reference to other figures. Additionally, Figure 11 The exemplary method shown can cooperate with other exemplary methods described herein (e.g., Figure 12 ) to provide the various exemplary benefits described herein. Although Figure 11Specific boxes are shown in a specific order, but the operations of the exemplary method may be performed in an order different from that shown and may be combined and / or divided into boxes with functions different from those shown. Optional boxes or operations are indicated by dashed lines.

[0335] The exemplary method may include the operation of block 1110, where the UE may receive multiple transmission configuration indication (TCI) states from a wireless network. In some embodiments, the multiple TCI states may be associated with one of the following: a corresponding multiple of nodes in the wireless network; or a corresponding multiple of beams associated with one or more nodes in the wireless network.

[0336] The exemplary method may further include the operation of block 1120, where the UE may receive scheduling information for a corresponding multiple of physical data channels carrying corresponding multiples of data blocks via a single physical control channel. For example, as discussed above, the physical control channel may be a PDCCH, and the scheduling information may be scheduling DCI. In some embodiments, the multiple physical data channels may be corresponding layers of a physical downlink shared channel (PDSCH). In other embodiments, each physical data channel may be a subset of all layers of the PDSCH.

[0337] In some embodiments, the scheduling information may further include an indicator for resources for receiving one or more of the repetitions. The indicated resources may be in at least one of the following dimensions: time, frequency, and spatial layer. In some embodiments, the resources for at least two of the repetitions may be in the same symbol set within a time slot.

[0338] In other embodiments, the scheduling information may include an indicator for a first resource for receiving a first repetition. In such embodiments, the exemplary method may further include the operation of block 1230, where the UE may receive one or more offsets to be applied to the first resource to determine other resources for receiving the remaining repetitions of the repetition. In such embodiments, the other resources may be in one of the following relative to the first resource: one or more subsequent time slots, or one or more subsequent symbols within the same time slot.

[0339] In some embodiments, the indicated resources for at least two of the repetitions may completely overlap in frequency. In such embodiments, the scheduling information further includes at least one of the following items for each of the completely overlapping repetitions: a unique set of demodulation reference signal (DMRS) ports; DMRS ports from a unique code division multiplexing (CDM) group; and a unique data scrambling seed.

[0340] In some embodiments, the scheduling information may further include an indicator of the mapping between the multiple repetitions and multiple redundancy versions (RVs) of the data block.

[0341] The exemplary method may further include the operation of block 1140, where the UE may assign one or more TCI states in the TCI state to multiple repetitions. In some embodiments, the multiple TCI states are less than the multiple repetitions, and the multiple TCI states are assigned to the repetitions in a predefined order. As an illustrative example, each physical data channel (carrying the corresponding repetition) may use one of the activated TCI states (the TCI state provided to the UE in block 1110) in a predefined order and be transmitted by a different TRP. The UE may also know the predefined order and assign the TCI states to the repetitions in a corresponding manner.

[0342] In other embodiments, the scheduling information may further include an indicator of the mapping between one or more TCI states in the TCI state and the multiple repetitions. In such embodiments, one or more TCI states are assigned to the repetitions based on the indicated mapping. In some of these embodiments, the indicator is included in a field having multiple code points, and the multiple TCI states are less than the multiple code points. In such embodiments, a first subset of the code points may be associated with individual TCI states, and a second subset of the code points may be associated with a combination of individual TCI states.

[0343] In some embodiments, each TCI state includes one or more source reference signal (RS) pairs, where each source RS pair has a corresponding quasi-co-location (QCL) relationship pair for the DM-RS that is mapped to a specific physical data channel. For example, the QCL relationship pair may include any of the QCL relationship types A-D discussed above. In such embodiments, these exemplary methods may further include the operation of block 1150, in which, for each TCI state among the multiple TCI states, the UE may determine channel parameters based on the source RS pairs included in the specific TCI state.

[0344] The exemplary method may further include the operation of block 1160, in which the UE may receive multiple repetitions via multiple physical data channels based on the scheduling information and the assigned TCI states. In some embodiments, the operation of block 1160 may include the operations of sub-blocks 1161-1163 for each of the physical data channels. In sub-block 1161, the UE may receive the DM-RS mapped to the physical data channel based on the channel parameters (e.g., determined for the source RS pairs in block 1150). In this way, the UE may use the source RS pairs and the QCL relationships to receive the target RS, e.g., the DM-RS. In sub-block 1162, the UE may determine further channel parameters based on the received DM-RS. In sub-block 1163, the UE may receive the physical data channel based on the further channel parameters.

[0345] In addition, Figure 12illustrates an exemplary method (e.g., process) for communicating with a single user equipment (UE) via multiple physical data channels according to various exemplary embodiments of the present disclosure. The exemplary method may be performed by one or more network nodes (e.g., base stations, eNBs, gNBs, en-gNBs, etc. or components thereof) of a wireless network (e.g., NG-RAN, E-UTRAN). For example, Figure 12 the illustrated exemplary method may be implemented in one or more network nodes of a wireless network configured as described herein with reference to other figures. Additionally, Figure 12 the illustrated exemplary method may be used in cooperation with other exemplary methods described herein (e.g., Figure 11 ) to provide various exemplary benefits and / or advantages. Although Figure 12 specific boxes are shown in a particular order, the operations of the exemplary method may be performed in an order different from that shown and may be combined and / or divided into boxes with functions different from those shown. Optional boxes or operations are indicated by dashed lines.

[0346] The exemplary method may include an operation in block 1210, in which the wireless network may send multiple transmission configuration indication (TCI) states to the UE. In some embodiments, the multiple TCI states may be associated with one of the following: a corresponding multiple of nodes in the wireless network; or a corresponding multiple of beams associated with one or more nodes in the wireless network.

[0347] The exemplary method may further include an operation in block 1220, in which the wireless network may assign one or more of the TCI states to multiple repetitions of data blocks to be carried by the corresponding multiple physical data channels. In some embodiments, the multiple TCI states may be less than the multiple repetitions, and the multiple TCI states may be assigned to the repetitions in a predefined order. As an illustrative example, each physical data channel (carrying a corresponding repetition) may use one of the TCI states of the activated TCI states (the TCI states provided to the UE in block 1210) in a predefined order to be transmitted by different TRPs. The UE may also know the predefined order and assign the TCI states to the repetitions in a corresponding manner.

[0348] The exemplary method may further include an operation in block 1230, in which the wireless network may send scheduling information for the corresponding multiple physical data channels carrying data blocks via a single physical control channel. For example, as discussed above, the physical control channel may be a PDCCH, and the scheduling information may be scheduling DCI. In some embodiments, the multiple physical data channels may be corresponding layers of a physical downlink shared channel (PDSCH). In other embodiments, each physical data channel may be a subset of all layers of the PDSCH.

[0349] In some embodiments, the scheduling information may further include an indicator for receiving resources for one or more repetitions of a repetition. The indicated resources may be in at least one of the following dimensions: time, frequency, and spatial layer. In some embodiments, the resources for at least two of the repetitions may be in the same symbol set within a time slot.

[0350] In other embodiments, the scheduling information may include an indicator for a first resource for receiving a first repetition of a repetition. In such embodiments, the exemplary method may further include the operation of block 1240, in which the wireless network may send one or more offsets that are to be applied to the first resource to determine other resources for receiving the remaining repetitions of the repetition. In such embodiments, the other resources may be in one of the following: one or more subsequent time slots relative to the first resource, or one or more subsequent symbols within the same time slot relative to the first resource.

[0351] In some embodiments, the indicated resources for at least two of the repetitions may completely overlap in frequency. In such embodiments, the scheduling information may further include at least one of the following items for each of the completely overlapping repetitions: a unique set of demodulation reference signal (DMRS) ports; DMRS ports from a unique code division multiplexing (CDM) group; and a unique data scrambling seed.

[0352] In some embodiments, the scheduling information may further include an indicator of a mapping between a plurality of repetitions and a plurality of redundant versions (RVs) of a data block.

[0353] In some embodiments, the scheduling information may further include an indicator of a mapping between one or more of the TCI states and a plurality of repetitions. For example, in block 1220, the mapping may reflect and / or indicate the allocation of TCI states to repetitions. In some of these embodiments, the indicator is included in a field having a plurality of code points, and a plurality of TCI states is less than the plurality of code points. In such embodiments, a first subset of the code points may be associated with individual TCI states, and a second subset of the code points may be associated with a combination of individual TCI states.

[0354] In some embodiments, each TCI state includes one or more source reference signal (RS) pairs, where each source RS pair has a corresponding quasi-co-location (QCL) relationship pair for the DM-RS that is mapped to a specific physical data channel. For example, the QCL relationship pair may include any of the QCL relationship types A-D discussed above. In such embodiments, the exemplary methods may further include the operation of block 1250, in which the wireless network may send, for each of the plurality of TCI states, the source RS pairs included in a specific TCI state.

[0355] The exemplary method may further include the operation of block 1260, wherein the wireless network may transmit multiple repetitions via multiple physical data channels based on scheduling information and the allocated TCI state. In some embodiments, the operation of block 1260 may include the operation of sub-block 1261, wherein the wireless network may transmit the corresponding DM-RS associated with the physical data channel to which they are mapped. This may facilitate the UE to receive the target RS (e.g., DM-RS) associated with a specific physical data channel by utilizing the source RS pair and the QCL relationship.

[0356] Although the various embodiments have been described above in terms of methods, techniques, and / or processes, those of ordinary skill in the art will readily understand that such methods, techniques, and / or processes may be implemented by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, computer program products, etc.

[0357] Figure 13 A block diagram of an exemplary wireless device or user equipment (UE) 1300 (referred to herein as "UE 1300") in accordance with various embodiments of the present disclosure, including the embodiments described above with reference to other figures, is shown. For example, UE 1300 may be configured to perform operations corresponding to one or more of the exemplary methods described herein by executing instructions stored on a computer-readable medium.

[0358] UE 1300 may include a processor 1310 (also referred to as "processing circuitry") operatively connected to a program memory 1320 and / or a data memory 1330 via a bus 1370, which may include parallel address and data buses, serial ports, or other methods and / or structures known to those of ordinary skill in the art. The program memory 1320 may store software code, programs, and / or instructions (collectively shown as Figure 13a computer program product 1321) therein, the software code, program, and / or instructions, when executed by the processor 1310, can configure and / or facilitate the UE 1300 to perform various operations, including operations corresponding to the various exemplary methods described herein. As part of or in addition to such operations, the execution of such instructions can configure and / or facilitate the UE 1300 to communicate using one or more wired or wireless communication protocols, including one or more wireless communication protocols standardized by 3GPP, 3GPP2, or IEEE, such as protocols commonly referred to as 5G / NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, 1xRTT, CDMA2000, 802.11WiFi, HDMI, USB, Firewire, etc., or any other current or future protocol that can be used in conjunction with the radio transceiver 1340, the user interface 1350, and / or the control interface 1360.

[0359] As another example, the processor 1310 can execute program code stored in the program memory 1320 that corresponds to the MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP (e.g., for NR and / or LTE). As a further example, the processor 1310 can execute program code stored in the program memory 1320 that, together with the radio transceiver 1340, implements the corresponding PHY layer protocols, such as orthogonal frequency division multiplexing (OFDM), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). As another example, the processor 1310 can execute program code stored in the program memory 1320 that, together with the radio transceiver 1340, implements device-to-device (D2D) communication with other compatible devices and / or UEs.

[0360] The program memory 1320 may also include software code executed by the processing UE 1310 to control the functions of the UE 1300, including configuring and controlling various components, such as the radio transceiver 1340, the user interface 1350, and / or the control interface 1360. The program memory 1320 may also include one or more applications and / or modules, including computer-executable instructions for implementing any of the exemplary methods described herein. Such software code may be specified or written using any known or future-developed programming language, such as, for example, Java, C++, C, Objective C, HTML, XHTML, machine code, and assembler, so long as, for example, the desired functionality defined by the method steps being implemented is preserved. Additionally, or alternatively, the program memory 1320 may include an external storage arrangement (not shown) remote from the UE 1300 from which instructions may be downloaded to the program memory 1320 located within or removably coupled to the UE 1300 to enable execution of such instructions.

[0361] The data memory 1330 may include memory areas for the processor 1310 to store variables used in the protocols, configurations, controls, and other functions of the UE 1300, including operations corresponding to or including any of the exemplary methods described herein. Moreover, the program memory 1320 and / or the data memory 1330 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or a combination thereof. Additionally, the data memory 1330 may include a memory slot through which removable memory cards (e.g., SD cards, memory sticks, compact flash, etc.) having one or more formats may be inserted and removed.

[0362] One of ordinary skill in the art will recognize that the processor 1310 may include multiple individual processors (including, for example, multi-core processors), each of which implements a portion of the functions described above. In such cases, the multiple individual processors may be commonly connected to the program memory 1320 and the data memory 1330 or individually connected to multiple individual program memories and / or data memories. More generally, one of ordinary skill in the art will recognize that the various protocols and other functions of the UE 1300 may be implemented in many different computer arrangements, including different combinations of hardware and software, including but not limited to application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed and / or programmable digital circuits, analog baseband circuits, radio frequency circuits, software, firmware, and middleware.

[0363] The radio transceiver 1340 may include radio frequency transmitter and / or receiver functions that facilitate the UE 1300 to communicate with other devices supporting similar wireless communication standards and / or protocols. In some exemplary embodiments, the radio transceiver 1340 includes one or more transmitters and one or more receivers that enable the UE 1300 to communicate according to various protocols and / or methods proposed by 3GPP and / or other standard bodies for standardization. For example, such functions may operate in cooperation with the processor 1310 to implement the PHY layer based on OFDM, OFDMA, and / or SC-FDMA technologies, such as those described herein with respect to other figures.

[0364] In some exemplary embodiments, the radio transceiver 1340 includes one or more transmitters and one or more receivers that may facilitate the UE 1300 to communicate with various LTE, LTE-Evolution (LTE-A), and / or NR networks according to standards promulgated by 3GPP. In some exemplary embodiments of the present disclosure, the radio transceiver 1340 includes the circuitry, firmware, etc. required for the UE 1300 to also communicate with various NR, NR-U, LTE, LTE-A, LTE-LAA, UMTS, and / or GSM / EDGE networks according to 3GPP standards. In some embodiments, the radio transceiver 1340 may include circuitry to support D2D communication between the UE 1300 and other compatible devices.

[0365] In some embodiments, the radio transceiver 1340 includes the circuitry, firmware, etc. required for the UE 1300 to communicate with various CDMA2000 networks according to 3GPP2 standards. In some embodiments, the radio transceiver 1340 may be capable of communicating using radio technologies operating in unlicensed frequency bands, such as IEEE802.11 WiFi operating at frequencies in the 2.4, 5.6, and / or 60 GHz regions. In some embodiments, the radio transceiver 1340 may include a transceiver capable of wired communication, such as by using IEEE 802.3 Ethernet technology. The functions specific to each of these embodiments may be coupled to and / or controlled by other circuitry in the UE 1300, such as the processor 1310 that executes program code stored in the program memory 1320 and / or supported by the data memory 1330 in conjunction with the data memory 1330.

[0366] The user interface 1350 may take various forms depending on the particular implementation of the UE 1300, or may be entirely absent from the UE 1300. In some embodiments, the user interface 1350 may include a microphone, a speaker, a slide button, a depressible button, a display, a touchscreen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and / or any other user interface features commonly found on a mobile phone. In other embodiments, the UE 1300 may include a tablet computing device, including a larger touchscreen display. In such embodiments, one or more of the mechanical features of the user interface 1350 may be replaced by comparable or functionally equivalent virtual user interface features (e.g., virtual keypad, virtual buttons, etc.) implemented using the touchscreen display. In other embodiments, the UE 1300 may be a digital computing device, such as a laptop computer, a desktop computer, a workstation, etc., including a mechanical keyboard that may be integrated, disassembled, or detachable depending on the particular exemplary embodiment. Such digital computing devices may also include a touchscreen display. Many exemplary embodiments of the UE 1300 with a touchscreen display are capable of receiving user input, such as input related to the exemplary methods described herein or otherwise known to those of ordinary skill in the art.

[0367] In some embodiments, the UE 1300 may include an orientation sensor that may be used in various ways through the features and functions of the UE 1300. For example, the UE 1300 may use the output of the orientation sensor to determine when the user has changed the physical orientation of the touchscreen display of the UE 1300. The indication signal from the orientation sensor may be used in any application executed on the UE 1300 such that the application may automatically change the orientation of the screen display (e.g., from portrait to landscape) when the indication signal indicates an approximately 90-degree change in the physical orientation of the device. In this exemplary manner, the application may maintain the screen display in a manner readable by the user regardless of the physical orientation of the device. Additionally, the output of the orientation sensor may be used in conjunction with the various exemplary embodiments of the present disclosure.

[0368] The control interface 1360 of the UE 1300 may take various forms depending on the particular exemplary embodiment of the UE 1300 and the particular interface requirements of other devices that the UE 1300 is intended to communicate with and / or control. For example, the control interface 1360 may include an RS-232 interface, an RS-4135 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE (“FireWire”) interface, an I 2C interfaces, PCMCIA interfaces, etc. In some exemplary embodiments of the present disclosure, the control interface 1360 may include, for example, an IEEE 802.3 Ethernet interface as described above. In some exemplary embodiments of the present disclosure, the control interface 1360 may include an analog interface circuit, including, for example, one or more digital-to-analog converters (DACs) and / or analog-to-digital converters (ADCs).

[0369] Those of ordinary skill in the art will recognize that the above list of features, interfaces, and radio communication standards is merely exemplary and is not limited to the scope of the present disclosure. In other words, the UE 1300 may include more functions than Figure 13 shown, including, for example, video and / or still image cameras, microphones, media players, and / or video recorders, etc. Moreover, the radio transceiver 1340 may include circuitry required to communicate using additional radio communication standards, including Bluetooth, GPS, and / or others. In addition, the processor 1310 may execute software code stored in the program memory 1320 to control such additional functions. For example, the direction speed and / or position estimate output from the GPS receiver may be used in any application executed on the UE 1300, including any program code corresponding to and / or implementing any exemplary embodiment described herein (e.g., of a method).

[0370] Figure 14 A block diagram of an exemplary network node 1400 is shown in accordance with various embodiments of the present disclosure (including the embodiments described above with reference to other figures). For example, the exemplary network node 1400 may be configured to perform operations corresponding to one or more of the exemplary methods described herein by executing instructions stored on a computer-readable medium. In some exemplary embodiments, the network node 1400 may include a base station, eNB, gNB, or one or more components thereof. For example, in accordance with the NR gNB architecture specified by 3GPP, the network node 1400 may be configured as a central unit (CU) and one or more distributed units (DU). More generally, the functions of the network node 1400 may be distributed across various physical devices and / or functional units, modules, etc.

[0371] The network node 1400 may include a processor 1410 (also referred to as a "processing circuit") operably connected to a program memory 1420 and a data memory 1430 via a bus 1470, which may include parallel address and data buses, serial ports, or other methods and / or structures known to those of ordinary skill in the art.

[0372] The program memory 1420 may store software code, programs, and / or instructions (collectively shown as Figure 14The computer program product 1421), the software code, program, and / or instructions of which, when executed by the processor 1410, can configure and / or facilitate the network node 1400 to perform various operations, including operations corresponding to the various exemplary methods described herein. As part of and / or in addition to such operations, the program memory 1420 may also include software code executed by the processor 1410, which can configure and / or facilitate the network node 1400 to communicate with one or more other UEs or network nodes using other protocols or protocol layers, such as one or more of the PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or NR, or any other higher layer (e.g., NAS) protocol used in combination with the radio network interface 1440 and / or the core network interface 1450. By way of example, the core network interface 1450 may include an S1 or NG interface, and the radio network interface 1440 may include a Uu interface standardized by 3GPP. The program memory 1420 may also include software code executed by the processor 1410 to control the functions of the network node 1400, including configuring and controlling various components, such as the radio network interface 1440 and the core network interface 1450.

[0373] The data memory 1430 may include memory areas for the processor 1410 to store variables used in the protocols, configurations, controls, and other functions of the network node 1400. Thus, the program memory 1420 and the data memory 1430 may include non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g., "cloud") storage devices, or combinations thereof. Those of ordinary skill in the art will recognize that the processor 1410 may include multiple individual processors (not shown), each of which implements a part of the functions described above. In such cases, the multiple individual processors may be commonly connected to the program memory 1420 and the data memory 1430 or individually connected to multiple individual program memories and / or data memories. More generally, those of ordinary skill in the art will recognize that the various protocols and other functions of the network node 1400 may be implemented in many different combinations of hardware and software, including but not limited to application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed digital circuits, programmable digital circuits, analog baseband circuits, radio frequency circuits, software, firmware, and middleware.

[0374] The radio network interface 1440 may include a transmitter, a receiver, a signal processor, an ASIC, an antenna, a beamforming unit, and other circuitry that enables the network node 1400 to communicate with other devices, such as, in some embodiments, a plurality of compatible user equipment (UE). In some embodiments, the interface 1440 may also enable the network node 1400 to communicate with a compatible satellite communication of a satellite communication network. In some exemplary embodiments, the radio network interface 1440 may include various protocols or protocol layers, such as the PHY, MAC, RLC, PDCP, and / or RRC layer protocols standardized by 3GPP for LTE, LTE-A, LTE-LAA, NR, NR-U, etc.; improvements thereto, such as those described hereinabove; or any other higher layer protocol used in conjunction with the radio network interface 1440. According to further exemplary embodiments of the present disclosure, the radio network interface 1440 may include a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technologies. In some embodiments, the functions of such a PHY layer may be provided by the cooperation of the radio network interface 1440 and the processor 1410 (including program code in the memory 1420).

[0375] The core network interface 1450 may include a transmitter, a receiver, and other circuitry that enables the network node 1400 to communicate with other devices in the core network, such as, in some embodiments, a circuit-switched (CS) and / or packet-switched core (PS) network. In some embodiments, the core network interface 1450 may include the S1 interface standardized by 3GPP. In some embodiments, the core network interface 1450 may include the NG interface standardized by 3GPP. In some exemplary embodiments, the core network interface 1450 may include one or more interfaces to one or more AMF, SMF, SGW, MME, SGSN, GGSN, and other physical devices, the AMF, SMF, SGW, MME, SGSN, GGSN, and other physical devices including functions found in GERAN, UTRAN, EPC, 5GC, and CDMA2000 core networks known to those of ordinary skill in the art. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, the lower layers of the core network interface 1450 may include one or more of the following: asynchronous transfer mode (ATM), Internet protocol over Ethernet (IP), SDH over fiber optic, T1 / E1 / PDH over copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.

[0376] In some embodiments, network node 1400 may include hardware and / or software that configures and / or facilitates network node 1400 to communicate with other network nodes in a RAN (also referred to as a “radio access network”), such as communicating with other eNBs, gNBs, ng-eNBs, en-gNBs, IAB nodes, etc. Such hardware and / or software may be part of radio network interface 1440 and / or core network interface 1450, or it may be a separate functional unit (not shown). For example, such hardware and / or software may configure and / or facilitate network node 1400 to communicate with other RAN nodes via an X2 or Xn interface standardized by 3GPP.

[0377] OA&M interface 1460 may include a transmitter, a receiver, and other circuitry that enables network node 1400 to communicate with external networks, computers, databases, etc., for the operation, administration, and maintenance of network node 1400 or other network devices operatively connected thereto. The lower layer of OA&M interface 1460 may include one or more of the following: Asynchronous Transfer Mode (ATM), Internet Protocol over Ethernet (IP), SDH over fiber optic, T1 / E1 / PDH over copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art. Also, in some embodiments, one or more of radio network interface 1440, core network interface 1450, and OA&M interface 1460 may be multiplexed together on a single physical interface, such as the examples listed above.

[0378] Figure 15 is a block diagram of an exemplary communication network configured to provide an over-the-top (OTT) data service between a host computer and a user equipment (UE) according to various exemplary embodiments of the present disclosure. UE 1510 may communicate with a radio access network (RAN, also referred to as a “radio network”) 1530 via radio interface 1520, which may be based on the protocols described above, including, for example, LTE, LTE-A, and 5G / NR. For example, UE 1510 may be configured and / or arranged as shown in the other figures discussed above.

[0379] RAN 1530 may include one or more terrestrial network nodes (e.g., base stations, eNBs, gNBs, controllers, etc.) operable in an authorized frequency band, and one or more network nodes operable in an unlicensed spectrum (using, for example, LAA or NR-U technologies), such as the 2.4-GHz band and / or the 5-GHz band. In such cases, the network nodes including RAN 1530 may operate cooperatively using both authorized and unlicensed spectrums. In some embodiments, RAN 1530 may include or be capable of communicating with one or more satellites including a satellite access network.

[0380] RAN 1530 may also communicate with the core network 1540 according to the various protocols and interfaces described above. For example, one or more devices including RAN 1530 (e.g., base stations, eNBs, gNBs, etc.) may communicate with the core network 1540 via the core network interface 1550 described above. In some exemplary embodiments, RAN 1530 and the core network 1540 may be configured and / or arranged as shown in the other figures discussed above. For example, an eNB including E-UTRAN 1530 may communicate with an EPC core network 1540 via the S1 interface. As another example, an ng-eNB and a gNB including NG-RAN 1530 may communicate with a 5GC core network 1530 via the NG interface.

[0381] According to the various protocols and interfaces known to those of ordinary skill in the art, the core network 1540 may also communicate with an external packet data network, shown as the Internet 1550 in Figure 15 . Many other devices and / or networks may also be connected and communicate via the Internet 1550, such as the exemplary host computer 1560. In some exemplary embodiments, the host computer 1560 may use the Internet 1550, the core network 1540, and RAN 1530 as middleware to communicate with the UE 1510. The host computer 1560 may be a server (e.g., an application server) under the ownership and / or control of a service provider. The host computer 1560 may be operated by an OTT service provider or by another entity on behalf of the service provider.

[0382] For example, the host computer 1560 may use the facilities of the core network 1540 and RAN 1530 to provide over-the-top (OTT) packet data services to the UE 1510, and the facilities of the core network 1540 and RAN 1530 may not know the routing of the output / input communication to / from the host computer 1560. Similarly, the host computer 1560 may not know the routing of the transmission from the host computer to the UE, e.g., the routing of the transmission through RAN 1530. Various OTT services may be provided using Figure 15 the exemplary configuration shown, including, for example, streaming (one-way) audio and / or video from the host computer to the UE, interactive (one-way) audio and / or video between the host computer and the UE, interactive messaging or social networking, interactive virtual or augmented reality, etc.

[0383] Figure 15The exemplary network shown may also include measurement procedures and / or sensors that monitor network performance metrics, including data rate, latency, and other factors improved by the exemplary embodiments disclosed herein. The exemplary network may also include functionality for reconfiguring the link between endpoints (e.g., host computers and UEs) in response to changes in the measurement results. Such procedures and functionality are known and practiced; if the network hides or extracts the radio interface from an OTT service provider, the measurement may be facilitated by dedicated signaling between the UE and the host computer.

[0384] The exemplary embodiments described herein provide effective techniques for ultra-reliable low-latency communication (URLLC) by configuring a UE - such as UE 1510 - to transmit and / or receive multiple versions of data blocks on separate physical data channels (e.g., PDSCH or PUSCH). In this way, PDSCH diversity can be achieved through multi-TRP transmission to a single UE even when only a single PDCCH is used to convey the configuration of multiple transmissions and / or receptions of data blocks. This can increase reliability, reduce latency, reduce PDCCH blocking probability, and / or reduce UE complexity. When used in an NR UE (e.g., UE 1510) and a gNB (e.g., a gNB including RAN 1530), the exemplary embodiments described herein can provide various improvements, benefits, and / or performance that facilitate the use of data services with strict performance requirements (e.g., URLLC). Thus, this improves the performance of these services as experienced by OTT service providers and end users, including more consistent data throughput and lower latency without excessive UE power consumption or other degradation in the user experience.

[0385] The foregoing merely illustrates the principles of the present disclosure. In light of the teachings herein, various modifications and variations of the described embodiments will be apparent to those skilled in the art. Thus, it will be understood that those skilled in the art will be able to design numerous systems, arrangements, and programs that, although not explicitly shown or described herein, embody the principles of the present disclosure and can thus be within the spirit and scope of the present disclosure. The various exemplary embodiments may be used together with one another and interchangeably with one another, as should be understood by those of ordinary skill in the art.

[0386] As used herein, the term unit may have its conventional meaning in the field of electronic devices, electrical equipment, and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, outputs, and / or display functions, etc., such as those described herein.

[0387] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of such functional units. These functional units may be implemented via a processing circuit, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program code stored in a memory, which may include one or several types of memories, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunication and / or data communication protocols and instructions for executing one or more of the techniques described herein. In some embodiments, the processing circuit may be used to cause the corresponding functional units to perform the corresponding functions according to one or more embodiments of the present disclosure.

[0388] As described herein, a device and / or apparatus may be represented by a semiconductor chip, chip set, or (hardware) module including such chips or chip sets; however, this does not exclude the possibility that the functions of the device or apparatus are implemented as software modules rather than as the implemented hardware, such software modules being, for example, computer programs or computer program products, including executable software code portions for execution or running on a processor. Additionally, the functions of a device or apparatus may be implemented by any combination of hardware and software. A device or apparatus may also be considered as a component of multiple devices and / or apparatuses, whether cooperating functionally with each other or independently. Furthermore, devices and apparatuses may be implemented in a distributed manner throughout the system, as long as the functions of the device or apparatus are retained. Such and similar principles are considered to be known to those skilled in the art.

[0389] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will also be understood that, unless explicitly defined as such herein, the terms used herein should be interpreted as having a meaning consistent with their meaning in this specification and the context of the relevant art and will not be interpreted in an idealized or overly formal sense.

[0390] Additionally, in some instances, certain terms used in this disclosure (including the specification and drawings), such as "data" and "information", may be used synonymously. It should be understood that although these terms (and / or other terms that may be synonymous with each other) may be used synonymously herein, there may be instances where such words may be intended to be used non - synonymously. Also, to the extent that prior art knowledge has not been explicitly incorporated herein by reference above, it is hereby incorporated by reference in its entirety. All the disclosures cited are incorporated by reference in their entirety herein.

[0391] Embodiments of the techniques and apparatuses described herein also include, but are not limited to, the examples listed below:

[0392] 1. A method for receiving multiple channels, such as a Physical Downlink Shared Channel (PDSCH), where each channel carries a version of the same data payload but is optionally transmitted by different sources (such as Transmission and Reception Points (TRPs)) in a wireless communication network in different frequency resources and / or different spatial resources. Optionally, the method includes one or more of the following:

[0393] Receiving, via a network node, from the network, multiple indicators associated with the respective multiple transmission sources, such as Transmission Configuration Indicator (TCI) states, or an indication of the multiple indicators;

[0394] For one or more of the multiple transmission sources,

[0395] Determining channel parameters based on receiving one or more source Reference Signals (RSs) identified by the indicators or an indication via the multiple indicators associated with the multiple transmission sources;

[0396] Receiving, via one or more channels, such as a Physical Downlink Control Channel (PDCCH), configuration information for the multiple PDSCHs; and

[0397] Receiving the multiple PDSCHs from the multiple transmission sources according to the configuration information based on the determined channel parameters.

[0398] 2. The method according to embodiment 1, wherein each of the source RSs is associated with a different physical data channel among the multiple physical data channels.

[0399] 3. The method according to any one of embodiments 1 to 2, wherein the configuration information identifies resources for receiving at least a portion of the multiple physical data channels (e.g., PDSCH), and wherein the identified resources are in at least one of the following dimensions: time, frequency, and spatial layer.

[0400] 4. The method according to embodiment 3, wherein resources for at least two physical data channels (e.g., PDSCH) in a physical data channel do not overlap in at least one of the following dimensions: frequency and spatial layer.

[0401] 5. The method according to any one of embodiments 3 to 4, wherein resources for at least two physical data channels (e.g., PDSCH) in a physical data channel completely overlap in frequency.

[0402] 6. The method according to embodiment 5, wherein the configuration information for the completely overlapping physical data channels (e.g., PDSCH) further includes at least one of the following:

[0403] A unique set of demodulation reference signal (DMRS) ports for each overlapping physical data channel (e.g., PDSCH);

[0404] DMRS ports from different CDM groups for each overlapping physical data channel (e.g., PDSCH);

[0405] And

[0406] A unique data scrambling seed for each overlapping physical data channel (e.g., PDSCH).

[0407] 7. The method according to any one of embodiments 3 to 6, wherein:

[0408] The configuration information identifies resources for receiving a first physical data channel among a plurality of physical data channels (e.g., PDSCH); and

[0409] The method further includes: receiving, via higher layer signaling, an identification of resources for receiving the remaining physical data channels among the plurality of physical data channels (e.g., PDSCH).

[0410] 8. The method according to embodiment 7, further including: determining, based on the identified resources for receiving the first physical data channel among the plurality of physical data channels, that the number of physical data channels (e.g., PDSCH) includes a plurality.

[0411] 9. The method according to any one of embodiments 3 to 8, wherein the identified resources for receiving a plurality of physical data channels (e.g., PDSCH) include time resources located within one of the following: a plurality of time slots, and a plurality of non-overlapping OFDM symbols within a time slot.

[0412] 10. The method according to any one of embodiments 1 to 9, wherein the plurality of physical data channels (e.g., PDSCH) carry different redundancy versions (RVs) of a single data block.

[0413] 11. The method according to any one of Embodiments 1 to 10, wherein the received configuration information includes information associating at least a part of a plurality of TCI states with a plurality of PDSCHs.

[0414] 12. The method according to Embodiment 11, wherein:

[0415] the received configuration information includes information associating a first TCI state among the plurality of TCI states with a first physical data channel among the plurality of physical data channels (e.g., PDSCH); and

[0416] the method further includes: for other physical data channels among the plurality of physical data channels (e.g., PDSCH), selecting other TCI states among the plurality of TCI states according to a predetermined rule.

[0417] 13. The method according to Embodiment 12, wherein:

[0418] the information associating the plurality of TCI states with the plurality of physical data channels (e.g., PDSCH) includes: a field having a plurality of code points;

[0419] each code point associated with one TCI state among the TCI states; and

[0420] a subset of the plurality of code points is used to associate a first TCI state among the plurality of TCI states with a first physical data channel among the plurality of physical data channels (e.g., PDSCH).

[0421] 14. The method according to any one of Embodiments 11 to 13, further includes: receiving a control message for activating at least a subset of the plurality of TCI states, wherein channel parameters are determined only for the activated subset of the TCI states.

[0422] 15. The method according to Embodiment 14, wherein the received configuration information includes information associating a further subset of the activated subset of the TCI states with the plurality of physical data channels (e.g., PDSCH).

[0423] 16. The method according to any one of Embodiments 1 to 15, wherein at least two physical data channels among the physical data channels (e.g., PDSCH) are in the same OFDM symbol set in a time slot.

[0424] 17. The method according to any one of Embodiments 1 to 16, wherein the source RS for each physical data channel (e.g., PDSCH) is different.

[0425] 18. A method for transmitting a plurality of channels (such as a Physical Uplink Shared Channel (PDSCH)) to a wireless communication network (e.g., to a network node such as a user equipment), wherein each channel carries a version of the same data payload, but is optionally transmitted by different sources (such as a Transmission and Reception Point (TRP)) in different frequency resources and / or in different spatial resources.

[0426] Optionally, the method includes one or more of the following:

[0427] Receiving from the network a plurality of resource indicators associated with respective ones of the plurality of transmission resources or an indication of the plurality of resource indicators associated with respective ones of the plurality of transmission resources;

[0428] For one or more of the plurality of transmission resources, determining channel parameters based on transmitting one or more source reference signals (RS) identified by the resource indicator associated with the transmission resource;

[0429] Receiving, for example via a single Physical Downlink Control Channel (e.g., PDCCH), configuration information for a plurality of physical channels (e.g., PUSCH); and

[0430] Based on the determined channel parameters, transmitting a plurality of physical channels (e.g., PUSCH) using the plurality of transmission resources according to the configuration information.

[0431] 19. The method according to embodiment 18, wherein each of the source RSs is associated with a different physical channel among the plurality of physical channels (e.g., PUSCH).

[0432] 20. The method according to any one of embodiments 18 to 19, wherein the configuration information identifies resources for transmitting at least a portion of the plurality of physical channels (e.g., PUSCH), and wherein the identified resources are in at least one of the following dimensions: time, frequency, and spatial layer.

[0433] 21. The method according to embodiment 20, wherein the resources for at least two PUSCHs among the PUSCHs do not overlap in at least one of the following dimensions: frequency, and spatial layer.

[0434] 22. The method according to any one of embodiments 20 to 21, wherein the resources for at least two physical channels among the physical channels (e.g., PUSCH) are fully overlapping in frequency.

[0435] 23. The method according to embodiment 22, wherein the configuration information for the fully overlapping physical channels (e.g., PUSCH) further includes at least one of the following:

[0436] A unique set of demodulation reference signal (DMRS) ports for each overlapping physical channel (e.g., PUSCH);

[0437] DMRS ports from different CDM groups for each overlapping physical channel (e.g., PUSCH); and

[0438] A unique data scrambling seed for each overlapping physical channel (e.g., PUSCH).

[0439] 24. The method according to any one of embodiments 20 to 23, wherein:

[0440] The configuration information identifies resources for transmitting a first physical channel among a plurality of physical channels (e.g., PUSCH); and / or

[0441] or

[0442] The method further includes: receiving, via higher layer signaling, an identification of resources for transmitting remaining physical channels among the plurality of physical channels (e.g., PUSCH).

[0443] 25. The method according to embodiment 24, further including: determining that the number of physical channels (e.g., PUSCH) includes a plurality based on the identified resources for transmitting a first physical data channel among the plurality of physical data channels.

[0444] 26. The method according to any one of embodiments 20 to 25, wherein the identified resources for transmitting a plurality of physical channels (e.g., PUSCH) include time resources within one of the following: a plurality of time slots, and a plurality of non-overlapping OFDM symbols within a time slot.

[0445] 27. The method according to any one of embodiments 18 to 26, wherein the plurality of physical channels (e.g., PUSCH) carry different redundancy versions (RVs) of a single data block.

[0446] 28. The method according to any one of embodiments 18 to 27, wherein the received configuration information includes information associating at least a portion of a plurality of resource indicators with the plurality of physical channels (e.g., PUSCH).

[0447] 29. The method according to embodiment 28, wherein:

[0448] The received configuration information includes information associating a first resource indicator among the plurality of resource indicators with a first physical channel among the plurality of physical channels (e.g., PUSCH); and / or

[0449] The method further includes: for other physical channels among a plurality of physical channels (e.g., PUSCH), selecting other resource indicators from among a plurality of resource indicators according to a predetermined rule.

[0450] 30. The method according to embodiment 29, wherein:

[0451] The information that associates a plurality of resource indicators with a plurality of physical channels (e.g., PUSCH) includes: a field having a plurality of code points; and / or

[0452] Each code point associated with one of the resource indicators; and / or

[0453] A subset of the plurality of code points is used to associate a first resource indicator among the plurality of resource indicators with a first physical channel among the plurality of physical channels (e.g.,

[0454] PUSCH).

[0455] 31. The method according to any one of embodiments 28 to 30, further includes: receiving a control message that at least activates a subset of the plurality of resource indicators, optionally wherein channel parameters are determined only for the activated subset of the resource indicators.

[0456] 32. The method according to embodiment 31, wherein the received configuration information includes information that associates a further subset of the activated subset of the resource indicators with a plurality of PUSCHs.

[0457] 33. The method according to any one of embodiments 18 to 32, wherein at least two physical channels among the physical channels (e.g., PUSCH) are in the same OFDM symbol set in a time slot.

[0458] 34. The method according to any one of embodiments 18 to 33, wherein the source RS for each physical channel (e.g., PUSCH) is different.

[0459] 35. A method, which is used, for example, to send a plurality of physical channels (e.g., PDSCH) to a single user equipment (UE), wherein each physical channel carries a version of the same data payload but is sent by different sources in a wireless communication network, the method includes one or more of the following:

[0460] Sending to the UE a plurality of indicators or an indication of a plurality of indicators associated with respective multiple transmission sources, e.g., transmission configuration indication (TCI) states;

[0461] For each of the multiple transmission sources, sending one or more source reference signals (RSs) identified by an indicator (e.g., a TCI state associated with the transmission source);

[0462] transmitting configuration information for a plurality of physical data channels (e.g., PDSCHs to be transmitted to a UE) to the UE via a single physical channel (e.g., PDCCH); and

[0463] transmitting a plurality of physical data channels (e.g., PDSCHs) from a plurality of transmission sources according to the configuration information.

[0464] 36. A method, for example, for receiving a plurality of physical channels (e.g., PUSCHs) from a single user equipment (UE), wherein each physical channel (e.g., PUSCH) carries a version of the same data payload but is transmitted using different resources, the method comprising one or more of the following:

[0465] transmitting an indication of a plurality of resource indicators associated with respective ones of a plurality of transmission resources to the UE;

[0466] for each of the plurality of transmission resources, determining channel parameters based on receiving one or more source reference signals (RSs) identified by a resource indicator associated with a particular transmission resource;

[0467] transmitting configuration information for a plurality of physical data channels (e.g.,

[0468] PUSCHs to be transmitted to the UE) to the UE via a single physical channel (e.g., PDCCH); and

[0469] receiving a plurality of physical data channels (e.g., PUSCHs) using the plurality of transmission resources according to the configuration information based on the determined channel parameters.

[0470] 37. A user equipment (UE), for example, configured to receive a plurality of physical channels (e.g., PDSCHs), wherein each physical channel (e.g., PDSCH) carries a version of the same data payload but is transmitted by different sources in a wireless communication network, the UE comprising one or more of the following:

[0471] a communication circuit configured to communicate with the wireless communication network; and

[0472] a processing circuit operably associated with the communication circuit and configured to perform operations corresponding to the method according to any one of exemplary embodiments 1 to 17.

[0473] 38. A user equipment (UE), for example, configured to transmit a plurality of physical channels, e.g., physical uplink shared channels (PDSCHs), wherein each physical channel (e.g., PUSCH) carries a version of the same data payload but is transmitted using different resources, the UE comprising:

[0474] A communication circuit configured to communicate with a wireless communication network; and

[0475] A processing circuit operably associated with the communication circuit and configured to perform operations corresponding to the method according to any one of exemplary embodiments 18 to 34.

[0476] 39. A radio access network (RAN), for example arranged to send a plurality of physical channels, such as a physical downlink shared channel (PDSCH), to a single user equipment (UE), wherein each physical channel (e.g., PDSCH) carries a version of the same data payload, but is sent from different sources in the RAN, the RAN comprising:

[0477] A communication circuit configured to communicate with the UE; and

[0478] A processing circuit operably associated with the communication circuit and configured to perform operations corresponding to the method according to embodiment 35.

[0479] 40. A radio access network (RAN), for example arranged to receive a plurality of physical channels, such as a physical uplink shared channel (PUSCH), from a single user equipment (UE), wherein each physical channel (e.g., PUSCH) carries a version of the same data payload, but is sent using different resources, the RAN comprising:

[0480] A communication circuit configured to communicate with the UE; and

[0481] A processing circuit operably associated with the communication circuit and configured to perform operations corresponding to the method according to embodiment 36.

[0482] 41. A non - transitory computer - readable medium storing computer - executable instructions that, when executed by at least one processor of a user equipment (UE), configure the UE to perform operations corresponding to the method according to any one of exemplary embodiments 1 to 34.

[0483] 42. A non - transitory computer - readable medium storing computer - executable instructions that, when executed by at least one processor of a radio access network (RAN), configure the RAN to perform operations corresponding to the method according to any one of exemplary embodiments 35 to 36.

[0484] Additionally, embodiments of the present disclosure include, but are not limited to, the following examples, which are divided into Group A ("receiving") and Group B ("sending"). Although the following refers to "TCI" and "SRI", these are merely examples and may also be different indicators, as recognized by those skilled in the art.

[0485] Group A

[0486] A UE, which is optionally configured by the network to receive multiple PDSCHs (or other similar channels), where each of the multiple PDSCHs is a repetition of the same data payload (or includes such a repetition), and where, optionally, the DMRS (or other similar reference signal) for each PDSCH is QCL with a configured source RS or source RS pair. One or more of the following features may further apply:

[0487] ● At least two of the PDSCHs are in the same OFDM symbol set within a time slot

[0488] ● The (one or more) source RSs for each PDSCH are different

[0489] ● The configuration is received by a DCI message (or other downlink message)

[0490] ● The configuration is received by an RRC message

[0491] ● The configuration includes a resource allocation for each of the multiple PDSCHs

[0492] · The configuration also includes a temporal repetition over multiple time slots and / or over multiple transmissions within a time slot in non - overlapping OFDM symbols (covering the case of micro - slot repetition)

[0493] · At least two PDSCHs do not overlap in frequency (FDM)

[0494] ● At least two PDSCHs completely overlap in frequency (spatial repetition)

[0495] ○ In this case, each of the overlapping PDSCHs is configured with a unique set of (one or more) DMRS ports (to maintain orthogonality of DMRS ports)

[0496] ○ In this case, each of the overlapping PDSCHs is configured with DMRSs from different CDM groups

[0497] ports

[0498] ○ In this case, each of the overlapping PDSCHs is configured with a unique data scrambling seed

[0499] · Each PDSCH uses a different RV coding

[0500] · Among them, the (one or more) source RSs for each PDSCH are obtained by associating each PDSCH with a TCI state from a set of TCI states

[0501] ○ Among them, for each PDSCH, different TCI states are selected from the set in a cyclic manner

[0502] ○ Among them, the TCI state for one PDSCH is given by a DCI state, and the TCI for another PDSCH from the set of TCI states is given by a predetermined rule

[0503]

[0504] ○ Among them, a subset of the code point values in the TCI field in the DCI is used to indicate the TCI state for one PDSCH, and another PDSCH from the set of TCI states is given by a predetermined rule

[0505]

[0506] ○ Among them, each TCI state in the set is an active TCI state activated by a MAC CE

[0507] ● Among them, the set of TCI states is configured by higher layer signaling between the network and the UE

[0508] · Among them, the set of TCI states is configured by higher layer signaling between the network and the UE, and the DCI further selects which TCI state is used for transmission

[0509] · Among them, the frequency resources occupied by each PDSCH are configured by higher layer signaling between the network and the UE

[0510] ○ Among them, the frequency resources can be configured to be overlapping ● The number of PDSCHs in a time slot is determined by the DCI

[0511] ○ Among them, the resource allocation for only one PDSCH is indicated in the DCI, and the resource allocation for the remaining PDSCHs in the time slot is determined and preconfigured by higher layer signaling

[0512] ○ Among them, the number of (one or more) PDSCHs is implicit, depending on one or more of the scheduled BW of the PDSCH indicated by the DCI, the carrier bandwidth, and the bandwidth of the bandwidth part

[0513] · Among them, the number of PDSCH transmissions in a repetition and the associated time and frequency resources, TCI state or TRP, redundancy version, and DMRS ports are jointly configured by the RRC and dynamically indicated in the DCI Group B

[0514] ​​A UE, which is optionally configured by the network to transmit multiple PUSCHs (or other similar channels), where optionally each of the multiple PUSCHs is a repetition of the same data payload, and optionally where the DMRS (or other reference signal) for each PUSCH has a spatial relationship with the source RS. Optionally, one or more of the following features may also apply:

[0515] · Where at least two of the PUSCHs are in the same OFDM symbol set within a time slot

[0516] · Where the source RS for each PUSCH is different

[0517] ● Where the configuration is received by a DCI message (or other downlink message)

[0518] · Where the configuration is received by an RRC message

[0519] · Where the configuration includes a resource allocation for each of the multiple PUSCHs

[0520] ● Where the configuration also includes a temporal repetition over multiple time slots and / or over multiple transmissions within a time slot in non-overlapping OFDM symbols (covering the case of micro-slot repetition)

[0521] ● Where at least two PUSCHs do not overlap in frequency (FDM) · Where at least two PUSCHs completely overlap in frequency (spatial repetition),

[0522] One or more of the following may apply:

[0523] ○ In this case, each of the overlapping PUSCHs is configured with a unique set of (one or more) DMRS ports (to maintain the orthogonality of the DMRS ports)

[0524] ○ In this case, each of the overlapping PUSCHs is configured with DMRS ports from different CDM groups

[0525] ○ In this case, each of the overlapping PUSCHs is configured with a unique data scrambling seed · Where each PUSCH uses a different RV coding

[0526] · Where the source RS for each PUSCH is obtained by associating each PUSCH with an SRI from an SRI set

[0527] One or more of the following may apply:

[0528] ○ Where for each PUSCH, different SRIs are selected cyclically from the set

[0529] Among them, the SRI for one PUSCH is given by DCI, and the SRI for another PUSCH from the SRI state set is given by a predetermined rule.

[0530] · Among them, the SRI state set is configured by higher layer signaling between the network and the UE.

[0531] · Among them, the SRI set is configured by higher layer signaling between the network and the UE, and among them, DCI further selects downwards.

[0532] Which SRI is used for transmission

[0533] · Among them, the frequency resources occupied by each PUSCH are configured by higher layer signaling between the network and the UE.

[0534] ○ Among them, the frequency resources can be configured to be overlapping. ● The number of PUSCHs in a time slot is determined by DCI.

[0535] ○ Among them, the resource allocation for only one PUSCH is indicated in DCI and the resource allocation for the remaining PUSCHs in the time slot is determined and preconfigured by higher layer signaling.

[0536] ○ Among them, the number of (one or more) PUSCHs is implicit and depends on the scheduled BW of the PUSCH indicated by DCI.

Claims

1. A method performed by a user equipment (UE) for communicating via multiple nodes in a wireless network, the method comprising: Receiving (1110) multiple transmission configuration indication (TCI) states; Receiving (1120) scheduling information for multiple physical data channels for respective multiple repetitions carrying data blocks via a single physical control channel; Allocating (1140) one or more of the TCI states to the multiple repetitions; And Receiving (1160) the multiple repetitions via the multiple physical data channels based on the scheduling information and the allocated TCI states.

2. The method according to claim 1, wherein: The multiple TCI states are less than the multiple repetitions; and The multiple TCI states are allocated to the repetitions in a predefined order.

3. The method according to claim 1, wherein: The scheduling information further includes an indicator of a mapping between one or more of the TCI states and the multiple repetitions; And The one or more TCI states are allocated to the repetitions based on the indicated mapping.

4. The method according to claim 3, wherein: The indicator is included in a field having multiple code points, and the multiple TCI states are less than the multiple code points; A first subset of the code points is associated with individual TCI states; and A second subset of the code points is associated with a combination of individual TCI states.

5. The method according to any one of claims 1 to 4, wherein The scheduling information further includes an indicator of resources for receiving one or more of the repetitions; and The indicated resources are in at least one of the following dimensions: time, frequency, and spatial layer.

6. The method according to claim 5, wherein, Resources for at least two of the repetitions are in the same symbol set within a time slot.

7. The method according to claim 5, wherein The scheduling information includes an indicator of a first resource for receiving a first repetition of the repetitions; And The method further includes: receiving (1130) one or more offsets to be applied to the first resource to determine other resources for receiving remaining repetitions of the repetitions.

8. The method according to claim 7, wherein The other resources are in one of the following: one or more subsequent time slots relative to the first resource, or one or more subsequent symbols within the same time slot relative to the first resource.

9. The method according to any one of claims 5 to 8, wherein The indicated resources for at least two of the repetitions completely overlap in frequency; and The scheduling information further includes at least one of the following items for each of the completely overlapping repetitions: A unique set of demodulation reference signal (DMRS) ports; DMRS ports from a unique code division multiplexing (CDM) group; and A unique data scrambling seed.

10. The method according to any one of claims 1 to 9, wherein, The scheduling information further includes an indicator of a mapping between the multiple repetitions and multiple redundancy versions (RVs) of the data block.

11. The method according to any one of claims 1 to 10, wherein: Each TCI state includes one or more source reference signal (RS) pairs; Each source RS pair has a corresponding pair of quasi - co - location (QCL) relationships with antenna ports for demodulation reference signals (DM - RS), where the DM - RS is mapped to a specific physical data channel; The method further includes: for each of the plurality of TCI states, determining (1150) channel parameters based on the source RS pairs included in the specific TCI state.

12. The method according to claim 11, wherein, Receiving (1160) the plurality of repetitions via the plurality of physical data channels further includes: for each physical data channel among the physical data channels: Based on the channel parameters, receiving (1161) the DM - RS mapped to the physical data channel; Based on the received DM - RS, determining (1162) further channel parameters; and Based on the further channel parameters, receiving (1163) the physical data channel.

13. The method according to any one of claims 1 to 12, wherein, The plurality of TCI states are associated with one of the following: The corresponding plurality of nodes in the wireless network; or The corresponding plurality of beams associated with one or more nodes in the wireless network.

14. The method according to any one of claims 1 to 13, wherein, One of the following applies: The plurality of physical data channels are the respective layers of a physical downlink shared channel (PDSCH); or Each physical data channel is a subset of all layers of the PDSCH.

15. A method performed by one or more nodes in a wireless network for communicating with a single user equipment (UE) via a plurality of physical data channels, the method including: Sending (1210) a plurality of transmission configuration indication (TCI) states to the UE; Allocating (1220) one or more of the TCI states to a plurality of repetitions of data blocks to be carried by the respective plurality of physical data channels; Sending (1230) scheduling information for the plurality of physical data channels carrying the respective plurality of repetitions to the UE via a single physical control channel; and Based on the scheduling information and the allocated TCI states, sending (1260) the plurality of repetitions via the plurality of physical data channels.

16. The method according to claim 15, wherein: The plurality of TCI states are less than the plurality of repetitions; and The plurality of TCI states are allocated to the repetitions in a predefined order.

17. The method according to claim 15, wherein: The scheduling information further includes an indicator of the mapping between one or more of the TCI states and the plurality of repetitions; and The one or more TCI states are allocated to the repetitions according to the mapping.

18. The method according to claim 17, wherein, The indicator is included in a field having a plurality of code points, and the plurality of TCI states are less than the plurality of code points; A first subset of the code points is associated with individual TCI states; and A second subset of the code points is associated with combinations of individual TCI states.

19. The method according to any one of claims 15 to 18, wherein: The scheduling information further includes an indicator of resources for sending or receiving one or more of the repetitions; and The indicated resources are in at least one of the following dimensions: time, frequency, and spatial layer.

20. The method according to claim 19, wherein, Resources for at least two of the repetitions are in the same symbol set within a time slot.

21. The method according to claim 19, wherein the scheduling information includes an indicator for a first resource for receiving a first repetition of the repetitions; and the method further includes: transmitting (1240) one or more offsets to be applied to the first resource to determine other resources for receiving remaining repetitions of the repetitions.

22. The method according to claim 21, wherein, The other resources are in one of the following: one or more subsequent time slots relative to the first resource, or one or more subsequent symbols within the same time slot relative to the first resource.

23. The method according to any one of claims 19 to 22, wherein: the indicated resources for at least two of the repetitions completely overlap in frequency; and the scheduling information further includes at least one of the following items for each of the completely overlapping repetitions: a unique set of demodulation reference signal DMRS ports; DMRS ports from a unique code division multiplexing CDM group; and a unique data scrambling seed.

24. The method according to any one of claims 15 to 23, wherein The scheduling information further includes an indicator of a mapping between the plurality of repetitions and a plurality of redundant versions RV of the data block.

25. The method according to any one of claims 15 to 24, wherein: each TCI state includes one or more source reference signal RS pairs; each source RS pair has a corresponding quasi-co-location QCL relationship pair for a demodulation reference signal DM-RS mapped to a specific physical data channel; the method further includes: for each of the plurality of TCI states, transmitting (1250) the source RS pairs included in the specific TCI state; and transmitting (1260) the plurality of repetitions via the plurality of physical data channels further includes: transmitting (1261) corresponding DM-RS associated with the physical data channel to which it is mapped.

26. The method according to any one of claims 15 to 25, wherein The plurality of TCI states are associated with one of the following: corresponding plurality of nodes in the wireless network; or corresponding plurality of beams associated with one or more nodes in the wireless network.

27. The method according to any one of claims 15 to 26, wherein, One of the following applies: the plurality of physical data channels are respective layers of a physical downlink shared channel PDSCH; or each physical data channel is a subset of all layers of the PDSCH.

28. A user equipment UE (120, 1300, 1510) configured to communicate via a plurality of nodes (105, 110, 115, 700, 750, 1400) in a wireless network (100, 799, 1530), the UE comprising: a radio transceiver circuit (1340) configured to communicate with the plurality of nodes; and a processing circuit (1310) operably coupled to the radio transceiver circuit, wherein the processing circuit and the radio transceiver circuit are configured to perform operations corresponding to the method according to any one of claims 1 to 14.

29. A user equipment UE (120, 1300, 1510) configured to communicate via a plurality of nodes (105, 110, 115, 700, 750, 1400) in a wireless network (100, 799, 1530), the UE is further arranged to perform operations corresponding to the method according to any one of claims 1 to 14.

30. A non-transitory computer-readable medium (1320) storing computer-executable instructions which, when executed by a processing circuit (1310) of a user equipment UE (120, 1300, 1510) configured to communicate via a plurality of nodes (105, 110, 115, 700, 750, 1400) in a wireless network (100, 799, 1530), configure the UE to perform operations corresponding to the method according to any one of claims 1 to 14.

31. A computer program product (1021) comprising computer-executable instructions which, when executed by a processing circuit (1010) of a user equipment UE (120, 1300, 1510) configured to communicate via a plurality of nodes (105, 110, 115, 700, 750, 1400) in a wireless network (100, 799, 1530), configure the UE to perform operations corresponding to the method according to any one of claims 1 to 14.

32. A wireless network (100, 799, 1530) comprising one or more nodes (105, 110, 115, 700, 750, 1400), the wireless network being configured to communicate with a single user equipment UE (120, 1300, 1510) via a plurality of physical shared channels, the one or more nodes comprising: a radio network interface circuit (1440) configured to communicate with the UE; and a processing circuit (1410) operably coupled to the radio network interface circuit, wherein the processing circuit and the radio network interface circuit are configured to perform operations corresponding to the method according to any one of claims 15 to 27.

33. A wireless network (100, 799, 1530) comprising one or more nodes (105, 110, 115, 700, 750, 1400), the wireless network being configured to communicate with a single user equipment UE (120, 1300, 1510) via a plurality of physical shared channels, the one or more nodes being further arranged to perform operations corresponding to the method according to any one of claims 15 to 27.

34. A non-transitory computer-readable medium (1420) stores computer-executable instructions that, when executed by a processing circuit (1410) of one or more nodes (105, 110, 115, 700, 750, 1400) in a wireless network (100, 799, 1530) configured to communicate with a single user equipment UE (120, 1300, 1510) via a plurality of physical shared channels, configure the wireless network to perform operations corresponding to the method according to any one of claims 15 to 27.

35. A computer program product (1121) includes computer-executable instructions that, when executed by a processing circuit (1110) of one or more nodes (105, 110, 115, 700, 750, 1400) in a wireless network (100, 799, 1530) configured to communicate with a single user equipment UE (120, 1300, 1510) via a plurality of physical shared channels, configure the wireless network to perform operations corresponding to the method according to any one of claims 15 to 27.

Images