WO2008064578A1

WO2008064578A1 - A method, system, access network and access terminal for releasing qos resource

Info

Publication number: WO2008064578A1
Application number: PCT/CN2007/070032
Authority: WO
Inventors: Sha Lv
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-11-30
Filing date: 2007-05-18
Publication date: 2008-06-05
Also published as: CN101193111B; CN101193111A

Abstract

A method for releasing the QoS resource includes: the access network releases the air interface connection with the access terminal corresponding to the QoS; B: the access network releases itself QoS storage space. Also, the present invention discloses a system, the access terminal and the access network for releasing the QoS resource. The present invention enables the access network to initiate the release of the air interface connection with the access terminal corresponding to the QoS and the release of itself QoS storage space, it avoids form the waste of the access network resource, and it may effectively utilize the access network resource.

Description

Method, system, access network and access terminal for releasing quality of service resources

The present invention relates to a communication technology of a wireless communication network, and in particular, to a method, system, access network, and access terminal for releasing quality of service resources. Background of the invention

With the rapid development of network multimedia technology and wireless networks, there are more and more types of services that access the Internet through mobile devices, such as Internet Protocol (IP), video conferencing, video on demand, and distance education. Multimedia real-time business, etc. These different services require different quality of service (QoS) requirements, and the requirements for QoS are constantly increasing. QoS is usually measured by parameters such as bandwidth, delay, delay jitter, and packet loss rate.

The wireless communication system includes an access terminal and an access network, wherein the access terminal is a mobile device that communicates with the access network through an air interface; and the access network provides wireless access of the access terminal. The wireless communication system also includes a gateway, which is an interface unit of the wireless communication system and the packet data network, for communication between the wireless communication system and the packet data network.

The following is a description of the establishment process of a service with QoS requirements by using the code division multiple access 2000 high speed packet data radio transmission technology version A (CDMA2000 lxEV-DO Rev. A, DOA) system as an example.

The DOA wireless communication system includes an access terminal (AT, Access Terminal), an access network (AN, Access Network), a packet control function unit (PCF, Packet Control Function), and a Packet Data Serving Node (PDSN). The PCF and PDSN can be integrated into one unit as a gateway for wireless communication systems and packet data networks. When the AT initiates the service transmission with the QoS requirement, the QoS configuration request message carrying the flow identifier is sent to the AN. After receiving the request, the AN allocates a storage space for the QoS in the AT and the AN, and the QoS state of the service enters the configuration state. If the service has multiple QoS requirements, the QoS configuration request message carries multiple flow identifiers corresponding to the QoS.

Then, the QoS parameters are configured between the AT and the AN, and the configured QoS parameters correspond to the flow identifiers. After the QoS parameter configuration is completed, the QoS parameters of the service are respectively saved in the storage space allocated by the AT and the AN for the QoS, and the QoS state of the service enters the ready state; at this time, the AN initiates carrying the flow identifier and QoS to the PCF/PDSN. The QoS update request of the parameter is used to update the QoS parameter in the PCF/PDSN. After receiving the QoS update request, the PCF/PDSN stores the QoS parameter of the service corresponding to the flow identifier.

At this time, the AN allocates air interface resources for the service by performing message interaction with the AT according to the configured QoS parameters of the service, that is, assigning an air interface connection corresponding to the QoS, mainly including: establishing and activating a certain wireless link a Radio Link Protocol (RLP) link of the Radio Link Protocol Identifier (RLPID), and binding the flow identifier corresponding to the service QoS with the RLPID to implement the correspondence between the QoS and the RLP link; The QoS of different services can be bound to the same RLP link. The number of QoS bound on the RLP link and the correspondence between the QoS and the RLP link are saved by the AN. If the QoS is the QoS of the reverse service, a medium access control (MAC) link with a Medium Access Control Flow Identifier (MACFlowID) is also required to be established and activated. The RLPID of the QoS corresponding RLP link is bound to the MACFlowID to implement the correspondence between the RLP link and the MAC link; different RLP links can be bound to the same MAC link, and the RLP chain bound on the MAC link The number of paths and the correspondence between the RLP link and the MAC link are saved by the AN.

Finally, the AT initiates a QoS activation request for the service carrying the flow identifier or other services that need to activate the QoS to the AN; after receiving the QoS activation request message, the AN sends the QoS activation request message to the PCF/PDSN. Send A9 to establish A8 (A9-Setup-A8) QoS update request, which carries the auxiliary service connection identifier (Additional A8 Traffic ID) and the forward/reverse QoS information (Forward/Reverse QoS Information) corresponding to the flow identifier. The pre/reverse QoS information indicates the service connection and the QoS correspondence relationship; after receiving the QoS update request, the PCF/PDSN obtains the QoS parameter corresponding to the flow identifier saved by itself, and establishes a service between the AN and the PCF/PDSN. Connection: A8 connection/A9 connection, and the service connection corresponds to the flow identifier of the QoS, and then accepts the QoS update request. At this point, the QoS of the service enters the authorization state. In this state, the service with QoS requirements can be transmitted by the AT to the packet data network through the AN and PCF/PDSN in turn, or can be transmitted to the AT through the PCF/PDSN and AN in turn by the packet data network.

After transmitting the service with the QoS requirement, the AT sends a QoS release request carrying the flow identifier to the AN. If the QoS is not the only QoS on the corresponding RLP link, after receiving the QoS release request, the AN sends an A9 update A8 (A9-Update-A8) QoS update request to the PCF/PDSN, where the QoS flow identifier is carried. Corresponding service connection and QoS correspondence. The AN and the PCF/PDSN delete the QoS parameters corresponding to the flow identifiers in the QoS release request message, and release the QoS resources corresponding to the flow identifier. If the QoS is the only QoS on the corresponding RLP link, when the AT requests the QoS release, the AN sends an A9 release A8 (A9-Release-A8) QoS update request to the PCF/PDSN, where the QoS flow identifier is carried. Corresponding auxiliary service connection identifier and service connection and QoS correspondence, requesting the PCF/PDSN to release the QoS and the corresponding service connection.

In this way, the prior art can perform QoS establishment, QoS activation, and QoS release for other services with QoS requirements.

The QoS state transition diagram of the above process is shown in Figure 1, which is a prior art QoS state transition diagram. Referring to Figure 1, QoS is divided into four states: empty state, configuration state, authorized state, and ready state. Where, the empty state: the service to be transmitted has no QoS state;

Configuration mode: The QoS configuration of the AT request service, and the QoS of the service after the AN is accepted is in the configuration state.

Ready state: The QoS of the service in the configured state completes all QoS parameter configuration and enters the state; in this state, when at least one QoS parameter configuration is not satisfied, the QoS of the service enters the configuration state.

Authorized state: After the QoS of the service in the ready state is activated, the authorization state is entered. In this state, the service can be transmitted normally. At this time, the QoS of the service is deactivated and enters the ready state. When at least one QoS parameter configuration is not satisfied, the entry is made. Configuration state; After the QoS resources of the service are released, they enter the empty state.

There are four QoS procedures for migrations that correspond to the above four states:

QoS establishment of the service: migration from the empty state to the configuration state or the ready state;

QoS release of the service: migrating from each state to the empty state (only the case from the authorized state to the empty state is shown in the figure);

QoS activation of the service: migration from ready state to authorized state;

QoS deactivation of the service: Migrate from the grant state to the ready state or configuration state.

It can be seen from the above that to transmit a service with QoS requirements, the AN needs to allocate a storage space for the service to store the QoS parameters corresponding to the service QoS flow identifier, and allocate resources for maintaining the service connection bound to the QoS. Service connections include air interface links and A8 connections/A9 connections. In this way, the QoS of the service occupies a large amount of resources in the AN.

Corresponding to the above process, when the AT sends an QoS activation request and a release request to the AN, the AN sends a corresponding QoS update request to the PCF/PDSN. In the QoS update process, when the PCF/PDSN is abnormal, the QoS parameters corresponding to the flow identifier in the QoS update request are lost, and the QoS parameters corresponding to the flow identifiers of the AT and the PCF/PDSN and the AN and the PCF/PDSN are inconsistent. When the PCF/PDSN does not have the corresponding flow identifier The QoS parameters are rejected, and the AT is rejected by the AN to initiate a QoS update request, thereby causing the QoS resources of the AT and the AN to hang.

However, in the DOA, the QoS establishment and release of the service can only be initiated by the AT. The AN cannot release the QoS resources in the AN even if it knows that it has hanged QoS resources. Therefore, the hanged QoS resources in the AN cannot be released. In the case that multiple ATs or multiple services with QoS requirements have the above phenomenon, the AN will save a large number of QoS resources that cannot be released, resulting in waste of QoS resources.

In addition, when the ATA activation initiated by the AT to the AN fails, the AT repeatedly initiates a QoS activation request. Because the QoS parameter corresponding to the flow identifier in the QoS activation request saved by the PCF/PDSN is lost, the message that rejects the QoS update, that is, the QoS activation request, is repeatedly sent to the AT through the AN, so that the QoS activation process of the service enters an infinite loop. Repeated QoS activation Request interactions occupy the resources of the AN, reducing the processing power of the AN. When multiple ATs or multiple services with QoS requirements appear in the above situation, it will inevitably affect the normal processing of the service by the AN.

Moreover, the resources of the AN are limited. When the AN accesses multiple services with different QoS requirements, the services that are required by the QoS are not satisfied because the resources are occupied by the AN. If the AN can actively release a part of the QoS resources, the service with high QoS requirements is allowed. Resources can meet the needs of users. However, in the prior art, the QoS establishment and release of the service are initiated by the AT, and the AN cannot initiate the release of the QoS, and therefore cannot satisfy the use of the service by the user with high QoS of the service. Therefore, in this case, the shortcomings of the prior art affect the quality of the wireless communication system serving the user. Summary of the invention

In view of this, the embodiments of the present invention provide a method for releasing QoS resources, so that the access network can actively release QoS resources. The embodiment of the invention provides a system for releasing QoS resources, so that the access network can actively release QoS resources.

The embodiment of the invention provides an access network for releasing QoS resources, and the access network can actively release QoS resources.

The embodiments of the present invention provide an access terminal that releases QoS resources, and releases QoS resources in conjunction with the access network.

The technical solution of the embodiment of the present invention is implemented as follows:

A method of releasing quality of service resources, including:

The access network releases the quality of service. The QoS corresponds to the air interface connection with the access terminal; the access network releases its own storage space of the QoS.

A system for releasing a quality of service resource, comprising: an access terminal and an access network, where the access terminal is configured to receive a message that is sent by an access network and that is related to an air interface connection between the access terminal and the access terminal;

The access network is configured to send a message for releasing an air interface connection between the access terminal and the access terminal to the access terminal, and release the storage space of the QoS of the QoS.

An access network for releasing a quality of service resource, the access network comprising a transceiver module and a QoS resource release module,

The transceiver module is configured to send, by the QoS resource release module, a message corresponding to the release QoS of the QoS resource release module to the air interface of the access terminal to the access terminal;

And the QoS resource release module is configured to send, to the transceiver module, a message for releasing an air interface connection between the access terminal and the access terminal, and releasing the storage space of the QoS of the access network itself.

An access terminal for releasing a quality of service resource, the access terminal comprising a terminal transceiver module and a QoS release response module,

The terminal transceiver module is configured to receive and release a release QoS corresponding to an access network Receiving a message of the air interface connection between the terminals; receiving a QoS release request message sent by the access network, forwarding the message to the QoS release response module; and transmitting, by the QoS release response module, the message receiving the QoS release request to the access network;

The QoS release response module is configured to receive a QoS release request forwarded by the terminal transceiver module, and send a message to the terminal transceiver module to accept the QoS release request.

It can be seen from the above technical solution that the method, system, access network and access terminal for releasing the quality of service resources provided by the embodiment of the present invention enable the access network to actively release the air interface connection corresponding to the QoS and the storage space of its own QoS. That is, the access network can actively release QoS resources, avoiding waste of resources, and making effective use of resources limited to the access network. BRIEF DESCRIPTION OF THE DRAWINGS

1 is a prior art QoS state transition diagram;

2 is a flowchart of a method for releasing a quality of service resource according to an embodiment of the present invention; FIG. 3 is a flowchart of a method according to Embodiment 1 of the present invention;

4 is a flowchart of a method according to Embodiment 2 of the present invention;

5 is a flowchart of a method according to Embodiment 3 of the present invention;

FIG. 6 is a structural diagram of a system for releasing a quality of service resource according to an embodiment of the present invention. Mode for carrying out the invention

The present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.

2 is a flowchart of a method for releasing a quality of service resource according to an embodiment of the present invention. Referring to FIG. 2, the method includes the following steps:

Step 200: The access network releases the air interface connection with the access terminal corresponding to the QoS. The process performed in this step is: accessing the network to QoS from the corresponding access terminal The RLP link is unbound; when the QoS is the only QoS corresponding to the RLP link, the step further includes deactivating the RLP link; in this case, when the QoS is reverse QoS, this step Still further comprising unbinding the deactivated RLP link from the corresponding MAC link further comprising deactivating the MAC link.

Step 201: The access network releases its storage space of the QoS.

The method may further include: the access network transmitting a QoS release request to the access terminal, and the access terminal accepting the QoS release request sent by the access network.

In the actual application, the method flow shown in Figure 2 may be triggered by the QoS update failure message sent by the gateway to trigger the access network to initiate; or when the resources of the access network are tight, the access network actively initiates.

When the access network actively initiates the release of the QoS resource due to resource constraints, the method further includes: the access network sending a message to the gateway to release the QoS resource of the gateway.

When the gateway sends a QoS update failure message and the access network initiates release of the QoS resource, the method further includes: the access network sending a message to the access terminal to prevent the access terminal from initiating a corresponding QoS re-update. The method may further comprise the step of the access terminal releasing the corresponding QoS resource and storage space.

The three embodiments of the present invention will be described in detail below by taking the D0A system as an example. In this system, the access terminal is AT, the access network is AN, and the gateway is PCF/PDSN.

Embodiment 1:

This embodiment details the method in which the AN actively releases the QoS resources after the QoS activation request initiated by the AT fails due to the QoS hang on the AN side. The AT initiates a QoS activation request to the AN. When the AN sends the A9 (A9-Setup-A8) QoS update request carrying the corresponding QoS flow identifier to the PCF/PDSN, the PCF/PDSN cannot find the corresponding QoS parameter. In the case where the QoS on the AN side is hanged, the AN actively initiates the hang of QoS resources. freed. FIG. 3 is a flowchart of a method according to Embodiment 1 of the present invention. Referring to FIG. 3, the method includes the following steps:

Step 300: The AT sends a QoS activation request carrying the flow identifier to the PCF/PDSN through the AN.

In this step, the AT first sends a QoS activation request message carrying the flow identifier to the AN, and then the AN sends a QoS update request to the PCF/PDSN carrying the A9 (A9-Setup-A8) message carrying the flow identifier.

The carried flow identifier may be one or more, which indicates a flow identifier corresponding to one QoS of one service, or a flow identifier corresponding to multiple QoSs of one service, or a flow identifier corresponding to QoS of multiple services.

Step 301: The PCF/PDSN sends a message rejecting the QoS update to the AN, and the QoS update fails.

The PCF/PDSN determines that the QoS parameter corresponding to the flow identifier is lost, that is, when the QoS corresponding to the flow identifier is determined to be hanged QoS, this step is performed.

In the prior art, before the AT initiates the QoS activation request carrying the flow identifier, the gateway has saved the QoS parameters corresponding to the flow identifier. However, the QoS parameters saved by the gateway may be lost under abnormal conditions. Therefore, when the QoS activation request is received, it is determined whether the corresponding QoS parameters are also saved.

In this step, the PCF/PDSN sends a message rejecting the QoS update to the AN, and carries the auxiliary service connection identifier and the service connection and QoS corresponding to the flow identifier of the QoS that failed this update.

Step 302: The AN prevents the AT from initiating hang-up QoS reactivation. This step is optional and can be initiated by the AN at any time after the QoS update fails.

In this step, the AN sends an attribute update request (AttributeUpdateRequest) message to the AT, and the message carries the pre/reverse QoS response. (ReservationKKQoSResponseFwd/Rev) attribute, the GrantedSetID field in the attribute is filled with 0, and the flow identifier in the attribute is the flow identifier of the hanged QoS, so that the AT knows that the AN no longer authorizes the hanged QoS. After receiving the attribute update request message, the AT sends an attribute update accept (AttributeUpdateAccept) message to the AN. At this time, although the state of the hang QoS on the AT is in the ready state, the activation of the hang QoS is no longer initiated.

Step 303: The AN binds the hang QoS from the RLP link corresponding to the hang QoS.

In this step, the AN sends an attribute update request message carrying the pre-/reverse RLP flow and QoS binding relationship (FlowNNReservationFwd/Rev) attribute to the AT, and the RLPID in the attribute value is the RLPID corresponding to the flow identifier of the hanged QoS. The hanged QoS is unbound from the RLP link corresponding to the RLPID. After receiving the attribute update request message, the AT sends an attribute update accept message to the AN.

At this point, the state of the hanged QoS on the AT and AN migrates to the configuration state.

Step 304: When the hang QoS is the only QoS corresponding to the RLP link, the AN deactivates the RLP link. This step is an optional step.

When the hang QoS is not the only QoS on the RLP link, this step can be omitted, and step 307 is directly executed.

In this step, the AN sends an attribute update request message carrying the pre/reverse RLP stream parameter setting (FlowNNIdentificationFwd/Rev) attribute to the AT, and the RLPID in the attribute value is the RLPID corresponding to the stream identifier of the hanged QoS, in the attribute value. The Active field is set to zero, and the RLP link corresponding to the hanged QoS is deactivated. After receiving the attribute update request message, the AT sends an attribute update accept message to the AN.

Step 305: If the hang QoS is the QoS of the reverse service, de-binding the RLP deactivated in step 304 from the MAC link corresponding to the RLP link. This step is an optional step. In this step, the AN sends an attribute update request message carrying the RLP flow and the MAC flow binding relationship (Associated FlowNN) attribute to the AT, and the RLP link is unbound from the corresponding MAC link. After receiving the attribute update request message, the AT sends an attribute update accept message to the AN. This step is an optional step.

Step 306: If the RLP link is the last RLP link on the MAC link corresponding to the RLP link, the AN deactivates the corresponding MAC link. This step is an optional step.

If the RLP link is not the last RLP link on the MAC link corresponding to the RLP link, this step may be omitted.

In this step, the AN sends an attribute update request message carrying the value of the bucket maximum value ( BucketLevelMaxNN ) set to zero to the AT, and deactivates the MAC link corresponding to the RLP link. After receiving the attribute update request message, the AT sends an attribute update accept message to the AN. This step is an optional step.

Step 307: The AN releases the storage space of the hanged QoS in the AN.

At this time, the state of the hanged QoS in the AN and the AT is inconsistent, and the hang QoS at the AT is the configuration state, but the corresponding QoS of the AN has gone to the empty state.

Step 308: The AT initiates release of the hanged QoS, that is, sends a QoS release request carrying the hanged QoS flow identifier to the AN. This step is an optional step.

In this step, the AT sends an attribute update request message carrying the pre-/reverse QoS request (ReservationKKQoSRequestFwd/Rev) attribute to the AN to release the hanged QoS, where the attribute type (ProfileType) field is null (NULL), in the attribute The flow identifier is a flow identifier that hangs the QoS.

Step 309: The AN sends an attribute update accept message to the AT, and the AT releases its own storage space of the hanged QoS. This step is an optional step.

At this time, the state of this hanged QoS on the AT transitions to the empty state.

Embodiment 2: This embodiment details the method in which the AN actively releases the hang QoS when the QoS update initiated by the AT fails due to the QoS hang on the AN side.

In this embodiment, the AN actively releases the hang QoS by two conditions:

The first case: The AT sends a QoS release request to the AN, and the AN sends the A9 release A8 (A9-Release-A8) QoS carrying the auxiliary service connection identifier corresponding to the QoS flow identifier and the service connection and QoS correspondence relationship to the PCF/PDSN. The update request, that is, the QoS release request, causes the AN-side corresponding QoS to hang due to the PCF/PDSN not finding the corresponding QoS, and the PCF/PDSN sends a message rejecting the current QoS update to the AN.

The second case: when the AT initiates a second service that is close to the QoS requirement of the first service, that is, when the QoS parameter is used in the same threshold range as the QoS parameter of the first service, the AN sends the bearer to the PCF/PDSN. The service connection corresponding to the traffic identifier and the QoS correspondence A9 update the QoS update request of A8. Since the PCF/PDSN cannot find the corresponding QoS parameter and the QoS hangs on the AN side, the PCF/PDSN sends the AN to reject the QoS update. Message.

4 is a flowchart of a method according to Embodiment 2 of the present invention. Referring to FIG. 4, the method includes the following steps:

Step 400: The AT sends, by the AN, a QoS update request carrying the auxiliary service connection identifier corresponding to the QoS flow identifier and the service connection and the QoS correspondence relationship to the PCF/PDSN.

In this step, the AT first sends a QoS update request carrying the flow identifier to the AN, and the QoS update request may be a QoS activation request or a QoS release request; then the AN sends a QoS update request to the PCF/PDSN, the QoS update. The request may be an A9 release A8 message carrying an auxiliary service connection identifier corresponding to the QoS flow identifier and a service connection and QoS correspondence, or an A9 update A8 message carrying the service connection and QoS correspondence corresponding to the QoS flow identifier. .

Step 401: The PCF/PDSN sends a message rejecting the current QoS update request to the AN. This QoS update failed.

The PCF/PDSN sends the refusal to the AN when the PCF/PDSN corresponds to the QoS corresponding to the QoS of the QoS. The message of the secondary QoS update request, which carries the auxiliary service connection identifier corresponding to the flow identifier of the QoS that failed this update, and the correspondence between the service connection and the QoS; after receiving the message, the AN identifies the auxiliary service connection identifier in the message. The service connection and the QoS correspondence correspond to the QoS flow identifier, and according to the message, the QoS update corresponding to the flow identifier fails.

Step 402: The AN sends a QoS release request to the AT. This step is an optional step. In this step, the AN sends an attribute update request message carrying the attribute pre/reverse QoS request ( ReservationKKQoSRequestFwd/Rev) to the AT, and the attribute carries the flow identifier of the QoS that failed this update, and the service type in the attribute value (ProfileType ) The field is set to zero. After receiving the attribute update request message, the AT returns an attribute update accept message to the AN.

Step 403: The AT sends a message to the AN to accept the QoS release request. This step is an optional step.

In this step, the AT sends an attribute update request message carrying the value of the ReservationKKQoSResponseFwd/Rev attribute to the AN. After receiving the attribute update request message, the AN sends an attribute update accept message to the AT.

Steps 404 to 407 are the same as steps 303 to 306.

Step 408: The AN and the AT respectively release their own storage space of the QoS.

Embodiment 3:

This embodiment details the method in which the AN actively initiates QoS resource release when the resources of the AN are tight. FIG. 5 is a flowchart of a method according to Embodiment 3 of the present invention. Referring to FIG. 5, the method includes the following steps: Step 500: The AN sends a QoS release request to the AT. This step is an optional step.

In this step, the AN sends an attribute update request message carrying the attribute pre/reverse QoS request ( ReservationKKQoSRequestFwd/Rev) to the AT, carries the flow identifier of the QoS to be released, and sets the service type (ProfileType) field in the attribute value to zero. . After receiving the attribute update request message, the AT replies to the AN with an attribute update accept message.

Steps 501 to 506 are the same as steps 403 to 408. The flow carried in the message is identified as the flow identifier of the QoS that needs to be released by the AN.

Step 507: The AN sends a QoS update request message corresponding to the QoS to the gateway. This step is an optional step.

In this step, if the QoS that the AN needs to release is the only QoS on the corresponding RLP link, the AN sends a QoS update request carrying the auxiliary service connection identifier corresponding to the QoS flow identifier and the service connection and QoS correspondence relationship to the gateway. That is, the A9-Release-A8 message releases the QoS parameter stored in the gateway and the service connection corresponding to the QoS; if, in addition to the QoS to be released, other QoS is bound to the corresponding RLP link, the AN goes to the gateway. The QoS update request carrying the service connection and the QoS corresponding relationship, that is, the A9-Update-A8 message, is sent, and only the QoS to be released saved on the gateway is released.

FIG. 6 is a structural diagram of a system for releasing a quality of service resource according to an embodiment of the present invention. Referring to Figure 6, the system includes an access terminal and an access network.

The access terminal is configured to receive, by the access network, a message that is related to an air interface connection between the access terminal and the release QoS.

The access network is configured to send a message for releasing an air interface connection between the access terminal and the access terminal to the access terminal, and release its own storage space of the QoS.

Specifically, the access network includes: a transceiver module, configured to send, by the QoS resource release module, a message for releasing an air interface between the access network corresponding to the access network and the access terminal to the access terminal; the QoS resource release module, Sending a release QoS-compliant access to the transceiver module The message of the air interface connection between the network and the access terminal, and releasing the access network itself

QoS storage space.

The access terminal includes: a terminal transceiver module, configured to receive a message of an air interface connection between the access network and the access terminal corresponding to the release QoS sent by the access network.

The access network may further include: a release requesting module, configured to send a QoS release request to the access terminal by using the transceiver module; at this time, the access terminal further includes: a QoS release response module, configured to access the network through the terminal transceiver module Send a message accepting the QoS release request.

The system further includes a gateway (not shown). In this case, the access terminal may further include: a QoS update request module, configured to send, by using the terminal transceiver module, a QoS update request message carrying the QoS flow identifier to the access network. The transceiver module in the access network further forwards the QoS update request message that carries the QoS flow identifier sent by the access terminal to the gateway; the gateway receives the QoS update request message sent by the access network, and determines that the saved corresponding QoS parameter is lost. That is, after determining that the QoS resource is hanged, a message that the QoS update fails is sent to the access network. Therefore, the access network automatically activates the QoS resources that fail to be updated, and the hanged QoS continues to occupy the resources of the access network, resulting in waste of resources.

When the QoS update request is a QoS activation request sent by the access terminal to the access network, the access network further includes: a blocking activation module, configured to send, by the transceiver module, the access terminal to prevent the access terminal from initiating the update failure QoS again. The activated message carrying the pre/reverse QoS response attribute; after receiving the message carrying the pre/reverse QoS response attribute sent by the access network, the QoS update request module no longer initiates activation of the failed QoS. Therefore, the access terminal does not repeatedly initiate the activation of the hang-up QoS on the network side, thereby avoiding the reduction of the processing capability of the access network due to the repeated initiation of QoS activation by the access terminal.

It can be seen from the foregoing that the method, the system, the access network, and the access terminal for releasing the quality of service resources provided by the embodiments of the present invention enable the access network to actively release the QoS corresponding The air interface connection and its own QoS storage space, that is, the access network can actively release QoS resources, thereby avoiding waste of resources and making effective use of resources limited to the access network.

When the QoS resources are hanged in the access network, the access network actively initiates the release of the hanged QoS resources, thereby avoiding the waste of the access network QoS resources caused by the hang of the QoS resources. In addition, the access network prevents the access terminal from repeatedly initiating the activation of the hang QoS, thereby avoiding the reduction of the access network processing capability caused by the access terminal repeatedly initiating QoS activation; and causing the access terminal to normally release its own hanged QoS resources.

The above description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A method for releasing a quality of service resource, the method comprising: the access network releasing an air interface connection between the access quality terminal corresponding to the quality of service QoS; and the access network releasing its own storage of the QoS space.

The method according to claim 1, wherein the access network releases the air interface connection with the access terminal corresponding to the QoS: the access network uses the QoS from the corresponding radio link protocol RLP Unbind on the link.

The method according to claim 1, wherein the access network releases the air interface connection between the QoS and the access terminal as: the access network sends the pre-/reverse RLP stream to the access terminal. An attribute update request message with a QoS binding relationship attribute.

4. The method of claim 2, wherein the QoS is the only QoS on the corresponding RLP link,

After the access network releases the air interface connection with the access terminal corresponding to the QoS, the method further includes: the access network deactivating the RLP link.

5. The method of claim 2, wherein the QoS is the only QoS on the corresponding RLP link,

After the access network releases the air interface connection with the access terminal corresponding to the QoS, the method further includes: the access network sending an attribute update request message carrying the pre/reverse RLP stream parameter setting attribute to the access terminal.

The method according to claim 4, wherein, after the QoS is reverse QoS, after the access network deactivates the RLP link, the method further comprises: accessing the network to the RLP chain The path is bound from the corresponding media access control MAC link.

7. The method according to claim 4, wherein when the QoS is reverse QoS, After the access network deactivates the RLP link, the method further includes: the access network sending an attribute update request message carrying the RLP flow and the MAC flow binding relationship attribute to the access terminal.

8. The method according to claim 6, wherein when the RLP link is the only link on the MAC link, the method further comprises: the access network deactivating the MAC link.

The method of claim 6, wherein the RLP link is the only link on the MAC link, and the method includes: the access network sends the maximum value of the leaky bucket to the access terminal. Attribute update request message.

The method according to claim 1, wherein before the access network releases the air interface connection between the QoS and the access terminal, the method further comprises: the access network sending the QoS release to the access terminal. request.

The method of claim 10, wherein, after the access network sends a QoS release request to the access terminal, the method further includes: the access terminal transmitting the accepting the QoS release request to the access network. Message.

12. The method according to claim 1, wherein after the access network releases its storage space of the QoS, the method further comprises: the access network sending a QoS update request for releasing the QoS to the gateway. Message.

The method according to claim 12, wherein the access network sends a QoS update request message releasing the QoS to the gateway: when the QoS is the only QoS on the corresponding RLP link The access network sends a QoS update request message that releases the QoS and releases the service connection corresponding to the QoS to the gateway; otherwise, the access network sends a release to the gateway. The QoS QoS Update Request message is placed.

The method of claim 1, wherein before the access network releases the air interface connection between the QoS and the access terminal, the method further includes:

The gateway receives the QoS update request initiated by the access terminal and carries the auxiliary service connection identifier or the service connection and the QoS corresponding to the QoS flow identifier, and connects the auxiliary service connection identifier or the service connection in the QoS update request message. The QoS corresponding relationship corresponds to the QoS flow identifier, and after determining that the saved QoS parameter corresponding to the flow identifier is lost, sending a QoS update failure message to the access network.

The method according to claim 14, wherein the air interface connection between the access network and the access terminal corresponding to the QoS release is:

The access network releases the air interface connection with the access terminal corresponding to the QoS in the QoS update failure message.

The method of claim 14, wherein the QoS update request is a QoS activation request sent by the access terminal to the access network, the method further comprising: before the access network sends the bearer to the access terminal/ An attribute update request message of the reverse QoS response attribute,

The method according to claim 1, 10, 12 or 14, wherein after the access network releases its own storage space of the QoS, the method further comprises: the access terminal releasing its own The storage space of the QoS.

18. A system for releasing quality of service resources, including an access terminal and an access network, characterized in that

The access terminal is configured to receive a message that is sent by the access network and that is related to an air interface connection between the access terminal and the access terminal;

The access network is configured to send a message for releasing an air interface connection between the QoS and the access terminal to the access terminal, and release the storage space of the QoS of the QoS.

The system according to claim 18, wherein the access network comprises: a transceiver module, configured to connect an air interface between the access network corresponding to the release QoS of the QoS resource release module and the access terminal The message is sent to the access terminal, and the QoS resource release module is configured to send, to the transceiver module, a message for releasing the air interface connection between the access network and the access terminal corresponding to the QoS, and releasing the storage space of the QoS of the access network itself. ;

The access network further includes: a release requesting module, configured to send a QoS release request to the transceiver module; the transceiver module further transmitting a QoS release request of the release requesting module to the access terminal;

The access terminal includes: a terminal transceiver module, configured to receive a message of an air interface connection between an access network and an access terminal corresponding to the release QoS sent by the access network;

The access terminal further includes: a QoS release response module, configured to send a message accepting the QoS release request to the terminal transceiver module; the terminal transceiver module further forwards the QoS release request message sent by the access network to the QoS release a response module: transmitting, by the QoS release response module, a message accepting the QoS release request to the access network.

The system of claim 19, wherein the access terminal further comprises: a QoS update request module, configured to send, by using a terminal transceiver module, a QoS update request message carrying a QoS flow identifier to the access network;

The transceiver module further forwards the QoS update request message that carries the QoS flow identifier sent by the access terminal to the gateway, and forwards the QoS update failure message sent by the gateway to the QoS resource release module.

The system further includes a gateway, configured to receive a QoS update request message sent by the access network, and determine to send a message that the QoS update fails to the access network after the saved corresponding QoS parameter is lost.

The system according to claim 20, wherein the QoS update request is a QoS activation request sent by an access terminal to an access network, The access network further includes: a blocking activation module, configured to send, by the transceiver module, a message to the access terminal to prevent the access terminal from initiating the update failed QoS re-active pre-/reverse QoS response attribute;

The terminal transceiver module further forwards a message carrying the pre/reverse QoS response attribute sent by the access network to the QoS update request module; the QoS update request module no longer initiates activation of the failed QoS.

The transceiver module is configured to send, by the QoS resource release module, a message that the air interface between the access network corresponding to the release QoS and the access terminal is sent to the access terminal;

And the QoS resource release module is configured to send, to the transceiver module, a message for releasing an air interface connection between the access network and the access terminal corresponding to the QoS, and releasing the storage space of the QoS of the access network itself.

The access network according to claim 22, wherein the access network further includes a release request module, configured to send a QoS release request to the transceiver module;

The transceiver module further sends a QoS release request of the release request module to the access terminal.

The access network according to claim 22, wherein the access network further comprises a blocking activation module, configured to send, to the transceiver module, a message that prevents QoS activation of the update failure;

The transceiver module further transmits a message of the QoS prevention activation module that prevents the update from failing to initiate activation of the QoS to the access terminal.

The terminal transceiver module is configured to receive an access QoS corresponding to the access network a message of an air interface connection between the network and the access terminal; receiving a QoS release request message sent by the access network, forwarding the message to the QoS release response module; and transmitting, by the QoS release response module, the message accepting the QoS release request to the access network ;

The QoS release response module is configured to receive a QoS release request forwarded by the terminal transceiver module, and send a message accepting the QoS release request to the terminal transceiver module.

The access terminal according to claim 25, wherein the QoS release response module further releases the storage space of the QoS of the access terminal itself.

The access terminal according to claim 25, wherein the access terminal further comprises: a QoS update requesting module, configured to send, by using the terminal transceiver module, a QoS update carrying a QoS flow identifier to an access network Request message