CN101035001A

CN101035001A - Method and system for processing the strategy control and charging

Info

Publication number: CN101035001A
Application number: CN 200610066612
Authority: CN
Inventors: 肖家幸; 陈卫民; 胡华东; 段小琴; 刘继兴
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2006-03-10
Filing date: 2006-04-13
Publication date: 2007-09-12

Abstract

This invention provides a method and system to deal with strategy control and accounting. The method including: to set up functional entities in the strategy control and accounting system through which to deal with the adoption of the roaming function under the rules of attribution strategy billing functions or transmit news and non-roaming network under a strategy to their billing rules functional entities addressable and information transmitted. Through this invention improve the existing control and accounting framework strategy to increase the flexibility of the network architecture that it is functional network topology; In addition, strategy billing rules functional entities addressable function under roaming circumstance be achieved and enhance current applications entities and users trigger flow of business strategy in the process of the establishment of accounting rules in functional entities addressing.

Description

Method and system for processing policy control and charging

Technical Field

The present invention relates to the field of mobile communications, and in particular, to a method and system for processing Policy Control and Charging (PCC), and more particularly, to a method and system for processing PCC.

Background

The following describes a method for handling PCC in the prior art by taking a 3GPP system as an example. Why is PCC introduced in 3GPP (3rd Generation Partnership Project? In Rel6 of 3GPP, a Policy Based on Local Session (SBLP) and a charging Based on Flow (FBC) scheme have been provided. However, these two schemes have a certain overlap, which is reflected in two aspects, namely function repetition and interface repetition. From a functional point of view, the flow based charging FBC may also provide some degree of policy control functionality, e.g. gating functionality, which poses a problem: also a function can be implemented using both local session based policy control SBLP and flow based charging FBC schemes, thus creating unnecessary redundancy of the system. From the interface point of view, the information transmitted by the interface is also very similar in the Policy control SBLP based on local session and the Charging FBC based on flow, for example, the Application Function (AF) entity in both schemes needs to provide service-related information to the decision entity in the scheme, namely the Policy Decision Function (PDF) and the Charging Rule Function (CRF), respectively. In summary, this duplication both increases the complexity of the system and reduces the efficiency of the system.

From the signaling point of view, the mechanism of separately issuing the policy and charging information will also greatly increase the time delay of some system operations, thereby aggravating the shortage of the real-time service processing capability of the current network. In the evolution of 3G (3th Generation; third Generation mobile communication standard) networks, how to reduce the signaling delay of the system has become one of the key issues to be solved, and has attracted extensive attention.

In addition, the universality of the Rel6 strategy control and flow charging is also a great problem. Taking the local session based policy control SBLP scheme as an example, it is specifically designed for session based GPRS packet services. However, in future evolution networks, the service types are varied, and the access technologies that users can select are increasing. This change naturally places new demands on the policy control mechanism in the network, and it needs to be able to adapt to various service environments (conversational and non-conversational) and various access environments, such as General Packet Radio Service (GPRS) and Wireless Local Access Network (WLAN), i.e. its scheme needs to be independent of specific service and access environments.

In order to improve the efficiency of the system, simplify the operation, reduce the time delay, and improve the universality of the policy control and flow charging mechanisms, the policy control and the charging control need to be fused, and the fused mechanism is the Policy Control and Charging (PCC).

Policy control and charging PCC the current architecture is a solution fused from the local session based policy control SBLP framework defined by R5 and the flow based charging FBC framework defined by R6 in 3 GPP. As shown in fig. 1, it is a schematic diagram of an architecture of a local session based policy control SBLP scheme; fig. 2 is a schematic diagram of the architecture of a flow-based charging FBC scheme; fig. 3 is a schematic diagram of a policy control and charging PCC architecture for merging local session based policy control SBLP and flow based charging FBC.

The original policy control mechanism cannot effectively monitor the traffic operation condition in the network, cannot distinguish the traffic of different services (services) carried in the context of Packet Data Protocol (PDP), and accordingly applies different policy control and different Quality of Service (QoS) for different services. Therefore, with the advent of a variety of applications, it is necessary to refine the extensive policy control approach in existing networks. The introduction of local session based policy control SBLP is to solve this problem. Fig. 1 is a schematic diagram illustrating an architecture of local session based policy control SBLP. Wherein,

the core mechanism of local session based policy control SBLP is its binding mechanism, which is also the rationale for its ability to implement service based policy control.

The binding mechanism associates a packet data protocol PDP context bearer with one or more IP flows in order to support service-based local policy enforcement. The binding information is passed to the Gateway GPRS Support Node (GGSN) in a packet data protocol PDP context activation or modification message. The purpose of the binding is to enable the GGSN to efficiently identify which flows (flows) belong to a certain PDP context and to know what strategy to use to ignore controlling these flows.

From the binding information, the address information of the corresponding Policy Decision Function (PDF) is obtained, so that the GGSN knows to whom the Policy information of the packet data protocol PDP context is going.

The content of the binding information includes: an authorization token and a flow flag. In the session establishment phase, the application function AF gives an authorization token to a User terminal (UE: User Equipment); then, the UE can put the token in a PDP context message or a Resource Reservation Protocol (RSVP) message, and form a binding message with the flow identifier, and then give the binding message to the GGSN for use in the subsequent operation flow. After the policy decision function PDF grants the application function AF an authorization token, the relevant SBLP local policy is stored for later use based on the service information received from the application function AF. When the GGSN applies bearer authorization to the policy decision function PDF, the PDF performs authorization operations based on the previously stored SBLP policy information. The GGSN obtains policy information from the policy decision function PDF and applies it to the passing packet data protocol PDP context bearers. The binding mechanism enables the GGSN to identify the IP media streams associated with a certain packet data protocol PDP context bearer and apply corresponding policy information accordingly.

The authorization token is unique in the domain space of the operator and complies with the relevant Internet Engineering Task Force (IETF) standards. The authorization token contains a legal domain name of the policy decision function PDF, so that the GGSN can know which policy decision function PDF to contact after obtaining the token, thereby obtaining the related resource authorization information. The flow marker plus token uniquely identifies an IP media flow. The policy decision function PDF may reject the authorization request of the application function AF due to a mismatch of the service information provided by the application function AF and the policy rules of the operator.

For the charging mechanism, the original charging mechanism is based on the packet data protocol PDP context charging, and this charging mode has a defect: since a session often includes a plurality of different media components (service data flows), it cannot implement independent charging for each media component, and can only perform uniform charging for the PDP context of the session. This charging mode is not reasonable because from the operator's point of view different media components occupy different network resources and therefore different charging criteria have to be implemented. Based on this, it is necessary to introduce a flow-based charging FBC mechanism to implement a finer-grained charging manner to achieve accurate control of the user network application. The flow-based charging approach may reduce the restriction on the PDP context media bearer type. Fig. 2 is a schematic diagram of the architecture of the flow-based charging FBC scheme. Wherein,

the implementation of flow based charging FBC relies on the implementation of charging rules, which is its basic principle.

By formulating different charging rules for different flows (flow), flow-based charging can be achieved; the charging rules have certain priority attributes. A Charging rule first comprises a traffic filter to filter out the target flows to be charged (Charging keys alone or together with service identifiers identify a flow). After the charging target flow is filtered out, the established charging rule can be implemented on the target flow, and corresponding metering operation is carried out.

In the flow-based charging FBC system, a charging execution function (TPF) is an execution logic module of a charging rule, the charging rule is installed in the charging execution function TPF, and the charging execution function TPF is responsible for flow differentiation, metering and charging result reporting. In a GPRS bearer network, the TPF may be implemented in the GGSN.

The Charging rules required by the Charging execution function TPF are provided by a Charging Rules Function (CRF) logic module, and the interface between the two is defined in Gx. The application function AF and the charging execution function TPF both provide some information to the charging rule function CRF, and according to these information, the charging rule function CRF selects the corresponding charging rule (stored in the service data flow based charging rule database), and installs it in the charging execution function TPF through the interface for execution.

Fig. 3 is a schematic diagram of a policy control and charging PCC architecture fusing SBLP and FBC. The introduction of policy control and charging PCC has mainly studied the following problems and their solutions:

1) the local session based policy control SBLP function and the flow based charging FBC function are combined under a new and separate architecture;

2) the new policy control and charging PCC system must be able to consider the subscription information of the user;

3) the research of a new binding mechanism enables the bearing and the service of the upper layer to correspond. This functionality enables the network to control the bearer performance used by the traffic flows.

Like the Flow-based charging FBC, the basic object that operates in the policy control and charging PCC is a Service Data Flow (SDF). Similarly, all operations in the policy control and Charging PCC are expressed by PCC rules (Rule), which in FBC is Charging Rule, and transferred to the performing functional entity in the network. The combination of the subscription information, the new binding mechanism and the PCC rule enables the policy control and charging PCC to be applicable to more general application environments, such as AF \ no AF, GPRS and non-GPRS load bearing, and the like, thereby providing a more generalized operation platform for implementing more new services.

As can be seen from fig. 3, the main change is to merge the policy decision Function PDF in SBLP and the Charging rule Function CRF in FBC into one functional entity, namely Policy and Charging Rule Function (PCRF), where PDF and CRF are both the functional entities for rule making; and fusing a Policy Enforcement Point (PEP) in the SBLP and a Charging Enforcement Function (TPF) in the FBC into a Policy and Charging Enforcement Function (PCEF), namely a Gateway (GW), wherein the PEP and the TPF are functional entities for executing rules. In addition, the application function AF inherits the previously existing function, i.e. provides service information for relevant decisions.

In addition, Go and Gx interfaces are merged into Gx +, which provides charging rules and policy control rules for PEP/TPF, respectively, and the Gx interface is easy to upgrade to support policy control function, called flow-based policy control (FBP). The two main functions of Gx are: transferring PCC rule request and response messages between the PCEF and the PCRF; event messages of the user plane are transferred between the PCEF and the PCRF. Interfaces Gq and Rx of the policy control and charging PCC towards the session layer and the application layer are merged into Rx +, and the Gq and Rx interfaces are very similar in function, and transfer information about IP-based multimedia subsystem (IMS) sessions and media parameters at the session control layer to the policy control and charging PCC.

A new solution is introduced to solve the binding problem of bearers and traffic, unlike the authorization token (token) mechanism used by existing SBLP. Flow-based policy control will use a data flow Template (TFT) contained within the PDP Context, the TFT identifying the flow by IP address and port number, in a similar way to the CRF/PDF identifying IP flows.

And finally, a Subscriber Profile Repository (SPR) functional entity is added in the PCC, which is mainly used for storing real-time subscriber subscription policies and better keeps the policy consistency of the network and the subscriber in the PCC. As shown in fig. 4, the schematic diagram of a new subscriber subscription information database SPR functional entity in the PCC framework is shown, where an Sp interface enables the subscriber subscription information database SPR to provide subscription information related to a subscriber to the policy and charging rule function PCRF. Through the Sp interface between the Subscriber subscription information database SPR and the PCRF, the policy and charging rules function PCRF can request the Subscriber subscription information database SPR for subscription information related to the bearer policy according to the effective Identification (ID) of the Subscriber, such as the International Mobile Subscriber Identity (IMSI). If the policy and charging rules function PCRF has requested the relevant subscription information before, when the subscriber subscription information database SPR detects that the relevant subscription information has changed, it will inform the corresponding PCRF of these changes via the Sp interface.

There is already an architecture for handling policy control and charging PCC in roaming in Rel7 of the existing 3GPP standard, wherein two scenarios are included, such as a scenario where an application function AF and a PCEF of a service user are both in a visited network and a scenario where an AF of a service user is in a home network and a PCEF of a service user is in a visited network; fig. 5 is a schematic diagram of an architecture for handling policy control and charging PCC in roaming case in the prior art.

In this structure diagram, the functions of the respective functional entities are as follows:

policy and charging enforcement function, PCEF, for probing traffic data flows, enforcement of policies, flow-based charging functions; a policy and charging rule function PCRF, which comprises a visiting policy charging rule function (V-PCRF: Visited PCRF) and a Home policy charging rule function (H-PCRF: Home PCRF), and is used for processing the formulation of QoS policy and charging policy, keeping the user policy consistent with the policy of the network side, and processing roaming function; the user subscription information database SPR comprises subscription related information of users, and directly provides the subscription related information for the PCRF users of the PCC, so that the real-time decision-making capability of the PCRF is enhanced; the application function AF provides some application information functions which need to carry out IP bearing user plane dynamic strategy resource control; an Online Charging System (OCS) for providing a user Online Charging function, namely a prepayment function; an Offline Charging System (OFCS) for providing a user Offline Charging function, namely a post-payment function; the Billing System (Billing System) has the function of generating a bill according to the charging information of the postpaid user.

In addition to the functional entities in the figures, the interfaces between them are described as follows:

the Rx interface is an interface between the AF functional entity and the PCRF functional entity and is used for transmitting dynamic service information between the AF functional entity and the PCRF functional entity; a Gx interface, which is an interface between a PCEF functional entity and a PCRF functional entity, and transmits service information based on a local QoS policy and a charging rule between the PCEF and the PCRF; the Gy interface is an interface between the PCEF functional entity and the OCS and is used for transmitting the related information of the prepaid user between the PCEF and the OCS; the Gz interface is an interface between the PCEF functional entity and the OFCS, and transmits the charging related information of the post-paid user between the PCEF and the OFCS; and the Sp interface is an interface between the PCRF functional entity and the SPR functional entity and is used for transmitting the information related to the subscription of the user.

In addition to the above interfaces, there are also some other interfaces. The specific naming of the interface between the V-PCRF and the H-PCRF is not yet determined, but the existence of the interface is necessary. The other marks are "? "and the specific nomenclature is not yet determined.

A framework for a PCC solution in roaming situations is formed by the above functional entities and interfaces. However, the disadvantage of the prior art is that the PCRF of the visited network can directly access the PCRF of the home network, so that the topology structure of the home network is directly exposed to the external network, topology hiding cannot be realized, and potential safety hazards are increased; in addition, in a roaming scenario, the current specifications of an addressing mechanism between the V-PCRF and the H-PCRF and an addressing mechanism in the current AF addressing and user-triggered service flow establishment process are not yet determined.

Disclosure of Invention

In view of the problems in the prior art, an object of the present invention is to provide a method of handling policy control and charging and a system thereof.

The invention provides a method for processing policy control and charging, wherein a functional entity is arranged in a policy control and charging system, and the functional entity is used for processing addressing and message forwarding of a home policy charging rule functional entity under roaming or addressing and message forwarding of a policy charging rule functional entity of a network under non-roaming.

According to the invention, the functional entity is arranged in the home network and connected with at least one home policy charging rule functional entity, the functional entity interacts with the policy charging rule functional entity of the visited network, and the home policy charging rule functional entity is addressed and message forwarding by the visited policy charging rule functional entity is processed by the functional entity.

The visiting strategy charging rule function entity addresses and transmits the message to the attribution strategy charging rule function entity, comprising the following steps:

visiting the address information of the policy charging rule function entity to inquire the function entity about the home policy charging rule function entity of the user;

after obtaining the address information, the visiting strategy charging rule function entity sends the user information to the attribution strategy charging rule function entity.

The visiting policy charging rule function entity inquires the address information of the home policy charging rule function entity of the user from the function entity, comprising the following steps:

the visiting strategy charging rule functional entity sends an address query request message to the functional entity;

after receiving the address inquiry request message, the functional entity inquires the address information of the attribution policy charging rule functional entity and feeds back the inquiry result to the visit policy charging rule functional entity.

The visiting strategy charging rule function entity addresses and forwards the message to the attribution strategy charging rule function entity, including the steps:

the visited policy charging rule functional entity sends the user message to the functional entity;

the functional entity inquires the address information and local storage of the home policy charging rule functional entity, and then forwards the user message to the home policy charging rule functional entity;

and after receiving the user message, the attribution policy rule functional entity sends a response message, and the response message is forwarded to the visited policy charging rule functional entity through the functional entity.

the visiting policy charging rule functional entity sends a user message to the functional entity, wherein the user message carries address information of the visiting policy charging rule functional entity;

the functional entity inquires the address information of the attribution policy charging rule functional entity and forwards the user information to the attribution policy charging rule functional entity;

after receiving the user message, the home policy charging rule functional entity sends a response message, and the response message is forwarded to the visited policy rule functional entity through the functional entity; or directly sending the response message to the visit policy rule functional entity, wherein the response message carries the address information of the home policy rule functional entity;

and after receiving the response message, the visiting policy charging rule function entity stores the address information of the attribution policy rule function entity so as to directly send the subsequent message of receiving the policy and charging of the user to the attribution policy charging rule function entity.

The functional entity inquires the address information of the home policy charging rule functional entity according to a local policy or a mode of inquiring from a user subscription information database.

An interface between the functional entity and the home policy charging rules functional entity is implemented to carry policy control and charging related messages between the functional entity and the home policy charging rules functional entity.

An interface between the functional entity and the visited policy charging rules functional entity is implemented to transfer policy control and charging related information between the two operators.

According to the invention, a functional entity is provided in each of the visited network and the home network, wherein,

the functional entity of the visit network is connected with the visit policy charging rule functional entity, and the functional entity of the home network is connected with at least one home policy charging rule functional entity, so that the functional entity of the home network interacts with the functional entity of the visit network, and the functional entity processes the addressing and message forwarding of the visit policy charging rule functional entity to the home policy charging rule functional entity.

the visiting policy charging rule function entity inquires the address information of the attribution policy charging rule function entity from the function entity of the visiting network;

the functional entity of the visit network inquires the address information of the home policy charging rule functional entity from the functional entity of the home network;

and after obtaining the address information of the home policy charging rule functional entity, the visiting policy charging rule functional entity sends the user information to the home policy charging rule functional entity.

The functional entity of the visit network inquires the address information of the home policy charging rule functional entity from the functional entity of the home network, comprising the steps of:

the functional entity of the visit network sends an address query request message to the functional entity of the home network;

after receiving the address query request message, the functional entity of the home network queries the address information of the home policy charging rule functional entity and feeds back the query result to the visited policy charging rule functional entity.

the visiting policy charging rule functional entity sends the user message to the functional entity of the visiting network;

the functional entity of the visiting network inquires the address information and local storage of the functional entity of the home network and forwards the user message to the functional entity of the home network;

the functional entity of the home network inquires the address information and local storage of the home policy charging rule functional entity of the user and forwards the user information to the home policy charging rule functional entity;

and after receiving the user message, the home policy rule functional entity sends a response message, and the response message is forwarded to the visited policy charging rule functional entity through the home network and the functional entities of the visited network.

the visiting policy charging rule functional entity sends a user message to a functional entity of a visiting network, wherein the user message carries address information of the visiting policy rule functional entity;

the functional entity of the visiting network inquires the address information of the functional entity of the home network and forwards the user message to the functional entity of the home network;

the functional entity of the home network inquires the address information of the home policy charging rule functional entity of the user and forwards the user information to the home policy charging rule functional entity;

after receiving the user message, the home policy charging rule functional entity sends a response message, and the response message is forwarded to the visited policy rule functional entity through the home network and the functional entity of the visited network; or directly sending the response message to the visit policy rule functional entity, wherein the response message carries the address information of the home policy rule functional entity;

The functional entity of the visiting network inquires the address information of the functional entity of the home network according to a local strategy or a mode of inquiring a user subscription information database.

The interface between the function entity of the home network and the home policy charging rule function entity is realized to bear the information related to policy control and charging between the function entity and the home policy charging rule function entity;

the interface between the functional entity of the visiting network and the visiting policy charging rule functional entity is realized to bear the information related to policy control and charging between the functional entity and the visiting policy charging rule functional entity.

An interface between the functional entities of the visited network and the functional entities of the home network is implemented to transfer policy control and charging related information between the two operators.

The application function entity is connected with the function entity of the network to which the application function entity belongs, and the function entity processes the addressing and message forwarding of the application function entity to the attributive strategy charging rule function entity.

According to the invention, the application function entity belongs to a home network, and the function entity connected with the application function entity is connected with at least one home policy charging rule function entity.

The application function entity addresses and forwards the message of the home policy charging rule function entity, comprising the steps of:

the application function entity inquires the address information of the attribution policy charging rule function entity of the user from the function entity;

and after obtaining the address information, the application function entity sends the user information to the attribution policy charging rule function entity.

an application functional entity sends a user message to the functional entity;

the functional entity inquires the address information and local storage of the attribution policy charging rule functional entity and forwards the user message to the attribution policy charging rule functional entity;

and after receiving the user message, the attribution policy rule functional entity sends a response message, and the response message is forwarded to the application functional entity through the functional entity.

an application function entity sends a user message to the function entity, wherein the user message carries address information of the application function entity;

after receiving the user message, the attribution policy charging rule functional entity sends a response message, and the response message is forwarded to the application functional entity through the functional entity; or directly sending the response message to the application function entity, wherein the response message carries the address information of the attribution policy rule function entity;

after receiving the response message, the application function entity stores the address information of the attribution policy rule function entity so as to directly send the subsequent message of receiving the user policy and charging to the attribution policy charging rule function entity.

According to the invention, the application function entity belongs to a visited network or a 3rd party network of a non-home, non-visited network; the home network is also provided with a functional entity which is connected with at least one home policy charging rule functional entity.

the application function entity inquires the address information of the home policy charging rule function entity of the user from the function entity of the network;

the functional entity of the affiliated network inquires the address information of the home policy charging rule functional entity of the user from the functional entity of the home network;

after obtaining the address information of the attribution policy charging rule function entity, the application function entity forwards the user information to the attribution policy charging rule function entity.

the application function entity sends the user message to the function entity of the network;

the functional entity of the affiliated network inquires the address information and the local storage of the functional entity of the home network and forwards the user related information to the functional entity of the home network;

the functional entity of the home network inquires the address information and local storage of the home policy charging rule functional entity of the user and forwards the user message to the home policy charging rule functional entity;

and after receiving the user message, the home policy rule functional entity sends a response message, and the response message is forwarded to the application functional entity through the home network and the functional entity of the home network.

the application function entity sends a user message to a function entity of a network, wherein the user message carries address information of the application function entity;

the functional entity of the affiliated network inquires the address information of the functional entity of the home network and forwards the user message to the functional entity of the home network;

after receiving the user message, the home policy charging rule functional entity sends a response message, and the response message is forwarded to the application functional entity through the home network and the functional entity of the home network; or directly sending the response message to the application function entity, wherein the response message carries the address information of the attribution policy rule function entity;

According to the invention, under non-roaming, the functional entity is connected with the gateway of the network and at least one policy charging rule functional entity, and the gateway addresses and forwards the message of the policy charging rule functional entity in the process of establishing the service flow triggered by the user through the functional entity.

The gateway addresses and message forwards the strategy charging rule function entity, including the steps:

the gateway inquires the address information of the policy charging rule functional entity of the user from the functional entity;

after obtaining the address information, the gateway sends the user information to the policy charging rule function entity.

the gateway sends the user message to the functional entity;

the functional entity inquires the address information and local storage of the policy charging rule functional entity, and then forwards the user message to the policy charging rule functional entity;

and after receiving the user message, the strategy rule functional entity sends a response message, and the response message is forwarded to the gateway through the functional entity.

the gateway sends a user message to the functional entity, wherein the user message carries address information of the gateway;

the functional entity inquires the address information of the policy charging rule functional entity and then forwards the user message to the policy charging rule functional entity;

after receiving the user message, the policy charging rule functional entity sends a response message, and the response message is forwarded to the gateway through the functional entity; or directly sending the response message to the gateway, wherein the response message carries the address information of the policy rule functional entity;

after receiving the response message, the gateway stores the address information of the attribution policy rule function entity so as to directly send the subsequent message of receiving the policy and charging of the user to the policy charging rule function entity.

An interface between the gateway and the functional entity is implemented to carry policy control and charging related messages between the functional entity and the gateway.

According to the invention, under roaming, a functional entity is respectively arranged in a visiting network and a home network, wherein the functional entity of the visiting network is connected with a visiting strategy charging rule functional entity and a visiting gateway, the functional entity of the home network is connected with a home strategy charging rule functional entity and a visiting strategy charging rule functional entity, and the visiting gateway addresses the home strategy charging rule functional entity and forwards messages in the process of establishing a service flow triggered by a user through the functional entities of the visiting network and the home network.

The visiting gateway addresses and transmits the message to the home policy charging rule function entity, including the steps:

after receiving the policy and charging request of the roaming user, the visiting gateway inquires the address information of the visiting policy charging rule function entity from the function entity of the visiting network;

after inquiring the address information, the functional entity of the visit network feeds back the address information to the visit gateway;

the visiting gateway sends a policy and charging request message of a user to a visiting policy charging rule function entity;

the visiting strategy charging rule function entity makes a local decision on the strategy and charging request message of the user and allows the user to pass;

then, the visiting strategy charging rule function entity addresses and transmits the message to the attribution strategy charging rule function entity.

after receiving the strategy and charging request of the roaming user, the visiting gateway sends the strategy and charging request message of the user to a functional entity of the visiting network;

after the functional entity of the visit network acquires the address information and local storage of the visit policy charging rule functional entity, the functional entity transmits the policy and charging request message of the user to the visit policy charging rule functional entity;

the visiting strategy charging rule function entity addresses and forwards the message to the attribution strategy charging rule function entity;

and after receiving the strategy and charging response message, the visiting strategy charging rule functional entity sends the strategy and charging response message to the visiting gateway through the functional entity of the visiting network.

after the functional entity of the visit network acquires the address information of the visit policy charging rule functional entity, the policy and charging request information of the user is transmitted to the visit policy charging rule functional entity;

when the visiting strategy charging rule function entity receives the strategy and charging response message, the strategy and charging response message is sent to the visiting gateway through the function entity of the visiting network or directly.

According to the invention, under roaming, a functional entity is respectively arranged in a visiting network and a home network, wherein the functional entity of the visiting network is connected with a visiting strategy charging rule functional entity and a visiting gateway, the functional entity of the home network is connected with a home strategy charging rule functional entity and a functional entity of the visiting network, and the visiting gateway addresses and forwards messages of the home strategy charging rule functional entity in the process of establishing a service flow triggered by a user through the functional entities of the visiting network and the home network.

and the visiting policy charging rule function entity addresses and forwards the message to the attribution policy charging rule function entity.

the visiting strategy charging rule function entity sends the message to the attribution strategy charging rule function entity;

then, visiting the policy charging rule function entity to the home policy charging rule function entity and forwarding the message;

when the visiting strategy charging rule functional entity receives the strategy and charging response message, the strategy and charging response message is sent to the visiting gateway through the functional entity of the visiting network or directly, wherein the response message carries the address information of the visiting strategy rule functional entity;

the visiting gateway directly sends the information of the strategy and the charging of the user which is received subsequently to the visiting strategy charging rule function entity.

The invention also provides a system for processing policy control and charging under roaming, which comprises a home network and a policy control and charging system of a visited network, wherein a functional entity is arranged in the policy control and charging system of the home network and is respectively connected with the home policy charging rule functional entity and the visited policy charging rule functional entity, so that the visited policy charging rule functional entity interacts with the functional entity of the home network.

The interface between the functional entity and the attribution policy charging rule functional entity is a PP interface;

the interface between the functional entity and the visited policy charging rule functional entity is a VH interface, and the interface is used for transmitting information related to policy control and charging between two operators.

The strategy control and charging system of the visit network also comprises a functional entity and a gateway, wherein the functional entity of the visit network is connected with the visit gateway and the visit strategy charging rule functional entity and is used for processing addressing and message forwarding of the visit strategy charging rule functional entity;

the interface between the function entity of the visit network and the visit policy charging rule function entity is a PP interface and is used for bearing the information related to policy control and charging between the function entity of the visit network and the visit policy charging rule function entity;

the interface between the visiting gateway and the function entity of the visiting network is a Pg interface which is used for bearing the relevant strategy control and the charging information between the visiting gateway and the function entity of the visiting network.

The invention also provides a system for processing policy control and charging under roaming, which comprises a home network and a visited network policy control and charging system, and is characterized in that a functional entity is respectively arranged in the home network and the visited network policy control and charging system and is respectively connected with a home policy charging rule functional entity and a visited policy charging rule functional entity, so that the functional entity of the home network and the functional entity of the visited network are interacted.

The interface between the function entity of home network and the home policy charging rule function entity is PP interface, which is used to bear the information related to policy control and charging between the function entity and the policy and charging rule function entity of home network;

the interface between the functional entity of the visit network and the visit policy charging rule functional entity is a PP interface, and the interface is used for bearing the information related to policy control and charging between the functional entity and the visit policy charging rule functional entity;

the interface between the functional entity of the home network and the functional entity of the visited network is a VH interface, which is used to transfer information between the two operators regarding policy control and charging.

The strategy control and charging system of the visit network also comprises a gateway, the functional entity of the visit network and the visit strategy charging rule functional entity are connected with the visit gateway, and the interface between the gateway and the functional entity of the visit network is a Pg interface.

The invention has the advantages that the PCC framework in the existing 3GPP is perfected, and the flexibility of the network architecture, namely the network topology function, is increased; in addition, the V-PCRF addressing function to the H-PCRF under the roaming condition can be realized, and the addressing function to the PCRF in the current AF and user triggered service flow establishing process can be enhanced.

Drawings

FIG. 1 is a schematic diagram of the architecture of session-based policy control SBLP;

fig. 2 is a schematic diagram of the architecture of a flow-based charging FBC;

FIG. 3 is a schematic diagram of a policy control and charging PCC architecture incorporating SBLP and FBC;

fig. 4 is a schematic diagram of an SPR functional entity of a subscriber subscription information database newly added in a PCC framework;

fig. 5 is a schematic diagram illustrating an architecture for handling policy control and charging PCC during roaming in the prior art;

fig. 6 is a schematic diagram of an architecture for handling policy control and charging PCC under roaming according to a first embodiment of the present invention;

fig. 7 is a flowchart of a V-PCRF addressing an H-PCRF and forwarding a message in a first embodiment of the present invention;

fig. 8 is a flowchart of a V-PCRF addressing an H-PCRF and forwarding a message in a first embodiment of the present invention;

fig. 9 is a flowchart of a V-PCRF addressing an H-PCRF and forwarding a message in a first embodiment of the present invention;

fig. 10 is a schematic diagram of an architecture for handling policy control and charging PCC under roaming according to a second embodiment of the present invention;

fig. 11 is a flowchart of the V-PCRF addressing and message forwarding for the H-PCRF in the second embodiment of the present invention;

fig. 12 is a flowchart of the V-PCRF addressing and message forwarding for the H-PCRF in the second embodiment of the present invention;

fig. 13 is a flowchart of the V-PCRF addressing and message forwarding for the H-PCRF in the second embodiment of the present invention;

fig. 14 is a schematic structural diagram of an application function entity addressing an H-PCRF in a third embodiment of the present invention;

fig. 15 is a flowchart of the AF of the home network addressing the H-PCRF and forwarding the message in the third embodiment of the present invention;

fig. 16 is a flowchart of the AF of the home network addressing the H-PCRF and forwarding the message in the third embodiment of the present invention;

fig. 17 is a flowchart of the AF of the home network addressing the H-PCRF and forwarding the message in the third embodiment of the present invention;

fig. 18 is a flowchart of the AF of the visited network and the third party network addressing the H-PCRF and forwarding the message in the third embodiment of the present invention;

fig. 19 is a flowchart of the AF of the visited network and the third party network addressing the H-PCRF and forwarding the message in the third embodiment of the present invention;

fig. 20 is a flowchart of the AF of the visited network and the third party network addressing the H-PCRF and forwarding the message in the third embodiment of the present invention;

fig. 21 is a schematic diagram illustrating an addressing structure of a PCRF in a service flow establishment procedure triggered by a user in a non-roaming state in the fourth embodiment of the present invention;

fig. 22 is a flowchart illustrating an addressing procedure of a PCRF in a non-roaming service flow establishment procedure triggered by a subscriber in a fourth embodiment of the present invention;

fig. 23 is a flowchart illustrating an addressing procedure of a PCRF in a service flow establishment procedure triggered by a subscriber in non-roaming in the fourth embodiment of the present invention;

fig. 24 is a flowchart illustrating an addressing procedure of a PCRF in a non-roaming service flow establishment procedure triggered by a subscriber in a fourth embodiment of the present invention;

fig. 25 is a schematic diagram of an addressing structure of an H-PCRF in a service flow establishment procedure triggered by a subscriber in roaming according to a fourth embodiment of the present invention;

fig. 26 is a flowchart illustrating an H-PCRF addressing procedure in a service flow establishment procedure triggered by a subscriber during roaming in the fourth embodiment of the present invention;

fig. 27 is a flowchart illustrating an H-PCRF addressing procedure in a service flow establishment procedure triggered by a subscriber during roaming in the fourth embodiment of the present invention;

fig. 28 is a flowchart illustrating an H-PCRF addressing procedure in a service flow establishment procedure triggered by a subscriber during roaming in the fourth embodiment of the present invention;

fig. 29 is a schematic diagram of an addressing structure of an H-PCRF in a service flow establishment procedure triggered by a subscriber in roaming according to a fourth embodiment of the present invention;

fig. 30 is a flowchart illustrating an H-PCRF addressing procedure in a service flow establishment procedure triggered by a subscriber during roaming in the fourth embodiment of the present invention;

fig. 31 is a flow chart of an H-PCRF addressing procedure in a service flow establishment procedure triggered from a user under roaming in the fourth embodiment of the present invention;

fig. 32 is a flowchart illustrating an H-PCRF addressing procedure in a service flow establishment procedure triggered by a subscriber during roaming in the fourth embodiment of the present invention.

Detailed Description

The present invention will be described in detail below with reference to the accompanying drawings.

The invention relates to a method and a system for processing policy control and charging. Wherein, the method comprises the following steps: setting a functional entity in the policy control and charging system, and processing the addressing and message forwarding of the home policy charging rule functional entity under roaming by the functional entity; or address and forward messages to the policy charging rule function entity of the network under non-roaming.

The method increases the flexibility of the network architecture, namely the network topology function, and plays a role in hiding the network topology structure. In addition, the addressing function of the PCRF in the current AF and user-triggered service flow establishment process is enhanced.

The name of the functional entity is not limited, and the functional entity is referred to as an Interrogating policy and charging rule function (I-PCRF) entity in this embodiment.

Example one

Fig. 6 is a schematic diagram of an architecture for handling policy control and charging PCC under roaming according to a first embodiment of the present invention. The inquiring policy charging rule function I-PCRF entity is arranged in a home network and is connected with at least one policy charging rule function H-PCRF entity of the home network, namely a home policy charging rule function (H-PCRF1, H-PCRF2.

As shown in fig. 6, in this embodiment, an interface between an I-PCRF entity and an H-PCRF entity is implemented, and the name of the interface is not limited. In this embodiment, the interface is referred to as a PP interface, and is used to carry a message that includes PCC related information, such as policy, charging, PCRF routing query, and the like, sent between an I-PCRF entity and an H-PCRF entity under roaming.

In addition, an interface between the I-PCRF entity and the V-PCRF entity is realized, and the name of the interface is not limited. In this embodiment, the interface is referred to as a VH interface, and the interface is an interface between the PCRFs of two operators, and is mainly used for transmitting messages of PCC related information between the two operators, such as service quality policy, charging, PCRF routing query, and the like, for a user.

The I-PCRF entity processes the addressing and message forwarding functions of the V-PCRF entity to the H-PCRF entity, and the steps are as follows: a routing query function, namely obtaining address information of an H-PCRF entity of a user according to a local policy or a query SPR (surface plasmon resonance) and the like, and locally storing the address information for subsequent calling of a message of the same user or subsequent carrying in a reply message; a message caching and forwarding function; and generating a charging information function. Wherein the function of generating charging information is optional.

As shown in fig. 7, the V-PCRF entity addresses the H-PCRF entity and forwards the message, and the following steps are adopted: a V-PCRF entity sends an address query request message to the I-PCRF entity (see step 1); after the I-PCRF entity receives the address query request message, the address information of the H-PCRF entity is queried, and the query result is fed back to the V-PCRF entity through the address query response message (see step 2); and after obtaining the address information, the V-PCRF entity sends the user policy control and charging request message to the H-PCRF entity (see step 3). And the H-PCRF entity returns a policy control and charging response message to the V-PCRF entity after receiving the request message (see step 4). In the above embodiment, the I-PCRF entity does not forward the message.

As shown in fig. 8, the V-PCRF entity addresses the H-PCRF entity and forwards the message, and the following steps are adopted: the V-PCRF entity sends a roaming user policy control and charging request message to an I-PCRF entity (see step 1); the I-PCRF entity inquires the address information of the H-PCRF entity and locally stores the address information for later calling the information of the same user, and then forwards the roaming user policy control and charging request information to the H-PCRF entity (see steps 2 and 3). And the H-PCRF entity returns a policy control and charging response message to the V-PCRF entity after receiving the request message (see steps 4 and 5). In addition, in the response message to the V-PCRF entity, the H-PCRF entity address information of the user is forwarded to the V-PCRF entity through the I-PCRF, and the process is repeated according to the path (see steps 6, 7, 8 and 9).

In addition, as shown in fig. 9, the V-PCRF entity may further adopt the following steps for addressing and forwarding the message to the H-PCRF entity:

the V-PCRF entity sends a user message to the I-PCRF entity (see step 1), wherein the user message carries address information of the V-PCRF entity; the I-PCRF entity inquires address information of the H-PCRF entity and forwards the user message to the H-PCRF entity (see steps 2 and 3); after receiving the user message, the H-PCRF entity sends a response message, and the response message is forwarded to the V-PCRF entity through the I-PCRF entity (see steps 4 and 5); or directly sending the response message to the V-PCRF entity (see steps 4 'and 5'), wherein the response message carries the address information of the H-PCRF entity; then, the V-PCRF entity directly sends a message of subsequently receiving the policy and charging of the user to the H-PCRF entity (see step 6), and the H-PCRF entity directly sends a response message to the V-PCRF (see steps 6 and 7).

In the embodiments shown in fig. 7, fig. 8 and fig. 9, the I-PCRF entity obtains the address information of the H-PCRF entity according to the local policy or by querying the SPR. But not limited to these two ways, and can also be obtained by other ways, which are not described herein again.

Example two

Fig. 10 is a schematic diagram of an architecture for handling policy control and charging PCC under roaming according to a second embodiment of the present invention. The I-PCRF entity is respectively arranged in the home network and the visit network, the I-PCRF entity of the home network is connected with the H-PCRF entity, and the I-PCRF entity of the visit network is connected with the V-PCRF entity, so that the I-PCRF of the home network interacts with the I-PCRF of the visit network.

As shown in fig. 10, in this embodiment, an interface between an I-PCRF entity and an H-PCRF entity of a home network is implemented, and the name of the interface is not limited. In this embodiment, the interface is referred to as a PP interface, and is used to carry a message that includes PCC related information, such as policy, charging, PCRF routing query, and the like, sent between an I-PCRF entity and an H-PCRF entity under roaming.

In addition, an interface between the I-PCRF entity and the V-PCRF entity of the visited network is realized, and the name of the interface is not limited. In this embodiment, the interface is referred to as a PP interface, and is used to carry a message that includes PCC related information, such as policy, charging, PCRF routing query, and the like, sent between an I-PCRF entity and a V-PCRF entity under roaming.

In addition, the interface between the I-PCRF entity of the visited network and the I-PCRF entity of the home network is realized, and the name of the interface is not limited. In this embodiment, the interface is referred to as a VH interface, and the interface is an interface between the PCRFs of two operators, and is mainly used for transmitting messages of PCC related information between the two operators, such as service quality policy, charging, PCRF routing query, and the like, for a user.

The I-PCRF entity processes the addressing and message forwarding functions of the V-PCRF entity to the H-PCRF entity, and the steps are as follows: the routing query function, namely in the visited network, the I-PCRF entity of the visited network completes the addressing and message forwarding functions of the I-PCRF entity in the home network, obtains the address information of the I-PCRF entity of the user home network according to the local policy or query SPR and other modes, and stores the address information locally for calling the message of the same user subsequently; in a home network, an I-PCRF entity of the home network completes the functions of addressing and message forwarding of the H-PCRF entity, obtains the address information of the H-PCRF entity of a user according to local strategies or modes such as SPR inquiry and the like, and stores the address information locally for calling the message of the same user later or carrying the address information in a reply message later; a message caching and forwarding function; and generating a charging information function. Wherein the function of generating charging information is optional.

As shown in fig. 11, the V-PCRF entity addresses the H-PCRF entity and forwards the message under roaming, and the following steps are adopted: the V-PCRF entity sends an address query request message for querying address information of an H-PCRF entity of the roaming user to an I-PCRF entity of the visited network (see step 1); the I-PCRF entity of the visited network sends the address query request message to the I-PCRF entity of the home network (see step 2); after receiving the address query request message, the I-PCRF entity of the home network queries the address information of the H-PCRF entity, feeds back the query result to the I-PCRF entity through the address query response message, and then feeds back to the V-PCRF entity (see steps 3 and 4); after obtaining the address of the H-PCRF entity, the V-PCRF entity sends a policy control and charging request message of a roaming user to the H-PCRF entity (see step 5); the H-PCRF entity then returns a policy control and charging response message to the V-PCRF entity (see step 6). In the above embodiment, the I-PCRF entity does not forward the message.

In addition, as shown in fig. 12, the V-PCRF entity addresses the H-PCRF entity and forwards the message under roaming, and the following steps are adopted: the V-PCRF entity sends a policy control and charging request message of the roaming user to an I-PCRF entity of the visited network (see step 1); the I-PCRF entity of the visited network inquires the address information and local storage of the I-PCRF entity of the home network for subsequent calling of the same user message, and forwards the policy control and charging request message of the roaming user to the I-PCRF entity of the home network (see steps 2 and 3); an I-PCRF entity of a home network inquires address information of an H-PCRF entity of a user and locally stores the address information for later calling the information of the same user, and forwards a policy control and charging request message of a roaming user to the H-PCRF entity (see steps 4 and 5); and after receiving the information, the H-PCRF entity returns a policy control and charging response message to the V-PCRF entity (see steps 6, 7 and 8). In addition, in a response message to the V-PCRF entity, the H-PCRF entity address information of the user is forwarded to the V-PCRF entity through the I-PCRF entities of the home network and the visited network, and the subsequent process is repeated according to the path (see steps 9-14).

As shown in fig. 13, the V-PCRF entity may further adopt the following steps for addressing and message forwarding the H-PCRF entity:

the V-PCRF entity sends a user message to an I-PCRF entity of a visited network, wherein the user message carries address information of the V-PCRF entity (see step 1); the I-PCRF entity of the visited network inquires the address information of the I-PCRF entity of the home network and forwards the user message to the I-PCRF entity of the home network (see steps 2 and 3); the I-PCRF entity of the home network inquires the address information of the H-PCRF entity of the user and forwards the user information to the H-PCRF entity (see steps 4 and 5); after receiving the user message, the H-PCRF entity sends a response message, and the response message is forwarded to the V-PCRF entity through an I-PCRF entity of a home network and a visited network (see steps 6-8); or directly sending the response message to the V-PCRF entity (step 6 '-8'), wherein the response message carries the address information of the H-PCRF entity; and the V-PCRF entity directly sends the subsequent messages of receiving the policy and charging of the user to the H-PCRF entity, and the H-PCRF entity sends the response messages to the V-PCRF entity (see steps 9 and 10).

In the above steps, the I-PCRF entity of the home network inquires the address information of the H-PCRF entity of the user according to a local policy or an SPR inquiry mode.

And the I-PCRF entity of the visited network inquires the address information of the I-PCRF entity of the home network in a mode including inquiring from a local policy or SPR (surface plasmon resonance).

However, the above query method is not limited to the above two methods, and other methods may be adopted, which are not described herein again.

EXAMPLE III

In the embodiment, an Application Function (AF) entity in the PCC is connected with an I-PCRF entity of a network to which the AF entity belongs, and is communicated with an H-PCRF entity.

Fig. 14 is a schematic structural diagram of an AF entity addressing an H-PCRF according to a third embodiment of the present invention. When an AF entity receives service information and determines interaction with a related PCRF, the AF entity firstly sends an H-PCRF address query request to the corresponding I-PCRF according to an I-PCRF address configured on the AF entity or obtained by other methods; after receiving the request message, the I-PCRF obtains H-PCRF information required by AF through local policy or further querying SPR and other modes; and then, the I-PCRF returns the obtained H-PCRF address information to the AF. After obtaining the information, the AF can directly communicate with the obtained H-PCRF, and can also continue to communicate with the H-PCRF through the I-PCRF. The method is suitable for the home network, the visiting network and the AF of the third party network of the non-visiting and home networks.

As shown in fig. 15, when the application function AF entity belongs to a home network, a message flow diagram for communicating with an H-PCRF entity is shown. As shown in the figure, the AF entity is connected with an I-PCRF entity of a home network, and the I-PCRF entity of the home network is connected with a home policy function entity H-PCRF (H-PCRF 1-H-PCRFn).

As shown in fig. 15, the AF entity addresses the H-PCRF entity and forwards the message, and the following steps are adopted: the AF entity sends an address query request message to the I-PCRF entity (see step 1); after receiving the address query request message, the I-PCRF entity queries the address information of the H-PCRF entity and then returns the address information to the AF entity through an address query response message (see step 2); and after obtaining the address information, the AF entity directly sends a user request message to the H-PCRF entity (see step 3). In the above embodiment, the I-PCRF entity does not forward the message.

In addition, as shown in fig. 16, the AF entity addresses the H-PCRF entity and forwards the message, and the following steps are adopted:

the AF entity sends a user message to the I-PCRF entity (see step 1); the I-PCRF entity inquires the address information of the H-PCRF entity and locally stores the address information for later calling the information of the same user, and forwards the user information to the H-PCRF entity (see steps 2 and 3). After that, after receiving the user message, the H-PCRF entity sends a response message, which is forwarded to the AF entity through the I-PCRF entity (see steps 4 and 5), and the following procedure is repeated according to the path (see steps 6, 7, 8 and 9).

In addition, as shown in fig. 17, the AF entity may further adopt the following steps for addressing and forwarding the H-PCRF entity by the AF entity:

the AF entity sends a user message to the I-PCRF entity, wherein the user message carries address information of the AF entity (see step 1);

the I-PCRF entity inquires address information of the H-PCRF entity and forwards the user message to the H-PCRF entity (see steps 2 and 3);

after receiving the user message, the H-PCRF entity sends a response message, and the response message is forwarded to the AF entity through the I-PCRF entity (see steps 4 and 5); or directly sending the response message to an AF entity (see steps 4 'to 5'), wherein the response message carries the address information of the H-PCRF entity;

the AF entity directly sends the message of subsequently receiving the policy and charging of the user to the H-PCRF entity, and the H-PCRF entity directly sends the response message to the AF entity (see steps 6 and 7). And the H-PCRF entity inquires the address information of the H-PCRF entity according to a local policy or an SPR inquiry mode. But is not limited to the two query methods described above.

In addition, when the application function AF entity belongs to a visiting network or a network of a third party, wherein AF is connected with an I-PCRF entity of the belonging network and interacts with the I-PCRF entity of the belonging network, the addressing and message forwarding of the AF entity to the H-PCRF entity are processed.

As shown in fig. 18, the AF entity addresses the H-PCRF entity and forwards the message, and the following steps are adopted: the AF entity sends an address query request message for querying address information of an H-PCRF entity of a user to an I-PCRF entity of a network (see step 1); the I-PCRF entity of the home network sends an address query request message to the I-PCRF entity of the home network (see step 2); after receiving the address query request message, the I-PCRF entity of the home network queries the address information of the H-PCRF entity and feeds back the query result to the AF entity through an address query response message (see steps 3 and 4); after obtaining the address information of the H-PCRF entity, the AF entity sends a user policy control and charging request message to the H-PCRF entity (see step 5); the H-PCRF entity then returns a policy control and charging response message to the AF entity (see step 6). In the above embodiment, the I-PCRF entity does not forward the message.

As shown in fig. 19, the AF entity addresses the H-PCRF entity and forwards the message, and the following steps are adopted: the AF entity sends a user policy control and charging request message to an I-PCRF entity of the network (see step 1); the I-PCRF entity of the affiliated network inquires the address information and local storage of the I-PCRF entity of the affiliated network for subsequent calling of the information of the same user and forwards the user policy control and charging request information to the I-PCRF entity of the affiliated network (see steps 2 and 3); an I-PCRF entity of a home network inquires address information of an H-PCRF entity of a user and stores the address information and the local address information for calling information of the same user later, and forwards a user policy control and charging request message to the H-PCRF entity (see steps 4 and 5); the H-PCRF entity then returns a policy control and charging response message to the AF entity (see steps 6, 7, 8). And then the H-PCRF entity sends a response message, forwards the response message to the AF entity through the home network and the I-PCRF entity of the home network, and repeats the process according to the path (see steps 9-14).

As shown in fig. 20, the AF entity may further adopt the following steps for addressing and forwarding the H-PCRF entity by the AF entity:

the AF entity sends a user message to an I-PCRF entity of the network to which the AF entity belongs, wherein the user message carries address information of the AF entity (see step 1); the I-PCRF entity of the network inquires the address information of the I-PCRF entity of the home network and forwards the user message to the I-PCRF entity of the home network (see steps 2 and 3);

the I-PCRF entity of the home network inquires the address information of the H-PCRF entity of the user and forwards the user information to the H-PCRF entity (see steps 4 and 5); after receiving the user message, the H-PCRF entity sends a response message, and the response message is forwarded to the AF entity through the home network and the I-PCRF entity of the home network (see steps 6, 7 and 8); or directly sending the response message to an AF entity (see steps 6 'to 8'), wherein the response message carries the address information of the H-PCRF entity; the AF entity directly sends the information of the strategy and charging of the user to the H-PCRF entity, the H-PCRF entity sends the response information to the AF entity (see steps 9 and 10), wherein, the I-PCRF entity of the home network inquires the address information of the home H-PCRF entity according to the local strategy or the mode of inquiring from SPR. But are not limited to the above two ways.

And the I-PCRF entity of the network inquires the address information of the H-PCRF entity of the home network according to a local policy or an SPR inquiry mode.

Example four

In this embodiment, an addressing and message forwarding for PCRF in a user-triggered service flow establishment procedure is provided.

When gateway GW receives user preset service or other service establishment request information and decides interaction between the gateway GW and PCRF related to the user, GW sends PCRF address query request corresponding to the user to corresponding I-PCRF according to local network I-PCRF functional entity address configured on the gateway GW; after receiving the request message, the I-PCRF functional entity obtains PCRF address information corresponding to the user and needed by the GW, in some manner, for example, in a manner of configuration information thereon or further querying SPR, etc.; and then, the I-PCRF returns the acquired PCRF address information to the GW. After obtaining the information, GW may communicate directly with the PCRF of the obtained address, or may continue to communicate with the PCRF through an I-PCRF functional entity.

Fig. 21 is a schematic view of an addressing structure of a PCRF in a service flow establishment procedure triggered by a subscriber in non-roaming. The I-PCRF entity is connected with a policy and charging rules function (PCRF 1-PCRFn) and is connected with a gateway GW of the network.

The interface between the I-PCRF entity and the PCRF 1-PCRFn is a PP interface and is used for bearing messages which are sent between the I-PCRF entity and the PCRF under non-roaming and contain relevant information such as policy, charging, PCRF routing query and the like; the interface between the gateway and the GW is a PG interface and is used for bearing messages which are sent between an I-PCRF entity and the GW (PCEF) under non-roaming and contain relevant information such as policy, charging, PCRF routing query and the like.

In addition, the interfaces between the PCRF 1-PCRFn entities and the GW still use the Gx interface in the existing protocol.

As shown in fig. 22, the GW addresses the PCRF entity and forwards the message, and the following steps are adopted:

GW sends address inquiry request message to I-PCRF entity of the network (see step 1); after receiving the address query request message, the I-PCRF entity queries the address information of the H-PCRF entity and feeds back the query result to the GW through the address query response message (see step 2); after the GW obtains the address information, it sends the user policy control and charging request message to the PCRF entity corresponding to the user (see step 3). After receiving the request message, the PCRF entity returns a policy control and charging response message to the GW (see step 4). In the above embodiment, the I-PCRF entity does not forward the message.

As shown in fig. 23, the GW addresses the PCRF entity and forwards the message, which may further adopt the following steps:

GW sends the user policy control and charging request message to the I-PCRF entity of the network (see step 1); the I-PCRF entity inquires address information of the PCRF entity and locally stores the address information for calling the information of the same user later, and then forwards the user policy control and charging request information to the corresponding PCRF entity (see steps 2 and 3); after receiving the request message, the PCRF entity forwards a policy control and charging response message to the GW through the I-PCRF entity (see steps 4 and 5), and the process repeats according to the path thereafter (see steps 6, 7, 8, and 9).

In addition, as shown in fig. 24, the GW may also address the PCRF entity and forward the message, and may further adopt the following steps:

GW sends user information to I-PCRF entity, wherein the user information carries GW address information (see step 1); the I-PCRF entity inquires address information of the PCRF entity and then forwards the user message to the PCRF entity (see steps 2 and 3); after receiving the user message, the PCRF entity sends a response message, and the response message is forwarded to GW through the I-PCRF entity (see steps 4 and 5); or directly sending the response message to GW (see step 4 'to 5'), wherein the response message carries address information of the PCRF entity; and the GW directly sends the subsequent messages of receiving the policy and the charging of the user to the PCRF entity, and the PCRF entity sends the response messages to the GW (see steps 6 and 7).

As shown in fig. 25, a schematic diagram of an addressing structure of an H-PCRF for a traffic flow establishment procedure triggered from a subscriber under roaming is shown. Wherein, an I-PCRF entity is respectively arranged in a visiting network and a home network, wherein,

an I-PCRF entity of a visit network is connected with a V-PCRF entity and a visit gateway (V-GW), and an I-PCRF entity of a home network is connected with an H-PCRF entity, so that the V-PCRF entity interacts with the I-PCRF entity of the home network, and addressing and message forwarding of the V-GW to the H-PCRF entity in a service flow establishing process triggered by a user are processed.

The I-PCRF entity in the visited network mainly completes the addressing and message forwarding functions of the V-PCRF, and the I-PCRF entity in the home network mainly completes the addressing and message forwarding functions of the home H-PCRF. The functions are subdivided as follows: obtaining the address information of a default V-PCRF and an H-PCRF of a user in a visited network according to local strategies or SPR inquiry and other modes, and locally storing the address information for calling the information of the same user later, namely a routing inquiry function; a message caching and forwarding function; a charging information function (optional) is generated.

As shown in fig. 26, the addressing and message forwarding of the H-PCRF entity by the V-GW adopts the following steps:

after receiving a policy and charging request of a user, the V-GW queries a PCRF corresponding to the user from an I-PCRF entity of the visited network, and feeds back address information of the V-PCRF in the default visited network to the V-GW after judging that the user is a roaming user (see steps 1 and 2); the V-GW sends a policy and charging request message of the user to a V-PCRF entity (see step 3); the V-PCRF entity addresses the H-PCRF entity and forwards the message, which is the method described in the first embodiment, and is not described herein again (see step 4).

After receiving the policy control and charging response message, the V-PCRF entity forwards the policy control and charging response message to the V-GW (see step 5), and the following procedure is repeated according to the path (see steps 6, 7, 8).

As shown in fig. 27, the V-GW may further perform the following steps for addressing and message forwarding to the H-PCRF entity:

after receiving the policy and charging request of the user, the V-GW sends the policy and charging request message of the user to an I-PCRF entity of the visited network (see step 1); the I-PCRF entity of the visited network inquires the PCRF entity corresponding to the user and stores the entity locally, and after judging that the entity is a roaming user, the policy and charging request message of the user is sent to a default V-PCRF entity (see steps 2 and 3); the V-PCRF entity addresses the H-PCRF entity and forwards the message, which is the method described in the first embodiment, and is not described herein again (see step 4).

After receiving the policy control and charging response message, the V-PCRF entity forwards the policy control and charging response message to the V-GW through the I-PCRF entity of the visited network (see steps 5 and 6), and the following procedure is repeated according to the path (see steps 7, 8, 9, 10 and 11).

In addition, as shown in fig. 28, the V-GW may further adopt the following steps for addressing and message forwarding of the H-PCRF entity:

after receiving the policy and charging request of the user, the V-GW sends the policy and charging request message of the user to an I-PCRF entity of the visited network (see step 1); the I-PCRF entity of the visited network inquires the PCRF entity corresponding to the user, and after judging that the user is a roaming user, the policy and charging request message of the user is sent to a default V-PCRF entity (see steps 2 and 3); the V-PCRF entity addresses the H-PCRF entity and forwards the message, which is the method described in the first embodiment, and is not described herein again (see step 4).

After receiving the response message, the V-PCRF entity forwards the policy control and charging response message to the V-GW through an I-PCRF entity of the visited network (see steps 5 and 6); or directly sending the response message to the V-GW (see steps 5 'to 6'), wherein the response message carries the address information of the V-PCRF entity; the flow thereafter repeats along this path (see steps 7, 8, 9).

As shown in fig. 29, a schematic diagram of an addressing structure of an H-PCRF for a traffic flow establishment procedure triggered from a subscriber under roaming. An I-PCRF entity is respectively arranged in a visiting network and a home network, wherein,

the I-PCRF entity of the visited network is connected with the V-PCRF entity and the V-GW, and the I-PCRF entity of the home network is connected with the H-PCRF entity, so that the I-PCRF entity of the visited network is interacted with the I-PCRF entity of the home network, and addressing and message forwarding of the H-PCRF entity by the V-GW in a service flow establishing process triggered by a user are processed.

The I-PCRF entity of the visited network mainly completes the addressing and message forwarding functions of the V-PCRF and the I-PCRF entity of the home network; the I-PCRF entity of the home network mainly completes the functions of addressing and message forwarding of the H-PCRF entity. The functions are subdivided as follows: obtaining the address information of a default V-PCRF and an H-PCRF of a user in a visited network according to local strategies or SPR inquiry and other modes, and locally storing the address information for calling the information of the same user later, namely a routing inquiry function; a message caching and forwarding function; a charging information function (optional) is generated.

As shown in fig. 30, the addressing and message forwarding of the H-PCRF entity by the V-GW adopts the following steps:

after receiving a policy and charging request of a user, the V-GW queries a PCRF entity corresponding to the user from an I-PCRF entity in a visited network, and feeds back address information of the V-PCRF entity in the default visited network to the V-GW after judging that the user is a roaming user (see steps 1 and 2); the V-GW sends the policy and charging request message of the user to the V-PCRF entity, and the V-PCRF entity makes a local decision on the policy and charging request of the user according to a local policy and charging rule (see step 3); after allowing the user to pass, the V-PCRF entity addresses and forwards the H-PCRF entity, and the method for addressing and forwarding the message may adopt the method described in embodiment two, which is not described herein again (see step 4);

after receiving the policy control and charging response message, the V-PCRF entity directly forwards the policy control and charging response message to the V-GW (see step 5), and the following procedure is repeated according to the path (see steps 6, 7, 8).

In addition, as shown in fig. 31, the V-GW may further adopt the following steps for addressing and message forwarding of the H-PCRF entity:

after receiving the policy and charging request of the user, the V-GW sends the policy and charging request message of the user to an I-PCRF in the visited network (see step 1);

an I-PCRF in a visited network inquires a PCRF entity corresponding to a user and locally stores the PCRF address information, after judging that the user is a roaming user, a policy and charging request message of the user is sent to a V-PCRF, and the V-PCRF makes a local decision for the policy and charging request of the user according to local policy and charging rules (see steps 2 and 3);

after allowing the user to pass, the V-PCRF entity addresses and forwards the H-PCRF entity, and the method for addressing and forwarding the message may adopt the method described in embodiment two, which is not described herein again (see step 4);

after receiving the policy control and charging response message, the V-PCRF entity forwards the policy control and charging response message to the V-GW through the I-PCRF entity of the visited network (see steps 5 and 6), and the following procedure is repeated according to the path (see steps 7, 8, 9, 10, and 11).

As shown in fig. 32, the V-GW may further adopt the following steps for addressing and message forwarding to the H-PCRF entity:

an I-PCRF in a visited network inquires a PCRF entity corresponding to a user, and after judging that the user is a roaming user, a policy and charging request message of the user is sent to a V-PCRF, and the V-PCRF makes a local decision on the policy and charging request of the user according to a local policy and charging rule (see steps 2 and 3);

after the V-PCRF entity receives the strategy control and charging response message, the strategy control and charging response message is forwarded to the V-GW through the I-PCRF entity of the visited network (see steps 5 and 6); or directly sending the response message to the V-GW (see the steps 5 'to 6'), wherein the response message carries the address information of the V-PCRF entity; the flow thereafter repeats along this path (see steps 7, 8, 9).

In the above embodiment, in addition to the proposed new functional entity, i.e. the query policy and charging rule function I-PCRF entity, the visited policy and charging control function V-PCRF and the home policy and charging control function H-PCRF only need to handle their own policy making and decision functions; other functional entities may process the original functions, which is the same as in the prior art and is not described herein again.

The method is not limited to the PCC architecture in 3GPP, and the method of the present invention may be adopted in any architecture related to PCC in other systems as long as the entity I-PCRF and the interface and function having the same function are adopted.

The above examples are intended to illustrate the invention, but not to limit the invention.

Claims

1. A method for processing policy control and charging is characterized in that a functional entity is arranged in a policy control and charging system, and the functional entity is used for processing addressing and message forwarding of a home policy charging rule functional entity under roaming or addressing and message forwarding of a policy charging rule functional entity of a network under non-roaming.

2. The method of claim 1, wherein the functional entity is configured in a home network and connected to at least one home policy charging rules function entity under roaming, and the functional entity interacts with a policy charging rules function entity of the visited network, and handles addressing and message forwarding of the home policy charging rules function entity by the visited policy charging rules function entity through the functional entity.

3. The method for processing policy control and charging according to claim 2, wherein the visited policy charging rules function entity addresses the home policy charging rules function entity and forwards the message, comprising the steps of:

4. The method for processing policy control and charging according to claim 3, wherein the visited policy charging rules function entity queries the address information of the home policy charging rules function entity of the user from the function entity, comprising the steps of:

5. The method for processing policy control and charging according to claim 2, wherein the visiting policy charging rules function entity addresses and forwards the message to the home policy charging rules function entity, comprising the steps of:

6. The method for processing policy control and charging according to claim 2, wherein the visiting policy charging rules function entity addresses and forwards the message to the home policy charging rules function entity, comprising the steps of:

7. The method of claim 4, 5 or 6, wherein the functional entity queries address information of the home policy charging rules functional entity according to a local policy or by querying a subscriber subscription information database.

8. A method for handling policy control and charging according to claim 2, wherein an interface between said functional entity and the home policy charging rules functional entity is implemented to carry policy control and charging related messages between the functional entity and the home policy charging rules functional entity.

9. A method for handling policy control and charging according to claim 2, characterized in that an interface between said functional entity and a visited policy charging rules functional entity is implemented to transfer policy control and charging related information between two operators.

10. Method for handling policy control and charging according to claim 1, wherein a functional entity is provided in the visited network and in the home network, respectively, wherein,

11. The method for processing policy control and charging according to claim 10, wherein the visited policy charging rules function entity addresses the home policy charging rules function entity and forwards the message, comprising the steps of:

12. The method for processing policy control and charging according to claim 11, wherein the functional entity of the visited network queries the functional entity of the home network for address information of the home policy charging rules functional entity, comprising the steps of:

13. The method for processing policy control and charging according to claim 10, wherein the visited policy charging rules function entity addresses the home policy charging rules function entity and forwards the message, comprising the steps of:

14. The method for processing policy control and charging according to claim 10, wherein the visited policy charging rules function entity addresses the home policy charging rules function entity and forwards the message, comprising the steps of:

15. The method of claim 13 wherein the functional entity of the visited network queries the address information of the functional entity of the home network according to a local policy or by querying a subscriber subscription information database.

16. The method of handling policy control and charging according to claim 10 wherein an interface between a functional entity of the home network and the home policy charging rules functional entity is implemented to carry policy control and charging related messages between the functional entity and the home policy charging rules functional entity;

17. Method for handling policy control and charging according to claim 10, wherein an interface between a functional entity of the visited network and a functional entity of the home network is implemented for transferring policy control and charging related information between two operators.

18. The method of handling policy control and charging according to claim 1 wherein the application function entity is connected to a function entity of the network to which it belongs, through which the addressing and message forwarding of the application function entity to the home policy charging rules function entity is handled.

19. The method of claim 18, wherein the application function entity belongs to a home network, and wherein the functional entity connected to the application function entity is connected to at least one home policy charging rules function entity.

20. The method of handling policy control and charging according to claim 19 wherein the addressing and message forwarding of the home policy charging rules function by the application function comprises the steps of:

21. The method of handling policy control and charging according to claim 19 wherein the addressing and message forwarding of the home policy charging rules function by the application function comprises the steps of:

an application functional entity sends a user message to the functional entity;

22. The method of handling policy control and charging according to claim 19 wherein the addressing and message forwarding of the home policy charging rules function by the application function comprises the steps of:

23. The method of handling policy control and charging according to claim 18 wherein said application function entity belongs to a 3rd party network being a visited network or a non-home, non-visited network; the home network is also provided with a functional entity which is connected with at least one home policy charging rule functional entity.

24. The method of handling policy control and charging according to claim 23 wherein the addressing and message forwarding of the home policy charging rules function by the application function comprises the steps of:

25. The method of handling policy control and charging according to claim 23 wherein the addressing and message forwarding of the home policy charging rules function by the application function comprises the steps of:

26. The method of handling policy control and charging according to claim 23 wherein the addressing and message forwarding of the home policy charging rules function by the application function comprises the steps of:

27. The method of claim 1, wherein the functional entity is connected to a gateway of the home network and at least one policy charging rules function entity under non-roaming, and the gateway addresses and forwards messages to the policy charging rules function entity during the user-triggered service flow establishment process.

28. The method for handling policy control and charging according to claim 27 wherein the addressing and message forwarding of the policy charging rules function by the gateway comprises the steps of:

29. The method for handling policy control and charging according to claim 27 wherein the addressing and message forwarding of the policy charging rules function by the gateway comprises the steps of:

the gateway sends the user message to the functional entity;

30. The method for handling policy control and charging according to claim 27 wherein the addressing and message forwarding of the policy charging rules function by the gateway comprises the steps of:

31. A method for handling policy control and charging according to claim 27 wherein an interface between said gateway and a functional entity is implemented to carry policy control and charging related messages between the functional entity and the gateway.

32. The method of handling policy control and charging according to claim 1 wherein a functional entity is provided in the visited network and the home network, respectively, under roaming, wherein,

the visiting network function entity is connected with the visiting strategy charging rule function entity and the visiting gateway, the home network function entity is connected with the home strategy charging rule function entity and the visiting strategy charging rule function entity, and the visiting gateway addresses and forwards the message of the home strategy charging rule function entity in the process of establishing the service flow triggered by the user through the visiting network and the home network function entity.

33. The method of handling policy control and charging according to claim 32 wherein the addressing and message forwarding of the home policy charging rules function entity by the visited gateway comprises the steps of:

34. The method of handling policy control and charging according to claim 32 wherein the addressing and message forwarding of the home policy charging rules function entity by the visited gateway comprises the steps of:

35. The method of handling policy control and charging according to claim 32 wherein the addressing and message forwarding of the home policy charging rules function entity by the visited gateway comprises the steps of:

36. The method of handling policy control and charging according to claim 1 wherein a functional entity is provided in the visited network and the home network, respectively, under roaming, wherein,

the visiting network function entity is connected with the visiting strategy charging rule function entity and the visiting gateway, the home network function entity is connected with the home strategy charging rule function entity and the visiting network function entity, and the visiting gateway addresses and forwards the home strategy charging rule function entity in the process of establishing the service flow triggered by the user through the visiting network and the home network function entity.

37. The method of handling policy control and charging according to claim 36 wherein the addressing and message forwarding of the home policy charging rules function entity by the visited gateway comprises the steps of:

38. The method of handling policy control and charging according to claim 36 wherein the addressing and message forwarding of the home policy charging rules function entity by the visited gateway comprises the steps of:

39. The method of handling policy control and charging according to claim 36 wherein the addressing and message forwarding of the home policy charging rules function entity by the visited gateway comprises the steps of:

40. A system for processing policy control and charging under roaming includes a home network and a policy control and charging system of a visit network, and is characterized in that a functional entity is set in the policy control and charging system of the home network and is respectively connected with a home policy charging rule functional entity and a visit policy charging rule functional entity, so that the visit policy charging rule functional entity interacts with the functional entity of the home network.

41. The system for handling policy control and charging under roaming according to claim 40, wherein the interface between the functional entity and home policy charging rules functional entity is a PP interface;

42. The system for handling policy control and charging under roaming of claim 40, wherein the policy control and charging system of the visited network further comprises a functional entity and a gateway, the functional entity of the visited network is connected with the visited gateway and the visited policy charging rules functional entity for handling addressing and message forwarding to the visited policy charging rules functional entity;

43. A system for processing policy control and charging under roaming includes a home network and a visited network policy control and charging system, and is characterized in that a functional entity is respectively set in the home network and the visited network policy control and charging system, and is respectively connected with a home policy charging rule functional entity and a visited policy charging rule functional entity, so that the functional entity of the home network interacts with the functional entity of the visited network.

44. The system for handling policy control and charging under roaming according to claim 43, wherein the interface between the functional entity of the home network and the home policy charging rules functional entity is a PP interface for carrying policy control and charging related messages between the functional entity and the policy and charging rules functional entity of the home network;

45. The system for handling policy control and charging under roaming of claim 44, wherein the policy control and charging system of the visited network further includes a gateway, the functional entity of the visited network and the functional entity of the visited policy charging rules are connected to the visited gateway, and the interface between the gateway and the functional entity of the visited network is Pg interface.