Communication method, terminal device, and computer-readable medium

Abstract

Embodiments of the present disclosure relate to apparatus, methods, devices, and computer-readable storage media for resource allocation for coverage enhancement. The method includes receiving an indication of a resource allocation mode from a network device at a terminal device to perform uplink data transmission, the resource allocation mode at least indicating resources allocated for uplink data transmission mapped across multiple time slots, the multiple time slots not including symbols configured for downlink transmission; and transmitting uplink data transmission based on the indication. In this way, according to the resource allocation method of the present disclosure, the coverage enhancement capability of a user equipment (UE) can be improved by scheduling resources for a physical uplink shared channel (PUSCH).

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly, to an apparatus, method, device, and computer-readable storage medium for coverage-enhanced resource allocation. Background Art

[0002] To enhance coverage, solutions for allocating resources to the Physical Uplink Shared Channel (PUSCH) for user equipment (UE) have been discussed. In Long Term Evolution (LTE), a sub-physical resource block (sub-PRB) approach is used for UE coverage enhancement. Sub-PRBs can provide UEs with more transmission power because they can accumulate power in the time domain rather than the frequency domain. Summary of the Invention

[0003] In summary, example embodiments of the present disclosure provide a solution for resource allocation for coverage enhancement.

[0004] In a first aspect, a method for communication is provided. The method includes receiving, at a terminal device, from a network device, an indication of a resource allocation pattern to perform uplink data transmission, the resource allocation pattern indicating at least resources allocated for uplink data transmission mapped across a plurality of time slots, the plurality of time slots not including symbols configured for downlink transmission; and transmitting the uplink data transmission based on the indication.

[0005] In a second aspect, a method for communication is provided. The method includes transmitting, at a network device, an indication of a resource allocation pattern to a terminal device for performing uplink data transmission, the resource allocation pattern indicating at least uplink data transmission mapped across a plurality of time slots, the plurality of time slots not including symbols allocated for downlink transmission; and receiving the uplink data transmission based on the indication.

[0006] In a third aspect, a terminal device is provided. The terminal device includes a processor and a memory storing instructions. The memory and the instructions are configured to work together with the processor to enable the terminal device to execute the method according to the first aspect.

[0007] In a fourth aspect, a network device is provided. The network device includes a processor and a memory storing instructions. The memory and the instructions are configured to, together with the processor, enable the network device to execute the method according to the second aspect.

[0008] In a fifth aspect, a computer readable medium having instructions stored thereon is provided, wherein the instructions, when executed on at least one processor of a device, cause the device to perform the method according to the first aspect.

[0009] In a sixth aspect, a computer readable medium having instructions stored thereon is provided, wherein the instructions, when executed on at least one processor of a device, cause the device to perform the method according to the second aspect.

[0010] Other features and advantages of the embodiments of the present disclosure will also be apparent from the following description of specific embodiments read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The embodiments of the present disclosure are presented in an exemplary sense and their advantages are explained in more detail below with reference to the accompanying drawings, in which

[0012] Figure 1 illustrates an example environment in which example embodiments of the present disclosure may be implemented;

[0013] Figure 2 shows a signaling diagram illustrating a procedure for resource allocation for coverage enhancement according to some example embodiments of the present disclosure;

[0014] Figure 3 A flowchart illustrating an example method for resource allocation for coverage enhancement according to some example embodiments of the present disclosure is shown;

[0015] Figure 4 A flowchart illustrating an example method for resource allocation for coverage enhancement according to some example embodiments of the present disclosure is shown;

[0016] Figure 5 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown.

[0017] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0018] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and are intended to help those skilled in the art understand and implement the present disclosure, rather than to limit the scope of the present disclosure in any way. The disclosure described herein can be implemented in various ways other than those described below.

[0019] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0020] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an example embodiment, it is considered within the knowledge of those skilled in the art to implement such feature, structure, or characteristic in conjunction with other embodiments, regardless of whether or not such feature, structure, or characteristic is explicitly described.

[0021] It should be understood that although the terms "first" and "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are merely used to distinguish the functionality of the various elements. As used herein, the term "and / or" includes any and all combinations of one or more of the listed items.

[0022] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are intended to include the plural forms as well. It should also be understood that when used herein, the terms "comprises", "has", and / or "includes" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0023] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as a fifth generation (5G) system, long term evolution (LTE), advanced LTE (LTE-A), wideband code division multiple access (WCDMA), high speed packet access (HSPA), narrowband Internet of Things (NB-IoT), etc. Further, in a communication network, the communication between a terminal device and a network device can be performed according to any suitable generation communication protocol, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) new radio (NR) communication protocol and / or any other protocol currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of the communication field, there will certainly be future types of communication technologies and systems that can embody the present disclosure. It should not be considered that the scope of the present disclosure is limited to only the above-mentioned systems.

[0024] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services. A network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR next-generation NodeB (gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node (such as a femto, pico, etc.), depending on the terminology and technology applied.

[0025] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over Internet protocol (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated process chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to the mobile terminal (MT) part of an integrated access and backhaul (IAB) node (also known as a relay node). In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0026] Although in various example embodiments, the functionality described herein may be performed in fixed and / or wireless network nodes, in other example embodiments, the functionality may be implemented in a user equipment device (such as a mobile phone or tablet or laptop or desktop computer or mobile IoT device or fixed IoT device). The user equipment device may, for example, be equipped with corresponding capabilities as described in conjunction with (multiple) fixed and / or wireless network nodes, where appropriate. The user equipment device may be a user device and / or a control device, such as a chipset or processor, which is configured to control the user device when installed in the user device. Examples of such functionality include boot server functionality and / or home subscriber servers, which may be implemented in the user equipment device by providing software to the user equipment device that is configured to cause the user equipment device to perform from the perspective of these functions / nodes.

[0027] Figure 1 An example communication network 100 is shown in which embodiments of the present disclosure may be implemented. Network 100 includes a terminal device 110 and a network device 120. Hereinafter, terminal device 110 may also be referred to as UE 110, and network device 120 may be referred to as gNB 120. Terminal device 110 and network device 120 may communicate with each other. It should be understood that the number of terminal devices and network devices is for illustrative purposes only and does not imply any limitation. Network 100 may include any appropriate number of terminal devices and network devices suitable for implementing embodiments of the present disclosure.

[0028] Depending on the communication technology, network 100 can be a code division multiple access (CDMA) network, a time division multiple access (TDMA) network, a frequency division multiple access (FDMA) network, an orthogonal frequency division multiple access (OFDMA) network, a single carrier frequency division multiple access (SC-FDMA) network, or any other network. The communications discussed in network 100 can conform to any suitable standard, including but not limited to new radio access (NR), long term evolution (LTE), evolved LTE, advanced LTE (LTE-A), wideband code division multiple access (WCDMA), code division multiple access (CDMA), cdma2000, and global system for mobile communications (GSM), etc. In addition, communications can be performed according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include but are not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, and fifth generation (5G) communication protocols. The technology described herein can be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below for LTE, and LTE terminology is used in much of the description below.

[0029] As mentioned above, solutions for resource allocation of the Physical Uplink Shared Channel (PUSCH) for User Equipment (UE) have been discussed for coverage enhancement.Some methods have been proposed for PUSCH enhancement.

[0030] To deliver packets to the gNB, UEs can be scheduled with a higher modulation and coding scheme (MCS) and fewer resources if channel conditions are favorable, or with a lower MCS and greater resources if channel conditions are poor. For UEs at the cell edge, larger resource allocations are less desirable due to limited power budgets. Therefore, cell-edge UEs are most likely to engage in narrowband transmissions with a low MCS (QPSK and a lower coding rate). Such a configuration often requires the UE to split higher-layer packets into multiple segments and transmit the packets using multiple small TBs across multiple UL grants. For example, if a UE has a 1280-bit packet (e.g., a video call), the UE can transmit the packet in a single timeslot using 16 RBs, or split it into four segments, each with 320 bits, and transmit them across four timeslots using 4 RBs for better coverage. It should be understood that the latter option is clearly a better choice for cell-edge UEs. Therefore, it has been proposed that cell-edge UEs can transmit packets over multiple timeslots. That is, the UE can be scheduled to transmit larger TBs using REs across multiple timeslots.

[0031] In addition, in Long Term Evolution (LTE), a sub-physical resource block (sub-PRB) approach is adopted for coverage-enhanced UEs. Sub-PRBs can give UEs more transmission power because UEs can accumulate power in the time domain rather than the frequency domain. For example, 4 resource blocks (RBs) in the frequency domain × 1 time slot in the time domain have the same number of time-frequency resource elements in OFDM as 1 RB in the frequency domain × 4 time slots in the time domain. For another example, 1 RB in the frequency domain × 1 time slot in the time domain has the same number of time-frequency resource elements (TFRE) in OFDM as 0.25 RB in the frequency domain × 4 time slots in the time domain. Shifting REs from the frequency domain to the time domain while maintaining TFRE can provide more power and save CRC bits.

[0032] Resource units are used to describe the mapping of PUSCH allocated using sub-PRBs to resource elements for BL / CE UEs. A resource unit is defined as SC-FDMA symbols and frequency domain consecutive subcarriers, where and Given in the table below.

[0033]

[0034] Table 1: For PUSCH and Supported combinations of PUSCH using sub-PRB allocation for frame structure type 1 and frame structure type 2

[0035] The present disclosure proposes a solution for resource selection for resource allocation for coverage enhancement. In this solution, a UE can receive an indication of a resource allocation pattern from a network device to perform uplink data transmission. The resource allocation pattern can at least indicate that the resources allocated for uplink data transmission can be mapped onto multiple time slots available for uplink data transmission. The UE can then perform uplink data transmission based on the indication. In this way, according to the resource allocation method of the present disclosure, the coverage enhancement capability for the UE can be improved by scheduling resources for the PUSCH.

[0036] The following will refer to Figure 2 The principles and implementation of the present invention are described in detail, which shows a schematic process of resource allocation for coverage enhancement. For the purpose of discussion, reference will be made to Figure 1 Describe process 200. Process 200 may involve Figure 1 The terminal device 110 and the network device 120 are shown.

[0037] like Figure 1 As shown in FIG, gNB 120 may generate 210 an indication of a resource allocation pattern for UE 110 to perform uplink data transmission. The resource allocation pattern indicates at least uplink data transmission mapped across a plurality of time slots.

[0038] As an option, the resource allocation mode may be referred to as slot bundling mode. In slot bundling mode, the resources allocated to a UE for transmitting a transport block in uplink data transmission may be mapped across multiple slots available for uplink data transmission. For example, the multiple slots may be multiple consecutive PUSCH slots. PUSCH slots mean that, based on the TDD-UL-DL-Configuration, no symbol in the PUSCH is indicated as DL.

[0039] As another option, the resource allocation mode may also be referred to as a sub-PRB mode, which may also be referred to as a sub-RB mode hereinafter. In the sub-RB mode, resources for uplink data transmission may be configured with a set of sub-RBs, which may be mapped to multiple time slots available for uplink data transmission. For example, the multiple time slots may be multiple consecutive PUSCH time slots.

[0040] gNB 120 may then transmit 220 an indication of the resource allocation mode to UE 110. In some example embodiments, the indication of the slot bundling mode may be indicated to UE 110 statically by radio resource control (RRC) signaling or dynamically by downlink control information (DCI).

[0041] In case the resource allocation mode refers to a slot bundling mode, the slot bundling mode may be configured to the UE 110 with transport block scaling based on the indication.

[0042] If slot bundling is configured, the resource elements (k′, l, n) allocated for PUSCH are assigned according to [6, TS 38.214]. p，μ The mapping shall be in increasing order of first index k′ on the assigned virtual resource block, then index l, then index n, where k′=0 is the first subcarrier in the smallest numbered virtual resource block assigned for transmission, the starting position of index l is given by [6, TS38.214], and n=0 is the first time slot in the time slot bundling.

[0043] In this case, the indication of the timeslot bundling mode may include the number of multiple consecutive PUSCH timeslots, which may be referred to as "G" hereinafter. In some example embodiments, the number of multiple timeslots "G" may be indicated in a bit field in the DCI or as a parameter in the RRC signaling.

[0044] The number of multiple time slots "G" may also be indicated by encoding the number of multiple time slots "G" in combination with a start and length indicator value (SLIV) to obtain SLGIV, where SLGIV=SLIV+105*G.

[0045] The starting symbol S may be relative to the start of the slot, and the number L of consecutive symbols counted from the symbol S allocated for PUSCH is determined from the start of the indexed row and the length indicator SLIV: if (L-1) ≤ 7, then SLIV = 14 (L-1) + S, otherwise SLIV = 14 (14-L+1) + (14-1-S), where 0 <L≤14-S。

[0046] Furthermore, the indication of the slot bundling mode may also include a set of resource blocks allocated for transmitting a transport block in the uplink data transmission.

[0047] When calculating the TB size, the slot bundling size should be considered to obtain the equivalent used RBs. The equivalent RB is RB*G. Alternatively, when determining the total number of REs, the number of REs in each slot is accumulated.

[0048] The total number of REs allocated for PUSCH (N RE ) can be determined by the following formula:

[0049] N RE =min(156, N′ RE )*n RB *g (1) where n PRB is the total number of PRBs allocated to the UE, and g is the slot bundling size when slot bundling is used.

[0050] The number of REs allocated for PUSCH in a PRB (N′ RE ) can be determined by the following formula:

[0051]

[0052] in is the number of subcarriers in the frequency domain in a physical resource block, is the number of symbols L allocated by the PUSCH for a scheduled PUSCH according to clause 6.1.2.1 or for a configured PUSCH according to clause 6.1.2.3, is the number of REs for DM-RS per PRB in the allocated duration, including the overhead of DM-RS CDM groups without data, as described in clause 6.1.2.3 for PUSCH with configured grants, or as described in DCI format 0_0 in clause 6.2.2 or as indicated in DCI format 0_1 ​​or DCI format 0_2, and It is the overhead configured by the higher-layer parameter xOverhead in PUSCH-ServingCellConfig. is not configured (a value from 6, 12, or 18), then is assumed to be 0. For Msg3 transmission, is always set to 0. In case of PUSCH repetition type B, assuming the nominal repetition has a duration of L symbols without segmentation, was determined.

[0053] In some example embodiments, the indication of the slot bundling mode may further include a condition for triggering the resource allocation mode. The condition may be associated with the number of RBs in a set of resources allocated for transmitting transport blocks in uplink data transmission. For example, the slot bundling mode may be configured to be triggered only when RBs <= X, e.g., X = 3. When the allocated RBs > X, the traditional single slot mode is used. When the allocated RBs <= X, if slot bundling mode has been configured, the slot bundling mode is used.

[0054] You can also configure the timeslot bundling mode to be triggered only when MCS <= X, for example, X = 3. When the assigned MCS > X, the traditional single timeslot mode is used. When the assigned MCS <= X, if timeslot bundling mode has been configured, timeslot bundling mode is used.

[0055] You can also configure timeslot bundling to be triggered only when L <= X, for example, X == 7. L is the symbol length in a timeslot. When the allocated L > X, traditional single timeslot mode is used. When the allocated L > X, timeslot bundling is used if configured.

[0056] In some example embodiments, the indication of the slot bundling mode may further indicate how resources allocated for transport blocks in uplink data transmissions are mapped across multiple slots when a physical uplink control channel (PUCCH) overlaps with the slot-bundled transmission. For example, uplink control information (UCI) may be multiplexed with the slot-bundled PUSCH.

[0057] In some example embodiments, the UCI resources may puncture the PUSCH data resources, i.e., PUSCH data that is first mapped to the resources and then to the UCI will overwrite the data later. The complexity for the timeslot bundling process is reduced by not considering the UCI first.

[0058] In some example embodiments, when UCI is multiplexed with TBs, the offset used to calculate the ratio of UCI to data is (beta_offset*G), where beta_offset is given by:

[0059]

[0060] in

[0061] -O ACK is the number of HARQ-ACK bits;

[0062] -If O ACK ≥360, then L ACK =11; otherwise L ACK is the number of CRC bits for HARQ-ACK determined according to clause 6.3.1.2.1;

[0063]

[0064] -C uL-SCH is the number of UL-SCH code blocks for PUSCH transmission;

[0065] - If the DCI format scheduling the PUSCH transmission includes a CBGTI field indicating that the UE should not transmit the rth code block, then Kr＝0 Otherwise, K r is the rth code block size of the UL-SCH for PUSCH transmission;

[0066] is the scheduled bandwidth of PUSCH transmission, expressed as the number of subcarriers;

[0067] It is the OFDM symbol carrying PTRS in PUSCH transmission.

[0068] The number of subcarriers in ;

[0069] It is used in PUSCH transmission for The number of resource elements that can be used for transmission of UCI in OFDM symbol 1, is the total number of OFDM symbols for PUSCH, including all OFDM symbols used for DMRS;

[0070] - For any OFDM symbol carrying PUSCH DMRS,

[0071] - For any OFDM symbol that does not carry DMRS for PUSCH,

[0072]

[0073] -α is configured by the high-level parameter scaling;

[0074] -10 is the symbol index of the first OFDM symbol in PUSCH transmission, after the first DMRS symbol(s), that does not carry DMRS for PUSCH.

[0075] In some example embodiments, in the case where the resource allocation mode refers to a sub-RB mode, the resources allocated for UE 110 to perform uplink data transmission may be configured with a group of sub-RBs.

[0076] In this case, the indication of the resource allocation mode may include configuration information for at least one resource unit associated with a group of RBs. For example, the configuration information may include a subcarrier length of a sub-RB and a time slot length of a sub-RB to generate a resource unit.

[0077] In some example embodiments, multiple resource units may be configured by RRC signaling, and the target resource unit to be used in uplink data transmission may be dynamically indicated in the DCI through grant scheduling. For example, the index of the target resource unit may be indicated by the DCI.

[0078] In some example embodiments, the indication of the resource allocation pattern may also include an allocation of a set of RBs in the time domain and the frequency domain.

[0079] For the frequency domain, only one set of RBs among all RBs in a bandwidth part (BWP) for sub-RB purposes may be configured, for example, by RRC signaling. Bit said, is the number of configured resource units. If the bit field is equal to k, the (k+1)th RU is indicated to the UE.

[0080] For the time domain, the number 'K' of consecutive PUSCH slots not indicated as DL based on tdd-UL-DL-Configuration may be configured as resources for sub-RB transmission.

[0081] In addition, the indication of the resource allocation mode may also include a condition for triggering the sub-RB mode. For example, RRC may configure an indication of dynamic switching between sub-RB resource allocation and traditional resource allocation, for example, through a 1-bit field indication.

[0082] In addition, the indication of the resource allocation pattern may also include the MCS calculation configured for a group of RBs. The total number of REs allocated for PUSCH (N RE ) can be determined by the following formula:

[0083] N RE =min(156, N′ RE )·n PRB (4)

[0084] where nPRB is the total number of PRBs allocated to the UE, or for sub-PRB allocation,

[0085] Alternatively, the indication of the resource allocation pattern may also include the power control mode configured for a group of RBs. For sub-PRB power control, the number of RBs should be 1 instead of (for example) 0.25 to gain power. This is because M=0.25 does not increase power compared to full RB allocation.

[0086] If a UE transmits a PUSCH on an active UL BWPb of carrier f in serving cell c using a parameter set configuration with index j and a PUSCH power control adjustment state with index l, the UE determines the PUSCH transmission power P at PUSCH transmission opportunity i. PUSCH，b,f，c (i, j, q d , l) is

[0087]

[0088] in is the bandwidth of the PUSCH resource assignment, expressed in the number of resource blocks for PUSCH transmission opportunity i on carrier f of serving cell c, and μ is the SCS configuration defined in [4, TS 38.211]. For sub-RB allocation,

[0089] Alternatively, the indication of the resource allocation mode may also include a transmission mode of a demodulation reference signal (DMRS) associated with a group of RBs. As an option, sub-RB frequency resource allocation is used only for PUSCH data. The DMRS used for the sub-RB mode is the full RB DMRS where the sub-RB is located, that is, the DMRS bandwidth > PUSCH bandwidth. As another option, only DMRS sequence generation is used when transform precoding is disabled. Only DMRS in the frequency domain overlapping with the sub-RB frequency resource can be used, that is, the DMRS bandwidth <= PUSCH bandwidth.

[0090] Return to reference Figure 2 , UE 110 may transmit 230 an uplink data transmission to gNB 120 based on the indication of the resource allocation pattern.

[0091] Through the different resource allocation modes proposed in the present invention, the coverage enhancement capability for UE can be improved.

[0092] Figure 3 A flow chart of an example method 300 for resource allocation for coverage enhancement according to some example embodiments of the present disclosure is shown. The method 300 may be implemented in a manner such as Figure 1 For the purpose of discussion, reference will be made to the terminal device 110 shown in FIG. Figure 1 Method 300 is described.

[0093] At 310, the terminal device receives an indication of a resource allocation pattern from the network device to perform uplink data transmission. The resource allocation pattern at least indicates uplink data transmission mapped on a plurality of time slots, and the plurality of time slots does not include symbols configured for downlink transmission.

[0094] In some example embodiments, the terminal device may receive the indication via RRC or DCI.

[0095] At 320, the terminal device transmits an uplink data transmission based on the indication.

[0096] In some example embodiments, the terminal device may obtain from the indication a set of parameters associated with the resource allocation mode, the set of parameters comprising at least one of: the number of multiple time slots; a condition for triggering the resource allocation mode; and a usage mode for transmitting uplink control information together with uplink data transmission.

[0097] In some example embodiments, the number of multiple time slots is indicated by one of: a bit field in downlink control information; a parameter in radio resource control signaling; or a combined encoding with start and length indicator values ​​that indicate a symbol of the multiple time slots allocated for uplink data transmission.

[0098] In some example embodiments, the condition for triggering the resource allocation pattern is associated with at least one of: a modulation and coding scheme configured for uplink data transmission; and a symbol length of a time slot in the plurality of time slots.

[0099] In some example embodiments, the usage mode indicates one of: uplink data transmission is multiplexed with uplink control information; and uplink data transmission is overwritten by the uplink control information.

[0100] In some example embodiments, the resource allocation pattern indicates a set of subcarriers in a resource block to be used for uplink data transmission.

[0101] In some example embodiments, the terminal device can obtain a set of parameters associated with the resource allocation mode from the indication, the set of parameters including at least one of the following: configuration information for at least one resource unit associated with at least one subcarrier in a group of subcarriers; allocation of a group of resource blocks associated with the resource unit in the time domain and the frequency domain; conditions for triggering the resource allocation mode; a power control mode configured for the group of resource blocks; a modulation and coding scheme configured for the group of resource blocks; and a transmission mode of a demodulation reference signal associated with a group of resource blocks.

[0102] In some example embodiments, the configuration information for the resource units includes: a subcarrier length of a resource block in a set of resource blocks; a number of at least one resource unit; and an index of a resource unit in the at least one resource unit that can be used for uplink data transmission.

[0103] Figure 4 A flow chart of an example method 400 for resource allocation for coverage enhancement according to some example embodiments of the present disclosure is shown. The method 400 may be implemented in a manner such as Figure 1 For the purpose of discussion, reference will be made to the network device 120 shown in FIG. Figure 1 Method 400 is described.

[0104] At 410, the network device transmits an indication of a resource allocation pattern to perform uplink data transmission. The resource allocation pattern indicates at least uplink data transmission mapped across a plurality of time slots, and the plurality of time slots does not include symbols configured for downlink transmission.

[0105] In some example embodiments, the network device may transmit the indication via RRC or DCI.

[0106] In some example embodiments, a network device may transmit a set of parameters associated with a resource allocation pattern, the set of parameters including at least one of: a number of multiple time slots; a condition for triggering the resource allocation pattern; and a usage pattern for transmitting uplink control information along with uplink data transmission.

[0107] In some example embodiments, the number of multiple time slots is indicated by one of: a bit field in downlink control information; a parameter in radio resource control signaling; or a combined encoding with start and length indicator values ​​that indicate a symbol of the multiple time slots allocated for uplink data transmission.

[0108] In some example embodiments, the condition for triggering the resource allocation pattern is associated with at least one of: a modulation and coding scheme configured for uplink data transmission; and a symbol length of a time slot in the plurality of time slots.

[0109] In some example embodiments, the usage mode indicates one of: uplink data transmission is multiplexed with uplink control information; and uplink data transmission is overwritten by the uplink control information.

[0110] In some example embodiments, a network device may transmit a set of parameters associated with a resource allocation mode, the set of parameters including at least one of the following: configuration information for at least one resource unit associated with at least one subcarrier in a set of subcarriers; allocation of a set of resource blocks associated with the resource unit in the time domain and the frequency domain; conditions for triggering the resource allocation mode; a power control mode configured for the set of resource blocks; a modulation and coding scheme configured for the set of resource blocks; and a transmission mode of a demodulation reference signal associated with the set of resource blocks.

[0111] In some example embodiments, the configuration information for the resource units includes: a subcarrier length of a resource block in a set of resource blocks; a number of at least one resource unit; and an index of a resource unit in the at least one resource unit that can be used for uplink data transmission.

[0112] At 420, the network device receives an uplink data transmission based on the indication.

[0113] Figure 5 is a simplified block diagram of a device 500 suitable for implementing embodiments of the present disclosure. The device 500 may be provided to implement a communication device, such as Figure 1 As shown in the figure, the device 500 includes one or more processors 510, one or more memories 540 coupled to the processor 510, and one or more transmitters and / or receivers (TX / RX) 540 coupled to the processor 510.

[0114] The TX / RX 540 is used for bidirectional communication. The TX / RX 540 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.

[0115] Processor 510 may be of any type suitable for the local technology network and, as non-limiting examples, may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 500 may have multiple processors, such as application specific integrated circuit chips that are time-slave to a clock synchronized with a main processor.

[0116] The memory 520 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 524, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 522 and other volatile memories that do not persist during a power outage.

[0117] Computer program 530 includes computer executable instructions that are executed by associated processor 510. Program 530 may be stored in ROM 520. Processor 510 may perform any suitable actions and processes by loading program 530 into RAM 520.

[0118] The embodiments of the present disclosure can be implemented with the aid of a program 530 so that the device 500 can execute the following steps: Figures 2 to 4 Any process of the present disclosure discussed. The embodiments of the present invention can also be implemented by hardware or by a combination of software and hardware.

[0119] In some embodiments, program 530 may be tangibly embodied in a computer-readable medium that may be included in device 500 (such as in memory 520) or in other storage devices accessible to device 500. Device 500 may load program 530 from the computer-readable medium into RAM 522 for execution. Computer-readable media may include any type of tangible, non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0120] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0121] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as those included in program modules, which are executed in a device on a target real or virtual processor to perform the above-referenced Figure 3-Figure 4 Methods 300 and 400 are described. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or split between program modules as needed. Machine-executable instructions for program modules can be executed on a local device or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0122] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when these program codes are executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0123] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0124] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of computer-readable storage media would include: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0125] In addition, although each operation is described in a specific order, this should not be understood as requiring such operations to be performed in the specific order shown or in sequence, or performing all illustrated operations to achieve desired results. In some scenarios, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of this disclosure, but should be interpreted as descriptions of features that may be specific to a particular embodiment. Some features described in the context of separate embodiments may also be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination.

[0126] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method performed by a terminal device, comprising: receiving downlink control information (DCI) indicating a value corresponding to a number of time slots allocated for transport block processing for a physical uplink shared channel (PUSCH); as well as transmitting uplink control information on the PUSCH based on the number of time slots, The uplink control information is a hybrid automatic repeat request acknowledgement HARQ-ACK, wherein the HARQ-ACK is transmitted on the PUSCH based on the following equation: where Z is calculated by dividing the number of time slots by Multiplying them together, we get is the number of HARQ-ACK bits; if ,but ;otherwise is the number of cyclic redundancy check (CRC) bits for HARQ-ACK; , and represents the offset value; is the number of uplink shared channel UL-SCH code blocks for PUSCH transmission; If the downlink control information DCI format for scheduling the PUSCH transmission includes a code block group transmission information CBGTI field indicating that the terminal device should not transmit the rth code block, then =0; otherwise, is the rth code block size of the UL-SCH for the PUSCH transmission; is the scheduled bandwidth of the PUSCH transmission, expressed as the number of subcarriers; It is the orthogonal frequency division multiplexing OFDM symbol carrying the phase tracking reference signal PTRS in the PUSCH transmission l The number of subcarriers in ; is the PUSCH transmission for can be used in OFDM symbols l The number of resource elements used for transmission of UCI in is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for the demodulation reference signal DMRS; For any OFDM symbol carrying the DMRS of the PUSCH, ; For any OFDM symbol that does not carry the DMRS of the PUSCH, ; By high-level parameters scaling Configuration; It is the symbol index of the first OFDM symbol after the first DMRS symbol in the PUSCH transmission and not carrying the DMRS of the PUSCH.

2. The method according to claim 1, further comprising: The transport block size is determined by determining the total number of resource elements (REs) allocated for the PUSCH based on the number of slots.

3. A method performed by a network device, comprising: downlink control information DCI transmitting an indication value, the value corresponding to the number of time slots allocated for transport block processing for a physical uplink shared channel PUSCH; as well as receiving uplink control information on the PUSCH based on the number of time slots, The uplink control information is a hybrid automatic repeat request acknowledgement HARQ-ACK, wherein the HARQ-ACK is received on the PUSCH based on the following equation: where Z is calculated by dividing the number of time slots by Multiplying them together, we get is the number of HARQ-ACK bits; if ,but ;otherwise is the number of cyclic redundancy check (CRC) bits for HARQ-ACK; , and represents the offset value; is the number of uplink shared channel UL-SCH code blocks for PUSCH transmission; If the downlink control information DCI format for scheduling the PUSCH transmission includes a code block group transmission information CBGTI field indicating that the terminal device should not transmit the rth code block, then =0; otherwise, is the rth code block size of the UL-SCH for the PUSCH transmission; is the scheduled bandwidth of the PUSCH transmission, expressed as the number of subcarriers; It is the orthogonal frequency division multiplexing OFDM symbol carrying the phase tracking reference signal PTRS in the PUSCH transmission l The number of subcarriers in ; is the PUSCH transmission for can be used in OFDM symbols l The number of resource elements used for transmission of UCI in is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for the demodulation reference signal DMRS; For any OFDM symbol carrying the DMRS of the PUSCH, ; For any OFDM symbol that does not carry the DMRS of the PUSCH, ; By high-level parameters scaling Configuration; It is the symbol index of the first OFDM symbol after the first DMRS symbol in the PUSCH transmission and not carrying the DMRS of the PUSCH.

4. The method according to claim 3, further comprising: The transport block size is determined by determining the total number of resource elements (REs) allocated for the PUSCH based on the number of slots.

5. A terminal device, comprising a processor, wherein the processor is configured to cause the terminal device to: receiving downlink control information (DCI) indicating a value corresponding to a number of time slots allocated for transport block processing for a physical uplink shared channel (PUSCH); and transmitting uplink control information on the PUSCH based on the number of time slots, The uplink control information is a hybrid automatic repeat request acknowledgement HARQ-ACK, The terminal device is caused to transmit the HARQ-ACK on the PUSCH based on the following equation: where Z is calculated by dividing the number of time slots by Multiplying them together, we get is the number of HARQ-ACK bits; if ,but ;otherwise is the number of cyclic redundancy check (CRC) bits for HARQ-ACK; , and represents the offset value; is the number of uplink shared channel UL-SCH code blocks for PUSCH transmission; If the downlink control information DCI format for scheduling the PUSCH transmission includes a code block group transmission information CBGTI field indicating that the terminal device should not transmit the rth code block, then =0; otherwise, is the rth code block size of the UL-SCH for the PUSCH transmission; is the scheduled bandwidth of the PUSCH transmission, expressed as the number of subcarriers; It is the orthogonal frequency division multiplexing OFDM symbol carrying the phase tracking reference signal PTRS in the PUSCH transmission l The number of subcarriers in ; is the PUSCH transmission for can be used in OFDM symbols l The number of resource elements used for transmission of UCI in is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for the demodulation reference signal DMRS; For any OFDM symbol carrying the DMRS of the PUSCH, ; For any OFDM symbol that does not carry the DMRS of the PUSCH, ; By high-level parameters scaling Configuration; It is the symbol index of the first OFDM symbol after the first DMRS symbol in the PUSCH transmission and not carrying the DMRS of the PUSCH.

6. The terminal device according to claim 5, wherein the processor is further configured to: The transport block size is determined by determining the total number of resource elements (REs) allocated for the PUSCH based on the number of slots.

7. A network device comprising a processor, wherein the processor is configured to cause the network device to: downlink control information DCI transmitting an indication value corresponding to the number of time slots allocated for transport block processing for a physical uplink shared channel PUSCH; as well as receiving uplink control information on the PUSCH based on the number of time slots, The uplink control information is a hybrid automatic repeat request acknowledgement HARQ-ACK, The network device is caused to receive the HARQ-ACK on the PUSCH based on the following equation: where Z is calculated by dividing the number of time slots by Multiplying them together, we get is the number of HARQ-ACK bits; if ,but ;otherwise is the number of cyclic redundancy check (CRC) bits for HARQ-ACK; , and represents the offset value; is the number of uplink shared channel UL-SCH code blocks for PUSCH transmission; If the downlink control information DCI format for scheduling the PUSCH transmission includes a code block group transmission information CBGTI field indicating that the terminal device should not transmit the rth code block, then =0; otherwise, is the rth code block size of the UL-SCH for the PUSCH transmission; is the scheduled bandwidth of the PUSCH transmission, expressed as the number of subcarriers; It is the orthogonal frequency division multiplexing OFDM symbol carrying the phase tracking reference signal PTRS in the PUSCH transmission l The number of subcarriers in ; is the PUSCH transmission for can be used in OFDM symbols l The number of resource elements used for transmission of UCI in is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for the demodulation reference signal DMRS; For any OFDM symbol carrying the DMRS of the PUSCH, ; For any OFDM symbol that does not carry the DMRS of the PUSCH, ; By high-level parameters scaling Configuration; It is the symbol index of the first OFDM symbol after the first DMRS symbol in the PUSCH transmission and not carrying the DMRS of the PUSCH.

8. The network device according to claim 7, wherein the processor is further configured to: The transport block size is determined by determining the total number of resource elements (REs) allocated for the PUSCH based on the number of slots.

Images