CN106803808B - Routing agent method and node - Google Patents

Routing agent method and node Download PDF

Info

Publication number
CN106803808B
CN106803808B CN201510827844.8A CN201510827844A CN106803808B CN 106803808 B CN106803808 B CN 106803808B CN 201510827844 A CN201510827844 A CN 201510827844A CN 106803808 B CN106803808 B CN 106803808B
Authority
CN
China
Prior art keywords
user
dra
session message
address
identifier
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201510827844.8A
Other languages
Chinese (zh)
Other versions
CN106803808A (en
Inventor
何宇锋
林奕琳
刘洁
张岚
吴敏清
程淑荣
黎明雪
曹磊
王波
王哲
区洪辉
张�雄
李志强
刁益辉
王庆扬
张琳峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN201510827844.8A priority Critical patent/CN106803808B/en
Publication of CN106803808A publication Critical patent/CN106803808A/en
Application granted granted Critical
Publication of CN106803808B publication Critical patent/CN106803808B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/30—Routing of multiclass traffic

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

The invention provides a routing agent method and a node, and relates to the field of intelligent pipelines. The routing agent method of the invention comprises the following steps: the routing agent node DRA acquires an Rx session message; the DRA judges whether the user is the user in the area or not according to the user identification in the Rx session message; and if the user is the local user, acquiring the corresponding PCRF according to the user identifier and the APN, and routing the Rx session message to the corresponding PCRF. By the method, the DRA can determine the PCRF to which the user belongs according to the acquired user identifier and APN information in the Rx session message, so that the Rx session message can be sent to the corresponding PCRF to realize session binding.

Description

Routing agent method and node
Technical Field
The invention relates to the field of intelligent pipelines, in particular to a routing agent method and a node.
Background
According to 3GPP series standards, an interface based on a Diameter protocol in LTE uses a DRA (Diameter routing agent, routing agent node) signaling network for addressing policy and routing. The current Gx interface roaming technology is supported by the industry standard and is commercially available, but the Rx interface roaming technology is not supported by the mature industry/enterprise standard.
Meanwhile, LTE is commercialized and popularized, multiple APNs (Access Point names ) will exist to Access scenes (Internet, VoLTE, etc.), and an increase in the number of 4G users will also require core network expansion, and at that time, in the same area, such as a provincial administrative district, multiple sets of PCRF and PCEF scenes will appear, which increases the difficulty for Rx interface roaming.
Disclosure of Invention
An object of the present invention is to provide a scheme for Rx interface roaming.
According to an aspect of the present invention, a routing agent method is provided, including: the routing agent node DRA acquires an Rx session message; the DRA judges whether the user is the user in the area or not according to the user identification in the Rx session message; and if the user is the local user, acquiring the corresponding PCRF according to the user identifier and the APN, and routing the Rx session message to the corresponding PCRF.
Further, if the user is not the user in the local area, roaming the Rx session message to the DRA in the home area, so that the DRA in the home area executes the step of acquiring the corresponding PCRF according to the user identifier and the APN.
Further, after the DRA acquires the Rx session message, judging whether the Rx session message includes a user identifier; if the user identification is included, executing the step of judging whether the user is the user in the area according to the user identification; if not, the DRA determines the PCRF based on the association information stored by the DRA according to the public network IP address and the private network IP address in the Rx session message, and routes the Rx session message to the corresponding PCRF.
Further, determining the PCRF based on the association information stored by the DRA according to the public network IP address and the private network IP address in the Rx session message specifically includes: judging whether the public network IP address is in the local area, if so, judging whether the user belongs to the local area according to the private network IP address; if the domain belongs to the region, determining the PCRF according to the association information stored by the DRA, and routing the Rx session message to the corresponding PCRF; if the domain does not belong to the domain, acquiring the user identifier and the APN according to the association information, filling the user identifier and the APN into the Rx session message, forwarding the Rx session message to the upper level DRA, and judging whether the Rx session message comprises the user identifier or not by the upper level DRA.
Further, if the public network IP address is judged not to be located in the local area, the Rx session message is routed to the upper level DRA, and the upper level DRA executes the step of judging whether the user is located in the local area according to the public network IP address.
Further, the step of judging whether the public network IP address is located in the local area specifically includes: and mapping the public network IP address into an IP domain identifier, and judging whether the IP domain identifier is the local domain identifier.
Further, the method also comprises the following steps: when the user is online, the DRA generates and stores the associated information, wherein the associated information comprises the user private network IP address, the PCEF identifier, the user identifier and the PCRF identifier in the Gx session.
Further, the DRA also stores a corresponding relationship between the PCEF identifier and the IP domain identifier, so as to determine the corresponding PCEF identifier according to the IP domain identifier.
By the method, the DRA can determine the PCRF to which the user belongs according to the acquired user identifier and APN information in the Rx session message, so that the Rx session message can be sent to the corresponding PCRF to realize session binding.
According to another aspect of the present invention, a routing proxy node is provided, comprising: a message obtaining module, configured to obtain an Rx session message; the local area user judging module is used for judging whether the user is the local area user according to the user identification in the Rx session message; and the execution module is used for acquiring the corresponding PCRF according to the user identifier and the APN and routing the Rx session message to the corresponding PCRF under the condition that the user is the local area user.
Further, when the local area user judgment module judges that the user is not the local area user, the execution module roams the Rx session message to the DRA in the home area, so that the home area DRA executes the step of acquiring the corresponding PCRF according to the user identifier and the APN.
Further, still include: the identification judging module is used for judging whether the Rx session message comprises the user identification or not after the DRA acquires the Rx session message; if the user identification is included, activating an identification judgment module; and if the Rx session message does not comprise the user identifier, the execution module is also used for determining the PCRF based on the correlation information stored by the DRA according to the public network IP address and the private network IP address in the Rx session message, and routing the Rx session message to the corresponding PCRF.
Further, determining the PCRF based on the association information stored by the DRA according to the public network IP address and the private network IP address in the Rx session message specifically includes: judging whether the public network IP address is in the local area, if so, judging whether the user belongs to the local area according to the private network IP address; if the domain belongs to the region, determining the PCRF according to the association information stored by the DRA, and routing the Rx session message to the corresponding PCRF; if the domain does not belong to the domain, acquiring the user identifier and the APN according to the association information, filling the user identifier and the APN into the Rx session message, forwarding the Rx session message to the upper level DRA, and judging whether the Rx session message comprises the user identifier or not by the upper level DRA.
Further, if the public network IP address is judged not to be located in the local area, the Rx session message is routed to the upper level DRA, and the upper level DRA executes the step of judging whether the user is located in the local area according to the public network IP address.
Further, the step of judging whether the public network IP address is located in the local area specifically includes: and mapping the public network IP address into an IP domain identifier, and judging whether the IP domain identifier is the local domain identifier.
Further, still include: the DRA also comprises an associated information module which is used for generating and storing associated information when the user is online, wherein the associated information comprises a user private network IP address, a PCEF identifier, a user identifier and a PCRF identifier.
Further, the DRA further includes a configuration module, configured to store a correspondence between the PCEF identifier and the IP domain identifier, so as to determine the corresponding PCEF identifier according to the IP domain identifier.
The routing agent node can determine the PCRF to which the user belongs according to the user identifier and the APN information in the obtained Rx session message, so that the Rx session message can be sent to the corresponding PCRF to realize session binding.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a flow chart of an embodiment of a routing agent method of the present invention.
Fig. 2 is a flow chart of another embodiment of a routing agent method of the present invention.
Fig. 3 is a flow chart of yet another embodiment of a routing agent method of the present invention.
Fig. 4 is a schematic diagram of an embodiment of a routing agent node of the present invention.
Fig. 5 is a schematic diagram of another embodiment of a routing agent node of the present invention.
Fig. 6 is a schematic diagram of yet another embodiment of a routing agent node of the present invention.
Detailed Description
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
A flow diagram of one embodiment of a routing agent method of the present invention is shown in fig. 1.
In step 101, the DRA acquires an Rx session message.
In step 102, the DRA determines whether the user is a user belonging to the region. If the user belongs to the local area, executing step 103; if the user does not belong to the local area, step 104 is executed.
In step 103, the DRA determines a corresponding PCRF according to the user identifier and the APN in the Rx session message, and routes the Rx session message to the PCRF, completing the flow of the routing agent method of the present invention.
In step 104, the DRA roams the Rx session message to the DRA of the user's home region. After receiving the Rx session message, the DRA in the home area of the user starts to execute from step 101, so as to determine the PCRF which the user belongs to in the home area.
By the method, the DRA can determine the PCRF to which the user belongs according to the acquired user identifier and APN information in the Rx session message, so that the Rx session message can be sent to the corresponding PCRF; particularly, in a multi-APN scene, even if multiple sets of PCRF and PCEF exist in the area, the PCRF search can be correctly realized according to the method so as to realize session binding.
In one embodiment, the user identity and/or APN identity may not be present in the Rx session message. A flow diagram of one embodiment of a routing agent method of the present invention is shown in fig. 2.
In step 201, the DRA acquires an Rx session message.
In step 202, the DRA determines whether the Rx session message includes a user identifier. If the user identifier is included, executing step 203; if the user identification is not included, step 206 is performed.
In step 203, the DRA judges whether the user belongs to the region according to the user identifier. If the user belongs to the local area, executing step 204; if the user does not belong to the local area, step 205 is executed.
In step 204, the DRA determines a corresponding PCRF according to the user identifier and the APN in the Rx session message, and routes the Rx session message to the PCRF, completing the flow of the routing agent method of the present invention.
In step 205, the DRA roams the Rx session message to the DRA of the user's home region. After receiving the Rx session message, the DRA in the home area of the user starts to execute from step 201, so as to determine the PCRF which the user belongs to in the home area.
In step 206, the DRA determines the user home PCRF based on the association information stored by the DRA according to the public network IP address information and the private network IP address information in the Rx session message, and routes the Rx session to the corresponding PCRF.
By the method, the DRA can judge whether the Rx session message comprises the user identification information; when the Rx session message does not include the user identification information, the DRA can determine the PCRF according to the user public network IP address and the user private network IP address, and can route the Rx session message to the corresponding PCRF to realize the binding of the session.
A flow diagram of yet another embodiment of the routing agent method of the present invention is shown in fig. 3.
In step 301, the DRA acquires an Rx session message.
In step 302, the DRA determines whether the Rx session message includes a user identifier. If the user identifier is included, executing step 303; if the user identification is not included, step 306 is executed.
In step 303, the DRA determines whether the user belongs to the region according to the user identifier. If the user belongs to the local area, go to step 304; if the user does not belong to the local area, step 305 is executed.
In step 304, the DRA determines the corresponding PCRF according to the user identifier and the APN in the Rx session message, and routes the Rx session message to the PCRF, completing the flow of the routing agent method of the present invention, without executing other steps in this embodiment.
In step 305, the DRA roams the Rx session message to the DRA in the user's home area, and the DRA does not perform any further steps in this embodiment.
After receiving the Rx session message, the DRA in the home area of the user starts to perform step 301, so as to determine the PCRF which the user belongs to in the home area.
In step 306, the DRA determines the IP domain identifier corresponding to the user, and determines whether the IP domain identifier belongs to the area. If the IP domain identifier does not belong to the local area, executing step 307; if the IP field ID belongs to the local area, go to step 308.
In step 307, the DRA routes the Rx session to the upper level DRA, and the present DRA does not continue to perform other steps in this embodiment.
After receiving the Rx session message, the upper level DRA performs the steps of this embodiment from step 301 until determining the PCRF to which the user belongs.
In step 308, the DRA determines whether the user belongs to the local area, and if the user is determined to belong to the local area, step 309 is executed; if the user does not belong to the local area, step 310 is executed.
In step 309, the DRA determines the PCRF of the user according to the private network IP address information of the user, and further routes the Rx session message to the corresponding PCRF, thereby completing the procedure of this embodiment.
In step 310, the DRA acquires the user identifier and the APN information according to the private network IP address information of the user, fills the user identifier and the APN information into the Rx session message, and forwards the modified Rx session message to the higher-level DRA, which does not execute any other flow of this embodiment. In one embodiment, the padding of the user identity and APN information into the Rx session message may be: and filling the user identification into a Subscription-Id AVP field in the Diameter AAR message, and filling the APN information into a Called-Station-Id AVP field.
After receiving the Rx session message, the upper level DRA starts to execute from step 301 until determining the corresponding PCRF.
By the method, the DRA can realize routing addressing and session binding under the conditions of multiple APNs, multiple PCRFs and multiple PCEF, and the PCRF to which the user belongs can be determined according to the method under the conditions that the Rx session message includes or does not include the user identifier, whether the user is located locally or not and whether the user belongs to locally or not, so as to realize session binding.
In an embodiment, the DRA may map the public network IP address in the Rx session message to an IP domain identifier, and further determine whether the IP domain identifier is a domain identifier of the area. If the IP domain identification is the domain identification of the local area, the public network IP address is the address of the local area, and the user is located in the local area; if the IP domain identifier is not the domain identifier of the region, the user is not located in the region, and the position of the user needs to be judged by the superior DRA.
By the method, the DRA can judge whether the user is located locally according to the IP address of the public network of the user, and further can determine whether the user PCRF is continuously searched by the DRA or is handed to a superior DRA for execution, so that the corresponding PCRF can be searched when the user is in a home location or roaming location state.
In an embodiment, the DRA further stores a corresponding relationship between the PCEF identifier and the IP domain identifier, and the DRA is capable of mapping the public network IP address in the Rx session message to the IP domain identifier, and then determining the PCEF identifier corresponding to the IP domain identifier based on the corresponding relationship between the PCEF identifier and the IP domain identifier.
By the method, when the Rx session message does not comprise the user identifier, the PCEF identifier can be obtained according to the IP address information of the public network of the user, so that the PCRF identifier of the user can be conveniently obtained by matching with the IP address information of the private network of the user.
In an embodiment, when a user is online, the DRA may generate and store user association information, where the association information may include a user private network IP address, a PCEF identifier, a user identifier, and a PCRF identifier in a Gx session.
By the method, the DRA can store the user association information when the user is online, so that after the Rx session message is received, the corresponding PCRF identifier can be searched based on the association information according to the information in the Rx session message as an index, and the session binding is realized.
A schematic diagram of one embodiment of a routing proxy node of the present invention is shown in fig. 4. The message acquiring module 401 may acquire an Rx session message and transmit the Rx session message to the local area user determining module 402. The local area user determining module 402 determines whether the user is a local area user according to the user identification information in the Rx session message; if the user is a local user, the execution module 403 acquires a corresponding PCRF according to the user identifier and the APN, and routes the Rx session message to the corresponding PCRF.
The DRA can determine the PCRF to which the user belongs according to the user identifier and the APN information in the obtained Rx session message, so that the Rx session message can be sent to the corresponding PCRF; particularly, in a multi-APN scene, even if multiple sets of PCRF and PCEF exist in the area, the DRA of the invention can also correctly realize PCRF search so as to realize session binding.
In one embodiment, when the local area user determining module 402 determines that the user is not the local area user, the executing module 403 routes the Rx session message to the upper level DRA. The upper level DRA message obtaining module 401 obtains Rx session message, and the local area user determining module 402 performs the step of determining whether the user is located in the local area according to the public network IP address.
Under the condition that the user is not the local area user, the DRA can route the Rx session message to the upper level DRA for processing, and the corresponding PCRF is ensured to be searched.
A schematic diagram of another embodiment of a routing proxy node of the present invention is shown in fig. 5. The message acquiring module 501 can acquire an Rx session message and transfer the Rx session message to the identifier determining module 502. The identity determination module 502 can determine whether the Rx session message includes a user identity.
If no user identification is included, the execution module 504 is activated. The execution module 504 determines a corresponding PCRF based on the association information stored by the DRA according to the public network IP address and the private network IP address in the Rx session message, and routes the Rx session message to the PCRF.
If the user identifier is included, the local area user determination module 503 is activated. The local area user determining module 503 determines whether the user is a local area user according to the user identifier information in the Rx session message. If the user is a local user, the execution module 504 acquires the corresponding PCRF according to the user identifier and the APN, and routes the Rx session message to the corresponding PCRF. When the local area user determining module 503 determines that the user is not the local area user, the executing module 504 routes the Rx session message to the upper level DRA. The message acquiring module 501 of the upper level DRA acquires the Rx session message, and activates the identifier determining module 502 thereof to execute the operation.
Such DRA can determine whether the Rx session message includes user identification information; when the Rx session message does not include the user identification information, the DRA can determine the PCRF according to the user public network IP address and the user private network IP address, and can route the Rx session message to the corresponding PCRF to realize the binding of the session.
In an embodiment, when the identifier determining module 502 determines that the Rx session message does not include the user identifier, the executing module 504 determines whether the IP domain identifier corresponding to the user public network IP address in the Rx session message is located in the local area. If the IP domain identifier does not belong to the area, the Rx session is routed to the upper level DRA, and after receiving the Rx session message, the message obtaining module 501 of the upper level DRA may activate the identifier determining module 502 to perform the next operation. If the execution module 504 determines that the user IP domain identifier belongs to the local area, it continues to determine whether the user private network IP address in the Rx session message is located in the local area. If the private network IP address is located in the local area, the user belongs to the local area, the PCRF of the user is determined according to the private network IP address information of the user, and the Rx session message is routed to the corresponding PCRF. If the private network IP address is not located in the local area, the user identifier and the APN information are obtained according to the private network IP address information of the user, the Rx session message is filled in the Rx session message, the modified Rx session message is forwarded to the upper-level DRA, the message obtaining module 501 of the upper-level DRA can activate the identifier judging module 502 to carry out the next operation after receiving the Rx session message, and the upper-level DRA can obtain the corresponding PCRF according to the user identifier and the APN.
The DRA can judge the position of the user according to the public network IP address of the user under the condition that the Rx session message does not include the user identifier, determine the attribution of the user according to the private network IP address information, and further determine the PCRF of the attribution of the user so as to realize session binding.
A schematic diagram of yet another embodiment of a routing proxy node of the present invention is shown in fig. 6. The structure and function of the message obtaining module 601, the identification judging module 602, the local area user judging module 603 and the executing module 604 are similar to those in fig. 5. The DRA may further include an association information module 605 configured to generate and store association information when the user is online, where the association information includes a user private network IP address, a PCEF identifier, a user identifier, and a PCRF identifier.
The DRA can store user association information when a user is online, so that after an Rx session message is received, the information in the Rx session message can be used as an index, and a corresponding PCRF identifier can be searched based on the association information, so that session binding is realized.
In an embodiment, the DRA may map the public network IP address in the Rx session message to an IP domain identifier, and further determine whether the IP domain identifier is a domain identifier of the area. If the IP domain identification is the domain identification of the local area, the public network IP address is the address of the local area, and the user is located in the local area; if the IP domain identifier is not the domain identifier of the region, the user is not located in the region, and the position of the user needs to be judged by the superior DRA.
The DRA can judge whether the user is located locally or not according to the IP address of the public network of the user, and further can determine whether the DRA continues to execute the PCRF search of the user or is handed to a higher-level DRA for execution.
In an embodiment, as shown in fig. 6, the DRA further includes a configuration module 606 configured to store a correspondence between the PCEF identifier and the IP domain identifier. The DRA can map the public network IP address in the Rx session message into an IP domain identifier, and then determines the PCEF identifier corresponding to the IP domain identifier based on the corresponding relation between the PCEF identifier and the IP domain identifier.
Thus, the DRA can acquire the PCEF identifier according to the IP address information of the public network of the user under the condition that the Rx session message does not include the user identifier, thereby being convenient for acquiring the PCRF identifier of the user by matching with the IP address information of the private network of the user.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention and not to limit it; although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art will understand that: modifications to the specific embodiments of the invention or equivalent substitutions for parts of the technical features may be made; without departing from the spirit of the present invention, it is intended to cover all aspects of the invention as defined by the appended claims.

Claims (12)

1. A routing agent method, comprising:
the routing agent node DRA acquires an Rx session message;
judging whether the Rx session message comprises a user identifier or not;
if the user identification is included, the DRA judges whether the user is the user in the local area or not according to the user identification in the Rx session message; if the user is the local area user, acquiring a corresponding PCRF according to the user identification and the APN, and routing the Rx session message to the corresponding PCRF;
if not, the DRA determines the PCRF based on the association information stored by the DRA according to the public network IP address and the private network IP address in the Rx session message, and routes the Rx session message to the corresponding PCRF, including:
judging whether the public network IP address is in the local area, if so, judging whether the user belongs to the local area according to the private network IP address;
and if the public network IP address is judged not to be located in the region, routing the Rx session message to a higher level DRA, and executing the step of judging whether the user is located in the region according to the public network IP address by the higher level DRA.
2. The method according to claim 1, wherein if the user is not a local area user, roaming the Rx session message to a home area DRA, so that the home area DRA performs the step of acquiring the corresponding PCRF according to the user identifier and the APN.
3. The method of claim 1, wherein determining the PCRF based on the association information stored by the DRA according to the public network IP address and the private network IP address in the Rx session message further comprises:
if the user is judged to belong to the local area according to the private network IP address, determining the PCRF according to the association information stored by the DRA, and routing the Rx session message to the corresponding PCRF;
and if the user does not belong to the region according to the private network IP address, acquiring a user identifier and an APN according to the association information, filling the user identifier and the APN into an Rx session message, forwarding the Rx session message to a superior DRA, and executing the step of judging whether the Rx session message comprises the user identifier by the superior DRA.
4. The method according to claim 3, wherein the determining whether the public network IP address is located in the local area specifically comprises:
and mapping the public network IP address into an IP domain identifier, and judging whether the IP domain identifier is the domain identifier of the region.
5. The method of claim 1, further comprising: when a user is online, the DRA generates and stores associated information, wherein the associated information comprises a user private network IP address, a PCEF (policy and charging enforcement function) identifier, a user identifier and a PCRF (policy and charging rules function) identifier in a Gx session.
6. The method according to claim 4, wherein the DRA further stores a correspondence between PCEF identifiers and IP domain identifiers, so as to determine the corresponding PCEF identifiers according to the IP domain identifiers.
7. A routing proxy node, comprising:
a message obtaining module, configured to obtain an Rx session message;
an identifier determining module, configured to determine, after the DRA obtains the Rx session message, whether the Rx session message includes a user identifier;
the local area user judging module is used for judging whether the user is the local area user or not according to the user identification in the Rx session message under the condition that the Rx session message comprises the user identification;
an execution module, configured to, when the local area user determination module determines that the user is a local area user, obtain a corresponding PCRF according to the user identifier and the access point name APN, and route the Rx session message to the corresponding PCRF; determining a PCRF based on correlation information stored by DRA according to a public network IP address and a private network IP address in the Rx session message under the condition that the Rx session message does not include a user identifier, and routing the Rx session message to a corresponding PCRF, wherein the method comprises the following steps:
judging whether the public network IP address is in the local area, if so, judging whether the user belongs to the local area according to the private network IP address;
and if the public network IP address is judged not to be located in the region, routing the Rx session message to a higher level DRA, and executing the step of judging whether the user is located in the region according to the public network IP address by the higher level DRA.
8. The node of claim 7,
and under the condition that the user is not the local area user, roaming the Rx session message to the DRA of the home area so that the home area DRA executes the step of acquiring the corresponding PCRF according to the user identifier and the APN.
9. The node of claim 7, wherein the determining the PCRF based on the correlation information stored by the DRA according to the public network IP address and the private network IP address in the Rx session message further comprises:
if the user is judged to belong to the local area according to the private network IP address, determining the PCRF according to the association information stored by the DRA, and routing the Rx session message to the corresponding PCRF;
and if the user does not belong to the region according to the private network IP address, acquiring a user identifier and an APN according to the association information, filling the user identifier and the APN into an Rx session message, forwarding the Rx session message to a superior DRA, and executing the step of judging whether the Rx session message comprises the user identifier by the superior DRA.
10. The node according to claim 9, wherein the determining whether the public network IP address is located in the local area specifically comprises:
and mapping the public network IP address into an IP domain identifier, and judging whether the IP domain identifier is the local domain identifier.
11. The node of claim 7, further comprising: the DRA also comprises an associated information module used for generating and storing associated information when a user is online, wherein the associated information comprises a user private network IP address, a PCEF identifier, a user identifier and a PCRF identifier.
12. The node of claim 10, wherein the DRA further comprises a configuration module configured to store a correspondence between PCEF identities and IP domain identities, so as to determine corresponding PCEF identities according to the IP domain identities.
CN201510827844.8A 2015-11-25 2015-11-25 Routing agent method and node Active CN106803808B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510827844.8A CN106803808B (en) 2015-11-25 2015-11-25 Routing agent method and node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510827844.8A CN106803808B (en) 2015-11-25 2015-11-25 Routing agent method and node

Publications (2)

Publication Number Publication Date
CN106803808A CN106803808A (en) 2017-06-06
CN106803808B true CN106803808B (en) 2020-09-04

Family

ID=58975714

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510827844.8A Active CN106803808B (en) 2015-11-25 2015-11-25 Routing agent method and node

Country Status (1)

Country Link
CN (1) CN106803808B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102958046A (en) * 2011-08-22 2013-03-06 中兴通讯股份有限公司 Method and system for controlling mobile terminal access services and DRA (diameter routing agent)
CN103731812A (en) * 2012-10-15 2014-04-16 中国移动通信集团公司 Session affinity method, device, gateways, service side access device and server
CN104219783A (en) * 2013-06-05 2014-12-17 中国移动通信集团公司 Session redirection method and equipment

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8249551B2 (en) * 2008-06-05 2012-08-21 Bridgewater Systems Corp. Long-term evolution (LTE) policy control and charging rules function (PCRF) selection
WO2012095697A1 (en) * 2011-01-10 2012-07-19 Telefonaktiebolaget L M Ericsson (Publ) Recovery of a system for policy control and charging, said system having a redundancy of policy and charging rules function
CN102300263B (en) * 2011-09-23 2013-11-27 电信科学技术研究院 Policy and charging rules function (PCRF) determination method, device and system
CN103139762A (en) * 2011-11-22 2013-06-05 中兴通讯股份有限公司 Method and system for selecting policy and charging rule function
US9397891B2 (en) * 2014-04-25 2016-07-19 Cellco Partnership Geo-redundant PCRF MRA with MPE allocation via IMSI hashing and IP indexed table
WO2015167377A1 (en) * 2014-04-30 2015-11-05 Telefonaktiebolaget L M Ericsson (Publ) Method and device of a policy control and charging (pcc) system in a communication network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102958046A (en) * 2011-08-22 2013-03-06 中兴通讯股份有限公司 Method and system for controlling mobile terminal access services and DRA (diameter routing agent)
CN103731812A (en) * 2012-10-15 2014-04-16 中国移动通信集团公司 Session affinity method, device, gateways, service side access device and server
CN104219783A (en) * 2013-06-05 2014-12-17 中国移动通信集团公司 Session redirection method and equipment

Also Published As

Publication number Publication date
CN106803808A (en) 2017-06-06

Similar Documents

Publication Publication Date Title
US11272440B2 (en) Network slice selection method and apparatus
US8099377B2 (en) Decision-making method, decision-making system, and policy decision function
JP5108055B2 (en) Communication system, communication method, and gateway
CN104115545B (en) Multiple subscribers are serviced by the access point of software enabling
JP5732550B2 (en) Method, system, and computer-readable medium for enhancing Diameter signaling messages
US8438290B2 (en) Method for selecting a policy and charging rules function entity in the non-roaming scenario
KR20210091221A (en) Selection of Network Slice Identifiers
CN103517264B (en) Network switching method and device
KR102048882B1 (en) Method and system for selecting pcef and pcrf in a wireless communication system
US9021073B2 (en) IP pool name lists
CN107645722B (en) Private network selective access method and system, public network MME, HSS and base station
JP7171729B2 (en) System, mobile communication network component, method for selecting network functions and method for registering network functions
WO2009092304A1 (en) A method and apparatus for selecting the policy and charging rule function entity
CN106792613B (en) Session binding method and system
EP2983442A1 (en) Method and device for implementing proximity communication service
CN102547658B (en) Method and device for transmitting data
CN113645254B (en) Method and device for signaling addressing
CN105681158A (en) Method, device and system for improving IP short message delivery accuracy
CN106507382B (en) Diameter message routing method and routing agent node
CN110430137B (en) Message processing method and device based on S11 interface
CN106803808B (en) Routing agent method and node
CN104918247A (en) Service discovery and authentication method, equipment, terminal and system
CN103379479A (en) Method, system and device for determining of user identification and informing of parameter information
JP2014531159A (en) Processing messages related to multiple potential entities
CN109673007B (en) User information acquisition method and device and computer readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant