Patent Application
20080070573
The present invention relates generally to IMS/MMD architecture, and more specifically to mitigation techniques for trombone routing encountered in IMS/MMD networks.
An IMS/MMD (IP Multimedia Subsystem/Multimedia Domain) network or architecture primarily comprises several signaling entities such as proxy-call session control function (P-CSCF), interrogating-CSCF (I-CSCF), serving-CSCF (S-CSCF), and home subscriber service (HSS) which is usually a database or other repository for user or subscriber information such as authorization data, including information related to services provided to a user. Roaming service and mobility are supported by a combination of Session Initiation Protocol (SIP) components such as the signaling entities, P-CSCF, S-CSCF, I-CSCF, and mobile IP components or nodes, such as home agent (HA) and foreign agent (FA). IMS/MMD architecture mandates that there should be security association (SA) between the mobile and P-CSCF. Secure Internet Protocol (IPSec) is one way of providing SA for signaling and media traffic.
In IMS, authentication of a user, or user's equipment (UE), can be achieved using authentication and key agreement (AKA). Authentication is achieved between the UE, generally a mobile, and its home network even though the SIP messaging is transported over the Serving, or visiting, network. This allows home network-based control of access to IMS resources, while the visited network controls bearer resources over the packet data servicing nodes (PDSN). SIP Registration and Response messages are used to transport the IMS/AKA protocol payloads. These messages are sent from the UE to the S-CSCF and vice versa. The S-CSCF queries the HSS to obtain security related parameters for the UE. IMS AKA uses a challenge response mechanism to authenticate the UE to the Home Network. The UE uses a long term key to compute a response to a challenge sent by the S-CSCF via the P-CSCF. The P-CSCF plays no role in challenge generation aside from acting as a forwarding element.
In an IMS/MMD network, the signaling and media travel to their destination, such as to S-CSCF, via the HA which usually resides on the home network. This long route or path from a Mobile Node or correspondent node (CN) to a destination through the home network is a phenomenon called trombone routing. Because trombone routing impacts both registration and call setup methods, trombone routing hinders efficiency during a mobile's boot-strapping (registration, re-registration, call setup) in the visited network and during its movement from one subnet to another. This causes both an initial call setup delay, and a handoff delay when the mobile moves from one visited subnet to another. In addition, during a mobile's movement between subnets, AKA is performed as part of registration; hence, a faster registration will help establish an expedited SA, thus reducing the handoff delay.
Hence, as shown in
MN→FA1→HA→P-CSCF→S-CSCF
and the path of a SIP registration Reply message is:
S-CSCF→P-CSCF→HA→FA1→MN.
Similarly, the path of a SIP INVITE, as shown in
CN→S-CSCF→P-CSCF→HA→FA1→MN
and the path of a SIP OK is:
MN→FA1→HA→P-CSCF→S-CSCF→CN
Since there is no FA in the visited network in MIPv6, the mobile obtains the new CoA using stateless auto-configuration. When a mobile registers with S-CSCF in the home network, the mobile provides its home address as its contact address. Since there is a reverse tunneling between the mobile and HA, both the call setup and registration (re-registration) process are subjected to trombone routing.
As shown in
MN→HA→P-CSCF→S-CSCF
and the path of a SIP registration Reply message is:
S-CSCF→P-CSCF→HA→MN.
Similarly, the path of a SIP INVITE, as shown in
CN→S-CSCF→P-CSCF→HA→MN
and the path of a SIP OK is:
MN→HA→P-CSCF→S-CSCF→CN
Thus, just like the case of MIPv4, the trombone routing will affect the performance. As is evident from both of these cases, trombone routing is undesirable.
Similarly, there is an inherent trombone routing problem with data or media, because the reverse tunneling is used by default.
In this handoff process, there are two issues. The first is slow handoff. As shown schematically in
The second issue is inefficient routing. Because of the reverse mode of tunneling between the FA and HA, the SIP messages between the Mobile Node and P-CSCF take the trombone routing path. Hence, as shown in
MN→FA→Gateway in Network B→Gateway in Home Network→HA→Gateway in Home Network→Gateway in Network B→P-CSCF
A SIP message from the P-CSCF to the Mobile Node takes the reverse path.
Thus, trombone routing causes inefficiencies and delays in both registration and handoff.
The following abbreviations are used throughout.
The present invention advantageously provides systems and methods for solving the trombone routing issues within an IMS/MMD network. These methods avoid trombone routing and increase the efficiency of signaling and overall performance of an IMS/MMD network.
In one embodiment, a system and method for mitigating trombone routing in a MIPv4 FA-CoA network is presented in which the SIP registration message is attached to an MIP control message. The MIP control message, along with the attached SIP registration message, is transmitted to an application-specific relaying node that performs both MIP registration and SIP registration. In particular, the application-specific relaying node sends the SIP registration to the S-CSCF while simulaneously sending the MIP registration to the HA.
In another embodiment, a system and method for mitigating trombone routing in a MIPv4 FA-CoA network using both tunneling and selective reverse tunneling is presented. In this approach, a bi-directional tunnel is created between FA and HA, an IP-IP tunnel is created from a mobile node to FA, and another tunnel is created from P-CSCF to FA. Packets in encapsulated delivery style are transmitted using the bi-directional tunnel from FA to HA and vice versa. Packets in direct delivery style are transmitted from mobile node to FA or from P-CSCF to FA.
In another embodiment, a system and method for mitigating trombone routing using the SIP-base mobility protocol is presented. In this approach, when a mobile node bootstraps, it obtains its IP address either from a stateful DHCP server or from stateless auto-configuration, because there are no MIP entities such as HA or FA. Hence, the registration message and reply use the standard routing path, avoiding trombone routing.
In another embodiment, a system and method for mitigating trombone routing in a MIPv6 network by using CoA in the mobile's registration message instead of the home address as the contact address is presented.
In another embodiment, a system and method for mitigating trombone routing in a MIPv4 FA-CoA network having HA and S-CSCF on the same machine is presented. The SIP registration message is attached to an MIP control message. The MIP control message, along with the attached SIP registration message, is transmitted to the HA, and HA communicates with S-CSCF.
In another embodiment, a system and method for mitigating trombone routing in a MIPv4 network having home agents, known as dynamic home agents, close the the mobile node's visiting networks is presented. Placing the home agents close to foreign agents minimizes the routing path.
In another embodiment, a system and method for mitigating trombone routing in a MIPv4 and a MIPv6 network, a policy agent is added at the foreign agent. The policy agent decides whether to send the signaling via tunneling to the HA or directly to P-CSCF.
The invention is further described in the detailed description that follows, by reference to the noted drawings by way of non-limiting illustrative embodiments of the invention, in which like reference numerals represent similar parts throughout the drawings. As should be understood, however, the invention is not limited to the precise arrangements and instrumentalities shown. In the drawings:
a illustrates a Trombone Routing in MIPv4 FA-COA during SIP Registration;
b illustrates a Trombone Routing in MIPv4 FA-COA during SIP Invite;
a illustrates a Trombone Routing in MIPv6 during SIP Registration;
b illustrates a Trombone Routing in MIPv6 during SIP Registration and Call Setup;
a illustrates a schematic of the Selective Reverse Tunneling and CoA approach for MIPv6 during SIP Registration;
b illustrates a schematic of the Selective Reverse Tunneling and CoA approach for MIPv6 during SIP Call Setup;
In order to avoid the trombone routing and speed up the handoff, several solutions are presented that help mitigate the trombone routing effect. These can broadly be divided into the following:
a) Piggy-backing SIP registration over MIP (Split at FA);
b) Selective Reverse Tunneling and Tunneling between FA and P-CSCF;
c) The SIP-based mobility protocol;
d) Use of CoA during SIP registration and call up in MIPv6;
e) Piggy-backing SIP registration when HA and S-CSCF Co-exist;
f) Using Dynamic Home Agents in MIPv4 FA-CoA; and
g) Interceptor-Caching Approach.
Each of these solutions will be described below.
A. Piggy-Backing SIP Registration Over MIP
In this approach, MIP and SIP signaling on control plane are integrated, enabling SIP messages to be delivered as part of MIP control messages, bypassing the FA-HA tunnel. The transport of data is not affected. DHCP operation is dropped because the Mobile Node does not need the IP address of the P-CSCF. Instead, FA needs to know the IP address of the corresponding P-CSCF in advance, and, since FA and P-CSCF are stationary, the IP address of P-CSCF can be preconfigured in the FA. Accordingly, MIP and SIP registrations can be independent and their operations can perform simultaneously in parallel. Specifically, SIP registration does not need to wait until the routing paths for the SIP messages are completely established through the MIP.
Operational Procedure of Piggy-Backing
As shown in
In this operating procedure, SIP messages from/to the Mobile Node to/from P-CSCF traverse according to the routes set by the regular IP routing not by MIP. Hence, no FA-HA tunnel is used for forwarding the messages.
As shown in
MN→Gateway in Network B→P-CSCF
The path of a MIP registration message 26, also shown in
HA→Gateway in Home Network→Gateway in Network B→FA→MN
This approach requires modifying both FA and the MIP client from their original configurations, for example, FA must be able to parse SIP messages. In addition, a filtering mechanism must be installed at the router. However, this approach offers a reduction in the number of signaling messages, and also enables two protocols, SIP and MIP, to be combined into one.
B. Selective Reverse Tunneling and Tunneling Between FA and P-CSCF
Another approach avoids trombone routing by using selective reverse tunneling and an encapsulation technique between the FA 14 and P-CSCF 28.
As discussed above, the root cause of the trombone routing problem is the use of reverse tunneling at the FA 14. The Internet Engineering Task Force (IEFT) protocol specifies Encapsulated Delivery style of packets between the Mobile Node 10 and FA 14, wherein the Mobile Node 10 sets up a tunnel 36 to the FA 14. The primary objective of this tunnel is to allow broadcast packets from the Mobile Node to be sent to their home network via reverse tunneling. In this approach, the IP header fields for packets received via the MN-FA tunnel 36 at the FA 14 are as follows:
To minimize trombone routing problems, a means to leverage the Encapsulated Delivery style to perform Selective Reverse Tunneling is presented. This is intended to support packet delivery to local resources and can be used to optimize delivery to the P-CSCF in the visited network. In this case, the Mobile Node can request the FA to perform Selective Reverse tunneling as follows:
Selective Reverse Tunneling with Encapsulated Delivery style of packets solves one part of the trombone routing problem by optimizing the route from the Mobile Node to the P-CSCF. However, packets from the P-CSCF to the Mobile Node will still be routed via the HA. The inefficiency and/or delay caused by this routing can be alleviated by establishing an IP-IP tunnel 40 between the P-CSCF 28 and the FA 14 for all packets destined for the Mobile Node 10 from the P-CSCF 28. Using this approach, the IP header fields for packets received at the FA from the P-CSCF are as follows:
The encapsulated packets received at the FA via the P-CSCF—FA tunnel 40 will be de-capsulated at the FA and forwarded to the MN. The de-capsulation is performed in a manner identical to that in which encapsulated packets received at the FA via the HA-FA tunnel are processed.
The use of Selective Reverse Tunneling requires the following enhancements to the system architecture.
This approach is somewhat complex because of the additional tunnels and the overhead they require. Like the piggy-backing approach, a filtering mechanism is needed at the router. This approach makes use of standard system features and does not necessitate any changes to the MIP protocol.
C. The SIP-Based Mobility Protocol
A third approach to avoid trombone routing is to use the SIP-based mobility protocol.
In SIP-based mobility, the Mobile Node 10 does not use an MIP entity or mobile IP component for providing mobility binding. Thus, there is no HA or FA, nor any equivalent therefore. When the Mobile Node bootstraps, i.e. boots up, in a visited network 42, Mobile Node must re-register and, if any session parameters have changed, Mobile Node must also re-INVITE. When the bootstrapping occurs, Mobile Node 10 obtains its IP address either from a stateful DHCP server, or by means of stateless auto-configuration. While obtaining its IP address, Mobile Node receives additional server configuration information, including the address of P-CSCF 28, from the DHCP server (not shown), typically using DHCP INFORM.
As Mobile Node 10 sends a registration message to S-CSCF 32, it sends the new CoA as the new contact address and the address of P-CSCF in the network's subnet. Thus, at any point in time, HSS knows the new contact address of the mobile and its corresponding P-CSCF address. Since there is no HA or MIP, the registration message and reply follow the standard routing path, and neither are subjected to trombone routing.
When a caller generates a new call or INVITE to the Mobile Node, the call is routed to S-CSCF using the Mobile Node's Universal Resource Identifier (URI). When the S-CSCF gets this new call, S-CSCF consults the registration database, and routes the call to the P-CSCF responsible for that Mobile Node. Since the contact address of the Mobile Node is still the new CoA obtained in the new network, P-CSCF looks up the contact address and forwards the call to the mobile using standard routing process. Thus trombone routing is avoided for both the call setup and the registration process. Using this procedure, delay during re-registration procedure is lessened, reducing the handoff delay during a Mobile Node's movement from one subnet to another.
This approach supports only SIP-based applications such as VoIP, streaming, and chat, and, at present, is not yet standardized. However, no protocols, such as MIP or SIP, need to be changed to use this approach, and standard SIP signaling is used.
D. Using CoA During SIP Registration and Call Up in MIPv6
Next, a method for avoiding trombone routing by using CoA instead of the home address as the contact address in the Mobile Node's registration message is presented.
While it is mandatory that the media between CN 38 and Mobile Node 10 must travel via the HA 30, having the signaling traverse through HA 30 may not be necessary. Hence, registration with CoA as the contact address in S-CSCF 32 could alleviate some of the trombone routing problems that are often observed in typical MIPv6 networks.
The operation of this approach is as follows. While in a visited network, a Mobile Node sends a request to register, and receives a registration address that can be used as the Mobile Node's CoA, instead of HA as CoA. This CoA is stored in S-CSCF. Hence, when a call is placed to this Mobile Node, S-CSCF finds this mobile node using the stored CoA, and the request does not need to be transmitted to the HA to obtain a CoA for this Mobile Node. Hence, trombone routing is avoided in call setup.
a) illustrates the path of a SIP registration message in MIPv6 to be:
MN→P-CSCF→S-CSCF
and the path of a SIP registration Reply message is:
S-CSCF→P-CSCF→MN.
Similarly, the path of a SIP INVITE, as shown in
CN→S-CSCF→P-CSCF→MN
and the path of a SIP OK is:
MN→P-CSCF→S-CSCF→CN
This approach is limited to MIPv6 in which CoA is used, as opposed to MIPv4 which requires FA and CoA. Standard system features can be used and no protocol changes are necessary for implementation of this approach.
E. Piggy-Backing SIP Registration when HA and S-CSCF Co-Exist
This method borrows some of the concepts from the approach of Piggy-backing SIP registration over MIP, discussed above. In this situation, HA 30 and S-CSCF 32 co-exist on the same machine, and HA 30 has a binding cache. SIP registration URI and P-CSCF address is sent as part of the MIP update. As with the piggy-backing method discussed above, SIP registration information is attached to the MIP message, and all the SIP related registration information is sent as part of MIP binding update. However, the MIP/SIP message does not get split at FA 14 as with the prior piggy-backing approach. Instead, HA 30 passes the SIP related messages to the logical entity S-CSCF 32 that resides on the machine with HA 30. Trombone routing is avoided by using Inter Process Communication instead of passing signals over the long distance.
Operation of this approach is as follows. The SIP registration URI and P-CSCF address is attached to or bound with the MIP registration message. This MIP message is sent via FA to HA which passes the SIP registration information using Inter Process Communication.
This approach requires that both HA and S-CSCF co-exist on the same machine, and the technique offers reduction of signaling and parallelization of processes.
F. Using Dynamic Home Agents in MIPv4 FA-CoA
As discussed above, the root cause of the trombone routing problem is that, without MIPv4 route optimization, every packet needs to traverse through the HA 30. Accordingly, another approach to mitigating the problem of such additional routing can be found by introducing Home Agents close to Mobile Node's visiting networks. These HAs are commonly known as Dynamic Home Agents (DHA) 44, or Mobility Agents (MA) 44. Dynamic home agent assignments are supported by the MIPv4 protocol. By placing Home Agents 30 close to Foreign Agents 14, one can minimize the routing path to a great extent.
MN→FA1→MA→P-CSCF→S-CSCF
and the path of a SIP registration Reply message is:
S-CSCF→P-CSCF→MA→FA1→MN.
Similarly, the path of a SIP INVITE, as shown in
CN→FA1→MA→P-CSCF→S-CSCF→MN
and the path of a SIP OK is:
MN→S-CSCF→P-CSCF→MA→FA1→CN
It is important to note that it is not necessary to deploy MA 44 in every subnet. Depending upon the topology and size of the visiting network 42, multiple MAs can be deployed. However, one MA 44 can handle multiple FAs 14 since it will be usually placed one level higher than subnet level. Several mobility optimization protocols published in the literature, such as Regional Registration, IDM, use the same concept of Dynamic Home Agent. In the sections below, DHA assignment procedures, registration procedure with the old HA, functionalities of MA, packet handling procedures at MA, and dynamic DNS update are described.
Dynamic Home Agent Assignment Procedures
For DHA assignment, FA in the visiting network must include the ‘D’ flag in the agent advertisement message. The ‘D’ bit occupies the first reserved bit after the other flag bits specified in RFC 3220. FA must also include its Network Access Identifier (NAI) in the agent advertisement message. By comparing the advertising FA's NAI with its own NAI, Mobile Node can determine whether or not it is in its home domain.
The signaling procedures and message exchanges for DHA assignment are shown in
Hence, the signaling message sequence is:
HHR→AMR→HAR→HAA→AMA→HHA.
In one embodiment, the HHR message can be defined as the Registration Request message in RFC 2002, but with the following changes:
The Mobile Node must include its NAI or fully qualified domain name (FQDN) in the extension for authentication purpose. The Mobile Node must set ‘S’ bit in its HHR message if it requires simultaneous HA bindings.
On the other hand, if Mobile Node obtains a temporary address from either DHCP or point to point protocol (PPP) before the HA assignment and wants to use this temporary address as its new home address, Mobile Node must set the home address field in the HHR message to be this dynamically allocated temporary address. When FA sends the AMR message to the AAA server, the Mobile-Node-Home-Address-Requested flag in the MIP-Feature-Vector AVP must be set to zero to indicate that no further home address needs to be assigned to the Mobile Node.
Registration Procedure with Old HA
For seamless handover, Mobile Node must send a registration request message to the old HA. The registration is sent directly to the old HA with the fields as specified below:
Home Address: the old Home Address
HA Address: the old HA Address
CoA: the new Home Address (e.g., MA Address)
Since the CoA of the old home address is set to the new home address, all the packets destined to the old home address will be redirected to the new home address of the Mobile Node by the old address after successful registration. The MA will then intercept all packets destined to the Mobile Node and forward them to the current location of the Mobile Node.
Functionalities of Mobility Agent
As mentioned earlier, Mobility Agent (MA) is a home agent that is dynamically assigned and has similar functionalities to an HA. For example, MA accepts the home registration request from the Mobile Node with the old HA. MA also has some behaviors like FA. For example, after receiving the home registration request, MA relays the request to the old HA. However, MA does not broadcast any FA advertisement and also does not provide any CoA address to the Mobile Nodes. Typically, MA will be placed one level higher than FA.
Packet Handling Procedures at MA
The MA should maintain two user lists. One user list is for normal HA function and the other is for seamless HA handover. For seamless handover, MA keeps a binding list that has <MN_Old_Home_Addr, MN_New_Home_Addr> information. For seamless session, MA will receive packets that are encapsulated by the old HA. For encapsulated packets, MA compares the inner destination address of the encapsulated packet with MA's binding list and, if there is a match, MA determines that it has received a packet whose inner destination address is the old home address. Then MA can de-capsulate the encapsulated packet or datagram, and tunnel it to Mobile Node's current location, that is, re-capsulating the datagram with the current CoA of the Mobile Node. For un-encapsulated packets destined to new home address of Mobile Node, MA should function like a normal HA of the Mobile Node.
In case of security association, MA needs to maintain two SAs: i) one is with the Mobile Node (a.k.a. MA-MN) employing the MN-HA registration key, and ii) another one is old HA (a.k.a. MA-OHA) employing the FA-HA registration key. During subsequent moves, for example, when Mobile Node changes the FA but does not change the MA, Mobile Node should send the registration request to the MA with Mobile Node's new CoA. When MA receives such registration request, MA should verify the previous home address in its HA binding list and respond with the registration reply accordingly.
Dynamic DNS Update
Mobile Node should perform a secure dynamic DNS update with its Authoritative Domain name Server (ADS) to update Mobile Node's name bindings after it gets a new home address. An alternative approach could be that a DHCP server can update the DNS if Mobile Node uses the new home address allocated by the DHCP server. By setting the ‘S’ bit in the DHCP_REQUEST, Mobile Node can delegate the DNS update to the DHCP server. In many cases where security is a concern for Mobile Node updating the DNS, delegating the DNS update may be a better approach.
G. Interceptor-Caching Approach
Yet another approach to trombone routing mitigation involves minimal changes to the FA and the mobile. Assuming reverse tunneling is mandatory for this approach, a policy agent or interceptor 50 at respective FA 14 is added. This policy agent 50 will snoop the incoming traffic and, based on the port number, the policy agent 50 will decide whether to send the traffic to the encapsulation agent or route it directly to P-CSCF 28. For example, if SIP signaling is usually carried over port 5060, then the policy agent 50 will have the ability to capture the packets, inspect each one, and selectively send these packets either to the encapsulating agent for tunneling it to HA 30 or send these packets directly to P-CSCF 28. Thus, any traffic other than SIP traffic will be sent back to HA 30 via reverse tunneling. This may include the media traffic as well. Hence, SIP related signaling such as REGISTER and INVITE messages will also traverse to P-CSCF 28 without being tunneled via HA 30, avoiding trombone routing. However, media traffic is a separate issue and needs to be addressed accordingly.
By virtue of reverse tunneling, any traffic destined to the Mobile Node 10 goes to HA 30 and gets tunneled to FA 14 before being delivered to P-CSCF 28. In this case, response messages for SIP REGISTER and SIP INVITE that are destined to Mobile Node 10 via P-CSCF 28 will also need to traverse to HA 30 before being intercepted by FA 14. As discussed above, this situation also adds an extra traversal between P-CSCF 28 and HA 30. In order to alleviate this problem, a caching functionality 52 at P-CSCF is introduced to map Mobile Node's HA 30 with the FA 14, and any message with a certain port number (e.g., 5060) that is destined to Mobile Node's HA 30 will be routed to FA 14 instead. The caching functionality at FA (not shown) and the dynamic routing ability will help route the packets of certain types destined to Mobile Node 10 via FA 14 instead of sending it to HA 30, as it does normally.
While the present invention has been described in particular embodiments, it should be appreciated that the present invention should not be construed as limited by such embodiments, but rather construed according to the below claims.
The present invention claims the benefit of U.S. provisional patent application 60/841,784 filed Aug. 31, 2006, and of U.S. provisional patent application 60/844,955 filed Sep. 15, 2006, the entire contents and disclosures of which are incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60841784 | Aug 2006 | US | |
| 60844955 | Sep 2006 | US |
