CN103731812B - Session association method, device, gateway, business side access device and server - Google Patents

Abstract

The present invention provides a session association method, device, gateway, service-side access device, and server. The method is used in DRA, including: establishing a Gx session with any gateway among the plurality of gateways, and After the Gx session is associated with a PCRF, establish a first correspondence between the private network IP address of the user equipment corresponding to the Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF; After establishing the first Rx session with the service-side access device, analyze the first Rx session to obtain the first private network IP address, access source information, and first APN of the first user equipment; The first private network domain corresponding to the source information; determining the first PCRF according to the first correspondence; associating the first Rx session with the first PCRF. The invention can solve the multi-PCRF addressing problem when the existing network address is repeated.

Description

Session association method, device, gateway, service side access device and server

technical field

The present invention relates to the communication field, in particular to a session association method, device, gateway, service-side access device and server.

Background technique

In order to provide users with differentiated services, a Policy Control and Charging (PCC) architecture is introduced into the network. PCC mainly defines policy control and flow-based Multi-dimensional management and control capabilities such as time and access type, and management and control methods including end-to-end priority setting (QoS), flow control, gate control, and differentiated billing.

The basic flow of the existing PCC control is shown in Figure 1. First, the online user logs in to the service server through the Policy and Charging Enforcement Function (PCEF) to perform services. For information exchange in the business aspect, the PA sends the business message to the Policy and Charging Rules Function (PCRF). Further, the PCRF uses the business information from the PA, combines the user's policy and charging control subscription information obtained from the SPR and the information from the The user information of the Gx interface of the PCEF generates a control policy and sends it to the PCEF, and the PCEF executes the policy at the service level, thereby realizing the policy management and control of the user.

The main interfaces in PCC are:

1. Rx, Rx is the reference point between the policy agent (PA) and PCRF, used to transmit business and session information (such as user IP address) from PA to PCRF, and PCRF makes policy decisions based on business and other information.

2. Gx, Gx is the reference point between PCEF and PCRF. Through this interface, the establishment and maintenance of IP-CAN session connection can be realized; PCC decision request is initiated from PCEF to PCRF; PCRF dynamically controls PCC behavior on PCEF and other functions . Wherein, when the session establishment is requested, the information transmitted from the PCEF to the PCRF includes private network IP, IMSI, MSISDN and other information, which can be used as user identification.

In the PCC architecture, when a user goes online, a Gx session is established between the PCEF and the PCRF. When the user accesses a service, an Rx session is established between the Policy Agent (PA) and the PCRF and the service information is transmitted to the PCRF. Only when the Gx session and Rx session of the same user are associated with the same PCRF, can the PCRF generate a control policy applicable to the user. Otherwise, the PCRF cannot generate policies based on user information, subscription information, and service information, and the PCC control process cannot be completed.

Due to the limitation of PCRF signaling processing capability and capacity, there is a scenario where multiple sets of PCRFs are deployed in one province in the existing network. This may cause the user's Gx session and Rx session to be associated with different PCRFs, as shown in Figure 2, resulting in failure to Service information formulates policies for users, thus failing to achieve the goal of coordinating networks and services.

The key to solving the above PCC session association problem is that on the Gx interface and the Rx interface, the PCEF and the P-CSCF can find the same PCRF through an effective addressing mechanism.

The existing 3GPP specification stipulates that the addressing based on the user's IP address can be realized by using the DRA device, that is, the PCC session association of the same user is realized through the same pair of DRA devices on the Gx interface and the Rx interface. In the current network, IPv4 address resources are very tight, and it is impossible to assign a public network address to each activated user. Therefore, the current situation is to assign a private network address to each activated user, and convert it into a public network address through PCEF firewall NAT to transfer. Generally, the IP address segments allocated by different PCEFs overlap. Therefore, the addressing scheme based on the IP address will face the problem of duplication of the user's private network IP address. This problem causes that on the Rx interface, the PCRF associated with the user's Gx session cannot be uniquely found through the user's private network IP address. Gx session failed to bind, policy not generated correctly.

An example of this is given below.

As shown in Figure 3, assuming that the private network IP address range allocated to users by PCEF1 is 10.0.0.50-10.0.0.100, and the private network IP address range allocated to users by PCEF2 is 10.0.0.70-10.0.0.120, then 10.0.0.70- 10.0.0.100 is an overlapping address segment.

As shown in Figure 3, UE1 and UE2 complete PDP activation on two different PCEFs (PCEF1, PCEF2), and the assigned IP addresses are both 10.0.0.100. UE1 registers with PCRF1 through PCEF1, and UE2 registers with PCRF2 through PCEF2. , the routing and addressing work of the Gx interface is completed by the same pair of DRA devices, and the corresponding relationship between the UE IP address and the PCRF is maintained on the DRA device.

Assuming that UE1 accesses services and generates an Rx session on the Rx interface through a Policy Agent (PA), the Rx session needs to find the PCRF serving UE1, that is, PCRF1, otherwise PCRF cannot associate UE1’s Gx session with the Rx session. The Rx session carries the private network IP address of the UE. The DRA device finds the PCRF registered with the user's Gx session by comparing the UE's private network IP address, and then addresses the Rx session to the PCRF.

However, since UE1 and UE2 use the same private network IP address 10.0.0.100 in the records maintained by DRA and correspond to different PCRFs, the DRA device cannot route the Rx session to the correct PCRF according to UE1's private network IP address, that is, PCRF1.

Contents of the invention

The purpose of the present invention is to provide a session association method, device, gateway, service-side access device and service server, so as to solve the problem of multiple PCRF addressing when the address of the existing network is repeated.

In order to achieve the above object, an embodiment of the present invention provides a session association method, which is used in a Diameter routing agent DRA, and the DRA is connected to multiple gateways and multiple policy and charging rule function PCRF entities. The session association method include:

After establishing a Gx session with any gateway in the plurality of gateways, and associating the Gx session with a PCRF, establishing the private network IP address of the user equipment corresponding to the Gx session, and the private network accessed by the user equipment A first correspondence between the private domain identifier of the domain, the APN, and the associated PCRF;

After the first Rx session is established with the service-side access device, the first Rx session is parsed, and the first private network IP address, access source information, and first APN of the first user equipment are obtained; the Rx session is all When the first user equipment initiates a service request to the service server, the service-side access device initiates a session to the DRA according to the interaction with the service server;

determining a first private network domain corresponding to the access source information;

determining a first PCRF corresponding to the first private network IP address, the first private network domain identifier of the first private network domain, and the first APN according to the first correspondence;

associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.

Wherein, preferably, the session association method is used in an IMS system, and the source information is the private network domain identifier of the first private network domain accessed by the first user equipment.

Wherein, preferably, the private network domain identifier is a gateway identifier.

Wherein, preferably, the session association method is used in a non-IMS system, the source information is the first NAT accessed by the first user equipment, and the session corresponding to the access source information is determined according to the access source information. The first private domain of is:

Confirming the first private network domain corresponding to the first NAT according to the pre-established correspondence between the NAT and the gateway.

In order to achieve the above object, an embodiment of the present invention also provides a session association device, which is used in a DRA, the DRA is connected to multiple gateways and multiple PCRFs, and the session association device includes:

A corresponding relationship establishment module, configured to establish a Gx session with any gateway in the plurality of gateways, and associate the Gx session with a PCRF, and establish the private network IP address of the user equipment corresponding to the Gx session, A first correspondence between the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF;

An information acquisition module, configured to analyze the first Rx session after establishing the first Rx session with the service-side access device, and obtain the first private network IP address, access source information, and first APN of the first user equipment; The Rx session is a session initiated by the service-side access device according to interaction with the service server when the first user equipment initiates a service request to the service server;

A private network domain determination module, configured to determine the first private network domain corresponding to the access source information;

A PCRF determining module, configured to determine a first PCRF corresponding to the first private network IP address, the first private network domain identifier of the first private network domain, and the first APN according to the first correspondence;

An associating module, configured to associate the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.

Wherein, preferably, the session association device is used in an IMS system, and the source information is the private network domain identifier of the first private network domain accessed by the first user equipment.

Wherein, preferably, the private network domain identifier is a gateway identifier.

Wherein, preferably, the session association device is used in a non-IMS system, the source information is the NAT identifier of the first NAT accessed by the first user equipment, and the private network domain determining module is specifically configured to The corresponding relationship between the NAT and the private network domain confirms the first private network domain corresponding to the first NAT.

In order to achieve the above object, an embodiment of the present invention also provides a Diameter routing agent DRA, which is connected to multiple gateways and multiple policy and charging rule function PCRF entities, and includes any one of the session association devices described above.

In order to achieve the above object, the embodiment of the present invention also provides a gateway, which is used to connect with a Diameter routing agent DRA and establish a Gx session, and the gateway sends the private network IP address of the user equipment corresponding to the Gx session, The private network domain identifier and APN of the private network domain accessed by the user equipment are given to the DRA, so that the DRA can:

After associating the Gx session with a PCRF, establish a first correspondence between the private network IP address of the user equipment corresponding to the Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF relation;

After the first Rx session is established with the service-side access device, the first Rx session is parsed, and the first private network IP address, access source information, and first APN of the first user equipment are obtained; the Rx session is all When the first user equipment initiates a service request to the service server, the service-side access device initiates a session to the DRA according to the interaction with the service server;

determining the first private network domain corresponding to the access source information;

determining a first PCRF corresponding to the first private network IP address, the first private network domain identifier of the first private network domain, and the first APN according to the first correspondence;

associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.

In order to achieve the above object, the embodiment of the present invention also provides a service-side access device, which is used to establish an Rx session with a Diameter routing agent DRA, and the service-side access device includes:

The first interaction module is used to interact with the service server when a first user equipment initiates a service request to a service server, obtain the first private network IP address of the first user equipment, and confirm the access source information and a the first APN;

A session establishment module, configured to establish a first Rx session with the DRA, where the first Rx session carries the first private network IP address, access source information, and first APN of the first user equipment, so that the The DRA is able to:

After establishing the first Rx session with the service-side access device, parsing the first Rx session to obtain the first private network IP address, access source information, and first APN of the first user equipment;

determining the first private network domain corresponding to the access source information;

According to the predetermined first corresponding relationship between the private network IP address of the user equipment corresponding to the Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF, determine the connection with the first private network The first PCRF corresponding to the network IP address, the first private network domain identifier of the first private network domain, and the first APN;

associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.

Wherein, preferably, the service-side access device is specifically a P-CSCF in an IMS system; and is specifically a policy proxy in a non-IMS system.

In order to achieve the above object, the embodiment of the present invention also provides a service server for a service platform, the service server includes:

A receiving module, configured to receive a service request initiated by a first user equipment;

An obtaining module, configured to obtain the first private network IP address of the first user equipment;

The second interaction module is configured to interact with a service-side access device, and send the first private network IP address of the first user equipment to the service-side access device, so that the service-side access device can:

Obtain the first private network IP address of the first user equipment, and confirm the access source information and a first APN;

Establish a first Rx session with a Diameter routing agent DRA, the first Rx session carries the first private network IP address, access source information and first APN of the first user equipment, so that the DRA can:

After establishing the first Rx session with the service-side access device, parsing the first Rx session to obtain the first private network IP address, access source information, and first APN of the first user equipment;

determining the first private network domain corresponding to the access source information;

According to the predetermined first corresponding relationship between the private network IP address of the user equipment corresponding to the Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF, determine the connection with the first private network The first PCRF corresponding to the network IP address, the first private network domain identifier of the first private network domain, and the first APN;

associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.

Embodiments of the present invention have at least one of the following beneficial effects:

The embodiment of the present invention locates the unique PCRF by adding a session source information, so the PCRF addressing problem when the live network address is repeated can be solved;

The embodiment of the present invention can be applied in both the IMS system and the non-IMS system;

In the embodiment of the present invention, the existing network architecture does not need to be changed when the associated PCC session is performed, which has little impact on the network.

Description of drawings

Fig. 1 is the basic flowchart schematic diagram of PCC control;

FIG. 2 is a schematic diagram of PCC session association in a multi-PCRF deployment environment;

Figure 3 is a schematic diagram showing that Gx/Rx sessions cannot be associated with the same PCRF when the private network IP address is repeated;

FIG. 4 is a schematic flowchart of a session association method according to an embodiment of the present invention;

FIG. 5 is a schematic flow diagram of session association under the IMS system according to an embodiment of the present invention;

FIG. 6 is a schematic flow diagram of session association in a non-IMS system according to an embodiment of the present invention;

Fig. 7 is a schematic structural diagram of a session association device according to an embodiment of the present invention.

detailed description

Before describing the embodiments of the present invention in detail, the problems in the prior art involved in the embodiments of the present invention and the related or similar solutions proposed by some current patents are described in detail, so as to better understand the embodiments of the present invention .

In view of the above problems, the embodiment of the present invention provides a session association method, which is used in the Diameter routing agent DRA, and the DRA is connected to multiple gateways and multiple policy and charging rule function PCRF entities, as shown in Figure 4, The session association method includes:

Step 41: After establishing a Gx session with any gateway in the plurality of gateways and associating the Gx session with a PCRF, establish the private network IP address of the user equipment corresponding to the Gx session, the user equipment access The first corresponding relationship between the private network domain identifier of the private network domain, the APN and the associated PCRF;

Step 42, after establishing the first Rx session with the service-side access device, analyze the first Rx session, and obtain the first private network IP address, access source information, and first APN of the first user equipment; the Rx The session is a session initiated by the service-side access device to the DRA according to the interaction with the service server when the first user equipment initiates a service request to the service server;

Step 43, determining the first private network domain corresponding to the access source information;

Step 44, determining a first PCRF corresponding to the first private network IP address, the first private network domain identifier of the first private network domain, and the first APN according to the first correspondence;

Step 45, associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.

The above method is used in Diameter routing agent DRA equipment. When DRA establishes a Gx session with any gateway in the plurality of gateways and associates the Gx session with a PCRF, the user corresponding to the Gx session will be established. A first correspondence between the private network IP address of the device, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF;

After the DRA establishes the first Rx session with the service-side access device, it analyzes the first Rx session, and obtains the first private network IP address, access source information, and first APN of the first user equipment therein; where the Rx session When initiating a service request to the service server for the first user equipment, the service-side access device initiates a session to the DRA according to the interaction with the service server;

The DRA determines the first private network domain corresponding to the access source information;

According to the private network IP address of the user equipment corresponding to the previously established Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the first correspondence between the APN and the associated PCRF, the DRA determines the connection with the first private network. The first PCRF corresponding to the network IP address, the first private network domain identifier of the first private network domain, and the first APN, and the PCRF determined at this time is unique;

Finally, associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with the Gx session corresponding to the first user equipment. The above method adds a private network domain identification parameter to the Rx interface. This parameter and the user's private network address can uniquely locate a user and address the PCRF. Since the private network address under a NAT or under a PCEF will not be repeated, the newly added private network domain identification parameter can be represented by a PCEF device identification or a NAT identification, and the above-mentioned process can solve the problem of duplicate addresses in the existing network PCRF addressing problem, ensure that the same PCRF can be correctly addressed to serve users on the Gx interface and the Rx interface.

The session association method provided by the embodiment of the present invention can be applied in an IMS system and a non-IMS system, which are respectively described as follows.

When used in an IMS system, the source information at this time is the private network domain identifier of the first private network domain accessed by the first user equipment.

In the IMS system, the gateway ID of the private network domain can be used as the ID of the private network domain, by adding the PCEF ID configured according to the VLAN at the P-CSCF and carrying it in the Rx interface, and adding the ID based on the DRA device The addressing function of the PCEF identifier uses the two parameters of the user's private network IP address and the PCEF identifier to be queried by the DRA device to realize the association between the Gx session and the Rx session of the same user. At this time, the service-side device is the P-CSCF.

At this time, the PCEF equipment, DRA equipment, and P-CSCF of the packet domain core network have the following requirements, including:

When a business request is made, the user can insert the private network IP address into the data packet and report it to the business platform;

The service platform should be able to resolve the private network address in the user data packet and send it to the P-CSCF;

The P-CSCF shall be able to configure the PCEF identifier according to the VLAN and carry it in the Rx interface;

The Rx interface should be able to increase the AVP identified by the PCEF;

The DRA device should be pre-configured with the correspondence table between the user's private network IP address and the PCEF identifier;

The DRA device should be able to parse and identify the user's private network IP address and PCEF identifier carried in the Rx session, and use the two parameters of the private network IP address and PCEF identifier to perform routing addressing, and finally find the destination PCRF.

For example, as shown in Figure 5: There are two users (UE1, UE2) in the network activating PDP through different PCEFs (PCEF1, PCEF2), assuming that the private network IP addresses assigned to UE1 and UE2 are the same (both private network IP UE1&UE2) , at this time, there will be no duplication of private network IP addresses corresponding to the same PCEF;

The DRA establishes Gx sessions with PCEF1 and PCEF2 respectively, and associates the Gx sessions with PCRF1 and PCRF2 respectively, that is, UE1 registers with PCRF1 through PCEF1, and UE2 registers with PCRF2 through PCEF2;

The Gx interface is statically addressed by the DRA device based on the IMSI. At this time, the addressing function based on the PCEF identifier is added to the DRA device, that is, the PCEF identifier item is added to the addressing information table, and the APN is confirmed. At this time, the APN can be the same , both of which are APNUE1&UE2, establish the first corresponding relationship between the private network IP address of the user equipment corresponding to the Gx session, the gateway identifier of the private network domain accessed by the user equipment, the APN and the associated PCRF in the DRA device, as shown in the table 1, which contains information such as IMSI, private network IP address, PCEF identifier, APN and PCRF mapping relationship table:

When user UE1 accesses the IMS service, it will carry its own private network address in the SDP. After receiving the user's SIP message, the P-CSCF initiates an Rx session to carry the service information. At this time, the P-CSCF needs to be able to configure the PCEF ID according to the VLAN , and carry the PCEF identifier in the Rx session, and at the same time, add an AVP with the PCEF identifier on the Rx interface;

The addressing of the Rx interface is also implemented by the DRA device, and the addressing of the Gx interface uses the same pair of DRAs. After receiving this message, the DRA device parses out the private network IP address and PCEF identifier of UE1. The routing addressing of the address and PCEF identification finally determines the correct PCRF.

When used in a non-IMS system, the source information is the first NAT accessed by the first user equipment at this time, and the first private network domain corresponding to the access source information is determined according to the access source information Specifically:

Confirming the first private network domain corresponding to the first NAT according to the pre-established correspondence between the NAT and the private network domain.

Add the mapping relationship table of the corresponding relationship between Network Address Translation (NAT) and the private network domain in the DRA device. The private network domain identification here can be the gateway (PCEF) identification, and add the NAT identification at the PA, through the private network IP and The PCEF identifies two parameters, and the DRA device performs a two-dimensional query to finally realize the session association between the Gx interface and the Rx interface of the same user. At this time, the service-side device is a policy agent (PA).

At this time, the following requirements are required for PCEF equipment, DRA equipment, and Policy Agent (PA) equipment in the packet domain core network, including:

When making a service request, the user should be able to insert the private network IP address obtained from the terminal into the data packet and report it to the service platform;

The service platform should be able to analyze the private network address in the user data packet, and send the user's private network IP address to the policy agent (PA);

The Policy Agent (PA) should be able to add the NAT identifier, and carry the user's private network IP address and NAT identifier when initiating an Rx session;

When DRA establishes the Gx session routing addressing information table, it should be able to include the user's PCEF information and the user's private network IP address;

The DRA device should be pre-configured with the corresponding relationship table between NAT and PCEF;

The DRA device should be able to parse and identify the user's private network IP address and NAT identifier carried in the Rx session, and can use the two parameters of the user's private network IP address and NAT identifier to perform two queries, and finally find the destination PCRF.

This is described in detail below.

As shown in Figure 6:

There are two users (UE1, UE2) in the network to activate PDP through different PCEFs (PCEF1, PCEF2). Assume that the private network IP addresses assigned to UE1 and UE2 are the same, both of which are private network IPUE1&UE2. At this time, PCEF1 and PCEF2 should be located at After two NAT devices, there will be no duplicate private network IP addresses under the same NAT device, because of network address planning, the public network IP addresses assigned by the two NAT devices are not duplicated;

The DRA establishes Gx sessions with PCEF1 and PCEF2 respectively, and associates the Gx sessions with PCRF1 and PCRF2 respectively, that is, UE1 registers with PCRF1 through PCEF1, and UE2 registers with PCRF2 through PCEF2;

The Gx interface is statically addressed by the DRA device based on the IMSI. At this time, the Gx session routing addressing information table is generated and maintained in the DRA device, as shown in Table 2:

Table 2 Gx session routing addressing information table

In addition, the corresponding relationship between NAT and PCEF needs to be pre-configured in the DRA device, as shown in Table 3:

NAT1 PCEF1～3 NAT2 PCEF4～6

Table 3 NAT and PCEF correspondence table

When user UE1 accesses the service, report its own private network IP address;

The service platform notifies the service-side access device (PA) of UE1's private network IP address, and the service-side access device initiates an Rx session. The service-side access device adds a NAT identifier, and the Rx session carries UE1's private network IP address and NAT identification;

The addressing of the Rx interface is also implemented by the DRA device, and the addressing of the Gx interface uses the same pair of DRAs. After receiving this message, the DRA device parses out the NAT identifier, performs the first query by comparing Table 3, and obtains that the Gx session corresponding to the Rx session is initiated from PCEF1-3 according to the corresponding relationship between NAT and PCEF pre-configured by DRA;

Use the private network IP address and the PCEF identifier to perform a second query through Table 2, and obtain that the PCRF serving the user is PCRF1, and complete the Rx interface addressing process.

In the above two systems, both the Gx session and the Rx session of UE1 are successfully associated with PCRF1, and the PCC session association is completed. When PCRF1 associates the Rx session with the Gx session, the following methods can be used: <Method 1> DRA determines When the first Rx session should be associated with PCRF1, inform the identifier of the Gx session corresponding to the first Rx session on PCRF1, and when PCRF1 associates the Gx session with the Rx session, it directly uses the The identifier of the corresponding Gx session can be associated.

<Mode 2> The private network IP address of the user equipment, the private network domain identifier accessed by the user equipment, the APN and the first correspondence between the corresponding Gx session are also stored on PCRF1, and the first Rx session is associated with the PCRF Then, according to the second correspondence, determine the Gx session corresponding to the first private network IP address in the first Rx session, the first private network domain identifier of the first private network domain, and the first APN. When the PCRF performs the association between the Rx session and the Gx session, there are various implementation methods, which will not be listed here.

According to the method provided by the embodiment of the present invention, the associated PCC session does not need to change the existing network architecture, and has little impact on the network.

The embodiment of the present invention also provides a session association device, which is used in a DRA. The DRA is connected to multiple gateways and multiple PCRFs. As shown in FIG. 7, the session association device includes:

A corresponding relationship establishment module, configured to establish a Gx session with any gateway in the plurality of gateways, and associate the Gx session with a PCRF, and establish the private network IP address of the user equipment corresponding to the Gx session, A first correspondence between the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF;

An information acquisition module, configured to analyze the first Rx session after establishing the first Rx session with the service-side access device, and obtain the first private network IP address, access source information, and first APN of the first user equipment ; The Rx session is a session initiated by the service-side access device according to the interaction with the service server when the first user equipment initiates a service request to the service server;

A private network domain determination module, configured to determine the first private network domain corresponding to the access source information;

A PCRF determining module, configured to determine a first PCRF corresponding to the first private network IP address, the first private network domain identifier of the first private network domain, and the first APN according to the first correspondence;

An associating module, configured to associate the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.

Wherein, preferably, the session association device is used in an IMS system, and the source information is the private network domain identifier of the first private network domain accessed by the first user equipment.

Wherein, preferably, the private network domain identifier is a gateway identifier.

Wherein, preferably, the session association device is used in a non-IMS system, the source information is the NAT identifier of the first NAT accessed by the first user equipment, and the private network domain determining module is specifically configured to The corresponding relationship between the NAT and the private network domain confirms the first private network domain corresponding to the first NAT.

The embodiment of the present invention also provides a Diameter routing agent DRA, which is connected to multiple gateways and multiple policy and charging rule function PCRF entities, and includes any one of the session association devices described above.

The embodiment of the present invention also provides a gateway, which is used to connect with a Diameter routing agent DRA and establish a Gx session, and the gateway sends the private network IP address of the user equipment corresponding to the Gx session, the user equipment access The private network domain identifier and APN of the private network domain are given to the DRA, so that the DRA can:

After associating the Gx session with a PCRF, establish a first correspondence between the private network IP address of the user equipment corresponding to the Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF relation;

After the first Rx session is established with the service-side access device, the first Rx session is parsed, and the first private network IP address, access source information, and first APN of the first user equipment are obtained; the Rx session is all When the first user equipment initiates a service request to the service server, the service-side access device initiates a session to the DRA according to the interaction with the service server;

determining the first private network domain corresponding to the access source information;

determining a first PCRF corresponding to the first private network IP address, the first private network domain identifier of the first private network domain, and the first APN according to the first correspondence;

associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.

The embodiment of the present invention also provides a service-side access device, which is used to establish an Rx session with a Diameter routing agent DRA, and the service-side access device includes:

The first interaction module is used to interact with the service server when a first user equipment initiates a service request to a service server, obtain the first private network IP address of the first user equipment, and confirm the access source information and a the first APN;

A session establishment module, configured to establish a first Rx session with the DRA, where the first Rx session carries the first private network IP address, access source information, and first APN of the first user equipment, so that the The DRA is able to:

After establishing the first Rx session with the service-side access device, parsing the first Rx session to obtain the first private network IP address, access source information, and first APN of the first user equipment;

determining the first private network domain corresponding to the access source information;

According to the predetermined first corresponding relationship between the private network IP address of the user equipment corresponding to the Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF, determine the connection with the first private network The first PCRF corresponding to the network IP address, the first private network domain identifier of the first private network domain, and the first APN;

associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.

Wherein, preferably, the access device at the service side is a P-CSCF in the IMS system and a policy agent in the non-IMS system.

The embodiment of the present invention also provides a kind of business server, is used for a business platform, and described business server comprises:

A receiving module, configured to receive a service request initiated by a first user equipment;

An obtaining module, configured to obtain the first private network IP address of the first user equipment;

The second interaction module is configured to interact with a service-side access device, and send the first private network IP address of the first user equipment to the service-side access device, so that the service-side access device can:

Obtain the first private network IP address of the first user equipment, and confirm the access source information and a first APN;

Establish a first Rx session with a Diameter routing agent DRA, the first Rx session carries the first private network IP address, access source information and first APN of the first user equipment, so that the DRA can:

After establishing the first Rx session with the service-side access device, parsing the first Rx session to obtain the first private network IP address, access source information, and first APN of the first user equipment;

determining the first private network domain corresponding to the access source information;

According to the predetermined first corresponding relationship between the private network IP address of the user equipment corresponding to the Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF, determine the connection with the first private network The first PCRF corresponding to the network IP address, the first private network domain identifier of the first private network domain, and the first APN;

associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.

The above is only a preferred embodiment of the present invention, it should be pointed out that, for those of ordinary skill in the art, without departing from the principle of the present invention, some improvements and modifications can also be made, and these improvements and modifications can also be made. It should be regarded as the protection scope of the present invention.

Claims (13)

1. A session association method, used for Diameter routing agent DRA equipment, described DRA equipment is connected with a plurality of gateways and a plurality of policies and charging rule function PCRF entity, it is characterized in that, described session association method comprises: After establishing a Gx session with any gateway in the plurality of gateways, and associating the Gx session with a PCRF, establishing the private network IP address of the user equipment corresponding to the Gx session, and the private network accessed by the user equipment A first correspondence between the private domain identifier of the domain, the APN, and the associated PCRF; After the first Rx session is established with the service-side access device, the first Rx session is parsed, and the first private network IP address, access source information, and first APN of the first user equipment are obtained; the Rx session is all When the first user equipment initiates a service request to the service server, the service-side access device initiates a session to the DRA according to the interaction with the service server; determining the first private network domain corresponding to the access source information; determining a first PCRF corresponding to the first private network IP address, the first private network domain identifier of the first private network domain, and the first APN according to the first correspondence; associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment. 2. The session association method according to claim 1, wherein the session association method is used in an IMS system, and the source information is the private network domain of the first private network domain accessed by the first user equipment logo. 3. The session association method according to claim 2, wherein the private network domain identifier is a gateway identifier. 4. The session association method according to claim 1, wherein the session association method is used in a non-IMS system, the source information is the first NAT accessed by the first user equipment, and according to the access The input source information determines that the first private network domain corresponding to the access source information is specifically: Confirming the first private network domain corresponding to the first NAT according to the pre-established correspondence between the NAT and the private network domain. 5. A session association device, used in a DRA device, the DRA device is connected to a plurality of gateways and a plurality of PCRFs, wherein the session association device includes: A corresponding relationship establishment module, configured to establish a Gx session with any gateway in the plurality of gateways, and associate the Gx session with a PCRF, and establish the private network IP address of the user equipment corresponding to the Gx session, A first correspondence between the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF; An information acquisition module, configured to analyze the first Rx session after establishing the first Rx session with the service-side access device, and obtain the first private network IP address, access source information, and first APN of the first user equipment; The Rx session is a session initiated by the service-side access device according to interaction with the service server when the first user equipment initiates a service request to the service server; A private network domain determination module, configured to determine the first private network domain corresponding to the access source information; A PCRF determining module, configured to determine a first PCRF corresponding to the first private network IP address, the first private network domain identifier of the first private network domain, and the first APN according to the first correspondence; An associating module, configured to associate the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment. 6. The session association device according to claim 5, wherein the session association device is used in an IMS system, and the source information is the private network domain of the first private network domain accessed by the first user equipment logo. 7. The session association device according to claim 6, wherein the private network domain identifier is a gateway identifier. 8. The session association device according to claim 5, wherein the session association device is used in a non-IMS system, and the source information is the NAT identifier of the first NAT accessed by the first user equipment, so The private network domain determination module is specifically configured to confirm the first private network domain corresponding to the first NAT according to the pre-established correspondence between NATs and private network domains. 9. A Diameter routing agent DRA device, connected to multiple gateways and multiple policy and charging rule function PCRF entities, characterized in that it comprises the session association device according to any one of claims 5 to 8. 10. A gateway, used to connect with a Diameter routing proxy DRA device, and set up a Gx session, characterized in that, the gateway sends the private network IP address of the user equipment corresponding to the Gx session, the user equipment access The private network domain identifier and APN of the private network domain are given to the DRA, so that the DRA can: After associating the Gx session with a PCRF, establish a first correspondence between the private network IP address of the user equipment corresponding to the Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF relation; After the first Rx session is established with the service-side access device, the first Rx session is parsed, and the first private network IP address, access source information, and first APN of the first user equipment are obtained; the Rx session is all When the first user equipment initiates a service request to the service server, the service-side access device initiates a session to the DRA according to the interaction with the service server; determining the first private network domain corresponding to the access source information; determining a first PCRF corresponding to the first private network IP address, the first private network domain identifier of the first private network domain, and the first APN according to the first correspondence; associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment. 11. A service side access device, used to set up an Rx session with a Diameter routing agent DRA, characterized in that the service side access device comprises: The first interaction module is used to interact with the service server when a first user equipment initiates a service request to a service server, obtain the first private network IP address of the first user equipment, and confirm the access source information and a the first APN; A session establishment module, configured to establish a first Rx session with the DRA, where the first Rx session carries the first private network IP address, access source information, and first APN of the first user equipment, so that the The DRA is able to: After establishing the first Rx session with the service-side access device, parsing the first Rx session to obtain the first private network IP address, access source information, and first APN of the first user equipment; determining the first private network domain corresponding to the access source information; According to the predetermined first corresponding relationship between the private network IP address of the user equipment corresponding to the Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF, determine the connection with the first private network The first PCRF corresponding to the network IP address, the first private network domain identifier of the first private network domain, and the first APN; associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment. 12. The service side access device according to claim 11, characterized in that it is a P-CSCF in an IMS system and a policy proxy in a non-IMS system. 13. A service server, characterized in that the service server comprises: A receiving module, configured to receive a service request initiated by a first user equipment; An obtaining module, configured to obtain the first private network IP address of the first user equipment; The second interaction module is configured to interact with a service-side access device, and send the first private network IP address of the first user equipment to the service-side access device, so that the service-side access device can: Obtain the first private network IP address of the first user equipment, and confirm the access source information and a first APN; establish a first Rx session with a Diameter routing agent DRA, and the first Rx session carries the The first private network IP address, access source information and first APN of the first user equipment, so that the DRA can: After establishing the first Rx session with the service-side access device, parsing the first Rx session to obtain the first private network IP address, access source information, and first APN of the first user equipment; determining the first private network domain corresponding to the access source information; According to the predetermined first corresponding relationship between the private network IP address of the user equipment corresponding to the Gx session, the private network domain identifier of the private network domain accessed by the user equipment, the APN, and the associated PCRF, determine the connection with the first private network The first PCRF corresponding to the network IP address, the first private network domain identifier of the first private network domain, and the first APN; associating the first Rx session with the first PCRF, so that the first PCRF can associate the first Rx session with a Gx session corresponding to the first user equipment.