Method for exchanging data concerning an electronic transaction

• US 20050071238A1
• Filed: 12/02/2002
• Published: 03/31/2005
• Est. Priority Date: 12/05/2001
• Status: Abandoned Application

• Current Assignee: Mobileway
• Original Assignee: Mobileway
• Inventors: Guillot, Carles
• Application Number:
  US10/497,680
• Publication Number:
  US 20050071238A1
• Time in Patent Office: Days
• US Class Current: 705/26
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0267 Wireless devices
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

A method for exchanging data concerning an electronic transaction between two entities, includes: a step which consists in determining and booking an origin address (TPOA) in conformity with a bidirectional mobile telephony (GSM) digital messaging service protocol (SMS); a step which consists in sending in accordance with the protocol (SMS), an offer message (OFFRE_SMS) of the transaction (TR), the offer message (OFFRE_SMS) being sent from the first the (MW) and addressed to the second entity (CL); and a step which consists in sending, from the second entity (CL) and addressed to the first entity (MW), a reply message comprising an information (REP) representing acceptance or rejection of the transaction.

Claims

1. Method of exchanging data relating to an electronic transaction between a first entity (MW) and a second entity (CL), said transaction (TR) being identified by an identifier (TR_ID), which method is characterized in that it comprises:

a step of determining and reserving an origin address (TPOA) conforming to a bidirectional digital mobile telephony (GSM) messaging protocol (SMS), said determination being effected as a function of said identifier (TR_ID) of said transaction (TR) and an identifier (CL_TEL) of said second entity (CL);

a step of sending a message (OFFER_SMS) in accordance with said protocol (SMS) offering said transaction (TR), said offer message (OFFER_SMS) being sent from said first entity (MW) to said second entity (CL) and containing said origin address (TPOA) reserved during said determination and reservation step; and

in the event of explicit acceptance or refusal of said transaction (TR), a step of sending from said second entity (CL) to said first entity (MW) a response message (RESPONSE_SMS) conforming to said protocol (SMS) to said offer message (OFFER_SMS), said response message containing information (REP) representative of acceptance or rejection of said transaction.

2. Data exchange method according to claim 1, characterized in that said first entity (MW) is adapted to repeat the step of sending said offer message (OFFER_SMS).

3. Data exchange method according to either claim 1, characterized in that it comprises, prior to said step of determining said origin address (TPOA), a step of sending a message (TR_DEF) defining said transaction (TR) from a third entity (BQ) to said first entity (MW), said definition message (TR_DEF) containing said transaction identifier (TR_ID) and an identifier (CL_TEL) of said second entity (CL).

4. Data exchange method according to claim 3, characterized in that said origin address (TPOA) is further determined as a function of an identifier (BQ_N) of said third entity (BQ).

5. Data exchange method according to claim 3, characterized in that said definition message (TR_DEF) further comprises a validity period (VP) of said transaction (TR).

6. Data exchange method according to claim 5, characterized in that said origin address (TPOA) is determined as a function of said validity period (VP).

7. Data exchange method according to claim 3, characterized in that said origin address (TPOA) is determined in a predetermined list (LS) known to said third entity (BQ) and to said second entity (CL).

8. Data exchange method according to claim 7, characterized in that said origin address (TPOA) is determined cyclically from said predetermined list (LS).

9. Data exchange method according to claim 3, characterized in that, on reception of said response message (RESPONSE_SMS), said first entity (MW) sends a response notification (RESPONSE_TR) to said third entity (BQ), said response notification containing said information (REP).

10. Data exchange method according to claim 9, characterized in that it comprises, prior to said step of sending the response message (RESPONSE_SMS), a step of inserting a code (PIN) representative of said second entity (CL) into said response message (RESPONSE_SMS).

11. Data exchange method according to claim 10, characterized in that said code (PIN) representative of a user of said second entity (CL) is inserted into said response notification (RESPONSE_TR).

12. Data exchange method according to claim 9, characterized in that, on reception of said response notification (RESPONSE_TR), said third entity (BQ) sends an acknowledgement message (ACK) to said first entity (MW).

13. Data exchange method according to claim 3 characterized in that, if no response message (RESPONSE_SMS) is received during said validity period (VP), said first entity (MW) sends a non-response notification message (NON-RESPONSE_TR) to said third entity (BQ).

14. Data exchange method according to claim 12, characterized in that, on reception of said non-response notification (NON-RESPONSE_TR), said third entity (BQ) sends an acknowledgement message (ACK) to said first entity (MW).

15. Data exchange method according to claim 14, characterized in that, on reception of said acknowledgement message (ACK), said first entity (MW) releases said origin address (TPOA) reserved during said obtaining and reservation step.

16. Data exchange method according to claim 14, characterized in that, on reception of said acknowledgement message (ACK), said first entity (MW) retains said origin address (TPOA) in order to allow said transaction (TR) to continue.

26. Data exchange method according to claim 10, characterized in that it comprises, prior to said step of sending the response message (RESPONSE_SMS), a step of inserting a code (PIN) representative of said second entity (CL) into said response message (RESPONSE_SMS).

17. Device for exchanging data relating to an electronic transaction with a second entity (CL), said transaction (TR) being identified by an identifier (TR_ID), characterized in that it comprises:

means (10) for determining and reserving an origin address (TPOA) conforming to a bidirectional digital mobile telephony (GSM) messaging protocol (SMS), said determination being effected as a function of said identifier (TR_ID) of said transaction (TR) and an identifier (CL_TEL) of said second entity (CL);

means (20) for sending a message (OFFER_SMS) in accordance with said protocol (SMS) offering said transaction (TR), said offer message (OFFER_SMS) being sent to said second entity (CL) and containing said origin address (TPOA) reserved during said determination and reservation step; and

means (30) for receiving, from said second entity (CL), a response message (RESPONSE_SMS) conforming to said protocol (SMS) and responding to said offer message (OFFER_SMS), said response message comprising information (REP) representative of acceptance or rejection of said transaction.

18. Data exchange device according to claim 17, characterized in that said sending means (20) are adapted to repeat the sending of said offer message (OFFER_SMS).

19. Data exchange device according to claim 17, characterized in that it comprises means (40) for receiving a message (TR_DEF) defining said transaction (TR) from a third entity (BQ), said definition message (TR_DEF) containing said transaction identifier (TR_ID) and an identifier (CL_TEL) of said second entity (CL).

20. Data exchange device according to claim 17 characterized in that said determination and reservation means (10) are further adapted to determine said origin address (TPOA) as a function of an identifier (BQ_N) of said third entity (BQ).

21. Data exchange device according to claim 19, characterized in that said definition message (TR_DEF) further comprising a validity period (VP) of said transaction (TR), said determination and reservation means (10) are adapted to determine said origin address (TPOA) as a function of said validity period (VP).

22. Data exchange device according to claim 19, characterized in that said determination and reservation means (10) are adapted to determine said origin address (TPOA) in a predetermined list (LS) known to said third entity (BQ) and to said second entity (CL).

23. Data exchange device according to claim 22, characterized in that said determination and reservation means (10) are adapted to determine said origin address (TPOA) in said predetermined list (LS) cyclically.

24. Data exchange method according to claim 19, characterized in that it further comprises means (50) for sending a response notification (RESPONSE_TR) adapted, on reception of said response message (RESPONSE_SMS), to send said response notification (RESPONSE_TR) to said third entity (BQ), said response notification containing said information (REP).

25. Data exchange device according to claim 17, characterized in that it further comprises means (60) for releasing said origin address (TPOA) reserved by said obtaining and reservation means (10).