Patent Description:
The new generation mobile wireless communication system (<NUM>) or new radio (NR) supports a diverse set of use cases and a diverse set of deployment scenarios. NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the downlink (i.e. from a network node, gNB, eNB, or base station, to a user equipment or UE) and both CP-OFDM and DFT-spread OFDM (DFT-S-OFDM) in the uplink (i.e. from UE to gNB). In the time domain, NR downlink and uplink physical resources are organized into equally-sized subframes of <NUM> each. A subframe is further divided into multiple slots of equal duration.

The slot length depends on subcarrier spacing. For subcarrier spacing of Δf = <NUM>, there is only one slot per subframe, and each slot always consists of <NUM> OFDM symbols, irrespectively of the subcarrier spacing.

Typical data scheduling in NR are per slot basis, an example is shown in <FIG> where the first two symbols contain physical downlink control channel (PDCCH) and the remaining <NUM> symbols contains physical data channel (PDCH), either a PDSCH (physical downlink data channel) or PUSCH (physical uplink data channel).

Different subcarrier spacing values are supported in NR. The supported subcarrier spacing (SCS) values (also referred to as different numerologies) are given by Δf = (<NUM> × <NUM>α) kHz where α ∈ (<NUM>,<NUM>,<NUM>,<NUM>,<NUM>). Δf = <NUM>kHz is the basic subcarrier spacing that is also used in LTE, the corresponding slot duration is <NUM>. For a given SCS, the corresponding slot duration is <MAT> ms.

In the frequency domain physical resource definition, a system bandwidth or a bandwidth part (BWP) is divided into resource blocks (RBs), each corresponds to <NUM> contiguous subcarriers. The basic NR physical time-frequency resource grid is illustrated in <FIG>, where only one resource block (RB) within a <NUM>-symbol slot is shown. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE).

Downlink transmissions can be dynamically scheduled, i.e., in each slot the gNB transmits downlink control information (DCI) over PDCCH about which UE data is to be transmitted to and which RBs and OFDM symbols in an indicated downlink slot the data is transmitted on. PDCCH is typically transmitted in the first few OFDM symbols in each slot in NR. The UE data are carried on PDSCH. A UE first detects and decodes PDCCH and if the decoding is successfully, it then decodes the corresponding PDSCH based on the decoded control information in the PDCCH. Uplink data transmission can also be dynamically scheduled using PDCCH. Similar to downlink, a UE first decodes uplink grants in PDCCH and then transmits data over PUSCH based the decoded control information in the uplink grant such as modulation order, coding rate, uplink resource allocation, etc..

In some situations, a gNB may need to dynamically switch between different PDSCH transmission schemes since some traffic needs to be received with high reliability while others can be received with normal reliability but with higher spectral efficiency. Thus, a need exists for the gNB to dynamically switch between different PDSCH transmission schemes when scheduling a UE for PDSCH reception. Examples of this can be found in "<NPL>.

<FIG> is a block diagram illustrating elements of a wireless device UE <NUM> (also referred to as a mobile terminal, a mobile communication terminal, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Wireless device <NUM> may be provided, for example, as discussed below with respect to wireless device QQ110 of <FIG>. ) As shown, wireless device UE may include an antenna <NUM> (e.g., corresponding to antenna QQ111 of <FIG>), and transceiver circuitry <NUM> (also referred to as a transceiver, e.g., corresponding to interface QQ114 of <FIG>) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node QQ160 of <FIG>, also referred to as a RAN node) of a radio access network. Wireless device UE may also include processing circuitry <NUM> (also referred to as a processor, e.g., corresponding to processing circuitry QQ120 of <FIG>) coupled to the transceiver circuitry, and memory circuitry <NUM> (also referred to as memory, e.g., corresponding to device readable medium QQ130 of <FIG>) coupled to the processing circuitry. The memory circuitry <NUM> may include computer readable program code that when executed by the processing circuitry <NUM> causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry <NUM> may be defined to include memory so that separate memory circuitry is not required. Wireless device UE may also include an interface (such as a user interface) coupled with processing circuitry <NUM>, and/or wireless device UE may be incorporated in a vehicle.

As discussed herein, operations of wireless device UE may be performed by processing circuitry <NUM> and/or transceiver circuitry <NUM>. For example, processing circuitry <NUM> may control transceiver circuitry <NUM> to transmit communications through transceiver circuitry <NUM> over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry <NUM> from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry <NUM>, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry <NUM>, processing circuitry <NUM> performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless devices).

<FIG> is a block diagram illustrating elements of a radio access network RAN node <NUM> (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts. (RAN node <NUM> may be provided, for example, as discussed below with respect to network node QQ160 of <FIG>. ) As shown, the RAN node may include transceiver circuitry <NUM> (also referred to as a transceiver, e.g., corresponding to portions of interface QQ190 of <FIG>) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node may include network interface circuitry <NUM> (also referred to as a network interface, e.g., corresponding to portions of interface QQ190 of <FIG>) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN. The network node may also include processing circuitry <NUM> (also referred to as a processor, e.g., corresponding to processing circuitry QQ170) coupled to the transceiver circuitry, and memory circuitry <NUM> (also referred to as memory, e.g., corresponding to device readable medium QQ180 of <FIG>) coupled to the processing circuitry. The memory circuitry <NUM> may include computer readable program code that when executed by the processing circuitry <NUM> causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry <NUM> may be defined to include memory so that a separate memory circuitry is not required.

As discussed herein, operations of the RAN node may be performed by processing circuitry <NUM>, network interface <NUM>, and/or transceiver <NUM>. For example, processing circuitry <NUM> may control transceiver <NUM> to transmit downlink communications through transceiver <NUM> over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver <NUM> from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry <NUM> may control network interface <NUM> to transmit communications through network interface <NUM> to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory <NUM>, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry <NUM>, processing circuitry <NUM> performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes).

When the UE is scheduled to receive PDSCH by a DCI, the Time domain resource (TDRA) assignment field value m of the DCI provides a row index m + <NUM> to an allocation table. The determination of the used resource allocation table is defined in sub-clause <NUM>. <NUM> of 3GPP TS <NUM> v15. When a DCI is detected in a UE specific search space for PDCCH, the PDSCH time domain resource allocation is according to an RRC configured TDRA list by an RRC parameter pdsch-TimeDomainAllocationList provided in a UE specific PDSCH configuration, pdsch-Config. Each TDRA entry in the TDRA list defines a slot offset K0 between the PDSCH and the PDCCH scheduling the PDSCH, a start and length indicator SLIV, and the PDSCH mapping type (either Type A or Type B) to be assumed in the PDSCH reception. An example of TDRA entries in a TDRA list is shown in Table <NUM>.

Demodulation reference signals (DMRS) are used for coherent demodulation of physical layer data channels, PDSCH (DL) and PUSCH (UL), as well as of physical layer downlink control channel PDCCH. The DMRS is confined to resource blocks carrying the associated physical layer data channel and is mapped on allocated resource elements (REs) of the OFDM time-frequency grid in NR such that the receiver can efficiently handle time/frequency-selective fading radio channels. A PDSCH or PUSCH can have one or multiple DMRS, each associated with an antenna por. Thus, a DMRS is also referred to a DMRS port. DMRS ports used for PDSCH or PUSCH are indicated in DCI scheduling the PDSCH or PUSCH.

The mapping of DMRS to REs is configurable in both frequency and time domain, with two mapping types in the frequency domain (configuration type <NUM> or type <NUM>). The REs in frequency domain are grouped into CDM groups, each contains a subset of subcarriers. The DMRS mapping in time domain can be single-symbol based or double-symbol based where the latter means that DMRS is mapped in pairs of two adjacent symbols.

A DMRS antenna port is mapped to the resource elements within one CDM group only. For single-symbol DMRS, two antenna ports can be mapped to each CDM group whereas for double-symbol DMRS four antenna ports can be mapped to each CDM group. Hence, the maximum number of DMRS ports for DMRS type <NUM> is either four or eight. The maximum number of DMRS ports for DM-RS type <NUM> it is either six or twelve. The mapping between a DMRS port and a CDM group is shown in Table 2a for type <NUM> DMRS and Table 2b for type <NUM> DMRS.

Several signals can be transmitted from different antenna ports of the same base station. These signals can have the same large-scale properties, for instance in terms of Doppler shift/spread, average delay spread, or average delay, when measured at the receiver. These antenna ports are then said to be quasi co-located (QCL). The network can then signal to the UE that two antenna ports are QCL. If the UE knows that two antenna ports are QCL with respect to a certain parameter (e.g. Doppler spread), the UE can estimate that parameter based on a reference signal transmitted one of the antenna ports and use that estimate when receiving another reference signal or physical channel the other antenna port. Typically, the first antenna port is represented by a measurement reference signal such as CSI-RS (known as source RS) and the second antenna port is a demodulation reference signal (DMRS) (known as target RS) for PDSCH or PDCCH reception.

In NR, a QCL relationship between a DMRS port in PDSCH and other reference signals is described by a TCI state. A UE can be configured through RRC signaling with M TCI states, where M is up to <NUM> in frequency range <NUM> (FR2) for the purpose of PDSCH reception and up to <NUM> in FR1, depending on UE capability. Each TCI state contains QCL information. A UE can be dynamically signaled one or two TCI states in the TCI field in a DCI scheduling a PDSCH.

Reliable data transmission with multiple panels or transmission points (TRP) has been proposed in 3GPP for Rel-<NUM>, in which a data packet may be transmitted over multiple TRPs to achieve diversity. Ultra-Reliable Low Latency (URLLC) data transmission may occur over multiple transmission points. An example is shown in <FIG>, where the two PDSCHs carry the same encoded data payload but with the same or different redundancy versions so that the UE can do soft combining of the two PDSCHs to achieve more reliable reception. The two PDSCHs can be frequency division multiplexed (FDM) in a same slot, or time division multiplexed (TDM) in different slots or mini-slots within a slot.

Different schemes have been identified in 3GPP for PDSCH transmissions from multiple TRPs scheduled by a single DCI, including:.

In RAN1#98bis, agreements were made on some signaling one or multiple of the schemes:.

For scheme <NUM>, the number of transmission occasions is implicitly determined by the number of TCI states indicated by a code point whereas one TCI state means one transmission occasion and two states means two transmission occasions. For scheme <NUM>, TDRA indication is enhanced to additionally indicate the number of PDSCH transmission occasions by using PDSCH-TimeDomainResourceAllocation field. The maximum number of repetitions is for further study. For single-DCI based M-TRP URLLC scheme differentiation among schemes 2a/2b/<NUM>, from the UE perspective, a new RRC parameter is introduced to enable one scheme or multiple schemes among Schemes 2a/2b/<NUM>.

As shown above, for URLLC and multi-TRP operation, multiple transmission schemes have been defined, such as schemes 2a,2b and <NUM> for example. A gNB may need to dynamically switch between different transmission schemes since some traffic needs to be received with high reliability while others can be received with normal reliability but with higher spectral efficiency. However, a problem exists in determining how to dynamically switch the different schemes when scheduling the UE.

In accordance with embodiments described herein, to solve this problem, in the DCI that contains the scheduling assignment for the UE, a combination of multiple fields, the TDRA table, the antenna port indication table, and the TCI codepoint indication, is jointly used to implicitly indicate the transmission scheme used for the PDSCH transmission. In one example, a repetition field in TDRA is used for signaling both Scheme <NUM> and Scheme <NUM>. More specifically, if the repetition field is present in the TDRA indicated in a DCI, the number of repetitions is one, and two TCI states are indicated in the DCI, Scheme <NUM> is selected. Otherwise, if the number of repetitions is greater than one and two TCI states are indicated in the DCI, Scheme <NUM> is selected.

In another example, if the repetition field is present in the TDRA indicated in a DCI, and one TCI states are indicated in the DCI, single TRP transmission scheme is used. If the number of repetitions, n, is greater than one, the PDSCH will be repeated in n consecutive slots. In another example, If the repetition field is not present and one TCI state is indicated in the DCI, Rel-<NUM> single TRP transmission is used. If the repetition field is not present and two TCI states and DMRS ports in two CDM groups are indicated in the DCI, Scheme 1a is used. Otherwise, if two TCI states and DMRS port(s) in one CDM group is indicated in the DCI, either Scheme 2a or 2b is used.

The inventive concepts described herein enables dynamic indication of transmission schemes without introducing any new DCI field or RRC parameter, hence DCI payload is unchanged, which is an advantage. It also allows dynamic indication of number of repetitions in single TRP transmission. The inventive concepts described herein also supports indicating a hybrid scheme of Scheme 1a and Scheme <NUM>, which has the benefit of increased diversity with multiple layers per repetition.

Operations of the wireless device <NUM> (implemented using the structure of the block diagram of <FIG>) will now be discussed with reference to the flow chart of <FIG> according to some embodiments of inventive concepts. For example, modules may be stored in memory <NUM> of <FIG>, and these modules may provide instructions so that when the instructions of a module are executed by respective wireless device processing circuitry <NUM>, processing circuitry <NUM> performs respective operations of the flow chart.

<FIG> illustrates a method of operating a wireless device in a communication network in accordance with embodiments of the inventive concepts. <FIG> illustrates the method includes receiving <NUM> a list of time domain resource allocations, TDRAs, from a network node of the communication network. For example, wireless device <NUM> may receive a list of TDRAs from a network node, such as, but not limited to, RAN node <NUM> illustrated in <FIG>. <FIG> also illustrates the method includes receiving <NUM> downlink control information, DCI, scheduling a physical downlink shared channel, PDSCH, for reception by the wireless device. Continuing the previous example, wireless device <NUM> may receive downlink control information, DCI, scheduling a physical downlink shared channel, PDSCH, for reception by wireless device <NUM>. The DCI may be received from the network node, such as RAN node <NUM>.

<FIG> also illustrates the method includes selecting <NUM> a TDRA from the list of TDRAs based on the received DCI. Continuing the previous example, wireless device <NUM> may select a TDRA from the list of TDRAs based on the received DCI. Additional embodiments regarding the selection of the TDRA from the list of TDRAs by wireless device <NUM> are described in further detail below. <FIG> further illustrates the method includes determining <NUM> a PDSCH transmission scheme including one or more transmission points, TRPs, based on a number of PDSCH transmission repetitions configured for the selected TDRA. Continuing the previous example, wireless device <NUM> may determine a PDSCH transmission scheme including one or more TRPs based on a number of PDSCH transmission repetitions configured for the selected TDRA. Additional embodiments regarding the determination of the PDSCH transmissions are described in further detail below.

In some embodiments, the UE is configured from network with a new TDRA where at least one entry in the TDRA table indicates a number of repetitions. Secondly, the UE is scheduled downlink data and the PDCCH DCI indicates the scheduling resource including an entry from the TDRA table. In accordance with embodiments, the received DCI indicates a number of transmission configuration indicator, TCI, states. In some embodiments, selecting the TDRA from the list of TDRAs comprises selecting the TDRA from the list of TDRAs based on the number of TCI states indicated in the received DCI. In some embodiments, selecting the TDRA from the list of TDRAs comprises selecting the TDRA from the list of TDRAs based on a time domain resource assignment bit field in the received DCI. Additional examples and implementations of the time domain resource assignment bit field are described herein above. The received DCI may also indicate a number of code multiplexed, CDM, groups associated with one or more demodulation reference signal, DMRS, ports. In accordance with some other embodiments, the method may include selecting the TDRA from the list of TDRAs based on the number of CDM groups associated with the one or more DRMS ports.

For example, if the number of PDSCH repetitions in the indicated TDRA indicated in a DCI scheduling a PDSCH is one and DCI indicates two TCI states and DCI indicates the DMRS ports limited within one CDM group only, (these are indicated in the same DCI), then this combination indicates to the UE that Scheme <NUM> is selected, i.e. the scheduled PDSCH will be transmitted according to Scheme <NUM> with two PDSCH transmissions within the same slot.

Alternatively, if the number of PDSCH repetitions in the indicated TDRA indicated in a DCI scheduling a PDSCH is larger than one and DCI indicates two TCI states and DCI indicates the DMRS ports limited within one CDM group only, (these are indicated in the same DCI), then this combination indicates to the UE that Scheme <NUM> is selected, i.e. the scheduled PDSCH will be transmitted according to Scheme <NUM> with the number of PDSCH transmission occasions across slots as indicated by the TDRA.

In accordance with embodiments, each TDRA of the list of TDRAs is associated with information indicating a number of PDSCH transmission repetitions configured for the TDRA. An example is shown Table <NUM>, where the table captures the TDRAs configured by an RRC parameter PDSCH-TimeDomainResourceAllocationList. Each entry in the "Number of PDSCH Repetitions (n)" column corresponds an information field in each TDRA configured by PDSCH-TimeDomainResourceAllocationList.

In accordance with embodiments, the method may include determining the PDSCH transmission scheme by selecting a PDSCH transmission scheme from multiple different PDSCH transmission schemes used for PDSCH transmission from multiple TRPs scheduled by a single DCI. For example, wireless device <NUM> may select a PDSCH transmission scheme from the multiple different PDSCH transmission schemes described herein from the one or multiple TRPs in Table <NUM> shown above using a single DCI. According to some embodiments, the multiple different PDSCH transmission schemes comprises one or more of the following PDSCH transmission schemes used for PDSCH transmission from multiple TRPs: PDSCH transmission scheme 1a, PDSCH transmission scheme <NUM>, PDSCH transmission scheme <NUM>, and PDSCH transmission scheme <NUM> as described herein. The multiple different PDSCH transmission schemes may also comprises a hybrid PDSCH transmission scheme in which the PDSCH transmission scheme 1a is repeated in one of two or four slots in accordance with embodiments.

The method may also include determining the PDSCH transmission scheme by selecting PDSCH transmission scheme <NUM> based on the number of PDSCH transmission repetitions being equal to one and the DCI indicating two TCI states and one CDM group according to some embodiments. For example, when row <NUM> in Table <NUM> is indicated in the TDRA field in a DCI and two TCI states and DMRS ports in one CDM group are indicated in the same DCI, Scheme <NUM> is used for the PDSCH. The method may also include determining the PDSCH transmission scheme by selecting PDSCH transmission scheme <NUM> based on the number of PDSCH transmission repetitions being greater than one and the DCI indicating two TCI states and one CDM group according to some other embodiments. In another example, if row <NUM> or row <NUM> of Table <NUM> is indicated and two TCI states and DMRS ports in one CDM group are indicated in the same DCI, then Scheme <NUM> is used with repetition <NUM> or <NUM>, respectively. In another example, if row <NUM>,<NUM> or <NUM> to row N in Table <NUM> is indicated, then neither Scheme <NUM> or <NUM> is used for the transmission.

The method may include determining the PDSCH transmission scheme by selecting a single TRP PDSCH transmission scheme based on the number of PDSCH transmission repetitions for the selected TDRA equals to one and the DCI indicates one TCI state according to some embodiments. For example, if row <NUM> in Table <NUM> is indicated in the TDRA field in a DCI but one TCI state is indicated in the same DCI instead of two TCI states, then Rel-<NUM> single TRP PDSCH transmission is used. In some other embodiments, the method may include determining the PDSCH transmission scheme by selecting a single TRP PDSCH transmission scheme based on the number of PDSCH transmission repetitions for the selected TDRA is greater than one and the DCI indicates one TCI state. For example, if row <NUM> or row <NUM> in Table <NUM> is indicated but only one TCI state is indicated in the same DCI, PDSCH repetition over a single TRP is used with <NUM> or <NUM> repetitions, respectively.

In some other embodiments, the method may include determining the PDSCH transmission scheme by selecting the hybrid PDSCH transmission scheme based on the number of PDSCH transmission repetitions is greater than one and the DCI indicating two TCI states and two CDM groups. For example, if row <NUM> or row <NUM> in Table <NUM> is indicated with two TCI states but DMRS ports in two CDM groups in a DCI, a hybrid scheme of Scheme 1a and Scheme <NUM> is used in which Scheme 1a is repeated in <NUM> or <NUM> slots, respectively.

The above embodiments and examples are summarized by the flowchart in <FIG>, which illustrates the selection process of various PDSCH schemes when the number of PDSCH repetition field is present in the TDRA. Further, scheme <NUM> may be disabled (or not enabled) by the network to the UE, in case <NUM> TCI states are indicated and <NUM> CDM group is indicated and one repetition in the TDRA, then the UE shall ignore this scheduling assignment since this would then correspond to an invalid scheduling assignment. Hence, scheme <NUM> may be additionally enabled by RRC configuration in the dynamic switching algorithm described here. This indication allows for dynamic switching between transmission schemes based on the traffic type and availability of the scheduling resources in one or multiple TRPs.

Furthermore, if the Number of PDSCH Repetitions field is not present in a row, i.e. "not configured" in the "Number of PDSCH Repetitions" column in Table <NUM> shown above, some more embodiments are elaborated in the following.

In one embodiment, if one TCI state is indicated in a DCI, Rel-<NUM> single TRP scheme is used. In some other embodiments, the method may include determining the PDSCH transmission scheme by selecting scheme 1a based on the information indicating that no PDSCH transmission repetitions are configured for the selected TDRA and the DCI indicating two TCI states and two CDM groups. For example, if two TCI states and DMRS ports in two CDM groups are indicated, Scheme 1a is used.

In some other embodiments, the method may include determining the PDSCH transmission scheme by selecting one of scheme 2a or 2b based on the information indicating that no PDSCH transmission repetitions are configured for the selected TDRA and the DCI indicating two TCI states and one CDM group. For example, if two TCI states and DMRS port(s) in one CDM group is indicated, either Scheme 2a or Scheme 2b is used. In this embodiment, schemes 2a and/or 2b are enabled by RRC. Scheme 2a or 2b may be indicated separately either by enabling using RRC configuration directly or by additional implicit selection by DCI. For example, if both Scheme 2a/2b are enabled by RRC, then which of Scheme 2a/2b is used for the scheduled PDSCH may be distinguished by the CDM group of the DMRS ports indicated by the same DCI.

The method may include determining the PDSCH transmission scheme by selecting scheme <NUM> based on the information indicating that no PDSCH transmission repetitions are configured for the selected TDRA and the DCI indicating two TCI states and one CDM group according to some other embodiments. For example, if the "Number of PDSCH Repetitions" field is not present in a row in Table <NUM> and two TCI states and DMRS port(s) in one CDM group is indicated, one of Scheme 2a, Scheme 2b, and Scheme <NUM> is used, provided that the scheme is first enabled by RRC signaling. Schemes 2a/2b/<NUM> may be indicated separately either by RRC configuration or implicitly by DCI. In another embodiment, between Scheme <NUM> and Scheme 2a/2b, it is signaled by RRC while between Schemes 2a and 2b, it is dynamically indicated by DCI.

According to some embodiments, as discussed above, the method may include determining the PDSCH transmission scheme comprises determining the PDSCH transmission scheme is enabled by radio resource control, RRC. The above examples are summarized in <FIG> for the case of RRC enables one of Schemes 2a and 2b, one of Schemes 2a/2b/<NUM>, and both Schemes 2a and 2b, respectively. <FIG> illustrates an example indication of various schemes when the number of PDSCH repetition field is not present in TDRA, and either Scheme 2a or 2b is enabled by RRC. <FIG> illustrates an example indication of various schemes when the number of PDSCH repetition field is not present in TDRA, and either Scheme 2a, 2b, or <NUM> is enabled by RRC. <FIG> illustrates an example indication of various schemes when the number of PDSCH repetition field in not present in TDRA, and both Scheme 2a and 2b are enabled by RRC.

Operations of a RAN node <NUM> (implemented using the structure of <FIG>) will now be discussed with reference to the flow chart of <FIG> according to some embodiments of inventive concepts. For example, modules may be stored in memory <NUM> of <FIG>, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry <NUM>, processing circuitry <NUM> performs respective operations of the flow chart.

<FIG> illustrates a method of operating a radio access network node, RAN, in a communication network in accordance with embodiments of the inventive concepts described herein. <FIG> illustrates the method includes transmitting <NUM> a list of time domain resource allocations, TDRAs, to a wireless device operating in the communication network, each TDRA comprising information indicating a number of PDSCH transmission repetitions configured for the selected TDRA. For example, RAN <NUM> may transmit a list of TDRAs to wireless device <NUM> operating in the communication network, each TDRA comprising information indicating the number of PDSCH transmission repetitions configured for the selected TDRA. <FIG> also illustrates the method includes scheduling <NUM> the PDSCH transmissions from the one or more TRPs according to a PDSCH transmission scheme associated with the TDRA indicated by the DCI. Continuing the previous example, RAN <NUM> may schedule the PDSCH transmissions from the one or more TRPs according to a PDSCH transmission scheme associated with the TDRA indicated by the DCI.

According to some embodiments, the method of operating the RAN may include scheduling the PDSCH transmissions from the one or more TRPs according to the PDSCH transmission scheme by selecting a PDSCH transmission scheme from multiple different PDSCH transmission schemes used for PDSCH transmission from the one or more TRPs scheduled by a single DCI. For example, RAN <NUM> may select one of the PDSCH transmission schemes described above according to the one or more TRPs listed in Table <NUM> above transmitted to wireless device <NUM>. Example embodiments are discussed below.

Explanations are provided below for various abbreviations/acronyms used in the present disclosure.

<FIG> <FIG> illustrates a wireless network in accordance with some embodiments.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in <FIG>. For simplicity, the wireless network of <FIG> only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ110, QQ110b, and QQ110c (also referred to as mobile terminals). In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node QQ160 and WD QQ110 comprise various components described in more detail below.

Yet further examples of network nodes include multistandard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.

In <FIG>, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160 illustrated in the example wireless network of <FIG> may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. Moreover, while the components of network node QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.

Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry QQ170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160 components, such as device readable medium QQ180, network node QQ160 functionality. For example, processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. In some embodiments, processing circuitry QQ170 may include a system on a chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.

Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170. Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160. Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication of signaling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170.

In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, <NUM> and <NUM>. In certain embodiments, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node.

Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187. As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187.

Alternative embodiments of network node QQ160 may include additional components beyond those shown in <FIG> that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port. Antenna QQ111, interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. In some embodiments, radio front end circuitry and/or antenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120. Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111. In some embodiments, WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered a part of interface QQ114. Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120.

Processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In certain embodiments processing circuitry QQ120 of WD QQ110 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.

User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.

<FIG> illustrates a user Equipment in accordance with some embodiments.

UE QQ2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated in <FIG>, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or <NUM> standards.

In <FIG>, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231, power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information.

In <FIG>, processing circuitry QQ201 may be configured to process computer instructions and data. Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ201 may include two central processing units (CPUs).

In the depicted embodiment, input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. For example, a USB port may be used to provide input to and output from UE QQ200. UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200.

In <FIG>, RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a. Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243a may comprise a Wi-Fi network. Network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like).

RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.

Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221, which may comprise a device readable medium.

In <FIG>, processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b may be the same network or networks or different network or networks. Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE <NUM>. QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200. In one example, communication subsystem QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231.

<FIG> illustrates a virtualization environment in accordance with some embodiments.

<FIG> is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized.

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330.

The functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory QQ390-<NUM> which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-<NUM> having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360. Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.

During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.

As shown in <FIG>, hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.

In the context of NFV, virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in <FIG>.

In some embodiments, one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225. Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signaling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.

<FIG> illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

With reference to <FIG>, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414. Access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491, QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.

The communication system of <FIG> as a whole enables connectivity between the connected UEs QQ491, QQ492 and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430 and the connected UEs QQ491, QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411, core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications. For example, base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.

<FIG> illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ511 includes host application QQ512. Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.

Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530. Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in <FIG>) served by base station QQ520. Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510. Connection QQ560 may be direct or it may pass through a core network (not shown in <FIG>) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531, which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532. Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the user, client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data. OTT connection QQ550 may transfer both the request data and the user data. Client application QQ532 may interact with the user to generate the user data that it provides.

It is noted that host computer QQ510, base station QQ520 and UE QQ530 illustrated in <FIG> may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491, QQ492 of <FIG>, respectively.

In <FIG>, OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the random access speed and/or reduce random access failure rates and thereby provide benefits such as faster and/or more reliable random access.

<FIG> illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. In step QQ610, the host computer provides user data. In substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

<FIG> illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. In step QQ710 of the method, the host computer provides user data. In step QQ720, the host computer initiates a transmission carrying the user data to the UE. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.

The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

In step QQ910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

The term "and/or" (abbreviated "/") includes any and all combinations of one or more of the associated listed items.

Claim 1:
A method of operating a wireless device (<NUM>) in a communication network, the method comprising:
obtaining (<NUM>) a list of time domain resource allocations, TDRAs, from a network node of the communication network;
receiving (<NUM>) downlink control information, DCI, scheduling a physical downlink shared channel, PDSCH, for reception by the wireless device, the received DCI indicating one or more transmission configuration indicator, TCI, states and one or more code domain multiplexed, CDM, groups associated with one or more demodulation reference signal, DMRS, ports;
selecting (<NUM>) a TDRA from the list of TDRAs based on the received DCI; and characterized by:
determining (<NUM>) a PDSCH transmission scheme including one or more transmission points, TRPs, based jointly on a number of PDSCH transmission repetitions configured for the selected TDRA, number of indicated TCI states and number of indicated CDM groups.