WO2011069390A1 - Method and system for signing consumption, consumption -based admission control method and system - Google Patents

Abstract

A method and system for signing consumption, as well as an admission control method and system based on consumption are disclosed in the present invention. Wherein, the admission control method includes: making a strategy according to the information of user consumption, and realizing admission control. In the admission control system, a making unit is used to make a strategy according to the information of user consumption; and an admission control unit is used to realize admission control according to the made strategy. The signing process of consumption can be improved by adopting the signing method and system of the present invention. The scheme for performing admission control according to the consumption-based Quality of Service (QoS) strategy is realized by adopting the admission control method and system of the present invention.

Description

 Usage signing method and system, usage-based acceptance control method and system

 The present invention relates to the field of communications, and in particular, to a usage signing method and system, and a usage-based admission control method and system. Background technique

 At present, the Next Generation Network (NGN) is a hot research topic in the field of communication standards. It uses IP packet technology as the bearer network technology and combines fixed communication and mobile communication, so that NGN can provide richer multimedia. Businesses, for example, emerging services with real-time requirements, such as IP TV, video conferencing, multimedia distance learning, video on demand, etc., all require communication networks to provide efficient end-to-end quality of service (QoS) support. At the same time, users are increasingly demanding the quality of network services. Therefore, providing end-to-end QoS is one of the core issues of NGN.

The International Telecommunication Union-Telecommunications Standardization Sector (ITU-T) is the telecommunications division of the International Telecommunication Union (ITU), which sets standards for resource admission control. In the latest draft of the Resource-Admission Control Functions (RACF) published by ITU-T, the functional framework of RACF is provided. As shown in Figure 1, the RACF consists of two parts, namely the policy decision function entity ( PD-FE, Policy Decision Functional Entity, and Transport Resource Control Functional Entity (TRC-FE), where the TRC-FE interacts with the transport function through the Rc interface, and performs a functional entity through the Rn interface and the transport resource ( TRE-FE, Transport Resource Enforcement Functional Entity), and the PD-FE interacts with the TRC-FE through the Rt interface and communicates with the Customer Premises Network (CPN) through the Rh interface. Mutually interact with the Policy Enforcement Functional Entity (PE-FE) through the Rw interface, interact with the Service Control Functions (SCF) of the service layer through the Rs interface, and control the functions through the Ru interface and the network ( NACF (Network Attachment Control Functions) interacts, and the PD-FE interacts with other next-generation networks through the Ri interface. In Figure 1, other next-generation networks are represented by NGNs.

 In addition, the PD-FE is independent of the transmission technology and has nothing to do with the SCF. The PD-FE is based on the network policy rules, the service information provided by the SCF, the transport layer subscription information provided by the NACF, and the resource availability decision result provided by the TRC-FE. The final decision on resource acceptance control.

 TRC-FE is not related to the business, but is related to transmission technology. The TRC-FE is responsible for collecting and maintaining transmission network information and resource status information. Upon receiving a resource request from the PD-FE, the TRC-FE performs resource-based admission control based on QoS, priority requirements, resource availability information, and transport-related policy rules.

 The transport layer consists of PE-FE and TRE-FE. The PE-FE implements the policy rule delivered by the PD-FE. The PE-FE is a packet-to-packet gateway. It can be located between the CPN and the access network, between the access network and the core network, or between different carrier networks. Key nodes for dynamic QoS control, port address translation control, and Network Address Translator (NAT). The TRE-FE implements the transmission resource policy rule delivered by the TRC-FE. Its scope and function and the Rn interface need to be further studied, which is not in the scope of the R2 phase.

TISPAN is a service and protocol for communication and Internet convergence of advanced networks. It is called Telecommunication and Internet converged Services and Protocols for Advanced Networking. The TISPAN protocol proposes a Resource Admission Control Subsystem (RACS) to solve NGN. Carrier QoS issues. TISPAN divides the NGN architecture into a service layer and a transport layer. At the transmission control layer, RACS and Network Attachment Subsystem (NASS) are introduced. The RACS solves the QoS problem of the NGN bearer network, while the NASS is responsible for providing the upper layer service layer. Independent user access management. The main functions of TISPAN RACS are similar to those of ITU-T RACF. The functional architecture of TISPAN RACS is shown in Figure 2. The RACS associates the resource requirements of the service layer with the resource allocation of the transport layer, and mainly performs functions such as policy control, resource reservation, admission control, and NAT traversal. The RACS provides the transport layer control service for the service layer through a series of QoS policies, so that the user equipment (UE, User Equipment) can obtain the required service quality guarantee. The following is specifically explained.

 The RACS consists of two entities: a Service-based Policy Decision Function (SPDF) and an Access-Resource and Admission Control Function (A-RACF).

 Among them, for SPDF, SPDF provides a unified interface to the application layer, shields the underlying network topology and specific access types, and provides service-based policy control. SPDF selects the local policy according to the request of the application function (AF, Application Function), and maps the request to IP QoS parameters, and sends it to A-RACF and Border Gateway Function (BGF) to control the corresponding resources.

 For A-RACF, A-RACF is located in the access network and has the function of admission control and network policy aggregation. The request is received from the SPDF, and then the admission control is implemented based on the saved policy, accepting or rejecting the request for the transmission resource. The A-RACF obtains the network attachment information and the user subscription information from the NASS through the e4 interface, so that the available network resources can be determined according to the network location information, for example, the address of the physical node of the access user, and the user subscription information is referred to when processing the resource allocation request. .

 The transport layer contains three functional entities: BGF, resource control execution function (RCEF, Resource

Control Enforcement Function ) and the Basic Transport Function ( BTF ).

For BGF, BGF is a packet-to-packet gateway, which can be located between the access network and the core network to implement the core border gateway function. The BGF can also be located between the two core networks to implement the interconnection border gateway function. . BGF completes NAT traversal, gating, QoS under the control of SPDF Tags, bandwidth limits, usage measurements, and resource synchronization.

 For RCEF, the RCEF implements the Layer 2/Layer 3 (L2/L3) media stream policy defined by the A-RACF through the Re interface to complete the functions of gating, QoS marking, and bandwidth limitation.

 In summary, it can be seen that the existing RACF architecture of ITU-T and the RACS architecture of TISPAN do not specify the process of signing the usage, and cannot support the usage-based QoS policy control when performing resource admission control. The signing process and the usage-based QoS policy implement the admission control scheme. Summary of the invention

 In view of this, the main object of the present invention is to provide a method and system for signing a quantity, and to complete the signing process of the dosage.

 Another object of the present invention is to provide a usage-based admission control method and system, and implement a revenue-based QoS policy for admission control.

 In order to achieve the above object, the technical solution of the present invention is achieved as follows:

 A method for signing usage, the method comprising:

 Signing user usage information in the user subscription database;

 User subscription data including the user usage information is actively pushed to the resource admission control platform by the network attachment platform; or, after the resource admission control platform requests the network attachment platform, and then from the network attachment platform The user subscription data including the user usage information is passively obtained.

 The user usage information is stored in the network attachment platform; the user usage information includes: information indicating a total allowable usage of the user and/or an allowable usage of the user subscription service.

Wherein, in the case of using the International Telecommunication Union (ITU-T) Resource Admission Control Function (RACF) architecture, the network attachment platform is a network attachment control function (NACF), and the resource admission control platform is a RACF; Alternatively, in the case of the communication and Internet convergence service and protocol (TISPAN) resource admission control subsystem (RACS) architecture of the advanced network, the network attachment platform is a network attachment subsystem (NASS), and the resource admission control The platform is RACS.

 A usage signing system, the system comprising: a signing unit and a sending unit; wherein, the signing unit is configured to sign user usage information in the user signing database;

 a sending unit, configured to send the user subscription data that includes the user usage information to the resource admission control platform by the network attachment platform; or, after the resource admission control platform requests the network attachment platform, The network attachment platform sends the user subscription data including the user usage information to the resource admission control platform.

 The system further includes: a saving unit, configured to save the user usage information in the network attachment platform; the user usage information includes: indicating a total allowable usage of the user and/or an allowable amount of the user subscription service information.

 A usage-based admission control method, the method comprising: formulating a policy according to user usage information, and implementing admission control.

 Wherein, in the case of using the ITU-T RACF architecture, the user usage information formulating strategy and implementing admission control includes:

 The RACF receives the resource initialization request from the service layer function (SCF) of the service layer; when the RACF does not store the user subscription data locally, the RACF interacts with the NACF and obtains the user subscription data;

 The RACF formulates a policy including the usage monitoring rule for the resource initialization request, and implements control of rejecting the access request or allowing the access request.

 The user usage information is stored in the NACF. The user usage information includes: information indicating a total allowable usage of the user and/or an allowable usage of the user subscription service.

The policy includes: a user and/or service that needs to perform usage monitoring, and a corresponding usage threshold; The control to implement the denial of access request or allow access request includes:

 When the total allowable usage of the user and/or the allowed usage of the user subscription service reaches the corresponding usage threshold, the RACF denies access to the resource initialization request; or initiates a statically configured quality of service (QoS) policy;

 Alternatively, the RACF allows access to the resource initialization request when the total allowed usage of the user and/or the allowed usage of the subscriber subscription service does not reach the corresponding usage threshold.

 After the accessing the resource initialization request is allowed, the method further includes: the RACF sending the policy to the policy enforcement function entity (PE-FE), and the PE-FE performs usage monitoring according to the policy.

 The method further includes: the PE-FE feeding back the monitoring result to the RACF;

 The PE-FE reports the usage monitoring result to the RACF when the usage of the user and/or service monitored by the usage reaches the corresponding usage threshold; or, when the PE-FE receives the user and/or service resource release request monitored by the usage After that, the usage monitoring result is reported to the RACF.

 Wherein, in the case of using the TISPAN RACS architecture, the formulating the policy according to the user usage information and implementing the admission control includes:

 The RACS receives the resource request from the application function (AF); when the RACS does not store the user subscription data locally, the RACS interacts with the NASS and obtains the user subscription data;

 The RACS formulates a policy including the usage monitoring rule for the resource request, and implements control of denying the access request or allowing the access request.

 The user usage information is stored in the NASS. The user usage information includes: information indicating a total allowed usage of the user and/or an allowed usage of the user subscription service.

 The method includes: the user and/or the service that needs to perform the quantity monitoring, and the corresponding usage threshold;

The control to implement the denial of access request or allow access request includes: When the total allowable usage of the user and/or the allowed usage of the user subscription service reaches the corresponding usage threshold, the RACS denies access to the resource request; or initiates a statically configured QoS policy; or, when the user is total The RACS allows access to the resource request when the allowed usage and/or the allowed usage of the user subscription service does not reach the corresponding usage threshold.

 After the request is allowed to access the resource request, the method further includes: the RACS sending the policy to the transmission function entity, and the transmission function entity performs usage monitoring according to the policy.

 The method further includes: the transmitting function entity feeding back the monitoring result to the RACS;

 When the usage of the user and/or service monitored by the usage reaches the corresponding usage threshold, the transmission function entity reports the usage monitoring result to the RACS; or, when the transmission function entity receives the user and/or service resource release request monitored by the usage After that, the usage monitoring result is reported to the RACS;

 The transport function entity includes: a resource control execution function (RCEF) and/or a border gateway function (BGF).

 A usage-based admission control system, the system comprising: a formulation unit, and an admission control unit; wherein

 a unit for formulating a strategy based on user usage information;

 Admission control unit for implementing admission control in accordance with established policies.

 Wherein, in the case of using the ITU-T RACF architecture, the admission control unit is further configured to receive a resource initialization request from the SCF by the RACF; when the RACF does not store the user subscription data locally, the RACF interacts with the NACF and obtains the user. The subscription data; the RACF formulates a policy including the usage monitoring rule for the resource initialization request, and implements the control of denying the access request or allowing the access request.

 The policy includes: a user and/or a service that needs to perform usage monitoring, and a corresponding usage threshold;

The admission control unit is further configured to: when the user is allowed to use the total amount and/or the user When the allowed usage of the service reaches the corresponding usage threshold, the RACF refuses to access the resource initialization request; or initiates a statically configured QoS policy; or the admission control unit is further used when the user always allows The RACF allows access to the resource initialization request when the usage and/or the allowed usage of the user subscription service does not reach the corresponding usage threshold;

 The system further includes: a usage monitoring unit, configured to allow the access to the resource initialization request, the RACF sends the policy to the PE-FE, and the PE-FE performs usage monitoring according to the policy.

 Wherein, in the case of using the TISPAN RACS architecture, the admission control unit is further configured to receive the resource request from the AF by the RACS; when the RACS does not store the user subscription data locally, the RACS interacts with the NASS and obtains the user subscription data; The RACS formulates a policy including the usage monitoring rule for the resource request, and implements control of denying the access request or allowing the access request.

 The policy includes: a user and/or a service that needs to perform usage monitoring, and a corresponding usage threshold;

 The admission control unit is further configured to: when the total allowed usage of the user and/or the allowed usage of the user subscription service reaches a corresponding usage threshold, the RACS refuses to access the resource request; or initiates static configured QoS. Or the admission control unit is further configured to: when the total allowed usage of the user and/or the allowed usage of the user subscription service does not reach the corresponding usage threshold, the RACS allows access to the resource request;

 The system further includes: a usage monitoring unit, configured to allow the access to the resource request, the RACS sends the policy to the transmission function entity, and the transmission function entity performs usage monitoring according to the policy.

The invention introduces user usage information, and signs user usage information in the user subscription database. The user subscription data including the user usage information is actively pushed to the resource admission control platform by the network attachment platform; or, after the resource admission control platform requests the network attachment platform, the user usage amount is passively obtained from the network attachment platform. User subscription data for information. By using the invention, the signing process of the dosage is improved. The invention formulates a strategy based on user usage information and implements admission control. By using the invention, the strategy is formulated according to the user usage information, and the admission control is implemented according to the formulated strategy. The usage-based admission control scheme is realized by using different policy controls for different usages. DRAWINGS

 1 is a schematic diagram of a functional framework of a RACF in the prior art;

 2 is a schematic diagram of a functional framework of a RACS in the prior art;

 3 is a schematic diagram of an implementation flow of an example 1 of the present invention;

 4 is a schematic flowchart of an implementation process of Example 2 of the present invention;

 FIG. 5 is a schematic diagram of an implementation process of Example 3 of the present invention; FIG.

 FIG. 6 is a schematic diagram of an implementation process of the fourth embodiment of the present invention. detailed description

 The basic idea of the present invention is: Introduce user usage information, and sign user usage information in the user subscription database. The user subscription data of the user usage information is forwarded to the resource admission control platform by the network attachment platform. Alternatively, after the resource admission control platform requests, the user subscription data including the user usage information is passively obtained from the network attachment platform.

 Develop policies based on user usage information and implement admission control.

 The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings.

 A usage signing method, the method comprising the following steps:

 Step 101: Sign the user usage information in the user subscription database.

 Here, the user usage information is saved in the network attachment platform. The user usage information includes: information indicating the total allowable usage of the user and/or the allowable usage of the user's contracted service.

 Step 102: The user subscription data including the user usage information is actively pushed to the resource admission control platform by the network attachment platform.

Alternatively, step 102 may be: requesting, by the resource admission control platform, the network attachment platform After that, the user subscription data including the user usage information is passively obtained from the network attachment platform. Here, a case: In the case of using the ITU-T RACF architecture, the network attachment platform is specifically NACF, and the resource admission control platform is specifically RACF; or, another case: in the case of using the TISPAN RACS architecture, the network attachment The platform is specifically NASS, and the resource admission control platform is specifically RACS.

 A usage-based admission control method, the method comprising: formulating a policy according to user usage information, and implementing admission control.

 Here, the operation of formulating the policy according to the user usage information and implementing the admission control may be implemented by the resource admission control platform. One case: In the case of using the ITU-T RACF architecture, the resource admission control platform is specifically RACF; or, another Case: In the case of the TISPAN RACS architecture, the resource admission control platform is specifically RACS. In this way, it is possible to clarify different usages and use different policy controls to achieve a usage-based admission control scheme.

 The specific implementation of the method differs in the case of different protocol architectures, and is therefore described separately below.

 Case 1: The case of the ITU-T RACF architecture.

 At this point, the specific process of formulating policies based on user usage information and implementing admission control includes the following steps:

 Step 1121a, the RACF receives a resource initialization request from the SCF.

 Step 1122a: When the RACF does not store the user subscription data locally, the RACF interacts with the NACF and obtains the user subscription data.

 Here, the user usage information is saved in the NACF. The RACF interacts with the NACF and obtains the user subscription data. The NACF includes the user subscription data including the user usage information and actively sends it to the RACF. Alternatively, after the RACF requests the NACF, the RACF passively obtains the user usage information from the NACF. User subscription data.

The user usage information includes: characterizing the total allowable usage of the user and/or the user subscription service. The amount of information allowed.

 Step 1123a: The RACF formulates a policy including a usage monitoring rule for the resource initialization request, and implements control of denying the access request or allowing the access request.

 Here, the strategies developed include: Users and/or businesses that need to monitor usage, and the corresponding usage threshold.

 Here, the specific processing procedure of the step 1123a includes: when the total allowed usage of the user and/or the allowed usage of the user subscription service reaches the corresponding usage threshold, the RACF refuses to access the resource initialization request; or starts the statically configured QoS policy.

 Alternatively, the specific processing procedure of step 1123a includes: when the total allowed usage of the user and/or the allowed usage of the subscription service of the user does not reach the corresponding usage threshold, the RACF allows access to the resource initialization request.

 Here, after the access resource initialization request is allowed, the method further includes: the RACF sends the policy to the PE-FE, and the PE-FE performs usage monitoring according to the policy.

 Here, the method further includes: the PE-FE feeding back the monitoring result to the RACF.

 The PE-FE reports the usage monitoring result to the RACF when the usage of the user and/or service monitored by the usage reaches the corresponding usage threshold; or, when the PE-FE receives the monitored user and/or service resources After the request is released, the usage monitoring result is reported to the RACF.

 Case 2: Using the TISPAN RACS architecture.

 At this point, the specific process of formulating policies based on user usage information and implementing admission control includes the following steps:

 Step 1121b, the RACS receives a resource request from the AF.

 Step 1122b: When the RACS does not store the user subscription data locally, the RACS interacts with the NASS and obtains the user subscription data.

Here, the user usage information is saved in the NASS. The interaction between the RACS and the NASS and obtaining the user subscription data specifically includes: NASS will sign the user subscription data containing the user usage information, and actively Pushing to the RACS; or, after the RACS requests the NASS, the user subscription data including the user usage information is passively obtained from the NASS.

 The user usage information includes: information indicating the total allowable usage of the user and/or the allowable usage of the user's subscription service.

 Step 1123b: The RACS formulates a policy including a usage monitoring rule for the resource request, and implements control of denying the access request or allowing the access request.

 Here, the strategies developed include: Users and/or businesses that need to monitor usage, and the corresponding usage threshold.

 Here, the specific processing procedure of step 1123b includes: when the total allowed usage of the user and/or the allowed usage of the user subscription service reaches the corresponding usage threshold, the RACS denies access to the resource request; or starts a statically configured QoS policy.

 Alternatively, the specific processing procedure of step 1123b includes: when the total allowed usage of the user and/or the allowed usage of the user subscription service does not reach the corresponding usage threshold, the RACS allows access to the resource request.

 Here, after the resource request is allowed to be accessed, the method further includes: the RACS sending the policy to the transport function entity, and performing, by the transport function entity, the usage monitoring according to the policy.

 Here, the method further includes: the transmission function entity feeding back the monitoring result to the RACS. The transmission function entity reports the usage monitoring result to the RACS when the usage of the user and/or service monitored by the usage reaches the corresponding usage threshold; or, when the transmission function entity receives the user and/or service resource monitored by the usage After the request is released, the usage monitoring result is reported to the RACS. The transmission function entity specifically includes: RCEF and/or BGF.

 In summary, the present invention mainly includes the following contents:

 For the ITU-T RACF architecture, the following four aspects are included:

A: The user usage information is signed in the user subscription database, and the usage information indicates the total allowed usage of the user and/or the allowed usage of the user's contracted service. The user usage information is saved in the NACF and pushed to the RACF by the NACF; or is actively requested by the RACF to the NACF.

 Second: RACF formulates policy rules based on user usage information and requests PE-FE to monitor usage.

 In the case of denying access, the usage monitoring based on the user usage information is specifically as follows: When the total allowable usage of the user and/or the allowed usage of the user's subscription service reaches a threshold, the RACF rejects the current resource request, or initiates a static configuration. QoS policy rules.

 When access is allowed, the usage monitoring based on the user usage information is as follows: The RACF sends the PE-FE the user and/or service that needs to be monitored for usage and the corresponding usage threshold.

 III: The PE-FE performs usage monitoring according to the RACF request; and the monitoring result is fed back to the RACF.

 The monitoring and feedback specifically include: when the usage of the user and/or service monitored by the usage reaches the corresponding usage threshold, the PE-FE monitors the result to the RACF; or when the PE-FE receives the monitored user and/or After the service resource release request, the usage monitoring result is reported to the RACF.

 Four: The updated after the feedback includes: The RACF records the current usage of the user and/or the service, and updates the user usage information. The RACF feeds back the updated user usage information to the NACF, and the NACF updates the user usage information.

 For the TISPAN RACS architecture, the following four aspects are included:

 A: User usage information is signed in the user subscription database, and the usage information indicates the total allowable usage of the user and/or the allowed usage of the user's contracted service.

 The user usage information is stored in the NASS and sent to the RACS by the NASS; or the RACS actively requests the NASS.

Second: RACS formulates policy rules based on user usage information and requests transmission function entities to monitor usage. Here, the transport function entity may be specifically: RCEF and/or BGF. In the case of denying access, the usage monitoring based on the user usage information is specifically as follows: When the total allowed usage of the user and/or the allowed usage of the user's subscription service reaches a threshold, the RACS rejects the current resource request, or initiates static configuration. QoS policy rules.

 When access is allowed, the usage monitoring based on the usage information of the user is as follows: The RACS sends the user and/or service that needs to monitor the usage and the corresponding usage value to the transmission function entity.

 III: The transmission function entity performs usage monitoring according to the request of the RACS; and feeds the monitoring result back to the RACS.

 The monitoring and feedback specifically include: when the usage of the user and/or service monitored by the usage reaches the corresponding usage threshold, the transmission function entity reports the usage monitoring result to the RACS; or when the transmission function entity receives the monitored user and/or After the service resource release request, the usage monitoring result is reported to the RACS.

 Four: The updated after the feedback includes: RACS records the usage of the current user and / or business usage, and updates the user usage information. The RACS feeds back the updated user usage information to NASS, which updates the user usage information.

 The invention is illustrated by way of example below.

 Example 1:

 As shown in Figure 3, this example is: Using the ITU-T RACF architecture, the process of signing user usage information, the process includes the following steps:

 Step 301: Sign the user usage information and save it in the NACF.

 Step 302: The NACF pushes the user subscription data including the user usage information to the RACF. Here, the user subscription data may be an existing user subscription information, which is not described below. Step 303: The RACF sends a response message to the NACF.

 Example 2:

As shown in Figure 4, this example is: Using the TISPAN RACS architecture, the user usage information is signed. The process, which includes the following steps:

 Step 401: Sign the user usage information and save it in the NASS.

 Step 402: The NASS pushes the user subscription data including the user usage information to the RACS. Step 403: The RACS sends a response message to the NASS.

 Example three:

 As shown in Figure 5, this example is as follows: The resource request procedure initiated by the SCF in the usage-based admission control method based on the ITU-T RACF architecture, the process includes the following steps:

 Step 501: The user initiates a service request, sends a request message to the SCF, and triggers the SCF to generate a resource initialization request.

 Step 502: The SCF determines a QoS requirement parameter of the requested service, and then sends a resource initialization request message to the RACF.

 The QoS requirement parameters include: bandwidth, service type, service level, and so on.

 The resource initialization request message carries information such as a media stream description and a QoS parameter to request the RACF to perform QoS resource authorization and reservation.

 Step 503: After the RACF receives the resource initialization request message, if the subscription information of the user is not stored locally, the RACF interacts with the NACF to obtain the subscription information of the user.

 Here, the user subscription data includes user usage information indicating the total allowed usage of the user and/or the allowable usage of the subscription service of the user.

 Step 504: The RACF performs an authorization check and an admission decision on the resource initialization request. Here, the specific processing of step 504 includes: verifying whether the requested QoS resource is consistent with the local operator policy rule and the user subscription data from the NACF; and checking the resource availability of the network involved.

 Here, if both the authorization check and the resource availability check are passed, the RACF makes a final admission decision based on the authorization check result and the resource availability check result.

Among them, the final admission decision, on the one hand, specifically includes: RACF based on user usage letter The policy rules are formulated, and the RACF includes the information about the users and/or services that need to be monitored and the corresponding usage thresholds. On the other hand, the specific method includes: The RACF formulates a policy rule according to the user usage information. When the total allowed usage of the user and/or the allowed usage of the user subscription service reaches a threshold, the RACF rejects the current resource request, and the RACF sends a resource initialization response message to the RACF. The SCF, the message carries the reason for the refusal, and the current process ends; or, after the current resource request is allowed to be accessed, and the statically configured QoS policy rule is started as the final policy rule, step 505 is performed.

 Step 505: If the final policy rule needs to be installed in the PE-FE, the RACF sends a resource initialization request message to the PE-FE to install the final policy rule.

 In step 506, the PE-FE installs the final policy rule from the RACF and sends a resource initialization response to the RACF.

 Here, the specific processing of step 506 includes: The PE-FE performs usage monitoring according to the request of the RACF. The PE-FE reports the usage monitoring result to the RACF when the usage of the monitored user and/or service reaches the corresponding usage threshold; or, after the PE-FE receives the monitored user and/or service resource release request, , report the usage monitoring results to the RACF.

 In step 507, the RACF sends a resource initialization response to the SCF.

 Example four:

 As shown in Figure 6, this example is: Using the TISPAN RACS architecture, the AF-based resource request process in the usage-based admission control method, the process includes the following steps:

 Step 601: The UE initiates a service request to the AF, and triggers the AF to generate a session for the service request.

 Step 602: The AF sends a resource request message to the RACS to request resource authorization and reservation. Step 603: After receiving the resource request message, the RACS performs an authorization check on the resource request according to the local operator policy rule.

Here, if the authorization check fails, the RACS sends a resource request response to the AF, currently The process ends. If the authorization check passes, step 604 is performed.

 Step 604: After the authorization check, if the subscription information of the user is not stored locally, the RACS interacts with the NASS to obtain the subscription information of the user.

 Here, the user subscription data includes user usage information indicating the total allowed usage of the user and/or the allowable usage of the subscription service of the user.

 Step 605: The RACS performs an authorization check and admission decision on the resource request according to the user subscription data, the resource availability, and the access network policy.

 Here, the specific processing procedure of step 605 includes: the RACS formulates a transmission policy according to the usage information of the user, and the RACS includes information about the user and/or service that needs to be monitored by the usage and the corresponding usage threshold. The specific processing procedure of step 605 includes, on the other hand, the RACS formulating a transmission policy according to the usage information of the user. When the total allowed usage of the user and/or the allowed usage of the subscription service of the user reaches a threshold, the RACS rejects the current resource request, and the current The process ends; or, after the statically configured QoS policy rule is started as the final transmission policy, step 606 is performed.

 Step 606: If the transmission policy needs to be installed in the transport function entity, the RACS sends a resource request message to the transport function entity to install the transport policy.

 Here, the transport function entity may be RCEF and/or BGF, which will not be described below.

 Step 607: The transport function entity installs a transmission policy from the RACS and sends a resource request response to the RACS.

 Here, the specific processing of step 607 includes: The transmission function entity performs usage monitoring according to the request of the RACS. When the usage of the user and/or service monitored by the usage reaches the corresponding usage threshold, the transmission function entity reports the usage monitoring result to the RACS; or, after the transmission function entity receives the monitored user and/or service resource release request, , report the usage monitoring result to RACS.

 Step 608: The RACS sends a resource request response to the AF.

A usage signing system, the system comprising: a signing unit and a sending unit. Among them, signed The unit is used to sign user usage information in the user subscription database. a sending unit, configured to send, by the network attachment platform, user subscription data including user usage information to the resource admission control platform; or, after the resource admission control platform requests the network attachment platform, the network attachment platform includes the user usage information. User subscription data is sent to the resource admission control platform.

 Here, the system further includes: a saving unit, configured to save the user usage information in the network attached platform. The user usage information includes: information indicating the total allowable usage of the user and/or the allowable usage of the user's subscription service.

 A usage-based admission control system, the system comprising: a formulation unit, and an admission control unit. Among them, a unit is formulated for formulating a policy based on user usage information. Admission control unit for implementing admission control in accordance with established policies.

 Due to the different protocol architectures, the specific implementation of the system is different, so the following is explained separately.

 Case 1: The case of the ITU-T RACF architecture.

 The admission control unit in the system is further used by the RACF to receive the resource initialization request from the SCF; when the RACF does not store the user subscription data locally, the RACF interacts with the NACF and obtains the user subscription data; the RACF formulates the resource initialization request. Monitor the policy of the rule and implement control to deny access requests or allow access requests.

 Here, the strategies developed include: Users and/or businesses that need to monitor usage, and the corresponding usage threshold.

 Here, the admission control unit is further configured to: when the total allowed usage of the user and/or the allowed usage of the user subscription service reaches the corresponding usage threshold, the RACF denies access to the resource initialization request; or initiates the statically configured QoS policy.

 Alternatively, the admission control unit is further configured to allow the RACF to access the resource initialization request when the total allowed usage of the user and/or the allowed usage of the user subscription service does not reach the corresponding usage threshold.

Here, the system further includes: a usage monitoring unit, configured to allow access to the resource initialization request After the RACF sends the policy to the PE-FE, the PE-FE performs the usage monitoring according to the policy. Case 2: Using the TISPAN RACS architecture.

 The admission control unit in the system is further configured to receive the resource request from the AF by the RACS; when the RACS does not store the user subscription data locally, the RACS interacts with the NASS and obtains the user subscription data; the RACS formulates the usage monitoring rule for the resource request. And implement control to deny access requests or allow access requests.

 Here, the strategies developed include: Users and/or businesses that need to monitor usage, and the corresponding usage threshold.

 Here, the admission control unit is further configured to: when the total allowed usage of the user and/or the allowed usage of the user subscription service reaches the corresponding usage threshold, the RACS denies access to the resource request; or initiates the statically configured QoS policy.

 Alternatively, the admission control unit is further configured to allow the RACS to access the resource request when the total allowed usage of the user and/or the allowed usage of the user subscription service does not reach the corresponding usage threshold.

 Here, the system further includes: a usage monitoring unit, configured to allow the access to the resource request, the RACS to deliver the policy to the transmission function entity, and the transmission function entity performs the usage monitoring according to the policy. The transmission function entity specifically includes: RCEF and/or BGF.

 In summary, according to the present invention, the usage-based admission control scheme is implemented by clarifying different QoS policy controls of different usages, thereby solving the problems in the prior art.

 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 signing usage, characterized in that the method comprises:  Signing user usage information in the user subscription database;  User subscription data including the user usage information is actively pushed to the resource admission control platform by the network attachment platform; or, after the resource admission control platform requests the network attachment platform, and then from the network attachment platform The user subscription data including the user usage information is passively obtained.  The method according to claim 1, wherein the user usage information is stored in the network attachment platform; and the user usage information comprises: indicating a total allowable usage of the user and/or permission of the user to subscribe to the service. Information on usage.  The method according to claim 1 or 2, wherein, in the case of using the International Telecommunication Union (ITU-T) Resource Admission Control Function (RACF) architecture, the network attachment platform is a network attachment control function ( NACF), the resource admission control platform is a RACF;  Alternatively, in the case of the communication and Internet convergence service and protocol (TISPAN) resource admission control subsystem (RACS) architecture of the advanced network, the network attachment platform is a network attachment subsystem (NASS), and the resource admission control The platform is RACS.  4. A usage signing system, characterized in that the system comprises: a signing unit and a sending unit; wherein  a signing unit for signing user usage information in the user subscription database;  a sending unit, configured to send the user subscription data that includes the user usage information to the resource admission control platform by the network attachment platform; or, after the resource admission control platform requests the network attachment platform, The network attachment platform sends the user subscription data including the user usage information to the resource admission control platform. The system according to claim 4, wherein the system further comprises: a saving unit, configured to save the user usage information in the network attachment platform; The information includes: information that characterizes the total allowable usage of the user and/or the allowed usage of the user's contracted service.  6. A usage-based admission control method, the method comprising: formulating a policy based on user usage information, and implementing admission control.  The method according to claim 6, wherein, in the case of using the ITU-T RACF architecture, the formulating the policy according to the user usage information and implementing the admission control comprises:  The RACF receives the resource initialization request from the service layer function (SCF) of the service layer; when the RACF does not store the user subscription data locally, the RACF interacts with the NACF and obtains the user subscription data;  The RACF formulates a policy including the usage monitoring rule for the resource initialization request, and implements control of rejecting the access request or allowing the access request.  The method according to claim 7, wherein the user usage information is saved in the NACF; wherein the user usage information comprises: indicating a total allowable usage of the user and/or permission of the user to subscribe to the service Information on usage.  The method according to claim 8, wherein the policy comprises: a user and/or a service that needs to perform usage monitoring, and a corresponding usage threshold;  The control to implement the denial of access request or allow access request includes:  When the total allowable usage of the user and/or the allowed usage of the user subscription service reaches the corresponding usage threshold, the RACF denies access to the resource initialization request; or initiates a statically configured quality of service (QoS) policy;  Alternatively, the RACF allows access to the resource initialization request when the total allowed usage of the user and/or the allowed usage of the subscriber subscription service does not reach the corresponding usage threshold.  The method according to claim 9, wherein after the resource initialization request is allowed to be accessed, the method further comprises: the RACF issuing the policy to the policy enforcement function entity (PE-FE), by the PE- FE performs dose monitoring according to the strategy. The method according to claim 10, wherein the method further comprises: The PE-FE feeds back the monitoring result to the RACF; wherein  The PE-FE reports the usage monitoring result to the RACF when the usage of the user and/or service monitored by the usage reaches the corresponding usage threshold; or, when the PE-FE receives the user and/or service resource release request monitored by the usage After that, the usage monitoring result is reported to the RACF.  The method according to claim 6, wherein, in the case of using the TISPAN RACS architecture, the formulating the policy according to the user usage information and implementing the admission control comprises:  The RACS receives the resource request from the application function (AF); when the RACS does not store the user subscription data locally, the RACS interacts with the NASS and obtains the user subscription data;  The RACS formulates a policy including the usage monitoring rule for the resource request, and implements control of denying the access request or allowing the access request.  The method according to claim 12, wherein the user usage information is stored in the NASS; wherein, the user usage information comprises: indicating a total allowable usage of the user and/or permission of the user to subscribe to the service Information on usage.  The method according to claim 13, wherein the policy comprises: a user and/or a service that needs to perform usage monitoring, and a corresponding usage threshold;  The control to implement the denial of access request or allow access request includes:  When the total allowable usage of the user and/or the allowed usage of the user subscription service reaches the corresponding usage threshold, the RACS denies access to the resource request; or initiates a statically configured QoS policy; or, when the user is total The RACS allows access to the resource request when the allowed usage and/or the allowed usage of the user subscription service does not reach the corresponding usage threshold.  The method according to claim 14, wherein, after the request for accessing the resource is allowed, the method further comprises: the RACS sending the policy to the transmission function entity, and the method is used by the transmission function entity according to the policy. monitor. The method according to claim 15, wherein the method further comprises: the transmitting function entity feeding back a monitoring result to the RACS; When the usage of the user and/or service monitored by the usage reaches the corresponding usage threshold, the transmission function entity reports the usage monitoring result to the RACS; or, when the transmission function entity receives the user and/or service resource release request monitored by the usage After that, the usage monitoring result is reported to the RACS;  The transport function entity includes: a resource control execution function (RCEF) and/or a border gateway function (BGF).  17. A usage-based admission control system, the system comprising: a formulation unit, and an admission control unit; wherein  a unit for formulating a strategy based on user usage information;  Admission control unit for implementing admission control in accordance with established policies.  The system according to claim 17, wherein, in the case of using the ITU-T RACF architecture, the admission control unit is further configured to receive a resource initialization request from the SCF by the RACF; the RACF is not locally stored. When the user subscribes to the data, the RACF interacts with the NACF and acquires the user subscription data; the RACF formulates a policy including the usage monitoring rule for the resource initialization request, and implements the control of rejecting the access request or allowing the access request.  The system according to claim 18, wherein the policy comprises: a user and/or a service that needs to perform usage monitoring, and a corresponding usage threshold;  The admission control unit is further configured to: when the total allowed usage of the user and/or the allowed usage of the user subscription service reaches a corresponding usage threshold, the RACF refuses to access the resource initialization request; or initiates static configuration. The QoS policy; or the admission control unit is further configured to: when the total allowed usage of the user and/or the allowed usage of the user subscription service does not reach the corresponding usage threshold, the RACF allows access to the resource initialization request. ;  The system further includes: a usage monitoring unit, configured to allow the access to the resource initialization request, the RACF sends the policy to the PE-FE, and the PE-FE performs usage monitoring according to the policy. 20. The system according to claim 17, wherein, in the case of using a TISPAN RACS architecture, the admission control unit is further configured to receive the FCS from the AF Source request; when the RACS does not store the user subscription data locally, the RACS interacts with the NASS and obtains the user subscription data; the RACS formulates a policy including the usage monitoring rule for the resource request, and implements the control of rejecting the access request or allowing the access request. .  The system according to claim 20, wherein the policy comprises: a user and/or a service that needs to perform usage monitoring, and a corresponding usage threshold;  The admission control unit is further configured to: when the total allowed usage of the user and/or the allowed usage of the user subscription service reaches a corresponding usage threshold, the RACS refuses to access the resource request; or initiates static configured QoS. Or the admission control unit is further configured to: when the total allowed usage of the user and/or the allowed usage of the user subscription service does not reach the corresponding usage threshold, the RACS allows access to the resource request;  The system further includes: a usage monitoring unit, configured to allow the access to the resource request, the RACS sends the policy to the transmission function entity, and the transmission function entity performs usage monitoring according to the policy.