WO2013064004A1

WO2013064004A1 - Method and system for updating quality of service

Info

Publication number: WO2013064004A1
Application number: PCT/CN2012/082588
Authority: WO
Inventors: 吴锦花; 周晓云; 宗在峰; 卢飞
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-10-10
Filing date: 2012-10-08
Publication date: 2013-05-10
Also published as: CN103037449A; CN103037449B

Abstract

A method and system for updating quality of service (QoS), the method comprising: in a procedure of service, a user equipment (UE) sends to a packet gateway (PGW) a QoS update request or a QoS confirmation instruction; the PGW initiates an IP connection access network (IP-CAN) session modification process to update QoS after receiving the QoS update request or the QoS confirmation instruction. The method allows users to experience the improved QoS before determining whether to accept it or not, thus enabling providing service QoS in accordance with the requirement of users.

Description

Method and system for updating service quality

Technical field

The present invention relates to a policy and a charging control technology in a wireless communication system, and in particular, to a method and system for updating a QoS (Quality of Service) in an Evolved Packet System (EPS). Background technique

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

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

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

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

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

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

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

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

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

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

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

In the related art, after the UE establishes an IP-CAN session to a certain PDN, the network provides network resources required for data transmission according to the corresponding authorized QoS, and the QoS can be changed according to requirements in the service process. For IMS (IP Multimedia Subsystem) 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 (User Data Convergence), the underlying network bearer resource information, etc., and re-authorizes and issues new PCC/QoS rules to the PCEF/BBERF. The PCEF/BBERF updates the corresponding rules and modifies them. Bear resources to provide new QoS for this service. For non-IMS services, operators can deploy networks according to their own needs, and customize non-IMS service platforms and data centers. The QoS is changed by triggering its PCRF to initiate an IP-CAN session modification process through a custom interface. If the service is not provided by the operator's own service platform, the operator can sign a private agreement with the service provider to trigger the PCRF to initiate an IP-CAN session modification process to change the QoS through a custom interface.

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

Figure 4 is a schematic diagram of a PCC structure of a roaming home route in the presence of a third-party application provider,

The HPLMN is the Home PLMN (Public Land Mobile Network), and the VPLMN is the visited PLMN.

As shown in FIG. 5, it is an I-in general bootstrapping architecture (GBA) scheme for interworking of mobile operators and third-party application providers; except for the EPS network and PCC in FIGS. 1 and 2. The architecture introduces GBA as a mobile operator to authenticate and authenticate third-party application providers to provide related application services for the UE. In the figure, the Bootstrapping Server Function (BSF) is the functional entity in the network of the operator. All GBA user security settings (GUSS) are stored in the HSS, and the interface between the BSF and the HSS (Zh) Obtain user security information and authentication information. A session key (Ks) is generated between the UE and the BSF through the authentication mechanism between the BSF and the UE. The Net Application Function (NAF Function) is responsible for service control, and the session key can be obtained from the BSF. In this way, the NAF and the UE can have a shared key, which can provide security for subsequent applications, especially when the application session starts to authenticate the UE and the NAF. Therefore, the operator can complete related authentication and authentication, and provide third-party application services for the contracted users. But third party There is no perfect solution for policy negotiation and resource management between application providers and operators.

As shown in FIG. 6, it is another solution for introducing interworking of mobile operators and third-party application providers to introduce GBA and OpenID architectures; Open ID is a solution for implementing unified authentication of the entire network: When the terminal user UE logs in one A website that supports Open ID, that is, a Relying Party (RP), is different from the way the user logs in at the website (the end user may not have registered with the website), and the user has chosen Open ID. Log in to the site. The Open ID is a Uniform Resource Locator (URL) that the user is on another website, the OpenID Provider (OP). The RP will discover the OP according to the Open ID provided by the user, and then request the OP to authenticate the identity of the user. After receiving the RP request, the OP will ask the user to log in to the OP authentication page for authentication. After the authentication, the OP will remind the user whether to allow 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 uses the GBA boot mode, and the OP is equivalent to the NAF in the GBA architecture.

Operators can establish cooperative relationships with some application service providers to provide good service quality and application experience for users' application services. However, the number and types of network third-party application providers are increasing, and operators are not. It is possible to have a business collaboration with all application providers. Therefore, when the user uses the service of the third-party application provider that does not have a cooperative relationship with the operator, how to ensure the quality of the service service according to the user's request and confirm the use is a problem that needs to be researched and solved. Summary of the invention

The embodiments of the present invention provide a method and system for updating the quality of service, which can ensure that the service quality of the service can be provided according to user requirements when the user uses the service of the third-party application provider that does not have a cooperative relationship with the operator.

To solve the above technical problem, the present invention provides a method for updating a quality of service, including: in a service process, a terminal (UE) sends an update quality of service (QoS) request or a QoS confirmation indication to a packet data network gateway (PGW) ; as well as

After receiving the update QoS request or QoS confirmation indication, the PGW initiates an IP connection. Incoming network (IP-CAN) session modification process, updating QoS.

After the PGW receives the update QoS request or the QoS confirmation indication, the step of initiating the IP-CAN session modification process includes:

When the network has a policy and charging control (PCC) deployment, the PGW receives the update QoS request or the QoS confirmation indication, and then requests a policy and charging rule function (PCRF) to perform a session modification decision, and triggers the PCRF to initiate an IP. -CAN session modification process.

The method further includes: after updating the QoS, the UE sends a QoS information and/or a QoS acknowledgement message to the PGW, where the QoS information and/or the QoS acknowledgement message is used to indicate acceptance of the current QoS or not to accept the current QoS;

The PGW decides to maintain the current QoS or modify the QoS to the pre-update QoS according to the QoS information and/or the QoS acknowledgment message.

The method further includes:

After updating the QoS, the UE sends a QoS information and/or a QoS acknowledgement message to the PCRF, where the QoS information and/or the QoS acknowledgement message is used to indicate acceptance of the current QoS or not to accept the current QoS;

The PCRF decides to maintain current QoS or modify QoS to pre-update QoS based on the QoS information and/or QoS acknowledgment message decision.

The step of the UE sending an update QoS request or a QoS confirmation indication to the PGW includes: sending, by the UE, an update QoS request or a QoS acknowledgement indication to the PGW by using a bearer resource modification procedure or a new message flow.

The step of the UE sending the update QoS request or the QoS confirmation indication to the PGW includes: sending, by the UE, the update QoS request or the QoS confirmation indication to the PGW by using a bearer resource modification procedure or a new message flow;

The step of the PGW requesting the PCRF to perform the session modification decision includes: the PGW requests the PCRF to perform a session modification decision by using an IP-CAN session modification request message, where the IP-CAN session modification request message carries the updated QoS information.

The step of the UE sending the update QoS request or the QoS confirmation indication to the PGW by using the bearer resource modification process or the newly added message flow includes: The UE sends a bearer resource modification request message to the mobility management unit (MME), carrying the update QoS request information or the QoS acknowledgement indication, and the MME sends the bearer resource command to the serving gateway (S-GW) after receiving the bearer resource modification request message. Carrying the updated QoS request information or the QoS acknowledgment indication, and the S-GW forwards the bearer resource command to the PGW; or

The UE sends a request message carrying the updated QoS request information or the QoS confirmation indication to the MME, and the MME forwards the request message to the S-GW, and the S-GW forwards the request message to the PGW.

The update QoS request information or QoS acknowledgment indication is carried by a Protocol Configuration Option (PCO) field or by other fields than the PCO.

The step of the UE sending the QoS information and/or the QoS acknowledgement message to the PGW includes: sending, by the UE, the QoS information and/or the QoS acknowledgement message to the PGW by using a bearer resource modification procedure or a new message flow.

The step of the UE sending the QoS information and/or the QoS acknowledgment message to the PCRF includes: sending, by the UE, the QoS information and/or the QoS acknowledgement message to the PGW by using a bearer resource modification procedure or a new message flow, and the PGW passes the credit control request message. The QoS information and/or QoS acknowledgment message is sent to the PCRF.

The step of the UE sending the QoS information and/or the QoS acknowledgement message to the PGW by using the bearer resource modification process or the newly added message flow includes:

The UE sends a bearer resource modification request message to the MME, and carries the QoS information and/or the QoS acknowledgement message. After receiving the bearer resource modification request message, the MME sends a bearer resource command to the S-GW, and carries the QoS information and/or a QoS acknowledgement message, the S-GW forwarding the bearer resource command to the PGW; or

The UE sends a request message carrying the QoS information and/or the QoS acknowledgement message to the MME, and the MME forwards the request message to the S-GW, and the S-GW forwards the request message to the PGW.

The method also includes:

After the PGW decides to maintain the current QoS according to the QoS information and/or the QoS acknowledgment message, the PGW sends a bearer resource failure indication carrying an acknowledgment response to the S-GW, and the S-GW forwards the bearer resource failure indication to the MME. Sending, by the MME, a bearer resource modification reject message to the UE To confirm the mouth should be.

The private extension field in the bearer resource failure indication is used to carry the acknowledgement response.

The method further includes: after the PCRF decides to maintain the current QoS according to the QoS information and/or the QoS acknowledgment message, sending an IP-CAN session modification indication message carrying an acknowledgment response to the PGW, where the PGW sends the SGW to the S-GW. The bearer resource failure indication carrying the acknowledgment response, the S-GW forwards the bearer resource failure indication to the MME, and the MME sends a bearer resource modification reject message to the UE as a confirmation response.

The step of the PGW modifying the QoS to the pre-updated QoS according to the QoS information and/or the QoS acknowledgment message decision includes:

The PGW initiates an IP-CAN session modification procedure to modify the QoS to the pre-update QoS. The step of the PCRF modifying the QoS to the pre-updated QoS according to the QoS information and/or the QoS acknowledgment message decision includes:

The PCRF initiates an IP-CAN session modification procedure to modify the QoS to the pre-update QoS. The method further includes:

After updating the QoS, the UE actively sends a request message carrying the updated QoS indication to the PGW or sends a notification response carrying the acknowledgement information; or

After updating the QoS, the UE sends a request message carrying the update QoS indication or sends the acknowledgement information to the PGW after receiving the notification message carrying the acknowledgement indication sent by the PGW to the UE through the S-GW and the MME. Notification response.

An embodiment of the present invention further provides a system for updating quality of service, including a first sending module located at a terminal (UE), and a first QoS update module located at a packet data network gateway (PGW), where:

The first sending module is configured to send an update quality of service (QoS) request or a QoS confirmation indication to the PGW in a service process;

The first QoS update module is configured to: after receiving the update QoS request or the QoS confirmation indication, initiate an IP connection access network (IP-CAN) session modification procedure, and update the QoS.

The first QoS update module is configured to initiate an IP-CAN session modification flow in the following manner Cheng:

When the network has policy and charging control (PCC) deployment, after receiving the update QoS request or QoS confirmation indication, requesting a policy and charging rule function (PCRF) to perform a session modification decision, triggering the PCRF to initiate an IP-CAN session modification process. .

The first sending module is further configured to send QoS information and/or a QoS acknowledgement message to the PGW by using a bearer resource modification procedure or a new message flow after the QoS is updated, where the QoS information and/or the QoS acknowledgement message is used to indicate acceptance. Current QoS or not accepting current QoS;

The first QoS update module is further configured to maintain current QoS or modify QoS to pre-update QoS based on the QoS information and/or QoS acknowledgment message decision.

The system also includes a second transmitting module at the PGW and a second located at the PCRF

QoS update module,

The first sending module is further configured to: after updating the QoS, send the QoS information and/or the QoS acknowledgement message to the PGW by using a bearer resource modification process or a new message flow, where the QoS information and/or the QoS acknowledgement message is used. Indicates acceptance of current QoS or does not accept current QoS;

The second sending module is configured to send the QoS information and/or the QoS confirmation message to the PCRF by using a credit control request message;

The second QoS update module is configured to: maintain current QoS or modify QoS to pre-update QoS according to the QoS information and/or QoS acknowledgment message.

The first sending module is configured to send an update QoS request or a QoS confirmation indication to the PGW in the following manner:

The update QoS request or QoS confirmation indication is sent to the PGW through the bearer resource modification process or the new message flow.

The first QoS update module is configured to request the PCRF to perform a session modification decision in the following manner:

Modifying the request message request by the IP-CAN session, the PCRF performs a session modification decision,

The IP-CAN session modification request message carries the updated QoS information.

The first QoS update module is further configured to: after the decision to maintain the current QoS, send a bearer resource failure indication carrying the acknowledgment response to the serving gateway (S-GW), and pass the S-GW and the mobility management list. The element (MME) sends an acknowledgment response to the UE.

The second QoS update module is further configured to: after the decision to maintain the current QoS, send an IP-CAN session modification indication message carrying an acknowledgment response to the PGW, and send the message to the UE by using the PGW, the S-GW, and the MME. Confirm the response.

The first sending module is further configured to: after updating the QoS, actively send a request message carrying the updated QoS indication to the PGW or send a notification response carrying the acknowledgement information; or, after updating the QoS, receiving the PGW After the S-GW and the MME send the notification message carrying the acknowledgment instruction to the UE, the SGW sends a request message carrying the update QoS indication or a notification response carrying the acknowledgment information to the PGW.

By using the method of the embodiment of the present invention, the user can first experience the improved QoS and then decide whether to accept the QoS, thereby providing the service quality according to the requirements of the user. BRIEF abstract

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

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

3 is a schematic diagram of a PCC structure in which a third-party application provider exists;

4 is a schematic structural diagram of a PCC structure of a roaming home route of a third-party application provider; FIG. 5 is a schematic diagram of a non-roaming network structure introduced into the GBA;

Figure 6 is a schematic diagram showing the structure of a non-roaming network introducing OpenID and GBA;

Figure 7 is a flow chart of an embodiment of the present invention;

Figure 8 is a schematic diagram of a system for implementing the method of Figure 7;

FIG. 9 is a flowchart of non-roaming according to Embodiment 1 of the present invention; FIG.

FIG. 10 is a flowchart of roaming according to Embodiment 1 of the present invention; FIG.

11 is a flowchart of Embodiment 2 of the present invention;

12 is a flowchart of Embodiment 3 of the present invention; FIG. 13 is a flowchart of Embodiment 4 of the present invention.

Preferred embodiment of the invention

When a user uses a service of a third-party application provider that does not have a cooperative relationship with the carrier, the operator needs to be able to independently provide the contracted users of the network with the service quality required for the application service, and can upgrade and reduce the service according to the user requirements. Quality, and can decide whether to charge extra for this high quality of service according to the user's wishes. For example, a subscriber A of an operator MNO Y is using a service provided by a third-party application provider X (for example, an online movie). Since MNO Y and X have no cooperation, the service uses the non-guaranteed bandwidth provided by the default bearer. Quality of service; In the process of using the service, the user A feels that the user experience is poor and initiates a request to the operator Y to improve the service quality of the service. Then the operator Y needs to modify the current IP-CAN session of the UE. Corresponding QOS; At the same time, due to the high service quality, there is an additional charge. It is necessary to inform the user whether it is satisfied with the upgraded service quality and is willing to pay for it. After the user confirms the permission, the operator can charge an additional fee for the improvement of the service quality. . In the related network technology, there is no application interface and communication protocol between the UE and the service quality decision network element PCRF of the operator, and the existing UE and the network process do not support the processing scheme for improving and confirming the quality of the service. Therefore, the prior art cannot achieve the above requirements.

The following solutions are provided to solve the above problem. As shown in FIG. 7, the method includes the following steps: Step 1: In a service process, a terminal (UE) sends an update quality of service (QoS) request or a QoS confirmation indication to the PGW;

Specifically, the UE may send an update QoS request or a QoS confirmation indication to the PGW by using a bearer resource modification procedure or a new message flow. For example, the UE sends a bearer resource modification request message to the MME, where the message carries the update QoS request information or the QoS acknowledgement indication, and after receiving the bearer resource modification request, the MME sends a bearer resource command to the S-GW, where the command carries the updated QoS request information. Or the QoS confirmation indication (for example, carried by the PCO (Protocol Configuration Option) field, or carried by other fields outside the PCO), the S-GW forwards the bearer resource command to the PGW; or, the UE sends the update QoS request information to the MME. Or the request message of the QoS confirmation indication, the MME forwards the request message to the S-GW, and the S-GW forwards the request message to the PGW.

The QoS acknowledgment indication may again be referred to as an update QoS indication, which may be referred to as QoS. Confirm the request.

Step 2: After receiving the update QoS request or the QoS confirmation indication, the PGW initiates an IP connection access network (IP-CAN) session modification process to update the QoS.

• When there is no PCC deployment in the network, there is no PCEF in the P-GW. After receiving the update QoS request or QoS confirmation indication, the P-GW initiates session modification.

The above method further includes: after updating the QoS,

The UE sends a QoS information and/or a QoS acknowledgment message to the PGW, the QoS information and/or QoS acknowledgment message is used to indicate acceptance of the current QoS or not to accept the current QoS; the PGW maintains the current QoS according to the QoS information and/or the QoS acknowledgment message decision or The QoS is modified to the QoS before the update.

The UE may send QoS information and/or QoS confirmation message to the PGW through a bearer resource modification procedure or a new message flow. Specifically, the UE sends a bearer resource modification request message to the MME, where the message carries the QoS information and/or the QoS acknowledgement message, and after receiving the bearer resource modification request, the MME sends a bearer resource command to the S-GW, where the command carries the QoS information and / or QoS acknowledgment message, the S-GW forwards the bearer resource command to the PGW; or, the UE sends a request message carrying the QoS information and/or the QoS acknowledgment message to the MME, and the MME forwards the request message to the S-GW, S- The GW forwards the request message to the PGW.

The method may further include the following steps: after the PGW maintains the current QoS according to the QoS information and/or the QoS acknowledgment message, the PGW sends a bearer resource failure indication carrying the acknowledgment response to the S-GW (the acknowledgment response may be placed in the bearer resource failure indication). In the private extension field, the S-GW forwards the bearer resource failure indication to the MME, and the MME sends a bearer resource modification reject message to the UE as an acknowledgement response.

If the PGW modifies the QoS to the pre-update QoS according to the QoS information and/or the QoS acknowledgment message decision, the PGW initiates an IP-CAN session modification procedure to modify the QoS to the pre-update QoS.

When the PCC is deployed in the network, the PCRF is the decision body, the PCEF is the executive, and the PCEF is located in the PGW. After receiving the updated QoS request or the QoS confirmation indication, the PGW initiates the IP-CAN session modification process, including:

After receiving the update QoS request or the QoS confirmation indication, the PGW requests the PCRF to perform a session modification decision, and the PGW triggers the PCRF to initiate an IP-CAN session modification procedure. Specifically, the PGW requests the PCRF to perform a session modification decision by: the P-GW requests the PCRF to perform a session modification decision by using an IP-CAN session modification request message, where the IP-CAN session modification request message carries the updated QoS information.

The above method further includes: after updating the QoS,

The UE sends the QoS information and/or the QoS acknowledgement message to the PCRF. For example, the UE sends the QoS information and/or the QoS acknowledgement message to the PGW through the bearer resource modification procedure or the new message flow, and the PGW sends the QoS information and/or through the credit control request message. Or a QoS acknowledgment message is sent to the PCRF), the QoS information and/or the QoS acknowledgment message is used to indicate acceptance of the current QoS or not to accept the current QoS; the PCRF decides to maintain the current QoS or modify the QoS according to the QoS information and/or QoS acknowledgment message decision to QoS before update.

The foregoing method may further include the following steps: after the PCRF decides to maintain the current QoS according to the QoS information and/or the QoS acknowledgment message, the IP-CAN session modification indication message carrying the acknowledgment response is sent to the PGW, and the PGW sends a carry confirmation response to the S-GW. The bearer resource failure indication indicates that the S-GW forwards the bearer resource failure indication to the MME, and the MME sends a bearer resource modification reject message to the UE as a confirmation response.

If the PCRF modifies the QoS to the pre-update QoS according to the QoS information and/or QoS acknowledgment message decision, the PCRF initiates an IP-CAN session modification procedure to modify the QoS to the pre-update QoS.

The method further includes: after updating the QoS, the UE actively sends a request message carrying the updated QoS indication to the PGW or sends a notification response carrying the acknowledgment information; or the UE receives the acknowledgment sent by the PGW through the S-GW and the MME to the UE. After the indicated notification message, a request message carrying the updated QoS indication is sent to the PGW or a notification response carrying the confirmation information is sent.

The above QoS update includes an increase or decrease in QoS.

The system for implementing the above method includes a first sending module located at the terminal, and a first QoS update module located at the PGW, where:

The first QoS update module is configured to receive the update QoS request or QoS confirmation finger After the indication, the IP connection access network (IP-CAN) session modification process is initiated, and the QoS is updated. Preferably, the first sending module is further configured to: after the QoS is updated, send the QoS information and/or the QoS acknowledgement message to the PGW by using a bearer resource modification procedure or a new message flow, where the QoS information and/or the QoS acknowledgement message is used to indicate Accepting the current QoS or not accepting the current QoS; the first QoS update module is further configured to maintain the current QoS or modify the QoS to the pre-update QoS based on the QoS information and/or QoS acknowledgment message decision.

The first QoS update module is further configured to send a bearer resource failure indication carrying an acknowledgment response to the S-GW after the decision to maintain the current QoS, and send a confirmation response to the UE by using the S-GW and the MME.

Preferably, when the network is deployed by the PCC, the first QoS update module initiates an IP-CAN session modification process: after receiving the update QoS request or the QoS confirmation indication, requesting the PCRF to perform a session modification decision, triggering the PCRF to initiate an IP-CAN session modification process. .

Preferably, when the network has a PCC deployment, the first sending module is further configured to: after updating the QoS, send the QoS information and/or the QoS acknowledgement message to the PGW by using a bearer resource modification process or a new message flow, where the QoS information and The QoS acknowledgment message is used to indicate acceptance of the current QoS or not to accept the current QoS; the system further includes a second sending module located at the PGW, configured to send the QoS information and/or the QoS acknowledgment message to the PCRF through the credit control request message; The system also includes a second QoS update module located at the PCRF that is configured to maintain current QoS or modify QoS to pre-update QoS based on the QoS information and/or QoS acknowledgment message decisions.

Preferably, the first QoS update module requests the PCRF to perform a session modification decision in the following manner: The IP-CAN session modification request message requests the PCRF to perform a session modification decision, and the IP-CAN session modification request message carries the updated QoS information.

Preferably, the second QoS update module is further configured to: after the decision to maintain the current QoS, send an IP-CAN session modification indication message carrying an acknowledgment response to the PGW, and send the message to the UE by using the PGW, the S-GW, and the MME. Confirm the response.

Preferably, the first sending module is further configured to: after updating the QoS, actively send a request message carrying the updated QoS indication to the PGW or send a notification response carrying the acknowledgment information; or, after receiving the PGW, pass the S-GW, The notification sent by the MME to the UE carrying the confirmation indication After the message, a request message carrying the updated QoS indication is sent to the PGW or a notification response carrying the confirmation information is sent.

The first sending module is configured to send an update QoS request or a QoS confirmation indication to the PGW by using a bearer resource modification process or a new message flow.

In order to make the objects, the technical solutions and the advantages of the present invention more clearly, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments of the present application may be arbitrarily combined with each other.

Embodiment 1

In this embodiment, the UE accesses the 3GPP network in a non-roaming scenario, and uses a service of a third-party application service provider that does not have a cooperative relationship with the operator. The operator is responsible for providing transmission resources for the third-party application of the UE, and can extend the existing resource modification process according to the requirements of the UE to adjust the service quality and notify the UE to confirm, as shown in FIG. 9, the method for updating and confirming the quality of service in this embodiment Specifically, the method includes the following steps: Step 101: The UE attaches to the home network, establishes an RRC (Radio Resource Control) connection, establishes a radio bearer, initiates a service request, and creates an IP-CAN session.

Step 102: The UE successfully accesses the Non-IMS AS (non-IMS application server) service, where the UE and the Non-IMS AS use the application level signaling or the HTTP protocol, and the non-IMS AS provides the UE with the application service;

Step 103: The Non-IMS AS initiates an Rx session establishment request to the PCRF, and carries the UE ID/IP, Service ID/application ID, and flow information related information to the PCRF. The PCRF obtains the contract AS information from the SPR/UDC, and formulates and delivers the PCC. Rule establishes the relevant data bearer. Since the AS does not cooperate with the operator, the authorized QoS is default bearer QoS;

Step 104: Complete the creation of the bearer required for the service; the PCRF formulates the PCC/QoS rule according to the information sent by the client, such as the AS, the SPR/UDC, and the PGW, and delivers the PCC/QoS rule to the PCEF/BBERF; PCEF/BBERF installs and executes the relevant rules. The bearer binding is complete. If there is no matching bearer, the bearer setup request is sent to create a bearer. The PCRF may also carry the relevant event trigger. (event trigger), as well as usage monitoring threshold, monitoring keywords and other information; PCEF sets and executes related event reporting and usage monitoring functions after receiving the information;

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

Step 106: 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 initiates an update QoS request to the operator, triggering the QoS update. Process;

Step 107: The UE sends a Request Bearer Resource Modify Request message to the MME, where the request message carries updated QoS indication information.

The application layer related parameters are updated one by one. The QoS indication information can be carried in PC0 (protocol configuration option) or other AVP. In addition to updating the QoS indication, you can also set bear usage as the priority bearer with the same effect. In addition, the request message may also carry: UE IP/ID, bearer ID (LBI), stream description (TAD), packet filter ID (PTI), QoS, and the TAD indication message in the message is a modify type; If the application is a GBR bearer, the packet filter identifier (s) association needs to be carried in the modification request. If possible, the service ID/Application ID is also carried.

Step 108: The MME sends a bear resource command (bear resource command) message to the SGW, where the message includes the updated QoS indication information, and other related parameters.

Step 109: After receiving the message, the SGW forwards the bearer resource command message to the PGW, and the message carries the specific parameters received;

Step 110: The PCEF (located at the P-GW) determines, according to the received bearer resource command message, that the QoS needs to be updated (for example, according to carrying the priority bearer indication or updating the QoS indication, or the QoS of the service request is higher than the first QoS, etc.), The IP-CAN session modification process is initiated, and a session modification request is sent to the PCRF, where the message carries the UE IP/ID, the requested QoS (ie, updated QoS information), the TAD, and the SDF fileter lD.

This embodiment is a scenario for deploying a PCC. If it is not deployed in the network in other embodiments.

PCC, then steps 110-115 are not performed, and the policy decision is made by the PGW.

Steps 111-113: The PCRF compares the relevant application (correlate application) with the service information (service information), and reports to the AS if the AS signs the resource status or modifies the event. Related modifications;

Step 114: 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, updates the QoS according to the request), updates the PCC policy decision (olicy decision), and issues the updated PCC rules are given to 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.

Step 115: The PCRF sends the updated PCC/QoS rule to the PCEF, and the PCEF/BBERF updates the PCC/QoS rule, and the modified or newly created bearer satisfies the upgraded QoS. And feedback the rule execution response message to the PCRF (optional) to complete the session modification process;

Steps 116-123: The PGW executes the QoS policy, completes the bearer modification and binding, and sends an Update Bearer Request to the SGW, and the SGW forwards the message to the MME. The MME constructs a Bearer modify Request message to the eNodeB. With the Bear ID, QoS; the eNodeB maps the EPS bearer QoS to the radio bearer QoS, and sends an RRC CR (connection reconfiguration) message to the UE, the UE updates the storage-related QoS, and returns the relevant response (response) step by step. The message up to the PGW completes the bearer modification process.

Step 124: If the QoS update is successful, the QoS acknowledgement 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 accepting the updated QoS may need to be prioritized) The stream processing provides additional tariffs; if the user is not satisfied or disagrees with the payment of 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 by default. For the network, in the technical implementation, the user does not 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). Preferably, the UE can set the startup timerl after receiving the message of step 119. Timer), after the Timer 1 timeout (Timer) (Timerl validity period should ensure that the normal PCRF initiated IP-CAN session modification update QoS processing is completed, that is, the step 123 has ended, and the UE has been provided according to the new QoS. Application service), the UE bearer sends an acknowledgement request message to the application layer. User perception. After transmitting the request message, the UE can start the user confirmation timer Timer2.

Alternatively, the notification may be triggered by the UE itself, and the notification is sent by the network side, as in steps 224a-c of the second embodiment. Step 125: After receiving the acknowledgement message of the UE application layer, if the user is satisfied with the updated (eg, promoted) service data flow and is willing to pay the fee for the priority flow processing, the user confirms the message, and the UE sends the acknowledgement to the affirmative Acknowledgement message to the network (carrying positive acknowledgment information in the PCO in request bearer resource modification), the operator will continue to provide updated QoS for the service according to the acknowledgment (for example, continue to perform priority flow processing, provide high priority or High bandwidth resources). If the UE is dissatisfied with the quality of service or user experience of the upgraded service data flow or 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 network, 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 may construct a negative acknowledgment message to be sent to the network according to the operator's requirement (the negative acknowledgment information is carried in the PCO in the request bearer resource modification), if If the user does not confirm, the application layer needs to trigger the bearer layer construction negative acknowledgement message to be sent to the network after the timer2 timeout waiting for the acknowledgement. The network will restore the QoS to the level before the request promotion after a certain preview time; Step 126 The MME receives the bearer resource request message of the UE, and sends a bearer resource command to the SGW, carrying parameters in the original message, such as QoS, PCO (which carries a positive or negative acknowledgement information or indication);

In other embodiments, other fields other than the PCO may be used to carry the positive or negative confirmation message or indication.

Step 127: The SGW forwards the message to the PGW, and carries parameters such as QoS and PCO. Step 128: The PCEF initiates an IP-CAN session modification process, and the PGW determines the QoS required by the user service according to the acknowledgement information/indication in the PCO. Then, step 129 is performed; if it is a negative acknowledgement, an IP-CAN session modification request is sent (if the diameter protocol is used between the PCEF and the PCRF, the IP-CAN session modification request message and other IP sessions can be carried by using the credit control request message. Related message) Initiating a session modification process for the PCRF, downgrading the QoS; after receiving the degraded QoS request message, the PCRF combines the subscription information with the local policy (for example, the user confirms that the Preview timer of the update QoS is timed out and needs to reply) The original QoS) initiates the IP-CAN session modification process, or may initiate a GWcontrol or TDF session modification procedure, correspondingly, updating the relevant PCC rules, or possibly QoS rules or ADC rules, to restore the original QoS of the service; For the CAN session modification process, refer to steps 110-123 to modify the bearer and session. The QoS provided for the service will be restored to the user promotion request. Level, according to the original QoS continue Step 132 is performed to provide a downlink service data flow.

It should be noted that the QoS fallback mechanism is not within the scope of this document. For example, the timer mechanism between network elements can be used to process the backoff time of the session modification, and the QoS before the update can be stored locally, or when the UE sends the downgrade QoS request message. Carry the previous QoS information, or carry the default QoS indication in the request message.

Step 129: After receiving the positive acknowledgment message, the PGW sends a bear recourse failure indication to the SGW, where the message carries the bearer ID, the PTI, the reason for the failure, and the private extension field (indicating the message is Confirmed response); no modification to the resource, just as an ACK message;

Step 130: The SGW forwards the message to the MME, and sends a confirmation response in the private extension field.

( confirm response ) , no modification to the resource, just as an ACK message;

Step 131: The bear recourse modification reject message is sent to the UE, and the PTI and the ESM cause (the cause) are sent; if the UE determines that the message is a confirmation response, the user confirm process is not triggered again. The process of improving the QoS request and the confirmation is completed;

Step 132: The process of upgrading or restoring the QoS process is completed. If it is step 128, after the downgrade QoS is completed, the downlink data is transmitted according to the initial QoS; if the QoS success confirmation step 131 is updated, 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.

In the above process description, the update QoS indication is carried in the PCO to the network, and the AVP field may be added to the PCO to carry the indication; the specific message flow is the same as that described above, and is not repeated here;

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 network elements such as BBERF/TDF and the charging network element OCS/OFCS and other charging systems; this part of the processing is beyond the scope of this article, so it will not be described in detail here;

The above steps 101-132 are the processing flow of the non-roaming scenario. If the UE roams to the visited place during the service use (see Figure 4, the roaming home routed scenario), Then, the UE needs to be notified of the roaming. If the QoS is increased, the UE needs to re-confirm whether it needs to maintain the high QoS/high priority flow processing. If the user confirms the high QoS processing of the service, an additional high priority flow may be required. Processing fee), if the user confirms, the visited place still provides high QoS for the UE. If the user does not confirm or negatively confirm, the visited place will use the default QoS to provide the service; the specific steps are as shown in Figure 10:

Step 133: The HPCRF learns that the UE has roamed, sends a QoS confirmation indication to the UE, notifies the UE to roam, and sends a confirmation message (confirm inform) to the UE, requesting the UE to confirm whether the QoS service flow will continue to be used in the visited place. The message carries a confirm indication, and other related information such as UEID/IP and QoS, and possibly other service information, such as flow information, service ID/application ID, etc.;

Here, the HPCRF indirectly informs the UE through the intermediate logic function or the network element or directly sends the UE to confirm that the notification is not within the scope of the discussion herein (for example, a client may be sent by the PCRF to send a notification, or through other applications. The function network element notifies the UE by HTTP). Sending a priority flow to process a high QoS acknowledgment request message to the UE, requesting the user to confirm whether to retain the high QoS flow processing, and returning a positive acknowledgment message if agreed (confirming that retaining high QoS may require additional tariff for this priority stream processing); If you agree to pay the additional priority stream processing fee, you will return a negative confirmation or no confirmation. If the user does not confirm, the terminal device may construct a negative acknowledgment and return it to the network, which facilitates the technical implementation to distinguish the user from sending the acknowledgment and acknowledging the message loss. Abnormal situation, but the specific processing is handled according to the carrier network);

Step 134: After receiving the acknowledgement message, if the UE wants to reserve the high QoS and is willing to pay the fee for the priority stream processing, the UE confirms the message, and the UE sends the acknowledgement response message to the network, and further feeds back to the home PCRF. The operator will continue to provide high QoS for this service (for example, continue with priority flow processing to provide high priority or high bandwidth resources).

If the UE is not willing to pay additional priority processing fees and does not want to use high priority flow processing or high QoS, the user does not acknowledge the acknowledgment request (does not return a response message) or returns a negative acknowledgment message (acknowledgement response message, or downgrade QoS request message) ) to the network. If the user does not agree to provide the service with high QoS but does not make a negative acknowledgment, the terminal device optionally constructs a negative acknowledgement message to the network according to the operator's requirements, and performs step 134a;

Step 134a: If the network does not receive the acknowledgement receiving message from the user within the specified time, or receives the message If the user confirms the rejection message or updates the QoS request message, the PCRF will likely initiate an IP-CAN session modification procedure to update the QoS request (eg, downgrade QoS);

The HPCRF combines subscription information with local policies (for example, the user confirms that the Preview timer timeout for retaining high QoS requires lowering the QoS), initiates an IP-CAN or GWcontrol or TDF session modification procedure, updates the relevant PCC or QoS or ADC rules, and restores the default of the service. QoS; If the QoS request message sent by the UE is sent to the PGW, the IP-CAN session modification procedure may also be initiated by the PCEF.

The network restores the service data stream to the default QoS, and delivers the service data stream according to the default bearer QoS.

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

In the above process, the S9 session of the specific home location and the roaming place is implemented according to the prior art; in addition, the scene of the local local access of the roaming local access, the notification confirmation and the QoS tampering process are the same as above, and the description is not repeated herein.

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

Embodiment 2

In this embodiment, the UE accesses the 3GPP network, and uses the service of the third-party application service provider that has no cooperation relationship with the operator. The operator is responsible for providing transmission resources for the third-party application of the UE, and can extend the existing resource modification process according to the requirements of the UE to adjust the service quality and notify the UE to confirm. As shown in FIG. 11, the method for updating and confirming the quality of service of the present invention is specific. Including the following steps: Step 201: The UE attaches to the home network, establishes a radio bearer, and creates an IP-CAN session. Step 202: The UE successfully accesses the Non-IMS AS service, where the UE and the Non-IMS AS use the application level signaling or the HTTP protocol, non-IMS. The AS provides an application service for the UE. Step 203: The Non-IMS AS initiates an Rx session establishment request to the PCRF, and carries the UE ID/IP, Service ID/application ID, and flow information related information to the PCRF. The PCRF obtains the contracted AS information from the SPR/UDC, and formulates and delivers the PCC rule to the PCEF to establish a related data bearer. Since the AS does not cooperate with the operator, the authorization QoS is the default bearer QoS;

Step 204: Complete the creation of the bearer required for the service; the PCRF formulates the PCC/QoS rules according to the information sent by the client, such as the AS, the SPR/UDC, and the PGW, and delivers the PCC/QoS rules to the PCEF/BBERF; PCEF/BBERF installs and executes the relevant rules. After the bearer binding is complete, if there is no matching bearer, the bearer setup request is sent to create a bearer; while the PCRF delivers the rule, it may also carry the relevant event trigger, and the usage monitoring threshold, monitoring keywords and other information; PCEF receives Set and execute related event reports and usage monitoring functions after the information;

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

Step 206: In the service process, the UE finds that the QoS of the QoS or the user experience is not satisfactory (for example, the data stream is unstable due to mobility or network conditions, or the bandwidth is too low, etc.), and initiates an QoS request to the operator to trigger the UE request. Process;

Step 207: The UE sends a request (Request) message to the MME, where the request message carries the updated QoS indication information, and the request message further carries the type of the request (update QoS), the UE IP/ID, the bearer ID (LBI), and the flow information. (eg Stream Description (TAD), Packet Filter ID (PTI), etc.), QoS. If the service/application is originally a GBR bearer, the request may carry a packet filter identifier(s); and if possible, a Service ID/Application ID;

Step 208: The MME forwards a request message to the SGW, where the message includes the relevant parameters in step 207.

Step 209: After receiving the message, the SGW forwards the request message to the PGW, and the message carries the specific parameters received; Step 210: The PCEF determines, according to the received request message parameter, that the QoS needs to be updated (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.), and initiates the IP- The CAN session modification process processes, and sends a session modification request to the PCRF. The message carries parameters such as UE IP/ID, requested QoS, flow information (such as TAD, and SDF fileter ID).

Step 211-213: The PCRF compares the relevant rules and service information. If the AS signs the resource status or modifies the event, it reports the relevant modification to the AS.

Step 214: 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.

Step 215: The PCEF/BBERF updates the PCC/QoS rule, and the modified or newly created bearer satisfies the upgraded QoS. And feedback the rule execution response message to the PCRF to complete the session modification process.

Steps 216-223: The PGW executes the QoS policy, completes the bearer modification and binding, and sends an Update Bearer Request to the SGW, and the SGW forwards the message to the MME. The MME constructs a bearer modification request message and sends it to the eNodeB, with the Bear ID. QoS; The eNodeB maps the EPS bearer QoS to the radio bearer QoS, and delivers the RRL CR message to the UE. The UE updates the storage-related QoS, and returns the relevant response message to the PGW step by step to complete the bearer modification process.

Step 224: If the update QoS is successful, the UE needs to send an update QoS confirmation 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 acknowledgment message (acknowledging that the QoS after accepting the update may need 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 acknowledgement and the acknowledgement message is lost, but the specific processing is implemented according to the carrier network.) In the process, the UE may set the start timerl after receiving the message of step 219. Timer), after the Timerl timing timeout (Timerl validity period should ensure that the normal PCRF initiated IP-CAN session modification update QoS processing is completed, that is, step 223 has ended, and the application service has been provided for the UE according to the new QoS) UE bearing The acknowledgment request message is sent to the application layer for the user to perceive. After transmitting the request message, the UE may enable the user acknowledgement timer Timer2.

Alternatively, instead of triggering the sensing by the UE itself, the network side sends a notification, and steps 224a-c are performed instead of step 224:

Step 224a: 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 is sent. Carrying a confirmation indication, indicating that the QoS update requested by the user is completed, requesting confirmation;

Step 224b: After receiving the notification message, the SGW sends the notification to the MME, for example, the UEID/IP, the necessary service flow information, and the confirmation indication are carried in the 224a;

Step 224c: The MME sends the message to the UE. After receiving the notification message, the UE provides a notification indication to the upper layer (for example, the application layer) to trigger the user to be aware;

Optionally, if it is not the request message of the subsequent step 225, the 224a-c step has an uplink response message.

Step 225: After receiving the acknowledgement message of the UE application layer, if the user is satisfied with the updated (for example, promoted) service data flow and is willing to pay the fee for the priority flow processing, the user confirms the message, and the UE sends a positive confirmation. The message is sent to the network (with a positive acknowledgment in the request or notification response), and the operator will continue to provide updated QoS for the service based on the acknowledgment (eg, continue to perform priority flow processing to provide high priority or high bandwidth resources) ). If the UE is not satisfied with the quality of service or user experience of the upgraded service data flow and is unwilling to pay additional priority processing fees, the acknowledgment request is not confirmed (no acknowledgment response message is returned) or a negative acknowledgment message is returned to the network ( That is, 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 timer2 timeout expires, the bearer layer construction false 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; in other embodiments, in addition to carrying the acknowledgement information in the request or notification response, The update QoS indication may also be carried in the request or notification response.

Step 226: The MME receives the request or notification response message of the UE, and forwards the message to the SGW. Carrying parameters in the original message, such as UE IP/ID, QoS, positive or negative acknowledgment information/indication, etc.; Step 227: The SGW forwards the message to the PGW, carrying parameters such as QoS and acknowledgment information/indication; Step 228: PGW according to The acknowledgment information/instruction determines the QoS required for the user's service. If the acknowledgment is positive, step 229 is performed.

If the acknowledgment is negative, the IP-CAN session modification request is sent to the PCRF to initiate a session modification process, and the QoS is downgraded; 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 updated QoS is timed out) Revert to the original QoS), initiate the IP-CAN or GWcontrol or TDF session tampering process, update the relevant PCC or QoS or ADC rules, and restore the original QoS of the service; the IP-CAN session modification process is described in steps 210-223, modifying the bearer and The QoS provided for the service will be restored to the level before the user upgrade request, and the downlink service data flow is continued according to the original QoS. (The QoS fallback mechanism is not within the scope of this document, and for example, the network element may be used. The inter-timer mechanism handles the retracement backoff time of the session, and locally stores the QoS before the update, or the UE carries the previous QoS information when sending the downgrade QoS request message, or the request message carries the default QoS indication, etc.) .

Preferably, if the step 225-227 is a UE request message, there is a downlink response message, from

PGW to UE.

Step 229: Upgrade or restore the QoS process is completed. If it is step 228, after the downgrade QoS is completed, the downlink data is transmitted according to the initial QoS; if the QoS success confirmation step 227 is updated, the downlink data is transmitted according to the upgraded QoS. That is, the network continues to provide traffic data for the service in accordance with the authorized QoS.

In other embodiments, steps 224a-224c may have corresponding response messages. Steps 225-227 may also have corresponding response messages. Preferably, steps 225-227 may be response messages of 224a-224c.

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 scope of this discussion, so this embodiment will not be described in detail herein; The above steps 201-229 are the processing flow of the non-roaming scenario. If the UE roams to the visited place during the service usage (see Figure 4, the routing scenario is the roaming attribution), the UE needs to be notified of the roaming. It is also necessary for the UE to reconfirm whether it is necessary to maintain high QoS/high priority flow processing (if the user confirms the high QoS processing of the service, an additional high priority flow processing fee may be required), and if the user confirms, the visited place remains the same. The UE provides high QoS. If the user does not confirm or negate the acknowledgment, the visited QoS will be used to provide the service. The specific steps are the same as the steps 133-135. There is no duplication of description here. The message that the network side notifies the UE to acknowledge the message may use the messages of the steps 224a-224c, and may also reuse other existing messages, which is not limited herein.

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

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

Embodiment 3

The present embodiment is based on FIG. 5, and FIG. 5 is a structural diagram of a non-roaming network based on GBA. The UE described in this embodiment accesses a 3GPP network in a non-roaming scenario, and uses a third-party application service provider that has no cooperation relationship with the operator. Business. The operator is responsible for authenticating and transmitting resource allocation to the UE and the third-party application provider, adjusting the quality of service according to the needs of the UE, and notifying the UE to confirm, such as As shown in FIG. 12, the method for updating and confirming the quality of service of the present invention specifically includes the following steps: Step 301: A UE attaches to a home network, establishes a radio bearer, and creates an IP-CAN session. Step 302: The UE accesses the Non-IMS AS/ NAF, in the bootstrapping mode of the GBA, the UE sends a registration request to the BSF, and carries the UEID; the BSF obtains the subscription information and the authentication vector from the HSS, and the BSF completes the authentication of the UE, generates the Ks and the B-TID, and The B-TID is returned to the UE, and the UE sends an application request to the NAF/Non-IMS AS to carry the B-TID. The NAFNon-IMS AS initiates an authentication request to the BSF by using the BTID, and returns a response to the UE after success. The UE establishes a secure session with the Non-IMS AS;

Step 303: The NAF/Non-IMS AS initiates an Rx session establishment request to the PCRF, and carries the UE ID/IP, Service ID/application ID, and flow information related information to the PCRF. The PCRF obtains the contracted AS information from the SPR/UDC, and formulates and delivers the PCC rule to the PCEF to establish a related data bearer. Because the AS does not cooperate with the operator, the QoS is the default bearer QoS; Step 304: Complete the bearer creation of the service; The PCRF formulates the PCC based on the information sent by the client such as Non-IMS 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 there is no matching bearer, the bearer setup request is sent and the bearer is created. The PCRF may also carry the relevant rules. Event trigger, and usage monitoring threshold, monitoring keywords and other information; PCEF sets and executes related event reporting and usage monitoring functions after receiving the information;

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

Steps 306-332: 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), and initiates an elevation QoS request to the operator; The request process and the operator update the QoS according to the user request and send an acknowledgment message to the user, and the related processing according to the user confirmation to continue or adjust the QoS is the same as steps 106-132; the above description is based on the reuse resource modification process, and may also comply with the second embodiment. The request and notification processing message in the specific implementation is the same as that in the second embodiment, and the description is not repeated here.

Embodiment 4 The present embodiment is based on FIG. 6, and FIG. 6 is based on the OpenID and GBA network structure. The UE described in this embodiment accesses the 3GPP network in a non-roaming scenario, and uses the service of the third-party application service provider that has no cooperation relationship with the operator. The operator is responsible for authenticating and transmitting resource allocation to the UE and the third-party application provider, adjusting the quality of service according to the needs of the UE, and notifying the UE to confirm. As shown in FIG. 13, the method for updating and confirming the quality of service of the present invention specifically includes the following steps:

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

Step 403: The RP/Non-IMS AS initiates an Rx session establishment request to the PCRF, and carries the UE ID/IP, Service ID/application ID, and flow information related information to the PCRF. The PCRF obtains the contracted AS information from the SPR/UDC, and formulates and delivers the PCC rule to the PCEF to establish the relevant data bearer. Since the AS does not cooperate with the operator, the authorized QoS is the default bearer QoS;

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

Step 405: The service bearer is created, and the network provides the downlink transmission of the service data for the UE according to the authorized QoS. Steps 406-432: 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 an elevation QoS request to the operator. The request process and the operator update the QoS according to the user request and send an acknowledgment message to the user, according to the user confirmation to continue or adjust the QoS related processing is the same as steps 106-132;

The above description is based on the re-use of the resource modification process, and can also be processed in accordance with the request and notification in the second embodiment. The specific implementation is the same as that in the second embodiment, and the description is not repeated here.

The above IP-CAN session modification process, PCC is an optional feature. If there is a PCC, all the modification request PGWs need to be sent to the PCRF decision, and the PCRF issues the rules to the PGW to perform the process modification. If there is no PCC deployment, the relevant modification request can be sent to the PGW. No longer - description in the relevant embodiment.

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

It is a matter of course that the invention may be embodied in various other forms and modifications without departing from the spirit and scope of the invention.

Industrial applicability

By using the method of the embodiment of the present invention, the user can first experience the improved QoS and then decide whether to connect the QoS, thereby providing the service quality according to the requirements of the user.

Claims

Claim

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

In the service process, the terminal (UE) sends an update quality of service (QoS) request or QoS confirmation indication to the packet data network gateway (PGW);

After receiving the update QoS request or the QoS confirmation indication, the PGW initiates an IP-Connected Network (IP-CAN) session modification procedure to update the QoS.

2. The method of claim 1, wherein the step of initiating the IP-CAN session modification process after the PGW receives the update QoS request or the QoS confirmation indication comprises:

3. The method of claim 1 further comprising:

After updating the QoS, the UE sends a QoS information and/or a QoS acknowledgement message to the PGW, where the QoS information and/or the QoS acknowledgement message is used to indicate acceptance of the current QoS or not to accept the current QoS;

4. The method of claim 2, further comprising:

5. The method of claim 1, wherein the step of the UE transmitting an update QoS request or a QoS acknowledgement indication to the PGW comprises:

The UE sends an update QoS request or a QoS confirmation indication to the PGW by using a bearer resource modification process or a new message flow.

6. The method of claim 2, wherein

The step of the PGW requesting the PCRF to perform a session modification decision includes: the PGW passing

The IP-CAN session modification request message requests the PCRF to perform a session modification decision, and the IP-CAN session modification request message carries the updated QoS information.

The method of claim 5 or 6, wherein the step of the UE transmitting the update QoS request or the QoS confirmation indication to the PGW by using a bearer resource modification procedure or a new message flow process includes: the UE to the mobility management unit (MME) Transmitting a bearer resource modification request message, carrying an update QoS request information or a QoS acknowledgement indication, and after receiving the bearer resource modification request message, the MME sends a bearer resource command to the serving gateway (S-GW), and carries the updated QoS request information or QoS confirmation indication, the S-GW forwards the bearer resource command to the PGW; or

8. The method of claim 7, wherein

9. The method of claim 3, wherein the UE sends QoS information to the PGW and/or

The steps of the QoS confirmation message include:

The UE sends the QoS information and/or the QoS acknowledgement message to the PGW by using a bearer resource modification procedure or a new message flow.

10. The method of claim 4, wherein the step of the UE transmitting the QoS information and/or the QoS acknowledgement message to the PCRF comprises:

The UE sends the QoS information and/or the QoS acknowledgement message to the PGW through the bearer resource modification procedure or the new message flow, and the PGW sends the QoS information and/or the QoS acknowledgement message to the PCRF through the credit control request message.

The method of claim 9 or 10, wherein the step of the UE transmitting the QoS information and/or the QoS acknowledgement message to the PGW by using the bearer resource modification process or the new message flow comprises: sending, by the UE, the bearer resource to the MME Modifying the request message, carrying the QoS information and/or the QoS acknowledgment message, after receiving the bearer resource modification request message, the MME sends a bearer resource command to the S-GW, carrying the QoS information and/or the QoS acknowledgement message, where the S- The GW forwards the bearer resource command to the PGW; or

12. The method of claim 3, further comprising:

After the PGW decides to maintain the current QoS according to the QoS information and/or the QoS acknowledgment message, the PGW sends a bearer resource failure indication carrying an acknowledgment response to the S-GW, and the S-GW forwards the bearer resource failure indication to the MME. The MME sends a bearer resource modification reject message to the UE as a confirmation port response.

13. The method of claim 12, wherein

14. The method of claim 4, further comprising:

After the PCRF decides to maintain the current QoS according to the QoS information and/or the QoS acknowledgment message, the IP-CAN session modification indication message carrying the acknowledgment response is sent to the PGW, and the PGW sends the bearer carrying the acknowledgment response to the S-GW. The resource failure indication, the S-GW forwards the bearer resource failure indication to the MME, and the MME sends a bearer resource modification reject message to the UE as a confirmation response.

15. The method according to claim 3, wherein the step of the PGW modifying the QoS to the pre-update QoS according to the QoS information and/or the QoS acknowledgment message decision comprises:

The PGW initiates an IP-CAN session modification procedure to modify the QoS to the pre-update QoS.

16. The method according to claim 4, wherein the step of the PCRF modifying the QoS to the pre-update QoS according to the QoS information and/or the QoS acknowledgment message decision comprises:

The PCRF initiates an IP-CAN session modification procedure to modify the QoS to the pre-update QoS.

17. The method of claim 1 or 2, further comprising:

18. A system for updating quality of service, comprising a first transmitting module at a terminal (UE) and a first QoS update module at a packet data network gateway (PGW), wherein:

19. The system of claim 18, wherein the first QoS update module is configured to initiate an IP-CAN session modification process in the following manner:

Receiving the updated QoS request or when the network has a Policy and Charging Control (PCC) deployment

After the QoS confirmation indication, the request policy and charging rule function (PCRF) performs a session modification decision, and triggers the PCRF to initiate an IP-CAN session modification process.

20. The system of claim 18, wherein

21. The system of claim 19, further comprising a second transmitting module at the PGW and a second QoS update module at the PCRF,

The first sending module is further configured to: after updating the QoS, send the QoS information and/or the QoS acknowledgement message to the PGW by using a bearer resource modification process or a new message flow, where the QoS information and/or the QoS acknowledgement message is used. Indicates acceptance of current QoS or does not accept current QoS; The second sending module is configured to send the QoS information and/or the QoS confirmation message to the PCRF by using a credit control request message;

The second QoS update module is configured to maintain current QoS or modify QoS to pre-update QoS based on the QoS information and/or QoS acknowledgment message decision.

22. The system of claim 18 or 19, wherein the first transmitting module is configured to: send an update QoS request or a QoS acknowledgement indication to the PGW in the following manner:

23. The system of claim 19, wherein the first QoS update module is configured to request the PCRF to make a session modification decision in the following manner:

24. The system of claim 20, wherein

The first QoS update module is further configured to: after the decision to maintain the current QoS, send a bearer resource failure indication carrying an acknowledgment response to the serving gateway (S-GW), and the S-GW and the mobility management unit (MME) The UE sends a confirmation response.

25. The system of claim 21, wherein

26. The system of claim 18 or 19, wherein