WO2010139261A1

WO2010139261A1 - Resource control method and system

Info

Publication number: WO2010139261A1
Application number: PCT/CN2010/073406
Authority: WO
Inventors: 霍玉臻; 周娜
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-06-05
Filing date: 2010-05-31
Publication date: 2010-12-09
Also published as: CN101720113A; CN101720113B

Abstract

A resource control method and system for a terminal accessing Worldwide Interoperability for Microwave Access (WiMAX) network are provided in the present invention. In the present invention scheme, a policy implementation network element provides resource change policy of service flow to each policy implementation function entity related to the corresponding service flow. The resource change policy of the service flow can be from an Authentication Authorization Accounting (AAA) server or a policy server, or can be configured by the policy implementation network element itself. The policy implementation network element provides the resource change policy of the service flow to each policy implementation function entity related to the corresponding service flow, thus according to the resource change policy each policy implementation function entity can definitely determine which operations can be executed and which operations are not allowed. Moreover, referring to same service flow the operations that each policy implementation function entity can execute are uniform, which to the maximum avoids the occurrence of inconsistent allowed operations for the same service flow at different policy implementation function entities, and can accurately control the service flow resources.

Description

Method and system for resource control

The present invention relates to the field of communications, and in particular to a terminal that communicates globally in microwave access.

(WiMAX, Worldwide Interoperability for Microwave Access) Resource control method and system for network access. Background technique

The current WiMAX network generally consists of three parts: a WiMAX terminal, an Access Service Network (ASN), and a Connect Service Network (CSN), as shown in Figure 1. For convenience of description, the following WiMAX terminal is simply referred to as a terminal.

The ASN mainly performs the following functions: completing the Layer 2 (L2) connection of the terminal, and transmitting the AAA (Authentication Authorization Accounting) message to the Home CSN (H-CSN) and the Network Service Provider (NSP). Network selection and discovery, relaying for terminal Layer 3 (L3) connections, radio resource management, tunnel maintenance between ASN and CSN. In the mobile scenario, the ASN also needs to support the following functions: ASN Anchored MM, CSN Anchored MM, Paging and Idle Mode.

The ASN is also used to manage the IEEE 802.16 air interface to provide wireless access to the terminal. The ASN is composed of a base station (BS) and an ASN gateway (AGW, ASN-GW), and may include a single AGW, as shown in FIG. 2A; and may also include multiple AGWs, as shown in FIG. 2B. The ASN communicates with the terminal at the R1 reference point, interworks with the CSN at the R3 reference point, and communicates with another ASN at the R4 reference point. The ASN is managed by a Network Access Provider (NAP).

CSN is a combination of network functions. The CSN can be used by Mobile IP's Home Agent (HA), AAA Proxy (AAA Proxy) or AAA Server (AAA Server), billing server, and mutual It is composed of gateway devices and so on. The CSN is managed by a Network Service Provider (NSP). The CSN mainly performs the following functions: session connection of the end user, IP address allocation of the terminal, Internet access, AAA proxy or AAA server, policy and license control of the end user, tunnel maintenance between the ASN and the CSN, and billing of the end user And settlement, roaming between CSNs, mobility management between CSNs, and WiMAX services.

If the terminal user needs to perform data services, it needs to be transparently forwarded through the network elements of the WiMAX network. For example, when the terminal user is a mobile IP user, the network elements passing through include: BS, AGW, and HA. In the forwarding nodes of these WiMAX networks, in order to distinguish data packets of different users, data packets of different users need to be forwarded through different data channels, and generally use Generic Routing Encapsulation (GRE) technology. Further, the same user may also perform different service applications at the same time, such as VoIP (voice over Internet Protocol), email, game, etc., and different service applications have different QoS (Quality of Service) requirements, Providing better services to users requires different data channels and differentiated QoS services for different business applications.

Here, the meaning of the data channel corresponds to the service flow, and the service flow is further divided into a preliminary service flow and a dynamic service flow. The pre-service flow is the data channel that the network immediately establishes for the user during the initial access process. Through these pre-service flows, some basic applications of the user can be guaranteed, and some basic upper-layer signaling protocols, such as the dynamic host configuration protocol, are carried. DHCP, Dynamic Host Configuration Protocol, Mobile IP (MIP, Mobile IP), for user IP address allocation, etc., the preliminary service flow is always maintained before the user quits, and will not be released. The dynamic service flow is a data channel that is temporarily established after a user accesses the WiMAX network at a certain time before the network is retired. Therefore, the corresponding data channel can be released immediately after the service application ends. To save network resources.

FIG. 3A is a schematic diagram of a process of establishing a preliminary service flow. As shown in FIG. 3A, the establishment of a preliminary service flow specifically includes the following steps: Step 301 A: The terminal accesses the WiMAX network, and initiates an initial access authentication process.

Step 302A: After the user is successfully authenticated, the AAA server notifies the relevant authorization parameter to the AGW through the Access Accept message, and the related authorization parameter includes the preliminary service flow parameter, and the preliminary service flow parameter may be multiple preliminary service flows. Parameters such as the number of traffic flows, authorization parameters per traffic flow, and so on. The Access Accept message may be based on a Radius (Remote Authentication Dial In User Service) protocol.

Step 303A: After the user successfully registers, the AGW sends an initial/pre-service flow setup request (Path_Reg_Req) message to the BS, and immediately initiates establishment of the initial service flow, where the initial service flow is the initially established preliminary service flow.

Step 304A: After receiving the Path_Reg_Req message, the BS sends a dynamic service establishment request (DSA_REQ) message to the terminal, requesting the terminal to establish a data channel.

Step 305A: After receiving the DSA_REQ message, the terminal applies for the resource of the relevant data channel, and sends a dynamic service establishment response (DSA_RSP) message to the BS in response to the DSA_REQ message of the BS.

Step 306A: After receiving the DSA_RSP message, the BS sends an initial/pre-service flow establishment response (Path_Reg_Rsp) message to the AGW after the resource allocation is successful.

Step 307A: After receiving the Path_Reg_Rsp message, the AGW confirms that the resource allocation is successful, and sends an initial/pre-service flow setup response (Path_Reg_Ack) message to the BS to confirm that the resource allocation is successful.

Step 308 A: After receiving the Path_Reg_Ack message, the BS sends a dynamic service setup response (DSA_ACK) message to the terminal to confirm to the terminal that the resource allocation is successful.

At this point, the terminal, BS, and AGW all allocate relevant resources for the service flow and establish a complete data channel.

Step 309A: If the AAA server further authorizes other preliminary service flows, the steps are sequentially established according to the above steps. FIG. 3B is a schematic diagram of a process of establishing a dynamic service flow initiated by a terminal. The process is similar to that of FIG. 3A, but the direction is reversed, and specifically includes the following steps:

Step 301B: The terminal sends a DSA_REQ message to the BS, requesting the BS to establish a dynamic service flow. Step 302B: After receiving the DSA_REQ message, the BS sends a dynamic service flow establishment request (Path_Reg_Req) message to the AGW, requesting the AGW to establish a dynamic service flow.

Step 303B: After receiving the Path_Reg_Req message, the AGW sends a dynamic service flow establishment response (Path_Reg_Rsp) message to the BS after the resource allocation is successful.

Step 304B: After receiving the Path_Reg_Rsp message, the BS confirms that the resource allocation is successful, and sends a DSA_RSP message to the terminal to confirm that the resource allocation is successful.

Step 305B: After receiving the DSA_RSP message, the terminal confirms that the resource allocation is successful, and sends a DSA_ACK message to the BS.

Step 306B: After receiving the DSA_ACK message, the BS sends a dynamic service flow establishment response (Path_Reg_Ack) message to the AGW.

At this point, the terminal, BS, and AGW all allocate related resources for the dynamic service flow and establish a complete data channel.

Step 307B: If the AAA server also authorizes other dynamic service flows, the steps are sequentially established according to the above steps.

The establishment of the dynamic service flow can also be initiated by the network side, and the process is basically the same as that of FIG. 3A, and details are not described herein again.

There are different requirements for different types of service flows. For example, for the preliminary service flow, based on the Net Working Group (NWG) protocol, deletion and modification are not allowed during a session of the user; The flow can be created at any time during a session of the user, and can generally be modified or deleted according to the needs of the business application. Referring to FIG. 3A and FIG. 3B, the message exchanged between the terminal and the BS is a DSA-REQ message, a DSA-RSP message, and a DSA-ACK message, whether it is a preliminary service flow establishment or a dynamic service flow establishment. Except that the first established service flow explicitly described in the protocol is a preliminary service flow, each network element can be clearly identified; for other service flows, each network element cannot distinguish between which is a preliminary service flow and which is a dynamic service flow. If multiple service flows are initially established, each network element may not be able to identify which service flow is a preliminary service flow. In this way, the different operational restrictions for different types of service flows specified in the current NWG protocol cannot be discussed. In particular, after the user crosses the BS handover and crosses the AGW handover, the switched BS and AGW are unable to identify the type of the service flow. . The resulting problems are also very obvious.

For example, because the terminal cannot identify which are the preliminary service flow and which are the dynamic service flow, the terminal may initiate the deletion process for the preliminary service flow; and the BS also cannot identify which is the preliminary service flow and which is the dynamic service flow, and may accept The pre-service flow deletion initiated by the terminal; the AGW may store the type of the service flow in its local context before the handover, and can identify which are the dynamic service flow and which are the preliminary service flow, and thus will reject according to the local context. The standby service flow initiated by the terminal is deleted. However, if the AGW is handed over, the AGW after the handover cannot identify which is the standby service flow and which is the dynamic service flow. Therefore, the standby service flow initiated by the terminal may be deleted. Normally resides in the WiMAX network.

Although the AGW may reject the deletion operation for the preliminary service flow, due to the well-known reasons, the deletion operation initiated by one network element or terminal cannot be rolled back because the deletion operation is more indicative. It is not a request. Even if the AGW refuses to delete the operation, the terminal and the BS also delete the related resources of the service flow, which also causes the terminal to not reside in the WiMAX network. Summary of the invention

In view of this, the main object of the present invention is to provide a method and system for resource control, which realizes precise control of service flow.

In order to solve the above technical problem, the technical solution of the present invention is implemented as follows:

A method of resource control, in which a terminal accesses a Worldwide Interoperability for Microwave Access (WiMAX) network, The method includes:

The policy enforcement network element provides a resource change policy for the service flow to each of the policy enforcement function entities associated with the service flow.

Before the policy execution network element provides the resource change policy of the service flow to each of the policy execution function entities related to the corresponding service flow, the method further includes:

a resource change policy for authenticating an authorized accounting (AAA) server or a policy server to authorize a service flow to a policy enforcement network element; or

The policy execution NE configures the resource change policy of the service flow.

When the policy execution network element is an access service network gateway (AGW), the AAA server or the policy server authorizes the resource change policy of the service flow to the policy execution network element, specifically: after the terminal initial access authentication succeeds, the AAA The resource change policy of the service flow is sent to the AGW by the server or the policy server by using the access accept message; or

The AAA server changes the resource change policy of the service flow, and sends a new resource change policy to the AGW by authorizing the change message.

The policy execution network element is an AGW, and when the policy execution function entity is also an AGW, the policy execution network element provides a resource change policy of the service flow to the policy execution function entity related to the service flow, specifically: The anchored traffic flow authorization (SFA) logical entity in the AGW of the policy enforcement network element notifies the resource change policy to the anchor data channel function (DPF) logical entity in the AGW as the policy enforcement function entity through the resource reservation request message;

The policy execution network element is an AGW, and when the policy execution function entity is a base station (BS), the policy execution network element provides a resource change policy of the service flow to the policy execution function entity related to the service flow, specifically The AGW sends a resource change policy to the BS by using a data channel setup request message, or a data channel setup response message, or a data channel modification request message, or a data channel modification response message;

The policy execution network element is a BS, and when the policy execution function entity is a terminal, the policy is The execution network element provides the resource change policy of the service flow to the policy execution function entity related to the service flow, which is specifically: the BS establishes a request message through a dynamic service, or a dynamic service establishment response message, or a dynamic service modification request message, or a dynamic The service modification response message sends a resource change policy of the service flow to the terminal;

The policy execution network element is a serving BS, and when the policy execution function entity is a target BS, the policy execution network element provides a resource change policy of the service flow to the policy execution function entity related to the service flow, specifically: The serving BS provides the target BS with a resource change policy of the service flow that the user has established through the handover request message or the context information;

The policy execution network element is an anchor AGW, and when the policy execution function entity is a target anchor AGW, the policy execution network element provides a resource change policy of the service flow to the policy execution function entity related to the service flow. Specifically, the anchoring AGW provides a resource change policy of the service flow that the user has established to the target anchoring AGW by anchoring the DPF switching request message.

After the providing the policy execution function entity related to the service flow, the policy execution function entity further operates the corresponding service flow according to the resource change policy of the service flow.

The resource change policy is a resource change policy parameter that includes a related flag, and the resource flow policy according to the service flow operates on the corresponding service flow, including:

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is valid, the resource of the corresponding service flow is allowed to be modified, and the resource modification of the service flow can be initiated actively according to the actual consumption of the local resource, or performed in other policies. When the functional entity initiates the resource of the service flow ^ 爹 'tampering process, accepting the resource of the service flow ^ 爹 ' tampering;

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is invalid, the resource of the corresponding service flow is not allowed to be modified, the resource modification of the service flow is not initiated, or the service entity of the other policy execution function initiates the service flow. When the resource modification process is performed, the resource modification of the service flow is rejected; If the "Allow Service Flow Resource Delete" flag of the "Resource Change Policy" parameter is valid, the resource of the corresponding service flow is allowed to be deleted, and the resource deletion of the service flow can be initiated actively according to the actual consumption of the local resource, or executed in other policies. When the function entity initiates the resource deletion process of the service flow, the resource of the service flow is deleted;

If the "Allow Service Flow Resource Delete" flag of the "Resource Change Policy" parameter is invalid, the resource of the corresponding service flow is not allowed to be deleted, the resource deletion of the service flow is not initiated, or the service entity of the other policy execution function initiates the service flow. When the resource deletion process, the resource deletion of the service flow is rejected.

The "resource change policy" parameter is implemented by setting parameters of an existing message.

A resource control system, the system includes: a policy execution network element and a policy execution function entity, where

The policy enforcement network element is configured to provide a resource change policy of the service flow to each policy execution function entity related to the corresponding service flow;

The policy enforcement function entity is configured to receive and store a resource change policy of the service flow.

The policy enforcement network element is further configured to configure a resource change policy of the service flow; or the system further includes: an AAA server/policy server, a resource change policy for authorizing the network element to the service execution network flow.

The policy enforcement function entity is further configured to: operate the corresponding service flow according to the resource change policy of the service flow.

In the solution of the present invention, the policy execution network element provides a resource change policy of the service flow to each policy execution function entity related to the corresponding service flow, so that each policy execution function entity can clearly know which operations are possible according to the resource change policy. And which operations are not allowed; and, since each of the policy execution function entities related to the service flow can obtain the resource change policy of the service flow, the operations that each policy execution function entity can perform for the same service flow are unified. To minimize the same business flow allowed on different policy enforcement functional entities The inconsistent operation occurs, and the resources of the service flow can be precisely controlled, so that the terminal can normally reside in the WiMAX network. DRAWINGS

Figure 1 is a schematic diagram of a WiMAX network framework;

2A is a schematic diagram 1 of the internal structure of the ASN;

2B is a schematic diagram 2 of the internal structure of the ASN;

FIG. 3A is a schematic diagram of a process of establishing a preliminary service flow;

FIG. 3B is a schematic diagram of a process of establishing a dynamic service flow initiated by an existing terminal;

4 is a schematic flowchart of a process for sending a resource change policy in an initial access according to the present invention; FIG. 5 is a schematic flowchart of a policy for a AAA active authorization resource change in the present invention; FIG. 6 is a schematic flowchart of a process for creating a preliminary service flow according to the present invention;

7 is a schematic flowchart of a dynamic service flow creation initiated by a terminal side in the present invention;

FIG. 8 is a schematic flowchart of modifying a service flow initiated by a network side according to the present invention;

9 is a schematic diagram of an ASN anchoring switching process in the present invention;

10 is a schematic diagram of an uncontrolled ASN anchor switching process in the present invention;

11 is a schematic diagram of a CSN anchoring switching process in the present invention;

12 is a schematic diagram of content of a Radius message including a resource change policy according to the present invention; and FIG. 13 is a schematic structural diagram of a system for implementing resource control in the present invention. detailed description

In the present invention, the policy enforcement network element provides a resource change policy of the service flow to each policy execution function entity associated with the corresponding service flow; the resource change policy of the service flow may be from an AAA server or a policy server, ie, an AAA server or policy. The server changes the resource change policy of the service flow to the policy execution network element; the resource change policy of the service flow may also be configured by the policy execution network element itself. The policy enforcement network element may be an AGW or a BS; the policy execution function entity Can be AGW, or BS, or terminal. In this way, the operation of the service execution function entity on the service flow will be completely performed according to the resource change policy of the corresponding service flow, thereby realizing precise control of the resources of the service flow. The policy enforcement network element can configure the resource change policy of the service flow according to the overall policy, or the service type, or the service flow.

The following is a detailed description of the specific implementation of the related process of the present invention by taking the resource change policy of the AAA server built in the policy server and transmitting the service flow based on the Radius protocol as an example. In a practical application, a resource change policy of a service flow, such as a Diameter protocol, may be delivered based on other types of protocols. In practice, there may also be a dedicated policy server and a specific protocol.

4 is a schematic diagram of a process for sending a resource change policy in an initial access manner according to the present invention. As shown in FIG. 4, a specific process for delivering a resource change policy in an initial access process of a terminal includes:

Step 401: The terminal enters the WiMAX network and initiates an initial access procedure.

Step 402: After the initial access authentication of the terminal is successful, the AAA server notifies the AGW that the authentication is successful through the Access Accept message, and the related 4 authorized parameters are also sent to the AGW through the Access Accept message. The related authorization parameters include preliminary service flow parameters, the preliminary service flow parameters contain information of one or more preliminary service flows, and further include resource change policies for each of the preliminary service flows. The Access Accept message may be based on the Radius protocol. After receiving the Access Accept message, the AGW obtains the resource change policy and stores it.

The resource change policy may be a "resource change policy" parameter including a related flag, and the specific content may be:

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is valid, it indicates that the AGW is allowed to modify the resource of the corresponding service flow, and the AGW can initiate the resource modification of the service flow according to the actual actual resource consumption situation, or When the terminal or the BS initiates the resource modification process of the service flow, the AGW accepts the resource modification of the service flow;

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is invalid, then It is indicated that the AGW does not modify the resources of the corresponding service flow, and the AGW does not initiate the resource modification of the service flow. When the terminal or the BS initiates the resource modification process of the service flow, the AGW rejects the resource of the service flow. ;

If the "Allow Service Flow Resource Deletion" flag of the "Resource Change Policy" parameter is valid, it indicates that the AGW is allowed to delete the resource of the corresponding service flow, and the AGW can initiate the resource deletion of the service flow according to the actual actual resource consumption situation, or When the terminal or the BS initiates the resource deletion process of the service flow, the AGW accepts the resource deletion of the service flow;

If the "Allow Service Flow Resource Delete" flag of the "Resource Change Policy" parameter is invalid, it indicates that the AGW is not allowed to delete the resource of the corresponding service flow, and the AGW does not initiate the resource deletion of the service flow, or initiates the call at the terminal or the BS. When the service stream deletes the process, the AGW rejects the resource deletion of the service flow.

In addition, the AAA server can also indicate that the resource change policy is not allowed to modify or delete the resources corresponding to the preliminary service flow by not issuing the "resource change policy" parameter.

Step 403: After the registration is completed, the AGW initiates an initial service flow, that is, a process of establishing a preliminary service flow, and sends a resource change policy of the relevant preliminary service flow to the BS and the terminal. The specific transmission process of the resource change policy can be seen in FIG. 6.

FIG. 5 is a schematic flowchart of a AAA active authorization resource change policy according to the present invention. As shown in FIG. 5, the specific process of the AAA active authorization resource change policy includes:

Step 501: The terminal enters the WiMAX network successfully, that is, the terminal initially accesses the WiMAX network to complete.

Step 502: Before the user quits the network, the AAA server changes the resource change policy of the preliminary service flow, and notifies the AGW of the new resource change policy by using a grant change (CoA) message, where the CoA message includes the preliminary service flow parameter, and the preliminary service flow. The parameters contain information of one or more preliminary traffic flows and further include resource change policies for each of the preliminary traffic flows. The CoA message can be based on the Radius protocol. After receiving the CoA message, the AGW obtains the resource change policy and Storage.

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is invalid, it indicates that the AGW is not allowed to modify the resource of the corresponding service flow, and the AGW does not actively initiate resource modification of the service flow, or initiates the call at the terminal or the BS. When the resource flow of the service flow is modified, the AGW rejects the resource of the service flow;

In addition, the AAA server can also indicate that the new resource change policy does not allow modification or deletion of resources corresponding to the preliminary service flow by not issuing the "resource change policy" parameter.

Step 503: The AGW initiates an authorization modification process of the preliminary service flow, and sends the resource change policy of the related standby service flow to the BS and the terminal. The specific transmission process of the resource change policy can be seen in FIG. 8.

6 is a schematic flowchart of creating a preliminary service flow in the present invention, as shown in FIG. The specific process of the resource change policy in the process of creating a preliminary service flow includes:

Step 601: The terminal enters the WiMAX network, initiates an initial access procedure, and after the access succeeds, initiates a preparatory service flow establishment process. At this time, the AGW sends a data channel establishment request (Path_Reg_Req) message to the BS, where the Path_Reg_Req message is included. There is a resource change strategy corresponding to the preliminary service flow. The AGW can indicate that the resource change policy is not allowed to modify or delete resources corresponding to the preliminary service flow by not issuing the "resource change policy" parameter. The resource change policy that the AGW sends to the BS comes from the AAA server.

Step 602: After receiving the Path_Reg_Req message, the BS obtains the resource change policy and stores it, and sends a DSA_REQ message to the terminal, where the DSA_REQ message includes a resource change policy corresponding to the preliminary service flow. If the AGW does not issue the resource change policy parameter, the BS may also indicate that the resource change policy is not allowed to modify or delete the resource corresponding to the preliminary service flow by not issuing the "resource change policy" parameter.

The resource change policy acquired by the BS may be a "resource change policy" parameter including a related flag, and the specific content may be:

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is valid, it indicates that the BS is allowed to modify the resource of the corresponding service flow, and the BS may initiate the resource modification of the service flow according to the actual actual resource consumption situation, or When the terminal or the AGW initiates the resource modification process of the service flow, the BS accepts the resource modification of the service flow;

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is invalid, it indicates that the BS is not allowed to modify the resource of the corresponding service flow, and the BS does not initiate the resource modification of the service flow, or initiates the call at the terminal or the AGW. When the resource flow of the service flow is modified, the BS rejects the resource of the service flow.

If the "Allow Service Flow Resource Deletion" flag of the "Resource Change Policy" parameter is valid, it indicates that the BS is allowed to delete the resource of the corresponding service flow, and the BS may initiate the resource deletion of the service flow according to the actual actual resource consumption situation, or Initiating the service flow at the terminal or AGW When the resource is deleted, the BS accepts the resource deletion of the service flow;

If the "Allow Service Flow Resource Delete" flag of the "Resource Change Policy" parameter is invalid, it indicates that the BS is not allowed to delete the resource of the corresponding service flow, and the BS does not initiate the resource deletion of the service flow, or initiates the resource at the terminal or the AGW. When the service stream deletes the process, the BS rejects the resource deletion of the service flow;

If the BS does not receive the "Resource Change Policy" parameter, it indicates that the BS is not allowed to modify or delete the resources corresponding to the preliminary service flow.

Step 603: After receiving the DSA_REQ message, the terminal acquires the resource change policy and stores it, allocates resources for the corresponding preliminary service flow, and then sends a DSA_RSP message to the BS. The number, the specific content can be:

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is valid, it indicates that the terminal is allowed to modify the resource of the corresponding service flow, and the terminal may initiate the resource modification of the service flow according to the actual actual resource consumption situation, or When the network side, such as a BS or an AGW, initiates a resource modification process of the service flow, the terminal accepts resource modification of the service flow;

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is invalid, it indicates that the terminal is not allowed to modify the resource of the corresponding service flow, and the terminal does not initiate the resource modification of the service flow, or initiates the service on the network side. When the flow of the resource is modified, the terminal rejects the resource modification of the service flow;

If the "Allow Service Flow Resource Deletion" flag of the "Resource Change Policy" parameter is valid, it indicates that the terminal is allowed to delete the resource of the corresponding service flow, and the terminal may initiate the resource deletion of the service flow according to the actual actual resource consumption situation, or When the network side initiates the resource deletion process of the service flow, the terminal accepts the resource deletion of the service flow;

If the "Allow Service Flow Resource Delete" flag of the "Resource Change Policy" parameter is invalid, it indicates that the terminal is not allowed to delete the resource of the corresponding service flow, and the terminal does not initiate the service flow. When the resource is deleted, or the resource deletion process of the service flow is initiated on the network side, the terminal rejects the resource deletion of the service flow;

If the terminal does not receive the "resource change policy" parameter, it indicates that the terminal is not allowed to modify or delete the resources corresponding to the preliminary service flow.

Step 604~Step 606: After receiving the DSA_RSP message, the BS allocates resources for the corresponding preliminary service flow, and sends a Data Channel Setup Response (Path_Reg_Rsp) message to the AGW. After receiving the Path_Reg_Rsp message, the AGW sends a Data Channel Setup Acknowledge (Path_Reg_Ack) message to the BS to confirm that the data channel setup is complete. After receiving the Path_Reg_Ack message, the BS sends a DS A_ACK message to the terminal to confirm that the data channel is established.

In addition, the network side actively initiates the process of creating a dynamic service flow. See also FIG. 6. Step 601 is specifically as follows: After the terminal successfully accesses the WiMAX network, the upper application server is ready to perform a certain service application, and the network side, such as the AGW, initiates a dynamic service. The flow establishing process, at this time, the AGW sends a Path_Reg_Req message to the BS, where the Path_Reg_Req message includes a resource change policy corresponding to the dynamic service flow. The AGW can indicate that the resource change policy is not allowed to modify or delete the resources of the corresponding dynamic service flow by not issuing the "resource change policy" parameter. The resource change policy that the AGW sends to the BS may come from the AAA server or the AGW itself. The remaining steps are basically the same as the above description, except that the resource change policy is directed to the dynamic service flow, and therefore will not be described again.

FIG. 7 is a schematic diagram of a process of creating a dynamic service flow initiated by a terminal side according to the present invention. As shown in FIG. 7, the specific process of the dynamic service flow creation and the resource change policy is initiated by the terminal side. Step 701 to step 702: The terminal is in the user. During a session, a temporary data service is prepared, a dynamic service flow creation process is initiated, and a DSA_REQ message is sent to the BS. After receiving the DSA_REQ message, the BS sends a Path_Reg_Req message to the AGW.

Step 703: After receiving the Path_Reg_Req message, the AGW allocates a resource for the corresponding dynamic service flow, and sends a Path_Reg_Rsp message to the BS, where the Path_Reg_Rsp message includes the corresponding action. Resource change strategy for stateful traffic. The AGW can indicate that the resource change policy is not allowed to modify or delete the resources of the corresponding dynamic service flow by not issuing the "resource change policy" parameter. The resource change policy sent by the AGW to the BS comes from the AAA server, or it can be configured by the AGW itself.

Step 704: After receiving the Path_Reg_Rsp message, the BS obtains the resource change policy and stores it; allocates a resource for the corresponding dynamic service flow, and sends a DSA_RSP message to the terminal, where the DSA_RSP message includes a resource change policy corresponding to the dynamic service flow. If the AGW does not issue the "Resource Change Policy" parameter, the BS may also indicate that the resource change policy is not allowed to modify or delete the resource corresponding to the dynamic service flow by not issuing the "Resource Change Policy" parameter.

The resource change policy acquired by the BS may be a "resource change policy" parameter including a related flag. For details, refer to the description in FIG. 6. If the BS does not receive the "resource change policy" parameter, it indicates that the BS is not allowed to modify or delete the corresponding dynamic. The resources of the business flow.

Step 705: After receiving the DSA_RSP message, the terminal acquires the resource change policy and stores it; allocates resources for the corresponding dynamic service flow, and sends a DSA_ACK message to the BS to confirm that the data channel is established. For details, refer to the description in Figure 6. If the terminal does not receive the "Resource Change Policy" parameter, it indicates that the terminal is not allowed to modify or delete the resources of the corresponding dynamic service flow.

Step 706: After receiving the DSA_ACK message, the BS sends a Path_Reg_Ack message to the AGW to confirm that the data channel establishment is completed.

If the BS initiates a dynamic service flow creation process, the process starts from step 702, and details are not described herein.

FIG. 8 is a schematic diagram of a process of modifying a service flow initiated by a network side according to the present invention. As shown in FIG. 8, the specific process of the resource change policy delivered by the network side to initiate a service flow modification process includes:

Step 801: After the terminal enters the WiMAX network, the AAA server modifies the resource change policy of the service flow, and sends the policy to the AGW. The AGW initiates the service flow modification process. The BS sends a data channel modification request (Path_Modify_Req) message, and the Path_Modify_Req message includes a resource change policy corresponding to the service flow. The AGW can indicate that the resource change policy is not allowed to modify or delete the resources of the corresponding service flow by not issuing the "resource change policy" parameter. The resource change policy sent by the AGW to the BS may also be configured by the AGW itself.

Step 802: After receiving the Path_Modify_Req message, the BS obtains the resource change policy and stores it, and updates the resource change policy of the corresponding service flow to the resource change policy currently sent by the AGW; and sends a dynamic service modification request (DSC_REQ) message to the terminal. The DSC_REQ message contains a resource change policy corresponding to the service flow. If the AGW does not issue the resource change policy parameter, the BS can also indicate that the resource change policy is not allowed to modify or delete the resource of the corresponding service flow by not issuing the resource change policy parameter.

The resource change policy obtained by the BS may be a "resource change policy" parameter including a related flag. For details, refer to the description in FIG. 6. If the BS does not receive the "resource change policy" parameter, it indicates that the BS is not allowed to modify or delete the corresponding service. Streaming resources.

Step 803: After receiving the DSC_REQ message, the terminal acquires the resource change policy and stores it, that is, the resource change policy of the corresponding service flow is updated to the resource change policy currently delivered by the BS; and allocates resources for the corresponding reserved service flow, and then sends the dynamic to the BS. Service Modification Response (DSC_RSP) message. For details, refer to the description in Figure 6. If the terminal does not receive the "Resource Change Policy" parameter, it indicates that the terminal is not allowed to modify or delete the resources of the corresponding service flow.

Step 804 to step 806: After receiving the DSC_RSP message, the BS allocates resources for the corresponding preliminary service flow, and sends a data channel modification response (Path_Modify_Rsp) message to the AGW. After receiving the Path_Modify_Rs message, the AGW sends a Data Channel Modification Reply (Path_Modify_Ack) message to the BS to confirm that the data channel establishment is complete. After receiving the Path_Modify_Ack message, the BS sends a dynamic service modification response (DSC_ACK) to the terminal. Information to confirm that the data channel is established.

The terminal side may also initiate a service flow modification process, in which the message involved is unchanged, but the flow direction is opposite to that of FIG. 8. For details, refer to FIG. 7.

The foregoing process is a description in which the policy execution network element is the AGW, the policy execution function entity is the BS, or the policy execution network element is the BS, and the policy execution function entity is the terminal. In addition, the policy execution network element and the policy enforcement function entity may also be the AGW. The AGW as the policy enforcement network element and the AGW as the policy execution function entity may be the same AGW or different AGWs. When the AGW as the policy enforcement network element and the AGW as the policy enforcement entity are different AGWs, the processing is as follows: the SFA (Service Flow Authorization) logical entity in the AGW as the policy enforcement network element passes the resource pre- The Leave Request message notifies the resource change policy to the Anchored Data Channel Function (DPF) logical entity in the AGW as the Policy Enforcement Function Entity.

9 is a schematic diagram of an ASN anchor handover procedure in the present invention. The ASN anchor handover refers to: The user's anchor ASN does not change during the handover process. As shown in FIG. 9, the user established service in the ASN anchor handover process. The specific process of stream resource change policy delivery includes:

Step 901 ~ Step 902: The terminal has accessed the WiM AX network, and is ready to perform the handover operation. The terminal sends a mobile request message to the serving BS, where the mobile request message includes information of one or more potential target BSs, where the potential target BS is a BS that the terminal may perform handover, where the plurality of potential target BSs are the target BS1 and Target BS2.

Step 903 to step 904: After receiving the mobile request message, the serving BS sends a handover request message to each potential target BS in parallel, where the handover request message includes a resource change policy of the service flow that the user has established, that is, the service BS moves to the target. The BS1 sends a handover request message, where the handover request message includes a resource change policy of the service flow that the user has established; the service BS also sends a handover request message to the target BS2, where the handover request message includes the service flow that the user has established. Resource change strategy. After receiving the handover request message, each target BS acquires the service flow that the user has established. The resource change policy is stored and stored, that is, after the target BS1 and the target BS2 receive the handover request message, the resource change policy of the service flow that the user has established is obtained and stored.

Step 905~Step 906: The target BS1 and the target BS2 perform a key context acquisition process. The target BS1 or the target BS2 can also be delayed until the handover execution phase to obtain the key context.

Step 907 to step 908: The target BS1 and the target BS2 obtain the context information, that is, the pre-establishment of the data channel can be initiated to the anchor ASN, and the channel pre-registration process is performed with the anchor ASN. The target BS1 or the target BS2 can also be delayed to the handover execution phase before channel pre-registration.

Step 909 to step 910: The target BS1 and the target BS2 respond to the serving BS with a handover response message and accept the handover request.

Step 911: The serving BS sends a mobile response message to the terminal, carrying one or more potential target BSs selected by the WiMAX network.

Step 912 to step 913: The serving BS sends a handover response message to each potential target BS in parallel.

The above is an example of the ASN anchoring handover process initiated by the terminal, which illustrates that the resource change strategy is

The ASN anchors the transfer to the target BS in the handover procedure. Correspondingly, the ASN anchor handover procedure can also be initiated by the serving BS. The ASN anchor handover procedure initiated by the serving BS is basically the same as the procedure shown in FIG. 9, and therefore will not be described in detail.

10 is a schematic diagram of an uncontrolled ASN anchoring handover process in the present invention. The uncontrolled ASN anchoring handover means that the user does not prepare for handover to the target BS, but initiates handover directly at the target BS, as shown in FIG. 10, The specific process of resource change policy delivery of the service flow that the user has established in the controlled ASN anchor handover process includes:

Step A01~Step A02: The terminal has accessed the WiMAX network and starts the switching operation. The terminal transmits a ranging request message to the target BS to perform an uncontrolled handover procedure.

Step A03: After receiving the ranging request message, the target BS requests the user context from the serving BS. Information, the serving BS responds to the target BS with context information, where the context information includes a resource change policy of the service flow that the user has established. After receiving the context information, the target BS acquires a resource change policy of the service flow that the user has established and stores.

Step A04: The target BS performs a key context acquisition process with the AGW with the authenticator. Step A05: The target BS performs data channel registration with the AGW having the anchor data channel. Step A06: The target BS sends a ranging response message to the terminal.

Step A07: The serving BS and the AGW continue to perform the user switching process.

FIG. 11 is a schematic diagram of a CSN anchoring handover process according to the present invention. The CSN anchoring handover refers to: a user handover causes an anchor AGW to be changed. As shown in FIG. 11, the CSN anchor handover process is a resource of a service flow that the user has established. The specific process of changing policy delivery includes:

Step B01: Target Anchoring When the AGW actively initiates a CSN anchor handover, the target anchor AGW sends an anchor DPF handover trigger message to the anchor AGW. If the anchor AGW initiates a CSN anchor handover, the step is not performed, and step B02 is directly executed.

Step B02: The anchor AGW sends an anchor DPF handover request message to the target anchor AGW, where the anchor DPF handover request message includes a resource change policy of the service flow that the user has established. Target Anchoring After receiving the anchor DPF switch request message, the AGW obtains the resource change policy of the service flow that the user has established and stores it.

Step B03: Continue the CSN anchor handover procedure in the prior art.

In order to make the drawings concise and concise, the above-mentioned drawings neglect the forwarding network elements that have no effect on the transmission of key parameters. In practice, these forwarding network elements may exist, and are not related to the inventive scheme. In addition, when the terminal roams, the transmission of the resource change policy may require the participation of the AAA proxy and other related network elements, but this does not affect the implementation essence of the solution of the present invention.

The resource change policy can be included by extending the existing message. For example, based on the Radius protocol and the NWG protocol, the resource change policy parameter can be set in the Radius message, and FIG. 12 shows the resource change policy (Resource-Policy) parameter. Radius vendor-defined attributes The content of the Radius VSA, Radius Vender Specific Attribute can be defined as follows: bitO indicates that the resource of the service flow is allowed to be modified, and bitl indicates the resource that allows the service flow to be deleted. These values can be valid at the same time. . The vendor described in Radius VSA refers to WiMAX.

The above is just an example of the Radius protocol. A resource change policy is implemented. This definition can also be applied to any other protocol. For example, if the Diameter protocol is used between the AGW and the AAA server, the resource changes the policy parameters. The same applies to the setting and definition.

FIG. 13 is a schematic structural diagram of a system for implementing resource control according to the present invention. As shown in FIG. 13, the system includes a policy execution network element and a policy execution function entity, where the policy execution network element is used to provide a resource change policy for a service flow. Each of the policy execution function entities associated with the corresponding service flow is used by the policy execution function entity to receive and store the resource change policy of the service flow.

The system further includes: an AAA server/policy server, a resource change policy for authorizing the network element to the service execution network flow. The AAA Server/Policy Server can be further used to make changes to the resource change policy of the traffic flow.

The policy enforcement network element is further configured to configure a resource change policy of the service flow. The policy enforcement network element can configure the resource change policy of the service flow according to the overall policy, or the type of service, or the service flow.

The policy enforcement function entity is further configured to operate on the corresponding service flow according to the resource change policy of the service flow.

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is valid, and the resource corresponding to the service flow is allowed to be modified, the resource modification of the service flow may be initiated according to the actual actual resource consumption situation, or may be performed in other policies. The functional entity initiates the flow of the service flow When the source ^ ί' tampering with the process, the resource of the service flow is accepted ^ 爹 'tampering;

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is invalid, the resource of the corresponding service flow is not allowed to be modified, the resource modification of the service flow is not initiated, or the service flow is initiated by another policy execution function entity. When the resource modification process, the resource modification of the service flow is rejected;

If the "Allow Service Flow Resource Delete" flag of the "Resource Change Policy" parameter is valid, the resource of the corresponding service flow is allowed to be deleted, and the resource deletion of the service flow may be initiated according to the actual actual resource consumption of the local resource, or performed in other policies. When the function entity initiates the resource deletion process of the service flow, the resource of the service flow is deleted;

If the "Allow Service Flow Resource Delete" flag of the "Resource Change Policy" parameter is invalid, the resource of the corresponding service flow is not allowed to be deleted, the resource deletion of the service flow is not initiated, or the service flow is initiated by another policy execution function entity. When the resource deletion process, the resource of the service flow is rejected.

The policy enforcement network element may be an AGW or a BS; the policy enforcement function entity may be an AGW, or a BS, or a terminal.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for resource control, the terminal accessing in a microwave access global interworking (WiMAX) network, wherein the method comprises:

The method according to claim 1, wherein the policy execution network element provides the resource change policy of the service flow to each of the policy execution function entities related to the corresponding service flow, and further includes:

The method according to claim 2, wherein when the policy execution network element is connected to an service network gateway (AGW),

The resource change policy of the AAA server or the policy server to authorize the network element to the service execution network element, specifically:

After the initial access authentication of the terminal is successful, the AAA server or the policy server sends a resource change policy of the service flow to the AGW by accessing the acceptance message; or

4. The method of claim 1 wherein:

The policy execution network element is an AGW, and when the policy execution function entity is also an AGW, the policy execution network element provides a resource change policy of the service flow to the policy execution function entity related to the service flow, specifically: The anchored traffic flow authorization (SFA) logical entity in the AGW of the policy enforcement network element notifies the resource change policy to the anchor data channel function (DPF) logical entity in the AGW as the policy enforcement function entity through the resource reservation request message; The policy execution network element is an AGW, and when the policy execution function entity is a base station (BS), the policy execution network element provides a resource change policy of the service flow to the policy execution function entity related to the service flow, specifically The AGW sends a resource change policy to the BS by using a data channel setup request message, or a data channel setup response message, or a data channel modification request message, or a data channel modification response message;

The policy execution network element is a BS, and when the policy execution function entity is a terminal, the policy execution network element provides a resource change policy of the service flow to the policy execution function entity related to the service flow, which is specifically: The dynamic service establishment request message, or the dynamic service establishment response message, or the dynamic service modification request message, or the dynamic service modification response message sends a resource change policy of the service flow to the terminal;

The policy execution network element is a service BS, and when the policy execution function entity is a target BS, the policy execution network element provides a resource change policy of the service flow to the policy execution function entity related to the service flow, specifically: The serving BS provides the target BS with a resource change policy of the service flow that the user has established through the handover request message or the context information;

The method according to any one of claims 1 to 4, wherein after the providing each of the policy execution function entities related to the service flow, the method further comprises: the policy execution function entity according to the resource of the service flow Change the policy to operate on the corresponding business flow.

The method according to claim 5, wherein the resource change policy is a resource change policy parameter that includes a related flag, and the resource change policy according to the service flow operates the corresponding service flow, including:

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is valid, Modifying the resource corresponding to the service flow, and actively initiating the resource modification of the service flow according to the actual actual resource consumption situation, or accepting the resource when the other policy execution function entity initiates the resource 爹 tampering process of the service flow Business stream resources ^ ί 'tamper;

If the "Allow Service Flow Resource Modification" flag of the "Resource Change Policy" parameter is invalid, the resource of the corresponding service flow is not allowed to be modified, the resource modification of the service flow is not initiated, or the service entity of the other policy execution function initiates the service flow. When the resource modification process is performed, the resource modification of the service flow is rejected;

If the "Allow Service Flow Resource Delete" flag of the "Resource Change Policy" parameter is valid, the resource of the corresponding service flow is allowed to be deleted, and the resource deletion of the service flow can be initiated actively according to the actual consumption of the local resource, or executed in other policies. When the function entity initiates the resource deletion process of the service flow, the resource of the service flow is deleted;

7. The method according to claim 6, wherein the "resource change policy" parameter is implemented by setting parameters of an existing message.

A resource control system, the system comprising: a policy execution network element and a policy execution function entity, where

9. The system of claim 8 wherein:

The policy enforcement network element is further configured to configure a resource change policy of the service flow; or the system further includes: an AAA server/policy server, configured to Resource change strategy for the right business flow.

The system according to claim 8 or 9, wherein the policy execution function entity is further configured to: operate the corresponding service flow according to the resource change policy of the service flow.