US 7,907,937 B2Grant
Prepaid communication services utilizing a prepaid identifier combined with another identifier
Issue Date:2011-03-15
•26 Claims
•5 Drawing Sheets
Abstract
Calls to or from a prepaid subscriber of a wireless communication network are identified as being associated with prepaid services, and a prepaid identifier is associated with the call. The prepaid identifier and other call information such as call origin or destination is routed to a prepaid services management system in another network that determines if the call is to be authorized based on, for example, a prepaid subscriber account balance stored at the prepaid services management system. The prepaid identifier can be combined with a number associated with the call origin or destination, and the combination delivered to the prepaid services management system.
Metadata
Assignee
- AT&T Mobility II LLC
Inventor
- Robert L. Engelhart
Application Information
Application Number:US 11/964,614
Filing Date:2007-12-26
Priority Date:2003-03-18
Art Unit:2618
Classifications
IPC:
H04W8/02H04W8/18H04W12/06
Patent Drawings (5 sheets)
Description
Technical Field
[0001] The disclosure pertains to providing prepaid services in communication systems.
Background
[0002] Wireless communication systems enable subscribers to send and receive communications at fixed or mobile locations. Typically wireless networks are configured so that a subscriber is associated with a wireless network based on a service agreement in which the subscriber receives a set of pre-arranged communication services in return for payment of a monthly service charge. Services that are not included in the pre-arranged communication services are billed to the subscriber in addition to the basic monthly service charge. Wireless network operators generally provide such services to subscribers who both elect such service plans and who qualify for such plans. Because such subscribers have significant access to communication services provided by the wireless network, a subscriber can accumulate significant network charges during any billing period so that network operators typically offer such periodic service plans to subscribers having acceptable credit histories in order to reduce account losses.
[0003] Some potential network subscribers cannot qualify for periodic subscription services because of unsatisfactory or otherwise insufficient credit histories. For example, some potential subscribers are youths who have yet to establish a credit history. In addition, some potential subscribers prefer to avoid the possibility of incurring the significant network charges that are possible with periodic service plans. For example, a parent can provide a child with a cell phone for emergency use, but is unable to control the use of the cell phone with the possibility that playful use by the child brings a substantial bill for network services. One way of accommodating such users is to provide prepaid communication services. A user provides a deposit to pay for services with a network operator, and the network operator permits the user to access services until the subscriber deposit is exhausted. In this way, the network operator avoids nonpayment risks and the subscriber caps the total amount spent on network services.
[0004] While such prepaid systems offer advantages to both subscribers and network operations, implementation of such systems can be complex as network usage by the prepaid subscriber must be tracked so that the prepaid subscriber cannot exceed the pre-purchased amount or a negative credit balance limit. Wireless network technologies continue to experience rapid technical advances, and installed networks must be operated in conjunction with new, more sophisticated network elements. In addition, newly installed network elements are preferably configured so that customer services are migrated so that newly installed network elements support services for existing network subscribers. Accordingly, methods and systems are needed for providing prepaid services to communication system subscribers.
Summary
[0005] Methods of providing prepaid services in a communication network comprise directing a service request to a first mobile network and associating the request with a prepaid subscriber based on a subscriber profile stored in the first mobile network. A service authorization is then requested from a second mobile network In representative examples, the first mobile network and the second mobile network are configured to conform to a first network protocol and a second network protocol, respectively, and in additional examples, the first network protocol and the second network protocol are different. In other examples, the first mobile network provides a prepaid identifier to the second mobile network and in other examples, a prepaid identifier and a mobile identification number are provided to the second mobile network. In further examples, the requested service is authorized based on a prepaid subscriber account balance stored in the second mobile network. In additional examples, a service completion status for the authorized service is determined and the service completion status is delivered to the prepaid system of the second mobile network. In some examples, a service charge is assessed to the prepaid subscriber account balance based on the service completion status. In other examples, the service charge is not assessed to a prepaid subscriber account balance if the service request is directed to voice mail or if the requested service is incomplete. In still other examples, the prepaid subscriber account balance is insufficient for service authorization, and the prepaid subscriber is contacted to request account balance replenishment.
[0006] A prepaid subscriber management system comprises an input configured to receive a subscriber identifier and a prepaid identifier. A memory is configured to retain prepaid subscriber data, and a processor is configured to produce a call authorization based on the prepaid subscriber data. According to additional representative embodiments, a service duration timer is included and the processor is configured to initiate the service duration timer, and the call completion authorization provided by the processor is configured to expire after a selected service duration.
[0007] Network element that comprises an input configured to receive a service destination identifier and a prepaid identifier, and a prepaid database configured to store prepaid account data associated with the service destination identifier. A processor is configured to interrogate the prepaid database based on receipt of the prepaid identifier, and to authorize providing a requested service based on prepaid account data associated with the service destination. In additional examples, the input is configured to communicate with a public switched telephone network.
[0008] Methods of providing a communication service to a prepaid subscriber comprise receiving a call request at a first network and associating the call request with the prepaid subscriber. A request for prepaid subscriber account information is directed to a second network, and call completion is authorized based on the prepaid subscriber account information. In additional representative examples, the call request is associated with the prepaid subscriber by combining a prepaid identifier with a destination identifier. In other examples, the call request is associated with the prepaid subscriber by combining a prepaid identifier with a source identifier. In further examples, the request for prepaid subscriber account information is directed to the second network via a public switched telephone network. In other examples, a service charge is assessed to a prepaid subscriber account balance.
[0009] Methods of paying for communication services comprise associating a call request for a selected access location with a prepaid subscriber. A prepaid identifier and the selected access location are transmitted to a prepaid management system. A call completion authorization is provided based on a prepaid account status for the selected access location. In additional examples, the prepaid identifier and the selected access location are transmitted to the prepaid management system using a public switched telephone network and the selected access location is a call destination or a call source. In other examples, the prepaid identifier and a call access location identifier are combined.
[0010] These and other examples and features are set forth below with reference to the accompanying drawings.
Brief Description of the Drawings
[0011] FIG. 1 is a schematic block diagram of a communication system that includes two wireless networks.
[0012] FIG. 2 is a schematic diagram illustrating processing of a call request to a prepaid subscriber of a wireless network.
[0013] FIG. 3 is a schematic diagram illustrating processing of a call request to a Prepaid subscriber of a wireless network.
[0014] FIG. 4 is a block diagram illustrating a method of calling a prepaid subscriber.
[0015] FIG. 5 is a block diagram of a communication system that includes a home network and a network associated with prepaid services management.
Detailed Description
[0016] References to ‘a’ or “an” embodiment or example do not necessarily refer to the same embodiment or example although they may. Lines of communication between two points do not necessarily indicate direct communication between the points, although they may. Communications identified by a single arrow may comprise information communicated together or in separate messages and/or signals. Examples are described based on representative communication network standards. Some examples include wireless communication networks configured based on the Global System for Mobile Communications (GSM), the Digital Advanced Mobile Phone Standard (D-AMPS), Interim Standard IS-54 (IS-54), and Interim Standard 136 (s-136). Signaling between mobile switching centers (MSCs) and other devices and networks can be based on Signaling System 7 (SS7), Interim Standard 51 (IS-51), or other messaging standards or protocols. The examples described below refer to any particular standards for convenience in illustrating various features.
[0017] With reference to FIG. 1 , a communication network 100 includes a mobile switching center (MSC) 102 that is in communication with a GSM MSC 104 via a communication link 106. The MSC 102 can be configured based on a communication standard such as IS-54 or IS-136 that permits communication signal multiplexing using time division multiple access (TDMA), and is referred to as the TDMA MSC 102. In the example of FIG. 1 , the MSCs 102, 104 are configured based on particular communication standards such as, for example IS-136, SS7, GSM, or other standards. The TDMA MSC 102 is in communication with a base station (BS) 108 and an antenna 110 that are configured to communicate with a mobile station 112 using an air interface 114. The TDMA MSC 102 is also in communication with a public switched telephone network 116 configured for communication with a landline telephone 118. In some examples, networks are configured for communication among landline telephones, mobile telephones and other mobile stations, fax machines, computer networks, laptop computers, personal digital assistants, handheld computers or other devices. The TDMA MSC 102 is in communication with a home location register (HLR) 122 that contains subscriber information for subscribers associated with a wireless network of which the TDMA MSC 102 is a part, and a visitor location register (VLR) 124 that contains information associated with network users who are registered on the network on a specific TDMA MSC such as the TDMA MSC 102. The TDMA MSC 102 is also in communication with a voice messaging (VMS) system 125 that is configured to receive and store messages such as messages that are directed to a network subscriber at times the subscriber is unavailable.
[0018] The GSM MSC 104 is in communication with a GSM prepaid (PPD) subscriber management system (GSM PPD) 130 and a GSM service control point (SCP) 132. The GSM PPD 130 and the SCP 132 can be implemented in a single network component 131 as shown in FIG. 1 , or in different systems, and can be situated at the same or different locations. The GSM PPD system 130 is configured to store subscriber information for prepaid network subscribers. Such subscriber information typically includes a current subscriber account balance, a renewal date/time at which the account balance is forfeited unless the subscriber updates the account balance, and other subscriber information. The GSM PPD system 130 also includes subscriber identifiers so that an account balance associated with a prepaid subscriber can be selected based on subscriber identifiers delivered by the TDMA MSC 102 to the GSM MSC 104. The SCP 132 is configured to deliver an authorization or a denial of service from the GSM PPD 130 to the TDMA MSC 102.
[0019] One example of communication using the network 100, the landline telephone initiates a call to the mobile station (MS) 112 that is associated with a prepaid subscriber. The call is directed to the TDMA MSC 102 that retrieves subscriber information from the HLR 122. Based on the retrieved subscriber information, the TDMA MSC 102 communicates with the GSM MSC 104 to obtain prepaid subscriber information, such as a call completion authorization, from the GSM PPD system 130. The PPD system 130 can be configured to grant or deny call completion authorization based on a user account balance, a call source, or a call billing rate. In addition, a network element can initiate a call timer so that depletion of the subscriber account balance can be tracked so that a connected call is not permitted to continue absent authorization of additional payment or addition of funds to the subscriber account balance. In addition, an authorization can be associated with a selected time interval after which authorization must be requested again. If the user does not answer, then the GSM PPD system 130 is informed of this condition and may or may not charge for the call depending on duration or other operator specified parameters. In some systems, call completion to a voice mail system is not billed against a user account balance, while in other systems voice mail call completion is billed.
[0020] The network 100 can be configured so that prepaid subscriber information is accessed upon call initiation by a prepaid subscriber and/or call completion to a prepaid subscriber. The MS 112 can be configured to communicate with the TDMA MSC 102 so that prepaid subscriber information is retrieved from the GSM PPD system 130 that is associated with the GSM MSC 104. The network 100 of FIG. 1 permits a prepaid subscriber management system configured for a particular network or communication standard to provide prepaid subscriber information for subscribers associated with networks that are configured according to other standards. Alternatively, prepaid subscriber information can be provided by a PPD system associated with a particular network or MSC, and retrieved by other networks or MSCs.
[0021] FIG. 2 illustrates processing of a call to a prepaid subscriber (SUB) 206 from, For example, a public switched telephone network (PSTN) 202. An incoming call request 204 from, for example, a landline telephone via the PSTN 202 to the prepaid Subscriber 206 is routed to a DMA MSC 208. The MSC 208 issues a locate request (LOCREQ) command 210 for the called number to a home location register (HTR) 212 that returns a value locreq associated with the called number in a communication 214. The value locreq includes destination information for the subscriber 206 as well as a prepaid identifier such as “000” to indicate that the called number is associated with a prepaid subscriber. If the called number is associated with postpaid services (such as, for example, a monthly subscriber), then the call is routed to the subscriber.
[0022] Prepaid subscribers are identified based on the value locreq based on, for example, the prepaid identifier “000” prepended to the called number. As shown in FIG. 2 , prepaid subscriber account information is not stored in the MSC 208 or the HLR 212, but is instead associated with a GSM network, or a network based on another network standard. The MSC 208 establishes a voice communication path 216 to a GSM MSC 218, and an Initial Detection Point (INIT_DP) message 222 is delivered to a GSM service control point (SCP) 220. The INIT_DP message 222 can be specified with reference to, for example, “Customized Applications for Mobile Network Enhanced Logic (CAMEL) Phase 4; CAMEL Application Part Specification (Release 5),” 3GPP TS 29.078 v 3.14.0 (2002-12), and typically includes address and other information related to call routing, such as, for example, a calling number (CNI, callingPartyNumber), a caller name, a called number (calledPartynumber), or other parameters. The SCP 220 communicates information based on the INIT_DP message 222 to a prepaid subscriber management system (PPD system) 224. The PPD system 224 is configured to store and process prepaid subscriber information, such as, for example, a current prepaid account balance, and based on the subscriber information, establishes if a call to the subscriber 206 is to be authorized. If sufficient funds are not available, then the PPD system returns a message indicating that the call is not authorized, and the call can be released.
[0023] For call destinations for which adequate funds are available, authorization messages 228, 230 are returned to the GSM SCP 220 and the GSM MSC 218, respectively. The GSM MSC 218 removes the prepaid identifier and directs a call 232 to the TDMA MSC 208. The TDMA MSC 208 issues a ring command 234 to a mobile station associated with the subscriber 206. The MSC 208 determines if the mobile station is busy or rings but does not answer (RNA) based on a communication 236. If the mobile station is busy or RNA, then a number transfer request (TRANUMREQ) 238 is directed to the HLR 212. Typically .the HLR 212 includes a call forwarding number (CFWN) associated with the subscriber 206 and a voice mail system (VMS) 240 that includes a subscriber voice mailbox. Based on the CFWN returned by the HLR 212, a voice channel 242 is established with the VMS 240 and a message for the subscriber 206 can be stored. As shown in FIG. 2 , the call request 204 is terminated in the VMS 240 and is billed to the prepaid subscriber based on a prepaid subscriber configuration stored in the PPD system 224. Upon call completion, or completion of message delivery to the TMDA VMS 240, a call duration or other billing-related information is returned to the PPD system 224 so that subscriber account balances can be updated.
[0024] With reference to FIG. 3 , a communication system 300 is configured to establish a voice channel to a prepaid subscriber and to terminate a call in a voice mail system, if the subscriber is unavailable, without billing the prepaid subscriber. An incoming call 304 from, for example, a PSTN 302 is directed to a TDMA MSC 308 that issues a location request (LOCREQ) 310 for destination information from a TDMA HLR 312. If the call destination is associated with prepaid service subscriber, then the HLR 312 returns a call destination information message 314 that includes a prepaid service identifier. In a representative example, the message 314 is based on a “000” identifier that is prepended to the called number. If the message does not contain the prepaid identifier, then the call is typically associated with a postpaid subscriber destination and can be completed without contacting a prepaid subscriber management system.
[0025] Calls associated with prepaid subscriber destinations are routed to a GSM MSC 318 that delivers a call destination information message to a service control point (SCP) 330 and a prepaid subscriber management system (PPD system) 334 in messages 322, 326, respectively. The PPD system 334 returns an authorization message 328 that includes the called number and a prepaid identifier to the SCP 330. Authorization information is delivered in a message 331 to the MSC 318 and in a voice channel 332 to the TDMA MSC 308. The GSM MSC 318 typically strips the prepaid identifier before delivering the call destination and authorization to the TDMA MSC 308. The TDMA MSC 308 then directs a message 334 to the prepaid subscriber 306 to indicate an incoming call. The prepaid subscriber 306 can be unavailable to answer the call, or the call destination can be busy. In some prepaid systems, calls that are not completed are not billed so that upon receiving a notification 336 that the destination is busy or does not answer, the TDMA MSC 308 again directs a message 338 to the TDMA HLR 308 that returns a message 340 that typically includes the prepaid identifier and a call forwarding number (CFWN). Based on the prepaid identifier, the TDMA MSC 308 communicates with the GSM MSC 318 over a voice channel 342, and messages 352, 356 are delivered to the SCP 330 and the PPD system 334, respectively. The PPD system 334 returns a message 358 authorizing call completion to a voicemail system, along with the prepaid identifier and the CFWN. Because call completion is reclassified as free, accumulation of charges using a billing clock is unnecessary. Call completion authorization is delivered to the TDMA MSC 308 over a voice channel 362. A voice channel 364 is then established for connection to a TDMA voice mail system 307. As a result, the incoming call is reclassified as a free call and a voice mail message is delivered to the TDMA VMS 307, without charging the prepaid subscriber for voice mail delivery. In some examples, the called number is not returned to the TDMA MSC 308 in the voice channel 362, and the caller is prompted to enter a mobile equipment identifier (MIN) associated with the voice mail destination.
[0026] FIG. 4 illustrates a method of calling a prepaid subscriber. In a step 402, a call is initiated and in a step 404 a home location register (HLR) associated with a subscriber's home network is queried. In a step 406, the subscriber type is evaluated to determine if the call destination is a prepaid destination. If the destination is not a prepaid destination, then the call is completed in a step 407. If the destination is a prepaid destination, then a prepaid network MSC is contacted in a step 408. Based on, for example, available billing credits, an account balance, a call source or call type, or other factors, a determination of whether to authorize call completion is performed at the prepaid network in a step 410. If the call is not authorized, then the call can be terminated in a step 411. Alternatively, delivery of a call indication can be selected in a step 413, so that a prepaid subscriber can be notified so that an account balance can be replenished and subsequent calls or the current call can be completed. After the account balance is selected for replenishment on a step 420, call authorization is again requested in the step 410. If the subscriber elects not to replenish his account, the call terminates in the step 411. If the call is authorized, then the call destination is contacted in a step 412. In a step 414, call status is evaluated to determine if the destination is busy or rings but does not answer (RNA). If the destination is busy, RNA, or is otherwise unavailable, the call can be directed to a voicemail system, with or without billing the prepaid subscriber for call completion to a voice mailbox. In a step 416, the prepaid network is contacted and in a step 418, the billing request is cancelled. In a step 420 the call to a busy or RNA destination is directed to a voice mail system. Typically the voice mail system is associated with the subscriber home network, and the home HLR is queried for information concerning contacting the voice mail system, such as, for example, a call forwarding number or a voice mailbox identifier. If the destination answers in the step 414, then the call is completed in a step 415.
[0027] In representative examples, a prepaid subscriber management system is included in a network based on a GSM standard, and an IS-136 or otherwise configured network provides prepaid services based on a GSM prepaid subscriber management system. In some examples, the GSM-based network is configured to communicate with additional GSM-based networks or other networks according to a Customized Applications for Mobile Network Enhanced Logic (CAMEL) signaling protocol. FIG. 5 is a schematic diagram of a communication system 500 that includes a home wireless network 501 and a prepaid management wireless network 503. The home wireless network 501 includes a home MSC 502, an HLR 522, and a voice messaging system 525. The prepaid management wireless network 503 is configured based on a GSM standard and includes a CAMEL processor 510 and a prepaid subscriber management system (PPD system) 530. The CAMEL processor 510 is configured for signaling between other GSM-based networks or networks based on other standards. The communication system 500 supports communications between, for example, a mobile station 512 associated with a prepaid subscriber and a landline telephone 518 using a public switched telephone network 516. The HLR 522 includes subscriber information that identifies prepaid subscribers so that the home MSC 502 communicates with the prepaid MSC 504 to obtain call authorization from the PPD system 530. Typically, authorization of call completion also starts a billing clock so that re-authorization is requested before a subscriber account balance is depleted. For calls that terminate in no charge destinations such as, for example, a voicemail system, a call to a busy destination or a des ton that does not answer can be returned to the PPD system 530 before (or after) the call is completed to voicemail so that such calls are not charged to the subscriber.
[0028] In a representative -example, prepaid subscriber information is stored in a prepaid system configured for communication with a GSM mobile switching center, but the associated call (or origin) destination is accessed via a TDMA mobile switching center. Other network configurations can be associated with a home network and a prepaid network. For example, the home network can be a GSM-based network while a prepaid subscriber management system is associated with a TDMA network In some examples, prepaid subscribers are billed for originating calls, receiving calls, call forwarding to voicemail, and/or call retrieval from voicemail. In other examples, services are provided to postpaid subscribers based on a credit limit established at a prepaid management system. These and other examples are illustrative. Many alternative examples will be apparent to those skilled in the art, and the described examples should not be taken as limiting in scope. Rather, we claim all that comes within the scope of the following claims and equivalents thereto.
Claims
The invention claimed is:
1. A method of providing prepaid services in a communication network, comprising:
directing a service request to a first mobile network;
associating the request with a prepaid subscriber based on a subscriber profile stored in the first mobile network by combining a prepaid identifier with a subscriber number used to establish a wireless communication link between the first mobile network and a wireless communication device of the prepaid subscriber;
transmitting the combined subscriber number and prepaid identifier to a second mobile network to thereby request a service authorization for the requested service from the second mobile network; and
receiving the service authorization from the second mobile network.
2. The method of claim 1 wherein the first mobile network and the second mobile network are configured to conform to a first network protocol and a second network protocol, respectively.
3. The method of claim 2 wherein the first network protocol and the second network protocol are different.
4. The method of claim 1 wherein the subscriber number is a functional telephone number that, when combined with the prepaid identifier becomes a non-functional number provided to the second mobile network, the method further comprising uncombining the prepaid subscriber identifier data and the subscriber number to thereby render the subscriber number functional if service to the subscriber is authorized by the second mobile network.
5. The method of claim 4 wherein the prepaid identifier and a mobile identification number are provided to the second mobile network.
6. The method of claim 5 wherein the prepaid identifier is prepended to the mobile identification number, and the combination is provided to the second mobile network.
7. The method of claim 4, further comprising authorizing the requested service based on a prepaid subscriber account balance stored in the second mobile network.
8. The method of claim 7, further comprising: determining a service completion status for the authorized service; and delivering the service completion status to a prepaid system.
9. The method of claim 8, further comprising assessing a service charge to the prepaid subscriber account balance based on the service completion status.
10. The method of claim 9 wherein the service charge is not assessed to the prepaid subscriber account balance if the service request is directed to voice mail.
11. The method of claim 9 wherein the service charge is not assessed to the prepaid subscriber account balance if the requested service is not completed.
12. The method of claim 4, further comprising verifying that a prepaid subscriber account balance is insufficient for service authorization, and contacting the prepaid subscriber to request account balance replenishment.
13. A network element, comprising:
an input configured to receive a service destination identifier combined with a prepaid identifier, the service destination identifier being a functional service destination identifier that is rendered non-functional when combined with the prepaid identifier;
a prepaid database configured to store prepaid account data associated with the service destination identifier;
a processor configured to interrogate the prepaid database based on receipt of the prepaid identifier, and to authorize providing a requested service based on prepaid account data associated with a service destination; and
uncombining the service destination identifier and the prepaid identifier to thereby render the service destination identifier functional if the requested service is authorized.
14. The network element of claim 13 wherein the input is configured to communicate with a public switched telephone network.
15. The network element of claim 13 wherein the processor is configured to receive the prepaid identifier prepended to the service destination identifier and associate the requested service with a prepaid subscriber based on the prepended prepaid identifier.
16. The network element of claim 13, further comprising a service duration timer wherein the processor is configured to initiate the service duration timer, and a call completion authorization is configured to expire after a selected service duration.
17. A method of providing a communication service to a prepaid subscriber, comprising:
receiving a call request at a first network;
identifying the call request associated with the prepaid subscriber;
combining prepaid subscriber identifier data and a subscriber identifier;
directing a request for prepaid subscriber account information from the first network to a second network, the request including the combined prepaid subscriber identifier data and the subscriber identifier; and
selectively authorizing call completion based on prepaid subscriber account information stored in the second network.
18. The method of claim 17 wherein combining the prepaid subscriber identifier data with the subscriber identifier comprises combining the prepaid subscriber identifier data with a destination identifier.
19. The method of claim 17 wherein the call request is associated with the prepaid subscriber based on a prepaid identifier.
20. The method of claim 19 wherein the prepaid identifier is prepended to a service destination identifier associated with a call access location.
21. The method of claim 20 wherein the service destination identifier is associated with a call destination.
22. The method of claim 20 wherein the service destination identifier is associated with a call source.
23. The method of claim 17 wherein combining the prepaid subscriber identifier data with the subscriber identifier comprises combining the prepaid subscriber identifier data with a source identifier.
24. The method of claim 17 wherein the request for prepaid subscriber account information is directed to the second network via a public switched telephone network.
25. The method of claim 17, further comprising assessing a service charge to a prepaid subscriber account balance.
26. A method of providing a communication service to a prepaid subscriber, comprising:
receiving a call request at a first network;
associating the call request with a prepaid account;
in response to the call request, transmitting a subscriber identifier and a prepaid identifier to a second mobile network to thereby request a service authorization from the second network; and
forwarding a call completion authorization into the first network based on prepaid account information stored in the second network.
Patent Citations (149)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5123111(A) | 1992-06-01 | Delory et al. | Applicant |
| US5353335(A) | 1994-10-01 | D'Urso et al. | Applicant |
| US5355406(A) | 1994-10-01 | Chencinski et al. | Applicant |
| US5488650(A) | 1996-01-01 | Greco et al. | Applicant |
| US5493608(A) | 1996-02-01 | O'Sullivan | Applicant |
| US5511114(A) | 1996-04-01 | Stimson et al. | Applicant |
| US5537594(A) | 1996-07-01 | Shannon et al. | Applicant |
| US5592535(A) | 1997-01-01 | Klotz | Applicant |
| US5722067(A) | 1998-02-01 | Fougnies et al. | Applicant |
| US5737393(A) | 1998-04-01 | Wolf | Applicant |
| US5737701(A) | 1998-04-01 | Rosenthal et al. | Applicant |
| US5771276(A) | 1998-06-01 | Wolf | Applicant |
| US5867570(A) | 1999-02-01 | Bargout et al. | Applicant |
| US5946380(A) | 1999-08-01 | Cohen et al. | Applicant |
| US5991407(A) | 1999-11-01 | Murto | Applicant |
| US5995822(A) | 1999-11-01 | Smith et al. | Applicant |
| US6014428(A) | 2000-01-01 | Wolf | Applicant |
| US6018652(A) | 2000-01-01 | Frager et al. | Applicant |
| US6037880(A) | 2000-03-01 | Manion | Applicant |
| US6058300(A) | 2000-05-01 | Hanson | Applicant |
| US6061433(A) | 2000-05-01 | Polcyn et al. | Applicant |
| US6070067(A) | 2000-05-01 | Nguyen et al. | Applicant |
| US6075855(A) | 2000-06-01 | Christiansen et al. | Applicant |
| US6075982(A) | 2000-06-01 | Donovan et al. | Examiner |
| US6122510(A) | 2000-09-01 | Granberg | Applicant |
| US6144847(A) | 2000-11-01 | Altschul et al. | Applicant |
| US6144938(A) | 2000-11-01 | Surace et al. | Applicant |
| US6157823(A) | 2000-12-01 | Fougnies et al. | Applicant |
| US6169975(B1) | 2001-01-01 | White et al. | Applicant |
| US6181785(B1) | 2001-01-01 | Adams et al. | Applicant |
| US6185414(B1) | 2001-02-01 | Brunner et al. | Applicant |
| US6185545(B1) | 2001-02-01 | Resnick et al. | Applicant |
| US6188752(B1) | 2001-02-01 | Lesley | Applicant |
| US6205326(B1) | 2001-03-01 | Tell et al. | Applicant |
| US6236851(B1) | 2001-05-01 | Fougnies et al. | Applicant |
| US6240284(B1) | 2001-05-01 | Bugnon et al. | Applicant |
| US6253072(B1) | 2001-06-01 | Verdonk | Applicant |
| US6256504(B1) | 2001-07-01 | Tell et al. | Applicant |
| US6327363(B1) | 2001-12-01 | Henderson et al. | Applicant |
| US6373930(B1) | 2002-04-01 | McConnell et al. | Applicant |
| US6377938(B1) | 2002-04-01 | Block et al. | Applicant |
| US6393269(B1) | 2002-05-01 | Hartmaier et al. | Applicant |
| US6397055(B1) | 2002-05-01 | McHenry et al. | Applicant |
| US6404880(B1) | 2002-06-01 | Stevens | Applicant |
| US6411803(B1) | 2002-06-01 | Malackowski et al. | Applicant |
| US6424706(B1) | 2002-07-01 | Katz et al. | Applicant |
| US6424840(B1) | 2002-07-01 | Fitch et al. | Applicant |
| US6434126(B1) | 2002-08-01 | Park | Applicant |
| US6463130(B1) | 2002-10-01 | Malik | Applicant |
| US6480710(B1) | 2002-11-01 | Laybourn et al. | Applicant |
| US6487277(B2) | 2002-11-01 | Beyda et al. | Applicant |
| US6487401(B2) | 2002-11-01 | Suryanarayana et al. | Applicant |
| US6490450(B1) | 2002-12-01 | Batni et al. | Applicant |
| US6493547(B1) | 2002-12-01 | Raith | Applicant |
| US6496690(B1) | 2002-12-01 | Cobo et al. | Applicant |
| US6496691(B1) | 2002-12-01 | Easley et al. | Applicant |
| US6507644(B1) | 2003-01-01 | Henderson et al. | Applicant |
| US6516190(B1) | 2003-02-01 | Linkola | Applicant |
| US6526273(B1) | 2003-02-01 | Link, II et al. | Applicant |
| US6542601(B1) | 2003-04-01 | Hernandez et al. | Applicant |
| US6594484(B1) | 2003-07-01 | Hitchings, Jr. | Applicant |
| US6625439(B2) | 2003-09-01 | Laybourn et al. | Applicant |
| US6671506(B1) | 2003-12-01 | Lee | Applicant |
| US6671523(B1) | 2003-12-01 | Niepel et al. | Applicant |
| US6684072(B1) | 2004-01-01 | Anvekar et al. | Applicant |
| US6705520(B1) | 2004-03-01 | Pitroda et al. | Applicant |
| US6728353(B1) | 2004-04-01 | Espejo et al. | Applicant |
| US6741687(B1) | 2004-05-01 | Coppage | Applicant |
| US6748066(B1) | 2004-06-01 | Espejo et al. | Applicant |
| US6771950(B1) | 2004-08-01 | Shupe et al. | Applicant |
| US6904035(B2) | 2005-06-01 | Requena | Applicant |
| US6912383(B1) | 2005-06-01 | Li et al. | Applicant |
| US6917798(B1) | 2005-07-01 | Hake et al. | Examiner |
| US6934529(B2) | 2005-08-01 | Bagoren et al. | Applicant |
| US6950876(B2) | 2005-09-01 | Bright et al. | Applicant |
| US6987969(B1) | 2006-01-01 | Brunig et al. | Applicant |
| US7050811(B2) | 2006-05-01 | Grech et al. | Applicant |
| US7088987(B1) | 2006-08-01 | Espejo et al. | Applicant |
| US7184748(B2) | 2007-02-01 | Espejo et al. | Applicant |
| US7209890(B1) | 2007-04-01 | Peon et al. | Applicant |
| US7215942(B1) | 2007-05-01 | McQuaide, Jr. et al. | Applicant |
| US7231201(B2) | 2007-06-01 | Espejo et al. | Applicant |
| US7330110(B1) | 2008-02-01 | Heintzman et al. | Applicant |
| US7463889(B1) | 2008-12-01 | DiPrima et al. | Applicant |
| US7466806(B2) | 2008-12-01 | Espejo et al. | Applicant |
| US7480710(B1) | 2009-01-01 | Olson et al. | Applicant |
| US7529538(B2) | 2009-05-01 | Espejo et al. | Applicant |
| US7539629(B1) | 2009-05-01 | Peon et al. | Applicant |
| US7653377(B1) | 2010-01-01 | Espejo et al. | Applicant |
| US7706792(B1) | 2010-04-01 | DiPrima et al. | Applicant |
| US2001/0001321(A1) | 2001-05-01 | Resnick et al. | Applicant |
| US2001/0028705(A1) | 2001-10-01 | Adams et al. | Applicant |
| US2001/0049656(A1) | 2001-12-01 | Halkosaari et al. | Applicant |
| US2002/0029189(A1) | 2002-03-01 | Titus et al. | Applicant |
| US2002/0077829(A1) | 2002-06-01 | Brennan et al. | Applicant |
| US2002/0091572(A1) | 2002-07-01 | Anderson et al. | Applicant |
| US2002/0104090(A1) | 2002-08-01 | Stettner | Applicant |
| US2002/0107007(A1) | 2002-08-01 | Gerson | Applicant |
| US2002/0107738(A1) | 2002-08-01 | Beach et al. | Applicant |
| US2002/0115424(A1) | 2002-08-01 | Bagoren et al. | Applicant |
| US2002/0143634(A1) | 2002-10-01 | Kumar et al. | Applicant |
| US2002/0156683(A1) | 2002-10-01 | Stoutenburg et al. | Applicant |
| US2002/0181710(A1) | 2002-12-01 | Adam et al. | Applicant |
| US2002/0193093(A1) | 2002-12-01 | Henrikson et al. | Applicant |
| US2002/0193100(A1) | 2002-12-01 | Riffe et al. | Applicant |
| US2003/0002635(A1) | 2003-01-01 | Koch et al. | Applicant |
| US2003/0026404(A1) | 2003-02-01 | Joyce et al. | Applicant |
| US2003/0037176(A1) | 2003-02-01 | Dannehr et al. | Applicant |
| US2003/0095566(A1) | 2003-05-01 | Bunting et al. | Applicant |
| US2003/0119477(A1) | 2003-06-01 | Uppal et al. | Applicant |
| US2003/0125042(A1) | 2003-07-01 | Olrik et al. | Applicant |
| US2003/0126020(A1) | 2003-07-01 | Smith et al. | Applicant |
| US2003/0143978(A1) | 2003-07-01 | Cooper | Applicant |
| US2003/0157925(A1) | 2003-08-01 | Sorber et al. | Applicant |
| US2003/0158960(A1) | 2003-08-01 | Engberg | Applicant |
| US2004/0063423(A1) | 2004-04-01 | Kagay, Jr. | Applicant |
| US2004/0097229(A1) | 2004-05-01 | Muhonen et al. | Applicant |
| US2004/0103191(A1) | 2004-05-01 | Larsson | Applicant |
| US2004/0132449(A1) | 2004-07-01 | Kowarsch | Applicant |
| US2004/0228457(A1) | 2004-11-01 | Espejo et al. | Applicant |
| US2005/0009499(A1) | 2005-01-01 | Koster | Applicant |
| US2005/0075106(A1) | 2005-04-01 | Jiang | Applicant |
| US2005/0101292(A1) | 2005-05-01 | Fukui | Applicant |
| US2005/0148319(A1) | 2005-07-01 | Himeno | Applicant |
| US2005/0164707(A1) | 2005-07-01 | Batni et al. | Applicant |
| US2005/0262355(A1) | 2005-11-01 | Banet et al. | Applicant |
| US2006/0003766(A1) | 2006-01-01 | Parameswar et al. | Applicant |
| US2006/0023856(A1) | 2006-02-01 | Welton | Applicant |
| US2006/0058010(A1) | 2006-03-01 | Williams et al. | Applicant |
| US2006/0058049(A1) | 2006-03-01 | McLaughlin et al. | Applicant |
| US2006/0240820(A1) | 2006-10-01 | Jiang | Applicant |
| US2006/0240822(A1) | 2006-10-01 | Jiang | Applicant |
| US2007/0049247(A1) | 2007-03-01 | Espejo et al. | Applicant |
| US2007/0106569(A1) | 2007-05-01 | McQuaide et al. | Applicant |
| US2007/0205263(A1) | 2007-09-01 | Peon et al. | Applicant |
| US2008/0119162(A1) | 2008-05-01 | Sivalingam et al. | Applicant |
| US2008/0299967(A1) | 2008-12-01 | Kazmi | Applicant |
| US2008/0318545(A1) | 2008-12-01 | Kazmi | Applicant |
| US2009/0029673(A1) | 2009-01-01 | Hamadi et al. | Applicant |
| US2009/0061815(A1) | 2009-03-01 | Myers et al. | Applicant |
| US2009/0061818(A1) | 2009-03-01 | Myers et al. | Applicant |
| US2009/0061856(A1) | 2009-03-01 | Kazmi et al. | Applicant |
| US2009/0061857(A1) | 2009-03-01 | Kazmi | Applicant |
| US2009/0061868(A1) | 2009-03-01 | Kazmi | Applicant |
| US2009/0081988(A1) | 2009-03-01 | Kazmi | Applicant |
| US2009/0234747(A1) | 2009-09-01 | Peon et al. | Applicant |
| US2010/0105369(A1) | 2010-04-01 | DiPrima et al. | Applicant |
| EP1372089 | 2003-12-01 | Applicant | |
| WO9216078 | 1992-09-01 | Applicant |
Non-Patent Literature (17)
- “3rd Generation Partnership Project; Technical Specification Group Core Network; Customised Applications for Mobile Network Enhanced Logic (CAMEL) Phase 4; CAMEL Application Part (CAP) specification (Release 5)”, 3GPP TS 29.078 5.0.0 (Jun. 2002).Applicant
- 3GPP TS 02.78 v7.2.0 (Dec. 2001) Technical Specification, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; (CAMEL); Service definition / State 1 (Release 1998),”GSM® Global System for Mobile Communications, 34 pages.Applicant
- Cloward, William H., “Sophisticated, High Speech Capacity Voice Response Application for End Users,” Official Proceedings of Speech Tech '86, Media Dimensions, Inc., Apr. 30, 1986, pp. 58/61.Applicant
- Crowe, David, “Thirsty for new features? Get a CAMEL?”, Cellular Networking Perspectives, David Crowe's Wireless Review Magazine Articles Protocols Section: Mar. 2001, 5 pages, retrieved Nov. 17, 2004 from URL: http://www.cnp/wireless.com/ArticleArchive/Wireless%20Review/200103%2OCAMEL.html.Applicant
- Ghadialy, Zahid, “CAMEL: An Introduction,” Jul. 25, 2004, 11 pages, URL: <http://www.3g4g.co.uk/Tutorial/Zg/zg—camel.html>.Applicant
- How does PayPal Auto-Recharge Work?, Skype Help, http://support.skype.com/index.php?—a=knowledgebase&— j=questiondetails&—i=1044, printed Aug. 28, 2007, 1 page.Applicant
- International Search Report and Written Opinion mailed Feb. 9, 2009 for App. PCT/US2008/056385, 12 pages.Applicant
- ITU/T Recommendation Q.762, “Signalling System No. 7—ISDN User Part general functions of messages and signals,” International Telecommunications Union, Dec. 1999, 30 pages, URL: <https://staff.hti.bfh.ch/mdm1/Kursunterlagen/SS7/T/REC/Q.762.pdf>.Applicant
- ITU/T Recommendation Q.763, “Signalling System No. 7—ISDN User Part formats and codes,” International Telecommunications Union, Dec. 1999, 134 pages, URL: <https://staff.hti.bfh.ch/mdm1/Kursunterlagen/SS7/T/REC/Q.763.pdf>.Applicant
- Joe Gadget, Purchase Coca Cola Using Your Cellphone in Japan, http://http://www.techfresh.net/gadgets/misc-gadgets/purchase-coca-cola-using-cellphone-in-japan/, Sep. 29, 2006, 5 pages.Applicant
- Kislak, Ali, “‘CAMEL,’ ‘Customised Applications for Mobile network Enhanced Logic,’” CAMEL & IN, Demo Version 1.0, Jan. 19, 2002, 18 pages, retrieved Nov. 17, 2004 from URL: http://www.hotel/fiesta.com/4g/aliweb/MyDOCS/CAMELMExEin/CAMELin.htm.Applicant
- Levy, Ira D., “Keeping the bells ringing: Account replenishment in near real time”, TMA Journal, v19n2, Mar./Apr. 1999, p. 24/26.Applicant
- Meskauskas, Paulius, “Customised Applications for Mobile Enhanced Logic (CAMEL),” Research Seminar on Nomadic Computing, University of Helsinki, 1999, 13 pages.Applicant
- Moshavi, Sharon, “Please Deposit No Cents,” Forbes, Aug. 16, 1993, 1 page.Applicant
- Mouly, Michel and Pautet, Marie/Bernadette, “The GSM System,” France, 1992, pp. 569/577.Applicant
- Smith, David G., “An Introduction to GSM Enhancements for Operator Specific Services (CAMEL),” 1996, IEEE, Savoy Place, London, 9 pages.Applicant
- Skype Help, “What is Auto credit and how do I use it?,” http://support.skype.com/index.php?—a=knowledgebase&—j=questiondetails&—i=633, printed Aug. 28, 2007, 1 page.Applicant