WO2016206354A1 - 第三方应用的策略控制方法、scef和pcrf - Google Patents

第三方应用的策略控制方法、scef和pcrf Download PDF

Info

Publication number
WO2016206354A1
WO2016206354A1 PCT/CN2016/070084 CN2016070084W WO2016206354A1 WO 2016206354 A1 WO2016206354 A1 WO 2016206354A1 CN 2016070084 W CN2016070084 W CN 2016070084W WO 2016206354 A1 WO2016206354 A1 WO 2016206354A1
Authority
WO
WIPO (PCT)
Prior art keywords
party
qos
service
information
pcrf
Prior art date
Application number
PCT/CN2016/070084
Other languages
English (en)
French (fr)
Inventor
吴锦花
周晓云
梁爽
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016206354A1 publication Critical patent/WO2016206354A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints

Definitions

  • the present invention relates to a communication technology, and particularly relates to a policy control method for a third-party application, a Service Capability Exposure Framework (SCEF), and a Policy and Charging Rules Function (PCRF). ), computer storage media.
  • SCEF Service Capability Exposure Framework
  • PCRF Policy and Charging Rules Function
  • the Policy and Charging Control (PCC) architecture of the 3rd Generation Partnership Project (3GPP) is a functional framework that can be applied to multiple access technologies.
  • UTRAN Universal Mobile Telecommunications System
  • UMT Universal Mobile Telecommunications System
  • GSM Global System for Mobile Communication
  • EDGE Enhanced Data Rates for Global Evolution
  • I-WLAN interworking wireless local area network
  • EPS Evolved Packet System
  • FIG. 1 is a schematic diagram of a related art Rel-9 PCC non-roaming architecture. The following describes various logical functional entities and their interface functions in the PCC architecture with reference to FIG. 1:
  • AF Application Function Entity
  • PCRF Policy and Charging Rules Function
  • 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 monitoring, Gating Control, Quality of Service (QoS) control, and data flow based charging rules. .
  • the PCRF sends its policy and charging rules to the Policy and Charging Enforcement Function (PCEF).
  • PCEF Policy and Charging Enforcement Function
  • 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 of the user policy charging control from the Subscription Profile Repository (SPR); and acquiring the network related to the bearer from the PCEF. information.
  • the PCEF is used to perform the policy and charging rules formulated by the PCRF on the bearer plane.
  • the PCEF monitors 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.
  • the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF.
  • 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, the PCEF needs to perform credit management together with the Online Charging System (OCS).
  • OCS Online Charging System
  • the interface between the PCEF and the PCRF is a Gx interface
  • the interface between the OCE and the OCS is a Gy interface
  • the interface between the OFCS and the OFCS is a Gz interface.
  • the PCEF function can also be enhanced to implement the flow detection function (TDF, referred to as Traffic Detection Function).
  • TDF Traffic Detection Function
  • the PCEF can perform application detection and policy enforcement according to the local configuration or the PCC rule that is sent by the PCRF and includes the Application Detection and Control (ADC). Lines (such as gating, redirection, and bandwidth restrictions).
  • the PCEF is usually located in a Gateway (Gate-Way, GW for short), such as a GPRS Gateway Support Node (GGSN) in GPRS and a Packet Data Gateway (PDG) in I-WLAN.
  • GGSN GPRS Gateway Support Node
  • PDG Packet Data Gateway
  • the TDF can also be deployed independently.
  • the interface between the TDF and the PCRF is the Sd interface.
  • the TDF can perform application detection and policy execution according to the application detection control rules delivered by the pre-configuration or PCRF.
  • the PCRF provides application detection control rules for the independent TDF, and the policy control execution operations of the independent TDF function include gating, redirection, and bandwidth limitation.
  • the TDF reports the related events and information of the detected service/flow to the PCRF, and sends a description of the service data flow to the PCRF, and transmits the signaling of the traffic detection and policy rules for the flow detection from the PCRF.
  • TDF has two modes: request service report and active service report: request service report mode, PCRF will notify TDF which services need to be detected and reported to PCRF; active service report mode, which services are pre-configured in TDF, which need to be detected and reported. The mode assumes that the user agrees not to request and execute.
  • Bearer Binding and Event Reporting Function whose functions include bearer binding, verification of uplink bearer binding, and event reporting.
  • BBERF Bearer Binding and Event Reporting Function
  • the BBERF is located at the S-GW, and when the UE accesses through the trusted non-3GPP access system, the BBERF is located in the trusted non- The 3GPP access gateway, when the UE accesses through the untrusted non-3GPP access system, the BBERF is located in the Evolved Packet Data Gateway (ePDG). At this time, the PCEF no longer performs the bearer binding function.
  • ePDG Evolved Packet Data Gateway
  • the User Contracted Database 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 together with the PCEF, controls and manages user credits in the online charging mode.
  • the offline charging system (OFCS), together with the PCEF, performs the charging operation in the offline charging mode.
  • IP-CAN IP Connectivity Access Network
  • PDN Packet Data Network
  • SCEF Service Capability Exposure Framework
  • the PCRF can perform QoS authorization on the IP-CAN session or the service data flow SDF of the UE according to the SPR subscription information, and generate a corresponding policy or charging rule, which is sent to the PCEF for installation and execution.
  • the carrier network needs to perform QoS authorization and service on the overall service capability of the third-party AS to access the 3GPP system, in addition to performing corresponding QoS authorization on the service according to the subscription of the user (corresponding UE).
  • the third-party AS contracted service performs QoS authorization.
  • the embodiments of the present invention provide a third-party application policy control method, a SECF, a PCRF, and a computer storage medium, which can implement overall QoS authorization for a third-party AS under the SCEF architecture, and can also implement QoS authorization for a third-party AS subscription service. .
  • the present invention provides a policy control method for a third-party application, where the method includes:
  • the service capability open network SCEF makes an authorization decision on the overall subscription quality of service QoS of the third-party application server AS;
  • the QoS request is used to enable the PCRF to make an authorization decision on the QoS of the service requested by the user terminal UE to generate a policy and charging control rule.
  • the SCEF stores the overall subscription information of the third-party AS, and the overall subscription information of the third-party AS includes at least one of the following:
  • the identifier of the third-party AS, the maximum bit rate MBR pre-signed by the third-party AS, the guaranteed bit rate GBR pre-signed by the third-party AS, and the maximum number of users pre-signed by the third-party AS, the third party The type and type of the service allowed by the AS in advance, and the QoS level information of the third-party AS.
  • the SCEF makes an authorization decision on the overall subscription QoS of the third-party AS, including:
  • the SCEF performs an authorization decision on the overall subscription QoS of the third-party AS according to the overall subscription information of the locally stored third-party AS and the QoS request of the third-party AS.
  • the QoS request includes service information requested by the UE, QoS information corresponding to the service requested by the UE, and overall QoS authorization decision information for the third-party AS.
  • the present invention provides a policy control method for a third party application, the method include:
  • the policy and charging rule function entity PCRF receives the QoS request from the third-party AS sent by the service capability open network SCEF;
  • the overall subscription information of the third-party AS is stored in the user subscription database SPR or predefined in the PCRF.
  • the overall subscription information of the third-party AS includes at least one of the following: an identifier of the third-party AS, an MBR pre-signed by the third-party AS, a GBR pre-signed by the third-party AS, and the first The maximum number of users pre-signed by the three-party AS, the types and types of allowed services pre-signed by the third-party AS, and QoS level information.
  • the QoS request carries information about a service requested by the UE and QoS information corresponding to the service requested by the UE.
  • the QoS request carries IP filtering information and application type information for the policy control differentiated service data flow SDF, application bandwidth requirement, overall subscription information of the third-party AS, time period for requesting QoS, or traffic threshold. information.
  • the present invention provides a service capability open network SCEF, where the SCEF includes:
  • the first authorization decision unit is configured to perform an authorization decision on the overall subscription quality of service QoS of the third-party application server AS;
  • the sending unit is configured to send a QoS request to the policy and charging rule function entity PCRF, where the QoS request is configured to enable the PCRF to make an authorization decision on the QoS of the service requested by the user terminal UE to generate a policy and charging control rule.
  • the SCEF further includes a first storage unit configured to store the third-party AS
  • the overall contract information of the third party AS includes at least one of the following:
  • the identifier of the third-party AS, the maximum bit rate MBR pre-signed by the third-party AS, the guaranteed bit rate GBR pre-signed by the third-party AS, and the maximum number of users pre-signed by the third-party AS, the third party The type and type of the service allowed by the AS in advance, and the QoS level information of the third-party AS.
  • the first authorization decision unit is further configured to perform an authorization decision on the overall subscription QoS of the third-party AS according to the overall subscription information of the third-party AS and the QoS request of the third-party AS.
  • the present invention provides a policy and charging rule function entity PCRF, where the PCRF includes:
  • a receiving unit configured to receive a QoS request from a third-party application server AS sent by the service capability open network SCEF;
  • the second authorization decision unit is configured to perform authorization decision on the overall subscription QoS of the third-party AS according to the overall subscription information and the user subscription information of the third-party AS, and perform authorization decision on the QoS of the UE requesting service, and generate a policy. And billing control rules.
  • the PCRF further includes a second storage unit configured to store overall subscription information of the third party AS.
  • an embodiment of the present invention provides a computer storage medium, where the computer storage medium stores executable instructions, and the executable instructions are configured to execute a policy control method of any one of the foregoing third-party applications.
  • the SCEF and the PCRF perform the hierarchical authorization decision, or the PCRF uniformly performs the authorization decision, and implements the overall QoS authorization of the third-party AS and the QoS authorization of the third-party AS service, in addition to ensuring the third party under the SCEF architecture.
  • the normal operation of the AS service can also make network resources more rationally allocated and avoid excessive traffic of third-party AS services in the network. Or the number of users is too large, resulting in excessive network load, and affecting the use of other users or services (such as the carrier's own business of users signing up for such services).
  • FIG. 1 is a schematic diagram of a Rel-9 PCC non-roaming architecture according to the related art
  • FIG. 2 is a schematic diagram of a PCC non-roaming architecture with SCEF deployment
  • FIG. 3 is a schematic flowchart 1 of an implementation process of policy control in a SCEF architecture according to an embodiment of the present invention
  • FIG. 4 is a second schematic diagram of an implementation process of policy control in a SCEF architecture according to an embodiment of the present invention.
  • 5a and 5b are schematic diagrams showing the functional structure of an SCEF according to an embodiment of the present invention.
  • 6a and 6b are schematic diagrams showing the functional structure of a PCRF according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a third-party AS session establishment process for hierarchically authorizing SCEF and PCR according to an embodiment of the present invention
  • FIG. 8 is a schematic diagram of a third-party AS session establishment process of a PCRF unified authorization decision according to an embodiment of the present invention.
  • the embodiment of the invention provides a policy control method under the SCEF architecture, which can implement global policy control on a third-party AS service.
  • the policy control method for a third-party application in the SCEF architecture described in the embodiment of the present invention includes the following steps:
  • Step S101 Under the PCC architecture deployed by the SCEF, the SCEF performs an authorization decision on the overall subscription QoS of the third-party AS.
  • the SCEF may be Authorizes the overall contracted QoS of the third-party AS according to the overall contract information of the third-party AS and the QoS request of the third-party AS.
  • the overall subscription information of the third-party AS may be stored in the SCEF, including at least one of the following: an identifier of the third-party AS, a maximum bit rate (MBR) of the third-party AS, and the third-party AS.
  • MRR maximum bit rate
  • the pre-signed guaranteed bit rate (GBR) the number of the largest users (corresponding UEs) pre-signed by the third-party AS, the types and types of pre-signed services allowed by the third-party AS, and the QoS level of the third-party AS.
  • Information (such as processing latency or latency of third-party AS pre-contracted services, and processing priority).
  • Step S102 Send a QoS request to the PCRF, so that the PCRF performs an authorization decision on the QoS of the service requested by the UE (that is, the PCRF performs the policy and charging control of the IP-CAN session), and generates a policy and a charging control rule.
  • the QoS request may include at least one of service information requested by the UE, QoS information corresponding to the service requested by the UE, and overall QoS authorization decision information of the third-party AS.
  • step S101 if the SCEF performs the authorization decision unsuccessfully, the QoS request is not sent to the PCEF; if the authorization decision part is successful, the information about the success of the authorization decision part may be carried in the QoS request and sent to the PCRF to enable the PCEF to complete the authorization. Decision; if the authorization decision is successful, a QoS request is sent to the PCRF.
  • the embodiment of the present invention further describes a policy control method for a third-party application in the SCEF architecture.
  • the third-party application policy control method in the SCEF architecture described in the embodiment of the present invention includes the following steps:
  • Step S201 Under the PCC architecture deployed by the SCEF, the PCRF receives the QoS request sent by the SCEF from the third-party AS.
  • the SCEF can locally process the QoS request (to be converted to a format that the PCRF can recognize) and send a QoS request to the PCRF over the Rx interface.
  • the QoS request (which can be sent in the form of a Diameter AAR message) carries the information of the service requested by the UE and the QoS information corresponding to the service requested by the UE; and may also include IP filtering for the policy control service data flow (SDF).
  • SDF policy control service data flow
  • Application information such as information and application type, application bandwidth requirements, overall predefined QoS subscription information of third-party AS (that is, overall contract information of third-party AS), time period for requesting QoS, or traffic threshold, etc., for PCRF to make policy decisions For reference.
  • Step S202 Perform an authorization decision on the overall subscription QoS of the third-party AS according to the overall subscription information and the user subscription information of the third-party AS, and perform authorization decision on the QoS of the service requested by the UE (corresponding user) to generate a policy and charging. Control rules.
  • the overall subscription information of the third-party AS is stored in the SPR or predefined in the PCRF.
  • the overall subscription information of the third-party AS includes at least one of the following: an identifier of the third-party AS, an MBR pre-signed by the third-party AS, a GBR pre-signed by the third-party AS, and a pre-signature of the third-party AS.
  • the maximum number of users, the types and types of allowed services pre-signed by the third-party AS, and QoS level information (such as processing wait time or delay of pre-signed services, and processing priority).
  • the embodiment of the present invention further describes an SCEF.
  • the SCEF includes:
  • the first authorization decision unit 100 is configured to perform an authorization decision on the overall subscription quality of service QoS of the third-party AS;
  • the sending unit 200 is configured to send a QoS request to the PCRF, where the QoS request causes the PCRF to perform an authorization decision on the QoS of the service requested by the UE to generate a policy and a charging control rule.
  • the first authorization decision unit 100 and the sending unit 200 can be regarded as entities of different functions in the SCEF, and can be implemented by a server or a server cluster carrying the SCEF.
  • the SCEF further includes a first storage unit 300 (which may be implemented by a non-volatile storage medium such as a hard disk, a flash memory, etc.) configured to store the entirety of the third-party AS.
  • a first storage unit 300 (which may be implemented by a non-volatile storage medium such as a hard disk, a flash memory, etc.) configured to store the entirety of the third-party AS.
  • the overall contract information of the third-party AS includes at least one of the following:
  • the first authorization decision unit 200 is further configured to perform an authorization decision on the overall subscription QoS of the third-party AS according to the overall subscription information of the third-party AS and the QoS request of the third-party AS.
  • the embodiment of the present invention further describes a PCRF.
  • the PCRF includes:
  • the receiving unit 400 is configured to receive a QoS request from the third-party AS sent by the SCEF;
  • the second authorization decision unit 500 is configured to perform authorization decision on the overall subscription QoS of the third-party AS according to the overall subscription information and the user subscription information of the third-party AS, and perform authorization decision on the QoS of the UE requesting service, and generate Policy and charging control rules.
  • the PCRF further includes a second storage unit 600 (which may be implemented by a non-volatile storage medium such as a hard disk, a flash memory, etc.) configured to store the overall subscription information of the third-party AS.
  • a second storage unit 600 (which may be implemented by a non-volatile storage medium such as a hard disk, a flash memory, etc.) configured to store the overall subscription information of the third-party AS.
  • the embodiment of the invention further describes a computer storage medium, wherein the computer storage medium stores executable instructions, and the executable instructions are used to execute the policy control method of the third party application shown in FIG. 3 or FIG. 4 .
  • This example describes that in the SCEF deployment scenario shown in Figure 2, on the first side, the SCEF makes an authorization decision on the overall subscription QoS of the third-party AS.
  • the PCRF performs IP-CAN on the UE.
  • the session and the intra-session data service flow QoS perform authorization decision, that is, the application session establishment process that is hierarchically authorized on both sides of the first side and the second side.
  • the overall subscription information of the third-party AS is stored in the SCEF.
  • policy control under the SCEF architecture includes the following steps:
  • Step S301 The UE attaches to the network to establish an IP-CAN session.
  • a Gx session for policy and charging control is established between the PCEF and the PCRF. If the IP-CAN session involves BBERF, a policy is established between the BBERF and the PCRF. The controlled gateway controls the session.
  • Step S302 The UE interacts with the third-party AS to initiate service access.
  • Step S303 A specific interaction process is performed between the third party AS and the AF.
  • the third-party AS sends a service request to the AF, and carries the service requested by the user and the QoS corresponding to the service requested by the user.
  • the QoS can be in the form of Hypertext Transfer Protocol (HTTP) or Application Program Interface (API).
  • HTTP Hypertext Transfer Protocol
  • API Application Program Interface
  • the service request may also include the amount of QoS requested (eg, application bandwidth, time, or traffic).
  • the interface for sending a service request between the third-party AS and the AF is a non-standard interface.
  • the actual application does not limit the messages and functions of the interface.
  • Step S304 The AF sends a QoS request to the SCEF.
  • the QoS request may be sent in the form of an HTTP POST or an API message, where the QoS request carries the UE IP, the UE IP, the service information requested by the UE, and the QoS information corresponding to the service requested by the UE.
  • the AF sends a QoS request to the SCEF based on the SCEF-recognizable standardized interface, so it is possible to format the QoS request from the third-party AS, including filtering and filling the information in the QoS request.
  • the QoS request may further include an application identifier and a media stream description, and the QoS corresponding to the service requested by the UE
  • the information may include QoS level information such as service processing latency or latency, and processing priority information; preferably, the QoS information may include usage of the requested QoS (eg, application bandwidth, time, or traffic).
  • Step S305 The SCEF makes an authorization decision on the overall subscription QoS of the third-party AS.
  • the SCEF authorizes the overall subscription QoS of the third-party AS according to the overall subscription information of the locally stored third-party AS, that is, the pre-defined QoS subscription information of the third-party AS and the QoS request of the third-party AS. Decision; if the authorization is successful, the subsequent steps are performed, and if the authorization decision fails, the SCEF may notify the third party AS of the authorization failure message.
  • the overall subscription information of the third-party AS includes at least information such as service processing waiting time, delay, and processing priority.
  • the overall subscription information of the third-party AS may also be the QoS agreed upon by the third-party application provider and the operator. Level indication, the specific way of negotiating the agreement is implemented according to the implementation requirements and the operator's policy.
  • the overall contract information of the third-party AS is stored in the SCEF, including at least one of the following: the identifier of the third-party AS, the MBR pre-signed by the third-party AS, the GBR pre-signed by the third-party AS, and the maximum number of users pre-signed by the third-party AS.
  • the types and types of allowed services that are pre-signed by the three-party AS, and the QoS level information of the third-party AS (including the processing priority and processing delay of the pre-signed service, etc.).
  • the method can be implemented in the following manner, and the specific manner can be selected according to the operator policy of the actual network deployment.
  • the authorization decision for the overall contracted QoS of the third-party AS may be After the SCEF is powered on, the first interaction is completed, and the authorization decision of the overall contracted QoS of the third-party AS is updated according to the authorization period, so that the authorization decision of such parameters is repeatedly executed in each UE's service request processing.
  • the AF session of the UE for the first time with a third-party AS For subscription parameter authorization for a single (Per) UE rather than a specific service (for example, the maximum number of users allowed by a third-party AS, the allowed access user level, etc.), the AF session of the UE for the first time with a third-party AS During the establishment process, the authorization decision of the overall contracted QoS of the third-party AS is completed, and the authorization decision of the overall contracted QoS of the third-party AS is updated according to the authorization period, so as to avoid repeatedly performing such parameters in each UE's service request processing. Authorization decision.
  • the authorization policy for the overall contracted QoS of the third-party AS is completed during the session establishment process with the SCEF, and the overall contracted QoS authorization decision for the third-party AS is updated according to the authorization period, so as to avoid repeating in each UE's service request processing. Authorization decisions to perform such parameters.
  • Step S306 The SCEF sends a QoS request to the PCRF (for example, in the form of a Diameter AAR message), and the QoS request carries the service information requested by the UE and the QoS information corresponding to the service requested by the UE, and the overall QoS authorization decision information of the third-party AS.
  • the PCRF for example, in the form of a Diameter AAR message
  • the QoS request may also include application information such as Internet Protocol (IP) filtering information and application type for policy control to distinguish SDF, application bandwidth requirement, overall subscription information of the third-party AS, time period for requesting QoS, or traffic threshold.
  • application information such as Internet Protocol (IP) filtering information and application type for policy control to distinguish SDF, application bandwidth requirement, overall subscription information of the third-party AS, time period for requesting QoS, or traffic threshold.
  • IP Internet Protocol
  • Information such as the PCRF further authorization decision for reference.
  • Step S307 The PCRF returns an AAA confirmation message to the SCEF.
  • Step S308 The SCEF returns an acknowledgement message (such as an HTTP or API message) to the AF/AS.
  • an acknowledgement message such as an HTTP or API message
  • Step S309 The PCRF makes an authorization decision on the service requested by the UE based on the received QoS request.
  • the PCC rule is also generated for the service transmitted in the IP-CAN session request based on the requested QoS. If the BBERF exists, the PCRF also formulates the QoS rule according to the PCC rule. .
  • Step S310 The PCRF provides a QoS rule to the BBERF.
  • Step S311 The PCRF provides a PCC rule to the PCEF.
  • the PCEF After the PCEF installs and executes the policy, it returns a confirmation message to the PCRF.
  • Step S312 The PCRF sends a (RAR, Re-Auth-Request) message to the SCEF, and notifies the SCEF of the authorization decision result of the UE requesting the service QoS generated in step S309.
  • Step S313 The SCEF sends an API or HTTP PUT message to the AF, and informs the UE of the authorization decision result of the service QoS.
  • Step S314 The AF returns an acknowledgement message to the SCEF.
  • Step S315 The SCEF returns an acknowledgement message to the PCRF.
  • Step S316 The AF and the third party's specific message, for example, report the cumulative usage to the application server and other application related information.
  • the AF message received by the SCEF includes various types of information related to the sponsored data, such as a sponsored service indication, a sponsor identification, an application provider identifier, and the like, and may preferably include a relevant usage threshold, and the charging is performed. Information such as the main body of the tariff.
  • the message provided by the PCRF received by the SCEF will include the information related to the sponsored data and the optional service usage report.
  • the specific sponsored data service process can be implemented by referring to the related technical process, because the QoS authorization decision process described in this embodiment does not exist. Impact, no specific description here.
  • This example describes that in the SCEF deployment scenario, the SCEF forwards the QoS request of the third-party AS to the PCRF, and the PCRF uniformly completes the overall subscription QoS for the third party, the IP-CAN session of the UE, and The QoS of the data service flow in the session performs authorization decision to complete the process of establishing the application session; wherein the overall subscription information of the third-party AS is stored in the SPR or predefined in the PCRF.
  • Step S401 The UE attaches to the network to establish an IP-CAN session.
  • a Gx session for policy and charging control is established between the PCEF and the PCRF. If the IP-CAN session involves BBERF, a gateway control session for policy control is established between the BBERF and the PCRF.
  • Step S402 The UE interacts with the third-party AS to initiate service access.
  • Step S403 Perform a specific interaction process between the third party AS and the AF.
  • the third-party AS provides the UE with the service information requested by the UE and the QoS information corresponding to the requested service, and the third-party AS sends a request to the AF, where the request carries the information of the service requested by the UE and the QoS information corresponding to the requested service.
  • the request is sent in the form of HTTP or API; preferably, the request may also include usage bandwidth, time, and traffic for requesting QoS.
  • Step S404 The AF sends a QoS request (for example, an HTTP POST or an API message) to the SCEF, where the QoS request carries the UE IP, the UE ID, the information of the service requested by the UE, and the QoS information corresponding to the UE requesting the service.
  • a QoS request for example, an HTTP POST or an API message
  • the QoS request may further include an application identifier and a media stream description; the QoS information may include information such as service processing latency or delay, processing priority, and the like, and may also include usage, such as application bandwidth, time, and traffic requesting QoS.
  • Step S405 The SCEF performs local processing on the QoS request (to be converted into a format recognizable by the PCRF) and sends a QoS request to the PCRF through the Rx interface.
  • the QoS request (which can be sent in the form of a Diameter AAR message) carries the information of the service requested by the UE and the QoS information corresponding to the service requested by the UE; and may also include application information and applications such as IP filtering information and application type used for policy control to distinguish the SDF.
  • application information and applications such as IP filtering information and application type used for policy control to distinguish the SDF.
  • Bandwidth requirements, third-party AS The overall predefined QoS subscription information (that is, the overall subscription information of the third-party AS), the time period for requesting QoS, or the traffic threshold are used for reference by the PCRF for further policy decisions.
  • the SCEF may have a mapping function of the overall predefined QoS subscription information of the third-party AS.
  • the overall predefined QoS subscription information of the third-party AS includes at least QoS level information, such as service processing waiting time or delay, and processing priority. Level information; the overall predefined QoS subscription information of the third-party AS can also be mapped to the current Rx interface QoS parameters; or the mapped QoS level indication for the SCEF (such as carrier-defined or carrier and third-party protocol commitments) QoS level).
  • the specific mode is implemented according to the implementation requirements and the carrier policy.
  • Step S406 The PCRF returns an AAA confirmation message to the SCEF.
  • Step S407 The SCEF returns an acknowledgement message to the AF/AS (the acknowledgement message may be sent in the form of an HTTP or API message).
  • Step S408 At this time, if the PCRF has not interacted with the SPR, then the PCRF needs to interact with the SPR.
  • the PCRF determines, according to the UE identifier, that if there is no subscription information of the UE, the contract document request is sent to the SPR, and the UE identifier and the PDN identifier are carried in the subscription document request.
  • Step S409 The SPR returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier.
  • the overall subscription information of the third-party AS can be stored in the SPR, including the third-party AS identifier, the MBR pre-signed by the third-party AS, the GBR pre-signed by the third-party AS, the maximum number of users pre-signed by the third-party AS, and the pre-signed contract of the third-party AS. Allows the type and type of service, and the QoS level information of the pre-contracted service of the third-party AS (such as processing waiting time or delay, processing priority, etc.).
  • the SPR will provide the sponsored data connection document and the sponsor's overall contract information to the PCRF at this time.
  • the sponsored data connection document includes information such as a sponsored service indication, a sponsor identification, an application provider identifier, and the like; preferably includes a relevant usage threshold, a billing fee body, and the like.
  • Information; the items included in the overall contract information of the sponsor may refer to the overall contract information of the third party AS described above.
  • Step S410 After the PCRF successfully determines the overall subscription OoS authorization of the third-party AS, based on the received subscription information of the SPR, the information requested by the UE provided by the third-party AS transmitted by the SCEF, and the QoS information corresponding to the service requested by the UE, And the overall contract information of the third-party AS, combined with the network policy and the current network load status and the like, and the user subscription information, etc., the authorization decision of the QoS of the service requested by the UE.
  • the UE performs an authorization decision on the QoS of the IP-CAN session and the gateway control session, and generates a PCC rule for the service based on the QoS of the UE requesting the service; if the BBERF exists, the PCRF also formulates the QoS rule according to the PCC rule.
  • the overall subscription information of the third-party AS can be customized in the PCRF according to the carrier policy.
  • the specific content can include the third-party AS identifier.
  • the third-party AS pre-signed MBR and the third-party AS are pre- The number of the maximum number of users that have been contracted by the GBR, the third-party AS, the type and type of the service that is pre-signed by the third-party AS, and the QoS level information such as the processing priority and processing delay of the third-party AS pre-contracted service.
  • the authorization decision of the QoS of the service requested by the UE is performed, provided that the overall subscription QoS authorization of the third-party AS is successful; that is to say, in this step, the third-party AS overall subscription QoS is authorized.
  • the decision, as well as the OoS requesting the service from the UE, is authorized to make a two-level authorization.
  • Step S411 The PCRF provides a QoS rule to the BBERF.
  • Step S412 The PCRF provides a PCC rule to the PCEF. After the PCEF installs and executes the policy, it returns an acknowledgement message to the PCRF.
  • Step S413 The PCRF sends a RAR message to the SCEF, and notifies the SCEF of the UE requesting the service QoS authorization decision result.
  • Step S414 The SCEF sends an API or HTTP PUT message to the AF to inform the UE to request the industry. The result of the QoS authorization decision.
  • Step S415 The AF returns an acknowledgement message to the SCEF.
  • Step S416 The SCEF returns an acknowledgement message to the PCRF.
  • Step S416 The AF and the third party's specific message, for example, report the cumulative usage to the application server and other application related information.
  • the AF message received by the SCEF includes various types of information related to the sponsored data, such as a sponsored service indication, a sponsor identification, an application provider identifier, and the like, preferably including a relevant usage threshold, and a charging fee. Subject and other information.
  • the message provided by the PCRF received by the SCEF will contain information related to the sponsored data, as well as an optional service usage report.
  • the specific sponsored data service process can be implemented by referring to the related technical process, and the QoS authorization mode of the present invention is not necessarily affected, and the present invention is not specifically described.
  • the SCEF may include an application access control logic function, but the SCEF and the application access control function entity are not identical and included; for the content of the overall subscription information of the third-party AS, an example is enumerated, and the actual network deployment is performed. It can be extended and combined according to the carrier's policy.
  • the storage of the overall contract information of the three-party application can be deployed to the network element proposed in the above embodiment or deployed to other data centers or platforms of the carrier network.
  • the SCEF and the PCRF perform hierarchical authorization decisions.
  • the PCRF uniformly authorizes two scenarios.
  • the carrier can perform combined deployment according to the operation policy, and can simultaneously support two authorization modes, and enable the corresponding mode according to requirements. carried out.
  • the overall QoS authorization of the third-party AS and the QoS authorization of the AS service are implemented by the operator in a reasonable manner.
  • the network resources can be allocated more reasonably. Avoid the problem that the network traffic is too large or the number of users is too large, which causes the network load to be too large, which affects the use of other users or services (such as the carrier's own services for users who sign up for such services); Business is a third-party AS industry While providing services, it will not hinder the normal operation of the operators' own services, and avoid the related technologies.
  • the above architecture and the embodiment are directed to the PCC architecture of the SCEF deployment.
  • the method of the present invention can also be used for the overall QoS of the AS.
  • Authorization and authorization of QoS for users and services; when deploying for AAC, replacing the SCEF in the two embodiments with the AAC function can implement the main solution.
  • the detailed detailed process is adjusted according to the actual network deployment requirements and operational policies.
  • the steps may be performed by a program instruction related hardware, and the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes the steps of the foregoing method embodiment; and the foregoing storage medium includes: mobile storage A device that can store program code, such as a device, a random access memory (RAM), a read-only memory (ROM), a magnetic disk, or an optical disk.
  • program code such as a device, a random access memory (RAM), a read-only memory (ROM), a magnetic disk, or an optical disk.
  • the above-described integrated unit of the present invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product.
  • the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for making
  • a computer device (which may be a personal computer, server, or network device, etc.) performs all of the methods described in various embodiments of the present invention or section.
  • the foregoing storage medium includes various media that can store program codes, such as a mobile storage device, a RAM, a ROM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了第三方应用的策略控制方法、业务能力开放网络(SCEF)以及策略与计费规则功能实体(PCRF)、计算机存储介质；方法包括：SCEF对第三方应用服务器(AS)的整体签约服务质量(QoS)进行授权决策；发送QoS请求给PCRF，所述QoS请求用于使所述PCRF对用户终端(UE)请求的业务的QoS进行授权决策，生成策略和计费控制规则。

Description

第三方应用的策略控制方法、SCEF和PCRF 技术领域
本发明涉及通信技术，具体涉及一种第三方应用的策略控制方法、业务能力开放网络(Service Capability Exposure Framework，简称为SCEF)和策略与计费规则功能实体(Policy and Charging Rules Function，简称为PCRF)、计算机存储介质。
背景技术
第三代合作伙伴计划(3rd Generation Partnership Project，简称为3GPP)的策略和计费控制(Policy and Charging Control，简称为PCC)架构是一个能够应用于多种接入技术的功能框架。例如，应用于通用移动通信系统(Universal Mobile Telecommunications System，简称为UMTS)的陆上无线接入网(UMTS Terrestrial Radio Access Network，简称为UTRAN)、全球移动通信系统(Global system for Mobile Communication，简称为GSM)/GSM数据增强演进(Enhanced Data rates for Global Evolution，简称为EDGE)无线接入网、互通无线局域网(I-WLAN)以及演进的分组系统(Evolved Packet System，简称为EPS)等。
图1为相关技术的Rel-9PCC非漫游架构的示意图，以下参照图1对该PCC架构中的各个逻辑功能实体及其接口功能进行描述：
应用功能实体(Application Function，简称为AF)，提供业务应用的接入点，这些业务应用所使用的网络资源需要进行动态的策略控制。在业务面进行参数协商时，AF将相关业务信息传递给策略与计费规则功能实体(Policy and Charging Rules Function，简称为PCRF)，如果这些业务信息与PCRF的策略相一致，则PCRF接受该协商；否则，PCRF拒绝该协商，并 在反馈中同时给出PCRF可接受的业务参数。随后，AF可将这些参数返回给用户设备(User Equipment，简称为UE)。其中，AF和PCRF之间的接口是Rx接口。
PCRF是PCC的核心，负责策略决策和计费规则的制定。PCRF提供了基于业务数据流的网络控制规则，这些网络控制包括业务数据流的监测、门控(Gating Control)、服务质量(Quality of Service，简称为QoS)控制以及基于数据流的计费规则等。PCRF将其制定的策略和计费规则发送给策略与计费执行功能实体(Policy and Charging Enforcement Function，简称为PCEF)执行，同时，PCRF还需要保证这些规则和用户的签约信息一致。PCRF制定策略和计费规则的依据包括：从AF获取与业务相关的信息；从用户签约数据库(Subscription Profile Repository，简称为SPR)获取用户策略计费控制签约信息；从PCEF获取与承载相关网络的信息。
PCEF，用于在承载面执行PCRF所制定的策略和计费规则。PCEF按照PCRF所发送的规则中的业务数据流过滤器对业务数据流进行监测，进而对这些业务数据流执行PCRF所制定的策略和计费规则。在承载建立时，PCEF按照PCRF发送的规则进行QoS授权，并根据AF的执行进行门控控制。根据PCRF发送的计费规则，PCEF执行相应的业务数据流计费操作，计费既可以是在线计费，也可以是离线计费。如果是在线计费，则PCEF需要和在线计费系统(Online Charging System，简称为OCS)一起进行信用管理。离线计费时，PCEF和离线计费系统(Offline Charging System，简称为OFCS)之间交换相关计费信息。PCEF与PCRF之间的接口是Gx接口，与OCS之间的接口是Gy接口，与OFCS之间的接口是Gz接口。也可增强PCEF功能实现流检测功能(TDF，简称为Traffic Detection Function)。PCEF可以根据本地配置或是PCRF下发的包含应用检测控制策略(ADC，Application Detection and Control)的PCC规则进行应用检测并进行策略执 行(如门控、重定向和带宽限制)。PCEF通常位于网络的网关(Gate-Way，简称为GW)内，如GPRS中的GPRS网关支持节点(GGSN)以及I-WLAN中的分组数据网关(Packet Data Gateway，简称为PDG)。
TDF也可以独立部署，此时TDF与PCRF之间的接口是Sd接口，TDF可以根据预配置或PCRF下发的应用检测控制规则进行应用检测和策略执行。PCRF为独立TDF提供应用检测控制规则，独立TDF功能的策略控制执行操作包括门控、重定向和带宽限制。TDF向PCRF作被检测业务/流的相关事件和信息的上报，以及给PCRF发送业务数据流描述，传送来自PCRF的用于流检测的业务检测和策略规则的信令。TDF存在请求业务报告和主动业务报告两种模式：请求业务报告方式，PCRF将会通知TDF哪些业务需要检测并报告给PCRF；主动业务报告方式，在TDF中预配置哪些业务需要检测和报告，该方式假定用户同意不需请求并可执行。
承载绑定和事件报告功能实体(Bearer Binding and Event Reporting Function，简称为BBERF)，其功能包括承载绑定、上行承载绑定的验证、以及事件报告。当UE通过E-UTRAN接入，并且S-GW与P-GW之间采用PMIPv6协议时，BBERF就位于S-GW，当UE通过可信任非3GPP接入系统接入时，BBERF位于可信任非3GPP接入网关，当UE通过不可信任非3GPP接入系统接入时、BBERF位于演进的分组数据网关(Evolved Packet Data Gateway，简称为ePDG)。此时，PCEF不再执行承载绑定功能。
用户签约数据库(SPR)存储了和策略控制与计费相关的用户策略计费控制签约信息。SPR和PCRF之间的接口是Sp接口。
在线计费系统(OCS)，与PCEF一起进行在线计费方式下用户信用的控制和管理。
离线计费系统(OFCS)，与PCEF一起完成离线计费方式下的计费操作。
以上PCC架构通过各功能实体实现了对UE为访问一个分组数据网络 (Packet Data Network，简称为PDN)所建立的IP连接接入网(IP Connectivity Access Network，简称为IP-CAN)会话的策略计费控制。
随着移动互联网的发展，运营商需要与第三方应用提供商进行互通，为第三方应用提供商提供的业务进行QoS保障。由于目前PCC支持的Rx接口采用的Diameter协议，而对于大多数第三方应用提供商来说，他们更擅长基于SOAP、REST协议的开发。目前业界研究PCC架构支持基于SOAP/REST协议的Rx接口。在PCRF和AF直接设置一个称为协议转换器的逻辑功能，配置为将SOAP或REST协议转换成Diameter。可以在PC上面增加一些接入控制功能，以便能够更好的实现运营商对第三方应用的接入控制，此时该逻辑功能还称为应用接入控制功能(Application Access Control,简称AAC)。此外，除了对外部应用的接入控制，移动运营商提供增值业务等3GPP的业务功能给外部应用提供商和基于网络的API商业合作方，提供内外部应用和业务的可达和互通。与提供企业或商业方案和基于网络的业务和内容的更广范围的外部应用提供商之间，开展新的签约和合作关系。这称为业务能力开放网络(Service Capability Exposure Framework，简称为SCEF)。当前PCC架构中，SCEF可部署在PCRF和外部AF之间(如图2所示)。
相关技术中，PCRF根据SPR签约信息可以对UE的IP-CAN会话或服务数据流SDF进行QoS授权，生成相应的策略或和计费规则，下发给PCEF安装执行。当引入第三方应用服务器AS和SCEF，运营商网络除了根据用户(对应UE)的签约对业务进行相应的QoS授权，还需要能够对第三方AS接入3GPP系统的整体业务能力进行QoS授权和对第三方AS签约业务进行QoS授权。
目前如何解决SCEF架构下对第三方AS进行整体QoS授权、对第三方AS的签约业务进行QoS授权，尚没有相关技术方案。
发明内容
本发明实施例提供一种第三方应用的策略控制方法、SECF以及PCRF、计算机存储介质，能够实现SCEF架构下对第三方AS进行整体QoS授权，还能够实现对第三方AS的签约业务进行QoS授权。
本发明实施例的技术方案是这样实现的：
第一方面，本发明提供了一种第三方应用的策略控制方法，所述方法包括：
业务能力开放网络SCEF对第三方应用服务器AS的整体签约服务质量QoS进行授权决策；
发送QoS请求给策略与计费规则功能实体PCRF，所述QoS请求用于使所述PCRF对用户终端UE请求的业务的QoS进行授权决策以生成策略和计费控制规则。
较佳地，所述SCEF存储有所述第三方AS的整体签约信息，所述第三方AS的整体签约信息包括以下至少之一：
所述第三方AS的标识、所述第三方AS预先签约的最大比特率MBR、所述第三方AS预先签约的保证比特率GBR、所述第三方AS预先签约的最大用户数，所述第三方AS预先签约的允许业务种类和类型、所述第三方AS的QoS级别信息。
较佳地，所述SCEF对第三方AS的整体签约QoS进行授权决策，包括：
所述SCEF根据本地存储的第三方AS的整体签约信息、以及所述第三方AS的QoS请求，对所述第三方AS的整体签约QoS进行授权决策。
较佳地，所述QoS请求包括UE请求的业务信息、所述UE请求的业务对应的QoS信息、以及对所述第三方AS的整体QoS授权决策信息。
第二方面，本发明提供了一种第三方应用的策略控制方法，所述方法 包括：
策略与计费规则功能实体PCRF收到业务能力开放网络SCEF发送的来自于第三方AS的QoS请求；
根据所述第三方应用服务器AS的整体签约信息、用户签约信息，对所述第三方AS的整体签约QoS进行授权决策，并对UE请求业务的QoS进行授权决策，生成策略和计费控制规则。
较佳地，所述第三方AS的整体签约信息存储于用户签约数据库SPR中，或预定义在所述PCRF中。
较佳地，所述第三方AS的整体签约信息包括以下至少之一：所述第三方AS的标识、所述第三方AS预先签约的MBR、所述第三方AS预先签约的GBR、所述第三方AS预先签约的最大用户数、所述第三方AS预先签约的允许业务种类和类型、QoS级别信息。
较佳地，所述QoS请求中携带UE请求的业务的信息、所述UE请求的业务对应的QoS信息。
较佳地，所述QoS请求中携带用于策略控制区分服务数据流SDF的IP过滤信息和应用类型信息、应用带宽需求、所述第三方AS的整体签约信息、请求QoS的时间周期或流量阈值信息。
第三方面，本发明提供了一种业务能力开放网络SCEF，所述SCEF包括：
第一授权决策单元，配置为对第三方应用服务器AS的整体签约服务质量QoS进行授权决策；
发送单元，配置为发送QoS请求给策略与计费规则功能实体PCRF，所述QoS请求配置为使所述PCRF对用户终端UE请求的业务的QoS进行授权决策以生成策略和计费控制规则。
较佳地，所述SCEF还包括第一存储单元，配置为存储所述第三方AS 的整体签约信息，所述第三方AS的整体签约信息包括以下至少之一：
所述第三方AS的标识、所述第三方AS预先签约的最大比特率MBR、所述第三方AS预先签约的保证比特率GBR、所述第三方AS预先签约的最大用户数，所述第三方AS预先签约的允许业务种类和类型、所述第三方AS的QoS级别信息。
较佳地，所述第一授权决策单元还配置为根据第三方AS的整体签约信息、以及所述第三方AS的QoS请求，对所述第三方AS的整体签约QoS进行授权决策。
第四方面，本发明提供了一种策略与计费规则功能实体PCRF，所述PCRF包括：
接收单元，配置为接收到业务能力开放网络SCEF发送的来自于第三方应用服务器AS的QoS请求；
第二授权决策单元，配置为根据所述第三方AS的整体签约信息、用户签约信息，对所述第三方AS的整体签约QoS进行授权决策，并对UE请求业务的QoS进行授权决策，生成策略和计费控制规则。
较佳地，
所述PCRF还包括第二存储单元，配置为存储所述第三方AS的整体签约信息。
第五方面，本发明实施例提供一种计算机存储介质，所述计算机存储介质中存储有可执行指令，所述可执行指令配置为执行上述的任意一种第三方应用的策略控制方法。
本发明实施例中，由SCEF和PCRF进行分级授权决策，或由PCRF统一进行授权决策，实现运营商对第三方AS的整体QoS授权和第三方AS业务的QoS授权，除了保证SCEF架构下第三方AS业务的正常运行，还能使网络资源得到更合理的分配，避免网络中由于第三方AS业务流量过大 或用户数过多，导致网络负荷过大，而影响其它用户或业务(例如签约该类业务的用户的运营商自有业务)的使用的问题。
附图说明
图1为根据相关技术的Rel-9PCC非漫游架构的示意图；
图2为具有SCEF部署的PCC非漫游架构的示意图；
图3为本发明实施例中SCEF架构下的策略控制的实现流程示意图一；
图4为本发明实施例中SCEF架构下的策略控制的实现流程示意图二；
图5a、图5b为本发明实施例中SCEF的功能结构示意图；
图6a、图6b为本发明实施例中PCRF的功能结构示意图；
图7为根据本发明实施例中SCEF和PCR分别分级授权的第三方AS会话建立流程示意图；
图8为根据本发明实施例中PCRF统一授权决策的第三方AS会话建立流程示意图。
具体实施方式
为了使本发明的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本发明进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
本发明实施例提供一种SCEF架构下的策略控制方法，能够实现对第三方AS业务实行全局策略控制。
如图3所示，本发明实施例记载的SCEF架构下的第三方应用的策略控制方法包括以下步骤：
步骤S101，在SCEF部署的PCC架构下，SCEF对第三方AS的整体签约QoS进行授权决策。
SCEF部署的PCC架构参见图1和图2，在步骤S101中，SCEF可以 根据第三方AS的整体签约信息和第三方AS的QoS请求，对第三方AS的整体签约QoS进行授权决策。
第三方AS的整体签约信息可以存储于SCEF，包括以下至少之一：所述第三方AS的标识、所述第三方AS预先签约的最大比特率(MBR，Maximum Bit Rate)、所述第三方AS预先签约的保证比特率(GBR，Guaranteed Bit Rate)、所述第三方AS预先签约的最大用户(对应UE)数，所述第三方AS预先签约的允许业务种类和类型、第三方AS的QoS级别信息(例如第三方AS预先签约业务的处理等待时间或时延、以及处理优先级)。
步骤S102，发送QoS请求给PCRF，使PCRF对UE请求的业务的QoS进行授权决策(也就是使PCRF执行IP-CAN会话的策略和计费控制)，生成策略和计费控制规则。
所述QoS请求可以包括UE请求的业务信息、所述UE请求的业务对应的QoS信息，以及第三方AS的整体QoS授权决策信息中的至少之一。
在步骤S101中，如果SCEF执行授权决策不成功，就不会发送QoS请求给PCEF；如果授权决策部分成功，关于授权决策部分成功的信息可以携带在QoS请求中发送给PCRF，以使PCEF完成授权决策；如果授权决策成功，则会发送QoS请求至PCRF。
本发明实施例还记载一种SCEF架构下的第三方应用的策略控制方法，如图4所示，本发明实施例记载的SCEF架构下的第三方应用的策略控制方法包括以下步骤：
步骤S201，SCEF部署的PCC架构下，PCRF接收SCEF发送的来自于第三方AS的QoS请求。
SCEF可以对QoS请求进行本地处理(以转换为PCRF可以识别的格式)并通过Rx接口向PCRF发送QoS请求。
QoS请求(可以Diameter AAR消息的形式发送)中携带UE请求的业务的信息、UE请求的业务对应的QoS信息；还可包含用于策略控制区分服务数据流(SDF，Service Data Flow)的IP过滤信息和应用类型等应用信息、应用带宽需求、第三方AS的整体预定义QoS签约信息(也即第三方AS的整体签约信息)、请求QoS的时间周期或流量阈值等信息，供PCRF进行策略决策做参考。
步骤S202，根据第三方AS的整体签约信息和用户签约信息，对所述第三方AS的整体签约QoS进行授权决策，并对UE(对应用户)请求业务的QoS进行授权决策，生成策略和计费控制规则。
其中，第三方AS的整体签约信息存储于SPR或预定义在PCRF中。
其中，第三方AS的整体签约信息包括以下至少之一：所述第三方AS的标识、所述第三方AS预先签约的MBR、所述第三方AS预先签约的GBR、所述第三方AS预先签约的最大用户数、所述第三方AS预先签约的允许业务种类和类型、QoS级别信息(例如预先签约业务的处理等待时间或时延、以及处理优先级)。
本发明实施例还记载一种SCEF，如图5a所示，所述SCEF包括：
第一授权决策单元100，配置为对第三方AS的整体签约服务质量QoS进行授权决策；
发送单元200，用于配置为发送QoS请求给PCRF，所述QoS请求使所述PCRF对UE请求的业务的QoS进行授权决策以生成策略和计费控制规则。
第一授权决策单元100、发送单元200均可视为SCEF中的不同功能的实体，具体可以由承载SCEF的服务器或服务器集群承载实现。
其中，如图5b所示，所述SCEF还包括第一存储单元300(可以由非易失性存储介质如硬盘、闪存等实现)，配置为存储所述第三方AS的整体 签约信息，所述第三方AS的整体签约信息包括以下至少之一：
所述第三方AS的标识、所述第三方AS预先签约的MBR、所述第三方AS预先签约的GBR、所述第三方AS预先签约的最大用户数，所述第三方AS预先签约的允许业务种类和类型、所述第三方AS的QoS级别信息。
其中，所述第一授权决策单元200还配置为根据第三方AS的整体签约信息、以及所述第三方AS的QoS请求，对所述第三方AS的整体签约QoS进行授权决策。
本发明实施例还记载一种PCRF，如图6a所示，所述PCRF包括：
接收单元400，配置为接收SCEF发送的来自于第三方AS的QoS请求；
第二授权决策单元500，配置为根据所述第三方AS的整体签约信息、用户签约信息，对所述第三方AS的整体签约QoS进行授权决策，并对UE请求业务的QoS进行授权决策，生成策略和计费控制规则。
其中，如图6b所示，所述PCRF还包括第二存储单元600(可以由非易失性存储介质如硬盘、闪存等实现)，配置为存储所述第三方AS的整体签约信息。
本发明实施例还记载一种计算机存储介质，所述计算机存储介质中存储有可执行指令，所述可执行指令用于执行图3或图4所示的第三方应用的策略控制方法。
下面结合具体示例对本发明实施例记载的第三方应用的策略控制方法进行说明。
示例一
本示例描述了在图2所示的SCEF部署场景下，在第一侧，SCEF对第三方AS的整体签约QoS进行授权决策，在第二侧，PCRF对UE的IP-CAN 会话及会话内数据业务流QoS进行授权决策，也即在第一侧、第二侧两侧分级授权的应用会话建立流程。本实施例中，第三方AS的整体签约信息存储在SCEF。
如图7所示，SCEF架构下的策略控制包括以下步骤：
步骤S301：UE附着到网络，建立IP-CAN会话。
在UE附着到网络，建立IP-CAN会话的过程中，PCEF与PCRF之间建立用于策略和计费控制的Gx会话，若IP-CAN会话涉及BBERF，则BBERF与PCRF之间建立用于策略控制的网关控制会话。
步骤S302：UE与第三方AS交互，发起业务访问。
步骤S303：第三方AS与AF之间执行特定的交互流程。
第三方AS发送业务请求给AF，携带用户请求的业务、用户请求的业务对应的QoS，可以采用超文本传输协议(HTTP，Hyper Text Transfer Protocol)或应用程序接口(API，Application Program Interface)的形式发送业务请求，业务请求中还可以包含请求QoS的用量(例如应用带宽、时间或流量)。
第三方AS和AF之间的发送业务请求的接口为非标准接口，实际应用中对该接口的消息和功能不做限定。
步骤S304：AF向SCEF发送QoS请求。
例如可以采用HTTP POST或API消息的形式发送QoS请求，QoS请求中携带UE IP、UE IP、UE请求的业务信息、UE请求的业务对应的QoS信息。
AF是基于SCEF可识别的标准化接口向SCEF发送QoS请求，因此可能对来自第三方AS的QoS请求进行格式转换，包括对QoS请求中的信息进行筛选和填充。
QoS请求还可包括应用标识和媒体流描述，UE请求的业务对应的QoS 信息可包含QoS级别信息，如业务处理等待时间或时延、以及处理优先级等信息；优选地，QoS信息可包含请求QoS的用量(如应用带宽、时间或流量)。
步骤S305：SCEF对第三方AS的整体签约QoS进行授权决策。
SCEF根据本地存储的第三方AS的整体签约信息，也即第三方AS的整体预定义QoS(pre-defined QoS)签约信息、以及第三方AS的QoS请求，对第三方AS的整体签约QoS进行授权决策；如果授权成功，则执行后续步骤，如果授权决策失败，SCEF可以将授权失败消息通知第三方AS。
如前所述，第三方AS的整体签约信息至少包括业务处理等待时间、时延、以及处理优先级等信息；第三方AS的整体签约信息也可以是第三方应用商和运营商协商约定的QoS级别指示，协商约定的具体方式根据实现需要和运营商策略执行。
第三方AS的整体签约信息存储于SCEF，包括以下至少之一：第三方AS的标识，第三方AS预先签约的MBR、第三方AS预先签约的GBR、第三方AS预先签约的最大用户数，第三方AS预先签约的允许业务种类和类型，以及第三方AS的QoS级别信息(包括预先签约业务的处理优先级和处理时延等)。
优选地，在实际部署网络执行时，SCEF进行针对第三方AS的整体签约QoS的授权决策时，可以通过以下的方式实现，具体使用何种方式可以根据实际网络部署的运营商策略选择。
1)对于静态的涉及第三方AS网元、用户数和带宽用量等与动态信息无关的参数授权(例如第三方AS是否签约可接入等)，对第三方AS的整体签约QoS的授权决策可在SCEF上电后的第一次交互完成，并根据授权周期更新对第三方AS的整体签约QoS的授权决策，避免在每次UE的业务请求处理中重复执行这类参数的授权决策。
2)对于针对单个(Per)UE而非具体业务的签约参数授权(例如第三方AS允许的最大用户数，允许的接入用户级别等)，可在UE第一次和第三方AS的AF会话建立过程中完成对第三方AS的整体签约QoS的授权决策，并根据授权周期进行更新对第三方AS的整体签约QoS的授权决策，避免在每次UE的业务请求处理中重复执行这类参数的授权决策。
3)针对第三方AS的具体业务的授权决策，而非针对UE请求的业务相关的签约参数授权决策，例如该第三方AS签约的允许业务类型和业务优先级等时，可在第三方AS第一次和SCEF的会话建立过程中完成对第三方AS的整体签约QoS的授权决策，并根据授权周期进行更新对第三方AS的整体签约QoS授权决策，避免在每次UE的业务请求处理中重复执行这类参数的授权决策。
步骤S306：SCEF向PCRF发送QoS请求(例如以Diameter AAR消息的形式发送)，QoS请求携带UE请求的业务信息和UE请求的业务对应的QoS信息，以及第三方AS的整体QoS授权决策信息。
QoS请求中还可包含用于策略控制区分SDF的网际协议(IP，Internet Protocol)过滤信息和应用类型等应用信息、应用带宽需求、第三方AS的整体签约信息、请求QoS的时间周期或流量阈值等信息，供PCRF进一步的授权决策做参考。
步骤S307：PCRF向SCEF返回AAA确认消息。
步骤S308：SCEF向AF/AS返回确认消息(例如HTTP或API消息)。
步骤S309：PCRF基于收到的QoS请求，对UE请求的业务进行授权决策。
SCEF传送的第三方AS提供的UE请求的业务信息、UE请求业务对应的QoS信息，以及第三方AS的整体QoS授权决策信息、并基于例如网络策略和当前网络的负荷状态信息、以及用户签约等信息，对UE请求的业务 的QoS进行授权决策。
对UE的IP-CAN会话和网关控制会话的QoS进行授权决策时，还基于请求的QoS为在IP-CAN会话请求传输的业务生成PCC规则，若BBERF存在，则PCRF还根据PCC规则制定QoS规则。
步骤S310：PCRF向BBERF提供QoS规则。
步骤S311：PCRF向PCEF提供PCC规则。
PCEF安装并执行策略后，向PCRF返回确认消息。
步骤S312：PCRF向SCEF发送(RAR，Re-Auth-Request)消息，将步骤S309生成的UE请求业务QoS的授权决策结果通知给SCEF。
步骤S313：SCEF向AF发送API或HTTP PUT消息，告知UE请求业务QoS的授权决策结果。
步骤S314：AF向SCEF返回确认消息。
步骤S315：SCEF向PCRF返回确认消息。
步骤S316：AF与第三方的特定消息，譬如向累计用量上报给应用服务器等应用相关信息上报。
本示例适用于常规第三方业务，以及第三方赞助数据业务。当为第三方赞助数据业务时，SCEF接收的AF消息中包含赞助数据相关的各类信息，例如赞助业务指示，赞助商标识，应用提供商标识等信息，优选地可以包含相关用量阈值，计费资费主体等信息。SCEF接收的PCRF提供的消息中，将会包含赞助数据相关的信息，以及可选的业务用量报告，具体的赞助数据业务流程可参照相关技术流程实现，因对本实施例记载的QoS授权决策流程没有影响，这里不做具体描述。
示例二
本示例描述了在SCEF部署场景下，SCEF转发第三方AS的QoS请求给PCRF，PCRF统一完成对第三方的整体签约QoS、UE的IP-CAN会话及 会话内数据业务流的QoS进行授权决策，以完成应用会话建立的流程；其中，第三方AS的整体签约信息存储在SPR中或预定义在PCRF本地。
如图8所示，包括以下步骤：
步骤S401：UE附着到网络，建立IP-CAN会话。
在这个过程中，PCEF与PCRF之间建立用于策略和计费控制的Gx会话。若IP-CAN会话涉及BBERF，则BBERF与PCRF之间建立用于策略控制的网关控制会话。
步骤S402：UE与第三方AS交互，发起业务访问。
步骤S403：第三方AS与AF之间执行特定的交互流程。
第三方AS向AF提供UE请求的业务信息，以及请求的业务对应的QoS信息，第三方AS发送一个请求给AF，该请求携带UE请求的业务的信息，以及请求的业务对应的QoS信息，可以采用HTTP或API的形式发送该请求；优选地，该请求中还可以包含请求QoS的应用带宽、时间和流量等用量。
步骤S404：AF向SCEF发送QoS请求(例如HTTP POST或API消息)，QoS请求中携带UE IP、UE ID、UE请求的业务的信息、以及UE请求业务对应的QoS信息。
QoS请求还可包括应用标识和媒体流描述；QoS信息可包含业务处理等待时间或时延，处理优先级等信息，优选地还可以包含用量，如请求QoS的应用带宽、时间和流量等。
步骤S405：SCEF对QoS请求进行本地处理(以转换为PCRF可以识别的格式)并通过Rx接口向PCRF发送QoS请求。
QoS请求(可以Diameter AAR消息的形式发送)中携带UE请求的业务的信息、UE请求的业务对应的QoS信息；还可包含用于策略控制区分SDF的IP过滤信息和应用类型等应用信息、应用带宽需求、第三方AS的 整体预定义QoS签约信息(也即第三方AS的整体签约信息)、请求QoS的时间周期或流量阈值等信息，供PCRF进一步的策略决策做参考。
SCEF可以具备第三方AS的整体预定义QoS签约信息的映射功能，如前所述，第三方AS的整体预定义QoS签约信息至少包括QoS级别信息，如业务处理等待时间或时延、以及处理优先级信息；第三方AS的整体预定义QoS签约信息还可以映射为当前Rx接口QoS参数；或者为SCEF进行映射后的QoS级别指示(例如运营商自定义的或是运营商和第三方协议约定的QoS级别)，具体方式根据实现需要和运营商策略执行。
步骤S406：PCRF向SCEF返回AAA确认消息。
步骤S407：SCEF向AF/AS返回确认消息(确认消息可以HTTP或API消息的形式发送)。
步骤S408：此时若PCRF还未与SPR交互，那么此时PCRF需要与SPR进行交互。
PCRF根据UE标识判断出如果还没有该UE的签约信息，则向SPR发送签约文档请求，并在该签约文档请求中携带UE标识和PDN标识。
步骤S409：SPR根据用户标识和PDN标识返回用户签约信息(即，签约文档应答)。
第三方AS的整体签约信息可存储于SPR，包括第三方AS标识、第三方AS预先签约的MBR、第三方AS预先签约的GBR、第三方AS预先签约的最大用户数、第三方AS预先签约的允许业务种类和类型、以及第三方AS预先签约业务的QoS级别信息(如处理等待时间或时延、以及处理优先级等)。
若为赞助数据业务，则此时SPR会向PCRF提供赞助数据连接文档和赞助商的整体签约信息。赞助数据连接文档包括赞助业务指示、赞助商标识、应用提供商标识等信息；优选地包含相关用量阈值、计费资费主体等 信息；赞助商的整体签约信息包括的项目可参照以上记载的第三方AS的整体签约信息。
步骤S410：PCRF对第三方AS的整体签约OoS授权决策成功后，基于收到的SPR的签约信息，SCEF传送的第三方AS提供的UE请求的业务的信息、UE请求的业务相应的QoS信息，以及第三方AS的整体签约信息，结合网络策略和当前网络的负荷状态等信息、以及用户签约等信息，对UE请求的业务的QoS进行授权决策。
对UE进行IP-CAN会话和网关控制会话的QoS进行授权决策，并基于UE请求业务的QoS为该业务生成PCC规则；若BBERF存在，则PCRF还根据PCC规则制定QoS规则。
本示例中，第三方AS的整体签约信息除了存储在SPR中外，也可以根据运营商策略在PCRF本地自定义，具体内容可包括第三方AS标识，第三方AS预先签约的MBR、第三方AS预先签约的GBR、第三方AS预先签约的最大用户数、第三方AS预先签约的允许业务种类和类型、以及第三方AS预先签约业务的处理优先级和处理时延等QoS级别信息。
需要指出的是，对UE请求的业务的QoS进行授权决策，前提是对第三方AS的整体签约QoS授权成功；也即是说，本步骤中，实质上包含对第三方AS整体签约QoS进行授权决策、以及对UE请求业务的OoS进行授权决策两极授权。
步骤S411：PCRF向BBERF提供QoS规则。
步骤S412：PCRF向PCEF提供PCC规则，PCEF安装并执行策略后，向PCRF返回确认消息。
步骤S413：PCRF向SCEF发送RAR消息，将UE请求业务QoS授权决策结果通知给SCEF。
步骤S414：SCEF向AF发送API或HTTP PUT消息，告知UE请求业 务QoS授权决策结果。
步骤S415：AF向SCEF返回确认消息。
步骤S416：SCEF向PCRF返回确认消息。
步骤S416：AF与第三方的特定消息，譬如向累计用量上报给应用服务器等应用相关信息上报。
本示例适用于常规第三方业务，以及第三方赞助数据业务。当为第三方赞助数据业务时，SCEF接收的AF消息中包含赞助数据相关的各类信息，例如赞助业务指示，赞助商标识，应用提供商标识等信息，优选地包含相关用量阈值，计费资费主体等信息。SCEF接收的PCRF提供的消息中，将会包含赞助数据相关的信息，以及可选的业务用量报告。具体的赞助数据业务流程可参照相关技术流程实现，因对本发明的QoS授权方式没有必然影响，本发明不做具体描述。
本发明实施例中，SCEF可包括应用接入控制逻辑功能，但SCEF和应用接入控制功能实体并不等同和包含；对于第三方AS的整体签约信息的内容，做了举例列举，实际网络部署可根据运营商策略进行扩展和组合；对于三方应用AS整体签约信息的存储，可根据运营策略部署到上述实施例建议的网元，或部署到运营商网络的其它数据中心或平台中。
示例一中，SCEF和PCRF进行分级授权决策，示例二中，PCRF统一授权两种场景；实际应用中，运营商可根据运营策略进行组合部署，可同时支持两种授权模式，根据需求开启相应模式执行。
本发明实施例中，合理地实现运营商对第三方AS的整体QoS授权和AS业务的QoS授权，除了保证SCEF架构下第三方AS业务的正常运行，还能使网络资源得到更合理的分配，避免网络此时AS业务流量过大或用户数过多，导致网络负荷过大，而影响其它用户或业务(例如签约该类业务的用户的运营商自有业务)的使用的问题；同时使运营商在为第三方AS业 务提供服务的同时，不会妨碍运营商自身业务的正常运行，避免了相关技术中如果大量用户签约了第三方AS业务且在忙时大量发起该业务，根据目前的签约机制，运营商无法对该类业务执行总体的资源策略控制，网络性能会受到该类业务的总体占用资源或用户数的冲击影响而严重下降的问题。
以上架构和实施例，针对SCEF部署的PCC架构；实际网络部署中，当采用功能更简单的AAC作为第三方AS和PCRF之间的连接网元时，同样可采用本发明的方法进行AS整体QoS授权和用户及业务的QoS的授权；当为AAC部署时，将两个实施例中的SCEF替换为AAC功能可实现主体方案，具体详细流程根据实际网络部署需要以及运营策略进行调整实施。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：移动存储设备、随机存取存储器(RAM，Random Access Memory)、只读存储器(ROM，Read-Only Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
或者，本发明上述集成的单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或 部分。而前述的存储介质包括：移动存储设备、RAM、ROM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (16)

  1. 一种第三方应用的策略控制方法，所述方法包括：
    业务能力开放网络SCEF对第三方应用服务器AS的整体签约服务质量QoS进行授权决策；
    发送QoS请求给策略与计费规则功能实体PCRF，所述QoS请求用于使所述PCRF对用户终端UE请求的业务的QoS进行授权决策以生成策略和计费控制规则。
  2. 如权利要求1所述的方法，其中，
    所述SCEF存储有所述第三方AS的整体签约信息，所述第三方AS的整体签约信息包括以下至少之一：
    所述第三方AS的标识、所述第三方AS预先签约的最大比特率MBR、所述第三方AS预先签约的保证比特率GBR、所述第三方AS预先签约的最大用户数，所述第三方AS预先签约的允许业务种类和类型、所述第三方AS的QoS级别信息。
  3. 如权利要求1所述的方法，其中，所述SCEF对第三方AS的整体签约QoS进行授权决策，包括：
    所述SCEF根据本地存储的第三方AS的整体签约信息、以及所述第三方AS的QoS请求，对所述第三方AS的整体签约QoS进行授权决策。
  4. 如权利要求1至3任一项所述的方法，其中，所述QoS请求包括UE请求的业务信息、所述UE请求的业务对应的QoS信息、以及对所述第三方AS的整体QoS授权决策信息。
  5. 一种第三方应用的策略控制方法，所述方法包括：
    策略与计费规则功能实体PCRF收到业务能力开放网络SCEF发送的来自于第三方AS的QoS请求；
    根据所述第三方应用服务器AS的整体签约信息、用户签约信息，对所 述第三方AS的整体签约QoS进行授权决策，并对UE请求业务的QoS进行授权决策，生成策略和计费控制规则。
  6. 如权利要求5所述的方法，其中，
    所述第三方AS的整体签约信息存储于用户签约数据库SPR中，或预定义在所述PCRF中。
  7. 如权利要求5所述的方法，其中，
    所述第三方AS的整体签约信息包括以下至少之一：所述第三方AS的标识、所述第三方AS预先签约的MBR、所述第三方AS预先签约的GBR、所述第三方AS预先签约的最大用户数、所述第三方AS预先签约的允许业务种类和类型、QoS级别信息。
  8. 如权利要求5所述的方法，其中，
    所述QoS请求中携带UE请求的业务的信息、所述UE请求的业务对应的QoS信息。
  9. 如权利要求5至8任一项所述的方法，其中，
    所述QoS请求中携带用于策略控制区分服务数据流SDF的IP过滤信息和应用类型信息、应用带宽需求、所述第三方AS的整体签约信息、请求QoS的时间周期或流量阈值信息。
  10. 一种业务能力开放网络SCEF，所述SCEF包括：
    第一授权决策单元，配置为对第三方应用服务器AS的整体签约服务质量QoS进行授权决策；
    发送单元，配置为发送QoS请求给策略与计费规则功能实体PCRF，所述QoS请求用于使所述PCRF对用户终端UE请求的业务的QoS进行授权决策以生成策略和计费控制规则。
  11. 如权利要求10所述的SCEF，其中，
    所述SCEF还包括第一存储单元，配置为存储所述第三方AS的整体签 约信息，所述第三方AS的整体签约信息包括以下至少之一：
    所述第三方AS的标识、所述第三方AS预先签约的最大比特率MBR、所述第三方AS预先签约的保证比特率GBR、所述第三方AS预先签约的最大用户数，所述第三方AS预先签约的允许业务种类和类型、所述第三方AS的QoS级别信息。
  12. 如权利要求10或11所述的SCEF，其中，所述第一授权决策单元还配置为根据第三方AS的整体签约信息、以及所述第三方AS的QoS请求，对所述第三方AS的整体签约QoS进行授权决策。
  13. 一种策略与计费规则功能实体PCRF，所述PCRF包括：
    接收单元，配置为接收到业务能力开放网络SCEF发送的来自于第三方应用服务器AS的QoS请求；
    第二授权决策单元，配置为根据所述第三方AS的整体签约信息、用户签约信息，对所述第三方AS的整体签约QoS进行授权决策，并对UE请求业务的QoS进行授权决策，生成策略和计费控制规则。
  14. 如权利要求13所述的PCRF，其中，
    所述PCRF还包括第二存储单元，配置为存储所述第三方AS的整体签约信息。
  15. 一种计算机存储介质，所述计算机存储介质中存储有可执行指令，所述可执行指令用于执行权利要求1至4任一项所述的第三方应用的策略控制方法。
  16. 一种计算机存储介质，所述计算机存储介质中存储有可执行指令，所述可执行指令用于执行权利要求5至9任一项所述的第三方应用的策略控制方法。
PCT/CN2016/070084 2015-06-23 2016-01-04 第三方应用的策略控制方法、scef和pcrf WO2016206354A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510351035.4A CN106304195B (zh) 2015-06-23 2015-06-23 第三方应用的策略控制方法、scef和pcrf
CN201510351035.4 2015-06-23

Publications (1)

Publication Number Publication Date
WO2016206354A1 true WO2016206354A1 (zh) 2016-12-29

Family

ID=57584393

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/070084 WO2016206354A1 (zh) 2015-06-23 2016-01-04 第三方应用的策略控制方法、scef和pcrf

Country Status (2)

Country Link
CN (1) CN106304195B (zh)
WO (1) WO2016206354A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108476388A (zh) * 2015-12-31 2018-08-31 华为技术有限公司 处理数据包的方法及装置
CN113099402A (zh) * 2019-12-23 2021-07-09 中兴通讯股份有限公司 终端设备的网络接入方法、电子设备及存储介质
CN115103401A (zh) * 2022-08-25 2022-09-23 广州丰石科技有限公司 一种基于5g多量纲的网络流量配置方法、系统及装置
US11910455B1 (en) 2022-08-12 2024-02-20 Cisco Technology, Inc. Techniques to provide sponsored data for a user equipment in a mobile network environment

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106792923B (zh) * 2017-02-09 2019-12-17 华为软件技术有限公司 一种配置QoS策略的方法及装置
CN113015210B (zh) * 2019-12-19 2022-11-29 中国电信股份有限公司 服务质量管控方法和系统
CN114079581B (zh) * 2020-08-14 2023-08-01 中国移动通信集团浙江有限公司 基于pcc的服务处理方法、系统、计算设备及存储介质
CN112637968B (zh) * 2020-12-16 2023-03-14 中国联合网络通信集团有限公司 专有承载建立方法、pcc业务管理服务器和网络管理设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2053782A1 (en) * 2006-08-21 2009-04-29 Huawei Technologies Co., Ltd. A communication network system and method for providing a service broker function and a service broker device
CN101442428A (zh) * 2007-11-19 2009-05-27 华为技术有限公司 一种端到端QoS的申请方法、系统和设备
CN101729511A (zh) * 2008-10-23 2010-06-09 华为技术有限公司 一种通用业务架构下用户动态签约的方法、装置与系统
CN104581670A (zh) * 2013-10-15 2015-04-29 中兴通讯股份有限公司 应用接入控制方法及应用功能实体装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2053782A1 (en) * 2006-08-21 2009-04-29 Huawei Technologies Co., Ltd. A communication network system and method for providing a service broker function and a service broker device
CN101442428A (zh) * 2007-11-19 2009-05-27 华为技术有限公司 一种端到端QoS的申请方法、系统和设备
CN101729511A (zh) * 2008-10-23 2010-06-09 华为技术有限公司 一种通用业务架构下用户动态签约的方法、装置与系统
CN104581670A (zh) * 2013-10-15 2015-04-29 中兴通讯股份有限公司 应用接入控制方法及应用功能实体装置

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108476388A (zh) * 2015-12-31 2018-08-31 华为技术有限公司 处理数据包的方法及装置
US10581623B2 (en) 2015-12-31 2020-03-03 Huawei Technologies Co., Ltd. Data packet processing method and apparatus
CN108476388B (zh) * 2015-12-31 2020-08-07 华为技术有限公司 处理数据包的方法及装置
US11336472B2 (en) 2015-12-31 2022-05-17 Huawei Technologies Co., Ltd. Data packet processing method and apparatus
CN113099402A (zh) * 2019-12-23 2021-07-09 中兴通讯股份有限公司 终端设备的网络接入方法、电子设备及存储介质
US11910455B1 (en) 2022-08-12 2024-02-20 Cisco Technology, Inc. Techniques to provide sponsored data for a user equipment in a mobile network environment
CN115103401A (zh) * 2022-08-25 2022-09-23 广州丰石科技有限公司 一种基于5g多量纲的网络流量配置方法、系统及装置
CN115103401B (zh) * 2022-08-25 2022-12-06 广州丰石科技有限公司 一种基于5g多量纲的网络流量配置方法、系统及装置

Also Published As

Publication number Publication date
CN106304195A (zh) 2017-01-04
CN106304195B (zh) 2020-06-19

Similar Documents

Publication Publication Date Title
WO2016206354A1 (zh) 第三方应用的策略控制方法、scef和pcrf
US8750170B2 (en) Method and system for authorizing sessions using subscriber database
EP2493222B1 (en) Method and system for implementing usage monitoring control
EP2537312B1 (en) Facilitating a communication session
EP2702727B1 (en) Method and device for controlling qos and/or policy and charging control of a guest user
KR101414921B1 (ko) 가입자에 관련된 변경에 대한 응답에서 인터넷 프로토콜 연결 액세스 네트워크(ｉｐ-ｃａｎ) 가입자 세션의 관리
US9647848B2 (en) Application charging method, device, and system
US8661145B2 (en) Method and system for transmitting a bearer control mode in roaming scenarios
WO2012075875A1 (zh) 一种消费限制业务的签约和执行方法及系统
CN103460642A (zh) 用于控制通信网络中的服务业务的方法和设备
WO2009124441A1 (zh) 会话终结触发方法、实现方法及系统
CN103037449A (zh) 一种更新服务质量的方法及系统
WO2011085621A1 (zh) 业务处理方法及系统
WO2015143851A1 (zh) 用量监控方法、装置和系统
CN104581670A (zh) 应用接入控制方法及应用功能实体装置
WO2012083779A1 (zh) 策略控制方法及装置
WO2012071956A1 (zh) 漫游场景支持被赞助数据连接的方法、系统和装置
US9485105B2 (en) Method and telecommunications network utilizing more than one online charging system for a given user
US8442480B2 (en) Priority communications in a shared access telecommunications network
US9532205B2 (en) Method and system for identifying application detection and control function mode
WO2013178183A1 (zh) 服务质量的更新处理方法及装置
WO2011127666A1 (zh) 计费处理方法、计费处理装置和计费处理系统
WO2014110966A1 (zh) 一种业务数据的处理方法、装置和系统
WO2017128817A1 (zh) 第三方应用访问方法及装置
CN102123370B (zh) 一种对用户的访问进行重定向的系统及方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16813470

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16813470

Country of ref document: EP

Kind code of ref document: A1