METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR USING

A DIAMETER ROUTING AGENT (DRA) TO OBTAIN MAPPINGS BETWEEN MOBILE SUBSCRIBER IDENTIFICATION INFORMATION AND DYNAMICALLY ASSIGNED INTERNET PROTOCOL (IP) ADDRESSES AND FOR MAKING THE MAPPINGS ACCESSIBLE TO APPLICATIONS

PRIORITY CLAIM

This application claims the benefit of U.S. Patent Application Serial No. 13/748,547 filed January 23, 2013; the disclosure of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The subject matter described herein relates to making mobile subscriber identification information accessible to applications. More particularly, the subject matter described herein relates to methods, systems, and computer readable media using a DRA to obtain mappings between mobile subscriber identification information and dynamically assigned IP addresses and for making the mappings accessible to applications.

BACKGROUND

When a mobile device, such as a mobile handset, accesses a network, the mobile device may be dynamically assigned an IP address so that the mobile device can communicate with applications over the Internet. One problem for application servers in the mobile Internet space is that the application servers may not receive the subscriber's identifying information, such as the mobile subscriber integrated services digital network (MSISDN) number or international mobile station identifier (IMSI), when the application servers receive a new data session for the subscriber. Application servers might only receive the dynamically assigned IPv4 or v6 address for the data session and may need to determine the identity of the subscriber, for example, for billing purposes.

Accordingly, there exists a need for methods, systems, and computer readable media for methods, systems, and computer readable media for using a DRA to obtain mappings between mobile subscriber identification information and dynamically assigned IP addresses and for making the mappings accessible to applications. SUMMARY

The subject matter described herein includes methods, systems and computer readable media for using a DRA to obtain mappings between mobile subscriber identification information and dynamically assigned IP addresses and for making the mappings accessible to applications. One exemplary method includes, at a DRA, receiving a Diameter message containing a dynamically assigned IP address and mobile subscriber identification information. The method further includes routing the received Diameter signaling message. The method further includes copying, by the DRA, the IP address and the mobile subscriber identification information from the message. The method further includes making a mapping between the dynamically assigned IP address and the subscriber identification information accessible to applications.

The subject matter described herein can be implemented in software in combination with hardware and/or firmware. For example, the subject matter described herein can be implemented in software executed by a processor. In one exemplary implementation, the subject matter described herein can be implemented using a non-transitory computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer control the computer to perform steps. Exemplary computer readable media suitable for implementing the subject matter described herein include non-transitory computer-readable media, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. In addition, a computer readable medium that implements the subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms. BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the subject matter described herein will now be explained with reference to the accompanying drawings of which:

Figure 1 is a network diagram illustrating an exemplary system for using a DRA to obtain mappings between dynamically assigned IP addresses and mobile subscriber identification information and for making the mappings accessible to applications according to an embodiment of the subject matter described herein;

Figure 2 is a network diagram illustrating an exemplary system for using a DRA to obtain mappings between dynamically assigned IP addresses and mobile subscriber identification information and for making the mappings accessible to applications according to an embodiment of the subject matter described herein;

Figure 3 is a network diagram illustrating an exemplary system for using a DRA to obtain mappings between dynamically assigned IP addresses and mobile subscriber identification information and for making the mappings accessible to applications according to an embodiment of the subject matter described herein;

Figure 4 is a block diagram for illustrating an exemplary internal architecture and message flow for using a DRA to obtain mappings between mobile subscriber identification information and dynamically assigned IP addresses and for making the mappings available to applications according to an embodiment of the subject matter described herein;

Figure 5 is a block diagram illustrating an exemplary internal architecture for using a DRA to obtain mappings between mobile subscriber identification information and dynamically assigned IP addresses and for making the mappings available to applications according to an embodiment of the subject matter described herein;

Figure 6 is a block diagram illustrating an exemplary architecture and message flow for using a DRA to obtain mappings between mobile subscriber identification information and dynamically assigned IP addresses and for making the mappings available to applications according to an embodiment of the subject matter described herein; and Figure 7 is a flow chart illustrating an exemplary process for using a DRA to obtain mappings between dynamically assigned IP addresses and mobile subscriber identification information and for making the mappings accessible to applications according to an embodiment of the subject matter described herein.

DETAILED DESCRIPTION

The subject matter described herein includes methods, systems, and computer readable media for using a DRA to obtain mappings between mobile subscriber identification information and dynamically assigned IP addresses and for making the mappings accessible to applications. Figure 1 is a network diagram illustrating a DRA and other nodes associated with providing services to mobile devices. Referring to Figure 1 , DRA 100 routes received Diameter signaling messages. DRA 100 may also be referred to as a Diameter signaling router or DSR. In addition to routing received Diameter signaling messages, DRA 100 may include a message copy function that copies certain Diameter signaling messages to a dynamic IP to mobile subscriber ID mapping database 102, which may be accessible by applications, such as mobile Internet application 104, to obtain mobile subscriber identification information. DRA 100 may obtain mappings between mobile subscriber identification information and dynamically assigned IP addresses from Diameter signaling messages received on the Gx interface between gateway GPRS support node (GGSN) 106 configured with a policy charging and enforcement function (PCEF) orfrom a packet data network (PDN) gateway (PGW) 108 configured with a PCEF. DRA 100 may route messages received on the Gx interface to policy and charging rules function (PCRF) 110. PCRF 110 may determine the appropriate policy and charging rules to apply to a given session in response to requests from PCEFs.

In the example illustrated in Figure 1 , in step 1 , DRA 100 receives a credit control request - initial (CCR-I) message from PGW 108. The CCR-I message may be generated by the PCEF function of PGW 108 to determine the appropriate charging and policy rules to apply to a data session requested by mobile subscriber. In step 2, DRA 100 receives the CCR-I message and routes the CCR-I message to PCRF 110, which determines the appropriate policy and charging rules to apply to the session.

In step 3, DRA 100 copies the CCR-I message or at least the dynamically assigned IP address and mobile subscriber identification information from the CCR-I message to dynamic IP to mobile subscriber ID mapping database 102. Upon receipt of the CCR-I message, database 102 may store the mapping between the dynamically assigned IP address and the mobile subscriber identifier. In step 4, application 104 queries dynamic IP to mobile subscriber ID mapping database 102 with the dynamically assigned IP address, and, in step 5, database 102 responds with the mobile subscriber identification information.

In Figure 1 , dynamic IP to mobile subscriber identification information mapping database 102 is external to DRA 100. In an alternate implementation, database 102 may be internal to DRA 100. Figure 2 illustrates such an embodiment. Referring to the message flow in Figure 2, in step 1 , PGW 108 sends a CCR-I message to PCRF 110 to determine the appropriate policy and charging rules to apply to a new session. In step 2, DRA 100 routes the CCR-I message to PCRF 110. In step 3, DRA 100 copies the CCR-I message or at least the mapping between the mobile subscriber identification information and the dynamically assigned IP address associated with the new session and stores the information in its internal dynamic IP to mobile subscriber ID mapping database 102. In step 4, mobile Internet application 104 queries DRA 100 to determine the mobile subscriber identification information. The query may include the dynamically assigned IP address. In response to the query, DRA 100 accesses its internal dynamic IP to mobile subscriber ID mapping database 102 and obtains the mobile subscriber identification information. In step 5, DRA 100 responds to application 104 with the mobile subscriber identification information, such as the IMSI or MSISDN.

In yet another implementation, DRA 100 may not maintain the mapping between the dynamically assigned IP address and the mobile subscriber identifier but instead may identify the application from the CCR-I message or have p re-configured information about the application and push the mapping to the application without requiring a query from the application. This scenario is illustrated in Figure 3. Referring to the message flow in Figure 3, in step 1 , PGW 108 sends a CCR-I message to PCRF 110 to determine the appropriate policy and charging rules to apply to a new session. In step 2, DRA 100 routes the CCR-I message to PCRF 110. In step 3, DRA 100 identifies the application associated with the new session from the CCR-I message, copies the CCR-I message or at least the mapping of the mobile subscriber identifier to the dynamically assigned IP address, and sends the copied CCR-I message to application 104. The embodiment illustrated in Figure 3 is advantageous in that application 104 is not required to query a database to obtain the mobile subscriber identification information.

Figure 4 illustrates an exemplary internal architecture and message flow within DRA 100 for the scenario illustrated in Figure 1 where the dynamic IP to mobile subscriber identification information database is external to DRA 100. In Figure 4, DRA 100 includes a plurality of message processors 400 and application processors 402. Message processors 400 and application processors 402 may each include a printed circuit board with one or more microprocessors and associated memory located thereon. Each microprocessor may execute one or more Diameter related modules for routing or processing Diameter signaling messages. In the illustrated example, message processors 400 include Diameter routing modules 403 and message copy modules 404. Diameter routing modules 403 route received Diameter signaling messages. Message copy modules 404 copy information, such as mappings between dynamically assigned IP addresses and mobile subscriber identifiers, from received signaling messages. Application processors 402 may host one or more Diameter applications 405 and may also include Diameter routing modules 403.

In the message flow illustrated in Figure 4, in step 1 a CCR-I message is received by one of message processors 400. In step 2, the Diameter routing modules 403 on ingress message processor 400 routes the CCR-I message to egress message processor 400. In step 3, egress message processor 400 forwards the CCR-I message over the network to the destination. When the original CCR-I message is received by Diameter message processor 400, message copy module 404 may identify the CCR-I message as being of the type that contains information for mapping a dynamically assigned IP address for a session to a mobile subscriber identifier, such as an MSISDN or IMSI. Accordingly, in step 4, message copy module 404 on ingress message processor 400 makes a copy of the CCR-I or at least the mapping between the dynamically assigned IP address and the mobile subscriber identification information and forwards the copy to egress message processor 400 that is associated with external dynamic IP to mobile subscriber ID mapping database 102. In step 5, egress message processor 402 forwards the copied information to database 102, which stores the mapping information for subsequent access by applications.

Figure 5 illustrates an exemplary internal architecture for DRA 100 corresponding to the scenario illustrated in Figure 2 where the dynamic IP address to mobile subscriber identification database is internal to DRA 100. Referring to Figure 5, each application processor 402 hosts dynamic IP to mobile subscriber ID mapping database 102. Dynamic IP to mobile subscriber ID mapping databases 102 hosted by application processors 402 may be identically provisioned, and message processors 400 may load share queries between databases hosted by different application processors 402. Referring to the message flow illustrated in Figure 5, in steps 1 -3, the CCR-I message is received by DRA 100 and routed to egress Diameter message processor 400 associated with PCRF 110, similar to the message flow illustrated in Figure 2. In step 4, message copy module 404 on ingress message processor 400 copies the CCR-I message or at least the dynamically assigned IP address and the mobile subscriber identification information from the CCR-I message and sends the copy to application processors 402, which store the information in internal databases 102. In step 5, application 104 queries DRA 100 for the subscriber identification information. The query is forwarded to one of the application processors 402 in step 6. In step 7, receiving application processor 402 accesses its internal database 102 and responds with the subscriber identification information. In step 8, the subscriber identification information is provided to querying application 104.

Figure 6 is a block diagram and message flow illustrating an exemplary architecture for DRA 100 for the scenario illustrated in Figure 3 where the DRA 100 pushes subscriber identification information to application 104 without requiring a query from the application. Referring to the message flow in Figure 6, in step 1 , the CCR-I message is received by ingress message processor 400, which routes the CCR-I message to egress message processor 400 in step 2. In step 3, egress message processor 400 routes the CCR-I message to its intended destination, which in this example is PCRF 110.

In step 4, message copy module 404 on ingress message processor 400 identifies application 104 from the CCR-I message, copies the CCR-I message and (in step 5) provides the message copy to egress message processor 400 that is associated with the application. The application may be identified from the access point name (APN) or other parameter in the CCR-I message or may be pre-configured. In step 6, egress message processor 400 pushes the mapping information to the identified application directly without requiring a query from the application.

Figure 7 is a flow chart illustrating exemplary steps for using a DRA to obtain mappings between dynamically assigned IP addresses and mobile subscriber identifiers and for making the mappings accessible to applications according to an embodiment of the subject matter described herein. Referring to Figure 7, in step 700, a Diameter signaling message is received. For example, DRA 100 may receive a CCR-I message from a PGW or other entity. In step 702, the DRA routes the received Diameter signaling message. For example, DRA 100 may route the CCR-I to PCRF 110. In step 704, it is determined whether the message is of a type that contains information that can be used to map a mobile subscriber identifier to an IP address. In one example, DRA 100 may identify CCR-I messages as being of the type that contain dynamic IP address to mobile subscriber identifier mapping information. Other Diameter message types may be routed or processed by DRA 100 according to the message type. If the message is determined not to be of the type that contains the mapping information, control returns to step 700 where the next message is processed. If the message is determined to be of the type that contains the mapping information, in step 706, the mapping between the dynamic IP address and the mobile subscriber identification information in the message is copied. For example, a message copy module 404 in DRA 100 may copy the dynamically assigned IP address and the MSISDN and/or IMSI from the message. In step 706, the mapping between the dynamically assigned IP address and the mobile subscriber identification information is made accessible to an application. For example, DRA 100 may push the mapping to an application, store the mapping in an internal database accessible to applications, or provide the mapping to an external database accessible to applications.

In addition to maintaining mappings between a dynamically assigned IP address and mobile subscriber identification information copied from a received Diameter signaling message, a DRA according to an embodiment of the subject matter described herein may also maintain mappings between different mobile subscriber identifiers and make the mappings available to applications. For example, DRA 100 in any of the above-described examples may copy a first mobile subscriber identifier, such as an IMSI and the dynamically assigned IP address from a received Diameter signaling message, such as a Gx signaling message. DRA 100 may be preconfigured with mappings between the first mobile subscriber identifier and as second mobile subscriber identifier, such as an MSISDN number. Applications, such as application 104, may then query DRA 100 with the MSISDN number and receive the IMSI.

It will be understood that various details of the presently disclosed subject matter may be changed without departing from the scope of the presently disclosed subject matter. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.