METHOD FOR REPEATING A TRANSPORT BLOCK (TB) OVER MULTIPLE TRANSMISSION / RECEPTION POINTS (TRPs)

Abstract

A method for repeating a transport block (TB) over multiple transport situations is provided. The method comprises the step of exchanging specific signaling between a radio device (e.g., user equipment) and a network node (e.g., base station) to repeat the same or different duplicate versions of a TB in multiple non-overlapping transport situations (e.g., mini-slots) corresponding to multiple transport configuration indication (TCI) states having different starting positions. More specifically, the network node transmits a time domain resource allocation (TDRA) to indicate multiple non-overlapping transport situations, and the radio device receives the TDRA indicating multiple non-overlapping transport situations. Thus, the radio device can receive repetitions of the TB according to the TDRA. By indicating transport situations in the TDRA, it is possible to efficiently schedule multiple transport situations over multiple TCI states, which helps improve efficiency, reliability, and coverage in a wireless communication network.

Description

Technology Field

[0001] This application claims the benefit of provisional application serial number 62 / 843,063 filed on May 3, 2019, the disclosures of which are incorporated herein by reference in whole.

[0002] The technology of the present disclosure generally relates to a Time Domain Resource Allocation (TDRA) for repeating a Transport Block (TB) through a number of Transmission / Reception Points (TRPs). Background Technology

[0003] The new 5th generation (5G) mobile wireless communication system, or New Radio (NR), supports a diverse set of use cases and a diverse set of deployment scenarios. NR uses Cyclic Prefix (CP)-Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) on the downlink (DL) (e.g., from a network node, gNB, eNB, or base station to a User Equipment (UE)), and uses both CP-OFDM and Discrete Fourier Transform (DFT)-Spread-OFDM (DFT-S-OFDM) on the uplink (UL) (e.g., from a UE to a gNB). In the time domain, NR downlink and uplink physical resources each consist of subframes of equal size of 1 millisecond (ms). The subframes are further divided into multiple slots of equal duration.

[0004] The slot length depends on the subcarrier spacing. For a subcarrier spacing of Δf = 15 kHz, regardless of the subcarrier spacing, there is only one slot per subframe, and each slot always consists of 14 OFDM symbols.

[0005] Typical data scheduling in NR is provided on a slot basis. FIG. 1 illustrates an example in which the first two symbols include a physical downline control channel (PDCCH) and the remaining 12 symbols include a physical data channel (PDCH) which may be a physical downline shared channel (PDSCH) or a physical upline shared channel (PUSCH).

[0006] Other subcarrier spacing values ​​are supported in NR. The supported subcarrier spacing (SCS) value is Δf = (15 x 2^2) (also referred to as other numerology). α It is given as )kHz, where α∈ (0,1,2,4,8). Δf=15kHz is the basic subcarrier interval also used in Long-Term Evolution (LTE), and the corresponding slot period is 1ms. For a given SCS, the corresponding slot period is 1 / (2 α It is )ms.

[0007] In the frequency domain physical resource definition, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 consecutive subcarriers. A basic NR physical time-frequency resource grid is illustrated in FIG. 2, where only a single RB within a 14-symbol slot is shown. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE).

[0008] Downlink transmission can be dynamically scheduled. For example, in each slot, the gNB transmits Downlink Control Information (DCI) via the PDCCH to indicate which UE data is being transmitted to which UE, and in which RB and OFDM symbols the UE data is being transmitted in the current downlink slot. The PDCCH is typically transmitted in the first one or two OFDM symbols of each slot of the NR. UE data is carried in the PDCCH. The UE first detects and decodes the PDCCH, and if the decoding is successful, the UE decodes the corresponding PDCCH based on the control information decoded from the PDCCH.

[0009] Uplink data transmission can also be dynamically scheduled using PDCCH. Similar to downlink, the UE first decodes the uplink grant from PDCCH and then transmits data via PUSCH based on control information decoded from the uplink grant, such as modulation order, coding rate, and uplink resource allocation.

[0010] Radio resource control (RRC) configuration for repeated iterations in Rel-15

[0011] In NR Rel-15, slot-aggregation is supported for both DL and UL transmissions, which is advantageous for enhancing coverage and improved reliability. In this case, PDSCH and PUSCH transmissions can be repeated across multiple slots when RRC parameters for slot aggregation are configured. The corresponding RRC parameters are referred to as PDSCH-AggregationFactor, PUSCH-AggregationFactor, repK for PDSCH, grant-based PUSCH, and grant-free PUSCH, respectively. To explain the use of these parameters, the relevant Information Elements (IEs) of TS 38.331 are listed below.

[0012] PDSCH-Config Information Elements

[0013] -- ASN1START

[0014] -- TAG-PDSCH-CONFIG-START

[0015] PDSCH-Config ::= SEQUENCE {

[0017] resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},

[0018] pdsch-TimeDomainAllocationList SetupRelease { PDSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need M

[0019] pdsch-AggregationFactor ENUMERATED { n2, n4, n8}

[0020] OPTIONAL, -- Need S

[0023] }

[0024] PUSCH-Config information elements

[0025] PUSCH-Config ::= SEQUENCE {

[0027] resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},

[0028] pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need M

[0029] pusch-AggregationFactor ENUMERATED { n2, n4, n8}

[0030] OPTIONAL, -- Need S

[0032] OPTIONAL, -- Need S

[0034] }

[0035] ConfiguredGrantConfig information element

[0036] ConfiguredGrantConfig ::= SEQUENCE {

[0038] repK ENUMERATED {n1, n2, n4, n8},

[0040] }

[0041] When a UE is scheduled by DL designation or DL ​​Semi-Persistent Scheduling (SPS) for PDSCH transmission in a given slot, the resource allocation signaled for PDSCH is used across multiple consecutive slots if the aggregation factor is configured to a value greater than 1. In this case, PDSCH is repeated with a different Redundancy Version (RV) in the slot scheduled for the transmission of the corresponding Transfer Block (TB). The same process applies to UL, where the UE is scheduled by UL designation or a grant-free method for PDSCH transmission in a slot and configured for slot aggregation. In this case, the UE uses the resource allocation signaled across a given number of slots by the aggregation factor, which uses a different RV for the transmission of the corresponding TB. The nth (n) of the TB th The RV to be applied to the transmission occasion is determined according to the table below, where rv id is the RV identification number.

[0042] Figure 5.1.2.1-2: Redundant versions applied when pdsch-AggregationFactor is given

[0043]

[0044] In NR Rel-16, proposals for representing the number of iterations in DCIs are under discussion. Some proposals in NR Rel-16 include representing the number of iterations in a newly introduced DCI field. Some other proposals in NR Rel-16 include representing the number of iterations using existing DCI fields, such as the Time Domain Resource Allocation (TDRA) field.

[0045] TDRA in NR Rel-15

[0046] In NR Rel-15, TDRA information for PDSCH transmission in a slot includes the slot where the PDSCH is expected to be received (also known as K0), the start symbol in the slot for receiving the PDSCH, and information that the UE can use to determine the length or duration of the PDSCH reception (also known as the Start and Length Indicator Value, SLIV). The UE is also provided with a mapping type that can be used to determine the location of the Demodulation Reference Signal (DMRS). In NR, the TDRA plot is specified to include other combinations such as K0 and SLIV. The UE may be signaled an index for a row of the TDRA plot that provides information about the K0 and SLIV to be used for reception.

[0047] A similar process applies to PUSCH transmissions, where the slot intended for the PUSCH transmission is obtained from a field in the UL designation (aka K2). SLIV information is provided in a similar manner to that for DL ​​receptions as well as for mapping types by UL designation and / or configuration.

[0048] TDRA is a time-domain resource allocation for the first moment of PDSCH reception or PUSCH transmission. As previously described, if a UE is configured with an aggregation factor, transmission in one slot is repeated across multiple slots based on the aggregation factor.

[0049] To explain the use of these parameters, the relevant IE of TS 38.331 is listed below.

[0050] PDSCH-TimeDomainResourceAllocationList information element

[0051] -- ASN1START

[0052] -- TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

[0053] PDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation

[0054] PDSCH-TimeDomainResourceAllocation ::= SEQUENCE {

[0055] k0 INTEGER(0..32)

[0056] OPTIONAL, -- Need S

[0057] mappingType ENUMERATED {typeA, typeB},

[0058] startSymbolAndLength INTEGER (0..127)

[0059] }

[0060] -- TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

[0061] -- ASN1STOP

[0062]

[0063] PUSCH-TimeDomainResourceAllocation information element

[0064] -- ASN1START

[0065] -- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

[0066] PUSCH-TimeDomainResourceAllocationList ::= SEQUENCE

[0067] (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-

[0068] TimeDomainResourceAllocation

[0069] PUSCH-TimeDomainResourceAllocation ::= SEQUENCE {

[0070] k2 INTEGER(0..32) OPTIONAL, --

[0071] Need S

[0072] mappingType ENUMERATED {typeA, typeB},

[0073] startSymbolAndLength INTEGER (0..127)

[0074] }

[0075] -- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

[0076]

[0077] Quasi Co-Located (QCL) and Transmission Configuration Indication (TCI) status

[0078] Multiple signals can be transmitted from the same base station antenna through different antenna ports. These signals may have the same macroscopic properties, for example, with respect to Doppler shift / spread, mean delay spread, or mean delay. These antenna ports are referred to as QCLs.

[0079] A network can signal to a UE where two antenna ports are QCL. When the UE recognizes that two antenna ports are QCL with respect to a specific parameter (e.g., Doppler spread), the UE can estimate that parameter based on one of the antenna ports and use that estimate when receiving from the other antenna port. Generally, the first antenna port is represented by a measurement reference signal, such as the Channel State Information (CSI)-Reference Signal (RS) (known as Source RS), and the second antenna port is represented by the DMRS (known as Target RS).

[0080] For example, if antenna ports A and B are QCL with respect to average delay, the UE can estimate the average delay from the signal received from antenna port A (known as the source RS) and assume that the signal received from antenna port B (target RS) has the same average delay. This is useful for demodulation because the UE can know the channel properties in advance when attempting channel measurements using DMRS.

[0081] Information regarding what assumptions can be made in relation to QCL is signaled from the network to the UE. In NR, four types of QCL relationships were defined between the transmitted source RS and the transmitted target RS:

[0082] * Type A: {Doppler shift, Doppler spread, mean delay, delay spread}

[0083] * Type B: {Doppler shift, Doppler spread}

[0084] * Type C: {mean delay, Doppler shift}

[0085] * Type D: {Space Rx parameter}

[0086] QCL Type D was introduced to facilitate beam management via analog beamforming and is known as spatial QCL. Although there is currently no strict definition of spatial QCL, it is understood that if two transmitting antenna ports are spatially QCL, the UE can receive using the same Rx beam. Regarding beam management, while the discussion primarily focuses on QCL Type D, it should be noted that it is also necessary to convey the Type A QCL relationship for RS to the UE so that all relevant macroscopic parameters can be estimated.

[0087] Generally, this is achieved by configuring the UE with CSI-RS for Tracking RS (TRS) for time / frequency offset estimation. For any QCL reference to be usable, the UE needs to receive the TRS with a sufficiently good Signal-to-Interference and Noise Ratio (SINR). In many cases, this means that the TRS must be transmitted to a specific UE via an appropriate beam.

[0088] To introduce dynamic elements into beam and transmit / receive point (TRP) selection, the UE can be configured via RRC signaling with N TCI states, where N is up to 128 in frequency range 2 (FR2) and up to 8 in frequency range 1 (FR1), depending on the UE's capabilities.

[0089] Each TCI state contains QCL information, for example, one or two source DL RSs associated with each QCL type. For example, a TCI state contains a pair of CSI-RSs associated with each QCL type, and for example, two different CSI-RSs {CSI-RS1, CSI-RS2} constitute {qcl-Type1, qcl-Type2} = {Type A, Type D} in the TCI state. This means that the UE can derive Doppler shift, Doppler spread, mean delay, and delay spread from CSI-RS1, and derive spatial Rx parameters (e.g., the RX beam used) from CSI-RS2. In cases where Type D (spatial information) cannot be applied, such as in low-band or mid-band operation, the TCI state contains only a single source RS.

[0090] Each of the N TCI states in the TCI state list 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.

[0091] A first list of available TCI states is configured for PDSCH, and a second list for PDCCH is a pointer, known as a TCI state ID, for a subset of TCI states configured for PDSCH. Includes. Subsequently, the network activates one TCI state for PDCCH (e.g., provides a TCI for PDCCH) and activates up to M active TCI states for PDSCH. The number of active TCI states M that the UE can support is the UE capability, but the maximum value in NR Rel-15 is 8.

[0092] Each configured TCI state contains parameters regarding the QCL association between the source RS (CSI-RS or SS / PBCH port) and the target RS (e.g., PDSCH / PDCCH DMRS port). The TCI state is also used to convey QCL information for CSI-RS reception.

[0093] When the UE is configured with 4 active TCI states (from a list of 64 total configured TCI states), 60 of the 64 TCI states are deactivated. As such, the UE does not need to be prepared to have estimated macro parameters for these deactivated TCI states. Instead, the UE continuously tracks and updates the macro parameters for the 4 active TCI states through the measurement and analysis of the source RS represented by each TCI state.

[0094] In NR Rel-15, when scheduling PDSCH to a UE, the DCI contains a pointer to one active TCI. At this time, the UE can determine macroscopic parameter estimates to use when performing PDSCH DMRS channel estimation and the subsequent PDSCH demodulation.

[0095] DMRS

[0096] DMRS is used for coherent demodulation of PDCCH as well as PDSCH (DL) and PUSCH (UL). DMRS is limited to RBs carrying associated physical layer channels and maps to assigned REs of the OFDM time-frequency grid, so that the receiver can efficiently handle time / frequency-selective fading radio channels.

[0097] The mapping of DMRS to RE can be configured in both frequency and time domains, and 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 location of the first DMRS within the transmission interval. DMRS mapping in the time domain can also be single-symbol based or dual-symbol based, where the latter means that the DMRS is mapped to two adjacent symbols. Additionally, the UE can be configured with one, two, three, or four single-symbol DMRS and one or two dual-symbol DMRS. In low Doppler scenarios, it may be sufficient to configure only front-loaded DMRS, for example, one single-symbol DMRS or one dual-symbol DMRS, but additional DMRS are required in high Doppler scenarios.

[0098] FIG. 3 illustrates the mapping of front-loaded DMRS for configuration types 1 and 2, which have single-symbol and dual-symbol DMRS, for mapping type A, which has the first DMRS in the third symbol of a transmission interval of 14 symbols. In FIG. 3, it can be seen that types 1 and 2 differ in the mapping structure and the number of supported Code Division Multiplexing (CDM) groups, where type 1 supports two CDM groups and type 2 supports three CDM groups.

[0099] The mapping structure of Type 1 is sometimes referred to as a 2-comb structure, in which two CDM groups are defined in the frequency domain by sets of subcarriers {0, 2, 4, …} and {1, 3, 5, …}. Since the comb mapping structure is a prerequisite for transmissions requiring low PAPR / CM, it is used in combination with DFT-S-OFDM, whereas CP-OFDM supports both Type 1 and Type 2 mappings.

[0100] DMRS antenna ports are mapped to resource elements within only one CDM group. For single-symbol DMRS, two antenna ports can be mapped to each CDM group, whereas for dual-symbol DMRS, four antenna ports can be mapped to each CDM group. Therefore, the maximum number of DMRS ports is four or eight for Type 1 and six or twelve for Type 2. An Orthogonal Cover Code (OCC) of length 2 ([+1,+1],[+1,-1]) is used to separate antenna ports mapped to the same resource element within a CDM group. When dual-symbol DMRS is configured, the OCC applies in the time domain as well as the frequency domain.

[0101] In NR Rel-15, antenna port p at OFDM symbol l of water index μ j The mapping of the PDSCH DMRS sequence r(m), m=0,1,… to the subcarrier k is specified in TS 38.211 as follows:

[0102]

[0103]

[0104] k'=0,1

[0105]

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

[0107] Here, OCC w in the frequency domain f Apply (k') and w in the time domain t After applying (l'), port p in CDM group λ j It represents the reference signal mapped to. Figures 2 and 3 below show the PDSCH DMRS mapping parameters for configuration type 1 and type 2, respectively.

[0108] Figure 2. PDSCH DMRS Mapping Parameters for Configuration Type 1

[0109]

[0110] Figure 3. PDSCH DMRS Mapping Parameters for Configuration Type 2

[0111]

[0112] QCL relationship to DMRS CDM group

[0113] In the NR specification TS 38.211, there is a limitation stating that "the UE may assume that PDSCH DMRS within the same CDM group are in a similar position with respect to Doppler shift, Doppler spread, mean delay, delay spread, and spatial Rx."

[0114] If a UE is not scheduled for any of the DMRS ports within a CDM group, there may be another UE simultaneously scheduled using the remaining ports of that CDM group. In this case, the UE can estimate the channel (and thus the interference signal) for that other UE to perform coherent interference suppression. Thus, this is useful for Multi-User-Multiple Input Multiple Output (MU-MIMO) scheduling and UE interference suppression.

[0115] Ultra-Reliable and Low Latency Communication (URLLC) NR

[0116] In NR Rel-16, the packet error rate is 10 -5 Specification improvements for URLLCs are underway. For these services, alternative Modulation and Coding Scheme (MCS) tables may be configured to be used for PDSCH or PUSCH scheduling, which provides more robust reception of data payloads.

[0117] NR Rel-16 improvement for PDSCH with multiple-TRPs

[0118] In NR Rel-16, discussions are underway regarding the support of PDSCHs with multiple TRPs. One mechanism being considered in NR Rel-16 is a single PDCCH that schedules one or more PDSCHs from different TRPs. A single PDCCH is received from one of the TRPs. Figure 4 illustrates an example where a DCI received by a UE from a PDCCH from TRP1 schedules two PDSCHs. The first PDSCH (PDSCH1) is received from TRP1, and the second PDSCH (PDSCH2) is received from TRP2. Alternatively, a single PDCCH schedules a single PDSCH, where the PDSCH layers are grouped into two groups, with layer group 1 received from TRP1 and layer group 2 received from TRP2. In this case, each PDSCH or layer group is transmitted from a different TRP and has a different associated TCI state. In the example of Figure 4, PDSCH1 is associated with TCI state p, and PDSCH2 is associated with TCI state q.

[0119] At the RAN1 AdHoc meeting in January 2019, it was agreed that the TCI indication framework should be improved in Rel-16, at least for eMBB:

[0120] Each TCI code point in DCI can correspond to one or two TCI states.

[0121] * When two TCI states are activated within a TCI code point, each TCI state corresponds to at least one CDM group for DMRS type 1.

[0122] Future Research (FFS) Design for DMRS Type 2

[0123] * For Future Research (FFS): TCI Field in DCI and Associated MAC-CE Signaling Effects

[0124] In accordance with the above agreement, each code point in the DCI TCI field may be mapped to one or two TCI states. This can be interpreted as follows: "The DCI in the PDCCH schedules one or two PDSCHs (or one or two layer groups in the case of a single PDSCH), where each PDSCH or layer group is associated with a different TCI state; and the code point in the TCI field of the DCI represents one or two TCI states associated with the scheduled one or two PDSCHs or layer groups." In this case, the two DMRSs of the two PDSCHs or two layer groups are not mapped to the same DMRS CDM group.

[0125] It should be noted that in FR2 operation, a single PDCCH received by the UE using a single TCI state with QCL type D (e.g., a single PDCCH received using a single receive beam) may represent one or more PDSCHs associated with another TCI state with QCL type D (e.g., one of the PDSCHs received using another receive beam). In this case, the UE needs to switch the beam from the point of receiving the last symbol of the single PDCCH to the point of receiving the first symbol of the PDSCH. This beam switching delay is counted as the number of OFDM symbols. For example, at a 60 kHz subcarrier interval, the beam switching delay may be 7 symbols; at a 120 kHz subcarrier interval, the beam switching delay may be 14 symbols.

[0126] For multi-TRP-based PDSCH transmission, a different method is being considered in NR Rel-16.

[0127] One of the already agreed methods involves slot-based time multiplexing of different PDSCHs transmitted from multiple TRPs. An example is illustrated in FIG. 5. In this example, the PDSCHs represent two different PDSCHs, where PDSCH 1 associated with TCI state p is transmitted from TRP 1 and PDSCH 2 associated with TCI state q is transmitted from TRP 2. Since PDSCH 1 and 2 are time multiplexed in different slots, the DMRSs corresponding to the two PDSCHs are transmitted to non-overlapping resources (e.g., different slots). Therefore, the DMRSs for the two PDSCHs can use the same or different CDM groups, or even the exact same antenna port in each slot. In the example in FIG. 5, the DMRS for PDSCH 1 is transmitted using CDM group 0 in slot n, and the DMRS for PDSCH 2 is transmitted using CDM group 0 in slot n+1. In NR Rel-16, the slot-based time-multiplexed PDSCH scheme associated with other TCI states is useful for URLLC.

[0128] Another agreed method involves time-multiplexing different PDSCHs transmitted from multiple TRPs on a mini-slot basis (also known as PDSCH Type B scheduling in the NR specification). An example is illustrated in Fig. 6. In this example, PDSCH represents two different PDSCHs, where PDSCH 1 associated with TCI state p is transmitted from TRP 1 and PDSCH 2 associated with TCI state q is transmitted from TRP 2. Since PDSCH 1 and 2 are time-multiplexed in different mini-slots, the DM-RSs corresponding to the two PDSCHs are transmitted to non-overlapping resources (e.g., different mini-slots). Therefore, the DMRSs for the two PDSCHs can use the same or different CDM groups or even the same antenna port in each mini-slot. In the example of Fig. 6, DMRS for PDSCH 1 is transmitted using CDM group 0 in mini-slot n, and DMRS for PDSCH 2 is transmitted using CDM group 0 in mini-slot n+1. In NR Rel-16, a method of time-multiplexed PDSCH based on mini-slots associated with different TCI states is being considered in URLLC.

[0129] It is noted that in the slot-based and mini-slot-based time multiplexing schemes of FIGS. 5 and 6, PDSCHs transmitted from two TRPs can correspond (e.g., iterations) to the same or different RVs of the same TB. Therefore, the UE can perform soft coupling of the two PDSCHs transmitted from the two TRPs to achieve more stable reception. Although the examples in FIGS. 5 and 6 illustrate two iterations across two TRPs, the slot-based and mini-slot-based time multiplexing schemes are also applicable to N (> 2) iterations across M (> 1) TRPs. means of solving the problem

[0130] An embodiment herein includes a method for repeating a transport block (TB) over a number of transport situations. The method includes the step of exchanging specific signaling between a radio device (e.g., User Equipment (UE)) and a network node (e.g., base station) to repeat the same or different duplicate versions of the TB in a number of non-overlapping transport situations (e.g., mini-slots) corresponding to a number of transport configuration indication (TCI) states having different starting positions. More specifically, the network node transmits a time domain resource allocation (TDRA) to indicate a number of non-overlapping transport situations, and the radio device receives the TDRA indicating a number of non-overlapping transport situations. Accordingly, the radio device can receive repetitions of the TB according to the TDRA. By indicating transport situations in the TDRA, it is possible to efficiently schedule a number of transport situations over a number of TCI states, which helps improve efficiency, reliability, and coverage in a wireless communication network.

[0131] In one embodiment, a method is provided to be executed by a wireless device to repeat a TB across a plurality of transmission situations. The method comprises the step of receiving a TDRA from a network node, wherein the TDRA indicates the reception of a plurality of transmission situations, each having a plurality of different starting positions and corresponding to a plurality of non-overlapping TCI states, for which the same or different duplicate versions of the TB are received. The method also comprises the step of receiving a plurality of transmission situations corresponding to a plurality of TCI states in a plurality of non-overlapping transmission situations.

[0132] In another embodiment, each of a plurality of non-overlapping transmission situations corresponds to a different length or period.

[0133] In another embodiment, each of a plurality of non-overlapping transmission situations corresponds to the same length or period.

[0134] In another embodiment, the method further includes the step of receiving a TDRA from a network node in the TDRA field of a downline control information (DCI) message.

[0135] In another embodiment, the method further includes the step of receiving a TCI field in a DCI message, and the TCI field indicates a plurality of TCI states.

[0136] In another embodiment, the number of transmission situations is explicitly indicated through the TDRA received in the TDRA field.

[0137] In another embodiment, the number of transmission situations and the TDRA for each of the transmission situations are jointly encoded and indicated by the code point of the TDRA field in the DCI message.

[0138] In another embodiment, TDRA corresponds to a start symbol and length defined by the parameter 'startSymbolAndLength'.

[0139] In another embodiment, a plurality of TCI states indicated in the TCI field are cyclically represented among a plurality of indicated transmission situations, wherein one of the transmission situations is associated with one of the plurality of TCI states according to the order of the plurality of TCI states indicated in the TCI field.

[0140] In another embodiment, among a plurality of TCI states, the first TCI state indicated in the TCI field is associated with the first transmission situation among a plurality of transmission situations.

[0141] In another embodiment, when a single state is indicated in the TCI field, the single TCI state is associated with all indicated numbers of multiple transmission situations.

[0142] In another embodiment, the number of transmission situations is indicated by the number of TCI states displayed in the TCI field.

[0143] In another embodiment, a plurality of TCI states indicated in the TCI field include a first TCI state and a second TCI state.

[0144] In another embodiment, among a plurality of transmission situations, an even number of transmission situations is associated with the indicated first TCI state, and among a plurality of transmission situations, an odd number of transmission situations is associated with the indicated second TCI state.

[0145] In another embodiment, only the start symbol and length of the odd-numbered transmission situations among a number of transmission situations are indicated in the TDRA, which is indicated by the code point of the TDRA field in the DCI message.

[0146] In another embodiment, the start symbol of an even-numbered transmission situation among a plurality of transmission situations is determined based on the last symbol of the immediately preceding odd-numbered transmission situation among the plurality of transmission situations.

[0147] In another embodiment, the start symbol of an even-numbered transmission situation among a plurality of transmission situations is determined by adding one (1) to the last symbol of the immediately preceding odd-numbered transmission situation among the plurality of transmission situations.

[0148] In another embodiment, the length of the transmission situation of an even number is defined by the length of the transmission situation of an odd number.

[0149] In another embodiment, 'PDSCH type B' indicated through the TDRA field in the DCI message applies to odd-numbered transmission situations and even-numbered transmission situations among a number of transmission situations.

[0150] In another embodiment, the indicated multiple TCI states correspond to multiple transmission / reception points (TRPs).

[0151] In another embodiment, the method further includes the step of receiving a TDRA from a network node for transmitting multiple upline transmission situations of identical or different duplicate versions of upline TBs from a wireless device to multiple TRPs.

[0152] In another embodiment, the method further includes one or more of the steps of providing user data; and transmitting user data to a host computer via transmission to a base station.

[0153] A wireless device comprising one or more transmitters; one or more receivers; and a processing circuit associated with one or more transmitters and one or more receivers, wherein the processing circuit is configured such that the wireless device receives a Time Domain Resource Allocation (TDRA) from a network node, and the TDRA indicates the reception of multiple transmission situations with the same or different duplicate versions of TB in multiple non-overlapping transmission situations corresponding to multiple transmission configuration indication (TCI) states, each having multiple different starting positions; and to receive multiple transmission situations corresponding to multiple TCI states in multiple non-overlapping transmission situations.

[0154] In another embodiment, the processing circuit is further configured to allow the wireless device to execute a method executed by the wireless device.

[0155] In another embodiment, a method executed by a base station to transmit a TB through a plurality of transmission situations is provided. The method includes the step of transmitting a TDRA to a wireless device. The TDRA indicates the transmission of a plurality of transmission situations, each having a plurality of different starting positions and corresponding to a plurality of non-overlapping TCI states, in which the same or different duplicate versions of the TB are transmitted. The method also includes the step of transmitting a plurality of transmission situations corresponding to a plurality of TCI states in a plurality of non-overlapping transmission situations.

[0156] In another embodiment, each of a plurality of non-overlapping transmission situations corresponds to a different length or period.

[0157] In another embodiment, each of a plurality of non-overlapping transmission situations corresponds to the same length or period.

[0158] In another embodiment, the method further includes the step of transmitting TDRA to a wireless device in the TDRA field of a DCI message.

[0159] In another embodiment, the method further includes the step of transmitting a TCI field in a DCI message, and the TCI field indicates a plurality of TCI states.

[0160] In another embodiment, the number of transmission situations is explicitly indicated through the TDRA transmitted in the TDRA field.

[0161] In another embodiment, the number of transmission situations and the TDRA for each of the transmission situations are jointly encoded and indicated by the code point of the TDRA field in the DCI message.

[0162] In another embodiment, TDRA corresponds to a start symbol and length defined by the parameter 'startSymbolAndLength'.

[0163] In another embodiment, a plurality of TCI states indicated in the TCI field are cyclically represented among a plurality of indicated transmission situations, wherein one of the transmission situations is associated with one of the plurality of TCI states according to the order of the plurality of TCI states indicated in the TCI field.

[0164] In another embodiment, among a plurality of TCI states, the first TCI state indicated in the TCI field is associated with the first transmission situation among a plurality of transmission situations.

[0165] In another embodiment, when a single TCI state is indicated in the TCI field, the single TCI state is associated with all indicated numbers among a number of transmission situations.

[0166] In another embodiment, the number of transmission situations is indicated by the number of TCI states displayed in the TCI field.

[0167] In another embodiment, a plurality of TCI states indicated in the TCI field include a first TCI state and a second TCI state.

[0168] In another embodiment, among a plurality of transmission situations, an even number of transmission situations is associated with the indicated first TCI state, and among a plurality of transmission situations, an odd number of transmission situations is associated with the indicated second TCI state.

[0169] In another embodiment, only the start symbol and length of the odd-numbered transmission situations among a number of transmission situations are indicated in the TDRA, which is indicated by the code point of the TDRA field in the DCI message.

[0170] In another embodiment, the start symbol of an even-numbered transmission situation among a plurality of transmission situations is determined based on the last symbol of the immediately preceding odd-numbered transmission situation among the plurality of transmission situations.

[0171] In another embodiment, the start symbol of an even-numbered transmission situation among a plurality of transmission situations is determined by adding one (1) to the last symbol of the immediately preceding odd-numbered transmission situation among the plurality of transmission situations.

[0172] In another embodiment, the length of the transmission situation of an even number is defined by the length of the transmission situation of an odd number.

[0173] In another embodiment, 'PDSCH type B' indicated through the TDRA field in the DCI message applies to odd-numbered transmission situations and even-numbered transmission situations among a number of transmission situations.

[0174] In another embodiment, the indicated multiple TCI states correspond to multiple TRPs.

[0175] In another embodiment, the method further includes the step of transmitting a TDRA to a wireless device for transmitting multiple upline transmission situations of the same or different duplicate versions of the upline TB from the wireless device to multiple TRPs.

[0176] In another embodiment, the base station includes: a radio unit configured to transmit a TDRA to a radio device, wherein the TDRA indicates the transmission of multiple transmission situations of the same or different duplicate versions of TB in multiple non-overlapping transmission situations corresponding to multiple TCI states, each having multiple different starting positions; and also includes a control system configured to transmit multiple transmission situations corresponding to multiple TCI states in multiple non-overlapping transmission situations.

[0177] In another embodiment, the base station is further configured to execute a method executed by the base station. Brief explanation of the drawing

[0178] The accompanying drawings, incorporated into and forming part of this specification, serve to illustrate various aspects of the present disclosure and, together with the description, explain the principles of the present disclosure. FIG. 1 illustrates an example of a New Radio (NR) time-domain structure having a 15 kHz subcarrier spacing. FIG. 2 illustrates an example of an NR physical resource grid. FIG. 3 illustrates the mapping of front-loaded Demodulation Reference Signal (DMRS) configuration types 1 and 2. FIG. 4 illustrates an example of NR enhancement for a Physical Downline Shared Channel (PDSCH), wherein multiple PDSCHs corresponding to different Transmission Configuration Indication (TCI) states are received from multiple Transmit / Receive Points (TRPs). FIG. 5 illustrates an example of slot-based time-multiplexed PDSCHs from two TRPs. FIG. 6 illustrates an example of mini-slot-based time-multiplexed PDSCHs from two TRPs. FIG. 7 illustrates an example of a cellular communication network in which embodiments of the present invention may be implemented. FIG. 8 is a flowchart illustrating the operation of a wireless device (e.g., UE) configured according to some embodiment of the present invention to improve non-overlapping Time Domain Resource Allocation (TDRA) signaling in multi-TRP operation. FIG. 9 is a flowchart illustrating the operation of a UE to receive indications of multiple PDSCH scheduling by a single Downline Control Information (DCI) message. FIG. 10 is a flowchart illustrating the operation of a base station to improve non-overlapping TDRA signaling in multi-TRP operation. FIG. 11 illustrates an example of different iteration lengths in the final iteration of a slot. FIG. 12 is a structural block diagram of a wireless access node according to some embodiment of the present invention. FIG. 13 is a structural block diagram illustrating a virtualized embodiment of a wireless access node according to some embodiment of the present invention. FIG. 14 is a structural block diagram of a wireless access node according to some other embodiment of the present invention. FIG. 15 is a structural block diagram of a UE according to some embodiment of the present invention.FIG. 16 is a structural block diagram of a UE according to some other embodiment of the present invention. FIG. 17 is a structural block diagram of a communication system including a telecommunication network such as a 3rd Generation Partnership Project (3GPP)-type cellular network, which includes an access network such as a radio access network (RAN) and a core network. FIG. 18 is a structural block diagram of a UE, a base station, and a host computer according to some other embodiment of the present invention. FIG. 19 is a flowchart illustrating a method implemented in a communication system according to one embodiment of the present invention. FIG. 20 is a flowchart illustrating a method implemented in a communication system according to one embodiment of the present invention. FIG. 21 is a flowchart illustrating a method implemented in a communication system according to one embodiment of the present invention. FIG. 22 is a flowchart illustrating a method implemented in a communication system according to one embodiment of the present invention. Specific details for implementing the invention

[0179] The embodiments described below provide information to enable a person skilled in the art to carry out the embodiments and to describe the best mode of carrying out the embodiments. When reading the following description in light of the accompanying drawings, a person skilled in the art will understand the concept of the present disclosure and recognize applications of such concept that are not specifically addressed herein. It should be understood that such concept and application fall within the scope of the present disclosure.

[0180] wireless node As used here, a "radio node" is a wireless access node or a wireless device.

[0181] wireless access nodeAs used herein, a “radio access node” or “radio network node” is any node within a radio access network of a cellular communication network that operates to transmit and / or receive signals wirelessly. Some examples of radio access nodes include, but are not limited to, base stations (e.g., New Radio (NR) base stations (gNB) in a 3GPP 5G NR network or enhanced or evolved node B (eNB) in a 3GPP Long Term Evolution (LTE) network), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, home eNBs, etc.), and relay nodes.

[0182] Core network node As used herein, a "core network node" is any node implementing a core network function or any type of node within the core network. Some examples of core network nodes include, for instance, a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Capability of Service Exposure Function (SCEF), and a Home Subscriber Server (HSS). Some other examples of core network nodes include nodes implementing Access and Mobility Function (AMF), User Plane Function (UPF), Session Management Function (SMF), Authentication Server Function (AUSF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Storage Function (NRF), Policy Control Function (PCF), and Unified Data Management (UDM).

[0183] wireless deviceAs used herein, a “wireless device” is any type of device that has access to (i.e., is serviced by) a cellular communication network by transmitting and / or receiving signals wirelessly to a wireless access node. Some examples of wireless devices include, but are not limited to, User Equipment (UE) devices and Machine Communication (MTC) devices in 3GPP networks.

[0184] network node As used herein, a "network node" is any node that is part of the wireless access network or core network of a cellular communication network / system.

[0185] The description given herein focuses on 3GPP cellular communication systems, and it should be noted that 3GPP terms or terms similar to 3GPP terms are often used. However, the concepts described herein are not limited to 3GPP systems.

[0186] It should be noted that the term "cell" may be mentioned in the description here; however, since a beam may be used instead of a cell, especially in relation to the 5G NR concept, it is important to note that the concept described here is equally applicable to both cells and beams.

[0187] FIG. 7 illustrates an example of a cellular communication network (700) in which an embodiment of the present invention may be implemented. In the embodiment described herein, the cellular communication network (700) is a 5G NR network. In this example, the cellular communication network (700) includes base stations (702-1, 702-2), referred to as gNBs in 5G NR, which control corresponding macro cells (704-1, 704-2). The base stations (702-1, 702-2) are generally referred to collectively as base stations (702) and individually as base stations (702). Similarly, the macro cells (704-1, 704-2) are generally referred to collectively as macro cells (704) and individually as macro cells (704). The cellular communication network (700) may also include a plurality of low-power nodes (706-1 to 706-4) controlling corresponding small cells (708-1 to 708-4). The low-power nodes (706-1 to 706-4) may be small base stations (such as pico or femto base stations) or remote radio heads (RRH), etc. In particular, although not illustrated, one or more of the small cells (708-1 to 708-4) may alternatively be provided by a base station (702). The low-power nodes (706-1 to 706-4) are generally referred to collectively here as low-power nodes (706) and individually as low-power nodes (706). Similarly, the small cells (708-1 to 708-4) are generally referred collectively here as small cells (708) and individually as small cells (708). The base station (702) (and optionally the low-power node (706)) is connected to the core network (710).

[0188] The base station (702) and the low-power node (706) provide service to wireless devices (712-1 to 712-5) in the corresponding cells (704, 708). The wireless devices (712-1 to 712-5) are generally referred to collectively as wireless devices (712) and individually as wireless devices (712). The wireless devices (712) are also sometimes referred to as UEs.

[0189] Currently, there are specific challenges. Although 3GPP has agreed on slot-based and mini-slot-based time multiplexing schemes for multiple Transmit / Receive Points (TRPs), detailed signaling for Time Domain Resource Allocation (TDRA) remains an unresolved issue. An additional unresolved issue is how to associate a specific Physical Downline Shared Channel (PDSCH) transmission from a TRP with a specific iteration, which may be a Radio Resource Control (RRC) that is dynamically configured or displayed via Downline Control Information (DCI).

[0190] Specific aspects and embodiments of the present disclosure may provide solutions to the challenges described above or other challenges. The aspects discussed herein provide a method for signaling multiple non-overlapping time domain resource allocations to a user device (UE) configured to receive slot-based or mini-slot-based time multiplexing-based iterations transmitted through multiple TRPs. An example indicating the start symbol and length of each iteration is also provided.

[0191] Various embodiments addressing one or more of the problems disclosed herein are proposed herein. Before describing some exemplary embodiments in detail, FIG. 8 is a flowchart illustrating the operation of a radio device (e.g., UE) configured to improve non-overlapping TDRA signaling in a multi-TRP operation according to some embodiments of the present invention (e.g., as defined in NR Rel. 15 and / or Rel. 16). The radio device may be configured to receive a TDRA from a network node (e.g., in a DCI message), the TDRA indicates the reception of multiple transmission situations (e.g., multiple mini-slots) of the same or different duplicate versions of a TB, each corresponding to a plurality of non-overlapping transmission situations (e.g., multiple mini-slots), wherein each transmission situation corresponds to a different start position (e.g., a start symbol) (Block 800). The radio device may also be configured to receive multiple transmission situations corresponding to a plurality of TCI states in non-overlapping repeating situations based on scheduling (Block 802).

[0192] FIG. 9 is a flowchart illustrating the operation of a UE receiving indications of multiple PDSCH scheduling (iterations) by a single DCI message. The UE may be configured to receive multiple non-overlapping TDRAs, wherein the UE is configured to receive information on the start symbol and length of each iteration (Block 900).

[0193] FIG. 10 is a flowchart illustrating the operation of a base station that improves non-overlapping TDRA signaling in a multi-TRP operation (e.g., as defined in NR Rel. 15 and / or Rel. 16). The base station may be configured to transmit a TDRA (e.g., in a DCI message) to a radio device (e.g., UE), and the TDRA represents a repetition of multiple transmission situations (e.g., multiple mini-slots) of the same or different duplicate versions of a TB, each corresponding to multiple TCI states, wherein each of the multiple transmission situations corresponds to a different start position (e.g., a start symbol) (Block 1000). The base station may also be configured to transmit multiple transmission situations corresponding to multiple TCI states in non-overlapping transmission situations (Block 1002).

[0194] Specific embodiments may provide one or more of the following technical advantages. The method described herein provides an efficient means for signaling non-overlapping TDRAs to a UE so that the UE can receive slot-based or mini-slot-based time-multiplexed repetitions transmitted through multiple TRPs.

[0195] The NR Rel-15 mechanism for TDRA using the TDRAPDSCH-TimeDomainResourceAllocationList information element for downline (DL) multi-TRP operation may not be suitable for multi-TRP operation because each PDSCH-TimeDomainResourceAllocation in the TimeDomainResourceAllocationList provides only one startSymbolAndLength index. In multi-TRP operation using mini-slot-based time multiplexing (where mini-slots are identical to PDSCH type B scheduling), the starting symbol of the mini-slot corresponding to a different TRP must be different. Generalized, the length of each mini-slot may also be different to provide flexibility. For example, if only 6 symbols are available in two mini-slots, one 4-symbol and one 2-symbol mini-slot may be scheduled.

[0196] A key aspect of the present invention is that the TDRA includes scheduling of a plurality of mini-slots, wherein each mini-slot may have a different starting position and may also have a different time period / length.

[0197] In one embodiment, the TDRA field in the DCI may include a co-encoding of the TDRA for scheduling multiple mini-slots, for example, for multiple PDSCH type B scheduling. For example, the relationship between the end symbols of the nth iteration may be used to define the start symbol for the (n+1)th iteration, and this relationship may be used to reduce the number of bits required for the TDRA in multi-slot scheduling. For example, in the case of back-to-back scheduling, the nth iteration ends at symbol q, and then the (n+1)th iteration starts at symbol q+1. With this compression, it is only necessary to indicate the start of the first iteration, the total length across all iterations, and the number of iterations (of the same period).

[0198] In another embodiment, the starting point of the first iteration, as well as the individual length of each iteration, are signaled. As described above, assuming sequential scheduling, the (n+1)th iteration starts at the first symbol after the nth. In one version of the embodiment, a row in the TDRA table contains at least the starting symbol for the first iteration and N different lengths, where N is the number of iterations. In some versions of the embodiment, the number of iterations is determined by the number of signaled lengths.

[0199] In some embodiments, the number of repetitions is signaled as a column within the TDRA table.

[0200] In an alternative embodiment, the length of one iteration is indicated, and the total length is the product of the number of iterations and the number of OFDM symbols per iteration. In another embodiment, only the start symbol and length of the first iteration are signaled. Iterations continue until the last OFDM symbol of the same slot where the first iteration begins. Iterations cycle through all TCI states indicated in the TCI field of the DCI (note that one TCI state may correspond to one TRP). The number of iterations may not be signaled. For example, if two TCI states (corresponding to TRP1 and TRP2) are indicated, an even number of iterations is transmitted from TRP1 and an odd number of iterations is transmitted from TRP2. The final iteration may have a different iteration and a different length depending on the available OFDM symbols between the start symbol and the last symbol in the slot. FIG. 11 illustrates an example in which a start symbol #4 with an iteration length of 4 symbols and two TCI states (corresponding to two TRPs) are signaled. The first iteration is transmitted from TRP1, and for the second iteration, since the remaining 6 symbols are less than twice the length of the signaled iteration, all 6 symbols are used for the second iteration from TRP2.

[0201] In one embodiment, the number of startSymbolAndLength indices (e.g., a list of startSymbolAndLength indices) is included in each PDSCH-TimeDomainResourceAllocation.

[0202] In one variation of the present embodiment, the startSymbolAndLength index is set to be equal to the repetition count X (e.g., the size of the list). The value of X may be a configured RRC, or X may be represented by the DCI using an information element or "field" in the DCI, for example (the DCI field may be a dedicated field of nX bits in the DCI for representing the repetition count, or an existing field in DCI format 1-1 may be reused for this purpose).

[0203] In one variation of the present embodiment, the iteration count X is co-encoded with the time-domain resource allocation for each iteration. That is, the code point of the TDRA in the DCI represents both the iteration count X and the startSymbolAndLength corresponding to each iteration. This can be achieved by using the following ASN.1 structure to define the interpretation of the TDRA field:

[0204] PDSCH-TimeDomainResourceAllocationList-Rep ::= SEQUENCE

[0205] (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-

[0206] TimeDomainResourceAllocation-Rep

[0207] PDSCH-TimeDomainResourceAllocation-Rep::= SEQUENCE {

[0208] nrofRepetitions INTEGER(1maxNRofRepetitions);

[0209] timeDomainResourceAllocationForEachRep SEQUENCE

[0210] (SIZE(1..nrofRepetitions)) OF PDSCH-TimeDomainResourceAllocation

[0211] }

[0212] PDSCH-TimeDomainResourceAllocation::= SEQUENCE {

[0213] mappingType ENUMERATED {typeA, typeB},

[0214] k0 INTEGER(0..32)

[0215] OPTIONAL, -- Need S

[0216] startSymbolAndLength INTEGER (0..127)

[0217] }

[0218] In some cases, if the TCI field in the DCI represents a single TRP (e.g., a single TCI state indicated in the DCI field, or alternatively, if multiple states are indicated, the indicated TCI states have the same value, for example, using the same entry in the list of configured TCI states), a number of startSymbolAndLength indices is applied to different PDSCH iterations transmitted from a single TRP. In this case, the UE may assume that the same TCI state is maintained for the PDSCH transmitted in all scheduled iterations. In a further embodiment, when this case applies, the UE is allowed to interpolate the channels measured from the DMRS in each mini-slot for all scheduled PDSCH iterations. In other words, the UE may allow channel interpolation to improve channel estimation performance by assuming that the DMRS antenna port in each mini-slot is valid as the same DMRS port for all mini-slots of the PDSCH iteration. Another interpretation is that the effective area in the time dimension of the DMRS antenna port used for the scheduled iterations of PDSCH spans all scheduled iterations of DMRS.

[0219] In an alternative case, if the TCI field in the DCI represents a single TRP (e.g., a single TCI state indicated in the DCI field, or alternatively, if multiple states are indicated, the indicated TCI states have the same value, for example, using the same entry in the list of configured TCI states), the first index of the startSymbolAndLength indices is applied to other PDSCH iterations transmitted from the single TRP. The embodiment related to channel interpolation in the previous paragraph may also apply to this alternative case.

[0220] In one case, the TCI field in the DCI represents M>1 TRPs (e.g., M different TCI states indicated in the DCI field) and the indicated number of iterations is N>2. In this case, in some variations of the present embodiment, the first ceiling (N / M) startSymbolAndLength index in the list corresponds to another PDSCH iteration transmitted from the first TRP associated with the first TCI state indicated in the DCI field. The next ceiling (N / M), or the remaining N-ceiling (N / M) startSymbolAndLength index in the list corresponds to another PDSCH iteration transmitted from the second TRP associated with the second TCI state indicated in the DCI field.

[0221] Alternatively, the startSymbolAndLength index in the list corresponds sequentially to PDSCH transfers from different TRPs. That is, the nth startSymbolAndLength index in the list corresponds to the PDSCH transfer associated with the TCI state mod(n,M).

[0222] In another embodiment, the start symbol and length are defined in different TDRA tables for multiple and single TRP operations. For a single TRP operation, each row of the TDRA table consists of a single start symbol and a single length. For a multiple TRP operation, each row of the TDRA table consists of multiple start symbols and one or more lengths. For multiple TRPs, at least the number of start symbols may be equal to the number of TRPs. Which table is used for which time domain resource allocation may depend on the number of TCI states indicated in the TCI field in the DCI. That is, if the TCI field in the DCI indicates a single TCI state, the first TDRA table for the single TRP operation is used. If the TCI field in the DCI indicates multiple TCI states, the second TDRA table for the multiple TRP operation is used.

[0223] Time resources in two different slots for two different TRPs

[0224] In another embodiment, the time domain resources of two different TRPs may be located in two different slots. Therefore, in addition to startSymbolAndLength, the parameter k0 also needs to be signaled for each TRP. Subsequently, an example of signaling TDRA is described assuming two TRPs.

[0225] PDSCH-TimeDomainResourceAllocationList-MultiTRP ::= SEQUENCE

[0226] (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-

[0227] TimeDomainResourceAllocation-MultiTRP

[0228] PDSCH-TimeDomainResourceAllocation-MultiTRP ::= SEQUENCE {

[0229] mappingType ENUMERATED {typeA, typeB},

[0230] k0-TRP1 INTEGER(0..32)

[0231] OPTIONAL, -- Need S

[0232] startSymbolAndLength-TRP1 INTEGER (0..127)

[0233] k0-TRP2 INTEGER(0..32)

[0234] OPTIONAL, -- Need S

[0235] startSymbolAndLength-TRP1 INTEGER (0..127)

[0236] }

[0237] In another embodiment, since the slot used by TRP2 is expected to be the same or within the next few slots, k0-TRP2 can be signaled as delta k0 instead to reduce the number of bits required. For example, the signaling can be updated as follows:

[0238] PDSCH-TimeDomainResourceAllocationList-MultiTRP ::= SEQUENCE

[0239] (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-

[0240] TimeDomainResourceAllocation-MultiTRP

[0241] PDSCH-TimeDomainResourceAllocation-MultiTRP ::= SEQUENCE {

[0242] mappingType ENUMERATED {typeA,

[0243] typeB},

[0244] k0-TRP1 INTEGER(0..32)

[0245] OPTIONAL, -- Need S

[0246] startSymbolAndLength-TRP1 INTEGER (0..127)

[0247] delta-k0-TRP2 INTEGER(0..4)

[0248] OPTIONAL, -- Need S

[0249] startSymbolAndLength-TRP1 INTEGER (0..127)

[0250] }

[0251] Along with the above, the k0 value for TRP2 is obtained as (k0-TRP1 + delta-k0-TRP2).

[0252] In the above, it was assumed that all TRPs use the same mappingType. Generally, since two TRPs can use different mappingTypes, it is required that the mappingType be signaled separately for each TRP.

[0253] For simplicity, it was assumed above that scheduling spans two TRPs. In general, two or more TRPs may be used to transfer TBs in DL. The same method and principles can be easily extended to apply to two or more TRPs.

[0254] TDRA for Upline (UL) Multi-TRP Operation

[0255] Similar to DL data transmission, the embodiments described herein can be applied to improve TDRA signaling for a physical upline shared channel (PUSCH) when multi-TRP operation is used.

[0256] For example, the embodiment can be modified as follows when applied to PUSCH scheduling. Thus, the k2 value for TRP2 is obtained as (k2-TRP1 + delta-k2-TRP2).

[0257] PUSCH-TimeDomainResourceAllocationList-MultiTRP ::= SEQUENCE

[0258] (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-

[0259] TimeDomainResourceAllocation-MultiTRP

[0260] PUSCH-TimeDomainResourceAllocation ::= SEQUENCE {

[0261] MappingType ENUMERATED {typeA, typeB},

[0262] k2-TRP1 INTEGER(0..32) OPTIONAL, -- Need S

[0263] startSymbolAndLength-TRP1 INTEGER (0..127)

[0264] delta-k2-TRP2 INTEGER(0..32) OPTIONAL, -- Need S

[0265] startSymbolAndLength-TRP2 INTEGER (0..127)

[0266] }

[0267] 부가적인 측면

[0268] FIG. 12 is a structural block diagram of a wireless access node (1200) according to some embodiment of the present disclosure. The wireless access node (1200) may be, for example, a base station (702 or 706). As illustrated, the wireless access node (1200) includes a control system (1202) comprising one or more processors (1204) (e.g., a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), memory (1206), and a network interface (1208). One or more processors (1204) are also referred to herein as processing circuits. Additionally, the wireless access node (1200) includes one or more wireless units (1210), each comprising one or more transmitters (1212) and one or more receivers (1214) coupled to one or more antennas (1216). The wireless units (1210) may be referred to as wireless interface circuits or be part thereof. In some embodiments, the wireless unit (1210) is located outside the control system (1202) and is connected to the control system, for example, via a wired connection (e.g., an optical cable). However, in some other embodiments, the wireless unit (1210) and potentially the antenna (1216) are integrated with the control system (1202). One or more processors (1204) operate to provide one or more functions of the wireless access node (1200) as described herein. In some embodiments, the functions are implemented, for example, by software stored in memory (1206) and executed by one or more processors (1204).

[0269] FIG. 13 is a structural block diagram illustrating a virtualized embodiment of a wireless access node (1200) according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have similar virtualized designs.

[0270] As used herein, a "virtualized" wireless access node is an implementation of a wireless access node (1200) in which at least some of the functions of the wireless access node (1200) are implemented as virtualized components (e.g., through a virtual machine running on a physical processing node within the network). As illustrated, in this example, the wireless access node (1200) comprises, as described above, a control system (1202) comprising one or more processors (1204) (e.g., CPU, ASIC, FPGA, etc.), memory (1206), and a network interface (1208), and one or more wireless units (1210) comprising one or more transmitters (1212) and one or more receivers (1214) each coupled to one or more antennas (1216). The control system (1202) is connected to the wireless units (1210), for example, via an optical cable, etc. The control system (1202) is connected to one or more processing nodes (1300) that are included as part of or coupled to the network (1302) via a network interface (1208). Each processing node (1300) includes one or more processors (1304) (e.g., CPU, ASIC, FPGA, etc.), memory (1306), and a network interface (1308).

[0271] In this example, the functions (1310) of the wireless access node (1200) described herein are implemented in one or more processing nodes (1300) or distributed across the control system (1202) and one or more processing nodes (1300) in any desired manner. In some specific embodiments, some or all of the functions (1310) of the wireless access node (1200) described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by the processing node (1300). As will be understood by those skilled in the art, additional signaling or communication between the processing node (1300) and the control system (1202) is used to perform at least some of the desired functions (1310). In particular, in some embodiments, the control system (1202) may not be included, in which case the wireless unit (1210) communicates directly with the processing node (1300) through a suitable network interface.

[0272] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause at least one processor to perform a function of a wireless access node (1200) or a node (e.g., a processing node (1300)) that implements one or more of the functions (1310) of the wireless access node (1200) in a virtual environment according to any of the embodiments described herein. In some embodiments, a carrier comprising the above-described computer program product is provided. The carrier is one of an electronic signal, an optical signal, a wireless signal, or a computer-readable storage medium (e.g., a non-transient computer-readable medium such as memory).

[0273] FIG. 14 is a structural block diagram of a wireless access node (1200) according to some other embodiment of the present disclosure. The wireless access node (1200) includes one or more modules (1400), each of which is implemented in software. The modules (1400) provide the functions of the wireless access node (1200) described herein. This discussion is equally applicable to the processing node (1300) of FIG. 13, wherein the modules (1400) may be implemented in one of the processing nodes (1300) or distributed across a plurality of processing nodes (1300), and / or distributed across the processing nodes (1300) and the control system (1202).

[0274] FIG. 15 is a structural block diagram of a UE (1500) according to some embodiment of the present disclosure. As illustrated, the UE (1500) comprises one or more processors (1502) (e.g., CPU, ASIC, FPGA, etc.), memory (1504), and one or more transceivers (1506) comprising one or more transmitters (1508) and one or more receivers (1510) each coupled to one or more antennas (1512). The transceivers (1506) comprise a wireless-front-end circuit connected to the antenna (1512) and configured to condition a signal communicated between the antenna (1512) and the processor (1502), as will be understood by those skilled in the art. The processor (1502) is also referred to herein as a processing circuit. The transceivers (1506) are also referred to herein as a wireless circuit. In some embodiments, the functions of the UE (1500) described above may be fully or partially implemented, for example, by software stored in memory (1504) and executed by a processor (1502). It should be noted that the UE (1500) may include additional components not shown in FIG. 15, such as one or more user interface components (e.g., an input / output interface including a display, buttons, a touch screen, a microphone, a speaker, etc., and / or any other component that allows information input to the UE (1500) and / or information output from the UE (1500)), power (e.g., a battery and an associated power circuit), etc.

[0275] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause at least one processor to perform the function of a UE (1500) according to any of the embodiments described herein. In some embodiments, a carrier comprising the above-described computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transient computer-readable medium such as memory).

[0276] FIG. 16 is a structural block diagram of a UE (1500) according to some other embodiment of the present disclosure. The UE (1500) includes one or more modules (1600), each of which is implemented in software. The modules (1600) provide the functions of the UE (1500) described herein.

[0277] Referring to FIG. 17, according to one embodiment, a communication system comprises a telecommunication network (1700), such as a 3GPP-type cellular network, comprising an access network (1702), such as a RAN, and a core network (1704). The access network (1702) comprises a plurality of base stations (1706A, 1706B, 1706C), such as NBs, eNBs, gNBs, or other types of wireless access points (APs), each defining a corresponding coverage area (1708A, 1708B, 1708C). Each base station (1706A, 1706B, 1706C) is capable of connecting to the core network (1704) via a wired or wireless connection (1710). A first UE (1712) located in the coverage area (1708C) is configured to connect wirelessly to the corresponding base station (1706C) or be paged by it. A second UE (1714) in the coverage area (1708A) can wirelessly connect to the corresponding base station (1706A). Although multiple UEs (1712, 1714) are shown in this example, the described embodiment is equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station (1706).

[0278] The telecommunications network (1700) itself is connected to a host computer (1716) which may be implemented in hardware and / or software of a standalone server, a cloud-implemented server, or a distributed server, or implemented as a processing resource of a server farm. The host computer (1716) may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. The connection (1718, 1720) between the telecommunications network (1700) and the host computer (1716) may extend directly from the core network (1704) to the host computer (1716) or may pass through an optional intermediate network (1722). The intermediate network (1722) may be one of a public, private, or hosting network, or a combination of two or more; the intermediate network (1722) may be a backbone network or the Internet, if any; in particular, the intermediate network (1722) may include two or more sub-networks (not shown).

[0279] The communication system of FIG. 17 enables a connection between the connected UEs (1712, 1714) and the host computer (1716) in total. The connection can be described as an Over-the-Top (OTT) connection (1724). The host computer (1716) and the connected UEs (1712, 1714) are configured to communicate data and / or signaling through the OTT connection (1724) using an access network (1702), a core network (1704), any intermediate network (1722), and additional infrastructure (not shown) that may act as an intermediary. The OTT connection (1724) may be transparent in that the participating communication device through which the OTT connection (1724) passes does not recognize the routing of upline and downline communication. For example, the base station (1706) may not be notified of or need to know about the past routing of incoming downline communication, for example, with data originating from the host computer (1716) that is transmitted (e.g., handed over) to the connected UE (1712). Similarly, the base station (1706) does not need to know about the future routing of outgoing upline communication from the UE (1712) toward the host computer (1716).

[0280] According to one embodiment, an exemplary implementation of the UE, base station, and host computer discussed in the previous paragraph is now described with reference to FIG. 18. In the communication system (1800), the host computer (1802) includes hardware (1804) comprising a communication interface (1806) configured to establish and maintain a wired or wireless connection with an interface of another communication device of the communication system (1800). The host computer (1802) further includes a processing circuit (1808) that may have storage and / or processing functions. In particular, the processing circuit (1808) may include one or more programmable processors, ASICs, FPGAs, or combinations thereof adapted to execute instructions (not shown). The host computer (1802) further includes software (1810) that is stored in or accessible by the host computer (1802) and executable by the processing circuit (1808). The software (1810) includes a host application (1812). The host application (1812) may be capable of providing services to a remote user, such as the UE (1814), connected via an OTT connection (1816) terminating at the UE (1814) and the host computer (1802). When providing services to the remote user, the host application (1812) may provide user data transmitted using the OTT connection (1816).

[0281] The communication system (1800) further includes a base station (1818) comprising hardware (1820) that is provided to the telecommunication system and enables communication with a host computer (1802) and a UE (1814). The hardware (1820) may include a communication interface (1822) for establishing and maintaining a wired or wireless connection with an interface of another communication device of the communication system (1800), as well as a wireless interface (1824) for establishing and maintaining at least a wireless connection (1826) with a UE (1814) located in a coverage area (not shown in FIG. 18) that is serviced by the base station (1818). The communication interface (1822) may be configured to facilitate a connection (1828) to the host computer (1802). The connection (1828) may be direct or pass through one or more intermediate networks outside the telecommunication system and / or the core network of the telecommunication system (not shown in FIG. 18). In the illustrated embodiment, the hardware (1820) of the base station (1818) may further include a processing circuit (1830) which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof adapted to execute commands (not illustrated). The base station (1818) further has software (1832) stored internally or accessible via an external connection.

[0282] The communication system (1800) further includes the previously mentioned UE (1814). The hardware (1834) of the UE (1814) may include a wireless interface (1836) configured to establish and maintain a wireless connection (1826) with a base station providing service to the coverage area where the UE (1814) is currently located. The hardware (1834) of the UE (1814) may further include a processing circuit (1838) which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof adapted to execute commands (not shown). The UE (1814) further includes software (1840) that is stored in or accessible by the UE (1814) and executable by the processing circuit (1838). The software (1840) includes a client application (1842). A client application (1842) may be operational to provide services to a human or non-human user via a UE (1814) with the support of a host computer (1802). On the host computer (1802), a host application (1812) running may communicate with a client application (1842) running via an OTT connection (1816) terminating at the UE (1814) and the host computer (1802). When providing services to a user, the client application (1842) may receive request data from the host application (1812) and provide user data in response to the request data. The OTT connection (1816) may transmit both the request data and the user data. The client application (1842) may interact with the user to generate the user data provided.

[0283] It should be noted that the host computer (1802), base station (1818), and UE (1814) shown in FIG. 18 may be similar or identical to the host computer (1716), one of the base stations (1706A, 1706B, 1706C), and one of the UEs (1712, 1714) of FIG. 17, that is to say, the internal operations of these objects are as shown in FIG. 18, and independently the surrounding network topology may be as in FIG. 17.

[0284] In FIG. 18, the OTT connection (1816) is abstractly depicted to describe communication between a host computer (1802) and a UE (1814) via a base station (1818) without any explicit reference to any intermediate device and the exact routing of messages through such device. The network infrastructure may determine routing that can be configured to be hidden from the UE (1814), from the service provider operating the host computer (1802), or from both. While the OTT connection (1816) is active, the network infrastructure may make further decisions to dynamically change routing (e.g., based on load balancing considerations or network reconfiguration).

[0285] The wireless connection (1826) between the UE (1814) and the base station (1818) follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE (1814) using the OTT connection (1816) in which the wireless connection (1826) forms the final segment. A measurement procedure may be provided for the purpose of monitoring the data transfer rate, latency, and other factors improved by one or more embodiments. There may be additional optional network functions for reconfiguring the OTT connection (1816) between the host computer (1802) and the UE (1814) in response to changes in the measurement results. The network functions for the measurement process and / or reconfiguring the OTT connection (1816) may be implemented in the software (1810) and hardware (1804) of the host computer (1802), or in the software (1840) and hardware (1834) of the UE (1814), or both. In some embodiments, a sensor (not illustrated) may be placed in or associated with a communication device through which the OTT connection (1816) passes; the sensor may participate in the measurement process by supplying a value of the monitored quantity exemplified above, or by supplying a value of another physical quantity through which the software (1810, 1840) can calculate or estimate the monitored quantity. Reconfiguration of the OTT connection (1816) may include message formats, retransmission settings, preferred routing, etc.; reconfiguration may not need to affect the base station (1818) and may not be known or perceived by the base station (1818). These processes and functions may be known and practiced in the prior art. In a particular embodiment, the measurement may include dedicated UE signaling to facilitate the measurement of throughput, propagation time, delay, etc. by the host computer (1802).Measurement can be implemented so that software (1810, 1840) monitors propagation time, errors, etc., and uses an OTT connection (1816) to transmit messages, especially empty or 'dummy' messages.

[0286] FIG. 19 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be described with reference to FIG. 17 and FIG. 18. For the sake of simplicity of the description, this section includes only drawing references to FIG. 19. In step (1900), the host computer provides user data. In a substep (1902) of step (1900) (which may be optional), the host computer provides user data by executing a host application. In step (1904), the host computer initiates a transmission carrying the user data to the UE. In step (1906) (which may be optional), the base station transmits the user data carried by the transmission initiated by the host computer to the UE, in accordance with the teachings of the embodiment described throughout this disclosure. In step (1908) (which may be optional), the UE executes a client application associated with the host application executed by the host computer.

[0287] FIG. 20 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be described with reference to FIG. 17 and FIG. 18. For the sake of simplicity of the description, this section includes only drawing references to FIG. 20. In step (2000) of the method, the host computer provides user data. In an optional substep (not shown), the host computer provides user data by running a host application. In step (2002), the host computer initiates a transmission carrying the user data to the UE. The transmission may pass through a base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step (2004), (which may be optional), the UE receives the user data carried by the transmission.

[0288] FIG. 21 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be described with reference to FIG. 17 and FIG. 18. For the sake of simplicity of this description, this section includes only drawing references to FIG. 21. In step (2100) (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step (2102), the UE provides user data. In substep (2104) of step (2100) (which may be optional), the UE provides user data by running a client application. In substep (2106) of step (2102) (which may be optional), the UE runs a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific way in which user data is provided, the UE initiates the transmission of user data to a host computer in step (2108), which may be optional. In step (2110) of the method, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0289] FIG. 22 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include a host computer, a base station, and a UE, which may be described with reference to FIG. 17 and FIG. 18. For the sake of simplicity of the description, this section includes only drawing references to FIG. 22. In step (2200), (which may be optional), according to the teachings of the embodiment described throughout the present disclosure, the base station receives user data from the UE. In step (2202), (which may be optional), the base station initiates the transmission of the received user data to the host computer. In step (2204), (which may be optional), the host computer receives the user data carried by the transmission initiated by the base station.

[0290] Any suitable step, method, feature, function, or advantage disclosed herein may be executed through one or more function units or modules of one or more virtual devices. Each virtual device may include a number of such function units. These function units may be implemented through processing circuits, which may include one or more microprocessors or microcontrollers, as well as other digital hardware such as digital signal processors (DSPs), special-purpose digital logic, etc. Processing circuits may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, as well as instructions for performing one or more techniques described herein. In some implementations, processing circuits may be used to enable each function unit to execute a corresponding function according to one or more embodiments of the present disclosure.

[0291] While the process of the drawings may represent operations in a specific order performed by a specific embodiment of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine specific operations, overlap specific operations, etc.).

[0292] Some exemplary embodiments of the present invention are as follows.

[0293] Group A Examples

[0294] Example 1: A method executed by a radio device to improve non-overlapping time domain resource allocation (TDRA) signaling in a multi-TRP (transmission point) operation (e.g., as defined in NR Rel. 15 and / or Rel. 16), comprising: receiving a downline control information (DCI) message containing a TDRA field (XX800), wherein the TDRA field contains a scheduling for receiving multiple mini-slots (e.g., multiple iterations) from multiple TRPs, each of which corresponds to a different starting position (e.g., a starting symbol); and receiving multiple mini-slots from multiple TRPs based on the scheduling received in the TDRA field of the DCI message (XX802), one or more of the above steps.

[0295] Example 2: In the method of Example 1, each of the plurality of mini-slots corresponds to a different time period / length.

[0296] Example 3: A method of any of the previous examples, wherein the scheduling information contained in the TDRA field includes a co-encoding representing the relationship between the end position (e.g., symbol) of a selected mini-slot among a plurality of mini-slots and the start position (e.g., symbol) of a subsequent mini-slot among a plurality of mini-slots.

[0297] Example 4: A method of any of the previous examples, wherein the scheduling information contained in the TDRA field comprises: an indication (e.g., of a symbol) of the starting position (e.g., of the first iteration) of the first mini-slot; and an indication (e.g., of a number of symbols) of the individual length / period (e.g., of each of the multiple mini-slots) of each of the multiple iterations.

[0298] Example 5: A method of any of the previous examples, wherein the DCI message further includes a TCI field, and the indication in the TCI field indicates a repeating cycle that passes through a plurality of TCI states corresponding to a plurality of TRPs.

[0299] Example 6: A method of any of the previous examples, further comprising the step of receiving multiple TDRAs from multiple TRPs in different slots.

[0300] Example 7: A method of any of the preceding examples comprising: receiving an even number of mini-slots (e.g., repetitions) from the first of a plurality of TRPs; and further comprising one or more of the steps of receiving an odd number of mini-slots (e.g., repetitions) from the second of a plurality of TRPs.

[0301] Example 8: A method of any of the previous examples comprising: a step of providing user data; and a step of transmitting user data to a host computer through transmission to a base station, further comprising one or more of the above.

[0302] Example 9: A method of any of the previous examples, further comprising the step of receiving each TDRA field to enable upline multi-TRP operation.

[0303] Example 10: A method in a user device (UE) (XX900) for receiving indication (of iterations) of a plurality of PDSCH scheduling by a single downline control information (DCI) message, comprising a plurality of non-overlapping time domain resource allocations, wherein the UE receives information of the start symbol and length of each iteration.

[0304] a. The number of repetitions can be explicitly signaled.

[0305] b. The number of iterations can be implicitly derived by the UE based on the start symbol and length.

[0306] c. The length of the final iteration may be the same as or different from the signaled length.

[0307] Each iteration is the first (1 st The first (1) corresponding to the ) repetition st It is associated with the TCI state (i.e., TRP) according to the order of the TCI states displayed in the TCI field starting from the TCI state.

[0308] Example 11: A method according to Example 10 in which the information carried in the TCI status field in the same DCI message provides information required to determine PDSCH time resource allocation for each of a plurality of scheduled PDSCH iterations and additional information.

[0309] Group B Examples

[0310] Example 12: A method executed by a base station to improve non-overlapping time domain resource allocation (TDRA) signaling in a multi-TRP (transmission point) operation (e.g., as defined in NR Rel. 15 and / or Rel. 16), comprising: a step (XX1000) of transmitting a downline control information (DCI) message containing a TDRA field, wherein the TDRA field contains a scheduling for transmitting a plurality of mini-slots (e.g., a plurality of iterations) from a plurality of TRPs, each of which corresponds to a different starting position (e.g., a starting symbol); and a step (XX1002) of transmitting a plurality of mini-slots from a plurality of TRPs based on the scheduling transmitted in the TDRA field of the DCI message.

[0311] Example 13: The method of Example 12 further comprises the step of transmitting a scheduling for transmitting a plurality of mini-slots from a plurality of TRPs, wherein each of the plurality of mini-slots corresponds to a different time period / length.

[0312] Example 14: A method of any of the previous examples, wherein the scheduling information contained in the TDRA field includes a co-encoding representing the relationship between the end position (e.g., symbol) of a selected mini-slot among a plurality of mini-slots and the start position (e.g., symbol) of a subsequent mini-slot among a plurality of mini-slots.

[0313] Example 15: A method of any of the preceding examples, wherein the scheduling information contained in the TDRA field comprises: an indication (e.g., of a symbol) of the starting position (e.g., of the first iteration) of the first mini-slot; and an indication (e.g., of a number of symbols) of the individual length / period (e.g., of each of the multiple mini-slots) of each of the multiple iterations.

[0314] Example 16: A method of any of the previous examples, wherein the DCI message further includes a TCI field, and the indication in the TCI field of the DCI represents a repeating cycle that passes through a plurality of TCI states corresponding to a plurality of TRPs.

[0315] Example 17: A method of any of the previous examples, further comprising the step of transmitting each TDRA field to enable upline multi-TRP operation.

[0316] Example 18: A method of any of the preceding examples comprising: a step of transmitting an even number of mini-slots (e.g., repetitions) from the first of a plurality of TRPs; and a step of transmitting an odd number of mini-slots (e.g., repetitions) from the second of a plurality of TRPs, further comprising one or more of the above steps.

[0317] Example 19: A method of any of the previous examples comprising: a step of acquiring user data; and a step of transmitting user data to a host computer or wireless device, further comprising one or more of these.

[0318] Group C Examples

[0319] Example 20: A radio device for improving non-overlapping time domain resource allocation (TDRA) signaling in multi-TRP (transmission point) operation (e.g., as defined in NR Rel. 15 and / or Rel. 16): comprising: a processing circuit configured to execute any step of any of the steps of any of the examples in Group A; and a power supply circuit configured to supply power to the radio device.

[0320] Example 21: A base station for improving non-overlapping time domain resource allocation (TDRA) signaling in multi-TRP (transmission point) operation (e.g., as defined in NR Rel. 15 and / or Rel. 16), comprising: a processing circuit configured to execute any step of any of the steps of any of the examples in Group B; and a power supply circuit configured to supply power to the base station.

[0321] Example 22: User equipment (UE) for improving non-overlapping time domain resource allocation (TDRA) signaling in multi-TRP (transmission point) operation (e.g., as defined in NR Rel. 15 and / or Rel. 16), comprising: an antenna configured to transmit and receive radio signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to regulate signals communicated between the antenna and the processing circuit; a processing circuit configured to execute any step of any of the steps of any of the examples in Group A; an input interface connected to the processing circuit and configured to allow input of information to the UE to be processed by the processing circuit; an output interface connected to the processing circuit and configured to output information from the UE processed by the processing circuit; and a battery connected to the processing circuit and configured to supply power to the UE.

[0322] Example 23: A communication system comprising a host computer: a processing circuit configured to provide user data; and a communication interface configured to transmit user data to a cellular network for transmission to a user equipment (UE); wherein the cellular network comprises a base station having a wireless interface and a processing circuit, and the processing circuit of the base station is configured to execute any step of any of the steps of any of the examples in Group B.

[0323] Example 24: A communication system comprising a base station in addition to the communication system of the previous example.

[0324] Example 25: A communication system of the previous two examples, further comprising a UE, wherein the UE is configured to communicate with a base station.

[0325] Example 26: A communication system of the previous three examples, wherein the processing circuit of the host computer is configured to execute a host application, thereby providing user data; and the UE comprises a processing circuit configured to execute a client application associated with the host application.

[0326] Example 27: A method implemented in a communication system comprising a host computer, a base station, and user equipment (UE), comprising: providing user data from the host computer; and initiating a transmission from the host computer to the UE through a cellular network comprising a base station, wherein the base station performs any step of any of the steps of any of the examples in Group B.

[0327] Example 28: A method of the previous example, further comprising the step of transmitting user data at a base station.

[0328] Example 29: A method of the previous two examples, wherein user data is provided by running a host application on a host computer, and the method further comprises the step of running a client application associated with the host application on a UE.

[0329] Example 30: User equipment (UE) configured to communicate with a base station, comprising: a wireless interface and a processing circuit configured to execute the method of the previous three examples.

[0330] Example 31: A communication system comprising a host computer: a processing circuit configured to provide user data; and a communication interface configured to transmit user data to a cellular network for transmission to a user device (UE); wherein the UE comprises a wireless interface and a processing circuit, and the components of the UE are configured to execute any step of any of the steps of any of the examples in Group A.

[0331] Example 32: In the communication system of the previous example, the cellular network further comprises a base station configured to communicate with a UE.

[0332] Example 33: A communication system in which, in the communication system of the previous two examples, the processing circuit of the host computer is configured to execute a host application, thereby providing user data; and the processing circuit of the UE is configured to execute a client application associated with the host application.

[0333] Example 34: A method implemented in a communication system comprising a host computer, a base station, and a user equipment (UE), comprising: providing user data at the host computer; and initiating a transmission from the host computer to the UE through a cellular network comprising a base station, wherein the UE performs any step of any of the steps of any of the examples in Group A.

[0334] Example 35: A method of the previous example, further comprising the step of receiving user data from a base station in the UE.

[0335] Example 36: A communication system comprising a host computer, comprising: a communication interface configured to receive user data originating from a transmission from a user device (UE) to a base station; wherein the UE comprises a wireless interface and a processing circuit, and the processing circuit of the UE is configured to execute any step of any of the steps of any of the examples in Group A.

[0336] Example 37: A communication system comprising a UE further comprising, in the communication system of the previous example.

[0337] Example 38: A communication system of the previous two embodiments, further comprising a base station, wherein the base station comprises a wireless interface configured to communicate with a UE and a communication interface configured to transmit user data carried by transmission from the UE to the base station to a host computer.

[0338] Example 39: A communication system in which, in the communication system of the previous three examples, the processing circuit of the host computer is configured to execute a host application; and the processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0339] Example 40: A communication system according to the previous four examples, wherein the processing circuit of the host computer is configured to execute a host application to provide request data; and the processing circuit of the UE is configured to execute a client application associated with the host application to provide user data in response to the request data.

[0340] Example 41: A method implemented in a communication system comprising a host computer, a base station, and user equipment (UE), comprising: receiving user data transmitted from the UE to the base station at the host computer, wherein the UE performs any step of any of the steps of any of the examples in Group A.

[0341] Example 42: A method of the previous example, further comprising the step of providing user data to a base station from the UE.

[0342] Example 43: A method of the previous two examples, further comprising: a step of executing a client application in a UE to provide user data to be transmitted by it; and a step of executing a host application associated with the client application in a host computer.

[0343] Example 44: A method of the previous three examples, comprising: a step of executing a client application in a UE; and a step of receiving input data for the client application in a UE, wherein the input data is provided by a host computer by executing a host application associated with the client application, and wherein user data transmitted is provided by the client application in response to the input data.

[0344] Example 45: A communication system comprising a host computer, comprising: a communication interface configured to receive user data originating from a transmission from a user device (UE) to a base station; wherein the base station comprises a wireless interface and a processing circuit, and the processing circuit of the base station is configured to execute any step of any of the steps of any of the examples in Group B.

[0345] Example 46: A communication system comprising a base station in addition to the communication system of the previous example.

[0346] Example 47: A communication system of the previous two examples, further comprising a UE, wherein the UE is configured to communicate with a base station.

[0347] Example 48: A communication system in which, in the communication system of the previous three embodiments, the processing circuit of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing user data received by the host computer.

[0348] Example 49: A method implemented in a communication system comprising a host computer, a base station, and user equipment (UE), comprising: a step of receiving user data from the base station originating from a transmission received from the UE at the host computer, wherein the UE performs any step of any of the steps of any of the examples in Group A.

[0349] Example 50: A method of the previous example, further comprising the step of receiving user data from a UE at a base station.

[0350] Example 51: A method of the previous two examples, further comprising the step of initiating transmission of received user data to a host computer at a base station.

[0351] At least some of the following abbreviations may be used in this disclosure. In the event of any discrepancy between the abbreviations, the manner used above should be given priority. Where listed multiple times below, the first list should take precedence over subsequent lists.

[0352] 3GPP 3rd Generation Partnership Project

[0353] 5G 5th Generation

[0354] AMF Access and Mobility Function

[0355] AN Access Network

[0356] AP Access Point

[0357] ASIC Application Specific Integrated Circuit

[0358] AUSF Authentication Server Function

[0359] CDM Code Division Multiplexing

[0360] CP Cyclic Prefix

[0361] CPU Central Processing Unit

[0362] CSI Channel State Information

[0363] CSI-RS Channel State Information Reference Signal

[0364] DCI Downlink Control Information

[0365] Discrete Fourier Transform (DFT)

[0366] DFT-S-OFDM Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing

[0367] DL Downlink

[0368] DMRS Demodulation Reference Signal

[0369] DSP Digital Signal Processor

[0370] eNB Enhanced or Evolved Node B

[0371] FPGA Field Programmable Gate Array

[0372] gNB New Radio Base Station

[0373] HSS Home Subscriber Server

[0374] IE Information Element

[0375] LTE Long-Term Evolution

[0376] MCS Modulation and Coding Scheme

[0377] MME Mobility Management Entity

[0378] MTC Machine Type Communication

[0379] MU-MIMO (Multiple User Multiple Input Multiple Output)

[0380] NEF Network Exposure Function

[0381] NF Network Function

[0382] NR New Radio

[0383] NRF Network Function Repository Function

[0384] NSSF Network Slice Selection Function

[0385] OCC Orthogonal Cover Code

[0386] OFDM Orthogonal Frequency Division Multiplexing

[0387] OTT Over-the-Top

[0388] PCF Policy Control Function

[0389] PDC Physical Data Channel

[0390] PDCCH Physical Downlink Control Channel

[0391] P-GW Packet Data Network Gateway

[0392] PDSCH Physical Downlink Shared Channel

[0393] PUSCH Physical Uplink Shared Channel

[0394] QCL Quasi Co-located

[0395] RAM Random Access Memory

[0396] RAN Radio Access Network

[0397] RB Resource Block

[0398] RE Resource Element

[0399] ROM Read Only Memory

[0400] RRC Radio Resource Control

[0401] RRH Remote Radio Head

[0402] RS Reference Signal

[0403] RV Redundancy Version

[0404] SCEF Service Capability Exposure Function

[0405] SCS Smaller Subcarrier Spacing

[0406] SINR Signal to Interference and Noise Ratio

[0407] SLIV Start and Length Indicator Value

[0408] SMF Session Management Function

[0409] SPS Semi-Persistent Scheduling

[0410] TB Transport Block

[0411] TCI Transmission Configuration Indication

[0412] TDRA Time Domain Resource Allocation

[0413] TRP Transmission / Reception Points

[0414] TRS Tracking Reference Signal

[0415] Unified Data Management (UDM)

[0416] UE User Equipment

[0417] UL Uplink

[0418] UPF User Plane Function

[0419] URLLC Ultra-Reliable and Low Latency Communication

[0420] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are deemed to be within the scope disclosed herein. Explanation of the symbols delete

Claims

Claim 1 A method executed by a wireless device (712, 1500) to receive a transport block (TB) over a plurality of transmission occasions, comprising: a step (800) of receiving a time domain resource allocation (TDRA) from a base station (702, 1200) in the TDRA field of a downlink control information (DCI) message, wherein the TDRA indicates the reception of a plurality of transmission occasions of the same or different duplicate versions of the TB in a plurality of non-overlapping transmission occasions corresponding to a plurality of transmission configuration indication (TCI) states, each having a plurality of different starting positions; wherein only the starting symbol and length of the odd-numbered transmission occasion among the plurality of transmission occasions are indicated in the TDRA indicated by the code point of the TDRA field in the DCI message, and further wherein the starting symbol of the even-numbered transmission occasion among the plurality of transmission occasions is determined based on the last symbol of the immediately preceding odd-numbered transmission occasion among the plurality of transmission occasions; A method comprising the step (802) of receiving the plurality of transmission situations corresponding to the plurality of TCI states in the plurality of non-overlapping transmission situations. Claim 2 A method according to claim 1, further comprising the step of receiving a TCI field in the DCI message, wherein the TCI field indicates the plurality of TCI states. Claim 3 A method executed by a base station (702, 1200) to transmit a transport block (TB) over a plurality of transmission situations, comprising: a step (1000) of transmitting a time domain resource allocation (TDRA) to a wireless device (712, 1500) in the TDRA field of a downlink control information (DCI) message, wherein the TDRA each has a plurality of different start positions and represents the transmission of a plurality of transmission situations with the same or different duplicate versions of the TB in a plurality of non-overlapping transmission situations corresponding to a plurality of transmission configuration indication (TCI) states; wherein only the start symbol and length of the odd-numbered transmission situation among the plurality of transmission situations are indicated in the TDRA indicated by the code point of the TDRA field in the DCI message, and the start symbol of the even-numbered transmission situation among the plurality of transmission situations is determined based on the last symbol of the immediately preceding odd-numbered transmission situation among the plurality of transmission situations; and a step (1002) of transmitting the plurality of transmission situations corresponding to the plurality of TCI states in the plurality of non-overlapping transmission situations. Claim 4 A method according to paragraph 3, further comprising the step of transmitting a TCI field in the DCI message, wherein the TCI field indicates the plurality of TCI states. Claim 5 A method according to claim 3 or 4, further comprising the step of transmitting the TDRA to the wireless device (712, 1500) for transmitting the TDRA in the TDRA field of the DCI message after transmitting the TDRA in the wireless device (1000) to the wireless device for transmitting multiple upline transmission situations of the same or different duplicate versions of the upline TB from the wireless device to the multiple TRPs. Claim 6 A method according to any one of claims 1 to 4, wherein each of the plurality of non-overlapping transmission situations corresponds to a different length or period, or each of the plurality of non-overlapping transmission situations corresponds to the same length or period. Claim 7 A method according to any one of claims 1 to 4, wherein the number of multiple transmission situations and the TDRA for each of the multiple transmission situations are jointly encoded and indicated by the code point of the TDRA field in the DCI message, wherein, optionally, the TDRA corresponds to a start symbol and a length defined by the parameter 'startSymbolAndLength'. Claim 8 In claim 7, the plurality of TCI states indicated in the TCI field are cyclic as many times as the indicated number of transmission situations, wherein one transmission situation among the plurality of transmission situations is associated with one of the plurality of TCI states according to the order of the plurality of TCI states indicated in the TCI field, and wherein, optionally, the first TCI state indicated in the TCI field among the plurality of TCI states is associated with the first transmission situation among the plurality of transmission situations. Claim 9 A method according to claim 2 or 4, wherein the number of transmission situations is indicated through the number of TCI states indicated in the TCI field, and the number of TCI states indicated in the TCI field includes a first TCI state and a second TCI state, wherein transmission situations with an even number among the number of transmission situations are associated with the indicated first TCI state and transmission situations with an odd number among the number of transmission situations are associated with the indicated second TCI state. Claim 10 In claim 1 or 3, the start symbol of an even-numbered transmission situation among the plurality of transmission situations is determined by adding one (1) to the last symbol of the immediately preceding odd-numbered transmission situation among the plurality of transmission situations; and / or the length of the even-numbered transmission situation is defined by the length of the odd-numbered transmission situation; and / or the 'PDSCH type B' indicated through the TDRA field in the DCI message is a method applied to the odd-numbered transmission situation and the even-numbered transmission situation among the plurality of transmission situations. Claim 11 A method according to claim 2 or 4, wherein the indicated plurality of TCI states correspond to a plurality of transmission / reception points (TRPs). Claim 12 A method according to claim 2, further comprising the step of receiving the TDRA from the base station (702, 1200) for transmitting a plurality of upline transmission situations of the same or different duplicate versions of the upline TB from the wireless device to the plurality of TRPs, after receiving the TDRA in the TDRA field of the DCI message from the base station (702, 1200) (800). Claim 13 A wireless device (712; 1500) comprising: one or more transmitters (1508); one or more receivers (1510); and a processing circuit (1502) associated with one or more transmitters and one or more receivers, wherein the processing circuit is configured to enable the wireless device to perform the method of claim 1, 2, or 12. Claim 14 A base station (702; 1200) comprising: a wireless unit (1210); and a control system (1202) operably connected to the wireless unit and configured to perform the method of claim 3 or 4.

Images