IP Library Granted Patent US 11,501,218
Granted Patent B2
US 11,501,218 · App. 14/695,707 · Granted Nov 15, 2022

Booking method and system

Inventor: Jukka Kalevi Salonen (Luhtajoki, FI)
G06Q10/02G06Q10/025G06Q10/109G06Q10/1095G06Q20/322G06Q20/3221G06Q20/3255G06Q20/40G06Q20/4014G06Q30/0267G06Q30/0601G06Q30/0609G06Q30/0623G06Q50/14H04L51/18H04L51/23H04L67/01H04L67/10H04M3/42382H04W4/12H04W4/14H04W4/40H04W4/50H04W12/06G08G1/207H04L2101/37H04W12/71H04W12/72
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,501,218
App. No.
14/695,707
Granted
Nov 15, 2022
Kind
B2
Abstract

The invention relates to a method and system for booking reservations in a booking system and synchronizing bookings among several booking systems. The system comprises at least one booking system; at least one service provider; a mediator service; a client, and at least one client terminal device that can be a mobile device and that includes a dialogue. The client uses the dialogue to enter information into the system and the mediator receives inquiries and answers from the at least one booking system, the at least one service provider, and the at least one client. The mediator transfers and adapts information between them. The method and system are particularly suited for use with mobile phone users by Small Message Service messages.

Claims (66)

1. A network server that controls communications between a provider of products or services and a user, wherein the user is associated with a mobile device having an identifier address and, wherein the network server:

receives an inquiry message at an address related to the provider or at an address related to the network server, the inquiry message being sent from the user's mobile device;

generates a shared secret that is specific to the inquiry message sent from the user's mobile device, wherein the generated shared secret is also specific to and a basis for identifying and authenticating subsequent reply communications received by the network server from the user, and wherein the generated shared secret is also a basis for identifying corresponding communications regarding the inquiry message that occur between the network server and the provider of products or services on behalf of the user;

transmits a reply message containing the generated shared secret to the identifier address of the user's mobile device;

receives an acceptance message sent by the user's mobile device in response to the transmitted reply message; and

determines whether the received acceptance message corresponds to the transmitted reply message based on detection of the generated shared secret in the received acceptance message,

wherein the received acceptance message authorizes a transaction involving a product or service provided by the provider or payment to the provider for the product or service,

wherein the generated shared secret relates to at least one of a reply address included in the transmitted reply message, a choice offered to the user and included in the transmitted reply message, a symbol associated with the choice offer included in the transmitted reply message, a communication channel over which the transmitted reply message was transmitted, or a communication channel upon which the received acceptance message was received, and

wherein the detection of the generated shared secret authenticates the user's authorization of the transaction involving the product or service provided by the provider or payment to the provider for the product or service.

2. The network server of claim 1 , wherein the inquiry message relates to a product or service.

3. The network server of claim 1 , wherein the provider is a booking system for booking a reservation.

4. The network server of claim 1 , wherein the provider is a provider of an on-line banking service and the transaction is a banking transaction.

5. The network server of claim 1 , wherein the provider is a provider of an on-line ticket service and the transaction is a purchase of a ticket.

6. The network server of claim 1 , wherein the provider is in the healthcare field and the transaction is a generation or confirmation of a healthcare appointment for the user.

7. The network server of claim 1 , wherein the provider is a vehicle maintenance organization and the transaction is a generation or confirmation of a vehicle maintenance appointment for the user.

8. The network server of claim 1 , wherein the provider is a hotel and the transaction is a generation or confirmation of a hotel room reservation for the user.

9. The network server of claim 1 , wherein the provider is an airline and the transaction is a generation or confirmation of an airline reservation for the user.

10. The network server of claim 1 , wherein the provider is a car service and the transaction is a generation or confirmation of a car service engagement for the user.

11. The network server of claim 1 , wherein the provider is a communications provider and the transaction is a generation or configuration of a communication connection for the user.

12. The network server of claim 1 , wherein the transmitted reply message uses, as a form of communication, at least one of text messaging, Short Message Service, Multimedia Message Service, electronic-mail, Internet mail, voice mail, Web browser, telephony application, call center, video conference, a Personal Information Manager, a Personal Data Assistant, a pager, facsimile, office equipment or a smart card.

13. The network server of claim 1 , wherein the reply address is compatible with text messaging, Short Message Service, Multimedia Message Service, electronic-mail, Internet mail, voice mail, Web browser, telephony application, call center, video conference, a Personal Information Manager, a Personal Data Assistant, a pager, facsimile, office equipment or a smart card address.

14. The network server of claim 1 , wherein the inquiry message is a text message, Short Message Service message, Multimedia Message Service message, electronic-mail message or Web browser input.

15. The network server of claim 1 , wherein the identifier address is an A-subscriber's number, a Calling Line Identity, an electronic-mail address or an IP address.

16. The network server of claim 1 , wherein the received acceptance message authenticates the user.

17. The network server of claim 1 , wherein the reply address is selected from a plurality of currently available reply addresses.

18. The network server of claim 1 , wherein the reply address is an A-subscriber's number, a Calling Line Identity, an electronic-mail address or an IP address.

19. The network server of claim 1 , wherein the choice is specified in the transmitted reply message.

20. The network server of claim 1 , wherein the symbol includes a letter, a number or another symbol specified in the transmitted reply message.

21. The network server of claim 1 , wherein the communication channel is text messaging, Short Message Service, Multimedia Message Service, electronic-mail, Internet mail, voice mail, Web browser, telephony application, call center, or video conference.

22. The network server of claim 1 , wherein the transmitted reply message is an offer message for a product or service.

23. The network server of claim 1 , wherein the received acceptance message authenticates the user.

24. The network server of claim 1 , wherein the received acceptance message authorizes the transaction involving the product or service provided by the provider.

25. The network server of claim 1 , wherein the received acceptance message authorizes the payment for the product or service provided by the provider.

26. A method for controlling communications between a provider of products or services and a user using a network server, wherein the user is associated with a mobile device having an identifier address, the method comprising:

receiving an inquiry message at an address related to the provider or at an address related to the network server, the inquiry message being sent from the user's mobile device;

generating a shared secret that is specific to the inquiry message sent from the user's mobile device, wherein the generated shared secret is also specific to and a basis for identifying and authenticating subsequent reply communications received by the network server from the user, and wherein the generated shared secret is also a basis for identifying corresponding communications regarding the inquiry message that occur between the network server and the provider of products or services on behalf of the user;

transmitting a reply message containing the generated shared secret to the identifier address of the user's mobile device;

receiving an acceptance message sent by the user's mobile device in response to the transmitted reply message; and

determining whether the received acceptance message corresponds to the transmitted reply message based on detection of the generated shared secret in the received acceptance message,

wherein the received acceptance message authorizes a transaction involving a product or service provided by the provider or payment to the provider for the product or service,

wherein the generated shared secret relates to at least one of a reply address included in the transmitted reply message, a choice offered to the user and included in the transmitted reply message, a symbol associated with the choice offer included in the transmitted reply message, a communication channel over which the transmitted reply message was transmitted, or a communication channel upon which the received acceptance message was received, and

wherein the detection of the generated shared secret authenticates the user's authorization of the transaction involving the product or service provided by the provider or payment to the provider for the product or service.

27. The method of claim 26 , wherein the inquiry message relates to a product or service.

28. The method of claim 26 , wherein the provider is a booking system for booking a reservation.

29. The method of claim 26 , wherein the provider is a provider of an on-line banking service and the transaction is a banking transaction.

30. The method of claim 26 , wherein the provider is a provider of an on-line ticket service and the transaction is a purchase of a ticket.

31. The method of claim 26 , wherein the provider is in the healthcare field and the transaction is a generation or confirmation of a healthcare appointment for the user.

32. The method of claim 26 , wherein the provider is a vehicle maintenance organization and the transaction is a generation or confirmation of a vehicle maintenance appointment for the user.

33. The method of claim 26 , wherein the provider is a hotel and the transaction is a generation or confirmation of a hotel room reservation for the user.

34. The method of claim 26 , wherein the provider is an airline and the transaction is a generation or confirmation of an airline reservation for the user.

35. The method of claim 26 , wherein the provider is a car service and the transaction is a generation or confirmation of a car service engagement for the user.

36. The method of claim 26 , wherein the provider is a communications provider and the transaction is a generation or configuration of a communication connection for the user.

37. The method of claim 26 , wherein the transmitted reply message uses, as a form of communication, at least one of text messaging, Short Message Service, Multimedia Message Service, electronic-mail, Internet mail, voice mail, Web browser, telephony application, call center, video conference, a Personal Information Manager, a Personal Data Assistant, a pager, facsimile, office equipment or a smart card.

38. The method of claim 26 , wherein the reply address is compatible with text messaging, Short Message Service, Multimedia Message Service, electronic-mail, Internet mail, voice mail, Web browser, telephony application, call center, video conference, a Personal Information Manager, a Personal Data Assistant, a pager, facsimile, office equipment or a smart card address.

39. The method of claim 26 , wherein the inquiry message is a text message, Short Message Service message, Multimedia Message Service message, electronic-mail message or Web browser input.

40. The method of claim 26 , wherein the identifier address is an A-subscriber's number, a Calling Line Identity, an electronic-mail address or an IP address.

41. The method of claim 26 , wherein the received acceptance message authenticates the user.

42. The method of claim 26 , wherein the reply address is selected from a plurality of currently available reply addresses.

43. The method of claim 26 , wherein the reply address is an A-subscriber's number, a Calling Line Identity, an electronic-mail address or an IP address.

44. The method of claim 26 , wherein the choice is specified in the transmitted reply message.

45. The method of claim 26 , wherein the symbol includes a letter, a number or another symbol specified in the transmitted reply message.

46. The method of claim 26 , wherein the communication channel is text messaging, Short Message Service, Multimedia Message Service, electronic-mail, Internet mail, voice mail, Web browser, telephony application, call center, or video conference.

47. The method of claim 26 , wherein the transmitted reply message is an offer message for a product or service.

48. The method of claim 26 , wherein the received acceptance message authenticates the user.

49. The method of claim 26 , wherein the received acceptance message authorizes the transaction involving the product or service provided by the provider.

50. The method of claim 26 , wherein the received acceptance message authorizes the payment for the product or service provided by the provider.

Assignments (13)
CHANGE OF NAME Recorded Jan 14, 2022
From: BOOKIT OY; BOOKIT AJANVARAUSPALVELU
To: SMARTCOM LABS OY
Reel/Frame 058736/0054 →
SECURITY INTEREST Recorded May 6, 2020
From: BOOKIT OY
To: BKI INVERS AB
Reel/Frame 052585/0723 →
SECURITY INTEREST Recorded May 6, 2020
From: BOOKIT OY
To: AUTERE, JUSSI
Reel/Frame 052585/0498 →
SECURITY INTEREST Recorded May 6, 2020
From: BOOKIT OY
To: MPJ YHTYMA OY
Reel/Frame 052587/0814 →
SECURITY INTEREST Recorded May 5, 2020
From: BOOKIT OY
To: RANIN, URSULA; ENTRADA OY
Reel/Frame 052581/0396 →
SECURITY INTEREST Recorded May 5, 2020
From: BOOKIT OY
To: RONNHOLM, RIKU; RAHNASTO, ILKKA
Reel/Frame 052579/0001 →
SECURITY INTEREST Recorded May 5, 2020
From: BOOKIT OY
To: PITKANEN, OLLI
Reel/Frame 052579/0136 →
SECURITY INTEREST Recorded Apr 16, 2020
From: BOOKIT OY
To: DUCK POND INVESTMENTS; GODFREY, PETER
Reel/Frame 052425/0192 →
SECURITY INTEREST Recorded Apr 16, 2020
From: BOOKIT OY
To: LOSMAA, MARITTTI
Reel/Frame 052426/0037 →
SECURITY INTEREST Recorded Apr 16, 2020
From: BOOKIT OY
To: KALONIENI, MARKKU
Reel/Frame 052535/0634 →
SECURITY INTEREST Recorded Apr 15, 2020
From: BOOKIT OY
To: DUCK POND INVESTMENTS; GODFREY, PETER
Reel/Frame 052410/0189 →
CHANGE OF NAME Recorded Jan 12, 2019
From: BOOKIT OY AJANVARAUSPALVELU
To: BOOKIT OY
Reel/Frame 049368/0480 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 8, 2019
From: SALONEN, JUKKA
To: BOOKIT OY AJANVARAUSPALVELU
Reel/Frame 047931/0219 →
Priority Claims (1)
FI 20011680 · Aug 21, 2001 · national
Continuity (3)
Continuation 10734352 · Dec 11, 2003
Continuation 10227194 · Aug 21, 2002
Related Publication 20150227857A1 · Aug 13, 2015
Cited By (1)
US 12,294,564