Universal short code administration facility

• US 8,374,637 B2
• Filed: 02/03/2011
• Issued: 02/12/2013
• Est. Priority Date: 02/07/2003
• Status: Active Grant

• Current Assignee: Sybase 365 Incorporated (SAP SE)
• Original Assignee: Sybase 365 Incorporated (SAP SE)
• Inventors: Sweatman, Phillip J., Lovell, Robert C. Jr., Chava, Venkatesh, Zimmern, Christian
• Primary Examiner(s): Kincaid, Lester
• Assistant Examiner(s): HERRERA, DIEGO D
• Application Number:
  US13/020,442
• Publication Number:
  US 20110151902A1
• Time in Patent Office: 740 Days
• Field of Search: 455/466
• US Class Current: 455/466
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support
• CPC Class Codes: H04W 88/184 Messaging devices, e.g. message centre

Abstract

Systems and methods for assigning short codes to provide uniformity among wireless carriers. In the systems and methods, a Universal Short Code (USC) Administrator maintains a list of short codes and their lease status so that SMS messages sent to a particular short code may be routed to the proper holder of the short code. A network facilitator is in communication with both the USC Administrator and at least one wireless carrier to route the SMS message to the proper holder of the short code. The short code may be leased for a specified period of time so that the short code can be reassigned after expiration of the lease.

Claims

1. In a Universal Short Code (USC) Administrator (UA), a server-based method for administering USCs, the server-based method comprising:

(a) receiving a USC lease request, the USC lease request comprising (i) an indicia of an Application Provider (AP) and (ii) a specified period of time;

(b) determining from the USC lease request a specific USC;

(c) determining a current status of the specific USC through at least a lookup against a repository;

(d) temporarily assigning the specific USC to the AP for the specified period of time, provided the current status of the specific USC is available, by at least updating the repository to (i) change the current status of the specific USC to unavailable and (ii) associate the AP indicia with the specific USC; and

(e) notifying one or more entities external to the UA of the temporary assignment of the specific USC to the AP.

2. The server-based method according to claim 1, wherein step (b) includes one of (i) processing one or more data elements in the USC lease request or (ii) processing a random selection.

3. The server-based method according to claim 1, wherein step (c) further includes contacting one or more entities external to the UA.

4. The server-based method according to claim 1, wherein step (d) further includes a financial transaction comprising a USC lease price.

5. The server-based method according to claim 4, wherein the USC lease price varies depending on one or more of (i) the specific USC, (ii) when the specific USC is leased, (iii) how long the specific USC is leased, and (iv) the popularity of the specific USC.

6. The server-based method according to claim 1, wherein the information in step (e) is dispatched by one or more of (i) a directed response or (ii) a broadcast.

7. The server-based method according to claim 1, wherein the temporary assignment of the specific USC to the AP is (i) automatically renewed at the end of the specified period of time, (ii) announced to one or more entities external to the UA near the end of the specified period of time, or (iii) rescinded due to low usage.

8. The server-based method according to claim 1, wherein at the end of the specified period of time the specific USC is unassigned from the AP by at least updating the repository to (i) change the current status of the specific USC to available and (ii) disassociate the AP indicia from the specific USC.

9. The server-based method according to claim 1, wherein in response to an information request the UA returns information on (i) a USC and/or (ii) an AP.

10. The server-based method according to claim 9, wherein the information on a USC includes one or more of (i) a current status of the USC and (ii) a USC lease price.

11. The server-based method according to claim 9, wherein the information on an AP includes one or more of a name of the AP, a mailing address of the AP, a telephone number of the AP, an email address of the AP, a point of contact for the AP, a date on which a USC lease by the AP ends, and a Web site URL of the AP.

12. In a Universal Short Code (USC) Administrator (UA) a processor-based system on a server configured to administer USCs, the processor-based system comprising:

a first interface configured to receive a USC lease request, the USC lease request comprising (i) an indicia of an Application Provider (AP) and (ii) a specified period of time;

application logic configured to (a) determine from the USC lease request a specific USC, (b) determine a current status of the specific USC through at least a lookup against a repository, and (c) temporarily assign the specific USC to the AP for the specified period of time, provided the current status of the specific USC is available, by at least updating the repository to (i) change the current status of the specific USC to unavailable and (ii) associate the AP indicia with the specific USC; and

a second interface configured to notify one or more entities external to the UA of a temporary assignment of the specific USC to the AP.

13. The processor-based system according to claim 12, wherein the application logic is further configured to determine from the USC lease request the specific USC by (i) processing one or more data elements in the USC lease request or (ii) processing a random selection.

14. The processor-based system according to claim 12, wherein the application logic is further configured to contact one or more entities external to the UA to determine the current status of the specific USC.

15. The processor-based system according to claim 12, wherein the application logic is further configured to perform a financial transaction comprising a USC lease price to temporarily assign the specific USC to the AP.

16. The processor-based system according to claim 15, wherein the USC lease price varies depending on one or more of (i) the specific USC, (ii) when the specific USC is leased, (iii) how long the specific USC is leased, and (iv) the popularity of the specific USC.

17. The processor-based system according to claim 12, wherein the application logic is further configured to notify one or more entities external to the UA by one or more of (i) a directed response or (ii) a broadcast.

18. The processor-based system according to claim 12, wherein the temporary assignment of the specific USC to the AP is (i) automatically renewed at the end of the specified period of time, (ii) announced to one or more entities external to the UA near the end of the specified period of time, or (iii) rescinded due to low usage.

19. The processor-based system according to claim 12, wherein at the end of the specified period of time the specific USC is unassigned from the AP by at least updating the repository to (i) change the current status of the specific USC to available and (ii) disassociate the AP indicia from the specific USC.

20. The processor-based system according to claim 12, wherein in response to an information request the UA returns information on (i) a USC and/or (ii) an AP.

21. The processor-based system according to claim 20, wherein the information on a USC includes one or more of (i) a current status of the USC and (ii) a USC lease price.

22. The processor-based system according to claim 20, wherein the information on an AP includes one or more of a name of the AP, a mailing address of the AP, a telephone number of the AP, an email address of the AP, a point of contact for the AP, a date on which a USC lease by the AP ends, and a Web site URL of the AP.