FI20030359A - Method and arrangement for developing traffic on work trips - Google Patents

Description

Method and system for improving commuting traffic Method and system for organizing commuter traffic

The present invention relates to a method and system for improving commuting traffic and particularly for improving easiness and safety of ride sharing when using a mobile communication system.

Background of the invention

Traffic congestion costs as Wasted time and in Wasted gasoline $ 100 billion per year in USA alone. Carpooling is one of the possibilities to ease the flow of traffic. Currently, carpooling systems are more or less based on agreements between participants well ahead of the trip. A lot has been done in the metropolitan areas of the United States to attract users for carpooling, but carpooling has not reached widespread acceptance among commuters and its popularity has actually increased in recent years.

According to the Bureau of Transportation Statistics, 87.7% of 118 million workers in the US use a private car as their principal means of transportation to work (78.2% only driver in a car, 9.4% at least one passenger in a car). The percentage of carpoolers has decreased from 14.1% in year 1985 to 9.4% in year 1999.

According to a survey of San Francisco Bay Area Commute Patterns in 2001, 17% of commuters in the area are using carpools now, roughly 10% use public transportation, and 69% use a single occupancy vehicle (SOV). The most common reasons for using SOV mode for commuting are "no other way to get to work" (18% of SOV users), "work hours / work schedule" 16%, "travel time to work" 12%, while " privacy not being dependent on others, Come and go as I please, like to drive "consisted of only 9% of SOV users as main reason for commute mode choice. The average time saved using a carpool is 23 minutes (per direction). From all carpoolers 80% indicated that carpooling is saving time. The average travel distance and time for a commute are 17 miles and 34 minutes. The average travel distance for carpool users is 22 miles.

In U.S. Patent 4,360,875, a flexible-route transportation system, particularly utilizing privately-owned vehicles to provide ridesharing transportation for the public, is described. Interactive communications terminals are provided through which drivers of vehicles can rapidly transmit via a telecommunications network to a central operations coordinating station equipped with a general purpose programmable computer. Rider interactive communications terminals, located at public and private facilities, are also connected to a telecommunications network with a central coordinating station, permitting eligible members of the public to quickly request rides from one location to another. The central coordinating station matches the ride requests with the ride offers, on a trip-by-trip basis, comparing the driver's indicated origin, destination, seating requirements and time with the rider's requested origin, destination, seat availability and time. If .a ride offer and ride request can be matched within reasonable limits of space and time, the central coordinating station transmits to the driver the rider's identity and location and transmits to the rider the description and the identity of the vehicle, so that the driver can pick up and drop off the rider en route to his or her destination. The system includes security features for preventing unauthorized access to the system by either drivers or riders, accounting features for properly billing riders and reimbursing vehicle owners for transportation services, and special terminals for entering trip information quickly and accurately.

Somewhat similar systems have been described in U.S. Patent Application Publication No: 2001/0037174 (Filed Apr 4, 2001) that generally supports an automated transit system that minimizes the social costs of urban transportation, the transit system being based on digital cellular communication, GPS locating technology and digital computers to provide real-time command and control of passengers and vehicles.

In casual / real-time creation of carpools the participants are sharing a car with stranger. This creates a possible security risk for the carpool participants.

Summary of the invention

The present invention describes how a casual carpool can be set up and how the security of the participants can be increased without any Complicated actions from the users. The Invented Method Relies on the Use of Mobile Communications Devices in the Setting Up of the Carpool and Solves Two Important Issues: How the Mobile Devices Carried Can Be Used device. Equally important for the system is that it introduces a minimum amount of work for the carpool participants.

In the present invention, it is described in details how the matching of the needs is done in real-time using mobile communications as well as the ease of use (needed for messaging to set up the ride-sharing) is improved and the setting up the carpool is integrated with the features of increasing the safety of carpoolers.

According to the first aspect of the invention, the method is provided for arranging transportation for at least two persons by one of the said persons. Each of the said persons has a communication device capable of communication with a server connected to a communication network. The communication devices can send and receive messages to and from the server. The method comprises at the server: - receiving registration information from a person, with registration information at least one route to be transported, identification identifying the person and registration at least one of the following category : driver of a vehicle and passenger of a vehicle; - receiving a message from at least one registered driver, - receiving a message from at least one registered passenger, - receiving a message from at least one registered passenger, - matching one registered driver and at least one registered passenger substantially similar route, - sending a message to the registered driver, including at least one registered passenger, - sending a message to the registered passenger, including at least one registered passenger.

The method is characterized by: - receiving a start message indicating a successful start from the transport of the driver, and - receiving a termination message indicating a successful end from the transport of the driver at least one registered passenger.

According to the second aspect of the invention, an electronic device is provided for arranging transportation for at least two persons by one of the said persons. The electronic device is essentially the server for implementing the method described above, so it is characteristic for the electronic device according to the invention, it comprises means for executing the steps of the method.

According to a third aspect of the invention, the system is provided for arranging transportation for at least two persons by the same vehicle driven by one of said persons. The system is built essentially around the server for implementing the method described above, so it is characteristic for the system according to the invention that it comprises means for executing the steps of the method.

According to a fourth aspect of the invention, a computer program product is provided for an electronic device for arranging transportation for at least two persons by one of the said persons. The computer program product is essentially a computer program to be stored into a program memory of a server according to the invention, so the characteristic features of the computer program product comprise means for causing the server to execute the steps of the method.

In the following, the invention will be described in greater detail with reference to the accompanying drawings, in which

Figure 1 illustrates a system according to an embodiment of the invention;

Figure 1b illustrates a system according to another embodiment of the invention;

Figure 2 illustrates a flow chart of registration to the system according to the invention;

Figure 3a illustrates a flow chart of a method according to an embodiment of the invention;

Figure 3b illustrates a flow chart of a method according to another embodiment of the invention;

Figure 4a illustrates a signaling diagram of a method according to an embodiment of the invention;

Figure 4b illustrates a signaling diagram of a method according to another embodiment of the invention;

Figure 5 illustrates a block diagram of a device according to an embodiment of the invention.

Detailed description of the invention

Figure 1a illustrates a system according to an embodiment of the invention. In the following text message (Short Message Service) is used as an example of data transfer means. However, other techniques such as multimedia messaging (MMS), WAP (Wireless Application Protocol) or more advanced mobile Internet approaches can be used. Similarly, the Mobile Station (MS) is used as an example of a mobile communications device.

The system comprises a centralized server 101 (a Carpool server) that is capable of communication with other network elements, for example to mobile communication devices 102 and 103. In this exemplary illustration, the communication devices 102 and 103 are operating in a GSM network. However, the communication device disclosed can also be other than one operating in a GSM network. Other communication devices operating in different networks can be used as well when implementing the present invention. In the example set-up in figure 1a, the server 101 is connected to the Short Message Service Center 104 (SMSC) allowing it to exchange short messages between it and MSs 102 and 103. Connecting to the Internet 106 allows service profiles to be generated by users of MSs 102 and 103.

The operation of the system of figure 1a will be ..disclosed later in detail with. reference to figures 2 and 3a.

Figure 1b illustrates a system according to an alternative embodiment of the invention. The system consists of a centralized server 101 (a Carpool server) that is capable of communication with other network elements, for example to MSs 102 and 103. In the example set-up in figure 1b, the server 101 is connected to a Short Message Service Center 104 (SMSC) allowing it to exchange short messages between it and MSs 102 and 103. Connection to the Internet 106 allows service profiles to be generated by users of MSs 102 and 103.

The system can further comprise e.g. the Gateway Mobile Location Center 105 (GMLC) that can provide location information on Mobile Stations 102 and 103 to the Carpool server 101 it is connected to. In a case of detected emergency connections to Public Safety Answering Points 107 (PSAP), such as the police, etc. are provided. GMLC is used as a generic name for a network element or feature in a passenger's or driver's MS capable for providing a location estimate of the site Ms to a server connected to a communications network.

The capabilities to calculate the location of mobile communication devices (MS) are opening the possibility to collect a large amount of data about the movements of individuals. Most likely the majority of people would find the location tracking of their MS as a violation of their privacy and therefore they are likely to disable the o tracking of their phones if possible. For persons using Intelligent ride-sharing systems the tracking of the person's MS location can be used to increase the security of the tracked person and it is very likely that the persons using these systems will not be allowed but will insist that the location of their MS is traced when they are using an Intelligent ride-sharing system. Location information can be used to enhance the easiness of the service. For example, the passenger can be located so that the starting point of the route is not needed to be indicated, or the arrival time of the driver can be estimated, etc.

By utilizing mobile phones and the ability to locate them, it is possible to create a system that enables fully dynamic, on-demand creation of carpool. In an instant / dynamic carpool one would not have to make any commitment well before the proposed trip, instead the user can indicate the system his / her willingness to participate immediately or a short time before the trip should take place.

The proposed system of Figure 1b utilizes Capability to locate a mobile communications device (from this referred to as MS). According to the proposed system, users of MS locations can be traced from the user indicated starting point to a user indicated stop point. The safety of a carpooler is increased as both partners are aware that their location can be continuously traced and an alarm can be triggered if they are diverting from the route to their destination more than is allowed or if either one's MS will be switched off.

The operation of the system of figure 1b will be revealed later in detail with reference to figures 2 and 3b.

Figure 2a illustrates a flow diagram of the registration to the system according to the invention. A reference has been made to the system disclosed in figures 1a and 1b. The steps of the method can be implemented as a computer program code stored in the memory of an electronic device 101 which can be e.g. a server in a communication network.

The system has two types of users: passengers and drivers. The driver is providing a lift for a trip to a passenger. Reference numeral 102 in figures 1 and 2 is referring to a passenger and reference numeral 103 is referring to a driver. Both driver 103 and passenger 102 have to register to the system in order to be able to use it. The task of the system is to dynamically in a real-time match the needs of the passengers to the offerings of the drivers. A single person can register to both a driver and a passenger.

Drivers and passengers register to the system using their mobile identity e.g. a mobile Subscriber identifier. The registration can be done e.g. via the Internet by using a desktop or laptop computer that is connected to the Internet. A connection to the server 101 is established e.g. by using either mobile or fixed line Internet access (step 201). Before registration is completed both passenger and driver have to fill in the profile questionnaire. The user profiles should contain at least the identity, gender and age of the user as well as at least one approximate route for which the user would need or offer a carpool. The last-mentioned means are typically giving a starting point and an end point, or identifying a starting point and an end area from the list of default areas. For the driver also his / her car type, model, color, license plate number, available number of seats and model year have to be entered. The driver has to also report the status of his / her driving license and possible points in the insurance. Depending on local legislation also permission to do certain checks on criminal record or traffic violations might be asked. The system generates an account for the user who subscribes to the system. The meaning of the account is to credit or debit the user depending on whether he / she is registered as a driver or a passenger. Alternatively, the user can give his / her bank account number for this purpose. Optionally credit cards or accounts in known person to person, business to business or business to person payment systems such as paypal can be used.

If the system and method revealed in figures 1 b and 3b is in question, the driver and the passenger'have also to sign a waiver in order to authorize the system to track his / her mobile phone while he / she is an active participant or is actively querying for participation in carpool in a carpool.

To validate the registration (step 203) the user has to send a message to the system using the mobile communications device. This message can be sent to the system before registration in order to gain access to the registration system (in this case he / she receives the password to the system as return message). Other possibility is that the user selects the password in the registration and sends that password using the mobile communications device to the system. In both cases, the system gets a confirmation that the user is registered to the system has the mobile communications device he / she registered in his / her possession (step 204).

In addition to the initial confirmation of the identity of the user, the system needs to be able to confirm the identity of the person each time he / she uses the system later on. This confirmation can be done for example using one or several of the following: a picture (of person ordering), a Fingerprint (of person ordering), any digital identity (digital identity card etc.), code sentences (question and answer pair) , a pass code, a personal identity code (actually a special case question and answer pair, not connected to a passenger code on a passenger device). In setting-up the carpool these are used to confirm the identities of the persons.

At step 205, the system provides a pass code to the user (optionally, the system can ask the user to form a pass code), which was needed to confirm the identity of the user when the transportation begins. The pass code is not sent to a communication device by which the user makes a transportation request and / or offer. That is because if the communication device is Stolen, it cannot be used for making successful transportations for a person who stole the device. At step 206 the registration has ended and the communication connection is terminated.

In the following an example of a confirmation of an identity of a user is illustrated. The system provides a pass code "asdf to a passenger when he / she has registered to the system. Further the system also sends a pass code" zxcv "to the driver when he / she has registered to the system. Pass codes can also be allocated dynamically per transaction, ie code "zxcv" is sent to the driver when he / she offers to share a ride. Likewise the passenger is given the code "asdf when he / she is requesting a ride. The passenger and driver may be required to renew his / her pass codes either periodically or upon usage. Now, if the driver and the passenger are matched by the system (ie they have similar starting point and ending point), the pass code ("zxcv") of the driver is sent to the passenger (for example to a communication device of the passenger) and the pass code ("asdf) of the passenger is sent for example to the communication device of the driver. When the passenger and the driver meets, the passenger utters the pass code" asdf to the driver. If the pass code the driver has received is identical with the uttered code of the passenger, the driver can be sure that the passenger is the right person. Also the driver utters the pass code "zxcv" to the passenger and if the pass code the passenger has received is identical with the uttered code of the driver, the passenger can be sure that the driver is the right person.

Figure 3a illustrates a flow chart of a method according to an embodiment of the invention. The steps of the method can be implemented for an example in a computer program code stored in a memory of an electronic device such as a server 101 in figures 1a and 1b. In real time operation the following identifies the actions needed for the driver and for the passenger to set up a carpbol. At step 310 the system receives a message from the driver 102 or the passenger 103.

If the message is from the driver indicating offering (step 311), the flow proceeds to step 313, the information received is stored in the memory of the server 101. This message includes information which the system uses to identify the route the driver is driving.

If the message received at step 311 is from a passenger (step 312) indicating the need for a ride, the flow proceeds to step 314, the message received is stored in the memory of the server 101. This message includes information which the system uses to identify the route for which a passenger is requesting a ride.

At step 315 the server 101 finds matches from drivers and passengers with substantially similar route and time information and ask confirmation from the driver (step 316). The system messages to the driver include the pick-up address of the passenger and either: a picture (of a passenger), a Fingerprint (of a passenger), any digital identity (needed information about the passenger's digital identity), code sentences (question and answer pair of passenger has registered), the previously mentioned pass code, personal identity code (of the passenger). Using the above information the driver can confirm the Personality of the passenger as he / she is inside the passenger. In the simplest method requiring least technology, the driver is delivered with the passenger's personal identity code.

Next the flow proceeds to step 325, a message from the driver is received. The message appears (e.g. "accepted" or "not accepted") whether he / she accepts the passenger or not. If the driver accepts the passenger, the flow proceeds to step 317. If the driver does not accept the passenger, the flow proceeds to step 324, the process ends. Alternatively, the flow can continue to step 315, a new match being searched for the passenger. Step 325 is optional, as well it can always be assumed that the driver accepts the passenger if he / she does not answer the message.

Next (at step 317) the server 101 sends a message to the passenger in order to inform the passenger about the ride. The system sends messages to the passenger including identification information about the driver's car and either: a picture of the driver, a Fingerprint (of the driver), any digital identity (needed information about the driver's digital identity), code sentences (question and answer pair) driver has registered), the previously mentioned pass code, personal identity code (of the driver). Using the above information the passenger can confirm the Personality of the driver as he / she inside the driver. In the simplest method requiring least technology, the passenger is delivered the driver's personal identity code.

In the meeting place driver and passenger confirm identify each other based on Descriptions sent. If pictures are sent they compare what they see. If personal identity codes are used driver ask from passenger to passenger identity code and Compares to answer from passenger to one he / she received from system (and vice versa). This procedure is used to confirm the identity of the participants and the Therefore a person can not use a stolen mobile device (mobile identity) in the system.

Passenger then sends a message to the server 101 informing the system that he / she has been picked-up by the driver (step 318). This message's meaning is to indicate that the passenger and the driver have met and that they have agreed to share a ride. At step 319, the passenger's account is debited with a predetermined amount of e.g. money or credits. At step 320 it is checked whether the message from the passenger is received or not within a predetermined time. If the end message from the passenger is received at step 320, the system knows that the transportation was successful and the flow proceeds to step 321 once the driver's account is credited with a predetermined amount of money or credits. From step 321 the flow proceeds to step 324 thus the process ends. If the end message from the passenger was not received at step 320, the system knows that the transportation was not successful and the flow proceeds to step 322 hence an inquiry is sent to the passenger. At step 323 a response to the inquiry from the passenger is waited. If one is received, the flow proceeds to step 321 as if the response was the usual end message. If the end response is still not received, the system assumes that something went wrong and skips step 321 before ending. This course of action follows a "minimal security" Assumption; not receiving an appropriate end message could also be interpreted as an alarming condition, which is described in more detail later in the association of figure 3b.

As is seen from above the driver in carpool has to send maximum of two simple messages, passenger three. It should be emphasized that the end users are using the service multiple times a week so remembering the message structure is not difficult. In addition, personalized credit card sized instructions for users can be made. The mobile device can also support the process, e.g. in the form of a JAVA application or similar acting as a user interface.

Figure 3b illustrates a flow chart of a method according to another embodiment of the invention. The steps of the method can be implemented for an example in a computer program code stored in a memory of an electronic device such as a server 101 in figures 1a and 1b.

At step 330, the server of the system receives a message from the driver 102 or a passenger 103. If the message is a message from the driver indicating the offer (step 331), the flow proceeds to step 333, receiving the information received in the message is stored in the memory of the server 101. This message includes information which the system uses to identify the route the driver is driving.

If the message received at step 331 is a request message from the passenger (step 332) indicating the need for a ride, the flow proceeds to step 334, the information received is stored in the memory of the server 101. This message includes information , which system uses to identify the route for which the passenger is requesting a ride. The request message and the offering message authorize the system to locate the passenger and the driver's mobile phone for a time period that could be equal to the estimated drive time to work + N minutes, where N is the sum of the maximum wait time , maximum drive time increase and Tolerance time.

At step 335 the server 101 finds matches from drivers and passengers with substantially similar route and time information and ask confirmation from the driver (step 336). The system messages to the driver include the pick-up address of the passenger and either: a picture (of a passenger), a Fingerprint (of a passenger), any digital identity (needed information about the passenger's digital identity), code sentences (question and answer pair of passenger has registered), the previously mentioned pass code, personal identity code (of the passenger). Using the above information the driver can confirm the Personality of the passenger as he / she is inside the passenger. In the simplest method requiring least technology, the driver is delivered with the passenger's personal identity code.

The driver either accepts or rejects the passenger by sending a message e.g. accept or reject to server (step 337). Optionally it can be always assumed that the driver accepts the passenger if he / she does not answer the message e.g. within a predetermined time, like 5 minutes for example.

Next (at step 338) the server 101 sends a message to the passenger in order to inform the passenger about the ride. The system sends messages to the passenger including identification information about the driver's car and either: a picture of the driver, a Fingerprint (of the driver), any digital identity (needed information about \ driver's digital identity), code sentences (question and answer pair of driver has registered), the previously mentioned pass code, personal identity code (of the driver). Using the above information the passenger can confirm the Personality of the driver as he / she inside the driver. In the simplest method requiring least technology, the passenger is delivered the driver's personal identity code.

In the meeting place driver and passenger confirm identify each other based on Descriptions sent. If pictures are sent they compare what they see. If personal identity codes are used driver ask from passenger to passenger identity code and Compares to answer from passenger to one he / she received from system (and vice versa). This procedure is used to confirm the identity of the participants and the Therefore a person can not use a stolen mobile device (mobile identity) in the system.

Passenger then sends a message to the server 101 informing the system that he / she has been picked-up by the driver (step 339). Also the driver can send a message to the server 101 informing the system that the passenger is now picked-up. The meaning of these messages is to indicate that the passenger and the driver have met and that they have agreed to share a ride. This message optionally authorizes (if not already done at steps 331 or 332) the system to locate the passenger's and driver's mobile phone for a time period that could, for example, equal to estimated drive time to work + N minutes, where N is a sum of maximum wait time, maximum drive time increase and Tolerance time. Alternatively, the system could be allowed to locate both the driver and passenger after offering (step 333) and request messages (step 334), respectively. The system can then track the positions of the driver and passenger at the approximate time of the pick-up. If the locations match, and the passenger does not send in step 339 a negative confirmation about the pickup, i.e. that pick-up is unsuccessful, the system assumes that the pick-up has happened, and the process continues.

As the meeting place is communicated through the system the system knows the · exact location of the passenger and driver at the moment this message was sent. The system can perform location update (step 340) for passenger's and driver's mobile devices to confirm location. The system continuously tracks the location of the passenger and driver (step 341). If the MS location is too much diverted from the route a check request is sent or directly an alarm would be triggered (step 342) and sent to the police or other emergency system together with the latest known location of the MS.

Finally the passenger identifies the system that he / she is approaching the drop-off location (step 343). This message's meaning is to indicate that the shared part of the trip is made. As the drop-off location is communicated through the system the system knows the exact location of the passenger and driver at the moment this message was sent. The system can perform a location update for the passenger's and driver's mobile devices to confirm the location. After the server 101 receives the message indicating that the trip is made (at step 343) the system considers the carpool as done. Optionally, the system communicates to the driver that the arriving message was received from the passenger. Location tracking is disabled (step 344) for driver and passenger mobile communications devices and the process ends. Location tracking can be disabled either immediately or shortly after the last messages are sent. Optionally the system can perform one more location update for passenger's and driver's mobile devices to make sure they're not driving together anymore.

At step 345, the passenger's account is debited with a predetermined amount of e.g. money or credits and flow proceeds to step 346 the driver's account is credited with a predetermined amount of money or credits. From step 346 the flow proceeds to step 347 the process ends.

Figure 4a illustrates a signaling diagram of a method according to an embodiment of the invention. In order to simplify this illustration, the system serves only one passenger and one driver. In a real situation, the amount of drivers and passengers is usually more than one. The passenger registers him / herself to the system by making a communication connection (401, 402) to the server. Also the driver registers him / herself to the system by making a communication connection (403, 404) to the server. The registration can be done e.g. via the Internet. The service profile is generated in this stage. It can consist of parameters such as routine routes, location checking periodicity, allowed deviation from the route, actions when some anomaly is detected (check SMS or call, alarm, etc.).

After registration the passenger and the driver may want to benefit from the services the system provides. The passenger sends a message (405) to the server, via SMSC, to inform the server that he / she would now use the route being stored in the server. A little later also the driver (406) sends a message to the server via SMSC in order to inform the server that he / she would now drive the route being stored in the server.

When the server receives messages (405 and 406) from passengers and drivers it starts to match them by comparing the route to messages to each other. A starting point and an end point of a passenger are compared to a corresponding starting point and an end point of a driver. If the starting points are located close enough to each other and / or the ending points are sufficiently close to each other, the server matches a driver and a passenger. The server sends a message 407 to the driver, consisting of the message identifying the passenger (eg name, picture, and / or pass code of the passenger, etc) and the location (street address) he / she is waiting for the lift . The message may further comprise the time of arrival when the driver should meet the passenger. The server sends a message 408 to the passenger, consisting of the message identifying the driver (eg name, picture, and / or pass code of the driver, etc) and the car he / she is driving (eg mark model and color) is coming to pick-up. The message may further comprise the estimated time of arrival.

Next the passenger and the driver meet and identify each other and the passenger sends a message 409 to the server indicating that the trip has started successfully. When the trip ends the passenger sends another message 410 indicating that the trip has ended successfully. Now the server 101 informs the passenger with a message 411 that the passenger account at the server 101 has been debited with an amount of money or credits. Next the server 101 sends a message 412 to the driver informing him / her that his / her account has been credited with an amount of money or credits.

Figure 4b illustrates a signaling diagram of a method according to another embodiment of the invention. The passenger registers him / herself to the system by making a communication connection (420, 421) to the server. Also a driver registers him / herself to the system by making a communication connection (422, 423) to the server. The registration can be done e.g. via the Internet. When a user (driver or passenger) wants his / her location to be traced he / she informs the system about when ordering to the system. The message should also contain information about the route that he / she has agreed with the other partner. The route information could be delivered by the Initiation of tracing or it might be stored in the server, in which case the user has only to indicate which route he / she is using. The information should (if the route is not stored on the server) include at least the start and stop points.

The passenger sends a message 424 to the server, via SMSC, to inform the server that he / she would now use the route being stored on the server. A little later also the driver 425 sends a message to the server via SMSC in order to inform the server that he / she would now drive the route being stored in the server.

When the server receives messages (424 and 425) from passengers and drivers it starts to match them by comparing the route to messages to each other. A starting point and an end point of a passenger are compared to a corresponding starting point and an end point of a driver. If the starting points are located close enough to each other and / or the ending points are sufficiently close to each other, the server matches a driver and a passenger. The server sends a message 426 to the driver, which includes the message identifying the passenger (eg name, picture, and / or pass code of the passenger, etc) and the location (street address) he / she is waiting for the lift . The message may further comprise the time of arrival when the driver should meet the passenger. The server sends a message 427 to the passenger, which includes the identification information of the driver (eg name, picture, and / or pass code of the driver, etc) and the car he / she is driving (eg mark model and color) is coming to pick-up. The message may further comprise the estimated time of arrival.

Next the passenger and the driver meet and identify each other and the passenger sends a message 428 to the server indicating that the trip has started successfully. Alternatively, the system can track the positions of the driver and passenger at the approximate time of the pick-up. If the locations match, and- the passenger does not send in step 428 a negative confirmation about the pickup, i.e. that pick-up is unsuccessful, the system assumes that the pick-up has happened, and the process continues. The location of the MS would then be traced (429) and if the MS location is too much diverted from the route (Step 430) a check request is sent (431) to the passenger's communication device. If no response (432) is received an alarm would be triggered (433) and sent to the police or other emergency system together with the latest known location of the MS. A user who's phone is set to be traced has to keep his / her phone on for the whole trip. After the ridesharing route is performed the user sends a message indicating that the tracing should be disabled and the server would be disabled the tracing provided that the MS is in the target area (close enough to the stop point). The user might also be able to configure the tracing of his / her phone in such a way that the server is automatically disabling the tracking as soon as the traced MS arrives to the target area. Naturally some password or pin codes should be used for disabling the tracking and also for the safety check some pin code or .password can be used. If users are participating in a ride-sharing organized by a server that creates matching of drivers and passengers in real-time, the triggering of safety features on and off can be included in the messaging used to set up the ride-sharing trip, therefore enabling the safety features would not require any further actions from the users.

In connection to carpool service the needed messages to authorize the system to perform location updates for the mobile devices can be fully integrated to the messages used to set up a carpool. Importantly the system knows the drive time estimate from the pick-up location to the drop-off location and thus the system can expect the arrival confirmation message. If the arrival confirmation message is not received in time, the safety procedure can be initialized.

If a problematic situation is detected, the code sentences the user has selected in the registration can be used to further improve the safety. As the safety procedure is initialized, the system asks for a certain (user selected) question from the user and depending on the validity of the answer the safety procedure is stopped or continued without indicating it to the user. This question and answer pair have to be different from one delivered to a carpool partner in setting up the carpool.

Figure 5 illustrates a block diagram of a device according to an embodiment of the invention. The device 500 comprises a processor 501 and a memory 502 for processing the tasks to be performed in the device. The memory 502 can comprise an example random access memory (RAM) and read only memory (ROM). The device further comprises a storage medium 503, for example, a hard disk of a desktop computer or a RAM memory, which further comprises an application 504 that may be an example of a computer program product according to the invention. The storage medium may further comprise a register 505 for storing information about the drivers and passengers that are using the services of the system. The device 500 is an example of a server located in a communication network. The device further has an input and output means for connecting to other elements of the network such as SMSC 104, GMLC 105, Internet 106 and PSAP 107 as illustrated in Figure 1b.

The server 500 is capable of receiving registration information from passengers and drivers via the Internet. All registration information is stored in the register 505. The server 500 receives request and offer messages from drivers and passengers via SMSC 104. The messages are stored in the register 505 and the application 504 performs matching of requests and offers in the register: When matched driver passenger pair is found, server requests location information from GMLC 105 for communication devices of matched driver and passenger. If a problem situation is detected, the server 400 sends a message to the PSAP 107 in order to inform the problem situation. The message can consist of an example of the name of the owner of a communication device having a problem and the location information of the communication device.

The above Disclosure illustrates the implementation of the invention and its embodiments by means of examples. A person skilled in the art will find it apparent that the invention is not restricted to the details of the above-described embodiments and that there are other ways of implementing the invention without deviating from the characteristics of the invention. The above embodiments should thus be considered as illustrative and not restrictive. Hence the possibilities of implementing and using the invention are only restricted by the claims and therefore the different alternative implementations of the invention, including equivalent implementations defined in the claims also Belong to the scope of the invention.

Claims (18)

1. A method for arranging transportation for at least two persons by a same vehicle driven by one of said persons, each of said persons having a communication device being capable of establishing a communication connection to a server connected to a communication network and sending and receiving messages to and from said server, the method comprising at the server: receiving registration information from a person wherein said registration information comprises at least an origination and a destination of at least one route to be transported, an identification identifying said person and registration to at least one of the following category: a driver of a vehicle and a passenger of a vehicle ' receiving a message from at least one registered driver, said message indicating a route of transportation, * receiving a message from at least one registered passenger, said message indicating a route of transportation, matching one registered driver and at least one registered passenger having substantially similar route, sending a message to said registered driver comprising at least identification and the route of said passenger, sending a message to said at least one registered passenger comprising identification of said driver; characterized in that the method comprises at the server: receiving a start message indicating successful start of transportation from said at least one registered passenger in response to successful identification of said driver, and receiving an ending message indicating successful end of transportation from said at least one registered passenger.

2. A method according to claim 1, characterized in that the method further comprises at the server, in response to said start message, enabling location tracking of a communication device of said passenger and said driver in order to confirm the location of said passenger and said driver.

3. A method according to claim 1, characterized in that the method further comprises at the server, in response to said route of transportation messages, enabling location tracking of a communication device of said passenger and said driver in order to confirm the location of said passenger and said driver.

4. A method according to claim 2, characterized in that the method further comprises at the server, sending a check request to the passenger if the location is diverted too much from the route.

5. A method according to claim 1, characterized in that the method further comprises at the server disabling location tracking of the communication devices of said passenger and said driver in response to said ending message.

6. A method according to claim 1, characterized in that the method further comprises at the server charging said passenger a certain amount of money in response to one of the following messages: said start message and said ending message.

7. A method according to claim 1, characterized in that the method further comprises at the server crediting said driver a certain amount of money in response to at least one of the following messages: said start message and said ending message.

8. A method according to claim 1, characterized in that the method further comprises at the server sending messages to be used to confirm the identity of passenger for a driver and messages to be used to confirm the identity of the driver to the passenger.

9. An electronic device (500) for arranging transportation for at least two persons by a same vehicle driven by one of said persons, said persons having a communication device being capable of establishing a communication connection to said device (500) connected to a communication network and sending and receiving messages to and from said device (500), the device comprising: receiving means for receiving registration information from a person wherein said registration information comprises at least an origination and a destination of at least one route to be transported, an identification identifying said person and registration to at least one of the following category: a driver of a vehicle and a passenger of a vehicle, receiving means for receiving a message from at least one registered driver, said message indicating a route of transportation, receiving means for receiving a message from at least one registered passenger, said message indicating a route of transportation, matching means for matching one registered driver and at least one registered passenger having substantially similar route, sending means for sending a message to said registered driver comprising at least identification and the route of said passenger, sending means for sending a message to said at least one registered passenger comprising identification of said driver; characterized in that the server comprises: receiving means for receiving a start message indicating successful start of transportation from said at least one registered passenger in response to successful identification of said driver, and receiving means for receiving an ending message indicating successful end of transportation from said at least one registered passenger.

10. A device according to claim 9, characterized in that the device further comprises enabling means for enabling location tracking of a communication device of said passenger and said, driver in order to confirm the location of said passenger and said driver in response to said start message.

11. A device according to claim 9, characterized in that the device further comprises enabling means for enabling location tracking of a communication device of said passenger and said driver in order to confirm the location of said passenger and said driver in response to said route indication messages.

12. A device according to claims 10 or 11, characterized in that the device further comprises sending means for sending a check request to the passenger if the location is diverted too much from the route.

13. A device according to claim 9, characterized in that the device further comprises disabling means for disabling location tracking of the communication devices of said passenger and said driver in response to said ending message.

14. A device according to claim 9, characterized in that the device further comprises charging means for charging said passenger a certain amount of money in response to one of the following messages: said start message and said ending message.

15. A device according to claim 9, characterized in that the device further comprises crediting means for crediting said driver a certain amount of money in response to at least one of the following messages: said start message and said ending message.

16. A device according to claim 9, characterized in that the device further comprises sending means for sending messages to be used to confirm the identity of passenger for a driver and messages to be used to confirm the identity of the driver to the passenger.

17. A system for arranging transportation for at least two persons by a same vehicle driven by one of said persons, said persons having a communication device being capable of establishing a communication connection to a device (500) connected to a communication network and sending and receiving messages to and from said device (500), the system comprising: receiving means for receiving registration information from a person wherein said registration information comprises at least an origination and a destination of at least one route to be transported, an identification identifying said person and registration to at least one of the following category: a driver of a vehicle and a passenger of a vehicle, receiving means for receiving a message from at least one registered driver, said message indicating a route of transportation, receiving means for receiving a message from at least one registered passenger, said message indicating a route of transportation, matching means for matching one registered driver and at least one registered passenger having substantially similar route, sending means for sending a message to said registered driver comprising at least identification and the route of said passenger, sending means for sending a message to said at least one registered passenger comprising identification of said driver; characterized in that the system comprises: receiving means for receiving a start message indicating successful start of transportation from said at least one registered passenger in response to successful identification of said driver, and receiving means for receiving an ending message indicating successful end of transportation from said at least one registered passenger.

18. A computer program product for an electronic device (500) for arranging transportation for at least two persons by a same vehicle driven by one of said persons, said persons having a communication device being capable of establishing a communication connection to said device (500) connected to a communication network and sending and receiving messages to and from said device (500), the computer program product comprising: computer program means for causing the device to receive registration information from a person wherein said registration information comprises at least an origination and a destination of a route to be transported, an identification identifying said person and registration to at least one of the following category: a driver of a vehicle and a passenger of a vehicle, computer program means for causing the device to receive a message from at least one registered driver, said message indicating a route of transportation, computer program means for causing the device to receive a message from at least one registered passenger, said message indicating a route of transportation, computer program means for causing the device to match one registered driver and at least one registered passenger having substantially similar route, computer program means for causing the device to send a message to said registered driver comprising at least identification and the route of said passenger, computer program means for causing the device to send a message to said at least one registered passenger comprising identification of said driver; characterized in that the computer program product comprises: computer program means for causing the device to receive a start message indicating successful start of transportation from said at least one registered passenger in response to successful identification of said driver, and computer program means for causing the device to receive an ending message indicating successful end of transportation from said at least one registered passenger.