WO2024000316A1

WO2024000316A1 - Data transmission method and apparatus, communication device, and storage medium

Info

Publication number: WO2024000316A1
Application number: PCT/CN2022/102510
Authority: WO
Inventors: 王德乾; 刘水
Original assignee: 北京小米移动软件有限公司
Priority date: 2022-06-29
Filing date: 2022-06-29
Publication date: 2024-01-04
Also published as: CN117643096A

Abstract

Disclosed in the embodiments of the present disclosure are a data transmission method and apparatus, a communication device, and a storage medium. The data transmission method is executed by a terminal, and comprises: receiving DCI; determining the DCI to indicate uplink scheduling information, and determining that there is no data to be reported; and stopping a reporting operation.

Description

Data transmission methods and devices, communication equipment and storage media

Technical field

The present disclosure relates to the field of wireless communication technology but is not limited to the field of wireless communication technology, and in particular, to a data transmission method and device, communication equipment and storage medium.

Background technique

In related technologies, the power consumption reduction scheme adopted for the power consumption generated during terminal communication is often achieved by controlling the uplink data transmission process, such as reducing the frequency of uplink data transmission, etc., but this method It often affects the data transmission effect, which may lead to abnormal communication. Moreover, in related technologies, there is often a pre-scheduling mechanism for communication resources between the base station and the terminal. Communication resources are often still scheduled when the terminal does not need to transmit data uplink, and the terminal is required to report empty data packets. Therefore, it not only occupies transmission resources but also causes the terminal to continue to conduct ineffective interactions, causing the terminal to generate a large amount of unnecessary power consumption, thereby shortening the terminal life time.

Contents of the invention

Embodiments of the present disclosure provide a data transmission method and device, communication equipment and storage media.

The first aspect of the embodiment of the present disclosure provides a data transmission method, which is executed by a terminal. The method includes:

Receive downlink control information (DCI);

Determine that the DCI indicates uplink scheduling information, and determine that there is no data to be reported;

Stop the reporting operation.

A second aspect of the embodiment of the present disclosure provides a data transmission device, which is applied to a terminal. The device includes:

a receiving unit configured to receive DCI;

a determining unit configured to determine that the DCI indicates uplink scheduling information, and determine that there is no data to be reported;

Stop unit, configured to stop reporting operations.

A third aspect of the embodiment of the present disclosure provides a communication device, including a processor, a memory, and an executable program stored on the memory and capable of being run by the processor, wherein when the processor runs the executable program, The data transmission method provided in the first aspect is as mentioned above.

A fourth aspect of the embodiments of the present disclosure provides a computer storage medium that stores an executable program; after the executable program is executed by a processor, the data transmission method provided by the first aspect can be implemented.

The technical solution provided by the embodiments of the present disclosure includes receiving downlink control information DCI; determining that the DCI indicates uplink scheduling information, and determining that there is no data to be reported; and stopping the reporting operation. . In this way, when the base station instructs the terminal to transmit data in the uplink, if the terminal does not have data to be reported, the reporting operation will not be performed, so that operations such as empty data packets will not be reported when the terminal has no need for uplink data transmission. Therefore, the terminal will not report empty packets due to resource pre-scheduling indicated by the base station when there is no need to transmit data uplink, thereby reducing the power consumption caused by the terminal's continuous reporting operations and improving the terminal battery life.

It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and do not limit the embodiments of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description serve to explain the principles of the embodiments of the invention.

Figure 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment;

Figure 2 is a schematic flowchart of a data transmission method according to an exemplary embodiment;

Figure 3 is a schematic flowchart of a data transmission method according to an exemplary embodiment;

Figure 4 is a schematic flow chart of a data transmission method according to an exemplary embodiment;

Figure 5 is a schematic flowchart of a data transmission method according to an exemplary embodiment;

Figure 6 is a schematic flowchart of a data transmission method according to an exemplary embodiment;

Figure 7 is a schematic flowchart of uplink transmission resource scheduling in related technologies according to an exemplary embodiment;

Figure 8 is a schematic flowchart of uplink transmission resource scheduling in related technologies according to an exemplary embodiment;

Figure 9 is a schematic flowchart of a data transmission method according to an exemplary embodiment;

Figure 10 is a schematic flowchart of a data transmission method according to an exemplary embodiment;

Figure 11 is a schematic structural diagram of a data transmission device according to an exemplary embodiment;

Figure 12 is a schematic structural diagram of a terminal according to an exemplary embodiment.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with embodiments of the invention. Rather, they are merely examples of apparatus and methods consistent with some aspects of embodiments of the invention.

The terminology used in the embodiments of the present disclosure is for the purpose of describing specific embodiments only and is not intended to limit the embodiments of the present disclosure. As used in this disclosure, the singular forms "a," "the" and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be called second information, and similarly, the second information may also be called first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to determining."

Please refer to FIG. 1 , which shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure. As shown in Figure 1, the wireless communication system is a communication system based on cellular mobile communication technology. The wireless communication system may include: several terminals 11 and several access devices 12.

Among them, the terminal 11 may be a device that provides voice and/or data connectivity to the user. Terminal 11 can communicate with one or more core networks via a Radio Access Network (RAN). Terminal 11 can be an Internet of Things terminal, such as a sensor device, a mobile phone (or "cellular" phone) and a device with The computer of the Internet of Things terminal, for example, can be a fixed, portable, pocket-sized, handheld, computer-built-in or vehicle-mounted device. For example, station (STA), subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), mobile station (mobile), remote station (remote station), access point, remote terminal ( remote terminal), access terminal, user terminal, user agent, user device, or user equipment (terminal). Alternatively, the terminal 11 may be a device of an unmanned aerial vehicle. Alternatively, the terminal 11 may also be a vehicle-mounted device, for example, it may be an on-board computer with a wireless communication function, or a wireless communication device connected to an external on-board computer. Alternatively, the terminal 11 may also be a roadside device, for example, it may be a streetlight, a signal light or other roadside device with wireless communication function.

The access device 12 may be a network-side device in the wireless communication system. Among them, the wireless communication system can be the 4th generation mobile communication technology (the 4th generation mobile communication, 4G) system, also known as the Long Term Evolution (LTE) system; or the wireless communication system can also be a 5G system, Also called new radio (NR) system or 5G NR system. Alternatively, the wireless communication system may also be a next-generation system of the 5G system. Among them, the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network). Or, MTC system.

The access device 12 may be an evolved access device (eNB) used in the 4G system. Alternatively, the access device 12 may also be an access device (gNB) using a centralized distributed architecture in the 5G system. When the access device 12 adopts a centralized distributed architecture, it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed unit, DU). The centralized unit is equipped with a protocol stack including the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control protocol (Radio Link Control, RLC) layer, and the Media Access Control (Media Access Control, MAC) layer; distributed The unit is provided with a physical (Physical, PHY) layer protocol stack, and the embodiment of the present disclosure does not limit the specific implementation of the access device 12.

A wireless connection can be established between the access device 12 and the terminal 11 through a wireless air interface. In different implementations, the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, such as The wireless air interface is a new air interface; alternatively, the wireless air interface may also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.

Optionally, the above wireless communication system may also include a network management device 13. Several access devices 12 are connected to the network management device 13 respectively. The network management device 13 may be a core network device in a wireless communication system. For example, the network management device 13 may be a mobility management entity (Mobility Management Entity) in an evolved packet core network (Evolved Packet Core, EPC). MME). Alternatively, the network management device can also be other core network devices, such as serving gateway (Serving GateWay, SGW), public data network gateway (Public Data Network GateWay, PGW), policy and charging rules functional unit (Policy and Charging Rules) Function, PCRF) or Home Subscriber Server (HSS), etc. The embodiment of the present disclosure does not limit the implementation form of the network management device 13 .

As shown in Figure 2, an embodiment of the present disclosure provides a data transmission method, which is executed by a terminal and may include:

S110: Receive DCI;

S120: Confirm that the DCI indicates uplink scheduling information, and determine that there is no data to be reported;

S130: Stop the reporting operation.

In this embodiment of the present disclosure, the terminal may be a user equipment (User Equipment, UE), used to communicate with network-side objects such as base stations. Taking communication between a terminal and a base station as an example, DCI can be downlink control information issued by the base station. For example, DCI can be used to instruct the terminal to transmit uplink data, and/or to instruct the terminal to schedule time domain resources for uplink transmission and/or Frequency domain resources and other information.

In one embodiment, the DCI can be issued by the base station based on the resource request message (Scheduling Request, SR) reported by the terminal, or it can be issued by the base station itself, for example, the DCI issued by the base station based on the enabled pre-scheduling function. Among them, the SR can be sent to the base station through the physical uplink control channel (PUCCH).

In related technologies, the pre-scheduling function can be enabled by network-side objects such as base stations to continuously monitor the uplink transmission data of terminals and reduce the failure of terminals to respond to sudden data reporting requirements. When the pre-scheduling function is turned on, when the base station does not receive the SR sent by the terminal, it also issues DCI to instruct the terminal to perform the reporting operation. For example, the terminal will report empty data packets based on DCI when there is no data reporting requirement.

In one embodiment, the uplink scheduling information may be information instructing the terminal to perform a reporting operation. For example, the uplink scheduling information may carry an uplink response message (UpLink Grant, ULGrant), and the ULGrant is used to instruct the terminal to start uplink transmission. Among them, the DCI carrying ULGrant can be delivered to the terminal through the physical downlink control channel (PDCCH).

In one embodiment, the uplink scheduling information may also indicate information such as the amount of data reported by the terminal and/or the reporting time.

In one embodiment, the uplink scheduling information may also indicate time domain resources and/or frequency domain resources scheduled to the terminal for uplink transmission. For example, time domain resources and/or frequency domain resources may be resources scheduled for the terminal based on SR and/or Buffer Status Report (Buffer Status Report, BSR) reported by the terminal.

Among them, the BSR can indicate the cache status of the cache module (Buffer) that stores the data to be reported by the terminal. For example, when the data to be reported is stored in the Buffer, the BSR can indicate the data storage amount or storage rate of the Buffer. When there is no data to be reported in the Buffer, the value of BSR can be 0.

In one embodiment, determining that there is no data to be reported may include: determining whether the SR is reported within the first time window before receiving the DCI; if no SR is reported within the first time window, determining that there is no data to be reported. data. The first time window may be a fixed value, such as 100 ms or 1 s, or the first time window may be determined based on the terminal's data uplink transmission situation.

For example, the first average duration between the first time when the SR is historically reported and the second time when the DCI corresponding to the SR is received is determined based on the terminal's historical reporting operation records, and the first time window can be determined based on the first average time duration. For example, the first time window may be equal to the first average duration, or may be equal to a preset ratio or a preset multiple of the first average duration.

In one embodiment, the first average duration may be an average duration between multiple sets of first moments and second moments within a preset period. For example, the preset period may be a fixed value such as 1 hour or 1 day, or it may be Determined based on the terminal’s data uplink transmission conditions. For example, the higher the data uplink transmission frequency of the terminal, the shorter the preset period, etc., thereby ensuring the accuracy of determining the first average duration based on the preset period without generating a high amount of data calculation.

In one embodiment, the historical reporting operation records of the terminal can be determined through the operation log information of the terminal. For example, the historical reporting operation records of the terminal within a certain period of time can be determined by retrieving the operation logs of the terminal within a certain period of time.

In this way, since the terminal sends an SR request for scheduling resources to the base station only when it needs to report data, it can be determined based on the sending status of the SR whether the terminal has data to be reported.

In one embodiment, the method may further include: determining whether the data to be reported exists in the storage location of the data to be reported. The storage location of the data to be reported may be a data buffer module (Buffer) for the data to be reported, etc.

In one embodiment, determining whether there is data to be reported in the storage location of the data to be reported may be to determine whether the value of the BSR reported before receiving the DCI is 0; if it is 0, determine whether there is no data in the storage location of the data to be reported. There is data to be reported. If it is not 0, there is data to be reported in the storage location of the data to be reported.

In one embodiment, determining whether the value of the BSR reported before receiving the DCI is 0 may be determined by determining whether the value of the last BSR reported before receiving the DCI is 0, or determining whether the value of the BSR reported before receiving the DCI is 0, or determining whether the value of the BSR reported before receiving the DCI is 0. Whether the value of BSR is 0, etc. The second time window may be a fixed value, such as 100 ms or 1 s, or the second time window may be determined based on the terminal's data uplink transmission situation.

For example, the second average duration between the third time when the BSR was historically reported and the fourth time when the DCI corresponding to the BSR was received may be determined based on the terminal's historical reporting operation records, and the second time window may be determined based on the second average time duration. For example, the second time window may be equal to the second average duration, or may be equal to a preset ratio or a preset multiple of the second average duration.

In one embodiment, the second average duration may be an average duration between multiple sets of third moments and fourth moments within a preset period. For example, the preset period may be a fixed value such as 1 hour or 1 day, or it may Determined based on the terminal’s data uplink transmission conditions. For example, the higher the data uplink transmission frequency of the terminal, the shorter the preset period, etc., thereby ensuring the accuracy of determining the second average duration based on the preset period without generating a high amount of data calculation.

In one embodiment, determining whether there is data to be reported in the storage location of the data to be reported may include: determining whether there is data to be reported in the storage location of the data to be reported based on the information to be reported generated by the terminal in response to DCI. For example, the information to be reported can be a Transport Block (TB), and based on the field information contained in the TB, it can be determined whether there is data to be reported in the storage location of the data to be reported.

For example, when the field information contained in the TB is all padding fields (Padding), it means that the terminal has no data to report. At this time, in response to the uplink scheduling information of the DCI, the terminal to report is an empty packet, then it can be determined that the data to be reported is There is no data to be reported in the storage location.

In one embodiment, determining that there is no data to be reported may include: determining that there is no data to be reported within the target time period. For example, the target duration can be a fixed value, or it can be determined based on the terminal data uplink transmission records. For example, the higher the terminal data uplink transmission frequency, the shorter or longer the target duration may be.

In one embodiment, stopping the reporting operation may be stopping reporting operations in response to DCI. For example, stop responding to DCI's TB reporting operation, etc.

In one embodiment, stopping the reporting operation may also be stopping the reporting operation within a preset period. The preset period can be a fixed value, for example, the reporting operation is stopped within 1 second, or the preset period can also be determined based on the terminal data uplink transmission record. For example, the higher the terminal historical data uplink transmission frequency, the shorter the preset period or The longer you wait.

In this way, when the DCI indicating that the base station instructs the terminal to transmit uplink data is detected, the terminal detects whether there is data to be reported. Therefore, when there is no uplink data transmission requirement, the terminal does not need to perform operations such as reporting empty data packets. Therefore, the terminal will not report empty packets due to resource pre-scheduling indicated by the base station when there is no need to transmit data uplink, thereby reducing the power consumption caused by the terminal's continuous reporting operations and improving the terminal battery life.

In some embodiments, as shown in Figure 3, step S110 may include:

S101: Obtain the currently reported cache status report BSR;

S102: If the value of BSR is 0, receive DCI.

In this embodiment of the present disclosure, the currently reported BSR may be the BSR reported at the current time or the latest time from the current time, or may be the BSR currently generated by the terminal and to be reported. Among them, the BSR can indicate the amount of data cached in the data cache module (Buffer) to be reported.

Here, when the value of BSR is 0, it can be determined that the terminal does not currently have data reporting requirements.

In one embodiment, obtaining the currently reported cache status report BSR may include obtaining the currently reported cache status report BSR according to the terminal BSR reporting log, or obtaining the BSR generated by the terminal to be reported after detecting that the terminal generates a BSR.

In one embodiment, if the value of the BSR is 0, receiving the downlink control information DCI may include: if the value of the BSR is 0 or the parameter value in the BSR indicating the amount of buffered data in the Buffer is 0, then receiving the downlink control information DCI .

In one embodiment, if the value of BSR is 0, receiving downlink control information DCI may include: if the value of BSR is 0, determining the current operating status of the terminal; and receiving downlink control information when the current operating status of the terminal meets preset conditions. DCI. The current operating status of the terminal may indicate the current power consumption level of the terminal. For example, the current operating status of the terminal may include at least one of the following: current average power consumption of the terminal, current resource occupancy rate of the terminal, current working mode of the terminal, and current remaining power of the terminal.

In one embodiment, the preset condition may be to indicate that the current power consumption level of the terminal is relatively high. For example, the preset condition may be at least one of the following: the current average power consumption of the terminal reaches the power consumption upper limit, the current resource occupancy rate of the terminal reaches The upper limit of occupancy rate, the current working mode of the terminal is power saving mode and the current remaining power of the terminal is lower than the lower limit of power, etc.

In one embodiment, obtaining the currently reported BSR may include: determining whether a BSR currently needs to be reported; and if so, obtaining the currently reported BSR. Determining whether the BSR needs to be reported currently may be determined based on the reporting operation status of the terminal. For example, whether the BSR needs to be reported currently can be determined based on the amount of data to be reported by the terminal or the BSR reporting situation.

In one embodiment, determining whether the BSR needs to be reported currently may be determined by determining whether the terminal needs to report the BSR within the target time window. For example, the target time window can be determined based on the BSR reporting situation. For example, it can be determined based on the BSR reporting cycle or the total duration of BSR historical reporting.

In some embodiments, determining whether the BSR needs to be reported currently may also be determined based on the reporting cycle of the BSR.

In one embodiment, determining whether the BSR needs to be reported at the current time according to the BSR reporting cycle may be based on the current time and the BSR reporting cycle, determining whether the BSR needs to be reported at the current time. For example, it is determined whether the BSR needs to be reported at the current time based on the current time and the BSR reporting time indicated by the BSR reporting cycle.

For example, when the current time exceeds the BSR reporting time indicated by the BSR reporting period and the BSR is not reported at the BSR reporting time, it is determined that the BSR does not need to be reported at the current time.

In this way, it can be determined whether the current terminal has data reporting requirements based on the currently reported or to-be-reported BSR, so that it can be more accurately determined whether the terminal needs to report data, and thus the reporting operation of the terminal can be more accurately controlled.

As shown in Figure 4, an embodiment of the present disclosure provides a data transmission method, which is executed by a terminal and may include:

S110: Receive DCI;

S121: Confirm that the DCI indicates uplink scheduling information, and determine that there is no data to be reported in the uplink data cache module of the terminal;

S130: Stop the reporting operation.

In the embodiment of the present disclosure, the uplink data cache module (Buffer) can be used to cache data to be reported by the terminal, for example, used to store data to be reported by the terminal within a target time period, etc. Determine whether there is data to be reported in the terminal's uplink data cache module.

In one embodiment, determining that there is no data to be reported in the uplink data cache module of the terminal can be determined by determining that the value of the BSR reported before receiving the DCI is 0, and determining that there is no data to be reported in the uplink data cache module of the terminal. data, if it is not 0, there is data to be reported in the uplink data cache module of the terminal.

In one embodiment, determining that the value of the BSR reported before receiving the DCI is 0 may be determining that the value of the last BSR reported before receiving the DCI is 0, or determining that the value of the BSR reported in the second time window before receiving the DCI is 0. The value is 0 etc. The second time window may be a fixed value, such as 100 ms or 1 s, or the second time window may be determined based on the terminal's data uplink transmission situation.

In one embodiment, determining that there is no data to be reported in the uplink data cache module of the terminal may include: based on the information to be reported generated by the terminal in response to DCI, determining that there is no data to be reported in the uplink data cache module of the terminal. For example, the information to be reported can be a Transport Block (TB). Based on the field information contained in the TB, it can be determined that there is no data to be reported in the uplink data cache module of the terminal.

In one embodiment, determining that there is no data to be reported in the uplink data cache module of the terminal may include: determining that there is no data to be reported within the target time period in the uplink data cache module of the terminal. For example, the target duration can be a fixed value, or it can be determined based on the terminal data uplink transmission records. For example, the higher the terminal data uplink transmission frequency, the shorter or longer the target duration may be.

In some embodiments, step S121 may include:

Get the fields contained in the transmission block TB to be reported;

If all the fields included in the TB are padding fields, it is determined that there is no data to be reported in the uplink data cache module of the terminal.

In this embodiment of the present disclosure, when the field information contained in the TB is all padding fields (Padding), it means that the terminal has no data to report. At this time, in response to the uplink scheduling information of the DCI, the terminal to report is an empty packet, then it can be determined that the data to be reported is empty. There is no data to be reported in the storage location of the reported data.

Here, the padding field can be the information filled in the TB when there is no data that needs to be carried in the TB for reporting when the TB is generated. For example, it can be empty data, or it can be bytes pre-agreed according to the agreement between the terminal and the base station, etc. .

In some embodiments, obtaining the fields contained in the transport block TB to be reported may include:

In response to the uplink scheduling information indicated by the DCI, generate the transport block TB to be reported;

Get the fields contained in TB.

In the embodiment of the present disclosure, the TB to be reported can be used to carry the data to be reported, for example, the data information to be reported is recorded through different fields contained in the TB. When there is no data to be reported, in response to the uplink scheduling information indicated by the DCI, all fields included in the generated TB may be padding.

In one embodiment, in response to the uplink scheduling information indicated by the DCI, generating the transmission block TB to be reported may include: in response to the uplink scheduling information indicated by the DCI, determining the data to be reported based on the uplink scheduling information; based on the data to be reported Generate TB to be reported.

In one embodiment, in response to the uplink scheduling information indicated by the DCI, determining the data to be reported based on the uplink scheduling information may include: in response to the uplink scheduling information indicated by the DCI, determining the data to be reported based on the uplink scheduling information within the target duration. . For example, the target duration can be a fixed value, or it can be determined based on the terminal data uplink transmission records. For example, the higher the terminal data uplink transmission frequency, the shorter or longer the target duration may be.

In this way, based on the fields included in the TB to be reported, it can be determined more quickly and accurately whether the terminal has data that needs to be reported, so that the terminal's reporting operation can be more accurately controlled and the terminal power consumption can be reduced.

As shown in Figure 5, an embodiment of the present disclosure provides a data transmission method, which is executed by a terminal and may include:

S110: Receive DCI;

S130: Stop reporting operation;

S140: If the data retransmission instruction issued by the base station is received and it is determined that there is no data to be reported, the data retransmission instruction will not be responded to.

In the embodiment of the present disclosure, the data retransmission instruction may be a retransmission instruction issued by a TB that the base station has not detected in response to a DCI report from the terminal, or it may be a DCI that the base station resends.

In one embodiment, the method used to determine that there is no data to be reported in step S140 may be the same as the method used to determine that there is no data to be reported in step S120, or may be different.

For example, determining that there is no data to be reported may be determining whether an SR is reported within the first time window before receiving the data retransmission instruction; if no SR is reported within the first time window, it is determined that there is no data to be reported.

In one embodiment, determining that there is no data to be reported may include: determining that there is no data to be reported in a storage location of the data to be reported. The storage location of the data to be reported may be a data buffer module (Buffer) for the data to be reported, etc.

In one embodiment, determining that there is no data to be reported in the storage location of the data to be reported may be to determine whether the value of the BSR reported before receiving the data retransmission instruction is 0; if it is 0, determine the storage location of the data to be reported. There is no data to be reported in the location. If it is not 0, there is data to be reported in the storage location of the data to be reported.

In one embodiment, determining whether the value of the BSR reported before the data retransmission instruction is received is 0 may be determined by determining whether the value of the BSR last reported before the data retransmission instruction is received is 0, or determining whether the value of the BSR reported before the data retransmission instruction is received is 0. Whether the BSR value reported in the second time window before transmitting the command is 0, etc.

In one embodiment, re-determining whether the data to be reported exists in the storage location of the data to be reported may include: based on the information to be reported generated by the terminal in response to the data retransmission instruction, re-determining whether the data to be reported exists in the storage location. Data to be reported. For example, the information to be reported can be a Transport Block (TB), and based on the field information contained in the TB, it can be determined whether there is data to be reported in the storage location of the data to be reported.

For example, when the field information contained in the TB is all padding fields (Padding), it means that the terminal has no data that needs to be reported. At this time, the uplink scheduling information to be reported by the terminal in response to the data retransmission instruction is an empty packet, and it can be determined that the packet to be reported is empty. There is no data to be reported in the storage location of the reported data.

In this way, when there is no data to be reported by the terminal, whether it receives DCI or data retransmission instructions continuously issued by the base station, the terminal will not perform reporting operations, thereby better controlling the reporting operations of the terminal and reducing the cost of the terminal. power consumption.

As shown in Figure 6, the data transmission method may also include:

S160: When it is determined not to continue reporting the BSR, report instruction information instructing to release the transmission link between the terminal and the base station.

In this embodiment of the present disclosure, determining not to continue to report the BSR may be based on the reporting operation status of the terminal. For example, it may be determined not to continue to report BSR based on the amount of data to be reported by the terminal or the BSR reporting situation.

In one embodiment, determining not to continue reporting the BSR may be determining that the terminal does not continue to report the BSR within the target time window. For example, the target time window can be determined based on the BSR reporting situation. For example, it can be determined based on the BSR reporting cycle or the total duration of BSR historical reporting.

In some embodiments, step S160 may include:

Determine not to continue reporting BSR at the current time based on the BSR reporting cycle.

In one embodiment, determining not to continue reporting the BSR at the current time based on the BSR reporting cycle may be based on the current time and the BSR reporting cycle, determining not to continue reporting the BSR at the current time.

For example, based on the current time and the BSR reporting time indicated by the BSR reporting cycle, it is determined not to continue to report the BSR at the current time.

For example, when the current time exceeds the BSR reporting time indicated by the BSR reporting cycle and the BSR is not reported at the BSR reporting time, it is determined not to continue to report the BSR.

In this way, when the terminal does not need to continue reporting BSR, it can be determined that the terminal does not need to perform reporting operations to the base station temporarily, thereby instructing the release of the transmission link, reducing the continuous occupation of transmission link resources, and improving the availability of transmission link resources.

In some embodiments, the method may further include:

If there is data to be reported, the data is reported based on the uplink scheduling information indicated by the DCI.

In the embodiment of the present disclosure, the reporting data based on the uplink scheduling information indicated by DCI may include reporting data based on the reporting parameters recorded in the uplink scheduling information indicated by DCI. For example, the reporting parameters may include at least one of the following: reporting time, reporting data type, reporting data amount, etc.

In some embodiments, reporting data based on the uplink scheduling information indicated by DCI includes:

Determine time domain resources and/or frequency domain resources based on the uplink scheduling information indicated by DCI;

Report data based on time domain resources and/or frequency domain resources.

Here, the time domain resources and/or the frequency domain resources may be allocated by the base station based on the resource reservation status of the base station and/or the data status to be reported by the terminal. For example, time domain resources and/or frequency domain resources may be allocated based on available resources of the base station and BSR and/or SR reported by the terminal.

It should be noted that those skilled in the art can understand that the methods provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

In order to better understand the embodiments of the present disclosure, the technical solution of the present disclosure is further described below through an exemplary embodiment:

The embodiment of the present disclosure provides a data transmission method, which may specifically include:

In related technologies, the uplink transmission resource scheduling process of 4G is shown in Figure 7, and the uplink transmission resource scheduling process of 5G is shown in Figure 8. When there is data to be reported by the UE between the base station (gNodeB) and the UE, the steps may include:

When the UE has data to send, it reports the resource request message SR to the base station;

After receiving the SR, the base station evaluates the resource reservation situation and issues DCI carrying UL Grant to the UE to indicate the UE's uplink scheduling information. The base station will schedule a small number of resource blocks (Resource Block, RB) to the UE;

The UE reports BSR/data (Data) to the base station, and the base station sends new DCI to the UE according to the index value (index) of the BSR and the base station resource reservation situation to adjust the uplink resources;

The 4G base station sends an acknowledgment character or non-acknowledge character (ACK/NACK) to the UE based on the decoding of the received UE data;

The 5G base station will not issue ACK/NACK, but will do so by determining whether the New Data Information (NDI) is inverted.

When the UE has no data to send, it will send a BSR value of 0, that is, BSR==0, so that the base station will no longer perform resource scheduling for the UE on the Physical Uplink Single Control Channel (PUSCH).

As shown in Figure 9, the data transmission method provided by the embodiment of the present disclosure takes power consumption into consideration while avoiding the impact on service perception. After the mobile phone starts the power consumption optimization mechanism, if the UE does not need to send data, the network side Uplink time-frequency resources are also continuously scheduled. If all the prepared data blocks are padding, the UE does not perform the sending task. Specifics may include:

1) When the UE enters the normal data transmission process, if the UE has no data transmission, the UE will report BSR==0 to indicate that the mobile phone does not need to perform uplink data transmission;

2). If the base station turns on the pre-scheduling function, the network side will still continue to schedule uplink resources to the UE by issuing DCI instructions.

3). If it is judged to be scheduled according to DCI instructions and all TB is padding, the UE will give up this transmission task;

4). If the base station continues to require the UE to report, the UE will still refuse until there is data in the Buffer.

5). Finally, the base station will release the connection.

Specifically, as shown in Figure 10, the method may include:

1. Start;

2. If BSR==0 and the power saving policy is enabled, after receiving the uplink scheduling information of the base station, it will be judged whether there is no data in the uplink buffer and only padding can be filled.

a) If TB is all padding;

i.UE does not perform transmission tasks;

ii. If the base station schedules retransmission;

iii. Determine whether there is no data in the upstream buffer

iv. If all the TB is padding, the UE still does not perform the transmission task;

v. Go to step 5;

b) If there is still some data in TB; then go to step 4;

3. The base station schedules uplink time-frequency resources for the UE:

4. The UE performs the uplink data sending task;

5. If the BSR is still reported after the previous BSR task is transmitted, go to step 2; otherwise, if the BSR is no longer reported, the base station releases the link.

6. End.

As shown in Figure 11, this embodiment provides a data transmission device, which is applied to a terminal and may include:

The receiving unit 10 is configured to receive downlink control information DCI;

The determining unit 20 is configured to determine that the DCI indicates uplink scheduling information, and determine that there is no data to be reported;

The stopping unit 30 is configured to stop the reporting operation.

In some embodiments, the device further includes:

The receiving unit is configured to obtain the currently reported buffer status report BSR; if the value of the BSR is 0, receive the downlink control information DCI.

In some embodiments, the determining unit 20 is specifically configured as:

Make sure there is no data to be reported in the terminal's uplink data cache module.

In some embodiments, the determining unit 20 is specifically configured as:

Get the fields contained in the transmission block TB to be reported;

In some embodiments, the determining unit 20 is specifically configured as:

Get the fields contained in TB.

In some embodiments, the device further includes:

The response unit is configured to not respond to the data retransmission instruction when it determines that there is no data to be reported after receiving the data retransmission instruction issued by the base station.

In some embodiments, the device further includes:

The release unit is configured to report indication information instructing to release the transmission link between the terminal and the base station when it is determined not to continue reporting the BSR.

In some embodiments, the release unit is specifically configured as:

In some embodiments, the device further includes:

The reporting unit is configured to report the data based on the uplink scheduling information indicated by the DCI if there is data to be reported.

In some embodiments, the reporting unit is specifically configured as:

Report data based on time domain resources and/or frequency domain resources.

Regarding the devices in the above embodiments, the specific manner in which each module performs operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

An embodiment of the present disclosure provides a communication device, including:

Memory used to store instructions executable by the processor;

processor, connected to memory;

Wherein, the processor is configured to execute the data transmission method provided by any of the foregoing technical solutions.

The processor may include various types of storage media, which are non-transitory computer storage media that can continue to store information stored thereon after the communication device is powered off.

Here, communication equipment includes: terminal or network element.

The processor may be connected to the memory through a bus or the like, and be used to read the executable program stored on the memory, for example, at least one of the methods shown in FIGS. 2 to 6 .

Figure 12 is a block diagram of a terminal 800 according to an exemplary embodiment. For example, the terminal 800 may be a mobile phone, a computer, a digital broadcast user device, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, or the like.

Referring to Figure 12, the terminal 800 may include one or more of the following components: a processing component 802, a memory 804, a power supply component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and communications component 816.

Processing component 802 generally controls the overall operations of terminal 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to generate all or part of the steps of the methods described above. Additionally, processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

Memory 804 is configured to store various types of data to support operations at terminal 800. Examples of such data include instructions for any application or method operating on the terminal 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

Power supply component 806 provides power to various components of terminal 800. Power component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to terminal 800.

Multimedia component 808 includes a screen that provides an output interface between terminal 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. A touch sensor can not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action. In some embodiments, multimedia component 808 includes a front-facing camera and/or a rear-facing camera. When the terminal 800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.

Audio component 810 is configured to output and/or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when terminal 800 is in operating modes, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 804 or sent via communications component 816 . In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

The I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.

Sensor component 814 includes one or more sensors that provide various aspects of status assessment for terminal 800 . For example, the sensor component 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the terminal 800, the sensor component 814 can also detect the position change of the terminal 800 or a component of the terminal 800, the user The presence or absence of contact with the terminal 800, the terminal 800 orientation or acceleration/deceleration and the temperature change of the terminal 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 816 is configured to facilitate wired or wireless communication between the terminal 800 and other devices. The terminal 800 can access a wireless network based on communication standards, such as WiFi, 2G or 3G, or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communications component 816 also includes a near field communications (NFC) module to facilitate short-range communications. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, the terminal 800 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable Gate array (FPGA), controller, microcontroller, microprocessor or other electronic components are implemented for executing the above method.

In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions, such as a memory 804 including instructions, executable by the processor 820 of the terminal 800 to generate the above method is also provided. For example, non-transitory computer-readable storage media may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

Other embodiments of the invention will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common common sense or customary technical means in the technical field that are not disclosed in the present disclosure. . It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

In some cases, any two of the above technical features can be combined into a new method and technical solution without conflict.

In some cases, any two of the above technical features can be combined into a new equipment technical solution without conflict.

It is to be understood that the present invention is not limited to the precise construction described above and illustrated in the accompanying drawings, and that various modifications and changes may be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

A data transmission method, which is executed by a terminal, and the method includes:

Receive downlink control information DCI;

Determine that the DCI indicates uplink scheduling information, and determine that there is no data to be reported;

Stop the reporting operation.
The method according to claim 1, wherein the receiving downlink control information DCI includes:

Get the currently reported cache status report BSR;

If the value of the BSR is 0, downlink control information DCI is received.
The method according to claim 1, wherein determining that there is no data to be reported includes:

It is determined that there is no data to be reported in the uplink data cache module of the terminal.
The method according to claim 3, wherein determining that there is no data to be reported in the uplink data cache module of the terminal includes:

Get the fields contained in the transmission block TB to be reported;

If all the fields included in the TB are padding fields, it is determined that there is no data to be reported in the uplink data cache module of the terminal.
The method according to claim 4, wherein said obtaining the fields contained in the transport block TB to be reported includes:

In response to the uplink scheduling information indicated by the DCI, generate a transport block TB to be reported;

Get the fields contained in the TB.
The method of claim 1, further comprising:

If the data retransmission instruction issued by the base station is received and it is determined that there is no data to be reported, the data retransmission instruction will not be responded to.
The method of claim 2, further comprising:

When it is determined not to continue to report the BSR, indication information instructing to release the transmission link between the terminal and the base station is reported.
The method according to claim 7, wherein the determining not to continue reporting the BSR includes:

Determine not to continue reporting the BSR at the current time according to the reporting cycle of the BSR.
The method of claim 1, further comprising:

If there is data to be reported, the data is reported based on the uplink scheduling information indicated by the DCI.
The method according to claim 9, wherein reporting the data based on the uplink scheduling information indicated by the DCI includes:

Determine time domain resources and/or frequency domain resources based on the uplink scheduling information indicated by the DCI;

The data is reported based on the time domain resources and/or frequency domain resources.
A data transmission device, which is applied to a terminal and includes:

a receiving unit configured to receive downlink control information DCI;

a determining unit configured to determine that the DCI indicates uplink scheduling information, and determine that there is no data to be reported;

Stop unit, configured to stop reporting operations.
The device of claim 11, further comprising:

The receiving unit is configured to obtain the currently reported buffer status report BSR; if the value of the BSR is 0, receive downlink control information DCI.
The device according to claim 11, wherein the determining unit is specifically configured to:

It is determined that there is no data to be reported in the uplink data cache module of the terminal.
The device according to claim 13, wherein the determining unit is specifically configured to:

Get the fields contained in the transmission block TB to be reported;

If all the fields included in the TB are padding fields, it is determined that there is no data to be reported in the uplink data cache module of the terminal.
The device according to claim 14, wherein the determining unit is specifically configured to:

In response to the uplink scheduling information indicated by the DCI, generate a transport block TB to be reported;

Get the fields contained in the TB.
The device of claim 11, further comprising:

The response unit is configured to not respond to the data retransmission instruction when it determines that there is no data to be reported after receiving the data retransmission instruction issued by the base station.
The device of claim 12, wherein the device further comprises:

The release unit is configured to report indication information instructing to release the transmission link between the terminal and the base station when it is determined not to continue reporting the BSR.
The device according to claim 17, wherein the release unit is specifically configured to:

Determine not to continue reporting the BSR at the current time according to the reporting cycle of the BSR.
The device of claim 11, further comprising:

The reporting unit is configured to report the data based on the uplink scheduling information indicated by the DCI if there is data to be reported.
The device according to claim 19, wherein the reporting unit is specifically configured to:

Determine time domain resources and/or frequency domain resources based on the uplink scheduling information indicated by the DCI;

The data is reported based on the time domain resources and/or frequency domain resources.
A communication device, including a processor, a memory, and an executable program stored in the memory and capable of being run by the processor, wherein when the processor runs the executable program, it executes any one of claims 1 to 10 The method provided by the item.
A computer storage medium stores an executable program; after the executable program is executed by a processor, the method as provided in any one of claims 1 to 10 can be implemented.