HK1087855A - Method and apparatus providing user with account balance notification - Google Patents

Description

Method and apparatus for providing prepaid wireless packet data service account balance notification to a subscriber

Technical Field

The present invention relates generally to prepaid wireless packet data services. More particularly, the present invention relates to various embodiments of apparatus and methods for providing balance notifications to a user relating to their prepaid wireless packet data account.

Technical Field

Prepaid wireless voice communication services have been directed to consumers for some time. Typically, the subscriber prepays for future voice calls made through the subscriber's wireless telephone. The subscriber spends his prepaid funds as he makes a wireless voice call using the network.

Wireless communication networks have been modified for some time to enable the relaying of wireless packet data services, i.e., electronic communications such as e-mail, web browsing, and other non-voice related services. For CDMA-2000 networks, prepaid wireless packet data services with added functionality, similar to traditional prepaid voice services, have been recently proposed. In this regard, one proposed standard for prepaid wireless packet data services IS the "CDMA 2000 Wireless IP network Standard," known as the Telecommunications Industry Association (TIA) IS-835-C. The fifth chapter on prepaid services is attached here as an appendix. Other references mention the use of prepaid packet data services in other network types, such as U.S. patent No. 6,496,690 for General Packet Radio Service (GPRS) networks. The entire contents of this patent are incorporated herein by reference.

In the case of the art described in these and other references, when a user pays to establish an account balance, it is allowed to use packet data services until the account balance reaches zero. When the account balance reaches zero, the network disconnects service until the user recharges the prepaid account balance. This is frustrating from a user's standpoint because there is no reliable reminder or other indication of an impending service disruption.

Disclosure of Invention

The present invention relates to a method and apparatus for providing a subscriber with account balance notification in a wireless packet data network regarding a prepaid wireless packet data service. The network detects the occurrence of a predetermined trigger event. In response to the occurrence of any of these predetermined triggering events associated with a prepaid wireless packet data subscriber station, the network issues a balance notification to the subscriber station.

In one embodiment, some exemplary predetermined triggering events include: the account balance of the subscriber station falls below a network-specified threshold, the account balance of the subscriber station falls below a subscriber-specified threshold, an account balance query from the subscriber station is received, an account balance query, an account balance recharge, and/or a specified time of arrival is received from the prepaid customer. The balance notification may be sent in a variety of ways, such as using network-architecture-specific (NAS) signaling, using Short Message Service (SMS), or using application/Internet Protocol (IP) communications.

Brief Description of Drawings

Fig. 1A is a block diagram of some of the hardware components and interconnections in a wireless packet data network.

Fig. 1B is a detailed block diagram showing some of the packet data-related hardware components and interconnections, particularly for CDMA-2000.

FIG. 2 is a block diagram of an exemplary digital data processing machine.

Fig. 3 is a plan view of an exemplary signal-bearing medium.

Fig. 4 is a flow chart illustrating an overall sequence of operating a wireless packet data network to provide prepaid packet data service balance notification.

Fig. 5 is a more detailed flow chart illustrating a sequence for providing balance notification using NAS signaling.

Fig. 6 is a more detailed flow chart illustrating a sequence for providing a balance notification using the Short Message Service (SMS) protocol.

Fig. 7 is a detailed flowchart showing a sequence of providing a balance notification using application/IP communication.

Figure 8 is a more detailed flow chart showing the sequence of submitting a balance query with a NAS signaling subscriber station.

Fig. 9 is a more detailed flow chart showing the sequence of a balance query submitted by a subscriber station using the SMS protocol.

Fig. 10 is a more detailed flow chart showing a sequence of submitting a balance query using an application/IP communication subscriber station.

Detailed Description

The nature, objectives, and advantages of the invention will become apparent to those skilled in the art from the following detailed description when taken in conjunction with the accompanying drawings.

Hardware components and interconnects

Introduction to the design reside in

As described above, the present disclosure is directed to various embodiments of apparatuses and methods for providing balance notifications to subscribers regarding their prepaid wireless packet data service accounts. The present disclosure is illustrated in the context of an exemplary wireless packet data network that includes a number of components as described below. FIG. 1A-network overview

Fig. 1A shows a highly simplified model of an exemplary wireless packet data network 100. The network includes useful features, such as enabling mobile stations to receive e-mail, browse the internet, and exchange other such "packet data". In this regard, wireless packet data network 100 may include TIA standard IS-835 features. Additionally, network 100 may conduct wireless voice calls in accordance with TIA standards IS-95/IS-2000, many variations and modifications known in the art. The IS-95 standard utilizes Code Division Multiple Access (CDMA) modulation techniques for wireless voice calls (wireless communication calls), and has greater capacity and greater performance than earlier wireless communication techniques.

Although specific embodiments of IS-95/IS-2000 (for voice calls) and IS-835-B/C (for packet data) are used to illustrate one embodiment in detail, those of ordinary skill in the art will recognize, with the benefit of this disclosure, that many of the principles of this disclosure may also be applied to other wireless networks, such as W-CDMA, GSM, GPRS, and so forth.

Network 100 includes a plurality of mobile stations, such as 114, which comprise CDMA-compatible wireless telephones, which may also be referred to as "access terminals" or "subscriber stations. The mobile station IS capable of transmitting and receiving packet data and, more particularly, packet data whose service has been prepaid as described in IS-835-C. The mobile station IS also capable of making voice calls by transmitting and receiving IS-95 type voice information. Some exemplary mobile stations include mobile telephones, Personal Communication Systems (PCS) devices, or other wireless subscriber devices, such as Fixed Wireless Terminals (FWTs).

Mobile stations 114 are served by a plurality of base stations 110, and base stations 110 exchange voice and/or packet data content with mobile stations 114. In a wireless voice telephone environment, telephone calls and other voice communications are conducted by exchanging data between mobile stations 114 and base stations 110 via Radio Frequency (RF) electromagnetic signal channels, such as 112 a. Base station 110 may also exchange other types of information with mobile station 114, such as call paging messages, origination messages, registration messages, pilot signal reports, and other digital data. For packet data, these communications are conducted by exchanging Internet Protocol (IP) packet data between the mobile station 114 and the base station 110 for relaying the internet 101 or some other packet data network (not shown), such as an enterprise communication network. Examples of packet data include Internet Protocol (IP) datagrams used for applications such as accessing web pages, retrieving e-mail, etc. These applications of packet data may run directly on mobile station 114 or may run on a separate computer device that uses mobile station 114 as a wireless modem. In a packet data environment, IP packet data is communicated between mobile station 114 and base station 110 via an RF electromagnetic signal channel, such as 112 b.

Some or all of the base stations 110 may be implemented using hardware as is currently used in conventional base stations in commercial use. Each base station 110 is coupled to a Base Station Controller (BSC)106, each of which conducts bidirectional information flow (described below) between the base station 110 and the plurality of network facilities 104. BSC 106 performs a number of functions to enable mobile communications to occur, including coordinating (organizing) handoffs of mobile stations 114 between base stations. For use in processing packet data, the BSC includes a Packet Control Function (PCF) module to facilitate the exchange of IP data packets with the network infrastructure 104. For example, each BSC 106 may be implemented using hardware as used in conventional wireless networks in current commercial use.

As described above, the BSC 106 conducts information between the base station 110 and the network infrastructure 104. The network infrastructure 104 may include components such as Packet Data Switching Nodes (PDSNs), Mobile Switching Centers (MSCs), Mobile Telephone Switching Offices (MTSOs), and the like. As is known in the art, the PDSN function is to extract IP packets received over a PPP connection with the mobile station and transmit the IP packets to the appropriate internet receiving station; in the opposite direction, the PDSN also performs additional functions. One function of the MSC is to relay voice stream information between the BSC 106 and the Public Switched Telephone Network (PSTN) 105. The MSC also provides mobility control, call processing, and call routing functionality. The MSC may also select routing of calls to and from other MSCs within and/or outside of network 100.

For use in processing packet data, the network infrastructure 104 may include one or more foreign agents. In a mobile IP embodiment, the network infrastructure 104 exchanges IP data between the BSC 106 and one or more home agents 102 over one or more links 103, such as wireless or wired T1 or T3 links, fiber optic connections, ethernet, or other Internet Protocol (IP) connections. The home agent 102 is in turn coupled to the internet 101 or any other IP network.

FIG. 1B-packet data and prepaid service components

Fig. 1B shows some of the packet data related components of fig. 1A in greater detail. In network 120, mobile station 114 is operatively coupled to base station 123, which communicates with mobile station 114 using an RF electromagnetic over-the-air (OTA) link. The structure and operation of the base station is known in the relevant art (except, of course, for any unique features introduced by this disclosure). BSC 121 and PCF 124 communicate between base station 123 and PDSN 126. In general, the BSC 121 functions to reassemble and check the integrity of the Radio Link Packet (RLP) data arriving from the mobile station via a base station, such as 123, as is known in the art. PCF 124 obtains data from BSC 121 in one format (the so-called "A8" format) and places the data in another format (the so-called "a 10" format) for delivery of packet data to/from PDSN 126. BSC 121 and PCF 124 also perform supplementary functions in the reverse direction, i.e., toward mobile station 114. More specifically, interface 121a between PCF 124 and PDSN126 may carry R-P (RN-PDSN) protocol data, and interface 121a is illustrated by the A10 or A11 Interfaces defined in 2002, 5 months, A.S0011-7-0v2.0, Interoperability Specification (IOS) for cdma2000 Access Network Interfaces, part 7(A10 and A11 Interfaces). In an implementation implementing SMS, BSC 121 may also be coupled to MSC132 through interface 121a for use in relaying SMS data, as described in detail below. The structure and operation of BSCs and PCFs are known in the relevant art (except, of course, for any unique features introduced by this disclosure).

PDSN126 functions to relay packet data communications between PCF 124 and the internet 149 or other destination coupled to IP network 138, such as home agent 148 in a mobile IP architecture. These communications are conducted through IS-835 defined Pi (PDSN-Internet) interface 126 a. PDSN126 also communicates with a visited authentication, authorization, accounting (AAA) server 134 for reasons described below. Connectivity with the visited AAA server 134 also occurs over a Pi-type interface. The visited AAA server 134 communicates using RADIUS, DIAMETER, or other AAA protocols. The structure and operation of a PDSN is known in the relevant art (except, of course, for any unique features introduced by this disclosure).

MSC132 is a component that routes incoming voice telephone calls from the Public Switched Telephone Network (PSTN), not shown, to the appropriate base station for transmission to the correct mobile station. MSC132 also controls the routing of calls in the reverse direction, i.e., from the originating mobile station to the PSTN through one or more base stations. In addition, MSC132 may direct in-network calls between mobile station units via appropriate base stations. The structure and operation of an MSC is known in the relevant art (except, of course, for any unique features introduced by this disclosure).

A plurality of local components 143 are also shown. By "local" is meant the local network of the service provider to which the user belongs. The home network includes the user's home AAA server 144, a prepaid server (PPS)146, and (sometimes) a home agent 148. Local component 143 may also include many other components, such as a Home Location Register (HLR), and other components not necessarily shown here for purposes of this disclosure.

The home AAA server 144 performs AAA functions for the mobile station, e.g., as described in the IS-835 standard. The local AAA server 144 may comprise, for example, a RADIUS server, as described in Internet Engineering Task Force (IETF) request for comments (RFC) 2138. Accordingly, the structure and operation of AAA entities are known in the relevant art (with the exception of, of course, any unique features introduced by this disclosure). The home AAA server 144 is coupled to the IP network 138 by connection 144 a.

Another component of network 120 is a prepaid server (PPS)146, which is a software, firmware, and/or hardware component that may be a subcomponent of home AAA server 144 or a single component connected through home AAA server 144 via an appropriate software and/or hardware interface 146 b. Thus, the PPS146 itself may be coupled to the IP network 138, as shown, through 146a, or by means of a PPS to local AAA connection utilizing network connection 144 a. The PPS146 performs various AAA functions related to prepaid packet data services including prepaid authorization procedures for subscribers defined as prepaid subscribers. In general, the PPS146 monitors, updates, and outputs information regarding the identity and condition of the prepaid packet data service account. The authorization procedure includes checking prepaid billing capabilities, checking account balances and conditions, returning prepaid billing capabilities to a "prepaid client" (described below) to indicate whether prepaid service is available, and so on. Some information about the known functionality of the PPS IS available in the IS-835-C standard. Other functions specific to the present disclosure will be described herein.

The home agent 148 is utilized under a "mobile IP" implementation of the network 120. The structure and operation of a home agent is known in the relevant art (except, of course, for any unique features introduced by this disclosure). The home agent 148 provides the mobile station 114 with an IP address ("home address") to transmit and receive information from the internet 149. This takes into account the capabilities of the mobile station, by virtue of its mobility, to move within the network 120 or even into other networks, and to receive the same IP address, regardless of the local topology of the visited network. Thus, the home agent 148 acts as a gateway between mobile stations, such as 114, and the Internet 149.

This is accomplished, at least in part, by the home agent 148 performing tunneling, i.e., receiving IP packets from the internet 149 to which the mobile station's home address is directed and tunneling/encapsulating the packets to a foreign agent serving the mobile station in the visited network. The foreign agent in turn decapsulates and forwards the packets to the appropriate mobile station. The foreign agent and home agent may also optionally perform tunneling in the reverse direction (i.e., from the foreign agent to the home agent). The tunneling and exact nature of the home agent 148 in the packet data service network is described in a number of publications that can be accessed by one of ordinary skill in the relevant art.

Optionally, the present disclosure also contemplates network 120 without home agent 148. This configuration is referred to as "simple IP". In this case, the mobile station is assigned a new IP address, and the mobile station's connection to the internet is at least momentarily interrupted each time it makes a handoff to the base station served by the new PDSN. In this configuration, PDSN126 forwards packets from the internet 149 to the current IP address of mobile station 114.

The visited AAA server 134 includes a local database to cache various data of the home AAA server 144 to provide local AAA services in cooperation with the home AAA server 144. In general, the visited AAA server 134 provides AAA functionality for mobiles requesting packet data services while outside of its home. Thus, the visited AAA server 134 authorizes, authenticates, and performs accounting functions for the visited mobile station by working with the home AAA server 144. When the mobile station is in the home network, only the home AAA server serves the mobile station. The visited AAA server 134 may be implemented by, for example, a RADIUS server.

Network 120 may additionally include one or more Domain Name Servers (DNS), such as DNS 150. Although a plurality of DNS units may be provided, for convenience and clarity of illustration, fig. 1B shows one DNS 150. DNS 150 may be coupled to IP network 138, a portion of Internet 149, or may be located in any other suitable location. DNS 150 provides domain name services, for example, as described in "internet with TCP/IP volume, Principles, Protocols, and Architecture" by Douglas e.corner. Those skilled in the relevant art are familiar with the services provided by domain name servers.

Network 120 also includes a Short Message Service (SMS) device 133. The SMS device 133 may include, for example, an information center (MC) to store and forward short messages, and may also optionally provide supplementary services related to SMS. The SMS device 133 may also include other SMS related components such as a Short Message Entity (SME) to compose/break up short messages, etc. SMS device 133 is coupled to many other components of network 120, including at least MSC132 and home AAA server 144 for purposes of this disclosure. The structure, interconnection, and use of SMS devices are known to those of ordinary skill in the art (except, of course, for any particular features described in this disclosure).

Exemplary digital data processing apparatus

The data processing entities, such as the components of FIGS. 1A-1B, or any one or more sub-components thereof, may be implemented in various forms. One embodiment is a digital data processing apparatus, as illustrated by the hardware components and interconnections of digital data processing apparatus 200 of FIG. 2.

The apparatus 200 includes a processor 202, such as a microprocessor, personal computer, workstation, controller, microcontroller, state machine, or other processor, coupled to a memory 204. In the present embodiment, the memory 204 includes a fast access memory 206, and a non-volatile memory 208. The fast access memory 206 may include Random Access Memory (RAM) and may be used to store programming instructions that are executable by the processor 202. The non-volatile memory 208 may comprise, for example, battery backed-up RAM, EEPROM, flash PROM, one or more magnetic data storage disks such as a "hard drive," a tape drive, or any suitable storage device. The apparatus 200 also includes an input/output 210 such as a line, bus, cable, electromagnetic link, or other means for the processor 202 to exchange data with other hardware external to the apparatus 200.

Although specifically described above, those of ordinary skill in the art, upon reading this disclosure, will recognize that the apparatus described above may be implemented in machines of different configurations without departing from the scope of the present invention. As a specific example, one of the components 206, 208 may be eliminated; additionally, memory 204, 206, and/or 208 may be provided on processor 202, or may even be provided external to device 200.

Logic circuit system

Unlike the digital data processing apparatus discussed above, a different embodiment of the invention uses logic circuitry rather than computer-executed instructions to implement multiple processing entities, such as those described above. Depending on the specific requirements of the application in the areas of speed, expense, tooling costs, etc., this logic may be implemented by constructing an Application Specific Integrated Circuit (ASIC) with thousands of tiny integrated transistors. Such an ASIC may be implemented in CMOS, TTL, VLSI, or another suitable structure. Other alternatives include digital signal processing chips (DSPs), discrete circuits (e.g., resistors, capacitors, diodes, inductors, and transistors), Field Programmable Gate Arrays (FPGAs), Programmable Logic Arrays (PLAs), Programmable Logic Devices (PLDs), and so forth.

Operation of

Having illustrated various structural features, some operational aspects of the present disclosure are now discussed. Signal bearing medium

Any of the functionality of the present disclosure is implemented using program sequences executed anywhere in one or more machines, which may be embodied in various forms of signal-bearing media. In the context of FIG. 2, the signal-bearing media may include, for example, the memory 204 or another signal-bearing media, such as a magnetic data storage diskette 300 (FIG. 3), directly or indirectly accessible by a processor 202. Whether contained in the memory 206, diskette 300, or elsewhere, the instructions may be stored on a variety of machine-readable data storage media. Some embodiments include direct access storage (e.g., a conventional "hard drive," a redundant array of inexpensive disks ("RAID"), or another direct access storage device ("DASD")), serial access storage such as magnetic or optical tape, electronic non-volatile memory (e.g., ROM, EPROM, flash PROM, or EEPROM), battery backed RAM, optical storage (e.g., CD-ROM, WORM, DVD, digital optical tape), paper "punch" cards, or other suitable signal bearing media including analog or digital transmission media and analog and communication links and wireless communications. In an illustrative embodiment of the invention, the machine-readable instructions may comprise software object code written in a language such as assembly language C.

Logic circuit system

In contrast to the signal-bearing media described above, some or all of the functionality of the present invention may be implemented using logic circuitry rather than using a processor to execute instructions. Thus, the logic circuitry is configured to perform operations to carry out the method portions of the invention. As noted above, the logic circuitry may be implemented using many different types of circuitry.

Prepaid packet data service introduction

Prepaid packet data services enable end users (also referred to as "users" or "customers") to purchase packet data services based on data volume or time. Prepaid subscribers purchase credits (credit) for using packet data services and the credit balance is stored and maintained at the PPS 146. In one embodiment, the credits are converted into a set of tickets (coupon), which may be sent one by one to an entity that assists the mobile station in managing prepaid service usage. This entity is referred to as a "prepaid client" because it interacts with the PPS146 on behalf of the mobile station 114, obtaining services, balance tickets, and/or other information from the PPS 146. In one embodiment of mobile IP, the prepaid client is home agent 148 and in another embodiment, the prepaid client is PDSN 126. In one embodiment of simple IP, the prepaid client is PDSN126, and in other embodiments of mobile-IP and simple-IP, the prepaid client may be present in any other network entity.

Initially, when a prepaid subscriber establishes a packet data session, the prepaid client receives tickets from the PPS 146. Whenever the ticket credit falls below the threshold, the prepaid client requests another ticket from the PPS 146. This process continues until the total credit balance reaches zero. To ensure secure communications, a clearing between the prepaid client and the PPS146 occurs through the home AAA server 144 and the visited AAA server 134.

More details of prepaid wireless data services are described in TIA standard IS-835-C.

General sequence of operations

Fig. 4 illustrates a general operational sequence 400 for providing account balance notification of prepaid wireless packet data services to a subscriber in a wireless packet data network. Sequence 400 is discussed in connection with the hardware components in FIG. 1B, but is not intended to be limiting in any way.

Prepaid network 120 is provisioned, step 401, and more specifically, various default system parameter values are established. These parameters will be discussed in detail in appropriate sections below.

At step 402, the customer's prepaid wireless packet data service is established by creating an account at the PPS 146. For example, the customer's account may be established manually at the PPS146 by a network technician, or remotely by a business sales agent or service provider interacting with the PPS146, or remotely by the customer using an automated teller machine or telephone or internet website interacting with the PPS146 or the like. In this step, the initiating entity enters the identity of the prepaid mobile station and the prepaid amount into the PPS146 of the mobile station's home network 143. Additional information may be recorded in the PPS146, such as the Electronic Serial Number (ESN) of the mobile station, the mobile identification number (MID), and other such data. Additional details of establishing prepaid service may be accomplished as described by IS-835-C.

At step 403, the mobile station spends, supplements, runs out, and/or queries the prepaid account balance. The use and management of prepaid packet data services IS described in detail in IS-835-C.

Various predefined account balance notification "trigger" events are detected, step 404. More specifically, these triggering events are detected by the PPS146, installed, reset, updated, programmed, or otherwise configured by the PPS146 previously occurring at step 401.

Some exemplary triggering events are described below. One such triggering event occurs at the network and, in particular, when the prepaid client (represented by home agent 148 or PDSN 126) or PPS146 detects that the mobile station's prepaid account balance falls below a system-specified threshold. The amount of the threshold may be predetermined by the service provider configuration of the network or home agent 148, the PDSN126, or the PPS146 (step 401), or by input from the operator of the mobile station (step 402).

Another exemplary triggering event is when the network, and in particular the PPS146, receives an account balance query from a mobile station or prepaid client. In the embodiment of a mobile station generated query, the operator may submit the account balance query to the network by entering a predetermined keystroke, utterance, display entry, menu item, or other input by his mobile station. The network element forwards the balance query to the PPS146 where the query is executed. The balance inquiry of the mobile station may be submitted to the PPS using various types of messaging, such as Network Architecture Specification (NAS) signaling protocol, Short Message Service (SMS), or Internet Protocol (IP). These techniques are described in more detail below in conjunction with fig. 8-10. The query may also be presented by a prepaid client, as described below.

Another exemplary triggering event is the network, and in particular, the PPS146 detecting a top-up of the mobile station prepaid account balance. For one embodiment, account recharge may occur via an initiating entity as described above in connection with step 401.

In another embodiment, the triggering event may include reaching a predetermined accounting balance notification time. These times may be periodic, semi-periodic, or occur according to another pre-scheduled schedule. For this purpose, a system clock, local timer, or other timing device may be used.

After detecting the predetermined account balance notification triggering event at step 404, step 406 is performed. If there are no trigger events, step 406 returns to step 403, and if there are trigger events, step 406 continues to step 408. Step 406 is performed by the same entity as step 404.

If a triggering event is detected (404, 406), step 408 sends the appropriate prepaid balance notification to the customer. For example, network 120 may send a message informing the user of his remaining prepaid balance in dollars, minutes, or other convenient unit of measure. This can be done with various types of information transfer, such as NAS signaling protocol, Short Message Service (SMS), or application/Internet Protocol (IP). These techniques are described in more detail below in conjunction with fig. 5-7. The type of communication used in step 408 depends on the determination made in the manner in which the network is employed, i.e., at the time of network implementation or other configuration.

After the customer is notified of his prepaid balance at step 408, process 400 returns to step 403.

In the foregoing description of sequence 400, as well as in the following description of other sequences, various interactions between PDSN126 and PPS146 and/or local AAA server 144 are described. For ease and simplicity of illustration, visited AAA server 134 is not specifically referenced, even though it is understood that certain information from subject mobile station 114 and/or PDSN126 is directed to PPS146 via visited AAA server 134 and home AAA server 144 whenever the mobile station 114 is outside of its home location. In these cases, the PDSN126 may direct communications to the visited AAA 134, which in turn negotiates (new) with the PPS146 via the home AAA server 144 (via interfaces 144a and 146 b).

Balance inquiry

Introduction to the design reside in

As described above, one potential event that may occur at step 403 (fig. 4) is the mobile station submitting a balance query. Fig. 8-10 illustrate some exemplary techniques that may occur therethrough. Embodiments of NAS messaging, SMS, and application/IP communications are discussed.

Detailed sequence: balance query with NAS signaling

As described above, one exemplary technique for the mobile station to submit a balance query at step 403 (FIG. 4) involves NAS signaling. Generally, NAS signaling refers to signaling that utilizes interface, interconnect, and other infrastructure-specific communications of the network. One example of NAS signaling IS IS-2000 compatible signaling, which IS used in CDMA-2000 networks, such as network 120 of FIG. 1B. Accordingly, as one representative embodiment of NAS signaling, FIG. 8 illustrates a sequence 800 by which a mobile station submits a balance query using IS-2000. Generally, in this sequence 800, a balance inquiry IS sent from the mobile station 114 to the PPS146 by successively delegating (address) and sending information to a plurality of network entities using IS-2000 communications until the information reaches the PPS 146.

In step 802, mobile station 114 sends a balance query to BSC 121 using over the air communication ("OTA signaling"). BSC 121 passes the balance query to the prepaid client at step 804. In one embodiment, the prepaid client is home agent 148 and in another embodiment is PDSN 126. In embodiments where the prepaid client is home agent 148, step 804 includes BSC 121 forwarding the message to PCF 124 via an a9 interface, PCF 124 sending the message to PDSN126 via an a11 interface, and PDSN126 sending the balance query to home agent 148 via a mobile IP message. If PDSN126 is a prepaid client, step 804 includes BSC 121 and PCF 124 forwarding the balance inquiry to PDSN126 using a9/a11 signaling.

At step 806, the prepaid client sends a balance query to the PPS146 using RADIUS protocol messages, completing sequence 800.

The above sequence utilizes IS-2000 signaling, as shown in the context of CDMA-2000 network 120. Of course, in other types of networks, the balance query is submitted in a similar but technically different way as NAS signaling (step 403, fig. 4). For example, in a GSM network, balance inquiries are relayed by GPRS messages; in the W-CDMA system, the balance inquiry is made using Universal Mobile Telecommunications System (UMTS) communications. More specifically, under GPRS or UMTS, the mobile station submits a balance query in the following manner.

First, the mobile station transmits a balance inquiry to a Radio Network Controller (RNC) using a GSM or W-CDMA type OTA link, if applicable. The RNC then forwards the message to the Serving GPRS Support Node (SGSN) using an interface such as lups (for UMTS) or Gb (for GPRS). The SGSN sends messages to prepaid clients, such as a Gateway GPRS Support Node (GGSN), on an interface such as Gp (if GGSN and SGSN are in the same carrier) or Gn (if GGSN and SGSN are in different carriers). The prepaid client then forwards the balance inquiry to the visited or home AAA using, for example, the RADIUS protocol.

Detailed sequence: balance inquiry using SMS

As described above, another exemplary technique for the mobile station to submit a balance query at step 403 (fig. 4) involves an SMS message, which may be used in any network configuration that is SMS capable, such as a CDMA-2000 network (e.g., 120), a GSM network, a W-CDMA network, etc. Fig. 9 shows a sequence 900 by which a mobile station submits a balance query using SMS. Generally, in this sequence 900, a balance inquiry is sent from the mobile station 114 to the PPS146 via an SMS message. In this embodiment, the PPS146 is defined as an entity (as well as mobile phones and other receiving stations) to which SMS messages can be directed.

In step 902, mobile station 114 sends a balance inquiry message in SMS format to BSC 121. In step 904, the BSC transmits the message to the SMS device 133 through the MSC132 and the interface 121 a. At step 906, the SMS device 133 relays the balance inquiry to the PPS 146. More specifically, at step 906, the SMS device 133 may forward the SMS balance query message to the home AAA server 144, which in turn passes the query to the PPS 146. Details of the use of known hardware components, interconnections, and SMS functionality for steps 904 and 906 will be apparent to those of ordinary skill in the art (after reading this disclosure). Sequence 900 is thus complete.

One of ordinary skill in the art, after reading this disclosure, will be able to implement similar SMS messaging in other non-CDMA 2000 networks, such as GSM, W-CDMA, etc., using the preceding description of sequence 900 without undue experimentation. The hardware components, interconnections, and SMS functionality in the various networks are known and documented.

Detailed sequence: balance inquiry using application/IP

As described above, another exemplary technique for the mobile station to submit a balance query at step 403 (FIG. 4) involves application/IP communications. For purposes of illustration, fig. 10 shows a sequence 1000 for communicating a mobile station's balance inquiry message in CDMA-2000 system 120 using application/IP communication. Generally, in this sequence 1000, the mobile station sends its balance inquiry directly to the PPS146 using application/IP communication. "application/IP" herein refers to communication, where: (1) the message is relayed in the network element according to the IP address of the receiving station; (2) the content of the message is partitioned, routed, recombined, error corrected or otherwise processed by a Transmission Control Protocol (TCP) or other packet management layer; and (3) the message content is processed at the sender and receiver by respective, mutually compatible "applications". One of ordinary skill (after reading this disclosure) will recognize that when using a client-server application, the client application will know the transport port number of the server application.

At step 1002, the mobile station 114 sends an application/IP message containing the balance inquiry to the IP address of the PPS 146. The mobile station 114 may obtain the IP address of the PPS146, e.g., by pre-programming the IP address earlier in the mobile station 114's memory, performing a DNS query, etc. The balance inquiry message comprises a prepaid service application layer protocol message utilizing an IP protocol suite.

At step 1004, the balance inquiry message is propagated through the network via appropriate connection components as needed to route the application/IP information to PPS146 (e.g., base station 123, BSC 121, PCF 124, PDSN126, etc.). Unlike sequence 800 (fig. 8), the mobile station does not specifically delegate balance notification to PDSN126 or any other intermediary, upstream components, due to the use of the actual IP address of PPS 146. The message is sent to the PPS146 over the IP network 138 without requiring participation by the visited AAA server 134 or the home AAA server 144.

Balance inquiry through prepayment client machine

Another potential event that may occur at step 403 (fig. 4) is a prepaid client (e.g., PDSN 126) submitting a balance query on behalf of a mobile station. Prepaid clients may submit balance queries in a variety of situations, depending on the needs of the application. For example, the prepaid client may submit a balance query for the mobile station each time the mobile uses a specified amount of packet data, according to a specified schedule, according to a final balance ticket (before the balance is exhausted) communicated to the mobile station, and so on.

In the case of PDSN126, it submits a balance query to home AAA server 144 (or visited AAA server 134) using NAS signaling, such as IS-2000 in the case of a CDMA-2000 network. The contents of the message for PDSN126 utilize AAA compatible protocols such as RADIUS, DIAMETER, etc.

Balance notification

Introduction to the design reside in

Fig. 5-7 illustrate some exemplary techniques for delivering a balance notification of step 408 (fig. 4). Examples of NAS signaling, SMS, application/IP communications are discussed.

Detailed sequence: balance notification using NAS

As discussed above, one exemplary technique for providing prepaid account balance notifications to customers as a compensation for step 408 (FIG. 4) involves NAS signaling.

One example of NAS signaling IS IS-2000 compatible signaling used in CDMA-2000 networks, such as network 120 of FIG. 1B, for example. Accordingly, fig. 5 shows an example of balance notification using NAS signaling, a specific example using IS-2000 signaling.

Generally, in this sequence 500, account balance notifications are sent from the PPS146 to the mobile station 114 by successively delegating and sending information to multiple network entities using IS-2000 communications until the information reaches the mobile station.

At step 502, the PPS146 sends a balance notification to the prepaid client using the RADIUS protocol. In one embodiment, the balance notification includes a balance number, such as $ 23.50. In another embodiment, the balance notification comprises a so-called "ticket" that includes a specified portion (e.g., $ 5) of the remaining balance, where the PPS146 releases the portion one by one. This document IS described in the IS-835-C publication mentioned above. In another embodiment, the balance information of step 502 may include a balance number and a ticket.

In step 504, the prepaid client communicates a balance notification to BSC 124. The prepaid client of step 502 is home agent 148 in one embodiment, and PDSN126 in another embodiment. In embodiments where the prepaid client is home agent 148, step 504 includes home agent 148 sending a balance notification to PDSN126 via a mobile IP message. PDSN126 then forwards the balance notification to PCF 124 and BSC 121 via a11 and a9 signaling. If PDSN126 is a prepaid client, step 504 includes PDSN126 relaying the balance notification to PCF 124 and BSC 121, respectively, via a11 and a9 signaling.

BSC 121 transmits the balance notification to mobile station 114 through BS 123, and BS 123 sends the message to mobile station 114 using OTA signaling in step 508.

Upon receiving the information, mobile station 114 displays the prepaid account balance and/or billing information to the operator (step 510). The display may involve, for example, a video display on a Liquid Crystal Diode (LCD) display screen, and/or a voice or other audio display.

The foregoing sequence utilizes IS-2000 signals and IS suitable for CDMA-2000 network 120. Of course, in other types of networks, the balance notification (step 403, fig. 4) is done in a similar but technically different way as NAS signaling. For example, in a GSM network, balance notification is performed using General Packet Radio Service (GPRS) messages; in the W-CDMA system, the balance notification is performed using Universal Mobile Telecommunications System (UMTS) communications. More specifically, under GPRS or UMTS, the balance notification is performed in the following manner according to the present disclosure. First, the AAA server transmits a balance notification and/or ticket to a prepaid client, such as a GGSN, using RADIUS or another suitable protocol. The GGSN may then forward the balance notification to the SGSN over an interface such as Gp (if GGSN and SGSN are in the same carrier) or Gn (if GGSN and SGSN are in different carriers), if applicable. The SGSN forwards the balance notification to the RNC using an interface such as lups (for UMTS) or Gb (for GPRS). The RNC passes the balance information to the mobile station using either the GMS or W-CDMA air link. Finally, the mobile station displays the balance to the user.

Detailed sequence: balance notification using SMS

To illustrate a different exemplary technique for providing prepaid account balance notifications to customers, sequence 600 (FIG. 6) utilizes SMS communications as a compensation to step 408 (FIG. 4). Sequence 600 is illustrated in the context of system 120 of FIG. 1B, but is not intended to be limiting in any way.

SMS is a widely accepted wireless service enabling the transmission of alphanumeric messages between mobile subscribers and external systems such as e-mail, paging and voice mail systems. Since SMS is known to those of ordinary skill in the relevant art, descriptions of protocols, interfaces, formats, and other communication details are omitted below.

At step 602, the PPS146 sends a balance notification to the SMS device 133 and, more particularly, to the MC assigned to the subject mobile station 114. In step 604, SMS device 133 sends a balance notification to BSC 121. As a more specific example in the context of CDMA-2000 system 120, step 604 includes SMS device 133 querying a Home Location Register (HLR) to identify a particular MSC in communication with mobile station 114, SMS device 133 forwarding a balance notification to identified MSC132, and MSC132 forwarding the balance notification to BSC 121.

In step 610, BSC 121 forwards the balance notification to mobile station 114 via the appropriate base station 123 using a message of the appropriate format. One embodiment is a "data subframe" message, which is a known method of carrying SMS data to a mobile station. Upon receiving this information, mobile station 114 displays prepaid account balance and/or billing information to its operator (step 612).

One of ordinary skill, after reading this disclosure, will be able to implement similar SMS messaging in other, non-CDMA-2000 networks, such as GSM, W-CDMA, etc., using the preceding description of sequence 600, without undue experimentation. The hardware components, interconnections, and functionality of SMS in various networks are known and documented in the art.

Detailed sequence: balance notification using application/IP

Another technique for providing prepaid account balance notifications to customers, as compensated for in step 408 (fig. 4), is implemented using application/IP messaging. Fig. 7 illustrates one embodiment in the form of a sequence 700. Sequence 700 is illustrated in the context of system 120 of fig. 1B, but is not intended to be limiting in any way. Unlike NAS signaling (fig. 5), where the balance notification is continuously delegated and then sent to different network entities until it reaches the mobile station, this sequence conveys this information directly using application/IP messages. "application/IP" herein refers to communication, where: (1) the message is relayed in the network element according to the IP address of the receiving station; (2) the content of the message is partitioned, routed, recombined, error corrected or otherwise processed by a Transmission Control Protocol (TCP) or other packet management layer; and (3) the message content is processed at the sender and receiver through compatible "applications".

In step 702, the PPS146 queries the DNS 150 for the IP address of the mobile station 114 to enable the PPS146 to send the balance notification directly to the mobile station 114. In one embodiment, the PPS146 may query a DNS 150 which in turn queries as many DNS entities as needed to obtain the IP address of the mobile station. In another embodiment, the PPS146 queries as many DNS entities as needed to find the desired address. One embodiment of these queries is to utilize the DNS protocol. The nature, syntax, and use of DNS queries are known in the relevant art. Also at step 702, the PPS146 receives the IP address of the mobile station from the DNS 150.

In another embodiment, the PPS146 queries another entity that has access to the IP address of the mobile station 114. For example, the PPS146 may query the local AAA server 144 to obtain the IP address of the mobile station. In other cases, the PPS146 may query the prepaid client or examine messages previously received from the prepaid client, for example, if the prepaid client, mobile station, or other source has initiated a balance query or other IP message to the PPS 146. Such a message may presumably contain the IP address of the mobile station.

After step 702, the PPS146 sends the balance notification directly to the mobile station IP address (step 704). The balance notification of the PPS146 comprises a prepaid service application layer protocol message utilizing an IP protocol suite. The prepaid client comprises PDSN126 or a home agent. The message propagates through a number of network elements, such as home agent 148 (for mobile IP), PDSN126, PCF 124, BSC 121, etc. (step 706). But the content of the message is transparent to these components. Unlike sequence 500 (fig. 5), the balance notification message is not specifically delegated to any intermediary, or downstream component, since the actual IP address of the mobile station is utilized.

Upon receiving this information, mobile station 114 displays the prepaid account balance and/or billing information to the operator (708).

Other embodiments

Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. It will be apparent to those skilled in the art that various modifications can be made to these embodiments, and the generic principles defined herein may be applied to other embodiments, without departing from the scope or spirit of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

The term "exemplary" as used herein means "serving as an example, instance, or illustration. Any embodiment described herein as "exemplary" is not to be construed as preferred or advantageous over other embodiments.

Claims (25)

1. A method of providing account balance notification for prepaid wireless packet data services in a wireless packet data network, comprising operations of:

detecting the occurrence of a predetermined triggering event;

in response to the occurrence of any one of said predetermined triggering events associated with a particular wireless subscriber station, sending a balance notification to said particular subscriber station over the network.

2. The method of claim 1, wherein the detecting of the occurrence of the predetermined triggering event comprises one or more network components detecting the occurrence of one or more of the following events:

the account balance of the particular subscriber station falls below a network specified threshold;

the account balance of the particular subscriber station falls below a subscriber station specified threshold;

receiving an account balance query from the particular subscriber station;

receiving an account balance query from a network component;

a recharge of an account balance for the particular subscriber station;

a predetermined account balance notification time is reached.

3. The method of claim 1, wherein the sending operation comprises:

relaying the balance notification to the particular subscriber station over a network using network architecture characteristic signaling.

4. The method of claim 1, wherein:

the wireless packet data network includes at least one prepaid server, at least one prepaid client, at least one packet control function module, and at least one base station controller;

the sending operation comprises:

the prepaid server sending data representing the balance notification to the prepaid client using an authentication, authorization, accounting (AAA) protocol;

the prepaid client sending data representing the balance notification to the packet control function using a11 protocol;

the packet control function module sends data representing the balance notification to the base station controller by using an A11 protocol;

the base station controller transmits data representing the balance notification to the particular subscriber station using a prescribed over-the-air (OTA) protocol.

5. The method of claim 1, the sending operation comprising:

relaying the balance notification to the particular subscriber station using a Short Message Service (SMS) communication.

6. The method of claim 1, the sending operation comprising:

transmitting the balance notification to an Internet Protocol (IP) address of the particular subscriber station.

7. The method of claim 6, wherein:

the operations further comprise, prior to the transmitting operation, querying at least one prescribed entity to obtain an IP address of the particular subscriber station.

8. The method of claim 1, wherein the operations further comprise:

the specific user station submits a balance inquiry to a prepaid server;

the operation of detecting the occurrence of the predetermined trigger event comprises the prepaid server detecting receipt of the balance inquiry.

9. The method of claim 8, wherein:

the submitting operation includes the particular subscriber station sending a balance query to the prepaid server using one of the following communication modes: network architecture feature signaling, Short Message Service (SMS), application/Internet Protocol (IP) messaging.

10. The method of claim 1, wherein the operations further comprise:

the prepaid client submitting a balance query to a prepaid server on behalf of said particular subscriber station;

the operation of detecting the occurrence of the predetermined trigger event comprises the prepaid server detecting receipt of the balance inquiry.

11. A signal bearing medium tangibly embodying a program of machine-readable instructions executable by a digital data processor to perform operations in a wireless packet data network for providing account balance notification for prepaid wireless packet data services, the operations comprising:

detecting the occurrence of a predetermined triggering event;

in response to the occurrence of any one of said predetermined triggering events associated with a particular wireless subscriber station, sending a balance notification to said particular subscriber station over the network.

12. The medium of claim 11, wherein the operation of detecting the occurrence of a predetermined triggering event comprises one or more network components detecting the occurrence of one or more of the following events:

the account balance of the particular subscriber station falls below a network specified threshold;

the account balance of the particular subscriber station falls below a subscriber station specified threshold;

receiving an account balance query from the particular subscriber station;

receiving an account balance query from a network component;

a recharge of an account balance for the particular subscriber station;

the projected account balance notification time is reached.

13. The medium of claim 11, wherein the sending operation comprises:

transmitting said balance notification to said network for delivery to said particular subscriber station using network architecture characteristic signaling.

14. The medium of claim 11, wherein the sending operation comprises:

transmitting the balance notification to the network for delivery to the particular subscriber station using Short Message Service (SMS) communication.

15. The medium of claim 11, wherein the sending operation comprises:

transmitting the balance notification to an Internet Protocol (IP) address of the particular subscriber station.

16. The medium of claim 15, wherein:

the operations further comprise, prior to the transmitting operation, querying at least one prescribed entity to obtain the IP address of the particular subscriber station.

17. The medium of claim 11, wherein:

one of the predetermined triggering events comprises receiving a balance query;

the receiving operation includes receiving the balance inquiry through one of the following communication modes: network architecture feature signaling, Short Message Service (SMS), application/Internet Protocol (IP) messaging.

18. Circuitry, comprising a plurality of interconnected electrically conductive elements, configured to perform operations in a wireless packet data network for providing account balance notification for prepaid wireless packet data services, the operations comprising:

detecting the occurrence of a predetermined triggering event;

in response to the occurrence of any one of said predetermined triggering events associated with a particular wireless subscriber station, sending a balance notification to said particular subscriber station over the network.

19. A prepaid server for providing account balance notification for prepaid wireless packet data services in a wireless packet data network, the prepaid server comprising:

a memory;

an input/output;

a digital data processor coupled to the memory and programmed to perform operations comprising:

detecting the occurrence of a predetermined triggering event;

the transmission of any one of said predetermined trigger events associated with a particular wireless subscriber station

In response, a balance notification is sent over the network to the particular subscriber station.

20. A prepaid server for providing account balance notification for prepaid wireless packet data services in a wireless packet data network, the prepaid server comprising:

a storage device;

an input/output device;

a digital data processing apparatus that performs operations comprising:

detecting the occurrence of a predetermined triggering event;

in response to the occurrence of any one of said predetermined triggering events associated with a particular wireless subscriber station, sending a balance notification to said particular subscriber station over the network.

21. A communications network for providing prepaid wireless packet data services, comprising:

at least one prepaid packet data service client;

at least one base station controller;

at least one component for managing packet data communications between said prepaid client and a base station controller;

a prepaid server programmed to perform operations for providing account balance notification for prepaid wireless packet data services, the operations comprising:

detecting the occurrence of a predetermined triggering event;

in response to the occurrence of any one of said predetermined triggering events associated with a particular wireless subscriber station, sending a balance notification to said particular subscriber station over the network.

22. The network of claim 21, wherein the prepaid server comprises part of a local authentication, authorization, accounting (AAA) component.

23. The network of claim 21, wherein the network comprises a home authentication, authorization, accounting (AAA) component, the prepaid server being externally coupled to the home AAA component.

24. The network of claim 21, wherein the network exhibits one of the following structures: CDMA-2000, W-CDMA, GPRS.

25. A communications network for providing prepaid wireless packet data services, comprising:

at least one prepaid packet data service client;

at least one base station controller;

means for managing packet data communications between said prepaid client and a base station controller;

a prepaid server device that provides account balance notification for prepaid wireless packet data services by performing operations comprising:

detecting the occurrence of a predetermined triggering event;

in response to the occurrence of any one of said predetermined triggering events associated with a particular wireless subscriber station, sending a balance notification to said particular subscriber station over the network.