CN109121219B - Method and device for sending scheduling request, storage medium and terminal - Google Patents
Method and device for sending scheduling request, storage medium and terminal Download PDFInfo
- Publication number
- CN109121219B CN109121219B CN201710486346.0A CN201710486346A CN109121219B CN 109121219 B CN109121219 B CN 109121219B CN 201710486346 A CN201710486346 A CN 201710486346A CN 109121219 B CN109121219 B CN 109121219B
- Authority
- CN
- China
- Prior art keywords
- scheduling request
- logical channel
- time
- random access
- channel group
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- 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
- 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
- H04W74/00—Wireless channel access, e.g. scheduled or random access
- H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
- H04W74/0833—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using a random access procedure
Abstract
A method and device for sending a scheduling request, a storage medium and a terminal are provided, the method comprises the following steps: when data trigger a scheduling request, acquiring a scheduling request configuration parameter of a logical channel or a logical channel group to which the data belong, wherein the scheduling request configuration parameter is predetermined by a network and corresponds to the logical channel or the logical channel group; and sending the scheduling request through the allocated PUCCH resource or random access based on the scheduling request configuration parameter and the triggering moment of the scheduling request. The technical scheme provided by the invention can more flexibly send the scheduling request through the allocated PUCCH resources and the random access, thereby more efficiently using the uplink resources and better reducing the access time delay of the user equipment.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for sending a scheduling request, a storage medium, and a terminal.
Background
Based on the existing Long Term Evolution (LTE) specification, two schemes are provided to send Scheduling Requests (SR). One of the schemes is to allocate Physical Uplink Control Channel (PUCCH) resources to User Equipment (User Equipment, UE for short) so that the User Equipment can use the allocated PUCCH resources to send its scheduling request to the network; if the user equipment is not allocated to PUCCH resources, the user equipment may execute the second scheme, that is, may execute a Random Access (RA) procedure to transmit its scheduling request.
Based on the two schemes, in practical application, if the user equipment is allocated with PUCCH resources, the user equipment will not initiate random access.
Although the scheme can meet the requirement of sending the scheduling request to the network by the user equipment to a certain extent, the problems of resource waste, extension in access and the like still exist. For example, for a scenario in which a user equipment is allocated with PUCCH resources, since the network does not know how much data the user equipment will transmit at, the network may allocate a scheduling request with a longer period (period) on each Logical Channel (LCH) for the user equipment. Such a scheme, while capable of improving resource utilization to some extent, may also result in a potentially long delay, e.g., the user equipment may need to wait for a longer time to transmit a scheduling request within a scheduling request period. In another prior art scheme, the period of the scheduling request allocated to the user equipment by the network is relatively short in order to shorten the access delay of the user equipment, but the resource of the PUCCH is limited, and such an allocation manner is very likely to cause resource waste.
At present, in most cases, when the ue really needs to use a resource carried by one of the logical channels (or a logical channel group, which may be determined according to a specific implementation) to send a scheduling request, an excessively long scheduling request period may increase access delay of the ue, which affects communication efficiency between the ue and the network.
Disclosure of Invention
The technical problem solved by the invention is how to more flexibly send the scheduling request through the allocated PUCCH resources and the random access.
To solve the foregoing technical problem, an embodiment of the present invention provides a method for sending a scheduling request, including: when data trigger a scheduling request, acquiring a scheduling request configuration parameter of a logical channel or a logical channel group to which the data belong, wherein the scheduling request configuration parameter is predetermined by a network and corresponds to the logical channel or the logical channel group; and sending the scheduling request through the allocated PUCCH resource or random access based on the scheduling request configuration parameter and the triggering moment of the scheduling request.
Optionally, the scheduling request configuration parameter includes a scheduling request period and a preset time threshold, where the scheduling request period is an interval between available time blocks of adjacent scheduling requests.
Optionally, the sending the scheduling request through the allocated PUCCH resource or the random access based on the scheduling request configuration parameter and the trigger time of the scheduling request includes: when the time interval between the trigger moment and the available time block of the next scheduling request is greater than or equal to a preset time threshold, the scheduling request is sent through random access; otherwise, the scheduling request is transmitted through the allocated PUCCH resource at the next scheduling request available time block.
Optionally, the scheduling request configuration parameters include a scheduling request period, a preset time threshold, and a preset buffer threshold, where the scheduling request period is an interval between available time blocks of adjacent scheduling requests.
Optionally, the sending the scheduling request through the allocated PUCCH resource or the random access based on the scheduling request configuration parameter and the trigger time of the scheduling request includes: when the buffer amount of the logical channel or the logical channel group is larger than or equal to the preset buffer threshold, determining to send the scheduling request through allocated PUCCH resources or random access according to a comparison result of a time interval between the trigger time and a next available scheduling request time block and a preset time threshold; otherwise, the scheduling request is transmitted through the allocated PUCCH resource at the next scheduling request available time block.
Optionally, when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold, determining to send the scheduling request through the allocated PUCCH resource or the random access according to a comparison result between a time interval from the trigger time to a next available scheduling request time block and a preset time threshold includes: and when the buffer amount of the logic channel or the logic channel group is greater than or equal to the preset buffer threshold value, and the time interval between the trigger moment and the next available scheduling request time block is greater than or equal to the preset time threshold value, sending the scheduling request through random access.
Optionally, the sending method further includes: and when the scheduling request is failed to be transmitted through the random access, transmitting the scheduling request through the allocated PUCCH resource at a next scheduling request available time block.
Optionally, when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold, determining to send the scheduling request through the allocated PUCCH resource or the random access according to a comparison result between a time interval from the trigger time to a next available scheduling request time block and a preset time threshold includes: and when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold value, and the time interval between the trigger moment and the next scheduling request available time block is smaller than the preset time threshold value, transmitting the scheduling request through the allocated PUCCH resource at the next scheduling request available time block.
Optionally, the scheduling request configuration parameter is received through an RRC message.
Optionally, before sending the scheduling request through the allocated PUCCH resource or the random access based on the scheduling request configuration parameter and the trigger time of the scheduling request, the sending method further includes: receiving indication information sent by a network, wherein the indication information is used for indicating whether the network allows the user equipment to send the scheduling request through random access under the condition that PUCCH resources are allocated to the user equipment; the sending the scheduling request through the allocated PUCCH resource or the random access based on the scheduling request configuration parameter and the trigger time of the scheduling request includes: when the indication information indicates that the network allows the user equipment to transmit the scheduling request through random access under the condition that the PUCCH resources are allocated, the scheduling request is transmitted through the allocated PUCCH resources or the random access based on the scheduling request configuration parameters and the triggering time of the scheduling request.
Optionally, the indication information is received through RRC signaling.
An embodiment of the present invention further provides a device for sending a scheduling request, including: an obtaining module, configured to obtain a scheduling request configuration parameter of a logical channel or a logical channel group to which data belongs when a scheduling request is triggered by the data, where the scheduling request configuration parameter is predetermined by a network and corresponds to the logical channel or the logical channel group; and the first sending module is used for sending the scheduling request through the allocated PUCCH resource or random access based on the scheduling request configuration parameter and the triggering moment of the scheduling request.
Optionally, the scheduling request configuration parameter includes a scheduling request period and a preset time threshold, where the scheduling request period is an interval between available time blocks of adjacent scheduling requests.
Optionally, the first sending module includes: the first sending submodule is used for sending the scheduling request through random access when the time interval between the triggering moment and the next available scheduling request time block is greater than or equal to a preset time threshold; and a second sending submodule, configured to send the scheduling request through the allocated PUCCH resource in the next available scheduling request time block when a time interval between the trigger time and the next available scheduling request time block is less than or equal to the preset time threshold.
Optionally, the scheduling request configuration parameters include a scheduling request period, a preset time threshold, and a preset buffer threshold, where the scheduling request period is an interval between available time blocks of adjacent scheduling requests.
Optionally, the first sending module includes: the determining submodule is used for determining to send the scheduling request through allocated PUCCH resources or random access according to a comparison result of a time interval between the triggering moment and the next available scheduling request time block and a preset time threshold when the buffer amount of the logical channel or the logical channel group is larger than or equal to the preset buffer threshold; and a third sending submodule, configured to send the scheduling request through the allocated PUCCH resource in the next available scheduling request time block when the buffer amount of the logical channel or the logical channel group is smaller than the preset buffer threshold.
Optionally, the determining sub-module includes: and the first sending unit is used for sending the scheduling request through random access when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold value and the time interval between the trigger time and the next available scheduling request time block is greater than or equal to the preset time threshold value.
Optionally, the sending apparatus further includes: and a second sending module, configured to send the scheduling request through the allocated PUCCH resource at a next scheduling request available time block when sending the scheduling request through random access fails.
Optionally, the determining sub-module includes: and a second sending unit, configured to send the scheduling request through the allocated PUCCH resource in the next available scheduling request time block when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold and a time interval between the trigger time and the next available scheduling request time block is smaller than a preset time threshold.
Optionally, the scheduling request configuration parameter is received through an RRC message.
Optionally, the sending apparatus further includes: a receiving module, configured to receive indication information sent by a network before sending the scheduling request through an allocated PUCCH resource or a random access based on the scheduling request configuration parameter and a trigger time of the scheduling request, where the indication information is used to indicate whether the network allows a user equipment to send the scheduling request through the random access under a condition that the PUCCH resource is allocated; the first transmitting module includes: a fourth sending sub-module, configured to, when the indication information indicates that the network allows the user equipment to send the scheduling request through random access under the condition that the PUCCH resource is allocated, send the scheduling request through the allocated PUCCH resource or random access based on the scheduling request configuration parameter and a trigger time of the scheduling request.
Optionally, the indication information is received through RRC signaling.
The embodiment of the invention also provides a storage medium, wherein computer instructions are stored on the storage medium, and the computer instructions execute the steps of the method when running.
The embodiment of the present invention further provides a terminal, which includes a memory and a processor, where the memory stores computer instructions capable of running on the processor, and the processor executes the steps of the method when executing the computer instructions.
Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:
when data trigger a scheduling request, acquiring a scheduling request configuration parameter of a logical channel or a logical channel group to which the data belong at a user equipment side, wherein the scheduling request configuration parameter is predetermined by a network and corresponds to the logical channel or the logical channel group; and sending the scheduling request through the allocated PUCCH resource or random access based on the scheduling request configuration parameter and the triggering moment of the scheduling request. Compared with the technical scheme that the user equipment can initiate the random access program to send the scheduling request only after the scheduling request is not allocated to the PUCCH resource or the number of times of sending the scheduling request on the allocated PUCCH resource reaches a preset upper limit (for example, the sending number exceeds a value specified by a parameter dsr-TransMax).
Further, the scheduling request configuration parameter includes a scheduling request period and a preset time threshold, where the scheduling request period is an interval between available time blocks of adjacent scheduling requests. Those skilled in the art understand that, as a result of comparing the time interval from the trigger time to the next available time block of the scheduling request with the preset time threshold, the user equipment can determine the sending mode of the scheduling request more accurately. For example, when the time interval between the trigger time and the next available scheduling request time block is greater than or equal to a preset time threshold, it may be considered that the ue needs to wait for a longer time to send the scheduling request through the allocated PUCCH resource, and in order to reduce access delay, the ue may send the scheduling request through random access; otherwise, when the time interval between the trigger time and the next available scheduling request time block is smaller than the preset time threshold, it may be considered that the ue may send the scheduling request through the allocated PUCCH resource only by waiting for a short time, and then the ue may temporarily not initiate random access, but send the scheduling request through the allocated PUCCH resource at the next available scheduling request time block.
Drawings
FIG. 1 is a schematic diagram of a prior art user equipment requesting resources;
fig. 2 is a flowchart of a method for transmitting a scheduling request according to a first embodiment of the present invention;
fig. 3 is a schematic structural diagram of a scheduling request transmitting apparatus according to a second embodiment of the present invention;
fig. 4 is a signaling interaction diagram of an exemplary application scenario in which an embodiment of the present invention is employed.
Detailed Description
As described in the background art, based on the existing Long Term Evolution (LTE) protocol, a User Equipment (User Equipment, UE) initiates a Random Access (RA) procedure only when a Physical Uplink Control Channel (PUCCH) resource is not allocated, so as to send a scheduling request to a network in a Random Access manner.
The resource Request logic of the existing user equipment may be represented based on the schematic diagram shown in fig. 1, where T1 is used to represent a Scheduling Request period (which may also be referred to as a Scheduling Request interval, SR interval for short) of the user equipment, for example, the Scheduling Request period T1 shown in fig. 1 is 10ms, and when the user equipment has a need to Request resources from a network (i.e., there is data reaching the user equipment to trigger a Scheduling Request), a Scheduling Request (Scheduling Request) may be sent to the network at a first Scheduling Request available time block (SR availability resource block, which may also be referred to as a Scheduling Request available resource block) a1, a second Scheduling Request available time block a2, or a third Scheduling Request available time block a3 allocated to the user equipment.
In one prior typical application scenario in conjunction with fig. 1, the ue does not request the resource requirement at or before the first scheduling request available time block a1, and thus the ue does not send the scheduling request to the network at the first scheduling request available time block a 1; whereas in the scheduling request interval T1 after the first scheduling request available time block a1, new data arrives at the user equipment and triggers the scheduling request, i.e. the user equipment has a need to perform operation s1, i.e. needs to request resources to transmit data to the network, the user equipment performs operation s2 at the second scheduling request available time block a2 to send the scheduling request to the network; after performing the operation s2, the ue performs an operation s3 in an nth subframe (not shown in the figure) to receive the uplink grant sent by the network, and performs an operation s4 after n + x subframes to transmit data to the network using the resources provided by the uplink grant according to the existing communication protocol, where x may be 4.
Further, if the ue does not receive grant information (i.e. uplink grant of the network) in the scheduling request interval T1, the ue may resend the scheduling request when the scheduling request interval T1 expires, and enter a random access procedure until the number of retransmissions reaches a preset maximum number of retransmissions or a maximum number of retransmissions set by a protocol parameter (e.g. dsr-TransMax), so as to transmit data to the network by means of random access.
However, based on the communication protocol represented by LTE and New Radio (NR), in order to save uplink overhead, the scheduling request sent by the ue occupies only 1 bit, which results in that the network does not know when the ue sending the scheduling request will send how much data. In an existing application scenario, in order to avoid PUCCH resource block idling, the network may allocate a longer scheduling request period (SR Periodicity) to each Logical Channel (LCH) that triggers a scheduling request of the ue, so as to improve resource utilization to a certain extent. However, such schemes may also result in potentially long delays. For example, the user equipment may need to wait for a longer time to transmit the scheduling request within the scheduling request period. In another prior art scheme, the period of the scheduling request allocated to the user equipment by the network is relatively short in order to shorten the access delay of the user equipment, but the resources of the PUCCH are limited, and such an allocation manner is very prone to cause resource waste. Further, when the ue really needs to use the resource carried by one of the logical channels (or the logical channel group) to send the scheduling request, an excessively long scheduling request period also increases the access delay of the ue, which affects the communication efficiency between the ue and the network.
In order to solve the technical problem, an embodiment of the present invention provides a technical solution that can transmit a scheduling request more flexibly by using allocated PUCCH resources and random access.
In a preferred embodiment of the present invention, at a user equipment side, when data triggers a scheduling request, a scheduling request configuration parameter of a logical channel or a logical channel group to which the data belongs is obtained, where the scheduling request configuration parameter is predetermined by a network and corresponds to the logical channel or the logical channel group; and sending the scheduling request through the allocated PUCCH resource or random access based on the scheduling request configuration parameter and the triggering moment of the scheduling request. The technical solution of the embodiment of the present invention combines the allocated PUCCH resource with the random access, and can transmit the scheduling request more flexibly, so as to use the uplink resource more efficiently and reduce the access delay of the user equipment better.
Further, the scheduling request configuration parameter includes a scheduling request period and a preset time threshold, where the scheduling request period is a time interval between available time blocks of adjacent scheduling requests. Those skilled in the art understand that, as a result of comparing the time interval from the trigger time to the next available time block of the scheduling request with the preset time threshold, the user equipment can determine the sending mode of the scheduling request more accurately. For example, when the time interval between the trigger time and the next available scheduling request time block is greater than or equal to a preset time threshold, it may be considered that the ue needs to wait for a longer time to send the scheduling request through the allocated PUCCH resource, and in order to reduce access delay, the ue may send the scheduling request through random access; otherwise, when the time interval between the trigger time and the next available scheduling request time block is smaller than the preset time threshold, it may be considered that the ue may send the scheduling request through the allocated PUCCH resource only by waiting for a short time, and then the ue may temporarily not initiate random access, but send the scheduling request through the allocated PUCCH resource at the next available scheduling request time block.
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.
Fig. 2 is a flowchart of a method for sending a scheduling request according to a first embodiment of the present invention. The scheduling request is used for requesting a network for a resource of an Uplink Shared Channel (UL-SCH) to perform new transmission. For example, when new uplink data is generated and needs to be transmitted, the ue needs to send a Buffer Status Report (BSR) to the network, so as to indicate to the network that one or more Logical Channel Groups (LCGs) of the ue need to upload data. However, since the BSR also needs to transmit using uplink resources, the ue needs to transmit a scheduling request through PUCCH resources first to request uplink resources from the network. The technical scheme of the embodiment of the invention provides a more flexible scheduling request sending mode, and the distributed PUCCH resources and random access can be used more flexibly, so that the uplink resources are used more efficiently, and the access delay of user equipment is reduced better.
Specifically, in this embodiment, the sending method of the scheduling request may be implemented according to the following steps:
step S101, when there is data triggering scheduling request, obtaining scheduling request configuration parameters of a logical channel or a logical channel group to which the data belongs, wherein the scheduling request configuration parameters are predetermined by a network and correspond to the logical channel or the logical channel group.
Step S102, based on the scheduling request configuration parameter and the triggering time of the scheduling request, the scheduling request is sent through the allocated PUCCH resource or random access.
Further, when the service of the user equipment needs to transmit data to the network, the user equipment may be triggered to start a scheduling request process. Still further, the act of triggering transmission of a scheduling request may be performed on a logical channel or a group of logical channels. For example, when the logical channel on which the data arrives has its own capability of triggering a scheduling request, the scheduling request may be triggered based on the logical channel. For another example, the logical channel itself may not have the capability of triggering a scheduling request, but the logical channel group to which the logical channel belongs has the capability of triggering a scheduling request, and then, for data arriving at any logical channel in the logical channel group, the scheduling request may be triggered based on the logical channel group.
Further, the traffic (traffic) of the ue may correspond to at least one Logical Channel group, and each Logical Channel group may include at least one Logical Channel (LCH). Further, according to the correspondence between the logical channel group and the service, when the service corresponds to any logical channel included in one logical channel group, the data that the user equipment needs to transmit may correspond to the logical channel group; alternatively, when the service of the user equipment corresponds to a specific logical channel in a logical channel group, the service (or the data that the service needs to transmit) may correspond to the logical channel.
In a preferred example, the network may configure the corresponding scheduling request configuration parameter for each logical channel. For example, the scheduling request configuration parameter may include a scheduling request period, and if the priority of the logical channel triggering the scheduling request is higher, the scheduling request period corresponding to the logical channel may be shorter. Those skilled in the art understand that resources of the PUCCH can be better saved by allocating a larger scheduling request period for a specific logical channel (e.g., a logical channel with a lower priority).
Further, the scheduling request configuration parameter may be received through a Radio Resource Control (RRC) message. For example, the network may send the Scheduling Request configuration parameter to the ue through Scheduling-Request-Config (Scheduling-Request-configuration). The scheduling request configuration may include a parameter sr-ConfigIndex IE, and may further include other configuration parameters. Alternatively, the network may also send the scheduling request configuration parameter to the ue through higher layer signaling (for example, a message sent from a layer higher than the RRC layer), and those skilled in the art may change more embodiments according to actual needs, which is not described herein.
In a preferred embodiment, the network may configure corresponding scheduling request configuration parameters for all logical channels corresponding to the service of the user equipment one by one, and send configuration results to the user equipment in advance through the RRC message, and when a logical channel of the user equipment triggers a scheduling request, the user equipment searches the configuration results received in advance to obtain the scheduling request configuration parameters corresponding to the logical channel. Or, the network may configure the corresponding scheduling request configuration parameters for all logical channel groups corresponding to the service of the user equipment one by one.
Further, the scheduling request configuration parameter may include a scheduling request period and a preset time threshold, where the scheduling request period is an interval between adjacent scheduling request available time blocks.
In conjunction with fig. 1, the scheduling request period T1 may be an interval between the scheduling request available time block a1 and the scheduling request available time block a2, and similarly, the scheduling request period T1 may also be an interval between the scheduling request available time block a2 and the scheduling request available time block a 3. Preferably, for each logical channel or logical channel group, the scheduling request period of the logical channel or logical channel group is fixed, and after a scheduling request is triggered by data, the user equipment may periodically send a scheduling request to the network according to the scheduling request period corresponding to the logical channel or logical channel group to which the data belongs.
The preset time threshold may be preset by the network, or may also be pre-agreed by the network and the ue. Those skilled in the art understand that the user equipment may determine whether to initiate a random access immediately according to a comparison result of a time interval between the trigger time and a next available time block of the scheduling request and the preset time threshold, so as to send the scheduling request through the random access.
In a typical application scenario, the step S102 may include: when the time interval between the trigger moment and the available time block of the next scheduling request is greater than or equal to a preset time threshold, the scheduling request is sent through random access; otherwise, the scheduling request is transmitted through the allocated PUCCH resource at the next scheduling request available time block.
For example, referring to fig. 1, the preset time threshold may be 5ms, when the trigger time is 3ms (i.e., the ue has a need to perform operation s 1' to send a scheduling request to the network), the trigger time is 7ms away from the next available scheduling request time block a2, and since the time interval is greater than or equal to the preset time threshold, it may be considered that the ue needs to wait for a longer time (i.e., needs to wait until the available scheduling request time block a2) to send the scheduling request through the allocated PUCCH resource, and then, in order to reduce access delay, the ue may immediately send the scheduling request through random access at the trigger time.
For another example, continuing with fig. 1, the preset time threshold is still 5ms, and when the trigger time is 8ms (i.e. the ue has a need to perform operation s1 to send a scheduling request to the network), the trigger time is 2ms away from the next available scheduling request time block a2, and since the time interval is smaller than the preset time threshold, it may be considered that the ue only needs to wait a short time (i.e. at the available scheduling request time block a2) to send the scheduling request through the allocated PUCCH resource, and the ue may temporarily not initiate random access but send the scheduling request through the allocated PUCCH resource at the available scheduling request time block a 2.
Those skilled in the art understand that, in particular when the scheduling request period of the logical information or the logical channel group configuration to which the data triggering the scheduling request belongs is large, in order to better control the access delay of the user equipment, the technical solution of this embodiment may allow the user equipment to send the scheduling request through random access outside the available time block of the scheduling request. For example, for a user equipment allocated with PUCCH resources, if a service arrives right after one scheduling request available time block elapses, based on the technical solution of this embodiment, the user equipment does not need to wait for the next scheduling request available time block to arrive, but can initiate a random access procedure in parallel to issue a scheduling request in time through random access.
Further, the scheduling request configuration parameter may further include a preset buffering threshold. Preferably, the user equipment may measure, by using the preset buffer threshold, whether a buffer amount of a logical channel or a logical channel group that triggers a scheduling request is overloaded, so as to determine whether to immediately initiate random access to timely offload the buffer amount of the logical channel or the logical channel group. Preferably, the preset buffer threshold may be preset by the network, or may be pre-agreed by the network and the ue.
In a preferred embodiment, the higher the priority of the logical channel or the logical channel group is, the smaller the corresponding preset buffer threshold value may be.
In a typical application scenario, the step S102 may include: when the buffer amount of the logical channel or the logical channel group is larger than or equal to the preset buffer threshold, determining to send the scheduling request through allocated PUCCH resources or random access according to a comparison result of a time interval between the trigger time and a next available scheduling request time block and a preset time threshold; otherwise, the scheduling request is transmitted through the allocated PUCCH resource at the next scheduling request available time block.
The buffer size of the logical channel may be the sum of the sizes of data packets of all data to be sent on the logical channel; the buffer amount of the logical channel group may be a sum of sizes of data packets of all data to be sent on the logical channel group. For example, the buffer amount of the logical channel group may be a sum of all data packets of data to be transmitted on all logical channels included in the logical channel group. Alternatively, the buffer amount of the logical channel group may also be a sum of packet sizes of all data to be sent on one or more logical channels with the highest priority in the logical channel group.
For example, in the application scenario, when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold, it may be considered that the data to be sent backlogged on the logical channel or the logical channel group is excessive, and a sending manner of the scheduling request needs to be further specifically determined according to a comparison result between a time interval from the trigger time to a next available time block of the scheduling request and the preset time threshold, so as to obtain the authorization of the network as soon as possible, and thus the data to be sent on the logical channel or the logical channel group is sent out as soon as possible.
For another example, in this application scenario, when the buffer amount of the logical channel or the logical channel group is smaller than the preset buffer threshold, it may be considered that the total size of data to be sent on the logical channel or the logical channel group is still within the processing capacity of the logical channel or the logical channel group, and regardless of a comparison result between a time interval from the trigger time to a next available time block of the scheduling request and a preset time threshold, the ue may wait for the next available time block of the scheduling request to arrive, so as to send the scheduling request through the allocated PUCCH resource at the next available time block of the scheduling request.
In a preferred example of the application scenario, when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold, and the time interval between the trigger time and the next available time block of the scheduling request is greater than or equal to the preset time threshold, it may be considered that the logical channel or the logical channel group cannot wait until the next available time block of the scheduling request arrives and data to be sent needs to be shunted, and the user equipment may send the scheduling request through random access.
In another preferred example of this application scenario, when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold, and the time interval from the trigger time to the next scheduling request available time block is smaller than the preset time threshold, the scheduling request may be sent through the allocated PUCCH resource at the next scheduling request available time block.
Further, the user equipment may calculate and determine the next available time block of the scheduling request according to the scheduling request period.
Further, the buffer amount may also be used to describe a packet size of a single data to be sent on the logical channel or the logical channel group. Correspondingly, when the technical scheme of this embodiment is executed, the sizes of data packets of all data to be sent on the logical channel or the logical channel group may be respectively compared with the preset buffer threshold, and if the comparison result indicates that there is data to be sent whose buffer amount is greater than or equal to the preset buffer threshold, random access is initiated for the data to be sent, so that the data to be sent can be transmitted by obtaining uplink authorization as soon as possible.
Further, for each data to be sent on the logical channel or the logical channel group, the user equipment may further adjust a preset buffer threshold of the data to be sent according to a priority of a service (traffic) corresponding to the data to be sent, so as to ensure that the data to be sent corresponding to a service with a higher priority can be preferentially transmitted in an uplink.
Further, when the time interval between the trigger time and the next available scheduling request time block is longer (for example, greater than or equal to a preset time threshold), the user equipment may further adjust the preset buffer threshold of all to-be-sent data on the logical channel or the logical channel group to zero, so that all to-be-sent data on the logical channel or the logical channel group may be sent through random access.
Those skilled in the art understand that, for data to be sent corresponding to a high-priority service, the preset buffer threshold of the data to be sent may be set to a very small value (for example, may be set to 0), so that the buffer amount of the logical channel or the logical channel group is always greater than or equal to the preset buffer threshold, so that the user equipment can obtain more opportunities to execute a random access procedure.
Those skilled in the art will appreciate that the preset caching threshold may also be used to make an implicit indication to the network to instruct the network to allocate resources for at least the traffic of the preset caching threshold size of the user equipment.
In a variation of this embodiment, after the step S102, the method may further include the step of: and when the scheduling request is failed to be transmitted through the random access, transmitting the scheduling request through the allocated PUCCH resource at a next scheduling request available time block. Those skilled in the art understand that, with the technical solution of this variation, in the time period waiting for the next available time block of the scheduling request to arrive, the ue may fully utilize the parallel random access attempt in this time period to obtain the uplink grant of the network as soon as possible, and complete uplink data transmission.
In another variation of this embodiment, when new data arrives on the logical channel or the logical channel group during the execution of the embodiment, and the priority of the new data is higher than that of the data triggering the scheduling request of this time, the ue may execute the technical solution of this embodiment on the new data, and when the time interval between the arrival time of the new data and the available time block of the next scheduling request is greater than or equal to the preset time threshold, the new data may be preferentially sent to the network through random access, instead of the prior art (the newly arrived data is sent later than the data triggering the scheduling request first).
In yet another variation of this embodiment, before executing step S102, the method may further include the steps of: receiving indication information sent by a network, wherein the indication information is used for indicating whether the network allows the user equipment to send the scheduling request through random access under the condition that PUCCH resources are allocated. The indication information may be received through RRC signaling, or the network may send the indication information to the user equipment through higher layer signaling (for example, a message sent from a layer higher than the RRC layer), and those skilled in the art may change more embodiments according to actual needs, which is not described herein.
Further, in this variation, the step S102 may include: when the indication information indicates that the network allows the user equipment to transmit the scheduling request through random access under the condition that the PUCCH resources are allocated, the scheduling request is transmitted through the allocated PUCCH resources or the random access based on the scheduling request configuration parameters and the triggering time of the scheduling request.
Preferably, the indication information may occupy one bit.
For example, when the value of the bit occupied by the indication information is 0, it may be indicated that the indication information is used to indicate that the user equipment needs to transmit the scheduling request by using the existing mechanism, that is, if the RRC of the user equipment configures a PUCCH, the scheduling request may be transmitted through the PUCCH resource until the number of times of transmitting the scheduling request through the PUCCH resource reaches dsr-TransMax. Further, if the scheduling request does not obtain the uplink grant of the network when the sending times reach dsr-TransMax, the UE can send the scheduling request by using random access. Further, the user equipment may transmit the scheduling request directly through the random access only when its RRC is not allocated with the PUCCH resource.
For another example, when the value of the bit occupied by the indication information is 1, it may be indicated that the indication information is used to indicate that the user equipment may transmit the scheduling request through the allocated PUCCH resource or the random access in parallel by using the technical solution of the embodiment of the present invention.
In another variation of this embodiment, the equaling may also be applied to a comparison criterion smaller than that, for example, when the time interval between the trigger time and the next available time block of the scheduling request is greater than a preset time threshold, the scheduling request is sent through random access; otherwise (i.e. when the time interval from the next scheduling request available time block to the trigger time is less than or equal to a preset time threshold), the scheduling request is transmitted through the allocated PUCCH resource at the next scheduling request available time block.
In this way, with the scheme of the first embodiment, a larger scheduling request period is allowed for each logical channel or logical channel group to better utilize PUCCH resources, and at the same time, the user equipment is allowed to transmit scheduling requests in parallel through a random access procedure to better control access delay.
Fig. 3 is a schematic structural diagram of a scheduling request transmitting apparatus according to a second embodiment of the present invention. Those skilled in the art understand that the sending apparatus 3 of the scheduling request in this embodiment is used to implement the technical solution of the method in the embodiment shown in fig. 2. Specifically, in this embodiment, the sending apparatus 3 of the scheduling request includes an obtaining module 32, configured to obtain a scheduling request configuration parameter of a logical channel or a logical channel group to which the data belongs when there is data triggering the scheduling request, where the scheduling request configuration parameter is predetermined by a network and corresponds to the logical channel or the logical channel group; a first sending module 33, configured to send the scheduling request through the allocated PUCCH resource or random access based on the scheduling request configuration parameter and the trigger time of the scheduling request.
Further, the scheduling request configuration parameter includes a scheduling request period and a preset time threshold, where the scheduling request period is an interval between adjacent scheduling request available time blocks.
In a preferred embodiment, the first sending module 33 includes a first sending sub-module 3311, configured to send the scheduling request through random access when a time interval between the trigger time and a next available time block of the scheduling request is greater than or equal to a preset time threshold; the second sending submodule 3312 is configured to, when the time interval between the trigger time and the next available scheduling request time block is less than or equal to the preset time threshold, send the scheduling request through the allocated PUCCH resource in the next available scheduling request time block.
Further, the scheduling request configuration parameters include a scheduling request period, a preset time threshold and a preset cache threshold, where the scheduling request period is an interval between available time blocks of adjacent scheduling requests.
In another preferred embodiment, the first sending module 33 includes a determining sub-module 3313, configured to determine to send the scheduling request through allocated PUCCH resources or random access according to a comparison result between a time interval from a next available scheduling request time block at the trigger time to a preset time threshold when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold; a third sending submodule 3314, configured to send the scheduling request through the allocated PUCCH resource in the next available scheduling request time block when the buffer amount of the logical channel or the logical channel group is smaller than the preset buffer threshold.
Preferably, the determining submodule 3313 includes a first sending unit 33131, configured to send the scheduling request through random access when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold, and a time interval between the trigger time and a next available scheduling request time block is greater than or equal to a preset time threshold.
Further, the transmitting apparatus 3 further includes a second transmitting module 34, configured to transmit the scheduling request through the allocated PUCCH resource at a next scheduling request available time block when transmission of the scheduling request through random access fails.
Preferably, the determining sub-module 3313 includes a second sending unit 33132, configured to send the scheduling request through the allocated PUCCH resource in a next available scheduling request time block when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold and the time interval from the trigger time to the next available scheduling request time block is less than a preset time threshold.
Further, the scheduling request configuration parameter is received through an RRC message.
Further, the sending apparatus 3 further includes a receiving module 31, configured to receive indication information sent by a network before sending the scheduling request through an allocated PUCCH resource or a random access based on the scheduling request configuration parameter and a trigger time of the scheduling request, where the indication information is used to indicate whether the network allows the user equipment to send the scheduling request through the random access on a condition that the PUCCH resource is allocated; the first sending module 33 includes a fourth sending submodule 331, configured to, when the indication information indicates that the network allows the user equipment to send the scheduling request through random access under the condition that PUCCH resources are allocated, send the scheduling request through allocated PUCCH resources or random access based on the scheduling request configuration parameter and the trigger time of the scheduling request.
Preferably, the indication information is received through RRC signaling.
For more details of the operation principle and the operation mode of the scheduling request transmitter 3, reference may be made to the description in fig. 2, and details are not repeated here.
In a typical application scenario, referring to fig. 4, a signaling interaction between a user equipment and a network using an embodiment of the present invention is further described.
Specifically, in the present application scenario, the network 42 may perform operation s1 to transmit indication information to the user equipment 41, where the indication information is used to indicate whether the network 42 allows the user equipment 41 to transmit the scheduling request through random access under the condition that the PUCCH resource is allocated.
Further, when the indication information indicates that the network 42 allows the user equipment 41 to transmit the scheduling request through random access under the condition that the PUCCH resource is allocated, the network 42 may further perform operation s2 to configure a corresponding scheduling request configuration parameter for each logical channel or logical channel group of the user equipment 41.
Further, the network 42 may also perform operation s3 to send the configured scheduling request configuration parameters to the user equipment 41 through an RRC message. Accordingly, the user equipment 41 may store the received scheduling request configuration parameters locally for later use.
Further, when a scheduling request is triggered, the user equipment 41 may perform operation s4 to search for a local to obtain a scheduling request configuration parameter corresponding to a logical channel or a logical channel group to which data triggering the scheduling request belongs.
Further, after acquiring the scheduling request configuration parameter corresponding to the logical channel or the logical channel group, the user equipment 41 may further perform operation s5 to transmit the scheduling request through the allocated PUCCH resource or random access based on the scheduling request configuration parameter and the trigger time of the scheduling request. Specifically, regarding more contents such as the operation principle of performing the operation s5, those skilled in the art may refer to the description in fig. 2, which is not repeated herein.
Further, the scheduling request configuration parameters may include at least a scheduling request period and a preset time threshold, where the scheduling request period is an interval between adjacent scheduling request available time blocks. Further, the scheduling request configuration parameter may further include a preset buffering threshold.
In a preferred example, performing the operation s5 may include performing operation s51, when the time interval from the next scheduling request available time block at the trigger time is greater than or equal to a preset time threshold; or when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold value, and the time interval between the trigger time and the next available scheduling request time block is greater than or equal to the preset time threshold value, the scheduling request is sent through random access.
Further, when the transmission of the scheduling request through the random access fails, the user equipment 41 may further perform operation s6 to transmit the scheduling request through the allocated PUCCH resource at a next scheduling request available time block.
In a variation, performing the operation s5 may further include performing operation s52, when the time interval from the next scheduling request available time block at the trigger time is greater than or equal to a preset time threshold; or when the buffer amount of the logical channel or the logical channel group is smaller than the preset buffer threshold value; or, when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold and the time interval from the trigger time to the next scheduling request available time block is less than the preset time threshold, the scheduling request is sent through the allocated PUCCH resource at the next scheduling request available time block.
An embodiment of the present invention further provides a storage medium, where a computer instruction is stored, and when the computer instruction runs, the technical solution of the method in the embodiment shown in fig. 2 is executed. Preferably, the storage medium may include a computer-readable storage medium. The storage medium may include ROM, RAM, magnetic or optical disks, etc.
An embodiment of the present invention further provides a terminal, which includes a memory and a processor, where the memory stores a computer instruction capable of running on the processor, and the processor executes the technical solution of the method in the embodiment shown in fig. 2 when running the computer instruction. Preferably, the terminal may be the user equipment.
Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be effected therein by one skilled in the art without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (12)
1. A method for sending a scheduling request, comprising:
when data trigger a scheduling request, acquiring a scheduling request configuration parameter of a logical channel or a logical channel group to which the data belong, wherein the scheduling request configuration parameter is predetermined by a network and corresponds to the logical channel or the logical channel group;
based on the scheduling request configuration parameters and the triggering time of the scheduling request, sending the scheduling request through allocated PUCCH resources or random access;
the scheduling request configuration parameters comprise a scheduling request period, a preset time threshold and a preset cache threshold, wherein the scheduling request period is an interval between available time blocks of adjacent scheduling requests;
the sending the scheduling request through the allocated PUCCH resource or the random access based on the scheduling request configuration parameter and the trigger time of the scheduling request includes:
when the buffer amount of the logical channel or the logical channel group is larger than or equal to the preset buffer threshold, determining to send the scheduling request through allocated PUCCH resources or random access according to a comparison result of a time interval between the trigger time and a next available scheduling request time block and a preset time threshold; otherwise, transmitting the scheduling request through the allocated PUCCH resource at the time block available for the next scheduling request;
the buffer amount of the logical channel is the sum of the sizes of data packets of all data to be sent on the logical channel, or the size of a data packet of a single data to be sent on the logical channel;
the buffer amount of the logical channel group is the sum of the sizes of all data packets of data to be sent on the logical channel group, the sum of the sizes of all data packets of data to be sent on one or more logical channels with the highest priority in the logical channel group, or the size of a single data packet of data to be sent on the logical channel group;
when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold, determining to send the scheduling request through the allocated PUCCH resource or random access according to a comparison result between a time interval from the trigger time to a next available scheduling request time block and a preset time threshold includes:
when the buffer amount of the logic channel or the logic channel group is greater than or equal to the preset buffer threshold value, and the time interval between the trigger moment and the next available scheduling request time block is greater than or equal to the preset time threshold value, the scheduling request is sent through random access;
and when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold value, and the time interval between the trigger moment and the next scheduling request available time block is smaller than the preset time threshold value, transmitting the scheduling request through the allocated PUCCH resource at the next scheduling request available time block.
2. The transmission method of claim 1, further comprising: and when the scheduling request is failed to be transmitted through the random access, transmitting the scheduling request through the allocated PUCCH resource at a next scheduling request available time block.
3. The transmission method according to claim 1 or 2, wherein the scheduling request configuration parameter is received via an RRC message.
4. The method according to claim 1 or 2, wherein before transmitting the scheduling request through the allocated PUCCH resource or the random access based on the scheduling request configuration parameter and the trigger time of the scheduling request, the method further comprises:
receiving indication information sent by a network, wherein the indication information is used for indicating whether the network allows the user equipment to send the scheduling request through random access under the condition that PUCCH resources are allocated to the user equipment;
the sending the scheduling request through the allocated PUCCH resource or the random access based on the scheduling request configuration parameter and the trigger time of the scheduling request includes:
when the indication information indicates that the network allows the user equipment to transmit the scheduling request through random access under the condition that the PUCCH resources are allocated, the scheduling request is transmitted through the allocated PUCCH resources or the random access based on the scheduling request configuration parameters and the triggering time of the scheduling request.
5. The transmission method of claim 4, wherein the indication information is received via RRC signaling.
6. An apparatus for transmitting a scheduling request, comprising:
an obtaining module, configured to obtain a scheduling request configuration parameter of a logical channel or a logical channel group to which data belongs when a scheduling request is triggered by the data, where the scheduling request configuration parameter is predetermined by a network and corresponds to the logical channel or the logical channel group;
a first sending module, configured to send the scheduling request through allocated PUCCH resources or random access based on the scheduling request configuration parameter and a trigger time of the scheduling request;
the scheduling request configuration parameters comprise a scheduling request period, a preset time threshold and a preset cache threshold, wherein the scheduling request period is an interval between available time blocks of adjacent scheduling requests;
the first transmitting module includes:
the determining submodule is used for determining to send the scheduling request through allocated PUCCH resources or random access according to a comparison result of a time interval between the triggering moment and the next available scheduling request time block and a preset time threshold when the buffer amount of the logical channel or the logical channel group is larger than or equal to the preset buffer threshold;
a third sending submodule, configured to send the scheduling request through the allocated PUCCH resource in the next available scheduling request time block when the buffer amount of the logical channel or the logical channel group is smaller than the preset buffer threshold;
the buffer amount of the logical channel is the sum of the sizes of data packets of all data to be sent on the logical channel, or the size of a data packet of a single data to be sent on the logical channel;
the buffer amount of the logical channel group is the sum of the sizes of all data packets of data to be sent on the logical channel group, the sum of the sizes of all data packets of data to be sent on one or more logical channels with the highest priority in the logical channel group, or the size of a single data packet of data to be sent on the logical channel group;
wherein the determining sub-module includes:
a first sending unit, configured to send the scheduling request through random access when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold, and a time interval between the trigger time and a next available scheduling request time block is greater than or equal to a preset time threshold;
and a second sending unit, configured to send the scheduling request through the allocated PUCCH resource in the next available scheduling request time block when the buffer amount of the logical channel or the logical channel group is greater than or equal to the preset buffer threshold and a time interval between the trigger time and the next available scheduling request time block is smaller than a preset time threshold.
7. The transmission apparatus according to claim 6, further comprising: and a second sending module, configured to send the scheduling request through the allocated PUCCH resource at a next scheduling request available time block when sending the scheduling request through random access fails.
8. The transmitting apparatus according to claim 6 or 7, wherein the scheduling request configuration parameter is received through an RRC message.
9. The transmission apparatus according to claim 6 or 7, characterized by further comprising:
a receiving module, configured to receive indication information sent by a network before sending the scheduling request through an allocated PUCCH resource or a random access based on the scheduling request configuration parameter and a trigger time of the scheduling request, where the indication information is used to indicate whether the network allows a user equipment to send the scheduling request through the random access under a condition that the PUCCH resource is allocated;
the first transmitting module includes:
a fourth sending sub-module, configured to, when the indication information indicates that the network allows the user equipment to send the scheduling request through random access under the condition that the PUCCH resource is allocated, send the scheduling request through the allocated PUCCH resource or random access based on the scheduling request configuration parameter and a trigger time of the scheduling request.
10. The transmitting apparatus of claim 9, wherein the indication information is received through RRC signaling.
11. A storage medium having a computer program stored thereon, the computer program, when being executed by a processor, performing the steps of the method according to any of the claims 1 to 5.
12. A terminal comprising a memory and a processor, the memory having stored thereon a computer program operable on the processor, wherein the processor, when executing the computer program, performs the steps of the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710486346.0A CN109121219B (en) | 2017-06-23 | 2017-06-23 | Method and device for sending scheduling request, storage medium and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710486346.0A CN109121219B (en) | 2017-06-23 | 2017-06-23 | Method and device for sending scheduling request, storage medium and terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109121219A CN109121219A (en) | 2019-01-01 |
| CN109121219B true CN109121219B (en) | 2021-04-27 |
Family
ID=64733125
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710486346.0A Active CN109121219B (en) | 2017-06-23 | 2017-06-23 | Method and device for sending scheduling request, storage medium and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109121219B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110366260B (en) * | 2019-07-16 | 2022-11-15 | 展讯通信（上海）有限公司 | Method and device for transmitting scheduling request and storage medium |
| WO2021072961A1 (en) * | 2019-10-18 | 2021-04-22 | Oppo广东移动通信有限公司 | Priority configuration method and apparatus, and terminal device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101795497A (en) * | 2009-02-01 | 2010-08-04 | 大唐移动通信设备有限公司 | Sending method of scheduling request and EU (User Equipment) thereof |
| CN103327613A (en) * | 2012-03-18 | 2013-09-25 | 上海贝尔股份有限公司 | Method for transmitting scheduling request in wireless communication network |
| WO2017007151A1 (en) * | 2015-07-08 | 2017-01-12 | Lg Electronics Inc. | Method for triggering a buffer status report in dual connectivity and a device therefor |
-
2017
- 2017-06-23 CN CN201710486346.0A patent/CN109121219B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101795497A (en) * | 2009-02-01 | 2010-08-04 | 大唐移动通信设备有限公司 | Sending method of scheduling request and EU (User Equipment) thereof |
| CN103327613A (en) * | 2012-03-18 | 2013-09-25 | 上海贝尔股份有限公司 | Method for transmitting scheduling request in wireless communication network |
| WO2017007151A1 (en) * | 2015-07-08 | 2017-01-12 | Lg Electronics Inc. | Method for triggering a buffer status report in dual connectivity and a device therefor |
Non-Patent Citations (1)
| Title |
|---|
| General details of SR procedure in NR including SR triggers and timers，R2-1706639;Samsung Electronics R&D Institute UK;《3GPP TSG-RAN WG2 NR ad-hoc #2》;20170616;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109121219A (en) | 2019-01-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20190364573A1 (en) | Method and User Equipment for Predicting Available Throughput for Uplink Data | |
| US10314032B2 (en) | Method and base station identifying PUCCH for processing feedback of user equipment | |
| CA2704189C (en) | Method and arrangement in a telecommunications system | |
| RU2749352C2 (en) | Data transmission method, user device and radio access device | |
| RU2510598C2 (en) | Method and device in wireless communication system | |
| EP2184943A2 (en) | Method of controlling allocation of a radio resource for transmitting a radio resource allocation request | |
| US10362597B2 (en) | Periodic uplink grant alignment in a cellular network | |
| CN105451345B (en) | Uplink authorization information sending method and base station | |
| CN108886716A (en) | A kind of data transmission method and device | |
| EP2724584A1 (en) | Network node and method related to buffer estimation | |
| US20170013608A1 (en) | Pucch resource allocation method, network side device and communications system | |
| US10477515B2 (en) | Selective usage of scheduled and unscheduled transmissions to a cellular network | |
| WO2016198110A1 (en) | Selective reallocation of previously allocated radio resources | |
| US9756654B2 (en) | Timer-based scheme for user equipment queue state estimation | |
| CN109121219B (en) | Method and device for sending scheduling request, storage medium and terminal | |
| EP3326314B1 (en) | Method for hybrid automatic repeat request process, network device and terminal device | |
| CN109561510B (en) | Method and device for sending scheduling request and user equipment | |
| US11252746B2 (en) | Method for data transmission, terminal device and network device | |
| CN110933699B (en) | Packet forwarding method and device | |
| CN110087322B (en) | Scheduling request method, terminal, resource allocation method and base station | |
| KR20220038504A (en) | Information transmission methods and electronic devices | |
| CN113677031A (en) | Terminal uplink resource scheduling method, device, computing equipment and computer storage medium | |
| CN113840304A (en) | Service processing method, parameter configuration method, device, terminal and network side equipment | |
| JP2020043449A (en) | Base station device performing radio resource allocation for terminal communicating by using a half duplex system, control method and program thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |