WO2013044730A1 - Quality of service updating method and system for policy and charging rules - Google Patents

Abstract

A quality of service updating method and system for policy and charging rules. The method includes: a terminal interacting with a trigger function to request or confirm the update of the quality of service of a service accessed by the terminal; and the trigger function interacting with a policy and charging rules function (PCRF), and the PCRF performing IP connection access network session modification according to the request of the trigger function and updating the quality of service of the service. The present solution can provide the user with improved quality of service of a service according to user demand when using a service of a third party application provider without partnership with the operators.

Description

 Method and system for updating service quality of policy and charging rules

Technical field

 The present invention relates to a policy and charging control technology in a wireless communication system, and more particularly to a method and system for updating a service quality of a policy and charging rule in an evolved packet system (EPS, Evolved Packet System).

Background technique

 1 is a schematic structural diagram of a 3GPP evolved packet system. As shown in FIG. 1, a 3GPP Evolved Packet System (EPS) is an evolved universal mobile communication system terrestrial radio access network (E-UTRAN, Evolved Universal Terrestrial Radio Access Network). ), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (PDN GW or P-GW, Packet Data Network Gateway), Home Subscriber Server (HSS, Home Subscriber) Server), 3GPP's AAA, Authentication, Authorization and Accounting, and the Policy and Charging Rules Function (PCRF) entity and other supporting nodes.

 The MME is used for control plane related operations such as mobility management, non-access stratum signaling processing, and user mobility management context management; the S-GW is an access gateway device connected to the E-UTRAN, in the E-UTRAN and The data is forwarded between the P-GWs and used to buffer the paging waiting data. The P-GW is a border gateway between the EPS and the PDN, and is used for PDN access and forwarding data between the EPS and the PDN.

EPS supports interworking with non-3GPP systems. The interworking with the non-3GPP system is implemented through the S2a, S2b, and S2c interfaces, and the P-GW serves as an anchor point between the 3GPP system and the non-3GPP system. Among them, the non-3GPP system is divided into a trusted non-3GPP access system and an untrusted non-3GPP access system. The trusted non-3GPP access system can be directly connected to the P-GW through the S2a interface; the untrusted non-3GPP access system needs to be connected to the P-GW via an ePLG (Evolved Packet Data Gateway), ePDG and P- The GW is an S2b interface. The S2c interface provides user plane-related control and mobility support between the user equipment (UE, User Equipment) and the P-GW, and the supported mobile The SMS management protocol is dual-stack mobile IPv6 (DSMIPv6, Moblie IPv6 support for dual stack Hosts and Routers).

 The EPS system introduces the policy charging control (PCC, Policy and Charging Control) function box to perform dynamic policy charging control for user service access. Figure 2-1 shows the structure of the PCC in the non-roaming scenario in the Rel-8. As shown in Figure 2, the application function (AF, Application Function) entity is used to provide access points for service applications. The network used by these service applications. Resources require dynamic policy control. When the parameters are negotiated on the service plane, the AF passes the related service information to the PCRF. If the service information is consistent with the PCRF policy, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation and gives the business parameters acceptable to the PCRF upon feedback. The AF can then return these parameters to the user equipment (UE, User Equipment). The interface between AF and PCRF is the Rx interface.

 The PCRF is the core of the PCC and is responsible for policy decision making and billing rules. The PCRF provides network control rules based on service data flows, including traffic data flow detection, Gating Control, Quality of Service (QoS) control, and data flow based charging rules. The PCRF sends its policy and charging rules to the Policy and Charging Enforcement Function (PCEF) entity. At the same time, the PCRF also needs to ensure that these rules are consistent with the user's subscription information. The basis for formulating the policy and charging rules by the PCRF includes: obtaining information related to the service from the AF, obtaining the subscription information related to the user policy charging control from the SPR (Spent Profile Repository), and obtaining the subscription information from the PCEF through the Gx interface. Information about the network associated with the bearer.

The PCEF is usually located in the gateway (GW, Gate-Way) and performs the policy and charging rules established by the PCRF on the bearer plane. The PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then executes the policy and charging rules formulated by the PCRF for these service data flows. When the bearer is established, the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF. At the same time, the PCEF triggers reporting of events occurring on the bearer network according to events subscribed by the PCRF. According to the charging rule sent by the PCRF, the PCEF performs a corresponding service data flow charging operation, and the charging can be either online charging or offline charging. In the case of online charging, the PCEF needs to perform credit management together with the Online Charging System (OCS). When offline charging, PCEF and offline charging system (OFCS, Offline Charging Exchange related accounting information between System. The interface between the PCEF and the PCRF is a Gx interface, the interface with the OCS is a Gy interface, and the interface between the OFCS and the OFCS is a Gz interface. PCEFs are generally located on the gateway of the network, such as the Packet Data Network Gateway (PDN-GW) of the EPS, the GPRS Gateway Support Node (GGSN) in the General Packet Radio Service (GPRS), and the interconnected wireless LAN. Packet Data Gateway (PDG) in (I-WLAN, Interworking WLAN, ).

 The Bearer Binding and Event Reporting Function (BBERF) entity is usually located in the Access Network Gateway. For example, when the user equipment accesses the EPS through the E-UTRAN, and the proxy mobile internet protocol version 6 (ΡΜΙΡνό, Proxy Mobile Internet Protocol version 6) protocol is used between the E-UTRAN and the P-GW, the S-GW exists. BBERF. When the user equipment accesses through a trusted non-3GPP access network, BBERF also exists in the trusted non-3GPP access gateway.

 The SPR stores user policy charging control subscription information related to policy control and charging. The interface between SPR and PCRF is the Sp interface.

 The Online Charging System (OCS) and PCEF are used to control and manage user credits in the online charging mode.

 The offline charging system (OFCS) and the PCEF are used to complete the charging operation in the offline charging mode.

 The above PCC architecture implements a policy plan for the IP Connectivity Access Network (IP-CAN) session established by the UE to access a Packet Data Network (PDN) through various functional entities. Fee control. The policy charging control information for an IP-CAN session is determined by only one PCRF.

In the related art, after the UE establishes an IP-CAN session to a certain PDN, the network provides network resources required for data transmission according to the corresponding authorized QoS, and the QoS can be changed according to requirements in the service process. For IMS-type services, the AF will provide new QoS information to the PCRF, and the PCRF initiates an IP-CAN session modification procedure. The PCRF combines the QoS of the new AF request with the corresponding subscription data of the SPR/UDC (User Data Convergence), re-authorizes the underlying network bearer resource information, and issues new PCC/QoS rules to the PCEF/BBERF. The PCEF/BBERF updates the corresponding rules and modifies them. Bear resources to provide new QoS for this service. For non-IMS services, operators can work according to their own needs. The network, custom non-IMS service platform and data center, triggers its PCRF to initiate an IP-CAN session modification process to change QoS through a custom interface. If the service is not provided by the operator's own service platform, the operator can sign a private agreement with the service provider to trigger the PCRF to initiate an IP-CAN session modification process to change the QoS through a custom interface.

 At the same time, mobile operators need to provide a growing variety of service processing for different devices, which may come from the operator's own data center or may be a third-party data application provider outside the carrier domain. Therefore, the way in which operators currently implement proprietary protocols to support private functions and non-3GPP interfaces with third-party data application providers has resulted in frequent upgrades of carrier networks and complex and confusing policy management mechanisms. Therefore, it is necessary for mobile operators to use a unified 3GPP interface for different data application providers to communicate with each other. Supporting such interworking scenarios in terms of authentication, authorization, policy, charging, mobility, and session continuity has become a necessary solution. problem.

 Operators can establish cooperative relationships with some application service providers to provide good service quality and application experience for users' application services. However, the number and types of network third-party application providers are increasing, and operators are not. It is possible to have a business collaboration with all application providers. Therefore, in this scenario, the operator needs to be able to independently provide the subscription users of the network with the service quality required for the application service, and can improve and lower the service quality according to the user requirements, and can decide whether to There is an extra charge for high quality of service. For example, a subscriber A of an operator MNO Y is using a service provided by a third-party application provider X (for example, an online movie). Since MNO Y and X have no cooperation, the service uses the non-guaranteed bandwidth provided by the default bearer. Quality of service; In the process of using the service, the user A feels that the user experience is poor and initiates a request to the operator Y to improve the service quality of the service. Then the operator Y needs to modify the current IP-CAN session of the UE. Corresponding QOS; At the same time, due to the high service quality, there is an additional charge. It is necessary to inform the user whether it is satisfied with the upgraded service quality and is willing to pay for it. After the user confirms the permission, the operator can charge an additional fee for the improvement of the service quality. . However, there are no solutions in the relevant UE and network processes that support the promotion and validation of this type of service.

Summary of the invention

Embodiments of the present invention provide a method and system for updating a service quality of a policy and a charging rule. The problem of providing service quality cannot be provided according to user requirements when the user uses the service of a third-party application provider that does not have a cooperative relationship with the operator.

 In order to solve the above technical problem, the present invention provides a service quality update method for a policy and a charging rule, including:

 The terminal interacts with the triggering function to request or confirm an update of the service quality of the service accessed by the terminal;

 The trigger function interacts with a policy charging rule function (PCRF), and the PCRF performs an IP-Connected Access Network (IP-CAN) session modification according to the request of the triggering function to update the service quality of the service.

 The PCRF entity performs an IP-CAN session modification, and the steps of updating the quality of service of the service include:

 After receiving the request for updating the quality of service of the service sent by the triggering function, if the PCRF determines that the terminal has subscribed to the high priority flow processing, performing the IP-CAN session modification to update the service of the service. quality.

 The method also includes:

 After the service quality update of the service is completed, the trigger function sends an update service quality confirmation request to the terminal or the terminal itself triggers an update service quality confirmation request;

 If the terminal agrees to perform the updated quality of service, it returns an update confirmation response to the trigger function, and if it does not agree to perform the updated quality of service, returns an update denied response or does not return a response to the trigger function.

 The method also includes:

 After the service quality update of the service is completed, if the terminal agrees to perform the updated service quality, the terminal returns an update confirmation response to the trigger function, and if it does not agree to perform the updated service quality, returns to the trigger function. Update the denied response or not return a response.

 The method also includes:

After the terminal is roaming, the home PCRF notifies the trigger function that the terminal is roaming, and the trigger function sends an update service quality confirmation request to the terminal. The method also includes:

 After the triggering function knows that the terminal does not agree to the updated quality of service, sending a negative acknowledgement to the PCRF, the PCRF initiates the IP-CAN session modification, and re-updates the service quality of the service, including reducing the The quality of service of the service or the original quality of service for the service.

 The trigger function is a logical function entity having an application function, integrated in the PCRF, or deployed in a network application function (NAF) or a non-IP multimedia subsystem application service (non-IMS AS) or dependent In the party (RP), and interacting with the PCRF through a protocol that meets the communication requirements of the two, the protocol includes the Diameter protocol.

 The embodiment of the present invention further provides another method for updating the quality of service of the policy and charging rules, including:

 The terminal interacts with the Policy Charging Rules Function (PCRF) to request or confirm an update of the quality of service of the service accessed by the terminal;

 The PCRF performs an IP-CAN session modification according to the trigger of the terminal, and updates the service quality of the service.

 The PCRF performs an IP-CAN session modification, and the steps of updating the quality of service of the service include:

 After the PCRF receives the request for updating the quality of service of the service sent by the terminal, and determines that the terminal has subscribed to the high priority flow processing, performing the IP-CAN session modification to update the service quality of the service. .

 The method also includes:

 After the service quality update of the service is completed, the PCRF sends an update service quality confirmation request to the terminal or the terminal itself triggers an update service quality confirmation request;

 If the terminal agrees to perform the updated quality of service, it returns an update confirmation response to the PCRF; if it does not agree to perform the updated quality of service, it returns an update denied response to the PCRF or does not return a response.

 The method also includes:

After the service quality update of the service is completed, if the terminal agrees to perform the updated service quality, the terminal returns an update confirmation response to the PCRF, and if it does not agree to perform the updated service quality, Then the update denied response is returned to the PCRF or no response is returned.

 The method also includes:

 After the terminal roams, the home PCRF sends an update service quality confirmation request to the terminal.

 The method also includes:

 After the PCRF learns that the terminal does not agree to the updated service quality, the IP-CAN session modification is initiated, and the service quality of the service is re-updated, including reducing the quality of service or restoring the original service quality.

 An embodiment of the present invention further provides a service quality update system for a policy and a charging rule, including a terminal and a policy charging rule function (PCRF), where

 The system also includes a trigger function;

 The terminal is configured to interact with the trigger function to request or confirm an update of a quality of service of a service accessed by the terminal;

 The triggering function is configured to interact with the PCRF, requesting the PCRF to initiate an IP connection access network (IP-CAN) session modification process to update the service quality of the service;

 The PCRF is configured to perform an IP-CAN session modification to update the quality of service of the service. The PCRF is configured to perform the IP-CAN session modification, and update the IP address when the terminal has signed the high priority flow processing after receiving the request for updating the service quality of the service sent by the trigger function. The quality of service of the business.

 The triggering function is further configured to: after the terminal does not agree to the updated quality of service, send a negative acknowledgement to the PCRF, trigger the PCRF to initiate the IP-CAN session modification, and re-update the service quality of the service. , including reducing the quality of the service or restoring the original quality of service. The embodiment of the present invention further provides another service quality update system for policy and charging rules, including a terminal and a policy charging rule function (PCRF), where

 The terminal is configured to interact with the PCRF to request or confirm an update of the quality of service of the service accessed by the terminal;

The PCRF is configured to perform an IP connection access network (IP-CAN) according to the trigger of the terminal Modify the words and update the service quality of the service.

 The PCRF is configured to perform the IP-CAN session modification and update the service when it is determined that the terminal has subscribed to the high priority flow processing after receiving the request for updating the quality of service of the service sent by the terminal. Quality of service.

 The PCRF is further configured to initiate the modification of the IP-CAN session and re-update the quality of service of the service after learning that the terminal does not agree to the updated quality of service, including reducing the quality of service or restoring the original quality of service.

This solution can ensure that users can provide service quality according to user requirements when using services of third-party application providers that do not have a cooperative relationship with operators.

BRIEF abstract

 1 is a schematic structural diagram of a 3GPP evolved packet system;

 2 is a schematic diagram of a PCC structure in a non-roaming scenario in Rel-10;

 Figure 3-1 is a schematic diagram of a service quality update method for policy and charging rules 1;

 Figure 3-2 is a schematic diagram 2 of the method for updating the quality of service of the policy and charging rules;

 4 is a schematic structural diagram of a system in a non-roaming scenario of a PCC in the first embodiment;

 5 is a schematic diagram of a service quality update procedure in a PCC-based non-roaming scenario in the first embodiment;

 6 is a schematic structural diagram of a system in a PCC roaming scenario in Embodiment 1;

 7 is a schematic diagram of a service quality update procedure in a PCC-based non-roaming scenario in the first embodiment;

 8 is a schematic structural diagram of a GBA network provided in Embodiment 2;

9 is a schematic structural diagram of a service quality update system based on a GBA network in Embodiment 2; FIG. 10 is a schematic diagram of a service quality update process based on a GBA network in Embodiment 2; FIG. 11 is a schematic diagram of an OpenID and GBA network structure provided in Embodiment 3. ; 12 is a schematic structural diagram of a service quality update system based on OpenID and GBA networks in Embodiment 3;

 13 is a schematic diagram of a service quality update process based on OpenID and GBA networks in Embodiment 3;

 14 is a schematic structural diagram of a system in a non-roaming scenario of a PCC in Embodiment 4;

 15 is a schematic diagram of a service quality update procedure in a PCC-based non-roaming scenario in Embodiment 4;

 16 is a schematic structural diagram of a system in a PCC roaming scenario in Embodiment 4;

 17 is a schematic diagram of a service quality update procedure in a PCC-based non-roaming scenario in Embodiment 4. Preferred embodiment of the invention

 As shown in Figure 3-1, an implementation method for the service quality update of the policy and the charging rule includes: the terminal interacting with the triggering function to request or confirm the update of the service quality of the service accessed by the terminal; The function interacts with the PCRF, and the PCRF performs IP-CAN session modification according to the request of the trigger function to update the quality of service of the service.

 The trigger function is deployed separately from the PCRF. The triggering function is a triggering NE with an application function. It is a logical functional entity. The deployment can be an entity such as NAF or non-IMS AS or RP. A trigger function and a PCRF interface Rx' are added. The Rx' is similar to the Rx interface. The two communicate through a protocol that meets the communication requirements of the two. For example, the trigger function interacts with the PCRF through the Diameter protocol, and the trigger function is sent as a PCRF client to the PCRF. The request message triggers the PCRF to initiate an IP-CAN session modification process.

 In this solution, an interface between the UE and the trigger function is added. The interface supports the http protocol or other application layer signaling, and the trigger function interacts with the terminal through Hypertext Transfer Protocol (HTTP) or application layer signaling.

In the method, after receiving the request for the service quality of the service sent by the triggering function, the PCRF may directly improve the service quality of the service, and may also determine that the terminal has subscribed to the high priority flow processing, and The IP-CAN session is modified to update the quality of service of the service. In this method, the PCRF can also reduce or restore QoS, specifically:

 After the service quality update of the service is completed, after the trigger function sends an update service quality confirmation request to the terminal or the terminal itself triggers an update service quality confirmation request, when the terminal agrees to perform the upgraded service quality, the The trigger function returns an update confirmation response, and when it does not agree to perform the promoted quality of service, returns an update denied response or does not return a response to the trigger function.

 Or, after the service quality update of the service is completed, when the terminal agrees to perform the updated service quality, returning an update confirmation response to the trigger function, and disagreeing to perform the upgraded service quality, returning to the trigger function Update the denied response or not return a response.

 After the terminal is roaming, the home PCRF notifies the trigger function that the terminal is roaming, and the trigger function sends an update service quality confirmation request to the terminal again.

 After the triggering function knows that the terminal does not agree to the improved quality of service, sending a negative acknowledgement to the PCRF, the PCRF initiates the IP-CAN session modification, and updates the service quality of the service, including reducing the service. Quality or restore the original quality of service.

 The service quality update system of the policy and charging rule corresponding to the above method includes a terminal and a policy charging rule function entity (PCRF), and the system further includes a trigger function.

 The terminal is configured to interact with the triggering function to request or confirm an update of the quality of service of the service accessed by the terminal; the triggering function is configured to interact with the PCRF, requesting the PCRF to initiate an IP-CAN session modification process, and updating the Determining the quality of service of the service; the PCRF is configured to perform an IP-CAN session modification to update the quality of service of the service.

 The trigger function is deployed separately from the PCRF. The triggering function is a triggering NE with an application function. It is a logical functional entity. The deployment can be an entity such as NAF or non-IMS AS or RP. Added trigger function and PCRF interface Rx', this Rx' is similar to Rx interface, and the two communicate with the protocol that meets the communication requirements of the two. For example, the trigger function interacts with the PCRF through the Diameter protocol, and the trigger function acts as the PCRF client to the PCRF. Sending a request message triggers the PCRF to initiate an IP-CAN session modification process.

In this solution, an interface between the UE and the trigger function is added. The interface supports the http protocol or other application layer signaling, and the trigger function interacts with the terminal through Hypertext Transfer Protocol (HTTP) or application layer signaling. The PCRF is configured to perform the IP-CAN session modification, and update the IP address when the terminal has signed the high priority flow processing after receiving the request for updating the service quality of the service sent by the trigger function. The quality of service of the business.

 The PCRF can also reduce or restore QoS. The triggering function is further configured to: after the terminal does not agree to the updated quality of service, send a negative acknowledgement to the PCRF to trigger the PCRF to initiate the IP-CAN session modification, and update the service quality of the service, including reducing The quality of service or the original quality of service is restored.

 The constituent entities in the system also have the same functions as those described in the above method, and the description will not be repeated here.

As shown in FIG. 3-2, an implementation method of the service quality update of the policy and the charging rule includes: the terminal interacting with the PCRF to request or confirm the update of the service quality of the service accessed by the terminal;

 The PCRF performs IP-CAN session modification according to the trigger of the terminal, and updates the service quality of the service.

 In the method, the PCRF has the function of triggering function in the above method, and it can be understood that the trigger function is integrated into the PCRF or the PCRF enhances the trigger function in the above method. The internal interface is used between the two, and the communication protocol of the two is not limited.

 In the method, after the PCRF receives the request for updating the service quality of the service, the PCRF may directly improve the service quality of the service, and may also determine that the terminal has signed the high priority flow processing, and performs The IP-CAN session is modified to update the quality of service of the service.

 In this method, the PCRF can also reduce or restore QoS, specifically:

 After the service quality update of the service is completed, after the PCRF sends an update service quality confirmation request to the terminal or the terminal itself triggers an update service quality confirmation request, when the terminal agrees to perform the upgraded service quality, the The PCRF returns an update confirmation response; when it does not agree to perform the promoted quality of service, it returns an update denied response to the PCRF or does not return a response.

Or, after the service quality update of the service is completed, when the terminal agrees to perform the updated service quality, returning an update confirmation response to the PCRF, disagreeing to perform the upgraded service quality. At the time, an update denied response is returned to the PCRF or no response is returned.

 After the terminal roams, the home PCRF sends an update service quality confirmation request to the terminal.

 After the PCRF knows that the terminal does not agree to the improved quality of service, the IP-CAN session modification is initiated, and the service quality of the service is updated, including reducing the quality of service or restoring the original service quality.

The service quality update system of the policy and charging rule corresponding to the foregoing method includes a terminal and a PCRF, wherein the terminal is configured to interact with the PCRF to request or confirm an update of the quality of service of the service accessed by the terminal; The PCRF is set to perform IP-CAN session modification according to the trigger of the terminal, and update the quality of service of the service.

 In this system, the PCRF has the function of the trigger function in the above method, and it can be understood that the trigger function is integrated in the PCRF or the PCRF enhances the trigger function in the above method. The internal interface is used between the two, and the communication protocol of the two is not limited.

 The PCRF is configured to perform the IP-CAN session modification and update the service when it is determined that the terminal has subscribed to the high priority flow processing after receiving the request for updating the quality of service of the service sent by the terminal. Quality of service.

 The PCRF can also reduce or restore QoS. The PCRF is further configured to: after the terminal does not agree to the improved quality of service, initiate the IP-CAN session modification, and update the service quality of the service, including reducing the quality of service or restoring the original quality of service.

 The constituent entities in the system also have the same functions as those described in the above method, and the description will not be repeated here.

In the foregoing solution, when the service used by the terminal is from a third-party application service provider that does not have a cooperative relationship with the operator, the service function of the service may be updated and modified by using a trigger function separately deployed with the PCRF or a PCRF having a trigger function. , to achieve the purpose of providing business service quality according to user requirements. This solution is also applicable to the carrier's own business and the cooperative third-party application service provider business. The present solution will be described below by way of specific embodiments.

 Embodiment 1

 As shown in FIG. 4, this embodiment introduces the trigger function of the solution on the basis of the architecture of FIG. 2, and adds an interface between the UE and the trigger function (here, the interface between the UE and the application function, which can use the http protocol or Other application layer signaling), also added a trigger function and PCRF interface Rx' (this Rx' is similar to the Rx interface, which can communicate using the Diameter protocol).

 The UE described in this embodiment accesses the 3GPP network in a non-roaming scenario, and uses the service of the third-party application service provider that has no cooperation relationship with the operator. The operator is responsible for providing transmission resources for the third-party application of the UE, and can adjust the quality of service according to the requirements of the UE and notify the UE to confirm. As shown in FIG. 5, the method for updating and confirming the quality of service includes the following steps:

 Step 501: The UE attaches to the home network, establishes a radio bearer, and creates an IP-CAN session. Step 502: The UE logs in and successfully accesses a non-IP multimedia subsystem application service (Non-IMS AS), and the non-IMS AS provides an application service for the UE. The UE and the Non-IMS AS can use HTTP protocol and application layer signaling when communicating.

 Step 503: The Non-IMS AS and the PCRF execute the PCC process.

 The Non-IMS AS initiates an Rx session establishment request to the PCRF, which may carry the UE ID/IP, the service ID/application ID, and the data flow related information. The PCRF obtains the contracted AS information from the SPR/UDC, and formulates and delivers the PCC rules to the PCEF to establish related data bearers.

 Because the AS does not cooperate with the operator, the QoS is the default bearer QoS; and for the AS without cooperation, the QoS information and service information of the Rx interface and the PCRF are optional steps.

 Step 504: Complete the creation of the bearer required for the service.

 Specifically, the PCRF formulates the PCC/QoS rules according to the information sent by the client, such as the AS, the SPR/UDC, and the PGW, and delivers the PCC/QoS rules to the PCEF/BBERF. The PCEF/BBERF installs and executes the relevant rules to complete the bearer binding. The bearer sends a bearer setup request to create a bearer. The PCRF may also carry related event triggers, as well as usage monitoring thresholds, monitoring keywords, and other information. PCEF receives and executes related event reports after receiving the information. Usage monitoring function.

Step 505: The service bearer is created, and the network provides the service data for the UE according to the authorized QoS. Downlink transmission.

 Step 506: In the service process, the UE finds that the quality of service QoS or the user experience is not satisfactory (for example, due to factors such as unstable data flow or low bandwidth due to mobility or network conditions), the UE initiates a QoS promotion request to the trigger function. .

 The QoS promotion request may carry the UEIP/ID, the priority flow processing indication/QoS, and the data flow information, and may carry the service ID/application ID if necessary.

 The communication protocol between the UE and the trigger function is not limited, and the http or application layer signaling can be implemented.

 Step 507: After receiving the QoS promotion request of the UE, the trigger function associates the UE Id/IP with the service/application that needs to improve the QoS, sends a QoS promotion request to the PCRF, and requests to initiate a session modification to improve the QoS of the corresponding session.

 The QoS promotion request may carry the UEIP/ID, the priority flow processing indication/QoS, and the data flow information, and may carry the service ID/application ID if necessary.

 Step 508: After receiving the request message of the trigger function, the PCRF queries whether the user of the SPR/UDC has subscribed to the high priority flow processing. (Querying whether the user subscribes to the high priority flow processing manner may also query the service or application used by the user. Whether the high priority stream processing implementation is signed, and if so, the session modification process is initiated according to the request.

 The PCRF also issues an updated PCC rule to the PCEF/BBERF, or ADC (Application Detection Control) rule to the TDF (Traffic Detection Function). The PCEF/BBERF/TDF updates the PCC/QoS/ADC rules, modifies or creates a new bearer, performs the binding of the enhanced QoS and related bearers, and sends a response message to the PCRF to feedback the execution result of the rule.

 Step 509: The PCRF returns an enhanced QoS modification response message (CCA Credit Control Answer) to the trigger function to notify whether the QoS modification is accepted. If the QoS modification is rejected, the relevant cause value is carried.

 Step 510: After the QoS is successfully upgraded, the trigger function sends an enhanced QoS confirmation request message to the UE, and the user is required to confirm whether the updated QoS is satisfied.

Step 511: After receiving the acknowledgement message of the trigger function, if the UE is satisfied with the updated (eg, boosted) service data flow and is willing to pay the fee for the priority flow processing, the UE confirms the message, and the UE confirms the message. A confirmation message will be sent to the trigger function. After receiving the acknowledgment response from the UE, the trigger function optionally returns an acknowledgment response message to the PCRF, and the operator will continue to provide the QoS after the promotion (for example, continuing the priority flow processing to provide high priority or high bandwidth resources). ). If the UE is not satisfied with the quality of service or user experience of the upgraded service data flow and is unwilling to pay additional priority processing fees, the user does not confirm the confirmation request (does not return a response message) or returns a negative acknowledgement message to the trigger. Function (ie if the user does not agree to perform the new quality of service to provide the service but does not make a negative acknowledgment, the terminal device optionally constructs a negative acknowledgment message to the trigger function according to the operator's requirements).

 If the user does not perform the confirmation, the terminal device may construct a negative acknowledgement and return to the network, so that the technical implementation can distinguish the abnormal situation that the user does not send the acknowledgement and the acknowledgement message is lost, but the specific processing is implemented according to the carrier network.

 In the above solution, the trigger function may set the QoS promotion timer Timer 1 in step 506 (the Timer 1 validity period should ensure that the normal PCRF initiated IP-CAN session modification update QoS processing is completed and the application service has been provided for the UE according to the new QoS. When the PCRFCCA acknowledgment message of step 509 is received and the Timerl expires, an acknowledgment request message is sent to the UE.

 The trigger function may also directly trigger an acknowledgment message to the UE after step 507, and the message prompts the user to be within a certain time interval (this time interval can effectively ensure that the IP-CAN session modification update initiated by the PCRF is completed and the new QoS has been pressed. The application service is provided for the UE, and the priority stream processing is confirmed, and the time rl is not required; the embodiment is not specifically limited according to the implementation arrangement.

 The trigger function may also enable the user acknowledgement timer Timer2 after sending the boost QoS acknowledgement request message in step 510.

 Step 511a: If the trigger function does not receive the acknowledgement receiving message of the user within a specified time (for example, timer2 duration), or receives the acknowledgement rejection message of the user, an update QoS request (for example, reducing the QoS request) is sent to the PCRF;

Step 511b: After receiving the QoS request message of the triggering function, the PCRF combines the subscription information and the local policy (for example, the user confirms that the preview timer of the updateQoS is timed out and needs to reply to the original QoS), and initiates an IP-CAN/GWcontrol/TDF session modification process. Update the relevant PCC/QoS/ADC rules to restore the original QoS of the service; Step 511c: After the QoS recovery process is completed or the QoS confirmation time expires, the processing of the service data flow by the network will be restored to the QoS before the UE requests the promotion.

 The QoS fallback mechanism is not within the scope of the solution, and the timeout mechanism between the network elements can be used to process the backoff time of the session modification, and the QoS before the update can be stored locally, or the Trigger node carries the downgrade QoS request message. The previous QoS information, or the request message carries the default QoS indication.

 In the above method, step 510 is an optional step. It is also possible to use the way the terminal itself triggers the update of the quality of service confirmation request.

 In the above process, if the trigger function is integrated with the PCRF, the interaction with the PCRF is handled as an internal interface. The interaction between all trigger functions and PCRF is all implemented as an internal function. The PCRF performs IP-CAN session modification, update, and confirmation of service quality based on the triggering of the trigger function.

 In the above process, in addition to the policy control, there is also a charging-related processing flow. For example, after updating the QoS, a new charging keyword may be issued in the new PCC rule (corresponding to a new charging rate), and PCRF, PCEF/ may exist. The interaction between the network element such as BBERF/TDF and the charging network element OCS/OFCS and other charging systems; this part of the processing is not included in the description of this solution, and will not be described in detail.

 The above steps 501-511 are the processing flow of the non-roaming scenario. In the service usage process, as shown in FIG. 6, if the UE roams to the visited place (the roaming home route scenario), the home PCRF needs to notify the triggering function that the UE has roamed. If the QoS is increased before, the UE needs to reconfirm whether it needs to maintain high QoS/high priority flow processing (if the user confirms the high QoS processing of the service, it may need to pay additional high priority flow processing fee), if the user confirms The visited location still provides high QoS for the UE. If the user does not confirm or negate the acknowledgment, the visited QoS will provide the service by default QoS; as shown in Figure 7, the specific steps are as follows: Step 512: HPCRF (Home PCRF) learns the UE Roaming occurs, sending a QoS confirmation indication to a trigger function (for example, a RAR message), notifying the UE to roam, and instructing the trigger function to send an acknowledgement message of the priority stream processing to the UE, requesting the UE to confirm whether the QoS service flow processing will continue to be used at the visited location;

The message may carry an acknowledgement indication, UEID/IP, QoS, and other service information that may exist, such as data flow information, service ID/application ID, and the like. Step 513: The trigger function sends an acknowledgement response message (for example, RAA) to reply to the indication request message of the HPCRF.

 Step 514: The trigger function sends a priority flow processing high QoS acknowledgment request message to the UE, requesting the user to confirm whether to retain the high QoS flow processing, if a positive acknowledgment message is returned (confirming that retaining high QoS may require additional tariff for this priority flow processing) If you do not agree to pay the additional priority stream processing fee, return a negative confirmation or no confirmation (if the user does not confirm, the terminal device may construct a negative confirmation to return to the network, which facilitates the technical implementation to distinguish the user from sending the confirmation and Confirm the abnormal situation of message loss, but the specific processing is implemented according to the carrier network); The processing flow, the trigger function can set the user confirmation timer Timer3 when sending the confirmation request, and if the timerout still does not receive the positive confirmation, initiate the lowering of the QoS. Processing flow);

 Step 515: After receiving the acknowledgement message of the trigger function, if the UE wants to reserve the high QoS and is willing to pay the fee for the priority stream processing, the UE confirms the message, and the UE sends an acknowledgement message to the trigger function. After receiving the acknowledgment response from the UE, the triggering function optionally returns an acknowledgment response message to the PCRF, and the operator will continue to provide high QoS for the service (for example, continuing priority flow processing to provide high priority or high bandwidth resources).

 If the UE is not willing to pay additional priority processing fees and does not want to use high priority flow processing/high QoS, the user does not acknowledge the acknowledgment request (does not return a response message) or returns a negative acknowledgment message to the trigger function (ie if the user disagrees) If the service is provided with high QoS but no negative acknowledgment, the terminal device optionally constructs a negative acknowledgment message to be sent to the trigger function according to the operator's requirement, and performs steps 515a-c.

 Step 515a: If the trigger function does not receive the acknowledgement receiving message of the user within a specified time (for example, timer3 duration), or receives the acknowledgement rejection message of the user, an update QoS request (for example, lowering QoS) is sent to the PCRF;

 Step 515b: After receiving the QoS request message of the triggering function, the HPCRF combines the subscription information and the local policy (for example, the user confirms that the timer that reserves the high QoS timeout needs to reduce the QoS), and initiates the IP-CAN/GWcontrol/TDF session modification process. Update the relevant PCC/QoS/ADC rules to restore the default QoS of the service;

Step 515c: The network restores the service data stream to the default QoS, and delivers the service data stream according to the default bearer QoS. In the description of the embodiment, the default processing of the roaming confirmation notification is low QoS processing, that is, the user does not confirm or negatively acknowledges the QoS (the default bearer provides the service); the user returns a positive acknowledgment and continues to maintain the high priority processing. The default processing method of the actual processing may also be that the default is high priority stream processing (that is, the user does not confirm or affirm the acknowledgment to provide the service with high priority after roaming), and if the user provides a negative acknowledgment, the QoS is lowered (using the default bearer as the Service provides QoS). This solution is not limited to the default processing method after specific roaming.

 The timers in the above embodiments, such as timer 1 and timer 2 of the trigger function, may be the same timer. According to the implementation requirements, this solution is not limited.

 The S9 session in the specific process and the roaming area in the above process is implemented according to the prior art; in addition, the scenario of the roaming local access, the notification confirmation and the QoS modification process are the same as above, and the description is not repeated.

 In the above roaming deployment, the trigger function is the home network element, the trigger function and the home PCRF, and the UE interaction. The actual network deployment can also directly interact with the trigger function of the UE and the visited trigger function and the visited PCRF (VPCRF). The VPCRF transmits the trigger function information to the HPCRF, depending on the carrier's deployment with the roaming protocol.

 Through the above process, the policy control process such as resource allocation and update when the operator provides the service of the non-cooperative third-party application provider to the user UE can be implemented; the user can upgrade or reduce the service quality/user experience according to the needs of the user, and change the operator to The service tariff rate corresponding to the consumed resources transmitted by the service;

Embodiment 2

Figure 8 is a generic introduction of the Generic Bootstrapping Architecture (GBA) solution for the current interaction between mobile operators and third-party application providers. In addition to the EPS network and the PCC architecture, GBA is introduced as a mobile operator. The authentication and authentication of the third-party application provider to provide related application services for the UE. In the figure, the Bootstrapping Server Function (BSF) is the functional entity in the operator's network. All GBA user security settings (GUSS) are stored in the HSS, and the BSF passes the interface with the HSS (Zh). Obtain user security information and authentication information. The UE and the BSF pass the authentication mechanism between the BSF and the UE. A session key (Ks) is generated, and a Net Application Function (NAF) is responsible for service control, and the session key can be obtained from the BSF. In this way, the NAF and the UE can have a shared key. This shared key provides security for subsequent applications, especially when the application session begins to authenticate the UE and NAF. Therefore, the operator can complete related authentication and authentication, and provide third-party application services for the contracted users.

 As shown in FIG. 9, the trigger function of the scheme is introduced on the basis of the GBA non-roaming network structure of FIG. 8, and the interface of the UE and the trigger function is added (here, the interface between the UE and the application function, and the http can be used. Protocol or other application layer signaling), an interface for triggering functions and PCRF is added (where Rx' is a similar Rx interface, which can communicate using the Diameter protocol). The trigger function is a new logic function, which can be deployed independently or integrated in other network elements. It supports communication with the application layer of the UE and communicates with the PCRF.

 The UE described in this embodiment accesses the 3GPP network in a non-roaming scenario, and uses the service of the third-party application service provider that has no cooperation relationship with the operator. The operator is responsible for the authentication and transmission resource allocation of the UE and the third-party application provider. The service quality is adjusted according to the requirements of the UE, and the UE needs to be notified. As shown in FIG. 10, the following steps are specifically included:

 Step 1001: The UE attaches to the home network, establishes a radio bearer, and creates an IP-CAN session. Step 1002: The UE accesses the Non-IMS AS/NAF, and uses the bootstrapping mode of the GBA, and the UE sends a registration request to the BSF to carry the UEID. Obtaining the subscription information and the authentication vector from the HSS, the BSF completes the authentication of the UE, generates the Ks and the B-TID, and returns the B-TID to the UE, and the UE sends an application request to the NAF/Non-IMS AS, carrying the B-TID. The NAFNon-IMS AS uses the BTID to initiate an authentication request to the BSF, and returns a response to the UE after successful. The UE establishes a secure session with the Non-IMS AS;

 Step 1003: The NAF/Non-IMS AS initiates an Rx session establishment request to the PCRF, and carries the UE ID/IP, the service ID/application ID, and the data flow related information to the PCRF. The PCRF obtains the contracted AS information from the SPR/UDC, and formulates and delivers the PCC rule to the PCEF to establish a related data bearer. Since the AS does not cooperate with the operator, the QoS is the default bearer QoS; and for the AS that does not cooperate, the QoS information and service information of the Rx interface and the PCRF are transmitted as an optional step;

Step 1004: Complete the creation of the bearer required for the service; the PCRF formulates the PCC/QoS rule according to the information sent by the client, such as the Non-IMS AS, the SPR/UDC, and the PGW, and sends the packet to the PCC/QoS rule. PCEF/BBERF; PCEF/BBERF installs and executes the relevant rules to complete the bearer binding. If there is no matching bearer, the bearer setup request is sent and the bearer is created. The PCRF delivers the rules and may also carry the relevant event trigger. Value, monitoring keywords and other information; PCEF sets and executes related event reports and usage monitoring functions after receiving the information;

 Step 1005: The service bearer is created, and the network provides the UE with downlink transmission of the service data according to the authorized QoS.

 Step 1006-1015C: During the service process, the UE finds that the quality of service QoS or the user experience is not satisfactory (for example, the data stream transmission is unstable or the bandwidth is too low due to mobility or network conditions), and the UE initiates an elevation QoS request to the operator. The request process and the operator update the QoS according to the user request and send an acknowledgment message to the user, and the related processing according to the user confirmation to continue or adjust the QoS is the same as steps 506-515c.

Embodiment 3

 Figure 11 is another solution for introducing the interaction between the mobile operator and the third-party application provider to introduce the GBA and OpenID architecture; Open ID is a solution for implementing unified authentication across the entire network: When the end user UE logs in to support an Open ID The website, that is, the Relying Party (RP), is different from the way the user logs in on the website (the end user may not have registered with the website), and the user has chosen to log in to the website as Open ID. . The Open ID is a Uniform Resource Locator (URL) registered by the user on another website, the OpenID Provider (OP). The RP will discover the OP according to the Open ID provided by the user, and then request the OP to authenticate the identity of the user. After receiving the RP request, the OP will ask the user to log in to the OP authentication page for authentication. After the authentication, the OP will remind the user whether to allow external website authentication. After the user agrees, the OP returns the authentication result to the relying party RP; the OP authentication here uses the GBA boot mode, and the OP is equivalent to the NAF in the GBA architecture.

Figure 12 shows the trigger function of the scheme based on the OpenID and GBA network structure based on Figure 11, and the interface of the UE and the trigger function (here, the interface between the UE and the application function, which can use the http protocol or other applications. Layer signaling), the interface for triggering function and PCRF is added (where Rx' is similar to Rx interface, which can communicate with Diameter protocol). The trigger function is a new logic function, which can be deployed independently or integrated in other network elements. Supports application layer communication with the UE. Communicate with the diameter of the PCRF.

 As shown in Figure 13, the following steps are specifically included:

 Step 1301: The UE attaches to the home network, establishes a radio bearer, and creates an IP-CAN session. Step 1302: The UE requests to log in to the RP website (third-party application provider), and selects to log in by using the Open ID method; the RP discovers the OP by standardizing the Open ID of the user, and establishes a secure channel with the OP for transmitting information (for example, an RP request). The OP authenticates the user identity, ;); The RP returns the Open Id login interface to the end user, or redirects the user to the OP; the user logs in to the OP, OP authenticates the user, and requests the user to perform login authentication (here used) The GBA authentication method); the UE sends a registration request to the BSF, and carries the UEID; the BSF obtains the subscription information and the authentication vector from the HSS, and the BSF completes the authentication of the UE, generates the Ks and the B-TID, and returns the B-TID to The UE sends an application request to the NAF/OP to carry the B-TID. The NAF/OP uses the BTID to initiate an authentication request to the BSF, and returns a response to the UE after success. The UE establishes a secure session with the NAF/OP. The OP returns the authentication result to the RP. The RP analyzes the result of the OP. If the user is authenticated, the user is authenticated successfully. The RP service can be used. And certification;

 Step 1303: The RP/Non-IMS AS initiates an Rx session establishment request to the PCRF, and carries the UE ID/IP, Service ID/application ID, and flow information related information to the PCRF „PCRF to obtain the contract AS information from the SPR/UDC, and formulates and The PCC rule is sent to the PCEF to establish the relevant data bearer. Since the AS does not cooperate with the operator, the authorized QoS is the default bearer QoS; and for the AS without cooperation, the QoS information and service information of the Rx interface and the PCRF are optional steps. Step 1304: Complete the creation of the bearer required for the service; the PCRF formulates the PCC/QoS rule according to the information sent by the client, such as the Non-IMS AS, the SPR/UDC, the PGW, and the like, and delivers the PCC/QoS rule to the PCEF/BBERF; PCEF/BBERF installation And the related rules are executed to complete the bearer binding. If there is no matching bearer, the bearer setup request is sent and the bearer is created. The PCRF sends the rules, and may also carry related event triggers, usage monitoring thresholds, and monitor keywords. PCEF sets and executes related event reports and usage monitoring functions after receiving the information;

 Step 1305: The service bearer is created, and the network provides the downlink transmission of the service data to the UE according to the authorized QoS.

Steps 1306-1315C: During the service process, the UE finds that the quality of service QoS or user experience is not full. Meaning (for example, due to mobility or network conditions, data streaming is unstable or bandwidth is too low, etc.)

The UE initiates an elevation QoS request to the operator. The request process and the operator update the QoS according to the user request and send an acknowledgment message to the user, and the related processing according to the user confirmation to continue or adjust the QoS is the same as the steps 506-515c.

Embodiment 4

 As shown in FIG. 14, this embodiment enhances the PCRF with the trigger function based on the architecture of FIG. 2, and adds an interface between the UE and the PCRF (here, the http protocol or other application layer signaling may be used).

 The UE described in this embodiment accesses the 3GPP network in a non-roaming scenario, and uses the service of the third-party application service provider that has no cooperation relationship with the operator. The operator is responsible for providing transmission resources for the third-party application of the UE, and can adjust the quality of service according to the requirements of the UE and notify the UE to confirm. As shown in FIG. 15, the method for updating and confirming the quality of service includes the following steps:

 Step 1501: The UE attaches to the home network, establishes a radio bearer, and creates an IP-CAN session. Step 1502: The UE logs in and successfully accesses the Non-IMS AS, and the non-IMS AS provides an application service for the UE. The UE and the Non-IMS AS can use the HTTP protocol and application layer signaling when communicating.

 Step 1503: The Non-IMS AS and the PCRF execute the PCC process.

 The Non-IMS AS initiates an Rx session establishment request to the PCRF, which may carry the UE ID/IP, the service ID/application ID, and the data flow related information. The PCRF obtains the contracted AS information from the SPR/UDC, and formulates and delivers the PCC rules to the PCEF to establish related data bearers.

 Because the AS does not cooperate with the operator, the QoS is the default bearer QoS; and for the AS without cooperation, the QoS information and service information of the Rx interface and the PCRF are optional steps.

 Step 1504: Complete the creation of the bearer required for the service.

Specifically, the PCRF formulates the PCC/QoS rules according to the information sent by the client, such as the AS, the SPR/UDC, and the PGW, and delivers the PCC/QoS rules to the PCEF/BBERF. The PCEF/BBERF installs and executes the relevant rules to complete the bearer binding. The bearer sends a bearer setup request to create a bearer. The PCRF may also carry related event triggers, as well as usage monitoring thresholds, monitoring keywords, and other information. PCEF receives and executes related event reports after receiving the information. Dosage monitoring •6匕

Fj匕.

 Step 1505: The service bearer is created, and the network provides the UE with downlink transmission of the service data according to the authorized QoS.

 Step 1506: In the service process, the UE finds that the quality of service QoS or the user experience is not satisfactory (for example, due to factors such as unstable data flow or low bandwidth due to mobility or network conditions), and the UE initiates to the PCRF that enhances the trigger function. QoS promotion request.

 The QoS promotion request may carry the UEIP/ID, the priority flow processing indication/QoS, and the data flow information, and may carry the service ID/application ID if necessary.

 The communication protocol between the UE and the PCRF is not limited, and the http or application layer signaling can be implemented. Step 1507: After receiving the request message of the UE, the PCRF queries whether the user of the SPR/UDC has subscribed to the high priority flow processing. (Querying whether the user subscribes to the high priority flow processing manner may also query whether the service or application used by the user is used. The high priority stream processing implementation is contracted), and if so, the session modification process is initiated according to the request.

 The PCRF also issues an updated PCC rule to the PCEF/BBERF, or ADC rules to the TDF. The PCEF/BBERF/TDF updates the PCC/QoS/ADC rules, modifies or creates a new bearer, performs the enhanced QoS and related bearer binding, and sends a response message to the PCRF to feedback the rule execution result.

 Step 1508: The PCRF returns an enhanced QoS modification response message to the UE to notify whether the QoS modification is accepted. If the QoS modification is rejected, the relevant cause value is carried.

 Step 1509: After the QoS is successfully upgraded, the PCRF optionally sends an enhanced QoS confirmation request message to the UE, asking the user to confirm whether the updated QoS is satisfactory. Or the confirmation indication is carried in step 1508.

Step 1510: After receiving the acknowledgement message of the PCRF, if the UE is satisfied with the updated (for example, boosted) service data flow and is willing to pay the fee for the priority flow processing, the UE confirms the message, and the UE sends a confirmation message to the UE. With the PCRF, the operator will continue to provide enhanced QoS for the service (for example, continue with priority flow processing to provide high priority or high bandwidth resources). If the UE is not satisfied with the quality of service or user experience of the upgraded service data flow and is unwilling to pay additional priority processing fees, the user does not confirm the confirmation request (does not return a response message) or returns a negative confirmation. The message is sent to the PCRF (ie, if the user does not agree to perform the new quality of service to provide the service but does not make a negative acknowledgment, the terminal device optionally constructs a negative acknowledgment message to the PCRF according to the operator's requirements).

 If the user does not perform the confirmation, the terminal device may construct a negative acknowledgement and return to the network, so that the technical implementation can distinguish the abnormal situation that the user does not send the acknowledgement and the acknowledgement message is lost, but the specific processing is implemented according to the carrier network.

 In the above solution, the PCRF may set the QoS promotion timer Timer in step 1507 (the validity period of the Timer should ensure that the IP-CAN session modification update QoS initiated by the normal PCRF is completed and the application service has been provided for the UE according to the new QoS), Timerl Timeout, sending a confirmation request message to the UE. The embodiment is not limited according to the implementation.

 The PCRF may also enable the user acknowledgement timer Timer2 after sending the boost QoS acknowledgement request message in step 1509.

 Step 1510a: If the user confirms the rejection, an update QoS request (for example, reducing the QoS request) is sent to the PCRF;

 Step 1510b: If the PCRF does not receive the acknowledgment receiving message from the user within a specified time (for example, the duration of the timer 2), or the PCRF receives the QoS request message from the UE, the binding information and the local policy are combined (for example, the user confirms that the update QoS is received by the Preview timer 2). The timeout needs to restore the original QoS), initiate the IP-CAN/GWcontrol/TDF session modification process, update the relevant PCC/QoS/ADC rules, and restore the original QoS of the service;

 Step 1510c: After the QoS recovery process is completed or the QoS confirmation time expires, the processing of the service data stream by the network will be restored to the QoS before the UE requests the promotion.

 The QoS fallback mechanism is not within the scope of the solution. For example, the timer mechanism between the network elements can be used to process the backoff time of the session modification. The QoS before the update can be stored locally, or the UE carries the previous QoS request message. The QoS information, or the request message carries the default QoS indication, and the like.

 In the above method, step 1509 is an optional step. It is also possible to use the way the terminal itself triggers the update of the quality of service confirmation request.

In the above process, the PCRF integrates or enhances the trigger function, and the PCRF performs IP-CAN session modification, update, and confirms the quality of service according to the trigger of the internal trigger function. In the above process, in addition to the policy control, there is also a charging-related processing flow. For example, after updating the QoS, a new charging keyword may be issued in the new PCC rule (corresponding to a new charging rate), and PCRF, PCEF/ may exist. The interaction between the network element such as BBERF/TDF and the charging network element OCS/OFCS and other charging systems; this part of the processing is not included in the description of this solution, and will not be described in detail.

 The above steps 1501-1510 are the processing flow of the non-roaming scenario. During the service usage, as shown in FIG. 16, if the UE roams to the visited place (the roaming home route scenario), the home PCRF needs to notify the trigger function that the UE has roamed. If the QoS is increased before, the UE needs to reconfirm whether it needs to maintain high QoS/high priority flow processing (if the user confirms the high QoS processing of the service, it may need to pay additional high priority flow processing fee), if the user confirms The visited location still provides high QoS for the UE. If the user does not confirm or negate the acknowledgment, the visited QoS will provide the service by default QoS; as shown in Figure 17, the specific steps are as follows:

 Step 1511: The HPCRF learns that the UE has roamed, sends a QoS confirmation indication message to the UE, notifies the UE to roam, and sends an acknowledgement indication of the priority flow processing to the UE, requesting the UE to confirm whether the QoS priority service flow processing will continue to be used in the visited place;

 The message may carry an acknowledgement indication, UEID/IP, QoS, and possibly other service information, such as data flow information, service ID/application ID, and the like.

 Step 1512: The trigger function sends a priority flow processing high QoS acknowledgment request message to the UE, asking the user to confirm whether to reserve high QoS flow processing, and if yes, returning a positive acknowledgment message (confirming that retaining high QoS may need to provide additional for this priority stream processing) If you do not agree to pay the additional priority stream processing fee, return a negative confirmation or no confirmation (if the user does not confirm, the terminal device may construct a negative confirmation to return to the network, which facilitates the technical implementation to distinguish the user from sending To confirm and confirm the abnormal situation of the lost message, but the specific processing is implemented according to the carrier network, perform steps 1513a-c. In the processing flow, the PCRF may set a user confirmation timer Timer3 when sending an acknowledgment request, and initiate a QoS reduction process if the timeout still does not receive a positive acknowledgment;

 Step 1513a: If the PCRF does not receive the acknowledgement receiving message of the user within a specified time (for example, timer3 duration), or receives the acknowledgement rejection message of the user, the UE will optionally send an update QoS request (for example, reduce QoS) to the PCRF. ;

Step 1513b: The HPCRF receives the UE's reduced QoS request message or negative acknowledgement response message. After that, combined with the subscription information and the local policy (for example, the user confirms that the high QoS timer expires, the QoS needs to be reduced), initiates the IP-CAN/GWcontrol/TDF session modification process, updates the relevant PCC/QoS/ADC rules, and restores the service. Default QoS;

 Step 1513c: Complete the session modification, restore the default QoS for the service data flow, and deliver the service data flow according to the default bearer QoS. If the UE sends a 1513a request QoS downgrade to the PCRF, the PCRF sends an Ack message to the UE as a response.

 In the description of the embodiment, the default processing of the roaming acknowledgement notification is low QoS processing, that is, the user does not acknowledge or negatively acknowledge the QoS (the default bearer provides the service); the user returns to the positive acknowledgement and continues to maintain the high priority processing. The default processing method of the actual processing may also be that the default is high priority stream processing (that is, the user does not confirm or affirm the acknowledgment to provide the service with high priority after roaming), and if the user provides a negative acknowledgment, the QoS is lowered (using the default bearer as the Service provides QoS). This solution is not limited to the default processing method after specific roaming.

 The timers in the above embodiments, such as timer 1 and timer 2 of the trigger function, may be the same timer. According to the implementation requirements, this solution is not limited.

 The S9 session in the specific process and the roaming area in the above process is implemented according to the prior art; in addition, the scenario of the roaming local access, the notification confirmation and the QoS modification process are the same as above, and the description is not repeated.

 The above roaming deployment is based on the home location PCRF enhanced triggering function and interacts with the UE. The actual network deployment can also directly interact with the UE and the visited PCRF (VPCRF enhanced trigger function), and then the VPCRF transmits information to the HPCRF, depending on the carrier deployment to the roaming protocol.

 Through the above process, the policy control process such as resource allocation and update when the operator provides the service of the non-cooperative third-party application provider to the user UE can be implemented; the user can upgrade or reduce the service quality/user experience according to the needs of the user, and change the operator to The service tariff rate corresponding to the consumed resources transmitted by the service;

Based on the method of FIG. 3-2, an embodiment of the PCRF enhanced trigger function based on the network structure based on GBA and OpenID, with reference to the comparison of Embodiments 2 and 3 with Embodiment 1, and FIGS. 15, 16, 17; Repeat the description. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other. It is a matter of course that the invention may be embodied in various other forms and modifications without departing from the spirit and scope of the invention.

 One of ordinary skill in the art will appreciate that all or a portion of the above steps may be accomplished by a program instructing the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

Industrial applicability

 This solution can ensure that users can provide service quality according to user requirements when using services of third-party application providers that do not have a cooperative relationship with operators.

Claims

Claim

 1. A service quality update method for a policy and charging rule, comprising:

 The terminal interacts with the triggering function to request or confirm an update of the service quality of the service accessed by the terminal;

 The trigger function interacts with a policy charging rule function (PCRF), and the PCRF performs an IP-Connected Access Network (IP-CAN) session modification according to the request of the triggering function to update the service quality of the service.

 2. The method according to claim 1, wherein the PCRF entity performs an IP-CAN session modification, and the step of updating the quality of service of the service includes:

 After receiving the request for updating the quality of service of the service sent by the triggering function, if the PCRF determines that the terminal has subscribed to the high priority flow processing, performing the IP-CAN session modification to update the service of the service. quality.

 3. The method of claim 1 further comprising:

 After the service quality update of the service is completed, the trigger function sends an update service quality confirmation request to the terminal or the terminal itself triggers an update service quality confirmation request;

 If the terminal agrees to perform the updated quality of service, it returns an update confirmation response to the trigger function, and if it does not agree to perform the updated quality of service, returns an update denied response or does not return a response to the trigger function.

 4. The method of claim 1 further comprising:

 After the service quality update of the service is completed, if the terminal agrees to perform the updated service quality, the terminal returns an update confirmation response to the trigger function, and if it does not agree to perform the updated service quality, returns to the trigger function. Update the denied response or not return a response.

 5. The method of claim 1 further comprising:

 After the terminal is roaming, the home PCRF notifies the trigger function that the terminal is roaming, and the trigger function sends an update service quality confirmation request to the terminal.

 6. The method of claim 3, 4 or 5, further comprising:

After the trigger function knows that the terminal does not agree to the updated service quality, sending a negative acknowledgement Giving the PCRF, the PCRF initiates the IP-CAN session modification, and re-updates the quality of service of the service, including reducing the quality of service of the service or restoring the original quality of service of the service.

 7. The method of claim 1, wherein

 The trigger function is a logical function entity having an application function, which is integrated in the PCRF, or deployed in a network application function (NAF) or a non-IP multimedia subsystem application service (non-IMS AS) or a relying party (RP). And interacting with the PCRF through a protocol that meets the communication requirements of the two, the protocol including the Diameter protocol.

 8. A service quality update method for a policy and charging rule, comprising:

 The terminal interacts with the Policy Charging Rules Function (PCRF) to request or confirm an update of the quality of service of the service accessed by the terminal;

 The PCRF performs an IP-CAN session modification according to the trigger of the terminal, and updates the service quality of the service.

 The method according to claim 8, wherein the PCRF performs an IP-CAN session modification, and the step of updating the quality of service of the service includes:

 After the PCRF receives the request for updating the quality of service of the service sent by the terminal, and determines that the terminal has subscribed to the high priority flow processing, performing the IP-CAN session modification to update the service quality of the service. .

 10. The method of claim 8 further comprising:

 After the service quality update of the service is completed, the PCRF sends an update service quality confirmation request to the terminal or the terminal itself triggers an update service quality confirmation request;

 If the terminal agrees to perform the updated quality of service, it returns an update confirmation response to the PCRF; if it does not agree to perform the updated quality of service, it returns an update denied response to the PCRF or does not return a response.

 11. The method of claim 8 further comprising:

After the service quality update of the service is completed, if the terminal agrees to perform the updated quality of service, the terminal returns an update confirmation response to the PCRF, and if it does not agree to perform the updated quality of service, returns an update rejection to the PCRF. Respond or not return a response.

12. The method of claim 8 further comprising:

 After the terminal roams, the home PCRF sends an update service quality confirmation request to the terminal.

 13. The method of claim 10, 11 or 12, further comprising:

 After the PCRF learns that the terminal does not agree to the updated service quality, the IP-CAN session modification is initiated, and the service quality of the service is re-updated, including reducing the quality of service or restoring the original service quality.

 14. A service quality update system for policy and charging rules, comprising a terminal and a policy charging rule function (PCRF), wherein

 The system also includes a trigger function;

 The terminal is configured to interact with the trigger function to request or confirm an update of a quality of service of a service accessed by the terminal;

 The triggering function is configured to interact with the PCRF, requesting the PCRF to initiate an IP connection access network (IP-CAN) session modification process to update the service quality of the service;

 The PCRF is configured to perform an IP-CAN session modification to update the quality of service of the service.

 15. The system of claim 14 wherein

 The PCRF is configured to perform the IP-CAN session modification, and update the IP address when the terminal has signed the high priority flow processing after receiving the request for updating the service quality of the service sent by the trigger function. The quality of service of the business.

 16. The system of claim 14 wherein

 The triggering function is further configured to: after the terminal does not agree to the updated quality of service, send a negative acknowledgement to the PCRF, trigger the PCRF to initiate the IP-CAN session modification, and re-update the service quality of the service. , including reducing the quality of the service or restoring the original quality of service.

 17. A service quality update system for policy and charging rules, comprising a terminal and a policy charging rule function (PCRF), wherein

The terminal is configured to interact with the PCRF to request or confirm an update of a quality of service of a service accessed by the terminal; The PCRF is configured to perform an IP-Connected Access Network (IP-CAN) session modification according to the trigger of the terminal, and update the quality of service of the service.

 18. The system of claim 17, wherein

 The PCRF is configured to perform the IP-CAN session modification and update the service when it is determined that the terminal has subscribed to the high priority flow processing after receiving the request for updating the quality of service of the service sent by the terminal. Quality of service.

 19. The system of claim 17, wherein

 The PCRF is further configured to initiate the modification of the IP-CAN session and re-update the quality of service of the service after learning that the terminal does not agree to the updated quality of service, including reducing the quality of service or restoring the original quality of service.