WO2014154349A1 - Système de serveurs en réseau, procédé d'échange de données, produit de programme d'ordinateur, serveur d'interactions et application de modification de compte mise en œuvre par ordinateur - Google Patents

Système de serveurs en réseau, procédé d'échange de données, produit de programme d'ordinateur, serveur d'interactions et application de modification de compte mise en œuvre par ordinateur Download PDF

Info

Publication number
WO2014154349A1
WO2014154349A1 PCT/EP2014/000792 EP2014000792W WO2014154349A1 WO 2014154349 A1 WO2014154349 A1 WO 2014154349A1 EP 2014000792 W EP2014000792 W EP 2014000792W WO 2014154349 A1 WO2014154349 A1 WO 2014154349A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
mobile device
account
server
request
Prior art date
Application number
PCT/EP2014/000792
Other languages
English (en)
Inventor
Matthias Albrecht
Original Assignee
Xcom Ag
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 Xcom Ag filed Critical Xcom Ag
Publication of WO2014154349A1 publication Critical patent/WO2014154349A1/fr

Links

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
    • 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/3223—Realising banking transactions through M-devices

Definitions

  • the following description relates to enabling data exchange between a mobile device of a sender and a remote computing device of a target via a network server system.
  • the description relates to a network server system, a method for data exchange, a computer program product, an interaction server, as well as a computer implemented account modification application.
  • mobile devices such as mobile phones or other hand-held devices
  • the user and/or the owner of the remote computing device may be referred to as a target.
  • the target may be a human person, that is the user of the remote computing device.
  • the target may be an artificial person, that is a legal person such as a company or the like.
  • a mobile network may be implemented as a group of interconnected computers and/or mobile devices, at least one of which communicates wirelessly, e.g. via the mobile cellular network with one or more of the remaining devices of the network.
  • a mobile device may refer to a device in the mobile network capable of wireless communication. Examples of mobile devices are smart phones, mobile phones, tablet computers, personal digital systems, pagers, and other electronic devices that can connect to a mobile network, and can be used to transmit and receive data.
  • a mobile device may communicate wirelessly using local area technologies such as wireless fidelity (WiFi), or wide area wireless technologies such as global system for mobile communication (GSM), general package radio service (GPRS), enhanced data rates for global evolution (EDGE), universal mobile telecommunications system (UMTS), high speed downlink/uplink packet access (HSDPA, HSUPA), long-term evolution (LTE), or world wide interoperability for microwave access (WIMAX). Other suitable communication technologies available today or in the future are also possible.
  • a computing device may refer to any computing device, i.e. any mobile device and any stationary computer/computing station comprising personal computers.
  • a network server system is utilized for data exchange between a mobile device of a sender and a remote computing device of a target, wherein the network server system comprises an interaction server and an account server.
  • the interaction server is operable to receive a request from the mobile device for initiating a transaction application operated by the account server.
  • the request contains a target identifier of the target of the transaction application.
  • a request for executing the transaction application from the mobile device is processed.
  • the request contains a content identifier to be processed by the transaction application.
  • the interaction server transmits the request for executing the transaction application to the account server.
  • the account server is operable to execute the transaction application and to process the content identifier by the transaction application.
  • the account server is operable to forward a target processing result to the interaction server. Further, the interaction server is operable to forward the target processing result to the remote computing device of the target.
  • the above described network server system enables a sender, that utilizes a mobile device, to perform a data exchange between the mobile device and the remote computing device by initiating a transaction application that is operated and executed on an account server. A processing result is then forwarded the remote computing device and e.g. displayed on the remote computing device without any further interaction of the user of the remote computing device being required.
  • the technical effect of the above is that the man-machine interaction is improved because a user of the mobile device may initiate a data transfer via a mobile phone by requesting a transaction application that resides on a server.
  • the transaction application is provided with a content identifier that is to be processed by the transaction application.
  • the results that are achieved by the transaction application are provided to the target of the data transfer, in particular to the remote computing device without any further interaction needed.
  • man machine interaction is improved, since with little or no interaction by the user of the remote computing device, the transaction application is executed on the account server and the results thereof are forwarded to the remote computing device without any interaction of the user of the remote computing device being necessary.
  • the target processing result is data obtained or generated at the account server, which data is ultimately intended for and forwarded to the remote computing device.
  • the interaction server system is further operable to transmit the target identifier to the account server.
  • the account server is operable to process the target identifier; and the interaction server is operable to receive a response from the account server.
  • the response includes target authentication data.
  • the interaction server is further operable to transmit the target authentication data to the mobile device.
  • transmitting the target authentication data to the mobile device completes the initiation.
  • the above features enable the sender that utilizes the mobile device to verify the target identifier identifying the target utilizing the remote computing device prior to sending the request for executing the transaction application.
  • the technical effect of these features is enhanced security as the receiver, i.e. the target can be verified by the user of the mobile device in order to avoid a data exchange with a non-authorized target.
  • the interaction server is further operable to receive the request for executing the transaction application from the mobile device.
  • the account server is operable to forward a mobile device processing result to the interaction server.
  • the interaction server is operable to forward the mobile device processing result to the mobile device.
  • the mobile device processing result is data obtained or established at the account server, which data is intended for and ultimately forwarded to mobile device.
  • the above features lead to the technical effect that the sender utilizing the mobile device is provided with an acknowledgment that the data has been successfully transferred.
  • the remote computing device needs not be involved in order to acknowledge that the transaction application has been successfully executed, i.e. the remote computing device needs not be involved in acknowledging the data transfer.
  • the interaction server is operable to authenticate the mobile device prior to receiving a request from the mobile device.
  • the authentication and the receiving of the request may be simultaneously.
  • the above feature has the technical effect that the mobile device is uniquely identified by the interaction server, such that no manipulated requests or target identifiers can be sent from the mobile device.
  • a mobile device user is holding a mobile device user account residing on the account server.
  • a target is holding a target account residing on the account server.
  • the target may also be referred to as a remote computing device user. Accordingly, the remote computing device user may be holding a remote device user account residing on the account server.
  • man machine interaction is improved, since due to the separation of the initiation process and the execution of the transfer application the system in total operates more stable. For example, incompatibilities between the accounts can be detected at an early stage, e.g. before executing the transfer application.
  • the feature has the technical effect that a data exchange between two accounts on the account server may be performed when executing the transaction application on the account server. Accordingly, the data does not have to be transmitted over a network. The security of the data transfer is increased.
  • executing the transaction application includes immediately performing an irreversible data transfer between the mobile device user account and the remote device user account, i.e. the target account.
  • the target can depend on the data transfer.
  • the target can rely thereon that the sender may not undo the data transfer.
  • the request for executing the transaction application includes an identifier of the data to be transferred between the mobile device user account and the remote device user account, i.e. the target account.
  • the target processing result includes a notification to be displayed at the remote computing device that the data to be transferred between the mobile device user account and the remote device user account has been successfully transferred.
  • the mobile device processing result further includes a notification to be displayed at the mobile device that the data transfer of the data to be transferred between the mobile device user account and the remote device user account has been executed.
  • the data to be transferred includes an amount of money to be transferred.
  • the mobile device user account that is the target account, is a bank account.
  • the remote device user account is a bank account.
  • the technical effect of the above feature is that a money transfer can be remotely initiated by a sender, securely performed on a bank account server between two bank accounts residing on said account server.
  • a further technical effect is that the money is transferred instantly from one bank account to another.
  • the receiver of the money, i.e. the target is provided instantly with the confirmation that the amount of money has been successfully transferred. Further, this improves the man-machine interaction, as the sender does not have to carry a card that is utilized in order to initiate a payment instruction. Further to that, the target does not have to provide a device that has to be utilized in order to initiate the payment procedure. Rather, the payment is initiated by the user of the mobile device, in particular by using the mobile device.
  • the amount of money i.e. the data to be transferred between the two accounts
  • the amount of money is defined and input at the mobile device and not at the remote computer, thereby improving the man machine interaction for the user of the remote computer.
  • the total man machine interaction i.e. the sum of interaction at the mobile device and remote computer is improved by initiating the transaction application already in advance, i.e. before inputting the money amount to be transferred.
  • the transaction application can be timely, particularly immediately executed upon request of the user of the mobile device. Accordingly, the waiting time between requesting executing of the transaction application and transferring the data between the accounts is reduced, since authentication and e.g.
  • the mobile device verifies whether the mobile device user account has sufficient funds prior to processing the initiation of the data transfer. This feature reduces the time consumed for a payment process, as the sender is provided with the information that his balance is not sufficient. The trial and error process as known from utilizing smart cards is avoided. Hence, man machine interaction is improved and the amount of necessary user input is reduced.
  • the interaction server and the account server are communicating via a secure communication protocol, e.g. the Hypertext Transfer Protocol Secure (HTTPS).
  • HTTPS Hypertext Transfer Protocol Secure
  • the mobile device is using a secure mobile communication protocol.
  • the mobile device uses encryption software to encrypt any requests prior to sending the requests to the interaction server.
  • the interaction server comprises decryption software in order to decrypt the encrypted requests received from the mobile device.
  • the effect of the above features is improved security, as the data are encrypted prior to be transferred between the entities (i.e. mobile device, transaction server and account server).
  • the target identifier includes data scanned from a QR code.
  • the identifier includes data received via a GPS sensor.
  • the identifier includes data received from mobile network cell data.
  • the identifier includes data received from the target, i.e. the user of the remote computing device.
  • the identifier includes data received from the remote computing device via a short message service (SMS), and/or a multimedia messaging service (MMS), and/or an email, a Bluetooth connection and/or an instant messaging service and/or near field communication (NFC).
  • SMS short message service
  • MMS multimedia messaging service
  • NFC near field communication
  • the interaction server of the network server system prior to receiving the request from the mobile device for initiating a transaction application operated by the account server, is operable to receive an identification request from the mobile device for initiating an identification application operated by the interaction server.
  • the identification request may comprise source location information associated with the mobile device.
  • the interaction server executes the identification application. Executing the identification application may comprise identifying one or more potential target computing devices located within a predetermined range with respect to the mobile computing device. The identification may be based on target location information associated with a target computing device.
  • the interaction server may send an invitation message to the one or more identified target computing devices.
  • the interaction server may receive a transaction request from one or more of the target computing devices.
  • a transaction request comprises a target identifier of one target computing device.
  • the interaction server transmits the target location information and/or the target identifier of each of the one or more target devices to the requesting mobile device.
  • the identification application is terminated.
  • the user of the mobile device may now choose one of the transaction identifiers associated with a transaction request to perform the transaction and initiate a request for executing the transaction application.
  • the identification request contains a source identifier of the source initiating the identification application, i.e. of the mobile device.
  • the source location information and the target location information may be e.g. gathered via multilateration of radio signals between one or more radio towers of a computing network the mobile device is connected to and/or via global positioning system (GPS).
  • GPS global positioning system
  • the users associated with the potential target computing devices are holders of an account located on the account server.
  • the invitation message comprises transaction information associated with the identification request of the mobile computing device.
  • the transaction request is initiated by a user of a target computing device in the case that the user accepts the invitation message.
  • An aspect of the invention relates to a computer-implemented method for a data exchange between a mobile device of a sender and a remote computing device of a target using a network server system, wherein the network server system comprises an interaction server and an account server.
  • the computer-implemented method includes the step of receiving, at the interaction server, a request, from the mobile device, for initiating a transaction application operated by the account server, wherein the request contains a target identifier of the target of the transaction application. Further, after completion of the initiation, the method includes the step of processing a request from the mobile device for executing the transaction application. The request contains a content identifier to be processed by the transaction application.
  • the method further includes the step of transmitting, from interaction server, the request for executing the transaction application to the account server.
  • the method includes the step of executing, at the account server, the transaction application and processing the content identifier by the transaction application.
  • the method includes the step of forwarding a target processing result from the account server to the interaction server and the step of forwarding the target processing result from the interaction server to the remote computing device of the target.
  • the method includes the step of transmitting, from the interaction server system, the target identifier to the account server.
  • the method includes the step of processing, at the account server, the target identifier and the step of receiving, at the interaction server, a response from the account server.
  • the response includes target authentication data.
  • the method includes the step of transmitting, from the interaction server, the target authentication data to the mobile device.
  • the step of transmitting the target authentication data to the mobile device completes the initiation.
  • the method includes the step of receiving, at the interaction server, the request for executing the transaction application from the mobile device.
  • the method includes the step of forwarding, from the account server, a mobile device processing result to the interaction server.
  • the method includes the step of forwarding, from interaction server, the mobile device processing result to the mobile device.
  • the method includes the step of authenticating, at the interaction server, the mobile device prior to receiving, at the interaction server, a request from the mobile device.
  • a mobile device user is holding a mobile device user account residing on the account server.
  • a remote computing device user is holding a remote device user account residing on the account server.
  • the step of executing the transaction application includes immediately performing an irreversible data transfer between the mobile device user account and the remote device user account.
  • the request for executing the transaction application includes an identifier of the data to be transferred between the mobile device user account and the remote device user account.
  • the target processing result includes a notification to be displayed at the remote computing device that the data to be transferred between the mobile device user account and the remote device user account has been successfully transferred.
  • the mobile device processing result further includes a notification to be displayed at the mobile device that the data transfer of the data to be transferred between the mobile device user account and the remote device user account has been executed.
  • the data to be transferred includes an amount of money to be transferred.
  • the mobile device user account is a bank account.
  • the remote device user account is a bank account.
  • the mobile device verifies whether the mobile device user account has sufficient funds prior to the step of processing the initiation of the data transfer.
  • the communication steps between the interaction server and the account server are performed via a secure communication protocol.
  • the mobile device is using a secure mobile communication protocol.
  • the mobile device uses encryption software to encrypt any requests prior to sending the requests to the interaction server.
  • the interaction server comprises decryption software in order to decrypt the encrypted requests received from the mobile device.
  • the target identifier includes data scanned from a QR code.
  • the identifier includes data received via a GPS sensor.
  • the identifier includes data received from mobile network cell data.
  • the identifier includes data received from the target, i.e. the user of the remote computing device.
  • the identifier includes data received from the remote computing device via a short message service (SMS), a multimedia messaging service (MMS), an email, a Bluetooth connection or an instant messaging service or near field communication.
  • SMS short message service
  • MMS multimedia messaging service
  • the interaction server of the network server system prior to receiving the request from the mobile device for initiating a transaction application operated by the account server, is operable to receive an identification request from the mobile device for initiating an identification application operated by the interaction server.
  • the identification request may comprise source location information associated with the mobile device.
  • the interaction server Upon receiving the request, the interaction server executes the identification application.
  • executing the identification application comprises identifying one or more potential target computing devices located within a predetermined range with respect to the mobile computing device based on target location information associated with a target computing device.
  • the interaction server Upon identifying the potential target computing devices, the interaction server sends an invitation message to the identified target computing devices.
  • the interaction server may receive a transaction request from one or more of the target computing devices.
  • a transaction request comprises a target identifier of one or more a target computing devices in particular of each target computing device.
  • the interaction server Upon receiving the transaction request, the interaction server transmits the target location information and/or the target identifier to the requesting mobile device. With this step, the identification application is terminated.
  • the user of the mobile device may now choose one of the transaction identifiers associated with a transaction request to perform the transaction with and initiate a request for executing the transaction application.
  • the identification request contains a source identifier of the source initiating the identification application, i.e. of the mobile device.
  • the source location information and the target location information may be e.g. gathered via multilateration of radio signals between one or more radio towers of a computing network the mobile device is connected to and/or via global positioning system (GPS).
  • GPS global positioning system
  • the users associated with the potential target computing devices are holders of an account located on the account server.
  • the invitation message comprises transaction information associated with the identification request of the mobile computing device.
  • the transaction request is initiated by a user of a target computing device in the case that the user accepts the invitation message.
  • An aspect of the invention relates to a computer program product comprising computer-readable instructions, which, when loaded and executed on a network server system, cause the network server system to perform method steps according to the computer-implemented method outlined above.
  • An aspect of the invention relates to an interaction server for data exchange between a mobile device of a sender, a remote computing device of a target and an account server.
  • the interaction server is operable to receive a request, from the mobile device, for initiating a transaction application operated by the account server.
  • the request contains a target identifier of a target of the transaction application.
  • After completion of the initiation a request from the mobile device for executing the transaction application is processed, wherein the request contains a content identifier to be processed by the transaction application.
  • the request for executing the transaction application is transmitted to the account server such that the account server is executing the transaction application which processes the content identifier.
  • a target processing result is received from the account server and the target processing result is forwarded to the remote computing device of the target.
  • the interaction server is operable to transmit the target identifier to the account server.
  • the interaction server is operable to receive a response from the account server.
  • the response includes target authentication data.
  • the interaction server is operable to transmit the target authentication data to the mobile device. According to an embodiment, transmitting the target authentication data to the mobile device completes the initiation.
  • the interaction server is operable to receive the request for executing the transaction application from the mobile device.
  • the interaction server is operable to receive a mobile device processing result from the account server. According to a preferred embodiment, the interaction server is operable to forward the mobile device processing result to the mobile device.
  • the interaction server is operable to authenticate the mobile device prior to receiving a request from the mobile device.
  • a mobile device user is holding a mobile device user account residing on the account server.
  • a remote computing device user is holding a remote device user account residing on the account server.
  • the execution of the transaction application by the application server includes immediately performing an irreversible data transfer between the mobile device user account and the remote device user account.
  • the request for executing the transaction application includes an identifier of the data to be transferred between the mobile device user account and the remote device user account.
  • the target processing result includes a notification to be displayed at the remote computing device that the data to be transferred between the mobile device user account and the remote device user account has been successfully transferred.
  • the mobile device processing result further includes a notification to be displayed at the mobile device that the data transfer of the data to be transferred between the mobile device user account and the remote device user account has been executed.
  • the data to be transferred includes an amount of money to be transferred.
  • the mobile device user account is a bank account.
  • the remote device user account is a bank account.
  • the mobile device is operable to verify whether the mobile device user account has sufficient funds prior to processing the initiation of the data transfer.
  • the interaction server and the account server are communicating via a secure communication protocol.
  • the mobile device is using a secure mobile communication protocol.
  • the mobile device uses encryption software to encrypt any requests prior to sending the requests to the interaction server.
  • the interaction server comprises decryption software in order to decrypt the encrypted requests received from the mobile device.
  • the target identifier includes data scanned from a QR code.
  • the identifier includes data received via a GPS sensor.
  • the identifier includes data received from mobile network cell data.
  • the identifier includes data received from the target, i.e. the user of the remote computing device.
  • the identifier includes data received from the remote computing device via a short message service (SMS), a multimedia messaging service (MMS), an email, a Bluetooth connection, an action/a transaction using Near Field Communication (NFC) or an instant messaging service.
  • SMS short message service
  • MMS multimedia messaging service
  • NFC Near Field Communication
  • the interaction server of the network server system prior to receiving the request from the mobile device for initiating a transaction application operated by the account server, is operable to receive an identification request from the mobile device for initiating an identification application operated by the interaction server.
  • the identification request may comprise source location information associated with the mobile device.
  • the interaction server Upon receiving the request, the interaction server executes the identification application.
  • executing the identification application comprises identifying one or more potential target computing devices located within a predetermined range with respect to the mobile computing device based on target location information associated with a target computing device.
  • the interaction server Upon identifying the potential target computing devices, the interaction server sends an invitation message to the identified target computing devices.
  • the interaction server may receive a transaction request from one or more of the target computing devices.
  • a transaction request may comprise a target identifier of a target computing device.
  • the interaction server Upon receiving the transaction request, the interaction server transmits the target location information and/or the target identifier to the requesting mobile device. With this step, the identification application is terminated. The user of the mobile device may now choose one of the transaction identifiers associated with a transaction request to perform the transaction with and initiate a request for executing the transaction application.
  • the identification request contains a source identifier of the source initiating the identification application, i.e. of the mobile device.
  • the source location information and the target location information may be e.g. gathered via multilateration of radio signals between one or more radio towers of a computing network the mobile device is connected to and/or via global positioning system (GPS).
  • GPS global positioning system
  • the users associated with the potential target computing devices are holders of an account located on the account server.
  • the invitation message comprises transaction information associated with the identification request of the mobile computing device.
  • the transaction request is initiated by a user of a target computing device in the case that the user accepts the invitation message.
  • An aspect of the invention relates to a computer-implemented account modification application for a mobile device.
  • the computer-implemented account modification application is operable by a user.
  • the account modification application is operable to perform the step of receiving a target identifier of a target. Then, the step of transmitting a request for initiating a transaction application to an interaction server is performed, wherein the request contains the target identifier of the target of the account modification.
  • the account modification application is operable to perform the steps of receiving, at the mobile device, a content identifier from the user and of transmitting a request for executing a transaction application to the interaction server, wherein the request contains the content identifier. Further, the application is operable to perform the step of receiving a mobile device processing result from the interaction server, wherein the mobile device processing result includes a notification that the transaction application has been executed.
  • the computer-implemented account modification application comprises the step of receiving, from the transaction server, a response to the request for initiating the transaction application.
  • the response is preferably provided simultaneously with or after completion of the initiation process and before transmitting the request for execution of the transfer application.
  • the response may include target authentication data.
  • the target authentication data is displayed on the mobile device.
  • the computer-implemented account modification application comprises the step of receiving, from the interaction server, a response to the request for initiating the transaction application, wherein the response includes target authentication data, wherein the target authentication data may be displayed on the mobile device.
  • the above aspects and embodiments in addition to the described improved man machine interaction and other technical advantages, overcome a conventionally known hurdle at a cash desk of a strongly frequented sales point, such as a whole seller, an individual seller, a gas station, a micro business or the like.
  • the sales point may be referred to as a target.
  • Personnel of the sales point may be referred to as a user of a remote computing device.
  • the target and the user of the remote computing device may be identical persons.
  • the above aspects and embodiments overcome the conventionally known hurdle of a sales point that customers may accept delay in the payment process by another customer slowly collecting the money coins and bills need for the payment transaction but the same customers would not accept delay due to electronic payment. Due to the above described splitting of the payment in two, namely the initiating part and the execution of the transaction application part, no delay will happen; the process is even faster than payment with cash money. Hence, the machine aided transfer - in addition to the above described - improves the payment workflow at a sales point. This may be particularly the case, since due to the ignition step, all the necessary connections will be established and the data needed for the payment will be verified upfront, i.e. before the payment process. At the actual payment process, i.e.
  • the account modification application shows the name of the target and the customer can verify the correctness of the target
  • the sales person i.e. the user of the remote computer, indicates the money amount to be paid. For example, the sales person simply tells the customer the money amount. The customer enters this money amount and requests the money transfer, i.e. the request for executing the transaction application, using the money amount entered;
  • the sales person can see the money amount transferred to his account on the display of the remote computer, which can be a tablet pc, a smart phone, or the like or part of his cash machine.
  • the sales person concludes the payment process by acknowledging the money transfer to the customer.
  • an indication may appear to the customer that the transaction is complete, so that the customer does not need to wait for the acknowledgement of the sales person.
  • the customer can verify that he is not deceived.
  • the customer announced payment (initiation of the process) without defining a specific money amount.
  • the money amount (content identifier) will only be indicated at a later time (request for executing the transaction application). Typically this request is carried out while the sales person is occupied with completing the order.
  • the initiator i.e. the user of the mobile device
  • the target provides the initiator with an identifier of the target device, e.g. via an SMS or simply tells the initiator the identifier of the target.
  • the identifier can be a user account (name/number), a number of the mobile phone, etc.;
  • the initiator starts the application, in particular the above described account modification application
  • the initiator selects money transfer from the application
  • the initiator selects the target
  • the account modification application shows the name of the target and the initiator can verify the correctness of the target
  • the initiator enters the received amount of cash, possibly with some extra fee, and requests the money transfer, i.e. the request for executing the transaction application, using the entered amount;
  • the target can see the amount of money transferred to his, i.e. the target's account on the display of the target device, which can be a tablet pc, a smart phone, or the like.
  • the target concludes the payment process by acknowledging the money transfer to the initiator.
  • an indication may appear to the initiator that the transaction is complete, so that the initiator does not need to wait for the acknowledgement of the target.
  • the user starts the application, in particular the above described identification application; 2. the user initiates an identification request from the mobile device for initiating the identification application operated by the interaction server;
  • the interaction server extracts source location information associated with the mobile device and identifies one or more potential target computing devices located within a predetermined range, e.g. between 1 and 20 m, more than 1 m and less than 20 m, preferably less than 5 m with respect to the mobile device based on corresponding target location information;
  • the interaction server sends an invitation message to the identified target computing devices containing requested transaction information, for example the request of the user may comprise the request of a money transfer from the user account to an account of the user of the target device in exchange for receiving cash money from the holder of the target device, optionally including an additional fee in exchange for the service of receiving cash money;
  • a transaction request is sent from the target computing device to the interaction server comprising a target identifier of the target computing device;
  • the interaction server transmits the target location information and the target identifier to the mobile device, which terminates the above described identification application since the mobile device has now been provided with the necessary target identifier;
  • the user of the mobile device selects one of the target devices to perform the transaction with.
  • the user of the mobile device receives cash money from the user of the selected target computing device; in the case that the user of the mobile device has been provided with one identifier of one potential target device, the user of the mobile device receives cash from the user of the target computing device;
  • the user of the mobile device selects money transfer from the application; 10. the user of the mobile device selects the target by utilizing the received target identifier;
  • the account modification application shows the name of the target and the user of the mobile device can thereby verify the correctness of the target
  • the customer enters the amount of money received and optionally plus some additional fee to account for the cash received from the user of the target device and requests the money transfer, i.e. the request for executing the transaction application, using the amount of money entered;
  • the user of the target device can see the amount of money transferred to his account on the display of the remote computer, i.e. the target device, which can be any computing device.
  • the user of the target device concludes the payment process by acknowledging the money transfer to the user of the mobile device.
  • an indication may appear to the customer that the transaction is complete, so that the user does not need to wait for the acknowledgement of the target.
  • Fig. 1 shows a use case diagram of a network server system suitable for enabling data exchange between a mobile device of a sender and a remote computing device of a target and the steps performed between the mobile device of the sender and the remote computing device of the target;
  • Fig. 2 shows a home screen as can be displayed on a mobile device of an exemplary account modification application showing exemplary functionalities provided by the account modification application;
  • Fig. 3 shows two prerequisites that need to be met prior to initiation of the transaction application operated by an account server;
  • Fig. 4 represents the screen which is displayed to the user of the mobile device when selecting and/or activating the icon for initiating a money transfer;
  • Fig. 5 shows the mobile devices processing result displayed at the mobile device;
  • Fig. 6 shows a computer system including a mobile computing environment coupled to a remote device.
  • Figure 1 shows a network service system as well as steps that are carried out in relation to the network service system.
  • the network service system may comprise a mobile device 110 as well as an interaction server 112 and an account server 114.
  • the interaction server 112 may also be referred to as a push server.
  • the interaction server 112 and the account server 114 may be arranged on one single hardware device as two different software implementations. As such, the interaction server 112 and the accounting server 114 may be two independent software applications or programs.
  • the interaction server 112 and the accounting server 114 may be implemented as by one software application and be different services of this one software application. In an embodiment, the interaction server 112 and the account server 114 may be implemented as two different hardware devices.
  • the mobile device 110 may be operable to transmit requests to the interaction server 112, and the mobile device 110 may further be operable to receive requests from the interaction server 112.
  • the interaction server 112 may be able to receive requests and transmit, e.g. push requests or content of requests to the account server 114.
  • the interaction server 112 may receive a response from the account server 1 4 to a request forwarded to the account server 114.
  • the interaction server 112 may transmit, e.g. push the response received from the account server 114 to a mobile device 110 or a remote computing device 116.
  • the remote computing device 116 can be a conventional cashing device of a sales person or the like.
  • the remote computing device 116 can be a conventional personal computer or a mobile device such as a mobile phone, smart phone, a tablet pc or the like.
  • the interaction server 112 is operable to receive requests from the mobile device 110.
  • the interaction server 112 is operable to initiate, in response to receiving an identification request from the mobile device 110, an identification application that is also operated by the interaction server 112.
  • the identification request may comprise source location information associated with the mobile device 110.
  • the identification request may further comprise a source identifier of the source initiating the identification request, i.e. of the requesting mobile device.
  • the interaction server 112 may execute the identification application.
  • the interaction server 112 may identify one or more potential target computing devices located within a predetermined range with respect to the requesting mobile computing device 110 based on target location information associated with the one or more potential target computing devices.
  • the users of the one or more potential target computing devices may be holders of an account located on the account server.
  • the source location information, i.e. the location information associated with the requesting mobile device 110, and the target location information, i.e. the location information associated with the one or more target computing devices may be gathered via multilateration of radio signals between one or more radio towers of a computing network the mobile device 110 is connected to and/or via global positioning system (GPS).
  • GPS global positioning system
  • the interaction server may send an invitation message to the identified target computing devices.
  • the invitation message may comprise transaction information associated with the identification request of the requesting mobile computing device 110.
  • the interaction server 112 may receive a transaction request form the one or more of the identified target computing devices, wherein the transaction request may comprise a target identifier of the corresponding target computing device.
  • the transaction request may be initiated by the user of the target computing device in the case that the user accepts the invitation message.
  • the interaction server 112 may transmit the target location information and the target identifier to the requesting mobile device 110.
  • the identification application may terminate.
  • the account server 114 is operable to receive requests from the interaction server 112 and to execute a transaction application operated by the account server 1 4.
  • the transaction application may be triggered by a request from the interaction server 12 for executing the transaction application.
  • the transaction application may be any kind of application known by a person skilled in the art, e.g. a service application, a daemon or the like.
  • the transaction application may be operable to transfer a certain money amount from one account, namely the account of the owner of the mobile device 110, to the account of a target, such as a sales person or a sales company.
  • the transaction application may be operable to transfer a certain money amount from one account, namely the account of the owner of an application operated on and/or by the mobile device 110, to the account of a target, such as a sales person or a sales company.
  • the account server 1 4 is operable to forward processing results of the execution of the transaction application to the interaction server 112.
  • the remote computing device 116 may not be operable to communicate with the interaction server 112, that is preferably there may exclusively exist a one way communication path between the remote computing device 116 and the interaction server 112 such that messages can be received from the interaction server 112 at the remote computing device 116. As an example, a message may be pushed from the interaction server 112 to the remote computing device 116, but not wee versa.
  • the remote computing device 116 may receive notifications from the interaction server 112.
  • FIG. 1 an exemplary data exchange between the mobile device 110 of the user 118 of the mobile devicel 0 and the remote computing device 116 of the target of the transaction application is shown.
  • the user 118 of the mobile device 110 may also be referred to as sender 118.
  • the mobile device 110 may receive from the sender 118 an indication that a data exchange is to be initiated. Such an indication can be made by pressing or selecting a respective button, icon or the like on the mobile device 110.
  • the mobile device 110 may receive a target identifier of the target of the transaction application.
  • the target identifier may be any kind of identifier suitable for identifying a target, e.g.
  • QR code is a code of identification data of the target
  • Step S112 may include, for example, scanning a bar code, a QR code, or the like, using the mobile device 110.
  • the mobile device 110 may transmit a request to the interaction server 112 for initiating the transaction application, which resides on the account server 114.
  • the request for initiating the transaction application may include the target identifier that represents the target or personnel 120 of the target of the transaction application.
  • the request for initiating the transaction application may include an identifier of the target.
  • the identifier may be a number and/or an id of the target that the account server 14 can identify.
  • the request may be transmitted via a mobile network. Further, the request may be transmitted using a secure mobile communication protocol.
  • the mobile device 110 may optionally use encryption software to encrypt any requests prior to sending the request to the interaction server 112.
  • the interaction server 112 may transmit the target identifier to the account server 114.
  • the account server 114 may process the target identifier, wherein processing the target identifier may include detecting whether the target, which is identified by the target identifier, holds a remote device user account on the account server 114. If the target holds the remote device user account on the account server 114, the account server 114 may process at step S118 a response to the interaction server 112.
  • the response may be or contain a variable indicating that the target holds an account on the account server 114 or not.
  • the response to the interaction server 112 may also include target authentication data, such as name and/or add ress of the target.
  • Step S120 the interaction server 112 may transmit the target authentication data and/or the parameter indicating that the target holds an account at the account server 14 to the mobile device 1 0.
  • Step S120 may be the step that completes the initiation.
  • the target identifier and the target authentication data may not be identical.
  • the target identifier may be data scanned by the mobile device 110 from a QR code.
  • the target identifier may be a telephone number and/or a machine processable number.
  • the target identifier may be received from the remote computer 116, i.e. the target.
  • the target identifier may be transmitted from the remote computer 116 to the mobile device 110 via a short message service (SMS), a multimedia messaging service (MMS), an email, a Bluetooth connection, an action/a transaction using Near Field Communication (NFC) or an instant messaging service.
  • SMS short message service
  • MMS multimedia messaging service
  • NFC Near Field Communication
  • the mobile device 110 transmits the telephone number to the interaction server 1 2.
  • the interaction server 112 transmits the telephone number to the application server 14.
  • the application server searches its account-holder-database for the telephone number. In case the telephone number is found, the account server 114 has successfully detected that a target holds an account on the account server 114 and has the telephone number received from the interaction server 112. Accordingly, the account server 114 may extract further information about the target, i.e. the account holder, e.g. his name and/or his address, which represents parts or all of the authentication data. Further to that, the account server 114 may transmit the authentication data to the interaction server 112, and the interaction server 112 may transmit the authentication data to the mobile device 110. The authentication data may then be displayed to the user of the mobile device 110. Accordingly, the user of the mobile device 110 can verify the target that has been chosen based on the target identifier.
  • the mobile device 10 may contain a list of favorite targets.
  • the list of favorite targets may be maintained by the user 118 of the mobile device 110.
  • the list of favorite targets may include target identifiers.
  • the user 118 of the mobile device 110 may be able to choose the target identifier from the list of favorites. Accordingly, the mobile device 110 may receive at step S112 the target identifier from the list of favorites. If the target is selected from the list of favorites, it may be assumed that the target owns a remote device user account on the account server 114. However, at step S114, the mobile device 110 transmits the request for initiating the transaction application which may include the target identifier of the target from the list of favorites.
  • the interaction server 112 may transmit the target identifier to the account server 114.
  • the account server 14 may verify whether the remote device user account of the target identified by the target identifier is still valid. With verifying the remote device user account of the target, the initiation process may be completed.
  • the mobile device 110 may initiate an identification application operated by the interaction server 12.
  • the interaction server 1 2 may receive an identification request from the mobile device 110.
  • the identification request may comprise source location information associated with the mobile device 110.
  • the identification request may further comprise a source identifier of the source initiating the identification request, i.e. of the requesting mobile device.
  • the interaction server 112 may execute the identification application.
  • the interaction server 112 may identify one or more potential target computing devices located within a predetermined range with respect to the requesting mobile computing device 110 based on target location information associated with the one or more potential target computing devices.
  • the users of the one or more potential target computing devices may be holders of an account located on the account server.
  • the source location information i.e. the location information associated with the requesting mobile device 1 0, and the target location information, i.e. the location information associated with the one or more target computing devices, may be gathered via multilateration of radio signals between one or more radio towers of a computing network the mobile device 110 is connected to and/or via global positioning system (GPS).
  • GPS global positioning system
  • the interaction server may send an invitation message to the identified target computing devices.
  • the invitation message may comprise transaction information associated with the identification request of the requesting mobile computing device 110.
  • the interaction server 112 may receive a transaction request form the one or more of the identified target computing devices, wherein the transaction request may comprise a target identifier of the corresponding target computing device.
  • the transaction request may be initiated by the user of the target computing device in the case that the user accepts the invitation message.
  • the interaction server 112 may transmit the target location information and the target identifier to the requesting mobile device 110.
  • the identification application may terminate.
  • Step S124 may comprise a verbal communication between sender 118 and user 120. Additionally or alternatively Step S124 may comprise that the remote computer 116 provides the content identifier. That is, the remote computer 116 may display a money amount that needs to be transferred. Additionally or alternatively, the remote computer 116 may send via a wireless connection, such as WiFi or Bluetooth the content identifier to the mobile device 110.
  • the mobile device 110 may receive the content identifier of the data to be transferred from the sender 118 manually e.g. through the user 118 or (semi) automatically from the remote computer 116.
  • the interaction server 112 may receive a request for executing the transaction application from the mobile device 110, wherein the request may include the verified target identifier and the content identifier.
  • the interaction server 112 may transmit the request for executing the transaction application to the account server 114.
  • the account server 114 may process the transaction application. Processing the transaction application may include identifying a mobile device 110 user account held by the sender 118, e.g. by utilizing log-in data of the sender 118 or by utilizing a unique device identification number of the mobile device 110 utilized by the sender 118. Further, processing the transaction application may include identifying the remote device user account of the target of the transaction application by the target identifier. Further to that, processing the transaction application may include a data transfer of the data identified by the content identifier from the mobile device 110 user account to the remote device user account of the receiver. For example, if the content identifier is an identifier of an amount of money to be transferred, the amount of money may be transferred from the mobile device 110 user account to the remote device user account, i.e. the target user account.
  • the transfer of the data between the mobile device 110 user account and the remote device user account may be performed immediately. In another embodiment, the transfer of the data may be performed at a later point in time. The data transfer may be irreversible.
  • the interaction server 112 may receive a mobile device 110 processing result from the account server 114, wherein the mobile device 110 processing result may include a notification to be displayed at the mobile device 110 indicating that the data transfer of the data to be transferred between the mobile device 110 user account and the remote device user account has been executed successfully.
  • the mobile device 110 may receive the mobile device 110 processing result and display it on the mobile device 110 display. For example, if the data to be transferred between the mobile device 110 user account and the remote device user account is an amount of money to be transferred between two bank accounts, the mobile device 110 processing result may include the new account balance of the account of the sender 118.
  • the account server 114 may transmit a target processing result to the interaction server 112, wherein the target processing result may include a notification to be displayed at the remote computing device 116, indicating that the data to be transferred between the mobile device 110 user account and the remote device user account has been successfully transferred.
  • the interaction server 112 may transmit the target processing result to the remote computing device 116.
  • the remote computing device 116 may display the notification to be displayed on its display.
  • Steps S142 and S144 may be carried out in the above order or in a reversed order or simultaneously.
  • the interaction server 112 may be a push server. According to a further embodiment of the invention, the interaction server 112 and the account server 114 may communicate via a secure communication protocol like for example HTTPS (hypertext transfer protocol secure). According to a further embodiment of the invention, a unique identifier of the mobile device 110 may be stored at the interaction server 112 such that whenever the interaction server 112 receives a request from the mobile device 110, the interaction server 112 may transmit the request from the mobile device 110 together with the unique identification number of the mobile device 110 to the account server 114. Accordingly, the account server 114 may be able to identify the mobile device 110 user account.
  • HTTPS hypertext transfer protocol secure
  • the sender 118 may be forced to perform a log in procedure by e.g. using an account modification application.
  • the user may be able to be logged-in via any mobile device 110 to the interaction server 12 because the interaction server 112 can uniquely identify the sender 118 from the log in data.
  • steps S136 and S140 i.e. transmitting the target processing result and the mobile device 110 processing result from the account server 114 to the interaction server 112 may be performed simultaneously.
  • steps S110, S 12 and S128 may be performed simultaneously.
  • the present invention provides the advantage that a data transfer, such as a money transfer from one account to another account, can be completely initiated before the actual data transfer is, i.e. the money transfer, is requested. Hence, once such a request for transfer is made, the request can be processed immediately. Therefore, the computer-implemented method provides the advantage that a money transfer once items to be bought are selected, is faster than a conventional money transfer using a debit card or even using money coins and bills, since only one amount has to be entered by the user 118 and a request button selected. The processing has been prepared by the initiation as described above and the actual transfer is faster than even selecting coins in purse or using a debit card, swiping the same through a reader and entering a pin.
  • Figure 2 shows a home screen of an exemplary account modification application.
  • the account modification application may be able to be utilized by any mobile device 1 10.
  • the home screen includes icon 210 which, if triggered e.g. by being touched or clicked, may initiate a screen which may be utilized by the sender 118 to perform a QR code scan.
  • the QR code scanner may be utilized in order to scan and/or read out the target. That is, QR codes may be positioned in a store and a user 1 18 may scan such QR codes using his mobile phone 110 or tablet 1 10.
  • Icon 212 represents an icon which, if triggered, may provide a read out to the sender 118 utilizing the account modification application, wherein the readout displays a list of all transactions that have been completed from the mobile device 1 10 user account.
  • Icon 214 represents an icon which, if triggered, may open a view that may enable the sender 1 18 utilizing the account modification application to collect money. Accordingly, money may be collected from any remote account, e.g. from a second bank account held by the sender 118, and transferred to the mobile device 1 10 user account.
  • Icon 216 may, if triggered, be used to initiate a money transfer from the mobile device 110 user account to a remote device user account.
  • icon 216 is the one that would be triggered by the sender 1 18 if the sender 1 18 wants to perform the data exchange between his mobile device 110 and a remote computing device 116 as explained above.
  • Icon 218 represents an icon which, if triggered, may initiate a screen that may enable the sender 1 18 to identify dealers, i.e. targets, that are located nearby. This identification can be based, for example, on GPS (global positioning system) data, on RFID (radio frequency identification) data or on data received from mobile network cell data.
  • Icon 220 represents an icon which, if triggered, may initiate a screen that allows the user to modify the account modification application, wherein the modification includes for example modification of favorites, the selection of a language, the selection of colors etc.
  • Field 222 represents a read out of the amount of money that may be available on the mobile device 110 user account the sender 118 is holding.
  • Field 224 represents a read out for an online status of the mobile device 110.
  • the icon which is exemplarily represented as a heart icon may indicate that the mobile device 110 is connected to the interaction server 112.
  • Figure 3 focuses on the two fields which represent the requirements that may have to been met in order to initiate the transaction application operated by the account server 114 as outlined above.
  • the first requirement may be that the amount of money which needs to be transferred be available on the mobile device 110 user account.
  • the mobile device 110 user account does not have the required amount of money the user may be able to collect the money from another account.
  • the money transfer may be performed even though there is not enough money on the mobile device 110 user account.
  • the money may then be collected from another account connected to the user.
  • the second requirement for successfully initiating a transaction application operated by the account server 114 may be a connection between the mobile device 110 and the interaction server 112.
  • an online connection between the mobile device 110 and the interaction server 112 may not be necessary. Accordingly, digital certificates may have to be utilized.
  • Figure 4 represents the screen which may be displayed to the user of the mobile device 110 when pressing the icon for initiating a money transfer.
  • the user may need to provide a target identifier of a target of the transaction application.
  • Icon 410 may allow the user to select the target identifier of a list of favorites.
  • Icon 412 if triggered, may enable the user to enter a telephone number which may be used as target identifier.
  • Icon 414 if triggered, may enable the user to scan a QR code such that the scanned data may be used as target identifier.
  • Icon 416 if triggered, may enable the user to switch back to the home screen of the account modification application as represented in Figure 2.
  • Field 418 represents a readout of the amount of money that may be to be transferred from the mobile device 110 user account to the remote device user account. The fact that no amount of money has been inserted in field 418 may provide the interaction server 112 with the information that it is the request for initiating the transaction application rather than the request for executing the transaction application.
  • Figure 5 represents the screen which may be displayed to the user after the target authentication data has been transmitted to the mobile device 110.
  • the target authentication data may have been identified by the account server 114 and transmitted from the interaction server 112.
  • Field 510 represents the read out for the user of the amount of money which may be intended to be transferred.
  • Field 512 represents a display for the target authentication data that may have been received at the mobile device 10 as response to the request for initiating the data transfer. Accordingly, the sender 118 is able to verify the target authentication data of the target.
  • Figure 6 represents the push screen that may be presented as a read out for the target processing result to the user 120 of the remote computing device 116.
  • the display on the remote computing device 116 may be updated at given time intervals, such as e.g. every 5 seconds, every 10 seconds, every 15 seconds, or the like. The interval may be at least 5 seconds and at most 60 seconds.
  • Field 610 represents a payment which may have been performed more than a predefined period of time ago, for example more than thirty minutes ago. Accordingly, the read out may appear smaller in the screen as the chances that the user of the remote computing device 116 has already perceived the incoming payment are considered to be high.
  • Field 612 represents a payment which may have been performed prior to the predefined period of time ago, for example less than five minutes ago.
  • the field may be represented bigger. Further, only a fixed amount of number of the latest transactions may be displayed on the push screen, e.g. the last 6 transactions. As an example between 1 and 20 latest transactions may be displayed. According to another example between 5 and 15 latest transactions may be displayed.
  • the push screen may be implemented as a news ticker. In the push screen older transactions may be less visible than newer transactions. As an example, older transactions may fade out slowly by reducing color intensity and/or brightness.
  • the user interface may not be utilized for any interactions like canceling a money transfer. However, the remote computing device 116 may utilize a specific application that enable the user 120 of cancellations of money transactions that have been executed according to the invention as outlined above.
  • Providing the user 120 of the remote computing device 1 6 with a screen, which pushes the target processing result to the remote computing device 116 of the target, wherein the result is displayed on the remote computing device 116, may enable an improved man-machine interaction.
  • the user 120 needs to perform a conventional log in into the target's bank account in order to verify whether a payment has been executed or not. Further to that, conventionally, the payment is not performed instantly. Accordingly, the user 120 would not be able to check whether a money transfer has been performed as he would have to wait a certain amount of time for the booking.
  • the user 120 is relieved from this problem, as any payment that needs to be performed on the remote device user account is performed on the fly and pushed to the remote computing device 116.
  • the user of the remote computing device 116 may identify any payment.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne de manière résumée un système de serveurs en réseau qui est utilisé pour l'échange de données entre un dispositif mobile 110 d'un expéditeur 118 et un dispositif informatique distant 116 d'une cible, le système de serveurs en réseau comprenant un serveur d'interactions 112 et un serveur de comptes 114. Le serveur d'interactions 112 sert à recevoir du dispositif mobile 110 une demande de lancement d'une application de transaction exécutée par le serveur de comptes 114, la demande contenant un identificateur pour la cible de l'application de transaction. Une fois le lancement effectué, une demande d'exécution de l'application de transaction provenant du dispositif mobile 110 est traitée, la demande contenant un identificateur de contenu à traiter par l'application de transaction. Le serveur d'interactions 112 envoie la demande d'exécution de l'application de transaction au serveur de comptes 114. Le serveur de comptes 114 sert à exécuter l'application de transaction et à faire traiter l'identificateur de contenu par l'application de transaction. Le serveur de comptes 114 sert également à envoyer un résultat de traitement de cible au serveur d'interactions 112. Le serveur d'interactions 112 sert aussi à envoyer le résultat de traitement de cible au dispositif informatique distant 116 de la cible.
PCT/EP2014/000792 2013-03-25 2014-03-24 Système de serveurs en réseau, procédé d'échange de données, produit de programme d'ordinateur, serveur d'interactions et application de modification de compte mise en œuvre par ordinateur WO2014154349A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EPPCT/EP2013/000898 2013-03-25
PCT/EP2013/000898 WO2014154224A1 (fr) 2013-03-25 2013-03-25 Système de serveur réseau, procédé d'échange de données, produit-programme informatique, serveur d'interaction et application de modification de compte mis en œuvre par ordinateur

Publications (1)

Publication Number Publication Date
WO2014154349A1 true WO2014154349A1 (fr) 2014-10-02

Family

ID=48141890

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/EP2013/000898 WO2014154224A1 (fr) 2013-03-25 2013-03-25 Système de serveur réseau, procédé d'échange de données, produit-programme informatique, serveur d'interaction et application de modification de compte mis en œuvre par ordinateur
PCT/EP2014/000792 WO2014154349A1 (fr) 2013-03-25 2014-03-24 Système de serveurs en réseau, procédé d'échange de données, produit de programme d'ordinateur, serveur d'interactions et application de modification de compte mise en œuvre par ordinateur

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/EP2013/000898 WO2014154224A1 (fr) 2013-03-25 2013-03-25 Système de serveur réseau, procédé d'échange de données, produit-programme informatique, serveur d'interaction et application de modification de compte mis en œuvre par ordinateur

Country Status (1)

Country Link
WO (2) WO2014154224A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003007538A1 (fr) * 2001-07-12 2003-01-23 Icontrol Transactions, Inc. Systeme, procede et model fonctionnel pour l'authentification et la non-repudiation des transactions dans un reseau mobile sans fil
US20090319425A1 (en) * 2007-03-30 2009-12-24 Obopay, Inc. Mobile Person-to-Person Payment System
US20120215690A1 (en) * 2011-01-25 2012-08-23 Ewise Systems Pty Ltd Method and apparatus for facilitating payment via mobile networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003007538A1 (fr) * 2001-07-12 2003-01-23 Icontrol Transactions, Inc. Systeme, procede et model fonctionnel pour l'authentification et la non-repudiation des transactions dans un reseau mobile sans fil
US20090319425A1 (en) * 2007-03-30 2009-12-24 Obopay, Inc. Mobile Person-to-Person Payment System
US20120215690A1 (en) * 2011-01-25 2012-08-23 Ewise Systems Pty Ltd Method and apparatus for facilitating payment via mobile networks

Also Published As

Publication number Publication date
WO2014154224A1 (fr) 2014-10-02

Similar Documents

Publication Publication Date Title
RU2698767C2 (ru) Обработка аутентификации удаленной переменной
US10657582B2 (en) Method, user terminal, and service terminal for processing service data
US10922674B2 (en) Dongle device for automatic pairing of payment terminal to mobile computing device
US8489067B2 (en) Methods and systems for distribution of a mobile wallet for a mobile device
US8121945B2 (en) Methods and systems for payment method selection by a payee in a mobile environment
US8145568B2 (en) Methods and systems for indicating a payment in a mobile environment
CN109074571B (zh) 基于近场通信nfc的交易方法和设备
US20150120504A1 (en) Systems and methods for completion of item delivery and transactions using a mobile beacon
WO2018005875A1 (fr) Diffusions d'identifiant localisées pour alerter des utilisateurs de processus disponibles et récupérer des données de serveur en ligne
US20130013501A1 (en) Methods and systems for making a payment via a stored value card in a mobile environment
US20120136754A1 (en) Automatic tab payment from a user device
US20120290468A1 (en) Method and apparatus for secure payment using a network-connectable device
KR20150038246A (ko) 비인터넷 연결 장치에 전자 지불을 위한 시스템 및 방법
EP2817770A1 (fr) Procédé et système de traitement de transactions
US20150348004A1 (en) Mobile merchant check-in at a user's home location
KR20130109912A (ko) 스마트 단말과 콜센터를 이용한 하이브리드 전자상거래 제공방법 및 이를 위한 프로그램을 기록한 컴퓨터로 판독가능한 기록매체
WO2011126756A1 (fr) Authentification par deux dispositifs
CN110945552A (zh) 一种产品销量提报方法、支付方法和终端设备
WO2012168457A1 (fr) Transactions électroniques
JP7303664B2 (ja) 情報処理装置、情報処理方法及びプログラム
US11257063B2 (en) Telephone call purchase with payment using mobile payment device
US12020228B2 (en) Apparatus and method for payment processing
KR20150082775A (ko) 문자메시지를 이용한 이체방법 및 시스템
WO2014154349A1 (fr) Système de serveurs en réseau, procédé d'échange de données, produit de programme d'ordinateur, serveur d'interactions et application de modification de compte mise en œuvre par ordinateur
KR101407398B1 (ko) 스마트 단말을 이용한 하이브리드 전자상거래 제공방법 및 이를 위한 프로그램을 기록한 컴퓨터로 판독가능한 기록매체

Legal Events

Date Code Title Description
DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14714937

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 01/12/2015)

122 Ep: pct application non-entry in european phase

Ref document number: 14714937

Country of ref document: EP

Kind code of ref document: A1