Abstract:
Systems, methods, media, and means for hiding network topology are provided. In some embodiments, methods for hiding network topology are provided, the methods including: receiving a message including topology information from a sender; removing at least part of the topology information; associating the removed topology information with an identifier; saving the topology information; sending the message to a receiver; receiving a response from the receiver; retrieving the removed topology information based on the identifier; inserting the removed topology information into the response; and sending the response to the sender.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Patent Application No. 60/873,493, filed Dec. 7, 2006, which is hereby incorporated by reference herein in its entirety. 
    
    
     TECHNICAL FIELD 
     The disclosed subject matter relates to systems, methods, media, and means hiding network topology. 
     BACKGROUND 
     Digital devices often exchange messages to communicate with each other. These messages can contain not only the information meant to be communicated, but also other information such as routing information. In some cases, network topology information can be determined by examining, for example, routing information exchanged between digital devices. For example, when sending a message, a sender may insert routing information into the message and send the message to a receiver on a path that travels through various other devices. Some of these devices may add further routing information, such as their network addresses, to the routing information associated with the message. The receiver of the message can include the routing information in its response so that the response can be correctly routed back to the sender. However, network providers may wish to keep this routing information away from, for example, attackers, other networks, network subscribers, or any entity that does require access to the information. 
     One reason to keep network topology information private is that attackers can use this information to identify parts of a network for attack. For example, an attacker masquerading as a legitimate user may examine the headers of a packet it receives from a network to determine the address of a critical component of that network. The attacker may then directly target the critical component with an attack, such as, for example, a denial-of-service (DoS) attack. A network provider may also want to keep network topology information private for reasons other than attack avoidance. For example, an IP address read from a packet header may reveal that a network provider has contracted to use the equipment of another entity (e.g., a competitor, a sub contractor, etc.). However, the network provider may have preferred to keep this information confidential for business reasons. 
     One method that can be used to protect network routing information in packets is encryption. For example, a network component that sends a packet to a mobile device can encrypt topology information that is needed by the network for routing responses from mobile devices, but is not directly needed by the mobile devices. A mobile device can insert the encrypted topology information into its response to the network component. The network can then decrypt the encrypted topology information and use it as necessary. However, mere encryption of the header may still leave the network vulnerable. For example, topology information may be inadvertently or maliciously removed such that the packet lacks proper routing information. Alternatively, an encrypted header may be altered so that a response cannot be routed or is routed improperly. It is also possible that an attacker may be able to decrypt an encrypted header and thus access the header and its now unprotected topology information. 
     SUMMARY 
     Systems, methods, media, and means for hiding network topology are provided. In some embodiments, methods for hiding network topology are provided, the methods including: receiving a message including topology information from a sender; removing at least part of the topology information; associating the removed topology information with an identifier; saving the topology information; sending the message to a receiver; receiving a response from the receiver; retrieving the removed topology information based on the identifier; inserting the removed topology information into the response; and sending the response to the sender. 
     In some embodiments, computer-readable media storing computer-executable instructions that, when executed by a processor, cause the processor to perform methods for hiding network topology are provided, the methods including: receiving a message including topology information from a sender; removing at least part of the topology information; associating the removed topology information with an identifier; saving the topology information; sending the message to a receiver; receiving a response from the receiver; retrieving the removed topology information based on the identifier; inserting the removed topology information into the response; and sending the response to the sender. 
     In some embodiments, a intermediate apparatus in a network, including: a memory; an interface; and a processor in communication with the memory and the interface is provided, wherein the processor: receives a message including topology information from the interface; removes at least part of the topology information; associates the removed topology information with an identifier; saves the topology information in the memory; sends the message through the interface; receives a response from the interface; retrieves the removed topology information from the memory based on the identifier; inserts the removed topology information into the response; and sends the response to the through the interface. 
     In some embodiments, a wireless communication system is provided, including: means for receiving a message including topology information from a sender; means for removing at least part of the topology information; means for associating the removed topology information with an identifier; means for saving the topology information; means for sending the message to a receiver; means for receiving a response from the receiver; means for retrieving the removed topology information based on the identifier; means for inserting the removed topology information into the response; and means for sending the response to the sender. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a simplified illustration of an IP Multimedia Subsystem (IMS) which can be used in accordance with some embodiments of the disclosed subject matter. 
         FIG. 2  is a simplified illustration of a Multimedia Domain (MMD) system which can be used in accordance with some embodiments of the disclosed subject matter. 
         FIG. 3  illustrates a control plane architecture for an IMS/MMD solution that can be used in accordance with some embodiments of the disclosed subject matter. 
         FIG. 4  illustrates a method for performing topology hiding in accordance with some embodiments of the disclosed subject matter. 
         FIG. 5  also illustrates a method for performing topology hiding in accordance with some embodiments of the disclosed subject matter. 
     
    
    
     DETAILED DESCRIPTION 
     Systems and methods for inhibiting access to network topology information are disclosed. Using some embodiments of the disclosed subject matter, an intermediate can remove topology information from an outgoing message and store the removed headers in, for example, a database, a memory, and/or a cache. When a response to the message is received at the intermediate, the topology information can be located and inserted into the response and the response can be forwarded to the sender of the message. Removal and reinsertion of topology information can be controlled by, for example, network policy settings. Some embodiments can provide removal and reinsertion of header information in some cases and encryption in others. This can allow, for example, a network operator to control who can address certain parts of a network and can allow different address realms to be used on an internal network and an external network. 
     Various embodiments of the disclosed subject matter can be used with various network types, protocols, standards, and/or topologies. For example,  FIG. 1  illustrates an IP Multimedia Subsystem (IMS)  100 , which is a network architecture that can provide users with mobile and fixed multimedia services implemented as, for example, functions. A function can be implemented on a dedicated node, spread over multiple nodes, or can be implemented on the same node as other functions and/or applications. For example, these functions can be implemented on an ST16 Intelligent Mobile Gateway available from Starent Networks, Corp. 
     Some functions can be grouped into logical units. For example, a Call Session Control Function (CSCF) includes three functions: a Proxy-CSCF (P-CSCF)  101 , an Interrogating CSCF (I-CSCF)  102 , and a Serving CSCF (S-CSCF)  103 . A CSCF can manage much of the signaling that occurs in an IP IMS core. CSCF functions can be embodied in various forms and can be used with various network topologies and/or standards. For example, a CSCF can be use in both the Global System for Mobile Communications (GSM) standard and the Code Division Multiple Access (CDMA) 2000 standard. The 3rd Generation Partnership Project (3GPP) is responsible for IMS which works with GSM systems. The 3rd Generation Partnership Project 2 (3GPP2) is responsible for Multimedia Domain (MMD) which is used with CDMA systems and is based on the 3GPP IMS concept. 
       FIG. 1  also includes a Home Subscriber Server (HSS)  104 , a Subscriber Location Function (SLF)  105 , User Equipment (UE)  106 , Breakout Gateway Control Function (BGCF)  107 , Media Gateway Control Function (MGCF)  108 , Media Gateway (MGW)  109 , Public Switched Telephone Network (PSTN)  110 , Multimedia Resource Controller (MRFC)  111 , Multimedia Resource Function Processor (MRFP)  112 . The HSS  104  is a master user database that supports the S-CSCF or other network entities that handle calls and sessions. The HSS  104  stores subscription-related information such as user profiles, performs user authentication and authorization, and can provide information about the physical location of a user. When multiple HSS&#39;s are used in a network, an SLF  105  can be used to direct the queries to the HSS  104  storing the information. Legacy signaling networks may also use the HSS  104  for services. The MRFC  111  communicates with the S-CSCF and controls the MRFP  112  to implement media related functions. The combination of the MRFC  111  and MRFP  112  provides a source of media in the home network. The BGCF  107  is a server that can route based on telephone number and is used when calling to a phone on the circuit switched network. The MGCF  108  and MGW  109  are used to convert signaling from IMS to that which is appropriate for PSTN  110  circuit switched networks. The IP Multimedia Networks can include application servers and other network entities that provide services to User Equipment (UE). The UE can include, for example, a cell phone, a personal digital assistant (PDA), or a laptop computer. 
       FIG. 2  illustrates an MMD system  210  within a larger network  200 . The MMD system  210  includes many of the same functions as the IMS system  100  of  FIG. 1 , but further includes an access gateway/foreign agent  201  to communicate with access networks  215 , as well as a home agent  202  to provide Mobile IP support to mobile stations (e.g., cell phone, PDA, laptop, etc.). 
     In the context of the IMS and MMD systems, a P-CSCF can be the initial interface between, for example, a mobile device and an IMS. A P-CSCF is typically located in a visited network or in a home network when the visited network is not IMS compliant. The P-CSCF acts as a Session Initiation Protocol (SIP) proxy and can forward messages from the user equipment or mobile station to the appropriate network entity and from a network entity to the user equipment/mobile station. The P-CSCF can inspect messages, provide SIP message compression/decompression using, for example, SIGComp, provide a security associate to the UE/MS, and generate charging data records (CDR) because it sits on the path of the signaling message. The P-CSCF can also include or communicate with a policy decision function (PDF) that authorizes media resources such as the provided quality of service (QoS), management of bandwidth, and provided access. 
     The I-CSCF is the contact point within a network for connections destined to a user of that network or a roaming user currently located within the network&#39;s service area. The I-CSCF assigns an S-CSCF to a user so that the user can communicate with the network. The I-CSCF&#39;s IP address can be published in a Domain Name System (DNS) so that remote servers can find it and use it as an entry point. 
     The S-CSCF performs the session control services for the, for example, UE/MS. This includes handling registration of the UE/MS, inspecting messages being routed through the S-CSCF, deciding which application server provides service, providing routing services such as sending messages to the chosen application server or to a PSTN, and enforcing the policies of a network for a given user. The S-CSCF can also communicate with the HSS to access user profiles and other information. 
     Application servers (e.g.,  220  and  221 ) can host and execute services such as caller ID, call waiting, call holding, push-to-talk, call forwarding, call transfer, call blocking services, lawful interception, announcement services, conference call services, voicemail, location based services, and presence information. The application servers can interface with the S-CSCF using SIP and, depending on the service, can operate in an SIP proxy mode, an SIP user agent mode, or an SIP back-to-back user agent mode. 
       FIG. 3  illustrates a control plane architecture for an IMS/MMD solution that can be used in accordance with some embodiments. A session manager  310  services and processes user session data flow for user equipment(UE)/mobile subscribers(MS). The session manager  310  includes functional layers such as a system service layer  311 , a call processing layer  320 , and a call processing support services layer  313 . The system services layer  311  provides an interface for instructions to be passed to the session manager  310  and the other layers. A command line interface (CLI)  314  as well as network processing unit interface  315  can be included. The call processing layer includes a service broker/Service Control Interaction Manager (SCIM)  321 , a CSCF core  322  that includes an I-CSCF, an P-CSCF, and an S-CSCF, a unified message mapping interface  323 , applications  324 , and a SIP stack  325 . The call processing support services layer  313  includes a variety of services such as routing and address translation service, subscriber management service, changing interface service, media interface service, QoS policy interface service, security interface, and regulatory server interface. 
     Returning to the call processing layer  320 , this layer includes signaling protocols and call control using universal SIP as an application program interface (API). The signaling protocols can be, for example, SIP, ISUP, MGCP, or H. 323 . Further, the call processing layer  320  allows inter-working between SIP variants and other protocols through a unified messaging mapping (UMM) interface. The UMM interface can convert protocol specific messages and parameters to the universal SIP like API format. SIP like messaging is used, in some embodiments, because SIP has a large message set and can cover the possible messaging scenarios for SIP and other protocols. 
     SIP messages can include, for example, request messages such as, INVITE, CANCEL, BYE, and ACK. SIP message can also include, response messages, such as, for example, PRACK, MESSAGE, PUBLISH, REFER, UPDATE, and OPTIONS. SIP message headers can include, for example, Via, Record Route, Route Contact, To, and From. Network topology information can be contained in these headers and these headers can be removed and/or encrypted in some embodiments. 
     As illustrated in  FIG. 4 , in some embodiments, a message can be received, at  400 , at an intermediate  405 , from, for example, a internal network component. The intermediate  405 , can be, for example, a network component at a network boundary, a CSCF, a P-CSCF, an I-CSCF, a proxy server, and/or an SMS proxy server. Topology hiding can be performed by removing information from a message, at  410 , and saving the information, at  420 . The message can be sent, at  430 , to a receiver  406  such as, for example, a UE/MS. The receiver can receive the message at  440  and send a response at  450 . When a response to the message is received, at  460 , the topology information can be retrieved, at  470 , and inserted into the response, at  480 . The receiver  406  can be, for example, a device outside of the network of intermediate  405 . For example, receiver  406  can be a mobile handset in communication with another device through an access network (e.g., Access Network  215  of  FIG. 2 ). 
     The topology information can be saved, at  420 , in, for example, a database, a cache, RAM, or any appropriate memory. The information can be associated with, for example, a user identifier that can be used to retrieve the information, at  470 . The user identifier can be, for example, a public user ID. In some embodiments, the memory space where the information is stored can be reserved and/or allocated to be used for a specific call session and can be released and/or de-allocated when the session ends. 
       FIG. 5  shows another illustration of a method for performing topology hiding. A message  501 , for example, an SIP request such as an INVITE, can be sent, at  510 , from sender  500 . The message  501  can arrive at an intermediate  550  and have its topology information removed and stored, at  520 . The message  502  (message  501  without topology information) can be sent, at  530 , to a receiver  560 . Receiver  560  can send a response  503 , at  535 . The response  503  can be received at intermediate  550  and have its topology information retrieved and inserted, at  540 . The response  504  ( 503  with the topology information) can be sent, at  545 , to sender  500 . Intermediate  550 , can be, for example, a network component at a network boundary, a CSCF, a P-CSCF, an I-CSCF, a proxy server, and/or an SMS proxy server. 
     In some embodiments, intermediate  550  can decide to remove only some topology information from message  501 . For example, the address of sender  500  can be left in message  501 , but other topology information, for example, the addresses of devices that message  501  traveled through between sender  500  and intermediate  550  can be removed. This may be done, for example, if receiver  560  needs to know the address of sender  500 . Intermediate  550  can encrypt some topology information and remove other topology information from a message  500 . For example, in the previous example, the address of sender  500  can be encrypted. Some embodiments can also select between one of using encryption or removing topology information (e.g. headers) to perform topology hiding. Decisions of whether to and/or what to remove and/or encrypt from topology information can be based on various factors, such as, for example, the identity and/or location of receiver  560 , the identity and/or location of sender  500 , the identity and/or location of intermediate  550 , the type of topology information, the type of message  501 , and/or network policy settings (e.g., P-CSCF policy, I-CSCF policy, etc.). In addition, in some embodiments, topology hiding can be enabled or disabled using a command line interface (CLI)/event monitoring service (EMS). 
     Returning to system  100  of  FIG. 1 , A P-CSCF  101 , according to some embodiments, can perform various tasks upon receiving a message. This message can be, for example, in UMM format and use UMM parameter. On receiving a REGISTER message, for example, a P-CSCF can insert a path header and insert a require header containing the option tag “path.” The P-CSCF can create a globally unique IMS charging identity (ICID), save it locally and insert it into the ICID parameter of the p-Charging-Vector header. If the security is supported, a P-CSCF can insert the integrity protected parameter with a “yes” value. Otherwise it can insert the integrity protected parameter with the a “no” value. A P-CSCF can insert a P-Visited-Network-ID header field with a pre-provisioned string that identifies the visited network in the home network. Even if the P-CSCF is local, this string can be inserted to be used for logging purposes. 
     On receiving  401  from S-CSCF a P-CSCF removes IK and CK values and sends a message to security interface for setting up the security association set up as a result of the challenge. If the security is enabled, a security server header can be inserted in the response. Once the positive response is received from security interface, the P-CSCF can send a returnResultSuccess to callLeg. 
     On receiving  200  OK response to register, a P-CSCF can check the expires header or expires parameter in contact. If it is non-zero then the service route headers for that public user identity can be stored. The security interface can be sent a message to setup the security association, if a new security association is needed. A message can be sent to the security interface to delete the old security association, if the new association is requested. A P-CSCF can return result success/failure to the callLeg to pass the response received from the security interface. 
     On receiving a request from UE P-CSCF a P-CSCF can match the service route header for that public user identity against the preloaded route header. If the match is not successful, a result error with a  400  response code can be returned to the callLeg. The P-CSCF&#39;s address can be added in the “via” header as configured in the service mode. The P-CSCF&#39;s Universal Resource Indicator (URI) can be added in the record route. The P-preferred-ID can removed and the P-Asserted-ID can be added. A globally unique ICID parameter can be created and inserted in the P-charging-Vector header. The result can be sent to the callLeg. 
     For responses, the P-CSCF can store the value received in the p-charging-function-address header and store the list of record route. The P-CSCF can also change the record route port number to the protected server port number as negotiated with UE during registration. 
     In some embodiments, a P-CSCF interacts with an IP Security (IPSEC) manager to set up security associations and interact with a policy interface to apply application policies. A P-CSCF can perform I-CSCF discovery in various ways. For example, a P-CSCF can use a configured list of I-CSCF defined by a peering server configuration. In other embodiments, a P-CSCF can perform I-CSCF discovery by using a DNS/Naming Authority Pointer (NAPTR). 
     IP address spoofing/IMS identity impersonation prevention is provided in certain embodiments. The P-CSCF can compare the IP address the request is received from and the subscriber&#39;s contact ip address to make sure the user who is registered is the one trying to make a call. The P-CSCF can also check the ip address allocated at the Packet Data Protocol (PDP) context creation with the IP address in the received SIP request to make sure the user who is paying for the IMS is using its own data access. 
     In some embodiments, the I-CSCF interfaces with HSS to validate visited network information sent by P-CSCF. If the subscriber is not allowed to roam in the visited network, the HSS sends an error indicating that roaming is not allowed. In certain embodiments, where the CSCF functionality is integrated into a Core CSCF module, the I-CSCF does not have to discover the S-CSCF based on the registering user and capabilities. In the second configuration when P-CSCF is separate I-CSCF is still integrated with S-CSCF therefore discovery is not required. External S-CSCF discovery can also be used by requesting an additional attribute from the HSS and selecting the S-CSCF based on the capabilities requested by the subscriber 
     Although the invention has been described and illustrated in the foregoing illustrative embodiments, it is understood that the present disclosure has been made only by way of example, and that numerous changes in the details of implementation of the invention can be made without departing from the spirit and scope of the invention, which is limited only by the claims that follow. Features of the disclosed embodiments can be combined and rearranged in various ways within the scope and spirit of the invention.