Data transmission method and apparatus

Abstract

The application relates to the field of wireless communication, in particular to a data transmission method and device. A data transmission method comprises the following steps: performing first uplink authorization on a terminal device in a pre-scheduling period, wherein the first uplink authorization is used for determining a first uplink data transmission configuration of the terminal device; receiving uplink data sent by the terminal device within the range of the first uplink data transmission configuration, and stopping sending downlink data to the terminal device; stopping receiving uplink data of the terminal device outside the range of the first uplink data transmission configuration, and resuming sending downlink data to the terminal device. The method reduces the opportunity of the terminal device actively sending a preamble to a network device to request uplink scheduling resources, and reduces the error code caused by the conflict of simultaneous uplink and downlink data transmission.

Description

[0001] The present application relates to the field of wireless communication, in particular to a data transmission method and device.

[0002] In some communication systems, terminal devices are designed in half-duplex mode, i.e. the uplink channel and the downlink channel of the terminal device cannot transmit data at the same time.

[0003] When the terminal device has uplink data to be sent, it needs to send a preamble to the network side to apply for uplink resources. However, the terminal device cannot detect whether the downlink channel is being occupied during the process of sending the preamble. The network device also cannot determine whether the terminal device is receiving downlink data according to the preamble reported by the terminal device, so it is very likely that the terminal device and the network device will send data at the same time, which will inevitably lead to uplink and downlink data transmission errors and data loss.

[0004] Therefore, the embodiments of the present application provide a data transmission method and device, in which the network device pre-authorizes the uplink data of the terminal device, instructs the terminal device to report the uplink data within a specified configuration range, and stops sending downlink data to the terminal device within the configuration range, thereby eliminating the data transmission errors caused by uplink and downlink data conflicts.

[0005] In a first aspect, the embodiments of the present application provide a data transmission method, which is applied to a network device, and the method comprises:

[0006] performing first uplink authorization to the terminal device in a pre-scheduling period, wherein the first uplink authorization is used to determine a first uplink data transmission configuration of the terminal device;

[0007] receiving uplink data sent by the terminal device within the range of the first uplink data transmission configuration, and stopping sending downlink data to the terminal device;

[0008] stopping receiving uplink data of the terminal device outside the range of the first uplink data transmission configuration, and resuming sending downlink data to the terminal device.

[0009] Optionally, the pre-scheduling period is determined according to a physical random access channel NPRACH period of the terminal device.

[0010] Optionally, the first uplink authorization performed to the terminal device is used to determine the first uplink data transmission configuration of the terminal device, and the first uplink authorization comprises:​​​

[0011] sending first uplink authorization information to the terminal device, the first uplink authorization information including time, frequency band resource, data block size, modulation mode and repetition number for allowing the terminal device to send uplink data;

[0012] The time, frequency band resource, data block size, modulation mode and repetition number for sending uplink data are used to jointly determine the first uplink data transmission configuration of the terminal device.

[0013] Optionally, the sending of the first uplink authorization information to the terminal device comprises:

[0014] encrypting the first uplink authorization information by the identity information of the terminal device;

[0015] The encrypted first uplink authorization information can be decrypted only by the identity information of the terminal device.

[0016] Optionally, after receiving the uplink data sent by the terminal device, the method further comprises:

[0017] parsing the uplink data to obtain first application layer data and a buffer status report (BSR) contained in the uplink data;

[0018] determining whether to perform second uplink authorization on the terminal device according to the BSR in the uplink data.

[0019] Optionally, the determining whether to perform second uplink authorization on the terminal device according to the BSR in the uplink data comprises:

[0020] when the BSR in the uplink data is not zero, determining second uplink authorization information for representing second uplink data transmission configuration according to the BSR, and performing second uplink authorization on the terminal device by the second uplink authorization information, wherein the BSR includes data block size of second application layer data to be reported by the terminal device;

[0021] when the BSR reported by the terminal device is zero, not performing second uplink authorization on the terminal device in the current pre-scheduling period.

[0022] Optionally, the method further comprises:

[0023] when there are multiple terminal devices connected, determining priority order of the terminal devices according to whether the terminal devices report BSR;

[0024] performing second uplink authorization on the terminal devices reporting BSR preferentially according to the priority order.

[0025] Optionally, the method further comprises:

[0026] determining an NPRACH period of the terminal device;

[0027] sending downlink data to the terminal device out of the NPRACH period of the terminal device.

[0028] In a second aspect, an embodiment of the present application provides a data transmission method, the method being applied to a terminal device, and the method comprising:

[0029] determining a first uplink data transmission configuration according to a first uplink grant performed by a network device in a pre-scheduling period;

[0030] sending uplink data to the network device within a range of the first uplink data transmission configuration, and stopping receiving downlink data sent by the network device;

[0031] stopping sending uplink data to the network device out of the range of the first uplink data transmission configuration, and resuming receiving the downlink data sent by the network device.

[0032] Optionally, the determining the first uplink data transmission configuration according to the first uplink grant performed by the network device in the pre-scheduling period comprises:

[0033] obtaining first uplink grant information sent by the network device;

[0034] determining a time, a frequency band resource, a data block size, a modulation mode and a repetition number for sending uplink data contained in the first uplink grant information;

[0035] determining the first uplink data transmission configuration according to the time, the frequency band resource, the data block size, the modulation mode and the repetition number for sending uplink data.

[0036] Optionally, the determining the time, the frequency band resource, the data block size, the modulation mode and the repetition number for sending uplink data contained in the first uplink grant information comprises:

[0037] decrypting the first uplink grant information through identity information of the terminal device;

[0038] obtaining the time, the frequency band resource, the data block size, the modulation mode and the repetition number for sending uplink data from the decrypted first uplink grant information.

[0039] Optionally, the sending uplink data to the network device comprises:

[0040] The uplink data sent to the network device contains first application layer data and a buffer status report (BSR), and the BSR includes a data block size of second application layer data to be reported by the terminal device.

[0041] The BSR is used by the network device to determine whether to perform a second uplink authorization on the terminal device.

[0042] Optionally, the BSR is used by the network device to determine whether to perform a second uplink authorization on the terminal device, including:

[0043] When the BSR is not zero, the BSR is used to instruct the network device to determine second uplink authorization information used to represent a second uplink data transmission configuration, and to perform a second uplink authorization on the terminal device through the second uplink authorization information.

[0044] When the BSR is zero, the BSR is used to instruct the network device to no longer perform a second uplink authorization on the terminal device within a current pre-scheduling period.

[0045] Optionally, the method further includes:

[0046] Receiving downlink data sent by the network device outside a physical random access channel (NPRACH) period.

[0047] In a third aspect, an embodiment of the present application provides a data transmission device, which is applied to a network device, and the device includes:

[0048] An authorization module performs a first uplink authorization on a terminal device in a pre-scheduling period, and the first uplink authorization is used to determine a first uplink data transmission configuration of the terminal device.

[0049] A receiving module receives uplink data sent by the terminal device within a range of the first uplink data transmission configuration, and stops sending downlink data to the terminal device.

[0050] A sending module stops sending uplink authorization and receiving uplink data of the terminal device outside the range of the first uplink data transmission configuration, and resumes sending downlink data to the terminal device.

[0051] In a fourth aspect, an embodiment of the present application provides a data transmission device, which includes:

[0052] At least one processor; and

[0053] At least one memory connected with the processor in communication, wherein:

[0054] The memory stores program instructions executable by the processor, and the processor invoking the program instructions can execute the method of any one of the first aspect.

[0055] In a fifth aspect, an embodiment of the present application provides a data transmission device, the device being applied to a terminal device, the device comprising:

[0056] A determining module, configured to determine a first uplink data transmission configuration according to a first uplink grant performed by a network device in a pre-scheduling period;

[0057] A sending module, configured to send uplink data to the network device within the range of the first uplink data transmission configuration, and stop receiving downlink data sent by the network device;

[0058] A receiving module, configured to stop sending uplink data to the network device outside the range of the first uplink data transmission configuration, and resume receiving downlink data sent by the network device.

[0059] In a sixth aspect, an embodiment of the present application provides a data transmission device, comprising:

[0060] At least one processor; and

[0061] At least one memory in communication with the processor, wherein:

[0062] The memory stores program instructions executable by the processor, and the processor invoking the program instructions can execute the method of any one of the second aspect.

[0063] In a seventh aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium comprising stored programs, wherein when the programs run, the device where the computer readable storage medium is located executes the method of any one of the first aspect or the second aspect.

[0064] Through the above scheme, the opportunities of the terminal device actively sending a preamble to the network device to apply for uplink scheduling resources are reduced, and the error codes caused by the conflict of simultaneous transmission of uplink and downlink data are reduced. BRIEF DESCRIPTION OF DRAWINGS

[0065] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0066] Figure 1 A structural schematic diagram of a data transmission system provided by an embodiment of the present application;

[0067] Figure 2 A flowchart of a data transmission method provided in an embodiment of the present invention;

[0068] Figure 3 A flowchart of another data transmission method provided in an embodiment of the present invention;

[0069] Figure 4 A flowchart of another data transmission method provided in an embodiment of the present invention;

[0070] Figure 5 This is a schematic diagram of the structure of a data transmission device provided in an embodiment of the present invention;

[0071] Figure 6 This is a schematic diagram of another data transmission device provided in an embodiment of the present invention;

[0072] Figure 7 This is a schematic diagram of a data transmission device provided in an embodiment of the present invention.

Detailed Implementation Methods

[0073] To better understand the technical solution of the present invention, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0074] It should be understood that the described embodiments are merely some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0075] In some communication systems, such as Narrow Band Internet of Things (NB-IoT) systems, to reduce the complexity and cost of terminal devices, they are often designed as half-duplex systems, meaning that the uplink and downlink channels of the terminal device cannot transmit data simultaneously. When a terminal device needs to send uplink data, it needs to request uplink data transmission resources from the network side by sending a preamble request. However, when the terminal device sends the preamble request, it does not monitor whether the downlink channel is occupied. Sending uplink data at this time will cause a transmission conflict with the downlink data, resulting in data transmission failure. This leads to more data retransmissions, increasing system load, reducing system speed, and increasing system latency. It not only consumes scarce spectrum resources but also increases the power consumption of the terminal device, significantly reducing its battery life.

[0076] The embodiment of the present application uses a network device to authorize uplink data of a terminal device, instructs the terminal device to send uplink data in a specified time and channel range, and stops the network device from sending downlink data to the terminal device in the range, so as to avoid interference between uplink and downlink data of the terminal device.

[0077] To avoid interference between uplink and downlink data of the terminal device in a data transmission process, the embodiment of the present application first provides a data transmission system, as shown in the figure. Figure 1 The data transmission system includes a network device 101 and a terminal device 102, and the terminal device 102 is in communication connection with the network device 101.

[0078] The network device 101 is used to send downlink data to the connected terminal device 102 in a communication range, and receives uplink data reported by the terminal device 102 at irregular time intervals, so as to realize data interaction between the network side and the terminal device 102 side. To avoid the terminal device 102 from sending uplink data at the same time when the network device 101 sends downlink data to the terminal device 102, causing uplink and downlink data transmission conflict, the network device 101 needs to pre-schedule uplink data transmission of the terminal device 102. The network device 101 can be implemented as a base station.

[0079] Specifically, the network device 101 sends uplink authorization information to the terminal device 102 to be authorized, so as to authorize uplink data of the terminal device 102. The uplink authorization information specifically defines uplink data transmission configuration of the terminal device 102 for sending uplink data. That is, the terminal device 102 is authorized to send uplink data in the specified uplink data transmission configuration range. Since the terminal device 102 is pre-authorized by the network device 101, the network device 101 also knows the uplink data transmission configuration range of the terminal device 102 for sending uplink data, so the network device 101 stops sending downlink data to the terminal device 102 in the specified data transmission configuration range, so as to avoid uplink and downlink data conflict.

[0080] The terminal device 102 is used to receive downlink data sent by the network device 101, and reports uplink data to the network device 101 when necessary, so as to realize data interaction between the terminal device 102 side and the network side. To avoid sending uplink data to the network device 101 at the same time when receiving downlink data sent by the network device 101, causing uplink and downlink data transmission conflict, the terminal device 102 needs to send uplink data to the network device 101 in the specified uplink data transmission configuration range according to the authorization of the network device 101. The terminal device 102 can be implemented as an intelligent street lamp, an intelligent water meter, an intelligent gas meter, an intelligent smoke sensor, and the like NB-IoT terminal.

[0081] Specifically, the terminal device 102 receives the uplink authorization information sent by the network device 101, and obtains the uplink data transmission configuration by analyzing the uplink authorization information. The uplink data is sent within the uplink data transmission configuration range specified by the network device 101, and since the network device 101 will not send downlink data within the uplink data transmission configuration range, the uplink and downlink data will not conflict.

[0082] In combination with Figure 1 The data transmission system shown in the embodiment of the present application provides a data transmission method, which is applied to the network device 101, as shown in the method. Figure 2 The processing steps of the method include:

[0083] 201. The uplink authorization is performed on the terminal device in the pre-scheduling period, and the uplink authorization is used to determine the uplink data transmission configuration of the terminal device.

[0084] Specifically, when the pre-scheduling period is reached, the first uplink authorization information is sent to the terminal device to be authorized to perform the first uplink authorization on the terminal device. The first uplink authorization information includes the time, frequency band resource, data block size, modulation mode, and repetition number of the terminal device for sending uplink data. The time, frequency band resource, data block size, modulation mode, and repetition number of the terminal device for sending uplink data are used to jointly determine the first uplink transmission configuration of the terminal device.

[0085] The network device can only authorize one terminal device at a time when sending the first uplink authorization information. At the same time, the network device also needs to encrypt the first uplink authorization information sent by the terminal device to be authorized through the identity information of the terminal device to be authorized. When the terminal device to be authorized receives the first uplink authorization information, it needs to decrypt the first uplink authorization information through its own identity information to obtain the content contained therein. Other terminal devices that are not authorized cannot decrypt the first authorization information to obtain the specific content therein even if they receive the first authorization information.

[0086] Optionally, the pre-scheduling period can be determined according to the Narrow-band Physical Random Access Channel (NPRACH) period of the terminal device.

[0087] 202. Within the range of the uplink data transmission configuration, the uplink data sent by the terminal device is received, and the sending of the downlink data to the terminal device is stopped.

[0088] Specifically, the uplink data is received within the specified time and frequency band according to the range of the first uplink transmission configuration, and the received uplink data is determined as the uplink data reported by the terminal device that has completed the authorization. At the same time, the sending of the downlink data to the terminal device within the range of the first uplink transmission configuration is stopped.

[0089] If the uplink data is not received within the range of the uplink transmission configuration, it is determined that the authorization to the terminal device fails, and the terminal device needs to be authorized again until the uplink data sent by the terminal device is received.

[0090] After receiving the uplink data sent by the terminal device, the network device needs to parse the uplink data by using a demodulation mode corresponding to the modulation mode specified in the first authorization information, to obtain the first application layer data and the buffer status report (BSR) contained therein. The first application layer data is the information actually needed to be reported by the terminal device, and the BSR is the reporting situation of the terminal device for the first application layer data.

[0091] Specifically, when the data block size configured by the network device for the terminal device in the first uplink authorization information is insufficient to support the terminal device to report all the information actually needed to be reported, the terminal device writes the size of the remaining information needed to be reported in the reported BSR. The BSR at this time is used to instruct the network device to authorize the terminal device for the second uplink according to the size of the remaining information needed to be reported by the terminal device, and to configure appropriate uplink resources for the terminal device to report the remaining second application layer data.

[0092] The process of authorizing the terminal device for the second uplink is consistent with the first uplink authorization process. By sending the encrypted second uplink authorization information to the terminal device, the terminal device is notified to perform uplink data transmission by using the data block size configured for it under the specified time, frequency band resource, modulation mode and repetition number.

[0093] When the data block size configured by the network device for the terminal device in the first uplink authorization information is sufficient to support the terminal device to complete the reporting of all the information, the terminal device marks 0 in the reported BSR and reports it to the network device. According to the received BSR being 0, the network device determines that the terminal device will not be authorized for the second uplink in the current pre-scheduling period.

[0094] 203, stop receiving the uplink data of the terminal device outside the range of the uplink transmission configuration, and resume sending the downlink data to the terminal device.

[0095] Specifically, when the range of the first uplink transmission configuration or the range of the second uplink transmission configuration is exceeded, the terminal device will not report data again. At this time, the reception of the uplink data sent by the terminal device according to the range of the uplink transmission configuration is stopped, and the sending of the downlink data to the terminal device is resumed.

[0096] The embodiment of the present application configures the terminal device with uplink pre-scheduling in a long time downlink data transmission, reduces the opportunity of the terminal device actively sending a preamble to the network device to apply for uplink scheduling resources, reduces the error code caused by uplink and downlink transmission conflict, and improves the timeliness of uplink data and reduces the additional signaling overhead caused by the preamble.

[0097] In some embodiments, the number of terminal devices establishing a communication connection with the network device is two or more. The network device needs to authorize uplink data for multiple terminal devices. Since the network device can only authorize one terminal device at a time when sending uplink authorization information, the network device cannot authorize each terminal device at the same time and needs to authorize each terminal device one by one. The network device can determine the order of authorization for different terminal devices according to the priority order of each terminal device during the authorization process.

[0098] Specifically, different priorities can be distinguished for each terminal device according to whether the terminal device reports a BSR. The priority of a terminal device that reports a BSR and needs to be configured with a data block size is set to high, and the priority of a terminal device that does not report a BSR and does not need to be configured with a data block size is set to low. The terminal device with high priority is preferentially authorized for the second uplink, and the terminal device with low priority is authorized for the first uplink.

[0099] In some embodiments, the network device can also directly avoid the NPRACH period of the terminal device when transmitting downlink data, that is, no downlink data is transmitted to the terminal device in the NPRACH period. Since the terminal device will only send a preamble to the network device to apply for uplink scheduling resources in the NPRACH period, resulting in data transmission conflict, no downlink data is transmitted to the terminal device in the NPRACH period of the terminal device, which can also avoid the uplink and downlink data conflict of the terminal device.

[0100] In combination with the data transmission system shown in Figure 1 The embodiment of the present application provides another data transmission method, which is applied to the terminal device 102, as shown in Figure 3 The processing steps of the method include:

[0101] 301, determining the uplink data transmission configuration according to the uplink authorization performed by the network device in the pre-scheduling period.

[0102] Specifically, the first uplink authorization information sent by the network device is received. The first uplink authorization information is decrypted by the identity information of the terminal device, and the range of the first uplink transmission configuration is determined from the first uplink authorization information, that is, the time, frequency band resource, data block size, modulation mode and repetition number allowed to send uplink data.

[0103] 302, within the range of the uplink transmission configuration, sending uplink data to the network device, and stopping receiving downlink data sent by the network device.

[0104] Specifically, the terminal device reports the first application layer data and the BSR to the network device according to the range of the first uplink transmission configuration.

[0105] The first application layer data is information actually needed by the terminal device to report to the network device, and the BSR is a report of the first application layer data, for example, the information contained in the BSR can be the remaining amount of information actually needed to be sent.

[0106] When the data block size configured by the network device in the first uplink grant information is not enough to complete the sending of all the information needed to be sent, the size of the remaining information needed to be sent needs to be written in the BSR, and the BSR is sent to the network device together with the first application layer data as uplink data. The BSR at this time is used to instruct the network device to perform a second uplink grant on the terminal device. The terminal device can send the second application layer information to the network device according to the time, frequency band resource, data block size, modulation mode and repetition number configured in the second uplink grant information to allow the sending of uplink data.

[0107] When the data block size configured by the network device in the first uplink grant information is enough to complete the sending of all the information actually needed to be reported, 0 is marked in the BSR, and the BSR is sent to the network device together with the first application layer data as uplink data.

[0108] The BSR sent by the terminal device is used to instruct the network device to perform a second uplink grant on the terminal device according to the data sending situation of the terminal device, or to stop performing a second uplink grant on the terminal device in the current pre-scheduling period.

[0109] 303, outside the range of the first uplink data transmission configuration, stopping sending uplink data to the network device, and resuming receiving downlink data sent by the network device.

[0110] The embodiment of the application reduces the opportunity of the terminal device to actively send a preamble request to the network device to apply for uplink scheduling resources, reduces the error code caused by the conflict of uplink and downlink simultaneous transmission, and improves the timeliness of uplink data and reduces the additional signaling overhead caused by the preamble request.

[0111] In combination with the data transmission system shown in Figure 1 The embodiment of the application provides a specific embodiment of a data transmission method, as shown in Figure 4 The processing steps include:

[0112] 401, the network device sends a first uplink grant to the terminal device in a pre-scheduling period, and the first uplink grant is used to determine a first uplink data transmission configuration of the terminal device.

[0113] Specifically, the network device establishes a communication connection with the terminal device A, the terminal device B and the terminal device C respectively. The network device needs to perform uplink authorization for the terminal device A.

[0114] The network device sends first uplink authorization information to the terminal device A to implement the first uplink authorization of the terminal device A. The first uplink authorization information indicates that the terminal device A needs to send 30k uplink data through a physical uplink shared channel (NPUSCH) after 50ms.

[0115] The network device encrypts the first uplink authorization information through the identity information of the terminal device A.

[0116] 402, the terminal device determines the first uplink data transmission configuration according to the first uplink authorization performed by the network device in the pre-scheduling period.

[0117] Specifically, the terminal device A receives the first uplink authorization information sent by the network device, decrypts the first uplink authorization information through its own identity information, and obtains the first uplink authorization information configuration range therein.

[0118] 403, the terminal device sends uplink data to the network device within the range of the first uplink data transmission configuration.

[0119] Specifically, the terminal device A sends 30k uplink data to the network device through the NPUSCH channel after 50ms according to the range of the first uplink data transmission configuration.

[0120] The 30k uplink data includes not only the first application layer data actually needed to be reported by the terminal device A, but also 4B BSR.

[0121] Since the data actually needed to be reported by the terminal device A is 50k, the data block size configured for the first uplink data is 30k, so the range of the first uplink data transmission configuration is not enough to support the terminal device A to report all the application layer data to the network device, and the BSR needs to be reported to the network device to reacquire authorization. The BSR sent by the terminal device A includes: the remaining information to be sent is 20k.

[0122] 404, the network device receives the uplink data sent by the terminal device within the range of the first uplink data transmission configuration, and stops sending downlink data to the terminal device.

[0123] Specifically, the network device receives the uplink information sent by the terminal device A through the NPUSCH channel after 50 ms. The uplink information sent by the terminal device A is analyzed to obtain the first application layer data and the BSR contained therein. The BSR can be obtained to know that the terminal device A still has 20k uplink data to be sent.

[0124] During the process of receiving the uplink data sent by the terminal device A by the network device, the downlink data sent by the terminal device A is no longer received.

[0125] 405, the network device performs second uplink authorization to the terminal device, and the second uplink authorization is used to determine the second uplink data transmission configuration of the terminal device.

[0126] Specifically, the network device configures the second uplink authorization information for the terminal device A according to the BSR reported by the terminal device A, and sends the second uplink authorization information to the terminal device A for the second uplink authorization.

[0127] The second uplink authorization information indicates that the terminal device A needs to send 20k uplink data through the NPUSCH channel after 50 ms.

[0128] 406, the terminal device determines the second uplink data transmission configuration according to the second uplink authorization of the network device.

[0129] 407, the terminal device sends uplink data to the network device within the range of the first uplink data transmission configuration.

[0130] Specifically, the terminal device A sends 20k uplink data to the network device through the NPUSCH channel after 50 ms according to the range of the second uplink data transmission configuration.

[0131] The 20k uplink data contains not only the second application layer data actually needed to be reported by the terminal device A, but also 4B BSR.

[0132] Since the 20k data block is sufficient to support the terminal device to report the remaining application layer data to the network device, the terminal device A marks 0 in the BSR and reports the BSR and the second application layer data as uplink data to the network device.

[0133] 408, the network device receives the uplink data sent by the terminal device within the range of the first uplink data transmission configuration, and stops sending downlink data to the terminal device.

[0134] Specifically, the network device receives the uplink information sent by the terminal device through the NPUSCH channel after 50 ms, and analyzes the uplink information sent by the terminal device to obtain the second application layer data and the BSR contained therein. The BSR can know that the terminal device A has no remaining uplink data to send, and the terminal device A does not need to be authorized for uplink transmission in the current pre-scheduling period.

[0135] 409, the network device stops receiving the uplink data of the terminal device out of the uplink data transmission configuration range, and resumes sending the downlink data of the terminal device.

[0136] Specifically, the terminal device A no longer sends uplink data out of the uplink data transmission configuration range, and continues to receive the downlink data sent by the network device.

[0137] The embodiment of the application configures the terminal device with timely uplink pre-scheduling in long downlink data transmission, reduces the opportunity of the terminal device to actively send a preamble request to apply for uplink scheduling resources, reduces the error code caused by the conflict of uplink and downlink simultaneous transmission, and improves the timeliness of uplink data and reduces the additional signaling overhead caused by the preamble request.

[0138] Corresponding to the above data transmission method, the embodiment of the application also provides a data transmission device. The data transmission device can be implemented as a network device. Referring to Figure 5 A structural diagram of a network device provided by the embodiment of the application, the network device can include an authorization module 501, a receiving module 502 and a sending module 503.

[0139] The authorization module 501 performs first uplink authorization to the terminal device in a pre-scheduling period, and the first uplink authorization is used to determine the first uplink data transmission configuration of the terminal device.

[0140] The receiving module 502 receives the uplink data sent by the terminal device within the range of the first uplink data transmission configuration, and stops sending the downlink data to the terminal device.

[0141] The sending module 503 stops sending the uplink authorization and stops receiving the uplink data of the terminal device out of the range of the first uplink data transmission configuration, and resumes sending the downlink data of the terminal device.

[0142] Corresponding to the above data transmission method, the embodiment of the application also provides another data transmission device. The data transmission device can be implemented as a terminal device. Referring to Figure 6 A structural diagram of a terminal device provided by the embodiment of the application, the terminal device can include a determination module 601, a sending module 602 and a receiving module 603.

[0143] Module 601 determines the first uplink data transmission configuration based on the first uplink authorization granted by the network device during the pre-scheduling period;

[0144] The sending module 602, within the range of the first uplink data transmission configuration, sends uplink data to the network device and stops receiving downlink data sent by the network device;

[0145] The receiving module 603 stops sending uplink data to the network device and resumes receiving downlink data sent by the network device when the uplink data transmission configuration is outside the range of the first uplink data transmission configuration.

[0146] Figure 7 This is a schematic diagram illustrating the structure of one embodiment of the electronic device described in this specification. The electronic device can be implemented as the network device or terminal device described above. Figure 7 As shown, the above-mentioned electronic device may include at least one processor; and at least one memory communicatively connected to the processing unit, wherein: the memory stores program instructions executable by the processing unit, and the processor can execute the data transmission method provided in this embodiment by calling the program instructions.

[0147] The aforementioned electronic device can be a device capable of intelligent dialogue with the user, such as a cloud server. This specification does not limit the specific form of the electronic device in the embodiments. It is understood that the electronic device here refers to the machine mentioned in the method embodiments.

[0148] Figure 7 A block diagram of an exemplary electronic device suitable for implementing embodiments of this specification is shown. Figure 7 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments described in this specification.

[0149] like Figure 7 As shown, the electronic device is represented in the form of a general-purpose computing device. The components of the electronic device may include, but are not limited to: one or more processors 710, communication interface 720, memory 730, and communication bus 740 connecting different system components (including memory 730, communication interface 720 and processor 710).

[0150] The communications bus 740 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration bus, a processor or local bus using any of a variety of bus architectures. By way of example, these architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0151] Electronic devices typically include a variety of computer system readable media. Such media can be any available media that is located either internally or externally to an electronic device. It includes storage of removable and non-removable, volatile and non-volatile computer system storage media.

[0152] The memory 730 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) and / or cache memory. The electronic device can further include other removable / non-removable, volatile / non-volatile computer system storage media. The memory 730 can include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the present disclosure.

[0153] The program / utility, having a set (at least one) of program modules, can be stored in the memory 730 by way of example, and can include an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, can include an implementation of a networking environment.

[0154] The processor 710, through the operating system, executes the various

[0155] The embodiments of the present disclosure provide a non-transitory computer readable storage medium storing computer instructions, which cause the computer to perform the data transmission method provided by the embodiments of the present disclosure.

[0156] The non-transitory computer-readable storage medium can employ any combination of one or more computer-readable media. The computer-readable media can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0157] A computer-readable signal medium can include a computer-readable program code carried in a baseband or propagated as a carrier wave in a propagation medium. Such a propagated signal can take a wide variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable medium that is not a computer-readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[0158] Program code embodied on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0159] Computer program code for carrying out operations of the present specification can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0160] The above description describes certain embodiments of the present specification. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order and still accomplish desirable results. Additionally, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous or necessary.

[0161] In addition, the terms "first", "second", etc. are used herein only to describe different instances, and do not imply or suggest relative importance or a number of the indicated technical features. Thus, the features defined with "first", "second" can explicitly or implicitly include at least one of the features. In the description of the present specification, the meaning of "a plurality of" is at least two, for example, two, three, etc., unless otherwise explicitly specified.

[0162] Any process or method descriptions or descriptions of processes or methods described in flow diagrams or otherwise described herein can be understood as representing code modules, segments, or portions of code which include one or more executable instructions for implementing specific logic functions (or steps) of the process, and that the various systems described herein can include one or more circuits, such as one or more processors, that are configured to implement the described processes or methods. The various systems described herein can include one or more circuits, such as one or more processors, that are configured to implement the described processes or methods. The various systems described herein can include one or more circuits, such as one or more processors, that are configured to implement the described processes or methods.

[0163] Depending on the context, the word "if" can be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [a stated condition or event] is detected" can be interpreted to mean "upon determining" or "in response to determining" or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]," depending on the context.

[0164] It should be noted that the terminal involved in the embodiments of the present specification can include, but is not limited to, a personal computer (PC), a personal digital assistant (PDA), a wireless handheld device, a tablet computer, a mobile phone, an MP3 player, an MP4 player, and the like.

[0165] In the embodiments provided by the present specification, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic. The division of the units is only a logical function division. There can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical, mechanical or in other forms.

[0166] In addition, each function unit in each embodiment of the present specification can be integrated into one processing unit, or each unit can exist alone physically, or two or more units can be integrated into one unit. The above integrated unit can be realized in the form of hardware, or in the form of hardware plus software function unit.

[0167] The integrated unit realized in the form of software function unit can be stored in a computer readable storage medium. The software function unit stored in the storage medium includes a plurality of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (Processor) to perform some steps of the methods described in each embodiment of the present specification.

[0168] The above only describes the preferred embodiments of the present specification and is not intended to limit the present specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of protection of the present specification.

Claims

1. A data transmission method, characterized by, The method is applied to a network device, and the method comprises: performing first uplink authorization on a terminal device in a pre-scheduling period, the first uplink authorization being used to determine a first uplink data transmission configuration of the terminal device; receiving uplink data sent by the terminal device within a range of the first uplink data transmission configuration, and stopping sending downlink data to the terminal device; stopping receiving uplink data of the terminal device outside the range of the first uplink data transmission configuration, and resuming sending downlink data to the terminal device; after the receiving of the uplink data sent by the terminal device, the method further comprises: analyzing the uplink data to obtain first application layer data and a buffer status report (BSR) contained in the uplink data; determining whether to perform second uplink authorization on the terminal device according to the BSR in the uplink data; the determining whether to perform second uplink authorization on the terminal device according to the BSR in the uplink data comprises: when the BSR in the uplink data is not zero, determining second uplink authorization information used to represent a second uplink data transmission configuration according to the BSR, and performing second uplink authorization on the terminal device through the second uplink authorization information, wherein the BSR comprises a data block size of second application layer data needed to be reported by the terminal device; when the BSR reported by the terminal device is zero, no second uplink authorization is performed on the terminal device in a current pre-scheduling period.

2. The method of claim 1, wherein, The pre-scheduling period is determined according to a physical random access channel (NPRACH) period of the terminal device.

3. The method of claim 1, wherein, The performing of the first uplink authorization on the terminal device comprises: sending first uplink authorization information to the terminal device, the first uplink authorization information comprising time, frequency band resource, data block size, modulation mode and repetition number of uplink data allowed to be sent by the terminal device; the time, frequency band resource, data block size, modulation mode and repetition number of the uplink data are used to determine the first uplink data transmission configuration of the terminal device together.

4. The method of claim 3, wherein, The sending of the first uplink authorization information to the terminal device comprises: encrypting the first uplink authorization information through identity information of the terminal device; the encrypted first uplink authorization information can be decrypted only through the identity information of the terminal device.

5. The method of claim 1, wherein, The method further comprises: when there are multiple terminal devices connected, determining a priority order of the terminal devices according to whether the terminal devices report BSRs; performing second uplink authorization on the terminal devices reporting BSRs preferentially according to the priority order.

6. The method of claim 1, wherein, The method further comprises: determining an NPRACH period of the terminal device; sending downlink data to the terminal device outside the NPRACH period of the terminal device.

7. A data transmission method, characterized by, The method is applied to a terminal device, and the method comprises: determining a first uplink data transmission configuration according to first uplink authorization performed by a network device in a pre-scheduling period; sending uplink data to the network device within a range of the first uplink data transmission configuration, and stopping receiving downlink data sent by the network device; stopping sending uplink data to the network device outside the range of the first uplink data transmission configuration, and resuming receiving downlink data sent by the network device; the sending uplink data to the network device comprises: the uplink data sent to the network device contains first application layer data and a buffer status report (BSR), and the BSR includes a data block size of second application layer data needed to be reported by the terminal device; the BSR is used for the network device to determine whether to perform second uplink authorization on the terminal device; the BSR is used for the network device to determine whether to perform second uplink authorization on the terminal device, comprising: when the BSR is not zero, the BSR is used to instruct the network device to determine second uplink authorization information used to represent a second uplink data transmission configuration, and perform second uplink authorization on the terminal device through the second uplink authorization information; when the BSR is zero, the BSR is used to instruct the network device to no longer perform second uplink authorization on the terminal device within a current pre-scheduling period.

8. The method of claim 7, wherein, the determining the first uplink data transmission configuration according to the first uplink authorization performed by the network device in the pre-scheduling period comprises: obtaining first uplink authorization information sent by the network device; determining time, frequency band resources, data block size, modulation mode and repetition number of uplink data allowed to be sent in the first uplink authorization information; determining the first uplink data transmission configuration according to the time, frequency band resources, data block size, modulation mode and repetition number of uplink data allowed to be sent.

9. The method of claim 8, wherein, the determining the time, frequency band resources, data block size, modulation mode and repetition number of uplink data allowed to be sent in the first uplink authorization information comprises: decrypting the first uplink authorization information through identity information of the terminal device itself; obtaining the time, frequency band resources, data block size, modulation mode and repetition number of uplink data allowed to be sent from the decrypted first uplink authorization information.

10. The method of claim 7, wherein, the method further comprises: receiving downlink data sent by the network device outside a physical random access channel (NPRACH) period.

11. A data transmission apparatus, characterized by comprising: the apparatus is applied to a network device, and the apparatus comprises: an authorization module, configured to perform first uplink authorization on a terminal device in a pre-scheduling period, and the first uplink authorization is used to determine a first uplink data transmission configuration of the terminal device; a receiving module, configured to receive uplink data sent by the terminal device within a range of the first uplink data transmission configuration, and stop sending downlink data to the terminal device; a sending module, configured to stop sending uplink authorization and stop receiving uplink data of the terminal device outside the range of the first uplink data transmission configuration, and resume sending downlink data to the terminal device; after the receiving uplink data sent by the terminal device, the apparatus further comprises: decrypting the uplink data to obtain first application layer data and a buffer status report (BSR) contained in the uplink data; determining whether to perform a second uplink grant on the terminal device according to the BSR in the uplink data; the determining whether to perform a second uplink grant on the terminal device according to the BSR in the uplink data comprises: when the BSR in the uplink data is not zero, determining second uplink grant information used for representing a second uplink data transmission configuration according to the BSR, and performing a second uplink grant on the terminal device through the second uplink grant information, wherein the BSR comprises a data block size of second application layer data needed to be reported by the terminal device; when the BSR reported by the terminal device is zero, no longer performing a second uplink grant on the terminal device in a current pre-scheduling period.

12. A data transmission device, characterized by comprise: at least one processor; and at least one memory connected with the processor in communication, wherein: the memory stores program instructions executable by the processor, and the processor invoking the program instructions can perform the method of any one of claims 1 to 6.

13. A data transmission apparatus, characterized by comprising: the device is applied to a terminal device, and the device comprises: a determining module configured to determine a first uplink data transmission configuration according to a first uplink grant performed by a network device in a pre-scheduling period; a sending module configured to send uplink data to the network device within a range of the first uplink data transmission configuration, and stop receiving downlink data sent by the network device; a receiving module configured to stop sending uplink data to the network device outside the range of the first uplink data transmission configuration, and resume receiving downlink data sent by the network device; the sending uplink data to the network device comprises: the uplink data sent to the network device comprises first application layer data and a buffer status report (BSR), and the BSR comprises a data block size of second application layer data needed to be reported by the terminal device; the BSR is used by the network device to determine whether to perform a second uplink grant on the terminal device; the BSR used by the network device to determine whether to perform a second uplink grant on the terminal device comprises: when the BSR is not zero, the BSR is used to instruct the network device to determine second uplink grant information used for representing a second uplink data transmission configuration, and perform a second uplink grant on the terminal device through the second uplink grant information; when the BSR is zero, the BSR is used to instruct the network device to no longer perform a second uplink grant on the terminal device in a current pre-scheduling period.

14. A data transmission device, characterized by comprise: at least one processor; and at least one memory connected with the processor in communication, wherein: the memory stores program instructions executable by the processor, and the processor invoking the program instructions can perform the method of any one of claims 7 to 10.

15. A computer-readable storage medium, characterized in that, the computer readable storage medium comprises a stored program, wherein when the program runs, the device where the computer readable storage medium is located performs the method of any one of claims 1 to 6 or claims 7 to 10.

Images