WO2019109353A1 - 缓存状态报告传输和装置 - Google Patents

缓存状态报告传输和装置 Download PDF

Info

Publication number
WO2019109353A1
WO2019109353A1 PCT/CN2017/115300 CN2017115300W WO2019109353A1 WO 2019109353 A1 WO2019109353 A1 WO 2019109353A1 CN 2017115300 W CN2017115300 W CN 2017115300W WO 2019109353 A1 WO2019109353 A1 WO 2019109353A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink
shared channel
time
duration
available
Prior art date
Application number
PCT/CN2017/115300
Other languages
English (en)
French (fr)
Inventor
江小威
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN201780002117.5A priority Critical patent/CN108401517B/zh
Priority to PCT/CN2017/115300 priority patent/WO2019109353A1/zh
Priority to PCT/CN2018/071406 priority patent/WO2019109447A1/zh
Priority to CN201880000012.0A priority patent/CN108476432B/zh
Priority to US16/472,744 priority patent/US11071129B2/en
Priority to PCT/CN2018/073259 priority patent/WO2019109478A1/zh
Priority to CN202210376781.9A priority patent/CN114828083A/zh
Priority to EP18886442.5A priority patent/EP3695643A4/en
Priority to CN201880000034.7A priority patent/CN108391462B/zh
Publication of WO2019109353A1 publication Critical patent/WO2019109353A1/zh
Priority to US17/333,455 priority patent/US11877280B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/535—Allocation or scheduling criteria for wireless resources based on resource usage policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a cache status report transmission method, a cache status report transmission device, an electronic device, and a computer readable storage medium.
  • the user equipment triggers the BSR (cache status report) after receiving the UR grant (uplink resource allocation indication information) sent by the base station in the LTE (Long Term Evolution) or the NR (New Radio). And determine whether the BSR can be transmitted to the base station.
  • the BSR cache status report
  • UR grant uplink resource allocation indication information
  • the BSR is required to be carried by the Up Link Shared Channel (ULSCH) resource. If no uplink shared channel resource is available, the SR (Scheduling Request) needs to be sent to the base station to request the uplink shared channel resource.
  • ULSCH Up Link Shared Channel
  • the user equipment may have different understandings of the "immediate" judgment, so that it is impossible to accurately determine how long the uplink shared channel resource is counted as available uplink shared channel resources after the BSR triggering time.
  • TTI Transmission Time Interval
  • the present invention proposes a cache status report transmission method, a cache status report transmission device, an electronic device, and a computer readable storage medium to solve the technical problems in the related art.
  • a method for transmitting a buffer status report which is applicable to a user equipment, and the method includes:
  • the buffer status report is transmitted to the base station by using the available uplink shared channel resource.
  • the method further includes:
  • the determining the estimated duration according to the time interval includes:
  • the maximum time interval is the estimated duration
  • the time interval corresponding to the maximum transmission duration of the uplink shared channel in the association relationship table is determined as the estimated duration.
  • the determining, according to the configuration message, the maximum transmission duration of the uplink shared channel includes:
  • the maximum shared channel transmission duration is obtained from the association relationship table as the maximum transmission duration of the uplink shared channel.
  • the determining the estimated duration according to the time interval includes:
  • Determining a shared channel transmission duration in a priority order restriction parameter of a logical channel in the configuration message The maximum time interval in the association table with the time interval is taken as the estimated duration.
  • the determining the estimated duration according to the time interval includes:
  • the determining the estimated duration according to the time interval includes:
  • the method further includes:
  • the configuration information includes a configuration duration corresponding to the logical channel required for transmitting the buffer status report, where the configuration duration is equal to the shared channel transmission duration and the time interval.
  • the configured duration is used as the estimated duration.
  • the method further includes:
  • determining a preset interval corresponding to the carrier of the transmission buffer status report, where the preset interval is that the uplink resource allocation indication is received from the user equipment The processing time required by the user equipment from the end time of the physical downlink control channel where the information is located, to the latest possible start time of the physical downlink shared channel transmission;
  • Determining whether there is an uplink available in the uplink transmission opportunity in the uplink transmission opportunity in the time range of the estimated duration from the triggering time of the buffer status report or the time from the physical downlink control channel Shared channel resources include:
  • the transmitting the buffer status report to the base station by using the available uplink shared channel resource includes:
  • the available uplink shared channel resource can carry a buffer status report, and if the buffer status report can be carried, the uplink sharing is performed.
  • the channel resource transmits a buffer status report to the base station.
  • the method further includes:
  • the uplink shared channel resource is requested by the sent scheduling request, and the buffer status report is transmitted to the base station by using the requested uplink shared channel resource.
  • the uplink shared channel resource is requested by the random access request to the base station, and the buffer status report is transmitted to the base station by using the requested uplink shared channel resource.
  • the determining whether to send the scheduling request includes:
  • the medium access control entity is configured to use the available uplink control channel resource to determine to send a scheduling request, otherwise, it is determined not to send the scheduling request.
  • the determining whether to send the scheduling request includes:
  • the medium access control entity is configured to use the available uplink control channel resource to determine to send a scheduling request, otherwise, it is determined not to send the scheduling request.
  • the determining whether to send the scheduling request includes:
  • the preset interval is from the end time of receiving the physical downlink control channel where the uplink resource allocation indication information is received by the user equipment, to the most The possible start time of the physical downlink shared channel transmission, and the processing time required by the user equipment;
  • the medium access control entity is configured to use the available uplink control channel resource to determine to send a scheduling request, otherwise, it is determined not to send the scheduling request.
  • the determining whether to send the scheduling request includes:
  • the medium access control entity is configured with available physical uplink control channel resources, it is determined to send a scheduling request, otherwise, it is determined not to send a scheduling request.
  • the method further includes:
  • the scheduling request is sent by using the available uplink control channel resources that are closest to the current time.
  • a buffer status report transmission apparatus which is applicable to a user equipment, and the apparatus includes:
  • Configuring a message receiving module configured to receive a configuration message sent by the base station
  • a time interval determining module configured to determine, according to the configuration message, a time interval of uplink transmission corresponding to the uplink resource allocation indication information sent by the base station and the uplink resource allocation indication information;
  • An estimated duration determining module configured to determine an estimated duration according to the time interval
  • a time determination module configured to determine a trigger time of the buffer status report and a time of the most recent physical downlink control channel before the trigger time of the buffer status report;
  • a resource determining module configured to determine a triggering time reported from the cache status or from the physical Whether the uplink shared channel resource available in the uplink transmission opportunity exists in the uplink transmission opportunity within the time range of the estimated duration from the time of the control channel;
  • the report transmission module is configured to transmit a buffer status report to the base station by using the available uplink shared channel resource if there is an uplink shared channel resource available in the uplink transmission opportunity.
  • the device further includes:
  • a duration determining module configured to determine, according to the configuration message, a maximum transmission duration of the uplink shared channel
  • the estimated duration determining module includes:
  • Obtaining a sub-module configured to obtain, from the configuration message, a relationship table between a shared channel transmission duration and the time interval;
  • Determining a sub-module configured to determine a time interval corresponding to a shared channel transmission duration in the association relationship table that is less than a maximum transmission duration of the uplink shared channel, where a maximum time interval is the estimated duration;
  • the time interval corresponding to the maximum transmission duration of the uplink shared channel in the association relationship table is determined as the estimated duration.
  • the duration determining module is configured to determine, according to a priority order limiting parameter of the logical channel in the configuration message, an uplink shared channel maximum transmission duration; if the logical channel has no uplink sharing in the priority order limiting parameter The maximum transmission duration of the channel is obtained, and the maximum shared channel transmission duration is obtained from the association table as the maximum transmission duration of the uplink shared channel.
  • the estimated duration determining module is configured to determine, in a priority order limiting parameter of the logical channel in the configuration message, a maximum time interval in a relationship table between a shared channel transmission duration and the time interval as The estimated duration.
  • the estimated duration determining module is configured to obtain, from the configuration message, an association relationship between a shared channel transmission duration and the time interval, and determine that a minimum time interval in the association relationship table is the pre- Estimate the duration.
  • the estimated duration determining module is configured to obtain, from the configuration message, an association relationship between a shared channel transmission duration and the time interval; and each time in the association table according to a preset algorithm. The interval is calculated, and the calculation result is taken as the estimated duration.
  • the estimated duration determining module is further configured to: before the determining the estimated duration according to the time interval, if the configuration information includes a configuration duration corresponding to a logical channel required for transmitting a buffer status report, The configuration duration is equal to a specified time interval in the association table between the shared channel transmission duration and the time interval; and the configured duration is used as the estimated duration.
  • the device further includes:
  • the preset interval determining module is configured to determine a preset interval corresponding to the carrier of the transmission buffer status report before determining whether there is an uplink shared channel resource available in the uplink transmission opportunity, where the preset interval is a slave user equipment The processing time required by the user equipment from the end time of receiving the physical downlink control channel where the uplink resource allocation indication information is located, to the latest possible start time of the physical downlink shared channel transmission;
  • the resource determining module is configured to determine whether the duration of the trigger time of the available uplink shared channel resource to the buffer status report is greater than the preset interval. If the value is greater than, determine that there is an uplink share available in the uplink transmission opportunity. Channel resources.
  • the report transmission module is configured to determine whether the available uplink shared channel resource can carry a buffer status report if there is an uplink shared channel resource available in the uplink transmission opportunity, and if the buffer status report can be carried, The uplink shared channel resource transmits a buffer status report to the base station.
  • the device further includes:
  • the sending determining module is configured to: if there is no uplink shared channel resource available in the uplink transmission opportunity, determine to trigger the scheduling request, and determine whether to send the scheduling request, where the time at which the scheduling request is triggered is determined as the scheduling request triggering time;
  • the resource requesting module is configured to: if the sending determining module determines to send the scheduling request, request the uplink shared channel resource by using the sent scheduling request, where the report transmission module is configured to transmit to the base station by using the requested uplink shared channel resource. Cache status report.
  • a random access module configured to: if the sending determining module determines not to send a scheduling request, by initiating a random access request to the base station to uplink shared channel resources, where the report transmission module is configured to pass the requested uplink shared channel resource A buffer status report is transmitted to the base station.
  • the sending determining module includes:
  • the first resource determining sub-module is configured to determine, from the triggering time of the scheduling request, a time period of each physical downlink control channel after the triggering time of the scheduling request as a starting point, and the duration of the estimated duration Within the scope, is there any uplink shared channel resource available in the uplink transmission opportunity;
  • a first resource determining submodule configured to determine, for an uplink transmission opportunity that does not have an available uplink shared channel resource, whether the medium access control entity is configured with an available uplink control channel within an estimated duration corresponding to the uplink transmission opportunity Resource
  • the first sending determining submodule is configured to: if the uplink transmission opportunity corresponds to the estimated duration, the medium access control entity is configured with the available uplink control channel resource, and determines to send the scheduling request, otherwise, determines not to send the scheduling request. .
  • the sending determining module includes:
  • the second resource determining sub-module is configured to determine, as a starting point, a time of the physical downlink control channel before the triggering time of the scheduling request, and a time of each physical downlink control channel after the triggering time of the scheduling request, Whether there is an uplink shared channel resource available in the uplink transmission opportunity within the time range of the estimated duration;
  • a second resource determining submodule configured to determine, for an uplink transmission opportunity that does not have an available uplink shared channel resource, whether the medium access control entity is configured with an available uplink control channel within an estimated duration corresponding to the uplink transmission opportunity Resource
  • the second sending determining submodule is configured to: if the uplink transmission opportunity corresponds to the estimated duration, the medium access control entity is configured with the available uplink control channel resource, and determines to send the scheduling request, otherwise, determines not to send the scheduling request. .
  • the sending determining module includes:
  • the interval determining sub-module is configured to determine a preset interval corresponding to the carrier that sends the scheduling request, where the preset interval is an end time from the user equipment that receives the physical downlink control channel where the uplink resource allocation indication information is located, The processing time required by the user equipment to the nearest possible start time of the physical downlink shared channel transmission;
  • the third resource judging sub-module is configured to determine whether the duration of the triggering time of the available uplink shared channel resource to the buffer status report is greater than the preset interval, and if it is greater than, determine that there is an uplink sharing available in the uplink transmission opportunity.
  • Channel resource
  • a third resource determining submodule configured to determine, for an uplink transmission opportunity that does not have an available uplink shared channel resource, whether the medium access control entity is configured with an available uplink control channel within an estimated duration corresponding to the uplink transmission opportunity Resource
  • the third sending determining submodule is configured to: if the uplink transmission opportunity corresponds to the estimated duration, the medium access control entity is configured with the available uplink control channel resource, and determines to send the scheduling request, otherwise, determines not to send the scheduling request. .
  • the sending determining module includes:
  • the fourth resource determining sub-module is configured to determine, according to each uplink transmission opportunity after the triggering time of the scheduling request, whether there is available uplink shared channel resource;
  • a fourth resource determining submodule configured to determine, for an uplink transmission opportunity that does not have an available uplink shared channel resource, whether the medium access control entity is configured within a duration corresponding to the uplink transmission opportunity and the last uplink transmission opportunity Available uplink control channel resources;
  • a fourth sending determining submodule configured to determine to send a scheduling request if the medium access control entity is configured with available physical uplink control channel resources, and otherwise determine not to send the scheduling request.
  • the device further includes:
  • the selection module is configured to select a plurality of available uplink control channel resources, and select an available uplink control channel resource that is closest to the current time to send a scheduling request.
  • an electronic device comprising:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the buffer status report is transmitted to the base station by using the available uplink shared channel resource.
  • a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the following steps:
  • the buffer status report is transmitted to the base station by using the available uplink shared channel resource.
  • the user equipment can determine, according to the relatively fixed duration of the estimated duration, how long after the triggering time of the buffer status report or the time of the physical downlink control channel
  • the uplink shared channel resources available in the uplink transmission opportunity are counted as available uplink shared channel resources, and then the buffer status report is transmitted to the base station through the available uplink shared channel resources, thereby preventing the user equipment from being unable to determine the available uplink shared channel.
  • the resource cannot transmit a buffer status report to the base station.
  • FIG. 1 is a schematic flow chart of a buffer status report transmission method according to an embodiment of the present disclosure. Figure.
  • FIG. 2 is a schematic flow chart of another method of buffer status report transmission according to an embodiment of the present disclosure.
  • FIG. 3 is a schematic diagram showing a time interval K2 in accordance with an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram showing an estimated duration T, in accordance with an embodiment of the present disclosure.
  • FIG. 5 is a schematic flowchart of determining a maximum transmission duration of an uplink shared channel according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flow chart showing determining an estimated duration according to the time interval according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flow chart showing another determination of an estimated duration based on the time interval, according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic flow chart showing still determining an estimated duration according to the time interval according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic flow chart of still another method for transmitting a buffer status report according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic flow chart of still another method for transmitting a buffer status report according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic flow chart of still another method for transmitting a buffer status report according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic flow chart of still another method for transmitting a buffer status report according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic flow chart of determining whether to send a scheduling request, according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic flow chart showing another method of determining whether to send a scheduling request, according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic diagram of determining whether to send a scheduling request, according to an embodiment of the present disclosure.
  • 16 is a schematic flow diagram of determining whether to send a scheduling request, according to an embodiment of the present disclosure. Cheng Tu.
  • FIG. 17 is a schematic flow chart showing still determining whether to send a scheduling request, according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic block diagram of a buffer status report transmission apparatus according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic block diagram of another cache status report transmission apparatus according to an embodiment of the present disclosure.
  • FIG. 20 is a schematic block diagram of still another cache status report transmission apparatus according to an embodiment of the present disclosure.
  • FIG. 21 is a schematic block diagram of still another cache status report transmission apparatus according to an embodiment of the present disclosure.
  • FIG. 22 is a schematic block diagram of a transmission determining module according to an embodiment of the present disclosure.
  • FIG. 23 is a schematic block diagram of another transmission determination module, according to an embodiment of the present disclosure.
  • FIG. 24 is a schematic block diagram of still another transmission determination module according to an embodiment of the present disclosure.
  • FIG. 25 is a schematic block diagram of still another transmission determining module according to an embodiment of the present disclosure.
  • FIG. 26 is a schematic block diagram of an apparatus for buffering status report transmission, according to an exemplary embodiment.
  • FIG. 1 is a schematic flow chart of a method for transmitting a buffer status report according to an embodiment of the present disclosure.
  • the cache status report transmission method shown in this embodiment may be applicable to a user equipment, and the user equipment may be an electronic device such as a mobile phone, a tablet computer, or a wearable device.
  • the cache status report transmission method may include the following steps:
  • step S1 a configuration message sent by the base station is received.
  • the configuration message may be an RRC (Radio Resource Control) message, or may be other types of messages.
  • RRC Radio Resource Control
  • step S2 the time interval between the uplink resource allocation indication information sent by the base station and the uplink transmission corresponding to the uplink resource allocation indication information (that is, the uplink transmission opportunity used by the user equipment to transmit the uplink data) is determined according to the configuration message. .
  • the configuration message may include a correlation table of a shared channel transmission duration and the time interval, where the association relationship table includes a shared channel transmission duration and the time interval, and includes each shared channel transmission.
  • the start symbol of the uplink transmission opportunity corresponding to the duration (for example, OFDM symbol, OFDM is short for Orthogonal Frequency Division Multiplexing, that is, orthogonal frequency division multiplexing), and the like; and may also include LCP (Logical Channel Prioritization) of each logical channel.
  • the priority of the logical channel is limited to the parameter; the information of the cell allocated for the user equipment may also be included; the information of the subcarrier spacing allocated for the user equipment may also be included; and the type of the uplink resource allocation indication information may also be included.
  • the configuration message may include multiple contents, and may be set as needed, but at least include the time interval.
  • the configuration message includes a relationship between the shared channel transmission duration and the time interval.
  • the user equipment may transmit the association table to the medium access control layer through the radio resource control layer or the physical layer.
  • the time interval in the association relationship table may also be transmitted only to the medium access control layer, and only the time interval in the association relationship table may be transmitted to the medium access control layer, and
  • the shared channel transmission duration and/or start symbols in the association table are transmitted to the medium access control layer.
  • step S3 the estimated duration is determined based on the time interval.
  • step S4 a trigger time of the buffer status report (BSR) and a time of the most recent physical downlink control channel before the trigger time of the buffer status report are determined.
  • BSR buffer status report
  • the time of the physical downlink channel may be the start time of the physical downlink channel or the end time of the physical downlink channel, regardless of the start time of the physical downlink channel or the end time of the physical downlink channel.
  • the end time of the physical downlink channel can be employed.
  • step S5 it is determined whether there is an uplink transmission in the uplink transmission opportunity in the time range of the estimated duration from the triggering time of the buffer status report or the time from the physical downlink control channel. There are available uplink shared channel resources in the opportunity.
  • step S6 if there is an uplink shared channel resource available in the uplink transmission opportunity, the buffer status report is transmitted to the base station by using the available uplink shared channel resource.
  • the user equipment can determine, according to the relatively fixed duration of the estimated duration, how long after the triggering time of the buffer status report or the time of the physical downlink control channel,
  • the available uplink shared channel resources are counted as available uplink shared channel resources, and the buffer status report is transmitted to the base station through the available uplink shared channel resources, so that the user equipment cannot determine the available uplink shared channel resources. It is not possible to transmit a buffer status report to the base station.
  • the SR may also be triggered to further determine whether to send the SR, and the related manner is shown in the following embodiments.
  • FIG. 2 is a schematic flow chart of another method of buffer status report transmission according to an embodiment of the present disclosure. As shown in FIG. 2, based on the embodiment shown in FIG. 1, the method further includes:
  • step S7 determining, according to the configuration message, a maximum transmission duration of the uplink shared channel
  • the determining the estimated duration according to the time interval includes:
  • step S301 a relationship table of a shared channel transmission duration and the time interval is obtained from the configuration message
  • the time interval corresponding to the shared channel transmission duration in the association relationship table that is smaller than the maximum transmission duration of the uplink shared channel is determined, and the maximum time interval is the estimated duration;
  • step S303 it is determined that the time interval corresponding to the maximum transmission duration of the uplink shared channel in the association relationship table is the estimated duration.
  • the estimated duration is determined according to the manner of step S302, or the estimated duration is determined according to the manner of step S303, and the selection may be performed as needed.
  • the maximum time interval is the estimated duration.
  • the time interval may be determined only according to a time interval corresponding to a shared channel transmission duration in the association table. And if the configuration message includes the time interval, and a start symbol position of an uplink transmission opportunity corresponding to each shared channel transmission duration, and the unit of the time interval is a slot, then the corresponding time interval may be determined. Further determining the start symbol in a time slot and transmitting the start symbol to The time when the uplink resource allocation indication information is used as the time interval. Based on this, the accuracy of the determined time interval can be improved.
  • FIG. 3 is a schematic diagram showing a time interval K2 in accordance with an embodiment of the present disclosure.
  • the time interval of the uplink transmission corresponding to the uplink resource allocation indication information (UL grant) and the uplink resource allocation indication information sent by the base station is K2.
  • the UL grant may be a UL grant before the BSR triggering time, or may be a UL grant after the BSR triggering time. This embodiment is mainly described by taking the UL grant before the BSR triggering time as an example. From the time when the base station sends the UL grant, there is an available uplink shared channel resource in the uplink transmission opportunity corresponding to the K2 duration, and the user equipment transmits the uplink data.
  • the user equipment since the user equipment cannot accurately determine that there is available uplink shared channel resource in the uplink transmission opportunity after the BSR triggering time, there is an available uplink shared channel resource transmission BSR.
  • the problem may be that the user equipment determines that there is no available uplink shared channel resource in the uplink transmission opportunity within the first time period after the BSR triggering time, thereby determining that the UL grant does not configure the available uplink shared channel resource for the transmission BSR.
  • an SR (scheduling request) is transmitted to the base station.
  • the most recent UL grant before the BSR triggering time is configured to allocate the available uplink shared channel resources for the BSR, but the duration of the uplink transmission opportunity of the configured uplink shared channel resource to the BSR triggering time is greater than the first duration.
  • the user equipment will generate an erroneous determination result, thereby falsely triggering the SR.
  • FIG. 4 is a schematic diagram showing an estimated duration T, in accordance with an embodiment of the present disclosure.
  • the trigger time from the BSR is triggered.
  • the uplink transmission opportunity in the time range of the continuous estimation time length T necessarily includes the uplink transmission opportunity corresponding to the available or unavailable uplink shared channel resources configured by the UR grant.
  • the available uplink shared channel resources it is determined whether there is an uplink shared channel resource available in the uplink transmission opportunity, and it can be ensured that the uplink transmission opportunity corresponding to the available or unavailable uplink shared channel resource configured by the UR grant is considered, thereby being in the uplink transmission opportunity.
  • the available uplink shared channel resources it may be determined that the BSR is transmitted through the uplink shared channel resource, thereby avoiding false triggering of the SR.
  • FIG. 5 is a schematic flowchart of determining a maximum transmission duration of an uplink shared channel according to an embodiment of the present disclosure. As shown in FIG. 5, on the basis of the embodiment shown in FIG. 2, determining, according to the configuration message, that an uplink shared channel has a maximum transmission duration includes:
  • step S701 determining, according to the priority order restriction parameter of the logical channel in the configuration message, an uplink transmission channel maximum transmission duration
  • step S702 if the uplink shared channel maximum transmission duration does not exist in the priority order restriction parameter of the logical channel, the maximum shared channel transmission duration is obtained from the association relationship table as the uplink shared channel maximum transmission duration.
  • the uplink shared channel maximum transmission duration may be configured in the priority order restriction parameter of the logical channel, and after receiving the configuration message, the uplink shared channel is determined to be the largest from the priority restriction parameter of the logical channel in the configuration message. The length of the transmission.
  • the uplink shared channel maximum transmission duration does not exist in the priority order restriction parameter of the logical channel, the maximum shared channel transmission duration is obtained from the association relationship table as the uplink shared channel maximum transmission duration.
  • FIG. 6 is a schematic flow chart showing determining an estimated duration according to the time interval according to an embodiment of the present disclosure. As shown in FIG. 6, on the basis of the embodiment shown in FIG. 1, the determining the estimated duration according to the time interval includes:
  • step S304 a maximum time interval in the association table of the shared channel transmission duration and the time interval is determined as the estimated duration in the priority order restriction parameter of the logical channel in the configuration message.
  • the time interval may be configured in a priority order restriction parameter of the logical channel, where the time interval in the association table of the shared channel transmission duration and the time interval may be configured, for example, The maximum time interval in the association table is configured in the priority order parameter of the logical channel.
  • the time interval may be determined from the priority order limiting parameter of the logical channel in the configuration message as the estimated duration.
  • FIG. 7 is a schematic flow chart showing another determination of an estimated duration based on the time interval, according to an embodiment of the present disclosure. As shown in FIG. 7, on the basis of the embodiment shown in FIG. 1, the determining the estimated duration according to the time interval includes:
  • step S305 a relationship table between the shared channel transmission duration and the time interval is obtained from the configuration message
  • step S306 it is determined that the minimum time interval in the association relationship table is the estimated duration.
  • the minimum time interval in the association table of the shared channel transmission duration and the time interval may be the estimated duration.
  • FIG. 8 is a schematic flow chart showing still determining an estimated duration according to the time interval according to an embodiment of the present disclosure. As shown in FIG. 8, on the basis of the embodiment shown in FIG. 1, the determining the estimated duration according to the time interval includes:
  • step S307 a relationship table between the shared channel transmission duration and the time interval is obtained from the configuration message
  • step S308 each time interval in the association relationship table is calculated according to a preset algorithm, and the calculation result is used as the estimated duration.
  • each time interval in the association table may also be calculated according to a preset algorithm, for example, an average value of each time interval may be calculated as an estimated duration, for example, each time interval is calculated. Fang Gen is used as the estimated duration.
  • FIG. 9 is a schematic flow chart of still another method for transmitting a buffer status report according to an embodiment of the present disclosure. As shown in FIG. 9, the method further includes:
  • step S8 before determining the estimated duration according to the time interval, if the configuration information includes a configuration duration corresponding to a logical channel required for transmitting a buffer status report, where the configuration duration is equal to the shared channel transmission duration and a specified time interval in the association table of the time interval; the configured duration is used as an estimated duration.
  • the configuration information sent by the base station to the user equipment may include the configuration duration.
  • the configuration time length may be directly used as the estimated duration.
  • the configuration duration in the configuration information may be set as needed. For example, a certain time interval in the association table between the duration and the time interval of the shared channel may be selected as the configuration duration, which is equal to which time interval. Designation is performed on the base station side.
  • FIG. 10 is a schematic flow chart of still another method for transmitting a buffer status report according to an embodiment of the present disclosure. As shown in FIG. 10, the method further includes:
  • step S9 before determining whether there is an uplink shared channel resource available in the uplink transmission opportunity, determining a preset interval corresponding to the carrier of the transmission buffer status report, where the preset interval is an inclusion interval received from the user equipment.
  • Determining a triggering time reported from the buffer status or a time from the physical downlink control channel From the uplink transmission opportunities in the time range of the estimated duration, whether there are uplink shared channel resources available in the uplink transmission opportunity includes:
  • step S501 it is determined whether the duration of the triggering time of the available uplink shared channel resource to the buffer status report is greater than the preset interval. If it is greater than, it is determined that there is an uplink shared channel resource available in the uplink transmission opportunity.
  • the different carriers may correspond to different preset intervals.
  • the corresponding preset interval N2 may be determined, and the preset interval N2 is the physical downlink where the uplink resource allocation indication information is located.
  • the time of the control channel (which may be the physical downlink control channel start time or the physical downlink control channel end time), the available uplink channel resource that is closest to the trigger time of the buffer status report after the trigger time of the buffer status report.
  • the data that needs to be transmitted is often already configured.
  • the triggering time of the available uplink shared channel resource to the buffer status report may be further determined to be greater than the preset interval. If not, the available uplink shared channel resource cannot be used. Enough for transmitting the buffer status report, determining that there is no uplink shared channel resource available in the uplink transmission opportunity; and if greater, the available uplink shared channel resource can be used for transmitting the buffer status report, determining that there is an uplink transmission opportunity There are available uplink shared channel resources.
  • FIG. 11 is a schematic flow chart of still another method for transmitting a buffer status report according to an embodiment of the present disclosure. As shown in FIG. 11, on the basis of the embodiment shown in FIG. 1, if there is an uplink shared channel resource available in the uplink transmission opportunity, the transmission of the buffer status report to the base station by using the available uplink shared channel resource includes:
  • step S601 if there is an uplink shared channel resource available in the uplink transmission opportunity, it is determined whether the available uplink shared channel resource can carry a buffer status report, and if the buffer status report can be carried, the uplink shared channel resource is used.
  • the base station transmits a buffer status report.
  • the available uplink shared channel resource may be the same as the uplink data, but may not be used to carry the buffer status report due to configuration problems. Therefore, it can be further determined whether the available uplink shared channel resource can carry the buffer status report, and if the buffer status report can be carried, the buffer status report is transmitted to the base station through the uplink shared channel resource.
  • FIG. 12 is a schematic flow diagram of still another cache status report transmission method according to an embodiment of the present disclosure. Cheng Tu. As shown in FIG. 12, based on any of the embodiments shown in FIG. 1 to FIG. 11, the method further includes:
  • step S10 if there is no uplink shared channel resource available in the uplink transmission opportunity, it is determined that the scheduling request is triggered to determine whether to send a scheduling request, where the time at which the scheduling request is triggered is determined as the scheduling request triggering time;
  • step S11 if a scheduling request is sent, the uplink shared channel resource is requested by the transmitted scheduling request, and the buffer status report is transmitted to the base station through the requested uplink shared channel resource.
  • step S12 if the scheduling request is not sent, the uplink shared channel resource is requested by the random access request to the base station, and the buffer status report is transmitted to the base station by using the requested uplink shared channel resource.
  • the uplink shared channel resource transmits a buffer status report to the base station; and when it is determined that the scheduling request is not sent, the uplink shared channel resource may be initiated by requesting the random access request to the base station, and the uplink shared channel resource of the request channel is used.
  • the base station transmits a buffer status report. Thereby ensuring that the user equipment can smoothly transmit the buffer status report to the base station.
  • the determination condition that “if there is no uplink shared channel resource available in the uplink transmission opportunity” means that the condition A is not satisfied: “trigger from the buffer status report” At the moment or from the moment of the physical downlink control channel, there is an available uplink shared channel resource in the uplink transmission opportunity within the time range of the estimated duration.
  • condition B is not satisfied: "whether the length of the trigger time of the available uplink shared channel resource to the buffer status report is greater than the preset interval", or the condition C is not satisfied: "If there is an uplink transmission opportunity available The uplink shared channel resource, the available uplink shared channel resource may carry the buffer status report, or neither the condition B nor the condition C is satisfied.
  • a random access request may be initiated on the primary cell or the primary secondary cell.
  • FIG. 13 is a schematic flow chart of determining whether to send a scheduling request, according to an embodiment of the present disclosure. As shown in FIG. 13, on the basis of the embodiment shown in FIG. 12, the determining whether to send a scheduling request includes:
  • step 1101 it is determined whether the time period from the triggering time of the scheduling request and the time of each physical downlink control channel after the triggering time of the scheduling request is the starting point, and whether the time period of the estimated duration is continuous There are available uplink shared channel resources in the uplink transmission opportunity;
  • step 1102 for an uplink transmission opportunity that does not have an available uplink shared channel resource, determine whether the medium access control entity is configured with an available uplink control channel resource within an estimated duration corresponding to the uplink transmission opportunity;
  • step 1103 if the estimated duration of the uplink transmission opportunity is within the estimated duration of the uplink transmission opportunity, the medium access control entity is configured to use the available uplink control channel resource to determine to send a scheduling request, otherwise, it is determined not to send the scheduling request.
  • the time period from the triggering time of the scheduling request and the time of each physical downlink control channel after the triggering time of the scheduling request may be determined as the starting point, and the time period of the estimated duration is continued. Whether there is an uplink shared channel resource available in the uplink transmission opportunity. If there is an uplink shared channel resource available in the uplink transmission opportunity, the buffer status report can be transmitted through the available uplink shared channel resource, so that no scheduling request needs to be sent.
  • the scheduling information may be sent through the uplink control channel resource, so that the scheduling information is determined, and if the physical uplink control channel resource is not configured, the scheduling information cannot be sent, so it is determined that the scheduling information is not sent.
  • FIG. 14 is a schematic flow chart showing another method of determining whether to send a scheduling request, according to an embodiment of the present disclosure. As shown in FIG. 14, on the basis of the embodiment shown in FIG. 12, the determining whether to send a scheduling request includes:
  • step 1104 it is determined that the time of the physical downlink control channel before the triggering time of the scheduling request and the time of each physical downlink control channel after the triggering time of the scheduling request are used as a starting point, and the estimation is continued. Whether there is an uplink shared channel resource available in the uplink transmission opportunity within the time range of the duration;
  • step 1105 determining, for an uplink transmission opportunity that does not have an available uplink shared channel resource, whether the medium access control entity is configured with an available uplink control channel resource within an estimated duration corresponding to the uplink transmission opportunity;
  • step 1106 if the estimated duration of the uplink transmission opportunity is within the estimated duration of the uplink transmission opportunity, the medium access control entity is configured to use the available uplink control channel resource to determine to send a scheduling request, otherwise, it is determined not to send the scheduling request.
  • the latest physical downlink before the triggering time of the scheduling request may be determined first.
  • the time of the control channel and the time of each physical downlink control channel after the triggering time of the scheduling request are the starting point, and whether there is an uplink shared channel resource available in the uplink transmission opportunity within the time range of the estimated duration. If there is an uplink shared channel resource available in the uplink transmission opportunity, the buffer status report can be transmitted through the available uplink shared channel resource, so that no scheduling request needs to be sent.
  • the scheduling information may be sent through the uplink control channel resource, so that the scheduling information is determined, and if the physical uplink control channel resource is not configured, the scheduling information cannot be sent, so it is determined that the scheduling information is not sent.
  • FIG. 15 is a schematic diagram of determining whether to send a scheduling request, according to an embodiment of the present disclosure.
  • each physical downlink control channel after the triggering time of the scheduling request may be determined by the physical downlink control channel, and the time of the physical downlink control channel (for example, the starting time of the physical downlink control channel, or the physical downlink)
  • the end time of the control channel is the starting point, and within the time range of the estimated duration, whether there is an uplink shared channel resource available in the uplink transmission opportunity.
  • the first T is a time range of the estimated duration of the latest physical downlink control channel before the triggering time of the scheduling request; the second T is the first time after the triggering time of the scheduling request.
  • the time of the physical downlink control channel is the starting point, and the time range of the estimated duration is continued;
  • the third T is the time range of the duration of the second physical downlink control channel after the triggering time of the scheduling request, and the duration of the estimated duration is
  • FIG. 16 is a schematic flow chart showing still determining whether to send a scheduling request according to an embodiment of the present disclosure. As shown in FIG. 16, on the basis of the embodiment shown in FIG. 12, the determining whether to send a scheduling request includes:
  • a preset interval corresponding to the carrier that sends the scheduling request is determined, where the preset interval is from the end time of receiving the physical downlink control channel where the uplink resource allocation indication information is located, The most recent possible start time for the physical downlink shared channel transmission, and the processing time required by the user equipment;
  • step 1108 it is determined whether the duration of the triggering time of the available uplink shared channel resource to the buffer status report is greater than the preset interval. If it is greater than, it is determined that there is an uplink shared channel resource available in the uplink transmission opportunity.
  • step 1109 for an uplink transmission opportunity that does not have an available uplink shared channel resource, determine whether the medium access control entity is configured with an available uplink control channel resource within an estimated duration corresponding to the uplink transmission opportunity;
  • step 110A if the estimated duration of the uplink transmission opportunity is within the estimated duration of the uplink transmission opportunity, the medium access control entity is configured to use the available uplink control channel resource to determine to send a scheduling request, otherwise, it is determined not to send the scheduling request.
  • the time of the latest physical downlink control channel before the triggering time of the scheduling request plus the preset interval, and the time of each physical downlink control channel after the triggering time of the scheduling request may be determined.
  • the time interval of the preset interval is the starting point, and the uplink shared channel resource is available in the uplink transmission opportunity in the time range of the estimated duration. If there is an uplink shared channel resource available in the uplink transmission opportunity, the The available uplink shared channel resource transmits a buffer status report, thereby eliminating the need to send a scheduling request.
  • the scheduling information may be sent through the uplink control channel resource, so that the scheduling information is determined, and if the physical uplink control channel resource is not configured, the scheduling information cannot be sent, so it is determined that the scheduling information is not sent.
  • FIG. 17 is a schematic flow chart showing still determining whether to send a scheduling request, according to an embodiment of the present disclosure. As shown in FIG. 17, on the basis of the embodiment shown in FIG. 12, the determining whether to send a scheduling request includes:
  • step 110B it is determined one by one for each uplink transmission opportunity after the triggering time of the scheduling request, whether there is available uplink shared channel resource;
  • step 110C for an uplink transmission opportunity that does not have an available uplink shared channel resource, it is determined whether the medium access control entity is configured with an available object uplink within a duration corresponding to the uplink transmission opportunity and the last uplink transmission opportunity. Control channel resources;
  • step 110D if the medium access control entity is configured with available physical uplink control channel resources, it is determined to send a scheduling request, otherwise, it is determined not to send a scheduling request.
  • whether there is available uplink shared channel resource may be determined one by one for each uplink transmission opportunity after the triggering time of the scheduling request.
  • the buffer status report can be sent through the available uplink shared channel resources, so the scheduling is not triggered. request.
  • a scheduling request may be triggered, and in order to determine whether to send a scheduling request, it is further required to further determine the uplink transmission opportunity and the previous uplink transmission opportunity (before the scheduling request triggering moment). Whether the medium access control entity is configured with available uplink control channel resources within the duration corresponding to each other.
  • the scheduling request may be sent through the available physical uplink control channel resources to determine the sending scheduling request; and if the medium access control entity is not configured with the available physical The uplink control channel resource determines that the scheduling request is not sent, and requests the uplink shared channel resource by initiating random access.
  • determining to send a scheduling request it may further determine whether the number of times the SR is sent is greater than or equal to a preset number of times, and the number of times of transmission is less than In the case of a preset number of times, it is determined that the scheduling request is sent, otherwise, it is determined that the scheduling request is not sent.
  • the scheduling request suppression timer When it is determined that the scheduling request is sent, it may further determine whether the scheduling request suppression timer is running, and if the scheduling request suppression timer is not running, determine to send the scheduling request, otherwise, determine not to send the scheduling request.
  • the method further includes:
  • the scheduling request is sent by using the available uplink control channel resources that are closest to the current time.
  • selecting the available uplink control channel resource transmission scheduling request that is closest to the current time may reduce the time delay of sending the scheduling request.
  • the present disclosure also proposes an embodiment of a cache status report transmission apparatus.
  • FIG. 18 is a schematic block diagram of a buffer status report transmission apparatus according to an embodiment of the present disclosure.
  • the cache status report transmission method shown in this embodiment may be applicable to a user equipment, and the user equipment may be an electronic device such as a mobile phone, a tablet computer, or a wearable device.
  • the cache status report transmission apparatus may include:
  • the configuration message receiving module 1 is configured to receive a configuration message sent by the base station
  • the time interval determining module 2 is configured to determine, according to the configuration message, a time interval of uplink transmission corresponding to the uplink resource allocation indication information sent by the base station and the uplink resource allocation indication information;
  • the estimated duration determining module 3 is configured to determine an estimated duration according to the time interval
  • the time determination module 4 is configured to determine a trigger time of the buffer status report and a time of the most recent physical downlink control channel before the trigger time of the buffer status report;
  • the resource determining module 5 is configured to determine whether there is an uplink transmission in an uplink transmission opportunity within a time range of the estimated duration from a triggering time of the buffer status report or a time from the physical downlink control channel There are available uplink shared channel resources in the opportunity;
  • the report transmission module 6 is configured to transmit a buffer status report to the base station by using the available uplink shared channel resource if there is an uplink shared channel resource available in the uplink transmission opportunity.
  • FIG. 19 is a schematic block diagram of another cache status report transmission apparatus according to an embodiment of the present disclosure. As shown in FIG. 19, on the basis of the embodiment shown in FIG. 18, the device further includes:
  • the duration determining module 7 is configured to determine, according to the configuration message, an uplink shared channel maximum transmission duration
  • the estimated duration determining module 3 includes:
  • the obtaining sub-module 301 is configured to obtain, from the configuration message, a relationship table between a shared channel transmission duration and the time interval;
  • the determining sub-module 302 is configured to determine, in the time interval corresponding to the shared channel transmission duration that is less than the maximum transmission duration of the uplink shared channel, the maximum time interval is the estimated duration; or determine the The time interval corresponding to the maximum transmission duration of the uplink shared channel in the association relationship table is the estimated duration.
  • the duration determining module is configured to determine, according to a priority order limiting parameter of the logical channel in the configuration message, an uplink shared channel maximum transmission duration; if the logical channel has no uplink sharing in the priority order limiting parameter The maximum transmission duration of the channel is obtained, and the maximum shared channel transmission duration is obtained from the association table as the maximum transmission duration of the uplink shared channel.
  • the estimated duration determining module is configured to determine, in a priority order limiting parameter of the logical channel in the configuration message, a maximum time interval in a relationship table between a shared channel transmission duration and the time interval as The estimated duration.
  • the estimated duration determining module is configured to obtain a shared channel transmission from the configuration message.
  • the estimated duration determining module is configured to obtain, from the configuration message, an association relationship between a shared channel transmission duration and the time interval; and each time in the association table according to a preset algorithm. The interval is calculated, and the calculation result is taken as the estimated duration.
  • the estimated duration determining module is further configured to: before the determining the estimated duration according to the time interval, if the configuration information includes a configuration duration corresponding to a logical channel required for transmitting a buffer status report, where The configured duration is equal to a specified time interval in the association table between the shared channel transmission duration and the time interval; and the configured duration is used as the estimated duration.
  • FIG. 20 is a schematic block diagram of still another cache status report transmission apparatus according to an embodiment of the present disclosure. As shown in FIG. 20, based on the embodiment shown in FIG. 18, the method further includes:
  • the preset interval determining module 8 is configured to determine a preset interval corresponding to the carrier of the transmission buffer status report (the information may be included in the configuration message) before determining whether there is an uplink shared channel resource available in the uplink transmission opportunity,
  • the preset interval is a start time from when the user equipment receives the end time of the physical downlink control channel where the uplink resource allocation indication information is located, to the latest possible physical downlink shared channel transmission, the user The processing time required by the device;
  • the resource determining module is configured to determine whether the duration of the trigger time of the available uplink shared channel resource to the buffer status report is greater than the preset interval. If the value is greater than, determine that there is an uplink share available in the uplink transmission opportunity. Channel resources.
  • the report transmission module is configured to determine whether the available uplink shared channel resource can carry a buffer status report if there is an uplink shared channel resource available in the uplink transmission opportunity, and if the buffer status report can be carried, The uplink shared channel resource transmits a buffer status report to the base station.
  • FIG. 21 is a schematic block diagram of still another cache status report transmission apparatus according to an embodiment of the present disclosure. As shown in FIG. 21, on the basis of the embodiment shown in FIG. 18, the device further includes:
  • the sending determining module 9 is configured to: if there is no uplink shared channel resource available in the uplink transmission opportunity, determine to trigger the scheduling request, and determine whether to send the scheduling request, where the time at which the scheduling request is triggered is determined as the scheduling request triggering time;
  • the resource requesting module 10 is configured to: if the sending determining module determines to send a scheduling request, request the uplink shared channel resource by using the sent scheduling request, where the report transmission module is configured to pass the requested uplink
  • the shared channel resource transmits a buffer status report to the base station.
  • the random access module 11 is configured to: if the sending determining module determines not to send a scheduling request, by initiating a random access request uplink shared channel resource to the base station, where the report transmission module is configured to pass the requested uplink shared channel The resource transmits a buffer status report to the base station.
  • FIG. 22 is a schematic block diagram of a transmission determining module according to an embodiment of the present disclosure. As shown in FIG. 22, on the basis of the embodiment shown in FIG. 21, the sending determining module 9 includes:
  • the first resource judging sub-module 901 is configured to determine, starting from a triggering time of the scheduling request, a starting time of each physical downlink control channel after a triggering time of the scheduling request, and continuing the estimated duration Whether there is an uplink shared channel resource available in the uplink transmission opportunity within the time range;
  • the first resource determining sub-module 902 is configured to determine, for an uplink transmission opportunity that does not have an available uplink shared channel resource, whether the medium access control entity is configured with available object uplink control within an estimated duration corresponding to the uplink transmission opportunity.
  • Channel resource
  • the first sending determining sub-module 903 is configured to: if the uplink transmission opportunity corresponds to the estimated duration, the medium access control entity is configured with the available uplink control channel resource, and determines to send a scheduling request, otherwise, determines not to send the scheduling. request.
  • the sending determining module 9 includes:
  • the second resource determining sub-module 904 is configured to determine, at a time when the physical control channel of the physical downlink control channel before the triggering time of the scheduling request, and a time of each physical downlink control channel after the triggering time of the scheduling request Whether there is an uplink shared channel resource available in the uplink transmission opportunity within the time range of the estimated duration;
  • the second resource determining sub-module 905 is configured to determine, for an uplink transmission opportunity that does not have an available uplink shared channel resource, whether the medium access control entity is configured with available object uplink control within an estimated duration corresponding to the uplink transmission opportunity.
  • Channel resource
  • the second sending determining sub-module 906 is configured to: if the uplink transmission opportunity corresponds to the estimated duration, the medium access control entity is configured with the available uplink control channel resource, and determines to send a scheduling request, otherwise, determines not to send the scheduling. request.
  • FIG. 24 is a schematic block diagram of still another transmission determination module according to an embodiment of the present disclosure. As shown 24, on the basis of the embodiment shown in FIG. 21, the sending determining module 9 includes:
  • the interval determining sub-module 907 is configured to determine a preset interval corresponding to the carrier that sends the scheduling request, where the preset interval is an end of receiving, by the user equipment, the physical downlink control channel where the uplink resource allocation indication information is located From the moment, to the latest possible start time of the physical downlink shared channel transmission, the processing time required by the user equipment;
  • the third resource judging sub-module 908 is configured to determine whether the duration of the triggering time of the available uplink shared channel resource to the buffer status report is greater than the preset interval. If it is greater than, it is determined that there is an available uplink transmission opportunity.
  • the third resource determining sub-module 909 is configured to determine, for an uplink transmission opportunity that does not have an available uplink shared channel resource, whether the medium access control entity is configured with available object uplink control within an estimated duration corresponding to the uplink transmission opportunity.
  • Channel resource
  • the third sending determining sub-module 910 is configured to: if the uplink transmission opportunity corresponds to the estimated duration, the medium access control entity is configured with the available uplink control channel resource, and determines to send a scheduling request, otherwise, determines not to send the scheduling. request.
  • FIG. 25 is a schematic block diagram of still another transmission determining module according to an embodiment of the present disclosure. As shown in FIG. 25, on the basis of the embodiment shown in FIG. 21, the sending determining module 9 includes:
  • the fourth resource judging sub-module 911 is configured to determine, according to each uplink transmission opportunity after the triggering time of the scheduling request, whether there is an available uplink shared channel resource;
  • the fourth resource determining sub-module 912 is configured to determine, for an uplink transmission opportunity that does not have an available uplink shared channel resource, whether the medium access control entity is within a duration corresponding to the uplink transmission opportunity and the last uplink transmission opportunity.
  • the fourth sending determining sub-module 913 is configured to determine to send a scheduling request if the medium access control entity is configured with available physical uplink control channel resources, and otherwise determine not to send a scheduling request.
  • the device further includes:
  • the selection module is configured to select a plurality of available uplink control channel resources, and select an available uplink control channel resource that is closest to the current time to send a scheduling request.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.
  • the present disclosure also proposes an electronic device, including:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the buffer status report is transmitted to the base station by using the available uplink shared channel resource.
  • the present disclosure also proposes a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the following steps:
  • the buffer status report is transmitted to the base station by using the available uplink shared channel resource.
  • FIG. 26 is a schematic block diagram of an apparatus 2600 for buffer status report transmission, according to an exemplary embodiment.
  • device 2600 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.
  • apparatus 2600 can include one or more of the following components: processing component 2602, memory 2604, power component 2606, multimedia component 2608, audio component 2610, input/output (I/O) interface 2612, sensor component 2614, And a communication component 2616.
  • Processing component 2602 typically controls the overall operation of device 2600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 2602 can include one or more processors 2620 to execute instructions to perform all or part of the steps of the above described methods.
  • processing component 2602 can include one or more modules to facilitate interaction between component 2602 and other components.
  • the processing component 2602 can include a multimedia module to facilitate interaction between the multimedia component 2608 and the processing component 2602.
  • Memory 2604 is configured to store various types of data to support operation at device 2600. Examples of such data include instructions for any application or method operating on device 2600, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 2604 can 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.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • Power component 2606 provides power to various components of device 2600.
  • Power component 2606 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 2600.
  • the multimedia component 2608 includes a screen between the device 2600 and the user that provides an output interface.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If screen The screen includes a touch panel, and the screen can 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, slides, and gestures on the touch panel. The touch sensor may sense not only the boundary of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 2608 includes a front camera and/or a rear camera. When the device 2600 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 2610 is configured to output and/or input an audio signal.
  • audio component 2610 includes a microphone (MIC) that is configured to receive an external audio signal when device 2600 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal may be further stored in memory 2604 or transmitted via communication component 2616.
  • audio component 2610 also includes a speaker for outputting an audio signal.
  • the I/O interface 2612 provides an interface between the processing component 2602 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 2614 includes one or more sensors for providing device 2600 with a status assessment of various aspects.
  • sensor assembly 2614 can detect an open/closed state of device 2600, a relative positioning of components, such as the display and keypad of device 2600, and sensor component 2614 can also detect a change in position of a component of device 2600 or device 2600. The presence or absence of user contact with device 2600, device 2600 orientation or acceleration/deceleration, and temperature change of device 2600.
  • Sensor assembly 2614 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 2614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 2614 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 2616 is configured to facilitate wired or wireless communication between device 2600 and other devices.
  • the device 2600 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • communication component 2616 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • the communication component 2616 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • device 2600 may 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 A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the method described in any of the above embodiments.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor or other electronic component implementation for performing the method described in any of the above embodiments.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 2604 comprising instructions executable by processor 2620 of apparatus 2600 to perform the above method.
  • the non-transitory computer readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开涉及缓存状态报告传输方法，包括：接收基站发送的配置消息；根据配置消息确定基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；根据时间间隔确定预估时长；确定从缓存状态报告的触发时刻或从物理下行控制信道的时刻起，持续预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；若存在上行传输机会中有可用的上行共享信道资源，通过可用的上行共享信道资源向基站传输缓存状态报告。根据本公开的实施例，可以避免用户设备因为无法确定可用的上行共享信道资源而无法向基站传输缓存状态报告。

Description

缓存状态报告传输和装置 技术领域
本申请涉及通信技术领域，具体而言，涉及缓存状态报告传输方法、缓存状态报告传输装置、电子设备和计算机可读存储介质。
背景技术
无论在LTE(Long Term Evolution，长期演进)中，还是在NR(New Radio，新空口)中，用户设备在接收到基站发送的UR grant(上行资源分配指示信息)后，触发BSR(缓存状态报告)，并判断是否可以向基站传输BSR。
一般需要通过上行共享信道(Up Link Shared Channel，简称ULSCH)资源来携带BSR，若没有可用的上行共享信道资源时，需要向基站发送SR(Scheduling Request，调度请求)来请求上行共享信道资源。
目前对于判断是否存在可用的上行共享信道资源，主要有以下其中方式：
其一，判断是否有立即的可用的上行共享信道资源。基于这种方式，用户设备对于“立即的”判断可以存在不同的理解，从而无法准确地确定在BSR触发时刻之后多长时间内的上行共享信道资源算作可用的上行共享信道资源。
其二，判断在下一个TTI(Tranmission Time Interval，传输时间间隔)是否有可用的上行共享信道资源。基于这种方式，由于TTI并非一个常量，例如可以是1个、2个、4个或8个符号，用户设备无法确定TTI具体对应多少个符号。
发明内容
有鉴于此，本发明提出了缓存状态报告传输方法、缓存状态报告传输装置、电子设备和计算机可读存储介质，以解决相关技术中的技术问题。
根据本公开的第一方面，提出了一种缓存状态报告传输方法，适用于用户设备，所述方法包括：
接收基站发送的配置消息；
根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
根据所述时间间隔确定预估时长；
确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
可选地，所述方法还包括：
根据所述配置消息确定上行共享信道最大传输时长；
所述根据所述时间间隔确定预估时长包括：
从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
确定所述关联关系表中小于所述上行共享信道最大传输时长的共享信道传输时长对应的时间间隔中，最大的时间间隔为所述预估时长；或
确定所述关联关系表中所述上行共享信道最大传输时长对应的时间间隔为所述预估时长。
可选地，所述根据所述配置消息确定上行共享信道最大传输时长包括：
根据所述配置消息中的逻辑信道的优先次序限制参数确定上行共享信道最大传输时长；
若所述逻辑信道的优先次序限制参数中不存在上行共享信道最大传输时长，从所述关联关系表中获取最大的共享信道传输时长，作为所述上行共享信道最大传输时长。
可选地，所述根据所述时间间隔确定预估时长包括：
在所述配置消息中的逻辑信道的优先次序限制参数中确定共享信道传输时长 与所述时间间隔的关联关系表中的最大的时间间隔作为所述预估时长。
可选地，所述根据所述时间间隔确定预估时长包括：
从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
确定所述关联关系表中最小的时间间隔为所述预估时长。
可选地，所述根据所述时间间隔确定预估时长包括：
从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
根据预设算法对所述关联关系表中的每个时间间隔进行计算，将计算结果作为所述预估时长。
可选地，所述方法还包括：
在根据所述时间间隔确定预估时长之前，若所述配置信息包含传输缓存状态报告所需用的逻辑信道对应的配置时长，其中，所述配置时长等于共享信道传输时长与所述时间间隔的关联关系表中的指定时间间隔；
将所述配置时长作为预估时长。
可选地，所述方法还包括：
在确定是否存在上行传输机会中有可用的上行共享信道资源之前，确定传输缓存状态报告的载波对应的预设间隔，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
所述确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源包括：
确定可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源。
可选地，若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告包括：
若存在上行传输机会中有可用的上行共享信道资源，确定所述可用的上行共享信道资源是否可以携带缓存状态报告，若可以携带缓存状态报告，通过所述上行共享 信道资源向所述基站传输缓存状态报告。
可选地，所述方法还包括：
若不存在上行传输机会中有可用的上行共享信道资源，确定触发调度请求，确定是否发送调度请求，其中，确定触发调度请求的时刻为调度请求触发时刻；
若发送调度请求，通过发送的调度请求来请求上行共享信道资源，通过请求的上行共享信道资源向所述基站传输缓存状态报告。
若不发送调度请求，通过向所述基站发起随机接入请求上行共享信道资源，通过请求的上行共享信道资源向所述基站传输缓存状态报告。
可选地，所述确定是否发送调度请求包括：
判断从所述调度请求的触发时刻起，以及以所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
可选地，所述确定是否发送调度请求包括：
判断以所述调度请的求触发时刻之前最近的物理下行控制信道的时刻，以及所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
可选地，所述确定是否发送调度请求包括：
确定发送调度请求的载波对应的预设间隔，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最 近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
判断可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源；
对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
可选地，所述确定是否发送调度请求包括：
针对所述调度请求的触发时刻之后的每一个上行传输机会，逐个判断是否有可用的上行共享信道资源；
对于没有可用的上行共享信道资源的上行传输机会，确定在该上行传输机会与上一个上行传输机会之间所对应的时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
若介质访问控制实体被配置了可用的物理上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
可选地，所述方法还包括：
若存在多个可用的上行控制信道资源，选择距离当前时刻最近的可用的上行控制信道资源发送调度请求。
根据本公开的第二方面，提出了一种缓存状态报告传输装置，适用于用户设备，所述装置包括：
配置消息接收模块，被配置为接收基站发送的配置消息；
时间间隔确定模块，被配置为根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
预估时长确定模块，被配置为根据所述时间间隔确定预估时长；
时刻确定模块，被配置为确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
资源确定模块，被配置为确定从所述缓存状态报告的触发时刻或从所述物理下 行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
报告传输模块，被配置为若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
可选地，所述装置还包括：
时长确定模块，被配置为根据所述配置消息确定上行共享信道最大传输时长；
其中，所述预估时长确定模块包括：
获取子模块，被配置为从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
确定子模块，被配置为确定所述关联关系表中小于所述上行共享信道最大传输时长的共享信道传输时长对应的时间间隔中，最大的时间间隔为所述预估时长；或
确定所述关联关系表中所述上行共享信道最大传输时长对应的时间间隔为所述预估时长。
可选地，所述时长确定模块，被配置为根据所述配置消息中的逻辑信道的优先次序限制参数确定上行共享信道最大传输时长；若所述逻辑信道的优先次序限制参数中不存在上行共享信道最大传输时长，从所述关联关系表中获取最大的共享信道传输时长，作为所述上行共享信道最大传输时长。
可选地，所述预估时长确定模块被配置为在所述配置消息中的逻辑信道的优先次序限制参数中确定共享信道传输时长与所述时间间隔的关联关系表中的最大的时间间隔作为所述预估时长。
可选地，所述预估时长确定模块被配置为从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；确定所述关联关系表中最小的时间间隔为所述预估时长。
可选地，所述预估时长确定模块被配置为从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；根据预设算法对所述关联关系表中的每个时间间隔进行计算，将计算结果作为所述预估时长。
可选地，所述预估时长确定模块还被配置为在根据所述时间间隔确定预估时长之前，若所述配置信息包含传输缓存状态报告所需用的逻辑信道对应的配置时长，其 中，所述配置时长等于共享信道传输时长与所述时间间隔的关联关系表中的指定时间间隔；将所述配置时长作为预估时长。
可选地，所述装置还包括：
预设间隔确定模块，被配置为在确定是否存在上行传输机会中有可用的上行共享信道资源之前，确定传输缓存状态报告的载波对应的预设间隔，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
其中，所述资源确定模块被配置为确定可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源。
可选地，所述报告传输模块被配置为若存在上行传输机会中有可用的上行共享信道资源，确定所述可用的上行共享信道资源是否可以携带缓存状态报告，若可以携带缓存状态报告，通过所述上行共享信道资源向所述基站传输缓存状态报告。
可选地，所述装置还包括：
发送确定模块，被配置为若不存在上行传输机会中有可用的上行共享信道资源，确定触发调度请求，确定是否发送调度请求，其中，确定触发调度请求的时刻为调度请求触发时刻；
资源请求模块，被配置为若发送确定模块确定发送调度请求，通过发送的调度请求来请求上行共享信道资源，其中，所述报告传输模块被配置为通过请求的上行共享信道资源向所述基站传输缓存状态报告。
随机接入模块，被配置为若发送确定模块确定不发送调度请求，通过向所述基站发起随机接入请求上行共享信道资源，其中，所述报告传输模块被配置为通过请求的上行共享信道资源向所述基站传输缓存状态报告。
可选地，所述发送确定模块包括：
第一资源判断子模块，被配置为判断从所述调度请求的触发时刻起，以及以所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
第一资源确定子模块，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
第一发送确定子模块，被配置为若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
可选地，所述发送确定模块包括：
第二资源判断子模块，被配置为判断以所述调度请的求触发时刻之前最近的物理下行控制信道的时刻，以及所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
第二资源确定子模块，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
第二发送确定子模块，被配置为若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
可选地，所述发送确定模块包括：
间隔确定子模块，被配置为确定发送调度请求的载波对应的预设间隔，其中，预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
第三资源判断子模块，被配置为判断可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源；
第三资源确定子模块，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
第三发送确定子模块，被配置为若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
可选地，所述发送确定模块包括：
第四资源判断子模块，被配置为针对所述调度请求的触发时刻之后的每一个上行传输机会，逐个判断是否有可用的上行共享信道资源；
第四资源确定子模块，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定在该上行传输机会与上一个上行传输机会之间所对应的时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
第四发送确定子模块，被配置为若介质访问控制实体被配置了可用的物理上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
可选地，所述装置还包括：
选择模块，被配置若存在多个可用的上行控制信道资源，选择距离当前时刻最近的可用的上行控制信道资源发送调度请求。
根据本公开的第三方面，提出了一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收基站发送的配置消息；
根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
根据所述时间间隔确定预估时长；
确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
根据本公开的第四方面，提出了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现以下步骤：
接收基站发送的配置消息；
根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
根据所述时间间隔确定预估时长；
确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
根据本公开的实施例，通过确定预估时长，使得用户设备可以根据预估时长这一相对固定的时长来确定，在缓存状态报告的触发时刻或物理下行控制信道的时刻之后，多长时间内的上行传输机会中有可用的上行共享信道资源，才算作有可用的上行共享信道资源，进而通过可用的上行共享信道资源向基站传输缓存状态报告，避免用户设备因为无法确定可用的上行共享信道资源而无法向基站传输缓存状态报告。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是根据本公开一个实施例示出的一种缓存状态报告传输方法的示意流程 图。
图2是根据本公开一个实施例示出的另一种缓存状态报告传输方法的示意流程图。
图3是根据本公开一个实施例示出的时间间隔K2的示意图。
图4是根据本公开一个实施例示出的预估时长T的示意图。
图5是根据本公开一个实施例示出的一种确定上行共享信道最大传输时长的示意流程图。
图6是根据本公开一个实施例示出的一种根据所述时间间隔确定预估时长的示意流程图。
图7是根据本公开一个实施例示出的另一种根据所述时间间隔确定预估时长的示意流程图。
图8是根据本公开一个实施例示出的又一种根据所述时间间隔确定预估时长的示意流程图。
图9是根据本公开一个实施例示出的又一种缓存状态报告传输方法的示意流程图。
图10是根据本公开一个实施例示出的又一种缓存状态报告传输方法的示意流程图。
图11是根据本公开一个实施例示出的又一种缓存状态报告传输方法的示意流程图。
图12是根据本公开一个实施例示出的又一种缓存状态报告传输方法的示意流程图。
图13是根据本公开一个实施例示出的一种确定是否发送调度请求的示意流程图。
图14是根据本公开一个实施例示出的另一种确定是否发送调度请求的示意流程图。
图15是根据本公开一个实施例示出的一种确定是否发送调度请求的示意图。
图16是根据本公开一个实施例示出的又一种确定是否发送调度请求的示意流 程图。
图17是根据本公开一个实施例示出的又一种确定是否发送调度请求的示意流程图。
图18是根据本公开一个实施例示出的一种缓存状态报告传输装置的示意框图。
图19是根据本公开一个实施例示出的另一种缓存状态报告传输装置的示意框图。
图20是根据本公开一个实施例示出的又一种缓存状态报告传输装置的示意框图。
图21是根据本公开一个实施例示出的又一种缓存状态报告传输装置的示意框图。
图22是根据本公开一个实施例示出的一种发送确定模块的示意框图。
图23是根据本公开一个实施例示出的另一种发送确定模块的示意框图。
图24是根据本公开一个实施例示出的又一种发送确定模块的示意框图。
图25是根据本公开一个实施例示出的又一种发送确定模块的示意框图。
图26是根据一示例性实施例示出的一种用于缓存状态报告传输的装置的示意框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图1是根据本公开一个实施例示出的一种缓存状态报告传输方法的示意流程图。本实施例所示的缓存状态报告传输方法可以适用于用户设备，所述用户设备可以是手机、平板电脑、可穿戴设备等电子设备。
如图1所示，所述缓存状态报告传输方法可以包括以下步骤：
在步骤S1中，接收基站发送的配置消息。
在一个实施例中，配置消息可以是RRC(Radio Resource Control，无线资源控制层)消息，也可以是其他类型的消息。
在步骤S2中，根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输(也即用户设备传输上行数据所使用的上行传输机会)的时间间隔。
在一个实施例中，配置消息可以包含共享信道传输时长与所述时间间隔的关联关系表，其中，所述关联关系表除了包含共享信道传输时长和所述时间间隔，还包含每个共享信道传输时长对应的上行传输机会的起始符号(例如OFDM符号，OFDM为Orthogonal Frequency Division Multiplexing的简称，也即正交频分复用)位置等内容；还可以包含每个逻辑信道的LCP(Logical Channel Prioritization，逻辑信道的优先次序)限制参数；还可以包含为用户设备分配的小区的信息；还可以包含为用户设备分配的子载波间隔的信息；还可以包含所述上行资源分配指示信息的类型。
综上所述，配置消息可以包含多种内容，具体可以根据需要进行设置，但是至少包含所述时间间隔。
其中，例如配置消息包含共享信道传输时长与所述时间间隔的关联关系表，用户设备在接收到配置消息后，可以通过无线资源控制层或物理层将所述关联关系表传输至介质访问控制层，也可以仅将所述关联关系表中的所述时间间隔传输至介质访问控制层，在仅将所述关联关系表中的所述时间间隔传输至介质访问控制层的基础上，还可以将关联关系表中的共享信道传输时长和/或起始符号传输至介质访问控制层。
在步骤S3中，根据所述时间间隔确定预估时长。
在步骤S4中，确定缓存状态报告(BSR)的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻。
在一个实施例中，物理下行信道的时刻，可以是物理下行信道的起始时刻，也可以是物理下行信道的结束时刻，无论物理下行信道的起始时刻，还是物理下行信道的结束时刻，都在缓存状态报告的触发时刻之前。优选地，可以采用物理下行信道的结束时刻。
在步骤S5中，确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输 机会中有可用的上行共享信道资源。
在步骤S6中，若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
在一个实施例中，通过确定预估时长，使得用户设备可以根据预估时长这一相对固定的时长来确定，在缓存状态报告的触发时刻或物理下行控制信道的时刻之后，多长时间内的上行传输机会中有可用的上行共享信道资源，才算作有可用的上行共享信道资源，进而通过可用的上行共享信道资源向基站传输缓存状态报告，避免用户设备因为无法确定可用的上行共享信道资源而无法向基站传输缓存状态报告。
在一个实施例中，若在上行传输机会中没有可用的上行共享信道资源，还可以触发SR，进一步确定是否发送SR，相关方式在后续实施例中示出。
图2是根据本公开一个实施例示出的另一种缓存状态报告传输方法的示意流程图。如图2所示，在图1所示实施例的基础上，所述方法还包括：
在步骤S7中，根据所述配置消息确定上行共享信道最大传输时长；
所述根据所述时间间隔确定预估时长包括：
在步骤S301中，从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
在步骤S302中，确定所述关联关系表中小于所述上行共享信道最大传输时长的共享信道传输时长对应的时间间隔中，最大的时间间隔为所述预估时长；或
在步骤S303中，确定所述关联关系表中所述上行共享信道最大传输时长对应的时间间隔为所述预估时长。
在一个实施例中，根据步骤S302的方式确定预估时长，还是根据步骤S303的方式确定预估时长，可以根据需要进行选择。例如以根据步骤S302的方式确定预估时长为例，也即确定关联关系表中小于上行共享信道最大传输时长的共享信道传输时长对应的时间间隔中，最大的时间间隔为预估时长。
在一个实施例中，所述时间间隔可以仅根据所述关联关系表中共享信道传输时长对应的时间间隔来确定。而若配置消息包含所述时间间隔，以及每个共享信道传输时长对应的上行传输机会的起始符号位置，且所述时间间隔的单位为时隙(slot)，那么可以在确定时间间隔对应的时隙中进一步确定所述起始符号，并将所述起始符号到 上行资源分配指示信息的时间作为所述时间间隔。基于此，可以提高确定的时间间隔的精度。
图3是根据本公开一个实施例示出的时间间隔K2的示意图。
在一个实施例中，如图3所示，基站发送的上行资源分配指示信息(UL grant)与该上行资源分配指示信息对应的上行传输的时间间隔为K2。其中，所述UL grant可以是指在BSR触发时刻之前的UL grant，也可以是指在BSR触发时刻之后的UL grant，本实施例主要以BSR触发时刻之前的UL grant为例进行示例性说明。从基站发送UL grant的时刻起，持续K2时长时对应的上行传输机会中，存在可用的上行共享信道资源，供用户设备传输上行数据。
在相关技术中，由于用户设备不能准确地确定在BSR触发时刻之后的多长时间内的上行传输机会中存在可用的上行共享信道资源，才算是存在可用的上行共享信道资源传输BSR。这可能引发的问题是，用户设备确定在BSR触发时刻之后的第一时长内的上行传输机会中不存在可用的上行共享信道资源，从而确定UL grant没有为传输BSR配置可用的上行共享信道资源，进而向基站发送SR(调度请求)。而实际上BSR触发时刻之前最近的UL grant，为传输BSR配置了可用的上行共享信道资源，只不过配置的可用的上行共享信道资源所在的上行传输机会到BSR触发时刻的时长大于第一时长。在这种情况下，用户设备就会产生错误的判定结果，从而误触发SR。
图4是根据本公开一个实施例示出的预估时长T的示意图。
在一个实施例中，如图4所示，由于预估时长T为关联关系表中小于上行共享信道最大传输时长的共享信道传输时长对应的时间间隔中最大的时间间隔K2，因此从BSR触发时刻起，持续预估时长T的时间范围内的上行传输机会中，必然包含UR grant所配置的可用或不可用的上行共享信道资源对应的上行传输机会。
在此基础上判断是否存在上行传输机会中有可用的上行共享信道资源，可以确保考虑含UR grant所配置的可用或不可用的上行共享信道资源对应的上行传输机会，从而在该上行传输机会中包含可用的上行共享信道资源时，可以确定通过该上行共享信道资源传输BSR，进而避免误触发SR。
图5是根据本公开一个实施例示出的一种确定上行共享信道最大传输时长的示意流程图。如图5所示，在图2所示实施例的基础上，所述根据所述配置消息确定上行共享信道最大传输时长包括：
在步骤S701中，根据所述配置消息中的逻辑信道的优先次序限制参数确定上行共享信道最大传输时长；
在步骤S702中，若所述逻辑信道的优先次序限制参数中不存在上行共享信道最大传输时长，从所述关联关系表中获取最大的共享信道传输时长，作为所述上行共享信道最大传输时长。
在一个实施例中，可以在逻辑信道的优先次序限制参数中配置上行共享信道最大传输时长，并在接收到配置消息后，优先从配置消息中的逻辑信道的优先次序限制参数确定上行共享信道最大传输时长。当逻辑信道的优先次序限制参数中不存在上行共享信道最大传输时长时，再从关联关系表中获取最大的共享信道传输时长作为所述上行共享信道最大传输时长。
图6是根据本公开一个实施例示出的一种根据所述时间间隔确定预估时长的示意流程图。如图6所述，在图1所示实施例的基础上，所述根据所述时间间隔确定预估时长包括：
在步骤S304中，在所述配置消息中的逻辑信道的优先次序限制参数中确定共享信道传输时长与所述时间间隔的关联关系表中的最大的时间间隔作为所述预估时长。
在一个实施例中，可以在逻辑信道的优先次序限制参数中配置所述时间间隔，其中，可以参考共享信道传输时长与所述时间间隔的关联关系表中的时间间隔来配置，例如可以将所述关联关系表中的最大的时间间隔配置在逻辑信道的优先次序限制参数中。进而在接收到配置消息后，可以从配置消息中的逻辑信道的优先次序限制参数中确定时间间隔作为预估时长。
图7是根据本公开一个实施例示出的另一种根据所述时间间隔确定预估时长的示意流程图。如图7所述，在图1所示实施例的基础上，所述根据所述时间间隔确定预估时长包括：
在步骤S305中，从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
在步骤S306中，确定所述关联关系表中最小的时间间隔为所述预估时长。
在一个实施例中，除了按照图2所示的实施例确定预估时长，也可以将共享信道传输时长与时间间隔的关联关系表中最小的时间间隔为预估时长。
图8是根据本公开一个实施例示出的又一种根据所述时间间隔确定预估时长的示意流程图。如图8所述，在图1所示实施例的基础上，所述根据所述时间间隔确定预估时长包括：
在步骤S307中，从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
在步骤S308中，根据预设算法对所述关联关系表中的每个时间间隔进行计算，将计算结果作为所述预估时长。
在一个实施例中，也可以根据需要按照预设算法对关联关系表中的每个时间间隔进行计算，例如可以计算每个时间间隔的平均值作为预估时长，例如计算每个时间间隔的均方根作为预估时长。
图9是根据本公开一个实施例示出的又一种缓存状态报告传输方法的示意流程图。如图9所示，所述方法还包括：
在步骤S8中，在根据所述时间间隔确定预估时长之前，若所述配置信息包含传输缓存状态报告所需用的逻辑信道对应的配置时长，其中，所述配置时长等于共享信道传输时长与所述时间间隔的关联关系表中的指定时间间隔；将所述配置时长作为预估时长。
在一个实施例中，基站发送给用户设备的配置信息中可以直接包含配置时长，用户设备当确定配置信息中存在配置时长时，可以直接将配置时长作为预估时长，而无需根据所述时间间隔来确定预估时长。需要说明的是，配置信息中的配置时长可以根据需要进行设置，例如可以选择共享信道传输时长与时间间隔的关联关系表中的某个时间间隔作为所述配置时长，具体等于哪个时间间隔，可以在基站侧进行指定。
图10是根据本公开一个实施例示出的又一种缓存状态报告传输方法的示意流程图。如图10所示，所述方法还包括：
在步骤S9中，在确定是否存在上行传输机会中有可用的上行共享信道资源之前，确定传输缓存状态报告的载波对应的预设间隔，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
所述确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻 起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源包括：
在步骤S501中，确定可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源。
在一个实施例中，不同的载波可以对应不同的预设间隔，对于传输缓存状态报告的载波，可以确定其对应的预设间隔N2，由于预设间隔N2为上行资源分配指示信息所在的物理下行控制信道的时刻(可以是物理下行控制信道起始时刻，也可以是物理下行控制信道结束时刻)，到在缓存状态报告的触发时刻之后，且距离缓存状态报告的触发时刻最近的可用上行信道资源的时间，在预设间隔N2内的上行传输机会中，往往已经被配置了需要传输的数据。
因此，在确定了可用的上行共享信道资源时，可以进一步判断可用的上行共享信道资源到缓存状态报告的触发时刻是否大于所述预设间隔，若不大于，那么可用的上行共享信道资源并不能够用于传输缓存状态报告，则确定不存在上行传输机会中有可用的上行共享信道资源；而若大于，那么可用的上行共享信道资源并能够用于传输缓存状态报告，则确定存在上行传输机会中有可用的上行共享信道资源。
图11是根据本公开一个实施例示出的又一种缓存状态报告传输方法的示意流程图。如图11所示，在图1所示实施例的基础上，若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告包括：
在步骤S601中，若存在上行传输机会中有可用的上行共享信道资源，确定所述可用的上行共享信道资源是否可以携带缓存状态报告，若可以携带缓存状态报告，通过所述上行共享信道资源向所述基站传输缓存状态报告。
在一个实施例中，当确定存在上行传输机会中有可用的上行共享信道资源，由于可用的上行共享信道资源虽然可以同于传输上行数据，但是由于配置问题，可能并不能用于携带缓存状态报告，因此，可以进一步确定可用的上行共享信道资源是否可以携带缓存状态报告，并在可以携带缓存状态报告的情况下，才通过上行共享信道资源向所述基站传输缓存状态报告。
图12是根据本公开一个实施例示出的又一种缓存状态报告传输方法的示意流 程图。如图12所示，在图1至图11所示的任一实施例的基础上，所述方法还包括：
在步骤S10中，若不存在上行传输机会中有可用的上行共享信道资源，确定触发调度请求，确定是否发送调度请求，其中，确定触发调度请求的时刻为调度请求触发时刻；
在步骤S11中，若发送调度请求，通过发送的调度请求来请求上行共享信道资源，通过请求的上行共享信道资源向所述基站传输缓存状态报告。
在步骤S12中，若不发送调度请求，通过向所述基站发起随机接入请求上行共享信道资源，通过请求的上行共享信道资源向所述基站传输缓存状态报告。
在一个实施例中，若不存在上行可用的上行共享信道资源，可以确定是否发送调度请求SR，并在确定发送调度请求的情况下，通过调度请求来请求上行共享信道资源，以便可以通过请求道的上行共享信道资源向所述基站传输缓存状态报告；而在确定不发送调度请求的情况下，则可以通过向基站发起随机接入请求上行共享信道资源，并通过请求道的上行共享信道资源向所述基站传输缓存状态报告。从而保证用户设备能够顺利地向基站传输缓存状态报告。
需要说明的是，对于图12所示实施例中“若不存在上行传输机会中有可用的上行共享信道资源”这一判断条件，是指不满足条件A：“从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，存在可用的上行共享信道资源”。
还可以指不满足条件B：“可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔”，或不满足条件C：“若存在上行传输机会中有可用的上行共享信道资源，可用的上行共享信道资源可以携带缓存状态报告”，或既不满足条件B，也不满足条件C。
在一个实施例中，可以在主小区或主辅小区上发起随机接入请求。
图13是根据本公开一个实施例示出的一种确定是否发送调度请求的示意流程图。如图13所示，在图12所示实施例的基础上，所述确定是否发送调度请求包括：
在步骤1101中，判断从所述调度请求的触发时刻起，以及以所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
在步骤1102中，对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
在步骤1103中，若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
在一个实施例中，可以先判断从所述调度请求的触发时刻起，以及以所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源，若存在上行传输机会中有可用的上行共享信道资源，那么可以通过该可用的上行共享信道资源传输缓存状态报告，从而无需发送调度请求。
而当不存在上行传输机会中有可用的上行共享信道资源，则进一步确定上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源，若被配置了物上行控制信道资源，则可以通过物上行控制信道资源发送调度信息，因此确定发送调度信息，而若没有被配置物理上行控制信道资源，那么就无法发送调度信息，因此确定不发送调度信息。
图14是根据本公开一个实施例示出的另一种确定是否发送调度请求的示意流程图。如图14所示，在图12所示实施例的基础上，所述确定是否发送调度请求包括：
在步骤1104中，判断以所述调度请的求触发时刻之前最近的物理下行控制信道的时刻，以及所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
在步骤1105中，对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
在步骤1106中，若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
在一个实施例中，可以先判断以所述调度请的求触发时刻之前最近的物理下行 控制信道的时刻，以及所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源，若存在上行传输机会中有可用的上行共享信道资源，那么可以通过该可用的上行共享信道资源传输缓存状态报告，从而无需发送调度请求。
而当不存在上行传输机会中有可用的上行共享信道资源，则进一步确定上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源，若被配置了物上行控制信道资源，则可以通过物上行控制信道资源发送调度信息，因此确定发送调度信息，而若没有被配置物理上行控制信道资源，那么就无法发送调度信息，因此确定不发送调度信息。
图15是根据本公开一个实施例示出的一种确定是否发送调度请求的示意图。
在一个实施例中，针对调度请求的触发时刻之后每个物理下行控制信道，可以逐个物理下行控制信道地判断，以物理下行控制信道的时刻(例如物理下行控制信道的起始时刻，或者物理下行控制信道的结束时刻)为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源。
如图15所示，其中第一个T为从调度请的求触发时刻之前最近的物理下行控制信道的时刻持续预估时长的时间范围；第二个T为以调度请求的触发时刻之后第一个物理下行控制信道的时刻为起点，持续预估时长的时间范围；第三个T为以调度请求的触发时刻之后第二个物理下行控制信道的时刻为起点，持续预估时长的时间范围，以此类推，针对每一个持续预估时长的时间范围，若确定发送调度信息，可以分别发送调度信息。
图16是根据本公开一个实施例示出的又一种确定是否发送调度请求的示意流程图。如图16所示，在图12所示实施例的基础上，所述确定是否发送调度请求包括：
在步骤1107中，确定发送调度请求的载波对应的预设间隔，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
在步骤1108中，判断可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源；
在步骤1109中，对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
在步骤110A中，若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
在一个实施例中，可以先判断以所述调度请求的触发时刻之前最近的物理下行控制信道的时刻加预设间隔的时刻，以及所述调度请求的触发时刻之后每个物理下行控制信道的时刻加预设间隔的时刻为起点，持续所述预估时长的时间范围内，上行传输机会中是否有可用的上行共享信道资源，若存在上行传输机会中有可用的上行共享信道资源，那么可以通过该可用的上行共享信道资源传输缓存状态报告，从而无需发送调度请求。
而当不存在上行传输机会中有可用的上行共享信道资源，则进一步确定上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源，若被配置了物上行控制信道资源，则可以通过物上行控制信道资源发送调度信息，因此确定发送调度信息，而若没有被配置物理上行控制信道资源，那么就无法发送调度信息，因此确定不发送调度信息。
图17是根据本公开一个实施例示出的又一种确定是否发送调度请求的示意流程图。如图17所示，在图12所示实施例的基础上，所述确定是否发送调度请求包括：
在步骤110B中，针对所述调度请求的触发时刻之后的每一个上行传输机会，逐个判断是否有可用的上行共享信道资源；
在步骤110C中，对于没有可用的上行共享信道资源的上行传输机会，确定在该上行传输机会与上一个上行传输机会之间所对应的时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
在步骤110D中，若介质访问控制实体被配置了可用的物理上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
在一个实施例中，可以针对所述调度请求的触发时刻之后的每一个上行传输机会，逐个判断是否有可用的上行共享信道资源。对于有可用的上行共享信道资源的上行传输机会，可以通过可用的上行共享信道资源发送缓存状态报告，因此不触发调度 请求。
对于没有可用的上行共享信道资源的上行传输机会，可以触发调度请求，而为了确定是否发送调度请求，还需要进一步确定在该上行传输机会与上一个上行传输机会(在调度请求触发时刻之前)之间所对应的时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源。
其中，若介质访问控制实体被配置了可用的物理上行控制信道资源，那么可以通过可用的物理上行控制信道资源发送调度请求，确定发送调度请求；而若介质访问控制实体未被配置了可用的物理上行控制信道资源，确定不发送调度请求，通过发起随机接入来请求上行共享信道资源。
需要说明的是，在图12至图17所示的任一实施例中，在确定发送调度请求的情况下，还可以进一步判断SR的发送次数是否大于或等于预设次数，并在发送次数小于预设次数的情况下，才确定发送调度请求，否则，确定不发送调度请求。
在确定发送调度请求的情况下，还可以进一步判断调度请求抑制定时器是否运行，并在调度请求抑制定时器未运行的情况下，才确定发送调度请求，否则，确定不发送调度请求。
可选地，在图13至图17所示的任一实施例的基础上，所述方法还包括：
若存在多个可用的上行控制信道资源，选择距离当前时刻最近的可用的上行控制信道资源发送调度请求。
在一个实施例中，在存在多个可用的上行控制信道资源的额情况下，选择距离当前时刻最近的可用的上行控制信道资源发送调度请求，可以降低发送调度请求的时间延迟。
与上述缓存状态报告传输方法的实施例相对应地，本公开还提出了缓存状态报告传输装置的实施例。
图18是根据本公开一个实施例示出的一种缓存状态报告传输装置的示意框图。本实施例所示的缓存状态报告传输方法可以适用于用户设备，所述用户设备可以是手机、平板电脑、可穿戴设备等电子设备。
如图18所示，所述缓存状态报告传输装置可以包括：
配置消息接收模块1，被配置为接收基站发送的配置消息；
时间间隔确定模块2，被配置为根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
预估时长确定模块3，被配置为根据所述时间间隔确定预估时长；
时刻确定模块4，被配置为确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
资源确定模块5，被配置为确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
报告传输模块6，被配置为若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
图19是根据本公开一个实施例示出的另一种缓存状态报告传输装置的示意框图。如图19所示，在图18所示实施例的基础上，所述装置还包括：
时长确定模块7，被配置为根据所述配置消息确定上行共享信道最大传输时长；
其中，所述预估时长确定模块3包括：
获取子模块301，被配置为从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
确定子模块302，被配置为确定所述关联关系表中小于所述上行共享信道最大传输时长的共享信道传输时长对应的时间间隔中，最大的时间间隔为所述预估时长；或确定所述关联关系表中所述上行共享信道最大传输时长对应的时间间隔为所述预估时长。
可选地，所述时长确定模块，被配置为根据所述配置消息中的逻辑信道的优先次序限制参数确定上行共享信道最大传输时长；若所述逻辑信道的优先次序限制参数中不存在上行共享信道最大传输时长，从所述关联关系表中获取最大的共享信道传输时长，作为所述上行共享信道最大传输时长。
可选地，所述预估时长确定模块被配置为在所述配置消息中的逻辑信道的优先次序限制参数中确定共享信道传输时长与所述时间间隔的关联关系表中的最大的时间间隔作为所述预估时长。
可选地，所述预估时长确定模块被配置为从所述配置消息中获取共享信道传输 时长与所述时间间隔的关联关系表；确定所述关联关系表中最小的时间间隔为所述预估时长。
可选地，所述预估时长确定模块被配置为从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；根据预设算法对所述关联关系表中的每个时间间隔进行计算，将计算结果作为所述预估时长。
可选地，所述预估时长确定模块还被配置为在根据所述时间间隔确定预估时长之前，若所述配置信息包含传输缓存状态报告所需用的逻辑信道对应的配置时长，其中，所述配置时长等于共享信道传输时长与所述时间间隔的关联关系表中的指定时间间隔；将所述配置时长作为预估时长。
图20是根据本公开一个实施例示出的又一种缓存状态报告传输装置的示意框图。如图20所示，在图18所示实施例的基础上，还包括：
预设间隔确定模块8，被配置为在确定是否存在上行传输机会中有可用的上行共享信道资源之前，确定传输缓存状态报告的载波对应的预设间隔(该信息可以包含在配置消息中)，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
其中，所述资源确定模块被配置为确定可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源。
可选地，所述报告传输模块被配置为若存在上行传输机会中有可用的上行共享信道资源，确定所述可用的上行共享信道资源是否可以携带缓存状态报告，若可以携带缓存状态报告，通过所述上行共享信道资源向所述基站传输缓存状态报告。
图21是根据本公开一个实施例示出的又一种缓存状态报告传输装置的示意框图。如图21所示，在图18所示实施例的基础上，所述装置还包括：
发送确定模块9，被配置为若不存在上行传输机会中有可用的上行共享信道资源，确定触发调度请求，确定是否发送调度请求，其中，确定触发调度请求的时刻为调度请求触发时刻；
资源请求模块10，被配置为若发送确定模块确定发送调度请求，通过发送的调度请求来请求上行共享信道资源，其中，所述报告传输模块被配置为通过请求的上行 共享信道资源向所述基站传输缓存状态报告。
随机接入模块11，被配置为若发送确定模块确定不发送调度请求，通过向所述基站发起随机接入请求上行共享信道资源，其中，所述报告传输模块被配置为通过请求的上行共享信道资源向所述基站传输缓存状态报告。
图22是根据本公开一个实施例示出的一种发送确定模块的示意框图。如图22所示，在图21所示实施例的基础上，所述发送确定模块9包括：
第一资源判断子模块901，被配置为判断从所述调度请求的触发时刻起，以及以所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
第一资源确定子模块902，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
第一发送确定子模块903，被配置为若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
图23是根据本公开一个实施例示出的另一种发送确定模块的示意框图。如图23所示，在图21所示实施例的基础上，所述发送确定模块9包括：
第二资源判断子模块904，被配置为判断以所述调度请的求触发时刻之前最近的物理下行控制信道的时刻，以及所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
第二资源确定子模块905，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
第二发送确定子模块906，被配置为若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
图24是根据本公开一个实施例示出的又一种发送确定模块的示意框图。如图 24所示，在图21所示实施例的基础上，所述发送确定模块9包括：
间隔确定子模块907，被配置为确定发送调度请求的载波对应的预设间隔，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
第三资源判断子模块908，被配置为判断确定可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源；
第三资源确定子模块909，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
第三发送确定子模块910，被配置为若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
图25是根据本公开一个实施例示出的又一种发送确定模块的示意框图。如图25所示，在图21所示实施例的基础上，所述发送确定模块9包括：
第四资源判断子模块911，被配置为针对所述调度请求的触发时刻之后的每一个上行传输机会，逐个判断是否有可用的上行共享信道资源；
第四资源确定子模块912，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定在该上行传输机会与上一个上行传输机会之间所对应的时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
第四发送确定子模块913，被配置为若介质访问控制实体被配置了可用的物理上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
可选地，在图21至图24所示的任一实施例的基础上，所述装置还包括：
选择模块，被配置若存在多个可用的上行控制信道资源，选择距离当前时刻最近的可用的上行控制信道资源发送调度请求。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在相关方法的实施例中进行了详细描述，此处将不做详细阐述说明。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
本公开还提出了一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收基站发送的配置消息；
根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
根据所述时间间隔确定预估时长；
确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
本公开还提出了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现以下步骤：
接收基站发送的配置消息；
根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
根据所述时间间隔确定预估时长；
确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
图26是根据一示例性实施例示出的一种用于缓存状态报告传输的装置2600的示意框图。例如，装置2600可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图26，装置2600可以包括以下一个或多个组件：处理组件2602，存储器2604，电源组件2606，多媒体组件2608，音频组件2610，输入/输出(I/O)的接口2612，传感器组件2614，以及通信组件2616。
处理组件2602通常控制装置2600的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件2602可以包括一个或多个处理器2620来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件2602可以包括一个或多个模块，便于处理组件2602和其他组件之间的交互。例如，处理组件2602可以包括多媒体模块，以方便多媒体组件2608和处理组件2602之间的交互。
存储器2604被配置为存储各种类型的数据以支持在装置2600的操作。这些数据的示例包括用于在装置2600上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器2604可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件2606为装置2600的各种组件提供电力。电源组件2606可以包括电源管理系统，一个或多个电源，及其他与为装置2600生成、管理和分配电力相关联的组件。
多媒体组件2608包括在所述装置2600和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏 幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件2608包括一个前置摄像头和/或后置摄像头。当装置2600处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件2610被配置为输出和/或输入音频信号。例如，音频组件2610包括一个麦克风(MIC)，当装置2600处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器2604或经由通信组件2616发送。在一些实施例中，音频组件2610还包括一个扬声器，用于输出音频信号。
I/O接口2612为处理组件2602和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件2614包括一个或多个传感器，用于为装置2600提供各个方面的状态评估。例如，传感器组件2614可以检测到装置2600的打开/关闭状态，组件的相对定位，例如所述组件为装置2600的显示器和小键盘，传感器组件2614还可以检测装置2600或装置2600一个组件的位置改变，用户与装置2600接触的存在或不存在，装置2600方位或加速/减速和装置2600的温度变化。传感器组件2614可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件2614还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件2614还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件2616被配置为便于装置2600和其他设备之间有线或无线方式的通信。装置2600可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件2616经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件2616还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技 术来实现。
在示例性实施例中，装置2600可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述任一实施例所述的方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器2604，上述指令可由装置2600的处理器2620执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的公开后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本发明实施例所提供的方法和装置进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为 对本发明的限制。

Claims (32)

  1. 一种缓存状态报告传输方法，其特征在于，适用于用户设备，所述方法包括：
    接收基站发送的配置消息；
    根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
    根据所述时间间隔确定预估时长；
    确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
    确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
    若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    根据所述配置消息确定上行共享信道最大传输时长；
    所述根据所述时间间隔确定预估时长包括：
    从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
    确定所述关联关系表中小于所述上行共享信道最大传输时长的共享信道传输时长对应的时间间隔中，最大的时间间隔为所述预估时长；或
    确定所述关联关系表中所述上行共享信道最大传输时长对应的时间间隔为所述预估时长。
  3. 根据权利要求2所述的方法，其特征在于，所述根据所述配置消息确定上行共享信道最大传输时长包括：
    根据所述配置消息中的逻辑信道的优先次序限制参数确定上行共享信道最大传输时长；
    若所述逻辑信道的优先次序限制参数中不存在上行共享信道最大传输时长，从所述关联关系表中获取最大的共享信道传输时长，作为所述上行共享信道最大传输时长。
  4. 根据权利要求1所述的方法，其特征在于，所述根据所述时间间隔确定预估时长包括：
    在所述配置消息中的逻辑信道的优先次序限制参数中确定共享信道传输时长与所述时间间隔的关联关系表中的最大的时间间隔作为所述预估时长。
  5. 根据权利要求1所述的方法，其特征在于，所述根据所述时间间隔确定预估时长包括：
    从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
    确定所述关联关系表中最小的时间间隔为所述预估时长。
  6. 根据权利要求1所述的方法，其特征在于，所述根据所述时间间隔确定预估时长包括：
    从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
    根据预设算法对所述关联关系表中的每个时间间隔进行计算，将计算结果作为所述预估时长。
  7. 根据权利要求1所述的方法，其特征在于，还包括：
    在根据所述时间间隔确定预估时长之前，若所述配置信息包含传输缓存状态报告所需用的逻辑信道对应的配置时长，其中，所述配置时长等于共享信道传输时长与所述时间间隔的关联关系表中的指定时间间隔；
    将所述配置时长作为预估时长。
  8. 根据权利要求1所述的方法，其特征在于，还包括：
    在确定是否存在上行传输机会中有可用的上行共享信道资源之前，确定传输缓存状态报告的载波对应的预设间隔，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
    所述确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源还包括：
    确定可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源。
  9. 根据权利要求1所述的方法，其特征在于，若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告包括：
    若存在上行传输机会中有可用的上行共享信道资源，确定所述可用的上行共享信道资源是否可以携带缓存状态报告，若可以携带缓存状态报告，通过所述上行共享信道资源向所述基站传输缓存状态报告。
  10. 根据权利要求1所述的方法，其特征在于，还包括：
    若不存在上行传输机会中有可用的上行共享信道资源，确定触发调度请求，确定是否发送调度请求，其中，确定触发调度请求的时刻为调度请求触发时刻；
    若发送调度请求，通过发送的调度请求来请求上行共享信道资源，通过请求的上行共享信道资源向所述基站传输缓存状态报告；
    若不发送调度请求，通过向所述基站发起随机接入请求上行共享信道资源，通过请求的上行共享信道资源向所述基站传输缓存状态报告。
  11. 根据权利要求10所述的方法，其特征在于，所述确定是否发送调度请求包括：
    判断从所述调度请求的触发时刻起，以及以所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
    对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
    若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
  12. 根据权利要求10所述的方法，其特征在于，所述确定是否发送调度请求包括：
    判断以所述调度请的求触发时刻之前最近的物理下行控制信道的时刻，以及所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
    对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
    若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
  13. 根据权利要求10所述的方法，其特征在于，所述确定是否发送调度请求包括：
    确定发送调度请求的载波对应的预设间隔，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
    判断可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源；
    对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
    若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上 行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
  14. 根据权利要求10所述的方法，其特征在于，所述确定是否发送调度请求包括：
    针对所述调度请求的触发时刻之后的每一个上行传输机会，逐个判断是否有可用的上行共享信道资源；
    对于没有可用的上行共享信道资源的上行传输机会，确定在该上行传输机会与上一个上行传输机会之间所对应的时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
    若介质访问控制实体被配置了可用的物理上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
  15. 根据权利要求11至14中任一项所述的方法，其特征在于，还包括：
    若存在多个可用的上行控制信道资源，选择距离当前时刻最近的可用的上行控制信道资源发送调度请求。
  16. 一种缓存状态报告传输装置，其特征在于，适用于用户设备，所述装置包括：
    配置消息接收模块，被配置为接收基站发送的配置消息；
    时间间隔确定模块，被配置为根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
    预估时长确定模块，被配置为根据所述时间间隔确定预估时长；
    时刻确定模块，被配置为确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
    资源确定模块，被配置为确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
    报告传输模块，被配置为若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
  17. 根据权利要求16所述的装置，其特征在于，还包括：
    时长确定模块，被配置为根据所述配置消息确定上行共享信道最大传输时长；
    其中，所述预估时长确定模块包括：
    获取子模块，被配置为从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；
    确定子模块，被配置为确定所述关联关系表中小于所述上行共享信道最大传输时长的共享信道传输时长对应的时间间隔中，最大的时间间隔为所述预估时长；或
    确定所述关联关系表中所述上行共享信道最大传输时长对应的时间间隔为所述预估时长。
  18. 根据权利要求17所述的装置，其特征在于，所述时长确定模块，被配置为根据所述配置消息中的逻辑信道的优先次序限制参数确定上行共享信道最大传输时长；若所述逻辑信道的优先次序限制参数中不存在上行共享信道最大传输时长，从所述关联关系表中获取最大的共享信道传输时长，作为所述上行共享信道最大传输时长。
  19. 根据权利要求16所述的装置，其特征在于，所述预估时长确定模块被配置为在所述配置消息中的逻辑信道的优先次序限制参数中确定共享信道传输时长与所述时间间隔的关联关系表中的最大的时间间隔作为所述预估时长。
  20. 根据权利要求16所述的装置，其特征在于，所述预估时长确定模块被配置为从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；确定所述关联关系表中最小的时间间隔为所述预估时长。
  21. 根据权利要求16所述的装置，其特征在于，所述预估时长确定模块被配置为从所述配置消息中获取共享信道传输时长与所述时间间隔的关联关系表；根据预设算法对所述关联关系表中的每个时间间隔进行计算，将计算结果作为所述预估时长。
  22. 根据权利要求16所述的装置，其特征在于，所述预估时长确定模块还被配置为在根据所述时间间隔确定预估时长之前，若所述配置信息包含传输缓存状态报告所需用的逻辑信道对应的配置时长，其中，所述配置时长等于共享信道传输时长与所述时间间隔的关联关系表中的指定时间间隔；将所述配置时长作为预估时长。
  23. 根据权利要求16所述的装置，其特征在于，还包括：
    预设间隔确定模块，被配置为在确定是否存在上行传输机会中有可用的上行共享信道资源之前，确定传输缓存状态报告的载波对应的预设间隔，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
    其中，所述资源确定模块被配置为确定可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源。
  24. 根据权利要求16所述的装置，其特征在于，所述报告传输模块被配置为若存在上行传输机会中有可用的上行共享信道资源，确定所述可用的上行共享信道资源是否可以携带缓存状态报告，若可以携带缓存状态报告，通过所述上行共享信道资源向 所述基站传输缓存状态报告。
  25. 根据权利要求16所述的装置，其特征在于，还包括：
    发送确定模块，被配置为若不存在上行传输机会中有可用的上行共享信道资源，确定触发调度请求，确定是否发送调度请求，其中，确定触发调度请求的时刻为调度请求触发时刻；
    资源请求模块，被配置为若发送确定模块确定发送调度请求，通过发送的调度请求来请求上行共享信道资源，其中，所述报告传输模块被配置为通过请求的上行共享信道资源向所述基站传输缓存状态报告；
    随机接入模块，被配置为若发送确定模块确定不发送调度请求，通过向所述基站发起随机接入请求上行共享信道资源，其中，所述报告传输模块被配置为通过请求的上行共享信道资源向所述基站传输缓存状态报告。
  26. 根据权利要求25所述的装置，其特征在于，所述发送确定模块包括：
    第一资源判断子模块，被配置为判断从所述调度请求的触发时刻起，以及以所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
    第一资源确定子模块，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
    第一发送确定子模块，被配置为若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
  27. 根据权利要求25所述的装置，其特征在于，所述发送确定模块包括：
    第二资源判断子模块，被配置为判断以所述调度请的求触发时刻之前最近的物理下行控制信道的时刻，以及所述调度请求的触发时刻之后每个物理下行控制信道的时刻为起点，持续所述预估时长的时间范围内，是否存在上行传输机会中有可用的上行共享信道资源；
    第二资源确定子模块，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
    第二发送确定子模块，被配置为若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不 发送调度请求。
  28. 根据权利要求25所述的装置，其特征在于，所述发送确定模块包括：
    间隔确定子模块，被配置为确定发送调度请求的载波对应的预设间隔，其中，所述预设间隔为从用户设备接收到包含所述上行资源分配指示信息所在的物理下行控制信道的结束时刻起，到最近的可能的可以进行物理下行共享信道发送的起始时刻，用户设备所需要的处理时间；
    第三资源判断子模块，被配置为判断可用的上行共享信道资源到所述缓存状态报告的触发时刻的时长是否大于所述预设间隔，若大于，确定存在上行传输机会中有可用的上行共享信道资源；
    第三资源确定子模块，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定该上行传输机会所对应的预估时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
    第三发送确定子模块，被配置为若该上行传输机会所对应的预估时长内，介质访问控制实体被配置了可用的物上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
  29. 根据权利要求25所述的装置，其特征在于，所述发送确定模块包括：
    第四资源判断子模块，被配置为针对所述调度请求的触发时刻之后的每一个上行传输机会，逐个判断是否有可用的上行共享信道资源；
    第四资源确定子模块，被配置为对于没有可用的上行共享信道资源的上行传输机会，确定在该上行传输机会与上一个上行传输机会之间所对应的时长内，介质访问控制实体是否被配置了可用的物上行控制信道资源；
    第四发送确定子模块，被配置为若介质访问控制实体被配置了可用的物理上行控制信道资源，确定发送调度请求，否则，确定不发送调度请求。
  30. 根据权利要求26至29中任一项所述的装置，其特征在于，还包括：
    选择模块，被配置若存在多个可用的上行控制信道资源，选择距离当前时刻最近的可用的上行控制信道资源发送调度请求。
  31. 一种电子设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    接收基站发送的配置消息；
    根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
    根据所述时间间隔确定预估时长；
    确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
    确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
    若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
  32. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现以下步骤：
    接收基站发送的配置消息；
    根据所述配置消息确定所述基站发送的上行资源分配指示信息与该上行资源分配指示信息对应的上行传输的时间间隔；
    根据所述时间间隔确定预估时长；
    确定缓存状态报告的触发时刻，以及在所述缓存状态报告的触发时刻之前最近的物理下行控制信道的时刻；
    确定从所述缓存状态报告的触发时刻或从所述物理下行控制信道的时刻起，持续所述预估时长的时间范围内的上行传输机会中，是否存在上行传输机会中有可用的上行共享信道资源；
    若存在上行传输机会中有可用的上行共享信道资源，通过所述可用的上行共享信道资源向所述基站传输缓存状态报告。
PCT/CN2017/115300 2017-12-08 2017-12-08 缓存状态报告传输和装置 WO2019109353A1 (zh)

Priority Applications (10)

Application Number Priority Date Filing Date Title
CN201780002117.5A CN108401517B (zh) 2017-12-08 2017-12-08 缓存状态报告传输和装置
PCT/CN2017/115300 WO2019109353A1 (zh) 2017-12-08 2017-12-08 缓存状态报告传输和装置
PCT/CN2018/071406 WO2019109447A1 (zh) 2017-12-08 2018-01-04 缓存状态报告传输和装置
CN201880000012.0A CN108476432B (zh) 2017-12-08 2018-01-04 缓存状态报告传输和装置
US16/472,744 US11071129B2 (en) 2017-12-08 2018-01-18 Buffer status report transmission and device
PCT/CN2018/073259 WO2019109478A1 (zh) 2017-12-08 2018-01-18 缓存状态报告传输和装置
CN202210376781.9A CN114828083A (zh) 2017-12-08 2018-01-18 缓存状态报告传输和装置
EP18886442.5A EP3695643A4 (en) 2017-12-08 2018-01-18 BUFFER STATUS REPORT SUBMISSION AND DEVICE
CN201880000034.7A CN108391462B (zh) 2017-12-08 2018-01-18 缓存状态报告传输和装置
US17/333,455 US11877280B2 (en) 2017-12-08 2021-05-28 Buffer status report transmission and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/115300 WO2019109353A1 (zh) 2017-12-08 2017-12-08 缓存状态报告传输和装置

Publications (1)

Publication Number Publication Date
WO2019109353A1 true WO2019109353A1 (zh) 2019-06-13

Family

ID=63095099

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/CN2017/115300 WO2019109353A1 (zh) 2017-12-08 2017-12-08 缓存状态报告传输和装置
PCT/CN2018/071406 WO2019109447A1 (zh) 2017-12-08 2018-01-04 缓存状态报告传输和装置
PCT/CN2018/073259 WO2019109478A1 (zh) 2017-12-08 2018-01-18 缓存状态报告传输和装置

Family Applications After (2)

Application Number Title Priority Date Filing Date
PCT/CN2018/071406 WO2019109447A1 (zh) 2017-12-08 2018-01-04 缓存状态报告传输和装置
PCT/CN2018/073259 WO2019109478A1 (zh) 2017-12-08 2018-01-18 缓存状态报告传输和装置

Country Status (4)

Country Link
US (2) US11071129B2 (zh)
EP (1) EP3695643A4 (zh)
CN (3) CN108401517B (zh)
WO (3) WO2019109353A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108401517B (zh) 2017-12-08 2022-01-11 北京小米移动软件有限公司 缓存状态报告传输和装置
CN110461041B (zh) * 2018-05-07 2021-05-11 维沃移动通信有限公司 一种操作控制方法、移动通信终端及网络侧设备
CN110838899B (zh) * 2018-08-16 2021-12-24 大唐移动通信设备有限公司 一种直接通信链路资源分配方法及终端
KR102554392B1 (ko) * 2018-09-28 2023-07-11 삼성전자주식회사 무선 통신 시스템에서 버퍼상태 보고를 전송하기 위한 방법 및 장치
CN111132091B (zh) * 2018-10-31 2021-10-22 大唐移动通信设备有限公司 资源分配方法及装置
CN111294936B (zh) * 2018-12-06 2023-04-14 大唐移动通信设备有限公司 一种传输方法及终端
WO2020114058A1 (en) * 2018-12-07 2020-06-11 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for buffer status report enhancement
CN113303007A (zh) * 2019-01-16 2021-08-24 瑞典爱立信有限公司 网络节点和在其中执行的用于处理基带资源的方法
US11758513B2 (en) 2020-04-20 2023-09-12 Qualcomm Incorporated Physical uplink control channel with uplink message short data field
US11523301B2 (en) * 2020-04-20 2022-12-06 Qualcomm Incorporated Physical uplink control channel with buffer status report
EP4150814A1 (en) * 2020-05-15 2023-03-22 Telefonaktiebolaget LM ERICSSON (PUBL) Uplink polling for new radio operation in mm-wave frequency bands
CN116193603A (zh) * 2021-11-25 2023-05-30 展讯通信（上海）有限公司 侧边链路波束报告汇报方法及装置、存储介质、终端设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102118189A (zh) * 2009-12-31 2011-07-06 华为技术有限公司 一种基于竞争资源的配置方法和装置
CN102333341A (zh) * 2010-07-13 2012-01-25 华为技术有限公司 数据传输方法、用户设备和基站
EP2816844A1 (en) * 2013-06-21 2014-12-24 Alcatel Lucent Method and apparatus for providing radio access information
CN104780608A (zh) * 2014-01-13 2015-07-15 中兴通讯股份有限公司 配置信息的下发、处理方法及装置

Family Cites Families (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101771521B (zh) 2009-01-06 2013-11-06 中兴通讯股份有限公司 一种缓冲区状态报告重传定时器的管理方法
CN101778418B (zh) * 2009-01-13 2014-03-19 中兴通讯股份有限公司 无线网络中触发或上报调度请求的方法和设备
CN101932019B (zh) * 2009-06-19 2015-06-03 中兴通讯股份有限公司 一种实现上报缓冲区状态报告的方法、终端及网络系统
WO2011079812A1 (zh) 2009-12-31 2011-07-07 华为技术有限公司 一种基于竞争资源的配置方法和装置
CN102202343B (zh) * 2010-03-23 2013-11-27 电信科学技术研究院 资源分配方法和用户侧上报bsr的方法及网络侧设备
US8625415B2 (en) * 2010-04-02 2014-01-07 Nokia Siemens Networks Oy Dynamic buffer status report selection for carrier aggregation
CN102761967B (zh) * 2011-04-29 2015-09-23 华为技术有限公司 数据发送方法、传输资源分配方法和装置
EP2798764B1 (en) 2011-12-30 2019-05-22 Nokia Technologies Oy Method and apparatus for coverage extension
CN104144512B (zh) * 2013-05-10 2017-09-08 上海贝尔股份有限公司 支持多连接的上行链路调度信息报告的装置与系统
EP2854444A1 (en) 2013-09-27 2015-04-01 Panasonic Intellectual Property Corporation of America Efficient uplink scheduling mechanism for dual connectivity
CN104661311B (zh) * 2013-11-25 2019-07-23 中兴通讯股份有限公司 载波聚合下缓存状态报告处理方法、装置及终端
EP3120607B1 (en) 2014-03-19 2019-09-11 LG Electronics Inc. Method and apparatus for configuring buffer status report for public safety transmission in wireless communication system
US10064035B2 (en) 2014-11-07 2018-08-28 Nokia Technologies Oy Device-to-device (D2D) resource release
CN112087794A (zh) 2014-12-23 2020-12-15 Idac控股公司 通过无线发射/接收单元wtru执行的用于传达数据的方法
WO2016119102A1 (zh) * 2015-01-26 2016-08-04 富士通株式会社 缓存状态报告的处理方法、装置以及通信系统
US10117229B2 (en) 2015-06-12 2018-10-30 Asustek Computer Inc. Method and apparatus for using a configured resource in a wireless communication system
CN105050189B (zh) 2015-08-10 2019-02-05 上海华为技术有限公司 一种无线资源调度的方法及相关设备
TWI619400B (zh) 2015-11-04 2018-03-21 財團法人資訊工業策進會 用於對一無線通訊資源進行排程之方法及裝置
US10355830B2 (en) 2015-12-07 2019-07-16 Telefonaktiebolaget Lm Ericsson (Publ) Uplink mac protocol aspects
US20180361678A1 (en) 2015-12-08 2018-12-20 Sabic Global Technologies B.V. Apparatus and methods of use for form, fill and sealing dies and packages formed thereby
CN107046727B (zh) 2016-02-06 2020-10-09 上海无线通信研究中心 一种上行资源共享方法、基站及终端
US10412620B2 (en) 2016-04-01 2019-09-10 Motorola Mobility Llc Method and apparatus for scheduling uplink transmissions with reduced latency
JP6435007B2 (ja) 2016-04-01 2018-12-05 華碩電腦股▲ふん▼有限公司 ワイヤレス通信システムにおける設定されたリソースを使用して送信を改善する方法及び装置
CN107277656B (zh) 2016-04-06 2019-11-05 宏碁股份有限公司 电子装置、检测装置和耳机播放设定方法
US10200991B2 (en) * 2016-04-25 2019-02-05 Ofinno Technologies, Llc Scheduling request process in a wireless device and wireless network
CN107347215B (zh) 2016-05-06 2019-11-08 普天信息技术有限公司 在v2x网络中资源的分配方法及终端
US20190150176A1 (en) 2016-05-12 2019-05-16 Idac Holdings, Inc. Flow-based processing in wireless systems
CN107370575A (zh) 2016-05-13 2017-11-21 电信科学技术研究院 一种自动重传的调度方法、终端及网络侧设备
CN106714213B (zh) * 2016-12-30 2019-06-21 北京小米移动软件有限公司 缓存状态报告bsr上报触发方法、装置和用户终端
CN107277856A (zh) 2017-05-05 2017-10-20 电信科学技术研究院 一种配置、触发缓冲区状态上报的方法及装置
CN108476432B (zh) 2017-12-08 2021-12-03 北京小米移动软件有限公司 缓存状态报告传输和装置
CN108401517B (zh) 2017-12-08 2022-01-11 北京小米移动软件有限公司 缓存状态报告传输和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102118189A (zh) * 2009-12-31 2011-07-06 华为技术有限公司 一种基于竞争资源的配置方法和装置
CN102333341A (zh) * 2010-07-13 2012-01-25 华为技术有限公司 数据传输方法、用户设备和基站
EP2816844A1 (en) * 2013-06-21 2014-12-24 Alcatel Lucent Method and apparatus for providing radio access information
CN104780608A (zh) * 2014-01-13 2015-07-15 中兴通讯股份有限公司 配置信息的下发、处理方法及装置

Also Published As

Publication number Publication date
WO2019109447A1 (zh) 2019-06-13
CN108391462B (zh) 2022-04-29
CN108391462A (zh) 2018-08-10
US20210289526A1 (en) 2021-09-16
US20210136793A1 (en) 2021-05-06
US11877280B2 (en) 2024-01-16
WO2019109478A1 (zh) 2019-06-13
US11071129B2 (en) 2021-07-20
EP3695643A4 (en) 2020-10-28
CN108401517B (zh) 2022-01-11
CN114828083A (zh) 2022-07-29
EP3695643A1 (en) 2020-08-19
CN108401517A (zh) 2018-08-14

Similar Documents

Publication Publication Date Title
WO2019109353A1 (zh) 缓存状态报告传输和装置
JP7328994B2 (ja) 情報多重伝送方法及び装置、情報受信方法及び装置
WO2019183881A1 (zh) 信息上报方法及装置和基于带宽部分的操作方法及装置
WO2019191967A1 (zh) 调度请求传输方法和调度请求传输装置
WO2019192021A1 (zh) 上行资源请求方法及装置
WO2019218366A1 (zh) 前导码和调度请求的发送方法及装置
WO2020034072A1 (zh) 上行调度请求的发送方法、装置、设备及存储介质
WO2019100402A1 (zh) 信息指示方法及装置、基站和用户设备
WO2019024039A1 (zh) 指示多业务数据复用传输的方法及装置、终端和基站
WO2019237360A1 (zh) 确定上下行切换点的方法及装置
US20220278779A1 (en) Time interval determination method and harq-ack sending method
WO2018201439A1 (zh) 随机接入方法及装置、用户设备和计算机可读存储介质
EP3751892B1 (en) Trigger hold method and trigger hold apparatus
WO2019127109A1 (zh) 调度方法、基站、终端及存储介质
WO2019218367A1 (zh) 信息传输方法及装置
WO2019127248A1 (zh) 数据传输方法和装置
WO2019148495A1 (zh) 系统消息接收方法和装置、系统消息发送方法和装置
CN108476432B (zh) 缓存状态报告传输和装置
WO2019056385A1 (zh) 随机接入方法及装置、用户设备和计算机可读存储介质
WO2019033431A1 (zh) 上行资源分配方法、装置和终端
WO2018227615A1 (zh) 一种数据调度方法及装置
WO2018201336A1 (zh) 下行控制信道的接收、发送方法及装置
WO2019127220A1 (zh) 数据传输方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17933895

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17933895

Country of ref document: EP

Kind code of ref document: A1