Method and system for binding rx session to gx session and routing proxy node
A proxy node and routing technology, applied in the field of communication, can solve problems such as the inability to bind Gx sessions and Rx sessions
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
Embodiment 1
[0091] Embodiment 1: Home Routed (home route) scenario, AF is in the visited place, see Figure 6 , the binding process between Rx session and Gx session is as follows:
[0092] Step S601, the user Gx session is set up, HDRA records the binding relationship between the GX session (the GX session can be identified with a private network IP address) and the HPCRF;
[0093] Step S602, AF initiates an Rx session request, and inserts NATed-Source-Port in AAR (Authorization Request), which is used to carry the source port address of the connection between the NAT device and AF, and Frame-IP-Address is used to carry the user's IP address after NAT conversion Public IP address, and send AAR to VDRA;
[0094] Step S603, VDRA finds that the AAR carries NATed-Source-Port, and the NAT support switch is turned on, so it initiates a NAT query request (NQR), because VDRA and NAT are not in the same domain, so the NAT device address and NAT translation will not be configured in VDRA Accordi...
Embodiment 2
[0103] Embodiment 2: Home Routed scenario, AF is at home, see Figure 7 , the binding process between Rx session and Gx session is as follows:
[0104] Step S701, the user Gx session is set up, and HDRA records the binding relationship between the GX session (the GX session can be identified with a private network IP address) and the HPCRF;
[0105] Step S702, AF initiates an Rx session request, and inserts NATed-Source-Port in AAR (Authorization Request), which is used to carry the source port address of the connection between the NAT device and AF, and Frame-IP-Address is used to carry the user's IP address after NAT conversion Public IP address, and send AAR to HDRA;
[0106] Step S703, HDRA finds that AAR carries NATed-Source-Port, and the NAT support switch is turned on, so it initiates a NAT query request, because HDRA and NAT are in the same domain, so the NAT device address and NAT-translated user will be configured in HDRA The mapping relationship of the public netw...
Embodiment 3
[0111] Embodiment 3: Home Routed scene, AF is in the third place, see Figure 8 , the binding process between Rx session and Gx session is as follows:
[0112] Step S801, the user Gx session is set up, and HDRA records the binding relationship between the GX session (the GX session can be identified with a private network IP address) and the HPCRF;
[0113] Step S802, AF initiates an Rx session request, and inserts NATed-Source-Port in AAR (Authorization Request), which is used to carry the source port address of the connection between the NAT device and AF, and Frame-IP-Address is used to carry the user's IP address after NAT conversion Public network IP address, and send the AAR to the third DRA;
[0114] Step S803, the third DRA finds that the AAR carries NATed-Source-Port, and the NAT support switch is turned on, so it initiates a NAT query request, because the third DRA and NAT are not in the same domain, so the third DRA will not configure this The mapping relationship...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 


