WO2013178183A1

WO2013178183A1 - Quality of service update processing method and device

Info

Publication number: WO2013178183A1
Application number: PCT/CN2013/080445
Authority: WO
Inventors: 吴锦花; 周晓云
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-08-01
Filing date: 2013-07-30
Publication date: 2013-12-05
Also published as: CN103582030B; CN103582030A

Abstract

Provided are a quality of service update processing method and device. The abovementioned method comprises: a UE obtaining the cooperative relationship between an application provider and an operator; and the UE requesting a quality of service (QoS) update according to the obtained cooperative relationship. The abovementioned technical solution provided in the present invention solves the technical problems in the related art, e.g. that there is still no method which enables a UE to correctly recognize the cooperative relationship between an application provider and an operator when no service cooperation exists between a third-party application provider and the operator while much internal hardware caching space is consumed due to the fact that multipath information of a user is managed, thereby enabling the UE to correctly process (such as update) QOS according to the cooperative relationship between the application provider and the operator.

Description

Service quality update processing method and device

TECHNICAL FIELD The present invention relates to the field of communications, and in particular, to an update processing method and apparatus for Quality of Service (QoS). BACKGROUND OF THE INVENTION FIG. 1 is a schematic diagram of a 3rd Generation Partnership Project (3GPP) evolved packet system structure. As shown in FIG. 1 , an Evolved Packet System (EPS) is evolved by a generalized Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Mobility Management Entity (MME), Serving Gateway (S-GW), grouping A data network gateway (Packet Data Network Gateway, abbreviated as PDN GW or P-GW), a Home Subscriber Server (HSS), and 3GPP Authenticated Authorization and Accounting (AAA) server The Policy and Charging Rules Function (PCRF) and other supporting nodes are formed. 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 P-GW forwards data and buffers 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 classified 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 through an Evolved Packet Data Gateway (ePDG), ePDG and The P-GW is an S2b interface. The S2c interface provides user plane-related control and mobility support between the user equipment (User Equipment, UE for short) and the P-GW. The supported mobility management protocol supports dual-port mobile IPv6 (Moblie IPv6 support for dual stack). Hosts and Routers, referred to as DSMIPv6).

The EPS system introduces the Policy and Charging Control (PCC) functional framework to dynamically policy charge control for user service access. Figure 2 is a schematic diagram of the PCC structure in a non-roaming scenario in the Rel-11. As shown in Figure 2, an application function (Application Function, AF) is used to For access points for business applications, the network resources used by these business applications require dynamic policy control. When the parameters are negotiated on the service plane, the AF delivers related service information to the PCRF. If the service information is consistent with the policy of the PCRF, 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 (User Equipment, UE for short). The interface between the AF and the PCRF is an 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 traffic data flows, including traffic data flow detection, Gating Control QoS control, and data flow based charging rules. The PCRF sends its policy and charging rules to the Policy and Control Enforcement Function (PCEF). 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 policies and charging rules by the PCRF includes: obtaining information related to the service from the AF, obtaining subscription information related to the user policy charging control from the Subscription Profile Repository (SPR), and the PCEF through the Gx interface. Acquired information about the bearer-related network.

The PCEF is usually located in the gateway (Gate-Way, GW for short), and performs the policy and charging rules defined 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. If it is online charging, Bayu PCEF needs to conduct credit management with Online Charging System (OCS). When offline charging, the PCEF exchanges relevant charging information with the Offline Charging System (OFCS). The interface between the PCEF and the PCRF is a Gx interface, the interface between the OCE and the OCS is a Gy interface, and the interface between the OFCS and the OFCS is a Gz interface. The PCEF is generally located on the gateway of the network, such as the Packet Data Network Gateway (PDN-GW) of the EPS and the Gateway General Packet Radio Service Support Node (General Packet Radio Service (GPRS) in the General Packet Radio Service (GPRS). The Service Supporting Node (referred to as GGSN) and the Packet Data Gateway (PDG) in the Interworking WLAN (I-WLAN). The Bearer Binding and Event Reporting Function (BBERF) is usually located in the Access Network Gateway (ANG). For example, when the user equipment accesses the EPS through the E-UTRAN, and the Proxy Mobile Internet Protocol version 6 (PMIPv6) protocol is used between the serving gateway S-GW and the P-GW, the S-GW There is a BBERF in it. When the user equipment accesses through the trusted non-3GPP access network, the 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 complete the charging operation in the offline charging mode.

The interface between the OCS and the PCRF is a Sy interface, and the charging policy session on the interface is used to transmit charging related information. The PCRF obtains charging related information from the OCS as one of the basis information for formulating PCC/QoS rules. After the OCS detects the authorization quota (for example, the usage threshold), it can initiate a charging policy report to the PCRF, trigger the PCRF to initiate a session modification process, and update the related rules. The above PCC architecture implements a policy plan for an 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. The mobile operator uses the functional framework of the Interworking between Mobile Operators using the Evolved Packet System and Data Application Providers (Simplified MOSAP) to introduce a Generic Bootstrapping Architecture (abbreviation). For the security mechanism of GBA) and Open ID, in addition to the PCC architecture in Figure 2, the GBA is used as the mobile operator to authenticate and authenticate the third-party application provider to provide relevant application services for the UE. Figure 3 is a schematic diagram of the structure of a third-party owned data application provider in a non-roaming scenario in R12. As shown in Figure 3, the Non-IMS AS is a third-party application server. Similar to AF, it can interact with the PCRF to provide corresponding service QoS information, and interact with the HSS to obtain related user subscription information. GBA (including Bootstrapping Server Function-BSF, Network Application Function - NAF and SLF) is intended to describe the use of 3GPP-based AKA mechanisms to provide shared keys for clients (UEs) and application servers (non-IMSAS) in a mobile context. The shared secret can then be used to authenticate communications between the client (UE) and the application server (non-IMSAS). Here GBA is used to support secure communication between the UE and the RP. 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. The BSF obtains the user through the interface (Zh) with the HSS. Safety information and certification information. A session key (Ks) is generated between the UE and the BSF through the authentication mechanism between the BSF and the UE, and the network application function (Net) Application Function (NAF for short) is responsible for service control and can obtain the session key from the BSF. In this way, NAF and UE can have a shared key, which can provide security for subsequent applications, especially The UE and NAF are authenticated at the beginning of the application session. Therefore, the operator can complete related authentication and authentication, and provide third-party application services for the contracted users. The Open ID is a solution for implementing unified authentication on the entire network. When the terminal user UE logs in to a website that supports Open ID, that is, the Relying Party (RP), the user login mode is different from that on the website. Perhaps not registered on the site), the user chose to log in to the site as an 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 0P according to the Open ID provided by the user, and then request the 0P to authenticate the identity of the user. After receiving the RP request, the 0P will ask the user to log in to the 0P authentication page for authentication. After the authentication, 0P will remind the user whether to allow the external website to authenticate it. After the user agrees, the OP returns the authentication result to the relying party RP; the OP authentication here adopts the GBA boot mode, and the OP is equivalent to the NAF in the GBA architecture. In the prior 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 the modification process of the IP-CAN session.

The PCRF combines the QoS of the new AF request with the corresponding subscription data of the SPR/UDC, re-authorizes the underlying network bearer resource information, and issues a new PCC/QoS rule to the PCEF/BBERF. The PCEF/BBERF updates the corresponding rule and modifies the bearer resource. The service provides new QoS. For non-IMS services (such as the services provided by the non-IMS AS in Figure 3), operators can deploy networks according to their own needs, customize non-IMS service platforms and data centers, and trigger their PCRF initiation through custom interfaces. The IP-CAN session modifies the process to change the QoS. 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 the IP-CAN session modification process to change the QoS through the custom interface. At present, the number and types of third-party application providers on the network are increasing. The carrier's own services are far from meeting the business needs of the users. The cooperation between the operators and some application service providers is established. There is an Rx interface between the IMS AS and the PCRF to provide a good service quality and application experience for the user's application service, and collect the due profit from the network transmission resources that it should provide. However, it is impossible for operators to have commercial cooperation with all application providers (in this scenario, there is no Rx interface between non-IMS AS and PCRF). For the service of a third-party application provider that does not have a cooperative relationship with the operator (there is no Rx interface between the non-IMS AS and the PCRF), the operator provides default QoS, but the user can initiate a request to obtain the fee by paying an additional fee. High QoS for the service. There are two types of third-party application providers that do not have a cooperative relationship with the carrier. The first category has no commercial relationship with the operator and does not have any business collaboration. The second category has no commercial relationship with the operator but no business collaboration. . For the third-party application provider of the first type, the user can only initiate the QoS request for the service to be upgraded by the operator, and the carrier can modify the relevant bearer resources of the service to meet the requirements of the user, and bear the additional QoS for the high QoS. . For a third-party application provider of the second type, the user may initiate a QoS request for the service to the third-party application provider, and the third-party application provider triggers the operator to modify the relevant bearer resource of the service to meet the user's needs, and The QoS bill for the high QoS extra billing is provided by the third-party application provider, and the request for promotion can be directly initiated with the operator as in the first category. In the related art, for the first type and the operator, there is no business relationship and no service cooperation. When the UE needs to improve the QoS, the UE may notify the GW by using the bearer resource modification process, and trigger the PCRF to initiate an IP-CAN session modification. The QoS re-authorization of the service; the UE may directly notify the operator of the AF-related service and the QoS promotion request, and trigger the PCRF to initiate the foregoing process. For the scenario where the second type has a business relationship with the operator but does not have any service cooperation, the UE may notify the DAP to enhance the request, and the DAP and the operator's PCRF interact to trigger the foregoing process; or the UE may directly trigger the QoS with the operator. Including the above-mentioned bearer resource modification process trigger or AF trigger. However, the above two types of scenarios exist in the actual operation network. The UE needs to perform corresponding processing according to different scenarios. Therefore, how to correctly distinguish between these two types of scenarios and make correct choices according to requirements becomes a key issue that must be solved. To summarize the above problems, it can be seen that, when there is a service provided by a third-party application provider in the network, and there is no service cooperation between the third-party application provider and the operator, how to enable the UE to process the QoS according to the operator or the UE for the related service. The correct handling of the requirements is a problem that needs to be solved. In view of the above problems in the related art, an effective solution has not yet been proposed. SUMMARY OF THE INVENTION In the related art, when there is no service cooperation between the third-party application provider and the operator, there is no technical problem that the UE correctly identifies the cooperation relationship between the application provider and the operator, and the embodiment of the present invention provides a service. The quality update processing method and apparatus are to solve at least the above problems. According to an embodiment of the present invention, a method for updating a quality of service is provided, including: a user equipment (UE) acquires a cooperation relationship between an application provider and an operator; and the UE requests a quality of service QoS update according to the acquired cooperation relationship. The above collaboration relationship includes one of the following: application collaboration exists between the application provider and the operator; the application provider and the operator do not have business collaboration and business relationship; the application provider and the operator only have a business relationship but no business collaboration.

The UE requests the QoS update according to the acquired collaboration relationship, including: When the application provider and the operator do not have the service cooperation and the business relationship, the UE directly sends a request to the operator, requesting the operator to update the QoS.

The UE requests the QoS update according to the acquired cooperation relationship, and includes: when the application provider and the operator only have a commercial relationship but no service cooperation, the UE initiates the update process of the QoS according to the cooperation relationship in one of the following manners: the UE directly to the operator Initiating a request, triggering an operator to perform update processing on the QoS; the UE initiates a request by the application provider to trigger the operator to perform update processing on the QoS. The UE acquires the cooperation relationship between the application provider and the operator, including: the UE receives the collaboration relationship sent by the application provider; or the UE receives the collaboration relationship sent by the operator.

The UE receives the cooperation relationship sent by the operator, and includes: the UE acquires the collaboration relationship from the application layer signaling or protocol sent by the application function AF entity of the operator; or the UE acquires the collaboration relationship from the bearer layer signaling of the operator. According to another embodiment of the present invention, a service quality update processing apparatus is provided, located in a UE, the apparatus comprising: an obtaining module, configured to acquire a collaboration relationship between an application provider and an operator; and a request module, configured to The acquired collaboration relationship requests a quality of service QoS update. The obtaining module is configured to obtain one of the following collaboration relationships: the application provider and the operator have business collaboration; the application provider and the operator have no business collaboration and business relationship; the application provider and the operator only have a business relationship but no business collaboration . The request module is configured to initiate a request to the operator directly when the application provider and the operator do not have a business collaboration and a business relationship, and request the operator to perform update processing on the QoS. The above request module is configured to initiate a process of updating the QoS according to the collaboration relationship when the application provider and the operator only have a commercial relationship but no service cooperation: directly initiate a request to the operator, and trigger the QoS of the operator. An update process is performed; the request is initiated by the application provider to trigger the operator to perform update processing on the QoS. The obtaining module is configured to receive a collaboration relationship sent by the application provider, or receive a collaboration relationship sent by the operator. Through the invention, the UE adopts the technical means for acquiring the cooperation relationship between the application provider and the operator, and solves the related technology, and the management of the multipath information of the user consumes more hardware internal cache space in the third party application provider and the operator. When there is no service collaboration, there is no technical problem that enables the UE to correctly identify the cooperation relationship between the application provider and the operator, so that the UE correctly processes (updates) the QOS according to the acquired cooperation relationship between the application provider and the operator. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a schematic structural diagram of a 3GPP evolved packet system according to the related art; FIG. 2 is a schematic diagram of a PCC structure in a Rel-11 non-roaming scenario according to the related art; FIG. 3 is a Rel-12 non-roaming according to the related art. FIG. 4 is a flowchart of a method for updating a quality of service according to Embodiment 1 of the present invention; FIG. 5 is a structural block diagram of an apparatus for updating quality of service according to Embodiment 1 of the present invention; A first flowchart of a method for updating quality of service according to Embodiment 2 of the present invention; FIG. 7 is a second flowchart of a method for updating quality of service according to Embodiment 2 of the present invention; FIG. 8 is an update of quality of service according to Embodiment 2 of the present invention; FIG. 9 is a first flowchart of a method for updating quality of service according to Embodiment 3 of the present invention; FIG. 10 is a second flowchart of a method for updating quality of service according to Embodiment 3 of the present invention; A third flowchart of the method for updating the quality of service according to Embodiment 3 of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. Considering the related technology, the application provider and the operator do not have any cooperative relationship in the two scenarios (that is, the first class and the operator do not have any commercial relationship and do not have any business cooperation, and the second class has a business relationship with the operator but does not have Under any business collaboration, there is no such thing as how to correctly distinguish between the two types of scenarios and make the right choices according to requirements. The related solutions are provided below in conjunction with the embodiments and will now be described in detail. Embodiment 1 FIG. 4 is a flowchart of a method for updating a quality of service according to Embodiment 1 of the present invention. As shown in FIG. 4, the method includes: Step S402: The UE acquires a collaboration relationship between an application provider and an operator. Step S404: The UE requests a QoS update according to the acquired collaboration relationship. Regardless of whether there is service collaboration between the operator and the application provider, the foregoing processing steps enable the UE to perceive the cooperation relationship between the operator and the application provider, especially in the case where the operator and the application provider do not have business collaboration. The UE is configured to perceive the specific cooperation between the two, so that the UE can correctly distinguish the two scenarios and make the correct selection according to the requirements. For example, for the first scenario in the related technology, the QoS promotion can only be triggered by the operator. The second type of scenario in the related art may make a corresponding trigger selection according to an operator policy or a user's tendency. In the step S404, the implementation process of the QoS update process is known in the related art, and details are not described herein again. The above collaboration relationship may include one of the following situations: application provider and operator have business collaboration; application provider and operator have no business collaboration and business relationship; application provider and operator only have business relationship but no business collaboration. For the above-mentioned cooperation relationship, the update process of step S404 is also slightly different: when there is no service cooperation and business relationship between the application provider and the operator, the UE directly requests the operator to request the operator to perform QoS. Update processing. When there is only a commercial relationship between the application provider and the operator but no service cooperation, the UE initiates the update process of the QoS according to the cooperation manner in one of the following ways: In the first manner, the UE directly initiates a request to the operator, triggering the operator. The QoS is updated. In the second mode, the UE initiates a request by the application provider to trigger the operator to update the QoS. For the case where the application provider and the operator have business cooperation, the QoS update processing may be performed in the first manner or the second manner. Which processing method can be selected according to a predetermined policy: the operator defaults to the first mode or the second mode; sets the priority of the first mode and the second mode; in response to the user's selection operation, from the pre-configured Selecting one of the first mode and the second mode; determining the first mode or the second mode according to different QoS attribution parties, for example, a charging policy that can be combined with the service It is decided that, for example, the tariff of the special QoS belongs to the application provider, and the second mode is selected. The tariff of the special QOS is attributed to the operator's bill, and the first method is selected.

There are various ways for the UE to obtain the cooperation relationship between the application provider and the operator. For example, the UE may receive the collaboration relationship sent by the application provider, or receive the collaboration relationship sent by the UE from the UE. For the UE to receive the cooperation relationship sent by the operator, the following processing procedure may be adopted: the UE obtains the collaboration relationship from the application layer signaling or protocol sent by the application function AF entity of the operator; or the UE from the operator The collaboration layer is obtained in the bearer layer signaling. For the specific implementation of the foregoing process, refer to the descriptions of Embodiment 2 and Embodiment 3, and details are not described herein again. In this embodiment, a service quality update processing device is also provided, which is located in the UE, and is used to implement the foregoing embodiments and preferred embodiments. The module to be explained. As used hereinafter, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and conceivable. Figure 5 is a block diagram showing the structure of an update processing apparatus for quality of service according to Embodiment 1 of the present invention. As shown in FIG. 5, the apparatus includes: an obtaining module 50, connected to the requesting module 52, configured to acquire a collaboration relationship between an application provider and an operator; and a requesting module 52, requesting a QoS update according to the acquired collaboration relationship. Through the functions implemented by the foregoing processing module, the UE can also perceive the cooperation relationship between the operator and the application provider, and in particular, if the carrier and the application provider do not have service cooperation, the UE can be specifically coordinated with the two. The situation is perceived, so that the UE can correctly distinguish the two types of scenarios and make a correct selection according to the requirements. For example, for the first type of scenario in the related technology, the QoS promotion can only be triggered by the operator, and the second type of scenario in the related art. The corresponding trigger selection can be made according to the operator's strategy or the user's tendency. Preferably, the obtaining module 50 is configured to obtain one of the following collaboration relationships: the application provider and the operator have service collaboration; the application provider and the operator do not have business collaboration and business relationship; and the application provider and the operator only have a business relationship But there is no business collaboration. The requesting module 52 is configured to directly initiate a request to the operator when the application provider and the operator do not have a service collaboration and a business relationship, and trigger the operator to perform update processing on the QoS. In this embodiment, the requesting module 52 is further configured to initiate the update process of the QoS according to the collaboration relationship in the following manner when the application provider and the operator only have a commercial relationship but no service cooperation: directly initiate the service to the operator. The request is requested to perform an update process on the QoS by the operator; the request is initiated by the application provider to trigger the operator to update the QoS. In this embodiment, the obtaining module 50 is configured to receive the collaboration relationship sent by the application provider; or receive the collaboration relationship sent by the operator. For a better understanding of Embodiment 1, the following is a detailed description of Embodiment 2 and Embodiment 3. The following embodiments relate to a UE-aware cooperative relationship update QoS in an EPS, and the purpose is that the UE provides services for operators and third-party services. The main design idea of the following embodiments is that the UE perceives the collaboration relationship between the application provider and the operator, and triggers according to the operator policy or the user's selection. Priority stream processing (ie QoS promotion). The UE can sense the cooperation relationship between the application provider and the operator through a third-party data application provider (DAP), and can also perceive the cooperation relationship between the application provider and the operator through the mobile operator. In the latter case, the UE is aware of the mobile operator's perception by: the application layer signaling of the operator application function, and the cooperation relationship between the application provider and the operator; the carrier layer signaling of the operator is used to sense the provider and the operator. Collaboration. The operator policy or the user's selection includes: 1) the UE initiates a request to the mobile operator, and the operator performs priority flow processing; 2) the UE initiates a request to the third-party application provider, and the third-party application provider requests the operator to give priority Stream processing. Embodiment 2 This embodiment provides a UE based on the MOSP architecture of FIG. 3 to perceive a collaboration relationship between an application provider and an operator through a third-party application provider DAP, and triggers QoS promotion according to an operator policy or a user selection. Methods and systems to implement priority flow processing triggered by users according to their needs. The UE described in this embodiment uses the service of the third-party application provider that does not have a cooperative relationship with the operator, and the third-party application provider and the operator do not have any commercial relationship and no business cooperation. The operator is responsible for providing transmission resources for the third-party application of the UE, and the UE initiates a priority flow processing request to the operator, and the operator processes the update of the relevant QoS.

After the IP-CAN session is created, the third-party application provider determines the cooperation relationship with the UE's home operator based on the information such as the subscription information, the UE ID, and the PLMNID of the collaboration carrier, and informs the UE of the corresponding API. The UE receives and stores the collaboration relationship with the operator sent by the third-party application provider. When the user is dissatisfied with the QoS of the current service and initiates the priority flow processing request, the UE makes a correct selection according to the cooperation relationship between the current DAP and the mobile operator (Mobile Operators, referred to as MO) and the operator policy. For example, the operator default policy is to directly request the MO to initiate a priority flow processing request when the DAP and the MO have neither a commercial relationship nor a service cooperation. According to the deployment of the carrier network, the UE may initiate the QoS update by using the bearer resource modification process, or may initiate the QoS update by using the operator-owned AF trigger PCRF.

(1) In the process shown in Figure 6, the carrier's own AF function in the network deployment (can be added to the logic function, can be deployed independently, or integrated in other network elements. It can be the carrier's own application platform, also It can be an AF-enabled proxy network element that is combined with NAF or OP. It can also be integrated into existing network elements, such as PCRF. It supports UE and AF interfaces (http protocol or other application layer signaling can be used). If the AF is outside the PCRF, the interface between the AF and the PCRF is supported (here, the Rx interface, which can communicate using the Diameter protocol). As shown in FIG. 6, the process includes: Step S601: The UE attaches to the home network, establishes a radio bearer, and creates an IP-CAN session. Step S602: The UE logs in and successfully accesses the Non-IMS AS, where UE and B Non-IMS The AS uses the application level signaling or the HTTP protocol, and the non-IMS AS provides the application service to the UE. The Non-IMS AS provides the Service ID/application ID and the flow information related information to the UE. Step S603: Complete the required bearer for the service. The PCRF creates a PCC/QoS rule based on the information sent by the client, such as AS, SPR/UDC, PGW, etc., and sends it to PCEF/BBERF. The PCEF/BBERF installs and executes the relevant rules to complete the bearer binding. If there is no match. The bearer sends a bearer setup request and creates a bearer. The PCRF may also carry related event triggers, as well as usage monitoring thresholds, monitoring keywords, and other information. PCEF sets and executes related event reports and usage after receiving the information. Monitoring function; Step S604: The service bearer is created, and the network provides the downlink transmission of the service data for the UE according to the authorized QoS; Step S605: Non-IMS AS root Information cooperating subscription information carriers, like PLMN ID and UE ID, UE determines off its home operator or cooperative relationship with, and notifies the cooperative relationship to the UE. The UE receives and stores the cooperative relationship between the non-IMS AS and the operator. The interaction signaling may be application layer signaling or an application protocol such as http. The collaboration indication informs the UE of the application provider's collaboration relationship with the operator, such as collaboration, non-collaboration (including business relationship but no business collaboration, neither business relationship nor business collaboration). The present invention aims to inform the UE of its double-reverse cooperation relationship, and its notification form is not limited to The way described above. The collaboration relationship notification may be a separate signaling or message, or may be included in other signaling or messages of the UE and the AS, for example, step S601. The indication of the collaboration relationship may be notified at any time after the non-IMS AS is acquired, not limited to after step S604; Step S606: In the service process, the UE finds that the quality of service QoS or the user experience is not satisfactory (for example, due to mobility or network The situation causes the data stream transmission to be unstable or the bandwidth is too low, etc., and the UE initiates a priority stream processing request. The UE makes the correct choice according to the current cooperation relationship between the application provider and the operator and the operator policy. For example, the default policy of the operator is: When the two have no business relationship business cooperation, the UE requests the operator to initiate a priority flow processing request. According to the deployment of the carrier network, the UE may initiate the QoS update by using the bearer resource modification process, or may initiate the QoS update by using the operator-owned AF trigger PCRF. Here the UE is triggered by the operator's own AF.

The UE sends a request message to the AF (the deployment may be an application platform such as a NAF or a non-IMS AS or RP or integrated in an existing network element); the request message of the UE carries the UEIP/ID, and the priority flow processing indication/QoS And flow information, and if possible, also carry Service ID/Application ID; (here, the communication protocol between UE and AF is not limited, http or application layer signaling can be implemented); In the specific implementation, except the above explicit notification The UE may also have an implementation that does not send any indication to the UE when there is no commercial relationship or service cooperation between the two, and the UE defaults to no non-cooperative relationship. The present invention aims to correctly judge the cooperation relationship between the network or the application provider, and does not limit the specific implementation of the sensing mode. Step S607: After receiving the request message of the UE, the AF associates the UE Id/IP with the service/application that needs to improve the QoS, sends a CCR request message to the PCRF, and requests to initiate a session to modify the update QoS; where the AF is used as the diameter client of the PCRF. Can be deployed independently or integrated into other network element entities. The request message carries the UE ID/IP, the priority stream processing indication/QoS, and the flow information, and possibly the service ID/application ID. Step S608: After receiving the AF request message, the PCRF queries the SPR/UDC user/ Whether the service/application has signed the high priority flow processing, if the contract is allowed, the session modification process is initiated according to the request; the updated PCC rule is issued to the PCEF/BBERF, or the ADC rule is given to the TDF. The PCEF/BBERF/TDF updates the PCC/QoS/ADC rules, modifies or creates a new bearer, and performs the binding of the updated QoS and related bearers. And sending a response message to the PCRF to feedback the execution result of the rule;

The PCRF returns an enhanced QoS modification response message CCA to the AF, notifying whether the modification is accepted, and if it is rejected, carrying the relevant cause; Step S609: If the update QoS authorization is successful, the AF sends an update QoS confirmation request message to the UE, asking the user to confirm whether the updated QoS is satisfactory, and if yes, returning a positive confirmation message within the preview time period (confirming acceptance of the updated QoS) After that, the user needs to provide additional tariff for this priority stream processing); if it is not satisfied or does 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 The negative acknowledgment is returned to the network, which facilitates the technical implementation to distinguish the abnormal situation in which the user does not send the acknowledgment and the acknowledgment message is lost. The AF can also set the timer to reject or accept the process of the service. However, the specific processing is implemented according to the carrier network); In the process flow, the AF can set the QoS promotion timer Timerl in the sending request StepS607, after receiving the CCA confirmation message of the PCRF and the Timerl Time out (the time period of the validity period of the timest should ensure that the IP-CANsession modification initiated by the normal PCRF is updated. And the application service has been provided to the UE according to the new QoS, and the AF is to the U. E sends a confirmation request message. AF can open the user confirmation timer Timer2 after sending the request message. Step S610: After receiving the acknowledgement message of the AF, 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 sends a confirmation message to the UE. The AF. After receiving the acknowledgment response from the UE, the AF optionally returns a confirmation response message to the PCRF, and the operator continues to provide QoS after the update for the service (for example, continuing priority flow processing to provide high priority or high bandwidth resources) . The PCRF will initiate the IP-CAN session modification process (same as StepS608) and issue a new Charigng key (the corresponding priority flow special charging for the service under the QoS). If the UE is dissatisfied 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 message to the AF. (ie, if the user does not agree to perform the new service quality to provide the service but does not make a negative acknowledgment, the terminal device optionally constructs a negative acknowledgment message to be sent to the AF according to the operator's requirements), and executes _S tepS 610a- _C; step S610a: if AF If the acknowledgment receiving message of the user is not received within the specified time (for example, timer2 timeout), or the acknowledgment rejection message of the user is received, the AF will send an update QoS request (for example, downgrade QoS) to the PCRF; Step S610b: PCRF receives the AF After the downgrade QoS request message, combined with the subscription information and the local policy (for example, the user confirms that the preview timer timeout for receiving updateQoS needs to reply to the original QoS), initiates the IP-CAN/GWcontrol/TDF session modification process, and updates the relevant PCC/QoS/ADC rules. Recovering the original QoS of the service; Step S610c: After the QoS recovery process is completed or the QoS confirmation time is raised, the network The processing of the service data stream will be restored to the QoS before the UE requests the promotion. The QoS fallback mechanism is not within the scope of the present invention. For example, the timer mechanism between the network elements can be used to process the rollback time of the session modification, and the update can be stored locally. The previous QoS, or the Trigger node sends the previous QoS information when sending the downgrade QoS request message, or the request message carries the default QoS indication, etc.). 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 the BBERF/TDF and the charging network element OCS/OFCS and other charging systems; this part of the processing can be found in the related art, and will not be described here. Through the process shown in FIG. 6, when the operator and the application provider have neither commercial relationship nor service cooperation, the UE directly requests the operator to initiate a priority flow processing request through the operator's perception of the collaboration relationship, and the carrier owns the request. The AF triggers the PCRF to initiate the QoS update, improve or lower the quality of service/user experience, and change the processing flow of the service tariff rate corresponding to the resource transmitted by the operator for the service.

(2) For the scenario, the UE requests QoS update. According to the carrier network deployment, the UE may also complete the QoS update by reusing the bearer resource modification process. In the process shown in FIG. 6, the UE senses the collaboration relationship through the third-party application provider, the third-party application provider does not have a commercial relationship with the mobile operator, and the UE does not have service cooperation, and the UE uses a mobile network operator (Mobile network operator, referred to as MNO) initiates the QoS update process, and triggers the "PCEF-initiated session modification process" to update the QOS by carrying the resource modification process. As shown in FIG. 7, the process includes: Step S701: Steps S501-S504 in FIG. 5, the UE attaches to the network to establish a related bearer and session, requests the service from the Non-IMS AS, and creates a related service bearer. The network provides the UE with the downlink transmission of the service data according to the authorized QoS; Step S702: The non-IMS AS determines, according to the cooperation information of the cooperation operator, the UE ID and the PLMN ID, the collaboration with the UE home operator or the UE Relationship, and notify the UE of the collaboration relationship. The UE receives and stores the cooperative relationship between the non-IMS AS and the operator. The interaction signaling may be application layer signaling or an application protocol such as http. The collaboration indication informs the UE of the application provider's collaboration relationship with the operator, such as collaboration, non-collaboration (including business relationship but no business collaboration, neither business relationship nor business collaboration). The present invention aims to inform the UE of its double-reverse cooperation relationship, and its notification form is not limited to the above. The collaboration relationship notification may be a separate signaling or message, or may be included in other signaling or messages of the UE and the AS. The indication of the collaboration relationship may be notified at any time after the non-IMS AS is acquired, and is not limited to after the end of step S701; Step S703: In 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, etc.), and the UE initiates a priority stream processing request. The UE makes the correct choice according to the current cooperation relationship between the application provider and the operator and the operator policy. For example, the default policy of the operator is: When the two have no business relationship business cooperation, the UE requests the operator to initiate a priority flow processing request. According to the deployment of the carrier network, the UE may initiate the QoS update by using the bearer resource modification process, or may initiate the QoS update by using the operator-owned AF trigger PCRF. Here, the UE initiates the QoS update by carrying a resource modification procedure.

The UE sends a Request message to the MME, and the request message carries the type of the request (update QoS), UEIP/ID, bearer ID (LBI), flow information (such as flow description (TAD), packet filter ID (PTI), etc.), QoS. If the service/application is previously a GBR bearer, the request may carry a packet filter identifier (s); and if possible, the Service ID/Application ID; Step S704: The MME forwards a request message to the SGW, where the message includes Step S705: After receiving the message, the SGW forwards the request message to the PGW, and the message carries the specific parameters received; Step S706: The PCEF determines that the QoS needs to be updated according to the received request message parameter (for example, according to Carrying the priority flow processing or bearer indication, or the QoS update indication, or the QoS of the service request is higher than the first QoS, etc., initiating the IP-CAN session modification process, and sending the session modification request to the PCRF to trigger the session modification, as shown in step 309. . The message carries parameters such as UE IP/ID, requested QoS, flow information (such as TAD, and SDF ffleter lD). The PCRF queries the SPR/UDC subscription information (for example, whether the user/service/application subscribes to the high-priority flow processing; if the subscription permits, the QoS is upgraded according to the request), updates the PCC policy decision, and sends the updated PCC rule to the PCEF/BBERF, Or ADC rules to TDF/PCEF (if there is application flow detection). Here, if there is no subscription information locally in the PCRF, the PCRF needs to obtain relevant subscription information from a database such as SPR/UDC/HSS. PCEF/BBERF updates the PCC/QoS rules, and the modified or newly created bearers satisfy the upgraded QoS. And the feedback rule executes the response message to the PCRF to complete the session modification process.

The PGW implements the QoS policy, completes the bearer modification and binding, and sends the Update Bearer Request to the SGW. The SGW forwards the message to the MME. The MME constructs the bearer modification request message and sends it to the eNodeB, which carries the Bear ID and QoS. The eNodeB maps the EPS bearer QoS to the wireless. The bearer QoS sends the RRL CR message to the UE, and the UE updates the storage-related QoS; returns the relevant response message to the PGW, and completes the bearer modification process. The detailed procedure for specifically referring to the content of each network element's message and its parameters can be referred to the UE-initiated bearer resource modification description in 3GPP TS 23.S701. Step S707: If the update QoS is successful, the UE needs to send an update QoS acknowledgement request message to the UE, and ask the user to confirm whether the updated QoS is satisfactory. If the UE is satisfied, the UE returns a positive acknowledgement message (confirm that the updated QoS needs to be the priority flow) The processing provides additional tariffs); if it is not satisfied or does not agree to pay the additional priority stream processing fee, the UE returns a negative acknowledgment or no acknowledgment to the network (if the user does not confirm, the terminal device may construct a negative acknowledgment and return to the network) In the technical implementation, it is convenient for the user to distinguish the abnormal situation that the user does not send the acknowledgment and the acknowledgment message is lost, but the specific processing is implemented according to the carrier network); or the notification may be triggered by the UE itself, and the notification is sent by the network side. After the IP-CAN session modification process is completed, the service data flow is provided for the service according to the updated QoS; the PGW/PCEF sends a notification message to the UE, and the UE is required to confirm the updated QoS, and the notification message carries the acknowledgement. The indication indicates that the QoS update requested by the user is completed, and the request is confirmed; after receiving the notification message, the SGW sends the notification to the MME, carries the UEID/IP, necessary service flow information, and the confirmation indication; the MME sends the message Sending to the UE, after receiving the notification message, the UE will provide a notification indication to the upper layer (for example, the application layer) to trigger the user's perception; Step S708: After the user receives the confirmation message of the UE application layer, if the update is performed (for example, after the promotion) If the service data flow is satisfactory and is willing to pay the fee for the priority stream processing, the message is acknowledged within the preview time period, and the UE will send a positive confirmation message to the network (with a positive confirmation in the request or notification corresponding) Information), the operator will continue to provide updated QoS for the service according to the acknowledgment (for example, continue priority flow processing, providing high priority) High bandwidth resources). The PCRF will initiate the IP-CAN session modification process (same as Step 309), and issue a new Charigng key (the corresponding priority flow special charging is performed for the service under the QoS). If the UE is dissatisfied 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 an acknowledgement response message) or returns a negative acknowledgement message to the network. (ie, if the user does not agree to perform the new service quality to provide the service but does not make a negative confirmation, the terminal device optionally constructs a negative acknowledgement message to the network according to the operator's requirement, and if the User does not confirm, the application layer needs to wait for confirmation. After the timer timeout, the bearer layer construction negative acknowledgement message is sent to the network, and the network will restore the QoS to the level before the request promotion after a certain preview time; Step S709: The MME receives the UE's request or notifies the corresponding message, and sends the corresponding message to the SGW. Transmitting the message, carrying the parameters in the original message, such as UE IP/ID, QoS, positive or negative acknowledgment information/indication, etc.; Step S710: The SGW forwards the message to the PGW, carrying parameters such as QoS and acknowledgment information/indication; S711: The PGW determines the QoS required by the user service according to the confirmation information/instruction, and if it is positive confirmation, executes Step S712. If the acknowledgment is negative, the IP-CAN session modification request is sent to the PCRF to initiate the session modification process, downgrade QoS; after receiving the downgrade QoS request message, the PCRF combines the subscription information with 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), initiates the IP-CAN/GWcontrol/TDF session modification process, updates the relevant PCC/QoS/ADC rules, and restores the original QoS of the service; the IP-CAN session modification process modifies the bearer and session, and the QoS provided for the service will Returning to the level before the user promotion request, the StepS7115 is continued to perform the downlink service data flow according to the original QoS; (the QoS fallback mechanism is not within the scope of the present invention, and the session modification mechanism may be processed, for example, by using a timer mechanism between the network elements. The QoS of the update may be stored locally, or the QoS information carried by the UE when the downlink QoS request message is sent, or the default QoS indication is carried in the request message. Steps S712-S714: The new IP-CAN session modification process initiated by the PCRF is sent in step S708.

Charigng key (performs the corresponding priority flow special charging for the service under QoS), and improves or restores the QoS process. The PGW confirms that the resource modification procedure initiated by the UE for sending the acknowledgment notification does not need to be performed (ie, the QoS does not need to be changed), and then sends a bearer resource modification failure indication to indicate the SGW, and the high QoS will continue to be applied to the service, and the QoS modification does not need to be re-initiated. In the process, step S712-S714 is performed to feed back the bearer resource modification failure indication. Step S715: If it is in step S711, after the downgrade QoS is completed, the downlink data is transmitted according to the initial QoS; if the update QoS is successfully confirmed in step S714, the downlink data is transmitted according to the upgraded QoS. That is, the network continues to provide service data flows for the service according to the authorized QoS. After the foregoing process, the UE directly requests the operator to initiate a priority flow processing request when the operator and the application provider have no commercial relationship or service cooperation, and triggers the PCRF to initiate an IP-CAN session modification through the bearer resource modification process, and updates the Service QoS, which improves or reduces the quality of service/user experience, and changes the processing rate of the service tariff rate corresponding to the resources transmitted by the operator for the service.

(3) Based on the MOSP architecture of FIG. 3, the present embodiment provides a UE that perceives the cooperation relationship between the application provider and the operator through the third-party application provider DAP, and triggers the QoS promotion according to the operator policy or the user's selection. Methods and systems to implement priority flow processing triggered by users according to their needs. The UE described in this embodiment uses the service of the third-party application provider that does not have a cooperative relationship with the operator, and the third-party application provider and the operator have a commercial relationship but do not have any business cooperation. The operator is responsible for providing transmission resources for the third-party application of the UE, and the UE initiates a priority flow processing request to the third-party service provider, and the DAP further initiates an update processing request for the relevant QoS to the operator, and triggers the operator to modify the session update QOS. After the IP-CAN session is created, the third-party application provider determines the cooperation relationship with the UE's home operator based on the information such as the subscription information, the UE ID, and the PLMNID of the collaboration carrier, and informs the UE of the corresponding API. The UE receives and stores the collaboration relationship with the operator sent by the third-party application provider. When the user is dissatisfied with the QoS of the current service and initiates the priority flow processing request, the UE makes a correct selection according to the current cooperation relationship between the DAP and the MO and the operator policy. For example, the operator default policy is that when there is a commercial relationship between the DAP and the MO but no service cooperation, the UE initiates a priority flow processing request to the third-party service provider, and the DAP further initiates an update processing request of the relevant QoS to the operator, triggering the operation. Revise the session update QOS. In the process shown in FIG. 8, the UE senses the collaboration relationship through the third-party application provider, the third-party application provider has a commercial relationship with the mobile operator but no service cooperation, and the UE initiates the QoS update through the operator MNO ( QoS update), the non-IMS AS notifies the PCRF, triggers the "PCEF initiated session modification process", and updates the QOS. In this network deployment, operators and third-party service providers have Rx interfaces that can transmit related service information. However, the operator will not perform third-party service tariff statistics and calculations for the third-party service provider. As shown in FIG. 8, the process includes: Step S801: The UE attaches to the home network, establishes a radio bearer, and creates an IP-CAN session. Step S802: The UE logs in and successfully accesses the Non-IMS AS, where UE and B Non-IMS The AS uses the application level signaling or the HTTP protocol, and the non-IMS AS provides the application service for the UE. Step S803: The Non-IMS AS provides the UE ID/IP, Service ID/application ID, and flow information related information to the PCRF of the operator. R Session establishment request. The PCRF obtains the UE subscription information and 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 has no business cooperation with the operator only, the authorized QoS is the default bearer QoS; Step S804: the creation of the bearer required to complete the service; the PCRF formulates the PCC according to the information sent by the client, such as AS, SPR/UDC, PGW, etc. / QoS rules are delivered to 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 may also carry the rules. Related event trigger, and usage monitoring threshold, monitoring keywords and other information; PCEF sets and executes related event report and usage monitoring function after receiving the information; Step S805: The service bearer is created, and the network provides the service to the UE according to the authorized QoS. The downlink transmission of the data; Step S806: The non-IMS AS judges the cooperation relationship with the UE home operator or the UE according to the subscription information, the UE ID and the PLMN ID of the cooperation operator, and notifies the UE of the collaboration relationship. . The UE receives and stores the cooperative relationship between the non-IMS AS and the operator. The interaction signaling can be application layer signaling Or application protocols such as http. The collaboration indication informs the UE of the application provider's collaboration relationship with the operator, such as collaboration, non-collaboration (including business relationship but no business collaboration, neither business relationship nor business collaboration). The present invention aims to inform the UE of its double-reverse cooperation relationship, and its notification form is not limited to the above. The collaboration relationship notification may be a separate signaling or message, or may be included in other signaling or messages of the UE and the AS, for example, step S801. The indication of the collaboration relationship may be notified at any time after the non-IMS AS is acquired, not limited to after step S805; Step S807: During the service process, the UE finds that the quality of service QoS or the user experience is not satisfactory (for example, due to mobility or network The situation causes the data stream transmission to be unstable or the bandwidth is too low, etc., and the UE initiates a priority stream processing request. The UE makes the correct choice according to the current cooperation relationship between the application provider and the operator and the operator policy. For example, the default policy of the operator is: When the two have a commercial relationship but no service cooperation, the UE initiates a priority flow processing request to the third-party service provider, and the DAP further initiates an update processing request of the relevant QoS to the operator, triggering the operation. Revise the session update QOS.

The UE sends a request message to the non-IMS AS, where the request message of the UE carries the UEIP/ID, the priority stream processing indication/QoS, and the flow information, and if possible, the Service ID/Application ID; Step S808: non- After receiving the request message of the UE, the IMS AS associates the UE Id/IP with the service/application that needs to improve the QoS, sends a request message to the PCRF, and requests to initiate a session to modify the update QoS; where the non-IMS AS functions as the diameter client of the PCRF. The request message carries the UE ID/IP, the priority stream processing indication/QoS, and the flow information, and possibly the service ID/application ID. Step S809: After receiving the request message of the non-IMS AS, the PCRF queries the SPR/UDC. Whether the user/service/application has subscribed to the high-priority stream processing (if the local subscription information is not available, the SPR/UDC is queried), if the contract is allowed, the session modification process is initiated according to the request; and the updated PCC rule is issued to the PCEF/BBERF. , orADC rules are given to TDF. The PCEF/BBERF/TDF updates the PCC/QoS/ADC rules, modifies or creates a new bearer, and performs the binding of the updated QoS and related bearers. And sending a response message to the PCRF, and feeding back the rule execution result; Step S810: The PCRF returns an enhanced QoS modification response message to the non-IMS AS, indicating whether the modification is accepted, and if it is rejected, carrying the relevant cause; this step requires the AF to send the QoS update. When the request is made, the event report such as the resource allocation status is subscribed; Step S811: If the update QoS update is successful, the non-IMS sends an update QoS confirmation request message to the UE, asking the user to confirm whether the updated QoS is satisfactory, and if satisfactory, at the preview time. A positive confirmation message is returned within the segment (after confirming that the updated QoS is accepted, the user needs to provide additional tariff for this priority stream processing); if it is not satisfied or does not agree to pay the additional priority stream processing fee, return a negative confirmation or not Confirmation (if the user does not confirm, the terminal device may construct a negative confirmation to return to the network, which is convenient for technical implementation. The user does not send an exception indicating that the acknowledgment and acknowledgment message are lost. The non-IMS AS can also set the timer as the time window for rejecting or accepting the process. But the specific processing is handled according to the product implementation). This step may also be performed by the UE after the QoS update succeeds, that is, after the resource modification is successful, and the locally set preview timer expires, and the triggering API sends an acknowledgement message to the user for sensing; Step S812: The user receives the confirmation request message of the non-IMS AS or After the acknowledgment request message triggered by the bottom layer UE, if the service data flow after the update (for example, promotion) is satisfied and is willing to pay the fee for the priority stream processing, the message is acknowledged, and the UE sends an acknowledgment response message to the non-IMS. AS. Step S813: After receiving the acknowledgment response from the UE, the non-IMS AS optionally sends an acknowledge response message to the PCRF. In order to receive the updated high QoS acknowledgment, the operator will continue to provide QoS after the update for the service (eg, continue to perform priority flow processing to provide high priority or high bandwidth resources). The PCRF will initiate an IP-CAN session modification process and deliver a new Charigng key (the corresponding priority flow special charging is performed for the service under the QoS). Steps S813a-c: 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 non-IMS AS (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 non-IMS AS according to the operator's requirements), and performs Step S813a-c; Step S813a: If the non-IMS AS does not receive the acknowledgment receiving message of the user within a predetermined time (for example, timer2 timeout), or receives the acknowledgment rejection message of the user, an update QoS request is sent (for example, Downgrade QoS) to the PCRF; Step S813b: After receiving the downgrade QoS request message of the non-IMS AS, the PCRF combines the subscription information with the local policy (for example, the user confirms that the Update timer receiving the updateQoS timeout needs to reply to the original QoS), and initiates the IP-CAN. /GWcontrol/TDF session modification process, update related PCC/QoS/ADC rules, restore the original QoS of the service; Step S813c: Complete QoS recovery processing After the QoS acknowledgement timeout 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 present invention, and the session modification may be processed by, for example, a timer mechanism between the network elements. The rollback time can be used to store the QoS before the update, or the AS carries the previous QoS information when sending the downgrade QoS request message, or the request message carries the default QoS indication. 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 within the protection scope of the present invention, so the present invention is not described in detail herein; in the above process, when DAP When there is a business relationship with the MO but no service cooperation, the default UE requests the DAP to trigger the MO to initiate the priority flow processing request, but the live network deployment can also support the direct request by the UE to initiate the priority flow processing request, which can be provided by the UE. The processing mechanism option is for the user to select and initiate a stream processing request according to its selection, or default one of the processing mechanisms according to the operator policy, or the default of the two mechanisms. It is determined according to the deployment requirements of the existing network and the strategy of the operator. For the process of this embodiment, if the operator has its own AF function or network element (for example, an application platform or an AF function integrated in other network elements), an interaction message between the non-IMS AS and the PCRF may be sent to the operation. The self-owned AF is forwarded to the PCRF for processing, and the related message may also be forwarded to the non-IMS AS of the third party via the AF. After the foregoing process, when the carrier and the application provider have a commercial relationship but no service cooperation, the UE initiates a priority flow processing request to the third-party service provider, and the DAP further initiates a related QoS update processing request to the operator, triggering The operator modifies the session update QOS, improves or reduces the quality of service/user experience, and changes the processing flow of the service tariff rate corresponding to the resources transmitted by the operator for the service. Embodiment 3 This embodiment provides a method and system for a UE to trigger a QoS promotion according to an operator policy or a user selection based on a carrier-aware collaboration relationship between an application provider and an operator based on the MOSAP architecture of FIG. To achieve priority flow processing triggered by users according to their needs. The UE described in this embodiment uses the service of the third-party application provider that does not have a cooperative relationship with the operator (the third-party application provider and the operator do not have any business relationship and have no business cooperation, or have a business relationship but no business cooperation. ). The operator is responsible for providing transmission resources for the third-party application of the UE, and the UE initiates a priority flow processing request to the operator or the third-party application provider, and the operator processes the update of the relevant QoS. After the IP-CAN session is created, the operator determines the cooperation relationship with the third-party application provider according to the contracted list of the cooperation operator in the contract information, the ID of the third-party application provider, the service/application ID, and the like. Tell the UE the corresponding API. The UE receives and stores the collaboration relationship with the application provider sent by the operator. When the user is dissatisfied with the QoS of the current service and initiates the priority flow processing request, the UE makes a correct selection according to the current DAP and MO cooperation relationship and the operator policy. For example, the operator default policy is to request the MO to initiate a priority flow processing request directly when the DAP and the MO have no commercial relationship service cooperation. According to the carrier network In the deployment, the UE may initiate the QoS update by using the bearer resource modification process, or may initiate the QoS update by using the operator-owned AF trigger PCRF.

(1) In the process shown in FIG. 9, the UE perceives the cooperative relationship through the operator, and the UE initiates the QoS update through the MNO, and triggers the session modification to update the QOS through the interaction between the operator-owned AF and the PCRF. In the process shown in FIG. 9, the UE uses the service of the third-party application provider that does not have a cooperative relationship with the operator (the third-party application provider and the operator do not have any commercial relationship and no business cooperation). The operator is responsible for providing transmission resources for the third-party application of the UE, and the UE initiates a priority flow processing request to the operator, and the operator processes the update of the relevant QoS. The carrier's own AF function in the network deployment (can be added to the logic function, can be deployed independently, or integrated in other network elements. It can be the carrier's own application platform, or it can be combined with NAF or OP.) The function of the proxy network element can also be integrated into the existing network element, for example, in the PCRF. The interface supporting the UE and the AF (http protocol or other application layer signaling can be used). If the AF is outside the PCRF, the AF is supported. Interface with PCRF (here Rx interface, communication using Diameter protocol). The self-owned AF function can solve the problem that the UE and the PCRF do not have a direct interface, and can also solve the problem that the QoS and application information provided by the IMS is not completely trusted by the IMS, and can be regarded as a non-IMS AS and an operator. Network proxy. As shown in FIG. 9, the process includes: Step S901: The UE attaches to the home network, establishes a radio bearer, and creates an IP-CAN session. Step S902: The UE logs in and successfully accesses the Non-IMS AS, where UE and B Non-IMS The AS uses the application level signaling or the HTTP protocol, and the non-IMS AS provides the application service for the UE. The Non-IMS AS provides the Service ID/application ID and the flow information related information to the UE. Step S903: Complete the required bearer for the service. The PCRF creates a PCC/QoS rule based on the information sent by the client, such as AS, SPR/UDC, PGW, etc., and sends it to PCEF/BBERF. The PCEF/BBERF installs and executes the relevant rules to complete the bearer binding. If there is no match. The bearer sends a bearer setup request and creates a bearer. The PCRF may also carry related event triggers, as well as usage monitoring thresholds, monitoring keywords, and other information. PCEF sets and executes related event reports and usage after receiving the information. Monitoring function; Step S904: The service bearer is created, and the network provides the downlink transmission of the service data for the UE according to the authorized QoS; Step S905: The operator according to The contracting list of the cooperation operator in the contract information, the ID of the third-party application provider, the service/application ID, etc., determine the cooperation relationship with the third-party application provider, and inform them The corresponding API of the UE. The UE receives and stores the collaboration relationship with the application provider sent by the operator. The interaction signaling may be application layer signaling or an application protocol such as http. The cooperation indication informs the UE of the application provider's cooperation relationship with the operator, such as collaboration, non-collaboration (including having a business relationship but no business collaboration). There are neither business relationships nor business collaboration. The present invention aims to inform the UE of the cooperative relationship between the two parties, and the form of notification thereof is not limited to the manner described above. The collaboration relationship notification may be a separate signaling or message, or may be included in other signaling or messages of the UE and the operator, for example, in step S901 or S903. The indication of the collaboration relationship may be notified at any time after the operator obtains, not limited to after step S904; Step S906: During the service process, the UE finds that the quality of service QoS or the user experience is not satisfactory (for example, due to mobility or network conditions) The data stream transmission is unstable or the bandwidth is too low, etc., and the UE initiates a priority stream processing request. The UE makes the correct choice according to the current cooperation relationship between the application provider and the operator and the operator policy. For example, the default policy of the operator is: When the two have no business relationship business cooperation, the UE requests the operator to initiate a priority flow processing request. According to the deployment of the carrier network, the UE may initiate the QoS update by using the bearer resource modification process, or may initiate the QoS update by using the operator-owned AF trigger PCRF. Here the UE is triggered by the operator's own AF. The UE sends a request message to the AF (the deployment may be an application platform such as a NAF or a non-IMS AS or RP or integrated in an existing network element); the request message of the UE carries the UEIP/ID, and the priority flow processing indication/QoS And the flow information, and if possible, the Service ID/Application ID; (where the communication protocol of the UE and the AF is not limited, http or application layer signaling can be implemented); Step S907: The AF receives the request message of the UE. Then, the UE Id/IP and the service/application that needs to improve the QoS are sent, and a CCR request message is sent to the PCRF to request to initiate a session to modify the update QoS. Here, the AF is used as the diameter client of the PCRF, and can be independently or integrated into other network element entities. deploy. The request message carries the UE ID/IP, the priority stream processing indication/QoS, and the flow information, and possibly the service ID/application ID. Step S908: After receiving the AF request message, the PCRF queries the SPR/UDC user/ Whether the service/application has signed the high priority flow processing, if the contract is allowed, the session modification process is initiated according to the request; the updated PCC rule is issued to the PCEF/BBERF, or the ADC rule is given to the TDF. The PCEF/BBERF/TDF updates the PCC/QoS/ADC rules, modifies or creates a new bearer, and performs the binding of the updated QoS and related bearers. And sending a response message to the PCRF to feedback the rule execution result;

The PCRF returns an enhanced QoS modification response message CCA to the AF, notifying whether the modification is accepted, and if it is rejected, carrying the relevant cause; Step S909: If the update QoS authorization is successful, the AF sends an update QoS confirmation request message to the UE, asking the user to confirm whether the updated QoS is satisfactory, and if yes, returning a positive acknowledgement message within the preview time period (confirming acceptance of the updated QoS) After that, the user needs to provide additional tariff for this priority stream processing); if it is not satisfied or does 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 The negative acknowledgment is returned to the network, which facilitates the technical implementation to distinguish the abnormal situation in which the user does not send the acknowledgment and the acknowledgment message is lost. The AF can also set the timer to reject or accept the process of the service. However, the specific processing is implemented according to the carrier network); In the processing flow, the AF can set the QoS promotion timer Timerl in the sending request StepS907, after receiving the CCA confirmation message of the PCRF and the Timerl Time out (the time period of the validity period of the timest should ensure that the IP-CANsession modification update QoS processing initiated by the normal PCRF is completed. And the application service has been provided to the UE according to the new QoS, and the AF is to the U. E sends a confirmation request message. AF can open the user confirmation timer Timer2 after sending the request message. Step S910: After receiving the acknowledgement message of the AF, 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 sends a confirmation message to the acknowledgement message. The AF. After receiving the acknowledgment response from the UE, the AF optionally returns a confirmation response message to the PCRF, and the operator continues to provide QoS after the update for the service (for example, continuing priority flow processing to provide high priority or high bandwidth resources) . The PCRF will initiate the IP-CAN session modification process (same as StepS908) and issue a new Charigng key (the corresponding priority flow special charging for the service under the QoS). If the UE is dissatisfied 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 message to the AF. (ie, if the user does not agree to perform the new service quality to provide the service but does not make a negative acknowledgment, the terminal device optionally constructs a negative acknowledgment message to be sent to the AF according to the operator's requirements), and executes _S tepS 910a- _C; step S910a: if AF If the acknowledgment receiving message of the user is not received within the specified time (for example, timer2 timeout), or the acknowledgment rejection message of the user is received, the AF will send an update QoS request (for example, downgrade QoS) to the PCRF; Step S910b: PCRF receives the AF After the downgrade QoS request message, combined with the subscription information and the local policy (for example, the user confirms that the preview timer timeout for receiving updateQoS needs to reply to the original QoS), initiates the IP-CAN/GWcontrol/TDF session modification process, and updates the relevant PCC/QoS/ADC rules. Recovering the original QoS of the service; Step S910c: After the QoS recovery process is completed or the QoS confirmation time expires, the network The processing of the service data stream will be restored to the QoS before the UE requests the promotion. The QoS fallback mechanism is not within the scope of the present invention. For example, the timer mechanism between the network elements can be used to process the rollback time of the session modification, and the update can be stored locally. The previous QoS, or the Trigger node sends the previous QoS information when sending the downgrade QoS request message, or the request message carries the default QoS indication, etc.). 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 network element such as BBERF/TDF interacts with the charging network element OCS/OFCS and other charging systems. Through the foregoing process, when the operator and the application provider have neither commercial relationship nor service cooperation, the UE directly requests the operator to initiate a priority flow processing request through the operator's perceived cooperative relationship, and triggers the carrier's own AF. The PCRF initiates the QoS update, improves or reduces the quality of service/user experience, and changes the processing flow of the service tariff rate corresponding to the resource transmitted by the operator for the service. (2) For the scenario, the UE requests QoS update. According to the carrier network deployment, the UE may also complete the QoS update by reusing the bearer resource modification process. In the process shown in FIG. 10, the UE perceives the collaboration relationship by the operator, the operator and the third-party application provider do not have a commercial relationship and no service cooperation, and the UE initiates the QoS update through the carrier MNO, and the bearer resource modification process is performed. Trigger "PCEF initiated session modification process" to update QOS. As shown in FIG. 10, the process includes: Step S1001: In the foregoing steps S901-S905, the UE attaches to the network to establish a related bearer and session, requests the service from the Non-IMS AS, and creates a related service bearer, and the network is authorized. The QoS provides the UE with the downlink transmission of the service data. Step S1002: The operator determines the third-party application according to the cooperation operator's subscription list, the third-party application provider ID, the service/application ID, and the like in the subscription information. The provider's collaboration and inform the UE of the corresponding API. The UE receives and stores the collaboration relationship with the application provider sent by the operator. The interaction signaling may be application layer signaling or an application protocol such as http. The collaboration indication informs the UE of the application provider's collaboration relationship with the operator, such as collaboration, non-collaboration (including business relationship but no business collaboration, neither business relationship nor business collaboration). The present invention aims to inform the UE of the cooperative relationship between the two parties, and the form of notification thereof is not limited to the manner described above. The collaboration relationship notification may be a separate signaling or message, or may be included in other signaling or messages of the UE and the operator. The indication of the collaboration relationship may be notified at any time after the operator obtains, not limited to after the end of step S1001; Step S1003: During the service process, the UE finds that the quality of service QoS or the user experience is not satisfactory (for example, due to mobility or network conditions) The data stream transmission is unstable or the bandwidth is too low, etc., and the UE initiates a priority stream processing request. The UE makes the correct choice according to the current cooperation relationship between the application provider and the operator and the operator policy. E.g, The default policy of the operator is: When the two have no business relationship business cooperation, the UE requests the operator to initiate a priority flow processing request. According to the deployment of the carrier network, the UE may initiate the QoS update by using the bearer resource modification process, or may initiate the QoS update by using the operator-owned AF trigger PCRF. Here, the UE initiates the QoS update by carrying a resource modification procedure. The UE sends a Request message to the MME, where the request message carries the type of the request (update QoS), UEIP/ID, bearer ID (LBI), flow information (such as flow description (TAD), packet filter ID (PTI), etc.) QoS. If the service/application is previously a GBR bearer, the request may carry a packet filter identifier(s); and if possible, a Service ID/Application ID; Step S1004: The MME forwards a request message to the SGW, where the message includes Step S1005: After receiving the message, the SGW forwards the request message to the PGW, and the message carries the specific parameters received; Step S1006: The PCEF determines that the update is required according to the received request message parameter. QoS (for example, according to carrying priority flow processing or bearer indication, or QoS update indication, or QoS of the service request is higher than the first QoS, etc.), initiating IP-CAN session modification flow processing, sending a session modification request to the PCRF to trigger session modification , as shown in step S909 of FIG. The message carries parameters such as UE IP/ID, requested QoS, flow information (such as TAD, and SDF fileter lD).

The PCRF queries the SPR/UDC subscription information (for example, whether the user/service/application subscribes to the high-priority flow processing; if the subscription permits, the QoS is upgraded according to the request), updates the PCC policy decision, and sends the updated PCC rule to the PCEF/BBERF, Or ADC rules to TDF/PCEF (if there is application flow detection). Here, if there is no subscription information locally in the PCRF, the PCRF needs to obtain relevant subscription information from a database such as SPR/UDC/HSS. PCEF/BBERF updates the PCC/QoS rules, and the modified or newly created bearers satisfy the upgraded QoS. And the feedback rule executes the response message to the PCRF to complete the session modification process.

The PGW implements the QoS policy, completes the bearer modification and binding, and sends the Update Bearer Request to the SGW. The SGW forwards the message to the MME. The MME constructs the bearer modification request message and sends it to the eNodeB, which carries the Bear ID and QoS. The eNodeB maps the EPS bearer QoS to the wireless. The bearer QoS sends the RRL CR message to the UE, and the UE updates the storage-related QoS; returns the relevant response message to the PGW, and completes the bearer modification process. The detailed procedure for specifically referring to the content of each network element's message and its parameters can be referred to the UE-initiated bearer resource modification description in 3GPP TS 23.401. Step SI 007: If the update QoS is successful, the update QoS confirmation request message needs to be sent to the UE, and the user is required to confirm whether the updated QoS is satisfactory. If the UE is satisfied, the UE returns a positive acknowledgment message (acknowledging that the updated QoS needs to be prioritized) Stream processing provides additional tariffs); if dissatisfied or disagrees with the payment of additional priority stream processing fees, the UE returns a negative acknowledgement or no acknowledgement to the network (if the user does not confirm, the terminal device may construct a negative acknowledgement back to The network is convenient for the technical implementation to distinguish the abnormal situation that the user does not send the acknowledgment and the acknowledgment message is lost, but the specific processing is implemented according to the carrier network); or the notification may be triggered by the UE itself, and the notification is sent by the network side. After the IP-CAN session modification process is completed, the service data flow is provided for the service according to the updated QoS; the PGW/PCEF sends a notification message to the UE, and the UE is required to confirm the updated QoS, and the notification message carries the acknowledgement. The indication indicates that the QoS update requested by the user is completed, and the request is confirmed; after receiving the notification message, the SGW sends the notification to the MME, carries the UEID/IP, necessary service flow information, and the confirmation indication; the MME sends the message Sending to the UE, after receiving the notification message, the UE will provide a notification indication to the upper layer (for example, the application layer) to trigger the user's perception; Step S1008: After the user receives the confirmation message of the UE application layer, if the update is performed (for example, after the promotion) If the service data flow is satisfactory and is willing to pay the fee for the priority stream processing, the message is acknowledged within the preview time period, and the UE will send a positive confirmation message to the network (with a positive confirmation in the request or notification corresponding) Information), the operator will continue to provide updated QoS for the service according to the acknowledgment (for example, continue priority flow processing, providing high priority) High bandwidth resources). The PCRF will initiate an IP-CAN session modification process (same as step S909 in FIG. 9), and issue a new Charigng key (perform the corresponding priority flow special charging for the service under the QoS). If the UE is dissatisfied 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 an acknowledgement response message) or returns a negative acknowledgement message to the network. (ie, if the user does not agree to perform the new service quality to provide the service but does not make a negative confirmation, the terminal device optionally constructs a negative acknowledgement message to the network according to the operator's requirement, and if the User does not confirm, the application layer needs to wait for confirmation. After the timer timeout, the bearer layer construction negative acknowledgement message is sent to the network, and the network will restore the QoS to the level before the request promotion after a certain preview time; Step S1009: The MME receives the UE's request or notifies the corresponding message, and sends the corresponding message to the SGW. Transmitting the message, carrying the parameters in the original message, such as UE IP/ID, QoS, positive or negative acknowledgment information/indication, etc.; Step S1010: The SGW forwards the message to the PGW, carrying parameters such as QoS and acknowledgment information/indication; S1011: The PGW determines the QoS required by the user service according to the acknowledgement information/instruction, and if it is positively confirmed, Step S1012; If the acknowledgment is negative, the IP-CAN session modification request is sent to the PCRF to initiate the session modification process, downgrade QoS; after receiving the downgrade QoS request message, the PCRF combines the subscription information with 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), initiates the IP-CAN/GWcontrol/TDF session modification process, updates the relevant PCC/QoS/ADC rules, and restores the original QoS of the service; the IP-CAN session modification process modifies the bearer and session, and the QoS provided for the service will Returning to the level before the user promotion request, the StepS 1015 is provided to provide the downlink service data flow according to the original QoS; (the QoS fallback mechanism is not within the scope of the present invention, and the session modification between the network elements can be used, for example, to process the session modification back. The QoS of the update may be stored locally, or the QoS information carried by the UE when the downlink QoS request message is sent, or the default QoS indication is carried in the request message. Steps S1012-S1014: A new process is sent in the IP-CAN session modification process initiated by the PCRF in step S1008.

Charigng key (performs the corresponding priority flow special charging for the service under QoS), and improves or restores the QoS process. The PGW confirms that the resource modification procedure initiated by the UE for sending the acknowledgment notification does not need to be performed (ie, the QoS does not need to be changed), and then sends a bearer resource modification failure indication to indicate the SGW, and the high QoS will continue to be applied to the service, and the QoS modification does not need to be re-initiated. In the process, the step S1012-S1014 is performed to feedback the bearer resource modification failure indication. Step S1015: If it is in step S1011, after the downgrade QoS is completed, the downlink data is transmitted according to the initial QoS; if the update QoS is successfully confirmed StepS1014, the downlink data is transmitted according to the upgraded QoS. That is, the network continues to provide service data flows for the service according to the authorized QoS. After the foregoing process, the UE can directly request the operator to initiate a priority flow processing request, and trigger the PCRF to initiate the bearer resource modification process, when the carrier and the application provider have no commercial relationship or service cooperation. IP-CAN session modification, updating the QoS of the service, improving or lowering the quality of service/user experience, and changing the processing flow of the service tariff rate corresponding to the resource transmitted by the operator for the service.

(3) Based on the MOSP architecture of FIG. 3, the present embodiment provides a method and system for a UE to trigger a QoS promotion according to an operator's policy or a user's choice, based on the operator's perceived cooperation relationship between the application provider and the operator. To achieve priority flow processing triggered by users according to their needs. The UE described in this embodiment uses the service of the third-party application provider that does not have a cooperative relationship with the operator, and the third-party application provider and the operator have a commercial relationship but do not have any business cooperation. The operator is responsible for providing transmission resources for the third-party application of the UE, and the UE initiates a priority flow processing request to the third-party service provider, and the DAP further initiates an update processing request for the relevant QoS to the operator, and triggers the operator to modify the session update QOS. After the IP-CAN session is created, the operator determines the cooperation relationship with the third-party application provider according to the contracted list of the cooperation operator in the contract information, the ID of the third-party application provider, the service/application ID, and the like. Tell the UE the corresponding API. The UE receives and stores the collaboration relationship with the application provider sent by the operator. When the user is dissatisfied with the QoS of the current service and initiates the priority flow processing request, the UE makes a correct selection according to the current DAP and MO cooperation relationship and the operator policy. For example, the operator default policy is that when there is a commercial relationship between the DAP and the MO but no service cooperation, the UE initiates a priority flow processing request to the third-party service provider, and the DAP further initiates an update processing request for the relevant QoS to the operator, triggering the operation. Revise the session update QOS. In the process shown in FIG. 11, the UE perceives the cooperative relationship through the operator MO, the third-party application provider and the operator have a commercial relationship but no service cooperation, and the UE initiates a QoS update through the MNO, and the non-IMS AS notifies the PCRF to trigger " The session modification process initiated by PCEF", update QOS. In this network deployment, operators and third-party service providers have an Rx interface that can transmit related service information. However, the operator will not perform third-party service tariff statistics and calculations for the third-party service provider. As shown in FIG. 11, the process includes: Step S1101: The UE attaches to the home network, establishes a radio bearer, and creates an IP-CAN session. Step S1102: The UE logs in and successfully accesses the Non-IMS AS, where the UE and the Non-IMS AS The non-IMS AS provides the application service for the UE by using the application level signaling or the HTTP protocol. Step S1103: The Non-IMS AS provides the UE ID/IP, Service ID/application ID, and flow information related information to the PCRF of the operator, and initiates R. Session establishment request. The PCRF obtains the UE subscription information and 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 has no business cooperation with the operator only, the authorized QoS is the default bearer QoS; Step S1104: The creation of the bearer required to complete the service; The PCRF formulates the PCC according to the information sent by the client such as AS, SPR/UDC, PGW, etc. The QoS rule is delivered to the PCEF/BBERF. The PCEF/BBERF installs and executes the relevant rules to complete the bearer binding. If no bearer is matched, the bearer setup request is sent to create a bearer. The PCRF may also carry the rule. Relevant event trigger, and usage monitoring threshold, monitoring keywords and other information; _PCEF sets and executes related event report and usage monitoring function after receiving the information; Step S1105: The service bearer is created, and the network provides the service to the UE according to the authorized QoS. The downlink transmission of the data; Step S1106: The operator determines the cooperation relationship with the third-party application provider according to the contracted list of the cooperation operator in the subscription information, the ID of the third-party application provider, the service/application ID, and the like. And inform the UE of the corresponding API. The UE receives and stores the collaboration relationship with the application provider sent by the operator. The cooperation indication informs the UE of the cooperation relationship between the service provider and the operator, such as collaboration, non-collaboration (package) Including the business relationship but no business collaboration, neither business relationship nor business collaboration. The present invention aims to inform the UE of the cooperative relationship between the two parties, and the notification form is not limited to a specific signaling manner. The collaboration relationship notification may be a separate signaling or message, or may be included in other signaling or messages of the UE and the operator, such as the messages of steps S1101 and S1104. The indication of the collaboration relationship may be notified at any time after the operator obtains, not limited to after step S1105; Step S1107: During the service process, the UE finds that the quality of service QoS or the user experience is not satisfactory (for example, due to mobility or network conditions) The data stream transmission is unstable or the bandwidth is too low, etc., and the UE initiates a priority stream processing request. The UE makes the correct choice according to the current cooperation relationship between the application provider and the operator and the operator policy. For example, the default policy of the operator is: When the two have a commercial relationship but no service cooperation, the UE initiates a priority flow processing request to the third-party service provider, and the DAP further initiates an update processing request of the relevant QoS to the operator, triggering the operation. Revise the session update QOS.

The UE sends a request message to the non-IMS AS, where the request message of the UE carries the UEIP/ID, the priority stream processing indication/QoS, and the flow information, and if possible, the Service ID/Application ID; Step S1108: non- After receiving the request message of the UE, the IMS AS associates the UE Id/IP with the service/application that needs to improve the QoS, sends a request message to the PCRF, and requests to initiate a session to modify the update QoS; where the non-IMS AS functions as the diameter client of the PCRF. The request message carries the UE ID/IP, the priority flow processing indication/QoS, and the flow information, and possibly the service ID/application ID. Step S1109: After receiving the request message of the non-IMS AS, the PCRF queries the SPR/UDC. Whether the user/service/application has subscribed to the high-priority stream processing (if the local subscription information is not available, the SPR/UDC is queried), if the contract is allowed, the session modification process is initiated according to the request; and the updated PCC rule is issued to the PCEF/BBERF. , orADC rules are given to TDF. The PCEF/BBERF/TDF updates the PCC/QoS/ADC rules, modifies or creates a new bearer, and performs the binding of the updated QoS and related bearers. And sending a response message to the PCRF, and feeding back the rule execution result; Step S1110: The PCRF returns an enhanced QoS modification response message to the non-IMS AS, indicating whether the modification is accepted, and if it is rejected, carrying the relevant cause; this step requires the AF to send the QoS update. When the request is made, the event report such as the resource allocation status is subscribed; Step S1111: If the update QoS update is successful, the non-IMS sends an update QoS confirmation request message to the UE, asking the user to confirm whether the updated QoS is satisfactory, and if satisfied, previewing A positive confirmation message is returned within the time period (after confirming that the updated QoS is accepted, the user needs to provide additional tariff for this priority flow processing); if it is not satisfied or does not agree to pay the additional priority flow processing fee, return a negative confirmation or not Confirmation (if the user does not confirm, the terminal device may construct a negative acknowledgment and return to the network, which facilitates the technical implementation to distinguish the abnormal situation in which the user does not send the acknowledgment and the acknowledgment message is lost. The non-IMS AS may also set the timer as the refusal. Never accept the time window of the process. But the specific processing is handled according to the product implementation). The step of the QoS update is successful, that is, after the resource is successfully modified, and the locally set preview timer expires, the triggering API sends an acknowledgement message to the user for sensing; Step S1112: The user receives the confirmation request message of the non-IMS AS or After the acknowledgment request message triggered by the bottom layer UE, if the service data flow after the update (for example, promotion) is satisfied and is willing to pay the fee for the priority stream processing, the message is acknowledged, and the UE sends an acknowledgment response message to the non-IMS. AS. Step S1113: After receiving the acknowledgment response from the UE, the non-IMS AS optionally sends an acknowledge response message to the PCRF. In order to receive the updated high QoS acknowledgment, the operator will continue to provide QoS after the update for the service (eg, continue to perform priority flow processing to provide high priority or high bandwidth resources). The PCRF will initiate an IP-CAN session modification process and deliver a new Charigng key (the corresponding priority flow special charging is performed for the service under the QoS). Step S1113a-c: If the UE is dissatisfied with the quality of service or user experience of the upgraded service data flow and is unwilling to pay an additional priority processing fee, the user does not confirm the confirmation request (does not return a response message) or returns a negative Acknowledgement message to the non-IMS AS (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 non-IMS AS according to the operator's requirements), and performs Steps 1113a-c; Step S1113a: If the non-IMS AS does not receive the acknowledgment receiving message of the user within a specified time (for example, timer2 timeout), or receives the acknowledgment rejection message of the user, an update QoS request is sent (for example, Downgrade QoS) to the PCRF; Step S1113b: After receiving the downgrade QoS request message of the non-IMS AS, the PCRF combines the subscription information with 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 the IP- CAN/GWcontrol/TDF session modification process, update related PCC/QoS/ADC rules, restore the original QoS of the service; Step S1113c: Restore in QoS After the completion of the QoS or the QoS acknowledgement timeout, the processing of the service data stream will be restored to the QoS before the UE requests the promotion. The QoS backoff mechanism is not within the scope of the present invention. For example, the timer mechanism between the network elements can be used. The QoS of the session modification may be stored locally, or the QoS before the update may be stored locally, or the QoS information carried by the AS when the downlink QoS request message is sent, or the default QoS indication is carried in the request message. 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 network element such as BBERF/TDF interacts with the charging network element OCS/OFCS and other charging systems. In the above process, when there is a commercial relationship between the DAP and the MO but no service cooperation, the default UE requests the DAP to trigger the MO to initiate the priority flow processing request, but the current network deployment can also directly request the MO to initiate the priority flow processing by the UE. The request may be provided by the UE with two processing mechanism options for the user to select and initiate a stream processing request according to the selection, or default one of the processing mechanisms according to the operator policy, or the priority of the default two mechanisms. It is determined according to the deployment requirements of the existing network and the strategy of the operator. For the process of this embodiment, if the operator has its own AF function or network element (for example, an application platform or an AF function integrated in other network elements), an interaction message between the non-IMS AS and the PCRF may be sent to the operation. The self-owned AF is forwarded to the PCRF for processing, and the related message may also be forwarded to the non-IMS AS of the third party via the AF. After the foregoing process, when the carrier and the application provider have a commercial relationship but no service cooperation, the UE senses the cooperation relationship by the operator, and initiates a priority flow processing request to the third-party service provider, and the DAP further initiates the service to the operator. The update processing request of the related QoS triggers the operator to modify the session update QOS, improve or lower the service quality/user experience, and change the processing flow of the service tariff rate corresponding to the resource transmitted by the operator for the service. The foregoing Embodiment 2 and Embodiment 3 can be used in combination, and are mainly supported according to specific network deployment and network element functions. The above embodiment is described in the context of the IE perception and differentiation in the scenario of the non-cooperative relationship between the operator and the third-party application provider. The above embodiment is also applicable to the collaborative operation between the carrier's own service and the operator and the third party. The perception and differentiation, as well as the carrier's own business, collaboration with third parties, non-communication with third parties, no commercial relationship, and non-collaborative but commercial relationships with third parties are deployed on the live network and Perception and differentiation in the application. In another embodiment, software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments. In another embodiment, a storage medium is provided, the software being stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, thereby Storing them in a storage device is performed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that herein, or they may be separately fabricated into individual integrated circuit modules, or Multiple of these modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

1. A method for updating the quality of service, including:

The user equipment UE acquires a cooperative relationship between the application provider and the operator;

The UE requests a quality of service QoS update according to the acquired cooperation relationship.

2. The method according to claim 1, wherein the collaboration relationship comprises one of the following:

The application provider and the operator have a service collaboration; the application provider and the operator do not have a business collaboration and a business relationship; the application provider and the operator only have a business relationship but no business collaboration .

The method of claim 2, wherein the requesting, by the UE, the QoS update according to the acquired collaboration relationship comprises:

When there is no service cooperation and business relationship between the application provider and the operator, the UE directly initiates a request to the operator, requesting the operator to perform update processing on the QoS.

When the application provider and the operator only have a commercial relationship but no service cooperation, the UE initiates an update process of the QoS according to the cooperation relationship in one of the following manners: the UE directly to the operator Initiating a request, triggering the operator to perform update processing on the QoS; the UE initiating a request by the application provider to trigger the operator to perform update processing on the QoS.

The method according to any one of claims 1 to 4, wherein the UE acquires a cooperation relationship between an application provider and an operator, including: the UE receiving the collaboration sent by the application provider Relationship; or the UE receives the collaboration relationship sent by the operator.

The method according to claim 5, wherein the UE receives the cooperation relationship sent by the operator, including: an application layer sent by the UE from an application function AF entity of the operator Obtaining the collaborative relationship in an order or agreement; or

The UE acquires the collaboration relationship from the bearer layer signaling of the operator.

A service quality update processing device, located in the user equipment UE, the device includes: an obtaining module, configured to acquire a cooperation relationship between the application provider and the operator;

The requesting module is configured to request a quality of service QoS update according to the obtained cooperation relationship.

The device according to claim 7, wherein the acquiring module is configured to acquire one of the following cooperation relationships: the application provider and the operator presence service cooperation; the application provider and the operator There is no business collaboration and business relationship; the application provider and the operator have only business relationships but no business collaboration.

9. The apparatus according to claim 8, wherein the requesting module is configured to directly initiate a request to the operator when the application provider and the operator do not have a business collaboration and a business relationship, requesting The operator performs an update process on the QoS.

The device according to claim 8, wherein the requesting module is configured to adopt the following manner according to the collaboration relationship when the application provider and the operator only have a commercial relationship but no business cooperation An initiation process for updating the QoS: directly initiating a request to the operator, triggering the operator to perform update processing on the QoS; and initiating a request via the application provider to trigger the operator to perform update processing on the QoS.

The device according to any one of claims 7 to 10, wherein the acquiring module is configured to receive the collaboration relationship sent by the application provider; or receive a message sent by the operator The collaborative relationship.