WO2017092563A1 - Data transmission control method, apparatus, system and related device - Google Patents

Abstract

Embodiments of the invention provide a data transmission control method, apparatus, system and a related device. The method comprises: receiving a data transmission request sent from an MTC terminal; in response to the data transmission request, determining a number of data retransmissions corresponding to the MTC terminal according to network status parameters of the MTC terminal; sending a downlink control signal carrying the number of data retransmissions to the MTC terminal; and repeatedly sending the same data block to the MTC terminal through a physical downlink shared channel (PDSCH) according to the number of data retransmissions. The embodiments of the invention enable effectively informing an MTC terminal about a number of data retransmissions by a network side, and reliability of data transmission is improved.

Description

Data transmission control method, device, system and related equipment Technical field

The present invention relates to the field of communications technologies, and in particular, to a data transmission control method, apparatus, system, and related device.

Background technique

Internet of Things (English: Internet of Things, abbreviation: IOT) is the use of local networks or the Internet and other communication technologies to connect sensors, controllers, machines, personnel, etc., to form people, things, things and things connected to achieve information, Intelligent and remotely manageable networks, where machine-to-machine communication (English: machine to machine, abbreviation: M2M) is an important part of IoT technology, enabling machine type communication (English: machine type communication, abbreviation: MTC) It has become an important research topic for various organizations. The basic goal of MTC technology is to reduce the transmission power while expanding the coverage.

At present, the method of repeatedly transmitting the control information and the data information by the network side to the MTC terminal generally achieves the effect of reducing the transmission power while expanding the coverage, which requires the network side to notify the MTC terminal in advance to repeatedly transmit the control information and the data information to the MTC terminal. frequency. Therefore, how to effectively notify the MTC terminal of the repeated transmission times of related information to improve the reliability of data transmission has become an urgent problem to be solved.

Summary of the invention

The embodiment of the invention provides a data transmission control method, device, system and related device, which can enable the network side to effectively notify the MTC terminal of the number of data retransmissions, thereby improving the reliability of data transmission.

A first aspect of the embodiments of the present invention provides a data transmission control method, including:

a data transmission request sent by the receiver type communication MTC terminal;

Determining, according to the network state parameter of the MTC terminal, a number of data retransmissions corresponding to the MTC terminal, in response to the data transmission request;

Transmitting downlink control signaling carrying the number of data retransmissions to the MTC terminal;

And transmitting the same data block to the MTC terminal through the physical downlink shared channel PDSCH according to the number of data retransmissions.

A second aspect of the embodiments of the present invention provides a data transmission control apparatus, including:

a receiving unit, configured to receive a data transmission request sent by the MTC terminal;

a processing unit, configured to determine, according to the network state parameter of the MTC terminal, a number of data retransmissions corresponding to the MTC terminal, in response to the data transmission request;

a first sending unit, configured to send, to the MTC terminal, downlink control signaling that carries the number of data retransmissions;

The first sending unit is further configured to repeatedly send the same data block to the MTC terminal through the PDSCH according to the number of data retransmissions.

A third aspect of the embodiments of the present invention provides a base station apparatus, including the data transmission control apparatus according to the second aspect.

A fourth aspect of the embodiments of the present invention provides a data transmission control method, including:

The MTC terminal sends a data transmission request to the network side;

The MTC terminal receives downlink control signaling that is sent by the network side and carries the number of data retransmissions corresponding to the MTC terminal, where the number of data retransmissions is responded to by the network side by the data transmission request, according to the The network status parameter of the MTC terminal is determined;

The MTC terminal repeatedly receives the same data block that the network side repeatedly transmits through the PDSCH according to the number of data retransmissions according to the number of data retransmissions.

A fifth aspect of the embodiments of the present invention provides a terminal device, including:

a sending unit, configured to send a data transmission request to the network side;

The first receiving unit is configured to receive, by the network side, downlink control signaling that carries the number of data retransmissions corresponding to the terminal device, where the number of data retransmissions is responded to by the network side by the data transmission request, Determining according to network state parameters of the terminal device;

And a second receiving unit, configured to repeatedly receive, according to the number of data retransmissions, the same data block that is repeatedly sent by the network side by using the PDSCH according to the number of data retransmissions.

A sixth aspect of the embodiments of the present invention provides a data transmission control system, comprising the base station device according to the third aspect, and the terminal device according to the fifth aspect.

The embodiment of the present invention can receive a data transmission request sent by the MTC terminal, and respond to the data transmission. The data transmission parameter determines the number of data retransmissions corresponding to the MTC terminal according to the network state parameter of the MTC terminal, and sends the downlink control signaling carrying the data retransmission times to the MTC terminal, and then passes the PDSCH according to the data retransmission times. The MTC terminal repeatedly sends the same data block, so that the network side can effectively notify the MTC terminal of the number of data retransmissions, thereby improving the reliability of data transmission.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings to be used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without paying for creative labor.

1 is a schematic flow chart of a first embodiment of a data transmission control method according to an embodiment of the present invention;

2 is a schematic structural diagram of an embodiment of a data transmission control apparatus according to an embodiment of the present invention;

3 is a schematic flow chart of a second embodiment of a data transmission control method according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of an embodiment of a terminal device according to an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of an embodiment of a data transmission control system according to an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of an embodiment of a data transmission control device according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of an embodiment of a terminal device according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The technical solution in the embodiments of the present invention can be applied to long term evolution (English: long term evolution, Abbreviation: LTE) Time division duplex (English: time division duplex, abbreviation: TDD) system.

The network side in the embodiment of the present invention may specifically include a base station, a mobility management entity (English: mobile management entity, abbreviation: MME), and a general packet radio service support node (English: serving GPRS (general packet radio service) support node, abbreviation : SGSN) One or more of the network elements.

FIG. 1 is a schematic flowchart diagram of a first embodiment of a data transmission control method according to an embodiment of the present invention. The data transmission control method described in this embodiment includes the following steps:

S101. A network side receiver type communication data transmission request sent by an MTC terminal.

Specifically, the network side receives a data transmission request initiated by the MTC terminal when performing various data services.

S102: The network side responds to the data transmission request, and determines, according to the network state parameter of the MTC terminal, a number of data retransmissions corresponding to the MTC terminal.

The network status parameter may include one or more of channel quality, service type, and quality of service (QoS: QoS), and the channel quality may be downlink signal to noise of the MTC terminal. For the service type of the MTC terminal, the reliability requirement level can be divided, that is, the service type with higher priority or emergency, the reliability requirement level is higher, the regular and common service types, and the reliability requirement level is higher. low. Different data transmissions can also correspond to different QoS levels, that is, define the QoS required for data transmission.

Specifically, the MTC terminal may carry the network state parameter in the data transmission request, or the network side sends a request for acquiring the MTC terminal network state parameter to the MTC terminal, and receives the carried network sent by the MTC terminal. The feedback information of the state parameter is used to obtain the channel quality of the MTC terminal, the reliability level of the service type, and the QoS level corresponding to the data transmission, and then the network side can determine the reliability level according to the channel quality and the service type. At least two of the QoS levels corresponding to the data transmission determine the number of data retransmissions corresponding to the MTC terminal, so that the number of data retransmissions can be flexibly and accurately determined according to the network state parameters of the MTC terminal, so as to ensure the reliability of data transmission. .

Further, the network side may increase the number of data retransmissions when the channel quality of the MTC terminal is low, the service type has a high reliability requirement level, and the QoS level is high, so as to improve data transmission reliability. Sexually, when the channel quality of the MTC terminal is high, the service type has a low level of reliability requirements, and the QoS level is low, the number of data retransmissions is appropriately reduced to reduce the load of the network.

For example, if the channel quality is m ₁ , the service type requires a reliability level of m ₂ , the data transmission corresponds to a QoS level of m ₃ , and the network side may according to at least two of m ₁ , m _{2 ,} and m ₃ . Determine the number of data retransmissions R, an optional formula is: R = (1/m ₁ ) * m ₂ * m ₃ , or R = (1/m ₁ ) * m ₂ , or R = (1/ m ₁ )*m ₃ , or R=m ₂ *m ₃ .

It should be noted that the specific calculation formula of the data retransmission times R is not limited to the above-exemplified formulas, and for example, different weights may be assigned to each specific parameter.

In some feasible implementation manners, the network side may also obtain the terminal capability parameter of the MTC terminal, and determine the number of data retransmissions corresponding to the MTC terminal according to the network state parameter of the MTC terminal and the terminal capability parameter.

The terminal capability parameter may include, but is not limited to, one or more of a duplex capability, a terminal version, a supported frequency band, a packet data convergence protocol (PDCP) parameter, and a remaining power. The duplex capability may include a half-duplex frequency division duplexing (HD-FDD) capability, which is a third-generation partner program supported by the MTC terminal (English: 3rd) Generation partnership project, abbreviated: 3GPP) standard version, such as R12 version, R13 version in 3GPP, etc., the supported frequency bands such as Band1, Band3, etc., the PDCP parameters such as header compression file Profile 0, Profile 1, etc. The remaining power is the current remaining power value of the MTC terminal, such as 90%, 15%, and the like. The terminal capability parameter described in the embodiment of the present invention may be a capability indicator included in the message (for example, a certain capability of the terminal may be indicated by a flag bit). As part of the embodiment of the present invention, in the LTE and LTE-A systems, whether the half-duplex transmission is supported may be determined by the base station scheduler according to the capability parameter of the terminal, and in the FDD mode, the base station scheduler may perform control according to the Downlink and uplink transmissions do not occur simultaneously on the same frequency. That is to say, in the HD-FDD communication mode, the mode conversion from the transmission to the reception needs to be performed between the base station and the terminal, and the delay caused by this conversion may cause a collision between the uplink transmission and the downlink subframe. .

Specifically, the MTC terminal may carry the network state parameter and the terminal capability parameter in the data transmission request, or the network side sends a request for acquiring the MTC terminal network state parameter and the terminal capability parameter to the MTC terminal, and receives the request. The MTC terminal sends a network status parameter And the feedback information of the number and the terminal capability parameter, to obtain the network state parameters such as the channel quality of the MTC terminal, the reliability level of the service type, and the QoS level corresponding to the data transmission, and the duplex capability, the terminal version, the supported frequency band, The terminal capability parameter such as the PDCP parameter and the remaining power, and the network side may determine the number of data retransmissions corresponding to the MTC terminal according to at least one of the network state parameter and the terminal capability parameter.

The network side may use the terminal capability parameter of the MTC terminal as follows: different maximum data retransmission times may be set according to different duplex capabilities, and the network side may predict uplink transmission and based on the maximum number of data retransmission times. A collision may occur between downlink subframes, so that the network side can schedule data transmission to avoid the collision. The test indicates that the network state parameters are combined, and different maximum data retransmission times are set according to different duplex capabilities. It can avoid conflicts caused by different terminal capabilities, and can also improve the reliability of data transmission. Different maximum data retransmission times are configured for different terminal versions. For example, when the terminal version of the MTC terminal is R12, the maximum data weight supported is The number of transmissions is 6. When the version is R13, the maximum number of data retransmissions supported is 8. Since the maximum number of data retransmissions of the R13 version of the MTC terminal is greater than that of the R12 version of the MTC terminal, if the network side determines the MTC terminal to access. For the R12 version, you can configure the MTC terminal to meet the maximum number of data retransmissions of 6. If the frequency of the data retransmission is not enough for the MTC terminal to receive the data retransmission times, the signaling resources are wasted; if the frequency band supported by the MTC terminal is Band3, the network side can configure the MTC terminal. If the frequency band supported by the MTC terminal is Band1, the network side can configure more data retransmission times (for example, 6 times) for the MTC terminal. This is because Band1 is more than Band3. The high frequency band leads to a large attenuation of electromagnetic wave transmission, and the probability of data transmission error is large, so that more data retransmission times can be configured for the MTC terminal with the supported frequency band Band1 to ensure the correct and complete data transmission; If the PDCP parameter of the MTC terminal is to support the profile 0, the network side can configure the number of data retransmissions (for example, 6 times) for the MTC terminal. If the PDCP parameter of the MTC terminal supports the profile 1, the network side can be The MTC terminal is configured with fewer data retransmission times (for example, 4 times). This is because Profile 0 does not perform header compression, and the amount of data transmitted is larger than that of Profile0, resulting in the same transmit power. In the case of a rate, the probability of data transmission error is large, so that the number of data retransmissions of the MTC terminal supporting the Profile 0 can be configured for the PDCP parameter to ensure the correct and complete data transmission; if the remaining power of the MTC terminal is 15 %, the network side can be the The MTC terminal is configured with a smaller number of data retransmission times (for example, 4 times). If the remaining power of the MTC terminal is 90%, the network side may configure the MTC terminal with a greater number of data retransmission times (for example, 6 times). Therefore, the number of data retransmissions is appropriately reduced when the power of the MTC terminal is low to ensure that the MTC terminal can maintain a long working time.

Further, based on the foregoing principle, the network side may combine at least one parameter of the network state parameter with at least one parameter of the terminal capability parameter to determine the number of data retransmissions corresponding to the MTC terminal, so that the network The side can determine the number of data retransmissions more flexibly and accurately to ensure the reliability of data transmission.

For example, the QoS in the network state parameter is combined with the duplex capability in the terminal capability parameter. If the QoS level is high and the duplex capability of the MTC terminal is strong, the network side can configure the MTC terminal. The number of data retransmissions (for example, 8 times). If the QoS level is high, but the duplex capability of the MTC terminal is poor, the network side can configure fewer times of data retransmission for the MTC terminal (for example, 7 times). If the QoS level is low, but the duplex capability of the MTC terminal is strong, the network side can configure more data retransmission times (for example, 6 times) for the MTC terminal, if the QoS level is lower, and If the duplex capability of the MTC terminal is poor, the network side can configure fewer times of data retransmission (for example, 5 times) for the MTC terminal, thereby optimizing network resource configuration and ensuring data transmission reliability.

For example, the channel quality in the network state parameter is combined with the supported frequency band in the terminal capability parameter. If the channel quality is poor, and the frequency band supported by the MTC terminal is Band1, the network side can configure the MTC terminal. The number of data retransmissions (for example, 8 times). If the channel quality is poor, but the frequency band supported by the MTC terminal is Band3, the network side can configure fewer times of data retransmission for the MTC terminal (for example, 7 times); If the channel quality is good, but the frequency band supported by the MTC terminal is Band1, the network side can configure more data retransmission times (for example, 6 times) for the MTC terminal, if the channel quality is good, and the frequency band supported by the MTC terminal For Band3, the network side can configure fewer times of data retransmission (such as 5 times) for the MTC terminal, avoiding the number of data retransmissions with poor channel quality but too many configurations, and better channel quality but too few configurations. The number of data retransmissions can be optimized to optimize the configuration of network resources.

For another example, the service type in the network state parameter is combined with the remaining power in the terminal capability parameter, if the service type requires a higher reliability level, and the remaining power of the MTC terminal is compared. If the number of data retransmissions (for example, 8 times) is configured for the MTC terminal, the network side may have a higher level of reliability requirements, but the MTC terminal has a higher reliability requirement level. If the remaining power is small (for example, not higher than 20%), the network side can configure the number of data retransmissions (for example, 7 times) for the MTC terminal; if the service type requires a lower level of reliability, If the remaining power of the MTC terminal is large (for example, not less than 50%), the network side can configure more data retransmission times (for example, 6 times) for the MTC terminal, if the service type has a lower reliability requirement level. If the remaining power of the MTC terminal is small (for example, not higher than 20%), the network side can configure the number of data retransmissions (for example, 5 times) for the MTC terminal to avoid the reliability requirement of the service type. The number of data retransmissions with a higher level but too many configurations and the number of times that the service type requires a lower level of reliability but less configuration data retransmission times can optimize the configuration of network resources and rationally allocate the remaining power.

It should be noted that the specific manner in which the network side combines at least one parameter of the network state parameter with at least one parameter of the terminal capability parameter to determine the number of data retransmissions corresponding to the MTC terminal is not limited to the foregoing. For example, you can configure it flexibly according to the actual application scenario.

In addition, the network side may also update the number of data retransmissions (ie, modify the value of the number of data retransmissions), and may be updated in the following cases:

(1) The network side may update the data retransmission times according to the current network state parameter and/or the terminal capability parameter of the MTC terminal when receiving the data transmission request sent by the MTC terminal, which may be sent each time the MTC terminal receives the data transmission request. The data transmission request is updated, or it may be updated when a predetermined number of data transmission requests are received.

(2) The network side may update the number of data retransmissions according to the network state parameter and/or the terminal capability parameter of the MTC terminal when the network state parameter and/or the terminal capability parameter of the MTC terminal changes, wherein the network state parameter The change may include: the amplitude of the channel quality change of the MTC terminal exceeds a preset threshold, the service type changes, the QoS required for data transmission changes, and the change of the terminal capability parameter may include: the change of the duplex capability. The terminal version is changed, the supported frequency band changes, the PDCP parameters are changed, and the remaining power is higher or lower than the preset value.

(3) The network side may update the number of data retransmissions according to the preset state frequency (for example, 5 times/hour) or at the appointed time according to the network state parameter and/or the terminal capability parameter of the MTC terminal. The MTC terminal may be sent to the network side, or may be determined by the network side according to the recorded change of the MTC terminal network state parameter and/or the terminal capability parameter.

Therefore, the network side updates the number of data retransmissions to ensure the reliability of data transmission, and can effectively balance the load of the network and improve the utilization of frequency resources.

S103. The network side sends downlink control signaling that carries the number of data retransmissions to the MTC terminal.

The number of consecutive consecutive subframes in the TDD system is 9. In addition to the first transmitted subframe, the number of data retransmissions can be 0 to 8 times. Therefore, 4 bits (English: bit) are required to indicate data retransmission. frequency.

Specifically, the network side may use the information of the hybrid automatic repeat request (English: process number) in the downlink control information (English: downlink control information, abbreviation: DCI). The field indicates the number of retransmissions of the data, that is, the value of the process number information field of the HARQ process is set to the number of data retransmissions, and the DCI is sent to the MTC terminal through a physical downlink control channel (English: physical downlink control channel, PDCCH). At the same time, the MTC terminal is instructed to receive downlink transmission data by means of synchronous HARQ.

For example, the HARQ timing of the physical downlink shared channel (PDSCH) transmission still follows the timing relationship in the R12 standard in 3GPP, and binds the HARQ process process to the subframe number, assuming that the TDD system is uplink and downlink. The ratio of the sub-frame is 1:1, and the uplink and downlink timeslots are configured as DSUUDDSUUD (D stands for the downlink subframe, S stands for the special subframe, and U stands for the uplink subframe), and the corresponding downlink HARQ process process and the subframe correspondence can be As shown in Table 1:

Subframe number 0 1 2 3 4 5 6 7 8 9 HARQ process number 0 1 2 3 4 5

Table 1

If the network side determines that the number of data retransmissions corresponding to the current data transmission request of the MTC terminal is two, the network side may set the value of the process number information field of the HARQ process number to 0010.

In some feasible implementation manners, the network side may also send the downlink control signaling that carries the number of retransmissions of the data to the MTC terminal by repeatedly sending the DCI to the MTC terminal, that is, the network side first follows the 3GPP in the MTC terminal through the PDCCH. The rule of the R12 standard sends the DCI (that is, the first DCI) once. The number of the HARQ process in the first DCI is used to indicate the HARQ process process used for data transmission, and then the DCI is sent to the MTC terminal again by the PDCCH (ie, The second DCI), the number of HARQ processes in the second DCI is used to indicate the number of retransmissions of the data, and the subsequent data formats and transmission and reception timings are unchanged.

It should be noted that the network side may also send the DCI (ie, the first DCI) to the MTC terminal by using the PDCCH. The number of the HARQ process in the first DCI is used to indicate the number of retransmissions of the data, and then according to the 3GPP. The rule of the R12 standard retransmits the DCI (ie, the second DCI) to the MTC terminal by using the PDCCH, and the process number information field of the HARQ process in the second DCI is used to indicate the HARQ process process used for data transmission, that is, the embodiment of the present invention sends The number of data retransmissions and the sequence of the HARQ process used for data transmission are not limited.

In some feasible implementation manners, the network side may further send downlink control signaling carrying the number of retransmissions of the data to the MTC terminal by adding 4 bits in the DCI to indicate the number of retransmissions of the data, that is, the network. The side adds 4 bits in the DCI of the PDCCH format except PDCCH format 0 to indicate the number of retransmissions of the data. The network side can pre-arrange the position of the 4 bits in the DCI with the MTC terminal, or the network side is in the MTC. Sending, by the terminal, a notification message for indicating the location information of the 4 bits in the DCI before or after the downlink control signaling carrying the number of retransmissions of the data, for example, assuming that the number of data retransmissions corresponding to the current data transmission request is If it is 3 times, the value of the newly added 4 bit on the network side is set to 0011.

S104. The network side repeatedly sends the same data block to the MTC terminal through the physical downlink shared channel PDSCH according to the number of data retransmissions.

Specifically, after the network side sends the data retransmission times to the MTC terminal, the data block can be sent to the MTC terminal through the PDSCH, and the same data block is repeatedly sent until the number of repetitions reaches the number of data retransmissions, and the MTC terminal follows the The number of data retransmissions repeatedly receives the same data block.

In the embodiment of the present invention, the network side receives the data transmission request sent by the MTC terminal, and determines the data corresponding to the MTC terminal according to the network state parameter of the MTC terminal in response to the data transmission request. The number of retransmissions is further sent to the MTC terminal for downlink control signaling carrying the number of retransmissions of the data; the network side repeatedly transmits the same data block to the MTC terminal through the PDSCH according to the number of retransmissions of the data, so that the data can be flexibly and accurately determined. The number of retransmissions is effectively notified to the MTC terminal by the number of data retransmissions, thereby improving the reliability of data transmission.

FIG. 2 is a schematic structural diagram of an embodiment of a data transmission control apparatus according to an embodiment of the present invention. The data transmission control device described in this embodiment includes:

The receiving unit 201 is configured to receive a data transmission request sent by the MTC terminal.

The processing unit 202 is configured to determine, according to the network state parameter of the MTC terminal, the number of data retransmissions corresponding to the MTC terminal, in response to the data transmission request.

The network status parameter may include, but is not limited to, one or more of channel quality, service type, and QoS. The channel quality may be a downlink signal to noise ratio of the MTC terminal, and the service type of the MTC terminal may be reliable. The classification of the level of sexual requirements, that is, the higher priority or urgent service type, has a higher reliability requirement level, and the conventional and common service types have lower reliability requirements. Different data transmissions can also correspond to different QoS levels, that is, define the QoS required for data transmission.

The processing unit 202 may specifically include:

The obtaining unit 2020 is configured to obtain, according to the data transmission request, a channel quality of the MTC terminal, a requirement level of the service type to reliability, and a QoS level corresponding to the data transmission.

The determining unit 2021 is configured to determine, according to the channel quality, the required level of reliability of the service type, and the QoS level corresponding to the data transmission, the number of data retransmissions corresponding to the MTC terminal.

Specifically, the MTC terminal may carry the network state parameter in the data transmission request, or the network side sends a request for acquiring the MTC terminal network state parameter to the MTC terminal, and receives the carried network sent by the MTC terminal. The feedback information of the state parameter, the obtaining unit 2020 obtains the channel quality of the MTC terminal, the requirement level of the service type and the QoS level corresponding to the data transmission, and the determining unit 2021 can determine the reliability according to the channel quality and the service type. At least two of the required level and the QoS level corresponding to the data transmission determine the number of data retransmissions corresponding to the MTC terminal, so that the network state parameter of the MTC terminal can be flexibly and accurately determined. The number of data retransmissions is determined to ensure the reliability of data transmission.

Further, the determining unit 2021 may increase the number of data retransmissions to improve the reliability of data transmission when the channel quality of the MTC terminal is low, the service type has a higher reliability requirement level, and the QoS level is higher, and the MTC terminal is used. The channel quality is high, the service type has a lower level of reliability requirements, and the QoS level is lower, the number of data retransmissions is appropriately reduced to reduce the load on the network.

In some feasible implementation manners, the processing unit 202 may determine the number of data retransmissions corresponding to the MTC terminal according to the network state parameter of the MTC terminal and the terminal capability parameter.

The processing unit 202 is further configured to acquire a terminal capability parameter of the MTC terminal, and determine the number of data retransmissions according to the network state parameter and the terminal capability parameter.

The terminal capability parameter may include, but is not limited to, one or more of a duplex capability, a terminal version, a supported frequency band, a PDCP parameter, and a remaining power. The duplex capability may include an HD-FDD capability, and the terminal version is For the standard version of the 3GPP supported by the MTC terminal, for example, the R12 version, the R13 version, and the like in the 3GPP, the supported frequency band is, for example, Band1, Band3, etc., and the PDCP parameters, such as the header compressed file Profile 0, Profile 1, etc., the remaining The power is the current remaining power value of the MTC terminal, for example, 90%, 15%, and the like. The terminal capability parameter described in the embodiment of the present invention may be a capability indicator included in the message (for example, a certain capability of the terminal may be indicated by a flag bit). As part of the embodiment of the present invention, in the LTE and LTE-A systems, whether the half-duplex transmission is supported may be determined by the base station scheduler according to the capability parameter of the terminal, and in the FDD mode, the base station scheduler may perform control according to the Downlink and uplink transmissions do not occur simultaneously on the same frequency. That is to say, in the HD-FDD communication mode, the mode conversion from the transmission to the reception needs to be performed between the base station and the terminal, and the delay caused by this conversion may cause a collision between the uplink transmission and the downlink subframe. .

Specifically, the MTC terminal may carry the network state parameter and the terminal capability parameter in the data transmission request, or the network side sends a request for acquiring the MTC terminal network state parameter and the terminal capability parameter to the MTC terminal, and receives the request. The MTC terminal sends the feedback information carrying the network state parameter and the terminal capability parameter, and the processing unit 202 acquires the network state parameter such as the channel quality of the MTC terminal, the requirement level of the service type to the reliability, and the QoS level corresponding to the data transmission, and The terminal capability parameter, such as the duplex capability, the terminal version, the supported frequency band, the PDCP parameter, and the remaining power, and the processing unit 202 may further perform the at least one parameter according to the network state parameter and the terminal capability. At least one parameter of the force parameter determines the number of data retransmissions corresponding to the MTC terminal.

The utilization of the terminal capability parameter of the MTC terminal may be as follows: different processing units 202 may set different maximum data retransmission times according to different duplex capabilities, and the network side may predict uplink transmission based on the maximum number of data retransmission times. A collision may occur between the downlink subframe and the downlink subframe, so that the network side can schedule the data transmission to avoid the conflict. The test indicates that the network state parameters are combined, and different maximum data retransmission times are set according to different duplex capabilities. Not only can conflicts caused by different terminal capabilities be avoided, but also the reliability of data transmission can be improved. Different maximum data retransmission times can be configured for different terminal versions. For example, the maximum data supported when the terminal version of the MTC terminal is R12 version. The number of retransmissions is 6. When the version is R13, the maximum number of data retransmissions supported is 8. Since the maximum number of data retransmissions of the R13 version of the MTC terminal is greater than that of the R12 version of the MTC terminal, if the network side determines the MTC of the access. When the terminal is in the R12 version, the processing unit 202 can be configured in the range of the maximum number of data retransmissions of 6. The number of data retransmissions of the MTC terminal capability is avoided, and the MTC terminal is prevented from receiving signaling resources for the configuration of the data retransmission times that does not meet its own capabilities; if the frequency band supported by the MTC terminal is Band3, the processing unit 202 may be The MTC terminal is configured with a small number of data retransmissions (for example, 4 times). If the frequency band supported by the MTC terminal is Band1, the processing unit 202 can configure more data retransmission times (for example, 6 times) for the MTC terminal. This is because Band1 is higher than Band3's frequency band, which causes a large attenuation during electromagnetic wave transmission and a high probability of data transmission error. Therefore, it can configure more data retransmission times for the supported MTC terminal with Band1 to ensure data transmission. If the PDCP parameter of the MTC terminal is to support Profile 0, the processing unit 202 can configure a greater number of data retransmission times (for example, 6 times) for the MTC terminal, if the PDCP parameter of the MTC terminal is a support profile. 1, the processing unit 202 can configure fewer times of data retransmission for the MTC terminal (for example, 4 times), because Profile 0 does not perform header compression, and the amount of data transmitted is If the profile 0 is large, the probability of data transmission error is high in the case of the same transmit power. Therefore, the number of data retransmissions can be configured for the MTC terminal supporting the Profile 0 with the PDCP parameter to ensure the correct and complete data transmission. If the remaining power of the MTC terminal is 15%, the processing unit 202 may configure the MTC terminal with a smaller number of data retransmission times (for example, 4 times), and if the remaining power of the MTC terminal is 90%, the processing unit 202 may The number of times of data retransmission (for example, 6 times) is configured for the MTC terminal, so that the number of data retransmissions is appropriately reduced when the power of the MTC terminal is low to ensure that the MTC terminal can Enough to maintain a long working time.

Further, based on the foregoing principle, the processing unit 202 may combine at least one parameter of the network state parameter with at least one parameter of the terminal capability parameter to determine the number of data retransmissions corresponding to the MTC terminal, thereby The number of data retransmissions can be determined more flexibly and accurately to ensure the reliability of data transmission.

For example, the QoS in the network state parameter is combined with the duplex capability in the terminal capability parameter. If the QoS class is high and the duplex capability of the MTC terminal is strong, the processing unit 202 can configure the MTC terminal. More data retransmission times (for example, 8 times). If the QoS level is high, but the duplex capability of the MTC terminal is poor, the processing unit 202 can configure the MTC terminal with fewer data retransmission times (for example). 7 times); if the QoS level is lower, but the duplex capability of the MTC terminal is stronger, the processing unit 202 can configure more data retransmission times (for example, 6 times) for the MTC terminal, if the QoS level is lower. If the duplex capability of the MTC terminal is poor, the processing unit 202 can configure fewer times of data retransmission (for example, 5 times) for the MTC terminal, thereby optimizing network resource configuration and ensuring data transmission reliability. .

The first sending unit 203 is configured to send, to the MTC terminal, downlink control signaling that carries the number of data retransmissions.

The number of consecutive consecutive subframes in the TDD system is 9. In addition to the first transmitted subframe, the number of data retransmissions can be 0 to 8 times. Therefore, 4 bits (English: bit) are required to indicate data retransmission. frequency.

The first sending unit 203 is further configured to repeatedly send the same data block to the MTC terminal through the PDSCH according to the number of data retransmissions.

In some possible implementations, the first sending unit 203 may specifically include:

The first setting unit 2030 is configured to set a value of a process number information field of a HARQ process number in the DCI to the number of data retransmissions.

The second sending unit 2031 is configured to send the DCI to the MTC terminal by using a PDCCH, and instruct the MTC terminal to receive downlink transmission data by using a synchronous HARQ.

Specifically, the first setting unit 2030 may use the information field of the process number of the HARQ process in the DCI to indicate the number of data retransmissions, that is, the value of the process number information field of the HARQ process number is set as the number of data retransmissions, and then the second transmission. The unit 2031 sends the PDCCH to the MTC terminal. The DCI is sent, and the MTC terminal is instructed to receive downlink transmission data by means of synchronous HARQ.

In some possible implementation manners, the specific manner in which the first sending unit 203 sends the downlink control signaling carrying the number of data retransmissions to the MTC terminal is:

The first DCI is sent to the MTC terminal by using a PDCCH, and the number of HARQ processes in the first DCI is used to indicate a HARQ process process used for data transmission.

The second DCI is sent to the MTC terminal by using the PDCCH, and the number of HARQ processes in the second DCI is used to indicate the number of data retransmissions.

or,

The first DCI is sent to the MTC terminal by using the PDCCH, and the number of HARQ processes in the first DCI is used to indicate the number of data retransmissions.

The second DCI is sent to the MTC terminal by using the PDCCH, and the HARQ process number process number information field in the second DCI is used to indicate the HARQ process process used for data transmission.

Specifically, the first sending unit 203 sends the DCI (that is, the first DCI) to the MTC terminal according to the rule of the R12 standard in the 3GPP through the PDCCH, and the number of the HARQ process in the first DCI is used to indicate the data transmission. The HARQ process process, and then the first sending unit 203 sends the DCI (ie, the second DCI) to the MTC terminal by using the PDCCH, and the process number information field of the HARQ process in the second DCI is used to indicate the number of data retransmissions.

It should be noted that the first sending unit 203 may also send the DCI (ie, the first DCI) to the MTC terminal by using the PDCCH. The number of the HARQ process in the first DCI is used to indicate the number of data retransmissions, and then The DCI process number information field in the second DCI is used to indicate the HARQ process process used for data transmission, that is, the implementation of the present invention, in accordance with the rules of the R12 standard in the 3GPP, by using the PDCCH to retransmit the DCI (ie, the second DCI) to the MTC terminal. For example, the order in which the first transmitting unit 203 sends the number of data retransmissions and the HARQ process process used for data transmission is not limited.

In some possible implementation manners, the specific manner in which the first sending unit 203 sends the downlink control signaling carrying the number of data retransmissions to the MTC terminal is:

The DCI is transmitted to the MTC terminal through a PDCCH, and the DCI includes a flag bit for indicating the number of times of the data retransmission.

Specifically, the second setting unit 2032 adds 4 bits in the DCI of the PDCCH format except for the PDCCH format 0 to indicate the number of data retransmissions, and the third sending unit 2033 sends the DCI to the MTC terminal through the PDCCH, for example, for example. Assuming that the number of data retransmissions corresponding to the data transmission request is three, the value of the newly added 4 bit is set to 0011 on the network side.

In some possible implementations, the data transmission control apparatus further includes:

The updating unit 204 is configured to update the data retransmission times according to the network state parameter and/or the terminal capability parameter of the MTC terminal when receiving the data transmission request sent by the MTC terminal, or to be used in the network When the state parameter and/or the terminal capability parameter are changed, the number of data retransmissions is updated according to the network state parameter and/or the terminal capability parameter of the MTC terminal, or is used according to the preset frequency or at the appointed time. The network state parameter and/or the terminal capability parameter of the MTC terminal updates the number of data retransmissions.

In some feasible implementation manners, the data transmission control apparatus in this embodiment may be disposed in the base station apparatus.

In the embodiment of the present invention, the network side receives the data transmission request sent by the MTC terminal, and determines the number of data retransmissions corresponding to the MTC terminal according to the network state parameter of the MTC terminal in response to the data transmission request, and further sends the data transmission number to the MTC terminal. Downlink control signaling of the number of data retransmissions; the network side repeatedly transmits the same data block to the MTC terminal through the PDSCH according to the number of data retransmission times, which can flexibly and accurately determine the number of data retransmissions and effectively retransmit the data Notify the MTC terminal to improve the reliability of data transmission.

FIG. 3 is a schematic flowchart diagram of a second embodiment of a data transmission control method according to an embodiment of the present invention. The data transmission control method described in this embodiment includes the following steps:

S301. The MTC terminal sends a data transmission request to the network side.

Specifically, the MTC terminal initiates a data transmission request to the network side when performing various data services.

S302, the MTC terminal receives, by the network side, downlink control signaling that carries the number of data retransmissions corresponding to the MTC terminal, where the number of data retransmissions is responded to by the network side by the data transmission request, according to The network status parameter of the MTC terminal is determined.

The network status parameter may include, but is not limited to, one or more of channel quality, service type, and QoS, where the channel quality may be a downlink signal to noise ratio of the MTC terminal, for the MTC. The service type of the terminal can be classified according to the reliability requirement level, that is, the service type with higher priority or emergency, and the reliability requirement level is higher. The regular and common service types have lower reliability requirements. Different data transmissions can also correspond to different QoS levels, that is, define the QoS required for data transmission.

Specifically, the MTC terminal may carry the network state parameter in the data transmission request, or the MTC terminal may carry the network state parameter when receiving the request for acquiring the network state parameter of the MTC terminal sent by the network side. The feedback information is sent to the network side, so that the network side obtains the channel quality of the MTC terminal, the reliability requirement level of the service type, and the QoS level corresponding to the data transmission, and then the network side can perform reliability according to the channel quality and the service type. At least two of the required level and the QoS level corresponding to the data transmission determine the number of data retransmissions corresponding to the MTC terminal, so that the number of data retransmissions can be flexibly and accurately determined according to the network state parameter of the MTC terminal to ensure data. The reliability of the transmission.

Further, the network side may increase the number of data retransmissions to improve the reliability of data transmission when the channel quality of the MTC terminal is low, the service type has a high reliability requirement level, and the QoS level is high, and the reliability of the data transmission is improved at the MTC terminal. When the channel quality is high, the service type requires a lower level of reliability, and the QoS level is lower, the number of data retransmissions is appropriately reduced to reduce the load on the network.

In some feasible implementation manners, the network side may also obtain the terminal capability parameter of the MTC terminal, and determine the number of data retransmissions corresponding to the MTC terminal according to the network state parameter of the MTC terminal and the terminal capability parameter.

The terminal capability parameter may include, but is not limited to, one or more of a duplex capability, a terminal version, a supported frequency band, a PDCP parameter, and a remaining power. The duplex capability may include an HD-FDD capability, and the terminal version is For the standard version of the 3GPP supported by the MTC terminal, for example, the R12 version, the R13 version, and the like in the 3GPP, the supported frequency band is, for example, Band1, Band3, etc., and the PDCP parameters, such as the header compressed file Profile 0, Profile 1, etc., the remaining The power is the current remaining power value of the MTC terminal, for example, 90%, 15%, and the like. The terminal capability parameter described in the embodiment of the present invention may be a capability indicator included in the message (for example, a certain capability of the terminal may be indicated by a flag bit). As part of the embodiment of the present invention, in the LTE and LTE-A systems, whether the half-duplex transmission is supported may be determined by the base station scheduler according to the capability parameter of the terminal, and in the FDD mode, the base station scheduler may perform control according to the Downlink and uplink transmissions do not occur simultaneously on the same frequency Now. That is to say, in the HD-FDD communication mode, the mode conversion from the transmission to the reception needs to be performed between the base station and the terminal, and the delay caused by this conversion may cause a collision between the uplink transmission and the downlink subframe. .

Specifically, the MTC terminal may carry the network state parameter and the terminal capability parameter in the data transmission request, or may be the request that the MTC terminal receives the network state parameter and the terminal capability parameter that is sent by the network side to obtain the MTC terminal network state parameter and the terminal capability parameter. The feedback information carrying the network state parameter and the terminal capability parameter is sent to the network side, so that the network side acquires the network quality parameter such as the channel quality of the MTC terminal, the reliability level of the service type, and the QoS level corresponding to the data transmission. And a terminal capability parameter, such as a duplex capability, a terminal version, a supported frequency band, a PDCP parameter, and a remaining power, and the network side may further perform, according to at least one of the network state parameter and the terminal capability parameter, Determine the number of data retransmissions corresponding to the MTC terminal.

The network side may use the terminal capability parameter of the MTC terminal as follows: different maximum data retransmission times may be set according to different duplex capabilities, and the network side may predict uplink transmission and based on the maximum number of data retransmission times. A collision may occur between downlink subframes, so that the network side can schedule data transmission to avoid the collision. The test indicates that the network state parameters are combined, and different maximum data retransmission times are set according to different duplex capabilities. It can avoid conflicts caused by different terminal capabilities, and can also improve the reliability of data transmission. Different maximum data retransmission times are configured for different terminal versions. For example, when the terminal version of the MTC terminal is R12, the maximum data weight supported is The number of transmissions is 6. When the version is R13, the maximum number of data retransmissions supported is 8. Since the maximum number of data retransmissions of the R13 version of the MTC terminal is greater than that of the R12 version of the MTC terminal, if the network side determines the MTC terminal to access. For the R12 version, you can configure the MTC terminal to meet the maximum number of data retransmissions of 6. If the frequency of the data retransmission is not enough for the MTC terminal to receive the data retransmission times, the signaling resources are wasted; if the frequency band supported by the MTC terminal is Band3, the network side can configure the MTC terminal. If the frequency band supported by the MTC terminal is Band1, the network side can configure more data retransmission times (for example, 6 times) for the MTC terminal. This is because Band1 is more than Band3. The high frequency band leads to a large attenuation of electromagnetic wave transmission, and the probability of data transmission error is large, so that more data retransmission times can be configured for the MTC terminal with the supported frequency band Band1 to ensure the correct and complete data transmission; The PDCP parameter of the MTC terminal supports Profile 0, and the network side The number of data retransmissions (for example, 6 times) can be configured for the MTC terminal. If the PDCP parameter of the MTC terminal is to support Profile 1, the network side can configure fewer times of data retransmission for the MTC terminal (for example, 4). Times), this is because Profile 0 does not perform header compression, and the amount of data transmitted is larger than that of Profile0, resulting in a high probability of data transmission error in the case of equal transmit power, so that the PDCP parameter can be an MTC terminal supporting Profile 0. Configure the number of data retransmissions to ensure the correct and complete data transmission. If the remaining power of the MTC terminal is 15%, the network side can configure the MTC terminal with a smaller number of data retransmissions (for example, 4 times). If the remaining power of the MTC terminal is 90%, the network side may configure the MTC terminal with a greater number of data retransmission times (for example, 6 times), thereby appropriately reducing the number of data retransmissions when the power of the MTC terminal is low. Ensure that the MTC terminal can maintain a long working time.

Further, based on the foregoing principle, the network side may combine at least one parameter of the network state parameter with at least one parameter of the terminal capability parameter to determine the number of data retransmissions corresponding to the MTC terminal, so that the network The side can determine the number of data retransmissions more flexibly and accurately to ensure the reliability of data transmission.

Further, the MTC terminal receives the DCI sent by the network side through the PDCCH, and the number of the HARQ process number in the DCI is the number of data retransmissions corresponding to the MTC terminal, and the number of data retransmissions is obtained, and the MTC terminal simultaneously The downlink transmission data is received by means of synchronous HARQ.

In some feasible implementation manners, the MTC terminal may further receive the first DCI sent by the network side through the PDCCH, where the number of HARQ processes in the first DCI is used to represent the HARQ process process used for data transmission, and receive the network. The second DCI sent by the PDCCH, the number of HARQ processes in the second DCI, the process number information field is used to indicate the number of data retransmissions corresponding to the MTC terminal, and the number of data retransmissions is obtained.

It should be noted that the MTC terminal may also receive the first DCI sent by the PDCCH on the network side, where the number of HARQ processes in the first DCI is used to indicate the number of data retransmissions corresponding to the MTC terminal, and the network side passes The second DCI sent by the PDCCH, the number of HARQ processes in the second DCI, the process number information field is used to represent the HARQ process process used for data transmission, and the number of data retransmissions is obtained, that is, the data is sent by the network side in the embodiment of the present invention. The number of retransmissions and the sequence of the HARQ process used by the data transmission are not limited.

In some feasible implementation manners, the MTC terminal may further receive the DCI sent by the network side by using the PDCCH, where the DCI includes a flag bit for indicating the number of times of the data retransmission, and then obtain the number of retransmissions of the data, for example, Assuming that the number of data retransmissions corresponding to the data transmission request is three, the value of the newly added 4 bits is set to 0011 on the network side.

It should be noted that the number of data retransmissions may be updated by the network side according to the network state parameter and/or the terminal capability parameter of the MTC terminal when receiving the data transmission request sent by the MTC terminal, specifically, the The data transmission request sent by the MTC terminal is updated, or may be updated when a predetermined number of data transmission requests are received.

Or, when the network state parameter and/or the terminal capability parameter are changed by the network side, the network state parameter and/or the terminal capability parameter of the MTC terminal are updated, where the change of the network state parameter may specifically include: the MTC terminal The change of the channel quality exceeds the preset threshold, the service type changes, and the QoS required for data transmission changes. The change of the terminal capability parameter may include: changing the duplex capability, changing the terminal version, and supporting the frequency band. Change, PDCP parameters change, the remaining power is higher or lower than the preset value.

Or, the network side is updated according to the network state parameter and/or the terminal capability parameter of the MTC terminal according to the preset frequency or the scheduled time, and the appointment time may be specifically sent by the MTC terminal to the network side, or may be recorded by the network side according to the network side. The change of the MTC terminal network state parameter and/or the terminal capability parameter is determined.

Therefore, the network side updates the number of data retransmissions to ensure the reliability of data transmission, and can effectively balance the load of the network and improve the utilization of frequency resources.

S303. The MTC terminal repeatedly receives the same data block that is repeatedly sent by the network side by using the PDSCH according to the number of data retransmissions according to the number of data retransmissions.

In the embodiment of the present invention, the MTC terminal sends a data transmission request to the network side, so that the network side determines the number of data retransmissions corresponding to the MTC terminal according to the network state parameter of the MTC terminal in response to the data transmission request; the MTC terminal receives the network. The downlink control signaling carried by the side carries the number of times of retransmission of the data, and repeatedly receives the same data block repeatedly sent by the network side through the PDSCH according to the number of retransmissions of the data according to the number of retransmissions of the data, and the MTC terminal can effectively acquire the data. The number of retransmissions and the determination of the number of data retransmissions are flexible and accurate, thereby improving the reliability of data transmission.

FIG. 4 is a schematic structural diagram of an embodiment of a terminal device according to an embodiment of the present invention. The terminal device described in this embodiment includes:

The sending unit 401 is configured to send a data transmission request to the network side.

The first receiving unit 402 is configured to receive, by the network side, downlink control signaling that carries the number of data retransmissions corresponding to the terminal device, where the number of data retransmissions is requested by the network side to respond to the data transmission request And determining according to the network state parameter of the terminal device.

The network status parameter may include, but is not limited to, one or more of channel quality, service type, and QoS. The channel quality may be a downlink signal to noise ratio of the terminal device, and the service type of the terminal device may be reliable. The classification of the level of sexual requirements, that is, the higher priority or urgent service type, has a higher reliability requirement level, and the conventional and common service types have lower reliability requirements. Different data transmissions can also correspond to different QoS levels, that is, define the QoS required for data transmission.

Specifically, the sending unit 401 may carry the network state parameter in the data transmission request, or may be, when the first receiving unit 402 receives the request for acquiring the network state parameter of the terminal device sent by the network side, the sending unit 401 The feedback information carrying the network state parameter is sent to the network side, so that the network side obtains the channel quality of the terminal device, the reliability requirement level of the service type, and the QoS level corresponding to the data transmission, and then the network side can according to the channel quality, At least two of the requirement level of the service type and the QoS level corresponding to the data transmission determine the number of data retransmissions corresponding to the terminal device, so that the data retransmission can be flexibly and accurately determined according to the network state parameter of the terminal device. The number of times to ensure the reliability of data transmission.

Further, the network side may increase the number of data retransmissions to improve the reliability of data transmission when the channel quality of the terminal device is low, the service type has a high reliability requirement level, and the QoS level is high, and the reliability of the data transmission is When the channel quality is high, the service type requires a lower level of reliability, and the QoS level is lower, the number of data retransmissions is appropriately reduced to reduce the load on the network.

In some feasible implementation manners, the network side may also obtain the terminal capability parameter of the terminal device, and determine the number of data retransmissions corresponding to the terminal device according to the network state parameter and the terminal capability parameter of the terminal device.

The terminal capability parameter may specifically include, but is not limited to, one or more of a duplex capability, a terminal version, a supported frequency band, a PDCP parameter, and a remaining power, and the duplex capability may include HD-FDD. The terminal version is the standard version defined in the 3GPP supported by the MTC terminal, for example, the R12 version and the R13 version in the 3GPP, and the supported frequency band is, for example, Band1, Band3, etc., and the PDCP parameter is, for example, a header compressed file Profile 0, Profile 1 and the like, the remaining power is the current remaining power value of the MTC terminal, for example, 90%, 15%, and the like. The terminal capability parameter described in the embodiment of the present invention may be a capability indicator included in the message (for example, a certain capability of the terminal may be indicated by a flag bit). As part of the embodiment of the present invention, in the LTE and LTE-A systems, whether the half-duplex transmission is supported may be determined by the base station scheduler according to the capability parameter of the terminal, and in the FDD mode, the base station scheduler may perform control according to the Downlink and uplink transmissions do not occur simultaneously on the same frequency. That is to say, in the HD-FDD communication mode, the mode conversion from the transmission to the reception needs to be performed between the base station and the terminal, and the delay caused by this conversion may cause a collision between the uplink transmission and the downlink subframe. .

Specifically, the sending unit 401 may carry the network state parameter and the terminal capability parameter in the data transmission request, or may be configured to receive, by the first receiving unit 402, the network state parameter and the terminal capability parameter that are sent by the network side for acquiring the terminal device. The sending unit 401 sends the feedback information carrying the network state parameter and the terminal capability parameter to the network side, so that the network side acquires the channel quality of the terminal device, the service class to the reliability requirement level, and the QoS corresponding to the data transmission. a network state parameter such as a level, and a terminal capability parameter such as a duplex capability, a terminal version, a supported frequency band, a PDCP parameter, and a remaining power. The network side may further determine at least one of the network state parameters and the terminal capability parameter. At least one parameter determines a number of data retransmissions corresponding to the terminal device.

The second receiving unit 403 is configured to repeatedly receive, according to the number of data retransmissions, the same data block that is repeatedly transmitted by the network side by using the PDSCH according to the number of data retransmissions.

In some possible implementation manners, the specific manner in which the first receiving unit 402 receives the downlink control signaling that is sent by the network side and carries the number of data retransmissions corresponding to the terminal device is:

Receiving the DCI sent by the PDCCH on the network side, and receiving the downlink transmission data by means of synchronous HARQ, where the number of the HARQ process number in the DCI is the number of data retransmissions corresponding to the terminal device.

In some possible implementations, the first receiving unit 402 may specifically include:

The third receiving unit 4020 is configured to receive a first DCI that is sent by the network side by using a PDCCH, where a number of HARQ processes in the first DCI is used to indicate data transmission. The HARQ process used.

The fourth receiving unit 4021 is configured to receive a second DCI that is sent by the network side by using the PDCCH, where a number of HARQ processes in the second DCI is used to indicate a number of data retransmissions corresponding to the terminal device. .

or,

The third receiving unit 4020 is configured to receive the first DCI that is sent by the network side by using the PDCCH, where the number of HARQ processes in the first DCI is used to indicate the number of data retransmissions corresponding to the terminal device.

The fourth receiving unit 4021 is configured to receive a second DCI that is sent by the network side by using the PDCCH, where a number of HARQ processes in the second DCI is used to indicate a HARQ process process used for data transmission.

In some possible implementation manners, the specific manner in which the first receiving unit 402 receives the downlink control signaling that is sent by the network side and carries the number of data retransmissions corresponding to the terminal device is:

Receiving, by the network side, a DCI sent by the PDCCH, where the DCI includes a flag bit for indicating the number of times of the data retransmission.

It should be noted that the number of data retransmissions may be updated by the network side according to the network state parameter and/or the terminal capability parameter of the terminal device when receiving the data transmission request sent by the terminal device, specifically, the The data transmission request sent by the terminal device is updated, or may be updated when a predetermined number of data transmission requests are received.

Or, when the network status parameter and/or the terminal capability parameter are changed by the network side, the network status parameter and/or the terminal capability parameter of the terminal device are updated, where the change of the network status parameter may specifically include: the terminal device The change of the channel quality exceeds the preset threshold, the service type changes, and the QoS required for data transmission changes. The change of the terminal capability parameter may include: change of duplex capability, change of terminal version, supported frequency band. Changes occur, the PDCP parameters are changed, and the remaining power is higher or lower than the preset value.

Or, the network side is updated according to the network state parameter and/or the terminal capability parameter of the terminal device according to the preset frequency or the scheduled time, and the appointment time may be specifically sent by the terminal device to the network side, or may be recorded by the network side according to the network side. The change of the terminal device network state parameter and/or the terminal capability parameter is determined.

Therefore, the network side updates the number of data retransmissions to ensure the reliability of data transmission, and can effectively balance the load of the network and improve the utilization of frequency resources.

In the embodiment of the present invention, the terminal device sends a data transmission request to the network side, so that the network side determines the number of data retransmissions corresponding to the terminal device according to the network state parameter of the terminal device in response to the data transmission request; the terminal device receives the network The downlink control signaling carried by the side carries the number of times of retransmission of the data, and repeatedly receives the same data block repeatedly sent by the network side through the PDSCH according to the number of retransmissions of the data according to the number of retransmissions of the data, and the terminal device can effectively acquire the data. The number of retransmissions and the determination of the number of data retransmissions are flexible and accurate, thereby improving the reliability of data transmission.

FIG. 5 is a schematic structural diagram of an embodiment of a data transmission control system according to an embodiment of the present invention. The data transmission control system described in this embodiment includes a base station device 501 and a terminal device 502, wherein the base station device 501 includes the data transmission control device shown in FIG. 2.

In the embodiment of the present invention, the terminal device 502 sends a data transmission request to the base station device 501, and the base station device 501 determines the number of data retransmissions corresponding to the terminal device 502 according to the network state parameter of the terminal device 502 in response to the data transmission request, and sends the data retransmission number corresponding to the terminal device 502 to the terminal device 502. Sending the downlink control signaling carrying the number of retransmissions of the data; the base station device 501 repeatedly transmits the same data block to the terminal device 502 through the PDSCH according to the number of data retransmissions, and the terminal device 502 repeatedly receives the same data block according to the number of retransmissions of the data. Therefore, the base station device can flexibly and accurately determine the number of data retransmissions, and effectively notify the terminal device of the number of data retransmissions, thereby improving the reliability of data transmission.

FIG. 6 is a schematic structural diagram of an embodiment of a data transmission control device according to an embodiment of the present invention. The data transmission control device described in this embodiment includes a transceiver 601, a processor 602, and a memory 603. The processor 602 is connected to the transceiver 601 and the memory 603 via a bus.

The transceiver 601 may be a radio frequency receiver or a radio frequency chip for transmitting and receiving signals 605 through the antenna 604. Specifically, the transceiver 601 may include an integrated transmit channel (Transmitter, TX) and a receiver (Receiver, RX). The processor 602 may be a baseband processor, a baseband chip, a digital signal processor (DSP), or a system on chip (SOC) including a baseband processor and an application processor. Wait.

The foregoing memory 603 is configured to store a set of program codes, and the processor 602 is configured to call the program code stored in the memory 603, and perform the following operations:

The transceiver 601 is configured to receive a data transmission request sent by the MTC terminal.

The processor 602 is configured to determine, according to the network state parameter of the MTC terminal, a number of data retransmissions corresponding to the MTC terminal, in response to the data transmission request.

The transceiver 601 is further configured to send, to the MTC terminal, downlink control signaling that carries the number of data retransmissions.

The transceiver 601 is further configured to repeatedly send the same data block to the MTC terminal through the PDSCH according to the number of data retransmissions.

In some possible implementations, the transceiver 601 is specifically configured to:

The value of the process number information field of the HARQ process number in the DCI is set as the number of data retransmissions.

And transmitting, by the PDCCH, the DCI to the MTC terminal, and instructing the MTC terminal to receive downlink transmission data by using a synchronous HARQ.

In some possible implementations, the transceiver 601 is specifically configured to:

The first DCI is sent to the MTC terminal by using a PDCCH, and the number of HARQ processes in the first DCI is used to indicate a HARQ process process used for data transmission.

The second DCI is sent to the MTC terminal by using the PDCCH, and the number of HARQ processes in the second DCI is used to indicate the number of data retransmissions.

or,

The first DCI is sent to the MTC terminal by using the PDCCH, and the number of HARQ processes in the first DCI is used to indicate the number of data retransmissions.

The second DCI is sent to the MTC terminal by using the PDCCH, and the HARQ process number process number information field in the second DCI is used to indicate the HARQ process process used for data transmission.

In some possible implementations, the transceiver 601 is specifically configured to:

The DCI is transmitted to the MTC terminal through a PDCCH, and the DCI includes a flag bit for indicating the number of times of the data retransmission.

In some possible implementations, the network state parameter includes one or more of channel quality, service type, and quality of service QoS, and the processor 602 is specifically configured to:

And responding to the data transmission request, acquiring a channel quality of the MTC terminal, a requirement level of the service type to reliability, and a QoS level corresponding to the data transmission.

Determining, according to the channel quality, the required level of reliability of the service type, and the QoS level corresponding to the data transmission, the number of data retransmissions corresponding to the MTC terminal.

In some possible implementations, the processor 602 is further configured to acquire a terminal capability parameter of the MTC terminal, and determine the number of data retransmissions according to the network state parameter and the terminal capability parameter.

In some implementations, the processor 602 is further configured to: according to the network state parameter and/or the terminal capability parameter of the MTC terminal, when the transceiver 601 receives the data transmission request sent by the MTC terminal Updating the number of data retransmissions, or for updating the data according to network state parameters and/or terminal capability parameters of the MTC terminal when the network state parameter and/or the terminal capability parameter are changed. The number of transmissions is used to update the number of data retransmissions according to the network state parameter and/or the terminal capability parameter of the MTC terminal according to a preset frequency or at an agreed time.

In a specific implementation, the transceiver 601, the processor 602, and the memory 603, which are described in the embodiments of the present invention, may be implemented in the first embodiment of the data transmission control method provided by the embodiment of the present invention. An implementation manner described in an embodiment of a data transmission control apparatus provided by an embodiment of the present invention is not described herein.

In the embodiment of the present invention, the transceiver 601 receives the data transmission request sent by the MTC terminal, and the processor 602 determines, according to the network transmission parameter of the MTC terminal, the number of data retransmissions corresponding to the MTC terminal, and the transceiver 601 The MTC terminal sends the downlink control signaling carrying the number of retransmissions of the data, and repeatedly sends the same data block to the MTC terminal through the PDSCH according to the number of data retransmissions, so that the number of data retransmissions can be flexibly and accurately determined, and effectively The number of data retransmissions is notified to the MTC terminal to improve the reliability of data transmission.

FIG. 7 is a schematic structural diagram of an embodiment of a terminal device according to an embodiment of the present invention. The terminal device described in this embodiment includes: a transceiver 701, a processor 702, and a memory 703. The processor 702 is connected to the transceiver 701 and the memory 703 via a bus.

The transceiver 701 may be a radio frequency receiver or a radio frequency chip for transmitting and receiving signals 705 through the antenna 704. Specifically, the transceiver 701 may include a transmit channel TX and a receiver RX integrated together. The processor 702 may be a baseband processor, a baseband chip, a DSP, or an SOC including a baseband processor and an application processor. The above memory 703 is a memory device of the terminal device for storing programs and data. It can be understood that the memory 703 herein may be a high-speed RAM memory, or may be a non-volatile memory, such as at least one disk memory; optionally, at least one of the processors 702 may be located away from the foregoing processor 702. Storage device.

The memory 703 is configured to store a set of program codes, and the processor 702 calls the program code stored in the memory 703 to perform the following operations:

The transceiver 701 is configured to send a data transmission request to the network side.

The transceiver 701 is further configured to receive, by the network side, downlink control signaling that carries the number of data retransmissions corresponding to the terminal device, where the number of data retransmissions is sent by the network side to the data transmission The request is determined according to a network status parameter of the terminal device.

The processor 702 is configured to repeatedly receive, by the transceiver 701, the same data block that is repeatedly sent by the network side through the PDSCH according to the number of data retransmissions according to the number of data retransmissions.

In some possible implementations, the transceiver 701 is specifically configured to:

Receiving the DCI sent by the PDCCH on the network side, and receiving the downlink transmission data by means of synchronous HARQ, where the number of the HARQ process number in the DCI is the number of data retransmissions corresponding to the terminal device.

In some possible implementations, the transceiver 701 is specifically configured to:

Receiving, by the network side, a first DCI sent by the PDCCH, where the number of HARQ processes in the first DCI is used to indicate a HARQ process process used for data transmission.

Receiving, by the network side, the second DCI sent by the PDCCH, where the process number information field of the HARQ process in the second DCI is used to indicate the number of data retransmissions corresponding to the terminal device.

or,

Receiving, by the network side, a first DCI sent by using a PDCCH, and the HARQ in the first DCI The process number information field is used to indicate the number of data retransmissions corresponding to the terminal device.

Receiving, by the network side, a second DCI sent by the PDCCH, where a number of HARQ processes in the second DCI is used to indicate a HARQ process process used for data transmission.

In some possible implementations, the transceiver 701 is specifically configured to:

Receiving, by the network side, a DCI sent by the PDCCH, where the DCI includes a flag bit for indicating the number of times of the data retransmission.

In some possible implementations, the network state parameter includes one or more of channel quality, service type, and quality of service QoS, and the network side responds to the data transmission request according to a network state of the terminal device. The specific method for determining the number of retransmissions of the data is as follows:

And responding to the data transmission request, acquiring a channel quality of the terminal device, a requirement level of reliability of the service type, and a QoS level corresponding to the data transmission.

Determining the number of data retransmissions according to at least two of the channel quality, the required level of reliability of the service type, and the QoS level corresponding to the data transmission.

In some feasible implementation manners, the network side acquires a terminal capability parameter of the terminal device, and determines the number of data retransmissions according to the network state parameter and the terminal capability parameter.

In some feasible implementation manners, the number of data retransmissions is updated by the network side according to the network state parameter and/or the terminal capability parameter of the terminal device when receiving the data transmission request sent by the terminal device, or And being updated by the network side according to the network state parameter and/or the terminal capability parameter of the terminal device, or by the network side, when the network state parameter and/or the terminal capability parameter are changed. The frequency is set or updated at the appointed moment according to the network state parameter and/or the terminal capability parameter of the terminal device.

In a specific implementation, the transceiver 701, the processor 702, and the memory 703, which are described in the embodiments of the present invention, may be implemented in the second embodiment of the data transmission control method provided by the embodiment of the present invention. An implementation manner described in an embodiment of a terminal device provided by an embodiment of the present invention is not described herein.

In the embodiment of the present invention, the transceiver 701 sends a data transmission request to the network side, so that the network side determines the number of data retransmissions corresponding to the MTC terminal according to the network state parameter of the MTC terminal, and the transceiver 701 receives the data transmission request. The network side sends the number of times the data is retransmitted. And the processor 702 repeatedly receives the same data block repeatedly transmitted by the network side through the PDSCH according to the number of times of the data retransmission according to the number of data retransmissions, and the terminal device can effectively obtain the number of data retransmissions, and The determination of the number of data retransmissions is flexible and accurate, thereby improving the reliability of data transmission.

The units in all the embodiments of the present invention may be implemented by a general-purpose integrated circuit, such as a CPU (Central Processing Unit), or by an ASIC (Application Specific Integrated Circuit).

The steps in the method of the embodiment of the present invention may be sequentially adjusted, merged, and deleted according to actual needs.

The units in the terminal in the embodiment of the present invention may be combined, divided, and deleted according to actual needs.

One of ordinary skill in the art can understand that all or part of the process of implementing the foregoing embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The data transmission control method, device, system and related equipment provided by the embodiments of the present invention are described in detail. The principles and implementation manners of the present invention are described in the following. The description of the above embodiments is only The method for understanding the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in specific embodiments and application scopes. The description should not be construed as limiting the invention.

Claims (30)

A data transmission control method, comprising: a data transmission request sent by the receiver type communication MTC terminal; Determining, according to the network state parameter of the MTC terminal, a number of data retransmissions corresponding to the MTC terminal, in response to the data transmission request; Transmitting downlink control signaling carrying the number of data retransmissions to the MTC terminal; And transmitting the same data block to the MTC terminal through the physical downlink shared channel PDSCH according to the number of data retransmissions. The method according to claim 1, wherein the sending, to the MTC terminal, downlink control signaling carrying the number of data retransmissions includes: The value of the hybrid automatic repeat request HARQ process number process number information field in the downlink control information DCI is set as the number of data retransmission times, and the DCI is sent to the MTC terminal through the physical downlink control channel PDCCH, and the indication is The MTC terminal receives downlink transmission data by means of synchronous HARQ. The method according to claim 1, wherein the sending, to the MTC terminal, downlink control signaling carrying the number of data retransmissions includes: Transmitting, by the PDCCH, the first DCI to the MTC terminal, where the number of HARQ processes in the first DCI is used to indicate a HARQ process process used for data transmission; Transmitting, by the PDCCH, a second DCI to the MTC terminal, where a number of HARQ processes in the second DCI is used to indicate the number of data retransmissions; or, Transmitting, by the PDCCH, the first DCI to the MTC terminal, where the number of HARQ processes in the first DCI is used to indicate the number of data retransmissions; The second DCI is sent to the MTC terminal by using the PDCCH, and the HARQ process number process number information field in the second DCI is used to indicate the HARQ process process used for data transmission. The method according to claim 1, wherein the sending, to the MTC terminal, downlink control signaling carrying the number of data retransmissions includes: The DCI is transmitted to the MTC terminal through a PDCCH, and the DCI includes a flag bit for indicating the number of times of the data retransmission. The method according to any one of claims 1 to 4, wherein the network state parameter comprises one or more of channel quality, service type and quality of service QoS, and the response to the data transmission request Determining, according to the network state parameter of the MTC terminal, the number of data retransmissions corresponding to the MTC terminal, including: And responding to the data transmission request, acquiring a channel quality of the MTC terminal, a requirement level of reliability of the service type, and a QoS level corresponding to the data transmission; Determining, according to the channel quality, the required level of reliability of the service type, and the QoS level corresponding to the data transmission, the number of data retransmissions corresponding to the MTC terminal. The method according to any one of claims 1 to 5, further comprising: Obtaining a terminal capability parameter of the MTC terminal, and determining the number of data retransmissions according to the network state parameter and the terminal capability parameter. The method of claim 6 further comprising: Updating the number of data retransmissions according to the network state parameter and/or the terminal capability parameter of the MTC terminal when receiving the data transmission request sent by the MTC terminal; or, Updating the number of data retransmissions according to the network state parameter and/or the terminal capability parameter of the MTC terminal when the network state parameter and/or the terminal capability parameter are changed; or, The number of data retransmissions is updated according to the network state parameter and/or the terminal capability parameter of the MTC terminal according to a preset frequency or at an agreed time. A data transmission control device, comprising: a receiving unit, configured to receive a data transmission request sent by the MTC terminal; a processing unit, configured to determine, according to the network state parameter of the MTC terminal, a number of data retransmissions corresponding to the MTC terminal, in response to the data transmission request; a first sending unit, configured to send, to the MTC terminal, downlink control signaling that carries the number of data retransmissions; The first sending unit is further configured to repeatedly send the same data block to the MTC terminal through the PDSCH according to the number of data retransmissions. The apparatus according to claim 8, wherein the first transmitting unit comprises: a first setting unit, configured to set a value of a process number information field of a HARQ process number in the DCI to the number of data retransmissions; And a second sending unit, configured to send the DCI to the MTC terminal by using a PDCCH, and instruct the MTC terminal to receive downlink transmission data by using a synchronous HARQ manner. The device according to claim 8, wherein the specific manner in which the first sending unit sends the downlink control signaling carrying the number of data retransmissions to the MTC terminal is: Transmitting, by the PDCCH, the first DCI to the MTC terminal, where the number of HARQ processes in the first DCI is used to indicate a HARQ process process used for data transmission; Transmitting, by the PDCCH, a second DCI to the MTC terminal, where a number of HARQ processes in the second DCI is used to indicate the number of data retransmissions; or, Transmitting, by the PDCCH, the first DCI to the MTC terminal, where the number of HARQ processes in the first DCI is used to indicate the number of data retransmissions; The second DCI is sent to the MTC terminal by using the PDCCH, and the HARQ process number process number information field in the second DCI is used to indicate the HARQ process process used for data transmission. The device according to claim 8, wherein the specific manner in which the first sending unit sends the downlink control signaling carrying the number of data retransmissions to the MTC terminal is: The DCI is transmitted to the MTC terminal through a PDCCH, and the DCI includes a flag bit for indicating the number of times of the data retransmission. The device according to any one of claims 8 to 11, wherein the network state parameter comprises one or more of channel quality, service type and quality of service QoS, and the processing unit comprises: An acquiring unit, configured to obtain, according to the data transmission request, a channel quality of the MTC terminal, a requirement level of the service type to reliability, and a QoS level corresponding to the data transmission; And a determining unit, configured to determine, according to the channel quality, the required level of reliability of the service type, and the QoS level corresponding to the data transmission, the number of data retransmissions corresponding to the MTC terminal. Apparatus according to any one of claims 8 to 12, wherein The processing unit is further configured to acquire a terminal capability parameter of the MTC terminal, and determine the number of data retransmissions according to the network state parameter and the terminal capability parameter. The device according to claim 13, further comprising: An update unit, configured to update the data retransmission times according to network state parameters and/or terminal capability parameters of the MTC terminal when receiving the data transmission request sent by the MTC terminal, or for using the network status When the parameter and/or the terminal capability parameter are changed, the number of data retransmissions is updated according to the network state parameter and/or the terminal capability parameter of the MTC terminal, or is used according to the preset frequency or at the appointed time. The network state parameter and/or the terminal capability parameter of the MTC terminal update the number of data retransmissions. A base station apparatus comprising the data transmission control apparatus according to any one of claims 8 to 14. A data transmission control method, comprising: The MTC terminal sends a data transmission request to the network side; The MTC terminal receives downlink control signaling that is sent by the network side and carries the number of data retransmissions corresponding to the MTC terminal, where the number of data retransmissions is responded to by the network side by the data transmission request, according to the The network status parameter of the MTC terminal is determined; The MTC terminal repeatedly receives the same data block that the network side repeatedly transmits through the PDSCH according to the number of data retransmissions according to the number of data retransmissions. The method according to claim 16, wherein the MTC terminal receives the downlink control signaling that is sent by the network side and carries the number of data retransmissions corresponding to the MTC terminal, and includes: The MTC terminal receives the DCI sent by the network side through the PDCCH, and receives the downlink transmission data by means of synchronous HARQ, where the value of the process number information field of the HARQ process in the DCI is a data retransmission corresponding to the MTC terminal. frequency. The method according to claim 16, wherein the MTC terminal receives the downlink control signaling that is sent by the network side and carries the number of data retransmissions corresponding to the MTC terminal, and includes: The MTC terminal receives the first DCI sent by the network side through the PDCCH, and the number of HARQ processes in the first DCI is used to indicate the HARQ process process used for data transmission; The MTC terminal receives the second DCI that is sent by the network side by using the PDCCH, and the number of HARQ processes in the second DCI is used to indicate the number of data retransmissions corresponding to the MTC terminal; or, The MTC terminal receives the first DCI that is sent by the network side through the PDCCH, and the number of HARQ processes in the first DCI is used to indicate the number of data retransmissions corresponding to the MTC terminal; The MTC terminal receives the second DCI sent by the network side through the PDCCH, and the HARQ process number process number information field in the second DCI is used to indicate the HARQ process process used for data transmission. The method according to claim 16, wherein the MTC terminal receives the downlink control signaling that is sent by the network side and carries the number of data retransmissions corresponding to the MTC terminal, and includes: The MTC terminal receives the DCI sent by the network side through the PDCCH, and the DCI includes a flag bit for indicating the number of times of the data retransmission. The method according to any one of claims 16 to 19, wherein the network state parameter comprises one or more of channel quality, service type and quality of service QoS, and the network side responds to the data The specific manner of determining the number of retransmissions of the data according to the network state parameter of the MTC terminal is: And responding to the data transmission request, acquiring a channel quality of the MTC terminal, a requirement level of reliability of the service type, and a QoS level corresponding to the data transmission; Determining the number of data retransmissions according to at least two of the channel quality, the required level of reliability of the service type, and the QoS level corresponding to the data transmission. The method according to any one of claims 16 to 20, further comprising: The network side acquires a terminal capability parameter of the MTC terminal, and determines the number of data retransmissions according to the network state parameter and the terminal capability parameter. The method of claim 21 wherein The number of data retransmissions is updated by the network side according to the network state parameter and/or the terminal capability parameter of the MTC terminal when receiving the data transmission request sent by the MTC terminal, or is performed by the network side. When the network state parameter and/or the terminal capability parameter are changed, the network state parameter and/or the terminal capability parameter of the MTC terminal are updated, or the network side according to the preset frequency or at the appointed time The network state parameters and/or terminal capability parameters of the MTC terminal are updated. A terminal device, comprising: a sending unit, configured to send a data transmission request to the network side; The first receiving unit is configured to receive, by the network side, downlink control signaling that carries the number of data retransmissions corresponding to the terminal device, where the number of data retransmissions is responded to by the network side by the data transmission request, Determining according to network state parameters of the terminal device; And a second receiving unit, configured to repeatedly receive, according to the number of data retransmissions, the same data block that is repeatedly sent by the network side by using the PDSCH according to the number of data retransmissions. The device according to claim 23, wherein the first receiving unit receives the downlink control signaling that is sent by the network side and carries the number of data retransmissions corresponding to the terminal device: Receiving the DCI sent by the PDCCH on the network side, and receiving the downlink transmission data by means of synchronous HARQ, where the number of the HARQ process number in the DCI is the number of data retransmissions corresponding to the terminal device. The apparatus according to claim 23, wherein the first receiving unit comprises: a third receiving unit, configured to receive a first DCI sent by the network side by using a PDCCH, where a number of HARQ processes in the first DCI is used to indicate a HARQ process process used for data transmission; a fourth receiving unit, configured to receive a second DCI that is sent by the network side by using the PDCCH, where a number of HARQ processes in the second DCI is used to indicate a number of data retransmissions corresponding to the terminal device; or, a third receiving unit, configured to receive a first DCI that is sent by the network side by using a PDCCH, where a number of HARQ processes in the first DCI is used to indicate a number of data retransmissions corresponding to the terminal device; And a fourth receiving unit, configured to receive a second DCI that is sent by the network side by using the PDCCH, where a number of HARQ processes in the second DCI is used to indicate a HARQ process process used for data transmission. The device according to claim 23, wherein the first receiving unit receives the downlink control signaling that is sent by the network side and carries the number of data retransmissions corresponding to the terminal device: Receiving, by the network side, a DCI sent by the PDCCH, where the DCI includes a flag bit for indicating the number of times of the data retransmission. The device according to any one of claims 23 to 26, wherein the network state parameter comprises one or more of channel quality, service type and quality of service QoS, and the network side responds to the data The specific manner of determining the number of retransmissions of the data according to the network state parameter of the terminal device is: And responding to the data transmission request, acquiring a channel quality of the terminal device, a requirement level of reliability of the service type, and a QoS level corresponding to the data transmission; Determining the number of data retransmissions according to at least two of the channel quality, the required level of reliability of the service type, and the QoS level corresponding to the data transmission. Apparatus according to any one of claims 23 to 27, wherein The network side acquires a terminal capability parameter of the terminal device, and determines the number of data retransmissions according to the network state parameter and the terminal capability parameter. The device according to claim 28, characterized in that The number of data retransmissions is updated by the network side according to the network state parameter and/or the terminal capability parameter of the terminal device when receiving the data transmission request sent by the terminal device, or is performed by the network side. When the network status parameter and/or the terminal capability parameter are changed, the network status parameter and/or the terminal capability parameter of the terminal device are updated, or the network side according to the preset frequency or at the appointed time The network status parameter and/or terminal capability parameter update of the terminal device. A data transmission control system comprising the base station device according to claim 15 and the terminal device according to any one of claims 23 to 29.

Images