CN101491136B - Uplink Maximum Bit Rate Control - Google Patents

Abstract

An improved uplink maximum bit rate (MBR) control in a wireless packet communication network is disclosed. According to the present invention, a user equipment (UE) in the network evaluates each data packet added to the transmission buffer according to the MBR level, and classifies each estimated data packet as a conforming data packet or a non-compliant data packet. Among them, a packet is classified as non-compliant if it will be dropped or delayed when evaluated. The UE also creates a buffer status report (BSR), which only includes the data volume information of the data packets classified as compliant in the transmission buffer, and sends this BSR to a node performing media access control (MAC) in the network.

Description

Uplink Maximum Bit Rate Control

technical field

The invention relates to uplink maximum bit rate control in a wireless packet communication network.

Background technique

Specifically, the present invention relates to a maximum bit rate (MBR) and an integrated maximum bit rate (AMBR) of a radio bearer in a wireless communication system, and the wireless communication system may be Long Term Evolution (LTE) of 3GPP or Universal Mobile Telecommunications System (UMTS), etc. .

In current quality of service (QoS) packet-based networks, data (and signaling) at different QoS levels may have different data loss rates, different delay characteristics and/or different throughputs.

Radio bearer is a service provided by the second layer of the Open System Interconnection (OSI) model in Wideband Code Division Multiple Access (WCDMA) 3G technology, and is used for user equipment (UE) and UMTS terrestrial radio access network (UTRAN) to transfer user data between.

Data of the same QoS level can be transmitted by the same radio bearer. Data of different QoS levels are transmitted by different radio bearers.

The terms Radio Access Bearer (RAB) and System Architecture Evolution (SAE) bearer are used in UMTS to identify services provided by the Access Stratum (AS) to the Non-Access Stratum (NAS) Transmit user data between networks (CN). Since the present invention relates to the radio interface, only the transmission on the radio bearer will be further described below.

In early 3GPP wireless networks, the enforcement of throughput limitation and MBR limitation is done in CN. The reasons for these restrictions can be business or subscription reasons. For example, only certain MBRs are allowed for a certain subscription.

For high-throughput radio interfaces, such as those in LTE, the achievable radio throughput may be much higher than the actually allowed MBR. Therefore, in order to save wireless resources, it is more appropriate to implement uplink (UpLink) MBR restriction in UE, which is also the current task of LTE. Different radio bearers may have different MBRs (or no MBR), and multiple groups of radio bearers may also have an AMBR restriction. In the following description, unless otherwise specified, MBR and AMBR are both represented by MBR.

Further, in this description, it is assumed that the UE cannot freely transmit data on the UL at any time, but must abide by the Medium Access Control (MAC) protocol to use uplink transmission resources.

3GPP's WCDMA Enhanced Uplink (E-DCH) has a MAC protocol, and the MAC protocol works as follows:

1. If the UE has (or more) data to send, the UE needs to send scheduling information to the network to indicate the amount of stored data and the highest transmission capacity of the UE in the current wireless situation. The scheduling information can be sent separately, or carried in the MAC protocol header of a certain data packet during the data sending process.

2. The network allocates radio resources for the UE, and notifies the UE of the resource allocation permission.

3. The UE can use the allocated radio resources to send data.

The UL of the first layer of WCDMA basically allows the UE to send scheduling information in time at any time, and the only side effect is that such sending increases interference.

For 3GPP LTE, it is assumed that steps 1, 2 and 3 above also need to be performed. However, for LTE, the situation is a bit different. For LTE, spontaneous transmissions are not possible except on random access channels. On the LTE UL, the UE either has to do a random access request to obtain enough UL transmission resources to be able to send scheduling information, or it has to have some kind of allocated periodic UL resources to indicate that it has data to send. Therefore, for LTE, there is likely to be an additional step before step 1 above.

Further, there are other differences between LTE and WCDMA:

The scheduling information in LTE may be more detailed, for example, it may include information about how much data is buffered in each priority level (that is, each radio bearer), that is, information about how much data is buffered in each radio bearer. This information is needed for reasonable scheduling if congestion occurs and there are different UEs transmitting on different priority levels. This part of the LTE scheduling information is called a Buffer Status Report (BSR, Buffer Status Report).

The nature of resource allocation grants is also different in WCDMA and LTE. In WCDMA, resource allocation grants relate to allowed transmission capabilities. In LTE, however, a group of subcarrier frequencies and time slots need to be specified in the resource allocation grant.

However, it should be noted that for WCDMA and LTE, resource allocation grants are per UE, and the above three basic steps illustrate how data is sent in LTE UL.

In order to control the transmission rate, it is often necessary to notify the data source (ie, the sender) to reduce its transmission rate. The implementation principle of this process varies with the protocol. Typically, rate control is an end-to-end function, usually part of an end-to-end protocol, while the reason for reducing the rate is reflected in the lower layer protocol, for example, in the network layer transmission or link layer transmission In the protocol, the rate control is very complicated.

Some protocol stacks pass explicit congestion notifications from lower layers to higher layers, however, in the context of Transmission Control Protocol/Internet Protocol (TCP/IP), for example, TCP transport protocol and User Datagram Protocol (UDP) applications often only Data transfer delays and data loss react. The TCP sender maintains timer and acknowledgment (ACK) status for transmitted protocol data units. When TCP acknowledges the loss of a PDU, TCP reduces its window size (i.e., the allowed burst size) to half, effectively reducing its rate and cache requirements for intermediate nodes. For UDP applications, there is no general requirement for rate control, but many applications, especially high-rate applications such as video, or applications tailored for wireless audio such as Adaptive Multi-Rate (AMR), can control rate control.

In general, for UDP applications, the receiver measures delays and dropped packets, and periodically sends transmission reports back to the sender to allow the sender to change its rate. It is also possible for the receiver to directly request a certain rate. UDP applications that have rate control and reduce the rate based on data loss and possibly delay increase are called TCP friendly applications.

As mentioned above, a specific service or subscription involves a specific allowable UL MBR, which should be implemented in the UE by limiting the transmission rate by packet discarding or delay.

The problem involved in limiting MBR is how to know when to MBR limit the transmitted data, for example when packets are dropped or delayed. According to the early 3GPP principle of deciding what to send and how much to send, such a decision is made at the time of sending, that is, after the UE receives the resource allocation permission from the network. This principle is also probably the most accurate one, since MBR can be performed based on the actual transmitted data.

It will be very inaccurate if MBR is performed in an internal stack transfer. The burst size inside the stack is mainly application dependent, and this burst size can be quite different from the wireless transmission burst size to be sent. Usually, the UE does not know the congestion status of the radio interface, and the UE usually cannot predict the congestion status. Therefore, if the decision whether to drop a packet is made at another time than when the data is being sent, the decision may be premature because the data may be delayed due to congestion on the air interface.

FIG. 1 is a flowchart of an existing MBR restriction method executed in a UE. In the first step of the method, a data packet arrives at the UE. These packets are added to the transmit buffer. In the second step of the method, the UE sends a buffer status report (BSR) to a network node that can allocate transmission resources. The BSR contains data volume information for all data packets in the transmission buffer. The network node allocates transmission resources corresponding to the request to the UE, and notifies the UE of the allocation in a response, so as to allow the UE to use these resources. In a third step, the UE receives a transmission resource grant for all data packets in the buffer. If necessary, in the fourth step, the UE performs MBR limitation by dropping packets until the bit rate is less than the MBR limit.

In the prior art, there is a problem of "permission loss" in the implementation scheme of MBR restriction. This problem arises when the UE reports in a Buffer Status Report that it has a certain number of bytes stored in its transmit buffer, and usually receives a response from the network that allows the UE to send the specified number of bytes resource allocation grant of bytes; then, if the UE enforces MBR restrictions when sending, the UE will most likely drop packets to avoid the rate exceeding the MBR limit; therefore, in this case, the UE will drop what it has requested and has Data packets that are granted transmission resources, as a result the entire resource allocation grant will not be utilized, ie wireless transmission resources are wasted.

Contents of the invention

An embodiment of the present invention provides a method for UL MBR control to solve the above problems.

The embodiment of the present invention provides a method for UL MBR control. Compared with the UL MBR execution method in the prior art, the method reduces the waste of transmission resources.

On the one hand, an embodiment of the present invention provides a method, in which a UE in a network is provided, including:

Evaluate each packet added to the transmission buffer according to the MBR level, and classify each evaluated packet as a compliant packet or a non-compliant packet, wherein if a packet is to be dropped or delayed during evaluation , the data packet is classified as a non-compliant data packet;

Create a buffer status report BSR, which only includes information on the amount of data in the transmission buffer that matches the data packet;

This BSR is sent to the nodes in the network that implement the medium access control MAC.

According to one aspect of the present invention, a user equipment is provided, and the user equipment includes:

Evaluate each packet added to the transmission buffer according to the MBR level, and divide each packet into units of conforming packets or non-compliant packets, wherein, if a packet is to be dropped or delayed while being evaluated, The data packet is classified as a non-compliant data packet;

means for creating a buffer status report (BSR) that only includes information on the amount of data in the transmission buffer that corresponds to the packet; and

This BSR is sent to the unit of the node in the network that performs the medium access control MAC.

The present invention also provides a communication system for providing MBR control of uplink maximum bit rate. The communication system includes at least one UE and at least one node;

The UE includes:

Evaluate each data packet added to the transmission buffer according to the MBR level, and divide each evaluated data packet into a unit of a conforming data packet or a non-compliant data packet,

A unit for creating a buffer status report BSR, and a unit for sending the BSR; the BSR only includes the data volume information of the data packets classified as conforming in the transmission buffer;

The node is configured to receive the BSR and respond to the UE to indicate which resources are allocated to the UE.

In the embodiment of the present invention, the cache status report only includes the data volume information classified as conforming data packets. Therefore, data size information for packets in the buffer that will not be sent will not be reported. The advantage of this embodiment is that "grant loss" can be avoided, since transmission resources are only requested for data packets that are really to be sent.

In addition, another advantage of the UL MBR control of the present invention is that discarding or delaying can be performed at the time of data transmission, thereby realizing accurate MBR limitation.

According to one embodiment of the present invention, data packets added to the transmission buffer are evaluated and it is determined whether the data packets are to be discarded. If there is a limit exceeding the MBR, these data packets will be classified as non-compliant data packets, and if they do not exceed the limit of the MBR, then these data packets will be classified as compliant data packets.

According to an embodiment of the present invention, the non-conforming data packets are classified, and in some cases, may be re-divided into conforming data packets.

Marking packets as compliant and non-compliant has the advantage that there are enough transmission resources for the UE to request and the allowed transmission resources can be used more efficiently.

When enough transmission resources are allowed, the packet loss mechanism decides which data packets to discard, which is based on the transmission resource permission received by the node performing media access control MAC in the network, and whether the data packets in the cache meet or do not meet the requirements. markup.

According to one embodiment of the present invention, the packet loss mechanism takes into account the impact of dropping or delaying a data packet on an application in which the data packet is used to transmit data. For example, if the application is a rate-adaptive application, packets in the buffer header are dropped or delayed in order to inform the application to reduce its rate as early as possible. The advantage of this embodiment is that the rate adaptation process of the application is relatively fast.

According to one embodiment of the present invention, evaluating, and dropping or delaying a data packet takes into account the priority assigned to the data packet. Therefore, the UL MBR control performed according to the embodiment of the present invention is also based on priority. So, lower priority packets are dropped before higher priority packets if possible. Therefore, the probability that important data packets, such as data packets of certain QoS levels or data packets of some important applications, are dropped or delayed is relatively low.

Hereinafter, specific embodiments and advantages of the UL MBR control of the present invention will be described with reference to the drawings of some preferred embodiments.

Description of drawings

Fig. 1 shows a flow chart of performing an existing MBR restriction method on a UE.

Fig. 2 shows a flow chart of the MBR restriction method implemented on the UE in the embodiment of the present invention.

Detailed ways

According to an embodiment of the present invention, in the transmission buffer of the UE, only data packets containing data that will not be discarded or delayed, that is, data packets containing conforming data, will be reported by the buffer status report. Grant loss can thus be avoided, since transmission resources are only requested for data packets that are actually to be sent.

According to the present invention, the principle of transmission resource request can be combined with accurate MBR restriction (ie discarding or delaying data), because the discarding or delaying of data can be done at the moment of transmission. Therefore, accurate MBR limitation can be achieved using the present invention.

Further, the principles of the present invention can also be combined with other functions required for data discarding, such as performing Random Early Discard (RED, Random Early Discard) to achieve moderate rate control, and QoS-based intelligent Random Early Discard (RED) to Know which traffic is rate-adaptive/non-rate-adaptive.

Also, in the case of congestion and long scheduling delays, the amount of data allowed to be transmitted in the cache status report may be underestimated (due to the delay between the cache status report and the resource allocation grant), which may require additional scheduling opportunities to transmit A certain amount of data.

According to an embodiment of the present invention, this problem can be solved by extending the information in the buffer status report, that is, including a higher-level indication in it, to indicate that more data is available for a certain radio bearer (RB), the data Data that may or may not conform to the MBR restriction depends on the time delay when the resource allocation permission is received.

According to the invention, data packets added to the transmission buffer are evaluated to determine whether the data packets are to be discarded. Packets that will be dropped are classified as non-compliant packets, and packets that will not be dropped are classified as compliant packets.

This evaluation basically checks whether adding packets to the transmit buffer would cause the UE to exceed its MBR limit. A packet is classified as non-compliant if there is a risk of exceeding the MBR limit, and a compliant packet if there is no risk of exceeding the MBR limit.

Generally speaking, if a data packet arrives at a rate too fast to exceed the rate corresponding to the output MBR, the data packet will be considered non-compliant. There are various ways to detect excessive arrival rates, such as token bucket model detection, or any other suitable mechanism familiar to rate detection technicians. The token bucket model is described in detail below.

According to an embodiment of the present invention, data packets classified as non-compliant may be reclassified as compliant in some cases. These situations include radio congestion issues, or situations where packets are dropped for reasons other than MBR constraints, or learning of resource allocation grants from network nodes is delayed, etc. In these cases, it is beneficial to reclassify packets from non-compliant to compliant, because otherwise the UE may drop too many packets.

Thus, according to the invention, after the data packets added to the transmission buffer have been evaluated, each data packet is marked as a conforming data packet or as a non-compliant data packet. Transmission resources are then requested for conforming packets. After that, it is up to the packet discarding mechanism to decide which data packets are finally discarded. The decision is based on the transmission resource grant received by the node performing Media Access Control (MAC) in the network, and the compliance or non-compliance flag of the data packets in the cache.

Fig. 2 shows a flowchart of a method for implementing MBR restriction in a UE in an embodiment of the present invention. In the first step of the method, a data packet arrives at the UE. In the second step, these arriving packets are evaluated to decide whether each packet will be sent or not. If the packet will be sent, the packet is classified as compliant, and if it will not be sent, it is classified as non-compliant. These packets are then added to the transmit buffer. In the third step of the method, the UE sends a buffer status report (BSR) to a network node capable of allocating transmission resources. The BSR only includes the data volume information of the data packets classified as compliant in the transmission buffer. Then, the network node allocates transmission resources to the UE according to the UE's request, and notifies the UE of the allocation in a response, allowing the UE to use these resources. In the fourth step, the UE receives all transmission resource grants matching the data packets in the cache. If necessary, in the fifth step, the UE implements MBR limitation through corresponding procedures, such as discarding data packets or delaying data packets or other actions until the bit rate is less than the MBR limitation. In this embodiment, the data packets to be discarded or delayed are selected according to the received permission and the evaluation of the data packets, wherein the evaluation of the data packets is only whether the data packets comply or not comply.

Therefore, the advantage of the MBR limiting method according to the present invention is that the waste of transmission resources is minimized since transmission resources are only requested for data packets that are actually to be sent.

Following the transmission of resource requests and grants, the discarding or delaying of data (data packets) can be accomplished in a number of ways according to the invention. Hereinafter, several examples of discarding data will be described in detail. Those skilled in the art know that there are many methods for discarding data, and these methods can be combined with the transmission resource request and allocation of the present invention. If the data is not discarded but delayed, a corresponding mechanism can also be used to discard the data, the difference is that the data is delayed but not deleted.

When congestion occurs, IP network devices (routers) drop packets to trigger the end-to-end rate control mechanism of TCP or TCP-friendly applications. And when severe congestion occurs, it can be considered that the data buffer is full and all/many arriving packets must be discarded. In order to allow proper rate reduction to be performed on various data streams, a Random Early Discard (RED) mechanism is typically used.

The idea of the RED mechanism is to pseudo-randomly select and discard a small number of data packets before the congestion becomes serious. These dropped packets serve as a signal to the rate adaptive application whose packets are dropped to reduce its transmission. So, packet drops are also a signal to the application that its bitrate is too high. This type of signaling is useful for rate adaptation applications.

According to an embodiment of the present invention, the UE is notified that the application is a rate adaptive application through signaling configuring the radio bearer of the application, or signaling from an internal data packet filter.

The RED mechanism provides a smooth rate reduction process, reducing the risk of congestion. However, since packets may need to be resent, data retransmissions may cause applications to increase rather than decrease transmission rates if packets are dropped indiscriminately.

According to one embodiment of the present invention, when RED is applied, data packets are chosen to be discarded at the head of the queue rather than at the tail of the queue. The purpose is to enable the end-to-end packet layer to detect dropped packets as early as possible. Therefore, it is possible for rate adaptive applications to perform faster rate adjustments by dropping packets at the head of the transmit buffer.

The rate control described above is described in the context of networking. Inside the protocol stack, rate control is also required, because the higher-level protocols may generate more data than the lower-level protocols can transmit. Inside the protocol stack, this problem can be solved by an explicit flow control mechanism between the protocol layers, ie, there is a possibility of rate control in the transmission application programming interface (API) between the protocol stack and the application. This is generally the case for TCP, but not for UDP.

In addition, other rate control mechanisms may also be implemented in the present invention. The token bucket model is such a mechanism, which can be used for rate control and traffic shaping.

The token bucket model can be used for various purposes. When used for traffic shaping, the token bucket mechanism is a simple and effective transmission rule. A token (usually) corresponds to a certain amount of data. Whenever the certain amount of data is sent, a corresponding token in the token bucket will be consumed. If multiple copies of the certain amount of data are sent at the same time, multiple tokens are consumed. If there are not enough tokens in the token bucket, the corresponding data packet is not allowed to be sent. The maximum amount of data that can be sent at the same time, that is, the maximum burst size, is the amount of data corresponding to a whole bucket of tokens. The token bucket is continuously filled (refilled) with tokens at a steady token rate, where the token rate is the MBR, and the token rate is consistent with the maximum allowed average rate.

According to an embodiment of the present invention, when the token bucket model is used for traffic shaping, the token bucket model judges which are compliant data packets and which are non-compliant data packets, and usually non-compliant data packets will be discarded later or delayed (put into cache). This enables controlled discarding without permission loss. Or, for other purposes, non-compliant data packets can be measured only, or used for possible subsequent QoS identification.

In the case of UDP applications, or in the case where the UE is connected to an application device such as a laptop through a cable, that is, in the case where the wireless protocol stack and the application protocol TCP/IP stack are separated, in order to perform UL MBR, here We assume that the flow control of the internal protocol stack cannot be relied on for rate control. Instead, it is assumed that dropping and delaying packets is the only way to do rate control, except perhaps in some specific applications.

According to an embodiment of the present invention, in order to execute MBR, the token bucket model is used to judge whether the data packet conforms to or does not conform to. To implement RED for proper rate control, the token bucket model has two token buckets, or one token bucket with an intermediate threshold. Therefore, the token bucket model includes:

1. No. 1 token bucket, or No. 1 threshold: randomly discarded.

This is the token bucket or threshold that triggers RED. Rate shaping is implemented using a random drop threshold when a small number of packets are randomly selected and dropped. The main purpose of this is to notify the application to adjust its uplink transmission bit rate by discarding as few data packets as possible, thereby reducing the bit rate.

2. No. 2 token bucket, or No. 2 threshold: discard in batches (empty bucket).

During bulk drop, the token bucket is emptied and all non-compliant packets are dropped.

It can be seen that the token bucket model is a relatively easy way to implement MBR control, which is the advantage of the token bucket model. In the present invention, the token bucket model for discarding data packets can also be implemented in a simple manner.

According to an embodiment of the present invention, the UE is notified of the parameters required for configuring the token bucket model through signaling, wherein the signaling is signaling for configuring a radio bearer used to transmit information for an application.

According to an embodiment of the present invention, the rate control is performed so that the probability of discarding a data packet of a rate-adaptive flow is greater than that of a non-rate-adaptive flow. This causes packets with rate-adapting application data to be dropped more often than packets with non-rate-adapting application data, which is beneficial because rate-adapting applications will Adjust its bitrate. A non-rate-adaptive application, even if it is aware that its packets are being dropped due to MBR limits, does not alleviate this problem.

As mentioned above, a group of radio bearers (RBs) may also have a common AMBR. Different RBs sharing one AMBR may also have different packet loss probabilities, that is, data packets of different RBs have different priorities, because the bit rates of different RBs may be different.

According to an embodiment of the present invention, these different packet loss probabilities may also be related to rate adaptation possibilities of applications carrying data by RBs.

In addition, data packets of different QoS levels will also be assigned different priorities.

The relationship between the rate adaptation possibility of the application and the above-mentioned packet loss probability is favorable, because it makes it possible to drop packets from the flows that are really capable of reacting to packet loss and not from other flows data pack. In this way, the amount of data loss caused by rate control can be minimized.

In one embodiment according to the invention, different priorities assigned to different data packets are also used to evaluate the data packets. Priority is also a deciding parameter here when evaluating packets for compliance. For example, if a high-priority data packet causes a risk of exceeding the MBR, the high-priority data packet is not classified as non-compliant, but the low-priority data packet is classified as non-compliant. Specifically, if the low-priority data packet is not included in the previously sent BSR, it is advantageous to classify the low-priority data packet as a non-compliant data packet; otherwise, the license will be lost.

According to an embodiment of the present invention, the data volume information of the non-compliant data packets should not be included in the cache status report. Then, the discarding of the data packet can be carried out in various ways, for example, it can be a way with the following characteristics:

1. Non-compliant packets may be discarded according to RED. In addition, in order to notify the adaptive application as early as possible that its data packets are being discarded, it may also choose to discard data packets at other positions in the queue, for example, data packets at the head of the queue. Packets elsewhere in the queue will be discarded only if their size is equal to or smaller than the sum of the sizes of all packets deemed non-compliant. Conversely, if the size of the packet chosen to be dropped exceeds the sum of the sizes of all non-compliant packets, this will result in excessive packet loss. If other data packets are selected instead of those considered non-compliant data packets during data packet evaluation, some data packets may need to be re-evaluated as non-compliant data packets.

2. When deciding to drop packets, if the discarded packets are not non-compliant packets that cause the packet loss decision, or only a subset of these packets are discarded, then the remaining non-compliant packets that cause the packet loss decision Packets are reclassified as conforming packets. This compensates for the packet loss rate of the token bucket without consuming tokens.

3. Re-evaluate the packet loss decision at least once each time the UE adjusts the transmission resource.

Therefore, according to an embodiment of the present invention, both non-compliant and compliant data packets can be selectively discarded or delayed. The selection is based on transmission resource availability, an assessment of whether the packet complies, and the impact of dropping or delaying the packet on the application utilizing the packet to transmit data.

To avoid further packet loss, a matching packet is only selected if there is a corresponding number of non-compliant packets in the transmit buffer. Also, if compliant packets are selected, non-compliant packets corresponding to the number of selected compliant packets are reclassified as compliant packets. This has the advantage that the resources requested by the UE are sufficient to carry packets that are not dropped or delayed, since the network node is likely to grant transmission resources for all compliant packets. Therefore, transmission resources are not wasted.

According to an embodiment of the present invention, if there is at least one non-compliant data packet in the transmission buffer, the BSR further includes information for indicating that there is at least one non-compliant data packet in the transmission buffer, such as including an identifier. However, the flag only indicates that there is at least one non-compliant data packet in the cache, but does not indicate the size of these data packets or request transmission resources for these data packets.

The above-mentioned different steps of the method of the present invention may be combined or performed in any suitable order. The condition is that when a step is combined with another of the method of the invention, the requirements such as available information required by the step must be fulfilled.

The method of the present invention can be implemented by a computer program comprising codes which, when run on a computer, cause the computer to carry out the steps of the method. This computer program is embodied in a computer readable medium of a computer program product. The computer readable medium can basically consist of any memory, such as read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), flash memory, electronically erasable programmable Read memory (EEPROM), or hard drive.

The invention also proposes a UE implementing the method of the invention. Therefore, the UE of the present invention is used to evaluate each data packet added to the transmission buffer according to the MBR level, and classify each data packet as conforming or not conforming. During evaluation, a packet is classified as non-compliant if it would be dropped or delayed when evaluated. The UE is also used to create a buffer status report (BSR), which only includes the data volume information of the packets classified as compliant in the transmission buffer, and sends this BSR to the node performing medium access control (MAC).

By configuring appropriate units, UE can be used to perform any step of the method of the present invention. Of course, it is required that the UE actually participates in this step.

Another embodiment of the present invention provides a communication system for providing uplink Maximum Bit Rate (MBR) control. The system includes at least one UE and at least one node. The at least one UE and at least one node can perform the above-mentioned MBR control. The at least one UE is configured to evaluate whether each data packet added to the transmission buffer will be sent at the MBR level, and send a buffer status report (BSR) to a node, wherein the BSR includes only the data packets to be transmitted in the transmission buffer The data volume information of the packet. The at least one node is configured to receive the BSR and respond to the UE to indicate which resources are allocated to the UE. The UE is configured to drop or delay at least one data packet based on resources allocated thereto and an evaluation of the data packets in a transmission buffer. Therefore, the transmission resources of the system are efficiently utilized.

It can be understood that, compared with the foregoing embodiments, those skilled in the art can modify the ULMBR control of the present invention.

Claims (46)

1. an uplink maximum bit rate MBR control method in a wireless packet communication network, characterized in that, the user equipment UE in the network performs the following steps: Evaluate each data packet added to the transmission buffer according to the MBR level, and classify each evaluated data packet as a compliant data packet or a non-compliant data packet, Create a buffer status report BSR, which only includes the data volume information of the data packets classified as compliant in the transmission buffer, Transmitting said BSR to a node in said network that implements Medium Access Control MAC. 2. The method according to claim 1, wherein the UE further performs the following steps: receiving an uplink resource allocation grant from the node, wherein the resource is used for uplink resource transmission, selecting at least one packet to be discarded based on said resource allocation grant, and an evaluation of packets in said transmit buffer, and Discarding the at least one selected data packet. 3. The method according to claim 1, wherein the UE further performs the following steps: receiving an uplink resource allocation grant from the node, wherein the resource is used for uplink resource transmission, selecting at least one packet to be delayed based on said resource allocation grant and an evaluation of packets in said transmit buffer, and Delaying the at least one selected data packet. 4. The method according to claim 2 or 3, characterized in that said selecting at least one data packet to be discarded or to be delayed is accomplished by selecting at least one of the data packets classified as non-compliant . 5. The method according to claim 4, wherein said selecting at least one data packet to be discarded or to be delayed is based on discarding or delaying said at least one data packet pair using at least one data packet to transmit data Applications are selected based on the expected impact they will have. the 6. The method according to claim 5, characterized in that all data packets classified as non-compliant are selected. 7. The method of claim 5, wherein the application is a rate adaptive application, and the expected impact is an impact of rate adaptation. 8. The method according to claim 7, wherein the information indicating that the application is a rate adaptive application is obtained by the UE from the signaling used to configure the radio bearer of the application. 9. The method according to claim 7, wherein the information indicating that the application is a rate adaptive application is obtained by the UE from a data packet filter inside the UE itself. 10. The method of claim 7, wherein at least one packet at the head of the transport buffer is selected to notify the application of rate adjustment at an early stage. 11. The method according to claim 2 or 3, wherein the selecting at least one data packet to be discarded or to be delayed is realized by selecting at least one data packet classified as conforming. 12. The method according to claim 11, wherein said selecting at least one data packet to be discarded or to be delayed uses said at least one data packet to transmit data according to discarding or delaying said at least one data packet pair. The expected impact of the application is selected. 13. The method of claim 12, wherein the application is a rate adaptation application and the expected impact is a rate adaptation impact. 14. The method according to claim 13, wherein the information indicating that the application is a rate adaptive application is obtained by the UE from signaling for configuring radio bearers of the application. 15. The method according to claim 13, wherein the information indicating that the application is a rate adaptive application is obtained by the UE from a data packet filter inside the UE itself. 16. The method of claim 13, wherein at least one packet at the head of the transport buffer is selected to notify the application as early as possible that a rate adjustment should be made. 17. The method of claim 11, wherein said selecting at least one packet to be discarded or delayed further comprises: Only when the sum of the size of the selected at least one conforming data packet is less than or equal to the sum of the sizes of all the non-conforming data packets in the transmission buffer, the at least one conforming data packet is selected. 18. The method of claim 17, wherein at least one of the transmission buffers is classified as a non-compliant packet when its size corresponds to the size of the selected at least one compliant packet , which are reclassified into packets that conform to . 19. The method according to claim 1, wherein said evaluating the data packet according to the MBR level further comprises the following steps: assessing whether the addition of a packet in the transmit buffer would cause the UE to exceed its MBR limit, and If the addition of the data packet causes the UE to exceed the limit of the MBR, the data packet is classified as a non-compliant data packet; If the addition of the packet does not cause the UE to exceed the MBR limit, then the packet is classified as a compliant packet. 20. The method of claim 19, wherein a token bucket model is used to determine whether a data packet causes the limit of the MBR to be exceeded. 21. The method of claim 20, wherein the token bucket model includes two token buckets for determining whether a data packet causes the limit of the MBR to be exceeded: The first token bucket is used to determine whether at least one data packet added to the transmission buffer is classified as a non-compliant data packet, The second token bucket is used to judge whether to classify all data packets added to the transmission buffer as non-compliant data packets. 22. The method of claim 21, wherein the first token bucket triggers a random early discard RED. 23. The method of claim 21, wherein the second token bucket triggers batch discard. 24. The method according to claim 21, wherein the parameter for configuring the token bucket model is obtained by the UE from the signaling used to configure the radio bearer for the application, wherein the at least one Data packets transport data for the application. the 25. The method according to claim 1 or 19, characterized in that, when wireless congestion occurs, the data packets previously classified as non-compliant are re-classified as compliant. 26. The method according to claim 1 or 19, wherein when a data packet is discarded due to a reason other than MBR control, the data packet previously classified as non-compliant is re-classified as compliant. 27. The method according to claim 1 or 19, characterized in that, when the reception of the uplink resource allocation grant is delayed, the data packets previously classified as non-compliant are re-classified as compliant. 28. The method of claim 1, wherein the node responds to the BSR by allocating resources for the UE and notifying the UE which resources are allocated to the UE. 29. The method of claim 1, wherein said creating a BSR further comprises the steps of: Information indicating whether there is at least one non-compliant data packet in the transmission buffer is included in the BSR. 30. The method of claim 29, wherein said indicating is accomplished with a marker. 31. The method according to claim 1, wherein the MBR is related to one radio bearer, or is an integrated MBR (AMBR) related to at least two radio bearers. 32. The method according to claim 31, wherein when the MBR is an integrated MBR related to at least two radio bearers (AMBR), each of the at least two radio bearers has a specific priority level, the specific priority is assigned to the respective data packets. 33. The method of claim 32, wherein said assessing whether a data packet is compliant or non-compliant is accomplished by taking into account said priority. 34. The method of claim 33, wherein said assessing whether a data packet is compliant or non-compliant further comprises the steps of: assessing whether the addition of the first packet in said transmit buffer causes the UE to exceed the limits of the AMBR, If the addition of the first data packet exceeds the limit of the AMBR and the first data packet is assigned a high priority, divide at least one second data packet with a lower priority than the first data packet The data packet is not conforming, and the first data packet is classified as conforming. the 35. The method of claim 34, wherein the second data packet was not included in a previous BSR. 36. The method of claim 34, wherein the first data packet corresponds in size to the at least one second data packet. 37. The method according to claim 32, wherein the UE further performs the following steps: receiving a resource allocation grant from said node, selecting at least one packet to be discarded based on said resource allocation grant and said priority, and Discarding the at least one selected data packet. 38. The method of claim 37, wherein said selecting at least one packet to be discarded is performed by: If at least two packets are to be dropped, packets with lower priority are dropped before packets with higher priority. 39. The method according to claim 33, wherein the UE further performs the following steps: receiving a resource allocation grant from said node, selecting at least one packet to be delayed based on said resource allocation grant and said priority, and Delaying the at least one selected data packet. 40. The method of claim 39, wherein said selecting at least one packet to be delayed is performed by: If there are at least two packets to be delayed, the lower priority packet is delayed before the higher priority packet. 41. A user equipment, configured to perform uplink maximum bit rate MBR control in a wireless packet communication network, characterized in that the user equipment UE comprises: Evaluate each data packet added to the transmission buffer according to the MBR level, and divide each evaluated data packet into a unit of a conforming data packet or a non-compliant data packet, A unit that creates a cache status report BSR, and means for sending said BSR to a node in said network that implements a medium access control MAC; The BSR only includes the data volume information of the data packets classified as conforming in the transmission buffer. 42. The user equipment according to claim 41, wherein the UE further comprises: A unit that receives an uplink resource allocation permission from the node, selecting at least one unit of packets to be discarded based on said resource allocation grant and an evaluation of packets in said transmission buffer, and discarding the at least one selected unit of data packets; The resources are used for uplink resource transmission. 43. The user equipment according to claim 41, wherein the UE further comprises: A unit that receives an uplink resource allocation permission from the node, selecting at least one unit of data packets to be delayed based on said resource allocation grant and an evaluation of data packets in said transmission buffer, and delaying the at least one selected packet unit; The resources are used for uplink resource transmission. 44. The user equipment according to claim 41, characterized in that, each data packet added to the transmission buffer is evaluated according to the MBR level, and each evaluated data packet is divided into a conforming data packet or a non-compliant The units of the packet include: means for evaluating whether the addition of data packets in said transmission buffer causes the UE to exceed the limits of said MBR, and If the addition of the data packet causes the UE to exceed the limit of the MBR, dividing the data packet into non-compliant units, If the addition of the data packet does not cause the UE to exceed the limit of the MBR, dividing the data packet into conforming units. the 45. A communication system providing uplink maximum bit rate MBR control, characterized by comprising: user equipment UE and a node; The UE includes: Evaluate each data packet added to the transmission buffer according to the MBR level, and divide each evaluated data packet into a unit of a conforming data packet or a non-compliant data packet, A unit for creating a buffer status report BSR, and a unit for sending the BSR; the BSR only includes the data volume information of the data packets classified as conforming in the transmission buffer; The node is configured to receive the BSR and respond to the UE to indicate which resources are allocated to the UE. 46. The system of claim 45, wherein the UE further comprises: Means for dropping or delaying at least one data packet based on the resource allocated for said UE and the evaluation of the data packet in said transmission buffer. the

Images