MXPA06006581A - System for account management and method therefor - Google Patents

System for account management and method therefor

Info

Publication number
MXPA06006581A
MXPA06006581A MXPA/A/2006/006581A MXPA06006581A MXPA06006581A MX PA06006581 A MXPA06006581 A MX PA06006581A MX PA06006581 A MXPA06006581 A MX PA06006581A MX PA06006581 A MXPA06006581 A MX PA06006581A
Authority
MX
Mexico
Prior art keywords
account
balance
management server
authorization
account balance
Prior art date
Application number
MXPA/A/2006/006581A
Other languages
Spanish (es)
Inventor
Marcelo Claure Bedoya Raul
Marcelo Narea Munoz Jaime
Braulio Peralta Gomez Juan
Original Assignee
Bedoya Raul Mc
Gomez Juan Bp
Munoz Jaime Mn
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bedoya Raul Mc, Gomez Juan Bp, Munoz Jaime Mn filed Critical Bedoya Raul Mc
Publication of MXPA06006581A publication Critical patent/MXPA06006581A/en

Links

Abstract

An account management server stores and operates on a plurality of accounts. Each account includes account user information and an account balance representing a measurement of communication time. The account manager is configured to transfer of at least a portion of an account balance associated with a first account to a second account.

Description

SYSTEM FOR ADMINISTRATION OF ACCOUNTS AND METHOD FOR THE SAME FIELD OF THE INVENTION The present invention relates generally to the management of accounts in the field of communication systems, and very specifically relates to the management of accounts of communication devices, both wireless devices and wired devices, which have prepaid and / or prepaid capabilities. of payment-posterior.
BACKGROUND OF THE INVENTION In previous years, cell phones, Personal Digital Assistants (PDA), message delivery devices, and other portable electronic devices that have communication capabilities have become a staple of daily life. It is not uncommon for the average person to own more than one communication device. As these devices evolve, prices go down. With the decline in prices, communication devices attract a larger portion of an economic demography. The growing demand and revenue generated by popularity allow the expansion of systems and capabilities, making such devices useful in many places. This allows the wireless connection to telephone systems, electronic mail processing, playing electronic games, Internet access and other communication functions which also fuel the increased desire for a broader economic demography. It is anticipated that, as the price decrease continues in combination with the expansion of characteristics, the use and demand of said device will be an integral and permanent part of people's daily lives. The operators of the wireless and wired system, ("carriers"), strive to increase their income by placing as many portable devices with paying customers, ("users") as possible. The income of the carriers comes from the use of portable devices. The larger the installed base, the greater the potential for revenues. But, the diverse economic demography and economic level of society demand different payment methods for different geographical scenarios, income and credit levels. In a typical carrier system there are two methods of payment between users, payment of credit, (later payment), and prepayment. Credit users receive the charges incrementally based on a criterion "as used", while prepaid users buy incremental blocks of time for communication in the carrier channel. Recently, there has been a noticeable change in the prepaid scheme. The use of prepayment creates a benefit for the user in the monetary budget. The user will know the number of time blocks purchased and remaining and can make a budget accordingly. There is no surprise in relation to the amount of the invoice at the end of the month. A typical scenario would be for parents to buy blocks for their children's use. This scheme allows the family to make a budget and have a communication that can be financed. The use of prepaid creates guaranteed income which is beneficial for the carrier. The income is generated at the time of sale of those blocks of time. Although some income could be generated from unused blocks of time, this is typically not the case. Unfortunately, some credit users are more likely to default on their payment than to offset any benefits from the unused prepaid blocks. But the prepaid block alleviates the potential for non-payment. The prepayment also allows the bearer to offer services in lower social economic demographics by reducing the risk of non-payment.
A typical disadvantage for the carrier account management scheme is that the uninterrupted use of credit users of the devices generates a constant flow of income for the bearer; while the prepaid user can only use his device until his respective time block is exhausted. The prepaid user must then find a place to buy additional blocks before using the portable device. Time out of the intermediate channel frustrates the user and costs the carrier's income while the user locates, and moves to the point of sale to buy additional blocks. In lower social economies, the transportation infrastructure is often sporadic, which increases the out-of-channel interval exacerbating the dilemma. Therefore, there is a need to overcome the problems with the prior art as discussed above.
SUMMARY OF THE INVENTION In a general aspect, an account management server stores and operates in a plurality of accounts. Each account includes user information for the account and an account balance that represents a measure of communication time. The account manager is configured to authorize a transfer of at least a portion of an account balance associated with a first account to a second account. The executions may include one or more of the following characteristics. For example, the user information of the account may include a plurality of shared users. The account balance may reflect a total balance, a plurality of balances for different account services, and / or a financial equivalent of communication time. In some cases, the account management server can convert the communication time measures into financial equivalents. The account management server can track the use of each of the plurality of accounts and decrease the associated account balance as required and / or increase the associated account balance of an account as credits are received for that account. For example, the account management server may increase the account balance in response to the receipt of a bank loan, a purchase of airtime credit, an account payment, or other financial entry. In some executions, each account may include account authorization information to access the account and use the account balance. Examples of account authorization information may include a password, speech recognition, and / or system recognition. The authorization may include over-the-air authorization when a communication device is authenticated to use and / or keyboard entries recognized by the account management server. The account management system may also include a transaction point operatively coupled to the account management server to allow users to manage multiple accounts. The aspects of the present invention can be executed by means of an apparatus and / or by a computer program stored on a computer-readable medium. The computer readable medium may comprise a disk, a client device, a network device and / or a propagated signal. Other features and advantages will be apparent from the following description, including the figures, and from the claims.
BRIEF DESCRIPTION OF THE FIGURES The accompanying figures, in which like reference numerals refer to identical elements or of similar functionality throughout the separate views and which together with the detailed description below are incorporated in, and form part of the description, serve to illustrate additionally several modalities and to explain various principles and advantages, all in accordance with the present invention. The present invention will be described by exemplary embodiments, but not limitations, illustrated in the accompanying drawings in which similar references indicate similar elements, and wherein: Figure 1 is an electronic block diagram illustrating an account management system . Figure 2 is an electronic block diagram illustrating a communication device for use within the account management system of Figure 1. Figures 3 and 4 are operational flow charts illustrating various modes of operation of the communication device. of Figure 2. Figure 5 is an operational flow chart illustrating one mode of operation of an account management server that operates within the account management system of Figure 1.
DETAILED DESCRIPTION OF THE INVENTION As required, the detailed embodiments of the present invention are described therein.; however, it should be understood that the embodiments described are merely examples of the invention, which can be exemplified in various ways. Therefore, specific functional and structural details described therein are not to be construed as limiting, but solely as a basis for the claims and as a representative basis for teaching those skilled in the art to variously employ the present invention. virtually any detailed structure in an appropriate manner. In addition, the terms and phrases used here are not intended to be limiting; but rather, to provide an understanding description of the invention. The terms "a" or "an", as used herein, are defined as one or more than one. The term plurality, as used herein, is defined as two or more than two. The term other, as used herein, is defined as at least one second or more. The terms that include and / or have, as used herein, are defined as comprising (ie, open language). The term "coupled", as used herein, is defined as connected, although not necessarily directly, and not necessarily mechanically. The terms program, software application, and the like, as used herein, are defined as a sequence of instructions designed for execution in a computer system. A program, computer program, or software application can include a sub-routine, a function, a procedure, an object method, an object execution, an executable application, an APPLET program, a SERVLET program, a source code, an object code, a shared library / dynamic load library and / or another sequence of instructions designed for execution in a computer system. The present invention, as described herein, is an account management system for providing the airtime account sharing within accounts determined among multiple users and communication devices. In accordance with an exemplary embodiment of the present invention, Figure 1 illustrates an account management system 100. The account management system 100 of Figure 1 includes an account management server 105 communicatively coupled through a network 125. to a plurality of communication devices 130. The plurality of communication devices 130, for example, can include an Internet device 135, a wireless device 140, a point-to-point device 145 and other equivalent communication devices 150 as is well known in the art. Similarly, the plurality of communication devices 130 may include any number of wireless or wired devices which may be mobile phones, Personal Digital Assistants, Computers, push-to-talk mobile radios, point-to-point communication devices, telephones, laptops, two-way message sending devices with audio capability, network communication devices, Internet communication devices, or the like. Those skilled in the art will appreciate that, in this exemplary embodiment, the network 125 may be a wireless network, a wired network or a combination of a wired and wireless network. In the description, the term "network" and "communication devices" refer to any mentioned network or communication device or an equivalent. One skilled in the art would recognize that the networks could support a plurality of communication devices that could operate in one of the networks or a combination of the networks. Those skilled in the art will appreciate that, the network 125 may be a first generation analog mobile telephone service, a second generation (2G) digital mobile telephone service (including 2.5G and 2.75G), a mobile phone service with third generation (3G) Internet capability, a message sending network, a conventional PSTN, or the like. In addition, the communications standard of the network 125 of Figure 1 can be Multiple Access by Code Division (CDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), Radio Service of General Package (GPRS), Frequency Division Multiple Access (FDMA), distorted Wired Line pair, or the like. Similarly, those skilled in the art will appreciate that the network 125, in conjunction with the present invention, can operate using any wireless channel, eg, mobile cell phone channel, mobile radio channels, (including radio channels) to talk), channels for sending one- and two-way messages, data channels or any equivalent. Additionally, the network 125 may operate using other types of communication channels such as the Internet, infrared channels, wired channels, short message delivery systems (SMS), and / or Bluetooth channels. In the following description, the term "network" refers to any wireless communication system or wired communication system or device of the communication systems discussed above or below or an equivalent. The account management server 105 preferably stores a plurality of accounts 110, where each account 115 has a credit balance 120 associated therewith. For example, a first account has a first account balance and a second account has a second account balance as illustrated in figure 1. The account balance can be a measure of communication time or a financial equivalent of communication time . The account balance can also be a total balance or a plurality of balances for different account services. The account management server 105 preferably includes a server processor 155 operatively coupled to the stored plurality of accounts 110 and programmed to operate on the plurality of accounts 110 in response to various events and entries received through network 125 or other media. Those skilled in the art will appreciate that the operation of the server processor 155 can be executed in hardware circuitry or alternatively in programmed software. In one embodiment, the processor 155 may be programmed with a predetermined algorithm to convert measures of communication time to its financial equivalents or vice versa. Said algorithm can be adjusted as the financial equivalent rates are adjusted. Software programs, for example, can be hard coded or programmed into the server processor 155 during manufacturing, can be programmed on-the-air once the customer subscribes, or can be downloadable applications. Those skilled in the art will appreciate that other programming methods can be used to program the server processor. The server processor 155 preferably tracks the use of each of the plurality of accounts 110 and decreases the associated account balance 120 of the account used 115 as required. Similarly, the server processor 155 increases the associated account balance 120 of account 115 as the credits are received for that account. For example, a bank loan, a purchase of airtime credit, an account payment, or other financial entry may be received to increase account balance 120. Each of the plurality of accounts 110, in one embodiment, includes information of the user of the account and account authorization information (not shown) to access the account and use the available account balance. The authorization may be in the form of a password, generated by the user, generated by the system, or predetermined, and may be in the form of numbers, letters, combination of both, speech recognition, system recognition (ie caller ID, or electronic serial number) or an equivalent. The authorization can occur as a function of the transfer (not shown) or by the user interaction required (not shown). In one mode, the authorization step (not shown) is not present or is not required. The processor of the server 155, in one mode, receives requests to use each account and verifies the authorization of the requestor before allowing said use. The authorization, for example, may be an over-the-air authorization when the communication device is authenticated in the system for use. Similarly, the authorization can be entered by means of a keyboard in the account management server 105 at the time of purchase of the communication device and initiation of the associated account. Those skilled in the art will appreciate that, the previously approved authorization may be stored in the account management server 105. Those skilled in the art will recognize that the account management server 105 may reside within the plurality of communication devices 130, as its own device, as part of the larger network or networks, or any combination of the aforementioned devices and systems. In one embodiment, the account management system 100 includes a transaction point 165 operatively coupled to the account management server 105. The transaction point allows users to manage their various accounts, such as increasing balances, requesting balances from account, prior authorizations, and the status of pending requests and equivalent operations. For example, the transaction point 165 can be communicatively coupled to the account management system 100 through the network 125, PSTN (Public Switched Telephone Network), Internet or an equivalent. Figure 2 is an electronic block diagram of a communication device 200 useful for use within the account management system 100 of Figure 1, in accordance with a preferred embodiment of the present invention. The communication device 200 can be, for example, any of the plurality of communication devices 130 as illustrated and discussed for Figure 1, such as the Internet device 135, the point-to-point device 145, or the device wireless 140. As illustrated, the communication device 200 of Figure 2 includes a transceiver 205, a processor 210, a user input 220, a display 225 and a memory 230. The transceiver 205 establishes communication with the network 125 to send and receive signals. The transceiver 205 preferably employs conventional modulation and demodulation techniques to receive the communication signals transmitted by the network 125 to the communications device 200. The transceiver 205 also transmits signals through an antenna in response to commands from the processor 210. Those skilled in the art. the art will appreciate that the transceiver 205 may be a singular electronic circuit capable of both functions, or alternatively it may be a single receiver circuit and a transmitter circuit. Those skilled in the art will appreciate that other similar electronic block diagrams or alternative types can be used to handle the communication requirements of the communication device 200. The transceiver 205 is operatively coupled to the processor 210. The processor 210 utilizes conventional techniques of signal processing to process the received signals. The processor 210 also sends commands to various operating components of the communication device 200 as described herein. The processor 210, in accordance with the present invention, includes an account manager 215 for performing the various account management functions as described herein. The account manager 215 can be executed in hardware circuitry or alternatively in programmed software. Software programs, for example, they can be hard coded or programmed into the processor 210 during their manufacture, they can be programmed over-the-air at the time of customer subscription, or they can be downloadable applications. Those skilled in the art will appreciate that other programming methods can be used to program the account manager 215. To perform the necessary functions of the exemplary communication device 200, the processor 210 is coupled to the display 225. Once a signal, the processor 210, for example, can generate a command signal to the display 225 to generate a visual notification of the reception of the signal. When the display 225 receives the command signal from the processor 210, a notification can be displayed. For example, the display 225 may display accounts, balances, amounts of airtime, messages received from and sent to the network 125, shared user information, menu concepts and the like. The display 225 may be, for example, a liquid crystal display, a dot matrix display, or an equivalent. The screen 225 can be a color or grayscale text or graphic screen or equivalent. The display 225 may include indicators and / or advertisements, or the equivalent, which would allow the user to visually determine the status of the communication device 200. The processor 210 is further coupled to the user input 220. The user input 220 may include one or more buttons (not shown), a series of button pressures, a voice response from the user of the device, a manual switch with associated circuitry (not shown), a momentary contact switch with associated circuitry (which not shown), buttons with associated circuitry (not shown), or any user activation signal or some other similar method of manual response initiated by a user of communication device 200. Those skilled in the art will appreciate that the input user 220 may be a combination of switches, buttons, or equivalents capable of generating a signal for processor 210, such as a signal interrupt or a polling signal detected by the processor 210, representing an activation signal. The processor 210 is coupled to the memory 230 and, therefore, operates the functions having characteristics of the communication device 200. The memory 230 preferably comprises a random access memory (RAM), a read only memory (ROM) , and / or an electronically erasable, programmable read-only memory (EEPROM) (not shown), temporary memory, or an equivalent. The memory 230 preferably includes memory locations for storing one or more shared users 250 and further includes memory locations for storing a plurality of accounts 235. Each account 240 of the plurality of accounts 235 has an account balance 245 associated therewith. In one embodiment of the present invention, the account balance 245 is stored within the memory 230 together with the account information 240 such as user authorizations, shared users, and the like. In accordance with the present invention, the account manager 215 is adapted to handle the use of the plurality of accounts 235 by one or more users. For example, account manager 215 tracks account usage, account balances, account access authorization criteria of shared users 250, and the like. Further, in response to user input 220, account manager 215 executes various operations such as increasing and decreasing one or more of the plurality of accounts 235, transferring balances from one account to another, and authorizing transfers of at least one portion of an account balance to another shared user. (That is, one of the shared users 250 stored within the memory 230 or another balance requestor). In a similar way, in response to a message received from network 125, the administrator of account 215 executes various operations such as increasing and decreasing one or more of the plurality of accounts 235, transferring balances from one account to another, and authorizing transfers at least from a portion of an account balance to another shared user. (That is, one of the shared users 250 stored within the memory 230 or another beneficiary of a balance transfer). The account manager 215, in one embodiment, may also increase account balances in response to transfers received from other shared users received through the network 125. The aforementioned accounts 235 may be prepaid, subsequently paid, credit cards, accounts banks, automatic distribution machines (ATM) or similar. Those skilled in the art will readily recognize that the exemplary communication device could be a communication device wired with the transceiver 205 identifying a modem to establish communication with the network 125. Figure 3 is an operational flow diagram illustrating one embodiment of the operation of the communication device 200 of Figure 2. Specifically, Figure 3 illustrates the operation of the communication device 200 when the communication device 200 is the transmitting device. As illustrated, the operation begins with step 300 wherein, the communication device 200 is in the alert mode. The alert mode is typically a low battery leak mode where the communication device 200 is waiting for inputs. Then, in step 305, the operation asks for the reception of a user input for a balance transfer. For example, the account manager 215 may receive a signal from the user's entry 220 indicating a user's desire to initiate an account balance transfer. When the user input for an account balance transfer in step 305 is not detected, the operation continues with step 310 in which the operation asks for the receipt of a transfer request. For example, the communication device 200 may receive a request for an account balance transfer from one of the plurality of communication devices 130 through the network 125. Similarly, the communication device 200 may receive a request for an account balance transfer from the account management server 105 through the network 125. Those skilled in the art will appreciate that the request for an account balance transfer may also be received from alternative sources not illustrated in the present invention, such as a secondary communication device or the like. When a transfer request is not detected in step 310, the operation returns to the alert mode of step 300. When the receipt of a transfer request is detected in step 310, the operation continues with step 315 in which, the operation determines whether the request has been accepted or not. For example, the account manager 215 may display the request on screen 225 and user input 220 may be used to accept or reject the transfer request. Similarly, the account administrator 215 may compare the information contained in the transfer request of the account balance, such as the identification of the applicants with authorization information, such as the shared users 250 stored in the memory 230 and either Accept or reject the request. In one embodiment, the user may review an account balance as part of the acceptance decision by executing the process of step 315. For example, the account balance may be sent to the transmitter device as a separate message or within the request for transfer of the account balance. Those skilled in the art will appreciate that the account balance can be automatically sent or alternatively sent in response to a user request. In an alternative modality, the account balance is stored in the memory of the transmitter device for recovery by the user, as required. When the request is denied (rejected) in step 315, the operation continues with step 320 in which, the communication device 200 sends a negative through the network 125 to the requester. The operation then returns to the alert mode of step 300. When the request is accepted in step 315 or when a user input for a transfer is received in step 305, the operation continues to step 325 in which an account is selected for balance transfer. For example, the account manager 215 may select one of the plurality of accounts 235 stored in the memory 230. Alternatively, the account manager 215 may display all the plurality of accounts 235 on the screen 225 and the account may be selected by the user input 220. Similarly, the server processor 155 of the account management server 105 may select one of the plurality of accounts 110 stored within the account management server 105. The operation proceeds to step 328, identified in FIG. appears as "correct account", where the account confirmation is carried out. For example, the account manager displays the selected account on screen 225 with the acceptance or denial announcement. The selection may be with the user input 220 or alternatively, the non-user input 220 during a counting clock, before the out time, may signal the acceptance or denial, or the similar confirmation operation. If the negation is selected, the operation returns to select account, step 325. In one mode the correct count, step 328, is not present and the operation continues to select the amount of airtime 330. Then, in step 330, it is select an amount of airtime. For example, the account manager 215 can be adapted to select an amount of airtime from the account balance of the account selected for transfer based on a set of predetermined rules. The rule set, for example, may include an algorithm to calculate the amount to be transferred based on the account balance. Alternatively, the rule set may include decoding a value contained in a received message. Alternatively, Account Manager 215 may display the account balance for the selected account on screen 225 and the air time amount of the account balance may be selected by user entry 220. Account Manager 215 may also display a plurality of selectable values on the screen 225 and one may be selected by the user input 220. Similarly, the server processor 155 of the account management server 105 may select an air time amount from the account balance of the account selected for transfer based on a predetermined set of rules as described in the present invention. Then, the operation proceeds to step 333, the correct amount, wherein the selected quantity of confirmation of amount of airtime takes place. For example, the account manager displays the selected amount of airtime on screen 225 with the announcement for acceptance or denial. The selection can be made using user input 220 or alternatively it can be a user consent with time out before user input 220, or any other equivalent confirmation operation. If the negation is selected, the operation returns to select the amount of airtime, step 335. In one embodiment the correct amount, step 333, is not present and the operation proceeds to step 335. Then, in step 335, the operation Check the validation of the transfer. Validation, for example, can include verification that the selected account and the amount of airtime are correct. Alternatively, the validation may include the authorization of the airtime request coming from the server processor 155 of the account management server 105 or the account manager 215 of the communication device 200. The validation may also include a series of acknowledgments between the communication device 200 and the account management server 105 and / or the communication device it requests. When the validation is not correct in step 335, the operation returns to step 315, where the user can either accept the request or send a denial. When the validation is correct in step 335, the operation continues to step 340 in which the balance transfer of accounts is sent. The operation of step 340, for example, may include making a decrease in the account balance within the transmitting device and an increase in the account balance within the receiving device. The increase and decrease may occur only within each device or alternatively may be stored within the account management server 105 as well. Next, in step 345, the transfer of the account balance is confirmed. For example, confirmation messages may be sent from each of the transmitting or receiving devices to / from the account management server and vice versa. In one embodiment, the transfer confirmations are displayed on the screen of each of the transmitting or receiving device for notification and user interaction. The operation returns to the alert mode of step 300. Figure 4 is an operational flow diagram illustrating a mode of operation of the communication device of Figure 2. Specifically, Figure 4 illustrates the operation of the communication device 200 when the communication device 200 is a receiving device. As illustrated, the operation begins with step 400 in which, the communication device 200 is in the alert mode. The alert mode is typically a low battery leak mode in which, the communication device 200 is waiting for inputs. Next, in step 405, the operation requests the receipt of a user input for a balance transfer. For example, account manager 215 may receive a signal from user input 200 indicating the user's desire to initiate a request for an account balance transfer. When a user input for an account balance transfer is detected in step 405, the operation continues with step 410 in which, the communication device 200 sends an airtime request. For example, the communication device 200 may send a request for an account balance transfer directly to one of the plurality of communication device 130 through the network 125. Similarly, the communication device 200 may send a request for a balance transfer of accounts to the account management server 105 through the network 125. Those skilled in the art will appreciate that the request for an account balance transfer may also be sent through alternative sources not illustrated in the present, such as a secondary communication device or the like. Then, in step 415, the operation determines whether the request has been accepted or not. For example, the account administrator 215 of the transmitting device can display the received request from the receiving device on the display 225 and the user input 220 can be used to accept or reject the transfer request. Similarly, the account administrator 215 of the transmitting device can compare the information contained in the account balance transfer request, such as the identification of the applicants, with authorization information, such as the shared users 250 stored in the memory 230 and either accepting or rejecting the request. When the request is denied (rejected) in step 415, the operation continues to step 420 in which, the communication device 200 receives a negation through the network 125 and the negation is announced on the screen 225 of the request device or, otherwise, communicated to the applicant. The operation then returns to the alert mode of step 400. Returning to step 405, when no user input is detected to transfer the account balance, the operation proceeds to step 425 in which the operation asks for receipt of a Account balance transfer entry. For example, the receiving device may receive an account balance transfer from a transmitting device as previously described in FIG. 3. When a transfer input is not detected in step 425, the operation returns to the alert mode of step 400. When the request is accepted in step 415 or when an input for a transfer is received in step 425, the operation proceeds to step 430 in which, the count in the receiving device increases with the amount of airtime that is transferred. Then, in step 435, the transfer of account balance is confirmed. For example, confirmation messages can be sent from each of the transmitting and receiving devices to / from the account management server and vice versa. In one embodiment, the transfer confirmations are displayed on the screen of each transmitting and receiving device for notification and user interaction. The operation returns to the alert mode of step 400. Figure 5 is an operational flow diagram illustrating a mode of operation of the account management server 105 that operates within the account management system 100 of figure 1. operation begins with step 500 in which, the account management server 105 is in the alert mode. Then, in step 505, the operation asks for the reception of a request for an account balance transfer. The request, for example, can be received from one of the plurality of communication devices 130 through the network 125. When a request is not detected in step 505, the operation returns to the alert mode of step 500. When detecting a request in step 505, the operation continues with step 510 in which, the account management server 105 determines whether the request for transfer of account balance is from a transmitter. When the request is not from a transmitter in step 510, the operation continues to step 515 in which, the account management server 105 determines whether the request is from a receiver. When the request is not from a receiver in step 515, it is presumed that the request is an error and the operation returns to the alert mode of step 500. When the request is from a receiver, such as a communication receiving device in In step 515, the operation continues to step 520 in which, the account management server 105 determines whether the transfer is authorized by the transmitter associated with the account from which the balance transfer is required. For example, the account management server 105 may send an authorization request to the transmitter and await an authorization. Alternatively, the account management server 105 may have a transmitter authorization for one or more receiving devices, to allow the transfer of the account balance of one or more accounts. When the authorization is not granted in step 520, the operation continues to step 525 in which a denial of the transfer is sent. Preferably, the denial is sent to the requesting device which initiated the transfer request. The operation then returns to the alert mode of step 500. When an authorization is received in step 520 or the request is from a transmitter in step 510, the operation continues with step 530 in which, the account management server 105 determines whether the transmitter account is valid or not. For example, the account management server 105 determines whether the account, of which the balance transfer is required, is active in the system (ie, stored within the plurality of accounts 110). Similarly, the account management server 105 determines whether balance transfers are enabled in the associated account. When the account is not valid in step 530, the operation continues to step 535 in which a transfer denial is sent. Preferably, the negation is sent to both the requesting device and the transmitting device. The operation then returns to the alert mode of step 500. When the transmitter account is valid in step 530, the operation continues to step 540 in which, the account management server 105 determines whether the current account balance, for The account includes enough funds available to allow the transfer. When funds are not available, the operation returns to step 535 in which a denial is sent as previously described herein. When the balance is available in step 540, the operation continues with step 545 in which the transfer is initiated. The operation of step 545, for example, may include effecting a reduction of the account balance within the transmitting device and an increase in the account balance within the receiving device. The increase and decrease may occur only within each device or, alternatively, may be stored within the account management server 105 as well. Then, in step 550, the transfer of account balance is confirmed. For example, confirmation messages can be sent from each of the transmitting or receiving devices to / from the account management server and vice versa. In one embodiment, the transfer confirmations are displayed on the screen of each of the transmitting or receiving device for notification and user interaction. The operation returns to the alert mode of step 500. The present invention can be performed within an individual system or multiple systems communicating together. For example, systems can communicate with one or more multiple protocols in one or more countries. In one embodiment, one skilled in the art would recognize the ability to transfer blocks of time from a user in Country A to the user in Country B. The present invention can be realized in hardware, software, or a combination of hardware and software. A system, according to a preferred embodiment of the present invention, can be performed in a centralized mode in a computer system, or in a distributed mode where different elements are broadcast through various interconnected computer systems. Any type of computer system, or other apparatus adapted to carry out the methods described herein, is adequate. A typical combination of hardware and software could be a general-purpose computer system with a computer program that, when loaded and executed, controls the computer system so that it performs the methods described herein. The present invention can also be incorporated into a computer program product, which comprises all the features that enable the execution of the methods described herein, and which, when loaded on a computer system, is capable of carrying out these methods. The computer program or computer program means in the present context means any expression, in any language, code or annotation, of a series of instructions intended to cause a system, having an information processing capacity, to execute a function particular either directly or afterwards in either or both of the following a) conversion to another language, code, or annotation; and b) reproduction in a different material form. Each computer system may include, among other things, one or more computers and at least one computer readable medium that allows a computer to read data, instructions, messages or message packets, and other computer-readable information from the readable media. computer. The computer-readable medium may include non-volatile memory, such as ROM, temporary memory, disk drive memory, CD-ROM, and other permanent storage. Additionally, a computer means may include, for example, volatile storage such as RAM, buffers, cache memory, and network circuits. Moreover, the computer readable medium may comprise computer readable information in a transient state medium such as a network link and / or network interface, which includes a wired network or a wireless network, which allows a computer to read said information. computer readable information. Although specific embodiments of the invention have been described, those skilled in the art will understand that changes can be made to specific embodiments without departing from the spirit and scope of the invention. The scope of the invention should not be restricted, therefore, to the specific embodiments, and it is intended that the appended embodiments cover any and all such applications, modifications, and embodiments within the scope of the present invention. Here various exemplary embodiments of the present methods and systems are presented and, these examples are intended to illustrate the potential executions of various modalities and / or aspects of the present methods and systems. It can be appreciated that said examples are intended primarily for purposes of illustration. No particular aspect or aspects of the exemplary embodiments of the method and system described herein are intended to limit the scope of the present invention. The terms "computer" and "computer system" as used herein may include, without limitation, one or more of the following devices: a wireless personal computer, a laptop, a personal digital assistant (PDA), a pager wireless, a "computer" can be a microcomputer, minicomputer, laptop, personal data assistant, cell phone, two-way locator, processor, and any other computerized device capable of transmitting, receiving and / or processing data over a network shared. The term "computer readable medium" is defined herein as understood by those skilled in the art. It can be appreciated that several method steps described herein can be executed, in certain embodiments, using instructions stored in a computer readable medium or means that operate a computer system to execute the steps of the method. A computer readable medium may include, for example, memory devices such as floppy disks, compact discs of both varieties, read only and write, optical disk drives, and hard disk drives. A computer-readable medium can also include memory storage that can be physical, virtual, permanent, temporary, semi-permanent and / or semi-temporary. A computer readable medium may also include one or more data signals transmitted on one or more carrier waves. It can be appreciated that, in some embodiments of the present methods and systems described herein, a single component can be replaced by multiple components, and multiple components can be replaced by a single component, to execute a particular function. Except in the case where said substitution would not be operative to practice the present methods and systems, said substitution is within the scope of the present invention. Although the particular embodiments of the invention have been described for the purpose of illustrating the invention and not for the purpose of limiting the same, those skilled in the art will appreciate that numerous variations of the details, materials and arrangements of parts can be made within the principle and scope of the invention without departing from the invention as described in the appended claims. A particular nomenclature choice for identifying an element or elements of the present methods and systems, for example, is solely for convenience of description.

Claims (1)

  1. NOVELTY OF THE INVENTION Having described the present invention, it is considered as a novelty and, therefore, the content of the following is claimed as a priority: CLAIMS 1. - An account management system comprising: an account management server for storing and operating in a plurality of accounts, each account includes information of the account user and an account balance comprising a measurement of communication time, wherein The account manager is configured to transfer at least a portion of an account balance associated with a first account to a second account. 2. - The system according to claim 1, wherein the account user information comprises a plurality of shared users. 3. The system according to claim 1, characterized in that the account balance comprises a total balance. 4. The system according to claim 1, characterized in that the account balance comprises a plurality of balances for different account services. 5. The system according to claim 1, characterized in that the account balance comprises a financial equivalent of communication time. 6. The system according to claim 1, characterized in that the account management server converts the measurements of the communication time into financial equivalents. 1 . - The system according to claim 1, characterized in that the account management server tracks the use of each of the plurality of accounts and decreases the associated account balance as required. 8. The system according to claim 1, characterized in that the account management server increases the account balance associated with the account as the credits are received for that account. 9. The system according to claim 8, characterized in that the account management server increases an account balance in response to the reception of one or more of: a bank loan, a purchase on airtime credit, a payment of account, and another financial entry. 10. The system according to claim 1, characterized in that each account also includes authorization information of the account to access the account and use the account balance. 11. The system according to claim 10, characterized in that the account authorization comprises one or more of a key, voice recognition, and system recognition. 12. The system according to claim 10, characterized in that the authorization comprises an over-the-air authorization when a communication device is authenticated for use. 13. The system according to claim 10, characterized in that the authorization comprises keyboard entries recognized by the account management server. 14. The system according to claim 10, further comprising a transaction point operatively coupled to the account management server to allow users to manage multiple accounts. 15. - An account management method comprising: storing a plurality of accounts, each account includes information of the account user and an account balance comprising a communication time measurement; and transfer at least a portion of an account balance associated with a first account to a second account. 16. The method according to claim 15, which also includes the authorization to access an account to use the account balance. 17. - The method according to claim 16, characterized in that the authorization comprises over-the-air authorization when a communication device is authenticated for its use. 18. The method according to claim 16, characterized in that the authorization comprises the recognition of keyboard entries. 19.- A computer program stored on a computer-readable medium, the program comprises instructions for: storing and operating in a plurality of accounts, each account includes user information of the account and an account balance comprising a time measurement Communication; and authorize a transfer of at least a portion of an account balance associated with a first account to a second account. 20. The program according to claim 19, characterized in that the computer readable medium comprises at least one disk, a device, and a propagated signal.
MXPA/A/2006/006581A 2003-12-08 2006-06-08 System for account management and method therefor MXPA06006581A (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US60/527,850 2003-12-08
US10737322 2003-12-16

Publications (1)

Publication Number Publication Date
MXPA06006581A true MXPA06006581A (en) 2007-04-20

Family

ID=

Similar Documents

Publication Publication Date Title
US20050125315A1 (en) System for account management and method therefor
US10127541B2 (en) Payment card terminal for mobile phones
US7331518B2 (en) Transaction processing systems and methods
CN100401326C (en) Method and module for blocking respectively unblocking of money accounts
US7024174B2 (en) Method and system for data management in electronic payments transactions
CN101185282B (en) System, device and method for wireless subscriber billing and distribution
US7831246B1 (en) Mobile merchant
US8412155B2 (en) Systems and methods to accelerate transactions based on predictions
US6934529B2 (en) Replenishment of pre-paid wireless telephone accounts using short message service (SMS)
US9864991B2 (en) Method and apparatus for secure transaction management
AU2010229107B2 (en) Cardholder verification rule applied in payment-enabled mobile telephone
US20010005832A1 (en) Transaction system and method
CN101454795A (en) Mobile person-to-person payment system
KR20060135767A (en) Application-based value billing in a wireless subscriber network
CN101288092A (en) Mobile account management
MXPA03011821A (en) Convergent communications platform and method for mobile and electronic commerce in a heterogeneous network environment.
KR20110020820A (en) Monetary transfer approval via mobile device
US20080057916A1 (en) Real-time, interactive balance check for wireless service
US8924287B1 (en) System and methods for mobile electronic funds transfers
RU2371877C2 (en) System allowing operator to render services of financial transactions, and methods of implementing such transactions
KR20040094249A (en) Method and System for Providing Credit Card Payment Service by Using Short Message
MXPA06006581A (en) System for account management and method therefor
Salvi et al. Dial m for money
MXPA04012262A (en) System for account management and method therefor.
KR100521993B1 (en) Card terminal which has advanced/deferred payment function, method for settling advanced/deferred payment