Method for distributing contact information between applications
View Patent ↗A method and system for distributing contacting information between applications is provided. The system preferably uses an ENUM-type protocol and a middleware tool kit to associate telephone numbers to other identifying information, such as e-mail addresses or URLs for web sites. The system enables the associated contacting information to be shared across multiple applications that may be implemented on a computer or a mobile telephony device. Information is shared only after verification that a requester is authorized to receive the requested contacting information.
1. A method for mobile application authorization, the method being implemented by one or more processors of a server and comprising:
receiving, over a network from a first mobile device of a first user, data corresponding to (i) a first phone number of the first mobile device, (ii) a set of account identifiers for the first user, and (iii) a set of phone numbers authorized to access the set of account identifiers;
receiving, over the network from a second mobile device of a second user, a query including the first phone number of the first mobile device and a second phone number of the second mobile device; and
in response to determining that the second phone number is in the set of phone numbers authorized to access the set of account identifiers, transmitting, without receiving an authorization signal from the first user in response to the query, one or more account identifiers from the set of account identifiers to the second mobile device.
2. The method of claim 1 , further comprising:
storing, in a server memory of the server, a mapping of the first phone number to the set of account identifiers for the first user and the set of phone numbers authorized to access the set of account identifiers.
3. The method of claim 2 , wherein the phone numbers authorized to access the set of account identifiers are access keys to the set of account identifiers in the server memory.
4. The method of claim 1 , wherein the second mobile device includes a middleware application that comprises:
a first application programming interface (API) for receiving requests for account identifiers from applications and transferring responses to the requests to the applications; and
a second API for transmitting the requests for account identifiers to the server over the network and receiving the responses to the requests from the server.
5. The method of claim 1 , wherein the set of account identifiers for the first user includes at least one Uniform Resource Indicator (URI).
6. The method of claim 5 , wherein the at least one URI is associated with an identifier selected from the group consisting of an e-mail address, an instant messaging handle, and a Uniform Resource Locator (URL) of a web page.
7. The method of claim 1 , wherein transmitting the one or more account identifiers from the set of account identifiers comprises transmitting an SMS text message to the second mobile device.
8. A network server comprising:
one or more processors; and
one or more memory resources that access the instructions to:
receive, over a network from a first mobile device of a first user, data corresponding to (i) a first phone number of the first mobile device, (ii) a set of account identifiers for the first user, and (iii) a set of phone numbers authorized to access the set of account identifiers;
receive, over the network from a second mobile device of a second user, a query including the first phone number of the first mobile device and a second phone number of the second mobile device; and
in response to a determination that the second phone number is in the set of phone numbers authorized to access the set of account identifiers, transmit, without receiving an authorization signal from the first user in response to the query, one or more account identifiers from the set of account identifiers to the second mobile device.
9. The network server of claim 8 , wherein the one or more processors access the instructions to:
store, in a server memory of the network server, a mapping of the first phone number to the set of account identifiers for the first user and the set of phone numbers authorized to access the set of account identifiers.
10. The network server of claim 9 , wherein the phone numbers authorized to access the set of account identifiers are access keys to the set of account identifiers in the server memory.
11. The network server of claim 8 , wherein the second mobile device includes a middleware application that comprises:
a first application programming interface (API) for receiving requests for account identifiers from applications and transferring responses to the requests to the applications; and
a second API for transmitting the requests for account identifiers to the network server over the network and receiving the responses to the requests from the network server.
12. The network server of claim 8 , wherein the set of account identifiers for the first user includes at least one Uniform Resource Indicator (URI).
13. The network server of claim 12 , wherein the at least one URI is associated with an identifier selected from the group consisting of an e-mail address, an instant messaging handle, and a Uniform Resource Locator (URL) of a web page.
14. The network server of claim 8 , wherein transmitting the one or more account identifiers from the set of account identifiers comprises transmitting an SMS text message to the second mobile device.
15. A non-transitory computer-readable medium that stores instructions, executable by one or more processors of a network server, to cause the network server to perform operations that comprise:
receiving, over a network from a first mobile device of a first user, data corresponding to (i) a first phone number of the first mobile device, (ii) a set of account identifiers for the first user, and (iii) a set of phone numbers authorized to access the set of account identifiers;
receiving, over the network from a second mobile device of a second user, a query including the first phone number of the first mobile device and a second phone number of the second mobile device; and
in response to determining that the second phone number is in the set of phone numbers authorized to access the set of account identifiers, transmitting, without receiving an authorization signal from the first user in response to the query, one or more account identifiers from the set of account identifiers to the second mobile device.
16. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed by the one or more processors, cause the network server to perform operations that comprise:
storing, in a server memory of the network server, a mapping of the first phone number to the set of account identifiers for the first user and the set of phone numbers authorized to access the set of account identifiers.
17. The non-transitory computer-readable medium of claim 16 , wherein the phone numbers authorized to access the set of account identifiers are access keys to the set of account identifiers in the server memory.
18. The non-transitory computer-readable medium of claim 15 , wherein the second mobile device includes a middleware application that comprises:
a first application programming interface (API) for receiving requests for account identifiers from applications and transferring responses to the requests to the applications; and
a second API for transmitting the requests for account identifiers to the network server over the network and receiving the responses to the requests from the network server.
19. The non-transitory computer-readable medium of claim 15 , wherein the set of account identifiers for the first user includes at least one Uniform Resource Indicator (URI).
20. The non-transitory computer-readable medium of claim 19 , wherein the at least one URI is associated with an identifier selected from the group consisting of an e-mail address, an instant messaging handle, and a Uniform Resource Locator (URL) of a web page.