CN106507382A

CN106507382A - A kind of Diameter message method for routing and route agent's node

Info

Publication number: CN106507382A
Application number: CN201510566180.4A
Authority: CN
Inventors: 周晓云; 梁爽
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2015-09-07
Filing date: 2015-09-07
Publication date: 2017-03-15
Anticipated expiration: 2035-09-07
Also published as: CN106507382B; WO2017041507A1

Abstract

The embodiment of the invention discloses a kind of Diameter message method for routing, receives Rx session establishment request messages, the 2nd UE private network IP address and the 2nd IP domain identifiers in the Rx session establishments request message, is carried；When the UE private network IP address in the 2nd UE private network IP address with route agent's DRA binding informations, the match is successful, and the PCEF marks in the 2nd IP domain identifiers and the DRA binding informations are when the match is successful, the value that the destination host domain Destinaion-Host AVP of the Rx session establishments request message are set to the marks of the first "Policy and Charging Rules Function PCRF in the DRA binding informations, and the value of the 2nd IP domain identifiers is replaced with the value that the first strategy and charge execution function PCEF in the DRA binding informations are identified.The embodiment of the present invention further simultaneously discloses a kind of route agent's node.

Description

Diameter message routing method and routing agent node

Technical Field

The invention relates to the technical field of mobile communication PCC, in particular to a Diameter message routing method and a routing agent node.

Background

Policy and Charging Control (PCC) architecture defined by The third Generation Partnership Project (3 GPP), as shown in fig. 1. The Policy and Charging Rules Function (PCRF) performs Quality of Service (QoS) and Charging Policy preparation for the Service using network resources. The PCRF is to formulate a control policy, which needs to combine service information received from an Application Function (AF), user Subscription information received from a Subscription database (SPR), a policy configured by an operator, and the like. The PCRF issues a control Policy formulated for the service to a Policy and Charging Enforcement Function (PCEF) or a Bearer Binding and Event Reporting Function (BBERF) for execution. Meanwhile, the PCRF can subscribe the bearer layer related events to the PCEF and/or the BBERF so as to timely sense and change the control strategy when the bearer layer has the events. In addition, the PCEF and the Traffic Detection Function (TDF) can perform Application Detection and Control functions according to a PCC rule (PCEF) or an Application Detection Control (ADC) rule (TDF) issued by the PCRF. An Online Charging System (OCS) provides a credit control function based on users and traffic data flows. An offline charging System (OFCS) provides charging functions based on user and traffic data flows.

With the development of the mobile internet, an operator needs to communicate with a third-party data application provider to guarantee the QoS for the services provided by the third-party data application provider. Due to the Diameter protocol adopted by the Rx interface supported by PCC at present, most third party data application providers are better at developing SOAP, REST based protocols. The research in the industry currently supports the Rx interface based on SOAP/REST protocol with PCC architecture. A logic function called Protocol Converter (PC) is directly set in PCRF and AF to convert SOAP or REST Protocol into Diameter. Further, some Access Control functions may be added to the PC, so as to better implement Access Control of an operator on third-party data applications, at this time, the logic function is also referred to as an Application Access Control (AAC) functional entity, as shown in fig. 2, a schematic diagram of a PCC architecture of AAC.

There are multiple PCRF nodes in a Public Land Mobile Network (PLMN) of an Evolved Packet System (EPS), and all PCRF nodes belong to one or more diameter (PCRF) domains, which are referred to as PCRF domains in the following description. A connection of a UE to a Packet Data Network (PDN) is called an IP Connectivity 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 one IP-CAN session are associated to the same PCRF, the EPS introduces a logic function module, Diameter Routing Agent (DRA) in each PCRF domain. When UE establishes an IP-CAN session to a PDN, the DRA selects a PCRF for the IP-CAN session. The PCEF, BBERF and AF associated with this IP-CAN session are associated by the DRA to the selected PCRF. Generally, one EPS network may have multiple Diameter management domains. As shown in fig. 3, there are two Diameter management domains in a PLMN. The DRA is responsible for managing the PCRF in the local domain, and the PCC clients in the local domain, such as PCEF, BBERF, AF, AAC, can find the correct PCRF through the DRA in the local domain. For the subscribed user in the management domain 1, when the UE accesses the management domain 1, the Diameter message sent by the PCC clients such as BBERF, PCEF, etc. in the management domain 1 is routed to the correct PCRF by DRA1, and if the UE moves to the management domain 2, the message sent by the PCC clients such as BBERF, PCEF, etc. in the management domain 2 first passes through DRA2, DRA2 sends the Diameter message to DRA1 according to the related information, and DRA1 routes the message to the correct PCRF. One or more Diameter agents are typically deployed prior to DRA1 and DRA2 for routing messages of DRA1 to DRA 2.

To Address the shortage of IP addresses, operators typically deploy Network Address Translation (NAT) devices behind packet Network gateways (P-GW). As shown in fig. 4, the PCC architecture diagram of NAT makes the same PDN connection carry a private IP address used inside an Evolved Packet Core (EPC), different from a public IP address used in an external Packet network due to the presence of NAT.

As shown in fig. 5, it is a schematic flow chart of the UE accessing the network through the P-GW (where PCEF2 is located) where management domain 2 is located and establishing an IP-CAN session in the prior art.

Step 501, receiving a message requesting to establish an IP-CAN session by the PCEF2, where the message requesting to establish the IP-CAN session 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 identity, the first UE private network IP address, and the first PDN identity. The IP-CAN session establishment indication message is specifically implemented as a Diameter CCR (Credit Control Request) message.

Step 503, receiving the IP-CAN session establishment indication message by DRA2, determining that the user is a subscriber of the administrative domain 1 according to the first user identifier, extracting a first PCEF identifier from the Origin-Host AVP of the IP-CAN session establishment indication message, and storing the first user identifier, the first UE private network IP address, the first PCEF identifier, and the first PDN identifier by DRA 2.

Step 504, the DRA2 sends the IP-CAN session establishment indication message to the DRA 1. If other Diameter agents exist between DRA2 and DRA1, the Diameter agents forward messages to the Diameter Agent of the next hop in sequence until DRA 1.

Step 505, DRA1 judges that no PCRF has been selected for the UE or the IP-CAN session, the DRA1 selects PCRF11 for the UE or the IP-CAN session, and stores the correspondence of the first subscriber identity, the first PDN identity, the first UE private network IP address, the first PCEF identity, and the PCRF 11. The corresponding relation between (the first subscriber identity, the first PDN identity, the first UE private network IP address, the first PCEF identity, and the PCRF11) is also referred to as DRA binding information.

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

Step 507, the PCRF11 receives the IP-CAN session establishment indication message, stores the relevant information of the IP-CAN session, and makes a PCC decision, and the PCRF11 may need to interact with the SPR when making a decision, 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 DRA 2.

Step 510, the DRA2 sends the IP-CAN session establishment acknowledgement message to the PCEF 2.

Step 511, the gateway where the PCEF2 is located sends a response message requesting establishment of an IP-CAN session to the UE.

Step 512, when the UE accesses the service of the network where the management Domain 2 is located, or the UE accesses the application having a subscription 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 called an Rx session establishment request message), 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 routed to DRA2, where the second UE private network IP Address is carried by Framed-IPv4-Address AVP, the second IP Domain identifier is carried by IP-Domain-Id AVP, and the second IP Domain identifier is usually a public network IP Address of the UE.

Step 513, the DRA2 receives the AAR message, matches the second UE private network IP address with the first UE private network IP address stored before, and matches the second IP domain identifier with the first PCEF identifier stored before, where DRA2 stores the correspondence between the IP domain identifier and the PCEF identifier in advance, and after the matching is successful, DRA2 forwards the AAR message to DRA1, where after one or more Diameter agents between DRA2 and DRA1 are matched by the above method, the message is routed to the correct next hop until DRA 1.

Step 514, the DRA1 matches the second UE private network IP address, the second IP domain identifier, and the DRA binding information stored before according to the matching (that is, the second UE private network IP address matches the first UE private network IP address stored before, and matches the second IP domain identifier with the first PCEF identifier stored before, where DRA1 pre-stores the correspondence between the IP domain identifier and the PCEF identifier), and the matching is successful, and it is determined that the IP-CAN session established before the UE selects PCRF 11. DRA1 forwards the service request message to PCRF 11.

Step 515, the PCRF11 performs session binding according to the second UE private network IP address and the second IP domain identifier (i.e. matching the second UE private network IP address with the first UE private network IP address stored before and matching the second IP domain identifier with the first PCEF identifier stored before), and performs session binding after successful matching, and stores the service information.

Step 516, PCRF11 sends an acknowledgement message to DRA 1.

Step 517, DRA1 forwards the confirmation message to DRA 2.

Step 518, DRA2 forwards the confirmation message to AF2/AAC 2.

In order to enable DRA2 to be routed to the correct PCRF11 in the management domain 2 and enable PCRF11 to perform the correct session binding, the prior art requires that the DRA (i.e., DRA2) in the management domain 2, the Diameter Agent between DRA2 and DRA1, the DRA (i.e., DRA1) in the management domain 1, and the PCRF11 all need to store the correspondence between the PCEF identifier and the IP domain identifier in the management domain 2, which may lead to complexity of network configuration. Moreover, in order to ensure that the Diameter message sent by DRA2 CAN be correctly routed by DRA1, the Diameter Agent between DRA2 and DRA1 needs to be able to store information such as UE private network IP address and PCEF identifier in the IP-CAN establishment process to perform correct routing, thereby increasing the capability requirement for the Diameter Agent.

Disclosure of Invention

To solve the foregoing technical problems, embodiments of the present invention provide a Diameter message routing method and a routing agent node, which can simplify network parameter configuration.

The technical scheme of the invention is realized as follows:

the embodiment of the invention provides a Diameter message routing method, which comprises the following steps:

receiving an Rx session establishment request message, wherein 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 is successfully matched with the first UE private network IP address in the DRA binding information and the second IP domain identification is successfully matched with the first Policy and Charging Enforcement Function (PCEF) identification in the DRA binding information, setting Destination Host domain Destination-Host AVP of the Rx session establishment request message as the value of the first Policy and Charging Rule Function (PCRF) identification in the DRA binding information, and replacing the value of the second IP domain identification with the value of the first PCEF identification in the DRA binding information.

Further, the DRA binding information is stored when an IP connection access network IP-CAN session is established, and the DRA binding information at least includes 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.

Further, the first PCEF identity is extracted from the setup indication message of the IP-CAN session.

Further, the Diameter message routing method further includes:

receiving the IP-CAN session establishment indication message, wherein the IP-CAN session establishment indication message carries the first user identifier;

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

Further, the Diameter message routing method further includes:

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

An embodiment of the present invention further provides a routing proxy node, where the 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;

and the processing unit is configured to, when 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 policy and charging enforcement function PCEF identifier in the DRA binding information, set a Destination Host domain Destination-Host AVP of the Rx session establishment request message to a value of the first policy and charging rules function PCRF identifier in the DRA binding information, and replace the value of the second IP domain identifier with the value of the first PCEF identifier in the DRA binding information.

Further, the routing agent node further comprises: a determining unit and a sending unit, wherein the determining unit is used for determining the data transmission rate,

the receiving unit is configured to receive the IP-CAN session establishment indication message, where the IP-CAN session establishment indication message carries the first user identifier;

the determining unit is used for determining that the user is a signed user of the first management domain according to the first user identification;

and the sending unit is used for sending the IP-CAN session establishment indication message to the DRA in the first management domain.

the determining unit is used for determining the affiliation province of the user according to the first user identification;

and the sending unit is used for sending the IP-CAN session establishment indication message to the DRA of the attribution province.

The embodiment of the invention provides a Diameter message routing method and a routing agent node, wherein an Rx session establishment request message is received, and 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 is successfully matched with the first UE private network IP address in the DRA binding information and the second IP domain identification is successfully matched with the first PCEF identification in the DRA binding information, setting the Destination Host domain Destination-Host AVP of the Rx session establishment request message as the value of the first policy and charging rule function PCRF identification in the DRA binding information, and replacing the value of the second IP domain identification with the value of the first policy and charging execution function PCEF identification in the DRA binding information. In the Diameter message routing method and the routing agent node provided in the embodiment of the present invention, after receiving a service request message (i.e., an Rx session establishment request message) sent by AF/AAC, a routing agent node DRA in a visited management domain or a visited province needs to send the service request message to a DRA in a home management domain or a home province, a destination host domain in forwarding the service request message through the DRA in the visited management domain is set as a PCRF identifier stored in an IP-CAN session establishment process, and the IP domain identifier is set as a PCEF identifier stored in the IP-CAN session establishment process, so that configuration of parameters of the home management domain DRA and the PCRF CAN be simplified.

Drawings

FIG. 1 is a schematic diagram of a PCC architecture;

FIG. 2 is a schematic representation of a PCC architecture of AAC;

FIG. 3 is a schematic diagram of an architecture for interworking between multiple administrative domains;

FIG. 4 is a schematic diagram of a PCC architecture for NAT;

FIG. 5 is a schematic flow chart of an IP-CAN session and a service request in the prior art;

figure 6 is a first flowchart of a Diameter message routing method according to an embodiment of the present invention;

figure 7 is a second flowchart of a Diameter message routing method according to an embodiment of the present invention;

figure 8 is a third schematic flow chart of a Diameter message routing method according to an embodiment of the present invention;

fig. 9 is a first schematic structural diagram of a routing agent node according to an embodiment of the present invention;

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

Detailed Description

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

It should be noted that the terms "first, second and the like" in the embodiments of the present invention are used for distinguishing similar objects, and are not necessarily used for describing a specific order or sequence.

Example one

An embodiment of the present invention provides a Diameter message routing method, as shown in fig. 6, where the Diameter message routing method may include:

step 101, 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.

It should be noted that the execution subject of the Diameter message Routing method provided in the embodiment of the present invention is a Routing Agent node (DRA) of a visited management domain or a visited province, that is, DRA 2.

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

Step 102, when the second UE private network IP address is successfully matched with the first UE private network IP address in the DRA binding information, and the second IP Domain identifier IP Domain id is successfully matched with the first policy and charging enforcement function 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 charging rules 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, wherein the corresponding relationship between the IP Domain identifier and the PCEF identifier is preconfigured.

Specifically, DRA2 receives the IP-CAN session establishment confirmation message sent by DRA1, extracts a first PCRF identifier, that is, a PCRF11 identifier, from the Origin-Host AVP of the IP-CAN session establishment confirmation message, and stores the first PCRF identifier as a corresponding relationship (a first user identifier, a first UE private network IP address, a first PCEF identifier, a first PDN identifier, and the first PCRF identifier), which is also referred to as DRA binding information, that is, the DRA binding information is stored when an IP connectivity access network IP-CAN session is established, where the DRA binding information at least includes the first UE private network IP address, the first PCEF identifier, and the first PCRF identifier is extracted from the IP-CAN session establishment confirmation message.

DRA2 matches the second UE private network IP address with the first UE private network IP address, and matches the second IP domain identification with the first PCEF identification. Wherein, DRA2 pre-stores the corresponding relationship between the IP domain identifier and the PCEF identifier.

When the second UE private network IP address is successfully matched with the first UE private network IP address, and the second IP Domain identification is successfully matched with the first PCEF identification, the Destination Host Domain of the Rx session establishment request message is set to be the value of the first PCRF identification, namely the Destination-Host AVP is set to be the value of the PCRF11 identification, and the value of the second IP Domain identification is replaced by the value of the first PCEF identification, namely the IP-Domain-Id AVP is set to be the value of the PCEF2 identification.

In the Diameter message routing method provided by the embodiment of the invention, when a routing agent node DRA of a visited management domain or a visited province receives a service request message (namely an Rx session establishment request message) sent by AF/AAC, the service request message needs to be sent to a DRA of a home management domain or a home province, a target host domain in the forwarding service request message through the DRA of the visited management domain is set as a PCRF (policy and charging rules function) identifier stored in the IP-CAN session establishment process, and the IP domain identifier is set as a PCEF (policy and charging rules function) identifier stored in the IP-CAN session establishment process, so that the parameter configuration of the home management domain or the DRA of the home province and the PCRF CAN be simplified.

Example two

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

An embodiment of the present invention provides a Diameter message routing method, as shown in fig. 7, where the Diameter message routing method may include:

step 201, receiving a message requesting to establish an IP-CAN session by the PCEF2, where the message requesting to establish the IP-CAN session at least carries 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 identity, the first UE private network IP address, and the first PDN identity.

The IP-CAN session establishment indication message is specifically implemented as a Diameter Credit Control Request (CCR) message.

Step 203, receiving an IP-CAN session establishment indication message, namely a CCR message, by 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; and determining that the user is a signed user in a first management domain according to the first user identifier, determining a first PCEF identifier according to the IP-CAN session establishment indication message, and storing the first user identifier, the first UE private network IP address, the first PCEF identifier and the first PDN identifier.

Specifically, the DRA2 receives the IP-CAN session establishment instruction message, and determines that the user is a first administrative domain, that is, a subscriber of the administrative domain 1, according to the first user identifier. The DRA2 extracts a first PCEF identifier from Origin-Host AVP of the IP-CAN session establishment indication message, and stores the first user identifier, the first UE private network IP address, the first PCEF identifier and the first PDN identifier.

And step 204, the DRA2 sends the IP-CAN session establishment indication message to the DRA 1.

Specifically, if there are other Diameter agents between DRA2 and DRA1, the Diameter agents forward messages to the Diameter Agent of the next hop in sequence until DRA 1.

Step 205, DRA1 judges that no PCRF has been selected for the UE or the IP-CAN session, and the DRA1 selects a first PCRF for the UE or the IP-CAN session as PCRF 11.

Specifically, DRA1 stores the corresponding relationship among the first user identifier, the first PDN identifier, the first UE private network IP address, the first PCEF identifier, and PCRF11, that is, DRA binding information.

Step 206, DRA1 sends the IP-CAN session establishment indication message to PCRF 11.

Step 207, the PCRF11 receives the IP-CAN session establishment indication message, stores the relevant information of the IP-CAN session, and makes a PCC decision.

When performing a PCC decision, PCRF11 may need to interact with an SPR to obtain subscription information of the user.

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.

And step 209, receiving the DRA1 by the DRA2 and sending the IP-CAN session establishment confirmation message.

Specifically, 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 a first PCRF identifier according to the IP-CAN session establishment confirmation message, and stores a corresponding relationship between the first user identifier, the first UE private network IP address, the first PCEF identifier, the first PDN identifier, and the first PCRF identifier, that is, DRA binding information.

Specifically, the DRA2 receives the DRA1 and sends the IP-CAN session establishment confirmation message, that is, a CCA message, proposes a first PCRF identifier, that is, a PCRF11 identifier, from the Origin-Host of the IP-CAN session establishment confirmation message, and stores the first PCRF identifier, the first UE private network IP address, the first PCEF identifier, the first PDN identifier, and a corresponding relationship of the PCRF11 identifier, that is, DRA binding information.

Step 211, the DRA2 sends the IP-CAN session establishment acknowledgement message to the first PCEF.

Wherein the first PCEF is PCEF 2.

Step 212, the gateway where PCEF2 is located sends a response message requesting establishment of an IP-CAN session to the UE.

Step 213, when the UE accesses the service of the network where the administrative domain 2 is located, or the UE accesses the application having a subscription relationship with the network where the administrative domain 2 is located, the AF2/AAC2 sends a service request message to the DRA 2.

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

Step 214, the DRA2, according to the matching of the second UE private network IP address, the second IP domain identifier and the DRA binding information, since the second UE private network IP address is successfully matched with the first UE private network IP address, and the second IP domain identifier is successfully matched with the first PCEF identifier, the DRA2 determines that the request message has activated DRA binding information, the DRA2 sets the Destination Host domain Destination-Host VAP of the service request message (i.e., the AAR message) to the value of the first PCRF identifier, i.e., 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, i.e., the PCEF identifier in the matched binding information, wherein the corresponding relationship between the IP domain identifier and the PCEF identifier is preconfigured.

Specifically, DRA2 receives the service request message, where the service request message at least carries a second UE private network IP address, a second IP domain identifier, and service information. DRA2 matches the second UE private network IP address with the first UE private network IP address stored before, and matches the second IP domain identification with the first PCEF identification stored before. Wherein, DRA2 pre-stores the corresponding relationship between the IP domain identifier and the PCEF identifier.

And when the second UE private network IP address is successfully matched with the first UE private network IP address and the second IP Domain identifier is successfully matched with the first PCEF identifier, setting a Destination Host Domain of the service request message as a value of the first PCRF identifier, namely setting a Destination-Host AVP as a value of the PCRF11 identifier, and replacing the value of the second IP Domain identifier with the value of the first PCEF identifier, namely setting an IP-Domain-Id AVP as a value of the PCEF2 identifier.

Step 215, the DRA2 sends the processed service request message to DRA 1.

Specifically, if there are other Diameter agents between DRA2 and DRA1, the Diameter agents forward messages to the Diameter Agent of the next hop in sequence until DRA 1. That is, the Diameter Agent between DRA2 and 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 message is routed to DRA1, wherein the Destination-Host AVP value is the value of the first PCRF identifier.

Step 216, the DRA1 sends the service request message to the PCRF11 according to the Destination Host domain Destination-Host AVP.

And step 217, the PCRF11 performs session binding according to the second UE private network IP address and the second IP domain identifier.

Specifically, the PCRF11 matches the second UE private network IP address in the service request message with the first UE private network IP address stored before, and matches the second IP domain identifier with the first PCEF identifier stored before, and because the matching is successful, the PCRF11 determines that the request message has a corresponding IP-CAN session, performs session binding, and stores the service information.

Specifically, in the processed service request message, the Destination-Host AVP is set as the value identified by PCRF11, and the IP-Domain-Id AVP is set as the value identified by PCEF 2. Because the value of the IP domain identifier is the same as the previously stored PCEF identifier, i.e., the value of PCEF2, PCRF11 can match according to the same value.

Step 218, PCRF11 sends an acknowledgement message to DRA 1.

Step 219, DRA1 forwards the confirmation message to DRA 2.

Step 220, DRA2 forwards the confirmation message to AF2/AAC 2.

Specifically, in China, a management domain can generally consider a network managed by a provincial company of an operator, and 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 cross-provincial roaming. The process described in the second embodiment of fig. 7 can be understood as that the UE accesses the network through the P-GW in the visited province and accesses the service in the visited province or the service having a subscription relationship with the visited province. The configuration of network parameters of DRA and PCRF in the province of affiliation is simplified by setting DRA in the province of visit to PCRF identification stored in the establishment process of IP-CAN session in Destination-Host AVP and setting the DRA in the province of IP-Domain-Id AVP to PCEF identification stored in the establishment process of IP-CAN session.

EXAMPLE III

The scenario of the Diameter message routing method provided by the embodiment of the invention is as follows: the UE accesses and establishes an IP-CAN session through the network where the management domain 2 is located, the AF/AAC of the UE initiating the service request is in a third management domain or has a subscription relationship with the third management domain, and the third management domain CAN be a management domain 3.

An embodiment of the present invention provides a Diameter message routing method, as shown in fig. 8, where the Diameter message routing method may include:

step 301, receiving a message requesting to establish an IP-CAN session by the PCEF2, where the message requesting to establish the IP-CAN session at least carries 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 (i.e., CCR 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.

Step 303, receiving an IP-CAN session establishment indication message by 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; and determining that the user is a signed user in a first management domain according to the first user identifier, determining a first PCEF identifier according to the IP-CAN session establishment indication message, and storing 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 message for indicating the establishment of the IP-CAN session to the DRA 1.

Step 305, DRA1 judges that no PCRF has been selected for the UE or the P-CAN session, and the DRA1 selects a first PCRF for the UE or the IP-CAN session as PCRF 11.

Step 306, DRA1 sends the IP-CAN session establishment indication message to PCRF 11.

Step 307, the PCRF11 receives the IP-CAN session establishment indication message, stores the relevant information of the IP-CAN session, and makes a PCC decision.

When performing a PCC decision, PCRF11 may need to obtain subscription information of the user according to SPR interaction.

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

Step 309, receiving DRA1 by DRA2 and sending the IP-CAN session establishment confirmation message.

Step 310, the DRA2 determines a first PCRF identifier according to the IP-CAN session establishment confirmation message, and stores a corresponding relationship among the first user identifier, the first UE private network IP address, the first PCEF identifier, the first PDN identifier, and the PCRF identifier, that is, DRA binding information.

Specifically, the DRA2 receives the DRA1 and sends the IP-CAN session establishment confirmation message, extracts a first PCRF identifier, that is, a PCRF11 identifier, from the Origin-Host of the IP-CAN session establishment confirmation message, and stores the first PCRF identifier, the first UE private network IP address, the first PCEF identifier, the first PDN identifier, and a corresponding relationship of the PCRF11 identifier, that is, DRA binding information.

Step 311, DRA2 sends the IP-CAN session establishment acknowledgement message to the first PCEF.

Wherein the first PCEF is PCEF 2.

Step 312, the gateway where PCEF2 is located sends a response message requesting establishment of an IP-CAN session to the UE.

Step 313, when the UE accesses the network where the administrative domain 3 is located, or the UE accesses the application having the subscription relationship with the network where the administrative domain 3 is located, the AF3/AAC3 will initiate a service request message.

The service request is an AAR message, which 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, and the service request message is routed to DRA 3. The second UE private network IP Address is carried by Framed-IPv4-Address AVP, the second IP Domain identification is carried by IP-Domain-Id AVP, and the second IP Domain identification is generally the UE public network IP Address.

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

And the Diameter Agent between DRA3 and DRA2 routes the service request message to the next hop according to the second IP domain identifier until the service request message is routed to DRA 2.

It should be noted that, according to an actual application scenario, one or more Diameter agents may be included between DRA3 and DRA2, or no Diameter Agent may be included.

Step 315, the DRA2 matches the stored DRA binding information according to the second UE private network IP address and the second IP domain identifier; when the second UE private network IP address is successfully matched with the first UE private network IP address, and the second IP domain identifier is successfully matched with the first PCEF identifier, DRA2 determines that the request message has corresponding activated DRA binding information, DRA2 sets the destination host domain of the service request message to the value of the first PCRF identifier, that is, the PCRF identifier in the matched DRA binding information, and replaces the value of the second IP domain identifier with the value of the first PCEF identifier, that is, the PCEF identifier in the matched DRA binding information, where a correspondence between the IP domain identifier and the PCEF identifier is pre-stored.

And step 316, sending the processed service request message to DRA1 by DRA 2.

Specifically, the Diameter Agent between DRA2 and DRA1 routes the message to the next hop according to the Destination Host domain Destination-Host AVP value of the processed service request message until the message is routed to DRA1, where the Destination-Host AVP value is the value of the first PCRF identifier.

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

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

Step 318, the PCRF11 performs session binding according to the second UE private network IP address and the second IP domain identification.

Specifically, the PCRF11 matches the second UE private network IP address in the processed service request message with the previously stored first UE private network IP address, and matches the second IP domain identifier with the previously stored first PCEF identifier. And the PCRF11 judges that the request message has a corresponding IP-CAN session due to successful matching, and stores the service information after executing session binding.

Step 319, PCRF11 sends an acknowledgement message to DRA 1.

Step 320, DRA1 forwards the confirmation message to DRA 2.

Step 321, DRA2 forwards the confirmation message to DRA 3.

Step 322, DRA3 forwards the confirmation message to AF3/AAC 3.

Specifically, in China, one management domain may generally consider a network managed by a province company of an operator, and the process described in the third embodiment of fig. 8 may be understood as that the UE accesses the network through the P-GW in the visited province and accesses the third province or a service having a subscription relationship with the third province. In the process of establishing the IP-CAN session, the DRA of the visiting province determines the attribution province signed by the UE according to the user identification of the user, and sends an IP-CAN session establishment indication message to the DRA of the attribution province. When receiving the Rx conversation establishment indication message, the DRA of the visiting province is set as the PCRF identifier stored in the IP-CAN conversation establishment process in the Destination-Host AVP in the service request message, and the PCEF identifier stored in the IP-CAN conversation establishment process in the IP-Domain-Id AVP, so that the configuration of the DRA and the PCRF network parameters of the belonging province is simplified.

Example four

An embodiment of the present invention provides a routing agent node 1, and as shown in fig. 9, the routing agent node 1 includes: a receiving unit 10, 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 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 policy and charging enforcement function PCEF identifier in the DRA binding information, set the destination Host domain destination-Host AVP of the Rx session establishment request message as a value of the first policy and charging rules function PCRF identifier in the DRA binding information, and replace the value of the second IP domain identifier with the value of the first PCEF identifier in the DRA binding information.

Further, as shown in fig. 10, the routing agent node 1 further includes: the determination unit 12, the sending unit 13,

the receiving unit 10 is configured to receive the 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 determining unit 12 is configured to determine, according to the first user identifier, that a user is a subscriber of the first administrative domain;

the sending unit 13 is configured to send the IP-CAN session establishment instruction message to the DRA in the first management domain.

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

the determining unit 12 is configured to determine, according to the first subscriber identity, an affiliation province of the user;

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

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

In practical applications, the receiving unit 10, the processing unit 11, the determining unit 12, and the sending unit 13 may be implemented by a Central Processing Unit (CPU), a microprocessor unit (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like located on the routing agent node.

In the routing agent node provided in the embodiment of the present invention, after receiving a service request message (i.e., an Rx session establishment request message) sent by AF/AAC, a routing agent node DRA in a visited management domain or a visited province needs to send the service request message to a DRA in a home management domain or a home province, a destination host domain in forwarding the service request message through the DRA in the visited management domain is set as a PCRF identifier stored in an IP-CAN session establishment process, and the IP domain identifier is set as a PCEF identifier stored in the IP-CAN session establishment process, so that configuration of network parameters of the home management domain or the home province DRA and the PCRF CAN be simplified.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A Diameter message routing method, comprising:

2. The Diameter message routing method of claim 1 wherein the DRA binding information is stored when an IP connectivity access network IP-CAN session is established, the DRA binding information at least includes a first UE private network IP address, the first PCEF identity, and the first PCRF identity, wherein the first PCRF identity is extracted from the IP-CAN session establishment confirmation message.

3. The Diameter message routing method of claim 1 or 2 wherein the first PCEF identity is extracted from an establishment indication message of the IP-CAN session.

4. The Diameter message routing method of claim 3, further comprising:

5. The Diameter message routing method of claim 3, further comprising:

6. A routing proxy node, characterized in that the routing proxy node comprises: a receiving unit and a processing unit; wherein,

7. The routing agent node of claim 6, wherein the DRA binding information is stored when an IP connectivity access network IP-CAN session is established, and the DRA binding information at least includes a first UE private network IP address, the first PCEF identity, and the first PCRF identity, wherein the first PCRF identity is extracted from the IP-CAN session establishment confirmation message.

8. The routing agent node according to claim 6 or 7, wherein the first PCEF identity is extracted from an establishment indication message of the IP-CAN session.

9. The routing proxy node of claim 8, wherein the routing proxy node further comprises: a determining unit and a sending unit, wherein the determining unit is used for determining the data transmission rate,

10. The routing proxy node of claim 8, wherein the routing proxy node further comprises: a determining unit and a sending unit, wherein the determining unit is used for determining the data transmission rate,