IP Library Granted Patent US 10,990,908
Granted Patent B2
US 10,990,908 · App. 15/608,527 · Granted Apr 27, 2021

Booking method and system

Inventor: Jukka Kalevi Salonen (Luhtajoki, FI)
G06Q10/02G06Q10/025G06Q10/109G06Q10/1095G06Q20/322G06Q20/3221G06Q20/3255G06Q20/40G06Q20/4014G06Q30/0267G06Q30/0601G06Q30/0609G06Q30/0623G06Q50/14H04L29/12726H04L51/18H04L51/30H04L67/10H04L67/42H04M3/42382H04W4/12H04W4/14H04W4/40H04W4/50H04W12/06G08G1/207H04W12/00512H04W12/00514
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 10,990,908
App. No.
15/608,527
Granted
Apr 27, 2021
Kind
B2
Abstract

There is disclosed herein a method and system for communicating over a telecommunications network between a service provider and one or more users, wherein the service provider can have access to multiple distinct addresses in the telecommunications network and each user is identified by an address, more specifically where a first message can be sent over at least a portion of the telecommunications network to a user's address and based on a response from the user determining the message to which the response is a reply to.

Claims (52)

1. A network server that facilitates communications between a product or service provider and a user's mobile device having an identifier address, wherein the network server operates based on software instructions for performing a method that comprises:

preparing one or more inquiry messages pertaining to a service provided by the product or service provider;

sending the one or more inquiry messages to the user's mobile device;

receiving at least one reply message to the one or more inquiry messages from the user's mobile device by the network server at a specified reply address, wherein the reply address is an address at which replies to the inquiry are transmitted, and wherein the received reply message includes the identifier address of the user's mobile device;

storing information pertaining to the received reply message in relation to the identifier address of the user's mobile device and the specified reply address at which the reply message was received;

determining, for the received reply message, a corresponding inquiry message of the one or more inquiry messages; and

determining whether to authorize a transaction on an automated basis based on content of the received reply message using at least semantic analysis of the content in the received reply message,

wherein, prior to the sending the one or more inquiry messages to the user's mobile device, the method further comprises specifying the reply address for the one or more inquiry messages being sent to a particular user's mobile device, wherein the specified reply address for the one or more inquiry messages being sent to the particular user's mobile device is selected from a plurality of different addresses.

2. The network server of claim 1 , wherein the one or more inquiry messages include at least one choice selectable by the user, wherein the received reply message also includes a user selected choice, and wherein the determination whether to authorize the transaction on an automated basis based on content of the received reply message includes determining the choice selected by the user in the received reply message using at least semantic analysis of the content in the received reply message.

3. The network server of claim 1 , wherein the semantic analysis includes analysis of information included in the received reply message to determine whether the information is an acceptable answer to the one or more inquiry messages.

4. The network server of claim 1 , wherein the determination whether to authorize the transaction is based also on the reply address associated with the received reply message and the identifier address of the user's mobile device indicated in the received reply message.

5. The network server of claim 1 , wherein the network server analyzes at least one of a profile that the user has created himself or herself, usage history records, and the user's location to formulate communication messages with the user via the user's mobile device.

6. The network server of claim 5 , wherein the network server is configured to make decisions in an automated manner to support user decision making regarding which transactions the user wishes to authorize.

7. The network server of claim 6 , wherein the network server is configured to act as an agent of the user and negotiate with one or more service providers to initiate negotiation of a transaction without user involvement.

8. The network server of claim 7 , wherein the initiation of transaction negotiation is performed based on the user's preferences included or determined from at least one of a profile that the user has created himself or herself, usage history records, and the user's location to formulate communication messages with the user.

9. The network server of claim 1 , wherein the inquiry and reply messages are text messages.

10. The network server of claim 1 , wherein the inquiry and reply messages are Short Messaging Service (SMS) messages.

11. The network server of claim 1 , wherein the identifier address of the user's mobile device includes an identifier chosen from the group consisting of the user's A-subscriber's number, Calling Line Identity, e-mail address and IP address.

12. The network server of claim 11 , wherein the inquiry message is a service request that identifies the user's mobile device.

13. The network server of claim 12 , wherein the inquiry message to which the received reply message corresponds is determined in an asynchronous manner, wherein the received reply message need not correspond to a most recently sent inquiry message.

14. The network server of claim 13 , wherein the determination of which of the plurality of inquiry messages sent to the user corresponds to the received reply message is based on semantic analysis of the received reply message.

15. The network server of claim 14 , wherein the determination of which of the plurality of inquiry messages sent to the user corresponds to the received reply message is also based on an identifier address for a device sending the received reply message and the reply address at which the received reply is received.

16. The network server of claim 1 , wherein the communications between the product or service provider and the user's mobile device are based upon technology in which a reply message to an inquiry message does not automatically include an explicit reference to the inquiry message.

17. The network server of claim 1 , wherein the determination, for the received reply message, of the corresponding inquiry message includes analyzing the specified reply address at which the received reply message was received to determine which inquiry message included the specified reply address.

18. The network server of claim 17 , wherein the determination, for the received reply message, of the corresponding inquiry message also includes analyzing the address of the user's mobile device from which the received reply message was sent.

19. The network server of claim 1 , wherein the determination, for the received reply message, of the corresponding inquiry message includes analyzing the address of the user's mobile device from which the received reply message was sent.

20. A method for facilitating communications between a product or service provider and a user's mobile device having an identifier address using a network server, the method comprising:

preparing one or inquiry messages pertaining to a service provided by the product or service provider;

sending the one or more inquiry messages to the user's mobile device;

receiving at least one reply message to the one or more inquiry messages from the user's mobile device by the network server at a specified reply address, wherein the reply address is an address at which replies to the inquiry are transmitted, and wherein the received reply message includes the identifier address of the user's mobile device;

storing information pertaining to the received reply message in relation to the identifier address of the user's mobile device and the specified reply address at which the reply message was received;

determining, for the received reply message, a corresponding inquiry message of the one or more inquiry messages; and

determining whether to authorize a transaction on an automated basis based on content of the received reply message using at least semantic analysis of the content in the received reply message,

wherein, prior to the sending the one or more inquiry messages to the user's mobile device, the method further comprises specifying the reply address for the one or more inquiry messages being sent to a particular user's mobile device, wherein the specified reply address for the one or more inquiry messages being sent to the particular user's mobile device is selected from a plurality of different addresses.

21. The method of claim 20 , wherein the one or more inquiry messages includes at least one choice selectable by the user, wherein the received reply message also includes a user selected choice, and wherein the determination whether to authorize the transaction on an automated basis based on content of the received reply message includes determining the choice selected by the user in the received reply message using at least semantic analysis of the content in the received reply message.

22. The method of claim 20 , wherein the semantic analysis includes analysis of information included in the received reply to determine whether the information is an acceptable answer to the one or more inquiry messages.

23. The method of claim 20 , wherein the determination whether to authorize the transaction is based also on the reply address associated with the received reply message and an identifier address of a user's mobile device indicated in the received reply message.

24. The method of claim 20 , wherein the network server analyzes at least one of a profile that the user has created himself or herself, usage history records, and the user's location to formulate communication messages with the user via the user's mobile device.

25. The network server of claim 5 , wherein the network server is configured to make decisions in an automated manner to support user decision making regarding which transactions the user wishes to authorize.

26. The network server of claim 25 , wherein network server is configured to act as an agent of the user and negotiate with one or more service providers to initiate negotiation of a transaction without user involvement.

27. The network server of claim 26 , wherein the initiation of transaction negotiation is performed based on the user's preferences included or determined from at least one of a profile that the user has created himself or herself, usage history records, and the user's location to formulate communication messages with the user.

28. The method of claim 20 , wherein the inquiry and reply messages are text messages.

29. The method of claim 20 , wherein the inquiry and reply messages are Short Messaging Service (SMS) messages.

30. The method of claim 20 , wherein the identifier address of the user's mobile device includes an identifier chosen from the group consisting of the user's A-subscriber's number, Calling Line Identity, e-mail address and IP address.

31. The method of claim 30 , wherein the inquiry message is a service request that identifies the user's mobile device.

32. The method of claim 31 , wherein the inquiry message to which the received reply message corresponds is determined in an asynchronous manner, wherein the received reply message need not correspond to a most recently sent inquiry message.

33. The method of claim 32 , wherein the determination of which of the plurality of inquiry messages sent to the user corresponds to the received reply message is based on semantic analysis of the received reply message.

34. The method of claim 33 , wherein the determination of which of the plurality of inquiry messages sent to the user corresponds to the received reply message is also based on an identifier address for a device sending the received reply message and the reply address at which the received reply is received.

35. The method of claim 20 , wherein the communications between the product or service provider and the user's mobile device are based upon technology in which a reply message to an inquiry message does not automatically include an explicitly reference to the inquiry message.

36. The method of claim 20 , wherein the determination, for the received reply message, of the corresponding inquiry message includes analyzing the specified reply address at which the received reply message was received to determine which inquiry message included the specified reply address.

37. The method of claim 36 , wherein the determination, for the received reply message, of the corresponding inquiry message also includes analyzing the address of the user's mobile device from which the received reply message was sent.

38. The method of claim 20 , wherein the determination, for the received reply message, of the corresponding inquiry message includes analyzing the address of the user's mobile device from which the received reply message was sent.

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 May 30, 2017
From: SALONEN, JUKKA
To: BOOKIT OY AJANVARAUSPALVELU
Reel/Frame 042532/0329 →
Priority Claims (1)
FI 20011680 · Aug 21, 2001 · national
Continuity (4)
Continuation 14715005 · May 18, 2015
Continuation 10734352 · Dec 11, 2003
Continuation 10227194 · Aug 21, 2002
Related Publication 20170272949A1 · Sep 21, 2017