Resource allocation method, method for reporting buffer status report (BSR) by user side and network-side equipment

Abstract

The invention discloses a resource allocation method and network-side equipment. The method comprises the following steps that: a network side judges whether the size of a data packet transmitted by a user side during a talkspurt period is in a stable status when determining that voiceover internet protocol (VoIP) service transmission enters the talkspurt period; the network side determines a lower limit value of the data packet transmitted by the user side during the talkspurt period according to the size of the data packet in the stable status after the size of the data packet is confirmed to be in the stable status; and the network side adopts a semi-continuous resource scheduling mode to allocate a semi-continuous resource to the user side when the following VoIP service is in the talkspurt period, wherein the semi-continuous resource is not greater than the determined lower limit value. By controlling the size of the semi-continuous resource, the report of unnecessary data volume in a buffer area is avoided, so the report expenditures on a buffer status report (BSR) and a scheduling request (SR) are effectively reduced, and the communication resources are saved.

Description

technical field [0001] The present invention relates to the field of communication technology, in particular to a resource allocation method, a method for reporting a BSR at a user side, a user side device, and a network side device. Background technique [0002] In a mobile communication system, if the network side wants to schedule and allocate resources for the uplink data packets of the user terminal UE, it needs to know the amount of data to be sent in the buffer area of ​​the UE on the uplink logical channel. Buffer Status Report (BSR) report. When the UE has no uplink shared resources to send BSR, it needs to apply for uplink shared resources by sending an SR (Scheduling Request) to the network side, and the network side allocates uplink shared resources for the UE for BSR transmission. The BSR reported in the above manner is called a Regular BSR, that is, only the Regular BSR can trigger SR reporting. [0003] There are three trigger conditions for regular BSR repo...

AI Technical Summary

Problems solved by technology

[0015] 1) Unnecessary BSR reporting leads to occupation of a large amount of PUSCH (Physical Uplink Shared Channel, physical uplink shared channel) resources, and unnecessary SR reporting leads to occupation of a large amount of uplink control channel PUCCH (Physical Uplink Control Channel, physical uplink control channel) resource

It is easy to cause PUCCH and PUSCH resources in the system to be limited

[0016] 2) Since BSR is scheduled and resource allocated through uplink dynamic scheduling, BSR reporting triggers SR reporting, and the network side needs to use PDCCH (Physical Downlink Control Channel, physical downlink control channel) to send user The side sends a scheduling signaling, so unnecessary BSR reporting will waste a lot of PDCCH resources, resulting in limited PDCCH resources

[0017] 3) Frequent reporting of BSR will lead to unnecessary SR reporting, which is not conducive to terminal power saving, and will also increase the interference of PUCCH

[0018] The existing resource scheduling method leads to resource limitations in the above aspects, which limits the number of users that can be accommodated in the communication system

Under the same user scale, it will reduce the service quality of the business in the network

Images