CN103200151A - Method and system of policy and charging control (PCC) conversation binding in network address translation (NAT) deployment environment and policy and charging rule function (PCRF) - Google Patents

Abstract

The invention discloses a PCC session binding method in a NAT deployment environment, comprising: PCRF receives the first address of the UE reported by the PCEF and the second address reported by the AF; binds the PCEF according to whether the first address and the second address are the same A session with PCRF and between AF and PCRF; wherein, when the first address and the second address are not the same, obtain the address mapping conversion relationship of the UE created by the NAT device; according to the second address and the address Mapping the mapping relationship in the conversion relationship, querying the third address corresponding to the second address; comparing whether the first address and the third address are the same to bind the sessions between the PCEF and the PCRF and between the AF and the PCRF. The invention can ensure that PCRF performs session binding under NAT environment. In addition, the invention also discloses a PCC session binding system and PCRF under the NAT deployment environment.

Description

PCC session binding method, system and PCRF in a NAT deployment environment

technical field

The invention relates to a PCC session binding method. Specifically, the method is applied in a NAT deployment environment and belongs to the field of network communication.

Background technique

The PCC (Policy and Charging Control) architecture is the QoS (Quality of Service) guarantee mechanism of the next-generation core network evolution SAE (System Architecture Evolution) project, which is characterized by the business flow as the granularity and high-level mechanism The end-to-end QoS solution, in which, through this architecture, the network can detect different service flows, and realize QoS control, billing and other requirements for the service flows.

FIG. 1 is a schematic diagram of a PCC networking architecture in the prior art;

As shown in Figure 1, the PCC architecture shown includes the following functional entities: AF (Application Function, application function entity), PCRF (Policy and Charging Rule Fuction, policy and charging control unit), PCEF (Policy and Charging Enforcement Function , policy and charging execution unit), BBERF (Bearing Binding and Event Report Function, bearer binding and event report functional entity), SPR (Subscription Profile Repository, user attribute storage), OCS (Online Charging System, online charging system) And OFCS (Offline Charging System, offline charging system).

Among them, PCRF (Policy and Charging Rule Function, policy and charging control unit) is the centralized decision-making point of QoS rules, and its decision-making input comes from the service information (service flow) provided by the Rx interface of AF (Application Function, application function entity). Description, service flow bandwidth requirements, service streaming media type, service ID), user ID and user subscription information contained in SPR, locally configured operator policies, PCRF generates authorized QoS rules and sends them to PCEF (Policy and ChargingEnforcement Fucntion, policy and charging enforcement unit), and the PCEF executes the policy according to the authorized QoS rules.

Under the 3GPP network, PCRF generates authorized QoS rules and issues them to PCEF (implemented by P-GW under LTE, and GGSN under 2G/3G), and PCEF implements policies according to authorized QoS rules; under non-3GPP networks (such as WLAN, Wimax), the PCRF generates the authorized QoS rules and sends them to the BBERF, and the BBERF executes the policy according to the authorized QoS rules.

QoS rules mainly include two parts: the description of business flow and related QoS parameters. Wherein, the QoS parameters mainly include ARP (for determining the priority of bearer resource acquisition), QCI (representing quality requirements such as forwarding priority, packet loss rate, bit error rate, etc.) and bandwidth requirements.

Based on the PCC architecture, when the UE initially attaches to the network, an IP-CAN session between the user terminal and the network side is established, and the UE develops its own business based on the established IP-CAN session. See Figure 2.

According to Figure 2 and Figure 3, a brief description of the process in the above figure is as follows:

Steps 301 to 302: The PCEF receives the IP-CAN session establishment request message sent by the UE (Gx interface, using the Diameter protocol), and requests the PCRF to issue the default PCC rules of the UE. For the convenience of expression, it is called PCEF and PCRF The session between is session one.

In the above process, it is required to provide the address of the UE to the PCRF after step 302 or step 310 (not shown in the above figure, used in the scenario where the PCEF cannot obtain the address of the UE at step 302). In step 302, the user identity (IMSI or MSISDN) of the UE also needs to be carried.

The IP-CAN session established by the process shown in the above figure establishes a default bearer between UE and PCEF. Based on the default bearer established in session 1, UE can initiate a service request, such as a login request or an IMS Invite request. wait.

In addition, in order to control the services to be carried out by the UE, it is necessary to formulate appropriate PCC rules for the services requested by the UE. Therefore, under the PCC architecture, it is also necessary to control the services of the UE. The following figure is a flow chart of the service control of the UE under the PCC architecture.

A brief description of the process follows:

Step 401 to Step 403:

After the AF is triggered, define the service information of the UE, send the service information of the UE to the PCRF through an Rx interface message (AAR message), and initiate a session between the AF and the PCRF.

Wherein, the service information of the UE may include a network address of the UE, a network identifier, service data flow description information, an identifier of the UE (IMSI or MSISDN) and the like. And for the convenience of expression, the session between the AF and the PCRF may be referred to as session two.

Step 404 , after receiving the AAR message from the AF, the PCRF stores the service information of the UE in it, and if the PCRF does not store user subscription data, then executes step 405 ; otherwise, executes step 407 . Step 405 to Step 406: PCRF sends a request message requesting user subscription data to SPR; SPR returns user subscription data to PCRF after receiving the request message.

Step 407 to Step 409: According to the network address of UE sent by AF in session 2 and the network address of UE received by PCEF in session 1, PCRF

Or through the UE user ID sent in session two and the UE user ID sent by PCEF received in session one (because the AF does not necessarily know the UE user ID—especially in third-party business scenarios—usually The first scheme) is used to bind session 1 and session 2. After the binding is successful, the PCRF formulates and stores the PCC rules, and sends a response to the AF indicating that the session binding is successful, thereby completing the overall process.

However, according to the invention patent application with the application number 200710165713.3, because NAT equipment is usually deployed between the UE, the PDN network and the AF, the AF (usually deployed on the service platform) usually cannot know the private network address of the UE ( Before NAT), the public network address of UE (after NAT) is provided to PCRF, and in session one, PCEF (specifically P-GW in LTE, which is responsible for UE network address allocation, usually a private network address ) The UE address reported to the PCRF is a private network address (before NAT), which leads to the failure of session binding.

Figure 4 is one of the most common NAT deployment environments. As shown in the figure, NAT is usually deployed on the firewall behind the P-GW, and there is a solution that the NAT device realizes one/a few public network addresses proxying multiple UE private network addresses.

In order to realize the data transmission between the service platform (AF) and the UE, the AF must and only needs to know the private network address/port of the UE used for data transmission after NAT conversion of the public network address/port, however, the AF does not necessarily know UE's private network address/port. In point-to-point communication, the other party only needs to know the public network address and port of the other end. Therefore, usually the AF will fill in the public network address/port of the UE in the session, so that the session 1 and session 2 cannot be bound.

In the invention patent application with Chinese patent application number: 200710165713.3, in order to overcome the above-mentioned shortcomings of the prior art, a technical solution is disclosed: the AF reports to the PCRF all the network addresses of the UE (including public network addresses and private network addresses) , and even the relay address), so as to realize the binding of session 1 and session 2. For this reason, the invention patent application of 200710165713.3 requires UE to provide all the above network address information to AF, specifically:

The UE carries all the above-mentioned network addresses of itself in the extension field of the SDP;

The UE fills in all of the above network addresses in the Via field of the SIP message;

The AF extracts all the above network address information from the message initiated by the above UE.

There is following shortcoming in above-mentioned prior art:

First, the UE is required to provide all network address information, which puts higher technical requirements on the UE, and in some scenarios, for example, in the NAT traversal scenario, the network device initiates an address mapping request to the NAT device, and the UE does not know that it is public network address;

Second, it involves the transformation of existing terminals/clients that are already working normally (without PCC network), and the workload is relatively large;

Third, the two methods for the UE to provide all address information provided by the invention patent application of Chinese patent application number 200710165713.3 may not work in actual deployment: when actually deploying IMS/SIP networks, operators usually deploy SBC devices at the edge of their own networks , to realize the full proxy of business messages and media streams (at this time, the SBC will replace the source address of the SIP message and the address in the SDP message), for example, the Via field will be replaced by The public network address after SBC (NAT), so this field cannot be accurately transmitted to AF.

Fourth, the invention patent of Chinese patent application No. 200710165713.3 requires the UE to adopt the SIP/SDP protocol, which is a text-based protocol and is rarely used on mobile terminals.

Contents of the invention

Aiming at the shortcomings of the prior art, the present invention provides a method that can reliably bind session 1 and session 2. Specifically, the technical solution adopted by the present invention is as follows:

A PCC session binding method under a NAT deployment environment, comprising:

The PCRF receives the first address of the UE reported by the PCEF and the second address reported by the AF;

Binding sessions between PCEF and PCRF and AF and PCRF according to whether the first address and the second address are the same; wherein, when the first address and the second address are not the same,

Obtain the address mapping translation relationship of the UE created by the NAT device;

Querying a third address corresponding to the second address according to the mapping relationship between the second address and the address mapping conversion relationship;

Compare whether the first address is the same as the third address to bind the sessions between the PCEF and the PCRF and between the AF and the PCRF.

Wherein, the preferred method is that the address mapping conversion relationship of the UE is a mapping relationship between the UE's private network address and port and the UE's public network address and port.

Further, preferably, the second address of the UE is a private network address of the UE or a public network address of the UE.

After adopting the above technical solution in this embodiment, after introducing the PCC architecture, it can ensure that the PCRF can accurately perform session binding between the PCEF and the PCRF and the AF and the PCRF in the NAT environment, thereby providing the QoS guarantee required by the service flow , with good technical effect.

In addition, the present invention also discloses a PCC session binding system in a NAT deployment environment, including:

The PCEF is used to report the first address of the UE to the PCRF;

The AF is configured to report the second address of the UE to the PCRF;

The NAT device is used to create and provide the address mapping translation relationship of the UE to the PCRF;

PCRF, used to bind the session between PCEF and PCRF and AF and PCRF according to whether the first address and the second address are the same; wherein, when the first address and the second address are not the same,

Obtain the address mapping translation relationship of the UE created by the NAT device;

Querying a third address corresponding to the second address according to the mapping relationship between the second address and the address mapping conversion relationship;

Compare whether the first address is the same as the third address to bind the sessions between the PCEF and the PCRF and between the AF and the PCRF.

After the present invention adopts the above technical scheme, through the interface and query between NAT equipment or data network equipment and PCRF, the technical purpose of PCC session binding under the NAT deployment environment to be protected by the present invention can be realized, which has better technology Effect.

In addition, the present invention also discloses a PCRF, comprising:

An information receiving unit, configured to receive the first address of the UE reported by the PCEF and the second address of the UE reported by the AF;

The first session binding unit is used to bind the session between PCEF and PCRF and AF and PCRF according to whether the first address and the second address are the same;

a translation relationship receiving unit, configured to acquire the address mapping translation relationship of the UE created by the NAT device;

The address conversion unit is configured to query the third address corresponding to the second address according to the mapping relationship between the second address and the address mapping conversion relationship after the first session binding unit fails to bind the session;

The second session binding unit is configured to bind the sessions between the PCEF and the PCRF and between the AF and the PCRF according to whether the first address is the same as the second address or the third address.

After the present invention adopts the above technical scheme, through the design of PCRF, the technical effect of PCC session binding in the NAT deployment environment is realized, and then, through the PCRF, the session binding relationship between PCEF and PCRF and AF and PCRF, It can further provide the purpose of QoS guarantee for the business.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

The present invention will be described in detail below in conjunction with the accompanying drawings and specific embodiments, so as to make the above-mentioned advantages of the present invention more clear.

FIG. 1 is a schematic diagram of a PCC architecture in the prior art;

FIG. 2 is a schematic diagram of establishment of session 1 between PCEF and PCRF in the prior art;

FIG. 3 is a schematic diagram of establishment of session 2 between AF and PCRF in the prior art;

Fig. 4 is a schematic diagram of the system structure under the NAT deployment environment in the prior art;

Fig. 5 is a schematic flow chart of the PCC session binding method under the NAT deployment environment of the present invention;

Fig. 6 is the specific flowchart of the PCC session binding method under the NAT deployment environment of the present invention;

Fig. 7 is a schematic structural diagram of the PCC session binding system under the NAT deployment environment of the present invention;

Fig. 8 is a schematic diagram of the specific structure of the PCRF of the present invention.

Detailed ways

The present invention will be described in detail below in conjunction with the accompanying drawings and specific embodiments.

Method embodiment one:

According to the present invention, a method for binding PCC sessions in a NAT deployment environment is provided;

Wherein, Fig. 5 is a schematic flow chart of the PCC session binding method under the NAT deployment environment of the present invention;

As shown in Figure 5, the method specifically includes:

S101: The PCRF receives the first address of the UE reported by the PCEF and the second address reported by the AF; specifically, in session 1 between the PCRF and the PCEF, the PCRF receives the first address of the UE reported by the PCEF to the PCRF;

In session two between PCRF and AF, PCRF receives the service flow information reported by AF to PCRF, wherein the service flow information includes the second address of the user UE obtained by the service platform AF and the second address of the user UE used for data transmission port, and the second address and port are the address and port after passing through the NAT device.

S102: PCRF binds the session between PCEF and PCRF and AF and PCRF according to whether the first address and the second address are the same;

Wherein, if the first address and the second address are the same, session one and session two are bound;

S103: If the first address and the second address are different;

S104: Obtain the address mapping conversion relationship of the UE created by the NAT device;

S105: Query a third address corresponding to the second address according to the mapping relationship between the second address and the address mapping conversion relationship;

Specifically, the address mapping relationship includes various address/port conversion relationships generated by the NAT device, thus, in this step, PCRF can query from the address mapping conversion relationship according to the second address and port a third address corresponding to the second address;

S106: Compare whether the first address is the same as the third address to bind the session between PCEF and PCRF and AF and PCRF;

Otherwise, the binding is deemed to have failed.

In this embodiment, the PCEF has different manifestations in specific architectures, for example, PCEF can be replaced by BBERF, and PCEF can have different functional entity manifestations in various network environments, which are known in the art What the skilled person can know will not be described in detail here.

After adopting the above-mentioned technical solution in this embodiment, after introducing the PCC architecture, it can ensure that the PCRF can accurately bind session 1 and session 2 in the NAT environment, and then provide the QoS guarantee required by the service flow, which has better technical effect.

Method embodiment two:

The present invention is described in more detail below in conjunction with accompanying drawing;

Wherein, Fig. 6 is a specific flowchart of the PCC session binding method under the NAT deployment environment of the present invention, as shown in Fig. 6, the method specifically further includes:

S201: In session one between the PCRF and the PCEF, the PCRF receives the first address of the UE reported by the PCEF to the PCRF;

Wherein, this step is substantially the same as the steps in the prior art. Specifically, the PCEF receives the IP-CAN session establishment request message sent by the UE, wherein the message adopts the Gx interface and adopts the Diameter protocol. The PCRF requests to deliver the PCC rules of the UE session, and the UE can initiate a specific service request based on the default bearer established in session one, for example, initiate a login request or an IMS Invite request.

Moreover, in order to control the services to be carried out by the UE, it is necessary to formulate appropriate PCC rules for the services requested by the UE.

S202: In session two between PCRF and AF, PCRF receives the service flow information reported by AF to PCRF, wherein the service flow information includes the second address of the user UE acquired by the service platform AF and the second address used for data transmission port, which is mainly used by the UE for IP data transmission;

Specifically, in one embodiment, for example, the AF receives the first message forwarded by the UE, and the message will trigger the AF, so that the AF obtains the second address of the UE from the message, and the AF also The specific port used by the UE for IP data transmission can be obtained from the first message.

Wherein, the second address and port are uniquely determined.

Specifically, the AF carries the obtained second address of the UE in the Rx interface message sent to the PCRF, and sends it to the PCRF together with the obtained port of the UE.

S204: After receiving the Rx interface message, the PCRF compares the second address of the UE sent from the AF side with the first address of the UE sent from the PCEF, wherein,

If the second address of the UE after comparison is the same as the first address of the UE in session one, it is considered that the two sessions are sent by the same UE, so session binding is implemented; and the binding is successful Later, the PCRF formulates and stores the PCC rules, and at the same time, sends a response to the AF indicating that the session binding is successful;

In an environment where a NAT device is provided, generally, the above-mentioned first address and the second address are mostly different. Therefore, the present invention specifically includes before step S204:

S203: PCRF obtains the conversion relationship between the private network address/port mapped by the NAT device and the public network address/port;

Wherein, in a preferred embodiment, the ways of providing the conversion relationship mainly include but are not limited to the following ways:

1. The NAT device actively provides to PCRF each time a pair of address mapping is created/cancelled;

2. The NAT device opens the query interface for PCRF query;

3. Provide the PCRF through a data network device, or open the query interface of the data network device for the PCRF to query, thus, the PCRF obtains the private network address/port and the public network address/port mapped by the NAT device through the above method Mapping and translation relationships between ports.

In this embodiment, the NAT device actively provides the PCRF with the translation relationship between the mapped private network address/port and the public network address/port.

Therefore, after step S204, proceed to step S205: if the first address and the second address are not the same, PCRF extracts the UE address and the port corresponding to the address from the service flow information summary transmitted from AF, and according to the step The conversion relationship between the private network address/port mapped by the NAT device and the public network address/port obtained in S203 is converted to obtain the third address of the UE.

Among them, since the mapping relationship between the network address/port is uniquely determined in the process of data transmission, we can use this conversion relationship and the acquired second address and port of the UE to obtain the UE corresponding the third address of .

And according to this method, the type of the third address and the type of the first address should be the same (public network address or private network address), and then, PCRF combines the obtained third address of the UE with the UE obtained in session one addresses are compared, and if the two addresses are the same, then

S206: Implement the binding between session one and session two; otherwise, determine that the binding fails.

Thus, the present invention can ensure that the PCRF is accurately located in the NAT environment under the network environment of the PCC architecture through the interaction between the PCRF, the NAT device, and the AF, and through the AF providing the address of the UE obtained and the corresponding port. The binding of the session 1 and the session 2 can be carried out under the following conditions, so as to solve the problem caused by the inconsistency of the public network address/private network address in the NAT deployment environment in the prior art.

System embodiment one:

Fig. 7 is a schematic structural diagram of the PCC session binding system under the NAT deployment environment of the present invention, as shown in the figure, in the described embodiment, specifically includes:

PCEF, used for reporting the first address of the UE to the PCRF in session one between the PCRF and the PCEF;

The AF is configured to report service flow information to the PCRF in session two between the PCRF and the AF, wherein the service flow information includes the second address of the user UE obtained by the AF and the corresponding port used for data transmission ;

PCRF, for binding the session between PCEF and PCRF and AF and PCRF according to whether the first address and the second address are the same;

Wherein, when the first address and the second address are different,

Obtain the address mapping translation relationship of the UE created by the NAT device;

Querying a third address corresponding to the second address according to the second address and the mapping relationship in the address mapping conversion relationship;

Compare whether the first address is the same as the third address to bind the sessions between the PCEF and the PCRF and between the AF and the PCRF.

As can be seen from Figure 7, the system further includes:

The NAT device is used to provide PCRF with the translation relationship between the mapped private network address/port and the public network address/port;

Wherein, the above conversion relationship may be directly provided by the NAT device to the PCRF, or may be acquired by the PCRF device inquiring the NAT device.

And in this specific embodiment, also be provided with data network equipment, it is connected with NAT equipment, and is used for storing the conversion relation of private network address/port and public network address/port mapped by NAT equipment, and, this data network equipment An inquiry service may also be provided to the PCRF.

After the present invention adopts the above technical scheme, through the interface and query between NAT equipment or data network equipment and PCRF, the technical purpose of PCC session binding under the NAT deployment environment to be protected by the present invention can be realized, which has better technology Effect.

Device embodiment one:

According to an embodiment of the present invention, a PCRF is disclosed;

Wherein, Fig. 8 is a specific structural schematic diagram of the PCRF of the present invention; as shown in Fig. 8, the PCRF specifically includes:

An information receiving unit, configured to receive the first address of the UE reported by the PCEF and the second address of the UE reported by the AF;

The first session binding unit is used to bind the session between PCEF and PCRF and AF and PCRF according to whether the first address and the second address are the same;

a translation relationship receiving unit, configured to acquire the address mapping translation relationship of the UE created by the NAT device;

The address conversion unit is configured to query the third address corresponding to the second address according to the mapping relationship between the second address and the address mapping conversion relationship after the first session binding unit fails to bind the session;

The second session binding unit is configured to bind the sessions between the PCEF and the PCRF and between the AF and the PCRF according to whether the first address is the same as the second address or the third address.

Wherein, the NAT device is configured to actively provide to the PCRF each time a pair of address mapping is created/cancelled; or, open a query interface for the PCRF to query.

In addition, a data network device is also provided for storing the address mapping conversion relationship of the UE created by the NAT device, and providing it to the PCRF or allowing the PCRF to query it.

Wherein, the address mapping conversion relationship of the UE includes: the mapping relationship between the private network address and the port of the UE and the public network address and the port of the UE.

Wherein, the second address of the UE is a private network address of the UE or a public network address of the UE.

In addition, the PCRF also includes:

The PCC rule generating unit is configured to formulate a PCC rule for a service data flow for a session after the session is successfully bound.

After adopting the above technical solution in the present invention, the PCRF implements PCC session binding under the NAT deployment environment, and further provides QoS guarantee for services, which has good technical effect.

Finally, it should be noted that: the above is only a preferred embodiment of the present invention, and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, for those skilled in the art, it still The technical solutions recorded in the foregoing embodiments may be modified, or some technical features thereof may be equivalently replaced. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. A PCC session binding method in NAT deployment environment comprises the following steps:

the PCRF receives a first address of the UE reported by the PCEF and a second address reported by the AF;

according to whether the first address and the second address are the same or not, the conversation between the PCEF and the PCRF and the conversation between the AF and the PCRF are bound; wherein, when the first address and the second address are not the same,

acquiring an address mapping conversion relation of the UE established by the NAT equipment;

inquiring a third address corresponding to the second address according to the second address and a mapping relation in the address mapping conversion relation;

comparing whether the first address and the third address are the same to bind the sessions between the PCEF and the PCRF and between the AF and the PCRF.

2. The method for binding PCC session in NAT deployment environment according to claim 1, wherein said UE's address mapping translation relationship comprises:

the mapping relation between the private network address and the port of the UE and the public network address and the port of the UE.

3. The PCC session binding method in the NAT deployment environment according to claim 2,

the second address of the UE is a private network address of the UE or a public network address of the UE.

4. The method for binding PCC session in NAT deployment environment according to claim 1, wherein the obtaining of the address mapping translation relationship of the UE created by the NAT device specifically includes: the NAT equipment actively provides the PCRF when creating/canceling a pair of address mapping; or,

the NAT equipment opens a query interface for the PCRF to query; or, the data network device is provided for the PCRF or used for the PCRF to inquire.

5. A PCRF, specifically comprising:

an information receiving unit, configured to receive a first address of the UE reported by a PCEF and a second address of the UE reported by an AF; the first session binding unit is used for binding the sessions between the PCEF and the PCRF and between the AF and the PCRF according to whether the first address and the second address are the same or not;

a translation relation receiving unit, configured to obtain an address mapping translation relation of the UE created by the NAT device;

the address conversion unit is used for inquiring a third address corresponding to the second address according to the mapping relation between the second address and the address mapping conversion relation after the first session binding unit fails to bind the session;

and the second session binding unit is used for binding the sessions between the PCEF and the PCRF and between the AF and the PCRF according to whether the first address and the second address or the third address are the same.

6. The PCRF of claim 5, wherein the address mapping translation of the UE comprises: the mapping relation between the private network address and the port of the UE and the public network address and the port of the UE.

7. The PCRF of claim 5 or 6, wherein the second address of the UE is a private network address of the UE or a public network address of the UE.

8. A system for PCC session binding in a NAT deployment environment, comprising:

the PCEF is used for reporting the first address of the UE to the PCRF;

the AF is used for reporting a second address of the UE to the PCRF;

NAT equipment, which is used to create and provide the address mapping conversion relation of UE to PCRF;

the PCRF is used for binding the conversation between the PCEF and the PCRF and the conversation between the AF and the PCRF according to whether the first address and the second address are the same or not; wherein, when the first address and the second address are not the same,

acquiring an address mapping conversion relation of the UE established by the NAT equipment;

inquiring a third address corresponding to the second address according to the second address and a mapping relation in the address mapping conversion relation;

comparing whether the first address and the third address are the same to bind the sessions between the PCEF and the PCRF and between the AF and the PCRF.

9. The system for PCC session binding in a NAT deployment environment of claim 8, wherein the NAT device is configured to proactively provide to the PCRF whenever a pair of address mappings is created/removed; or, the query interface is opened for the query of the PCRF.

10. The system for PCC session binding in a NAT deployment environment according to claim 8 or 9,

and the data network equipment is used for storing the address mapping conversion relation of the UE established by the NAT equipment and providing the address mapping conversion relation for the PCRF or providing the address mapping conversion relation for the PCRF to inquire.

Images