METHOD AND SYSTEM FOR CORRELATION OF INTERNET APPLICATION DOMAIN IDENTITIES AND NETWORK DEVICE IDENTIFIERS

• US 20150019721A1
• Filed: 07/11/2014
• Published: 01/15/2015
• Est. Priority Date: 07/11/2013
• Status: Active Grant

• Current Assignee: Cinarra Systems
• Original Assignee: Cinarra Systems Pte., Ltd. (Cinarra Systems, Inc.)
• Inventors: Zinin, Alexey D.
• Granted Patent: US 9,621,625 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 61/103 across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

System and methods for determining a relationship between an application-level identifier and a network-level identifier are provided. In one implementation, a discovery server receives a data request that includes an application-level identifier and a transitory network-level identifier. Based on the transitory network-level identifier, the discovery server determines a stable network-level identifier, and further maps the application-level identifier to the stable network-level identifier.

Claims

1. A system for determining a relationship between an application-level identifier and a network-level identifier, the system comprising:

a discovery server comprising at least one memory for storing computer-executable instructions and at least one processor for executing the instructions, wherein the execution of the instructions programs the server to perform operations comprising;

receiving a data request comprising an application-level identifier and a transitory network-level identifier;

determining a stable network-level identifier based on the transitory network-level identifier; and

mapping the application-level identifier to the stable network-level identifier.

2. The system of claim 1, further comprising an application integration agent for providing content to an application platform, the content comprising a reference to an external server.

3. The system of claim 2, wherein the reference to the external server resolves to an address associated with the discovery server.

4. The system of claim 3, wherein the operations further comprise relaying the data request to the external server.

5. The system of claim 1, further comprising an application integration agent for providing content to an application platform, the content comprising a reference to the discovery server.

6. The system of claim 5, wherein the data request is based on the reference to the discovery server.

7. The system of claim 1, wherein the determining comprises:

extracting the transitory network-level identifier from the data request; and

resolving the stable network-level identifier based on IP address allocation records corresponding to the transitory network-level identifier.

8. The system of claim 1, further comprising an application integration agent for providing customized content based on the mapping between the application-level identifier and the stable network-level identifier.

9. The system of claim 1, wherein the application-level identifier is selected from the group consisting of an HTTP cookie, a UUID, an ODIN, an IFA, and a UDID.

10. The system of claim 1, wherein the transitory network-level identifier comprises an IP address.

11. The system of claim 1, wherein the stable network-level identifier is selected from the group consisting of a MAC address, an IMEI, and an IMSI.

12. A method of determining a relationship between an application-level identifier and a network-level identifier, the method comprising:

receiving, by a discovery server utilizing a processor, a data request comprising an application-level identifier and a transitory network-level identifier;

determining, by the discovery server, a stable network-level identifier based on the transitory network-level identifier; and

mapping, by the discovery server, the application-level identifier to the stable network-level identifier.

13. The method of claim 12, further comprising providing content, by an application integration agent, to an application platform, the content comprising a reference to an external server.

14. The method of claim 13, wherein the reference to the external server resolves to an address associated with the discovery server.

15. The method of claim 14, further comprising relaying, by the discovery server, the data request to the external server.

16. The method of claim 12, further comprising providing content, by an application integration agent, to an application platform, the content comprising a reference to the discovery server.

17. The method of claim 16, wherein the data request is based on the reference to the discovery server.

18. The method of claim 12, wherein the determining comprises:

extracting the transitory network-level identifier from the data request; and

resolving the stable network-level identifier based on IP address allocation records corresponding to the transitory network-level identifier.

19. The method of claim 12, further comprising providing customized content, by an application integration agent, based on the mapping between the application-level identifier and the stable network-level identifier.

20. The method of claim 12, wherein the application-level identifier is selected from the group consisting of an HTTP cookie, a UUID, an ODIN, an IFA, and a UDID.

21. The method of claim 12, wherein the transitory network-level identifier comprises an IP address.

22. The method of claim 12, wherein the stable network-level identifier is selected from the group consisting of a MAC address, an IMEI, and an IMSI.