WO2008022602A1 - Procédé, dispositif et système de commande de conditions d'utilisation et de facturation - Google Patents

Procédé, dispositif et système de commande de conditions d'utilisation et de facturation Download PDF

Info

Publication number
WO2008022602A1
WO2008022602A1 PCT/CN2007/070513 CN2007070513W WO2008022602A1 WO 2008022602 A1 WO2008022602 A1 WO 2008022602A1 CN 2007070513 W CN2007070513 W CN 2007070513W WO 2008022602 A1 WO2008022602 A1 WO 2008022602A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
policy
charging
pcef
pcef entity
Prior art date
Application number
PCT/CN2007/070513
Other languages
English (en)
Chinese (zh)
Inventor
Huadong Hu
Jin Zhang
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.
Publication of WO2008022602A1 publication Critical patent/WO2008022602A1/fr

Links

Classifications

    • 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

Definitions

  • the present invention relates to policy and charging control techniques in mobile communications, and more particularly to systems, methods and apparatus for implementing policy and charging control. Background of the invention
  • the operators In order to control the services in the network and the resources used by the services, the operators generally implement the policies and charging rules.
  • the Policy and Charging Control (PCC) framework is a standard for implementing policy and charging rules.
  • the Policy and Charging Rules Function (PCRF) entity is the core of the policy and charging function, mainly based on the Policy and Charging Enforcement Function (PCEF) entity.
  • PCRF Policy and Charging Rules Function
  • Network information formulation policies and charging rules related to the formulation of policy charging rules in the network may also be related to service-related information obtained from an application function (AF, Application Function) entity, and related to user subscription specifications obtained from an SPR (Subscription Profile Repository) entity. Information to develop policies and billing rules.
  • AF Application Function
  • SPR Subscribescription Profile Repository
  • the policy and charging execution function (PCEF) of the gateway follows the policy and charging rules formulated by the PCRF entity to the current UE.
  • the business data flow of the business is controlled.
  • the policies described herein generally refer to information such as quality of service (QoS) and gating.
  • the PCEF can control the service data flow of the current service of the UE according to these established policies.
  • PCEF can also perform traffic statistics on services to achieve billing purposes.
  • the PCC framework can be applied to existing mobile communication networks, such as: General Packet Radio Service (GPRS) network, Interworking Wireless Local Area Network (I-WLAN), Coaxial Cable Data Service Interface Specification (DOCSIS) network, etc., can also be applied to the 3rd Generation Partnership Project (3GPP) in.
  • GPRS General Packet Radio Service
  • I-WLAN Interworking Wireless Local Area Network
  • DOCSIS Coaxial Cable Data Service Interface Specification
  • 3GPP 3rd Generation Partnership Project
  • An object of the present invention is to provide a system for implementing policy and charging control.
  • the UE may continue to perform policy and charging on the service data flow of the current service of the UE. control.
  • Another object of the present invention is to provide a method for implementing policy and charging control in a communication system.
  • the service data flow of the current service of the UE may continue. Perform policy and billing control.
  • the present invention also provides an apparatus for implementing policy and charging rule functions in a communication system.
  • the present invention further provides a policy and charging execution apparatus in a communication system, which is configured to control a service data flow of a user equipment UE within a control range according to a policy and a charging rule.
  • a system for implementing policy and charging control is provided, the system comprising at least a first PCEF entity and a second PCEF entity: The first PCEF entity is configured to control, according to a policy and a charging rule, a service data flow of a current service of a user equipment UE within a control range thereof;
  • the second PCEF entity is configured to acquire a policy and a charging rule when the UE enters the second PCEF entity control range from the first PCEF entity control range, and perform a service on the current service of the UE according to the obtained policy and charging rule.
  • the data stream is controlled.
  • a method for implementing policy and charging control in a communication system when a user equipment UE enters a second PCEF entity control range from a first policy and a charging execution function PCEF entity control range, The method includes the following steps:
  • the second PCEF entity acquires the policy and the charging rule, and controls the service data flow of the current service of the UE according to the obtained policy and the charging rule.
  • the present invention also provides an apparatus for implementing a policy and charging rule function in a communication system, the apparatus for entering a second PCEF entity at a user equipment UE from a first policy and charging execution function PCEF entity control range
  • policy and charging rules are formulated for the UE according to the current network information, and the policy and charging rules are sent to the second PCEF entity.
  • the present invention further provides a policy and charging execution apparatus in a communication system, which is configured to control a service data flow of a user equipment UE within a control range according to a policy and a charging rule, when a new UE enters the device.
  • the device is configured to acquire a policy and a charging rule of the new UE from the original home policy and the charging execution device or the policy charging rule function entity PCRF of the new UE, and according to the obtained policy charging rule Controlling the service data flow of the UE.
  • the present invention also provides a policy and charging execution apparatus in a communication system, which is configured to control a service data flow of a user equipment UE within a control range according to a policy and a charging rule, when a UE within its control range enters
  • the device is configured to send the UE's policy and charging rules to the other policy and charging executing device when the other policies and charging execution devices are in range.
  • the policy and charging rule function entity PCRF is sent to request the UE to allocate policies and charging rules within the control range of other policies and charging devices.
  • the present invention provides a system, method, and apparatus for implementing policy and charging control.
  • the second PCEF entity first obtains the policy and the meter.
  • the fee rule, and the bearer is established with the UE, and then the gate is opened, and the service data flow of the current service of the UE is continuously controlled according to the obtained policy and charging rule, so that the effect of the service can be guaranteed.
  • FIG. 1 is a schematic view showing the basic structure of a first embodiment of the system of the present invention
  • FIG. 2 is a schematic diagram showing the basic structure of a second embodiment of the system of the present invention.
  • FIG. 3 is a schematic diagram showing the basic structure of a third embodiment of the system of the present invention.
  • Figure 4 is a flow chart of the solution of the present invention.
  • FIG. 5 is a schematic diagram of a message flow according to Embodiment 1 of the method of the present invention.
  • FIG. 6 is a schematic diagram of a message flow of a second embodiment of a method according to the present invention.
  • FIG. 7 is a schematic diagram of a message flow of a third embodiment of the method in the present invention. Mode for carrying out the invention
  • the system for implementing policy and charging control of the present invention includes at least a first PCEF entity and a second PCEF entity.
  • the first PCEF entity is configured to control, according to a policy and a charging rule, a service data flow of a current service of a UE within a control range thereof;
  • the second PCEF entity is configured to enter the first time when the UE controls the range from the first PCEF entity
  • the policy and the charging rule are obtained, and the service data flow of the current service of the UE is controlled according to the obtained policy and the charging rule.
  • the second PCEF may obtain the policy and the charging rule in multiple ways.
  • the policy and the charging rule may be obtained from the first PCEF entity, or may be obtained by using the PCRF entity. And billing rules.
  • the specific obtaining process can also be implemented in multiple manners.
  • the first PCEF entity can send a rule notification carrying the policy and the charging rule to the second PCEF entity.
  • the second PCEF entity obtains policy and charging rules from the rule notification message.
  • the second PCEF entity sends a rule request message to the first PCEF entity, and obtains a policy and charging rule from the returned rule notification message.
  • the first PCEF entity After receiving the rule request message from the second PCEF entity, the first PCEF entity sends the rule request message to the second PCEF.
  • the entity returns a rule notification message carrying policy and charging rules.
  • the PCRF entity of the system is configured to receive a rule request message carrying the address information of the second PCEF entity from the first PCEF entity, according to the address information of the second PCEF entity. Establishing a session with the second PCEF entity, and transmitting the policy and charging rule saved in itself to the second PCEF entity by using a rule notification message; the first PCEF entity further for using the rule of the address information carrying the second PCEF entity The request message is sent to the PCRF; the second PCEF entity is further configured to establish a session with the PCRF and receive a rule notification message from the PCRF.
  • the PCRF entity is configured to receive a rule request message from a second PCEF entity, establish a session with the second PCEF entity according to the address information of the second PCEF entity, and save the The policy and charging rule in the self is sent to the second PCEF entity by using the rule notification message.
  • the second PCEF entity is further configured to send a rule request message to the PCRF, establish a session with the PCRF, and receive the carried policy and the meter from the PCRF. The rule notification message for the fee.
  • the system further includes a mobility management function entity;
  • the PCRF is configured to receive a rule request message carrying the second PCEF entity address information from the mobility management function entity, establish a session with the second PCEF according to the second PCEF address information, and Transmitting the saved policy and the charging rule to the second p CEF by using the rule notification message;
  • the mobility management function entity is configured to send the address information of the second PCEF entity to the second PCEF entity directly or through another network element by using the rule request message
  • the second PCEF entity is further configured to establish a session with the PCRF, and receive a rule notification message carrying the policy and charging rules from the PCRF.
  • system may further include an online charging system (OCS) for receiving the remaining credit value of the UE returned from the first PCEF, and allocating the available credit value according to the total remaining credit value of the UE and returning to the a second PCEF entity; the second PCEF entity controls the service data flow of the current service of the UE according to the available credit value.
  • OCS online charging system
  • Figure 1 shows the basic structure of the first embodiment of the system.
  • the embodiment includes: a first PCEF entity 101, a second PCEF entity 102, a PCRF entity 103, a mobility management function entity 104, and an OCS 105. among them,
  • the first PCEF entity 101 is configured to receive a handover trigger message sent by the mobility management function entity 104, and the handover trigger message sends a rule request message to the PCRF entity 103, and receives the returned rule request response message; Charge the rule, and send the corresponding MIP/PMIP message or correspondingly delete and 7 between the UE, and return the UE remaining credit value to the OCS entity 105, and send a handover execution request message to the PCRF entity 103, A handover trigger response message is returned to the mobility management function entity 104.
  • the second PCEF entity 102 is configured to receive a rule request response message carrying a policy and charging rule from the PCRF entity 103, and send a credit value request to the OCS entity 105 after receiving the handover indication message sent by the PCRF entity 103.
  • the message receives the returned credit value request message, sends a corresponding MIP/PMIP message or establishes a bearer with the UE, and controls the service data flow of the current service of the UE according to the obtaining policy and the charging rule.
  • the PCRF entity 103 is configured to receive a rule request message from the first PCEF entity 101, formulate a policy and charging rule, and send the rule notification message to the second PCEF entity 102, and also to send to the second PCEF entity 102. Switch the indication message.
  • the mobility management function entity 104 is configured to send a handover trigger message and a handover execution trigger message to the first PCEF entity 101 directly or via other network elements, and receive the returned handover trigger response message and the handover execution trigger response message.
  • the mobility management function entity 104 When the UE enters the second PCEF entity 102 control range from the first PCEF entity 101 control range, the mobility management function entity 104 first sends a handover trigger message to the first PCEF entity 101 directly or via other network elements, the first PCEF entity 101 Sending a rule request message to the PCRF entity 103, the PCRF entity 103 formulates a policy and charging rule according to the information carried in the rule request message, and sends the policy and charging rule to the second PCEF entity 102. The second PCEF entity 102 then establishes a bearer with the UE, and moves to the mobility.
  • the management function entity 104 returns a handover trigger response message; the first PCEF entity 101 sends a handover execution trigger message to the mobility management function entity 104, the first PCEF deletes the policy and charging rules and sends a corresponding MIP/PMIP message or corresponding deletion and UE
  • the bearer between the UEs and the remaining credit value of the UE is returned to the OCS entity 105.
  • the first PCEF entity 101 sends a handover execution request message to the PCRF entity 103, and the PCRF entity 103 sends a handover indication message to the second PCEF entity 102, the second PCEF.
  • the entity obtains the allocated available credit value from the OCS entity 105, it sends the corresponding MIP/PMIP message or establishes with the UE. Bearer, and according to the obtained policy and charging rules
  • the service data flow of the current service of the UE is controlled.
  • FIG. 2 shows a schematic diagram of the system structure of the second embodiment of the system. As shown in FIG. 2, this embodiment includes a first PCEF entity 201, a second PCEF entity 202, a PCRF entity 203, a mobility management function entity 204, and an OCS 205. among them,
  • the first PCEF entity 201 is configured to receive a handover execution message from the PCRF entity 203, and return a handover execution response message, delete a policy and a charging rule, and send a corresponding MIP PMIP message or correspondingly delete and bear between the UEs. The remaining credit value of the UE is returned to the OCS entity 205.
  • the second PCEF entity 202 is configured to receive a rule notification message carrying a policy and a charging rule from the PCRF entity 203, obtain an available credit value from the OCS entity 205, and send a corresponding MIP/PMIP message or establish with the UE.
  • the bearer controls the service data flow of the current service of the UE according to the obtained policy and charging rule.
  • the PCRF entity 203 is configured to receive a rule request message from the mobility management function entity 204, send a handover execution message to the first PCEF entity 201, execute a policy and a charging rule, and send the rule notification message to the second PCEF entity 202.
  • the mobility management function entity 204 is configured to send a rule request message to the PCRF entity 203, and receive the returned rule request response message.
  • the OCS entity 205 is configured to receive a UE residual credit value from the first PCEF entity 201, and send the allocated available credit value to the second PCEF entity 202.
  • the mobility management function entity 201 sends a rule request message to the PCRF entity 203, and the PCRF entity 203 sends a handover execution message to the first PCEF entity 201,
  • a PCRF entity 201 deletes the policy and charging rules and sends a corresponding MIP/PMIP message or correspondingly deletes the bearer between the UE and returns the remaining credit value of the UE to the OCS entity 205,
  • the backward PCRF entity 203 sends a handover execution response message; the PCRF entity 203 formulates a policy and charging rule and sends it to the second PCEF entity 202; the second PCEF entity 202 obtains the available credit value from the OCS entity 205, and then transmits the corresponding
  • the MIP/PMIP message is used to establish a bearer with the UE, and controls the service data flow of the current service of the UE according to the obtained policy and charging rule.
  • FIG. 3 is a schematic diagram showing the system structure of the third embodiment of the system. As shown in FIG. 3, this embodiment includes a first PCEF entity 301, a second PCEF entity 302, a PCRF entity 303, and a mobility management function entity 304.
  • the first PCEF entity 301 is configured to receive a rule request message from the second PCEF entity 302, and return the saved policy and charging rule to the second PCEF entity 302. Also used to receive the mobility management After the handover execution trigger message sent by the function entity 304, the corresponding MIP/PMIP message is sent or the bearer between the UE and the UE is correspondingly deleted, and a handover indication message is sent to the second PCEF entity.
  • the second PCEF entity 302 is configured to receive a handover trigger message from the mobility management function entity 304, send a rule request message to the first PCEF entity, and receive the returned policy and charging rule; send the handover preparation to the PCRF entity 303.
  • the notification message notifies the PCRF entity 303 of the information about the PCEF transmission handover; and is also used to send a corresponding MIP/PMIP message or establish a bearer with the UE, and control the service data flow of the current service of the UE according to the obtained policy and charging rule. .
  • the PCRF entity 303 is configured to receive a handover preparation notification message from the second PCEF entity 302, and save information about the handover of the carried PCEF.
  • the mobility management function entity 304 is configured to send a handover trigger message to the second PCEF entity 302 directly or via other network elements, and send a handover execution trigger message to the first PCEF directly or via other network elements.
  • the mobility management function entity 304 sends a handover trigger message to the second PCEF entity 302 directly or via other network elements
  • the second PCEF entity 302 sends a rule request message to the first PCEF entity 301
  • the first PCEF entity 301 returns its saved policy and charging rule to the second PCEF entity 302
  • the second PCEF entity 302 switches the PCEF by switching the preparation notification message.
  • the first PCEF deletes its own rule and sends a corresponding MIP PMIP message or correspondingly deletes the bearer between the UE and the second
  • the PCEF entity 302 sends a handover indication message; the second PCEF sends a corresponding MIP/PMIP message or establishes a bearer with the UE, and controls the service data flow of the current service of the UE according to the obtained policy and charging rule.
  • the system for implementing policy and charging control according to the present invention is a logical structure system.
  • the first PCEF entity and the second PCEF may be in an existing General Packet Radio Servier (GPRS) network.
  • GPRS General Packet Radio Servier
  • MIP Mobile IP
  • SGSN General Packet Radio Servier
  • HA Home Agent
  • MIP Mobile IP
  • PMA Proxy Mobile Agent
  • PMIP Proxy MIP
  • the mobility management function entity can be supported by two GPRS service support nodes in the GPRS network (SGSN, Serving GPRS Support Node) can also be implemented by two interoperable mobility management entities (MME, Mobility Managem) in the future evolution network. Entity), or mobile IP, FA, PMA in proxy mobile IP, or 3GPP authentication, authorization and accounting proxy/server (3GPP AAA) Proxy/Server, Authentication, Authorisation and Accounting);
  • MME Mobility Managem
  • the present invention also proposes a method for implementing policy and charging control in a communication system for the proposed system for implementing policy and charging control.
  • the second PCEF entity acquires the policy and charging rule, and controls the service data flow of the current service of the UE instead of the first PCEF entity.
  • Figure 4 shows a flow chart of the invention. As shown in FIG. 4, when the UE enters the second PCEF entity control range from the first PCEF entity control range, the method for implementing the policy and charging rule of the present invention includes the following steps:
  • Step 401 The second PCEF entity obtains a policy and charging rule.
  • the second PCEF entity has many methods for obtaining policy and charging rules, and can be roughly divided into two types of methods:
  • the first method is to obtain the policy and charging rules from the first PCEF entity.
  • the method is suitable for the network information related to the policy charging rule in the network where the first PCEF entity is located, and the network of the second PCEF entity.
  • the same situation is established for the network information related to the policy charging rules.
  • the network information related to the policy charging rule described herein includes information such as an IP access type and a wireless access technology. That is, the second PCEF entity will perform the same policy and charging rules as the first PCEF entity, and there is no need to re-define the policy and charging rules suitable for the second PCEF entity by the PCRF entity. .
  • the present invention abbreviates the network information related to the policy charging rule in the network where the first PCEF entity is located as the original network information, and the network of the second PCEF entity
  • the network information tube associated with the policy charging rules is called new network information.
  • the method for the second PCEF entity to obtain the policy and the charging rule from the first PCEF entity may be: the first PCEF entity sends a rule notification message carrying the policy and the charging rule to the second PCEF entity, and the second PCEF entity directly reports from the rule
  • the method for obtaining the policy and the charging rule in the message; the method for the second PCEF entity to obtain the policy and the charging rule from the first PCEF entity may also be: the second PCEF entity sends a rule request message to the first PCEF entity, where the first PCEF entity The second PCEF entity returns a rule notification message carrying the policy and charging rules, and the second PCEF entity obtains the policy and charging rules from the rule notification message.
  • the second method is to obtain the policy and charging rules from the PCRF entity.
  • the method is generally applicable to the case where the new network information is different from the original network information.
  • the network where the first PCEF entity is located is GPRS
  • the network where the second PCEF entity is located is I-WLAN.
  • the PCRF entity needs to re-define the policy and charging rules according to the new network information, and control the service data flow of the current service of the UE.
  • the method for the second PCEF entity to obtain the policy and the charging rule from the PCRF entity may be: the first PCEF entity or the mobility management function entity sends a rule request message to the PCRF entity, where the rule request message carries the obtained second The address information and the new network information of the PCEF entity, the PCRF entity formulates a policy and charging rule according to the new network information, establishes a session with the second PCEF entity according to the address information of the second PCEF entity, and then formulates the policy through the rule notification message. And charging rules are sent to the second PCEF entity;
  • the second PCEF entity sends a rule request message to the PCRF entity, where the rule request message carries new network information, the PCRF entity formulates a policy and charging rule according to the new network information, and then formulates the policy by using the rule notification message. And the charging rule is sent to the second PCEF entity.
  • the second PCEF entity can still obtain the policy and charging rules from the PCRF entity.
  • the method of this situation Different from the second type of method, the first PCEF entity, the second PCEF entity, or the mobility management function entity does not include new network information in the rule request message sent by the PCRF entity. That is to say, the PCRF entity does not need to re-define the policy and charging rules, but only sends the already formulated policy and charging rules to the second PCEF entity.
  • the policy and charging rules described herein are related to the first PCEF. The policies and charging rules in the entity are the same.
  • the specific implementation is as follows: The first PCEF entity or the mobility management function entity sends a rule request message carrying the address information of the second PCEF entity to the PCRF entity, and the PCRF establishes a session with the second PCEF entity according to the address information of the second PCEF entity. And then sending the corresponding policy and charging rule to the second PCEF entity by using the rule notification message;
  • the second PCEF entity sends a rule request message to the PCRF entity, and the PCRF sends the corresponding policy and charging rule to the second PCEF entity by using the rule notification message.
  • the mobility management function entity When the UE enters the second PCEF entity control range from the control range of the first PCEF entity, the mobility management function entity itself may determine the address information and the new network information of the second PCEF entity, and may also obtain and determine from the access side of the network. Address information and new network information of the second PCEF entity.
  • the method for determining the address information of the second PCEF entity and the network information of the network where the second PCEF entity is located is related to the policy-based charging rule, and is not described here.
  • how the PCRF entity formulates policies and charging rules according to the network information related to the policy charging rules is also a prior art, and will not be described here.
  • the address information of the second PCEF entity and the network of the second PCEF entity may be directly or through other handover control messages.
  • the network information related to the fee rule is sent to the first PCEF entity or the second PCEF entity, and the first PCEF entity or the second PCEF entity may send a rule request message to the PCRF entity.
  • the mobility management function entity can directly directly address the address information and the new network information of the second PCEF entity. Send to the PCRF entity.
  • Step 402 The second PCEF entity controls the service data traffic of the current service of the UE according to the obtained policy and charging rule.
  • the PCEF can identify the service data flow (SDF, Service Data Flow) of the current service of the UE according to the policy and charging rules, which is generally implemented by using a service data flow template (SDF Template) in the policy and charging rules. After identifying the service data flow of the current service of the UE, the PCEF can perform policy and charging control on the service data flow according to the corresponding control indication in the policy and the charging rule.
  • These controls generally include operations such as QoS control, gating, and charging control.
  • the QoS control refers to the maximum bit rate (MBR) and guaranteed bit rate (GBR) of the upstream and downstream data streams identified by the PCEF for the policy and charging rules.
  • the gate operation refers to the PCEF constructing multiple gates according to the service data flow template information, and opening or closing the gate according to the requirements of the application layer or the policy control. If gate is enabled, PCEF will pass the service data flow corresponding to gate; if gate is closed, PCEF will discard the data packet.
  • the first PCEF entity may delete its own policy and charging rules before the second PCEF entity acquires the policy and charging rules, and may also delete its own policy and charging rules after the second PCEF entity obtains the policy and charging rules. .
  • the first PCEF entity deletes the policy and the charging rule
  • the corresponding MIP/PMIP message needs to be sent or the bearer between the first PCEF entity and the UE is deleted, and the network resources occupied by the bearers are released.
  • the second PCEF entity may send a corresponding MIP/PMIP message or establish a bearer with the UE, and then control the service data flow of the current service of the UE according to the obtained policy and charging rule. .
  • the system may adopt an offline charging method or an online charging method.
  • the PCRF entity can be sent to the PCEF policy and
  • the charging rule includes an offline charging indication
  • the PCEF performs offline charging on the service data flow identified by the policy and the charging rule according to the offline charging indication, which is implemented as follows:
  • the PCEF performs statistics on the time and traffic of the service data flow. That is, the UE uses the service to collect statistics, and after the UE ends using the service, the statistics are sent to the offline charging system (OFCS), and the OFCS performs charging processing according to the statistical result.
  • OFCS offline charging system
  • the PCRF entity may include an online charging indication in the policy charging rule sent to the PCEF, and the PCEF performs online charging according to the online charging indication for the service data flow identified by the policy and the charging rule.
  • the implementation is as follows: The PCEF first requests the available credit value of the UE from the OCS, and then records the remaining credit value of the UE in real time according to the situation in which the UE uses the service.
  • the available credit values described herein reflect the network resources that the UE can use at the current billing price.
  • the available credit value reflects the duration that the UE can receive or send the service data stream; if it is based on the traffic charge, the available credit value reflects the traffic that the UE can receive or send the service data stream.
  • the online charging method after the first PCEF entity deletes its own policy and charging rules, the first PCEF entity needs to send the remaining credit value recorded in real time according to the situation in which the UE uses the service to the OCS, when the second When the PCEF entity requests the credit value from the OCS, the OCS re-occupies the remaining credit value to allocate the available credit value to the second PCEF entity and sends it to the second PCEF entity; the second PCEF entity determines whether the UE has the right according to the available credit value. The service is used, and if so, the service data flow control is performed on the UE.
  • the original network information is different from the new network information
  • the PCRF entity needs to re-define the policy and charging rules according to the network information suitable for the network where the second PCEF entity is located.
  • the second PCEF entity obtains the policy and charging rules.
  • the first PCEF entity sends a rule request message to the PCRF entity, and the PCRF entity formulates a policy and charging rule according to the rule-related network information of the network where the second PCEF entity is obtained from the rule request message, and sends the policy and charging rule to the second PCEF entity.
  • the first PCEF entity deletes its own policy and charging rules after the second PCEF entity acquires the policy and charging rules.
  • the system adopts the online charging mode. Before the PCEF handover, the first PCEF entity uses the service according to the UE. The situation records the remaining credit value of the UE in real time and returns it to the OCS. .
  • Fig. 1 is a schematic view showing the structure of the system of the present embodiment
  • Fig. 5 is a view showing the flow of the message of the embodiment.
  • Step 501 The mobility management function entity directly or via another network
  • the unit sends a handover trigger message to the first PCEF entity, where the handover trigger message carries the address information of the second PCEF entity and the new network information.
  • the mobility management function entity may also send a PCEF handover trigger message to the second PCEF entity or the PCRF entity.
  • a PCEF handover trigger message may be sent to the second PCEF entity or the PCRF entity.
  • the handover trigger message may be directly sent through the mobility management function entity or directly through other networks.
  • the unit sends the first PCEF entity or the second PCEF entity to switch the trigger message to trigger the PCEF or the second PCEF entity to send a rule request message to the PCRF entity.
  • the mobility management function entity may also send the address information and the new network information of the second PCEF entity by using the bearer setup request message directly or via other network elements.
  • the packet is sent to the second PCEF entity.
  • the bearer setup request message is equivalent to the handover trigger message.
  • the mobility management function entity may first send the handover trigger message to the first or other network unit.
  • a PCEF entity triggers the first PCEF entity to delete its own policy and charging rules by using a handover trigger message.
  • the mobility management function entity needs to send the rule request message carrying the second PCEF entity address information and the new network information to the PCRF entity, the The rule request message is used as the handover trigger message, and there is no need to send a special handover trigger message.
  • the mobility management function entity sends a handover trigger message is related to a specific scheme. If it needs to be sent, it is sent to an entity that first executes the scheme of the present invention to trigger the entity to perform a subsequent process.
  • Step 502 The first PCEF entity sends a rule request message to the PCRF entity, where the rule request message includes the obtained address information of the second PCEF entity and new network information.
  • Step 503 to step 504 The PCRF entity formulates a policy and a charging rule according to the new network information, and then establishes a session with the second PCEF entity according to the address information of the second PCEF entity, and sends the formulated policy and charging rule by using a rule notification message. Give the second PCEF entity.
  • the PCRF entity may store the first PCEF entity connection information, where the connection information is used to record the correspondence between the PCEF and the UE.
  • the PCRF entity will receive the PCEF update information during the interaction with the first PCEF entity, the second PCEF entity or the mobility management function entity, the PCRF entity According to the PCEF update information, the first PCEF entity saved in advance will be connected.
  • the information is replaced with the second PCEF entity connection information.
  • the policy charging rule changes accordingly, and the PCRF entity can connect to the second PCEF entity according to the record.
  • the changed policy charging rules are accurately sent to the second PCEF entity for execution.
  • the PCEF connection information may be the address information of the PCEF
  • the PCEF update information may include the first PCEF entity address information, the second PCEF entity address information, and the UE identifier.
  • the first PCEF entity address, the second PCEF entity or the mobility management function entity obtains the first PCEF entity address information and the second PCEF entity address information obtained in advance.
  • the UE identifier is sent to the PCRF entity, and the PCRF entity determines the first PCEF entity address information corresponding thereto according to the UE identifier, and replaces the first PCEF entity address information with the second PCEF entity address information.
  • the PCRF entity can also use other methods to record the handover of the PCEF. As long as the new policy and charging rules can be developed, the new policy and charging rules can be accurately sent to the second PCEF entity.
  • the PCRF entity since the PCRF entity needs to send the policy and the charging rule to the second PCEF entity, the PCRF entity can record the PCEF update information when receiving the rule request message.
  • the PCRF entity does not need to formulate a policy and charging rule for the second PCEF entity, the second PCEF entity or the second PCEF needs to be obtained after the second PCEF entity obtains the policy and charging rule from the first PCEF entity.
  • the entity notifies the PCF update information to the PCRF entity, and the PCRF entity replaces the previously saved first PCEF entity connection information with the second PCEF entity connection information according to the PCEF update information.
  • Step 505 to step 507 The second PCEF entity sends a rule notification response message to the PCRF entity, and the PCRF entity sends a rule request response message to the first PCEF entity, and the first PCEF entity sends a handover trigger response message to the mobility management function entity.
  • Step 509 The first PCEF entity deletes its own policy and charging rules.
  • the first PCEF entity also needs to send a corresponding MIP/PMIP message or delete the bearer established between the UE and release the network resource.
  • Step 510 ⁇ Step 511 The first PCEF entity sends the remaining credit value of the UE to the OCS through a credit value notification message, and the OCS returns a credit value response message to the first PCEF entity.
  • Step 512 ⁇ Step 513 The first PCEF entity sends a handover execution request message to the PCRF entity, and the PCRF entity sends a handover indication message to the second PCEF entity.
  • Step 516 The second PCEF entity sends a corresponding MIP/PMIP message or establishes a bearer with the UE, and controls the service data flow according to the obtained policy and charging rule.
  • the steps 501 to 507 are the handover preparation phase.
  • the second PCEF entity obtains the policy and the charging rule, and performs the handover preparation work.
  • the first PCEF entity still performs the service of the UE.
  • Step 509 ⁇ Step 519 is a handover execution phase, and the second PCEF entity controls the service by replacing the first PCEF entity, and continues to charge the UE according to the obtained remaining credit value.
  • Method embodiment two the network information related to the policy and charging decision of the first PCEF entity and the second PCEF entity is different, and the PCRF entity needs to re-define the policy and charging rule suitable for the network where the second PCEF entity is located;
  • the entity obtains the policy and charging rules as follows:
  • the mobility management function entity sends a rule request message to the PCRF entity, the PCRF entity formulates a policy and charging rule, and then sends the formulated policy and charging rule to the first through the rule notification message.
  • Two PCEF entities Two PCEF entities.
  • the system adopts an online charging mode, and records the remaining credit value of the UE in real time according to the situation in which the UE uses the service.
  • Fig. 2 is a view showing the structure of the system of the embodiment
  • Fig. 6 is a view showing the flow of the message of the embodiment.
  • Step 601 The mobility management function entity sends a rule to the PCRF entity.
  • the request message, the rule request carries the address information of the second PCEF entity and the new network information.
  • the mobility management function entity may directly use the rule request message described in this step as a handover trigger message, and does not need to specifically send a handover trigger message.
  • the rule request message described herein may include only the address information of the second PCEF entity.
  • Step 602 After receiving the rule request message, the PCRF entity first sends a handover execution message to the first PCEF entity.
  • Step 603 After receiving the handover execution message, the first PCEF entity deletes its own policy and charging rules.
  • the first PCEF entity also needs to send a corresponding MIP/PMIP message or correspondingly delete the bearer established between the first PCEF entity and the UE and release the network resource.
  • Step 611 The second PCEF entity sends a corresponding MIP PMIP message or establishes a bearer with the UE, and controls the service data flow according to the obtained policy and charging rule.
  • Step 612 ⁇ Step 613 The second PCEF entity returns a rule notification response message to the PCRF entity, and the PCRF entity returns a rule request response message to the mobility management function entity.
  • the PCEF entity deletes its own policy and charging rules, and then performs handover preparation.
  • the second PCEF entity obtains the policy and charging rules, and establishes a bearer with the UE, and controls the service according to the obtained policy and charging rules.
  • the original network information is the same as the new network information, and the PCRF entity does not need to re-define the policy and charging rules.
  • the second PCEF entity obtains the policy and charging rules as follows: The second PCEF entity sends a rule to the first PCEF entity. The request message, the first PCEF entity returns a rule notification message carrying the policy and charging rules to the second PCEF entity, and the second PCEF entity obtains the policy and charging rules from the rule notification message.
  • FIG. 3 is a schematic diagram showing the structure of the system of the embodiment
  • FIG. 7 is a schematic diagram showing the message flow of the embodiment. As shown in FIG.
  • Step 701 The mobility management function entity directly or via another network
  • the unit sends a handover trigger message carrying the first PCEF entity address information to the second PCEF entity.
  • Step 702 ?? Step 703 The second PCEF entity sends a rule request message to the first PCEF entity according to the first PCEF entity address, and the first PCEF entity returns its own policy and charging rule to the second PCEF entity by using the rule notification message.
  • Step 706 The second PCEF entity returns a handover trigger response message to the mobility management function entity.
  • Step 707 The mobility management function entity sends a handover execution trigger message to the first PCEF entity directly or via other network elements.
  • Step 708 The first PCEF entity deletes its own policy and charging rules.
  • the first PCEF entity also sends a corresponding MIP/PMIP message or correspondingly deletes the bearer established with the UE, and releases the network resource.
  • the first PCEF entity performs offline charging on the service data flow of the UE before deleting the own policy and the charging rule, and performs statistics on time and traffic of the service data flow, that is, using the service for the UE. The situation is counted. After the policy and the charging rule are deleted, the first PCEF entity also needs to send the statistics to the OFCS, and the OFCS performs charging according to the statistics, and generates a bill.
  • the first PCEF entity needs to return the remaining credit value of the user to the OCS after deleting the policy and charging rules of the user, and the second PCEF entity obtains the remaining credit value of the user from the OCS.
  • the method and the first embodiment and the second embodiment The online charging method described above is the same and will not be described in detail herein.
  • Step 709 The first PCEF entity sends a handover indication message to the second PCEF entity. If the online charging method is adopted, the OCS may also send a handover indication to the second PCEF entity after the OCS obtains the user residual credit value.
  • Step 710 The second PCEF entity sends a corresponding MIP PMIP message or establishes a bearer with the UE, and controls the service data flow according to the obtained policy and charging rule.
  • the policy and charging rules used by the second PCEF entity are the same policy and charging rules as the first PCEF entity.
  • Step 711 to step 712 The second PCEF entity sends a handover complete notification message to the PCRF entity, and the PCRF entity returns a handover complete notification response message to the second PCEF entity.
  • the second PCEF entity may send the PCEF update information to the PCRF entity by using a handover preparation notification message or a handover completion notification message in step 704 or step 711, and the PCRF entity will record the first PCEF according to the PCEF update information.
  • the entity connection information is replaced with the second PCEF entity connection information.
  • Step 713 to step 714 The second PCEF entity returns a handover indication response message to the first PCEF entity, and the first PCEF entity returns a handover execution response message to the mobility management function entity.
  • steps 701 to 706 are handover preparation phases
  • steps 707 to 714 are handover execution phases.
  • the second PCEF entity first obtains a policy and charging rule from the first PCEF entity, and establishes a bearer with the UE.
  • the second PCEF entity sends a corresponding MIP/PMIP message or establishes a bearer with the UE. And follow The obtained policy and charging rules control the service data flow of the UE.
  • both phases are triggered by the mobility management function entity, and in actual applications, the two phases may not be clearly separated, and are triggered only once by the mobility management function entity.
  • the mobility management function entity may not send a handover execution trigger message to the first PCEF entity, and steps 706 and 707 may be omitted.
  • the sent messages generally appear in pairs, but in actual applications, they may not appear in pairs.
  • the process may be directly ended, and the subsequent response message does not need to be executed, that is, steps 712 to 714 may be omitted.
  • the handover completion notification message may not be sent any more, that is, steps 711 and 712 are omitted.
  • the second PCEF entity may obtain a policy and charging rule for controlling the service data flow of the current service of the UE, instead of The first PCEF entity continues to control the current service of the UE.
  • the second PCEF entity obtains the policy and charging rules
  • the second PCEF entity controls the service data flow by Which entity triggers, whether the PCRF entity needs to formulate policies and charging rules according to the network information related to the policy charging rules of the network where the second PCEF entity is located, how the PCEF update information is sent to the PCRF entity, and the mobility management function entity will switch Which entity is triggered to send the message, whether the handover preparation phase and the handover execution phase are performed separately or in combination, etc. are all related to the specific solution, and can be determined by the user who applies the solution of the present invention, and is not enumerated here.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Meter Arrangements (AREA)

Abstract

Cette invention concerne un système, un dispositif et un procédé permettant de commander des conditions d'utilisation et une facturation. Lorsque UE entre dans le mode de commande de la seconde entité à fonction de commande des conditions d'utilisation et de facturation (PCEF) depuis le mode de commande de la première entité à fonction de commande des conditions d'utilisation et de facturation, la seconde entité PCEF peut obtenir les règles régissant les conditions d'utilisation et la facturation auprès de la première entité PCEF ou la fonction d'application des conditions d'utilisation et de la facturation; la seconde entité PCEF se présente en tant que détenteur avec UE; puis la seconde entité PCEF régule le flux de données de service de UE d'après les règles régissant les conditions d'utilisation et la facturation qui sont déjà acquises. Lorsque UE entre dans le mode de commande de la première entité PCEF, le procédé décrit dans cette invention permet de faire basculer la seconde entité PCEF depuis la première entité PCEF; et la seconde entité PCEF peut remplacer la première entité PCEF pour commander le flux de données en service en cours; ensuite, le procédé décrit dans cette invention permet de commander efficacement le fonctionnement du système.
PCT/CN2007/070513 2006-08-18 2007-08-17 Procédé, dispositif et système de commande de conditions d'utilisation et de facturation WO2008022602A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2006101098587A CN101127694B (zh) 2006-08-18 2006-08-18 一种实现策略和计费控制的系统和方法
CN200610109858.7 2006-08-18

Publications (1)

Publication Number Publication Date
WO2008022602A1 true WO2008022602A1 (fr) 2008-02-28

Family

ID=39095622

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070513 WO2008022602A1 (fr) 2006-08-18 2007-08-17 Procédé, dispositif et système de commande de conditions d'utilisation et de facturation

Country Status (2)

Country Link
CN (1) CN101127694B (fr)
WO (1) WO2008022602A1 (fr)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101370253B (zh) * 2007-08-15 2011-10-05 华为技术有限公司 一种点对点业务实现方法及通讯系统以及相关设备
CN101447917B (zh) * 2008-03-04 2011-09-21 中兴通讯股份有限公司 策略控制方法和装置
CN101471797B (zh) * 2008-03-31 2012-05-30 华为技术有限公司 决策方法及系统和策略决策单元
CN101296517B (zh) * 2008-04-22 2013-01-23 中国移动通信集团设计院有限公司 异构网络中保证服务质量管理的切换方法、系统及装置
CN101567793A (zh) * 2008-04-25 2009-10-28 华为技术有限公司 Pcc规则更新的方法、装置及系统
CN101572915B (zh) * 2008-04-28 2012-10-17 华为技术有限公司 一种无线网络中实现切换的方法、装置及系统
US8204505B2 (en) * 2008-06-17 2012-06-19 Qualcomm Incorporated Managing network-initiated quality of service setup in mobile device and network
CN101616143B (zh) * 2008-06-23 2012-11-21 华为技术有限公司 策略控制方法、系统、数据网关和策略决策实体
CN101729265B (zh) * 2008-10-25 2013-06-05 华为技术有限公司 在演进的分组系统eps中进行计费的方法、装置和系统
CN101610529B (zh) * 2009-07-16 2012-01-11 中兴通讯股份有限公司 策略控制系统和通信系统中的策略控制方法
EP2296309B1 (fr) * 2009-09-11 2012-10-31 Alcatel Lucent Procédé de fourniture de règles de politique à un utilisateur final, en fonction de son solde de compte et son niveau d'abonnement au service dans un réseau de télécommunication
CN102215469B (zh) * 2010-04-09 2015-01-28 中兴通讯股份有限公司 一种基于网络负荷的策略计费控制方法和系统
CN103067193B (zh) * 2011-10-21 2017-07-14 中兴通讯股份有限公司 一种基于用户感知的网络策略实现方法及系统
CN102726076B (zh) * 2011-12-12 2014-07-30 华为技术有限公司 策略和计费控制方法、实体及系统
CN104219645B (zh) * 2013-05-29 2018-02-06 中国电信股份有限公司 融合在线计费方法与系统
CN106686676B (zh) * 2015-11-06 2020-10-09 华为技术有限公司 一种会话切换的方法、设备及系统
CN109768947A (zh) * 2017-11-09 2019-05-17 中国移动通信有限公司研究院 一种用户身份认证方法、装置和介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1674707A (zh) * 2004-03-24 2005-09-28 华为技术有限公司 一种实现边界漫游计费的方法
US20060008063A1 (en) * 2002-10-15 2006-01-12 Magnus Harnesk System for providing flexible charging in a network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060008063A1 (en) * 2002-10-15 2006-01-12 Magnus Harnesk System for providing flexible charging in a network
CN1674707A (zh) * 2004-03-24 2005-09-28 华为技术有限公司 一种实现边界漫游计费的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Technical Specification Group Service and System Aspects; Policy and Charging control architecture (Release 7)", 3GPP TS 23.203 V1.0.0, May 2006 (2006-05-01) *

Also Published As

Publication number Publication date
CN101127694B (zh) 2011-04-20
CN101127694A (zh) 2008-02-20

Similar Documents

Publication Publication Date Title
WO2008022602A1 (fr) Procédé, dispositif et système de commande de conditions d'utilisation et de facturation
US20070185809A1 (en) Method and system for processing online charging
WO2011006317A1 (fr) Procédé et système permettant d'effacer des informations redondantes d'une fonction d’imputation et de règles domestique
WO2012058998A1 (fr) Procédé de commande de politique et de facturation soutenant une mobilité de flux ip dans un scénario d'itinérance
WO2007143940A1 (fr) procédé, système et équipement de contrôle des conditions d'utilisation et de la facturation lorsque l'utilisateur est mobile
WO2010108356A1 (fr) Procédé de chargement, système et procédé de rapport pour accès à un terminal par le biais de réseaux à accès multiple
WO2009021462A1 (fr) Procédé et dispositif d'établissement de session ip-can
WO2009059544A1 (fr) Procédé, dispositif et système permettant de mettre en œuvre la commutation entre des réseaux
WO2006015548A1 (fr) Methode de traitement fondee sur un evenement de declenchement de chargement et sur un evenement de reautorisation de flux de donnees de paquets
WO2011029289A1 (fr) Procédé et système de transmission d'un mode de commande de support dans des scénarios d'itinérance
WO2013060170A1 (fr) Procédé et dispositif de fourniture de support de facturation basé sur un support lipa
CN101001402B (zh) 移动通信系统及使用归属网络应用功能业务的方法
WO2011026385A1 (fr) Procédé et système de facturation en ligne dans des scénarios d'itinérance à raccordement local
WO2014094488A1 (fr) Procédé et dispositif de gestion de politique de facturation destinés à un service local d'itinérance
WO2014107985A1 (fr) Procédé de facturation en ligne de services d'itinérance locale, h-ocs et v-ocs
WO2011085620A1 (fr) Procédé et système de mise en œuvre d'un contrôle de qualité de service
WO2009138016A1 (fr) Procédé, appareil et système de transmission d’information
WO2012129992A1 (fr) Procédé de traitement de connectivité de données sponsorisées, et fonction d'imputation et de règles
WO2010118673A1 (fr) Procédé, système et dispositif de gestion du contrôle des règles d'utilisation et de facturation
WO2010066157A1 (fr) Procédé de facturation, dispositif de facturation, passerelle de facturation et système de facturation
WO2012041150A1 (fr) Procédé de contrôle de l'utilisation du volume de ressources et fonction de règles de contrôle de politique et de taxation
WO2012155774A1 (fr) Procédé, système d'établissement d'une sous-session s9, et fonction "règles de politique et de facturation"
US20110082776A1 (en) Credit authorization in a core network
WO2011026409A1 (fr) Procédé, appareil et système de mise à jour de session
WO2007079682A1 (fr) Procédé et système utilisant la commande de politique et de facturation du service de la fonction d'application

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: 07800989

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07800989

Country of ref document: EP

Kind code of ref document: A1