CN117643096A

CN117643096A - Data transmission method and device, communication equipment and storage medium

Info

Publication number: CN117643096A
Application number: CN202280004553.7A
Authority: CN
Inventors: 王德乾; 刘水
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2022-06-29
Filing date: 2022-06-29
Publication date: 2024-03-01
Also published as: WO2024000316A1

Abstract

The embodiment of the disclosure provides a data transmission method and device, a communication device and a storage medium, wherein the data transmission method is executed by a terminal and comprises the following steps: receiving DCI; determining DCI to indicate uplink scheduling information, and determining that no data to be reported exists; and stopping reporting operation.

Description

Data transmission method and device, communication equipment and storage medium

Technical Field

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

Background

In the related art, regarding a power consumption reduction scheme adopted for power consumption generated in a terminal communication process, an effect of reducing power consumption is often achieved by controlling an uplink data transmission process, for example, reducing an uplink data transmission frequency, but the method often affects a data transmission effect, so that communication may be abnormal. In the related technology, a pre-scheduling mechanism of communication resources between the base station and the terminal often exists, the communication resources are often still scheduled when the terminal does not need to transmit data in an uplink mode, and the terminal is required to report empty data packets. Therefore, the terminal is caused to continuously perform invalid interaction while occupying transmission resources, so that a large amount of unnecessary power consumption is generated by the terminal, and the duration of the terminal is shortened.

Disclosure of Invention

The embodiment of the disclosure provides a data transmission method and device, communication equipment and storage medium.

A first aspect of an embodiment of the present disclosure provides a data transmission method, performed by a terminal, the method including:

receiving downlink control information (Downlink Control Information, DCI);

determining that the DCI indicates uplink scheduling information and determining that no data to be reported exists;

and stopping reporting operation.

A second aspect of an embodiment of the present disclosure provides a data transmission apparatus, applied to a terminal, the apparatus including:

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;

and the stopping unit is configured to stop the reporting operation.

A third aspect of the disclosed embodiments provides a communication device comprising a processor, a memory and an executable program stored on the memory and capable of being executed by the processor, wherein the processor executes the data transmission method as provided in the first aspect when executing the executable program.

A fourth aspect of the disclosed embodiments provides a computer storage medium storing an executable program; the executable program, when executed by the processor, can implement the data transmission method provided in the foregoing first aspect.

According to the technical scheme provided by the embodiment of the disclosure, downlink control information DCI is received; determining that the DCI indicates uplink scheduling information and determining that no data to be reported exists; and stopping reporting operation. . Therefore, when the base station indicates the terminal to transmit data in the uplink, if the terminal does not have data to be reported, reporting operation is not executed, so that operations such as reporting empty data packets still can not be executed when the terminal does not have uplink data transmission requirements. Therefore, the terminal does not perform blank packet reporting operation due to resource pre-scheduling indicated by the base station when uplink data transmission is not needed, so that power consumption caused by continuous reporting operation of the terminal is reduced, and the endurance time of the terminal is prolonged.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of embodiments of the disclosure.

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.

Fig. 1 is a schematic diagram of a wireless communication system according to an exemplary embodiment;

FIG. 2 is a flow chart illustrating a method of data transmission according to an exemplary embodiment;

FIG. 3 is a flow chart illustrating a method of data transmission according to an exemplary embodiment;

FIG. 4 is a flow chart illustrating a method of data transmission according to an exemplary embodiment;

FIG. 5 is a flow chart illustrating a method of data transmission according to an exemplary embodiment;

FIG. 6 is a flow chart illustrating a method of data transmission according to an exemplary embodiment;

fig. 7 is a flowchart illustrating uplink transmission resource scheduling in the related art according to an exemplary embodiment;

fig. 8 is a flow chart illustrating uplink transmission resource scheduling in the related art according to an exemplary embodiment;

fig. 9 is a flow chart illustrating a data transmission method according to an exemplary embodiment;

fig. 10 is a flow chart illustrating a data transmission method according to an exemplary embodiment;

fig. 11 is a schematic diagram showing a structure of a data transmission apparatus according to an exemplary embodiment;

fig. 12 is a schematic structural view of a terminal according to an exemplary embodiment.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying 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 aspects of embodiments of the invention.

The terminology used in the embodiments of the disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the disclosure. As used in this disclosure, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or 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 in embodiments of the present disclosure to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of embodiments of the present disclosure. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

Referring to fig. 1, a schematic structural diagram of a wireless communication system according to an embodiment of the disclosure is shown. As shown in fig. 1, the wireless communication system is a communication system based on a cellular mobile communication technology, and may include: a number of terminals 11 and a number of access devices 12.

Where the terminal 11 may be a device providing voice and/or data connectivity to a user. The terminal 11 may communicate with one or more core networks via a radio access network (Radio Access Network, RAN), and the terminal 11 may be an internet of things terminal such as a sensor device, a mobile phone (or "cellular" phone) and a computer with an internet of things terminal, for example, a stationary, portable, pocket, hand-held, computer-built-in or vehicle-mounted device. Such as a 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 (access terminal), user device (user terminal), user agent (user agent), user equipment (user device), or user terminal (user equipment). Alternatively, the terminal 11 may be an unmanned aerial vehicle device. Alternatively, the terminal 11 may be a vehicle-mounted device, for example, a car-driving computer having a wireless communication function, or a wireless communication device externally connected to the car-driving computer. Alternatively, the terminal 11 may be a roadside device, for example, a street lamp, a signal lamp, or other roadside devices having a wireless communication function.

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

Wherein the access device 12 may be an evolved access device (eNB) employed in a 4G system. Alternatively, access device 12 may be an access device (gNB) in a 5G system that employs a centralized and distributed architecture. When the access device 12 employs a centralized and distributed architecture, it typically includes a Centralized Unit (CU) and at least two Distributed Units (DUs). A protocol stack of a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer, a radio link layer control protocol (Radio Link Control, RLC) layer, and a medium access control (Media Access Control, MAC) layer is provided in the centralized unit; a Physical (PHY) layer protocol stack is provided in the distribution unit, and the specific implementation of the access device 12 is not limited by the embodiments of the present disclosure.

A wireless connection may be established between access device 12 and terminal 11 over a wireless air interface. In various embodiments, the wireless air interface is a fourth generation mobile communication network technology (4G) standard-based wireless air interface; or, the wireless air interface is a wireless air interface based on a fifth generation mobile communication network technology (5G) standard, for example, the wireless air interface is a new air interface; alternatively, the wireless air interface may be a wireless air interface based on a 5G-based technology standard of a next generation mobile communication network.

Optionally, the above wireless communication system may further 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, MME) in an evolved packet core network (Evolved Packet Core, EPC). Alternatively, the network management device may be other core network devices, such as a Serving GateWay (SGW), a public data network GateWay (Public Data Network GateWay, PGW), a policy and charging rules function (Policy and Charging Rules Function, PCRF) or a home subscriber server (Home Subscriber Server, HSS), etc. The embodiment of the present disclosure is not limited to the implementation form of the network management device 13.

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

s110: receiving DCI;

s120: determining DCI to indicate uplink scheduling information, and determining that no data to be reported exists;

s130: and stopping reporting operation.

In the embodiment of the present disclosure, the terminal may be a User Equipment (UE) configured to communicate with a network side object such as a base station. Taking the communication between the terminal and the base station as an example, the DCI may be downlink control information issued by the base station, for example, the DCI may be used to indicate uplink data transmission of the terminal, and/or indicate information such as time domain resources and/or frequency domain resources for uplink transmission, which are scheduled to the terminal.

In one embodiment, the DCI may be issued by the base station based on a resource request message (Scheduling Request, SR) reported by the terminal, or may be issued by the base station itself, for example, the DCI issued by the base station based on an on pre-scheduling function. The SR may be transmitted to the base station through a physical uplink control channel (physical uplink control channel, PUCCH).

In the related art, the pre-scheduling function can be a scheduling function that a network side object such as a base station continuously monitors uplink transmission data of a terminal, and reduces that a data reporting requirement suddenly appearing by the terminal cannot be responded to and started. When the pre-scheduling function is started, the base station also issues DCI to instruct the terminal to execute reporting operation when the base station does not receive the SR sent by the terminal. For example, the terminal may report a null data packet based on DCI when there is no data reporting requirement.

In an embodiment, the UpLink scheduling information may be information indicating that the terminal performs the reporting operation, for example, the UpLink scheduling information may carry an UpLink Grant (ULGrant) for indicating that the terminal starts UpLink transmission. The DCI carrying the ULGrant may be sent to the terminal through a physical downlink control channel (physical downlink control channel, PDCCH).

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

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

The BSR may indicate a Buffer status of a Buffer module (Buffer) storing data to be reported by the terminal, for example, when the data to be reported is stored in the Buffer, the BSR may indicate a data storage amount or a storage rate of the Buffer, and so on. When there is no data to be reported in Buffer, the BSR value may be 0.

In one embodiment, determining that there is no data to report may include: determining whether to report an SR in a first time window before receiving DCI; if the SR is not reported in the first time window, determining that the data to be reported does not exist. The first time window may be a fixed value, for example, 100ms or 1s, or the first time window may also be determined according to the uplink data transmission condition of the terminal.

For example, a first average duration between a first time of reporting the SR historically and a second time of receiving DCI corresponding to the SR is determined according to the terminal reporting operation record, and the first time window may be determined based on the first average duration. For example, the first time window may be equal to the first average duration, or may be equal to a predetermined proportion or a predetermined multiple of the first average duration.

In an embodiment, the first average duration may be an average duration between multiple sets of first time and second time within a preset period, for example, the preset period may be a fixed value, for example, 1h or 1 day, or may be determined according to a data uplink transmission situation of the terminal. The higher the data uplink transmission frequency of the terminal, the shorter the preset period can be, so that the accuracy of determining the first average duration based on the preset period is ensured, and the higher data calculation amount is not generated.

In one embodiment, the historical reporting operation record of the terminal may be determined by operation log information of the terminal, for example, by retrieving an operation log of the terminal for a certain period of time, to determine the historical reporting operation record of the terminal for the period of time.

Therefore, the terminal can send the SR request scheduling resource to the base station when the terminal needs to report the data, so that whether the terminal has the data to be reported or not can be determined based on the sending condition of the SR.

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

In one embodiment, determining whether the data to be reported exists in the storage location of the data to be reported may be determining whether the BSR value reported before receiving the DCI is 0; if the data is 0, determining that the data to be reported does not exist in the storage position of the data to be reported, and if the data is not 0, determining that the data to be reported exists in the storage position 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 to determine whether the value of the BSR reported last time before receiving the DCI is 0, or whether the value of the BSR reported in the second time window before receiving the DCI is 0, etc. The second time window may be a fixed value, for example, 100ms or 1s, or the second time window may be determined according to the uplink data transmission situation of the terminal.

For example, a second average duration between a third time when the BSR is reported historically and a fourth time when DCI corresponding to the BSR is received may be determined according to the terminal reporting operation record, and the second time window may be determined based on the second average duration. For example, the second time window may be equal to the second average duration, or may be equal to a preset proportion or a preset multiple of the second average duration.

In an embodiment, the second average duration may be an average value of durations between the third time and the fourth time in a preset period, for example, the preset period may be a fixed value, for example, 1h or 1 day, or may be determined according to a data uplink transmission condition of the terminal. The higher the data uplink transmission frequency of the terminal, the shorter the preset period can be, and the like, so that the accuracy of determining the second average duration based on the preset period is ensured, and higher data calculation amount cannot be generated.

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

For example, when all the field information included in the TB is a Padding field (Padding), it indicates that the terminal does not have data to be reported, and at this time, if the uplink scheduling information terminal responding to the DCI is to report an empty packet, it may be determined that there is no data to be reported in the storage location of the data to be reported.

In one embodiment, determining that there is no data to report may include: and determining that the data to be reported in the target duration does not exist. For example, the target duration may be a fixed value, or may be determined according to the uplink transmission record of the terminal data. For example, the higher the uplink transmission frequency of the terminal data, the shorter or longer the target duration may be.

In one embodiment, the reporting operation is stopped, which may be to stop reporting operations in response to DCI. For example, stopping TB reporting operations in response to DCI, etc.

In one embodiment, the reporting operation is stopped, and the reporting operation may also be stopped in a preset period. The preset period may be a fixed value, for example, the reporting operation is stopped within 1s, or the preset period may be determined according to the uplink transmission record of the terminal data, for example, the higher the uplink transmission frequency of the terminal history data is, the shorter or longer the preset period may be.

In this way, when DCI indicating the terminal to transmit data in the uplink by the base station is detected, whether the terminal has data to be reported or not is detected, so that the terminal does not need to execute operations such as reporting empty data packets when no uplink data transmission requirement exists. Therefore, the terminal does not perform blank packet reporting operation due to resource pre-scheduling indicated by the base station when uplink data transmission is not needed, so that power consumption caused by continuous reporting operation of the terminal is reduced, and the endurance time of the terminal is prolonged.

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

s101: acquiring a currently reported Buffer Status Report (BSR);

s102: if the value of the BSR is 0, DCI is received.

In the embodiment of the present disclosure, the BSR currently reported may be the BSR currently reported at the current time or the BSR recently reported from the current time, or may be the BSR to be reported currently generated by the terminal. The BSR may indicate an amount of data buffered in a data Buffer module (Buffer) to be reported.

Here, when the BSR value is 0, it may be determined that the terminal does not currently have a data reporting requirement.

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

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

In one embodiment, if the BSR value is 0, receiving the downlink control information DCI may include: if the BSR value is 0, determining the current running condition of the terminal; and receiving downlink control information DCI when the current running condition of the terminal meets the preset condition. The current operation condition of the terminal may indicate the current power consumption level of the terminal, for example, the current operation condition of the terminal may include at least one of the following: the method comprises the steps of current average power consumption of a terminal, current resource occupancy rate of the terminal, current working mode of the terminal and current residual capacity of the terminal.

In one embodiment, the preset condition may be to indicate that the current power consumption level of the terminal is high, for example, the preset condition may be at least one of the following: the current average power consumption of the terminal reaches the upper limit value of power consumption, the current resource occupancy rate of the terminal reaches the upper limit value of occupancy rate, the current working mode of the terminal is a power saving mode, the current residual electric quantity of the terminal is lower than the lower limit value of electric quantity, and the like.

In one embodiment, obtaining the BSR currently reported may include: determining whether a BSR needs to be reported currently; if so, acquiring the currently reported BSR. Whether the BSR needs to be reported currently is determined, and whether the BSR needs to be reported currently can be determined according to the reporting operation condition of the terminal. For example, whether the BSR needs to be reported currently or not may be determined according to the data amount of the data to be reported by the terminal or the BSR reporting condition.

In one embodiment, determining whether the BSR is currently required to be reported may be to determine whether the terminal needs to report the BSR within a target time window. For example, the target time window may be determined according to BSR reporting conditions. Illustratively, the determination may be based on a BSR reporting period or a BSR history reporting total duration, etc.

In some embodiments, determining whether the BSR needs to be reported currently may further determine whether the BSR needs to be reported at the current time according to a reporting period of the BSR.

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

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.

Therefore, whether the current terminal has data reporting requirements or not can be determined according to the current reporting or the BSR to be reported, so that whether the terminal needs to report data or not can be determined more accurately, and the reporting operation of the terminal can be controlled more accurately.

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

s110: receiving DCI;

s121: determining DCI indicating uplink scheduling information, and determining that no data to be reported exists in an uplink data cache module of a terminal;

s130: and stopping reporting operation.

In the embodiment of the present disclosure, an uplink data Buffer module (Buffer) may be used to Buffer data to be reported by a terminal, for example, to store data to be reported by the terminal in a target duration. And determining whether data to be reported exists in an uplink data cache module of the terminal.

In an embodiment, it is determined that the data to be reported does not exist in the uplink data buffer module of the terminal, and it may be determined that the data to be reported does not exist in the uplink data buffer module of the terminal when the BSR value reported before the DCI is received is determined to be 0, and if the value is not 0, the data to be reported exists in the uplink data buffer module of the terminal.

In one embodiment, the value of BSR reported before DCI is received is determined to be 0, which may be the value of BSR reported last time before DCI is received is determined to be 0, or the value of BSR reported in a second time window before DCI is received is determined to be 0, etc. The second time window may be a fixed value, for example, 100ms or 1s, or the second time window may be determined according to the uplink data transmission situation of the terminal.

In one embodiment, determining that there is no data to be reported in the uplink data buffer module of the terminal may include: and determining that the data to be reported does not exist in an uplink data caching module of the terminal based on the information to be reported generated by the terminal in response to the DCI. For example, the information to be reported may be a Transport Block (TB), and it may be determined that the uplink data buffer module of the terminal does not have data to be reported based on the field information included in the TB.

In one embodiment, determining that there is no data to be reported in the uplink data buffer module of the terminal may include: and determining that the data to be reported in the target duration does not exist in an uplink data cache module of the terminal. For example, the target duration may be a fixed value, or may be determined according to the uplink transmission record of the terminal data. For example, the higher the uplink transmission frequency of the terminal data, the shorter or longer the target duration may be.

In some embodiments, step S121 may include:

acquiring a field contained in a Transmission Block (TB) to be reported;

if all the fields contained in the TB are filling fields, determining that the data to be reported does not exist in an uplink data cache module of the terminal.

In the embodiment of the present disclosure, when all field information included in the TB is a Padding field (Padding), it indicates that the terminal does not have data to be reported, and at this time, in response to that the uplink scheduling information of the DCI is an empty packet to be reported, it may be determined that there is no data to be reported in a storage location of the data to be reported.

Here, the padding field may be information to be padded in the TB when the TB is generated and when there is no data to be carried in the TB for reporting, for example, may be null data, or may be a byte or the like which is predetermined according to an inter-terminal and base station protocol.

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

generating a Transport Block (TB) to be reported in response to uplink scheduling information indicated by DCI;

the fields contained in the TB are obtained.

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

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

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

Therefore, based on the field contained in the TB to be reported, whether the data to be reported exist in the terminal or not can be determined more rapidly and accurately, so that the reporting operation of the terminal can be controlled more accurately, and the power consumption of the terminal is reduced.

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

s110: receiving DCI;

s130: stopping reporting operation;

s140: if a data retransmission instruction issued by the base station is received, the data retransmission instruction is not responded when the data to be reported does not exist.

In the embodiment of the present disclosure, the data retransmission instruction may be a retransmission instruction issued by the base station when the base station does not detect a TB or the like reported by the terminal in response to the DCI, or may be DCI retransmitted by the base station.

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

For example, determining that there is no data to be reported may be determining whether to report an SR within a first time window before receiving a data retransmission instruction; if the SR is not reported in the first time window, determining that the data to be reported does not exist.

In one embodiment, determining that there is no data to report may include: and determining that the data to be reported does not exist in the storage position of the data to be reported. The storage location of the data to be reported may be a data Buffer module (Buffer) 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 determining whether the BSR value reported before receiving the data retransmission instruction is 0; if the data is 0, determining that the data to be reported does not exist in the storage position of the data to be reported, and if the data is not 0, determining that the data to be reported exists in the storage position of the data to be reported.

In one embodiment, determining whether the BSR value reported before the data retransmission instruction is received is 0 may be to determine whether the BSR value reported last time before the data retransmission instruction is received is 0, or to determine whether the BSR value reported in the second time window before the data retransmission instruction is received is 0, or the like.

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

For example, when all the field information included in the TB is a Padding field (Padding), it indicates that the terminal does not have data to be reported, and at this time, the uplink scheduling information terminal responding to the data retransmission instruction is to report an empty packet, and it may be determined that there is no data to be reported in the storage location of the data to be reported.

In this way, in the time when the terminal does not have data to be reported, no matter whether DCI is received or a data retransmission instruction and the like continuously issued by the base station, the terminal does not execute reporting operation, thereby better controlling the reporting operation of the terminal and reducing the power consumption of the terminal.

As shown in fig. 6, the data transmission method may further include:

s160: and when the BSR is not continuously reported, reporting the indication information for indicating to release the transmission link between the terminal and the base station.

In the embodiment of the present disclosure, determining not to report the BSR may be determining not to report the BSR according to the reporting operation condition of the terminal. For example, it may be determined that the BSR is not continuously reported according to the data amount of the data to be reported by the terminal or the BSR reporting condition.

In one embodiment, determining not to continue reporting the BSR may be for determining that the terminal does not continue reporting the BSR within the target time window. For example, the target time window may be determined according to BSR reporting conditions. Illustratively, the determination may be based on a BSR reporting period or a BSR history reporting total duration, etc.

In some embodiments, step S160 may include:

and determining that the BSR is not continuously reported at the current moment according to the reporting period of the BSR.

In one embodiment, the determining that the BSR is not continuously reported at the current time according to the reporting period of the BSR may be determining that the BSR is not continuously reported at the current time according to the current time and the reporting period of the BSR.

For example, according to the current time and the BSR reporting time indicated by the BSR reporting period, it is determined that the BSR is not continuously reported at the current time.

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 is not continuously reported.

Therefore, when the terminal does not need to continuously report the BSR, the terminal can be determined to temporarily not need to execute reporting operation to the base station, so that the release of the transmission link can be indicated, the continuous occupation of the transmission link resource is reduced, and the availability of the transmission link resource is improved.

In some embodiments, the method may further comprise:

if the data to be reported exist, reporting the data based on the uplink scheduling information indicated by the DCI.

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

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

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

reporting data based on the time domain resources and/or the frequency domain resources.

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

It should be noted that, as those skilled in the art may understand, the methods provided in the embodiments of the present disclosure may be performed alone or together with some methods in the embodiments of the present disclosure or some methods in the related art.

For a better understanding of the embodiments of the present disclosure, the following further describes the technical solution of the present disclosure by means of an exemplary embodiment:

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

in the related art, the uplink transmission resource scheduling process of 4G is shown in fig. 7, and the uplink transmission resource scheduling process of 5G is shown in fig. 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, reporting a resource request message SR to the base station;

after receiving the SR, the base station evaluates according to the Resource reservation condition and transmits DCI carrying UL Grant to the UE for indicating the uplink scheduling information of the UE, and the base station schedules a small number of Resource Blocks (RBs) to the UE;

the UE reports BSR/Data (Data) to the base station, and the base station issues new DCI to the UE according to the index value (index) of the BSR and the base station resource reservation condition, and adjusts uplink resources;

the 4G base station sends acknowledgement characters or Non-acknowledgement characters (Acknowledge character/Non-Acknowledge character, ACK/NACK) to the UE according to the received decoding condition of the UE data;

the 5G base station does not issue an ACK/NACK but rather by determining whether the new data indication (New Data Information, NDI) is inverted.

When the UE has no data to transmit, the BSR value is 0, i.e., bsr= =0, so that the base station does not perform resource scheduling of the physical uplink single control channel (Physical Uplink Single Control Channel, PUSCH) for the UE.

As shown in fig. 9, in the data transmission method provided in the embodiment of the present disclosure, power consumption is considered, and meanwhile, influence on service perception is avoided, after a mobile phone starts a power consumption optimization mechanism, if the UE does not need to transmit data, the network side continuously schedules uplink time-frequency resources, and if all the prepared data blocks are padding, the UE does not execute a transmission task. The method specifically comprises the following steps:

1) When the UE enters a normal data transmission flow, if the UE does not transmit data, the UE reports bsr= 0 to indicate that the mobile phone does not need to transmit uplink data;

2) If the base station opens the prescheduling function, the network side still can continuously schedule uplink resources to the UE by issuing DCI indication.

3) If judging that the scheduling is performed according to the DCI indication, the UE gives up the transmission task at this time if all the TB is padding;

4) If the base station continuously requires the UE to report, the UE still refuses until the Buffer has data.

5) Eventually the base station will release the connection.

Specifically, as shown in fig. 10, the method may include:

1. starting;

2. if bsr= =0 and the power saving policy is on, after the uplink scheduling information of the base station is received later, it is determined whether there is no data in the uplink Buffer and only padding can be performed.

a) If the TB is padding;

the UE does not execute the transmitting task;

if the base station schedules a retransmission;

third, judging whether there is no data in the uplink Buffer

if all of the TBs are padding, the UE still does not perform the transmit task;

v. go to step 5;

b) If there is still partial data in the TB; go to step 4;

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

4. the UE executes an uplink data transmission task;

5. if the BSR is still reported after the previous BSR task is transmitted, the step 2 is switched; otherwise, if the BSR is not reported any more, the base station releases the link.

6. And (5) ending.

As shown in fig. 11, the present embodiment provides a data transmission device, which is applied to a terminal and may include:

A receiving unit 10 configured to receive downlink control information DCI;

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

and a stopping unit 30 configured to stop the reporting operation.

In some embodiments, the apparatus further comprises:

the receiving unit is configured to acquire a Buffer Status Report (BSR) which is currently reported; if the value of the BSR is 0, receiving downlink control information DCI.

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

and determining that the data to be reported does not exist in an uplink data cache module of the terminal.

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

acquiring a field contained in a Transmission Block (TB) to be reported;

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

the fields contained in the TB are obtained.

In some embodiments, the apparatus further comprises:

and the response unit is configured to not respond to the data retransmission instruction when determining that the data to be reported does not exist if the data retransmission instruction issued by the base station is received.

In some embodiments, the apparatus further comprises:

and the release unit is configured to report the indication information for indicating the transmission link between the release terminal and the base station when the BSR is not continuously reported.

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

In some embodiments, the apparatus further comprises:

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

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

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

The embodiment of the disclosure provides a communication device, comprising:

a memory for storing processor-executable instructions;

a processor connected with the memory;

wherein the processor is configured to execute the data transmission method provided in any of the foregoing technical solutions.

The processor may include various types of storage medium, which are non-transitory computer storage media, capable of continuing to memorize information stored thereon after a power down of the communication device.

Here, the communication apparatus includes: a terminal or a network element.

The processor may be coupled to the memory via a bus or the like for reading an executable program stored on the memory, for example, at least one of the methods shown in fig. 2-6.

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

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

The processing component 802 generally controls overall operation of the terminal 800, such as operations associated with display, telephone 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. Further, the processing component 802 can include one or more modules that facilitate interactions between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

The memory 804 is configured to store various types of data to support operations at the 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, and the like. The memory 804 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

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

The multimedia component 808 includes a screen between the terminal 800 and the user that provides an output interface. 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 a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. The front camera and/or the rear camera may receive external multimedia data when the terminal 800 is in an operation mode, such as a photographing mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the terminal 800 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 further includes a speaker for outputting audio signals.

The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 814 includes one or more sensors for providing status assessment of various aspects of the terminal 800. For example, the sensor assembly 814 may detect an on/off state of the device 800, a relative positioning of the assemblies, such as a display and keypad of the terminal 800, the sensor assembly 814 may also detect a change in position of the terminal 800 or a component of the terminal 800, the presence or absence of user contact with the terminal 800, an orientation or acceleration/deceleration of the terminal 800, and a change in temperature of the terminal 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The 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 assembly 814 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 816 is configured to facilitate communication between the terminal 800 and other devices, either wired or wireless. The terminal 800 may access a wireless network based on a communication standard, 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, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may 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 can be implemented 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 Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.

In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 804 including instructions executable by processor 820 of terminal 800 to generate the above-described method. For example, the non-transitory computer readable storage medium 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 apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. 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 technical features can be combined into a new method technical scheme under the condition of no conflict.

In some cases, any two technical features mentioned above can be combined into a new device technical scheme without collision.

It is to be understood that the invention is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the invention is limited only by the appended claims.

Claims

A data transmission method, wherein the method is performed by a terminal, the method comprising:

receiving downlink control information DCI;

Determining that the DCI indicates uplink scheduling information and determining that no data to be reported exists;

and stopping reporting operation.
The method of claim 1, wherein the receiving downlink control information, DCI, comprises:

acquiring a currently reported Buffer Status Report (BSR);

and if the value of the BSR is 0, receiving downlink control information DCI.
The method of claim 1, wherein the determining that there is no data to report comprises:

and determining that the data to be reported does not exist in an uplink data cache module of the terminal.
The method of claim 3, wherein the determining that there is no data to be reported in the uplink data cache module of the terminal comprises:

acquiring a field contained in a Transmission Block (TB) to be reported;

if all the fields contained in the TB are filling fields, determining that no data to be reported exists in an uplink data cache module of the terminal.
The method of claim 4, wherein the obtaining the field contained in the transport block TB to be reported comprises:

generating a Transport Block (TB) to be reported in response to the uplink scheduling information indicated by the DCI;

and acquiring a field contained in the TB.
The method of claim 1, wherein the method further comprises:

If a data retransmission instruction issued by the base station is received, and when the fact that the data to be reported does not exist is determined, the data retransmission instruction is not responded.
The method of claim 2, wherein the method further comprises:

and when the BSR is determined not to be continuously reported, reporting indication information for indicating to release a transmission link between the terminal and the base station.
The method of claim 7, wherein the determining not to continue reporting the BSR comprises:

and determining that the BSR is not continuously reported at the current moment according to the reporting period of the BSR.
The method of claim 1, wherein the method further comprises:

and if the data to be reported exist, reporting the data based on the uplink scheduling information indicated by the DCI.
The method of claim 9, wherein the reporting the data based on the uplink scheduling information indicated by the DCI comprises:

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

and reporting the data based on the time domain resource and/or the frequency domain resource.
A data transmission apparatus, wherein the apparatus is applied to a terminal, the apparatus comprising:

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;

and the stopping unit is configured to stop the reporting operation.
The apparatus of claim 11, wherein the apparatus further comprises:

the receiving unit is configured to acquire a Buffer Status Report (BSR) which is currently reported; and if the value of the BSR is 0, receiving downlink control information DCI.
The apparatus of claim 11, wherein the determining unit is specifically configured to:

and determining that the data to be reported does not exist in an uplink data cache module of the terminal.
The apparatus of claim 13, wherein the determining unit is specifically configured to:

acquiring a field contained in a Transmission Block (TB) to be reported;

if all the fields contained in the TB are filling fields, determining that no data to be reported exists in an uplink data cache module of the terminal.
The apparatus of claim 14, wherein the determining unit is specifically configured to:

generating a Transport Block (TB) to be reported in response to the uplink scheduling information indicated by the DCI;

and acquiring a field contained in the TB.
The apparatus of claim 11, wherein the apparatus further comprises:

And the response unit is configured to not respond to the data retransmission instruction when determining that the data to be reported does not exist if the data retransmission instruction issued by the base station is received.
The apparatus of claim 12, wherein the apparatus further comprises:

and the release unit is configured to report indication information for indicating to release a transmission link between the terminal and the base station when the BSR is determined not to be continuously reported.
The apparatus of claim 17, wherein the release unit is specifically configured to:

and determining that the BSR is not continuously reported at the current moment according to the reporting period of the BSR.
The apparatus of claim 11, wherein the apparatus further comprises:

and the reporting unit is configured to report the data based on the uplink scheduling information indicated by the DCI if the data to be reported exists.
The apparatus of claim 19, wherein the reporting unit is specifically configured to:

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

and reporting the data based on the time domain resource and/or the frequency domain resource.
A communication device comprising a processor, a memory and an executable program stored on the memory and capable of being run by the processor, wherein the processor performs the method as provided in any one of claims 1 to 10 when running the executable program.
A computer storage medium storing an executable program; the executable program, when executed by a processor, is capable of implementing the method as provided in any one of claims 1 to 10.