[0025] Since the TCP protocol controls the source rate of the upper-layer services carried by it, while the non-TCP protocol does not control the source rate of the upper-layer services carried by it, the present invention divides the received data packets into TCP and non-TCP based on this feature. Two types, and adaptive bandwidth adjustment according to their own characteristics. Refer to the attached below figure 2 , A detailed description of the adaptive bandwidth adjustment method for packet data services proposed by the present invention includes the following steps:
[0026] Step 201: When the RNC (Radio Network Controller) receives the downlink PS packet data service establishment request, it allocates an appropriate initial bandwidth according to the current load of the cell and other resource conditions, and establishes the corresponding PDCP (Packet Data Convergence Protocol) and RLC (Wireless Link Control) and other examples. This step is a general step in the steps of establishing a PS packet data service, and is the same as the prior art, so this step will not be described in detail.
[0027] Step 202: After the packet data service is established, the PDCP entity performs statistics on the protocol types of the downlink service data, and PDCP performs statistics according to a given statistical period to determine the current dominant protocol type. The dominant protocol type means the protocol type occupying a major proportion.
[0028] We know that each IP data packet carries an 8-bit protocol field, indicating the type of upper layer protocol carried by the data packet. PDCP counts the protocols carried by the IP data packets arriving at the PDCP layer. In this example, all possible protocol types are classified as TCP and non-TCP, and the percentages of TCP and non-TCP packets are counted. The sum of the two is 100%.
[0029] PDCP judges the current dominant protocol type as TCP according to the given statistical period and the specific standards that the protocol dominates (for example, if the proportion of TCP data packets exceeds the proportion of non-TCP data packets and reaches a predetermined value, the current dominant protocol type is considered to be TCP). Whether the dominant protocol type changes, when the dominant protocol type changes, promptly notify the RRM (radio resource management module) in the RRC (radio resource control) entity, which is a well-known functional module in the RRC layer, which is mainly responsible for such as channel bandwidth and power And other wireless resource allocation and management functions).
[0030] The RRM module in the RRC entity updates the current dominant protocol type recorded in the RRC entity in real time according to the dominant protocol type reported by the PDCP.
[0031] At the same time as step 202, the PDCP entity also performs throughput statistics on the downlink service data, and the RLC entity also performs statistics on the downlink service volume. And adopt the event mode PDCP/RLC entity to report the downlink throughput/traffic volume change of the service. The event mode may be: when the downlink throughput/traffic volume counted by the PDCP/RLC entity exceeds a given upper threshold or is lower than a given lower threshold, and the lag time is met, a measurement report is reported to the RRM module. Wherein, the upper threshold, lower threshold and hysteresis time parameters of the throughput/traffic volume are pre-configured. It is not difficult to understand that the event mode may also be: a mode of reporting regularly or a mode of reporting exceeding a threshold, etc.
[0032] Step 203: The RRM module in the RRC entity selects and receives different downlink measurement reports to trigger bandwidth adjustment according to different current dominant protocol types, as follows:
[0033]When the current dominant protocol is TCP, the bandwidth adjustment is triggered when the RRM module receives the downlink traffic report reported by the RLC. For TCP services, the change in RLC service volume reflects the amount of service data to be sent (for TCP services, active rate control, so TCP will try to use the maximum bandwidth provided by its lower layer, so RLC service volume changes can reflect TCP traffic data changes), so when the traffic volume exceeds the upper threshold, indicating that the traffic volume is large, a larger bandwidth is allocated and the service is reconfigured to a bandwidth as high as possible; otherwise, the traffic volume is lower than the lower limit. In the case of a threshold, a smaller bandwidth is reconfigured for the business.
[0034] When the current dominant protocol is non-TCP, and when the RRM module receives the downlink throughput report reported by PDCP, it triggers bandwidth adjustment, and adjusts the bandwidth for downlink services according to the downlink throughput reported by PDCP. In downlink transmission, for non-TCP services, since there is no rate control, the downlink throughput of the PDCP layer is relatively close to the service source rate. (Because PDCP is adjacent to the non-access layer, the throughput measurement can best reflect the upper layer data The configured bandwidth of the packet source rate can completely refer to the current downlink throughput. For throughput exceeding the upper threshold or lower than the lower threshold, considering that there will be some error retransmissions in air interface transmission, in order to ensure that the current throughput requirements are met, when the service is reconfigured, a ratio is measured. The actual throughput is slightly larger on the bandwidth.
[0035] After the above steps, a service bandwidth adjustment is completed. Among them, different bandwidth configurations occupied by current packet data services have different upper threshold, lower threshold, and lag time parameters. Therefore, after adjusting the bandwidth of one service, reconfigure the threshold and lag time used for PDCP and RLC measurement to the parameters corresponding to the current packet data service, and then return to step 202 to enter the next service bandwidth adjustment.
[0036] The present invention tracks the protocol type of data in real time, and adopts bandwidth adjustment strategies based on RLC downlink traffic volume and PDCP downlink throughput for different protocol types, so as to accurately track the change of protocol type and data volume used in packet services in real time The changing demands of bandwidth greatly strengthen the pertinence and rationality of bandwidth adjustment. Under the premise of ensuring service quality, it effectively saves the system's downlink bandwidth resources.
[0037] The above descriptions are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the present invention. Within the scope of protection.
