WO2008116363A1 - Procédé et système et fonction pcrf pour traitement d'opérations - Google Patents

Procédé et système et fonction pcrf pour traitement d'opérations Download PDF

Info

Publication number
WO2008116363A1
WO2008116363A1 PCT/CN2007/003984 CN2007003984W WO2008116363A1 WO 2008116363 A1 WO2008116363 A1 WO 2008116363A1 CN 2007003984 W CN2007003984 W CN 2007003984W WO 2008116363 A1 WO2008116363 A1 WO 2008116363A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
priority
information
service
bearer priority
Prior art date
Application number
PCT/CN2007/003984
Other languages
English (en)
French (fr)
Inventor
Shibi Huang
Peng Zhao
Yuxin Mao
Shiyong Tan
Yan Li
Weihua Wei
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to ES07846018T priority Critical patent/ES2397285T3/es
Priority to EP07846018A priority patent/EP2093931B1/en
Priority to JP2009546630A priority patent/JP5189108B2/ja
Publication of WO2008116363A1 publication Critical patent/WO2008116363A1/zh
Priority to US12/564,558 priority patent/US8601125B2/en
Priority to US14/069,546 priority patent/US9438522B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system

Definitions

  • an existing service processing system includes: a Policy Control and Charging Rules Function (PCRF), which is used to limit the user access network, and an operator policy.
  • PCRF Policy Control and Charging Rules Function
  • the user subscription data (obtained from the SPR functional entity) and the service information currently being performed by the user (obtained from the AF functional entity) determine the policy and charging control (PCC) rules, and provide the PCC rules.
  • PCC policy and charging control
  • the PCC rule is executed by the PCEF, and the PCC rule includes a detection rule of the service data flow, whether the gate is controlled, a QoS corresponding to the service data flow, and a flow-based charging rule; and a policy and charging execution entity (Policy and Charging)
  • the Enforcement Function (PCEF) is configured to perform detection of the service data flow according to the PCC rule delivered by the PCRF, execute the policy (the policy includes the QoS policy), ensure the QoS of the service data flow, and perform functions such as flow-based charging.
  • the PCEF is set in the gateway; the subscription profile repository (Subscription Profile Repository, SP) R), for storing user subscription data; Application Function (AF), for dynamically providing business information of the service layer to the PCRF, and the PCRF dynamically generates or modifies the corresponding rule according to the information.
  • the subscription profile repository Subscribescription Profile Repository, SP
  • AF Application Function
  • IP-CAN IP access
  • the IP access session establishment process is as follows:
  • Step 201 After receiving the IP access session establishment request message initiated by the user terminal, the PCEF allocates an IP address visible in the PDN network, and establishes a first PDP context. 7 003984 Step 202: The PCEF creates a new Diameter Credit-Control (DCC) session, and sends a Credit-Control-Request (CCR) message to the PCRF to notify the PCRF to establish an IP access session.
  • the credit control request message includes a user terminal identifier and an IP address.
  • Step 203 The PCRF stores the user terminal identifier and the IP address of the credit control request message.
  • Step 204 If the user needs to sign the related information, the PCRF sends a user subscription information request message to the SPR.
  • Step 205 The SPR returns a user subscription response message, where the user subscription response message includes information such as a service, a charging mode, and the like currently signed by the user.
  • Step 206 The PCRF generates a new PCC rule.
  • Step 207 The PCRF stores the PCC rule.
  • Step 208 The PCRF returns the PCC rule to the PCEF through a CCA (Credit-Control-Answer) message.
  • CCA Clear-Control-Answer
  • Step 209 The PCEF installs the rule, and opens or closes the corresponding service data flow according to the rule to ensure the corresponding QoS.
  • Step 210 The PCEF returns an IP access session establishment response message to the user terminal.
  • the IP access bearer establishment process is as follows:
  • Step 301 After the AF receives a trigger event (for example, the multimedia call control signal initiated by the user terminal starts the AF session), the AF needs to establish a new Diameter session and provide service information to the PCRF.
  • a trigger event for example, the multimedia call control signal initiated by the user terminal starts the AF session
  • Step 302 The AF extracts the required service information (such as the address information of the IP stream, the port number, the media type, and the like) from the trigger event.
  • the required service information such as the address information of the IP stream, the port number, the media type, and the like
  • Step 303 The AF sends a Diameter AAR (AA-Request, Authentication Authorization Request) message to the PCRF, where the authentication authorization request message includes service information.
  • AA-Request Authentication Authorization Request
  • Step 304 The PCRF saves the received service information.
  • Step 305 If the PCRF does not have the user subscription information at this time, send a user subscription request message to the SPR to obtain the user subscription information.
  • Step 306 The SPR returns a user subscription response message to the PCRF, where the user subscription response message includes The business that the user is currently signing up.
  • Step 307 The PCRF associates the AF session to a corresponding IP access session according to the received service information and information from the PCEF (eg, an IP address of the IP access session, and the like).
  • Step 308 The PCRF returns an AAA (AA-Answer) message to the AF, and the AF sends an authentication authorization response message to the user terminal. After receiving the authentication authorization response message, the user terminal initiates an IP connection to the PCEF. Into the session message.
  • AAA AAA
  • AAA AAA
  • the user terminal After receiving the authentication authorization response message, the user terminal initiates an IP connection to the PCEF. Into the session message.
  • Step 309 The PCEF receives the IP access session message initiated by the user terminal, and requests to establish a new IP access bearer to establish a second PDP context.
  • Step 310 The PCEF sends a credit control request message to the PCRF to notify the PCRF to modify the IP access session and request a PCC rule for the IP access bearer.
  • Step 311 The PCRF stores the IP access bearer information in the credit control request message.
  • Step 312 The PCRF associates the IP access session with a specific AF session by using information and service information received from the PCEF (an IP access session may be associated with multiple AF sessions).
  • Step 313 The PCRF generates a new PCC rule according to information such as service information, user subscription information, and operator configuration.
  • Step 314 The PCRF saves the new PCC rule.
  • Step 315 The PCRF returns a credit control response message to the PCEF, and the credit control response message carries a new PCC rule.
  • Step 316 The PCEF installs the rule, and opens or closes the corresponding service data flow according to the rule to ensure the corresponding QoS.
  • Step 317 The PCEF returns an IP access session response message to the user terminal, and completes establishment of the IP access bearer.
  • the binding relationship between the IP access session, the IP access bearer, and the PCC rule as shown in FIG. 4 is actually formed on the PCEF.
  • the user terminal when the user terminal is assigned an addressable IP address, the user terminal establishes an IP access session.
  • the PCF rule that the PCRF passes to the PCEF through the Gx interface includes the service data flow.
  • QoS control parameters Bandwidth and QoS class identification.
  • IP access bearers with different QoS requirements can be established in the same IP access session. For example, services with higher QoS requirements (such as VOIP, multimedia call, etc.) can use IP-CAN Bearer 1.
  • IP-CAN Bearer 2 can be used for services with lower QoS requirements (such as file downloading, web browsing, etc.).
  • PCEF can be based on PCC rules (PCC rules include IP quintuple, ie, IP source address, IP destination address, The IP source port number, the IP destination port number, and the protocol) identify the IP flows and place the IP flows on different IP access bearers according to the QoS required by the PCC rules.
  • PCC rules include IP quintuple, ie, IP source address, IP destination address, The IP source port number, the IP destination port number, and the protocol
  • IP flows identify the IP flows and place the IP flows on different IP access bearers according to the QoS required by the PCC rules.
  • Each PCC rule can correspond to one or more IP flows (also known as traffic data flows).
  • the PCRF can determine the QoS level of the service data flow according to the policy context information (such as the priority of the application service, the priority of the user subscription, the customized QoS policy configured by the operator, etc.).
  • the QoS parameters such as the identifier and the bandwidth are then passed to the PCEF through the Gx interface to transmit the IP quintuple filter rule and the corresponding QoS parameter of the service data flow.
  • the PCEF can perform QoS control on the service data flow according to the QoS parameter of the service data flow.
  • the service data flows required by QoS provide different QoS guarantees.
  • the bearer layer has the same QoS requirements
  • the need for differentiated processing is required.
  • common voice service and emergency voice service their QoS requirements such as bandwidth, transmission delay, and packet loss rate are the same.
  • it is desirable to prioritize emergency voice services In the case where the QoS requirements of different users are the same, there are scenarios that are treated differently according to the type of the subscribed user.
  • the bearer transmission resources it is desirable to preferentially guarantee the bearer of the high priority user, such as the gold medal user.
  • the PCRF can only derive the QoS class identifier of the bearer layer and pass it to the PCEF for QoS control, which cannot meet the control requirements of the PCEF for the different bearers with the same QoS requirements.
  • ARP Allocation/Retention Priority
  • RAB Radio Access Bearer
  • the embodiments of the present invention provide a service processing method and system, a policy control, and a charging rule function entity, which are used to solve the problem that the service cannot be differentiated according to the policy context information in the prior art when the QoS requirements are the same.
  • An embodiment of the present invention provides a service processing method, including:
  • Bearer priority information includes: bearer priority information of the service data flow, bearer priority information of the IP access session, and/or an IP access bearer Carrying priority information;
  • the service is processed according to the bearer priority information.
  • the embodiment of the invention also discloses a service processing system, including:
  • a policy control and charging rule function entity configured to obtain, according to the obtained policy context information, the policy context information at least one of the following factors: a service type, a service priority, a user priority, and a custom priority;
  • the policy context information generates bearer priority information, and then sends the bearer priority information to the policy and charging execution entity;
  • the policy and charging execution entity is configured to process the service according to the bearer priority information.
  • the embodiment of the present invention further discloses a policy control and charging rule function entity, including: an obtaining unit, configured to obtain, according to the obtained policy context information, the policy context information includes at least one of the following factors: service type, service priority , user priority and custom priority;
  • a generating unit configured to generate bearer priority information according to the policy context information
  • a sending unit configured to send the bearer priority information to the policy and charging execution entity.
  • the embodiment of the invention also discloses a policy and charging execution entity, including: a receiving unit, configured to receive the bearer priority information processing service sent by the policy control and charging rule function entity;
  • the processing unit is configured to perform the bearer priority information processing service.
  • the embodiment of the present invention converts the policy context information into the bearer priority information, so that the PCEF processes the service according to the bearer priority information, so that when the QoS requirements are the same, different services are processed according to the policy context information.
  • BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 illustrates a prior art business processing system
  • FIG. 2 shows a prior art IP access session establishment process
  • FIG. 3 shows a prior art IP access bearer establishment process
  • FIG. 4 shows a binding relationship between an IP access session, an IP access bearer, a PCC rule, and an IP flow
  • FIG. 5 shows a service processing flow according to Embodiment 1 of the present invention
  • FIG. 6 shows a service processing procedure of Embodiment 2 of the present invention
  • FIG. 7 is a flowchart showing a service process according to Embodiment 3 of the present invention.
  • FIG. 8 is a flowchart showing a service process of Embodiment 4 of the present invention.
  • FIG. 9 is a diagram showing a policy control and charging rule function entity according to Embodiment 6 of the present invention.
  • FIG. 10 shows a policy and charging execution entity of Embodiment 7 of the present invention. DETAILED DESCRIPTION OF THE INVENTION
  • this embodiment provides a service processing method, including the following steps.
  • Step 501 PCRF > determines bearer priority information according to policy context information (such as service type, service priority, user priority, and/or operator-defined policy, etc.).
  • the bearer priority information includes a priority level and/or an IP access network bearer identifier.
  • Bearer priority information can be divided into the following categories: The bearer priority information of the data flow, the bearer priority information of the IP access session, and the bearer priority information of the IP access bearer.
  • the forwarding method of the bearer priority level is derived based on policy context information such as application service type, service priority, user priority, and operator's policy.
  • the bearer layer priority information may be derived only according to the emergency service type, for example, the bearer layer priority of the emergency service type is set to the highest; or the emergency service type may be combined with the voice, video service category, and the like, such as voice emergency service.
  • the bearer priority level is set to 15, and the bearer priority level of the video emergency service is set to 13; it can also be combined with the voice and video service categories according to the user priority, such as the priority of the gold user voice service is 10, the silver user voice
  • the bearer priority level of the service is 8, and the bearer priority level of the ordinary user voice service is 6.
  • the specific export rules can be flexibly defined according to the actual requirements in the application and according to various policy context information on the PCRF.
  • Step 502 The PCRF passes the bearer priority information to the PCEF through the Gx interface between the PCRF and the PCEF, and the PCEF may be set in the GW or set in other network elements.
  • a bearer priority cell can be added to the Diameter protocol: Bearer-Priority, so that the Bearer-Priority is directly set to the bearer priority message ( For example, in the re-authentication request message or the credit control response message, or set the Bearer-Priority in an existing cell (such as an authorized QoS cell: Authorized-QoS AVP, or a charging rule definition cell: Charging The -Rule-Defmition AVP is then sent to the PCEF through the bearer priority message.
  • the Bearer-Priority is used to indicate bearer priority information, and the format of Bearer-Priority: 3 ⁇ 4 port:
  • the AVP Header indicates the format definition of the bearer priority cell
  • XXXX indicates the code carrying the priority AVP
  • the Priority indicates the bearer priority level, which may be an integer within a certain range.
  • a certain range may be determined according to the number of bearer priority levels. For example, when the bearer priority is divided into 16 levels, any integer ranging from 0 to 15 may be taken as a bearer priority level, and the bearer priority level is carried. It may correspond to any integer from 0 to 15 (eg, 0 represents the lowest priority level, 15 represents the highest priority); Bearer-Identifier represents the identity of the IP access bearer.
  • the bearer priority information may be set in the bearer priority cell according to the type of bearer priority information, and then the bearer priority cell is set in a different message.
  • the bearer priority information is the bearer priority information of the service data flow
  • the bearer identifier sub-cell is set to be empty, and the bearer priority level of the service data flow is set in the bearer priority sub-cell, and the bearer is preferentially
  • the level information element is set in the charging rule definition information element, and the charging rule definition information element may be set in the credit control response message and/or the re-authentication request message;
  • the bearer priority information is IP
  • the bearer identifier sub-cell is set to be empty, the bearer priority level of the IP access session is set in the bearer identifier sub-cell, and the bearer priority cell is set in the In the credit control response message and/or the re-authentication request (RAR) message;
  • the bearer priority information is the bearer priority information of the IP bearer
  • the IP bearer identifier is set in the bearer identifier sub-cell Setting a bearer priority level of the IP bearer in the bearer identifier sub-cell
  • the bearer priority level is a priority level indicating the entire IP access session. If the bearer priority cell is placed in the charging rule definition cell, the bearer priority level is a priority level indicating the service data flow defined in the corresponding PCC rule. When the bearer priority cell contains a bearer identifier, the bearer priority level indicates the priority level of the IP access bearer specified by the bearer identifier.
  • Diameter protocol message (re-authentication request message, credit control response message) is described in detail below.
  • the PCRF may directly add the bearer priority cell to the re-authentication request message or the credit control response message, so as to be brought by the Diameter protocol.
  • the PCRF can be defined in the charging rule.
  • the PCRF can send bearer priority information to the PCEF through a Diameter protocol message (re-authentication request message and/or credit control response).
  • the bearer identifier indicates the identifier of the IP access bearer.
  • Bearer-Priority indicates the priority level of the service data flow defined in the corresponding PCC rule.
  • the bearer priority level is the priority level indicating the entire IP access session; if the QoS letter is authorized at this time.
  • the bearer bearer identifier (Bearer-Identifier), the bearer priority level is the priority of the IP access bearer corresponding to the bearer identifier.
  • Step 503 The PCEF performs corresponding processing on the service according to the bearer priority information delivered by the Gx interface, or maps to the allocation/holding priority of the IP access bearer, so as to process the service according to the ARP, so that the PCEF can be implemented.
  • the service processing is performed according to the policy context information, which ensures the support of the service priority of the entire network.
  • the process is as follows: The PCEF performs resource reservation according to the bearer priority, so that when the high-priority service and the low-priority service are concurrent, the high-priority service is preferentially guaranteed.
  • This embodiment describes an application example for deriving bearer priority information of a service data flow according to a service type of an application session.
  • the application function entity sends the service type indication to the PCRF according to the service type of the application session. It is assumed that the emergency service indication is sent to the PCRF, and the PCRF derives the bearer priority level of the service data flow according to the emergency service type indication, and sends the priority to the PCEF through the Gx interface.
  • the PCEF changes the original ARP priority level according to the bearer priority level of the service data flow, or creates an IP access bearer that meets the current bearer priority level for carrying the emergency service.
  • Step 601 After obtaining the service type information from the application session, the application function entity sends an authentication authorization request message to the PCRF, where the authentication authorization request message carries a service type and a service priority: Reservation-Priority. Reservation-Priority (from ⁇ 1 ⁇ high) defines ⁇ ! Under the mouth:
  • Step 602 After receiving the authentication authorization request message, the PCRF according to the service type (in this embodiment)
  • the service type is the emergency service.
  • the bearer priority information of the service data flow corresponding to the emergency service is exported.
  • the export rule refer to step 501 of the first embodiment, that is, the bearer priority level of the service data flow of the emergency service.
  • Step 603 The PCRF sets the bearer priority of the service data flow in the charging rule definition information cell, and then sets the charging rule definition information element in the re-authentication request message (for the setting method, refer to step 502 of the first embodiment), and A re-authentication request message will be sent to the PCEF with the bearer priority level of the PCC rules to be installed, the authorized QoS information, and the service data flow of the emergency service.
  • Step 604 The PCEF installs the PCC rule, executes the policy according to the PCC rule sent by the Gx interface, and creates an IP access bearer that meets the current bearer priority level for carrying the emergency service, or changes the original IP according to the bearer priority of the service data flow.
  • the priority level of the access bearer may be: mapping the bearer priority of the specific service data flow to the ARP priority level of the IP access bearer, and the mapping table may be as shown in the following table.
  • Step 605 The PCEF returns a re-authentication response message to the PCRF.
  • Step 606 The PCRF returns an authentication authorization response message to the application function entity.
  • Step 607 The PCEF initiates an IP access session modification or a QoS update operation, and the IP access bearer according to the mapped IP priority level is used to carry the emergency service.
  • the different service types correspond to different bearer priority levels
  • the emergency service corresponds to a higher bearer priority level
  • the normal service corresponds to a lower bearer priority level
  • the PCEF prioritizes the bearer priority when processing the service.
  • emergency services can be prioritized (such as allocating bearers, reserving resources, etc.), thus ensuring the priority operation of emergency services.
  • an application example of a bearer priority of an IP access bearer is derived according to a user subscription priority.
  • the PCRF obtains the subscription information from the SPR.
  • the subscription information defines the user priority.
  • the PCRF is forwarded to the bearer priority according to the user priority and sent to the PCEF for processing. The specific flow will be described below with reference to FIG.
  • Step 701 The user initiates an IP access session establishment request to the PCEF.
  • Step 702 The PCEF sends a credit control request message to the PCRF for requesting policy information.
  • Step 703 The PCRF obtains user information in the SPR, where the user information includes user priority information.
  • Step 704 The PCRF performs policy decision, for example, the bearer priority information is derived according to the user priority information (for the export rule, refer to step 501 of the first embodiment).
  • Step 705 The PCRF sends a credit control response message to the PCEF, where the message carries policy information.
  • the policy information includes PCC rules, authorized QoS information, and bearer priority information of the IP access bearer.
  • the allocation/holding priority of the IP access bearer (for the mapping method, refer to step 604 of the second embodiment).
  • Step 707 The PCEF sends an IP access session setup response message carrying the allocation/holding priority information to the user terminal.
  • different users have different bearer priority levels, and higher users are preferred.
  • the priority corresponds to a higher bearer priority level
  • the lower user priority corresponds to a lower bearer priority and the higher user priority is preferentially processed (such as allocating bearers, reserving resources, etc.), thereby ensuring a higher The priority operation of the user priority service.
  • This embodiment describes an application example of preferentially guaranteeing high-priority bearer resources in the case of PCEF resource conflicts. It is assumed that the application sessions of user 1 and user 2 apply for bearer resources to the PCEF of the bearer layer through the PCRF. The specific flow will be described below with reference to FIG.
  • Step 801 For the user 1, the establishment of the application function entity session triggers the application function entity to send an authentication authorization request message to the PCRF, where the message carries the service application information.
  • Step 802 For user 2, the establishment of the application function entity session triggers the application function entity to send an authentication authorization request message to the PCRF, where the message carries the service application information.
  • Step 803 The PCRF performs a policy decision, and the priority level of the bearer corresponding to the application service session of the user 1 and the user 2 is respectively derived according to the service application information and the user subscription information, and the bearer priority of the application service session of the exported user 2 is assumed to be prioritized.
  • the level is higher than the corresponding bearer priority level of User 1.
  • Step 804 The PCRF sends a re-authentication request message to the PCEF, where the message carries the PCC rule, the authorized QoS information, and the bearer priority information that the user 1 needs to install, modify, or delete.
  • Step 805 The PCRF also sends a re-authentication request message to the PCEF, where the message carries the PCC rule, the authorized QoS information, and the bearer priority information that the user 2 needs to install, modify, or delete.
  • Step 806 The PCEF performs policy execution according to the rules and bearer priority information delivered by the Gx interface.
  • the PCEF finds that the current bearer resource can only satisfy the user 1 or the user 2, but cannot satisfy the user 1 and the user 2 at the same time.
  • the bearer resource is allocated to the user 2 with the highest priority of the bearer.
  • the bearer resource of the user 2 is successfully allocated. For user 1, the allocation of bearer resources of user 1 fails due to insufficient resources.
  • Step 807 The PCEF returns a re-authentication response message to the PCRF, where the user 1 resource allocation fails.
  • Ai-self Step 808 The PCEF returns a re-authentication response message to the PCRF, and is used to successfully answer the user 2 re-authentication request message.
  • Step 809 The PCRF returns an authentication authorization response message to the application function entity, where the message 1 has a resource allocation failure information, which causes the application session on the application function entity to fail.
  • Step 810 The PCRF returns an authentication authorization response message to the application function entity, and is used to successfully respond to the user 2 authentication authorization request information.
  • Step 811 The PCEF initiates an update of the corresponding IP access session or an update operation of the QoS for the user 2.
  • Step 812 The high priority user 2 performs an application service.
  • the PCEF resource allocation can only allocate the bearer resource for the application session of one user. Because the user 2 has a higher priority, the PCEF allocates the bearer resource to the user 2, and the user 2 can successfully perform the application session. The user 2 does not allocate resources to the user 1 to cause the session to fail. This ensures that the session with the higher priority of the user has been set up preferentially, so that the PCEF can allocate the bearer resources according to the policy context information.
  • this embodiment discloses a service processing system, which includes: a policy control and charging rule function entity, which is used to obtain policy context information, where the policy context information includes at least one of the following factors: Type, service priority, user priority, and custom priority; and generating bearer priority information according to the policy context information, and then sending the bearer priority information to the policy and charging execution entity; a fee execution entity, configured to process a service according to the bearer priority information; an application function entity, configured to obtain a service type and a service priority, and send the service type and the service priority to the policy control and charging rule function entity;
  • the information base is configured to store user subscription data, and the user subscription data includes a user priority.
  • this embodiment discloses a policy control and charging rule function entity, including: an obtaining unit, configured to obtain policy context information, where the policy context information includes at least one of the following factors: Type, business priority, user priority, and custom priority; generating unit, used for Generating bearer priority information according to the policy context information, and sending, by the sending unit, the bearer priority information to the policy and charging execution entity.
  • an obtaining unit configured to obtain policy context information, where the policy context information includes at least one of the following factors: Type, business priority, user priority, and custom priority
  • generating unit used for Generating bearer priority information according to the policy context information, and sending, by the sending unit, the bearer priority information to the policy and charging execution entity.
  • this embodiment discloses a policy and charging execution entity, including: a receiving unit, configured to receive the bearer priority information processing service sent by a policy control and charging rule function entity; And configured to process a service according to the bearer priority information.
  • the PCRF determines the bearer layer service data flow, the IP access session, or the IP access according to the policy context information such as the application service type, the application service optimization level, the users of different priorities, or the operator-defined policy.
  • Bearer bearer priority information is sent to the PCEF through the Gx interface, so that the PCEF processes the service data flow or the specific user bearer according to the received service data flow or the bearer priority information carried by the specific user, or receives the received data.
  • the bearer priority information of a certain service data flow or a specific user is mapped to the ARP priority, so that the service priority is associated with the allocation/holding priority used by the access network, so that the access network can use the ARP to the service data flow or A specific user bearer is processed, so that a higher session of the service priority can be preferentially obtained, and a session with a lower service priority may be released. Therefore, the resource priority of the service priority in the access network is better ensured, and the support of the service priority of the entire network is ensured.

Description

业务处理方法和系统、 策略控制和计费规则功能实体
技术领域 本发明涉及一种通信技术， 尤其涉及一种业务处理方法和系统、 策略控制 和计费规则功能实体。 背景技术 如图 1所示， 现有的业务处理系统包括： 策略控制和计费规则功能实体 ( Policy Control and Charging Rules Function, PCRF ) ， 用于才艮据用户接入网络 的限制、 运营商策略、 用户签约数据（从 SPR功能实体获取）以及用户当前正在 进行的业务信息（从 AF功能实体获取）等决定业务策略和计费控制 （Policy and charging control, PCC )规则， 并将该 PCC规则提供给 PCEF, 由 PCEF执行 PCC 规则， 所述 PCC规则包括业务数据流的检测规则、是否门控、 业务数据流对应的 QoS和基于流的计费规则等； 策略和计费执行实体 （Policy and Charging Enforcement Function, PCEF ) , 用于根据 PCRF下发的 PCC规则执行业务数据流 的检测， 执行策略（所述策略包括 QoS策略）以保证业务数据流的 QoS, 以及执 行基于流的计费等功能， 所述 PCEF设置在网关中； 签约信息库 （Subscription Profile Repository, SPR ) , 用于存储用户签约数据； 应用功能实体（ Application Function, AF ) , 用于向 PCRF动态提供业务层的业务信息， PCRF根据该信息动 态生成或者修改对应的规则。
基于上述通信系统， 下面参照图 2和图 3分别描述 IP接入（IP-CAN )会话的 建立流程和 IP接入承载的建立流程。
如图 2所示， IP接入会话建立流程如下：
步骤 201、 PCEF接收到用户终端发起的 IP接入会话建立请求消息后， 分配一 个在 PDN网络可见的 IP地址， 并建立第一个 PDP上下文。 7 003984 步骤 202、 PCEF创建一个新的信用控制（Diameter Credit-Control, DCC )会 话， 向 PCRF发送信用控制请求（Credit-Control-Request, CCR )消息以通知 PCRF 进行 IP接入会话建立， 所述信用控制请求消息包括用户终端标识和 IP地址。
步骤 203、 PCRF存储信用控制请求消息的用户终端标识和 IP地址。
步骤 204、 PCRF如果需要用户签约相关信息， 则向 SPR发送用户签约信息请 求消息；
步骤 205、 SPR返回用户签约响应消息， 所述用户签约响应消息包括用户当 前签约的业务、 计费模式等信息。
步骤 206、 PCRF生成新的 PCC规则。
步骤 207、 PCRF存储 PCC规则。
步骤 208、 PCRF通过 CCA ( Credit-Control- Answer, 信用控制应答） 消息将 PCC规则返回给 PCEF。
步骤 209、 PCEF安装规则， 并根据规则打开或者关闭对应的业务数据流， 保 证相应的 QoS。
步骤 210、 PCEF向用户终端返回 IP接入会话建立响应消息。
如图 3所示， IP接入承载建立流程如下：
步骤 301、 AF接收到一个触发事件（如， 用户终端发起的多媒体呼叫控制信 令启动 AF会话）后， 需要建立一个新的 Diameter会话并向 PCRF提供业务信息。
步骤 302、 AF从触发事件中提取需要的业务信息（比如 IP流的地址信息， 端 口号， 媒体类型等） 。
步骤 303、 AF向 PCRF发送 Diameter AAR ( AA-Request, 鉴权授权请求） 消 息， 所述鉴权授权请求消息包含业务信息。
步骤 304、 PCRF保存接收到的业务信息。
步骤 305、 如果 PCRF此时没有用户签约信息， 则向 SPR发送用户签约请求消 息， 以获得用户签约信息。
步骤 306、 SPR向 PCRF返回用户签约响应消息， 所述用户签约响应消息包括 用户当前签约的业务。
步骤 307、 PCRF根据接收到的业务信息和来自 PCEF的信息（如， IP接入会 话的 IP地址等）将该 AF会话关联到一个对应的 IP接入会话。
步骤 308、 PCRF向 AF返回 AAA ( AA-Answer， 鉴权 4曼权应答） 消息， AF将 鉴权授权应答消息发给用户终端，用户终端接收到鉴权授权应答消息后，向 PCEF 发起 IP接入会话消息。
步骤 309、 PCEF接收到用户终端发起的 IP接入会话消息， 要求建立新的 IP接 入承载， 建立第二个 PDP上下文。
步骤 310、 PCEF向 PCRF发送信用控制请求消息， 以通知 PCRF修改 IP接入会 话， 并请求针对该 IP接入承载的 PCC规则。
步骤 311、 PCRF存储信用控制请求消息中的 IP接入承载信息。
步骤 312、 PCRF利用从 PCEF接收的信息和业务信息， 将 IP接入会话关联到 特定的 AF会话（一个 IP接入会话可与多个 AF会话有关联关系） 。
步骤 313、 PCRF根据业务信息、 用户签约信息、 运营商配置等信息生成新 的 PCC规则。
步骤 314、 PCRF保存新的 PCC规则。
步骤 315、 PCRF向 PCEF返回信用控制应答消息， 所述信用控制应答消息带 有新的 PCC规则。
步骤 316、 PCEF安装规则， 并根据规则打开或者关闭对应的业务数据流，保 证对应的 QoS。
步骤 317、 PCEF向用户终端返回 IP接入会话响应消息， 完成 IP接入承载的建 立。
通过以上 IP接入会话建立过程和 IP接入承载建立过程， 在 PCEF上实际形成 了如图 4所示的 IP接入会话、 IP接入承载、 PCC规则之间的绑定关系。 具体而言， 当用户终端被分配了可寻址的 IP地址后， 用户终端就建立了 IP接入会话。在建立 IP接入承载过程中， PCRF通过 Gx接口传递给 PCEF的 PCC规则中包括业务数据流 的 QoS控制参数： 带宽和 QoS等级标识。 为了满足不同的 QoS要求， 在同一个 IP 接入会话里可以建立不同 QoS要求的 IP接入承载， 比如对于 QoS要求较高的业务 (如 VOIP, 多媒体呼叫等）可以使用 IP-CAN Bearer 1， 对于 QoS要求较低业务 (比如文件下栽等， 网页浏览等）可以使用 IP- CAN Bearer 2。 在每个 IP接入承载 里可以有多个 IP流（比如用户可以同时在不同服务器下载文件） ， PCEF可根据 PCC规则 （PCC规则包含 IP五元组， 即， IP源地址、 IP目的地址、 IP源端口号、 IP目的端口号、 协议）来识别 IP流， 并根据 PCC规则要求的 QoS将 IP流置于不同 的 IP接入承载。 每个 PCC规则可以对应一到多个 IP流（也称为业务数据流） 。
在现有 PCC所提供的机制中， PCRF可以根据策略上下文信息 （如应用业务 的优先级， 用户签约的优先级， 运营商配置的自定义的 QoS策略等信息）来决定 业务数据流的 QoS等级标识和带宽等 QoS参数，然后通过 Gx接口把业务数据流的 IP五元组过滤规则和相应的 QoS参数传递给 PCEF, PCEF可以根据业务数据流的 QoS参数对业务数据流进行 QoS控制， 对不同 QoS需求的业务数据流分别提供不 同的 QoS保证。
在某些应用场景下，当承载层存在着在 QoS需求相同的情况下还需要进行区 别处理的需求。 如对于不同的语音业务： 普通语音业务和紧急语音业务， 它们 的带宽、传输时延、 丢包率等 QoS需求都是一样的， 但当承载传输资源存在冲突 的时候希望能够优先保证紧急语音业务；又如对于不同用户的 QoS需求相同的情 况下， 存在着根据签约的用户类型区别对待的场景， 当承载传输资源存在冲突 的时候希望能够优先保证高优先级用户， 如金牌用户的承载。 现有 PCC机制中， PCRF仅可以导出承载层的 QoS等级标识并传递到 PCEF进行 QoS控制， 无法满足 PCEF针对 QoS需求相同的承载根据不同情况进行区别处理的控制需求。
在现有技术中， 已有人提出了分配 /保持优先级 （ Allocation/Retention Priority, ARP ) 的概念， 所述分配优先级用于在用户建立无线接入承载（Radio Access Bearer, RAB )时根据优先级分配资源，保持优先级用于 UTRAN在业务建 立后根据优先级保留资源。然而， 分配 /保持优先级不能体现特定业务的优先级， 这样， 可能会出现： 较高优先级的业务因为分配 /保持优先级较低， 导致用户会 话的释放。 这就不能很好保证业务优先级在接入网的资源预留， 无法保证全网 对业务优先级的支持。
综上所述， 现有技术在 QoS需求相同的情况下， 没有综合考虑策略上下文信 息对业务处理的影响。 发明内容
本发明的实施例提供了一种业务处理方法和系统、 策略控制和计费规则功 能实体，用于解决现有技术中在 QoS需求相同的情况下无法根据策略上下文信息 进行区别处理业务的问题。
本发明的实施例提供了一种业务处理方法， 包括：
接收来自策略控制和计费规则功能实体的承载优先级信息， 所述承载优先 级信息包括： 业务数据流的承载优先级信息、 IP接入会话的承载优先级信息和 / 或 IP接入承载的承栽优先级信息；
根据承载优先级信息处理业务。
本发明实施例还公开了一种业务处理系统， 包括：
策略控制和计费规则功能实体， 用于根据获得策略上下文信息， 所述策略 上下文信息至少包括下述因素之一： 业务类型、 业务优先级、 用户优先级和自 定义优先级； 并根据所述策略上下文信息生成承载优先级信息， 然后将所述承 载优先级信息发给发给策略和计费执行实体；
策略和计费执行实体， 用于根据所述承载优先级信息处理业务。
本发明实施例还公开了一种策略控制和计费规则功能实体， 包括： 获得单元， 用于根据获得策略上下文信息， 所述策略上下文信息至少包括 下述因素之一： 业务类型、 业务优先级、 用户优先级和自定义优先级；
生成单元， 用于根据所述策略上下文信息生成承载优先级信息；
发送单元， 用于将所述承载优先级信息发给发给策略和计费执行实体。 本发明实施例还公开了一种策略和计费执行实体， 包括： 接收单元， 用于接收策略控制和计费规则功能实体发送的所述承载优先级 信息处理业务；
处理单元， 用于 居所述承载优先级信息处理业务。
本发明实施例通过将策略上下文信息转换为承载优先级信息， 使得 PCEF根 据承载优先级信息处理业务，从而实现了在 QoS需求相同的情况下，根据策略上 下文信息对不同的业务进^"区别处理。 附图说明 图 1示出了现有技术的业务处理系统；
图 2示出了现有技术的 IP接入会话建立流程；
图 3示出了现有技术的 IP接入承载建立流程；
图 4示出了 IP接入会话、 IP接入承载、 PCC规则和 IP流之间的绑定关系； 图 5示出了本发明实施例一的业务处理流程；
图 6示出了本发明实施例二的业务处理流程；
图 7示出了本发明实施例三的业务处理流程；
图 8示出了本发明实施例四的业务处理流程；
图 9示出了本发明实施例六的策略控制和计费规则功能实体；
图 10示出了本发明实施例七的策略和计费执行实体。 具体实施方式 为了便于本领域一般技术人员理解和实现本发明 , 现结合附图描绘本发明 的实施例。
实施例一
如图 5所示， 本实施例提供了一种业务处理方法， 包括如下步骤。
步骤 501、 PCRF >据策略上下文信息 （如业务类型、 业务优先级、 用户优 先级和 /或运营商自定义策略等）来决定承载优先级信息。 所述承载优先级信息 包括优先级级别和 /或 IP接入网承载标识。 承载优先级信息可分为如下几种： 业 务数据流的承载优先级信息、 IP接入会话的承载优先级信息和 IP接入承载的承载 优先级信息。
承载优先级级别的导出方法是， 根据应用业务类型、 业务优先级、 用户优 先级和运营商的策略等策略上下文信息导出。 如， 可以仅根据紧急业务类型导 出承载层优先级信息， 如把紧急业务类型的承载层优先级设置为最高； 也可以 根据紧急业务类型， 结合语音、 视频业务类别等信息导出， 如语音紧急业务的 承载优先级级别设置为 15 , 而视频紧急业务的承载优先级级别设置为 13; 还可 以根据用户优先级， 结合语音、 视频业务类别导出， 如金牌用户语音业务优先 级为 10, 银牌用户语音业务的承载优先级级别为 8, 而普通用户语音业务的承载 优先级级别为 6等等。 这里仅给出一些具体的承载优先级级别导出示例， 实际实 施中具体的导出规则可以根据应用中的实际需求， 并根据 PCRF上的各种策略上 下文信息进行灵活定义。
步骤 502、 PCRF通过其与 PCEF之间的 Gx接口把承栽优先级信息传递给 PCEF, 所述 PCEF可设置在 GW中， 或设置在其它网元中。
为了将承载优先级 ( Bearer-Priority )信息下发给 PCEF ,可以通过在 Diameter 协议中增加一个承载优先级信元： Bearer-Priority, 以便将所述 Bearer-Priority直 接设置在承栽优先级消息 （如， 重鉴权请求消息或信用控制应答消息） 中， 或 者将所述 Bearer-Priority设置在已有的信元 （如授权 QoS信元： Authorized-QoS AVP, 或计费规则定义信元： Charging-Rule-Defmition AVP ) 中， 然后通过所述 承载优先级消息下发给 PCEF。 所述 Bearer-Priority 用于表示承载优先级信息， Bearer-Priority的格式: ¾口下：
Bearer-Priority： := < A VP Header: xxxx>
[ priority ]
[ Bearer-Identifier ]
其中， AVP Header表示承载优先级信元的格式定义， XXXX表示承载优先 级 AVP 的代码； Priority表示承载优先级级别， 其可以是某一范围内的整数， 所 述某一范围可根据承载优先级级别的数目来确定， 例如， 当将承载优先级划分 为 16个级别时， 可取 0至 15范围内的任一整数作为一个承载优先级级别， 承载优 先级级别可与 0至 15中的任一整数——对应 （如， 0代表最低优先级别， 15代表 最高优先级） ； 承载标识（Bearer-Identifier )表示 IP接入承载的标识。
可根据承载优先级信息的种类将承载优先级信息设置在承载优先级信元， 然后将承载优先级信元设置在不同的消息中。
当承载优先级信息为业务数据流的承载优先级信息时， 将承载标识子信元 设置为空， 将业务数据流的承载优先级级别设置在承载优先级子信元中， 将所 述承载优先級信元设置在所述计费规则定义信元中， 所述计费规则定义信元可 设置在所述信用控制应答消息和 /或重鉴权请求消息中； 当承载优先级信息为 IP 接入会话的承载优先级信息时，将承载标识子信元设置为空，将 IP接入会话的承 载优先级级别设置在承载标识子信元中， 将所述承载优先级信元设置在所述信 用控制应答消息和 /或重鉴权请求（Re-Auth-Request, RAR ) 消息中； 当承载优 先级信息为 IP承载的承载优先级信息 ,将所述 IP承载标识设置在承载标识子信元 中，将 IP承载的承载优先级级别设置在所述承载标识子信元中，将所述承载优先 级信元设置在所述信用控制应答消息和 /或重鉴权请求消息中。
这样， 当承载优先级信元不包含承载标识时， 如果承载优先级信元放置在 重鉴权请求或信用控制应答消息中，则该承载优先级级别是表示整个 IP接入会话 的优先级级别； 如果承载优先级信元放置在计费规则定义信元中， 则该承载优 先级级别是表示相应 PCC规则中定义的业务数据流的优先级级别。当承载优先级 信元包含承载标识时，承载优先级级别表示承载标识指定的 IP接入承载的优先级 级别。
下面详细描述将承载优先级信元设置在 Diameter协议消息 （重鉴权请求消 息、 信用控制应答消息） 中的方法。
( a )、对于 IP接入会话的承载优先级信息， PCRF可以直接在重鉴权请求消 息或信用控制应答消息中增加承载优先级信元， 以便通过 Diameter协议带给 PCEFo
在重鉴权请求消息增加承载优先级信元的方式如下：
<RA-Requst> ： : = < Diameter Header: 258, REQf PXY >
< Session -工 d >
{ Auth-Applicati〇n-Id }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Destination-Host }
{ Re-Auth-Requst-Type }
[ Origin- St ate- Id ]
★ [ Event-Trigger ]
* [ Charging— Rule - Remove ]
* [ Charging— Rule— Install ]
[ Charging - Information ]
[ Authorized - QoS ]
[ Bearer - Priority ]
* [ Proxy一工 nf〇 ]
* [ Route-Record ]
* [ AVP] 在信用控制应答消息增加承载优先级信元的方式如下：
<CC-Answer> ： := < Diameter Header: 272, PXY >
< Session-Id >
{ Auth-Application—Id }
{ Origin-Host }
{ Origin-Realm }
[ Result-Code ]
[ Experimental -Re suit ]
{ CC-Requst-Type }
{ CC-Requst-Number }
★ [ Event-Trigger ]
[. Origin - State- Id ]
* t Charging - Rule - Remove ]
★ [ Charging - Rule— Install ]
[ Charging -工 nformation ]
[ Authorized— QoS ]
[Bearer-Priority ]
[ Error-Message ]
[ Error - Reporting - Host ]
* [ Failed - AVP ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
(b) 、 对于业务数据流的承载优先级信息， PCRF可以在计费规则定义
( Charging-Rule-Defmition AVP M言元中增加 载优先级信元，以便通过 Diameter 协议带给 PCEF。
在 Charging-Rule-Defmition AVP信元中增加承载优先级信元的方式如下：
Charging- Rule- Def init ion ：： = < AVP Header : 1003 >
Charging—Rule— Name }
Service- Identi f ier ]
Rating-Group ]
Flow- Description ]
Flow-Status ]
Authori zed— Q〇S ]
Reporting— Leve l ]
Onl ine ]
Of fline ]
Metering-Method ]
Precedence ]
AF-Charging- Identi f ier ]
Bearer-Priority ]
Flows ]
AVP ] 这样， PCRF可通过 Diameter协议消息（重鉴权请求消息和 /或信用控制应答） 将承载优先级信息发给 PCEF。
下面描述将 Bearer-Priority 设置在授权 QoS (服务质量） 信元中 ( Authorized-QoS AVP ) 中的方法：
Authorized-QoS ::= < AVP Header: 1016 >
[ QoS-Class-Identifier ]
[ Maximum-Requested-B andwidth-UL ]
[ Maximum-Requested-Bandwidth-DL ]
[ Guaranteed-Bitrate-UL ]
[ Guaranteed-Bitrate-DL ]
[Bearer-Priority]
[ Bearer-Identifier ]
其中， 承载标识（Bearer-Identifier )表示 IP接入承载的标识。 当授权 QoS信 元（Authorized-QoS AVP )放置在计费规则定义信元（Charging-Rule-Defmition AVP ) 中时， Bearer-Priority表示相应 PCC规则中定义的业务数据流的优先级级 别。当授权 QoS信元（ Authorized-QoS AVP )放置在重鉴权请求（ Re-Auth-Request， RAR )或信用控制应答消息中， 如果这时候授权 QoS信元没有携带承载标识 ( Bearer-Identifier )，则该承载优先级级别是表示整个 IP接入会话的优先级级别； 如果这时候授权 QoS信元带有承载标识（Bearer-Identifier ) , 则该承载优先级级 别是表示承载标识对应的 IP接入承载的优先豉。
步骤 503、 PCEF根据 Gx接口下发的承载优先级信息对业务进行相应的处理， 或映射到 IP接入承载的分配 /保持优先级上， 以便根据 ARP对业务进行处理， 这 样， 就使得 PCEF可根据策略上下文信息进行业务处理， 保证了全网对业务优先 级的支持。 所述处理如： PCEF根据承载优先级进行资源预留， 以便当高优先级 业务和低优先级业务并发时， 将优先保证高优先级业务。
发明的业务处理流程。
实施例二
本实施例描述根据应用会话的业务类型导出业务数据流的承载优先级信息 的应用实例。
应用功能实体根据应用会话的业务类型向 PCRF下发业务类型指示， 现假设 向 PCRF下发紧急业务指示， PCRF根据紧急业务类型指示导出业务数据流的承载 优先级级别， 通过 Gx接口下发到 PCEF, PCEF根据业务数据流的承载优先级级 别更改原来 ARP优先级級别，或创建满足当前承载优先级级别的 IP接入承载用于 承栽紧急业务。 下面结合图 6描述上述情形下的业务处理流程。
步骤 601、 应用功能实体从应用会话中获得业务类型信息后， 发送鉴权授权 请求消息到 PCRF , 所述鉴权授权请求消息中带有业务类型和业务优先级： Reservation-Priority。 Reservation-Priority (从氐 1】高)定义^！口下：
DEFAULT ( 0 )
PRIORITY-ONE ( 1 )
PRIORITY-TWO ( 2 )
PRIORITY- THREE ( 3 )
PRIORITY- FOUR ( 4 )
PRIORITY-FIVE ( 5 )
PRIORITY-SIX ( 6 )
步骤 602、 PCRF收到鉴权授权请求消息后， 根据业务类型 （本实施例中业 务类型为紧急业务）导出紧急业务对应的业务数据流的承载优先级信息 （导出 规则参见实施例一的步骤 501 ) , 即紧急业务的业务数据流的承载优先级级别。
步骤 603、 PCRF将业务数据流的承载优先级设置在计费规则定义信元中， 然后将计费规则定义信元设置在重鉴权请求消息 （设置方法参见实施例一的步 骤 502 ) , 并将发送重鉴权请求消息到 PCEF, 消息中带有需要安装的 PCC规则、 授权的 QoS信息和紧急业务的业务数据流的承载优先级级别。
步骤 604、 PCEF安装 PCC规则， 根据 Gx接口下发的 PCC规则执行策略， 并 创建满足当前承载优先级级别的 IP接入承载用于承载紧急业务，或根据业务数据 流的承载优先级更改原来 IP接入承载的优先级级别。更改方法可以是，将具体业 务数据流的承载优先级映射到 IP接入承载的 ARP优先级级别，映射表可以如下表 所示。
业务数据流的承载优先级 IP接入承载的 ARP优先级
0,1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
10 10
11 11
12 12
13 13
14 14
15 15 步骤 605、 PCEF给 PCRF回重鉴权应答消息。
步骤 606、 PCRF给应用功能实体回鉴权授权应答消息。
步骤 607、 PCEF发起 IP接入会话的修改或 QoS的更新操作， 根据映射后的 IP 优先级级别的 IP接入承载用于承载紧急业务。
根据本实施例， 由于不同业务类型对应不同的承载优先级级别， 紧急业务 对应较高的承载优先级级别， 普通业务对应较低的承载优先级级别， 这样 PCEF 在处理业务时通过优先考虑承载优先级级别较高的业务， 可使紧急业务得到优 先处理（如分配承载、 预留资源等） ， 从而保证了紧急业务的优先运行。
实施例三
本实施例为根据用户签约优先级导出 IP接入承载的承载优先级应用实例。 用户在 IP接入会话建立时， PCRF到 SPR中取签约信息， 签约信息中定义有用户 优先级， PCRF将根据用户优先级导出到承载优先级， 并发送给 PCEF进行处理。 下面参照图 7描述具体流程。
步骤 701、 用户发起 IP接入会话建立请求到 PCEF。
步骤 702、 PCEF发送信用控制请求消息到 PCRF, 用于请求策略信息。
步骤 703、 PCRF到 SPR中获取用户信息，所述用户信息包括用户优先级信息。 步骤 704、 PCRF进行策略决策， 如根据用户优先级信息导出承载优先级信 息（导出规则参见实施例一的步骤 501 ) 。
步骤 705、 PCRF发送信用控制应答消息到 PCEF, 消息中带有策略信息。 所 述策略信息包括 PCC规则、 授权的 QoS信息和 IP接入承载的承载优先级信息。 制的 IP接入承载的分配 /保持优先级（映射方法参见实施例二的步骤 604 ) 。
步骤 707、 PCEF向用户终端发送携带有分配 /保持优先级信息的 IP接入会话 建立应答消息。
根据本实施例， 由于不同用户对应不同的承载优先级级别， 较高的用户优 先级对应较高的承载优先级级别， 较低的用户优先级对应较低的承载优先级级 高用户优先级的业务得到优先处理（如分配承载、 预留资源等） ， 从而保证了 较高用户优先级的业务的优先运行。
实施例四
本实施例描述 PCEF资源冲突情况下优先保证高优先级承载资源的应用实 例。 假设用户 1和用户 2的应用会话通过 PCRF向承载层的 PCEF申请承载资源时。 下面参照图 8描述具体流程。
步骤 801、 对于用户 1 , 应用功能实体会话的建立， 会触发应用功能实体发 送鉴权授权请求消息到 PCRF , 消息中带有业务应用信息。
步骤 802、 对用户 2， 应用功能实体会话的建立， 会触发应用功能实体发送 鉴权授权请求消息到 PCRF, 消息中带业务应用信息。
步骤 803、 PCRF进行策略决策， 根据业务应用信息和用户签约信息等分别 导出用户 1和用户 2的应用业务会话所对应的承载的优先级级别， 假设导出的用 户 2的应用业务会话对应的承载优先级级别高于用户 1相应的承载优先级级别。
步骤 804、 PCRF发送重鉴权请求消息到 PCEF, 消息中带有用户 1需要安装、 修改或删除的 PCC规则、 授权的 QoS信息和承载优先级信息。
步骤 805、 PCRF同样发送重鉴权请求消息到 PCEF, 消息中带有用户 2需要安 装、 修改或删除的 PCC规则、 授权的 QoS信息和承载优先级信息。
步骤 806、 PCEF根据 Gx接口下发的规则和承载优先级信息进行策略执行， PCEF发现目前承载资源只能满足用户 1或用户 2,而不能同时满足用户 1和用户 2， 这时， 可才 据承载优先级别优先为承载优先级级别高的用户 2分配承载资源， 用 户 2的承载资源分配成功。 对用户 1而言， 因资源不足而导致用户 1的承载资源分 配失败。
步骤 807、 PCEF给 PCRF回重鉴权应答消息， 消息中带有用户 1资源分配失败
A-i-自 步驟 808、 PCEF给 PCRF回重鉴权应答消息， 用于成功应答用户 2 重鉴权请 求消息。
步骤 809、 PCRF给应用功能实体回鉴权授权应答消息， 消息中带有用户 1资 源分配失败信息， 导致应用功能实体上的应用会话失败。
步骤 810、 PCRF给应用功能实体回鉴权授权应答消息， 用于成功应答用户 2 鉴权授权请求信息
步骤 811、 PCEF为用户 2发起相应 IP接入会话的更新或 QoS的更新操作。 步骤 812、 高优先级用户 2进行应用业务。
在本实施例中， 由于 PCEF资源限制， 只能为一个用户的应用会话分配承载 资源， 由于用户 2具有较高的优先级， 所以 PCEF为用户 2分配承载资源， 用户 2 可以成功进行应用会话， 而不会为用户 1分配资源导致用户 2会话失败， 从而保 证了用户优先级较高的会话得已优先建立， 使得 PCEF可根据策略上下文信息分 配承载资源。
实施例五
参照图 1， 本实施例公开了一种业务处理系统， 包括： 策略控制和计费规则 功能实体， 用于才 M居获得策略上下文信息， 所述策略上下文信息至少包括下述 因素之一： 业务类型、 业务优先级、 用户优先级和自定义优先级； 并根据所述 策略上下文信息生成承载优先级信息， 然后将所述承载优先级信息发给发给策 略和计费执行实体； 策略和计费执行实体， 用于根据所述承载优先级信息处理 业务； 应用功能实体， 用于获得业务类型和业务优先级， 并将业务类型和业务 优先级发给策略控制和计费规则功能实体； 签约信息库， 用于存储用户签约数 据， 所述用户签约数据包括用户优先级。
实施例六
如图 9所示， 本实施例公开一种策略控制和计费规则功能实体， 包括： 获得 单元， 用于才艮据获得策略上下文信息， 所述策略上下文信息至少包括下述因素 之一： 业务类型、 业务优先级、 用户优先级和自定义优先级； 生成单元， 用于 根据所述策略上下文信息生成承载优先级信息； 发送单元， 用于将所述承载优 先级信息发给发给策略和计费执行实体。
实施例七
如图 10所示， 本实施例公开了一种策略和计费执行实体， 包括： 接收单元， 用于接收策略控制和计费规则功能实体发送的所述承载优先级信息处理业务； 处理单元， 用于根据所述承载优先级信息处理业务。
根据本发明实施例， PCRF根据应用业务类型、 应用业务优化级、 不同优先 级的用户、 或运营商自定义的策略等策略上下文信息来决定承载层业务数据流、 IP接入会话或 IP接入承载的承载优先级信息。 并将所述承载优先级信息通过 Gx 接口下发给 PCEF,使得 PCEF根据接收的某一业务数据流或特定用户承载的承载 优先级信息对业务数据流或特定用户承载进行处理， 或将接收的某一业务数据 流或特定用户承载的承载优先级信息映射到 ARP优先级上， 使得业务优先级和 接入网使用的分配 /保持优先级相关联， 以便接入网根据 ARP对业务数据流或特 定用户承载进行处理， 这样， 可以使得业务优先级的较高会话优先获得资源， 业务优先级较低的会话可能被释放。 从而较好地保证了业务优先级在接入网的 资源预留， 保证了全网对业务优先级的支持。
虽然通过实施例描绘了本发明， 但本领域普通技术人员知道， 在不脱离本 发明的精神和实质的情况下， 就可使本发明有许多变形和变化， 本发明的范围 由所附的权利要求来限定。

Claims

权利要求 一种业务处理方法， 其特征在于， 包括：
接收来自策略控制和计费规则功能实体的承载优先级信息， 所述承载优先 级信息包括： 业务数据流的承载优先级信息、 IP接入会话的承载优先级信息和 / 5 或 IP接入承载的承载优先级信息；
根据承栽优先级信息处理业务。
2、 根据权利要求 1所述的方法， 其特征在于， 所述方法还包括： 增加承载 优先级信元， 所述承载优先级信元可以直接设置在承栽优先级消息中、 或者设 置在已有信元中， 所述承载优先级消息包括信用控制应答消息、 重鉴权请求消0 息； 所述已有信元包括计费规则定义信元和 /或授权服务质量信元； 所述承栽优 先级信元包括： 承载优先级级别子信元， 用于承载承载优先级级别； 和承载标 识子信元， 用于承载用户承载标识。
3、 根据权利要求 2所述的方法， 其特征在于， 所述方法还包括： 将承载优 先级信息设置在所述承载优先级信元中， 设置方法如下：
5 当所述承载优先级信息为业务数据流的承载优先级信息时， 将所述承载标 识子信元设置为空， 将所述业务数据流的承载优先级级别设置在所述承载优先 级子信元中； 子信元设置为空，将所述 IP接入会话的承载优先级级别设置在所述承载标识子信
>0 元中；
当所述承栽优先级信息为 IP接入承载的承载优先级信息，将所述 IP接入承载 标识设置在承栽标识子信元中，将 IP接入承载的承载优先级级别设置在所述承载 标识子信元中。
4、 根据权利要求 3所述的方法， 其特征在于， 所述承载优先级信元直接设 :5 置在承载优先级消息中具体包括： 当所述承载优先级信息为业务数据流的承载优先级信息时， 将所述承载优 先级信元设置在计费规则定义信元中；
当所述承载优先级信息为 IP接入会话的承载优先级信息时，将所述承载优先 级信元设置在所述信用控制应答消息和 /或重鉴权请求消息中；
当所述承载优先级信息为 IP接入承载的承载优先级信息，将所述承载优先级 信元设置在所述信用控制应答消息、 重鉴权请求消息中。
5、 根据权利要求 3所述的方法， 其特征在于， 所述已有信元为授权服务质 量信元时， 所述承载优先级信元设置在已有信元具体包括：
当所述承载优先级信息为业务数据流的承载优先级信息时， 将所述承载优 先级信元设置在授权服务质量信元， 然后将授权服务质量信元设置在计费规则 定义信元中；
当所述承载优先级信息为 IP接入会话的承载优先级信息时，将所述承载优先 级信元设置在授权服务质量信元， 然后将授权服务质量信元设置在所述信用控 制应答消息和 /或重鉴权请求消息中；
当所述承载优先级信息为 IP接入承载的承载优先级信息，将所述承载优先级 信元设置在授权服务质量信元， 然后将授权服务质量信元设置在所述信用控制 应答消息、 重鉴权请求消息中。
6、 根据权利要求 4或 5所述的方法， 其特征在于， 所述接收来自策略控制和 计费规则功能实体的承载优先级信息具体包括： 通过承载优先级消息接收来自 策略控制和计费规则功能实体的所述承载优先级信息。
7、 根据权利要求 1所述的方法， 其特征在于， 所述根据承载优先级信息处 理业务具体包括： 将承载优先级级别映射到分配 /保持优先级上。
8、 根据权利要求 1所述的方法， 其特征在于， 所述根据承载优先级信息处 理业务具体包括： 根据承载优先级级别对业务进行区别处理， 当资源冲突时优 先保证承载优先级级别较高的业务。
9、 根据权利要求 1所述的方法， 其特征在于， 所述方法还包括： 策略控制 和计费规则功能实体获得策略上下文信息， 所述策略上下文信息包括业务类型、 业务优先级、 用户优先级。
10、 根据权利要求 9所述的方法， 其特征在于， 所述策略控制和计费规则功 能实体获得策略上下文信息具体包括： 策略控制和计费规则功能实体从应用功 能实体获得业务类型和业务优先级。
11、 根据权利要求 9所述的方法， 其特征在于， 所述策略控制和计费规则功 能实体获得策略上下文信息具体包括： 策略控制和计费规则功能实体从签约信 息库获得用户优先级。
12、 根据权利要求 1至 11其中之一所述的方法， 其特征在于， 所述承载优先 級信息由策略上下文信息生成。
13、 根据权利要求 12所述的方法， 其特征在于， 所述承载优先级信息由策 略上下文信息生成具体包括： 所述承载优先级信息由下述因素任意组合生成： 业务类型、 业务优先级、 用户优先级和自定义优先级。
14、 一种业务处理系统， 其特征在于， 包括：
策略控制和计费规则功能实体， 用于根据获得策略上下文信息， 所述策略 上下文信息至少包括下述因素之一： 业务类型、 业务优先级、 用户优先级和自 定义优先级； 并根据所述策略上下文信息生成承载优先级信息， 然后将所述承 载优先级信息发给发给策略和计费执行实体；
策略和计费执行实体， 用于根据所述承载优先级信息处理业务。
15、 根据权利要求 14所述的业务处理系统， 其特征在于， 所述系统还包括： 应用功能实体， 用于获得业务类型和业务优先级， 并将业务类型和业务优 先级发给策略控制和计费规则功能实体。
16、 根据权利要求 14所述的业务处理系统， 其特征在于， 所述系统还包括： 签约信息库， 用于存储用户签约数据， 所述用户签约数据包括用户优先级。
17、 一种策略控制和计费规则功能实体， 其特征在于， 包括：
获得单元， 用于根据获得策略上下文信息， 所述策略上下文信息至少包括 下述因素之一： 业务类型、 业务优先级、 用户优先级和自定义优先级； 生成单元， 用于根据所述策略上下文信息生成承载优先级信息；
发送单元， 用于将所述承载优先级信息发给发给策略和计费执行实体。
18、 一种策略和计费执行实体， 其特征在于， 包括：
接收单元， 用于接收策略控制和计费规则功能实体发送的所述承载优先级 信息处理业务；
处理单元， 用于 4 据所述承载优先级信息处理业务。
PCT/CN2007/003984 2007-03-23 2007-12-29 Procédé et système et fonction pcrf pour traitement d'opérations WO2008116363A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
ES07846018T ES2397285T3 (es) 2007-03-23 2007-12-29 Método, sistema y política de control y función de reglas de facturación para procesar flujos de datos de servicio
EP07846018A EP2093931B1 (en) 2007-03-23 2007-12-29 Method, system and policy control and charging rules function for processing service data streams
JP2009546630A JP5189108B2 (ja) 2007-03-23 2007-12-29 サービス処理方法およびサービス処理システム、ならびにポリシー制御および料金請求規則機能
US12/564,558 US8601125B2 (en) 2007-03-23 2009-09-22 Service processing method and system, and policy control and charging rules function
US14/069,546 US9438522B2 (en) 2007-03-23 2013-11-01 Service processing method and system, and policy control and charging rules function

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710089952.5 2007-03-23
CN2007100899525A CN101272256B (zh) 2007-03-23 2007-03-23 业务处理方法和系统、策略控制和计费规则功能实体

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/564,558 Continuation US8601125B2 (en) 2007-03-23 2009-09-22 Service processing method and system, and policy control and charging rules function

Publications (1)

Publication Number Publication Date
WO2008116363A1 true WO2008116363A1 (fr) 2008-10-02

Family

ID=39788027

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/003984 WO2008116363A1 (fr) 2007-03-23 2007-12-29 Procédé et système et fonction pcrf pour traitement d'opérations

Country Status (6)

Country Link
US (2) US8601125B2 (zh)
EP (1) EP2093931B1 (zh)
JP (1) JP5189108B2 (zh)
CN (1) CN101272256B (zh)
ES (1) ES2397285T3 (zh)
WO (1) WO2008116363A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013510535A (ja) * 2009-11-09 2013-03-21 サムスン エレクトロニクス カンパニー リミテッド ハンドオーバー中に単一無線映像通話連続性を支援する方法及びシステム
CN104202738A (zh) * 2014-08-30 2014-12-10 华为技术有限公司 策略控制方法、系统及网关

Families Citing this family (159)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101499919B (zh) * 2008-01-28 2012-12-12 华为技术有限公司 策略决策实体的管理方法、管理网元及网络系统
US8924543B2 (en) 2009-01-28 2014-12-30 Headwater Partners I Llc Service design center for device assisted services
US8402111B2 (en) 2009-01-28 2013-03-19 Headwater Partners I, Llc Device assisted services install
US8340634B2 (en) 2009-01-28 2012-12-25 Headwater Partners I, Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US8635335B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc System and method for wireless network offloading
US8229812B2 (en) * 2009-01-28 2012-07-24 Headwater Partners I, Llc Open transaction central billing system
US8626115B2 (en) 2009-01-28 2014-01-07 Headwater Partners I Llc Wireless network service interfaces
US8832777B2 (en) 2009-03-02 2014-09-09 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US8548428B2 (en) 2009-01-28 2013-10-01 Headwater Partners I Llc Device group partitions and settlement platform
US8725123B2 (en) 2008-06-05 2014-05-13 Headwater Partners I Llc Communications device with secure data path processing agents
US8275830B2 (en) 2009-01-28 2012-09-25 Headwater Partners I Llc Device assisted CDR creation, aggregation, mediation and billing
US8406748B2 (en) 2009-01-28 2013-03-26 Headwater Partners I Llc Adaptive ambient services
US8391834B2 (en) 2009-01-28 2013-03-05 Headwater Partners I Llc Security techniques for device assisted services
US8346225B2 (en) 2009-01-28 2013-01-01 Headwater Partners I, Llc Quality of service for device assisted services
US8589541B2 (en) 2009-01-28 2013-11-19 Headwater Partners I Llc Device-assisted services for protecting network capacity
US8813168B2 (en) 2008-06-05 2014-08-19 Tekelec, Inc. Methods, systems, and computer readable media for providing nested policy configuration in a communications network
US8898293B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Service offer set publishing to device agent with on-device service selection
US8924469B2 (en) 2008-06-05 2014-12-30 Headwater Partners I Llc Enterprise access control and accounting allocation for access networks
US7937300B2 (en) * 2008-07-10 2011-05-03 Bridgewater Systems Corp. System and method for providing interoperability between diameter policy control and charging in a 3GPP network
CN101360113B (zh) * 2008-09-01 2013-05-08 中兴通讯股份有限公司 服务质量请求信息的实现方法以及策略执行功能实体
US8683553B2 (en) * 2009-01-07 2014-03-25 Telcordia Technologies, Inc. System, method, and computer program products for enabling trusted access to information in a diverse service environment
WO2010086013A1 (en) * 2009-01-27 2010-08-05 Telefonaktiebolaget Lm Ericsson (Publ) Group session management for policy control
US10798252B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10484858B2 (en) 2009-01-28 2019-11-19 Headwater Research Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US9270559B2 (en) 2009-01-28 2016-02-23 Headwater Partners I Llc Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US8893009B2 (en) 2009-01-28 2014-11-18 Headwater Partners I Llc End user device that secures an association of application to service policy with an application certificate check
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US10779177B2 (en) 2009-01-28 2020-09-15 Headwater Research Llc Device group partitions and settlement platform
US10841839B2 (en) 2009-01-28 2020-11-17 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10057775B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US9392462B2 (en) 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US10715342B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US8793758B2 (en) 2009-01-28 2014-07-29 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US8745191B2 (en) 2009-01-28 2014-06-03 Headwater Partners I Llc System and method for providing user notifications
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US9609510B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Automated credential porting for mobile devices
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US9357568B2 (en) * 2009-06-16 2016-05-31 Futurewei Technologies, Inc. System and method for adapting an application source rate to a load condition
US8972553B2 (en) 2009-08-10 2015-03-03 Qualcomm Incorporated Method and apparatus for handling policy and charging control rule or quality of service rule modification failures
CN101998531B (zh) * 2009-08-11 2013-04-24 华为技术有限公司 策略和计费控制规则授权方法、装置及系统
KR101643932B1 (ko) 2009-08-28 2016-07-29 삼성전자 주식회사 실시간 과금 시스템 및 그 시스템에서 ＱｏＳ 및 과금 변경 제어 방법
ES2435472T3 (es) * 2009-09-25 2013-12-19 Telefonaktiebolaget Lm Ericsson (Publ) Método y aparato para gestionar una prioridad de retención y de asignación evolucionada
CN102612821B (zh) * 2009-10-02 2016-03-09 瑞典爱立信有限公司 用于专用承载的计费关联的装置
US8750126B2 (en) * 2009-10-16 2014-06-10 Tekelec, Inc. Methods, systems, and computer readable media for multi-interface monitoring and correlation of diameter signaling information
WO2011047382A2 (en) * 2009-10-16 2011-04-21 Tekelec Methods, systems, and computer readable media for providing diameter signaling router with integrated monitoring and/or firewall functionality
US10721269B1 (en) 2009-11-06 2020-07-21 F5 Networks, Inc. Methods and system for returning requests with javascript for clients before passing a request to a server
US8787174B2 (en) * 2009-12-31 2014-07-22 Tekelec, Inc. Methods, systems, and computer readable media for condition-triggered policies
CN102158907B (zh) 2010-02-12 2013-01-23 华为技术有限公司 优先级业务处理方法、装置和系统
IN2012CN07527A (zh) 2010-02-12 2015-08-07 Tekelec Inc
EP2534794B1 (en) * 2010-02-12 2019-03-27 Tekelec, Inc. Methods, systems, and computer readable media for providing peer routing at a diameter node
US9647936B2 (en) 2010-02-12 2017-05-09 Tekelec, Inc. Methods, systems, and computer readable media for routing diameter messages at a diameter signaling router
US9503483B2 (en) * 2010-02-16 2016-11-22 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatuses for identifying and reporting quality of service rules applicable to a communication session
US9185510B2 (en) 2010-03-03 2015-11-10 Tekelec, Inc. Methods, systems, and computer readable media for managing the roaming preferences of mobile subscribers
US9917700B2 (en) 2010-03-15 2018-03-13 Tekelec, Inc. Systems, methods, and computer readable media for policy enforcement correlation
CN102238698B (zh) * 2010-04-27 2016-06-15 中兴通讯股份有限公司 授权请求方法、系统及装置
CN102238512B (zh) * 2010-04-29 2015-11-25 中兴通讯股份有限公司 机器类通信mtc的策略应用方法及策略和计费执行实体
US8645510B2 (en) * 2010-05-20 2014-02-04 Alcatel Lucent Method of distributing PCC rules among IP-connectivity access network (IP-CAN) bearers
US9141625B1 (en) 2010-06-22 2015-09-22 F5 Networks, Inc. Methods for preserving flow state during virtual machine migration and devices thereof
US10015286B1 (en) 2010-06-23 2018-07-03 F5 Networks, Inc. System and method for proxying HTTP single sign on across network domains
US8347100B1 (en) 2010-07-14 2013-01-01 F5 Networks, Inc. Methods for DNSSEC proxying and deployment amelioration and systems thereof
US8812020B2 (en) 2010-10-15 2014-08-19 Tekelec, Inc. Methods, systems, and computer readable media for location-based policy enhancement
CN102457938B (zh) * 2010-10-18 2016-03-30 中兴通讯股份有限公司 终端接入限制的方法及系统
US8626156B2 (en) 2010-10-20 2014-01-07 Tekelec, Inc. Methods, systems, and computer readable media for selective policy enhancement (PE) for high-usage roamers
US9237480B2 (en) * 2010-10-22 2016-01-12 Telefonaktiebolaget L M Ericsson (Publ) Accelerated content delivery
WO2012052569A1 (en) 2010-10-22 2012-04-26 Telefonaktiebolaget L M Ericsson (Publ) Mobile-access information based adaptation of network address lookup for differentiated handling of data traffic
EP2633667B1 (en) * 2010-10-29 2017-09-06 F5 Networks, Inc System and method for on the fly protocol conversion in obtaining policy enforcement information
US8681622B2 (en) 2010-12-17 2014-03-25 Tekelec, Inc. Policy and charging rules function (PCRF) and performance intelligence center (PIC) based congestion control
US9374737B2 (en) * 2010-12-17 2016-06-21 Telefonaktiebolaget Lm Ericsson (Publ) Policy and/or charging control
US10135831B2 (en) 2011-01-28 2018-11-20 F5 Networks, Inc. System and method for combining an access control system with a traffic management system
WO2012119147A1 (en) 2011-03-03 2012-09-07 Tekelec, Inc. Methods, systems, and computer readable media for enriching a diameter signaling message
US20120233335A1 (en) * 2011-03-08 2012-09-13 Alcatel Lucent Canada Inc. Auxiliary host and sessions
US8902854B2 (en) 2011-03-18 2014-12-02 Tekelec, Inc. Methods, systems, and computer readable media for diameter-based steering of mobile device network access
US9154826B2 (en) 2011-04-06 2015-10-06 Headwater Partners Ii Llc Distributing content and service launch objects to mobile devices
US9225849B2 (en) 2011-05-06 2015-12-29 Tekelec, Inc. Methods, systems, and computer readable media for steering a subscriber between access networks
CN102202411B (zh) * 2011-06-01 2013-10-09 上海华为技术有限公司 业务数据的调度方法及相关设备
US9246819B1 (en) 2011-06-20 2016-01-26 F5 Networks, Inc. System and method for performing message-based load balancing
US9106769B2 (en) 2011-08-10 2015-08-11 Tekelec, Inc. Methods, systems, and computer readable media for congestion management in a diameter signaling network
US9495706B2 (en) * 2011-10-03 2016-11-15 Alcatel Lucent Sy based integrated policy and charging control
US8792439B2 (en) * 2011-10-05 2014-07-29 Alcatel Lucent Method and system for rate adaptive allocation of resources
US9270766B2 (en) 2011-12-30 2016-02-23 F5 Networks, Inc. Methods for identifying network traffic characteristics to correlate and manage one or more subsequent flows and devices thereof
CN105263164B (zh) * 2012-01-20 2019-02-19 华为技术有限公司 一种服务质量控制的方法、设备和系统
SG11201404248TA (en) * 2012-01-20 2014-10-30 Huawei Tech Co Ltd Method, device and system for controlling quality of service
KR20140125814A (ko) 2012-01-27 2014-10-29 노키아 솔루션스 앤드 네트웍스 오와이 모바일 패킷 코어 네트워크에서의 세션 종결
US9036822B1 (en) 2012-02-15 2015-05-19 F5 Networks, Inc. Methods for managing user information and devices thereof
US10230566B1 (en) 2012-02-17 2019-03-12 F5 Networks, Inc. Methods for dynamically constructing a service principal name and devices thereof
US9172753B1 (en) 2012-02-20 2015-10-27 F5 Networks, Inc. Methods for optimizing HTTP header based authentication and devices thereof
EP2853074B1 (en) 2012-04-27 2021-03-24 F5 Networks, Inc Methods for optimizing service of content requests and devices thereof
US8988997B2 (en) 2012-06-08 2015-03-24 Telefonaktiebolaget L M Ericsson (Publ) Communication network congestion control using allocation and retention priority
WO2014014823A1 (en) 2012-07-14 2014-01-23 Tekelec, Inc. Methods, systems, and computer readable media for policy-based local breakout (lbo)
WO2014014829A1 (en) 2012-07-14 2014-01-23 Tekelec, Inc. Methods, systems, and computer readable media for dynamically controlling congestion in a radio access network
JP6448536B2 (ja) 2012-07-20 2019-01-09 テケレック・インコーポレイテッドＴｅｋｅｌｅｃ， Ｉｎｃ． ポリシールールをモバイルエッジに配信するための方法、システム、およびコンピュータ読取可能媒体
CN102882726B (zh) * 2012-09-29 2015-11-18 北京东土科技股份有限公司 一种可配置设备的配置管理方法及系统
US9319867B2 (en) * 2012-10-02 2016-04-19 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatuses for policy and charging control of machine-to-machine type communications
CN103857004A (zh) * 2012-12-03 2014-06-11 华为技术有限公司 处理无线网络用户接入的方法、装置及系统
EP2956872B1 (en) * 2013-02-15 2018-08-08 Telefonaktiebolaget LM Ericsson (publ) Method and apparatuses for handling concurrent accesses to data in a directory
US9215133B2 (en) 2013-02-20 2015-12-15 Tekelec, Inc. Methods, systems, and computer readable media for detecting orphan Sy or Rx sessions using audit messages with fake parameter values
CN104010332B (zh) * 2013-02-21 2019-03-15 中兴通讯股份有限公司 承载绑定方法及系统
CN103298145A (zh) * 2013-05-09 2013-09-11 大唐移动通信设备有限公司 差分服务代码点dscp信息的配置方法、装置及系统
EP2991400A4 (en) * 2013-05-30 2016-05-18 Huawei Tech Co Ltd DATA TRANSFER CONTROL METHOD AND DEVICE BASED ON A WIRELESS COMMUNICATION NETWORK
JP2016531489A (ja) 2013-07-25 2016-10-06 コンヴィーダ ワイヤレス， エルエルシー サービス層サウスバウンドインターフェースおよびサービスの質
US10187317B1 (en) 2013-11-15 2019-01-22 F5 Networks, Inc. Methods for traffic rate control and devices thereof
KR102118412B1 (ko) * 2013-11-27 2020-06-03 삼성전자 주식회사 기기 대 기기 무선 통신을 위한 자원 운용 방법 및 장치
WO2014029406A2 (en) * 2013-12-11 2014-02-27 Vkr Holding A/S Presence detection in building automation systems
US10015143B1 (en) 2014-06-05 2018-07-03 F5 Networks, Inc. Methods for securing one or more license entitlement grants and devices thereof
CN105307141B (zh) * 2014-06-11 2019-11-29 南京中兴新软件有限责任公司 策略控制和计费的方法、装置及设备
US10122630B1 (en) 2014-08-15 2018-11-06 F5 Networks, Inc. Methods for network traffic presteering and devices thereof
CN105634970B (zh) * 2014-11-06 2019-06-11 中国移动通信集团公司 一种流量核减方法、设备及系统
WO2016074177A1 (zh) 2014-11-12 2016-05-19 华为技术有限公司 控制数据流绑定承载的方法及设备
CN105827415B (zh) * 2015-01-07 2018-12-04 中国移动通信集团上海有限公司 用于加速业务专有承载恢复的pcc系统、设备及方法
US10834065B1 (en) 2015-03-31 2020-11-10 F5 Networks, Inc. Methods for SSL protected NTLM re-authentication and devices thereof
US10505818B1 (en) 2015-05-05 2019-12-10 F5 Networks. Inc. Methods for analyzing and load balancing based on server health and devices thereof
US11350254B1 (en) 2015-05-05 2022-05-31 F5, Inc. Methods for enforcing compliance policies and devices thereof
US10117127B2 (en) 2015-07-08 2018-10-30 Oracle International Corporation Methods, systems, and computer readable media for communicating radio access network congestion status information for large numbers of users
CN106358172B (zh) * 2015-07-17 2020-05-05 中兴通讯股份有限公司 网络架构中网元之间的交互方法及装置
US10623936B2 (en) * 2015-10-02 2020-04-14 Telefonaktiebolaget Lm Ericsson (Publ) Priority handling for data flow transport in communication systems
US11757946B1 (en) 2015-12-22 2023-09-12 F5, Inc. Methods for analyzing network traffic and enforcing network policies and devices thereof
US10404698B1 (en) 2016-01-15 2019-09-03 F5 Networks, Inc. Methods for adaptive organization of web application access points in webtops and devices thereof
US10797888B1 (en) 2016-01-20 2020-10-06 F5 Networks, Inc. Methods for secured SCEP enrollment for client devices and devices thereof
US11178150B1 (en) 2016-01-20 2021-11-16 F5 Networks, Inc. Methods for enforcing access control list based on managed application and devices thereof
CN107370779B (zh) 2016-05-12 2020-12-15 华为技术有限公司 一种数据传输方法、装置及系统
JP2016154389A (ja) * 2016-05-18 2016-08-25 ノキア ソリューションズ アンド ネットワークス オサケユキチュア 移動パケットコアネットワークにおけるセッション終了
US10321300B2 (en) 2016-05-26 2019-06-11 Oracle International Corporation Methods, systems, and computer readable media for providing end-to-end priority service in long term evolution (LTE) or subsequent generation networks
US10791088B1 (en) 2016-06-17 2020-09-29 F5 Networks, Inc. Methods for disaggregating subscribers via DHCP address translation and devices thereof
CN107666505B (zh) * 2016-07-29 2020-09-15 京东方科技集团股份有限公司 对资源接入进行控制的方法和装置
US11063758B1 (en) 2016-11-01 2021-07-13 F5 Networks, Inc. Methods for facilitating cipher selection and devices thereof
US10505792B1 (en) 2016-11-02 2019-12-10 F5 Networks, Inc. Methods for facilitating network traffic analytics and devices thereof
US10425342B2 (en) 2016-12-16 2019-09-24 Oracle International Corporation Methods, systems, and computer readable media for priority routing of diameter messages
CN108270577B (zh) * 2016-12-30 2020-12-22 中移（杭州）信息技术有限公司 一种基于策略与计费控制架构的策略运营方法及系统
US10812266B1 (en) 2017-03-17 2020-10-20 F5 Networks, Inc. Methods for managing security tokens based on security violations and devices thereof
US10225762B2 (en) 2017-03-28 2019-03-05 Oracle International Corporation Methods, systems, and computer readable media for message flood suppression during access node-gateway (AN-GW) unavailability and after AN-GW restoration
US10237418B2 (en) 2017-04-21 2019-03-19 Oracle International Corporation Methods, systems, and computer readable media for charging based on radio congestion in mobile networks
US10972453B1 (en) 2017-05-03 2021-04-06 F5 Networks, Inc. Methods for token refreshment based on single sign-on (SSO) for federated identity environments and devices thereof
US11122042B1 (en) 2017-05-12 2021-09-14 F5 Networks, Inc. Methods for dynamically managing user access control and devices thereof
US11343237B1 (en) 2017-05-12 2022-05-24 F5, Inc. Methods for managing a federated identity environment using security and access control data and devices thereof
WO2018220426A1 (en) * 2017-05-31 2018-12-06 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for packet processing of a distributed virtual network function (vnf)
US11122083B1 (en) 2017-09-08 2021-09-14 F5 Networks, Inc. Methods for managing network connections based on DNS data and network policies and devices thereof
CN111355595B (zh) * 2018-12-21 2022-03-29 中国移动通信集团山东有限公司 Pcc策略调度方法及系统
US11438802B2 (en) 2019-11-27 2022-09-06 Aeris Communications, Inc. Method and system for quality-of-service authorization based on type of radio access technology and other data session attributes
CN112491631B (zh) * 2020-12-08 2022-10-14 国家电网公司华中分部 一种业务qos保障方法、装置、设备和存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005084061A1 (fr) * 2004-01-28 2005-09-09 France Telecom Procede de gestion des ressources radio dans un reseau d’acces radio de type utran
CN1859197A (zh) * 2006-02-14 2006-11-08 华为技术有限公司 一种确定QoS策略的方法

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB9501378D0 (en) 1995-01-24 1995-03-15 Ibm A system and method for establishing a communication channel over a heterogeneous network between a source node and a destination node
FI110987B (fi) 1998-03-31 2003-04-30 Nokia Corp Menetelmä tiedonsiirtovirtausten kytkemiseksi
FI108601B (fi) 1999-01-05 2002-02-15 Nokia Corp QoS-kartoitustiedon välitys pakettiradioverkossa
WO2000057607A1 (en) 1999-03-19 2000-09-28 Atcomm Corporation Combined telephone pbx and computer data router with pooled resources
US6621793B2 (en) 2000-05-22 2003-09-16 Telefonaktiebolaget Lm Ericsson (Publ) Application influenced policy
US6870811B2 (en) 2001-01-18 2005-03-22 International Business Machines Corporation Quality of service functions implemented in input interface circuit interface devices in computer network hardware
US20020152319A1 (en) 2001-02-08 2002-10-17 Amin Rajesh B. Accounting management support based on QOS in an IP centric distributed network
SE524599C2 (sv) 2002-01-18 2004-08-31 Ericsson Telefon Ab L M Metod, system och datorprogramprodukt för att anordna tjänstekvalitet QoS
US7450591B2 (en) * 2002-10-15 2008-11-11 Telefonaktiebolaget L M Ericsson (Publ) System for providing flexible charging in a network
JP2005051580A (ja) * 2003-07-30 2005-02-24 Yokogawa Electric Corp イーサネット回線における優先度フロー別帯域制御方法及び帯域制御方式
FR2859862A1 (fr) * 2003-09-11 2005-03-18 France Telecom Procede de differenciation de la qualite de service dans les reseaux de communication mobile en mode paquets
EP1720364A4 (en) * 2004-02-23 2011-02-09 Nec Corp MOBILITY PARTNERS NETWORK AND COMPANY MANAGEMENT PROCEDURES
JP4382528B2 (ja) 2004-02-27 2009-12-16 富士通株式会社 マルチキャストネットワーク装置，マルチキャストネットワークシステムおよびマルチキャスト方法
ATE519344T1 (de) * 2004-06-21 2011-08-15 Panasonic Corp Adaptive und skalierbare dienstqualitätsarchitektur für einzelträger- multicast/broadcast-dienste
WO2006071155A1 (en) * 2004-12-29 2006-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Priority bearers in a mobile telecommunication network
WO2007097670A1 (en) * 2006-02-27 2007-08-30 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for communication
CN101047949B (zh) * 2006-03-27 2010-05-12 华为技术有限公司 业务数据流的承载控制方法
US8856860B2 (en) * 2006-08-18 2014-10-07 Cisco Technology, Inc. System and method for implementing policy server based application interaction manager

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005084061A1 (fr) * 2004-01-28 2005-09-09 France Telecom Procede de gestion des ressources radio dans un reseau d’acces radio de type utran
CN1859197A (zh) * 2006-02-14 2006-11-08 华为技术有限公司 一种确定QoS策略的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2093931A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013510535A (ja) * 2009-11-09 2013-03-21 サムスン エレクトロニクス カンパニー リミテッド ハンドオーバー中に単一無線映像通話連続性を支援する方法及びシステム
US9392626B2 (en) 2009-11-09 2016-07-12 Samsung Electronics Co., Ltd. Method and system to support single radio video call continuity during handover
CN104202738A (zh) * 2014-08-30 2014-12-10 华为技术有限公司 策略控制方法、系统及网关

Also Published As

Publication number Publication date
EP2093931A1 (en) 2009-08-26
ES2397285T3 (es) 2013-03-06
JP5189108B2 (ja) 2013-04-24
US9438522B2 (en) 2016-09-06
EP2093931B1 (en) 2012-12-05
EP2093931A4 (en) 2010-11-03
CN101272256A (zh) 2008-09-24
CN101272256B (zh) 2011-07-06
US20140064074A1 (en) 2014-03-06
US8601125B2 (en) 2013-12-03
JP2010517387A (ja) 2010-05-20
US20100017846A1 (en) 2010-01-21

Similar Documents

Publication Publication Date Title
WO2008116363A1 (fr) Procédé et système et fonction pcrf pour traitement d&#39;opérations
JP5054699B2 (ja) ポリシ施行点インターフェース・システムおよび方法
EP1762056B1 (en) Dynamic service information for the access network
US7889650B2 (en) Method for establishing diameter session for packet flow based charging
EP1964421B1 (en) Mapping of packet flows to bearers in a communication system
CN101163091B (zh) 一种资源接纳控制系统及方法
EP2005661B1 (en) System, arrangements and method relating to access handling
EP2499858B1 (en) Service event trigger
EP2521305B1 (en) Method, device and system for controlling user session policy
US20100186064A1 (en) Method and device for obtaining capabilities of policy and charging enforcement function
CN108259434B (zh) 一种用户侧QoS保障能力的开放方法及服务器
US10555325B2 (en) Network resource prioritization for mobile termination services
EP2537312A1 (en) Facilitating a communication session
WO2011120462A2 (zh) 费率组处理方法、数据业务计费方法和相关设备及系统
JP2012507223A (ja) ポリシー及び課金制御方法、サーバ、及びコンピュータプログラム
WO2011020498A1 (en) Method, apparatus and computer program for enforcing policy across associated sessions taking into account a total usage quota for associated user
JP2013535171A (ja) サービス要求に基づいてｐｃｃルールを生成および更新するためのシステムおよび方法
WO2009024050A1 (fr) Procédé, système et dispositif de commande de politique
US10673817B2 (en) Dynamic policy rule selection
WO2011120222A1 (zh) 优先级业务激活、去激活方法、装置和系统
WO2011088702A1 (zh) 在全业务融合网络中控制资源的方法和系统
WO2008083621A1 (fr) Procédé et système de traitement de flux de service ainsi que procédé et système d&#39;association d&#39;une prise en charge
CN101163102B (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: 07846018

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2449/KOLNP/2009

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2007846018

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2009546630

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE