EP2613513B1 - Transfert de crédit à partir d'un terminal mobile - Google Patents

Transfert de crédit à partir d'un terminal mobile Download PDF

Info

Publication number
EP2613513B1
EP2613513B1 EP12305005.6A EP12305005A EP2613513B1 EP 2613513 B1 EP2613513 B1 EP 2613513B1 EP 12305005 A EP12305005 A EP 12305005A EP 2613513 B1 EP2613513 B1 EP 2613513B1
Authority
EP
European Patent Office
Prior art keywords
message
reseller
user
credit
application server
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
Application number
EP12305005.6A
Other languages
German (de)
English (en)
Other versions
EP2613513A1 (fr
Inventor
Varun Grover
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alcatel Lucent SAS
Original Assignee
Alcatel Lucent SAS
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 Alcatel Lucent SAS filed Critical Alcatel Lucent SAS
Priority to EP12305005.6A priority Critical patent/EP2613513B1/fr
Publication of EP2613513A1 publication Critical patent/EP2613513A1/fr
Application granted granted Critical
Publication of EP2613513B1 publication Critical patent/EP2613513B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102—Bill distribution or payments
    • 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/16—Payments settled via telecommunication 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/20—Point-of-sale [POS] network systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0196—Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking

Definitions

  • the present invention relates to a system for transferring credit in a telecommunication network.
  • EP 0708547 and WO 98/47116 relate to the area of credit transfers between a reseller and a user of a mobile telephone.SUMMARY
  • a method for transferring credit from an account held by a user owning a mobile terminal to an account held by a reseller owning a communication device in a billing server comprises the following steps in an application server able to communicate with the mobile terminal, the communication device and the billing server through a telecommunication network:
  • the user For an immediate fulfillment of cash availability, the user requires advantageously nothing else but a mobile terminal with a prepaid or postpaid connection.
  • a postpaid account the user will be making use of his normally unused credit limit (which is normally set by an operator to a level substantially higher than the average usage per month of a particular user).
  • his normally unused credit limit which is normally set by an operator to a level substantially higher than the average usage per month of a particular user.
  • the user will be able to encash his remaining balance.
  • the first message can be a USSD message and can comprise an access code, the first message being first received by a USSD gateway that routes the first message to the application server identified by the access code.
  • an identifier of the reseller can be stored in the application server in correspondence with an identifier of an account of the reseller in the billing server, and an identifier of the user can be stored in the application server in correspondence with an identifier of an account of the user in the billing server.
  • the identifier of the reseller can be stored in correspondence with a call number of the communication device in the application server and the first message can comprise an identifier of the reseller.
  • the application server can retrieve the identifier of the user from the received first message, the identifier being included in the first message or deduced from the first message.
  • the second message sent by the application server to the billing server can comprise the identifier of an account of the reseller, the identifier of an account of the user, and a command to perform a transaction of credit transfer by said amount of credit.
  • the application server can send a confirmation message to the mobile terminal, the confirmation message comprising information on the performed credit transfer.
  • a further object of the invention is an application server for transferring credit from an account held by a user owning a mobile terminal to an account held by a reseller owning a communication device in a billing server, the application server being able to communicate with the mobile terminal, the communication device and the billing server through a telecommunication network, the application server comprising:
  • the invention relates further to a computer program adapted to be executed in a server for performing a transfer of credit, said program including instructions which, when the program is executed in said server, execute the steps of the method of the invention.
  • a communication system comprises an application server CS which is able to communicate with a billing server BS, a mobile terminal MT and a communication device CD through a telecommunication network TN.
  • the telecommunication network TN is wireless network, eventually combined with other wired and wireless networks.
  • the mobile terminal MT can be a radio communication mobile terminal.
  • the terminal MT is a mobile phone, or is a communicating Personal Digital Assistant PDA, or an intelligent telephone like SmartPhone.
  • the mobile terminal MT is a cellular mobile radio communication terminal, connected by a channel to a radio access network comprising the network of a fixed radio communication network, eg GSM (Global System for Mobile communications) or UMTS (Universal Mobile Telecommunications System) or LTE (Long Term Evolution).
  • GSM Global System for Mobile communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the communication device CD may be an entity similar to the mobile terminal MT.
  • the mobile terminal is owned by a user who is a subscriber of the telecommunication network and who wishes to have cash credit at his disposal by asking a reseller who owns the communication device CD.
  • the user owns an account held be the telecommunication network operator, like a mobile account being a prepaid or postpaid balance account, but does not have any bank account.
  • the user may wish to convert the credit present on his account into money that can be retrieved by the reseller in form of cash money to give to the user or that can serve as a way of payment for purchasing a good for example.
  • the application server AS is a server included in the telecommunication network TN able to handle USSD (Unstructured Supplementary Service Data) message and SMS (Short Message Service) messages.
  • USSD Unstructured Supplementary Service Data
  • SMS Short Message Service
  • the application server AS comprises a messaging module MM and a controlling module CM.
  • the application server AS may be a server SCP (Service Control Point).
  • the application server AS stores in a database DB a profile of each reseller registered to the service provided by the application server.
  • the database DB memorizes an identifier IdR of each reseller in correspondence with a call number associated with the communication device CD, and optionally in correspondence with an authentication code Ca.
  • the messaging module MM acts as an interface handling exchange of messages with the mobile terminal MT and the communication device CD.
  • the billing server BS stores an account for the user owning the mobile terminal MT and an account for the reseller owning the communication device CD.
  • the billing server BS may be able to communicate with bank servers in order to convert the credit present in an account into money for an account managed by the bank server, in case the reseller needs any action or agreement from his bank to use credit received on his mobile account as a way of transaction, such as a purchase of a good in the store.
  • the money available to the user corresponds to his mobile balance which he may convert to cash for his personal use or credit it to reseller's account as a payment for a product/service purchased from the reseller.
  • the identifier IdR of the reseller in correspondence with an identifier IdAR of an account of the reseller in the billing server BS.
  • an identifier IdU of the user in correspondence with an identifier IdAU of an account of the user in the billing server BS.
  • the identifier IdR of the reseller may be an assigned number.
  • the identifier IdU of the user may be an assigned number or a number related to the user, such as the IMSI identity (International Mobile Subscriber Identity).
  • a method for transferring credit comprises steps S1 to S6 executed automatically within the communication system.
  • a user owning a mobile terminal MT is present at a place where a reseller owning a communication device CD can propose cash money retrieval.
  • the mobile terminal MT sends a USSD message towards the application server AS.
  • the USSD message comprises an access code Cx to initiate the transaction service by the application server, the reseller identifier IdR, an authentication code Ca, and the amount of credit wished by the user.
  • the USSD message is received by a USSD gateway that routes then the USSD message to the application server identified by the access code.
  • the USSD message can be under the following form: *121*12345* ⁇ 989>*500#, where 121 is the access code Cx, 12345 is the reseller identifier IdR, 989 is authentication code Ca and 500 is the amount of credit.
  • the authentication code Ca is a key composed of three or more digits that can be pre-shared by the user and the reseller, or already stored in the application server AS and known by the reseller that can give it to the user.
  • the messaging module MM of the application server AS receives the USSD message.
  • the controlling module CM checks the reseller identifier IdR in the database DB and stores temporarily the authentication code Ca in correspondence with the identifier IdR.
  • the application server AS only check the presence of the reseller identifier IdR and the authentication code Ca in the database DB.
  • the controlling module CM of the application server AS identifies also the call number associated with the communication device CD that is stored in correspondence with the identifier IdR in the database DB.
  • the application server AS identifies also the identifier IdU of the user.
  • the identifier IdU can be an assigned number that is entered by the user and included in the USSD message, or the identifier IdU can be deduced from the USSD message if the identifier IdU is the mobile terminal call number or IMEI. In both cases, the application server AS can identify the user and an identifier IdAU of an account of the user in the billing server BS.
  • the identifier IdU of the user may be an assigned number or a number related to the mobile terminal MT, such as the call number or the IMEI (International Mobile Equipment Identity).
  • the messaging module MM of the application server AS sends a request Req to the communication device CD, the request being under the format of a SMS message for example.
  • the request comprises a demand of credit transfer, for a cash money retrieval, for the amount included in the USSD message and a demand of confirmation by the reseller.
  • the request comprises also an identifier of a user, for example the call number of the mobile terminal MT.
  • the communication device CD receives the request Req. If the reseller acknowledges the transaction, he can enter the authentication code Ca.
  • the communication device CD sends a response Res to the application server AS, the response being under the format of a SMS message for example.
  • the response Res comprises the authentication code Ca that can be interpreted as a confirmation of transaction.
  • the messaging module MM of the application server AS receives the response Res and checks if the authentication code received in the response is identical to the authentication code received in the USSD message.
  • the controlling module CM of the application server AS retrieves the identifier IdAR of an account of the reseller in the billing server BS by means of the identifier IdR of the reseller.
  • the application server AS retrieves also the identifier IdAU of an account of the user by means of the identifier IdU of the user.
  • the controlling module CM commands the message module MM to send a message Mes to the billing server BS in order to debit the account of the user of the amount of credit indicated in the USSD message and to credit the account of the reseller of the same amount of credit.
  • the message Mes comprises the identifier IdAR of an account of the reseller, the identifier IdAU of an account of the user, and a command to perform a transaction of credit transfer by the amount of credit.
  • the billing server BS performs the transaction of credit transfer and sends a message back to the application server AS indicating that the credit transfer has been performed.
  • the messaging module MM of the application server AS then sends a confirmation message MesC to the mobile terminal MT, the confirmation message MesC comprising information on the performed credit transfer.
  • the reseller can then give an amount of money to the user according to the amount of credit that has been transferred.
  • the amount of credit received by the reseller on its account can be a way of payment, for example for purchasing a good in the store held by the reseller.
  • the messaging module MM of the application server AS sends also a confirmation message to the communication device Cd, comprising information on the performed credit transfer.
  • the credit transfer from subscriber to reseller can be explained as follows: after credit transfer request and successful authentication, the said amount to be debited from the user's mobile account and the same amount to be credited to the bank account of the reseller by way of a settlement from the network operator to the reseller for the current transaction.
  • a "credit limit" is set by the operator based on the user's credit history, usage patterns etc. and is set to a limit substantially higher than the average bill per month of a particular user. This limit defines how much credit in terms of service usage charges can be allowed to a particular user.
  • this credit limit of the users It is intended to use this credit limit of the users to actually be able to withdraw amount up to this limit, and after a positive feedback of this feature from the end users (trend analysis of usage of this service) and timely repayment of bills by the user, the operator may increase the credit limit of the users to encourage more withdrawals through this method.
  • This cash withdrawal by a postpaid user could be seen as analogous to a credit card user withdrawing cash from his credit card account.
  • a balance is maintained in his mobile connection account by the operator. This balance is a purchased balance and is essentially owned by the user.
  • the user may get his account refilled at a given date with excess money (based on availability of cash with him) and keep it in his mobile account for as long as he wishes. He may use the amount to make calls, surf internet etc. and also withdraw cash out of his mobile account whenever needed.
  • This cash withdrawal from a prepaid mobile account could be seen as analogous to a bank account holding user withdrawing cash from his account subject to a maximum limit of his bank account balance.
  • the invention described here relates to a method and a server for a transfer of credit.
  • the steps of the method of the invention are determined by the instructions of a computer program incorporated in a server such as the application server AS according to the invention.
  • the program includes program instructions which, when said program is executed in a processor of the server the operation whereof is then controlled by the execution of the program, execute the steps of the method according to the invention.
  • the invention applies also to a computer program, in particular a computer program on or in an information medium readable by a data processing device, adapted to implement the invention.
  • That program may use any programming language and be in the form of source code, object code or an intermediate code between source code and object code, such as a partially compiled form, or in any other desirable form for implementing the method according to the invention.
  • the information medium may be any entity or device capable of storing the program.
  • the medium may include storage means or a recording medium on which the computer program according to the invention is recorded, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a USB key, or magnetic recording means, for example a diskette (floppy disk) or a hard disk.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Meter Arrangements (AREA)

Claims (8)

  1. Procédé pour transférer du crédit depuis un compte tenu par un utilisateur possédant un terminal mobile (MT) vers un compte tenu par un revendeur possédant un dispositif de communication (CD) et étant présent à un même endroit que l'utilisateur, les comptes étant stockés dans un serveur de facturation (BS), comprenant les étapes suivantes dans un serveur d'application (AS) pouvant communiquer avec le terminal mobile (MT), le dispositif de communication (CD) et le serveur de facturation (BS) via un réseau de télécommunication (TN) :
    la réception (S2) d'un premier message envoyé par le terminal mobile (MT), le message comprenant au moins un code d'authentification (Ca) qui est une clé pré-partagée par l'utilisateur et le revendeur, un identifiant de revendeur (IdR) et une somme de crédit,
    dans lequel le premier message est un message USSD et comprend un code d'accès (Cx), le premier message étant d'abord reçu par une passerelle USSD qui route le premier message vers le serveur d'application (AS) identifié par le code d'accès (Cx),
    l'envoi (S3) d'une demande (Req) au dispositif de communication (CD), la demande comprenant un ordre de transfert de crédit,
    après réception d'une réponse (Res) envoyée par le dispositif de communication (CD), l'envoi (S5) d'un second message (Mes) au serveur de facturation (BS) pour effectuer un transfert de crédit de ladite somme de crédit depuis le compte tenu par l'utilisateur vers le compte tenu par le revendeur, si la réponse (Res) reçue comprend un code d'authentification identique au code d'authentification (Ca) compris dans le premier message reçu.
  2. Procédé selon la revendication 1, un identifiant (IdR) du revendeur étant stocké dans le serveur d'application (AS) en correspondance avec un identifiant (IdAR) d'un compte du revendeur dans le serveur de facturation (BS), et un identifiant (IdU) de l'utilisateur est stocké dans le serveur d'application (AS) en correspondance avec un identifiant (IdAU) d'un compte de l'utilisateur dans le serveur de facturation (BS) .
  3. Procédé selon la revendication 2, dans lequel l'identifiant (IdR) du revendeur est stocké en correspondance avec un numéro d'appel du dispositif de communication (CD) dans le serveur d'application (AS) et le premier message comprend un identifiant (IdR) du revendeur.
  4. Procédé selon la revendication 2 ou 3, dans lequel le serveur d'application (AS) extrait l'identifiant (IdU) de l'utilisateur du premier message reçu, l'identifiant (IdU) étant compris dans le premier message ou déduit à partir du premier message.
  5. Procédé selon l'une quelconque des revendications 2 à 4, dans lequel le second message (Mes) envoyé par le serveur d'application (AS) au serveur de facturation (BS) comprend l'identifiant (IdAR) d'un compte du revendeur, l'identifiant (IdAU) d'un compte de l'utilisateur, et une instruction pour effectuer une transaction de transfert de crédit selon ladite somme de crédit.
  6. Procédé selon l'une quelconque des revendications 1 à 5, dans lequel le serveur d'application (AS) envoie un message de confirmation (MesC) au terminal mobile (MT), le message de confirmation (MesC) comprenant des informations sur le transfert de crédit effectué.
  7. Serveur d'application (AS) pour transférer du crédit depuis un compte tenu par un utilisateur possédant un terminal mobile (MT) vers un compte tenu par un revendeur possédant un dispositif de communication (CD) et étant présent à un même endroit que l'utilisateur, les comptes étant stockés dans un serveur de facturation (BS), le serveur d'application (AS) pouvant communiquer avec le terminal mobile (MT), le dispositif de communication (CD) et le serveur de facturation (BS) via un réseau de télécommunication (TN), le serveur d'application (AS) comprenant :
    un moyen (MM) pour recevoir un premier message envoyé par le terminal mobile (MT), le message comprenant au moins un code d'authentification (Ca) qui est une clé pré-partagée par l'utilisateur et le revendeur, un identifiant de revendeur (IdR) et une somme de crédit,
    dans lequel le premier message est un message USSD et comprend un code d'accès (Cx), le premier message étant d'abord reçu par une passerelle USSD qui route le premier message vers le serveur d'application (AS) identifié par le code d'accès (Cx),
    un moyen (MM) pour envoyer une demande (Req) au dispositif de communication (CD), la demande comprenant un ordre de transfert de crédit,
    un moyen pour envoyer (MM) un second message (Mes) au serveur de facturation (BS) pour effectuer un transfert de crédit de ladite somme de crédit depuis le compte tenu par l'utilisateur vers le compte tenu par le revendeur, après réception d'une réponse (Res) envoyée par le dispositif de communication (CD), si la réponse (Res) reçue comprend un code d'authentification identique au code d'authentification (Ca) compris dans le premier message reçu.
  8. Programme informatique conçu pour être exécuté dans un serveur d'application (AS) pour transférer du crédit depuis un compte tenu par un utilisateur possédant un terminal mobile (MT) vers un compte tenu par un revendeur possédant un dispositif de communication (CD) et étant présent à un même endroit que l'utilisateur, les comptes étant stockés dans un serveur de facturation (BS), le serveur d'application (AS) pouvant communiquer avec le terminal mobile (MT), le dispositif de communication (CD) et le serveur de facturation (BS) via un réseau de télécommunication (TN), ledit programme comprenant des instructions qui, lorsque ledit programme est exécuté dans ledit serveur d'application, exécutent les étapes suivantes :
    la réception (S2) d'un premier message envoyé par le terminal mobile (MT), le message comprenant au moins un code d'authentification (Ca) qui est une clé pré-partagée par l'utilisateur et le revendeur, un identifiant de revendeur (IdR) et une somme de crédit,
    dans lequel le premier message est un message USSD et comprend un code d'accès (Cx), le premier message étant d'abord reçu par une passerelle USSD qui route le premier message vers le serveur d'application (AS) identifié par le code d'accès (Cx),
    l'envoi (S3) d'une demande (Req) au dispositif de communication (CD), la demande comprenant un ordre de transfert de crédit,
    après réception d'une réponse (Res) envoyée par le dispositif de communication (CD), l'envoi (S5) d'un second message (Mes) au serveur de facturation (BS) pour effectuer un transfert de crédit de ladite somme de crédit depuis le compte tenu par l'utilisateur vers le compte tenu par le revendeur, si la réponse (Res) reçue comprend un code d'authentification identique au code d'authentification (Ca) compris dans le premier message reçu.
EP12305005.6A 2012-01-03 2012-01-03 Transfert de crédit à partir d'un terminal mobile Active EP2613513B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP12305005.6A EP2613513B1 (fr) 2012-01-03 2012-01-03 Transfert de crédit à partir d'un terminal mobile

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP12305005.6A EP2613513B1 (fr) 2012-01-03 2012-01-03 Transfert de crédit à partir d'un terminal mobile

Publications (2)

Publication Number Publication Date
EP2613513A1 EP2613513A1 (fr) 2013-07-10
EP2613513B1 true EP2613513B1 (fr) 2019-05-01

Family

ID=45495876

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12305005.6A Active EP2613513B1 (fr) 2012-01-03 2012-01-03 Transfert de crédit à partir d'un terminal mobile

Country Status (1)

Country Link
EP (1) EP2613513B1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017099680A1 (fr) 2015-12-11 2017-06-15 Turkcell Teknoloji Arastirma Ve Gelistirme Anonim Sirketi Système intégré de transfert de crédit entre des comptes mobiles

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5608778A (en) * 1994-09-22 1997-03-04 Lucent Technologies Inc. Cellular telephone as an authenticated transaction controller
US6868391B1 (en) * 1997-04-15 2005-03-15 Telefonaktiebolaget Lm Ericsson (Publ) Tele/datacommunications payment method and apparatus
US6915272B1 (en) * 2000-02-23 2005-07-05 Nokia Corporation System and method of secure payment and delivery of goods and services
EP1315131B1 (fr) * 2001-11-23 2005-03-23 Siemens Aktiengesellschaft Méthode permettant la compensation d'argent entre systèmes de payement dans un réseau de communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP2613513A1 (fr) 2013-07-10

Similar Documents

Publication Publication Date Title
AU2010249214C1 (en) Methods, apparatus, and systems for supporting purchases of goods and services via prepaid telecommunication accounts
RU2310229C2 (ru) Многочисленные виртуальные бумажники в беспроводных устройствах
CN100584076C (zh) 远程sim卡替换和激活处理
TWI618391B (zh) 用於通訊網路訂用控制之方法及裝置，和非暫時性記憶體媒體
US20040243490A1 (en) Method and system for performing a financial transaction in a mobile communications system
EA018525B1 (ru) Способ и система реализации телефонного биллинга, стимулирующие совместное использование телефона
AU2004300110B2 (en) System and method for facilitating payment via a communications network using value accredited to a customer of the communications network
KR101101173B1 (ko) 계좌를 이용한 결제 중계 방법
CN101626562A (zh) 基于ussd充值缴费的实现方法以及充值缴费平台
US8775304B2 (en) Money transfer using cellular networks
WO2000052921A2 (fr) Communications cellulaires pour utilisateur itinerant
EP2613513B1 (fr) Transfert de crédit à partir d'un terminal mobile
WO2015007392A1 (fr) Prêt d'argent par le biais d'un dispositif mobile
KR101142007B1 (ko) 다중 접속망에서 공유된 데이터 쿠폰 상품을 지원하는 과금 처리 방법 및 시스템
US9462138B2 (en) Cellular airtime management
CN101800957B (zh) 实现通讯终端业务付费的方法、***及业务平台
KR20080030921A (ko) 상품 대금 결제 방법 및 시스템
KR100648066B1 (ko) 공중 전화기를 이용한 이동통신 선불 요금 충전 시스템 및방법
WO2015125126A2 (fr) Procédés et systèmes de transaction à l'aide d'une monnaie virtuelle générée à partir d'un temps d'utilisation prépayé dans un environnement de télécommunication interopérable
WO2001063902A9 (fr) Procede de traitement de communications et systeme de communication
WO2004015973A1 (fr) Techniques d'autorisation de services sans fils a prepaiement
KR20100135110A (ko) 전자화폐를 이용한 선불카드 충전 시스템 및 충전 방법
WO2008027016A2 (fr) Système et procédé permettant d'augmenter le crédit d'appel sur un compte de téléphonie mobile existant

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

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

17P Request for examination filed

Effective date: 20140110

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

17Q First examination report despatched

Effective date: 20140519

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ALCATEL LUCENT

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ALCATEL LUCENT

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602012059553

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04M0015000000

Ipc: G06Q0020100000

RIC1 Information provided on ipc code assigned before grant

Ipc: G06Q 20/16 20120101ALI20181218BHEP

Ipc: H04M 15/00 20060101ALI20181218BHEP

Ipc: G06Q 20/10 20120101AFI20181218BHEP

Ipc: G06Q 20/20 20120101ALI20181218BHEP

Ipc: G06Q 20/32 20120101ALI20181218BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20190131

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM 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: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1127917

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190515

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602012059553

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20190501

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: 20190501

Ref country code: NO

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: 20190801

Ref country code: HR

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: 20190501

Ref country code: ES

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: 20190501

Ref country code: NL

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: 20190501

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: 20190501

Ref country code: PT

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: 20190901

Ref country code: AL

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: 20190501

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: 20190501

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20190801

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: 20190802

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: 20190501

Ref country code: RS

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: 20190501

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1127917

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190501

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20190901

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20190501

Ref country code: RO

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: 20190501

Ref country code: CZ

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: 20190501

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: 20190501

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: 20190501

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: 20190501

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602012059553

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

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: 20190501

Ref country code: IT

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: 20190501

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

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

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: 20190501

26N No opposition filed

Effective date: 20200204

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

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: 20190501

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602012059553

Country of ref document: DE

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20200103

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200131

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: 20200103

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200103

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200131

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200801

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200131

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200131

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200131

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200103

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

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: 20190501

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: 20190501

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

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: 20190501