BOOKING METHOD AND SYSTEM

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.

Description

FIELD

Disclosed embodiments relate to telecommunications. In particular, the disclosed embodiments relate to a method and system for booking a reservation in a booking system and synchronizing bookings in several booking systems comprising at least one booking systems; involving 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. In addition, the system comprises telecommunication connections that are used to connect the booking systems, the service providers, the mediator, and the client terminal device.

BACKGROUND

Services that are booked or used via the Internet are constantly increasing. The Internet enables one to use several on-line services such as services connected to banks, health services, travel agencies, vehicle maintenance, and so on.

The increasing popularity of mobile computing and communications devices introduce new challenges to services on the Internet. Mobile terminals are able to deliver information to users when needed and where needed. Users want ubiquitous access to information and applications from the device at hand. They also want to access and update this information wherever they happen to be.

It is important to notice, however, that not all the terminals will be mobile. Future services must be able to communicate with a large variety of terminal devices, both those that are mobile and those that are not. Different terminal devices have very different capabilities.

The interoperability of different services and terminal devices requires standards on several levels. It is not enough to have, say, common communication protocols. It would be very important to share common concepts and understanding what a certain piece of data means in a certain context. However, it has been very difficult to agree on those issues, as there exist an enormous number of companies, organizations, and other actors in the field.

Many services must be able to manage bookings. They include for example booking appointments for health services; booking travel reservations for hotels, airlines, and rental cars; booking tickets for venues; booking appointments for vehicle maintenance; booking maintenance for apartments; and so on. It would be very useful, if those services could get information from one another. For example, if a customer is booking tickets for a concert, he or she might want to book a table in a restaurant also. It helps, if the restaurant's booking service gets basic information, like date and customer's name from the theater's booking system. Unfortunately, there have not been methods to exchange information between different kinds of booking systems.

There are many methods to exchange information between services. Speaking of services that include booking or calendar functions, information exchange often takes place as synchronizing booking or calendar entries. For that purpose, several important standardization efforts are going on. For example, SyncML is an industry initiative to develop and promote a single, common data synchronization protocol.

vCalendar is an exchange format for personal scheduling information. It is applicable to a wide variety of calendaring and scheduling products and is useful in exchanging information across a broad range of transport methods. A number of vendors have adopted the specification because it allows their products to exchange calendaring and scheduling information. vCalendar is an open specification based on industry standards such as the x/Open and XAPIA Calendaring and Scheduling API (CSA), the ISO 8601 international date and time standard and the related MIME email standards. The vCalendar format utilizes data normally stored within a calendaring and scheduling application, facilitating the cross platform exchange of information about items such as events and to-do's. An event is a calendaring and scheduling entity that represents a designated amount of time on a calendar. A to-do is a calendaring and scheduling entity that represents an action item or assignment. For instance, it may be an item of work assigned to an individual.

vCard automates the exchange of personal information typically found on a traditional business card. vCard is used in applications such as Internet mail, voice mail, Web browsers, telephony applications, call centers, video conferencing, PIMs (Personal Information Managers), PDAs (Personal Data Assistants), pagers, fax, office equipment, and smart cards. In addition to text, vCard information may include elements like pictures, company logos, live Web addresses, and so on.

As these examples show, there have been lots of efforts to build systems that can synchronize booking systems. A common problem with all of these existing solutions is that they do not provide common semantics for different systems. For example, if an entry is tentative, different systems may interpret it in different ways.

Another problem is that booking systems have multiple different and usually quite complex user interfaces. If a customer wants to both make an appointment with a dentist and book a taxi to take him or her there, the customer needs to enter all the booking information to both booking systems in different ways.

One more problem is that it becomes challenging to manage client replies, if a client has been given a number of questions. For example, it makes sense to use SMS text messages to ask client which option he or she chooses, because in many countries, like in Finland, it is very common to communicate with SMS text messages and they create revenues to operators. However, if a client replies to several inquires by sending a number of text messages, it can be troublesome to find out, which answer corresponds to a certain question because the reply does not automatically include a reference to the question. Say, a service asks a client if he or she wants to reserve—in addition to a flight ticket—also a taxi and a hotel room, and the client replies “yes” to one question but “no” to the other, the service does not necessarily know which offer the client has accepted.

SUMMARY

Disclosed embodiments may eliminate the drawbacks referred above or at least significantly alleviate them and enable new kind of value adding services particularly for mobile services.

Disclosed embodiments provide a method and system capable of making booking type transactions involving at least one service provider and a plurality of users who are each communicating with a mobile telephone capable of receiving and sending short text messages.

Disclosed embodiments provide a method and system capable of making booking type transactions between a plurality of service providers and a plurality of users who are each communicating with a mobile telephone capable of receiving and sending short text messages.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following section, the disclosed embodiments will be described in detail by the aid of a few examples of its embodiments, in which

FIG. 1 represents one advantageous system in accordance with the disclosed embodiments;

FIG. 2 represents a second advantageous system in accordance with the disclosed embodiments;

FIG. 3 represents a third advantageous system in accordance with the disclosed embodiments;

FIG. 4 is one advantageous example of a sequence diagram representing messages transmitted within a system in accordance with the disclosed embodiments;

FIG. 5 is a second advantageous example of a sequence diagram representing messages transmitted within a system in accordance with the disclosed embodiments.

FIG. 6 shows an example of the dynamic dialog matrix applied to a query and reply according to the disclosed embodiments.

FIG. 7 shows the phases of the booking process in a preferred embodiment of the disclosed embodiments.

FIG. 8 shows a matrix diagram corresponding to Example 2, according to a preferred embodiment of the disclosed embodiments.

DETAILED DESCRIPTION

Disclosed embodiments relate to exchanging and synchronizing information between booking systems and user terminal devices. The services may be for example booking appointments for health services; booking travel reservations for hotels, airlines, and rental cars; booking tickets for venues; booking appointments for vehicle maintenance; booking maintenance for apartments; and so on.

The booking system in accordance with the disclosed embodiments comprises at least one service provider booking system; at least one service provider; a mediator; a client; at least one client terminal device that can be a mobile device capable of receiving text messages, and that includes a dialogue; and telecommunication connections that are used to connect the service provider booking systems, the service providers, the mediator and the client terminal device to one another.

The service providers are those with whom clients want to make appointments, reservations, or other bookings and comprise the resources for the booking system to allocate. Service providers conduct business through service provider booking services. As used in this application, the mediator is a network based service available to the service provider booking services over the network that provides additional semantics, translation and synchronization services needed for communication of the information needed for a client to complete a transaction with a service provider. The service provider booking services and the mediator are preferably applications operating on network servers such as the Internet or a private Intranet. In general, a system will comprise a plurality of service providers and service provider booking systems (implementing service provider booking services), but it is possible to have a simple booking system for only one service provider in which case the mediator and service provider could be tightly integrated into a single application.

Clients preferably include clients communicating on mobile telephones capable of receiving short text messages, such as Short Message Service (SMS) messages. Of course, a system that is capable of handling SMS messages will also handle other clients with greater capabilities. The mediator preferably communicates with mobile telephone clients through an SMS gateway, such as are operated by mobile telephone providers and a well known today. The mediator communicates with clients using dialogues. Dialogues are short messages which present information to the client and allow a simple reply. Dialogues preferably provide users with simple choices such as yes/no or to allow a selection from an ordered list. Dialogues can also be one way, such as to acknowledge a reservation. A transaction may typically involve a sequence of dialogues each involving a simple response. Dialogues involve asynchronous communication by messages. The system as described makes it possible to coordinate bookings among different service provider systems in order to fill a clients need, for example coordination of an airline booking with transportation to the airport.

FIG. 1 is a diagram of the simplest system comprising a single service provider booking system 100 for a single service provider, a mediator 102 communicating with the service provider over a network, and a user with a mobile phone having a dialogue entered thereon.

FIG. 2 shows a plurality of service provider booking systems communicating with a mediator over a network.

FIG. 3 shows a mediator named BookIT communicating with various service provider systems and users with telephone devices communicating dialogues.

A reason based customer dialogue is a desirable improvement from the client's point of view, because service providers can create their own dialogues in connection with each booking event. A dialogue is closely related to a certain booking situation. It becomes active automatically at the right moment, or the client can activate the dialogue as needed, or another entity in the system can send a message to the dialogue to activate it. The dialogue then sends an inquiry to another entity in the system or informs the client and possibly inquires client's choices. By means of this kind of dialogue, the client can make reservations in several booking systems using only one user interface. The dialogue connects to remote booking systems e.g. through the Internet or even mobile networks.

A mediator service can be capable of transmitting booking information between service provider booking systems. For example, after a booking is entered into an airline booking system, a taxi booking system can offer the client a lift to the airport. In this application, a booking is an allocation of a single resource (either the airline booking or the taxi in the previous example), while a reservation is the union of the bookings for all of the resources for the same event (the airline booking plus the taxi booking in the previous example). The dialogue between the client, the mediator and the booking systems as well as stored customer profiles ensure that the client gets the reason based service he or she needs, not intrusive advertising.

A client can make reservations as well as confirm, change, and cancel them using many kinds of communication means, including but not limited to the Internet, e-mail, and mobile terminals. The client can also synchronize a calendar provided by the mediator or a service provider with a calendar in a terminal device using mediator's synchronization functions.

A service provider can remind clients to make reservations on a regular basis and thus increase customer loyalty. A mediator can help service providers to bring their booking systems together to provide more comprehensive services without extending their businesses unnecessarily. Because of internationalization, the mediator is able to support for example many languages, time zones, currencies, and data formats.

The system, including at least a dialogue, a mediator, a service provider, and a service provider booking system, can be on one of the following levels:

1. There is a predetermined set of dialogues in the system. Their content and the possible choices are set in advance. For example, if a client books a flight, a dialogue always offers certain other bookings. Client's prior actions are not taken into consideration.

2. There is an unlimited number of dynamic or “intelligent” dialogues that are based on, for instance, a profile that a client has created himself or herself, usage history records, and client's location. Simple logic supports decisions. It is a low-level expert system.

3. The system is able to make decisions by itself and to support client's decision making. On this level, a dialogue may include a high-level expert system. It can act as an agent and negotiate with several service providers to get the best offer without client's direct involvement.

In one preferred embodiment of the method, a client books a service from a service provider. The booking may be carried out using a terminal that is connected to the mediator service. First, the client connects to the mediator service using a dialogue. The client inputs reservation inquiry to the dialogue that sends the inquiry to the mediator. The mediator inquires possible reservations from service provider's information system using concepts and terminology that those services are able to interpret. The inquiry is based on client's preferences. The client discloses some preferences that are related to the specific booking when he or she inputs reservation inquiry to the dialogue. In addition, the dialogue and the mediator service may have stored client's general preferences and use them so that the client do not need to input all the preferences each time.

Managing the inquiry and bookings is based on sophisticated state models. Each booking involves several phases that are described by states that track its status through its life cycle. For example, when the mediator has inquired about a reservation from a service provider, the corresponding entry in each system has a state that the booking is pending but not confirmed. If the systems do not have common understanding what a certain state means, the mediator translates them. A preferred booking process including the phases and states is described in Example 1.

In addition to inquiring reservations from the service provider, the mediator is able to synchronize bookings in several service providers' systems. The synchronization is based on rules specified in the mediator service. For example, a rule can be that “if a client inquires booking for an airline ticket, inquire also bookings for taxis to the airport.” Therefore, an inquiry from the client may be multiplied in the mediator service resulting a number of inquiries. The service providers answer to the mediator if they are able to provide requested service and they may add some additional information, like on seats or timing. The mediator combines gathered information and sends it to the dialogue that shows a simple list of options to the client. For example, the dialogue may show three options for a flight and ask if the client also wants to reserve a taxi that is actually already tentatively booked by the mediator. The client makes his or her decision by choosing the options from the simple list of alternatives. The dialogue sends information on client's choice to the mediator that confirms the bookings in accordance with client's choices and cancels the unnecessary reservations.

FIG. 4 shows a sequence diagram of an inquiry CINQ1 originated by a client using a dialogue DINQ1 sent to the mediator. The mediator initiates the inquiry MINQ1 which corresponds to CINQ1 and DINQ1 to booking system 1 a service provider booking system. Ultimately an answer DANS1 gets back to the client offering a choice which is responded to with a selection CSEL1 resulting in a booking by the client on booking system 1. The mediator recognizes the potential need for a complementary service from booking service 2 and initiates an inquiry, MINQ2, to booking system 2, which ultimately results in a proposal including several choices, DANS2, returned to the client from which a selection, CSEL2, is made, resulting in a complementary booking on booking system 2.

The bookings can be done in other means as well, for instance, by calling the service provider with a telephone or by visiting on site the service provider's office. In that case the service provider may inform the mediator about client's bookings so that the mediator can inform the client on other options. For example, a dentist could tell the mediator that the client has booked an appointment so that the mediator may offer to book a taxi also.

Also, it is possible to add a reminder to the mediator service so that the mediator asks at certain time if the client wants to make a new booking. For instance, the mediator can send a notice to the client that it has been a year since the client last had an appointment with his or her dentist and ask if the client wants to make a new appointment. This notice can already include a few options for the appointment. The mediator has checked the client's calendar if he or she has allowed that so that the given options are convenient for the client. The dialogue shows the options in a simple and handy way. The client needs only to choose which option is the best for him or her or whether he or she wants to get new options or postpone the booking. FIG. 5 is a time sequence chart for such a situation where the original inquiry, MINQ1, was initiated by the mediator.

Example 1

A Preferred Booking System

A preferred booking system according to the disclosed embodiments, is described below in terms of a system named BookIt.

BookIT is designed to interface between service provider booking systems and other parties over a network such as the Internet, and to end user clients equipped with mobile phones capable of receiving text messages. The former is preferably accomplished with a generic XML interface. BookIT supports vCard and vCalendar standards since they are used by all major booking and calendar systems.

BookIT communicates with mobile phone users using Short Message Service (SMS) via an SMS Gateway for asynchronous communication. BookIT uses the novel Dynamic Dialogue Matrix (DDM) for secure transfer and mapping of the SMS messages. The DDM is described further below.

A clear distinction needs to be made between a service provider booking process and BookIT Process. The former covers the standard booking only with time and resource reservation. The latter consists of booking, work, and financing. Both processes end to the same point. The BookIT Process consists of seven phases as follows:

Phases (Status Handling)

The phases make a bond (rubber band) between the resources. In each of the BookIT Process' phases the data related to the booking will be amended to reflect the needs of the phase in question. For the statuses and values please see the underneath table.

The phases are described in more detail in the following discussion.

1. Filing

Filing means initialization of a BookIT Process and a booking process. As a result of the initialization an entry is inserted in the database w/basic information. It will not appear in a calendar since there is no scheduling information. It can be displayed in a separate task list of the owner as an open task.

2. Requesting

In the Requesting phase a booking request is sent to the resources required for the previously filed task. Since there is no scheduling, which in most cases will be essential, this phase may be executed together with the Scheduling phase.

3. Scheduling

Schedule is given to the owner and the resources. As a part and a result of the Scheduling the following data is needed:

a suggested start-time (ISO time-stamp w/time zone)

b suggested start-location (coordinates)

c suggested end-time (ISO time-stamp w/time zone)

d suggested end-location (coordinates)

4. Confirming

Time and location as it is accepted by the resources that have accepted. Data related to this phase:

a accepted start-time (ISO time-stamp w/time zone)

b accepted start-location (coordinates)

c accepted end-time (ISO time-stamp w/time zone)

d accepted end-location (coordinates)

By default the data is copied from the Planning phase.

In practice, if planned time is not needed, the same data structures can be used for this and status indicates the actual meaning of the data.

5. Working

The resources perform the booked task. Data related to this phase consists of different attributes and their values, which are related to the actual task. In addition, following static structures are needed:

a actual start-time (ISO time-stamp w/time zone)

b actual start-location (coordinates)

c actual end-time (ISO time-stamp w/time zone)

d actual end-location (coordinates)

e products used, extras, mileage,

By default the data is copied from the Confirming phase.

6. Accounting

At this point all data stored in the data structures on previous phases is analyzed and processed for invoicing purposes.

Data related to this phase: Accounting data. To be defined separately.

7. Completing

The task has been completed. From the whole

BookIT process point of view it is irrelevant whether the task succeeded or not. It is relevant to the Accounting phase, in which the financial actions to the organizer are handled. In this phase, housekeeping (database contents; temporary files, . . . ) is made in order to complete the BookIT Process.

The following table shows data available in each phase. Booking phase is in italics.

Filing	X					X
Requesting	X	X				X
Scheduling	X	X	X			X
Confirming	X	X	X	X		X
Working	X	X	X	X	X	X
Accounting	X	X	X	X	X	X
Completing	X	X	X	X	X	X	X
Phase/Data	Identifying	Resources	Suggested	Accepted	Task's	Accounting	Closing
			time	time	work
					related

Phase Statuses, Values, and Transitions

The following table describes the phases, their statuses, and values along with transition to next logical phase based on the values gotten. In addition, corresponding vCalendar statuses are shown when applicable.

Phase	Satus	Next Phase	vEvent	vTodo
Filing		Requesting
Requesting		Scheduling	Sent	Sent
Scheduling	Pending	Confirming	Needs	Needs
			Action	Action
Scheduling	Scheduled	Confirming	Needs	Needs
			Action	Action
Scheduling	Re-	Confirming	Needs	Needs
	scheduled		Action	Action
Confirming	Accepted	Working	Confirmed	Accepted
Confirming	Declined	Accounting	Declined	Declined
Confirming	Tentative	Accounting	Tentative
Confirming	Delegated	Requesting	Delegated	Delegated
Confirming	Re-	Accounting or
	Scheduling	Scheduling
	requested
Confirming	InProgress	Working
Working	InProgress	Working
Working	Delayed	Working
Working	Started	Working
Working	n % ready	Working
Working	Ready	Accounting
Accounting		Completing
Completing	<Copied	n/a
	from phase
	before
	Accounting>

Internal phases Paused, Re-started, and Canceled act as follows for all relevant phases at any point:

	<Phase y>	Paused	<Status x>
	<Phase y>	Re-started	<Status x>
	<Phase y>	Cancelled	Accounting

FIG. 6 shows the work flow transitions from phase to phase. For conditions, see the table above. Also, please note that Canceled Status always leads to Accounting.

Confirming the (Whole) Reservation

In order for the whole Reservation to be successful, all resources, which accepted the reservation, need to have the same scheduling. In addition, there will resources in different roles and data related to the working phase may vary even greatly.

The different statuses of the whole reservation are:

a “NoReplies” (0) for “No-one hasn't replied to the request made by the organizer”

b “NoDeclines” (1) for “Not all invitees have replied yet. The ones who have replied have accepted”

c “AllAccepts” (2) for “all invitees have confirmed”

d “SomeDeclines” (3) for “Some of the invitees have declined”

e “AliDeclines” (4) for “All of the invitees have declined”.

The following decision table helps in evaluating the status of the whole booking. “Maybe” means that this condition only does not incontestably specify true or false result.

Booking Status\	No one	No one	Some	All	No one	Some	All
Confirmations	answered	accepted	Accepted	accepted	declined	declined	declined
NoReplies	True	Maybe			Maybe
NoDeclines	True	Maybe	Maybe	True	True
NoAccepts	True	True			Maybe	Maybe	True
AllAccepts			True	True	Maybe
SomeAccepts			True	Maybe	Maybe	Maybe
AllDeclines		Maybe					True
SomeDeclines		Maybe	Maybe			True	Maybe

Based on the information and decision table above the organizer/application has to make the decision of what to do with the reservation. That can be an automatic decision made by the system based on pre-set rules or made by the organizer manually.

One major problem solved by the disclosed embodiments is the challenge of managing client replies, when a client has been given a number of questions and the client is using SMS text messages or similar technology in which a reply does not automatically include an explicit reference to the inquiry. The disclosed embodiments solve this problem using dynamic dialog matrices. An inquiry always includes some kind of receiver's address or identification. In the SMS text message case that is so called B subscriber's number. On the other hand, sender's A subscriber's number or Calling Line Identity (CLI), or similar identification is also attached to each text message. Therefore the client or B subscriber is usually easily able to answer a message using mobile device's answer or reply function. If a mediator service that sends inquiries to a client, uses different A subscriber numbers in different inquires, it is possible to differentiate between answers based on which number the client is sending replies to. For example, if a mediator sends a client an inquiry “Do you need a taxi also?” using A subscriber number A1 and then inquiries “Do you need a hotel room?” from A subscriber number A2, client's reply to the first question goes to number A1 and the second answer goes to number A2. Using a dialog matrix, a mediator keeps track on inquires and answers. In the matrix, there is a column for each client and a row for each A subscriber number the mediator is using. Obviously, there could be a row for each client and correspondingly a column for each A subscriber number as well. After sending an inquiry from a certain A subscriber number to a client, the status and the reply is stored in the corresponding shell of the matrix. As a result, the mediator is able to find out whether the client has replied to a certain inquiry and what the answer was. Also, it is possible to use the matrix to collect information about clients' behavior and use it for example for marketing purposes. A mediator needs only a limited number of A subscriber numbers. A dialog matrix can also be used to find out which A subscriber numbers can be used when the next inquiry to a certain client is sent.

The use of the Dynamic Dialog Matrix as described above is illustrated in FIG. 7.

The Dynamic Dialog Matrix is also a powerful but very simple security measure for authenticating a mobile phone user who has only the capability of sending and receiving messages. The problem is for a service to confirm a sender's identity. One way to try to identify the user is to check the sender's address. Normally SMS, e-mail, and other alike messages have the sender's address attached. That address can be for example the sender's A-subscriber's number or Calling Line Identity (CLI), or e-mail address or IP address. However, it is quite easy to falsify a sender address. From the service provider's perspective, the downlink from a service provider to a user is usually relatively reliable and it is hard for others to capture or change messages, but the uplink from a user to a service provider is much more vulnerable and it is not too difficult to give a wrong sender's address. A well-known solution to the above problem is to use encryption technologies to secure the communications, public-key infrastructures (PKI) being good examples. For instance, a user device can be equipped with a microchip, a secure SIM card in GSM devices for example, to encrypt messages using the user's private key. Then the service provider can be sure that the message is from the user, if it can be decrypted using the user's public key. However, this solution requires special devices that are not very common, inexpensive, or standardized so far. Relying on such a solution restricts the number of potential users significantly.

Using the DDM provides a novel solution. When the service sends a request to the mobile phone user, each request contains a different, preferably randomly chosen, reply number. Thus an acceptable answer is only the one that is sent to the correct reply address.

Example 2

Use of the Dynamic Dialogue Matrix

This simple example deals with securing tickets on a morning flight tomorrow. The system sends a series of questions as SMS messages requiring a short response. Each message is earmarked so that its response can be identified so the messages need not necessarily be sent or replied to in a particular sequence unless logic so demands (for instance, if the answer to one question affects the content of the next question).

A user whose phone number is ID=0418 979 813 has requested the ticket. The system sends the following requests as individual SMS messages:

Please choose one of the following departure times:

6:00 a.m., answer A

7:30 a.m., answer B

8:15 a.m., answer C.

If none of these is OK, answer D.

Sender: +358440844027

Please choose ticket class:

First class, answer A

Business class, answer B

Economy class, answer C

Cheapest available, answer D

Sender: +358440844011

Please choose:

Window seat, answer A

Aisle seat, answer C

Sender: +358440844034

Please select the meal:

Vegetarian, answer A

Beef, answer B

Chicken, answer C

Sender: +358440844003

The answers received from the customer to the preceding questions and several others were as follows:

‘A’ to question with ref. no +358440844027

‘D’ to question with ref. no +358440844011

‘A’ to question with ref. no +358440844034

‘B’ to question with ref. no +358440844003

] ‘D’ to question with ref. no +358440859751

‘A’ to question with ref. no +358440844277

‘C’ to question with ref. no +358440841368

From this, the service provider can find out that the customer chose:

the first morning flight (=A),

cheapest available ticket (=D),

window seat (=A),

beef for meal (=B), and etc.

It is important to note with the matrix the customer can answer the questions in any order, and can even fail to answer some questions. If these are relevant, the system can urge for an answer. If not, the system can proceed without this information.

The above responses are shown on FIG. 8 as a three dimensional matrix with customer numbers plotted on the X-axis, reply numbers are plotted on the Y-axis and answers plotted on the Z-axis. Our user with phone number 0418979813 is the left most user along the X-axis. The answers are plotted along the Z-axis corresponding to the reply numbers on the Y-axis.

Additional security can be achieved using semantic analysis. In the matrix shells, there can be information about the inquiry and what kinds of answers are acceptable. If an answer does not meet the criteria, it is rejected. For example, if the service provider asks the user to tell how many items are ordered, and the user answers “yes”, then apparently the user did not know what the question was and the message was not an answer for the inquiry.

It is also possible that the service provider is actually a mediator and the “real” service provider is somewhere else. In that case, only the mediator needs to have the matrix-based system and the actual service provider communicates with the mediator using either the mediator's matrix-system or other secure means like a crypto-channel. For example, a car sharing system could be implemented in the following way: cars are located randomly around a city. When a user needs a car, he or she sends a message to a mediator to ask where the nearest car is. The mediator sends a message telling the car's location. That reply comes from a random address y′. When the user reaches the car, he or she sends a message to y′ telling that the rental period begins and asking the mediator to remotely release the car's locks. This message is relatively reliable, because it is sent to the address that the user only knows. Therefore it constitutes a valid reason to release the locks and start billing. The communication between mediator and the car, on the other hand, is invisible to the user and outsiders. The car can be equipped with special devices and therefore remote commands to release the locks etc. can be encrypted. Or, the communication between the car and the mediator could also be implemented using matrices. In either case, the mediator operates as a “firewall” between the user and the car disabling outsiders from unauthorized usage.

Although the present invention has been described in considerable detail with reference to certain preferred versions thereof, other versions are possible. Therefore the spirit and scope of the appended claims should not be limited to the preferred versions herein.

Claims

1. A network server that facilitates communications between a product or service provider and a mobile device associated with a user and having an identifier address, the network server: preparing one or more inquiry messages pertaining to a service provided by the 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 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 a received reply message, a corresponding inquiry message of the one or more inquiry messages; anddetermining 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.

2. The network server of claim 1, 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.

3. The network server of claim 1, 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.

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 and the identifier address of the user 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 a user has created himself or herself, usage history records, and a 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 a user wishes to authorize.

7. The network server of claim 6, 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.

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

9. The network server of claim 1, wherein the communication messages are text messages.

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

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

12. The network server of claim 1, wherein the inquiry is a service request that identifies the user terminal device.

13. The network server of claim 12, wherein the inquiry to which a received reply message corresponds is determined in an asynchronous manner, wherein a 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 the user identifier address for a device sending with 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 service provider and the user terminal device are based upon technology in which a reply to an inquiry does not automatically include an explicit reference to the inquiry.

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 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 mobile device identifier address 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 mobile device identifier address from which the received reply message was sent.

20. The network server of claim 1, further comprising, prior to the sending the one or more inquiry messages to the user's mobile device, specifying the reply address for the one or more inquiry messages, the specified reply address being selected from a plurality of different addresses.

21. A method for facilitating communications between a product or service provider and a mobile device associated with a user and having an identifier address using a network server, the method comprising: preparing one or more inquiry messages pertaining to a service provided by the 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 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 a received reply message, a corresponding inquiry message of the one or more inquiry messages; anddetermining 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.

22. The method of claim 21, 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.

23. The method of claim 21, 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.

24. The method of claim 21, wherein the determination whether to authorize the transaction is based also on the reply address associated with the received reply and the identifier address of the user mobile device indicated in the received reply message.

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

26. 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 a user wishes to authorize.

27. The network server of claim 26, 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.

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

29. The method of claim 21, wherein the communication messages are text messages.

30. The method of claim 21, wherein the communication messages are Short Messaging Service (SMS) messages.

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

32. The method of claim 21, wherein the inquiry is a service request that identifies the user terminal device.

33. The method of claim 32, wherein the inquiry to which a received reply message corresponds is determined in an asynchronous manner, wherein a received reply message need not correspond to a most recently sent inquiry 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 based on semantic analysis of the received reply message.

35. The method of claim 34, 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 the user identifier address for a device sending with the received reply message and the reply address at which the received reply is received.

36. The method of claim 21, wherein the communications between the service provider and the user terminal device are based upon technology in which a reply to an inquiry does not automatically include an explicit reference to the inquiry.

37. The method of claim 21, 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 to determine which inquiry message included the specified reply address.

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

39. The method of claim 21, wherein the determination, for the received reply message, of the corresponding inquiry message includes analyzing the mobile device identifier address from which the received reply message was sent.

40. The method of claim 21, further comprising, prior to the sending the one or more inquiry messages to the user's mobile device, specifying the reply address for the one or more inquiry messages, the specified reply address being selected from a plurality of different addresses.