+

WO2009030136A1 - Procédé et système pour distribuer une stratégie et entité de distribution de stratégie - Google Patents

Procédé et système pour distribuer une stratégie et entité de distribution de stratégie Download PDF

Info

Publication number
WO2009030136A1
WO2009030136A1 PCT/CN2008/072008 CN2008072008W WO2009030136A1 WO 2009030136 A1 WO2009030136 A1 WO 2009030136A1 CN 2008072008 W CN2008072008 W CN 2008072008W WO 2009030136 A1 WO2009030136 A1 WO 2009030136A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
entity
distribution
enforcement
execution
Prior art date
Application number
PCT/CN2008/072008
Other languages
English (en)
Chinese (zh)
Inventor
Shibi Huang
Fengbo Wang
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 WO2009030136A1 publication Critical patent/WO2009030136A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • the present invention relates to mobile communication technologies, and in particular, to a method, system and policy distribution entity for distributing policies. Background technique
  • a policy refers to a rule for processing a business data stream, such as controlling the passage of a service data stream.
  • QoS Quality of Service
  • the network side needs to distribute the policies so that the conducted business data flows conform to the processing rules.
  • the User Equipment UE is establishing an IP connectivity access network.
  • IP Connectivity Access Network, IP-CAN IP Connectivity Access Network
  • the QoS parameter information is carried in the IP-CAN bearer request sent to the network side, and the network side receives the IP-CAN bearer setup request, according to the The UE's subscriber subscription information and device processing capabilities determine the QoS that it can use and send the QoS to the UE. In this way, the UE can perform service data transmission according to the QoS distributed by the network side.
  • the network side will distribute the default QoS or the user subscription QoS of the UE.
  • the QoS used by the UE may be different from the QoS required for the performed service, especially for services with higher real-time requirements, which may not meet the transmission requirements.
  • the IP-CAN in the above refers to the IP continuous access network.
  • the UE changes position or roams within the IP-CAN, it can still maintain IP service continuity without interrupting the IP-CAN.
  • the General Packet Radio Service (GPRS) network the Interworking Wireless Local Area Network (I-WLAN) network, and the Worldwide Interoperability for Microwave Access (WIMAX) network.
  • GPRS General Packet Radio Service
  • I-WLAN Interworking Wireless Local Area Network
  • WIMAX Worldwide Interoperability for Microwave Access
  • Etc. belong to IP-CAN.
  • An IP-CAN bearer refers to an IP transmission path with a clear rate, delay, and bit error rate, for example, a Packet Data Protocol (PDP) context for a GPRS network.
  • PDP Packet Data Protocol
  • multiple IP-CAN carriers may be located in the same IP-CAN session, which refers to the connection relationship between the UE and a packet data network (such as the Internet).
  • the policy-related entities are located in the Policy and Charging Control (PCC) system.
  • Figure 1 shows a block diagram of the policy-related entities in the PCC system.
  • a Policy Control and Charging Rules Function (PCRF) 101 a Policy and Charging Enforcement Function (PCEF) 102, and a user subscription information database (Subscription) are included.
  • PCRF Policy Control and Charging Rules Function
  • PCEF Policy and Charging Enforcement Function
  • Subscription user subscription information database
  • the PCRF 101 determines the corresponding policy according to the restriction of the user access network, the operator policy, the user subscription data acquired from the SPR 103, and the current service information of the UE acquired by the AF 104, and provides the policy to the PCEF. 102.
  • the PCEF 102 performs the policy that is sent or specified by the PCRF 101, and includes the detection and measurement of the service data flow, the QoS of the service data flow, the user plane traffic processing, and the session management of the trigger control plane.
  • SPR 103 providing user subscription information to PCRF 101.
  • the AF 104 dynamically provides session information of the application layer to the PCRF 101, and the PCRF 101 dynamically generates or modifies the corresponding rule according to the information.
  • the Rx reference point, the AF 104 sends application layer related information through the reference point, where the information includes but is not limited to an IP filter, which is used to identify the bandwidth information required by the service data stream, the application or the media, and the reference point can use the Internet project.
  • IP filter which is used to identify the bandwidth information required by the service data stream, the application or the media
  • the reference point can use the Internet project.
  • Diameter protocol defined by the Internet Engineering Task Force (IETF).
  • the Gx reference point through which the PCRF 101 can dynamically control the PCC rules executed on the PCEF 102. Specifically, the reference point implements the following functions: establishment, maintenance And terminating the IP-CAN session; PCEF 102 requests PCC rules from PCRF 101; PCRF 101 provides PCC rules to PCEF 102; negotiates IP-CAN bearer setup mode.
  • This reference point can use the Diameter protocol defined by the IETF.
  • the S reference point through which the PCRF 101 requests the SPR 103 for user subscription information which is used to determine the IP-CAN transport layer policy.
  • the interface is currently a private interface, which is customized by the device vendor and is not publicized.
  • FIG. 2 shows a flow diagram of a terminal request triggering a distribution policy. As shown in Figure 2, the following steps are included:
  • Step 201 The PCEF receives the UE-initiated IP-CAN session establishment request message.
  • Step 203 The PCRF stores the information in the Diameter CCR message, performs PCC decision, and generates a policy.
  • Step 204 The PCRF returns the policy to the PCEF through a Diameter CCA message.
  • Step 205 The PCEF loads and executes the policy.
  • Step 206 The PCEF returns an IP-CAN session response message to the UE.
  • FIG. 3 shows a flow chart of the PCRF active delivery policy.
  • the method includes the following steps: Step 301: After the AF receives a trigger event (such as the UE initiated multimedia call control signaling), the AF needs to establish a new Diameter session and provide service information to the PCRF.
  • a trigger event such as the UE initiated multimedia call control signaling
  • 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 triggering event, and sends the information to the PCRF through the Diameter AAR message.
  • 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 PCRF performs PCC decision and generates a policy.
  • Step 304 The PCRF sends the PCC rule to the PCEF through a Diameter Re-Auth-Request (RAR) message.
  • RAR Diameter Re-Auth-Request
  • Step 305 The PCEF executes the policy.
  • Step 306 The PCEF returns a Diameter Re-Author Answer (RAA) message to the PCRF.
  • RAA Diameter Re-Author Answer
  • Non-3GPP non-3GPP networks
  • WIMAX Wide Area Network
  • WLAN Wireless Fidelity
  • CDMA Code Division Multiple Access
  • FIG. 4 shows a block diagram of a PCC in a non-3gpp network.
  • PCEFs in the public data network gateway (PDN-GW, P-GW), Serving-Gateway (S-GW) and non-3gpp networks.
  • PDN-GW public data network gateway
  • S-GW Serving-Gateway
  • non-3gpp networks These PCEFs receive PCRF through the Gx extension interface.
  • the policies issued including vPCRF and hPCRF), that is, the PCRF needs to distribute the policy among these PCEFs.
  • a policy distribution architecture is proposed in WIMAX.
  • PCEF policy enforcement points
  • C-PCEF connection service network PCEF
  • A-PCEF access service network PCEF
  • C-PCEF as an anchor point PCEF can be located on the Home Agent (HA) of the Connection Service Network (CSN) in the WiMAX network, and implement some of the user's policies such as billing and gating.
  • the A-PCEF is located in the Access Service Network (ASN) of the WIMAX network and implements some of the user's policies, such as QOS.
  • PDF Policy Distribution Function
  • the PDF can be located at the anchor point or PCRF.
  • FIG. 6 shows a block diagram of a PCC in a 3GPP2 network.
  • the PCC architecture of 3GPP2 there are two policy enforcement points, local mobility at the anchor point, Local Mobility Anchor (LMA) /HA, and Access Gateway (AGW). ).
  • LMA Local Mobility Anchor
  • AGW Access Gateway
  • PCRF requires policy distribution between the two policy enforcement entities.
  • FIG. 7 is a diagram of a policy distribution architecture.
  • Figure 8 is a diagram of a policy distribution architecture in the case of roaming.
  • the policy server such as PDF in PCR, PCRF, PCRF in 3GPP2
  • Different policies of the traffic data flow are distributed to multiple policy enforcement points (eg, A-PCEF and C-PCEF in WiMAX, HA and Traffic Plane Function (TPF) in 3GPP2).
  • the charging and gating policy is distributed to the policy enforcement entity 1, the QoS policy is distributed to the policy enforcement entity 2, and the roaming is distributed through the Gx extension interface and the S9 interface (roaming interface).
  • the PDP in the figure is the Policy Decision Point
  • the PEP is the Policy Enforcement Point
  • the NPR is the Network Policy Repository.
  • An object of the embodiments of the present invention is to provide a method, a system, and a policy distribution entity for distributing a policy, so that the policy server distributes different policies to the corresponding policy execution entity.
  • the embodiment of the present invention provides a method, system, and policy distribution entity for distributing a policy, such as:
  • a method of distributing a policy including:
  • the policy distribution entity learns the policy and knows the policy execution capability of the policy enforcement entity, where the policy refers to a processing rule for the service data flow; and the policy execution entity is supplied.
  • a system for distributing policies including a policy server, a policy distribution entity, and a policy enforcement entity, where
  • the policy server is used to send a policy to the policy distribution entity
  • the policy distribution entity receives the policy sent by the policy server and learns the policy enforcement entity Policy execution capability; if the policy enforcement entity has policy enforcement capability, the policy distribution entity provides a corresponding one of the policies to the policy enforcement entity according to the policy execution capability of the policy enforcement entity;
  • the policy enforcement entity is configured to report a policy execution capability or an entity type, and receive a corresponding policy that the policy server distributes according to the reported policy execution capability or entity type.
  • a policy enforcement entity of a distribution policy comprising: a receiving unit and a reporting unit, wherein the reporting unit is configured to report a policy execution capability or an entity type of the policy execution entity;
  • a receiving unit configured to receive, according to the policy enforcement capability of the reported policy enforcement entity or a corresponding policy of the entity type distribution.
  • a policy distribution entity of a distribution policy comprising: an obtaining unit and a distribution unit, wherein the obtaining unit is configured to learn a policy execution capability of the policy executing entity;
  • a distribution unit configured to provide a related policy to the corresponding policy enforcement entity according to the policy enforcement capability of each policy enforcement entity configured on the configuration unit.
  • the policy distribution entity learns all the policies, and learns the policy execution capability of each policy enforcement entity, so as to provide a corresponding policy to each policy execution entity according to the policy execution capability of each policy enforcement entity. In this way, different policies are distributed to the corresponding policy enforcement entities.
  • FIG. 1 is a block diagram of a policy-related entity in a prior art policy and charging control system
  • FIG. 3 is a flow chart of a policy and charging execution entity actively issuing a policy in the prior art
  • FIG. 4 is a block diagram of a policy and charging control system in a prior art microwave access global interworking network
  • FIG. 7 is a schematic diagram of a policy distribution architecture in the prior art
  • 8 is a schematic diagram of a policy distribution architecture in a roaming situation in the prior art Non-3GPP/3GPP2;
  • FIG. 10 is a flowchart of a first embodiment of a first method embodiment of the present invention
  • FIG. 11 is a flowchart of a second embodiment of the first method embodiment of the present invention
  • FIG. 12 is a first method of the present invention
  • FIG. 13 is a flowchart of a complete embodiment 4 corresponding to the first method embodiment of the present invention
  • FIG. 14 is a block diagram of a first system embodiment of the present invention
  • Figure 15 is a block diagram of a policy server corresponding to the first system embodiment of the present invention
  • Figure 16 is a block diagram of a second system embodiment of the present invention
  • FIG. 17 is a block diagram of a policy server corresponding to a second system embodiment of the present invention.
  • FIG. 18 is a block diagram of a third system embodiment of the present invention.
  • Figure 19 is a block diagram of a policy enforcement entity corresponding to a third system embodiment of the present invention.
  • Figure 20 is a block diagram of a fourth system embodiment of the present invention.
  • Figure 21 is a block diagram of a visited location policy server corresponding to the fourth system embodiment of the present invention.
  • FIG. 23 is a flowchart of a complete embodiment of a second method embodiment of the present invention
  • FIG. 24 is a block diagram of a corresponding system according to a second method embodiment of the present invention.
  • the embodiment of the present invention provides an embodiment of a method for distributing a policy.
  • the policy distribution entity learns all the policies, and obtains the policy execution capability of each policy enforcement entity, so as to provide a corresponding policy to each policy execution according to the policy execution capability of each policy enforcement entity. entity.
  • Step 901 The policy server acquires a policy execution capability of the policy execution entity.
  • the policy server needs to obtain the policy execution capability of each policy enforcement entity, which can be implemented in the following ways:
  • Manner 1 Configure the policy enforcement capabilities of each policy enforcement entity or the type of each policy enforcement entity on the policy server.
  • the policy enforcement entity 1 and the policy enforcement entity 2 are respectively configured, the policy enforcement entity 1 is used to execute the charging and gating policies, and the policy enforcement entity 2 is used to execute the QoS policy.
  • the charging policy execution capability and the gated policy execution capability of the policy enforcement entity 1 can be configured on the policy server, and the QoS policy execution capability of the policy enforcement entity 2 can be configured.
  • the policy enforcement entity 1 and the policy enforcement entity 2 can generally be represented by an IP address on the policy server.
  • the policy enforcement entity 1 may be configured as an anchor point policy execution entity type on the policy server, and the policy enforcement entity 2 is an access gateway policy execution entity type, such that The policy server may obtain the charging policy execution capability and the gated policy execution capability of the policy enforcement entity 1 and the QoS policy execution capability of the policy enforcement entity 2 according to the configured entity type. Similar to the foregoing, the policy enforcement entity 1 and the policy enforcement entity 2 can generally be represented by an IP address on the policy server.
  • Each policy enforcement entity can report its own policy execution capability to the policy server.
  • the policy enforcement entity 1 can report its own policy execution capability to the policy server when the event is triggered. For example, the policy execution entity 1 reports the charging and gating policy execution capability to the policy server when receiving the mobile IP registration request.
  • the policy enforcement entity 1 can also report its own policy execution capability to the policy server when the event is triggered. For example, when receiving the mobile IP registration response, the policy execution capability, such as the QoS policy execution capability, is reported.
  • Strategy The server may associate multiple policy enforcement entities of the corresponding IP CAN Session according to the user IP address reported in the multiple event trigger.
  • the credit control request (CCR) message of the extended Gx interface can be used for the capability reporting, and the policy execution capability of the policy enforcement entity can be determined by the Diameter AVP (Attribute-Value Pair) in the CCR message. ) to identify.
  • the CCR message can be as follows:
  • Policy-Capability is the policy enforcement capability of the PCEF. For example, it can be valued as follows:
  • Q0S ( 0 ) indicates the Q0S policy execution capability
  • GatingControl ( 1 ) indicates the ability to gate the policy
  • ChargingControl (2) indicates the charging policy execution capability.
  • policy execution capabilities can also be obtained by the type of policy enforcement entity. For example, it can be reported by the following message:
  • PCEF-TYPE indicates the type of the policy enforcement entity
  • M0BILE-ANCH0R(0) indicates an anchor point policy enforcement entity, such as HA or P-GW, which generally performs policies such as charging and gating;
  • ACCESS_GW(1) denotes a policy enforcement entity in the access network, such as a policy enforcement entity on the WIMAX ASN-GW, a policy enforcement entity on the access gateway in 3GPP2, etc., which generally implement QoS policies.
  • Manner 3 A policy enforcement entity uniformly reports the policy enforcement capability or entity type of each policy enforcement entity.
  • each policy enforcement entity can be uniformly reported by the anchor point policy enforcement entity.
  • the two policy enforcement entities are respectively a policy enforcement entity 1 and a policy enforcement entity 2, and the policy enforcement entity 1 is an anchor point policy enforcement entity. Then, you can follow the steps below:
  • Step a The first policy enforcement entity obtains the IP address of the second policy enforcement entity.
  • the first policy enforcement entity may be an anchor point policy enforcement entity.
  • Each policy enforcement entity may have the execution capability of other policy enforcement entities, for example, the first policy execution entity has a policy execution capability 1 corresponding to the first policy execution entity, and the policy execution capability of the second policy execution entity remains. 2 . Therefore, the policy execution capabilities 1 and 1 can be uniformly reported to the policy server.
  • the policy server may know that the reported policy execution capability 1 corresponds to the first policy enforcement entity, but the policy server does not know the policy enforcement entity corresponding to the policy execution capability 2, and therefore, when the first policy enforcement entity reports the policy execution capability 1, The IP address of the second policy enforcement entity needs to be reported to the policy server, so that the policy server can know that the reported policy execution capability 2 corresponds to the second policy enforcement entity.
  • the policy enforcement entity needs to interact with the authentication server during the authentication process, and the authentication server can know the IP address of the policy execution entity in the process. Therefore, with this, the IP address of a policy enforcement entity can be sent to another policy enforcement entity.
  • the authentication server may send the IP address of the second policy enforcement entity to the first policy enforcement entity.
  • step a can be implemented as follows: Step a: The authentication server obtains the IP address of the second policy enforcement entity from the authentication process of the second policy enforcement entity.
  • Step a2 The authentication server sends the IP address of the second policy enforcement entity to the first policy enforcement entity by using a gateway address update response message.
  • the first policy enforcement entity obtains the IP address of the second policy enforcement entity from the gateway address update response.
  • the authentication server may be an Authentication, Authorization and Accounting (AAA) server.
  • AAA Authentication, Authorization and Accounting
  • Step b The first policy enforcement entity sends its corresponding policy execution capability and the policy execution capability corresponding to the second policy enforcement entity and the IP address of the second policy enforcement entity to the policy server.
  • the first policy enforcement entity can be configured to send its corresponding policy execution capability and execution capabilities and IP addresses of other policy enforcement entities to the policy server.
  • PCEF-Pol icy-Capabi 1 i ty indicates the policy execution ability of each policy enforcement entity:
  • the PCEF-ID identifies the policy enforcement entity, which is generally identified by the IP address of the policy enforcement entity.
  • Pol icy-Capabi 1 ty is the policy enforcement capability of the policy enforcement entity.
  • step b It can also be implemented in the following ways:
  • the first policy enforcement entity sends its type and the type of the second policy enforcement entity and the IP address of the second policy enforcement entity to the policy server.
  • the first policy enforcement entity can send its type and the type and IP address of other policy enforcement entities to the policy server, and the policy server derives the policy execution capability according to the type of each policy execution entity. That is, the policy execution capability corresponding to the first policy enforcement entity and the policy execution capability and IP address of other policy enforcement entities are sent to the policy server.
  • the PCEF-ID identifies the policy enforcement entity, and the PCEF-TYPE is the type of the policy enforcement entity.
  • Step 902 If the policy enforcement entity has policy execution capability, the policy server distributes the corresponding policy to the policy enforcement entity.
  • the policy server will charge and gate the policy. It is sent to the policy enforcement entity 1 and the QoS policy is sent to the policy enforcement entity 2.
  • the policy server sends the charging and gating policy to the policy execution.
  • Entity 1 the QoS policy is sent to the policy enforcement entity 2.
  • the complete embodiment 1 corresponding to the first method embodiment is described below.
  • the policy execution capability of the policy enforcement entity is configured on the policy server, and the policy server distributes the corresponding policy to each policy enforcement entity according to the configured policy execution capability.
  • FIG. 10 shows this complete embodiment one, as shown:
  • Step 1001 Configure policy execution performance of each policy execution entity on the policy server. Force.
  • the policy enforcement entity 1 corresponds to the charging and gating policy execution capability
  • the policy enforcement entity 2 corresponds to the QoS policy execution capability
  • Step 1002 The policy server generates a QoS, charging, and gating policy corresponding to the service data flow according to information such as service information delivered by the application function entity (AF), and the service data flow is bound to an IP address.
  • AF application function entity
  • Step 1003 The policy server distributes the charging and gating policy to the policy enforcement entity
  • Step 1004 The policy server distributes the QoS policy to the policy enforcement entity 2.
  • step 1003 and step 1004 are not sequential.
  • the complete embodiment 2 corresponding to the first method embodiment is described below.
  • the policy enforcement entity 1 reports the charging and gating policy execution capability to the policy server
  • the policy enforcement entity 2 reports the QoS policy execution capability to the policy server.
  • the policy server distributes the corresponding policy to the policy according to the reported policy execution capability. Execution Entity 1 and Policy Execution Entity 2.
  • FIG 11 shows the complete embodiment 2, as shown:
  • Step 1101 The policy enforcement entity 1 reports the charging and gating policy execution capability to the policy server.
  • the step may be triggered by an event, causing the policy enforcement entity 1 to report the charging and gating policy execution capability.
  • the triggering event may be, for example, the policy enforcement entity 1 receiving the mobile IP registration request.
  • the policy execution entity 1 reports its own accounting policy execution capability and the gated policy execution capability to the policy server.
  • the message can be implemented by using the Diameter CCR message.
  • the message carries the following AVP:
  • the Policy-Capability can have two values, which are 1 (representing the gating policy enforcement capability) and 2 (representing the charging policy enforcement capability).
  • Step 1102 The policy enforcement entity 2 reports the QoS policy execution capability to the policy server.
  • the step may be triggered by an event, causing the policy enforcement entity 2 to report the QoS policy enforcement capability.
  • the triggering event may be, for example, the policy enforcement entity 2 receiving the mobile IP registration response.
  • the policy execution entity 1 reports its own QoS policy execution capability to the policy server, which can be implemented by using a Diameter CCR message.
  • the message carries the following AVP:
  • Step 1103 The policy server generates a QoS, charging, and gating policy corresponding to the service data flow according to information such as service information delivered by the application function (AF), where the service data flow is bound to the user IP address in the report message. Corresponding IP CAN Session.
  • AF application function
  • Step 1104 The policy server distributes the charging and gating policy to the policy enforcement entity
  • Step 1105 The policy server distributes the QoS policy to the policy enforcement entity 2.
  • step 1104 and step 1105 are not sequential. Moreover, the step 1104 and the step 1105 are: the policy server performs a decision according to the user service information sent by the AF, and generates a service data flow policy for the corresponding IP CAN Session, where the policy includes policies such as QoS, charging, and gating. In the second embodiment, as described above, the policy enforcement entity 1 and the policy enforcement entity 2 may separately report the policy execution entity type.
  • the IP addresses of the policy enforcement entity 1 and the policy enforcement entity 1 are IP1 and IP2, respectively.
  • the policy execution entity 1 is an anchor point policy execution entity, and uniformly reports the policy execution capability of the policy execution entity 1 and the policy execution entity 2 to the policy server.
  • the policy server distributes the policy to the policy enforcement entity 1 and the policy enforcement entity 2 accordingly.
  • Figure 12 shows the complete embodiment three, as shown:
  • Step 1201 The policy execution entity 2 performs an authentication message interaction with the AAA server. In this step, the IP address IP2 of the policy enforcement entity 1 is obtained.
  • Step 1202 The AAA server receives the trigger event, which may be a gateway address update request of the policy enforcement entity 1.
  • Step 1203 The AAA server sends a gateway address update response message to the policy enforcement entity 1 according to the received event triggering, and the response message carries the IP address of the policy enforcement entity 1.
  • Step 1204 The policy execution entity 1 reports the policy execution capability of the policy execution entity 1 and the policy execution entity 1 to the policy server.
  • the reporting policy execution capability in this step can use the Diameter CCR message, which carries the following AVP:
  • PCEF_Pol icy-Capability There are two PCEF_Pol icy-Capability, which are respectively as follows: Policy Execution Entity 2:
  • the value of the PCEF-ID is IP2 and the value of the Policy-Capability is 0 (the QoS policy enforcement capability).
  • the PCEF-ID value is IP1
  • the two Policy-Capability values are 1 (gating policy execution capability) and 2 (accounting policy execution capability).
  • Step 1205 The policy server generates a QoS, charging, and gating policy corresponding to the service data flow according to information such as service information delivered by the application function (AF), where the service data flow is bound to the user IP address in the report message. Corresponding IP CAN Session.
  • AF application function
  • Step 1206 The policy server distributes the charging and gating policy to the policy enforcement entity
  • Step 1207 The policy server distributes the QoS policy to the policy enforcement entity 2.
  • Steps 1206 and 1207 do not have a sequence. Moreover, in step 1206 and step 1207, the policy server performs a decision according to the user service information sent by the AF, and generates a service data flow policy for the corresponding IP CAN Session, where the policy includes policies such as QoS, charging, and gating.
  • the policy enforcement entity types of the upper policy enforcement entity 1 and the policy enforcement entity 1 may also be used.
  • the policy execution entity 1 when the user roams, there are two policy enforcement entities: the policy execution entity 1 is located at the home location, and the policy execution entity 2 is located at the visited place. Policy distribution is done by the user's home policy server.
  • the policy enforcement entity 1 reports the type of the policy enforcement entity to the home policy server as an anchor point, and the policy enforcement entity 2 passes the visited policy server to the home policy.
  • the server reports its own entity type as an access gateway.
  • the policy server obtains its policy execution capability according to the type of each policy enforcement entity, and then executes the capability distribution policy according to the policy.
  • Figure 13 shows this complete embodiment four, as shown:
  • Step 1301 The policy enforcement entity 1 reports its own policy enforcement entity type to the home policy server.
  • the step may be triggered by an event, causing the policy enforcement entity 1 to report the policy execution entity type, and the triggering event may be, for example, the policy enforcement entity 1 receives the mobile IP registration request.
  • PCEF-Type takes a value of 1 (an anchor point)
  • Step 1302 The policy execution entity 1 reports its own policy execution entity type to the visited policy server.
  • the step may be triggered by an event, causing the policy enforcement entity 2 to report the QoS policy enforcement capability.
  • the triggering event may be, for example, the policy enforcement entity 2 receiving the mobile IP registration response.
  • PCEF-Type 1 (access gateway).
  • Step 1303 The visited policy server sends the policy execution entity type reported by the policy enforcement entity 1 to the home policy server.
  • Step 1304 The policy server generates a QoS, charging, and gating policy corresponding to the service data flow according to information such as service information delivered by the application function entity (AF), and the service data flow is bound to the report message.
  • the IP address of the user IP address corresponds to the IP CAN Ses s ion.
  • Step 1305 The home policy server distributes the charging and gating policy to the policy enforcement entity 1.
  • Step 1306 The home policy server distributes the QoS policy to the policy enforcement entity 2 through the visited policy server.
  • Step 1305 and step 1306 are not in order. Moreover, in step 1305 and step 1306, the policy server performs a decision according to the user service information sent by the AF, and generates a service data flow policy for the corresponding IP CAN message, the policy including policies such as QoS, charging, and gating.
  • the policy server performs a decision according to the user service information sent by the AF, and generates a service data flow policy for the corresponding IP CAN message, the policy including policies such as QoS, charging, and gating.
  • the policy server obtains the policy execution capability of each policy enforcement entity, determines the corresponding policy according to the policy execution capability of each policy enforcement entity, and distributes the determined policy to each policy execution entity, thus implementing different policies to be distributed to corresponding Policy enforcement entity.
  • a system for distributing policies including a policy server and a policy enforcement entity, wherein the policy server is configured to acquire the policy execution capability of each policy execution entity; and according to the acquired policy execution capabilities of each policy execution entity, distribute different policies to corresponding Policy enforcement entity;
  • the policy server distributes the corresponding policy to the policy enforcement entity.
  • the policy enforcement entity is configured to receive a corresponding policy distributed by the policy server. It is also used to report policy enforcement capabilities or entity types.
  • the following describes a policy server for distributing policies, including acquisition units and distribution orders. Yuan.
  • An obtaining unit configured to acquire a policy execution capability of the policy execution entity
  • a distribution unit configured to distribute related policies to corresponding policy execution entities according to policy enforcement capabilities of each policy enforcement entity configured on the configuration unit;
  • the obtaining unit obtains the policy execution entity policy execution capability by the policy execution capability of the policy execution entity configured thereon; or, the policy server 141 as shown in FIG. 14 , the policy server 141 is specifically configured by the configuration unit 141 1 Unit 1412, wherein
  • the configuration unit 1411 is configured to configure a policy execution capability or an entity type of the policy enforcement entity
  • the distribution unit 1412 is configured to distribute the policy to the corresponding policy enforcement entity according to the policy execution capability of each policy enforcement entity configured on the configuration unit 1411.
  • FIG. 15 is a block diagram of an embodiment of the policy server. As shown in the figure, the method includes an obtaining unit 1511 and a distribution unit 1512.
  • the acquiring unit 1511 is specifically configured to receive a reporting unit, and is configured to acquire a policy execution capability reported by each policy execution entity. ;
  • the distribution unit 1512 is configured to distribute different policies to the corresponding policy execution entities according to the acquired policy execution capabilities of the policy enforcement entities.
  • Figure 16 shows a block diagram of an embodiment of the system, as shown, including a first policy enforcement entity 161, a second policy enforcement entity 162, and a policy server 163, wherein
  • the first policy enforcement entity 161 is configured to report the entity type of the first policy enforcement entity 161 to the policy server 163; and is further configured to receive the corresponding policy distributed by the policy server 163; the second policy enforcement entity 162 is configured to report the second policy enforcement entity 162. Entity type to policy server 163; also for receiving a quality of service policy distributed by policy server 163;
  • the policy server 163 is configured with the type of each policy enforcement entity, or receives the entity type of each policy execution entity that is reported, and then derives the policy according to the type of each policy execution entity. The ability is slightly executed, and the policy is distributed to the corresponding policy enforcement entity according to the derived policy execution capability.
  • the method includes a obtaining unit 1711 and a distributing unit 1712.
  • the obtaining unit 1711 specifically includes an entity type obtaining unit 17111 and an exporting unit 17112.
  • the entity type obtaining unit 17111 is configured with the type of each policy enforcement entity; or receives the entity type of each policy enforcement entity that is reported;
  • the exporting unit 17112 is configured to derive a policy execution capability of each policy execution entity according to an entity type of each policy execution entity;
  • the distribution unit 1712 is configured to distribute the policy according to the derived policy execution capability to the corresponding policy enforcement entity.
  • Figure 18 is a block diagram showing an embodiment of the system, as shown, including a first policy enforcement entity 181, a second policy enforcement entity 182, a policy server 183, and an authentication server 184, wherein
  • the second policy enforcement entity 182 is configured to initiate an authentication request to the authentication server 184; and is further configured to receive a quality of service policy distributed by the policy server 183;
  • the authentication server 184 is configured to perform an authentication interaction with the second policy enforcement entity 182, and obtain an IP address of the second policy enforcement entity 182.
  • the IP address of the second policy enforcement entity 182 obtained by the authentication interaction is also sent to the IP address of the second policy enforcement entity 182.
  • the first policy enforcement entity 181 is configured to report the policy execution capability corresponding to the first policy enforcement entity 181 and the policy execution capability corresponding to the second policy enforcement entity 182, and the received IP address of the second policy enforcement entity. To the policy server 183; or, the type of the first policy enforcement entity 181 and the second policy enforcement entity 182 and the IP address of the second policy enforcement entity are sent to the policy server 183;
  • the policy server 183 is configured to obtain the policy execution capability of each policy execution entity, or derive the policy execution capability by receiving the entity type of each policy execution entity, and distribute different policies to corresponding according to the obtained policy execution capabilities of each policy execution entity. Policy enforcement entity.
  • the second policy enforcement entity 182 includes an authentication request unit 1821 and a receiving unit 1822.
  • the authentication request unit 1821 is configured to initiate an authentication request to the authentication server 184;
  • the receiving unit 1822 is configured to receive the quality of service policy distributed by the policy server 183;
  • the authentication server 184 includes an authentication interaction unit 1841 and an address sending unit 1842, and the authentication
  • the interaction unit 1841 is configured to perform an authentication interaction with the authentication request unit 1821 in the second policy enforcement entity 182, and obtain an IP address of the second policy enforcement entity 182.
  • the address sending unit 1842 obtains the second obtained by the authentication interaction unit 1841.
  • the IP address of the policy enforcement entity 182 is sent to the first policy enforcement entity 181;
  • the first policy enforcement entity 181 includes an address receiving unit 1811, a reporting unit 1812, and a receiving unit 1813.
  • the address receiving unit 1811 is configured to receive an IP address of the second policy enforcement entity
  • the reporting unit 1812 is configured to: the policy execution capability corresponding to the first policy enforcement entity 181 and the policy execution capability corresponding to the second policy enforcement entity 182, and the received The IP address of the second policy enforcement entity is reported to the policy server 183; or, the type of the first policy enforcement entity 181 and the type of the second policy enforcement entity 182, and the received IP address of the second policy enforcement entity are sent to the policy.
  • Server 183 is configured to receive an IP address of the second policy enforcement entity
  • the reporting unit 1812 is configured to: the policy execution capability corresponding to the first policy enforcement entity 181 and the policy execution capability corresponding to the second policy enforcement entity 182, and the received The IP address of the second policy enforcement entity is reported to the policy server 183; or, the type of the first policy enforcement entity 181 and the type of the second policy enforcement entity 182, and the received IP address of the second policy enforcement entity are sent to the policy.
  • Server 183 is configured to receive an IP address of the second
  • the receiving unit 1813 is configured to receive a policy distributed by the policy server 183;
  • FIG. 19 is a block diagram showing an embodiment of the first policy enforcement entity, as shown, including an address receiving unit 1811, a reporting unit 1812, and a receiving unit 1813, wherein the address receiving unit 1811 is configured to receive the second policy enforcement entity.
  • the IP address; the reporting unit 1812 is configured to report the policy execution capability corresponding to the first policy enforcement entity 181 and the policy execution capability of the second policy enforcement entity 182 and the IP address of the second policy enforcement entity to the policy server 183; or The type of the first policy enforcement entity 181 and the type of the second policy enforcement entity 182 and the IP address of the second policy enforcement entity are sent to the policy server 183;
  • the receiving unit 1813 is configured to receive the charging and gating policies distributed by the policy server 183.
  • a fourth system embodiment of the present invention is described below.
  • Figure 20 shows a block diagram of an embodiment of the system, as shown, including a first policy enforcement entity 201, a second policy enforcement entity 202, the home policy server 203, the visited policy server 204, wherein the first policy enforcement entity 201 is configured to report the entity type of the first policy enforcement entity 201 to the policy server 203; and receive the first distributed by the home policy server 203.
  • the second policy enforcement entity 202 is configured to report the entity type of the second policy enforcement entity 202 to the visited policy server 204; and receive the second policy forwarded by the visited policy server 204;
  • the home policy server 203 is configured to distribute the determined policy to the corresponding policy enforcement entity; specifically, the first policy is distributed to the first policy enforcement entity 201, and the second policy is distributed to the second policy enforcement entity 202;
  • the visited policy server 204 includes a type forwarding unit 2041 and a policy forwarding unit 2042.
  • the type forwarding unit 2041 is configured to forward the entity type of the second policy enforcement entity 202 reported by the second policy enforcement entity 202 to the home policy server 203; and forward the second policy sent by the home policy server 203 to the second policy execution. Entity 202.
  • Figure 21 is a block diagram showing an embodiment of the visited policy server, as shown, including a type forwarding unit 2041 and a policy forwarding unit 2042, where
  • the type forwarding unit 2041 is configured to forward the entity type of the second policy enforcement entity 202 reported by the second policy enforcement entity 202 to the home policy server 203;
  • the policy forwarding unit 2042 is configured to forward the second policy sent by the home policy server to the second policy enforcement entity 202.
  • Figure 22 is a flow chart showing an embodiment of the second method of the present invention. As shown, it includes:
  • Step 2201 The policy distribution entity receives all the policies sent by the policy server, and obtains the policy execution capability of the policy execution entity.
  • Step 2202 The policy distribution entity distributes the corresponding policy of all the received policies to the corresponding policy enforcement entity according to the policy execution capability of each policy enforcement entity.
  • Step 2301 The policy server sends all policies to the policy enforcement entity 1. Policy distribution entity.
  • Step 2302 The policy distribution entity receives the policy execution capability reported by the policy execution entity 1.
  • Step 2303 The policy distribution entity on the policy enforcement entity 1 distributes the corresponding policy execution capability of all the received policies to the policy enforcement entity 1 according to the policy execution capability of the policy execution entity 1.
  • Step 2304 The policy distribution entity on the policy enforcement entity 1 distributes the corresponding policy execution capability of all the received policies to the policy enforcement entity 2 according to the policy execution capability of the policy execution entity 2.
  • the policy distribution entity may also be combined with a policy server, or a separate entity, or combined with a policy enforcement entity.
  • the policy server distributes the policy to the policy distribution entity, which can be distributed through the prior art Gx interface.
  • the policy distribution entity can also be combined with the policy server, that is, the case of the first embodiment of the foregoing method.
  • the policy distribution entity can know all the policies without the policy server sending.
  • the policy distribution entity can know the policy execution capability and the policy execution capability of other policy enforcement entities without requiring the policy enforcement entity to report.
  • the policy distribution entity can also know the entity type of the policy enforcement entity.
  • the above complete embodiment is an example of a policy distribution entity and a policy enforcement entity.
  • the policy distribution entity receives the policy execution capability reported by each policy execution entity, and performs policy execution according to each policy execution entity. The capability distributes the corresponding policy enforcement capabilities of all received policies to the corresponding policy enforcement entity.
  • the method for receiving the policy execution capability reported by the policy enforcement entity is similar to the case of the first method embodiment.
  • the policy execution entity may report the policy execution capability of the policy execution entity, or may report the entity type, and no further details are provided herein.
  • the policy execution capability of each policy enforcement entity may be pre-configured on the policy distribution entity, or the entity type of each policy execution entity may be pre-configured, and the corresponding policy execution capability may be derived through the entity type. Force, similar to the one described above.
  • Figure 24 shows a block diagram of an embodiment of the system. As shown, the policy server 2401, the policy distribution entity 2402, the first policy enforcement entity 2403, and the second policy enforcement entity 2404 are combined with the policy enforcement entity 1
  • the policy server 2401 is configured to send all the policies to the policy distribution entity 2402.
  • the policy distribution entity 2402 is configured to receive the policy execution capability reported by the policy execution entity 1, and execute all the policies that are to be received according to the policy execution capability of the entity 1 The corresponding policy execution capability is distributed to the policy enforcement entity 1;
  • the policy distribution entity may be co-located with a policy server, or a separate entity, or combined with a policy enforcement entity.
  • the policy distribution entity may also be associated with the policy server, i.e., the system embodiment or device embodiment corresponding to the foregoing FIGS. 14-21.
  • the policy distribution entity can know the policy enforcement capabilities of each policy enforcement entity without requiring the policy server to send to the policy distribution entity.
  • the policy server learns all the policies, and obtains the policy execution capability of each policy enforcement entity, and distributes the policy to the policy execution entity according to the policy execution capability of the policy execution entity, so that different policies are distributed to the corresponding policies. Execution entity.
  • the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for making a A computer device (which may be a personal computer, a server, or a network device, etc.) performs the methods described in various embodiments of the present invention.

Landscapes

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

Abstract

L'invention concerne un procédé et un système pour distribuer une stratégie ainsi qu'une entité de distribution de stratégie. Le procédé consiste à, pour l'entité de distribution de stratégie, obtenir une stratégie ;obtenir une capacité de mise en œuvre de stratégie d'une entité de mise en œuvre de stratégie, la stratégie se rapportant à la règle de traitement d'un flux de données de service ; fournir à l'entité de mise en œuvre de stratégie une stratégie conformément à la capacité de mise en œuvre de stratégie de l'entité de mise en œuvre de stratégie.
PCT/CN2008/072008 2007-08-31 2008-08-15 Procédé et système pour distribuer une stratégie et entité de distribution de stratégie WO2009030136A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710145740.4 2007-08-31
CN200710145740.4A CN101378522B (zh) 2007-08-31 2007-08-31 分发策略的方法、系统和策略分发实体

Publications (1)

Publication Number Publication Date
WO2009030136A1 true WO2009030136A1 (fr) 2009-03-12

Family

ID=40421809

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/072008 WO2009030136A1 (fr) 2007-08-31 2008-08-15 Procédé et système pour distribuer une stratégie et entité de distribution de stratégie

Country Status (2)

Country Link
CN (1) CN101378522B (fr)
WO (1) WO2009030136A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103297382B (zh) * 2012-02-23 2018-08-31 中兴通讯股份有限公司 接入内容分发网络处理方法及装置
CN112910969B (zh) * 2017-02-28 2022-07-29 华为技术有限公司 一种业务管理方法及其装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1774891A (zh) * 2003-03-20 2006-05-17 波音公司 传送策略工具
CN1777179A (zh) * 2004-11-19 2006-05-24 微软公司 用于分发安全策略的方法和系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1601945A (zh) * 2003-09-28 2005-03-30 华为技术有限公司 一种实现数据业务付费实时性的系统和方法
CN100512293C (zh) * 2005-09-07 2009-07-08 华为技术有限公司 一种会话初始化协议消息体内容处理方法及网络

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1774891A (zh) * 2003-03-20 2006-05-17 波音公司 传送策略工具
CN1777179A (zh) * 2004-11-19 2006-05-24 微软公司 用于分发安全策略的方法和系统

Also Published As

Publication number Publication date
CN101378522A (zh) 2009-03-04
CN101378522B (zh) 2012-01-25

Similar Documents

Publication Publication Date Title
CN100579302C (zh) 一种非漫游场景下策略和计费规则功能服务器的选择方法
CN100536401C (zh) 策略与计费控制中用户签约信息的处理方法及装置
US8601533B2 (en) Method and system for session modification
CN102340866B (zh) 一种上报固网接入信息的方法及系统
CN101459951B (zh) 一种承载绑定和事件报告功能策略控制的方法及系统
WO2010031316A1 (fr) Procédé et système pour réaliser la commande de politique et de facturation sur la scène de multiples réseaux de données par paquets (pdn)
CN102075900A (zh) 一种实现用量监测控制的方法及系统
WO2009012686A1 (fr) Procédé, équipement et système de mise en œuvre du contrôle des conditions d'utilisation et de facturation
WO2013155942A1 (fr) Procédé de commande de politique et de facturation, v-pcrf et v-ocs
WO2011097911A1 (fr) Procédé, dispositif et système pour sélectionner une entité de fonction de politique et de règles de facturation
WO2011082036A2 (fr) Procédés, systèmes et supports lisibles sur machine pour établir une configuration de politique de groupe dans un réseau de communication par le biais d'un faux utilisateur
WO2009046678A1 (fr) Procédé et dispositif pour obtenir la capacité de fonction d'application de politique et de facturation
WO2009021462A1 (fr) Procédé et dispositif d'établissement de session ip-can
WO2016201999A1 (fr) Procédé et appareil de facturation d'application tierce, et dispositif à fonction d'application
WO2010052030A1 (fr) Appareil de commande de politique et procédé de transfert d'informations de commande de politique
WO2011029289A1 (fr) Procédé et système de transmission d'un mode de commande de support dans des scénarios d'itinérance
WO2011063688A1 (fr) Procédé et système de sélection d'entité à fonction de règles de politique et de facturation
WO2012075875A1 (fr) Procédé et système permettant l'enregistrement et la mise en application d'un service de limitation des dépenses
CN102316548A (zh) 信息传递方法和系统
WO2011085614A1 (fr) Procédé de gestion de ressources dans un réseau convergent à service complet et système correspondant
WO2011026385A1 (fr) Procédé et système de facturation en ligne dans des scénarios d'itinérance à raccordement local
CN103929725B (zh) 漫游本地业务的在线计费方法、h-ocs及v-ocs
CN104581670A (zh) 应用接入控制方法及应用功能实体装置
WO2014094488A1 (fr) Procédé et dispositif de gestion de politique de facturation destinés à un service local d'itinérance
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

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08783999

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载