CN111182634B

CN111182634B - Data transmission method, terminal and network equipment

Info

Publication number: CN111182634B
Application number: CN201811399906.XA
Authority: CN
Inventors: 鲁智; 潘学明; 沈晓冬
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2018-11-22
Filing date: 2018-11-22
Publication date: 2021-09-14
Anticipated expiration: 2038-11-22
Also published as: CN111182634A

Abstract

The invention provides a data transmission method, a terminal and network equipment, and relates to the technical field of communication. The data transmission method is applied to a terminal and comprises the following steps: when the repeated transmission of the PUSCH transmission is in a DMRS sharing mode, acquiring a time domain resource allocation mode of the repeated transmission of the PUSCH transmission, wherein the time domain resource allocation mode comprises the following steps: each transmission uses the same time domain duration or at least two transmissions use different time domain durations; and carrying out repeated transmission of PUSCH transmission according to the time domain resource allocation mode. Or, the data transmission method is applied to a network device, and includes: when the repeated transmission of the PDSCH transmission is in a DMRS sharing mode, sending a time domain resource allocation mode of the repeated transmission of the PDSCH transmission to a terminal, wherein the time domain resource allocation mode comprises the following steps: each transmission uses the same time domain duration or at least two transmissions use different time domain durations; and according to the time domain resource allocation mode, carrying out repeated transmission of PDSCH transmission.

Description

Data transmission method, terminal and network equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a data transmission method, a terminal, and a network device.

Background

Future fifth Generation (5th Generation, 5G) mobile communication systems need to accommodate more diverse scenarios and service demands than previous mobile communication systems. The main scenes of 5G include Enhanced Mobile Broadband (eMBB), Ultra-high Reliable and Low Latency Communications (URLLC), and large-scale internet of things (mtc), and these scenes have proposed requirements for the system such as high reliability, Low Latency, large bandwidth, and wide coverage. For some User Equipments (UEs), also called terminals, services with different numerical configurations (numerology) may be supported. Existing repeated transmissions can only be for the uplink and are based on slot (slot) granularity, i.e. having the same starting symbol and duration in each slot of the repetition. This is not applicable to URLLC traffic. For the URLLC service, in order to meet the requirements of low-delay and high-reliability service indexes, a Physical Uplink Shared Channel (PUSCH) or a Physical Downlink Shared Channel (PDSCH) at a symbol level or a non-slot (non-slot) or mini-slot (mini-slot) level is used for transmission, and at the same time, time-domain repeated transmission is used to increase reliability.

For repeated PUSCH transmissions at the symbol level or non-slot (or mini-slot) level, multiple transmissions within one slot need to be supported to reduce latency. Generally, the network only needs to indicate the time domain information of the first transmission, i.e. the starting symbol and the duration, and the UE can determine each of the other repeated time domain information according to the time domain information of the first transmission. When a PUSCH repetition transmission encounters a DL symbol, or a flexible (flexible) symbol is changed to a DL (or UL) symbol, or a flexible symbol is not available, the UE may defer the PUSCH transmission. When a De-Modulation Reference Signal (DMRS) is shared, how the UE performs repeated transmission of the PUSCH is not yet standardized; the same problem exists for the network device with respect to the PDSCH.

Disclosure of Invention

Embodiments of the present invention provide a data transmission method, a terminal, and a network device, so as to solve a problem that, in the case of repeated transmission, when DMRS is shared, the terminal (or the network device) cannot ensure reliability of network communication because it is not known how to perform repeated transmission of data.

In order to solve the technical problem, the invention adopts the following scheme:

in a first aspect, an embodiment of the present invention provides a data transmission method, applied to a terminal, including:

when the repeated transmission of the PUSCH transmission is a demodulation reference signal (DMRS) sharing mode, acquiring a time domain resource allocation mode of the repeated transmission of the PUSCH transmission, wherein the time domain resource allocation mode comprises the following steps: each transmission uses the same time domain duration or at least two transmissions use different time domain durations;

and performing repeated transmission of the PUSCH transmission according to the time domain resource allocation mode.

In a second aspect, an embodiment of the present invention provides a data transmission method, applied to a network device, including:

receiving repeated transmission of Physical Uplink Shared Channel (PUSCH) transmission sent by a terminal;

the repeated transmission is sent by the terminal according to a time domain resource allocation mode of repeated transmission of the PUSCH transmission when the repeated transmission of the PUSCH transmission is a demodulation reference signal (DMRS) sharing mode;

the time domain resource allocation pattern comprises: each transmission uses the same time domain duration or at least two transmissions use different time domain durations.

In a third aspect, an embodiment of the present invention provides a data transmission method applied to a network device, including:

when the repeated transmission of the physical downlink shared channel PDSCH transmission is in a demodulation reference signal (DMRS) sharing mode, sending a time domain resource allocation mode of the repeated transmission of the PDSCH transmission to a terminal, wherein the time domain resource allocation mode comprises the following steps: each transmission uses the same time domain duration or at least two transmissions use different time domain durations;

and according to the time domain resource allocation mode, carrying out repeated transmission of the PDSCH transmission.

In a fourth aspect, an embodiment of the present invention provides a data transmission method, which is applied to a terminal, and includes:

receiving a time domain resource allocation mode of repeated transmission of Physical Downlink Shared Channel (PDSCH) transmission sent by network equipment;

receiving repeated transmission of PDSCH transmission sent by the network equipment according to the time domain resource allocation mode;

wherein the time domain resource allocation pattern comprises: each transmission uses the same time domain duration or at least two transmissions use different time domain durations.

In a fifth aspect, an embodiment of the present invention provides a terminal, including:

a first obtaining module, configured to obtain a time domain resource allocation pattern of repeated transmission of a physical uplink shared channel, PUSCH, when the repeated transmission of the PUSCH transmission is a demodulation reference signal, DMRS, shared manner, where the time domain resource allocation pattern includes: each transmission uses the same time domain duration or at least two transmissions use different time domain durations;

and the first transmission module is used for carrying out repeated transmission of the PUSCH transmission according to the time domain resource allocation mode.

In a sixth aspect, an embodiment of the present invention provides a network device, including:

the terminal comprises a first receiving module, a second receiving module and a transmitting module, wherein the first receiving module is used for receiving repeated transmission of Physical Uplink Shared Channel (PUSCH) transmission sent by the terminal;

In a seventh aspect, an embodiment of the present invention provides a network device, including:

a first sending module, configured to send, to a terminal, a time domain resource allocation pattern of repeated transmission of a physical downlink shared channel PDSCH transmission when the repeated transmission of the PDSCH transmission is in a DMRS (demodulation reference signal) sharing mode, where the time domain resource allocation pattern includes: each transmission uses the same time domain duration or at least two transmissions use different time domain durations;

and a second transmission module, configured to perform repeated transmission of the PDSCH transmission according to the time domain resource allocation pattern.

In an eighth aspect, an embodiment of the present invention provides a terminal, including:

a second receiving module, configured to receive a time domain resource allocation pattern of repeated transmission of a PDSCH (physical downlink shared channel) transmission sent by a network device;

a third receiving module, configured to receive, according to the time domain resource allocation pattern, repeated transmission of PDSCH transmission sent by the network device;

In a ninth aspect, an embodiment of the present invention provides a terminal, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the data transmission method described above.

In a tenth aspect, an embodiment of the present invention provides a network device, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the data transmission method described above.

In an eleventh aspect, the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores thereon a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the data transmission method described above.

One of the beneficial effects of the invention is that corresponding repeated transmission is carried out according to the time domain resource allocation mode of repeated transmission of PUSCH transmission or PDSCH transmission in the DMRS sharing mode, so that the network communication flow is perfected, the accurate transmission of data can be ensured, and the communication reliability is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

FIG. 1 is a block diagram of a network system suitable for use in embodiments of the present invention;

fig. 2 shows a PUSCH transmission scheme without DMRS sharing;

fig. 3 is a flowchart illustrating a data transmission method applied to a terminal according to an embodiment of the present invention;

fig. 4 shows one of the transmission state diagrams in particular in the case where DMRS is shared, with the same time-domain duration for each transmission;

fig. 5 shows a second diagram of a specific transmission state in the case where DMRS is shared and each transmission uses the same time-domain duration;

fig. 6 shows one of the transmission state diagrams in particular in case of DMRS sharing, at least two transmissions with different time domain durations;

fig. 7 shows a second diagram of transmission states in particular in the case where DMRS is shared and at least two transmissions use different time-domain durations;

fig. 8 shows a third diagram of a specific transmission state in the case where DMRS is shared and at least two transmissions use different time domain durations;

fig. 9 is a flowchart illustrating a data transmission method applied to a network device according to an embodiment of the present invention;

fig. 10 shows one of the block diagrams of a terminal according to an embodiment of the present invention;

fig. 11 shows one of the configuration block diagrams of a terminal of the embodiment of the present invention;

FIG. 12 shows one of the block diagrams of a network device of an embodiment of the invention;

FIG. 13 is a block diagram of a network device according to an embodiment of the present invention;

fig. 14 is a second flowchart of a data transmission method applied to a network device according to an embodiment of the invention;

fig. 15 is a second flowchart of a data transmission method applied to a terminal according to an embodiment of the present invention;

FIG. 16 is a second block diagram of a network device according to an embodiment of the invention;

fig. 17 shows a second block diagram of the network device according to the embodiment of the invention;

fig. 18 is a second block diagram of a terminal according to the embodiment of the present invention;

fig. 19 shows a second configuration block diagram of the terminal according to the embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be implemented, for example, in a sequence other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.

In the embodiments of the present invention, words such as "exemplary" or "for example" are used to mean serving as examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

Embodiments of the present invention are described below with reference to the accompanying drawings. The data transmission method, the terminal and the network equipment provided by the embodiment of the invention can be applied to a wireless communication system. The wireless communication system may be a system adopting a 5th Generation (5G) mobile communication technology (hereinafter, referred to as a 5G system), and those skilled in the art will appreciate that the 5G NR system is only an example and is not a limitation.

Referring to fig. 1, fig. 1 is a structural diagram of a network system to which an embodiment of the present invention is applicable, and as shown in fig. 1, the network system includes a User terminal 11 and a base station 12, where the User terminal 11 may be a User Equipment (UE), for example: the terminal side Device may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), or a Wearable Device (Wearable Device), and it should be noted that the specific type of the user terminal 11 is not limited in the embodiments of the present invention. The base station 12 may be a base station of 5G and later releases (e.g., a gNB, a 5G NR NB), or a base station in other communication systems, or referred to as a node B, and it should be noted that, in the embodiment of the present invention, only the 5G base station is taken as an example, but the specific type of the base station 12 is not limited.

Before proceeding with the description of the embodiments of the present invention, some concepts mentioned below will be explained.

It should be noted that, for the repeated transmission of the PUSCH transmission, the method includes: two modes of transmission based on dynamic scheduling and transmission based on configuration authorization.

It should be noted that, based on dynamic scheduling transmission, the network device indicates the time-frequency resource of the first PUSCH transmission through Downlink Control Information (DCI), and the number of times of the repeated transmission may be indicated through Radio Resource Control (RRC) signaling configuration or DCI;

while for configuration grant transmission, the number of PUSCH transmissions may be activated by RRC signaling configuration or DCI configuration grant (i.e., DCI configuration grant functions as a usage switch).

There may be two ways for the time-frequency resource of PUSCH transmission:

based on configuration authorization transmission, the network equipment configures time-frequency resources for each repeated transmission of the terminal, and when the terminal service arrives, the terminal selects the nearest available time-frequency resources for transmission, including repeated transmission;

for dynamic scheduling transmission, the network device instructs the terminal to perform time-frequency resources for the first repeated transmission, and the subsequent repeated transmission is determined according to the time-frequency resources, the transmission times and the time slot format for the first transmission.

For example, when a terminal performs uplink transmission based on dynamic scheduling, if the base station does not instruct the terminal to use DMRS sharing. As shown in fig. 2, the terminal is instructed to transmit 4 times, which includes one initial transmission and three retransmissions. The base station may only notify the time domain resource allocation of the first transmission (it should be noted that, in general, the frequency domain resource location of each transmission is fixed, and in the first notification, the base station notifies the terminal of the time domain resource and the frequency domain resource), for example, the first transmission start location is symbol 6 and the length is 3 symbols, where the first symbol is a DMRS symbol, and the other 2 symbols are data symbols; the terminal determines the time domain position of subsequent transmission according to the position, the time slot format and the transmission times of the first transmission, the second transmission is positioned at symbols 9-11, because the symbols 12 and 13 are not enough for the time length of the first transmission, the third transmission is positioned at symbols 2-4 of a time slot n +1, and the fourth transmission is positioned at symbols 5-7 of the time slot n + 1; it should be noted here that each transmission needs to occur on consecutive available flexible symbols or uplink symbols, and multiple transmissions may occur on one slot.

In fig. 2, the slash-filled boxes indicate that the DMRS is transmitted through the symbol, and the blank boxes indicate that the data is transmitted through the symbol.

It should be noted that, for the repeated transmission of the PDSCH transmission, the specific transmission process is similar to the PUSCH transmission, and is not described herein again.

In order to solve the problem that when DMRS is repeatedly transmitted and DMRS is shared, a terminal (or a network device) cannot ensure reliability of network communication because it is not known how to repeatedly transmit data, embodiments of the present invention provide a data transmission method, a terminal, and a network device.

Specific implementation cases of PUSCH transmission and PDSCH transmission are described below.

One, PUSCH transmission

Specifically, as shown in fig. 3, fig. 3 is a schematic flowchart of a data transmission method according to an embodiment of the present invention, where the data transmission method is applied to a terminal, and includes:

301, when the repeated transmission of the physical uplink shared channel PUSCH transmission is in a demodulation reference signal (DMRS) sharing mode, acquiring a time domain resource allocation mode of the repeated transmission of the PUSCH transmission;

note that, the PUSCH transmission includes: at least one of dynamically scheduled based transmissions and configuration-based grant transmissions.

The time domain resource allocation mode may be obtained through RRC signaling or DCI signaling, and includes: each transmission uses the same time domain duration or at least two transmissions use different time domain durations; specifically, the time domain duration refers to the number of OFDM symbols occupied by time domain resources allocated for data transmission; further, the use of the same time domain duration for each transmission means that: the number of OFDM symbols occupied in the time domain for each transmission is completely the same, for example, each transmission occupies 3 OFDM symbols; the at least two transmissions using different time domain durations means: the number of OFDM symbols occupied by different transmissions in the time domain may be different, for example, 3 OFDM symbols occupied by the first transmission, 2 OFDM symbols occupied by the second transmission, 2 OFDM symbols occupied by the third transmission, and 3 OFDM symbols occupied by the fourth transmission.

Step 302, according to the time domain resource allocation mode, performing repeated transmission of the PUSCH transmission.

Specifically, before step 302, a Redundancy Version (RV) used for each transmission needs to be obtained, and when the terminal executes step 302, the terminal needs to perform repeated transmission of the PUSCH transmission according to the Redundancy Version and the time domain resource allocation pattern.

Specifically, the manner of obtaining the redundancy version used in each transmission is as follows:

acquiring a redundancy mode and a redundancy sequence;

and determining the redundancy version adopted by each transmission according to the redundancy mode and the redundancy sequence.

It should be noted that, when the PUSCH transmission is based on dynamic scheduling transmission, the redundancy mode is indicated by Radio Resource Control (RRC) signaling, the redundancy sequence is indicated by downlink control information DCI, or the redundancy mode and the redundancy sequence are indicated by DCI.

For the case where RRC signaling and DCI in combination indicate redundancy version, for example, the network device may configure a redundancy mode through RRC signaling, e.g., redundancy mode 1: {0,2,3,1}, redundancy mode 2: {0,0,0,0}, redundancy mode 3: {0,3,0,3}. Further, the network device indicates the redundancy mode to be used through RRC signaling, and the network device indicates the redundancy sequence to be used for transmission through DCI, as shown in table 1, where table 1 is the redundancy sequence to be used for transmission in redundancy mode 1.

Table 1 redundancy sequence in redundancy mode 1

The terminal can determine and obtain the redundancy version used by each transmission according to the redundancy mode and the redundancy sequence indicated by the network equipment.

It should be further noted that, when the DCI is used to indicate the redundancy mode and the redundancy sequence at the same time, as shown in table 2:

TABLE 2

In this way, the network device only needs to send the DCI once to indicate, that is, when the terminal receives the DCI, the terminal may obtain the redundancy mode and the redundancy sequence by analyzing the DCI.

It should be noted that if the number of transmissions is more or less than the redundancy version indicated by the DCI, the terminal repeats or truncates the redundancy version sequence. I.e. the terminal can determine the redundancy version to be used for each repeated transmission based on the redundancy sequence and the number of transmissions.

For example, when the DCI indicates that 000 in table 2 is used as the redundancy sequence of the repeated transmission, and when 8 times of repeated transmission are indicated, the redundancy versions used in each of the 8 transmissions are: 0. 2,3,1, 0,2,3, 1; if the transmission times is 3 times, the redundancy versions adopted each time are respectively as follows: 0. 2 and 3.

It should be further noted that, for the configuration grant transmission, the redundancy mode and the redundancy sequence are generally indicated by RRC signaling or DCI activation of the configuration grant, and specifically, the network device preferably performs the indication of the redundancy mode and the redundancy sequence in the manner shown in table 2.

It should be noted that, specific repeated transmission procedures may also be different due to different time domain resource allocation patterns, and specific procedures for performing repeated transmission of PUSCH transmission in different time domain resource allocation patterns are described below.

1. Time domain resource allocation patterns that use the same time domain duration for each transmission

It should be noted that, in this way, the specific implementation of step 302 is:

performing repeated transmission of the PUSCH transmission by adopting a second preset rule;

it should be noted that, the second preset rule includes one of the following manners:

a11, carrying out channel coding according to PUSCH transmission without DMRS, and for PUSCH transmission with DMRS, punching data in symbols occupied by the DMRS;

it should be noted that, as shown in fig. 4, four transmissions are taken as an example, where the second transmission (i.e., transmission 2) shares the DMRS of the first transmission with the first transmission (i.e., transmission 1), and the fourth transmission (i.e., transmission 4) shares the DMRS of the third transmission with the third transmission (i.e., transmission 3). Transmission 2 and transmission 4 are referred to as transmissions of the shared DMRS, and transmission 1 and transmission 3 are referred to as transmissions of the shared DMRS. The terminal performs coding on a once repeated transmission according to time domain resource allocation without DMRS (demodulation reference signal), namely, performs coding according to time domain duration with 3 symbols for transmission 2 and transmission 4, and adopts the same channel coding for data for transmission 1 and transmission 3, and because the first symbol needs to transmit the DMRS, the first symbol is punctured, and a related data part is lost (drop).

The method has the advantages that the terminal can carry out repeated transmission for many times only by carrying out channel coding once, and does not need to carry out different coding and rate matching processes; this approach requires less delay and processing complexity.

It should be noted that, for data symbol transmission by using a puncturing method, the redundancy sequence may be:

all transmissions use redundancy versions that support more self-decoding, such as

redundancy versions

0 and 3 in the redundancy order of table 1 above;

the transmission requiring puncturing uses less self-decoded redundancy versions, as shown in fig. 4, transmission 1 and transmission 3 may use

redundancy versions

2 and 1, respectively, in any one of the redundancy sequences of table 1 above, and transmission 2 and transmission 4

use versions

0 and 3 in any one of the redundancy sequences of table 1 above; alternatively, transmission 1 and transmission 3 may use

redundancy versions

0 and 3, respectively, in any of the redundancy sequences of table 1 above, and transmission 2 and transmission 4

use versions

2 and 1, respectively, in any of the redundancy sequences of table 1 above.

A12, when the repeated transmission of the PUSCH transmission adopts the same redundancy version, the PUSCH transmission of a first preset number of data symbols of the PUSCH transmission without the DMRS is the same as the data of the data symbols of the PUSCH transmission with the DMRS, and a second preset number of data symbols of the PUSCH transmission without the DMRS is used for transmitting the data of the first target number of data symbols, wherein the first target number of data symbols are the first preset number of data symbols arranged in the first preset number of data symbols in time sequence;

it should be noted that the first preset number refers to the number of data symbols in transmission including the DMRS, and the second preset number refers to the number of symbols occupied by the DMRS;

for example, as shown in fig. 5, transmission 1 and transmission 2 both occupy 3 OFDM symbols, where transmission 1 is transmission including a DMRS, transmission 2 is transmission not including a DMRS, the number of symbols transmitting data in transmission 1 is 2, and the number of symbols occupied by a DMRS is 1, that is, the first two symbols in transmission 2 are the same as the content transmitted by the last two symbols in transmission 1, and the third symbol in transmission 2 may transmit the content in the first data symbol, so as to increase redundancy and improve reliability.

A13, when the repeated transmission of the PUSCH transmission adopts different redundancy versions, the transmission of the third preset number of data symbols of the PUSCH transmission without the DMRS is the same as the data of the data symbols of the PUSCH transmission with the DMRS, the fourth preset number of data symbols of the PUSCH transmission without the DMRS transmits the data of the second target number of data symbols, and the second target number of data symbols is the fourth preset number of data symbols which are arranged before in time sequence in the third preset number of data symbols of the PUSCH transmission at this time.

It should be noted that the third preset number refers to the number of data symbols in transmission including the DMRS, and the fourth preset number refers to the number of symbols occupied by the DMRS;

for example, continuing as shown in fig. 5, transmission 1 and transmission 2 both occupy 3 OFDM symbols, where transmission 1 is a transmission containing a DMRS, transmission 2 is a transmission not containing a DMRS, the number of symbols transmitting data in transmission 1 is 2, and the number of symbols occupied by the DMRS is 1, that is, the first two symbols in transmission 2 are the same as the content transmitted by the last two symbols in transmission 1, and the content of the third symbol in transmission 2 is the same as the content of the first data symbol in transmission 2.

2. Time domain resource allocation patterns employing different time domain durations for at least two transmissions

step S3021, acquiring a DMRS transmission mode;

it should be noted that the DMRS transmission mode refers to whether each transmission carries a DMRS, and the DMRS transmission mode may be acquired through RRC signaling or DCI signaling.

Step S3022, according to the DMRS transmission mode, performing repeated transmission of the PUSCH transmission according to a first preset rule;

it should be noted that, the first preset rule includes:

the number of data symbols per PUSCH transmission is the same, and the same channel coding is used for the data symbols for PUSCH transmission with DMRS and PUSCH transmission without DMRS.

Specifically, based on dynamically scheduled transmission, and at least two transmissions adopt different time domain durations, the network device needs to indicate the terminal DMRS transmission pattern, e.g., for 4 transmissions, the network device indicates that the DMRS transmission pattern is 1011, where 1 indicates transmission with DMRS (i.e., the transmission occupies 3 OFDM symbols), 0 indicates transmission without DMRS (i.e., the transmission occupies 2 OFDM symbols, and the transmission shares DMRS with other transmissions), and a specific transmission state at the terminal side is as shown in fig. 6, where transmission 2 and transmission 1 share DMRS of transmission 1; for example, when the network device indicates that the DMRS transmission mode is 1001, the specific transmission state at the terminal side is as shown in fig. 7, where transmission 1, transmission 2, and transmission 3 share the DMRS of transmission 1; for example, the network device indicates a DMRS transmission pattern 1010, and a specific transmission state at the terminal side is as shown in fig. 8, where transmission 2 and transmission 1 share the DMRS of transmission 1, and where transmission 4 and transmission 3 share the DMRS of transmission 3.

In fig. 6 to 8, for example, data occupies two OFDM symbols, and DMRS occupies one OFDM symbol, where a slash filling box indicates that DMRS is transmitted in the symbol, and a blank box indicates that data is transmitted in the symbol.

It should be further noted that, for configuring the grant transmission, the time-frequency resource of each transmission is determined according to the following principle:

continuous PUSCH transmissions must share DMRS, which cannot cross slot boundaries; discontinuous transmission does not share DMRS; in addition, it is necessary to ensure that the delay of the repeated transmission is minimized.

Further, the network device may configure a maximum number of transmissions of the shared DMRS.

It should be noted that, in the embodiment of the present invention, in the DMRS sharing manner, the time domain resource allocation pattern of the repeated transmission of the PUSCH is obtained first, and then the corresponding repeated transmission of the PUSCH is performed according to the time domain resource allocation pattern, so that the network communication flow is improved, accurate transmission of data can be ensured, and the communication reliability is improved.

As shown in fig. 9, an embodiment of the present invention further provides a data transmission method applied to a network device, including:

step 901, receiving repeated transmission of Physical Uplink Shared Channel (PUSCH) transmission sent by a terminal;

It should be noted that how the terminal side transmits, the network device side also receives in the same manner, that is, the terminal and the network device have the same understanding of the transmitted data.

It should be noted that all the descriptions regarding the network device in the above embodiments are applicable to the embodiment of the data transmission method, and the same technical effects can be achieved.

As shown in fig. 10, an embodiment of the present invention further provides a terminal 1000, including:

a first obtaining module 1001, configured to obtain a time domain resource allocation pattern of repeated transmission of a physical uplink shared channel, PUSCH, when the repeated transmission of the PUSCH transmission is a demodulation reference signal, DMRS, shared manner, where the time domain resource allocation pattern includes: each transmission uses the same time domain duration or at least two transmissions use different time domain durations;

a first transmission module 1002, configured to perform repeated transmission of the PUSCH transmission according to the time domain resource allocation pattern.

Specifically, the PUSCH transmission includes: at least one of dynamically scheduled based transmissions and configuration-based grant transmissions.

Optionally, before the first transmitting module 1002 performs the repeated transmission of the PUSCH transmission according to the time domain resource allocation pattern, the terminal further includes:

the second acquisition module is used for acquiring the redundancy version adopted by each transmission;

the first transmission module 1002 is configured to:

and performing repeated transmission of the PUSCH transmission according to the redundancy version and the time domain resource allocation mode.

Further, the second obtaining module includes:

a first acquisition unit configured to acquire a redundancy pattern and a redundancy order;

and the determining unit is used for determining the redundancy version adopted by each transmission according to the redundancy mode and the redundancy sequence.

Optionally, the time domain resource allocation pattern adopts different time domain durations for at least two transmissions, and the first transmitting module 1002 includes:

a second obtaining unit, configured to obtain a DMRS transmission mode;

a first transmission unit, configured to perform repeated transmission of the PUSCH transmission according to a first preset rule according to the DMRS transmission mode;

wherein the first preset rule includes:

Optionally, the time domain resource allocation pattern adopts the same time domain duration for each transmission, and the first transmitting module 1002 is configured to:

wherein the second preset rule includes one of the following modes:

performing channel coding according to PUSCH transmission without the DMRS, and punching data in symbols occupied by the DMRS for the PUSCH transmission with the DMRS;

when the repeated transmission of the PUSCH transmission adopts the same redundancy version, the PUSCH transmission of a first preset number of data symbols of the PUSCH transmission without the DMRS is the same as the data of the data symbols of the PUSCH transmission with the DMRS, and a second preset number of data symbols of the PUSCH transmission without the DMRS is used for transmitting data of a first target number of data symbols, wherein the first target number of data symbols are the first second preset number of data symbols which are arranged in the first preset number of data symbols in time sequence;

when the repeated transmission of the PUSCH transmission adopts different redundancy versions, the transmission of a third preset number of data symbols of the PUSCH transmission without the DMRS is the same as the data of the data symbols of the PUSCH transmission with the DMRS, and a fourth preset number of data symbols of the PUSCH transmission without the DMRS transmits data of a second target number of data symbols, wherein the data symbols of the second target number are the data symbols of the fourth preset number which are arranged in front of the data symbols of the third preset number in time sequence in the PUSCH transmission at this time.

Specifically, when the PUSCH transmission is based on dynamic scheduling transmission, the redundancy mode is indicated by radio resource control RRC signaling, the redundancy order is indicated by downlink control information DCI, or the redundancy mode and the redundancy order are indicated by DCI;

when the PUSCH transmission is a configuration grant based transmission, the redundancy mode and the redundancy order are indicated by RRC signaling or activated by DCI of a configuration grant.

It should be noted that the terminal embodiment is a terminal corresponding to the data transmission method applied to the terminal side, and all implementations of the above embodiments are applicable to the terminal embodiment, and can achieve the same technical effects.

Fig. 11 is a schematic diagram of a hardware structure of a terminal for implementing an embodiment of the present invention.

The terminal 110 includes but is not limited to: radio frequency unit 1110, network module 1120, audio output unit 1130, input unit 1140, sensor 1150, display unit 1160, user input unit 1170, interface unit 1180, memory 1190, processor 1111, and power supply 1112. Those skilled in the art will appreciate that the terminal structure shown in fig. 11 does not constitute a limitation of the terminal, and that the terminal may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

The processor 1111 is configured to, when the repeated transmission of the PUSCH transmission on the physical uplink shared channel is in the DMRS sharing manner, obtain a time domain resource allocation pattern of the repeated transmission of the PUSCH transmission, where the time domain resource allocation pattern includes: each transmission uses the same time domain duration or at least two transmissions use different time domain durations; and performing repeated transmission of the PUSCH transmission according to the time domain resource allocation mode.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 1110 may be configured to receive and transmit signals during a message transmission or a call, and specifically, receive downlink data from a network device and then process the received downlink data to the processor 1111; in addition, the uplink data is sent to the network device. Generally, the radio frequency unit 1110 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 1110 may also communicate with a network and other devices through a wireless communication system.

The terminal provides wireless broadband internet access to the user through the network module 1120, such as helping the user send and receive e-mails, browse web pages, and access streaming media.

The audio output unit 1130 may convert audio data received by the radio frequency unit 1110 or the network module 1120 or stored in the memory 1190 into an audio signal and output as sound. Also, the audio output unit 1130 may also provide audio output related to a specific function performed by the terminal 110 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 1130 includes a speaker, a buzzer, a receiver, and the like.

The input unit 1140 is used to receive an audio or video signal. The input Unit 1140 may include a Graphic Processing Unit (GPU) 1141 and a microphone 1142, and the graphic processor 1141 processes image data of a still picture or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frame may be displayed on the display unit 1160. The image frames processed by the graphic processor 1141 may be stored in the memory 1190 (or other storage medium) or transmitted via the radio frequency unit 1110 or the network module 1120. The microphone 1142 may receive sound and may be capable of processing such sound into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication network device via the radio frequency unit 1110 in case of the phone call mode.

The terminal 110 also includes at least one sensor 1150, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that adjusts the brightness of the display panel 1161 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 1161 and/or backlight when the terminal 110 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensors 1150 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.

The display unit 1160 is used to display information input by a user or information provided to a user. The Display unit 1160 may include a Display panel 1161, and the Display panel 1161 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 1170 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 1170 includes a touch panel 1171 and other input devices 1172. Touch panel 1171, also referred to as a touch screen, may collect touch operations by a user on or near it (e.g., user operations on or near touch panel 1171 using a finger, stylus, or any suitable object or accessory). Touch panel 1171 can include two portions, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, and sends the touch point coordinates to the processor 1111 to receive and execute commands sent from the processor 1111. In addition, the touch panel 1171 can be implemented by various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1171, the user input unit 1170 may also include other input devices 1172. Specifically, the other input devices 1172 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a track ball, a mouse, and a joystick, which are not described herein.

Further, touch panel 1171 can be overlaid on display panel 1161, and when touch panel 1171 detects a touch operation thereon or nearby, the touch operation can be transmitted to processor 1111 for determining the type of touch event, and then processor 1111 can provide a corresponding visual output on display panel 1161 according to the type of touch event. Although in fig. 11, the touch panel 1171 and the display panel 1161 are two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 1171 and the display panel 1161 may be integrated to implement the input and output functions of the terminal, and the implementation is not limited herein.

The interface unit 1180 is an interface for connecting an external device to the terminal 110. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 1180 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 110 or may be used to transmit data between the terminal 110 and the external device.

Memory 1190 may be used to store software programs as well as various data. The memory 1190 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 1190 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 1111 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 1190 and calling data stored in the memory 1190, thereby integrally monitoring the terminal. Processor 1111 may include one or more processing units; preferably, the processor 1111 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 1111.

The terminal 110 may further include a power supply 1112 (e.g., a battery) for powering the various components, and preferably, the power supply 1112 may be logically coupled to the processor 1111 via a power management system to enable management of charging, discharging, and power consumption via the power management system.

In addition, the terminal 110 includes some functional modules that are not shown, and are not described in detail herein.

Preferably, an embodiment of the present invention further provides a terminal, including a processor 1111, a memory 1190, and a computer program stored in the memory 1190 and capable of running on the processor 1111, where the computer program, when executed by the processor 1111, implements each process of the embodiment of the data transmission method applied to the terminal side, and can achieve the same technical effect, and therefore, in order to avoid repetition, no further description is provided herein.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the data transmission method embodiment applied to the terminal side, and can achieve the same technical effect, and in order to avoid repetition, the detailed description is omitted here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

As shown in fig. 12, an embodiment of the present invention further provides a network device 1200, including:

a first receiving module 1201, configured to receive a repeated transmission of a physical uplink shared channel PUSCH transmission sent by a terminal;

It should be noted that, the network device embodiment is a network device corresponding to the data transmission method applied to the network device side, and all implementation manners of the foregoing embodiments are applicable to the network device embodiment, and the same technical effects as those of the foregoing embodiments can also be achieved.

Fig. 13 is a structural diagram of a network device according to an embodiment of the present invention, which can implement details of the data transmission method applied to the network device side and achieve the same effect. As shown in fig. 13, the network device 1300 includes: a processor 1301, a transceiver 1302, a memory 1303 and a bus interface, wherein:

the processor 1301 is configured to read the program in the memory 1303, and execute the following processes:

receiving, by the transceiver 1302, a repeated transmission of a physical uplink shared channel, PUSCH, transmission sent by a terminal;

In fig. 13, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 1301 and various circuits of memory represented by memory 1303 linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1302 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

The processor 1301 is responsible for managing a bus architecture and general processing, and the memory 1303 may store data used by the processor 1301 in performing operations.

An embodiment of the present invention further provides a network device, including: the data transmission method applied to the network device side comprises a memory, a processor and a computer program which is stored in the memory and can run on the processor, wherein when the computer program is executed by the processor, each process in the data transmission method embodiment applied to the network device side is realized, the same technical effect can be achieved, and in order to avoid repetition, the details are not repeated.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process in the data transmission method embodiment applied to the network device side, and can achieve the same technical effect, and is not described herein again to avoid repetition. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

Two, PDSCH transmission

As shown in fig. 14, an embodiment of the present invention provides a data transmission method applied to a network device, including:

1401, when the repeated transmission of the physical downlink shared channel PDSCH transmission is in a demodulation reference signal DMRS sharing mode, sending a time domain resource allocation mode of the repeated transmission of the PDSCH transmission to a terminal;

it should be noted that the PDSCH transmission includes: at least one of dynamically scheduled based transmissions and configuration-based grant transmissions.

The time domain resource allocation pattern comprises: each transmission uses the same time domain duration or at least two transmissions use different time domain durations; specifically, the time domain duration refers to the number of OFDM symbols occupied by time domain resources allocated for data transmission; further, the use of the same time domain duration for each transmission means that: the number of OFDM symbols occupied in the time domain for each transmission is completely the same, for example, each transmission occupies 3 OFDM symbols; the at least two transmissions using different time domain durations means: the number of OFDM symbols occupied by different transmissions in the time domain may be different, for example, 3 OFDM symbols occupied by the first transmission, 2 OFDM symbols occupied by the second transmission, 2 OFDM symbols occupied by the third transmission, and 3 OFDM symbols occupied by the fourth transmission.

It should be further noted that the time domain resource allocation pattern may be sent to the terminal through RRC signaling or DCI signaling.

Step 1402, according to the time domain resource allocation pattern, performing repeated transmission of the PDSCH transmission.

Before step 1402, the data transmission method further includes:

determining a redundancy version adopted by each transmission according to a redundancy mode and a redundancy sequence;

further, the step 1402 is implemented to include: and according to the redundancy version and the time domain resource allocation mode, carrying out repeated transmission of the PDSCH transmission.

Further, in order to ensure that the terminal side can smoothly receive the repeated transmission, the network device needs to send a redundancy pattern and a redundancy sequence to the terminal.

Specifically, when the network device notifies the terminal of the redundancy mode and the redundancy sequence, the adopted manner is the same as the notification manner of the redundancy mode and the redundancy sequence in the PUSCH transmission, and details are not repeated again.

It should be noted that, specific repeated transmission processes may also be different due to different time domain resource allocation patterns, and specific processes for performing repeated transmission of the PDSCH transmission in different time domain resource allocation patterns are described below.

It should be noted that, in this way, the specific implementation of step 1402 is:

performing repeated transmission of the PDSCH transmission by adopting a fourth preset rule;

it should be noted that, the fourth preset rule includes one of the following modes:

b11, carrying out channel coding according to the PDSCH transmission without the DMRS, and punching data in symbols occupied by the DMRS for the PDSCH transmission with the DMRS;

it should be noted that this method is the same as the corresponding method in the PUSCH transmission, and is not described herein again.

B12, when the repeated transmission of the PDSCH transmission adopts the same redundancy version, the transmission of the fifth preset number of data symbols without DMRS transmission is the same as the data of the data symbols with DMRS transmission, and the sixth preset number of data symbols without DMRS transmission transmits the data of the third target number of data symbols, where the third target number of data symbols is the sixth preset number of data symbols that are chronologically before in the fifth preset number of data symbols;

it should be noted that the fifth preset number refers to the number of data symbols in transmission including the DMRS, and the sixth preset number refers to the number of symbols occupied by the DMRS; for example, as shown in fig. 5, transmission 1 and transmission 2 both occupy 3 OFDM symbols, where transmission 1 is transmission including a DMRS, transmission 2 is transmission not including a DMRS, the number of symbols transmitting data in transmission 1 is 2, the number of symbols occupied by a DMRS is 1, that is, the first two symbols in transmission 2 are the same as the content transmitted by the last two symbols in transmission 1, and the third symbol in transmission 2 transmits the content in the first data symbol.

B13, when the repeated transmission of the PDSCH transmission adopts different redundancy versions, the PDSCH transmission of the seventh preset number of data symbols transmitted by the PDSCH without DMRS is the same as the data symbols transmitted by the PDSCH with DMRS, the eighth preset number of data symbols transmitted by the PDSCH without DMRS transmits data of the fourth target number of data symbols, and the fourth target number of data symbols is the eighth preset number of data symbols which are arranged before in time sequence in the seventh preset number of data symbols transmitted this time.

It should be noted that the seventh preset number refers to the number of data symbols in transmission including the DMRS, and the eighth preset number refers to the number of symbols occupied by the DMRS;

according to the DMRS transmission mode and a third preset rule, carrying out repeated transmission of the PDSCH transmission;

it should be noted that the DMRS transmission pattern refers to whether each transmission carries a DMRS, and the DMRS transmission pattern is obtained by a higher layer of a network device.

It should be noted that, the third preset rule includes:

the number of data symbols transmitted per PDSCH is the same, and the same channel coding is used for data symbols transmitted by PDSCH with DMRS and by PDSCH without DMRS.

Specifically, the network device obtains a DMRS transmission pattern of a higher layer, for example, for 4 transmissions, the network device indicates that the DMRS transmission pattern is 1011, where 1 indicates a transmission with a DMRS (i.e., the transmission occupies 3 OFDM symbols), 0 indicates a transmission without a DMRS (i.e., the transmission occupies 2 OFDM symbols and shares a DMRS with other transmissions), and a specific transmission state on the network device side is as shown in fig. 6, where transmission 2 and transmission 1 share a DMRS of transmission 1; for example, when the network device indicates that the DMRS transmission mode is 1001, a specific transmission state on the network device side is as shown in fig. 7, where transmission 1, transmission 2, and transmission 3 share the DMRS of transmission 1; for example, the network device indicates a DMRS transmission pattern 1010, and a specific transmission state on the network device side is as shown in fig. 8, where transmission 2 and transmission 1 share the DMRS of transmission 1, and where transmission 4 and transmission 3 share the DMRS of transmission 3.

It should be further noted that, in order to ensure that the terminal can accurately receive the repeated transmission of the PDSCH transmission, the network device further needs to send a DMRS transmission pattern to the terminal to assist the terminal in accurately receiving the PDSCH transmission, where the DMRS transmission pattern may be sent to the terminal through RRC signaling or DCI signaling.

It should be noted that, in the embodiments of the present invention, in the DMRS sharing manner, the time domain resource allocation pattern of the PDSCH transmission is used to perform the repeated transmission of the corresponding PDSCH, so as to improve the network communication process, ensure the accurate transmission of data, and improve the communication reliability.

As shown in fig. 15, an embodiment of the present invention further provides a data transmission method, which is applied to a terminal, and includes:

step 1501, receiving a time domain resource allocation mode of repeated transmission of Physical Downlink Shared Channel (PDSCH) transmission sent by a network device;

step 1502, receiving a repeated transmission of a PDSCH transmission sent by a network device according to the time domain resource allocation pattern;

it should be noted that the time domain resource allocation pattern includes: each transmission uses the same time domain duration or at least two transmissions use different time domain durations.

It should be noted that how the network device side transmits, the terminal side also receives in the same manner, that is, the terminal and the network device have the same understanding of the transmitted data.

Further, the data transmission method further includes:

receiving a redundancy mode and a redundancy sequence sent by network equipment;

determining a redundancy version adopted by each transmission according to the redundancy mode and the redundancy sequence;

further, the implementation manner of the step 1502 is as follows:

and receiving the repeated transmission of the PDSCH transmission sent by the network equipment according to the redundancy version and the time domain resource allocation mode.

Further, when the time domain resource allocation pattern adopts different time domain durations for at least two transmissions, the terminal side needs to receive a DMRS transmission pattern sent by the network device;

further, the specific implementation manner of step 1502 is:

and receiving the repeated transmission of the PDSCH transmission sent by the network equipment according to the DMRS transmission mode.

It should be noted that all the descriptions regarding the terminal in the above embodiments are applicable to the embodiment of the data transmission method, and the same technical effects can be achieved.

As shown in fig. 16, an embodiment of the present invention further provides a network device 1600, including:

a first sending module 1601, configured to send, to a terminal, a time domain resource allocation pattern of repeated transmission of a physical downlink shared channel PDSCH transmission when the repeated transmission of the PDSCH transmission is in a DMRS (demodulation reference signal) sharing manner, where the time domain resource allocation pattern includes: each transmission uses the same time domain duration or at least two transmissions use different time domain durations;

a second transmission module 1602, configured to perform repeated transmission of the PDSCH transmission according to the time domain resource allocation pattern.

Specifically, the PDSCH transmission comprises: at least one of dynamically scheduled based transmissions and configuration-based grant transmissions.

Further, before the second transmitting module 1602 performs the repeated transmission of the PDSCH transmission according to the time domain resource allocation pattern, the method further includes:

the first determining module is used for determining the redundancy version adopted by each transmission according to the redundancy mode and the redundancy sequence;

the second transmission module 1602 is configured to:

and according to the redundancy version and the time domain resource allocation mode, carrying out repeated transmission of the PDSCH transmission.

Optionally, the network device further includes:

and the second sending module is used for sending the redundancy mode and the redundancy sequence to the terminal.

Optionally, the time domain resource allocation pattern adopts different time domain durations for at least two transmissions, and the second transmitting module 1602 is configured to:

wherein the third preset rule includes:

Further, the network device further includes:

and the third sending module is used for sending the DMRS transmission mode to the terminal.

Optionally, the time domain resource allocation pattern adopts the same time domain duration for each transmission, and the second transmitting module 1602 is configured to:

wherein the fourth preset rule includes one of the following modes:

performing channel coding according to PDSCH transmission without DMRS, and punching data in symbols occupied by the DMRS for PDSCH transmission with the DMRS;

when the repeated transmission of the PDSCH transmission adopts the same redundancy version, the transmission of a fifth preset number of data symbols without DMRS transmission is the same as the data of the data symbols with DMRS transmission, and the data of a third target number of data symbols is transmitted by a sixth preset number of data symbols without DMRS transmission, where the third target number of data symbols is the sixth preset number of data symbols that are arranged before in time sequence among the fifth preset number of data symbols;

when the repeated transmission of the PDSCH transmission adopts different redundancy versions, the PDSCH transmission of a seventh preset number of data symbols transmitted by the PDSCH without the DMRS is the same as the data symbols transmitted by the PDSCH with the DMRS, the eighth preset number of data symbols transmitted by the PDSCH without the DMRS transmit data of a fourth target number of data symbols, and the fourth target number of data symbols are the eighth preset number of data symbols which are arranged in the front of the seventh preset number of data symbols transmitted this time according to the time sequence.

Fig. 17 is a structural diagram of a network device according to an embodiment of the present invention, which can implement the details of the data transmission method applied to the network device side and achieve the same effect. As shown in fig. 17, the network device 1700 includes: a processor 1701, a transceiver 1702, a memory 1703, and a bus interface, wherein:

the processor 1701 is configured to read a program in the memory 1703 and execute the following processes:

when the repeated transmission of the PDSCH transmission of the physical downlink shared channel is in the DMRS sharing mode, sending a time-domain resource allocation pattern of the repeated transmission of the PDSCH transmission to the terminal through the transceiver 1702, where the time-domain resource allocation pattern includes: each transmission uses the same time domain duration or at least two transmissions use different time domain durations; repeating the transmission of the PDSCH transmission by the transceiver 1702 in accordance with the time domain resource allocation pattern.

In fig. 17, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by the processor 1701, and various circuits, represented by the memory 1703, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1702 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

The processor 1701 is responsible for managing a bus architecture and general processing, and the memory 1703 may store data used by the processor 1701 in performing operations.

Alternatively, the processor 1701 is configured to read a program in the memory 1703 and execute:

the redundancy pattern and the redundancy sequence are transmitted to the terminal via the transceiver 1702.

Optionally, the time domain resource allocation pattern adopts different time domain durations for at least two transmissions, and the processor 1701 is configured to read a program in the memory 1703 and execute:

wherein the third preset rule includes:

transmitting the DMRS transmission pattern to a terminal through the transceiver 1702.

Optionally, the time domain resource allocation pattern uses the same time domain duration for each transmission, and the processor 1701 is configured to read a program in the memory 1703 and execute:

wherein the fourth preset rule includes one of the following modes:

As shown in fig. 18, an embodiment of the present invention further provides a terminal 1800, including:

a second receiving module 1801, configured to receive a time domain resource allocation pattern of repeated transmission of a PDSCH transmission of a physical downlink shared channel sent by a network device;

a third receiving module 1802, configured to receive, according to the time domain resource allocation pattern, repeated transmission of PDSCH transmission sent by the network device;

Optionally, before the third receiving module 1802 receives the repeated transmission of the PDSCH transmission sent by the network device according to the time domain resource allocation pattern, the method further includes:

the fourth receiving module is used for receiving the redundancy mode and the redundancy sequence sent by the network equipment;

a second determining module, configured to determine, according to the redundancy pattern and the redundancy sequence, a redundancy version used for each transmission;

the third receiving module 1802 is configured to:

Optionally, the time domain resource allocation mode adopts different time domain durations for at least two transmissions, and before the third receiving module 1802 receives the repeated transmission of the PDSCH transmission sent by the network device according to the redundancy version and the time domain resource allocation mode, the method further includes:

a fifth receiving module, configured to receive a DMRS transmission pattern sent by a network device;

further, the third receiving module 1802 is configured to:

Fig. 19 is a schematic diagram of a hardware structure of a terminal for implementing an embodiment of the present invention.

The terminal 190 includes but is not limited to: radio frequency unit 1910, network module 1920, audio output unit 1930, input unit 1940, sensor 1950, display unit 1960, user input unit 1970, interface unit 1980, memory 1990, processor 1911, and power supply 1912. Those skilled in the art will appreciate that the terminal configuration shown in fig. 19 is not intended to be limiting, and that the terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

The radio frequency unit 1910 is configured to receive a time domain resource allocation pattern of repeated transmission of a physical downlink shared channel PDSCH transmission sent by a network device;

It should be understood that, in the embodiment of the present invention, the radio frequency unit 1910 may be configured to receive and transmit signals during a message transmission or a call, and specifically, receive downlink data from a network device and then process the received downlink data in the processor 1911; in addition, the uplink data is sent to the network device. In general, radio frequency unit 1910 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 1910 may also communicate with a network and other devices through a wireless communication system.

The terminal provides the user with wireless broadband internet access via the network module 1920, such as helping the user send and receive e-mails, browse web pages, and access streaming media.

The audio output unit 1930 may convert audio data received by the radio frequency unit 1910 or the network module 1920 or stored in the memory 1990 into an audio signal and output as sound. Also, the audio output unit 1930 may also provide audio output related to a specific function performed by the terminal 190 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 1930 includes a speaker, a buzzer, a receiver, and the like.

The input unit 1940 is used to receive an audio or video signal. The input Unit 1940 may include a Graphics Processing Unit (GPU) 1941 and a microphone 1942, and the Graphics processor 1941 processes image data of still pictures or video obtained by an image capturing apparatus (such as a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 1960. The image frames processed by the graphic processor 1941 may be stored in the memory 1990 (or other storage medium) or transmitted via the radio frequency unit 1910 or the network module 1920. The microphone 1942 may receive sound, and can process such sound into audio data. The processed audio data may be converted into a format output transmittable to the mobile communication network device via the radio frequency unit 1910 in case of the phone call mode.

The terminal 190 also includes at least one sensor 1950, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that may adjust the brightness of the display panel 1961 according to the brightness of ambient light, and a proximity sensor that may turn off the display panel 1961 and/or a backlight when the terminal 190 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensors 1950 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.

The display unit 1960 serves to display information input by a user or information provided to the user. The Display unit 1960 may include a Display panel 1961, and the Display panel 1961 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 1970 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 1970 includes a touch panel 1971 and other input devices 1972. Touch panel 1971, also referred to as a touch screen, may collect touch operations by a user on or near the touch panel 1971 (e.g., operations by a user on or near touch panel 1971 using a finger, stylus, or any other suitable object or attachment). The touch panel 1971 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 1919, and receives and executes commands sent from the processor 1911. In addition, the touch panel 1971 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The user input unit 1970 may include other input devices 1972 in addition to the touch panel 1971. In particular, other input devices 1972 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

Further, the touch panel 1971 may be overlaid on the display panel 1961, and when the touch panel 1971 detects a touch operation on or near the touch panel 1971, the touch panel may be transmitted to the processor 1911 to determine the type of the touch event, and then the processor 1911 may provide a corresponding visual output on the display panel 1961 according to the type of the touch event. Although the touch panel 1971 and the display panel 1961 are shown in fig. 19 as two separate components to implement the input and output functions of the terminal, in some embodiments, the touch panel 1971 and the display panel 1961 may be integrated to implement the input and output functions of the terminal, and is not limited herein.

The interface unit 1980 is an interface for connecting an external device to the terminal 190. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 1980 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the terminal 190 or may be used to transmit data between the terminal 190 and external devices.

The memory 1990 may be used to store software programs as well as various data. The memory 1990 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. In addition, the memory 1990 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 1911 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 1990 and calling data stored in the memory 1990, thereby integrally monitoring the terminal. The processor 1911 may include one or more processing units; preferably, the processor 1911 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It is to be appreciated that the modem processor described above may not be integrated into the processor 1911.

The terminal 190 may also include a power supply 1912 (e.g., a battery) to provide power to the various components, and preferably, the power supply 1912 may be logically coupled to the processor 1911 via a power management system to manage charging, discharging, and power consumption via the power management system.

In addition, the terminal 190 includes some functional modules that are not shown, and are not described in detail herein.

Preferably, the embodiment of the present invention further provides a terminal, including a processor 1911, a memory 1990, and a computer program stored in the memory 1990 and operable on the processor 1911, where the computer program, when executed by the processor 1911, implements each process of the embodiment of the data transmission method applied to the terminal side, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.

It should be noted that the network device in the embodiment of the present invention may be a Base Transceiver Station (BTS) in Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA), a Base Station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved Node B (evolved Node B, eNB, or eNodeB) in LTE, a relay Station, an Access point, or a Base Station in a future 5G network, and the like, which is not limited herein.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims.

Claims

1. A data transmission method is applied to a terminal, and is characterized by comprising the following steps:

performing repeated transmission of the PUSCH transmission according to the time domain resource allocation mode;

wherein the performing the repeated transmission of the PUSCH transmission according to the time domain resource allocation pattern comprises:

performing repeated transmission of the PUSCH transmission according to a redundancy version and the time domain resource allocation mode;

the time domain resource allocation pattern adopts different time domain durations for at least two transmissions, and the repeated transmission of the PUSCH transmission according to the redundancy version and the time domain resource allocation pattern includes:

acquiring a DMRS transmission mode;

according to the DMRS transmission mode and a first preset rule, carrying out repeated transmission of the PUSCH transmission;

wherein the first preset rule includes:

the number of data symbols transmitted by the PUSCH at each time is the same, and the same channel coding is adopted for the data symbols transmitted by the PUSCH with the DMRS and the data symbols transmitted by the PUSCH without the DMRS;

wherein the DMRS transmission pattern is used to indicate whether a transmission carries a DMRS;

or

The time domain resource allocation pattern employs the same time domain duration for each transmission, and the repeated transmission of the PUSCH transmission according to the redundancy version and the time domain resource allocation pattern includes:

wherein the second preset rule includes one of the following modes:

2. The data transmission method of claim 1, wherein the PUSCH transmission comprises: at least one of dynamically scheduled based transmissions and configuration-based grant transmissions.

3. The data transmission method according to claim 1, further comprising, before the repeatedly transmitting the PUSCH transmission according to the time-domain resource allocation pattern:

the redundancy version employed for each transmission is obtained.

4. The data transmission method according to claim 3, wherein the obtaining the redundancy version used for each transmission comprises:

acquiring a redundancy mode and a redundancy sequence;

5. The data transmission method according to claim 4, wherein when the PUSCH transmission is a dynamic scheduling based transmission, the redundancy mode is indicated by Radio Resource Control (RRC) signaling, the redundancy order is indicated by Downlink Control Information (DCI), or the redundancy mode and the redundancy order are indicated by DCI;

6. A data transmission method is applied to network equipment and is characterized by comprising the following steps:

the time domain resource allocation pattern comprises: each transmission uses the same time domain duration or at least two transmissions use different time domain durations;

the repeated transmission is sent by the terminal according to a redundancy version and a time domain resource allocation mode of the repeated transmission of the PUSCH transmission;

the time domain resource allocation mode adopts different time domain durations for at least two transmissions, and the terminal sends the repeated transmission according to the redundancy version and the time domain resource allocation mode of the repeated transmission of the PUSCH transmission in the following way:

acquiring a DMRS transmission mode;

wherein the first preset rule includes:

or

The time domain resource allocation mode adopts the same time domain duration for each transmission, and the terminal sends the repeated transmission according to the redundancy version and the time domain resource allocation mode of the repeated transmission of the PUSCH transmission in the following way:

wherein the second preset rule includes one of the following modes:

7. A data transmission method is applied to network equipment and is characterized by comprising the following steps:

according to the time domain resource allocation mode, carrying out repeated transmission of the PDSCH transmission;

wherein the performing the repeated transmission of the PDSCH transmission according to the time domain resource allocation pattern comprises:

performing repeated transmission of the PDSCH transmission according to the redundancy version and the time domain resource allocation mode;

the time domain resource allocation pattern adopts different time domain durations for at least two transmissions, and the repeated transmission of the PDSCH transmission according to the redundancy version and the time domain resource allocation pattern includes:

wherein the third preset rule includes:

the number of data symbols transmitted by the PDSCH at each time is the same, and the same channel coding is adopted for the data symbols transmitted by the PDSCH with the DMRS and the data symbols transmitted by the PDSCH without the DMRS;

or

The time domain resource allocation pattern employs the same time domain duration for each transmission, and the repeated transmission of the PDSCH transmission according to the redundancy version and the time domain resource allocation pattern includes:

wherein the fourth preset rule includes one of the following modes:

8. The data transmission method of claim 7, wherein the PDSCH transmission comprises: at least one of dynamically scheduled based transmissions and configuration-based grant transmissions.

9. The data transmission method according to claim 7, wherein before the step of performing the repeated transmission of the PDSCH transmission according to the time domain resource allocation pattern, further comprising:

10. The data transmission method according to claim 9, wherein before the performing the repeated transmission of the PDSCH transmission according to the redundancy version and the time domain resource allocation pattern, further comprising:

and sending the redundancy mode and the redundancy sequence to the terminal.

11. The data transmission method according to claim 7, wherein before the repeatedly transmitting the PDSCH transmission according to the DMRS transmission pattern and according to a third preset rule, the method further comprises:

and sending the DMRS transmission mode to a terminal.

12. A data transmission method is applied to a terminal, and is characterized by comprising the following steps:

wherein the time domain resource allocation pattern comprises: each transmission uses the same time domain duration or at least two transmissions use different time domain durations;

wherein, the receiving the repeated transmission of the PDSCH transmission sent by the network device according to the time domain resource allocation pattern includes:

receiving the repeated transmission of the PDSCH transmission sent by the network equipment according to the redundancy version and the time domain resource allocation mode;

the time domain resource allocation mode adopts different time domain durations for at least two transmissions, and the receiving of the repeated transmission of the PDSCH transmission sent by the network device according to the redundancy version and the time domain resource allocation mode includes:

receiving repeated transmission of PDSCH transmission sent by the network equipment according to the DMRS transmission mode and a third preset rule;

wherein the third preset rule includes:

or

The time domain resource allocation mode adopts the same time domain duration for each transmission, and the receiving of the repeated transmission of the PDSCH transmission sent by the network device according to the redundancy version and the time domain resource allocation mode includes:

receiving repeated transmission of PDSCH transmission sent by the network equipment by adopting a fourth preset rule;

wherein the fourth preset rule includes one of the following modes:

13. The data transmission method according to claim 12, wherein before the receiving the repeated transmission of the PDSCH transmission sent by the network device according to the time domain resource allocation pattern, further comprising:

14. The data transmission method according to claim 12, wherein the time domain resource allocation pattern uses different time domain durations for at least two transmissions, and further comprising, before the receiving the repeated transmission of the PDSCH transmission sent by the network device according to the redundancy version and the time domain resource allocation pattern:

and receiving the DMRS transmission mode sent by the network equipment.

15. A terminal, comprising:

a first transmission module, configured to perform repeated transmission of the PUSCH transmission according to the time domain resource allocation pattern;

wherein the first transmission module is configured to:

the time domain resource allocation pattern employs different time domain durations for at least two transmissions, and the first transmission module includes:

a second obtaining unit, configured to obtain a DMRS transmission mode;

wherein the first preset rule includes:

or

The time domain resource allocation pattern employs the same time domain duration for each transmission, and the first transmission module is configured to:

wherein the second preset rule includes one of the following modes:

16. A network device, comprising:

acquiring a DMRS transmission mode;

wherein the first preset rule includes:

or

wherein the second preset rule includes one of the following modes:

17. A network device, comprising:

a second transmission module, configured to perform repeated transmission of the PDSCH transmission according to the time domain resource allocation pattern;

wherein the second transmission module is configured to:

the time domain resource allocation pattern employs different time domain durations for at least two transmissions, and the second transmission module is configured to:

wherein the third preset rule includes:

or

The time domain resource allocation pattern employs the same time domain duration for each transmission, and the second transmission module is configured to:

wherein the fourth preset rule includes one of the following modes:

18. A terminal, comprising:

wherein the third receiving module is configured to:

the time domain resource allocation pattern employs different time domain durations for at least two transmissions, and the third receiving module is configured to:

wherein the third preset rule includes:

or

The time domain resource allocation pattern employs the same time domain duration for each transmission, and the third receiving module is configured to:

wherein the fourth preset rule includes one of the following modes:

19. A terminal, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program when executed by the processor implements the steps of the data transmission method according to any of claims 1 to 5 or according to any of claims 12 to 14.

20. A network device, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when being executed by the processor, carries out the steps of the data transmission method according to one of claims 6 to 11.

21. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the data transmission method according to one of claims 1 to 14.