EP1922681B1 - Gestion de compte mobile - Google Patents
Gestion de compte mobile Download PDFInfo
- Publication number
- EP1922681B1 EP1922681B1 EP06779120A EP06779120A EP1922681B1 EP 1922681 B1 EP1922681 B1 EP 1922681B1 EP 06779120 A EP06779120 A EP 06779120A EP 06779120 A EP06779120 A EP 06779120A EP 1922681 B1 EP1922681 B1 EP 1922681B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- transaction
- messages
- message
- mobile
- incoming
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000000034 method Methods 0.000 claims description 33
- 238000012546 transfer Methods 0.000 claims description 15
- 238000004891 communication Methods 0.000 claims description 11
- 230000010267 cellular communication Effects 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 8
- 230000004044 response Effects 0.000 claims description 8
- 238000012790 confirmation Methods 0.000 claims description 3
- 238000009877 rendering Methods 0.000 claims 1
- 238000007726 management method Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 6
- 238000012384 transportation and delivery Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 230000004913 activation Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000012550 audit Methods 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 2
- 238000000151 deposition Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000001105 regulatory effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000013474 audit trail Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000008021 deposition Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000003909 pattern recognition Methods 0.000 description 1
- 230000000135 prohibitive effect Effects 0.000 description 1
- 230000009711 regulatory function Effects 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 230000004936 stimulating effect Effects 0.000 description 1
- 230000008685 targeting Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/326—Payment applications installed on the mobile devices
- G06Q20/3265—Payment applications installed on the mobile devices characterised by personalisation for use
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
- G06Q20/123—Shopping for digital content
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
- G06Q20/3229—Use of the SIM of a M-device as secure element
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
- G06Q20/3255—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks using mobile network messaging services for payment, e.g. SMS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/70—Administration or customization aspects; Counter-checking correct charges
- H04M15/705—Account settings, e.g. limits or numbers or payment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/20—Technology dependant metering
- H04M2215/2026—Wireless network, e.g. GSM, PCS, TACS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/32—Involving wireless systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/70—Administration aspects, modify settings or limits or counter-check correct charges
- H04M2215/7009—Account settings, e.g. users, terminals, limits, numbers or payment
Definitions
- the invention relates to the management of secure transactions in a wireless communications network.
- the invention relates to the secure transfer of messages representing the exchange of title to monetary assets.
- banking facilities A large proportion of the world's population is not served by conventional banking facilities. There are limited facilities for transferring money between 'enterprises' (e.g. business to business) or between individuals (one location to another). Consequently, cash must often physically change hands. This lack of banking facilities affects small-scale business men and women in emerging markets particularly strongly.
- microcredit or “microfinance”
- microfinance is seen as being central to stimulating economic activity in emerging markets.
- the cellular network provides the platform on which financial services can be delivered, far exceeding the reach of landlines, bank branches and automated teller machines (ATMs) which are largely restricted to urban areas.
- ATMs automated teller machines
- SMS short message functionality
- CelPay Fundamo Elevator deployed in Zambia as CelPay, targeting high end customers and based on SIM protocol. Registered customers are provided with a CelPay SIM card.
- the SIM card is programmed to generate a new menu once inserted into a suitable mobile telephone handset.
- Celpay accounts are credited either via a transfer from a conventional bank account, or by directly depositing cash or cheque into a Celpay partner bank.
- the CelPay user wishes to make a payment, he uses the CelPay menu on his handset to input the amount to be paid to the merchant or supplier. He is prompted to authenticate the transaction by inputting a secure Personal Identification Number (PIN). Both payer and payee receive confirmation of the transaction (in the form of an SMS message).
- PIN Personal Identification Number
- Globe G-Cash in the Philippines uses SMS notification in relation to conventional "straight money transfer" person to person via outlet agents.
- a G-Cash account is provided for each registered user. SMS messages requesting payment in G-Cash to recipient accounts are sent to a short code number (a central service) for processing (e.g. to pay a bill or to buy call credit).
- a short code number a central service
- Smart Money also implemented in the Philippines, uses 'smart credits' as electronic payments.
- the Smart Money application makes use of an electronic-wallet card that is linked to a mobile phone account.
- the card can be used like a debit card.
- customers with bank accounts can, via SMS, load money onto the card, transfer money between cards, track transactions, pay bills etc.
- a mobile-phone enabled account management system for maintaining a plurality of virtual accounts in a cellular communications system, the cellular communications system carrying messages between mobile terminals and each mobile terminal including a data card with a unique identifier, the account management system including:
- the account management system is thus a mobile phone-enabled account management platform.
- This system has the functionality to allow users to move money at both at a business-to-business level and at a person-to-person level, via mobile terminals (in particular, through the use of widely-available GSM mobile phones).
- the system makes use of specially developed software running on a mobile phone's SIM card to conduct the conversation with the end user and uses short message service (SMS) to communicate between the SIM card and a central server.
- SMS short message service
- a mobile-phone enabled method for maintaining a plurality of virtual accounts in a cellular communications system the cellular communications system carrying messages between mobile terminals and each mobile terminal including a data card with a unique identifier, the method comprising:
- the platform By creating a series of virtual accounts within a standard deposit account operated on behalf of individual customers and organisations such as, microfmance institutions (MFI), the platform enables individual users, service providers and agents to move 'allocated funds' between these virtual accounts by instructing the account manager to do so, for example via SMS.
- MFI microfmance institutions
- Value can be moved between accounts within the virtual account system when instructions are received by SMS, say. For example, an individual can request value to be moved between his virtual account and the corresponding virtual account of a merchant from which he is buying goods or services.
- the value represented by the virtual account can be encashed at any suitable registered agent, such as an airtime reseller or any location that has suitable 'cash flow' (shops, petrol stations, etc). These agents are much more widespread and convenient to access than bank outlets. The process is quick and transaction costs should be lowered substantially. In particular, this arrangement also obviates the need for the physical movement (and (re)counting) of 'cash' and so offers security benefits for the user.
- any suitable registered agent such as an airtime reseller or any location that has suitable 'cash flow' (shops, petrol stations, etc).
- Using mobile technology to make financial transactions faster, cheaper, and more secure facilitates the delivery of financial services in emerging markets where other financial transaction mechanisms are unattractive.
- the invention also facilitates the wider transfer of money between migrant workers and their families.
- the platform is provided with a security layer.
- the security layer may be implemented at each stage of a transaction. This layer is built into the Account Manager to protect against fraudulent use.
- the security of the exchange of information between individual users, service providers and agents i.e. a handset with an appropriate SIM installed
- the account manager may be enhanced by requiring encryption of the message (e.g. SMS message) using a key that is shared between both parties.
- the SIM used in the handset may be provided with a SIM Toolkit (STK) application for encrypting and decrypting such messages.
- STK SIM Toolkit
- security may be provided using other ID and security checks independent of the SIM or handset.
- alternate checks include: Personal Identification Numbers (PINs); username/password combinations; biometric parameters (such as iris scans, fingerprinting, voice pattern recognition etc.).
- PINs Personal Identification Numbers
- biometric parameters such as iris scans, fingerprinting, voice pattern recognition etc.
- IVR interactive voice response
- Voice Recognition Voice Recognition
- a reporting means for providing a reporting functionality that allows movement of value between the virtual accounts to be tracked.
- the reporting means may further track encashment.
- the reporting means thereby provides an audit trail as may be required by regulatory authorities.
- FIG. 1 shows schematically a network in which the invention may be used.
- the figure shows a cellular network.
- Mobile terminal 1 is registered with GSM/GPRS or UMTS (3G) mobile telecommunications network 3.
- the mobile terminal 1 may be a handheld mobile telephone, a personal digital assistant (PDA) or a laptop computer equipped with a datacard.
- PDA personal digital assistant
- the mobile terminal 1 communicates wirelessly with mobile telecommunications network 3 via the radio access network (RAN) of the mobile telecommunications network 3, comprising, in the case of a UMTS network, base station (Node B) 5, and radio network controller (RNC) 7. Communications between the mobile terminal 1 and the mobile telecommunications network 3 are routed from the radio access network via GPRS support nodes (SGSN) 9, which may be connected by a fixed (cable) link to the mobile telecommunications network 3.
- RAN radio access network
- Node B base station
- RNC radio network controller
- a multiplicity of other mobile terminals is registered with the mobile telecommunications network 3.
- These mobile terminals include mobile terminals 11 and 13.
- the terminals 11 and 13 communicate with the mobile telecommunications network 3 in a similar manner to the terminal 1, that is via an appropriate Node B 5, RNC 7 and SGSN 9.
- the mobile telecommunications network 3 includes a gateway GPRS support node (GGSN) 17 which enables IP-based communications with other networks, such as the Internet 19 via an appropriate link 21.
- GGSN gateway GPRS support node
- a multiplicity of terminals are connected to the Internet (by fixed or wireless links), and a PC terminal 23 and a PDA terminal 25 are shown by way of example.
- Each of the mobile terminals 1, 11 and 13 is provided with a respective subscriber identity module (SIM) 15.
- SIM subscriber identity module
- the mobile telecommunications network 3 itself stores details of each of the SIMs issued under its control.
- a terminal 1, 11, 13 is authenticated (for example, when the user activates the terminal in the network with a view to making or receiving calls) by the network sending a challenge to the terminal 1,11,13 incorporating a SIM 15, in response to which the SIM 15 calculates a reply (dependent on the predetermined information held on the SIM - typically an authentication algorithm and a unique key Ki) and transmits it back to the mobile telecommunications network 3.
- the mobile telecommunications network 3 includes an authentication processor 17 which generates the challenge and which receives the reply from the terminal 1, 11, 13.
- the authentication processor uses information pre-stored concerning the content of the relevant SIM 15, the authentication processor calculates the expected value of the reply from the mobile terminal 1, 11, 13. If the reply received matches the expected calculated reply, the SIM 15 and the associated mobile terminal are considered to be authenticated.
- the terminal communicates wirelessly with the mobile telecommunications network 3 via the network's radio access network, although this is not essential.
- the terminal may communicate with the network via the fixed telephone network (PSTN), via a UMA "access point" and/or via the Internet.
- PSTN fixed telephone network
- UMA UMA "access point”
- the Internet may also be provided with a SIM 15 under the control of the network.
- the SIM 15 used by the terminal 1,11,13,23,25 may be a SIM of the type defined in the GSM or UMTS standards specifications, or may be a simulation of a SIM - that is, software or hardware that performs a function corresponding to that of the SIM.
- the SIM may be in accordance with the arrangement described in WO-A-2004 036513 .
- the authentication process being described does not necessarily authenticate the human identity of the user.
- mobile telecommunication networks have pre-pay subscribers who are issued with SIMs in return for pre-payment, enabling them to use network services.
- the identity of such pre-pay subscribers may not be known by the network. Nevertheless, such a user cannot make use of the network until the network has authenticated the user's SIM - that is, has confirmed that such user is a particular user who has a particular pre-paid account with a network.
- the network shown in Figure 1 comprises both the mobile telecommunications network 3 and the Internet 19 (which itself comprises a multiplicity of other networks).
- short messages or "SMS messages” as used in relation to the embodiments means short messages as defined in the GSM or 3G standard specifications. Such messages are commonly in the form of text messages of limited maximum length, but they can have other forms, such as in the form of binary data, or may contain configuration data for changing the functional parameters of a mobile.
- SMS messages as used in relation to the embodiments means short messages as defined in the GSM or 3G standard specifications. Such messages are commonly in the form of text messages of limited maximum length, but they can have other forms, such as in the form of binary data, or may contain configuration data for changing the functional parameters of a mobile.
- the invention is not limited to the transmission of messages of this "short message" type.
- Short messages may be sent to or from mobiles such as the mobiles 1,11,13 and the others belonging to the network 3.
- short messages may be sent to or from "short message entities" (SMEs) such as shown at 20,20A,20B.
- SMEs short message entities
- These SMEs may be in the form of terminals of various sorts such as fixed terminals for sending short messages of various types to mobiles and for receiving short messages from mobiles.
- the SMEs may be in the form of terminals associated with banking computers or computers of other types generating information (commercial information, for example) for transmission to mobiles and for receiving short messages in response from mobiles, but may be of many other types, such as application servers of various types.
- the network 3 has a short message service centre (SMSC) 26 associated with it.
- SMSC short message service centre
- the SMEs 20,20A,20B are connected to the SMSC 26 by fixed networks 30 of suitable type.
- a mobile wishes to send a short message, it will do this via the SMSC 26 of its network 3.
- the SMSC 26 of its network 3.
- the SMSC 26 carries the address of the local SMSC (this address is automatically generated by the sender), together with the address of the intended destination of the short message.
- the local SMSC receives the short message, it then reads the address (the MSISDN or Mobile Station ISDN number or telephone number of the intended destination) and despatches the short message accordingly.
- the SMS messages may be secured and authenticated in accordance with the arrangement described in co-pending patent application publication No. GB-A-2415574 .
- the invention allows the straightforward transfer of value between customers, where each customer has a respective virtual account provided on the platform.
- account transactions are conducted wholly over a telecommunications network (for instance a GSM network).
- An exchange of SMS transaction messages causes the transfer of funds between one customer account and another customer account, each account being managed by the account management system, thereby allowing money to be sent home or up country without the security risks normally involved with such activities.
- the customers only require a SIM card to be able to operate such virtual accounts, the SIM card being inserted in a suitable terminal (generally a mobile phone handset) in order to connect to the telecommunication network.
- FIG. 2 illustrates the interactions between "actors" in a microfinance system.
- a virtual account management system in accordance with the present invention may be installed in the Data Centre such that customers and operators can access the facilities either through mobile telephone handsets or over a network link (either leased line or internet).
- Each customer's virtual account has an associated SIM inbox within which recent transactions are preferably stored, thereby representing the current balance of the virtual account.
- VPN virtual private network
- Cisco 3000 a virtual private network
- the VPN concentrator allows the creation of a VPN tunnel for the development and administration of the data stored on the data centre remotely.
- provision of a VPN facilitates access by individual organisational partners/customers (eg. microfinance institutions (MFIs), Airtime Dealerships acting as Agents) to their core accounts using an internet connection.
- MFIs microfinance institutions
- Airtime Dealerships acting as Agents an internet connection.
- SMS transaction messages may also be directed to an SMSC bureau which routes SMS messages as packets through the internet (as, for example, e-mail under the SNMP, Simple Network Mail protocol).
- the virtual account management system may optionally be accessed via one or more channels within a range of complimentary channels including the Web, GPRS, Unstructured Supplementary Service Data (USSD), and Voice.
- GPRS General Packet Radio Service
- USSD Unstructured Supplementary Service Data
- SMS transaction messages are used to withdraw and deposit cash in a process facilitated by the provision of an Agent account.
- Approved agents of the account management system such as telephone credit resellers (or shop owners), are provided with further menu facilities to allow them to verify the withdrawal and/or deposition of physical cash with the agent.
- the client may buy goods directly without the use of physical cash by transferring funds to a Merchant account.
- the merchant account is a virtual account management system account provided to merchants to allow the sale of goods and services in return for fund transfer from a client account to the merchant.
- a typical transaction may be illustrated by referring to the elements of Figure 3 .
- a mobile phone user initiates the transaction by navigating through menus displayed on the screen of his mobile phone 302 to a funds transaction application on the SIM card (installed in the phone 302). Similarly, other users also carry out transactions on the system using their mobile phones 304,306. The user then chooses the appropriate transaction from a funds transaction application menu and enters the requested information such as destination account, amount, PIN, etc.
- the information is packaged into an encrypted message and then sent via SMS to a Transaction Processor 340.
- the encrypted message must first pass through the network operator's short message service centre - SMSC, 310 and an SMS service module 330. The connection from the mobile phones to the SMSC is made over the mobile network.
- MQs can work across computers and allows the two entities at either end to work independently. One entity submits a message, without waiting for a reply, and the other receives and processes it at a later time.
- the SMS service module 330 can continue to receive SMS messages and relay them to a queue while the Transaction Processor 340 is temporarily turned off for maintenance.
- the Transaction Processor 340 is triggered by events such as the arrival of an incoming message or delivery notification, notification of SMSC acceptance of an outgoing message, timer expiration or external request. It determines the correct response to the event and carries it out.
- the Transaction Processor 340 can connect simultaneously to more than one SMSC 310,320. This allows for differences in the functionality of different SMSCs.
- the architecture also allows for multiple SMS Services 330, potentially spread across a plurality of host computers 300, with each SMS Service 330 connected to one or more SMSCs. It also allows for multiple Transaction Processors 340 for scalability.
- the Transaction Processor 340 is responsible for accepting incoming requests of different types and handling them through to completion. Each incoming request initiates a new transaction. Before completing, the new transaction may involve one or more steps over a period of time (in some cases, as long as 45 minutes).
- a customer initiating a Send Money transaction When the Transaction Processor 340 receives the request message the Processor verifies the message, queries the main database 350 and, if successful, sends a reply to the customer's mobile phone 302 confirming that the transaction has taken place. Some seconds or minutes later the Transaction Processor 340 receives confirmation of delivery of the reply, confirms the transaction to the transaction database 350 and sends a notification to the recipient.
- an SMS message is sent from the SIM to the Transaction Processor 340.
- the Transaction Processor 340 decrypts and decodes the incoming message to discover that it is an activation request and that it includes the correct PIN for that phone number.
- the Transaction Processor 340 sends a further, text SMS message to the phone 302 containing the, now activated, SIM telling the user that activation was successful. All these events - the initial message, the notification from the SMSC 310 of the acceptance of the initial menu messages and each of the delivery notifications are grouped together by the Transaction Processor 340 as a single application-level transaction.
- the Transaction Processor 340 makes extensive use of the Microsoft [RTM] Enterprise Library, the transactions being MS-DTC level transactions and the incoming events being communicated by means of MSMQ messages.
- the Transaction Processor 340 is arranged to ensure that everything from reading a message from a queue, the resulting database processing and any sent messages are all covered by a single, respective, MS-DTC transaction. Therefore, should any error occur during processing, all the work is undone by a single rollback and can be re-started: as a result this implementation is able to cope with database deadlocks.
- the Transaction Processor 340 is preferably adapted to nest transactions: using an outer transaction to obtain the next event and an inner transaction to process it. If the inner transaction fails the outer one is preferably allowed to proceed on the grounds that having it fail merely causes the event to be read again and the same error to occur. Only if the inner transaction results in a retryable error does the outer one fail. There is a mechanism for limiting the number of such retries.
- the Message Security component 380 is responsible for encrypting and decrypting messages sent between the SIM application (not shown, resident on the user's mobile phone 302) and the Transaction Processor 340. As part of the decoding PINs (and passwords) is verified and new PINs are encrypted in such a way that unencrypted PINs and keys are not exposed outside the Message Security component 380. Each SIM uses a different key for encrypting and decrypting messages. Verification that the appropriate key was used is taken as proof that a message originated on a particular mobile phone 302.
- Messages are preferably delivered to the user's mobile phone SIM application as (binary) message programs.
- This provides a totally secured two-way communication channel, robust against such security threats as "spoofing" of the Account Manager Servers.
- SIM card applications are prevented from receiving such SMS messages while menus are being displayed on the screen of the mobile phone 302.
- the system can be configured such that messages sent from the server are sent to SIMs as plain text messages.
- the Message Security component 380 is a COM+ component running as a standalone COM+ server application.
- the component 380 provides methods for obtaining date and generation information associated with an encrypted PIN; obtaining date and purpose information associated with an encrypted item; encrypting master keys; generating a SIM specific key according to a predefined master key algorithm; encrypting passwords; and verifying passwords against encrypted passwords.
- the component 380 uses COM+ role security to limit particular interface methods to particular users. For example, only the service operator can decrypt and encrypt messages for the funds transaction SIM application but the web account user 370 can create PINs.
- the particular encryption scheme adopted is selected in accordance with the capabilities of the SIMs used. It is however preferred that all SIMs share a single public key (provided the SIMs support public key encryption). Where this is not possible a SIM specific key may instead be generated from a single shared symmetric key and ID information unique to the SIM. In the latter case, the reliability of the security depends upon the secrecy of the shared symmetric key.
- FIG. 4 illustrates the stages in the operation of this embodiment of the invention.
- the MFI maintains a core virtual account in the Data Centre.
- virtual accounts are provided for different roles within a microfinance scheme: field officers, who distribute small loans within communities; clients, virtual account holders who receive loans from the MFI; and group treasurers, whose job it is to verify that loans are being repaid correctly.
- SMS transaction message When the MFI approves the release of funds for distribution as loans by a field officer, a suitable SMS transaction message is sent.
- the SMS transaction message effects transfer of funds to the field officer's account.
- the field officer in turn disperses loans within a group of client accounts.
- the client accounts are credited with an approved sum, again using an SMS transaction message.
- Clients of a particular MFI agree to repay their loan by transferring funds at a pre-determined rate to the account of the group treasurer. This activity is also effected by exchange of secure SMS messages. Finally the group treasurer, once he is satisfied that the correct repayments have been made, transfers the appropriate sum back to the core account of the MFI.
- the system of the invention provides two-way secure communication to the SIM via SMS transaction messages. A unique key is provided for each SIM. The system therefore provides complete transparency in terms of which SIM initiates which transaction, facilitating audit and other regulatory functions.
- the interface operating on each enabled handset includes an "interpreter".
- the interpreter is an application similar to a browser.
- each SMS transaction message requesting an account management transaction is constructed through the use of a dialog menu presented by the interpreter, in which the customer is asked to indicate: the target account, the value to be transferred (or withdrawn), the date of transfer and to input security data for authentication.
- the interpreter is fully customisable over the air. Menus, even the language displayed, can be changed remotely.
- Each menu item action is effected by a respective mini-programme (for example, Java script running on the browser or an applet).
- the interface is, furthermore, responsive to server driven events.
- the system provides for the different requirements of users of the system.
- the system can be customised with appropriate menus and options.
- Such updates are conveniently effected by over-the-air updates.
- SMSC short message service centre
- the SMSC is coupled to the switched network environment by means of an SMSC gateway.
- the SMS transaction message is then transferred by the SMS service across the switched network environment to a transaction processor which interprets the SMS transaction message and, once the SMS has been authenticated, alters the data representing each account affected by the SMS transaction message accordingly, the data being stored in a data centre.
- the user is presented with an account inbox, separate from the conventional SMS inbox, whereby he can maintain a transaction history.
- the account inbox is only accessible through the authentication functionality of the SIM inserted in the handset, so the integrity of the transaction history is assured by SIM authentication.
- a corresponding transaction completed message is then generated for each account affected by the transaction and the transaction completed message is then encapsulated in an encrypted message which can only be opened correctly by a mobile terminal having a SIM card with the correct decryption key.
- the transaction completed message is electronically signed with a key specific to the SIM.
- the encrypted messages are formatted as SMS messages and delivered via the SMS service to the transaction requesting party and the account owner of the affected account. These SMS messages are delivered to the account inboxes for the respective accounts, so that only the verified user of the SIM can view the transaction status.
- SMSC Short Message Service Centres
- the service is expandable (supporting multiple SMSCs) and scaleable (storing different phone numbers on the same SMSC, thereby allowing more than one microfinance institution).
- the service is preferably also implemented so that it is agnostic with respect to the network infrastructure bearing the transaction messages.
- a significant capability for the implementation is the ability to remotely host the Servers.
- firewall restrictions limit the number of network locations where simultaneous access can be obtained to more than one SMSC.
- This short-coming can be addressed by implementing a utility application, a message forwarder (see Fig 5 ), for forwarding MQ messages from a message queue on one computer to the message queue on another computer using protocols that are adapted to cross such firewalls. Since communication between the Transaction Processor 340 and the SMSC 310,320 starts with MQ messages, this utility enables the system to be located elsewhere.
- the message forwarder must be capable of sending and receiving MQ messages across the firewall preventing incoming connections.
- the Message Forwarder consists of two parts, a web service and a client implemented as, for example, a Windows NT Service.
- the client runs on the computer within the firewall (Computer A) and initiates all calls to the web service running on Computer B. Since web service calls use HTTP, this is allowed.
- Figure 5 shows how the parts interconnect.
- the system is capable of imposing cost-based routing policies ensuring that SMS transaction messages are routed according to predetermined criteria, such as lowest financial cost, shortest distance, or fastest service.
- the system imposes policies that are updated dynamically, thereby ensuring that the operator can provide the service at least cost.
- a local mobile service provider will be used for Inbound SMS messages. Primarily, this permits the provision of SMS services that are cost-free for the user. This does also keep costs of SMS traffic low.
- the database and logic of the virtual account manager are preferably provided with extension applications to cater for currency conversions, language and regulatory differences (e.g. anti-fraud measures).
- the architecture of the system means that one-to-many transactions are relatively simple to implement: thus, for example, a single agent transaction can be used to top up three separate virtual accounts.
- the Transaction Processor is provided with an SMS multiplexer facility that determines which of several possible SMSCs should be used to deliver any given SMS message.
- the Transaction Manager In addition to facility for handling transaction request from user SIMs and from website access, the Transaction Manager also conveniently has a facility for handling requests for airtime from prepay customers (either for the user himself or on behalf of another user and/or phone). Such requests could originate from within the transaction application menu or from access to a suitable webpage.
- the system may request or infer the physical location of the user.
- this location information e.g. the Cell ID
- the system can ensure that information provided to the user is relevant to that user's physical context. This allows handsets to be used as a community building tool - advertising locally available resources, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Computer Networks & Wireless Communication (AREA)
- General Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Signal Processing (AREA)
- Finance (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Claims (18)
- Système de gestion de compte intégré à un téléphone mobile pour actualiser une pluralité de comptes virtuels dans un système de communications cellulaires, le système de communications cellulaires servant à acheminer des messages entre des terminaux mobiles (302, 304, 306) et chaque terminal mobile englobant une carte de données laquelle possède un identifiant inédit, le système de gestion de compte comportant :des moyens de messagerie (330) qui sont conçus pour recevoir des messages de transaction entrants provenant de terminaux mobiles utilisant le système de communications, les messages entrants englobant l'identifiant inédit du terminal mobile expéditeur, et pour transmettre, en réaction, des messages de transaction sortants vers des terminaux mobiles ;un processeur de transactions (340) qui est couplé aux moyens de messagerie par l'intermédiaire d'une paire de files d'attente de messages (332, 334) et conçu pour interpréter des messages de transaction entrants et pour produire des instructions de transaction correspondantes ;des moyens sécuritaires de messages (380), couplés au processeur de transactions (340), lesquels authentifient les messages de transaction entrants en comparant l'identifiant inédit inclus aux entrées figurant dans une liste de comptes virtuels valides ; etune interface à mémoire de données de transaction, couplée au processeur de transactions (340), par le biais de laquelle le processeur de transactions communique avec une mémoire de données (350), l'interface étant conçue pour acheminer des instructions visant à modifier des données conservées dans un ou plusieurs comptes virtuels valides stockés dans la mémoire de données, et pour acheminer des messages de terminaison de transaction à partir de la mémoire de données vers le processeur de transactions (340) lorsque la modification est achevée ;cas dans lequel les files d'attente de messages (332, 334) comportent une file d'attente Réception et une file d'attente Envoi, la file d'attente Réception étant conçue pour mettre en file d'attente des messages reçus à partir du processeur de transactions (340) et la file d'attente Envoi étant conçue pour mettre en file d'attente des messages envoyés vers le processeur de transactions (340) ;cas dans lequel le processeur de transactions (340) est également conçu pour interpréter des messages de terminaison de transaction et pour produire des messages correspondants de terminaison de transaction interprétés vers les moyens de messagerie (330) par l'intermédiaire de la file d'attente Réception ;cas dans lequel chaque message de terminaison de transaction interprété englobe des informations sécuritaires générées à partir d'identifiants inédits de comptes virtuels modifiés, les moyens de messagerie étant conçus pour canaliser les messages sortants générés à partir des messages de terminaison de transaction interprétés vers des terminaux mobiles correspondants ; etcas dans lequel chaque message sortant reçu se présente sous un format qui exige la saisie d'une clé inédite à partir de la carte de données insérée dans le terminal mobile, ce qui permet par conséquent de garantir que le message sortant peut uniquement être lu en présence d'une carte de données avec une clé inédite laquelle concorde avec les informations sécuritaires figurant dans le message sortant.
- Système selon la revendication 1, les moyens de traitement de transactions comportant en outre un composant de compte rendu pour procurer une fonctionnalité de compte rendu de sorte que tout mouvement de valeur entre les comptes virtuels fasse l'objet d'un suivi.
- Système selon la revendication 1 ou la revendication 2, les moyens de traitement de transactions offrant une pluralité de comptes virtuels, chaque compte représentant un rôle, parmi un certain nombre de rôles distincts, dans le cadre d'un plan de microfinancement.
- Système selon l'une quelconque des revendications 1 à 3, les moyens de traitement de transactions possédant une fonctionnalité supplémentaire, et cas dans lequel l'accès à distance à la fonctionnalité supplémentaire est protégé encore davantage en raison de la nécessité d'établir un réseau privé virtuel.
- Système selon l'une quelconque des revendications 1 à 4, les moyens de messagerie étant conçus pour recevoir directement des messages de transaction entrants en provenance d'un composant SMSC du système de communications.
- Système selon l'une quelconque des revendications 1 à 4, les moyens de messagerie étant conçus pour recevoir des messages de transaction entrants en provenance d'une entité de messages courts, laquelle est conçue pour intercepter des messages de transaction entrants en provenance du système de communications cellulaires et pour délivrer les messages de transaction entrants via une interface internet.
- Système selon l'une ou l'autre des revendications 5 ou 6, le trajet emprunté par chacun des messages de transaction entrants étant déterminé sur une base de coûts, en conformité avec un ensemble prédéterminé de critères portant sur les coûts.
- Système selon la revendication 7, les critères étant mis à jour de façon dynamique en réaction à des changements opérés dans les coûts.
- Système de microfinancement comprenant:le système de gestion de compte selon l'une quelconque des revendications 1 à 8 ; etun combiné de téléphone mobile (302) agencé pour supporter le système de gestion de compte.
- Procédé intégré à un téléphone mobile pour actualiser une pluralité de comptes virtuels dans un système de communications cellulaires, le système de communications cellulaires servant à acheminer des messages entre des terminaux mobiles, et chaque terminal mobile englobant une carte de données laquelle possède un identifiant inédit, le procédé comprenant les opérations consistant à :recevoir des messages de transaction entrants provenant de terminaux mobiles utilisant le système de communications, les messages entrants englobant l'identifiant inédit du terminal mobile expéditeur ;mettre en file d'attente les messages entrants ;interpréter les messages de transaction entrants ;authentifier les messages de transaction entrants en comparant l'identifiant inédit inclus aux entrées figurant dans une liste de comptes virtuels valides ;dans les cas où les messages de transaction entrants sont authentiques, produire des instructions de transaction correspondantes visant à modifier des données conservées dans un ou plusieurs comptes virtuels valides stockés dans une mémoire de données ;recevoir des messages de terminaison de transaction à partir de la mémoire de données lorsque la modification est achevée ;mettre en file d'attente les messages de terminaison de transaction ; ettransmettre les messages de transaction sortants, mis en file d'attente, vers les terminaux mobiles expéditeurs, chaque message de terminaison de transaction interprété englobant des informations sécuritaires générées à partir d'identifiants inédits de comptes virtuels modifiés ;cas dans lequel chaque message sortant reçu se présente sous un format qui exige la saisie d'une clé inédite à partir de la carte de données insérée dans le terminal mobile, ce qui permet par conséquent de garantir que le message sortant peut uniquement être lu en présence d'une carte de données avec une clé inédite laquelle concorde avec les informations sécuritaires figurant dans le message sortant.
- Procédé destiné à réaliser une transaction dans un système de microfinancement, le procédé comprenant :le procédé selon la revendication 10 ; etun procédé pour exploiter un combiné de téléphone mobile (302) agencé pour supporter le procédé selon la revendication 10, le procédé pour exploiter le combiné de téléphone mobile (302) comportant les opérations consistant à :mettre à disposition une application d'interprétation personnalisable ;utiliser l'application d'interprétation pour fournir des menus en vue d'un affichage sur le téléphone mobile (302) ;accepter des informations de transaction saisies par l'intermédiaire des menus ;générer des messages de transaction entrants en conformité avec les informations de transaction saisies ;transmettre au système les messages de transaction entrants ;recevoir des messages de transaction sortants en provenance du système ; etafficher, sur le combiné du mobile (302), la confirmation de la terminaison de la transaction.
- Procédé selon la revendication 11, lors du procédé destiné à exploiter un combiné de téléphone mobile (302), l'étape de fourniture d'un menu en vue d'un affichage comportant l'étape consistant à recevoir un message de menu et à adapter le menu en réaction au contenu du message de menu, ce qui permet par conséquent de personnaliser le menu pour satisfaire aux différentes exigences des utilisateurs du système.
- Procédé selon la revendication 12, lors du procédé destiné à exploiter un combiné de téléphone mobile (302), le message du menu étant reçu sous la forme d'une mise à jour par liaison radio.
- Procédé selon la revendication 12 ou 13, le procédé destiné à exploiter un combiné de téléphone mobile (302) comprenant en outre les opérations consistant à déterminer la localisation physique du combiné et à générer des informations dépendantes de la localisation, cas dans lequel le message de menu englobe des informations dépendantes de la localisation qui sont appropriées à la localisation physique du combiné.
- Procédé selon l'une quelconque des revendications 11 à 14, lors du procédé destiné à exploiter un combiné de téléphone mobile (302), l'étape d'acceptation des informations de transaction saisies comportant les opérations consistant à :présenter à l'utilisateur un menu à dialogue ;inviter l'utilisateur à saisir les informations de la transaction ; etstocker les informations de transaction saisies sous un format adapté à être traité en message de transaction.
- Procédé selon la revendication 15, lors du procédé destiné à exploiter un combiné de téléphone mobile (302), les informations de transaction saisies comportant des informations lesquelles ïdentifient un ou plusieurs des paramètres suivants : le compte cible ; la valeur devant être transférée ; la date du transfert ; la valeur devant être retirée ; la date du retrait; et des données sécuritaires en vue de l'authentification.
- Procédé selon les revendications 11 à 16, lors du procédé destiné à exploiter un combiné de téléphone mobile (302), l'étape d'acceptation des informations de transaction saisies comportant une étape préliminaire visant à authentifier la tentative d'accéder à une boîte de réception de compte donnée grâce à la fonctionnalité d'authentification de la carte de données insérée dans le combiné de téléphone mobile, permettant ainsi de veiller à l'intégrité de l'historique des transactions en vertu de l'authentification SIM.
- Procédé selon la revendication 17, lors du procédé destiné à exploiter un combiné de téléphone mobile (302), l'étape d'authentification englobant les opérations consistant à : inviter l'utilisateur à parler dans un microphone monté sur le combiné ; enregistrer une saisie vocale ; et comparer la saisie vocale à un échantillon vocal d'un utilisateur vérifié ; et confirmer la voix comme étant celle de l'utilisateur, ce qui permet par conséquent d'authentifier l'utilisateur à l'aide de la reconnaissance vocale.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PL06779120T PL1922681T3 (pl) | 2005-08-12 | 2006-08-11 | Zarządzanie rachunkiem w telefonii komórkowej |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GBGB0516616.0A GB0516616D0 (en) | 2005-08-12 | 2005-08-12 | Mobile account management |
PCT/GB2006/002997 WO2007020394A1 (fr) | 2005-08-12 | 2006-08-11 | Gestion de compte mobile |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1922681A1 EP1922681A1 (fr) | 2008-05-21 |
EP1922681B1 true EP1922681B1 (fr) | 2013-04-03 |
Family
ID=35098237
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP06779120A Active EP1922681B1 (fr) | 2005-08-12 | 2006-08-11 | Gestion de compte mobile |
Country Status (8)
Country | Link |
---|---|
EP (1) | EP1922681B1 (fr) |
JP (1) | JP5144514B2 (fr) |
CN (1) | CN101288092A (fr) |
ES (1) | ES2415365T3 (fr) |
GB (1) | GB0516616D0 (fr) |
PL (1) | PL1922681T3 (fr) |
PT (1) | PT1922681E (fr) |
WO (1) | WO2007020394A1 (fr) |
Families Citing this family (54)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8606723B2 (en) | 2004-06-04 | 2013-12-10 | Sap Ag | Consistent set of interfaces derived from a business object model |
WO2006038924A2 (fr) | 2004-06-18 | 2006-04-13 | Sap Ag | Ensemble coherent d'interfaces derivees d'un modele d'objet commercial |
US8744937B2 (en) | 2005-02-25 | 2014-06-03 | Sap Ag | Consistent set of interfaces derived from a business object model |
EP2076874A4 (fr) | 2006-05-13 | 2011-03-09 | Sap Ag | Ensemble cohérent d'interfaces dérivées d'un modèle d'objet commercial |
US8566193B2 (en) | 2006-08-11 | 2013-10-22 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8396768B1 (en) | 2006-09-28 | 2013-03-12 | Sap Ag | Managing consistent interfaces for human resources business objects across heterogeneous systems |
WO2009065417A1 (fr) * | 2007-11-19 | 2009-05-28 | Net Signature For Advanced Solutions (I.N.K.) | Devise m - netsense |
US8417593B2 (en) | 2008-02-28 | 2013-04-09 | Sap Ag | System and computer-readable medium for managing consistent interfaces for business objects across heterogeneous systems |
US8930248B2 (en) | 2008-03-31 | 2015-01-06 | Sap Se | Managing consistent interfaces for supply network business objects across heterogeneous systems |
US20090326988A1 (en) | 2008-06-26 | 2009-12-31 | Robert Barth | Managing consistent interfaces for business objects across heterogeneous systems |
US8671064B2 (en) | 2008-06-26 | 2014-03-11 | Sap Ag | Managing consistent interfaces for supply chain management business objects across heterogeneous systems |
CN101730060B (zh) * | 2008-10-30 | 2012-08-29 | 电信科学技术研究院 | 提高***安全性的方法、***及装置 |
CN102224515A (zh) * | 2008-11-25 | 2011-10-19 | 阿尔卡特朗讯 | 使用蜂窝网络的资金转移 |
US20100153297A1 (en) | 2008-12-12 | 2010-06-17 | Sap Ag | Managing Consistent Interfaces for Credit Portfolio Business Objects Across Heterogeneous Systems |
CN101923753B (zh) * | 2009-06-10 | 2012-09-05 | 中国联合网络通信集团有限公司 | 电子货币管理***和方法 |
US8396751B2 (en) | 2009-09-30 | 2013-03-12 | Sap Ag | Managing consistent interfaces for merchandising business objects across heterogeneous systems |
GR1007336B (el) * | 2010-01-19 | 2011-07-05 | Καφετζης, Νικολαος Γεωργιου | Μεθοδος-πρωτοκολλο διενεργειας τηλε-ηλεκτρονικων συναλλαγων |
KR101078173B1 (ko) * | 2010-05-14 | 2011-10-28 | 박귀숙 | 휴대폰 모바일을 이용한 안심 결제시스템 및 그 결제시스템을 이용한 결제방법 |
US8732083B2 (en) | 2010-06-15 | 2014-05-20 | Sap Ag | Managing consistent interfaces for number range, number range profile, payment card payment authorisation, and product template template business objects across heterogeneous systems |
US9135585B2 (en) | 2010-06-15 | 2015-09-15 | Sap Se | Managing consistent interfaces for property library, property list template, quantity conversion virtual object, and supplier property specification business objects across heterogeneous systems |
US8417588B2 (en) | 2010-06-15 | 2013-04-09 | Sap Ag | Managing consistent interfaces for goods tag, production bill of material hierarchy, and release order template business objects across heterogeneous systems |
CN102223615A (zh) * | 2011-06-17 | 2011-10-19 | 余方波 | 移动通信终端费用转移方法 |
US8666845B2 (en) | 2011-07-28 | 2014-03-04 | Sap Ag | Managing consistent interfaces for a customer requirement business object across heterogeneous systems |
US8775280B2 (en) | 2011-07-28 | 2014-07-08 | Sap Ag | Managing consistent interfaces for financial business objects across heterogeneous systems |
US8601490B2 (en) | 2011-07-28 | 2013-12-03 | Sap Ag | Managing consistent interfaces for business rule business object across heterogeneous systems |
WO2013013343A1 (fr) * | 2011-07-28 | 2013-01-31 | Sap Ag | Gestion d'interfaces cohérentes pour des objets d'entreprise de facture de fournisseur et de classification de produits du commerce extérieur dans des systèmes hétérogènes |
US8560392B2 (en) | 2011-07-28 | 2013-10-15 | Sap Ag | Managing consistent interfaces for a point of sale transaction business object across heterogeneous systems |
US8521838B2 (en) | 2011-07-28 | 2013-08-27 | Sap Ag | Managing consistent interfaces for communication system and object identifier mapping business objects across heterogeneous systems |
US8725654B2 (en) | 2011-07-28 | 2014-05-13 | Sap Ag | Managing consistent interfaces for employee data replication business objects across heterogeneous systems |
GB2499360B8 (en) * | 2011-10-12 | 2016-01-27 | Technology Business Man Ltd | Secure ID authentication |
US8762453B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for feed collaboration group and feed event subscription |
US9232368B2 (en) | 2012-02-16 | 2016-01-05 | Sap Se | Consistent interface for user feed administrator, user feed event link and user feed settings |
US8756274B2 (en) | 2012-02-16 | 2014-06-17 | Sap Ag | Consistent interface for sales territory message type set 1 |
US8984050B2 (en) | 2012-02-16 | 2015-03-17 | Sap Se | Consistent interface for sales territory message type set 2 |
US9237425B2 (en) | 2012-02-16 | 2016-01-12 | Sap Se | Consistent interface for feed event, feed event document and feed event type |
US8762454B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for flag and tag |
US20140019341A1 (en) * | 2012-04-10 | 2014-01-16 | Kabbage, Inc. | Method, apparatus and computer readable storage to effectuate an instantaneous monetary transfer |
US8521621B1 (en) | 2012-06-28 | 2013-08-27 | Sap Ag | Consistent interface for inbound delivery request |
US8615451B1 (en) | 2012-06-28 | 2013-12-24 | Sap Ag | Consistent interface for goods and activity confirmation |
US8949855B2 (en) | 2012-06-28 | 2015-02-03 | Sap Se | Consistent interface for address snapshot and approval process definition |
US9246869B2 (en) | 2012-06-28 | 2016-01-26 | Sap Se | Consistent interface for opportunity |
US9400998B2 (en) | 2012-06-28 | 2016-07-26 | Sap Se | Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule |
US8756135B2 (en) | 2012-06-28 | 2014-06-17 | Sap Ag | Consistent interface for product valuation data and product valuation level |
US9367826B2 (en) | 2012-06-28 | 2016-06-14 | Sap Se | Consistent interface for entitlement product |
WO2014000200A1 (fr) | 2012-06-28 | 2014-01-03 | Sap Ag | Interface cohérente pour demande de génération de document |
US9547833B2 (en) | 2012-08-22 | 2017-01-17 | Sap Se | Consistent interface for financial instrument impairment calculation |
US9076112B2 (en) | 2012-08-22 | 2015-07-07 | Sap Se | Consistent interface for financial instrument impairment expected cash flow analytical result |
US9043236B2 (en) | 2012-08-22 | 2015-05-26 | Sap Se | Consistent interface for financial instrument impairment attribute values analytical result |
US9191343B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for appointment activity business object |
US9191357B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for email activity business object |
WO2014162309A1 (fr) * | 2013-04-01 | 2014-10-09 | Pt. Cyberport | Système de transactions financières utilisant un dispositif mobile via un réseau ussd |
WO2014169269A1 (fr) | 2013-04-12 | 2014-10-16 | Nant Holdings Ip, Llc | Systèmes et procédés de caissier virtuel |
US9754260B2 (en) | 2013-10-28 | 2017-09-05 | Quisk, Inc. | Account locking using transaction codes |
CN111541729B (zh) * | 2016-09-20 | 2023-10-10 | 徐蔚 | 一种基于属性信息进行支付的方法、装置与移动终端 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7089208B1 (en) * | 1999-04-30 | 2006-08-08 | Paypal, Inc. | System and method for electronically exchanging value among distributed users |
KR20010094229A (ko) * | 2000-04-04 | 2001-10-31 | 이수성 | 전화기의 음성인식 조작 방법 및 시스템 |
WO2001097118A1 (fr) * | 2000-06-14 | 2001-12-20 | Takako Jogu | Procede de reglement par telephone mobile et telephone mobile |
GB2372615A (en) * | 2000-12-27 | 2002-08-28 | Robert Joseph Gerard Macnamee | Telephone based payment system |
AU2003255848A1 (en) * | 2002-08-20 | 2004-03-11 | Teimuraz Tchkadua | Method and system for transfer of money via telecommunication network |
JP4553565B2 (ja) * | 2002-08-26 | 2010-09-29 | パナソニック株式会社 | 電子バリューの認証方式と認証システムと装置 |
JP4509931B2 (ja) * | 2002-10-17 | 2010-07-21 | ヴォウダフォン・グループ・ピーエルシー | トランザクションの容易化および認証 |
JP4162468B2 (ja) * | 2002-10-25 | 2008-10-08 | ソフトバンクモバイル株式会社 | 情報通信端末における暗号鍵情報の管理方法及び情報通信端末 |
MXPA06000174A (es) * | 2003-07-02 | 2006-04-11 | Mobipay International S A | Sistema de transacciones y pagos mediante telefono movil digital. |
EP1510983A1 (fr) * | 2003-08-26 | 2005-03-02 | Siemens Aktiengesellschaft | Plate-form de paiement pour operateurs de réseau et pour terminaux pour la réalisation d'un paiement éléctronique et procédés correspendants |
CN1879071B (zh) * | 2003-11-07 | 2010-06-09 | 意大利电信股份公司 | 用于认证数据处理***的用户的方法和*** |
JP2005184618A (ja) * | 2003-12-22 | 2005-07-07 | Matsushita Electric Ind Co Ltd | 音声認証装置、音声認証システム及び音声認証方法 |
GB2415574B (en) | 2004-06-21 | 2009-02-25 | Vodafone Plc | Authenticating messages in a telecommunications system |
-
2005
- 2005-08-12 GB GBGB0516616.0A patent/GB0516616D0/en not_active Ceased
-
2006
- 2006-08-11 EP EP06779120A patent/EP1922681B1/fr active Active
- 2006-08-11 PL PL06779120T patent/PL1922681T3/pl unknown
- 2006-08-11 CN CNA2006800382993A patent/CN101288092A/zh active Pending
- 2006-08-11 JP JP2008525641A patent/JP5144514B2/ja not_active Expired - Fee Related
- 2006-08-11 WO PCT/GB2006/002997 patent/WO2007020394A1/fr active Application Filing
- 2006-08-11 ES ES06779120T patent/ES2415365T3/es active Active
- 2006-08-11 PT PT67791202T patent/PT1922681E/pt unknown
Also Published As
Publication number | Publication date |
---|---|
WO2007020394A1 (fr) | 2007-02-22 |
GB0516616D0 (en) | 2005-09-21 |
ES2415365T3 (es) | 2013-07-25 |
JP2009505199A (ja) | 2009-02-05 |
PL1922681T3 (pl) | 2013-08-30 |
EP1922681A1 (fr) | 2008-05-21 |
PT1922681E (pt) | 2013-07-09 |
CN101288092A (zh) | 2008-10-15 |
JP5144514B2 (ja) | 2013-02-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1922681B1 (fr) | Gestion de compte mobile | |
US10504082B2 (en) | Interoperable financial transactions via mobile devices | |
US20160026991A1 (en) | Mobile account management | |
US20120054102A1 (en) | Method & System for Providing Payments Over A Wireless Connection | |
US9807042B2 (en) | Enhanced real-time messaging | |
US20060224470A1 (en) | Digital mobile telephone transaction and payment system | |
US20120089514A1 (en) | Method of authentication | |
KR20040104660A (ko) | 통신 운영자가 금융 거래 서비스를 제공할 수 있도록 하는시스템 및 상기 거래를 구현하는 방법 | |
CZ20013012A3 (cs) | Způsob placení po telefonu a systém umoľňující toto placení | |
US20070270124A1 (en) | Systems and methods for adding credit to a wireless telecommunications account | |
CN104112196A (zh) | 用于提供银行服务的电子*** | |
CA2842108A1 (fr) | Systeme et procede de transactions financieres | |
WO2010035224A2 (fr) | Procédé et système de transaction | |
KR101024810B1 (ko) | 에이알에스를 이용한 모바일 결제방법 및 시스템 | |
WO2004049621A1 (fr) | Systeme d'authentification et d'identification et transactions utilisant un tel systeme d'authentification et d'identification | |
WO2008091191A1 (fr) | Procédé et système pour exécuter de façon sécurisée une transaction de débit | |
US20100257097A1 (en) | Secure transactions using non-secure communications | |
Krugel | Mobile Banking Technology Options | |
JP2011044151A (ja) | 安全な携帯端末支払いのための方法とシステム | |
WO2006004441A2 (fr) | Operation bancaires electroniques | |
WO2014077770A1 (fr) | Procédé de réalisation d'un paiement faisant appel à un dispositif de communication portable | |
WO2002071354A2 (fr) | Systeme et procede permettant de faciliter une transaction de commerce electronique | |
EP2920752A1 (fr) | Procédé d'achat d'un produit faisant appel à un dispositif de communication portable | |
KR20020002938A (ko) | 전화번호를 이용한 전자 지불 방법 | |
EP1906349A1 (fr) | Système de paiement et de transaction utilisant des téléphones mobiles numériques |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20080304 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
17Q | First examination report despatched |
Effective date: 20081215 |
|
DAX | Request for extension of the european patent (deleted) | ||
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602006035446 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: G06Q0020000000 Ipc: H04M0015000000 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04M 15/00 20060101AFI20121106BHEP Ipc: H04W 4/24 20090101ALI20121106BHEP Ipc: G06Q 20/32 20120101ALI20121106BHEP Ipc: G06Q 20/12 20120101ALI20121106BHEP |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 605355 Country of ref document: AT Kind code of ref document: T Effective date: 20130415 Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602006035446 Country of ref document: DE Effective date: 20130529 |
|
REG | Reference to a national code |
Ref country code: RO Ref legal event code: EPE |
|
REG | Reference to a national code |
Ref country code: PT Ref legal event code: SC4A Free format text: AVAILABILITY OF NATIONAL TRANSLATION Effective date: 20130628 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 2415365 Country of ref document: ES Kind code of ref document: T3 Effective date: 20130725 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: MC Payment date: 20130626 Year of fee payment: 8 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 605355 Country of ref document: AT Kind code of ref document: T Effective date: 20130403 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 |
|
REG | Reference to a national code |
Ref country code: PL Ref legal event code: T3 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: T3 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130704 Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130803 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130703 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130403 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20140106 |
|
REG | Reference to a national code |
Ref country code: HU Ref legal event code: AG4A Ref document number: E018251 Country of ref document: HU |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602006035446 Country of ref document: DE Effective date: 20140106 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140901 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 10 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: PT Payment date: 20150810 Year of fee payment: 10 Ref country code: CH Payment date: 20150819 Year of fee payment: 10 Ref country code: IE Payment date: 20150820 Year of fee payment: 10 Ref country code: CZ Payment date: 20150810 Year of fee payment: 10 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20150820 Year of fee payment: 10 Ref country code: HU Payment date: 20150819 Year of fee payment: 10 Ref country code: PL Payment date: 20150728 Year of fee payment: 10 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: RO Payment date: 20160729 Year of fee payment: 11 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160831 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160831 Ref country code: HU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160812 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20170428 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CZ Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160811 Ref country code: PT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170213 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160831 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160811 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160811 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RO Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170811 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180811 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20230821 Year of fee payment: 18 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: TR Payment date: 20230810 Year of fee payment: 18 Ref country code: IT Payment date: 20230825 Year of fee payment: 18 Ref country code: GB Payment date: 20230822 Year of fee payment: 18 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20230821 Year of fee payment: 18 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: ES Payment date: 20231027 Year of fee payment: 18 |