CN105207786B - The method and system and route agent's node of Rx sessions and Gx binding sessions - Google Patents
The method and system and route agent's node of Rx sessions and Gx binding sessions Download PDFInfo
- Publication number
- CN105207786B CN105207786B CN201410238656.7A CN201410238656A CN105207786B CN 105207786 B CN105207786 B CN 105207786B CN 201410238656 A CN201410238656 A CN 201410238656A CN 105207786 B CN105207786 B CN 105207786B
- Authority
- CN
- China
- Prior art keywords
- address
- public network
- dra
- nat
- sessions
- 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
Links
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses the method and systems and route agent's node of a kind of Rx sessions and Gx binding sessions, are related to the communications field.The embodiment of the present invention receives the Rx interface message that AF is sent by DRA, the source port that public network IP address and AF are connect with NAT device is carried in Rx interface message, if public network IP address is in this domain, DRA is according to the mapping relations of the public network IP address and NAT device address of configuration, inquiry NAT device corresponding with public network IP address, if in public network IP address no longer this domain, NAT device corresponding with public network IP address is inquired by the DRA in its domain, then private network IP address corresponding with public network IP address and source port is obtained from NAT device, corresponding Gx sessions are found according to private network IP address, realize the binding of Rx sessions and Gx sessions.
Description
Technical field
The present invention relates to the communications field, more particularly to method and system and routing of a kind of Rx sessions with Gx binding sessions
Agent node.
Background technology
With internet, the high speed development of mobile Internet, there is serious shortage in the addresses IPV4, and the development of IPV6
It is relatively also relatively slower.In order to solve the problems, such as Address Run Short in communication network, many commercial cities of runing are disposed in a communication network
NAT (network address translation) equipment is to save address resource.
NAT device is deployed to PCC (policy control and charging) framework and brings a problem, that is, due in Gx sessions
IP address be NAT device before private network IP address, and the IP address in Rx sessions is the public network IP address after NAT device,
Cause Gx sessions that can not be bound with Rx sessions.
Invention content
A technical problem to be solved of the embodiment of the present invention is：Solve the problems, such as Gx sessions and Rx binding sessions.
One side according to the ... of the embodiment of the present invention proposes a kind of method of Rx sessions and Gx binding sessions, including：DRA
(route agent's node) receives the Rx interface message that AF (Application Function) is sent, public network IP is carried in Rx interface message
The source port that location and AF are connect with NAT device；Whether DRA judges public network IP address in this domain；Exist in response to public network IP address
Judging result in this domain, DRA is according to the mapping relations of the public network IP address and NAT device address of configuration, inquiry and public network IP
The corresponding NAT device in address；DRA obtains private network IP address corresponding with public network IP address and source port from NAT device；DRA roots
Corresponding Gx sessions are found according to private network IP address, realize the binding of Rx interface message and Gx sessions.
In one embodiment, this method further includes：In response to the public network IP address not judging result in this domain, DRA
The DRA that NAT inquiry requests are routed to its domain according to public network IP address carries public network IP address and AF in NAT inquiry requests
The source port being connect with NAT device；The DRA in its domain is looked into according to the mapping relations of the public network IP address and NAT device address of configuration
Ask NAT device corresponding with public network IP address.
In one embodiment, DRA obtains private network IP address packet corresponding with public network IP address and source port from NAT device
It includes：The DRA in its domain obtains private network IP address corresponding with public network IP address and source port from NAT device, and sends DRA to.
In one embodiment, before whether DRA judges public network IP address in this domain, further include：DRA judges NAT
Whether support opens, and judges that the source port cell in Rx interface message whether there is, if NAT supports opening and Rx
Source port cell in interface message exists, and starts NAT querying flows.
In one embodiment, this method further includes：DRA deletes the source port in Rx interface message, by Rx interface message
In public network IP address replace with private network IP address, Rx interface message is forwarded according to the destination address of Gx binding sessions.
Another aspect according to the ... of the embodiment of the present invention proposes a kind of route agent's section of Rx sessions and Gx binding sessions
Point, including：Rx message reception modules, the Rx interface message for receiving AF transmissions, in Rx interface message with carrying public network IP
The source port that location and AF are connect with network address translation device；Private network IP address acquisition module, for judging public network IP address
Whether in this domain；In response to judging result of the public network IP address in this domain, according to the public network IP address and NAT device of configuration
The mapping relations of address inquire NAT device corresponding with public network IP address；It is obtained and public network IP address and source from NAT device
The corresponding private network IP address of mouth；Binding session module realizes that Rx connects for finding corresponding Gx sessions according to private network IP address
The binding of mouth message and Gx sessions.
In one embodiment, private network IP address acquisition module is additionally operable in response to public network IP address not in this domain
NAT inquiry requests are routed to the DRA in its domain according to public network IP address by judging result, and public network IP is carried in NAT inquiry requests
The source port that address and AF are connect with NAT device, so as to its domain DRA according to the public network IP address of configuration and NAT device address
Mapping relations, inquire corresponding with public network IP address NAT device.
In one embodiment, private network IP address acquisition module, the DRA for being additionally operable to receive its domain are obtained, simultaneously from NAT device
The private network IP address corresponding with public network IP address and source port of transmission.
In one embodiment, route agent's node further includes：Starting module, for judging whether NAT supports open, and
And judge that the source port cell in Rx interface message whether there is, if NAT supports the source in opening and Rx interface message
Message member exists, and starts NAT querying flows.
In one embodiment, route agent's node further includes：Message transmission module, for deleting in Rx interface message
Public network IP address in Rx interface message is replaced with private network IP address by source port, will according to the destination address of Gx binding sessions
Rx interface message forwards.
Another aspect according to the ... of the embodiment of the present invention proposes a kind of system of Rx sessions and Gx binding sessions, including preceding
Route agent the node DRA and Application Function AF stated；AF is used to send Rx interface message to DRA, in Rx interface message
Carry the source port that public network IP address and AF are connect with network address translation device.
In one embodiment, when public network IP address is not in this domain, system further includes：The DRA in its domain, for receiving
The NAT inquiry requests that DRA is sent, according to the mapping relations of the public network IP address of configuration and NAT device address, inquiry and public network IP
The corresponding NAT device in address obtains private network IP address corresponding with public network IP address and source port from NAT device, and sends to
DRA。
The embodiment of the present invention receives the Rx interface message that AF is sent by DRA, public network IP is carried in Rx interface message
The source port that location and AF are connect with NAT device, if public network IP address is in this domain, DRA is according to the public network IP address of configuration
With the mapping relations of NAT device address, NAT device corresponding with public network IP address is inquired, if public network IP address no longer this domain
In, NAT device corresponding with public network IP address is inquired by the DRA in its domain, then obtain from NAT device and public network IP address and
The corresponding private network IP address of source port finds corresponding Gx sessions according to private network IP address, realizes Rx sessions and Gx sessions
Binding.
By referring to the drawings to the detailed description of exemplary embodiment of the present invention, other feature of the invention and its
Advantage will become apparent.
Description of the drawings
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technology description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
Some embodiments of invention without having to pay creative labor, may be used also for those of ordinary skill in the art
With obtain other attached drawings according to these attached drawings.
Fig. 1 is the enhanced PCC configuration diagrams of the present invention.
Fig. 2 is DRA of the present invention and interaction diagrams of the NAT in the same domain.
Fig. 3 is the DRA of the present invention and NAT not interaction diagrams in same domain.
Fig. 4 is the flow chart of Rx sessions of the present invention and method one embodiment of Gx binding sessions.
Fig. 5 is the flow chart of Rx sessions of the present invention and the method further embodiment of Gx binding sessions.
Fig. 6 is that the present invention illustrates in Home Routed scenes, AF in the Rx sessions of visited place and Gx binding session processes
Figure.
Fig. 7 is that the present invention illustrates in Home Routed scenes, AF in the Rx sessions of ownership place and Gx binding session processes
Figure.
Fig. 8 is that the present invention illustrates in Home Routed scenes, AF in the Rx sessions on third ground and Gx binding session processes
Figure.
Fig. 9 is that the present invention shows in Local Breakout scenes, AF in the Rx sessions of visited place and Gx binding session processes
It is intended to.
Figure 10 is that the present invention shows in Local Breakout scenes, AF in the Rx sessions of ownership place and Gx binding session processes
It is intended to.
Figure 11 is that the present invention shows in Local Breakout scenes, AF in the Rx sessions on third ground and Gx binding session processes
It is intended to.
Figure 12 is the structural schematic diagram of Rx sessions of the present invention and system one embodiment of Gx binding sessions.
Figure 13 is the structural schematic diagram of Rx sessions of the present invention and the system further embodiment of Gx binding sessions.
Figure 14 is the structural schematic diagram of Rx sessions of the present invention and route agent's node one embodiment of Gx binding sessions.
Figure 15 is the structural schematic diagram of Rx sessions of the present invention and route agent's node further embodiment of Gx binding sessions.
Specific implementation mode
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation describes, it is clear that described embodiments are only a part of the embodiments of the present invention, instead of all the embodiments.Below
Description only actually at least one exemplary embodiment is illustrative, is never used as to the present invention and its application or makes
Any restrictions.Based on the embodiments of the present invention, those of ordinary skill in the art are not making creative work premise
Lower obtained every other embodiment, shall fall within the protection scope of the present invention.
Unless specifically stated otherwise, positioned opposite, the digital table of the component and step that otherwise illustrate in these embodiments
It is not limited the scope of the invention up to formula and numerical value.
Simultaneously, it should be appreciated that for ease of description, the size of attached various pieces shown in the drawings is not according to reality
Proportionate relationship draw.
Technology, method and apparatus known to person of ordinary skill in the relevant may be not discussed in detail, but suitable
In the case of, the technology, method and apparatus should be considered as authorizing part of specification.
In shown here and discussion all examples, any occurrence should be construed as merely illustrative, without
It is as limitation.Therefore, the other examples of exemplary embodiment can have different values.
It should be noted that：Similar label and letter indicate similar terms in following attached drawing, therefore, once a certain Xiang Yi
It is defined, then it need not be further discussed in subsequent attached drawing in a attached drawing.
Fig. 1 is the enhanced PCC configuration diagrams of the present invention.As shown in Figure 1, ("Policy and Charging Rules Function is real by PCRF
Body) be PCC core, be responsible for strategic decision-making and charging regulation formulation, PCRF provide business data flow detection, gate, QOS
The functions such as (service quality) control, event report processing, dosage monitoring, binding and the charging regulation based on data flow, PCRF
The rule formulated is handed down to PCEF (strategy and charging execution function entity) and executes.PCEF is usually located in gateway, such as PGW
In (packet data network gateway), GGSN (Gateway GPRS Support Node), PDSN (packet data serving node), executed in data surface
The strategy and charging regulation of PCRF, the business datum flow filter in the rule that PCEF is issued by PCRF carry out business data flow
Detection, and then corresponding strategy is executed to these business data flows, according to the charging policy that PCRF is sent, PCEF executes corresponding
Service data flow charge operates, and charging can be online charging, can also be offline charging.Interface between PCEF and PCRF is
Gx interfaces.The function of BBERF (bearing binding and event reporting functions entity) includes that bearing binding, uplink bearing binding are tested
Card and time report.BBERF is present in SGW (gateway) or HSGW (HPRD in PMIP (proxy-mobile IP) scene
(high speed packet data) gateway), in the equipment such as ePDG (packet data gateway of evolution), when there are BBERF, PCRF exists
While issuing PCC rules to PCEF, QOS rules are also issued to BBERF.AF (Application Function) provides service application
Application message is passed to PCRF with aid decision making by access point, AF, and AF is interacted by Rx interface with PCRF.(route agent saves DRA
Point) it is responsible for destination address translation and conversion.The present invention enhances the function of DRA, AF.
DRA functions enhance：
1, the mapping relations of NAT transformed IP address section (public network IP address) and NAT device address are configured on DRA；
2, DRA according to NAT support whether to open and Rx interface on the source port cell of message (be set as NATed-
Source-Port) whether there is, to determine whether starting NAT querying flows；
3, DRA can be with public network IP address (being set as Frame-IP-Address) for condition, and query configuration information learns that NAT is set
Standby address；
4, DRA can construct NAT inquiry requests (being set as NQR), and the Frame-IP- in Rx interface message is carried in NQR
Input parameter of the two parameters of Address and NATed-Source-Port as inquiry private IP address；
5, when NAT device and DRA be not or not same domain, DRA can route to NQR correctly according to Frame-IP-Address
Domain in, that is, NQR is sent to the DRA in its domain according to Frame-IP-Address；
6, after the private IP address of DRA acquisitions user, the Frame-IP-Address in Rx message can be substituted for the private
There is IP address.
AF functions enhance：
The AVP (attribute value to) that NATed-Source-Port is extended in Rx interface message, connect for carrying UE with AF
Source port (that is, source port that NAT device is connect with AF).AVP is a kind of and relevant information of Diameter information
Packaging method.
Newly-increased interactive interface between DRA and NAT is inquired for NAT.According to DRA and NAT whether in same domain, DRA
Interaction flow between NAT is specifically divided into following two situations.
For DRA and NAT in the same domain, interaction flow is shown in Figure 2：
Step S201 sends out NAT inquiry requests (NQR) after DRA obtains the device address of NAT to NAT device, to obtain
Station address (private network IP address) before NAT conversions, carried in NQR the transformed addresses NAT (public network IP address) and AF and
The source port of NAT device connection；
Step S202 after NAT device receives NQR, is inquired according to the source port that public network IP address and AF are connect with NAT device
Address (private network IP address) of the user before NAT conversions returns to the NAT comprising private network IP address and success code and looks into if finding
Response (NQA) is ask, if can not find out, returns to the NQA for including error code.
For DRA and NAT not in same domain, interaction flow is shown in Figure 3：
Not in the same domain, it cannot directly acquire NAT device address by step S301, DRA1 and NAT, thus in NQR
It does not carry destination host address (Destination-Host), but the transformed addresses NAT (public network IP can be carried in NQR
Location) and the source ports that are connect with NAT device of AF, that is, by the Frame-IP- in public network IP address and source port filling NQR
Address and NATed-Source-Port.NQR is forwarded to DRA2 by DRA1 according to Frame-IP-Address.
Step S302, DRA2 inquire NAT device address according to Frame-IP-Address, if DRA2 has inquired NAT and set
Destination address Destination-Host is then inserted into standby address in NQR, is worth for NAT device address, and NQR is forwarded to NAT
Equipment；If DRA2 inquiries are less than NAT device address, because DRA2 and Frame-IP-Address belongs to the same domain,
DRA2 can return to the mistake of Diameter-Unable-to-Deliver (can not transmit).
Step S303 after NAT device receives NQR, is inquired according to Frame-IP-Address and NATed-Source-Port
Address mapping table obtains the IP address (private network IP address) before NAT conversions, and returns to private network IP address to DRA2 by NQA.
NQA is returned to DRA1 by step S304, DRA2.
Diameter (diameter) agreements or other agreements, primary message head may be used in interface protocol between DRA and NAT
It is defined as follows：
Wherein, Session-Id indicates that session identification, Vendor-Specific-Application-Id indicate application mark
Knowing, Origin-Host indicates that source host, Origin-Realm indicate that source domain, Destination-Realm indicate purpose domain,
Destination-Host indicates that destination host, Frame-IP-Address indicate the transformed addresses NAT (public network IP address),
NATed-Source-Port indicates the source port that AF is connect with NAT device.Result-Code indicates object code.
Fig. 4 is the flow chart of Rx sessions of the present invention and method one embodiment of Gx binding sessions.As shown in figure 4, this reality
The method for applying example includes the following steps：
Step S401, DRA receive the Rx interface message that AF is sent, carried in Rx interface message public network IP address and AF with
The source port (referred to as " source port ") of NAT device connection；
Whether step S402, DRA judge public network IP address in this domain；In response to judgement of the public network IP address in this domain
As a result, execute step S403~S404, in response to the public network IP address not judging result in this domain, execute step S405~
S407；
Step S403, DRA are according to the mapping relations of the public network IP address and NAT device address of configuration, inquiry and public network IP
The corresponding NAT device in address；
Step S404, DRA obtain private network IP address corresponding with public network IP address and source port from NAT device；Then it holds
Row step S408；
NAT inquiry requests are routed to the DRA in its domain according to public network IP address by step S405, DRA, in NAT inquiry requests
The middle source port for carrying public network IP address and AF and being connect with NAT device；
Step S406, the DRA in its domain according to the mapping relations of the public network IP address and NAT device address of configuration, inquiry with
The corresponding NAT device of public network IP address；
The DRA of step S407, its domain obtain private network IP address corresponding with public network IP address and source port from NAT device,
And send DRA to；Then step S408 is executed；
Step S408, DRA find corresponding Gx sessions according to private network IP address, realize Rx interface message and Gx sessions
Binding.
Above example implements the bindings of Rx sessions and Gx sessions, and the binding method be applicable not only to it is PCRF single
Scape, and it is suitable for more PCRF scenes.
During Rx sessions and Gx binding sessions, the judgement step for whether starting NAT querying flows can be further increased
Suddenly, specifically, DRA judges whether NAT supports open, and judge that the source port cell in Rx interface message whether there is, such as
Fruit NAT supports to open and the source port cell in Rx interface message exists, then starts NAT querying flows.
In Rx sessions and during Gx binding sessions, obtain public network IP address and the corresponding private network IP address of source port it
Afterwards, can the correspondence of the public network IP address of acquisition and source port and private network IP address be further added to dynamic mapping table
In, to be quickly obtained public network IP address and the corresponding private network IP address of source port subsequently through dynamic mapping table.
During Rx sessions and Gx binding sessions, in the binding found Gx sessions, realize Rx interface message and Gx sessions
Later, DRA deletes the source port in Rx interface message, and the public network IP address in Rx interface message is replaced with private network IP address,
If Gx binding sessions destination address, forwards Rx interface message according to the destination address of Gx binding sessions, if Gx
Destination address is not bound in session, and the forwarding of Rx interface message is carried out according to the domains IP.
Fig. 5 is the flow chart of Rx sessions of the present invention and the method further embodiment of Gx binding sessions.As shown in figure 5, this
The method of embodiment includes the following steps：
Step S501, DRA receive the Rx interface message that AF is sent, carried in Rx interface message public network IP address and AF with
The source port (referred to as " source port ") of NAT device connection；
Step S502, DRA judge whether NAT supports open, and whether judge the source port cell in Rx interface message
In the presence of, if it is judged that being to be, step S503 is executed, otherwise, execution step S513；
Whether step S503, DRA obtain public network IP address and the corresponding private network IP address of source port by dynamic mapping table；
If obtained, step S512 is executed, if there is no, executes step S504；
Whether step S504, DRA judge public network IP address in this domain；In response to judgement of the public network IP address in this domain
As a result, execute step S505~S506, in response to the public network IP address not judging result in this domain, execute step S507~
S509；
Step S505, DRA are according to the mapping relations of the public network IP address and NAT device address of configuration, inquiry and public network IP
The corresponding NAT device in address；
Step S506, DRA obtain private network IP address corresponding with public network IP address and source port from NAT device；Then it holds
Row step S510；
NAT inquiry requests are routed to the DRA in its domain according to public network IP address by step S507, DRA, in NAT inquiry requests
The middle source port for carrying public network IP address and AF and being connect with NAT device；
Step S508, the DRA in its domain according to the mapping relations of the public network IP address and NAT device address of configuration, inquiry with
The corresponding NAT device of public network IP address；
The DRA of step S509, its domain obtain private network IP address corresponding with public network IP address and source port from NAT device,
And send DRA to；Then step S510 is executed；
Step S510, DRA find corresponding Gx sessions according to private network IP address, realize Rx interface message and Gx sessions
Binding；
Source port in step S511, DRA deletion Rx interface message, the public network IP address in Rx interface message is replaced with
Private network IP address, if Gx binding sessions destination address, according to the destination address of Gx binding sessions forwards Rx interface message
It goes out, if destination address is not bound in Gx sessions, the forwarding of Rx interface message is carried out according to the domains IP.By the public network IP of acquisition
The correspondence of location and source port and private network IP address is added in dynamic mapping table.Flow terminates.
Source port in step S512, DRA deletion Rx interface message, the public network IP address in Rx interface message is replaced with
Private network IP address, if Gx binding sessions destination address, according to the destination address of Gx binding sessions forwards Rx interface message
It goes out, if destination address is not bound in Gx sessions, the forwarding of Rx interface message is carried out according to the domains IP.Flow terminates.
Step S513 normally forwards message according to existing 3GPP flows, i.e., if Gx binding sessions destination address, according to
The destination address of Gx binding sessions forwards Rx interface message, if destination address is not bound in Gx sessions, according to the domains IP
Carry out the forwarding of Rx interface message.Flow terminates.
Below for the different location residing for different scene and AF, the binding side of Rx sessions and Gx sessions is illustrated
Case.Wherein, Gx sessions are also referred to as IP-CAN (IP-Connectivity Access Network, IP agreement access network) meeting
Words.HDRA (local DRA), VDRA (visited place DRA), HPCRF (local PCRF), VPCRF (visited place PCRF).
Embodiment one：Home Routed (ownership routing) scene, AF is in visited place, referring to Fig. 6, Rx sessions and Gx sessions
Binding procedure is as follows：
Step S601, user's Gx session establishments, HDRA record GX sessions (GX sessions can be identified with private network IP address) and
Binding relationship between HPCRF；
Step S602, AF initiate Rx session requests, and NATed-Source-Port is inserted into AAR (authorization requests), is used for
The source port address that NAT device is connect with AF is carried, Frame-IP-Address is for carrying user after NAT conversions
Public network IP address, and AAR is sent to VDRA；
Step S603, VDRA has found to carry NATed-Source-Port in AAR, and NAT supports switch to open, therefore sends out
Play NAT inquiry requests (NQR) because VDRA and NAT will not be configured not in same domain, therefore in VDRA the NAT device address with
NQR message is forwarded to by the mapping relations of the transformed user's public network IP address of NAT, VDRA according to user's public network IP address
HDRA；
Step S604, HDRA inquires NAT device mapping table, will after finding NAT device address according to public network IP address
NQR message is forwarded to NAT device；
Step S605, NAT device according in NQR message public network IP address and source port number with obtaining user private network IP
Location, and construct NAT inquiry responses (NQA) and user private network IP address is returned into HDRA；
NQA is back to VDRA by step S606, HDRA；
Step S607 is taken the Frame-IP-Address in AAR message after VDRA obtains the private network IP address of user
The public network IP address of band replaces with private network IP address, deletes NATed-Source-Port, and VDRA searches user's public network IP address pair
The HDRA answered, and AAR is forwarded to HDRA；
Step S608, HDRA search the binding relationship for the GX sessions established before according to the private network IP address of user, and will
AAR is forwarded to correct HPCRF, and HPCRF finds the Gx sessions established before according to user private network IP address；
Step S609, HPCRF return to AAA (authorization response) to HDRA；
Step S610, HDRA return to AAA to VDRA；
Step S611, VDRA return to AAA to AF.
Embodiment two：Home Routed scenes, AF is in ownership place, and referring to Fig. 7, Rx sessions and Gx binding sessions process are such as
Under：
Step S701, user's Gx session establishments, HDRA record GX sessions (GX sessions can be identified with private network IP address) and
Binding relationship between HPCRF；
Step S702, AF initiate Rx session requests, and NATed-Source-Port is inserted into AAR (authorization requests), is used for
The source port address that NAT device is connect with AF is carried, Frame-IP-Address is for carrying user after NAT conversions
Public network IP address, and AAR is sent to HDRA；
Step S703, HDRA has found to carry NATed-Source-Port in AAR, and NAT supports switch to open, therefore sends out
NAT inquiry requests are played, because HDRA and NAT be in same domain, therefore the NAT device address can be configured in HDRA and be converted with NAT
After HDRA finds NAT device address according to public network IP address, NQR message is turned for the mapping relations of user's public network IP address afterwards
It is sent to NAT device；
Step S704, NAT device according in NQR message public network IP address and port numbers obtain user private network IP address,
And it constructs NQA and user private network IP address is returned into HDRA；
Step S705 is taken the Frame-IP-Address in AAR message after HDRA obtains the private network IP address of user
The public network IP address of band replaces with private network IP address, deletes NATed-Source-Port, is searched according to the private network IP address of user
The binding relationship for the GX sessions established before, and AAR is forwarded to correct HPCRF, HPCRF is looked for according to user private network IP address
To the Gx sessions established before；
Step S706, HPCRF return to AAA to HDRA；
Step S707, HDRA return to AAA to AF.
Embodiment three：Home Routed scenes, in third, referring to Fig. 8, Rx sessions and Gx binding sessions process are such as by AF
Under：
Step S801, user's Gx session establishments, HDRA record GX sessions (GX sessions can be identified with private network IP address) and
Binding relationship between HPCRF；
Step S802, AF initiate Rx session requests, and NATed-Source-Port is inserted into AAR (authorization requests), is used for
The source port address that NAT device is connect with AF is carried, Frame-IP-Address is for carrying user after NAT conversions
Public network IP address, and by AAR with being sent to third DRA；
Step S803, third DRA find to carry NATed-Source-Port in AAR, and NAT supports switch to open, because
This initiates NAT inquiry requests because third DRA and NAT not in same domain, therefore third will not configure the NAT in DRA and set
The mapping relations of standby address and the transformed user's public network IP address of NAT, third DRA according to user's public network IP address by NQR
Message is forwarded to HDRA；
Step S804, HDRA inquires NAT device mapping table, will after finding NAT device address according to public network IP address
NQR message is forwarded to NAT device；
Step S805, NAT device according in NQR message public network IP address and port numbers obtain user private network IP address,
And it constructs NQA and user private network IP address is returned into HDRA；
Step S806, HDRA are by NQA with being back to third DRA；
Step S807, third DRA obtain user private network IP address after, by the Frame-IP- in AAR message
Public network IP address entrained by Address replaces with private network IP address, deletes NATed-Source-Port, and AAR is forwarded to
HDRA；
Step S808, HDRA search the binding relationship for the GX sessions established before according to the private network IP address of user, and will
AAR is forwarded to correct HPCRF, and HPCRF finds the Gx sessions established before according to user private network IP address；
Step S809, HPCRF return to AAA to HDRA；
Step S810, HDRA return to AAA to third DRA；
Step S811, third DRA return AAA to AF.
Example IV：Local Breakout (local break-out) scene, AF is in visited place, referring to Fig. 9, Rx sessions and Gx meetings
It is as follows to talk about binding procedure：
Step S901, user's Gx session establishments, VDRA record GX sessions (GX sessions can be identified with private network IP address) and
Binding relationship between VPCRF；
Step S902, AF initiate Rx session requests, and NATed-Source-Port is inserted into AAR (authorization requests), is used for
The source port address that NAT device is connect with AF is carried, Frame-IP-Address is for carrying user after NAT conversions
Public network IP address, and AAR is sent to VDRA；
Step S903, VDRA has found to carry NATed-Source-Port in AAR, and NAT supports switch to open, therefore sends out
NAT inquiry requests are played, because VDRA and NAT be in same domain, therefore the NAT device address can be configured in VDRA and be converted with NAT
After VDRA finds NAT device address according to public network IP address, NQR message is turned for the mapping relations of user's public network IP address afterwards
It is sent to NAT device；
Step S904, NAT device according in NQR message public network IP address and port numbers obtain user private network IP address,
And it constructs NQA and user private network IP address is returned into VDRA；
Step S905 is taken the Frame-IP-Address in AAR message after VDRA obtains the private network IP address of user
The public network IP address of band replaces with private network IP address, deletes NATed-Source-Port, is searched according to the private network IP address of user
The binding relationship for the GX sessions established before, and AAR is forwarded to correct VPCRF, VPCRF is looked for according to user private network IP address
To the Gx sessions established before；
AAR message is sent to HPCRF by step S906, VPCRF；
Step S907, HPCRF return to AAA message to VPCRF；
Step S908, VPCRF return to AAA message to VDRA；
Step S909, VDRA return to AAA message to AF.
Embodiment five：Local Breakout scenes, AF is in ownership place, referring to Figure 10, Rx sessions and Gx binding session mistakes
Journey is as follows：
Step S1001, user's GX session establishments, VDRA record GX sessions (GX sessions can be identified with private network IP address) and
Binding relationship between VPCRF, HDRA record the binding relationship between the corresponding HPCRF of S9 sessions；
Wherein, strategy of the S9 sessions under roaming scence between HPCRF and VPCRF is sent, S9 sessions and Gx sessions
There are binding relationships.Rx message can pass to HPCRF by S9 sessions from VPCRF.
Step S1002, AF initiate Rx session requests, and NATed-Source-Port is inserted into AAR, for carry NAT with
The source port of AF connections, Frame-IP-Address are used to carry public network IP address of the user after NAT conversions, and will
AAR is sent to HDRA；
Step S1003, HDRA has found to carry NATed-Source-Port in AAR, and NAT supports switch to open, therefore sends out
NAT inquiry requests are played, because HDRA and NAT will not configure the NAT device address not in same domain, therefore in HDRA and turn with NAT
NQR message is forwarded to VDRA by the mapping relations of user's public network IP address after changing, HDRA according to user's public network IP address；
Step S1004, VDRA inquiry NAT device mapping table, NAT device address is found according to user's public network IP address
Afterwards, NQR message is forwarded to NAT device；
Step S1005, NAT device according in NQR message public network IP address and port numbers obtain user private network IP address,
And it constructs NQA and user private network IP address is returned into VDRA；
NQA is back to HDRA by step S1006, VDRA；
Step S1007, after HDRA obtains the private network IP address of user, by the Frame-IP-Address institutes in AAR message
The public network IP address of carrying replaces with private network IP address, deletes NATed-Source-Port, and according to the private network IP address of user
The binding relationship and AAR for searching the S9 sessions established before are forwarded to correct HPCRF, and HPCRF is according to user private network IP address
Find the S9 sessions established before；
Step S1008, HPCRF return to AAA to HDRA；
Step S1009, HDRA return to AAA to AF.
Embodiment six：Local Breakout scenes, AF in third, referring to Figure 11, Rx sessions and Gx binding session mistakes
Journey is as follows：
Step S1101, user's GX session establishments, VDRA record GX sessions (GX sessions can be identified with private network IP address) and
Binding relationship between VPCRF, HDRA record the binding relationship between S9 sessions and HPCRF；
Step S1102, AF initiate Rx session requests, and NATed-Source-Port is inserted into AAR, for carry NAT with
The source port address of AF connections, Frame-IP-Address are used to carry public network IP address of the user after NAT conversions, and
By AAR with being sent to third DRA；
Step S1103, third DRA find to carry NATed-Source-Port in AAR, and NAT supports switch to open,
Therefore NAT inquiry requests are initiated because third DRA and NAT not in same domain, therefore third will not configure the NAT in DRA
The mapping relations of device address and the transformed user's public network IP address of NAT, third DRA according to user's public network IP address will
NQR message is forwarded to VDRA；
The static allocation list of step S1104, VDRA inquiry NAT device mapping relations, finds according to user's public network IP address
Behind NAT device address, NQR message is forwarded to NAT device；
Step S1105, NAT device according in NQR message public network IP address and port numbers obtain user private network IP address,
And it constructs NQA and user private network IP address is returned into VDRA；
Step S1106, VDRA are by NQA with being back to third DRA；
Step S1107, third DRA obtain user private network IP address after, by the Frame-IP- in AAR message
Public network IP address entrained by Address replaces with private network IP address, deletes NATed-Source-Port, and AAR is forwarded to
VDRA；
Step S1108, VDRA search the binding relationship for the GX sessions established before according to the private network IP address of user, and
AAR is forwarded to correct VPCRF, and VPCRF finds the session established before according to user private network IP address；
Step S1109, VPCRF send AAR to HPCRF；
Step S1110, HPCRF return to AAA to VPCRF；
Step S1111, VPCRF return to AAA to VDRA；
Step S1112, VDRA return to AAA to third DRA；
Step S1113, third DRA return AAA to AF.
Figure 12 is the structural schematic diagram of Rx sessions of the present invention and system one embodiment of Gx binding sessions.
Figure 13 is the structural schematic diagram of Rx sessions of the present invention and the system further embodiment of Gx binding sessions.
As shown in Figure 12 and Figure 13, which includes DRA1201 and AF1202.In DRA configured with public network IP address with
The mapping relations of NAT device address.
AF1202 is used to send Rx interface message to DRA1201, carried in Rx interface message public network IP address and AF with
The source port of network address translation device connection.
When public network IP address is in this domain, DRA1201 is used for the public network IP address according to configuration and NAT device address
Mapping relations inquire NAT device corresponding with public network IP address, are obtained from NAT device corresponding with public network IP address and source port
Private network IP address, corresponding Gx sessions are found according to private network IP address, realize the binding of Rx interface message and Gx sessions.
When public network IP address is not in this domain, as shown in figure 13, which further includes：The DRA1303 in its domain, in its domain
DRA in be configured with public network IP address and NAT device address mapping relations；DRA1201 is used to send NAT to the DRA in its domain
Inquiry request carries the source port that public network IP address and AF are connect with NAT device in NAT inquiry requests；The DRA1303 in its domain
The NAT inquiry requests that DRA1201 is sent are received, according to the mapping relations of the public network IP address of configuration and NAT device address, inquiry
NAT device corresponding with public network IP address obtains private network IP address corresponding with public network IP address and source port from NAT device,
And send DRA1201 to.
Figure 14 is the structural schematic diagram of Rx sessions of the present invention and route agent's node one embodiment of Gx binding sessions.
As shown in figure 14, route agent's node of the present embodiment includes：
Rx message reception modules 1401, the Rx interface message sent for receiving Application Function AF, disappear in Rx interface
The source port that public network IP address and AF are connect with network address translation device is carried in breath；
Private network IP address acquisition module 1402, for judging public network IP address whether in this domain；In response to public network IP
Judging result of the location in this domain, according to the mapping relations of the public network IP address of configuration and NAT device address, inquiry and public network IP
The corresponding NAT device in address；Private network IP address corresponding with public network IP address and source port is obtained from NAT device；
Binding session module 1403 realizes Rx interface message for finding corresponding Gx sessions according to private network IP address
With the binding of Gx sessions.
In one embodiment, private network IP address acquisition module 1402 is additionally operable in response to public network IP address not in this domain
In judging result, NAT inquiry requests are routed to the route agent node DRA in its domain according to public network IP address, NAT inquire
The source port that public network IP address and AF are connect with NAT device is carried in request, so as to its domain DRA according to the public network IP of configuration
The mapping relations of location and NAT device address inquire NAT device corresponding with public network IP address.
In one embodiment, private network IP address acquisition module 1402, the DRA for being additionally operable to receive its domain are obtained from NAT device
The private network IP address corresponding with public network IP address and source port for taking and transmitting.
Figure 15 is the structural schematic diagram of Rx sessions of the present invention and route agent's node further embodiment of Gx binding sessions.
As shown in figure 15, route agent's node of the present embodiment further includes：
Starting module 1504 for judging whether NAT supports open, and judges the source port cell in Rx interface message
It whether there is, if NAT supports to open and the source port cell in Rx interface message exists, start NAT querying flows.
As shown in figure 15, route agent's node of the present embodiment further includes：
Message transmission module 1505, for deleting the source port in Rx interface message, by the public network IP in Rx interface message
Address replaces with private network IP address, is forwarded Rx interface message according to the destination address of Gx binding sessions.
Above example implements the bindings of Rx sessions and Gx sessions, and the binding method be applicable not only to it is PCRF single
Scape, and it is suitable for more PCRF scenes.
One of ordinary skill in the art will appreciate that realizing that all or part of step of above-described embodiment can pass through hardware
It completes, relevant hardware can also be instructed to complete by program, the program can be stored in a kind of computer-readable
In storage medium, storage medium mentioned above can be read-only memory, disk or CD etc..
The foregoing is merely presently preferred embodiments of the present invention, is not intended to limit the invention, it is all the present invention spirit and
Within principle, any modification, equivalent replacement, improvement and so on should all be included in the protection scope of the present invention.
Claims (12)
1. a kind of method of Rx sessions and Gx binding sessions, including：
Route agent node DRA receives the Rx interface message that Application Function AF is sent, and the Rx interface message carries public network
The source port that IP address and AF are connect with network address translation device；
Whether DRA judges the public network IP address in this domain；
In response to judging result of the public network IP address in this domain, DRA is according to the public network IP address of configuration and NAT device
The mapping relations of location inquire NAT device corresponding with the public network IP address；
DRA obtains private network IP address corresponding with the public network IP address and the source port from the NAT device；
DRA finds corresponding Gx sessions according to the private network IP address, realizes the binding of Rx interface message and Gx sessions.
2. according to the method described in claim 1, it is characterized in that, further including：
In response to the public network IP address, the judging result in this domain, DRA do not ask NAT inquiries according to the public network IP address
The DRA for routing to its domain is sought, the source that the public network IP address and the AF are connect with NAT device is carried in NAT inquiry requests
Port；
The DRA in its domain is inquired and the public network IP address according to the mapping relations of the public network IP address and NAT device address of configuration
Corresponding NAT device.
3. according to the method described in claim 2, it is characterized in that, DRA is obtained and the public network IP address from the NAT device
Private network IP address corresponding with the source port includes：
The DRA in its domain obtains private network IP address corresponding with the public network IP address and the source port from the NAT device, and
Send the DRA to.
4. according to the method described in claim 1, it is characterized in that, judging the public network IP address whether in this domain in DRA
Before, further include：
DRA judges whether NAT supports open, and judges that the source port cell in the Rx interface message whether there is, if
NAT supports to open and the source port cell in the Rx interface message exists, and starts NAT querying flows.
5. according to the method described in claim 1, it is characterized in that, further including：
DRA deletes the source port in the Rx interface message, and the public network IP address in Rx interface message is replaced with the private network
IP address forwards the Rx interface message according to the destination address of Gx binding sessions.
6. route agent's node of a kind of Rx sessions and Gx binding sessions, including：
Rx message reception modules, the Rx interface message sent for receiving Application Function AF, the Rx interface message carry
The source port that public network IP address and AF are connect with network address translation device；
Private network IP address acquisition module, for judging the public network IP address whether in this domain；In response to the public network IP
Judging result of the location in this domain, according to the mapping relations of the public network IP address of configuration and NAT device address, inquiry and the public affairs
The corresponding NAT device of net IP address；Private network corresponding with the public network IP address and the source port is obtained from the NAT device
IP address；
Binding session module realizes Rx interface message and Gx for finding corresponding Gx sessions according to the private network IP address
The binding of session.
7. route agent's node according to claim 6, which is characterized in that private network IP address acquisition module is additionally operable to ring
The not judging result in this domain of public network IP address described in Ying Yu, routes to NAT inquiry requests according to the public network IP address
The route agent node DRA in its domain, carries the public network IP address in NAT inquiry requests and the AF is connect with NAT device
Source port, so as to its domain DRA according to the mapping relations of the public network IP address and NAT device address of configuration, inquiry with it is described
The corresponding NAT device of public network IP address.
8. route agent's node according to claim 7, which is characterized in that private network IP address acquisition module is additionally operable to connect
Receive the private network IP corresponding with the public network IP address and the source port that the DRA in its domain is obtained and transmitted from the NAT device
Address.
9. route agent's node according to claim 6, which is characterized in that further include：
Whether starting module for judging whether NAT supports open, and judges the source port cell in the Rx interface message
In the presence of if NAT supports to open and the source port cell in the Rx interface message exists, startup NAT querying flows.
10. route agent's node according to claim 6, which is characterized in that further include：
Message transmission module, for deleting the source port in the Rx interface message, by the public network IP address in Rx interface message
The private network IP address is replaced with, is forwarded the Rx interface message according to the destination address of Gx binding sessions.
11. a kind of system of Rx sessions and Gx binding sessions, including claim 6-10 any one of them route agent node
DRA and Application Function AF；
The AF is used to send Rx interface message to the DRA, carried in the Rx interface message public network IP address and AF with
The source port of network address translation device connection.
12. system according to claim 11, which is characterized in that described when the public network IP address is not in this domain
System further includes：
The DRA in its domain, the NAT inquiry requests sent for receiving the DRA, according to the public network IP address and NAT device of configuration
The mapping relations of address inquire NAT device corresponding with the public network IP address, are obtained and the public network from the NAT device
IP address and the corresponding private network IP address of the source port, and send the DRA to.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410238656.7A CN105207786B (en) | 2014-05-30 | 2014-05-30 | The method and system and route agent's node of Rx sessions and Gx binding sessions |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410238656.7A CN105207786B (en) | 2014-05-30 | 2014-05-30 | The method and system and route agent's node of Rx sessions and Gx binding sessions |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105207786A CN105207786A (en) | 2015-12-30 |
| CN105207786B true CN105207786B (en) | 2018-10-02 |
Family
ID=54955242
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410238656.7A Active CN105207786B (en) | 2014-05-30 | 2014-05-30 | The method and system and route agent's node of Rx sessions and Gx binding sessions |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105207786B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106998542B (en) * | 2016-01-22 | 2020-08-07 | 中国电信股份有限公司 | Method and system for configuring PCC policy |
| US20200099725A1 (en) * | 2017-06-08 | 2020-03-26 | Telefonaktiebolaget Lm Ericsson (Publ) | A Method and Device for Triggering Service Logic Execution Recording for a Call between a Calling User Equipment, UE, and a Called UE in a Telecommunication Network |
| CN111343291B (en) * | 2018-12-19 | 2022-04-26 | 中国电信股份有限公司 | Service acceleration processing method and device, QoS platform and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102137367A (en) * | 2010-01-26 | 2011-07-27 | 中兴通讯股份有限公司 | Enhanced policy and charging control method and system and PCC (Policy Charge Control) system |
| WO2012103931A1 (en) * | 2011-02-01 | 2012-08-09 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for pcc support for scenarios with nat/napt in the pdn-gw |
| CN103685582A (en) * | 2012-09-05 | 2014-03-26 | 中国移动通信集团公司 | PCRF addressing method, as well as system, terminal, server, PA equipment and DRA equipment corresponding to same |
| CN103731812A (en) * | 2012-10-15 | 2014-04-16 | 中国移动通信集团公司 | Session affinity method, device, gateways, service side access device and server |
-
2014
- 2014-05-30 CN CN201410238656.7A patent/CN105207786B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102137367A (en) * | 2010-01-26 | 2011-07-27 | 中兴通讯股份有限公司 | Enhanced policy and charging control method and system and PCC (Policy Charge Control) system |
| WO2012103931A1 (en) * | 2011-02-01 | 2012-08-09 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for pcc support for scenarios with nat/napt in the pdn-gw |
| CN103329588A (en) * | 2011-02-01 | 2013-09-25 | 瑞典爱立信有限公司 | Method and apparatus for PCC support for scenarios with NAT/NAPT in the PDN-GW |
| CN103685582A (en) * | 2012-09-05 | 2014-03-26 | 中国移动通信集团公司 | PCRF addressing method, as well as system, terminal, server, PA equipment and DRA equipment corresponding to same |
| CN103731812A (en) * | 2012-10-15 | 2014-04-16 | 中国移动通信集团公司 | Session affinity method, device, gateways, service side access device and server |
Non-Patent Citations (2)
| Title |
|---|
| "DRA技术和组网应用介绍";聂衡等;《2012全国无线及移动通信学术大会论文集（下）》;20120901;全文 * |
| "Session binding in visited access with AF located in HPLMN";Huawei;《3GPP》;20140523;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105207786A (en) | 2015-12-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8745244B2 (en) | Method and system for implementing policy and charging control in multi-PDN scenario | |
| EP3179753B1 (en) | Online charging method and device for cross-plmn roaming data service | |
| EP2242205A1 (en) | A method for selecting a policy and charging rules function entity in the non-roaming scenario | |
| US8516545B2 (en) | Method and system for session modification | |
| US8799440B2 (en) | Policy and charging control method and system for multi-PDN connections of single APN | |
| CN102238512B (en) | The application of policies method of machine type communication MTC and tactful and charging execution entity | |
| US20120124220A1 (en) | Method for Implementing Policy and Charging Control in a Roaming Scene | |
| EP2217018A1 (en) | Decision making method and system, and policy decision making unit | |
| CN103209401A (en) | Strategy control method and system in convergence network | |
| EP2472918B1 (en) | Method, apparatus and system for transmitting a bearer control mode in roaming scenarios | |
| CN105101176B (en) | A kind of binding session methods, devices and systems under roaming scence | |
| CN109361526A (en) | Method for routing, PCRF/PCF and the DRA of policy control | |
| US20130013794A1 (en) | Method and apparatus for creating ip-can session | |
| CN101198171A (en) | Routing method for strategy charging control information in roaming scene | |
| CN105207786B (en) | The method and system and route agent's node of Rx sessions and Gx binding sessions | |
| CN102238507A (en) | Method and system for determining policy and charging rules function | |
| EP2509256A1 (en) | Flow charging method, apparatus and system | |
| CN108574667A (en) | A kind of control method and device of Business Stream | |
| WO2015000514A1 (en) | Selection of a policy and charging control unit by a diameter routing unit | |
| CN104581670B (en) | Using connection control method and Application Function device | |
| WO2011091682A1 (en) | Method and system for enhanced policy and charging control, policy and charging control (pcc) system | |
| CN102655634B (en) | The method and system that strategy and charging control function entity function are consulted | |
| CN103906223B (en) | Information synchronization method and system based on double DRA in domain | |
| US20160227394A1 (en) | Hiding Diameter Network Topology | |
| CN102791042B (en) | Method and system for establishing S9 subsession and policy and charging rules function (PCRF) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |