WO2017041507A1

WO2017041507A1 - Diameter message routing method and routing agent node

Info

Publication number: WO2017041507A1
Application number: PCT/CN2016/082239
Authority: WO
Inventors: 周晓云; 梁爽
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-09-07
Filing date: 2016-05-16
Publication date: 2017-03-16
Also published as: CN106507382A; CN106507382B

Abstract

Published are a Diameter message routing method and a routing agent node. The method comprises: receiving an Rx session establishment request message, wherein the Rx session establishment request message carries a private network IP address of a second UE and a second IP domain identifier; and when the private network IP address of the second UE successfully matches a private network IP address of a first UE in Diameter routing agent (DRA) binding information and the second IP domain identifier successfully matches a first PCEF identifier in the DRA binding information, setting a destination host domain (Destination-Host AVP) of the Rx session establishment request message to be a value of a first Policy and Charging Rules Function (PCRF) identifier in the DRA binding information, and replacing a value of the second IP domain identifier with the value of the first Policy and Charging Enforcement Function (PCEF) identifier in the DRA binding information.

Description

Diameter message routing method and routing proxy node

Technical field

This application relates to, but is not limited to, the field of mobile communication PCC technology.

Background technique

A schematic diagram of a Policy and Charging Control (PCC) architecture defined by the 3rd Generation Partnership Project (3GPP), as shown in FIG. The Policy and Charging Rules Function (PCRF) is used to formulate the QoS (Quality of Service) and the charging policy for the service using network resources. The PCRF needs to combine the service information received from the application function (AF, Application Function), the user subscription information received from the User Profile Repository (SPR), and the policy configured by the operator. The PCRF sends the control policy for the service to the Policy and Charging Enforcement Function (PCEF) or the Bearer Binding and Event Report Function (BBERF). At the same time, the PCRF can subscribe to the bearer layer related events to the PCEF and/or the BBERF to sense in time when the bearer layer occurs, and change the control strategy. In addition, the PCEF and the Traffic Detection Function (TDF) can perform application detection and control functions according to PCC rules (PCEF) or Application Detection Control (ADC) issued by the PCRF. The Online Charging System (OCS) provides credit control functions based on user and business data streams. The Off-line Charging System (OFCS) provides charging functions based on user and service data flows.

With the development of the mobile Internet, operators need to communicate with third-party data application providers to provide QoS for services provided by third-party data application providers. Due to the Diameter protocol currently used by the RX interface supported by PCC, for most third-party data application providers, they are better at developing based on SOAP and REST protocols. Currently, the industry research PCC architecture supports the Rx interface based on the SOAP/REST protocol. Directly set up a logic function called Protocol Converter (PC) in PCRF and AF for SOAP or REST protocol. Convert to Diameter. Further, some access control functions may be added to the PC to better implement the access control of the third-party data application by the operator. In this case, the logical function is also called application access control (AAC, Application Access). Control) functional entity, as shown in Figure 2, AAC's PCC architecture diagram.

There are multiple PCRF nodes in a Public Land Mobile Network (PLMN) of the Evolved Packet System (EPS), and all PCRF nodes belong to one or more Diameter (PCRF) domains, in the following description. The Diameter (PCRF) domain is simply referred to as a PCRF domain. A UE-to-packet data network (PDN) connection is called an IP-Connected Access Network (IP-CAN) session. The PCC policy for an IP-CAN session is determined by only one PCRF. In order to ensure that all PCEFs, GWs and AFs associated with an IP-CAN session are associated with the same PCRF, the EPS introduces a Dialogic Routing Agent (DRA) in each PCRF domain. When the UE establishes an IP-CAN session to a PDN, the DRA selects a PCRF for this IP-CAN session. This IP-CAN session related PCEF, BBERF and AF are associated by the DRA to the selected PCRF. In general, an EPS network may have multiple Diameter management domains. As shown in FIG. 3, there is a schematic diagram of two Diameter management domains in one PLMN. The DRA is responsible for managing the PCRF in this domain. In the PCC clients in this domain, such as PCEF, BBERF, AF, and AAC, the correct PCRF can be found through the DRA of this domain. For the subscribers in the management domain 1, when the UE accesses in the management domain 1, the Diameter message sent by the PCC client such as the BBERF and the PCEF in the management domain 1 is routed to the correct PCRF through the DRA1, if the UE moves to the management domain. At 2 o'clock, the message sent by the PCC client such as BBERF and PCEF in the management domain 2 first passes the DRA2, and the DRA2 sends the Diameter message to the DRA1 according to the related information, and the DRA1 then routes the message to the correct PCRF. One or more Diameter Agents are typically deployed prior to DRA1 and DRA2 to route DRA1 messages to DRA2.

In order to solve the problem of shortage of IP addresses, operators usually deploy Network Address Translation (NAT) after the packet network gateway (P-GW, PDNGateway). As shown in Figure 4, the schematic diagram of the PCC architecture of NAT, because of the existence of NAT, enables the same PDN connection to carry the private IP address used inside the packet core evolution network (EPC, Evolved Packet Core), and the public IP used in the external packet network. The address is different.

As shown in FIG. 5, a schematic diagram of a process in which a UE of the related art accesses a network and establishes an IP-CAN session through a P-GW in which the management domain 2 is located (the PCEF2 is located in the GW).

Step 501: The PCEF2 receives a request to establish an IP-CAN session message, where the request to establish an IP-CAN session message carries a first user identifier, a first UE private network IP address, and a first PDN identifier.

Step 502: The PCEF2 sends an IP-CAN session establishment indication message to the DRA2, where the IP-CAN session establishment indication message carries the first user identifier, the first UE private network IP address, and the first PDN identifier. The IP-CAN session establishment indication message is actually implemented as a Diameter CCR (Credit Control Request) message.

Step 503: The DRA2 receives the IP-CAN session establishment indication message, determines, according to the first user identifier, that the user is a subscription user of the management domain 1, and uses the Origin-Host AVP that establishes an IP-CAN session indication message. The first PCEF identifier is extracted, and the DRA2 stores the first user identifier, the first UE private network IP address, the first PCEF identifier, and the first PDN identifier.

Step 504: The DRA2 sends the IP-CAN session establishment indication message to the DRA1. If there are other Diameter Agents between DRA2 and DRA1, the Diameter Agent forwards the message to the Diameter Agent of the next hop in turn until DRA1.

Step 505: The DRA1 determines that the PCRF has not been selected for the UE or the IP-CAN session, and the DRA1 selects the PCRF11 for the UE or the IP-CAN session, and saves the first user identifier, the first a correspondence between a PDN identifier, the first UE private network IP address, the first PCEF identifier, and the PCRF 11. The correspondence between the first user identifier, the first PDN identifier, the first UE private network IP address, the first PCEF identifier, and the PCRF 11 is also referred to as DRA binding information.

Step 506: The DRA1 sends the IP-CAN session establishment indication message to the PCRF 11.

Step 507: The PCRF11 receives the IP-CAN session establishment indication message, saves the related information of the IP-CAN session, and performs PCC decision. When the PCRF11 makes a decision, it may need to interact with the SPR to obtain the subscription information of the user. .

Step 508: The PCRF11 sends an IP-CAN session establishment confirmation message to the DRA1, where The IP-CAN session establishment confirmation message carries the PCC decision information.

Step 509: The DRA1 sends the IP-CAN session establishment confirmation message to the DRA2.

Step 510: The DRA2 sends the IP-CAN session establishment confirmation message to the PCEF2.

Step 511: The gateway where the PCEF2 is located sends a request to the UE to establish an IP-CAN session response message.

Step 512: When the UE accesses the service of the network where the management domain 2 is located, or the UE accesses an application that has a contractual relationship with the network where the management domain 2 is located, the AF2/AAC2 initiates a service request, where the service request is An AAR message (also referred to as an Rx session establishment request message), where the AAR message carries at least a second UE private network IP address, a second IP domain identifier, and service information, and the AAR message is to be routed to the DRA2, where the The second IP domain identifier is carried by the IP-Domain-Id AVP, and the second IP domain identifier is usually the public IP address of the UE.

Step 513: The DRA receives the AAR message, and matches the second UE private network IP address with the previously saved first UE private network IP address, and the second IP domain identifier and the previously saved first The PCEF identifier is matched. The DRA2 pre-stores the correspondence between the IP domain identifier and the PCEF identifier. After the matching succeeds, the DRA2 forwards the AAR message to the DRA1, where one or more Diameters between the DRA2 and the DRA1 After the agent matches the above method, the message is routed to the correct next hop until DRA1.

Step 514: The DRA matches the previously configured private network IP address and the previously saved first private network IP address according to the second UE private network IP address and the second IP domain identifier. Matching, and matching the second IP domain identifier with the previously saved first PCEF identifier, where the DRA1 pre-stores the correspondence between the IP domain identifier and the PCEF identifier), the matching is successful, and the IP established before the UE is determined. -CAN session selects PCRF11. DRA1 forwards the service request message to PCRF11.

Step 515: The PCRF11 performs session binding according to the second UE private network IP address and the second IP domain identifier (that is, the second UE private network IP address is matched with the previously saved first UE private network IP address, and the The second IP domain identifier is matched with the previously saved first PCEF identifier, and the matching is successfully performed for session binding, and the service information is saved.

In step 516, the PCRF 11 sends an acknowledgement message to the DRA1.

Step 517: The DRA1 forwards the acknowledgement message to the DRA2.

Step 518: The DRA2 forwards the confirmation message to the AF2/AAC2.

In order to realize that DRA2 can be routed to the correct PCRF11 in the management domain 2, and the PCRF11 can perform correct session binding, the related art requires the DRA (ie DRA2) in the management domain 2, the Diameter Agent between the DRA2 and the DRA1, and the management domain. Both the DRA (ie, DRA1) and the PCRF11 in 1 need to store the correspondence between the PCEF identifier and the IP domain identifier in the management domain 2, which may result in network configuration complexity. Moreover, in order to ensure that the Diameter message sent by the DRA2 can correctly route the DRA1, the Diameter Agent between the DRA2 and the DRA1 needs to be able to save the information such as the private network IP address and the PCEF identifier of the UE during the IP-CAN establishment process, so that the correct route can be performed. , increased the ability requirements for the Diameter Agent.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a Diameter message routing method and a routing proxy node, which can simplify network parameter configuration.

An embodiment of the present invention provides a method for routing a Diameter message, where the Diameter message routing method includes:

Receiving an Rx session establishment request message, where the Rx session establishment request message carries a second UE private network IP address and a second IP domain identifier;

When the second UE private network IP address matches the first UE private network IP address in the routing agent node DRA binding information, and the second IP domain identifier and the first policy in the DRA binding information And setting the destination host domain Destination-Host AVP of the Rx session establishment request message to the value of the first policy and the charging rule function PCRF identifier in the DRA binding information. And replacing the value of the second IP domain identifier with the value of the first PCEF identifier in the DRA binding information.

Optionally, the DRA binding information is established when the IP connection access network IP-CAN session is established. The DRA binding information includes a first UE private network IP address, the first PCEF identifier, and the first PCRF identifier, where the first PCRF identifier is from the IP-CAN session establishment confirmation message. Extracted.

Optionally, the first PCEF identifier is extracted and obtained from the establishment indication message of the IP-CAN session.

Optionally, the Diameter message routing method further includes:

Receiving the IP-CAN session establishment indication message, where the establishing an IP-CAN session indication message carries a first user identifier;

And determining, by the first user identifier, that the user is a subscription user of the first management domain, and sending the IP-CAN session establishment indication message to the DRA of the first management domain.

Optionally, the Diameter message routing method further includes:

Determining the attribution province of the user according to the first user identifier, and sending the IP-CAN session establishment indication message to the DRA of the home province.

The embodiment of the present invention further provides a routing proxy node, where the routing proxy node includes: a receiving unit and a processing unit;

The receiving unit is configured to: receive an Rx session establishment request message, where the Rx session establishment request message carries a second UE private network IP address and a second IP domain identifier;

The processing unit is configured to: when the second UE private network IP address and the routing agent DRA binding information match the first UE private network IP address, and the second IP domain identifier is tied to the DRA The destination host domain Destination-Host AVP of the Rx session establishment request message is set as the first policy and the accounting in the DRA binding information, when the first policy and the accounting execution function PCEF identifier are successfully matched. The value of the rule is determined by the value of the PCRF, and the value of the second IP domain identifier is replaced by the value of the first PCEF identifier in the DRA binding information.

Optionally, the DRA binding information is saved when the IP connection access network IP-CAN session is established, where the DRA binding information includes a first UE private network IP address, the first PCEF identifier, and the first a PCRF identifier, wherein the first PCRF identifier establishes an acknowledgement from the IP-CAN session The message is extracted and obtained.

Optionally, the routing proxy node further includes: a determining unit and a sending unit,

The receiving unit is further configured to: receive the IP-CAN session establishment indication message, where the establishing an IP-CAN session indication message carries a first user identifier;

The determining unit is configured to: determine, according to the first user identifier, that the user is a subscription user of the first administrative domain;

The sending unit is configured to: send the IP-CAN session establishment indication message to the DRA of the first management domain.

The determining unit is configured to: determine, according to the first user identifier, a attribution province of the user;

The sending unit is configured to: send the IP-CAN session establishment indication message to the DRA of the home province.

The embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions for performing the method of any of the above.

The embodiment of the present invention provides a Diameter message routing method and a routing proxy node, and receives an Rx session establishment request message, where the Rx session establishment request message carries a second UE private network IP address and a second IP domain identifier; The second UE private network IP address is successfully matched with the first UE private network IP address in the routing agent DRA binding information, and the second IP domain identifier is successfully matched with the first PCEF identifier in the DRA binding information. Setting the destination host domain Destination-Host AVP of the Rx session establishment request message to the value of the first policy and the charging rule function PCRF identifier in the DRA binding information, and the second IP domain The value of the identifier is replaced by the value of the first policy and the charging execution function PCEF identifier in the DRA binding information. The Diameter message routing method and the routing proxy node provided by the embodiment of the present invention, when visiting the administrative domain or visiting the provincial route After receiving the service request message (ie, the Rx session establishment request message) sent by the AF/AAC, the proxy node DRA sends the service request message to the DRA of the home management domain or the home province, and forwards the service request message by visiting the management domain DRA. The destination host domain is set to the PCRF identifier saved during the IP-CAN session establishment process, and the IP domain identifier is set to the PCEF identifier saved during the IP-CAN session establishment process, thereby simplifying the configuration of the home management domain DRA and PCRF network parameters. .

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

Figure 1 is a schematic diagram of a PCC architecture;

2 is a schematic diagram of a PCC architecture of an AAC;

FIG. 3 is a schematic structural diagram of interworking between multiple management domains;

4 is a schematic diagram of a PCC architecture of NAT;

5 is a schematic flowchart of an IP-CAN session and a service request in the related art;

FIG. 6 is a schematic flowchart 1 of a method for routing a Diameter message according to an embodiment of the present invention;

FIG. 7 is a schematic flowchart 2 of a method for routing a Diameter message according to an embodiment of the present invention;

FIG. 8 is a schematic flowchart 3 of a method for routing a Diameter message according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram 1 of a routing proxy node according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram 2 of a routing proxy node according to an embodiment of the present invention.

Embodiments of the invention

The technical solutions in the embodiments of the present invention will be clearly and completely described in the following with reference to the accompanying drawings.

It should be noted that the terms “first, second” and the like in the embodiments of the present invention are used to distinguish similar objects, and are not necessarily used to describe a specific order or order.

Embodiment 1

The embodiment of the present invention provides a method for routing a Diameter message. As shown in FIG. 6, the method for routing a Diameter message may include:

Step 101: Receive an Rx session establishment request message, where the Rx session establishment request message carries a second UE private network IP address and a second IP domain identifier.

The execution subject of the Diameter message routing method provided by the embodiment of the present invention is a visited management domain or a DIA (Diameter Routing Agent), that is, DRA2.

The DRA2 receives the Rx session establishment request message, where the Rx session establishment request message carries at least the second UE private network IP address, the second IP domain identifier, and the service information. The Rx session establishment request message may be an authorization authentication request AAR message.

Step 102: The first UE private network IP address and the first UE private network IP address in the DRA binding information are successfully matched, and the second IP domain identifier IP Domain id and the first policy in the DRA binding information are The destination host domain Destination-Host AVP of the Rx session establishment request message is set to the value of the first policy and the charging rule function PCRF identifier in the DRA binding information. And replacing the value of the second IP domain identifier with the value of the first PCEF identifier.

The correspondence between the IP domain identifier and the PCEF identifier is pre-configured.

The DRA2 receives the IP-CAN session establishment confirmation message sent by the DRA1, and extracts the first PCRF identifier, that is, the PCRF11 identifier from the Origin-Host AVP of the IP-CAN session establishment confirmation message, and saves it as (the first user) Corresponding relationship between the identifier, the first UE private network IP address, the first PCEF identifier, the first PDN identifier, and the first PCRF identifier, which is also referred to as DRA binding information, that is, the DRA binding information is an IP connection. When the network IP-CAN session is established, the DRA binding information includes at least a first UE private network IP address, the first PCEF identifier, and the first PCRF identifier, where the first PCRF identifier is Extracted from the IP-CAN session establishment confirmation message.

The DRA2 matches the second UE private network IP address with the first UE private network IP address, and matches the second IP domain identifier with the first PCEF identifier. The DRA2 pre-stores the correspondence between the IP domain identifier and the PCEF identifier.

When the second UE private network IP address matches the first UE private network IP address, and the second IP domain identifier matches the first PCEF identifier, the destination host domain of the Rx session establishment request message is set to The value of the first PCRF identifier, that is, the Destination-Host AVP is set to The value of the identifier of the PCRF11 is changed, and the value of the second IP domain identifier is replaced by the value of the first PCEF identifier, that is, the IP-Domain-Id AVP is set to the value of the PCEF2 identifier.

The method of routing the Diameter message provided by the embodiment of the present invention sends a service request message to the home after receiving the service request message (ie, the Rx session establishment request message) sent by the AF/AAC after receiving the service request message (ie, the Rx session establishment request message) sent by the AF/AAC. The DRA of the management domain or the affiliation province is set to the PCRF identifier saved in the IP-CAN session establishment process by calling the management domain DRA in the forwarding service request message, and the IP domain identifier is set to be in the IP-CAN session establishment process. The saved PCEF identifier, thereby simplifying the configuration of the home management domain or the home province DRA and PCRF network parameters.

Embodiment 2

The scenario of the Diameter message routing method provided by the embodiment of the present invention is: the UE accesses and establishes an IP-CAN session through the P-GW of the network where the management domain 2 is located (the PCEF2 is located in the gateway), and the UE initiates the service request AF/ AAC is also in management domain 2 or has a contractual relationship with administrative domain 2.

An embodiment of the present invention provides a method for routing a Diameter message. As shown in FIG. 7, the method for routing a Diameter message may include:

Step 201: The PCEF2 receives a request to establish an IP-CAN session message, where the request to establish an IP-CAN session message carries at least a first user identifier, a first UE private network IP address, and a first PDN identifier.

Step 202: The PCEF2 sends an IP-CAN session establishment indication message to the DRA2, where the IP-CAN session establishment indication message carries at least the first user identifier, the first UE private network IP address, and the first PDN identifier.

In this embodiment, the IP-CAN session establishment indication message is a Diameter Credit Control Request (CCR) message.

Step 203: The DRA2 receives an IP-CAN session establishment indication message, that is, a CCR message, where the IP-CAN session establishment indication message carries the first user identifier, the first UE private network IP address, and the first PDN identifier. Determining, according to the first user identifier, that the user is a subscription user of the first management domain, and determining, according to the IP-CAN session establishment indication message, the first PCEF identifier, and saving the first user identifier, the first UE private a network IP address, the first PCEF identifier, and the The first PDN identifier.

The DRA2 receives the IP-CAN session establishment indication message, and determines that the user is the first management domain, that is, the subscription user of the management domain 1, according to the first user identifier. The DRA2 extracts the first PCEF identifier from the Origin-Host AVP of the IP-CAN session establishment indication message, and saves the first user identifier, the first UE private network IP address, and the first PCEF. Identification, the first PDN identifier.

Step 204: The DRA2 sends the IP-CAN session establishment indication message to the DRA1.

If there is another Diameter Agent between DRA2 and DRA1, the Diameter Agent forwards the message to the Diameter Agent of the next hop in turn until DRA1.

Step 205: The DRA1 determines that the PCRF has not been selected for the UE or the IP-CAN session, and the DRA1 selects the first PCRF as the PCRF11 for the UE or the IP-CAN session.

The DRA1 stores the first user identifier, the first PDN identifier, the first UE private network IP address, the first PCEF identifier, and the PCRF11 correspondence, that is, DRA binding information.

Step 206: The DRA1 sends the IP-CAN session establishment indication message to the PCRF11.

Step 207: The PCRF11 receives the IP-CAN session establishment indication message, saves related information of the IP-CAN session, and performs PCC decision.

The PCRF 11 may need to interact with the SPR to obtain the subscription information of the user when performing the PCC decision.

Step 208: The PCRF11 sends an IP-CAN session establishment confirmation message to the DRA1, where the IP-CAN session establishment confirmation message carries the PCC decision information.

Step 209: The DRA2 receives the DRA1 to send the IP-CAN session establishment confirmation message.

The DRA1 sends the IP-CAN session establishment confirmation message to the DRA2, and the DRA2 receives the IP-CAN session establishment confirmation message, where the IP-CAN session establishment confirmation message carries the PCC decision information.

Step 210: The DRA2 determines the first PCRF identifier according to the IP-CAN session establishment confirmation message, and saves the first user identifier, the first UE private network IP address, and the first PCEF label. And a corresponding relationship between the first PDN identifier and the first PCRF identifier, that is, DRA binding information.

The DRA2 receives the IP-CAN session establishment confirmation message, that is, the CCA message, and the first PCRF identifier, that is, the PCRF11 identifier, is sent from the Origin-Host of the IP-CAN session establishment confirmation message, and is saved as the first The correspondence between the user identifier, the first UE private network IP address, the first PCEF identifier, the first PDN identifier, and the PCRF11 identifier, that is, the DRA binding information.

Step 211: The DRA2 sends the IP-CAN session establishment confirmation message to the first PCEF.

The first PCEF is PCEF2.

Step 212: The gateway where the PCEF2 is located sends a request to the UE to establish an IP-CAN session response message.

Step 213: When the UE accesses the service of the network where the management domain 2 is located, or the UE accesses an application that has a contract relationship with the network where the management domain 2 is located, the AF2/AAC2 sends a service request message to the DRA2.

The AF2/AAC2 initiates a service request message, where the service request is an AAR message, that is, an Rx session establishment request message, where the service request message carries at least a second UE private network IP address, a second IP domain identifier, and service information. The service request message will be routed to DRA2. The second UE domain IP address is carried by the Framed-IPv4-Address AVP, the second IP domain identifier is carried by the IP-Domain-Id AVP, and the second IP domain identifier is usually the public IP address of the UE. address.

Step 214: The DRA matches the second UE private network IP address and the second IP domain identifier and the DRA binding information, because the second UE private network IP address matches the first UE private network IP address successfully, and the second IP address is obtained. The domain identifier is successfully matched with the first PCEF identifier, so the DRA2 determines that the request message has activated DRA binding information, and the DRA2 sets the destination host domain Destination-Host VAP of the service request message (that is, the AAR message) to the first The value of the PCRF identifier, that is, the PCRF identifier in the matched binding information, and replaces the value of the second IP domain identifier with the value of the first PCEF identifier, that is, the PCEF in the matched binding information. The identifier, where the correspondence between the IP domain identifier and the PCEF identifier is pre-configured.

The DRA2 receives the service request message, where the service request message carries at least a second The private network IP address, the second IP domain identifier, and service information of the UE. The DRA2 matches the second UE private network IP address with the previously saved first UE private network IP address, and matches the second IP domain identifier with the previously saved first PCEF identifier. The DRA2 pre-stores the correspondence between the IP domain identifier and the PCEF identifier.

If the second UE private network IP address is successfully matched with the first UE private network IP address, and the second IP domain identifier matches the first PCEF identifier, the destination host domain of the service request message is set to the first The value of the PCRF identifier, that is, the Destination-Host AVP is set to the value of the PCRF11 identifier, and the value of the second IP domain identifier is replaced by the value of the first PCEF identifier, that is, the IP-Domain-Id. The AVP is set to the value of the PCEF2 identifier.

Step 215: The DRA2 sends the processed service request message to the DRA1.

If there is another Diameter Agent between DRA2 and DRA1, the Diameter Agent forwards the message to the Diameter Agent of the next hop in turn until DRA1. That is, the Diameter Agent between the DRA2 and the DRA1 routes the message to the next hop according to the destination host domain Destination-Host AVP value of the service request message, until the route is to the DRA1, where the Destination-Host AVP takes the value The value of a PCRF identifier.

Step 216: The DRA1 sends the service request message to the PCRF 11 according to the destination host domain Destination-Host AVP.

Step 217: The PCRF11 performs session binding according to the second UE private network IP address and the second IP domain identifier.

The PCRF 11 matches the second UE private network IP address in the service request message with the previously saved first UE private network IP address, and matches the second IP domain identifier with the previously saved first PCEF identifier. Because the matching is successful, the PCRF 11 determines that the request message has a corresponding IP-CAN session, performs session binding, and saves the service information.

The destination-host AVP is set to the value identified by the PCRF11, and the IP-Domain-Id AVP is set to the value of the PCEF2 identifier. Since the value of the IP domain identifier is the same as the previously saved PCEF identifier, that is, the value of PCEF2, the PCRF11 can match according to the same value.

Step 218: The PCRF11 sends an acknowledgement message to the DRA1.

Step 219: The DRA1 forwards the acknowledgement message to the DRA2.

Step 220: The DRA2 forwards the confirmation message to the AF2/AAC2.

In the domestic, an administrative domain can be regarded as a network managed by a provincial company of an operator. A scenario in which a user of the management domain 1 accesses the network through the P-GW of the management domain 2 can be understood as a scenario of inter-provincial roaming. The process described in the second embodiment of FIG. 7 can be understood as that the UE accesses the network by visiting the provincial P-GW, and accesses the service of the visited province or the service with the contracted relationship with the visited province. Set the PCRF identifier saved in the IP-CAN session establishment process in the Destination-Host AVP in the service request message by visiting the DRA of the province. The IP-Domain-Id AVP is set to the PCEF saved during the IP-CAN session establishment process. The method of identification simplifies the configuration of network parameters of the home province DRA and PCRF.

The method of routing the Diameter message provided by the embodiment of the present invention, after receiving the service request message (ie, the Rx session establishment request message) sent by the AF/AAC, the route requesting node DRA of the visited management domain or the visiting province needs to send the service request message to The DRA of the home management domain or the home province is set to the PCRF identifier saved in the IP-CAN session establishment process by calling the management domain DRA in the forwarding service request message, and the IP domain identifier is set to be established in the IP-CAN session. The PCEF identifier saved in the process, thereby simplifying the configuration of the home management domain or the home province DRA and PCRF network parameters.

Embodiment 3

The scenario of the Diameter message routing method provided by the embodiment of the present invention is: the UE accesses and establishes an IP-CAN session through the network where the management domain 2 is located, and the AF/AAC that the UE initiates the service request is in the third management domain or The three administrative domains have contracted relationships, and the third administrative domain can be administrative domain 3.

An embodiment of the present invention provides a method for routing a Diameter message. As shown in FIG. 8, the method for routing a Diameter message may include:

Step 301: The PCEF2 receives a request to establish an IP-CAN session message, where the request to establish an IP-CAN session message carries at least a first user identifier, a first UE private network IP address, and a first PDN identifier.

Step 302: The PCEF2 sends an IP-CAN session establishment indication message (ie, a CCR message) to the DRA2, where the IP-CAN session establishment indication message carries at least the first user identifier, the first a UE private network IP address and the first PDN identifier.

Step 303: The DRA2 receives an IP-CAN session establishment indication message, where the IP-CAN session establishment indication message carries the first user identifier, the first UE private network IP address, and the first PDN identifier. The first user identifier determines that the user is the subscription user of the first management domain, and determines the first PCEF identifier according to the IP-CAN session establishment indication message, and saves the first user identifier, the first UE private network IP address, The first PCEF identifier and the first PDN identifier.

Step 304: The DRA2 sends the establishment IP-CAN session indication message to the DRA1.

If there are other Diameter Agents between DRA2 and DRA1, the Diameter Agent forwards the message to the Diameter Agent of the next hop in turn until DRA1.

Step 305: The DRA1 determines that the PCRF has not been selected for the UE or the P-CAN session, and the DRA1 selects the first PCRF as the PCRF11 for the UE or the IP-CAN session.

Step 306: The DRA1 sends the IP-CAN session establishment indication message to the PCRF11.

Step 307: The PCRF11 receives the IP-CAN session establishment indication message, saves related information of the IP-CAN session, and performs PCC decision.

The PCRF11 may need to obtain the subscription information of the user according to the SPR interaction when performing the PCC decision.

Step 308: The PCRF11 sends an IP-CAN session establishment confirmation message (ie, a CCA message) to the DRA1, where the IP-CAN session establishment confirmation message carries the PCC decision information.

Step 309: The DRA2 receives the DRA1 to send the IP-CAN session establishment confirmation message.

Step 310: The DRA2 determines the first PCRF identifier according to the IP-CAN session establishment confirmation message, and saves the first user identifier, the first UE private network IP address, the first PCEF identifier, and the first PDN identifier. Correspondence relationship with the PCRF identifier, that is, DRA binding information.

The DRA2 receives the IP-CAN session establishment confirmation message, and extracts the first PCRF identifier, that is, the PCRF11 identifier, from the Origin-Host of the IP-CAN session establishment confirmation message, and saves the identifier as the first user identifier. The correspondence between the first UE private network IP address, the first PCEF identifier, the first PDN identifier, and the PCRF11 identifier, that is, the DRA binding information.

Step 311: The DRA2 sends the IP-CAN session establishment confirmation message to the first PCEF.

The first PCEF is PCEF2.

Step 312: The gateway where the PCEF2 is located sends a request to the UE to establish an IP-CAN session response message.

Step 313: When the UE accesses the network where the management domain 3 is located, or the UE accesses an application that has a contractual relationship with the network where the management domain 3 is located, the AF3/AAC3 will initiate a service request message.

The service request is an AAR message, and the service request message may also be referred to as an Rx session establishment request message, where the service request message carries at least a second UE private network IP address, a second IP domain identifier, and service information. The service request message will be routed to DRA3. The second UE domain IP address is carried by the Framed-IPv4-Address AVP, and the second IP domain identifier is carried by the IP-Domain-Id AVP, and the second IP domain identifier is usually the public IP address of the UE.

Step 314: The DRA3 determines, according to the second IP domain identifier, that the IP address of the user access service is allocated by the network where the non-administrative domain 3 is located, and routes the service request message to the DRA2 according to the second IP domain identifier.

The Diameter Agent between the DRA3 and the DRA2 routes the service request message to the next hop according to the second IP domain identifier until the route is forwarded to the DRA2.

It should be noted that, according to the actual application scenario, one or more Diameter Agents may or may not be included between the DRA3 and the DRA2.

Step 315: The DRA matches the saved IP address of the second UE according to the private IP address of the second UE and the second IP domain identifier. The IP address of the private network of the second UE is successfully matched with the IP address of the private network of the first UE. When the second IP domain identifier is successfully matched with the first PCEF identifier, the DRA2 determines that the request message has corresponding active DRA binding information, and the DRA2 sets the destination host domain of the service request message to the first PCRF identifier. The value of the matching, that is, the PCRF identifier in the matched DRA binding information, and the value of the second IP domain identifier is replaced by the value of the first PCEF identifier, that is, the PCEF in the matched DRA binding information. The identifier, where the correspondence between the IP domain identifier and the PCEF identifier is pre-stored.

The DRA2 receives the service request message, where the service request message carries at least a second UE private network IP address, a second IP domain identifier, and service information. The DRA2 matches the second UE private network IP address with the previously saved first UE private network IP address, and matches the second IP domain identifier with the previously saved first PCEF identifier. The DRA2 pre-stores the correspondence between the IP domain identifier and the PCEF identifier.

Step 316: The DRA2 sends the processed service request message to the DRA1.

The Diameter Agent between the DRA2 and the DRA1 routes the message to the next hop according to the value of the destination-domain AVP of the service request message, and the route is sent to the DRA1. The value of the Destination-Host AVP is The value of the first PCRF identifier.

Step 317: The DRA1 sends the processed service request message to the PCRF11 according to the destination host domain.

The value of the destination host field of the processed service request message is the value of the first PCRF identifier, that is, the value of the identifier of the PCRF11. Therefore, the DRA1 sends the processed service request message to the PCRF11.

Step 318: The PCRF11 performs session binding according to the second UE private network IP address and the second IP domain identifier.

The PCRF 11 matches the second UE private network IP address in the processed service request message with the previously saved first UE private network IP address, and matches the second IP domain identifier with the previously saved first PCEF identifier. Because the matching is successful, the PCRF 11 determines that the request message has a corresponding IP-CAN session, and after performing session binding, saves the service information.

In the processed service request message, the Destination-Host AVP is set to the value identified by the PCRF11, and the IP-Domain-Id AVP is set to the value identified by the PCEF2. Since the value of the IP domain identifier is the same as the previously saved PCEF identifier, that is, the value of PCEF2, the PCRF11 can match according to the same value.

In step 319, the PCRF11 sends an acknowledgement message to the DRA1.

Step 320: The DRA1 forwards the acknowledgement message to the DRA2.

Step 321: The DRA2 forwards the acknowledgement message to the DRA3.

Step 322: The DRA3 forwards the confirmation message to the AF3/AAC3.

In China, a management domain can be regarded as a network managed by a provincial company. The process described in the third embodiment of FIG. 8 can be understood as the UE accessing the network through the P-GW of the province and accessing the third province or A business with a contractual relationship with the third province. During the IP-CAN session establishment process, the visiting DRA determines the home province of the UE subscription according to the user identifier of the user, and sends an IP-CAN session establishment indication message to the DRA of the home province. When receiving the Rx session establishment indication message, the DFM in the service request message is set in the Destination-Host AVP in the service request message to be the PCRF identifier saved in the IP-CAN session establishment process, and the IP-Domain-Id AVP is set to be in the IP-Domain-Id AVP. The method of storing the PCEF identifier during the IP-CAN session establishment process simplifies the configuration of the network parameters of the home province DRA and PCRF.

The method of routing the Diameter message provided by the embodiment of the present invention, after receiving the service request message (ie, the Rx session establishment request message) sent by the AF/AAC, the route requesting node DRA of the visited management domain or the visiting province needs to send the service request message to The DRA of the home management domain or the home province is set to the PCRF identifier saved in the IP-CAN session establishment process by calling the management domain DRA in the forwarding service request message, and the IP domain identifier is set to be established in the IP-CAN session. In the process The saved PCEF identifier, thereby simplifying the configuration of the home management domain or the home province DRA and PCRF network parameters.

Embodiment 4

The embodiment of the present invention provides a routing proxy node 1, as shown in FIG. 9, the routing proxy node 1 includes: a receiving unit 10 and a processing unit 11, wherein

The receiving unit 10 is configured to: receive an Rx session establishment request message, where the Rx session establishment request message carries a second UE private network IP address and a second IP domain identifier;

The processing unit 11 is configured to: when the second UE private network IP address and the routing agent DRA binding information match the first UE private network IP address, and the second IP domain identifier and the DRA When the first policy and the charging execution function PCEF identifier in the binding information are successfully matched, the destination host domain Destinaion-Host AVP of the Rx session establishment request message is set as the first policy and meter in the DRA binding information. And the value of the first IPEF identifier in the DRA binding information is replaced by the value of the first IPEF identifier in the DRA binding information.

Optionally, the DRA binding information is saved when the IP connection access network IP-CAN session is established, and the DRA binding information includes at least a first UE private network IP address, the first PCEF identifier, and the first A PCRF identifier, wherein the first PCRF identifier is extracted and obtained from the IP-CAN session establishment confirmation message.

Optionally, as shown in FIG. 10, the routing proxy node 1 further includes: a determining unit 12 and a sending unit 13,

The receiving unit 10 is further configured to: receive the IP-CAN session establishment indication message, where the establishing an IP-CAN session indication message carries the first user identifier, the first UE private network IP address, and the Describe the first PDN identifier;

The determining unit 12 is configured to: determine, according to the first user identifier, that the user is a subscription user of the first administrative domain;

The sending unit 13 is configured to: send the IP-CAN session establishment indication message to the DRA of the first management domain.

The receiving unit 10 is further configured to: receive the IP-CAN session establishment indication message, where the establishing an IP-CAN session indication message carries the first user identifier;

The determining unit 12 is configured to: determine a attribution province of the user according to the first user identifier;

The sending unit 13 is configured to: send the IP-CAN session establishment indication message to the DRA of the home province.

For the understanding of the routing proxy node provided by the embodiment of the present invention, reference may be made to the description of the method for routing the Diameter message in the first embodiment to the third embodiment, and details are not described herein again.

In practical applications, the receiving unit 10, the processing unit 11, the determining unit 12, and the transmitting unit 13 may be a central processing unit (CPU), a microprocessor (MPU), and a digital signal processor (DSP) located on the routing proxy node. Or implementation of a field programmable gate array (FPGA).

The routing proxy node provided by the embodiment of the present invention needs to send a service request message to the home after receiving the service request message (ie, the Rx session establishment request message) sent by the AF/AAC after the DAP of the visited management domain or the visiting province receives the service request message (ie, the Rx session establishment request message). The DRA of the management domain or the affiliation province is set to the PCRF identifier saved in the IP-CAN session establishment process by calling the management domain DRA in the forwarding service request message, and the IP domain identifier is set to be in the IP-CAN session establishment process. The saved PCEF identifier, thereby simplifying the configuration of the home management domain or the home province DRA and PCRF network parameters.

The embodiment of the invention further provides a computer readable storage medium storing computer executable instructions for executing the above Diameter message routing method.

One of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described embodiments can be implemented using a computer program flow, which can be stored in a computer readable storage medium, such as on a corresponding hardware platform (eg, The system, device, device, device, etc. are executed, and when executed, include one or a combination of the steps of the method embodiments.

Optionally, all or part of the steps of the foregoing embodiments may also be implemented by using an integrated circuit, and the steps may be separately fabricated into integrated circuit modules, or multiple modules thereof or The steps are made into a single integrated circuit module.

The devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.

When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. The above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

The above description is only for the embodiments of the present invention and is not intended to limit the scope of the present invention.

Industrial applicability

The Diameter message routing method and the routing proxy node provided by the embodiment of the present invention, when the visited routing domain or the visited routing proxy node DRA receives the service request message (ie, the Rx session establishment request message) sent by the AF/AAC, the service request is sent. The message is sent to the DRA of the home management domain or the home province. The destination host domain in the forwarding service request message is set to the PCRF identifier saved in the IP-CAN session establishment process by the visited management domain DRA, and the IP domain identifier is set to be in the IP- The PCEF identifier saved during the CAN session establishment process, thereby simplifying the configuration of the home management domain DRA and PCRF network parameters.

Claims

A Diameter message routing method includes:

Receiving an Rx session establishment request message, where the Rx session establishment request message carries a second user equipment UE private network IP address and a second IP domain identifier;

When the second UE private network IP address matches the first UE private network IP address in the routing agent node DRA binding information, and the second IP domain identifier and the first policy in the DRA binding information And setting the destination host domain Destination-Host AVP of the Rx session establishment request message to the value of the first policy and the charging rule function PCRF identifier in the DRA binding information. And replacing the value of the second IP domain identifier with the value of the first PCEF identifier in the DRA binding information.
The Diameter message routing method according to claim 1, wherein the DRA binding information is saved when an IP connection access network IP-CAN session is established, and the DRA binding information includes a private network IP address of the first UE. Determining the first PCEF identifier and the first PCRF identifier, wherein the first PCRF identifier is extracted and obtained from the IP-CAN session establishment confirmation message.
The Diameter message routing method according to claim 2, wherein the first PCEF identifier is extracted and obtained from an establishment indication message of the IP-CAN session.
The Diameter message routing method according to claim 3, wherein the Diameter message routing method further comprises:

Receiving the IP-CAN session establishment indication message, where the establishing an IP-CAN session indication message carries a first user identifier;

And determining, by the first user identifier, that the user is a subscription user of the first management domain, and sending the IP-CAN session establishment indication message to the DRA of the first management domain.
The Diameter message routing method according to claim 3, wherein the Diameter message routing method further comprises:

Receiving the IP-CAN session establishment indication message, where the establishing an IP-CAN session indication message carries a first user identifier;

Determining the attribution province of the user according to the first user identifier, and sending the IP-CAN session establishment indication message to the DRA of the home province.
A routing proxy node includes: a receiving unit and a processing unit; wherein

The receiving unit is configured to: receive an Rx session establishment request message, where the Rx session establishment request message carries a second UE private network IP address and a second IP domain identifier;

The processing unit is configured to: when the second UE private network IP address and the routing agent DRA binding information match the first UE private network IP address, and the second IP domain identifier is tied to the DRA The destination host domain Destination-Host AVP of the Rx session establishment request message is set as the first policy and the accounting in the DRA binding information, when the first policy and the accounting execution function PCEF identifier are successfully matched. The value of the rule is determined by the value of the PCRF, and the value of the second IP domain identifier is replaced by the value of the first PCEF identifier in the DRA binding information.
The routing proxy node according to claim 6, wherein the DRA binding information is saved when an IP connection access network IP-CAN session is established, the DRA binding information includes a first UE private network IP address, and the a first PCEF identifier and the first PCRF identifier, wherein the first PCRF identifier is extracted and obtained from the IP-CAN session establishment confirmation message.
The routing proxy node according to claim 6 or 7, wherein said first PCEF identification is extracted and obtained from said establishment indication message of said IP-CAN session.
The routing proxy node according to claim 8, wherein the routing proxy node further comprises: a determining unit and a sending unit,

The receiving unit is further configured to: receive the IP-CAN session establishment indication message, where the establishing an IP-CAN session indication message carries a first user identifier;

The determining unit is configured to: determine, according to the first user identifier, that the user is a subscription user of the first administrative domain;

The sending unit is configured to: send the IP-CAN session establishment indication message to the DRA of the first management domain.
The routing proxy node according to claim 8, wherein the routing proxy node further comprises: a determining unit and a sending unit,

The receiving unit is further configured to: receive the IP-CAN session establishment indication message, where the establishing an IP-CAN session indication message carries a first user identifier;

The determining unit is configured to: determine, according to the first user identifier, a attribution province of the user;

The sending unit is configured to: send the IP-CAN session establishment indication message to the DRA of the home province.